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 542118 - crash in Open Folder: This is a re-submission ...
crash in Open Folder: This is a re-submission ...
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-07-08 22:09 UTC by superstubby13
Modified: 2008-07-08 22:11 UTC
See Also:
GNOME target: ---
GNOME version: 2.21/2.22



Description superstubby13 2008-07-08 22:09:41 UTC
Version: 2.20.0

What were you doing when the application crashed?
This is a re-submission of the same bug with debugging information available.

I was attempting to connect to a new (new in that I have not connected to this particular folder before) windows share on my campus network.  Accepts my password and user info, then crashes.

I have (easily) connected to multiple shares on the same network without any problems.


Distribution: Debian lenny/sid
Gnome Release: 2.22.2 2008-05-29 (Debian)
BugBuddy Version: 2.22.0

System: Linux 2.6.24-custom #1 SMP Sun Jul 6 14:54:58 EDT 2008 i686
X Vendor: The X.Org Foundation
X Vendor Release: 10402000
Selinux: No
Accessibility: Disabled
GTK+ Theme: Clearlooks
Icon Theme: black-white_2-Gloss

Memory status: size: 61018112 vsize: 61018112 resident: 25669632 share: 15233024 rss: 25669632 rss_rlim: 4294967295
CPU usage: start_time: 1215554728 rtime: 155 utime: 147 stime: 8 cutime:0 cstime: 0 timeout: 0 it_real_value: 0 frequency: 100

Backtrace was generated from '/usr/bin/nautilus'

Using host libthread_db library "/lib/libthread_db.so.1".
[Thread debugging using libthread_db enabled]
[New Thread 0xb6afa720 (LWP 3545)]
[New Thread 0xb58ddb90 (LWP 3604)]
0xb7297f91 in waitpid () from /lib/libpthread.so.0

Thread 1 (Thread 0xb6afa720 (LWP 3545))

  • #0 waitpid
    from /lib/libpthread.so.0
  • #1 g_spawn_sync
    from /usr/lib/libglib-2.0.so.0
  • #2 g_spawn_command_line_sync
    from /usr/lib/libglib-2.0.so.0
  • #3 ??
    from /usr/lib/gtk-2.0/modules/libgnomebreakpad.so
  • #4 <signal handler called>
  • #5 istr_hash
    at nautilus-directory-async.c line 170
  • #6 ??
    from /usr/lib/libglib-2.0.so.0
  • #7 ??
  • #0 waitpid
    from /lib/libpthread.so.0


----------- .xsession-errors (59 sec old) ---------------------
** (gnome-settings-daemon:3448): WARNING **: Failed to open file '/etc/gnome/config/General.ad': No such file or directory
Window manager warning: Failed to read saved session file /home/superstubby/.metacity/sessions/default0.ms: Failed to open file '/home/superstubby/.metacity/sessions/default0.ms': No such file or dire
seahorse nautilus module initialized
Initializing gnome-mount extension
(gnome-panel:3469): Gtk-WARNING **: gtk_widget_size_allocate(): attempt to allocate widget with width -21 and height 24
connection_message_func(): Callback
CALLBACK: fill-authentication!!!
connection_message_func(): Callback
CALLBACK: fill-authentication!!!
connection_message_func(): Callback
CALLBACK: full-authentication!!!
seahorse nautilus module initialized
Initializing gnome-mount extension
--------------------------------------------------
Comment 1 A. Walton 2008-07-08 22:11:03 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 ***