Bug 158153 - Cannot enter in the KDE 4.0.1
Summary: Cannot enter in the KDE 4.0.1
Status: RESOLVED DUPLICATE of bug 159717
Alias: None
Product: plasma4
Classification: Unmaintained
Component: general (show other bugs)
Version: unspecified
Platform: unspecified Linux
: NOR crash
Target Milestone: ---
Assignee: Plasma Bugs List
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2008-02-21 12:29 UTC by Georgy Georgiev
Modified: 2008-03-25 23:26 UTC (History)
0 users

See Also:
Latest Commit:
Version Fixed In:
Sentry Crash Report:


Attachments
plasma.kcrash (1005 bytes, application/octet-stream)
2008-02-21 14:08 UTC, Georgy Georgiev
Details

Note You need to log in before you can comment on or make changes to this bug.
Description Georgy Georgiev 2008-02-21 12:29:18 UTC
Version:           0.0 (using 4.0.1 (KDE 4.0.x >=20080201) "release 12.4", compiled sources)
Compiler:          gcc
OS:                Linux (x86_64) release 2.6.22.17-0.1-default

Plasma crashed and I cannot enter in the KDE 4.0.1
Comment 1 Pino Toscano 2008-02-21 13:21:56 UTC
Can't you provide a backtrace, or a log, or anything?
A so generic problem like this without further information is totally useless.
Comment 2 Georgy Georgiev 2008-02-21 14:08:17 UTC
I can reproduce it. After reporting the bug I removed ~/.kde4 directory and can enter in KDE4. 
I reproduce it I did the following steps:
1. Start konqueror (for KDE3) and start to find in my home directory.
2. Start konqueror for KDE4.
3. restart X server by the console.
4. After login again in the KDE4 the plasma is crashed.

----- Original Message ----
From: Pino Toscano <pino@kde.org>
To: gosho_tg@yahoo.com
Sent: Thursday, February 21, 2008 2:21:57 PM
Subject: [Bug 158153] Cannot enter in the KDE 4.1   

------- You are receiving this mail because: -------
You reported the bug, or are watching the reporter.
         
http://bugs.kde.org/show_bug.cgi?id=158153         




------- Additional Comments From pino kde org  2008-02-21 13:21 -------
Can't you provide a backtrace, or a log, or anything?
A so generic problem like this without further information is totally useless.





      ____________________________________________________________________________________
Be a better friend, newshound, and 
know-it-all with Yahoo! Mobile.  Try it now.  http://mobile.yahoo.com/;_ylt=Ahu06i62sR8HDtDypao8Wcj9tAcJ 


Created an attachment (id=23648)
plasma.kcrash
Comment 3 Georgy Georgiev 2008-02-21 14:13:34 UTC
The backtrace is following:

[?1034h(no debugging symbols found)
Using host libthread_db library "/lib64/libthread_db.so.1".
(no debugging symbols found)
(no debugging symbols found)
[Thread debugging using libthread_db enabled]
[New Thread 0x2b0e30360ac0 (LWP 10830)]
[KCrash handler]
#5  0x0000000000000011 in ?? ()
#6  0x00002b0e26b5a99e in Plasma::Applet::flushUpdatedConstraints ()
   from /usr/lib64/libplasma.so.1
#7  0x00002b0e26b7f775 in Plasma::Corona::loadApplets ()
   from /usr/lib64/libplasma.so.1
#8  0x00002b0e268c39c2 in ?? () from /usr/lib64/libkdeinit4_plasma.so
#9  0x00002b0e268c5968 in ?? () from /usr/lib64/libkdeinit4_plasma.so
#10 0x00002b0e268c46c0 in ?? () from /usr/lib64/libkdeinit4_plasma.so
#11 0x00002b0e268c4822 in ?? () from /usr/lib64/libkdeinit4_plasma.so
#12 0x00002b0e268c370f in kdemain () from /usr/lib64/libkdeinit4_plasma.so
#13 0x00002b0e2cd54b54 in __libc_start_main () from /lib64/libc.so.6
#14 0x00000000004008a9 in _start ()
#0  0x00002b0e2cdcd670 in nanosleep () from /lib64/libc.so.6



      ____________________________________________________________________________________
Never miss a thing.  Make Yahoo your home page. 
http://www.yahoo.com/r/hs
Comment 4 S. Burmeister 2008-02-21 14:57:50 UTC
> [?1034h(no debugging symbols found)
> (no debugging symbols found)
> (no debugging symbols found)


A backtrace with the above lines is useless, please install the debuginfo 
packages provided by your distro in order to provide useful backtraces.
Comment 5 Rolf Eike Beer 2008-03-25 23:26:15 UTC
Marking this as dupe of the newer bug because that one has a usable backtrace

*** This bug has been marked as a duplicate of 159717 ***