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 505241 - crash in Computer: I was reading the launch...
crash in Computer: I was reading the launch...
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-23 15:49 UTC by Alain DUGUET
Modified: 2007-12-26 22:47 UTC
See Also:
GNOME target: ---
GNOME version: 2.19/2.20


Description Alain DUGUET 2007-12-23 15:49:03 UTC 
Version: 2.18.3

What were you doing when the application crashed?
I was reading the launching properties of a launcher on my .Desktop


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

System: Linux 2.6.22-3-k7 #1 SMP Mon Nov 12 09:12:50 UTC 2007 i686
X Vendor: The X.Org Foundation
X Vendor Release: 10400000
Selinux: No
Accessibility: Disabled
GTK+ Theme: Mist
Icon Theme: Snow-Apple

Memory status: size: 221126656 vsize: 221126656 resident: 171302912 share: 16338944 rss: 171302912 rss_rlim: 4294967295
CPU usage: start_time: 1198420559 rtime: 9925 utime: 8644 stime: 1281 cutime:442 cstime: 68 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 0xb6dfb6b0 (LWP 5004)]
(no debugging symbols found)
0xffffe410 in __kernel_vsyscall ()

+ Trace 182788

Thread 1 (Thread 0xb6dfb6b0 (LWP 5004))

  • #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 (2441 sec old) ---------------------
** Message: volume = 0
** Message: drive = 0
** Message: volume = 0
** Message: drive = 0
** Message: volume = 0
** Message: drive = 0
** Message: volume = 0
** Message: drive = 0
** Message: volume = 0
** Message: drive = 0
** Message: volume = 0
** Message: drive = 0
** Message: volume = 0
...Too much output, ignoring rest...
--------------------------------------------------
Comment 1 Cosimo Cecchi 2007-12-23 18:24:33 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 ***
Comment 2 Alain DUGUET 2007-12-26 22:47:49 UTC 
Thanks to you for your reply and your job!