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 507569 - crash in File Browser: There was no problem, do...
crash in File Browser: There was no problem, do...
Status: RESOLVED DUPLICATE of bug 355018
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-06 00:08 UTC by paulagracia2002
Modified: 2008-01-07 13:30 UTC
See Also:
GNOME target: ---
GNOME version: 2.19/2.20


Description paulagracia2002 2008-01-06 00:08:02 UTC 
Version: 2.18.3

What were you doing when the application crashed?
There was no problem, don't worrie, We had electrycal problems in my house.



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

System: Linux 2.6.22-3-686 #1 SMP Mon Nov 12 08:32:57 UTC 2007 i686
X Vendor: The X.Org Foundation
X Vendor Release: 10300000
Selinux: No
Accessibility: Disabled
GTK+ Theme: Crux
Icon Theme: Crux

Memory status: size: 97615872 vsize: 97615872 resident: 38912000 share: 16158720 rss: 38912000 rss_rlim: 4294967295
CPU usage: start_time: 1199562802 rtime: 6678 utime: 6120 stime: 558 cutime:0 cstime: 1 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 0xb6d9a6b0 (LWP 11232)]
(no debugging symbols found)
0xb75d8321 in waitpid () from /lib/libpthread.so.0

+ Trace 184217

Thread 1 (Thread 0xb6d9a6b0 (LWP 11232))

  • #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 strcmp
    from /lib/libc.so.6
  • #6 ??
  • #7 ??
  • #0 waitpid
    from /lib/libpthread.so.0 


----------- .xsession-errors (16956 sec old) ---------------------
[mpeg4 @ 0xb6cefb48]marker does not match f_code
[mpeg4 @ 0xb6cefb48]marker does not match f_code
[mpeg4 @ 0xb6cefb48]marker does not match f_code
[mpeg4 @ 0xb6cefb48]marker does not match f_code
[mpeg4 @ 0xb6cefb48]marker does not match f_code
[mpeg4 @ 0xb6cefb48]marker does not match f_code
[mpeg4 @ 0xb6cefb48]marker does not match f_code
[mpeg4 @ 0xb6cefb48]marker does not match f_code
[mpeg4 @ 0xb6cefb48]marker does not match f_code
[mpeg4 @ 0xb6cefb48]marker does not match f_code
[mpeg4 @ 0xb6cefb48]marker does not match f_code
[mpeg4 @ 0xb6cefb48]marker does not match f_code
[mpeg4 @ 0xb6cefb48]marker does not match f_code
[mpeg4 @ 0xb6cefb48]marker does not ma
...Too much output, ignoring rest...
--------------------------------------------------
Comment 1 Cosimo Cecchi 2008-01-07 13:30:20 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 ***