Recent install, R4.3.0 ; And yet, Global Config/This Device says…R4.3.1-rc1 ! There’s no way I would opt for that much pain. I did not re-install or do an in place upgrade. Please tell me this ‘rc1’ is a typographical error. Is updating now equal to a release candidate version ? I’m sorry this aspect of my problem is in the “wrong” catagory. I really just want to fix the Global Clipboard.
1 Like
It’s a typo in the sense that the rc1 is “efectively” stable. (Same over here.) See @marmarek 's comment:
2 Likes
For the rc1 label, I’d treat it separately from the clipboard problem. It looks like the known 4.3.1 version-string issue rather than proof that you installed a release-candidate ISO.
For the global clipboard, what exactly fails: copy from AppVM to dom0, paste from dom0 to AppVM, or both? Also useful: the source/target qubes, whether you see the dom0 notification/prompt, and if you changed anything under /etc/qubes/policy.d. That should narrow it down faster than chasing the rc1 text.
1 Like
At the time you wrote this, it was, yes:
[…] since Qubes 4.3.1 is a patch release, it’s essentially Qubes 4.3.0 inclusive of all updates to date, which largely amounts to just using a fully-updated 4.3.0 installation.
From:
However, I can certainly understand why it would be unsettling for users who specifically choose stable releases for production systems involving important work to see that they’re suddenly testing an RC just because they updated normally.
On the other hand, I can also imagine 4.3.0 users who want to test 4.3.1-rc1 by updating normally being perplexed that updating doesn’t bring them up to 4.3.1-rc1.
@marmarek, any ideas for how we should handle this situation?
(Personally, I’m leaning toward the position that normal updating should never result in being on an RC. In other words, once you install a stable release, all updates from stable repos should result in a stable release. Updates from testing repos could result in a testing release, though.)
3 Likes
Opened an issue:
(FWIW, I also see the same thing on my system.)
1 Like
The latest release updates (release package 4.3.4) fixed things. Global config now says “4.3.1”.
1 Like
Thank you for your response. 'Sorry it’s taken so long on my end. Copying from AppVM to Dom0 fails. I’m not sure about the dom0 notification-(what would it say ?). After I try to copy something; Iclick on the global clipboard ico and it says, “global cilboard is empty”. I have not changed anything in /etc/qubes/policy.d .
It should in that direction. That’s part of the concept.
Oui, ce comportement est attendu si la destination est dom0. Le presse-papiers global de Qubes sert surtout à transférer entre qubes, pas à faire entrer directement le contenu d’une AppVM dans dom0. Pour isoler le problème, je testerais d’abord AppVM A → AppVM B avec le raccourci global prévu, puis dom0 → AppVM dans l’autre sens. Si ces deux cas marchent, le message “global clipboard is empty” quand tu vises dom0 n’indique probablement pas une panne de ta config, mais la limite de sécurité normale.