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 537271 - crash in Open Folder: each time I try to acces...
crash in Open Folder: each time I try to acces...
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-08 15:42 UTC by Denis Stenderchuck
Modified: 2008-06-19 22:23 UTC
See Also:
GNOME target: ---
GNOME version: 2.21/2.22


Attachments
error info (11.51 KB, text/plain)
2008-06-19 21:01 UTC, Denis Stenderchuck
Details

Description Denis Stenderchuck 2008-06-08 15:42:47 UTC
Version: 2.20.0

What were you doing when the application crashed?
each time I try to access shared folder on WinXP SP3 machine it gave me this error.


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

System: Linux 2.6.24.3 #2 PREEMPT Sun Mar 16 00:17:05 EET 2008 i686
X Vendor: The X.Org Foundation
X Vendor Release: 10400090
Selinux: No
Accessibility: Disabled
GTK+ Theme: Glossy
Icon Theme: Wasp

Memory status: size: 82542592 vsize: 82542592 resident: 21622784 share: 15138816 rss: 21622784 rss_rlim: 4294967295
CPU usage: start_time: 1212939655 rtime: 201 utime: 185 stime: 16 cutime:2 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 0xb6bc2720 (LWP 7718)]
(no debugging symbols found)
0xb7f7b410 in __kernel_vsyscall ()

Thread 1 (Thread 0xb6bc2720 (LWP 7718))

  • #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 (57 sec old) ---------------------
Initializing gnome-mount extension
Initializing nautilus-share extension
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 denied
You do not have permission to create a usershare. Ask your administrator to grant you permissions to create a share.
--------------------------------------------------
Comment 1 Cosimo Cecchi 2008-06-08 17:52:19 UTC
Thanks for taking the time to report this bug.
Unfortunately, that stack trace is missing some elements that will help a lot to solve the problem, so it will be hard for the developers to fix that crash. Can you get us a stack trace with debugging symbols? Please see http://live.gnome.org/GettingTraces for more information on how to do so and reopen this bug or report a new one. Thanks in advance!
Comment 2 Denis Stenderchuck 2008-06-19 21:01:47 UTC
Created attachment 113072 [details]
error info
Comment 3 Denis Stenderchuck 2008-06-19 21:03:19 UTC
Comment on attachment 113072 [details]
error info

Sorry for delay, here is requested info.
Comment 4 A. Walton 2008-06-19 22:23:14 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 ***