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 382443 - crash in Trash: yum update I believe...b...
crash in Trash: yum update I believe...b...
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: 2006-12-05 00:31 UTC by dhuckaby
Modified: 2006-12-05 13:48 UTC
See Also:
GNOME target: ---
GNOME version: 2.15/2.16



Description dhuckaby 2006-12-05 00:31:37 UTC
What were you doing when the application crashed?
yum update I believe...but it's still going strong in the background...


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

System: Linux 2.6.18-1.2849.fc6 #1 SMP Fri Nov 10 12:34:46 EST 2006 x86_64
X Vendor: The X.Org Foundation
X Vendor Release: 60900000
Selinux: Permissive
Accessibility: Disabled

Memory status: size: 471609344 vsize: 471609344 resident: 10813440 share: 8192000 rss: 10813440 rss_rlim: -1
CPU usage: start_time: 1165277671 rtime: 5 utime: 4 stime: 1 cutime:0 cstime: 0 timeout: 0 it_real_value: 0 frequency: 100

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

(no debugging symbols found)
Using host libthread_db library "/lib64/libthread_db.so.1".
(no debugging symbols found)
[Thread debugging using libthread_db enabled]
[New Thread 46912670317424 (LWP 4131)]
(no debugging symbols found)
0x00002aaaaf83096f in waitpid () from /lib64/libpthread.so.0

Thread 1 (Thread 46912670317424 (LWP 4131))

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

Comment 1 Susana 2006-12-05 13:48:10 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 ***