This forum has been archived. All content is frozen. Please use KDE Discuss instead.

KDE 4.2 Plasma (Panel & Widgets) crash

Tags: None
(comma "," separated)
zmdmw52
Registered Member
Posts
10
Karma
0
OS
[font=Trebuchet MS]
I just upgraded from KDE 4.1.3 to KDE 4.2, on openSUSE 11.1. Initial session was okay, but after logging in second time and trying to add a 'widget' to the panel (after unlocking it), the panel crashed and all the panel icons an widget got spread out over the desktop.

I tried this script as recommended by some, but did not help:[/font]

Code: Select all
kquitapp plasma && rm ~/.kde4/share/config/plasma* && plasma &


[font=Trebuchet MS]What can be done to get the panel back to original state ?[/font]


Linux User 483705
User avatar
bcooksley
Administrator
Posts
19765
Karma
87
OS
Is a new user affected by this?


KDE Sysadmin
[img]content/bcooksley_sig.png[/img]
zmdmw52
Registered Member
Posts
10
Karma
0
OS
bcooksley wrote:Is a new user affected by this?

[font=Trebuchet MS]
There is only 1 User- me; of course, in addition to 'root' (this is a home desktop PC).

I tried out the following in Konsole, as somebody had reported success with it (on openSUSE Forums). The code and results are in box below-[/font]

[size=small][font=Times New Roman]
user@linux-4a48:~> kquitapp plasma
user@linux-4a48:~> rm ~/.kde4/share/config/plasma-appletsrc
user@linux-4a48:~> plasma &
[1] 4516
user@linux-4a48:~> plasma(4519)/libplasma Plasma::AppletPrivate::mainConfigGroup: requesting config for "Plain Desktop" without a containment!
plasma(4519)/libplasma Plasma::AppletPrivate::mainConfigGroup: requesting config for "Panel" without a containment!
QLayout: Attempting to add QLayout "" to QWidget "", which already has a layout
plasma(4519)/kdecore (KService) KServicePrivate::init: The desktop entry file "/usr/share/kde4/services/sysinfo.protocol" has Type= "Application" but no Exec line

Unrecognized character: /
Unrecognized character: /
ERROR: syntax error
plasma(4519)/libplasma Plasma::FrameSvg::resizeFrame: Invalid size QSizeF(-2, -1)
plasma(4519)/libplasma Plasma::FrameSvg::resizeFrame: Invalid size QSizeF(-2, -1)
plasma(4519)/libplasma Plasma::FrameSvg::resizeFrame: Invalid size QSizeF(-2, -1)
Object::connect: Attempt to bind non-signal TaskManager::TaskGroup::editRequest()
Object::connect: Attempt to bind non-signal TaskManager::TaskGroup::editRequest()
QCoreApplication::postEvent: Unexpected null receiver
plasma(4519)/libplasma Plasma::FrameSvg::resizeFrame: Invalid size QSizeF(0, 18)
plasma(4519)/libplasma Plasma::FrameSvg::resizeFrame: Invalid size QSizeF(0, 0)
plasma(4519)/libplasma Plasma::FrameSvg::resizeFrame: Invalid size QSizeF(0, 18)
plasma(4519)/libplasma Plasma::FrameSvg::resizeFrame: Invalid size QSizeF(0, 0)
plasma(4519)/libplasma Plasma::FrameSvg::resizeFrame: Invalid size QSizeF(0, 18)
plasma(4519)/libplasma Plasma::FrameSvg::resizeFrame: Invalid size QSizeF(0, 0)
plasma(4519)/libplasma Plasma::FrameSvg::resizeFrame: Invalid size QSizeF(0, 18)
plasma(4519)/libplasma Plasma::FrameSvg::resizeFrame: Invalid size QSizeF(0, 0)
plasma(4519)/libplasma Plasma::FrameSvg::resizeFrame: Invalid size QSizeF(-16, 18)
plasma(4519)/libplasma Plasma::FrameSvg::resizeFrame: Invalid size QSizeF(0, 0)
plasma(4519)/libplasma Plasma::FrameSvg::resizeFrame: Invalid size QSizeF(-16, 18)
plasma(4519)/libplasma Plasma::FrameSvg::resizeFrame: Invalid size QSizeF(0, 0)
QGraphicsLayout::addChildLayout: layout already has a parent
QGraphicsLayout::addChildLayout: layout already has a parent
user@linux-4a48:~> link g3502 hasn't been detected!
link g3502 hasn't been detected!
link g3502 hasn't been detected!
Couldn't resolve property: linearGradient3679
Couldn't resolve property: linearGradient3681
Couldn't resolve property: linearGradient3941
Couldn't resolve property: linearGradient5184
Couldn't resolve property: linearGradient4745
Couldn't resolve property: radialGradient5077
Couldn't resolve property: linearGradient4636
Couldn't resolve property: linearGradient4592
Couldn't resolve property: linearGradient4247
plasma(4519)/libplasma Plasma::FrameSvg::resizeFrame: Invalid size QSizeF(0, 18)
plasma(4519)/libplasma Plasma::FrameSvg::resizeFrame: Invalid size QSizeF(0, 0)
plasma(4519)/libplasma Plasma::FrameSvg::resizeFrame: Invalid size QSizeF(0, 18)
plasma(4519)/libplasma Plasma::FrameSvg::resizeFrame: Invalid size QSizeF(0, 0)
plasma(4519)/libplasma Plasma::FrameSvg::resizeFrame: Invalid size QSizeF(0, 18)
plasma(4519)/libplasma Plasma::FrameSvg::resizeFrame: Invalid size QSizeF(0, 0)
plasma(4519)/libplasma Plasma::FrameSvg::resizeFrame: Invalid size QSizeF(0, 18)
plasma(4519)/libplasma Plasma::FrameSvg::resizeFrame: Invalid size QSizeF(0, 0)
plasma(4519)/libplasma Plasma::AppletPrivate::mainConfigGroup: requesting config for "Network Management" without a containment!
QDBusObjectPath: invalid path ""
plasma(4519)/libplasma Plasma::FrameSvg::resizeFrame: Invalid size QSizeF(-16, 18)
plasma(4519)/libplasma Plasma::FrameSvg::resizeFrame: Invalid size QSizeF(0, 0)
plasma(4519)/libplasma Plasma::FrameSvg::resizeFrame: Invalid size QSizeF(-16, 18)
plasma(4519)/libplasma Plasma::FrameSvg::resizeFrame: Invalid size QSizeF(0, 0)
QCoreApplication::postEvent: Unexpected null receiver
plasma(4519)/libplasma Plasma::AppletPrivate::mainConfigGroup: requesting config for "Network Management" without a containment!

[cursor stops here...press 'Enter' (Carriage return)]

[1]+ Done plasma
user@linux-4a48:~>
[/font][/size]

PS:
What the user has to enter at cmd prompt is in colored text.

[font=Trebuchet MS]This restored a basic panel & then I was able to add the extra shortcuts & widgets as before.
Should a bugzilla be filed about this, if not already done ? I have seen a number of posts with this problem.

[/font]

Last edited by zmdmw52 on Mon Feb 16, 2009 2:43 pm, edited 1 time in total.


Linux User 483705
User avatar
bcooksley
Administrator
Posts
19765
Karma
87
OS
This is one of those nasty crashes that corrupts the configuration file. If you can reliably reproduce the original crash that corrupted the configuration, then please file a bug. It would be best to install qt, kdelibs, and workspace debug packages so a full backtrace can be generated.


KDE Sysadmin
[img]content/bcooksley_sig.png[/img]
zmdmw52
Registered Member
Posts
10
Karma
0
OS
bcooksley wrote:This is one of those nasty crashes that corrupts the configuration file. If you can reliably reproduce the original crash that corrupted the configuration, then please file a bug. It would be best to install qt, kdelibs, and workspace debug packages so a full backtrace can be generated.


How can I get the required info for reporting the bug- what are the system files that would have a log ?

I will d/l and install the debug packages later today. How is a crash report generated using the debug packages (auto/user-initiated) ? I think I should mention that I do not have an advanced knowledge of Linux/Programming.

Last edited by zmdmw52 on Tue Feb 17, 2009 10:58 am, edited 1 time in total.


Linux User 483705
User avatar
bcooksley
Administrator
Posts
19765
Karma
87
OS
No knowledge of programming is required. The next time this happens, Dr. Konqi will start saying "The application Plasma.... signal SIGSEGV....". When this appears, tick the "More details" checkbox to generate the backtrace. It will take several minutes to do so. Once it is done, save the backtrace and post that, along with your corrupted configuration to a new bug.

The only information generally required is which Distribution you are using, and the steps you took to create the error.

Last edited by bcooksley on Wed Feb 18, 2009 4:43 am, edited 1 time in total.


KDE Sysadmin
[img]content/bcooksley_sig.png[/img]
zmdmw52
Registered Member
Posts
10
Karma
0
OS
bcooksley wrote:No knowledge of programming is required. The next time this happens, Dr. Konqi will start saying "The application Plasma.... signal SIGSEGV....". When this appears, tick the "More details" checkbox to generate the backtrace. It will take several minutes to do so. Once it is done, save the backtrace and post that, along with your corrupted configuration to a new bug.

The only information generally required is which Distribution you are using, and the steps you took to create the error.


[font=Trebuchet MS]As I recall, there was something like that message the first time plasma crashed. The symptoms were similar. I did copy the text (with 'more details') of the Error Message and save it.

You can view it here - http://www.nopaste.com/p/aJ1wBXYxe (NoPaste service, plain text file).

Is this information relevant & how do I proceed ?[/font]


Linux User 483705
User avatar
bcooksley
Administrator
Posts
19765
Karma
87
OS
That is it yes. However it unfortunately is of little use to developers because you are missing the Debug symbols. Please install the appropriate debugging Packages ( Qt, KDE Libs, Plasma )


KDE Sysadmin
[img]content/bcooksley_sig.png[/img]
zmdmw52
Registered Member
Posts
10
Karma
0
OS
bcooksley wrote:That is it yes. However it unfortunately is of little use to developers because you are missing the Debug symbols. Please install the appropriate debugging Packages ( Qt, KDE Libs, Plasma )


[font=Trebuchet MS]I hope installation of the debugging packages (for Qt, KDE Libs & Plasma) will not affect the main components of those ?
There was a repo/zypper KDE 4.2 upgrade problem and so I was not able to install the packages; hope to fix it today & if YaST Update works, then I'll install the debug packages.[/font]


Linux User 483705
User avatar
bcooksley
Administrator
Posts
19765
Karma
87
OS
The debugging packages will have no affect on the main components. They will only be used when you decide to generate the backtraces.


KDE Sysadmin
[img]content/bcooksley_sig.png[/img]


Bookmarks



Who is online

Registered users: Bing [Bot], daret, Google [Bot], sandyvee, Sogou [Bot]