Bug 381199 – crash in Trash: Nothing. The screensave...

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 381199 - crash in Trash: Nothing. The screensave...


Summary:	crash in Trash: Nothing. The screensave...


Status:	RESOLVED DUPLICATE of bug 366370

Product:	gnome-applets
Classification:	Other
Component:	trash applet
Version:	unspecified
Hardware:	Other All

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

URL:
Whiteboard:

Depends on:
Blocks:

Reported:	2006-12-01 08:59 UTC by jeremy_langley
Modified:	2006-12-01 10:10 UTC

See Also:
GNOME target:	---
GNOME version:	2.15/2.16

Description jeremy_langley 2006-12-01 08:59:47 UTC

What were you doing when the application crashed?
Nothing.  The screensaver just came on and when I returned I saw bug buddy there waiting.


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: 288346112 vsize: 288346112 resident: 7983104 share: 6246400 rss: 7983104 rss_rlim: -1
CPU usage: start_time: 1164962697 rtime: 3 utime: 2 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 46912496358512 (LWP 17858)]
(no debugging symbols found)
0x000000328ac0d96f in waitpid () from /lib64/libpthread.so.0

+ Trace 90766

Thread 1 (Thread 46912496358512 (LWP 17858))

#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 Carlos Garcia Campos 2006-12-01 10:10:50 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 ***