KDE crashing and returning to login screen with Mag2

[DiBosco]

I'm finding that on the machine I upgraded to Mageia 2 every now and again it will drop out of KDE with no warning and return me to the login screen. Has anyone else come across this? The machine is a homebrew i5 with a dual monitor nvidia card set-up. I had problems with flash completely crashing the M1 installation at the start, but after a while this went away, I guess due to a software upgrade at some point.

[doktor5000]

Nothing at the bottom of ~/.xsession-errors about that issue?

[wintpe]

I used to have this when i upgraded mandriva to mageia1 and as Doktor pointed out to me
my old .kde4 directory may be responcible, well he was right after clearing it the problem disappeared.

regards peter

[DiBosco]

Folks,

I have no .xsession-errors file or directory and I have only one .kde directory. I deleted the old one as I had a lot of weirdness going on with my desktop when I first did the M2 installation.

[DiBosco]

It's done it four times this afternoon. Am on the verge of going back to M1 here. Would be grateful for any other suggestions. Definitely would not recommend M2 over M1.

[doktor5000]

I think you're using Nouveau driver, this happened to me today too (as i forgot to restart Xserver or reboot after adding nvidia driver)
Actually with Mageia 1 the nouveau driver did the same thing, and even more often, maybe you only don't remember anymore ...
Please show the outout of

Code: Select all

grep -i driver /var/log/Xorg.0.log

and the output of

Code: Select all

rpm -qa | grep nvidia

and maybe

Code: Select all

urpmq --list-media active

Just fire up drakx11 if you have nonfree repo enabled already, select your graphics card, say Yes to the question about proprietary driver and then Ok and logoff or reboot.

[DiBosco]

I don't think I am using nouveau. I tried it at first to see what it was like these days, but the whole system was quite sluggish, so I used the nvidia one instead.

Code: Select all

[robertw@localhost ~]$ grep -i driver /var/log/Xorg.0.log
[    48.719] (WW) Hotplugging is on, devices using drivers 'kbd', 'mouse' or 'vmmouse' will be disabled.
[    48.719]    X.Org Video Driver: 11.0
[    48.719]    X.Org XInput driver : 13.0
[    48.720] (II) Loading /usr/lib/xorg/modules/drivers/v4l_drv.so
[    48.720]    ABI class: X.Org Video Driver, version 11.0
[    49.171]    Module class: X.Org Video Driver
[    49.171] (II) v4l driver for Video4Linux
[    49.171] (II) NVIDIA dlloader X Driver  295.49  Mon Apr 30 23:31:55 PDT 2012
[    49.171] (II) NVIDIA Unified Driver for all Supported NVIDIA GPUs
[    51.349] (II) NVIDIA(0): [DRI2]   VDPAU driver: nvidia
[    51.399]    Module class: X.Org XInput Driver
[    51.399]    ABI class: X.Org XInput driver, version 13.0
[    51.399] (II) Using input driver 'evdev' for 'Power Button'
[    51.411] (II) Using input driver 'evdev' for 'Power Button'
[    51.412] (II) No input driver specified, ignoring this device.
[    51.412] (II) No input driver specified, ignoring this device.
[    51.412] (II) No input driver specified, ignoring this device.
[    51.412] (II) No input driver specified, ignoring this device.
[    51.412] (II) No input driver specified, ignoring this device.
[    51.413] (II) No input driver specified, ignoring this device.
[    51.413] (II) No input driver specified, ignoring this device.
[    51.413] (II) No input driver specified, ignoring this device.
[    51.413] (II) Using input driver 'evdev' for 'ATEN CS1784'
[    51.413] (II) Using input driver 'evdev' for 'ATEN CS1784'
[    51.414] (II) No input driver specified, ignoring this device.
[    51.414] (II) Using input driver 'evdev' for 'Eee PC WMI hotkeys'

Code: Select all

[robertw@localhost ~]$ rpm -qa | grep nvidia
nvidia-current-doc-html-295.49-2.mga2.nonfree
dkms-nvidia-current-295.49-2.mga2.nonfree
nvidia-current-kernel-server-latest-295.49-4.mga2.nonfree
nvidia-current-kernel-3.3.6-server-2.mga2-295.49-4.mga2.nonfree
x11-driver-video-nvidia-current-295.49-2.mga2.nonfree

Code: Select all

[robertw@localhost ~]$ urpmq --list-media active
core media
Core Release (distrib1)
Core Updates (distrib3)
Nonfree Release (distrib11)
Tainted Release (distrib21)

[DiBosco]

After doing a Google search for KDE 4.8.2 crashing (as that's what is happening really I think - it's not taking down the machine, just the desktop) I have tried turning off effects. I'll let you know whether that helps in a few days' time.

[DiBosco]

OK, several days later and all runs perfectly. Even running Second Life on one monitor with a broswer runnig video and a avi playing in mplayer on the other monitor it works fine. So, I would say, if you're having problems with KDE throwing you out, just trying turning off desktop effects. They're silly anyway. ;~)

[DiBosco]

Well, would you believe it. A few minutes after posting it's all ok, it crashed. So, back to square one. Think I will go back to M1.

[yankee495]

My MGA2 kwin window decorator crashes on log out. Only with certain theme.

Code: Select all

Application: KDE Window Decorator (kde4-window-decorator), signal: Segmentation fault
Using host libthread_db library "/lib64/libthread_db.so.1".
[KCrash Handler]
#6  0x00007fd23c5ad0e9 in QRasterWindowSurface::~QRasterWindowSurface() () from /usr/lib64/libQtGui.so.4
#7  0x00007fd23c5ad169 in QRasterWindowSurface::~QRasterWindowSurface() () from /usr/lib64/libQtGui.so.4
#8  0x00007fd23c5c582e in ?? () from /usr/lib64/libQtGui.so.4
#9  0x00007fd23c3fb7a9 in ?? () from /usr/lib64/libQtGui.so.4
#10 0x00007fd23c3fb8fe in QWidgetPrivate::deleteExtra() () from /usr/lib64/libQtGui.so.4
#11 0x00007fd23c3fbb2c in QWidgetPrivate::~QWidgetPrivate() () from /usr/lib64/libQtGui.so.4
#12 0x00007fd23c3fbe39 in QWidgetPrivate::~QWidgetPrivate() () from /usr/lib64/libQtGui.so.4
#13 0x00007fd23d03bd10 in QObject::~QObject() () from /usr/lib64/libQtCore.so.4
#14 0x00007fd23c3fdb7d in QWidget::~QWidget() () from /usr/lib64/libQtGui.so.4
#15 0x00007fd23c3fddb9 in QWidget::~QWidget() () from /usr/lib64/libQtGui.so.4
#16 0x00007fd23c980445 in ?? () from /usr/lib64/libQtGui.so.4
#17 0x00007fd23bb93ec1 in __run_exit_handlers () from /lib64/libc.so.6
#18 0x00007fd23bb93f45 in exit () from /lib64/libc.so.6
#19 0x00007fd23bb7e334 in __libc_start_main () from /lib64/libc.so.6
#20 0x0000000000409e65 in _start ()

I still don't know why...something with the theme I guess.

But hang in there...You can't fix it if you don't keep and study it.

I gave similar advice a while back. The OP was glad they did.

Hang on, help is on it's way (Old Little River Band song).

If you look around all of this is not Mageia's fault. Some is changes to KDE4.

And eye candy.

[DiBosco]

I'm not blaming Mageia at all. However, I use the computer all day every working day for work, I can't have it crashing and losing work.

[yankee495]

I'm not blaming Mageia at all. However, I use the computer all day every working day for work, I can't have it crashing and losing work.

I found it was me, and my theme. Not saying it is your fault. Only try to isolate it. What was the difference from all is ok to it crashed?


All I lost was settings on log out. No work. I do think it is KDE and I have been a KDE man from the start.

It has some quirks I have not seen. One for example. Add Widget: Instant messaging presence. Every since I removed it, if I add it back, it has no icon. I can add 10 and they are all invisible.

Dok, I'll do a bug report when I catch the thing.

[yankee495]

I would say not "guess", but find out why. Long story short. I have never had a flawless Linux install. There was always something I had to google (Generic=look up). Even when I found the answer I wanted to know why?

So I could fix it again if I needed to. If it is a work machine then put something you trust on it. I trusted 2010.2 until I done the updates on my desktop and it went stupid. Then it was ok. Why? Don't know but it runs like a show room demo!

My MGA2 on my laptop, crashes at log out? Why? Don't know. But I know Oxygen theme fixes it. Why? Don't know.

I have backups on two machines with Win7, 2010.2, MGA2. Two large dogs, an 8 week old kitten, two year old cat that kills squirrels...he is just mean...and they walk on my keyboard so I can only guess at times.

A little humor here too, but for real. The kitten (kabob) tries to log in as root.

No joke. And, like Dok said...3D eyecandy stuff is fun...but not worth loosing work over. My Compiz works on my 2010 but is not stable on MGA2. The KDE bug reports reflect that, search for "pager".

I am only trying to help with a smile. Usually I have problems, ask for help, then figure it out.

[yankee495]

I should add...In Windows, a blue screen, wham, and there you are, starting over...is usually a driver, BAD RAM, Overheated CPU or corrupt hard drive.

I have found that in Linux it is not that easy, either it works or it don't.

Small history: Old man, retired (award winning) football coach (80+), called me his computer was "starting over". The dirt on the heatsink looked like carpet.

If your machine is clean, cool, runs on something else...I would suggest like Dok. Turn off what you don't need and start from there.

I have been going to ask why does a (theme) picture cause a log out crash?

Try basic theme...for real.

[doktor5000]

I have been going to ask why does a (theme) picture cause a log out crash?

Themes are nowadays not only pictures, there are binary engines which also have to do with window decoration and such stuff.
So if something goes wrong, it can kill your xserver or something like that. Absolutely silly, yes - but that's the present situation.

You may want to change to vanilla-kde4-config for troubleshooting reasons, which is also documented in Errata: https://wiki.mageia.org/en/Mageia_2_Err ... ace_Issues


BTW: For the plasmoid issues you described, you can try running the telepathy thingie in

Code: Select all

plasmoidviewer

in a terminal, where you might get more verbose feedback and possible error messages.