Amarok Fails to Start, Tmp Directory is a Text File
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
amarok (Ubuntu) |
Invalid
|
Undecided
|
Unassigned |
Bug Description
Binary package hint: amarok
I'm running gutsy with all the latest updates and back ports enabled. On Jan 11/08 I noticed amarok refused to start. I hadn't used it for a few days before that so I'm not sure exactly when or how this happened. But when I tried to run it, I would see the splash and then nothing, and nothing was running in the system monitor either.
Running from terminal produced this:
kevin@Kevin-
Amarok: [Loader] Starting amarokapp..
Amarok: [Loader] Don't run gdb, valgrind, etc. against this binary! Use amarokapp.
kbuildsycoca running...
kbuildsycoca: WARNING: KTempFile: Error trying to create /home/kevin/
kdecore (KAction): WARNING: KAction:
QLayout "unnamed" added to QVBox "unnamed", which already has a layout
kdecore (KAction): WARNING: KAction:
QLayout: Adding KToolBar/
QObject::connect: Incompatible sender/receiver arguments
amarok: WARNING: KTempFile: Error trying to create /home/kevin/
amarok: WARNING: KTempFile: Error trying to create /home/kevin/
I went under the ./kde directory and noticed that tmp-Kevin-Laptop existed as a plain text file and not a directory. I deleted it and made a directory and that fixed my problem. Amarok now loads fine.
Closing as it is fixed.