rhythmbox crashes on podcast link click
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
rhythmbox (Ubuntu) |
Invalid
|
Undecided
|
Unassigned |
Bug Description
Binary package hint: rhythmbox
Description: Ubuntu 10.10
Release: 10.10
rhythmbox:
Installato: 0.13.1-0ubuntu6
Candidato: 0.13.1-0ubuntu6
Tabella versione:
*** 0.13.1-0ubuntu6 0
500 http://
100 /var/lib/
0.
500 http://
PROBLEM:
On click on a podcast link in iTunes:
1. Rhythmbox starts
2. Rhythmbox loads the GUI
3. Rhythmbox crashes
SHELL OUTPUT on 'rhythmbox' executed:
(rhythmbox:2948): GLib-GObject-
** Message: pygobject_
** (rhythmbox:2948): DEBUG: SyncDaemon already running, initializing SyncdaemonDaemon object
error: line 3: bad flagvector
error: line 7: bad flagvector
error: line 10: bad flagvector
error: line 12: bad flagvector
error: line 14: bad flagvector
error: line 16: bad flagvector
error: line 21: bad flagvector
error: line 26: bad flagvector
** (rhythmbox:2948): DEBUG: Loading the real store page
** (rhythmbox:2948): WARNING **: Got less number of items in credentials hash table than expected!
** (rhythmbox:2948): DEBUG: navigation requested to https:/
(rhythmbox:2948): GLib-GObject-
** (rhythmbox:2948): DEBUG: navigation requested to http://
Errore di segmentazione
ProblemType: Bug
DistroRelease: Ubuntu 10.10
Package: rhythmbox 0.13.1-0ubuntu6
ProcVersionSign
Uname: Linux 2.6.35-24-generic i686
NonfreeKernelMo
Architecture: i386
Date: Mon Jan 24 21:59:21 2011
ExecutablePath: /usr/bin/rhythmbox
InstallationMedia: Ubuntu 10.10 "Maverick Meerkat" - Release i386 (20101007)
ProcEnviron:
LANG=it_IT.utf8
SHELL=/bin/bash
SourcePackage: rhythmbox
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.