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 548403 - crash in File Browser: renaming a truetype font...
crash in File Browser: renaming a truetype font...
Status: RESOLVED DUPLICATE of bug 522534
Product: nautilus
Classification: Core
Component: general
2.20.x
Other All
: High critical
: ---
Assigned To: Nautilus Maintainers
Nautilus Maintainers
Depends on:
Blocks:
 
 
Reported: 2008-08-19 09:21 UTC by pragmart
Modified: 2008-08-19 17:02 UTC
See Also:
GNOME target: ---
GNOME version: 2.21/2.22



Description pragmart 2008-08-19 09:21:19 UTC
Version: 2.20.0

What were you doing when the application crashed?
renaming a truetype font in my /usr/share/fonts folder using nautilus "open as root"


Distribution: Debian lenny/sid
Gnome Release: 2.22.3 2008-06-30 (Debian)
BugBuddy Version: 2.22.0

System: Linux 2.6.25-2-686 #1 SMP Fri Jul 18 17:46:56 UTC 2008 i686
X Vendor: The X.Org Foundation
X Vendor Release: 10402000
Selinux: No
Accessibility: Disabled
GTK+ Theme: aqua-clear
Icon Theme: gnome-wise

Memory status: size: 51470336 vsize: 51470336 resident: 24182784 share: 16453632 rss: 24182784 rss_rlim: 4294967295
CPU usage: start_time: 1219137489 rtime: 86 utime: 75 stime: 11 cutime:0 cstime: 0 timeout: 0 it_real_value: 0 frequency: 100

Backtrace was generated from '/usr/bin/nautilus'

(no debugging symbols found)
[Thread debugging using libthread_db enabled]
[New Thread 0xb6b23710 (LWP 25456)]
(no debugging symbols found)
0xb7f6d424 in __kernel_vsyscall ()

Thread 1 (Thread 0xb6b23710 (LWP 25456))

  • #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 ??
    from /usr/lib/libglib-2.0.so.0
  • #7 ??
    from /usr/lib/libglib-2.0.so.0
  • #8 ??
  • #9 ??
  • #10 ??
    from /lib/i686/cmov/libc.so.6
  • #11 ??
  • #0 __kernel_vsyscall

Comment 1 Susana 2008-08-19 17:02:46 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 522534 ***