[Touch-packages] [Bug 2004551] Re: upgrade to lunar fails due to rescue-ssh.target or port 22 takeover

[Christian Ehrhardt ]

Thank you Steve, documenting what kind of debug data you'd expect helps
me or anyone else who might run into this next time.

Once I'm done with my current tasks on this system I'll try to redeploy
and re-upgrade to check if it happens again.

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

Title:
  upgrade to lunar fails due to rescue-ssh.target or port 22 takeover

Status in openssh package in Ubuntu:
  Incomplete

Bug description:
  Hi,
  I just upgraded a system from Jammy to Lunar and openssh-server refuses to 
upgrade well.

  Setting up openssh-server (1:9.0p1-1ubuntu8) ...
  Replacing config file /etc/ssh/sshd_config with new version
  Replacing config file /etc/ssh/sshd_config with new version
  Synchronizing state of ssh.service with SysV service script with 
/lib/systemd/systemd-sysv-install.
  Executing: /lib/systemd/systemd-sysv-install disable ssh
  rescue-ssh.target is a disabled or a static unit not running, not starting it.
  Could not execute systemctl:  at /usr/bin/deb-systemd-invoke line 145.
  dpkg: error processing package openssh-server (--configure):
   installed openssh-server package post-installation script subprocess 
returned error exit status 1
  Processing triggers for man-db (2.11.2-1) ...
  Processing triggers for libc-bin (2.36-0ubuntu4) ...
  Errors were encountered while processing:
   openssh-server
  Error: Timeout was reached
  needrestart is being skipped since dpkg has failed
  E: Sub-process /usr/bin/dpkg returned an error code (1)

  I'm not sure what exactly it is.
  This output complains about rescue-ssh.target and indeed that can not be 
started even directly.

  $ sudo systemctl start rescue-ssh.target
  A dependency job for rescue-ssh.target failed. See 'journalctl -xe' for 
details.

  And in postinst is a try to start it:
  $  grep rescue /var/lib/dpkg/info/openssh-server.postinst 
deb-systemd-invoke $_dh_action 'rescue-ssh.target' >/dev/null 
|| true

  
  But I think the underlying issue is that ssh is already on, and I'm logged in 
via it.
  And that makes the service restart of the ssh socket which was added break.

  Feb 02 10:40:56 node-horsea systemd[104560]: ssh.socket: Failed to create 
listening socket ([::]:22): Address already in use
  Feb 02 10:40:56 node-horsea systemd[1]: ssh.socket: Failed to receive 
listening socket ([::]:22): Input/output error
  Feb 02 10:40:56 node-horsea systemd[1]: ssh.socket: Failed to listen on 
sockets: Input/output error
  Feb 02 10:40:56 node-horsea systemd[1]: ssh.socket: Failed with result 
'resources'.

  
  Now, whichever it is, it is hard to resolve.
  The only way to get the socket to own it would be rebooting so that sshd lets 
go and systemd can take over.
  I could reboot, but that is not the point.
  What if I'd want to get the service and upgrade completed before reboot.
  Because as of now dpkg considers the system unhappy, and that would usually 
be a sign for "better not reboot before being resolved" to me.

  One thing though, I have not upgraded with do-release-upgrade - would
  we / do we have magic there to make the ssh socket activation
  transition smoother?

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/openssh/+bug/2004551/+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 2003756] Re: Cannot configure krb5-kdc on Ubuntu Jammy 22.04.01, "Could not execute systemctl: at /usr/bin/deb-systemd-invoke line 142."

[Surfrock66]

There is a bunch of interesting order-of-events issues I'm discovering
with what I'm doing, and because of that it is creating errors that are
obscured in the packaging process.  I don't know if there's a fix, or
just some alerts, etc.  The package failure appears to be because I did
NOT set up a realm; intending to use ldap as the backend, I figured I
would NOT have krb5-kdc config create an initial realm.  This means when
it tries to start the service, I get this in the logs:

Cannot open DB2 database '/var/lib/krb5kdc/principal': No such file or
directory - while initializing database for realm SUBDOMAIN.DOMAIN.COM

The realm is defined by the install of krb5-config, so it knows the
realm it wants to use.  So, fine, maybe that's expected; then I go in
and run krb5_ldap_util to create the realm, and THAT led to another
error...the tool doesn't support TLS.  I get "Confidentiality required
while initializing database" which indicates a TLS error.  Disabled
forcing of tls on the ldap server and I could initialize the realm,
stash everything needed in keyfiles, and I was off to the races.

I don't know if there is a packaging fix (other than the advice from the
maintainers above about handling the systemd calls knowing they will
fail) but it's been interesting to troubleshoot.

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

Title:
  Cannot configure krb5-kdc on Ubuntu Jammy 22.04.01, "Could not execute
  systemctl:  at /usr/bin/deb-systemd-invoke line 142."

Status in init-system-helpers package in Ubuntu:
  New
Status in krb5 package in Ubuntu:
  New

Bug description:
  I have a fresh install of Ubuntu Server 22.04.01 LTS.  After
  installing the server and running all updates, I run the following
  command:

  apt -y install slapd ldap-utils schema2ldif sasl2-bin
  libsasl2-modules-gssapi-mit krb5-kdc-ldap krb5-admin-server krb5-kdc

  This will be installing krb5-kdc 1.19.2-2.

  This is in preparation for setting up an OpenLDAP server, a Kerberos
  server with an LDAP backend, and saslauthd for pass-through
  authentication.  krb5-kdc was auto-selected when running the steps in
  the guide here in my development environment:
  https://ubuntu.com/server/docs/service-kerberos-with-openldap-backend
  When installing that, I get the following in the output:

  Setting up krb5-kdc (1.19.2-2) ...
  Created symlink /etc/systemd/system/multi-user.target.wants/krb5-kdc.service 
→ /lib/systemd/system/krb5-kdc.service.
  Could not execute systemctl:  at /usr/bin/deb-systemd-invoke line 142.

  I do get the prompts for the realm, kdc, and admin server hostnames,
  and they are reflected in /etc/krb5.conf.  If I then run the
  following:

  dpkg-reconfigure krb5-kdc

  I am prompted for whether I want the package to create the Kerberos
  KDC configuration automatically, and when I say yes, it then repeats
  the following error:

  Could not execute systemctl:  at /usr/bin/deb-systemd-invoke line 142.

  I cannot find any further debug in the syslog or anything to indicate
  what the root cause is; the list of packages here are all installed
  together on a separate development server where I experimented with
  the configuration I will be deploying here in production so I don't
  think it's incompatible packages in the install list, but I am open to
  feedback on that.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/init-system-helpers/+bug/2003756/+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 2004533] Re: Gtk-WARNING **: ...: drawing failure for widget '...': invalid value (typically too big)

[Daniel van Vugt]

** Summary changed:

- very unstable desktop, icons vanish, cannot control windows, cannot resize or 
scale multi monitors easily.
+ Gtk-WARNING **: ...: drawing failure for widget '...': invalid value 
(typically too big)

** Summary changed:

- Gtk-WARNING **: ...: drawing failure for widget '...': invalid value 
(typically too big)
+ Gtk-WARNING ... drawing failure for widget ... invalid value (typically too 
big)

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

Title:
  Gtk-WARNING ... drawing failure for widget ... invalid value
  (typically too big)

Status in gtk+3.0 package in Ubuntu:
  Incomplete

Bug description:
  A tiny sample of of my logs starting with the subject of this thread:
  gnome-shell[15376]: Can't update stage views actor [:0x564e0cfc0900] is on 
because it needs an allocation.
  others
  gnome-shell[15376]: DING: (gjs:23748): Gtk-WARNING **: 19:23:18.003: drawing 
failure for widget 'GtkImage': invalid value (typically too big) for the size 
of the input (surface, pattern, etc.)
  gnome-shell[15376]: DING: (gjs:23748): Gtk-WARNING **: 19:23:17.986: infinite 
surface size not supported
  gnome-shell[15376]: DING: (gjs:23748): Gtk-WARNING **: 19:23:17.970: drawing 
failure for widget 'GtkImage': invalid value (typically too big) for the size 
of the input (surface, pattern, etc.)
  Feb  1 19:23:17 gnome-shell[15376]: DING: (gjs:23748): Gtk-WARNING **: 
19:23:17.970: drawing failure for widget 'GtkBox': invalid value (typically too 
big) for the size of the input (surface, pattern, etc.)
  Feb  1 19:23:17 gnome-shell[15376]: DING: (gjs:23748): Gtk-WARNING **: 
19:23:17.970: drawing failure for widget 'GtkEventBox': invalid value 
(typically too big) for the size of the input (surface, pattern, etc.)
  Feb  1 19:23:17  gnome-shell[15376]: DING: (gjs:23748): Gtk-WARNING **: 
19:23:17.970: drawing failure for widget 'GtkEventBox': invalid value 
(typically too big) for the size of the input (surface, pattern, etc.)
  Feb  1 19:23:17  gnome-shell[15376]: DING: (gjs:23748): Gtk-WARNING **: 
19:23:17.970: drawing failure for widget 'GtkBox': invalid value (typically too 
big) for the size of the input (surface, pattern, etc.)
  Feb  1 19:23:17  gnome-shell[15376]: DING: (gjs:23748): Gtk-WARNING **: 
19:23:17.970: drawing failure for widget 'GtkFixed': invalid value (typically 
too big) for the size of the input (surface, pattern, etc.)
  Feb  1 19:23:17  gnome-shell[15376]: DING: (gjs:23748): Gtk-WARNING **: 
19:23:17.970: drawing failure for widget 'GtkEventBox': invalid value 
(typically too big) for the size of the input (surface, pattern, etc.)
  Feb  1 19:23:17  gnome-shell[15376]: DING: (gjs:23748): Gtk-WARNING **: 
19:23:17.970: drawing failure for widget 'GtkApplicationWindow': invalid value 
(typically too big) for the size of the input (surface, pattern, etc.)
  st_widget_get_theme_node called on the widget [0x564e28a187d0 StBoxLayout 
("…")] which is not in the stage.
  gnome-shell[15376]: Window manager warning: Buggy client sent a 
_NET_ACTIVE_WINDOW message with a timestamp of 0 for 0x3a4
  Feb  1 19:02:01 gnome-control-c[19519]: Finalizing AdwPreferencesPage 
0x556a2f5a5b70, but it still has children left:
  Feb  1 19:02:01 gnome-control-c[19519]:- GtkCenterBox 0x556a2f5b2300
  Feb  1 19:02:03 gnome-shell[15376]: Window manager warning: Buggy client sent 
a _NET_ACTIVE_WINDOW message with a timestamp of 0 for 0x3a00018

  ProblemType: Bug
  DistroRelease: Ubuntu 22.10
  Package: gnome-shell 43.1-0ubuntu1
  ProcVersionSignature: Ubuntu 5.19.0-29.30-generic 5.19.17
  Uname: Linux 5.19.0-29-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  ApportVersion: 2.23.1-0ubuntu3
  Architecture: amd64
  CasperMD5CheckResult: unknown
  CurrentDesktop: ubuntu:GNOME
  Date: Wed Feb  1 23:40:47 2023
  DisplayManager: gdm3
  GsettingsChanges:
   b'org.gnome.shell' b'disable-user-extensions' b'true'
   b'org.gnome.desktop.input-sources' b'sources' b"[('xkb', 'us')]"
  InstallationDate: Installed on 2021-01-17 (745 days ago)
  InstallationMedia: Ubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731)
  ProcEnviron:
   LANGUAGE=en_CA:en
   TERM=xterm-256color
   PATH=(custom, no user)
   LANG=en_CA.UTF-8
   SHELL=/bin/bash
  RelatedPackageVersions: mutter-common 43.0-1ubuntu4
  SourcePackage: gnome-shell
  UpgradeStatus: Upgraded to kinetic on 2023-01-05 (27 days ago)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gtk+3.0/+bug/2004533/+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 2004534] Re: suspend does not work

[Daniel van Vugt]

Please also collect a system log of the problem.

If you had to reboot to recover from it then run:

  journalctl -b-1 > prevboot.txt

or if you didn't need to reboot then run:

  journalctl -b0 > journal.txt

and attach the resulting text file here.


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

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

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

Title:
  suspend does not work

Status in Ubuntu:
  Incomplete

Bug description:
   - on locked screen: the keyboard blocks after a while and I cannot login 
anymore;
   - on unlocked screen: 
   = apps do not start (failed to start); 
   = no icon pictures on desktop; 
   = no wallpaper anymore (black background);

  ProblemType: Bug
  DistroRelease: Ubuntu 22.04
  Package: xorg 1:7.7+23ubuntu2
  ProcVersionSignature: Ubuntu 5.15.0-58.64-generic 5.15.74
  Uname: Linux 5.15.0-58-generic x86_64
  ApportVersion: 2.20.11-0ubuntu82.3
  Architecture: amd64
  BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
  CasperMD5CheckResult: pass
  CompositorRunning: None
  CurrentDesktop: ubuntu:GNOME
  Date: Thu Feb  2 07:15:13 2023
  DistUpgraded: Fresh install
  DistroCodename: jammy
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes, including running git bisection searches
  GraphicsCard:
   Advanced Micro Devices, Inc. [AMD/ATI] Barcelo [1002:15e7] (rev c2) (prog-if 
00 [VGA controller])
 Subsystem: Lenovo Device [17aa:3801]
  InstallationDate: Installed on 2023-02-01 (1 days ago)
  InstallationMedia: Ubuntu 22.04.1 LTS "Jammy Jellyfish" - Release amd64 
(20220809.1)
  MachineType: LENOVO 82RN
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.15.0-58-generic 
root=UUID=b63af605-bd2f-4b16-8bb4-1cc9bb85554c ro quiet splash vt.handoff=7
  SourcePackage: xorg
  Symptom: display
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 08/04/2022
  dmi.bios.release: 1.38
  dmi.bios.vendor: LENOVO
  dmi.bios.version: JTCN38WW
  dmi.board.asset.tag: No Asset Tag
  dmi.board.name: LNVNB161216
  dmi.board.vendor: LENOVO
  dmi.board.version: NO DPK
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: IdeaPad 3 15ABA7
  dmi.ec.firmware.release: 1.38
  dmi.modalias: 
dmi:bvnLENOVO:bvrJTCN38WW:bd08/04/2022:br1.38:efr1.38:svnLENOVO:pn82RN:pvrIdeaPad315ABA7:rvnLENOVO:rnLNVNB161216:rvrNODPK:cvnLENOVO:ct10:cvrIdeaPad315ABA7:skuLENOVO_MT_82RN_BU_idea_FM_IdeaPad315ABA7:
  dmi.product.family: IdeaPad 3 15ABA7
  dmi.product.name: 82RN
  dmi.product.sku: LENOVO_MT_82RN_BU_idea_FM_IdeaPad 3 15ABA7
  dmi.product.version: IdeaPad 3 15ABA7
  dmi.sys.vendor: LENOVO
  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.110-1ubuntu1
  version.libgl1-mesa-dri: libgl1-mesa-dri 22.0.5-0ubuntu0.1
  version.libgl1-mesa-glx: libgl1-mesa-glx N/A
  version.xserver-xorg-core: xserver-xorg-core 2:21.1.3-2ubuntu2.5
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-2ubuntu1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20210115-1
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 
1:1.0.17-2build1

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+bug/2004534/+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 2004534] Re: suspend does not work

[Daniel van Vugt]

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

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

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

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


** Tags added: amdgpu

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

Title:
  suspend does not work

Status in Ubuntu:
  Incomplete

Bug description:
   - on locked screen: the keyboard blocks after a while and I cannot login 
anymore;
   - on unlocked screen: 
   = apps do not start (failed to start); 
   = no icon pictures on desktop; 
   = no wallpaper anymore (black background);

  ProblemType: Bug
  DistroRelease: Ubuntu 22.04
  Package: xorg 1:7.7+23ubuntu2
  ProcVersionSignature: Ubuntu 5.15.0-58.64-generic 5.15.74
  Uname: Linux 5.15.0-58-generic x86_64
  ApportVersion: 2.20.11-0ubuntu82.3
  Architecture: amd64
  BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
  CasperMD5CheckResult: pass
  CompositorRunning: None
  CurrentDesktop: ubuntu:GNOME
  Date: Thu Feb  2 07:15:13 2023
  DistUpgraded: Fresh install
  DistroCodename: jammy
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes, including running git bisection searches
  GraphicsCard:
   Advanced Micro Devices, Inc. [AMD/ATI] Barcelo [1002:15e7] (rev c2) (prog-if 
00 [VGA controller])
 Subsystem: Lenovo Device [17aa:3801]
  InstallationDate: Installed on 2023-02-01 (1 days ago)
  InstallationMedia: Ubuntu 22.04.1 LTS "Jammy Jellyfish" - Release amd64 
(20220809.1)
  MachineType: LENOVO 82RN
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.15.0-58-generic 
root=UUID=b63af605-bd2f-4b16-8bb4-1cc9bb85554c ro quiet splash vt.handoff=7
  SourcePackage: xorg
  Symptom: display
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 08/04/2022
  dmi.bios.release: 1.38
  dmi.bios.vendor: LENOVO
  dmi.bios.version: JTCN38WW
  dmi.board.asset.tag: No Asset Tag
  dmi.board.name: LNVNB161216
  dmi.board.vendor: LENOVO
  dmi.board.version: NO DPK
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: IdeaPad 3 15ABA7
  dmi.ec.firmware.release: 1.38
  dmi.modalias: 
dmi:bvnLENOVO:bvrJTCN38WW:bd08/04/2022:br1.38:efr1.38:svnLENOVO:pn82RN:pvrIdeaPad315ABA7:rvnLENOVO:rnLNVNB161216:rvrNODPK:cvnLENOVO:ct10:cvrIdeaPad315ABA7:skuLENOVO_MT_82RN_BU_idea_FM_IdeaPad315ABA7:
  dmi.product.family: IdeaPad 3 15ABA7
  dmi.product.name: 82RN
  dmi.product.sku: LENOVO_MT_82RN_BU_idea_FM_IdeaPad 3 15ABA7
  dmi.product.version: IdeaPad 3 15ABA7
  dmi.sys.vendor: LENOVO
  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.110-1ubuntu1
  version.libgl1-mesa-dri: libgl1-mesa-dri 22.0.5-0ubuntu0.1
  version.libgl1-mesa-glx: libgl1-mesa-glx N/A
  version.xserver-xorg-core: xserver-xorg-core 2:21.1.3-2ubuntu2.5
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-2ubuntu1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20210115-1
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 
1:1.0.17-2build1

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+bug/2004534/+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 2004533] Re: very unstable desktop, icons vanish, cannot control windows, cannot resize or scale multi monitors easily.

[Daniel van Vugt]

** No longer affects: nvidia-graphics-drivers-525 (Ubuntu)

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

Title:
  Gtk-WARNING **: ...: drawing failure for widget '...': invalid value
  (typically too big)

Status in gtk+3.0 package in Ubuntu:
  Incomplete

Bug description:
  A tiny sample of of my logs starting with the subject of this thread:
  gnome-shell[15376]: Can't update stage views actor [:0x564e0cfc0900] is on 
because it needs an allocation.
  others
  gnome-shell[15376]: DING: (gjs:23748): Gtk-WARNING **: 19:23:18.003: drawing 
failure for widget 'GtkImage': invalid value (typically too big) for the size 
of the input (surface, pattern, etc.)
  gnome-shell[15376]: DING: (gjs:23748): Gtk-WARNING **: 19:23:17.986: infinite 
surface size not supported
  gnome-shell[15376]: DING: (gjs:23748): Gtk-WARNING **: 19:23:17.970: drawing 
failure for widget 'GtkImage': invalid value (typically too big) for the size 
of the input (surface, pattern, etc.)
  Feb  1 19:23:17 gnome-shell[15376]: DING: (gjs:23748): Gtk-WARNING **: 
19:23:17.970: drawing failure for widget 'GtkBox': invalid value (typically too 
big) for the size of the input (surface, pattern, etc.)
  Feb  1 19:23:17 gnome-shell[15376]: DING: (gjs:23748): Gtk-WARNING **: 
19:23:17.970: drawing failure for widget 'GtkEventBox': invalid value 
(typically too big) for the size of the input (surface, pattern, etc.)
  Feb  1 19:23:17  gnome-shell[15376]: DING: (gjs:23748): Gtk-WARNING **: 
19:23:17.970: drawing failure for widget 'GtkEventBox': invalid value 
(typically too big) for the size of the input (surface, pattern, etc.)
  Feb  1 19:23:17  gnome-shell[15376]: DING: (gjs:23748): Gtk-WARNING **: 
19:23:17.970: drawing failure for widget 'GtkBox': invalid value (typically too 
big) for the size of the input (surface, pattern, etc.)
  Feb  1 19:23:17  gnome-shell[15376]: DING: (gjs:23748): Gtk-WARNING **: 
19:23:17.970: drawing failure for widget 'GtkFixed': invalid value (typically 
too big) for the size of the input (surface, pattern, etc.)
  Feb  1 19:23:17  gnome-shell[15376]: DING: (gjs:23748): Gtk-WARNING **: 
19:23:17.970: drawing failure for widget 'GtkEventBox': invalid value 
(typically too big) for the size of the input (surface, pattern, etc.)
  Feb  1 19:23:17  gnome-shell[15376]: DING: (gjs:23748): Gtk-WARNING **: 
19:23:17.970: drawing failure for widget 'GtkApplicationWindow': invalid value 
(typically too big) for the size of the input (surface, pattern, etc.)
  st_widget_get_theme_node called on the widget [0x564e28a187d0 StBoxLayout 
("…")] which is not in the stage.
  gnome-shell[15376]: Window manager warning: Buggy client sent a 
_NET_ACTIVE_WINDOW message with a timestamp of 0 for 0x3a4
  Feb  1 19:02:01 gnome-control-c[19519]: Finalizing AdwPreferencesPage 
0x556a2f5a5b70, but it still has children left:
  Feb  1 19:02:01 gnome-control-c[19519]:- GtkCenterBox 0x556a2f5b2300
  Feb  1 19:02:03 gnome-shell[15376]: Window manager warning: Buggy client sent 
a _NET_ACTIVE_WINDOW message with a timestamp of 0 for 0x3a00018

  ProblemType: Bug
  DistroRelease: Ubuntu 22.10
  Package: gnome-shell 43.1-0ubuntu1
  ProcVersionSignature: Ubuntu 5.19.0-29.30-generic 5.19.17
  Uname: Linux 5.19.0-29-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  ApportVersion: 2.23.1-0ubuntu3
  Architecture: amd64
  CasperMD5CheckResult: unknown
  CurrentDesktop: ubuntu:GNOME
  Date: Wed Feb  1 23:40:47 2023
  DisplayManager: gdm3
  GsettingsChanges:
   b'org.gnome.shell' b'disable-user-extensions' b'true'
   b'org.gnome.desktop.input-sources' b'sources' b"[('xkb', 'us')]"
  InstallationDate: Installed on 2021-01-17 (745 days ago)
  InstallationMedia: Ubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731)
  ProcEnviron:
   LANGUAGE=en_CA:en
   TERM=xterm-256color
   PATH=(custom, no user)
   LANG=en_CA.UTF-8
   SHELL=/bin/bash
  RelatedPackageVersions: mutter-common 43.0-1ubuntu4
  SourcePackage: gnome-shell
  UpgradeStatus: Upgraded to kinetic on 2023-01-05 (27 days ago)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gtk+3.0/+bug/2004533/+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 2004613] Re: Intel UHD Graphics 770 (ADL-S GT1) max res 1920x1080, should be 4K

[Daniel van Vugt]

The most likely explanation here is that the kernel is not offering 4K
as a supported resolution, which you can check by running:

  grep . /sys/class/drm/*/modes

If it's not listed there then you need a higher quality HDMI 2.0 cable.
Or even better to use DisplayPort instead.


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

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

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

Title:
  Intel UHD Graphics 770 (ADL-S GT1) max res 1920x1080, should be 4K

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  This GPU should be capable of 4K resolution, but it's unavailable.

  Tried manually adding modeline with

  xrandr --newmode "3840x2160_60.00"  712.75  3840 4160 4576 5312  2160 2163 
2168 2237 -hsync +vsync
  xrandr --addmode HDMI-3 "3840x2160_60.00"

  Still fails to set 4K resolution.

  Upgraded to signed kernel 5.19.0-28-generic #29~22.04.1-Ubuntu, added
  linux-modules-extra, ensured that system is loading i915 kernel
  module.

  inxi -G 
  Graphics:
Device-1: Intel driver: i915 v: kernel
Display: x11 server: X.Org v: 1.21.1.3 driver: X: loaded: modesetting
  unloaded: fbdev,vesa gpu: i915 resolution: 1920x1080~60Hz
OpenGL: renderer: Mesa Intel UHD Graphics 770 (ADL-S GT1)
  v: 4.6 Mesa 22.0.5

  lspci -k | head -10
  00:00.0 Host bridge: Intel Corporation Device 4650 (rev 05)
  Subsystem: Dell Device 0ac5
  00:02.0 VGA compatible controller: Intel Corporation Device 4690 (rev 0c)
  Subsystem: Dell Device 0ac5
  Kernel driver in use: i915
  Kernel modules: i915

  xrandr
  Screen 0: minimum 320 x 200, current 1920 x 1080, maximum 16384 x 16384
  DP-1 disconnected (normal left inverted right x axis y axis)
  HDMI-1 disconnected (normal left inverted right x axis y axis)
  DP-2 disconnected (normal left inverted right x axis y axis)
  HDMI-2 disconnected (normal left inverted right x axis y axis)
  HDMI-3 connected primary 1920x1080+0+0 (normal left inverted right x axis y 
axis) 800mm x 450mm
 1920x1080 60.00*   59.9430.0024.0029.9723.98  
 1920x1080i60.0059.94  
 1680x1050 59.88  
 1280x1024 75.0260.02  
 1440x900  59.90  
 1280x960  60.00  
 1360x768  60.02  
 1280x800  59.91  
 1152x864  75.00  
 1280x720  60.0030.0059.9429.9724.0023.98  
 1024x768  75.0370.0760.00  
 800x600   72.1975.0060.32  
 720x480   60.0059.94  
 720x480i  60.0059.94  
 640x480   75.0072.8160.0059.94  
 720x400   70.08  
 3840x2160_60.00  59.98  # <--- manually configured 

  xrandr --output HDMI-3 --mode 3840x2160_60.00
  xrandr: Configure crtc 0 failed

  ProblemType: Bug
  DistroRelease: Ubuntu 22.04
  Package: xorg 1:7.7+23ubuntu2
  ProcVersionSignature: Ubuntu 5.19.0-28.29~22.04.1-generic 5.19.17
  Uname: Linux 5.19.0-28-generic x86_64
  ApportVersion: 2.20.11-0ubuntu82.3
  Architecture: amd64
  BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
  CasperMD5CheckResult: unknown
  CompositorRunning: None
  CurrentDesktop: KDE
  Date: Thu Feb  2 22:00:36 2023
  DistUpgraded: 2023-01-28 19:49:57,594 DEBUG Running PostInstallScript: 
'/usr/lib/ubuntu-advantage/upgrade_lts_contract.py'
  DistroCodename: jammy
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes, including running git bisection searches
  GraphicsCard:
   Intel Corporation Device [8086:4690] (rev 0c) (prog-if 00 [VGA controller])
 Subsystem: Dell Device [1028:0ac5]
  InstallationDate: Installed on 2020-07-18 (929 days ago)
  InstallationMedia: Kubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423)
  Lsusb:
   Bus 002 Device 002: ID 0480:0110 Toshiba America Inc External USB 3.0
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 003: ID 0489:e0c8 Foxconn / Hon Hai Wireless_Device
   Bus 001 Device 002: ID 248a:8367 Maxxter Telink Wireless Receiver
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: Dell Inc. OptiPlex 3000
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.19.0-28-generic 
root=/dev/mapper/vgkubuntu-root ro nosplash
  SourcePackage: xorg
  Symptom: display
  UpgradeStatus: Upgraded to jammy on 2023-01-29 (5 days ago)
  dmi.bios.date: 05/18/2022
  dmi.bios.release: 1.1
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: 1.1.60
  dmi.board.name: 057FFP
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A00
  dmi.chassis.type: 3
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvr1.1.60:bd05/18/2022:br1.1:svnDellInc.:pnOptiPlex3000:pvr:rvnDellInc.:rn057FFP:rvrA00:cvnDellInc.:ct3:cvr:sku0AC5:
  dmi.product.family: OptiPlex
  dmi.product.name: OptiPlex 3000
  dmi.product.sku: 0AC5
  

[Touch-packages] [Bug 2004533] Re: very unstable desktop, icons vanish, cannot control windows, cannot resize or scale multi monitors easily.

[Daniel van Vugt]

It looks like you're using Xorg fractional scaling, so yes that will
take the texture requirements past the limit supported by the GPU if you
do it across multiple 4K monitors. Some parts of the desktop will cope
and other parts (GTK) might not cope.

To confirm this, please run:

  xrandr --verbose > xrandr.txt

and attach the resulting text file here.

Possible workarounds (you only need one):

  * Only use integer scaling
  * Only use Wayland sessions
  * Use fewer monitors


** Package changed: gnome-shell (Ubuntu) => gtk+3.0 (Ubuntu)

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

** Package changed: ubuntu => nvidia-graphics-drivers-525 (Ubuntu)

** Package changed: gnome-shell-extension-desktop-icons-ng (Ubuntu) =>
gtk+3.0 (Ubuntu)

** Tags added: xrandr-scaling

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

Title:
  very unstable desktop, icons vanish, cannot control windows, cannot
  resize or scale multi monitors easily.

Status in gtk+3.0 package in Ubuntu:
  Incomplete
Status in nvidia-graphics-drivers-525 package in Ubuntu:
  Incomplete

Bug description:
  A tiny sample of of my logs starting with the subject of this thread:
  gnome-shell[15376]: Can't update stage views actor [:0x564e0cfc0900] is on 
because it needs an allocation.
  others
  gnome-shell[15376]: DING: (gjs:23748): Gtk-WARNING **: 19:23:18.003: drawing 
failure for widget 'GtkImage': invalid value (typically too big) for the size 
of the input (surface, pattern, etc.)
  gnome-shell[15376]: DING: (gjs:23748): Gtk-WARNING **: 19:23:17.986: infinite 
surface size not supported
  gnome-shell[15376]: DING: (gjs:23748): Gtk-WARNING **: 19:23:17.970: drawing 
failure for widget 'GtkImage': invalid value (typically too big) for the size 
of the input (surface, pattern, etc.)
  Feb  1 19:23:17 gnome-shell[15376]: DING: (gjs:23748): Gtk-WARNING **: 
19:23:17.970: drawing failure for widget 'GtkBox': invalid value (typically too 
big) for the size of the input (surface, pattern, etc.)
  Feb  1 19:23:17 gnome-shell[15376]: DING: (gjs:23748): Gtk-WARNING **: 
19:23:17.970: drawing failure for widget 'GtkEventBox': invalid value 
(typically too big) for the size of the input (surface, pattern, etc.)
  Feb  1 19:23:17  gnome-shell[15376]: DING: (gjs:23748): Gtk-WARNING **: 
19:23:17.970: drawing failure for widget 'GtkEventBox': invalid value 
(typically too big) for the size of the input (surface, pattern, etc.)
  Feb  1 19:23:17  gnome-shell[15376]: DING: (gjs:23748): Gtk-WARNING **: 
19:23:17.970: drawing failure for widget 'GtkBox': invalid value (typically too 
big) for the size of the input (surface, pattern, etc.)
  Feb  1 19:23:17  gnome-shell[15376]: DING: (gjs:23748): Gtk-WARNING **: 
19:23:17.970: drawing failure for widget 'GtkFixed': invalid value (typically 
too big) for the size of the input (surface, pattern, etc.)
  Feb  1 19:23:17  gnome-shell[15376]: DING: (gjs:23748): Gtk-WARNING **: 
19:23:17.970: drawing failure for widget 'GtkEventBox': invalid value 
(typically too big) for the size of the input (surface, pattern, etc.)
  Feb  1 19:23:17  gnome-shell[15376]: DING: (gjs:23748): Gtk-WARNING **: 
19:23:17.970: drawing failure for widget 'GtkApplicationWindow': invalid value 
(typically too big) for the size of the input (surface, pattern, etc.)
  st_widget_get_theme_node called on the widget [0x564e28a187d0 StBoxLayout 
("…")] which is not in the stage.
  gnome-shell[15376]: Window manager warning: Buggy client sent a 
_NET_ACTIVE_WINDOW message with a timestamp of 0 for 0x3a4
  Feb  1 19:02:01 gnome-control-c[19519]: Finalizing AdwPreferencesPage 
0x556a2f5a5b70, but it still has children left:
  Feb  1 19:02:01 gnome-control-c[19519]:- GtkCenterBox 0x556a2f5b2300
  Feb  1 19:02:03 gnome-shell[15376]: Window manager warning: Buggy client sent 
a _NET_ACTIVE_WINDOW message with a timestamp of 0 for 0x3a00018

  ProblemType: Bug
  DistroRelease: Ubuntu 22.10
  Package: gnome-shell 43.1-0ubuntu1
  ProcVersionSignature: Ubuntu 5.19.0-29.30-generic 5.19.17
  Uname: Linux 5.19.0-29-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  ApportVersion: 2.23.1-0ubuntu3
  Architecture: amd64
  CasperMD5CheckResult: unknown
  CurrentDesktop: ubuntu:GNOME
  Date: Wed Feb  1 23:40:47 2023
  DisplayManager: gdm3
  GsettingsChanges:
   b'org.gnome.shell' b'disable-user-extensions' b'true'
   b'org.gnome.desktop.input-sources' b'sources' b"[('xkb', 'us')]"
  InstallationDate: Installed on 2021-01-17 (745 days ago)
  InstallationMedia: Ubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731)
  ProcEnviron:
   LANGUAGE=en_CA:en
   TERM=xterm-256color
   PATH=(custom, no user)
   LANG=en_CA.UTF-8
   SHELL=/bin/bash
  RelatedPackageVersions: mutter-common 43.0-1ubuntu4
  SourcePackage: gnome-shell
  UpgradeStatus: Upgraded to kinetic on 2023-01-05 (27 days ago)

To manage notifications 

[Touch-packages] [Bug 2004533] [NEW] very unstable desktop, icons vanish, cannot control windows, cannot resize or scale multi monitors easily.

[Launchpad Bug Tracker]

You have been subscribed to a public bug:

A tiny sample of of my logs starting with the subject of this thread:
gnome-shell[15376]: Can't update stage views actor [:0x564e0cfc0900] is on 
because it needs an allocation.
others
gnome-shell[15376]: DING: (gjs:23748): Gtk-WARNING **: 19:23:18.003: drawing 
failure for widget 'GtkImage': invalid value (typically too big) for the size 
of the input (surface, pattern, etc.)
gnome-shell[15376]: DING: (gjs:23748): Gtk-WARNING **: 19:23:17.986: infinite 
surface size not supported
gnome-shell[15376]: DING: (gjs:23748): Gtk-WARNING **: 19:23:17.970: drawing 
failure for widget 'GtkImage': invalid value (typically too big) for the size 
of the input (surface, pattern, etc.)
Feb  1 19:23:17 gnome-shell[15376]: DING: (gjs:23748): Gtk-WARNING **: 
19:23:17.970: drawing failure for widget 'GtkBox': invalid value (typically too 
big) for the size of the input (surface, pattern, etc.)
Feb  1 19:23:17 gnome-shell[15376]: DING: (gjs:23748): Gtk-WARNING **: 
19:23:17.970: drawing failure for widget 'GtkEventBox': invalid value 
(typically too big) for the size of the input (surface, pattern, etc.)
Feb  1 19:23:17  gnome-shell[15376]: DING: (gjs:23748): Gtk-WARNING **: 
19:23:17.970: drawing failure for widget 'GtkEventBox': invalid value 
(typically too big) for the size of the input (surface, pattern, etc.)
Feb  1 19:23:17  gnome-shell[15376]: DING: (gjs:23748): Gtk-WARNING **: 
19:23:17.970: drawing failure for widget 'GtkBox': invalid value (typically too 
big) for the size of the input (surface, pattern, etc.)
Feb  1 19:23:17  gnome-shell[15376]: DING: (gjs:23748): Gtk-WARNING **: 
19:23:17.970: drawing failure for widget 'GtkFixed': invalid value (typically 
too big) for the size of the input (surface, pattern, etc.)
Feb  1 19:23:17  gnome-shell[15376]: DING: (gjs:23748): Gtk-WARNING **: 
19:23:17.970: drawing failure for widget 'GtkEventBox': invalid value 
(typically too big) for the size of the input (surface, pattern, etc.)
Feb  1 19:23:17  gnome-shell[15376]: DING: (gjs:23748): Gtk-WARNING **: 
19:23:17.970: drawing failure for widget 'GtkApplicationWindow': invalid value 
(typically too big) for the size of the input (surface, pattern, etc.)
st_widget_get_theme_node called on the widget [0x564e28a187d0 StBoxLayout 
("…")] which is not in the stage.
gnome-shell[15376]: Window manager warning: Buggy client sent a 
_NET_ACTIVE_WINDOW message with a timestamp of 0 for 0x3a4
Feb  1 19:02:01 gnome-control-c[19519]: Finalizing AdwPreferencesPage 
0x556a2f5a5b70, but it still has children left:
Feb  1 19:02:01 gnome-control-c[19519]:- GtkCenterBox 0x556a2f5b2300
Feb  1 19:02:03 gnome-shell[15376]: Window manager warning: Buggy client sent a 
_NET_ACTIVE_WINDOW message with a timestamp of 0 for 0x3a00018

ProblemType: Bug
DistroRelease: Ubuntu 22.10
Package: gnome-shell 43.1-0ubuntu1
ProcVersionSignature: Ubuntu 5.19.0-29.30-generic 5.19.17
Uname: Linux 5.19.0-29-generic x86_64
NonfreeKernelModules: nvidia_modeset nvidia
ApportVersion: 2.23.1-0ubuntu3
Architecture: amd64
CasperMD5CheckResult: unknown
CurrentDesktop: ubuntu:GNOME
Date: Wed Feb  1 23:40:47 2023
DisplayManager: gdm3
GsettingsChanges:
 b'org.gnome.shell' b'disable-user-extensions' b'true'
 b'org.gnome.desktop.input-sources' b'sources' b"[('xkb', 'us')]"
InstallationDate: Installed on 2021-01-17 (745 days ago)
InstallationMedia: Ubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731)
ProcEnviron:
 LANGUAGE=en_CA:en
 TERM=xterm-256color
 PATH=(custom, no user)
 LANG=en_CA.UTF-8
 SHELL=/bin/bash
RelatedPackageVersions: mutter-common 43.0-1ubuntu4
SourcePackage: gnome-shell
UpgradeStatus: Upgraded to kinetic on 2023-01-05 (27 days ago)

** Affects: gtk+3.0 (Ubuntu)
 Importance: Undecided
 Status: Incomplete

** Affects: nvidia-graphics-drivers-525 (Ubuntu)
 Importance: Undecided
 Status: Incomplete


** Tags: amd64 apport-bug kinetic
-- 
very unstable desktop, icons vanish, cannot control windows, cannot resize or 
scale multi monitors easily.
https://bugs.launchpad.net/bugs/2004533
You received this bug notification because you are a member of Ubuntu Touch 
seeded packages, which is subscribed to gtk+3.0 in Ubuntu.

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

[Touch-packages] [Bug 2004533] [NEW] very unstable desktop, icons vanish, cannot control windows, cannot resize or scale multi monitors easily.

[Launchpad Bug Tracker]

You have been subscribed to a public bug:

A tiny sample of of my logs starting with the subject of this thread:
gnome-shell[15376]: Can't update stage views actor [:0x564e0cfc0900] is on 
because it needs an allocation.
others
gnome-shell[15376]: DING: (gjs:23748): Gtk-WARNING **: 19:23:18.003: drawing 
failure for widget 'GtkImage': invalid value (typically too big) for the size 
of the input (surface, pattern, etc.)
gnome-shell[15376]: DING: (gjs:23748): Gtk-WARNING **: 19:23:17.986: infinite 
surface size not supported
gnome-shell[15376]: DING: (gjs:23748): Gtk-WARNING **: 19:23:17.970: drawing 
failure for widget 'GtkImage': invalid value (typically too big) for the size 
of the input (surface, pattern, etc.)
Feb  1 19:23:17 gnome-shell[15376]: DING: (gjs:23748): Gtk-WARNING **: 
19:23:17.970: drawing failure for widget 'GtkBox': invalid value (typically too 
big) for the size of the input (surface, pattern, etc.)
Feb  1 19:23:17 gnome-shell[15376]: DING: (gjs:23748): Gtk-WARNING **: 
19:23:17.970: drawing failure for widget 'GtkEventBox': invalid value 
(typically too big) for the size of the input (surface, pattern, etc.)
Feb  1 19:23:17  gnome-shell[15376]: DING: (gjs:23748): Gtk-WARNING **: 
19:23:17.970: drawing failure for widget 'GtkEventBox': invalid value 
(typically too big) for the size of the input (surface, pattern, etc.)
Feb  1 19:23:17  gnome-shell[15376]: DING: (gjs:23748): Gtk-WARNING **: 
19:23:17.970: drawing failure for widget 'GtkBox': invalid value (typically too 
big) for the size of the input (surface, pattern, etc.)
Feb  1 19:23:17  gnome-shell[15376]: DING: (gjs:23748): Gtk-WARNING **: 
19:23:17.970: drawing failure for widget 'GtkFixed': invalid value (typically 
too big) for the size of the input (surface, pattern, etc.)
Feb  1 19:23:17  gnome-shell[15376]: DING: (gjs:23748): Gtk-WARNING **: 
19:23:17.970: drawing failure for widget 'GtkEventBox': invalid value 
(typically too big) for the size of the input (surface, pattern, etc.)
Feb  1 19:23:17  gnome-shell[15376]: DING: (gjs:23748): Gtk-WARNING **: 
19:23:17.970: drawing failure for widget 'GtkApplicationWindow': invalid value 
(typically too big) for the size of the input (surface, pattern, etc.)
st_widget_get_theme_node called on the widget [0x564e28a187d0 StBoxLayout 
("…")] which is not in the stage.
gnome-shell[15376]: Window manager warning: Buggy client sent a 
_NET_ACTIVE_WINDOW message with a timestamp of 0 for 0x3a4
Feb  1 19:02:01 gnome-control-c[19519]: Finalizing AdwPreferencesPage 
0x556a2f5a5b70, but it still has children left:
Feb  1 19:02:01 gnome-control-c[19519]:- GtkCenterBox 0x556a2f5b2300
Feb  1 19:02:03 gnome-shell[15376]: Window manager warning: Buggy client sent a 
_NET_ACTIVE_WINDOW message with a timestamp of 0 for 0x3a00018

ProblemType: Bug
DistroRelease: Ubuntu 22.10
Package: gnome-shell 43.1-0ubuntu1
ProcVersionSignature: Ubuntu 5.19.0-29.30-generic 5.19.17
Uname: Linux 5.19.0-29-generic x86_64
NonfreeKernelModules: nvidia_modeset nvidia
ApportVersion: 2.23.1-0ubuntu3
Architecture: amd64
CasperMD5CheckResult: unknown
CurrentDesktop: ubuntu:GNOME
Date: Wed Feb  1 23:40:47 2023
DisplayManager: gdm3
GsettingsChanges:
 b'org.gnome.shell' b'disable-user-extensions' b'true'
 b'org.gnome.desktop.input-sources' b'sources' b"[('xkb', 'us')]"
InstallationDate: Installed on 2021-01-17 (745 days ago)
InstallationMedia: Ubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731)
ProcEnviron:
 LANGUAGE=en_CA:en
 TERM=xterm-256color
 PATH=(custom, no user)
 LANG=en_CA.UTF-8
 SHELL=/bin/bash
RelatedPackageVersions: mutter-common 43.0-1ubuntu4
SourcePackage: gnome-shell
UpgradeStatus: Upgraded to kinetic on 2023-01-05 (27 days ago)

** Affects: gtk+3.0 (Ubuntu)
 Importance: Undecided
 Status: Incomplete

** Affects: gnome-shell-extension-desktop-icons-ng (Ubuntu)
 Importance: Undecided
 Status: Incomplete


** Tags: amd64 apport-bug kinetic
-- 
very unstable desktop, icons vanish, cannot control windows, cannot resize or 
scale multi monitors easily.
https://bugs.launchpad.net/bugs/2004533
You received this bug notification because you are a member of Ubuntu Touch 
seeded packages, which is subscribed to gtk+3.0 in Ubuntu.

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

[Touch-packages] [Bug 2004613] [NEW] Intel UHD Graphics 770 (ADL-S GT1) max res 1920x1080, should be 4K

[Nicholas Leskiw]

Public bug reported:

This GPU should be capable of 4K resolution, but it's unavailable.

Tried manually adding modeline with

xrandr --newmode "3840x2160_60.00"  712.75  3840 4160 4576 5312  2160 2163 2168 
2237 -hsync +vsync
xrandr --addmode HDMI-3 "3840x2160_60.00"

Still fails to set 4K resolution.

Upgraded to signed kernel 5.19.0-28-generic #29~22.04.1-Ubuntu, added
linux-modules-extra, ensured that system is loading i915 kernel module.

inxi -G 
Graphics:
  Device-1: Intel driver: i915 v: kernel
  Display: x11 server: X.Org v: 1.21.1.3 driver: X: loaded: modesetting
unloaded: fbdev,vesa gpu: i915 resolution: 1920x1080~60Hz
  OpenGL: renderer: Mesa Intel UHD Graphics 770 (ADL-S GT1)
v: 4.6 Mesa 22.0.5

lspci -k | head -10
00:00.0 Host bridge: Intel Corporation Device 4650 (rev 05)
Subsystem: Dell Device 0ac5
00:02.0 VGA compatible controller: Intel Corporation Device 4690 (rev 0c)
Subsystem: Dell Device 0ac5
Kernel driver in use: i915
Kernel modules: i915

xrandr
Screen 0: minimum 320 x 200, current 1920 x 1080, maximum 16384 x 16384
DP-1 disconnected (normal left inverted right x axis y axis)
HDMI-1 disconnected (normal left inverted right x axis y axis)
DP-2 disconnected (normal left inverted right x axis y axis)
HDMI-2 disconnected (normal left inverted right x axis y axis)
HDMI-3 connected primary 1920x1080+0+0 (normal left inverted right x axis y 
axis) 800mm x 450mm
   1920x1080 60.00*   59.9430.0024.0029.9723.98  
   1920x1080i60.0059.94  
   1680x1050 59.88  
   1280x1024 75.0260.02  
   1440x900  59.90  
   1280x960  60.00  
   1360x768  60.02  
   1280x800  59.91  
   1152x864  75.00  
   1280x720  60.0030.0059.9429.9724.0023.98  
   1024x768  75.0370.0760.00  
   800x600   72.1975.0060.32  
   720x480   60.0059.94  
   720x480i  60.0059.94  
   640x480   75.0072.8160.0059.94  
   720x400   70.08  
   3840x2160_60.00  59.98  # <--- manually configured 

xrandr --output HDMI-3 --mode 3840x2160_60.00
xrandr: Configure crtc 0 failed

ProblemType: Bug
DistroRelease: Ubuntu 22.04
Package: xorg 1:7.7+23ubuntu2
ProcVersionSignature: Ubuntu 5.19.0-28.29~22.04.1-generic 5.19.17
Uname: Linux 5.19.0-28-generic x86_64
ApportVersion: 2.20.11-0ubuntu82.3
Architecture: amd64
BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
CasperMD5CheckResult: unknown
CompositorRunning: None
CurrentDesktop: KDE
Date: Thu Feb  2 22:00:36 2023
DistUpgraded: 2023-01-28 19:49:57,594 DEBUG Running PostInstallScript: 
'/usr/lib/ubuntu-advantage/upgrade_lts_contract.py'
DistroCodename: jammy
DistroVariant: ubuntu
ExtraDebuggingInterest: Yes, including running git bisection searches
GraphicsCard:
 Intel Corporation Device [8086:4690] (rev 0c) (prog-if 00 [VGA controller])
   Subsystem: Dell Device [1028:0ac5]
InstallationDate: Installed on 2020-07-18 (929 days ago)
InstallationMedia: Kubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423)
Lsusb:
 Bus 002 Device 002: ID 0480:0110 Toshiba America Inc External USB 3.0
 Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
 Bus 001 Device 003: ID 0489:e0c8 Foxconn / Hon Hai Wireless_Device
 Bus 001 Device 002: ID 248a:8367 Maxxter Telink Wireless Receiver
 Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
MachineType: Dell Inc. OptiPlex 3000
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.19.0-28-generic 
root=/dev/mapper/vgkubuntu-root ro nosplash
SourcePackage: xorg
Symptom: display
UpgradeStatus: Upgraded to jammy on 2023-01-29 (5 days ago)
dmi.bios.date: 05/18/2022
dmi.bios.release: 1.1
dmi.bios.vendor: Dell Inc.
dmi.bios.version: 1.1.60
dmi.board.name: 057FFP
dmi.board.vendor: Dell Inc.
dmi.board.version: A00
dmi.chassis.type: 3
dmi.chassis.vendor: Dell Inc.
dmi.modalias: 
dmi:bvnDellInc.:bvr1.1.60:bd05/18/2022:br1.1:svnDellInc.:pnOptiPlex3000:pvr:rvnDellInc.:rn057FFP:rvrA00:cvnDellInc.:ct3:cvr:sku0AC5:
dmi.product.family: OptiPlex
dmi.product.name: OptiPlex 3000
dmi.product.sku: 0AC5
dmi.sys.vendor: Dell Inc.
version.compiz: compiz N/A
version.libdrm2: libdrm2 2.4.110-1ubuntu1
version.libgl1-mesa-dri: libgl1-mesa-dri 22.0.5-0ubuntu0.3
version.libgl1-mesa-glx: libgl1-mesa-glx 22.0.5-0ubuntu0.3
version.xserver-xorg-core: xserver-xorg-core 2:21.1.3-2ubuntu2.5
version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-2ubuntu1
version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20210115-1
version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.17-2build1

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


** Tags: amd64 apport-bug jammy kubuntu resolution ubuntu

** Summary changed:

- Intel Intel UHD Graphics 770 (ADL-S GT1) max res 1920x1080, should be 4K
+ Intel UHD Graphics 770 (ADL-S GT1) max res 1920x1080, should be 4K

-- 
You 

[Touch-packages] [Bug 2003331] Re: Can't log in to lunar x11 session

[Gunnar Hjalmarsson]

On 2023-02-02 20:25, Brian Murray wrote:
> Could this be a duplicate of bug 2004092?

I don't think so. The buttons showed up as expected, and I installed
successfully. My user ID is 1000. The problem is that I can't log in to
"Ubuntu on Xorg".

Just updated the packages and the problem is still present.

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

Title:
  Can't log in to lunar x11 session

Status in ubuntu-meta package in Ubuntu:
  New

Bug description:
  On a freshly installed and updated lunar in VirtualBox it doesn't let
  me log in to Ubuntu on Xorg. I'm just bumped back to the login screen.
  journalctl extract attached.

  On my regular (updated) lunar install, logging in to Ubuntu on Xorg
  works fine. But that's anything but a fresh install.

  Missing dependency?

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


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

[Touch-packages] [Bug 2004477] Re: cryptography pkg 39.0.0 incompatible with pyOpenSSL 21.0.0 - crashes ensue

[Donald H Locker]

** Summary changed:

- Can't launch proton vpn
+ cryptography pkg 39.0.0 incompatible with pyOpenSSL 21.0.0 - crashes ensue

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

Title:
  cryptography pkg 39.0.0 incompatible with pyOpenSSL 21.0.0 - crashes
  ensue

Status in openssl package in Ubuntu:
  New

Bug description:
  crypto.py crashes when starting protonvpn:

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

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

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

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

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

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

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

  but downgrading openssl package is not desirable for security reasons.

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

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

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


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

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

[Mehmet Can Cömert]

My current user experience is like following:
I just updated kept-back packages by mistake today by using apt install 
command. 
I thought it was due to a wrong mark of Manuel tag in apt and marked them with 
apt-mark auto again.
Then after a bit search in internet I realized that it is due to a phased 
update policy, which makes sense.

I think either message should not shown at all (as suggested above)
or if you want to show the list, please state somehow that this is only info 
and we do not have to do something about it, such as:
The following packages have been kept back as a part of phased update policy of 
Ubuntu:

Just stating packages are kept back, gives the impression that something
is broken in the dependency resolution.

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

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

Status in apt package in Ubuntu:
  Triaged

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

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

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

  Incidentally note that aptitude does not respect phased updates.

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

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


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

[Touch-packages] [Bug 2004551] Re: upgrade to lunar fails due to rescue-ssh.target or port 22 takeover

[Steve Langasek]

> rescue-ssh.target is a disabled or a static unit not running, not
starting it.

Not really a complaint, just informational.

> But I think the underlying issue is that ssh is already on, and I'm logged in 
> via it.
> And that makes the service restart of the ssh socket which was added break.

I recall that I did test this case without problem.  sshd in general
doesn't fail if there are open connections and you restart it, because
it properly configures its sockets with SO_REUSEADDR.

To debug this I would really want to see what process is holding that
port; but as you've rebooted, that's not really possible to see now.  If
you ever reproduce it on another instance, please grab the output of
fuser -n tcp 22 or equivalent!  If we failed to stop the ssh.service, we
want to see why.

> One thing though, I have not upgraded with do-release-upgrade - would we
> / do we have magic there to make the ssh socket activation transition 
> smoother?

No, this is all supposed to be handled cleanly with the package
maintainer scripts alone.

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

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

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

Title:
  upgrade to lunar fails due to rescue-ssh.target or port 22 takeover

Status in openssh package in Ubuntu:
  Incomplete

Bug description:
  Hi,
  I just upgraded a system from Jammy to Lunar and openssh-server refuses to 
upgrade well.

  Setting up openssh-server (1:9.0p1-1ubuntu8) ...
  Replacing config file /etc/ssh/sshd_config with new version
  Replacing config file /etc/ssh/sshd_config with new version
  Synchronizing state of ssh.service with SysV service script with 
/lib/systemd/systemd-sysv-install.
  Executing: /lib/systemd/systemd-sysv-install disable ssh
  rescue-ssh.target is a disabled or a static unit not running, not starting it.
  Could not execute systemctl:  at /usr/bin/deb-systemd-invoke line 145.
  dpkg: error processing package openssh-server (--configure):
   installed openssh-server package post-installation script subprocess 
returned error exit status 1
  Processing triggers for man-db (2.11.2-1) ...
  Processing triggers for libc-bin (2.36-0ubuntu4) ...
  Errors were encountered while processing:
   openssh-server
  Error: Timeout was reached
  needrestart is being skipped since dpkg has failed
  E: Sub-process /usr/bin/dpkg returned an error code (1)

  I'm not sure what exactly it is.
  This output complains about rescue-ssh.target and indeed that can not be 
started even directly.

  $ sudo systemctl start rescue-ssh.target
  A dependency job for rescue-ssh.target failed. See 'journalctl -xe' for 
details.

  And in postinst is a try to start it:
  $  grep rescue /var/lib/dpkg/info/openssh-server.postinst 
deb-systemd-invoke $_dh_action 'rescue-ssh.target' >/dev/null 
|| true

  
  But I think the underlying issue is that ssh is already on, and I'm logged in 
via it.
  And that makes the service restart of the ssh socket which was added break.

  Feb 02 10:40:56 node-horsea systemd[104560]: ssh.socket: Failed to create 
listening socket ([::]:22): Address already in use
  Feb 02 10:40:56 node-horsea systemd[1]: ssh.socket: Failed to receive 
listening socket ([::]:22): Input/output error
  Feb 02 10:40:56 node-horsea systemd[1]: ssh.socket: Failed to listen on 
sockets: Input/output error
  Feb 02 10:40:56 node-horsea systemd[1]: ssh.socket: Failed with result 
'resources'.

  
  Now, whichever it is, it is hard to resolve.
  The only way to get the socket to own it would be rebooting so that sshd lets 
go and systemd can take over.
  I could reboot, but that is not the point.
  What if I'd want to get the service and upgrade completed before reboot.
  Because as of now dpkg considers the system unhappy, and that would usually 
be a sign for "better not reboot before being resolved" to me.

  One thing though, I have not upgraded with do-release-upgrade - would
  we / do we have magic there to make the ssh socket activation
  transition smoother?

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


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

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

[Launchpad Bug Tracker]

This bug was fixed in the package ubuntu-dev-tools - 0.192

---
ubuntu-dev-tools (0.192) unstable; urgency=medium

  [ Benjamin Drung ]
  * sponsor-patch:
+ Ignore exit code 1 of debdiff call.
+ Use --skip-patches instead of --no-preparation with dpkg-source -x.
  * Demote bzr/brz from Recommends to Suggests, as nowadays git is the way.
Closes: #940531
  * Use PEP440 compliant version in setup.py (LP: #1991606)
  * Fix issues found by flake8 on the Python scripts
  * Check Python scripts with flake8 again
  * Format Python code with black and run black during package build
  * Sort Python imports with isort and run isort during package build
  * Replace deprecated optparse with argparse
  * requestbackport: Remove useless loop from locate_package
  * reverse-depends: Restore field titles format
  * test: Fix deprecated return value for test case
  * Fix all errors and warnings found by pylint and implement most refactorings
and conventions. Run pylint during package build again.
  * Bump Standards-Version to 4.6.2
  * Drop unneeded X-Python3-Version from d/control

  [ Masahiro Yamada ]
  * mk-sbuild:
+ Handle the new location of the Debian bullseye security archive.
  Closes: #1001832; LP: #1955116

  [ Mattia Rizzolo ]
  * requestbackport:
+ Apply patch from Krytarik Raido and Unit 193 to update the template and
  workflow after the new Ubuntu Backport process has been established.
  LP: #1959115

 -- Benjamin Drung   Wed, 01 Feb 2023 12:45:15 +0100

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

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

Title:
  Invalid PEP440 package version breaking setuptools >= 60

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

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

    File 
"/builds/databiosphere/toil/venv/lib/python3.9/site-packages/pkg_resources/__init__.py",
 line 844, in _resolve_dist
  env = Environment(self.entries)
    File 
"/builds/databiosphere/toil/venv/lib/python3.9/site-packages/pkg_resources/__init__.py",
 line 1044, in __init__
  self.scan(search_path)
    File 
"/builds/databiosphere/toil/venv/lib/python3.9/site-packages/pkg_resources/__init__.py",
 line 1077, in scan
  self.add(dist)
    File 
"/builds/databiosphere/toil/venv/lib/python3.9/site-packages/pkg_resources/__init__.py",
 line 1096, in add
  dists.sort(key=operator.attrgetter('hashcmp'), reverse=True)
    File 
"/builds/databiosphere/toil/venv/lib/python3.9/site-packages/pkg_resources/__init__.py",
 line 2631, in hashcmp
  self.parsed_version,
    File 
"/builds/databiosphere/toil/venv/lib/python3.9/site-packages/pkg_resources/__init__.py",
 line 2678, in 

[Touch-packages] [Bug 1877219] Re: dozens of empty grilo-plugin-cache folders polluting /tmp

[Launchpad Bug Tracker]

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

** Changed in: grilo-plugins (Ubuntu)
   Status: New => Confirmed

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

Title:
  dozens of empty grilo-plugin-cache folders polluting /tmp

Status in Grilo Plugins:
  Fix Released
Status in grilo-plugins package in Ubuntu:
  Confirmed

Bug description:
  My /tmp folder has dozens of empty folders with names like grilo-
  plugin-cache-ABCDEF. I don't know anything about grilo-plugins, but
  surely they can do their job without leaving endless garbage
  directories behind when they're done?

  $ lsb_release -a
  No LSB modules are available.
  Distributor ID:   Ubuntu
  Description:  Ubuntu 19.10
  Release:  19.10
  Codename: eoan

  $ dpkg-query --show grilo-plugins-0.3-base
  grilo-plugins-0.3-base:amd64  0.3.9-1ubuntu1

To manage notifications about this bug go to:
https://bugs.launchpad.net/grilo-plugins/+bug/1877219/+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 2003331] Re: Can't log in to lunar x11 session

[Brian Murray]

Could this be a duplicate of bug 2004092?

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

Title:
  Can't log in to lunar x11 session

Status in ubuntu-meta package in Ubuntu:
  New

Bug description:
  On a freshly installed and updated lunar in VirtualBox it doesn't let
  me log in to Ubuntu on Xorg. I'm just bumped back to the login screen.
  journalctl extract attached.

  On my regular (updated) lunar install, logging in to Ubuntu on Xorg
  works fine. But that's anything but a fresh install.

  Missing dependency?

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/ubuntu-meta/+bug/2003331/+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 2003756] Re: Cannot configure krb5-kdc on Ubuntu Jammy 22.04.01, "Could not execute systemctl: at /usr/bin/deb-systemd-invoke line 142."

[Sam Hartman]

> "Sergio" == Sergio Durigan Junior <2003...@bugs.launchpad.net> writes:
Sergio> systemd-invoke will try to run systemctl like this:

Sergio> systemctl --quiet --system restart krb5-kdc.service

Sergio> which fails because of the problem mentioned above.

So, there was a bug that made its way to the Debian TC asking what the
behavior ought to be when a maintainer script tried to restart a unit
and the unit failed.
The conclusion of that bug was that there is no general
policy--sometimes you want the maintainer script to fail, sometimes you
do not.
At least that was my recollection.

krb5-kdc is a service where you probably don't want the unit
restarting/starting to be a failure to cause the maintainer script to
fail.
How to I explain that to debhelper?

--Sam

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

Title:
  Cannot configure krb5-kdc on Ubuntu Jammy 22.04.01, "Could not execute
  systemctl:  at /usr/bin/deb-systemd-invoke line 142."

Status in init-system-helpers package in Ubuntu:
  New
Status in krb5 package in Ubuntu:
  New

Bug description:
  I have a fresh install of Ubuntu Server 22.04.01 LTS.  After
  installing the server and running all updates, I run the following
  command:

  apt -y install slapd ldap-utils schema2ldif sasl2-bin
  libsasl2-modules-gssapi-mit krb5-kdc-ldap krb5-admin-server krb5-kdc

  This will be installing krb5-kdc 1.19.2-2.

  This is in preparation for setting up an OpenLDAP server, a Kerberos
  server with an LDAP backend, and saslauthd for pass-through
  authentication.  krb5-kdc was auto-selected when running the steps in
  the guide here in my development environment:
  https://ubuntu.com/server/docs/service-kerberos-with-openldap-backend
  When installing that, I get the following in the output:

  Setting up krb5-kdc (1.19.2-2) ...
  Created symlink /etc/systemd/system/multi-user.target.wants/krb5-kdc.service 
→ /lib/systemd/system/krb5-kdc.service.
  Could not execute systemctl:  at /usr/bin/deb-systemd-invoke line 142.

  I do get the prompts for the realm, kdc, and admin server hostnames,
  and they are reflected in /etc/krb5.conf.  If I then run the
  following:

  dpkg-reconfigure krb5-kdc

  I am prompted for whether I want the package to create the Kerberos
  KDC configuration automatically, and when I say yes, it then repeats
  the following error:

  Could not execute systemctl:  at /usr/bin/deb-systemd-invoke line 142.

  I cannot find any further debug in the syslog or anything to indicate
  what the root cause is; the list of packages here are all installed
  together on a separate development server where I experimented with
  the configuration I will be deploying here in production so I don't
  think it's incompatible packages in the install list, but I am open to
  feedback on that.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/init-system-helpers/+bug/2003756/+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 2003756] Re: Cannot configure krb5-kdc on Ubuntu Jammy 22.04.01, "Could not execute systemctl: at /usr/bin/deb-systemd-invoke line 142."

[Sergio Durigan Junior]

FWIW, because Focal's deb-systemd-invoke doesn't use --quiet we end up
getting a clearer error there:

# dpkg-reconfigure krb5-kdc 

Job for krb5-kdc.service failed because the control process exited with error 
code.   
See "systemctl status krb5-kdc.service" and "journalctl -xe" for details.
invoke-rc.d: initscript krb5-kdc, action "start" failed.
● krb5-kdc.service - Kerberos 5 Key Distribution Center
 Loaded: loaded (/lib/systemd/system/krb5-kdc.service; enabled; vendor 
preset: enabled)
 Active: failed (Result: exit-code) since Thu 2023-02-02 18:32:34 UTC; 7ms 
ago
Process: 2000 ExecStart=/usr/sbin/krb5kdc -P /var/run/krb5-kdc.pid 
$DAEMON_ARGS (code=exited, status=1/FAILURE)
CPU: 10ms

Feb 02 18:32:34 bla systemd[1]: Starting Kerberos 5 Key Distribution Center...
Feb 02 18:32:34 bla krb5kdc[2000]: Cannot open DB2 database 
'/var/lib/krb5kdc/principal': No such file or directory - while initializing 
database for realm LXD
Feb 02 18:32:34 bla krb5kdc[2000]: krb5kdc: cannot initialize realm LXD - see 
log file for details
Feb 02 18:32:34 bla systemd[1]: krb5-kdc.service: Control process exited, 
code=exited, status=1/FAILURE
Feb 02 18:32:34 bla systemd[1]: krb5-kdc.service: Failed with result 
'exit-code'.
Feb 02 18:32:34 bla systemd[1]: Failed to start Kerberos 5 Key Distribution 
Center.

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

Title:
  Cannot configure krb5-kdc on Ubuntu Jammy 22.04.01, "Could not execute
  systemctl:  at /usr/bin/deb-systemd-invoke line 142."

Status in init-system-helpers package in Ubuntu:
  New
Status in krb5 package in Ubuntu:
  New

Bug description:
  I have a fresh install of Ubuntu Server 22.04.01 LTS.  After
  installing the server and running all updates, I run the following
  command:

  apt -y install slapd ldap-utils schema2ldif sasl2-bin
  libsasl2-modules-gssapi-mit krb5-kdc-ldap krb5-admin-server krb5-kdc

  This will be installing krb5-kdc 1.19.2-2.

  This is in preparation for setting up an OpenLDAP server, a Kerberos
  server with an LDAP backend, and saslauthd for pass-through
  authentication.  krb5-kdc was auto-selected when running the steps in
  the guide here in my development environment:
  https://ubuntu.com/server/docs/service-kerberos-with-openldap-backend
  When installing that, I get the following in the output:

  Setting up krb5-kdc (1.19.2-2) ...
  Created symlink /etc/systemd/system/multi-user.target.wants/krb5-kdc.service 
→ /lib/systemd/system/krb5-kdc.service.
  Could not execute systemctl:  at /usr/bin/deb-systemd-invoke line 142.

  I do get the prompts for the realm, kdc, and admin server hostnames,
  and they are reflected in /etc/krb5.conf.  If I then run the
  following:

  dpkg-reconfigure krb5-kdc

  I am prompted for whether I want the package to create the Kerberos
  KDC configuration automatically, and when I say yes, it then repeats
  the following error:

  Could not execute systemctl:  at /usr/bin/deb-systemd-invoke line 142.

  I cannot find any further debug in the syslog or anything to indicate
  what the root cause is; the list of packages here are all installed
  together on a separate development server where I experimented with
  the configuration I will be deploying here in production so I don't
  think it's incompatible packages in the install list, but I am open to
  feedback on that.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/init-system-helpers/+bug/2003756/+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 2004592] [NEW] aalogparse.h cannot be included from C++ code

[Steve Langasek]

Public bug reported:

aalogparse.h cannot be included from C++ code because it uses
'namespace' and 'class' as variable names, and these are reserved
keywords in C++.

/usr/include/aalogparse/aalogparse.h:137:15: error: expected unqualified-id 
before ‘namespace’
  137 | char *namespace;
  |   ^
/usr/include/aalogparse/aalogparse.h:163:15: error: expected unqualified-id 
before ‘class’
  163 | char *class;
  |   ^

This is interesting to me because abi-compliance-checker necessarily
processes all headers as C++; but it's likely of general interest to be
able to link C++ code to libapparmor.

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

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

Title:
  aalogparse.h cannot be included from C++ code

Status in apparmor package in Ubuntu:
  New

Bug description:
  aalogparse.h cannot be included from C++ code because it uses
  'namespace' and 'class' as variable names, and these are reserved
  keywords in C++.

  /usr/include/aalogparse/aalogparse.h:137:15: error: expected unqualified-id 
before ‘namespace’
137 | char *namespace;
|   ^
  /usr/include/aalogparse/aalogparse.h:163:15: error: expected unqualified-id 
before ‘class’
163 | char *class;
|   ^

  This is interesting to me because abi-compliance-checker necessarily
  processes all headers as C++; but it's likely of general interest to
  be able to link C++ code to libapparmor.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/apparmor/+bug/2004592/+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 2003756] Re: Cannot configure krb5-kdc on Ubuntu Jammy 22.04.01, "Could not execute systemctl: at /usr/bin/deb-systemd-invoke line 142."

[Sergio Durigan Junior]

I did a little debugging, and the problem happens because
krb5-kdc.service fails to start with:

Feb 02 15:22:34 krb5-test systemd[1]: Starting Kerberos 5 Key Distribution 
Center...
Feb 02 15:22:34 krb5-test krb5kdc[3957]: Cannot open DB2 database 
'/var/lib/krb5kdc/principal': No such file or directory - while initializing 
database for realm LXD
Feb 02 15:22:34 krb5-test krb5kdc[3957]: krb5kdc: cannot initialize realm LXD - 
see log file for details
Feb 02 15:22:34 krb5-test systemd[1]: krb5-kdc.service: Control process exited, 
code=exited, status=1/FAILURE
Feb 02 15:22:34 krb5-test systemd[1]: krb5-kdc.service: Failed with result 
'exit-code'.
Feb 02 15:22:34 krb5-test systemd[1]: Failed to start Kerberos 5 Key 
Distribution Center.

systemd-invoke will try to run systemctl like this:

systemctl --quiet --system restart krb5-kdc.service

which fails because of the problem mentioned above.

I don't think this is a problem with init-system-helpers, but rather an
issue with krb5-kdc indeed.  Also, I believe it's worth reporting this
bug to Debian, since they suffer from it too.

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

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

Title:
  Cannot configure krb5-kdc on Ubuntu Jammy 22.04.01, "Could not execute
  systemctl:  at /usr/bin/deb-systemd-invoke line 142."

Status in init-system-helpers package in Ubuntu:
  New
Status in krb5 package in Ubuntu:
  New

Bug description:
  I have a fresh install of Ubuntu Server 22.04.01 LTS.  After
  installing the server and running all updates, I run the following
  command:

  apt -y install slapd ldap-utils schema2ldif sasl2-bin
  libsasl2-modules-gssapi-mit krb5-kdc-ldap krb5-admin-server krb5-kdc

  This will be installing krb5-kdc 1.19.2-2.

  This is in preparation for setting up an OpenLDAP server, a Kerberos
  server with an LDAP backend, and saslauthd for pass-through
  authentication.  krb5-kdc was auto-selected when running the steps in
  the guide here in my development environment:
  https://ubuntu.com/server/docs/service-kerberos-with-openldap-backend
  When installing that, I get the following in the output:

  Setting up krb5-kdc (1.19.2-2) ...
  Created symlink /etc/systemd/system/multi-user.target.wants/krb5-kdc.service 
→ /lib/systemd/system/krb5-kdc.service.
  Could not execute systemctl:  at /usr/bin/deb-systemd-invoke line 142.

  I do get the prompts for the realm, kdc, and admin server hostnames,
  and they are reflected in /etc/krb5.conf.  If I then run the
  following:

  dpkg-reconfigure krb5-kdc

  I am prompted for whether I want the package to create the Kerberos
  KDC configuration automatically, and when I say yes, it then repeats
  the following error:

  Could not execute systemctl:  at /usr/bin/deb-systemd-invoke line 142.

  I cannot find any further debug in the syslog or anything to indicate
  what the root cause is; the list of packages here are all installed
  together on a separate development server where I experimented with
  the configuration I will be deploying here in production so I don't
  think it's incompatible packages in the install list, but I am open to
  feedback on that.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/init-system-helpers/+bug/2003756/+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 1989959] Re: Incorrect ESM coverage information

[Lech Sandecki]

@vofka this is because of the launch of Ubuntu Pro, which finally brings
coverage for the Universe repo https://ubuntu.com/pro

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

Title:
  Incorrect ESM coverage information

Status in software-properties package in Ubuntu:
  Triaged

Bug description:
  Software Properties says that Extended Security Maintenance provides
  security updates for over 3 Ubuntu packages, see lines 1269 and
  1346 in data/gtkbuilder/main.ui.

  According to https://ubuntu.com/16-04, Canonical provides extended
  security maintenance for binary packages that reside in the "main"
  Ubuntu repository, which contains about 7000 architecture-specific
  packages depending on the Ubuntu release. Moreover, ESM is only
  provided for a part of packages, not for all packages in the "main"
  repository.

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


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

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

[Tuetuopay]

Sure! Here is a quick test using a veth pair and dnsmasq:

ip link add veth0 up type veth peer name veth1
ip addr add 172.20.0.1/24 dev veth0
cat > /etc/netplan/60-veth1.yaml 

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

[fabio andres pino gutierrez]

My error is quite annoying to, already the hotspot work on the SO, the
activated the wifi and detect the wifi, but when my cellphone connected
to the hotspot assigned a public ip, for been exactly assigned by
default the DHCP the ip 10.42.0.189 with a mask subred 255.255.255.0,
but the computer than is working like service DHCP already had
192.168.1.56, i'm undestand if this hotspot is working like a bridge
appliance, but, this time didnt is the case, because the default router
has the 192.168.1.254, so the subred mask of the segment of the red is
from 192.168.1.0 - 192.168.1.255 wtf, why assign me a public IP,
jajajaj, i will send the evidence.

** Attachment added: "hotspot problem2.png"
   
https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1971538/+attachment/5644473/+files/hotspot%20problem2.png

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

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

Status in network-manager package in Ubuntu:
  Confirmed

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

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

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

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


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

[Touch-packages] [Bug 2004578] [NEW] Missing Telia Root CA v2

[micke]

Public bug reported:

$ lsb_release -rd
Description:Ubuntu 22.04.1 LTS
Release:22.04

$ apt-cache policy ca-certificates
ca-certificates:
  Installed: 20211016ubuntu0.22.04.1
  Candidate: 20211016ubuntu0.22.04.1


Missing new Telia Root CA v2

$ apt-file search Telia
ca-certificates: /usr/share/ca-certificates/mozilla/TeliaSonera_Root_CA_v1.crt

$ dpkg -L ca-certificates | grep -i telia
/usr/share/ca-certificates/mozilla/TeliaSonera_Root_CA_v1.crt

https://cps.trust.telia.com/

https://support.trust.telia.com/sslhelp_en.html
"""
Telia is moving to new Telia Root CA v2 root certificate. Mentioned certificate 
is not yet included in all operating systems and browsers. Thus it is not used 
for certificate issuance at the moment. During transition period a three-tier 
hierarchy will be used.
"""

** Affects: ca-certificates (Ubuntu)
 Importance: Undecided
 Status: New

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

Title:
  Missing Telia Root CA v2

Status in ca-certificates package in Ubuntu:
  New

Bug description:
  $ lsb_release -rd
  Description:Ubuntu 22.04.1 LTS
  Release:22.04

  $ apt-cache policy ca-certificates
  ca-certificates:
Installed: 20211016ubuntu0.22.04.1
Candidate: 20211016ubuntu0.22.04.1

  
  Missing new Telia Root CA v2

  $ apt-file search Telia
  ca-certificates: /usr/share/ca-certificates/mozilla/TeliaSonera_Root_CA_v1.crt

  $ dpkg -L ca-certificates | grep -i telia
  /usr/share/ca-certificates/mozilla/TeliaSonera_Root_CA_v1.crt

  https://cps.trust.telia.com/

  https://support.trust.telia.com/sslhelp_en.html
  """
  Telia is moving to new Telia Root CA v2 root certificate. Mentioned 
certificate is not yet included in all operating systems and browsers. Thus it 
is not used for certificate issuance at the moment. During transition period a 
three-tier hierarchy will be used.
  """

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/ca-certificates/+bug/2004578/+subscriptions


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

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

[Nick Rosbrook]

I haven't tested to confirm the broken behavior on jammy, but the patch
looks straight forward. To help the process along, could you try to
provide some simple steps to reproduce the bug on jammy?

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

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

Status in systemd package in Ubuntu:
  New

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

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

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

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

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

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

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

  Thanks.

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


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

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

[Nick Rosbrook]

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

** Changed in: systemd (Ubuntu Focal)
   Importance: Undecided => Low

** Changed in: systemd (Ubuntu)
   Status: New => Fix Released

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

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

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

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

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

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

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

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

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


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

[Touch-packages] [Bug 2003098] Re: whoopsie-upload-all: package specific hooks not run

[Benjamin Drung]

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

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

Title:
  whoopsie-upload-all: package specific hooks not run

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

Bug description:
  Commit f8edc7280d492e710218c193e53542f1f86cfa91 (for fixing bug
  #1983481) introduces a regression: The package specific hooks are not
  run in whoopsie-upload-all because add_hooks_info is called with
  ui=None. add_hooks_info will raise an AssertionError for ui=None.

To manage notifications about this bug go to:
https://bugs.launchpad.net/apport/+bug/2003098/+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 2004035] Re: package openssh-server 1:8.9p1-3ubuntu0.1 failed to install/upgrade: installed openssh-server package post-installation script subprocess returned error exit status

[Sergio Durigan Junior]

Thank you for taking the time to file a bug report.

According to the logs you posted:

Setting up openssh-server (1:8.9p1-3ubuntu0.1) ...
Not replacing deleted config file /etc/ssh/sshd_config
dpkg: error processing package openssh-server (--configure):
 installed openssh-server package post-installation script subprocess returned 
error exit status 1

This problem usually happens when you remove a package using "apt-get
remove", and then manually remove its configuration files.  If you would
like to remove a package *and* its configuration files, you should
normally use "apt-get purge".  When dpkg detects that openssh's config
files have been manually removed, it decides not to reinstall them.

Since it seems likely to me that this is a local configuration problem,
rather than a bug in Ubuntu, I am marking this bug as 'Incomplete'.

However, if you believe that this is really a bug in Ubuntu, then we would
be grateful if you would provide a more complete description of the problem
with steps to reproduce, explain why you believe this is a bug in Ubuntu
rather than a problem specific to your system, and then change the bug
status back to "New".

For local configuration issues, you can find assistance here:
http://www.ubuntu.com/support/community

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

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

Title:
  package openssh-server 1:8.9p1-3ubuntu0.1 failed to install/upgrade:
  installed openssh-server package post-installation script subprocess
  returned error exit status 1

Status in openssh package in Ubuntu:
  Incomplete

Bug description:
  The following NEW packages will be installed:
ncurses-term openssh-server openssh-sftp-server ssh-import-id
  0 upgraded, 4 newly installed, 0 to remove and 0 not upgraded.
  Need to get 750 kB of archives.
  After this operation, 6,046 kB of additional disk space will be used.
  Do you want to continue? [Y/n] y
  Get:1 http://us.archive.ubuntu.com/ubuntu jammy-updates/main amd64 
openssh-sftp-server amd64 1:8.9p1-3ubuntu0.1 [38.7 kB]
  Get:2 http://us.archive.ubuntu.com/ubuntu jammy-updates/main amd64 
openssh-server amd64 1:8.9p1-3ubuntu0.1 [434 kB]
  Get:3 http://us.archive.ubuntu.com/ubuntu jammy/main amd64 ncurses-term all 
6.3-2 [267 kB]
  Get:4 http://us.archive.ubuntu.com/ubuntu jammy/main amd64 ssh-import-id all 
5.11-0ubuntu1 [10.1 kB]
  Fetched 750 kB in 0s (2,652 kB/s) 
  Preconfiguring packages ...
  Selecting previously unselected package openssh-sftp-server.
  (Reading database ... 143729 files and directories currently installed.)
  Preparing to unpack .../openssh-sftp-server_1%3a8.9p1-3ubuntu0.1_amd64.deb ...
  Unpacking openssh-sftp-server (1:8.9p1-3ubuntu0.1) ...
  Selecting previously unselected package openssh-server.
  Preparing to unpack .../openssh-server_1%3a8.9p1-3ubuntu0.1_amd64.deb ...
  Unpacking openssh-server (1:8.9p1-3ubuntu0.1) ...
  Selecting previously unselected package ncurses-term.
  Preparing to unpack .../ncurses-term_6.3-2_all.deb ...
  Unpacking ncurses-term (6.3-2) ...
  Selecting previously unselected package ssh-import-id.
  Preparing to unpack .../ssh-import-id_5.11-0ubuntu1_all.deb ...
  Unpacking ssh-import-id (5.11-0ubuntu1) ...
  Setting up openssh-sftp-server (1:8.9p1-3ubuntu0.1) ...
  Setting up openssh-server (1:8.9p1-3ubuntu0.1) ...
  Not replacing deleted config file /etc/ssh/sshd_config
  dpkg: error processing package openssh-server (--configure):
   installed openssh-server package post-installation script subprocess 
returned error exit status 1
  Setting up ssh-import-id (5.11-0ubuntu1) ...
  Setting up ncurses-term (6.3-2) ...
  Processing triggers for man-db (2.10.2-1) ...
  Processing triggers for ufw (0.36.1-4build1) ...
  Errors were encountered while processing:
   openssh-server

  ProblemType: Package
  DistroRelease: Ubuntu 22.04
  Package: openssh-server 1:8.9p1-3ubuntu0.1
  ProcVersionSignature: Ubuntu 5.15.0-58.64-generic 5.15.74
  Uname: Linux 5.15.0-58-generic x86_64
  ApportVersion: 2.20.11-0ubuntu82.3
  AptOrdering:
   openssh-sftp-server:amd64: Install
   openssh-server:amd64: Install
   ncurses-term:amd64: Install
   ssh-import-id:amd64: Install
   NULL: ConfigurePending
  Architecture: amd64
  CasperMD5CheckResult: unknown
  Date: Fri Jan 27 08:22:28 2023
  DuplicateSignature:
   package:openssh-server:1:8.9p1-3ubuntu0.1
   Setting up openssh-server (1:8.9p1-3ubuntu0.1) ...
   Not replacing deleted config file /etc/ssh/sshd_config
   dpkg: error processing package openssh-server (--configure):
installed openssh-server package post-installation script subprocess 
returned error exit status 1
  ErrorMessage: installed openssh-server package post-installation script 
subprocess returned error exit status 1
  InstallationDate: Installed on 2022-01-20 (371 days ago)
  InstallationMedia: 

[Touch-packages] [Bug 1937110] Re: dhcp option 121 & 249

[Steve Langasek]

There is no reason to expect this to be fixed in the daily jammy image.

Progress on fixing this was blocked for months for lack of a test case.

A prospective fix has been uploaded to the queue.  Daily server images
won't include the fix until it has been reviewed by the SRU team,
accepted into the -proposed pocket, tested, and promoted to the -updates
pocket.

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

Title:
  dhcp option 121 & 249

Status in subiquity:
  New
Status in isc-dhcp package in Ubuntu:
  Fix Released
Status in isc-dhcp source package in Focal:
  In Progress
Status in isc-dhcp source package in Jammy:
  In Progress

Bug description:
  [Impact]

   * DHCP classless static routes aren't applied
 by dhclient at the initramfs (e.g., ip=dhcp).

   * This happens as rfc3442-classless-routes is
 not copied to /etc/dhcp/dhclient-exit-hooks.d/
 in the initramfs.

   * On Jammy, if such DHCP option(s) are present
 in the DHCP server response, the DHCP client
 ignores the 'routers' option from the server,
 thus leaving no routes configured.

   * On Focal, the older code still adds 'routers',
 which is slightly better, but still does not
 add the classless static routes.

  [Test Plan]

   * Use LXD container/VMs for DHCP server/client,
 configure the DHCP server with option 121,
 and some sample classless static routes.
 (see comments #12/jammy and #13/focal).

  [Regression Potential]

   * Acquisition of DHCP leases/routes at initramfs
 with ip=dhcp.

   * The code/script is not new, and is exercised
 normally during on rootfs (ie, post-initramfs)
 when dhclient is run.

   * It's also been in the initramfs in Kinetic
 already, since on Aug 2022; giving it tests.

  [Original Description]
  Hello,

  I'm running into issues with subiquity on a cloud provider.  The cloud
  provider is using an on-link L3 gateway.

  His DHCP response looks like this:

  OPTION:  53 (  1) DHCP message type 5 (DHCPACK)
  OPTION:  54 (  4) Server identifier 172.31.1.1
  OPTION:  51 (  4) IP address leasetime  86400 (24h)
  OPTION:   1 (  4) Subnet mask   255.255.255.255
  OPTION:   3 (  4) Routers   172.31.1.1
  OPTION:   6 ( 12) DNS server
  OPTION: 121 ( 14) Classless Static Route20ac1f010100  ...
   ac1f0101 ..
  OPTION: 249 ( 14) MSFT - Classless route20ac1f010100  ...
   ac1f0101 ..

  Im booting the subiquity process with an patched ipxe
  (https://github.com/ipxe/ipxe/pull/104) like this:

  #!ipxe
  kernel .../vmlinuz initrd=initrd root=/dev/ram0 ramdisk_size=150 ip=dhcp 
url=https://cdimage.ubuntu.com/ubuntu-server/focal/daily-live/current/focal-live-server-amd64.iso
 autoinstall ds=nocloud-net;s=.../...-ad-78/ cloud-config-url=/dev/null
  initrd .../initrd
  boot

  initrd/vmlinuz is extracted right out of focal-live-server-amd64.iso

  Sadly subiquity is stuck with a broken network (because of missing
  dhcp option 121/249 support). It happens when its running the /init
  from the kernel right after kernel is booted, i guess even before the
  subiquity is started(?).

  After further debugging, it looks like the provided kernel 5.4.80 #90
  Ubuntu, is using busybox 1.30.1-4ubuntu~6.3 which includes isc-
  dhclient-4.4.1 which is lacking the given options.

  Would be awesome if this could be fixed.. maybe just a simple busybox
  compile option?

To manage notifications about this bug go to:
https://bugs.launchpad.net/subiquity/+bug/1937110/+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 1728130] Re: Policy needs improved feature versioning to ensure it is correctly being applied

[Heather Lemon]

Great! Thank you Georgia.

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

Title:
  Policy needs improved feature versioning to ensure it is correctly
  being applied

Status in apparmor package in Ubuntu:
  Confirmed
Status in apparmor source package in Focal:
  Fix Committed

Bug description:
  [ Impact ]

  Currently allows pinning a single feature abi or running in a
  developer mode where the full abi available of the current kernel is
  enforced.

  However this can result in breaking applications in undesirable ways.

  If an application is shipped with its own policy, that policy might be
  different than the pinned feature abi, which can either result in
  denials because features the policy was not developed for are being
  enforced.

  If the feature version is not pinned then the most recent kernel abi
  is taken and applied to policy, which has not been updated. This can
  result in denials for userspace effectively breaking userspace. This
  is less than ideal for most users as it leads to a bad experience than
  they have not opted into and can lead to them disabling security
  protections.

  [ Test Plan ]

  The test can be done with several features. Here we are using mqueue as an 
example.
  Verify that the kernel that has mqueue mediation support:
  root@ubuntu:~# [ -e /sys/kernel/security/apparmor/features/ipc/posix_mqueue ] 
&& echo "supports mqueue"
  supports mqueue

  cd /tmp
  pull-ppa-source --ppa georgiag/mqueue-sru apparmor focal
  cd apparmor-2.13.3/tests/regression/apparmor/
  USE_SYSTEM=1 make

  Using the parser from the mqueue-sru PPA, load the profile.
  echo "
  abi ,
  include 
  /tmp/apparmor-2.13.3/tests/regression/apparmor/posix_mq_rcv {
include 
/tmp/apparmor-2.13.3/tests/regression/apparmor/posix_mq_snd ux,
  }
  " | apparmor_parser -q -r

  Run the test, which should fail.
  ./posix_mq_rcv -c ./posix_mq_snd
  FAIL - could not open mq: Permission denied

  Now use an abi that does not have mqueue. This simulates a scenario
  where a policy was developed before mqueue support was added, so posix
  message queues should be allowed by default.

  echo "
  abi ,
  include 
  /tmp/apparmor-2.13.3/tests/regression/apparmor/posix_mq_rcv {
include 
/tmp/apparmor-2.13.3/tests/regression/apparmor/posix_mq_snd ux,
  }
  " | apparmor_parser -q -r

  Run the test again, it should pass.
  ./posix_mq_rcv -c ./posix_mq_snd
  PASS

  [ Where problems could occur ]

  ABI pinning forces policies that don't have abi specified in their
  profile to use the ABI pinned in parser.conf. When the ABI is pinned
  and the user is trying to use mediation that is not in the pinned ABI,
  they might be confused why it is always being allowed. This can be
  circumvented by specifying the correct abi in the profile.

  [ Other Info ]

  The patches for focal (apparmor-2.13) can be found at:
  https://launchpad.net/~georgiag/+archive/ubuntu/mqueue-sru/
  apparmor-3.0 already has this feature.

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


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

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

[Launchpad Bug Tracker]

This bug was fixed in the package duecredit - 0.9.1-1ubuntu1

---
duecredit (0.9.1-1ubuntu1) lunar; urgency=medium

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

 -- Benjamin Drung   Wed, 01 Feb 2023 11:45:02 +0100

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

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

Title:
  Invalid PEP440 package version breaking setuptools >= 60

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

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

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

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

  suffix 1build1 is invalid.

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

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

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


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

[Touch-packages] [Bug 1926139] Re: dhclient: thread concurrency race leads to DHCPOFFER packets not being received

[Mauricio Faria de Oliveira]

** Tags added: se-sru-sponsor-mfo

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

Title:
  dhclient: thread concurrency race leads to DHCPOFFER packets not being
  received

Status in bind9-libs package in Ubuntu:
  Won't Fix
Status in isc-dhcp package in Ubuntu:
  Invalid
Status in isc-dhcp source package in Focal:
  In Progress
Status in isc-dhcp source package in Jammy:
  In Progress

Bug description:
  [Impact]

   * Occasionally, during instance boot or machine start-up,
 dhclient will attempt to acquire a dhcp lease and fail,
 leaving the instance with no IP address and making it
 unreachable.

   * This happens about once every 100 reboots on bare metal,
 or affecting between ~0.3% to 2% of deployments on Azure
 (comment #2).
 
   * Azure uses dhclient called from cloud-init instead of
 systemd-networkd, and this is causing issues with larger
 deployments.

   * The logs of an affected dhclient produce the following:

 Listening on LPF/enp1s0/52:54:00:1c:d7:00
 Sending on   LPF/enp1s0/52:54:00:1c:d7:00
 Sending on   Socket/fallback
 DHCPDISCOVER on enp1s0 to 255.255.255.255 port 67 ...
 DHCPDISCOVER on enp1s0 to 255.255.255.255 port 67 ...
 ...
 (omitting 20 similar lines)
 ...
 DHCPDISCOVER on enp1s0 to 255.255.255.255 port 67 ...
 DHCPDISCOVER on enp1s0 to 255.255.255.255 port 67 ...
 DHCPDISCOVER on enp1s0 to 255.255.255.255 port 67 ...
 No DHCPOFFERS received.
 No working leases in persistent database - sleeping.

   * This only impacts Focal and Jammy, where bind9-libs
 are multi-threaded (Bionic/earlier and Kinetic/later
 are single-threaded).

   * The actual problem is dhclient containing a thread
 concurrency race condition, and when the race occurs,
 the read socket is incorrectly/prematurely unwatched
 because required structures are not yet consistent,
 thus dhclient does not read any DHCPOFFER replies.

   * Detailed analysis of the issue is in comment #17.

  [Fix]

   * Prevent the race condition by starting to watch the
 read socket after required structures are consistent.
   
   * The fix has been tested in Azure w/ 13500 instances,
 and no errors have been observed (previously: 0.4%).
 
   * Anyway, in case regressions are observed, the patch
 introduces 2 switches to revert to previous behavior,
 which can be applied per-process or system-wide:
 - DHCP_FD_FLAGS_POKE=0 environment variable
 - dhcp.fd_flags_poke=0 kernel cmdline option 
   
   * (Previous approaches/discussions included reverting
  bind9-libs to single-threaded, but we concluded it
  would have more regression risk than the expected
  [some bits in comment #8, and some internal chat],
  and remove exported symbols (apparently unused, but).
  We also considered a mutex/spinlock approach, but
  later found a simpler way w/ isc lib; comment #13.)
  
  [Test Plan]

   * Synthetic reproducer with GDB to force the race
 condition, and DHCP server/client/noise injection
 is described in comment #9.
   
   * Test with the original package (problem occurs).
   
   * Test with the modified package (problem fixed).
 - Set DHCP_FD_FLAGS_POKE=0 (problem occurs).
 - Set dhcp.fd_flags_poke=0 (problem occurs).

  [Regression Potential]

   * 1) dhclient failing to acquire DHCP leases.
  
   * 2) dhcpd is also affected by code changes,
 thus failures to handle DHCP lease requests
 also have potential for regressions.
 
   * 3) the functional change added by the fix,
 if a regression were to occur, would likely
 be an issue only under some (unknown) race
 condition as well, thus expected to be rare.

   * Note: this potentially affects Focal/Jammy 
 on Azure as a whole, per usage of dhclient
 in cloud-init instead of systemd-networkd.
 
 Azure provided extensive testing for all 3
 approaches (mostly internal communications,
 and some bug comments), with ~13k instances.
 
 No issues were observed (previously: 0.4%).
 
   * Such testing scale seems to indicate that
 there are no regressions for dhclient to
 acquire DHCP leases (1), nor another race
 condition that hit the fix/new behavior (3).
 
 With that, apparently (2) should be OK too.
 
   * Also, so to mitigate the regression risk
 as much as possible, there's very detailed
 analysis provided here (comments #17, #18)
 and more information about the fix in its
 patch file's comment.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/bind9-libs/+bug/1926139/+subscriptions


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

[Touch-packages] [Bug 2004560] [NEW] smbk5pwd test fails due to perms (FS and AppArmor)

[Andreas Hasenack]

Public bug reported:

https://autopkgtest.ubuntu.com/packages/o/openldap/lunar/amd64

autopkgtest [16:06:32]: test smbk5pwd: [---
adding new entry "cn=samba,cn=schema,cn=config"

SASL/EXTERNAL authentication started
SASL username: gidNumber=0+uidNumber=0,cn=peercred,cn=external,cn=auth
SASL SSF: 0
SASL/EXTERNAL authentication started
SASL username: gidNumber=0+uidNumber=0,cn=peercred,cn=external,cn=auth
SASL SSF: 0
adding new entry "cn=hdb,cn=schema,cn=config"

SASL/EXTERNAL authentication started
SASL username: gidNumber=0+uidNumber=0,cn=peercred,cn=external,cn=auth
SASL SSF: 0
modifying entry "cn=module{0},cn=config"

adding new entry "olcOverlay=smbk5pwd,olcDatabase={1}mdb,cn=config"

ldap_add: Other (e.g., implementation specific) error (80)
additional info:  handler exited with 1
autopkgtest [16:06:33]: test smbk5pwd: ---]
autopkgtest [16:06:33]: test smbk5pwd:  - - - - - - - - - - results - - - - - - 
- - - -
smbk5pwd FAIL non-zero exit status 80

I reproduced this in a container, and the failure is two-fold:

a) /var/lib/heimdal-kdc/ is root:root 0700, and the slapd server needs
FS read access to the key

b) Then the slapd apparmor profile blocks it:
[qui fev  2 09:54:02 2023] audit: type=1400 audit(1675342444.436:3242): 
apparmor="DENIED" operation="open" class="file" 
namespace="root//lxd-l-dep8_" 
profile="/usr/sbin/slapd" name="/var/lib/heimdal-kdc/m-key" pid=1161656 
comm="slapd" requested_mask="r" denied_mask="r" fsuid=1000110 ouid=100

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


** Tags: update-excuse

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

Title:
  smbk5pwd test fails due to perms (FS and AppArmor)

Status in openldap package in Ubuntu:
  New

Bug description:
  https://autopkgtest.ubuntu.com/packages/o/openldap/lunar/amd64

  autopkgtest [16:06:32]: test smbk5pwd: [---
  adding new entry "cn=samba,cn=schema,cn=config"

  SASL/EXTERNAL authentication started
  SASL username: gidNumber=0+uidNumber=0,cn=peercred,cn=external,cn=auth
  SASL SSF: 0
  SASL/EXTERNAL authentication started
  SASL username: gidNumber=0+uidNumber=0,cn=peercred,cn=external,cn=auth
  SASL SSF: 0
  adding new entry "cn=hdb,cn=schema,cn=config"

  SASL/EXTERNAL authentication started
  SASL username: gidNumber=0+uidNumber=0,cn=peercred,cn=external,cn=auth
  SASL SSF: 0
  modifying entry "cn=module{0},cn=config"

  adding new entry "olcOverlay=smbk5pwd,olcDatabase={1}mdb,cn=config"

  ldap_add: Other (e.g., implementation specific) error (80)
additional info:  handler exited with 1
  autopkgtest [16:06:33]: test smbk5pwd: ---]
  autopkgtest [16:06:33]: test smbk5pwd:  - - - - - - - - - - results - - - - - 
- - - - -
  smbk5pwd FAIL non-zero exit status 80

  I reproduced this in a container, and the failure is two-fold:

  a) /var/lib/heimdal-kdc/ is root:root 0700, and the slapd server needs
  FS read access to the key

  b) Then the slapd apparmor profile blocks it:
  [qui fev  2 09:54:02 2023] audit: type=1400 audit(1675342444.436:3242): 
apparmor="DENIED" operation="open" class="file" 
namespace="root//lxd-l-dep8_" 
profile="/usr/sbin/slapd" name="/var/lib/heimdal-kdc/m-key" pid=1161656 
comm="slapd" requested_mask="r" denied_mask="r" fsuid=1000110 ouid=100

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


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

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

[Andreas Hasenack]

** Changed in: openldap (Ubuntu)
   Status: Triaged => In Progress

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

Title:
  Wrong SHA256-value computed on kinetic

Status in openldap package in Ubuntu:
  In Progress

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

  
  The problematic computation:

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

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

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

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

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


  
  Ubuntu:

  Description:Ubuntu 22.10
  Release:22.10

  OpenLDAP-Package: 2.5.13+dfsg-1ubuntu1

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


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

[Touch-packages] [Bug 1842439] Re: apport-gtk crashed with SIGSEGV in _gtk_settings_get_screen(settings=0x0) from gtk_css_value_icon_theme_compute() from gtk_css_static_style_compute_value()

[Sebastien Bacher]

@Andrzej, right, but the issue is that your session is closing and
that's a probably in a key component as the shell, session manager and
graphical server. Resolving the fact that 'ubuntu-bug', the bug report
helper is being hit by the session closing would not solve your issue.
You should for other .crash reports on your system and probably submit
those

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

Title:
  apport-gtk crashed with SIGSEGV in
  _gtk_settings_get_screen(settings=0x0) from
  gtk_css_value_icon_theme_compute() from
  gtk_css_static_style_compute_value()

Status in apport package in Ubuntu:
  Invalid
Status in gtk+3.0 package in Ubuntu:
  Triaged
Status in apport source package in Focal:
  Invalid
Status in gtk+3.0 source package in Focal:
  Triaged
Status in apport source package in Lunar:
  Invalid
Status in gtk+3.0 source package in Lunar:
  Triaged

Bug description:
  Steps to reproduce
  --

  1. Use GNOME with GNOME shell
  2. killall -11 gnome-shell

  Suspicious Apport log:

  gdbus call error: Error:
  GDBus.Error:org.freedesktop.DBus.Error.ServiceUnknown: The name
  org.gnome.SessionManager was not provided by any .service files

  Error tracker
  -
  https://errors.ubuntu.com/problem/815a179408135a894bbb5921adef3757563c75c5
  https://errors.ubuntu.com/problem/276759c7bf0b6628977c63ca70d26b53c9defd22

  Stack trace
  ---

  Python:

  ```
File "apport-gtk", line 703, in 
  app = GTKUserInterface(sys.argv)
File "apport-gtk", line 68, in GTKUserInterface.__init__
  self.widgets.add_from_file(
  os.path.join(os.path.dirname(argv[0]), "apport-gtk.ui")
  )
  ```

  StacktraceTop:
   _gtk_settings_get_screen (settings=0x0) at ../../../../gtk/gtksettings.c:3319
   gtk_css_value_icon_theme_compute (icon_theme=, 
property_id=, provider=, style=, 
parent_style=) at ../../../../gtk/gtkcssiconthemevalue.c:84
   gtk_css_static_style_compute_value (style=0x1e7c320, provider=0x0, 
parent_style=0x0, id=3, specified=0x7f53258b9b20 , section=0x0) at 
../../../../gtk/gtkcssstaticstyle.c:237
   _gtk_css_lookup_resolve (lookup=lookup@entry=0x1e7e790, 
provider=provider@entry=0x0, style=style@entry=0x1e7c320, 
parent_style=parent_style@entry=0x0) at ../../../../gtk/gtkcsslookup.c:122
   gtk_css_static_style_new_compute (provider=provider@entry=0x0, 
matcher=matcher@entry=0x0, parent=parent@entry=0x0) at 
../../../../gtk/gtkcssstaticstyle.c:195

  Original report
  ---
  Session suddenly stopped and came back to login screen, all opened windows 
lost.

  ProblemType: Crash
  DistroRelease: Ubuntu 19.10
  Package: apport-gtk 2.20.11-0ubuntu7
  ProcVersionSignature: Ubuntu 5.2.0-15.16-generic 5.2.9
  Uname: Linux 5.2.0-15-generic x86_64
  ApportVersion: 2.20.11-0ubuntu7
  Architecture: amd64
  CrashReports:
   640:1000:117:7292709:2019-09-03 16:20:13.909392833 +0200:2019-09-03 
16:20:14.909392833 +0200:/var/crash/_usr_share_apport_apport-gtk.1000.crash
   640:1000:117:48937942:2019-09-03 16:20:11.681426286 +0200:2019-09-03 
16:20:12.681426286 +0200:/var/crash/_usr_bin_gnome-shell.1000.crash
   640:1000:117:32054:2019-08-27 17:39:07.125607490 +0200:2019-08-28 
12:36:17.087672961 +0200:/var/crash/_usr_bin_dbus-daemon.1000.crash
  CurrentDesktop: ubuntu:GNOME
  Date: Tue Sep  3 16:20:13 2019
  ExecutablePath: /usr/share/apport/apport-gtk
  InstallationDate: Installed on 2018-06-16 (443 days ago)
  InstallationMedia: Ubuntu 18.10 "Cosmic Cuttlefish" - Alpha amd64 (20180611)
  InterpreterPath: /usr/bin/python3.7
  PackageArchitecture: all
  ProcCmdline: /usr/bin/python3 /usr/share/apport/apport-gtk
  ProcEnviron:
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=fr_FR.UTF-8
   SHELL=/bin/bash
  Python3Details: /usr/bin/python3.7, Python 3.7.4, python3-minimal, 3.7.3-1
  PythonDetails: /usr/bin/python2.7, Python 2.7.16+, python-minimal, 2.7.16-1
  SegvAnalysis:
   Segfault happened at: 0x7f532548f8c4:mov0x18(%rdi),%rax
   PC (0x7f532548f8c4) ok
   source "0x18(%rdi)" (0x0018) not located in a known VMA region (needed 
readable region)!
   destination "%rax" ok
  SegvReason: reading NULL VMA
  Signal: 11
  SourcePackage: apport
  StacktraceTop:
   ?? () from /usr/lib/x86_64-linux-gnu/libgtk-3.so.0
   ?? () from /usr/lib/x86_64-linux-gnu/libgtk-3.so.0
   ?? () from /usr/lib/x86_64-linux-gnu/libgtk-3.so.0
   ?? () from /usr/lib/x86_64-linux-gnu/libgtk-3.so.0
   ?? () from /usr/lib/x86_64-linux-gnu/libgtk-3.so.0
  Title: apport-gtk crashed with SIGSEGV
  UpgradeStatus: Upgraded to eoan on 2019-06-10 (84 days ago)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
  separator:

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


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

[Touch-packages] [Bug 2004554] Re: While using application switching in multi-tasking

[Daniel van Vugt]

Thanks for the bug report.

I have just tested:

  Settings >
  Multitasking > 
  Application Switching >
  Include applications from the current workspace only

and although I wasn't able to reproduce exactly the same bug, I was able
to reproduce a similar bug in that the dot next to the Files icon
disappeared even on the workspace where the Files window is still open.


** Package changed: xorg (Ubuntu) => gnome-shell-extension-ubuntu-dock (Ubuntu)

** Summary changed:

- While using application switching in multi-tasking
+ Dock shows wrong indicator dots (eventually) when "Include applications from 
the current workspace only" is enabled

** Changed in: gnome-shell-extension-ubuntu-dock (Ubuntu)
   Importance: Undecided => Medium

** Changed in: gnome-shell-extension-ubuntu-dock (Ubuntu)
   Status: New => Triaged

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

Title:
  Dock shows wrong indicator dots (eventually) when "Include
  applications from the current workspace only" is enabled

Status in gnome-shell-extension-ubuntu-dock package in Ubuntu:
  Triaged

Bug description:
  While switching workspace, the option : include applications from
  current workspace only is opted. The files founder does not switch
  properly. If opened in one workspace, and switched to another
  workspace. Then the dot ( that shoes finder is open) does not go away.
  And many more please check.

  ProblemType: Bug
  DistroRelease: Ubuntu 22.04
  Package: xorg 1:7.7+23ubuntu2
  ProcVersionSignature: Ubuntu 5.15.0-58.64-generic 5.15.74
  Uname: Linux 5.15.0-58-generic x86_64
  ApportVersion: 2.20.11-0ubuntu82.3
  Architecture: amd64
  BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
  CasperMD5CheckResult: unknown
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: None
  CurrentDesktop: ubuntu:GNOME
  Date: Thu Feb  2 16:47:24 2023
  DistUpgraded: 2023-01-27 15:07:45,014 DEBUG Running PostInstallScript: 
'/usr/lib/ubuntu-advantage/upgrade_lts_contract.py'
  DistroCodename: jammy
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes
  GraphicsCard:
   Intel Corporation CoffeeLake-H GT2 [UHD Graphics 630] [8086:3e9b] (prog-if 
00 [VGA controller])
 Subsystem: Micro-Star International Co., Ltd. [MSI] CoffeeLake-H GT2 [UHD 
Graphics 630] [1462:12aa]
   NVIDIA Corporation TU106M [GeForce RTX 2060 Mobile] [10de:1f15] (rev a1) 
(prog-if 00 [VGA controller])
 Subsystem: Micro-Star International Co., Ltd. [MSI] TU106M [GeForce RTX 
2060 Mobile] [1462:12aa]
  InstallationDate: Installed on 2021-05-11 (631 days ago)
  InstallationMedia: Ubuntu 20.04.2.0 LTS "Focal Fossa" - Release amd64 
(20210209.1)
  MachineType: Micro-Star International Co., Ltd. GF65 Thin 9SEXR
  ProcEnviron:
   LANGUAGE=en_IN:en
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_IN
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.15.0-58-generic 
root=UUID=f2aafeb8-65f1-4f53-a7f4-a8bac75a5fbd ro quiet splash vt.handoff=7
  SourcePackage: xorg
  Symptom: display
  UpgradeStatus: Upgraded to jammy on 2023-01-27 (6 days ago)
  dmi.bios.date: 10/21/2021
  dmi.bios.release: 1.12
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: E16W1IMS.10C
  dmi.board.asset.tag: Default string
  dmi.board.name: MS-16W1
  dmi.board.vendor: Micro-Star International Co., Ltd.
  dmi.board.version: REV:1.0
  dmi.chassis.asset.tag: Default string
  dmi.chassis.type: 10
  dmi.chassis.vendor: Micro-Star International Co., Ltd.
  dmi.chassis.version: Default string
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrE16W1IMS.10C:bd10/21/2021:br1.12:svnMicro-StarInternationalCo.,Ltd.:pnGF65Thin9SEXR:pvrREV1.0:rvnMicro-StarInternationalCo.,Ltd.:rnMS-16W1:rvrREV1.0:cvnMicro-StarInternationalCo.,Ltd.:ct10:cvrDefaultstring:sku16W1.1:
  dmi.product.family: GF
  dmi.product.name: GF65 Thin 9SEXR
  dmi.product.sku: 16W1.1
  dmi.product.version: REV:1.0
  dmi.sys.vendor: Micro-Star International Co., Ltd.
  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.110-1ubuntu1
  version.libgl1-mesa-dri: libgl1-mesa-dri 22.0.5-0ubuntu0.3
  version.libgl1-mesa-glx: libgl1-mesa-glx N/A
  version.xserver-xorg-core: xserver-xorg-core 2:21.1.3-2ubuntu2.5
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-2ubuntu1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20210115-1
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 
1:1.0.17-2build1

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-shell-extension-ubuntu-dock/+bug/2004554/+subscriptions


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

[Touch-packages] [Bug 1842439] Re: apport-gtk crashed with SIGSEGV in _gtk_settings_get_screen(settings=0x0) from gtk_css_value_icon_theme_compute() from gtk_css_static_style_compute_value()

[Andrzej Doros]

Dear @Sebastien Bacher (seb128)

It isn't true that it isn't 'real world issue' (at least in my case). My Ubuntu 
22.04 is randomly crashing (approximately once per day), all applications are 
closed and systems go to the login screen. During the crash time, I'm losing 
all my work, so it is seriously touching my daily tasks. 
Due to the above, I will be appreciated, if someone will fix the bug.

Best regards,
Andrzej

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

Title:
  apport-gtk crashed with SIGSEGV in
  _gtk_settings_get_screen(settings=0x0) from
  gtk_css_value_icon_theme_compute() from
  gtk_css_static_style_compute_value()

Status in apport package in Ubuntu:
  Invalid
Status in gtk+3.0 package in Ubuntu:
  Triaged
Status in apport source package in Focal:
  Invalid
Status in gtk+3.0 source package in Focal:
  Triaged
Status in apport source package in Lunar:
  Invalid
Status in gtk+3.0 source package in Lunar:
  Triaged

Bug description:
  Steps to reproduce
  --

  1. Use GNOME with GNOME shell
  2. killall -11 gnome-shell

  Suspicious Apport log:

  gdbus call error: Error:
  GDBus.Error:org.freedesktop.DBus.Error.ServiceUnknown: The name
  org.gnome.SessionManager was not provided by any .service files

  Error tracker
  -
  https://errors.ubuntu.com/problem/815a179408135a894bbb5921adef3757563c75c5
  https://errors.ubuntu.com/problem/276759c7bf0b6628977c63ca70d26b53c9defd22

  Stack trace
  ---

  Python:

  ```
File "apport-gtk", line 703, in 
  app = GTKUserInterface(sys.argv)
File "apport-gtk", line 68, in GTKUserInterface.__init__
  self.widgets.add_from_file(
  os.path.join(os.path.dirname(argv[0]), "apport-gtk.ui")
  )
  ```

  StacktraceTop:
   _gtk_settings_get_screen (settings=0x0) at ../../../../gtk/gtksettings.c:3319
   gtk_css_value_icon_theme_compute (icon_theme=, 
property_id=, provider=, style=, 
parent_style=) at ../../../../gtk/gtkcssiconthemevalue.c:84
   gtk_css_static_style_compute_value (style=0x1e7c320, provider=0x0, 
parent_style=0x0, id=3, specified=0x7f53258b9b20 , section=0x0) at 
../../../../gtk/gtkcssstaticstyle.c:237
   _gtk_css_lookup_resolve (lookup=lookup@entry=0x1e7e790, 
provider=provider@entry=0x0, style=style@entry=0x1e7c320, 
parent_style=parent_style@entry=0x0) at ../../../../gtk/gtkcsslookup.c:122
   gtk_css_static_style_new_compute (provider=provider@entry=0x0, 
matcher=matcher@entry=0x0, parent=parent@entry=0x0) at 
../../../../gtk/gtkcssstaticstyle.c:195

  Original report
  ---
  Session suddenly stopped and came back to login screen, all opened windows 
lost.

  ProblemType: Crash
  DistroRelease: Ubuntu 19.10
  Package: apport-gtk 2.20.11-0ubuntu7
  ProcVersionSignature: Ubuntu 5.2.0-15.16-generic 5.2.9
  Uname: Linux 5.2.0-15-generic x86_64
  ApportVersion: 2.20.11-0ubuntu7
  Architecture: amd64
  CrashReports:
   640:1000:117:7292709:2019-09-03 16:20:13.909392833 +0200:2019-09-03 
16:20:14.909392833 +0200:/var/crash/_usr_share_apport_apport-gtk.1000.crash
   640:1000:117:48937942:2019-09-03 16:20:11.681426286 +0200:2019-09-03 
16:20:12.681426286 +0200:/var/crash/_usr_bin_gnome-shell.1000.crash
   640:1000:117:32054:2019-08-27 17:39:07.125607490 +0200:2019-08-28 
12:36:17.087672961 +0200:/var/crash/_usr_bin_dbus-daemon.1000.crash
  CurrentDesktop: ubuntu:GNOME
  Date: Tue Sep  3 16:20:13 2019
  ExecutablePath: /usr/share/apport/apport-gtk
  InstallationDate: Installed on 2018-06-16 (443 days ago)
  InstallationMedia: Ubuntu 18.10 "Cosmic Cuttlefish" - Alpha amd64 (20180611)
  InterpreterPath: /usr/bin/python3.7
  PackageArchitecture: all
  ProcCmdline: /usr/bin/python3 /usr/share/apport/apport-gtk
  ProcEnviron:
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=fr_FR.UTF-8
   SHELL=/bin/bash
  Python3Details: /usr/bin/python3.7, Python 3.7.4, python3-minimal, 3.7.3-1
  PythonDetails: /usr/bin/python2.7, Python 2.7.16+, python-minimal, 2.7.16-1
  SegvAnalysis:
   Segfault happened at: 0x7f532548f8c4:mov0x18(%rdi),%rax
   PC (0x7f532548f8c4) ok
   source "0x18(%rdi)" (0x0018) not located in a known VMA region (needed 
readable region)!
   destination "%rax" ok
  SegvReason: reading NULL VMA
  Signal: 11
  SourcePackage: apport
  StacktraceTop:
   ?? () from /usr/lib/x86_64-linux-gnu/libgtk-3.so.0
   ?? () from /usr/lib/x86_64-linux-gnu/libgtk-3.so.0
   ?? () from /usr/lib/x86_64-linux-gnu/libgtk-3.so.0
   ?? () from /usr/lib/x86_64-linux-gnu/libgtk-3.so.0
   ?? () from /usr/lib/x86_64-linux-gnu/libgtk-3.so.0
  Title: apport-gtk crashed with SIGSEGV
  UpgradeStatus: Upgraded to eoan on 2019-06-10 (84 days ago)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
  separator:

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


-- 

[Touch-packages] [Bug 2004554] [NEW] While using application switching in multi-tasking

[Akshya Singh]

Public bug reported:

While switching workspace, the option : include applications from
current workspace only is opted. The files founder does not switch
properly. If opened in one workspace, and switched to another workspace.
Then the dot ( that shoes finder is open) does not go away. And many
more please check.

ProblemType: Bug
DistroRelease: Ubuntu 22.04
Package: xorg 1:7.7+23ubuntu2
ProcVersionSignature: Ubuntu 5.15.0-58.64-generic 5.15.74
Uname: Linux 5.15.0-58-generic x86_64
ApportVersion: 2.20.11-0ubuntu82.3
Architecture: amd64
BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
CasperMD5CheckResult: unknown
CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
CompositorRunning: None
CurrentDesktop: ubuntu:GNOME
Date: Thu Feb  2 16:47:24 2023
DistUpgraded: 2023-01-27 15:07:45,014 DEBUG Running PostInstallScript: 
'/usr/lib/ubuntu-advantage/upgrade_lts_contract.py'
DistroCodename: jammy
DistroVariant: ubuntu
ExtraDebuggingInterest: Yes
GraphicsCard:
 Intel Corporation CoffeeLake-H GT2 [UHD Graphics 630] [8086:3e9b] (prog-if 00 
[VGA controller])
   Subsystem: Micro-Star International Co., Ltd. [MSI] CoffeeLake-H GT2 [UHD 
Graphics 630] [1462:12aa]
 NVIDIA Corporation TU106M [GeForce RTX 2060 Mobile] [10de:1f15] (rev a1) 
(prog-if 00 [VGA controller])
   Subsystem: Micro-Star International Co., Ltd. [MSI] TU106M [GeForce RTX 2060 
Mobile] [1462:12aa]
InstallationDate: Installed on 2021-05-11 (631 days ago)
InstallationMedia: Ubuntu 20.04.2.0 LTS "Focal Fossa" - Release amd64 
(20210209.1)
MachineType: Micro-Star International Co., Ltd. GF65 Thin 9SEXR
ProcEnviron:
 LANGUAGE=en_IN:en
 PATH=(custom, no user)
 XDG_RUNTIME_DIR=
 LANG=en_IN
 SHELL=/bin/bash
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.15.0-58-generic 
root=UUID=f2aafeb8-65f1-4f53-a7f4-a8bac75a5fbd ro quiet splash vt.handoff=7
SourcePackage: xorg
Symptom: display
UpgradeStatus: Upgraded to jammy on 2023-01-27 (6 days ago)
dmi.bios.date: 10/21/2021
dmi.bios.release: 1.12
dmi.bios.vendor: American Megatrends Inc.
dmi.bios.version: E16W1IMS.10C
dmi.board.asset.tag: Default string
dmi.board.name: MS-16W1
dmi.board.vendor: Micro-Star International Co., Ltd.
dmi.board.version: REV:1.0
dmi.chassis.asset.tag: Default string
dmi.chassis.type: 10
dmi.chassis.vendor: Micro-Star International Co., Ltd.
dmi.chassis.version: Default string
dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrE16W1IMS.10C:bd10/21/2021:br1.12:svnMicro-StarInternationalCo.,Ltd.:pnGF65Thin9SEXR:pvrREV1.0:rvnMicro-StarInternationalCo.,Ltd.:rnMS-16W1:rvrREV1.0:cvnMicro-StarInternationalCo.,Ltd.:ct10:cvrDefaultstring:sku16W1.1:
dmi.product.family: GF
dmi.product.name: GF65 Thin 9SEXR
dmi.product.sku: 16W1.1
dmi.product.version: REV:1.0
dmi.sys.vendor: Micro-Star International Co., Ltd.
version.compiz: compiz N/A
version.libdrm2: libdrm2 2.4.110-1ubuntu1
version.libgl1-mesa-dri: libgl1-mesa-dri 22.0.5-0ubuntu0.3
version.libgl1-mesa-glx: libgl1-mesa-glx N/A
version.xserver-xorg-core: xserver-xorg-core 2:21.1.3-2ubuntu2.5
version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-2ubuntu1
version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20210115-1
version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.17-2build1

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


** Tags: amd64 apport-bug jammy possible-manual-nvidia-install ubuntu

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

Title:
  While using application switching in multi-tasking

Status in xorg package in Ubuntu:
  New

Bug description:
  While switching workspace, the option : include applications from
  current workspace only is opted. The files founder does not switch
  properly. If opened in one workspace, and switched to another
  workspace. Then the dot ( that shoes finder is open) does not go away.
  And many more please check.

  ProblemType: Bug
  DistroRelease: Ubuntu 22.04
  Package: xorg 1:7.7+23ubuntu2
  ProcVersionSignature: Ubuntu 5.15.0-58.64-generic 5.15.74
  Uname: Linux 5.15.0-58-generic x86_64
  ApportVersion: 2.20.11-0ubuntu82.3
  Architecture: amd64
  BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
  CasperMD5CheckResult: unknown
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: None
  CurrentDesktop: ubuntu:GNOME
  Date: Thu Feb  2 16:47:24 2023
  DistUpgraded: 2023-01-27 15:07:45,014 DEBUG Running PostInstallScript: 
'/usr/lib/ubuntu-advantage/upgrade_lts_contract.py'
  DistroCodename: jammy
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes
  GraphicsCard:
   Intel Corporation CoffeeLake-H GT2 [UHD Graphics 630] [8086:3e9b] (prog-if 
00 [VGA controller])
 Subsystem: Micro-Star International Co., Ltd. [MSI] 

[Touch-packages] [Bug 1937110] Re: dhcp option 121 & 249

[sascha arthur]

Thanks for updating the version.

Lately we just wasted 4 workdays pitfalling again over the issue,
without remembering it.

We lately tried if its fixed.

Sadly its still not fixed in

http://cdimage.ubuntu.com/cdimage/ubuntu-server/jammy/daily-
live/current/jammy-live-server-amd64.iso

with sha

f2a1fca61a38d71b7f9d0aaebcd534710f6ef543366d203ada5cf676a4fb4219


Still we can confirm, that the default route is missing. 

DHCP works perfectly fine, but the default route is missing if one of
those options is provided by isc-dhcp:

option rfc3442-classless-static-routes 0,10,141,255,254;
option ms-classless-static-routes  0,10,141,255,254;

sadly it seems the dhcp-client is even internally crashing, without
changing the return code / putting an error message on the console.

removing both of the dhcp options, let the dhcp install the default
route again.

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

Title:
  dhcp option 121 & 249

Status in subiquity:
  New
Status in isc-dhcp package in Ubuntu:
  Fix Released
Status in isc-dhcp source package in Focal:
  In Progress
Status in isc-dhcp source package in Jammy:
  In Progress

Bug description:
  [Impact]

   * DHCP classless static routes aren't applied
 by dhclient at the initramfs (e.g., ip=dhcp).

   * This happens as rfc3442-classless-routes is
 not copied to /etc/dhcp/dhclient-exit-hooks.d/
 in the initramfs.

   * On Jammy, if such DHCP option(s) are present
 in the DHCP server response, the DHCP client
 ignores the 'routers' option from the server,
 thus leaving no routes configured.

   * On Focal, the older code still adds 'routers',
 which is slightly better, but still does not
 add the classless static routes.

  [Test Plan]

   * Use LXD container/VMs for DHCP server/client,
 configure the DHCP server with option 121,
 and some sample classless static routes.
 (see comments #12/jammy and #13/focal).

  [Regression Potential]

   * Acquisition of DHCP leases/routes at initramfs
 with ip=dhcp.

   * The code/script is not new, and is exercised
 normally during on rootfs (ie, post-initramfs)
 when dhclient is run.

   * It's also been in the initramfs in Kinetic
 already, since on Aug 2022; giving it tests.

  [Original Description]
  Hello,

  I'm running into issues with subiquity on a cloud provider.  The cloud
  provider is using an on-link L3 gateway.

  His DHCP response looks like this:

  OPTION:  53 (  1) DHCP message type 5 (DHCPACK)
  OPTION:  54 (  4) Server identifier 172.31.1.1
  OPTION:  51 (  4) IP address leasetime  86400 (24h)
  OPTION:   1 (  4) Subnet mask   255.255.255.255
  OPTION:   3 (  4) Routers   172.31.1.1
  OPTION:   6 ( 12) DNS server
  OPTION: 121 ( 14) Classless Static Route20ac1f010100  ...
   ac1f0101 ..
  OPTION: 249 ( 14) MSFT - Classless route20ac1f010100  ...
   ac1f0101 ..

  Im booting the subiquity process with an patched ipxe
  (https://github.com/ipxe/ipxe/pull/104) like this:

  #!ipxe
  kernel .../vmlinuz initrd=initrd root=/dev/ram0 ramdisk_size=150 ip=dhcp 
url=https://cdimage.ubuntu.com/ubuntu-server/focal/daily-live/current/focal-live-server-amd64.iso
 autoinstall ds=nocloud-net;s=.../...-ad-78/ cloud-config-url=/dev/null
  initrd .../initrd
  boot

  initrd/vmlinuz is extracted right out of focal-live-server-amd64.iso

  Sadly subiquity is stuck with a broken network (because of missing
  dhcp option 121/249 support). It happens when its running the /init
  from the kernel right after kernel is booted, i guess even before the
  subiquity is started(?).

  After further debugging, it looks like the provided kernel 5.4.80 #90
  Ubuntu, is using busybox 1.30.1-4ubuntu~6.3 which includes isc-
  dhclient-4.4.1 which is lacking the given options.

  Would be awesome if this could be fixed.. maybe just a simple busybox
  compile option?

To manage notifications about this bug go to:
https://bugs.launchpad.net/subiquity/+bug/1937110/+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 2004552] [NEW] Sound doesn't work on ASUS X670E-E motherboard.

[Alexander Koskovich]

Public bug reported:

None of the outputs work for my digital optical output on my ASUS ROG
STRIX X670E-E GAMING WIFI motherboard since updating the ALC4080/ALC4082
firmware.

The issue is resolved in the upstream package of alsa-ucm-conf
(https://github.com/alsa-project/alsa-ucm-conf). When I applied the
newer configs sound started working again.

ProblemType: Bug
DistroRelease: Ubuntu 22.10
Package: alsa-base 1.0.25+dfsg-0ubuntu7
ProcVersionSignature: Ubuntu 5.19.0-29.30-generic 5.19.17
Uname: Linux 5.19.0-29-generic x86_64
NonfreeKernelModules: nvidia_modeset nvidia
ApportVersion: 2.23.1-0ubuntu3
Architecture: amd64
CasperMD5CheckResult: pass
CurrentDesktop: ubuntu:GNOME
Date: Thu Feb  2 06:08:15 2023
InstallationDate: Installed on 2023-01-08 (24 days ago)
InstallationMedia: Ubuntu 22.10 "Kinetic Kudu" - Release amd64 (20221020)
PackageArchitecture: all
ProcEnviron:
 TERM=xterm-256color
 PATH=(custom, no user)
 XDG_RUNTIME_DIR=
 LANG=en_US.UTF-8
 SHELL=/bin/bash
SourcePackage: alsa-driver
Symptom: audio
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 11/04/2022
dmi.bios.release: 8.5
dmi.bios.vendor: American Megatrends Inc.
dmi.bios.version: 0805
dmi.board.asset.tag: Default string
dmi.board.name: ROG STRIX X670E-E GAMING WIFI
dmi.board.vendor: ASUSTeK COMPUTER INC.
dmi.board.version: Rev 1.xx
dmi.chassis.asset.tag: Default string
dmi.chassis.type: 3
dmi.chassis.vendor: Default string
dmi.chassis.version: Default string
dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr0805:bd11/04/2022:br8.5:svnASUS:pnSystemProductName:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnROGSTRIXX670E-EGAMINGWIFI:rvrRev1.xx:cvnDefaultstring:ct3:cvrDefaultstring:skuSKU:
dmi.product.family: To be filled by O.E.M.
dmi.product.name: System Product Name
dmi.product.sku: SKU
dmi.product.version: System Version
dmi.sys.vendor: ASUS

** Affects: alsa-driver (Ubuntu)
 Importance: Undecided
 Status: New


** Tags: amd64 apport-bug kinetic

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

Title:
  Sound doesn't work on ASUS X670E-E motherboard.

Status in alsa-driver package in Ubuntu:
  New

Bug description:
  None of the outputs work for my digital optical output on my ASUS ROG
  STRIX X670E-E GAMING WIFI motherboard since updating the
  ALC4080/ALC4082 firmware.

  The issue is resolved in the upstream package of alsa-ucm-conf
  (https://github.com/alsa-project/alsa-ucm-conf). When I applied the
  newer configs sound started working again.

  ProblemType: Bug
  DistroRelease: Ubuntu 22.10
  Package: alsa-base 1.0.25+dfsg-0ubuntu7
  ProcVersionSignature: Ubuntu 5.19.0-29.30-generic 5.19.17
  Uname: Linux 5.19.0-29-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  ApportVersion: 2.23.1-0ubuntu3
  Architecture: amd64
  CasperMD5CheckResult: pass
  CurrentDesktop: ubuntu:GNOME
  Date: Thu Feb  2 06:08:15 2023
  InstallationDate: Installed on 2023-01-08 (24 days ago)
  InstallationMedia: Ubuntu 22.10 "Kinetic Kudu" - Release amd64 (20221020)
  PackageArchitecture: all
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: alsa-driver
  Symptom: audio
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 11/04/2022
  dmi.bios.release: 8.5
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 0805
  dmi.board.asset.tag: Default string
  dmi.board.name: ROG STRIX X670E-E GAMING WIFI
  dmi.board.vendor: ASUSTeK COMPUTER INC.
  dmi.board.version: Rev 1.xx
  dmi.chassis.asset.tag: Default string
  dmi.chassis.type: 3
  dmi.chassis.vendor: Default string
  dmi.chassis.version: Default string
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr0805:bd11/04/2022:br8.5:svnASUS:pnSystemProductName:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnROGSTRIXX670E-EGAMINGWIFI:rvrRev1.xx:cvnDefaultstring:ct3:cvrDefaultstring:skuSKU:
  dmi.product.family: To be filled by O.E.M.
  dmi.product.name: System Product Name
  dmi.product.sku: SKU
  dmi.product.version: System Version
  dmi.sys.vendor: ASUS

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/2004552/+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 2004551] Re: upgrade to lunar fails due to rescue-ssh.target or port 22 takeover

[Christian Ehrhardt ]

As expected, on reboot all is fine for the service status


ubuntu@node-horsea:~$ systemctl status ssh.service
● ssh.service - OpenBSD Secure Shell server
 Loaded: loaded (/lib/systemd/system/ssh.service; disabled; preset: enabled)
Drop-In: /etc/systemd/system/ssh.service.d
 └─00-socket.conf
 Active: active (running) since Thu 2023-02-02 10:54:40 UTC; 12min ago
TriggeredBy: ● ssh.socket
   Docs: man:sshd(8)
 man:sshd_config(5)
Process: 2689 ExecStartPre=/usr/sbin/sshd -t (code=exited, status=0/SUCCESS)
   Main PID: 2690 (sshd)
  Tasks: 1 (limit: 38220)
 Memory: 5.3M
CPU: 894ms
 CGroup: /system.slice/ssh.service
 └─2690 "sshd: /usr/sbin/sshd -D [listener] 0 of 10-100 startups"

Feb 02 11:06:27 node-horsea sshd[14629]: Accepted publickey for ubuntu from 
10.172.196.173 port 47348 ssh2: RSA 
SHA256:KyONnhWWzlbscZNTHPZ25GWCXDQY5u/UD72EtQcwtqU
Feb 02 11:06:27 node-horsea sshd[14629]: pam_unix(sshd:session): session opened 
for user ubuntu(uid=1000) by (uid=0)
Feb 02 11:06:27 node-horsea sshd[14629]: pam_env(sshd:session): deprecated 
reading of user environment enabled
Feb 02 11:06:58 node-horsea sshd[14735]: Accepted publickey for ubuntu from 
10.172.196.173 port 55016 ssh2: RSA 
SHA256:KyONnhWWzlbscZNTHPZ25GWCXDQY5u/UD72EtQcwtqU
Feb 02 11:06:58 node-horsea sshd[14735]: pam_unix(sshd:session): session opened 
for user ubuntu(uid=1000) by (uid=0)
Feb 02 11:06:59 node-horsea sshd[14735]: pam_env(sshd:session): deprecated 
reading of user environment enabled
Feb 02 11:07:03 node-horsea sshd[14796]: Accepted publickey for ubuntu from 
10.172.196.173 port 57034 ssh2: RSA 
SHA256:KyONnhWWzlbscZNTHPZ25GWCXDQY5u/UD72EtQcwtqU
Feb 02 11:07:03 node-horsea sshd[14796]: pam_unix(sshd:session): session opened 
for user ubuntu(uid=1000) by (uid=0)
Feb 02 11:07:03 node-horsea sshd[14796]: pam_env(sshd:session): deprecated 
reading of user environment enabled
Feb 02 11:07:03 node-horsea sshd[14796]: pam_unix(sshd:session): session closed 
for user ubuntu
ubuntu@node-horsea:~$ systemctl status ssh.socket
● ssh.socket - OpenBSD Secure Shell server socket
 Loaded: loaded (/lib/systemd/system/ssh.socket; enabled; preset: enabled)
 Active: active (running) since Thu 2023-02-02 10:54:21 UTC; 12min ago
  Until: Thu 2023-02-02 10:54:21 UTC; 12min ago
   Triggers: ● ssh.service
 Listen: [::]:22 (Stream)
  Tasks: 0 (limit: 38220)
 Memory: 8.0K
CPU: 894us
 CGroup: /system.slice/ssh.socket

Feb 02 10:54:21 node-horsea systemd[1]: Listening on OpenBSD Secure
Shell server socket.


And out of this condition it can even complete the package
configuration.

ubuntu@node-horsea:~$ sudo dpkg-reconfigure openssh-server
/usr/sbin/dpkg-reconfigure: openssh-server is broken or not fully installed
ubuntu@node-horsea:~$ sudo apt-get install --fix-broken
Reading package lists... Done
Building dependency tree... Done
Reading state information... Done
0 upgraded, 0 newly installed, 0 to remove and 0 not upgraded.
1 not fully installed or removed.
After this operation, 0 B of additional disk space will be used.
Setting up openssh-server (1:9.0p1-1ubuntu8) ...
Replacing config file /etc/ssh/sshd_config with new version
Replacing config file /etc/ssh/sshd_config with new version
Synchronizing state of ssh.service with SysV service script with 
/lib/systemd/systemd-sysv-install.
Executing: /lib/systemd/systemd-sysv-install disable ssh
Warning: Stopping ssh.service, but it can still be activated by:
  ssh.socket
rescue-ssh.target is a disabled or a static unit not running, not starting it.
ubuntu@node-horsea:~$ echo $?
0

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

Title:
  upgrade to lunar fails due to rescue-ssh.target or port 22 takeover

Status in openssh package in Ubuntu:
  New

Bug description:
  Hi,
  I just upgraded a system from Jammy to Lunar and openssh-server refuses to 
upgrade well.

  Setting up openssh-server (1:9.0p1-1ubuntu8) ...
  Replacing config file /etc/ssh/sshd_config with new version
  Replacing config file /etc/ssh/sshd_config with new version
  Synchronizing state of ssh.service with SysV service script with 
/lib/systemd/systemd-sysv-install.
  Executing: /lib/systemd/systemd-sysv-install disable ssh
  rescue-ssh.target is a disabled or a static unit not running, not starting it.
  Could not execute systemctl:  at /usr/bin/deb-systemd-invoke line 145.
  dpkg: error processing package openssh-server (--configure):
   installed openssh-server package post-installation script subprocess 
returned error exit status 1
  Processing triggers for man-db (2.11.2-1) ...
  Processing triggers for libc-bin (2.36-0ubuntu4) ...
  Errors were encountered while processing:
   openssh-server
  Error: Timeout was reached
  needrestart is being skipped since dpkg has failed
  E: Sub-process /usr/bin/dpkg 

[Touch-packages] [Bug 2004551] [NEW] upgrade to lunar fails due to rescue-ssh.target or port 22 takeover

[Christian Ehrhardt ]

Public bug reported:

Hi,
I just upgraded a system from Jammy to Lunar and openssh-server refuses to 
upgrade well.

Setting up openssh-server (1:9.0p1-1ubuntu8) ...
Replacing config file /etc/ssh/sshd_config with new version
Replacing config file /etc/ssh/sshd_config with new version
Synchronizing state of ssh.service with SysV service script with 
/lib/systemd/systemd-sysv-install.
Executing: /lib/systemd/systemd-sysv-install disable ssh
rescue-ssh.target is a disabled or a static unit not running, not starting it.
Could not execute systemctl:  at /usr/bin/deb-systemd-invoke line 145.
dpkg: error processing package openssh-server (--configure):
 installed openssh-server package post-installation script subprocess returned 
error exit status 1
Processing triggers for man-db (2.11.2-1) ...
Processing triggers for libc-bin (2.36-0ubuntu4) ...
Errors were encountered while processing:
 openssh-server
Error: Timeout was reached
needrestart is being skipped since dpkg has failed
E: Sub-process /usr/bin/dpkg returned an error code (1)

I'm not sure what exactly it is.
This output complains about rescue-ssh.target and indeed that can not be 
started even directly.

$ sudo systemctl start rescue-ssh.target
A dependency job for rescue-ssh.target failed. See 'journalctl -xe' for details.

And in postinst is a try to start it:
$  grep rescue /var/lib/dpkg/info/openssh-server.postinst 
deb-systemd-invoke $_dh_action 'rescue-ssh.target' >/dev/null 
|| true


But I think the underlying issue is that ssh is already on, and I'm logged in 
via it.
And that makes the service restart of the ssh socket which was added break.

Feb 02 10:40:56 node-horsea systemd[104560]: ssh.socket: Failed to create 
listening socket ([::]:22): Address already in use
Feb 02 10:40:56 node-horsea systemd[1]: ssh.socket: Failed to receive listening 
socket ([::]:22): Input/output error
Feb 02 10:40:56 node-horsea systemd[1]: ssh.socket: Failed to listen on 
sockets: Input/output error
Feb 02 10:40:56 node-horsea systemd[1]: ssh.socket: Failed with result 
'resources'.


Now, whichever it is, it is hard to resolve.
The only way to get the socket to own it would be rebooting so that sshd lets 
go and systemd can take over.
I could reboot, but that is not the point.
What if I'd want to get the service and upgrade completed before reboot.
Because as of now dpkg considers the system unhappy, and that would usually be 
a sign for "better not reboot before being resolved" to me.

One thing though, I have not upgraded with do-release-upgrade - would we
/ do we have magic there to make the ssh socket activation transition
smoother?

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

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

Title:
  upgrade to lunar fails due to rescue-ssh.target or port 22 takeover

Status in openssh package in Ubuntu:
  New

Bug description:
  Hi,
  I just upgraded a system from Jammy to Lunar and openssh-server refuses to 
upgrade well.

  Setting up openssh-server (1:9.0p1-1ubuntu8) ...
  Replacing config file /etc/ssh/sshd_config with new version
  Replacing config file /etc/ssh/sshd_config with new version
  Synchronizing state of ssh.service with SysV service script with 
/lib/systemd/systemd-sysv-install.
  Executing: /lib/systemd/systemd-sysv-install disable ssh
  rescue-ssh.target is a disabled or a static unit not running, not starting it.
  Could not execute systemctl:  at /usr/bin/deb-systemd-invoke line 145.
  dpkg: error processing package openssh-server (--configure):
   installed openssh-server package post-installation script subprocess 
returned error exit status 1
  Processing triggers for man-db (2.11.2-1) ...
  Processing triggers for libc-bin (2.36-0ubuntu4) ...
  Errors were encountered while processing:
   openssh-server
  Error: Timeout was reached
  needrestart is being skipped since dpkg has failed
  E: Sub-process /usr/bin/dpkg returned an error code (1)

  I'm not sure what exactly it is.
  This output complains about rescue-ssh.target and indeed that can not be 
started even directly.

  $ sudo systemctl start rescue-ssh.target
  A dependency job for rescue-ssh.target failed. See 'journalctl -xe' for 
details.

  And in postinst is a try to start it:
  $  grep rescue /var/lib/dpkg/info/openssh-server.postinst 
deb-systemd-invoke $_dh_action 'rescue-ssh.target' >/dev/null 
|| true

  
  But I think the underlying issue is that ssh is already on, and I'm logged in 
via it.
  And that makes the service restart of the ssh socket which was added break.

  Feb 02 10:40:56 node-horsea systemd[104560]: ssh.socket: Failed to create 
listening socket ([::]:22): Address already in use
  Feb 02 10:40:56 node-horsea systemd[1]: ssh.socket: Failed to receive 
listening socket ([::]:22): Input/output error
  Feb 02 10:40:56 

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

[Roxana Nicolescu]

Created a merge request for systemd:ubuntu-focal
https://code.launchpad.net/~roxanan/ubuntu/+source/systemd/+git/systemd/+merge/436747

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

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

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

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

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

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

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

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

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


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

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

[Launchpad Bug Tracker]

This bug was fixed in the package python-debian - 0.1.49ubuntu2

---
python-debian (0.1.49ubuntu2) lunar; urgency=medium

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

 -- Benjamin Drung   Wed, 01 Feb 2023 10:32:24 +0100

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

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

Title:
  Invalid PEP440 package version breaking setuptools >= 60

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

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

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

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

  suffix 1build1 is invalid.

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

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

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


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

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

[Roxana Nicolescu]

Fyi sysctl syscall was completely removed in 5.5
(88db0aa2421666d2f73486d15b239a4521983d55).

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

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

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

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

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

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

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

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

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


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

[Touch-packages] [Bug 2003892] Re: libcap2 seems to not work correctly when linked with -Bsymbolic-functions

[Danilo Egea Gondolfo]

More specifically, this test [1] is failing. It uses clone() to create a
process in a new user namespace and apparently it should fail.

I can't reproduce it with a LXD arhmf container on my own environment.
All the tests pass.

[1] -
https://git.launchpad.net/ubuntu/+source/libcap2/tree/tests/uns_test.c

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

Title:
  libcap2 seems to not work correctly when linked with -Bsymbolic-
  functions

Status in libcap2 package in Ubuntu:
  In Progress

Bug description:
  Ubuntu will include -Wl,-Bsymbolic-functions in the build flags by
  default. This option seems to break libcap2.

  One of the autopkgtests that is supposed to prevent an exploitation
  instance using capabilities fails:
  https://autopkgtest.ubuntu.com/results/autopkgtest-
  lunar/lunar/amd64/libc/libcap2/20230123_094238_95088@/log.gz

  The solution is to exclude this flag from the set of flags:

  debian/rules:
  export DEB_LDFLAGS_MAINT_STRIP = -Wl,-Bsymbolic-functions

  Debian seems to not be affected by that as they don't include this
  flag in their build:
  
https://buildd.debian.org/status/fetch.php?pkg=libcap2=amd64=1%3A2.66-3=1671660323=0

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/libcap2/+bug/2003892/+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 2003892] Re: libcap2 seems to not work correctly when linked with -Bsymbolic-functions

[Lukas Märdian]

There's now an additional failure on armhf only, which is most probably
related to the armhf test runners being executed as LXD containers on a
base system using an older kernel:

autopkgtest [09:46:55]: test upstream-root: [---
@@@ Running upstream tests (root required) @@@
## Preparation ##
## libcap2 tests ##
user namespace launched exploit worked - upgrade kernel
autopkgtest [09:46:58]: test upstream-root: ---]
autopkgtest [09:47:02]: test upstream-root:  - - - - - - - - - - results - - - 
- - - - - - -
upstream-rootFAIL non-zero exit status 1

That "upstream-root" test is a new case, which is not yet available in
the -release version of libcap2 (1:2.44-1build3), therefore this should
not be considered a regression, but rather an issue with the test
infrastructure. IMO this test case should be skipped or hinted on armhf.

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

Title:
  libcap2 seems to not work correctly when linked with -Bsymbolic-
  functions

Status in libcap2 package in Ubuntu:
  In Progress

Bug description:
  Ubuntu will include -Wl,-Bsymbolic-functions in the build flags by
  default. This option seems to break libcap2.

  One of the autopkgtests that is supposed to prevent an exploitation
  instance using capabilities fails:
  https://autopkgtest.ubuntu.com/results/autopkgtest-
  lunar/lunar/amd64/libc/libcap2/20230123_094238_95088@/log.gz

  The solution is to exclude this flag from the set of flags:

  debian/rules:
  export DEB_LDFLAGS_MAINT_STRIP = -Wl,-Bsymbolic-functions

  Debian seems to not be affected by that as they don't include this
  flag in their build:
  
https://buildd.debian.org/status/fetch.php?pkg=libcap2=amd64=1%3A2.66-3=1671660323=0

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/libcap2/+bug/2003892/+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 2004534] Re: suspend does not work

[Ubuntu Foundations Team Bug Bot]

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

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

Title:
  suspend does not work

Status in xorg package in Ubuntu:
  New

Bug description:
   - on locked screen: the keyboard blocks after a while and I cannot login 
anymore;
   - on unlocked screen: 
   = apps do not start (failed to start); 
   = no icon pictures on desktop; 
   = no wallpaper anymore (black background);

  ProblemType: Bug
  DistroRelease: Ubuntu 22.04
  Package: xorg 1:7.7+23ubuntu2
  ProcVersionSignature: Ubuntu 5.15.0-58.64-generic 5.15.74
  Uname: Linux 5.15.0-58-generic x86_64
  ApportVersion: 2.20.11-0ubuntu82.3
  Architecture: amd64
  BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
  CasperMD5CheckResult: pass
  CompositorRunning: None
  CurrentDesktop: ubuntu:GNOME
  Date: Thu Feb  2 07:15:13 2023
  DistUpgraded: Fresh install
  DistroCodename: jammy
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes, including running git bisection searches
  GraphicsCard:
   Advanced Micro Devices, Inc. [AMD/ATI] Barcelo [1002:15e7] (rev c2) (prog-if 
00 [VGA controller])
 Subsystem: Lenovo Device [17aa:3801]
  InstallationDate: Installed on 2023-02-01 (1 days ago)
  InstallationMedia: Ubuntu 22.04.1 LTS "Jammy Jellyfish" - Release amd64 
(20220809.1)
  MachineType: LENOVO 82RN
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.15.0-58-generic 
root=UUID=b63af605-bd2f-4b16-8bb4-1cc9bb85554c ro quiet splash vt.handoff=7
  SourcePackage: xorg
  Symptom: display
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 08/04/2022
  dmi.bios.release: 1.38
  dmi.bios.vendor: LENOVO
  dmi.bios.version: JTCN38WW
  dmi.board.asset.tag: No Asset Tag
  dmi.board.name: LNVNB161216
  dmi.board.vendor: LENOVO
  dmi.board.version: NO DPK
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: IdeaPad 3 15ABA7
  dmi.ec.firmware.release: 1.38
  dmi.modalias: 
dmi:bvnLENOVO:bvrJTCN38WW:bd08/04/2022:br1.38:efr1.38:svnLENOVO:pn82RN:pvrIdeaPad315ABA7:rvnLENOVO:rnLNVNB161216:rvrNODPK:cvnLENOVO:ct10:cvrIdeaPad315ABA7:skuLENOVO_MT_82RN_BU_idea_FM_IdeaPad315ABA7:
  dmi.product.family: IdeaPad 3 15ABA7
  dmi.product.name: 82RN
  dmi.product.sku: LENOVO_MT_82RN_BU_idea_FM_IdeaPad 3 15ABA7
  dmi.product.version: IdeaPad 3 15ABA7
  dmi.sys.vendor: LENOVO
  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.110-1ubuntu1
  version.libgl1-mesa-dri: libgl1-mesa-dri 22.0.5-0ubuntu0.1
  version.libgl1-mesa-glx: libgl1-mesa-glx N/A
  version.xserver-xorg-core: xserver-xorg-core 2:21.1.3-2ubuntu2.5
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-2ubuntu1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20210115-1
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 
1:1.0.17-2build1

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/2004534/+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 2004534] [NEW] suspend does not work

[Launchpad Bug Tracker]

You have been subscribed to a public bug:

 - on locked screen: the keyboard blocks after a while and I cannot login 
anymore;
 - on unlocked screen: 
 = apps do not start (failed to start); 
 = no icon pictures on desktop; 
 = no wallpaper anymore (black background);

ProblemType: Bug
DistroRelease: Ubuntu 22.04
Package: xorg 1:7.7+23ubuntu2
ProcVersionSignature: Ubuntu 5.15.0-58.64-generic 5.15.74
Uname: Linux 5.15.0-58-generic x86_64
ApportVersion: 2.20.11-0ubuntu82.3
Architecture: amd64
BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
CasperMD5CheckResult: pass
CompositorRunning: None
CurrentDesktop: ubuntu:GNOME
Date: Thu Feb  2 07:15:13 2023
DistUpgraded: Fresh install
DistroCodename: jammy
DistroVariant: ubuntu
ExtraDebuggingInterest: Yes, including running git bisection searches
GraphicsCard:
 Advanced Micro Devices, Inc. [AMD/ATI] Barcelo [1002:15e7] (rev c2) (prog-if 
00 [VGA controller])
   Subsystem: Lenovo Device [17aa:3801]
InstallationDate: Installed on 2023-02-01 (1 days ago)
InstallationMedia: Ubuntu 22.04.1 LTS "Jammy Jellyfish" - Release amd64 
(20220809.1)
MachineType: LENOVO 82RN
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.15.0-58-generic 
root=UUID=b63af605-bd2f-4b16-8bb4-1cc9bb85554c ro quiet splash vt.handoff=7
SourcePackage: xorg
Symptom: display
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 08/04/2022
dmi.bios.release: 1.38
dmi.bios.vendor: LENOVO
dmi.bios.version: JTCN38WW
dmi.board.asset.tag: No Asset Tag
dmi.board.name: LNVNB161216
dmi.board.vendor: LENOVO
dmi.board.version: NO DPK
dmi.chassis.asset.tag: No Asset Tag
dmi.chassis.type: 10
dmi.chassis.vendor: LENOVO
dmi.chassis.version: IdeaPad 3 15ABA7
dmi.ec.firmware.release: 1.38
dmi.modalias: 
dmi:bvnLENOVO:bvrJTCN38WW:bd08/04/2022:br1.38:efr1.38:svnLENOVO:pn82RN:pvrIdeaPad315ABA7:rvnLENOVO:rnLNVNB161216:rvrNODPK:cvnLENOVO:ct10:cvrIdeaPad315ABA7:skuLENOVO_MT_82RN_BU_idea_FM_IdeaPad315ABA7:
dmi.product.family: IdeaPad 3 15ABA7
dmi.product.name: 82RN
dmi.product.sku: LENOVO_MT_82RN_BU_idea_FM_IdeaPad 3 15ABA7
dmi.product.version: IdeaPad 3 15ABA7
dmi.sys.vendor: LENOVO
version.compiz: compiz N/A
version.libdrm2: libdrm2 2.4.110-1ubuntu1
version.libgl1-mesa-dri: libgl1-mesa-dri 22.0.5-0ubuntu0.1
version.libgl1-mesa-glx: libgl1-mesa-glx N/A
version.xserver-xorg-core: xserver-xorg-core 2:21.1.3-2ubuntu2.5
version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-2ubuntu1
version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20210115-1
version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.17-2build1

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


** Tags: amd64 apport-bug jammy ubuntu wayland-session
-- 
suspend does not work
https://bugs.launchpad.net/bugs/2004534
You received this bug notification because you are a member of Ubuntu Touch 
seeded packages, which is subscribed to xorg in Ubuntu.

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