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 520512 - crash in Open Folder: right-click on a file (o...
crash in Open Folder: right-click on a file (o...
Status: RESOLVED DUPLICATE of bug 355018
Product: nautilus
Classification: Core
Component: general
2.20.x
Other All
: High critical
: ---
Assigned To: Nautilus Maintainers
Nautilus Maintainers
Depends on:
Blocks:
 
 
Reported: 2008-03-05 13:08 UTC by noone
Modified: 2008-03-06 16:55 UTC
See Also:
GNOME target: ---
GNOME version: 2.19/2.20



Description noone 2008-03-05 13:08:18 UTC
Version: 2.20.0

What were you doing when the application crashed?
right-click on a file (on the samba network) without extension (.ext) -> open with ...


Distribution: Debian lenny/sid
Gnome Release: 2.20.3 2008-01-12 (Debian)
BugBuddy Version: 2.20.1

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: 60900000
Selinux: No
Accessibility: Disabled
GTK+ Theme: Clearlooks
Icon Theme: gnome

Memory status: size: 85082112 vsize: 85082112 resident: 28135424 share: 16076800 rss: 28135424 rss_rlim: 4294967295
CPU usage: start_time: 1204714033 rtime: 1974 utime: 1809 stime: 165 cutime:0 cstime: 1 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 0xb6b276c0 (LWP 6175)]
(no debugging symbols found)
0xffffe410 in __kernel_vsyscall ()

Thread 1 (Thread 0xb6b276c0 (LWP 6175))

  • #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 (411242 sec old) ---------------------
Window manager warning: Invalid WM_TRANSIENT_FOR window 0x2e00003 specified for 0x2e0037a (Page Setup).
Window manager warning: Invalid WM_TRANSIENT_FOR window 0x2e00003 specified for 0x2e0047e (Properties).
Window manager warning: Invalid WM_TRANSIENT_FOR window 0x2e00003 specified for 0x2e005c1 (Page Setup).
Window manager warning: Buggy client sent a _NET_ACTIVE_WINDOW message with a timestamp of 0 for 0x2e00058 (template-r)
Window manager warning: meta_window_activate called by a pager with a 0 timestamp; the pager needs to be fixed.
Window manager warning: Buggy client sent a _NET_ACTIVE_WINDOW message with a timestamp of 0 for 0x2e00058 (template-r)
Window manager warning: meta_window_activate called by a pager with a 0 timestamp; the pager needs to be fixed.
** (gnome-cups-manager:7712): CRITICAL **: gnome_cups_request_new_for_printer: assertion `gnome_cups_printer_get_attributes_initialized (printer)' failed
** (gnome-cups-manager:7712): WARNING **: Neither request nor output_fd set
Window manager warning: Buggy client sent a _NET_ACTIVE_WINDOW message with a timestamp of 0 for 0x2800003 (slavenka -)
Window manager warning: meta_window_activate called by a pager with a 0 timestamp; the pager needs to be fixed.
Window manager warning: CurrentTime used to choose focus window; focus window may not be correct.
Window manager warning: Got a request to focus the no_focus_window with a timestamp of 0.  This shouldn't happen!
--------------------------------------------------
Comment 1 Cosimo Cecchi 2008-03-06 16:55:39 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 ***