Yes, based on the diagrams on their blog, it looks like this only impacts Snaps.
From the Discourse Blog:
The Linux desktop provides XDG Desktop Portals as a standardised way for applications to access resources that are outside of the sandbox. Applications that have been updated to use XDG Desktop Portals will continue to use them. Prompting is not intended to replace XDG Desktop Portals but to complement them by providing the desktop an alternative way to ask the user for permission. Either when an application has not been updated to use XDG Desktop Portals, or when it makes access requests not covered by XDG Desktop Portals.
Since prompting works at the syscall level, it does not require an application’s awareness or cooperation to work and extends the set of applications that can be run inside of a sandbox, allowing for a safer desktop. It is designed to enable desktop applications to take full advantage of snap packaging that might otherwise require classic confinement.
So this looks like it complements and not replaces the XDG Desktop Portals, especially for applications that have not implemented the Portals. It allows you to still run those applications in confinement while providing some more granular access controls.
From what I can tell, Pop!_OS does not ship their own version of timeshift. Instead, it comes directly from Ubuntu. So if there is a change in maintainers, it should be reported to Ubuntu:
I used to use VLC for music, but these days I use Symphony to play local files on my phone. VLC tended to struggle when scanning or indexing large folders (which it did all the time…), while Symphony is a bit better at that. That said, I still use VLC for video and for casting things from my DLNA server (VLC supports Chromecast).
For ebooks, I’ve used Librera FD and that has been mostly OK. I’ll checkout the two you mentioned though. Thanks!
On Ubuntu, there is a program called “Firmware Updater” which uses LVFS to retrieve and install firmware updates (including BIOS/UEFI).
According to this page: https://fwupd.org/lvfs/devices/com.lenovo.ThinkPadN23ETXXW.firmware your Carbon X1 Gen 6 should be supported.
All my servers moved to 24.04 and I wanted my desktop to keep in line with them (so they all had the same packages). Likewise, I’ve been following the development of GNOME and I really liked what they have done with versions 45 and 46, so I wanted to try a more modern version of that desktop environment (Pop 22.04 is still on GNOME 42 and is now missing out on some cool features like the quick settings menu).
Finally, I wanted to try out Wayland and the experience on Pop 22.04 is not great with Wayland, especially since it is missing out on the more recent fixes and updates in Ubuntu 24.04.
If you are happy with Pop 22.04 and willing to wait for COSMIC to stabilize and become feature complete, then that is what you should do. For me, I used this delay in releasing Pop 24.04 as an opportunity to try out something different and for the most part, I’m pretty happy with the experience.
Unfortunately, there will not be a release of Pop 24.04 with GNOME before COSMIC is released. In fact, System76 has stopped development of Pop-shell as referenced here:
https://reddit.com/r/pop_os/comments/1eo59wj/will_xorg_still_be_an_option_in_2404/
Once, Pop 24.04 is released, you will be able to install gnome-session to get GNOME, but it will be the version from Ubuntu and not Pop-shell (though you can install the unsupported extension yourself).
Basically, the development of COSMIC is delaying the release of Pop 24.04… which means the whole distro update probably won’t come until 2025 as the desktop matures.
For this reason, among others, I’ve decided to switch to Ubuntu until COSMIC matures and Pop 24.04 is released.
I think you meant Pop!_OS (is developed by System76). TuxedoOS is developed by Tuxedo Computers, which is a European Linux focused hardware company.
That said, the point stands… there are hardware companies making Linux supported devices.
The default “App Center” does not support flatpaks (only snaps). However, if you install the GNOME software center with the suggested dependencies:
$ sudo apt install --install-suggests gnome-software
Then you will be able to install flatpaks, debs, and snaps.
If you are using Pop!_OS 22.04, then you are using gdm. You can just create the file if it doesn’t exist.
If you are using gdm
as your login manager, you can put the command in ~/.xprofile
… which is sourced by gdm3
.
Hi! Did you read my reply in the other post you made in !system76@lemmy.ml?
Was is this article How to install the Rust Cosmic Desktop environment on Pop!_OS?
Either way, if you want to use the new COSMIC login screen, you can install the cosmic-greeter package:
sudo apt install cosmic-greeter
Once that is installed, you should be able to switch back and forth between cosmic-greeter and gdm3 with:
sudo dpkg-reconfigure gdm3
and selecting whichever login manager you wish to use.
I’ve been using Weechat-Android to connect to my self-hosted Weechat for over a decade. This is one of the killer mobile apps that keeps me on Android and I love it.
I also have a couple instances of thelounge that people use on mobile via the PWA (progressive web app).
Oh. I’m sorry if this was discussed previously… I only returned to lemmy a few weeks ago and didn’t see the story covered yet.
I think the WINE project was maintaining a fork of Mono that was used to support running certain Windows applications:
So in addition to translating traditional WIN32 system calls, WINE also supports .NET applications, which a number of Windows programs require.
Coincidentally, I received a firmware (EFI) update from Dell today via LVFS. Really nice that it works so smoothly on native Linux (no more manually downloading firmware to USB drives, or relying on Windows).
This reddit post seems relevant. A user mentions:
I found out that only the containers having these kind of networking problems where all running the container in “host” networking mode.https://docs.docker.com/network/drivers/
Since I don’t need host mode, I can just comment that line out, and it will start using the standard Bridge (which will be used by default if you don’t specify any networking settings for your containers)
This is running under docker as you had in your initial configuration.
Another reddit post mentions setting the gateway and DNS server if you have a static IP:
It turned out to be nothing to do with Plex but rather was the fact that there was missing information on my static IP setup. Once I added in the gateway and DNS information those extraneous messages went away.
I’m not sure if that will help, but it’s perhaps something you could consider as you debug this issue. Good luck.
The reasons for this shift in budget away from funding Free Software and the NGI initiative seems to be an allocation of more funds for AI, leaving internet infrastructure by the wayside. Meanwhile, the EC has thus far declined to comment to share its official reasoning for striking this funding from its budget.
Sigh. It appears that they are chasing after the latest “shiny” thing instead of investing in existing infrastructure. Not surprising, but disappointing.
Pretty happy that we opted out of the Slack AI “feature” at work.
Still using mutt after two decades (with isync for fetching).