.Xsession-errors

[pannerrammer]

Whenever I start gdm I get this in my ~/.Xsession-errors file.

What's causing the warnings, and how do I 'clear' them? They mostly seem to be keyboard things, but am not certain. Help appreciated!


/etc/gdm/Xsession: Beginning session setup...
Setting IM through im-switch for locale=en_GB.
Start IM through /etc/X11/xinit/xinput.d/all_ALL linked to /etc/X11/xinit/xinput.d/default.
SESSION_MANAGER=local/engels:/tmp/.ICE-unix/5782
ALSA lib control.c:909:(snd_ctl_open_noupdate) Invalid CTL front:0
ALSA lib control.c:909:(snd_ctl_open_noupdate) Invalid CTL front:0
Warning: Multiple definitions of the FOUR_LEVEL_KEYPAD key type
Earlier definition ignored
expected keysym, got XF86KbdLightOnOff: line 70 of pc
last scanned symbol is: XF86KbdLightOnOff
expected keysym, got XF86KbdBrightnessDown: line 71 of pc
last scanned symbol is: XF86KbdBrightnessDown
expected keysym, got XF86KbdBrightnessUp: line 72 of pc
last scanned symbol is: XF86KbdBrightnessUp
Warning: No symbols defined for <SYRQ> (keycode 92)
Warning: No symbols defined for <II65> (keycode 101)
Warning: No symbols defined for <BRK> (keycode 114)
Warning: No symbols defined for <FK13> (keycode 118)
Warning: No symbols defined for <FK14> (keycode 119)
Warning: No symbols defined for <I7E> (keycode 254)
Warning: No symbols defined for <I7F> (keycode 255)
Shutdown failed or nothing to shut down.
xrdb: "*Label.background" on line 220 overrides entry on line 150
xrdb: "*Text.background" on line 226 overrides entry on line 191
xrdb: "*Label.foreground" on line 232 overrides entry on line 151
xrdb: "*Text.foreground" on line 238 overrides entry on line 192
Window manager warning: Failed to read saved session file /home/phil/.metacity/sessions/default0.ms: Failed to open file '/home/phil/.metacity/sessions/default0.ms': No such file or directory
seahorse nautilus module initialized
Initializing nautilus-share extension

** (nautilus:6141): WARNING **: Unable to add monitor: Not supported
PID TTY TIME CMD
5913 ? 00:00:00 pulseaudio

(gnome-display-properties:6213): display-properties-WARNING **: Creating revert dialogThanks.

[dstew]

Try reconfiguring your keyboard. Boot into Recovery Mode, and on the command line enter
sudo dpkg-reconfigure xserver-xorgThat gets you a text-based reconfiguration program that asks questions about your keyboard, mouse and display. After you are done reconfiguring, enter startx and see if it is better.

[pannerrammer]

Try reconfiguring your keyboard. Boot into Recovery Mode, and on the command line enter
sudo dpkg-reconfigure xserver-xorgThat gets you a text-based reconfiguration program that asks questions about your keyboard, mouse and display. After you are done reconfiguring, enter startx and see if it is better.

Thanks. I always hate dpkg-reconfigure as I always end up with problems. So, did it and got the usual issues (no screen). This is my original xorg.conf file


Section "InputDevice"
Identifier "Generic Keyboard"
Driver "kbd"
Option "XkbRules" "xorg"
Option "XkbModel" "pc102"
Option "XkbLayout" "gb"
EndSection

Section "InputDevice"
Identifier "Configured Mouse"
Driver "mouse"
Option "CorePointer"
EndSection

Section "Device"
Identifier "Configured Video Device"
Driver "fglrx" ****
EndSection

Section "Monitor"
Identifier "Configured Monitor"
EndSection

Section "Screen"
Identifier "Default Screen"
Monitor "Configured Monitor"
Device "Configured Video Device"
Defaultdepth 24 ****
EndSection

Section "ServerLayout"
Identifier "Default Layout"
Screen "Default Screen"
EndSection
Section "Module" ****
Load "glx" ****
EndSection ****


The lines I've marked with *** are the lines that get removed after running dpkg-reconfigure (video stuff, the kybd stuff is unaltered).

[dstew]

Do you, in fact, have a PC-102 keyboard with a Great Britain layout?

[pannerrammer]

I do indeed have a genuine IBM AT keyboard with individually sprung keys (not these bubble membrane sponges made nowadays!) dating from 1988.

However it doesn't work with my new KVM switch, so have had to replace it with a 1996 model.

Both made in Greenock, Scotland. Cost a small fortune, but it's a lovely keyboard!

So, "Yes" is the short answer!

The pc has a fresh install of Hardy, more or less settings as per 'out of the box'.

I've also got Gutsy on another pc using the same keyb/mouse/monitor combo. Set it up yesterday with pretty well the default settings. No Xsession-errors.

Have 3rd pc on the same KVM combo with Hardy, has similar Xsession-errors (though not identical) to pc1.

Have also set up laptop with Hardy (no connection to IBM keyboard). Also exhibits Xsession-errors.

[dstew]

AT this point, it sounds like a bug in the Hardy distribution. You might consider reporting it on Launchpad (https://launchpad.net/ubuntu). Anytime a piece of hardware works with an older distribution, but not with the newer, the bug-squashers like to hear about it.

For your particular case, other than direct editing of xorg.conf to try different things, I am out of ideas. Good luck.

P.S. I fondly remember the old clicking IBM pc keyboards too...