mittorn
- 0 Posts
- 8 Comments
@certified_expert @WanderingThoughts bomb.zip
mittorn@masturbated.oneto
linuxmemes@lemmy.world•I'll try something different next install, I swear.
1·26 days ago@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
mittorn@masturbated.oneto
linuxmemes@lemmy.world•Where to go now since Linux is mainstream
3·2 months ago@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
@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