#Tag
Oh thank $deity I can still launch #Chrome with --ozone-platform=x11 even though the configuration flag has been removed. Because #Wayland breaks *so many things* for me.
Surely I'm not the only one seeing dropdowns, tooltips etc. render in top-left corner of my screen under Wayland?
#GNOME #FreeSoftware #OpenSource #FOSS #OSS #YouBrokeMyWorkflow #X11 forever
For anyone struggling #X11 stopped working on #FreeBSD after upgrading main branch of #ports tree to commit 316774b85e4fc8858989a98da1a36075b6cbc8d2 and later with nvidia GPUs, reverting following commits and rebuild graphics/drm-[61|66]-kmod whichever you're using and corresponding graphics/nvidia-drm-[61|66]-kmod[-devel] you're using and reboot would help.
https://cgit.freebsd.org/ports/commit/?id=316774b85e4fc8858989a98da1a36075b6cbc8d2
https://cgit.freebsd.org/ports/commit/?id=09f1e5c29432d77a992f5f554f48986ef8674e9c
https://cgit.freebsd.org/ports/commit/?id=803213ed04ad14ea91a65cd48e6e8d6d610e3b98
https://cgit.freebsd.org/ports/commit/?id=ac934345a14f64a3e6f09bbde56f0dcacc8b3066
This issue is tracked at #FreeBSD Bugzilla.
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=289647
For anyone struggling #X11 stopped working on #FreeBSD after upgrading main branch of #ports tree to commit 316774b85e4fc8858989a98da1a36075b6cbc8d2 and later with nvidia GPUs, reverting following commits and rebuild graphics/drm-[61|66]-kmod whichever you're using and corresponding graphics/nvidia-drm-[61|66]-kmod[-devel] you're using and reboot would help.
https://cgit.freebsd.org/ports/commit/?id=316774b85e4fc8858989a98da1a36075b6cbc8d2
https://cgit.freebsd.org/ports/commit/?id=09f1e5c29432d77a992f5f554f48986ef8674e9c
https://cgit.freebsd.org/ports/commit/?id=803213ed04ad14ea91a65cd48e6e8d6d610e3b98
https://cgit.freebsd.org/ports/commit/?id=ac934345a14f64a3e6f09bbde56f0dcacc8b3066
This issue is tracked at #FreeBSD Bugzilla.
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=289647
This is bizarre and cool: Term.Everything❗ is an X11 and Wayland Linux tool for running GUI programs in the terminal.
This is bizarre and cool: Term.Everything❗ is an X11 and Wayland Linux tool for running GUI programs in the terminal.
Very specific feature!
In desperate need for a Wayland compositor that permits this same feature I had on X11 with this DWM "combo" patch: Holding Super and pressing simultaneously 1 and 2 permits me to see both tags (~ workspaces) 1 and 2.
Very specific feature!
In desperate need for a Wayland compositor that permits this same feature I had on X11 with this DWM "combo" patch: Holding Super and pressing simultaneously 1 and 2 permits me to see both tags (~ workspaces) 1 and 2.
Just in case there is somebody who is using Clear.Dental in production, I want to let everyone know I am making a number of major changes in the next few months (see attached image)
These will be major changes that will help bring Clear.Dental to the mass market. Now that Clear.Dental is the only Open Source EHR/PMS, getting people to switch has never been more important.
Just in case there is somebody who is using Clear.Dental in production, I want to let everyone know I am making a number of major changes in the next few months (see attached image)
These will be major changes that will help bring Clear.Dental to the mass market. Now that Clear.Dental is the only Open Source EHR/PMS, getting people to switch has never been more important.
Creating ~/.XCompose causes Emacs, URxvt, and xterm to ignore the default /usr/share/X11/locale/${LANG}/Compose, while Firefox and KiCad read both.
At first I thought it was just Emacs being different, and doing something wrong because NIH.
But after consulting the Compose(5) manual, it's Firefox and KiCad that are wrong for reading both (I should put include "%L" in my ~/.XCompose to include the system file). Probably they both inherit this bug from #GTK (and Emacs' NIH saved it).
Creating ~/.XCompose causes Emacs, URxvt, and xterm to ignore the default /usr/share/X11/locale/${LANG}/Compose, while Firefox and KiCad read both.
At first I thought it was just Emacs being different, and doing something wrong because NIH.
But after consulting the Compose(5) manual, it's Firefox and KiCad that are wrong for reading both (I should put include "%L" in my ~/.XCompose to include the system file). Probably they both inherit this bug from #GTK (and Emacs' NIH saved it).
Delightful commons news 🔥
Thanks to @nlnet I was able to give new impetus to delightful commons, and yesterday added new sections to the #fediverse experience list:
https://delightful.coding.social/delightful-fediverse-experience
New sections added under Fediversity:
- ActivityPub bots
- Browser extensions
- Fediverse metrics
- Tools and utilities
- Mastodon API based
🥳 Even better.. There is a new delightful list created and maintained by @lmemsm and collecting delightful #X11 resources.
Check it out at:
Delightful commons news 🔥
Thanks to @nlnet I was able to give new impetus to delightful commons, and yesterday added new sections to the #fediverse experience list:
https://delightful.coding.social/delightful-fediverse-experience
New sections added under Fediversity:
- ActivityPub bots
- Browser extensions
- Fediverse metrics
- Tools and utilities
- Mastodon API based
🥳 Even better.. There is a new delightful list created and maintained by @lmemsm and collecting delightful #X11 resources.
Check it out at:
⚙️ Plasma 6.4 review - A worrying trend • Dedoimedo
｢ Overall, Plasma is nice and fast. Version 6.4 ain't no exception. But this version brings numerous ergonomic regressions, forcing you to waste time that you previously didn't need to, it hides important things in the name of who knows what ｣
A weird thing about #Slack on #Linux#X11: whenever it gains keyboard focus, it immediately reads the X11 clipboard, even if you didn't try to paste anything. I see no evidence that it does anything with what it reads, but I know it reads it.
I found this out by accident, because I wrote a stunt X11 client which owns the clipboard for just long enough to paste once, and then terminates. The idea was to queue up three different pastes on the command line, and paste them in quick succession into fields of a form. Works very well, unless I accidentally mouse over Slack on the way to the form I want to paste into – then my focus-follows-mouse activates it, and it consumes one of my clipboard strings!
I have no idea why, or whether it's on purpose. I'm prepared to give it the benefit of the doubt, by assuming until further evidence that it's some unforeseen emergent consequence of the huge wobbly tower of libraries and wrappers and browsers that the desktop Slack app is built on top of. But it's not great. Some password managers will put passwords in the clipboard!
A weird thing about #Slack on #Linux#X11: whenever it gains keyboard focus, it immediately reads the X11 clipboard, even if you didn't try to paste anything. I see no evidence that it does anything with what it reads, but I know it reads it.
I found this out by accident, because I wrote a stunt X11 client which owns the clipboard for just long enough to paste once, and then terminates. The idea was to queue up three different pastes on the command line, and paste them in quick succession into fields of a form. Works very well, unless I accidentally mouse over Slack on the way to the form I want to paste into – then my focus-follows-mouse activates it, and it consumes one of my clipboard strings!
I have no idea why, or whether it's on purpose. I'm prepared to give it the benefit of the doubt, by assuming until further evidence that it's some unforeseen emergent consequence of the huge wobbly tower of libraries and wrappers and browsers that the desktop Slack app is built on top of. But it's not great. Some password managers will put passwords in the clipboard!
✨ Wayland Will Never Be Ready ✨
The full article titled, "Wayland Will Never Be Ready For Every X11 User" is one of my favorite writings on the topic. Well done Maya Posch, well done indeed.
https://hackaday.com/2025/07/28/wayland-will-never-be-ready-for-every-x11-user/
✨ Wayland Will Never Be Ready ✨
The full article titled, "Wayland Will Never Be Ready For Every X11 User" is one of my favorite writings on the topic. Well done Maya Posch, well done indeed.
https://hackaday.com/2025/07/28/wayland-will-never-be-ready-for-every-x11-user/
Hey #OpenGL and #graphics people, are there any graphics profiling/instrumentation/frame debugger solutions which work with OpenGL on modern non-Windows systems? Something à la #RenderDoc but that works on #Wayland or Apple Silicon Macs. To do frame debugging right now I have to log out of my Wayland session on my #Linux desktop and log in to #X11, which is uber-broken on my mixed DPI fractional scaling multi monitor setup... #programming #graphicsprogramming #macdev
A space for Bonfire maintainers and contributors to communicate
