Amarok process runs, but application window/tray icon do not appear

Bug #199011 reported by ironstorm
12
Affects Status Importance Assigned to Milestone
amarok (Ubuntu)
Fix Released
Undecided
Unassigned

Bug Description

Binary package hint: amarok

Click on the amarok quick launch icon, amarok menu item, or type amarok or amarokapp in a terminal. The process starts eating up ~256MB, but the application window does not open, no tray icon appears and it uses no CPU cycles.

amarok-kde4 does load (too bad it's still pre-alpha crap)...

Kubuntu Gutsy / AMD64 / Compiz + Emerald - here is the System info and gdb output:
ged@quadcore:~/libdjconsole-0.1.2$ cat /etc/lsb-release
DISTRIB_ID=Ubuntu
DISTRIB_RELEASE=7.10
DISTRIB_CODENAME=gutsy
DISTRIB_DESCRIPTION="Ubuntu 7.10"
ged@quadcore:~/libdjconsole-0.1.2$ uname -a
Linux quadcore 2.6.22-14-generic #1 SMP Tue Feb 12 02:46:46 UTC 2008 x86_64 GNU/Linux
ged@quadcore:~/libdjconsole-0.1.2$ amarok --version
Qt: 3.3.7
KDE: 3.5.8
Amarok: 1.4.8

ged@quadcore:~/libdjconsole-0.1.2$ gdb amarokapp
GNU gdb 6.6-debian
Copyright (C) 2006 Free Software Foundation, Inc.
GDB is free software, covered by the GNU General Public License, and you are
welcome to change it and/or distribute copies of it under certain conditions.
Type "show copying" to see the conditions.
There is absolutely no warranty for GDB. Type "show warranty" for details.
This GDB was configured as "x86_64-linux-gnu"...
(no debugging symbols found)
Using host libthread_db library "/lib/libthread_db.so.1".
(gdb) run
Starting program: /usr/bin/amarokapp
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
[Thread debugging using libthread_db enabled]
[New process 10759]
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
---Type <return> to continue, or q <return> to quit---
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
Qt: gdb: -nograb added to command-line options.
         Use the -dograb option to enforce grabbing.
[New Thread 48010086386480 (LWP 10759)]
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
[New Thread 1082149200 (LWP 10762)]
[Thread 1082149200 (LWP 10762) exited]
[New Thread 1090541904 (LWP 10763)]
[Thread 1090541904 (LWP 10763) exited]

Revision history for this message
Harald Sitter (apachelogger) wrote :

Please try whether
`rm -rf ~/.kde/share/config/amarokrc`
resolves the issue.

Changed in amarok:
status: New → Incomplete
Revision history for this message
ironstorm (ironstorm-gmail) wrote :

Here's the output:

ged@quadcore:~$ rm -rf ~/.kde/share/config/amarokrc
ged@quadcore:~$ amarok

Amarok: [Loader] Starting amarokapp..
Amarok: [Loader] Don't run gdb, valgrind, etc. against this binary! Use amarokapp.
[ A small window briefly appears indicating Amarok is updating databases, then disappears ]
Amarok: [Loader] Amarok is taking a long time to load! Perhaps something has gone wrong?

If watching with gdb, the small updating DB window appears after the second "[Thread ... (LWP ... ) exited]" (see previous post), then nothing more... :(

Revision history for this message
ironstorm (ironstorm-gmail) wrote :

An update on this issue... it appeared to resolve itself and now Amarok opens.

There was a language-pack-en update a couple of days ago that may have been the resolution.

This bug may be related to the language issues that killed my X server before... I use Canadian English and a number of Canadian KDE users got nuked and were forced to remove a language pack in order to get kde to start. (Related to bug #191327?)

rediskanight, are you also a Canuck?

Revision history for this message
Harald Sitter (apachelogger) wrote :

Just so I have it written once in a bug tracker: I find the amount and strangeness of issues caused by en_CA quite annoying and time wasting :-(

Revision history for this message
ironstorm (ironstorm-gmail) wrote :

Just so I have written it once in the bug tracker: I find it very annoying that KDE has problems with something so simple as a variation of British English has the occasional "eh" in it, eh?

Revision history for this message
Harald Sitter (apachelogger) wrote :

1) KDE doesn't ship en_CA
2) The issues I came across were all due to completly wrong translation syntax, partly caused by Ubuntu's translation interface.

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

Duplicates of this bug

Other bug subscribers

Remote bug watches

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