Starting yesterday, a couple of strange things started happening. First, Amarok started acting very slow, and then not really responding at all. So I restarted it, but it was even worse. So I rebooted, and then it would not even open Amarok. Furthermore, my Kicker or K Launcher, or whatever it is called, became very unresponsive. This was not a resource issue, since my CPU use (among four processors) was just a few percent, and my memory (of 8GB) was less than 30 percent. When I would start the app launcher from the panel, it would take several minutes to open, and the panel was completely dead during that wait. Some apps, though by no means all, will not open either, such as Muon Package manager.
I tried opening Amarok from a Konsole to see what error messages were thrown, and got:
DBusConnection: session D-Bus connection created before QCoreApplication. Application may misbehave.
QDBusConnection: session D-Bus connection created before QCoreApplication. Application may misbehave.
KGlobal::locale::Warning your global KLocale is being recreated with a valid main component instead of a fake component, this usually means you tried to call i18n related functions before your main component was created. You should not do that since it most likely will not work
It then froze and the CLI did not return until ctrl-c. Amarok never opens though ps -ejH|grep amarok shows some process is running. Still, no significant CPU or memory use. Oddly, this process cannot be killed from the CLI, but can from some System Activity window that comes from a widget on the panel. While the panel is frozen waiting for the launcher menu, my Cairo dock functions fine.
I just did a reinstall of Amarok, because I did not know what else to do. This made no difference. I also purged Amarok and reinstalled, but this changed nothing. I don't even know where to start debugging this.
Anyone have any ideas?
**UPDATE**
Very soon after posting this, my screen started flickering badly. Sound like a video card or driver problem. According to lspci, this is:
VGA compatible controller: Intel Corporation 2nd Generation Core Processor Family Integrated Graphics Controller (rev 09)
**UPDATE #2 (though probably no one cares) **
I did another reboot and noticed that there was a Kate process that was trying to start but didn't. Using ps I found a Kate process that was not showing up on the screen. After killing it, things seemed to go back to normal. That is very strange behavior.
I tried opening Amarok from a Konsole to see what error messages were thrown, and got:
DBusConnection: session D-Bus connection created before QCoreApplication. Application may misbehave.
QDBusConnection: session D-Bus connection created before QCoreApplication. Application may misbehave.
KGlobal::locale::Warning your global KLocale is being recreated with a valid main component instead of a fake component, this usually means you tried to call i18n related functions before your main component was created. You should not do that since it most likely will not work
It then froze and the CLI did not return until ctrl-c. Amarok never opens though ps -ejH|grep amarok shows some process is running. Still, no significant CPU or memory use. Oddly, this process cannot be killed from the CLI, but can from some System Activity window that comes from a widget on the panel. While the panel is frozen waiting for the launcher menu, my Cairo dock functions fine.
I just did a reinstall of Amarok, because I did not know what else to do. This made no difference. I also purged Amarok and reinstalled, but this changed nothing. I don't even know where to start debugging this.
Anyone have any ideas?
**UPDATE**
Very soon after posting this, my screen started flickering badly. Sound like a video card or driver problem. According to lspci, this is:
VGA compatible controller: Intel Corporation 2nd Generation Core Processor Family Integrated Graphics Controller (rev 09)
**UPDATE #2 (though probably no one cares) **
I did another reboot and noticed that there was a Kate process that was trying to start but didn't. Using ps I found a Kate process that was not showing up on the screen. After killing it, things seemed to go back to normal. That is very strange behavior.
Comment