awesome | 29 Sep 07:49 2014

[awesome bugs] #1155 - Windows not managed after changing resolution through RandR in 3.5.1

THIS IS AN AUTOMATED MESSAGE, DO NOT REPLY.

The following task has a new comment added:

FS#1155 - Windows not managed after changing resolution through RandR in 3.5.1
User who did this - Arnaud Fontaine (arnau)

----------
Thanks for your comment. The problem I initially reported can be reproduced on 3.5.5. I have just tested
with current master (57b6433) and even if it seems much better than before, I still have the following issue:

1. Start Awesome using default configuration. Both LVDS1 and DP1 are active and layout is float.
2. Open one xterm on LVDS1 (xterm-LVDS1) and another on DP1 (xterm-DP1).
3. Run ``xrandr --output DP1 --off''.

xterm-DP1 is properly displayed in the titlebar and now visible on LVDS1. However, xterm-LVDS1 is *not*
visible anymore on LVDS1 but it is displayed in the titlebar of LVDS1 and according to xwininfo, its
MapState is 'IsViewable' (and so is its parent). Clicking on xterm-LVDS1 title in the titlebar has no
effect but switching to another layout finally display it.

Adding what you suggested in default configuration just after the required() seems to have no effect...

Here are the output of xwininfo and xprop (xterm-LVDS1 is 0xc0000d and xterm-DP1 is 0x80000d):

xwininfo: Window id: 0xae (the root window) (has no name)

$ xwininfo -root -tree
  Root window id: 0xae (the root window) (has no name)
  Parent window id: 0x0 (none)
     6 children:
(Continue reading)

awesome | 26 Sep 11:39 2014

[awesome bugs] #1034 - indicator support

THIS IS AN AUTOMATED MESSAGE, DO NOT REPLY.

The following task has a new comment added:

FS#1034 - indicator support
User who did this - Tim Ansell (mithro)

----------
I've got a proof of a concept system which "swallows" the gnome-panel / panel-test-applets into the
awesome wibox. https://github.com/mithro/rcfiles/blob/master/awesome/config/swallow.lua

It's horribly hacky, but it's good enough for me to get back my network-manager, power and volume control.
----------

More information can be found at the following URL:
https://awesome.naquadah.org/bugs/index.php?do=details&task_id=1034#comment4144

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.

awesome | 25 Sep 17:54 2014

[awesome bugs] #1155 - Windows not managed after changing resolution through RandR in 3.5.1

THIS IS AN AUTOMATED MESSAGE, DO NOT REPLY.

The following task has a new comment added:

FS#1155 - Windows not managed after changing resolution through RandR in 3.5.1
User who did this - Daniel Hahler (blueyed)

----------
Arnaud, there have been some fixes in this regard.

Can you still reproduce it using master and/or the latest release?
Can you add the debug code I've posted to your config, which might help with debugging this.

Regarding bisecting, you've said that it was introduced by 1e418cb (or rather "1e418cb..8348d4"), which
is very old already.
----------

More information can be found at the following URL:
https://awesome.naquadah.org/bugs/index.php?do=details&task_id=1155#comment4143

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.

awesome | 25 Sep 10:05 2014

[awesome bugs] #1155 - Windows not managed after changing resolution through RandR in 3.5.1

THIS IS AN AUTOMATED MESSAGE, DO NOT REPLY.

The following task has a new comment added:

FS#1155 - Windows not managed after changing resolution through RandR in 3.5.1
User who did this - Uli Schlachter (psychon)

----------
Nope, no idea and no time
----------

More information can be found at the following URL:
https://awesome.naquadah.org/bugs/index.php?do=details&task_id=1155#comment4142

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.

awesome | 25 Sep 08:56 2014

[awesome bugs] #1155 - Windows not managed after changing resolution through RandR in 3.5.1

THIS IS AN AUTOMATED MESSAGE, DO NOT REPLY.

The following task has a new comment added:

FS#1155 - Windows not managed after changing resolution through RandR in 3.5.1
User who did this - Arnaud Fontaine (arnau)

----------
Any fix at all for this bug? As of Debian, Awesome 3.5 is still in experimental because of this and the freeze
is drawing near...
----------

More information can be found at the following URL:
https://awesome.naquadah.org/bugs/index.php?do=details&task_id=1155#comment4141

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.

awesome | 24 Sep 17:11 2014

[awesome bugs] #957 - maximizing always honour size hints

THIS IS AN AUTOMATED MESSAGE, DO NOT REPLY.

The following task has a new comment added:

FS#957 - maximizing always honour size hints
User who did this - Luigi Rocca (ggrocca)

----------
I confirm this bug in awesome v3.5.5 (Kansas City Shuffle), on Arch Linux.

The gaps happen not only when maximixing, but also when going fullscreen, despite setting
honor_size_hints = false. The offending applicaion on my machine is Emacs. To clarify, this happens when
maximizing/fullscreening single windows, not when the whole screen layout gets changed to max or max.fullscreen.

I manually applied Felix's patch to /usr/share/awesome/lib/awful .lua files and it works wonders - the
issue is completely fixed. Could it be included in the main release with a bit of polish?

I personally don't see any reason for honoring the size hints in fullscreen/maximize mode even when
honor_size_hints = false, but if this is the case maybe an additional option to control this behavior to
could be added.

----------

More information can be found at the following URL:
https://awesome.naquadah.org/bugs/index.php?do=details&task_id=957#comment4140

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.

(Continue reading)

awesome | 18 Sep 09:17 2014

[awesome bugs] #1297 - Add support for XCB_ICCCM_WM_HINT_ICON_PIXMAP

THIS IS AN AUTOMATED MESSAGE, DO NOT REPLY.

The following task has a new comment added:

FS#1297 - Add support for XCB_ICCCM_WM_HINT_ICON_PIXMAP
User who did this - Ben Winslow (rain)

----------
I can reproduce with xterm -- awesome doesn't pick up the icon because it's only set via the ICCCM hint.
----------

More information can be found at the following URL:
https://awesome.naquadah.org/bugs/index.php?do=details&task_id=1297#comment4139

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.

awesome | 18 Sep 01:33 2014

[awesome bugs] #1299 - MyPaint (GTK3/git version) cannot be fullscreened.

THIS IS AN AUTOMATED MESSAGE, DO NOT REPLY.

The following task has a new comment added:

FS#1299 - MyPaint (GTK3/git version) cannot be fullscreened.
User who did this - David Gowers (laurtik)

----------
Yes, it does work fine with mypaint 1.1, which indeed runs on GTK2. Try a version that runs on GTK3.

More recent versions of MyPaint also support XDG basedir.

The console output does not say anything when attempting to fullscreen.
----------

More information can be found at the following URL:
https://awesome.naquadah.org/bugs/index.php?do=details&task_id=1299#comment4138

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.

awesome | 17 Sep 20:46 2014

[awesome bugs] #1198 - Please allow the background of systray to be an image as well rather than only a color

THIS IS AN AUTOMATED MESSAGE, DO NOT REPLY.

The following task has a new comment added:

FS#1198 - Please allow the background of systray to be an image as well rather than only a color
User who did this - gyrfalco (gyrfalco)

----------
>> Same patch as attached to FS#1215

Patch works, tray can be transparent, but only 1 icon is shown, other icons (more than 1 tray app running) are hidden.
----------

More information can be found at the following URL:
https://awesome.naquadah.org/bugs/index.php?do=details&task_id=1198#comment4137

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.

awesome | 17 Sep 09:24 2014

[awesome bugs] #1299 - MyPaint (GTK3/git version) cannot be fullscreened.

THIS IS AN AUTOMATED MESSAGE, DO NOT REPLY.

The following task has a new comment added:

FS#1299 - MyPaint (GTK3/git version) cannot be fullscreened.
User who did this - Uli Schlachter (psychon)

----------
Works fine here with awesome v3.5.2-186-ga113fe0 and mypaint 1.1.0-3 from debian testing. Apparently
this is not using GTK2 here:

$ mypaint 
0
Using GTK2
builtin python 2.6 json support
DEBUG: getlocale(): ('de_DE', 'UTF-8')
DEBUG: localepath:  /usr/share/locale
DEBUG: localepath_brushlib:  /usr/share/locale
confpath = /home/psychon/.mypaint/
Created /home/psychon/.mypaint/
Created /home/psychon/.mypaint/backgrounds
Created /home/psychon/.mypaint/brushes
Created /home/psychon/.mypaint/scratchpads
DEBUG: mode stack updated: <ModeStack [SwitchableFreehandMode]>
Merging upstream brush changes into your collection.
Looking for GTK devices with pressure:
Device "Logitech USB-PS/2 Optical Mouse" has a pressure axis
Skipping "Logitech USB-PS/2 Optical Mouse" (probably a mouse)
Device "SynPS/2 Synaptics TouchPad" has a pressure axis
Skipping "SynPS/2 Synaptics TouchPad" (probably a laptop touchpad without pressure info)
(Continue reading)

awesome | 17 Sep 09:22 2014

[awesome bugs] #1280 - multiple tag selection wasn't highlighting properly when *_occupied is set in theme table

THIS IS AN AUTOMATED MESSAGE, DO NOT REPLY.

The following task is now closed:

FS#1280 - multiple tag selection wasn't highlighting properly when *_occupied is set in theme table
User who did this - Uli Schlachter (psychon)

Reason for closing: Fixed
Additional comments about closing: Pull request pulled (well, cherry-picked...)

More information can be found at the following URL:
https://awesome.naquadah.org/bugs/index.php?do=details&task_id=1280

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.


Gmane