Search

Items tagged with: X11


I mean, in Wayland mode, it crashes when you, for example, rotate a mesh. It also, as you move a mesh the slightest bit, will suddenly lurch the mesh off the screen. You're still attached to it. You can drag it back with the mouse like you're reeling in a trout. When you try to minimize a screen, it won't do it. You have to drag the screen somewhere else. Then it usually will. If it won't, drag it again.

I'm going back to X11 mode, where it still crashes, but with less stupidity along the way.

Unreal consistently gives Linux developers the middle finger.

#UE5 #Linux #Wayland #X11


Upgraded to PopOS 24.04 and Cosmic and kept getting stream freezes on OBS until I switched back to Cinammon + #x11

Curious if anyone got tips or had more success on how to make streaming stable on Cosmic and/or #Wayland in general

Behavior was basically ever few minutes video would freeze but audio was fine (Pipewire Window capture, OBS v 33 flatpak)

Googled a lot and only ran into audio troubleshooting or general "Use windows for streaming" advice

#LinuxStreaming #Linux


The media in this post is not displayed to visitors. To view it, please go to the original post.

I found something unexpected today:
the “milk” X11 Window Manager
github.com/mirvoxtm/milk

It is written in the Odin programming language (compiled). The install script pulls down the source and Odin compiler and compiles and installs after after you questions about how you’d like it set up.

I had trouble getting audio and brightness working. I was on Devuan, but decided to install a Void derivative distro. Had the same problems on that. It ended up being that I needed to create an .xinitrc file and put a line in it to start dbus and pulseaudio (I removed pipewire from Neko-Void).

cat ~/.xinitrc
dbus-run-session pulseaudio --start

Now that I have audio working, I am very pleased with the ‘milk’ window manager. The default configuration is great and easy to edit by pointing and clicking in a the settings panel (can edit a milk.json config file, too).

#WindowManager #Linux #Void #Odin #X11


this is ridiculous. the sample code which implements this is even worse. why is this all necessary?? #Wayland you fuckin' stink. I can't believe that you managed to make something that makes vanilla #X11 programming seem sensible.

(passage from wayland-book dot com)

In summary, the following steps will take you from zero to a window on-screen:

Bind to wl_compositor and use it to create a wl_surface.
Bind to xdg_wm_base and use it to create an xdg_surface with your wl_surface.
Create an xdg_toplevel from the xdg_surface with xdg_surface.get_toplevel.
Configure a listener for the xdg_surface and await the configure event.
Bind to the buffer allocation mechanism of your choosing (such as wl_shm) and allocate a shared buffer, then render your content to it.
Use wl_surface.attach to attach the wl_buffer to the wl_surface.
Use xdg_surface.ack_configure, passing it the serial from configure, acknowledging that you have prepared a suitable frame.
Send a wl_surface.commit request.


So... If I understand correctly, my @kde_neon is completely STUCK. Indeed, @kde 6.8 drops #plasma #X11 sessions, and #wayland still doesn't support my basic, but essential, workflow need: restoring app windows positions.

I am stuck (cannot update the distro) and very unhappy! 😡😡😡🤬

Another wrong move for #kde and #neon. (6.6 to 6.7 on Neon was a real nightmare).


Just checked: only happens on #Wayland

Works fine on #X11



The crashing and bad window minimizing behavior were due to Wayland. After I forced UE5 to use X11, the problems have disappeared.

#UE5 #X11 #Wayland #Ubuntu


*sigh* I guess I'll stick to i3. The gaming latency between X11 and Wayland is very noticeable (to me) anyway whenever I play osu!lazer with AR and OD 11 on standard.

Every ms counts even if it's just 8ms

#i3wm #gaming #x11 #wayland #kde #osulazer


lol, the attempt to ram through a pro-slop KDE policy just got closed yet again because people found out about it

invent.kde.org/plasma/plasma-w…



why can't I fuckiNG MIDDLE CLICK PASTE IN GAJIM

(I'm sure it's because the Gnome people decided to fuck us over)

I miss X11, where things ACTUALLY WORKED. Where shit like middle-click paste couldn't be arbitrarily blocked by the GUI-toolkit people because they don't like us Users™ having such nice things as /features/.

"oh but X needs to die!!" no it doesn't.
"oh but Wayland is BETTER!" no it isn't.
"oh but you need Wayland for HDR and stuff!" yeah that was a /choice/ to not implement those for X11.
"oh but SECURITY!" this isn't a phone, we're not running random proprietary crap.

bonus: "oh but you can use a different DE!" and ditch /everything/ that's nice about KDE? (and land on something that uses GTK and is beholden to the Gnome people, who are the type of people to arbitrarily block middle-click paste in their GUI toolkit?)

#linux #X11 #wayland



Still playing osu! with ar11 random mirror mods.

Unlike most "gamers", I use 1366x768 60 Hz VGA monitor, btw. Never managed to buy some modern monitor with modern res cos monehhh, plus it still works.

I bought the main one with my own money and the second monitor, I just got it from my old workplace, lol.

Oh I also stopped using KDE. Wayland gets in the fucking way of me having fun when I have AR11, HP11, and OD11 set on osu!. The latency is noticeable. Feels like my mousepad is "well-oiled" when I'm in X11, Still love KDE tho but yeah..

#youtube: youtu.be/Hjal3Q-mYDA
#twitch: twitch.tv/reallylazybear

#linuxgaming #osulazer #rhythmgame #osu #osugame #opensource #eldenring #gaming #archlinux #cachyos #x11 #wayland #freesoftware #kde


Oh my, I didn't realise the state of develop-for-Wayland was this bad. As a sometimes hobbyist developer I can feel the pain.

It really does feel like one of the Linux non-profits could usefully somehow "take ownership" of the protocol level to at least standardise on one way to do things like virtual keyboard input. You'd think at least Gnome and KDE could have saved both their selves some time by co-operating on these things.

I'll continue with Xorg-based X11 until there's good reason not to. Yes, I know about recent security issues, lack of maintainer-ship, and the shit show that has been the forks/alternatives...

... but my current X11+fvwm3 setup *works for me*.

#wayland #linux #x11 #xorg


This morning I did get #kde #plasma #wayland up and running, had first fight with #sddm , this for my old monitors had really big colour difference, one darker and a grey/yellow taint. So I thought one of the monitors was breaking down, I spent weeks to looks for what next and spent money on new monitors. I have the same issue, so I decided to switch #Xorg for wayland, sure the issue is till there... and gosh wayland ain't the best on handling sessions IMHO, as which VT seems to be a bit randomish, you are stuck with "Switch User" and gosh it's SLOW like hell and easy to make plasmashell to crash on a session you are switching to. sddm don't allow you to specify the VTs you want to use, not even which VT to start with.

Plasma had the nice feature where you could scale old #X11 applications that don't have built in scaling, but then it would affect all X11 applications, this should have been a Special Window/Application rule, then it had been a lot more useful. Enabling #HDR , it works just for one monitor.

When #plasmashell crashes when you try to switch back, the view port seems to change to something a lot smaller. I can't get #yakuake to appear (either it's for it's far outside the view port or shift-f12 don't work when plasmashell wyaland crashes (in Xorg it works and the view is still full resolution).

It feels like everyone nowadays only develops a single user experience, desktop manager that can't handle multiple session (darn I miss #KDM , best ever desktop manager), desktop environments just don't handle that they aren't active. Multi monitor setups is nowadays a lot more experimental than it was in the 1990's.

As my main issue didn't get solved, I will revert back to Xorg and get a bit more stability. Maybe there will come something better to replace wayland, once in the time I was enthusiastic about it, but with time I just think it's just been a waste of time which could have been spent on gutting out all the old in Xorg and add new features.


Prepare for a riveting saga of #Linux #input #latency, where #X11 and #Wayland battle for supremacy 🏆, yet somehow everyone still uses Windows for #gaming anyway. The author bravely ventures into realms of VRR and #DXVK, only to realize that the true enemy is their own patience 😩. Meanwhile, the rest of us just want to play #Quake without summoning the tech gods. 🎮
marco-nett.de/blog/measuring-i… #HackerNews #ngated


The media in this post is not displayed to visitors. To view it, please go to the original post.

Trying out NextSpace on Slackware -current with XLibre.

A modern implementation inspired by the classic NeXTSTEP desktop. It's interesting to see how its design and workflow still feel relevant decades later.

Definitely a fun project to explore.

#Slackware #NextSpace #XLibre #Unix #X11


The current version of #KDE on my machine (6.7) seems to be very buggy in terms of what happens when I try to add extra monitor(s) in the #Wayland version, whether it’s via #HDMI or #USB with #Displaylink. The screens go haywire and I can even get a terminal open. I’ve had to revert back to the #X11 version just as I’d got used to Wayland. I’m no fanboy of Wayland or X11 but when such a major breaking of the system happens, it forces my hand. Not good at all.

#Fedora #Linux #Desktop #KDE6_7



OK, so finally ~migrated to #wayland from #x11 on my #vmware #fusion VM, but since it's a Fusion VM I hit the seemingly unresolved clipboard problem between host and guest machines.

As far as I can see based on my searches, it's pretty much unfixable. How are folks working this around today? Clipboard over network? Just use x11 and hope for a fix in our lifetime?


apart from the clear fallacy of #KDE claiming most their users use #wayland over #x11 , how are they getting that telemetry eh? Isn't that inherently flawed...


SonicDE

We forked the #KDE Plasma Login Manager. It now runs on #X11, drops privileges after init, and supports #systemd-free too. We tested it on Artix Linux with OpenRC, CachyOS with systemd, and on the #FreeBSD-based GhostBSD. #SonicDE sonic-login-manager

x.com/SonicDesktop/status/2056…


#kde #x11


Need to use an ‘input method’ for Japanese characters, but said ‘input method’ forces only a single keyboard layout on the system level, so I can no longer type Czech characters using Alt Gr on the Czech layout without first turning off the option that adds Esperanto characters to Alt Gr on the first system keyboard layout. :gutkato_flucerba:

Incidentally, I can add another system keyboard layout in KDE, but it’s automatically deleted on startup. My solution would be to write a script which either turns the Esperanto characters on/off or adds a keyboard layout, but it seems like there is nothing like setxkbmap under Wayland, so my best option would be poking at KDE settings with severely underdocumented command-line tools. :gutkato_renversa:

Why does technology always have to turn ugly?

#lang_en #KDE #setxkbmap #technology #Wayland #X11



Uuurgh... why does everything run like crap on #wayland? Or rather #kde on #wayland.
I never had any major performance problems on #xfce and #x11. Here kwin_wayland keeps using at least 20% or often 40% CPU. Chromium even hogs all the CPU time it can get when open.
Firefox only runs well through XWayland.
Who said wayland is stable? #archlinux #ThinkPadX260
(Also.. suggestions are appreciated. I already tried looking up my sympoms online)

⇧