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 524959 - crash in File Browser:
crash in File Browser:
Status: RESOLVED DUPLICATE of bug 355018
Product: nautilus
Classification: Core
Component: general
2.20.x
Other All
: High critical
: ---
Assigned To: Nautilus Maintainers
Nautilus Maintainers
Depends on:
Blocks:
 
 
Reported: 2008-03-29 13:27 UTC by icegreen
Modified: 2008-03-29 17:51 UTC
See Also:
GNOME target: ---
GNOME version: 2.19/2.20


Description icegreen 2008-03-29 13:27:23 UTC 
Version: 2.20.0

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.22-3-k7 #1 SMP Sun Feb 10 21:04:14 UTC 2008 i686
X Vendor: The X.Org Foundation
X Vendor Release: 10400000
Selinux: No
Accessibility: Disabled
GTK+ Theme: Industrial
Icon Theme: Neu

Memory status: size: 123060224 vsize: 123060224 resident: 46440448 share: 17158144 rss: 46440448 rss_rlim: 4294967295
CPU usage: start_time: 1206784504 rtime: 4461 utime: 3306 stime: 1155 cutime:1345 cstime: 196 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 0xb6c4d6c0 (LWP 16352)]
(no debugging symbols found)
0xffffe410 in __kernel_vsyscall ()

+ Trace 193610

Thread 1 (Thread 0xb6c4d6c0 (LWP 16352))

  • #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 (143766 sec old) ---------------------
(amule:5969): GLib-WARNING **: poll(2) failed due to: Argumento inválido.
(amule:5969): GLib-WARNING **: poll(2) failed due to: Argumento inválido.
(amule:5969): GLib-WARNING **: poll(2) failed due to: Argumento inválido.
(amule:5969): GLib-WARNING **: poll(2) failed due to: Argumento inválido.
(amule:5969): GLib-WARNING **: poll(2) failed due to: Argumento inválido.
(amule:5969): GLib-WARNING **: poll(2) failed due to: Argumento inválido.
(amule:5969): GLib-WARN
...Too much output, ignoring rest...
--------------------------------------------------
Comment 1 Cosimo Cecchi 2008-03-29 17:51:50 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 355018 ***