GNOME Bugzilla – Bug 528879
crash in Home Folder: - right mouse click on f...
Last modified: 2008-04-19 10:40:28 UTC
What were you doing when the application crashed? - right mouse click on file - "open with" (oeffnen mit) --> crash Distribution: Debian lenny/sid Gnome Release: 2.22.0 2008-03-14 (Debian) BugBuddy Version: 2.22.0 System: Linux 2.6.24-1-686 #1 SMP Thu Mar 27 17:45:04 UTC 2008 i686 X Vendor: The X.Org Foundation X Vendor Release: 10300000 Selinux: No Accessibility: Disabled GTK+ Theme: Clearlooks Icon Theme: gnome Memory status: size: 69758976 vsize: 69758976 resident: 34631680 share: 18337792 rss: 34631680 rss_rlim: 4294967295 CPU usage: start_time: 1208601243 rtime: 507 utime: 470 stime: 37 cutime:0 cstime: 0 timeout: 0 it_real_value: 0 frequency: 100 Backtrace was generated from '/usr/bin/nautilus' Using host libthread_db library "/lib/i686/cmov/libthread_db.so.1". [Thread debugging using libthread_db enabled] [New Thread 0xb6b86720 (LWP 4606)] 0xffffe410 in __kernel_vsyscall ()
+ Trace 195617
Thread 1 (Thread 0xb6b86720 (LWP 4606))
----------- .xsession-errors --------------------- ERROR:dbus.connection:Exception in handler for D-Bus signal: Traceback (most recent call last): File "/var/lib/python-support/python2.4/dbus/connection.py", line 214, in maybe_handle_message self._handler(*args, **kwargs) TypeError: evolution_new_mail_callback() takes at most 2 arguments (3 given) e-attachment-bar.c-Message: DEBUG: Launch failed: Mit diesem Speicherort ist keine Vorgabeaktion verknüpft. (nautilus:2972): Eel-WARNING **: No extension, not implemented yet Initializing nautilus-open-terminal extension seahorse nautilus module initialized Initializing nautilus-image-converter extension Initializing gnome-mount extension (nautilus:4606): Eel-WARNING **: No extension, not implemented yet --------------------------------------------------
Thanks for taking the time to report this bug. This particular bug has already been reported into our bug tracking system, but we are happy to tell you that the problem has already been fixed. It should be solved in the next software version. You may want to check for a software upgrade. *** This bug has been marked as a duplicate of 355018 ***