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 507120 - crash in Open Folder: changing from view as ic...
crash in Open Folder: changing from view as ic...
Status: RESOLVED DUPLICATE of bug 474388
Product: nautilus
Classification: Core
Component: general
2.18.x
Other All
: High critical
: ---
Assigned To: Nautilus Maintainers
Nautilus Maintainers
Depends on:
Blocks:
 
 
Reported: 2008-01-03 21:42 UTC by kieran.murray
Modified: 2008-04-18 18:08 UTC
See Also:
GNOME target: ---
GNOME version: 2.17/2.18


Description kieran.murray 2008-01-03 21:42:00 UTC 
Version: 2.18.3

What were you doing when the application crashed?
changing from view as icons to view as list - also highlight a file which is downloading


Distribution: Fedora release 7 (Moonshine)
Gnome Release: 2.18.3 2007-11-13 (Red Hat, Inc)
BugBuddy Version: 2.18.0

System: Linux 2.6.23.8-34.fc7 #1 SMP Thu Nov 22 20:39:56 EST 2007 x86_64
X Vendor: The X.Org Foundation
X Vendor Release: 10300000
Selinux: Permissive
Accessibility: Disabled
GTK+ Theme: Clearlooks
Icon Theme: Fedora

Memory status: size: 610922496 vsize: 610922496 resident: 52170752 share: 24985600 rss: 52170752 rss_rlim: 18446744073709551615
CPU usage: start_time: 1199388319 rtime: 17940 utime: 15705 stime: 2235 cutime:9963 cstime: 3526 timeout: 0 it_real_value: 0 frequency: 100

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

(no debugging symbols found)
Using host libthread_db library "/lib64/libthread_db.so.1".
(no debugging symbols found)
[Thread debugging using libthread_db enabled]
[New Thread 46912496430624 (LWP 18008)]
(no debugging symbols found)
0x00000030c6e0d97f in waitpid () from /lib64/libpthread.so.0

+ Trace 183973

Thread 1 (Thread 46912496430624 (LWP 18008))

  • #0 waitpid
    from /lib64/libpthread.so.0
  • #1 g_cclosure_marshal_VOID__ENUM
    from /usr/lib64/libgnomeui-2.so.0
  • #2 <signal handler called>
  • #3 gnome_vfs_uri_unref
    from /usr/lib64/libgnomevfs-2.so.0
  • #4 g_cclosure_marshal_VOID__ENUM
    from /usr/lib64/libgnomevfs-2.so.0
  • #5 g_cclosure_marshal_VOID__ENUM
    from /usr/lib64/libgnomevfs-2.so.0
  • #6 g_cclosure_marshal_VOID__ENUM
    from /usr/lib64/libgnomevfs-2.so.0
  • #7 g_main_context_dispatch
    from /lib64/libglib-2.0.so.0
  • #8 g_cclosure_marshal_VOID__ENUM
    from /lib64/libglib-2.0.so.0
  • #9 g_main_loop_run
    from /lib64/libglib-2.0.so.0
  • #10 gtk_main
    from /usr/lib64/libgtk-x11-2.0.so.0
  • #11 main
  • #0 waitpid
    from /lib64/libpthread.so.0 


----------- .xsession-errors (5439 sec old) ---------------------
** Message: don't know how to handle video/x-xvid, framerate=(fraction)25/1, width=(int)320, height=(int)240
totem-video-thumbnailer: 'file:///tmp/mplayXBXJSS' isn't thumbnailable
Reason: Media contains no supported video streams.
** Message: don't know how to handle video/x-xvid, framerate=(fraction)25/1, width=(int)320, height=(int)240
totem-video-thumbnailer: 'file:///tmp/mplayXBXJSS' isn't thumbnailable
Reason: Media contains no supported video streams.
** Message: don't know how to handle video/x-xvid, framerate=(fraction)25/1, width=(int)320, height=(int)240
totem-video-thumbnailer: 'file:///tmp/mplayXBXJSS' isn't thumbnailable
Reason: Media contains no supported video streams.
** Message: don't know how to handle video/x-xvid, framerate=(fraction)25/1, width=(int)320, height=(int)240
totem-video-thumbnailer: 'file:///tmp/mplayXBXJSS' isn't thumbnailable
Reason: Media contains no supported video streams.
** Message: don't know how to handle video/x-xvid, framerate=(fraction)25/1, width=(int)320, height=(int)240
...Too much output, ignoring rest...
--------------------------------------------------
Comment 1 Cosimo Cecchi 2008-01-03 23:27:59 UTC 
Thanks for taking the time to report this bug.
This particular bug has already been reported into our bug tracking system, but the maintainers need more information to fix the bug. Could you please answer the questions in the other report in order to help the developers?


*** This bug has been marked as a duplicate of 474388 ***
Comment 2 Cosimo Cecchi 2008-04-18 18:08:00 UTC 
*** Bug 527564 has been marked as a duplicate of this bug. ***