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 702916 - rhythmbox crashed with SIGSEGV in sem_post()
rhythmbox crashed with SIGSEGV in sem_post()
Status: RESOLVED INCOMPLETE
Product: rhythmbox
Classification: Other
Component: general
2.99.x
Other Linux
: Normal critical
: ---
Assigned To: RhythmBox Maintainers
RhythmBox Maintainers
Depends on:
Blocks:
 
 
Reported: 2013-06-23 19:36 UTC by Cristian Aravena Romero
Modified: 2017-07-29 15:08 UTC
See Also:
GNOME target: ---
GNOME version: ---


Description Cristian Aravena Romero 2013-06-23 19:36:13 UTC 
Open bug in launchpad.net
https://bugs.launchpad.net/ubuntu/+source/rhythmbox/+bug/1193525

"Crashed while clicking 'next'"

+ Trace 232135

  • #0 sem_post
    at ../nptl/sysdeps/unix/sysv/linux/x86_64/sem_post.S line 33
  • #1 PyThread_release_lock
    from /tmp/apport_sandbox_uP17lo/usr/lib/x86_64-linux-gnu/libpython2.7.so.1.0
  • #2 g_datalist_clear
    at /build/buildd/glib2.0-2.37.1/./glib/gdataset.c line 277
  • #3 g_object_finalize
    at /build/buildd/glib2.0-2.37.1/./gobject/gobject.c line 1019
  • #4 g_object_unref
    at /build/buildd/glib2.0-2.37.1/./gobject/gobject.c line 3189
  • #5 g_thread_pool_thread_proxy
    at /build/buildd/glib2.0-2.37.1/./glib/gthreadpool.c line 309
  • #6 g_thread_proxy
    at /build/buildd/glib2.0-2.37.1/./glib/gthread.c line 798
  • #7 start_thread
    at pthread_create.c line 311
  • #8 clone
    at ../sysdeps/unix/sysv/linux/x86_64/clone.S line 113 






Comment 1


André Klapper





          2015-01-03 22:08:40 UTC
        



There is not a single call from Rhythmbox in that one thread that you pasted. Please provide a complete stacktrace that includes all threads, if this is still a problem.






Comment 2


André Klapper





          2017-07-29 15:08:19 UTC
        



Closing this bug report as no further information has been provided. Please feel free to reopen this bug report if you can provide the information that was asked for in a previous comment.
Thanks!