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 474032 - crash in Panel: removing a applicationfr...
crash in Panel: removing a applicationfr...
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-09-05 21:21 UTC by jgiolma
Modified: 2007-09-09 11:12 UTC
See Also:
GNOME target: ---
GNOME version: 2.17/2.18



Description jgiolma 2007-09-05 21:21:24 UTC
Version: 2.18.3

What were you doing when the application crashed?
removing a applicationfrom the panel--gnome has been crashing a lot for me, and has been leaving applications running (gam-server, bonobo-activation server) after I log out.


Distribution: Fedora release 7 (Moonshine)
Gnome Release: 2.18.3 2007-07-02 (Red Hat, Inc)
BugBuddy Version: 2.18.0

System: Linux 2.6.22.1-41.fc7 #1 SMP Fri Jul 27 18:10:34 EDT 2007 i686
X Vendor: The X.Org Foundation
X Vendor Release: 10300000
Selinux: Enforcing
Accessibility: Disabled
GTK+ Theme: Clearlooks
Icon Theme: Fedora

Memory status: size: 54325248 vsize: 54325248 resident: 26755072 share: 23199744 rss: 26755072 rss_rlim: 4294967295
CPU usage: start_time: 1189027135 rtime: 77 utime: 70 stime: 7 cutime:0 cstime: 0 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 -1208674592 (LWP 7088)]
(no debugging symbols found)
0x00110402 in __kernel_vsyscall ()

Thread 1 (Thread -1208674592 (LWP 7088))

  • #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_context_iteration
    from /lib/libglib-2.0.so.0
  • #24 link_main_iteration
    from /usr/lib/libORBit-2.so.0
  • #25 giop_recv_buffer_get
    from /usr/lib/libORBit-2.so.0
  • #26 ORBit_small_invoke_stub
    from /usr/lib/libORBit-2.so.0
  • #27 ORBit_small_invoke_stub_n
    from /usr/lib/libORBit-2.so.0
  • #28 ORBit_c_stub_invoke
    from /usr/lib/libORBit-2.so.0
  • #29 Bonobo_PropertyBag_setValue
    from /usr/lib/libbonobo-2.so.0
  • #30 bonobo_pbclient_set_value
    from /usr/lib/libbonobo-2.so.0
  • #31 bonobo_pbclient_set_string
    from /usr/lib/libbonobo-2.so.0
  • #32 panel_applet_frame_change_background
  • #33 ??
    from /usr/lib/libgtk-x11-2.0.so.0
  • #34 gtk_container_foreach
    from /usr/lib/libgtk-x11-2.0.so.0
  • #35 ??
  • #36 g_cclosure_marshal_VOID__VOID
    from /lib/libgobject-2.0.so.0
  • #37 g_closure_invoke
    from /lib/libgobject-2.0.so.0
  • #38 ??
    from /lib/libgobject-2.0.so.0
  • #39 g_signal_emit_valist
    from /lib/libgobject-2.0.so.0
  • #40 g_signal_emit
    from /lib/libgobject-2.0.so.0
  • #41 ??
  • #42 ??
  • #43 ??
  • #44 g_cclosure_marshal_VOID__OBJECT
    from /lib/libgobject-2.0.so.0
  • #45 ??
    from /lib/libgobject-2.0.so.0
  • #46 g_closure_invoke
    from /lib/libgobject-2.0.so.0
  • #47 ??
    from /lib/libgobject-2.0.so.0
  • #48 g_signal_emit_valist
    from /lib/libgobject-2.0.so.0
  • #49 g_signal_emit
    from /lib/libgobject-2.0.so.0
  • #50 ??
    from /usr/lib/libgtk-x11-2.0.so.0
  • #51 ??
    from /usr/lib/libgtk-x11-2.0.so.0
  • #52 ??
    from /usr/lib/libgtk-x11-2.0.so.0
  • #53 gtk_container_forall
    from /usr/lib/libgtk-x11-2.0.so.0
  • #54 ??
    from /usr/lib/libgtk-x11-2.0.so.0
  • #55 ??
    from /usr/lib/libgtk-x11-2.0.so.0
  • #56 gtk_container_forall
    from /usr/lib/libgtk-x11-2.0.so.0
  • #57 ??
    from /usr/lib/libgtk-x11-2.0.so.0
  • #58 ??
    from /usr/lib/libgtk-x11-2.0.so.0
  • #59 gtk_container_forall
    from /usr/lib/libgtk-x11-2.0.so.0
  • #60 ??
    from /usr/lib/libgtk-x11-2.0.so.0
  • #61 gtk_widget_reset_rc_styles
    from /usr/lib/libgtk-x11-2.0.so.0
  • #62 ??
    from /usr/lib/libgtk-x11-2.0.so.0
  • #63 gtk_rc_reparse_all_for_settings
    from /usr/lib/libgtk-x11-2.0.so.0
  • #64 ??
    from /usr/lib/libgtk-x11-2.0.so.0
  • #65 g_cclosure_marshal_VOID__PARAM
    from /lib/libgobject-2.0.so.0
  • #66 g_closure_invoke
    from /lib/libgobject-2.0.so.0
  • #67 ??
    from /lib/libgobject-2.0.so.0
  • #68 g_signal_emit_valist
    from /lib/libgobject-2.0.so.0
  • #69 g_signal_emit
    from /lib/libgobject-2.0.so.0
  • #70 ??
    from /lib/libgobject-2.0.so.0
  • #71 ??
    from /lib/libgobject-2.0.so.0
  • #72 g_object_notify
    from /lib/libgobject-2.0.so.0
  • #73 ??
    from /usr/lib/libgtk-x11-2.0.so.0
  • #74 gtk_main_do_event
    from /usr/lib/libgtk-x11-2.0.so.0
  • #75 ??
    from /usr/lib/libgdk-x11-2.0.so.0
  • #76 g_main_context_dispatch
    from /lib/libglib-2.0.so.0
  • #77 ??
    from /lib/libglib-2.0.so.0
  • #78 g_main_loop_run
    from /lib/libglib-2.0.so.0
  • #79 gtk_main
    from /usr/lib/libgtk-x11-2.0.so.0
  • #80 main
  • #0 __kernel_vsyscall


----------- .xsession-errors (35 sec old) ---------------------
    self._getOnDbus()
  File "/usr/bin/puplet", line 229, in _getOnDbus
    "/Updatesd")
  File "/usr/lib/python2.5/site-packages/dbus/bus.py", line 226, in get_object
    follow_name_owner_changes=follow_name_owner_changes)
  File "/usr/lib/python2.5/site-packages/dbus/proxies.py", line 236, in __init__
    self._named_service = conn.activate_name_owner(bus_name)
  File "/usr/lib/python2.5/site-packages/dbus/bus.py", line 165, in activate_name_owner
    self.start_service_by_name(bus_name)
  File "/usr/lib/python2.5/site-packages/dbus/bus.py", line 261, in start_service_by_name
    'su', (bus_name, flags)))
  File "/usr/lib/python2.5/site-packages/dbus/connection.py", line 598, in call_blocking
    message, timeout)
dbus.exceptions.DBusException: org.freedesktop.DBus.Error.ServiceUnknown: The name edu.duke.linux.yum was not provided by any .service files
Window manager warning: Invalid WM_TRANSIENT_FOR window 0x448 specified for 0xe001f8 ().
--------------------------------------------------
Comment 1 Vincent Untz 2007-09-06 09:08:05 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 ***
Comment 2 jgiolma 2007-09-06 13:39:12 UTC
Are there questions for me to address?  I didn't find any here or under 441520.

In case this is helpful--we have a script we use to remove users' gnome files (when there are problems, and when we do upgrades of the OS).  Running the script seems to postpone the recurrence of my problems--especially with the panel.
Comment 3 Vincent Untz 2007-09-09 11:12:40 UTC
What we need is a good stack trace so we can know what's happening. Please see
http://live.gnome.org/GettingTraces for more information on how to do so.