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 538888 - crash in Home Folder: I tried to open a direct...
crash in Home Folder: I tried to open a direct...
Status: RESOLVED FIXED
Product: nautilus
Classification: Core
Component: general
2.20.x
Other All
: High critical
: ---
Assigned To: Nautilus Maintainers
Nautilus Maintainers
nautilus[EMC08]
Depends on:
Blocks:
 
 
Reported: 2008-06-18 04:48 UTC by bbfk
Modified: 2009-03-13 08:28 UTC
See Also:
GNOME target: ---
GNOME version: 2.21/2.22


Attachments
file that lets nautilus down (18 bytes, image/x-tga)
2008-06-20 05:18 UTC, bbfk
  Details
Don't display error message for NULL errors (1.22 KB, patch)
2008-11-17 16:45 UTC, palfrey
none Details | Review
Revised version of the patch, removing extra cruft (853 bytes, patch)
2008-11-17 16:48 UTC, palfrey
accepted-commit_after_freeze Details | Review

Description bbfk 2008-06-18 04:48:03 UTC
What were you doing when the application crashed?
I tried to open a directory. As administrator and logged in to the console I am able to open this directory. Being unable to open this relevant dir I had (with administrator rights) copied all files and subdirectory files into a new directory, changed user and group rights to my user ones and I am still not able to open the directory using nautilus. I am lost.

Further information is available.


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

System: Linux 2.6.25-2-686 #1 SMP Thu Jun 12 16:26:30 UTC 2008 i686
X Vendor: The X.Org Foundation
X Vendor Release: 10400090
Selinux: No
Accessibility: Disabled
GTK+ Theme: Crux
Icon Theme: gnome

Memory status: size: 65744896 vsize: 65744896 resident: 24465408 share: 16343040 rss: 24465408 rss_rlim: 4294967295
CPU usage: start_time: 1213763920 rtime: 440 utime: 406 stime: 34 cutime:8 cstime: 1 timeout: 0 it_real_value: 0 frequency: 100

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

(no debugging symbols found)
[Thread debugging using libthread_db enabled]
[New Thread 0xb6a26720 (LWP 5200)]
(no debugging symbols found)
0xb7f16424 in __kernel_vsyscall ()

Thread 1 (Thread 0xb6a26720 (LWP 5200))

  • #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 ??
  • #0 __kernel_vsyscall


----------- .xsession-errors ---------------------
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 Keine Berechtigun
You do not have permission to create a usershare. Ask your administrator to grant you permissions to create a share.
(nautilus:5200): GdkPixbuf-CRITICAL **: io_buffer_free_segment: assertion `buffer->data != NULL' failed
**** alsa_pcm: xrun of at least 1213763260776.448 msecs
--------------------------------------------------
Comment 1 Cosimo Cecchi 2008-06-18 12:20:13 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 bbfk 2008-06-19 20:52:53 UTC
I have encircled the bug: since I could copy and move the files using a terminal, I found two file whose presence induces the bug. these files have the ending of .tga. I do no longer know which structural modelling program rasmol etc saved these files. they have only 18 byte indicated by "ls -laF". if you point me to a hex editor I can copy the files here.

I can "cat" the files indicating that there is no harddisk error. I wonder for what reason nautilus refuses to work with and show these files.
Comment 3 A. Walton 2008-06-19 22:22:12 UTC
Looks as if we're crashing while attempting to thumbnail them, however, without a proper backtrace of the crash, there is not a whole lot we can do. If you can provide the files or a better trace, please do so. Thanks.
Comment 4 bbfk 2008-06-20 05:18:08 UTC
Created attachment 113092 [details]
file that lets nautilus down
Comment 5 bbfk 2008-06-20 05:18:57 UTC
I have added one of the two files.
Comment 6 Cosimo Cecchi 2008-06-23 11:13:39 UTC
I can't manage to open the file, it seems it is corrupted in some way.
Also here (Nautilus 2.23.4 on Ubuntu Ibex alpha) the file doesn't get thumbnailed anyway.
Do you have the chance to try reproducing the bug with Nautilus >= 2.22.x?
Comment 7 bbfk 2008-06-23 12:12:22 UTC
I am using latest debian unstable. the version of nautilus of today 2008-06-23 is 2.20.0. Sorry, I cannot provide more info. You have the file and it corrupts Nautilus: Isn't that a bug?

Cosimo, what about changing the tag to confirmed?
Comment 8 Cosimo Cecchi 2008-06-23 12:34:27 UTC
Until we have a valid stack trace or we can manage to reproduce the bug in some way, I can't confirm this is a Nautilus bug.
For instance, it could also be a bug in your thumbnailer for TGA files or in GTK+ TGA pixbuf loader or maybe even in some other component.
Comment 9 bbfk 2008-06-23 13:18:54 UTC
I installed nautilus-dbg and repeated the crash. Please see the new backtrace

Bernhard

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

System: Linux 2.6.25-2-686 #1 SMP Thu Jun 12 16:26:30 UTC 2008 i686
X Vendor: The X.Org Foundation
X Vendor Release: 10400090
Selinux: No
Accessibility: Disabled
GTK+ Theme: Crux
Icon Theme: gnome

Memory status: size: 93237248 vsize: 93237248 resident: 42323968 share: 16371712 rss: 42323968 rss_rlim: 4294967295
CPU usage: start_time: 1214117163 rtime: 5731 utime: 5264 stime: 467 cutime:483 cstime: 146 timeout: 0 it_real_value: 0 frequency: 100

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

[Thread debugging using libthread_db enabled]
[New Thread 0xb6a96720 (LWP 4378)]
0xb7f86424 in __kernel_vsyscall ()

Thread 1 (Thread 0xb6a96720 (LWP 4378))

  • #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 get_pixbuf_from_data
    at nautilus-thumbnails.c line 395
  • #7 nautilus_thumbnail_load_image
    at nautilus-thumbnails.c line 436
  • #8 create_normal_cache_icon
    at nautilus-icon-factory.c line 1288
  • #9 nautilus_icon_factory_get_pixbuf_for_icon
    at nautilus-icon-factory.c line 1479
  • #10 nautilus_icon_factory_get_pixbuf_for_file_with_icon
    at nautilus-icon-factory.c line 1730
  • #11 nautilus_icon_container_update_icon
    at nautilus-icon-container.c line 5819
  • #12 nautilus_icon_container_request_update
    at nautilus-icon-container.c line 6152
  • #13 fm_icon_view_file_changed
    at fm-icon-view.c line 607
  • #14 nautilus_marshal_VOID__OBJECT_OBJECT
    at nautilus-marshal-guts.c line 469
  • #15 ??
    from /usr/lib/libgobject-2.0.so.0
  • #16 ??
  • #17 ??
  • #0 __kernel_vsyscall


----------- .xsession-errors (3577 sec old) ---------------------
**** alsa_pcm: xrun of at least 1214116790272.000 msecs
**** alsa_pcm: xrun of at least 1214116790272.000 msecs
**** alsa_pcm: xrun of at least 1214116790272.000 msecs
...Too much output, ignoring rest...
--------------------------------------------------
Comment 10 palfrey 2008-11-17 16:45:50 UTC
Created attachment 122861 [details] [review]
Don't display error message for NULL errors

Looks like there's even more issues with gdk_pixbuf_loader_close than just the one worked around in bug 403255. In this case, it looks like gdk_pixbuf_loader_close has returned false, but error hasn't been set... This is probably an issue with the TGA loader doing stupid crap, but this patch stops nautilus from crapping out when that happens. I'm guessing this has been sorted out by the time of whatever version of GTK is present on Ubuntu Ibex alpha, but probably a bright idea to catch this anyway.

Alternately, if anyone feels like tracking down the broken GTK revisions, it might be worth bumping Nautilus' dependency to get to a less broken revision and let us clean up all these workarounds!
Comment 11 palfrey 2008-11-17 16:48:44 UTC
Created attachment 122864 [details] [review]
Revised version of the patch, removing extra cruft

Had random other fix in the earlier patch, submitting cleaner version.
Comment 12 Alexander Larsson 2009-03-11 13:07:28 UTC
patch looks good, lets get it in after the freeze
Comment 13 André Klapper 2009-03-11 13:24:37 UTC
I think a trivial crash fix is worth asking for freeze break...
This woiuld be r-t approval 1 of 2.
Comment 14 Alexander Larsson 2009-03-12 12:27:57 UTC
commited.
Comment 15 Christian Persch 2009-03-12 15:31:34 UTC
Is there a bug filed against gdk-pixbuf for this gdk-pixbuf loader failure?
Comment 16 Alexander Larsson 2009-03-13 08:28:57 UTC
I opened bug 575217