Bug 86113 – crash of nautilus music-view

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 86113 - crash of nautilus music-view


Summary:	crash of nautilus music-view


Status:	RESOLVED DUPLICATE of bug 85975

Product:	nautilus
Classification:	Core
Component:	File and Folder Operations
Version:	unspecified
Hardware:	Other other

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

URL:
Whiteboard:

Depends on:
Blocks:

Reported:	2002-06-21 06:51 UTC by alkex
Modified:	2004-12-22 21:47 UTC

See Also:
GNOME target:	---
GNOME version:	2.0

Description alkex 2002-06-21 06:49:51 UTC

Package: nautilus
Severity: major
Version: 2.0.0
Synopsis: crash of nautilus music-view
Bugzilla-Product: nautilus
Bugzilla-Component: File and Folder Operations
BugBuddy-GnomeVersion: 2.0 (2.0.1)

Description:
Description of Problem:
can't start nautilus in a directory were was selected the music-view and
were there is no more mp3

Steps to reproduce the problem:
1. set music view far a directory
2. move away from it yuor mp3 files
3. try to open the dir whit nautilus

Actual Results:
crash

Expected Results:
run correctly

How often does this happen?
always

Additional Information:
Backtrace was generated from '/usr/bin/nautilus-music-view'

[New Thread 1024 (LWP 2314)]
[New Thread 2049 (LWP 2315)]
[New Thread 1026 (LWP 2316)]
[New Thread 2051 (LWP 2317)]
0x40a5f319 in __wait4 () from /lib/libc.so.6

+ Trace 24109

Thread 1 (Thread 1024 (LWP 2314))

#0 __wait4
from /lib/libc.so.6
#1 __DTOR_END__
from /lib/libc.so.6
#2 waitpid
at wrapsyscall.c line 172
#3 libgnomeui_segv_handle
at gnome-ui-init.c line 620
#4 pthread_sighandler
at signals.c line 97
#5 <signal handler called>
#6 gtk_tree_model_get_valist
at gtktreemodel.c line 1060
#0 __wait4
from /lib/libc.so.6
#1 __DTOR_END__
from /lib/libc.so.6
#2 waitpid
at wrapsyscall.c line 172
#3 libgnomeui_segv_handle
at gnome-ui-init.c line 620
#4 pthread_sighandler
at signals.c line 97
#5 <signal handler called>
#6 gtk_tree_model_get_valist
at gtktreemodel.c line 1060
#7 gtk_tree_model_get
at gtktreemodel.c line 1022
#8 get_song_text
at nautilus-music-view.c line 580
#9 music_view_set_selected_song_title
at nautilus-music-view.c line 636
#10 nautilus_music_view_update
at nautilus-music-view.c line 1821
#11 nautilus_music_view_load_uri
at nautilus-music-view.c line 1846
#12 music_view_load_location_callback
at nautilus-music-view.c line 1878
#13 g_cclosure_marshal_VOID__STRING
at gmarshal.c line 496
#14 g_closure_invoke
at gclosure.c line 437
#15 signal_emit_unlocked_R
at gsignal.c line 2341
#16 g_signal_emit_valist
at gsignal.c line 2100
#17 g_signal_emit
at gsignal.c line 2144
#18 call_load_location
at nautilus-view.c line 159
#19 execute_queued_functions
at nautilus-idle-queue.c line 66
#20 g_idle_dispatch
at gmain.c line 3129
#21 g_main_dispatch
at gmain.c line 1617
#22 g_main_context_dispatch
at gmain.c line 2161
#23 g_main_context_iterate
at gmain.c line 2242
#24 g_main_loop_run
at gmain.c line 2462
#25 gtk_main
at gtkmain.c line 936
#26 nautilus_view_standard_main_multi
at nautilus-view-standard-main.c line 330
#27 nautilus_view_standard_main
at nautilus-view-standard-main.c line 414
#28 main
at main.c line 55
#29 __libc_start_main
at ../sysdeps/generic/libc-start.c line 129


      v_pointer = 0x0}, {v_int = 0, v_uint = 0, v_long = 0, v_ulong = 0,

      v_int64 = 0, v_uint64 = 0, v_float = 0, v_double = 0, v_pointer =
0x0}}}
	error = (gchar *) 0xbffecee4 "t




------- Bug moved to this database by unknown@bugzilla.gnome.org 2002-06-21 02:49 -------

The original reporter (alkex@inwind.it) of this bug does not have an account here.
Reassigning to the exporter, unknown@bugzilla.gnome.org.
Reassigning to the default owner of the component, nautilus-maint@bugzilla.gnome.org.

Comment 1 Luis Villa 2002-06-21 11:17:03 UTC

Damon: is this bug 85975 again?

Comment 2 John Fleck 2002-06-21 13:01:07 UTC

Marking dup, the stack trace is exactly the same as #85337, which was
marked a dup of #85975

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