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 511889 - crash in Computer: Trying to view propertie...
crash in Computer: Trying to view propertie...
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:44 UTC by carmen.cru
Modified: 2008-01-24 21:08 UTC
See Also:
GNOME target: ---
GNOME version: 2.19/2.20


Description carmen.cru 2008-01-24 20:44:51 UTC 
Version: 2.18.3

What were you doing when the application crashed?
Trying to view properties of a removable disk with rigth click 


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

System: Linux 2.6.21-2-amd64 #1 SMP Wed Jul 11 05:38:29 UTC 2007 x86_64
X Vendor: The X.Org Foundation
X Vendor Release: 10300000
Selinux: No
Accessibility: Disabled
GTK+ Theme: DebianRed
Icon Theme: gartoon

Memory status: size: 72601600 vsize: 72601600 resident: 23777280 share: 15998976 rss: 23777280 rss_rlim: 18446744073709551615
CPU usage: start_time: 1201190753 rtime: 516 utime: 460 stime: 56 cutime:263 cstime: 20 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 0xf6d696b0 (LWP 3120)]
(no debugging symbols found)
0xf75be321 in waitpid () from /lib/libpthread.so.0

+ Trace 186677

Thread 1 (Thread 0xf6d696b0 (LWP 3120))

  • #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 ---------------------
(nautilus:3120): Gtk-WARNING **: Failed to set text from markup due to error parsing markup: Erreur à la ligne 1 caractère 43 : L'élément « markup » a été fermé, mais l'élément actuellem
(nautilus:3120): Gtk-WARNING **: Failed to set text from markup due to error parsing markup: Erreur à la ligne 1 caractère 43 : L'élément « markup » a été fermé, mais l'élément actuellem
(nautilus:3120): Gtk-WARNING **: Failed to set text from markup due to error parsing markup: Erreur à la ligne 1 caractère 43 : L'élément « markup » a été fermé, mais l'élément actuellem
(nautilus:3120): Gtk-WARNING **: Failed to set text from markup due to error parsing markup: Erreur à la ligne 1 caractère 43 : L'élément « markup » a été fermé, mais l'élément actuellem
(nautilus:3120): Gtk-WARNING **: Failed to set text from markup due to error parsing markup: Erreur à la ligne 1 caractère 43 : L'élément « markup » a été fermé, mais l'élément actuellem
(nautilus:3120): Gtk-WARNING **: Failed to set text from markup due to error parsing markup: Erreur à la ligne 1 caractère 43 : L'élément « markup » a été fermé, mais l'élément actuellem
(bug-buddy:11905): Gtk-WARNING **: Impossible de trouver le moteur de thème dans module_path : « lighthouseblue »
warning: Lowest section in system-supplied DSO at 0xffffe000 is .hash at ffffe0b4
--------------------------------------------------
Comment 1 Cosimo Cecchi 2008-01-24 21:08:40 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 ***