Show more

@catsalad Had a really excessive number of annoying papercuts after updating to 6.0.1 - nothing really showstopping though and 6.0.2 already fixed vast majority of them, so it's not bad after all 馃槉

@stfn @wariat @pecet@pol.social To podstawowe sk艂adowe ka偶dego sterownika graficznego pod Linuksem. Zapewne nadal u偶ywasz ju偶 nierozwijanego Xorga - Nvidia od wielu lat mia艂a w艂asny sterownik dla Xorga, ale Linux w ci膮gu ostatnich dw贸ch dekad dorobi艂 si臋 wielu API do obs艂ugi GPU i sam robi rzeczy, kt贸re kiedy艣 robi艂 Xorg. Nvidia dopiero niedawno wypu艣ci艂a sterownik implementuj膮cy te API i nadal ma w nim powa偶ne braki (a gry to jeden z use-cas贸w kt贸ry na tym cierpi, z migaj膮cymi klatkami pod Waylandem).

@stfn @wariat @pecet@pol.social Nvidia latami nie potrafi艂a przygotowa膰 dzia艂aj膮cego sterownika implementuj膮cego GBM, a dzisiaj nadal nie ogarnia niejawnej synchronizacji bufor贸w. To s膮 absolutnie podstawowe aspekty stosu graficznego, ich brak nie mie艣ci si臋 w mojej definicji "dzia艂a".

@wariat @pecet@pol.social Je偶eli ma dzia艂a膰 i mowa o x86, to odpowied藕 brzmi "wszystko tylko nie nvidia".

@raptor85 @sos @kkolakowski CMake is a leaky abstraction with awful DSL, and my 12yo cmake scripts are a pile of incredible mess riddled with technical debt, but it still does its job well enough that I could just point my projects to stuff like devkitpro, vitasdk, osxcross, Emscripten, Flatpak or Steam Runtime and focus on actual porting rather than fighting with build recipes.

@sos @raptor85 @kkolakowski To do actual work, we have proper IDEs that can handle such exotic and rarely-seen things as CMake projects (/s) natively 馃槀

@sos @kkolakowski Is it though? All I can see here is you trying to use a tool blindly without understanding what it's for :P
It's a build solution generator, and VS project files are merely one of the kinds of outputs it does (alongside Ninja, Make, Xcode and plenty of some obscure ones too). Generated files are just intermediate build artifacts - you use them to build, they're not for human consumption nor for editing.
It's simply an abstraction on top of various incompatible build systems.

@kkolakowski @sos It's a much better idea than having to maintain a myriad of separate build scripts for each platform and having to deal with stuff like Visual Studio or Xcode directly. CMake isn't a particularly beautiful implementation of that idea, but any other sane build system works the same way.

@krosylight Not in gaming mode at least. It may make sense when used with nested kwin_wayland for example (which is how I usually run Plasma on my Deck), but it's useless when used directly under gamescope.

You could run gamescope with `--expose-wayland` parameter, but even then it will only work with very simple apps; definitely not with Firefox 馃槄

@krosylight Which part of "everyone" is ambiguous? 馃槣 Yes, mine too.

@krosylight Gamescope doesn't really handle Wayland (xdg-shell) clients. It has some very basic support, but not nearly enough to handle apps like Firefox, so it all goes through X11 over XWayland.

@cassidy @flathub Wow, the 35 character limit for sum---maries is extreme in English already, and it's not the most verbose language out there 馃檲

"---" denotes the 35th character mark 馃槶

phosh 0.37.0 is out 馃殌馃摫:

- Wi-Fi selection via quick settings
- Build custom quick settings via plugins
- Caffeine quick settings
- Support fractional-scale-v1 protocol
- Updated #squeekboard layouts
- Improved Sound file and favorites selection
- Hardware specific pages in Tour
- Support notches of 16 more phones
- Support trie predictor in p-o-s
- Support more emojis in p-o-s

Check out the full release notes at phosh.mobi/releases/rel-0.37.0

#phosh #gnome #linux #mobile #LinuxMobile #GNOMEMobile

#Librem5 and notebook sharing the same keyboard and mouse.

Moving the mouse over the edge of the screen into the direction of the other device brings the mouse focus to the other device - just like moving the mouse between displays in a dual screen setup.

The keyboard focus follows. It is like a kvm that is controlled by the mouse position.

Let's #deskhop!

@flathub Ah, the communication was pretty much non-existent and left me confused for hours. I've noticed that the CI publish job has failed and didn't really know why until I dug into logs of earlier jobs (that were marked as successful), searched the error message from there on the Web and then stumbled upon github.com/flathub/flathub/iss which made me look at the website.

Apparently there should have been an e-mail - I haven't got any though. The takeaway: "don't touch permissions when not needed" 馃槀

Looks like Flathub has just punished me for removing an unnecessary permission from the app I published by putting the update into moderation queue 馃槄 The queue itself is a welcome new addition to the infra, but perhaps it still needs some adjustments regarding the incentives it offers to the developers 馃槣 docs.flathub.org/blog/improved @flathub

We now provide nightly builds for Phosh and some related 馃摝 targeting #Debian Trixie thus making the current development
versions easier to test on Debian and Debian based distributions like @mobian (and hopefully in the future #PureOS):

More details at
phosh.mobi/posts/phosh-nightly

Show more
Librem Social

Librem Social is an opt-in public network. Messages are shared under Creative Commons BY-SA 4.0 license terms. Policy.

Stay safe. Please abide by our code of conduct.

(Source code)

image/svg+xml Librem Chat image/svg+xml