In typical Qubes fashion, the docs on the 4.3 are wrong and unfixed even though a pull request has been sitting there. I followed pre reboot and post reboot instructions an am completely screwed. Yes I backed up and can reinstall my whole system
from scratch but you sloppy incompetents should remove the in place upgrade option. It failed like most things about this project. You can’t even document it right so no surprise the code failed. 100% amateur hour.
Worked great for me and many others. Maybe if you give a bit more info we can help you resolve this and avoid having to restore everything.
Since when we allow people talking like that in the Forum ?
I disagree with you about “most things are failed about this project”.
Excuse me, if you think you’re competent enough, why dont you help this project a proper documentation? I too failed at 4.3 in-place upgrade, but with the patience marmarek came to help and everything worked as expected.
My motivation to help someone who expresses themselves so stupidly and insults developers who create software for free is close to zero.
8 posts were merged into an existing topic: Why not all comments on the forum are acceptable
This is the attitude I try to adopt when participating in online communities: When I visit someone else’s community, I consider myself a guest in their online home. I try to behave accordingly. My participation is a privilege, and is subject to the owner’s discretion.
Some people seem to have a really hard time with the whole notion of privately funded/owned online communities. They can’t accept that they don’t have the right to ‘free speech’ everywhere online. They visit their favourite online communities expecting to be able to rant and rave about anything they wish. I’d call that a delusion. (I know of some forums where you’d be banned immediately for that.)
Please keep the project going and try to contribute.
Been using Qubes 10 years, I was here when this toxic “community” was created and have watched it slide into garbage.
This is the second time performing a mundane user action nuked my entire laptop.
marmarek STILL has no sense of quality control or respect for users.
Erroneous upgrade instructions reported in December still aren’t fixed. Someone from the community even made a PR to fix. It is being ignored. Toxic, dysfunctional, garbage.
Someone upthead said the upgrade is working fine. lol! You can find MANY people dominating results with borked installs on a simple forum search for 4.3 upgrade Search results for '4.3 upgrade ' - Qubes OS Forum
The first hit it someone hitting my exact issue in December
Someone on the team tries to claim it is due to edge case weird setups. Nope! I am using only standard templates, nothing weird in dom0, ultra basic 4.2 install, still failed.
QUBES SUCKS. Garbage battery life, endless Xen exploits, toxic community that would rather mod the forum than commit a docs PR or test install scripts. And I bring up my laptop getting borked twice with this OS and you just get a bunch of Stockholm syndrome posters trying to claim this is some weird exception. Qubes has NEVER actually worked well. If you actually had used it as long as me and watched its long slide
you would know this. Some day you will.
As for my tone, I used to try and be positive, offer fixes, make tutorial or two. I had it with being condescended to and actively told my work wasn’t welcome by people like …. Well I won’t name them but two names come straight to mind. People pretending to be helpful stewards but just shutting people out and gatekeeping. Ya I’m bitter, because I offered to help and was shut out. So here we are. I’ll just say: this sucks. Bad software bad community.
I don’t mean to make light of your frustration, just an observation, with your name and avatar my brain naturally acts out your posts in-character, and it’s like perfect. Anyway, I’m sorry for your upgrade travails and I hope you overcome them swiftly and then have a long sequence of convenient days.
I’ve been unhappy with previous upgrade scripts, but this one worked
fine for me, and a good number of other users. It’s noteworthy that OP
in the thread you referred to upgraded in place on five systems, and hit
an issue with only one.
People who do not have issues are far less likely to report in
the forum than people who do.
I take responsibility for parulin’s (draft) PR not being merged, but
that PR does not address the issue that you have reported in your case,
that has affected some users but not others. Partly this is because I
have been trying to isolate the issue - @marcos-morar suggested that it
was triggered when KDE was installed, but this is not a sufficient
condition. And, of course, you encountered issues on what seems to be
a vanilla system.
Toxic, dysfunctional, garbage.
[… 11 lines elided]
QUBES SUCKS
Touch grass. Then, restore from your backup.
Please don’t take any responsibility for that. I don’t understand why we should expect you to carefully review and merge this PR when no one else has reviewed it? Especially when this is mostly a clarification of the instructions, nothing essential.
(Actually, I just changed the status of the PR to draft because I introduced a “strongly discouraged” way to use gpg.)
You should have a look at the relevant statistics:
That’s around 7.5 relevant security issues per year. Other operating systems, including Linux, get this in about one or two weeks.
Apart from this, I am just wondering how you were able to endure Qubes for 10 years, if it’s so bad.
You can’t really discard that qubes os is also affected by all Linux related vulnerabilities. It’s just that if they were to be exploited, the damages would be limited (managed?).
Contained.
Hi there.
My experience has been - on the contrary - better on previous upgrade script release.
I’ve two installed qubes but in this run the “usb-installed-one” is dead, because between pre-reboot and post-reboot stage, usb management is disabled.
It’s for security reason, of course, so I’ve not reported anything untill now, but statistically speaking, new script fails more than previous one.
Another thing I noted: previous release reminded to disable external repos (as 3isec), but not this one, so if it’s your first upgrade, it - simply - doesn’t work!
I hope these modest suggestions may be considered in next upgrade script version.
Thanks a lot.
Cheers.
That’s just the big advantage: With native Linux, you’re cooked, but in Qubes, only a VM - hopefully an AppVM - is ruined, and you can easily survive that in most cases.
Posting a link to the draft PR here would have been actually helpful. Identifying points within that have delayed applying it, moreso.
Upgrade-in-place working is a benefit that cannot be expected, but must be admired. (It did work for me. Thanks to those who made that happen!) In anticipation of applying the PR, identifying system details that make it risky, and noting that it may well not work regardless would anyway help calibrate expectations.
It has been posted at least 3 times before:
No one reviewed it and there are/were other PRs that are/were more important: this PR won’t fix anything special.