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 513839 - crash in Computer:
crash in Computer:
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-02-02 07:10 UTC by debianpmd
Modified: 2008-02-02 10:34 UTC
See Also:
GNOME target: ---
GNOME version: 2.19/2.20


Description debianpmd 2008-02-02 07:10:53 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-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: Clearlooks
Icon Theme: gnome

Memory status: size: 75276288 vsize: 75276288 resident: 24477696 share: 15917056 rss: 24477696 rss_rlim: 4294967295
CPU usage: start_time: 1201935980 rtime: 466 utime: 392 stime: 74 cutime:0 cstime: 0 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 0xb6bc16c0 (LWP 7383)]
0xffffe410 in __kernel_vsyscall ()

+ Trace 187817

Thread 1 (Thread 0xb6bc16c0 (LWP 7383))

  • #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 g_str_equal
    from /usr/lib/libglib-2.0.so.0
  • #8 ??
    from /usr/lib/libeel-2-2.20.so
  • #9 ??
  • #10 ??
  • #0 __kernel_vsyscall 


----------- .xsession-errors ---------------------
xrdb:  "*Text.background" on line 226 overrides entry on line 191
xrdb:  "*Label.foreground" on line 232 overrides entry on line 151
xrdb:  "*Text.foreground" on line 238 overrides entry on line 192
/usr/share/themes/Clearlooks/gtk-2.0/gtkrc:170: Invalid symbolic color 'tooltip_bg_color'
/usr/share/themes/Clearlooks/gtk-2.0/gtkrc:170: error: invalid identifier `tooltip_bg_color', expected valid identifier
/usr/share/themes/Clearlooks/gtk-2.0/gtkrc:170: Invalid symbolic color 'tooltip_bg_color'
/usr/share/themes/Clearlooks/gtk-2.0/gtkrc:170: error: invalid identifier `tooltip_bg_color', expected valid identifier
/usr/share/themes/Clearlooks/gtk-2.0/gtkrc:170: Invalid symbolic color 'tooltip_bg_color'
/usr/share/themes/Clearlooks/gtk-2.0/gtkrc:170: error: invalid identifier `tooltip_bg_color', expected valid identifier
Avertissement du gestionnaire de fenêtres : Fenêtre WM_TRANSIENT_FOR 0x64 non valide indiquée pour 0xe00598 ().
(nautilus:3837): Eel-WARNING **: No extension, not implemented yet
Initializing gnome-mount extension
(nautilus:7383): Eel-WARNING **: No extension, not implemented yet
--------------------------------------------------
Comment 1 Gianluca Borello 2008-02-02 10:34:24 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 ***