Amarok freezes on Kubuntu Feisty
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
Medibuntu |
Fix Released
|
Undecided
|
Unassigned | ||
amarok (Ubuntu) |
Invalid
|
Undecided
|
Unassigned |
Bug Description
Binary package hint: amarok
I've been running Feisty since Herd 3 came out and haven't used Amarok since, so I'm not sure if this problem has been there all along or has occurred by a set of recent updates. When I run Amarok (for the first time) and try to open an MP3 file, I get the message box stating that MP3 support has not been installed and do I want to install it. But after this message displayed Amarok freezes up. The cursor turns to busy and I can't click the "Install MP3 support" button and have to kill Amarok. I've tried reinstalling Amarok and the same thing happens.
I'm using Amarok 1.4.5
Andrew Ash (ash211) wrote : | #1 |
Changed in amarok: | |
assignee: | nobody → ash211 |
status: | Unconfirmed → Needs Info |
Justin Newman (eqisow) wrote : | #2 |
I have the same problem. I get the following output in console:
Amarok: [Loader] Starting amarokapp..
Amarok: [Loader] Don't run gdb, valgrind, etc. against this binary! Use amarokapp.
kdecore (KAction): WARNING: KAction:
QLayout "unnamed" added to QVBox "unnamed", which already has a layout
kdecore (KAction): WARNING: KAction:
QLayout: Adding KToolBar/
After that, it drops back to the prompt. The Amarok tray applet is present, but invisible (it makes the tray expand) and the process is still running, but simply sits at 50-80% CPU usage doing nothing.
Andrew Ash (ash211) wrote : | #3 |
Thanks, Justin. It looks to me like this may have been a corrupted setting in ~/.kde
Please try backing up ~/.kde/
Justin Newman (eqisow) wrote : | #4 |
I just tested forcing the edgy version of 1.4.5. It produces the same results. Rolling even further back to 1.4.4 from Medibuntu (unsupported, I know) results in the process not even starting.
Justin Newman (eqisow) wrote : | #5 |
Sorry Andrew, I posted that last comment before I saw yours. You were correct; that solved the problem. I lost my collection, settings, etc. obviously, but at least it works!
Andrew Ash (ash211) wrote : | #6 |
That begs the question, though, of what caused 1.4.5 to not work anymore. Did you do a clean install of Herd 3 or have you been dist-upgrading through the process or from an edgy installation?
Justin Newman (eqisow) wrote : | #7 |
My system is a dist-upgrade of Edgy that was a dist-upgrade of Dapper, so it could very likely be related to that. I had been using 1.4.4 in Feisty with no incident though.
Andrew Ash (ash211) wrote : | #8 |
I'm confirming this then. We'll have to make sure that plenty of dist-upgrade testing is done between edgy and feisty then to ensure that this isn't a problem for more people.
I'm not quite sure what would have made 1.4.4 work fine and 1.4.5 not. Maybe internal config file structure changed or something.
Anyways, this needs to be checked on as the release of Feisty approaches :)
Changed in amarok: | |
assignee: | ash211 → nobody |
status: | Needs Info → Confirmed |
Kazade (kazade) wrote : | #9 |
When the bug occurred with me, it was on a clean install of Feisty NOT a dist-upgrade from Edgy. I dont know what I did but Amarok is working now, I installed MP3 support manually, then when I tried to play an MP3 in Amarok it said MP3 support needed to be installed. I could click the install button this time, but then it froze. I killed Amarok and when I restarted it was working fine.
Justin Newman (eqisow) wrote : | #10 |
I'm not sure whether this should be filed as a new report or not, because it seems slightly different. However, Amarok has started locking up when I launch it again. This time, however, the window opens but becomes unresponsive nearly immediately. I have tried purging the configuration files as well as re-installing Amarok to no avail. It started when Amarok refused to play music; it said the audio device was in use even though I wasn't actually using any other audio. I restarted the application to try and fix the error, and have been stuck like this since. The console output is as follows:
kdecore (KAction): WARNING: KAction:
QLayout "unnamed" added to QVBox "unnamed", which already has a layout
kdecore (KAction): WARNING: KAction:
QLayout: Adding KToolBar/
Jeroen Vijfhuizen (jeroenvijfhuizen) wrote : | #11 |
Having this issue too. Dist-upgrade from Edgy, now at Amarok version 1.4.5. Installed libxine-
kdecore (KAction): WARNING: KAction:
QLayout "unnamed" added to QVBox "unnamed", which already has a layout
kdecore (KAction): WARNING: KAction:
QLayout: Adding KToolBar/
STARTUP
So the above warnings are not an issue and happen before the mp3 issue, this is what I get after adding a mp3:
Xlib: unexpected async reply (sequence 0x158e4d)!
After which the program hangs. I now cancel the program (CTRL-C) and try again. When I add another mp3 now, I get:
Very strange! got a DCOPReply opcode, but we were not waiting for a reply!
This message shows, nothing happens ( although I suspect a background job is hanging). Unlike the first time, I can continue using the program.
So the last message is different on two different tries and seems to vary between mp3 files. Quite odd.
vaughn (vaughngrisham) wrote : | #12 |
I had the same issue with a clean install of herd 5. I took the steps you suggested, but it still freezes when the No MP3 Support box pops up. Any suggestions?
vaughn (vaughngrisham) wrote : | #13 |
I forgot to add my output....
vaughn@
X Error: BadDevice, invalid or uninitialized input device 169
Major opcode: 145
Minor opcode: 3
Resource id: 0x0
Failed to open device
X Error: BadDevice, invalid or uninitialized input device 169
Major opcode: 145
Minor opcode: 3
Resource id: 0x0
Failed to open device
kdecore (KAction): WARNING: KAction:
QLayout "unnamed" added to QVBox "unnamed", which already has a layout
kdecore (KAction): WARNING: KAction:
QLayout: Adding KToolBar/
STARTUP
amarok: WARNING: Pixmap not found for mimetype application/
amarok: WARNING: Pixmap not found for mimetype application/
Amarok is crashing...
Running: gdb --nw -n --batch -x /tmp/kde-
Running: file `which amarokapp`
1.4.5 [___stripped]
X Error: BadIDChoice (invalid resource ID chosen for this connection) 14
Major opcode: 53
Minor opcode: 0
Resource id: 0x3600cee
X Error: BadDrawable (invalid Pixmap or Window parameter) 9
Major opcode: 62
Minor opcode: 0
Resource id: 0x3600ce5
X Error: RenderBadPicture (invalid Picture parameter) 180
Major opcode: 153
Minor opcode: 7
Resource id: 0x3600ce6
X Error: BadPixmap (invalid Pixmap parameter) 4
Major opcode: 54
Minor opcode: 0
Resource id: 0x3600ce5
X Error: BadIDChoice (invalid resource ID chosen for this connection) 14
Major opcode: 153
Minor opcode: 4
Resource id: 0x3600cf1
X Error: BadIDChoice (invalid resource ID chosen for this connection) 14
Major opcode: 1
Minor opcode: 0
Resource id: 0x3600cf2
X Error: BadIDChoice (invalid resource ID chosen for this connection) 14
Major opcode: 1
Minor opcode: 0
Resource id: 0x3600cf3
Xlib: sequence lost (0x2a7ad2 > 0x2a79d2) in reply type 0x1!
vaughn (vaughngrisham) wrote : | #14 |
Here's a verified workaround!
http://
Quoting LindaLinux:
Go to amarok director, /usr/lib/amarok. There you will find install mp3. Click it , mp3 support will be installed. Then start amarok, it will work fine.
## End Quote
A.K.Karthikeyan (mindaslab) wrote : | #15 |
If Kubuntu wants to be equal to Vista, this must be fixed. Not all Linux users are geeks.
Regards
A.K.Karthikeyan
Evgeny Remizov (ram3ai) wrote : | #16 |
Confirming this on a fresh Kubuntu Feisty (release, dvd) install. Neither deleting both config directories nor running install-mp3 manually helps.
jonas_s (jonas-soderstrom) wrote : | #17 |
I also experience this bug. Or at least a bug similar to it.
I installed Feisty ( Desktop 32-bit ) from iso I downloaded from Kubuntu homepage.
When I start Amarok I get to screen that says "Hello Amarok User..." The cursor is spinning and spinning and nothing happens.
I have to terminate it. ( Output later in comment )
I have tried deleting ~/.kde/
Didn't help.
I tried running install-mp3
Didn't install, it just said something like "This didn't work, install libxine1-ffmpeg manually"
I ran "sudo apt-get install libxine1-ffmpeg" which worked fine.
But amarok still won't start.
Could be different bug than explained above but I posted it here just in case. Feel free to move my post.
If there is anything I can do to help you find the problem please let me know.
Output:
X Error: BadDevice, invalid or uninitialized input device 167
Major opcode: 144
Minor opcode: 3
Resource id: 0x0
Failed to open device
X Error: BadDevice, invalid or uninitialized input device 167
Major opcode: 144
Minor opcode: 3
Resource id: 0x0
Failed to open device
Amarok: [Loader] Starting amarokapp..
Amarok: [Loader] Don't run gdb, valgrind, etc. against this binary! Use amarokapp.
X Error: BadDevice, invalid or uninitialized input device 167
Major opcode: 144
Minor opcode: 3
Resource id: 0x0
Failed to open device
X Error: BadDevice, invalid or uninitialized input device 167
Major opcode: 144
Minor opcode: 3
Resource id: 0x0
Failed to open device
kdecore (KAction): WARNING: KAction:
QLayout "unnamed" added to QVBox "unnamed", which already has a layout
kdecore (KAction): WARNING: KAction:
QLayout: Adding KToolBar/
Amarok: [Loader] Amarok is taking a long time to load! Perhaps something has gone wrong?
jonas_s (jonas-soderstrom) wrote : | #18 |
I restarted my computer and it works.
Before trying out Amarok I installed penguin flash and watched a bunch of flash videos.
I also tried playing a .mpg file with Kaffeine that didn't work.
Suddenly the sound stopped working in the flash videos. Can't remember if it before or after I tried Kaffeine.
I thought it was just flash sound that stopped working but now that I think of it the sound stopped working for the whole system
( I remember wondering why Konsole didn't make a sound when I spelled something incorrect. )
So what happened?
Either flash or Kaffeine messed up the sound of my system ( blocked access to the sound card ?? )
And when the sound was messed up Amarok just waited and waited.
I'll try to investigate more later ( I work as a software tester after all )
But not now, it's way past my bedtime.
tomasz2006 (karzelek) wrote : | #19 |
Had the same. I have just upgraded to Kubuntu Feisty (over internet) from a clean install of Edgy. Can it be something to do with my repositories (multiverse, universe) not being enabled? The solution for me was to kill Amarok and manually enable the repositories and install libxine1-ffmpeg.
vaughn (vaughngrisham) wrote : Re: [Bug 84967] Re: Amarok freezes on Kubuntu Feisty | #20 |
tomasz2006, I don't think the repos have anything to do with it; mine were
all enabled.
On 4/23/07, tomasz2006 <email address hidden> wrote:
>
> Had the same. I have just upgraded to Kubuntu Feisty (over internet)
> from a clean install of Edgy. Can it be something to do with my
> repositories (multiverse, universe) not being enabled? The solution for
> me was to kill Amarok and manually enable the repositories and install
> libxine1-ffmpeg.
>
> --
> Amarok freezes on Kubuntu Feisty
> https:/
> You received this bug notification because you are a direct subscriber
> of the bug.
>
jaycun (grout) wrote : | #21 |
I am also experiencing the problem. I also notice that xine does the same thing, so my thought is that it is an issue with the xine-engine that amarok uses.
All the fixes posted above don't work.
Robert (robertvanreij) wrote : | #22 |
Having the same problem when starting amarok. :
X Error: BadDevice, invalid or uninitialized input device 167
Major opcode: 144
Minor opcode: 3
Resource id: 0x0
Failed to open device
X Error: BadDevice, invalid or uninitialized input device 167
Major opcode: 144
Minor opcode: 3
Resource id: 0x0
Failed to open device
Amarok: [Loader] Starting amarokapp..
Amarok: [Loader] Don't run gdb, valgrind, etc. against this binary! Use amarokapp.
X Error: BadDevice, invalid or uninitialized input device 167
Major opcode: 144
Minor opcode: 3
Resource id: 0x0
Failed to open device
X Error: BadDevice, invalid or uninitialized input device 167
Major opcode: 144
Minor opcode: 3
Resource id: 0x0
Failed to open device
kdecore (KAction): WARNING: KAction:
QLayout "unnamed" added to QVBox "unnamed", which already has a layout
kdecore (KAction): WARNING: KAction:
QLayout: Adding KToolBar/
Amarok: [Loader] Amarok is taking a long time to load! Perhaps something has gone wrong?
Kaffeine starts but won't play any mp3 files. XMMS has no problems starting up and playing mp3 files
amadeov (amadeo3d) wrote : | #23 |
Amarok has been freezing since I installed Ubuntu Feisty. The window will come up and it will attempt to load my collection, but it normally freezes at about 90%. Sometimes, I can open a song and play it, but the application will totally freeze after it plays one song. Other times, it will freeze entirely and I will be unable to do anything.
Stefan Wilke (sweepheart) wrote : | #24 |
Hi.
I have the same problem too. I've upgraded my edgy system to one of the last betas. everything works for me. Especially mp3 in amarok. But some days after the final release i 've got these message too. My mp3 support was still installed. After some days i reinstalled my system from a cd. Only my old settings are backed up and work in all other kde-apps. Only the amarok problemis still there. I tried several things, including delete the amarok config, install the libxine-ffmpeg manual and try to execute the install-mp3 script in /usr/lib/amarok (it dont starts). So i have no idea what should i do next.
On my laptop i have nearly the same system (feisty upgraded from edgy) and there it still works.
Findeton (redeadlink) wrote : | #25 |
I have the same problem. I have Amarok 1.4.5 and an upgraded Feisty Fawn. The thing is that i've had feisty fawn for 3 weeks without problems, but yesterday i started the computer and i just couldn't init amarok, it closes after about 5 seconds giving the following output:
$ amarok
Amarok: [Loader] Starting amarokapp..
Amarok: [Loader] Don't run gdb, valgrind, etc. against this binary! Use amarokapp.
kdecore (KAction): WARNING: KAction:
QLayout "unnamed" added to QVBox "unnamed", which already has a layout
kdecore (KAction): WARNING: KAction:
QLayout: Adding KToolBar/
$
Now i'll try to fix this with what's written here.
ksoze (doctor-bangali) wrote : | #26 |
Having this problem since last update
Miguel Tadeu (mtadeunet) wrote : | #27 |
Same problem here. First amarok used to freeze when loading it. After that, I realized my sound card was not being detected( an on board AC97, which is very linux compliant, from my point of view ). After a few tests, I removed my tv card, and the sound card just show up as expected.
Now the behavior is as reported above. It starts playing, but after a few seconds it freezes. The exactly same thing is happening with kaffeine, which makes me think it is something in xine. I don't know is the last series of updates contained a xine update. Can it be something between xine and the last kernel update? Gotta try this with the previous kernel latter today.
regards
gst (g-starck) wrote : | #28 |
Hi guys,
I **had** the exact same issue and found how to fix it - well actually it's running perfectly while i'm listening dire straits with it..
So, I had, too, when launching amarok on cmd line :
greg@brutus:~$ amarokapp
kdecore (KAction): WARNING: KAction:
QLayout "unnamed" added to QVBox "unnamed", which already has a layout
kdecore (KAction): WARNING: KAction:
QLayout: Adding KToolBar/
Amarok is crashing...
Running: gdb --nw -n --batch -x /tmp/kde-
Running: file `which amarokapp`
1.4.5 [___stripped]
Amarok s'est interrompu anormalement ! Nous en sommes vraiment désolé :(
Mais tout n'est pas perdu ! Peut-être qu'une mise à jour est déjà disponible et résoud ce problème. Vérifiez les versions disponibles pour votre distribution.
greg@brutus:~$
NB: I already tried all possible fix of this page (deleting amarok config, reinstalling, ..), no one helped.
So now what I did :
greg@brutus:~$ mv ./.xine/ ._old_.xine
and then:
greg@brutus:~$ amarokapp
kdecore (KAction): WARNING: KAction:
QLayout "unnamed" added to QVBox "unnamed", which already has a layout
kdecore (KAction): WARNING: KAction:
QLayout: Adding KToolBar/
STARTUP
QDom: saving invalid character �, the document will not be well-formed
QDom: saving invalid character �, the document will not be well-formed
QDom: saving invalid character , the document will not be well-formed
QObject:
QObject::connect: Cannot connect (null):
greg@brutus:~$
(it's returned here because I did close it normaly ;))
:))
NB: thx to jaycun's comment as I realized I had also same kind of issue with my xine too..
Alexandre Germain (germain-alexandre) wrote : | #29 |
Justin, I just found a fix for the amarok freezing up upon startup.
I almost banged my head on the wall, until I realized the medibuntu repository was the cause of all my problems.
I couldnt even OPEN xine, it kept on freezing. So I guessed it was xine that crashed amarok.
Here's what I did:
remove the medibuntu depository from /etc/apt/
apt-get update
remove every amarok-related package with "dpkg --force-all -P packages" ("dpkg -l | grep amarok" will give you a list)
remove every xine-related package ( same procedure )
apt-get -f install
And then amarok was back to normal.
This will teach me not to use apt-pinning to conserve TRUE ubuntu packages!!
Alex
Sarah Kowalik (hobbsee-deactivatedaccount) wrote : | #30 |
cant deal with medibuntu. please report medibuntu bugs there instead.
Changed in amarok: | |
status: | Confirmed → Fix Released |
status: | Fix Released → Rejected |
kokoko (bababa) wrote : | #31 |
Just wanted to say that I had this problem too. To fix that, I just enabled the mp3 support manually by installing libxine1-ffmpeg
Pierre_Dubath (pierre-dubath) wrote : | #32 |
I had the same problem that I solved by just installing libxinel-ffmpeg. Thanks for the suggestion. Why is this library not install by default with amarok?
kokoko (bababa) wrote : | #33 |
Pierre_Dubath,
because mp3 is not an open format. By the way, since I'm using Gutsy at the moment, I have to mention that this problem is FIXED in Gutsy, and Amarok downloaded and installed the necessary codecs for me, with no problems.
Guillaume Martres (smarter) wrote : | #34 |
This problem should be fixed with amarok 2:1.4.5-0ubuntu6 or higher, please reopen if you still experience this problem.
Changed in medibuntu: | |
status: | New → Fix Released |
Could you please try running amarok from the command line and posting the output from the crash here? Thanks