Bug#697028: xinit: startx &, then (unneeded) bg freezes window manager
Package: xinit
Version: 1.2.0-2
Severity: normal
After starting X using "startx &" in a shell in a text console, if back in
that text console I happen to run "bg" on the startx job (which reports
"... already in background"), then when I go back to the X console, the
window manager is frozen. (For example, it doesn't change window focus per
mouse movement or update its pager.) The X server is still running otherwise
(at least enough that whatever window had focus still gets keyboard events).
(Since "bg" reported that the job is already in the background, I wouldn't
expect there to be a change in the status of the job--so I didn't expect
that the job (including the window manager or whatever) would be affected.
I also notice that if I do 'startx &' and then log off of the text console,
the window manager is also frozen. On Sarge, that didn't happen. What
changed?
Especially for the "bg" case, is there a bug somewhere in X components,
especially related to shell job control?
Daniel
-- System Information:
Debian Release: 6.0.6
APT prefers stable-updates
APT policy: (500, 'stable-updates'), (500, 'stable')
Architecture: amd64 (x86_64)
Kernel: Linux 2.6.32-5-amd64 (SMP w/4 CPU cores)
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Versions of packages xinit depends on:
ii coreutils 8.5-1 GNU core utilities
ii libc6 2.11.3-4 Embedded GNU C Library: Shared lib
ii libx11-6 2:1.3.3-4 X11 client-side library
ii x11-common 1:7.5+8+squeeze1 X Window System (X.Org) infrastruc
ii xauth 1:1.0.4-1 X authentication utility
Versions of packages xinit recommends:
ii fvwm [x-window-manager] 1:2.5.30.ds-1 F(?) Virtual Window Manager
ii vnc4server [xserver] 4.1.1+X4.3.0-37 Virtual network computing server s
ii xserver-xorg 1:7.5+8+squeeze1 the X.Org X server
ii xserver-xorg-core [xser 2:1.7.7-14 Xorg X server - core server
ii xterm [x-terminal-emula 261-1 X terminal emulator
xinit suggests no packages.
-- no debconf information
Reply to: