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 507925 - crash in Computer: J'ai fait un clic droit ...
crash in Computer: J'ai fait un clic droit ...
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-07 20:54 UTC by la.poubelle.a.jean
Modified: 2008-01-08 00:54 UTC
See Also:
GNOME target: ---
GNOME version: 2.19/2.20


Description la.poubelle.a.jean 2008-01-07 20:54:57 UTC 
Version: 2.18.3

What were you doing when the application crashed?
J'ai fait un clic droit sur un fichier dans nautilus et j'ai selectionné "Propriétés". Ce bug est systématique


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

System: Linux 2.6.21.070829 #1 SMP PREEMPT Wed Aug 29 22:46:20 CEST 2007 i686
X Vendor: The X.Org Foundation
X Vendor Release: 10300000
Selinux: No
Accessibility: Disabled
GTK+ Theme: Glossy P
Icon Theme: Buuf-Deuce

Memory status: size: 81313792 vsize: 81313792 resident: 30281728 share: 15978496 rss: 30281728 rss_rlim: 4294967295
CPU usage: start_time: 1199742785 rtime: 219 utime: 200 stime: 19 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 0xb6d4c6b0 (LWP 9636)]
(no debugging symbols found)
0xffffe410 in __kernel_vsyscall ()

+ Trace 184445

Thread 1 (Thread 0xb6d4c6b0 (LWP 9636))

  • #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 ---------------------
** Message: volume = 0
** Message: drive = 0
** Message: volume = 0
(nautilus:9636): 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:9636): 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:9636): 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:9636): 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:9636): 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:9636): 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-08 00:54:59 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 ***