Hello,
I have been with KDE4 for a few weeks and I had always kept it up-to-date with the factory version without any problems.
Yesterday I upgraded to KDE 4.1.1, but since then, I get stuck with the splash screen when signing on. Ctrl+Esc delivers no window, but I can log off normally after Ctrl+Alt+Del.
KDE3 works fine on the same machine.
Does anyone have a good idea what I could do?
Thanks!
don’t know for sure if it will work or not but log into kde 3.5 rename the .kde4 log out and try logging into kde 4 again
Hello,
unfortunately, after renaming .kde4, the problem is the same.
Also, when I log on as root, it has exactly the same result…
Try running updates in the kde4.1 repo again, there are some there now, I’m running it myself.
Unfortunately, it doesn’t seem to help much.
I have, in the meantime, created a new user, and here is a part of the content of .xsession-errors I get when trying to start KDE 4.1.1 with this user. Maybe some of you can understand its content…
…]
b80bc000-b80d7000 r-xp 00000000 08:05 229356 /lib/ld-2.8.so
b80d7000-b80d8000 r–p 0001a000 08:05 229356 /lib/ld-2.8.so
b80d8000-b80d9000 rw-p 0001b000 08:05 229356 /lib/ld-2.8.so
bf9c3000-bf9d6000 rwxp bffeb000 00:00 0 [stack]
bf9d6000-bf9d8000 rw-p bfffe000 00:00 0
ffffe000-fffff000 r-xp 00000000 00:00 0 [vdso]
Plasma crashed, attempting to automatically recover
X Error of failed request: BadWindow (invalid Window parameter)
Major opcode of failed request: 128 (SHAPE)
Minor opcode of failed request: 6 (X_ShapeSelectInput)
Resource id in failed request: 0x1600003
Serial number of failed request: 6346
Current serial number in output stream: 6375
libxcb: WARNING! Program tries to lock an already locked connection,
which indicates a programming error.
There will be no further warnings about this issue.
QObject: Do not delete object, ‘unnamed’, during its event handler!
startkde: Shutting down…
klauncher: Exiting on signal 1
KWrited überwacht Gerät /dev/pts/1
startkde: Running shutdown scripts…
startkde: Done.
It seems that you need KDE3 as some GUI.
The part that you pasted shows mess where Plasma is trying to recover from crash, but startkde is shutting GUI down anyway. It is usually after Xorg crash. The same behavior with a new user login points in that direction.
BTW, avoid using root user when you have problem to log in. A bug that can be fixed can mess your system (if it already didn’t).
It would be good to know what graphic card and driver you are using?
I know that nvidia guys are fixing their drivers. I’m currently running latest Beta from ftp://download.nvidia.com/XFree86/Linux-x86_64/177.70 (compiled yesterday) . It still has some bugs as desktop effects are turned off by kwin (a window manager).
I’m having the same problem. The system was working (NVIDIA 177.70, but same drivers for over a week working fine) until a recent KDE 4.1 update.
But it apparently is a driver issue. I went back to 177.13 and it works now…
Dear Rajko,
what you say is correct, I’m now back at KDE3. KDE4 is dead for me for the time being.
My graphics card is ATI Mobility Radeon X1600, not Nvidia.
When logging on in KDE4, I have somehow managed to look at the task list, and Plasma seems to be running, but the display is completely unuseable. And I can start plasma in KDE3 - I don’t know whether it’s a good idea to do, but it works…
Rajko gave me the correct hint - even though I don’t have a Nvidia card, but also for the ATI card, updating the driver helps.
I have done that, now it works perfectly. I’d never have thought that the reason might be here. So, thanks Rajko.
Herr Klugbeisser wrote:
>
> Rajko gave me the correct hint - even though I don’t have a Nvidia card,
> but also for the ATI card, updating the driver helps.
>
> I have done that, now it works perfectly. I’d never have thought that
> the reason might be here. So, thanks Rajko.
>
>
It is known problem.
It seems that KDE4 is using graphic card functions not used by KDE3, so
Nvidia and ATI guys have to implement and/or debug that. It appears to be a
lot of work, so we should be patient for a while, and keep up to date both
graphic card drivers and KDE4.
While I like KDE4, I test it and defend in any occassion, I still use KDE3
as main workhorse. KDE4 is still in heavy development and settings are
changing from time to time creating problems.
BTW, I recommend, for time being, to create another user and log in that
account only with KDE4. Any problems with KDE4 will stay there. Such setup
is OK for forums, web mail etc, where small number of files is created on
user’s computer, and can be easily copied to another user. With 1 GB RAM
and more it is possible to log in both at the same time, which is useful
for debugging.
–
Regards, Rajko
mikedl wrote:
>
> But it apparently is a driver issue. I went back to 177.13 and it works
> now…
>
Interesting.
I have seen some reports that 177.67 or 177.68 work fine.
Latest rpm is 177.14, so one more back should do it.
I got to see change log, before I try it 
–
Regards, Rajko
Rajko M. wrote:
> mikedl wrote:
>
>> But it apparently is a driver issue. I went back to 177.13 and it works
>> now…
>
> Interesting.
> I have seen some reports that 177.67 or 177.68 work fine.
>
> Latest rpm is 177.14, so one more back should do it.
>
> I got to see change log, before I try it
>
So, looking again for 177.13 to see the difference to 177.70 I got no luck.
There is no such version.
Where did you found it?
–
Regards, Rajko
Rajko M. wrote:
>So, looking again for 177.13 to see the difference to >177.70 I got no luck.
>There is no such version.
>Where did you found it?
A google search for “177.13” returns several results although I do not know which are still live.
mikedl wrote:
> “177.13”
OK. Found.
I was looking the ftp server:
ftp://download.nvidia.com/XFree86/Linux-x86_64/
while Google points to this page:
http://www.nvidia.com/object/linux_display_ia32_177.13.html
I have to check nvidia forums.
OK. There are some parameters for xorg.conf:
http://www.nvnews.net/vbulletin/showthread.php?s=9ac5f0a4b0fcd34076acd511f5cbdef3&t=118088
–
Regards, Rajko
don’t know for sure if it will work or not but log into kde 3.5 rename the .kde4 log out and try logging into kde 4 again