You are not logged in.
So that's all.
Everything was fine yesterday (except the wifi, but that's normal), I upgraded the system to the latest kdemod packages and today when I started my laptop plasma crashed.
I tried to restart the process and I also used the plasma Nutcracker to be sure that isn't a configuration error.
Anyone knows what could be? Is a packaging error or is just me? Any solution?
Here's the log file found in /myhomedirectory/plasmabug I only attach the one I think it's important, If you want any of the other files just ask
Plasma.log
QDBusObjectPath: invalid path ""
QLayout: Attempting to add QLayout "" to QWidget "", which already has a layout
couldn't create image from "/home/jan/branding.png"
QGraphicsGridLayout::itemAt: invalid row, column 0, 0
QGraphicsGridLayout::itemAt: invalid row, column 0, 1
QGraphicsGridLayout::itemAt: invalid row, column 0, 2
process 6581: arguments to dbus_message_new_method_call() were incorrect, assertion "_dbus_check_is_valid_path (path)" failed in file dbus-message.c line 1078.
This is normally a bug in some application using the D-Bus library.
D-Bus not built with -rdynamic so unable to print a backtrace
KCrash: Application 'plasma-desktop' crashing...
QDBusObjectPath: invalid path ""
QLayout: Attempting to add QLayout "" to QWidget "", which already has a layout
couldn't create image from "/home/jan/branding.png"
QGraphicsGridLayout::itemAt: invalid row, column 0, 0
QGraphicsGridLayout::itemAt: invalid row, column 0, 1
QGraphicsGridLayout::itemAt: invalid row, column 0, 2
process 6588: arguments to dbus_message_new_method_call() were incorrect, assertion "_dbus_check_is_valid_path (path)" failed in file dbus-message.c line 1078.
This is normally a bug in some application using the D-Bus library.
D-Bus not built with -rdynamic so unable to print a backtrace
Offline
Welcome to the forum, zoraks!
Did you read/follow this ?
http://wiki.archlinux.org/index.php/KDE
http://wiki.archlinux.org/index.php/Plasma
http://wiki.archlinux.org/index.php/KDEmod
Offline
Have you tried removing plasmoids one-by-one, to see if one of them is crashing it? I had the same problem, with a slightly different error message, and removing the NetworkManager plasmoid made things work happily.
-Jeffery
Offline
Hi, thanks for reply
Yes it was like you said, I removed the network plasmoid and by now everything is fine and working.
I also found that executing plasma-desktop with sudo makes plasma work so I figure that maybe is some problem with permissions, Is posible?
Anyway thanks both of you, no more sudo plasma-desktop at start! :-)
Offline
No problem, feel free to ask us anyway.
Offline
Yes it was like you said, I removed the network plasmoid and by now everything is fine and working.
The NetworkManager plasmoid on the Kubuntu PPAs works fine, so I'm not sure what's up here (maybe a different revision - I haven't checked), but as far as I know, it's still experimental at the moment. I don't have time to check into this, but this should probably be added to whichever bugtracker would be most relevant. Anyone?
I also found that executing plasma-desktop with sudo makes plasma work so I figure that maybe is some problem with permissions, Is posible?
I don't know why that would make it work, but running your desktop shell as root is probably not a good idea
-Jeffery
Offline