You are not logged in.

Bye Bye Plasma

vark79

Beginner

  • "vark79" started this thread

Posts: 6

  • Send private message

1

Saturday, December 15th 2007, 11:03am

Bye Bye Plasma

Hello all of you

Yesterday I installed the RC2 of KDE4. Seems to me a great piece of work..but only for about 10 minutes. I don't know what happened but Plasma crashed and now, even after a complete logout I cannot start again Plasma. Here is the complete trace of the error:

[?1034h(no debugging symbols found)
Using host libthread_db library "/lib64/libthread_db.so.1".
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
[Thread debugging using libthread_db enabled]
[New Thread 0x2b789beb4440 (LWP 6146)]
[KCrash handler]
#5 0x00002b7896d4cdfb in QRectF::contains () from /usr/lib64/libQtCore.so.4
#6 0x00002b7897d662e1 in QGraphicsTextItem::contains ()
from /usr/lib64/libQtGui.so.4
#7 0x00002b7892e06fca in Plasma::Applet::boundingRect ()
from /usr/lib64/libplasma.so.1
#8 0x00002b7892e59da4 in Plasma::Widget::update ()
from /usr/lib64/libplasma.so.1
#9 0x00002b7892e06baa in Plasma::Applet::setGeometry ()
from /usr/lib64/libplasma.so.1
#10 0x00002b7892e59f9e in Plasma::Widget::updateGeometry ()
from /usr/lib64/libplasma.so.1
#11 0x00002b7892e5a567 in Plasma::Widget::itemChange ()
from /usr/lib64/libplasma.so.1
#12 0x00002b7892e010d3 in Plasma::Applet::itemChange ()
from /usr/lib64/libplasma.so.1
#13 0x00002b7897d723f7 in QGraphicsItem::~QGraphicsItem ()
from /usr/lib64/libQtGui.so.4
#14 0x00002b7897d725de in QGraphicsTextItem::~QGraphicsTextItem ()
from /usr/lib64/libQtGui.so.4
#15 0x00002b7892e555c2 in Plasma::LineEdit::~LineEdit ()
from /usr/lib64/libplasma.so.1
#16 0x00002b7892e07952 in ?? () from /usr/lib64/libplasma.so.1
#17 0x00002b7892e02465 in Plasma::Applet::setFailedToLaunch ()
from /usr/lib64/libplasma.so.1
#18 0x00002b7892e27aca in Plasma::Corona::addContainment ()
from /usr/lib64/libplasma.so.1
#19 0x00002b7892e28052 in Plasma::Corona::loadApplets ()
from /usr/lib64/libplasma.so.1
#20 0x00002b7892b733f2 in ?? () from /usr/lib64/libkdeinit4_plasma.so
#21 0x00002b7892b75742 in ?? () from /usr/lib64/libkdeinit4_plasma.so
#22 0x00002b7892b74aba in ?? () from /usr/lib64/libkdeinit4_plasma.so
#23 0x00002b7892b74c32 in ?? () from /usr/lib64/libkdeinit4_plasma.so
#24 0x00002b7892b731be in kdemain () from /usr/lib64/libkdeinit4_plasma.so
#25 0x00002b7898f4cb54 in __libc_start_main () from /lib64/libc.so.6
#26 0x00000000004008a9 in _start ()
#0 0x00002b7898fc5670 in nanosleep () from /lib64/libc.so.6

So, if anyone can help me to bring up again my KDE4 installation I'll be very happy. Also, maybe it's a new bug and it might be interesting for developers. BTW, I am using OpenSuse 10.3 64 bit.

Cheers!

Trizt

Beginner

Posts: 2

Occupation: Developer/Programmer

  • Send private message

2

Saturday, December 15th 2007, 6:31pm

I did the same thing, installed KDE4 RC2 yesterday.
When I tried to login the second time I got the error message you describe, I didn't do so much about it, played with another user account, but I believe I know what the problem is, that you are still using the KDE3.x.x settings (see your ~/.kde), move away your current settings to another directory and I think it should work for you.

Myself I got quite disappointed on the OSX copy, had been nice if we had got something more KDEish. I felt that the configuration options got as bad as in Gnome2, just basic configuration options. I think I'll wait for 4.2 for next look, until then I think I stay with KDE3.5.8.

sunnytom

Beginner

Posts: 1

  • Send private message

3

Sunday, January 6th 2008, 11:17pm

Solve the problem with

delete /home/yourcrashedusername/home/kde4 directory or empty this dir.

KDE4 save's the crashed session but debugging or rebuilding is not implemented yet as it seems. I had the same problem after working with firefox and going to sleepmode for 10 minutes. after erasing my tmp and cache files in home/myuser/kde4 it works again fine.

it looks like that kde rc1 works more stabil than rc2 isn't it

Quoted

I think I'll wait for 4.2 for next look, until then I think I stay with KDE3.5.8.

Good idea of course but stay tuned for kde4, i feel good for the upcoming release


greez

tom

This post has been edited 2 times, last edit by "sunnytom" (Jan 6th 2008, 11:24pm)