Re: Broken GTK menus
On 2012–11–29 Marco wrote: I filed a bug report¹ against gtk+. Feel free to add more information or a better description of the behaviour. [1] https://bugzilla.gnome.org/show_bug.cgi?id=689030 Geoff has written a patch to address this issue. I didn't try it yet, but he mentions that it's not only a bug in gtk+, but also in awesome. On 2013-01-09 Geoff Reedy wrote: The amount of data in the _NET_WORKAREA property was not being checked and some window managers (at least xmonad, i3, and awesome) are only including 4 values even if they report a number of desktops greater than 1. While we're at it also check that the type is CARDINAL and the format is 32. After being annoyed by this bug for months (I use xmonad) I've finally tracked it down. The patch applies onto master, gtk-3-4, and gtk-3-6 cleanly right now. This is actually a bug both in gtk and in the window managers. The window managers should be setting enough values in the _NET_WORKAREA property and gtk should not be trying to get non-existent values from the property. Maybe someone could have a look into that. Marco signature.asc Description: Digital signature
Skype / Tray Status Icon
Hi All, A quick question - Yesterday I had an icon in my tray for Skype [ie: minimized], now today it has gone (but the main process is definitely running) - Anyone seen this or have any suggestions on what I do to get it back? PS: Using Ubuntu Server [12.04.1] with awesome from the ubuntu repository [3.4.11] PPS: Only change I can think of was to apply the latest updates that (from memory) were man firefox PPPS: I also run remmina guake ane their icons appear Regards, Dave -- To unsubscribe, send mail to awesome-unsubscr...@naquadah.org.
make e.g. synaptic-pkexec work under awesome?
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Hi I am using Ubuntu quantal and Awesome. I used gnome-session and awesome, but somehow it was really slow, so I went back to using the normal awesome. Everything is still fine, but I have one problem: I use gnome-do, and when starting synaptic via gnome-do, synaptic-pkexec is executed. Under gnome-session, this launches a graphical dialog asking for the password to run synaptic with root privileges, but not when gnome-session is not launched, then nothing happens (same by the way when executing synaptic-pkexec in the awesome run box). I would very much like to get this to work again, as I use gnome-do regularly. In a terminal, synaptic-pkexec works by asking in the terminal for the password. Any suggestions which component I have to start to get the default behavior back? Thanks, Rainer -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.11 (GNU/Linux) Comment: Using GnuPG with Thunderbird - http://www.enigmail.net/ iEYEARECAAYFAlDtewcACgkQoYgNqgF2egov7gCfe6gLSXE4aFpeaQzoXk7Qp/b1 YfsAn3VhLIuuJe6ryQVIBP+qlv8/pIdr =T21R -END PGP SIGNATURE- -- To unsubscribe, send mail to awesome-unsubscr...@naquadah.org.
Re: make e.g. synaptic-pkexec work under awesome?
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On 09/01/13 15:13, Rainer M Krug wrote: Hi I am using Ubuntu quantal and Awesome. I used gnome-session and awesome, but somehow it was really slow, so I went back to using the normal awesome. Everything is still fine, but I have one problem: I use gnome-do, and when starting synaptic via gnome-do, synaptic-pkexec is executed. Under gnome-session, this launches a graphical dialog asking for the password to run synaptic with root privileges, but not when gnome-session is not launched, then nothing happens (same by the way when executing synaptic-pkexec in the awesome run box). I would very much like to get this to work again, as I use gnome-do regularly. In a terminal, synaptic-pkexec works by asking in the terminal for the password. Any suggestions which component I have to start to get the default behavior back? /usr/lib/policykit-1-gnome/polkit-gnome-authentication-agent-1 Thanks Christopher, that's working Rainer Thanks, Rainer -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.11 (GNU/Linux) Comment: Using GnuPG with Thunderbird - http://www.enigmail.net/ iEYEARECAAYFAlDtfwsACgkQoYgNqgF2egr2MwCfWEaDq3C/7+1ePqmoVEwxE8Fw /vcAniqrOWMuvN9DiI5VPdRj45GOXs5q =HcLl -END PGP SIGNATURE- -- To unsubscribe, send mail to awesome-unsubscr...@naquadah.org.
Re: make e.g. synaptic-pkexec work under awesome?
On 2013–01–09 Rainer M Krug wrote: Everything is still fine, but I have one problem: I use gnome-do, and when starting synaptic via gnome-do, synaptic-pkexec is executed. Under gnome-session, this launches a graphical dialog asking for the password to run synaptic with root privileges, but not when gnome-session is not launched, then nothing happens (same by the way when executing synaptic-pkexec in the awesome run box). I cannot directly provide a solution, but I will tell you how I solved this (not using gnome-do, but the awesome menubar but that should not matter, I guess). I copied the synaptic.desktop file to $HOME/.local/share/applications and modified the name and the command line from Name=Synaptic Package Manager Exec=synaptic-pkexec to Name=Synaptic Exec=su-to-root -X -c synaptic Shortening the name sorts it before the default one. So when I type “syn” the customised version is selected. And `su-to-root` uses `gksu` by default, which should then ask for your password. Marco signature.asc Description: Digital signature
Re: [ANNOUNCE] awesome 3.4.14 released
Christopher Schmidt christop...@ch.ristopher.com writes: IIRC this is due to the X feature of setting the keyboard layout right before the first key is pressed. This is just a vague guess, though - I do not remember any details. A non-intrusive workaround for this bug is to set the keyboard layout before starting awesome, e.g. via setxkbmap in .xsession. Christopher -- To unsubscribe, send mail to awesome-unsubscr...@naquadah.org.
Re: make e.g. synaptic-pkexec work under awesome?
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On 09/01/13 15:43, Marco wrote: On 2013–01–09 Rainer M Krug wrote: Everything is still fine, but I have one problem: I use gnome-do, and when starting synaptic via gnome-do, synaptic-pkexec is executed. Under gnome-session, this launches a graphical dialog asking for the password to run synaptic with root privileges, but not when gnome-session is not launched, then nothing happens (same by the way when executing synaptic-pkexec in the awesome run box). I cannot directly provide a solution, but I will tell you how I solved this (not using gnome-do, but the awesome menubar but that should not matter, I guess). I copied the synaptic.desktop file to $HOME/.local/share/applications and modified the name and the command line from Name=Synaptic Package Manager Exec=synaptic-pkexec to Name=Synaptic Exec=su-to-root -X -c synaptic Shortening the name sorts it before the default one. So when I type “syn” the customised version is selected. And `su-to-root` uses `gksu` by default, which should then ask for your password. Yes - I read this when googling, but I prefer as little as possible changes - and if other programs use the policykit as well, I have to change them as well. I rather prefer to start the polkit-gnome-authentication-agent-1 as suggested by Christoph. Thanks a lot, Rainer Marco -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.11 (GNU/Linux) Comment: Using GnuPG with Thunderbird - http://www.enigmail.net/ iEYEARECAAYFAlDthMYACgkQoYgNqgF2egpAOwCfREheGJHFOxsmKI+G/N8pGpbk KV0An1NQFEQ2nPRP4x6IrHvyvZwsgcOO =okNS -END PGP SIGNATURE- -- To unsubscribe, send mail to awesome-unsubscr...@naquadah.org.
Re: [ANNOUNCE] awesome 3.4.14 released
Hi, On 09.01.2013 14:45, Christopher Schmidt wrote: 000::0006: 8: XKEYBOARD-Request(145,0): UseExtension major=1 minor=0 000::0006:32: Reply to UseExtension: major=1 minor=0 I hate Xlib. So much. No one should ever use it. We should rip it out of awesome ASAP again. Luckily, someone is porting libXcursor to xcb right now, so this might very well be usable. Anyway, back to the issue at hand: I have no idea what the XKEYBOARD extension does here exactly. However, let's quote [0] on what XkbUseExtension does: Once a client asks for XKB extension semantics by issuing this request, the server reports the extended XKB keyboard state in some core protocol events and requests, as described in the overview section of this specification. I check Xlib's source code and I found some env vars which might be useful. Could someone please start awesome with these variables: XKB_DEBUG=1 XKB_DISABLE=1 awesome This should print a message XKEYBOARD extension disabled or missing and hopefully fix this issue. If this bug still exists afterwards, I'll have to check the trace more carefully. Uli [0] http://www.x.org/releases/X11R7.7/doc/kbproto/xkbproto.html -- If you have to type the letters A-E-S into your source code, you're doing it wrong. -- To unsubscribe, send mail to awesome-unsubscr...@naquadah.org.
Re: [ANNOUNCE] awesome 3.4.14 released
Uli Schlachter psyc...@znc.in writes: On 09.01.2013 14:45, Christopher Schmidt wrote: 000::0006: 8: XKEYBOARD-Request(145,0): UseExtension major=1 minor=0 000::0006:32: Reply to UseExtension: major=1 minor=0 [...] Anyway, back to the issue at hand: I have no idea what the XKEYBOARD extension does here exactly. However, let's quote [0] on what XkbUseExtension does: Once a client asks for XKB extension semantics by issuing this request, the server reports the extended XKB keyboard state in some core protocol events and requests, as described in the overview section of this specification. I check Xlib's source code and I found some env vars which might be useful. Could someone please start awesome with these variables: XKB_DEBUG=1 XKB_DISABLE=1 awesome This should print a message XKEYBOARD extension disabled or missing and hopefully fix this issue. This fixes the issue. Thank you very much. Greetings, Christopher -- To unsubscribe, send mail to awesome-unsubscr...@naquadah.org.
Increase the space between tags in taglist
Hi, I just upgraded awesome to 3.5. It seems that (I'm not positively sure) the space between tags in awesome 3.5 in narrower. For example, in awesome 3.4, the taglist looks like this: | Tag1 | Tag2 | Tag3| In awesome 3.5: |Tag1|Tag2|Tag3| So, Can I increase the space between these tags? Regards. -- To unsubscribe, send mail to awesome-unsubscr...@naquadah.org.
Re: Increase the space between tags in taglist
I just found a screenshot for my old awesome 3.4 setup, and I can confirm that the space is indeed narrower. Please see the attached png. (The above taglist is awesome 3.5, and the bottom one is from the screenshot of the old 3.4) Regards. attachment: difference_between_3.4_3.5.png
Re: [ANNOUNCE] awesome 3.4.14 released
Hi, On 09.01.2013 16:46, Christopher Schmidt wrote: Uli Schlachter psyc...@znc.in writes: [...] I check Xlib's source code and I found some env vars which might be useful. Could someone please start awesome with these variables: XKB_DEBUG=1 XKB_DISABLE=1 awesome This should print a message XKEYBOARD extension disabled or missing and hopefully fix this issue. This fixes the issue. Thank you very much. OK, so let's turn this into a patch. Could at least two different persons test the attached patch on 3.4 and confirm that this fixes our issue? Seems like we will have an awesome 3.4.15 release. Uli P.S.: Proposals for a code name? -- - Buck, when, exactly, did you lose your mind? - Three months ago. I woke up one morning married to a pineapple. An ugly pineapple... But I loved her. diff --git a/awesome.c b/awesome.c index 3f8c81a..241c883 100644 --- a/awesome.c +++ b/awesome.c @@ -34,6 +34,7 @@ #include xcb/xtest.h #include X11/Xlib-xcb.h +#include X11/XKBlib.h #include awesome.h #include spawn.h @@ -374,6 +375,9 @@ main(int argc, char **argv) sigemptyset(sa.sa_mask); sigaction(SIGSEGV, sa, 0); +/* XLib sucks */ +XkbIgnoreExtension(True); + /* X stuff */ globalconf.display = XOpenDisplay(NULL); if (globalconf.display == NULL)
Re: Increase the space between tags in taglist
Would it be an idea to insert spaces at the beginning and at the end of the tags' names? Seems to do what you want. Greetings Manuel -- To unsubscribe, send mail to awesome-unsubscr...@naquadah.org.
set background colour in mysystray and mylayoutbox
hi, I want to be able to change the background colour of mysystraybox and mylayoutbox, I can't do it with wibox.widget.backgound(), testing that I get this error, so that says to me this is not the way the background is set on this widgets: /usr/share/awesome/lib/gears/debug.lua.23 : assertion failed: 'draw is not a function' stack traceback: /usr/share/awesome/lib/gearsdebug.lua:23: in function 'assert' /usr/share/awesome/widget/base.lua:113: in function 'check_widget' /usr/share/awesome/widget/background.lua:64: in function 'set_widget' /home/shuuichi/.config/awesome/rc.lua:438: in main chunk there is a way that I can custom the background colour in mysystray and mylayoutbox widgets?
[awesome bugs] #1091 - wildcard matching in rules is no longer working
THIS IS AN AUTOMATED MESSAGE, DO NOT REPLY.
A new Flyspray task has been opened. Details are below.
User who did this - Kasi (popsch)
Attached to Project - awesome
Summary - wildcard matching in rules is no longer working
Task Type - Bug Report
Category - Core
Status - Unconfirmed
Assigned To -
Operating System - All
Severity - Low
Priority - Normal
Reported Version - git/master
Due in Version - Undecided
Due Date - Undecided
Details - I'm trying to make skype call windows to be floating and on top, so
they don't vanish. The followin rule worked with 3.4. It doesn't work now
anymore:
{ rule = { name = Call with*, class = Skype },
properties = { floating = true, ontop = true } },
Steps to reproduce are simple:
1. Open skype
2. Make a skype call to any land line
This is what xprop says about my skype call window:
_NET_WM_NAME(UTF8_STRING) = Call with +1X
WM_WINDOW_ROLE(STRING) = CallWindow
WM_PROTOCOLS(ATOM): protocols WM_DELETE_WINDOW, WM_TAKE_FOCUS, _NET_WM_PING,
_NET_WM_SYNC_REQUEST
WM_NAME(STRING) = Call with +1
WM_CLASS(STRING) = skype, Skype
More information can be found at the following URL:
https://awesome.naquadah.org/bugs/index.php?do=detailstask_id=1091
You are receiving this message because you have requested it from the Flyspray
bugtracking system. If you did not expect this message or don't want to
receive mails in future, you can change your notification settings at the URL
shown above.
--
To unsubscribe, send mail to awesome-devel-unsubscr...@naquadah.org.
[awesome bugs] #1091 - wildcard matching in rules is no longer working
THIS IS AN AUTOMATED MESSAGE, DO NOT REPLY.
The following task has a new comment added:
FS#1091 - wildcard matching in rules is no longer working
User who did this - Uli Schlachter (psychon)
--
Could you try if the following rule works?
{ rule = { name = Call with*, class = Skype }, callback = function(c)
naughty.notify({text = It works!}) end }
--
More information can be found at the following URL:
https://awesome.naquadah.org/bugs/index.php?do=detailstask_id=1091#comment3349
You are receiving this message because you have requested it from the Flyspray
bugtracking system. If you did not expect this message or don't want to
receive mails in future, you can change your notification settings at the URL
shown above.
--
To unsubscribe, send mail to awesome-devel-unsubscr...@naquadah.org.
[awesome bugs] #1082 - Resize operation does not end after unclicking (intermittent)
THIS IS AN AUTOMATED MESSAGE, DO NOT REPLY. The following task has a new comment added: FS#1082 - Resize operation does not end after unclicking (intermittent) User who did this - Tim (tdy) -- Hmm yes, same here.. happens every time I close and open the firefox preferences dialog. -- More information can be found at the following URL: https://awesome.naquadah.org/bugs/index.php?do=detailstask_id=1082#comment3352 You are receiving this message because you have requested it from the Flyspray bugtracking system. If you did not expect this message or don't want to receive mails in future, you can change your notification settings at the URL shown above. -- To unsubscribe, send mail to awesome-devel-unsubscr...@naquadah.org.
