fixed and backported

*** Bug 186304 has been marked as a duplicate of this bug. ***

*** Bug 186200 has been marked as a duplicate of this bug. ***

Is there a temporary work around?

After having installed 4:4.2.1-0ubuntu1~intrepid2 I could use plasma again, but only until the next reboot. Below's the backtrace,

Rafael

----
Anwendung: Plasma-Arbeitsfläche (plasma), Signal SIGSEGV
[Current thread is 0 (LWP 6247)]

Thread 2 (Thread 0xa9b95b90 (LWP 6248)):
#0  0xb7fc5430 in __kernel_vsyscall ()
#1  0xb5878075 in pthread_cond_wait@@GLIBC_2.3.2 () from /lib/tls/i686/cmov/libpthread.so.0
#2  0xb6441bbd in pthread_cond_wait () from /lib/tls/i686/cmov/libc.so.6
#3  0xb662b6f2 in QWaitCondition::wait () from /usr/lib/libQtCore.so.4
#4  0xb7985532 in ?? () from /usr/lib/libQtNetwork.so.4
#5  0xb662a6ae in ?? () from /usr/lib/libQtCore.so.4
#6  0xb587450f in start_thread () from /lib/tls/i686/cmov/libpthread.so.0
#7  0xb6433a0e in clone () from /lib/tls/i686/cmov/libc.so.6

Thread 1 (Thread 0xb53f16c0 (LWP 6247)):
[KCrash Handler]
#6  0xb6735bba in QTimer::stop () from /usr/lib/libQtCore.so.4
#7  0xb7f5e870 in PanelView::updatePanelGeometry (this=0xa524a10) at /build/buildd/kdebase-workspace-4.2.1a/plasma/shells/desktop/panelview.cpp:543
#8  0xb7f5fa87 in PanelView::pinchContainment (this=0xa524a10, screenGeom=@0xbf9c4060) at /build/buildd/kdebase-workspace-4.2.1a/plasma/shells/desktop/panelview.cpp:689
#9  0xb7f61648 in PanelView (this=0xa524a10, panel=0xa039d78, id=1, parent=0x0) at /build/buildd/kdebase-workspace-4.2.1a/plasma/shells/desktop/panelview.cpp:243
#10 0xb7f6b376 in PlasmaApp::createView (this=0x9f588b8, containment=0xa039d78) at /build/buildd/kdebase-workspace-4.2.1a/plasma/shells/desktop/plasmaapp.cpp:619
#11 0xb7f6ba96 in PlasmaApp::containmentAdded (this=0x9f588b8, containment=0xa039d78) at /build/buildd/kdebase-workspace-4.2.1a/plasma/shells/desktop/plasmaapp.cpp:663
#12 0xb7f6bd0c in PlasmaApp::qt_metacall (this=0x9f588b8, _c=QMetaObject::InvokeMetaMethod, _id=4, _a=0xbf9c436c)
    at /build/buildd/kdebase-workspace-4.2.1a/obj-i486-linux-gnu/plasma/shells/desktop/plasmaapp.moc:96
#13 0xb672fa60 in QMetaObject::activate () from /usr/lib/libQtCore.so.4
#14 0xb67307e2 in QMetaObject::activate () from /usr/lib/libQtCore.so.4
#15 0xb7e08963 in Plasma::Corona::containmentAdded () from /usr/lib/libplasma.so.3
#16 0xb7e0a038 in Plasma::Corona::loadLayout () from /usr/lib/libplasma.so.3
#17 0xb7e0b751 in Plasma::Corona::initializeLayout () from /usr/lib/libplasma.so.3
#18 0xb7f689ad in PlasmaApp::corona (this=0x9f588b8) at /build/buildd/kdebase-workspace-4.2.1a/plasma/shells/desktop/plasmaapp.cpp:517
#19 0xb7f68b45 in PlasmaApp::setupDesktop (this=0x9f588b8) at /build/buildd/kdebase-workspace-4.2.1a/plasma/shells/desktop/plasmaapp.cpp:255
#20 0xb7f6bd3b in PlasmaApp::qt_metacall (this=0x9f588b8, _c=QMetaObject::InvokeMetaMethod, _id=2, _a=0xbf9c4668)
    at /build/buildd/kdebase-workspace-4.2.1a/obj-i486-linux-gnu/plasma/shells/desktop/plasmaapp.moc:94
#21 0xb672fa60 in QMetaObject::activate () from /usr/lib/libQtCore.so.4
#22 0xb67307e2 in QMetaObject::activate () from /usr/lib/libQtCore.so.4
#23 0xb6735db7 in ?? () from /usr/lib/libQtCore.so.4
#24 0xb6735edc in ?? () from /usr/lib/libQtCore.so.4
#25 0xb672a53f in QObject::event () from /usr/lib/libQtCore.so.4
#26 0xb69aa8ec in QApplicationPrivate::notify_helper () from /usr/lib/libQtGui.so.4
#27 0xb69b272e in QApplication::notify () from /usr/lib/libQtGui.so.4
#28 0xb771010d in KApplication::notify (this=0x9f588b8, receiver=0xa006898, event=0xbf9c4afc) at /build/buildd/kde4libs-4.2.1a/kdeui/kernel/kapplication.cpp:307
#29 0xb671ae61 in QCoreApplication::notifyInternal () from /usr/lib/libQtCore.so.4
#30 0xb6748d81 in ?? () from /usr/lib/libQtCore.so.4
#31 0xb6745520 in ?? () from /usr/lib/libQtCore.so.4
#32 0xb56b96f8 in g_main_context_dispatch () from /usr/lib/libglib-2.0.so.0
#33 0xb56bcda3 in ?? () from /usr/lib/libglib-2.0.so.0
#34 0xb56bcf61 in g_main_context_iteration () from /usr/lib/libglib-2.0.so.0
#35 0xb6745478 in QEventDispatcherGlib::processEvents () from /usr/lib/libQtCore.so.4
#36 0xb6a44ea5 in ?? () from /usr/lib/libQtGui.so.4
#37 0xb671952a in QEventLoop::processEvents () from /usr/lib/libQtCore.so.4
#38 0xb67196ea in QEventLoop::exec () from /usr/lib/libQtCore.so.4
#39 0xb671bda5 in QCoreApplication::exec () from /usr/lib/libQtCore.so.4
#40 0xb69aa767 in QApplication::exec () from /usr/lib/libQtGui.so.4
#41 0xb7f547f6 in kdemain (argc=1, argv=0xbf9c4ed4) at /build/buildd/kdebase-workspace-4.2.1a/plasma/shells/desktop/main.cpp:54
#42 0x08048712 in main (argc=) at /build/buildd/kdebase-workspace-4.2.1a/obj-i486-linux-gnu/plasma/shells/desktop/plasma_qgv_dummy.cpp:3

@Mark: look at bug 185741 comment 3 for a workaround

(In reply to comment #1)
> fixed and backported

Marco Im new here and I read and replied to bug 185741 at the end of this post. But when you say is fixed and backported why this means? I saw it before in other posts here and in Launchpad, means that changes where done to new packages and when I update will fix the problem?

@Gerard:

The current development "branch" is KDE 4.2.x (that only accepts bugfixes)
The current development "trunk" is KDE4.3.x (that accepts bugfixes and new features)

This bug being fixed in branch and trunk means that it was fixed in the KDE4.3.x code , and also in the KDE4.2.x code. So you will have to wait at least for KDE 4.2.2 (the next KDE4.2.x release) in order to get this fixed.

When KDE4.3.0 gets out,branch will be 4.3.x and trunk will be 4.4.x, and so on.

Thanks Dario for rapiud nswer! But I still cant understand, as said here https://bugs.kde.org/show_bug.cgi?id=186200#c4 how the same PLASMA CRASH BUG is repeating 3 times from Kubuntu 8.10 release, KDE 4.1.2, to KDE 4.2 RC1 and again to KDE 4.2.1. So for that I launched a QUESTION for know that IF EVERYTIME KDE UPDATES (AND PLASMA) THE SAME BUG WILL OCCUR AS THIS IS ANNOYING AND PROBABLY AN IMPEDIMENT FOR NEW OR FEW SKILLED USERS, THAT SURE CHOOSE GNOME. 

And Im saying this cause my mother's PC is infected by a viurs in Windows and I repeat her several times to migrate to Linux and TONIGHT I SHOWED HER MY KUBUNTU 8.10 but when after login plasma crushed again and she saw the CRAHS an she say that she dont want to use complicated software that crashes, waht it is perfectly UNDERSTANDABLE, more even if she doesnt inderstand english to search for help (we're spanish).

But waht is the mening o doing changes in a version that still doesnt bing published and hw can I fix NOW this? I read the workaround yu link bug 185741 comment 3 but i dont understand much and seems that, thug errors happens, TYPING "plasma" ON Konsole LOADS KDE so I RECOMMEND TO PUT THIS AS A TIP OF THE BUG REPORTING TOOL AS A PANIC SOLUTION FOR NEWBIES (as I ;))...

@Gerard: I can't see this *exact crash* (we use the backtraces to compare) in KDE 4.1.2 reports. If you experienced a Plasma crash in KDE4.1.2 so then it's probably a completely different crash/bug(within another different situation)

It can repeats from KDE4.2Rc to KDE4.2.1 because it wasn't properly fixed (or fixed at all) until now. I mean , the bug could be discovered in KDE4.2rc1 but no one could fix it (or triage it), so the bug is still on 4.2.0, and even in 4.2.1 ... And now , that the developers can take a look on it , they have fixed it for 4.2.2.

Developers are working full time and beside that they have their lifes... There are a lot to things to do in KDE and this is a big project.

We are all working on KDE stability and fixing crashes too. But software (and human beings that wrote it) aren't perfect. And there are some corner case that can trigger a crash/bug, that the developers can't reproduce (and therefore they can't fix them).

If you want to fix this know , you may try to get the source code of an stable release and try to apply the patch that fixed this issue against it, then compile it. There isn't an easy way to do that. 
Also you can run the development version (which has this bug fixed), but it's probably more unstable than the 4.2.1 stable version (as it's being developed currently)

We can't put tips on the crash handler because each crash is different an unique, and you need a human being to analyse them. (( Anyways , I'm working on that crash dialog to do it more user friendly ))

Workaround from bug 185741 comment 3 (easy way):
- Open your /home/username/.kde4/share/config/plasmarc file  (the file path may differ, I don't know which path ubuntu uses)
- Delete any line which contains the "geometry" word. This may cause you some lost of settings, but it's required.
- Save that file
- Restart your PC / KDE

(( 

Are you sure you are suffering this exact bug? are you getting the same backtrace as the original report??

#6  0xb66aabba in QTimer::stop () from /usr/lib/libQtCore.so.4
#7  0xb7ed3870 in PanelView::updatePanelGeometry (this=0x85a3d78) at

))

Thanks
Regards. Darío

PLASMA CRASH, from many BACKTRACES, it's all the SAME to me and the SAME ERROR AT ALL. I was very excited for KDE thinkin was SUPERIOR to GNOME IN SATBIBLITY but after every crash Iv been losse it AND NOW IT ONLY EXCEEDS IT IN FUNCTIONS...

Yeah I appreciate all that work but understand that when a crash is repeatin 3 times during updates that makes me loose my patience.

"And there are some corner case that can trigger a crash/bug, that the developers can't reproduce (and therefore they can't fix them)."

corner case? what means? sorry but my english isnt perfect, if youre spaniard
translte me please as some words dont appear in WordReference and is difficult read posts here..Thanks for explanations, I understand a bit more that vast and complex and amazing world of FREE SOFTWARE..;)

"If you want to fix this know , you may try to get the source code of an stable
rlease and try to apply the patch that fixed this issue against it"

You mean the PATCH IS THE WORKAROUND here bug 185741 ?

"Also you can run the development version (which has this bug fixed), but it's
probably more unstable than the 4.2.1 stable version (as it's being developed
currently)"

What is "Development Version"? I search in http://en.wikipedia.org/wiki/Software_release_life_cycle but don't appear. Can you reccomend me a place to DOCUMENT ME of that spacific thechnic terms? But if you say that fixed plasma crashes but continue bieng unstable...

TIP, yeah in the prev post Rafael typed plasma in konsole and didnt worked, but does for me, is that you mean? But if there is a chance of temporaly fix, IT CAN HELP PEOPLE. It would be somethig like: "A FATAL ERROR OCCURRED (PLASMA HAS CRASHED), YOU CAN REPORT THE BACKTRACE TO KDE BUGS AND TRY TO FIX IT TEMPORALY OPENING A CONSOLE (KONSOLE) WITH CTRL+ALT F2 AND TYPING PLASMA IN IT TO TRY TO LOAD IT"

Geometry means SCREEN GEOMETRY? mmm.., that has something to do with the bug reported here of everytime starts KDE sets screen resolution to MAX ?

I had  succes by simply removing
~/.kde/share/config/plasmarc

My configuration was almost not affected, and it is a lot easier.

gerard: people are more likely to help you if you stop screaming :P  (ie, don't type in all caps)

I'm not even going to read the rest of what you wrote, it's too painful with all the yelling...

BTW: Gerard: I already mailed you in Spanish explaning all. :)

DARIO-->If I remember well, I deleted PLASMAPPLETSRC when plasma crushed in KDE 4.1.3 or 4.2RC1. But I LOST all the FAST START ICONS on the PANEL. Besides, as I like BIG ICONS, the space for the SYSTEM TRAY? in wich PROGRAMS appear MINIMIZED where TOO SMALL, so I created another panel and move it up ala GNOME. Like this, though take away a bit of the visible screen when BROWSING, I have more SPACE to VIEW my minimized apps up and Ive more space to ADD more fast start icons in the lower panel. THEN, IF I DELETE what YOU or MARK say I LOSE all that CONFIGURATION?

Besides I said if that issue had something to do with the SREEN RESOLUTION SET TO MAX evertytmie kde LOADs as you sai mo to delete SCREEN GEOMETRY lines.

CHANI--> Well, Id know that question would be asked me one day... ;P but I ve to tell you that you that youre MISTAKEN. First: Im not SCREAMING, Im TYPING ;P and I know that equivalence in FORUMS. Second: I dont write all in CAPS, if you READ CAREFULLY I only write in caps the WORDS i want to EMPHASIZE for when I ended to write my message and other can VIEW FAST reading that CAPS you HATE and FAST he KNOWS what the post is talkin about as this isnt a FORUM and there isnt any TEXT FORMATTING tool, like BOLDS, that I often use.This is specially USEFUL, when REPLYING a LONG POST that you dont want to READ COMPLETELY... LOGICAL UH? But If you and OTHERS AGREE with you that FEEL ALL THAT PAIN (Jesus...) when Reply me tell me that and I wont use it anymore.

If you just remove the "Geometry" lines you will not lost ALL your configuration.. only the Geometry one

> Besides I said if that issue had something to do with the SREEN RESOLUTION SET
> TO MAX evertytmie kde LOADs as you sai mo to delete SCREEN GEOMETRY lines.
> 

Yes, this crash/bug has a relation with the screen resolution and the panel geometry.

> CHANI--> Well, Id know that question would be asked me one day... ;P but I ve
> to tell you that you that youre MISTAKEN. First: Im not SCREAMING, Im TYPING ;P

It's also irritating here, please don't do that.

> and I know that equivalence in FORUMS. Second: I dont write all in CAPS, if you

Instead of writing long texts, you can write small ones.
I already told you: this isn't a friendly place for newbies. 
And please, answer my mail instead of posting here. Thanks

Im usinf Firefox 3 now instead Knoqueror and dont apper the buuton reply why?
Well Dario:

If you just remove the "Geometry" lines you will not lost ALL your
configuration.. only the Geometry one

> Besides I said if that issue had something to do with the SREEN RESOLUTION SET
> TO MAX evertytmie kde LOADs as you sai mo to delete SCREEN GEOMETRY lines.
> 

Yes, this crash/bug has a relation with the screen resolution and the panel
geometry.

Then If I delete it the screen res set to MAX will be fixed too? And what about the solution maded by Mark? (removing ~/.kde/share/config/plasmarc His configuration was almost not affected, and it is a lot easier he said) I dont know what is teh best option...

> CHANI--> Well, Id know that question would be asked me one day... ;P but I ve
> to tell you that you that youre MISTAKEN. First: Im not SCREAMING, Im TYPING ;P

It's also irritating here, please don't do that.

Appears that neither u and Chani understand it, and youre so smart for this, IM NO DOING IT FOR YELLING OK? IM DOING IT TO EMPHASIZE THE WORDS AS IT IS DIFFICULT FOR ME WRITING IN INGLISH ! JESUS! But if you both cant understand this OK MAn Ill write all without CAPs..

> and I know that equivalence in FORUMS. Second: I dont write all in CAPS, if you

Instead of writing long texts, 

Heyeyey wait a moment, LONG TEXTS? If I write long texts is for Ive too much things to QUESTION and I like to ARGUE it with ARGUMENTS for you UNDERRSTAND me better! Im doing all that for GOOD and Chani and you are CRITICIZE me all the time ! Have you look your reply to me? Its even larger than mine! Do you know that Ive SPENT HOURS TRYING TO WRITE CORRECTLY HERE IN ENGLISH ?!

you can write small ones.

What? This is INCREDIBLE, youre saying me that dont ask waht I need to ask? Your saing me that Ive to SHUT UP? I cant BELIEVE it..

I already told you: this isn't a friendly place for newbies. 

Yeah I know that from Launchpad as I reply on ur email, but Im not so NEWBIE,as I was registered in Launchpad from January...And Iwas thinkin that PROGRAMMERS WERE MORE FRIENDLY PEOPLE, OBVIOUSLY i WAS MISTAKEN, PROBABLY CAUSE U ARNT PAID FOR UR WORK?...and then You talk about all that SHIT of FREE SOFTWARE and blabla...and u CAN CONTRIBUTE BLABLABLA...and wen I REGISTER, TRANSLATE AND SPENT HOURS WRITNG HERE YOU SAY ME THAT I SHUT UP AND DONT POST HERE? Is that u saing me? Well that Im TIRED of this and all yuour MANIAS. Precisely casue some are NEWBIES that we dont KNOW things and we WANT to know and colaborate and If we post here and we found all this COLDNESS we then WONT COLLABORATE A SHIT ! And u must have to test software.

And please, answer my mail instead of posting here. Thanks

Are u an ADMIN here? or do u like to do orders? no CAP writing, no LONG texts, and now Ive to mail u instead of postin here? Would be better to put all of this after registering isnt it? Yeah I read ur email and answered it, and you started to LIKE me and, since you said all that FASCIST CRAP, CONFLICTING with FREE SOFTWARE THINKING. EVEN MICROSOFT Sites are more FRIENDLY THAN HERE, PERHAPS CAUSE HIS PROGRAMMERS EARNS MONEY,,AND I DONT KNOW IF YOU EARN SOMETING. Everyday Im more CLEAR that Im gonna change to GNOME and I hope GNOME BUGS, if there is, were better than that as Im gona INFORM ME NOW. AND I WRITE HERE TO ALL KNOW THAT AND REPPLY ME IF THEY WANT CASUE IM NOT NOBODY TO SAY OTHERS WHAT TO DO...IM REALLY REALLY FREE, AND FREEDOM SOMETIMES MEANS TELL EHAT U THINK AND IF IT DOESNT IM NOT GONNA POST HERE ANYMORE, IM NOT COMFORTABLE...AND THE U CROITICISE MICROSOFT? AT LEAST IF I PAY I OBTAIN DECENT HELP! WAHT A HUGE DISAPPOINTMENT...

You see Chani? Can u red all that? THAT IS THE DIFFERENCE OF WRITING SOME WORDS OR ALL IN CAPS ! Something done when somenone is ANGRY WHEN OTHERS TRY TO CENSURE IT REPETEADLY, someting that u and Dario ACHIEVED...

Besides I add Chewry or Rafel posts isnt large eh Dario? My God...

Gerard. This is enough now. Stop this stupid ranting and remove the caps lock button from your keyboard.

Bugzilla is a bug reporting tool and the issue reported by Per Cherwy is now fixed.

So unless you have new elements or are suffering from the same issue, please refrain from posting here.

If you want some user support, use your distribution own forums.

OK Cristophe, perhaps I got carried by ANGER, but I think that this isnt stupid as is totally understandable when someone has so many problems with KDE and when trying to get help in a diffrnt language somoene dont understand him and put  handicaps. In fact CAPS are more EASY TO VIEW THAN NORMAL LETTERS isnt? But I follow your advice...

I thought bugzilla was reporting tool from Mozilla, not KDE and If u read my posts I suffer from same issue. In the BEGGINING of RANTING POST i SAID:

< Im usinf Firefox 3 now instead Knoqueror and dont apper the buuton reply why?
Well Dario:

If you just remove the "Geometry" lines you will not lost ALL your
configuration.. only the Geometry one

> Besides I said if that issue had something to do with the SREEN RESOLUTION SET
> TO MAX evertytmie kde LOADs as you sai mo to delete SCREEN GEOMETRY lines.
> 

Yes, this crash/bug has a relation with the screen resolution and the panel
geometry.

Then If I delete it the screen res set to MAX will be fixed too? And what about
the solution maded by Mark? (removing ~/.kde/share/config/plasmarc His
configuration was almost not affected, and it is a lot easier he said) I dont
know what is teh best option...>

Ill follow ur advice, Ill search for forums...

Created attachment 31935 [details]
Plasma Crash Backtrace no valid

Created attachment 31936 [details]
KDE BUG MANAGER snapshot showing the impossibility of create a valid backtrace (in spanish)

Dario Ive replied ur email and Im so sorry for my ranting here but so many errors were STRONGER than me, and some PERSONAL difficulties too...Im HUMAN and sometimes seems that all difficulties happen at time but as human I ADMIT my ERROR. So if you want reply me to previous question, I appreciate that.

Today I turn on PC and has the same crash. Ive open /home/gerard/.kde (not .kde4)/share/config plasmarc and I find that GEOMETRY line: geometry[$d] I dont know what it is and I think that here isnt the problem. But then crolling down I found: 

[PlasmaViews][1][Sizes][Horizontal1152]
max=1152,38
min=1024,38
offset=0
size=1152,38

so I open the other file: plasma-appletsrc, that Launchpad users said me in previous plasma crashes and found something like:

[Containments][27]
activity=
desktop=-1
formfactor=2
geometry=0,-126,1024,38
immutability=1
location=3
plugin=panel
screen=0
zvalue=150

[Containments][27][Applets][32]
geometry=0,0,1002,32
immutability=1
plugin=tasks
zvalue=621

and more...so I think that perhaps u refered to plasma-appletsrc intead of plasmarc.

KDE Bug manager said that cant create a good BACKTRACE, sais that is for the packages (it is for Kubuntu problems yu said me on email?) or for the STACK has CORRUPTED. Both things I dont understand...:(
I select all the text and attached and a snapshot of KDE MANGER BUG if not that would be interminable ! Seems that the line you said me here https://bugs.kde.org/show_bug.cgi?id=186324#c10 is the same:

#6  0xb6860bba in QTimer::stop () from /usr/lib/libQtCore.so.4

but I didnt find the other:

#7  0xb7ed3870 in PanelView::updatePanelGeometry (this=0x85a3d78) at /build/buildd/kdebase-workspace-4.2.1a/plasma/shells/desktop/panelview.cpp:543

And how can I have the same line as Rafael if my backtrace is not correct ?
I know I commited and error (KDE has many ;)) and I want to IMPROVE (less caps than prevs posts ;))

*** Bug 186649 has been marked as a duplicate of this bug. ***

*** Bug 186624 has been marked as a duplicate of this bug. ***

*** Bug 186668 has been marked as a duplicate of this bug. ***

Janathan: sorry for duplication, i looked here on first lines of backtrace, they were different in mine, so ive started another bug. I hadn't saw that later backtraces are the same.

I see one, propably important think with that bug. I doesn't happens on ati's fglrx drivers for me, but happens on xf86-video-ati and radeonhd drivers compiled from GIT.
I dont have time to test all driver/kde-version combinations, but im also sure that it didnt happened on xf86-video-radeonhd (newest, not from git) on 4.2.0, on the same system.

*** Bug 186714 has been marked as a duplicate of this bug. ***