Bug 418686 – crash in Rhythmbox Music Player: I'm was editing my ID3 t...

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 418686 - crash in Rhythmbox Music Player: I'm was editing my ID3 t...


Summary:	crash in Rhythmbox Music Player: I'm was editing my ID3 t...


Status:	RESOLVED DUPLICATE of bug 359083

Product:	rhythmbox
Classification:	Other
Component:	general
Version:	unspecified
Hardware:	Other All

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

URL:
Whiteboard:

Depends on:
Blocks:

Reported:	2007-03-15 19:22 UTC by iack83
Modified:	2007-03-15 23:39 UTC

See Also:
GNOME target:	---
GNOME version:	2.15/2.16

Description iack83 2007-03-15 19:22:03 UTC

Version: 0.9.7.90

What were you doing when the application crashed?
I'm was editing my ID3 tag with easytag


Distribution: Ubuntu 6.10 (edgy)
Gnome Release: 2.16.1 2006-10-02 (Ubuntu)
BugBuddy Version: 2.16.0

Memory status: size: 71139328 vsize: 0 resident: 71139328 share: 0 rss: 28499968 rss_rlim: 0
CPU usage: start_time: 1173986461 rtime: 0 utime: 528 stime: 0 cutime:474 cstime: 0 timeout: 54 it_real_value: 0 frequency: 9

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

(no debugging symbols found)
Using host libthread_db library "/lib/tls/i686/cmov/libthread_db.so.1".
(no debugging symbols found)
[Thread debugging using libthread_db enabled]
[New Thread -1229018944 (LWP 32758)]
[New Thread -1254098016 (LWP 301)]
(no debugging symbols found)
0xffffe410 in __kernel_vsyscall ()

+ Trace 118904

Thread 1 (Thread -1229018944 (LWP 32758))

#0 __kernel_vsyscall
#1 __waitpid_nocancel
from /lib/tls/i686/cmov/libpthread.so.0
#2 gnome_gtk_module_info_get
from /usr/lib/libgnomeui-2.so.0
#3 <signal handler called>
#4 __kernel_vsyscall
#5 raise
from /lib/tls/i686/cmov/libc.so.6
#6 abort
from /lib/tls/i686/cmov/libc.so.6
#7 g_logv
from /usr/lib/libglib-2.0.so.0
#8 g_log
from /usr/lib/libglib-2.0.so.0
#9 g_assert_warning
from /usr/lib/libglib-2.0.so.0
#10 rhythmdb_property_model_new
#11 rhythmdb_property_model_new
#12 rhythmdb_property_model_new
#13 gtk_tree_model_foreach_helper
at gtktreemodel.c line 1576
#14 IA__gtk_tree_model_foreach
at gtktreemodel.c line 1622
#15 rhythmdb_property_model_new
#16 g_object_set_valist
from /usr/lib/libgobject-2.0.so.0
#17 g_object_set
from /usr/lib/libgobject-2.0.so.0
#18 rb_library_browser_set_model
from /usr/lib/librhythmbox-core.so.0
#19 rb_browser_source_get_type
#20 rb_source_search
from /usr/lib/librhythmbox-core.so.0
#21 rb_source_header_clear_search
#22 g_cclosure_marshal_VOID__STRING
from /usr/lib/libgobject-2.0.so.0
#23 g_closure_invoke
from /usr/lib/libgobject-2.0.so.0
#24 g_signal_chain_from_overridden
from /usr/lib/libgobject-2.0.so.0
#25 g_signal_emit_valist
from /usr/lib/libgobject-2.0.so.0
#26 g_signal_emit
from /usr/lib/libgobject-2.0.so.0
#27 rb_search_entry_new
from /usr/lib/librhythmbox-core.so.0
#28 g_source_get_current_time
from /usr/lib/libglib-2.0.so.0
#29 g_main_context_dispatch
from /usr/lib/libglib-2.0.so.0
#30 g_main_context_check
from /usr/lib/libglib-2.0.so.0
#31 g_main_loop_run
from /usr/lib/libglib-2.0.so.0
#32 IA__gtk_main
at gtkmain.c line 1024
#33 main
#0 __kernel_vsyscall

Comment 1 Alex Lancaster 2007-03-15 23:39:03 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 359083 ***