Join GitHub today
GitHub is home to over 28 million developers working together to host and review code, manage projects, and build software together.
Sign upaptitude is not working in Whonix VMs #3882
Comments
This comment has been minimized.
Show comment
Hide comment
This comment has been minimized.
andrewdavidwong
added
bug
C: Whonix
labels
May 6, 2018
andrewdavidwong
added this to the Release 4.0 updates milestone
May 6, 2018
This comment has been minimized.
Show comment
Hide comment
This comment has been minimized.
adrelanos
May 6, 2018
Member
Maybe uwt issue.
https://github.com/Whonix/qubes-whonix/blob/master/etc/uwt.d/40_qubes.conf#L70
What if you run sudo aptitude-curses update directly, does that work?
~ $ ls -la /usr/bin/aptitude
lrwxrwxrwx 1 root root 26 Aug 9 2016 /usr/bin/aptitude -> /etc/alternatives/aptitude
~ $ ls -la /etc/alternatives/aptitude
lrwxrwxrwx 1 root root 24 Aug 9 2016 /etc/alternatives/aptitude -> /usr/bin/aptitude-curses
Looks same for you?
|
Maybe uwt issue. https://github.com/Whonix/qubes-whonix/blob/master/etc/uwt.d/40_qubes.conf#L70 What if you run
Looks same for you? |
This comment has been minimized.
Show comment
Hide comment
This comment has been minimized.
starius
May 6, 2018
What if you run sudo aptitude-curses update directly, does that work?
No, I see the same errors:
W: Failed to fetch http://security.debian.org/dists/jessie/updates/contrib/binary-amd64/Packages:
Cannot initiate the connection to 127.0.0.1:8082 (127.0.0.1). - connect (1: Operation not permitted)
Looks same for you?
Yes.
I did not change anything in Whonix templates - it happened right after installation of Qubes 4.
starius
commented
May 6, 2018
No, I see the same errors:
Yes. I did not change anything in Whonix templates - it happened right after installation of Qubes 4. |
added a commit
to Whonix/uwt
that referenced
this issue
Jun 5, 2018
This comment has been minimized.
Show comment
Hide comment
This comment has been minimized.
|
Note to self: works in Qubes-Whonix 14 / Qubes R3.2 |
This comment has been minimized.
Show comment
Hide comment
This comment has been minimized.
|
This is fixed in Qubes-Whonix 14 after upgrades. Please test. |
This comment has been minimized.
Show comment
Hide comment
This comment has been minimized.
starius
Jun 13, 2018
I upgraded everything using Qube Manager and restarted the VM. Still getting that error.
How to check the Whonix version I am using?
$ lsb_release -a
No LSB modules are available.
Distributor ID: Whonix
Description: Whonix GNU/Linux 8.10 (jessie)
Release: 8.10
Codename: jessie
starius
commented
Jun 13, 2018
|
I upgraded everything using Qube Manager and restarted the VM. Still getting that error.
|
This comment has been minimized.
Show comment
Hide comment
This comment has been minimized.
adrelanos
Jun 14, 2018
Member
Expected. You're on stable rather than testers-only version. Fixed inQubes-Whonix 14 after upgrades only.
|
Expected. You're on stable rather than testers-only version. Fixed inQubes-Whonix 14 after upgrades only. |
starius commentedMay 5, 2018
Qubes OS version:
R4.0Affected component(s):
Whonix
Steps to reproduce the behavior:
Open Konsole in
whonix-gworwhonix-wsand typesudo aptitude updateExpected behavior:
I expect the command to work.
Actual behavior:
The command fails.
At the same time,
apt-getworks in Whonix. Also, on Debian bothapt-getandaptitudework.