consolekit is not active after running startx.
➜ ~ 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' Please help. thanks -- To unsubscribe, send mail to awesome-unsubscr...@naquadah.org.
Re: consolekit is not active after running startx.
On Sat, Jul 14, 2012 at 04:22:00PM +0800, Leiking wrote: > [...] > awesome >> ~/.awesome_stdout 2>> ~/.awesome_stderr > exec ck-launch-session awesome >> ~/.awesome_stdout 2>> ~/.awesome_stderr > [...] What do you expect? You start awesome, which then runs. And only after that instance of awesome exits, you use ck-launch-session to start awesome within a consolekit session. Simply remove the first call to awesome and that should be it. -- Gregor Best pgpC0gQ27wiVA.pgp Description: PGP signature
Re: consolekit is not active after running startx.
sorry, the first line is commented.
My config is that:
➜ ~ git:(master) ✗ cat /etc/inittab
#
# /etc/inittab: This file describes how the INIT process should set up
#the system in a certain run-level.
#
# Author: Miquel van Smoorenburg,
# Modified by: Patrick J. Volkerding,
# Modified by: Daniel Robbins,
# Modified by: Martin Schlemmer,
# Modified by: Mike Frysinger,
# Modified by: Robin H. Johnson,
#
# $Header: /var/cvsroot/gentoo-x86/sys-apps/sysvinit/files/inittab-2.87,v
1.1 2010/01/08 16:55:07 williamh Exp $
# Default runlevel.
id:3:initdefault:
# System initialization, mount local filesystems, etc.
si::sysinit:/sbin/rc sysinit
# Further system initialization, brings up the boot runlevel.
rc::bootwait:/sbin/rc boot
l0:0:wait:/sbin/rc shutdown
l0s:0:wait:/sbin/halt -dhp
l1:1:wait:/sbin/rc single
l2:2:wait:/sbin/rc nonetwork
l3:3:wait:/sbin/rc default
l4:4:wait:/sbin/rc default
l5:5:wait:/sbin/rc default
l6:6:wait:/sbin/rc reboot
l6r:6:wait:/sbin/reboot -dk
#z6:6:respawn:/sbin/sulogin
# new-style single-user
su0:S:wait:/sbin/rc single
su1:S:wait:/sbin/sulogin
# TERMINALS
#c1:12345:respawn:/sbin/agetty 38400 tty1 linux
c1:5:respawn:/sbin/agetty -a jinleileiking -8 -s 38400 tty1 linux
c2:2345:respawn:/sbin/agetty 38400 tty2 linux
c3:2345:respawn:/sbin/agetty 38400 tty3 linux
c4:2345:respawn:/sbin/agetty 38400 tty4 linux
c5:2345:respawn:/sbin/agetty 38400 tty5 linux
c6:2345:respawn:/sbin/agetty 38400 tty6 linux
# SERIAL CONSOLES
#s0:12345:respawn:/sbin/agetty 9600 ttyS0 vt100
#s1:12345:respawn:/sbin/agetty 9600 ttyS1 vt100
# What to do at the "Three Finger Salute".
ca:12345:ctrlaltdel:/sbin/shutdown -r now
# Used by /etc/init.d/xdm to control DM startup.
# Read the comments in /etc/init.d/xdm for more
# info. Do NOT remove, as this will start nothing
# extra at boot if /etc/init.d/xdm is not added
# to the "default" runlevel.
x:a:once:/etc/X11/startDM.sh
#x1:5:once:/bin/su - -- jinleileiking -l -c '/usr/bin/startx
/dev/null 2>&1'
➜ ~ git:(master) ✗
➜ ~ 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 ck-launch-session dbus-launch --sh-syntax --exit-with-session
awesome >> ~/.awesome_stdout 2>> ~/.awesome_stderr
#exec awesome >> ~/.awesome_stdout 2>> ~/.awesome_stderr
➜ ~ git:(master) ✗ cat .zprofile
# New environment setting added by Sourcery CodeBench Lite for ARM
EABI on Thu Jul 05 17:04:19 CST 2012 1.
# The unmodified version of this file is saved in
/home/jinleileiking/.zprofile2131715756.
# Do NOT modify these lines; they are used to uninstall.
PATH="/home/jinleileiking/crosstools/CodeSourcery/Sourcery_CodeBench_Lite_for_ARM_EABI/bin:${PATH}"
export PATH
# End comments by InstallAnywhere on Thu Jul 05 17:04:19 CST 2012 1.
if [[ -z $DISPLAY ]] && [[ $(tty) = /dev/tty1 ]]; then
exec startx
# Could use xinit instead of startx
#exec xinit -- /usr/bin/X -nolisten tcp vt7
fi
In grub menu, I chose 5.
Then ---> inittab 5 (loggin as jinleileiking)---> .zprofile ---> startx
But, in awesome:
➜ ~ git:(master) ✗ ck-list-sessions
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-14T09:19:58.527229Z'
login-session-id = ''
Session2:
unix-user = '1000'
realname = '(null)'
seat = 'Seat2'
session-type = ''
active = FALSE
x11-display = ':0'
x11-display-device = '/dev/tty7'
display-device = '/dev/tty1'
remote-host-name = ''
is-local = FALSE
on-since = '2012-07-14T09:20:09.346425Z'
login-session-id = ''
Session2 is not active
2012/7/14 Gregor Best :
> On Sat, Jul 14, 2012 at 04:22:00PM +0800, Leiking wrote:
>> [...]
>> awesome >> ~/.awesome_stdout 2>> ~/.awesome_stderr
>> exec ck-launch-session awesome >> ~/.awesome_stdout 2>> ~/.awesome_stderr
>> [...]
>
> What do you expect? You start awesome, which then runs. And only after that
> instance
> of awesome exits, you use ck-launch-session to start awesome within a
> consolekit
> session. Simply remove the first call to awesome and that should be it.
>
> --
> Gregor Best
--
To unsubscrib
Re: consolekit is not active after running startx.
❦ 14 juillet 2012 13:02 CEST, Leiking : > In grub menu, I chose 5. > > Then ---> inittab 5 (loggin as jinleileiking)---> .zprofile ---> startx > > > But, in awesome: > > ➜ ~ git:(master) ✗ ck-list-sessions > 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-14T09:19:58.527229Z' > login-session-id = '' > Session2: > unix-user = '1000' > realname = '(null)' > seat = 'Seat2' > session-type = '' > active = FALSE > x11-display = ':0' > x11-display-device = '/dev/tty7' > display-device = '/dev/tty1' > remote-host-name = '' > is-local = FALSE > on-since = '2012-07-14T09:20:09.346425Z' > login-session-id = '' > > Session2 is not active There was a change in console kit that did not allow a non-root user to be considered as active. This is the job of the DM to do this operation. Not all DM are able to do so. You can either use GDM3 (a very lightweight DM which pulls a window manager as a dependency) with autologin or slim (from 1.3.3 for consolekit support), with autologin as well. Another solution would be to investigate if you have the pam_ck_connector.so module which may do the same things for console users. I have it in /etc/pam.d/common-session: session optionalpam_ck_connector.so nox11 I don't know if it is enabled with your way of autologin (there is no authentication but maybe getty is calling PAM session nonetheless). -- Write and test a big program in small pieces. - The Elements of Programming Style (Kernighan & Plauger) -- To unsubscribe, send mail to awesome-unsubscr...@naquadah.org.
Re: Master width factor and with several tags
❦ 12 juillet 2012 16:42 CEST, Bryan Gardiner : >> What is the rule when we display two tags with different master width >> factors? Currently, it seems to be "random". Sometimes, I get the >> master width of the initial tag, sometimes the one of the new tag. >> >> Thanks. > > I believe the policy is to always use the layout of the left-most > active tag. That does not match what I have noticed. Therefore, I have looked at the source: local t = tag.selected(param.screen) awful.tag.selected() is advertised to return the _first_ visible tag. It uses awful.tag.selectedlist() which iterates over capi.screen[screen]:tags(). In my case, this table is not ordered correctly, hence the "undefined" behaviour I got. I think this is because I am using "sharedtags" which swaps tags between screens. -- Each module should do one thing well. - The Elements of Programming Style (Kernighan & Plauger) -- To unsubscribe, send mail to awesome-unsubscr...@naquadah.org.
Emacs not tiling to 100%
http://minus.com/l4aDzHyH0wb9i As you can see in that screenshot, emacs is not tiling to 100%, some empty space is being left on the right. I'd really really like to fix that. What should I do? Thank you. Attached are my rc.lua and my theme.lua -- David Gomes rc.lua Description: Binary data theme.lua Description: Binary data
Re: Emacs not tiling to 100%
❦ 14 juillet 2012 14:04 CEST, David Gomes : > http://minus.com/l4aDzHyH0wb9i As you can see in that screenshot, emacs is > not tiling to 100%, some empty space is being left on the right. > > I'd really really like to fix that. What should I do? You can change `size_hints_honors = true` to `size_hints_honors = false`. See this FAQ entry: http://awesome.naquadah.org/wiki/FAQ#How_to_remove_gaps_between_windows.3F -- /* Thanks to Rob `CmdrTaco' Malda for not influencing this code in any * way. */ 2.4.3 linux/net/core/netfilter.c -- To unsubscribe, send mail to awesome-unsubscr...@naquadah.org.
Re: Emacs not tiling to 100%
Didn't work. I did that, restarted awesome wm, reopened emacs, and I have the exactly same problem. On Sat, Jul 14, 2012 at 1:33 PM, Vincent Bernat wrote: > ❦ 14 juillet 2012 14:04 CEST, David Gomes : > > > http://minus.com/l4aDzHyH0wb9i As you can see in that screenshot, emacs > is > > not tiling to 100%, some empty space is being left on the right. > > > > I'd really really like to fix that. What should I do? > > You can change `size_hints_honors = true` to `size_hints_honors = > false`. See this FAQ entry: > > http://awesome.naquadah.org/wiki/FAQ#How_to_remove_gaps_between_windows.3F > -- > /* Thanks to Rob `CmdrTaco' Malda for not influencing this code in any > * way. > */ > 2.4.3 linux/net/core/netfilter.c > -- David Gomes
Re: Emacs not tiling to 100%
On Sat, Jul 14, 2012 at 01:39:16PM +0100, David Gomes wrote: > Didn't work. I did that, restarted awesome wm, reopened emacs, and I have > the exactly same problem. Are you 100% sure that rule is correctly applied to all clients? I don't see any other reason as to why Awesome might behave this way. -- Daniel Martí - mv...@mvdan.cc - GPG 0x58BF72C3 pgpCpuiwwwHZ9.pgp Description: PGP signature
Re: Emacs not tiling to 100%
awful.rules.rules = {
-- All clients will match this rule.
{ rule = { },
properties = { border_width = beautiful.border_width,
border_color = beautiful.border_normal,
focus = true,
keys = clientkeys,
buttons = clientbuttons,
size_hints_honors = false } },
{ rule = { class = "MPlayer" },
properties = { floating = true } },
{ rule = { class = "pinentry" },
properties = { floating = true } },
-- Set Firefox to always map on tags number 2 of screen 1.
-- { rule = { class = "Firefox" },
-- properties = { tag = tags[1][2] } },
}
That is the relevant part of the code, I'm pretty sure I am doing it right
:S
On Sat, Jul 14, 2012 at 1:42 PM, Daniel Martí wrote:
> On Sat, Jul 14, 2012 at 01:39:16PM +0100, David Gomes wrote:
> > Didn't work. I did that, restarted awesome wm, reopened emacs, and I have
> > the exactly same problem.
>
> Are you 100% sure that rule is correctly applied to all clients? I don't
> see any other reason as to why Awesome might behave this way.
>
> --
> Daniel Martí - mv...@mvdan.cc - GPG 0x58BF72C3
>
--
David Gomes
Re: Emacs not tiling to 100%
❦ 14 juillet 2012 15:59 CEST, David Gomes :
> awful.rules.rules = {
> -- All clients will match this rule.
> { rule = { },
> properties = { border_width = beautiful.border_width,
> border_color = beautiful.border_normal,
> focus = true,
> keys = clientkeys,
> buttons = clientbuttons,
> size_hints_honors = false } },
> { rule = { class = "MPlayer" },
> properties = { floating = true } },
> { rule = { class = "pinentry" },
> properties = { floating = true } },
> -- Set Firefox to always map on tags number 2 of screen 1.
> -- { rule = { class = "Firefox" },
> -- properties = { tag = tags[1][2] } },
> }
>
> That is the relevant part of the code, I'm pretty sure I am doing it right
> :S
This should be `size_hints_honor`.
--
Make sure input cannot violate the limits of the program.
- The Elements of Programming Style (Kernighan & Plauger)
--
To unsubscribe, send mail to awesome-unsubscr...@naquadah.org.
Re: Emacs not tiling to 100%
Excellent eye :-) That's definitely it. On Sat, Jul 14, 2012 at 05:59:53PM +0200, Vincent Bernat wrote: > > That is the relevant part of the code, I'm pretty sure I am doing it right > > :S > > This should be `size_hints_honor`. -- Daniel Martí - mv...@mvdan.cc - GPG 0x58BF72C3 pgpubK0KsNNGB.pgp Description: PGP signature
