Bug 525931 – 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 525931 - crash in File Browser:


Summary:	crash in File Browser:


Status:	RESOLVED DUPLICATE of bug 355018

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

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

URL:
Whiteboard:

Depends on:
Blocks:

Reported:	2008-04-03 10:44 UTC by bib
Modified:	2008-04-03 12:03 UTC

See Also:
GNOME target:	---
GNOME version:	2.21/2.22

Description bib 2008-04-03 10:44:38 UTC

Version: 2.20.0

What were you doing when the application crashed?



Distribution: Debian lenny/sid
Gnome Release: 2.22.0 2008-03-14 (Debian)
BugBuddy Version: 2.22.0

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: 125853696 vsize: 125853696 resident: 66285568 share: 16896000 rss: 66285568 rss_rlim: 4294967295
CPU usage: start_time: 1207203526 rtime: 1628 utime: 1506 stime: 122 cutime:0 cstime: 4 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 0xb6b89720 (LWP 6633)]
[New Thread 0xb44f9b90 (LWP 16354)]
(no debugging symbols found)
0xffffe410 in __kernel_vsyscall ()

+ Trace 194104

Thread 1 (Thread 0xb6b89720 (LWP 6633))

#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 g_str_equal
from /usr/lib/libglib-2.0.so.0
#8 ??
from /usr/lib/libeel-2-2.20.so
#9 ??
#10 ??
#0 __kernel_vsyscall



----------- .xsession-errors ---------------------
(nautilus:6633): Eel-CRITICAL **: eel_pango_font_description_get_largest_fitting_font_size: assertion `maximum_acceptable_font_size > minimum_acceptable_font_size' failed
(nautilus:6633): Eel-CRITICAL **: eel_pango_font_description_get_largest_fitting_font_size: assertion `maximum_acceptable_font_size > minimum_acceptable_font_size' failed
(nautilus:6633): Eel-CRITICAL **: eel_pango_font_description_get_largest_fitting_font_size: assertion `maximum_acceptable_font_size > minimum_acceptable_font_size' failed
(nautilus:6633): Eel-CRITICAL **: eel_pango_font_description_get_largest_fitting_font_size: assertion `maximum_acceptable_font_size > minimum_acceptable_font_size' failed
kbuildsycoca running...
Reusing existing ksycoca
(nautilus:6633): Eel-CRITICAL **: eel_pango_font_description_get_largest_fitting_font_size: assertion `maximum_acceptable_font_size > minimum_acceptable_font_size' failed
(nautilus:6633): Eel-CRITICAL **: eel_pango_font_description_get_largest_fitting_font_size: assertion `maximum_acceptable_font_size > minimum_acceptable_font_size' failed
(nautilus:6633): Eel-WARNING **: No extension, not implemented yet
--------------------------------------------------

Comment 1 Cosimo Cecchi 2008-04-03 12:03:13 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 ***