awesome | 16 Nov 14:14 2014

[awesome bugs] #1312 - Initial fullscreen with mpv not working (Attachment added)

THIS IS AN AUTOMATED MESSAGE, DO NOT REPLY.

The following task has a new comment added:

FS#1312 - Initial fullscreen with mpv not working
User who did this - Sven Greiner (SammysHP)

----------
Output of xprop for the client. It's the same output with initial fullscreen and after toggling.
----------

One or more files have been attached.

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

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 | 16 Nov 14:09 2014

[awesome bugs] #1312 - Initial fullscreen with mpv not working

THIS IS AN AUTOMATED MESSAGE, DO NOT REPLY.

A new Flyspray task has been opened.  Details are below. 

User who did this - Sven Greiner (SammysHP) 

Attached to Project - awesome
Summary - Initial fullscreen with mpv not working
Task Type - Bug Report
Category - Core
Status - Unconfirmed
Assigned To - 
Operating System - Linux
Severity - Low
Priority - Normal
Reported Version - 3.5.5
Due in Version - Undecided
Due Date - Undecided
Details - Play a video with mpv in fullscreen mode:

$ mpv --fs <some video file>

You'll notice that the wibox is still visible and the fullscreen video is moved down by exactly the height of
the wibox.
Toggle the fullscreen mode by pressing f twice. Now the video covers the whole screen.

During my research I found this comment, maybe it is related: https://github.com/mpv-player/mpv/issues/431#issuecomment-58489165

> Note that we do indeed use a different method for the initial fullscreen setting, because 
> that allows us to atomically create a fullscreen window without flicker. We do this by 
(Continue reading)

awesome | 14 Nov 06:05 2014

[awesome bugs] #1311 - awful.util.spawn crashes during startup, works fine afterwards

THIS IS AN AUTOMATED MESSAGE, DO NOT REPLY.

A new Flyspray task has been opened.  Details are below. 

User who did this - Dean Scarff (dos) 

Attached to Project - awesome
Summary - awful.util.spawn crashes during startup, works fine afterwards
Task Type - Bug Report
Category - Core
Status - Unconfirmed
Assigned To - 
Operating System - All
Severity - Medium
Priority - Normal
Reported Version - 3.4.15
Due in Version - Undecided
Due Date - Undecided
Details - This was reported independently in Debian and Ubuntu a while ago:
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=705011
https://bugs.launchpad.net/ubuntu/+source/awesome/+bug/1176862

I can reproduce in 3.4.15-1ubuntu1.  This was definitely a regression (my rc.lua didn't change, I just
upgraded awesome and probably some other packages).

Steps to reproduce:
1. In rc.lua:
awful.util.spawn("/bin/echo")
2. Start awesome from GDM

(Continue reading)

awesome | 8 Nov 01:33 2014

[awesome bugs] #1030 - Wine floating windows move to the right&down by themselves

THIS IS AN AUTOMATED MESSAGE, DO NOT REPLY.

The following task has a new comment added:

FS#1030 - Wine floating windows move to the right&down by themselves
User who did this - Daniel Hahler (blueyed)

----------
This is related to the border width. Using 0 instead of 1 does not trigger it.

I am applying the client.border_width via:

    for s = 1, screen.count() do screen[s]:connect_signal("arrange", function ()
      ...
      c.border_width = beautiful.border_width

----------

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

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 | 8 Nov 01:29 2014

[awesome bugs] #1030 - Wine floating windows move to the right&down by themselves

THIS IS AN AUTOMATED MESSAGE, DO NOT REPLY.

The following task has a new comment added:

FS#1030 - Wine floating windows move to the right&down by themselves
User who did this - Daniel Hahler (blueyed)

----------
I can reproduce this issue using urxvt (rxvt-unicode) and the following escape sequence:

   printf '\033]710;xft:monospace:size=10\033\'

This sets the new font. So on first invocation the floating window will change altogether, but when called
again, it moves down and right by one pixel.
----------

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

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 | 7 Nov 22:06 2014

[awesome bugs] #1268 - awful.tag.delete doesn't properly support multitagging

THIS IS AN AUTOMATED MESSAGE, DO NOT REPLY.

The following task is now closed:

FS#1268 - awful.tag.delete doesn't properly support multitagging
User who did this - Uli Schlachter (psychon)

Reason for closing: Fixed
Additional comments about closing: Elv13 requested this to be closed with the reason "Merged". I trust him
on this,

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

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 | 7 Nov 22:05 2014

[awesome bugs] #1264 - Provide context with request::activate signal / separate signal for _NET_ACTIVE_WINDOW

THIS IS AN AUTOMATED MESSAGE, DO NOT REPLY.

The following task is now closed:

FS#1264 - Provide context with request::activate signal / separate signal for _NET_ACTIVE_WINDOW
User who did this - Uli Schlachter (psychon)

Reason for closing: Fixed
Additional comments about closing: (Sorry, I  missed thatthe commit doesn't refer to this FS in the commit message)

commit 37684abe3342886a3bd5f6a9c65acd2d99d313e8
Author: Emmanuel Lepage Vallee <elv1313 <at> gmail.com>
Date:   Mon May 5 23:12:21 2014 -0400

    Add context to request::activate signal

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

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 | 7 Nov 22:04 2014

[awesome bugs] #1267 - impossible to mouse-resize any custom layout due to hardcoding in mouse/init.lua

THIS IS AN AUTOMATED MESSAGE, DO NOT REPLY.

The following task is now closed:

FS#1267 - impossible to mouse-resize any custom layout due to hardcoding in mouse/init.lua
User who did this - Uli Schlachter (psychon)

Reason for closing: Fixed
Additional comments about closing: commit 8d7b0feedd9de3cb41bcbc2deff26c9a8ab34450
Author: Robert Siska <siska.robert <at> gmail.com>
Date:   Thu Oct 23 01:30:19 2014 +0200

    Layouts can define their own resizing handler (FS#1267)

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

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 | 7 Nov 22:04 2014

[awesome bugs] #1229 - Tag "index" is not handled properly

THIS IS AN AUTOMATED MESSAGE, DO NOT REPLY.

The following task is now closed:

FS#1229 - Tag "index" is not handled properly
User who did this - Uli Schlachter (psychon)

Reason for closing: Fixed
Additional comments about closing: commit 45ad4459f2e6bab737e4e93009fd4dff9f4a546b
Author: Emmanuel Lepage Vallee <elv1313 <at> gmail.com>
Date:   Sat Nov 1 18:46:06 2014 -0400

    tag: Improve tag property::index support (FS#1229)

    * Move the "index" setting burden to individual functions
      instead of gettags().

    * Add some properties earlier so the signal hooks will be called
      with valid data.

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

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 | 6 Nov 22:04 2014

[awesome bugs] #1309 - Crossover/WINWORD.exe is invisible

THIS IS AN AUTOMATED MESSAGE, DO NOT REPLY.

The following task has a new comment added:

FS#1309 - Crossover/WINWORD.exe is invisible
User who did this - Daniel Hahler (blueyed)

----------
Oleksii,

here is a pointer: http://git-scm.com/docs/git-bisect :)

It would be really helpful to have information about which commit caused the regression.

Thanks.
----------

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

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 | 6 Nov 21:58 2014

[awesome bugs] #1310 - Current client gets tagged as urgent and mod4+u does not move to next urgent

THIS IS AN AUTOMATED MESSAGE, DO NOT REPLY.

The following task has a new comment added:

FS#1310 - Current client gets tagged as urgent and mod4+u does not move to next urgent
User who did this - Daniel Hahler (blueyed)

----------
The other improvement mentioned is provided in https://github.com/awesomeWM/awesome/pull/33/.
----------

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

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