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 708092 - rhthmbox crashes after playing an ogg vorbis file
rhthmbox crashes after playing an ogg vorbis file
Status: RESOLVED DUPLICATE of bug 700401
Product: rhythmbox
Classification: Other
Component: playback
2.99.x
Other Linux
: Normal normal
: ---
Assigned To: RhythmBox Maintainers
RhythmBox Maintainers
Depends on:
Blocks:
 
 
Reported: 2013-09-14 22:26 UTC by gonzalo rivero
Modified: 2013-09-14 22:37 UTC
See Also:
GNOME target: ---
GNOME version: ---



Description gonzalo rivero 2013-09-14 22:26:01 UTC
Overview: 
rhythmbox crashes after a song in an oggvorbis files finishes or I skip to the next song. My library has mp3 and ogg files, and this only seems to happens with ogg.

Steps to Reproduce: 
choose a song (ogg, of course), click on play and waits until it finishes or skip to another

Actual results:
rhythmbox crashes

expected results: plays the next song file

Build Date & Platform:
I don't know the date, but it is from debian testing on amd64
Version: 2.99.1-3
Installed-Size: 594
Maintainer: Debian GNOME Maintainers <pkg-gnome-maintainers@lists.alioth.debian.org>
Architecture: amd64
Linux 3.10-2-amd64 #1 SMP Debian 3.10.7-1 (2013-08-17) x86_64 GNU/Linux

Additional Information:gdb information:
sfish@gonzalo:~$ gdb rhythmbox
GNU gdb (GDB) 7.6 (Debian 7.6-5)
Copyright (C) 2013 Free Software Foundation, Inc.
License GPLv3+: GNU GPL version 3 or later <http://gnu.org/licenses/gpl.html>
This is free software: you are free to change and redistribute it.
There is NO WARRANTY, to the extent permitted by law.  Type "show copying"
and "show warranty" for details.
This GDB was configured as "x86_64-linux-gnu".
For bug reporting instructions, please see:
<http://www.gnu.org/software/gdb/bugs/>...
Reading symbols from /usr/bin/rhythmbox...Reading symbols from /usr/lib/debug/.build-id/91/730e7327bd7bc6d284380f5cb40ee473502310.debug...done.
done.
(gdb) run
Starting program: /usr/bin/rhythmbox 
warning: Could not load shared library symbols for linux-vdso.so.1.
Do you need "set solib-search-path" or "set sysroot"?
[Thread debugging using libthread_db enabled]
Using host libthread_db library "/lib/x86_64-linux-gnu/libthread_db.so.1".
[New Thread 0x7fffde004700 (LWP 14802)]
[New Thread 0x7fffd7fff700 (LWP 14803)]
[New Thread 0x7fffd508e700 (LWP 14804)]
[New Thread 0x7fffd488d700 (LWP 14805)]
[Thread 0x7fffd488d700 (LWP 14805) exited]
[New Thread 0x7fffd488d700 (LWP 14807)]
[Thread 0x7fffd488d700 (LWP 14807) exited]
[New Thread 0x7fffc2fc1700 (LWP 14810)]
[New Thread 0x7fffc21ab700 (LWP 14812)]
[New Thread 0x7fffc19aa700 (LWP 14813)]
[New Thread 0x7fffc11a9700 (LWP 14814)]
[Thread 0x7fffc11a9700 (LWP 14814) exited]
[Thread 0x7fffc2fc1700 (LWP 14810) exited]
[Thread 0x7fffc21ab700 (LWP 14812) exited]
[New Thread 0x7fffc21ab700 (LWP 14815)]
[Thread 0x7fffc21ab700 (LWP 14815) exited]
[New Thread 0x7fffc8108700 (LWP 14816)]
Cannot connect to server socket err = No existe el fichero o el directorio
Cannot connect to server request channel
jack server is not running or cannot be started
[Thread 0x7fffc8108700 (LWP 14816) exited]
[New Thread 0x7fffc21ab700 (LWP 14817)]
[New Thread 0x7fffc2fc1700 (LWP 14818)]
[New Thread 0x7fffb4ecf700 (LWP 14819)]
[New Thread 0x7fffaffff700 (LWP 14821)]
[New Thread 0x7fffaf7fe700 (LWP 14822)]
[New Thread 0x7fffaeffd700 (LWP 14823)]
[New Thread 0x7fffae3e7700 (LWP 14824)]
[New Thread 0x7fffadbe6700 (LWP 14825)]
[Thread 0x7fffc21ab700 (LWP 14817) exited]
[Thread 0x7fffadbe6700 (LWP 14825) exited]
[New Thread 0x7fffadbe6700 (LWP 14830)]
[New Thread 0x7fffc21ab700 (LWP 14831)]
[New Thread 0x7fffad3e5700 (LWP 14835)]
[Thread 0x7fffad3e5700 (LWP 14835) exited]
[Thread 0x7fffadbe6700 (LWP 14830) exited]
[New Thread 0x7fffacbe4700 (LWP 14836)]
[Thread 0x7fffacbe4700 (LWP 14836) exited]
[Thread 0x7fffc2fc1700 (LWP 14818) exited]
[New Thread 0x7fffc2fc1700 (LWP 14847)]
[New Thread 0x7fffacbe4700 (LWP 14848)]
[Thread 0x7fffacbe4700 (LWP 14848) exited]
[Thread 0x7fffc2fc1700 (LWP 14847) exited]
[New Thread 0x7fffc2fc1700 (LWP 14870)]
[New Thread 0x7fffacbe4700 (LWP 14871)]
[Thread 0x7fffacbe4700 (LWP 14871) exited]
[New Thread 0x7fffacbe4700 (LWP 14875)]
[Thread 0x7fffc2fc1700 (LWP 14870) exited]
[Thread 0x7fffacbe4700 (LWP 14875) exited]
[New Thread 0x7fffacbe4700 (LWP 14914)]
[New Thread 0x7fffc2fc1700 (LWP 14915)]
[Thread 0x7fffacbe4700 (LWP 14914) exited]
[New Thread 0x7fffacbe4700 (LWP 14919)]
[Thread 0x7fffacbe4700 (LWP 14919) exited]
[Thread 0x7fffc2fc1700 (LWP 14915) exited]
[New Thread 0x7fffc2fc1700 (LWP 14966)]
[New Thread 0x7fffacbe4700 (LWP 14967)]
[Thread 0x7fffacbe4700 (LWP 14967) exited]
[New Thread 0x7fffacbe4700 (LWP 14968)]
[New Thread 0x7fff97fff700 (LWP 14972)]
[New Thread 0x7fff977fe700 (LWP 14973)]
[Thread 0x7fff97fff700 (LWP 14972) exited]
[Thread 0x7fff977fe700 (LWP 14973) exited]
[Thread 0x7fffc2fc1700 (LWP 14966) exited]
[Thread 0x7fffacbe4700 (LWP 14968) exited]
[New Thread 0x7fffacbe4700 (LWP 15007)]
[New Thread 0x7fffc2fc1700 (LWP 15008)]
[Thread 0x7fffc2fc1700 (LWP 15008) exited]
[New Thread 0x7fffc2fc1700 (LWP 15012)]
[Thread 0x7fffc2fc1700 (LWP 15012) exited]
[Thread 0x7fffacbe4700 (LWP 15007) exited]
[New Thread 0x7fffacbe4700 (LWP 15049)]
[New Thread 0x7fffc2fc1700 (LWP 15050)]
[Thread 0x7fffacbe4700 (LWP 15049) exited]
[New Thread 0x7fffacbe4700 (LWP 15054)]
[New Thread 0x7fff977fe700 (LWP 15055)]
[Thread 0x7fff977fe700 (LWP 15055) exited]
[Thread 0x7fffacbe4700 (LWP 15054) exited]
[Thread 0x7fffc2fc1700 (LWP 15050) exited]
[New Thread 0x7fffc2fc1700 (LWP 15078)]
[New Thread 0x7fffacbe4700 (LWP 15079)]
[New Thread 0x7fff97fff700 (LWP 15080)]
[New Thread 0x7fff96ffd700 (LWP 15084)]
[New Thread 0x7fff967fc700 (LWP 15085)]

(rhythmbox:14797): GStreamer-CRITICAL **: gst_segment_to_stream_time: assertion `segment->format == format' failed
[Thread 0x7fffae3e7700 (LWP 14824) exited]
[New Thread 0x7fffae3e7700 (LWP 15087)]
[Thread 0x7fffae3e7700 (LWP 15087) exited]
[New Thread 0x7fffc8108700 (LWP 15088)]
Cannot connect to server socket err = No existe el fichero o el directorio
Cannot connect to server request channel
jack server is not running or cannot be started
[Thread 0x7fffc8108700 (LWP 15088) exited]

** (rhythmbox:14797): CRITICAL **: g_callable_info_load_return_type: assertion `GI_IS_CALLABLE_INFO (info)' failed

** (rhythmbox:14797): CRITICAL **: g_type_info_get_tag: assertion `GI_IS_TYPE_INFO (info)' failed

** (rhythmbox:14797): CRITICAL **: g_callable_info_get_caller_owns: assertion `GI_IS_CALLABLE_INFO (info)' failed

** (rhythmbox:14797): CRITICAL **: g_type_info_get_tag: assertion `GI_IS_TYPE_INFO (info)' failed

** (rhythmbox:14797): CRITICAL **: g_type_info_get_tag: assertion `GI_IS_TYPE_INFO (info)' failed

** (rhythmbox:14797): CRITICAL **: g_callable_info_get_n_args: assertion `GI_IS_CALLABLE_INFO (info)' failed
**
ERROR:girepository/gibaseinfo.c:293:g_base_info_get_name: assertion failed: (rinfo->ref_count > 0)

Program received signal SIGABRT, Aborted.
0x00007fffef8581e5 in __GI_raise (sig=sig@entry=6) at ../nptl/sysdeps/unix/sysv/linux/raise.c:56
56	../nptl/sysdeps/unix/sysv/linux/raise.c: No existe el fichero o el directorio.
Comment 1 gonzalo rivero 2013-09-14 22:34:02 UTC
when I skip a song, gdb produces different output:
...
[Thread 0x7fffc8136700 (LWP 15439) exited]

Program received signal SIGSEGV, Segmentation fault.
0x00007ffff055b520 in g_base_info_get_type () from /usr/lib/libgirepository-1.0.so.1


Also, when running from gdb, rhythmbox doesn't crash, but hangs (I don't know if this is a normal behavior when running programs from gdb)
Comment 2 Jonathan Matthew 2013-09-14 22:37:07 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 bug 700401 ***