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 543776 - crash in Home Folder:
crash in Home Folder:
Status: RESOLVED DUPLICATE of bug 522534
Product: nautilus
Classification: Core
Component: general
unspecified
Other All
: High critical
: ---
Assigned To: Nautilus Maintainers
Nautilus Maintainers
Depends on:
Blocks:
 
 
Reported: 2008-07-19 20:59 UTC by martin.ringwelski
Modified: 2008-07-20 14:51 UTC
See Also:
GNOME target: ---
GNOME version: 2.19/2.20



Description martin.ringwelski 2008-07-19 20:59:12 UTC
What were you doing when the application crashed?



Distribution: Debian lenny/sid
Gnome Release: 2.20.3 2008-01-12 (Debian)
BugBuddy Version: 2.20.1

System: Linux 2.6.25-2-686 #1 SMP Fri Jun 27 03:23:20 UTC 2008 i686
X Vendor: The X.Org Foundation
X Vendor Release: 10400090
Selinux: No
Accessibility: Disabled
GTK+ Theme: Glossy P
Icon Theme: dlg-neu

Memory status: size: 62599168 vsize: 62599168 resident: 28839936 share: 15998976 rss: 28839936 rss_rlim: 4294967295
CPU usage: start_time: 1216501116 rtime: 358 utime: 339 stime: 19 cutime:4 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 0xb6a98720 (LWP 4336)]
(no debugging symbols found)
0xb7ee6424 in __kernel_vsyscall ()

Thread 1 (Thread 0xb6a98720 (LWP 4336))

  • #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 ---------------------
(nautilus:4336): libgnomevfs-WARNING **: Failed to create service browser: Bad state
(nautilus:4336): libgnomevfs-WARNING **: Failed to create service browser: Bad state
(nautilus:4336): libgnomevfs-WARNING **: Failed to create service browser: Bad state
(nautilus:4336): gnome-vfs-modules-WARNING **: Failed to create client: Daemon not running
** (nautilus:4336): WARNING **: Keine Beschreibung für MIME-Type »x-directory/smb-share« gefunden (Datei ist »home«), teilen Sie dies der gnome-vfs-Mailingliste mit.
--------------------------------------------------
Comment 1 Susana 2008-07-20 10:25:26 UTC
Thanks for taking the time to report this bug.
Unfortunately, the 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.

Could you please help fixing this by installing some debugging packages [1],
start the application as normal, and try to reproduce the crash, if possible?

Once bug-buddy pops up, you can find the stacktrace in the 'Details', now
containing way more information. Please copy that stacktrace and paste it as a
comment here. Thanks in advance!

[1] Please install debug packages for nautilus, glib2, gtk2, pango, gnome-vfs2,
libgnome, and libgnomeui.

More details can be found here: http://live.gnome.org/GettingTraces
Comment 2 martin.ringwelski 2008-07-20 13:58:45 UTC
Ok, I only found the nautilus-dbg package. pango and gnome-vfs2 are not even installed.
The error occured when I tried to get access to an smb share. I can enter the computer and the folde which is shared and even the subfolder, but when I enter the next subfolder nautilus crashes.
The error occured again, I hope this helps you:

Distribution: Debian lenny/sid
Gnome Release: 2.20.3 2008-01-12 (Debian)
BugBuddy Version: 2.20.1

System: Linux 2.6.25-2-686 #1 SMP Fri Jun 27 03:23:20 UTC 2008 i686
X Vendor: The X.Org Foundation
X Vendor Release: 10400090
Selinux: No
Accessibility: Disabled
GTK+ Theme: Glossy P
Icon Theme: dlg-neu

Memory status: size: 58671104 vsize: 58671104 resident: 24817664 share: 16007168 rss: 24817664 rss_rlim: 4294967295
CPU usage: start_time: 1216561522 rtime: 397 utime: 378 stime: 19 cutime:3 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 0xb6ab4720 (LWP 7416)]
[New Thread 0xb610cb90 (LWP 7535)]
0xb7f02424 in __kernel_vsyscall ()

Thread 1 (Thread 0xb6ab4720 (LWP 7416))

  • #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 (313 sec old) ---------------------
** (gnome-video-thumbnailer:7255): WARNING **: Could not take screenshot: no video info
totem-video-thumbnailer couldn't get a picture from 'file:///home/martin/musik/ska-p/08%20-%20Bla%2C%20Bla%2C%20Bla.ogg'
** (gnome-video-thumbnailer:7261): WARNING **: Could not take screenshot: no video info
** (gnome-video-thumbnailer:7261): WARNING **: Could not take screenshot: no video info
** (gnome-video-thumbnailer:7261): WARNING **: Could not take screenshot: no video info
** (gnome-video-thumbnailer:7261): WARNING **: Could not take screenshot: no video info
** (gnome-video-thumbnailer:7261): WARNING **: Could not take screenshot: no video info
...Too much output, ignoring rest...
--------------------------------------------------
Comment 3 Susana 2008-07-20 14:51:12 UTC
Hi Martin,

Thanks for the feedback. This is a duplicate.

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 ***