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 536221 - crash in Open Folder: entering shared disk
crash in Open Folder: entering shared disk
Status: RESOLVED DUPLICATE of bug 522534
Product: nautilus
Classification: Core
Component: general
2.20.x
Other All
: High critical
: ---
Assigned To: Nautilus Maintainers
Nautilus Maintainers
Depends on:
Blocks:
 
 
Reported: 2008-06-02 12:13 UTC by markpoks
Modified: 2008-06-02 12:52 UTC
See Also:
GNOME target: ---
GNOME version: 2.21/2.22



Description markpoks 2008-06-02 12:13:38 UTC
Version: 2.20.0

What were you doing when the application crashed?
entering shared disk


Distribution: Debian lenny/sid
Gnome Release: 2.22.1 2008-04-08 (Debian)
BugBuddy Version: 2.22.0

System: Linux 2.6.24-1-686 #1 SMP Thu May 8 02:16:39 UTC 2008 i686
X Vendor: The X.Org Foundation
X Vendor Release: 10400090
Selinux: No
Accessibility: Disabled
GTK+ Theme: Glossy
Icon Theme: Gorilla

Memory status: size: 78061568 vsize: 78061568 resident: 23203840 share: 15695872 rss: 23203840 rss_rlim: 4294967295
CPU usage: start_time: 1212394091 rtime: 334 utime: 301 stime: 33 cutime:0 cstime: 0 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 0xb6b4b720 (LWP 3513)]
(no debugging symbols found)
0xffffe410 in __kernel_vsyscall ()

Thread 1 (Thread 0xb6b4b720 (LWP 3513))

  • #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 ??
  • #7 ??
  • #8 ??
  • #9 ??
  • #10 ??
    from /usr/lib/libglib-2.0.so.0
  • #11 ??
  • #12 ??
  • #13 ??
  • #14 ??
    from /usr/lib/libglib-2.0.so.0
  • #15 ??
  • #0 __kernel_vsyscall


----------- .xsession-errors ---------------------
(flamerobin:6627): Gtk-CRITICAL **: gtk_container_remove: assertion `GTK_IS_TOOLBAR (container) || widget->parent == GTK_WIDGET (container)' failed
(flamerobin:6627): Gtk-CRITICAL **: gtk_container_remove: assertion `GTK_IS_TOOLBAR (container) || widget->parent == GTK_WIDGET (container)' failed
CalDAV Eplugin starting up ...
** (evolution:7207): DEBUG: mailto URL command: evolution %s
** (evolution:7207): DEBUG: mailto URL program: evolution
Window manager warning: Invalid WM_TRANSIENT_FOR window 0x3e00007 specified for 0x3e00011 ( ).
Window manager warning: Invalid WM_TRANSIENT_FOR window 0x3e00007 specified for 0x3e00011 ( ).
Window manager warning: Invalid WM_TRANSIENT_FOR window 0x3e00007 specified for 0x3e00011 ( ).
Window manager warning: Window 0x3e00020 (Documaster) sets an MWM hint indicating it isn't resizable, but sets min size 92 x 72 and max size 2147483647 x 2147483647; this doesn't make much sense.
Window manager warning: Window 0x3e00020 (Documaster) sets an MWM hint indicating it isn't resizable, but sets min size 92 x 72 and max size 2147483647 x 2147483647; this doesn't make much sense.
Window manager warning: Window 0x3e00020 (Documaster) sets an MWM hint indicating it isn't resizable, but sets min size 792 x 572 and max size 2147483647 x 2147483647; this doesn't make much sense.
connection_message_func(): Callback
CALLBACK: fill-authentication!!!
--------------------------------------------------
Comment 1 Cosimo Cecchi 2008-06-02 12:52:47 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 522534 ***