GNOME Bugzilla – Bug 134985
nautilus crashing upon browsing smb:/// share and escaping the password screen
Last modified: 2005-05-28 12:54:41 UTC
Distribution: Debian testing/unstable Package: nautilus Severity: normal Version: GNOME2.4.1 2.4.2 Gnome-Distributor: Debian Synopsis: nautilus crashing upon browsing smb:/// share and escaping the password screen Bugzilla-Product: nautilus Bugzilla-Component: general Bugzilla-Version: 2.4.2 BugBuddy-GnomeVersion: 2.0 (2.4.0.1) Description: Description of the crash: nautilus crashed while browsing a windows 2003 samba share, and refusing to enter a password (the password screen comes up a couple of times, it crashed after the third escape) Steps to reproduce the crash: 1. start nautilus 2. browse an smb:/// share on a win2k3 system 3. do not enter the password, hold escape instead Expected Results: should crash same as here How often does this happen? not entirely sure yet, incidental. Additional Information: none. Debugging Information: Backtrace was generated from '/usr/bin/nautilus' (no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...[New Thread 1083796992 (LWP 1986)] [New Thread 1087556528 (LWP 1997)] [New Thread 1083796992 (LWP 1986)] [New Thread 1087556528 (LWP 1997)] [New Thread 1083796992 (LWP 1986)] [New Thread 1087556528 (LWP 1997)] (no debugging symbols found)...[New Thread 1087294384 (LWP 1996)] (no debugging symbols found)...[New Thread 1087032240 (LWP 1995)] (no debugging symbols found)...[New Thread 1085991856 (LWP 1990)] (no debugging symbols found)...[New Thread 1085729712 (LWP 1989)] (no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...0x41188411 in __waitpid_nocancel () from /lib/tls/libpthread.so.0
+ Trace 44411
Thread 1 (Thread 1083796992 (LWP 1986))
------- Bug moved to this database by unknown@bugzilla.gnome.org 2004-02-20 13:30 ------- Unknown version 2.4.2 in product nautilus. Setting version to the default, "unspecified". The original reporter (yonie@tiscali.nl) of this bug does not have an account here. Reassigning to the exporter, unknown@bugzilla.gnome.org. Reassigning to the default owner of the component, nautilus-maint@bugzilla.gnome.org.
Thanks for the bug report. Does debian have debug packages yet for gnome? It would be really helpful if you could get a stacktrace with debugging symbols: http://bugzilla.gnome.org/getting-traces.cgi Also, what exactly do you mean when you say it happens "incidentally"? Is this a first time occurence? Is it reproduceable?
im sorry, but i couldnt find a debug package and id rather not compile things myself. the bug seems to occur every time when i try to reproduce it. i was not entirely correct when i first wrote down the steps to reproduce. the correct way to get this segfault is: 1. share a folder with a lot of files and folders on a win2003 machine. set folder to be only visible to some user account. 2. start nautilus --nodesktop (im running xfce) 3. go to smb:///workgroup 4. doubleclick on the win2003 server 5. enter your account's username and password. you will now see the shares. 6. doubleclick the share made in step one 7. it will ask for your userid and password again. also enter these here. 8. when youve entered the account data, you'll see the window cleaning up the shares (as if it is about to display the share's contents), but another password window will appear. Cancel this one by pressing Escape. 9. nautilus will now segfault. This happens every time i try it this way. Hope this helps.
This is likely fixed in gnome-vfs 2.5.x.
*** Bug 140945 has been marked as a duplicate of this bug. ***
changing to FIXED based on alexl's comment and based on my experience so far with gnome-2.6. reopen if it can be reproduced on gnome-2.6 or better.
*** Bug 141771 has been marked as a duplicate of this bug. ***
*** Bug 146063 has been marked as a duplicate of this bug. ***
*** Bug 164273 has been marked as a duplicate of this bug. ***
Both bug 146063 and bug 164273 were using gnome 2.6.x, so I'm reopening.
*** Bug 164683 has been marked as a duplicate of this bug. ***
*** Bug 166324 has been marked as a duplicate of this bug. ***
*** Bug 166346 has been marked as a duplicate of this bug. ***
*** Bug 167201 has been marked as a duplicate of this bug. ***
*** Bug 167398 has been marked as a duplicate of this bug. ***
*** Bug 167683 has been marked as a duplicate of this bug. ***
*** Bug 168363 has been marked as a duplicate of this bug. ***
*** Bug 170915 has been marked as a duplicate of this bug. ***
the bug has duplicate with nautilus 2.10, updating
This is a libgnomeui issue, reassigning.
Created attachment 39637 [details] [review] One way to fix it The current close event handler will simply destroy the widget. But later on GtkDialog tries to synthesize a close button event on the destroyed widget, sometimes crashing in the process. When the close event handler is removed, it'll destroy the dialog via the button_clicked callback when pressing escape (and handle it the same way as a click on cancel).
*** Bug 300066 has been marked as a duplicate of this bug. ***
*** Bug 170890 has been marked as a duplicate of this bug. ***
*** Bug 300562 has been marked as a duplicate of this bug. ***
*** Bug 301506 has been marked as a duplicate of this bug. ***
*** Bug 303252 has been marked as a duplicate of this bug. ***
Balamurali filed basically the same patch (before me) at bug 169917.
*** Bug 153301 has been marked as a duplicate of this bug. ***
*** Bug 169917 has been marked as a duplicate of this bug. ***
Commited to both branches. Thanks a lot.
*** Bug 159730 has been marked as a duplicate of this bug. ***
*** Bug 156291 has been marked as a duplicate of this bug. ***
*** Bug 305520 has been marked as a duplicate of this bug. ***