First, I currently have v2.2.1 installed via the KDE repo. After futzing about with it I’ve finally got it working and playing music. The problem is that I can no longer connect my Creative Zen Vision:M. The fact that 2.x no longer provides the MTP device configuration interface is troubling.
Originally, I had the 2.1.x version that is in the 11.2 repo installed. As soon as I plugged in my device Amarok saw it and immediately connected. This blew me away. No such luck in 2.2.1, though.
That actually leads to my next issue. I tried to downgrade so I could try to get that functionality back. I can successfully get the version in the 11.2 repo installed but, whenever I try to run it it immediately crashes. I get the splash screen then the crashed app window.
Anyone think they can help me with this?
How did you make the upgrade? And the subsequent roll-back?
Please post the result of this
zypper lr -d
Upgrade and rollback both via the YaST versioning. I’ll post the results of the command when I get in to work tomorrow.
If you have a repo that provides 2.2
then in a su terminal zypper dup should roll everything back
No dice. I’ve removed the KDE repos as well as the Packman repo and ran “zypper dup” as you suggested. There was certainly a lot of activity as could be expected. However, Amarok still crashes immediately following the splashscreen.
zypper lr -d:
1 | Mozilla | Mozilla | Yes | Yes | 99 | rpm-md | http://download.opensuse.org/repositories/mozilla/openSUSE_11.2/ |
2 | Nvidia | Nvidia | Yes | Yes | 99 | rpm-md | http://download.nvidia.com/opensuse/11.2/ |
3 | http-download.opensuse.org-d66156b7 | Updates for openSUSE 11.2-0 | Yes | Yes | 99 | rpm-md | http://download.opensuse.org/update/11.2/ |
4 | repo-non-oss | openSUSE-11.2-Non-Oss | Yes | Yes | 99 | yast2 | http://download.opensuse.org/distribution/11.2/repo/non-oss/ |
5 | repo-oss | openSUSE-11.2-Oss | Yes | Yes | 99 | yast2 | http://download.opensuse.org/distribution/11.2/repo/oss/ |
I suggest you delete these hidden user files/folders
A step in the right direction. It now loads but sadly it isn’t seeing my Zen still.
At first, plugging the device in indicates it is docked which is what I expected. But then that goes away, track info is displayed and then Amarok crashes.
Granted, this could very well be an issue with the device itself but I haven’t had any problems with it up until now. Perhaps I should do a reset on it just in case anyway.
I have no experience with these devices, I don’t have one. But that there are issues does not surprise me. You may find this has bugged up those settings files again?!
Maybe someone else with one of these will reply with more useful advice than I can offer.
It might be worth looking at the bug reports at Novell and even at kde. And maybe report one yourself.
I found a small bit of info in /var/log/messages after I plugged the device in:
usbfs: process 31828 (amarok) did not claim interface 0 before use
It appears that Amarok is seeing the device. Maybe something is preventing it from grabbing control of it?
Also seeing this:
reset high speed USB device using ehci_hcd and address 34
device descriptor read/64, error -110
It is shortly after this that Amarok crashes.
Did some maintenance on my device and it seems to be good now. Amarok pulled it up as soon as I plugged it in. Now to play around and break it again