mustermann, max | 29 Jul 19:01 2015

changing border settings results in no noticeable effect, despite the theme and cfg works

hello.

i want to change the border settings of my theme. but when i do, nothing 
happens - whatever value i choose. changing other theme values is 
noticable, so the theme and cfg at all are working properly. what can i 
do to find the preventing factor? of course i changed my terminator cfg 
to allow borders.

=> the border is not visible at all

Does someone have an advice for me?

regards

Johannes Graumann | 29 Jul 00:16 2015
Picon

awsome and kde(4/5) - network-manager etc.

Hi,

I returned to awesome and am wrestling with an old issue: how to get the 
plasmoid goodness of kde integrated in the otherwise brilliant window 
manager. When starting kontact etc. all s in order and the corresponding 
icon shows up in the awesome status bar. What I am missing, however, is a 
way to use non-app plasmoids such as the network-manager widget, the 
keyboard layout switcher, battery status etc. integrated (without having to 
add additional (gnome)-components such as nm-widget).

Thank you for any hint.

Sincerely, Joh

Jayson Willson | 28 Jul 10:46 2015
Picon

Applying commits from master to 3.5 branch

Hello everybody.
I have tried to apply some commits from "master" git branch to "3.5" and 
I have an error during compilation. Commits:
d8b73de7397bb3293637acbe64a84d8e0fbf9086
996f6785a885349855a1233113ba092816175843
d9b1d5490cd0ef18578d969153ecab1f9e1f53a5
19137a55c3c2c80d77f7d9993292acc3784cbe35
372d12ee316e665107b335b850e93e93e9094b33
e2562227ab8f123a526cf0a1478c2d37d25d1e02
7d88aebbf912d449402458d0563497f6f73087fb
f50ed9a1e8a665868e4c2cfb5cc9b65c36866a14
835c13bd8054ce11fcc84b94537b0f9da6726aad
594c01dc361d17d88dacae61efaef28c1705e8ef
After resolving git conflicts (which was easy!), I get the following 
compilation error:
Linking C executable awesome
CMakeFiles/awesome.dir/xkb.c.o: In function `event_handle_xkb_notify':
xkb.c:190: undefined reference to `globalconf_get_lua_State'
collect2: error: ld returned 1 exit status

Could you please help me to resolve this problem? Thank you.

Alfredo Palhares | 23 Jul 03:39 2015
Picon

xbacklight does not work when called from awesome

Hello everyone, 

I am trying to xall xbacklight from awesome, with the following commands:

```lua
awful.key({ }, "XF86MonBrightnessDown", function ()
    awful.util.spawn("xbacklight -dec 15") end),
awful.key({ }, "XF86MonBrightnessUp", function ()
    awful.util.spawn("xbacklight -inc 15") end),
```

But I always get this "No outputs have backlight property", calling the commands from the command line works.

Do you have any ideas ?

--

-- 
Alfredo Palhares
GPG/PGP Key Fingerprint
68FC B06A 6C22 8B9B F110
38D6 E8F7 4D1F 0763 CAAD
Gregor Mahnic | 18 Jul 13:05 2015
Picon

Trying to set up awesome on two identical monitors.

Hello,

I have not been active much and that is because I have not been using awesome in the past year or so. Now though I want to get back to using it especially now that I have a double monitor set up on my desktop PC. 

The first thing is that while browsing the webpage: Using Multiple Screens - awesome I noticed that the link to the stupid.sh script to be dead. Since every one keeps linking us back to this page I figured this may need to corrected. It says that it simplifies in the due process of picking the correct refresh rate for my monitors. Maybe there is some other way?

I am not using a graphic card. The two AOC I2267Fwh monitors are connected to the computer via HDMI cables. 

  • Size21.5"
  • Resolution1920x1080 <at> 60Hz
Best regards!


Hacksign | 8 Jul 08:07 2015
Picon

Screen Display move fast from right to left once lock screen with dm-tool

Hi there,
      I use lightdm-gtk-greeter as my login manager.
      Once I locked my screen with 'dm-tool lock', and try to light my 
monitor up again, graphic on monitor flashes (graphics on my laptop 
monitor moves very fast from right to left).
      But monitor on my HDMI port can display normally.
      If I input my username and password correctly, the laptop monitor 
just blank, I have to use 'xrandr --output eDP1 --off & xrandr --output 
eDP1 --auto' light it up again

     any on knows how it happens ?

below is my lightdm log:
[root <at> XSign lightdm]# cat lightdm.log
[+0.00s] DEBUG: Logging to /var/log/lightdm/lightdm.log
[+0.00s] DEBUG: Starting Light Display Manager 1.14.0, UID=0 PID=273
[+0.00s] DEBUG: Loading configuration dirs from 
/usr/share/lightdm/lightdm.conf.d
[+0.00s] DEBUG: Loading configuration dirs from 
/usr/local/share/lightdm/lightdm.conf.d
[+0.00s] DEBUG: Loading configuration dirs from 
/etc/xdg/lightdm/lightdm.conf.d
[+0.00s] DEBUG: Loading configuration from /etc/lightdm/lightdm.conf
[+0.00s] DEBUG: Using D-Bus name org.freedesktop.DisplayManager
[+0.00s] DEBUG: Registered seat module xlocal
[+0.00s] DEBUG: Registered seat module xremote
[+0.00s] DEBUG: Registered seat module unity
[+0.01s] DEBUG: Monitoring logind for seats
[+0.01s] DEBUG: New seat added from logind: seat0
[+0.01s] DEBUG: Loading properties from config section SeatDefaults
[+0.01s] DEBUG: Seat seat0: Starting
[+0.01s] DEBUG: Seat seat0: Creating greeter session
[+0.01s] DEBUG: Seat seat0: Creating display server of type x
[+0.01s] DEBUG: Could not run plymouth --ping: Failed to execute child 
process "plymouth" (No such file or directory)
[+0.01s] DEBUG: Using VT 7
[+0.01s] DEBUG: Seat seat0: Starting local X display on VT 7
[+0.01s] DEBUG: DisplayServer x-0: Logging to /var/log/lightdm/x-0.log
[+0.01s] DEBUG: DisplayServer x-0: Writing X server authority to 
/run/lightdm/root/:0
[+0.01s] DEBUG: DisplayServer x-0: Launching X Server
[+0.01s] DEBUG: Launching process 285: /usr/sbin/X :0 -seat seat0 -auth 
/run/lightdm/root/:0 -nolisten tcp vt7 -novtswitch
[+0.01s] DEBUG: DisplayServer x-0: Waiting for ready signal from X server :0
[+0.01s] DEBUG: Acquired bus name org.freedesktop.DisplayManager
[+0.01s] DEBUG: Registering seat with bus path 
/org/freedesktop/DisplayManager/Seat0
[+0.07s] DEBUG: Loading users from org.freedesktop.Accounts
[+0.07s] DEBUG: User /org/freedesktop/Accounts/User1000 added
[+1.71s] DEBUG: Got signal 10 from process 285
[+1.71s] DEBUG: DisplayServer x-0: Got signal from X server :0
[+1.71s] DEBUG: DisplayServer x-0: Connecting to XServer :0
[+1.73s] DEBUG: Seat seat0: Display server ready, starting session 
authentication
[+1.73s] DEBUG: Session pid=337: Started with service 'lightdm-greeter', 
username 'lightdm'
[+1.74s] DEBUG: Session pid=337: Authentication complete with return 
value 0: Success
[+1.74s] DEBUG: Seat seat0: Session authenticated, running command
[+1.74s] DEBUG: Session pid=337: Running command 
/usr/sbin/lightdm-gtk-greeter
[+1.74s] DEBUG: Creating shared data directory /var/lib/lightdm-data/lightdm
[+1.74s] DEBUG: Session pid=337: Logging to /var/log/lightdm/x-0-greeter.log
[+1.76s] DEBUG: Activating VT 7
[+1.76s] DEBUG: Activating login1 session c1
[+1.76s] DEBUG: Seat seat0 changes active session to c1
[+1.76s] DEBUG: Session c1 is already active
[+1.89s] DEBUG: Session pid=337: Greeter connected version=1.14.0 
resettable=false
[+1.96s] DEBUG: Session pid=337: Greeter start authentication for hacksign
[+1.96s] DEBUG: Session pid=360: Started with service 'lightdm', 
username 'hacksign'
[+1.96s] DEBUG: Session pid=360: Got 1 message(s) from PAM
[+1.96s] DEBUG: Session pid=337: Prompt greeter with 1 message(s)
[+1276.89s] DEBUG: Session pid=337: Greeter start authentication
[+1276.89s] DEBUG: Session pid=360: Sending SIGTERM
[+1276.89s] DEBUG: Session pid=509: Started with service 'lightdm', 
username '(null)'
[+1276.89s] DEBUG: Session pid=360: Terminated with signal 15
[+1276.89s] DEBUG: Session: Failed during authentication
[+1276.89s] DEBUG: Seat seat0: Session stopped
[+1276.90s] DEBUG: Session pid=509: Got 1 message(s) from PAM
[+1276.90s] DEBUG: Session pid=337: Prompt greeter with 1 message(s)
[+1279.95s] DEBUG: Session pid=337: Greeter start authentication for 
hacksign
[+1279.95s] DEBUG: Session pid=509: Sending SIGTERM
[+1279.95s] DEBUG: Session pid=510: Started with service 'lightdm', 
username 'hacksign'
[+1279.95s] DEBUG: Session pid=509: Terminated with signal 15
[+1279.95s] DEBUG: Session: Failed during authentication
[+1279.95s] DEBUG: Seat seat0: Session stopped
[+1279.96s] DEBUG: Session pid=510: Got 1 message(s) from PAM
[+1279.96s] DEBUG: Session pid=337: Prompt greeter with 1 message(s)
[+1282.87s] DEBUG: Session pid=337: Continue authentication
[+1282.88s] DEBUG: Session pid=510: Authentication complete with return 
value 0: Success
[+1282.88s] DEBUG: Session pid=337: Authenticate result for user 
hacksign: Success
[+1282.88s] DEBUG: Session pid=337: User hacksign authorized
[+1282.89s] DEBUG: Session pid=337: Greeter sets language en_US.utf8
[+1282.91s] DEBUG: Writing /home/hacksign/.dmrc
[+1282.93s] DEBUG: Session pid=337: Greeter requests session awesome
[+1282.94s] DEBUG: Writing /home/hacksign/.dmrc
[+1282.95s] DEBUG: Seat seat0: Stopping greeter; display server will be 
re-used for user session
[+1282.95s] DEBUG: Session pid=337: Sending SIGTERM
[+1282.97s] DEBUG: Session pid=337: Greeter closed communication channel
[+1282.97s] DEBUG: Session pid=337: Exited with return value 0
[+1282.97s] DEBUG: Seat seat0: Session stopped
[+1282.97s] DEBUG: Seat seat0: Greeter stopped, running session
[+1282.97s] DEBUG: Registering session with bus path 
/org/freedesktop/DisplayManager/Session0
[+1282.97s] DEBUG: Session pid=510: Running command 
/etc/lightdm/Xsession awesome
[+1282.97s] DEBUG: Creating shared data directory 
/var/lib/lightdm-data/hacksign
[+1282.97s] DEBUG: Session pid=510: Logging to .xsession-errors
[+1282.98s] DEBUG: Activating VT 7
[+1282.98s] DEBUG: Activating login1 session c2
[+1282.98s] DEBUG: Seat seat0 changes active session to c2
[+1282.98s] DEBUG: Session c2 is already active
[+1363.82s] DEBUG: Seat seat0: Locking
[+1363.82s] DEBUG: Seat seat0: Creating greeter session
[+1363.82s] DEBUG: Seat seat0: Creating display server of type x
[+1363.82s] DEBUG: Using VT 8
[+1363.82s] DEBUG: Seat seat0: Starting local X display on VT 8
[+1363.82s] DEBUG: DisplayServer x-1: Logging to /var/log/lightdm/x-1.log
[+1363.82s] DEBUG: DisplayServer x-1: Writing X server authority to 
/run/lightdm/root/:1
[+1363.82s] DEBUG: DisplayServer x-1: Launching X Server
[+1363.82s] DEBUG: Launching process 1386: /usr/sbin/X :1 -seat seat0 
-auth /run/lightdm/root/:1 -nolisten tcp vt8 -novtswitch
[+1363.82s] DEBUG: DisplayServer x-1: Waiting for ready signal from X 
server :1
[+1364.28s] DEBUG: Seat seat0 changes active session to
[+1364.65s] DEBUG: Got signal 10 from process 1386
[+1364.65s] DEBUG: DisplayServer x-1: Got signal from X server :1
[+1364.65s] DEBUG: DisplayServer x-1: Connecting to XServer :1
[+1364.65s] DEBUG: Seat seat0: Display server ready, starting session 
authentication
[+1364.65s] DEBUG: Session pid=1417: Started with service 
'lightdm-greeter', username 'lightdm'
[+1364.66s] DEBUG: Session pid=1417: Authentication complete with return 
value 0: Success
[+1364.66s] DEBUG: Seat seat0: Session authenticated, running command
[+1364.66s] DEBUG: Session pid=1417: Running command 
/usr/sbin/lightdm-gtk-greeter
[+1364.66s] DEBUG: Creating shared data directory 
/var/lib/lightdm-data/lightdm
[+1364.66s] DEBUG: Session pid=1417: Logging to 
/var/log/lightdm/x-1-greeter.log
[+1364.66s] DEBUG: Activating VT 8
[+1364.66s] DEBUG: Locking login1 session c2
[+1364.66s] DEBUG: Activating login1 session c3
[+1364.66s] DEBUG: Seat seat0 changes active session to c3
[+1364.66s] DEBUG: Session c3 is already active
[+1364.73s] DEBUG: Session pid=1417: Greeter connected version=1.14.0 
resettable=false
[+1365.33s] DEBUG: Session pid=1417: Greeter start authentication for 
hacksign
[+1365.33s] DEBUG: Session pid=1441: Started with service 'lightdm', 
username 'hacksign'
[+1365.33s] DEBUG: Session pid=1441: Got 1 message(s) from PAM
[+1365.33s] DEBUG: Session pid=1417: Prompt greeter with 1 message(s)
[+1370.63s] DEBUG: Session pid=1417: Continue authentication
[+1370.65s] DEBUG: Session pid=1441: Authentication complete with return 
value 0: Success
[+1370.65s] DEBUG: Session pid=1417: Authenticate result for user 
hacksign: Success
[+1370.65s] DEBUG: Session pid=1417: User hacksign authorized
[+1370.65s] DEBUG: Session pid=1417: Greeter sets language en_US.utf8
[+1370.67s] DEBUG: Session pid=1417: Greeter requests session awesome
[+1370.67s] DEBUG: Seat seat0: Returning to existing user session hacksign
[+1370.67s] DEBUG: Unlocking login1 session c2
[+1370.68s] DEBUG: Activating VT 7
[+1370.68s] WARNING: Error using VT_WAITACTIVE 7 on /dev/console: 
Interrupted system call
[+1370.68s] DEBUG: Seat seat0: Stopping greeter
[+1370.68s] DEBUG: Session pid=1417: Sending SIGTERM
[+1370.68s] DEBUG: Activating login1 session c2
[+1370.68s] DEBUG: Session pid=1441: Exited with return value 0
[+1370.68s] DEBUG: Seat seat0: Session stopped
[+1370.69s] DEBUG: Session pid=1417: Greeter closed communication channel
[+1370.69s] DEBUG: Session pid=1417: Exited with return value 0
[+1370.69s] DEBUG: Seat seat0: Session stopped
[+1370.69s] DEBUG: Seat seat0: Stopping display server, no sessions 
require it
[+1370.69s] DEBUG: Sending signal 15 to process 1386
[+1371.15s] DEBUG: Seat seat0 changes active session to c2
[+1371.15s] DEBUG: Session c2 is already active
[+1371.40s] DEBUG: Process 1386 exited with return value 0
[+1371.40s] DEBUG: DisplayServer x-1: X server stopped
[+1371.40s] DEBUG: Releasing VT 8
[+1371.40s] DEBUG: DisplayServer x-1: Removing X server authority 
/run/lightdm/root/:1
[+1371.40s] DEBUG: Seat seat0: Display server stopped

below is my greeter log:
[root <at> XSign lightdm]# cat x-0-greeter.log
** Message: Starting lightdm-gtk-greeter 2.0.1 (May 26 2015, 08:48:40)
** Message: [Configuration] Reading file: 
/etc/lightdm/lightdm-gtk-greeter.conf

** (lightdm-gtk-greeter:343): WARNING **: [PIDs] Failed to execute 
command: upstart

(lightdm-gtk-greeter:343): GLib-GObject-WARNING **: The property 
GtkWidget:margin-left is deprecated and shouldn't be used anymore. It 
will be removed in a future version.

(lightdm-gtk-greeter:343): GLib-GObject-WARNING **: The property 
GtkWidget:margin-right is deprecated and shouldn't be used anymore. It 
will be removed in a future version.

(lightdm-gtk-greeter:343): GLib-GObject-WARNING **: The property 
GtkImage:stock is deprecated and shouldn't be used anymore. It will be 
removed in a future version.

(lightdm-gtk-greeter:343): GLib-CRITICAL **: g_variant_get_type: 
assertion 'value != NULL' failed

(lightdm-gtk-greeter:343): GLib-CRITICAL **: 
g_variant_type_is_subtype_of: assertion 'g_variant_type_check (type)' failed

(lightdm-gtk-greeter:343): GLib-CRITICAL **: g_variant_get_boolean: 
assertion 'g_variant_is_of_type (value, G_VARIANT_TYPE_BOOLEAN)' failed

(lightdm-gtk-greeter:343): GLib-CRITICAL **: g_variant_unref: assertion 
'value != NULL' failed

below is a log I don't know what it is, but looks like a log from Xorg 
server:
[root <at> XSign lightdm]# cat x-0.log

X.Org X Server 1.17.2
Release Date: 2015-06-16
X Protocol Version 11, Revision 0
Build Operating System: Linux 4.0.4-2-ARCH x86_64
Current Operating System: Linux XSign 4.0.7-2-ARCH #1 SMP PREEMPT Tue 
Jun 30 07:50:21 UTC 2015 x86_64
Kernel command line: BOOT_IMAGE=/boot/vmlinuz-linux 
root=UUID=372ccd03-2b93-4c0c-ac40-25459cbcbed8 rw quiet
Build Date: 30 June 2015  09:00:12PM

Current version of pixman: 0.32.6
     Before reporting problems, check http://wiki.x.org
     to make sure that you have the latest version.
Markers: (--) probed, (**) from config file, (==) default setting,
     (++) from command line, (!!) notice, (II) informational,
     (WW) warning, (EE) error, (NI) not implemented, (??) unknown.
(==) Log file: "/var/log/Xorg.0.log", Time: Wed Jul  8 13:22:38 2015
(==) Using config directory: "/etc/X11/xorg.conf.d"
(==) Using system config directory "/usr/share/X11/xorg.conf.d"
(II) AIGLX: Suspending AIGLX clients for VT switch

Uli Schlachter | 4 Jul 15:58 2015
Picon

Re: How to change mouse cursor size ?

Am 04.07.2015 um 19:26 schrieb Hacksign:
> added Xcursor.size: 64 in ~/.Xresources, but no any effect.

Is this applied?

Does xrdb -merge ~/.Xresources and then restarting awesome (ctrl-mod-r in the
default config) help?

> BTW:
> icon also too small any way make it larger ?

Dunno, I don't know much about GTK theming.
--

-- 
Who needs a ~/.signature anyway?

Johannes Sauer | 11 Jun 16:21 2015

Howto apply certain rules only at startup

Hi,

what I want to do is automatically start application on a certain tag. However when I later start another instance of the application I want it to appear on the tag I am at that moment.
I tried to do something like this in rc.lua:

   rules_always  = {
       -- All clients will match this rule.
       { rule = { },
         properties = { border_width = beautiful.border_width,
                        border_color = beautiful.border_normal,
                        focus = true,
                        keys = clientkeys,
                        buttons = clientbuttons } },
  
       -- Set Thunderbird to always map on tags number 3 of screen 1.
       { rule = { class = "Thunderbird" },
         properties = { tag = tags[1][3] } },
   }
  
   rules_startup = {
       -- Set Firefox to always map on tags number 3 of screen 1.
       { rule = { class = "Firefox" },
         properties = { tag = tags[1][2] } },
   }
  
   awful.rules.rules = awful.util.table.join(rules_always, rules_startup)

then at the end of rc.lua:

   run_once("firefox")

   awful.rules.rules = rules_startup

However the effect is that still all rules will be applied, i.e. every new instance of firefox will appear on tag 2.

What am I doing wrong?

Best,
Johannes

PS: My awesome version is 3.4.11, don't think it's relevant for this question.

Elv1313 . | 5 Jun 23:04 2015
Picon

Fwd: Dual-Monitor Systray

I don't think so, it require the compositor to be tied to the shell
and a lot of hacky code. XEMBED is a terrible thing, a security
nightmare and is also totally inflexible (no themes, *almost* no way
to have a transparent background, no accessibility support and so on).

References:
http://standards.freedesktop.org/systemtray-spec/systemtray-spec-latest.html
http://standards.freedesktop.org/xembed-spec/xembed-spec-latest.html

On 5 June 2015 at 16:49, Jeferson Lesbao <jefersonlsiq <at> gmail.com> wrote:
> Hi,
>
> Didn't know about this X11 limitation. Using compton as an composite manager
> can make it possible ?
>
> Regards,
> Jeferson
>
> On Fri, Jun 5, 2015 at 5:47 PM, Elv1313 . <elv1313 <at> gmail.com> wrote:
>>
>> Hello,
>>
>> Not really, this is an X11 limitations, they simply forbid it by
>> design. Some WMs use compositing to "fix" this, but Awesome doesn't
>> have it's own compositor.
>>
>> Regards,
>> Emmanuel
>>
>> On 5 June 2015 at 16:43, Abraham Baker <z1693060 <at> students.niu.edu> wrote:
>> > Hi,
>> >
>> > Another multi-monitor question:  is it possible to have the system tray
>> > (where icons like nm-applet show up) appear on every monitor?
>> >
>> > I tried this and it now flickers unreliably between each monitor based
>> > on
>> > which client is focused:
>> >
>> > in rc.lua, around line 202:
>> >  right_layout:add(wibox.widget.systray())
>> >
>> > as opposed to
>> >   if s == 1 then right_layout:add(wibox.widget.systray()) end
>> >
>> > Thanks,
>> > Abe
>>
>> --
>> To unsubscribe, send mail to awesome-unsubscribe <at> naquadah.org.
>
>

Abraham Baker | 5 Jun 22:43 2015

Dual-Monitor Systray

Hi,

Another multi-monitor question:  is it possible to have the system tray (where icons like nm-applet show up) appear on every monitor?

I tried this and it now flickers unreliably between each monitor based on which client is focused:

in rc.lua, around line 202:
 right_layout:add(wibox.widget.systray())

as opposed to
  if s == 1 then right_layout:add(wibox.widget.systray()) end

Thanks,
Abe
John Yates | 3 Jun 18:08 2015

Trouble building on Debian 7 (wheezy)

I am trying to build the git tip.  Things seem to go fine until it is time to build the man pages:

...
Scanning dependencies of target lgi-check
[ 55%] Built target lgi-check
Scanning dependencies of target man
[ 56%] Generating manpages/man1/awesome.1.xml
[ 57%] Generating manpages/man1/awesome.1
Note: Writing awesome.1
make[3]: *** [manpages/man1/awesome.1] Error 1
make[2]: *** [CMakeFiles/man.dir/all] Error 2
make[1]: *** [all] Error 2
make: *** [install] Error 2

Any suggestions?

/john

Gmane