Using ctrl-alt-F# keys crashes KDE and X.

Dear visitor, welcome to KDE-Forum.org. If this is your first visit here, please read the Help. It explains in detail how this page works. To use all features of this page, you should consider registering. Please use the registration form, to register here or read more information about the registration process. If you are already registered, please login here.

ant

Beginner

Posts: 11

Location: An Ant Farm

Occupation: Worker Ant

Monday, March 10th 2008, 2:49am

Using ctrl-alt-F# keys crashes KDE and X.

Hello,

I am having a crash problem with my KDE v3.5.8 crashing X to console (I use startx command when booting up Debian). Anyways, I think I had this problem for months and maybe a year, but finally figured out the pattern to reproduce it.

Basically in KDE, I go to virtual desktop 2, 3, or 4 (I have four set up). If I press ctrl-alt-F1 (or any other console screens) keys to go back to console/text mode, then KDE and X crash. I can reproduce this easily. If I am in virtual desktop #1, then no crash.

I have two logs from X: http://pastebin.ca/936064 and I hope these help! Any ideas on what's the problem and how to fix it? Thank you in advance.

Ant @ The Ant Farm (http://antfarm.ma.cx) and Ant's Quality Foraged Links (http://aqfl.net).

Go to the top of the page

ant

Beginner

Posts: 11

Location: An Ant Farm

Occupation: Worker Ant

Tuesday, March 11th 2008, 5:31am

RE: Using ctrl-alt-F# keys crashes KDE and X.

OK I reproduced it without KDE, so it is not KDE's fault!

I basically loaded up GKrellM2 (doesn't matter if it uses defaults or customized) with gkrellm-hdplop plugin running only on ONE virtual desktop in KDE v3.5 or Gnome v2. Then, I switched to another virtual desktop that didn't have GKrellM on screen.

Then, I pressed ctrl-alt-F# (# is a number like 1) to go back to console/text mode. It resulted a X crash like:
Backtrace:
0: /usr/bin/X11/X(xf86SigHandler+0x81) [0x80c89c1]
1: [0xffffe420]
2: /usr/bin/X11/X [0x81771e0]
3: /usr/bin/X11/X [0x814a8ba]
4: /usr/bin/X11/X [0x814b504]
5: /usr/bin/X11/X [0x8154c1e]
6: /usr/bin/X11/X(Dispatch+0x1a1) [0x808eff1]
7: /usr/bin/X11/X(main+0x47e) [0x8076e2e]
8: /lib/i686/cmov/libc.so.6(__libc_start_main+0xe0) [0xb7dc5450]
9: /usr/bin/X11/X(FontFileCompleteXLFD+0x1e9) [0x80761b1]

Fatal server error:
Caught signal 11. Server aborting

If I disable this plugin, then I won't get the crash. This plugin is so cool to have. I am just wondering if I am the only one with this problem. :(

Thanks in advance. :)

Ant @ The Ant Farm (http://antfarm.ma.cx) and Ant's Quality Foraged Links (http://aqfl.net).

This post has been edited 1 times, last edit by "ant" (Mar 11th 2008, 5:31am)

Go to the top of the page

ant

Beginner

Posts: 11

Location: An Ant Farm

Occupation: Worker Ant

Wednesday, March 12th 2008, 4:06am

OK, it is definitely not KDE's fault.

Just a follow-up. I am starting to think this is NVIDIA's fault. I went
back to nv driver by renaming /etc/X11/xorg.conf and run startx. I tried
to reproduce the problem and no crash with gkrellm-hdplop plugin!

I will stop posting updates in here unless I find evidences it is related to KDE. Thanks for reading.

Ant @ The Ant Farm (http://antfarm.ma.cx) and Ant's Quality Foraged Links (http://aqfl.net).

Go to the top of the page