Bug 528403 – crash in Computer:

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 528403 - crash in Computer:


Summary:	crash in Computer:


Status:	RESOLVED DUPLICATE of bug 522534

Product:	nautilus
Classification:	Core
Component:	general
Version:	2.20.x
Hardware:	Other All

Importance:	High critical
Target Milestone:	---
Assigned To:	Nautilus Maintainers
QA Contact:	Nautilus Maintainers

URL:
Whiteboard:

Depends on:
Blocks:

Reported:	2008-04-16 13:16 UTC by François Guerraz
Modified:	2008-04-16 18:10 UTC

See Also:
GNOME target:	---
GNOME version:	2.21/2.22

Description François Guerraz 2008-04-16 13:16:54 UTC

Version: 2.20.0

What were you doing when the application crashed?



Distribution: Debian lenny/sid
Gnome Release: 2.22.0 2008-03-14 (Debian)
BugBuddy Version: 2.22.0

System: Linux 2.6.24.4 #11 SMP Fri Mar 28 10:04:10 CET 2008 i686
X Vendor: The X.Org Foundation
X Vendor Release: 10300000
Selinux: No
Accessibility: Disabled
GTK+ Theme: Lush
Icon Theme: Lush

Memory status: size: 95019008 vsize: 95019008 resident: 37048320 share: 18272256 rss: 37048320 rss_rlim: 4294967295
CPU usage: start_time: 1208351659 rtime: 183 utime: 174 stime: 9 cutime:2 cstime: 0 timeout: 0 it_real_value: 0 frequency: 100

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

Using host libthread_db library "/lib/i686/cmov/libthread_db.so.1".
[Thread debugging using libthread_db enabled]
[New Thread 0xb6bdd720 (LWP 15040)]
0xb7f7f410 in __kernel_vsyscall ()

+ Trace 195377

Thread 1 (Thread 0xb6bdd720 (LWP 15040))

#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 istr_hash
at nautilus-directory-async.c line 170
#7 ??
from /usr/lib/libglib-2.0.so.0
#8 ??
#0 __kernel_vsyscall



----------- .xsession-errors (25 sec old) ---------------------
Initializing gnome-mount extension
seahorse nautilus module initialized
Nautilus-Share-Message: REFRESHING SHARES
Nautilus-Share-Message: ------------------------------------------
Nautilus-Share-Message: spawn arg "net"
Nautilus-Share-Message: spawn arg "usershare"
Nautilus-Share-Message: spawn arg "info"
Nautilus-Share-Message: end of spawn args; SPAWNING
Nautilus-Share-Message: returned from spawn: SUCCESS: 
Nautilus-Share-Message: exit code 255
Nautilus-Share-Message: ------------------------------------------
Nautilus-Share-Message: Called "net usershare info" but it failed: 'net usershare' returned error 255: net usershare: cannot open usershare directory /var/lib/samba/usershares. Error Permission non ac
You do not have permission to create a usershare. Ask your administrator to grant you permissions to create a share.
--------------------------------------------------

Comment 1 François Guerraz 2008-04-16 13:21:22 UTC

Hello,

Sorry for the lack of comment in the report in itself.

What I was doing :

Trying to open a network share on a windows station.
Nautilus freeze before any icon is displayed.


Reproductible : yes, every time.

Comment 2 Cosimo Cecchi 2008-04-16 18:10:05 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 522534 ***