Bug 444700 – crash in Home Folder:

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 444700 - crash in Home Folder:


Summary:	crash in Home Folder:


Status:	RESOLVED DUPLICATE of bug 433983

Product:	nautilus
Classification:	Core
Component:	general
Version:	unspecified
Hardware:	Other All

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

URL:
Whiteboard:

Depends on:
Blocks:

Reported:	2007-06-06 12:46 UTC by allissonjorge
Modified:	2007-06-22 18:11 UTC

See Also:
GNOME target:	---
GNOME version:	2.17/2.18

Description allissonjorge 2007-06-06 12:46:39 UTC

What were you doing when the application crashed?



Distribution: Fedora release 6.93 (Rawhide)
Gnome Release: 2.18.0 2007-03-23 (Red Hat, Inc)
BugBuddy Version: 2.18.0

System: Linux 2.6.20-1.3104.fc7 #1 SMP Sat Apr 21 22:20:43 EDT 2007 i686
X Vendor: The X.Org Foundation
X Vendor Release: 10300000
Selinux: No
Accessibility: Disabled
GTK+ Theme: Clearlooks
Icon Theme: Fedora

Memory status: size: 93425664 vsize: 93425664 resident: 31707136 share: 18276352 rss: 31707136 rss_rlim: 4294967295
CPU usage: start_time: 1181127483 rtime: 891 utime: 757 stime: 134 cutime:0 cstime: 0 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 -1209046256 (LWP 2778)]
(no debugging symbols found)
0x00f08402 in __kernel_vsyscall ()

+ Trace 138732

Thread 1 (Thread -1209046256 (LWP 2778))

#0 __kernel_vsyscall
#1 waitpid
from /lib/libpthread.so.0
#2 ??
from /usr/lib/libgnomeui-2.so.0
#3 <signal handler called>
#4 __kernel_vsyscall
#5 raise
from /lib/libc.so.6
#6 abort
from /lib/libc.so.6
#7 g_logv
from /lib/libglib-2.0.so.0
#8 g_log
from /lib/libglib-2.0.so.0
#9 g_assert_warning
from /lib/libglib-2.0.so.0
#10 ??
#11 gtk_tree_model_unref_node
from /usr/lib/libgtk-x11-2.0.so.0
#12 ??
from /usr/lib/libgtk-x11-2.0.so.0
#13 gtk_tree_model_unref_node
from /usr/lib/libgtk-x11-2.0.so.0
#14 ??
from /usr/lib/libgtk-x11-2.0.so.0
#15 ??
from /usr/lib/libgtk-x11-2.0.so.0
#16 ??
from /usr/lib/libgtk-x11-2.0.so.0
#17 ??
from /usr/lib/libgtk-x11-2.0.so.0
#18 gtk_tree_row_reference_free
from /usr/lib/libgtk-x11-2.0.so.0
#19 ??
from /usr/lib/libgtk-x11-2.0.so.0
#20 gtk_tree_view_set_cursor_on_cell
from /usr/lib/libgtk-x11-2.0.so.0
#21 gtk_tree_view_set_cursor
from /usr/lib/libgtk-x11-2.0.so.0
#22 ??
#23 ??
from /lib/libglib-2.0.so.0
#24 g_main_context_dispatch
from /lib/libglib-2.0.so.0
#25 ??
from /lib/libglib-2.0.so.0
#26 g_main_loop_run
from /lib/libglib-2.0.so.0
#27 gtk_main
from /usr/lib/libgtk-x11-2.0.so.0
#28 main
#0 __kernel_vsyscall



----------- .xsession-errors (666 sec old) ---------------------
 Album: Perfil
 Year: 2002
 Comment: by Neckel - Musik4All       
 Track: 3
 Genre: Other
==========================================================================
Opening audio decoder: [mp3lib] MPEG layer-2, layer-3
AUDIO: 44100 Hz, 2 ch, s16le, 192.0 kbit/13.61% (ratio: 24000->176400)
Selected audio codec: [mp3] afm: mp3lib (mp3lib MPEG layer-2, layer-3)
==========================================================================
AO: [alsa] 48000Hz 2ch s16le (2 bytes per sample)
Video: no video
Starting playback...
A:   0.0 (00.0) of 298.0 (04:58.0) ??,?%                                        
A:   0.0 (00.0) of 298.0 (04:58.0) ??,?%                                        
A:   0.1 (00.0) of 298.0 (04:58.0) ??,
...Too much output, ignoring rest...
--------------------------------------------------

Comment 1 André Klapper 2007-06-22 18:11:36 UTC

Thanks for taking the time to report this bug.
This particular bug has already been reported into our bug tracking system, but the maintainers need more information to fix the bug. Could you please answer the questions in the other report in order to help the developers?


*** This bug has been marked as a duplicate of 433983 ***