GNOME Bugzilla – Bug 527689
crash in Home Folder: Hello, After I have rig...
Last modified: 2008-04-13 09:41:08 UTC
What were you doing when the application crashed? Hello, After I have right-clicked a txt-file of mime-type 'application/octet-stream', then "open with" (sorry, I do not know the corresponding translation of the german context-menu point "Mit anderer Anwendung öffnen"), the application nautilus (as a browser) crashed. Thanks, sebastian mach/sebbb Distribution: Debian lenny/sid Gnome Release: 2.22.0 2008-03-14 (Debian) BugBuddy Version: 2.22.0 System: Linux 2.6.22-3-k7 #1 SMP Sun Feb 10 21:04:14 UTC 2008 i686 X Vendor: The X.Org Foundation X Vendor Release: 10300000 Selinux: No Accessibility: Disabled GTK+ Theme: Clearlooks Human Icon Theme: Human Memory status: size: 89653248 vsize: 89653248 resident: 30224384 share: 13373440 rss: 30224384 rss_rlim: 4294967295 CPU usage: start_time: 1207937904 rtime: 6103 utime: 5451 stime: 652 cutime:13 cstime: 8 timeout: 0 it_real_value: 0 frequency: 100 Backtrace was generated from '/usr/bin/nautilus' (no debugging symbols found) Using host libthread_db library "/lib/i686/cmov/libthread_db.so.1". (no debugging symbols found) [Thread debugging using libthread_db enabled] [New Thread 0xb6ba6720 (LWP 3934)] [New Thread 0xb25ffb90 (LWP 26462)] 0xffffe410 in __kernel_vsyscall ()
+ Trace 195021
Thread 1 (Thread 0xb6ba6720 (LWP 3934))
----------- .xsession-errors (20 sec old) --------------------- min bigger or equal to max Traceback (most recent call last): File "/usr/bin/lybniz", line 809, in key_press_plot plot(None) File "/usr/bin/lybniz", line 505, in plot graph.plot() File "/usr/bin/lybniz", line 274, in plot for i in marks(self.y_min,self.y_max): File "/usr/bin/lybniz", line 96, in marks raise ValueError ValueError Fenstermanager-Warnung:Buggy client sent a _NET_ACTIVE_WINDOW message with a timestamp of 0 for 0x5c0001f (Archivmana) Fenstermanager-Warnung:meta_window_activate called by a pager with a 0 timestamp; the pager needs to be fixed. (nautilus:3934): 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 ***