| Summary: | sys-apps/qingy-1.0.0: non-working fluxbox keybindings | ||
|---|---|---|---|
| Product: | Gentoo Linux | Reporter: | Raphaël Droz <raphael.droz+floss> |
| Component: | Current packages | Assignee: | Gentoo Linux bug wranglers <bug-wranglers> |
| Status: | RESOLVED DUPLICATE | ||
| Severity: | normal | ||
| Priority: | High | ||
| Version: | unspecified | ||
| Hardware: | AMD64 | ||
| OS: | Linux | ||
| Whiteboard: | |||
| Package list: | Runtime testing required: | --- | |
|
Description
Raphaël Droz
2010-12-31 13:37:06 UTC
I added exec &> > /tmp/log to my .xsession One part of the problem is in the $DISPLAY definition. with qingy $DISPLAY is never :0 while application expected :0 I added a binding doing the following to fluxbox : export -p > /tmp/env,save The binding works ($DISPLAY is set to :0) That's why qingy running directly my .xsession cause problem while when I run startx I do not have any problem. I think qingy miss something from the startx wrapper when it spawns the xinit command line. When .xsession is loaded by qingy, $DISPLAY=:1 .xsession does exec fluxbox But then, in the fluxbox context, $DISPLAY=:0 that's where the problem is. And about the "Shift" modifier from comment #1, adding "loadkeys fr" in /etc/qingy/pre_GUI.sh was enough. (It may be a DirectFB kbd layout detection bug, but a separate one) I doubt qingy is the culprit here but rather the way fluxbox handles $DISPLAY environment. Duplicate of bug #348819 libX11 1.4.0 + $DISPLAY variable handling. If :\d is sent to fluxbox, it becomes :0 But, as a workaround, the following works (in .xsession) [[ -n "$DISPLAY" && $DISPLAY =~ ^:[0-9]$ ]] && export DISPLAY=$DISPLAY.0 (adds .0 to the $DISPLAY string if it only match the :\d pattern) *** This bug has been marked as a duplicate of bug 348819 *** |