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 763678 - Import Errors - Sansa - Elementary OS
Import Errors - Sansa - Elementary OS
Status: RESOLVED OBSOLETE
Product: rhythmbox
Classification: Other
Component: Removable Media
3.3
Other Linux
: High critical
: ---
Assigned To: RhythmBox Maintainers
RhythmBox Maintainers
Depends on:
Blocks:
 
 
Reported: 2016-03-15 12:37 UTC by Thomas
Modified: 2018-05-24 18:47 UTC
See Also:
GNOME target: ---
GNOME version: ---



Description Thomas 2016-03-15 12:37:59 UTC
I am using Rhythmbox 3.3 with Elementary Freya. I installed Rhythmbox and libmtp using the fossfreedom ppa.

My device is a Sansa Clip+ in MSC mode. The Sansa Clip has a .is_audio_player file in its root directory.

Elementary Freya doesn't have an automount option so I mount the Sansa Clip in the file browser before opening Rhythmbox. Rhythmbox sees the player and lists it under Other Sources.

I have had no difficulty opening the player, browsing the contents and transferring audio. However, the Rhythmbox Library shows an Import Errors notice when the device is connected. And only when the device is connected. If I click on Import Errors then Rhythmbox crashes.

I have also had a problem opening a USB stick with a .is_audio_player file. Rhythmbox crashing if I click on the device.

Both the player and the stick work just fine with Rhythmbox 3.3 on Ubuntu 14.04.
Comment 1 Jonathan Matthew 2016-03-15 12:42:24 UTC
Thanks for taking the time to report this.
Without a stack trace from the crash it's very hard to determine what caused it.
Can you get us a stack trace? Please see https://wiki.gnome.org/Community/GettingInTouch/Bugzilla/GettingTraces for more information on how to do so. When pasting a stack trace in this bug report, please reset the status of this bug report from NEEDINFO to its previous status. Thanks in advance!
Comment 2 Thomas 2016-03-24 11:21:19 UTC
(In reply to Jonathan Matthew from comment #1)
> Thanks for taking the time to report this.
> Without a stack trace from the crash it's very hard to determine what caused
> it.
> Can you get us a stack trace? Please see
> https://wiki.gnome.org/Community/GettingInTouch/Bugzilla/GettingTraces for
> more information on how to do so. When pasting a stack trace in this bug
> report, please reset the status of this bug report from NEEDINFO to its
> previous status. Thanks in advance!

Hi,

Sorry for the late reply.

I try to install Rhythmbox-dbg but get:

rhythmbox-dbg: 
  Depends: rhythmbox (=3.0.2-0ubuntu2) but 3.3.0.0-1~trustyubuntu3 is to be installed 
 Recommends: gstreamer1.0-plugins-good-dbg but it is not going to be installed


 I try to install  gstreamer1.0-plugins-good-dbg but get:

gstreamer1.0-plugins-good-dbg: 
  Depends: gstreamer1.0-plugins-good (=1.2.4-1~ubuntu1) but 1.2.4-1~ubuntu1+14.04~ricotz1 is to be installed 
  Depends: gstreamer1.0-pulseaudio (=1.2.4-1~ubuntu1) but 1.2.4-1~ubuntu1+14.04~ricotz1 is to be installed

At this point I gave up for fear of creating a mess which will take a week or more to fix. However, downgrading to 3.0.2-0ubuntu1 (trusty) has solved the problem.

I  retained the (1.1.9.0-1+ppafossfreedomubuntu1) libmtp upgrades from the fossfreedom ppa and they don't seem to have caused any bother. The problem is somewhere within fossfreedom's rhythmbox release. 

Sorry that I couldn't be of any more help.
Comment 3 foss.freedom 2016-03-24 12:43:13 UTC
that looks like you've uplifted to the latest gnome-stack using ricotz1 PPA?

Yeah - that will cause you just such issues when installing stuff - not just rhythmbox.

generally sudo apt -f install should sort stuff out ... but you should simulate the install first just to check what is upgraded / and what is uninstalled

sudo apt -s -f install
Comment 4 GNOME Infrastructure Team 2018-05-24 18:47:58 UTC
-- GitLab Migration Automatic Message --

This bug has been migrated to GNOME's GitLab instance and has been closed from further activity.

You can subscribe and participate further through the new bug through this link to our GitLab instance: https://gitlab.gnome.org/GNOME/rhythmbox/issues/1447.