I am having this problem as well, exactly as described by
terry_gardener, above. I have attached a GDB backtrace and execution log
with all debugging symbols installed so nothing is missing.

This is still an issue in Saucy currently, though it must not be for
very many people. Wondering why this affects such a small user base?

Please let me know if there is any other information I can provide to
assist in fixing this issue.

Jon

** Attachment added: "GDB execution log and full backtrace with all debugging 
symbols"
   
https://bugs.launchpad.net/ubuntu/+source/rhythmbox/+bug/1193525/+attachment/3997361/+files/rhythmbox_gdb_log_stacktrace.log

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to rhythmbox in Ubuntu.
https://bugs.launchpad.net/bugs/1193525

Title:
  rhythmbox crashed with SIGSEGV in sem_post()

Status in The Rhythmbox Music Management Application:
  New
Status in “rhythmbox” package in Ubuntu:
  Confirmed

Bug description:
  Possible Workaround:

  Try disabling all the python based plugins:
  * Context Pane
  * Cover art search
  * IM status
  * Magnatune store
  * Python console
  * Send tracks
  * Song lyrics
  * Ubuntu One
  * Zeitgeist

  Crashed while clicking 'next'

  ProblemType: Crash
  DistroRelease: Ubuntu 13.10
  Package: rhythmbox 2.99.1-0ubuntu1
  ProcVersionSignature: Ubuntu 3.9.0-6.14-generic 3.9.6
  Uname: Linux 3.9.0-6-generic x86_64
  ApportVersion: 2.10.2-0ubuntu2
  Architecture: amd64
  CrashCounter: 1
  Date: Sat Jun 22 11:12:40 2013
  ExecutablePath: /usr/bin/rhythmbox
  InstallationDate: Installed on 2012-09-09 (285 days ago)
  InstallationMedia: Ubuntu 12.10 "Quantal Quetzal" - Alpha amd64 (20120905.2)
  MarkForUpload: True
  ProcCmdline: rhythmbox
  ProcEnviron:
   XDG_RUNTIME_DIR=<set>
   SHELL=/bin/bash
   LANGUAGE=en_AU:en
   PATH=(custom, no user)
   LANG=en_AU.UTF-8
  SegvAnalysis:
   Segfault happened at: 0x7f76731561e0 <sem_post>:     mov    (%rdi),%eax
   PC (0x7f76731561e0) ok
   source "(%rdi)" (0x00000000) not located in a known VMA region (needed 
readable region)!
   destination "%eax" ok
   Stack memory exhausted (SP below stack segment)
  SegvReason: reading NULL VMA
  Signal: 11
  SourcePackage: rhythmbox
  StacktraceTop:
   sem_post () from /lib/x86_64-linux-gnu/libpthread.so.0
   PyThread_release_lock () from /usr/lib/x86_64-linux-gnu/libpython2.7.so.1.0
   g_datalist_clear () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
   ?? () from /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0
   g_object_unref () from /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0
  Title: rhythmbox crashed with SIGSEGV in sem_post()
  UpgradeStatus: Upgraded to saucy on 2013-05-25 (27 days ago)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo

To manage notifications about this bug go to:
https://bugs.launchpad.net/rhythmbox/+bug/1193525/+subscriptions

-- 
Mailing list: https://launchpad.net/~desktop-packages
Post to     : [email protected]
Unsubscribe : https://launchpad.net/~desktop-packages
More help   : https://help.launchpad.net/ListHelp

Reply via email to