[HOME] [DOWNLOAD] [DOCS] [NEWS] [SUPPORT] [TIPS] [ISSUES] [DONATE]

Qubes-Whonix version 14 (Debian stretch based) can be upgraded to version 15 (Debian buster based). - Testers Wanted!

testers-wanted
#1

Upgrades are possible.

Qubes-Whonix version 14 (Debian stretch based) can be upgraded to version 15 (Debian buster based).

Testers wanted!


New Qubes-Whonix 15 TemplateVM downloads are unavailable at this time and will require more time (prerequisite). Another news will be posted when these become available.


Other Whonix platforms version 15:
See Whonix News Blog

1 Like
#2
  • Expected behavior (i think) while upgrading:

  • useful in case of Qubes-Whonix only.
apt-get purge exim*
  • Running

apt-get install qubes-whonix-gateway

will give:

root@host:/home/user# apt-get install qubes-whonix-gateway
Reading package lists... Done
Building dependency tree       
Reading state information... Done
Some packages could not be installed. This may mean that you have
requested an impossible situation or if you are using the unstable
distribution that some required packages have not yet been created
or been moved out of Incoming.
The following information may help to resolve the situation:

The following packages have unmet dependencies:
 qubes-whonix-gateway : Depends: hardened-desktop-applications-xfce but it is not going to be installed
E: Unable to correct problems, you have held broken packages.
root@host:/home/user#

as result of that it will give this message after reboot:


There is one issue and its inside Qubes-Whonix&Vbox-Whonix the presence of duplicate “Xfce Terminal” name but one is the known konsole/terminal and one for terminal settings though both of them containing the same name.

#3

So what’s the package conflict?

sudo apt-get install -f
1 Like
#4

no package conflicting its an error to whonix repository , i was on whonix tester 14 before when i upgraded to whonix 15 the repository changed to this:

deb https://deb.whonix.org n/a-testers main contrib non-free

-> n/a-testers

while it should be buster-testers.


There is as well 2 similar names “FileManager” one to customize file manager and one i dunno what for and when i press on the one that i dunno what is for it show this message:

filemanager

Thunar File Manager already there and you can see the folders through it normally.

1 Like
#5

Nyx showing: (GW 15)

[WARN] Socks version 71 not recognized. (This port is not an HTTP proxy; did you want to use HTTPTunnelPort?)

according to https://tor.stackexchange.com/questions/3435/how-do-i-configure-chrome-to-use-tor
and so as here https://stackoverflow.com/questions/17719516/trouble-in-tor-with-c-sharp

thats mean there is one service in GW talking to Tor as an HTTP service while it should be SOCKS. how do we know which one?

1 Like
#6

Whonix 14 to 15 showing hash weak error to libd5.3:

Err:121 tor+http://vwakviie2ienjx6t.onion/debian buster/main amd64 libdb5.3 amd64 5.3.28+dfsg1-0.5                                                                        
  Hash Sum mismatch
  Hashes of expected file:
   - SHA256:c7f0e9a423840731362ee52d4344c0bcf84318fbc06dad4fefe0e61d9e7062bc
   - MD5Sum:c5dd77595d2b94a8f833227815fef78c [weak]
   - Filesize:683176 [weak]
  Hashes of received file:
   - SHA256:5e905fde3320b6c9a072b7d5bd0a6feb96562add4f11a6051ea1e317255b869f
   - MD5Sum:100e22a5417fedbbd6537848c41d24ea [weak]
   - Filesize:107162 [weak]
  Last modification reported: Tue, 26 Feb 2019 10:11:55 +0000

sudo apt update --fix-missing && sudo dist-upgrade

^ seems fixed it


Then after that there is a blockage to the upgrade:

maybe because i used --no-install-recommends then i fixed the missing packages with dist-upgrade ? i dunno what causing that…


There is no ability shown to move files between VMs inside whonix 15:

1 Like
#7

Similar to an existing ARM FAQ entry but now added the exact wording there too:
https://www.whonix.org/wiki/Tor_Controller#Arm_FAQ

1 Like
#8

Transient upgrading errors are advised to ignore as per https://rsync.whonix.org/wiki/Operating_System_Software_and_Updates.

1 Like
#9

TNT_BOM_BOM via Whonix Forum:

no package conflicting its an error to whonix repository , i was one tester 14 before when i upgraded to whonix 15 the repository changed to this:

deb https://deb.whonix.org n/a-testers main contrib non-free

-> n/a-testers

while it should be buster-testers.

I don’t know how this could happen. whonix_repository already had code
to safeguard against $codename being set to n/a.

Could you please provide instructions how to reproduce this issue?

I can imagine that this would happen if you run whonix_repository during
the upgrade. With new files from stretch but still old whonix-repository
package. Please don’t run whonix_repository while upgrades are still
running.

I’ve added a series of commits to further safeguard against $codename
being set to n/a. Package upgraded to version 5.4-1 all buster
repositories.

Please check your local version is same as

Otherwise please run whonix_repository with debugging so I can see how
this happens:

sudo bash -x whonix_repository --enable --repository testers

There is as well 2 similar names “FileManager” one to customize file manager and one i dunno what for and when i press on the one that i dunno what is for it show this message:

filemanager

Thunar File Manager already there and you can see the folders through it normally.

Can you report this please do Qubes, mentioning this happens when
upgrading to Debian buster with file manager thunar?

1 Like
#10

Actually, it shouldn’t happen. whonixcheck has code to safeguard against this. Package manager running check runs before Tor Pid Check. If a package manager is still running, whonixcheck should stay silent. (Since when package manager upgrades Tor, is is normal for Tor to be stopped for a while.)

Tor Pid Check shouldn’t run in Qubes TemplateVM anyhow.

Looks like this happened while upgrading a Standalone Whonix-Gateway or sys-whonix? In that case this might help at the beginning before upgrading:

sudo systemctl stop whonixcheck
1 Like
#11

A lot issues reported here. Thanks! I guess I should have addressed each of them in this thread. Should I have forgotten any, please remind me.

1 Like
#12

yes

1 Like
#13
  • Thunar issue resolved by installing libexo-1-0
  • Update Qubes onion repos to the new one:
1 Like
#14
1 Like
#15

I noticed that there are two entries in Qubes-Settings > Applications for “Xfce Terminal” for the gateway and workstation. One is the actual terminal and the other is the terminal preferences. They even have the same icon.

The root of the problem is that /usr/share/applications/xfce4-terminal{,-settings}.desktop both have the entries Name=Xfce4 Terminal and Icon=utilities-terminal.

2 Likes
#16

qubenix via Whonix Forum:

I noticed that there are two entries in Qubes-Settings > Applications for “Xfce Terminal” for the gateway and workstation. One is the actual terminal and the other is the terminal preferences. They even have the same icon.

The root of the problem is that /usr/share/applications/xfce4-terminal{,-settings}.desktop both have the entries Name=Xfce4 Terminal and Icon=utilities-terminal.

Qubes Debian buster bug. Could you report it to Qubes please?

#17

Reported here: https://github.com/QubesOS/qubes-issues/issues/4993

2 Likes