On Thu, Jul 30, 2015 at 12:24:04PM +0000, Debian Bug Tracking System wrote: > Thank you for the additional information you have supplied regarding > this Bug report. > This is an automatically generated reply to let you know your message > has been received.
Oh! Nice! > Your message is being forwarded to the package maintainers and other > interested parties for their attention; they will reply in due course. Still waiting for some not-machine-answer. So, changing to another user is not possible. Pushing anway ~/,kde daoes not make any change in the well known missbehavior. X works perfektly well: X.Org X Server 1.17.2 Release Date: 2015-06-16 X Protocol Version 11, Revision 0 Build Operating System: Linux 3.16.0-4-amd64 i686 Debian Current Operating System: Linux 9398 4.0.0-2-686-pae #1 SMP Debian 4.0.8-2 (2015-07-22) i686 Kernel command line: BOOT_IMAGE=/boot/vmlinuz-4.0.0-2-686-pae root=UUID=51052b81-aa31-419e-8bb0-8a6ca7f0b466 ro vga=0x11a quiet Build Date: 01 July 2015 05:17:45PM xorg-server 2:1.17.2-1 (http://www.debian.org/support) Current version of pixman: 0.32.6 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: Fri Jul 31 13:15:06 2015 (==) Using config file: "/etc/X11/xorg.conf" (==) Using system config directory "/usr/share/X11/xorg.conf.d" The XKEYBOARD keymap compiler (xkbcomp) reports: > Warning: Type "ONE_LEVEL" has 1 levels, but <RALT> has 2 symbols > Ignoring extra symbols Errors from xkbcomp are not fatal to the X server (II) AIGLX: Suspending AIGLX clients for VT switch stopping X: xinit: connection to X server lost waiting for X server to shut down (II) Server terminated successfully (0). Closing log file. I am thinking to kill KDE ASAP. XAB. -- To UNSUBSCRIBE, email to [email protected] with a subject of "unsubscribe". Trouble? Contact [email protected]
