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 505400 - crash in File Browser: When I see the propertie...
crash in File Browser: When I see the propertie...
Status: RESOLVED DUPLICATE of bug 485526
Product: nautilus
Classification: Core
Component: general
2.18.x
Other All
: High critical
: ---
Assigned To: Nautilus Maintainers
Nautilus Maintainers
Depends on:
Blocks:
 
 
Reported: 2007-12-24 11:21 UTC by rastandy
Modified: 2007-12-24 14:23 UTC
See Also:
GNOME target: ---
GNOME version: 2.19/2.20



Description rastandy 2007-12-24 11:21:27 UTC
Version: 2.18.3

What were you doing when the application crashed?
When I see the properties of a folder through the right-click menu, nautilus crashes.


Distribution: Debian lenny/sid
Gnome Release: 2.20.2 2007-11-29 (Debian)
BugBuddy Version: 2.20.1

System: Linux 2.6.23-1-686 #1 SMP Fri Dec 21 13:57:07 UTC 2007 i686
X Vendor: The X.Org Foundation
X Vendor Release: 10300000
Selinux: No
Accessibility: Disabled
GTK+ Theme: Glossy P
Icon Theme: gartoon

Memory status: size: 77803520 vsize: 77803520 resident: 22056960 share: 13524992 rss: 22056960 rss_rlim: 4294967295
CPU usage: start_time: 1198343966 rtime: 7709 utime: 6817 stime: 892 cutime:196 cstime: 42 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 0xb6d456b0 (LWP 4534)]
(no debugging symbols found)
0xffffe410 in __kernel_vsyscall ()

Thread 1 (Thread 0xb6d456b0 (LWP 4534))

  • #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 strcmp
    from /lib/i686/cmov/libc.so.6
  • #7 ??
  • #8 ??
  • #0 __kernel_vsyscall


----------- .xsession-errors (75397 sec old) ---------------------
TIMING   WARNING: Calling <function <lambda> at 0xa64c994> on HTTPClient: http://img.youtube.com/vi/BhrZ57XxYJU/default.jpg too slow (2.350 secs)
TIMING   WARNING: Calling <function <lambda> at 0x9093ca4> on HTTPClient: http://img.youtube.com/vi/9lmvztCsBfk/default.jpg too slow (2.687 secs)
TIMING   WARNING: Calling <function <lambda> at 0xa64c064> on HTTPClient: http://img.youtube.com/vi/H1su15BsJzc/default.jpg too slow (1.414 secs)
INFO     moving to movies directory filename is /home/andy/Movies/Incomplete Downloads/get_video-video_id=-ZLQ0p5s_lw.flv.part
TIMING   WARNING: Calling <function <lambda> at 0x90a65a4> on HTTPClient: http://img.youtube.com/vi/VIhTmmG75cQ/default.jpg too slow (1.115 secs)
TIMING   WARNING: Calling <function <lambda> at 0xa64cbc4> on HTTPClient: http://img.youtube.com/vi/isbUuSznUhg/default.jpg too slow (1.154 secs)
TIMING   WARNING: Calling <function <lambda> at 0x90a65a4> on HTTPClient: http://img.youtube.com/vi/I-vuvOvQqag/default.jpg too slow (1.344 secs)
INFO     failed() called; generating crash report.
INFO     ----- CRASH REPORT (DANGER CAN HAPPEN) -----
INFO     App:        Miro
Publisher:  Participatory Culture Foundation
Platform:   gtk-x11
Python:     2.4.4 (#2, Aug 16 2007, 02:03:40)  [GCC 4.1.3 20070812 (prerelease) (Debian 4.1.2-15)]
Py Path:    ['/var/lib/python-support/python2.4/miro', '/usr/bin', '/usr/lib/python24.zip', '/usr/lib/python2.4', '/usr/lib/python2.4/plat-linux2', '/usr/lib/python2.4/lib-tk', '/usr/lib/python2.4/lib
...Too much output, ignoring rest...
--------------------------------------------------
Comment 1 Cosimo Cecchi 2007-12-24 14:23:58 UTC
Thanks for the bug report. This particular bug has already been reported into our bug tracking system, but please feel free to report any further bugs you find.


*** This bug has been marked as a duplicate of 485526 ***