After an evaluation, GNOME has moved from Bugzilla to GitLab. Learn more about GitLab.
No new issues can be reported in GNOME Bugzilla anymore.
To report an issue in a GNOME project, go to GNOME GitLab.
Do not go to GNOME Gitlab for: Bluefish, Doxygen, GnuCash, GStreamer, java-gnome, LDTP, NetworkManager, Tomboy.
Bug 455360 - crash in Panel: I was trying to remove p...
crash in Panel: I was trying to remove p...
Status: RESOLVED DUPLICATE of bug 441520
Product: gnome-panel
Classification: Other
Component: general
2.18.x
Other All
: High critical
: ---
Assigned To: Panel Maintainers
Panel Maintainers
Depends on:
Blocks:
 
 
Reported: 2007-07-09 23:50 UTC by kerkus
Modified: 2007-07-10 13:31 UTC
See Also:
GNOME target: ---
GNOME version: 2.17/2.18



Description kerkus 2007-07-09 23:50:41 UTC
Version: 2.18.2

What were you doing when the application crashed?
I was trying to remove password revelation from task bar


Distribution: Fedora release 7 (Moonshine)
Gnome Release: 2.18.2 2007-05-28 (Red Hat, Inc)
BugBuddy Version: 2.18.0

System: Linux 2.6.21-1.3228.fc7 #1 SMP Tue Jun 12 15:37:31 EDT 2007 i686
X Vendor: The X.Org Foundation
X Vendor Release: 10300000
Selinux: No
Accessibility: Disabled
GTK+ Theme: Clearlooks
Icon Theme: Fedora

Memory status: size: 90800128 vsize: 90800128 resident: 16961536 share: 11952128 rss: 16961536 rss_rlim: 4294967295
CPU usage: start_time: 1183392995 rtime: 4338 utime: 3651 stime: 687 cutime:1 cstime: 13 timeout: 0 it_real_value: 0 frequency: 100

Backtrace was generated from '/usr/bin/gnome-panel'

(no debugging symbols found)
Using host libthread_db library "/lib/libthread_db.so.1".
(no debugging symbols found)
[Thread debugging using libthread_db enabled]
[New Thread -1208719648 (LWP 3893)]
(no debugging symbols found)
0x00400402 in __kernel_vsyscall ()

Thread 1 (Thread -1208719648 (LWP 3893))

  • #0 __kernel_vsyscall
  • #1 __waitpid_nocancel
    from /lib/libpthread.so.0
  • #2 ??
    from /usr/lib/libgnomeui-2.so.0
  • #3 <signal handler called>
  • #4 panel_profile_delete_object
  • #5 ??
    from /usr/lib/libbonoboui-2.so.0
  • #6 g_closure_invoke
    from /lib/libgobject-2.0.so.0
  • #7 bonobo_closure_invoke_va_list
    from /usr/lib/libbonobo-2.so.0
  • #8 bonobo_closure_invoke
    from /usr/lib/libbonobo-2.so.0
  • #9 ??
    from /usr/lib/libbonoboui-2.so.0
  • #10 _ORBIT_skel_small_Bonobo_UIComponent_execVerb
    from /usr/lib/libbonobo-2.so.0
  • #11 ??
    from /usr/lib/libORBit-2.so.0
  • #12 ORBit_OAObject_invoke
    from /usr/lib/libORBit-2.so.0
  • #13 ORBit_small_invoke_adaptor
    from /usr/lib/libORBit-2.so.0
  • #14 ??
    from /usr/lib/libORBit-2.so.0
  • #15 ??
    from /usr/lib/libORBit-2.so.0
  • #16 ??
    from /usr/lib/libORBit-2.so.0
  • #17 ORBit_handle_request
    from /usr/lib/libORBit-2.so.0
  • #18 giop_connection_handle_input
    from /usr/lib/libORBit-2.so.0
  • #19 ??
    from /usr/lib/libORBit-2.so.0
  • #20 ??
    from /usr/lib/libORBit-2.so.0
  • #21 g_main_context_dispatch
    from /lib/libglib-2.0.so.0
  • #22 ??
    from /lib/libglib-2.0.so.0
  • #23 g_main_loop_run
    from /lib/libglib-2.0.so.0
  • #24 gtk_main
    from /usr/lib/libgtk-x11-2.0.so.0
  • #25 main
  • #0 __kernel_vsyscall


----------- .xsession-errors ---------------------
warning: .dynamic section for "/usr/lib/libcroco-0.6.so.3" is not at the expected address
warning: difference appears to be caused by prelink, adjusting expectations
warning: .dynamic section for "/usr/lib/libbz2.so.1" is not at the expected address
warning: difference appears to be caused by prelink, adjusting expectations
warning: .dynamic section for "/lib/libattr.so.1" is not at the expected address
warning: difference appears to be caused by prelink, adjusting expectations
warning: .dynamic section for "/lib/libacl.so.1" is not at the expected address
warning: difference appears to be caused by prelink, adjusting expectations
--------------------------------------------------
Comment 1 Vincent Untz 2007-07-10 13:31:49 UTC
Thanks for taking the time to report this bug.
This particular bug has already been reported into our bug tracking system, but the maintainers need more information to fix the bug. Could you please answer the questions in the other report in order to help the developers?


*** This bug has been marked as a duplicate of 441520 ***