Menubar Parsing Bug

[Maxwell Anselm]

The menubar library breaks entirely if it cannot parse every .desktop file
in its search path. For example, it breaks if one of your .desktop files is
a broken symlink.

For example, run

# ln -s /foo /usr/share/applications/broken.desktop

Restart awesome, and open the menubar. You will get an error at
lib/menubar/utils.lua:131 because it assumes that it will be able to parse
every .desktop file. It's an uncommon situation, but it's pretty annoying
that it breaks the whole menubar rather than skipping the problematic file.

Max

Re: Dragging inskape guides from rulers in awesome

[Maxwell Anselm]

Yes, I have two screens. I also get the weird maximized behavior from
Inkscape but I think that is unrelated as everything else works fine.
On Sep 29, 2015 10:24 AM, "Szymon Hennel" <szymon.hen...@gmail.com> wrote:

> I have just discovered that the behavior is more complex than just
> treating any click as mod4+button1 : Inkscape jumps between screens, but
> not within a single screen. If I reduce my setup to only one screen, there
> is no problem. Let me explain this better :
>
> I have 2 screens, both showing their first tag, using the layout
> awful.layout.suit.tile. I have a bunch on xterms on each screen. I open
> inskape on screen 1, it starts maximized even though I have the rule
>
> { rule = { class = "Inkscape" },
>   properties = {maximized_horizontal = false, maximized_vertical =
> false } },
>
> With mod4+button1, I can drag it around screen1 and make it jump between
> the possible positions in the tiling scheme, I can also drag it over to
> screen 2 in a controlled way.
>
> If I left click on inkscape and drag towards screen 2 (nothing should
> happen), then it immediately jumps to screen2, without going through
> available positition within the tiling scheme of screen 1. I can not drag
> it around screen 2 either, all I can do is make it it go back to its
> initial position on screen 1 if I drag the mouse in the other direction.
>
> Do you guys have multiple screens?
>
>
>
>
> On 2015-09-29 15:40, Maxwell Anselm wrote:
>
> No problem here either, with the same versions as lilydjwg.
>
> My config
>
> https://github.com/silverhammermba/.files/blob/bet/awesome/.config/awesome/rc.lua
>
> On Tue, Sep 29, 2015 at 9:31 AM, lilydjwg <lilyd...@gmail.com> wrote:
>
>> On Tue, Sep 29, 2015 at 11:54:03AM +0200, Szymon Hennel wrote:
>> > Hi,
>> >
>> > I have the same issue, so it's unlikely to be an error in your config.
>> > Left-Clicking and dragging on any pixel that does not belong to the
>> document
>> > or to a button is interpreted as mod4+button1.
>>
>> I don't have the issue. It works quite well for me. Here's my config:
>> https://github.com/lilydjwg/myawesomerc
>>
>> Versions:
>>
>> awesome 3.5.6-2
>> inkscape 0.91-9
>>
>> --
>> Best regards,
>> lilydjwg
>>
>> --
>> To unsubscribe, send mail to awesome-unsubscr...@naquadah.org.
>>
>
>
>

Re: When tiling is active drag-n-drop doesn't work as expected

[Maxwell Anselm]

I've had drag'n'drop problems while tiled with other programs as well. Most
notably dragging tabs in Chrome.

On Thu, Oct 1, 2015 at 10:14 AM, / vt  wrote:

> Hi,
>
> Today I found something strange and interesting and still a bug ; )
> I was not in "float" mode but in "tiling" mode and I had several clients
> (windows) on the screen one of which was the "Archive Manager" (Gnome) and
> another one was Nautilus.
> When I tried to drag a folder from the archive opened in the Archive
> Manager to the Nautilus in order to unzip it I noticed that I cannot do it.
> My mouse was returning back to the Archive Manager client and the
> drag-n-drop feature failed with stupid 'null' message. When I switched to
> floating mode I was able to unzip the folder by dragging and dropping.
> Do you know how this can be fixed?
>
> awesome v3.4.15 (Never Gonna Give You Up)
>  • Build: Feb 17 2013 21:10:46 for x86_64 by gcc version 4.7.2
> (buildd@barber)
>  • D-Bus support: ✔
>
> Debian 8 Jessie, x64
>
>
> Thanks,
> /v
>

Re: My problems with the last version

[Maxwell Anselm]

If you're running a compositor such as compton, try disabling it.
On Feb 2, 2016 08:20, "Antonio Marín"  wrote:

> Awesome for Arch (x86_64) is my only one window manager... in my home...
> in the office.
> But the last versions (3.5.7 and 3.5.8, from Arch repository)  give me
> problems.
> I had to downgrade to 3.5.6 that works perfectly for me.
>
> The problem is when I try to init my X via startx with the last versions.
> Someone can help me to solve this little problem?
> All seems a xorg configuration problem. But the question is that's all ok
> with the 3.5.6 version.
>
> That's a trace  in my Xorg log:
>
> 342 [   350.478] (EE)
> 343 [   350.478] (EE) Backtrace:
> 344 [   350.478] (EE) 0: /usr/lib/xorg-server/Xorg (OsLookupColor+0x139)
> [0x598499]
> 345 [   350.479] (EE) 1: /usr/lib/libc.so.6 (__restore_rt+0x0)
> [0x7fb7ba73b67f]
> 346 [   350.480] (EE) 2: /usr/lib/libpixman-1.so.0
> (pixman_region_fini+0x9) [0x7fb7bb650a69]
> 347 [   350.480] (EE) 3: /usr/lib/xorg/modules/drivers/intel_drv.so
> (_init+0x58576) [0x7fb7b535f336]
> 348 [   350.480] (EE) 4: /usr/lib/xorg/modules/drivers/intel_drv.so
> (_init+0x56141) [0x7fb7b535a3e1]
> 349 [   350.480] (EE) 5: /usr/lib/xorg-server/Xorg
> (DamageRegionAppend+0x621) [0x51c361]
> 350 [   350.481] (EE) 6: /usr/lib/xorg-server/Xorg (AddTraps+0x40d7)
> [0x5159c7]
> 351 [   350.481] (EE) 7: /usr/lib/xorg-server/Xorg
> (SendErrorToClient+0x2df) [0x43626f]
> 352 [   350.481] (EE) 8: /usr/lib/xorg-server/Xorg
> (remove_fs_handlers+0x453) [0x43a293]
> 353 [   350.481] (EE) 9: /usr/lib/libc.so.6 (__libc_start_main+0xf0)
> [0x7fb7ba728610]
> 354 [   350.482] (EE) 10: /usr/lib/xorg-server/Xorg (_start+0x29)
> [0x4245c9]
> 355 [   350.482] (EE) 11: ? (?+0x29) [0x29]
> 356 [   350.482] (EE)
> 357 [   350.482] (EE) Segmentation fault at address 0x0
> 358 [   350.482] (EE)
> 359 Fatal server error:
> 360 [   350.482] (EE) Caught signal 11 (Segmentation fault). Server
> aborting
> 361 [   350.482] (EE)
> 362 [   350.482] (EE)
> 363 Please consult the The X.Org Foundation support
> 364  at http://wiki.x.org
> 365  for help.
> 366 [   350.482] (EE) Please also check the log file at 
> for additional information.
> 367 [   350.482] (EE)
> 368 [   350.482] (II) AIGLX: Suspending AIGLX clients for VT switch
> 369 [   350.591] (EE) Server terminated with error (1). Closing log file.
>
> --
> Antonio Marín
>