From tomi at nomi.cz  Wed Oct  4 10:05:08 2023
From: tomi at nomi.cz (Tomas Janousek)
Date: Wed, 4 Oct 2023 11:05:08 +0100
Subject: [xmonad] Fwd: [geekosaur/xmonad-contrib] Run failed: Packdeps -
 master (0e2d3c1)
In-Reply-To: <9aa8f35012839698096c0fa80958b4db2e51967f.camel@joachim-breitner.de>
References: <geekosaur/xmonad-contrib/check-suites/CS_kwDOFKxMq88AAAADx15wNw/1694834033@github.com>
 <CAKFCL4U_eDuCp4njFbigE8dmOpKB8tc3+k7BhCD8EemGSHJWoA@mail.gmail.com>
 <ZQXv9f5OE42Xc1NA@nomi.cz>
 <a98a3bc32f81b397674c5e5f1a400257f477ab69.camel@joachim-breitner.de>
 <87y1h4hxwf.fsf@hyperspace> <ZQgTNTjNFJcxaOAJ@nomi.cz>
 <9aa8f35012839698096c0fa80958b4db2e51967f.camel@joachim-breitner.de>
Message-ID: <ZR041BGHyZhXoxWb@nomi.cz>

Hi Joachim,

On Thu, Sep 21, 2023 at 12:21:04PM +0200, Joachim Breitner wrote:
>See https://github.com/haskell-CI/haskell-ci/issues/667 if you care
>about this. I built https://github.com/nomeata/cabal-force-upper-bound
>so that on can make a CI matrix that exercises the upper bounds, but it
>hasn’t been integrated into haskell-ci so far.

Nice! Subscribed to the issue(s) so we can adopt it once it becomes 
easier to do so. Thank you :-)

-- 
Tomáš "liskin" ("Pivník") Janoušek, https://lisk.in/
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mail.haskell.org/pipermail/xmonad/attachments/20231004/1075e9c6/attachment.html>

From jandetke at outlook.com  Thu Oct 19 15:04:02 2023
From: jandetke at outlook.com (Jan Detke)
Date: Thu, 19 Oct 2023 17:04:02 +0200
Subject: [xmonad] Broken Xmonad after updates
Message-ID: <PAVPR08MB9401EA35CA326B98300A072EC2D4A@PAVPR08MB9401.eurprd08.prod.outlook.com>

Hi,

today I moved my xmonad.hs config from $HOME/.xmonad to $HOME/.config/xmonad. After that I was unable to recompile xmonad. I then moved it back into $HOME/.xmonad but the issue was still persistent. It was unable to load the libraries even though I had not changed them at all.

After rebooting and updating the system I tried recompiling again with the following result:

xmonad --recompile --verbose
XMonad is recompiling and replacing itself with another XMonad process because the current process is called "xmonad" but the compiled configuration should be called "xmonad-x86_64-linux"
XMonad will use ghc to recompile, because neither "/home/jan/.xmonad/build" nor "/home/jan/.xmonad/stack.yaml" exists.
XMonad skipping recompile because it is not forced (e.g. via --recompile), and neither xmonad.hs nor any *.hs / *.lhs / *.hsc files in lib/ have been changed.
/home/jan/.xmonad/xmonad-x86_64-linux: error while loading shared libraries: libHSxmonad-contrib-0.17.1-2BxpGTW6opKG3sVOzMilq0-ghc9.0.2.so: cannot open shared object file: No such file or directory

So far I have read this issue https://github.com/xmonad/xmonad/issues/301. I am wondering if this is the only option for me here too.

I installed Xmonad via pacman.

Best regards
Jan

From allbery.b at gmail.com  Thu Oct 19 15:08:41 2023
From: allbery.b at gmail.com (Brandon Allbery)
Date: Thu, 19 Oct 2023 11:08:41 -0400
Subject: [xmonad] Broken Xmonad after updates
In-Reply-To: <PAVPR08MB9401EA35CA326B98300A072EC2D4A@PAVPR08MB9401.eurprd08.prod.outlook.com>
References: <PAVPR08MB9401EA35CA326B98300A072EC2D4A@PAVPR08MB9401.eurprd08.prod.outlook.com>
Message-ID: <CAKFCL4W7jn5rLoA+6WCP8TLcikkUHEtpvKB7Fpom87J4ewx4dg@mail.gmail.com>

Essentially yes. Arch and derivatives insist on using dynamic linking, and
you must rebuild your config after every system update to ensure it still
works. We strongly recommend you use `stack` or `cabal` instead, and
install `xmonad` and `xmonad-contrib` from Hackage. If you choose not to do
so, see
https://wiki.archlinux.org/title/Xmonad#Problems_with_finding_shared_libraries_after_update

On Thu, Oct 19, 2023 at 11:04 AM Jan Detke <jandetke at outlook.com> wrote:

> Hi,
>
> today I moved my xmonad.hs config from $HOME/.xmonad to
> $HOME/.config/xmonad. After that I was unable to recompile xmonad. I then
> moved it back into $HOME/.xmonad but the issue was still persistent. It was
> unable to load the libraries even though I had not changed them at all.
>
> After rebooting and updating the system I tried recompiling again with the
> following result:
>
> xmonad --recompile --verbose
> XMonad is recompiling and replacing itself with another XMonad process
> because the current process is called "xmonad" but the compiled
> configuration should be called "xmonad-x86_64-linux"
> XMonad will use ghc to recompile, because neither
> "/home/jan/.xmonad/build" nor "/home/jan/.xmonad/stack.yaml" exists.
> XMonad skipping recompile because it is not forced (e.g. via --recompile),
> and neither xmonad.hs nor any *.hs / *.lhs / *.hsc files in lib/ have been
> changed.
> /home/jan/.xmonad/xmonad-x86_64-linux: error while loading shared
> libraries: libHSxmonad-contrib-0.17.1-2BxpGTW6opKG3sVOzMilq0-ghc9.0.2.so:
> cannot open shared object file: No such file or directory
>
> So far I have read this issue https://github.com/xmonad/xmonad/issues/301.
> I am wondering if this is the only option for me here too.
>
> I installed Xmonad via pacman.
>
> Best regards
> Jan
> _______________________________________________
> xmonad mailing list
> xmonad at haskell.org
> http://mail.haskell.org/cgi-bin/mailman/listinfo/xmonad
>


-- 
brandon s allbery kf8nh
allbery.b at gmail.com
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mail.haskell.org/pipermail/xmonad/attachments/20231019/aa2ee7be/attachment.html>

From jandetke at outlook.com  Sun Oct 22 15:11:16 2023
From: jandetke at outlook.com (Jan Detke)
Date: Sun, 22 Oct 2023 17:11:16 +0200
Subject: [xmonad] Broken Xmonad after updates
In-Reply-To: <CAKFCL4W7jn5rLoA+6WCP8TLcikkUHEtpvKB7Fpom87J4ewx4dg@mail.gmail.com>
References: <PAVPR08MB9401EA35CA326B98300A072EC2D4A@PAVPR08MB9401.eurprd08.prod.outlook.com>
 <CAKFCL4W7jn5rLoA+6WCP8TLcikkUHEtpvKB7Fpom87J4ewx4dg@mail.gmail.com>
Message-ID: <PAVPR08MB9401ABE8BC1DC21CE1AF05B7C2D9A@PAVPR08MB9401.eurprd08.prod.outlook.com>

Brandon Allbery <allbery.b at gmail.com> writes:

> Essentially yes. Arch and derivatives insist on using dynamic linking, and
> you must rebuild your config after every system update to ensure it still
> works. We strongly recommend you use `stack` or `cabal` instead, and
> install `xmonad` and `xmonad-contrib` from Hackage. If you choose not to do
> so, see
> https://wiki.archlinux.org/title/Xmonad#Problems_with_finding_shared_libraries_after_update

So I went the route of removing everything related to haskell, ghci and cabal from my system and followed the instructions of installing and setting up xmonad with stack. The installation went through and xmonad is recompiling under the usage of the given bash script (which invokes stack build). There are no errors given to me but I noticed that there is no 'xmonad-x86_64-linux' executable generated in my folder after running the script. In fact there is an executable created called '-lm' but I do not know if this is just an issue related to the filename or something else wrong here.

I followed these instructions on installing xmonad via stack: https://github.com/xmonad/xmonad/blob/883143fd5895e0da4ee8e50722e3011cf30e2ca6/INSTALL.md

Can you help me out here?

Best regards
Jan

From allbery.b at gmail.com  Sun Oct 22 16:41:20 2023
From: allbery.b at gmail.com (Brandon Allbery)
Date: Sun, 22 Oct 2023 12:41:20 -0400
Subject: [xmonad] Broken Xmonad after updates
In-Reply-To: <PAVPR08MB9401ABE8BC1DC21CE1AF05B7C2D9A@PAVPR08MB9401.eurprd08.prod.outlook.com>
References: <PAVPR08MB9401EA35CA326B98300A072EC2D4A@PAVPR08MB9401.eurprd08.prod.outlook.com>
 <CAKFCL4W7jn5rLoA+6WCP8TLcikkUHEtpvKB7Fpom87J4ewx4dg@mail.gmail.com>
 <PAVPR08MB9401ABE8BC1DC21CE1AF05B7C2D9A@PAVPR08MB9401.eurprd08.prod.outlook.com>
Message-ID: <CAKFCL4X=F1MTJrO4fb=9iqZUo=0Vydp0+JbV6S4s1uvLLj4DBA@mail.gmail.com>

I'm looking at that page, and aside from one slight documentation bug that
doesn't really affect anything here it looks correct to me and shouldn't be
able to get the wrong executable name unless something has gone wrong
inside xmonad's compile logic. Although that also looks out of date: we
support stack building directly, so xmonad should use essentially that
build script itself when it sees a `stack.yaml` file.

You probably want to use the latest version of the install documentation:
https://github.com/xmonad/xmonad/blob/master/INSTALL.md#build-using-stack

On Sun, Oct 22, 2023 at 11:11 AM Jan Detke <jandetke at outlook.com> wrote:

> Brandon Allbery <allbery.b at gmail.com> writes:
>
> > Essentially yes. Arch and derivatives insist on using dynamic linking,
> and
> > you must rebuild your config after every system update to ensure it still
> > works. We strongly recommend you use `stack` or `cabal` instead, and
> > install `xmonad` and `xmonad-contrib` from Hackage. If you choose not to
> do
> > so, see
> >
> https://wiki.archlinux.org/title/Xmonad#Problems_with_finding_shared_libraries_after_update
>
> So I went the route of removing everything related to haskell, ghci and
> cabal from my system and followed the instructions of installing and
> setting up xmonad with stack. The installation went through and xmonad is
> recompiling under the usage of the given bash script (which invokes stack
> build). There are no errors given to me but I noticed that there is no
> 'xmonad-x86_64-linux' executable generated in my folder after running the
> script. In fact there is an executable created called '-lm' but I do not
> know if this is just an issue related to the filename or something else
> wrong here.
>
> I followed these instructions on installing xmonad via stack:
> https://github.com/xmonad/xmonad/blob/883143fd5895e0da4ee8e50722e3011cf30e2ca6/INSTALL.md
>
> Can you help me out here?
>
> Best regards
> Jan
>


-- 
brandon s allbery kf8nh
allbery.b at gmail.com
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mail.haskell.org/pipermail/xmonad/attachments/20231022/5ddbb807/attachment.html>

From jandetke at outlook.com  Sun Oct 22 19:03:41 2023
From: jandetke at outlook.com (Jan Detke)
Date: Sun, 22 Oct 2023 21:03:41 +0200
Subject: [xmonad] Broken Xmonad after updates
In-Reply-To: <CAKFCL4X=F1MTJrO4fb=9iqZUo=0Vydp0+JbV6S4s1uvLLj4DBA@mail.gmail.com>
References: <PAVPR08MB9401EA35CA326B98300A072EC2D4A@PAVPR08MB9401.eurprd08.prod.outlook.com>
 <CAKFCL4W7jn5rLoA+6WCP8TLcikkUHEtpvKB7Fpom87J4ewx4dg@mail.gmail.com>
 <PAVPR08MB9401ABE8BC1DC21CE1AF05B7C2D9A@PAVPR08MB9401.eurprd08.prod.outlook.com>
 <CAKFCL4X=F1MTJrO4fb=9iqZUo=0Vydp0+JbV6S4s1uvLLj4DBA@mail.gmail.com>
Message-ID: <PAVPR08MB9401AB3D682FCEA874B7CF9BC2D9A@PAVPR08MB9401.eurprd08.prod.outlook.com>

Brandon Allbery <allbery.b at gmail.com> writes:

> I'm looking at that page, and aside from one slight documentation bug that
> doesn't really affect anything here it looks correct to me and shouldn't be
> able to get the wrong executable name unless something has gone wrong
> inside xmonad's compile logic. Although that also looks out of date: we
> support stack building directly, so xmonad should use essentially that
> build script itself when it sees a `stack.yaml` file.
>
> You probably want to use the latest version of the install documentation:
> https://github.com/xmonad/xmonad/blob/master/INSTALL.md#build-using-stack
>
I found the executable under '$HOME/.cache/xmonad/'. Is this the intendet location for the executable? I assumed that it would reside in the directory where my xmonad.hs and the build script are located.

Additionally, I tried starting xmonad outside of my display manager that did not work out. I will look deeper into xinit for this regard - but as a short notice: I loggend in a tty, ran startx (with some warnings) and then xmonad. The received output was 'xmonad-x86_64-linux: user error (openDisplay)', which indicates that the xserver is not running properly.

I will try to fall back to my display manager by creating a desktop entry for xmonad under '/usr/share/xsessions/', but that is a task for tomorrow.

Thanks again
Jan

From allbery.b at gmail.com  Sun Oct 22 19:10:23 2023
From: allbery.b at gmail.com (Brandon Allbery)
Date: Sun, 22 Oct 2023 15:10:23 -0400
Subject: [xmonad] Broken Xmonad after updates
In-Reply-To: <PAVPR08MB9401AB3D682FCEA874B7CF9BC2D9A@PAVPR08MB9401.eurprd08.prod.outlook.com>
References: <PAVPR08MB9401EA35CA326B98300A072EC2D4A@PAVPR08MB9401.eurprd08.prod.outlook.com>
 <CAKFCL4W7jn5rLoA+6WCP8TLcikkUHEtpvKB7Fpom87J4ewx4dg@mail.gmail.com>
 <PAVPR08MB9401ABE8BC1DC21CE1AF05B7C2D9A@PAVPR08MB9401.eurprd08.prod.outlook.com>
 <CAKFCL4X=F1MTJrO4fb=9iqZUo=0Vydp0+JbV6S4s1uvLLj4DBA@mail.gmail.com>
 <PAVPR08MB9401AB3D682FCEA874B7CF9BC2D9A@PAVPR08MB9401.eurprd08.prod.outlook.com>
Message-ID: <CAKFCL4UBJx8t6hPrPLHxPxXzvn+SkzXYh=CMxrEMNwei4AUETA@mail.gmail.com>

In XDG mode, per the XDG spec executables are not to be stored in config
file locations. Since it can be regenerated from `xmonad.hs` when needed,
it belongs under `.cache`. In legacy mode (~/.xmonad) the executable is
kept next to the `xmonad.hs` file.

Your description of running `startx` seems a bit confused to me. Did you
run it in the background and then try to run xmonad? This won't work
because `startx` can't alter the environment variables of the running
shell, so `$DISPLAY` won't be set. You need to run xmonad within the client
environment: `startx ~/.cache/xmonad/xmonad-x86_64-linux` (it has to be a
full pathname; see the `startx` documentation).

On Sun, Oct 22, 2023 at 3:03 PM Jan Detke <jandetke at outlook.com> wrote:

> Brandon Allbery <allbery.b at gmail.com> writes:
>
> > I'm looking at that page, and aside from one slight documentation bug
> that
> > doesn't really affect anything here it looks correct to me and shouldn't
> be
> > able to get the wrong executable name unless something has gone wrong
> > inside xmonad's compile logic. Although that also looks out of date: we
> > support stack building directly, so xmonad should use essentially that
> > build script itself when it sees a `stack.yaml` file.
> >
> > You probably want to use the latest version of the install documentation:
> >
> https://github.com/xmonad/xmonad/blob/master/INSTALL.md#build-using-stack
> >
> I found the executable under '$HOME/.cache/xmonad/'. Is this the intendet
> location for the executable? I assumed that it would reside in the
> directory where my xmonad.hs and the build script are located.
>
> Additionally, I tried starting xmonad outside of my display manager that
> did not work out. I will look deeper into xinit for this regard - but as a
> short notice: I loggend in a tty, ran startx (with some warnings) and then
> xmonad. The received output was 'xmonad-x86_64-linux: user error
> (openDisplay)', which indicates that the xserver is not running properly.
>
> I will try to fall back to my display manager by creating a desktop entry
> for xmonad under '/usr/share/xsessions/', but that is a task for tomorrow.
>
> Thanks again
> Jan
>


-- 
brandon s allbery kf8nh
allbery.b at gmail.com
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mail.haskell.org/pipermail/xmonad/attachments/20231022/6c2b9d65/attachment-0001.html>

From jandetke at outlook.com  Mon Oct 23 16:38:28 2023
From: jandetke at outlook.com (Jan Detke)
Date: Mon, 23 Oct 2023 18:38:28 +0200
Subject: [xmonad] Broken Xmonad after updates
In-Reply-To: <CAKFCL4UBJx8t6hPrPLHxPxXzvn+SkzXYh=CMxrEMNwei4AUETA@mail.gmail.com>
References: <PAVPR08MB9401EA35CA326B98300A072EC2D4A@PAVPR08MB9401.eurprd08.prod.outlook.com>
 <CAKFCL4W7jn5rLoA+6WCP8TLcikkUHEtpvKB7Fpom87J4ewx4dg@mail.gmail.com>
 <PAVPR08MB9401ABE8BC1DC21CE1AF05B7C2D9A@PAVPR08MB9401.eurprd08.prod.outlook.com>
 <CAKFCL4X=F1MTJrO4fb=9iqZUo=0Vydp0+JbV6S4s1uvLLj4DBA@mail.gmail.com>
 <PAVPR08MB9401AB3D682FCEA874B7CF9BC2D9A@PAVPR08MB9401.eurprd08.prod.outlook.com>
 <CAKFCL4UBJx8t6hPrPLHxPxXzvn+SkzXYh=CMxrEMNwei4AUETA@mail.gmail.com>
Message-ID: <PAVPR08MB94015D9E0967E9B3543A96D4C2D8A@PAVPR08MB9401.eurprd08.prod.outlook.com>

Brandon Allbery <allbery.b at gmail.com> writes:

> Your description of running `startx` seems a bit confused to me. Did you
> run it in the background and then try to run xmonad? This won't work
> because `startx` can't alter the environment variables of the running
> shell, so `$DISPLAY` won't be set. You need to run xmonad within the client
> environment: `startx ~/.cache/xmonad/xmonad-x86_64-linux` (it has to be a
> full pathname; see the `startx` documentation).
>
I thought that I had to start the xserver before invoking 'exec ~/.cache/xmonad/...'' like I would in .xinitrc. Now when I log in and manually run 'startx ~/.cache/xmonad/xmonad-x86_64-linux' it works like a charm. But when I run 'startx .xinitrc' where one line of .xinitrc contains 'exec ~/.cache/xmonad/xmonad-x86_64-linux' the startup of the xserver fails. I also tried giving the full path like 'home/jan/.cache/...' but it still fails. Do I have to wrap the path into quotes for the exec command or what is wrong here?

Best regards
Jan

From allbery.b at gmail.com  Mon Oct 23 16:56:59 2023
From: allbery.b at gmail.com (Brandon Allbery)
Date: Mon, 23 Oct 2023 12:56:59 -0400
Subject: [xmonad] Broken Xmonad after updates
In-Reply-To: <PAVPR08MB94015D9E0967E9B3543A96D4C2D8A@PAVPR08MB9401.eurprd08.prod.outlook.com>
References: <PAVPR08MB9401EA35CA326B98300A072EC2D4A@PAVPR08MB9401.eurprd08.prod.outlook.com>
 <CAKFCL4W7jn5rLoA+6WCP8TLcikkUHEtpvKB7Fpom87J4ewx4dg@mail.gmail.com>
 <PAVPR08MB9401ABE8BC1DC21CE1AF05B7C2D9A@PAVPR08MB9401.eurprd08.prod.outlook.com>
 <CAKFCL4X=F1MTJrO4fb=9iqZUo=0Vydp0+JbV6S4s1uvLLj4DBA@mail.gmail.com>
 <PAVPR08MB9401AB3D682FCEA874B7CF9BC2D9A@PAVPR08MB9401.eurprd08.prod.outlook.com>
 <CAKFCL4UBJx8t6hPrPLHxPxXzvn+SkzXYh=CMxrEMNwei4AUETA@mail.gmail.com>
 <PAVPR08MB94015D9E0967E9B3543A96D4C2D8A@PAVPR08MB9401.eurprd08.prod.outlook.com>
Message-ID: <CAKFCL4VmN19P_Oj50ChJhTNbXniA4aAr7=F0hkNUnjMGO30Bvg@mail.gmail.com>

As per the documentation of `startx`, if you do not use a full pathname it
runs a default session and passes it your argument as a parameter. Also
make sure `~/.xinitrc` is executable (`chmod +x ~/.xinitrc) and that its
first line is `#! /bin/bash` or `#! /bin/sh`.

On Mon, Oct 23, 2023 at 12:38 PM Jan Detke <jandetke at outlook.com> wrote:

> Brandon Allbery <allbery.b at gmail.com> writes:
>
> > Your description of running `startx` seems a bit confused to me. Did you
> > run it in the background and then try to run xmonad? This won't work
> > because `startx` can't alter the environment variables of the running
> > shell, so `$DISPLAY` won't be set. You need to run xmonad within the
> client
> > environment: `startx ~/.cache/xmonad/xmonad-x86_64-linux` (it has to be a
> > full pathname; see the `startx` documentation).
> >
> I thought that I had to start the xserver before invoking 'exec
> ~/.cache/xmonad/...'' like I would in .xinitrc. Now when I log in and
> manually run 'startx ~/.cache/xmonad/xmonad-x86_64-linux' it works like a
> charm. But when I run 'startx .xinitrc' where one line of .xinitrc contains
> 'exec ~/.cache/xmonad/xmonad-x86_64-linux' the startup of the xserver
> fails. I also tried giving the full path like 'home/jan/.cache/...' but it
> still fails. Do I have to wrap the path into quotes for the exec command or
> what is wrong here?
>
> Best regards
> Jan
>


-- 
brandon s allbery kf8nh
allbery.b at gmail.com
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mail.haskell.org/pipermail/xmonad/attachments/20231023/56359255/attachment.html>

From jandetke at outlook.com  Mon Oct 23 17:36:04 2023
From: jandetke at outlook.com (Jan Detke)
Date: Mon, 23 Oct 2023 19:36:04 +0200
Subject: [xmonad] Broken Xmonad after updates
In-Reply-To: <CAKFCL4VmN19P_Oj50ChJhTNbXniA4aAr7=F0hkNUnjMGO30Bvg@mail.gmail.com>
References: <PAVPR08MB9401EA35CA326B98300A072EC2D4A@PAVPR08MB9401.eurprd08.prod.outlook.com>
 <CAKFCL4W7jn5rLoA+6WCP8TLcikkUHEtpvKB7Fpom87J4ewx4dg@mail.gmail.com>
 <PAVPR08MB9401ABE8BC1DC21CE1AF05B7C2D9A@PAVPR08MB9401.eurprd08.prod.outlook.com>
 <CAKFCL4X=F1MTJrO4fb=9iqZUo=0Vydp0+JbV6S4s1uvLLj4DBA@mail.gmail.com>
 <PAVPR08MB9401AB3D682FCEA874B7CF9BC2D9A@PAVPR08MB9401.eurprd08.prod.outlook.com>
 <CAKFCL4UBJx8t6hPrPLHxPxXzvn+SkzXYh=CMxrEMNwei4AUETA@mail.gmail.com>
 <PAVPR08MB94015D9E0967E9B3543A96D4C2D8A@PAVPR08MB9401.eurprd08.prod.outlook.com>
 <CAKFCL4VmN19P_Oj50ChJhTNbXniA4aAr7=F0hkNUnjMGO30Bvg@mail.gmail.com>
Message-ID: <PAVPR08MB940186B18E467273379CC677C2D8A@PAVPR08MB9401.eurprd08.prod.outlook.com>

Brandon Allbery <allbery.b at gmail.com> writes:

> As per the documentation of `startx`, if you do not use a full pathname it
> runs a default session and passes it your argument as a parameter. Also
> make sure `~/.xinitrc` is executable (`chmod +x ~/.xinitrc) and that its
> first line is `#! /bin/bash` or `#! /bin/sh`.
>
I found the issue. It had to with an unclosed if statement in my xinitrc which resulted in an unexpected EOF error. After fixing this everything works well. Permissions to execute the xinitrc were not necessary.

Thank you Brandon for supporting me. Really appreciate you taking your time and effort :)

Best regards
Jan

From wferi at niif.hu  Thu Oct 26 19:04:17 2023
From: wferi at niif.hu (=?utf-8?Q?Ferenc_W=C3=A1gner?=)
Date: Thu, 26 Oct 2023 21:04:17 +0200
Subject: [xmonad] contemporary Gnome Flashback panel integration
Message-ID: <877cn95hou.fsf@fin.soreny>

Hi,

I'm using Xmonad in a Gnome Flashback session as distributed with Debian
bookworm.  There are several internet search hits for showing Xmonad log
messages via specialized Gnome panel applets (see below), but they're
all like ten years old and require the outdated libpanel-applet-4-dev
dependency (or something even older), which isn't available for
gnome-panel 3.46 or later.  What's the current best practice for showing
Xmonad log messages under Gnome?

Thanks,
Feri.

https://www.reddit.com/r/xmonad/comments/ft5e4/making_xmonad_log_to_the_gnome_panel/
https://github.com/alexkay/xmonad-log-applet/
https://web.archive.org/web/20180821093617/http://uhsure.com/xmonad-log-applet.html
https://wiki.haskell.org/Xmonad/Using_xmonad_in_Gnome
https://wiki.haskell.org/Installing_xmonad_log_applet