Bug#586515: x11-xkb-utils: Gnome login pops up error and loses changes to keyboard map

[Greg Kochanski]

Package: x11-xkb-utils
Version: 7.5+2
Severity: normal


On login, I get an error pop-up which contains the following
recommendation:
If you report this situation as a bug, please include:
- The result of xprop -root | grep XKB
- The result of gconftool-2 -R /desktop/gnome/peripherals/keyboard/kbd
And, then when I log in, I find that my caps-lock key is no longer
mapped to ctrl.

* No obvious errors appear in /var/log/Xorg.0.log
* Keyboard is a Maxim KB200PC
* This worked for a while (i.e. last few months)

$ xprop -root | grep XKB
_XKB_RULES_NAMES_BACKUP(STRING) = evdev, pc104, us, , 
_XKB_RULES_NAMES(STRING) = evdev, pc104, us, , 
$

$ gconftool-2 -R /desktop/gnome/peripherals/keyboard/kbd
layouts = []
options = [ctrl ctrl:nocaps]
model = 
$

$ cat .xsession_errors
/etc/gdm/Xsession: Beginning session setup...
x-session-manager[9388]: WARNING: Could not parse desktop file 
/home/gpk/.config/autostart/xfce4-tips-autostart.desktop: Key file does not 
have key 'Name'
x-session-manager[9388]: WARNING: could not read 
/home/gpk/.config/autostart/xfce4-tips-autostart.desktop
x-session-manager[9388]: WARNING: Could not parse desktop file 
/home/gpk/.config/autostart/xfconf-migration-4.6.desktop: Key file does not 
have key 'Name'
x-session-manager[9388]: WARNING: could not read 
/home/gpk/.config/autostart/xfconf-migration-4.6.desktop
x-session-manager[9388]: WARNING: Could not parse desktop file 
/home/gpk/.config/autostart/bluetooth-applet.desktop: Key file does not have 
key 'Name'
x-session-manager[9388]: WARNING: could not read 
/home/gpk/.config/autostart/bluetooth-applet.desktop
x-session-manager[9388]: WARNING: Could not parse desktop file 
/home/gpk/.config/autostart/xfce4-settings-helper-autostart.desktop: Key file 
does not have key 'Name'
x-session-manager[9388]: WARNING: could not read 
/home/gpk/.config/autostart/xfce4-settings-helper-autostart.desktop
GNOME_KEYRING_CONTROL=/tmp/keyring-hIPal4
GNOME_KEYRING_PID=9450
GNOME_KEYRING_CONTROL=/tmp/keyring-hIPal4
GNOME_KEYRING_CONTROL=/tmp/keyring-hIPal4
SSH_AUTH_SOCK=/tmp/keyring-hIPal4/ssh
Errors encountered in /tmp/filedN5AXC; not compiled.
Window manager warning: Failed to read saved session file 
/home/gpk/.config/metacity/sessions/106e67817c6c0de97d12770236006025070093880026.ms:
 Failed to open file 
'/home/gpk/.config/metacity/sessions/106e67817c6c0de97d12770236006025070093880026.ms':
 No such file or directory

** (gnome-settings-daemon:9449): WARNING **: Could not activate the XKB 
configuration

(polkit-gnome-authentication-agent-1:9478): GLib-GObject-WARNING **: cannot 
register existing type `_PolkitError'

(polkit-gnome-authentication-agent-1:9478): GLib-CRITICAL **: 
g_once_init_leave: assertion `initialization_value != 0' failed

** (bluetooth-applet:9484): WARNING **: Could not open RFKILL control device, 
please verify your installation
shm_open() failed: No such file or directory
beagled will run in the background.
Use beagle-status to check progress of beagled.
For log files check /home/gpk/.beagle/Log/current-Beagle.


(gnome-settings-daemon:9449): GdkPixbuf-CRITICAL **: 
gdk_pixbuf_format_get_name: assertion `format != NULL' failed
** (update-notifier:9485): DEBUG: error during dbus call: The name 
org.debian.apt was not provided by any .service files

Couldn't find a suitable icon theme to migrate to at 
/usr/lib/xfce4/xfconf-migration/xfconf-migration-4.6.pl line 324.

(nautilus:9469): GdkPixbuf-CRITICAL **: gdk_pixbuf_format_get_name: assertion 
`format != NULL' failed

MCS-Xfconf settings migration complete

16
Failure: Module initalization failed
new binding F12
Got accel 65481, 0, 0
Got keycode 96
Got modmask 0
Warn: Inotify watches may be too low (8192) for some users!  Increase it to at 
least 65535 by setting fs.inotify.max_user_watches in /etc/sysctl.conf
Debug: Starting Inotify threads
Debug: Using utf8 encoding for filenames
Got Event! 33, -1
$



$ cat /var/log/Xorg.0.log
X.Org X Server 1.7.7
Release Date: 2010-05-04
X Protocol Version 11, Revision 0
Build Operating System: Linux 2.6.32.14-dsa-ia32 i686 Debian
Current Operating System: Linux desk 2.6.32-5-686 #1 SMP Tue Jun 1 04:59:47 UTC 
2010 i686
Kernel command line: BOOT_IMAGE=/boot/vmlinuz-2.6.32-5-686 
root=UUID=b698ca7f-9513-46a3-8690-6020385f550b ro quiet
Build Date: 03 June 2010  04:08:50PM
xorg-server 2:1.7.7-2 (Julien Cristau jcris...@debian.org) 
Current version of pixman: 0.16.4
Before reporting problems, check http://wiki.x.org
to make sure that you have the latest version.
Markers: (--) probed, (**) from config file, (==) default setting,
(++) from command line, (!!) notice, (II) informational,
(WW) warning, (EE) error, (NI) not implemented, (??) unknown.
(==) Log file: /var/log/Xorg.0.log, Time: Sun Jun 20 05:50:12 2010
(==) Using config file: /etc/X11/xorg.conf
(==) Using system config directory /usr/share/X11/xorg.conf.d
(==) No Layout section.  Using the first Screen section.
(**) 

Bug#302685: An explanation

[Greg Kochanski]

The problem turned out to be a mixture of two
causes:
1) A bug in my .bash_profile, and
2) a vulnerability in X (a design flaw).

In my .bash_profile, I had lines in the form of

set line_oriented_history=on

These lines should have been in my .inputrc, instead.
When placed in .bash_profile, they changed the shell's
positional parameters.

Now, the X scripts like /etc/X11/Xsession and /etc/kde3/kdm/Xsession
have a serious design flaw.They pass important information
around in the positional parameters through the point where
my .bash_profile is sourced.

So, X sets $1 and runs /etc/kde3/kdm/Xsession.
/etc/kde3/kdm/Xsession sources $HOME/.bash_profile  (around line 10).
X uses $1  (/etc/X11/Xsession sources
/etc/X11/Xsession.d/20x11-common_process-args
which uses $1)

There is probably no legitimate reason for a .bash_profile
to change $1 (though human ingenuity is always surprising),
so I consider this a bug in the Xsession scripts.


--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]

Bug#230173: /usr/X11R6/bin/xclock: It's behind the time, on average.

[Greg Kochanski]

Package: xbase-clients
Version: 4.2.1-12.1
Severity: minor
File: /usr/X11R6/bin/xclock

When xclock updates the display, it updates to the current
time.   Then it waits (for 1 minute, by default).
At the end of the minute, xclock is 1 minute slow.

Thus, on average, xclock is 30 seconds behind the times.

If xclock updated the time so that it was half of the update
interval *ahead* of real time, then at the end of the
interval it would be only 30s slow,
and it would be correct, on average.

I noticed this at midnight, on New Year's.
Looked like a bloody fool, when the big high-tech
computer clock was still reading 11:59, while everyone
was making noise and toasting.

Also, these days, we can probably afford the CPU cycles
to update the xclock face more often, say once every 10 seconds,
by default.

-- System Information:
Debian Release: testing/unstable
Architecture: i386
Kernel: Linux gpk 2.4.23 #2 Sun Dec 7 11:46:58 GMT 2003 i686
Locale: LANG=C, LC_CTYPE=C

Versions of packages xbase-clients depends on:
ii  cpp-3.2   1:3.2.3-9  The GNU C preprocessor
ii  libc6 2.3.2.ds1-10   GNU C Library: Shared libraries an
ii  libdps1   4.2.1-12.1 Display PostScript (DPS) client li
ii  libfreetype6  2.1.7-1.1  FreeType 2 font engine, shared lib
ii  libncurses5   5.3.20030719-5 Shared libraries for terminal hand
ii  libxaw7   4.2.1-12.1 X Athena widget set library
ii  xlibmesa3-gl [libgl1] 4.2.1-12.1 Mesa 3D graphics library [XFree86]
ii  xlibmesa3-glu [libglu1]   4.2.1-12.1 Mesa OpenGL utility library [XFree
ii  xlibs 4.2.1-12.1 X Window System client libraries

-- no debconf information