date:20240416

Forgetting and reconnecting to the WiFi networks solves the issue. 
Fell free to mark this bug as solved if you consider that this workaround 
invalidates the bug.

-- 
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/2061686

Title:
  After updating to ubuntu 24.04, WiFi doesn't connect to secured
  networks at login or resume from sleep

Status in network-manager package in Ubuntu:
  New

Bug description:
  I updated a Thinkpad T14 AMD Gen 2 from 23.10 to 24.04. Since the
  update, WiFi doesn't automatically connect at login or when resuming
  from sleep if the network is secured with a password.

  It does connect automatically if it finds a remembered open network.

  ProblemType: Bug
  DistroRelease: Ubuntu 24.04
  Package: network-manager 1.46.0-1ubuntu2
  ProcVersionSignature: Ubuntu 6.8.0-22.22-generic 6.8.1
  Uname: Linux 6.8.0-22-generic x86_64
  ApportVersion: 2.28.0-0ubuntu1
  Architecture: amd64
  CRDA: N/A
  CasperMD5CheckResult: pass
  CurrentDesktop: ubuntu:GNOME
  Date: Mon Apr 15 17:50:40 2024
  InstallationDate: Installed on 2022-02-02 (803 days ago)
  InstallationMedia: Ubuntu 21.10 "Impish Indri" - Release amd64 (20211012)
  IpRoute:
   default via 192.168.0.1 dev wlan0 proto dhcp src 192.168.0.128 metric 600 
   172.17.0.0/16 dev docker0 proto kernel scope link src 172.17.0.1 linkdown 
   192.168.0.0/24 dev wlan0 proto kernel scope link src 192.168.0.128 metric 
600 
   192.168.122.0/24 dev virbr0 proto kernel scope link src 192.168.122.1 
linkdown
  SourcePackage: network-manager
  UpgradeStatus: Upgraded to noble on 2024-04-11 (4 days ago)
  nmcli-nm:
   RUNNING VERSION  STATE  STARTUP   CONNECTIVITY  NETWORKING  WIFI-HW  
 WIFI  WWAN-HW  WWAN 
   ejecutando  1.46.0   conectado  Iniciado  total activadoactivado 
 activado  missing  activado

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/2061686/+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 2061912] Re: After a very recent update most browsers are not able to load webpages in Ubuntu 24.04

** Package changed: network-manager (Ubuntu) => linux-lowlatency
(Ubuntu)

-- 
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/2061912

Title:
  After a very recent update most browsers are not able to load webpages
  in Ubuntu 24.04

Status in linux-lowlatency package in Ubuntu:
  New

Bug description:
  After a recent update of packages (in the last couple of hours or so)
  neither Firefox (snap) nor Google Chrome (.deb) nor Chromium (snap)
  are able to load pages. Gnome Web is the only one that seems to work.
  Also, apt loads fine.

  Chromium complains of DNS_PROBE_FINISHED_NO_INTERNET.

  ProblemType: Bug
  DistroRelease: Ubuntu 24.04
  Package: network-manager 1.46.0-1ubuntu2
  ProcVersionSignature: Ubuntu 6.8.0-25.25.3-lowlatency 6.8.1
  Uname: Linux 6.8.0-25-lowlatency x86_64
  ApportVersion: 2.28.0-0ubuntu1
  Architecture: amd64
  CRDA: N/A
  CasperMD5CheckResult: pass
  CurrentDesktop: ubuntu:GNOME
  Date: Tue Apr 16 18:55:41 2024
  InstallationDate: Installed on 2022-02-02 (804 days ago)
  InstallationMedia: Ubuntu 21.10 "Impish Indri" - Release amd64 (20211012)
  IpRoute:
   default via 192.168.0.1 dev wlan0 proto dhcp src 192.168.0.128 metric 600 
   172.17.0.0/16 dev docker0 proto kernel scope link src 172.17.0.1 linkdown 
   192.168.0.0/24 dev wlan0 proto kernel scope link src 192.168.0.128 metric 
600 
   192.168.122.0/24 dev virbr0 proto kernel scope link src 192.168.122.1 
linkdown
  SourcePackage: network-manager
  UpgradeStatus: Upgraded to noble on 2024-04-11 (5 days ago)
  nmcli-nm:
   RUNNING VERSION  STATE  STARTUP   CONNECTIVITY  NETWORKING  WIFI-HW  
 WIFI  WWAN-HW  WWAN 
   ejecutando  1.46.0   conectado  Iniciado  total activadoactivado 
 activado  missing  activado

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux-lowlatency/+bug/2061912/+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

Re: [Touch-packages] [Bug 2061912] [NEW] After a very recent update most browsers are not able to load webpages in Ubuntu 24.04

I could narrow down the problem to linux-lowlatency 6.8.0-25.25.3.
Before updating to Ubuntu 24.04 I had the lowlatency kernel installed. When
updating it reverted back to generic and the last update installed
linux-lowlatency 6.8.0-25.25.3, which seems to have generated the bug.

Uninstalling the lowlatency kernel and running on the generic solves the
issue.

On Tue, Apr 16, 2024 at 7:05 PM Nicolás Abel Carbone <
2061...@bugs.launchpad.net> wrote:

> Public bug reported:
>
> After a recent update of packages (in the last couple of hours or so)
> neither Firefox (snap) nor Google Chrome (.deb) nor Chromium (snap) are
> able to load pages. Gnome Web is the only one that seems to work. Also,
> apt loads fine.
>
> Chromium complains of DNS_PROBE_FINISHED_NO_INTERNET.
>
> ProblemType: Bug
> DistroRelease: Ubuntu 24.04
> Package: network-manager 1.46.0-1ubuntu2
> ProcVersionSignature: Ubuntu 6.8.0-25.25.3-lowlatency 6.8.1
> Uname: Linux 6.8.0-25-lowlatency x86_64
> ApportVersion: 2.28.0-0ubuntu1
> Architecture: amd64
> CRDA: N/A
> CasperMD5CheckResult: pass
> CurrentDesktop: ubuntu:GNOME
> Date: Tue Apr 16 18:55:41 2024
> InstallationDate: Installed on 2022-02-02 (804 days ago)
> InstallationMedia: Ubuntu 21.10 "Impish Indri" - Release amd64 (20211012)
> IpRoute:
>  default via 192.168.0.1 dev wlan0 proto dhcp src 192.168.0.128 metric 600
>  172.17.0.0/16 dev docker0 proto kernel scope link src 172.17.0.1
> linkdown
>  192.168.0.0/24 dev wlan0 proto kernel scope link src 192.168.0.128
> metric 600
>  192.168.122.0/24 dev virbr0 proto kernel scope link src 192.168.122.1
> linkdown
> SourcePackage: network-manager
> UpgradeStatus: Upgraded to noble on 2024-04-11 (5 days ago)
> nmcli-nm:
>  RUNNING VERSION  STATE  STARTUP   CONNECTIVITY  NETWORKING
> WIFI-HW   WIFI  WWAN-HW  WWAN
>  ejecutando  1.46.0   conectado  Iniciado  total activado
> activado  activado  missing  activado
>
> ** Affects: network-manager (Ubuntu)
>  Importance: Undecided
>  Status: New
>
>
> ** Tags: amd64 apport-bug noble wayland-session
>
> --
> You received this bug notification because you are subscribed to the bug
> report.
> https://bugs.launchpad.net/bugs/2061912
>
> Title:
>   After a very recent update most browsers are not able to load webpages
>   in Ubuntu 24.04
>
> To manage notifications about this bug go to:
>
> https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/2061912/+subscriptions
>
>

-- 
Nicolás Abel Carbone

Doctor en Física
Investigador Asistente CONICET
JTP en Facultad de Ciencias Exactas UNCPBA
Grupo de Óptica Biomédica - CIFICEN-CONICET-UNCPBA

Research Gate  - epsilon.h
 - Bionirs  - Github


*Mi horario de trabajo puede no coincidir con el suyo. Salvo que así lo
indique el mail, por favor no se sienta obligado a responder este mensaje
fuera de su horario de trabajo habitual.*

*My working hours may not be your working hours. Unless otherwise specified
in the mail, please do not feel obligated to reply outside of your normal
work schedule.*

-- 
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/2061912

Title:
  After a very recent update most browsers are not able to load webpages
  in Ubuntu 24.04

Status in network-manager package in Ubuntu:
  New

Bug description:
  After a recent update of packages (in the last couple of hours or so)
  neither Firefox (snap) nor Google Chrome (.deb) nor Chromium (snap)
  are able to load pages. Gnome Web is the only one that seems to work.
  Also, apt loads fine.

  Chromium complains of DNS_PROBE_FINISHED_NO_INTERNET.

  ProblemType: Bug
  DistroRelease: Ubuntu 24.04
  Package: network-manager 1.46.0-1ubuntu2
  ProcVersionSignature: Ubuntu 6.8.0-25.25.3-lowlatency 6.8.1
  Uname: Linux 6.8.0-25-lowlatency x86_64
  ApportVersion: 2.28.0-0ubuntu1
  Architecture: amd64
  CRDA: N/A
  CasperMD5CheckResult: pass
  CurrentDesktop: ubuntu:GNOME
  Date: Tue Apr 16 18:55:41 2024
  InstallationDate: Installed on 2022-02-02 (804 days ago)
  InstallationMedia: Ubuntu 21.10 "Impish Indri" - Release amd64 (20211012)
  IpRoute:
   default via 192.168.0.1 dev wlan0 proto dhcp src 192.168.0.128 metric 600 
   172.17.0.0/16 dev docker0 proto kernel scope link src 172.17.0.1 linkdown 
   192.168.0.0/24 dev wlan0 proto kernel scope link src 192.168.0.128 metric 
600 
   192.168.122.0/24 dev virbr0 proto kernel scope link src 192.168.122.1 
linkdown
  SourcePackage: network-manager
  UpgradeStatus: Upgraded to noble on 2024-04-11 (5 days ago)
  nmcli-nm:
   RUNNING VERSION  STATE  STARTUP   CONNECTIVITY  NETWORKING  WIFI-HW  
 WIFI  WWAN-HW  WWAN 
   ejecutando  1.46.0   conectado  Iniciado  total activadoactivado 
 activado  missing  activado

To manage notifications about this bug go to:

[Touch-packages] [Bug 2061912] [NEW] After a very recent update most browsers are not able to load webpages in Ubuntu 24.04

Public bug reported:

After a recent update of packages (in the last couple of hours or so)
neither Firefox (snap) nor Google Chrome (.deb) nor Chromium (snap) are
able to load pages. Gnome Web is the only one that seems to work. Also,
apt loads fine.

Chromium complains of DNS_PROBE_FINISHED_NO_INTERNET.

ProblemType: Bug
DistroRelease: Ubuntu 24.04
Package: network-manager 1.46.0-1ubuntu2
ProcVersionSignature: Ubuntu 6.8.0-25.25.3-lowlatency 6.8.1
Uname: Linux 6.8.0-25-lowlatency x86_64
ApportVersion: 2.28.0-0ubuntu1
Architecture: amd64
CRDA: N/A
CasperMD5CheckResult: pass
CurrentDesktop: ubuntu:GNOME
Date: Tue Apr 16 18:55:41 2024
InstallationDate: Installed on 2022-02-02 (804 days ago)
InstallationMedia: Ubuntu 21.10 "Impish Indri" - Release amd64 (20211012)
IpRoute:
 default via 192.168.0.1 dev wlan0 proto dhcp src 192.168.0.128 metric 600 
 172.17.0.0/16 dev docker0 proto kernel scope link src 172.17.0.1 linkdown 
 192.168.0.0/24 dev wlan0 proto kernel scope link src 192.168.0.128 metric 600 
 192.168.122.0/24 dev virbr0 proto kernel scope link src 192.168.122.1 linkdown
SourcePackage: network-manager
UpgradeStatus: Upgraded to noble on 2024-04-11 (5 days ago)
nmcli-nm:
 RUNNING VERSION  STATE  STARTUP   CONNECTIVITY  NETWORKING  WIFI-HW   
WIFI  WWAN-HW  WWAN 
 ejecutando  1.46.0   conectado  Iniciado  total activadoactivado  
activado  missing  activado

** Affects: network-manager (Ubuntu)
 Importance: Undecided
 Status: New


** Tags: amd64 apport-bug noble wayland-session

-- 
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/2061912

Title:
  After a very recent update most browsers are not able to load webpages
  in Ubuntu 24.04

Status in network-manager package in Ubuntu:
  New

Bug description:
  After a recent update of packages (in the last couple of hours or so)
  neither Firefox (snap) nor Google Chrome (.deb) nor Chromium (snap)
  are able to load pages. Gnome Web is the only one that seems to work.
  Also, apt loads fine.

  Chromium complains of DNS_PROBE_FINISHED_NO_INTERNET.

  ProblemType: Bug
  DistroRelease: Ubuntu 24.04
  Package: network-manager 1.46.0-1ubuntu2
  ProcVersionSignature: Ubuntu 6.8.0-25.25.3-lowlatency 6.8.1
  Uname: Linux 6.8.0-25-lowlatency x86_64
  ApportVersion: 2.28.0-0ubuntu1
  Architecture: amd64
  CRDA: N/A
  CasperMD5CheckResult: pass
  CurrentDesktop: ubuntu:GNOME
  Date: Tue Apr 16 18:55:41 2024
  InstallationDate: Installed on 2022-02-02 (804 days ago)
  InstallationMedia: Ubuntu 21.10 "Impish Indri" - Release amd64 (20211012)
  IpRoute:
   default via 192.168.0.1 dev wlan0 proto dhcp src 192.168.0.128 metric 600 
   172.17.0.0/16 dev docker0 proto kernel scope link src 172.17.0.1 linkdown 
   192.168.0.0/24 dev wlan0 proto kernel scope link src 192.168.0.128 metric 
600 
   192.168.122.0/24 dev virbr0 proto kernel scope link src 192.168.122.1 
linkdown
  SourcePackage: network-manager
  UpgradeStatus: Upgraded to noble on 2024-04-11 (5 days ago)
  nmcli-nm:
   RUNNING VERSION  STATE  STARTUP   CONNECTIVITY  NETWORKING  WIFI-HW  
 WIFI  WWAN-HW  WWAN 
   ejecutando  1.46.0   conectado  Iniciado  total activadoactivado 
 activado  missing  activado

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/2061912/+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 1097467] Re: bash does not fulfill --rcfile option properly

2024-04-16 Thread Dave Jones

Attaching new debdiff based on the current noble version.

** Patch added: "1097467-3.debdiff"

https://bugs.launchpad.net/ubuntu/+source/bash/+bug/1097467/+attachment/5766422/+files/1097467-3.debdiff

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

Title:
bash does not fulfill --rcfile option properly

Status in Gnu Bash:
New
Status in bash package in Ubuntu:
Confirmed

Bug description:
I am starting a bash shell using

$ bash --noprofile --rcfile my-custom-bash-rc-file

Due to the --rcflag, the newly started bash should *not* execute
commands from /etc/bash.bashrc. That is at least how I interpret `man
bash`:

--rcfile file
Execute commands from file instead of the system wide
initialization file /etc/bash.bashrc and the standard personal initial‐
ization file ~/.bashrc if the shell is interactive (see
INVOCATION below).

However, it seems that the commands in /etc/bash.bashrc are in fact
executed.

To see/reproduce/diagnose this, on Ubuntu I believe one can just
invoke bash like this (as the regular user):

$ touch testrc
$ env -i bash --noprofile --rcfile testrc

The expected result would be that nothing special is printed on the
terminal. However, there is an error message, which is printed from
/etc/bash.bashrc. The "env -i" causes $HOME to not be set in the
invoked shell, which in turn triggers the error. The error message is:

> To run a command as administrator (user "root"), use "sudo ".
> See "man sudo_root" for details.

Another way to see this -- without the "env -i" -- is to add a
command to /etc/bash.bashrc, such as

echo HELLO THERE

To trigger the bug(?), one can then just do

$ touch testrc
$ bash --noprofile --rcfile testrc

The expected result would be that nothing special is shown in the
terminal. However, it turns out that the string

HELLO THERE

is printed.

To manage notifications about this bug go to:
https://bugs.launchpad.net/gnubash/+bug/1097467/+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 2061886] [NEW] Under VMWare resolution does not change automaticaly

2024-04-16 Thread Mario Charest

Public bug reported:

When resizing a VMWare Workstation, under Ubuntu20 the resolution would
change automaticaly.  It does not in the Ubuntu 24 Beta. During
installation I have enabled download of third party driver.

I can see vmtoold running.

ProblemType: Bug
DistroRelease: Ubuntu 24.04
Package: xorg 1:7.7+23ubuntu2
ProcVersionSignature: Ubuntu 6.8.0-22.22-generic 6.8.1
Uname: Linux 6.8.0-22-generic x86_64
ApportVersion: 2.28.0-0ubuntu1
Architecture: amd64
CasperMD5CheckResult: pass
CompositorRunning: None
CurrentDesktop: XFCE
Date: Tue Apr 16 14:03:39 2024
DistUpgraded: Fresh install
DistroCodename: noble
DistroVariant: ubuntu
ExtraDebuggingInterest: Yes
GraphicsCard:
 VMware SVGA II Adapter [15ad:0405] (prog-if 00 [VGA controller])
   Subsystem: VMware SVGA II Adapter [15ad:0405]
InstallationDate: Installed on 2024-04-16 (0 days ago)
InstallationMedia: Xubuntu 24.04 LTS "Noble Numbat" - Beta amd64 (20240410.1)
Lsusb: Error: command ['lsusb'] failed with exit code 1:
Lsusb-t:
 
Lsusb-v: Error: command ['lsusb', '-v'] failed with exit code 1:
MachineType: VMware, Inc. VMware7,1
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-6.8.0-22-generic 
root=UUID=93447c69-bef1-4d4b-917b-41be1fbda0ea ro
SourcePackage: xorg
Symptom: display
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 01/11/2023
dmi.bios.vendor: VMware, Inc.
dmi.bios.version: VMW71.00V.21100432.B64.2301110304
dmi.board.name: 440BX Desktop Reference Platform
dmi.board.vendor: Intel Corporation
dmi.board.version: None
dmi.chassis.asset.tag: No Asset Tag
dmi.chassis.type: 1
dmi.chassis.vendor: No Enclosure
dmi.chassis.version: N/A
dmi.modalias: 
dmi:bvnVMware,Inc.:bvrVMW71.00V.21100432.B64.2301110304:bd01/11/2023:svnVMware,Inc.:pnVMware7,1:pvrNone:rvnIntelCorporation:rn440BXDesktopReferencePlatform:rvrNone:cvnNoEnclosure:ct1:cvrN/A:sku:
dmi.product.name: VMware7,1
dmi.product.version: None
dmi.sys.vendor: VMware, Inc.
version.compiz: compiz N/A
version.libdrm2: libdrm2 2.4.120-2build1
version.libgl1-mesa-dri: libgl1-mesa-dri 24.0.5-1ubuntu1
version.libgl1-mesa-glx: libgl1-mesa-glx N/A
version.xserver-xorg-core: xserver-xorg-core 2:21.1.11-2ubuntu1
version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:22.0.0-1build1
version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20210115-1build1
version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.17-2build1

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


** Tags: amd64 apport-bug noble resolution ubuntu

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

Title:
  Under VMWare resolution does not change automaticaly

Status in xorg package in Ubuntu:
  New

Bug description:
  When resizing a VMWare Workstation, under Ubuntu20 the resolution
  would change automaticaly.  It does not in the Ubuntu 24 Beta. During
  installation I have enabled download of third party driver.

  I can see vmtoold running.

  ProblemType: Bug
  DistroRelease: Ubuntu 24.04
  Package: xorg 1:7.7+23ubuntu2
  ProcVersionSignature: Ubuntu 6.8.0-22.22-generic 6.8.1
  Uname: Linux 6.8.0-22-generic x86_64
  ApportVersion: 2.28.0-0ubuntu1
  Architecture: amd64
  CasperMD5CheckResult: pass
  CompositorRunning: None
  CurrentDesktop: XFCE
  Date: Tue Apr 16 14:03:39 2024
  DistUpgraded: Fresh install
  DistroCodename: noble
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes
  GraphicsCard:
   VMware SVGA II Adapter [15ad:0405] (prog-if 00 [VGA controller])
 Subsystem: VMware SVGA II Adapter [15ad:0405]
  InstallationDate: Installed on 2024-04-16 (0 days ago)
  InstallationMedia: Xubuntu 24.04 LTS "Noble Numbat" - Beta amd64 (20240410.1)
  Lsusb: Error: command ['lsusb'] failed with exit code 1:
  Lsusb-t:
   
  Lsusb-v: Error: command ['lsusb', '-v'] failed with exit code 1:
  MachineType: VMware, Inc. VMware7,1
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-6.8.0-22-generic 
root=UUID=93447c69-bef1-4d4b-917b-41be1fbda0ea ro
  SourcePackage: xorg
  Symptom: display
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 01/11/2023
  dmi.bios.vendor: VMware, Inc.
  dmi.bios.version: VMW71.00V.21100432.B64.2301110304
  dmi.board.name: 440BX Desktop Reference Platform
  dmi.board.vendor: Intel Corporation
  dmi.board.version: None
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 1
  dmi.chassis.vendor: No Enclosure
  dmi.chassis.version: N/A
  dmi.modalias: 
dmi:bvnVMware,Inc.:bvrVMW71.00V.21100432.B64.2301110304:bd01/11/2023:svnVMware,Inc.:pnVMware7,1:pvrNone:rvnIntelCorporation:rn440BXDesktopReferencePlatform:rvrNone:cvnNoEnclosure:ct1:cvrN/A:sku:
  dmi.product.name: VMware7,1
  dmi.product.version: None
  dmi.sys.vendor: VMware, Inc.
  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.120-2build1

[Touch-packages] [Bug 2061753] Re: /usr/share/apport/whoopsie-upload-all:RuntimeError:/usr/share/apport/whoopsie-upload-all@246:main:collect_info:process_report:add_gdb_info:gdb_command:write:_get_zst

The apport binary need an additional dependency: "apport-core-dump-
handler | python3-zstandard"

-- 
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/2061753

Title:
  /usr/share/apport/whoopsie-upload-
  all:RuntimeError:/usr/share/apport/whoopsie-upload-
  
all@246:main:collect_info:process_report:add_gdb_info:gdb_command:write:_get_zstandard_decompressor

Status in apport package in Ubuntu:
  Confirmed

Bug description:
  The Ubuntu Error Tracker has been receiving reports about a problem regarding 
apport.  This problem was most recently seen with package version 
2.28.0-0ubuntu1, the problem page at 
https://errors.ubuntu.com/problem/f50c9c3ef623e6e5c7e3e7d4d1915d8fc6b938f1 
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

  Traceback (most recent call last):
File "/usr/share/apport/whoopsie-upload-all", line 246, in 
  main()
File "/usr/share/apport/whoopsie-upload-all", line 228, in main
  stamps = collect_info()
   ^^
File "/usr/share/apport/whoopsie-upload-all", line 162, in collect_info
  res = process_report(r)
^
File "/usr/share/apport/whoopsie-upload-all", line 112, in process_report
  r.add_gdb_info()
File "/usr/lib/python3/dist-packages/apport/report.py", line 932, in 
add_gdb_info
  gdb_cmd, environ = self.gdb_command(rootdir, gdb_sandbox)
 ^^
File "/usr/lib/python3/dist-packages/apport/report.py", line 1942, in 
gdb_command
  self["CoreDump"].write(f)
File "/usr/lib/python3/dist-packages/problem_report.py", line 284, in write
  decompressor = _get_zstandard_decompressor()
 ^
File "/usr/lib/python3/dist-packages/problem_report.py", line 139, in 
_get_zstandard_decompressor
  raise RuntimeError(
  RuntimeError: Failed to import zstandard library: No module named 
'zstandard'. Please install python3-zstandard.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/apport/+bug/2061753/+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 2060898] Re: Trying to install gimp-help-en threatens to install wslu

This bug was fixed in the package ubuntu-mate-meta - 1.296

---
ubuntu-mate-meta (1.296) noble; urgency=medium

  * Refreshed dependencies
  * Added caja-seahorse to desktop-recommends [armhf]
  * Added firefox to core-recommends [amd64 arm64 armhf], desktop-
recommends [amd64 arm64 armhf] (LP: #2060898)

 -- Martin Wimpress   Tue, 16 Apr 2024 14:47:27 +

** Changed in: ubuntu-mate-meta (Ubuntu Noble)
   Status: Fix Committed => Fix Released

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

Title:
  Trying to install gimp-help-en threatens to install wslu

Status in edubuntu-meta package in Ubuntu:
  Fix Released
Status in kubuntu-meta package in Ubuntu:
  Fix Released
Status in lubuntu-meta package in Ubuntu:
  Fix Released
Status in ubuntu-budgie-meta package in Ubuntu:
  Fix Released
Status in ubuntu-mate-meta package in Ubuntu:
  Fix Released
Status in ubuntu-meta package in Ubuntu:
  Invalid
Status in ubuntustudio-meta package in Ubuntu:
  Fix Released
Status in wslu package in Ubuntu:
  Invalid
Status in edubuntu-meta source package in Noble:
  Fix Released
Status in kubuntu-meta source package in Noble:
  Fix Released
Status in lubuntu-meta source package in Noble:
  Fix Released
Status in ubuntu-budgie-meta source package in Noble:
  Fix Released
Status in ubuntu-mate-meta source package in Noble:
  Fix Released
Status in ubuntu-meta source package in Noble:
  Invalid
Status in ubuntustudio-meta source package in Noble:
  Fix Released
Status in wslu source package in Noble:
  Invalid

Bug description:
  Filing this against ubuntu-meta since I believe this is a seed problem
  that potentially affects all variants of Ubuntu (flavors or
  otherwise).

  wslu is "a collection of utilities for the Windows 10 Linux Subsystem,
  such as for converting Linux paths to a Windows paths or creating
  Linux application shortcuts on the Windows 10 Desktop." Obviously this
  package should *never* be installed on a desktop or even on most VMs,
  but only within WSL instances. However...

  wslu provides the virtual package www-browser, as one of its features
  is to open links in Windows 10 using the default browser set there.
  This means that if a package depends or recommends www-browser, it may
  attempt to pull in one of several packages, wslu included. In the
  past, this hasn't been a problem because Firefox was present on all
  flavor images, and Firefox provides www-browser as well. However, now
  that Firefox is a Snap, it is possible for Firefox to be installed
  without the firefox transitional apt package being installed. (This is
  the case in a default installation of Kubuntu Noble Beta.) As it turns
  out, Kubuntu Noble Beta ships with *no* packages that provide www-
  browser, meaning that any package that depends on it will have to
  install a new browser.

  Due to some stroke of misfortune, apt is picking wslu out of all
  packages as the package for this use case. Installing gimp-help-en
  will also install www-browser, which results in wslu becoming
  installed.

  wslu causes quite a few problems when installed on a desktop system -
  among them, the syslog is spammed with errors due to the system not in
  fact being a WSL VM, audio breaks in weird ways, and application
  launchers sometimes fail. Why this happens is unclear, but the issues
  appear to resolve once wslu is removed from the system. It is
  therefore probably a good idea to avoid wslu becoming installed on
  accident in this way.

  Probably the best way to resolve this is to ensure that some package
  that provides www-browser is available on every Ubuntu image. This
  could be done via seeding or by adding a package to ubuntu-minimal.
  Alternatively, wslu could be set to no longer provide www-browser,
  though it's unclear if that would break its functionality.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/edubuntu-meta/+bug/2060898/+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 2061869] Re: Snaps unable to connect to network under linux-lowlatency 6.8.0-25.25.3

2024-04-16 Thread John Johansen

the kernel team is already rolling kernels with the fix for 2061851 but
it is also building in https://launchpad.net/~apparmor-
dev/+archive/ubuntu/apparmor-devel ppa

-- 
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/2061869

Title:
  Snaps unable to connect to network under linux-lowlatency
  6.8.0-25.25.3

Status in apparmor package in Ubuntu:
  New
Status in linux-lowlatency package in Ubuntu:
  New

Bug description:
  After upgrading to linux-lowlatency 6.8.0-25, suddenly snaps can no
  longer connect to network. I tried downgrading snapd from edge, still
  no connectivity. Only solution was to downgrade back to 6.8.0-7. I'll
  also add apparmor in case this is an apparmor issue as well.

  Marking as "critical" priority as this affects all installs of Ubuntu
  Studio and affects Firefox and Thunderbird.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/apparmor/+bug/2061869/+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 2061869] Re: Snaps unable to connect to network under linux-lowlatency 6.8.0-25.25.3

2024-04-16 Thread John Johansen

This is likely a dup of
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2061851

-- 
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/2061869

Title:
  Snaps unable to connect to network under linux-lowlatency
  6.8.0-25.25.3

Status in apparmor package in Ubuntu:
  New
Status in linux-lowlatency package in Ubuntu:
  New

Bug description:
  After upgrading to linux-lowlatency 6.8.0-25, suddenly snaps can no
  longer connect to network. I tried downgrading snapd from edge, still
  no connectivity. Only solution was to downgrade back to 6.8.0-7. I'll
  also add apparmor in case this is an apparmor issue as well.

  Marking as "critical" priority as this affects all installs of Ubuntu
  Studio and affects Firefox and Thunderbird.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/apparmor/+bug/2061869/+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 2058380] Re: apport crashed with FileNotFoundError in iter_compressed(): [Errno 2] No such file or directory: '/var/lib/systemd/coredump/core.tracker-extract.1000.92c6d53b71364e3

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

** Changed in: apport
   Status: New => Fix Committed

** Changed in: apport (Ubuntu)
   Status: New => 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/2058380

Title:
  apport crashed with FileNotFoundError in iter_compressed(): [Errno 2]
  No such file or directory: '/var/lib/systemd/coredump/core.tracker-
  extract.1000.92c6d53b71364e3286fd6011f3dad5e7.4441.171084529900.zst'

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

Bug description:
  Ubuntu 24.04 (noble) VM.

  ```
  Traceback (most recent call last):
File "/usr/share/apport/apport", line 1244, in 
  sys.exit(main(sys.argv[1:]))
   ^^
File "/usr/share/apport/apport", line 761, in main
  return 
process_crash_from_systemd_coredump(options.systemd_coredump_instance)
 
^^
File "/usr/share/apport/apport", line 1240, in 
process_crash_from_systemd_coredump
  return process_crash(report, real_user, report_owner)
 ^^
File "/usr/share/apport/apport", line 1146, in process_crash
  info.write(reportfile)
File "/usr/lib/python3/dist-packages/problem_report.py", line 548, in write
  self._write_binary_item_compressed_and_encoded(file, k)
File "/usr/lib/python3/dist-packages/problem_report.py", line 722, in 
_write_binary_item_compressed_and_encoded
  self._write_binary_item_base64_encoded(
File "/usr/lib/python3/dist-packages/problem_report.py", line 629, in 
_write_binary_item_base64_encoded
  for chunk in chunks:
File "/usr/lib/python3/dist-packages/problem_report.py", line 649, in 
_generate_compressed_chunks
  yield from value.iter_compressed()
File "/usr/lib/python3/dist-packages/problem_report.py", line 194, in 
iter_compressed
  with open(self.filename, "rb") as compressed_file:
   ^
  FileNotFoundError: [Errno 2] No such file or directory: 
'/var/lib/systemd/coredump/core.tracker-extract.1000.92c6d53b71364e3286fd6011f3dad5e7.4441.171084529900.zst'
  ```

  ProblemType: Crash
  DistroRelease: Ubuntu 24.04
  Package: apport 2.28.0-0ubuntu1
  ProcVersionSignature: Ubuntu 6.8.0-19.19-generic 6.8.0
  Uname: Linux 6.8.0-19-generic x86_64
  NonfreeKernelModules: zfs
  ApportVersion: 2.28.0-0ubuntu1
  Architecture: amd64
  CasperMD5CheckResult: pass
  CrashCounter: 1
  CrashReports: 640:1000:1000:31075:2024-03-19 11:48:24.843744754 
+0100:2024-03-19 11:48:25.843744754 
+0100:/var/crash/_usr_share_apport_apport.0.crash
  Date: Tue Mar 19 11:48:23 2024
  ExecutablePath: /usr/share/apport/apport
  InstallationDate: Installed on 2023-09-19 (182 days ago)
  InstallationMedia: Ubuntu 23.04 "Lunar Lobster" - Release amd64 (20230418)
  InterpreterPath: /usr/bin/python3.12
  PackageArchitecture: all
  ProcCmdline: /usr/bin/python3 /usr/share/apport/apport 
--from-systemd-coredump 0-4553-0
  ProcEnviron: Error: [Errno 13] Permission denied: 'environ'
  Python3Details: /usr/bin/python3.12, Python 3.12.2, python3-minimal, 
3.12.1-0ubuntu2
  PythonArgs: ['/usr/share/apport/apport', '--from-systemd-coredump', 
'0-4553-0']
  PythonDetails: N/A
  SourcePackage: apport
  Title: apport crashed with FileNotFoundError in iter_compressed(): [Errno 2] 
No such file or directory: 
'/var/lib/systemd/coredump/core.tracker-extract.1000.92c6d53b71364e3286fd6011f3dad5e7.4441.171084529900.zst'
  UpgradeStatus: Upgraded to noble on 2024-01-12 (67 days ago)
  UserGroups: adm cdrom dip lpadmin lxd plugdev sudo users

To manage notifications about this bug go to:
https://bugs.launchpad.net/apport/+bug/2058380/+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 2061869] [NEW] Snaps unable to connect to network under linux-lowlatency 6.8.0-25.25.3

2024-04-16 Thread Erich Eickmeyer

Public bug reported:

After upgrading to linux-lowlatency 6.8.0-25, suddenly snaps can no
longer connect to network. I tried downgrading snapd from edge, still no
connectivity. Only solution was to downgrade back to 6.8.0-7. I'll also
add apparmor in case this is an apparmor issue as well.

Marking as "critical" priority as this affects all installs of Ubuntu
Studio and affects Firefox and Thunderbird.

** Affects: apparmor (Ubuntu)
 Importance: Critical
 Status: New

** Affects: linux-lowlatency (Ubuntu)
 Importance: Critical
 Status: New

** Also affects: apparmor (Ubuntu)
   Importance: Undecided
   Status: New

** Description changed:

  After upgrading to linux-lowlatency 6.8.0-25, suddenly snaps can no
  longer connect to network. I tried downgrading snapd from edge, still no
  connectivity. Only solution was to downgrade back to 6.8.0-7. I'll also
  add apparmor in case this is an apparmor issue as well.
+ 
+ Marking as "critical" priority as this affects all installs of Ubuntu
+ Studio and affects Firefox and Thunderbird.

** Changed in: apparmor (Ubuntu)
   Importance: Undecided => Critical

** Changed in: linux-lowlatency (Ubuntu)
   Importance: Undecided => Critical

** Changed in: apparmor (Ubuntu)
Milestone: None => ubuntu-24.04

** Changed in: linux-lowlatency (Ubuntu)
Milestone: None => ubuntu-24.04

-- 
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/2061869

Title:
  Snaps unable to connect to network under linux-lowlatency
  6.8.0-25.25.3

Status in apparmor package in Ubuntu:
  New
Status in linux-lowlatency package in Ubuntu:
  New

Bug description:
  After upgrading to linux-lowlatency 6.8.0-25, suddenly snaps can no
  longer connect to network. I tried downgrading snapd from edge, still
  no connectivity. Only solution was to downgrade back to 6.8.0-7. I'll
  also add apparmor in case this is an apparmor issue as well.

  Marking as "critical" priority as this affects all installs of Ubuntu
  Studio and affects Firefox and Thunderbird.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/apparmor/+bug/2061869/+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 2061753] Re: /usr/share/apport/whoopsie-upload-all:RuntimeError:/usr/share/apport/whoopsie-upload-all@246:main:collect_info:process_report:add_gdb_info:gdb_command:write:_get_zst

2024-04-16 Thread Patrice DUROUX

Here is what I am getting (related to #2061739):

avril 16 17:23:35 kos-201907 whoopsie-upload-all[5701]: INFO:root:Collecting 
info for /var/crash/_usr_bin_gnome-shell.1001.crash...
avril 16 17:23:37 kos-201907 gnome-character[4079]: JS LOG: Characters 
Application exiting
avril 16 17:23:39 kos-201907 whoopsie-upload-all[5701]: Traceback (most recent 
call last):
avril 16 17:23:39 kos-201907 whoopsie-upload-all[5701]:   File 
"/usr/share/apport/whoopsie-upload-all", line 246, in 
avril 16 17:23:39 kos-201907 whoopsie-upload-all[5701]: main()
avril 16 17:23:39 kos-201907 whoopsie-upload-all[5701]:   File 
"/usr/share/apport/whoopsie-upload-all", line 228, in main
avril 16 17:23:39 kos-201907 whoopsie-upload-all[5701]: stamps = 
collect_info()
avril 16 17:23:39 kos-201907 whoopsie-upload-all[5701]:  
^^
avril 16 17:23:39 kos-201907 whoopsie-upload-all[5701]:   File 
"/usr/share/apport/whoopsie-upload-all", line 162, in collect_info
avril 16 17:23:39 kos-201907 whoopsie-upload-all[5701]: res = 
process_report(r)
avril 16 17:23:39 kos-201907 whoopsie-upload-all[5701]:   
^
avril 16 17:23:39 kos-201907 whoopsie-upload-all[5701]:   File 
"/usr/share/apport/whoopsie-upload-all", line 112, in process_report
avril 16 17:23:39 kos-201907 whoopsie-upload-all[5701]: r.add_gdb_info()
avril 16 17:23:39 kos-201907 whoopsie-upload-all[5701]:   File 
"/usr/lib/python3/dist-packages/apport/report.py", line 932, in add_gdb_info
avril 16 17:23:39 kos-201907 whoopsie-upload-all[5701]: gdb_cmd, environ = 
self.gdb_command(rootdir, gdb_sandbox)
avril 16 17:23:39 kos-201907 whoopsie-upload-all[5701]:
^^
avril 16 17:23:39 kos-201907 whoopsie-upload-all[5701]:   File 
"/usr/lib/python3/dist-packages/apport/report.py", line 1942, in gdb_command
avril 16 17:23:39 kos-201907 whoopsie-upload-all[5701]: 
self["CoreDump"].write(f)
avril 16 17:23:39 kos-201907 whoopsie-upload-all[5701]:   File 
"/usr/lib/python3/dist-packages/problem_report.py", line 284, in write
avril 16 17:23:39 kos-201907 whoopsie-upload-all[5701]: decompressor = 
_get_zstandard_decompressor()
avril 16 17:23:39 kos-201907 whoopsie-upload-all[5701]:
^
avril 16 17:23:39 kos-201907 whoopsie-upload-all[5701]:   File 
"/usr/lib/python3/dist-packages/problem_report.py", line 139, in 
_get_zstandard_decompressor
avril 16 17:23:39 kos-201907 whoopsie-upload-all[5701]: raise RuntimeError(
avril 16 17:23:39 kos-201907 whoopsie-upload-all[5701]: RuntimeError: Failed to 
import zstandard library: No module named 'zstandard'. Please install 
python3-zstandard.
avril 16 17:23:39 kos-201907 systemd[1]: apport-autoreport.service: Main 
process exited, code=exited, status=1/FAILURE

-- 
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/2061753

Title:
  /usr/share/apport/whoopsie-upload-
  all:RuntimeError:/usr/share/apport/whoopsie-upload-
  
all@246:main:collect_info:process_report:add_gdb_info:gdb_command:write:_get_zstandard_decompressor

Status in apport package in Ubuntu:
  Confirmed

Bug description:
  The Ubuntu Error Tracker has been receiving reports about a problem regarding 
apport.  This problem was most recently seen with package version 
2.28.0-0ubuntu1, the problem page at 
https://errors.ubuntu.com/problem/f50c9c3ef623e6e5c7e3e7d4d1915d8fc6b938f1 
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

  Traceback (most recent call last):
File "/usr/share/apport/whoopsie-upload-all", line 246, in 
  main()
File "/usr/share/apport/whoopsie-upload-all", line 228, in main
  stamps = collect_info()
   ^^
File "/usr/share/apport/whoopsie-upload-all", line 162, in collect_info
  res = process_report(r)
^
File "/usr/share/apport/whoopsie-upload-all", line 112, in process_report
  r.add_gdb_info()
File "/usr/lib/python3/dist-packages/apport/report.py", line 932, in 
add_gdb_info
  gdb_cmd, environ = self.gdb_command(rootdir, gdb_sandbox)
 ^^
File "/usr/lib/python3/dist-packages/apport/report.py", line 1942, in 
gdb_command
  self["CoreDump"].write(f)
File "/usr/lib/python3/dist-packages/problem_report.py", line 284, in write
  decompressor = _get_zstandard_decompressor()
 ^
File "/usr/lib/python3/dist-packages/problem_report.py", line 139, in 
_get_zstandard_decompressor
  raise RuntimeError(
  RuntimeError: Failed to import

[Touch-packages] [Bug 2061753] Re: /usr/share/apport/whoopsie-upload-all:RuntimeError:/usr/share/apport/whoopsie-upload-all@246:main:collect_info:process_report:add_gdb_info:gdb_command:write:_get_zst

Status changed to 'Confirmed' because the bug affects multiple users.

** Changed in: apport (Ubuntu)
   Status: New => Confirmed

-- 
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/2061753

Title:
  /usr/share/apport/whoopsie-upload-
  all:RuntimeError:/usr/share/apport/whoopsie-upload-
  
all@246:main:collect_info:process_report:add_gdb_info:gdb_command:write:_get_zstandard_decompressor

Status in apport package in Ubuntu:
  Confirmed

Bug description:
  The Ubuntu Error Tracker has been receiving reports about a problem regarding 
apport.  This problem was most recently seen with package version 
2.28.0-0ubuntu1, the problem page at 
https://errors.ubuntu.com/problem/f50c9c3ef623e6e5c7e3e7d4d1915d8fc6b938f1 
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

  Traceback (most recent call last):
File "/usr/share/apport/whoopsie-upload-all", line 246, in 
  main()
File "/usr/share/apport/whoopsie-upload-all", line 228, in main
  stamps = collect_info()
   ^^
File "/usr/share/apport/whoopsie-upload-all", line 162, in collect_info
  res = process_report(r)
^
File "/usr/share/apport/whoopsie-upload-all", line 112, in process_report
  r.add_gdb_info()
File "/usr/lib/python3/dist-packages/apport/report.py", line 932, in 
add_gdb_info
  gdb_cmd, environ = self.gdb_command(rootdir, gdb_sandbox)
 ^^
File "/usr/lib/python3/dist-packages/apport/report.py", line 1942, in 
gdb_command
  self["CoreDump"].write(f)
File "/usr/lib/python3/dist-packages/problem_report.py", line 284, in write
  decompressor = _get_zstandard_decompressor()
 ^
File "/usr/lib/python3/dist-packages/problem_report.py", line 139, in 
_get_zstandard_decompressor
  raise RuntimeError(
  RuntimeError: Failed to import zstandard library: No module named 
'zstandard'. Please install python3-zstandard.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/apport/+bug/2061753/+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 2058380] Re: apport crashed with FileNotFoundError in iter_compressed(): [Errno 2] No such file or directory: '/var/lib/systemd/coredump/core.tracker-extract.1000.92c6d53b71364e3

Proposed fix: https://github.com/canonical/apport/pull/318

-- 
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/2058380

Title:
  apport crashed with FileNotFoundError in iter_compressed(): [Errno 2]
  No such file or directory: '/var/lib/systemd/coredump/core.tracker-
  extract.1000.92c6d53b71364e3286fd6011f3dad5e7.4441.171084529900.zst'

Status in Apport:
  New
Status in apport package in Ubuntu:
  New

Bug description:
  Ubuntu 24.04 (noble) VM.

  ```
  Traceback (most recent call last):
File "/usr/share/apport/apport", line 1244, in 
  sys.exit(main(sys.argv[1:]))
   ^^
File "/usr/share/apport/apport", line 761, in main
  return 
process_crash_from_systemd_coredump(options.systemd_coredump_instance)
 
^^
File "/usr/share/apport/apport", line 1240, in 
process_crash_from_systemd_coredump
  return process_crash(report, real_user, report_owner)
 ^^
File "/usr/share/apport/apport", line 1146, in process_crash
  info.write(reportfile)
File "/usr/lib/python3/dist-packages/problem_report.py", line 548, in write
  self._write_binary_item_compressed_and_encoded(file, k)
File "/usr/lib/python3/dist-packages/problem_report.py", line 722, in 
_write_binary_item_compressed_and_encoded
  self._write_binary_item_base64_encoded(
File "/usr/lib/python3/dist-packages/problem_report.py", line 629, in 
_write_binary_item_base64_encoded
  for chunk in chunks:
File "/usr/lib/python3/dist-packages/problem_report.py", line 649, in 
_generate_compressed_chunks
  yield from value.iter_compressed()
File "/usr/lib/python3/dist-packages/problem_report.py", line 194, in 
iter_compressed
  with open(self.filename, "rb") as compressed_file:
   ^
  FileNotFoundError: [Errno 2] No such file or directory: 
'/var/lib/systemd/coredump/core.tracker-extract.1000.92c6d53b71364e3286fd6011f3dad5e7.4441.171084529900.zst'
  ```

  ProblemType: Crash
  DistroRelease: Ubuntu 24.04
  Package: apport 2.28.0-0ubuntu1
  ProcVersionSignature: Ubuntu 6.8.0-19.19-generic 6.8.0
  Uname: Linux 6.8.0-19-generic x86_64
  NonfreeKernelModules: zfs
  ApportVersion: 2.28.0-0ubuntu1
  Architecture: amd64
  CasperMD5CheckResult: pass
  CrashCounter: 1
  CrashReports: 640:1000:1000:31075:2024-03-19 11:48:24.843744754 
+0100:2024-03-19 11:48:25.843744754 
+0100:/var/crash/_usr_share_apport_apport.0.crash
  Date: Tue Mar 19 11:48:23 2024
  ExecutablePath: /usr/share/apport/apport
  InstallationDate: Installed on 2023-09-19 (182 days ago)
  InstallationMedia: Ubuntu 23.04 "Lunar Lobster" - Release amd64 (20230418)
  InterpreterPath: /usr/bin/python3.12
  PackageArchitecture: all
  ProcCmdline: /usr/bin/python3 /usr/share/apport/apport 
--from-systemd-coredump 0-4553-0
  ProcEnviron: Error: [Errno 13] Permission denied: 'environ'
  Python3Details: /usr/bin/python3.12, Python 3.12.2, python3-minimal, 
3.12.1-0ubuntu2
  PythonArgs: ['/usr/share/apport/apport', '--from-systemd-coredump', 
'0-4553-0']
  PythonDetails: N/A
  SourcePackage: apport
  Title: apport crashed with FileNotFoundError in iter_compressed(): [Errno 2] 
No such file or directory: 
'/var/lib/systemd/coredump/core.tracker-extract.1000.92c6d53b71364e3286fd6011f3dad5e7.4441.171084529900.zst'
  UpgradeStatus: Upgraded to noble on 2024-01-12 (67 days ago)
  UserGroups: adm cdrom dip lpadmin lxd plugdev sudo users

To manage notifications about this bug go to:
https://bugs.launchpad.net/apport/+bug/2058380/+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 2060311] Re: Setting "optional: true" to overcome he timeout "Job systemd-networkd-wait-online" does no longer work with latest noble image

2024-04-16 Thread Lukas Märdian

With version ~ppa5 we're now skipping the activation of systemd-
networkd-wait-online.service in case all Netplan interfaces are defined
to be "optional: true", using "ConditionPathIsSymbolicLink=" on
Netplan's s-n-wait-online.service enablement link, that's only set when
we have non-optional interfaces.

All the magic happens in /run/systemd/system/systemd-networkd-wait-
online.service.d/10-netplan.conf override under the generic "systemd-
networkd-wait-online.service" umbrella.

Code is up-to-date in https://github.com/canonical/netplan/pull/456
Test buidls in PPA: 
https://launchpad.net/~slyon/+archive/ubuntu/lp2060311/+packages

-- 
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/2060311

Title:
  Setting "optional: true" to overcome he timeout "Job systemd-networkd-
  wait-online" does no longer work with latest noble image

Status in Netplan:
  In Progress
Status in Ubuntu on IBM z Systems:
  New
Status in netplan.io package in Ubuntu:
  Confirmed
Status in systemd package in Ubuntu:
  Confirmed
Status in netplan.io source package in Noble:
  Confirmed
Status in systemd source package in Noble:
  Confirmed

Bug description:
  Especially on s390x (but not limited to s390x) it's often the case that a 
system has network devices that are not necessarily connected during boot-up 
and one gets such a 2 min timeout:
  "Job systemd-networkd-wait-online. Start running (1min 59s / no limit)"

  In the past I could avoid that by setting "optional: true" post-install (no 
perfect, but worked),
  but this does no longer seem to work using the latest noble ISO image (Apr 
5th).

  Setting 'optional: true' in /etc/netplan/50-cloud-init.yaml looks like
  this for me:

  # This file is generated from information provided by the datasource.  Changes
  # to it will not persist across an instance reboot.  To disable cloud-init's
  # network configuration capabilities, write a file
  # /etc/cloud/cloud.cfg.d/99-disable-network-config.cfg with the following:
  # network: {config: disabled}
  network:
  ethernets:
  enP1p0s0:
  optional: true
  dhcp4: true
  enP1p0s0d1:
  optional: true
  dhcp4: true
  enP2p0s0:
  optional: true
  dhcp4: true
  enP2p0s0d1:
  optional: true
  dhcp4: true
  encc000: {}
  version: 2
  vlans:
  encc000.2653:
  addresses:
  - 10.11.12.15/24
  gateway4: 10.11.12.1
  id: 2653
  link: encc000
  nameservers:
  addresses:
  - 10.11.12.1

  ... can be set fine (also --dry-run does not moan, except about
  dhcp4).

  This worked in the past on noble, but also on older Ubuntu releases
  like jammy.

To manage notifications about this bug go to:
https://bugs.launchpad.net/netplan/+bug/2060311/+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 2060721] Re: APT 2.8.0: Promote weak key warnings to errors

2024-04-16 Thread Julian Andres Klode

** Changed in: apt (Ubuntu Noble)
   Status: New => Triaged

** Changed in: apt (Ubuntu Noble)
 Assignee: (unassigned) => Julian Andres Klode (juliank)

-- 
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/2060721

Title:
  APT 2.8.0: Promote weak key warnings to errors

Status in apt package in Ubuntu:
  Triaged
Status in apt source package in Noble:
  Triaged

Bug description:
  ⚠️ Only land this in the release pocket after PPAs have been resigned

  (This bumps the apt version to 2.8.0. APT uses the odd/even number
  system, with 2.7.x being the development series for 2.8, and this is
  the only change left for the 2.8 release, safe for some minor
  translation/test suite improvements)

  (This will be uploaded after the beta and may be released before noble
  release, as a zero day SRU or within the weeks following the release)

  [Impact]
  APT is currently just warning about keys that it should be rejecting to give 
Launchpad time to resign PPAs. This needs to be bumped to an error such that 
the crypto policy is fully implemented and we only trust keys that are still 
being trusted. #2055193

  A warning provides some help right now to third-parties to fix their
  repositories, but it's not *safe*: A repository could have multiple
  signing keys and be signed by a good key now, then later, a previous
  key still in trusted.gpg.d could be revoked and we'd degrade to
  warnings, which, given that we update in the background automatically,
  the user may not see.

  Other fixes:
  - The test suite has been made less flaky in two places
  - Documentation translation has been unfuzzied for URL changes in 2.7.14

  [Test plan]
  The vast regression test suite prevents regression in other components. 
Additional tests are:

  1. (promotion to error) Take a repository that has a weak key warning, 
upgrade apt and check that it is an error
  2. (still valid) Check that the main Ubuntu repositories and/or resigned PPAs 
work correctly.

  We don't have any tests for the test changes or the documentation
  translation URL unfuzzying.

  [Where problems could occur]
  apt will start to fail updates of repositories with weak signing keys, but it 
will have warned users about that before. Given that it is still early in the 
cycle, and we only enable updates for 24.04.1, this seems the right tradeoff 
for future security.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/apt/+bug/2060721/+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 2061857] [NEW] [FFe] enable the new GNOME OneDrive backend

2024-04-16 Thread Sebastien Bacher

Public bug reported:

One of the new features of the new GNOME 46 is the support of Microsoft
OneDrive accounts. The code relies on a new library 'msgraph'. The MIR
bug #2060035 just got approved and such we would like to turn on the
option now in Noble.

The changes are in

- gnome-online-accounts, adding a new provider for OneDrive

The package with the change has been built in the desktop ppa
https://launchpad.net/~ubuntu-desktop/+archive/ubuntu/ppa/+sourcepub/15971851/+listing-archive-extra

The change is basically adding the libmsgraph-dev Build-Depends in
debian/control and changing the option to true in debian/rules

- gvfs, adding a new backend to be able to browse those locations from
nautilus

The package is similar built in our ppa
https://launchpad.net/~ubuntu-desktop/+archive/ubuntu/ppa/+sourcepub/15972025/+listing-archive-extra

And the change are similar Build-Depends/rules option


The regression potential is low since those are new backends and not changing 
existing features.

** Affects: gnome-online-accounts (Ubuntu)
 Importance: Undecided
 Status: New

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

** Also affects: gvfs (Ubuntu)
   Importance: Undecided
   Status: New

** Summary changed:

- [FFe] enable the new OneDrive backend
+ [FFe] enable the new GNOME OneDrive backend

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

Title:
  [FFe] enable the new GNOME OneDrive backend

Status in gnome-online-accounts package in Ubuntu:
  New
Status in gvfs package in Ubuntu:
  New

Bug description:
  One of the new features of the new GNOME 46 is the support of
  Microsoft OneDrive accounts. The code relies on a new library
  'msgraph'. The MIR bug #2060035 just got approved and such we would
  like to turn on the option now in Noble.

  The changes are in

  - gnome-online-accounts, adding a new provider for OneDrive

  The package with the change has been built in the desktop ppa
  
https://launchpad.net/~ubuntu-desktop/+archive/ubuntu/ppa/+sourcepub/15971851/+listing-archive-extra

  The change is basically adding the libmsgraph-dev Build-Depends in
  debian/control and changing the option to true in debian/rules

  - gvfs, adding a new backend to be able to browse those locations from
  nautilus

  The package is similar built in our ppa
  
https://launchpad.net/~ubuntu-desktop/+archive/ubuntu/ppa/+sourcepub/15972025/+listing-archive-extra

  And the change are similar Build-Depends/rules option

  
  The regression potential is low since those are new backends and not changing 
existing features.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-online-accounts/+bug/2061857/+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 2036358] Re: systemd wait-online now times out after jammy and lunar upgrade

2024-04-16 Thread bam

Got it on mantic -> noble upgrade too, the solution proposed in the Description 
helped:
 
$ systemctl disable --now systemd-networkd.service

-- 
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/2036358

Title:
  systemd wait-online now times out after jammy and lunar upgrade

Status in systemd package in Ubuntu:
  Invalid
Status in systemd source package in Jammy:
  Fix Released
Status in systemd source package in Lunar:
  Fix Released

Bug description:
  [NOTE]

  If you are running a desktop system and you see this issue, you should
  run:

  $ systemctl disable --now systemd-networkd.service

  This will disable systemd-networkd and associated units, including
  systemd-networkd-wait-online.service. NetworkManager and systemd-
  networkd should not be running at the same time. On desktop,
  NetworkManager is the default network stack.

  [Impact]

  When all interfaces are "not required for online", e.g. when they are
  marked "optional: true" in netplan, systemd-networkd-wait-online will
  timeout. Or, in other words, systemd-networkd-wait-online will timeout
  even though all interfaces are ignored, hence none of them will ever
  be marked as "ready." Depending on what units depend on network-
  online.target, this can delay boot by 120 seconds (the default timeout
  for systemd-networkd-wait-online).

  [Test Plan]

  1. Create a new LXD container. These instructions assume jammy is the
  release, but the same can be done for lunar.

  $ lxc launch ubuntu-daily:jammy jammy
  $ lxc exec jammy bash

  2. Once in the container, modify the default /etc/netplan/10-lxc.yaml
  so that eth0 is configured with "optional: true":

  $ vi /etc/netplan/50-cloud-init.yaml # Use whatever editor you like
  $ cat /etc/netplan/50-cloud-init.yaml
  network:
    version: 2
    ethernets:
  eth0:
    dhcp4: true
    dhcp-identifier: mac
    optional: true

  3. Re-generate and apply the netplan configuration.

  $ netplan generate
  $ netplan apply

  4. Manually run systemd-networkd-wait-online, and observe that all
  links are ignored, and the command times out:

  $ SYSTEMD_LOG_LEVEL=debug /lib/systemd/systemd-networkd-wait-online 
--timeout=10
  Found link lo(1)
  Found link eth0(19)
  lo: link is ignored
  eth0: link is ignored
  Timeout occurred while waiting for network connectivity.

  [Where problems could occur]

  This patch partially re-instates a patch remove in bug 1982218.
  However, instead of exiting if all links are unmanaged, we exit if all
  links are ignored in manager_configured(). If the patch was wrong, we
  may re-introduce bug 1982218, so as part of this SRU verification,
  that bug should be tested too. Any other regressions would also be
  related to systemd-networkd-wait-online behavior.

  [Original Description]

  On Ubuntu 22.04 desktop system using network-manager and upgrading to
  systemd 249.11-0ubuntu3.10, wait-online now times out which prevents
  logins (GDM, ssh, console) until it does time out. This seems to be
  introduced by the change for
  https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1982218.

  https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1982218/comments/21
  also mentioned the problem on Lunar.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/2036358/+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 1568094] Re: Many error message such as "Start request repeated too quickly."

** No longer affects: laptop-mode-tools (Ubuntu)

** Changed in: laptop-mode-tools (Ubuntu Xenial)
   Status: New => Fix Released

-- 
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/1568094

Title:
  Many error message such as "Start request repeated too quickly."

Status in systemd package in Ubuntu:
  Fix Released
Status in laptop-mode-tools source package in Xenial:
  Fix Released
Status in systemd source package in Xenial:
  Fix Released

Bug description:
  * Analysis:

  The error messages are caused by a bad interaction between systemd and
  laptop-mode-tools.

  * Fixes:

  There is a fix in systemd:
  https://github.com/systemd/systemd/pull/3148

  The problem can also be fixed by updating laptop-mode-tools.

  * Symptoms:

  Apr 08 20:23:50 xeelee systemd[1]: systemd-binfmt.service: Start request 
repeated too quickly.
  Apr 08 20:23:50 xeelee systemd[1]: Failed to start Set Up Additional Binary 
Formats.
  Apr 08 20:23:50 xeelee systemd[1]: friendly-recovery.service: Start request 
repeated too quickly.
  Apr 08 20:23:50 xeelee systemd[1]: Failed to start Recovery mode menu.
  Apr 08 20:23:50 xeelee systemd[1]: sys-kernel-config.mount: Start request 
repeated too quickly.
  Apr 08 20:23:50 xeelee systemd[1]: Failed to mount Configuration File System.
  Apr 08 20:23:50 xeelee systemd[1]: systemd-fsck-root.service: Start request 
repeated too quickly.
  Apr 08 20:23:50 xeelee systemd[1]: Failed to start File System Check on Root 
Device.
  Apr 08 20:23:50 xeelee systemd[1]: Started Show Plymouth Boot Screen.
  Apr 08 20:23:50 xeelee systemd[1]: systemd-hwdb-update.service: Start request 
repeated too quickly.
  Apr 08 20:23:50 xeelee systemd[1]: Failed to start Rebuild Hardware Database.
  Apr 08 20:23:50 xeelee systemd[1]: systemd-binfmt.service: Start request 
repeated too quickly.
  Apr 08 20:23:50 xeelee systemd[1]: Failed to start Set Up Additional Binary 
Formats.
  Apr 08 20:23:50 xeelee systemd[1]: Starting Show Plymouth Boot Screen...
  Apr 08 20:23:50 xeelee systemd[1]: friendly-recovery.service: Start request 
repeated too quickly.
  Apr 08 20:23:50 xeelee systemd[1]: Failed to start Recovery mode menu.
  Apr 08 20:23:50 xeelee systemd[1]: systemd-fsck-root.service: Start request 
repeated too quickly.
  Apr 08 20:23:50 xeelee systemd[1]: Failed to start File System Check on Root 
Device.
  Apr 08 20:23:50 xeelee systemd[1]: sys-kernel-config.mount: Start request 
repeated too quickly.
  Apr 08 20:23:50 xeelee systemd[1]: Failed to mount Configuration File System.
  Apr 08 20:23:50 xeelee systemd[1]: systemd-binfmt.service: Start request 
repeated too quickly.
  Apr 08 20:23:50 xeelee systemd[1]: Failed to start Set Up Additional Binary 
Formats.
  Apr 08 20:23:50 xeelee systemd[1]: systemd-hwdb-update.service: Start request 
repeated too quickly.
  Apr 08 20:23:50 xeelee systemd[1]: Failed to start Rebuild Hardware Database.
  Apr 08 20:23:50 xeelee systemd[1]: friendly-recovery.service: Start request 
repeated too quickly.
  Apr 08 20:23:50 xeelee systemd[1]: Failed to start Recovery mode menu.
  Apr 08 20:23:50 xeelee systemd[1]: systemd-fsck-root.service: Start request 
repeated too quickly.
  Apr 08 20:23:50 xeelee systemd[1]: Failed to start File System Check on Root 
Device.
  Apr 08 20:23:50 xeelee systemd[1]: sys-kernel-config.mount: Start request 
repeated too quickly.
  Apr 08 20:23:50 xeelee systemd[1]: Failed to mount Configuration File System.
  Apr 08 20:23:50 xeelee systemd[1]: Started Show Plymouth Boot Screen.
  Apr 08 20:23:50 xeelee systemd[1]: friendly-recovery.service: Start request 
repeated too quickly.
  Apr 08 20:23:50 xeelee systemd[1]: Failed to start Recovery mode menu.
  Apr 08 20:23:50 xeelee systemd[1]: systemd-fsck-root.service: Start request 
repeated too quickly.
  Apr 08 20:23:50 xeelee systemd[1]: Failed to start File System Check on Root 
Device.
  Apr 08 20:23:50 xeelee systemd[1]: systemd-hwdb-update.service: Start request 
repeated too quickly.
  Apr 08 20:23:50 xeelee systemd[1]: Failed to start Rebuild Hardware Database.
  Apr 08 20:23:50 xeelee systemd[1]: sys-kernel-config.mount: Start request 
repeated too quickly.
  Apr 08 20:23:50 xeelee systemd[1]: Failed to mount Configuration File System.
  Apr 08 20:23:50 xeelee systemd[1]: systemd-binfmt.service: Start request 
repeated too quickly.
  Apr 08 20:23:50 xeelee systemd[1]: Failed to start Set Up Additional Binary 
Formats.
  Apr 08 20:23:50 xeelee systemd[1]: plymouth-start.service: Start request 
repeated too quickly.
  Apr 08 20:23:50 xeelee systemd[1]: Failed to start Show Plymouth Boot Screen.
  Apr 08 20:23:50 xeelee systemd[1]: systemd-ask-password-console.path: Start 
request repeated too quickly.
  Apr 08 20:23:50 xeelee systemd[1]: Failed to start Dispatch Password Requests 
to Console Directory Watch.
  Apr 08 20:23:50 xeelee systemd[1]:

[Touch-packages] [Bug 2036358] Re: systemd wait-online now times out after jammy and lunar upgrade

2024-04-16 Thread bam

Got it on mantic -> noble upgrade too, the solution proposed in the Description 
helped:
 
$ systemctl disable --now systemd-networkd.service

-- 
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/2036358

Title:
  systemd wait-online now times out after jammy and lunar upgrade

Status in systemd package in Ubuntu:
  Invalid
Status in systemd source package in Jammy:
  Fix Released
Status in systemd source package in Lunar:
  Fix Released

Bug description:
  [NOTE]

  If you are running a desktop system and you see this issue, you should
  run:

  $ systemctl disable --now systemd-networkd.service

  This will disable systemd-networkd and associated units, including
  systemd-networkd-wait-online.service. NetworkManager and systemd-
  networkd should not be running at the same time. On desktop,
  NetworkManager is the default network stack.

  [Impact]

  When all interfaces are "not required for online", e.g. when they are
  marked "optional: true" in netplan, systemd-networkd-wait-online will
  timeout. Or, in other words, systemd-networkd-wait-online will timeout
  even though all interfaces are ignored, hence none of them will ever
  be marked as "ready." Depending on what units depend on network-
  online.target, this can delay boot by 120 seconds (the default timeout
  for systemd-networkd-wait-online).

  [Test Plan]

  1. Create a new LXD container. These instructions assume jammy is the
  release, but the same can be done for lunar.

  $ lxc launch ubuntu-daily:jammy jammy
  $ lxc exec jammy bash

  2. Once in the container, modify the default /etc/netplan/10-lxc.yaml
  so that eth0 is configured with "optional: true":

  $ vi /etc/netplan/50-cloud-init.yaml # Use whatever editor you like
  $ cat /etc/netplan/50-cloud-init.yaml
  network:
    version: 2
    ethernets:
  eth0:
    dhcp4: true
    dhcp-identifier: mac
    optional: true

  3. Re-generate and apply the netplan configuration.

  $ netplan generate
  $ netplan apply

  4. Manually run systemd-networkd-wait-online, and observe that all
  links are ignored, and the command times out:

  $ SYSTEMD_LOG_LEVEL=debug /lib/systemd/systemd-networkd-wait-online 
--timeout=10
  Found link lo(1)
  Found link eth0(19)
  lo: link is ignored
  eth0: link is ignored
  Timeout occurred while waiting for network connectivity.

  [Where problems could occur]

  This patch partially re-instates a patch remove in bug 1982218.
  However, instead of exiting if all links are unmanaged, we exit if all
  links are ignored in manager_configured(). If the patch was wrong, we
  may re-introduce bug 1982218, so as part of this SRU verification,
  that bug should be tested too. Any other regressions would also be
  related to systemd-networkd-wait-online behavior.

  [Original Description]

  On Ubuntu 22.04 desktop system using network-manager and upgrading to
  systemd 249.11-0ubuntu3.10, wait-online now times out which prevents
  logins (GDM, ssh, console) until it does time out. This seems to be
  introduced by the change for
  https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1982218.

  https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1982218/comments/21
  also mentioned the problem on Lunar.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/2036358/+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 1446865] Re: KDE5/Qt5 does not support session restoration

** No longer affects: qt

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

Title:
  KDE5/Qt5 does not support session restoration

Status in KDE Base Workspace:
  Fix Released
Status in plasma-workspace package in Ubuntu:
  Fix Released
Status in qtbase-opensource-src package in Ubuntu:
  Fix Released

Bug description:
  KDE5/Qt5 does not support proper session restoration.

  ProblemType: Bug
  DistroRelease: Ubuntu 15.10

To manage notifications about this bug go to:
https://bugs.launchpad.net/kdebase-workspace/+bug/1446865/+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 2060721] Re: APT 2.8.0: Promote weak key warnings to errors

2024-04-16 Thread Julian Andres Klode

** Tags added: block-proposed block-proposed-noble

** Tags removed: block-proposed-noble

** Description changed:

+ ⚠️ Only land this in the release pocket after PPAs have been resigned
+ 
  (This bumps the apt version to 2.8.0. APT uses the odd/even number
  system, with 2.7.x being the development series for 2.8, and this is the
  only change left for the 2.8 release, safe for some minor
  translation/test suite improvements)
  
  (This will be uploaded after the beta and may be released before noble
  release, as a zero day SRU or within the weeks following the release)
  
  [Impact]
  APT is currently just warning about keys that it should be rejecting to give 
Launchpad time to resign PPAs. This needs to be bumped to an error such that 
the crypto policy is fully implemented and we only trust keys that are still 
being trusted. #2055193
  
  A warning provides some help right now to third-parties to fix their
  repositories, but it's not *safe*: A repository could have multiple
  signing keys and be signed by a good key now, then later, a previous key
  still in trusted.gpg.d could be revoked and we'd degrade to warnings,
  which, given that we update in the background automatically, the user
  may not see.
  
  Other fixes:
  - The test suite has been made less flaky in two places
  - Documentation translation has been unfuzzied for URL changes in 2.7.14
  
  [Test plan]
  The vast regression test suite prevents regression in other components. 
Additional tests are:
  
  1. (promotion to error) Take a repository that has a weak key warning, 
upgrade apt and check that it is an error
  2. (still valid) Check that the main Ubuntu repositories and/or resigned PPAs 
work correctly.
  
  We don't have any tests for the test changes or the documentation
  translation URL unfuzzying.
  
  [Where problems could occur]
  apt will start to fail updates of repositories with weak signing keys, but it 
will have warned users about that before. Given that it is still early in the 
cycle, and we only enable updates for 24.04.1, this seems the right tradeoff 
for future security.

-- 
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/2060721

Title:
  APT 2.8.0: Promote weak key warnings to errors

Status in apt package in Ubuntu:
  New
Status in apt source package in Noble:
  New

Bug description:
  ⚠️ Only land this in the release pocket after PPAs have been resigned

  (This bumps the apt version to 2.8.0. APT uses the odd/even number
  system, with 2.7.x being the development series for 2.8, and this is
  the only change left for the 2.8 release, safe for some minor
  translation/test suite improvements)

  (This will be uploaded after the beta and may be released before noble
  release, as a zero day SRU or within the weeks following the release)

  [Impact]
  APT is currently just warning about keys that it should be rejecting to give 
Launchpad time to resign PPAs. This needs to be bumped to an error such that 
the crypto policy is fully implemented and we only trust keys that are still 
being trusted. #2055193

  A warning provides some help right now to third-parties to fix their
  repositories, but it's not *safe*: A repository could have multiple
  signing keys and be signed by a good key now, then later, a previous
  key still in trusted.gpg.d could be revoked and we'd degrade to
  warnings, which, given that we update in the background automatically,
  the user may not see.

  Other fixes:
  - The test suite has been made less flaky in two places
  - Documentation translation has been unfuzzied for URL changes in 2.7.14

  [Test plan]
  The vast regression test suite prevents regression in other components. 
Additional tests are:

  1. (promotion to error) Take a repository that has a weak key warning, 
upgrade apt and check that it is an error
  2. (still valid) Check that the main Ubuntu repositories and/or resigned PPAs 
work correctly.

  We don't have any tests for the test changes or the documentation
  translation URL unfuzzying.

  [Where problems could occur]
  apt will start to fail updates of repositories with weak signing keys, but it 
will have warned users about that before. Given that it is still early in the 
cycle, and we only enable updates for 24.04.1, this seems the right tradeoff 
for future security.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/apt/+bug/2060721/+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 2061849] Re: Segmentation fault when calling standard library functions via `print` or `call` while debugging a `main()` function that accepts arguments

2024-04-16 Thread Aaron Rainbolt

This does NOT occur on Noble. Trying it there, the following happens
(note that I allowed debuginfod to be used but I'm not sure if that
makes any difference):

```
(gdb) print strlen(statstr)
'strlen' has unknown return type; cast the call to its declared return type
(gdb) print (size_t)strlen(statstr)
$1 = 12
```

However, attempting to use `print (size_t)strlen(statstr)` under Jammy
still segfaults.

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

Title:
  Segmentation fault when calling standard library functions via `print`
  or `call` while debugging a `main()` function that accepts arguments

Status in gdb package in Ubuntu:
  New
Status in gdb source package in Jammy:
  New

Bug description:
  Steps to reproduce:

  1: Create a file `test.c` with the following very simple program:

  #include   /* for printf */
  #include  /* for strlen */

  int main(int argc, char **argv) {
  const char *statstr = "hello there!";
  printf("%s\n", statstr);
  }

  2: Save this file and compile it with `gcc -g test.c`.
  3: Debug it with `gdb a.out`.
  4: Run `b test.c:6` to set a breakpoint on the printf call.
  5: Run `r` to start the program.
  6: Run `print strlen(statstr)` to attempt to get the length of the statstr 
string.

  Expected result: The length of the string should be printed like so:
  `$1 = 12`

  Actual result: gdb segfaults.

  Segfault backtrace and info:

  ```
  (gdb) print strlen(statstr)

  
  Fatal signal: Segmentation fault
  - Backtrace -
  0x5ac45237f077 ???
  0x5ac452481859 ???
  0x5ac452481a22 ???
  0x72ec6204251f ???
  ./signal/../sysdeps/unix/sysv/linux/x86_64/libc_sigaction.c:0
  0x5ac45232f020 ???
  0x5ac4524d6637 ???
  0x5ac45247f24a ???
  0x5ac45247b827 ???
  0x5ac45259e79f ???
  0x5ac45259ecef ???
  0x5ac4523b4654 ???
  0x5ac4526aa394 ???
  0x5ac4524829a4 ???
  0x5ac452482d43 ???
  0x5ac4524834c6 ???
  0x72ec633a7e0d ???
  0x5ac452481a95 ???
  0x5ac452483374 ???
  0x5ac45248168b ???
  0x5ac452833815 ???
  0x5ac452833caa ???
  0x5ac45253f36c ???
  0x5ac452541054 ???
  0x5ac4522d715f ???
  0x72ec62029d8f __libc_start_call_main
  ../sysdeps/nptl/libc_start_call_main.h:58
  0x72ec62029e3f __libc_start_main_impl
  ../csu/libc-start.c:392
  0x5ac4522dcbf4 ???
  0x ???
  -
  A fatal error internal to GDB has been detected, further
  debugging is not possible.  GDB will now terminate.

  This is a bug, please report it.  For instructions, see:
  .

  Segmentation fault (core dumped)
  ```

  Additional info:

  * You can create a function inside `test.c` that accepts a string as input 
and returns the result of running `strlen` on it. Calling that function via 
`print len(statstr)` does NOT segfault, but behaves as expected.
  * If you remove the `int argc, char **argv` from the `main()` function's 
argument list, calling `strlen(statstr)` in step 6 does NOT segfault, but 
behaves as expected.

  ProblemType: Bug
  DistroRelease: Ubuntu 22.04
  Package: gdb 12.1-0ubuntu1~22.04
  ProcVersionSignature: Ubuntu 6.5.0-25.25~22.04.1-generic 6.5.13
  Uname: Linux 6.5.0-25-generic x86_64
  ApportVersion: 2.20.11-0ubuntu82.5
  Architecture: amd64
  CasperMD5CheckResult: unknown
  CurrentDesktop: KDE
  Date: Tue Apr 16 09:51:33 2024
  InstallationDate: Installed on 2024-03-30 (17 days ago)
  InstallationMedia: Kubuntu 22.04.3 LTS "Jammy Jellyfish" (20231113)
  SourcePackage: gdb
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gdb/+bug/2061849/+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 1847493] Re: recentmanager crashed with signal 5 in _g_log_abort()

This bug seems to be fixed in Ubuntu noble.
Thanks!

** Package changed: gtk+3.0 (Ubuntu) => ubuntu

** Changed in: ubuntu
   Status: New => Fix Released

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

Title:
  recentmanager crashed with signal 5 in _g_log_abort()

Status in Ubuntu:
  Fix Released

Bug description:
  recentmanager crashed while I was running gnome-desktop-testing-runner

  ProblemType: Crash
  DistroRelease: Ubuntu 19.10
  Package: gtk-3-examples 3.24.12-1ubuntu1
  Uname: Linux 5.3.5-050305-generic x86_64
  ApportVersion: 2.20.11-0ubuntu7
  Architecture: amd64
  CurrentDesktop: KDE
  Date: Wed Oct  9 11:44:28 2019
  ExecutablePath: /usr/libexec/installed-tests/gtk+/recentmanager
  ProcCmdline: /usr/libexec/installed-tests/gtk+/recentmanager --tap
  Signal: 5
  SourcePackage: gtk+3.0
  StacktraceTop:
   _g_log_abort (breakpoint=1) at ../../../glib/gmessages.c:554
   g_log_writer_default (log_level=18, log_level@entry=G_LOG_LEVEL_WARNING, 
fields=fields@entry=0x7ffd694bb840, n_fields=n_fields@entry=6, 
user_data=user_data@entry=0x0) at ../../../glib/gmessages.c:2694
   g_log_structured_array (n_fields=6, fields=0x7ffd694bb840, 
log_level=G_LOG_LEVEL_WARNING) at ../../../glib/gmessages.c:1925
   g_log_structured_array (log_level=G_LOG_LEVEL_WARNING, 
fields=0x7ffd694bb840, n_fields=6) at ../../../glib/gmessages.c:1898
   g_log_structured_standard (log_domain=log_domain@entry=0x7f4c5831c047 "Gtk", 
log_level=log_level@entry=G_LOG_LEVEL_WARNING, file=file@entry=0x7f4c58379b60 
"../../../../gtk/gtkrecentmanager.c", line=, func=, message_format=) at ../../../glib/gmessages.c:1982
  Title: recentmanager crashed with signal 5 in _g_log_abort()
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip fuse kvm libvirt libvirt-qemu libvirtd lpadmin 
plugdev sambashare staff sudo
  separator:

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+bug/1847493/+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 2044129] Re: ubuntu-bug does not allow for reporting a bug in "other software" manually giving a symptom description

** Changed in: apport
Milestone: 2.28.1 => None

-- 
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/2044129

Title:
  ubuntu-bug does not allow for reporting a bug in "other software"
  manually giving a symptom description

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

Bug description:
  the man page of ubuntu-bug/apport-bug (what is the difference? why am
  I shown the manpage of apport-bug when typing man ubuntu-bug?) says
  running apport-bug without arguments results in showing me a list of
  symptoms.

  When I try to report a bug in some general program that is not related
  to the other 9 categories - which is most of the 1 apps in Ubuntu
  - I must chose "Other Problem" - but in contrary to the man page that
  tells me I am asked about further things, I only get "You need to
  specific the pakacge or PID".

  I currently try to report a bug in the things that identifies itself
  as "Ubuntu Software" in the Dock, but I have no idea what its correct
  program or package name is, and have no idea how to find that. In PS
  there is no process with "ubuntu" or "software" in its name.

  ProblemType: Bug
  DistroRelease: Ubuntu 23.10
  Package: apport 2.27.0-0ubuntu5
  ProcVersionSignature: Ubuntu 6.2.0-1015.15-lowlatency 6.2.16
  Uname: Linux 6.2.0-1015-lowlatency x86_64
  ApportVersion: 2.27.0-0ubuntu5
  Architecture: amd64
  CasperMD5CheckResult: pass
  CurrentDesktop: ubuntu:GNOME
  Date: Tue Nov 21 14:38:42 2023
  InstallationDate: Installed on 2023-08-21 (92 days ago)
  InstallationMedia: Ubuntu 23.04 "Lunar Lobster" - Release amd64 (20230418)
  PackageArchitecture: all
  ProcEnviron:
   LANG=en_US.UTF-8
   PATH=(custom, no user)
   SHELL=/bin/bash
   TERM=xterm-256color
   XDG_RUNTIME_DIR=
  RebootRequiredPkgs: Error: path contained symlinks.
  SourcePackage: apport
  UpgradeStatus: Upgraded to mantic on 2023-11-05 (16 days ago)

To manage notifications about this bug go to:
https://bugs.launchpad.net/apport/+bug/2044129/+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 1899749] Re: Please add DCCP to rarely used protocols

** Tags added: noble

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

Title:
  Please add DCCP to rarely used protocols

Status in kmod package in Ubuntu:
  New

Bug description:
  Hi,

  according to this message:

https://www.openwall.com/lists/oss-security/2020/10/13/7

  the DCCP protocol may be used as an attack vector to the kernel.

  So could you please add it to /etc/modprobe.d/blacklist-rare-
  network.conf ?

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: kmod 27-1ubuntu2
  Uname: Linux 5.8.14-050814-generic x86_64
  ApportVersion: 2.20.11-0ubuntu27.10
  Architecture: amd64
  CasperMD5CheckResult: skip
  CurrentDesktop: KDE
  Date: Wed Oct 14 10:21:37 2020
  SourcePackage: kmod
  UpgradeStatus: No upgrade log present (probably fresh install)
  mtime.conffile..etc.modprobe.d.blacklist-rare-network.conf: 
2020-10-14T10:21:22.472169

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/kmod/+bug/1899749/+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 2061849] [NEW] Segmentation fault when calling standard library functions via `print` or `call` while debugging a `main()` function that accepts arguments

2024-04-16 Thread Aaron Rainbolt

Public bug reported:

Steps to reproduce:

1: Create a file `test.c` with the following very simple program:

#include   /* for printf */
#include  /* for strlen */

int main(int argc, char **argv) {
const char *statstr = "hello there!";
printf("%s\n", statstr);
}

2: Save this file and compile it with `gcc -g test.c`.
3: Debug it with `gdb a.out`.
4: Run `b test.c:6` to set a breakpoint on the printf call.
5: Run `r` to start the program.
6: Run `print strlen(statstr)` to attempt to get the length of the statstr 
string.

Expected result: The length of the string should be printed like so: `$1
= 12`

Actual result: gdb segfaults.

Segfault backtrace and info:

```
(gdb) print strlen(statstr)


Fatal signal: Segmentation fault
- Backtrace -
0x5ac45237f077 ???
0x5ac452481859 ???
0x5ac452481a22 ???
0x72ec6204251f ???
./signal/../sysdeps/unix/sysv/linux/x86_64/libc_sigaction.c:0
0x5ac45232f020 ???
0x5ac4524d6637 ???
0x5ac45247f24a ???
0x5ac45247b827 ???
0x5ac45259e79f ???
0x5ac45259ecef ???
0x5ac4523b4654 ???
0x5ac4526aa394 ???
0x5ac4524829a4 ???
0x5ac452482d43 ???
0x5ac4524834c6 ???
0x72ec633a7e0d ???
0x5ac452481a95 ???
0x5ac452483374 ???
0x5ac45248168b ???
0x5ac452833815 ???
0x5ac452833caa ???
0x5ac45253f36c ???
0x5ac452541054 ???
0x5ac4522d715f ???
0x72ec62029d8f __libc_start_call_main
../sysdeps/nptl/libc_start_call_main.h:58
0x72ec62029e3f __libc_start_main_impl
../csu/libc-start.c:392
0x5ac4522dcbf4 ???
0x ???
-
A fatal error internal to GDB has been detected, further
debugging is not possible.  GDB will now terminate.

This is a bug, please report it.  For instructions, see:
.

Segmentation fault (core dumped)
```

Additional info:

* You can create a function inside `test.c` that accepts a string as input and 
returns the result of running `strlen` on it. Calling that function via `print 
len(statstr)` does NOT segfault, but behaves as expected.
* If you remove the `int argc, char **argv` from the `main()` function's 
argument list, calling `strlen(statstr)` in step 6 does NOT segfault, but 
behaves as expected.

ProblemType: Bug
DistroRelease: Ubuntu 22.04
Package: gdb 12.1-0ubuntu1~22.04
ProcVersionSignature: Ubuntu 6.5.0-25.25~22.04.1-generic 6.5.13
Uname: Linux 6.5.0-25-generic x86_64
ApportVersion: 2.20.11-0ubuntu82.5
Architecture: amd64
CasperMD5CheckResult: unknown
CurrentDesktop: KDE
Date: Tue Apr 16 09:51:33 2024
InstallationDate: Installed on 2024-03-30 (17 days ago)
InstallationMedia: Kubuntu 22.04.3 LTS "Jammy Jellyfish" (20231113)
SourcePackage: gdb
UpgradeStatus: No upgrade log present (probably fresh install)

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

** Affects: gdb (Ubuntu Jammy)
 Importance: Undecided
 Status: New


** Tags: amd64 apport-bug jammy

** Also affects: gdb (Ubuntu Jammy)
   Importance: Undecided
   Status: New

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

Title:
  Segmentation fault when calling standard library functions via `print`
  or `call` while debugging a `main()` function that accepts arguments

Status in gdb package in Ubuntu:
  New
Status in gdb source package in Jammy:
  New

Bug description:
  Steps to reproduce:

  1: Create a file `test.c` with the following very simple program:

  #include   /* for printf */
  #include  /* for strlen */

  int main(int argc, char **argv) {
  const char *statstr = "hello there!";
  printf("%s\n", statstr);
  }

  2: Save this file and compile it with `gcc -g test.c`.
  3: Debug it with `gdb a.out`.
  4: Run `b test.c:6` to set a breakpoint on the printf call.
  5: Run `r` to start the program.
  6: Run `print strlen(statstr)` to attempt to get the length of the statstr 
string.

  Expected result: The length of the string should be printed like so:
  `$1 = 12`

  Actual result: gdb segfaults.

  Segfault backtrace and info:

  ```
  (gdb) print strlen(statstr)

  
  Fatal signal: Segmentation fault
  - Backtrace -
  0x5ac45237f077 ???
  0x5ac452481859 ???
  0x5ac452481a22 ???
  0x72ec6204251f ???
  ./signal/../sysdeps/unix/sysv/linux/x86_64/libc_sigaction.c:0
  0x5ac45232f020 ???
  0x5ac4524d6637 ???
  0x5ac45247f24a ???
  0x5ac45247b827 ???
  0x5ac45259e79f ???
  0x5ac45259ecef ???
  0x5ac4523b4654 ???
  0x5ac4526aa394 ???
  0x5ac4524829a4 ???
  0x5ac452482d43 ???
  0x5ac4524834c6 ???
  0x72ec633a7e0d ???
  0x5ac452481a95 ???
  0x5ac452483374 ???
  0x5ac45248168b ???
  0x5ac452833815 ???
  0x5ac452833caa ???
  0x5ac45253f36c ???
  0x5ac452541054 ???
  0x5ac4522d715f ???
  0x72ec62029d8f __libc_start_call_main
  ../sysdeps/nptl/libc_start_call_main.h:58
  0x72ec62029e3f __libc_start_main_impl
  ../csu/libc-start.c:392
  0x5ac4522dcbf4 ???

[Touch-packages] [Bug 2060806] Re: Update gstreamer to 1.24.2

This bug was fixed in the package gst-plugins-bad1.0 - 1.24.2-1ubuntu4

---
gst-plugins-bad1.0 (1.24.2-1ubuntu4) noble; urgency=medium

  * Don't try to build zxing on i386

 -- Jeremy Bícha   Mon, 15 Apr 2024 09:00:06 -0400

** Changed in: gst-plugins-bad1.0 (Ubuntu)
   Status: In Progress => Fix Released

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

Title:
  Update gstreamer to 1.24.2

Status in gst-plugins-bad1.0 package in Ubuntu:
  Fix Released
Status in gst-plugins-good1.0 package in Ubuntu:
  Fix Released

Bug description:
  Yesterday, there was a new bugfix release in the stable 1.24.2 series.
  This bug is to track updates for Ubuntu 24.04 LTS.

  https://gstreamer.freedesktop.org/releases/1.24/#1.24.2

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gst-plugins-bad1.0/+bug/2060806/+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 2055397] Re: netplan/systemd-networkd: route metric not applied to routes to the local subnet

2024-04-16 Thread Ioanna Alifieraki

** Description changed:

+ [SRU TEMPLATE]
+ 
+ [DESCRIPTION]
+ 
  Cloud-init introduced a feature to configure policy routing on AWS EC2 
instances with multiple NICs in
  
https://github.com/canonical/cloud-init/commit/0ca5f31043e2d98eab31a43d9dde9bdaef1435cb
 targeting v24.1.
  
  Cloud-init generates the following netplan config:
  
  ```
  $ cat /etc/netplan/50-cloud-init.yaml
  network:
- ethernets:
- ens5:
- dhcp4: true
- dhcp4-overrides: 
- route-metric: 100
- dhcp6: true
- dhcp6-overrides: *id001
- match:
- macaddress: 0a:c8:ab:90:c2:fb
- set-name: ens5
- ens6:
- dhcp4: true
- dhcp4-overrides:
- route-metric: 200
- use-routes: true
- dhcp6: false
- match:
- macaddress: 0a:c6:55:a1:dc:3b
- routes:
- -   table: 101
- to: 0.0.0.0/0
- via: 192.168.0.1
- -   table: 101
- to: 192.168.0.0/20
- routing-policy:
- -   from: 192.168.10.212
- table: 101
- set-name: ens6
- version: 2
+ ethernets:
+ ens5:
+ dhcp4: true
+ dhcp4-overrides: 
+ route-metric: 100
+ dhcp6: true
+ dhcp6-overrides: *id001
+ match:
+ macaddress: 0a:c8:ab:90:c2:fb
+ set-name: ens5
+ ens6:
+ dhcp4: true
+ dhcp4-overrides:
+ route-metric: 200
+ use-routes: true
+ dhcp6: false
+ match:
+ macaddress: 0a:c6:55:a1:dc:3b
+ routes:
+ -   table: 101
+ to: 0.0.0.0/0
+ via: 192.168.0.1
+ -   table: 101
+ to: 192.168.0.0/20
+ routing-policy:
+ -   from: 192.168.10.212
+ table: 101
+ set-name: ens6
+ version: 2
  ```
  
  Which renders the following systemd-networkd config files:
  
  ```
  $ cat 10-netplan-ens5.link
  [Match]
  MACAddress=0a:c8:ab:90:c2:fb
  
  [Link]
  Name=ens5
  WakeOnLan=off
  
- 
  $ cat 10-netplan-ens5.network
  [Match]
  MACAddress=0a:c8:ab:90:c2:fb
  Name=ens5
  
  [Network]
  DHCP=yes
  LinkLocalAddressing=ipv6
  
  [DHCP]
  RouteMetric=100
  UseMTU=true
  
- 
  $ cat 10-netplan-ens6.link
  [Match]
  MACAddress=0a:c6:55:a1:dc:3b
  
  [Link]
  Name=ens6
  WakeOnLan=off
- 
  
  $ cat 10-netplan-ens6.network
  [Match]
  MACAddress=0a:c6:55:a1:dc:3b
  Name=ens6
  
  [Network]
  DHCP=ipv4
  LinkLocalAddressing=ipv6
  
  [Route]
  Destination=0.0.0.0/0
  Gateway=192.168.0.1
  Table=101
  
  [Route]
  Destination=192.168.0.0/20
  Scope=link
  Table=101
  
  [RoutingPolicyRule]
  From=192.168.10.212
  Table=101
  
  [DHCP]
  RouteMetric=200
  UseMTU=true
  ```
  
  Which configures the instance with the following state in Ubuntu Focal:
  
  ```
  $ ip a
  1: lo:  mtu 65536 qdisc noqueue state UNKNOWN group 
default qlen 1000
- link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00
- inet 127.0.0.1/8 scope host lo
-valid_lft forever preferred_lft forever
- inet6 ::1/128 scope host
-valid_lft forever preferred_lft forever
+ link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00
+ inet 127.0.0.1/8 scope host lo
+    valid_lft forever preferred_lft forever
+ inet6 ::1/128 scope host
+    valid_lft forever preferred_lft forever
  2: ens5:  mtu 9001 qdisc mq state UP group 
default qlen 1000
- link/ether 0a:c8:ab:90:c2:fb brd ff:ff:ff:ff:ff:ff
- inet 192.168.12.94/20 brd 192.168.15.255 scope global dynamic ens5
-valid_lft 2087sec preferred_lft 2087sec
- inet6 2a05:d012:ea0:c500:6d12:2b20:5fef:a502/128 scope global dynamic 
noprefixroute
-valid_lft 440sec preferred_lft 130sec
- inet6 fe80::8c8:abff:fe90:c2fb/64 scope link
-valid_lft forever preferred_lft forever
+ link/ether 0a:c8:ab:90:c2:fb brd ff:ff:ff:ff:ff:ff
+ inet 192.168.12.94/20 brd 192.168.15.255 scope global dynamic ens5
+    valid_lft 2087sec preferred_lft 2087sec
+ inet6 2a05:d012:ea0:c500:6d12:2b20:5fef:a502/128 scope global dynamic 
noprefixroute
+    valid_lft 440sec preferred_lft 130sec
+ inet6 fe80::8c8:abff:fe90:c2fb/64 scope link
+    valid_lft forever preferred_lft forever
  3: ens6:  mtu 9001 qdisc mq state UP group 
default qlen 1000
- link/ether 0a:c6:55:a1:dc:3b brd ff:ff:ff:ff:ff:ff
- inet 192.168.10.212/20 brd 192.168.15.255 scope global dynamic ens6
-valid_lft 2083sec preferred_lft 2083sec
- inet6 fe80::8c6:55ff:fea1:dc3b/64 scope link
-valid_lft forever preferred_lft forever
- 
+ link/ether 0a:c6:55:a1:dc:3b brd ff:ff:ff:ff:ff:ff
+ inet 192.168.10.212/20 brd 192.168.15.255 scope global dynamic ens6
+

[Touch-packages] [Bug 2060898] Re: Trying to install gimp-help-en threatens to install wslu

2024-04-16 Thread Martin Wimpress 

** Changed in: ubuntu-mate-meta (Ubuntu Noble)
   Status: Triaged => In Progress

** Changed in: ubuntu-mate-meta (Ubuntu Noble)
 Assignee: (unassigned) => Martin Wimpress  (flexiondotorg)

** Changed in: ubuntu-mate-meta (Ubuntu Noble)
   Status: In Progress => Fix Committed

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

Title:
  Trying to install gimp-help-en threatens to install wslu

Status in edubuntu-meta package in Ubuntu:
  Fix Released
Status in kubuntu-meta package in Ubuntu:
  Fix Released
Status in lubuntu-meta package in Ubuntu:
  Fix Released
Status in ubuntu-budgie-meta package in Ubuntu:
  Fix Released
Status in ubuntu-mate-meta package in Ubuntu:
  Fix Committed
Status in ubuntu-meta package in Ubuntu:
  Invalid
Status in ubuntustudio-meta package in Ubuntu:
  Fix Released
Status in wslu package in Ubuntu:
  Invalid
Status in edubuntu-meta source package in Noble:
  Fix Released
Status in kubuntu-meta source package in Noble:
  Fix Released
Status in lubuntu-meta source package in Noble:
  Fix Released
Status in ubuntu-budgie-meta source package in Noble:
  Fix Released
Status in ubuntu-mate-meta source package in Noble:
  Fix Committed
Status in ubuntu-meta source package in Noble:
  Invalid
Status in ubuntustudio-meta source package in Noble:
  Fix Released
Status in wslu source package in Noble:
  Invalid

Bug description:
  Filing this against ubuntu-meta since I believe this is a seed problem
  that potentially affects all variants of Ubuntu (flavors or
  otherwise).

  wslu is "a collection of utilities for the Windows 10 Linux Subsystem,
  such as for converting Linux paths to a Windows paths or creating
  Linux application shortcuts on the Windows 10 Desktop." Obviously this
  package should *never* be installed on a desktop or even on most VMs,
  but only within WSL instances. However...

  wslu provides the virtual package www-browser, as one of its features
  is to open links in Windows 10 using the default browser set there.
  This means that if a package depends or recommends www-browser, it may
  attempt to pull in one of several packages, wslu included. In the
  past, this hasn't been a problem because Firefox was present on all
  flavor images, and Firefox provides www-browser as well. However, now
  that Firefox is a Snap, it is possible for Firefox to be installed
  without the firefox transitional apt package being installed. (This is
  the case in a default installation of Kubuntu Noble Beta.) As it turns
  out, Kubuntu Noble Beta ships with *no* packages that provide www-
  browser, meaning that any package that depends on it will have to
  install a new browser.

  Due to some stroke of misfortune, apt is picking wslu out of all
  packages as the package for this use case. Installing gimp-help-en
  will also install www-browser, which results in wslu becoming
  installed.

  wslu causes quite a few problems when installed on a desktop system -
  among them, the syslog is spammed with errors due to the system not in
  fact being a WSL VM, audio breaks in weird ways, and application
  launchers sometimes fail. Why this happens is unclear, but the issues
  appear to resolve once wslu is removed from the system. It is
  therefore probably a good idea to avoid wslu becoming installed on
  accident in this way.

  Probably the best way to resolve this is to ensure that some package
  that provides www-browser is available on every Ubuntu image. This
  could be done via seeding or by adding a package to ubuntu-minimal.
  Alternatively, wslu could be set to no longer provide www-browser,
  though it's unclear if that would break its functionality.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/edubuntu-meta/+bug/2060898/+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 1747499] Re: 98-reboot-required and Interaction with livepatch

2024-04-16 Thread Robie Basak

** Tags added: reboot-required

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

Title:
  98-reboot-required and Interaction with livepatch

Status in unattended-upgrades package in Ubuntu:
  Fix Released
Status in update-notifier package in Ubuntu:
  Fix Released
Status in unattended-upgrades source package in Focal:
  Fix Released
Status in update-notifier source package in Focal:
  Fix Released

Bug description:
  
  [Impact]

   * If a system is using canonical livepatch, has it enabled, and
  patches are applied, it could be confusing for a user to receive a
  "system restart required" messages in the MOTD when logging in.

   * Livepatch is available on LTS releases. Thus, the users can be
  confused following a kernel update on 20.04.

   * The upload prevents update-notifier and unattended-ugprades hooks from 
adding "system restart"-related messages to motd when Livepatch is enabled.
  Livepatch, when enabled, already contributes to the motd message so there is 
no need to have duplicate (and sometimes contradictory) information.

  [Test Plan]

   * how to reproduce the bug:

 1. Install and boot a 20.04 server VM
 2. Make sure it runs a generic kernel (or another flavour that supports 
Livepatch)
 3. Enable Livepatch using the following command:
 $ ua attach # replace  by an actual contract token
 4. Upgrade the kernel (if you are already running the latest available 
kernel update, you can install a different flavour)
 5. Upon logging in again, the motd will show ***System restart required***.

   * other testing appropriate to perform before landing this update:

* Making sure that the patch has no impact when livepatch is not enabled.
* The motd should show ***System restart required*** after upgrading the 
kernel if livepatch is not enabled.

  [Where problems could occur]

   * The change updates a hook script in /etc/kernel/postinst.d/.
  Scripts in this directory are executing when upgrading / installing a
  kernel. If somehow the script is broken, it can prevent dpkg for
  succeeding when upgrading / installing the kernel.

   * If the implementation is wrong, we might end up "losing" the
  ***System restart required*** message when livepatch is disabled

  [Original bug description]

  If a system is using canonical livepatch, has it enabled, and patches
  are applied, it could be confusing for a user to receive a "system
  restart required" messages in the MOTD when logging in.

  That message, when present, is printed by 98-reboot-required which
  essentially just cats /var/run/reboot-required to stdout. That file is
  placed by packages that require a reboot so that they are properly
  used in their updated versions. Examples that come to mind are libc
  and the kernel.

  There is a secondary file that can be created which says which
  packages requested the reboot. That would be /var/run/reboot-
  required.pkgs

  Ideally that script should not print out the reboot required message
  if a) livepatch is installed and enabled; b) the only trigger for the
  reboot is a kernel update.

  For (a), one can use the command "ubuntu-advantage is-livepatch-
  enabled" and check $?. That is in the ubuntu-advantage-tools package.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/unattended-upgrades/+bug/1747499/+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 2017401] Re: Unexpected / unwanted unattended-upgrades behaviour after kernel upgrade when Livepatch enabled

2024-04-16 Thread Robie Basak

** Tags added: reboot-required

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

Title:
  Unexpected / unwanted unattended-upgrades behaviour after kernel
  upgrade when Livepatch enabled

Status in unattended-upgrades package in Ubuntu:
  Confirmed
Status in unattended-upgrades source package in Focal:
  Confirmed
Status in unattended-upgrades source package in Jammy:
  Confirmed

Bug description:
  Following the resolution for bug #1747499, after a kernel upgrade when
  Livepatch is enabled, the current behaviour in unattended-upgrades
  (2.3ubuntu0.2 and later) is not to touch /var/run/reboot-required so
  as not to confuse users with two separate messages calling for a
  restart in motd. This functionality is implemented in the script at
  /etc/kernel/postinst.d/unattended-upgrades.

  While this works as intended in terms of suppressing an extra message
  in motd, it defeats the ability of unattended-upgrades to restart
  automatically with the new kernel, which is reliant on
  /var/run/reboot-required being present.

  This is unexpected / unwanted behaviour in scenarios where a)
  Livepatch is being used to provide fast-response kernel patching; and
  b) Unattended-Upgrade::Automatic-Reboot is set to true, to enable
  automatic reboots during a regular maintenance window. In this case,
  without administrative intervention, the system could never boot into
  the new kernel even though it would be expected to, leaving Livepatch
  to do all the heavy lifting indefinitely, and unnecessarily.

  I believe this counts as a regression caused by the resolution to bug
  #1747499. It also has the potential to be a security threat if
  Livepatch doesn't work comprehensively for a particular kernel flaw,
  and an administrator is reliant on expected behaviour according to
  unattended-upgrades settings.

  Potential options for a fix that come to mind:
  1. Revert to original behaviour in 
/etc/kernel/postinst.d/unattended-upgrades, and change the ***System restart 
required*** message to be less alarming or confusing when the cause is a kernel 
upgrade that's being patched by Livepatch.
  2. Add an extra configuration setting (eg 
Unattended-Upgrade::Automatic-Reboot-After-Livepatch) that triggers a reboot 
when it's 'recommended' by Livepatch, not reliant on the presence of 
/var/run/reboot-required.
  3. Add support in /etc/kernel/postinst.d/unattended-upgrades for an extra 
file somewhere. When present, /var/run/reboot-required is always touched, even 
if Livepatch is enabled.

  (This is my first time reporting a bug in this system, and I apologise
  if I haven't followed the usual descriptive format.)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/unattended-upgrades/+bug/2017401/+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 2060331] Re: add-apt-repository --list not returning any deb822 repositories

2024-04-16 Thread Nathan Teodosio

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

-- 
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/2060331

Title:
  add-apt-repository --list not returning any deb822 repositories

Status in software-properties package in Ubuntu:
  Confirmed

Bug description:
  Recreating the following bug report (#2052851) with a new title per
  Jeremy Bícha's (jbicha) request:

  https://bugs.launchpad.net/ubuntu/+source/software-
  properties/+bug/2052851

  ---

  On Ubuntu 23.10:

  * When adding a PPA, 'add-apt-repository' will add the repository in
  the new deb822 format as a '.sources' file in
  '/etc/apt/sources.list.d'

  * However, 'add-apt-repository --list' cannot see/understand the new
  '.sources' file

  For example, with the flacon ppa
  (https://launchpad.net/~flacon/+archive/ubuntu/ppa):

  1. 'sudo add-apt-repository ppa:flacon/ppa' adds the flacon repo as
  '/etc/apt/sources.list.d/flacon-ubuntu-ppa-mantic.sources'

  2. apt can install and update from the new repo, as expected. you can
  also remove the repo, as expected, by running 'sudo add-apt-repository
  --remove ppa:flacon/ppa'

  3. However, 'add-apt-repository --list' does not list the repo as it
  should. GUI package managers such as Muon and Synaptic also do not see
  the new repo.

  It makes working with packages frustrating, and unfortunately, per
  Julian Andres Klode (juliank), there seems to be no plan to fix the
  broken 'software-properties-common' any time soon. See here:

  https://bugs.launchpad.net/ubuntu/+source/software-
  properties/+bug/2033949

  Also see related issues:

  https://bugs.launchpad.net/ubuntu/+source/ppa-purge/+bug/2036761
  https://bugs.launchpad.net/ubuntu/+source/software-properties/+bug/2037210
  https://bugs.launchpad.net/ubuntu/+source/ubuntu-release-upgrader/+bug/2036288
  https://lists.ubuntu.com/archives/ubuntu-devel/2023-September/042791.html

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/software-properties/+bug/2060331/+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 2061140] Re: dropbear-initramfs package fails to install on Ubuntu 24.04 beta server

2024-04-16 Thread Johan Ehnberg

Indeed, looks like this issue is related to initramfs-tools, be that
through an incompatibility introduced in either.

I tested with the package in Debian Sid dropbear-initramfs (2024.84-1)
and got the same error. Meanwhile, on a Debian Sid install, it works.

Based on the above, I added initramfs-tools as affected package.

** Also affects: initramfs-tools (Ubuntu)
   Importance: Undecided
   Status: New

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

Title:
  dropbear-initramfs package fails to install on Ubuntu 24.04 beta
  server

Status in dropbear package in Ubuntu:
  Confirmed
Status in initramfs-tools package in Ubuntu:
  New

Bug description:
  dropbear-initramfs seems to fail on not figuring out what the root
  device is. This applies both to  autoinstall and manual install and is
  observed on today's beta (ubuntu-24.04-beta-live-server-amd64.iso on
  2024-04-12)

  ubuntu@ubuntu-server:~$ sudo apt install dropbear-initramfs 
  [sudo] password for ubuntu: 
  Reading package lists... Done
  Building dependency tree... Done
  Reading state information... Done
  dropbear-initramfs is already the newest version (2022.83-4).
  0 upgraded, 0 newly installed, 0 to remove and 0 not upgraded.
  1 not fully installed or removed.
  After this operation, 0 B of additional disk space will be used.
  Do you want to continue? [Y/n] 
  Setting up initramfs-tools (0.142ubuntu24) ...
  update-initramfs: deferring update (trigger activated)
  Processing triggers for initramfs-tools (0.142ubuntu24) ...
  update-initramfs: Generating /boot/initrd.img-6.8.0-22-generic
  dropbear: WARNING: Couldn't find ~root, SSH login to initramfs won't work!
  E: /usr/share/initramfs-tools/hooks/dropbear failed with return 1.
  update-initramfs: failed for /boot/initrd.img-6.8.0-22-generic with 1.
  dpkg: error processing package initramfs-tools (--configure):
   installed initramfs-tools package post-installation script subprocess 
returned 
  error exit status 1
  Errors were encountered while processing:
   initramfs-tools
  needrestart is being skipped since dpkg has failed
  E: Sub-process /usr/bin/dpkg returned an error code (1)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/dropbear/+bug/2061140/+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 2059796] Re: Other Software > Remove button doesn't work