Bug 448280 – crash in Panel:

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 448280 - crash in Panel:


Summary:	crash in Panel:


Status:	RESOLVED DUPLICATE of bug 446183

Product:	gnome-panel
Classification:	Other
Component:	general
Version:	2.18.x
Hardware:	Other All

Importance:	High critical
Target Milestone:	---
Assigned To:	Panel Maintainers
QA Contact:	Panel Maintainers

URL:
Whiteboard:

Depends on:
Blocks:

Reported:	2007-06-16 18:46 UTC by vpmm92
Modified:	2007-06-17 16:40 UTC

See Also:
GNOME target:	---
GNOME version:	2.17/2.18

Description vpmm92 2007-06-16 18:46:09 UTC

Version: 2.18.2

What were you doing when the application crashed?



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: Permissive
Accessibility: Disabled
GTK+ Theme: Clearlooks
Icon Theme: Fedora

Memory status: size: 35545088 vsize: 35545088 resident: 16236544 share: 13717504 rss: 16236544 rss_rlim: 4294967295
CPU usage: start_time: 1182019554 rtime: 27 utime: 21 stime: 6 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 -1208875296 (LWP 3154)]
(no debugging symbols found)
0x00b51402 in __kernel_vsyscall ()

+ Trace 141486

Thread 1 (Thread -1208875296 (LWP 3154))

#0 __kernel_vsyscall
#1 __waitpid_nocancel
from /lib/libpthread.so.0
#2 g_cclosure_marshal_VOID__ENUM
from /usr/lib/libgnomeui-2.so.0
#3 <signal handler called>
#4 g_cclosure_marshal_VOID__ENUM
from /usr/lib/libgtk-x11-2.0.so.0
#5 g_hash_table_foreach
from /lib/libglib-2.0.so.0
#6 gtk_rc_reset_styles
from /usr/lib/libgtk-x11-2.0.so.0
#7 g_cclosure_marshal_VOID__ENUM
from /usr/lib/libgtk-x11-2.0.so.0
#8 g_cclosure_marshal_VOID__PARAM
from /lib/libgobject-2.0.so.0
#9 g_cclosure_marshal_VOID__ENUM
from /lib/libgobject-2.0.so.0
#10 g_closure_invoke
from /lib/libgobject-2.0.so.0
#11 g_cclosure_marshal_VOID__ENUM
from /lib/libgobject-2.0.so.0
#12 g_signal_emit_valist
from /lib/libgobject-2.0.so.0
#13 g_signal_emit
from /lib/libgobject-2.0.so.0
#14 g_cclosure_marshal_VOID__ENUM
from /lib/libgobject-2.0.so.0
#15 g_cclosure_marshal_VOID__ENUM
from /lib/libgobject-2.0.so.0
#16 g_object_notify
from /lib/libgobject-2.0.so.0
#17 g_cclosure_marshal_VOID__ENUM
from /usr/lib/libgtk-x11-2.0.so.0
#18 gtk_main_do_event
from /usr/lib/libgtk-x11-2.0.so.0
#19 g_cclosure_marshal_VOID__ENUM
from /usr/lib/libgdk-x11-2.0.so.0
#20 g_main_context_dispatch
from /lib/libglib-2.0.so.0
#21 g_cclosure_marshal_VOID__ENUM
from /lib/libglib-2.0.so.0
#22 g_main_loop_run
from /lib/libglib-2.0.so.0
#23 gtk_main
from /usr/lib/libgtk-x11-2.0.so.0
#24 main
#0 __kernel_vsyscall



----------- .xsession-errors ---------------------
  File "/usr/bin/puplet", line 371, in <module>
    main()
  File "/usr/bin/puplet", line 368, in main
    p.run()
  File "/usr/bin/puplet", line 355, in run
    self._getOnDbus()
  File "/usr/bin/puplet", line 229, in _getOnDbus
    "/Updatesd")
  File "/usr/lib/python2.5/site-packages/dbus/_dbus.py", line 410, in get_object
    follow_name_owner_changes=follow_name_owner_changes)
  File "/usr/lib/python2.5/site-packages/dbus/proxies.py", line 230, in __init__
    _dbus_bindings.UInt32(0))
  File "/usr/lib/python2.5/site-packages/dbus/proxies.py", line 169, in __call__
    reply_message = self._connection.send_message_with_reply_and_block(message, timeout)
dbus.DBusException: org.freedesktop.DBus.Error.ServiceUnknown: The name edu.duke.linux.yum was not provided by any .service files
--------------------------------------------------

Comment 1 Vincent Untz 2007-06-17 16:40:30 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 446183 ***