From byorgey at gmail.com Fri Jan 6 22:20:27 2017 From: byorgey at gmail.com (Brent Yorgey) Date: Fri, 06 Jan 2017 22:20:27 +0000 Subject: [xmonad] Controlling Window Location with XMonad.Layout.ThreeColumns In-Reply-To: References: Message-ID: Hi Eyal, I'm just going back through old xmonad emails trying to make sure nothing falls through the cracks. Would you mind creating an issue for this at https://github.com/xmonad/xmonad-contrib/issues ? I am not yet confident I understand what is going on here well enough to know what the right fix is, but if a ticket is created then it becomes easier for others to look at it, and it won't accidentally be forgotten. Thanks! -Brent On Wed, Nov 9, 2016 at 4:38 PM Eyal Erez wrote: > Hi Daniel, > > Thank you for your response. I've spent the last few days trying to > compile and run xmonad locally without much success. > Would there be any chance you could make this change so that it might get > into 0.13 before it gets released? > > Otherwise, I'll continue to try and get xmonad to run locally. > > > On Sun, Oct 23, 2016 at 6:32 AM, Daniel Wagner wrote: > > I think I'd consider that a bug, and it's probably easy enough to fix it. > This is a guess based on reading the source, so you should verify for > yourself whether this changes things appropriately, but... > > In XMonad.Layout.ThreeColumns.split3HorizontallyBy, swap the second two > elements of the triple in the True branch, so that it reads: > > then ( Rectangle (sx + fromIntegral r3w) sy r1w sh > , Rectangle sx sy r3w sh > , Rectangle (sx + fromIntegral r3w + fromIntegral r1w) sy r2w sh ) > > ~d > > On Tue, Oct 18, 2016 at 12:02 AM, Eyal Erez wrote: > > Hi, > > I have an ultrawide monitor and so I use ThreeColumns most of the > time. I create it like so: > > ThreeColMid 1 (3/100) (1/3) > > This works fine, however, I'm getting some strange behavior when > creating an closing windows. I hope I can explain this with a small > diagram which shows window location as I create and close apps: > > CREATE > 1 [ a ] > 2 [b][ a ] > 3 [a][c][b] > > CLOSE > 1 [a][c][b] > 2 [b][ a ] > 3 [ a ] > > So, when going from 2 to 3 open windows, window "a" and "b" switch > location for some reason. in step #2 "b" is on the left and "a" is on > the right, but when a third window is added (or removed) they swap > locations. This is very confusing. > > Is there anyway I can cause this to stop happening? It would also be > nice if window "b" was created into the active location, but that's > more of a nitpick. > > Thank you > > -- > There are 10 types of people, those who know binary and those who don't. > > > > > > > > > _______________________________________________ > xmonad mailing list > xmonad at haskell.org > http://mail.haskell.org/cgi-bin/mailman/listinfo/xmonad > > > > > > -- > *Eyal Erez <**oneself at gmail.com* *>* > > There are 10 types of people, those who know binary and those who don't. > > _______________________________________________ > xmonad mailing list > xmonad at haskell.org > http://mail.haskell.org/cgi-bin/mailman/listinfo/xmonad > -------------- next part -------------- An HTML attachment was scrubbed... URL: From es at ethanschoonover.com Wed Jan 11 05:38:58 2017 From: es at ethanschoonover.com (Ethan Schoonover) Date: Tue, 10 Jan 2017 21:38:58 -0800 Subject: [xmonad] Issue with screenlocker obscured in background after display change Message-ID: A consistently reproducible problem involving titlebar decorations & screenlockers. I would have submitted an issue on github, but I'm not even sure if this is an XMonad core issue, an X.L.NoFrillsDecoration issue, a general decoration issue, or what, exactly. Summary: ------------------------------------------------------- Screenlocker (tested with various) is obscured by windows after display change when using a minimal layout with titlebar decorations. Video demonstrating issue: ------------------------------------------------------- https://www.youtube.com/watch?v=O3P_VJIZBE0 Environment: ------------------------------------------------------- Dual monitor (laptop/external), normally used one at a time. I have a udev rule that triggers a shell script that switches display when hotplugging/unplugging. Scenario (as demonstrated in video): ------------------------------------------------------- 1. External monitor active, internal inactive (or vice versa, point being only one display active) 2. Screen lock using any of several common screen lockers (tested this issue with: xscreensaver, i3lock, sxlock) is activated while connected to external display. Hot-unplug of external display triggers udev xrandr script, internal laptop display is successfully activated. 3. If using layout without titlebar decorations, there is no problem 4 If using X.L.NoFrillsDecoration to make title bar decorations on the windows, the layout windows are drawn on TOP of the screen locker on the new display. The screenlocker retains input focus, so it can be unlocked, but it is obscured by the windows on top of it. (I can see the screenlocker through the terminals since I'm using transparency, but if a non transparent window, the screenlocker is completely obscured). Dotfiles: ------------------------------------------------------- Gist of very basic XMonad config I put together to test this. https://gist.github.com/altercation/1e5150369b4eb6f7caf013550de0bd43 Any ideas on work arounds for this? -Ethan Ethan Schoonover es at ethanschoonover.com @ethanschoonover http://ethanschoonover.com Freenode/Github: altercation From mlists at pmade.com Thu Jan 12 20:34:38 2017 From: mlists at pmade.com (Peter Jones) Date: Thu, 12 Jan 2017 13:34:38 -0700 Subject: [xmonad] Ready for v0.13? References: <87wpggy3qb.fsf@pmade.com> Message-ID: <87lgugnhk1.fsf@pmade.com> Peter Jones writes: > I'd like to close as many issues and pull requests as we can before > making a release. And of course, getting master tested before the > release would be a good idea too ;) Update on v0.13: I've identified issues and PRs that will be included in v0.13. This isn't an absolutely complete list, just a line in the sand to help prevent feature creep and get the next release out the door. https://github.com/xmonad/xmonad/milestones/v0.13 https://github.com/xmonad/xmonad-contrib/milestones/v0.13 Also, I have assigned myself to issues/PRs that I will be working on over the next couple of weeks. For any issues that don't have someone assigned, please consider assigning yourself if you have time. I'd like to aim for a release date sometime during the week of January 30. If there are still open issues with a v0.13 milestone by then we'll have to figure out if we want to remove those issues from the milestone or push the release back. -- Peter Jones, Founder, Devalot.com Defending the honor of good code From mlists at pmade.com Thu Jan 12 21:14:47 2017 From: mlists at pmade.com (Peter Jones) Date: Thu, 12 Jan 2017 14:14:47 -0700 Subject: [xmonad] Issue with screenlocker obscured in background after display change References: Message-ID: <87ziiw3rqw.fsf@pmade.com> Ethan Schoonover writes: > A consistently reproducible problem involving titlebar decorations & > screenlockers. I would have submitted an issue on github, but I'm not > even sure if this is an XMonad core issue, an X.L.NoFrillsDecoration > issue, a general decoration issue, or what, exactly. This is a very bizarre problem for sure. Open an issue under the xmonad-contrib repository so it doesn't get swept under the rug. -- Peter Jones, Founder, Devalot.com Defending the honor of good code From oneself at gmail.com Fri Jan 13 02:33:20 2017 From: oneself at gmail.com (Eyal Erez) Date: Thu, 12 Jan 2017 21:33:20 -0500 Subject: [xmonad] Controlling Window Location with XMonad.Layout.ThreeColumns In-Reply-To: References: Message-ID: Definitely, Thank you very much for following up. On Fri, Jan 6, 2017 at 5:20 PM, Brent Yorgey wrote: > Hi Eyal, > > I'm just going back through old xmonad emails trying to make sure nothing > falls through the cracks. Would you mind creating an issue for this at > https://github.com/xmonad/xmonad-contrib/issues ? I am not yet confident > I understand what is going on here well enough to know what the right fix > is, but if a ticket is created then it becomes easier for others to look at > it, and it won't accidentally be forgotten. Thanks! > > -Brent > > > On Wed, Nov 9, 2016 at 4:38 PM Eyal Erez wrote: > >> Hi Daniel, >> >> Thank you for your response. I've spent the last few days trying to >> compile and run xmonad locally without much success. >> Would there be any chance you could make this change so that it might get >> into 0.13 before it gets released? >> >> Otherwise, I'll continue to try and get xmonad to run locally. >> >> >> On Sun, Oct 23, 2016 at 6:32 AM, Daniel Wagner wrote: >> >> I think I'd consider that a bug, and it's probably easy enough to fix it. >> This is a guess based on reading the source, so you should verify for >> yourself whether this changes things appropriately, but... >> >> In XMonad.Layout.ThreeColumns.split3HorizontallyBy, swap the second two >> elements of the triple in the True branch, so that it reads: >> >> then ( Rectangle (sx + fromIntegral r3w) sy r1w sh >> , Rectangle sx sy r3w sh >> , Rectangle (sx + fromIntegral r3w + fromIntegral r1w) sy r2w sh >> ) >> >> ~d >> >> On Tue, Oct 18, 2016 at 12:02 AM, Eyal Erez wrote: >> >> Hi, >> >> I have an ultrawide monitor and so I use ThreeColumns most of the >> time. I create it like so: >> >> ThreeColMid 1 (3/100) (1/3) >> >> This works fine, however, I'm getting some strange behavior when >> creating an closing windows. I hope I can explain this with a small >> diagram which shows window location as I create and close apps: >> >> CREATE >> 1 [ a ] >> 2 [b][ a ] >> 3 [a][c][b] >> >> CLOSE >> 1 [a][c][b] >> 2 [b][ a ] >> 3 [ a ] >> >> So, when going from 2 to 3 open windows, window "a" and "b" switch >> location for some reason. in step #2 "b" is on the left and "a" is on >> the right, but when a third window is added (or removed) they swap >> locations. This is very confusing. >> >> Is there anyway I can cause this to stop happening? It would also be >> nice if window "b" was created into the active location, but that's >> more of a nitpick. >> >> Thank you >> >> -- >> There are 10 types of people, those who know binary and those who don't. >> >> >> >> >> >> >> >> >> _______________________________________________ >> xmonad mailing list >> xmonad at haskell.org >> http://mail.haskell.org/cgi-bin/mailman/listinfo/xmonad >> >> >> >> >> >> -- >> *Eyal Erez <**oneself at gmail.com* *>* >> >> There are 10 types of people, those who know binary and those who don't. >> >> _______________________________________________ >> xmonad mailing list >> xmonad at haskell.org >> http://mail.haskell.org/cgi-bin/mailman/listinfo/xmonad >> > -- *Eyal Erez <**oneself at gmail.com* *>* There are 10 types of people, those who know binary and those who don't. -------------- next part -------------- An HTML attachment was scrubbed... URL: From es at ethanschoonover.com Mon Jan 16 18:30:05 2017 From: es at ethanschoonover.com (Ethan Schoonover) Date: Mon, 16 Jan 2017 10:30:05 -0800 Subject: [xmonad] Issue with screenlocker obscured in background after display change In-Reply-To: <87ziiw3rqw.fsf@pmade.com> References: <87ziiw3rqw.fsf@pmade.com> Message-ID: Peter, thanks for the reply on this. I was testing further to see if I could mitigate it and have to provide some further information. I don't really know if this will let XMonad off the hook or if it in fact reveals a edge case issue: I realized that my screen switching script (which is triggered on udev events) included an "xmonad --restart" as xmobar was failing to reposition properly. I removed the restart from my script and the windows no longer appear in front of the screen locker. I still find it to be interesting/strange that a restart with titlebar decorations has different effects than restarting XMonad without titlebar decorations. I'm happy to submit an issue for this, though I realize that it's a weird edge case if even that. Cheers, Ethan Ethan Schoonover es at ethanschoonover.com @ethanschoonover http://ethanschoonover.com Freenode/Github: altercation On Thu, Jan 12, 2017 at 1:14 PM, Peter Jones wrote: > Ethan Schoonover > writes: >> A consistently reproducible problem involving titlebar decorations & >> screenlockers. I would have submitted an issue on github, but I'm not >> even sure if this is an XMonad core issue, an X.L.NoFrillsDecoration >> issue, a general decoration issue, or what, exactly. > > This is a very bizarre problem for sure. Open an issue under the > xmonad-contrib repository so it doesn't get swept under the rug. > > -- > Peter Jones, Founder, Devalot.com > Defending the honor of good code > > _______________________________________________ > xmonad mailing list > xmonad at haskell.org > http://mail.haskell.org/cgi-bin/mailman/listinfo/xmonad From allbery.b at gmail.com Mon Jan 16 19:00:42 2017 From: allbery.b at gmail.com (Brandon Allbery) Date: Mon, 16 Jan 2017 14:00:42 -0500 Subject: [xmonad] Issue with screenlocker obscured in background after display change In-Reply-To: References: <87ziiw3rqw.fsf@pmade.com> Message-ID: On Mon, Jan 16, 2017 at 1:30 PM, Ethan Schoonover wrote: > I still find it to be interesting/strange that a restart with titlebar > decorations has different effects than restarting XMonad without > titlebar decorations. > The Decoration module is a trainwreck. -- brandon s allbery kf8nh sine nomine associates allbery.b at gmail.com ballbery at sinenomine.net unix, openafs, kerberos, infrastructure, xmonad http://sinenomine.net -------------- next part -------------- An HTML attachment was scrubbed... URL: From jschwab at gmail.com Tue Jan 17 16:56:10 2017 From: jschwab at gmail.com (Josiah Schwab) Date: Tue, 17 Jan 2017 08:56:10 -0800 Subject: [xmonad] Starting Audacity under Xmonad triggers end of user session Message-ID: <87h94xvd5h.fsf@gmail.com> Hello, I am using xmonad on Arch Linux on a ThinkPad X1 Carbon (Gen 4). Over the past few months, I have occasionally had issues where my X session suddenly ends and I am dumped back into my display manager. There is no relevant information in /var/log/Xorg.0.log.old, simply the line [ 4566.334] (II) Server terminated successfully (0). Closing log file The only relevant lines I see in the journal are: Jan 17 08:26:55 monolith lightdm[31036]: pam_unix(lightdm:session): session closed for user jschwab Jan 17 08:26:55 monolith org.a11y.atspi.Registry[31192]: XIO: fatal IO error 11 (Resource temporarily unavailable) on X server ":0" Jan 17 08:26:55 monolith org.a11y.atspi.Registry[31192]: after 885 requests (885 known processed) with 0 events remaining. I finally found a 100% reproducible case, which is to launch the program audacity. I confirmed that this issue occurs using the example xmonad configuration shipped with the Arch Linux package (/usr/share/x86_64-linux-ghc-8.0.1/xmonad-0.12/man/xmonad.hs). I suspect that xmonad is at least a contributing factor, because I installed another window manager (openbox) and confirmed that the problem does not occur there. I also confirmed that the issue occurs with the xmonad-git and xmonad-contrib-git packages, which track master on GitHub, so this hasn't been fixed since 0.12. Does anyone have any suggestions on how to track down the source of this problem? Josiah P.S. This was cross-posted on the Arch Linux forums. https://bbs.archlinux.org/viewtopic.php?pid=1684595 From asjo at koldfront.dk Tue Jan 17 17:29:19 2017 From: asjo at koldfront.dk (Adam =?utf-8?Q?Sj=C3=B8gren?=) Date: Tue, 17 Jan 2017 18:29:19 +0100 Subject: [xmonad] Starting Audacity under Xmonad triggers end of user session References: <87h94xvd5h.fsf@gmail.com> Message-ID: <87o9z5egsw.fsf@koldfront.dk> Josiah writes: > I finally found a 100% reproducible case, which is to launch the program > audacity. I can't reproduce this on my machine (which also happens to be an X1 carbon) - however, one tip is to look in ~/.xsession-errors after the crash occurs, and see if that provides any indication of the cause. It might very well be getWindowAttributes, as discussed here: · https://github.com/xmonad/xmonad/issues/70 Best regards, Adam -- "Do I really want to set this in Denmark?" Adam Sjøgren asjo at koldfront.dk From jschwab at gmail.com Tue Jan 17 17:55:19 2017 From: jschwab at gmail.com (Josiah Schwab) Date: Tue, 17 Jan 2017 09:55:19 -0800 Subject: [xmonad] Starting Audacity under Xmonad triggers end of user session In-Reply-To: <87o9z5egsw.fsf@koldfront.dk> References: <87h94xvd5h.fsf@gmail.com> <87o9z5egsw.fsf@koldfront.dk> Message-ID: <8760ldlgfs.fsf@gmail.com> Hi Adam, > I can't reproduce this on my machine (which also happens to be an X1 > carbon) - however, one tip is to look in ~/.xsession-errors after the > crash occurs, and see if that provides any indication of the cause. Thank you for that suggestion. I had forgotten about that file. > It might very well be getWindowAttributes, as discussed here: > > · https://github.com/xmonad/xmonad/issues/70 Indeed that is it. I've got the line xmonad-x86_64-linux: user error (Error in function getWindowAttributes) sitting in my ~/.xsession-errors.old. I'll read through that GitHub issue to learn more. Josiah