I’ll probably continue working on my Swift GTK/libadwaita wrapper and the demo project that makes use of the library. Doing it this way has been very pleasant, it allows me to put it through real world tests and helps me identify stopgaps in the toolkit I wouldn’t otherwise notice through unit tests alone.
- 1 Post
- 12 Comments
Joined 6 years ago
Cake day: September 8th, 2020
You are not logged in. If you use a Fediverse account that is able to follow users, you can follow this user.
2·4 months agoGiven the first few commits referring to scaffolding phases and the frequent use of em dashes, I’m suspicious this was built with AI assistance. Nothing wrong with that, but a disclaimer of some sort somewhere would go a long way.
Yeah, device support is the biggest issue. But the OS as a whole is pretty good. I used it with a OnePlus 6T and a Nothing Phone 1, both of which have pretty decent support. Some things about it were broken, and I didn’t try putting in a SIM card and making calls or texts, but the overall experience was good. I have high hopes for when we eventually get good “flagship” linux mobile phones that have full PostmarketOS compatibility.
Out of curiosity, what about PostmarketOS is not daily driveable? Postmarket is a vague umbrella OS with a lot of DE options, all of which have vastly different user experiences. KDE mobile, phosh, and GNOME mobile have all come a long way and provide everything a smartphone OS needs. The only thing I’d argue that could prevent daily driving is lack of app support and lack of good mobile Linux hardware, but that’s not PostmarketOS’s problem.
Very well said. Thank you very much for your help. I wouldn’t have know to check the ownership issues or if GDM were properly running Wayland were it not for your help. I’ll reach out to the GNOME devs on the relevant repositories and see if they might be able to point me in the right direction. Thank you for your time and expertise.
Yes. Here’s the contents I currently have in
/var/lib/gdm/.config/monitors.xml:physical 0 0 1 yes DP-1 SAM Odyssey G93SC HNTW700164 5120 1440 239.997 bt2100 HDMI-1 FUN Evanlak8K V2 0x00006410The disabled dummy plug is the “Evanlak8K V2” device while my functional monitor is my Samsung Odyssey OLED G9. This config is the same as the one currently running on my GNOME desktop config, but in GDM still defaults to the enabled dummy plug, even with the fixed ownership.
Just checked the ownership of the monitor config, it was
gdm:root, so I changed the ownership togdm:gdmand rebooted. Still facing the same issue.Didn’t see any error messages in the logs about not being able to load wayland, but just to confirm, I ran
loginctl show-session {gdm session id} -p Typewhich returnsType=wayland, so it’s definitely running under wayland. I have an AMD GPU though so I wouldn’t expect there to be any problems there.Not seeing anything else weird in the logs that are jumping out as strange to me either, so a bit at a loss here. Any other suggestions?
More accurately, It uses WebkitGTK, which is a fork of Webkit. Blink, the engine Chromium and Chromium based browsers use, is also a fork of Webkit.
I had a few Raspberry Pis and some Libre Computer boards a while back, but I recently decided to just build a beefy small form factor PC and put Proxmox on it, and honestly couldn’t be happier with the results. The ability to allocate resources for services and containers on the fly is a game changer. I can spin up a fresh container running whatever service I want in a matter of minutes without the hassle of flashing to a device and setting up networking, etc.
Any specific reason why you’d like to move away from Fedora? It’s an amazing distro, all things considered.
I’m loving my Aqara Matter smart thermostat. It can do everything the Nest and Ecobees can do and works entirely locally communicating directly with my Home Assistant instance and costs less than the competition. No third party app necessary. Configurable over Wi-Fi or Zigbee over Thread.