Plasma desktop crashes when kde finishes loading

[jaegermeister]

Hello,

while on live version all goes well, after installing vanilla siduction I got this problem, which is that, after completing all the steps in splash screen, the background gets black, no panel, nothing but a bug window which says that the plasma desktop shell unexpectedly failed, reporting a segmentation fault with plasma-desktop.

Odd enough, as this was a fresh install yet to be configured in anything, I thought that something went wrong during install, so just went to init 3 and wiped out .kde, thing which resulted in desktop correctly loading.

After shutting down the machine I booted it this evening and the same phenomenon took place again!

Willing to enquire, I have put yakuake in .kde/Autostart do debug something, and, trying to load plasma-desktop from yakuake I got the following:

Code Select Expand


QDBusConnection: session D-Bus connection created before QCoreApplication. Application may misbehave.
QDBusConnection: session D-Bus connection created before QCoreApplication. Application may misbehave.
QDBusObjectPath: invalid path ""
plasma-desktop(31450)/libplasma Plasma::isPluginVersionCompatible: unversioned plugin detected, may result in instability
QGraphicsLinearLayout::insertItem: cannot insert null item
plasma-desktop(31450)/libplasma Plasma::isPluginVersionCompatible: unversioned plugin detected, may result in instability
plasma-desktop(31450)/libplasma Plasma::isPluginVersionCompatible: unversioned plugin detected, may result in instability
plasma-desktop(31450)/libplasma Plasma::isPluginVersionCompatible: unversioned plugin detected, may result in instability
plasma-desktop(31450)/libplasma Plasma::isPluginVersionCompatible: unversioned plugin detected, may result in instability
plasma-desktop(31450)/libplasma Plasma::isPluginVersionCompatible: unversioned plugin detected, may result in instability
plasma-desktop(31450)/libplasma Plasma::isPluginVersionCompatible: unversioned plugin detected, may result in instability
plasma-desktop(31450)/libplasma Plasma::isPluginVersionCompatible: unversioned plugin detected, may result in instability
plasma-desktop(31450)/libplasma Plasma::isPluginVersionCompatible: unversioned plugin detected, may result in instability
static bool QDeclarativeMetaType::isModule(const QByteArray&, int, int) Qt 4.7 import detected; please note that Qt 4.7 is directly reusable as QtQuick 1.x with no code changes. Continuing, but startup time will be slower.
KCrash: Attempting to start /usr/bin/plasma-desktop from kdeinit
KCrash: Connect sock_file=/home/jaeger/.kde/socket-RONIN/kdeinit4__0
plasma-desktop(31449): Communication problem with  "plasma-desktop" , it probably crashed.
Error message was:  "org.freedesktop.DBus.Error.NoReply" : " "Message did not receive a reply (timeout by message bus)" "

jaeger@RONIN:~$ KCrash: Application 'plasma-desktop' crashing...
KCrash: Attempting to start /usr/lib/kde4/libexec/drkonqi from kdeinit
KCrash: Connect sock_file=/home/jaeger/.kde/socket-RONIN/kdeinit4__0


This is the inxi -F of current machine:

Code Select Expand


System:    Host: RONIN Kernel: 3.17-4.towo-siduction-amd64 x86_64 (64 bit) Desktop: KDE 4.14.2
           Distro: siduction 14.1.0 Indian Summer - kde - (201411230337)
Machine:   System: Hewlett-Packard product: HP xw8400 Workstation
           Mobo: Hewlett-Packard model: 0A08h v: NA Bios: Hewlett-Packard v: 786D5 v02.38 date: 10/25/2010
CPU(s):    2 Dual core Intel Xeon 5150s (-HT-SMP-) cache: 8192 KB
           clock speeds: max: 2667 MHz 1: 1998 MHz 2: 1998 MHz 3: 1998 MHz 4: 1998 MHz
Graphics:  Card: NVIDIA G96 [GeForce 9400 GT]
           Display Server: X.Org 1.16.1.901 drivers: nouveau (unloaded: fbdev,vesa) Resolution: 1600x1200@85.00hz
           GLX Renderer: Gallium 0.4 on NV96 GLX Version: 3.0 Mesa 10.3.2
Audio:     Card-1 Creative Labs SB Audigy driver: snd_emu10k1 Sound: ALSA v: k3.17-4.towo-siduction-amd64
           Card-2 Intel 631xESB/632xESB High Definition Audio Controller driver: snd_hda_intel
Network:   Card-1: Realtek RTL-8100/8101L/8139 PCI Fast Ethernet Adapter driver: 8139too
           IF: eth0 state: down mac: 00:40:f4:5d:89:6b
           Card-2: Broadcom NetXtreme BCM5752 Gigabit Ethernet PCI Express driver: tg3
           IF: eth1 state: up speed: 100 Mbps duplex: full mac: 00:17:08:2a:d3:1b
Drives:    HDD Total Size: 3300.6GB (1.1% used) ID-1: /dev/sda model: WDC_WD1003FBYX size: 1000.2GB
           ID-2: /dev/sdb model: ST330057SSUN300G size: 300.0GB
           ID-3: /dev/sdc model: WDC_WD2003FYYS size: 2000.4GB
Partition: ID-1: / size: 30G used: 4.7G (16%) fs: xfs dev: /dev/sdb2
           ID-2: /home size: 194G used: 110M (1%) fs: xfs dev: /dev/sdb3
Sensors:   System Temperatures: cpu: 51.0C mobo: N/A gpu: 48.0
           Fan Speeds (in rpm): cpu: N/A
Info:      Processes: 221 Uptime: 18 min Memory: 796.7/16054.5MB Client: Shell (bash) inxi: 2.2.16


Till now wiping .kde is the only medicine but one cannot reconfigure desktop every time he loads the system, that gets me nuts!
I tried to fiddle with .kde/share/config/plasma-desktoprc but no results

The machine has been du'd today as well, but no change.
What may it be?
THX

[michaaa62]

For me plasma-desktop crashes, if i fiddle with the system-tray's setting. If i try to activate additional  elements, the session will continue, but after logout or restart plasma-desktop crashes at the next restart. My solution is to just have a default system-tray.


Btw.: You might try to get a working backup of .kde, like .kde-bak, to speed up the process to your final desktop. Switch to  console, then log in as root

Code Select Expand

init 3
rm -rf /home/$USER/.kde
cp -a /home/$USER/.kde-bak /home/$USER/.kde
chown -R $USER:$USER /home/$USER/.kde
init 5

[jaegermeister]

Hello michaaa,

Yes I changed a couple of items in system tray.
I will try to redo the thing without touching it.
I also thought about saving a working KDE profile, but it is just a workaround and not an acceptable solution, the point is that there is some bug that must be squashed.

Actually, for the moment, I would prefer to know which file in .kde originates the mess to try to fix it. Any ideas?

[jaegermeister]

Small update, this morning also on openbsd mailing list the same problem was reported, so it looks like it is not something debian-related but kde-related.

[jaegermeister]

It looks that michaaa is right and that a single addition to systray creates the problem.

To test the issue I have added milou to systray and diffed with a working profile, shit happens in file .kde/share/config/plasma-desktop-appletsrc

Here is the diff of the offending lines:

Code Select Expand


81c81
< geometry=172,3,1026,32
---
> geometry=172,3,998,32
90c90
< geometry=1202,3,32,32
---
> geometry=1174,3,32,32
99c99
< geometry=1238,3,162,32
---
> geometry=1210,3,190,32
105a106,112
> ShowApplicationStatus=true
> ShowCommunications=true
> ShowHardware=true
> ShowSystemServices=true
> ShowUnknown=true
> alwaysShown=
> hidden=
112a120,122
> [Containments][1][Applets][7][Configuration][Applets][1][Shortcuts]
> global=
>
121a132,134
> [Containments][1][Applets][7][Configuration][Applets][13][Shortcuts]
> global=
>
127a141,143
> [Containments][1][Applets][7][Configuration][Applets][14][Shortcuts]
> global=
>
133a150,152
> [Containments][1][Applets][7][Configuration][Applets][15][Shortcuts]
> global=
>
137a157,165
> zvalue=0
>
> [Containments][1][Applets][7][Configuration][Applets][16][Shortcuts]
> global=
>
> [Containments][1][Applets][7][Configuration][Applets][17]
> geometry=0,0,24,24
> immutability=1
> plugin=org.kde.milou


Now the question is, provided that there must be some upstream bug, what to do?
THX

[devil]

could you try, if something other than milou has the same effect? Milou is installed per default in the latest release.


greetz
devil

[jaegermeister]

Yes I can, this night late.

But do you mean just choosing some other icon among the available ones within the list or install some plugin/program (any suggestion?) to see how an element foreign to base install reacts?

[devil]

I guess the latter would make more sense. I guess it does not matter what you choose. I would just like to know if we can pin this to milou or not. Did you remove that before reinstating it?


greetz
devil

[jaegermeister]

Hallo devil,

so, in short: it is tied to milou. Btw I removed it from panel, because I wanted it smaller in systray. That's where shit happened.

Long story: I tried activating all other items one by one like meteo or all together (even battery which is meaningless on this workstation), no problem. Then I installed some program like remmina which shows up in tray and set its icon to always show: no problem. Then installed kdeplasma-addons, but unfortunately none of those does show up in tray, they just can be stuck on desktop. I have, anyway, made several of them run at the same time (also the stupid red ball) with the tray superfull: no problem.

After an hour of intensive and creative tests, I can for sure say that milou in systray wreaks havoc. This looks like something to be signaled upstream to kde developers, of which I know none.

[devil]

This is probably my fault. Milou is not yet officialy in KDE. As I had (and still have) it running here for almost a year, I integrated it into the new release. After release Santa said that he had told me it was buggy still, but I must've missesd that somehow. I never ran into a prob with it, but I just used it, never tried anythintg else.


greetz
devil

[melmarker]

but we can look for updates - and far more - if one could provide useful debugging output, im sure that the kde guys are interested in this.
-- please ignore the sentence about 'are interested in' --
we are outdated, i try to find the last version without KF5

[melmarker]

Good news - milou has reached a 5.x version - bad news the last version build with Qt4 and without KF5 is 0.1. I uploaded the latest version with some desktop file changes and some translation changes. If milou work for one - great, if not - shit happed. In this case we can only suggest to purge the packages and be done with that until KF5 hits debian and/or siduction.

Code Select Expand


apt-get purge plasma-widget-milou


[jaegermeister]

Actually my output could be already useful for debugging.
I could provide further input if instructed how to.

[melmarker]

i dont think that the output is of any use now - the latest commit with qt4 is in late april - until then the development switched to Qt5 and KF5 - on could consider the Qt4 thing dead.