If I press the reboot button or logout button KDE just shows a blank black screen and hangs. It also happens if I try to reboot from the KDM login screen. If I hit the power button on my laptop the system will shutdown however.

Anyideas on how to fix this? KDE 4.4 - FC11 - nVidia drivers

Are any error messages relating to this output to ~/.xsession-errors? Do you use Desktop Effects?

How severe is the hang? Is it possible to switch to a virtual terminal?

bcooksley wrote:Are any error messages relating to this output to ~/.xsession-errors? Do you use Desktop Effects?

How severe is the hang? Is it possible to switch to a virtual terminal?

It is not possible to switch to a virtual terminal but I can use reboot or init 6 from the command line inside the gui to reboot from. If it locks up you can only press the power button to send the term signal.

Code: Select all

[tylerm@compaq Patches]$ cat ~/.xsession-errors | grep error
XRANDR error base:  177
kwrite(3153)/Kate (Scripting) KateScriptManager::collect: Script value error: No type specified in script meta data:  /usr/share/kde4/apps/katepart/script/jstest.js
error: option -s not recognized
                      <level>: none, info*, error, warn, debug (*default)   
dolphin(5055)/kio (KIOJob) KIO::SlaveInterface::dispatch: error  104   "Cannot create thumbnail for directory"
dolphin(5055)/kio (KIOJob) KIO::SlaveInterface::dispatch: error  104   "Cannot create thumbnail for directory"
dolphin(5055)/kio (KIOJob) KIO::SlaveInterface::dispatch: error  104   "Cannot create thumbnail for directory"
dolphin(5055)/kio (KIOJob) KIO::SlaveInterface::dispatch: error  104   "Cannot create thumbnail for directory"
dolphin(5055)/kio (KIOJob) KIO::SlaveInterface::dispatch: error  104   "Cannot create thumbnail for directory"
dolphin(5055)/kio (KIOJob) KIO::SlaveInterface::dispatch: error  104   "Cannot create thumbnail for directory"
dolphin(5055)/kio (KIOJob) KIO::SlaveInterface::dispatch: error  104   "Cannot create thumbnail for directory"
dolphin(15485)/kio (KIOJob) KIO::SlaveInterface::dispatch: error  104   "Cannot create thumbnail for directory"
        at org.eclipse.swt.SWT.error(Unknown Source)
        at org.eclipse.swt.SWT.error(Unknown Source)
        at org.eclipse.swt.dnd.DND.error(Unknown Source)
        at org.eclipse.swt.dnd.DND.error(Unknown Source)
        at org.eclipse.swt.SWT.error(Unknown Source)
        at org.eclipse.swt.SWT.error(Unknown Source)
        at org.eclipse.swt.dnd.DND.error(Unknown Source)
        at org.eclipse.swt.dnd.DND.error(Unknown Source)
        at org.eclipse.swt.SWT.error(Unknown Source)
        at org.eclipse.swt.SWT.error(Unknown Source)
        at org.eclipse.swt.SWT.error(Unknown Source)
        at org.eclipse.swt.widgets.Display.error(Unknown Source)
        at org.eclipse.swt.SWT.error(Unknown Source)
        at org.eclipse.swt.SWT.error(Unknown Source)
        at org.eclipse.swt.SWT.error(Unknown Source)
        at org.eclipse.swt.widgets.Display.error(Unknown Source)
        at org.eclipse.swt.SWT.error(Unknown Source)
        at org.eclipse.swt.SWT.error(Unknown Source)
        at org.eclipse.swt.SWT.error(Unknown Source)
        at org.eclipse.swt.widgets.Display.error(Unknown Source)
        at org.eclipse.swt.SWT.error(Unknown Source)
        at org.eclipse.swt.SWT.error(Unknown Source)
        at org.eclipse.swt.SWT.error(Unknown Source)
        at org.eclipse.swt.widgets.Display.error(Unknown Source)
        at org.eclipse.swt.SWT.error(Unknown Source)
        at org.eclipse.swt.SWT.error(Unknown Source)
        at org.eclipse.swt.SWT.error(Unknown Source)
        at org.eclipse.swt.widgets.Display.error(Unknown Source)


The last 100 lines of ~/.xsession-errors and /var/log/messages should likely contain the reason why this occurs...

bcooksley wrote:The last 100 lines of ~/.xsession-errors and /var/log/messages should likely contain the reason why this occurs...

I don't see anything. Should I mention I'm using XFS for the root filesystem?

The type of file system shouldn't matter to KDE. Are you using Desktop Effects? If so, try disabling them to see if there is any effect.

bcooksley wrote:The type of file system shouldn't matter to KDE. Are you using Desktop Effects? If so, try disabling them to see if there is any effect.

Did not help. I tried running kbuildsycoca --noincremental

(That did not work either)

If you start X using only the VESA driver, does this occur?

bcooksley wrote:If you start X using only the VESA driver, does this occur?

I have not messed with the new style xorg config yet. How would I simply start up with vesa?

This is what it looks like now:

Code: Select all

# Xorg configuration created by livna-config-display

Section "Files"
        ModulePath   "/usr/lib64/xorg/modules/extensions/nvidia"
        ModulePath   "/usr/lib64/xorg/modules"
EndSection

Section "ServerFlags"
        Option      "AIGLX" "on"
EndSection

Section "Device"
        Identifier  "Videocard0"
        Driver      "nvidia"
        Option      "AddARGBGLXVisuals" "True"
EndSection

Section "Extensions"
        Option      "Composite" "Enable"
EndSection


Should I simply do this?

Code: Select all

# Xorg configuration created by livna-config-display

Section "Files"
        #ModulePath   "/usr/lib64/xorg/modules/extensions/nvidia"
        #ModulePath   "/usr/lib64/xorg/modules"
EndSection

Section "ServerFlags"
        #Option      "AIGLX" "on"
EndSection

Section "Device"
        #Identifier  "Videocard0"
        Driver      "vesa"
        #Option      "AddARGBGLXVisuals" "True"
EndSection

Section "Extensions"
        #Option      "Composite" "Enable"
EndSection


I see that you are on Fedora 11 and I spent a long time on this problem
and discovered that it had nothing to do with KDE but instead with the
synaptics driver "xorg-x11-drv-synaptics-1.1.3-2". This was crashing X11
upon any kind of exit from KDE. Going back to 1.1.3-1 version resolved
the problem. The problem may be related to the use of nvidia drivers since
I use them too. I reported the problem to Fedora but not much have been done
on it, probably because it only happens for nvidia.

@Thaidog: yes, that looks correct.

@sambo57u: very interesting... never seen that cause the problem before.

bcooksley wrote:@Thaidog: yes, that looks correct.

@sambo57u: very interesting... never seen that cause the problem before.

Ok using the vesa driver I can indeed make it back to the KDM login... but I can not reboot from it. If I bring up the shutdown dialogue box and choose restart the system blacks out and hangs again until I hit my power button. From the KDE 4.4 desktop however if I choose restart from the kickoff menu I can reboot now from there. At boot up when X starts I am still getting the nVidia X flash so for some reason it looks like the nVidia module still loads...

Now that you know the vesa hack works, is there a fix?

Unfortunately this confirms that the NVidia driver contains a bug which is causing this issue.

The only way of fixing it is to report the issue to NVidia and update when they make new releases, hoping they decide to correct the issue.

Avoiding applications which use OpenGL ( such as KWin's Desktop Effects, Compiz, Google Earth and Flash in some cases ) should help avoid the issue in many cases however.

bcooksley wrote:Unfortunately this confirms that the NVidia driver contains a bug which is causing this issue.

The only way of fixing it is to report the issue to NVidia and update when they make new releases, hoping they decide to correct the issue.

Avoiding applications which use OpenGL ( such as KWin's Desktop Effects, Compiz, Google Earth and Flash in some cases ) should help avoid the issue in many cases however.

What about updating to Fedora Core 12? Was this a new bug with kde 4.4?

Yes, interesting indeed if you spend half a day tracking it down. More
interestingly changelog for the rpm that breaks says:

* Wed Dec 09 2009 Adam Jackson <ajax@redhat.com> 1.1.3-2 - synaptics-1.1.3-timer-fix.patch: Don't free the timer in DeviceOff, since that happens on VT switch. (#540248)

this seems to crash X when using nvidia driver. Perhaps related to the fact
that UseEvents is set to false in xorg.conf and I believe by default since
nvidia had a problem with this.