date:20231019

[Touch-packages] [Bug 2039340] Re: On upgrade from 23.04 to 23.10, cannot login using Gnome or Ubuntu WM entries

2023-10-19 Thread Anadon

I am unable to feasibly comply with running anything from apport.
Apport uses `#!/usr/bin/python3` instead of `#!/usr/bin/env python3`
across its files, which runs into issues with my Guix installation's
instance of Glibc even when removing all the environmental variables
that allow Guix to hook into the terminal.  Apport must be doing
something clever but not quite clever enough to isolate itself from
potentially broken system components?  In it's place, I'll attach the
crash file.

** Attachment added: "_usr_bin_gnome-shell.120.crash"
   
https://bugs.launchpad.net/ubuntu/+source/apparmor/+bug/2039340/+attachment/5711471/+files/_usr_bin_gnome-shell.120.crash

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

Title:
  On upgrade from 23.04 to 23.10, cannot login using Gnome or Ubuntu WM
  entries

Status in apparmor package in Ubuntu:
  New
Status in gnome-shell package in Ubuntu:
  Incomplete

Bug description:
  Last time I hacked around a bug like this, it had portions in PAM,
  apparmor, Seahorse, and Gnome so this time I'd like someone more
  focused on broad stability to look at things.

  The problem is simple.  Before the upgrade to 23.10, I could log in
  using the "Ubuntu", "Ubuntu on X.org". "Gnome", and "Gnome on X.org"
  WMs.  Now I can't.  I can still login using XFCE and TTY.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/apparmor/+bug/2039340/+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 2039422] Re: Feature request: allow user to check 'Show password' by default in the WiFi password dialogue

2023-10-19 Thread Kitserve

The gnome-shell developers say that they don't even have the checkbox
option. I realise that I didn't state in the original bug report, but
I'm using XFCE via Xubuntu. I have network-manager and network-manager-
gnome installed.

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

Title:
  Feature request: allow user to check 'Show password' by default in the
  WiFi password dialogue

Status in network-manager package in Ubuntu:
  New

Bug description:
  Whenever I connect to a new WiFi network, the password dialogue pops
  up. Every time (and I do mean literally every time), I end up clicking
  on the 'Show password' checkbox to make sure that I got it right. I
  understand the reasoning behind obscuring password fields, but for the
  vast majority of users, a WiFi password is not a personal secret. It's
  known to everyone in the same physical location, and obscuring the
  password is primarily a protection against shoulder surfing. It's
  usually also long and not easily memorable. I would like to request a
  user option to always check the 'Show password' box by default, which
  would initially be set to off (in other words, keeping the current
  behaviour by default, but allowing opt-in).

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/2039422/+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 2039811] Re: Xorg freeze

2023-10-19 Thread Daniel van Vugt

Thank you for taking the time to report this bug and helping to make
Ubuntu better. It sounds like some part of the system has crashed. To
help us find the cause of the crash please follow these steps:

1. Run these commands:
journalctl -b0 > journal.txt
journalctl -b-1 > prevjournal.txt
and attach the resulting text files here.

2. Look in /var/crash for crash files and if found run:
ubuntu-bug YOURFILE.crash
Then tell us the ID of the newly-created bug.

3. If step 2 failed then look at https://errors.ubuntu.com/user/ID where
ID is the content of file /var/lib/whoopsie/whoopsie-id on the machine.
Do you find any links to recent problems on that page? If so then please
send the links to us.

Please take care to avoid attaching .crash files to bugs as we are
unable to process them as file attachments. It would also be a security
risk for yourself.


** Package changed: xorg (Ubuntu) => ubuntu

** Changed in: ubuntu
   Status: New => Incomplete

** Summary changed:

- Xorg freeze
+ Screen freeze

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

Title:
  Screen freeze

Status in Ubuntu:
  Incomplete

Bug description:
  while using google meet with google-chrome and sharing screen it
  happens that the video hangs completely, the audio continues to work,
  if I'm lucky I can restore my desktop using CTRL+ALT+F8 and then
  CTRL+ALT+F2 again, otherwise I need a forced shutdown.

  lsb_release -rd 
  No LSB modules are available.
  Description:  Ubuntu 23.10
  Release:  23.10

  
  apt-cache policy xorg
  xorg:
Installed: 1:7.7+23ubuntu2
Candidate: 1:7.7+23ubuntu2
Version table:
   *** 1:7.7+23ubuntu2 500
  500 http://it.archive.ubuntu.com/ubuntu mantic/main amd64 Packages
  100 /var/lib/dpkg/status

  ProblemType: Bug
  DistroRelease: Ubuntu 23.10
  Package: xorg 1:7.7+23ubuntu2
  ProcVersionSignature: Ubuntu 6.5.0-9.9-generic 6.5.3
  Uname: Linux 6.5.0-9-generic x86_64
  ApportVersion: 2.27.0-0ubuntu5
  Architecture: amd64
  BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
  CasperMD5CheckResult: unknown
  CompositorRunning: None
  CurrentDesktop: ubuntu:GNOME
  Date: Thu Oct 19 15:13:12 2023
  DistUpgraded: 2023-10-14 15:27:57,866 DEBUG Running PostInstallScript: 
'/usr/lib/ubuntu-advantage/upgrade_lts_contract.py'
  DistroCodename: mantic
  DistroVariant: ubuntu
  DkmsStatus:
   virtualbox/7.0.10, 6.2.0-34-generic, x86_64: installed
   virtualbox/7.0.10, 6.5.0-9-generic, x86_64: installed
  EcryptfsInUse: Yes
  ExtraDebuggingInterest: No
  GpuHangFrequency: Several times a day
  GpuHangReproducibility: Seems to happen randomly
  GpuHangStarted: Immediately after installing this version of Ubuntu
  GraphicsCard:
   Intel Corporation Raptor Lake-P [Iris Xe Graphics] [8086:a7a1] (rev 04) 
(prog-if 00 [VGA controller])
 Subsystem: Hewlett-Packard Company Raptor Lake-P [Iris Xe Graphics] 
[103c:8b41]
  InstallationDate: Installed on 2023-10-04 (15 days ago)
  InstallationMedia: Ubuntu 23.04 "Lunar Lobster" - Release amd64 (20230418)
  MachineType: {report['dmi.sys.vendor']} {report['dmi.product.name']}
  ProcEnviron:
   LANG=en_US.UTF-8
   PATH=(custom, no user)
   SHELL=/usr/bin/fish
   TERM=xterm-256color
   XDG_RUNTIME_DIR=
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-6.5.0-9-generic 
root=UUID=0179f596-cd6b-485d-82e8-a9db5d32f999 ro quiet splash vt.handoff=7
  SourcePackage: xorg
  Symptom: display
  Title: Xorg freeze
  UpgradeStatus: Upgraded to mantic on 2023-10-14 (5 days ago)
  dmi.bios.date: 05/30/2023
  dmi.bios.release: 1.8
  dmi.bios.vendor: HP
  dmi.bios.version: V70 Ver. 01.01.08
  dmi.board.name: 8B41
  dmi.board.vendor: HP
  dmi.board.version: KBC Version 51.2B.00
  dmi.chassis.type: 10
  dmi.chassis.vendor: HP
  dmi.ec.firmware.release: 81.43
  dmi.modalias: 
dmi:bvnHP:bvrV70Ver.01.01.08:bd05/30/2023:br1.8:efr81.43:svnHP:pnHPEliteBook86016inchG10NotebookPC:pvr:rvnHP:rn8B41:rvrKBCVersion51.2B.00:cvnHP:ct10:cvr:sku8A452EA#ABZ:
  dmi.product.family: 103C_5336AN HP EliteBook
  dmi.product.name: HP EliteBook 860 16 inch G10 Notebook PC
  dmi.product.sku: 8A452EA#ABZ
  dmi.sys.vendor: HP
  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.115-1
  version.libgl1-mesa-dri: libgl1-mesa-dri 23.2.1-1ubuntu3
  version.libgl1-mesa-glx: libgl1-mesa-glx N/A
  version.xserver-xorg-core: xserver-xorg-core 2:21.1.7-3ubuntu2
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-3
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20210115-1
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 
1:1.0.17-2build1

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


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

[Touch-packages] [Bug 2039252] Re: [needs-packaging] The packages ntp and ntpsec are not equivalent

2023-10-19 Thread Jonathan Ferguson

** Bug watch added: Email to rlaager@debian #
   mailto:rlaa...@debian.org

** Also affects: ntp via
   mailto:rlaa...@debian.org
   Importance: Undecided
   Status: New

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

Title:
  [needs-packaging] The packages ntp and ntpsec are not equivalent

Status in NTP:
  New
Status in ntp package in Ubuntu:
  Confirmed
Status in ntp package in Debian:
  Confirmed

Bug description:
  I recently did an install of Ubuntu 23.04 and then configured ntp as I have 
been doing so for more than 8 years.
  With previous versions of Debian and Ubuntu using the real ntp package, the 
details at https://wiki.ubuntu.com/JonathanFerguson/NTP?action=recall=38 
created the desired results.
  I updated the details at https://wiki.ubuntu.com/JonathanFerguson/NTP with 
the new location of ntp.conf, after restarting I noticed that the resultant 
output was missing requisite details.

  
  Compare the following and the lack of ".MCST." and ".ACST.":

  Original ntp on Apollo-Lake-N3150
  jonathan@Apollo-Lake-N3450:~$ lsb_release -rd
  Description:Ubuntu 22.04.3 LTS
  Release:22.04
  jonathan@Apollo-Lake-N3450:~$ ntpq -p
   remote   refid  st t when poll reach   delay   offset  jitter
  ==
   0.ubuntu.pool.n .POOL.  16 p-   6400.000   +0.000   0.000
   1.ubuntu.pool.n .POOL.  16 p-   6400.000   +0.000   0.000
   2.ubuntu.pool.n .POOL.  16 p-   6400.000   +0.000   0.000
   3.ubuntu.pool.n .POOL.  16 p-   6400.000   +0.000   0.000
   ntp.ubuntu.com  .POOL.  16 p-   6400.000   +0.000   0.000
   ntp.mcast.net   .MCST.  16 M-   6400.000   +0.000   0.000
   ff0e::101   .MCST.  16 M-   6400.000   +0.000   0.000
   ntp.mcast.net   .ACST.  16 a-   6400.000   +0.000   0.000
   ff0e::101   .ACST.  16 a-   6400.000   +0.000   0.000
  *time.cloudflare 10.242.8.77  3 u  469 1024  367  234.691   -0.929  67.380
  +2001-44b8-2100- 42.3.115.79  2 u  581 1024  377  487.209  +55.669  57.154
  +2001-44b8-2100- 4.179.66.17  3 u  215 1024  377  489.637  +57.002  35.399
  jonathan@Apollo-Lake-N3450:~$

  NTPsec on Braswell-N3150
  jonathan@Braswell-N3150:~$ lsb_release -rd
  No LSB modules are available.
  Description:Ubuntu 23.04
  Release:23.04
  jonathan@Braswell-N3150:~$ ntpq -p
   remote   refid  st t when poll reach 
  delay   offset   jitter
  
===
   0.ubuntu.pool.ntp.org   .POOL.  16 p-  2560  
 0.   0.   0.0002
   1.ubuntu.pool.ntp.org   .POOL.  16 p-  2560  
 0.   0.   0.0002
   2.ubuntu.pool.ntp.org   .POOL.  16 p-  2560  
 0.   0.   0.0002
   3.ubuntu.pool.ntp.org   .POOL.  16 p-   640  
 0.   0.   0.0002
  +prod-ntp-5.ntp1.ps5.canonical.com   37.15.221.1892 u  141 1024  367 
383.4932 -19.6895  35.0534
  *time.tfmcloud.au203.35.83.2422 u  325 1024  367 
325.9317  -0.1496  43.0522
  +any.time.nl 133.243.238.243  2 u  158 1024  373 
300.7941 -20.8962 136.1422
  +ntp2.its.waikato.ac.nz  .GPS.1 u  363 1024  377 
356.5361 -18.2740 140.5984
  +2001-44b8-2100-3f00---007b-0004 42.3.115.79  2 u  214 1024  367 
490.3898  28.3416   2.7728
  +tic.ntp.telstra.net 203.35.83.2422 u   13 1024  367 
566.0744 -14.1332   6.0377
  +863xqmprtfqv69pv7nwc.ip6.superloop.au   192.168.1.1  2 u   79 1024  367 
330.2658 -14.3483  16.2172
  +gps-ads.10mrlp.juneks.com.au.PPS.1 u  271 1024  367 
443.4812 -71.8020  44.6332
  +x.ns.gin.ntt.net129.250.35.222   2 u   57 1024  367  
22.4974  41.3055   6.0639
  jonathan@Braswell-N3150:~$

  
  This behaviour will affect the following:
  Ubuntu 22.10, 23.04 and 23.10
  Debian 12, 13 and 14

  NTPsec have documented their reasoning for lacking support.
  https://docs.ntpsec.org/latest/discover.html
  https://docs.ntpsec.org/latest/ntpsec.html
  https://docs.ntpsec.org/latest/assoc.html#broad
  https://docs.ntpsec.org/latest/assoc.html#many

  The issue remains that ntp and ntpsec are not capability equivalent.

  I foresee two means of rectifying this predicament, if NTPsec is going
  to be the default implementation of NTP then ntpsec needs to implement
  all of the capabilities of ntp, or the easier alternative is that the
  real ntp https://www.ntp.org/downloads/ is packaged

[Touch-packages] [Bug 2038650] Re: crash reports not sent to the Error Tracker

2023-10-19 Thread Launchpad Bug Tracker

This bug was fixed in the package apport - 2.26.1-0ubuntu2.1

---
apport (2.26.1-0ubuntu2.1) lunar; urgency=medium

  * d/p/lp2038650: Fix crash reporting when going through the UI (LP:
#2038650)

 -- Simon Chopin   Mon, 16 Oct 2023 17:09:25 +0200

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

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

Title:
  crash reports not sent to the Error Tracker

Status in apport package in Ubuntu:
  Fix Released
Status in apport source package in Lunar:
  Fix Released
Status in apport source package in Mantic:
  Fix Released

Bug description:
  [ Impact ]

  Crash reports aren't sent in when going through the UI, unless the
  user looks at the crash details.

  [ Test Plan ]

  0) Make sure that error reporting is set to manual in the system settings (in 
Privacy screen)
  1) Launch xeyes
  2) pkill -11 xeyes
  3) Click send in the apport dialog. DO NOT look at the details of the report.
  4) ls -lh /var/crash/*xeyes*

  There should be 3 files:

  -rw-r- 1 bdmurray whoopsie  3370567 Oct  6 11:53 _usr_bin_xeyes.1000.crash
  -rw-rw-r-- 1 bdmurray bdmurray0 Oct  6 11:53 
_usr_bin_xeyes.1000.upload
  -rw--- 1 whoopsie whoopsie   37 Oct  6 11:53 
_usr_bin_xeyes.1000.uploaded

  [ Where problems could occur ]

  If the patch is wrong, we actually see similar bugs for other UI
  paths, e.g. ticking the "Remember this" box, etc. I tried to cover
  them during manual testing but I might have missed some.

  [ Other Info ]
   
  If possible I'd like for us not to wait too long for this to mature in 
-proposed, as this would affect crashes during the upgrade.

  [ Original report ]
  From what I can tell when I click the send button to send a crash report to 
the Error Tracker the crash doesn't actually get sent. My testing process 
follows:

  1) Launch xeyes
  2) pkill -11 xeyes
  3) Click send in the apport dialog
  4) ls -lh /var/crash

  I would expect there to be three files in /var/crash:

  -rw-r- 1 bdmurray whoopsie  3370567 Oct  6 11:53 _usr_bin_xeyes.1000.crash
  -rw-rw-r-- 1 bdmurray bdmurray0 Oct  6 11:53 
_usr_bin_xeyes.1000.upload
  -rw--- 1 whoopsie whoopsie   37 Oct  6 11:53 
_usr_bin_xeyes.1000.uploaded

  However, after step #4 I'm only seeing the .crash file and not a
  .upload or .uploaded.  I was able to get the .upload and .uploaded
  files created if I chose to "View Report" and then click "Send".

  It's worth noting though that I did notice the size of the .crash file
  increase after clicking "Send" so some post-processing was done.

  ProblemType: BugDistroRelease: Ubuntu 23.10
  Package: apport 2.27.0-0ubuntu4
  ProcVersionSignature: Ubuntu 6.5.0-5.5-generic 6.5.0
  Uname: Linux 6.5.0-5-generic x86_64
  NonfreeKernelModules: zfs
  ApportVersion: 2.27.0-0ubuntu4
  Architecture: amd64
  CasperMD5CheckResult: pass
  CrashReports: 640:1000:123:20944237:2023-10-06 12:10:47.809248208 
+0100:2023-10-06 12:11:23.340030509 +0100:/var/crash/_usr_bin_mpv.1000.crash
  CurrentDesktop: ubuntu:GNOME
  Date: Fri Oct  6 12:12:46 2023
  InstallationDate: Installed on 2022-01-07 (637 days ago)
  InstallationMedia: Ubuntu 21.10 "Impish Indri" - Release amd64 (20211012)
  PackageArchitecture: allSourcePackage: apport
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/apport/+bug/2038650/+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 2038650] Update Released

2023-10-19 Thread Brian Murray

The verification of the Stable Release Update for apport has completed
successfully and the package is now being released to -updates.
Subsequently, the Ubuntu Stable Release Updates Team is being
unsubscribed and will not receive messages about this bug report.  In
the event that you encounter a regression using the package from
-updates please report a new bug using ubuntu-bug and tag the bug report
regression-update so we can easily find any regressions.

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

Title:
  crash reports not sent to the Error Tracker

Status in apport package in Ubuntu:
  Fix Released
Status in apport source package in Lunar:
  Fix Released
Status in apport source package in Mantic:
  Fix Released

Bug description:
  [ Impact ]

  Crash reports aren't sent in when going through the UI, unless the
  user looks at the crash details.

  [ Test Plan ]

  0) Make sure that error reporting is set to manual in the system settings (in 
Privacy screen)
  1) Launch xeyes
  2) pkill -11 xeyes
  3) Click send in the apport dialog. DO NOT look at the details of the report.
  4) ls -lh /var/crash/*xeyes*

  There should be 3 files:

  -rw-r- 1 bdmurray whoopsie  3370567 Oct  6 11:53 _usr_bin_xeyes.1000.crash
  -rw-rw-r-- 1 bdmurray bdmurray0 Oct  6 11:53 
_usr_bin_xeyes.1000.upload
  -rw--- 1 whoopsie whoopsie   37 Oct  6 11:53 
_usr_bin_xeyes.1000.uploaded

  [ Where problems could occur ]

  If the patch is wrong, we actually see similar bugs for other UI
  paths, e.g. ticking the "Remember this" box, etc. I tried to cover
  them during manual testing but I might have missed some.

  [ Other Info ]
   
  If possible I'd like for us not to wait too long for this to mature in 
-proposed, as this would affect crashes during the upgrade.

  [ Original report ]
  From what I can tell when I click the send button to send a crash report to 
the Error Tracker the crash doesn't actually get sent. My testing process 
follows:

  1) Launch xeyes
  2) pkill -11 xeyes
  3) Click send in the apport dialog
  4) ls -lh /var/crash

  I would expect there to be three files in /var/crash:

  -rw-r- 1 bdmurray whoopsie  3370567 Oct  6 11:53 _usr_bin_xeyes.1000.crash
  -rw-rw-r-- 1 bdmurray bdmurray0 Oct  6 11:53 
_usr_bin_xeyes.1000.upload
  -rw--- 1 whoopsie whoopsie   37 Oct  6 11:53 
_usr_bin_xeyes.1000.uploaded

  However, after step #4 I'm only seeing the .crash file and not a
  .upload or .uploaded.  I was able to get the .upload and .uploaded
  files created if I chose to "View Report" and then click "Send".

  It's worth noting though that I did notice the size of the .crash file
  increase after clicking "Send" so some post-processing was done.

  ProblemType: BugDistroRelease: Ubuntu 23.10
  Package: apport 2.27.0-0ubuntu4
  ProcVersionSignature: Ubuntu 6.5.0-5.5-generic 6.5.0
  Uname: Linux 6.5.0-5-generic x86_64
  NonfreeKernelModules: zfs
  ApportVersion: 2.27.0-0ubuntu4
  Architecture: amd64
  CasperMD5CheckResult: pass
  CrashReports: 640:1000:123:20944237:2023-10-06 12:10:47.809248208 
+0100:2023-10-06 12:11:23.340030509 +0100:/var/crash/_usr_bin_mpv.1000.crash
  CurrentDesktop: ubuntu:GNOME
  Date: Fri Oct  6 12:12:46 2023
  InstallationDate: Installed on 2022-01-07 (637 days ago)
  InstallationMedia: Ubuntu 21.10 "Impish Indri" - Release amd64 (20211012)
  PackageArchitecture: allSourcePackage: apport
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/apport/+bug/2038650/+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 2023545] Re: [UBUNTU 22.04] openssl with ibmca engine configured dumps core when creating a new certificate

2023-10-19 Thread Adrien Nader

Hi Lucas,

Sorry, this is part of an SRU with 4 patches but that we've decided to
hold back for a bit (a few days after the current release). I've removed
ubuntu-sponsors from the "main" LP bug (link near the top of the bug
report) but not from the others. I'll do it now and I think maybe it's
better to only add ~ubuntu-sponsors to that main ticket.

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

Title:
  [UBUNTU 22.04] openssl with ibmca engine configured dumps core when
  creating a new certificate

Status in Ubuntu on IBM z Systems:
  In Progress
Status in openssl package in Ubuntu:
  In Progress
Status in openssl source package in Jammy:
  In Progress
Status in openssl source package in Lunar:
  Fix Released

Bug description:
  === SRU information ===
  [Meta]
  This bug is part of a series of four bugs for a single SRU.
  The "central" bug with the global information and debdiff is 
http://pad.lv/2033422

  [Impact]
  Openssl using an engine dumps core upon certificate creation; other 
operations are probably affected too. Overall, engines are likely mostly 
unusable.

  [Test plan]
  An engine is needed to test the fix and I don't think we have many in the 
archive. This complicates reproducing the issue. I have been relying on user 
reports which have been very detailled and helpful.
  The issue has also been reported independently and with another engine 
(devcrypto).
  The issue is fixed in openssl 3.0.8 which landed in lunar.

  [Where problems could occur]
  I don't pretend to understand the lifecycle of providers in openssl3 but the 
patch is simple and has been widely tested by now, including on ubuntu. Thus, I 
see little chance an unexpected problem would occur with it.

  [Patches]
  The patches come directly from upstream and apply cleanly.

  https://github.com/openssl/openssl/issues/18578

  *
  
https://git.launchpad.net/~adrien-n/ubuntu/+source/openssl/tree/debian/patches/jammy-
  sru-0001-Release-the-drbg-in-the-global-default-context-
  befor.patch?h=jammy-sru=04ef023920ab08fba214817523fba897527dfff0

  === Original description ===

  openssl req -new -newkey rsa:2048 -x509 -sha256 -nodes -out __cert.pem
  -keyout __key.pem --subj '/CN=US'

  ---Problem Description---
  OpenSSL with ibmca engine configured dumps core when creating a new 
certificate.

  # openssl engine
  (dynamic) Dynamic engine loading support
  (ibmca) Ibmca hardware engine support
  # openssl req  -new -newkey rsa:2048 -x509 -sha256 -nodes -out __cert.pem 
-keyout __key.pem --subj '/CN=US'
  Segmentation fault (core dumped)

  # journalctl
  Jun 07 13:06:08 SYSTEM kernel: User process fault: interruption code 003b 
ilc:2 in libc.so.6[3ffae08+1ca000]
  Jun 07 13:06:08 SYSTEM kernel: Failing address:  TEID: 
0800
  Jun 07 13:06:08 SYSTEM kernel: Fault in primary space mode while using user 
ASCE.
  Jun 07 13:06:08 SYSTEM kernel: AS:9c2941c7 R3:0024
  Jun 07 13:06:08 SYSTEM kernel: CPU: 2 PID: 2344 Comm: openssl Kdump: loaded 
Not tainted 5.15.0-73-generic #80-Ubuntu
  Jun 07 13:06:08 SYSTEM kernel: Hardware name: IBM 3931 A01 703 (z/VM 7.3.0)
  Jun 07 13:06:08 SYSTEM kernel: User PSW : 070500018000 03ffae11c708
  Jun 07 13:06:08 SYSTEM kernel:R:0 T:1 IO:1 EX:1 Key:0 M:1 W:0 P:1 
AS:0 CC:0 PM:0 RI:0 EA:3
  Jun 07 13:06:08 SYSTEM kernel: User GPRS: 0007 03ffae11c6f0 
 02aa3289f9d0
  Jun 07 13:06:08 SYSTEM kernel:02aa1825980f 02aa3289f9d0 
 02aa328a4300
  Jun 07 13:06:08 SYSTEM kernel:03ffae870720 03ffae657128 
02aa03ff 
  Jun 07 13:06:08 SYSTEM kernel:03ffae24dd10 03ffae657120 
03ffae437c22 03ffec2fe000
  Jun 07 13:06:08 SYSTEM kernel: User Code: 03ffae11c6fc: b90400b2  
  lgr%r11,%r2
    03ffae11c700: 
4700bc0,0
   #03ffae11c704: 
b24f00a0ear%r10,%a0
   >03ffae11c708: 
58102018l%r1,24(%r2)
    03ffae11c70c: 
ebaa002dsllg%r10,%r10,32
    03ffae11c712: 
b24f00a1ear%r10,%a1
    03ffae11c716: 
5910a0d0c%r1,208(%r10)
    03ffae11c71a: 
a7840033brc8,03ffae11c780
  Jun 07 13:06:08 SYSTEM kernel: Last Breaking-Event-Address:
  Jun 07 13:06:08 SYSTEM kernel:  [<03ffae33242c>] 0x3ffae33242c
  Jun

[Touch-packages] [Bug 2033422] Re: openssl: backport to jammy "clear method store / query cache confusion"

2023-10-19 Thread Adrien Nader

Removed ~ubuntu-sponsors for a few days while a few things settle.

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

Title:
openssl: backport to jammy "clear method store / query cache
confusion"

Status in openssl package in Ubuntu:
New
Status in openssl source package in Jammy:
In Progress
Status in openssl source package in Lunar:
Fix Released

Bug description:
=== SRU information ===
[Meta]
This bug is part of a series of four bugs for a single SRU.
This ( #2033422 ) is the "central" bug with the global information and
debdiff.

This SRU addresses four issues with Jammy's openssl version:
- http://pad.lv/1990216: Blowfish OFB/CFB decryption
- http://pad.lv/1994165: ignored SMIME signature errors
- http://pad.lv/2023545: imbca engine dumps core
- http://pad.lv/2033422: very high CPU usage for concurrent TLS connections

The SRU information has been added to the four bug reports and I am
attaching the debdiff here only for all four.

All the patches have been included in subsequent openssl 3.0.x
releases which in turn have been included in subsequent Ubuntu
releases. There has been no report of issues when updating to these
Ubuntu releases.

I have rebuilt the openssl versions and used abi-compliance-checker to
compare the ABIs of the libraries in jammy and the one for the SRU.
Both matched completely (FYI, mantic's matched completely too).

The patch related to blowfish presents an annoying situation: jammy's openssl
creates incompatible files and cannot read other files but fixing it will lead
to files created on jammy so far to become unreadable. Fortunately, blowfish is
long-deprecated and applications can be improved to handle this situation if
the need arises in practice.
This is stated in the SRU information in the bug and in d/changelog.
The current situation in Jammy could be a security issue but due to the
aforementioned deprecation, the low usage of blowfish and the fact that
upstream didn't consider this worthy of a security notice, we (this includes
the security team) chose not to pursue that path either.

I have also pushed the code to git (without any attempt to make it
git-ubuntu friendly).

https://code.launchpad.net/~adrien-n/ubuntu/+source/openssl/+git/openssl/+ref/jammy-
sru

I asked Brian Murray about phasing speed and he concurs a slow roll-out is
probably better for openssl. There is a small uncertainty because a security
update could come before the phasing is over, effectively fast-forwarding the
SRU. Still, unless there is already a current pre-advisory, this is probably
better than a 10% phasing which is over after only a couple days anyway.
NB: at the moment openssl doesn't phase slowly so this needs to be
implemented.

[Impact]
Severely degraded performance for concurrent operations compared to openssl
1.1. The performance is so degraded that some workloads fail due to timeouts or
insufficient resources (noone magically has 5 times more machines). As a
consequence, a number of people use openssl 1.1 instead and do not get security
updates.

[Test plan]
Rafael Lopez has shared a simple benchmarks in http://pad.lv/2009544 with
https://bugs.launchpad.net/ubuntu/+source/openssl/+bug/2009544/+attachment/5690224/+files/main.py
.
Using this, I get the following numbers on my laptop:

3.0.2:
real 2m5.567s
user 4m3.948s
sys 2m0.233s

this SRU:
real 0m23.966s
user 2m35.687s
sys 0m1.920s

As can be easily seen, the speed-up is massive: system time is divided
by 60 and overall wall clock time is roughly five times lower.

In http://pad.lv/2009544 , Rafael also shared his performance numbers
and they are relatable to these. He used slightly different versions
(upstreams rather than patched with cherry-picks) but at least one of
the version used does not include other performance change. He also
used different hardware and this performance issue seems to depend on
the number of CPUs available but also obtained a performance several
times better. Results on a given machine vary also very little across
runs (less than 2% variation on runs of size 10). They are also very
similar on a Raspberry Pi 4 (8GB).

The benchmark uses https://www.google.com/humans.txt which takes
around 130ms to download on my machine but I modified the script to
download something only 20ms away. Results are so close to the ones
using humans.txt that they are within the error margin. This is
consistent with the high-concurrency in the benchmark which both
saturates CPU, and "hides" latencies that are relatively low.

Finally, there are positive reports on github. Unfortunately they are
not always completely targeted at these patches only and therefore I
will not link directly to them but they have also been

[Touch-packages] [Bug 2038894] Re: Ubuntu 23.10 cloud images unexpected UDP listening port 5353

2023-10-19 Thread Steve Langasek

"no open ports" is the long standing policy for all Ubuntu and is not
just for cloud images. (Even port 22 is not supposed to be open on bare
metal server by default, only as opt in.)

I don't have a link handy at the moment to documentation of this policy
but it IS the policy.

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

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

Title:
  Ubuntu 23.10 cloud images unexpected UDP listening port  5353

Status in cloud-images:
  New
Status in systemd package in Ubuntu:
  New
Status in systemd source package in Mantic:
  New

Bug description:
  [Impact]

  In the latest Ubuntu 23.10 cloud images we are seeing unexpected UDP
  listening port 5353.

  By default and by policy, aside from port 22 there should be no other
  open ports on Ubuntu cloud images. Listening port 5353 is a
  regression.

  [Test Plan]

  Check that port 5353 is not open, and in particular that systemd-
  resolved is not listening on 5353. This is what it looks like when
  systemd-resolved *is* listening on 5353:

  ```
  $ ss --listening --no-header --tcp --udp --numeric
  udp   UNCONN  
 00 

   127.0.0.54:53
0.0.0.0:*
  udp   UNCONN  
 00 

127.0.0.53%lo:53
0.0.0.0:*
  udp   UNCONN  
 00 

 10.154.0.17%ens4:68
0.0.0.0:*
  udp   UNCONN  
 00 

127.0.0.1:323   
0.0.0.0:*
  udp   UNCONN  
 00 

  0.0.0.0:5353  
0.0.0.0:*
  udp   UNCONN  
 00 

[::1]:323   
   [::]:*
  udp   UNCONN  
 00 

 [::]:5353  
   [::]:*
  tcp   LISTEN  
 0
4096
  127.0.0.53%lo:53  
  0.0.0.0:*
  tcp   LISTEN  
 0
4096
 127.0.0.54:53  
  0.0.0.0:*
  tcp   LISTEN  
 0
4096

[Touch-packages] [Bug 2038894] Re: Ubuntu 23.10 cloud images unexpected UDP listening port 5353

2023-10-19 Thread Steve Langasek

The effect of opening a port was a not-understood consequence of
changing the default.

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

Title:
  Ubuntu 23.10 cloud images unexpected UDP listening port  5353

Status in cloud-images:
  New
Status in systemd package in Ubuntu:
  New
Status in systemd source package in Mantic:
  New

Bug description:
  [Impact]

  In the latest Ubuntu 23.10 cloud images we are seeing unexpected UDP
  listening port 5353.

  By default and by policy, aside from port 22 there should be no other
  open ports on Ubuntu cloud images. Listening port 5353 is a
  regression.

  [Test Plan]

  Check that port 5353 is not open, and in particular that systemd-
  resolved is not listening on 5353. This is what it looks like when
  systemd-resolved *is* listening on 5353:

  ```
  $ ss --listening --no-header --tcp --udp --numeric
  udp   UNCONN  
 00 

   127.0.0.54:53
0.0.0.0:*
  udp   UNCONN  
 00 

127.0.0.53%lo:53
0.0.0.0:*
  udp   UNCONN  
 00 

 10.154.0.17%ens4:68
0.0.0.0:*
  udp   UNCONN  
 00 

127.0.0.1:323   
0.0.0.0:*
  udp   UNCONN  
 00 

  0.0.0.0:5353  
0.0.0.0:*
  udp   UNCONN  
 00 

[::1]:323   
   [::]:*
  udp   UNCONN  
 00 

 [::]:5353  
   [::]:*
  tcp   LISTEN  
 0
4096
  127.0.0.53%lo:53  
  0.0.0.0:*
  tcp   LISTEN  
 0
4096
 127.0.0.54:53  
  0.0.0.0:*
  tcp   LISTEN  
 0
4096
  *:22  
*:*
  ```

  ```
  $ sudo lsof -i -n -P
  COMMANDPIDUSER   FD   TYPE DEVICE SIZE/OFF NODE NAME
  systemd  1root  153u

[Touch-packages] [Bug 2023545] Re: [UBUNTU 22.04] openssl with ibmca engine configured dumps core when creating a new certificate

2023-10-19 Thread Lucas Kanashiro

Hi Adrien,

You subscribed ubuntu-sponsors, do you have any debdiff or MP to be
reviewed? Sorry, I did not find anything ready to review. Without that I
believe the best way is to unsubscribe ubuntu-sponsors until there is
something ready to be uploaded.

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

Title:
  [UBUNTU 22.04] openssl with ibmca engine configured dumps core when
  creating a new certificate

Status in Ubuntu on IBM z Systems:
  In Progress
Status in openssl package in Ubuntu:
  In Progress
Status in openssl source package in Jammy:
  In Progress
Status in openssl source package in Lunar:
  Fix Released

Bug description:
  === SRU information ===
  [Meta]
  This bug is part of a series of four bugs for a single SRU.
  The "central" bug with the global information and debdiff is 
http://pad.lv/2033422

  [Impact]
  Openssl using an engine dumps core upon certificate creation; other 
operations are probably affected too. Overall, engines are likely mostly 
unusable.

  [Test plan]
  An engine is needed to test the fix and I don't think we have many in the 
archive. This complicates reproducing the issue. I have been relying on user 
reports which have been very detailled and helpful.
  The issue has also been reported independently and with another engine 
(devcrypto).
  The issue is fixed in openssl 3.0.8 which landed in lunar.

  [Where problems could occur]
  I don't pretend to understand the lifecycle of providers in openssl3 but the 
patch is simple and has been widely tested by now, including on ubuntu. Thus, I 
see little chance an unexpected problem would occur with it.

  [Patches]
  The patches come directly from upstream and apply cleanly.

  https://github.com/openssl/openssl/issues/18578

  *
  
https://git.launchpad.net/~adrien-n/ubuntu/+source/openssl/tree/debian/patches/jammy-
  sru-0001-Release-the-drbg-in-the-global-default-context-
  befor.patch?h=jammy-sru=04ef023920ab08fba214817523fba897527dfff0

  === Original description ===

  openssl req -new -newkey rsa:2048 -x509 -sha256 -nodes -out __cert.pem
  -keyout __key.pem --subj '/CN=US'

  ---Problem Description---
  OpenSSL with ibmca engine configured dumps core when creating a new 
certificate.

  # openssl engine
  (dynamic) Dynamic engine loading support
  (ibmca) Ibmca hardware engine support
  # openssl req  -new -newkey rsa:2048 -x509 -sha256 -nodes -out __cert.pem 
-keyout __key.pem --subj '/CN=US'
  Segmentation fault (core dumped)

  # journalctl
  Jun 07 13:06:08 SYSTEM kernel: User process fault: interruption code 003b 
ilc:2 in libc.so.6[3ffae08+1ca000]
  Jun 07 13:06:08 SYSTEM kernel: Failing address:  TEID: 
0800
  Jun 07 13:06:08 SYSTEM kernel: Fault in primary space mode while using user 
ASCE.
  Jun 07 13:06:08 SYSTEM kernel: AS:9c2941c7 R3:0024
  Jun 07 13:06:08 SYSTEM kernel: CPU: 2 PID: 2344 Comm: openssl Kdump: loaded 
Not tainted 5.15.0-73-generic #80-Ubuntu
  Jun 07 13:06:08 SYSTEM kernel: Hardware name: IBM 3931 A01 703 (z/VM 7.3.0)
  Jun 07 13:06:08 SYSTEM kernel: User PSW : 070500018000 03ffae11c708
  Jun 07 13:06:08 SYSTEM kernel:R:0 T:1 IO:1 EX:1 Key:0 M:1 W:0 P:1 
AS:0 CC:0 PM:0 RI:0 EA:3
  Jun 07 13:06:08 SYSTEM kernel: User GPRS: 0007 03ffae11c6f0 
 02aa3289f9d0
  Jun 07 13:06:08 SYSTEM kernel:02aa1825980f 02aa3289f9d0 
 02aa328a4300
  Jun 07 13:06:08 SYSTEM kernel:03ffae870720 03ffae657128 
02aa03ff 
  Jun 07 13:06:08 SYSTEM kernel:03ffae24dd10 03ffae657120 
03ffae437c22 03ffec2fe000
  Jun 07 13:06:08 SYSTEM kernel: User Code: 03ffae11c6fc: b90400b2  
  lgr%r11,%r2
    03ffae11c700: 
4700bc0,0
   #03ffae11c704: 
b24f00a0ear%r10,%a0
   >03ffae11c708: 
58102018l%r1,24(%r2)
    03ffae11c70c: 
ebaa002dsllg%r10,%r10,32
    03ffae11c712: 
b24f00a1ear%r10,%a1
    03ffae11c716: 
5910a0d0c%r1,208(%r10)
    03ffae11c71a: 
a7840033brc8,03ffae11c780
  Jun 07 13:06:08 SYSTEM kernel: Last Breaking-Event-Address:
  Jun 07 13:06:08 SYSTEM kernel:  [<03ffae33242c>] 0x3ffae33242c
  Jun 07 13:06:08 SYSTEM systemd[1]: Started Process Core Dump (PID 2345/UID 0).
  Jun 07 13:06:08

[Touch-packages] [Bug 1794064] Re: Clicking a hyperlink in a PDF fails to open it if the default browser is a snap

2023-10-19 Thread Georgia Garcia

Hi! You're right, I forgot to request a sponsorship.

I uploaded the patch for evince/jammy, could you take a look and sponsor
if possible? Thanks

** Patch added: "evince_42.3-0ubuntu3.1.debdiff"
   
https://bugs.launchpad.net/ubuntu/+source/evince/+bug/1794064/+attachment/5711419/+files/evince_42.3-0ubuntu3.1.debdiff

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

Title:
  Clicking a hyperlink in a PDF fails to open it if the default browser
  is a snap

Status in apparmor package in Ubuntu:
  Fix Released
Status in evince package in Ubuntu:
  Fix Released
Status in apparmor source package in Jammy:
  Fix Committed
Status in evince source package in Jammy:
  In Progress
Status in apparmor source package in Lunar:
  Fix Released
Status in evince source package in Lunar:
  Fix Released
Status in apparmor package in Debian:
  Fix Released
Status in evince package in Debian:
  Confirmed

Bug description:
  [Impact]

   * Users cannot open a hyperlink in a PDF opened with evince when the default 
browser is a snap.
   * The fix creates a snap_browsers abstraction on AppArmor which can be used 
in a transition for when the browser is executed. The snap_browsers abstraction 
provides the minimal amount of permissions required to execute a browser 
provided through snaps. This is a workaround since AppArmor currently does not 
provide mediation/filtering on enhanced environment variables.

  [Test Plan]

   * Make sure the default browser is provided through the snap store.
   * Open a PDF that contains a hyperlink using evince and click on the URL.
   * The browser should open the requested URL. 

  [Where problems could occur]

   * If the browser or snap core update to have new requirements for
  opening a browser, then the current policy could become obsolete and
  will need to be updated again.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/apparmor/+bug/1794064/+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 2039873] Re: liblxc-dev was built with LXC_DEVEL=1 in Ubuntu Jammy/Kinetic

2023-10-19 Thread Simon Déziel

https://git.launchpad.net/ubuntu/+source/lxc/tree/debian/patches/0003-meson-
Set-DEVEL-flag-post-release.patch is the patch that should be dropped by
the SRU.

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

Title:
liblxc-dev was built with LXC_DEVEL=1 in Ubuntu Jammy/Kinetic

Status in lxc package in Ubuntu:
New

Bug description:
Dear colleagues,

As I can see from:
-
https://git.launchpad.net/ubuntu/+source/lxc/tree/configure?h=applied/ubuntu/jammy
-
https://git.launchpad.net/ubuntu/+source/lxc/tree/configure?h=applied/ubuntu/kinetic

LXC 5.0.0 was built with LXC_DEVEL=1 set. But for release build we
should have LXC_DEVEL=0.

LXC_DEVEL is a variable that appears in the /usr/include/lxc/version.h
and then can be (and actually it is) used by other projects to detect
if liblxc-dev is a development build or stable.

Having LXC_DEVEL=1 makes problems for the users who want to build projects
those are depend on liblxc
from source (for example, LXD, go-lxc:
https://github.com/canonical/lxd/pull/12420).

Q: Why it was not a problem for so long?
A: Because LXC API was stable for a long time, but recently we have extended
liblxc API (https://github.com/lxc/lxc/pull/4260) and dependant package go-lxc
was updated too (https://github.com/lxc/go-lxc/pull/166).
This change was developed properly to be backward compatible with the old
versions of liblxc. But, there is a problem. If LXC_DEVEL=1 then the macro
check VERSION_AT_LEAST
(https://github.com/lxc/go-lxc/blob/ccae595aa49e779f7ecc9250329967aa546acd31/lxc-binding.h#L7)
is disabled. That's why we should *not* have LXC_DEVEL=1 for *any* release
build of LXC.

And also, as I can see the source code that was used to build LXC
5.0.0 in Jammy/Kinetic is not precisely the same as in the official
LXC 5.0.0 tag (https://github.com/lxc/lxc/tree/lxc-5.0.0).

I understand that Jammy is a LTS release and making any changes is a
problem and we should go through the SRU process. But I believe that
we have to do something at least with LXC_DEVEL to make things work
properly.

Kind regards,
Alex

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/lxc/+bug/2039873/+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 2038894] Re: Ubuntu 23.10 cloud images unexpected UDP listening port 5353

2023-10-19 Thread Andreas Hasenack

Hi Philip,

I have some questions here:

a) You state that some policy says that no ports other than 22 should be
open, which policy is that? Does it apply only to cloud images, or is it
an Ubuntu policy in general?

b) This is in mantic release at the moment, and switching that option
back to "no" could regress users that were relying on this default. What
exactly are we losing when we disable this service in this SRU? I
checked the original commit[1] but it does not have a bug number linked
to it with more details about what was the reasoning to enable this
option in the first place.

c) If this is only about cloud images, is the workaround in comment #4
something that could be added to the cloud image build process, or we
really want to avoid that?

d) Are there specific security concerns with keeping this service
enabled? I presume these were considered when the option was set to
"resolve" in that commit[1].


1. 
https://git.launchpad.net/~ubuntu-core-dev/ubuntu/+source/systemd/commit/?id=b308303f34484b293920473e5c4e0395142e4bcc

** Changed in: systemd (Ubuntu Mantic)
   Status: In Progress => Incomplete

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

Title:
  Ubuntu 23.10 cloud images unexpected UDP listening port  5353

Status in cloud-images:
  New
Status in systemd package in Ubuntu:
  Incomplete
Status in systemd source package in Mantic:
  Incomplete

Bug description:
  [Impact]

  In the latest Ubuntu 23.10 cloud images we are seeing unexpected UDP
  listening port 5353.

  By default and by policy, aside from port 22 there should be no other
  open ports on Ubuntu cloud images. Listening port 5353 is a
  regression.

  [Test Plan]

  Check that port 5353 is not open, and in particular that systemd-
  resolved is not listening on 5353. This is what it looks like when
  systemd-resolved *is* listening on 5353:

  ```
  $ ss --listening --no-header --tcp --udp --numeric
  udp   UNCONN  
 00 

   127.0.0.54:53
0.0.0.0:*
  udp   UNCONN  
 00 

127.0.0.53%lo:53
0.0.0.0:*
  udp   UNCONN  
 00 

 10.154.0.17%ens4:68
0.0.0.0:*
  udp   UNCONN  
 00 

127.0.0.1:323   
0.0.0.0:*
  udp   UNCONN  
 00 

  0.0.0.0:5353  
0.0.0.0:*
  udp   UNCONN  
 00 

[::1]:323   
   [::]:*
  udp   UNCONN  
 00 

 [::]:5353  
   [::]:*
  tcp   LISTEN  
 0
4096

[Touch-packages] [Bug 2039873] [NEW] liblxc-dev was built with LXC_DEVEL=1 in Ubuntu Jammy/Kinetic

2023-10-19 Thread Aleksandr Mikhalitsyn

Public bug reported:

Dear colleagues,

As I can see from:
-
https://git.launchpad.net/ubuntu/+source/lxc/tree/configure?h=applied/ubuntu/jammy
-
https://git.launchpad.net/ubuntu/+source/lxc/tree/configure?h=applied/ubuntu/kinetic

LXC 5.0.0 was built with LXC_DEVEL=1 set. But for release build we
should have LXC_DEVEL=0.

LXC_DEVEL is a variable that appears in the /usr/include/lxc/version.h
and then can be (and actually it is) used by other projects to detect if
liblxc-dev is a development build or stable.

Having LXC_DEVEL=1 makes problems for the users who want to build projects
those are depend on liblxc
from source (for example, LXD, go-lxc:
https://github.com/canonical/lxd/pull/12420).

And also, as I can see the source code that was used to build LXC 5.0.0
in Jammy/Kinetic is not precisely the same as in the official LXC 5.0.0
tag (https://github.com/lxc/lxc/tree/lxc-5.0.0).

I understand that Jammy is a LTS release and making any changes is a
problem and we should go through the SRU process. But I believe that we
have to do something at least with LXC_DEVEL to make things work
properly.

Kind regards,
Alex

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

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

Title:
liblxc-dev was built with LXC_DEVEL=1 in Ubuntu Jammy/Kinetic

Status in lxc package in Ubuntu:
New

Bug description:
Dear colleagues,

As I can see from:
-
https://git.launchpad.net/ubuntu/+source/lxc/tree/configure?h=applied/ubuntu/jammy
-
https://git.launchpad.net/ubuntu/+source/lxc/tree/configure?h=applied/ubuntu/kinetic

LXC 5.0.0 was built with LXC_DEVEL=1 set. But for release build we
should have LXC_DEVEL=0.

LXC_DEVEL is a variable that appears in the /usr/include/lxc/version.h
and then can be (and actually it is) used by other projects to detect
if liblxc-dev is a development build or stable.

Having LXC_DEVEL=1 makes problems for the users who want to build projects
those are depend on liblxc
from source (for example, LXD, go-lxc:
https://github.com/canonical/lxd/pull/12420).

And also, as I can see the source code that was used to build LXC
5.0.0 in Jammy/Kinetic is not precisely the same as in the official
LXC 5.0.0 tag (https://github.com/lxc/lxc/tree/lxc-5.0.0).

Kind regards,
Alex

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/lxc/+bug/2039873/+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 2039503] Re: package network-manager 1.44.2-1ubuntu1 failed to install/upgrade: installed network-manager package post-installation script subprocess returned error exit status 1

2023-10-19 Thread Launchpad Bug Tracker

This bug was fixed in the package network-manager - 1.44.2-1ubuntu1.1

---
network-manager (1.44.2-1ubuntu1.1) mantic; urgency=medium

  * network-manager.postinst: Skip unknown connection profiles (LP: #2039503)
  * Update debian/gbp.conf

 -- Lukas Märdian   Wed, 18 Oct 2023 10:45:22 +0200

** Changed in: network-manager (Ubuntu Mantic)
   Status: Fix Committed => Fix Released

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

Title:
  package network-manager 1.44.2-1ubuntu1 failed to install/upgrade:
  installed network-manager package post-installation script subprocess
  returned error exit status 10

Status in network-manager package in Ubuntu:
  Fix Released
Status in network-manager source package in Mantic:
  Fix Released

Bug description:
  [ Impact ]

   * A failure to query nmcli will fail the network-manager.postinst
  maintainer script (using "set -e")

   * This will make the package installation/upgrade fail

   * The fix catches the error on "ORIG_NAME=$(nmcli --get-values
  connection.id con show "$UUID")" and skips the corresponding keyfile
  with a warning message

  [ Test Plan ]

  $ sudo vim /etc/NetworkManager/system-connections/UPTOWN.guests # bad file
  [connection]
  id=UPTOWN.guests
  uuid=491fa5c8-68ef-4140-8679-dca422f5c262
  type=wifi

  [wifi]
  ssid=UPTOWN.guests
  mode=infrastructure
  mac-address=E0:9D:31:09:84:54

  [ipv6]
  method=auto

  [ipv4]
  method=auto

  $ sudo vim /etc/NetworkManager/system-connections/aaaUPTOWN # good file
  [connection]
  id=aaaUPTOWN
  uuid=491fa5c8-68ef---dca422f5c262
  type=wifi

  [wifi]
  ssid=aaaUPTOWN
  mode=infrastructure
  mac-address=E0:9D:31:09:84:54

  [ipv6]
  method=auto

  [ipv4]
  method=auto

  $ sudo chmod 600 /etc/NetworkManager/system-connections/*UPTOWN*
  $ sudo nmcli con reload
  $ ls -la /etc/NetworkManager/system-connections/
  total 32
  drwxr-xr-x 2 root root 12288 Oct 17 17:51 ./
  drwxr-xr-x 7 root root 12288 Oct 17 17:46 ../
  -rw--- 1 root root   199 Oct 17 17:05 UPTOWN.guests
  -rw--- 1 root root   191 Oct 17 17:46 aaaUPTOWN

  # Install network-manager from proposed
  $ apt update && apt install -t mantic-proposed network-manager # version 
1.44.2-1ubuntu1.1

  # Verify you don't see an error like this, breaking the pkg install
  Error: 491fa5c8-68ef-4140-8679-dca422f5c262 - no such connection profile.
  dpkg: error processing package network-manager (--configure):
   installed network-manager package post-installation script subprocess 
returned error exit status 10

  # Verify you see a migration log like this and the package installation is 
successful:
  Error: 491fa5c8-68ef-4140-8679-dca422f5c262 - no such connection profile.
  SKIP: UPTOWN.guests (491fa5c8-68ef-4140-8679-dca422f5c262) unknown to 
NetworkManager.
  Migrating aaaUPTOWN (491fa5c8-68ef---dca422f5c262) to /etc/netplan
  $ echo $?
  0

  # Verify the good profile got migrated, while the bad one remains:
  $ sudo grep -RH UPTOWN /etc/netplan/
  /etc/netplan/90-NM-491fa5c8-68ef---dca422f5c262.yaml:
"aaaUPTOWN":
  /etc/netplan/90-NM-491fa5c8-68ef---dca422f5c262.yaml:
name: "aaaUPTOWN"
  /etc/netplan/90-NM-491fa5c8-68ef---dca422f5c262.yaml:name: 
"aaaUPTOWN"
  $ ls -la /etc/NetworkManager/system-connections/
  insgesamt 28
  drwxr-xr-x 2 root root 12288 Okt 17 18:03 .
  drwxr-xr-x 7 root root 12288 Okt 17 17:46 ..
  -rw--- 1 root root   199 Okt 17 17:05 UPTOWN.guests

  [ Where problems could occur ]

   * This is touching NetworkManager's maintainer script
   * Breaking it could lead to a broken/unconfigured NetworkManager package
   * This could render a machine's networking unusable
   * It could break distribution upgrades on package install/configure failure

  [ Other Info ]

   * Linting was used to validate the maintainer script:
     shellcheck --shell=sh debian/network-manager.postinst

  === original bug description ===

  lunar to mantic upgrade, exciting to see output from network-manager
  postinst migrating connections to /etc/netplan one by one.  But then:

  Error: 491fa5c8-68ef-4140-8679-dca422f5c262 - no such connection profile.
  dpkg: error processing package network-manager (--configure):
   installed network-manager package post-installation script subprocess 
returned error exit status 10

  That UUID appears in a file /etc/NetworkManager/system-
  connections/UPTOWN.guests that hasn't been touched since 2015.

  Contents of the file were:

  [connection]
  id=UPTOWN.guests
  uuid=491fa5c8-68ef-4140-8679-dca422f5c262
  type=wifi

  [wifi]
  ssid=UPTOWN.guests
  mode=infrastructure
  mac-address=E0:9D:31:09:84:54

  [ipv6]
  method=auto

  [ipv4]
  method=auto

  I've removed it from disk and the migration continued to completion.

  Then I got another failure on:

  [connection]

[Touch-packages] [Bug 2039503] Update Released

2023-10-19 Thread Brian Murray

The verification of the Stable Release Update for network-manager has
completed successfully and the package is now being released to
-updates.  Subsequently, the Ubuntu Stable Release Updates Team is being
unsubscribed and will not receive messages about this bug report.  In
the event that you encounter a regression using the package from
-updates please report a new bug using ubuntu-bug and tag the bug report
regression-update so we can easily find any regressions.

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

Title:
  package network-manager 1.44.2-1ubuntu1 failed to install/upgrade:
  installed network-manager package post-installation script subprocess
  returned error exit status 10

Status in network-manager package in Ubuntu:
  Fix Released
Status in network-manager source package in Mantic:
  Fix Released

Bug description:
  [ Impact ]

   * A failure to query nmcli will fail the network-manager.postinst
  maintainer script (using "set -e")

   * This will make the package installation/upgrade fail

   * The fix catches the error on "ORIG_NAME=$(nmcli --get-values
  connection.id con show "$UUID")" and skips the corresponding keyfile
  with a warning message

  [ Test Plan ]

  $ sudo vim /etc/NetworkManager/system-connections/UPTOWN.guests # bad file
  [connection]
  id=UPTOWN.guests
  uuid=491fa5c8-68ef-4140-8679-dca422f5c262
  type=wifi

  [wifi]
  ssid=UPTOWN.guests
  mode=infrastructure
  mac-address=E0:9D:31:09:84:54

  [ipv6]
  method=auto

  [ipv4]
  method=auto

  $ sudo vim /etc/NetworkManager/system-connections/aaaUPTOWN # good file
  [connection]
  id=aaaUPTOWN
  uuid=491fa5c8-68ef---dca422f5c262
  type=wifi

  [wifi]
  ssid=aaaUPTOWN
  mode=infrastructure
  mac-address=E0:9D:31:09:84:54

  [ipv6]
  method=auto

  [ipv4]
  method=auto

  $ sudo chmod 600 /etc/NetworkManager/system-connections/*UPTOWN*
  $ sudo nmcli con reload
  $ ls -la /etc/NetworkManager/system-connections/
  total 32
  drwxr-xr-x 2 root root 12288 Oct 17 17:51 ./
  drwxr-xr-x 7 root root 12288 Oct 17 17:46 ../
  -rw--- 1 root root   199 Oct 17 17:05 UPTOWN.guests
  -rw--- 1 root root   191 Oct 17 17:46 aaaUPTOWN

  # Install network-manager from proposed
  $ apt update && apt install -t mantic-proposed network-manager # version 
1.44.2-1ubuntu1.1

  # Verify you don't see an error like this, breaking the pkg install
  Error: 491fa5c8-68ef-4140-8679-dca422f5c262 - no such connection profile.
  dpkg: error processing package network-manager (--configure):
   installed network-manager package post-installation script subprocess 
returned error exit status 10

  # Verify you see a migration log like this and the package installation is 
successful:
  Error: 491fa5c8-68ef-4140-8679-dca422f5c262 - no such connection profile.
  SKIP: UPTOWN.guests (491fa5c8-68ef-4140-8679-dca422f5c262) unknown to 
NetworkManager.
  Migrating aaaUPTOWN (491fa5c8-68ef---dca422f5c262) to /etc/netplan
  $ echo $?
  0

  # Verify the good profile got migrated, while the bad one remains:
  $ sudo grep -RH UPTOWN /etc/netplan/
  /etc/netplan/90-NM-491fa5c8-68ef---dca422f5c262.yaml:
"aaaUPTOWN":
  /etc/netplan/90-NM-491fa5c8-68ef---dca422f5c262.yaml:
name: "aaaUPTOWN"
  /etc/netplan/90-NM-491fa5c8-68ef---dca422f5c262.yaml:name: 
"aaaUPTOWN"
  $ ls -la /etc/NetworkManager/system-connections/
  insgesamt 28
  drwxr-xr-x 2 root root 12288 Okt 17 18:03 .
  drwxr-xr-x 7 root root 12288 Okt 17 17:46 ..
  -rw--- 1 root root   199 Okt 17 17:05 UPTOWN.guests

  [ Where problems could occur ]

   * This is touching NetworkManager's maintainer script
   * Breaking it could lead to a broken/unconfigured NetworkManager package
   * This could render a machine's networking unusable
   * It could break distribution upgrades on package install/configure failure

  [ Other Info ]

   * Linting was used to validate the maintainer script:
     shellcheck --shell=sh debian/network-manager.postinst

  === original bug description ===

  lunar to mantic upgrade, exciting to see output from network-manager
  postinst migrating connections to /etc/netplan one by one.  But then:

  Error: 491fa5c8-68ef-4140-8679-dca422f5c262 - no such connection profile.
  dpkg: error processing package network-manager (--configure):
   installed network-manager package post-installation script subprocess 
returned error exit status 10

  That UUID appears in a file /etc/NetworkManager/system-
  connections/UPTOWN.guests that hasn't been touched since 2015.

  Contents of the file were:

  [connection]
  id=UPTOWN.guests
  uuid=491fa5c8-68ef-4140-8679-dca422f5c262
  type=wifi

  [wifi]
  ssid=UPTOWN.guests
  mode=infrastructure
  mac-address=E0:9D:31:09:84:54

  [ipv6]
  method=auto

  [ipv4]
  method=auto

  I've removed it from disk and the migration continued to

[Touch-packages] [Bug 2039868] Re: amdgpu reset during usage of firefox

2023-10-19 Thread Erich Eickmeyer

Working with Pirouette on IRC, we determined this may be related to
https://bugzilla.kernel.org/show_bug.cgi?id=201957#c94 in which the
solution, sadly, was to add amdgpu.mcbp=0 to the kernel boot parameters.
Per that bug report, it does appear as though this might be the result
of a regression in the 6.5 kernel as they did not experience this issue
in prior kernels or Ubuntu 23.04.

They also found mentions of
https://gitlab.freedesktop.org/drm/amd/-/issues/2848 where Kernel 6.6
has a fix which we could pull a patch from, and we might have a patch
for mesa at
https://gitlab.freedesktop.org/drm/amd/-/issues/2848#note_2095536.

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

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

Title:
  amdgpu reset during usage of firefox

Status in Linux:
  Unknown
Status in linux package in Ubuntu:
  Confirmed
Status in mesa package in Ubuntu:
  New

Bug description:
  Running nightly on 23.10 (since monday), I have been experiencing a
  few amdgpu resets in the past hours

  ProblemType: Bug
  DistroRelease: Ubuntu 23.10
  Package: linux-image-6.5.0-9-generic 6.5.0-9.9
  ProcVersionSignature: Ubuntu 6.5.0-9.9-generic 6.5.3
  Uname: Linux 6.5.0-9-generic x86_64
  ApportVersion: 2.27.0-0ubuntu5
  Architecture: amd64
  CasperMD5CheckResult: pass
  CurrentDesktop: ubuntu:GNOME
  Date: Thu Oct 19 18:26:43 2023
  HibernationDevice: RESUME=/dev/mapper/vg--ubuntu-lv--ubuntu--swap
  InstallationDate: Installed on 2022-07-04 (472 days ago)
  InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Release amd64 
(20220419)
  MachineType: {report['dmi.sys.vendor']} {report['dmi.product.name']}
  ProcEnviron:
   LANG=fr_FR.UTF-8
   PATH=(custom, no user)
   SHELL=/bin/bash
   TERM=xterm-256color
  ProcFB: 0 amdgpudrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-6.5.0-9-generic 
root=/dev/mapper/vg--ubuntu-lv--ubuntu--root ro rootflags=subvol=@ quiet splash 
resume=/dev/mapper/vg--ubuntu-lv--ubuntu--swap vt.handoff=7
  RelatedPackageVersions:
   linux-restricted-modules-6.5.0-9-generic N/A
   linux-backports-modules-6.5.0-9-generic  N/A
   linux-firmware   20230919.git3672ccab-0ubuntu2.1
  SourcePackage: linux
  UpgradeStatus: Upgraded to mantic on 2023-10-16 (3 days ago)
  dmi.bios.date: 05/15/2023
  dmi.bios.release: 1.24
  dmi.bios.vendor: LENOVO
  dmi.bios.version: R1MET54W (1.24 )
  dmi.board.asset.tag: Not Available
  dmi.board.name: 21A0CTO1WW
  dmi.board.vendor: LENOVO
  dmi.board.version: Not Defined
  dmi.chassis.asset.tag: No Asset Information
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: None
  dmi.ec.firmware.release: 1.24
  dmi.modalias: 
dmi:bvnLENOVO:bvrR1MET54W(1.24):bd05/15/2023:br1.24:efr1.24:svnLENOVO:pn21A0CTO1WW:pvrThinkPadP14sGen2a:rvnLENOVO:rn21A0CTO1WW:rvrNotDefined:cvnLENOVO:ct10:cvrNone:skuLENOVO_MT_21A0_BU_Think_FM_ThinkPadP14sGen2a:
  dmi.product.family: ThinkPad P14s Gen 2a
  dmi.product.name: 21A0CTO1WW
  dmi.product.sku: LENOVO_MT_21A0_BU_Think_FM_ThinkPad P14s Gen 2a
  dmi.product.version: ThinkPad P14s Gen 2a
  dmi.sys.vendor: LENOVO

To manage notifications about this bug go to:
https://bugs.launchpad.net/linux/+bug/2039868/+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 2038807] Re: /usr/libexec/packagekitd:6:g_assertion_message:g_assertion_message_expr:pk_transaction_dispose:pk_transaction_dispose:g_object_unref

2023-10-19 Thread Benjamin Drung

219 crash reports so far. Leaving the ticket untouched until next week.

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

Title:
  
/usr/libexec/packagekitd:6:g_assertion_message:g_assertion_message_expr:pk_transaction_dispose:pk_transaction_dispose:g_object_unref

Status in packagekit package in Ubuntu:
  New

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

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/packagekit/+bug/2038807/+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 2037667] Re: Regression on Jammy's kernel 5.15 when creating ip6gre and vti6 tunnels

2023-10-19 Thread Lukas Märdian

** Changed in: systemd (Ubuntu)
   Status: Invalid => Confirmed

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

Title:
  Regression on Jammy's kernel 5.15 when creating ip6gre and vti6
  tunnels

Status in linux package in Ubuntu:
  Confirmed
Status in systemd package in Ubuntu:
  Confirmed
Status in linux source package in Jammy:
  Triaged
Status in systemd source package in Jammy:
  New

Bug description:
  We noticed that some of Netplan's integration tests started to fail on
  Jammy. These tests will try to create ip6gre and vti6 virtual
  interfaces and systemd-networkd is failing to create them starting on
  kernel 5.15.0-83.92. As far as I can tell, kernel 5.15.0-82.91 is the
  last revision where it works. So, some change between 5.15.0-82.91 and
  5.15.0-83.92 is causing this regression.

  How to reproduce the issue:

  # Launch a jammy cloud VM:

  lxc launch images:ubuntu/jammy/cloud jammy --vm
  lxc shell jammy

  # Create a netplan file that creates 2 tunnels:
   
  cat > /etc/netplan/10-tun.yaml 2' && reboot

  # Check with "ip link" again that both tun0 and tun1 were created

  # Reboot again to go back to the most recent kernel and check with "ip link" 
that both tun0 and tun1 were not created.
  --- 
  ProblemType: Bug
  AlsaDevices:
   total 0
   crw-rw 1 root audio 116,  1 Sep 29 12:52 seq
   crw-rw 1 root audio 116, 33 Sep 29 12:52 timer
  AplayDevices: Error: [Errno 2] No such file or directory: 'aplay'
  ApportVersion: 2.20.11-0ubuntu82.5
  Architecture: amd64
  ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord'
  AudioDevicesInUse: Error: [Errno 2] No such file or directory: 'fuser'
  CRDA: N/A
  CasperMD5CheckResult: unknown
  CloudArchitecture: x86_64
  CloudID: lxd
  CloudName: lxd
  CloudPlatform: lxd
  CloudSubPlatform: LXD socket API v. 1.0 (/dev/lxd/sock)
  DistroRelease: Ubuntu 22.04
  IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig'
  Lspci: Error: [Errno 2] No such file or directory: 'lspci'
  Lspci-vt: Error: [Errno 2] No such file or directory: 'lspci'
  Lsusb: Error: [Errno 2] No such file or directory: 'lsusb'
  Lsusb-t: Error: [Errno 2] No such file or directory: 'lsusb'
  Lsusb-v: Error: [Errno 2] No such file or directory: 'lsusb'
  MachineType: QEMU Standard PC (Q35 + ICH9, 2009)
  Package: linux (not installed)
  PciMultimedia:
   
  ProcEnviron:
   TERM=screen-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcFB: 0 virtio_gpudrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.15.0-84-generic root=/dev/sda2 
ro quiet splash console=tty1 console=ttyS0 vt.handoff=7
  ProcVersionSignature: Ubuntu 5.15.0-84.93-generic 5.15.116
  RelatedPackageVersions:
   linux-restricted-modules-5.15.0-84-generic N/A
   linux-backports-modules-5.15.0-84-generic  N/A
   linux-firmware N/A
  RfKill: Error: [Errno 2] No such file or directory: 'rfkill'
  Tags:  jammy uec-images
  Uname: Linux 5.15.0-84-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: N/A
  _MarkForUpload: True
  dmi.bios.date: 2/2/2022
  dmi.bios.release: 0.0
  dmi.bios.vendor: EDK II
  dmi.bios.version: unknown
  dmi.board.name: LXD
  dmi.board.vendor: Canonical Ltd.
  dmi.board.version: pc-q35-8.0
  dmi.chassis.type: 1
  dmi.chassis.vendor: QEMU
  dmi.chassis.version: pc-q35-8.0
  dmi.modalias: 
dmi:bvnEDKII:bvrunknown:bd2/2/2022:br0.0:svnQEMU:pnStandardPC(Q35+ICH9,2009):pvrpc-q35-8.0:rvnCanonicalLtd.:rnLXD:rvrpc-q35-8.0:cvnQEMU:ct1:cvrpc-q35-8.0:sku:
  dmi.product.name: Standard PC (Q35 + ICH9, 2009)
  dmi.product.version: pc-q35-8.0
  dmi.sys.vendor: QEMU

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2037667/+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 1794064] Re: Clicking a hyperlink in a PDF fails to open it if the default browser is a snap

2023-10-19 Thread Andreas Hasenack

Hi Georgia, is this still pending an evince fix? Your PPA has an updated
evince package, but I don't think it was uploaded to unapproved yet,
without the recommends.

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

Title:
  Clicking a hyperlink in a PDF fails to open it if the default browser
  is a snap

Status in apparmor package in Ubuntu:
  Fix Released
Status in evince package in Ubuntu:
  Fix Released
Status in apparmor source package in Jammy:
  Fix Committed
Status in evince source package in Jammy:
  In Progress
Status in apparmor source package in Lunar:
  Fix Released
Status in evince source package in Lunar:
  Fix Released
Status in apparmor package in Debian:
  Fix Released
Status in evince package in Debian:
  Confirmed

Bug description:
  [Impact]

   * Users cannot open a hyperlink in a PDF opened with evince when the default 
browser is a snap.
   * The fix creates a snap_browsers abstraction on AppArmor which can be used 
in a transition for when the browser is executed. The snap_browsers abstraction 
provides the minimal amount of permissions required to execute a browser 
provided through snaps. This is a workaround since AppArmor currently does not 
provide mediation/filtering on enhanced environment variables.

  [Test Plan]

   * Make sure the default browser is provided through the snap store.
   * Open a PDF that contains a hyperlink using evince and click on the URL.
   * The browser should open the requested URL. 

  [Where problems could occur]

   * If the browser or snap core update to have new requirements for
  opening a browser, then the current policy could become obsolete and
  will need to be updated again.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/apparmor/+bug/1794064/+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 1907878] Re: wrong var declaration in if-up.d/resolved (nm-dispatcher[54417]: /etc/network/if-up.d/resolved: 12: mystatedir: not found)

2023-10-19 Thread Heitor Alves de Siqueira

@jasimioni I've dropped some bits of your diff that aren't necessary for
SRU (the typo fix), and sponsored your changes with mine from bug
1981103. Thank you for the help on fixing this!

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

Title:
  wrong var declaration in if-up.d/resolved (nm-dispatcher[54417]:
  /etc/network/if-up.d/resolved: 12: mystatedir: not found)

Status in ifupdown package in Ubuntu:
  Fix Released
Status in ifupdown source package in Jammy:
  In Progress

Bug description:
  Syslog error:

     nm-dispatcher[...]: /etc/network/if-up.d/resolved: 12: mystatedir:
  not found

  I think it's because of this line:

    if systemctl is-enabled systemd-resolved > /dev/null 2>&1; then
    mystatedir statedir ifindex interface <- this 
is interpreted as a 'mystatedir' command and fails

    interface=$IFACE
    if [ ! "$interface" ]; then

  Perhaps the intention was to 'export mystatedir statedir ...'

  SRU for Jammy:

  [ Impact ]

 * /etc/network/if-{up,down}.d/resolved have a mistype:
 
 mystatedir statedir ifindex interface
 
 And when this line is executed, mystatedir is not found (not a valid 
command)
 and it generates an error log in /var/log/syslog and the terminal output. 
 It's not fatal, and the rest of the code gets executed, but it generates 
the
 message.
 
 # ifup ens3
 /etc/network/if-up.d/resolved: 12: mystatedir: not found

 # ifdown ens3
 /etc/network/if-down.d/resolved: 12: mystatedir: not found 
 
 The fix accepted in kinetic is only to remove this line. The same fix can 
be
 applied to Jammy.
 
  [ Test Plan ]

 With the new package installed, remove netplan configuration and add a 
valid
 /etc/network/interfaces file and then use the commands:
 
 # ifdown 
 # ifup 
 
 And confirm the messages are not displayed and the network configuration
 succeeds.
 
  [ Where problems could occur ]

 If mystatedir would be a valid command or function, which is not the case,
 that could break the script.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/ifupdown/+bug/1907878/+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 2039815] [NEW] Update to at least systemd v254 in lunar

2023-10-19 Thread Tripple Moon

Public bug reported:

There have been many enhancements to systemd in the newer versions, which i 
would like to use.
fe. see this thread: 
https://github.com/systemd/systemd/issues/28984#issuecomment-1770883963

```
$ lsb_release -rd:
Description:Ubuntu 23.04
Release:23.04

$ apt-cache policy systemd
systemd:
  Installed: 252.5-2ubuntu3.1
  Candidate: 252.5-2ubuntu3.1
  Version table:
 *** 252.5-2ubuntu3.1 500
500 http://archive.ubuntu.com/ubuntu lunar-updates/main amd64 Packages
100 /var/lib/dpkg/status
 252.5-2ubuntu3 500
500 http://archive.ubuntu.com/ubuntu lunar/main amd64 Packages
```

```
Operating System: Kubuntu 23.04
KDE Plasma Version: 5.27.4
KDE Frameworks Version: 5.104.0
Qt Version: 5.15.8
Kernel Version: 6.2.0-34-generic (64-bit)
Graphics Platform: X11
Processors: 12 × Intel® Core™ i7-5820K CPU @ 3.30GHz
Memory: 31,2 GiB of RAM
Graphics Processor: NVIDIA GeForce GTX 1080 Ti/PCIe/SSE2
Manufacturer: ASUS
Product Name: All Series
```

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


** Tags: lunar

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

Title:
  Update to at least systemd v254 in lunar

Status in systemd package in Ubuntu:
  New

Bug description:
  There have been many enhancements to systemd in the newer versions, which i 
would like to use.
  fe. see this thread: 
https://github.com/systemd/systemd/issues/28984#issuecomment-1770883963

  ```
  $ lsb_release -rd:
  Description:  Ubuntu 23.04
  Release:  23.04

  $ apt-cache policy systemd
  systemd:
Installed: 252.5-2ubuntu3.1
Candidate: 252.5-2ubuntu3.1
Version table:
   *** 252.5-2ubuntu3.1 500
  500 http://archive.ubuntu.com/ubuntu lunar-updates/main amd64 Packages
  100 /var/lib/dpkg/status
   252.5-2ubuntu3 500
  500 http://archive.ubuntu.com/ubuntu lunar/main amd64 Packages
  ```

  ```
  Operating System: Kubuntu 23.04
  KDE Plasma Version: 5.27.4
  KDE Frameworks Version: 5.104.0
  Qt Version: 5.15.8
  Kernel Version: 6.2.0-34-generic (64-bit)
  Graphics Platform: X11
  Processors: 12 × Intel® Core™ i7-5820K CPU @ 3.30GHz
  Memory: 31,2 GiB of RAM
  Graphics Processor: NVIDIA GeForce GTX 1080 Ti/PCIe/SSE2
  Manufacturer: ASUS
  Product Name: All Series
  ```

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

2023-10-19 Thread Andreas Hasenack

Hi @enr0n, could you please comment on Chris's remark above about the
state of this SRU?

-- 
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 Committed
Status in systemd source package in Lunar:
  Fix Committed

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 2039811] [NEW] Xorg freeze

2023-10-19 Thread magowiz

Public bug reported:

while using google meet with google-chrome and sharing screen it happens
that the video hangs completely, the audio continues to work, if I'm
lucky I can restore my desktop using CTRL+ALT+F8 and then CTRL+ALT+F2
again, otherwise I need a forced shutdown.

lsb_release -rd 
No LSB modules are available.
Description:Ubuntu 23.10
Release:23.10


apt-cache policy xorg
xorg:
  Installed: 1:7.7+23ubuntu2
  Candidate: 1:7.7+23ubuntu2
  Version table:
 *** 1:7.7+23ubuntu2 500
500 http://it.archive.ubuntu.com/ubuntu mantic/main amd64 Packages
100 /var/lib/dpkg/status

ProblemType: Bug
DistroRelease: Ubuntu 23.10
Package: xorg 1:7.7+23ubuntu2
ProcVersionSignature: Ubuntu 6.5.0-9.9-generic 6.5.3
Uname: Linux 6.5.0-9-generic x86_64
ApportVersion: 2.27.0-0ubuntu5
Architecture: amd64
BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
CasperMD5CheckResult: unknown
CompositorRunning: None
CurrentDesktop: ubuntu:GNOME
Date: Thu Oct 19 15:13:12 2023
DistUpgraded: 2023-10-14 15:27:57,866 DEBUG Running PostInstallScript: 
'/usr/lib/ubuntu-advantage/upgrade_lts_contract.py'
DistroCodename: mantic
DistroVariant: ubuntu
DkmsStatus:
 virtualbox/7.0.10, 6.2.0-34-generic, x86_64: installed
 virtualbox/7.0.10, 6.5.0-9-generic, x86_64: installed
EcryptfsInUse: Yes
ExtraDebuggingInterest: No
GpuHangFrequency: Several times a day
GpuHangReproducibility: Seems to happen randomly
GpuHangStarted: Immediately after installing this version of Ubuntu
GraphicsCard:
 Intel Corporation Raptor Lake-P [Iris Xe Graphics] [8086:a7a1] (rev 04) 
(prog-if 00 [VGA controller])
   Subsystem: Hewlett-Packard Company Raptor Lake-P [Iris Xe Graphics] 
[103c:8b41]
InstallationDate: Installed on 2023-10-04 (15 days ago)
InstallationMedia: Ubuntu 23.04 "Lunar Lobster" - Release amd64 (20230418)
MachineType: {report['dmi.sys.vendor']} {report['dmi.product.name']}
ProcEnviron:
 LANG=en_US.UTF-8
 PATH=(custom, no user)
 SHELL=/usr/bin/fish
 TERM=xterm-256color
 XDG_RUNTIME_DIR=
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-6.5.0-9-generic 
root=UUID=0179f596-cd6b-485d-82e8-a9db5d32f999 ro quiet splash vt.handoff=7
SourcePackage: xorg
Symptom: display
Title: Xorg freeze
UpgradeStatus: Upgraded to mantic on 2023-10-14 (5 days ago)
dmi.bios.date: 05/30/2023
dmi.bios.release: 1.8
dmi.bios.vendor: HP
dmi.bios.version: V70 Ver. 01.01.08
dmi.board.name: 8B41
dmi.board.vendor: HP
dmi.board.version: KBC Version 51.2B.00
dmi.chassis.type: 10
dmi.chassis.vendor: HP
dmi.ec.firmware.release: 81.43
dmi.modalias: 
dmi:bvnHP:bvrV70Ver.01.01.08:bd05/30/2023:br1.8:efr81.43:svnHP:pnHPEliteBook86016inchG10NotebookPC:pvr:rvnHP:rn8B41:rvrKBCVersion51.2B.00:cvnHP:ct10:cvr:sku8A452EA#ABZ:
dmi.product.family: 103C_5336AN HP EliteBook
dmi.product.name: HP EliteBook 860 16 inch G10 Notebook PC
dmi.product.sku: 8A452EA#ABZ
dmi.sys.vendor: HP
version.compiz: compiz N/A
version.libdrm2: libdrm2 2.4.115-1
version.libgl1-mesa-dri: libgl1-mesa-dri 23.2.1-1ubuntu3
version.libgl1-mesa-glx: libgl1-mesa-glx N/A
version.xserver-xorg-core: xserver-xorg-core 2:21.1.7-3ubuntu2
version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-3
version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20210115-1
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 freeze mantic 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/2039811

Title:
  Xorg freeze

Status in xorg package in Ubuntu:
  New

Bug description:
  while using google meet with google-chrome and sharing screen it
  happens that the video hangs completely, the audio continues to work,
  if I'm lucky I can restore my desktop using CTRL+ALT+F8 and then
  CTRL+ALT+F2 again, otherwise I need a forced shutdown.

  lsb_release -rd 
  No LSB modules are available.
  Description:  Ubuntu 23.10
  Release:  23.10

  
  apt-cache policy xorg
  xorg:
Installed: 1:7.7+23ubuntu2
Candidate: 1:7.7+23ubuntu2
Version table:
   *** 1:7.7+23ubuntu2 500
  500 http://it.archive.ubuntu.com/ubuntu mantic/main amd64 Packages
  100 /var/lib/dpkg/status

  ProblemType: Bug
  DistroRelease: Ubuntu 23.10
  Package: xorg 1:7.7+23ubuntu2
  ProcVersionSignature: Ubuntu 6.5.0-9.9-generic 6.5.3
  Uname: Linux 6.5.0-9-generic x86_64
  ApportVersion: 2.27.0-0ubuntu5
  Architecture: amd64
  BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
  CasperMD5CheckResult: unknown
  CompositorRunning: None
  CurrentDesktop: ubuntu:GNOME
  Date: Thu Oct 19 15:13:12 2023
  DistUpgraded: 2023-10-14 15:27:57,866 DEBUG Running PostInstallScript: 
'/usr/lib/ubuntu-advantage/upgrade_lts_contract.py'
  DistroCodename: mantic
  DistroVariant: ubuntu

[Touch-packages] [Bug 794315] Re: lightdm forgets to source /etc/profile and ~/.profile

2023-10-19 Thread Bug Watch Updater

** Changed in: lightdm (Debian)
   Status: Confirmed => Fix Released

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

Title:
  lightdm forgets to source /etc/profile and ~/.profile

Status in Light Display Manager:
  Fix Released
Status in lightdm package in Ubuntu:
  Fix Released
Status in lightdm package in Debian:
  Fix Released

Bug description:
  Binary package hint: lightdm

  /etc/gdm/Xsession had this code:
# First read /etc/profile and .profile
test -f /etc/profile && . /etc/profile
test -f "$HOME/.profile" && . "$HOME/.profile"
# Second read /etc/xprofile and .xprofile for X specific setup
test -f /etc/xprofile && . /etc/xprofile
test -f "$HOME/.xprofile" && . "$HOME/.xprofile"
  so that, for example, ~/bin gets added to the path (by the default 
~/.profile), and any user-customized environment setup gets run.

  After switching from gdm to lightdm, this no longer happens.  This is
  going to be a regression now that lightdm is becoming the default
  display manager.

  ProblemType: Bug
  DistroRelease: Ubuntu 11.10
  Package: lightdm 0.3.7-0ubuntu1
  ProcVersionSignature: Ubuntu 2.6.39-3.10-generic 2.6.39
  Uname: Linux 2.6.39-3-generic x86_64
  NonfreeKernelModules: openafs
  Architecture: amd64
  Date: Tue Jun  7 19:27:11 2011
  EcryptfsInUse: Yes
  InstallationMedia: Ubuntu 11.04 "Natty Narwhal" - Alpha amd64 (20101202)
  ProcEnviron:
   LANGUAGE=en_US:en
   PATH=(custom, no user)
   LANG=en_US.utf8
   LC_MESSAGES=en_US.utf8
   SHELL=/bin/bash
  SourcePackage: lightdm
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/lightdm/+bug/794315/+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 1978351] Re: MITM vector: ifupdown puts .domains TLD in resolv.conf

2023-10-19 Thread Jun Aruga

> Anyone, could you tell me how to fix this issue, maybe adjusting the
`zzz-fix-domains` script? Thanks.

I was able to fix this issue with another workaround even when rebooting
OS. I didn't use the workaround script `/etc/network/if-up.d/zzz-fix-
domains`. I added a new systemd service to run the `/usr/bin/resolvectl
domain bond0 ""` in my case.

You can see the following link for details.
https://github.com/ruby/spec/issues/1095#issuecomment-1770537299


** Bug watch added: github.com/ruby/spec/issues #1095
   https://github.com/ruby/spec/issues/1095

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

Title:
  MITM vector: ifupdown puts .domains TLD in resolv.conf

Status in ifupdown package in Ubuntu:
  Confirmed

Bug description:
  The bug described in
  https://bugs.launchpad.net/ubuntu/+source/ifupdown/+bug/1907878?comments=all
  is a security vulnerability because DNS names that would normally fail
  are now attempted as "foo.domains".

  ".domains" is a real TLD, with the registrar "Donuts, Inc." based in Bellvue, 
WA.
  "google.com.domains" is registered, for example. So is "test.domains".

  For users with ifupdown, any Internet request (especially that does
  not involve some cryptographic payload and destination signature
  verification) is potentially sending packets to an unintended
  audience. It's impossible to say, but likely, that malicious
  registrants are squatting sensitive and common names in the .domains
  TLD.

  The ifupdown package is still used by some cloud providers that have not 
adopted netplan.
  This vulnerability affects 22.04 and potentially other releases.

  This issue has not been corrected in 0.8.36+nmu1ubuntu4.

  With 0.8.36+nmu1ubuntu3 and after an update to 0.8.36+nmu1ubuntu4, the
  resolv.conf looks like the following (which is vulnerable to mitm
  attacks):

  ```
  root@foo:~# cat /etc/resolv.conf
  # This is /run/systemd/resolve/stub-resolv.conf managed by 
man:systemd-resolved(8).
  # Do not edit.
  #
  # This file might be symlinked as /etc/resolv.conf. If you're looking at
  # /etc/resolv.conf and seeing this text, you have followed the symlink.
  #
  # This is a dynamic resolv.conf file for connecting local clients to the
  # internal DNS stub resolver of systemd-resolved. This file lists all
  # configured search domains.
  #
  # Run "resolvectl status" to see details about the uplink DNS servers
  # currently in use.
  #
  # Third party programs should typically not access this file directly, but 
only
  # through the symlink at /etc/resolv.conf. To manage man:resolv.conf(5) in a
  # different way, replace this symlink by a static file or a different symlink.
  #
  # See man:systemd-resolved.service(8) for details about the supported modes of
  # operation for /etc/resolv.conf.

  nameserver 127.0.0.53
  options edns0 trust-ad
  search DOMAINS
  ```

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/ifupdown/+bug/1978351/+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 2039798] [NEW] please upgrade to 8.4 to address vulnerability

2023-10-19 Thread madigal

Public bug reported:

Actually Mantic has 8.2.1 version
A huge security issue is fixed with 8.4 : 
https://linuxsecurity.com/news/security-vulnerabilities/curl-8-4-released-for-addressing-a-big-security-vulnerability

changelog: https://curl.se/changes.html
Available on Debian Sid: https://packages.debian.org/sid/curl

** Affects: curl (Ubuntu)
 Importance: Undecided
 Status: Confirmed


** Tags: community-security mantic

** Tags added: community-security mantic

** Description changed:

  Actually Mantic has 8.2.1 version
  A huge security issue is fixed with 8.4 : 
https://linuxsecurity.com/news/security-vulnerabilities/curl-8-4-released-for-addressing-a-big-security-vulnerability
  
  changelog: https://curl.se/changes.html
+ Available on Debian Sid: https://packages.debian.org/sid/curl

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

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

Title:
  please upgrade to 8.4 to address vulnerability

Status in curl package in Ubuntu:
  Confirmed

Bug description:
  Actually Mantic has 8.2.1 version
  A huge security issue is fixed with 8.4 : 
https://linuxsecurity.com/news/security-vulnerabilities/curl-8-4-released-for-addressing-a-big-security-vulnerability

  changelog: https://curl.se/changes.html
  Available on Debian Sid: https://packages.debian.org/sid/curl

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/curl/+bug/2039798/+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 2034996] Re: Mantic amd64 daily ISO also installs i386 packages

2023-10-19 Thread Jeremy Bícha

It is not a requirement for every package that can use another package
to list it in their dependencies.

I am closing this issue because Ubuntu Desktop intentionally includes
gamemode.

Steam is in the Snap Store. Steam is confusingly both 32-bit and 64-bit
because so many of the games it distributes are 32-bit.

** Changed in: ubuntu-meta (Ubuntu)
   Status: Incomplete => Won't Fix

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

Title:
  Mantic amd64 daily ISO also installs i386 packages

Status in ubuntu-meta package in Ubuntu:
  Won't Fix

Bug description:
  Mantic amd64 daily ISO installed these i386 packages

  libgcc-s1:i386 gcc-13-base:i386 libc6:i386 libcap2:i386 libcom-
  err2:i386 libdbus-1-3:i386 libgamemode0:i386 libgamemodeauto0:i386
  libgcrypt20:i386 libgpg-error0:i386 libgssapi-krb5-2:i386
  libidn2-0:i386 libk5crypto3:i386 libkeyutils1:i386 libkrb5-3:i386
  libkrb5support0:i386 liblz4-1:i386 liblzma5:i386 libnsl2:i386 libnss-
  nis:i386 libnss-nisplus:i386 libssl3:i386 libsystemd0:i386
  libtirpc3:i386 libunistring2:i386 libzstd1:i386

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/ubuntu-meta/+bug/2034996/+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 2038834] Re: GPU acceleration via VirGL is broken in qemu

2023-10-19 Thread Launchpad Bug Tracker

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

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

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

Title:
  GPU acceleration via VirGL is broken in qemu

Status in Release Notes for Ubuntu:
  New
Status in mesa package in Ubuntu:
  Confirmed

Bug description:
  This was reported by someone else upstream and is already fixed by
  https://gitlab.freedesktop.org/mesa/mesa/-/merge_requests/25580.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu-release-notes/+bug/2038834/+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 2039411] Re: Addition of ppa repository failing intermittently

2023-10-19 Thread Shubham Verma

Thanks @nosnilmot

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

Title:
  Addition of ppa repository failing intermittently

Status in software-properties package in Ubuntu:
  Confirmed

Bug description:
  I get following error intermittently when trying to add ppa repository:
  $ sudo add-apt-repository ppa:~longsleep/ubuntu/golang-backports
  Cannot add PPA: 'ppa:~longsleep/ubuntu/golang-backports'.
  The user named '~longsleep' has no PPA named 'ubuntu/golang-backports'
  Please choose from the following available PPAs:
   * 'bcmwl':  bcmwl
   * 'couchdb':  Apache CouchDB
   * 'couchdb-precise-backport':  Apache CouchDB with Erlang 18 for precise
   * 'createrepo-backports':  Createrepo Backports
   * 'firehol-backports':  Firehol Backports
   * 'golang-backports':  Golang Backports
   * 'golang-backports-dev':  Golang Backports Dev
   * 'iridium-browser-dev':  Iridium Browser Dev dependencies
   * 'pixel-extras':  Pixel extras
   * 'python2.7-backports':  Python 2.7 Backports
   * 'python3-m2crypto-backports':  Python 3 M2Crypto backports
   * 'stuff':  Stuff
   * 'ubuntu-pine64-flavour-makers':  Ubuntu Pine64 Makers PPA

  After multiple attempts, it may succeed, but the same above command sometimes 
may return following error as well (intermittently):
  $ sudo add-apt-repository ppa:~longsleep/ubuntu/golang-backports
  Traceback (most recent call last):
File "/usr/bin/add-apt-repository", line 137, in 
  shortcut = shortcut_handler(line)
File 
"/usr/lib/python3/dist-packages/softwareproperties/SoftwareProperties.py", line 
885, in shortcut_handler
  ret = factory(shortcut)
File "/usr/lib/python3/dist-packages/softwareproperties/ppa.py", line 469, 
in shortcut_handler
  return PPAShortcutHandler(shortcut)
File "/usr/lib/python3/dist-packages/softwareproperties/ppa.py", line 426, 
in __init__
  info = get_ppa_info(self.shortcut)
File "/usr/lib/python3/dist-packages/softwareproperties/ppa.py", line 392, 
in get_ppa_info
  _get_suggested_ppa_message(user, ppa))
File "/usr/lib/python3/dist-packages/softwareproperties/ppa.py", line 349, 
in _get_suggested_ppa_message
  lp_user = get_info_from_lp(LAUNCHPAD_USER_API % user)
File "/usr/lib/python3/dist-packages/softwareproperties/ppa.py", line 104, 
in get_info_from_lp
  return get_info_from_https(lp_url, True)
File "/usr/lib/python3/dist-packages/softwareproperties/ppa.py", line 98, 
in get_info_from_https
  return json.loads(data)
File "/usr/lib/python3.8/json/__init__.py", line 357, in loads
  return _default_decoder.decode(s)
File "/usr/lib/python3.8/json/decoder.py", line 337, in decode
  obj, end = self.raw_decode(s, idx=_w(s, 0).end())
File "/usr/lib/python3.8/json/decoder.py", line 355, in raw_decode
  raise JSONDecodeError("Expecting value", s, err.value) from None
  json.decoder.JSONDecodeError: Expecting value: line 1 column 1 (char 0)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/software-properties/+bug/2039411/+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 2034996] Re: Mantic amd64 daily ISO also installs i386 packages

2023-10-19 Thread wontfix

Packages that would use that i386 library or daemon should optimally
have them in their dependencies, no? The steam packages don't recommend
them. RetroArch recommends the x64 library. Lutris only suggests the
main gamemode package. Can a user install an i386 program from the snap
store?

If it is for snaps, isn't this the real answer?
https://github.com/ashuntu/gamemode/tree/add-snap-support

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

Title:
  Mantic amd64 daily ISO also installs i386 packages

Status in ubuntu-meta package in Ubuntu:
  Incomplete

Bug description:
  Mantic amd64 daily ISO installed these i386 packages

  libgcc-s1:i386 gcc-13-base:i386 libc6:i386 libcap2:i386 libcom-
  err2:i386 libdbus-1-3:i386 libgamemode0:i386 libgamemodeauto0:i386
  libgcrypt20:i386 libgpg-error0:i386 libgssapi-krb5-2:i386
  libidn2-0:i386 libk5crypto3:i386 libkeyutils1:i386 libkrb5-3:i386
  libkrb5support0:i386 liblz4-1:i386 liblzma5:i386 libnsl2:i386 libnss-
  nis:i386 libnss-nisplus:i386 libssl3:i386 libsystemd0:i386
  libtirpc3:i386 libunistring2:i386 libzstd1:i386

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/ubuntu-meta/+bug/2034996/+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 2039340] Re: On upgrade from 23.04 to 23.10, cannot login using Gnome or Ubuntu WM entries

[Touch-packages] [Bug 2039422] Re: Feature request: allow user to check 'Show password' by default in the WiFi password dialogue

[Touch-packages] [Bug 2039811] Re: Xorg freeze

[Touch-packages] [Bug 2039252] Re: [needs-packaging] The packages ntp and ntpsec are not equivalent

[Touch-packages] [Bug 2038650] Re: crash reports not sent to the Error Tracker

[Touch-packages] [Bug 2038650] Update Released

[Touch-packages] [Bug 2023545] Re: [UBUNTU 22.04] openssl with ibmca engine configured dumps core when creating a new certificate

[Touch-packages] [Bug 2033422] Re: openssl: backport to jammy "clear method store / query cache confusion"

[Touch-packages] [Bug 2038894] Re: Ubuntu 23.10 cloud images unexpected UDP listening port 5353

[Touch-packages] [Bug 2038894] Re: Ubuntu 23.10 cloud images unexpected UDP listening port 5353

[Touch-packages] [Bug 2023545] Re: [UBUNTU 22.04] openssl with ibmca engine configured dumps core when creating a new certificate

[Touch-packages] [Bug 1794064] Re: Clicking a hyperlink in a PDF fails to open it if the default browser is a snap

[Touch-packages] [Bug 2039873] Re: liblxc-dev was built with LXC_DEVEL=1 in Ubuntu Jammy/Kinetic

[Touch-packages] [Bug 2038894] Re: Ubuntu 23.10 cloud images unexpected UDP listening port 5353

[Touch-packages] [Bug 2039873] [NEW] liblxc-dev was built with LXC_DEVEL=1 in Ubuntu Jammy/Kinetic

[Touch-packages] [Bug 2039503] Re: package network-manager 1.44.2-1ubuntu1 failed to install/upgrade: installed network-manager package post-installation script subprocess returned error exit status 1

[Touch-packages] [Bug 2039503] Update Released

[Touch-packages] [Bug 2039868] Re: amdgpu reset during usage of firefox

[Touch-packages] [Bug 2038807] Re: /usr/libexec/packagekitd:6:g_assertion_message:g_assertion_message_expr:pk_transaction_dispose:pk_transaction_dispose:g_object_unref

[Touch-packages] [Bug 2037667] Re: Regression on Jammy's kernel 5.15 when creating ip6gre and vti6 tunnels

[Touch-packages] [Bug 1794064] Re: Clicking a hyperlink in a PDF fails to open it if the default browser is a snap

[Touch-packages] [Bug 1907878] Re: wrong var declaration in if-up.d/resolved (nm-dispatcher[54417]: /etc/network/if-up.d/resolved: 12: mystatedir: not found)

[Touch-packages] [Bug 2039815] [NEW] Update to at least systemd v254 in lunar

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

[Touch-packages] [Bug 2039811] [NEW] Xorg freeze

[Touch-packages] [Bug 794315] Re: lightdm forgets to source /etc/profile and ~/.profile

[Touch-packages] [Bug 1978351] Re: MITM vector: ifupdown puts .domains TLD in resolv.conf

[Touch-packages] [Bug 2039798] [NEW] please upgrade to 8.4 to address vulnerability

[Touch-packages] [Bug 2034996] Re: Mantic amd64 daily ISO also installs i386 packages

[Touch-packages] [Bug 2038834] Re: GPU acceleration via VirGL is broken in qemu

[Touch-packages] [Bug 2039411] Re: Addition of ppa repository failing intermittently

[Touch-packages] [Bug 2034996] Re: Mantic amd64 daily ISO also installs i386 packages

32 matches

Site Navigation

Mail list logo

Footer information