Logs: liberachat/#xmonad
| 2022-11-04 18:26:16 | <jabuxas> | my bad |
| 2022-11-04 18:28:05 | <geekosaur> | I have a still-undiagnosed situation where something is eating all of my memory and OOMing, and xmonad disappears without a log message (strongly suggesting it's xmonad that is OOMing, but I can't see how) |
| 2022-11-04 18:28:33 | <geekosaur> | but it leaves the rest of my session because I run xmonad under MATE so mate-session is still running |
| 2022-11-04 18:29:12 | <geekosaur> | was wondering of that might be related, but unless you're running under a session manager xmonad OOMing would kill your session |
| 2022-11-04 18:29:16 | <geekosaur> | *if that |
| 2022-11-04 18:29:53 | <geekosaur> | might use top if you can get something to respond (already-open terminal?) to see what's spinning |
| 2022-11-04 18:30:47 | <jabuxas> | yeah I'll remember to do that, i usually have a terminal open either way |
| 2022-11-04 18:31:29 | <geekosaur> | but that again might require a session manager if xmonad is what's spinning, since it would presumably ignore switching focus in that situation |
| 2022-11-04 18:32:34 | <jabuxas> | oh it does respond to focus |
| 2022-11-04 18:32:41 | <geekosaur> | hm, I can open a terminal without requiring xmonad but if it were still running it'd have to manage it. so still wouldn't help |
| 2022-11-04 18:32:45 | <geekosaur> | oh goood |
| 2022-11-04 18:33:59 | <jabuxas> | by session manager do you mean a display manager like sddm or lightdm? |
| 2022-11-04 18:34:20 | <geekosaur> | no, something like xfce4-session or mate-session |
| 2022-11-04 18:34:32 | <geekosaur> | or even a minimal one like xsm |
| 2022-11-04 18:34:45 | <jabuxas> | oh i dont have that |
| 2022-11-04 18:35:31 | <jabuxas> | well even if it lost focus, i could still switch to a tty and do top there |
| 2022-11-04 18:35:39 | <geekosaur> | I rely on that to get5 things running again if I manage to crash xmonad, since (1) my session keeps running (2) I can pop a terminal via the mate menu without a window manager being involved, and restart xmonad from there |
| 2022-11-04 18:35:45 | <jabuxas> | now i am kinda hoping it crashes again so i can figure out what it culd be |
| 2022-11-04 18:36:58 | <jabuxas> | with the way my config is now, if i were to use xmonad with a DE would I really need to change anything? |
| 2022-11-04 18:37:23 | <jabuxas> | i looked at xmonad.config.xfce and it just does ewmh stuff, no? |
| 2022-11-04 18:38:29 | <geekosaur> | also swaps mod-shift-q to the xfce logout dialog and mod-p (or maybe mod-shift-p) to its run dialog |
| 2022-11-04 18:39:16 | <geekosaur> | xfce's one of the more minimal integrations; mate integration also includes some dbus stuff to tell the session manager that xmonad has started |
| 2022-11-04 18:40:36 | <geekosaur> | if you did want to log some xmobar-like stuff under xfce, you'd either have to configure xmobar to display somewhere other than where xfce4-panel was or you'd have to build the xfce flavor of xmonad-log-applet and plumb it into your config manually because it uses dbus |
| 2022-11-04 18:43:37 | <jabuxas> | my xfce panel is on the left of the screen and xmobar on top, but even like that both were invisible, no idea what happened. i might try it out at a later date if i have time |
| 2022-11-04 18:43:44 | <jabuxas> | for now everything is working |
| 2022-11-04 18:44:24 | <jabuxas> | ty again geekosaur |
| 2022-11-04 18:51:43 | → | darkkaster joins (~user@206.62.170.243) |
| 2022-11-04 18:53:25 | <darkkaster> | I get this error when I start xorg https://termbin.com/omhg |
| 2022-11-04 18:59:32 | × | darkkaster quits (~user@206.62.170.243) (Quit: ERC 5.4 (IRC client for GNU Emacs 28.2)) |
| 2022-11-04 19:02:01 | → | darkkaster joins (~user@206.62.170.243) |
| 2022-11-04 19:02:44 | <geekosaur> | are you just runing xmonad at a terminal? |
| 2022-11-04 19:03:04 | <geekosaur> | hm, no, that would be an openDisplay error |
| 2022-11-04 19:04:04 | <geekosaur> | but we only use the required Atoms on startup, and should be creating e.g. the EWMH atoms as needed |
| 2022-11-04 19:04:27 | <darkkaster> | i run xmonad using xinitrc but redirect the output to a text file |
| 2022-11-04 19:08:27 | × | jao quits (~jao@cpc103048-sgyl39-2-0-cust502.18-2.cable.virginm.net) (Ping timeout: 272 seconds) |
| 2022-11-04 19:12:02 | <geekosaur> | X_ChangeProperty error… doesn't seem like we should be doing that |
| 2022-11-04 19:12:31 | <geekosaur> | oh, WM_STATE. but if that atom's not defined (or its type isn't defined) there should be bigger problems than just xmonad failing |
| 2022-11-04 19:12:50 | → | sogens joins (sogens@gateway/vpn/protonvpn/sogens) |
| 2022-11-04 19:14:00 | <geekosaur> | sometimes I wish we used the standard error reporter, be nice to have a clue about where / when this was failing |
| 2022-11-04 19:14:11 | <geekosaur> | then again xmonad should be continuing after this |
| 2022-11-04 19:14:23 | <geekosaur> | because the error handler we use tries to recover |
| 2022-11-04 19:17:30 | × | darkkaster quits (~user@206.62.170.243) (Remote host closed the connection) |
| 2022-11-04 19:19:50 | → | darkkaster joins (~user@206.62.170.243) |
| 2022-11-04 19:22:12 | × | darkkaster quits (~user@206.62.170.243) (Remote host closed the connection) |
| 2022-11-04 19:48:56 | → | Guest47 joins (~Guest47@171.79.46.173) |
| 2022-11-04 19:56:32 | <jabuxas> | is this normal? https://0x0.st/ogUD.png both xmobars consuming ~4% cpu |
| 2022-11-04 20:01:38 | × | Guest47 quits (~Guest47@171.79.46.173) (Ping timeout: 260 seconds) |
| 2022-11-04 20:12:04 | geekosaur | has no clue |
| 2022-11-04 20:18:12 | <jabuxas> | Solid, what do you think? |
| 2022-11-04 20:19:10 | <geekosaur> | istr that liskin worked a bit on xmobar performance, but I don't know what current "normal" is |
| 2022-11-04 20:55:26 | × | td_ quits (~td@83.135.9.48) (Read error: error:1408F10B:SSL routines:ssl3_get_record:wrong version number) |
| 2022-11-04 21:00:43 | → | td_ joins (~td@83.135.9.48) |
| 2022-11-04 21:08:01 | → | jao joins (~jao@cpc103048-sgyl39-2-0-cust502.18-2.cable.virginm.net) |
| 2022-11-04 21:09:42 | <jabuxas> | hmm |
| 2022-11-04 21:11:19 | × | td_ quits (~td@83.135.9.48) (Ping timeout: 272 seconds) |
| 2022-11-04 21:13:01 | → | td_ joins (~td@83.135.9.48) |
| 2022-11-04 21:37:45 | × | mncheck quits (~mncheck@193.224.205.254) (Ping timeout: 255 seconds) |
| 2022-11-04 21:49:28 | → | mojowings[m] joins (~mojowings@2001:470:69fc:105::2:b42f) |
| 2022-11-04 21:51:20 | <mojowings[m]> | I have a system 76 laptop with integrated and nvidia graphics. I have used xmonad for years but my actual understanding of WM related things is sadly shallow so apologies for the potentially simple question. |
| 2022-11-04 21:54:26 | <mojowings[m]> | * I have a system 76 laptop with integrated and nvidia graphics. I have used xmonad for years but my actual understanding of WM related things is sadly shallow so apologies for the potentially simple question. |
| 2022-11-04 21:54:26 | <mojowings[m]> | When I set hybrid use of integrated and nvidia (or strict use of nvidia), starting xmonad with startx results in an entirely black screen where I am unable to open terminals. Xmonad is running and does not crash. If I restrict to integrated only, then I can use xmonad as expected. I am happy to investigate anything on my end to facilitate this, but I'm unsure where to start. |
| 2022-11-04 21:55:50 | <mojowings[m]> | * I have a system 76 laptop with integrated and nvidia graphics. I have used xmonad for years but my actual understanding of WM related things is sadly shallow so apologies for the potentially simple question. |
| 2022-11-04 21:55:50 | <mojowings[m]> | When I set hybrid use of integrated and nvidia (or strict use of nvidia), starting xmonad with startx (or via the login manager) results in an entirely black screen where I am unable to open terminals. Xmonad is running and does not crash. If I restrict to integrated only, then I can use xmonad as expected. I am happy to investigate anything on my end to facilitate this, but I'm unsure where to start. |
| 2022-11-04 21:59:31 | <jabuxas> | what distro are you using and how are the drivers installed? |
| 2022-11-04 22:00:35 | <mojowings[m]> | I am using pop!_os which handles these things for me. |
| 2022-11-04 22:02:07 | <jabuxas> | oh yeah stupid question of me, totally forgot pop os is from system76 |
| 2022-11-04 22:03:05 | <jabuxas> | do you have any other wm installed where you can try and launch to see if it works as expected? |
| 2022-11-04 22:03:16 | <mojowings[m]> | * No worries! I am usually a debian or ubuntu user but pop os is based on ubuntu. Typically xmonad works fine for me on ubuntu so I was surprised by this. |
| 2022-11-04 22:04:54 | <mojowings[m]> | ahhh no i dont. it does work in integrated only mode. i wish there was a straightforward way to debug this but it probably involves x11 understanding etc... |
| 2022-11-04 22:15:09 | <geekosaur> | can you post your Xorg.0.log to a pastebin? |
| 2022-11-04 22:15:13 | <geekosaur> | @where paste |
| 2022-11-04 22:15:13 | <lambdabot> | Help us help you: please paste full code, input and/or output at e.g. https://paste.tomsmeding.com |
| 2022-11-04 22:15:35 | <geekosaur> | should be /var/log/Xorg.0.log |
| 2022-11-04 22:41:05 | × | thaumavorio quits (~thaumavor@thaumavor.io) (Quit: ZNC 1.8.2 - https://znc.in) |
| 2022-11-04 22:43:36 | × | stackdroid18 quits (14094@user/stackdroid) (Quit: hasta la vista... tchau!) |
| 2022-11-04 22:43:59 | → | thaumavorio joins (~thaumavor@thaumavor.io) |
| 2022-11-04 22:44:26 | → | sadmax joins (~user@209.205.174.253) |
| 2022-11-04 22:47:51 | × | sadmax quits (~user@209.205.174.253) (Remote host closed the connection) |
| 2022-11-04 22:48:41 | → | sadmax joins (~user@209.205.174.253) |
| 2022-11-04 22:51:22 | × | sadmax quits (~user@209.205.174.253) (Remote host closed the connection) |
| 2022-11-04 22:52:14 | × | sogens quits (sogens@gateway/vpn/protonvpn/sogens) (Ping timeout: 246 seconds) |
| 2022-11-04 22:53:07 | → | sadmax joins (~user@209.205.174.253) |
| 2022-11-04 22:53:31 | × | sadmax quits (~user@209.205.174.253) (Remote host closed the connection) |
| 2022-11-04 22:54:13 | → | sadmax joins (~user@209.205.174.253) |
| 2022-11-04 22:55:09 | → | sogens joins (sogens@gateway/vpn/protonvpn/sogens) |
| 2022-11-04 22:55:17 | × | sadmax quits (~user@209.205.174.253) (Remote host closed the connection) |
| 2022-11-04 22:56:46 | → | sadmax joins (~user@209.205.174.253) |
| 2022-11-04 22:57:53 | × | sadmax quits (~user@209.205.174.253) (Remote host closed the connection) |
| 2022-11-04 22:58:45 | → | sadmax joins (~user@209.205.174.253) |
| 2022-11-04 23:04:03 | → | sadmax22 joins (~user@209.205.174.253) |
| 2022-11-04 23:04:23 | × | sadmax quits (~user@209.205.174.253) (Remote host closed the connection) |
| 2022-11-04 23:04:25 | × | sadmax22 quits (~user@209.205.174.253) (Remote host closed the connection) |
| 2022-11-04 23:09:33 | × | sogens quits (sogens@gateway/vpn/protonvpn/sogens) (Ping timeout: 255 seconds) |
| 2022-11-04 23:16:43 | × | chomwitt quits (~chomwitt@athedsl-351939.home.otenet.gr) (Ping timeout: 272 seconds) |
| 2022-11-05 00:21:19 | × | tremon quits (~tremon@83-84-18-241.cable.dynamic.v4.ziggo.nl) (Quit: getting boxed in) |
| 2022-11-05 00:29:46 | → | mvk joins (~mvk@2607:fea8:5ce3:8500::4b68) |
| 2022-11-05 02:02:47 | × | jabuxas quits (~jabuxas@user/jabuxas) (Read error: Connection reset by peer) |
| 2022-11-05 02:06:27 | × | rundown quits (~eb0t@90.202.12.12) (Ping timeout: 272 seconds) |
| 2022-11-05 02:08:06 | → | rundown joins (~eb0t@33ba0477.skybroadband.com) |
| 2022-11-05 02:17:30 | → | sogens joins (sogens@gateway/vpn/protonvpn/sogens) |
All times are in UTC.