Bug 29339 - Gnome filebrowser chrash when opening.
Summary: Gnome filebrowser chrash when opening.
Status: RESOLVED FIXED
Alias: None
Product: cairo
Classification: Unclassified
Component: general (show other bugs)
Version: 1.9.6
Hardware: x86 (IA32) Linux (All)
: medium major
Assignee: Carl Worth
QA Contact: cairo-bugs mailing list
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2010-08-01 04:47 UTC by Kobi
Modified: 2010-08-08 08:48 UTC (History)
0 users

See Also:
i915 platform:
i915 features:


Attachments
Crash raport (45.28 KB, text/plain)
2010-08-01 04:47 UTC, Kobi
Details

Description Kobi 2010-08-01 04:47:27 UTC
Created attachment 37499 [details]
Crash raport

Nautilus crash when opening home folder or other folder.
Opening home folder (lauching nautilus).
This crash happens only when using elementary theme icons.
I reported bug to gnome https://bugzilla.gnome.org/show_bug.cgi?id=625748
but they said it is cairo bug.

-----------------------------------------------------------------
Distribution: Mandriva Linux release 2010.1 (Official) for i586
Gnome Release: 2.30.0 2010-03-31 (Mandriva)
BugBuddy Version: 2.30.0

System: Linux 2.6.33.5-desktop-2mnb #1 SMP Thu Jun 17 21:30:10 UTC 2010 i686
X Vendor: The X.Org Foundation
X Vendor Release: 10707000
Selinux: No
Accessibility: Disabled
GTK+ Theme: elementary1.1
Icon Theme: elementary
GTK+ Modules: canberra-gtk-module, gnomebreakpad

Memory status: size: 143073280 vsize: 143073280 resident: 24539136 share:
16834560 rss: 24539136 rss_rlim: 18446744073709551615
CPU usage: start_time: 1280651908 rtime: 175 utime: 157 stime: 18 cutime:1
cstime: 0 timeout: 0 it_real_value: 0 frequency: 100

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

[Thread debugging using libthread_db enabled]
[New Thread 0xaf4ffb70 (LWP 14420)]
0xffffe424 in __kernel_vsyscall ()
Comment 1 Chris Wilson 2010-08-08 08:48:48 UTC
Old bug, fixed just after 1.9.6 was snapshotted.


Use of freedesktop.org services, including Bugzilla, is subject to our Code of Conduct. How we collect and use information is described in our Privacy Policy.