date:20231121

** Also affects: systemd (Ubuntu Mantic)
   Importance: Undecided
   Status: New

** Also affects: systemd (Ubuntu Lunar)
   Importance: Undecided
   Status: New

** Changed in: systemd (Ubuntu Lunar)
   Status: New => Won't Fix

** Changed in: systemd (Ubuntu Mantic)
   Status: New => Won't Fix

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

Title:
  Under ubuntu core/core-desktop, /etc/default/locale is not modifiable

Status in systemd package in Ubuntu:
  New
Status in systemd source package in Jammy:
  New
Status in systemd source package in Lunar:
  Won't Fix
Status in systemd source package in Mantic:
  Won't Fix

Bug description:
  [Impact]

  When working with ubuntu core or ubuntu core desktop, neither
  */etc/default/locale* nor */etc/default/keyboard* are modifiable, so
  it's not possible to set the global keyboard or the global language.
  This is required to allow to set the GDM language, and the default one
  during installation.

  The first half of the solution is to create the folder
  */etc/writable/default*, and make soft-links from
  */etc/default/locale* to */etc/writable/default/locale* and from
  */etc/default/keyboard* to */etc/writable/default/keyboard*, just like
  it is already being done with */etc/hostname*, */etc/issue*,
  */etc/localtime*, */etc/motd* and , */etc/timezone*.

  This solution, unfortunately, isn't complete. Although any application
  that just reads the files will work, not all of the applications that
  write to them will; specifically the systemd utilities that set the
  contents for those files, because they don't open the file directly;
  instead, they create first the new file in the same folder than the
  old one, fill its contents, and only then delete the old one and
  rename the new one. To solve this, systemd in Ubuntu already has
  several patches that detect if a file is a soft-link, in which case it
  replaces the old path with the destination one.

  Currently I have in place a patch for Ubuntu Core Desktop that
  implements both changes for both */etc/default/locale* and
  */etc/default/keyboard*.

  [Test plan]

  Using *localectl set-lang LANG="xx_YY.UTF-8"* should change the locale
  to the specified one. Also, *localectl* should return the current
  locale.

  [Where problems could occur]

  In general, applications just read the content of the file and use the
  DBus interface to set the locale, so only those applications that
  modify by themselves the */etc/default/keyboard* and/or
  */etc/default/locale* would present a problem, in which case they
  would require specific patches. Anyway, those applications neither
  would work with the current state (with those files in a read-only
  filesystem).

  [Other info]

  For Noble, this will be addressed when we merge systemd v255 from
  Debian. This is only needed on core, so we don't need to fix for
  Mantic or Lunar.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/2035122/+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 2044014] Re: networkmanager crashes on configuring wireguard connection via nm-connection-editor

2023-11-21 Thread Danilo Egea Gondolfo

Hi,

I can't find anything wrong in your configuration. And that makes me
wonder if you have another YAML with the same wg0 interface in it. We
recently fixed a bug in Network Manager that was leading to duplication
in the configuration. You might have been affected by this bug when you
upgraded to Mantic.

If you grep /etc/netplan by the interface name, do you see more than one
file? Something like this "sudo grep wg0 /etc/netplan/*". If you find
the same interface in more than one file, try to remove them and create
the connection again using the GUI. The problem might be that you have
multiple YAMLs with the same interface. Netplan will merge them in a
single configuration and the result might be a broken config.

Let me know if it helps.

Thanks!

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

Title:
  networkmanager crashes on configuring wireguard connection via nm-
  connection-editor

Status in network-manager package in Ubuntu:
  Triaged

Bug description:
  when configuring a new wireguard connection both via nm-connection-editor and 
the settings app, NetworkManager crashes and restarts, with the error message 
"Message recipient disconnected from message bus without replying".
  Currently, I'm unable to add wireguard connections at all.
  Also, I have netplan.io/now 0.107-5ubuntu1~ppa3 installed to outrule 
https://bugs.launchpad.net/ubuntu/+source/netplan.io/+bug/2039821

  Ubuntu 23.10
  network-manager/mantic-updates,now 1.44.2-1ubuntu1.2 amd64
  netplan.io/now 0.107-5ubuntu1~ppa3

  ProblemType: Bug
  DistroRelease: Ubuntu 23.10
  Package: network-manager 1.44.2-1ubuntu1.2
  ProcVersionSignature: Ubuntu 6.5.0-10.10-generic 6.5.3
  Uname: Linux 6.5.0-10-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  ApportVersion: 2.27.0-0ubuntu5
  Architecture: amd64
  CasperMD5CheckResult: unknown
  CurrentDesktop: ubuntu:GNOME
  Date: Mon Nov 20 20:10:40 2023
  IfupdownConfig:
   # interfaces(5) file used by ifup(8) and ifdown(8)
   auto lo
   iface lo inet loopback
  InstallationDate: Installed on 2018-05-15 (2015 days ago)
  InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426)
  IpRoute:
   default via  dev enp0s31f6 proto dhcp src  metric 100
   /24 dev enp0s31f6 proto kernel scope link src  metric 
100
   169.254.0.0/16 dev enp0s31f6 scope link metric 1000
  NetworkManager.state:
   [main]
   NetworkingEnabled=true
   WirelessEnabled=false
   WWANEnabled=false
  ProcEnviron:
   LANG=de_DE.UTF-8
   PATH=(custom, no user)
   SHELL=/bin/bash
   TERM=xterm-256color
  SourcePackage: network-manager
  UpgradeStatus: Upgraded to mantic on 2023-11-05 (15 days ago)
  http_proxy: http://:3128
  nmcli-nm:
   RUNNING  VERSION  STATE  STARTUP  CONNECTIVITY  NETWORKING  WIFI-HW  
WIFI  WWAN-HW  WWAN
   running  1.44.2   connected  started  full  enabled enabled  
disabled  missing  disabled
  no_proxy: 127.0.0.1,172.16.0.0/12,10.0.0.0/8,192.168.0.0/16,

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/2044014/+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 2035122] Re: Under ubuntu core/core-desktop, /etc/default/locale is not modifiable

** Description changed:

  [Impact]
  
  When working with ubuntu core or ubuntu core desktop, neither
  */etc/default/locale* nor */etc/default/keyboard* are modifiable, so
  it's not possible to set the global keyboard or the global language.
  This is required to allow to set the GDM language, and the default one
  during installation.
  
  The first half of the solution is to create the folder
  */etc/writable/default*, and make soft-links from */etc/default/locale*
  to */etc/writable/default/locale* and from */etc/default/keyboard* to
  */etc/writable/default/keyboard*, just like it is already being done
  with */etc/hostname*, */etc/issue*, */etc/localtime*, */etc/motd* and ,
  */etc/timezone*.
  
  This solution, unfortunately, isn't complete. Although any application
  that just reads the files will work, not all of the applications that
  write to them will; specifically the systemd utilities that set the
  contents for those files, because they don't open the file directly;
  instead, they create first the new file in the same folder than the old
  one, fill its contents, and only then delete the old one and rename the
  new one. To solve this, systemd in Ubuntu already has several patches
  that detect if a file is a soft-link, in which case it replaces the old
  path with the destination one.
  
  Currently I have in place a patch for Ubuntu Core Desktop that
  implements both changes for both */etc/default/locale* and
  */etc/default/keyboard*.
  
  [Test plan]
  
  Using *localectl set-lang LANG="xx_YY.UTF-8"* should change the locale
  to the specified one. Also, *localectl* should return the current
  locale.
  
  [Where problems could occur]
  
  In general, applications just read the content of the file and use the
  DBus interface to set the locale, so only those applications that modify
  by themselves the */etc/default/keyboard* and/or */etc/default/locale*
  would present a problem, in which case they would require specific
  patches. Anyway, those applications neither would work with the current
  state (with those files in a read-only filesystem).
+ 
+ [Other info]
+ 
+ For Noble, this will be addressed when we merge systemd v255 from
+ Debian. This is only needed on core, so we don't need to fix for Mantic
+ or 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/2035122

Title:
  Under ubuntu core/core-desktop, /etc/default/locale is not modifiable

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

Bug description:
  [Impact]

  When working with ubuntu core or ubuntu core desktop, neither
  */etc/default/locale* nor */etc/default/keyboard* are modifiable, so
  it's not possible to set the global keyboard or the global language.
  This is required to allow to set the GDM language, and the default one
  during installation.

  The first half of the solution is to create the folder
  */etc/writable/default*, and make soft-links from
  */etc/default/locale* to */etc/writable/default/locale* and from
  */etc/default/keyboard* to */etc/writable/default/keyboard*, just like
  it is already being done with */etc/hostname*, */etc/issue*,
  */etc/localtime*, */etc/motd* and , */etc/timezone*.

  This solution, unfortunately, isn't complete. Although any application
  that just reads the files will work, not all of the applications that
  write to them will; specifically the systemd utilities that set the
  contents for those files, because they don't open the file directly;
  instead, they create first the new file in the same folder than the
  old one, fill its contents, and only then delete the old one and
  rename the new one. To solve this, systemd in Ubuntu already has
  several patches that detect if a file is a soft-link, in which case it
  replaces the old path with the destination one.

  Currently I have in place a patch for Ubuntu Core Desktop that
  implements both changes for both */etc/default/locale* and
  */etc/default/keyboard*.

  [Test plan]

  Using *localectl set-lang LANG="xx_YY.UTF-8"* should change the locale
  to the specified one. Also, *localectl* should return the current
  locale.

  [Where problems could occur]

  In general, applications just read the content of the file and use the
  DBus interface to set the locale, so only those applications that
  modify by themselves the */etc/default/keyboard* and/or
  */etc/default/locale* would present a problem, in which case they
  would require specific patches. Anyway, those applications neither
  would work with the current state (with those files in a read-only
  filesystem).

  [Other info]

  For Noble, this will be addressed when we merge systemd v255 from
  Debian. This is only needed on core, so we don't need to fix for
  Mantic or Lunar.

To manage notifications about this bug go to:

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

2023-11-21 Thread Georgia Garcia

The autopkgtests for apparmor failed for the evince update because the
test requires the apparmor update which is also in proposed
https://launchpad.net/ubuntu/+source/apparmor/3.0.4-2ubuntu2.3 but it is
not a regression.

-- 
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:
  Fix Committed
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 2030684] Re: tzname[1] empty after tzset() with env TZ="UTC"

2023-11-21 Thread Sergio Durigan Junior

According to comment #10 from Athos, the php8.2 task has been added to
this bug only to serve as a reminder for a future investigation when
time permits.  Since everything else affected by the bug has been marked
as Fix Released, I removed the update-excuses tag.

** Tags removed: update-excuse

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

Title:
  tzname[1] empty after tzset() with env TZ="UTC"

Status in django-mailman3 package in Ubuntu:
  Fix Released
Status in php8.2 package in Ubuntu:
  Triaged
Status in postgresql-15 package in Ubuntu:
  Fix Committed
Status in python-django package in Ubuntu:
  Fix Released
Status in systemd package in Ubuntu:
  Invalid
Status in tzdata package in Ubuntu:
  Fix Released
Status in tzdata package in Debian:
  Fix Released

Bug description:
  The following program prints different output when run with tzdata
  2023c-7ubuntu1 from mantic, versus tzdata 2023c-8ubuntu1 from mantic-
  proposed:

  root@mantic:~# cat bug.c 
  #include 
  #include 
  #include 
  #include 
  #include 

  int main(void) {
  int r;

  r = setenv("TZ", ":UTC", 1);
  if (r < 0) {
  printf("Failed to set TZ env var: %s\n", strerror(errno));
  return 1;
  }

  tzset();

  printf("timezone = %lu, daylight = %d\n", timezone, daylight);
  printf("tzname[0] = %s, tzname[1] = %s\n", tzname[0], tzname[1]);
  }

  root@mantic:~# gcc bug.c
  root@mantic:~# ./a.out 
  timezone = 0, daylight = 0
  tzname[0] = UTC, tzname[1] = UTC
  root@mantic:~# apt-cache policy tzdata
  tzdata:
Installed: 2023c-7ubuntu1
Candidate: 2023c-7ubuntu1
Version table:
   *** 2023c-7ubuntu1 500
  500 http://archive.ubuntu.com/ubuntu mantic/main amd64 Packages
  100 /var/lib/dpkg/status

  If I install tzdata from mantic-proposed, I get different output:

  root@mantic:~# vi /etc/apt/sources.list
  root@mantic:~# apt update && apt install tzdata
  Hit:1 http://archive.ubuntu.com/ubuntu mantic InRelease
  Hit:2 http://security.ubuntu.com/ubuntu mantic-security InRelease
  Get:3 http://archive.ubuntu.com/ubuntu mantic-proposed InRelease [118 kB]
  Hit:4 http://archive.ubuntu.com/ubuntu mantic-updates InRelease
  Hit:5 http://archive.ubuntu.com/ubuntu mantic-backports InRelease
  Get:6 http://archive.ubuntu.com/ubuntu mantic-proposed/main amd64 Packages 
[35.9 kB]
  Get:7 http://archive.ubuntu.com/ubuntu mantic-proposed/main Translation-en 
[14.8 kB]
  Get:8 http://archive.ubuntu.com/ubuntu mantic-proposed/main amd64 DEP-11 
Metadata [2376 B]
  Get:9 http://archive.ubuntu.com/ubuntu mantic-proposed/main amd64 c-n-f 
Metadata [1004 B]
  Get:10 http://archive.ubuntu.com/ubuntu mantic-proposed/restricted amd64 
Packages [15.9 kB]
  Get:11 http://archive.ubuntu.com/ubuntu mantic-proposed/restricted 
Translation-en [3564 B]
  Get:12 http://archive.ubuntu.com/ubuntu mantic-proposed/restricted amd64 
c-n-f Metadata [336 B]
  Fetched 192 kB in 1s (324 kB/s) 
  Reading package lists... Done
  Building dependency tree... Done
  Reading state information... Done
  72 packages can be upgraded. Run 'apt list --upgradable' to see them.
  root@mantic:~# apt install tzdata=2023c-8ubuntu1
  Reading package lists... Done
  Building dependency tree... Done
  Reading state information... Done
  The following packages were automatically installed and are no longer 
required:
libefiboot1 libefivar1
  Use 'apt autoremove' to remove them.
  The following packages will be upgraded:
tzdata
  1 upgraded, 0 newly installed, 0 to remove and 72 not upgraded.
  Need to get 269 kB of archives.
  After this operation, 142 kB disk space will be freed.
  Get:1 http://archive.ubuntu.com/ubuntu mantic-proposed/main amd64 tzdata all 
2023c-8ubuntu1 [269 kB]
  Fetched 269 kB in 0s (867 kB/s)
  Preconfiguring packages ...
  (Reading database ... 39935 files and directories currently installed.)
  Preparing to unpack .../tzdata_2023c-8ubuntu1_all.deb ...
  Unpacking tzdata (2023c-8ubuntu1) over (2023c-7ubuntu1) ...
  Setting up tzdata (2023c-8ubuntu1) ...

  Current default time zone: 'Etc/UTC'
  Local time is now:  Mon Aug  7 21:18:35 UTC 2023.
  Universal Time is now:  Mon Aug  7 21:18:35 UTC 2023.
  Run 'dpkg-reconfigure tzdata' if you wish to change it.

  Scanning processes... 


 
  Scanning candidates...


 

  Restarting services...
  Service

[Touch-packages] [Bug 1993370] Re: Cannot install proprietary Broadcom WiFi drivers on Ubuntu Studio Jammy 22.04.2 and Kinetic

2023-11-21 Thread Aaron Rainbolt

Followed the test plan using the latest daily image of Ubuntu Studio
Jammy. Everything worked as expected (no error in terminal when
selecting "Using Broadcom 802.11 Linux STA wireless driver from bcmwl-
kernel-source (proprietary)"), driver installed properly and allowed me
to connect to WiFi. Driver also continued to work after a reboot. I
verified that the version of software-properties on my system is the one
in Proposed.

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

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

Title:
  Cannot install proprietary Broadcom WiFi drivers on Ubuntu Studio
  Jammy 22.04.2 and Kinetic

Status in software-properties package in Ubuntu:
  Fix Released
Status in software-properties source package in Jammy:
  Fix Committed
Status in software-properties source package in Kinetic:
  Won't Fix

Bug description:
  [Impact]
  software-properties-qt will crash when a user tries to install drivers for 
Broadcom wireless devices.

  This same change has been made in the software-properties-gtk frontend
  (see bug 1969460) without any issues.

  There are also problems in the Error Tracker for this crash:
  https://errors.ubuntu.com/problem/1c41600298c08b5dfc2d86ee90ad27ef56cd4524
  https://errors.ubuntu.com/problem/49f4156af6d9d2367fc480105e19064da3575269

  [Test Plan]
  1) Install Ubuntu Studio 22.04.3 on a system with Broadcom WiFi
  2) Reboot into the installed sytem
  3) Open a terminal and run 'sudo software-properties-kde'
  4) Click the 'Additional Drivers' tab
  5) Click "Using Broadcom 802.11 Linux STA wireless driver source from 
bcmwl-kernel-source (proprietary)".

  With the version of the package in -updates you'll observe the
  following Traceback in the terminal:

  Traceback (most recent call last):
    File 
"/usr/lib/python3/dist-packages/softwareproperties/qt/SoftwarePropertiesQt.py", 
line 1061, in on_driver_selection_changed
  modules_package_obj = self.apt_cache[modules_package]
  TypeError: Expected a string or a pair of strings

  With the version of the package in -proposed you will not.

  [ Where problems could occur ]
  It's possible we'll hide a real error as we are catching all TypeErrors, but 
given we haven't heard of any issues with other stable releases and that this 
was fixed in software-properties-gtk in the same way I think it is safe.

  Hardware: HP Elitebook 8570p, 16 GB RAM, 120 GB SSD, 3rd Gen Intel
  Core i5, UEFI, no secure boot, Broadcom WiFi.

  OS: Ubuntu Studio Kinetic, Final ISO

  Steps to reproduce:

  1. Boot the Ubuntu Studio ISO on a system with Broadcom WiFi, and install the 
system normally. (No encryption, allow Internet access during installation 
using some method of connectivity other than WiFi.)
  2. Reboot and log into the newly installed system.
  3. Open a terminal and run "sudo software-properties-kde".
  4. Click "Additional Drivers" in the window that pops up.
  5. Click "Using Broadcom 802.11 Linux STA wireless driver source from 
bcmwl-kernel-source (proprietary)".

  Expected result: The Apply Changes button should become clickable,
  allowing the user to install the driver.

  Actual result: The button remains grayed out, and the following error
  message is printed in the terminal:

  Traceback (most recent call last):
    File 
"/usr/lib/python3/dist-packages/softwareproperties/qt/SoftwarePropertiesQt.py", 
line 1063, in on_driver_selection_changed
  modules_package_obj = self.apt_cache[modules_package]
  TypeError: Expected a string or a pair of strings

  ProblemType: BugDistroRelease: Ubuntu 22.10
  Package: software-properties-qt 0.99.27
  ProcVersionSignature: Ubuntu 5.19.0-1007.7-lowlatency 5.19.7
  Uname: Linux 5.19.0-1007-lowlatency x86_64
  ApportVersion: 2.23.1-0ubuntu3
  Architecture: amd64
  CasperMD5CheckResult: unknown
  CurrentDesktop: KDE
  Date: Tue Oct 18 21:33:51 2022
  InstallationDate: Installed on 2022-10-19 (0 days ago)
  InstallationMedia: Ubuntu-Studio 22.10 "Kinetic Kudu" - Release amd64 
(20221017.1)
  PackageArchitecture: allSourcePackage: software-properties
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/software-properties/+bug/1993370/+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 2044014] Re: networkmanager crashes on configuring wireguard connection via nm-connection-editor

actually, it doesn't matter if any dns setting is set or left empty =>
the message stays the same.

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

Title:
  networkmanager crashes on configuring wireguard connection via nm-
  connection-editor

Status in network-manager package in Ubuntu:
  Triaged

Bug description:
  when configuring a new wireguard connection both via nm-connection-editor and 
the settings app, NetworkManager crashes and restarts, with the error message 
"Message recipient disconnected from message bus without replying".
  Currently, I'm unable to add wireguard connections at all.
  Also, I have netplan.io/now 0.107-5ubuntu1~ppa3 installed to outrule 
https://bugs.launchpad.net/ubuntu/+source/netplan.io/+bug/2039821

  Ubuntu 23.10
  network-manager/mantic-updates,now 1.44.2-1ubuntu1.2 amd64
  netplan.io/now 0.107-5ubuntu1~ppa3

  ProblemType: Bug
  DistroRelease: Ubuntu 23.10
  Package: network-manager 1.44.2-1ubuntu1.2
  ProcVersionSignature: Ubuntu 6.5.0-10.10-generic 6.5.3
  Uname: Linux 6.5.0-10-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  ApportVersion: 2.27.0-0ubuntu5
  Architecture: amd64
  CasperMD5CheckResult: unknown
  CurrentDesktop: ubuntu:GNOME
  Date: Mon Nov 20 20:10:40 2023
  IfupdownConfig:
   # interfaces(5) file used by ifup(8) and ifdown(8)
   auto lo
   iface lo inet loopback
  InstallationDate: Installed on 2018-05-15 (2015 days ago)
  InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426)
  IpRoute:
   default via  dev enp0s31f6 proto dhcp src  metric 100
   /24 dev enp0s31f6 proto kernel scope link src  metric 
100
   169.254.0.0/16 dev enp0s31f6 scope link metric 1000
  NetworkManager.state:
   [main]
   NetworkingEnabled=true
   WirelessEnabled=false
   WWANEnabled=false
  ProcEnviron:
   LANG=de_DE.UTF-8
   PATH=(custom, no user)
   SHELL=/bin/bash
   TERM=xterm-256color
  SourcePackage: network-manager
  UpgradeStatus: Upgraded to mantic on 2023-11-05 (15 days ago)
  http_proxy: http://:3128
  nmcli-nm:
   RUNNING  VERSION  STATE  STARTUP  CONNECTIVITY  NETWORKING  WIFI-HW  
WIFI  WWAN-HW  WWAN
   running  1.44.2   connected  started  full  enabled enabled  
disabled  missing  disabled
  no_proxy: 127.0.0.1,172.16.0.0/12,10.0.0.0/8,192.168.0.0/16,

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/2044014/+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 2044014] Re: networkmanager crashes on configuring wireguard connection via nm-connection-editor

** Attachment added: "Bildschirmfoto vom 2023-11-21 19-48-26.png"
   
https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/2044014/+attachment/5721830/+files/Bildschirmfoto%20vom%202023-11-21%2019-48-26.png

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

Title:
  networkmanager crashes on configuring wireguard connection via nm-
  connection-editor

Status in network-manager package in Ubuntu:
  Triaged

Bug description:
  when configuring a new wireguard connection both via nm-connection-editor and 
the settings app, NetworkManager crashes and restarts, with the error message 
"Message recipient disconnected from message bus without replying".
  Currently, I'm unable to add wireguard connections at all.
  Also, I have netplan.io/now 0.107-5ubuntu1~ppa3 installed to outrule 
https://bugs.launchpad.net/ubuntu/+source/netplan.io/+bug/2039821

  Ubuntu 23.10
  network-manager/mantic-updates,now 1.44.2-1ubuntu1.2 amd64
  netplan.io/now 0.107-5ubuntu1~ppa3

  ProblemType: Bug
  DistroRelease: Ubuntu 23.10
  Package: network-manager 1.44.2-1ubuntu1.2
  ProcVersionSignature: Ubuntu 6.5.0-10.10-generic 6.5.3
  Uname: Linux 6.5.0-10-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  ApportVersion: 2.27.0-0ubuntu5
  Architecture: amd64
  CasperMD5CheckResult: unknown
  CurrentDesktop: ubuntu:GNOME
  Date: Mon Nov 20 20:10:40 2023
  IfupdownConfig:
   # interfaces(5) file used by ifup(8) and ifdown(8)
   auto lo
   iface lo inet loopback
  InstallationDate: Installed on 2018-05-15 (2015 days ago)
  InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426)
  IpRoute:
   default via  dev enp0s31f6 proto dhcp src  metric 100
   /24 dev enp0s31f6 proto kernel scope link src  metric 
100
   169.254.0.0/16 dev enp0s31f6 scope link metric 1000
  NetworkManager.state:
   [main]
   NetworkingEnabled=true
   WirelessEnabled=false
   WWANEnabled=false
  ProcEnviron:
   LANG=de_DE.UTF-8
   PATH=(custom, no user)
   SHELL=/bin/bash
   TERM=xterm-256color
  SourcePackage: network-manager
  UpgradeStatus: Upgraded to mantic on 2023-11-05 (15 days ago)
  http_proxy: http://:3128
  nmcli-nm:
   RUNNING  VERSION  STATE  STARTUP  CONNECTIVITY  NETWORKING  WIFI-HW  
WIFI  WWAN-HW  WWAN
   running  1.44.2   connected  started  full  enabled enabled  
disabled  missing  disabled
  no_proxy: 127.0.0.1,172.16.0.0/12,10.0.0.0/8,192.168.0.0/16,

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/2044014/+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 2044014] Re: networkmanager crashes on configuring wireguard connection via nm-connection-editor

** Attachment added: "unitlog.log.txt"
   
https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/2044014/+attachment/5721831/+files/unitlog.log.txt

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

Title:
  networkmanager crashes on configuring wireguard connection via nm-
  connection-editor

Status in network-manager package in Ubuntu:
  Triaged

Bug description:
  when configuring a new wireguard connection both via nm-connection-editor and 
the settings app, NetworkManager crashes and restarts, with the error message 
"Message recipient disconnected from message bus without replying".
  Currently, I'm unable to add wireguard connections at all.
  Also, I have netplan.io/now 0.107-5ubuntu1~ppa3 installed to outrule 
https://bugs.launchpad.net/ubuntu/+source/netplan.io/+bug/2039821

  Ubuntu 23.10
  network-manager/mantic-updates,now 1.44.2-1ubuntu1.2 amd64
  netplan.io/now 0.107-5ubuntu1~ppa3

  ProblemType: Bug
  DistroRelease: Ubuntu 23.10
  Package: network-manager 1.44.2-1ubuntu1.2
  ProcVersionSignature: Ubuntu 6.5.0-10.10-generic 6.5.3
  Uname: Linux 6.5.0-10-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  ApportVersion: 2.27.0-0ubuntu5
  Architecture: amd64
  CasperMD5CheckResult: unknown
  CurrentDesktop: ubuntu:GNOME
  Date: Mon Nov 20 20:10:40 2023
  IfupdownConfig:
   # interfaces(5) file used by ifup(8) and ifdown(8)
   auto lo
   iface lo inet loopback
  InstallationDate: Installed on 2018-05-15 (2015 days ago)
  InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426)
  IpRoute:
   default via  dev enp0s31f6 proto dhcp src  metric 100
   /24 dev enp0s31f6 proto kernel scope link src  metric 
100
   169.254.0.0/16 dev enp0s31f6 scope link metric 1000
  NetworkManager.state:
   [main]
   NetworkingEnabled=true
   WirelessEnabled=false
   WWANEnabled=false
  ProcEnviron:
   LANG=de_DE.UTF-8
   PATH=(custom, no user)
   SHELL=/bin/bash
   TERM=xterm-256color
  SourcePackage: network-manager
  UpgradeStatus: Upgraded to mantic on 2023-11-05 (15 days ago)
  http_proxy: http://:3128
  nmcli-nm:
   RUNNING  VERSION  STATE  STARTUP  CONNECTIVITY  NETWORKING  WIFI-HW  
WIFI  WWAN-HW  WWAN
   running  1.44.2   connected  started  full  enabled enabled  
disabled  missing  disabled
  no_proxy: 127.0.0.1,172.16.0.0/12,10.0.0.0/8,192.168.0.0/16,

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/2044014/+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 2044014] Re: networkmanager crashes on configuring wireguard connection via nm-connection-editor

** Attachment added: "Bildschirmfoto vom 2023-11-21 19-45-58.png"
   
https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/2044014/+attachment/5721829/+files/Bildschirmfoto%20vom%202023-11-21%2019-45-58.png

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

Title:
  networkmanager crashes on configuring wireguard connection via nm-
  connection-editor

Status in network-manager package in Ubuntu:
  Triaged

Bug description:
  when configuring a new wireguard connection both via nm-connection-editor and 
the settings app, NetworkManager crashes and restarts, with the error message 
"Message recipient disconnected from message bus without replying".
  Currently, I'm unable to add wireguard connections at all.
  Also, I have netplan.io/now 0.107-5ubuntu1~ppa3 installed to outrule 
https://bugs.launchpad.net/ubuntu/+source/netplan.io/+bug/2039821

  Ubuntu 23.10
  network-manager/mantic-updates,now 1.44.2-1ubuntu1.2 amd64
  netplan.io/now 0.107-5ubuntu1~ppa3

  ProblemType: Bug
  DistroRelease: Ubuntu 23.10
  Package: network-manager 1.44.2-1ubuntu1.2
  ProcVersionSignature: Ubuntu 6.5.0-10.10-generic 6.5.3
  Uname: Linux 6.5.0-10-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  ApportVersion: 2.27.0-0ubuntu5
  Architecture: amd64
  CasperMD5CheckResult: unknown
  CurrentDesktop: ubuntu:GNOME
  Date: Mon Nov 20 20:10:40 2023
  IfupdownConfig:
   # interfaces(5) file used by ifup(8) and ifdown(8)
   auto lo
   iface lo inet loopback
  InstallationDate: Installed on 2018-05-15 (2015 days ago)
  InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426)
  IpRoute:
   default via  dev enp0s31f6 proto dhcp src  metric 100
   /24 dev enp0s31f6 proto kernel scope link src  metric 
100
   169.254.0.0/16 dev enp0s31f6 scope link metric 1000
  NetworkManager.state:
   [main]
   NetworkingEnabled=true
   WirelessEnabled=false
   WWANEnabled=false
  ProcEnviron:
   LANG=de_DE.UTF-8
   PATH=(custom, no user)
   SHELL=/bin/bash
   TERM=xterm-256color
  SourcePackage: network-manager
  UpgradeStatus: Upgraded to mantic on 2023-11-05 (15 days ago)
  http_proxy: http://:3128
  nmcli-nm:
   RUNNING  VERSION  STATE  STARTUP  CONNECTIVITY  NETWORKING  WIFI-HW  
WIFI  WWAN-HW  WWAN
   running  1.44.2   connected  started  full  enabled enabled  
disabled  missing  disabled
  no_proxy: 127.0.0.1,172.16.0.0/12,10.0.0.0/8,192.168.0.0/16,

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/2044014/+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 2044014] Re: networkmanager crashes on configuring wireguard connection via nm-connection-editor

** Attachment added: "Bildschirmfoto vom 2023-11-21 19-46-12.png"
   
https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/2044014/+attachment/5721828/+files/Bildschirmfoto%20vom%202023-11-21%2019-46-12.png

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

Title:
  networkmanager crashes on configuring wireguard connection via nm-
  connection-editor

Status in network-manager package in Ubuntu:
  Triaged

Bug description:
  when configuring a new wireguard connection both via nm-connection-editor and 
the settings app, NetworkManager crashes and restarts, with the error message 
"Message recipient disconnected from message bus without replying".
  Currently, I'm unable to add wireguard connections at all.
  Also, I have netplan.io/now 0.107-5ubuntu1~ppa3 installed to outrule 
https://bugs.launchpad.net/ubuntu/+source/netplan.io/+bug/2039821

  Ubuntu 23.10
  network-manager/mantic-updates,now 1.44.2-1ubuntu1.2 amd64
  netplan.io/now 0.107-5ubuntu1~ppa3

  ProblemType: Bug
  DistroRelease: Ubuntu 23.10
  Package: network-manager 1.44.2-1ubuntu1.2
  ProcVersionSignature: Ubuntu 6.5.0-10.10-generic 6.5.3
  Uname: Linux 6.5.0-10-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  ApportVersion: 2.27.0-0ubuntu5
  Architecture: amd64
  CasperMD5CheckResult: unknown
  CurrentDesktop: ubuntu:GNOME
  Date: Mon Nov 20 20:10:40 2023
  IfupdownConfig:
   # interfaces(5) file used by ifup(8) and ifdown(8)
   auto lo
   iface lo inet loopback
  InstallationDate: Installed on 2018-05-15 (2015 days ago)
  InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426)
  IpRoute:
   default via  dev enp0s31f6 proto dhcp src  metric 100
   /24 dev enp0s31f6 proto kernel scope link src  metric 
100
   169.254.0.0/16 dev enp0s31f6 scope link metric 1000
  NetworkManager.state:
   [main]
   NetworkingEnabled=true
   WirelessEnabled=false
   WWANEnabled=false
  ProcEnviron:
   LANG=de_DE.UTF-8
   PATH=(custom, no user)
   SHELL=/bin/bash
   TERM=xterm-256color
  SourcePackage: network-manager
  UpgradeStatus: Upgraded to mantic on 2023-11-05 (15 days ago)
  http_proxy: http://:3128
  nmcli-nm:
   RUNNING  VERSION  STATE  STARTUP  CONNECTIVITY  NETWORKING  WIFI-HW  
WIFI  WWAN-HW  WWAN
   running  1.44.2   connected  started  full  enabled enabled  
disabled  missing  disabled
  no_proxy: 127.0.0.1,172.16.0.0/12,10.0.0.0/8,192.168.0.0/16,

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/2044014/+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 2044014] Re: networkmanager crashes on configuring wireguard connection via nm-connection-editor

** Attachment added: "Bildschirmfoto vom 2023-11-21 19-46-08.png"
   
https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/2044014/+attachment/5721827/+files/Bildschirmfoto%20vom%202023-11-21%2019-46-08.png

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

Title:
  networkmanager crashes on configuring wireguard connection via nm-
  connection-editor

Status in network-manager package in Ubuntu:
  Triaged

Bug description:
  when configuring a new wireguard connection both via nm-connection-editor and 
the settings app, NetworkManager crashes and restarts, with the error message 
"Message recipient disconnected from message bus without replying".
  Currently, I'm unable to add wireguard connections at all.
  Also, I have netplan.io/now 0.107-5ubuntu1~ppa3 installed to outrule 
https://bugs.launchpad.net/ubuntu/+source/netplan.io/+bug/2039821

  Ubuntu 23.10
  network-manager/mantic-updates,now 1.44.2-1ubuntu1.2 amd64
  netplan.io/now 0.107-5ubuntu1~ppa3

  ProblemType: Bug
  DistroRelease: Ubuntu 23.10
  Package: network-manager 1.44.2-1ubuntu1.2
  ProcVersionSignature: Ubuntu 6.5.0-10.10-generic 6.5.3
  Uname: Linux 6.5.0-10-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  ApportVersion: 2.27.0-0ubuntu5
  Architecture: amd64
  CasperMD5CheckResult: unknown
  CurrentDesktop: ubuntu:GNOME
  Date: Mon Nov 20 20:10:40 2023
  IfupdownConfig:
   # interfaces(5) file used by ifup(8) and ifdown(8)
   auto lo
   iface lo inet loopback
  InstallationDate: Installed on 2018-05-15 (2015 days ago)
  InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426)
  IpRoute:
   default via  dev enp0s31f6 proto dhcp src  metric 100
   /24 dev enp0s31f6 proto kernel scope link src  metric 
100
   169.254.0.0/16 dev enp0s31f6 scope link metric 1000
  NetworkManager.state:
   [main]
   NetworkingEnabled=true
   WirelessEnabled=false
   WWANEnabled=false
  ProcEnviron:
   LANG=de_DE.UTF-8
   PATH=(custom, no user)
   SHELL=/bin/bash
   TERM=xterm-256color
  SourcePackage: network-manager
  UpgradeStatus: Upgraded to mantic on 2023-11-05 (15 days ago)
  http_proxy: http://:3128
  nmcli-nm:
   RUNNING  VERSION  STATE  STARTUP  CONNECTIVITY  NETWORKING  WIFI-HW  
WIFI  WWAN-HW  WWAN
   running  1.44.2   connected  started  full  enabled enabled  
disabled  missing  disabled
  no_proxy: 127.0.0.1,172.16.0.0/12,10.0.0.0/8,192.168.0.0/16,

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/2044014/+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 2044014] Re: networkmanager crashes on configuring wireguard connection via nm-connection-editor

Hello Danilo,
yes I am aware of that; actually I can't tell from where this is set as 
actually I did not set any dns configuration. Please see attached log and 
screenshots.
Yes, a netplan file has been created. I just retracted all the sensible 
information. Quotes and double quotes were set correctly, have just been 
"overwritten" by my retraction.
If you need any further logs just give me a hint how I can create them.
Thanks a lot!

** Attachment added: "Bildschirmfoto vom 2023-11-21 19-46-03.png"
   
https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/2044014/+attachment/5721826/+files/Bildschirmfoto%20vom%202023-11-21%2019-46-03.png

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

Title:
  networkmanager crashes on configuring wireguard connection via nm-
  connection-editor

Status in network-manager package in Ubuntu:
  Triaged

Bug description:
  when configuring a new wireguard connection both via nm-connection-editor and 
the settings app, NetworkManager crashes and restarts, with the error message 
"Message recipient disconnected from message bus without replying".
  Currently, I'm unable to add wireguard connections at all.
  Also, I have netplan.io/now 0.107-5ubuntu1~ppa3 installed to outrule 
https://bugs.launchpad.net/ubuntu/+source/netplan.io/+bug/2039821

  Ubuntu 23.10
  network-manager/mantic-updates,now 1.44.2-1ubuntu1.2 amd64
  netplan.io/now 0.107-5ubuntu1~ppa3

  ProblemType: Bug
  DistroRelease: Ubuntu 23.10
  Package: network-manager 1.44.2-1ubuntu1.2
  ProcVersionSignature: Ubuntu 6.5.0-10.10-generic 6.5.3
  Uname: Linux 6.5.0-10-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  ApportVersion: 2.27.0-0ubuntu5
  Architecture: amd64
  CasperMD5CheckResult: unknown
  CurrentDesktop: ubuntu:GNOME
  Date: Mon Nov 20 20:10:40 2023
  IfupdownConfig:
   # interfaces(5) file used by ifup(8) and ifdown(8)
   auto lo
   iface lo inet loopback
  InstallationDate: Installed on 2018-05-15 (2015 days ago)
  InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426)
  IpRoute:
   default via  dev enp0s31f6 proto dhcp src  metric 100
   /24 dev enp0s31f6 proto kernel scope link src  metric 
100
   169.254.0.0/16 dev enp0s31f6 scope link metric 1000
  NetworkManager.state:
   [main]
   NetworkingEnabled=true
   WirelessEnabled=false
   WWANEnabled=false
  ProcEnviron:
   LANG=de_DE.UTF-8
   PATH=(custom, no user)
   SHELL=/bin/bash
   TERM=xterm-256color
  SourcePackage: network-manager
  UpgradeStatus: Upgraded to mantic on 2023-11-05 (15 days ago)
  http_proxy: http://:3128
  nmcli-nm:
   RUNNING  VERSION  STATE  STARTUP  CONNECTIVITY  NETWORKING  WIFI-HW  
WIFI  WWAN-HW  WWAN
   running  1.44.2   connected  started  full  enabled enabled  
disabled  missing  disabled
  no_proxy: 127.0.0.1,172.16.0.0/12,10.0.0.0/8,192.168.0.0/16,

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/2044014/+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 2044014] Re: networkmanager crashes on configuring wireguard connection via nm-connection-editor

2023-11-21 Thread Danilo Egea Gondolfo

Hi Sebastian, thanks for your bug report.

I can see the following error in your syslog.log:

 [1700508393.5530] BUG: the profile cannot be stored in keyfile
format without becoming unusable: invalid connection: ipv4.dns: This
property is not allowed for "method=disabled"

What steps did you follow to setup the connection? I want to understand
how you managed to set the ipv4.dns property with ipv4.method set to
disabled using the GUI interface.


May I ask you to watch the Network Manager's journal while you reproduce the 
crash and add the relevant part of the logs here?

journalctl -u NetworkManager.service -f


Also, you will probably find a YAML in /etc/netplan that was created for the 
problematic connection. Can you find it, remove all the keys and IPs from it, 
and paste it here?

I'm running netplan.io 0.107-5ubuntu0.1 and I can create Wireguard
connections just fine. But maybe you are using some settings that's
triggering another bug that we are not aware of.

Thank you.

** Changed in: network-manager (Ubuntu)
   Status: New => Triaged

** Changed in: network-manager (Ubuntu)
   Importance: Undecided => Medium

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

Title:
  networkmanager crashes on configuring wireguard connection via nm-
  connection-editor

Status in network-manager package in Ubuntu:
  Triaged

Bug description:
  when configuring a new wireguard connection both via nm-connection-editor and 
the settings app, NetworkManager crashes and restarts, with the error message 
"Message recipient disconnected from message bus without replying".
  Currently, I'm unable to add wireguard connections at all.
  Also, I have netplan.io/now 0.107-5ubuntu1~ppa3 installed to outrule 
https://bugs.launchpad.net/ubuntu/+source/netplan.io/+bug/2039821

  Ubuntu 23.10
  network-manager/mantic-updates,now 1.44.2-1ubuntu1.2 amd64
  netplan.io/now 0.107-5ubuntu1~ppa3

  ProblemType: Bug
  DistroRelease: Ubuntu 23.10
  Package: network-manager 1.44.2-1ubuntu1.2
  ProcVersionSignature: Ubuntu 6.5.0-10.10-generic 6.5.3
  Uname: Linux 6.5.0-10-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  ApportVersion: 2.27.0-0ubuntu5
  Architecture: amd64
  CasperMD5CheckResult: unknown
  CurrentDesktop: ubuntu:GNOME
  Date: Mon Nov 20 20:10:40 2023
  IfupdownConfig:
   # interfaces(5) file used by ifup(8) and ifdown(8)
   auto lo
   iface lo inet loopback
  InstallationDate: Installed on 2018-05-15 (2015 days ago)
  InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426)
  IpRoute:
   default via  dev enp0s31f6 proto dhcp src  metric 100
   /24 dev enp0s31f6 proto kernel scope link src  metric 
100
   169.254.0.0/16 dev enp0s31f6 scope link metric 1000
  NetworkManager.state:
   [main]
   NetworkingEnabled=true
   WirelessEnabled=false
   WWANEnabled=false
  ProcEnviron:
   LANG=de_DE.UTF-8
   PATH=(custom, no user)
   SHELL=/bin/bash
   TERM=xterm-256color
  SourcePackage: network-manager
  UpgradeStatus: Upgraded to mantic on 2023-11-05 (15 days ago)
  http_proxy: http://:3128
  nmcli-nm:
   RUNNING  VERSION  STATE  STARTUP  CONNECTIVITY  NETWORKING  WIFI-HW  
WIFI  WWAN-HW  WWAN
   running  1.44.2   connected  started  full  enabled enabled  
disabled  missing  disabled
  no_proxy: 127.0.0.1,172.16.0.0/12,10.0.0.0/8,192.168.0.0/16,

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/2044014/+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 2044159] [NEW] Ubuntu-bug triggers an error cloud-init run data not found on system. Unable to add cloud-specific data

2023-11-21 Thread lotuspsychje

Public bug reported:

Ubuntu-desktop 24.04 development branch @ 21/11/2023


When filing individual bugs from terminal using ubuntu-bug package

i'm getting an error: cloud-init run data not found on system. Unable to
add cloud-specific data

wich in some cases prevents me to file the bug

ProblemType: Bug
DistroRelease: Ubuntu 24.04
Package: apport 2.27.0-0ubuntu6
ProcVersionSignature: Ubuntu 6.5.0-10.10-generic 6.5.3
Uname: Linux 6.5.0-10-generic x86_64
ApportLog:
 
ApportVersion: 2.27.0-0ubuntu6
Architecture: amd64
CasperMD5CheckResult: unknown
CurrentDesktop: ubuntu:GNOME
Date: Tue Nov 21 18:06:19 2023
InstallationDate: Installed on 2023-11-09 (12 days ago)
InstallationMedia: Ubuntu 23.10.1 "Mantic Minotaur" - Release amd64 (20231016.1)
PackageArchitecture: all
ProcEnviron:
 LANG=nl_NL.UTF-8
 PATH=(custom, no user)
 SHELL=/bin/bash
 TERM=xterm-256color
 XDG_RUNTIME_DIR=
SourcePackage: apport
UpgradeStatus: Upgraded to noble on 2023-11-09 (12 days ago)

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


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

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

Title:
  Ubuntu-bug triggers an error cloud-init run data not found on system.
  Unable to add cloud-specific data

Status in apport package in Ubuntu:
  New

Bug description:
  Ubuntu-desktop 24.04 development branch @ 21/11/2023

  
  When filing individual bugs from terminal using ubuntu-bug package

  i'm getting an error: cloud-init run data not found on system. Unable
  to add cloud-specific data

  wich in some cases prevents me to file the bug

  ProblemType: Bug
  DistroRelease: Ubuntu 24.04
  Package: apport 2.27.0-0ubuntu6
  ProcVersionSignature: Ubuntu 6.5.0-10.10-generic 6.5.3
  Uname: Linux 6.5.0-10-generic x86_64
  ApportLog:
   
  ApportVersion: 2.27.0-0ubuntu6
  Architecture: amd64
  CasperMD5CheckResult: unknown
  CurrentDesktop: ubuntu:GNOME
  Date: Tue Nov 21 18:06:19 2023
  InstallationDate: Installed on 2023-11-09 (12 days ago)
  InstallationMedia: Ubuntu 23.10.1 "Mantic Minotaur" - Release amd64 
(20231016.1)
  PackageArchitecture: all
  ProcEnviron:
   LANG=nl_NL.UTF-8
   PATH=(custom, no user)
   SHELL=/bin/bash
   TERM=xterm-256color
   XDG_RUNTIME_DIR=
  SourcePackage: apport
  UpgradeStatus: Upgraded to noble on 2023-11-09 (12 days ago)

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


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

Re: [Touch-packages] [Bug 2043711] Re: Open3.pm tries to run code in /tmp when updating ubuntu-drivers-common

2023-11-21 Thread Steve Langasek

On Sun, Nov 19, 2023 at 08:02:42PM -, Andrew J. Caines wrote:

> the fact remains that processes running as root created a file directly in
> /tmp not using a safe *mktemp* process

There is no evidence in this bug of unsafe temp file creation in /tmp.

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

Title:
  Open3.pm tries to run code in /tmp when updating ubuntu-drivers-common

Status in perl package in Ubuntu:
  Invalid

Bug description:
  During update of ubuntu-drivers-common:

Can't exec "/tmp/ubuntu-drivers-common.config.55GJ8b": Permission denied at 
/usr/lib/x86_64-linux-gnu/perl-base/IPC/Open3.pm line 178,  line 1.
  open2: exec of /tmp/ubuntu-drivers-common.config.55GJ8b configure 
1:0.9.6.2~0.22.04.4 failed: Permission 
denied at /usr/share/perl5/Debconf/ConfModule.pm line 59.
Preconfiguring packages ...
Can't exec "/tmp/ubuntu-drivers-common.config.uSPrCH": Permission denied at 
/usr/lib/x86_64-linux-gnu/perl-base/IPC/Open3.pm line 178,  line 1.
open2: exec of /tmp/ubuntu-drivers-common.config.uSPrCH configure 
1:0.9.6.2~0.22.04.4 failed: Permission 
denied at /usr/share/perl5/Debconf/ConfModule.pm line 59.

  /tmp is mounted with noexec because running code from /tmp has been a
  vulnerability vector for several decades, hence reporting this as a
  vulnerability in perl-base.

  This error did not appear to prevent the update of ubuntu-drivers-
  common and "dpkg --verify ubuntu-drivers-common" returns 0.

___

  Attempting to use the package search on this form by clicking the 
  created a modal in which there is an error

Sorry, something went wrong with your search. We've recorded what
  happened, and we'll fix it as soon as possible. (Error ID:
  OOPS-c80f71590b02908a1187b9f743c53eac)

  which is repeated with any attempt to search for a package.

___

  Submitting this form gives an error

"perl-base" does not exist in Ubuntu. Please choose a different
  package. If you're unsure, please select "I don't know"

$ dpkg -S /usr/lib/x86_64-linux-gnu/perl-base/IPC/Open3.pm
perl-base: /usr/lib/x86_64-linux-gnu/perl-base/IPC/Open3.pm
$ dpkg -l perl-base
Desired=Unknown/Install/Remove/Purge/Hold
| 
Status=Not/Inst/Conf-files/Unpacked/halF-conf/Half-inst/trig-aWait/Trig-pend
|/ Err?=(none)/Reinst-required (Status,Err: uppercase=bad)
||/ Name   Version   Architecture Description

+++-==-=--=>
ii  perl-base  5.34.0-3ubuntu1.2 amd64minimal Perl system

  Looks like a package to me. Nevertheless, using "Did you mean..."
  offers "perl".

  ProblemType: Bug
  DistroRelease: Ubuntu 22.04
  Package: perl-base 5.34.0-3ubuntu1.2
  ProcVersionSignature: Ubuntu 6.5.0-1007.7-oem 6.5.3
  Uname: Linux 6.5.0-1007-oem x86_64
  ApportVersion: 2.20.11-0ubuntu82.5
  Architecture: amd64
  CasperMD5CheckResult: unknown
  CurrentDesktop: ubuntu:GNOME
  Date: Thu Nov 16 10:08:48 2023
  InstallationDate: Installed on 2016-04-23 (2763 days ago)
  InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 
(20160420.1)
  ProcEnviron:
   TERM=rxvt
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: perl
  UpgradeStatus: Upgraded to jammy on 2022-08-19 (453 days ago)

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

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

Re: [Touch-packages] [Bug 2043711] Re: Open3.pm tries to run code in /tmp when updating ubuntu-drivers-common

2023-11-21 Thread Steve Langasek

On Mon, Nov 20, 2023 at 08:50:05PM -, Andrew J. Caines wrote:
> You are of course quite right that the risk associated with a file
> created with a "random" six character case-insensitive alphanumeric
> suffix and run a moment later is far smaller than more obviously risky
> misuses of /tmp.

No.  The use of a random filename is not a security feature; it is a
mechanism to avoid filename *collisions* (either accidental or as part of a
denial of service).

> or if the code checks for the presence of the file before trying to create
> it (which I trust it does)

That is not how you securely handle temp files.

I'm sorry, but you have a very incomplete understanding of how secure temp
file handling works.

You have /tmp mounted noexec on your system.  This is fine, and
supported.

It is not a protection against vulnerable system code.  It is a mechanism to
protect against attackers from writing payload code to /tmp and then
executing it.

System software must handle temp files under /tmp securely *independently of
whether the files it's writing are intended to be executed*.

You have something on your system trying to write a file to /tmp and then
execute it.  That should be fixed.  But it's not a bug in perl, and it's not
a bug in apt-utils, and it's entirely unclear what code is doing this since
this in not part of the standard debconf code path.

If you can identify where this is coming from in Ubuntu, we can reassign the
bug report and get it fixed.

The rest is off-topic for an Ubuntu bug report.

-- 
Steve Langasek   Give me a lever long enough and a Free OS
Debian Developer   to set it on, and I can move the world.
Ubuntu Developer   https://www.debian.org/
slanga...@ubuntu.com vor...@debian.org

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

Title:
  Open3.pm tries to run code in /tmp when updating ubuntu-drivers-common

Status in perl package in Ubuntu:
  Invalid

Bug description:
  During update of ubuntu-drivers-common:

Can't exec "/tmp/ubuntu-drivers-common.config.55GJ8b": Permission denied at 
/usr/lib/x86_64-linux-gnu/perl-base/IPC/Open3.pm line 178,  line 1.
  open2: exec of /tmp/ubuntu-drivers-common.config.55GJ8b configure 
1:0.9.6.2~0.22.04.4 failed: Permission 
denied at /usr/share/perl5/Debconf/ConfModule.pm line 59.
Preconfiguring packages ...
Can't exec "/tmp/ubuntu-drivers-common.config.uSPrCH": Permission denied at 
/usr/lib/x86_64-linux-gnu/perl-base/IPC/Open3.pm line 178,  line 1.
open2: exec of /tmp/ubuntu-drivers-common.config.uSPrCH configure 
1:0.9.6.2~0.22.04.4 failed: Permission 
denied at /usr/share/perl5/Debconf/ConfModule.pm line 59.

  /tmp is mounted with noexec because running code from /tmp has been a
  vulnerability vector for several decades, hence reporting this as a
  vulnerability in perl-base.

  This error did not appear to prevent the update of ubuntu-drivers-
  common and "dpkg --verify ubuntu-drivers-common" returns 0.

___

  Attempting to use the package search on this form by clicking the 
  created a modal in which there is an error

Sorry, something went wrong with your search. We've recorded what
  happened, and we'll fix it as soon as possible. (Error ID:
  OOPS-c80f71590b02908a1187b9f743c53eac)

  which is repeated with any attempt to search for a package.

___

  Submitting this form gives an error

"perl-base" does not exist in Ubuntu. Please choose a different
  package. If you're unsure, please select "I don't know"

$ dpkg -S /usr/lib/x86_64-linux-gnu/perl-base/IPC/Open3.pm
perl-base: /usr/lib/x86_64-linux-gnu/perl-base/IPC/Open3.pm
$ dpkg -l perl-base
Desired=Unknown/Install/Remove/Purge/Hold
| 
Status=Not/Inst/Conf-files/Unpacked/halF-conf/Half-inst/trig-aWait/Trig-pend
|/ Err?=(none)/Reinst-required (Status,Err: uppercase=bad)
||/ Name   Version   Architecture Description

+++-==-=--=>
ii  perl-base  5.34.0-3ubuntu1.2 amd64minimal Perl system

  Looks like a package to me. Nevertheless, using "Did you mean..."
  offers "perl".

  ProblemType: Bug
  DistroRelease: Ubuntu 22.04
  Package: perl-base 5.34.0-3ubuntu1.2
  ProcVersionSignature: Ubuntu 6.5.0-1007.7-oem 6.5.3
  Uname: Linux 6.5.0-1007-oem x86_64
  ApportVersion: 2.20.11-0ubuntu82.5
  Architecture: amd64
  CasperMD5CheckResult: unknown
  CurrentDesktop: ubuntu:GNOME
  Date: Thu Nov 16 10:08:48 2023
  InstallationDate: Installed on 2016-04-23 (2763 days ago)
  InstallationMedia: Ubuntu

[Touch-packages] [Bug 2044130] Re: "Ubuntu Software" keeps telling me "an important update has been made" for the same "UEFI dbx" at every boot.

2023-11-21 Thread Paul White

*** This bug is a duplicate of bug 2024392 ***
https://bugs.launchpad.net/bugs/2024392

** This bug has been marked a duplicate of bug 2024392
   Gnome-software displays notification about OS upgrade on each boot

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

Title:
  "Ubuntu Software" keeps telling me "an important update has been made"
  for the same "UEFI dbx" at every boot.

Status in apport package in Ubuntu:
  New

Bug description:
  At every boot (maybe also every new login, haven't tried that),
  "Ubuntu Software" pops up and tells me it updated an important
  component, and when clicking to review for more information, it's
  always "UEFI dbx".

  I dont think that this thing is always updated (I also didn run and
  updates with apt or the GUI), it looks like a bug in "Ubuntu
  software".

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/apport/+bug/2044130/+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 2029352] Re: systemd/ 245.4-4ubuntu3.22 ADT test failure with linux/5.4.0-156.173

** Description changed:

+ [Impact]
+
+ The armhf autopkgtest fails for focal and ultimately leads to less test
+ coverage because other packages now won't block on these failures, and
+ may not notice new regressions.
+
+ [Test Plan]
+
+ The test-execute test within root-unittests should pass.
+
+ [Where problems could occur]
+
+ The patch only changes a service file in the test tree of systemd, so
+ this is not a change that will be seen on real Ubuntu systems. Hence any
+ further problems would be seen only in the test-execute test.
+
+ [Original Description]
+
This is a scripted bug report about ADT failures while running systemd tests
for linux/5.4.0-156.173 on focal. Whether this is caused by the dep8 tests of
the tested source or the kernel has yet to be determined.
root-unittests fails.

Testing failed on:
- armhf:
https://autopkgtest.ubuntu.com/results/autopkgtest-focal/focal/armhf/s/systemd/20230727_150132_9cd77@/log.gz
+ armhf:
https://autopkgtest.ubuntu.com/results/autopkgtest-focal/focal/armhf/s/systemd/20230727_150132_9cd77@/log.gz

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

Title:
systemd/ 245.4-4ubuntu3.22 ADT test failure with linux/5.4.0-156.173

Status in systemd package in Ubuntu:
Invalid
Status in systemd source package in Focal:
Triaged

Bug description:
[Impact]

The armhf autopkgtest fails for focal and ultimately leads to less
test coverage because other packages now won't block on these
failures, and may not notice new regressions.

[Test Plan]

The test-execute test within root-unittests should pass.

[Where problems could occur]

The patch only changes a service file in the test tree of systemd, so
this is not a change that will be seen on real Ubuntu systems. Hence
any further problems would be seen only in the test-execute test.

[Original Description]

This is a scripted bug report about ADT failures while running systemd tests
for linux/5.4.0-156.173 on focal. Whether this is caused by the dep8 tests of
the tested source or the kernel has yet to be determined.
root-unittests fails.

Testing failed on:
armhf:
https://autopkgtest.ubuntu.com/results/autopkgtest-focal/focal/armhf/s/systemd/20230727_150132_9cd77@/log.gz

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/2029352/+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 2029352] Re: systemd/ 245.4-4ubuntu3.22 ADT test failure with linux/5.4.0-156.173

This is fixed by upstream commit [1], which is included in v251 and
newer. The reason this is not needed in Jammy (v249) is because we
already have a patch [2] that causes this test case to be skipped on
arhmf.

[1] 
https://github.com/systemd/systemd/commit/646cba5c4208c28c56dbe52d676ab1a176c69b7f
[2] 
https://git.launchpad.net/~ubuntu-core-dev/ubuntu/+source/systemd/tree/debian/patches/debian/UBUNTU-src-test-test-execute.c-Skip-parts-of-test-execute-in-con.patch?h=ubuntu-jammy

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

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

Title:
  systemd/ 245.4-4ubuntu3.22  ADT test failure with linux/5.4.0-156.173

Status in systemd package in Ubuntu:
  Invalid
Status in systemd source package in Focal:
  Triaged

Bug description:
  [Impact]

  The armhf autopkgtest fails for focal and ultimately leads to less
  test coverage because other packages now won't block on these
  failures, and may not notice new regressions.

  [Test Plan]

  The test-execute test within root-unittests should pass.

  [Where problems could occur]

  The patch only changes a service file in the test tree of systemd, so
  this is not a change that will be seen on real Ubuntu systems. Hence
  any further problems would be seen only in the test-execute test.

  [Original Description]

  This is a scripted bug report about ADT failures while running systemd tests 
for linux/5.4.0-156.173 on focal. Whether this is caused by the dep8 tests of 
the tested source or the kernel has yet to be determined.
  root-unittests fails.

  Testing failed on:
  armhf: 
https://autopkgtest.ubuntu.com/results/autopkgtest-focal/focal/armhf/s/systemd/20230727_150132_9cd77@/log.gz

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/2029352/+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 2044034] Re: /etc/security/limits.conf memlock changes have no effect

2023-11-21 Thread David Favor

This also fails... meaning... ulimit -l as root still shows 64...

*-   memlock unlimited
root -   memlock unlimited

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

Title:
  /etc/security/limits.conf memlock changes have no effect

Status in pam package in Ubuntu:
  New

Bug description:
  APT reports package as libpam-modules + launchpad says pam is the
  closest package. Please change package name, if required.

  Summary says it all.

  Default of memlock seems to be 64 (which limits.conf suggests means
  64k). Changing this setting seems to have no effect.

  The following entry seems to be correct, and has no effect after
  reboot, meaning ulimit -l still reports 64. I've tried 128, -1,
  unlimited, nothing seems to work.

  Maybe I just misunderstand the correct settings or maybe Ubuntu
  overrides limits.conf at boot time.

  My entry...

  *-   memlock unlimited

  Be great if someone can help me fixing this, as likely it's a simple
  config file fix somewhere.

  Thanks!

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/pam/+bug/2044034/+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 2044139] [NEW] Kernel image 6.5 (web-)midi problems

Public bug reported:

After the update to mantis, I have a problem with (at least - i have not
yet researched further issues) Web-Midi applications running in the
browser.

Up to Kernel 6.2 it works just fine (also when downgrading the kernel to
6.2 in mantis)to use https://app.electra.one/
http://components.novationmusic.com/ with a web midi enabled browser
(must be google chrome installed by deb or chromium installed from their
nightly builds or via nixos - because the snap version doesn't properly
allow web midi for some reason that I still need to investigate
further).

When using any 6.5 or later kernel as included in mantis, or also when
building my own from kernel.org, the devices I want to be managed with
are basically identified, but no further actions are possible.

This is 100% reproducible, switching back and forth between 6.5+ and 6.2 
kernels is very clearly showing the old version always works easily, but the 
newer version doesn't.
Also a 6.6.1 mainlne kernel from kernel.org still has the issue.

I have fiddled with this quite some hours, I suspected it has something to to 
with the midi 2.0 change in kernel 6.5 and tried turning it off with module 
parameters, but also when disabled or compiled a kernel without midi 2.0 
support the problem, persists. 
The same with the latest 6.6.1 kernel.

I have not found any error output in dmesg or journalctl that seems to
be related to the problem so far, and also no other way to try to
trigger the problem but the above described web midi thing.

All tests have been done with the ubuntu kernel config - and the
mainline configs created with make oldconfig.

So I might additionally test the default mainline configuration, and
also later mainline versions like 6.6.2 and try to identify other
erratic behaviours in midi usage (of controllers etc) and add
information about it... also I did not yet try the normal "generic"
kernels, just

Also I found this thing right now:

https://forum.cockos.com/showthread.php?t=283086

at the end it says there has been a bug in the kernel in the midi code.

But I'm not sure if that is the same issue. For one I have not seen similar 
error messages in my system, but mainly this post says the bug is fixed in 
6.5.6  https://lwn.net/Articles/946853/ - and I have tested 6.5.11 mainline 
form kernel.org with the problem still persisting. 
It might be there is some more wrong with the 6.5+ kernels in the midi area.


if there are any further tests or logs needed or helpful, please let me know.

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

** Package changed: apport (Ubuntu) => linux-signed-lowlatency (Ubuntu)

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

Title:
  Kernel image 6.5 (web-)midi problems

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

Bug description:
  After the update to mantis, I have a problem with (at least - i have
  not yet researched further issues) Web-Midi applications running in
  the browser.

  Up to Kernel 6.2 it works just fine (also when downgrading the kernel
  to 6.2 in mantis)to use https://app.electra.one/
  http://components.novationmusic.com/ with a web midi enabled browser
  (must be google chrome installed by deb or chromium installed from
  their nightly builds or via nixos - because the snap version doesn't
  properly allow web midi for some reason that I still need to
  investigate further).

  When using any 6.5 or later kernel as included in mantis, or also when
  building my own from kernel.org, the devices I want to be managed with
  are basically identified, but no further actions are possible.

  This is 100% reproducible, switching back and forth between 6.5+ and 6.2 
kernels is very clearly showing the old version always works easily, but the 
newer version doesn't.
  Also a 6.6.1 mainlne kernel from kernel.org still has the issue.

  I have fiddled with this quite some hours, I suspected it has something to to 
with the midi 2.0 change in kernel 6.5 and tried turning it off with module 
parameters, but also when disabled or compiled a kernel without midi 2.0 
support the problem, persists. 
  The same with the latest 6.6.1 kernel.

  I have not found any error output in dmesg or journalctl that seems to
  be related to the problem so far, and also no other way to try to
  trigger the problem but the above described web midi thing.

  All tests have been done with the ubuntu kernel config - and the
  mainline configs created with make oldconfig.

  So I might additionally test the default mainline configuration, and
  also later mainline versions like 6.6.2 and try to identify other
  erratic behaviours in midi usage (of controllers etc) and add
  information about it... also I did not yet try the normal "generic"
  kernels, just

  Also I found this thing right now:

[Touch-packages] [Bug 2044130] Re: "Ubuntu Software" keeps telling me "an important update has been made" for the same "UEFI dbx" at every boot.

Also, i tried to report this via ubuntu-bug / apport-bug - but this was
impossible, because for me as a user it is impossible to find out, which
package name or PID I must give apport for the app that identifies as
"Ubuntu Software" in the Dock, because there is nothing called "ubuntu-
software" or similar in the output of "ps", there is no package "ubuntu-
software" or similar in the installed packages, and the app itself also
has no further menus like an "help" and "about" section that most apps
usually have, where program and or package name could be found.

it's really a challenge for users trying to report bugs in an
application that doesn't give information about how to identify it for
apport. I just spend about an hour with that issue while what I was
trying to report was just the simple information above.

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

Title:
  "Ubuntu Software" keeps telling me "an important update has been made"
  for the same "UEFI dbx" at every boot.

Status in apport package in Ubuntu:
  New

Bug description:
  At every boot (maybe also every new login, haven't tried that),
  "Ubuntu Software" pops up and tells me it updated an important
  component, and when clicking to review for more information, it's
  always "UEFI dbx".

  I dont think that this thing is always updated (I also didn run and
  updates with apt or the GUI), it looks like a bug in "Ubuntu
  software".

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/apport/+bug/2044130/+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 2044130] [NEW] "Ubuntu Software" keeps telling me "an important update has been made" for the same "UEFI dbx" at every boot.

Public bug reported:

At every boot (maybe also every new login, haven't tried that), "Ubuntu
Software" pops up and tells me it updated an important component, and
when clicking to review for more information, it's always "UEFI dbx".

I dont think that this thing is always updated (I also didn run and
updates with apt or the GUI), it looks like a bug in "Ubuntu software".

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

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

Title:
  "Ubuntu Software" keeps telling me "an important update has been made"
  for the same "UEFI dbx" at every boot.

Status in apport package in Ubuntu:
  New

Bug description:
  At every boot (maybe also every new login, haven't tried that),
  "Ubuntu Software" pops up and tells me it updated an important
  component, and when clicking to review for more information, it's
  always "UEFI dbx".

  I dont think that this thing is always updated (I also didn run and
  updates with apt or the GUI), it looks like a bug in "Ubuntu
  software".

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


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

[Touch-packages] [Bug 2044129] [NEW] ubuntu-bug does not allow for reporting a bug in "other software" manually giving a symptom description

Public bug reported:

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

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

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

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

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


** Tags: amd64 apport-bug mantic

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

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

Status in apport package in Ubuntu:
  New

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

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

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

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

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


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

[Touch-packages] [Bug 1995790] Re: regression: ?garbage does not work correctly in install commands

2023-11-21 Thread Julian Andres Klode

Actually I have one followup fix for the test suite to commit to fix up
some asserted debug output :D

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

Title:
  regression: ?garbage does not work correctly in install commands

Status in apt package in Ubuntu:
  Fix Committed
Status in apt source package in Jammy:
  Triaged
Status in apt source package in Lunar:
  Won't Fix
Status in apt source package in Mantic:
  Triaged

Bug description:
  The awesome apt has a some wonderful tips on their EXAMPLES section
  (printed below). The choice of name to "garbage" might not have been
  the best but the function is extremely useful.

  $ man apt-patterns | sed '/EXAMPLES/,/^[^ ]/!d;/^[^ ]/d'
 apt remove ?garbage
 Remove all packages that are automatically installed and no longer 
needed -
 same as apt autoremove

 apt purge ?config-files
 Purge all packages that only have configuration files left

 apt list '~i !~M (~slibs|~sperl|~spython)'
 List all manually-installed packages in sections matching libs, 
perl, or
 python.

  Lets mark a package as automatically installed, and use the examples.

  $ sudo apt-mark auto shotwell
  shotwell set to automatically installed.

  $ sudo apt remove ?garbage
  Reading package lists... Done
  Building dependency tree... Done
  Reading state information... Done
  The following packages were automatically installed and are no longer 
required:
libraw20 shotwell shotwell-common
  Use 'sudo apt autoremove' to remove them.
  0 upgraded, 0 newly installed, 0 to remove and 0 not upgraded.

  $ sudo apt autoremove 
  Reading package lists... Done
  Building dependency tree... Done
  Reading state information... Done
  The following packages will be REMOVED:
libraw20 shotwell shotwell-common
  0 upgraded, 0 newly installed, 3 to remove and 0 not upgraded.
  After this operation, 9.806 kB disk space will be freed.
  Do you want to continue? [Y/n] N
  Abort.

  Apt-patterns works as it should everywhere else, as far as I can see,
  it works wonders with ie `apt list '~g|~c'` and many other
  applications. I used `apt purge '~g|~c'` successfully in Ubuntu 20.04
  for years, so I feel this is a regression.

  ProblemType: Bug
  DistroRelease: Ubuntu 22.04
  Package: apt 2.4.8
  ProcVersionSignature: Ubuntu 5.15.0-52.58-generic 5.15.60
  Uname: Linux 5.15.0-52-generic x86_64
  NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
  ApportVersion: 2.20.11-0ubuntu82.1
  Architecture: amd64
  CasperMD5CheckResult: unknown
  CurrentDesktop: ubuntu:GNOME
  Date: Sun Nov  6 10:57:52 2022
  SourcePackage: apt
  UpgradeStatus: Upgraded to jammy on 2022-03-26 (224 days ago)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/apt/+bug/1995790/+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 2044104] Re: [UBUNTU 20.04] chzdev -e is rebuilding initramfs even with zdev:early=0 set

2023-11-21 Thread Frank Heimes

This was implemented around 2020, mainly to catch any ccw config changes in a 
user friendly way:
https://bugs.launchpad.net/bugs/1892367
https://i527439087.restricted.launchpadlibrarian.net/527439087/20f6c87a-829f-11eb-9412-002481e91f22.txt?token=zC4n7TlCmffBDHm9Dl002PsfchDXC3Dk

Regarding:
"1) Have the generic udev initramfs script not copy zdev-generated Udev rules,"
we need to be super careful here to not break stuff ...

How to best identify the zdev-generated Udev rules,
since these are not all the rules generated by chzdev (indicated by first line 
in rule), are they?

I'm not very sure if initramfs(-tools) maintainer(s) are very happy ...

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

Title:
  [UBUNTU 20.04] chzdev -e is rebuilding initramfs even with
  zdev:early=0 set

Status in Ubuntu on IBM z Systems:
  New
Status in initramfs-tools package in Ubuntu:
  New
Status in s390-tools package in Ubuntu:
  New

Bug description:
  Versions:
  Ubuntu 20.04.5 s390-tools version 2.12.0-0ubuntu3.7.s390x
  Ubuntu 22.04.2 s390-tools version 2.20.0-0ubuntu3.2.s390x

  When I configure a zfcp LUN persistently via chzdev, the initrd is
  being rebuilt even with parameter zdev:early=0

  root@a8315003:~# chzdev -e zfcp-lun 
0.0.1803:0x500507630910d430:0x40194092 zdev:early=0
  zFCP LUN 0.0.1803:0x500507630910d430:0x40194092 configured
  Note: The initial RAM-disk must be updated for these changes to take effect:
 - zFCP LUN 0.0.1803:0x500507630910d430:0x40194092
  update-initramfs: Generating /boot/initrd.img-5.15.0-60-generic
  I: The initramfs will attempt to resume from /dev/dasdb1
  I: (UUID=e70ecb80-4d1e-4074-9cda-ce231ad6e698)
  I: Set the RESUME variable to override this.
  Using config file '/etc/zipl.conf'
  Building bootmap in '/boot'
  Adding IPL section 'ubuntu' (default)
  Preparing boot device: dasda (c00a).
  Done.
  root@a8315003:~#

  == Comment: - Thorsten Diehl  - 2023-03-01 
06:55:47 ==
  @BOE-dev
  This behaviour is unexpected.
  https://www.ibm.com/docs/en/linux-on-systems?topic=commands-chzdev says:
  Activating a device early during the boot process

  Use the zdev:early device attribute to activate a device early during
  the boot process and to override any existing auto-configuration with
  a persistent device configuration.

  zdev:early=1
  The device is activated during the initial RAM disc phase according to 
the persistent configuration.

  zdev:early=0
  The device is activated as usual during the boot process. This is the 
default. If auto-configuration data is present, the device is activated during 
the initial RAM disc phase according to the auto-configuration. 

  I can't interprete a SCSI LUN as a device with auto configuration
  data. (At least, if the zfcp device hasn't NPIV enabled)

  == Comment: #5 - Peter Oberparleiter  - 
2023-03-01 11:18:28 ==
  (In reply to comment #2)
  > @BOE-dev
  > This behaviour is unexpected.
  > https://www.ibm.com/docs/en/linux-on-systems?topic=commands-chzdev says:
  > Activating a device early during the boot process
  > 
  > Use the zdev:early device attribute to activate a device early during the
  > boot process and to override any existing auto-configuration with a
  > persistent device configuration.
  > 
  > zdev:early=1
  > The device is activated during the initial RAM disc phase according to
  > the persistent configuration.
  > 
  > zdev:early=0
  > The device is activated as usual during the boot process. This is the
  > default. If auto-configuration data is present, the device is activated
  > during the initial RAM disc phase according to the auto-configuration. 

  The documentation is incorrect for Ubuntu. Canonical specifically
  builds zdev in a way that every change to persistent device
  configuration causes an update to the initial RAM-disk. See also:

  https://bugzilla.linux.ibm.com/show_bug.cgi?id=187578#c35
  
https://github.com/ibm-s390-linux/s390-tools/commit/7dd03eaeecdd0e2674f145aca34be1275d291bd8

  > I can't interprete a SCSI LUN as a device with auto configuration data. (At
  > least, if the zfcp device hasn't NPIV enabled)

  This is related to auto-configuration as implemented for DPM.

  == Comment: #6 - Thorsten Diehl  - 2023-03-03 
12:41:44 ==
  So, IIUC, chzdev is built for Ubuntu with ZDEV_ALWAYS_UPDATE_INITRD=1, which 
make the parameter zdev:early=0 ineffective. Correct?
  If you confirm, you may also close this bug.

  Not nice - then we have to find an alternate solution.

  == Comment: #7 - Peter Oberparleiter  - 
2023-03-07 06:48:07 ==
  (In reply to comment #6)
  > So, IIUC, chzdev is built for Ubuntu with ZDEV_ALWAYS_UPDATE_INITRD=1, which
  > make the parameter zdev:early=0 ineffective. Correct?
  > If you confirm, you may also close this bug.
  > 
  > Not nice - then we have to find an alternate

[Touch-packages] [Bug 2044124] Re: ubuntu-bug shows extra information window that does not fit on screen so action buttons not available

screenshot of the situation

** Attachment added: "IMG_6587.JPG"
   
https://bugs.launchpad.net/ubuntu/+source/apport/+bug/2044124/+attachment/5721679/+files/IMG_6587.JPG

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

Title:
  ubuntu-bug shows extra information window that does not fit on screen
  so action buttons not available

Status in apport package in Ubuntu:
  New

Bug description:
  When trying to report a bug on "Ubuntu Software" I try to use the "-w"
  option to select the window of the application

  (because I dont know the program or the package name of the
  application running with the icon in the dock saying it's "Ubuntu
  Software", and it seems impossible to find out the pid "Ubuntu
  Software" is running on, as there is nothing resembling "ubuntu
  software" in the ps process list)

  but after selecting it shows me some additional info dialog window,
  that seems to have so much text content, that any further action
  buttons that might be at the end of the text are not visible and
  reachable.

  it looks like the apport dialog window goes over the size of my screen
  and I see not possibility how to move it to reach its bottom. This
  used to work by pressing "alt" and moving the window with the mouse
  but that doesn't do the job.

  So it's impossible for me to file a bug.

  
  A better behaviour would be if the window are with the lots amount of text 
content would be scrollable and the window made to just fit the current screen 
resolution so the buttons are reachable.

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

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/apport/+bug/2044124/+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 2044127] [NEW] ubuntu-but does not accept "program" paramater as documented in --help

Public bug reported:

ubuntu-bug --help says

$ ubuntu-bug --help
usage: ubuntu-bug [options] [symptom|pid|package|program path|.apport/.crash 
file]


which suggest I can type a symptom after "ubuntu-bug" that I want to report.

But doing something like:

$ ubuntu-bug "Ubuntu Software tells me at every boot that it installed
important OS update 'UEFI dbx'"


only results in the error:

dpkg-query: no packages found matching Ubuntu


The man page of ubuntu-bug states that the symptoms are asked for when I run 
"ubuntu-bug" without parameters. 

So the --help output is wrong or the program is lacking some fallback if
the message given as sysmptom is neither a pid, nor a package name nor a
program path nor a crash file, the given parameter must be accepted as a
symptom description.

Probably the easiest part to solve that is to remove the nonworking
symptom parameter from the --help output as long as that is not working.

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

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


** Tags: amd64 apport-bug mantic

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

Title:
  ubuntu-but does not accept "program" paramater as documented in --help

Status in apport package in Ubuntu:
  New

Bug description:
  ubuntu-bug --help says

  $ ubuntu-bug --help
  usage: ubuntu-bug [options] [symptom|pid|package|program path|.apport/.crash 
file]

  
  which suggest I can type a symptom after "ubuntu-bug" that I want to report.

  But doing something like:

  $ ubuntu-bug "Ubuntu Software tells me at every boot that it installed
  important OS update 'UEFI dbx'"

  
  only results in the error:

  dpkg-query: no packages found matching Ubuntu

  
  The man page of ubuntu-bug states that the symptoms are asked for when I run 
"ubuntu-bug" without parameters. 

  So the --help output is wrong or the program is lacking some fallback
  if the message given as sysmptom is neither a pid, nor a package name
  nor a program path nor a crash file, the given parameter must be
  accepted as a symptom description.

  Probably the easiest part to solve that is to remove the nonworking
  symptom parameter from the --help output as long as that is not
  working.

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

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/apport/+bug/2044127/+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 2044104] Re: [UBUNTU 20.04] chzdev -e is rebuilding initramfs even with zdev:early=0 set

2023-11-21 Thread Frank Heimes

** Package changed: linux (Ubuntu) => s390-tools (Ubuntu)

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

** Also affects: ubuntu-z-systems
   Importance: Undecided
   Status: New

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

Title:
  [UBUNTU 20.04] chzdev -e is rebuilding initramfs even with
  zdev:early=0 set

Status in Ubuntu on IBM z Systems:
  New
Status in initramfs-tools package in Ubuntu:
  New
Status in s390-tools package in Ubuntu:
  New

Bug description:
  Versions:
  Ubuntu 20.04.5 s390-tools version 2.12.0-0ubuntu3.7.s390x
  Ubuntu 22.04.2 s390-tools version 2.20.0-0ubuntu3.2.s390x

  When I configure a zfcp LUN persistently via chzdev, the initrd is
  being rebuilt even with parameter zdev:early=0

  root@a8315003:~# chzdev -e zfcp-lun 
0.0.1803:0x500507630910d430:0x40194092 zdev:early=0
  zFCP LUN 0.0.1803:0x500507630910d430:0x40194092 configured
  Note: The initial RAM-disk must be updated for these changes to take effect:
 - zFCP LUN 0.0.1803:0x500507630910d430:0x40194092
  update-initramfs: Generating /boot/initrd.img-5.15.0-60-generic
  I: The initramfs will attempt to resume from /dev/dasdb1
  I: (UUID=e70ecb80-4d1e-4074-9cda-ce231ad6e698)
  I: Set the RESUME variable to override this.
  Using config file '/etc/zipl.conf'
  Building bootmap in '/boot'
  Adding IPL section 'ubuntu' (default)
  Preparing boot device: dasda (c00a).
  Done.
  root@a8315003:~#

  == Comment: - Thorsten Diehl  - 2023-03-01 
06:55:47 ==
  @BOE-dev
  This behaviour is unexpected.
  https://www.ibm.com/docs/en/linux-on-systems?topic=commands-chzdev says:
  Activating a device early during the boot process

  Use the zdev:early device attribute to activate a device early during
  the boot process and to override any existing auto-configuration with
  a persistent device configuration.

  zdev:early=1
  The device is activated during the initial RAM disc phase according to 
the persistent configuration.

  zdev:early=0
  The device is activated as usual during the boot process. This is the 
default. If auto-configuration data is present, the device is activated during 
the initial RAM disc phase according to the auto-configuration. 

  I can't interprete a SCSI LUN as a device with auto configuration
  data. (At least, if the zfcp device hasn't NPIV enabled)

  == Comment: #5 - Peter Oberparleiter  - 
2023-03-01 11:18:28 ==
  (In reply to comment #2)
  > @BOE-dev
  > This behaviour is unexpected.
  > https://www.ibm.com/docs/en/linux-on-systems?topic=commands-chzdev says:
  > Activating a device early during the boot process
  > 
  > Use the zdev:early device attribute to activate a device early during the
  > boot process and to override any existing auto-configuration with a
  > persistent device configuration.
  > 
  > zdev:early=1
  > The device is activated during the initial RAM disc phase according to
  > the persistent configuration.
  > 
  > zdev:early=0
  > The device is activated as usual during the boot process. This is the
  > default. If auto-configuration data is present, the device is activated
  > during the initial RAM disc phase according to the auto-configuration. 

  The documentation is incorrect for Ubuntu. Canonical specifically
  builds zdev in a way that every change to persistent device
  configuration causes an update to the initial RAM-disk. See also:

  https://bugzilla.linux.ibm.com/show_bug.cgi?id=187578#c35
  
https://github.com/ibm-s390-linux/s390-tools/commit/7dd03eaeecdd0e2674f145aca34be1275d291bd8

  > I can't interprete a SCSI LUN as a device with auto configuration data. (At
  > least, if the zfcp device hasn't NPIV enabled)

  This is related to auto-configuration as implemented for DPM.

  == Comment: #6 - Thorsten Diehl  - 2023-03-03 
12:41:44 ==
  So, IIUC, chzdev is built for Ubuntu with ZDEV_ALWAYS_UPDATE_INITRD=1, which 
make the parameter zdev:early=0 ineffective. Correct?
  If you confirm, you may also close this bug.

  Not nice - then we have to find an alternate solution.

  == Comment: #7 - Peter Oberparleiter  - 
2023-03-07 06:48:07 ==
  (In reply to comment #6)
  > So, IIUC, chzdev is built for Ubuntu with ZDEV_ALWAYS_UPDATE_INITRD=1, which
  > make the parameter zdev:early=0 ineffective. Correct?
  > If you confirm, you may also close this bug.
  > 
  > Not nice - then we have to find an alternate solution.

  chzdev -p on Ubuntu will by default rebuild the initrd. This is intended
  behavior by Canonical and controlled by the ZDEV_ALWAYS_UPDATE_INITRD 
build-time
  switch. You can suppress it by adding option --no-root-update to the command
  line.

  Specifying zdev:early=0 to chzdev has exactly the effect that it is supposed 
to
  have: it tells zdev not to enable that device during initrd processing,
  resulting in the

[Touch-packages] [Bug 2044124] [NEW] ubuntu-bug shows extra information window that does not fit on screen so action buttons not available