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 517805 - crash in Open Folder:
crash in Open Folder:
Status: RESOLVED DUPLICATE of bug 406462
Product: nautilus
Classification: Core
Component: general
2.20.x
Other All
: High critical
: ---
Assigned To: Nautilus Maintainers
Nautilus Maintainers
Depends on:
Blocks:
 
 
Reported: 2008-02-21 06:52 UTC by brett_senior
Modified: 2008-02-21 09:36 UTC
See Also:
GNOME target: ---
GNOME version: 2.19/2.20



Description brett_senior 2008-02-21 06:52:28 UTC
Version: 2.20.0

What were you doing when the application crashed?



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

System: Linux 2.6.22-3-686 #1 SMP Sun Feb 10 20:20:49 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: 86138880 vsize: 86138880 resident: 33808384 share: 16371712 rss: 33808384 rss_rlim: 4294967295
CPU usage: start_time: 1203561582 rtime: 6292 utime: 5490 stime: 802 cutime:0 cstime: 6 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 0xb6c81980 (LWP 5961)]
0xffffe410 in __kernel_vsyscall ()

Thread 1 (Thread 0xb6c81980 (LWP 5961))

  • #0 __kernel_vsyscall
  • #1 waitpid
    from /lib/i686/cmov/libpthread.so.0
  • #2 IA__g_spawn_sync
    at gspawn.c line 374
  • #3 IA__g_spawn_command_line_sync
    at gspawn.c line 682
  • #4 ??
    from /usr/lib/gtk-2.0/modules/libgnomebreakpad.so
  • #5 <signal handler called>
  • #6 IA__gtk_widget_get_toplevel
    at gtkwidget.c line 7283
  • #7 gtk_widget_get_screen_unchecked
    at gtkwidget.c line 6581
  • #8 IA__gtk_widget_has_screen
    at gtkwidget.c line 6654
  • #9 recompute_idle_func
    at gtkentry.c line 3198
  • #10 gdk_threads_dispatch
    at gdk.c line 470
  • #11 g_idle_dispatch
    at gmain.c line 4142
  • #12 IA__g_main_context_dispatch
    at gmain.c line 2064
  • #13 g_main_context_iterate
    at gmain.c line 2697
  • #14 IA__g_main_loop_run
    at gmain.c line 2905
  • #15 IA__gtk_main
    at gtkmain.c line 1163
  • #16 ??
  • #17 ??
  • #18 ??
  • #0 __kernel_vsyscall


----------- .xsession-errors (271 sec old) ---------------------
Window manager warning: Buggy client sent a _NET_ACTIVE_WINDOW message with a timestamp of 0 for 0x188d53f (Save as)
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 0x188d53f (Save as)
Window manager warning: meta_window_activate called by a pager with a 0 timestamp; the pager needs to be fixed.
Window manager warning: Window 0x20002d5 (AntiVirus ) sets an MWM hint indicating it isn't resizable, but sets min size 1 x 1 and max size 2147483647 x 2147483647; this doesn't make much sense.
Window manager warning: Window 0x2000004 (About Anti) sets an MWM hint indicating it isn't resizable, but sets min size 100 x 70 and max size 1270 x 1014; this doesn't make much sense.
Window manager warning: Window 0x2000004 (About Anti) sets an MWM hint indicating it isn't resizable, but sets min size 100 x 70 and max size 1270 x 1014; this doesn't make much sense.

(gnome-terminal:21148): GnomeUI-WARNING **: While connecting to session manager:
Authentication Rejected, reason : None of the authentication protocols specified are supported and host-based authentication failed.
Window manager warning: last_user_time (3075683376) is greater than comparison timestamp (985470040).  This most likely represents a buggy client sending inaccurate timestamps in messages such as _NET
Window manager warning: 0x200001e (Terminal) appears to be one of the offending windows with a timestamp of 3075683376.  Working around...
Window manager warning: Invalid WM_TRANSIENT_FOR window 0x3e specified for 0x220009c (Error - Kl).
Window manager warning: Window 0x2c002d5 (AntiVirus ) sets an MWM hint indicating it isn't resizable, but sets min size 1 x 1 and max size 2147483647 x 2147483647; this doesn't make much sense.
Window manager warning: Window 0x22002d5 (AntiVirus ) sets an MWM hint indicating it isn't resizable, but sets min size 1 x 1 and max size 2147483647 x 2147483647; this doesn't make much sense.
--------------------------------------------------
Comment 1 Cosimo Cecchi 2008-02-21 09:36:34 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 406462 ***