[Touch-packages] [Bug 2004416] Re: Bluetooth Headset Loses Audio

[Daniel van Vugt]

The full set of messages related to this bug seems to be:

Jan 31 22:26:18 t935 wireplumber[1791]: 0x56370f33ca08: error 24
Jan 31 22:26:18 t935 wireplumber[1791]: RFCOMM write error: Connection reset by 
peer
Jan 31 22:26:18 t935 acpid[876]: input device has been disconnected, fd 18
Jan 31 22:26:18 t935 bluetoothd[885]: src/profile.c:ext_io_disconnected() 
Unable to get io data for Hands-Free Voice gateway: getpeername: Transport 
endpoint is not connected (107)
Jan 31 22:26:18 t935 wireplumber[1791]: (bluez_output.04_5D_4B_29_06_26.1-24) 
running -> error (Received error event)
Jan 31 22:26:18 t935 dbus-daemon[888]: [system] Rejected send message, 0 
matched rules; type="method_return", sender=":1.80" (uid=1000 pid=1791 
comm="/usr/bin/wireplumber" label="unconfined") interface="(unset)" 
member="(unset)" error name="(unset)" requested_reply="0" destination=":1.11" 
(uid=0 pid=885 comm="/usr/lib/bluetooth/bluetoothd" label="unconfined")
Jan 31 22:26:18 t935 pipewire[1789]: pw.node: 
(bluez_output.04_5D_4B_29_06_26.1-60) running -> error (Received error event)
Jan 31 22:26:18 t935 gsd-media-keys[2098]: Unable to get default sink

Although sometimes the first couple are missing. So it seems like a full
Bluetooth stack issue always starting in bluetoothd (BlueZ). That's not
to say it's definitely a software bug because it sounds like the headset
might have disconnected to begin with.

** Summary changed:

- Bluetooth Headset Loses Audio
+ Bluetooth Headset Loses Audio [pw.node: (bluez_output.04_5D_4B_29_06_26.1-80) 
running -> error (Received error event)]

** Package changed: linux (Ubuntu) => bluez (Ubuntu)

** Changed in: bluez (Ubuntu)
   Status: Incomplete => New

** Attachment removed: "journal.txt"
   
https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/2004416/+attachment/5644345/+files/journal.txt

** Attachment removed: "journal.txt"
   
https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/2004416/+attachment/5644337/+files/journal.txt

** Attachment removed: "lspci.txt"
   
https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/2004416/+attachment/5644338/+files/lspci.txt

** Attachment removed: "lsusb.txt"
   
https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/2004416/+attachment/5644339/+files/lsusb.txt

** Attachment removed: "rfkill.txt"
   
https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/2004416/+attachment/5644340/+files/rfkill.txt

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to bluez in Ubuntu.
https://bugs.launchpad.net/bugs/2004416

Title:
  Bluetooth Headset Loses Audio [pw.node:
  (bluez_output.04_5D_4B_29_06_26.1-80) running -> error (Received error
  event)]

Status in bluez package in Ubuntu:
  New

Bug description:
  I keep finding that some time after connecting and listening to audio
  with my Bluetooth headset, the audio fails to play on them.  If I turn
  them off and back on again, it works.  So far, if I am listening, it
  doesn't quit, but if I stop and try to listen to audio again after a
  while, there is no sound.  This error in the logs prompted me to
  submit this bug to pipewire.

  pw.node: (bluez_output.04_5D_4B_29_06_26.1-80) running -> error
  (Received error event)

  I'd be happy to try and help debug this if you need me to try things.

  Rob

  ProblemType: Bug
  DistroRelease: Ubuntu 22.10
  Package: pipewire 0.3.58-2ubuntu1
  ProcVersionSignature: Ubuntu 5.19.0-29.30-generic 5.19.17
  Uname: Linux 5.19.0-29-generic x86_64
  ApportVersion: 2.23.1-0ubuntu3
  Architecture: amd64
  CasperMD5CheckResult: pass
  CurrentDesktop: ubuntu:GNOME
  Date: Tue Jan 31 09:18:37 2023
  InstallationDate: Installed on 2021-05-25 (616 days ago)
  InstallationMedia: Ubuntu 21.04 "Hirsute Hippo" - Release amd64 (20210420)
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: pipewire
  UpgradeStatus: Upgraded to kinetic on 2022-10-26 (97 days ago)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/2004416/+subscriptions


-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp

[Touch-packages] [Bug 2004416] [NEW] Bluetooth Headset Loses Audio [pw.node: (bluez_output.04_5D_4B_29_06_26.1-80) running -> error (Received error event)]

[Launchpad Bug Tracker]

You have been subscribed to a public bug:

I keep finding that some time after connecting and listening to audio
with my Bluetooth headset, the audio fails to play on them.  If I turn
them off and back on again, it works.  So far, if I am listening, it
doesn't quit, but if I stop and try to listen to audio again after a
while, there is no sound.  This error in the logs prompted me to submit
this bug to pipewire.

pw.node: (bluez_output.04_5D_4B_29_06_26.1-80) running -> error
(Received error event)

I'd be happy to try and help debug this if you need me to try things.

Rob

ProblemType: Bug
DistroRelease: Ubuntu 22.10
Package: pipewire 0.3.58-2ubuntu1
ProcVersionSignature: Ubuntu 5.19.0-29.30-generic 5.19.17
Uname: Linux 5.19.0-29-generic x86_64
ApportVersion: 2.23.1-0ubuntu3
Architecture: amd64
CasperMD5CheckResult: pass
CurrentDesktop: ubuntu:GNOME
Date: Tue Jan 31 09:18:37 2023
InstallationDate: Installed on 2021-05-25 (616 days ago)
InstallationMedia: Ubuntu 21.04 "Hirsute Hippo" - Release amd64 (20210420)
ProcEnviron:
 TERM=xterm-256color
 PATH=(custom, no user)
 XDG_RUNTIME_DIR=
 LANG=en_US.UTF-8
 SHELL=/bin/bash
SourcePackage: pipewire
UpgradeStatus: Upgraded to kinetic on 2022-10-26 (97 days ago)

** Affects: bluez (Ubuntu)
 Importance: Undecided
 Status: New


** Tags: amd64 apport-bug kinetic wayland-session
-- 
Bluetooth Headset Loses Audio [pw.node: (bluez_output.04_5D_4B_29_06_26.1-80) 
running -> error (Received error event)]
https://bugs.launchpad.net/bugs/2004416
You received this bug notification because you are a member of Ubuntu Touch 
seeded packages, which is subscribed to bluez in Ubuntu.

-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp

[Touch-packages] [Bug 1972790] Re: Can't connect to hotspot created on ubuntu

[John Pietrzak]

I'd just like to repeat, this is Linux.  Just because Ubuntu offers a
feature doesn't mean you have to use it.  I'm using the "Linux Wifi
Hotspot" app created by Lakinduakash:

https://github.com/lakinduakash/linux-wifi-hotspot

It works just fine on Ubuntu.

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to wpa in Ubuntu.
https://bugs.launchpad.net/bugs/1972790

Title:
  Can't connect to hotspot created on ubuntu

Status in wpa package in Ubuntu:
  Confirmed

Bug description:
  We currently have older systems (18.04) with hotspot's and we will migrate to 
22.04.
  Anything work's fine, expect the hotspot.
  The Hotspot will be created and is visible in the WLAN-List, but if the 
security is set to "WPA & WPA2 Personal" we get the error message "Failed to 
connect to the network".
  If we change the Security to "WPA3 Personal" we get the error message 
"Invalid Password", even if the password is correct.
  As soon we remove the security (change it to "none"), we can connect with out 
any problems.

  We can reproduce it with a fresh installtion of the Ubuntu Server
  22.04 and the following two commands:

  apt install network-manager

  nmcli c add type wifi ifname wlp3s0 con-name Hotspot autoconnect yes
  ssid test-ap 802-11-wireless.mode ap 802-11-wireless.band bg
  802-11-wireless.mac-address "80:45:dd:f0:27:ba" wifi-sec.group ccmp
  wifi-sec.key-mgmt wpa-psk wifi-sec.pairwise ccmp wifi-sec.proto rsn
  wifi-sec.psk "test12345" ipv4.addresses 192.168.60.1/24 ipv4.method
  shared && nmcli connection up Hotspot

  
  We thought it could be similar to this issue: 
https://bugs.launchpad.net/ubuntu/+source/wpa/+bug/1958267
  Because if we test it with 20.04 it worked fine, because 20.04 uses the 
Version 2:2.9.0-21build1 as described in the Ticket.

  As @Sebastian Bacher suggested 
(https://bugs.launchpad.net/ubuntu/+source/wpa/+bug/1958267/comments/58), i 
created a own report.
  In the attachment is the requested log file.

  ProblemType: Bug
  DistroRelease: Ubuntu 22.04
  Package: wpasupplicant 2:2.10-6 [modified: 
lib/systemd/system/wpa_supplicant.service]
  ProcVersionSignature: Ubuntu 5.15.0-25.25-generic 5.15.30
  Uname: Linux 5.15.0-25-generic x86_64
  ApportVersion: 2.20.11-0ubuntu82
  Architecture: amd64
  CasperMD5CheckResult: pass
  Date: Tue May 10 07:24:15 2022
  InstallationDate: Installed on 2022-05-10 (0 days ago)
  InstallationMedia: Ubuntu-Server 22.04 LTS "Jammy Jellyfish" - Release amd64 
(20220421)
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   LANG=de_DE.UTF-8
   SHELL=/bin/bash
  SourcePackage: wpa
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/wpa/+bug/1972790/+subscriptions


-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp

[Touch-packages] [Bug 1972790] Re: Can't connect to hotspot created on ubuntu

[Serj Fomin]

Unassigned

I see nobody give a  about this bug! Ubuntu is garbage without such
important features as Hotspot. Back to Windows. The only adequate OS
unfortunately. I hope some day Ubuntu will be usefull, without countless
stupid bugs.

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to wpa in Ubuntu.
https://bugs.launchpad.net/bugs/1972790

Title:
  Can't connect to hotspot created on ubuntu

Status in wpa package in Ubuntu:
  Confirmed

Bug description:
  We currently have older systems (18.04) with hotspot's and we will migrate to 
22.04.
  Anything work's fine, expect the hotspot.
  The Hotspot will be created and is visible in the WLAN-List, but if the 
security is set to "WPA & WPA2 Personal" we get the error message "Failed to 
connect to the network".
  If we change the Security to "WPA3 Personal" we get the error message 
"Invalid Password", even if the password is correct.
  As soon we remove the security (change it to "none"), we can connect with out 
any problems.

  We can reproduce it with a fresh installtion of the Ubuntu Server
  22.04 and the following two commands:

  apt install network-manager

  nmcli c add type wifi ifname wlp3s0 con-name Hotspot autoconnect yes
  ssid test-ap 802-11-wireless.mode ap 802-11-wireless.band bg
  802-11-wireless.mac-address "80:45:dd:f0:27:ba" wifi-sec.group ccmp
  wifi-sec.key-mgmt wpa-psk wifi-sec.pairwise ccmp wifi-sec.proto rsn
  wifi-sec.psk "test12345" ipv4.addresses 192.168.60.1/24 ipv4.method
  shared && nmcli connection up Hotspot

  
  We thought it could be similar to this issue: 
https://bugs.launchpad.net/ubuntu/+source/wpa/+bug/1958267
  Because if we test it with 20.04 it worked fine, because 20.04 uses the 
Version 2:2.9.0-21build1 as described in the Ticket.

  As @Sebastian Bacher suggested 
(https://bugs.launchpad.net/ubuntu/+source/wpa/+bug/1958267/comments/58), i 
created a own report.
  In the attachment is the requested log file.

  ProblemType: Bug
  DistroRelease: Ubuntu 22.04
  Package: wpasupplicant 2:2.10-6 [modified: 
lib/systemd/system/wpa_supplicant.service]
  ProcVersionSignature: Ubuntu 5.15.0-25.25-generic 5.15.30
  Uname: Linux 5.15.0-25-generic x86_64
  ApportVersion: 2.20.11-0ubuntu82
  Architecture: amd64
  CasperMD5CheckResult: pass
  Date: Tue May 10 07:24:15 2022
  InstallationDate: Installed on 2022-05-10 (0 days ago)
  InstallationMedia: Ubuntu-Server 22.04 LTS "Jammy Jellyfish" - Release amd64 
(20220421)
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   LANG=de_DE.UTF-8
   SHELL=/bin/bash
  SourcePackage: wpa
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/wpa/+bug/1972790/+subscriptions


-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp

[Touch-packages] [Bug 2000817] Re: Wrong SHA256-value computed on kinetic

[Launchpad Bug Tracker]

** Merge proposal linked:
   
https://code.launchpad.net/~ahasenack/ubuntu/+source/openldap/+git/openldap/+merge/436723

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to openldap in Ubuntu.
https://bugs.launchpad.net/bugs/2000817

Title:
  Wrong SHA256-value computed on kinetic

Status in openldap package in Ubuntu:
  Triaged

Bug description:
  The OpenLDAP-contrib module sha2 (located in contrib/slapd-
  modules/passwd/sha2/) computes a wrong SHA256/SSHA256-hash on Ubuntu
  kinetic. This breaks our current password-authentication in ldap.

  
  The problematic computation:

  $ slappasswd -s secret -h '{SHA256}' -o module-load=pw-sha2
  {SHA256}WIrrpN3OjEVOUf6yrH1j+o+ODuUuNBo979Od4UXnu54=

  The (correct) reference-value on the same system (or older ubuntu
  Versions):

  $ echo -n "secret" | openssl dgst -sha256 -binary | openssl enc -base64
  K7gNU3sdo+OL0wNhqoVWhr3g6s1xYv72ol/pe/Unols=

  
  We nailed the problem down to a bug in the gcc-optimizer for strict-aliasing. 
so most probably the gcc-version on kinetic (v12.2.0) is the reason. The 
workaround is to compile the sha2-Module with the flag "-fno-strict-aliasing". 
Then the correct value is computed. An example taken from a git-compiled 
version of OpenLDAP 2.5.13:

  $ ./servers/slapd/slappasswd -T passwd -s secret -h '{SHA256}' -o 
module-load=pw-sha2 -o module-path=contrib/slapd-modules/passwd/sha2/.libs
  {SHA256}K7gNU3sdo+OL0wNhqoVWhr3g6s1xYv72ol/pe/Unols=


  
  Ubuntu:

  Description:Ubuntu 22.10
  Release:22.10

  OpenLDAP-Package: 2.5.13+dfsg-1ubuntu1

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/openldap/+bug/2000817/+subscriptions


-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp

[Touch-packages] [Bug 1988819] Re: When apt keeps back packages due to phased updates, it should say nothing

[Walter]

Haha, yea, long time debian/ubuntu user here too. The only way I found
out and know was because my script that parses apt-policy failed [1].
Pure luck [2].

Also seconding the do-translations-later. I don't know if there are
statistics available for this, but based on anecdotal evidence alone, I
say that many people run their OS in English anyway. And that the
average debian/ubuntu user is used to more English than average users of
proprietary operating systems..

[1] 
https://github.com/ossobv/vcutil/commit/9a34b973491f7165790f8c239f1b1c39bf4d1687
[2] Yay for defensive coding.

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to apt in Ubuntu.
https://bugs.launchpad.net/bugs/1988819

Title:
  When apt keeps back packages due to phased updates, it should say
  nothing

Status in apt package in Ubuntu:
  Triaged

Bug description:
  After phased updates have been introduced, it may happen that apt
  upgrade shows packages as upgradable but ends up not upgrading them.
  In this case the packages are indicated as being "kept back".

  Unfortunately, the feedback provided about this to the user is not
  very informative. The user sees the packages being kept back and
  thinks something is going wrong on the system.

  When packages are kept back because of phased updates, apt should say
  so e.g., it should say that the upgrade is delayed.

  Incidentally note that aptitude does not respect phased updates.

  ProblemType: Bug
  DistroRelease: Ubuntu 22.04
  Package: apt 2.4.7
  ProcVersionSignature: Ubuntu 5.15.0-47.51-generic 5.15.46
  Uname: Linux 5.15.0-47-generic x86_64
  ApportVersion: 2.20.11-0ubuntu82.1
  Architecture: amd64
  CasperMD5CheckResult: unknown
  CurrentDesktop: KDE
  Date: Tue Sep  6 10:05:14 2022
  EcryptfsInUse: Yes
  InstallationDate: Installed on 2020-02-16 (933 days ago)
  InstallationMedia: Kubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017)
  SourcePackage: apt
  UpgradeStatus: Upgraded to jammy on 2022-06-03 (94 days ago)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/apt/+bug/1988819/+subscriptions


-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp

[Touch-packages] [Bug 2004505] Re: apt-key is still packaged

[Julian Andres Klode]

And it also will for 23.04

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to apt in Ubuntu.
https://bugs.launchpad.net/bugs/2004505

Title:
  apt-key is still packaged

Status in apt package in Ubuntu:
  New

Bug description:
  The apt-key(8) manpage includes:

  apt-key(8) will last be available in Debian 11 and Ubuntu 22.04.

  It appears that apt-key was shipped in Ubuntu 22.10 by accident.
  apt-key is still in the 2.5.5 apt packaged for Lunar:
  https://launchpad.net/ubuntu/lunar/amd64/apt/2.5.5

  ⏚ [sarnold:/tmp] $ wget 
http://launchpadlibrarian.net/646589288/apt_2.5.5_amd64.deb
  --2023-02-01 18:58:39--  
http://launchpadlibrarian.net/646589288/apt_2.5.5_amd64.deb
  Resolving launchpadlibrarian.net (launchpadlibrarian.net)... 
2620:2d:4000:1001::8007, 2620:2d:4000:1001::8008, 185.125.189.229, ...
  Connecting to launchpadlibrarian.net 
(launchpadlibrarian.net)|2620:2d:4000:1001::8007|:80... connected.
  HTTP request sent, awaiting response... 200 OK
  Length: 1377746 (1.3M) [application/x-debian-package]
  Saving to: ‘apt_2.5.5_amd64.deb’

  apt_2.5.5_amd64.deb
  
100%[>]
  1.31M  1.26MB/sin 1.0s

  2023-02-01 18:58:41 (1.26 MB/s) - ‘apt_2.5.5_amd64.deb’ saved
  [1377746/1377746]

  ⏚ [sarnold:/tmp] 2s $ ar x apt_2.5.5_amd64.deb 
  ⏚ [sarnold:/tmp] $ tar tf data.tar.zst | grep bin
  ./usr/bin/
  ./usr/bin/apt
  ./usr/bin/apt-cache
  ./usr/bin/apt-cdrom
  ./usr/bin/apt-config
  ./usr/bin/apt-get
  ./usr/bin/apt-key
  ./usr/bin/apt-mark
  ⏚ [sarnold:/tmp] $ 

  Thanks

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/apt/+bug/2004505/+subscriptions


-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp

[Touch-packages] [Bug 2004505] Re: apt-key is still packaged

[Julian Andres Klode]

The manual page is a bit overexcited:D

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to apt in Ubuntu.
https://bugs.launchpad.net/bugs/2004505

Title:
  apt-key is still packaged

Status in apt package in Ubuntu:
  New

Bug description:
  The apt-key(8) manpage includes:

  apt-key(8) will last be available in Debian 11 and Ubuntu 22.04.

  It appears that apt-key was shipped in Ubuntu 22.10 by accident.
  apt-key is still in the 2.5.5 apt packaged for Lunar:
  https://launchpad.net/ubuntu/lunar/amd64/apt/2.5.5

  ⏚ [sarnold:/tmp] $ wget 
http://launchpadlibrarian.net/646589288/apt_2.5.5_amd64.deb
  --2023-02-01 18:58:39--  
http://launchpadlibrarian.net/646589288/apt_2.5.5_amd64.deb
  Resolving launchpadlibrarian.net (launchpadlibrarian.net)... 
2620:2d:4000:1001::8007, 2620:2d:4000:1001::8008, 185.125.189.229, ...
  Connecting to launchpadlibrarian.net 
(launchpadlibrarian.net)|2620:2d:4000:1001::8007|:80... connected.
  HTTP request sent, awaiting response... 200 OK
  Length: 1377746 (1.3M) [application/x-debian-package]
  Saving to: ‘apt_2.5.5_amd64.deb’

  apt_2.5.5_amd64.deb
  
100%[>]
  1.31M  1.26MB/sin 1.0s

  2023-02-01 18:58:41 (1.26 MB/s) - ‘apt_2.5.5_amd64.deb’ saved
  [1377746/1377746]

  ⏚ [sarnold:/tmp] 2s $ ar x apt_2.5.5_amd64.deb 
  ⏚ [sarnold:/tmp] $ tar tf data.tar.zst | grep bin
  ./usr/bin/
  ./usr/bin/apt
  ./usr/bin/apt-cache
  ./usr/bin/apt-cdrom
  ./usr/bin/apt-config
  ./usr/bin/apt-get
  ./usr/bin/apt-key
  ./usr/bin/apt-mark
  ⏚ [sarnold:/tmp] $ 

  Thanks

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/apt/+bug/2004505/+subscriptions


-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp

[Touch-packages] [Bug 2004505] [NEW] apt-key is still packaged

[Seth Arnold]

Public bug reported:

The apt-key(8) manpage includes:

apt-key(8) will last be available in Debian 11 and Ubuntu 22.04.

It appears that apt-key was shipped in Ubuntu 22.10 by accident.
apt-key is still in the 2.5.5 apt packaged for Lunar:
https://launchpad.net/ubuntu/lunar/amd64/apt/2.5.5

⏚ [sarnold:/tmp] $ wget 
http://launchpadlibrarian.net/646589288/apt_2.5.5_amd64.deb
--2023-02-01 18:58:39--  
http://launchpadlibrarian.net/646589288/apt_2.5.5_amd64.deb
Resolving launchpadlibrarian.net (launchpadlibrarian.net)... 
2620:2d:4000:1001::8007, 2620:2d:4000:1001::8008, 185.125.189.229, ...
Connecting to launchpadlibrarian.net 
(launchpadlibrarian.net)|2620:2d:4000:1001::8007|:80... connected.
HTTP request sent, awaiting response... 200 OK
Length: 1377746 (1.3M) [application/x-debian-package]
Saving to: ‘apt_2.5.5_amd64.deb’

apt_2.5.5_amd64.deb
100%[>]
1.31M  1.26MB/sin 1.0s

2023-02-01 18:58:41 (1.26 MB/s) - ‘apt_2.5.5_amd64.deb’ saved
[1377746/1377746]

⏚ [sarnold:/tmp] 2s $ ar x apt_2.5.5_amd64.deb 
⏚ [sarnold:/tmp] $ tar tf data.tar.zst | grep bin
./usr/bin/
./usr/bin/apt
./usr/bin/apt-cache
./usr/bin/apt-cdrom
./usr/bin/apt-config
./usr/bin/apt-get
./usr/bin/apt-key
./usr/bin/apt-mark
⏚ [sarnold:/tmp] $ 

Thanks

** Affects: apt (Ubuntu)
 Importance: Undecided
 Status: New

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to apt in Ubuntu.
https://bugs.launchpad.net/bugs/2004505

Title:
  apt-key is still packaged

Status in apt package in Ubuntu:
  New

Bug description:
  The apt-key(8) manpage includes:

  apt-key(8) will last be available in Debian 11 and Ubuntu 22.04.

  It appears that apt-key was shipped in Ubuntu 22.10 by accident.
  apt-key is still in the 2.5.5 apt packaged for Lunar:
  https://launchpad.net/ubuntu/lunar/amd64/apt/2.5.5

  ⏚ [sarnold:/tmp] $ wget 
http://launchpadlibrarian.net/646589288/apt_2.5.5_amd64.deb
  --2023-02-01 18:58:39--  
http://launchpadlibrarian.net/646589288/apt_2.5.5_amd64.deb
  Resolving launchpadlibrarian.net (launchpadlibrarian.net)... 
2620:2d:4000:1001::8007, 2620:2d:4000:1001::8008, 185.125.189.229, ...
  Connecting to launchpadlibrarian.net 
(launchpadlibrarian.net)|2620:2d:4000:1001::8007|:80... connected.
  HTTP request sent, awaiting response... 200 OK
  Length: 1377746 (1.3M) [application/x-debian-package]
  Saving to: ‘apt_2.5.5_amd64.deb’

  apt_2.5.5_amd64.deb
  
100%[>]
  1.31M  1.26MB/sin 1.0s

  2023-02-01 18:58:41 (1.26 MB/s) - ‘apt_2.5.5_amd64.deb’ saved
  [1377746/1377746]

  ⏚ [sarnold:/tmp] 2s $ ar x apt_2.5.5_amd64.deb 
  ⏚ [sarnold:/tmp] $ tar tf data.tar.zst | grep bin
  ./usr/bin/
  ./usr/bin/apt
  ./usr/bin/apt-cache
  ./usr/bin/apt-cdrom
  ./usr/bin/apt-config
  ./usr/bin/apt-get
  ./usr/bin/apt-key
  ./usr/bin/apt-mark
  ⏚ [sarnold:/tmp] $ 

  Thanks

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/apt/+bug/2004505/+subscriptions


-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp

[Touch-packages] [Bug 1998207] Re: netplan network-manager plugin tries to save temporary connections

[Danilo Egea Gondolfo]

The same problem happens if you spin up an OpenVPN server and kill it.
An yaml file will be created for the tun interface used by the server.

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to network-manager in Ubuntu.
https://bugs.launchpad.net/bugs/1998207

Title:
  netplan network-manager plugin tries to save temporary connections

Status in netplan:
  Triaged
Status in network-manager package in Ubuntu:
  Triaged

Bug description:
  *** Note: This bug is mostly about comment #10, now ***

  When creating an OpenVPN connection, a temporal connection called tunN
  is created. For instance, after activating a connection called
  vpntest, I have:

  NAME  UUID  TYPE  DEVICE
  vpntest   458856e6-8f0f-4dc6-82f2-dd72868252a0  vpn   ens3
  tun0  1eb1dbe8-5678-4818-9adf-fb2dc01ed132  tun   tun0

  tun0 is created/removed after activating/deactivating vpntest and
  should not really be saved, but I see netplan adding it in
  /etc/netplan. And while doing so the plugin also reports some errors
  (I see these when stopping the connection):

  Nov 28 16:16:57 ubuntu NetworkManager[11752]:  [1669652217.2920] BUG: 
the profile cannot be stored in keyfile format without becoming unusable: 
cannot access file: No such file or directory
  Nov 28 16:16:57 ubuntu NetworkManager[11752]: 
((src/libnm-core-impl/nm-connection.c:342)): assertion '' failed
  Nov 28 16:16:57 ubuntu NetworkManager[11752]:   [1669652217.2920] 
keyfile: commit: failure to write 1eb1dbe8-5678-4818-9adf-fb2dc01ed132 ((null)) 
to 
"/run/NetworkManager/system-connections/tun0-1eb1dbe8-5678-4818-9adf-fb2dc01ed132.nmconnection":
 keyfile writer produces an invalid connection: cannot access file: No such 
file or directory

To manage notifications about this bug go to:
https://bugs.launchpad.net/netplan/+bug/1998207/+subscriptions


-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp

[Touch-packages] [Bug 2002660] Re: networkx incompatible with numpy 1.24

[Simon Quigley]

** Tags removed: update-excuse

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to python3-defaults in
Ubuntu.
https://bugs.launchpad.net/bugs/2002660

Title:
  networkx incompatible with numpy 1.24

Status in networkx package in Ubuntu:
  Fix Released
Status in nipype package in Ubuntu:
  Invalid
Status in python3-defaults package in Ubuntu:
  Invalid

Bug description:
  The nipype autopkgtests have started failing with the following stack
  trace:

   ERROR collecting pipeline/plugins/tests/test_tools.py 
_
  /usr/lib/python3.10/importlib/__init__.py:126: in import_module
  return _bootstrap._gcd_import(name[level:], package, level)
  :1050: in _gcd_import
  ???
  :1027: in _find_and_load
  ???
  :992: in _find_and_load_unlocked
  ???
  :241: in _call_with_frames_removed
  ???
  :1050: in _gcd_import
  ???
  :1027: in _find_and_load
  ???
  :992: in _find_and_load_unlocked
  ???
  :241: in _call_with_frames_removed
  ???
  :1050: in _gcd_import
  ???
  :1027: in _find_and_load
  ???
  :1006: in _find_and_load_unlocked
  ???
  :688: in _load_unlocked
  ???
  :883: in exec_module
  ???
  :241: in _call_with_frames_removed
  ???
  nipype/pipeline/plugins/__init__.py:5: in 
  from .debug import DebugPlugin
  nipype/pipeline/plugins/debug.py:7: in 
  import networkx as nx
  /usr/lib/python3/dist-packages/networkx/__init__.py:115: in 
  import networkx.readwrite
  /usr/lib/python3/dist-packages/networkx/readwrite/__init__.py:15: in 
  from networkx.readwrite.graphml import *
  /usr/lib/python3/dist-packages/networkx/readwrite/graphml.py:314: in 
  class GraphML(object):
  /usr/lib/python3/dist-packages/networkx/readwrite/graphml.py:346: in GraphML
  (np.int, "int"), (np.int8, "int"),
  /usr/lib/python3/dist-packages/numpy/__init__.py:284: in __getattr__
  raise AttributeError("module {!r} has no attribute "
  E   AttributeError: module 'numpy' has no attribute 'int'

  The problematic code is in the networkx package, and seems to have
  been fixed in
  
https://github.com/networkx/networkx/commit/207147ee179554a33f10f25032054d3e01f96188
  (which is in 2.5 onwards).

  Debian currently ships with 2.8.8, we might want to merge?

  This is currently blocking the python3-defaults transition.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/networkx/+bug/2002660/+subscriptions


-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp

[Touch-packages] [Bug 2002660] Re: networkx incompatible with numpy 1.24

[Steve Langasek]

** Changed in: python3-defaults (Ubuntu)
   Status: New => Invalid

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to python3-defaults in
Ubuntu.
https://bugs.launchpad.net/bugs/2002660

Title:
  networkx incompatible with numpy 1.24

Status in networkx package in Ubuntu:
  Fix Released
Status in nipype package in Ubuntu:
  Invalid
Status in python3-defaults package in Ubuntu:
  Invalid

Bug description:
  The nipype autopkgtests have started failing with the following stack
  trace:

   ERROR collecting pipeline/plugins/tests/test_tools.py 
_
  /usr/lib/python3.10/importlib/__init__.py:126: in import_module
  return _bootstrap._gcd_import(name[level:], package, level)
  :1050: in _gcd_import
  ???
  :1027: in _find_and_load
  ???
  :992: in _find_and_load_unlocked
  ???
  :241: in _call_with_frames_removed
  ???
  :1050: in _gcd_import
  ???
  :1027: in _find_and_load
  ???
  :992: in _find_and_load_unlocked
  ???
  :241: in _call_with_frames_removed
  ???
  :1050: in _gcd_import
  ???
  :1027: in _find_and_load
  ???
  :1006: in _find_and_load_unlocked
  ???
  :688: in _load_unlocked
  ???
  :883: in exec_module
  ???
  :241: in _call_with_frames_removed
  ???
  nipype/pipeline/plugins/__init__.py:5: in 
  from .debug import DebugPlugin
  nipype/pipeline/plugins/debug.py:7: in 
  import networkx as nx
  /usr/lib/python3/dist-packages/networkx/__init__.py:115: in 
  import networkx.readwrite
  /usr/lib/python3/dist-packages/networkx/readwrite/__init__.py:15: in 
  from networkx.readwrite.graphml import *
  /usr/lib/python3/dist-packages/networkx/readwrite/graphml.py:314: in 
  class GraphML(object):
  /usr/lib/python3/dist-packages/networkx/readwrite/graphml.py:346: in GraphML
  (np.int, "int"), (np.int8, "int"),
  /usr/lib/python3/dist-packages/numpy/__init__.py:284: in __getattr__
  raise AttributeError("module {!r} has no attribute "
  E   AttributeError: module 'numpy' has no attribute 'int'

  The problematic code is in the networkx package, and seems to have
  been fixed in
  
https://github.com/networkx/networkx/commit/207147ee179554a33f10f25032054d3e01f96188
  (which is in 2.5 onwards).

  Debian currently ships with 2.8.8, we might want to merge?

  This is currently blocking the python3-defaults transition.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/networkx/+bug/2002660/+subscriptions


-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp

[Touch-packages] [Bug 1562477] Re: apport-retrace crashed with TypeError in error(): not enough arguments for format string

[Benjamin Drung]

https://github.com/canonical/apport/pull/85 got merged.

** Changed in: apport
   Status: In Progress => Fix Committed

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to apport in Ubuntu.
https://bugs.launchpad.net/bugs/1562477

Title:
  apport-retrace crashed with TypeError in error(): not enough arguments
  for format string

Status in Apport:
  Fix Committed
Status in apport package in Ubuntu:
  Triaged

Bug description:
  Retracing the crash of window-buttons applet produced this error.

  ```
  Traceback (most recent call last):
File "/usr/bin/apport-retrace", line 301, in 
  options.dynamic_origins)
File "/usr/lib/python2.7/dist-packages/apport/sandboxutils.py", line 204, 
in make_sandbox
  apport.fatal(str(e))
File "/usr/lib/python2.7/dist-packages/apport/__init__.py", line 35, in 
fatal
  error(msg, *args)
File "/usr/lib/python2.7/dist-packages/apport/__init__.py", line 44, in 
error
  sys.stderr.write(msg % args)
  TypeError: not enough arguments for format string
  ```

  ProblemType: Crash
  DistroRelease: Ubuntu 16.04
  Package: apport-retrace 2.20-0ubuntu3
  ProcVersionSignature: Ubuntu 4.4.0-15.31-generic 4.4.6
  Uname: Linux 4.4.0-15-generic x86_64
  ApportVersion: 2.20-0ubuntu3
  Architecture: amd64
  CrashCounter: 1
  CurrentDesktop: GNOME-Flashback:Unity
  Date: Sun Mar 27 17:32:09 2016
  EcryptfsInUse: Yes
  ExecutablePath: /usr/bin/apport-retrace
  InstallationDate: Installed on 2015-09-28 (180 days ago)
  InstallationMedia: Ubuntu 15.04 "Vivid Vervet" - Release amd64 (20150422)
  InterpreterPath: /usr/bin/python2.7
  PackageArchitecture: all
  ProcCmdline: /usr/bin/python /usr/bin/apport-retrace -S system -C 
/home/username/.cache/apport/retrace -v --gdb 
/var/crash/_usr_lib_gnome-window-applets_windowbuttons.1000.crash
  PythonArgs: ['/usr/bin/apport-retrace', '-S', 'system', '-C', 
'/home/username/.cache/apport/retrace', '-v', '--gdb', 
'/var/crash/_usr_lib_gnome-window-applets_windowbuttons.1000.crash']
  SourcePackage: apport
  Title: apport-retrace crashed with TypeError in error(): not enough arguments 
for format string
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip docker kismet libvirtd lp lpadmin lxd mail mythtv 
plugdev sambashare sudo vboxusers

To manage notifications about this bug go to:
https://bugs.launchpad.net/apport/+bug/1562477/+subscriptions


-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp

[Touch-packages] [Bug 1933090] Re: systemd/245.4-4ubuntu3.6 ADT test failure with linux-hwe-5.11/5.11.0-20.21~20.04.1

[Roxana Nicolescu]

I run the test locally on a vm running linux-oracle-5.15-1029.
It seems `syscall(__NR__sysctl, NULL)` returns ENOSYS(38) -- Function not 
implemented.
Checking `/proc/kallsyms` it seems sysctl is not implemented indeed.

If I take a closer look at jammy-ubuntu tag in systemd source (test that is not 
failing currently)
I can see that it asserts for either EFAULT or ENOSYS:

assert_se(IN_SET(errno, EFAULT, ENOSYS));

This patch will solve the issue:

diff --git a/src/test/test-seccomp.c b/src/test/test-seccomp.c
index 67900d85e..7ebcca4d3 100644
--- a/src/test/test-seccomp.c
+++ b/src/test/test-seccomp.c
@@ -307,7 +307,7 @@ static void test_protect_sysctl(void) {
 if (pid == 0) {
 #if defined __NR__sysctl && __NR__sysctl >= 0
 assert_se(syscall(__NR__sysctl, NULL) < 0);
-assert_se(errno == EFAULT);
+assert_se(IN_SET(errno, EFAULT, ENOSYS));
 #endif

 assert_se(seccomp_protect_sysctl() >= 0);

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to systemd in Ubuntu.
https://bugs.launchpad.net/bugs/1933090

Title:
  systemd/245.4-4ubuntu3.6 ADT test failure with linux-
  hwe-5.11/5.11.0-20.21~20.04.1

Status in linux-hwe-5.11 package in Ubuntu:
  Won't Fix
Status in linux-hwe-5.15 package in Ubuntu:
  New
Status in systemd package in Ubuntu:
  New
Status in linux-hwe-5.11 source package in Focal:
  Won't Fix
Status in linux-hwe-5.15 source package in Focal:
  New
Status in systemd source package in Focal:
  New

Bug description:
  This is a scripted bug report about ADT failures while running systemd
  tests for linux-hwe-5.11/5.11.0-20.21~20.04.1 on focal. Whether this
  is caused by the dep8 tests of the tested source or the kernel has yet
  to be determined.

  Testing failed on:
  amd64: 
https://autopkgtest.ubuntu.com/results/autopkgtest-focal/focal/amd64/s/systemd/20210611_220645_bf5b6@/log.gz
  armhf: 
https://autopkgtest.ubuntu.com/results/autopkgtest-focal/focal/armhf/s/systemd/20210617_124738_5b554@/log.gz
  ppc64el: 
https://autopkgtest.ubuntu.com/results/autopkgtest-focal/focal/ppc64el/s/systemd/20210611_235629_92856@/log.gz
  s390x: 
https://autopkgtest.ubuntu.com/results/autopkgtest-focal/focal/s390x/s/systemd/20210611_214456_6427f@/log.gz

  In arm64, ppc64el and s390x, 'root-unittests' fails with:

  /* test_protect_sysctl */
  Assertion 'errno == EFAULT' failed at src/test/test-seccomp.c:311, function 
test_protect_sysctl(). A
  borting.
  sysctlseccomp terminated by signal ABRT.
  Assertion 'wait_for_terminate_and_check("sysctlseccomp", pid, WAIT_LOG) == 
EXIT_SUCCESS' failed at s
  rc/test/test-seccomp.c:324, function test_protect_sysctl(). Aborting.
  FAIL: test-seccomp (code: 134)

  In amd64, 'upstream' also fails on 'TEST-24-UNIT-TESTS', which
  apparently is caused by the same 'test-seccomp.c:311' assertion
  failure.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux-hwe-5.11/+bug/1933090/+subscriptions


-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp

[Touch-packages] [Bug 2004482] Re: /usr/bin/software-properties-gtk:ModuleNotFoundError:/usr/bin/software-properties-gtk@37:/usr/lib/python3/dist-packages/softwareproperties/gtk/SoftwarePropertiesGtk.

[Sebastien Bacher]

** Package changed: software-properties (Ubuntu) => ubuntu-advantage-
tools (Ubuntu)

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to software-properties in
Ubuntu.
https://bugs.launchpad.net/bugs/2004482

Title:
  /usr/bin/software-properties-
  gtk:ModuleNotFoundError:/usr/bin/software-properties-
  gtk@37:/usr/lib/python3/dist-
  
packages/softwareproperties/gtk/SoftwarePropertiesGtk.py@57:/usr/lib/python3/dist-
  packages/softwareproperties/gtk/UbuntuProPage.py@27:/usr/lib/python3/dist-
  packages/softwareproperties/gtk/DialogUaAttach.py@25

Status in ubuntu-advantage-tools package in Ubuntu:
  New

Bug description:
  The Ubuntu Error Tracker has been receiving reports about a problem regarding 
software-properties.  This problem was most recently seen with package version 
0.99.9.10, the problem page at 
https://errors.ubuntu.com/problem/4b05d8835016bb4e877825ae6aff4814cbfccabf 
contains more details, including versions of packages affected, stacktrace or 
traceback, and individual crash reports.
  If you do not have access to the Ubuntu Error Tracker and are a software 
developer, you can request it at http://forms.canonical.com/reports/.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/ubuntu-advantage-tools/+bug/2004482/+subscriptions


-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp

[Touch-packages] [Bug 2004477] Re: Can't launch proton vpn

[Donald H Locker]

** Description changed:

  crypto.py crashes when starting protonvpn:
  
  $ protonvpn-cli connect SE1
Tue Jan 31 07:08:04 AM EST 2023
  Traceback (most recent call last):
File "/usr/bin/protonvpn-cli", line 11, in 
  load_entry_point('protonvpn-cli==3.13.0', 'console_scripts', 
'protonvpn-cli')()
File "/usr/lib/python3/dist-packages/protonvpn_cli/main.py", line 20, in 
main
  from .cli import ProtonVPNCLI
File "/usr/lib/python3/dist-packages/protonvpn_cli/cli.py", line 4, in 

  from proton.constants import VERSION as proton_version
File "/usr/lib/python3/dist-packages/proton/__init__.py", line 1, in 

  from .api import Session # noqa
File "/usr/lib/python3/dist-packages/proton/api.py", line 21, in 
  from .cert_pinning import TLSPinningAdapter
File "/usr/lib/python3/dist-packages/proton/cert_pinning.py", line 5, in 

  from OpenSSL import crypto
File "/usr/lib/python3/dist-packages/OpenSSL/__init__.py", line 8, in 

  from OpenSSL import crypto, SSL
File "/usr/lib/python3/dist-packages/OpenSSL/crypto.py", line 3279, in 

  _lib.OpenSSL_add_all_algorithms()
  AttributeError: module 'lib' has no attribute 'OpenSSL_add_all_algorithms'
  Tue Jan 31 07:08:05 AM EST 2023
  
  c.f. https://askubuntu.com/questions/1450578/couldnt-launch-proton-vpn
  
  but downgrading openssl package is not desirable for security reasons.
  
  per https://github.com/pyca/cryptography/issues/7959 and other hits on 
search, cryptography package 39.0.0 is incompatible with pyOpenSSL 21.0.0; 
cryptography 38.0.4 works with 21.0.0; cryptography 39.0.0 requires 22.1.0 or 
greater.
  Installed packages are python3-cryptography 3.4.8-1ubuntu2 and 21.0.0-1 
python3-openssl
- Currently, python3-openssl is not available from repo.
+ Currently, python3-openssl 22.1.0 is not available from repo.
  
  $ lsb_release -rd:
  Description:  Ubuntu 22.04.1 LTS
  Release:  22.04
  $ apt-cache policy python3-openssl
  python3-openssl:
Installed: 21.0.0-1
Candidate: 21.0.0-1
Version table:
   *** 21.0.0-1 500
  500 http://archive.ubuntu.com/ubuntu jammy/main amd64 Packages
  500 http://archive.ubuntu.com/ubuntu jammy/main i386 Packages
  100 /var/lib/dpkg/status
  $

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to openssl in Ubuntu.
https://bugs.launchpad.net/bugs/2004477

Title:
  Can't launch proton vpn

Status in openssl package in Ubuntu:
  New

Bug description:
  crypto.py crashes when starting protonvpn:

  $ protonvpn-cli connect SE1
Tue Jan 31 07:08:04 AM EST 2023
  Traceback (most recent call last):
File "/usr/bin/protonvpn-cli", line 11, in 
  load_entry_point('protonvpn-cli==3.13.0', 'console_scripts', 
'protonvpn-cli')()
File "/usr/lib/python3/dist-packages/protonvpn_cli/main.py", line 20, in 
main
  from .cli import ProtonVPNCLI
File "/usr/lib/python3/dist-packages/protonvpn_cli/cli.py", line 4, in 

  from proton.constants import VERSION as proton_version
File "/usr/lib/python3/dist-packages/proton/__init__.py", line 1, in 

  from .api import Session # noqa
File "/usr/lib/python3/dist-packages/proton/api.py", line 21, in 
  from .cert_pinning import TLSPinningAdapter
File "/usr/lib/python3/dist-packages/proton/cert_pinning.py", line 5, in 

  from OpenSSL import crypto
File "/usr/lib/python3/dist-packages/OpenSSL/__init__.py", line 8, in 

  from OpenSSL import crypto, SSL
File "/usr/lib/python3/dist-packages/OpenSSL/crypto.py", line 3279, in 

  _lib.OpenSSL_add_all_algorithms()
  AttributeError: module 'lib' has no attribute 'OpenSSL_add_all_algorithms'
  Tue Jan 31 07:08:05 AM EST 2023

  c.f. https://askubuntu.com/questions/1450578/couldnt-launch-proton-vpn

  but downgrading openssl package is not desirable for security reasons.

  per https://github.com/pyca/cryptography/issues/7959 and other hits on 
search, cryptography package 39.0.0 is incompatible with pyOpenSSL 21.0.0; 
cryptography 38.0.4 works with 21.0.0; cryptography 39.0.0 requires 22.1.0 or 
greater.
  Installed packages are python3-cryptography 3.4.8-1ubuntu2 and 21.0.0-1 
python3-openssl
  Currently, python3-openssl 22.1.0 is not available from repo.

  $ lsb_release -rd:
  Description:  Ubuntu 22.04.1 LTS
  Release:  22.04
  $ apt-cache policy python3-openssl
  python3-openssl:
Installed: 21.0.0-1
Candidate: 21.0.0-1
Version table:
   *** 21.0.0-1 500
  500 http://archive.ubuntu.com/ubuntu jammy/main amd64 Packages
  500 http://archive.ubuntu.com/ubuntu jammy/main i386 Packages
  100 /var/lib/dpkg/status
  $

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/openssl/+bug/2004477/+subscriptions


-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : 

[Touch-packages] [Bug 2004482] [NEW] /usr/bin/software-properties-gtk:ModuleNotFoundError:/usr/bin/software-properties-gtk@37:/usr/lib/python3/dist-packages/softwareproperties/gtk/SoftwarePropertiesGt

[errors.ubuntu.com bug bridge]

Public bug reported:

The Ubuntu Error Tracker has been receiving reports about a problem regarding 
software-properties.  This problem was most recently seen with package version 
0.99.9.10, the problem page at 
https://errors.ubuntu.com/problem/4b05d8835016bb4e877825ae6aff4814cbfccabf 
contains more details, including versions of packages affected, stacktrace or 
traceback, and individual crash reports.
If you do not have access to the Ubuntu Error Tracker and are a software 
developer, you can request it at http://forms.canonical.com/reports/.

** Affects: software-properties (Ubuntu)
 Importance: Undecided
 Status: New


** Tags: focal

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to software-properties in
Ubuntu.
https://bugs.launchpad.net/bugs/2004482

Title:
  /usr/bin/software-properties-
  gtk:ModuleNotFoundError:/usr/bin/software-properties-
  gtk@37:/usr/lib/python3/dist-
  
packages/softwareproperties/gtk/SoftwarePropertiesGtk.py@57:/usr/lib/python3/dist-
  packages/softwareproperties/gtk/UbuntuProPage.py@27:/usr/lib/python3/dist-
  packages/softwareproperties/gtk/DialogUaAttach.py@25

Status in software-properties package in Ubuntu:
  New

Bug description:
  The Ubuntu Error Tracker has been receiving reports about a problem regarding 
software-properties.  This problem was most recently seen with package version 
0.99.9.10, the problem page at 
https://errors.ubuntu.com/problem/4b05d8835016bb4e877825ae6aff4814cbfccabf 
contains more details, including versions of packages affected, stacktrace or 
traceback, and individual crash reports.
  If you do not have access to the Ubuntu Error Tracker and are a software 
developer, you can request it at http://forms.canonical.com/reports/.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/software-properties/+bug/2004482/+subscriptions


-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp

[Touch-packages] [Bug 1991606] Re: Invalid PEP440 package version breaking setuptools >= 60

[Launchpad Bug Tracker]

This bug was fixed in the package reportbug - 11.6.0ubuntu2

---
reportbug (11.6.0ubuntu2) lunar; urgency=medium

  * Make Python version PEP440 compliant (LP: #1991606)

 -- Benjamin Drung   Wed, 01 Feb 2023 11:03:46 +0100

** Changed in: reportbug (Ubuntu)
   Status: Fix Committed => Fix Released

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to python-debian in Ubuntu.
https://bugs.launchpad.net/bugs/1991606

Title:
  Invalid PEP440 package version breaking setuptools >= 60

Status in devscripts package in Ubuntu:
  New
Status in distro-info package in Ubuntu:
  Fix Released
Status in drslib package in Ubuntu:
  New
Status in duecredit package in Ubuntu:
  Fix Committed
Status in python-debian package in Ubuntu:
  Fix Committed
Status in reportbug package in Ubuntu:
  Fix Released
Status in ubuntu-dev-tools package in Ubuntu:
  Fix Committed
Status in devscripts source package in Bionic:
  New
Status in distro-info source package in Bionic:
  New
Status in drslib source package in Bionic:
  Invalid
Status in duecredit source package in Bionic:
  New
Status in python-debian source package in Bionic:
  Invalid
Status in reportbug source package in Bionic:
  New
Status in ubuntu-dev-tools source package in Bionic:
  New
Status in devscripts source package in Focal:
  New
Status in distro-info source package in Focal:
  New
Status in drslib source package in Focal:
  New
Status in duecredit source package in Focal:
  New
Status in python-debian source package in Focal:
  New
Status in reportbug source package in Focal:
  New
Status in ubuntu-dev-tools source package in Focal:
  New
Status in devscripts source package in Jammy:
  New
Status in distro-info source package in Jammy:
  New
Status in drslib source package in Jammy:
  New
Status in duecredit source package in Jammy:
  New
Status in python-debian source package in Jammy:
  New
Status in reportbug source package in Jammy:
  New
Status in ubuntu-dev-tools source package in Jammy:
  Invalid
Status in devscripts source package in Kinetic:
  New
Status in distro-info source package in Kinetic:
  New
Status in drslib source package in Kinetic:
  New
Status in duecredit source package in Kinetic:
  New
Status in python-debian source package in Kinetic:
  Invalid
Status in reportbug source package in Kinetic:
  New
Status in ubuntu-dev-tools source package in Kinetic:
  Invalid

Bug description:
  With setuptools 66, the versions of all packages visible in the Python
  environment *must* obey PEP440 .
  Otherwise, attempts to use pip to install a package with a setup.py-
  based build system, or other attempts to use the `pkg-resources`
  module, can produce errors like this:

    File 
"/builds/databiosphere/toil/venv/lib/python3.9/site-packages/pkg_resources/__init__.py",
 line 844, in _resolve_dist
  env = Environment(self.entries)
    File 
"/builds/databiosphere/toil/venv/lib/python3.9/site-packages/pkg_resources/__init__.py",
 line 1044, in __init__
  self.scan(search_path)
    File 
"/builds/databiosphere/toil/venv/lib/python3.9/site-packages/pkg_resources/__init__.py",
 line 1077, in scan
  self.add(dist)
    File 
"/builds/databiosphere/toil/venv/lib/python3.9/site-packages/pkg_resources/__init__.py",
 line 1096, in add
  dists.sort(key=operator.attrgetter('hashcmp'), reverse=True)
    File 
"/builds/databiosphere/toil/venv/lib/python3.9/site-packages/pkg_resources/__init__.py",
 line 2631, in hashcmp
  self.parsed_version,
    File 
"/builds/databiosphere/toil/venv/lib/python3.9/site-packages/pkg_resources/__init__.py",
 line 2678, in parsed_version
  self._parsed_version = parse_version(self.version)
    File 
"/builds/databiosphere/toil/venv/lib/python3.9/site-packages/pkg_resources/_vendor/packaging/version.py",
 line 266, in __init__
  raise InvalidVersion(f"Invalid version: '{version}'")
  pkg_resources.extern.packaging.version.InvalidVersion: Invalid version: 
'0.23ubuntu1'

  The official opinion of the setuptools maintainers seems to be that
  version strings of this form haven't *really* been allowed since about
  2014, and distributions need to change their package version naming
  scheme for Python packages they install, so that the resulting version
  strings obey PEP440. See for example
  .

  suffix 1build1 is invalid.

  Some python building tools, that verifies if version strings are
  compatible with PEP440, are failing.

  Example: python poetry: Invalid PEP 440 version: '1.1build1'

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/devscripts/+bug/1991606/+subscriptions


-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : 

[Touch-packages] [Bug 1993353] Re: Add posix message queue IPC mediation

[Heather Lemon]

### VERIFICATION DONE FOCAL ###
* These steps were copied from 
https://bugs.launchpad.net/ubuntu/+source/apparmor/+bug/1728130
as they are testing the same components, the setup is similar. * 

sudo add-apt-repository ppa:apparmor-dev/mqueue-dev
sudo apt update

# exchange keypair ssh
scp linux-* ubuntu@x.x.x.x:~

sudo dpkg -i linux*
sudo apt --fix-broken install

# edit /etc/default/grub
GRUB_DEFAULT='Advanced options for Ubuntu>Ubuntu, with Linux 5.4.0-131-generic'
sudo update-grub

restart/reboot machine

sudo apt-get upgrade apparmor

# go find menu entry and update grub
/boot/boot.cfg
# menuentry 'Ubuntu, with Linux 5.4.0-131-generic'

# execute command
GRUB_DEFAULT='Advanced options for Ubuntu>Ubuntu, with Linux 5.4.0-131-generic'

# should output
supports mqueue

sudo apt install ubuntu-dev-tools -y

pull-ppa-source --ppa georgiag/mqueue-sru apparmor focal

sudo apt-get install autoconf libtool -y

cd ./libraries/libapparmor/

./autogen.sh

export PYTHONPATH=/tmp/apparmor-2.13.3/libraries/libapparmor/swig/python
export PYTHON=/usr/bin/python3
export PYTHON_VERSION=3
export PYTHON_VERSIONS=python3
export USE_SYSTEM=1 make

./configure

sudo apt-get install flex dejagnu

make

sudo make check

sudo make install

cd binutils
make
make check
make install

cd ./libraries/libapparmor
sh ./autogen.sh
sh ./configure
make
make check
make install

cd parser
$ make # depends on libapparmor having been built first
$ make check

# run unit tests
cd /tests/regession/apparmor/
sudo make tests


# from the main directory
make -C parser check 

# all unit tests pass from the parser. 
Ran 66 tests in 44.800s
PASS
Generated 24964 xtransition interaction tests
Generated 45132 dbus tests
simple.pl .. ok   
All tests successful.
There are deprecation warnings, but those can be ignored. 

### VERIFICATION DONE FOCAL ###

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to apparmor in Ubuntu.
https://bugs.launchpad.net/bugs/1993353

Title:
  Add posix message queue IPC mediation

Status in apparmor package in Ubuntu:
  New
Status in apparmor source package in Focal:
  Fix Committed
Status in apparmor source package in Jammy:
  Fix Committed

Bug description:
  [ Impact ]

  We need to add IPC mediation support in the userspace tools, starting with 
posix message queue.
  This would improve security and lower the attack surface for applications
  There is already a proposal upstream:
  https://gitlab.com/apparmor/apparmor/-/merge_requests/858

  [ Test Plan ]

  In the merge request in the description there are several tests added.
  There are parser tests that can be run with "make -C parser check" in the 
project source tree.
  There are also tests for the python tools that can be run ith "make -C utils 
check" in the project source tree.
  There are also regression tests in tests/regression/apparmor. They run with 
the whole test suite when you run with "sudo make tests", but they can also be 
run individually with "sudo ./posix_mq.sh"

  [ Where problems could occur ]

  There could be problems related to Bug 1728130, where a policy was developed 
for a set of rules supported by a specific kernel, and if new mediation is 
available on newer kernels, then there will be some denied rules. Therefore we 
need to also prevent that from happening. This is already available in 
apparmor-3.+, but for older versions could be done by backporting the abi 
patches from
  apparmor-3.0.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/apparmor/+bug/1993353/+subscriptions


-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp

[Touch-packages] [Bug 1998263] Re: JPEG ( backing store not supported ) : many pictures won't open.

[Marian Rainer-Harbach]

I installed libgdk-pixbuf2.0-common (2.42.9+dfsg-1ubuntu1) and libgdk-
pixbuf-2.0-0 (2.42.9+dfsg-1ubuntu1) from the proposed repository on
22.10. I can confirm that I'm now able to open large images in eog that
I wasn't able to open before, so this looks good to me.

** Tags removed: verification-needed verification-needed-kinetic
** Tags added: verification-done verification-done-kinetic

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to gdk-pixbuf in Ubuntu.
https://bugs.launchpad.net/bugs/1998263

Title:
  JPEG ( backing store not supported ) : many pictures won't open.

Status in Eye of GNOME:
  Fix Released
Status in gdk-pixbuf:
  Fix Released
Status in gdk-pixbuf package in Ubuntu:
  Fix Released
Status in gdk-pixbuf source package in Jammy:
  Invalid
Status in gdk-pixbuf source package in Kinetic:
  Fix Committed
Status in gdk-pixbuf source package in Lunar:
  Fix Released

Bug description:
  * Impact

  Eog can't open high resolution jpg files

  * Test Case

  - download 
https://gitlab.gnome.org/GNOME/gdk-pixbuf/uploads/fcda5bc359fbf55a1b9755ba92c3303d/kwiatek.jpg
  - try to open the image in eog

  * Regression potential

  The change increase the memory usage limit for loading jpg, it could
  lead to put the system under memory pressure. The limit has been added
  in 22.10 though so it isn't a regression compared to the previous
  version of Ubuntu

  -

  
  Hi,

  22.10. Just try to open some .jpg files from my usual storage.

  Error interpreting jpeg file ( Backing store not supported. )

  Those same pictures open in other OSes ( 22.04, 20.04 and else. )

  Can't use those pictures as backgrounds.

  But able to open them in Gimp or Shotwell.

  Maybe related to : https://gitlab.gnome.org/GNOME/gdk-
  pixbuf/-/issues/216

  ProblemType: Bug
  DistroRelease: Ubuntu 22.10
  Package: eog 43.0-1
  ProcVersionSignature: Ubuntu 5.19.0-23.24-generic 5.19.7
  Uname: Linux 5.19.0-23-generic x86_64
  ApportVersion: 2.23.1-0ubuntu3
  Architecture: amd64
  CasperMD5CheckResult: pass
  CurrentDesktop: ubuntu:GNOME
  Date: Tue Nov 29 23:31:36 2022
  InstallationDate: Installed on 2022-10-27 (33 days ago)
  InstallationMedia: Ubuntu 22.10 "Kinetic Kudu" - Release amd64 (20221020)
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=fr_FR.UTF-8
   SHELL=/bin/bash
  SourcePackage: eog
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/eog/+bug/1998263/+subscriptions


-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp

[Touch-packages] [Bug 2004478] [NEW] systemd-networkd's dhcp4 client ignores local subnet routes

[Tuetuopay]

Public bug reported:

RFC3442 specifies option 121 (Classless Static Routes) that allow a DHCP
server to push arbitrary routes to a client. It has a Local Subnet
Routes section expliciting the behavior of routes with a null (0.0.0.0)
gateway.

Such routes are to be installed on the interface with a Link scope, to
mark them as directly available on the link without any gateway.

Networkd currently drops those routes, which is against the RFC, as
Linux has proper support for such routes.

This has been observed as broken on Ubuntu Jammy 22.04 LTS, but working
in previous LTS (Focall 20.04 and Bionic 18.04 tested).

1. Ubuntu release: 22.04.1 LTS
2. Systemd release: 249.11-0ubuntu3.6
3. Expected behavior: routes from DHCP option 121 with a gateway set to 0.0.0.0 
to be installed as "scope link"
4. Observed behavior: routes are silently dropped by systemd-networkd's dhcp 
client (actually logged with a debug level, effectively silently with the 
default configuration)

I wrote a fix that has been accepted in upstream systemd:
https://github.com/systemd/systemd/pull/26234, which applies cleanly to
the current package's sources obtained through apt-get source.

As this is a fix for something that is an actual regression, can it be
backported to Ubuntu 22.04's systemd tree?

Thanks.

** Affects: systemd (Ubuntu)
 Importance: Undecided
 Status: New

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to systemd in Ubuntu.
https://bugs.launchpad.net/bugs/2004478

Title:
  systemd-networkd's dhcp4 client ignores local subnet routes

Status in systemd package in Ubuntu:
  New

Bug description:
  RFC3442 specifies option 121 (Classless Static Routes) that allow a
  DHCP server to push arbitrary routes to a client. It has a Local
  Subnet Routes section expliciting the behavior of routes with a null
  (0.0.0.0) gateway.

  Such routes are to be installed on the interface with a Link scope, to
  mark them as directly available on the link without any gateway.

  Networkd currently drops those routes, which is against the RFC, as
  Linux has proper support for such routes.

  This has been observed as broken on Ubuntu Jammy 22.04 LTS, but
  working in previous LTS (Focall 20.04 and Bionic 18.04 tested).

  1. Ubuntu release: 22.04.1 LTS
  2. Systemd release: 249.11-0ubuntu3.6
  3. Expected behavior: routes from DHCP option 121 with a gateway set to 
0.0.0.0 to be installed as "scope link"
  4. Observed behavior: routes are silently dropped by systemd-networkd's dhcp 
client (actually logged with a debug level, effectively silently with the 
default configuration)

  I wrote a fix that has been accepted in upstream systemd:
  https://github.com/systemd/systemd/pull/26234, which applies cleanly
  to the current package's sources obtained through apt-get source.

  As this is a fix for something that is an actual regression, can it be
  backported to Ubuntu 22.04's systemd tree?

  Thanks.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/2004478/+subscriptions


-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp

[Touch-packages] [Bug 2004477] [NEW] Can't launch proton vpn

[Donald H Locker]

Public bug reported:

crypto.py crashes when starting protonvpn:

$ protonvpn-cli connect SE1
  Tue Jan 31 07:08:04 AM EST 2023
Traceback (most recent call last):
  File "/usr/bin/protonvpn-cli", line 11, in 
load_entry_point('protonvpn-cli==3.13.0', 'console_scripts', 
'protonvpn-cli')()
  File "/usr/lib/python3/dist-packages/protonvpn_cli/main.py", line 20, in main
from .cli import ProtonVPNCLI
  File "/usr/lib/python3/dist-packages/protonvpn_cli/cli.py", line 4, in 

from proton.constants import VERSION as proton_version
  File "/usr/lib/python3/dist-packages/proton/__init__.py", line 1, in 
from .api import Session # noqa
  File "/usr/lib/python3/dist-packages/proton/api.py", line 21, in 
from .cert_pinning import TLSPinningAdapter
  File "/usr/lib/python3/dist-packages/proton/cert_pinning.py", line 5, in 

from OpenSSL import crypto
  File "/usr/lib/python3/dist-packages/OpenSSL/__init__.py", line 8, in 
from OpenSSL import crypto, SSL
  File "/usr/lib/python3/dist-packages/OpenSSL/crypto.py", line 3279, in 

_lib.OpenSSL_add_all_algorithms()
AttributeError: module 'lib' has no attribute 'OpenSSL_add_all_algorithms'
Tue Jan 31 07:08:05 AM EST 2023

c.f. https://askubuntu.com/questions/1450578/couldnt-launch-proton-vpn

but downgrading openssl package is not desirable for security reasons.

per https://github.com/pyca/cryptography/issues/7959 and other hits on search, 
cryptography package 39.0.0 is incompatible with pyOpenSSL 21.0.0; cryptography 
38.0.4 works with 21.0.0; cryptography 39.0.0 requires 22.1.0 or greater.
Installed packages are python3-cryptography 3.4.8-1ubuntu2 and 21.0.0-1 
python3-openssl
Currently, python3-openssl is not available from repo.

$ lsb_release -rd:
Description:Ubuntu 22.04.1 LTS
Release:22.04
$ apt-cache policy python3-openssl
python3-openssl:
  Installed: 21.0.0-1
  Candidate: 21.0.0-1
  Version table:
 *** 21.0.0-1 500
500 http://archive.ubuntu.com/ubuntu jammy/main amd64 Packages
500 http://archive.ubuntu.com/ubuntu jammy/main i386 Packages
100 /var/lib/dpkg/status
$

** Affects: openssl (Ubuntu)
 Importance: Undecided
 Status: New


** Tags: cryptography openssl python python3

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to openssl in Ubuntu.
https://bugs.launchpad.net/bugs/2004477

Title:
  Can't launch proton vpn

Status in openssl package in Ubuntu:
  New

Bug description:
  crypto.py crashes when starting protonvpn:

  $ protonvpn-cli connect SE1
Tue Jan 31 07:08:04 AM EST 2023
  Traceback (most recent call last):
File "/usr/bin/protonvpn-cli", line 11, in 
  load_entry_point('protonvpn-cli==3.13.0', 'console_scripts', 
'protonvpn-cli')()
File "/usr/lib/python3/dist-packages/protonvpn_cli/main.py", line 20, in 
main
  from .cli import ProtonVPNCLI
File "/usr/lib/python3/dist-packages/protonvpn_cli/cli.py", line 4, in 

  from proton.constants import VERSION as proton_version
File "/usr/lib/python3/dist-packages/proton/__init__.py", line 1, in 

  from .api import Session # noqa
File "/usr/lib/python3/dist-packages/proton/api.py", line 21, in 
  from .cert_pinning import TLSPinningAdapter
File "/usr/lib/python3/dist-packages/proton/cert_pinning.py", line 5, in 

  from OpenSSL import crypto
File "/usr/lib/python3/dist-packages/OpenSSL/__init__.py", line 8, in 

  from OpenSSL import crypto, SSL
File "/usr/lib/python3/dist-packages/OpenSSL/crypto.py", line 3279, in 

  _lib.OpenSSL_add_all_algorithms()
  AttributeError: module 'lib' has no attribute 'OpenSSL_add_all_algorithms'
  Tue Jan 31 07:08:05 AM EST 2023

  c.f. https://askubuntu.com/questions/1450578/couldnt-launch-proton-vpn

  but downgrading openssl package is not desirable for security reasons.

  per https://github.com/pyca/cryptography/issues/7959 and other hits on 
search, cryptography package 39.0.0 is incompatible with pyOpenSSL 21.0.0; 
cryptography 38.0.4 works with 21.0.0; cryptography 39.0.0 requires 22.1.0 or 
greater.
  Installed packages are python3-cryptography 3.4.8-1ubuntu2 and 21.0.0-1 
python3-openssl
  Currently, python3-openssl is not available from repo.

  $ lsb_release -rd:
  Description:  Ubuntu 22.04.1 LTS
  Release:  22.04
  $ apt-cache policy python3-openssl
  python3-openssl:
Installed: 21.0.0-1
Candidate: 21.0.0-1
Version table:
   *** 21.0.0-1 500
  500 http://archive.ubuntu.com/ubuntu jammy/main amd64 Packages
  500 http://archive.ubuntu.com/ubuntu jammy/main i386 Packages
  100 /var/lib/dpkg/status
  $

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/openssl/+bug/2004477/+subscriptions


-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : 

[Touch-packages] [Bug 1971538] Re: My machine has Wi-Fi Hotspot broken after upgrade to 22.04

[Dilip]

WiFi hotspot not working for me in 22.04

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to network-manager in Ubuntu.
https://bugs.launchpad.net/bugs/1971538

Title:
  My machine has Wi-Fi Hotspot broken after upgrade to 22.04

Status in network-manager package in Ubuntu:
  Confirmed

Bug description:
  * Impact
  The hotspot feature fails to forward the data to the clients

  * Test case
  - log into an Ubuntu or GNOME session
  - connect the machine to an eth cable for internet
  - go to gnome-control-center -> wifi
  - enable the hotspot from the menu in the headerbar
  - connect another device to the wifi created
  -> the client should connect and access to internet work correctly

  Upon updating to 22.04, none of my machines can use the connection.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1971538/+subscriptions


-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp

[Touch-packages] [Bug 1971538] Re: My machine has Wi-Fi Hotspot broken after upgrade to 22.04

[Dilip]

I installed a fresh 22.04 still no luck. I check Gnome bug reports, they
are asking to talk to the distro.  Thanks.

** Attachment added: "Screenshot from 2023-02-01 17-39-43.png"
   
https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1971538/+attachment/5644283/+files/Screenshot%20from%202023-02-01%2017-39-43.png

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to network-manager in Ubuntu.
https://bugs.launchpad.net/bugs/1971538

Title:
  My machine has Wi-Fi Hotspot broken after upgrade to 22.04

Status in network-manager package in Ubuntu:
  Confirmed

Bug description:
  * Impact
  The hotspot feature fails to forward the data to the clients

  * Test case
  - log into an Ubuntu or GNOME session
  - connect the machine to an eth cable for internet
  - go to gnome-control-center -> wifi
  - enable the hotspot from the menu in the headerbar
  - connect another device to the wifi created
  -> the client should connect and access to internet work correctly

  Upon updating to 22.04, none of my machines can use the connection.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1971538/+subscriptions


-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp

[Touch-packages] [Bug 1951491] Re: Can't run snaps: .slice/session-1.scope is not a snap cgroup

[Leonardo Camilo]

unfortunately my problem still lingers.


Though for some reason, it only affects users with a non-standard $HOME 
location. 

For instance, I have created a few users on the directory
/storage/home/  and voilà the problem shows up whenever I try to
run a snap.

The problem does not affect users with the home directory at
/home/


Does anyone know how I can address this?

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to systemd in Ubuntu.
https://bugs.launchpad.net/bugs/1951491

Title:
  Can't run snaps: .slice/session-1.scope is not a snap cgroup

Status in X2Go:
  New
Status in Xpra Terminal Server:
  New
Status in snapd package in Ubuntu:
  Confirmed
Status in systemd package in Ubuntu:
  Incomplete
Status in x2goserver package in Ubuntu:
  Confirmed
Status in snapd package in Debian:
  New
Status in snapd package in Fedora:
  New

Bug description:
  I just upgraded from hirsute to impish using do-release-upgrade. On
  the upgraded system, I can't run either firefox or chromium (both of
  which worked fine under hirsute). Both fail with:

  /user.slice/user-NNN.slice/session-1.scope is not a snap cgroup where
  NNN is my uid

  With firefox, I was able to fix the problem with:

  snap remove --purge firefox
  apt purge firefox
  apt install firefox

  Now firefox works. But I tried the same thing substituting chromium-
  browser for firefox, and it didn't help: chromium fails with the same
  error message.

  I guess there must be something left over from the hirsute version of
  snapd that isn't getting noticed or cleared by the impish version?

  Someone suggested this might be related to bug 1850667, but that bug
  is marked fixed as of a couple months ago, and I just did this upgrade
  today. Also, it doesn't mention the error message I'm seeing.

  ProblemType: Bug
  DistroRelease: Ubuntu 21.10
  Package: snapd 2.53+21.10ubuntu1
  ProcVersionSignature: Ubuntu 5.13.0-21.21-generic 5.13.18
  Uname: Linux 5.13.0-21-generic x86_64
  ApportVersion: 2.20.11-0ubuntu71
  Architecture: amd64
  CasperMD5CheckResult: unknown
  Date: Thu Nov 18 18:12:45 2021
  InstallationDate: Installed on 2020-04-29 (568 days ago)
  InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423)
  SourcePackage: snapd
  UpgradeStatus: Upgraded to impish on 2021-11-18 (0 days ago)

To manage notifications about this bug go to:
https://bugs.launchpad.net/x2go/+bug/1951491/+subscriptions


-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp

[Touch-packages] [Bug 1991606] Re: Invalid PEP440 package version breaking setuptools >= 60

[Benjamin Drung]

Uploaded distro-info 1.4, python-debian 0.1.49ubuntu2, reportbug
11.6.0ubuntu2, duecredit 0.9.1-1ubuntu1, and ubuntu-dev-tools 0.192 to
fix the bug in lunar. I am working on devscripts now.  drslib is broken
upsteam and should be fixed there first.

** Changed in: ubuntu-dev-tools (Ubuntu)
   Status: New => Fix Committed

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to python-debian in Ubuntu.
https://bugs.launchpad.net/bugs/1991606

Title:
  Invalid PEP440 package version breaking setuptools >= 60

Status in devscripts package in Ubuntu:
  New
Status in distro-info package in Ubuntu:
  Fix Released
Status in drslib package in Ubuntu:
  New
Status in duecredit package in Ubuntu:
  Fix Committed
Status in python-debian package in Ubuntu:
  Fix Committed
Status in reportbug package in Ubuntu:
  Fix Committed
Status in ubuntu-dev-tools package in Ubuntu:
  Fix Committed
Status in devscripts source package in Bionic:
  New
Status in distro-info source package in Bionic:
  New
Status in drslib source package in Bionic:
  Invalid
Status in duecredit source package in Bionic:
  New
Status in python-debian source package in Bionic:
  Invalid
Status in reportbug source package in Bionic:
  New
Status in ubuntu-dev-tools source package in Bionic:
  New
Status in devscripts source package in Focal:
  New
Status in distro-info source package in Focal:
  New
Status in drslib source package in Focal:
  New
Status in duecredit source package in Focal:
  New
Status in python-debian source package in Focal:
  New
Status in reportbug source package in Focal:
  New
Status in ubuntu-dev-tools source package in Focal:
  New
Status in devscripts source package in Jammy:
  New
Status in distro-info source package in Jammy:
  New
Status in drslib source package in Jammy:
  New
Status in duecredit source package in Jammy:
  New
Status in python-debian source package in Jammy:
  New
Status in reportbug source package in Jammy:
  New
Status in ubuntu-dev-tools source package in Jammy:
  Invalid
Status in devscripts source package in Kinetic:
  New
Status in distro-info source package in Kinetic:
  New
Status in drslib source package in Kinetic:
  New
Status in duecredit source package in Kinetic:
  New
Status in python-debian source package in Kinetic:
  Invalid
Status in reportbug source package in Kinetic:
  New
Status in ubuntu-dev-tools source package in Kinetic:
  Invalid

Bug description:
  With setuptools 66, the versions of all packages visible in the Python
  environment *must* obey PEP440 .
  Otherwise, attempts to use pip to install a package with a setup.py-
  based build system, or other attempts to use the `pkg-resources`
  module, can produce errors like this:

    File 
"/builds/databiosphere/toil/venv/lib/python3.9/site-packages/pkg_resources/__init__.py",
 line 844, in _resolve_dist
  env = Environment(self.entries)
    File 
"/builds/databiosphere/toil/venv/lib/python3.9/site-packages/pkg_resources/__init__.py",
 line 1044, in __init__
  self.scan(search_path)
    File 
"/builds/databiosphere/toil/venv/lib/python3.9/site-packages/pkg_resources/__init__.py",
 line 1077, in scan
  self.add(dist)
    File 
"/builds/databiosphere/toil/venv/lib/python3.9/site-packages/pkg_resources/__init__.py",
 line 1096, in add
  dists.sort(key=operator.attrgetter('hashcmp'), reverse=True)
    File 
"/builds/databiosphere/toil/venv/lib/python3.9/site-packages/pkg_resources/__init__.py",
 line 2631, in hashcmp
  self.parsed_version,
    File 
"/builds/databiosphere/toil/venv/lib/python3.9/site-packages/pkg_resources/__init__.py",
 line 2678, in parsed_version
  self._parsed_version = parse_version(self.version)
    File 
"/builds/databiosphere/toil/venv/lib/python3.9/site-packages/pkg_resources/_vendor/packaging/version.py",
 line 266, in __init__
  raise InvalidVersion(f"Invalid version: '{version}'")
  pkg_resources.extern.packaging.version.InvalidVersion: Invalid version: 
'0.23ubuntu1'

  The official opinion of the setuptools maintainers seems to be that
  version strings of this form haven't *really* been allowed since about
  2014, and distributions need to change their package version naming
  scheme for Python packages they install, so that the resulting version
  strings obey PEP440. See for example
  .

  suffix 1build1 is invalid.

  Some python building tools, that verifies if version strings are
  compatible with PEP440, are failing.

  Example: python poetry: Invalid PEP 440 version: '1.1build1'

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/devscripts/+bug/1991606/+subscriptions


-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : 

[Touch-packages] [Bug 1991606] Re: Invalid PEP440 package version breaking setuptools >= 60

[Martin Pecka]

Ah, now I get it, thanks.

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to python-debian in Ubuntu.
https://bugs.launchpad.net/bugs/1991606

Title:
  Invalid PEP440 package version breaking setuptools >= 60

Status in devscripts package in Ubuntu:
  New
Status in distro-info package in Ubuntu:
  Fix Released
Status in drslib package in Ubuntu:
  New
Status in duecredit package in Ubuntu:
  Fix Committed
Status in python-debian package in Ubuntu:
  Fix Committed
Status in reportbug package in Ubuntu:
  Fix Committed
Status in ubuntu-dev-tools package in Ubuntu:
  Fix Committed
Status in devscripts source package in Bionic:
  New
Status in distro-info source package in Bionic:
  New
Status in drslib source package in Bionic:
  Invalid
Status in duecredit source package in Bionic:
  New
Status in python-debian source package in Bionic:
  Invalid
Status in reportbug source package in Bionic:
  New
Status in ubuntu-dev-tools source package in Bionic:
  New
Status in devscripts source package in Focal:
  New
Status in distro-info source package in Focal:
  New
Status in drslib source package in Focal:
  New
Status in duecredit source package in Focal:
  New
Status in python-debian source package in Focal:
  New
Status in reportbug source package in Focal:
  New
Status in ubuntu-dev-tools source package in Focal:
  New
Status in devscripts source package in Jammy:
  New
Status in distro-info source package in Jammy:
  New
Status in drslib source package in Jammy:
  New
Status in duecredit source package in Jammy:
  New
Status in python-debian source package in Jammy:
  New
Status in reportbug source package in Jammy:
  New
Status in ubuntu-dev-tools source package in Jammy:
  Invalid
Status in devscripts source package in Kinetic:
  New
Status in distro-info source package in Kinetic:
  New
Status in drslib source package in Kinetic:
  New
Status in duecredit source package in Kinetic:
  New
Status in python-debian source package in Kinetic:
  Invalid
Status in reportbug source package in Kinetic:
  New
Status in ubuntu-dev-tools source package in Kinetic:
  Invalid

Bug description:
  With setuptools 66, the versions of all packages visible in the Python
  environment *must* obey PEP440 .
  Otherwise, attempts to use pip to install a package with a setup.py-
  based build system, or other attempts to use the `pkg-resources`
  module, can produce errors like this:

    File 
"/builds/databiosphere/toil/venv/lib/python3.9/site-packages/pkg_resources/__init__.py",
 line 844, in _resolve_dist
  env = Environment(self.entries)
    File 
"/builds/databiosphere/toil/venv/lib/python3.9/site-packages/pkg_resources/__init__.py",
 line 1044, in __init__
  self.scan(search_path)
    File 
"/builds/databiosphere/toil/venv/lib/python3.9/site-packages/pkg_resources/__init__.py",
 line 1077, in scan
  self.add(dist)
    File 
"/builds/databiosphere/toil/venv/lib/python3.9/site-packages/pkg_resources/__init__.py",
 line 1096, in add
  dists.sort(key=operator.attrgetter('hashcmp'), reverse=True)
    File 
"/builds/databiosphere/toil/venv/lib/python3.9/site-packages/pkg_resources/__init__.py",
 line 2631, in hashcmp
  self.parsed_version,
    File 
"/builds/databiosphere/toil/venv/lib/python3.9/site-packages/pkg_resources/__init__.py",
 line 2678, in parsed_version
  self._parsed_version = parse_version(self.version)
    File 
"/builds/databiosphere/toil/venv/lib/python3.9/site-packages/pkg_resources/_vendor/packaging/version.py",
 line 266, in __init__
  raise InvalidVersion(f"Invalid version: '{version}'")
  pkg_resources.extern.packaging.version.InvalidVersion: Invalid version: 
'0.23ubuntu1'

  The official opinion of the setuptools maintainers seems to be that
  version strings of this form haven't *really* been allowed since about
  2014, and distributions need to change their package version naming
  scheme for Python packages they install, so that the resulting version
  strings obey PEP440. See for example
  .

  suffix 1build1 is invalid.

  Some python building tools, that verifies if version strings are
  compatible with PEP440, are failing.

  Example: python poetry: Invalid PEP 440 version: '1.1build1'

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/devscripts/+bug/1991606/+subscriptions


-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp

[Touch-packages] [Bug 1991606] Re: Invalid PEP440 package version breaking setuptools >= 60

[Benjamin Drung]

python-debian 0.1.32 in bionic is fine. Therefore I marked it invalid
for *python-debian* in bionic. distro-info 0.18ubuntu0.18.04.1 in bionic
needs to be fixed though.

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to python-debian in Ubuntu.
https://bugs.launchpad.net/bugs/1991606

Title:
  Invalid PEP440 package version breaking setuptools >= 60

Status in devscripts package in Ubuntu:
  New
Status in distro-info package in Ubuntu:
  Fix Released
Status in drslib package in Ubuntu:
  New
Status in duecredit package in Ubuntu:
  Fix Committed
Status in python-debian package in Ubuntu:
  Fix Committed
Status in reportbug package in Ubuntu:
  Fix Committed
Status in ubuntu-dev-tools package in Ubuntu:
  New
Status in devscripts source package in Bionic:
  New
Status in distro-info source package in Bionic:
  New
Status in drslib source package in Bionic:
  Invalid
Status in duecredit source package in Bionic:
  New
Status in python-debian source package in Bionic:
  Invalid
Status in reportbug source package in Bionic:
  New
Status in ubuntu-dev-tools source package in Bionic:
  New
Status in devscripts source package in Focal:
  New
Status in distro-info source package in Focal:
  New
Status in drslib source package in Focal:
  New
Status in duecredit source package in Focal:
  New
Status in python-debian source package in Focal:
  New
Status in reportbug source package in Focal:
  New
Status in ubuntu-dev-tools source package in Focal:
  New
Status in devscripts source package in Jammy:
  New
Status in distro-info source package in Jammy:
  New
Status in drslib source package in Jammy:
  New
Status in duecredit source package in Jammy:
  New
Status in python-debian source package in Jammy:
  New
Status in reportbug source package in Jammy:
  New
Status in ubuntu-dev-tools source package in Jammy:
  Invalid
Status in devscripts source package in Kinetic:
  New
Status in distro-info source package in Kinetic:
  New
Status in drslib source package in Kinetic:
  New
Status in duecredit source package in Kinetic:
  New
Status in python-debian source package in Kinetic:
  Invalid
Status in reportbug source package in Kinetic:
  New
Status in ubuntu-dev-tools source package in Kinetic:
  Invalid

Bug description:
  With setuptools 66, the versions of all packages visible in the Python
  environment *must* obey PEP440 .
  Otherwise, attempts to use pip to install a package with a setup.py-
  based build system, or other attempts to use the `pkg-resources`
  module, can produce errors like this:

    File 
"/builds/databiosphere/toil/venv/lib/python3.9/site-packages/pkg_resources/__init__.py",
 line 844, in _resolve_dist
  env = Environment(self.entries)
    File 
"/builds/databiosphere/toil/venv/lib/python3.9/site-packages/pkg_resources/__init__.py",
 line 1044, in __init__
  self.scan(search_path)
    File 
"/builds/databiosphere/toil/venv/lib/python3.9/site-packages/pkg_resources/__init__.py",
 line 1077, in scan
  self.add(dist)
    File 
"/builds/databiosphere/toil/venv/lib/python3.9/site-packages/pkg_resources/__init__.py",
 line 1096, in add
  dists.sort(key=operator.attrgetter('hashcmp'), reverse=True)
    File 
"/builds/databiosphere/toil/venv/lib/python3.9/site-packages/pkg_resources/__init__.py",
 line 2631, in hashcmp
  self.parsed_version,
    File 
"/builds/databiosphere/toil/venv/lib/python3.9/site-packages/pkg_resources/__init__.py",
 line 2678, in parsed_version
  self._parsed_version = parse_version(self.version)
    File 
"/builds/databiosphere/toil/venv/lib/python3.9/site-packages/pkg_resources/_vendor/packaging/version.py",
 line 266, in __init__
  raise InvalidVersion(f"Invalid version: '{version}'")
  pkg_resources.extern.packaging.version.InvalidVersion: Invalid version: 
'0.23ubuntu1'

  The official opinion of the setuptools maintainers seems to be that
  version strings of this form haven't *really* been allowed since about
  2014, and distributions need to change their package version naming
  scheme for Python packages they install, so that the resulting version
  strings obey PEP440. See for example
  .

  suffix 1build1 is invalid.

  Some python building tools, that verifies if version strings are
  compatible with PEP440, are failing.

  Example: python poetry: Invalid PEP 440 version: '1.1build1'

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/devscripts/+bug/1991606/+subscriptions


-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp

[Touch-packages] [Bug 1991606] Re: Invalid PEP440 package version breaking setuptools >= 60

[Martin Pecka]

> Changed in python-debian (Ubuntu Bionic):
> status:   New → Invalid 

Can I ask about this change? How is it invalid for bionic? The name of
the package is wrong there, too... (for both python-distro-info an
python3-distro-info).

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to python-debian in Ubuntu.
https://bugs.launchpad.net/bugs/1991606

Title:
  Invalid PEP440 package version breaking setuptools >= 60

Status in devscripts package in Ubuntu:
  New
Status in distro-info package in Ubuntu:
  Fix Released
Status in drslib package in Ubuntu:
  New
Status in duecredit package in Ubuntu:
  Fix Committed
Status in python-debian package in Ubuntu:
  Fix Committed
Status in reportbug package in Ubuntu:
  Fix Committed
Status in ubuntu-dev-tools package in Ubuntu:
  New
Status in devscripts source package in Bionic:
  New
Status in distro-info source package in Bionic:
  New
Status in drslib source package in Bionic:
  Invalid
Status in duecredit source package in Bionic:
  New
Status in python-debian source package in Bionic:
  Invalid
Status in reportbug source package in Bionic:
  New
Status in ubuntu-dev-tools source package in Bionic:
  New
Status in devscripts source package in Focal:
  New
Status in distro-info source package in Focal:
  New
Status in drslib source package in Focal:
  New
Status in duecredit source package in Focal:
  New
Status in python-debian source package in Focal:
  New
Status in reportbug source package in Focal:
  New
Status in ubuntu-dev-tools source package in Focal:
  New
Status in devscripts source package in Jammy:
  New
Status in distro-info source package in Jammy:
  New
Status in drslib source package in Jammy:
  New
Status in duecredit source package in Jammy:
  New
Status in python-debian source package in Jammy:
  New
Status in reportbug source package in Jammy:
  New
Status in ubuntu-dev-tools source package in Jammy:
  Invalid
Status in devscripts source package in Kinetic:
  New
Status in distro-info source package in Kinetic:
  New
Status in drslib source package in Kinetic:
  New
Status in duecredit source package in Kinetic:
  New
Status in python-debian source package in Kinetic:
  Invalid
Status in reportbug source package in Kinetic:
  New
Status in ubuntu-dev-tools source package in Kinetic:
  Invalid

Bug description:
  With setuptools 66, the versions of all packages visible in the Python
  environment *must* obey PEP440 .
  Otherwise, attempts to use pip to install a package with a setup.py-
  based build system, or other attempts to use the `pkg-resources`
  module, can produce errors like this:

    File 
"/builds/databiosphere/toil/venv/lib/python3.9/site-packages/pkg_resources/__init__.py",
 line 844, in _resolve_dist
  env = Environment(self.entries)
    File 
"/builds/databiosphere/toil/venv/lib/python3.9/site-packages/pkg_resources/__init__.py",
 line 1044, in __init__
  self.scan(search_path)
    File 
"/builds/databiosphere/toil/venv/lib/python3.9/site-packages/pkg_resources/__init__.py",
 line 1077, in scan
  self.add(dist)
    File 
"/builds/databiosphere/toil/venv/lib/python3.9/site-packages/pkg_resources/__init__.py",
 line 1096, in add
  dists.sort(key=operator.attrgetter('hashcmp'), reverse=True)
    File 
"/builds/databiosphere/toil/venv/lib/python3.9/site-packages/pkg_resources/__init__.py",
 line 2631, in hashcmp
  self.parsed_version,
    File 
"/builds/databiosphere/toil/venv/lib/python3.9/site-packages/pkg_resources/__init__.py",
 line 2678, in parsed_version
  self._parsed_version = parse_version(self.version)
    File 
"/builds/databiosphere/toil/venv/lib/python3.9/site-packages/pkg_resources/_vendor/packaging/version.py",
 line 266, in __init__
  raise InvalidVersion(f"Invalid version: '{version}'")
  pkg_resources.extern.packaging.version.InvalidVersion: Invalid version: 
'0.23ubuntu1'

  The official opinion of the setuptools maintainers seems to be that
  version strings of this form haven't *really* been allowed since about
  2014, and distributions need to change their package version naming
  scheme for Python packages they install, so that the resulting version
  strings obey PEP440. See for example
  .

  suffix 1build1 is invalid.

  Some python building tools, that verifies if version strings are
  compatible with PEP440, are failing.

  Example: python poetry: Invalid PEP 440 version: '1.1build1'

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/devscripts/+bug/1991606/+subscriptions


-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp

[Touch-packages] [Bug 1991606] Re: Invalid PEP440 package version breaking setuptools >= 60

[Benjamin Drung]

** Changed in: duecredit (Ubuntu)
   Status: New => Fix Committed

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to python-debian in Ubuntu.
https://bugs.launchpad.net/bugs/1991606

Title:
  Invalid PEP440 package version breaking setuptools >= 60

Status in devscripts package in Ubuntu:
  New
Status in distro-info package in Ubuntu:
  Fix Released
Status in drslib package in Ubuntu:
  New
Status in duecredit package in Ubuntu:
  Fix Committed
Status in python-debian package in Ubuntu:
  Fix Committed
Status in reportbug package in Ubuntu:
  Fix Committed
Status in ubuntu-dev-tools package in Ubuntu:
  New
Status in devscripts source package in Bionic:
  New
Status in distro-info source package in Bionic:
  New
Status in drslib source package in Bionic:
  Invalid
Status in duecredit source package in Bionic:
  New
Status in python-debian source package in Bionic:
  Invalid
Status in reportbug source package in Bionic:
  New
Status in ubuntu-dev-tools source package in Bionic:
  New
Status in devscripts source package in Focal:
  New
Status in distro-info source package in Focal:
  New
Status in drslib source package in Focal:
  New
Status in duecredit source package in Focal:
  New
Status in python-debian source package in Focal:
  New
Status in reportbug source package in Focal:
  New
Status in ubuntu-dev-tools source package in Focal:
  New
Status in devscripts source package in Jammy:
  New
Status in distro-info source package in Jammy:
  New
Status in drslib source package in Jammy:
  New
Status in duecredit source package in Jammy:
  New
Status in python-debian source package in Jammy:
  New
Status in reportbug source package in Jammy:
  New
Status in ubuntu-dev-tools source package in Jammy:
  Invalid
Status in devscripts source package in Kinetic:
  New
Status in distro-info source package in Kinetic:
  New
Status in drslib source package in Kinetic:
  New
Status in duecredit source package in Kinetic:
  New
Status in python-debian source package in Kinetic:
  Invalid
Status in reportbug source package in Kinetic:
  New
Status in ubuntu-dev-tools source package in Kinetic:
  Invalid

Bug description:
  With setuptools 66, the versions of all packages visible in the Python
  environment *must* obey PEP440 .
  Otherwise, attempts to use pip to install a package with a setup.py-
  based build system, or other attempts to use the `pkg-resources`
  module, can produce errors like this:

    File 
"/builds/databiosphere/toil/venv/lib/python3.9/site-packages/pkg_resources/__init__.py",
 line 844, in _resolve_dist
  env = Environment(self.entries)
    File 
"/builds/databiosphere/toil/venv/lib/python3.9/site-packages/pkg_resources/__init__.py",
 line 1044, in __init__
  self.scan(search_path)
    File 
"/builds/databiosphere/toil/venv/lib/python3.9/site-packages/pkg_resources/__init__.py",
 line 1077, in scan
  self.add(dist)
    File 
"/builds/databiosphere/toil/venv/lib/python3.9/site-packages/pkg_resources/__init__.py",
 line 1096, in add
  dists.sort(key=operator.attrgetter('hashcmp'), reverse=True)
    File 
"/builds/databiosphere/toil/venv/lib/python3.9/site-packages/pkg_resources/__init__.py",
 line 2631, in hashcmp
  self.parsed_version,
    File 
"/builds/databiosphere/toil/venv/lib/python3.9/site-packages/pkg_resources/__init__.py",
 line 2678, in parsed_version
  self._parsed_version = parse_version(self.version)
    File 
"/builds/databiosphere/toil/venv/lib/python3.9/site-packages/pkg_resources/_vendor/packaging/version.py",
 line 266, in __init__
  raise InvalidVersion(f"Invalid version: '{version}'")
  pkg_resources.extern.packaging.version.InvalidVersion: Invalid version: 
'0.23ubuntu1'

  The official opinion of the setuptools maintainers seems to be that
  version strings of this form haven't *really* been allowed since about
  2014, and distributions need to change their package version naming
  scheme for Python packages they install, so that the resulting version
  strings obey PEP440. See for example
  .

  suffix 1build1 is invalid.

  Some python building tools, that verifies if version strings are
  compatible with PEP440, are failing.

  Example: python poetry: Invalid PEP 440 version: '1.1build1'

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/devscripts/+bug/1991606/+subscriptions


-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp

[Touch-packages] [Bug 1991606] Re: Invalid PEP440 package version breaking setuptools >= 60

[Benjamin Drung]

** Changed in: python-debian (Ubuntu)
   Status: New => Fix Committed

** Changed in: reportbug (Ubuntu)
   Status: New => Fix Committed

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to python-debian in Ubuntu.
https://bugs.launchpad.net/bugs/1991606

Title:
  Invalid PEP440 package version breaking setuptools >= 60

Status in devscripts package in Ubuntu:
  New
Status in distro-info package in Ubuntu:
  Fix Released
Status in drslib package in Ubuntu:
  New
Status in duecredit package in Ubuntu:
  New
Status in python-debian package in Ubuntu:
  Fix Committed
Status in reportbug package in Ubuntu:
  Fix Committed
Status in ubuntu-dev-tools package in Ubuntu:
  New
Status in devscripts source package in Bionic:
  New
Status in distro-info source package in Bionic:
  New
Status in drslib source package in Bionic:
  Invalid
Status in duecredit source package in Bionic:
  New
Status in python-debian source package in Bionic:
  Invalid
Status in reportbug source package in Bionic:
  New
Status in ubuntu-dev-tools source package in Bionic:
  New
Status in devscripts source package in Focal:
  New
Status in distro-info source package in Focal:
  New
Status in drslib source package in Focal:
  New
Status in duecredit source package in Focal:
  New
Status in python-debian source package in Focal:
  New
Status in reportbug source package in Focal:
  New
Status in ubuntu-dev-tools source package in Focal:
  New
Status in devscripts source package in Jammy:
  New
Status in distro-info source package in Jammy:
  New
Status in drslib source package in Jammy:
  New
Status in duecredit source package in Jammy:
  New
Status in python-debian source package in Jammy:
  New
Status in reportbug source package in Jammy:
  New
Status in ubuntu-dev-tools source package in Jammy:
  Invalid
Status in devscripts source package in Kinetic:
  New
Status in distro-info source package in Kinetic:
  New
Status in drslib source package in Kinetic:
  New
Status in duecredit source package in Kinetic:
  New
Status in python-debian source package in Kinetic:
  Invalid
Status in reportbug source package in Kinetic:
  New
Status in ubuntu-dev-tools source package in Kinetic:
  Invalid

Bug description:
  With setuptools 66, the versions of all packages visible in the Python
  environment *must* obey PEP440 .
  Otherwise, attempts to use pip to install a package with a setup.py-
  based build system, or other attempts to use the `pkg-resources`
  module, can produce errors like this:

    File 
"/builds/databiosphere/toil/venv/lib/python3.9/site-packages/pkg_resources/__init__.py",
 line 844, in _resolve_dist
  env = Environment(self.entries)
    File 
"/builds/databiosphere/toil/venv/lib/python3.9/site-packages/pkg_resources/__init__.py",
 line 1044, in __init__
  self.scan(search_path)
    File 
"/builds/databiosphere/toil/venv/lib/python3.9/site-packages/pkg_resources/__init__.py",
 line 1077, in scan
  self.add(dist)
    File 
"/builds/databiosphere/toil/venv/lib/python3.9/site-packages/pkg_resources/__init__.py",
 line 1096, in add
  dists.sort(key=operator.attrgetter('hashcmp'), reverse=True)
    File 
"/builds/databiosphere/toil/venv/lib/python3.9/site-packages/pkg_resources/__init__.py",
 line 2631, in hashcmp
  self.parsed_version,
    File 
"/builds/databiosphere/toil/venv/lib/python3.9/site-packages/pkg_resources/__init__.py",
 line 2678, in parsed_version
  self._parsed_version = parse_version(self.version)
    File 
"/builds/databiosphere/toil/venv/lib/python3.9/site-packages/pkg_resources/_vendor/packaging/version.py",
 line 266, in __init__
  raise InvalidVersion(f"Invalid version: '{version}'")
  pkg_resources.extern.packaging.version.InvalidVersion: Invalid version: 
'0.23ubuntu1'

  The official opinion of the setuptools maintainers seems to be that
  version strings of this form haven't *really* been allowed since about
  2014, and distributions need to change their package version naming
  scheme for Python packages they install, so that the resulting version
  strings obey PEP440. See for example
  .

  suffix 1build1 is invalid.

  Some python building tools, that verifies if version strings are
  compatible with PEP440, are failing.

  Example: python poetry: Invalid PEP 440 version: '1.1build1'

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/devscripts/+bug/1991606/+subscriptions


-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp

[Touch-packages] [Bug 1991606] Re: Invalid PEP440 package version breaking setuptools >= 60

[Benjamin Drung]

** Changed in: distro-info (Ubuntu)
   Importance: Medium => High

** Changed in: devscripts (Ubuntu)
   Importance: Undecided => High

** Changed in: drslib (Ubuntu Bionic)
   Status: New => Invalid

** Changed in: python-debian (Ubuntu Kinetic)
   Status: New => Invalid

** Changed in: python-debian (Ubuntu Bionic)
   Status: New => Invalid

** Changed in: python-debian (Ubuntu)
   Importance: Undecided => High

** Changed in: duecredit (Ubuntu)
   Importance: Undecided => High

** Changed in: drslib (Ubuntu)
   Importance: Undecided => High

** Changed in: reportbug (Ubuntu)
   Importance: Undecided => High

** Changed in: ubuntu-dev-tools (Ubuntu)
   Importance: Undecided => High

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to python-debian in Ubuntu.
https://bugs.launchpad.net/bugs/1991606

Title:
  Invalid PEP440 package version breaking setuptools >= 60

Status in devscripts package in Ubuntu:
  New
Status in distro-info package in Ubuntu:
  Fix Released
Status in drslib package in Ubuntu:
  New
Status in duecredit package in Ubuntu:
  New
Status in python-debian package in Ubuntu:
  New
Status in reportbug package in Ubuntu:
  New
Status in ubuntu-dev-tools package in Ubuntu:
  New
Status in devscripts source package in Bionic:
  New
Status in distro-info source package in Bionic:
  New
Status in drslib source package in Bionic:
  Invalid
Status in duecredit source package in Bionic:
  New
Status in python-debian source package in Bionic:
  Invalid
Status in reportbug source package in Bionic:
  New
Status in ubuntu-dev-tools source package in Bionic:
  New
Status in devscripts source package in Focal:
  New
Status in distro-info source package in Focal:
  New
Status in drslib source package in Focal:
  New
Status in duecredit source package in Focal:
  New
Status in python-debian source package in Focal:
  New
Status in reportbug source package in Focal:
  New
Status in ubuntu-dev-tools source package in Focal:
  New
Status in devscripts source package in Jammy:
  New
Status in distro-info source package in Jammy:
  New
Status in drslib source package in Jammy:
  New
Status in duecredit source package in Jammy:
  New
Status in python-debian source package in Jammy:
  New
Status in reportbug source package in Jammy:
  New
Status in ubuntu-dev-tools source package in Jammy:
  Invalid
Status in devscripts source package in Kinetic:
  New
Status in distro-info source package in Kinetic:
  New
Status in drslib source package in Kinetic:
  New
Status in duecredit source package in Kinetic:
  New
Status in python-debian source package in Kinetic:
  Invalid
Status in reportbug source package in Kinetic:
  New
Status in ubuntu-dev-tools source package in Kinetic:
  Invalid

Bug description:
  With setuptools 66, the versions of all packages visible in the Python
  environment *must* obey PEP440 .
  Otherwise, attempts to use pip to install a package with a setup.py-
  based build system, or other attempts to use the `pkg-resources`
  module, can produce errors like this:

    File 
"/builds/databiosphere/toil/venv/lib/python3.9/site-packages/pkg_resources/__init__.py",
 line 844, in _resolve_dist
  env = Environment(self.entries)
    File 
"/builds/databiosphere/toil/venv/lib/python3.9/site-packages/pkg_resources/__init__.py",
 line 1044, in __init__
  self.scan(search_path)
    File 
"/builds/databiosphere/toil/venv/lib/python3.9/site-packages/pkg_resources/__init__.py",
 line 1077, in scan
  self.add(dist)
    File 
"/builds/databiosphere/toil/venv/lib/python3.9/site-packages/pkg_resources/__init__.py",
 line 1096, in add
  dists.sort(key=operator.attrgetter('hashcmp'), reverse=True)
    File 
"/builds/databiosphere/toil/venv/lib/python3.9/site-packages/pkg_resources/__init__.py",
 line 2631, in hashcmp
  self.parsed_version,
    File 
"/builds/databiosphere/toil/venv/lib/python3.9/site-packages/pkg_resources/__init__.py",
 line 2678, in parsed_version
  self._parsed_version = parse_version(self.version)
    File 
"/builds/databiosphere/toil/venv/lib/python3.9/site-packages/pkg_resources/_vendor/packaging/version.py",
 line 266, in __init__
  raise InvalidVersion(f"Invalid version: '{version}'")
  pkg_resources.extern.packaging.version.InvalidVersion: Invalid version: 
'0.23ubuntu1'

  The official opinion of the setuptools maintainers seems to be that
  version strings of this form haven't *really* been allowed since about
  2014, and distributions need to change their package version naming
  scheme for Python packages they install, so that the resulting version
  strings obey PEP440. See for example
  .

  suffix 1build1 is invalid.

  Some python building tools, that verifies if version strings are
  compatible with PEP440, are failing.

  Example: python poetry: Invalid PEP 440 

[Touch-packages] [Bug 2004245] Re: /usr/bin/software-properties-gtk:AttributeError:on_radio_toggled:update_state

[Nathan Teodosio]

** Changed in: software-properties (Ubuntu)
   Status: Triaged => Fix Committed

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to software-properties in
Ubuntu.
https://bugs.launchpad.net/bugs/2004245

Title:
  /usr/bin/software-properties-
  gtk:AttributeError:on_radio_toggled:update_state

Status in software-properties package in Ubuntu:
  Fix Committed

Bug description:
  The Ubuntu Error Tracker has been receiving reports about a problem regarding 
software-properties.  This problem was most recently seen with package version 
0.99.22.5, the problem page at 
https://errors.ubuntu.com/problem/0d4bb9d499df175309552a99a411e2909a88fab1 
contains more details, including versions of packages affected, stacktrace or 
traceback, and individual crash reports.
  If you do not have access to the Ubuntu Error Tracker and are a software 
developer, you can request it at http://forms.canonical.com/reports/.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/software-properties/+bug/2004245/+subscriptions


-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp

[Touch-packages] [Bug 2004459] Re: /usr/bin/software-properties-gtk:uaclient.exceptions.ConnectivityError:do_open:request:_send_request:endheaders:_send_output:send:connect:connect:create_connection:g

[Nathan Teodosio]

This is a re-spin of LP: #2003996.

Should be fixed once https://git.launchpad.net/software-
properties/commit/?id=684756fd2c9d606071a23dd97352cdf572b531f5 is
released.

** Description changed:

  The Ubuntu Error Tracker has been receiving reports about a problem regarding 
software-properties.  This problem was most recently seen with package version 
0.99.22.5, the problem page at 
https://errors.ubuntu.com/problem/52f13b0d1d5c75b8a964d28dbe58d616be9fa781 
contains more details, including versions of packages affected, stacktrace or 
traceback, and individual crash reports.
  If you do not have access to the Ubuntu Error Tracker and are a software 
developer, you can request it at http://forms.canonical.com/reports/.
+ 
+ Traceback (most recent call last):
+   File "/usr/lib/python3.10/urllib/request.py", line 1348, in do_open
+ h.request(req.get_method(), req.selector, req.data, headers,
+   File "/usr/lib/python3.10/http/client.py", line 1282, in request
+ self._send_request(method, url, body, headers, encode_chunked)
+   File "/usr/lib/python3.10/http/client.py", line 1328, in _send_request
+ self.endheaders(body, encode_chunked=encode_chunked)
+   File "/usr/lib/python3.10/http/client.py", line 1277, in endheaders
+ self._send_output(message_body, encode_chunked=encode_chunked)
+   File "/usr/lib/python3.10/http/client.py", line 1037, in _send_output
+ self.send(msg)
+   File "/usr/lib/python3.10/http/client.py", line 975, in send
+ self.connect()
+   File "/usr/lib/python3.10/http/client.py", line 1447, in connect
+ super().connect()
+   File "/usr/lib/python3.10/http/client.py", line 941, in connect
+ self.sock = self._create_connection(
+   File "/usr/lib/python3.10/socket.py", line 824, in create_connection
+ for res in getaddrinfo(host, port, 0, SOCK_STREAM):
+   File "/usr/lib/python3.10/socket.py", line 955, in getaddrinfo
+ for res in _socket.getaddrinfo(host, port, family, type, proto, flags):
+ socket.gaierror: [Errno -3] Temporary failure in name resolution
+ 
+ During handling of the above exception, another exception occurred:
+ 
+ Traceback (most recent call last):
+   File 
"/usr/lib/python3/dist-packages/softwareproperties/gtk/DialogUaAttach.py", line 
144, in poll_for_magic_token
+ response = wait(options)
+   File 
"/usr/lib/python3/dist-packages/uaclient/api/u/pro/attach/magic/wait/v1.py", 
line 57, in wait
+ return _wait(options, UAConfig())
+   File 
"/usr/lib/python3/dist-packages/uaclient/api/u/pro/attach/magic/wait/v1.py", 
line 93, in _wait
+ raise e
+   File 
"/usr/lib/python3/dist-packages/uaclient/api/u/pro/attach/magic/wait/v1.py", 
line 73, in _wait
+ wait_resp = contract.get_magic_attach_token_info(
+   File "/usr/lib/python3/dist-packages/uaclient/contract.py", line 214, in 
get_magic_attach_token_info
+ raise exceptions.ConnectivityError()
+ uaclient.exceptions.ConnectivityError

** Merge proposal linked:
   
https://code.launchpad.net/~nteodosio/software-properties/+git/software-properties/+merge/436428

** Changed in: software-properties (Ubuntu)
   Status: Confirmed => Fix Committed

** Changed in: software-properties (Ubuntu)
 Assignee: (unassigned) => Nathan Teodosio (nteodosio)

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to software-properties in
Ubuntu.
https://bugs.launchpad.net/bugs/2004459

Title:
  /usr/bin/software-properties-
  
gtk:uaclient.exceptions.ConnectivityError:do_open:request:_send_request:endheaders:_send_output:send:connect:connect:create_connection:getaddrinfo:request_url:readurl:urlopen:open:_open:_call_chain:https_open:do_open:get_magic_attach_token_info:request_url:poll_for_magic_token:wait:_wait:_wait:get_magic_attach_token_info

Status in software-properties package in Ubuntu:
  Fix Committed

Bug description:
  The Ubuntu Error Tracker has been receiving reports about a problem regarding 
software-properties.  This problem was most recently seen with package version 
0.99.22.5, the problem page at 
https://errors.ubuntu.com/problem/52f13b0d1d5c75b8a964d28dbe58d616be9fa781 
contains more details, including versions of packages affected, stacktrace or 
traceback, and individual crash reports.
  If you do not have access to the Ubuntu Error Tracker and are a software 
developer, you can request it at http://forms.canonical.com/reports/.

  Traceback (most recent call last):
File "/usr/lib/python3.10/urllib/request.py", line 1348, in do_open
  h.request(req.get_method(), req.selector, req.data, headers,
File "/usr/lib/python3.10/http/client.py", line 1282, in request
  self._send_request(method, url, body, headers, encode_chunked)
File "/usr/lib/python3.10/http/client.py", line 1328, in _send_request
  self.endheaders(body, encode_chunked=encode_chunked)
File "/usr/lib/python3.10/http/client.py", line 1277, in endheaders
  self._send_output(message_body, 

[Touch-packages] [Bug 2003996] Re: /usr/bin/software-properties-gtk:TimeoutError:poll_for_magic_token:wait:_wait:get_magic_attach_token_info:request_url:readurl:urlopen:open:_open:_call_chain:https_op

[Nathan Teodosio]

** Changed in: software-properties (Ubuntu)
   Status: In Progress => Fix Committed

** Description changed:

  The Ubuntu Error Tracker has been receiving reports about a problem regarding 
software-properties.  This problem was most recently seen with package version 
0.99.22.5, the problem page at 
https://errors.ubuntu.com/problem/032c1f3f3d9b9b05e5087f7e37a05a3d0d40e699 
contains more details, including versions of packages affected, stacktrace or 
traceback, and individual crash reports.
  If you do not have access to the Ubuntu Error Tracker and are a software 
developer, you can request it at http://forms.canonical.com/reports/.
+ 
+ Traceback (most recent call last):
+   File 
"/usr/lib/python3/dist-packages/softwareproperties/gtk/DialogUaAttach.py", line 
144, in poll_for_magic_token
+ response = wait(options)
+   File 
"/usr/lib/python3/dist-packages/uaclient/api/u/pro/attach/magic/wait/v1.py", 
line 57, in wait
+ return _wait(options, UAConfig())
+   File 
"/usr/lib/python3/dist-packages/uaclient/api/u/pro/attach/magic/wait/v1.py", 
line 73, in _wait
+ wait_resp = contract.get_magic_attach_token_info(
+   File "/usr/lib/python3/dist-packages/uaclient/contract.py", line 202, in 
get_magic_attach_token_info
+ response, _ = self.request_url(
+   File "/usr/lib/python3/dist-packages/uaclient/serviceclient.py", line 72, 
in request_url
+ response, headers = util.readurl(
+   File "/usr/lib/python3/dist-packages/uaclient/util.py", line 324, in readurl
+ resp = request.urlopen(req, timeout=timeout)
+   File "/usr/lib/python3.10/urllib/request.py", line 216, in urlopen
+ return opener.open(url, data, timeout)
+   File "/usr/lib/python3.10/urllib/request.py", line 519, in open
+ response = self._open(req, data)
+   File "/usr/lib/python3.10/urllib/request.py", line 536, in _open
+ result = self._call_chain(self.handle_open, protocol, protocol +
+   File "/usr/lib/python3.10/urllib/request.py", line 496, in _call_chain
+ result = func(*args)
+   File "/usr/lib/python3.10/urllib/request.py", line 1391, in https_open
+ return self.do_open(http.client.HTTPSConnection, req,
+   File "/usr/lib/python3.10/urllib/request.py", line 1352, in do_open
+ r = h.getresponse()
+   File "/usr/lib/python3.10/http/client.py", line 1374, in getresponse
+ response.begin()
+   File "/usr/lib/python3.10/http/client.py", line 318, in begin
+ version, status, reason = self._read_status()
+   File "/usr/lib/python3.10/http/client.py", line 279, in _read_status
+ line = str(self.fp.readline(_MAXLINE + 1), "iso-8859-1")
+   File "/usr/lib/python3.10/socket.py", line 705, in readinto
+ return self._sock.recv_into(b)
+   File "/usr/lib/python3.10/ssl.py", line 1274, in recv_into
+ return self.read(nbytes, buffer)
+   File "/usr/lib/python3.10/ssl.py", line 1130, in read
+ return self._sslobj.read(len, buffer)
+ TimeoutError: The read operation timed out

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to software-properties in
Ubuntu.
https://bugs.launchpad.net/bugs/2003996

Title:
  /usr/bin/software-properties-
  
gtk:TimeoutError:poll_for_magic_token:wait:_wait:get_magic_attach_token_info:request_url:readurl:urlopen:open:_open:_call_chain:https_open:do_open:getresponse:begin:_read_status:readinto:recv_into:read

Status in software-properties package in Ubuntu:
  Fix Committed

Bug description:
  The Ubuntu Error Tracker has been receiving reports about a problem regarding 
software-properties.  This problem was most recently seen with package version 
0.99.22.5, the problem page at 
https://errors.ubuntu.com/problem/032c1f3f3d9b9b05e5087f7e37a05a3d0d40e699 
contains more details, including versions of packages affected, stacktrace or 
traceback, and individual crash reports.
  If you do not have access to the Ubuntu Error Tracker and are a software 
developer, you can request it at http://forms.canonical.com/reports/.

  Traceback (most recent call last):
File 
"/usr/lib/python3/dist-packages/softwareproperties/gtk/DialogUaAttach.py", line 
144, in poll_for_magic_token
  response = wait(options)
File 
"/usr/lib/python3/dist-packages/uaclient/api/u/pro/attach/magic/wait/v1.py", 
line 57, in wait
  return _wait(options, UAConfig())
File 
"/usr/lib/python3/dist-packages/uaclient/api/u/pro/attach/magic/wait/v1.py", 
line 73, in _wait
  wait_resp = contract.get_magic_attach_token_info(
File "/usr/lib/python3/dist-packages/uaclient/contract.py", line 202, in 
get_magic_attach_token_info
  response, _ = self.request_url(
File "/usr/lib/python3/dist-packages/uaclient/serviceclient.py", line 72, 
in request_url
  response, headers = util.readurl(
File "/usr/lib/python3/dist-packages/uaclient/util.py", line 324, in readurl
  resp = request.urlopen(req, timeout=timeout)
File "/usr/lib/python3.10/urllib/request.py", line 216, in urlopen
  

[Touch-packages] [Bug 1991606] Re: Invalid PEP440 package version breaking setuptools >= 60

[Benjamin Drung]

** Tags added: regression-update

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to python-debian in Ubuntu.
https://bugs.launchpad.net/bugs/1991606

Title:
  Invalid PEP440 package version breaking setuptools >= 60

Status in devscripts package in Ubuntu:
  New
Status in distro-info package in Ubuntu:
  Fix Released
Status in drslib package in Ubuntu:
  New
Status in duecredit package in Ubuntu:
  New
Status in python-debian package in Ubuntu:
  New
Status in reportbug package in Ubuntu:
  New
Status in ubuntu-dev-tools package in Ubuntu:
  New
Status in devscripts source package in Bionic:
  New
Status in distro-info source package in Bionic:
  New
Status in drslib source package in Bionic:
  New
Status in duecredit source package in Bionic:
  New
Status in python-debian source package in Bionic:
  New
Status in reportbug source package in Bionic:
  New
Status in ubuntu-dev-tools source package in Bionic:
  New
Status in devscripts source package in Focal:
  New
Status in distro-info source package in Focal:
  New
Status in drslib source package in Focal:
  New
Status in duecredit source package in Focal:
  New
Status in python-debian source package in Focal:
  New
Status in reportbug source package in Focal:
  New
Status in ubuntu-dev-tools source package in Focal:
  New
Status in devscripts source package in Jammy:
  New
Status in distro-info source package in Jammy:
  New
Status in drslib source package in Jammy:
  New
Status in duecredit source package in Jammy:
  New
Status in python-debian source package in Jammy:
  New
Status in reportbug source package in Jammy:
  New
Status in ubuntu-dev-tools source package in Jammy:
  Invalid
Status in devscripts source package in Kinetic:
  New
Status in distro-info source package in Kinetic:
  New
Status in drslib source package in Kinetic:
  New
Status in duecredit source package in Kinetic:
  New
Status in python-debian source package in Kinetic:
  New
Status in reportbug source package in Kinetic:
  New
Status in ubuntu-dev-tools source package in Kinetic:
  Invalid

Bug description:
  With setuptools 66, the versions of all packages visible in the Python
  environment *must* obey PEP440 .
  Otherwise, attempts to use pip to install a package with a setup.py-
  based build system, or other attempts to use the `pkg-resources`
  module, can produce errors like this:

    File 
"/builds/databiosphere/toil/venv/lib/python3.9/site-packages/pkg_resources/__init__.py",
 line 844, in _resolve_dist
  env = Environment(self.entries)
    File 
"/builds/databiosphere/toil/venv/lib/python3.9/site-packages/pkg_resources/__init__.py",
 line 1044, in __init__
  self.scan(search_path)
    File 
"/builds/databiosphere/toil/venv/lib/python3.9/site-packages/pkg_resources/__init__.py",
 line 1077, in scan
  self.add(dist)
    File 
"/builds/databiosphere/toil/venv/lib/python3.9/site-packages/pkg_resources/__init__.py",
 line 1096, in add
  dists.sort(key=operator.attrgetter('hashcmp'), reverse=True)
    File 
"/builds/databiosphere/toil/venv/lib/python3.9/site-packages/pkg_resources/__init__.py",
 line 2631, in hashcmp
  self.parsed_version,
    File 
"/builds/databiosphere/toil/venv/lib/python3.9/site-packages/pkg_resources/__init__.py",
 line 2678, in parsed_version
  self._parsed_version = parse_version(self.version)
    File 
"/builds/databiosphere/toil/venv/lib/python3.9/site-packages/pkg_resources/_vendor/packaging/version.py",
 line 266, in __init__
  raise InvalidVersion(f"Invalid version: '{version}'")
  pkg_resources.extern.packaging.version.InvalidVersion: Invalid version: 
'0.23ubuntu1'

  The official opinion of the setuptools maintainers seems to be that
  version strings of this form haven't *really* been allowed since about
  2014, and distributions need to change their package version naming
  scheme for Python packages they install, so that the resulting version
  strings obey PEP440. See for example
  .

  suffix 1build1 is invalid.

  Some python building tools, that verifies if version strings are
  compatible with PEP440, are failing.

  Example: python poetry: Invalid PEP 440 version: '1.1build1'

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/devscripts/+bug/1991606/+subscriptions


-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp

[Touch-packages] [Bug 2004459] [NEW] /usr/bin/software-properties-gtk:uaclient.exceptions.ConnectivityError:do_open:request:_send_request:endheaders:_send_output:send:connect:connect:create_connection

[errors.ubuntu.com bug bridge]

Public bug reported:

The Ubuntu Error Tracker has been receiving reports about a problem regarding 
software-properties.  This problem was most recently seen with package version 
0.99.22.5, the problem page at 
https://errors.ubuntu.com/problem/52f13b0d1d5c75b8a964d28dbe58d616be9fa781 
contains more details, including versions of packages affected, stacktrace or 
traceback, and individual crash reports.
If you do not have access to the Ubuntu Error Tracker and are a software 
developer, you can request it at http://forms.canonical.com/reports/.

** Affects: software-properties (Ubuntu)
 Importance: High
 Status: Confirmed


** Tags: jammy

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to software-properties in
Ubuntu.
https://bugs.launchpad.net/bugs/2004459

Title:
  /usr/bin/software-properties-
  
gtk:uaclient.exceptions.ConnectivityError:do_open:request:_send_request:endheaders:_send_output:send:connect:connect:create_connection:getaddrinfo:request_url:readurl:urlopen:open:_open:_call_chain:https_open:do_open:get_magic_attach_token_info:request_url:poll_for_magic_token:wait:_wait:_wait:get_magic_attach_token_info

Status in software-properties package in Ubuntu:
  Confirmed

Bug description:
  The Ubuntu Error Tracker has been receiving reports about a problem regarding 
software-properties.  This problem was most recently seen with package version 
0.99.22.5, the problem page at 
https://errors.ubuntu.com/problem/52f13b0d1d5c75b8a964d28dbe58d616be9fa781 
contains more details, including versions of packages affected, stacktrace or 
traceback, and individual crash reports.
  If you do not have access to the Ubuntu Error Tracker and are a software 
developer, you can request it at http://forms.canonical.com/reports/.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/software-properties/+bug/2004459/+subscriptions


-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp

[Touch-packages] [Bug 2004459] Re: /usr/bin/software-properties-gtk:uaclient.exceptions.ConnectivityError:do_open:request:_send_request:endheaders:_send_output:send:connect:connect:create_connection:g

[Sebastien Bacher]

** Changed in: software-properties (Ubuntu)
   Importance: Undecided => High

** Changed in: software-properties (Ubuntu)
   Status: New => Confirmed

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to software-properties in
Ubuntu.
https://bugs.launchpad.net/bugs/2004459

Title:
  /usr/bin/software-properties-
  
gtk:uaclient.exceptions.ConnectivityError:do_open:request:_send_request:endheaders:_send_output:send:connect:connect:create_connection:getaddrinfo:request_url:readurl:urlopen:open:_open:_call_chain:https_open:do_open:get_magic_attach_token_info:request_url:poll_for_magic_token:wait:_wait:_wait:get_magic_attach_token_info

Status in software-properties package in Ubuntu:
  Confirmed

Bug description:
  The Ubuntu Error Tracker has been receiving reports about a problem regarding 
software-properties.  This problem was most recently seen with package version 
0.99.22.5, the problem page at 
https://errors.ubuntu.com/problem/52f13b0d1d5c75b8a964d28dbe58d616be9fa781 
contains more details, including versions of packages affected, stacktrace or 
traceback, and individual crash reports.
  If you do not have access to the Ubuntu Error Tracker and are a software 
developer, you can request it at http://forms.canonical.com/reports/.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/software-properties/+bug/2004459/+subscriptions


-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp