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 527689 - crash in Home Folder: Hello, After I have rig...
crash in Home Folder: Hello, After I have rig...
Status: RESOLVED DUPLICATE of bug 355018
Product: nautilus
Classification: Core
Component: general
unspecified
Other All
: High critical
: ---
Assigned To: Nautilus Maintainers
Nautilus Maintainers
Depends on:
Blocks:
 
 
Reported: 2008-04-12 11:13 UTC by Sebastian Mach
Modified: 2008-04-13 09:41 UTC
See Also:
GNOME target: ---
GNOME version: 2.21/2.22



Description Sebastian Mach 2008-04-12 11:13:37 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 ()

Thread 1 (Thread 0xb6ba6720 (LWP 3934))

  • #0 __kernel_vsyscall
  • #1 waitpid
    from /lib/i686/cmov/libpthread.so.0
  • #2 g_spawn_sync
    from /usr/lib/libglib-2.0.so.0
  • #3 g_spawn_command_line_sync
    from /usr/lib/libglib-2.0.so.0
  • #4 ??
    from /usr/lib/gtk-2.0/modules/libgnomebreakpad.so
  • #5 <signal handler called>
  • #6 strcmp
    from /lib/i686/cmov/libc.so.6
  • #7 g_str_equal
    from /usr/lib/libglib-2.0.so.0
  • #8 ??
    from /usr/lib/libeel-2-2.20.so
  • #9 ??
  • #10 ??
  • #0 __kernel_vsyscall


----------- .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
--------------------------------------------------
Comment 1 Cosimo Cecchi 2008-04-13 09:41:08 UTC
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 ***