MP3 "install-wizard" (somestimes) fails but reports success

Bug #181479 reported by Finch
4
Affects Status Importance Assigned to Milestone
amarok (Ubuntu)
Invalid
Medium
Unassigned

Bug Description

Hi everybody,

This is for Amarok 1.4.7 on KDE 3.5.8 on Ubuntu 7.10.

When I tried to play an MP3 file, Amarok told me that it cannot currently play MP3 and helpfully offered to install MP3-support.
Oh, that's very nice! I clicked yes.
A few seconds later, it told me (something like): "MP3-support now installed, you need to restart Amarok".
I restarted Amarok and it started by telling me that it cannot play MP3 and again offered to install it for me.
Well... I did that a couple of times until I got bored ;-)

Shortly after that, I found the reason for this strange behavior: I had Synaptic already running so Amarok couldn't start it for me.

I'm pretty sure whatever Amarok tried to do for me returned with an error code and Amarok shouldn't have told me that everything was ok. This can be very confusing, right?

I think the "wizard" is very helpful, but it *should* display an error message if it fails...

One way would be checking the return code which "probably" (?) indicates the error (I sometimes get a message like "configuration database locked").
It would probably be better if you could check if the required package is installed. I don't remember exactly, but this is still "semi-manual", isn't it? What if the user changes the package or in some other way aborts the process?

Finch

Revision history for this message
Sarah Kowalik (hobbsee-deactivatedaccount) wrote :

This is true. Someone should fix this.

Changed in amarok:
importance: Undecided → Medium
status: New → Triaged
Revision history for this message
Andrew Ash (ash211) wrote :

It looks like there was a new version of Amarok uploaded on 3-27-08 to address just this issue [1]. Can you please check that the bug is still occurring and report back? Thanks

[1] https://edge.launchpad.net/ubuntu/+source/amarok

Changed in amarok:
status: Triaged → Incomplete
Revision history for this message
Harald Sitter (apachelogger) wrote :

We are closing this bug report because it lacks the information we need to investigate the problem, as described in the previous comments. Please reopen it if you can give us the missing information, and don't hesitate to submit bug reports in the future. To reopen the bug report you can click on the current status, under the Status column, and change the Status back to "New". Thanks again!

Changed in amarok:
status: Incomplete → Invalid
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Related questions

Remote bug watches

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