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 511882 - crash in Computer: I was opening a window o...
crash in Computer: I was opening a window o...
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-24 20:35 UTC by sebastien.estieu
Modified: 2008-01-24 21:10 UTC
See Also:
GNOME target: ---
GNOME version: 2.19/2.20


Description sebastien.estieu 2008-01-24 20:35:37 UTC 
Version: 2.18.3

What were you doing when the application crashed?
I was opening a window of my mobile phone card 


Distribution: Debian lenny/sid
Gnome Release: 2.20.3 2008-01-12 (Debian)
BugBuddy Version: 2.20.1

System: Linux 2.6.22-3-486 #1 Mon Nov 12 07:53:08 UTC 2007 i686
X Vendor: The X.Org Foundation
X Vendor Release: 10300000
Selinux: No
Accessibility: Disabled
GTK+ Theme: Nuvola
Icon Theme: Nuvola

Memory status: size: 74571776 vsize: 74571776 resident: 24915968 share: 15900672 rss: 24915968 rss_rlim: 4294967295
CPU usage: start_time: 1201205789 rtime: 1038 utime: 950 stime: 88 cutime:266 cstime: 27 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 0xb6dd16b0 (LWP 5316)]
(no debugging symbols found)
0xb7626321 in waitpid () from /lib/libpthread.so.0

+ Trace 186674

Thread 1 (Thread 0xb6dd16b0 (LWP 5316))

  • #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 (10 sec old) ---------------------
** Message: volume = 0
** Message: drive = 0
** Message: volume = 0
(nautilus:5316): Gtk-WARNING **: Failed to set text from markup due to error parsing markup: Error on line 1 char 43: Element 'markup' was closed, but the currently open element is 'b'
(nautilus:5316): Gtk-WARNING **: Failed to set text from markup due to error parsing markup: Error on line 1 char 43: Element 'markup' was closed, but the currently open element is 'b'
(nautilus:5316): Gtk-WARNING **: Failed to set text from markup due to error parsing markup: Error on line 1 char 43: Element 'markup' was closed, but the currently open element is 'b'
(nautilus:5316): Gtk-WARNING **: Failed to set text from markup due to error parsing markup: Error on line 1 char 43: Element 'markup' was closed, but the currently open element is 'b'
(nautilus:5316): Gtk-WARNING **: Failed to set text from markup due to error parsing markup: Error on line 1 char 43: Element 'markup' was closed, but the currently open element is 'b'
(nautilus:5316): Gtk-WARNING **: Failed to set text from markup due to error parsing markup: Error on line 1 char 43: Element 'markup' was closed, but the currently open element is 'b'
--------------------------------------------------
Comment 1 Cosimo Cecchi 2008-01-24 21:10:14 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 ***