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 395348 - crash in Trash: Killing yum-updatesd ser...
crash in Trash: Killing yum-updatesd ser...
Status: RESOLVED DUPLICATE of bug 366370
Product: gnome-applets
Classification: Other
Component: trash applet
unspecified
Other All
: High critical
: ---
Assigned To: gnome-applets Maintainers
gnome-applets Maintainers
Depends on:
Blocks:
 
 
Reported: 2007-01-11 11:14 UTC by erwansalim
Modified: 2007-01-15 00:30 UTC
See Also:
GNOME target: ---
GNOME version: 2.15/2.16


Description erwansalim 2007-01-11 11:14:29 UTC 
What were you doing when the application crashed?
Killing yum-updatesd service, Kill X Window Server


Distribution: Fedora Core release 6 (Zod)
Gnome Release: 2.16.0 2006-09-04 (Red Hat, Inc)
BugBuddy Version: 2.16.0

Memory status: size: 78004224 vsize: 0 resident: 78004224 share: 0 rss: 8749056 rss_rlim: 0
CPU usage: start_time: 1168514327 rtime: 0 utime: 10 stime: 0 cutime:8 cstime: 0 timeout: 2 it_real_value: 0 frequency: 0

Backtrace was generated from '/usr/libexec/trashapplet'

(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 -1208445232 (LWP 25256)]
(no debugging symbols found)
0x00526402 in __kernel_vsyscall ()

+ Trace 101221

Thread 1 (Thread -1208445232 (LWP 25256))

  • #0 __kernel_vsyscall
  • #1 __waitpid_nocancel
    from /lib/libpthread.so.0
  • #2 gnome_gtk_module_info_get
    from /usr/lib/libgnomeui-2.so.0
  • #3 <signal handler called>
  • #4 __kernel_vsyscall
  • #5 raise
    from /lib/libc.so.6
  • #6 abort
    from /lib/libc.so.6
  • #7 dbus_malloc
    from /lib/libdbus-1.so.3
  • #8 dbus_watch_set_data
    from /lib/libdbus-1.so.3
  • #9 dbus_connection_send_with_reply_and_block
    from /lib/libdbus-1.so.3
  • #10 dbus_bus_start_service_by_name
    from /lib/libdbus-1.so.3
  • #11 gnome_vfs_daemon_message_iter_get_file_info
    from /usr/lib/libgnomevfs-2.so.0
  • #12 gnome_vfs_daemon_message_iter_get_file_info
    from /usr/lib/libgnomevfs-2.so.0
  • #13 gnome_vfs_daemon_message_iter_get_file_info
    from /usr/lib/libgnomevfs-2.so.0
  • #14 dbus_connection_dispatch
    from /lib/libdbus-1.so.3
  • #15 dbus_server_setup_with_g_main
    from /usr/lib/libdbus-glib-1.so.2
  • #16 g_main_context_dispatch
    from /lib/libglib-2.0.so.0
  • #17 g_main_context_check
    from /lib/libglib-2.0.so.0
  • #18 g_main_loop_run
    from /lib/libglib-2.0.so.0
  • #19 bonobo_main
    from /usr/lib/libbonobo-2.so.0
  • #20 bonobo_generic_factory_main_timeout
    from /usr/lib/libbonobo-2.so.0
  • #21 bonobo_generic_factory_main
    from /usr/lib/libbonobo-2.so.0
  • #22 panel_applet_factory_main_closure
    from /usr/lib/libpanel-applet-2.so.0
  • #23 panel_applet_factory_main
    from /usr/lib/libpanel-applet-2.so.0
  • #24 g_cclosure_marshal_VOID__VOID
  • #25 __libc_start_main
    from /lib/libc.so.6
  • #26 g_cclosure_marshal_VOID__VOID
  • #0 __kernel_vsyscall 






Comment 1


palfrey





          2007-01-11 18:40:05 UTC
        



Thanks for taking the time to report this bug.
Unfortunately, that stack trace is missing some elements that will help a lot to solve the problem, so it will be hard for the developers to fix that crash. Can you get us a stack trace with debugging symbols? Please see http://live.gnome.org/GettingTraces for more information on how to do so. Thanks in advance!







Comment 2


palfrey





          2007-01-15 00:30:20 UTC
        



Thanks for the bug report. This particular bug has already been reported into our bug tracking system, but please feel free to report any further bugs you find.


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