Registered Member
|
[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]
[font=Trebuchet MS]What can be done to get the panel back to original state ?[/font]
Linux User 483705
|
Administrator
|
Is a new user affected by this?
KDE Sysadmin
[img]content/bcooksley_sig.png[/img] |
Registered Member
|
[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] [/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
|
Administrator
|
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] |
Registered Member
|
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
|
Administrator
|
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] |
Registered Member
|
[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
|
Administrator
|
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] |
Registered Member
|
[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
|
Administrator
|
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] |
Registered users: Bing [Bot], daret, Google [Bot], sandyvee, Sogou [Bot]