Bug 508507 – crash in File Browser:

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 508507 - crash in File Browser:


Summary:	crash in File Browser:


Status:	RESOLVED DUPLICATE of bug 356672

Product:	nautilus
Classification:	Core
Component:	general
Version:	2.18.x
Hardware:	Other All

Importance:	High critical
Target Milestone:	---
Assigned To:	Nautilus Maintainers
QA Contact:	Nautilus Maintainers

URL:
Whiteboard:

Depends on:
Blocks:

Reported:	2008-01-10 13:09 UTC by bib
Modified:	2008-01-10 13:42 UTC

See Also:
GNOME target:	---
GNOME version:	2.19/2.20

Description bib 2008-01-10 13:09:34 UTC

Version: 2.18.3

What were you doing when the application crashed?



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

System: Linux 2.6.22-2-686 #1 SMP Fri Aug 31 00:24:01 UTC 2007 i686
X Vendor: The X.Org Foundation
X Vendor Release: 10300000
Selinux: No
Accessibility: Disabled
GTK+ Theme: Clearlooks
Icon Theme: Crux

Memory status: size: 101933056 vsize: 101933056 resident: 43380736 share: 16441344 rss: 43380736 rss_rlim: 4294967295
CPU usage: start_time: 1199952421 rtime: 12463 utime: 8865 stime: 3598 cutime:242 cstime: 56 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 0xb6d496b0 (LWP 4352)]
(no debugging symbols found)
0xffffe410 in __kernel_vsyscall ()

+ Trace 184790

Thread 1 (Thread 0xb6d496b0 (LWP 4352))

#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 __kernel_vsyscall
#7 raise
from /lib/i686/cmov/libc.so.6
#8 abort
from /lib/i686/cmov/libc.so.6
#9 g_logv
from /usr/lib/libglib-2.0.so.0
#10 g_log
from /usr/lib/libglib-2.0.so.0
#11 g_assert_warning
from /usr/lib/libglib-2.0.so.0
#12 ??
#13 ??
#0 __kernel_vsyscall



----------- .xsession-errors ---------------------
** Message: drive = 0
** Message: volume = 0
get boyan pop://boyan@luceros.dccia.ua.es/
Find Items 0
get bib pop://bib@mail.alu.ua.es/
Find Items 0
get bib pop://bib@mail.alu.ua.es/
Find Items 0
get boyan pop://boyan@luceros.dccia.ua.es/
Find Items 0
(nautilus:4352): Eel-CRITICAL **: eel_pango_font_description_get_largest_fitting_font_size: assertion `maximum_acceptable_font_size > minimum_acceptable_font_size' failed
** ERROR **: file fm-tree-model.c: line 1527 (fm_tree_model_unref_node): assertion failed: (parent->dummy_child_ref_count > 0)
aborting...
--------------------------------------------------

Comment 1 Cosimo Cecchi 2008-01-10 13:42:32 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 356672 ***