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 763206 - RhythmDB-CRITICAL **: rhythmdb_entry_get_entry_type: assertion 'entry != NULL' failed
RhythmDB-CRITICAL **: rhythmdb_entry_get_entry_type: assertion 'entry != NULL...
Status: RESOLVED FIXED
Product: rhythmbox
Classification: Other
Component: general
3.3
Other Linux
: High critical
: ---
Assigned To: RhythmBox Maintainers
RhythmBox Maintainers
Depends on:
Blocks:
 
 
Reported: 2016-03-07 08:10 UTC by pascal.christoph
Modified: 2016-03-08 08:36 UTC
See Also:
GNOME target: ---
GNOME version: ---


Attachments
gdb trace (14.11 KB, text/plain)
2016-03-07 08:10 UTC, pascal.christoph
Details

Description pascal.christoph 2016-03-07 08:10:12 UTC
Created attachment 323236 [details]
gdb trace

After upgrading my OS "debian-testing" rhythmbox first starts fine and seems to  load the music DB, it even plays a song some time (minute or so), then crashes with:

(rhythmbox:9157): RhythmDB-CRITICAL **: rhythmdb_entry_get_entry_type: assertion 'entry != NULL' failed

Using KDE. Gdb trace attached.
Comment 1 Jonathan Matthew 2016-03-07 08:18:31 UTC
Thanks for taking the time to report this.
Unfortunately, that stack trace is missing some elements that will help a lot to solve the problem, so it will be hard for the developers to fix that crash. Can you get us a stack trace with debugging symbols? Please see https://wiki.gnome.org/Community/GettingInTouch/Bugzilla/GettingTraces for more information on how to do so and reopen this bug report. Thanks in advance!
Comment 2 pascal.christoph 2016-03-07 09:52:25 UTC
I did what's written at https://wiki.gnome.org/Community/GettingInTouch/Bugzilla/GettingTraces/Details#Obtaining_a_stack_trace_using_GDB_with_a_running_program . If I understand http://www.tutorialspoint.com/gnu_debugger/gdb_debugging_symbols.htm correct I have to compile rhythmbox with special parameters?
Comment 3 Jonathan Matthew 2016-03-07 10:03:00 UTC
There are specific instructions for debian here: https://wiki.debian.org/HowToGetABacktrace

You should just have to install some extra packages that provide the necessary debug symbols.
Comment 4 pascal.christoph 2016-03-07 10:23:08 UTC
Did :

# aptitude install rhythmbox-dbg

and then ran agaian gdb. Now there is a bit more of debug info:
{
(rhythmbox:3528): Rhythmbox-WARNING **: Unable to grab media player keys: GDBus.Error:org.freedesktop.DBus.Error.ServiceUnknown: The name org.gnome.SettingsDaemon was not provided by any .service files
...
(rhythmbox:3528): RhythmDB-CRITICAL **: rhythmdb_entry_get_entry_type: assertion 'entry != NULL' failed

Program received signal SIGSEGV, Segmentation fault.
rhythmdb_entry_cache_metadata (entry=0x0) at rhythmdb-entry-type.c:266
266     rhythmdb-entry-type.c: Datei oder Verzeichnis nicht gefunden.
(gdb) thread apply all bt

Thread 1 (Thread 0xf147c940 (LWP 3528))

  • #0 rhythmdb_entry_cache_metadata
    at rhythmdb-entry-type.c line 266
  • #1 rhythmdb_process_metadata_load
    at rhythmdb.c line 2531
  • #2 rhythmdb_process_one_event
    at rhythmdb.c line 2637
  • #3 rb_async_queue_watch_dispatch
  • #4 g_main_context_dispatch
    from /lib/i386-linux-gnu/libglib-2.0.so.0
  • #5 ??
    from /lib/i386-linux-gnu/libglib-2.0.so.0
  • #6 g_main_context_iteration
    from /lib/i386-linux-gnu/libglib-2.0.so.0
  • #7 g_application_run
    from /usr/lib/i386-linux-gnu/libgio-2.0.so.0
  • #8 rb_application_run
    at rb-application.c line 646
  • #9 main
    at main.c line 89

Comment 5 Jonathan Matthew 2016-03-07 12:17:03 UTC
Thanks.  Commit 036ed0a fixes this.
Comment 6 Jonathan Matthew 2016-03-07 21:23:54 UTC
You should be able to stop the current version from crashing by removing files smaller than 4kb from your configured music library location.  Otherwise, there should be a new release in a couple of weeks that will include this fix.
Comment 7 pascal.christoph 2016-03-08 08:36:24 UTC
Thx very much :)