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

[BloodyIron]

I just upgraded a core system from Ubuntu 18.04->20.04->22.04, and this
is somehow the only system that has this 2minute + wait bug.

How exactly was this not handled automatically in the upgrade process
for 20.04->22.04? Isn't that the whole point of that automation?

I'm not entirely sure right now what I _should_ do to correct this... :/
this sucks

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

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

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

Bug description:
  [NOTE]

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

  $ systemctl disable --now systemd-networkd.service

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

  [Impact]

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

  [Test Plan]

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

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

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

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

  3. Re-generate and apply the netplan configuration.

  $ netplan generate
  $ netplan apply

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

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

  [Where problems could occur]

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

  [Original Description]

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

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

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


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

[Touch-packages] [Bug 2023322] Re: GTK internal browser does not render with Nvidia drivers

[Daniel van Vugt]

** Summary changed:

- Unable to setup Google Online Accounts with Nvidia drivers
+ GTK internal browser does not render with Nvidia drivers

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

Title:
  GTK internal browser does not render with Nvidia drivers

Status in Webkit:
  Confirmed
Status in gnome-control-center package in Ubuntu:
  Triaged
Status in gnome-online-accounts package in Ubuntu:
  Triaged
Status in webkit2gtk package in Ubuntu:
  In Progress
Status in yelp package in Ubuntu:
  Triaged
Status in webkit2gtk package in Debian:
  Fix Released

Bug description:
  When I go into Settings > Online Accounts > Google, I get to the
  prompt for email address, once in a while it stops accepting input
  there. But often I can get to the password screen. Once I do, I can't
  type anything or paste anything.

  This is a fresh install of Ubuntu 23.04 and I have installed all
  updates.

  Nothing in /var/crash

  Jun 08 11:15:59 CCW-HAL systemd[3523]: 
vte-spawn-8b4a59a3-a060-4bdd-92e6-285656bdb9a2.scope: Consumed 3.448s CPU time.
  Jun 08 11:16:01 CCW-HAL gnome-shell[3803]: g_closure_unref: assertion 
'closure->ref_count > 0' failed
  Jun 08 11:16:01 CCW-HAL gnome-shell[3803]: g_closure_unref: assertion 
'closure->ref_count > 0' failed
  Jun 08 11:16:01 CCW-HAL gnome-shell[3803]: g_closure_unref: assertion 
'closure->ref_count > 0' failed
  Jun 08 11:16:29 CCW-HAL systemd[3523]: Started 
app-gnome-org.gnome.Terminal-10924.scope - Application launched by gnome-shell.
  Jun 08 11:16:29 CCW-HAL dbus-daemon[3552]: [session uid=1000 pid=3552] 
Activating via systemd: service name='org.gnome.Terminal' 
unit='gnome-terminal-server.service' requested by ':1.167' (uid=1000 pid=10927 
comm="/usr/bin/gnome-terminal.real" label="unconfined")
  Jun 08 11:16:29 CCW-HAL systemd[3523]: Starting gnome-terminal-server.service 
- GNOME Terminal Server...
  Jun 08 11:16:29 CCW-HAL dbus-daemon[3552]: [session uid=1000 pid=3552] 
Successfully activated service 'org.gnome.Terminal'
  Jun 08 11:16:29 CCW-HAL systemd[3523]: Started gnome-terminal-server.service 
- GNOME Terminal Server.
  Jun 08 11:16:29 CCW-HAL systemd[3523]: Started 
vte-spawn-9cee1911-372a-4bb4-8b57-694984e43990.scope - VTE child process 10955 
launched by gnome-terminal-server process 10931.
  Jun 08 11:16:49 CCW-HAL gnome-control-c[8079]: Error showing account: Child 
process exited with code 1
  Jun 08 11:16:53 CCW-HAL gnome-online-accounts-panel.desktop[9764]: GLib-GIO: 
Using cross-namespace EXTERNAL authentication (this will deadlock if server is 
GDBus < 2.73.3)GLib-GIO: _g_io_module_get_default: Found default implementation 
gvfs (GDaemonVfs) for ‘gio-vfs’GLib: unsetenv() is not thread-safe and should 
not be used after threads are createdGLib-GIO: _g_io_module_get_default: Found 
default implementation dconf (DConfSettingsBackend) for 
‘gsettings-backend’GoaBackend: Loading all providers: GoaBackend: - 
googleGoaBackend: - owncloudGoaBackend: - windows_liveGoaBackend: - 
exchangeGoaBackend: - lastfmGoaBackend: - imap_smtpGoaBackend: - 
kerberosGoaBackend: activated kerberos providerGLib-GIO: 
_g_io_module_get_default: Found default implementation gnutls 
(GTlsBackendGnutls) for ‘gio-tls-backend’Failed to create account: Dialog was 
dismissed
  Jun 08 11:16:53 CCW-HAL xdg-desktop-por[3907]: Realtime error: Could not map 
pid: Could not determine pid namespace: Could not find instance-id in process's 
/.flatpak-info
  Jun 08 11:17:01 CCW-HAL CRON[11093]: pam_unix(cron:session): session opened 
for user root(uid=0) by (uid=0)
  Jun 08 11:17:01 CCW-HAL CRON[11094]: (root) CMD (cd / && run-parts --report 
/etc/cron.hourly)
  Jun 08 11:17:01 CCW-HAL CRON[11093]: pam_unix(cron:session): session closed 
for user root
  Jun 08 11:17:06 CCW-HAL kernel: WebKitWebProces[11026]: segfault at 
55bd22ad9adc ip 55bd22ad9adc sp 7ffd1f6adbe8 error 14 likely on CPU 2 
(core 2, socket 0)
  Jun 08 11:17:06 CCW-HAL kernel: Code: Unable to access opcode bytes at 
0x55bd22ad9ab2.
  Jun 08 11:17:36 CCW-HAL gnome-shell[3803]: Window manager warning: 
WM_TRANSIENT_FOR window 0x3a02767 for 0x3a02778 window override-redirect is an 
override-redirect window and this is not correct according to the standard, so 
we'll fallback to the first non-override-redirect window 0x3a006dc.
  Jun 08 11:17:42 CCW-HAL systemd[1]: Starting systemd-tmpfiles-clean.service - 
Cleanup of Temporary Directories...
  Jun 08 11:17:42 CCW-HAL systemd[1]: systemd-tmpfiles-clean.service: 
Deactivated successfully.
  Jun 08 11:17:42 CCW-HAL systemd[1]: Finished systemd-tmpfiles-clean.service - 
Cleanup of Temporary Directories.
  Jun 08 11:17:42 CCW-HAL systemd[1]: 
run-credentials-systemd\x2dtmpfiles\x2dclean.service.mount: Deactivated 
successfully.
  Jun 08 11:18:10 CCW-HAL gnome-shell[3803]: Window manager warning: 
WM_TRANSIENT_FOR window 0x3a029e2 

[Touch-packages] [Bug 2023322] Re: Unable to setup Google Online Accounts with Nvidia drivers

[Daniel van Vugt]

** Tags added: jammy

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

Title:
  Unable to setup Google Online Accounts with Nvidia drivers

Status in Webkit:
  Confirmed
Status in gnome-control-center package in Ubuntu:
  Triaged
Status in gnome-online-accounts package in Ubuntu:
  Triaged
Status in webkit2gtk package in Ubuntu:
  In Progress
Status in yelp package in Ubuntu:
  Triaged
Status in webkit2gtk package in Debian:
  Fix Released

Bug description:
  When I go into Settings > Online Accounts > Google, I get to the
  prompt for email address, once in a while it stops accepting input
  there. But often I can get to the password screen. Once I do, I can't
  type anything or paste anything.

  This is a fresh install of Ubuntu 23.04 and I have installed all
  updates.

  Nothing in /var/crash

  Jun 08 11:15:59 CCW-HAL systemd[3523]: 
vte-spawn-8b4a59a3-a060-4bdd-92e6-285656bdb9a2.scope: Consumed 3.448s CPU time.
  Jun 08 11:16:01 CCW-HAL gnome-shell[3803]: g_closure_unref: assertion 
'closure->ref_count > 0' failed
  Jun 08 11:16:01 CCW-HAL gnome-shell[3803]: g_closure_unref: assertion 
'closure->ref_count > 0' failed
  Jun 08 11:16:01 CCW-HAL gnome-shell[3803]: g_closure_unref: assertion 
'closure->ref_count > 0' failed
  Jun 08 11:16:29 CCW-HAL systemd[3523]: Started 
app-gnome-org.gnome.Terminal-10924.scope - Application launched by gnome-shell.
  Jun 08 11:16:29 CCW-HAL dbus-daemon[3552]: [session uid=1000 pid=3552] 
Activating via systemd: service name='org.gnome.Terminal' 
unit='gnome-terminal-server.service' requested by ':1.167' (uid=1000 pid=10927 
comm="/usr/bin/gnome-terminal.real" label="unconfined")
  Jun 08 11:16:29 CCW-HAL systemd[3523]: Starting gnome-terminal-server.service 
- GNOME Terminal Server...
  Jun 08 11:16:29 CCW-HAL dbus-daemon[3552]: [session uid=1000 pid=3552] 
Successfully activated service 'org.gnome.Terminal'
  Jun 08 11:16:29 CCW-HAL systemd[3523]: Started gnome-terminal-server.service 
- GNOME Terminal Server.
  Jun 08 11:16:29 CCW-HAL systemd[3523]: Started 
vte-spawn-9cee1911-372a-4bb4-8b57-694984e43990.scope - VTE child process 10955 
launched by gnome-terminal-server process 10931.
  Jun 08 11:16:49 CCW-HAL gnome-control-c[8079]: Error showing account: Child 
process exited with code 1
  Jun 08 11:16:53 CCW-HAL gnome-online-accounts-panel.desktop[9764]: GLib-GIO: 
Using cross-namespace EXTERNAL authentication (this will deadlock if server is 
GDBus < 2.73.3)GLib-GIO: _g_io_module_get_default: Found default implementation 
gvfs (GDaemonVfs) for ‘gio-vfs’GLib: unsetenv() is not thread-safe and should 
not be used after threads are createdGLib-GIO: _g_io_module_get_default: Found 
default implementation dconf (DConfSettingsBackend) for 
‘gsettings-backend’GoaBackend: Loading all providers: GoaBackend: - 
googleGoaBackend: - owncloudGoaBackend: - windows_liveGoaBackend: - 
exchangeGoaBackend: - lastfmGoaBackend: - imap_smtpGoaBackend: - 
kerberosGoaBackend: activated kerberos providerGLib-GIO: 
_g_io_module_get_default: Found default implementation gnutls 
(GTlsBackendGnutls) for ‘gio-tls-backend’Failed to create account: Dialog was 
dismissed
  Jun 08 11:16:53 CCW-HAL xdg-desktop-por[3907]: Realtime error: Could not map 
pid: Could not determine pid namespace: Could not find instance-id in process's 
/.flatpak-info
  Jun 08 11:17:01 CCW-HAL CRON[11093]: pam_unix(cron:session): session opened 
for user root(uid=0) by (uid=0)
  Jun 08 11:17:01 CCW-HAL CRON[11094]: (root) CMD (cd / && run-parts --report 
/etc/cron.hourly)
  Jun 08 11:17:01 CCW-HAL CRON[11093]: pam_unix(cron:session): session closed 
for user root
  Jun 08 11:17:06 CCW-HAL kernel: WebKitWebProces[11026]: segfault at 
55bd22ad9adc ip 55bd22ad9adc sp 7ffd1f6adbe8 error 14 likely on CPU 2 
(core 2, socket 0)
  Jun 08 11:17:06 CCW-HAL kernel: Code: Unable to access opcode bytes at 
0x55bd22ad9ab2.
  Jun 08 11:17:36 CCW-HAL gnome-shell[3803]: Window manager warning: 
WM_TRANSIENT_FOR window 0x3a02767 for 0x3a02778 window override-redirect is an 
override-redirect window and this is not correct according to the standard, so 
we'll fallback to the first non-override-redirect window 0x3a006dc.
  Jun 08 11:17:42 CCW-HAL systemd[1]: Starting systemd-tmpfiles-clean.service - 
Cleanup of Temporary Directories...
  Jun 08 11:17:42 CCW-HAL systemd[1]: systemd-tmpfiles-clean.service: 
Deactivated successfully.
  Jun 08 11:17:42 CCW-HAL systemd[1]: Finished systemd-tmpfiles-clean.service - 
Cleanup of Temporary Directories.
  Jun 08 11:17:42 CCW-HAL systemd[1]: 
run-credentials-systemd\x2dtmpfiles\x2dclean.service.mount: Deactivated 
successfully.
  Jun 08 11:18:10 CCW-HAL gnome-shell[3803]: Window manager warning: 
WM_TRANSIENT_FOR window 0x3a029e2 for 0x3a029f0 window override-redirect is an 
override-redirect window and this is not correct according to the 

[Touch-packages] [Bug 2039752] [NEW] package openssh-server 1:9.0p1-1ubuntu8.5 failed to install/upgrade: installed openssh-server package post-installation script subprocess returned error exit statu

[Markle Liu]

Public bug reported:

I don't known, but the system report the bug

ProblemType: Package
DistroRelease: Ubuntu 23.04
Package: openssh-server 1:9.0p1-1ubuntu8.5
ProcVersionSignature: Ubuntu 6.2.0-34.34-generic 6.2.16
Uname: Linux 6.2.0-34-generic x86_64
ApportVersion: 2.26.1-0ubuntu2
Architecture: amd64
CasperMD5CheckResult: unknown
Date: Thu Oct 19 09:27:02 2023
ErrorMessage: installed openssh-server package post-installation script 
subprocess returned error exit status 1
InstallationDate: Installed on 2023-10-18 (0 days ago)
InstallationMedia: Ubuntu 23.04 "Lunar Lobster" - Release amd64 (20230418)
Python3Details: /usr/bin/python3.11, Python 3.11.4, python3-minimal, 3.11.2-1
PythonDetails: N/A
RelatedPackageVersions:
 dpkg 1.21.21ubuntu1
 apt  2.6.0ubuntu0.1
SourcePackage: openssh
Title: package openssh-server 1:9.0p1-1ubuntu8.5 failed to install/upgrade: 
installed openssh-server package post-installation script subprocess returned 
error exit status 1
UpgradeStatus: No upgrade log present (probably fresh install)

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


** Tags: amd64 apport-package lunar need-duplicate-check

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

Title:
  package openssh-server 1:9.0p1-1ubuntu8.5 failed to install/upgrade:
  installed openssh-server package post-installation script subprocess
  returned error exit status 1

Status in openssh package in Ubuntu:
  New

Bug description:
  I don't known, but the system report the bug

  ProblemType: Package
  DistroRelease: Ubuntu 23.04
  Package: openssh-server 1:9.0p1-1ubuntu8.5
  ProcVersionSignature: Ubuntu 6.2.0-34.34-generic 6.2.16
  Uname: Linux 6.2.0-34-generic x86_64
  ApportVersion: 2.26.1-0ubuntu2
  Architecture: amd64
  CasperMD5CheckResult: unknown
  Date: Thu Oct 19 09:27:02 2023
  ErrorMessage: installed openssh-server package post-installation script 
subprocess returned error exit status 1
  InstallationDate: Installed on 2023-10-18 (0 days ago)
  InstallationMedia: Ubuntu 23.04 "Lunar Lobster" - Release amd64 (20230418)
  Python3Details: /usr/bin/python3.11, Python 3.11.4, python3-minimal, 3.11.2-1
  PythonDetails: N/A
  RelatedPackageVersions:
   dpkg 1.21.21ubuntu1
   apt  2.6.0ubuntu0.1
  SourcePackage: openssh
  Title: package openssh-server 1:9.0p1-1ubuntu8.5 failed to install/upgrade: 
installed openssh-server package post-installation script subprocess returned 
error exit status 1
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/openssh/+bug/2039752/+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 2039252] Re: [needs-packaging] The packages ntp and ntpsec are not equivalent

[Brian Murray]

*** This is an automated message ***

This bug is tagged needs-packaging which identifies it as a request for
a new package in Ubuntu.  As a part of the managing needs-packaging bug
reports specification,
https://wiki.ubuntu.com/QATeam/Specs/NeedsPackagingBugs, all needs-
packaging bug reports have Wishlist importance.  Subsequently, I'm
setting this bug's status to Wishlist.

** Summary changed:

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

** Changed in: ntp (Ubuntu)
   Importance: Undecided => Wishlist

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

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

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

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

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

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

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

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

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

[Touch-packages] [Bug 2038998] Re: [amdgpu] Screen artifacts/UI oddities on Wayland

[Noctis Bennington]

I just realised it happens when I'm change from 60hz to 120hz. Doesn't
mean in 120hz my monitor crash, just when I make a change in my display,
sometimes the desktop makes that strange glitch.

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

Title:
  [amdgpu] Screen artifacts/UI oddities on Wayland

Status in linux package in Ubuntu:
  Confirmed
Status in mesa package in Ubuntu:
  Confirmed

Bug description:
  Laptop is a Lenovo ThinkPad P14s Gen 2 AMD.
  Ryzen 7 PRO 5850U
  with Radeon (RX Vega 8?) integrated graphics
  16 GB RAM

  Running Ubuntu 23.10 (GNOME) from a clean install performed October 9,
  2023 from a daily-live/current .iso generated on October 4, 2023.

  Wayland
  Kernel 6.5.0-9-generic

  * * * * *

  Installed a pre-release build of Ubuntu 23.10 to my ThinkPad the other
  day, was going through setting up and testing the usual programs.

  Installed Steam through apt from the 'mantic' repositories. Installed
  Proton 8.0 and Steam Linux Runtime 3.0 (Sniper) alongside two
  compatible titles.

  Screen corruption (white and grey streaks) present in-game when GNOME
  UI elements appeared on-screen (e.g., volume, brightness, and keyboard
  backlight indicators) and omnipresent after closing either game.

  Artifacts remain on screen until log-out or reboot. Artifacts were not
  present beforehand.

  Artifacts only appeared in Wayland session; not X11/Xorg.

  I previously had been running the same games on Ubuntu 22.04 LTS
  (GNOME, Wayland) and Kubuntu 22.04 LTS (Plasma, X11/Xorg) on this
  computer without issue (kernel 6.2).

  * * * * *

  Please see subsequent posts for video/images.

  Happy to provide any other information as needed. Thanks!

  * * * * *

  ProblemType: Bug
  DistroRelease: Ubuntu 23.10
  Package: xorg 1:7.7+23ubuntu2
  ProcVersionSignature: Ubuntu 6.5.0-9.9-generic 6.5.3
  Uname: Linux 6.5.0-9-generic x86_64
  ApportVersion: 2.27.0-0ubuntu5
  Architecture: amd64
  BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
  CasperMD5CheckResult: unknown
  CompositorRunning: None
  CurrentDesktop: ubuntu:GNOME
  Date: Wed Oct 11 01:17:43 2023
  DistUpgraded: Fresh install
  DistroCodename: mantic
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes, if not too technical
  GraphicsCard:
   Advanced Micro Devices, Inc. [AMD/ATI] Cezanne [Radeon Vega Series / Radeon 
Vega Mobile Series] [1002:1638] (rev d1) (prog-if 00 [VGA controller])
     Subsystem: Lenovo Cezanne [Radeon Vega Series / Radeon Vega Mobile Series] 
[17aa:509b]
  MachineType: {report['dmi.sys.vendor']} {report['dmi.product.name']}
  ProcEnviron:
   LANG=en_US.UTF-8
   PATH=(custom, no user)
   SHELL=/bin/bash
   TERM=xterm-256color
   XDG_RUNTIME_DIR=
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-6.5.0-9-generic 
root=/dev/mapper/ubuntu--vg-ubuntu--lv ro quiet splash vt.handoff=7
  SourcePackage: xorg
  Symptom: display
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 05/15/2023
  dmi.bios.release: 1.24
  dmi.bios.vendor: LENOVO
  dmi.bios.version: R1MET54W (1.24 )
  dmi.board.asset.tag: Not Available
  dmi.board.name: 21A00068US
  dmi.board.vendor: LENOVO
  dmi.board.version: SDK0T76530 WIN
  dmi.chassis.asset.tag: No Asset Information
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: None
  dmi.ec.firmware.release: 1.24
  dmi.modalias: 
dmi:bvnLENOVO:bvrR1MET54W(1.24):bd05/15/2023:br1.24:efr1.24:svnLENOVO:pn21A00068US:pvrThinkPadP14sGen2a:rvnLENOVO:rn21A00068US:rvrSDK0T76530WIN:cvnLENOVO:ct10:cvrNone:skuLENOVO_MT_21A0_BU_Think_FM_ThinkPadP14sGen2a:
  dmi.product.family: ThinkPad P14s Gen 2a
  dmi.product.name: 21A00068US
  dmi.product.sku: LENOVO_MT_21A0_BU_Think_FM_ThinkPad P14s Gen 2a
  dmi.product.version: ThinkPad P14s Gen 2a
  dmi.sys.vendor: LENOVO
  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.115-1
  version.libgl1-mesa-dri: libgl1-mesa-dri 23.2.1-1ubuntu3
  version.libgl1-mesa-glx: libgl1-mesa-glx N/A
  version.xserver-xorg-core: xserver-xorg-core 2:21.1.7-3ubuntu2
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-3
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20210115-1
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 
1:1.0.17-2build1

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2038998/+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 2039743] [NEW] Intermittent DHCP startup failure during boot due to potential race condition in interface renaming

[Drew Hastings]

Public bug reported:

The server fails to start its network with DHCP seemingly randomly. It
can take a few reboots to bring up the network. This causes issues where
automated updates that trigger a reboot cause the server to go offline.

I've attached syslog examples of both success and failure.

My assumption is that the cause of this bug is a race condition where
systemd is not waiting on the interface renaming.

Notably, when it boots properly, it says:

"Interface is under renaming, pending initialization."

That message is not logged when it fails.

The server uses cloud-init, and the cloud image provided by Ubuntu.

Another possible explanation is the netplan configuration at
/etc/netplan/50-cloud-init.yaml is:

network:
version: 2
ethernets:
eth0:
dhcp4: true
match:
macaddress: 92:00:00:00:43:6a
set-name: eth0

Maybe set-name is redundant here, but it's the default configuration
generated by cloud-init.

ProblemType: Bug
DistroRelease: Ubuntu 20.04
Package: systemd 245.4-4ubuntu3.21
ProcVersionSignature: Ubuntu 5.4.0-164.181-generic 5.4.248
Uname: Linux 5.4.0-164-generic x86_64
ApportVersion: 2.20.11-0ubuntu27.27
Architecture: amd64
CasperMD5CheckResult: skip
Date: Wed Oct 18 16:22:57 2023
Lsusb: Bus 001 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
Lsusb-t: /:  Bus 01.Port 1: Dev 1, Class=root_hub, Driver=uhci_hcd/2p, 12M
MachineType: Slicie.com Slicie Cloud Server
ProcEnviron:
 TERM=xterm-256color
 PATH=(custom, no user)
 XDG_RUNTIME_DIR=
 LANG=C.UTF-8
 SHELL=/bin/bash
ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.4.0-164-generic 
root=UUID=f849f569-82f8-4fc0-9ac6-d4f7f7ef9609 ro console=tty1 console=ttyS0
SourcePackage: systemd
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 04/01/2014
dmi.bios.vendor: SeaBIOS
dmi.bios.version: 1.13.0-1ubuntu1.1
dmi.chassis.type: 1
dmi.chassis.vendor: QEMU
dmi.chassis.version: pc-i440fx-2.1
dmi.modalias: 
dmi:bvnSeaBIOS:bvr1.13.0-1ubuntu1.1:bd04/01/2014:svnSlicie.com:pnSlicieCloudServer:pvr1.0.0:cvnQEMU:ct1:cvrpc-i440fx-2.1:
dmi.product.name: Slicie Cloud Server
dmi.product.version: 1.0.0
dmi.sys.vendor: Slicie.com

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


** Tags: amd64 apport-bug focal third-party-packages uec-images

** Attachment added: "Relevant syslog lines for success and failure"
   https://bugs.launchpad.net/bugs/2039743/+attachment/5710951/+files/syslog.txt

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

Title:
  Intermittent DHCP startup failure during boot due to potential race
  condition in interface renaming

Status in systemd package in Ubuntu:
  New

Bug description:
  The server fails to start its network with DHCP seemingly randomly. It
  can take a few reboots to bring up the network. This causes issues
  where automated updates that trigger a reboot cause the server to go
  offline.

  I've attached syslog examples of both success and failure.

  My assumption is that the cause of this bug is a race condition where
  systemd is not waiting on the interface renaming.

  Notably, when it boots properly, it says:

  "Interface is under renaming, pending initialization."

  That message is not logged when it fails.

  The server uses cloud-init, and the cloud image provided by Ubuntu.

  Another possible explanation is the netplan configuration at
  /etc/netplan/50-cloud-init.yaml is:

  network:
  version: 2
  ethernets:
  eth0:
  dhcp4: true
  match:
  macaddress: 92:00:00:00:43:6a
  set-name: eth0

  Maybe set-name is redundant here, but it's the default configuration
  generated by cloud-init.

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: systemd 245.4-4ubuntu3.21
  ProcVersionSignature: Ubuntu 5.4.0-164.181-generic 5.4.248
  Uname: Linux 5.4.0-164-generic x86_64
  ApportVersion: 2.20.11-0ubuntu27.27
  Architecture: amd64
  CasperMD5CheckResult: skip
  Date: Wed Oct 18 16:22:57 2023
  Lsusb: Bus 001 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
  Lsusb-t: /:  Bus 01.Port 1: Dev 1, Class=root_hub, Driver=uhci_hcd/2p, 12M
  MachineType: Slicie.com Slicie Cloud Server
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=C.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.4.0-164-generic 
root=UUID=f849f569-82f8-4fc0-9ac6-d4f7f7ef9609 ro console=tty1 console=ttyS0
  SourcePackage: systemd
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 04/01/2014
  dmi.bios.vendor: SeaBIOS
  dmi.bios.version: 1.13.0-1ubuntu1.1
  dmi.chassis.type: 1
  dmi.chassis.vendor: QEMU
  dmi.chassis.version: pc-i440fx-2.1
  dmi.modalias: 

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

[Tim Richardson]

If you find a way to reproduce it, for example installing into a VM in such
a way that you can trigger it, then it would be helpful. The point is that
there are millions of standard Ubuntu installs involving a few different
kernel versions and the only reports of it are a couple here.  If a
developer can't reproduce it, they can't fix it.

On Wed, 18 Oct 2023 at 20:47, mtu <1951...@bugs.launchpad.net> wrote:

> As noted in #57, this bug _does_ occur on standard desktop installs,
> such as mine (updated from 21.10 to 22.04, thus taking firefox from .deb
> to snap).
>
> --
> You received this bug notification because you are subscribed to the bug
> report.
> https://bugs.launchpad.net/bugs/1951491
>
> Title:
>   Can't run snaps: .slice/session-1.scope is not a snap cgroup
>
> To manage notifications about this bug go to:
> https://bugs.launchpad.net/x2go/+bug/1951491/+subscriptions
>
>

-- 
Tim Richardson

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

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

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

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

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

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

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

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

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

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

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

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


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

[Touch-packages] [Bug 2038998] Re: [amdgpu] Screen artifacts/UI oddities on Wayland

[Antoine DAVID]

I'm experiencing the same issue as well.

I'm using an Asus TUF A15 with an RTX 4050.

Gnome crashes when using multiple screens with Firefox and the file
explorer.

One tip is to debug 'the frozen screen' by changing the screen order in
Settings > Display.

Best regards,

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

Title:
  [amdgpu] Screen artifacts/UI oddities on Wayland

Status in linux package in Ubuntu:
  Confirmed
Status in mesa package in Ubuntu:
  Confirmed

Bug description:
  Laptop is a Lenovo ThinkPad P14s Gen 2 AMD.
  Ryzen 7 PRO 5850U
  with Radeon (RX Vega 8?) integrated graphics
  16 GB RAM

  Running Ubuntu 23.10 (GNOME) from a clean install performed October 9,
  2023 from a daily-live/current .iso generated on October 4, 2023.

  Wayland
  Kernel 6.5.0-9-generic

  * * * * *

  Installed a pre-release build of Ubuntu 23.10 to my ThinkPad the other
  day, was going through setting up and testing the usual programs.

  Installed Steam through apt from the 'mantic' repositories. Installed
  Proton 8.0 and Steam Linux Runtime 3.0 (Sniper) alongside two
  compatible titles.

  Screen corruption (white and grey streaks) present in-game when GNOME
  UI elements appeared on-screen (e.g., volume, brightness, and keyboard
  backlight indicators) and omnipresent after closing either game.

  Artifacts remain on screen until log-out or reboot. Artifacts were not
  present beforehand.

  Artifacts only appeared in Wayland session; not X11/Xorg.

  I previously had been running the same games on Ubuntu 22.04 LTS
  (GNOME, Wayland) and Kubuntu 22.04 LTS (Plasma, X11/Xorg) on this
  computer without issue (kernel 6.2).

  * * * * *

  Please see subsequent posts for video/images.

  Happy to provide any other information as needed. Thanks!

  * * * * *

  ProblemType: Bug
  DistroRelease: Ubuntu 23.10
  Package: xorg 1:7.7+23ubuntu2
  ProcVersionSignature: Ubuntu 6.5.0-9.9-generic 6.5.3
  Uname: Linux 6.5.0-9-generic x86_64
  ApportVersion: 2.27.0-0ubuntu5
  Architecture: amd64
  BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
  CasperMD5CheckResult: unknown
  CompositorRunning: None
  CurrentDesktop: ubuntu:GNOME
  Date: Wed Oct 11 01:17:43 2023
  DistUpgraded: Fresh install
  DistroCodename: mantic
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes, if not too technical
  GraphicsCard:
   Advanced Micro Devices, Inc. [AMD/ATI] Cezanne [Radeon Vega Series / Radeon 
Vega Mobile Series] [1002:1638] (rev d1) (prog-if 00 [VGA controller])
     Subsystem: Lenovo Cezanne [Radeon Vega Series / Radeon Vega Mobile Series] 
[17aa:509b]
  MachineType: {report['dmi.sys.vendor']} {report['dmi.product.name']}
  ProcEnviron:
   LANG=en_US.UTF-8
   PATH=(custom, no user)
   SHELL=/bin/bash
   TERM=xterm-256color
   XDG_RUNTIME_DIR=
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-6.5.0-9-generic 
root=/dev/mapper/ubuntu--vg-ubuntu--lv ro quiet splash vt.handoff=7
  SourcePackage: xorg
  Symptom: display
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 05/15/2023
  dmi.bios.release: 1.24
  dmi.bios.vendor: LENOVO
  dmi.bios.version: R1MET54W (1.24 )
  dmi.board.asset.tag: Not Available
  dmi.board.name: 21A00068US
  dmi.board.vendor: LENOVO
  dmi.board.version: SDK0T76530 WIN
  dmi.chassis.asset.tag: No Asset Information
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: None
  dmi.ec.firmware.release: 1.24
  dmi.modalias: 
dmi:bvnLENOVO:bvrR1MET54W(1.24):bd05/15/2023:br1.24:efr1.24:svnLENOVO:pn21A00068US:pvrThinkPadP14sGen2a:rvnLENOVO:rn21A00068US:rvrSDK0T76530WIN:cvnLENOVO:ct10:cvrNone:skuLENOVO_MT_21A0_BU_Think_FM_ThinkPadP14sGen2a:
  dmi.product.family: ThinkPad P14s Gen 2a
  dmi.product.name: 21A00068US
  dmi.product.sku: LENOVO_MT_21A0_BU_Think_FM_ThinkPad P14s Gen 2a
  dmi.product.version: ThinkPad P14s Gen 2a
  dmi.sys.vendor: LENOVO
  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.115-1
  version.libgl1-mesa-dri: libgl1-mesa-dri 23.2.1-1ubuntu3
  version.libgl1-mesa-glx: libgl1-mesa-glx N/A
  version.xserver-xorg-core: xserver-xorg-core 2:21.1.7-3ubuntu2
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-3
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20210115-1
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 
1:1.0.17-2build1

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2038998/+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 2034986] Re: some text became unreadable during a distribution upgrade

[Launchpad Bug Tracker]

This bug was fixed in the package ubuntu-release-upgrader - 1:23.04.7

---
ubuntu-release-upgrader (1:23.04.7) lunar; urgency=medium

  * do-release-upgrade: pass XDG_CURRENT_DESKTOP env var (LP: #2034986)
  * Run pre-build.sh: updating po files, mirrors, and demotions.

 -- Nick Rosbrook   Thu, 12 Oct 2023 10:52:01 -0400

** Changed in: ubuntu-release-upgrader (Ubuntu Lunar)
   Status: Fix Committed => Fix Released

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

Title:
  some text became unreadable during a distribution upgrade

Status in Cinnamon:
  New
Status in Ubuntu MATE:
  New
Status in ubuntu-meta package in Ubuntu:
  Fix Released
Status in ubuntu-release-upgrader package in Ubuntu:
  In Progress
Status in ubuntu-release-upgrader source package in Jammy:
  Fix Committed
Status in ubuntu-release-upgrader source package in Lunar:
  Fix Released
Status in ubuntu-meta source package in Mantic:
  Fix Released
Status in ubuntu-release-upgrader source package in Mantic:
  In Progress

Bug description:
  [ Impact ]

   * On Ubuntu Mate with the Lunar series, when running
     ubuntu-release-upgrader, the displayed font of running
     applications (including the upgrader) becomes very corrupted.

   * This is not just a display problem, it is also a functional one.
     The release upgrader will have text corrupted to the point
     where a dialog asks a decision, and displays two buttons, but the
     text is unreadable and one has to guess which button is the one
     that carries out their desired action.

   * In the early parts of the upgrader tool, users are told in bold:
     "To prevent data loss close all open applications and documents."
     This is just before the "Start Upgrade" button is available.
     But they may not do so.  Many applications may have a corrupted
     font.

   * To address this, an additional environment variable is being
     passed along to pkexec, XDG_CURRENT_DESKTOP, as this is the
     critical criteria for making the Mate version of the fix work.

   * Also in the change are
     * an update to tests
 * from pre-build.sh
       * an update of the mirrors.cfg, adding and removing several
 mirrors
       * a refresh of the po files

  [ Test Plan ]

   * acquire an Ubuntu Mate environment running Ubuntu Lunar on amd64

   * as user, run "update-manager -d"

   * monitor the "Distribution Upgrade" screen.  During the "Installing
     the upgrades" step (and mind that this step will be long), observe
     the text of the "Distribution Upgrade" screen and verify that the
     font does not corrupt.

   * Repeat the above for Ubuntu Desktop

  [ Where problems could occur ]

   * We are changing, at release time, ubuntu-release upgrader.  If we
     are careless, we could regress upgrades for a wider group of users
     than just Ubuntu Mate.  That said, it is believed that passing the
     additional XDG_CURRENT_DESKTOP variable is relatively low risk.

  [ Other Info ]

   * TBD

  ---

  Original description:

  I was upgrading from Lunar to Mantic the other day and left a couple
  of applications open during the upgrade process. During the upgrade
  the text in audacious became unreadable (I'll attach a screenshot) and
  I seem to recall the title bar of Firefox being unreadable but the
  contents of web pages still being readable.

  ProblemType: Bug
  DistroRelease: Ubuntu 23.10
  Package: ubuntu-release-upgrader-core 1:23.10.5
  ProcVersionSignature: Ubuntu 6.5.0-4.4-generic 6.5.0
  Uname: Linux 6.5.0-4-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia zfs
  ApportVersion: 2.27.0-0ubuntu2
  Architecture: amd64
  CasperMD5CheckResult: unknown
  CrashDB: ubuntu
  CurrentDesktop: ubuntu:GNOME
  Date: Fri Sep  8 15:39:27 2023
  InstallationDate: Installed on 2018-08-10 (1855 days ago)
  InstallationMedia: Ubuntu-Server 18.04.1 LTS "Bionic Beaver" - Release amd64 
(20180725)
  PackageArchitecture: all
  SourcePackage: ubuntu-release-upgrader
  Symptom: ubuntu-release-upgrader
  UpgradeStatus: Upgraded to mantic on 2023-09-06 (2 days ago)
  VarLogDistupgradeAptclonesystemstate.tar.gz: Error: command ['pkexec', 'cat', 
'/var/log/dist-upgrade/apt-clone_system_state.tar.gz'] failed with exit code 
126: Error executing command as another user: Request dismissed
  VarLogDistupgradeTermlog:

  mtime.conffile..etc.update-manager.meta-release:
  2021-05-27T16:30:16.970490

To manage notifications about this bug go to:
https://bugs.launchpad.net/cinnamon-project/+bug/2034986/+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 2034986] Update Released

[Brian Murray]

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

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

Title:
  some text became unreadable during a distribution upgrade

Status in Cinnamon:
  New
Status in Ubuntu MATE:
  New
Status in ubuntu-meta package in Ubuntu:
  Fix Released
Status in ubuntu-release-upgrader package in Ubuntu:
  In Progress
Status in ubuntu-release-upgrader source package in Jammy:
  Fix Committed
Status in ubuntu-release-upgrader source package in Lunar:
  Fix Released
Status in ubuntu-meta source package in Mantic:
  Fix Released
Status in ubuntu-release-upgrader source package in Mantic:
  In Progress

Bug description:
  [ Impact ]

   * On Ubuntu Mate with the Lunar series, when running
     ubuntu-release-upgrader, the displayed font of running
     applications (including the upgrader) becomes very corrupted.

   * This is not just a display problem, it is also a functional one.
     The release upgrader will have text corrupted to the point
     where a dialog asks a decision, and displays two buttons, but the
     text is unreadable and one has to guess which button is the one
     that carries out their desired action.

   * In the early parts of the upgrader tool, users are told in bold:
     "To prevent data loss close all open applications and documents."
     This is just before the "Start Upgrade" button is available.
     But they may not do so.  Many applications may have a corrupted
     font.

   * To address this, an additional environment variable is being
     passed along to pkexec, XDG_CURRENT_DESKTOP, as this is the
     critical criteria for making the Mate version of the fix work.

   * Also in the change are
     * an update to tests
 * from pre-build.sh
       * an update of the mirrors.cfg, adding and removing several
 mirrors
       * a refresh of the po files

  [ Test Plan ]

   * acquire an Ubuntu Mate environment running Ubuntu Lunar on amd64

   * as user, run "update-manager -d"

   * monitor the "Distribution Upgrade" screen.  During the "Installing
     the upgrades" step (and mind that this step will be long), observe
     the text of the "Distribution Upgrade" screen and verify that the
     font does not corrupt.

   * Repeat the above for Ubuntu Desktop

  [ Where problems could occur ]

   * We are changing, at release time, ubuntu-release upgrader.  If we
     are careless, we could regress upgrades for a wider group of users
     than just Ubuntu Mate.  That said, it is believed that passing the
     additional XDG_CURRENT_DESKTOP variable is relatively low risk.

  [ Other Info ]

   * TBD

  ---

  Original description:

  I was upgrading from Lunar to Mantic the other day and left a couple
  of applications open during the upgrade process. During the upgrade
  the text in audacious became unreadable (I'll attach a screenshot) and
  I seem to recall the title bar of Firefox being unreadable but the
  contents of web pages still being readable.

  ProblemType: Bug
  DistroRelease: Ubuntu 23.10
  Package: ubuntu-release-upgrader-core 1:23.10.5
  ProcVersionSignature: Ubuntu 6.5.0-4.4-generic 6.5.0
  Uname: Linux 6.5.0-4-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia zfs
  ApportVersion: 2.27.0-0ubuntu2
  Architecture: amd64
  CasperMD5CheckResult: unknown
  CrashDB: ubuntu
  CurrentDesktop: ubuntu:GNOME
  Date: Fri Sep  8 15:39:27 2023
  InstallationDate: Installed on 2018-08-10 (1855 days ago)
  InstallationMedia: Ubuntu-Server 18.04.1 LTS "Bionic Beaver" - Release amd64 
(20180725)
  PackageArchitecture: all
  SourcePackage: ubuntu-release-upgrader
  Symptom: ubuntu-release-upgrader
  UpgradeStatus: Upgraded to mantic on 2023-09-06 (2 days ago)
  VarLogDistupgradeAptclonesystemstate.tar.gz: Error: command ['pkexec', 'cat', 
'/var/log/dist-upgrade/apt-clone_system_state.tar.gz'] failed with exit code 
126: Error executing command as another user: Request dismissed
  VarLogDistupgradeTermlog:

  mtime.conffile..etc.update-manager.meta-release:
  2021-05-27T16:30:16.970490

To manage notifications about this bug go to:
https://bugs.launchpad.net/cinnamon-project/+bug/2034986/+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 2039611] Re: [SRU] Fix fcc-unlock script for Lenovo X13s

[Ubuntu Foundations Team Bug Bot]

The attachment "modemmanager-1.20.6-1ubuntu2.patch" seems to be a
debdiff.  The ubuntu-sponsors team has been subscribed to the bug report
so that they can review and hopefully sponsor the debdiff.  If the
attachment isn't a patch, please remove the "patch" flag from the
attachment, remove the "patch" tag, and if you are member of the
~ubuntu-sponsors, unsubscribe the team.

[This is an automated message performed by a Launchpad user owned by
~brian-murray, for any issue please contact him.]

** Tags added: patch

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

Title:
   [SRU] Fix fcc-unlock script for Lenovo X13s

Status in modemmanager package in Ubuntu:
  New

Bug description:
  [ Impact ]

  Some of the Lenovo X13s laptop SKUs, based on the Qualcomm Snapdragon
  8cx, come with an integrated 4G/5G modem. The modem on the X13s is
  manufactured by foxconn, and is based on the Qualcomm Snapdragon X55
  PCIe modem.

  Here is the output of mmcli -m 0 on an X13s

Hardware  |manufacturer: foxconn
  |   model: Qualcomm Snapdragon X55 5G
  |   firmware revision: T99W175.F0.6.0.0.6.OG.005
  |  045  1  [Feb 03 2023 10:00:00]
   
  All Linux kernel drivers are upstream to support this data modem, and 
included in the Ubuntu kernel for mantic. The support for this modem is also 
merged in modemmanager, including the fcc-unlock script for this modem model 
(https://gitlab.freedesktop.org/mobile-broadband/ModemManager/-/commit/ac06052b97cc02e60ae1ed7a551727b3c14d6a22).
 

  We are however missing the symlink for the specific PCIe ID link
  reported on the X13s for this modem, which is shown by lspci as:

  0004:01:00.0 Wireless controller [0d40]: Foxconn International, Inc.
  T99W175 5G Modem [Snapdragon X55] [105b:e0c3]

  This is already fixed upstream with
  https://gitlab.freedesktop.org/mobile-
  broadband/ModemManager/-/commit/8061bcd9c03c26946b6fa3356313e069203f8838.

  With the backport of this patch the modem on the X13S can be enabled
  by laptop users using the fcc-unlock generic guidelines. And mobile
  broadband is working out of the box. Without it, the modem won't work.

  
  [ Test Plan ]

  Without the ability to FCC unlock this modem model, any attempt to
  enable/start the modem will fail / stall, as detailed on
  https://modemmanager.org/docs/modemmanager/fcc-unlock/.

  With this backport/fix, the Ubuntu Mobile network settings/UI can be
  used to enabled the modem, unlock the SIM card and connect to the
  4G/5G network (assuming the user has a SIM card with an appropriate
  data plan).

  
  [ Where problems could occur ]

  The patch is fairly isolated change. The purpose of this change is to
  create an additional symlink in /usr/share/ModemManager/fcc-
  unlock.available.d/ whose name is the PCIe ID of this specific device.
  PCIe IDs are documented here: https://cateee.net/lkddb/web-
  lkddb/MHI_BUS.html.

  Also links in this folder have no effect on the system, unless the
  user manually enable the appropriate fcc unlock script, typically by
  adding a link in /etc/ModemManager/fcc-unlock.d/ to the appropriate
  modem model script.

  [ Other Info ]
   
  I am working on a debdiff, and will upload shortly

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/modemmanager/+bug/2039611/+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 2039712] [NEW] Two critical CVEs in zbar

[Remi Meier]

*** This bug is a security vulnerability ***

Public security bug reported:

There are two CVEs with a score of 9.8 CRITICAL published on 29-08-2023:

* https://nvd.nist.gov/vuln/detail/CVE-2023-40889
* https://nvd.nist.gov/vuln/detail/CVE-2023-40890

No new release seems to be available that fixes these vulnerabilities.
The latest package version seems to be zbar-tools (0.23.92-7).

Additional information:

~ $ lsb_release -rd
No LSB modules are available.
Description:Ubuntu 23.04
Release:23.04
~ $ apt-cache policy zbar-tools
zbar-tools:
  Installed: 0.23.92-7
  Candidate: 0.23.92-7
  Version table:
 *** 0.23.92-7 500
500 http://ch.archive.ubuntu.com/ubuntu lunar/universe amd64 Packages
100 /var/lib/dpkg/status

# Expected

No CVE

# Actual

There are two known CVEs

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

** Description changed:

  There are two CVEs with a score of 9.8 CRITICAL published on 29-08-2023:
  
  * https://nvd.nist.gov/vuln/detail/CVE-2023-40889
  * https://nvd.nist.gov/vuln/detail/CVE-2023-40890
  
- Now new release seems to be available that fixes these vulnerabilities.
- The latest package version seems to be zbar-tools (0.23-1.3).
- 
+ No new release seems to be available that fixes these vulnerabilities.
+ The latest package version seems to be zbar-tools (0.23.92-7).
  
  Additional information:
  
  ~ $ lsb_release -rd
  No LSB modules are available.
  Description:  Ubuntu 23.04
  Release:  23.04
- ~ $ apt-cache policy zbar-tools 
+ ~ $ apt-cache policy zbar-tools
  zbar-tools:
-   Installed: 0.23.92-7
-   Candidate: 0.23.92-7
-   Version table:
-  *** 0.23.92-7 500
- 500 http://ch.archive.ubuntu.com/ubuntu lunar/universe amd64 Packages
- 100 /var/lib/dpkg/status
+   Installed: 0.23.92-7
+   Candidate: 0.23.92-7
+   Version table:
+  *** 0.23.92-7 500
+ 500 http://ch.archive.ubuntu.com/ubuntu lunar/universe amd64 Packages
+ 100 /var/lib/dpkg/status
  
  # Expected
  
  No CVE
  
  # Actual
  
  There are two known CVEs

** CVE added: https://cve.mitre.org/cgi-bin/cvename.cgi?name=2023-40890

** CVE added: https://cve.mitre.org/cgi-bin/cvename.cgi?name=2023-40889

** Information type changed from Private Security to Public Security

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

Title:
  Two critical CVEs in zbar

Status in zbar package in Ubuntu:
  New

Bug description:
  There are two CVEs with a score of 9.8 CRITICAL published on
  29-08-2023:

  * https://nvd.nist.gov/vuln/detail/CVE-2023-40889
  * https://nvd.nist.gov/vuln/detail/CVE-2023-40890

  No new release seems to be available that fixes these vulnerabilities.
  The latest package version seems to be zbar-tools (0.23.92-7).

  Additional information:

  ~ $ lsb_release -rd
  No LSB modules are available.
  Description:  Ubuntu 23.04
  Release:  23.04
  ~ $ apt-cache policy zbar-tools
  zbar-tools:
    Installed: 0.23.92-7
    Candidate: 0.23.92-7
    Version table:
   *** 0.23.92-7 500
  500 http://ch.archive.ubuntu.com/ubuntu lunar/universe amd64 Packages
  100 /var/lib/dpkg/status

  # Expected

  No CVE

  # Actual

  There are two known CVEs

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/zbar/+bug/2039712/+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 1914875] Re: Use of uninitialized value $ret in string eq at /usr/share/perl5/Debconf/FrontEnd/Passthrough.pm line 134.

[Athos Ribeiro]

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

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

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

Title:
  Use of uninitialized value $ret in string eq at
  /usr/share/perl5/Debconf/FrontEnd/Passthrough.pm line 134.

Status in debconf package in Ubuntu:
  Confirmed
Status in glibc package in Ubuntu:
  Invalid
Status in samba package in Ubuntu:
  Invalid
Status in sssd package in Ubuntu:
  Invalid
Status in tzdata package in Ubuntu:
  Invalid

Bug description:
  Some error message popped up. Everything seems normal still.

  ProblemType: Package
  DistroRelease: Ubuntu 20.10
  Package: libpam-sss:amd64 2.3.1-3ubuntu3
  ProcVersionSignature: Ubuntu 5.8.0-41.46-generic 5.8.18
  Uname: Linux 5.8.0-41-generic x86_64
  ApportVersion: 2.20.11-0ubuntu50.5
  Architecture: amd64
  CasperMD5CheckResult: skip
  Date: Sat Feb  6 16:42:33 2021
  DuplicateSignature:
   package:libpam-sss:amd64:2.3.1-3ubuntu3
   Setting up libpam-sss:amd64 (2.3.1-3ubuntu3) ...
   Use of uninitialized value $ret in string eq at 
/usr/share/perl5/Debconf/FrontEnd/Passthrough.pm line 134.
   dpkg: error processing package libpam-sss:amd64 (--configure):
installed libpam-sss:amd64 package post-installation script subprocess 
returned error exit status 128
  ErrorMessage: installed libpam-sss:amd64 package post-installation script 
subprocess returned error exit status 128
  InstallationDate: Installed on 2020-12-14 (54 days ago)
  InstallationMedia: Ubuntu 20.10 "Groovy Gorilla" - Release amd64 (20201022)
  Python3Details: /usr/bin/python3.8, Python 3.8.6, python3-minimal, 
3.8.6-0ubuntu1
  PythonDetails: N/A
  RelatedPackageVersions:
   dpkg 1.20.5ubuntu2
   apt  2.1.10ubuntu0.2
  SourcePackage: sssd
  Title: package libpam-sss:amd64 2.3.1-3ubuntu3 failed to install/upgrade: 
installed libpam-sss:amd64 package post-installation script subprocess returned 
error exit status 128
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/debconf/+bug/1914875/+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 2034986] Re: some text became unreadable during a distribution upgrade

[Gunnar Hjalmarsson]

@Michael: Then you hadn't installed version version 1:23.04.7 of ubuntu-
release-upgrader first, right? Please compare comment #44.

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

Title:
  some text became unreadable during a distribution upgrade

Status in Cinnamon:
  New
Status in Ubuntu MATE:
  New
Status in ubuntu-meta package in Ubuntu:
  Fix Released
Status in ubuntu-release-upgrader package in Ubuntu:
  In Progress
Status in ubuntu-release-upgrader source package in Jammy:
  Fix Committed
Status in ubuntu-release-upgrader source package in Lunar:
  Fix Committed
Status in ubuntu-meta source package in Mantic:
  Fix Released
Status in ubuntu-release-upgrader source package in Mantic:
  In Progress

Bug description:
  [ Impact ]

   * On Ubuntu Mate with the Lunar series, when running
     ubuntu-release-upgrader, the displayed font of running
     applications (including the upgrader) becomes very corrupted.

   * This is not just a display problem, it is also a functional one.
     The release upgrader will have text corrupted to the point
     where a dialog asks a decision, and displays two buttons, but the
     text is unreadable and one has to guess which button is the one
     that carries out their desired action.

   * In the early parts of the upgrader tool, users are told in bold:
     "To prevent data loss close all open applications and documents."
     This is just before the "Start Upgrade" button is available.
     But they may not do so.  Many applications may have a corrupted
     font.

   * To address this, an additional environment variable is being
     passed along to pkexec, XDG_CURRENT_DESKTOP, as this is the
     critical criteria for making the Mate version of the fix work.

   * Also in the change are
     * an update to tests
 * from pre-build.sh
       * an update of the mirrors.cfg, adding and removing several
 mirrors
       * a refresh of the po files

  [ Test Plan ]

   * acquire an Ubuntu Mate environment running Ubuntu Lunar on amd64

   * as user, run "update-manager -d"

   * monitor the "Distribution Upgrade" screen.  During the "Installing
     the upgrades" step (and mind that this step will be long), observe
     the text of the "Distribution Upgrade" screen and verify that the
     font does not corrupt.

   * Repeat the above for Ubuntu Desktop

  [ Where problems could occur ]

   * We are changing, at release time, ubuntu-release upgrader.  If we
     are careless, we could regress upgrades for a wider group of users
     than just Ubuntu Mate.  That said, it is believed that passing the
     additional XDG_CURRENT_DESKTOP variable is relatively low risk.

  [ Other Info ]

   * TBD

  ---

  Original description:

  I was upgrading from Lunar to Mantic the other day and left a couple
  of applications open during the upgrade process. During the upgrade
  the text in audacious became unreadable (I'll attach a screenshot) and
  I seem to recall the title bar of Firefox being unreadable but the
  contents of web pages still being readable.

  ProblemType: Bug
  DistroRelease: Ubuntu 23.10
  Package: ubuntu-release-upgrader-core 1:23.10.5
  ProcVersionSignature: Ubuntu 6.5.0-4.4-generic 6.5.0
  Uname: Linux 6.5.0-4-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia zfs
  ApportVersion: 2.27.0-0ubuntu2
  Architecture: amd64
  CasperMD5CheckResult: unknown
  CrashDB: ubuntu
  CurrentDesktop: ubuntu:GNOME
  Date: Fri Sep  8 15:39:27 2023
  InstallationDate: Installed on 2018-08-10 (1855 days ago)
  InstallationMedia: Ubuntu-Server 18.04.1 LTS "Bionic Beaver" - Release amd64 
(20180725)
  PackageArchitecture: all
  SourcePackage: ubuntu-release-upgrader
  Symptom: ubuntu-release-upgrader
  UpgradeStatus: Upgraded to mantic on 2023-09-06 (2 days ago)
  VarLogDistupgradeAptclonesystemstate.tar.gz: Error: command ['pkexec', 'cat', 
'/var/log/dist-upgrade/apt-clone_system_state.tar.gz'] failed with exit code 
126: Error executing command as another user: Request dismissed
  VarLogDistupgradeTermlog:

  mtime.conffile..etc.update-manager.meta-release:
  2021-05-27T16:30:16.970490

To manage notifications about this bug go to:
https://bugs.launchpad.net/cinnamon-project/+bug/2034986/+subscriptions


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

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

[Lukas Märdian]

I tested network-manager 1.44.2-1ubuntu1.1 inside a Mantic LXD
container. Package installation/upgrade and Netplan migration of (valid)
connection profiles worked nicely, according to the "Test Plan":


# Previous version of NM is installed
root@mm-nm-sru:~# dpkg -l network-manager
Desired=Unknown/Install/Remove/Purge/Hold
| Status=Not/Inst/Conf-files/Unpacked/halF-conf/Half-inst/trig-aWait/Trig-pend
|/ Err?=(none)/Reinst-required (Status,Err: uppercase=bad)
||/ NameVersion Architecture Description
+++-===-===--=
ii  network-manager 1.44.2-1ubuntu1 amd64network management framework 
(daemon and userspace tools)

# Creating test files
root@mm-nm-sru:~# cat /etc/NetworkManager/system-connections/UPTOWN.guests
[connection]
id=UPTOWN.guests
uuid=491fa5c8-68ef-4140-8679-dca422f5c262
type=wifi

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

[ipv6]
method=auto

[ipv4]
method=auto
root@mm-nm-sru:~# cat /etc/NetworkManager/system-connections/aaaUPTOWN
[connection]
id=aaaUPTOWN
uuid=491fa5c8-68ef---dca422f5c262
type=wifi

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

[ipv6]
method=auto

[ipv4]
method=auto
root@mm-nm-sru:~# sudo chmod 600 /etc/NetworkManager/system-connections/*UPTOWN*

# Valid connection profiles are loaded into the old NM version as keyfiles in 
/etc/NetworkManager/
root@mm-nm-sru:~# ls -la /etc/NetworkManager/system-connections/
total 16
drwxr-xr-x 2 root root 4096 Oct 18 13:11 .
drwxr-xr-x 7 root root 4096 Oct 18 13:11 ..
-rw--- 1 root root  199 Oct 18 13:11 UPTOWN.guests
-rw--- 1 root root  191 Oct 18 13:11 aaaUPTOWN
root@mm-nm-sru:~# sudo nmcli con reload  
root@mm-nm-sru:~# nmcli c
NAME   UUID  TYPE  DEVICE 
aaaUPTOWN  491fa5c8-68ef---dca422f5c262  wifi  -- 


# Upgrade to SRU version of NetworkManager
root@mm-nm-sru:~# vim /etc/apt/sources.list # enable -proposed
root@mm-nm-sru:~# apt update && apt install -t mantic-proposed network-manager
Hit:1 http://archive.ubuntu.com/ubuntu mantic InRelease
Hit:2 http://archive.ubuntu.com/ubuntu mantic-updates InRelease
Get:3 http://archive.ubuntu.com/ubuntu mantic-proposed InRelease [256 kB]
Hit:4 http://security.ubuntu.com/ubuntu mantic-security InRelease   
 
Hit:5 http://archive.ubuntu.com/ubuntu mantic-backports InRelease
Get:6 http://archive.ubuntu.com/ubuntu mantic-proposed/main amd64 Packages 
[9428 B]
Get:7 http://archive.ubuntu.com/ubuntu mantic-proposed/main Translation-en 
[3480 B]
Get:8 http://archive.ubuntu.com/ubuntu mantic-proposed/main amd64 DEP-11 
Metadata [7604 B]
Get:9 http://archive.ubuntu.com/ubuntu mantic-proposed/main amd64 c-n-f 
Metadata [292 B]
Get:10 http://archive.ubuntu.com/ubuntu mantic-proposed/restricted amd64 c-n-f 
Metadata [116 B]
Fetched 277 kB in 1s (532 kB/s)  
Reading package lists... Done
Building dependency tree... Done
Reading state information... Done
3 packages can be upgraded. Run 'apt list --upgradable' to see them.
Reading package lists... Done
Building dependency tree... Done
Reading state information... Done
The following additional packages will be installed:
  libnm0
Suggested packages:
  avahi-autoipd libteam-utils
The following packages will be upgraded:
  libnm0 network-manager
2 upgraded, 0 newly installed, 0 to remove and 5 not upgraded.
Need to get 2809 kB of archives.
After this operation, 0 B of additional disk space will be used.
Do you want to continue? [Y/n] 
Get:1 http://archive.ubuntu.com/ubuntu mantic-proposed/main amd64 
network-manager amd64 1.44.2-1ubuntu1.1 [2331 kB]
Get:2 http://archive.ubuntu.com/ubuntu mantic-proposed/main amd64 libnm0 amd64 
1.44.2-1ubuntu1.1 [478 kB]
Fetched 2809 kB in 1s (2511 kB/s)
(Reading database ... 33906 files and directories currently installed.)
Preparing to unpack .../network-manager_1.44.2-1ubuntu1.1_amd64.deb ...
Unpacking network-manager (1.44.2-1ubuntu1.1) over (1.44.2-1ubuntu1) ...
Preparing to unpack .../libnm0_1.44.2-1ubuntu1.1_amd64.deb ...
Unpacking libnm0:amd64 (1.44.2-1ubuntu1.1) over (1.44.2-1ubuntu1) ...
Setting up libnm0:amd64 (1.44.2-1ubuntu1.1) ...

#
# Here is the relevant NetworkManager Netplan migration.
# The invalid UPTOWN.guests file is skipped
# The valid aaaUPTOWN profile is migrated
#
Setting up network-manager (1.44.2-1ubuntu1.1) ...
Error: 491fa5c8-68ef-4140-8679-dca422f5c262 - no such connection profile.
SKIP: UPTOWN.guests (491fa5c8-68ef-4140-8679-dca422f5c262) unknown to 
NetworkManager.
Migrating aaaUPTOWN (491fa5c8-68ef---dca422f5c262) to /etc/netplan
Processing triggers for dbus (1.14.10-1ubuntu1) ...
Processing triggers for libc-bin (2.38-1ubuntu6) ...
Processing triggers for man-db (2.11.2-3) ...
Scanning processes...   

[Touch-packages] [Bug 2039611] Re: [SRU] Fix fcc-unlock script for Lenovo X13s

[Nicolas Dechesne]

** Patch added: "modemmanager-1.20.6-1ubuntu2.patch"
   
https://bugs.launchpad.net/ubuntu/+source/modemmanager/+bug/2039611/+attachment/5710761/+files/modemmanager-1.20.6-1ubuntu2.patch

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

Title:
   [SRU] Fix fcc-unlock script for Lenovo X13s

Status in modemmanager package in Ubuntu:
  New

Bug description:
  [ Impact ]

  Some of the Lenovo X13s laptop SKUs, based on the Qualcomm Snapdragon
  8cx, come with an integrated 4G/5G modem. The modem on the X13s is
  manufactured by foxconn, and is based on the Qualcomm Snapdragon X55
  PCIe modem.

  Here is the output of mmcli -m 0 on an X13s

Hardware  |manufacturer: foxconn
  |   model: Qualcomm Snapdragon X55 5G
  |   firmware revision: T99W175.F0.6.0.0.6.OG.005
  |  045  1  [Feb 03 2023 10:00:00]
   
  All Linux kernel drivers are upstream to support this data modem, and 
included in the Ubuntu kernel for mantic. The support for this modem is also 
merged in modemmanager, including the fcc-unlock script for this modem model 
(https://gitlab.freedesktop.org/mobile-broadband/ModemManager/-/commit/ac06052b97cc02e60ae1ed7a551727b3c14d6a22).
 

  We are however missing the symlink for the specific PCIe ID link
  reported on the X13s for this modem, which is shown by lspci as:

  0004:01:00.0 Wireless controller [0d40]: Foxconn International, Inc.
  T99W175 5G Modem [Snapdragon X55] [105b:e0c3]

  This is already fixed upstream with
  https://gitlab.freedesktop.org/mobile-
  broadband/ModemManager/-/commit/8061bcd9c03c26946b6fa3356313e069203f8838.

  With the backport of this patch the modem on the X13S can be enabled
  by laptop users using the fcc-unlock generic guidelines. And mobile
  broadband is working out of the box. Without it, the modem won't work.

  
  [ Test Plan ]

  Without the ability to FCC unlock this modem model, any attempt to
  enable/start the modem will fail / stall, as detailed on
  https://modemmanager.org/docs/modemmanager/fcc-unlock/.

  With this backport/fix, the Ubuntu Mobile network settings/UI can be
  used to enabled the modem, unlock the SIM card and connect to the
  4G/5G network (assuming the user has a SIM card with an appropriate
  data plan).

  
  [ Where problems could occur ]

  The patch is fairly isolated change. The purpose of this change is to
  create an additional symlink in /usr/share/ModemManager/fcc-
  unlock.available.d/ whose name is the PCIe ID of this specific device.
  PCIe IDs are documented here: https://cateee.net/lkddb/web-
  lkddb/MHI_BUS.html.

  Also links in this folder have no effect on the system, unless the
  user manually enable the appropriate fcc unlock script, typically by
  adding a link in /etc/ModemManager/fcc-unlock.d/ to the appropriate
  modem model script.

  [ Other Info ]
   
  I am working on a debdiff, and will upload shortly

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


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

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

[Jun Aruga]

Hi I am seeing this issue `search DOMAINS` on Ubuntu jammy arm64 in the
following environment.

```
$ cat /etc/os-release | grep ^VERSION
VERSION_ID="22.04"
VERSION="22.04.2 LTS (Jammy Jellyfish)"
VERSION_CODENAME=jammy

$ uname -m
aarch64

$ dpkg -S /etc/network/if-up.d/resolved 
ifupdown: /etc/network/if-up.d/resolved

$ dpkg -s ifupdown | grep ^Version
Version: 0.8.36+nmu1ubuntu3
```

I saw the "search DOMAINS" in the /etc/resolv.conf.

```
$ cat /etc/resolv.conf | grep -v ^#

nameserver NNN.NNN.NNN.NNN (masked by myself)
options edns0 trust-ad
search DOMAINS
```

Then I tried the workaround script mentioned at
https://bugs.launchpad.net/ubuntu/+source/ifupdown/+bug/1978351/comments/5
.

```
$ cat /etc/network/if-up.d/zzz-fix-domains
#!/bin/sh
statedir=/run/systemd/resolve/netif
grep -rl DOMAINS $statedir | xargs -r perl -pi -e 's/DOMAINS=DOMAINS//'
systemctl try-restart systemd-resolved || true
```

```
$ sudo chmod +x /etc/network/if-up.d/zzz-fix-domains
```

After running the `zzz-fix-domains`, the `search DOMAINS` was replaced
with `search .`.

```
$ sudo /etc/network/if-up.d/zzz-fix-domains

$ grep -v ^# /etc/resolv.conf

nameserver NNN.NNN.NNN.NNN (masked by myself)
options edns0 trust-ad
search .
```


However, when rebooting OS, the `systemd-resolved` failed to start with booting.

```
...
[  OK  ] Found device /sys/subsystem/net/devices/bond0.
[  OK  ] Started ifup for bond0.
ifup@bond0.service
[  OK  ] Started Network Configuration.
 Starting Wait for Network to be Configured...
systemd-networkd.service
 Starting Network Name Resolution...
[  OK  ] Finished Wait for Network to be Configured.
systemd-networkd-wait-online.service
[  OK  ] Started Network Name Resolution.
[  OK  ] Reached target Host and Network Name Lookups.
systemd-resolved.service
 Stopping Network Name Resolution...
[  OK  ] Stopped Network Name Resolution.
 Starting Network Name Resolution...
[  OK  ] Started Network Name Resolution.
systemd-resolved.service
[  OK  ] Finished Helper to synchronize boot up for ifupdown.
ifupdown-pre.service
 Starting Raise network interfaces...
 Stopping Network Name Resolution...
[  OK  ] Stopped Network Name Resolution.
 Starting Network Name Resolution...
[  OK  ] Started Network Name Resolution.
systemd-resolved.service
 Stopping Network Name Resolution...
[  OK  ] Stopped Network Name Resolution.
 Starting Network Name Resolution...
[  OK  ] Started Network Name Resolution.
systemd-resolved.service
 Stopping Network Name Resolution...
[  OK  ] Stopped Network Name Resolution.
 Starting Network Name Resolution...
[  OK  ] Started Network Name Resolution.
systemd-resolved.service
 Stopping Network Name Resolution...
[  OK  ] Stopped Network Name Resolution.
[FAILED] Failed to start Network Name Resolution.
See 'systemctl status systemd-resolved.service' for details.
[  OK  ] Finished Raise network interfaces.
...
```

The following log shows it failed with "Start request repeated too
quickly".

```
Oct 18 12:37:48 ruby1 systemd[1]: systemd-resolved.service: Start request 
repeated too quickly.
Oct 18 12:37:48 ruby1 systemd[1]: systemd-resolved.service: Failed with result 
'start-limit-hit'.
```


```
$ sudo systemctl status systemd-resolved.service
× systemd-resolved.service - Network Name Resolution
 Loaded: loaded (/lib/systemd/system/systemd-resolved.service; enabled; 
vendor preset: enabled)
 Active: failed (Result: start-limit-hit) since Wed 2023-10-18 12:37:48 
UTC; 20min ago
   Docs: man:systemd-resolved.service(8)
 man:org.freedesktop.resolve1(5)
 
https://www.freedesktop.org/wiki/Software/systemd/writing-network-configuration-managers
 
https://www.freedesktop.org/wiki/Software/systemd/writing-resolver-clients
Process: 2021 ExecStart=/lib/systemd/systemd-resolved (code=exited, 
status=0/SUCCESS)
   Main PID: 2021 (code=exited, status=0/SUCCESS)
 Status: "Shutting down..."
CPU: 69ms

Oct 18 12:37:47 ruby1 systemd-resolved[2021]: . IN DS 20326 8 2 
e06d44b80b8f1d39a95c0b0d7c65d08458e880409bbc683457104237c7f8ec8d
Oct 18 12:37:47 ruby1 systemd-resolved[2021]: Negative trust anchors: home.arpa 
10.in-addr.arpa 16.172.in-addr.arpa 17.172.in-addr.arpa 18.172.in-addr.arpa 
19.172.in-addr.arpa 20.172.in-a>
Oct 18 12:37:47 ruby1 systemd-resolved[2021]: Using system hostname 'ruby1'.
Oct 18 12:37:47 ruby1 systemd[1]: Started Network Name Resolution.
Oct 18 12:37:48 ruby1 systemd[1]: Stopping Network Name Resolution...
Oct 18 12:37:48 ruby1 systemd[1]: systemd-resolved.service: Deactivated 
successfully.
Oct 18 12:37:48 ruby1 systemd[1]: Stopped Network Name Resolution.
Oct 18 12:37:48 ruby1 systemd[1]: systemd-resolved.service: Start request 
repeated too quickly.
Oct 18 12:37:48 ruby1 systemd[1]: systemd-resolved.service: Failed with result 
'start-limit-hit'.
Oct 18 12:37:48 ruby1 systemd[1]: Failed to start Network Name 

[Touch-packages] [Bug 2034986] Re: some text became unreadable during a distribution upgrade

[Michael Baker]

Just now upgrading ubuntu-mate 23.04 to 23.10 and encountered the
corrupt text issues.  Screenshot attached.

** Attachment added: "corruption.png"
   
https://bugs.launchpad.net/ubuntu/+source/ubuntu-release-upgrader/+bug/2034986/+attachment/5710737/+files/corruption.png

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

Title:
  some text became unreadable during a distribution upgrade

Status in Cinnamon:
  New
Status in Ubuntu MATE:
  New
Status in ubuntu-meta package in Ubuntu:
  Fix Released
Status in ubuntu-release-upgrader package in Ubuntu:
  In Progress
Status in ubuntu-release-upgrader source package in Jammy:
  Fix Committed
Status in ubuntu-release-upgrader source package in Lunar:
  Fix Committed
Status in ubuntu-meta source package in Mantic:
  Fix Released
Status in ubuntu-release-upgrader source package in Mantic:
  In Progress

Bug description:
  [ Impact ]

   * On Ubuntu Mate with the Lunar series, when running
     ubuntu-release-upgrader, the displayed font of running
     applications (including the upgrader) becomes very corrupted.

   * This is not just a display problem, it is also a functional one.
     The release upgrader will have text corrupted to the point
     where a dialog asks a decision, and displays two buttons, but the
     text is unreadable and one has to guess which button is the one
     that carries out their desired action.

   * In the early parts of the upgrader tool, users are told in bold:
     "To prevent data loss close all open applications and documents."
     This is just before the "Start Upgrade" button is available.
     But they may not do so.  Many applications may have a corrupted
     font.

   * To address this, an additional environment variable is being
     passed along to pkexec, XDG_CURRENT_DESKTOP, as this is the
     critical criteria for making the Mate version of the fix work.

   * Also in the change are
     * an update to tests
 * from pre-build.sh
       * an update of the mirrors.cfg, adding and removing several
 mirrors
       * a refresh of the po files

  [ Test Plan ]

   * acquire an Ubuntu Mate environment running Ubuntu Lunar on amd64

   * as user, run "update-manager -d"

   * monitor the "Distribution Upgrade" screen.  During the "Installing
     the upgrades" step (and mind that this step will be long), observe
     the text of the "Distribution Upgrade" screen and verify that the
     font does not corrupt.

   * Repeat the above for Ubuntu Desktop

  [ Where problems could occur ]

   * We are changing, at release time, ubuntu-release upgrader.  If we
     are careless, we could regress upgrades for a wider group of users
     than just Ubuntu Mate.  That said, it is believed that passing the
     additional XDG_CURRENT_DESKTOP variable is relatively low risk.

  [ Other Info ]

   * TBD

  ---

  Original description:

  I was upgrading from Lunar to Mantic the other day and left a couple
  of applications open during the upgrade process. During the upgrade
  the text in audacious became unreadable (I'll attach a screenshot) and
  I seem to recall the title bar of Firefox being unreadable but the
  contents of web pages still being readable.

  ProblemType: Bug
  DistroRelease: Ubuntu 23.10
  Package: ubuntu-release-upgrader-core 1:23.10.5
  ProcVersionSignature: Ubuntu 6.5.0-4.4-generic 6.5.0
  Uname: Linux 6.5.0-4-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia zfs
  ApportVersion: 2.27.0-0ubuntu2
  Architecture: amd64
  CasperMD5CheckResult: unknown
  CrashDB: ubuntu
  CurrentDesktop: ubuntu:GNOME
  Date: Fri Sep  8 15:39:27 2023
  InstallationDate: Installed on 2018-08-10 (1855 days ago)
  InstallationMedia: Ubuntu-Server 18.04.1 LTS "Bionic Beaver" - Release amd64 
(20180725)
  PackageArchitecture: all
  SourcePackage: ubuntu-release-upgrader
  Symptom: ubuntu-release-upgrader
  UpgradeStatus: Upgraded to mantic on 2023-09-06 (2 days ago)
  VarLogDistupgradeAptclonesystemstate.tar.gz: Error: command ['pkexec', 'cat', 
'/var/log/dist-upgrade/apt-clone_system_state.tar.gz'] failed with exit code 
126: Error executing command as another user: Request dismissed
  VarLogDistupgradeTermlog:

  mtime.conffile..etc.update-manager.meta-release:
  2021-05-27T16:30:16.970490

To manage notifications about this bug go to:
https://bugs.launchpad.net/cinnamon-project/+bug/2034986/+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 2034986] Re: some text became unreadable during a distribution upgrade

[Michael Baker]

Am in the process of an Ubuntu-Mate 23.04 to 23.10 upgrade and have the
corrupted text issue.

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

Title:
  some text became unreadable during a distribution upgrade

Status in Cinnamon:
  New
Status in Ubuntu MATE:
  New
Status in ubuntu-meta package in Ubuntu:
  Fix Released
Status in ubuntu-release-upgrader package in Ubuntu:
  In Progress
Status in ubuntu-release-upgrader source package in Jammy:
  Fix Committed
Status in ubuntu-release-upgrader source package in Lunar:
  Fix Committed
Status in ubuntu-meta source package in Mantic:
  Fix Released
Status in ubuntu-release-upgrader source package in Mantic:
  In Progress

Bug description:
  [ Impact ]

   * On Ubuntu Mate with the Lunar series, when running
     ubuntu-release-upgrader, the displayed font of running
     applications (including the upgrader) becomes very corrupted.

   * This is not just a display problem, it is also a functional one.
     The release upgrader will have text corrupted to the point
     where a dialog asks a decision, and displays two buttons, but the
     text is unreadable and one has to guess which button is the one
     that carries out their desired action.

   * In the early parts of the upgrader tool, users are told in bold:
     "To prevent data loss close all open applications and documents."
     This is just before the "Start Upgrade" button is available.
     But they may not do so.  Many applications may have a corrupted
     font.

   * To address this, an additional environment variable is being
     passed along to pkexec, XDG_CURRENT_DESKTOP, as this is the
     critical criteria for making the Mate version of the fix work.

   * Also in the change are
     * an update to tests
 * from pre-build.sh
       * an update of the mirrors.cfg, adding and removing several
 mirrors
       * a refresh of the po files

  [ Test Plan ]

   * acquire an Ubuntu Mate environment running Ubuntu Lunar on amd64

   * as user, run "update-manager -d"

   * monitor the "Distribution Upgrade" screen.  During the "Installing
     the upgrades" step (and mind that this step will be long), observe
     the text of the "Distribution Upgrade" screen and verify that the
     font does not corrupt.

   * Repeat the above for Ubuntu Desktop

  [ Where problems could occur ]

   * We are changing, at release time, ubuntu-release upgrader.  If we
     are careless, we could regress upgrades for a wider group of users
     than just Ubuntu Mate.  That said, it is believed that passing the
     additional XDG_CURRENT_DESKTOP variable is relatively low risk.

  [ Other Info ]

   * TBD

  ---

  Original description:

  I was upgrading from Lunar to Mantic the other day and left a couple
  of applications open during the upgrade process. During the upgrade
  the text in audacious became unreadable (I'll attach a screenshot) and
  I seem to recall the title bar of Firefox being unreadable but the
  contents of web pages still being readable.

  ProblemType: Bug
  DistroRelease: Ubuntu 23.10
  Package: ubuntu-release-upgrader-core 1:23.10.5
  ProcVersionSignature: Ubuntu 6.5.0-4.4-generic 6.5.0
  Uname: Linux 6.5.0-4-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia zfs
  ApportVersion: 2.27.0-0ubuntu2
  Architecture: amd64
  CasperMD5CheckResult: unknown
  CrashDB: ubuntu
  CurrentDesktop: ubuntu:GNOME
  Date: Fri Sep  8 15:39:27 2023
  InstallationDate: Installed on 2018-08-10 (1855 days ago)
  InstallationMedia: Ubuntu-Server 18.04.1 LTS "Bionic Beaver" - Release amd64 
(20180725)
  PackageArchitecture: all
  SourcePackage: ubuntu-release-upgrader
  Symptom: ubuntu-release-upgrader
  UpgradeStatus: Upgraded to mantic on 2023-09-06 (2 days ago)
  VarLogDistupgradeAptclonesystemstate.tar.gz: Error: command ['pkexec', 'cat', 
'/var/log/dist-upgrade/apt-clone_system_state.tar.gz'] failed with exit code 
126: Error executing command as another user: Request dismissed
  VarLogDistupgradeTermlog:

  mtime.conffile..etc.update-manager.meta-release:
  2021-05-27T16:30:16.970490

To manage notifications about this bug go to:
https://bugs.launchpad.net/cinnamon-project/+bug/2034986/+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 2000276] Re: FIDO2 user verification impossible when using the ssh agent

[Athos Ribeiro]

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

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

Title:
  FIDO2 user verification impossible when using the ssh agent

Status in openssh package in Ubuntu:
  Triaged

Bug description:
  I am having trouble setting up FIDO2 ssh keys with my yubikey 5C NFC
  if I want to enable user verification (user presence works fine).

  
  Steps to reproduce:

  = Prep work =

  Client (kinetic):
  * generate a key that requires user verification:
$ ssh-keygen -t ed25519-sk -f ~/.ssh/id_ed25519_verify_sk -O 
verify-required -C "this key requires UV"
[provide your authenticator PIN, touch it, and add an encryption password]

  Server (jammy):
  * add id_ed25519_verify_sk.pub to authorized_keys

  = Symptoms =

  Shell 1 (w/ssh agent):

  $ eval $(ssh-agent)
  Agent pid 3279738

  $ ssh-add ~/.ssh/id_ed25519_verify_sk
  Enter passphrase for /home/aieri/.ssh/id_ed25519_verify_sk: 
  Identity added: /home/aieri/.ssh/id_ed25519_verify_sk (this key requires UV)

  $ ssh ubuntu@10.35.202.231 -i ~/.ssh/id_ed25519_verify_sk "echo FIDO2 fails\!"
  sign_and_send_pubkey: signing failed for ED25519-SK 
"/home/aieri/.ssh/id_ed25519_verify_sk" from agent: agent refused operation
  ubuntu@10.35.202.231: Permission denied (publickey).

  [note that the above is printed immediately, and that the yubikey does
  not light up]

  Shell 2 (no ssh agent):

  $ ssh ubuntu@10.35.202.231 -i ~/.ssh/id_ed25519_verify_sk "echo FIDO2 works\!"
  Enter passphrase for key '/home/aieri/.ssh/id_ed25519_verify_sk': 
  Enter PIN for ED25519-SK key /home/aieri/.ssh/id_ed25519_verify_sk: 
  Confirm user presence for key ED25519-SK 
SHA256:nhgS4c2rGtE7XKeez3rAsofrjJvsL6rmBLShZxfTXIY
  User presence confirmed
  FIDO2 works!


  NOTE: 
  * user _presence_ can be validated correctly with or without the ssh-agent: 
keys generated without `-O verify-required` work as expected (aside from bug 
1869897)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/openssh/+bug/2000276/+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 2035076] Re: Wayland - Capital accented letters not recognized

[Sebastien Bacher]

It's an upstream GNOME issue and landed a fix recently, see details on
https://bugzilla.redhat.com/show_bug.cgi?id=2240490 , it should be
included in the 45.1 updates

** Bug watch added: Red Hat Bugzilla #2240490
   https://bugzilla.redhat.com/show_bug.cgi?id=2240490

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

** Changed in: ubuntu
   Status: Confirmed => Triaged

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

** Changed in: gnome-shell (Ubuntu)
   Importance: Undecided => High

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

Title:
  Wayland - Capital accented letters not recognized

Status in gnome-shell package in Ubuntu:
  Triaged

Bug description:
  Most programs don't recognize Italian accented capital letters.
  When "Caps Lock" is on àèìòù should be written as ÀÈÌÒÙ... but for some 
reasons they are not capitalized.
  I've noticed that everything works fine using the Live session which still 
uses X11 session.

  It looks there's no problem with programs that use xwayland like Gimp
  and MarkText.

  
  WORKAROUND
  ===
  In "Settings -> Keyboard" it's possible to set a "compose key".
  For example I've selected the [Super left] key. If I want to compose È I 
press and immediately release each key:
  [Super left] + [E] + [Alt Gr] + [']

  If you want É:
  [Super left] + [E] + [']

  Do the same for the other vowels.
  ===

  ProblemType: Bug
  DistroRelease: Ubuntu 23.10
  Package: gnome-text-editor 45~beta-1
  ProcVersionSignature: Ubuntu 6.3.0-7.7-generic 6.3.5
  Uname: Linux 6.3.0-7-generic x86_64
  ApportVersion: 2.27.0-0ubuntu2
  Architecture: amd64
  CasperMD5CheckResult: pass
  CurrentDesktop: ubuntu:GNOME
  Date: Mon Sep 11 11:48:41 2023
  InstallationDate: Installed on 2023-09-07 (4 days ago)
  InstallationMedia: Ubuntu 23.10 "Mantic Minotaur" - Daily amd64 (20230906.3)
  ProcEnviron:
   LANG=it_IT.UTF-8
   PATH=(custom, no user)
   SHELL=/bin/bash
   TERM=xterm-256color
   XDG_RUNTIME_DIR=
  SourcePackage: gnome-text-editor
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/2035076/+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 2035076] Re: Wayland - Capital accented letters not recognized

[Antoine-terracol]

Same here on a French keyboard.

In a Wayland session, softwares such as Gedit, Thunderbird or Libre
Office are unable to display accented capiatals using caps-lock (but
VSCode works fine). In an X11 session everythings works as expected.

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

Title:
  Wayland - Capital accented letters not recognized

Status in gtk+3.0 package in Ubuntu:
  Confirmed

Bug description:
  Most programs don't recognize Italian accented capital letters.
  When "Caps Lock" is on àèìòù should be written as ÀÈÌÒÙ... but for some 
reasons they are not capitalized.
  I've noticed that everything works fine using the Live session which still 
uses X11 session.

  It looks there's no problem with programs that use xwayland like Gimp
  and MarkText.

  
  WORKAROUND
  ===
  In "Settings -> Keyboard" it's possible to set a "compose key".
  For example I've selected the [Super left] key. If I want to compose È I 
press and immediately release each key:
  [Super left] + [E] + [Alt Gr] + [']

  If you want É:
  [Super left] + [E] + [']

  Do the same for the other vowels.
  ===

  ProblemType: Bug
  DistroRelease: Ubuntu 23.10
  Package: gnome-text-editor 45~beta-1
  ProcVersionSignature: Ubuntu 6.3.0-7.7-generic 6.3.5
  Uname: Linux 6.3.0-7-generic x86_64
  ApportVersion: 2.27.0-0ubuntu2
  Architecture: amd64
  CasperMD5CheckResult: pass
  CurrentDesktop: ubuntu:GNOME
  Date: Mon Sep 11 11:48:41 2023
  InstallationDate: Installed on 2023-09-07 (4 days ago)
  InstallationMedia: Ubuntu 23.10 "Mantic Minotaur" - Daily amd64 (20230906.3)
  ProcEnviron:
   LANG=it_IT.UTF-8
   PATH=(custom, no user)
   SHELL=/bin/bash
   TERM=xterm-256color
   XDG_RUNTIME_DIR=
  SourcePackage: gnome-text-editor
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gtk+3.0/+bug/2035076/+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 2035076] Re: Wayland - Capital accented letters not recognized

[Launchpad Bug Tracker]

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

** Changed in: gtk+3.0 (Ubuntu)
   Status: New => Confirmed

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

Title:
  Wayland - Capital accented letters not recognized

Status in gtk+3.0 package in Ubuntu:
  Confirmed

Bug description:
  Most programs don't recognize Italian accented capital letters.
  When "Caps Lock" is on àèìòù should be written as ÀÈÌÒÙ... but for some 
reasons they are not capitalized.
  I've noticed that everything works fine using the Live session which still 
uses X11 session.

  It looks there's no problem with programs that use xwayland like Gimp
  and MarkText.

  
  WORKAROUND
  ===
  In "Settings -> Keyboard" it's possible to set a "compose key".
  For example I've selected the [Super left] key. If I want to compose È I 
press and immediately release each key:
  [Super left] + [E] + [Alt Gr] + [']

  If you want É:
  [Super left] + [E] + [']

  Do the same for the other vowels.
  ===

  ProblemType: Bug
  DistroRelease: Ubuntu 23.10
  Package: gnome-text-editor 45~beta-1
  ProcVersionSignature: Ubuntu 6.3.0-7.7-generic 6.3.5
  Uname: Linux 6.3.0-7-generic x86_64
  ApportVersion: 2.27.0-0ubuntu2
  Architecture: amd64
  CasperMD5CheckResult: pass
  CurrentDesktop: ubuntu:GNOME
  Date: Mon Sep 11 11:48:41 2023
  InstallationDate: Installed on 2023-09-07 (4 days ago)
  InstallationMedia: Ubuntu 23.10 "Mantic Minotaur" - Daily amd64 (20230906.3)
  ProcEnviron:
   LANG=it_IT.UTF-8
   PATH=(custom, no user)
   SHELL=/bin/bash
   TERM=xterm-256color
   XDG_RUNTIME_DIR=
  SourcePackage: gnome-text-editor
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gtk+3.0/+bug/2035076/+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 2039252] Re: The packages ntp and ntpsec are not equivalent

[Jonathan Ferguson]

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

** Tags added: needs-packaging

** Changed in: ntp (Debian)
   Status: Invalid => Confirmed

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

Title:
  The packages ntp and ntpsec are not equivalent

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

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

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

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

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

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

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

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

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

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

[Łukasz Zemczak]

Hello Steve, or anyone else affected,

Accepted network-manager into mantic-proposed. The package will build
now and be available at https://launchpad.net/ubuntu/+source/network-
manager/1.44.2-1ubuntu1.1 in a few hours, and then in the -proposed
repository.

Please help us by testing this new package.  See
https://wiki.ubuntu.com/Testing/EnableProposed for documentation on how
to enable and use -proposed.  Your feedback will aid us getting this
update out to other Ubuntu users.

If this package fixes the bug for you, please add a comment to this bug,
mentioning the version of the package you tested, what testing has been
performed on the package and change the tag from verification-needed-
mantic to verification-done-mantic. If it does not fix the bug for you,
please add a comment stating that, and change the tag to verification-
failed-mantic. In either case, without details of your testing we will
not be able to proceed.

Further information regarding the verification process can be found at
https://wiki.ubuntu.com/QATeam/PerformingSRUVerification .  Thank you in
advance for helping!

N.B. The updated package will be released to -updates after the bug(s)
fixed by this package have been verified and the package has been in
-proposed for a minimum of 7 days.

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

** Tags added: verification-needed verification-needed-mantic

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

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

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

Bug description:
  [ Impact ]

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

   * This will make the package installation/upgrade fail

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

  [ Test Plan ]

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

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

  [ipv6]
  method=auto

  [ipv4]
  method=auto

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

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

  [ipv6]
  method=auto

  [ipv4]
  method=auto

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

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

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

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

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

  [ Where problems could occur ]

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

  [ Other Info ]

   * Linting was 

[Touch-packages] [Bug 2039660] Re: wayland application not inputting accentuated caps characters after upgrade to 23.10

[Paul White]

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

** Package changed: wayland (Ubuntu) => mutter (Ubuntu)

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

Title:
  wayland application not inputting accentuated caps characters after
  upgrade to 23.10

Status in mutter package in Ubuntu:
  New
Status in Fedora:
  Unknown

Bug description:
  After upgrading to 23.10 from 23.04, I am unable to input accentuated
  caps chars like « É ».

  STR:
   - Configure keyboard input as french (any variant does the job it seems)
   - Make sure you are in caps lock mode
   - Type the "2 é" char on the keyboard

  Expected:
   - « É » is produced

  Actual:
   - « é » in produced

  Fun fact:
   When reproducing in the GNOME Settings app, there is an interesting behavior:
   - if you try to input « É » WITHOUT focusing first in the search field of 
the app, then the first char will be correctly produced as « É » but subsequent 
will not
   - obviously, if you try the same WITH focusing first in the search field, 
you end up in the first case

  Facts:
   - xev shows proper data arriving
   - reproduced on several wayland app (gnome-text-editor, firefox, 
gnome-settings, gedit)
   - not reproduced on xwayland (hexchat, GDB_BACKEND=x11 gedit)

  ProblemType: Bug
  DistroRelease: Ubuntu 23.10
  Package: ubuntu-release-upgrader-core 1:23.10.10
  ProcVersionSignature: Ubuntu 6.5.0-9.9-generic 6.5.3
  Uname: Linux 6.5.0-9-generic x86_64
  ApportVersion: 2.27.0-0ubuntu5
  Architecture: amd64
  CasperMD5CheckResult: pass
  CrashDB: ubuntu
  CurrentDesktop: ubuntu:GNOME
  Date: Wed Oct 18 11:57:45 2023
  InstallationDate: Installed on 2022-07-04 (471 days ago)
  InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Release amd64 
(20220419)
  PackageArchitecture: all
  ProcEnviron:
   LANG=fr_FR.UTF-8
   PATH=(custom, no user)
   SHELL=/bin/bash
   TERM=xterm-256color
   XDG_RUNTIME_DIR=
  SourcePackage: ubuntu-release-upgrader
  Symptom: release-upgrade
  UpgradeStatus: Upgraded to mantic on 2023-10-16 (2 days ago)
  VarLogDistupgradeXorgFixuplog:
   INFO:root:/usr/bin/do-release-upgrade running
   INFO:root:No xorg.conf, exiting

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/mutter/+bug/2039660/+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 2039660] [NEW] wayland application not inputting accentuated caps characters after upgrade to 23.10

[Launchpad Bug Tracker]

You have been subscribed to a public bug:

After upgrading to 23.10 from 23.04, I am unable to input accentuated
caps chars like « É ».

STR:
 - Configure keyboard input as french (any variant does the job it seems)
 - Make sure you are in caps lock mode
 - Type the "2 é" char on the keyboard

Expected:
 - « É » is produced

Actual:
 - « é » in produced

Fun fact:
 When reproducing in the GNOME Settings app, there is an interesting behavior:
 - if you try to input « É » WITHOUT focusing first in the search field of the 
app, then the first char will be correctly produced as « É » but subsequent 
will not
 - obviously, if you try the same WITH focusing first in the search field, you 
end up in the first case

Facts:
 - xev shows proper data arriving
 - reproduced on several wayland app (gnome-text-editor, firefox, 
gnome-settings, gedit)
 - not reproduced on xwayland (hexchat, GDB_BACKEND=x11 gedit)

ProblemType: Bug
DistroRelease: Ubuntu 23.10
Package: ubuntu-release-upgrader-core 1:23.10.10
ProcVersionSignature: Ubuntu 6.5.0-9.9-generic 6.5.3
Uname: Linux 6.5.0-9-generic x86_64
ApportVersion: 2.27.0-0ubuntu5
Architecture: amd64
CasperMD5CheckResult: pass
CrashDB: ubuntu
CurrentDesktop: ubuntu:GNOME
Date: Wed Oct 18 11:57:45 2023
InstallationDate: Installed on 2022-07-04 (471 days ago)
InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Release amd64 (20220419)
PackageArchitecture: all
ProcEnviron:
 LANG=fr_FR.UTF-8
 PATH=(custom, no user)
 SHELL=/bin/bash
 TERM=xterm-256color
 XDG_RUNTIME_DIR=
SourcePackage: ubuntu-release-upgrader
Symptom: release-upgrade
UpgradeStatus: Upgraded to mantic on 2023-10-16 (2 days ago)
VarLogDistupgradeXorgFixuplog:
 INFO:root:/usr/bin/do-release-upgrade running
 INFO:root:No xorg.conf, exiting

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

** Affects: fedora
 Importance: Unknown
 Status: Unknown


** Tags: amd64 apport-bug dist-upgrade mantic wayland-session
-- 
wayland application not inputting accentuated caps characters after upgrade to 
23.10
https://bugs.launchpad.net/bugs/2039660
You received this bug notification because you are a member of Ubuntu Touch 
seeded packages, which is subscribed to wayland 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 1951491] Re: Can't run snaps: .slice/session-1.scope is not a snap cgroup

[mtu]

As noted in #57, this bug _does_ occur on standard desktop installs,
such as mine (updated from 21.10 to 22.04, thus taking firefox from .deb
to snap).

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

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

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

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

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

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

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

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

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

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

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

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


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

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

[Lukas Märdian]

After restoring git history for bug #2038439 I've now uploaded this SRU
into Mantic, using the `ubuntu-mantic` branch (tag:
ubuntu/1.44.2-1ubuntu1.1):

https://launchpad.net/ubuntu/mantic/+queue?queue_state=1_text=network-
manager

** Description changed:

  [ Impact ]
  
   * A failure to query nmcli will fail the network-manager.postinst
  maintainer script (using "set -e")
  
   * This will make the package installation/upgrade fail
  
   * The fix catches the error on "ORIG_NAME=$(nmcli --get-values
  connection.id con show "$UUID")" and skips the corresponding keyfile
  with a warning message
  
  [ Test Plan ]
  
  $ sudo vim /etc/NetworkManager/system-connections/UPTOWN.guests # bad file
  [connection]
  id=UPTOWN.guests
  uuid=491fa5c8-68ef-4140-8679-dca422f5c262
  type=wifi
  
  [wifi]
  ssid=UPTOWN.guests
  mode=infrastructure
  mac-address=E0:9D:31:09:84:54
  
  [ipv6]
  method=auto
  
  [ipv4]
  method=auto
  
  $ sudo vim /etc/NetworkManager/system-connections/aaaUPTOWN # good file
  [connection]
  id=aaaUPTOWN
  uuid=491fa5c8-68ef---dca422f5c262
  type=wifi
  
  [wifi]
  ssid=aaaUPTOWN
  mode=infrastructure
  mac-address=E0:9D:31:09:84:54
  
  [ipv6]
  method=auto
  
  [ipv4]
  method=auto
  
  $ sudo chmod 600 /etc/NetworkManager/system-connections/*UPTOWN*
  $ sudo nmcli con reload
  $ ls -la /etc/NetworkManager/system-connections/
  total 32
  drwxr-xr-x 2 root root 12288 Oct 17 17:51 ./
  drwxr-xr-x 7 root root 12288 Oct 17 17:46 ../
  -rw--- 1 root root   199 Oct 17 17:05 UPTOWN.guests
  -rw--- 1 root root   191 Oct 17 17:46 aaaUPTOWN
  
  # Install network-manager from proposed
- $ apt update && apt install -t mantic-proposed network-manager # version 
1.44.0-1ubuntu2.1
+ $ apt update && apt install -t mantic-proposed network-manager # version 
1.44.2-1ubuntu1.1
  
  # Verify you don't see an error like this, breaking the pkg install
  Error: 491fa5c8-68ef-4140-8679-dca422f5c262 - no such connection profile.
  dpkg: error processing package network-manager (--configure):
   installed network-manager package post-installation script subprocess 
returned error exit status 10
  
  # Verify you see a migration log like this and the package installation is 
successful:
  Error: 491fa5c8-68ef-4140-8679-dca422f5c262 - no such connection profile.
  SKIP: UPTOWN.guests (491fa5c8-68ef-4140-8679-dca422f5c262) unknown to 
NetworkManager.
  Migrating aaaUPTOWN (491fa5c8-68ef---dca422f5c262) to /etc/netplan
  $ echo $?
  0
  
  # Verify the good profile got migrated, while the bad one remains:
  $ sudo grep -RH UPTOWN /etc/netplan/
  /etc/netplan/90-NM-491fa5c8-68ef---dca422f5c262.yaml:
"aaaUPTOWN":
  /etc/netplan/90-NM-491fa5c8-68ef---dca422f5c262.yaml:
name: "aaaUPTOWN"
  /etc/netplan/90-NM-491fa5c8-68ef---dca422f5c262.yaml:name: 
"aaaUPTOWN"
  $ ls -la /etc/NetworkManager/system-connections/
  insgesamt 28
  drwxr-xr-x 2 root root 12288 Okt 17 18:03 .
  drwxr-xr-x 7 root root 12288 Okt 17 17:46 ..
  -rw--- 1 root root   199 Okt 17 17:05 UPTOWN.guests
  
  [ Where problems could occur ]
  
   * This is touching NetworkManager's maintainer script
-  * Breaking it could lead to a broken/unconfigured NetworkManager package
-  * This could render a machine's networking unusable
-  * It could break distribution upgrades on package install/configure failure
+  * Breaking it could lead to a broken/unconfigured NetworkManager package
+  * This could render a machine's networking unusable
+  * It could break distribution upgrades on package install/configure failure
  
  [ Other Info ]
  
   * Linting was used to validate the maintainer script:
-shellcheck --shell=sh debian/network-manager.postinst
+    shellcheck --shell=sh debian/network-manager.postinst
  
  === original bug description ===
  
  lunar to mantic upgrade, exciting to see output from network-manager
  postinst migrating connections to /etc/netplan one by one.  But then:
  
  Error: 491fa5c8-68ef-4140-8679-dca422f5c262 - no such connection profile.
  dpkg: error processing package network-manager (--configure):
   installed network-manager package post-installation script subprocess 
returned error exit status 10
  
  That UUID appears in a file /etc/NetworkManager/system-
  connections/UPTOWN.guests that hasn't been touched since 2015.
  
  Contents of the file were:
  
  [connection]
  id=UPTOWN.guests
  uuid=491fa5c8-68ef-4140-8679-dca422f5c262
  type=wifi
  
  [wifi]
  ssid=UPTOWN.guests
  mode=infrastructure
  mac-address=E0:9D:31:09:84:54
  
  [ipv6]
  method=auto
  
  [ipv4]
  method=auto
  
  I've removed it from disk and the migration continued to completion.
  
  Then I got another failure on:
  
  [connection]
  id=belkin.1e4.guests
  uuid=2c77e512-f3e3-4238-b401-c94559cc6db0
  type=802-11-wireless
  
  [802-11-wireless]
  ssid=belkin.1e4.guests
  mode=infrastructure
  mac-address=00:24:D7:1F:EA:20
  
  [ipv6]
  method=auto
  
  [ipv4]
  

[Touch-packages] [Bug 2037906] Re: [Intel AX201] Bluetooth LE not working after upgrade from 22.04 to 23.10

[Grzegorz - Thulium]

ok- I just saw I needed to mark the bug as Confirmed

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

Title:
  [Intel AX201] Bluetooth LE not working after upgrade from 22.04 to
  23.10

Status in Linux Firmware:
  New
Status in bluez package in Ubuntu:
  New
Status in linux package in Ubuntu:
  Confirmed

Bug description:
  syslog:
  2023-09-20T09:32:54.138852+02:00 zaionc kernel: [   13.539860] Bluetooth: 
hci0: Waiting for firmware download to complete
  2023-09-20T09:32:54.138857+02:00 zaionc kernel: [   13.540223] Bluetooth: 
hci0: Firmware loaded in 1706498 usecs
  2023-09-20T09:32:54.138858+02:00 zaionc kernel: [   13.540278] Bluetooth: 
hci0: Waiting for device to boot
  2023-09-20T09:32:54.154894+02:00 zaionc kernel: [   13.555430] Bluetooth: 
hci0: Malformed MSFT vendor event: 0x02
  2023-09-20T09:32:54.154908+02:00 zaionc kernel: [   13.555482] Bluetooth: 
hci0: Device booted in 14872 usecs
  2023-09-20T09:32:54.154910+02:00 zaionc kernel: [   13.555913] Bluetooth: 
hci0: Found Intel DDC parameters: intel/ibt-19-0-4.ddc
  2023-09-20T09:32:54.158856+02:00 zaionc kernel: [   13.558300] Bluetooth: 
hci0: Applying Intel DDC parameters completed
  2023-09-20T09:32:54.158859+02:00 zaionc kernel: [   13.559326] Bluetooth: 
hci0: Firmware revision 0.4 build 249 week 27 2023

  lshw:
    *-usb:5
     description: Bluetooth wireless interface
     product: AX201 Bluetooth
     vendor: Intel Corp.
     physical id: a
     bus info: usb@3:a
     version: 0.02
     capabilities: bluetooth usb-2.01
     configuration: driver=btusb maxpower=100mA speed=12Mbit/s

  root@zaionc:~# hcitool lescan
  Set scan parameters failed: Input/output error

  At first bluetooth stopped working at all due to Ubuntu bug = missing
  firmware. It was fixed recently and now the bluetooth module seems
  fine, but the whole BTLE part is not available. Particularly I cannot
  detect/pair Logitech M720 mouse.

  Platform: ThinkPad T14 Gen 2i
  --- 
  ProblemType: Bug
  ApportVersion: 2.27.0-0ubuntu4
  Architecture: amd64
  CasperMD5CheckResult: pass
  CurrentDesktop: ubuntu:GNOME
  DistroRelease: Ubuntu 23.10
  InstallationDate: Installed on 2022-05-28 (494 days ago)
  InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Release amd64 
(20220419)
  InterestingModules: rfcomm bnep btusb bluetooth
  MachineType: {report['dmi.sys.vendor']} {report['dmi.product.name']}
  Package: linux
  PackageArchitecture: amd64
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-6.5.0-5-generic 
root=UUID=d0002130-adf6-4f18-93b1-fda536d8b499 ro quiet splash vt.handoff=7
  ProcVersionSignature: Ubuntu 6.5.0-5.5-generic 6.5.0
  RebootRequiredPkgs: Error: path contained symlinks.
  Tags: mantic
  Uname: Linux 6.5.0-5-generic x86_64
  UpgradeStatus: Upgraded to mantic on 2023-09-03 (30 days ago)
  UserGroups: adm cdrom dialout dip docker lpadmin lxd plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 05/10/2023
  dmi.bios.release: 1.56
  dmi.bios.vendor: LENOVO
  dmi.bios.version: N34ET56W (1.56 )
  dmi.board.asset.tag: Not Available
  dmi.board.name: 20W000AMPB
  dmi.board.vendor: LENOVO
  dmi.board.version: SDK0J40697 WIN
  dmi.chassis.asset.tag: No Asset Information
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: None
  dmi.ec.firmware.release: 1.42
  dmi.modalias: 
dmi:bvnLENOVO:bvrN34ET56W(1.56):bd05/10/2023:br1.56:efr1.42:svnLENOVO:pn20W000AMPB:pvrThinkPadT14Gen2i:rvnLENOVO:rn20W000AMPB:rvrSDK0J40697WIN:cvnLENOVO:ct10:cvrNone:skuLENOVO_MT_20W0_BU_Think_FM_ThinkPadT14Gen2i:
  dmi.product.family: ThinkPad T14 Gen 2i
  dmi.product.name: 20W000AMPB
  dmi.product.sku: LENOVO_MT_20W0_BU_Think_FM_ThinkPad T14 Gen 2i
  dmi.product.version: ThinkPad T14 Gen 2i
  dmi.sys.vendor: LENOVO
  hciconfig:
   hci0:Type: Primary  Bus: USB
BD Address: A0:E7:0B:23:70:E8  ACL MTU: 1021:4  SCO MTU: 96:6
UP RUNNING 
RX bytes:22183 acl:0 sco:0 events:3531 errors:0
TX bytes:821193 acl:0 sco:0 commands:3510 errors:0

To manage notifications about this bug go to:
https://bugs.launchpad.net/linux-firmware/+bug/2037906/+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 2037906] Re: [Intel AX201] Bluetooth LE not working after upgrade from 22.04 to 23.10

[Grzegorz - Thulium]

Is there anything else I can provide?

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

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

Title:
  [Intel AX201] Bluetooth LE not working after upgrade from 22.04 to
  23.10

Status in Linux Firmware:
  New
Status in bluez package in Ubuntu:
  New
Status in linux package in Ubuntu:
  Confirmed

Bug description:
  syslog:
  2023-09-20T09:32:54.138852+02:00 zaionc kernel: [   13.539860] Bluetooth: 
hci0: Waiting for firmware download to complete
  2023-09-20T09:32:54.138857+02:00 zaionc kernel: [   13.540223] Bluetooth: 
hci0: Firmware loaded in 1706498 usecs
  2023-09-20T09:32:54.138858+02:00 zaionc kernel: [   13.540278] Bluetooth: 
hci0: Waiting for device to boot
  2023-09-20T09:32:54.154894+02:00 zaionc kernel: [   13.555430] Bluetooth: 
hci0: Malformed MSFT vendor event: 0x02
  2023-09-20T09:32:54.154908+02:00 zaionc kernel: [   13.555482] Bluetooth: 
hci0: Device booted in 14872 usecs
  2023-09-20T09:32:54.154910+02:00 zaionc kernel: [   13.555913] Bluetooth: 
hci0: Found Intel DDC parameters: intel/ibt-19-0-4.ddc
  2023-09-20T09:32:54.158856+02:00 zaionc kernel: [   13.558300] Bluetooth: 
hci0: Applying Intel DDC parameters completed
  2023-09-20T09:32:54.158859+02:00 zaionc kernel: [   13.559326] Bluetooth: 
hci0: Firmware revision 0.4 build 249 week 27 2023

  lshw:
    *-usb:5
     description: Bluetooth wireless interface
     product: AX201 Bluetooth
     vendor: Intel Corp.
     physical id: a
     bus info: usb@3:a
     version: 0.02
     capabilities: bluetooth usb-2.01
     configuration: driver=btusb maxpower=100mA speed=12Mbit/s

  root@zaionc:~# hcitool lescan
  Set scan parameters failed: Input/output error

  At first bluetooth stopped working at all due to Ubuntu bug = missing
  firmware. It was fixed recently and now the bluetooth module seems
  fine, but the whole BTLE part is not available. Particularly I cannot
  detect/pair Logitech M720 mouse.

  Platform: ThinkPad T14 Gen 2i
  --- 
  ProblemType: Bug
  ApportVersion: 2.27.0-0ubuntu4
  Architecture: amd64
  CasperMD5CheckResult: pass
  CurrentDesktop: ubuntu:GNOME
  DistroRelease: Ubuntu 23.10
  InstallationDate: Installed on 2022-05-28 (494 days ago)
  InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Release amd64 
(20220419)
  InterestingModules: rfcomm bnep btusb bluetooth
  MachineType: {report['dmi.sys.vendor']} {report['dmi.product.name']}
  Package: linux
  PackageArchitecture: amd64
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-6.5.0-5-generic 
root=UUID=d0002130-adf6-4f18-93b1-fda536d8b499 ro quiet splash vt.handoff=7
  ProcVersionSignature: Ubuntu 6.5.0-5.5-generic 6.5.0
  RebootRequiredPkgs: Error: path contained symlinks.
  Tags: mantic
  Uname: Linux 6.5.0-5-generic x86_64
  UpgradeStatus: Upgraded to mantic on 2023-09-03 (30 days ago)
  UserGroups: adm cdrom dialout dip docker lpadmin lxd plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 05/10/2023
  dmi.bios.release: 1.56
  dmi.bios.vendor: LENOVO
  dmi.bios.version: N34ET56W (1.56 )
  dmi.board.asset.tag: Not Available
  dmi.board.name: 20W000AMPB
  dmi.board.vendor: LENOVO
  dmi.board.version: SDK0J40697 WIN
  dmi.chassis.asset.tag: No Asset Information
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: None
  dmi.ec.firmware.release: 1.42
  dmi.modalias: 
dmi:bvnLENOVO:bvrN34ET56W(1.56):bd05/10/2023:br1.56:efr1.42:svnLENOVO:pn20W000AMPB:pvrThinkPadT14Gen2i:rvnLENOVO:rn20W000AMPB:rvrSDK0J40697WIN:cvnLENOVO:ct10:cvrNone:skuLENOVO_MT_20W0_BU_Think_FM_ThinkPadT14Gen2i:
  dmi.product.family: ThinkPad T14 Gen 2i
  dmi.product.name: 20W000AMPB
  dmi.product.sku: LENOVO_MT_20W0_BU_Think_FM_ThinkPad T14 Gen 2i
  dmi.product.version: ThinkPad T14 Gen 2i
  dmi.sys.vendor: LENOVO
  hciconfig:
   hci0:Type: Primary  Bus: USB
BD Address: A0:E7:0B:23:70:E8  ACL MTU: 1021:4  SCO MTU: 96:6
UP RUNNING 
RX bytes:22183 acl:0 sco:0 events:3531 errors:0
TX bytes:821193 acl:0 sco:0 commands:3510 errors:0

To manage notifications about this bug go to:
https://bugs.launchpad.net/linux-firmware/+bug/2037906/+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 2039651] [NEW] Pulse Audio Fails to reach 7.1 Surround

[Erick Couts II]

Public bug reported:

I have attempted every possible fix that I could find online, but Pulseaudio 
and Ubuntu Sound Settings fails to set 7.1 surround sound audio when it's 
selected.  I have my 7.1 surround sound system connected through ARC connection 
on my television.  While Windows and other Linux Distros can find it, Ubuntu 
has failed to work properly in changing the Pulseaudio settings for the past 3 
releases at least.  I'm willing to play around with the settings some more, but 
I don't have days to spend on it after I spent over 6 hours trying to fix it 
once.  I've dug through settings and manuals alike.
If it doesn't work as intended, then it doesn't work.

ProblemType: Bug
DistroRelease: Ubuntu 23.10
Package: pulseaudio 1:16.1+dfsg1-2ubuntu4
ProcVersionSignature: Ubuntu 6.5.0-9.9-generic 6.5.3
Uname: Linux 6.5.0-9-generic x86_64
NonfreeKernelModules: nvidia_modeset nvidia
ApportVersion: 2.27.0-0ubuntu5
Architecture: amd64
CasperMD5CheckResult: unknown
CurrentDesktop: ubuntu:GNOME
Date: Wed Oct 18 02:42:47 2023
ProcEnviron:
 LANG=en_US.UTF-8
 PATH=(custom, no user)
 SHELL=/bin/bash
 XDG_RUNTIME_DIR=
PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No 
PulseAudio daemon running, or not running as session daemon.
SourcePackage: pulseaudio
UpgradeStatus: Upgraded to mantic on 2023-10-15 (3 days ago)
dmi.bios.date: 06/05/2018
dmi.bios.release: 5.11
dmi.bios.vendor: American Megatrends Inc.
dmi.bios.version: P3.60
dmi.board.name: X99 Professional
dmi.board.vendor: ASRock
dmi.chassis.asset.tag: To Be Filled By O.E.M.
dmi.chassis.type: 3
dmi.chassis.vendor: To Be Filled By O.E.M.
dmi.chassis.version: To Be Filled By O.E.M.
dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrP3.60:bd06/05/2018:br5.11:svnToBeFilledByO.E.M.:pnToBeFilledByO.E.M.:pvrToBeFilledByO.E.M.:rvnASRock:rnX99Professional:rvr:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.:skuToBeFilledByO.E.M.:
dmi.product.family: To Be Filled By O.E.M.
dmi.product.name: To Be Filled By O.E.M.
dmi.product.sku: To Be Filled By O.E.M.
dmi.product.version: To Be Filled By O.E.M.
dmi.sys.vendor: To Be Filled By O.E.M.
modified.conffile..etc.pulse.daemon.conf: [modified]
modified.conffile..etc.pulse.default.pa: [modified]
mtime.conffile..etc.pulse.daemon.conf: 2023-10-18T02:34:08.524529
mtime.conffile..etc.pulse.default.pa: 2023-06-07T22:26:00.302860

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


** Tags: amd64 apport-bug mantic

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

Title:
  Pulse Audio Fails to reach 7.1 Surround

Status in pulseaudio package in Ubuntu:
  New

Bug description:
  I have attempted every possible fix that I could find online, but Pulseaudio 
and Ubuntu Sound Settings fails to set 7.1 surround sound audio when it's 
selected.  I have my 7.1 surround sound system connected through ARC connection 
on my television.  While Windows and other Linux Distros can find it, Ubuntu 
has failed to work properly in changing the Pulseaudio settings for the past 3 
releases at least.  I'm willing to play around with the settings some more, but 
I don't have days to spend on it after I spent over 6 hours trying to fix it 
once.  I've dug through settings and manuals alike.
  If it doesn't work as intended, then it doesn't work.

  ProblemType: Bug
  DistroRelease: Ubuntu 23.10
  Package: pulseaudio 1:16.1+dfsg1-2ubuntu4
  ProcVersionSignature: Ubuntu 6.5.0-9.9-generic 6.5.3
  Uname: Linux 6.5.0-9-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  ApportVersion: 2.27.0-0ubuntu5
  Architecture: amd64
  CasperMD5CheckResult: unknown
  CurrentDesktop: ubuntu:GNOME
  Date: Wed Oct 18 02:42:47 2023
  ProcEnviron:
   LANG=en_US.UTF-8
   PATH=(custom, no user)
   SHELL=/bin/bash
   XDG_RUNTIME_DIR=
  PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No 
PulseAudio daemon running, or not running as session daemon.
  SourcePackage: pulseaudio
  UpgradeStatus: Upgraded to mantic on 2023-10-15 (3 days ago)
  dmi.bios.date: 06/05/2018
  dmi.bios.release: 5.11
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: P3.60
  dmi.board.name: X99 Professional
  dmi.board.vendor: ASRock
  dmi.chassis.asset.tag: To Be Filled By O.E.M.
  dmi.chassis.type: 3
  dmi.chassis.vendor: To Be Filled By O.E.M.
  dmi.chassis.version: To Be Filled By O.E.M.
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrP3.60:bd06/05/2018:br5.11:svnToBeFilledByO.E.M.:pnToBeFilledByO.E.M.:pvrToBeFilledByO.E.M.:rvnASRock:rnX99Professional:rvr:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.:skuToBeFilledByO.E.M.:
  dmi.product.family: To Be Filled By O.E.M.
  dmi.product.name: To Be Filled By O.E.M.
  dmi.product.sku: To Be Filled By O.E.M.
  dmi.product.version: To Be Filled By O.E.M.
  dmi.sys.vendor: To Be Filled By O.E.M.
  

[Touch-packages] [Bug 2039589] Re: Nwidia driver Ubuntu bug

[Daniel van Vugt]

Thanks for the bug report. Can you explain in more detail where and when
you see the error?

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

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

** Summary changed:

- Nwidia driver Ubuntu bug
+ Nvidia driver Ubuntu bug

** Package changed: ubuntu => nvidia-graphics-drivers-470 (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/2039589

Title:
  Nvidia driver Ubuntu bug

Status in nvidia-graphics-drivers-470 package in Ubuntu:
  Incomplete

Bug description:
  Nvidia driver error 470: UFW main window not displayed properly and
  Help not displayed. The issue affects Ubuntu 22.04.3 LTS, Ubuntu 23.10
  and Linux Mint.

  ProblemType: Bug
  DistroRelease: Ubuntu 22.04
  Package: xorg 1:7.7+23ubuntu2
  ProcVersionSignature: Ubuntu 6.2.0-34.34~22.04.1-generic 6.2.16
  Uname: Linux 6.2.0-34-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  .proc.driver.nvidia.capabilities.gpu0: Error: path was not a regular file.
  .proc.driver.nvidia.capabilities.mig: Error: path was not a regular file.
  .proc.driver.nvidia.gpus..01.00.0: Error: path was not a regular file.
  .proc.driver.nvidia.registry: Binary: ""
  .proc.driver.nvidia.suspend: suspend hibernate resume
  .proc.driver.nvidia.suspend_depth: default modeset uvm
  .proc.driver.nvidia.version:
   NVRM version: NVIDIA UNIX x86_64 Kernel Module  470.199.02  Thu May 11 
11:46:56 UTC 2023
   GCC version:
  ApportVersion: 2.20.11-0ubuntu82.5
  Architecture: amd64
  BootLog: Error: [Errno 13] Brak dostępu: '/var/log/boot.log'
  CasperMD5CheckResult: pass
  CompositorRunning: None
  CurrentDesktop: ubuntu:GNOME
  Date: Tue Oct 17 18:13:32 2023
  DistUpgraded: Fresh install
  DistroCodename: jammy
  DistroVariant: ubuntu
  GraphicsCard:
   NVIDIA Corporation GK107 [GeForce GTX 650] [10de:0fc6] (rev a1) (prog-if 00 
[VGA controller])
 Subsystem: CardExpert Technology GK107 [GeForce GTX 650] [10b0:0fc6]
  InstallationDate: Installed on 2023-10-16 (1 days ago)
  InstallationMedia: Ubuntu 22.04.3 LTS "Jammy Jellyfish" - Release amd64 
(20230807.2)
  MachineType: Gigabyte Technology Co., Ltd. To be filled by O.E.M.
  ProcEnviron:
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=pl_PL.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-6.2.0-34-generic 
root=UUID=7faab2db-29fa-4024-ae67-d6f019c15904 ro quiet splash vt.handoff=7
  SourcePackage: xorg
  Symptom: display
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 02/25/2014
  dmi.bios.release: 4.6
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 10b
  dmi.board.asset.tag: To be filled by O.E.M.
  dmi.board.name: H61M-S1
  dmi.board.vendor: Gigabyte Technology Co., Ltd.
  dmi.board.version: x.x
  dmi.chassis.asset.tag: To Be Filled By O.E.M.
  dmi.chassis.type: 3
  dmi.chassis.vendor: Gigabyte Technology Co., Ltd.
  dmi.chassis.version: To Be Filled By O.E.M.
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr10b:bd02/25/2014:br4.6:svnGigabyteTechnologyCo.,Ltd.:pnTobefilledbyO.E.M.:pvrTobefilledbyO.E.M.:rvnGigabyteTechnologyCo.,Ltd.:rnH61M-S1:rvrx.x:cvnGigabyteTechnologyCo.,Ltd.:ct3:cvrToBeFilledByO.E.M.:skuTobefilledbyO.E.M.:
  dmi.product.family: To be filled by O.E.M.
  dmi.product.name: To be filled by O.E.M.
  dmi.product.sku: To be filled by O.E.M.
  dmi.product.version: To be filled by O.E.M.
  dmi.sys.vendor: Gigabyte Technology Co., Ltd.
  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.113-2~ubuntu0.22.04.1
  version.libgl1-mesa-dri: libgl1-mesa-dri 23.0.4-0ubuntu1~22.04.1
  version.libgl1-mesa-glx: libgl1-mesa-glx N/A
  version.nvidia-graphics-drivers: nvidia-graphics-drivers-* N/A
  version.xserver-xorg-core: xserver-xorg-core 2:21.1.4-2ubuntu1.7~22.04.1
  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/nvidia-graphics-drivers-470/+bug/2039589/+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 2038998] Re: [amdgpu] Screen artifacts/UI oddities on Wayland

[Daniel van Vugt]

** Summary changed:

- [amdgpu] Screen artifacts/UI oddities on Wayland following Steam/Proton 
session
+ [amdgpu] Screen artifacts/UI oddities on Wayland

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

Title:
  [amdgpu] Screen artifacts/UI oddities on Wayland

Status in linux package in Ubuntu:
  Confirmed
Status in mesa package in Ubuntu:
  Confirmed

Bug description:
  Laptop is a Lenovo ThinkPad P14s Gen 2 AMD.
  Ryzen 7 PRO 5850U
  with Radeon (RX Vega 8?) integrated graphics
  16 GB RAM

  Running Ubuntu 23.10 (GNOME) from a clean install performed October 9,
  2023 from a daily-live/current .iso generated on October 4, 2023.

  Wayland
  Kernel 6.5.0-9-generic

  * * * * *

  Installed a pre-release build of Ubuntu 23.10 to my ThinkPad the other
  day, was going through setting up and testing the usual programs.

  Installed Steam through apt from the 'mantic' repositories. Installed
  Proton 8.0 and Steam Linux Runtime 3.0 (Sniper) alongside two
  compatible titles.

  Screen corruption (white and grey streaks) present in-game when GNOME
  UI elements appeared on-screen (e.g., volume, brightness, and keyboard
  backlight indicators) and omnipresent after closing either game.

  Artifacts remain on screen until log-out or reboot. Artifacts were not
  present beforehand.

  Artifacts only appeared in Wayland session; not X11/Xorg.

  I previously had been running the same games on Ubuntu 22.04 LTS
  (GNOME, Wayland) and Kubuntu 22.04 LTS (Plasma, X11/Xorg) on this
  computer without issue (kernel 6.2).

  * * * * *

  Please see subsequent posts for video/images.

  Happy to provide any other information as needed. Thanks!

  * * * * *

  ProblemType: Bug
  DistroRelease: Ubuntu 23.10
  Package: xorg 1:7.7+23ubuntu2
  ProcVersionSignature: Ubuntu 6.5.0-9.9-generic 6.5.3
  Uname: Linux 6.5.0-9-generic x86_64
  ApportVersion: 2.27.0-0ubuntu5
  Architecture: amd64
  BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
  CasperMD5CheckResult: unknown
  CompositorRunning: None
  CurrentDesktop: ubuntu:GNOME
  Date: Wed Oct 11 01:17:43 2023
  DistUpgraded: Fresh install
  DistroCodename: mantic
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes, if not too technical
  GraphicsCard:
   Advanced Micro Devices, Inc. [AMD/ATI] Cezanne [Radeon Vega Series / Radeon 
Vega Mobile Series] [1002:1638] (rev d1) (prog-if 00 [VGA controller])
     Subsystem: Lenovo Cezanne [Radeon Vega Series / Radeon Vega Mobile Series] 
[17aa:509b]
  MachineType: {report['dmi.sys.vendor']} {report['dmi.product.name']}
  ProcEnviron:
   LANG=en_US.UTF-8
   PATH=(custom, no user)
   SHELL=/bin/bash
   TERM=xterm-256color
   XDG_RUNTIME_DIR=
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-6.5.0-9-generic 
root=/dev/mapper/ubuntu--vg-ubuntu--lv ro quiet splash vt.handoff=7
  SourcePackage: xorg
  Symptom: display
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 05/15/2023
  dmi.bios.release: 1.24
  dmi.bios.vendor: LENOVO
  dmi.bios.version: R1MET54W (1.24 )
  dmi.board.asset.tag: Not Available
  dmi.board.name: 21A00068US
  dmi.board.vendor: LENOVO
  dmi.board.version: SDK0T76530 WIN
  dmi.chassis.asset.tag: No Asset Information
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: None
  dmi.ec.firmware.release: 1.24
  dmi.modalias: 
dmi:bvnLENOVO:bvrR1MET54W(1.24):bd05/15/2023:br1.24:efr1.24:svnLENOVO:pn21A00068US:pvrThinkPadP14sGen2a:rvnLENOVO:rn21A00068US:rvrSDK0T76530WIN:cvnLENOVO:ct10:cvrNone:skuLENOVO_MT_21A0_BU_Think_FM_ThinkPadP14sGen2a:
  dmi.product.family: ThinkPad P14s Gen 2a
  dmi.product.name: 21A00068US
  dmi.product.sku: LENOVO_MT_21A0_BU_Think_FM_ThinkPad P14s Gen 2a
  dmi.product.version: ThinkPad P14s Gen 2a
  dmi.sys.vendor: LENOVO
  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.115-1
  version.libgl1-mesa-dri: libgl1-mesa-dri 23.2.1-1ubuntu3
  version.libgl1-mesa-glx: libgl1-mesa-glx N/A
  version.xserver-xorg-core: xserver-xorg-core 2:21.1.7-3ubuntu2
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-3
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20210115-1
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 
1:1.0.17-2build1

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2038998/+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 2038998] Re: [amdgpu] Screen artifacts/UI oddities on Wayland

[Launchpad Bug Tracker]

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

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

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

Title:
  [amdgpu] Screen artifacts/UI oddities on Wayland

Status in linux package in Ubuntu:
  Confirmed
Status in mesa package in Ubuntu:
  Confirmed

Bug description:
  Laptop is a Lenovo ThinkPad P14s Gen 2 AMD.
  Ryzen 7 PRO 5850U
  with Radeon (RX Vega 8?) integrated graphics
  16 GB RAM

  Running Ubuntu 23.10 (GNOME) from a clean install performed October 9,
  2023 from a daily-live/current .iso generated on October 4, 2023.

  Wayland
  Kernel 6.5.0-9-generic

  * * * * *

  Installed a pre-release build of Ubuntu 23.10 to my ThinkPad the other
  day, was going through setting up and testing the usual programs.

  Installed Steam through apt from the 'mantic' repositories. Installed
  Proton 8.0 and Steam Linux Runtime 3.0 (Sniper) alongside two
  compatible titles.

  Screen corruption (white and grey streaks) present in-game when GNOME
  UI elements appeared on-screen (e.g., volume, brightness, and keyboard
  backlight indicators) and omnipresent after closing either game.

  Artifacts remain on screen until log-out or reboot. Artifacts were not
  present beforehand.

  Artifacts only appeared in Wayland session; not X11/Xorg.

  I previously had been running the same games on Ubuntu 22.04 LTS
  (GNOME, Wayland) and Kubuntu 22.04 LTS (Plasma, X11/Xorg) on this
  computer without issue (kernel 6.2).

  * * * * *

  Please see subsequent posts for video/images.

  Happy to provide any other information as needed. Thanks!

  * * * * *

  ProblemType: Bug
  DistroRelease: Ubuntu 23.10
  Package: xorg 1:7.7+23ubuntu2
  ProcVersionSignature: Ubuntu 6.5.0-9.9-generic 6.5.3
  Uname: Linux 6.5.0-9-generic x86_64
  ApportVersion: 2.27.0-0ubuntu5
  Architecture: amd64
  BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
  CasperMD5CheckResult: unknown
  CompositorRunning: None
  CurrentDesktop: ubuntu:GNOME
  Date: Wed Oct 11 01:17:43 2023
  DistUpgraded: Fresh install
  DistroCodename: mantic
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes, if not too technical
  GraphicsCard:
   Advanced Micro Devices, Inc. [AMD/ATI] Cezanne [Radeon Vega Series / Radeon 
Vega Mobile Series] [1002:1638] (rev d1) (prog-if 00 [VGA controller])
     Subsystem: Lenovo Cezanne [Radeon Vega Series / Radeon Vega Mobile Series] 
[17aa:509b]
  MachineType: {report['dmi.sys.vendor']} {report['dmi.product.name']}
  ProcEnviron:
   LANG=en_US.UTF-8
   PATH=(custom, no user)
   SHELL=/bin/bash
   TERM=xterm-256color
   XDG_RUNTIME_DIR=
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-6.5.0-9-generic 
root=/dev/mapper/ubuntu--vg-ubuntu--lv ro quiet splash vt.handoff=7
  SourcePackage: xorg
  Symptom: display
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 05/15/2023
  dmi.bios.release: 1.24
  dmi.bios.vendor: LENOVO
  dmi.bios.version: R1MET54W (1.24 )
  dmi.board.asset.tag: Not Available
  dmi.board.name: 21A00068US
  dmi.board.vendor: LENOVO
  dmi.board.version: SDK0T76530 WIN
  dmi.chassis.asset.tag: No Asset Information
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: None
  dmi.ec.firmware.release: 1.24
  dmi.modalias: 
dmi:bvnLENOVO:bvrR1MET54W(1.24):bd05/15/2023:br1.24:efr1.24:svnLENOVO:pn21A00068US:pvrThinkPadP14sGen2a:rvnLENOVO:rn21A00068US:rvrSDK0T76530WIN:cvnLENOVO:ct10:cvrNone:skuLENOVO_MT_21A0_BU_Think_FM_ThinkPadP14sGen2a:
  dmi.product.family: ThinkPad P14s Gen 2a
  dmi.product.name: 21A00068US
  dmi.product.sku: LENOVO_MT_21A0_BU_Think_FM_ThinkPad P14s Gen 2a
  dmi.product.version: ThinkPad P14s Gen 2a
  dmi.sys.vendor: LENOVO
  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.115-1
  version.libgl1-mesa-dri: libgl1-mesa-dri 23.2.1-1ubuntu3
  version.libgl1-mesa-glx: libgl1-mesa-glx N/A
  version.xserver-xorg-core: xserver-xorg-core 2:21.1.7-3ubuntu2
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-3
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20210115-1
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 
1:1.0.17-2build1

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2038998/+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 2038998] Re: [amdgpu] Screen artifacts/UI oddities on Wayland

[Daniel van Vugt]

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

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

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

Title:
  [amdgpu] Screen artifacts/UI oddities on Wayland

Status in linux package in Ubuntu:
  Confirmed
Status in mesa package in Ubuntu:
  Confirmed

Bug description:
  Laptop is a Lenovo ThinkPad P14s Gen 2 AMD.
  Ryzen 7 PRO 5850U
  with Radeon (RX Vega 8?) integrated graphics
  16 GB RAM

  Running Ubuntu 23.10 (GNOME) from a clean install performed October 9,
  2023 from a daily-live/current .iso generated on October 4, 2023.

  Wayland
  Kernel 6.5.0-9-generic

  * * * * *

  Installed a pre-release build of Ubuntu 23.10 to my ThinkPad the other
  day, was going through setting up and testing the usual programs.

  Installed Steam through apt from the 'mantic' repositories. Installed
  Proton 8.0 and Steam Linux Runtime 3.0 (Sniper) alongside two
  compatible titles.

  Screen corruption (white and grey streaks) present in-game when GNOME
  UI elements appeared on-screen (e.g., volume, brightness, and keyboard
  backlight indicators) and omnipresent after closing either game.

  Artifacts remain on screen until log-out or reboot. Artifacts were not
  present beforehand.

  Artifacts only appeared in Wayland session; not X11/Xorg.

  I previously had been running the same games on Ubuntu 22.04 LTS
  (GNOME, Wayland) and Kubuntu 22.04 LTS (Plasma, X11/Xorg) on this
  computer without issue (kernel 6.2).

  * * * * *

  Please see subsequent posts for video/images.

  Happy to provide any other information as needed. Thanks!

  * * * * *

  ProblemType: Bug
  DistroRelease: Ubuntu 23.10
  Package: xorg 1:7.7+23ubuntu2
  ProcVersionSignature: Ubuntu 6.5.0-9.9-generic 6.5.3
  Uname: Linux 6.5.0-9-generic x86_64
  ApportVersion: 2.27.0-0ubuntu5
  Architecture: amd64
  BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
  CasperMD5CheckResult: unknown
  CompositorRunning: None
  CurrentDesktop: ubuntu:GNOME
  Date: Wed Oct 11 01:17:43 2023
  DistUpgraded: Fresh install
  DistroCodename: mantic
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes, if not too technical
  GraphicsCard:
   Advanced Micro Devices, Inc. [AMD/ATI] Cezanne [Radeon Vega Series / Radeon 
Vega Mobile Series] [1002:1638] (rev d1) (prog-if 00 [VGA controller])
     Subsystem: Lenovo Cezanne [Radeon Vega Series / Radeon Vega Mobile Series] 
[17aa:509b]
  MachineType: {report['dmi.sys.vendor']} {report['dmi.product.name']}
  ProcEnviron:
   LANG=en_US.UTF-8
   PATH=(custom, no user)
   SHELL=/bin/bash
   TERM=xterm-256color
   XDG_RUNTIME_DIR=
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-6.5.0-9-generic 
root=/dev/mapper/ubuntu--vg-ubuntu--lv ro quiet splash vt.handoff=7
  SourcePackage: xorg
  Symptom: display
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 05/15/2023
  dmi.bios.release: 1.24
  dmi.bios.vendor: LENOVO
  dmi.bios.version: R1MET54W (1.24 )
  dmi.board.asset.tag: Not Available
  dmi.board.name: 21A00068US
  dmi.board.vendor: LENOVO
  dmi.board.version: SDK0T76530 WIN
  dmi.chassis.asset.tag: No Asset Information
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: None
  dmi.ec.firmware.release: 1.24
  dmi.modalias: 
dmi:bvnLENOVO:bvrR1MET54W(1.24):bd05/15/2023:br1.24:efr1.24:svnLENOVO:pn21A00068US:pvrThinkPadP14sGen2a:rvnLENOVO:rn21A00068US:rvrSDK0T76530WIN:cvnLENOVO:ct10:cvrNone:skuLENOVO_MT_21A0_BU_Think_FM_ThinkPadP14sGen2a:
  dmi.product.family: ThinkPad P14s Gen 2a
  dmi.product.name: 21A00068US
  dmi.product.sku: LENOVO_MT_21A0_BU_Think_FM_ThinkPad P14s Gen 2a
  dmi.product.version: ThinkPad P14s Gen 2a
  dmi.sys.vendor: LENOVO
  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.115-1
  version.libgl1-mesa-dri: libgl1-mesa-dri 23.2.1-1ubuntu3
  version.libgl1-mesa-glx: libgl1-mesa-glx N/A
  version.xserver-xorg-core: xserver-xorg-core 2:21.1.7-3ubuntu2
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-3
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20210115-1
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 
1:1.0.17-2build1

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2038998/+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 2038998] Status changed to Confirmed

[Ubuntu Kernel Bot]

This change was made by a bot.

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

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

Title:
  [amdgpu] Screen artifacts/UI oddities on Wayland

Status in linux package in Ubuntu:
  Confirmed
Status in mesa package in Ubuntu:
  Confirmed

Bug description:
  Laptop is a Lenovo ThinkPad P14s Gen 2 AMD.
  Ryzen 7 PRO 5850U
  with Radeon (RX Vega 8?) integrated graphics
  16 GB RAM

  Running Ubuntu 23.10 (GNOME) from a clean install performed October 9,
  2023 from a daily-live/current .iso generated on October 4, 2023.

  Wayland
  Kernel 6.5.0-9-generic

  * * * * *

  Installed a pre-release build of Ubuntu 23.10 to my ThinkPad the other
  day, was going through setting up and testing the usual programs.

  Installed Steam through apt from the 'mantic' repositories. Installed
  Proton 8.0 and Steam Linux Runtime 3.0 (Sniper) alongside two
  compatible titles.

  Screen corruption (white and grey streaks) present in-game when GNOME
  UI elements appeared on-screen (e.g., volume, brightness, and keyboard
  backlight indicators) and omnipresent after closing either game.

  Artifacts remain on screen until log-out or reboot. Artifacts were not
  present beforehand.

  Artifacts only appeared in Wayland session; not X11/Xorg.

  I previously had been running the same games on Ubuntu 22.04 LTS
  (GNOME, Wayland) and Kubuntu 22.04 LTS (Plasma, X11/Xorg) on this
  computer without issue (kernel 6.2).

  * * * * *

  Please see subsequent posts for video/images.

  Happy to provide any other information as needed. Thanks!

  * * * * *

  ProblemType: Bug
  DistroRelease: Ubuntu 23.10
  Package: xorg 1:7.7+23ubuntu2
  ProcVersionSignature: Ubuntu 6.5.0-9.9-generic 6.5.3
  Uname: Linux 6.5.0-9-generic x86_64
  ApportVersion: 2.27.0-0ubuntu5
  Architecture: amd64
  BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
  CasperMD5CheckResult: unknown
  CompositorRunning: None
  CurrentDesktop: ubuntu:GNOME
  Date: Wed Oct 11 01:17:43 2023
  DistUpgraded: Fresh install
  DistroCodename: mantic
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes, if not too technical
  GraphicsCard:
   Advanced Micro Devices, Inc. [AMD/ATI] Cezanne [Radeon Vega Series / Radeon 
Vega Mobile Series] [1002:1638] (rev d1) (prog-if 00 [VGA controller])
     Subsystem: Lenovo Cezanne [Radeon Vega Series / Radeon Vega Mobile Series] 
[17aa:509b]
  MachineType: {report['dmi.sys.vendor']} {report['dmi.product.name']}
  ProcEnviron:
   LANG=en_US.UTF-8
   PATH=(custom, no user)
   SHELL=/bin/bash
   TERM=xterm-256color
   XDG_RUNTIME_DIR=
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-6.5.0-9-generic 
root=/dev/mapper/ubuntu--vg-ubuntu--lv ro quiet splash vt.handoff=7
  SourcePackage: xorg
  Symptom: display
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 05/15/2023
  dmi.bios.release: 1.24
  dmi.bios.vendor: LENOVO
  dmi.bios.version: R1MET54W (1.24 )
  dmi.board.asset.tag: Not Available
  dmi.board.name: 21A00068US
  dmi.board.vendor: LENOVO
  dmi.board.version: SDK0T76530 WIN
  dmi.chassis.asset.tag: No Asset Information
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: None
  dmi.ec.firmware.release: 1.24
  dmi.modalias: 
dmi:bvnLENOVO:bvrR1MET54W(1.24):bd05/15/2023:br1.24:efr1.24:svnLENOVO:pn21A00068US:pvrThinkPadP14sGen2a:rvnLENOVO:rn21A00068US:rvrSDK0T76530WIN:cvnLENOVO:ct10:cvrNone:skuLENOVO_MT_21A0_BU_Think_FM_ThinkPadP14sGen2a:
  dmi.product.family: ThinkPad P14s Gen 2a
  dmi.product.name: 21A00068US
  dmi.product.sku: LENOVO_MT_21A0_BU_Think_FM_ThinkPad P14s Gen 2a
  dmi.product.version: ThinkPad P14s Gen 2a
  dmi.sys.vendor: LENOVO
  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.115-1
  version.libgl1-mesa-dri: libgl1-mesa-dri 23.2.1-1ubuntu3
  version.libgl1-mesa-glx: libgl1-mesa-glx N/A
  version.xserver-xorg-core: xserver-xorg-core 2:21.1.7-3ubuntu2
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-3
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20210115-1
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 
1:1.0.17-2build1

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


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

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

[Daniel van Vugt]

Also just in case you've found a new form of bug 2034619 please try
adding this to /etc/environment:

  MUTTER_DEBUG_KMS_THREAD_TYPE=user

and then reboot.


** No longer affects: ubuntu

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

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

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

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

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

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


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

[Touch-packages] [Bug 2039391] Re: pakage broken

[Daniel van Vugt]

** Package changed: xorg (Ubuntu) => 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/2039391

Title:
  pakage broken

Status in Ubuntu:
  Incomplete

Bug description:
  instaler pakage broken

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: xorg 1:7.7+19ubuntu14
  ProcVersionSignature: Ubuntu 5.4.0-164.181-generic 5.4.248
  Uname: Linux 5.4.0-164-generic x86_64
  .tmp.unity_support_test.0:
   
  ApportVersion: 2.20.11-0ubuntu27.27
  Architecture: amd64
  CasperMD5CheckResult: skip
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: None
  Date: Sun Oct 15 22:20:43 2023
  DistUpgraded: Fresh install
  DistributionChannelDescriptor:
   # This is a distribution channel descriptor
   # For more information see 
http://wiki.ubuntu.com/DistributionChannelDescriptor
   canonical-oem-somerville-xenial-amd64-20160624-2
  DistroCodename: focal
  DistroVariant: ubuntu
  DkmsStatus:
   intel-hid, 3.1, 4.4.0-210-generic, x86_64: installed
   oem-audio-hda-daily, 0.201708030416~ubuntu16.04.1, 4.4.0-210-generic, 
x86_64: installed
   oem-wifi-qualcomm-ath10k-lp1734600-4.4, 4.1, 4.4.0-210-generic, x86_64: 
installed
  ExtraDebuggingInterest: I just need to know a workaround
  GraphicsCard:
   Intel Corporation Skylake GT2 [HD Graphics 520] [8086:1916] (rev 07) 
(prog-if 00 [VGA controller])
 Subsystem: Dell Skylake GT2 [HD Graphics 520] [1028:0793]
  InstallationDate: Installed on 2023-07-12 (95 days ago)
  InstallationMedia: Ubuntu 16.04 "Xenial" - Build amd64 LIVE Binary 
20160624-10:47
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 004: ID 0cf3:e009 Qualcomm Atheros Communications 
   Bus 001 Device 003: ID 0bda:0129 Realtek Semiconductor Corp. RTS5129 Card 
Reader Controller
   Bus 001 Device 002: ID 0bda:5769 Realtek Semiconductor Corp. 
Integrated_Webcam_HD
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: Dell Inc. Vostro 15-3568
  ProcEnviron:
   LANGUAGE=en_IN:en
   PATH=(custom, no user)
   LANG=en_IN
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-164-generic 
root=UUID=ecd93531-cc0b-4642-b530-68a5e7081e61 ro acpi_rev_override 
locale=en_IN alx.enable_wol=1 mem_sleep_default=deep quiet splash vt.handoff=7
  SourcePackage: xorg
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 04/19/2018
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: 2.5.0
  dmi.board.name: 05HRPP
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A00
  dmi.chassis.type: 9
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvr2.5.0:bd04/19/2018:svnDellInc.:pnVostro15-3568:pvr:rvnDellInc.:rn05HRPP:rvrA00:cvnDellInc.:ct9:cvr:
  dmi.product.family: Vostro
  dmi.product.name: Vostro 15-3568
  dmi.product.sku: 0793
  dmi.sys.vendor: Dell Inc.
  version.compiz: compiz 1:0.9.14.1+20.04.20220820-0ubuntu1
  version.libdrm2: libdrm2 2.4.107-8ubuntu1~20.04.2
  version.libgl1-mesa-dri: libgl1-mesa-dri 21.2.6-0ubuntu0.1~20.04.2
  version.libgl1-mesa-glx: libgl1-mesa-glx 21.2.6-0ubuntu0.1~20.04.2
  version.xserver-xorg-core: xserver-xorg-core 2:1.20.13-1ubuntu1~20.04.8
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.10.6-1
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20200226-1
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1
  xserver.bootTime: Sun Oct 15 21:52:15 2023
  xserver.configfile: default
  xserver.errors:
   open /dev/dri/card0: No such file or directory
   open /dev/dri/card0: No such file or directory
   Screen 0 deleted because of no matching config section.
  xserver.logfile: /var/log/Xorg.0.log
  xserver.outputs:
   
  xserver.version: 2:1.20.13-1ubuntu1~20.04.8

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


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

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

[Daniel van Vugt]

There's also a lot of this in the journal:

  GNOME Shell crashed with signal 11

so 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.

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

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

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

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

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

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


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

[Touch-packages] [Bug 2039401] Re: Suspend/Hibernate resume fails with NVIDIA

[Daniel van Vugt]

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

** Also affects: nvidia-graphics-drivers-535 (Ubuntu)
   Importance: Undecided
   Status: New

** Tags added: nvidia suspend-resume

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

Title:
  Suspend/Hibernate resume fails with NVIDIA

Status in linux package in Ubuntu:
  New
Status in nvidia-graphics-drivers-535 package in Ubuntu:
  New

Bug description:
  Following are the NVIDIA, uname information
  Linux awesomesystem 6.2.0-34-generic #34-Ubuntu SMP PREEMPT_DYNAMIC Mon Sep  
4 13:06:55 UTC 2023 x86_64 x86_64 x86_64 GNU/Linux 

  
+---+
  |NVIDIA-SMI 535.113.01 Driver Version: 535.113.01   CUDA Version: 
12.2  |
  
|-+--+--+
  | GPU  Name Persistence-M | Bus-IdDisp.A | Volatile 
Uncorr. ECC |
  | Fan  Temp   Perf  Pwr:Usage/Cap | Memory-Usage | GPU-Util  
Compute M. |
  | |  |
   MIG M. |
  
|=+==+==|
  |   0  NVIDIA GeForce RTX 3050 ...Off | :01:00.0 Off |
  N/A |
  | N/A   40CP8   6W /  60W |  9MiB /  4096MiB |  0%
  Default |
  | |  |
  N/A |
  
+-+--+--+

   
  
+---+
  | Processes:  
  |
  |  GPU   GI   CIPID   Type   Process name
GPU Memory |
  |ID   ID 
Usage  |
  
|===|
  |0   N/A  N/A  2091  G   /usr/lib/xorg/Xorg   
 4MiB |
  
+---+

  ProblemType: Bug
  DistroRelease: Ubuntu 23.04
  Package: xorg 1:7.7+23ubuntu2
  ProcVersionSignature: Ubuntu 6.2.0-34.34-generic 6.2.16
  Uname: Linux 6.2.0-34-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  .proc.driver.nvidia.capabilities.gpu0: Error: path was not a regular file.
  .proc.driver.nvidia.capabilities.mig: Error: path was not a regular file.
  .proc.driver.nvidia.gpus..01.00.0: Error: path was not a regular file.
  .proc.driver.nvidia.registry: Binary: ""
  .proc.driver.nvidia.suspend: suspend hibernate resume
  .proc.driver.nvidia.suspend_depth: default modeset uvm
  .proc.driver.nvidia.version:
   NVRM version: NVIDIA UNIX x86_64 Kernel Module  535.113.01  Tue Sep 12 
19:41:24 UTC 2023
   GCC version:
  ApportVersion: 2.26.1-0ubuntu2
  Architecture: amd64
  BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
  CasperMD5CheckResult: pass
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: None
  CurrentDesktop: ubuntu:GNOME
  Date: Mon Oct 16 07:08:51 2023
  DistUpgraded: 2023-09-17 10:26:39,390 DEBUG icon theme changed, re-reading
  DistroCodename: lunar
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes
  GraphicsCard:
   Intel Corporation Alder Lake-P GT1 [UHD Graphics] [8086:46a3] (rev 0c) 
(prog-if 00 [VGA controller])
 Subsystem: Hewlett-Packard Company Alder Lake-P GT1 [UHD Graphics] 
[103c:8a4f]
   NVIDIA Corporation GA107M [GeForce RTX 3050 Ti Mobile] [10de:25a0] (rev a1) 
(prog-if 00 [VGA controller])
 Subsystem: Hewlett-Packard Company GA107M [GeForce RTX 3050 Ti Mobile] 
[103c:8a4f]
  InstallationDate: Installed on 2022-10-31 (349 days ago)
  InstallationMedia: Ubuntu 22.04.1 LTS "Jammy Jellyfish" - Release amd64 
(20220809.1)
  MachineType: HP Victus by HP Gaming Laptop 15-fa0xxx
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-6.2.0-34-generic 
root=UUID=4d4e900e-4cd2-46f8-b708-9e4d3afa286f ro quiet splash vt.handoff=7
  SourcePackage: xorg
  Symptom: display
  UpgradeStatus: Upgraded to lunar on 2023-09-17 (28 days ago)
  dmi.bios.date: 08/25/2023
  dmi.bios.release: 15.23
  dmi.bios.vendor: AMI
  dmi.bios.version: F.23
  dmi.board.asset.tag: Base Board Asset Tag
  dmi.board.name: 8A4F
  dmi.board.vendor: HP
  dmi.board.version: 37.54
  dmi.chassis.type: 10
  dmi.chassis.vendor: HP
  dmi.chassis.version: Chassis Version
  dmi.ec.firmware.release: 37.54
  dmi.modalias: 

[Touch-packages] [Bug 2039449] Re: Screen flickers sometimes and all applications closed on return from lock screen/sleep more

[Daniel van Vugt]

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

Thank you for taking the time to report this bug and helping to make
Ubuntu better. This particular bug has already been reported and is a
duplicate of bug 2034619, so it is being marked as such. Please look at
the other bug report to see if there is any missing information that you
can provide, or to see if there is a workaround for the bug.
Additionally, any further discussion regarding the bug should occur in
the other report. Feel free to continue to report any other bugs you may
find.


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

** This bug has been marked a duplicate of bug 2034619
   [amdgpu] gnome-shell gets SIGKILL'd when lock screen or under heavy load in 
Wayland

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

Title:
  Screen flickers sometimes and all applications closed on return from
  lock screen/sleep more

Status in mutter package in Ubuntu:
  New

Bug description:
  Recent Upgrade to 23.10. 
  New hardware, Lenovo T14 G4 AMD Ryzen 7 PRO 7840U w/ Radeon 780M Graphics

  ProblemType: Bug
  DistroRelease: Ubuntu 23.10
  Package: xorg 1:7.7+23ubuntu2
  ProcVersionSignature: Ubuntu 6.5.0-9.9-generic 6.5.3
  Uname: Linux 6.5.0-9-generic x86_64
  ApportVersion: 2.27.0-0ubuntu5
  Architecture: amd64
  BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
  CasperMD5CheckResult: pass
  CompositorRunning: None
  CurrentDesktop: ubuntu:GNOME
  Date: Mon Oct 16 15:36:51 2023
  DistUpgraded: 2023-10-15 14:21:56,603 DEBUG Running PostInstallScript: 
'/usr/lib/ubuntu-advantage/upgrade_lts_contract.py'
  DistroCodename: mantic
  DistroVariant: ubuntu
  GraphicsCard:
   Advanced Micro Devices, Inc. [AMD/ATI] Phoenix1 [1002:15bf] (rev dd) 
(prog-if 00 [VGA controller])
 Subsystem: Lenovo Phoenix [17aa:50d9]
  InstallationDate: Installed on 2023-10-04 (12 days ago)
  InstallationMedia: Ubuntu 23.04 "Lunar Lobster" - Release amd64 (20230418)
  MachineType: {report['dmi.sys.vendor']} {report['dmi.product.name']}
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-6.5.0-9-generic 
root=/dev/mapper/ubuntu--vg-ubuntu--lv ro quiet splash vt.handoff=7
  SourcePackage: xorg
  Symptom: display
  UpgradeStatus: Upgraded to mantic on 2023-10-15 (1 days ago)
  dmi.bios.date: 08/03/2023
  dmi.bios.release: 1.11
  dmi.bios.vendor: LENOVO
  dmi.bios.version: R2FET31W (1.11 )
  dmi.board.asset.tag: Not Available
  dmi.board.name: 21K4S02000
  dmi.board.vendor: LENOVO
  dmi.board.version: Not Defined
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: None
  dmi.ec.firmware.release: 1.9
  dmi.modalias: 
dmi:bvnLENOVO:bvrR2FET31W(1.11):bd08/03/2023:br1.11:efr1.9:svnLENOVO:pn21K4S02000:pvrThinkPadT14Gen4:rvnLENOVO:rn21K4S02000:rvrNotDefined:cvnLENOVO:ct10:cvrNone:skuLENOVO_MT_21K4_BU_Think_FM_ThinkPadT14Gen4:
  dmi.product.family: ThinkPad T14 Gen 4
  dmi.product.name: 21K4S02000
  dmi.product.sku: LENOVO_MT_21K4_BU_Think_FM_ThinkPad T14 Gen 4
  dmi.product.version: ThinkPad T14 Gen 4
  dmi.sys.vendor: LENOVO
  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.115-1
  version.libgl1-mesa-dri: libgl1-mesa-dri 23.2.1-1ubuntu3
  version.libgl1-mesa-glx: libgl1-mesa-glx N/A
  version.xserver-xorg-core: xserver-xorg-core 2:21.1.7-3ubuntu2
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-3
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20210115-1
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 
1:1.0.17-2build1

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/mutter/+bug/2039449/+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 2038998] Re: Screen artifacts/UI oddities on Wayland following Steam/Proton session

[Daniel van Vugt]

Also reported in:
https://gitlab.gnome.org/GNOME/gnome-shell/-/issues/7062

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

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

** Bug watch added: gitlab.gnome.org/GNOME/gnome-shell/-/issues #7062
   https://gitlab.gnome.org/GNOME/gnome-shell/-/issues/7062

** Tags added: amdgpu

** Summary changed:

- Screen artifacts/UI oddities on Wayland following Steam/Proton session
+ [amdgpu] Screen artifacts/UI oddities on Wayland following Steam/Proton 
session

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

Title:
  [amdgpu] Screen artifacts/UI oddities on Wayland following
  Steam/Proton session

Status in linux package in Ubuntu:
  New
Status in mesa package in Ubuntu:
  New

Bug description:
  Laptop is a Lenovo ThinkPad P14s Gen 2 AMD.
  Ryzen 7 PRO 5850U
  with Radeon (RX Vega 8?) integrated graphics
  16 GB RAM

  Running Ubuntu 23.10 (GNOME) from a clean install performed October 9,
  2023 from a daily-live/current .iso generated on October 4, 2023.

  Wayland
  Kernel 6.5.0-9-generic

  * * * * *

  Installed a pre-release build of Ubuntu 23.10 to my ThinkPad the other
  day, was going through setting up and testing the usual programs.

  Installed Steam through apt from the 'mantic' repositories. Installed
  Proton 8.0 and Steam Linux Runtime 3.0 (Sniper) alongside two
  compatible titles.

  Screen corruption (white and grey streaks) present in-game when GNOME
  UI elements appeared on-screen (e.g., volume, brightness, and keyboard
  backlight indicators) and omnipresent after closing either game.

  Artifacts remain on screen until log-out or reboot. Artifacts were not
  present beforehand.

  Artifacts only appeared in Wayland session; not X11/Xorg.

  I previously had been running the same games on Ubuntu 22.04 LTS
  (GNOME, Wayland) and Kubuntu 22.04 LTS (Plasma, X11/Xorg) on this
  computer without issue (kernel 6.2).

  * * * * *

  Please see subsequent posts for video/images.

  Happy to provide any other information as needed. Thanks!

  * * * * *

  ProblemType: Bug
  DistroRelease: Ubuntu 23.10
  Package: xorg 1:7.7+23ubuntu2
  ProcVersionSignature: Ubuntu 6.5.0-9.9-generic 6.5.3
  Uname: Linux 6.5.0-9-generic x86_64
  ApportVersion: 2.27.0-0ubuntu5
  Architecture: amd64
  BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
  CasperMD5CheckResult: unknown
  CompositorRunning: None
  CurrentDesktop: ubuntu:GNOME
  Date: Wed Oct 11 01:17:43 2023
  DistUpgraded: Fresh install
  DistroCodename: mantic
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes, if not too technical
  GraphicsCard:
   Advanced Micro Devices, Inc. [AMD/ATI] Cezanne [Radeon Vega Series / Radeon 
Vega Mobile Series] [1002:1638] (rev d1) (prog-if 00 [VGA controller])
     Subsystem: Lenovo Cezanne [Radeon Vega Series / Radeon Vega Mobile Series] 
[17aa:509b]
  MachineType: {report['dmi.sys.vendor']} {report['dmi.product.name']}
  ProcEnviron:
   LANG=en_US.UTF-8
   PATH=(custom, no user)
   SHELL=/bin/bash
   TERM=xterm-256color
   XDG_RUNTIME_DIR=
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-6.5.0-9-generic 
root=/dev/mapper/ubuntu--vg-ubuntu--lv ro quiet splash vt.handoff=7
  SourcePackage: xorg
  Symptom: display
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 05/15/2023
  dmi.bios.release: 1.24
  dmi.bios.vendor: LENOVO
  dmi.bios.version: R1MET54W (1.24 )
  dmi.board.asset.tag: Not Available
  dmi.board.name: 21A00068US
  dmi.board.vendor: LENOVO
  dmi.board.version: SDK0T76530 WIN
  dmi.chassis.asset.tag: No Asset Information
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: None
  dmi.ec.firmware.release: 1.24
  dmi.modalias: 
dmi:bvnLENOVO:bvrR1MET54W(1.24):bd05/15/2023:br1.24:efr1.24:svnLENOVO:pn21A00068US:pvrThinkPadP14sGen2a:rvnLENOVO:rn21A00068US:rvrSDK0T76530WIN:cvnLENOVO:ct10:cvrNone:skuLENOVO_MT_21A0_BU_Think_FM_ThinkPadP14sGen2a:
  dmi.product.family: ThinkPad P14s Gen 2a
  dmi.product.name: 21A00068US
  dmi.product.sku: LENOVO_MT_21A0_BU_Think_FM_ThinkPad P14s Gen 2a
  dmi.product.version: ThinkPad P14s Gen 2a
  dmi.sys.vendor: LENOVO
  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.115-1
  version.libgl1-mesa-dri: libgl1-mesa-dri 23.2.1-1ubuntu3
  version.libgl1-mesa-glx: libgl1-mesa-glx N/A
  version.xserver-xorg-core: xserver-xorg-core 2:21.1.7-3ubuntu2
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-3
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20210115-1
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 
1:1.0.17-2build1

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


-- 
Mailing list: 

[Touch-packages] [Bug 2038922] Re: Sudden screen crash

[Daniel van Vugt]

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

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

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

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

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



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

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

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

Title:
  Sudden screen crash

Status in Ubuntu:
  Incomplete

Bug description:
  All of the sudden screen started flickering and showing artifacts and
  after a few seconds got frozen.

  ProblemType: Bug
  DistroRelease: Ubuntu 22.04
  Package: xserver-xorg 1:7.7+23ubuntu2
  ProcVersionSignature: Ubuntu 6.2.0-34.34~22.04.1-generic 6.2.16
  Uname: Linux 6.2.0-34-generic x86_64
  ApportVersion: 2.20.11-0ubuntu82.5
  Architecture: amd64
  CasperMD5CheckResult: unknown
  CompositorRunning: None
  CurrentDesktop:
   
  Date: Tue Oct 10 15:46:11 2023
  DistUpgraded: Fresh install
  DistroCodename: jammy
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes
  GraphicsCard:
   Intel Corporation HD Graphics 620 [8086:5916] (rev 02) (prog-if 00 [VGA 
controller])
 Subsystem: Lenovo HD Graphics 620 [17aa:5062]
  InstallationDate: Installed on 2023-04-20 (172 days ago)
  InstallationMedia: Lubuntu 22.04.2 LTS "Jammy Jellyfish" - Release amd64 
(20230217.1)
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 003: ID 04ca:7066 Lite-On Technology Corp. Integrated Camera
   Bus 001 Device 002: ID 8087:0a2b Intel Corp. Bluetooth wireless interface
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: LENOVO 20HMS6XX00
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-6.2.0-34-generic 
root=UUID=63da9f00-db9b-478f-91b2-b370baa48314 ro quiet splash vt.handoff=7
  SourcePackage: xorg
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 11/18/2022
  dmi.bios.release: 1.47
  dmi.bios.vendor: LENOVO
  dmi.bios.version: R0IET69W (1.47 )
  dmi.board.asset.tag: Not Available
  dmi.board.name: 20HMS6XX00
  dmi.board.vendor: LENOVO
  dmi.board.version: Not Defined
  dmi.chassis.asset.tag: No Asset Information
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: None
  dmi.ec.firmware.release: 1.18
  dmi.modalias: 
dmi:bvnLENOVO:bvrR0IET69W(1.47):bd11/18/2022:br1.47:efr1.18:svnLENOVO:pn20HMS6XX00:pvrThinkPadX270:rvnLENOVO:rn20HMS6XX00:rvrNotDefined:cvnLENOVO:ct10:cvrNone:skuLENOVO_MT_20HM_BU_Think_FM_ThinkPadX270:
  dmi.product.family: ThinkPad X270
  dmi.product.name: 20HMS6XX00
  dmi.product.sku: LENOVO_MT_20HM_BU_Think_FM_ThinkPad X270
  dmi.product.version: ThinkPad X270
  dmi.sys.vendor: LENOVO
  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.113-2~ubuntu0.22.04.1
  version.libgl1-mesa-dri: libgl1-mesa-dri 23.0.4-0ubuntu1~22.04.1
  version.libgl1-mesa-glx: libgl1-mesa-glx 23.0.4-0ubuntu1~22.04.1
  version.xserver-xorg-core: xserver-xorg-core 2:21.1.4-2ubuntu1.7~22.04.1
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.10.6-2build1
  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/2038922/+subscriptions


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

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

[Chris Halse Rogers]

(SRU team member): It's not entirely clear to me what the status of this
bug is? It's marked as verification-done and all the autopkgtests are
clear, but there's a lot of “it doesn't work” chatter. Let's see if I
can summarise:

Werner seems to be seeing a hanging problem with 249.11-0ubuntu3.11.
Looking at the debug information, it seems that there's a *non*-ignored
interface present, and so they're not running into *this* bug, but are
probably hitting the same problem reported on the Pi images?

Shaun (#37) doesn't specify the version, but I infer that they're using
the version in -updates, not -proposed, so they're probably hitting the
bug this upload is fixing.

So I *think* the next step here would be to release *this* package to
-updates, as it seems to fix what it claims to fix without regressing
anything else *over what's already in -updates*, and then file *another*
bug (possibly against netplan?) to cover the “the real interface is
marked as optional: true, but there is another, unmanaged interface”
problem?

The assumption here is that this is *not* a regression over what's
already in -updates - @Werner, @Dave, can you confirm that?

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

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

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

Bug description:
  [NOTE]

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

  $ systemctl disable --now systemd-networkd.service

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

  [Impact]

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

  [Test Plan]

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

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

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

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

  3. Re-generate and apply the netplan configuration.

  $ netplan generate
  $ netplan apply

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

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

  [Where problems could occur]

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

  [Original Description]

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

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

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


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

[Touch-packages] [Bug 145604] Re: VRGB sub-pixel hinting causes black-on-black text rendering

[emadahmed687]

nice.
http://www.hairvitamins6.com
http://www.uaegoldpricetoday.com
http://www.saudigoldpricetoday.com

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

Title:
  VRGB sub-pixel hinting causes black-on-black text rendering

Status in libcairo:
  Unknown
Status in cairo package in Ubuntu:
  Triaged
Status in compiz package in Ubuntu:
  Invalid
Status in compiz-fusion-plugins-main package in Ubuntu:
  Invalid

Bug description:
  Binary package hint: libcairo2

  There is a long-standing problem (Gutsy, Hardy, Intrepid - possibly
  Jaunty too) with sub-pixel rendering which affects metacity or compiz
  composition (see the images attached to this bug) when VRGB is chosen
  as the sub-pixel format. Comment #15 by MoMaT demonstrates a non-
  compiz scenario. My comments #2 and #10 demonstrate the issue with
  Compiz enabled.

  The underlying issue essentially seems to be: where should sub-pixel
  rendering should be done - in libcairo or in the font renderer
  (FreeType in this case) ?

  There have been two versions of the Ubuntu patch in
  libcairo/libcairo2. Reports seem to suggest that both versions may be
  responsible for the VRGB problem (however, that supposition needs
  checking - see Bob McElrath's comment #19).

  We need to be aware that libcairo (libcairo 1.5.4 in Universe) and
  libcairo2 (cairo 1.6.0 in Main) are similarly patched and will need
  similar fixes.

To manage notifications about this bug go to:
https://bugs.launchpad.net/libcairo/+bug/145604/+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 164640] Re: Build Firefox 3 against a subpixel-patched cairo

[emadahmed687]

great work.
http://www.hairvitamins6.com
http://www.uaegoldpricetoday.com
http://www.saudigoldpricetoday.com

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

Title:
  Build Firefox 3 against a subpixel-patched cairo

Status in Fontconfig:
  Fix Released
Status in libcairo:
  Unknown
Status in fontconfig package in Ubuntu:
  Fix Released
Status in libcairo package in Ubuntu:
  Fix Released
Status in xulrunner-1.9 package in Ubuntu:
  Fix Released

Bug description:
  Binary package hint: firefox-3.0

  In Ubuntu 7.10 and newer, Firefox 3.0 looks out of place with subpixel
  rendering enabled, due to the fact that it uses an unpatched, bundled
  version of Cairo.

  The patch should be ported to Cairo 1.5 and applied in the firefox-3.0
  package.

To manage notifications about this bug go to:
https://bugs.launchpad.net/fontconfig/+bug/164640/+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 1639372] Re: CVE-2016-9082: DOS attack in converting SVG to PNG

[emadahmed687]

very good post.
http://www.hairvitamins6.com
http://www.uaegoldpricetoday.com
http://www.saudigoldpricetoday.com

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

Title:
  CVE-2016-9082: DOS attack in converting SVG to PNG

Status in cairo:
  Unknown
Status in cairo package in Ubuntu:
  Fix Released
Status in cairo source package in Precise:
  Won't Fix
Status in cairo source package in Trusty:
  Confirmed
Status in cairo source package in Xenial:
  Fix Released
Status in cairo source package in Yakkety:
  Confirmed
Status in cairo package in Debian:
  Fix Released

Bug description:
  I'm attaching debdiffs for trusty, xenial and yakkety. Zesty is
  already fixed by syncing cairo 1.14.6-1.1 from Debian. Maybe someone
  else can work on the precise update.

  Proof of Concept at
  http://seclists.org/oss-sec/2016/q4/44

  I didn't get gdb to work, but when I tried to convert the file, I got
  a crash report named /var/crash/_usr_bin_rsvg-convert.1000.crash .
  After the update, no crash happened.

  I reproduced the crash and verified that the new package doesn't crash
  on yakkety. In xenial I wasn't able to reproduce the crash. I did not
  test on trusty.

To manage notifications about this bug go to:
https://bugs.launchpad.net/cairo/+bug/1639372/+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 2039589] Re: Nwidia driver Ubuntu bug

[Alex Murray]

Thanks for taking the time to report this bug and helping to make Ubuntu
better. We appreciate the difficulties you are facing, but this appears
to be a "regular" (non-security) bug.  I have unmarked it as a security
issue since this bug does not show evidence of allowing attackers to
cross privilege boundaries nor directly cause loss of data/privacy.
Please feel free to report any other bugs you may find.

** Information type changed from Private Security to Public

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

Title:
  Nwidia driver Ubuntu bug

Status in xorg package in Ubuntu:
  New

Bug description:
  Nvidia driver error 470: UFW main window not displayed properly and
  Help not displayed. The issue affects Ubuntu 22.04.3 LTS, Ubuntu 23.10
  and Linux Mint.

  ProblemType: Bug
  DistroRelease: Ubuntu 22.04
  Package: xorg 1:7.7+23ubuntu2
  ProcVersionSignature: Ubuntu 6.2.0-34.34~22.04.1-generic 6.2.16
  Uname: Linux 6.2.0-34-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  .proc.driver.nvidia.capabilities.gpu0: Error: path was not a regular file.
  .proc.driver.nvidia.capabilities.mig: Error: path was not a regular file.
  .proc.driver.nvidia.gpus..01.00.0: Error: path was not a regular file.
  .proc.driver.nvidia.registry: Binary: ""
  .proc.driver.nvidia.suspend: suspend hibernate resume
  .proc.driver.nvidia.suspend_depth: default modeset uvm
  .proc.driver.nvidia.version:
   NVRM version: NVIDIA UNIX x86_64 Kernel Module  470.199.02  Thu May 11 
11:46:56 UTC 2023
   GCC version:
  ApportVersion: 2.20.11-0ubuntu82.5
  Architecture: amd64
  BootLog: Error: [Errno 13] Brak dostępu: '/var/log/boot.log'
  CasperMD5CheckResult: pass
  CompositorRunning: None
  CurrentDesktop: ubuntu:GNOME
  Date: Tue Oct 17 18:13:32 2023
  DistUpgraded: Fresh install
  DistroCodename: jammy
  DistroVariant: ubuntu
  GraphicsCard:
   NVIDIA Corporation GK107 [GeForce GTX 650] [10de:0fc6] (rev a1) (prog-if 00 
[VGA controller])
 Subsystem: CardExpert Technology GK107 [GeForce GTX 650] [10b0:0fc6]
  InstallationDate: Installed on 2023-10-16 (1 days ago)
  InstallationMedia: Ubuntu 22.04.3 LTS "Jammy Jellyfish" - Release amd64 
(20230807.2)
  MachineType: Gigabyte Technology Co., Ltd. To be filled by O.E.M.
  ProcEnviron:
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=pl_PL.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-6.2.0-34-generic 
root=UUID=7faab2db-29fa-4024-ae67-d6f019c15904 ro quiet splash vt.handoff=7
  SourcePackage: xorg
  Symptom: display
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 02/25/2014
  dmi.bios.release: 4.6
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 10b
  dmi.board.asset.tag: To be filled by O.E.M.
  dmi.board.name: H61M-S1
  dmi.board.vendor: Gigabyte Technology Co., Ltd.
  dmi.board.version: x.x
  dmi.chassis.asset.tag: To Be Filled By O.E.M.
  dmi.chassis.type: 3
  dmi.chassis.vendor: Gigabyte Technology Co., Ltd.
  dmi.chassis.version: To Be Filled By O.E.M.
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr10b:bd02/25/2014:br4.6:svnGigabyteTechnologyCo.,Ltd.:pnTobefilledbyO.E.M.:pvrTobefilledbyO.E.M.:rvnGigabyteTechnologyCo.,Ltd.:rnH61M-S1:rvrx.x:cvnGigabyteTechnologyCo.,Ltd.:ct3:cvrToBeFilledByO.E.M.:skuTobefilledbyO.E.M.:
  dmi.product.family: To be filled by O.E.M.
  dmi.product.name: To be filled by O.E.M.
  dmi.product.sku: To be filled by O.E.M.
  dmi.product.version: To be filled by O.E.M.
  dmi.sys.vendor: Gigabyte Technology Co., Ltd.
  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.113-2~ubuntu0.22.04.1
  version.libgl1-mesa-dri: libgl1-mesa-dri 23.0.4-0ubuntu1~22.04.1
  version.libgl1-mesa-glx: libgl1-mesa-glx N/A
  version.nvidia-graphics-drivers: nvidia-graphics-drivers-* N/A
  version.xserver-xorg-core: xserver-xorg-core 2:21.1.4-2ubuntu1.7~22.04.1
  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/2039589/+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