Red Hat Bugzilla – Bug 860634
firstboot sets DISPLAY so no need to use "WM --display"
Last modified: 2013-10-14 06:46:58 EDT
Created attachment 617523 [details]
Description of problem:
Firstboot fails to start openbox and will fail to start other
(yet unsupported) WM's that do not support the --display option either.
It would be better if firstboot set DISPLAY=:9 for the WM process
instead of using --display=:9 which is not supported by many
window managers. Otherwise it would be better not to start
a window manager since "openbox --display" crashes immediately anyway.
And in fact for most users firstboot works well enough without
In fact since the DISPLAY envvar is already set in frontend.py
--display is redundant and can be dropped. The attached patch
Version-Release number of selected component (if applicable):
Steps to Reproduce:
1. install LXDE
2. boot to firstboot
3. Go to a VC and check openbox process status.
4. Click on user account buttons to popup windows.
3. openbox crashed at startup [defunct] due to unsupported --display option.
4. windows not decorated
3. window managers that don't support --display not to crash
4. popup windows to be handled by WM.
I tested metacity, xfwm4, openbox, and xmonad with the --display option dropped and they all work find in firstboot. (I can test kwin later.)
This package has changed ownership in the Fedora Package Database. Reassigning to the new owner of this component.
The firstboot utility is deprecated and no longer developed in Fedora 19 and newer releases. It was replaced by the initial-setup utility with a completely different codebase. If you still have any similar problems with Fedora 19 or later, please file a new bug against initial-setup or gnome-initial-setup if you did a GNOME install.