46
you are viewing a single comment's thread
view the rest of the comments
view the rest of the comments
this post was submitted on 13 Mar 2024
46 points (79.5% liked)
Selfhosted
40246 readers
454 users here now
A place to share alternatives to popular online services that can be self-hosted without giving up privacy or locking you into a service you don't control.
Rules:
-
Be civil: we're here to support and learn from one another. Insults won't be tolerated. Flame wars are frowned upon.
-
No spam posting.
-
Posts have to be centered around self-hosting. There are other communities for discussing hardware or home computing. If it's not obvious why your post topic revolves around selfhosting, please include details to make it clear.
-
Don't duplicate the full text of your blog or github here. Just post the link for folks to click.
-
Submission headline should match the article title (don’t cherry-pick information from the title to fit your agenda).
-
No trolling.
Resources:
- selfh.st Newsletter and index of selfhosted software and apps
- awesome-selfhosted software
- awesome-sysadmin resources
- Self-Hosted Podcast from Jupiter Broadcasting
Any issues on the community? Report it using the report flag.
Questions? DM the mods!
founded 1 year ago
MODERATORS
You're right but if an installer renders a computer inoperable until reboot (tried in another PC, same result, doesn't only kill explorer.exe because if I run it again via taskmgr, the taskbar is broken and non functional until reboot) it means it has been pushed to the "stable" channel without being tested a single time.
The problem is present since 2021 and it's a bit ridiculous now https://github.com/nextcloud/desktop/issues/3551
In the topic you can see the devs "ok fixed in next release" => next release didn't fix it (=nobody actually clicked the exe before releasing, it just passed all automated tests), then "ok so next release gonna fix it", and again again
It has been said to gracefully restart explorer.exe instead of crashing it, it still chooses violence for a restart. It asks "do you want to reboot" twice.
I like having the bleeding edge stuff, running nextcloud in docker under the "latest" tag, but those are clearly nightlies
I think this one https://github.com/nextcloud/desktop/issues/5369 is probably the more relevant, and also open, issue. However even in that issue people claim you can choose not to. The argument is only that it suggests restarting explorer and also rebooting and that this is annoying. So you never get a prompt, it just dies?
I agree though that the amount of time where it was force rebooting is pretty bad, and it looks like the rollout of the patch was mishandled. I also should probably admit that I've never touched the windows client, my environment is entirely Linux and Android. The Linux client even with file manager integration doesn't require restarts of anything.