Pithos launch triggers indicator-sound crash SIGSEGV in g_variant_builder_add_value()

Bug #1310951 reported by Spencer
56
This bug affects 13 people
Affects Status Importance Assigned to Milestone
The Sound Menu
Invalid
Undecided
Unassigned

Bug Description

Same issue as https://github.com/pithos/pithos/issues/90

One "workaround" is to use "killall unity-panel-service" to force the panel service to restart.

Tags: trusty
Revision history for this message
Spencer (spec4d) wrote :
tags: added: trusty
Revision history for this message
Charles Kerr (charlesk) wrote :

 Thank you for taking the time to report this bug and helping to make Ubuntu better. However, your crash report is either missing or challenging to deal with as a ".crash" file. Please follow these instructions to have apport report a new bug about your crash that can be dealt with by the automatic retracer.

If you are running the Ubuntu Stable Release you might need to enable apport in /etc/default/apport and restart.

Now open your file manager, navigate to your /var/crash directory and open the crash report you wish to submit.
If this fails you will have to open a terminal and file your report with 'ubuntu-bug /var/crash/_my_crash_report.crash' where _my_crash_report.crash is the crash you would like to report. If you get an error that you aren't allowed to access this report you will have to file it with 'sudo ubuntu-bug /var/crash/_my_crash_report.crash'.

I'm closing this bug report since the process outlined above will automatically open a new bug report which can then dealt with more efficiently. Thanks in advance for your cooperation and understanding.

Changed in indicator-sound:
status: New → Invalid
Revision history for this message
Scott Kostyshak (scott-kostyshak) wrote :
Revision history for this message
Scott Kostyshak (scott-kostyshak) wrote :

For some reason, 'ubuntu-bug' does not open a bug report for me to create a new bug. I have apport enabled and whoopsie seems to be fine so I'm not sure why. I attach the .crash here.

Revision history for this message
Corey J. Bryant (c-jason-b) wrote :

Duplicated today 21 July 2014 approx 20:00:00
Simply opened Pithos and the problem occurred. Problem did not exist with Pithos approximately 3 weeks ago.

To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.