@LastYearsIrritant @chunes then use cloud as a black box, replicating it behaviour

@MonkeMischief @corsicanguppy portage tree already conains all instructions and follows automaticly. You optionally may override options with use flags unlike binary distros where you only can use default configuration

@auzy1 @MattW03 windows 2000

@toothbrush @Tanoh
>xwayland-satellite
does not implement anything, just glues xwayland to session
phoenix and yserver might be good Xwayland alternative, not Xorg/xf86, because Xorg is mostly about DDX drivers and it’s only way to use 2d acceleration on old hardware (which is deprecated, but still might be useful)

@Scrollone @jayands it is reversed, but AMD still may crash everything on gpu hang

@RustyNova @MyNameIsRichard
>On nix os, blender doesn’t want to render anything after waking from sleep (may be a blender issue.)

seems to be cuda issue. On my machine cuda sometimes refusing to work after sleep, requiring some ‘node restart’
Might be fixed by disabling modeset (nvidia-drm modeset=0), or by blocking display server from using nvidia drm node (if display output does not use nvidia)

@Digit @flamingos it will be replaced by systemd-dated soon

@MonkderVierte @tjhrulz
Hm? Removed pulse, installed pipewire-pulse, run pipewire && wireplumber && pipewire-pulse as user and got no available sound devices.Why? Because wireplumber’s bullshit crashed after forking to daemon somewhere in camera support code (but i do not have cameras!).
With reference pipewire-media-session everything worked, but everybody forcing unstable and bloaty wireplumber, making old configuration not supported…
Yes, maybe it’s not pipewire fault, just it’s modular architecture, but it makes me unhappy with it, so i still using jack. And i sure, there should be separate provider processes for camera and audio devices

@WanderingThoughts @Ek-Hou-Van-Braai https://unix.stackexchange.com/questions/282155/what-is-the-out-of-memory-message-sacrifice-child

@certified_expert @WanderingThoughts bomb.zip

@orlyowl @TrickDacy for me it was entire session crash on compositor crash. And gnome is still keeping this very useful feature, but making this crash even stronger with wayland

@spez @qaz
>country not allowed
not a great loss…

@evol Haiku?

@possiblylinux127 @Skullgrid protocol itself is mostly OK. Yes, it have many limitations, but it covers much more desktop needs than wayland/mir/surfaceflinger/etc.
But implementation is really broken.
For example, the way how some extensions override vtable is terrible: overriding functions usually should restore base function in vtable before calling it and and restore back after. Breaking this would break call chain and override function will never be called again.
I think, this is a reason why devs switched to wayland. Nobody want to reimplement x11 from scratch, but exisiting implementation is borked

@KuzhinierSileon no video moment

@Digit @thatradomguy i just built minimalistic kkernel for orange pi with almost everrything disabled and it takes 6mB even in compressed state

@Digit @tourist TDE is bloated too.; It’s good alternative to KDE, but if you have really resource-limited system, it’s better to use some WM

@aloofPenguin @chloroken it’s so stupid like trying replace xrandr with ddcutil…

@Kolanaki @The_Picard_Maneuver i’m not sure if any existing hardware can handle vrchat smoothly. This piece of udon and photon cannot work smoothly with more than dozen players

@NullPointerException @yesman debian never updates it