[Touch-packages] [Bug 1043298] Re: more information about errors on update failure
** Changed in: apt (Ubuntu) Status: Confirmed => Triaged -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to apt in Ubuntu. https://bugs.launchpad.net/bugs/1043298 Title: more information about errors on update failure Status in rapt: New Status in apt package in Ubuntu: Triaged Bug description: when i run apt-get update i get that error: W: GPG error: http://ppa.launchpad.net precise Release: The following signatures couldn't be verified because the public key is not available: NO_PUBKEY 99184AAECFB359B9 cause having a lot of LP repos enabled, i would appreciate if apt can give more information on the specific repo failed to be verified To manage notifications about this bug go to: https://bugs.launchpad.net/rapt/+bug/1043298/+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 2021956] Re: crash cups-proxyd
I'm getting this error on 23.10: cups-proxyd[2415]: segfault at 18 ip 55efd95e6d75 sp 7ffc3ee0d810 error 4 in cups-proxyd[55efd95e3000+7000] likely on CPU 1 (core 1, socket 0) ** Changed in: cups (Ubuntu) Status: Expired => New -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to cups in Ubuntu. https://bugs.launchpad.net/bugs/2021956 Title: crash cups-proxyd Status in cups package in Ubuntu: New Bug description: Ubuntu IOT Desktop 22.04 LTS # cat /etc/os-release PRETTY_NAME="Ubuntu 22.04.2 LTS" NAME="Ubuntu" VERSION_ID="22.04" VERSION="22.04.2 LTS (Jammy Jellyfish)" VERSION_CODENAME=jammy ID=ubuntu ID_LIKE=debian HOME_URL="https://www.ubuntu.com/"; SUPPORT_URL="https://help.ubuntu.com/"; BUG_REPORT_URL="https://bugs.launchpad.net/ubuntu/"; PRIVACY_POLICY_URL="https://www.ubuntu.com/legal/terms-and-policies/privacy-policy"; UBUNTU_CODENAME=jammy Kernel Version: 5.15.0-1028-intel-iotg # journalctl --no-hostname -b --no-pager | grep cups-proxyd mai 31 11:51:22 cups.cupsd[949]: + PROXY_DAEMON=cups-proxyd mai 31 11:51:22 cups.cupsd[3032]: exec cups-proxyd /var/snap/cups/common/run/cups.sock /run/cups/cups.sock -l --logdir /var/snap/cups/872/var/log mai 31 11:51:23 audit[3032]: SECCOMP auid=4294967295 uid=0 gid=0 ses=4294967295 subj=snap.cups.cupsd pid=3032 comm="cups-proxyd" exe="/snap/cups/872/sbin/cups-proxyd" sig=0 arch=c03e syscall=314 compat=0 ip=0x7fb050c2973d code=0x5 mai 31 11:51:23 kernel: audit: type=1326 audit(1685523083.773:85): auid=4294967295 uid=0 gid=0 ses=4294967295 subj=snap.cups.cupsd pid=3032 comm="cups-proxyd" exe="/snap/cups/872/sbin/cups-proxyd" sig=0 arch=c03e syscall=314 compat=0 ip=0x7fb050c2973d code=0x5 mai 31 11:51:24 kernel: cups-proxyd[3032]: segfault at 18 ip 558e95990d6e sp 7ffe2436a230 error 4 in cups-proxyd[558e9598d000+7000] Error: cups-proxyd[3032]: segfault at 18 ip 558e95990d6e sp 7ffe2436a230 error 4 in cups-proxyd[558e9598d000+7000] Snap list: # snap list Name Version RevTracking Publisher Notes bare 1.0 5 latest/stable canonical✓ base chromium 113.0.5672.1262477 latest/stable canonical✓ - core20 20230503 1891 latest/stable canonical✓ base core22 20230503 634latest/stable canonical✓ base cups 2.4.2-5 872latest/stable openprinting✓ - firefox111.0-2 2432 latest/stable/… mozilla✓ - gnome-3-38-20040+git.6f39565 140latest/stable/… canonical✓ - gnome-42-2204 0+git.587e965 102latest/stable canonical✓ - gtk-common-themes 0.1-81-g442e511 1535 latest/stable/… canonical✓ - snap-store 41.3-71-g709398e 959latest/stable/… canonical✓ - snapd 2.59.219122 latest/stable canonical✓ snapd snapd-desktop-integration 0.9 83 latest/stable/… canonical✓ - Reproduced: At every boot OS To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/cups/+bug/2021956/+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 2045245] [NEW] ubuntu22.04 ibus Chinese pinying input not response
Public bug reported: I have used 22.04 many times, and I encountered this problem every time. During the first period of installing the system, everything was fine, but once I used the system for more than a few months, the ibus started to stop responding and I could not enter. There is no response when pressing any keys on the keyboard. The only solution is to manually click the input method icon in the upper right corner, switch to English, and then enter `ibus restart`. But this problem of input method not responding is too frequent and occurs every few minutes. I can't stand this torture anymore, and I now use a third-party input method. ** Affects: ibus (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to ibus in Ubuntu. https://bugs.launchpad.net/bugs/2045245 Title: ubuntu22.04 ibus Chinese pinying input not response Status in ibus package in Ubuntu: New Bug description: I have used 22.04 many times, and I encountered this problem every time. During the first period of installing the system, everything was fine, but once I used the system for more than a few months, the ibus started to stop responding and I could not enter. There is no response when pressing any keys on the keyboard. The only solution is to manually click the input method icon in the upper right corner, switch to English, and then enter `ibus restart`. But this problem of input method not responding is too frequent and occurs every few minutes. I can't stand this torture anymore, and I now use a third-party input method. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ibus/+bug/2045245/+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
Apparently you need to have libnvidia-egl-gbm1 for the fix to work? I'm not so sure about that because I verified the fix on 23.10 and it looks like libnvidia-egl-gbm1 wasn't installed. -- 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: Invalid Status in gnome-online-accounts package in Ubuntu: Invalid Status in webkit2gtk package in Ubuntu: Fix Released Status in yelp package in Ubuntu: Invalid 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
[Touch-packages] [Bug 2029464] Re: A stack overflow in GNU Tar
Yes, they reserved one, but with no details: https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2023-39804 Feel free to assign a different one with information about the issue, or update the already reserved CVE number. ** CVE added: https://cve.mitre.org/cgi-bin/cvename.cgi?name=2023-39804 -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to tar in Ubuntu. https://bugs.launchpad.net/bugs/2029464 Title: A stack overflow in GNU Tar Status in tar package in Ubuntu: New Bug description: A stack overflow vulnerability exists in GNU Tar up to including v1.34, as far as I can see, Ubuntu is using v1.3. The bug exists in the function xattr_decoder() in xheader.c, where alloca() is used and it may overflow the stack if a sufficiently long xattr key is used. The vulnerability can be triggered when extracting a tar/pax archive that contains such a long xattr key. Vulnerable code: https://git.savannah.gnu.org/cgit/tar.git/tree/src/xheader.c?h=release_1_34#n1723 PoC tar archive is attached in a zip archive to reduce the size. I reported the vulnerability yesterday to GNU Tar maintainers and they replied that the issue was fixed in the version that was released two weeks ago: "Sergey fixed that bug here: https://git.savannah.gnu.org/cgit/tar.git/commit/?id=a339f05cd269013fa133d2f148d73f6f7d4247e4 and the fix appears in tar 1.35, released July 18. " To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/tar/+bug/2029464/+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 2045250] [NEW] pam_lastlog doesn't handle localtime_r related errors properly
Public bug reported:
The pam version(s) in Debian (checked buster) and Ubuntu (checked focal to
noble) are affected by
https://bugzilla.redhat.com/show_bug.cgi?id=2012871
Customers report a command going through PAM crashing for a given user.
A potential follow on issue can be that no ssh remote connections to an
affected server are possible anymore, esp. painful with headless systems (was
reported on a different distro).
This is caused by an issue in modules/pam_lastlog/pam_lastlog.c:
with tm = localtime_r(...) that can be NULL and needs to be handled.
There are two such cases in modules/pam_lastlog/pam_lastlog.c (here noble):
314-ll_time = last_login.ll_time;
315:if ((tm = localtime_r (&ll_time, &tm_buf)) != NULL) {
316-strftime (the_time, sizeof (the_time),
317-/* TRANSLATORS: "strftime options for date of last
login" */
--
574-
575-lf_time = utuser.ut_tv.tv_sec;
576:tm = localtime_r (&lf_time, &tm_buf);
577-strftime (the_time, sizeof (the_time),
578-/* TRANSLATORS: "strftime options for date of last login" */
Case 1 (line 315) is properly handled, but not case 2 (line 576).
The second case got fixed by:
https://github.com/linux-pam/linux-pam/commit/40c271164dbcebfc5304d0537a42fb42e6b6803c
This fix should be included in Ubuntu (and Debian).
** Affects: pam (Ubuntu)
Importance: Undecided
Status: New
** Affects: pam (Fedora)
Importance: Unknown
Status: Unknown
** Tags: rls-ff-incoming rls-jj-incoming rls-ll-incoming rls-mm-incoming
rls-nn-incoming
** Bug watch added: Red Hat Bugzilla #2012871
https://bugzilla.redhat.com/show_bug.cgi?id=2012871
** Also affects: pam (Fedora) via
https://bugzilla.redhat.com/show_bug.cgi?id=2012871
Importance: Unknown
Status: Unknown
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to pam in Ubuntu.
https://bugs.launchpad.net/bugs/2045250
Title:
pam_lastlog doesn't handle localtime_r related errors properly
Status in pam package in Ubuntu:
New
Status in pam package in Fedora:
Unknown
Bug description:
The pam version(s) in Debian (checked buster) and Ubuntu (checked focal to
noble) are affected by
https://bugzilla.redhat.com/show_bug.cgi?id=2012871
Customers report a command going through PAM crashing for a given user.
A potential follow on issue can be that no ssh remote connections to an
affected server are possible anymore, esp. painful with headless systems (was
reported on a different distro).
This is caused by an issue in modules/pam_lastlog/pam_lastlog.c:
with tm = localtime_r(...) that can be NULL and needs to be handled.
There are two such cases in modules/pam_lastlog/pam_lastlog.c (here noble):
314- ll_time = last_login.ll_time;
315: if ((tm = localtime_r (&ll_time, &tm_buf)) != NULL) {
316- strftime (the_time, sizeof (the_time),
317- /* TRANSLATORS: "strftime options for date of last
login" */
--
574-
575- lf_time = utuser.ut_tv.tv_sec;
576: tm = localtime_r (&lf_time, &tm_buf);
577- strftime (the_time, sizeof (the_time),
578- /* TRANSLATORS: "strftime options for date of last login" */
Case 1 (line 315) is properly handled, but not case 2 (line 576).
The second case got fixed by:
https://github.com/linux-pam/linux-pam/commit/40c271164dbcebfc5304d0537a42fb42e6b6803c
This fix should be included in Ubuntu (and Debian).
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/pam/+bug/2045250/+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 2045250] Re: pam_lastlog doesn't handle localtime_r related errors properly
Launchpad has imported 5 comments from the remote bug at
https://bugzilla.redhat.com/show_bug.cgi?id=2012871.
If you reply to an imported comment from within Launchpad, your comment
will be sent to the remote bug automatically. Read more about
Launchpad's inter-bugtracker facilities at
https://help.launchpad.net/InterBugTracking.
On 2021-10-11T13:47:24+00:00 rmetrich wrote:
Description of problem:
We got a customer report of a command going through PAM crashing for a given
user.
It appears that the pam_lastlog code doesn't check the result of localtime_r(),
which leads to crashing in glibc's strftime():
~~~
494 static int
495 last_login_failed(pam_handle_t *pamh, int announce, const char *user,
time_t lltime)
496 {
:
502 char the_time[256];
:
535 if (failed) {
536 /* we want the date? */
537 if (announce & LASTLOG_DATE) {
538 struct tm *tm, tm_buf;
539 time_t lf_time;
540
541 lf_time = utuser.ut_tv.tv_sec;
542 tm = localtime_r (&lf_time, &tm_buf);
543 strftime (the_time, sizeof (the_time),
544 /* TRANSLATORS: "strftime options for date of last login" */
545 _(" %a %b %e %H:%M:%S %Z %Y"), tm);
546
547 date = the_time;
548 }
~~~
Here above, assuming "lf_time" is very large, due to a corruption in btmp
database, this leads to:
1. having "tm" = NULL
2. calling strftime(..., NULL), which crashes
Hence, checking the result is mandatory.
Version-Release number of selected component (if applicable):
PAM from RHEL7 and later
How reproducible:
Don't know, need to have a corrupted "btmp" entry
Reply at:
https://bugs.launchpad.net/ubuntu/+source/pam/+bug/2045250/comments/0
On 2021-10-18T07:08:52+00:00 ipedrosa wrote:
It would help us if you could ask the customer for the reproduction
steps
Reply at:
https://bugs.launchpad.net/ubuntu/+source/pam/+bug/2045250/comments/1
On 2021-10-18T07:51:50+00:00 rmetrich wrote:
The customer gave me his btmp database but unfortunately I couldn't
reproduce with it either: PAM was detecting the corruption for me,
whereas not for the customer.
Reply at:
https://bugs.launchpad.net/ubuntu/+source/pam/+bug/2045250/comments/2
On 2022-09-27T09:22:53+00:00 ipedrosa wrote:
master:
pam_lastlog: check localtime_r() return value -
40c271164dbcebfc5304d0537a42fb42e6b6803c
Reply at:
https://bugs.launchpad.net/ubuntu/+source/pam/+bug/2045250/comments/3
On 2023-05-16T09:02:48+00:00 errata-xmlrpc wrote:
Since the problem described in this bug report should be
resolved in a recent advisory, it has been closed with a
resolution of ERRATA.
For information on the advisory (pam bug fix and enhancement update), and where
to find the updated
files, follow the link below.
If the solution does not work for you, open a new bug report.
https://access.redhat.com/errata/RHBA-2023:2954
Reply at:
https://bugs.launchpad.net/ubuntu/+source/pam/+bug/2045250/comments/4
** Changed in: pam (Fedora)
Status: Unknown => Fix Released
** Changed in: pam (Fedora)
Importance: Unknown => High
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to pam in Ubuntu.
https://bugs.launchpad.net/bugs/2045250
Title:
pam_lastlog doesn't handle localtime_r related errors properly
Status in pam package in Ubuntu:
New
Status in pam package in Fedora:
Fix Released
Bug description:
The pam version(s) in Debian (checked buster) and Ubuntu (checked focal to
noble) are affected by
https://bugzilla.redhat.com/show_bug.cgi?id=2012871
Customers report a command going through PAM crashing for a given user.
A potential follow on issue can be that no ssh remote connections to an
affected server are possible anymore, esp. painful with headless systems (was
reported on a different distro).
This is caused by an issue in modules/pam_lastlog/pam_lastlog.c:
with tm = localtime_r(...) that can be NULL and needs to be handled.
There are two such cases in modules/pam_lastlog/pam_lastlog.c (here noble):
314- ll_time = last_login.ll_time;
315: if ((tm = localtime_r (&ll_time, &tm_buf)) != NULL) {
316- strftime (the_time, sizeof (the_time),
317- /* TRANSLATORS: "strftime options for date of last
login" */
--
574-
575- lf_time = utuser.ut_tv.tv_sec;
576: tm = localtime_r (&lf_time, &tm_buf);
577- strftime (the_time, sizeof (the_time),
578- /* TRANSLATORS: "strftime options for date of last login" */
Case 1 (line 315) is properly
[Touch-packages] [Bug 2045245] Re: ubuntu22.04 ibus Chinese pinying input not response
Thanks for your report. It's hard to comment on without more info. Possibly there is a need to clean the cache in ~/.cache/ibus/libpinyin . ** Changed in: ibus (Ubuntu) Status: New => Incomplete -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to ibus in Ubuntu. https://bugs.launchpad.net/bugs/2045245 Title: ubuntu22.04 ibus Chinese pinying input not response Status in ibus package in Ubuntu: Incomplete Bug description: I have used 22.04 many times, and I encountered this problem every time. During the first period of installing the system, everything was fine, but once I used the system for more than a few months, the ibus started to stop responding and I could not enter. There is no response when pressing any keys on the keyboard. The only solution is to manually click the input method icon in the upper right corner, switch to English, and then enter `ibus restart`. But this problem of input method not responding is too frequent and occurs every few minutes. I can't stand this torture anymore, and I now use a third-party input method. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ibus/+bug/2045245/+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 2044304] Re: Apparmor crashes GPU acceleration in Firefox 120
Status changed to 'Confirmed' because the bug affects multiple users.
** Changed in: apparmor (Ubuntu)
Status: New => Confirmed
--
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/2044304
Title:
Apparmor crashes GPU acceleration in Firefox 120
Status in apparmor package in Ubuntu:
Confirmed
Bug description:
$ lsb_release -rd
Description: Ubuntu 22.04.3 LTS
Release: 22.04
$ apt-cache policy apparmor
apparmor:
Installed: 3.0.4-2ubuntu2.3
Candidate: 3.0.4-2ubuntu2.3
Version table:
*** 3.0.4-2ubuntu2.3 500 (phased 20%)
500 http://us.archive.ubuntu.com/ubuntu jammy-updates/main amd64
Packages
100 /var/lib/dpkg/status
3.0.4-2ubuntu2 500
500 http://us.archive.ubuntu.com/ubuntu jammy/main amd64 Packages
$ apt-cache policy firefox
firefox:
Installed: 120.0+build2-0ubuntu0.22.04.1~mt1
Candidate: 120.0+build2-0ubuntu0.22.04.1~mt1
Version table:
1:1snap1-0ubuntu2 -1
500 http://us.archive.ubuntu.com/ubuntu jammy/main amd64 Packages
*** 120.0+build2-0ubuntu0.22.04.1~mt1 1001
1001 https://ppa.launchpadcontent.net/mozillateam/ppa/ubuntu
jammy/main amd64 Packages
100 /var/lib/dpkg/status
$ apt-cache policy libglx-mesa0
libglx-mesa0:
Installed: 23.0.4-0ubuntu1~22.04.1
Candidate: 23.0.4-0ubuntu1~22.04.1
Version table:
*** 23.0.4-0ubuntu1~22.04.1 500
500 http://us.archive.ubuntu.com/ubuntu jammy-updates/main amd64
Packages
100 /var/lib/dpkg/status
22.0.1-1ubuntu2 500
500 http://us.archive.ubuntu.com/ubuntu jammy/main amd64 Packages
Firefox Apparmor profile seems out of date and needs extra
permissions.
The issue started happening in Firefox version 120 after an upgrade
from 119.0.1.
I do see the lots of DENIED Apparmor errors before the freeze/crash:
AVC apparmor="DENIED" operation="open" class="file" profile="firefox"
name="/sys/devices/pci:00/:00:01.0/:01:00.0/config" pid=11949
comm="firefox" requested_mask="r" denied_mask="r" fsuid=1000 ouid=0
AVC apparmor="DENIED" operation="open" class="file" profile="firefox"
name="/sys/devices/pci:00/:00:01.0/:01:00.0/revision"
pid=11949 comm="firefox" requested_mask="r" denied_mask="r" fsuid=1000
ouid=0
AVC apparmor="DENIED" operation="open" class="file" profile="firefox"
name="/proc/34029/cgroup" pid=34029
comm=49736F6C617465642057656220436F requested_mask="r" denied_mask="r"
fsuid=1000 ouid=1000
MESA: error: Failed to query drm device.
libEGL warning: egl: failed to create dri2 screen
Adding the following the following permissions to
/etc/apparmor.d/local/usr.bin.firefox seems to mitigate the issue:
/sys/devices/pci*/**/{config,revision} r,
@{PROC}/[0-9]*/**/comm r,
@{PROC}/[0-9]*/**/oom_score_adj w,
Disabling the firefox profile also mitigates the issue. It seems the
profile needs an update to include permissions required by Firefox
120.
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/apparmor/+bug/2044304/+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 2044304] Re: Apparmor crashes GPU acceleration in Firefox 120
thanks for this report and solution, very strange that FF uses dri/mesa
when hw-acceleration is disabled (yes, i unchecked both checkboxes).
i had this issue reproducable on google-login (drive.google.com) with
clean new profile without extensions
i can verify that the change in usr.bin.firefox file and restarting
apparmor solves this issue
--
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/2044304
Title:
Apparmor crashes GPU acceleration in Firefox 120
Status in apparmor package in Ubuntu:
Confirmed
Bug description:
$ lsb_release -rd
Description: Ubuntu 22.04.3 LTS
Release: 22.04
$ apt-cache policy apparmor
apparmor:
Installed: 3.0.4-2ubuntu2.3
Candidate: 3.0.4-2ubuntu2.3
Version table:
*** 3.0.4-2ubuntu2.3 500 (phased 20%)
500 http://us.archive.ubuntu.com/ubuntu jammy-updates/main amd64
Packages
100 /var/lib/dpkg/status
3.0.4-2ubuntu2 500
500 http://us.archive.ubuntu.com/ubuntu jammy/main amd64 Packages
$ apt-cache policy firefox
firefox:
Installed: 120.0+build2-0ubuntu0.22.04.1~mt1
Candidate: 120.0+build2-0ubuntu0.22.04.1~mt1
Version table:
1:1snap1-0ubuntu2 -1
500 http://us.archive.ubuntu.com/ubuntu jammy/main amd64 Packages
*** 120.0+build2-0ubuntu0.22.04.1~mt1 1001
1001 https://ppa.launchpadcontent.net/mozillateam/ppa/ubuntu
jammy/main amd64 Packages
100 /var/lib/dpkg/status
$ apt-cache policy libglx-mesa0
libglx-mesa0:
Installed: 23.0.4-0ubuntu1~22.04.1
Candidate: 23.0.4-0ubuntu1~22.04.1
Version table:
*** 23.0.4-0ubuntu1~22.04.1 500
500 http://us.archive.ubuntu.com/ubuntu jammy-updates/main amd64
Packages
100 /var/lib/dpkg/status
22.0.1-1ubuntu2 500
500 http://us.archive.ubuntu.com/ubuntu jammy/main amd64 Packages
Firefox Apparmor profile seems out of date and needs extra
permissions.
The issue started happening in Firefox version 120 after an upgrade
from 119.0.1.
I do see the lots of DENIED Apparmor errors before the freeze/crash:
AVC apparmor="DENIED" operation="open" class="file" profile="firefox"
name="/sys/devices/pci:00/:00:01.0/:01:00.0/config" pid=11949
comm="firefox" requested_mask="r" denied_mask="r" fsuid=1000 ouid=0
AVC apparmor="DENIED" operation="open" class="file" profile="firefox"
name="/sys/devices/pci:00/:00:01.0/:01:00.0/revision"
pid=11949 comm="firefox" requested_mask="r" denied_mask="r" fsuid=1000
ouid=0
AVC apparmor="DENIED" operation="open" class="file" profile="firefox"
name="/proc/34029/cgroup" pid=34029
comm=49736F6C617465642057656220436F requested_mask="r" denied_mask="r"
fsuid=1000 ouid=1000
MESA: error: Failed to query drm device.
libEGL warning: egl: failed to create dri2 screen
Adding the following the following permissions to
/etc/apparmor.d/local/usr.bin.firefox seems to mitigate the issue:
/sys/devices/pci*/**/{config,revision} r,
@{PROC}/[0-9]*/**/comm r,
@{PROC}/[0-9]*/**/oom_score_adj w,
Disabling the firefox profile also mitigates the issue. It seems the
profile needs an update to include permissions required by Firefox
120.
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/apparmor/+bug/2044304/+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 2038433] Re: systemd autopkgtest regression on arm64 and s390x on mantic
A couple of retries and the test finally passes. There's some flakiness.
--
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/2038433
Title:
systemd autopkgtest regression on arm64 and s390x on mantic
Status in linux package in Ubuntu:
Confirmed
Status in systemd package in Ubuntu:
New
Status in linux source package in Mantic:
Confirmed
Status in systemd source package in Mantic:
New
Bug description:
tests-in-lxd seems to fail to download the lxd image used for the test (or
something similar), looking at the log:
...
Publishing instance: Image pack: 85% (5.51MB/s)
Instance published with fingerprint:
83b511be44395f2afc7d4d1ee0708cb18834c8b15cb208c9d218964ed8479114
6845s autopkgtest [09:11:14]: starting date and time: 2023-10-03 09:11:14+
6845s autopkgtest [09:11:14]: version 5.28ubuntu1
6845s autopkgtest [09:11:14]: host autopkgtest; command line:
/usr/bin/autopkgtest -U -B . --test-name=unit-tests -- lxd
autopkgtest/ubuntu/mantic/arm64
7063s : failure: (down) ['mktemp', '--directory', '--tmpdir',
'autopkgtest.XX'] failed (exit status 1, stderr '')
7063s autopkgtest [09:14:52]: ERROR: testbed failure: unexpected eof from the
testbed
7063s autopkgtest [09:14:52]: test tests-in-lxd: ---]
7064s autopkgtest [09:14:53]: test tests-in-lxd: - - - - - - - - - - results
- - - - - - - - - -
7064s tests-in-lxd FAIL non-zero exit status 1
2:40 PM
...
This introduces a regression that is blocking the promotion of new
kernels in Mantic.
ProblemType: Bug
DistroRelease: Ubuntu 23.10
Package: systemd 253.5-1ubuntu6
ProcVersionSignature: Ubuntu 6.5.0-5.5.1-lowlatency 6.5.0
Uname: Linux 6.5.0-5-lowlatency x86_64
ApportVersion: 2.27.0-0ubuntu4
Architecture: amd64
CasperMD5CheckResult: pass
CurrentDesktop: ubuntu:GNOME
Date: Wed Oct 4 14:38:15 2023
InstallationDate: Installed on 2023-09-25 (9 days ago)
InstallationMedia: Ubuntu 23.10 "Mantic Minotaur" - Beta amd64 (20230924)
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-5-lowlatency
root=/dev/mapper/ubuntu--vg-ubuntu--lv ro quiet splash vt.handoff=7
SourcePackage: systemd
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 09/01/2022
dmi.bios.release: 5.19
dmi.bios.vendor: American Megatrends International, LLC.
dmi.bios.version: 2.04
dmi.board.asset.tag: Default string
dmi.board.name: G1621-02
dmi.board.vendor: GPD
dmi.board.version: Default string
dmi.chassis.asset.tag: Default string
dmi.chassis.type: 10
dmi.chassis.vendor: Default string
dmi.chassis.version: Default string
dmi.ec.firmware.release: 2.3
dmi.modalias:
dmi:bvnAmericanMegatrendsInternational,LLC.:bvr2.04:bd09/01/2022:br5.19:efr2.3:svnGPD:pnG1621-02:pvrDefaultstring:rvnGPD:rnG1621-02:rvrDefaultstring:cvnDefaultstring:ct10:cvrDefaultstring:skuDefaultstring:
dmi.product.family: Default string
dmi.product.name: G1621-02
dmi.product.sku: Default string
dmi.product.version: Default string
dmi.sys.vendor: GPD
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2038433/+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 1827154] Re: [wacom] gnome-control-center crashed with SIGSEGV in _gdk_event_queue_handle_motion_compression()
** Changed in: gnome-control-center Status: New => Fix Released -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to gtk+3.0 in Ubuntu. https://bugs.launchpad.net/bugs/1827154 Title: [wacom] gnome-control-center crashed with SIGSEGV in _gdk_event_queue_handle_motion_compression() Status in gnome-control-center: Fix Released Status in gnome-control-center package in Ubuntu: Triaged Status in gtk+3.0 package in Ubuntu: Triaged Bug description: https://gitlab.gnome.org/GNOME/gnome-control-center/issues/503 --- [Impact] When I try to set the pen on my touch screen. gnome-control-center crashes. [Fix] That you can configure the pencil to later occupy it with my touch screen. [Test Case] 1. Open gnome-control-center 2. Click on Wacom tablet 3. Press the buttons of the pencil, touching the screen 4. gnome-control-center crashes ProblemType: Bug DistroRelease: Ubuntu 19.10 Package: gnome-control-center 1:3.32.1-1ubuntu5 Uname: Linux 5.1.0-050100rc7-generic x86_64 ApportVersion: 2.20.10-0ubuntu27 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Tue Apr 30 19:28:42 2019 InstallationDate: Installed on 2018-12-02 (149 days ago) InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 (20180725) SourcePackage: gnome-control-center UpgradeStatus: Upgraded to eoan on 2018-12-02 (149 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-control-center/+bug/1827154/+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 1813581] Re: gpgme1.0 ftbfs in 18.04 LTS
can you please move such updates into esm-proposed instead? -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to gpgme1.0 in Ubuntu. https://bugs.launchpad.net/bugs/1813581 Title: gpgme1.0 ftbfs in 18.04 LTS Status in gpgme1.0 package in Ubuntu: Fix Released Status in gpgme1.0 source package in Bionic: Won't Fix Bug description: [Impact] according to http://people.canonical.com/~doko/ftbfs-report/test-rebuild-20181222-bionic.html gpgme1.0 ftbfs. * Start testing of TofuInfoTest * Config: Using QtTest library 5.9.5, Qt 5.9.5 (x86_64-little_endian-lp64 shared (dynamic) release build; by GCC 7.3.0) PASS : TofuInfoTest::initTestCase() PASS : TofuInfoTest::testTofuNull() PASS : TofuInfoTest::testTofuInfo() PASS : TofuInfoTest::testTofuSignCount() PASS : TofuInfoTest::testTofuKeyList() PASS : TofuInfoTest::testTofuPolicy() FAIL! : TofuInfoTest::testTofuConflict() 'sig.validity() == Signature::Marginal' returned FALSE. () Loc: [t-tofuinfo.cpp(458)] PASS : TofuInfoTest::cleanupTestCase() Totals: 7 passed, 1 failed, 0 skipped, 0 blacklisted, 2386ms * Finished testing of TofuInfoTest * FAIL: t-tofuinfo [Test case] build it [Regression potential] This only changes the test suite run during build, and that one currently fails, so it can't cause any regression. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gpgme1.0/+bug/1813581/+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 2045250] Re: pam_lastlog doesn't handle localtime_r related errors properly
** Tags removed: rls-ff-incoming rls-jj-incoming rls-ll-incoming
rls-mm-incoming rls-nn-incoming
** Tags added: foundations-todo
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to pam in Ubuntu.
https://bugs.launchpad.net/bugs/2045250
Title:
pam_lastlog doesn't handle localtime_r related errors properly
Status in pam package in Ubuntu:
New
Status in pam package in Fedora:
Fix Released
Bug description:
The pam version(s) in Debian (checked buster) and Ubuntu (checked focal to
noble) are affected by
https://bugzilla.redhat.com/show_bug.cgi?id=2012871
Customers report a command going through PAM crashing for a given user.
A potential follow on issue can be that no ssh remote connections to an
affected server are possible anymore, esp. painful with headless systems (was
reported on a different distro).
This is caused by an issue in modules/pam_lastlog/pam_lastlog.c:
with tm = localtime_r(...) that can be NULL and needs to be handled.
There are two such cases in modules/pam_lastlog/pam_lastlog.c (here noble):
314- ll_time = last_login.ll_time;
315: if ((tm = localtime_r (&ll_time, &tm_buf)) != NULL) {
316- strftime (the_time, sizeof (the_time),
317- /* TRANSLATORS: "strftime options for date of last
login" */
--
574-
575- lf_time = utuser.ut_tv.tv_sec;
576: tm = localtime_r (&lf_time, &tm_buf);
577- strftime (the_time, sizeof (the_time),
578- /* TRANSLATORS: "strftime options for date of last login" */
Case 1 (line 315) is properly handled, but not case 2 (line 576).
The second case got fixed by:
https://github.com/linux-pam/linux-pam/commit/40c271164dbcebfc5304d0537a42fb42e6b6803c
This fix should be included in Ubuntu (and Debian).
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/pam/+bug/2045250/+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 2041518] Re: /usr/share/apport/apport-gtk:5:_g_log_abort:g_log_writer_default:g_log_structured_array:g_log_structured_array:g_log_structured_standard
Is desktop aware this is for desktop to solve on gtk+3.0 side first? -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to apport in Ubuntu. https://bugs.launchpad.net/bugs/2041518 Title: /usr/share/apport/apport- gtk:5:_g_log_abort:g_log_writer_default:g_log_structured_array:g_log_structured_array:g_log_structured_standard Status in apport package in Ubuntu: New Status in gtk+3.0 package in Ubuntu: New Bug description: The Ubuntu Error Tracker has been receiving reports about a problem regarding apport. This problem was most recently seen with package version 2.27.0-0ubuntu5, the problem page at https://errors.ubuntu.com/problem/196d97dec8fe94e52eebaf9e7da150d1629a1e05 contains more details, including versions of packages affected, stacktrace or traceback, and individual crash reports. If you do not have access to the Ubuntu Error Tracker and are a software developer, you can request it at http://forms.canonical.com/reports/. g_log_structured_standard (log_domain=log_domain@entry=0x7f7fa9a12014 "Gtk", log_level=log_level@entry=G_LOG_LEVEL_ERROR, file=file@entry=0x7f7fa9a4e7c0 "../../../gtk/gtkstylecontext.c", line=line@entry=0x7f7fa9a1a381 "348", func=func@entry=0x7f7fa9a849a0 <__func__.70> "gtk_style_context_init", message_format=message_format@entry=0x7f7fa9a4edf0 "Can't create a GtkStyleContext without a display connection") This crash is probably a different variant of bug #1842439 but I cannot reproduce this crash (by running "killall -11 gnome-shell" on a mantic system). This bug is the top 1 apport bug in Ubuntu 23.10 (mantic). To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apport/+bug/2041518/+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 2041831] Re: /usr/bin/update-manager:11:g_type_check_instance_is_fundamentally_a:g_object_ref:gdk_event_copy:pygi_boxed_copy_in_place:arg_boxed_to_py_cleanup
I believe this seems like a pygobject issue for desktop to investigate, probably a type declared wrong somewhere? -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to pygobject in Ubuntu. https://bugs.launchpad.net/bugs/2041831 Title: /usr/bin/update- manager:11:g_type_check_instance_is_fundamentally_a:g_object_ref:gdk_event_copy:pygi_boxed_copy_in_place:arg_boxed_to_py_cleanup Status in pygobject package in Ubuntu: New Status in update-manager package in Ubuntu: New Bug description: The Ubuntu Error Tracker has been receiving reports about a problem regarding update-manager. This problem was most recently seen with package version 1:23.10.1, the problem page at https://errors.ubuntu.com/problem/dff72cd5c27c916b2d887a56311ba08ef15b0dff contains more details, including versions of packages affected, stacktrace or traceback, and individual crash reports. If you do not have access to the Ubuntu Error Tracker and are a software developer, you can request it at http://forms.canonical.com/reports/. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/pygobject/+bug/2041831/+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 2039083] Re: "optional: true" flag introduces problem it's meant to fix in certain circumstances
Lukas - upstream is actually broken in v253 until v253.6, and the reason it appears "OK" in v253.5 (which we have in Mantic) is that [1] introduces a bug upstream that makes systemd-networkd-wait-online behave similarly to Ubuntu's patched systemd-networkd-wait-online prior to systemd 249.11-0ubuntu3.10. Since (a) there has been lots of churn in this area already with SRUs and bug reports, and (b) we really need to implement our network-online spec to *really* fix this, I decided to leave it alone for Mantic. Isaac - what happens if you add the --any flag to systemd-networkd-wait- online.service (best to do this with an override config), e.g. # /etc/systemd/system/systemd-networkd-wait-online.service.d/override.conf [Service] ExecStart= ExecStart=/lib/systemd/systemd-networkd-wait-online --any That should make it so that it does not wait on all the other unmanaged interfaces. I realize this is a change in behavior in Jammy, but the old behavior systemd-networkd-wait-online was worse in my opinion. It's "wrong" to run systemd-networkd-wait-online without arguments on a system where not everything is managed by systemd-networkd, so I think the best solution for users in Isaac's situation is to add overrides that work for their setup. [1] https://github.com/systemd/systemd/commit/ab3aed4a0349bbaa26f53340770c1b59b463e05d ** Changed in: systemd (Ubuntu) Status: Confirmed => Incomplete ** Tags removed: rls-jj-incoming -- 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/2039083 Title: "optional: true" flag introduces problem it's meant to fix in certain circumstances Status in netplan: Invalid Status in systemd package in Ubuntu: Incomplete Bug description: Hello! This bug is in relation to the situation where the "systemd-networkd- wait-online.service" hangs for several minutes on boot before eventually failing. I guess I don't know if this flag was introduced specifically for this situation, but I do know that one of the fixes for this issue is to add "optional: true" to any non-critical interfaces (as per the docs[1]). While this may be the case, it just so happens that adding this flag to an interface when it's the only configured interface in netplan can actually INTRODUCE the issue as well. Example: --- :~# grep -Ev "^#" /etc/netplan/50-cloud-init.yaml network: version: 2 ethernets: enp5s0: dhcp4: true optional: true --- The above config will cause the service hang/failure, and the removal of the flag will resolve the issue. I primarily opened this bug report with the idea that we might update aforementioned documentation to include a caveat that you want to avoid adding this flag to the only configured interface. However, it was also discussed that we might consider having the netplan config parser complain about such a setup and consider it invalid, which it kinda is. I believe in a situation where you may have a server that should have NO network connectivity, you would simply leave netplan unconfigured and/or stop any relevant services, rather than try to configure all interfaces as optional. My original test was on Jammy, though I tested this also on Focal and Bionic, and neither of those appear to be affected by this - setting the only interface as optional in either of those does not cause the "systemd-networkd-wait-online" service to hang and the system boots normally. Let me know if you'd like/need any more info from me! Thank you! [1] https://netplan.io/faq#prevent-waiting-for-interface To manage notifications about this bug go to: https://bugs.launchpad.net/netplan/+bug/2039083/+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 2041518] Re: /usr/share/apport/apport-gtk:5:_g_log_abort:g_log_writer_default:g_log_structured_array:g_log_structured_array:g_log_structured_standard
Desktop is aware but it's not likely we will have the resources to work on that issue this cycle -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to apport in Ubuntu. https://bugs.launchpad.net/bugs/2041518 Title: /usr/share/apport/apport- gtk:5:_g_log_abort:g_log_writer_default:g_log_structured_array:g_log_structured_array:g_log_structured_standard Status in apport package in Ubuntu: New Status in gtk+3.0 package in Ubuntu: New Bug description: The Ubuntu Error Tracker has been receiving reports about a problem regarding apport. This problem was most recently seen with package version 2.27.0-0ubuntu5, the problem page at https://errors.ubuntu.com/problem/196d97dec8fe94e52eebaf9e7da150d1629a1e05 contains more details, including versions of packages affected, stacktrace or traceback, and individual crash reports. If you do not have access to the Ubuntu Error Tracker and are a software developer, you can request it at http://forms.canonical.com/reports/. g_log_structured_standard (log_domain=log_domain@entry=0x7f7fa9a12014 "Gtk", log_level=log_level@entry=G_LOG_LEVEL_ERROR, file=file@entry=0x7f7fa9a4e7c0 "../../../gtk/gtkstylecontext.c", line=line@entry=0x7f7fa9a1a381 "348", func=func@entry=0x7f7fa9a849a0 <__func__.70> "gtk_style_context_init", message_format=message_format@entry=0x7f7fa9a4edf0 "Can't create a GtkStyleContext without a display connection") This crash is probably a different variant of bug #1842439 but I cannot reproduce this crash (by running "killall -11 gnome-shell" on a mantic system). This bug is the top 1 apport bug in Ubuntu 23.10 (mantic). To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apport/+bug/2041518/+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 2040405] Re: Merge openldap from Debian unstable for noble
Nothing to merge yet.
** Changed in: openldap (Ubuntu)
Milestone: ubuntu-23.12 => ubuntu-24.01
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to openldap in Ubuntu.
https://bugs.launchpad.net/bugs/2040405
Title:
Merge openldap from Debian unstable for noble
Status in openldap package in Ubuntu:
New
Bug description:
Upstream: tbd
Debian: 2.5.13+dfsg-52.6.6+dfsg-1~exp2
Ubuntu: 2.6.6+dfsg-1~exp1ubuntu1
Debian new has 2.6.6+dfsg-1~exp2, which may be available for merge
soon.
If it turns out this needs a sync rather than a merge, please change
the tag 'needs-merge' to 'needs-sync', and (optionally) update the
title as desired.
### New Debian Changes ###
openldap (2.5.13+dfsg-5) unstable; urgency=medium
* Fix sha2-contrib autopkgtest failure. Call slappasswd using its full path.
(Closes: #1030814)
* Disable flaky test test069-delta-multiprovider-starttls.
-- Ryan Tandy Tue, 07 Feb 2023 17:56:12 -0800
openldap (2.5.13+dfsg-4) unstable; urgency=medium
[ Andreas Hasenack ]
* d/rules: Fix passwd/sha2 build (Closes: #1030716, LP: #2000817)
* d/t/sha2-contrib: add test for sha2 module
-- Ryan Tandy Mon, 06 Feb 2023 19:21:05 -0800
openldap (2.5.13+dfsg-3) unstable; urgency=medium
[ Ryan Tandy ]
* Disable flaky test test063-delta-multiprovider. Mitigates #1010608.
[ Gioele Barabucci ]
* slapd.scripts-common: Avoid double-UTF8-encoding org name (Closes:
#1016185)
* d/slapd.scripts-common: Remove outdated `migrate_to_slapd_d_style`
* d/slapd.postinst: Remove test for ancient version
* slapd.scripts-common: Remove unused `normalize_ldif`
* d/slapd.scripts-common: Use sed instead of perl in `release_diagnostics`
-- Ryan Tandy Fri, 13 Jan 2023 16:29:59 -0800
openldap (2.5.13+dfsg-2) unstable; urgency=medium
* d/tests/smbk5pwd: Grant slapd access to /var/lib/heimdal-kdc. Fixes the
autopkgtest failure due to heimdal setting mode 700 on this directory.
(Closes: #1020442)
* d/source/lintian-overrides: Add wildcards to make overrides compatible
with both older and newer versions of lintian.
* d/slapd-contrib.lintian-overrides: Remove unused
custom-library-search-path override now that krb5-config no longer sets
-rpath.
-- Ryan Tandy Sat, 24 Sep 2022 12:40:21 -0700
openldap (2.5.13+dfsg-1) unstable; urgency=medium
* d/rules: Remove get-orig-source, now unnecessary.
* Check PGP signature when running uscan.
* d/watch: Modernize watch file; use repacksuffix.
* d/copyright: Update according to DEP-5.
* d/control: Add myself to Uploaders.
* New upstream release.
-- Sergio Durigan Junior Sun, 18 Sep 2022
18:29:46 -0400
openldap (2.5.12+dfsg-2) unstable; urgency=medium
* Stop slapd explicitly in prerm as a workaround for #1006147, which caused
dpkg-reconfigure to not restart the service, so the new configuration was
not applied. See also #994204. (Closes: #1010971)
-- Ryan Tandy Mon, 23 May 2022 10:14:53 -0700
openldap (2.5.12+dfsg-1) unstable; urgency=medium
* New upstream release.
- Fixed SQL injection in back-sql (ITS#9815) (CVE-2022-29155)
* Update debconf translations:
- German, thanks to Helge Kreutzmann. (Closes: #1007728)
- Spanish, thanks to Camaleón. (Closes: #1008529)
- Dutch, thanks to Frans Spiesschaert. (Closes: #1010034)
-- Ryan Tandy Wed, 04 May 2022 18:00:16 -0700
openldap (2.5.11+dfsg-1) unstable; urgency=medium
* Upload to unstable.
-- Ryan Tandy Fri, 11 Mar 2022 19:38:02 -0800
openldap (2.5.11+dfsg-1~exp1) experimental; urgency=medium
* New upstream release.
* Add openssl to Build-Depends to enable more checks in test067-tls.
* Update slapd-contrib's custom-library-search-path override to work with
current Lintian.
-- Ryan Tandy Sun, 23 Jan 2022 17:16:05 -0800
openldap (2.5.8+dfsg-1~exp1) experimental; urgency=medium
* New upstream release.
* Update slapd-contrib's custom-library-search-path override to work with
Lintian 2.108.0.
-- Ryan Tandy Wed, 13 Oct 2021 18:42:55 -0700
openldap (2.5.7+dfsg-1~exp1) experimental; urgency=medium
* New upstream release.
* Don't run autoreconf in contrib/ldapc++. We don't build it, and it is not
### Old Ubuntu Delta ###
openldap (2.6.6+dfsg-1~exp1ubuntu1) mantic; urgency=medium
* Merge with Debian unstable (LP: #2028721). Remaining changes:
- Enable AppArmor support:
+ d/apparmor-profile: add AppArmor profile
+ d/rules: use dh_apparmor
+ d/control: Build-Depends on dh-apparmor
+ d/slapd.README.Debian: add note about AppArmor
- Enable ufw support:
+ d/control: suggest ufw.
+ d/rules: install ufw profile.
+ d/slapd.ufw.profile: add ufw profile.
- d/{rules,slapd.py}: Ad
[Touch-packages] [Bug 2029464] Re: A stack overflow in GNU Tar
Excellent - thanks for letting us know. So since a CVE has already been assigned then we won't assign an additional one. I'll add the details to our CVE tracker. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to tar in Ubuntu. https://bugs.launchpad.net/bugs/2029464 Title: A stack overflow in GNU Tar Status in tar package in Ubuntu: New Bug description: A stack overflow vulnerability exists in GNU Tar up to including v1.34, as far as I can see, Ubuntu is using v1.3. The bug exists in the function xattr_decoder() in xheader.c, where alloca() is used and it may overflow the stack if a sufficiently long xattr key is used. The vulnerability can be triggered when extracting a tar/pax archive that contains such a long xattr key. Vulnerable code: https://git.savannah.gnu.org/cgit/tar.git/tree/src/xheader.c?h=release_1_34#n1723 PoC tar archive is attached in a zip archive to reduce the size. I reported the vulnerability yesterday to GNU Tar maintainers and they replied that the issue was fixed in the version that was released two weeks ago: "Sergey fixed that bug here: https://git.savannah.gnu.org/cgit/tar.git/commit/?id=a339f05cd269013fa133d2f148d73f6f7d4247e4 and the fix appears in tar 1.35, released July 18. " To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/tar/+bug/2029464/+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 1922686] Re: Can't log in every time lightdm Xubuntu 20.04.2.1
[Expired for lightdm (Ubuntu) because there has been no activity for 60 days.] ** Changed in: lightdm (Ubuntu) Status: Incomplete => Expired -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to lightdm in Ubuntu. https://bugs.launchpad.net/bugs/1922686 Title: Can't log in every time lightdm Xubuntu 20.04.2.1 Status in lightdm package in Ubuntu: Expired Bug description: I select my username on the login screen, enter my password, the password field becomes inactive and nothing happens. If I try a second time by switching to "other user" and then back to myself, filling in the password again, it sometimes logs in and other times prints a message saying login failed. Then I have to restart via the console, which also takes an unreasonable amount of time. Also, there is a mysterious "Guest" account that I didn't create, which is not in the user list, and also requires a password, which I couldn't find anywhere on the internet. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/lightdm/+bug/1922686/+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 1958019]
Is there some way I can help to get Realtek/tas working for the Lenovo Slim Pro 9i (named Yoga Slim 9i outside of the US)? On my Manjaro install, the top speakers work (although I don't think they're amplified?) and the bottom subwoofers are off. I've managed to get qemu working for sniffing following this guide: https://github.com/ryanprescott/realtek-verb-tools/wiki/How-to-sniff-verbs-from-a-Windows-sound-driver At one point, Win10 in qemu had sound working similar to Linux (only top-firing, maybe unamplified), and I saw event logs, but I don't remember the driver. I might need to do a clean install at this point. When I try to install the driver in qemu in win10 or win11, I get a bluescreen. Windows is using Realtek Semi Corp ver 6.0.9553.1. uname: Linux andrew-slim 6.6.2-1-MANJARO #1 SMP PREEMPT_DYNAMIC Mon Nov 20 13:00:47 UTC 2023 x86_64 GNU/Linux lspci shows: 00:1f.3 Multimedia audio controller: Intel Corporation Device 51cf (rev 01) Subsystem: Lenovo Device 3802 Control: I/O- Mem+ BusMaster- SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B- DisINTx- Status: Cap+ 66MHz- UDF- FastB2B- ParErr- DEVSEL=fast >TAbort- SERR- Capabilities: [60] MSI: Enable- Count=1/1 Maskable- 64bit+ Address: Data: Kernel driver in use: vfio-pci Kernel modules: snd_hda_intel, snd_sof_pci_intel_tg >From lsmod: snd_soc_tas2781_fmwlib53248 1 snd_hda_scodec_tas2781_i2c snd_soc_tas2781_comlib24576 2 snd_soc_tas2781_fmwlib,snd_hda_scodec_tas2781_i2c >From dmesg (1f.3 is the device, I think): [0.709119] pci :00:1f.0: [8086:519f] type 00 class 0x060100 [0.709450] pci :00:1f.3: [8086:51cf] type 00 class 0x040100 [0.709492] pci :00:1f.3: reg 0x10: [mem 0x620319-0x6203193fff 64bit] [0.709546] pci :00:1f.3: reg 0x20: [mem 0x620300-0x62030f 64bit] [0.709651] pci :00:1f.3: PME# supported from D3hot D3cold [0.709735] pci :00:1f.4: [8086:51a3] type 00 class 0x0c0500 [0.709756] pci :00:1f.4: reg 0x10: [mem 0x620319c000-0x620319c0ff 64bit] [0.709778] pci :00:1f.4: reg 0x20: [io 0xefa0-0xefbf] [0.710013] pci :00:1f.5: [8086:51a4] type 00 class 0x0c8000 [0.710035] pci :00:1f.5: reg 0x10: [mem 0xfe01-0xfe010fff] I have a separate grub entry to boot without sound (for qemu sniffing) using these flags: modprobe.blacklist=snd_hda_intel,snd_sof_pci_intel_tgl pci- stub.ids=8086:51cf iommu=pt intel_iommu=on I'm not sure if that's enough. Happy to help in any way! -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to alsa-driver in Ubuntu. https://bugs.launchpad.net/bugs/1958019 Title: [Lenovo Legion7 16ACHg6 82N6, Realtek ALC287, Speaker, Internal] No sound at all Status in sound-2.6 (alsa-kernel): Confirmed Status in alsa-driver package in Ubuntu: Confirmed Bug description: On my Lenovo Legion-7-16ACHg6 laptop I can't hear any sound by internal speakers, but it work by headphones connected to standard jack aux. uname -r 5.11.0-44-generic ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: alsa-base 1.0.25+dfsg-0ubuntu5 ProcVersionSignature: Ubuntu 5.11.0-44.48~20.04.2-generic 5.11.22 Uname: Linux 5.11.0-44-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu27.21 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC2: i3draven 1266 F pulseaudio /dev/snd/controlC0: i3draven 1266 F pulseaudio /dev/snd/controlC1: i3draven 1266 F pulseaudio /dev/snd/pcmC1D0p: i3draven 1266 F...m pulseaudio CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Sat Jan 15 15:10:53 2022 InstallationDate: Installed on 2021-10-11 (96 days ago) InstallationMedia: Ubuntu 20.04.3 LTS "Focal Fossa" - Release amd64 (20210819) PackageArchitecture: all SourcePackage: alsa-driver Symptom: audio Symptom_AlsaPlaybackTest: ALSA playback test through plughw:Generic failed Symptom_Card: Family 17h (Models 10h-1fh) HD Audio Controller - HD-Audio Generic Symptom_DevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC2: i3draven 1266 F pulseaudio /dev/snd/controlC0: i3draven 1266 F pulseaudio /dev/snd/controlC1: i3draven 1266 F pulseaudio /dev/snd/pcmC1D0p: i3draven 1266 F...m pulseaudio Symptom_Jack: Speaker, Internal Symptom_Type: No sound at all Title: [82N6, Realtek ALC287, Speaker, Internal] No sound at all UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 11/08/2021 dmi.bios.release: 1.49 dmi.bios.vendor: LENOVO dmi.bios.version: GKCN49WW dmi.board.asset.tag: NO Asset Tag dmi.board.name: LNVNB161216 dmi.board.vendor: LENOVO dmi.board.version: SDK0R32862 WIN dmi.chassis.asset.tag: NO Asset Tag dmi.chassis.type: 10 dmi.c
[Touch-packages] [Bug 1958019]
Andrew, the verb approach doesn't work here as smart amps are being used. The tas2781 smart amp is generally supported as of kernel 6.6... but now it's a question of if firmware for your laptop is available. Without your alsa-info, I can't tell if your laptop is supported... But you can just try the firmware for yourself from here: https://neo-zeon.de/~hiryu/tas/firmware-6.6.tar.bz2 Just copy the files into /lib/firmware/ and reboot. Hopefully you have sound. A number of Lenovo laptops with tas2781 are supported, but I don't think the list is anywhere near comprehensive so we'll see..? Good luck! I'm not sure if these firmware files are yet in the pipeline to be commonly redistributed at this time... I'll see if there's something I can do to get that process started. (In reply to Andrew from comment #787) > From lsmod: > snd_soc_tas2781_fmwlib53248 1 snd_hda_scodec_tas2781_i2c > snd_soc_tas2781_comlib24576 2 > snd_soc_tas2781_fmwlib,snd_hda_scodec_tas2781_i2c > > From dmesg (1f.3 is the device, I think): > [0.709119] pci :00:1f.0: [8086:519f] type 00 class 0x060100 > [0.709450] pci :00:1f.3: [8086:51cf] type 00 class 0x040100 > [0.709492] pci :00:1f.3: reg 0x10: [mem 0x620319-0x6203193fff > 64bit] > [0.709546] pci :00:1f.3: reg 0x20: [mem 0x620300-0x62030f > 64bit] > [0.709651] pci :00:1f.3: PME# supported from D3hot D3cold > [0.709735] pci :00:1f.4: [8086:51a3] type 00 class 0x0c0500 > [0.709756] pci :00:1f.4: reg 0x10: [mem 0x620319c000-0x620319c0ff > 64bit] > [0.709778] pci :00:1f.4: reg 0x20: [io 0xefa0-0xefbf] > [0.710013] pci :00:1f.5: [8086:51a4] type 00 class 0x0c8000 > [0.710035] pci :00:1f.5: reg 0x10: [mem 0xfe01-0xfe010fff] > > I have a separate grub entry to boot without sound (for qemu sniffing) using > these flags: modprobe.blacklist=snd_hda_intel,snd_sof_pci_intel_tgl > pci-stub.ids=8086:51cf iommu=pt intel_iommu=on > > I'm not sure if that's enough. Happy to help in any way! -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to alsa-driver in Ubuntu. https://bugs.launchpad.net/bugs/1958019 Title: [Lenovo Legion7 16ACHg6 82N6, Realtek ALC287, Speaker, Internal] No sound at all Status in sound-2.6 (alsa-kernel): Confirmed Status in alsa-driver package in Ubuntu: Confirmed Bug description: On my Lenovo Legion-7-16ACHg6 laptop I can't hear any sound by internal speakers, but it work by headphones connected to standard jack aux. uname -r 5.11.0-44-generic ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: alsa-base 1.0.25+dfsg-0ubuntu5 ProcVersionSignature: Ubuntu 5.11.0-44.48~20.04.2-generic 5.11.22 Uname: Linux 5.11.0-44-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu27.21 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC2: i3draven 1266 F pulseaudio /dev/snd/controlC0: i3draven 1266 F pulseaudio /dev/snd/controlC1: i3draven 1266 F pulseaudio /dev/snd/pcmC1D0p: i3draven 1266 F...m pulseaudio CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Sat Jan 15 15:10:53 2022 InstallationDate: Installed on 2021-10-11 (96 days ago) InstallationMedia: Ubuntu 20.04.3 LTS "Focal Fossa" - Release amd64 (20210819) PackageArchitecture: all SourcePackage: alsa-driver Symptom: audio Symptom_AlsaPlaybackTest: ALSA playback test through plughw:Generic failed Symptom_Card: Family 17h (Models 10h-1fh) HD Audio Controller - HD-Audio Generic Symptom_DevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC2: i3draven 1266 F pulseaudio /dev/snd/controlC0: i3draven 1266 F pulseaudio /dev/snd/controlC1: i3draven 1266 F pulseaudio /dev/snd/pcmC1D0p: i3draven 1266 F...m pulseaudio Symptom_Jack: Speaker, Internal Symptom_Type: No sound at all Title: [82N6, Realtek ALC287, Speaker, Internal] No sound at all UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 11/08/2021 dmi.bios.release: 1.49 dmi.bios.vendor: LENOVO dmi.bios.version: GKCN49WW dmi.board.asset.tag: NO Asset Tag dmi.board.name: LNVNB161216 dmi.board.vendor: LENOVO dmi.board.version: SDK0R32862 WIN dmi.chassis.asset.tag: NO Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: Legion 7 16ACHg6 dmi.ec.firmware.release: 1.49 dmi.modalias: dmi:bvnLENOVO:bvrGKCN49WW:bd11/08/2021:br1.49:efr1.49:svnLENOVO:pn82N6:pvrLegion716ACHg6:skuLENOVO_MT_82N6_BU_idea_FM_Legion716ACHg6:rvnLENOVO:rnLNVNB161216:rvrSDK0R32862WIN:cvnLENOVO:ct10:cvrLegion716ACHg6: dmi.product.family: Legion 7 16ACHg6 dmi.product.name: 82N6 dmi.product.sku: LENOVO_MT_82N6_BU_idea_FM_Legion 7 16ACHg6 dmi.product.version: Legion 7 16ACHg6 dmi.sys.vendor: LENOVO To manage notifications ab
[Touch-packages] [Bug 1958019]
Created attachment 305523 alsa-info.txt Thanks Cameron! Adding those files to /lib/firmware didn't work (I copied the files directly), so I'm probably out of luck for now. I've attached my alsa-info.txt in case it helps. On Thu, Nov 30, 2023 at 10:45 AM wrote: > https://bugzilla.kernel.org/show_bug.cgi?id=208555 > > --- Comment #788 from Cameron Berkenpas (c...@neo-zeon.de) --- > Andrew, the verb approach doesn't work here as smart amps are being used. > > The tas2781 smart amp is generally supported as of kernel 6.6... but now > it's a > question of if firmware for your laptop is available. > > Without your alsa-info, I can't tell if your laptop is supported... > > But you can just try the firmware for yourself from here: > https://neo-zeon.de/~hiryu/tas/firmware-6.6.tar.bz2 > > Just copy the files into /lib/firmware/ and reboot. Hopefully you have > sound. > > A number of Lenovo laptops with tas2781 are supported, but I don't think > the > list is anywhere near comprehensive so we'll see..? > > Good luck! > > I'm not sure if these firmware files are yet in the pipeline to be commonly > redistributed at this time... I'll see if there's something I can do to get > that process started. > > (In reply to Andrew from comment #787) > > > From lsmod: > > snd_soc_tas2781_fmwlib53248 1 snd_hda_scodec_tas2781_i2c > > snd_soc_tas2781_comlib24576 2 > > snd_soc_tas2781_fmwlib,snd_hda_scodec_tas2781_i2c > > > > From dmesg (1f.3 is the device, I think): > > [0.709119] pci :00:1f.0: [8086:519f] type 00 class 0x060100 > > [0.709450] pci :00:1f.3: [8086:51cf] type 00 class 0x040100 > > [0.709492] pci :00:1f.3: reg 0x10: [mem 0x620319-0x6203193fff > > 64bit] > > [0.709546] pci :00:1f.3: reg 0x20: [mem 0x620300-0x62030f > > 64bit] > > [0.709651] pci :00:1f.3: PME# supported from D3hot D3cold > > [0.709735] pci :00:1f.4: [8086:51a3] type 00 class 0x0c0500 > > [0.709756] pci :00:1f.4: reg 0x10: [mem 0x620319c000-0x620319c0ff > > 64bit] > > [0.709778] pci :00:1f.4: reg 0x20: [io 0xefa0-0xefbf] > > [0.710013] pci :00:1f.5: [8086:51a4] type 00 class 0x0c8000 > > [0.710035] pci :00:1f.5: reg 0x10: [mem 0xfe01-0xfe010fff] > > > > I have a separate grub entry to boot without sound (for qemu sniffing) > using > > these flags: modprobe.blacklist=snd_hda_intel,snd_sof_pci_intel_tgl > > pci-stub.ids=8086:51cf iommu=pt intel_iommu=on > > > > I'm not sure if that's enough. Happy to help in any way! > > -- > You may reply to this email to add a comment. > > You are receiving this mail because: > You are on the CC list for the bug. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to alsa-driver in Ubuntu. https://bugs.launchpad.net/bugs/1958019 Title: [Lenovo Legion7 16ACHg6 82N6, Realtek ALC287, Speaker, Internal] No sound at all Status in sound-2.6 (alsa-kernel): Confirmed Status in alsa-driver package in Ubuntu: Confirmed Bug description: On my Lenovo Legion-7-16ACHg6 laptop I can't hear any sound by internal speakers, but it work by headphones connected to standard jack aux. uname -r 5.11.0-44-generic ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: alsa-base 1.0.25+dfsg-0ubuntu5 ProcVersionSignature: Ubuntu 5.11.0-44.48~20.04.2-generic 5.11.22 Uname: Linux 5.11.0-44-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu27.21 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC2: i3draven 1266 F pulseaudio /dev/snd/controlC0: i3draven 1266 F pulseaudio /dev/snd/controlC1: i3draven 1266 F pulseaudio /dev/snd/pcmC1D0p: i3draven 1266 F...m pulseaudio CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Sat Jan 15 15:10:53 2022 InstallationDate: Installed on 2021-10-11 (96 days ago) InstallationMedia: Ubuntu 20.04.3 LTS "Focal Fossa" - Release amd64 (20210819) PackageArchitecture: all SourcePackage: alsa-driver Symptom: audio Symptom_AlsaPlaybackTest: ALSA playback test through plughw:Generic failed Symptom_Card: Family 17h (Models 10h-1fh) HD Audio Controller - HD-Audio Generic Symptom_DevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC2: i3draven 1266 F pulseaudio /dev/snd/controlC0: i3draven 1266 F pulseaudio /dev/snd/controlC1: i3draven 1266 F pulseaudio /dev/snd/pcmC1D0p: i3draven 1266 F...m pulseaudio Symptom_Jack: Speaker, Internal Symptom_Type: No sound at all Title: [82N6, Realtek ALC287, Speaker, Internal] No sound at all UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 11/08/2021 dmi.bios.release: 1.49 dmi.bios.vendor: LENOVO dmi.bios.version: GKCN49WW dmi.board.asset.tag: NO Asset Tag dmi.board.name: LNVNB161216 dmi.board.vendor: LENOVO dmi.board.version: SDK0R3286
[Touch-packages] [Bug 2045375] [NEW] Sound Output Device : Dummy Output
Public bug reported: Fresh install and there is no sound. The only option in Sound Output Device settings is `Dummy Output`. I attempted a fix described at https://askubuntu.com/a/1236100 which revealed different output devices, but still no sound. ProblemType: Bug DistroRelease: Ubuntu 23.10 Package: alsa-base 1.0.25+dfsg-0ubuntu7 ProcVersionSignature: Ubuntu 6.5.0-13.13-generic 6.5.3 Uname: Linux 6.5.0-13-generic x86_64 ApportVersion: 2.27.0-0ubuntu5 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: nils 1388 F wireplumber /dev/snd/seq:nils 1378 F pipewire CasperMD5CheckResult: unknown CurrentDesktop: ubuntu:GNOME Date: Thu Nov 30 21:49:16 2023 InstallationDate: Installed on 2023-11-30 (0 days ago) InstallationMedia: Ubuntu 23.10.1 "Mantic Minotaur" - Release amd64 (20231016.1) PackageArchitecture: all ProcEnviron: LANG=en_US.UTF-8 PATH=(custom, no user) SHELL=/bin/bash XDG_RUNTIME_DIR= SourcePackage: alsa-driver Symptom: audio UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 08/17/2023 dmi.bios.release: 0.1 dmi.bios.vendor: Apple Inc. dmi.bios.version: 522.0.0.0.0 dmi.board.name: Mac-4B682C642B45593E dmi.board.vendor: Apple Inc. dmi.board.version: iMac18,1 dmi.chassis.type: 9 dmi.chassis.vendor: Apple Inc. dmi.chassis.version: Mac-4B682C642B45593E dmi.modalias: dmi:bvnAppleInc.:bvr522.0.0.0.0:bd08/17/2023:br0.1:svnAppleInc.:pniMac18,1:pvr1.0:rvnAppleInc.:rnMac-4B682C642B45593E:rvriMac18,1:cvnAppleInc.:ct9:cvrMac-4B682C642B45593E:sku: dmi.product.family: iMac dmi.product.name: iMac18,1 dmi.product.version: 1.0 dmi.sys.vendor: Apple Inc. mtime.conffile..etc.modprobe.d.alsa-base.conf: 2023-11-30T21:48:48.924029 ** Affects: alsa-driver (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug mantic wayland-session -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to alsa-driver in Ubuntu. https://bugs.launchpad.net/bugs/2045375 Title: Sound Output Device : Dummy Output Status in alsa-driver package in Ubuntu: New Bug description: Fresh install and there is no sound. The only option in Sound Output Device settings is `Dummy Output`. I attempted a fix described at https://askubuntu.com/a/1236100 which revealed different output devices, but still no sound. ProblemType: Bug DistroRelease: Ubuntu 23.10 Package: alsa-base 1.0.25+dfsg-0ubuntu7 ProcVersionSignature: Ubuntu 6.5.0-13.13-generic 6.5.3 Uname: Linux 6.5.0-13-generic x86_64 ApportVersion: 2.27.0-0ubuntu5 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: nils 1388 F wireplumber /dev/snd/seq:nils 1378 F pipewire CasperMD5CheckResult: unknown CurrentDesktop: ubuntu:GNOME Date: Thu Nov 30 21:49:16 2023 InstallationDate: Installed on 2023-11-30 (0 days ago) InstallationMedia: Ubuntu 23.10.1 "Mantic Minotaur" - Release amd64 (20231016.1) PackageArchitecture: all ProcEnviron: LANG=en_US.UTF-8 PATH=(custom, no user) SHELL=/bin/bash XDG_RUNTIME_DIR= SourcePackage: alsa-driver Symptom: audio UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 08/17/2023 dmi.bios.release: 0.1 dmi.bios.vendor: Apple Inc. dmi.bios.version: 522.0.0.0.0 dmi.board.name: Mac-4B682C642B45593E dmi.board.vendor: Apple Inc. dmi.board.version: iMac18,1 dmi.chassis.type: 9 dmi.chassis.vendor: Apple Inc. dmi.chassis.version: Mac-4B682C642B45593E dmi.modalias: dmi:bvnAppleInc.:bvr522.0.0.0.0:bd08/17/2023:br0.1:svnAppleInc.:pniMac18,1:pvr1.0:rvnAppleInc.:rnMac-4B682C642B45593E:rvriMac18,1:cvnAppleInc.:ct9:cvrMac-4B682C642B45593E:sku: dmi.product.family: iMac dmi.product.name: iMac18,1 dmi.product.version: 1.0 dmi.sys.vendor: Apple Inc. mtime.conffile..etc.modprobe.d.alsa-base.conf: 2023-11-30T21:48:48.924029 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/2045375/+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 2040484] Re: ubuntu_seccomp pseudo-syscall fails on s390
This issue can be found on ppc64el (openstack VM) as well, all the way from 5.4 to 6.5 ** Tags added: 5.15 5.4 6.2 6.5 focal jammy lunar mantic ppc64el s390x sru-20231030 ubuntu-seccomp -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to libseccomp in Ubuntu. https://bugs.launchpad.net/bugs/2040484 Title: ubuntu_seccomp pseudo-syscall fails on s390 Status in ubuntu-kernel-tests: New Status in libseccomp package in Ubuntu: New Bug description: libseccomp upstream has changed the test code for 29-sim- pseudo_syscall.c, which has broken it for s390. Perhaps s390 has been broken since forever and the test change is just uncovering it. We need to investigate if the fix would be needed in the test, libseccomp or the kernel. This seems to affect at least 4.4 and 5.4 kernels, but may affect everything. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-kernel-tests/+bug/2040484/+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 2040484] Re: ubuntu_seccomp pseudo-syscall fails on s390 / PowerPC
** Summary changed: - ubuntu_seccomp pseudo-syscall fails on s390 + ubuntu_seccomp pseudo-syscall fails on s390 / PowerPC -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to libseccomp in Ubuntu. https://bugs.launchpad.net/bugs/2040484 Title: ubuntu_seccomp pseudo-syscall fails on s390 / PowerPC Status in ubuntu-kernel-tests: New Status in libseccomp package in Ubuntu: New Bug description: libseccomp upstream has changed the test code for 29-sim- pseudo_syscall.c, which has broken it for s390. Perhaps s390 has been broken since forever and the test change is just uncovering it. We need to investigate if the fix would be needed in the test, libseccomp or the kernel. This seems to affect at least 4.4 and 5.4 kernels, but may affect everything. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-kernel-tests/+bug/2040484/+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 2043234] Re: Symlink for resolv.conf is wrong on fresh install
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: systemd (Ubuntu) Status: New => Confirmed -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to systemd in Ubuntu. https://bugs.launchpad.net/bugs/2043234 Title: Symlink for resolv.conf is wrong on fresh install Status in systemd package in Ubuntu: Confirmed Bug description: Hello. Sorry for disturb, may I ask you please to confirm if im not doing anything wrong with new installation? Its being a while since the problem exists AT LEAST IN MY CASE with "faulty path" for symlinc at resolv.conf I believe its keep happening since 18.04 version and even now in 22.04 So, in the fresh install the path looks like this: lrwxrwxrwx 1 root root 39 Feb 17 2023 resolv.conf -> ../run/systemd/resolve/stub-resolv.conf but once im running : sudo ln -sf /run/systemd/resolve/resolv.conf /etc/resolv.conf everything works fine. By everything I mean when I run nslookup. Regards, Vitalii Sharapov To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/2043234/+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 2043234] Re: Symlink for resolv.conf is wrong on fresh install
Thank you Vitalii, Your fix helped me a lot, My Ubuntu was in 22.04 when this problem appeared : DNS domain search paths not updated when VPN started Before your fix : ➜ ~ sudo ls -la /etc/resolv.conf lrwxrwxrwx 1 root root 39 juin 23 12:37 /etc/resolv.conf -> ../run/systemd/resolve/stub-resolv.conf So this symbolic link has been changed on june 23, 2023. -- 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/2043234 Title: Symlink for resolv.conf is wrong on fresh install Status in systemd package in Ubuntu: Confirmed Bug description: Hello. Sorry for disturb, may I ask you please to confirm if im not doing anything wrong with new installation? Its being a while since the problem exists AT LEAST IN MY CASE with "faulty path" for symlinc at resolv.conf I believe its keep happening since 18.04 version and even now in 22.04 So, in the fresh install the path looks like this: lrwxrwxrwx 1 root root 39 Feb 17 2023 resolv.conf -> ../run/systemd/resolve/stub-resolv.conf but once im running : sudo ln -sf /run/systemd/resolve/resolv.conf /etc/resolv.conf everything works fine. By everything I mean when I run nslookup. Regards, Vitalii Sharapov To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/2043234/+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
