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 549301 - crash in Open Folder:
crash in Open Folder:
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-08-25 13:39 UTC by thomas.wright
Modified: 2008-08-26 10:04 UTC
See Also:
GNOME target: ---
GNOME version: 2.21/2.22



Description thomas.wright 2008-08-25 13:39:45 UTC
Version: 2.20.0

What were you doing when the application crashed?



Distribution: Debian lenny/sid
Gnome Release: 2.22.3 2008-06-30 (Debian)
BugBuddy Version: 2.20.1

System: Linux 2.6.17.7 #2 Mon Jul 31 10:57:24 EDT 2006 x86_64
X Vendor: The X.Org Foundation
X Vendor Release: 10402000
Selinux: No
Accessibility: Disabled
GTK+ Theme: SphereCrystal
Icon Theme: SphereCrystal

Memory status: size: 372928512 vsize: 372928512 resident: 43810816 share: 17612800 rss: 43810816 rss_rlim: 18446744073709551615
CPU usage: start_time: 1219503395 rtime: 949 utime: 894 stime: 55 cutime:5 cstime: 3 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/libthread_db.so.1".
(no debugging symbols found)
[Thread debugging using libthread_db enabled]
[New Thread 0x2ae37be92c20 (LWP 2300)]
0x00002ae375665edf in waitpid () from /lib/libpthread.so.0

Thread 1 (Thread 0x2ae37be92c20 (LWP 2300))

  • #0 waitpid
    from /lib/libpthread.so.0
  • #1 g_spawn_sync
    from /usr/lib/libglib-2.0.so.0
  • #2 g_spawn_command_line_sync
    from /usr/lib/libglib-2.0.so.0
  • #3 ??
    from /usr/lib/gtk-2.0/modules/libgnomebreakpad.so
  • #4 <signal handler called>
  • #5 ??
  • #6 ??
    from /usr/lib/libglib-2.0.so.0
  • #7 ??
  • #8 ??
  • #9 ??
    from /usr/lib/libgnomevfs-2.so.0
  • #10 g_main_context_dispatch
    from /usr/lib/libglib-2.0.so.0
  • #11 ??
    from /usr/lib/libglib-2.0.so.0
  • #12 g_main_loop_run
    from /usr/lib/libglib-2.0.so.0
  • #13 gtk_main
    from /usr/lib/libgtk-x11-2.0.so.0
  • #14 ??
  • #15 __libc_start_main
    from /lib/libc.so.6
  • #16 ??
  • #17 ??
  • #18 ??
  • #0 waitpid
    from /lib/libpthread.so.0


----------- .xsession-errors (15 sec old) ---------------------
CALLBACK: fill-authentication!!!
connection_message_func(): Callback
CALLBACK: full-authentication!!!
** Message: Failed to write /home/tom/dora3.pcx to thumbnail pixbuf loader: Image has invalid width and/or height
** Message: Failed to write /home/tom/dora3.pcx to thumbnail pixbuf loader: Image has invalid width and/or height
** Message: Failed to write /home/tom/dora3.pcx to thumbnail pixbuf loader: Image has invalid width and/or height
** Message: Failed to write /home/tom/dora3.pcx to thumbnail pixbuf loader: Image has invalid width and/or height
** Message: Failed to write /home/tom/dora3.pcx to thumbnail pixbuf loader: Image has invalid width and/or height
** Message: Failed to write /home/tom/dora3.pcx to thumbnail pixbuf loader: Image has invalid width and/or height
** Message: Failed to write /home/tom/dora3.pcx to thumbnail pixbuf loader: Image has invalid width and/or height
** Message: Failed to write /home/tom/dora3.pcx to thumbnail pixbuf loader: Image has invalid width and/or height
** Message: Failed to write /home/tom/dora3.pcx to thumbnail pixbuf loader: Image has invalid width and/or height
** Message: Failed to write /home/tom/dora3.pcx to thumbnail pixbuf loader: Image has invalid width and/or height
** Message: Failed to write /home/tom/dora3.pcx to thumbnail pixbuf loader: Image has invalid width and/or height
** Message: Failed to write /home/tom/dora3.pcx to thumbnail pixbuf loader: Image has invalid width and/or height
--------------------------------------------------
Comment 1 Cosimo Cecchi 2008-08-26 10:04:51 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 ***