'Re: [xmonad] xmonad becomes inoperable in random situations'

[prev in list] [next in list] [prev in thread] [next in thread] 

List:       xmonad
Subject:    Re: [xmonad] xmonad becomes inoperable in random situations
From:       Platon Pronko <platon7pronko () gmail ! com>
Date:       2021-09-21 4:59:16
Message-ID: 2c09f32f-b9d0-e74d-d25a-f31f4452590a () gmail ! com
[Download RAW message or body]

Hi!

hPutStrLn is needed here to send the current window title to xmobar (you have the \
current window title displayed in your bottom bar, and that's how it gets it). So \
removing it from xmprocB will result in no window title being displayed.

Can you still unfreeze your system by killing the xmobar? If yes, then which one do \
you need to kill - top or bottom?

Best regards,
Platon Pronko

On 2021-09-20 23:03, Björn Kessler wrote:
> Sorry, back again.
> 
> Seems like I celebrated to early. It happened again. But to me it seems as
> if it was much later then normally. I never understood, what the hPutStrLn
> is for. Would it be worth a try to remove it from xmprocB too?
> 
> With kind regards,
> 
> Bjoern
> 
> Am Mo., 20. Sept. 2021 um 21:39 Uhr schrieb Björn Kessler <
> bjoern.lindig@gmail.com>:
> 
> > Hey Platon,
> > 
> > this is really great! It seems you've hit the nail to its head. The system
> > runs every test safe and easy. I forgot how comfortable it is to have a
> > reliable system! Seriously! This is just wonderful!
> > 
> > Thank you so much!
> > 
> > Best Bjoern
> > 
> > Am Mo., 20. Sept. 2021 um 19:48 Uhr schrieb Platon Pronko <
> > platon7pronko@gmail.com>:
> > 
> > > Hi!
> > > 
> > > Just a stab in the dark, but can you try removing `hPutStrLn xmprocT`
> > > from ppOutput?
> > > I suspect that without StdinReader your top xmobar just never reads its
> > > stdin, but Xmonad continues to send it the output until it hits the
> > > pipe limit, and after that everything blocks.
> > > 
> > > Best regards,
> > > Platon Pronko
> > > 
> > > On 2021-09-20 20:32, Björn Kessler wrote:
> > > > Hey Platon,
> > > > 
> > > > thanks for the hint. Somehow it didn't come to my mind to try that.
> > > > Actually I was fiddling around a lot on my Xmonad config because I
> > > wanted
> > > > to have both a bar on top and on the bottom of the screen. And as it
> > > turns
> > > > out you where right. If I violently kill xmobar after the issue occurs,
> > > > everything works fine again.
> > > > 
> > > > Hm, so what did I do wrong?
> > > > 
> > > > I've created a pastie with my config in case someone is having the time
> > > to
> > > > check it. It would be awesome!
> > > > 
> > > > https://pastie.iem.at/view/d4d44ce1   --> xmonad.hs
> > > > https://pastie.iem.at/view/9374a807   --> xmobar-top.hs
> > > > https://pastie.iem.at/view/189e5014   --> xmobar-buttom.hs
> > > > 
> > > > Best,
> > > > 
> > > > Bjoern
> > > > 
> > > > Am So., 19. Sept. 2021 um 18:46 Uhr schrieb Platon Pronko <
> > > > platon7pronko@gmail.com>:
> > > > 
> > > > > Hi!
> > > > > 
> > > > > I'm not an expert in this by any means, but I'll try giving some
> > > pointers
> > > > > in case you haven't explored them already.
> > > > > 
> > > > > Have you looked at the `top` output to see what process is consuming
> > > > > CPU or disk resources? Since you say that only X is affected, then ttys
> > > > > should be available on Ctrl-Alt-F2 (3,4,etc) and you can run top there.
> > > > > 
> > > > > How complex is your Xmonad config? Have you tried removing most
> > > > > customizations
> > > > > and running the simplest config possible?
> > > > > 
> > > > > I doubt that rotated monitor is relevant here, but you can easily check
> > > > > that -
> > > > > just run non-rotated monitor for a while, after the first time it
> > > freezes
> > > > > again
> > > > > you will be sure that rotated monitor wasn't the issue.
> > > > > 
> > > > > Best regards,
> > > > > Platon Pronko
> > > > > 
> > > > > On 2021-09-18 14:35, Björn Kessler wrote:
> > > > > > Hi there,
> > > > > > 
> > > > > > I'm new to the list and poppin in with a question. But before getting
> > > to
> > > > > > that, I would like to send out a big "thank you" to the community,
> > > that
> > > > > is
> > > > > > providing this greatest windowmanager ever! I'm using it since more
> > > than
> > > > > 5
> > > > > > years now and never had an issue...
> > > > > > 
> > > > > > ... up to now: My xmonad is freezing again and again and I don't
> > > really
> > > > > > know how to figure out what causes the issue. It happens when I use
> > > > > > programs like musescore or radium. I don't know, maybe because they
> > > put
> > > > > > heavy load on graphics or something!? Anyway, when it happens, some
> > > > > > functionalities of the program stay functional, but changing the
> > > screen
> > > > > in
> > > > > > xmonad or starting new programms via dmenu is impossible then.
> > > > > > 
> > > > > > I'm on archlinux and xmonad.errors doesn't show anything, as far as I
> > > can
> > > > > > see. I'm using xorg and I'm launching it with startx from the command
> > > > > > prompt.
> > > > > > 
> > > > > > In my Xorg.0.log I get the following error:
> > > > > > 
> > > > > > > [  6588.014] (EE) event6  - LITE-ON Technology USB NetVista Full
> > > Width
> > > > > > Keyboard.: client bug: event processing lagging behind by 13ms, your
> > > > > system
> > > > > > is too slow
> > > > > > 
> > > > > > The slowest device in my setup is the harddrive. I now it needs
> > > > > replacement
> > > > > > soon. Can it be, that X freezes because of a slow harddrive?
> > > > > > 
> > > > > > I'm also using a rotated monitor. Can it be that the issue is
> > > concerned
> > > > > > with the portrait view?
> > > > > > 
> > > > > > Here is my script that I use to do the rotation
> > > > > > > xrandr --output VGA-1 --off --output DP-1 --off --output  HDMI-1
> > > --off
> > > > > > --output DP-2 --mode 1680x1050 --pos 0x0  --rotate left --output
> > > HDMI-2
> > > > > > --off
> > > > > > 
> > > > > > If someone is having any idea on how to narrow this down, I'd be very
> > > > > > thankfull. Even only to figure out whether it is concerned with
> > > xmonad or
> > > > > > not, would help a lot. I'm suspecting xmonad, because after killing it
> > > > > and
> > > > > > restarting X everything works fine again, but I know that by killing
> > > > > xmonad
> > > > > > I'm also stopping a whole lot of other processes too...
> > > > > > 
> > > > > > With kind regards,
> > > > > > 
> > > > > > Bjroern
> > > > > > 
> > > > > > 
> > > > > > _______________________________________________
> > > > > > xmonad mailing list
> > > > > > xmonad@haskell.org
> > > > > > http://mail.haskell.org/cgi-bin/mailman/listinfo/xmonad
> > > > > > 
> > > > > _______________________________________________
> > > > > xmonad mailing list
> > > > > xmonad@haskell.org
> > > > > http://mail.haskell.org/cgi-bin/mailman/listinfo/xmonad
> > > > > 
> > > > 
> > > 
> > 
> 
_______________________________________________
xmonad mailing list
xmonad@haskell.org
http://mail.haskell.org/cgi-bin/mailman/listinfo/xmonad

[prev in list] [next in list] [prev in thread] [next in thread] 