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 533748 - crash in Open Folder: accessing windows share(...
crash in Open Folder: accessing 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-18 20:34 UTC by totonebadass
Modified: 2008-05-19 09:30 UTC
See Also:
GNOME target: ---
GNOME version: 2.21/2.22



Description totonebadass 2008-05-18 20:34:57 UTC
Version: 2.20.0

What were you doing when the application crashed?
accessing windows share(smb) from local 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: Clearlooks
Icon Theme: gnome

Memory status: size: 98881536 vsize: 98881536 resident: 43929600 share: 17227776 rss: 43929600 rss_rlim: 4294967295
CPU usage: start_time: 1211123689 rtime: 17947 utime: 5632 stime: 12315 cutime:2923 cstime: 410 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 0xb6b62720 (LWP 3849)]
[New Thread 0xb4720b90 (LWP 6565)]
(no debugging symbols found)
0xffffe410 in __kernel_vsyscall ()

Thread 1 (Thread 0xb6b62720 (LWP 3849))

  • #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 ??
  • #8 ??
  • #9 ??
  • #10 ??
    from /usr/lib/libglib-2.0.so.0
  • #11 ??
  • #12 ??
  • #13 ??
  • #14 ??
    from /usr/lib/libglib-2.0.so.0
  • #15 ??
  • #0 __kernel_vsyscall


----------- .xsession-errors (11901 sec old) ---------------------
Reading tag for /media/extern_ext3/Muzica/bz/music/The Offspring/The Offspring/Offspring - TEHRAN.mp3
Reading tag for /media/extern_ext3/Muzica/bz/music/The Offspring/The Offspring/Offspring - A THOUSAND DAYS.mp3
Reading tag for /media/extern_ext3/Muzica/bz/music/The Offspring/Ignition/The Offspring - 26.mp3
Reading tag for /media/extern_ext3/Muzica/bz/music/The Offspring/Ignition/The Offspring -  We Are One.mp3
Reading tag for /media/extern_ext3/Muzica/bz/music/The Offspring/Ignition/The Offspring -  L.A.P.D..mp3
Reading tag for /media/extern_ext3/Muzica/bz/music/The Offspring/Ignition/The Offspring -  Get It Right .mp3
Reading tag for /media/extern_ext3/Muzica/bz/music/The Offspring/Ignition/The Offspring - Session.mp3
Reading tag for /media/extern_ext3/Muzica/bz/music/The Offspring/Ignition/The Offspring -  Take It Like A Man.mp3
Reading tag for /media/extern_ext3/Muzica/bz/music/The Offspring/Ignition/The Offspring -  Kick Him When He's Down.mp3
Reading tag for /media/extern_ext3/Muzica/bz/music/The Offspring/Ignition/The Offspring -  Forever And A  Day.mp3
Reading tag for /media/extern_ext3/Muzica/bz/music/The Offspring/Ignition/The Offspring -  Hypodermic.mp3
Reading tag for /media/extern_ext3/Muzica/bz/music/The Offspring/Ignition/The Offspring - Nothing From Something.mp3
Reading tag for /media/extern_ext3/Muzica/bz/music/The Offspring/Ignition/The Offspring -  No Hero.mp3
...Too much output, ignoring rest...
--------------------------------------------------
Comment 1 Cosimo Cecchi 2008-05-19 09:30:07 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 ***