Anybody know the solution?? 2012/7/16 Leiking <jinleileik...@gmail.com>: > waiting expert to solve it ... > > 2012/7/16 Leiking <jinleileik...@gmail.com>: >> I tryed this. Althoght the seat is active, but awesome seems not work well. >> >> meta + 1 2 3 is not responding.... >> >> -_-####. >> >> >> 2012/7/15 Renato Botelho <rbga...@gmail.com>: >>> On Sat, Jul 14, 2012 at 5:22 AM, Leiking <jinleileik...@gmail.com> wrote: >>>> ➜ ~ git:(master) ✗ cat .xinitrc >>>> #!/bin/sh >>>> #export XMODIFIERS="@im=ibus" >>>> #export GTK_IM_MODULE="ibus" >>>> #export QT_IM_MODULE="xim" >>>> >>>> xrdb ~/.Xresources >>>> >>>> export XMODIFIERS=@im=fcitx >>>> export GTK_IM_MODULE=fcitx # 或者是xim,取决于你是否编译了对应的输入法模块 >>>> export QT_IM_MODULE=fcitx # 或者是xim,取决于你是否编译了对应的输入法模块 >>>> #eval `dbus-launch --sh-syntax --exit-with-session` >>>> >>>> #xrandr --output LVDS1 --primary >>>> #xrandr --output VGA1 --mode 1280x1024 --right-of LVDS1 >>>> xrandr --output LVDS1 --primary --mode 1366x768 --output VGA1 --mode >>>> 1280x1024 --right-of LVDS1 >>>> #exec ck-launch-session dbus-launch --sh-syntax --exit-with-session >>>> awesome >> ~/.awesome_stdout 2>> ~/.awesome_stderr >>>> exec ck-launch-session awesome >> ~/.awesome_stdout 2>> ~/.awesome_stderr >>>> >>>> #exec awesome >> ~/.awesome_stdout 2>> ~/.awesome_stderr >>>> >>>> ➜ ~ git:(master) ✗ ck-list-sessions >>>> Session5: >>>> unix-user = '1000' >>>> realname = '(null)' >>>> seat = 'Seat5' >>>> session-type = '' >>>> active = FALSE >>>> x11-display = ':0' >>>> x11-display-device = '/dev/tty8' >>>> display-device = '/dev/tty1' >>>> remote-host-name = '' >>>> is-local = FALSE >>>> on-since = '2012-07-14T08:11:52.554923Z' >>>> login-session-id = '' >>>> Session1: >>>> unix-user = '1000' >>>> realname = '(null)' >>>> seat = 'Seat1' >>>> session-type = '' >>>> active = FALSE >>>> x11-display = '' >>>> x11-display-device = '' >>>> display-device = '/dev/tty1' >>>> remote-host-name = '' >>>> is-local = TRUE >>>> on-since = '2012-07-14T07:56:10.440619Z' >>>> login-session-id = '' >>>> idle-since-hint = '2012-07-14T08:12:17.578563Z' >>> >>> I had this same issue after move to fedora 17. The workaround i found >>> was to run (if you are on tty1): >>> >>> # startx -- vt01 >>> >>> There is a proposed patch on redhat's bugzilla to make startx adding >>> the vtNN automatically. >>> >>> Regards >>> -- >>> Renato Botelho
-- To unsubscribe, send mail to awesome-unsubscr...@naquadah.org.