System Update Daemon & UI Feedback #871
sorceresslucienne
started this conversation in
Ideas
Replies: 1 comment 4 replies
-
|
Hey thanks for that feedback! It’s worth opening an issue report in system settings for a button to restart and update from within system settings however we probably should prevent system settings and elementary settings daemon from running in other desktops since they contain a lot of stuff that’s specific to pantheon. So many settings will just not apply or will probably conflict and maybe cause breakage with other desktop environments. It’s really not meant to be a mix-n-match kind of situation. I know that’s not a answer that you’d like to hear sorry! |
Beta Was this translation helpful? Give feedback.
4 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Uh oh!
There was an error while loading. Please reload this page.
Uh oh!
There was an error while loading. Please reload this page.
-
Hi,
So first of all, I fully acknowledge that by using xfce in place of Pantheon as my daily driver I am outside the realm of support. With that said, I think there is some nuance for discussion here and so I'll share my experience in good faith anyway. This is something I have a solution for myself personally so there's no real issue here even if this discussion is closed with a blanket "No.", but think there are some opportunities to streamline things for folks using Pantheon and other desktop environments if you'll hear me out. More potential users for you and more flexibility for your existing ones, is my thinking. Ultimately I think this is such a great distro to support, and so even though I am using Pantheon less than y'all probably want me to lol, I still am proud and happy to be using elementary OS and want to help improve it.
Bummer is though, unlike the backend for the AppCenter (which I assume is the "io.elementary.appcenter --silent" task running in the background at login), the "System Settings"/system updates daemon ("io.elementary.settings-daemon") does not start up automatically at login in other desktop environments. I've remedied this for myself, but I'm curious why this is the case when it isn't for the AppCenter one. Is this something that could be modified to do regardless of whether Pantheon is in use?
For reference, you just get a "Cannot connect to the backend" error when you check for system updates if you try. No big deal - you start the daemon up and tell it to check again and it works. The implication of this though obviously is that if you do want to switch desktop environments, you'll never get system updates unless you notice the daemon isn't running and fix that for yourself. It didn't even occur to me at first that system updates aren't coming through the AppCenter, and that there even was a separate daemon for those.
Again, if these things aren't possible or are totally outside the realm of what you want to touch development-wise, I understand. With that said, these are a small couple of changes that could give folks like myself a little bit more flex to use whatever they want while still being in elementary OS' ecosystem.
Let me know if I posted this in the wrong place. :-) I don't have a lot of personal experience using GitHub and don't know y'all's workflows either.
Thanks, y'all!
-Eri
Beta Was this translation helpful? Give feedback.
All reactions