Chigozirim

This does not seem to be something `yay` can prevent. The PKGBUILD for that [package](https://aur.archlinux.org/packages/quassel-client-git) is what explicitly builds everything. See also https://wiki.archlinux.org/title/Meta_package_and_package_group

You can also specify `--xinmera-head=n` on the command line which will allow you to launch conky on multiple displays using the same config. This was exactly what I was searching...

@mgimenoromanadevinta can you show point to the build that exhibits this behavior? The error you are pointing to may also be based on the fact that this action only works...

I wasn't sure how to make the arguments lazily evaluated without resorting to using the same syntax as lazy pipe. This is the syntax I settled on. There are two:...

#1279

I just wanted to add that I was having this issue when I had disabled the web client portion of the server component. My setup is using nginx as a...

This is still an issue. See also #2197

I don't think it is related to Chrome. I use firefox and I experience the same issue. 

@FredrikOseberg that's exactly how I am doing it. I use [mui](https://mui.com/) components, and I am wrapping the chatbot container within a [`Fade`](https://mui.com/api/fade/#main-content) component: ```jsx ``` As you can see, when...

> Hey @smac89, did you find any workaround for that issue? No, unfortunately not. We decided to go a different approach and deployed a pre-built chatbot rather than building one.