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 535322 - crash in Open Folder: Opening a windows share ...
crash in Open Folder: Opening a windows share ...
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-05-28 18:46 UTC by turbohawk80
Modified: 2008-05-28 22:50 UTC
See Also:
GNOME target: ---
GNOME version: 2.21/2.22


Description turbohawk80 2008-05-28 18:46:26 UTC 
Version: 2.20.0

What were you doing when the application crashed?
Opening a windows share on the network


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 Sat Apr 19 00:37:55 UTC 2008 i686
X Vendor: The X.Org Foundation
X Vendor Release: 10400090
Selinux: No
Accessibility: Disabled
GTK+ Theme: SphereCrystal
Icon Theme: SphereCrystal

Memory status: size: 103038976 vsize: 103038976 resident: 39215104 share: 16547840 rss: 39215104 rss_rlim: 4294967295
CPU usage: start_time: 1211921999 rtime: 13678 utime: 12868 stime: 810 cutime:3 cstime: 19 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 0xb6b44720 (LWP 12964)]
[New Thread 0xb5f0fb90 (LWP 26864)]
(no debugging symbols found)
0xffffe410 in __kernel_vsyscall ()

+ Trace 198889

Thread 1 (Thread 0xb6b44720 (LWP 12964))

  • #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 ??
  • #0 __kernel_vsyscall 


----------- .xsession-errors (9 sec old) ---------------------
QLayout "unnamed" added to CHexToolWidget "unnamed", which already has a layout
QLayout "unnamed" added to CHexToolWidget "unnamed", which already has a layout
(nautilus:12964): Gtk-CRITICAL **: gtk_window_realize_icon: assertion `info->icon_pixmap == NULL' failed
QLayout "unnamed" added to CHexToolWidget "unnamed", which already has a layout
QLayout "unnamed" added to CHexToolWidget "unnamed", which already has a layout
kbuildsycoca running...
Reusing existing ksycoca
Window manager warning: Received a _NET_WM_MOVERESIZE message for 0x100b123 (Predator_O); these messages lack timestamps and therefore suck.
connection_message_func(): Callback
CALLBACK: fill-authentication!!!
connection_message_func(): Callback
CALLBACK: fill-authentication!!!
** (nautilus:12964): WARNING **: No description found for mime type "x-directory/smb-share" (file is "bin"), please tell the gnome-vfs mailing list.
--------------------------------------------------
Comment 1 Cosimo Cecchi 2008-05-28 22:50:56 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 ***