[Touch-packages] [Bug 1853956] Re: 34 wireguard peers result in invalid peer configuration
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/1853956 Title: 34 wireguard peers result in invalid peer configuration Status in systemd package in Ubuntu: Confirmed Bug description: ubuntu server 18.04.3 LTS systemd 237-3ubuntu10.31 wireguard 0.0.20191012-wg1~bionic from PPA. We're using systemd-networkd to configure wireguard via wireguard.netdev and wireguard.network files in /etc/systemd/network/. All endpoints have IPv4 addresses. When we include 34, 35, or 36 [WireGuardPeer] entries in the netdev file some peers are configured incorrectly. The affected peers seem to be related to the total number of peers (counting from 0 here): 33 peers: No issue 34 peers: Peer 1 and 2 fail 35 peers: Peer 2 and 3 fail 36 peers: Peer 3 and 4 fail 37 peers: No issue In all cases peer 0 is functional. For an affected pair of peers A and B, peer A ends up with the allowed IP address range of peer B. Peer B ends up with no allowed IP addresses. This can be seen in the output of wg. The connections to both peers fail because of incorrect address range assignments. We first encountered this issue in a production environment when we moved from 33 to 34 unique peers on each server. The issue was reproduced on 3 different physical servers with similar configuration by adding and removing peer 34. The [WireGuardPeer] entries do not need to be unique to reproduce the issue. In my testing I used 6 distinct peers and then used 28 or more identical copies of a 7th peer. The results were the same. In January 2019 a bug was reported that was also related to the number of wireguard peers, but the description seems sufficiently different from our case that I felt I should file a distinct bug report. Here's a link to that report in case I'm wrong about that: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1811149 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1853956/+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 1844853] Autopkgtest regression report (glib2.0/2.62.3-2~ubuntu19.10.1)
All autopkgtests for the newly accepted glib2.0 (2.62.3-2~ubuntu19.10.1) for
eoan have finished running.
The following regressions have been reported in tests triggered by the package:
automake-1.16/1:1.16.1-4ubuntu3 (s390x)
libreoffice/1:6.3.4-0ubuntu0.19.10.1 (ppc64el)
umockdev/0.13.2-1 (armhf, i386)
asterisk/1:16.2.1~dfsg-2build2 (arm64)
tracker/2.3.0-1 (armhf)
glib2.0/2.62.3-2~ubuntu19.10.1 (i386)
cmake-extras/1.3+17.04.20170310-5 (armhf)
netplan.io/0.98-0ubuntu1 (ppc64el, i386)
dbus-test-runner/15.04.0+19.04.20190115-0ubuntu1 (armhf, i386)
sbd/1.4.0-18-g5e3283c-1ubuntu1 (amd64, i386)
ocaml-cairo2/unknown (armhf)
netplan.io/unknown (armhf)
gvfs/1.42.1-1ubuntu1 (arm64)
openssh/1:8.0p1-6build1 (amd64, armhf, arm64, s390x, i386, ppc64el)
snapd-glib/1.49-0ubuntu1.19.10.0 (armhf)
Please visit the excuses page listed below and investigate the failures,
proceeding afterwards as per the StableReleaseUpdates policy regarding
autopkgtest regressions [1].
https://people.canonical.com/~ubuntu-archive/proposed-
migration/eoan/update_excuses.html#glib2.0
[1] https://wiki.ubuntu.com/StableReleaseUpdates#Autopkgtest_Regressions
Thank you!
--
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/1844853
Title:
IBus no longer works in Qt applications after upgrade
Status in GLib:
Fix Released
Status in ibus:
Fix Released
Status in glib2.0 package in Ubuntu:
Fix Released
Status in ibus package in Ubuntu:
Fix Released
Status in glib2.0 source package in Xenial:
Fix Committed
Status in glib2.0 source package in Bionic:
Fix Committed
Status in glib2.0 source package in Disco:
Fix Committed
Status in glib2.0 source package in Eoan:
Fix Committed
Status in glib2.0 source package in Focal:
Fix Released
Status in ibus source package in Focal:
Fix Released
Status in glib2.0 package in Debian:
Fix Released
Bug description:
[Impact]
IBus was broken for Qt applications as a regression due to the fix of
CVE-2019-14822. As a result the IBus patch was disabled temporarily,
which fixed IBus from a usability POV.
The real fix has been made in glib2.0, and the updates in -proposed
will allow the IBus patch to be re-enabled.
[Test Case]
* On a standard Ubuntu {eoan,disco,bionic,xenial} installation
- Upgrade the glib2.0 packages from
{eoan,disco,bionic,xenial}-proposed
- Upgrade the ibus packages from
https://launchpad.net/~ubuntu-security-proposed/+archive/ubuntu/ppa
- Install some IBus input method, e.g. ibus-libpinyin
- Install some Qt application, e.g. Kate
* Relogin (maybe reboot)
* Add the input method to the input sources
* Open the Qt app and try to input something using the IBus IM
=> Find that the transliteration works as expected
[Regression Potential]
The applicable patches origin from glib upstream:
https://gitlab.gnome.org/GNOME/glib/merge_requests/1176
Consequently the changes have been reviewed by the glib maintainer, but also
tested by the IBus maintainer, by me (gunnarhj), and - of course - the author
Simon McVittie. The changes have been in Debian unstable since 2019-10-30.
[Original description]
Kubuntu Release 18.04.3 LTS
Expected behavior:
ibus continues working as before after applying security update
1.5.17-ubuntu5.1 from version 1.5.17-ubuntu5.
Observed behavior:
ibus is not usable anymore in Qt applications.
After updating ibus and the related packages ibus-gtk, ibus-gtk3,
libibus-1.0-5 and gir1.2-ibus-1.0 all from version 1.5.17-ubuntu5 to
1.5.17-ubuntu5.1, I can no longer use ibus in Qt applications. Using
shift-space no longer changes the selected input method and even when i switch
to the mozc input method in a gtk application, i can not use it in any Qt
applications.
When starting qtconfig in a terminal, I also get the following message:
Bus::open: Connect ibus failed!
IBusInputContext::createInputContext: no connection to ibus-daemon
This bug was not present in version 1.5.17-3ubuntu5 and I also
confirmed that downgrading the packages to version 1.5.17-3ubuntu4
restores ibus functionality in Qt applications.
ProblemType: Bug
DistroRelease: Ubuntu 18.04
Package: ibus 1.5.17-3ubuntu5.1
ProcVersionSignature: Ubuntu 5.0.0-30.32~18.04.1-generic 5.0.21
Uname: Linux 5.0.0-30-generic x86_64
NonfreeKernelModules: nvidia_modeset nvidia
ApportVersion: 2.20.9-0ubuntu7.7
Architecture: amd64
CurrentDesktop: KDE
Date: Sat Sep 21 07:58:56 2019
InstallationDate: Installed on 2019-06-28 (84 days ago)
InstallationMedia: Kubuntu 18.04.2 LTS "Bionic Beaver" - Release amd64
(20190210)
SourcePackage: ibus
UpgradeStatus: No upgrade log present (probably fresh install)
To manage notifications about this bug go to:
https://bugs.launchpad.net/glib/+bug/1844853/+subscriptions
--
Mailing list: https://launchpad.net/~touch-packages
Post to
[Touch-packages] [Bug 1850932] Autopkgtest regression report (glib2.0/2.62.3-2~ubuntu19.10.1)
All autopkgtests for the newly accepted glib2.0 (2.62.3-2~ubuntu19.10.1) for eoan have finished running. The following regressions have been reported in tests triggered by the package: automake-1.16/1:1.16.1-4ubuntu3 (s390x) libreoffice/1:6.3.4-0ubuntu0.19.10.1 (ppc64el) umockdev/0.13.2-1 (armhf, i386) asterisk/1:16.2.1~dfsg-2build2 (arm64) tracker/2.3.0-1 (armhf) glib2.0/2.62.3-2~ubuntu19.10.1 (i386) cmake-extras/1.3+17.04.20170310-5 (armhf) netplan.io/0.98-0ubuntu1 (ppc64el, i386) dbus-test-runner/15.04.0+19.04.20190115-0ubuntu1 (armhf, i386) sbd/1.4.0-18-g5e3283c-1ubuntu1 (amd64, i386) ocaml-cairo2/unknown (armhf) netplan.io/unknown (armhf) gvfs/1.42.1-1ubuntu1 (arm64) openssh/1:8.0p1-6build1 (amd64, armhf, arm64, s390x, i386, ppc64el) snapd-glib/1.49-0ubuntu1.19.10.0 (armhf) Please visit the excuses page listed below and investigate the failures, proceeding afterwards as per the StableReleaseUpdates policy regarding autopkgtest regressions [1]. https://people.canonical.com/~ubuntu-archive/proposed- migration/eoan/update_excuses.html#glib2.0 [1] https://wiki.ubuntu.com/StableReleaseUpdates#Autopkgtest_Regressions Thank you! -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to glib2.0 in Ubuntu. https://bugs.launchpad.net/bugs/1850932 Title: [SRU] Backport 2.62.3-2 Status in glib2.0 package in Ubuntu: Fix Released Status in glib2.0 source package in Eoan: Fix Committed Bug description: [ Description ] I'm creating this bug report to have a place to describe the proposed backport of glib2.0 2.62.3-2 from focal. One purpose of this backport is to fix bug #1844853. But there are several other changes. Here's the diff of NEWS: +Overview of changes in GLib 2.62.3 +== + +* Use `poll()` in `g_spawn_sync()` rather than `select()`, which is subject to + FD limits (#954) + +* Fix undefined behaviour with `g_utf8_find_prev_char()` (#1917) + +* Bugs fixed: + - #954 The g_spawn_sync() function uses select() which has limitations + - #1318 rare failure in gdbus-peer test: invalid uninstantiatable type '(null)' in cast to 'GDBusServer' + - #1897 glib 2.62.0 fails test 'test_writev_no_vectors' wih gcc7 + - #1903 use-after-free in mimeapps test causes intermittent segfault during testing + - #1916 objcopy not used from cross-compilation file in GIO tests + - #1917 Test utf8-pointer fails with static build, LTO, optimisations, and new GCC + - !1174 Backport !1164 “use-after-free fix in mimeapps test” to glib-2-62 + - !1184 Backport !1173 “gvariant: Limit recursion in g_variant_parse()” to glib-2-62 + - !1194 Backport !1176, !1183, !1188, !1191 to `glib-2-62` + - !1203 Backport !1192, !1193, !1197 Fixes for gdbus-peer tests to glib-2-62 + - !1207 Backport !1206 “goption: Relax assertion to avoid being broken by kdeinit5” to glib-2-62 + - !1215 [2.62] gdbus-peer: Specifically listen on 127.0.0.1 + - !1219 Backport !1218 “gdb: Fix GHashTable pretty printer off-by-one error” + - !1222 Backport !1221 “Add NOTE_REVOKE to the list of the monitoring events” to glib-2-62 + - !1228 Backport !1199 “gunicode: Fix UB in gutf8.c and utf8-pointer test” to glib-2-62 + + +Overview of changes in GLib 2.62.2 +== + +* Bugs fixed: + - #1896 Use after free when calling g_dbus_connection_flush_sync() in a dedicated thread + - !1154 Backport !1152 “gwinhttpvfs: Handle g_get_prgname() returning NULL” to glib-2-62 + - !1156 Backport !1146 Solaris fixes to glib-2-62 This release can be considered to be tested under https://wiki.ubuntu.com/StableReleaseUpdates/GNOME There are patches from the upstream master branch rather than this stable release: + Add-a-test-for-GDBusServer-authentication.patch + gdbus-server-auth-test-Create-temporary-directory-for-Uni.patch + gdbus-server-auth-test-Include-gcredentialsprivate.h.patch + Make-ld-executable-configurable.patch They are sensible backports which I hope are appropriate for SRU. [ QA ] The testsuite fixes will verify themselves during the build and autopkgtest. For the rest of the fixes, please exercise the desktop thoroughly. Log in, log out, run many applications and make sure there are no regressions. [ Regression potential ] test fixes> Build failures or autopkgtest failures. GLib is a central desktop library. Regressions could break any part of the desktop - so QA is important, the SRU exception notwithstanding. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/glib2.0/+bug/1850932/+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 1848202] Autopkgtest regression report (glib2.0/2.62.3-2~ubuntu19.10.1)
All autopkgtests for the newly accepted glib2.0 (2.62.3-2~ubuntu19.10.1) for eoan have finished running. The following regressions have been reported in tests triggered by the package: automake-1.16/1:1.16.1-4ubuntu3 (s390x) libreoffice/1:6.3.4-0ubuntu0.19.10.1 (ppc64el) umockdev/0.13.2-1 (armhf, i386) asterisk/1:16.2.1~dfsg-2build2 (arm64) tracker/2.3.0-1 (armhf) glib2.0/2.62.3-2~ubuntu19.10.1 (i386) cmake-extras/1.3+17.04.20170310-5 (armhf) netplan.io/0.98-0ubuntu1 (ppc64el, i386) dbus-test-runner/15.04.0+19.04.20190115-0ubuntu1 (armhf, i386) sbd/1.4.0-18-g5e3283c-1ubuntu1 (amd64, i386) ocaml-cairo2/unknown (armhf) netplan.io/unknown (armhf) gvfs/1.42.1-1ubuntu1 (arm64) openssh/1:8.0p1-6build1 (amd64, armhf, arm64, s390x, i386, ppc64el) snapd-glib/1.49-0ubuntu1.19.10.0 (armhf) Please visit the excuses page listed below and investigate the failures, proceeding afterwards as per the StableReleaseUpdates policy regarding autopkgtest regressions [1]. https://people.canonical.com/~ubuntu-archive/proposed- migration/eoan/update_excuses.html#glib2.0 [1] https://wiki.ubuntu.com/StableReleaseUpdates#Autopkgtest_Regressions Thank you! -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to glib2.0 in Ubuntu. https://bugs.launchpad.net/bugs/1848202 Title: Use after free in gdbus leads to eds segfaults Status in GLib: Fix Released Status in glib2.0 package in Ubuntu: Fix Released Status in glib2.0 source package in Eoan: Fix Committed Bug description: [ Description ] The Ubuntu Error Tracker has been receiving reports about a problem regarding evolution-data-server. This problem was most recently seen with package version 3.34.1-1, the problem page at https://errors.ubuntu.com/problem/b1f62616406e36e521fd1fb1d2be4ac2fe9a2cda 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/. [ Fix ] This bug was fixed upstream in 2.62.2 (see the links below). That update is being issues to eoan. [ QA ] Under https://wiki.ubuntu.com/StableReleaseUpdates/GNOME, we don't need to explicitly test that this bug is fixed. Nevertheless, to verify this bug please give the desktop a good workout. Ideally install the SRU and use your machine as you would normally for a variety of tasks. Make sure there are no regressions. [ Regression potential ] 1) The changes involve mutexes and stuff, which is error prone. 2) It's GLib, a core library, so any bad regressions will be really serious for the desktop as a whole. To manage notifications about this bug go to: https://bugs.launchpad.net/glib/+bug/1848202/+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 702433] Re: Graphical SSH passphrase prompt does not come up in front/foreground of guake terminal (focus)
[Expired for guake (Ubuntu) because there has been no activity for 60 days.] ** Changed in: guake (Ubuntu) Status: Incomplete => Expired -- 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/702433 Title: Graphical SSH passphrase prompt does not come up in front/foreground of guake terminal (focus) Status in guake package in Ubuntu: Expired Status in openssh package in Ubuntu: Won't Fix Bug description: Graphical SSH passphrase prompt does not come up in front/foreground of guake terminal (focus). Steps to reproduce: 1) Open a Guake Terminal 2) SSH into a machine which requires pubkey auth What happens: Graphical SSH Passphrase window shows up behind the terminal and blocks interface. One must click on it to see it. Expected: -Passphrase should be asked from the command line (how would I change this?) -GUI passphrase window should be on top of all other windows ProblemType: Bug DistroRelease: Ubuntu 10.04 Package: openssh-client 1:5.3p1-3ubuntu4 ProcVersionSignature: Ubuntu 2.6.32-27.49-generic 2.6.32.26+drm33.12 Uname: Linux 2.6.32-27-generic i686 Architecture: i386 Date: Thu Jan 13 11:07:26 2011 InstallationMedia: Ubuntu 10.04 "Lucid Lynx" - Release Candidate i386 (20100419.1) ProcEnviron: LANGUAGE=en_US:en_CA:en LANG=en_US.utf8 SHELL=/bin/bash SourcePackage: openssh To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/guake/+bug/702433/+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 1847967] Re: oem kernel packages treated differently from generic kernel ones
** Changed in: oem-priority Assignee: (unassigned) => Yuan-Chen Cheng (ycheng-twn) -- 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/1847967 Title: oem kernel packages treated differently from generic kernel ones Status in OEM Priority Project: New Status in apport package in Ubuntu: Fix Released Status in apport source package in Bionic: In Progress Status in apport source package in Disco: In Progress Status in apport source package in Eoan: In Progress Status in apport source package in Focal: Fix Released Bug description: [SRU Justification] [Impact] When `apport-bug linux` was executed on systems with linux-oem, linux-oem-osp1 kernels, many details are not included as generic linux kernel does. Alsa info, dmesg, lspci, lsusb, DMI, etc. are missing. [Fix] Fix already merged in Focal: https://bazaar.launchpad.net/~ubuntu-core-dev/ubuntu/focal/apport/ubuntu/revision/2724 . SRU merge proposals in: * https://code.launchpad.net/~vicamo/ubuntu/bionic/apport/bug-1847967/+merge/376380 * https://code.launchpad.net/~vicamo/ubuntu/disco/apport/bug-1847967/+merge/376381 * https://code.launchpad.net/~vicamo/ubuntu/eoan/apport/bug-1847967/+merge/374263 [Test Case] 1. Boot with linux-oem or linux-oem-osp1 kernel and try to collect apport logs with: $ apport-cli --save saved.apport linux-oem-osp1 2. Make sure the report contains PCI/ALSA/DMI/Sysfs info. [Regression Potential] Low. original bug description When `apport-bug linux` was executed on systems with linux-oem, linux- oem-osp1 kernels, many details are not included as generic linux kernel does. Alsa info, dmesg, lspci, lsusb, DMI, etc. are missing. To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/1847967/+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 1859996] Re: pulseaudio-equalizer make pulseaudio's start fail
Thank you for taking the time to report this bug and helping to make Ubuntu better. Please execute the following command only once, as it will automatically gather debugging information, in a terminal: apport-collect 1859996 When reporting bugs in the future please use apport by using 'ubuntu- bug' and the name of the package affected. You can learn more about this functionality at https://wiki.ubuntu.com/ReportingBugs. ** Changed in: pulseaudio (Ubuntu) Status: New => Incomplete -- 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/1859996 Title: pulseaudio-equalizer make pulseaudio's start fail Status in pulseaudio package in Ubuntu: Incomplete Bug description: After installing pulseaudio-equalizer package, Pulseaudio doesn't work anymore. Due to that, no device can be configured glad to KDE's sound widget: https://askubuntu.com/questions/976375/kubuntu-17-10-no-audio- devices-found-no-settings-no-sound sudo cat /var/log/syslog | grep pulseaudio [pulseaudio] module-equalizer-sink.c: module-equalizer-sink is currently unsupported, and can sometimes cause PulseAudio crashes, increased latency or audible artifacts. [pulseaudio] module-equalizer-sink.c: If you're facing audio problems, try unloading this module as a potential workaround. [pulseaudio] module-equalizer-sink.c: Master sink not found [pulseaudio] module.c: Failed to load module "module-equalizer-sink" (argument: ""): initialization failed. Also, "apt purge pulseaudio-equalizer" doesn't remove "load-module module-equalizer-sink" from the .config/pulse/default.pa so it continues to fail at start afterwards. sudo cat /var/log/syslog | grep pulseaudio [pulseaudio] ltdl-bind-now.c: Failed to open module module-equalizer-sink.so : module-equalizer-sink.so: cannot open shared object file: No such file or directory [pulseaudio] module.c: Failed to open module "module-equalizer-sink". NB: I cannot choose pulseaudio-equalizer as targeted package for this bug as it's not listed despite this: sudo apt search pulseaudio-equalizer pulseaudio-equalizer/eoan-updates 1:13.0-1ubuntu1.1 amd64 Equalizer sink module for PulseAudio sound server To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1859996/+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 1859730] Re: [comet lake] Gnome freezes, icons missing, graphics corruption
Finally, the problem might be triggered by the atomic modesetting code used by Xorg sessions. Please try logging into 'Ubuntu on Wayland' and tell us if that avoids some of the problem. ** Also affects: linux (Ubuntu) Importance: Undecided Status: New ** Changed in: linux (Ubuntu) Status: New => Incomplete -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to mesa in Ubuntu. https://bugs.launchpad.net/bugs/1859730 Title: [comet lake] Gnome freezes, icons missing, graphics corruption Status in linux package in Ubuntu: Incomplete Status in mesa package in Ubuntu: Incomplete Bug description: ack please.. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: xorg 1:7.7+19ubuntu7.1 Uname: Linux 5.4.11-050411-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.9 Architecture: amd64 CompositorRunning: None Date: Tue Jan 14 20:17:26 2020 DistUpgraded: Fresh install DistributionChannelDescriptor: # This is the distribution channel descriptor for the OEM CDs # For more information see http://wiki.ubuntu.com/DistributionChannelDescriptor canonical-oem-somerville-bionic-amd64-20180608-47+beaver-three-eyed-raven+X92 DistroCodename: bionic DistroVariant: ubuntu DkmsStatus: backport-iwlwifi, 8286, 4.15.0-1042-oem, x86_64: installed backport-iwlwifi, 8286, 4.15.0-1066-oem, x86_64: installed ExtraDebuggingInterest: Yes GpuHangFrequency: Very infrequently GraphicsCard: Intel Corporation Device [8086:9bca] (rev 04) (prog-if 00 [VGA controller]) Subsystem: Dell Device [1028:0962] InstallationDate: Installed on 2020-01-13 (1 days ago) InstallationMedia: Ubuntu 18.04 "Bionic" - Build amd64 LIVE Binary 20180608-09:38 Lsusb: Bus 004 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 003 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 002: ID 8087:0029 Intel Corp. Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: Dell Inc. XPS 13 7390 ProcEnviron: TERM=xterm-256color PATH=(custom, no user) LANG=es_CL.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.11-050411-generic root=UUID=8fd25548-00af-4395-92f0-5d7d27a54deb ro quiet splash vt.handoff=1 SourcePackage: xorg Symptom: display Title: Xorg freeze UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 11/25/2019 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.4.0 dmi.board.name: 0377MH dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 10 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr1.4.0:bd11/25/2019:svnDellInc.:pnXPS137390:pvr:rvnDellInc.:rn0377MH:rvrA00:cvnDellInc.:ct10:cvr: dmi.product.family: XPS dmi.product.name: XPS 13 7390 dmi.product.sku: 0962 dmi.sys.vendor: Dell Inc. version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.97-1ubuntu1~18.04.1 version.libgl1-mesa-dri: libgl1-mesa-dri 19.0.8-0ubuntu0~18.04.3 version.libgl1-mesa-glx: libgl1-mesa-glx 19.0.8-0ubuntu0~18.04.3 version.xserver-xorg-core: xserver-xorg-core 2:1.19.6-1ubuntu4.3 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:18.0.1-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20171229-1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.15-2 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1859730/+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 1859730] Re: [comet lake] Gnome freezes, icons missing, graphics corruption
This also appears once in your kernel log: [ 24.955117] [drm:intel_cpu_fifo_underrun_irq_handler [i915]] *ERROR* CPU pipe A FIFO underrun which might be associated with the flashing and out-of-sync screen you describe. See bug 1550779. -- 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/1859730 Title: [comet lake] Gnome freezes, icons missing, graphics corruption Status in linux package in Ubuntu: Incomplete Status in mesa package in Ubuntu: Incomplete Bug description: ack please.. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: xorg 1:7.7+19ubuntu7.1 Uname: Linux 5.4.11-050411-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.9 Architecture: amd64 CompositorRunning: None Date: Tue Jan 14 20:17:26 2020 DistUpgraded: Fresh install DistributionChannelDescriptor: # This is the distribution channel descriptor for the OEM CDs # For more information see http://wiki.ubuntu.com/DistributionChannelDescriptor canonical-oem-somerville-bionic-amd64-20180608-47+beaver-three-eyed-raven+X92 DistroCodename: bionic DistroVariant: ubuntu DkmsStatus: backport-iwlwifi, 8286, 4.15.0-1042-oem, x86_64: installed backport-iwlwifi, 8286, 4.15.0-1066-oem, x86_64: installed ExtraDebuggingInterest: Yes GpuHangFrequency: Very infrequently GraphicsCard: Intel Corporation Device [8086:9bca] (rev 04) (prog-if 00 [VGA controller]) Subsystem: Dell Device [1028:0962] InstallationDate: Installed on 2020-01-13 (1 days ago) InstallationMedia: Ubuntu 18.04 "Bionic" - Build amd64 LIVE Binary 20180608-09:38 Lsusb: Bus 004 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 003 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 002: ID 8087:0029 Intel Corp. Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: Dell Inc. XPS 13 7390 ProcEnviron: TERM=xterm-256color PATH=(custom, no user) LANG=es_CL.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.11-050411-generic root=UUID=8fd25548-00af-4395-92f0-5d7d27a54deb ro quiet splash vt.handoff=1 SourcePackage: xorg Symptom: display Title: Xorg freeze UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 11/25/2019 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.4.0 dmi.board.name: 0377MH dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 10 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr1.4.0:bd11/25/2019:svnDellInc.:pnXPS137390:pvr:rvnDellInc.:rn0377MH:rvrA00:cvnDellInc.:ct10:cvr: dmi.product.family: XPS dmi.product.name: XPS 13 7390 dmi.product.sku: 0962 dmi.sys.vendor: Dell Inc. version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.97-1ubuntu1~18.04.1 version.libgl1-mesa-dri: libgl1-mesa-dri 19.0.8-0ubuntu0~18.04.3 version.libgl1-mesa-glx: libgl1-mesa-glx 19.0.8-0ubuntu0~18.04.3 version.xserver-xorg-core: xserver-xorg-core 2:1.19.6-1ubuntu4.3 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:18.0.1-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20171229-1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.15-2 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1859730/+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 1859730] Re: [comet lake] Gnome freezes, icons missing, graphics corruption
Thanks. I should have noticed earlier that you're using very new hardware with a slightly old Ubuntu release. Although it is the latest LTS release. I am guessing you probably need a newer version of Mesa for this GPU. To test that theory please try booting Ubuntu 20.04 from USB (http://cdimage.ubuntu.com/daily-live/current/) and tell us if it has the same issues. ** Summary changed: - Xorg freeze + [comet lake] Gnome freezes, icons missing, graphics corruption ** Package changed: ubuntu => mesa (Ubuntu) -- 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/1859730 Title: [comet lake] Gnome freezes, icons missing, graphics corruption Status in linux package in Ubuntu: Incomplete Status in mesa package in Ubuntu: Incomplete Bug description: ack please.. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: xorg 1:7.7+19ubuntu7.1 Uname: Linux 5.4.11-050411-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.9 Architecture: amd64 CompositorRunning: None Date: Tue Jan 14 20:17:26 2020 DistUpgraded: Fresh install DistributionChannelDescriptor: # This is the distribution channel descriptor for the OEM CDs # For more information see http://wiki.ubuntu.com/DistributionChannelDescriptor canonical-oem-somerville-bionic-amd64-20180608-47+beaver-three-eyed-raven+X92 DistroCodename: bionic DistroVariant: ubuntu DkmsStatus: backport-iwlwifi, 8286, 4.15.0-1042-oem, x86_64: installed backport-iwlwifi, 8286, 4.15.0-1066-oem, x86_64: installed ExtraDebuggingInterest: Yes GpuHangFrequency: Very infrequently GraphicsCard: Intel Corporation Device [8086:9bca] (rev 04) (prog-if 00 [VGA controller]) Subsystem: Dell Device [1028:0962] InstallationDate: Installed on 2020-01-13 (1 days ago) InstallationMedia: Ubuntu 18.04 "Bionic" - Build amd64 LIVE Binary 20180608-09:38 Lsusb: Bus 004 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 003 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 002: ID 8087:0029 Intel Corp. Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: Dell Inc. XPS 13 7390 ProcEnviron: TERM=xterm-256color PATH=(custom, no user) LANG=es_CL.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.11-050411-generic root=UUID=8fd25548-00af-4395-92f0-5d7d27a54deb ro quiet splash vt.handoff=1 SourcePackage: xorg Symptom: display Title: Xorg freeze UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 11/25/2019 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.4.0 dmi.board.name: 0377MH dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 10 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr1.4.0:bd11/25/2019:svnDellInc.:pnXPS137390:pvr:rvnDellInc.:rn0377MH:rvrA00:cvnDellInc.:ct10:cvr: dmi.product.family: XPS dmi.product.name: XPS 13 7390 dmi.product.sku: 0962 dmi.sys.vendor: Dell Inc. version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.97-1ubuntu1~18.04.1 version.libgl1-mesa-dri: libgl1-mesa-dri 19.0.8-0ubuntu0~18.04.3 version.libgl1-mesa-glx: libgl1-mesa-glx 19.0.8-0ubuntu0~18.04.3 version.xserver-xorg-core: xserver-xorg-core 2:1.19.6-1ubuntu4.3 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:18.0.1-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20171229-1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.15-2 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1859730/+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 1859730] [NEW] [comet lake] Gnome freezes, icons missing, graphics corruption
You have been subscribed to a public bug: ack please.. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: xorg 1:7.7+19ubuntu7.1 Uname: Linux 5.4.11-050411-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.9 Architecture: amd64 CompositorRunning: None Date: Tue Jan 14 20:17:26 2020 DistUpgraded: Fresh install DistributionChannelDescriptor: # This is the distribution channel descriptor for the OEM CDs # For more information see http://wiki.ubuntu.com/DistributionChannelDescriptor canonical-oem-somerville-bionic-amd64-20180608-47+beaver-three-eyed-raven+X92 DistroCodename: bionic DistroVariant: ubuntu DkmsStatus: backport-iwlwifi, 8286, 4.15.0-1042-oem, x86_64: installed backport-iwlwifi, 8286, 4.15.0-1066-oem, x86_64: installed ExtraDebuggingInterest: Yes GpuHangFrequency: Very infrequently GraphicsCard: Intel Corporation Device [8086:9bca] (rev 04) (prog-if 00 [VGA controller]) Subsystem: Dell Device [1028:0962] InstallationDate: Installed on 2020-01-13 (1 days ago) InstallationMedia: Ubuntu 18.04 "Bionic" - Build amd64 LIVE Binary 20180608-09:38 Lsusb: Bus 004 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 003 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 002: ID 8087:0029 Intel Corp. Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: Dell Inc. XPS 13 7390 ProcEnviron: TERM=xterm-256color PATH=(custom, no user) LANG=es_CL.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.11-050411-generic root=UUID=8fd25548-00af-4395-92f0-5d7d27a54deb ro quiet splash vt.handoff=1 SourcePackage: xorg Symptom: display Title: Xorg freeze UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 11/25/2019 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.4.0 dmi.board.name: 0377MH dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 10 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr1.4.0:bd11/25/2019:svnDellInc.:pnXPS137390:pvr:rvnDellInc.:rn0377MH:rvrA00:cvnDellInc.:ct10:cvr: dmi.product.family: XPS dmi.product.name: XPS 13 7390 dmi.product.sku: 0962 dmi.sys.vendor: Dell Inc. version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.97-1ubuntu1~18.04.1 version.libgl1-mesa-dri: libgl1-mesa-dri 19.0.8-0ubuntu0~18.04.3 version.libgl1-mesa-glx: libgl1-mesa-glx 19.0.8-0ubuntu0~18.04.3 version.xserver-xorg-core: xserver-xorg-core 2:1.19.6-1ubuntu4.3 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:18.0.1-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20171229-1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.15-2 ** Affects: mesa (Ubuntu) Importance: Undecided Status: Incomplete ** Tags: amd64 apport-bug bionic freeze ubuntu -- [comet lake] Gnome freezes, icons missing, graphics corruption https://bugs.launchpad.net/bugs/1859730 You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to mesa 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 1857720] Re: apport-collect -p linux-oem-osp1 not get useful information
I'm going to close this out then and we can use bug 1847967 for tracking getting the hooks SRU'ed. ** Changed in: apport (Ubuntu) Status: Incomplete => Invalid -- 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/1857720 Title: apport-collect -p linux-oem-osp1 not get useful information Status in OEM Priority Project: New Status in apport package in Ubuntu: Invalid Bug description: This is a test of 'apport-collect -p linux-oem-osp1' LP: #1857719 test in pc enablement tools project (apport-collect -p linux-oem-osp1) This is a test of 'apport-collect -p linux' 1857718 test in pc enablement tools project (apport-collect -p linux) looks the first one not get enough information for debugging. What package should apply to 'apport-collect -p' if I would like to report a bug for machine running linux-oem-osp1 kernel? To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/1857720/+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 1857639] Re: DNS server capability detection is broken and has critical consequences when DNSSEC is enabled
``` systemd[1]: Starting Network Name Resolution... systemd-resolved[1392]: Positive Trust Anchors: systemd-resolved[1392]: . IN DS 19036 8 2 49aac11d7b6f6446702e54a1607371607a1a41855200fd2ce1cdde32f24e8fb5 systemd-resolved[1392]: . IN DS 20326 8 2 e06d44b80b8f1d39a95c0b0d7c65d08458e880409bbc683457104237c7f8ec8d systemd-resolved[1392]: Negative trust anchors: 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-addr.arpa 21.172.in-addr.arpa 22.172.in-addr.arpa 23.172.in-addr.arpa 24.172.in-addr.arpa 2 systemd-resolved[1392]: Using system hostname 'machine'. systemd[1]: Started Network Name Resolution. systemd-resolved[1392]: DNSSEC validation failed for question 0.a.c.0.0.0.0.0.0.0.0.0.0.0.0.0.8.e.f.ip6.arpa IN DS: no-signature systemd-resolved[1392]: DNSSEC validation failed for question 0.a.c.0.0.0.0.0.0.0.0.0.0.0.0.0.8.e.f.ip6.arpa IN SOA: no-signature systemd-resolved[1392]: DNSSEC validation failed for question 2.0.a.c.0.0.0.0.0.0.0.0.0.0.0.0.0.8.e.f.ip6.arpa IN DS: no-signature systemd-resolved[1392]: DNSSEC validation failed for question 2.0.a.c.0.0.0.0.0.0.0.0.0.0.0.0.0.8.e.f.ip6.arpa IN SOA: no-signature systemd-resolved[1392]: DNSSEC validation failed for question 2.2.0.a.c.0.0.0.0.0.0.0.0.0.0.0.0.0.8.e.f.ip6.arpa IN DS: no-signature systemd-resolved[1392]: DNSSEC validation failed for question 2.2.0.a.c.0.0.0.0.0.0.0.0.0.0.0.0.0.8.e.f.ip6.arpa IN SOA: no-signature systemd-resolved[1392]: DNSSEC validation failed for question 3.2.2.0.a.c.0.0.0.0.0.0.0.0.0.0.0.0.0.8.e.f.ip6.arpa IN DS: no-signature systemd-resolved[1392]: DNSSEC validation failed for question 3.2.2.0.a.c.0.0.0.0.0.0.0.0.0.0.0.0.0.8.e.f.ip6.arpa IN SOA: no-signature systemd-resolved[1392]: DNSSEC validation failed for question c.3.2.2.0.a.c.0.0.0.0.0.0.0.0.0.0.0.0.0.8.e.f.ip6.arpa IN DS: no-signature systemd-resolved[1392]: DNSSEC validation failed for question c.3.2.2.0.a.c.0.0.0.0.0.0.0.0.0.0.0.0.0.8.e.f.ip6.arpa IN SOA: no-signature systemd-resolved[1392]: DNSSEC validation failed for question c.c.3.2.2.0.a.c.0.0.0.0.0.0.0.0.0.0.0.0.0.8.e.f.ip6.arpa IN DS: no-signature systemd-resolved[1392]: DNSSEC validation failed for question c.c.3.2.2.0.a.c.0.0.0.0.0.0.0.0.0.0.0.0.0.8.e.f.ip6.arpa IN SOA: no-signature systemd-resolved[1392]: DNSSEC validation failed for question 9.c.c.3.2.2.0.a.c.0.0.0.0.0.0.0.0.0.0.0.0.0.8.e.f.ip6.arpa IN DS: no-signature systemd-resolved[1392]: DNSSEC validation failed for question 9.c.c.3.2.2.0.a.c.0.0.0.0.0.0.0.0.0.0.0.0.0.8.e.f.ip6.arpa IN SOA: no-signature systemd-resolved[1392]: DNSSEC validation failed for question b.9.c.c.3.2.2.0.a.c.0.0.0.0.0.0.0.0.0.0.0.0.0.8.e.f.ip6.arpa IN DS: no-signature systemd-resolved[1392]: DNSSEC validation failed for question b.9.c.c.3.2.2.0.a.c.0.0.0.0.0.0.0.0.0.0.0.0.0.8.e.f.ip6.arpa IN SOA: no-signature systemd-resolved[1392]: DNSSEC validation failed for question 1.b.9.c.c.3.2.2.0.a.c.0.0.0.0.0.0.0.0.0.0.0.0.0.8.e.f.ip6.arpa IN DS: no-signature systemd-resolved[1392]: DNSSEC validation failed for question 1.b.9.c.c.3.2.2.0.a.c.0.0.0.0.0.0.0.0.0.0.0.0.0.8.e.f.ip6.arpa IN SOA: no-signature systemd-resolved[1392]: DNSSEC validation failed for question d.1.b.9.c.c.3.2.2.0.a.c.0.0.0.0.0.0.0.0.0.0.0.0.0.8.e.f.ip6.arpa IN DS: no-signature systemd-resolved[1392]: DNSSEC validation failed for question d.1.b.9.c.c.3.2.2.0.a.c.0.0.0.0.0.0.0.0.0.0.0.0.0.8.e.f.ip6.arpa IN SOA: no-signature systemd-resolved[1392]: DNSSEC validation failed for question f.d.1.b.9.c.c.3.2.2.0.a.c.0.0.0.0.0.0.0.0.0.0.0.0.0.8.e.f.ip6.arpa IN DS: no-signature systemd-resolved[1392]: DNSSEC validation failed for question f.d.1.b.9.c.c.3.2.2.0.a.c.0.0.0.0.0.0.0.0.0.0.0.0.0.8.e.f.ip6.arpa IN SOA: no-signature systemd-resolved[1392]: DNSSEC validation failed for question 0.f.d.1.b.9.c.c.3.2.2.0.a.c.0.0.0.0.0.0.0.0.0.0.0.0.0.8.e.f.ip6.arpa IN DS: no-signature systemd-resolved[1392]: DNSSEC validation failed for question 0.f.d.1.b.9.c.c.3.2.2.0.a.c.0.0.0.0.0.0.0.0.0.0.0.0.0.8.e.f.ip6.arpa IN SOA: no-signature systemd-resolved[1392]: DNSSEC validation failed for question 4.0.f.d.1.b.9.c.c.3.2.2.0.a.c.0.0.0.0.0.0.0.0.0.0.0.0.0.8.e.f.ip6.arpa IN DS: no-signature systemd-resolved[1392]: DNSSEC validation failed for question 4.0.f.d.1.b.9.c.c.3.2.2.0.a.c.0.0.0.0.0.0.0.0.0.0.0.0.0.8.e.f.ip6.arpa IN SOA: no-signature systemd-resolved[1392]: DNSSEC validation failed for question f.4.0.f.d.1.b.9.c.c.3.2.2.0.a.c.0.0.0.0.0.0.0.0.0.0.0.0.0.8.e.f.ip6.arpa IN DS: no-signature systemd-resolved[1392]: DNSSEC validation failed for question f.4.0.f.d.1.b.9.c.c.3.2.2.0.a.c.0.0.0.0.0.0.0.0.0.0.0.0.0.8.e.f.ip6.arpa IN SOA: no-signature systemd-resolved[1392]: DNSSEC validation failed for question f.4.0.f.d.1.b.9.c.c.3.2.2.0.a.c.0.0.0.0.0.0.0.0.0.0.0.0.0.8.e.f.ip6.arpa IN PTR: no-signature systemd-resolved[1392]: Using degraded feature set (UDP+EDNS0+DO) for DNS server 8.8.8.8. systemd-resolved[1392]: Using degraded feature set
[Touch-packages] [Bug 1841953] Re: Bionic ⋅ SuperTuxKart ⋅ Flickering shadows ⋅ Haswell i915
Oooh sadness ! My flickering problem is back since those recent updates from official regular repositories : coeur-noir@asgard:~$ dpkg -l | grep mesa ii libegl-mesa0:amd64 19.2.1-1ubuntu1~18.04.1 amd64free implementation of the EGL API -- Mesa vendor library ii libegl1-mesa:amd64 19.2.1-1ubuntu1~18.04.1 amd64transitional dummy package ii libgl1-mesa-dri:amd64 19.2.1-1ubuntu1~18.04.1 amd64free implementation of the OpenGL API -- DRI modules ii libgl1-mesa-dri:i38619.2.1-1ubuntu1~18.04.1 i386 free implementation of the OpenGL API -- DRI modules ii libgl1-mesa-glx:amd64 19.2.1-1ubuntu1~18.04.1 amd64transitional dummy package ii libgl1-mesa-glx:i38619.2.1-1ubuntu1~18.04.1 i386 transitional dummy package ii libglapi-mesa:amd64 19.2.1-1ubuntu1~18.04.1 amd64free implementation of the GL API -- shared library ii libglapi-mesa:i386 19.2.1-1ubuntu1~18.04.1 i386 free implementation of the GL API -- shared library ii libgles2-mesa:amd64 19.2.1-1ubuntu1~18.04.1 amd64transitional dummy package ii libglu1-mesa:amd64 9.0.0-2.1build1 amd64Mesa OpenGL utility library (GLU) ii libglu1-mesa:i386 9.0.0-2.1build1 i386 Mesa OpenGL utility library (GLU) ii libglx-mesa0:amd64 19.2.1-1ubuntu1~18.04.1 amd64free implementation of the OpenGL API -- GLX vendor library ii libglx-mesa0:i386 19.2.1-1ubuntu1~18.04.1 i386 free implementation of the OpenGL API -- GLX vendor library ii libosmesa6:amd6419.2.1-1ubuntu1~18.04.1 amd64Mesa Off-screen rendering extension ii libosmesa6:i386 19.2.1-1ubuntu1~18.04.1 i386 Mesa Off-screen rendering extension ii libwayland-egl1-mesa:amd64 19.2.1-1ubuntu1~18.04.1 amd64transitional dummy package ii mesa-utils 8.4.0-1 amd64Miscellaneous Mesa GL utilities ii mesa-utils-extra8.4.0-1 amd64Miscellaneous Mesa utilies (opengles, egl) ii mesa-va-drivers:amd64 19.2.1-1ubuntu1~18.04.1 amd64Mesa VA-API video acceleration drivers ii mesa-vdpau-drivers:amd6419.2.1-1ubuntu1~18.04.1 amd64Mesa VDPAU video acceleration drivers ii mesa-vulkan-drivers:amd64 19.2.1-1ubuntu1~18.04.1 amd64Mesa Vulkan graphics drivers coeur-noir@asgard:~$ -- 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/1841953 Title: Bionic ⋅ SuperTuxKart ⋅ Flickering shadows ⋅ Haswell i915 Status in mesa package in Ubuntu: Confirmed Status in supertuxkart package in Ubuntu: New Bug description: Hi, for few weeks now, I've noticed a big change in graphic performance while playing famous SuperTuxKart on ubuntu bionic : shadows are flickering, all over the screen, it's a big pain for eyes ( and wonder what would happen for epileptic people ). My computer is : Intel(R) Core(TM) i7-4770K CPU @ 3.50GHz with 16Go ram and Haswell integrated graphics. coeur-noir@asgard:~$ lspci -k | grep -A 2 -i "VGA" 00:02.0 VGA compatible controller: Intel Corporation Xeon E3-1200 v3/4th Gen Core Processor Integrated Graphics Controller (rev 06) Subsystem: ASUSTeK Computer Inc. Xeon E3-1200 v3/4th Gen Core Processor Integrated Graphics Controller Kernel driver in use: i915 coeur-noir@asgard:~$ sudo lshw -c video *-display description: VGA compatible controller produit: Xeon E3-1200 v3/4th Gen Core Processor Integrated Graphics Controller fabriquant: Intel Corporation identifiant matériel: 2 information bus: pci@:00:02.0 version: 06 bits: 64 bits horloge: 33MHz fonctionnalités: msi pm vga_controller bus_master cap_list rom configuration: driver=i915 latency=0 ressources: irq:26 mémoire:f780-f7bf mémoire:e000-efff portE/S:f000(taille=64) mémoire:c-d coeur-noir@asgard:~$ My Ubuntu Budgie 18.04 is
[Touch-packages] [Bug 1857051] Re: Please add ${distro_id}ESM:${distro_codename}-infra-security and ${distro_id}ESM:${distro_codename}-apps-security to allowed origins (on Ubuntu)
** Description changed:
ESM -infra-security and -apps-security will need to
participate in unattended upgrades.
+
+
+ Currently /etc/apt/apt.conf.d/50unattended-upgrades provides:
+ Unattended-Upgrade::Allowed-Origins {
+ "${distro_id}ESM:${distro_codename}";
+ }
+
+
+ Given that there have been ESM apt pocket renames over the last few months,
the above ESM allowed-origin should not apply anymore and can be dropped or
replaced.
+
+ See RT #C122697 and #C121067 for the pocket/suite renames related to ESM
+
+
+ What is needed after the ESM apt pocket/suite renames:
+
+ Support for unattended upgrades for ESM for Infrastructure customers:
+
+
+ Unattended-Upgrade::Allowed-Origins {
+ // Extended Security Maintenance; doesn't necessarily exist for
+ // every release and this system may not have it installed, but if
+ // available, the policy for updates is such that unattended-upgrades
+ // should also install from here by default.
+ "${distro_id}ESM:${distro_codename}-infra-security";
+ "${distro_id}ESMApps:${distro_codename}-apps-security";
+ };
+
+
+ Confirmed proper origin on an attached Trusty instance with ESM-infra enabled:
+
+
+ 500 https://esm.ubuntu.com/ubuntu/ trusty-infra-security/main amd64 Packages
+ release
v=14.04,o=UbuntuESM,a=trusty-infra-security,n=trusty,l=UbuntuESM,c=main
+
+ Confirmed proper origins on Bionic for enabled ESM-infra and ESM-apps on an
AWS Ubuntu PRO instance:
+ 500 https://esm.ubuntu.com/infra/ubuntu bionic-infra-security/main amd64
Packages
+ release
v=18.04,o=UbuntuESM,a=bionic-infra-security,n=bionic,l=UbuntuESM,c=main,b=amd64
+
+ 500 https://esm.ubuntu.com/apps/ubuntu bionic-apps-security/main amd64
Packages
+ release
v=18.04,o=UbuntuESMApps,a=bionic-apps-security,n=bionic,l=UbuntuESMApps,c=main,b=amd64
** Description changed:
ESM -infra-security and -apps-security will need to
participate in unattended upgrades.
-
Currently /etc/apt/apt.conf.d/50unattended-upgrades provides:
Unattended-Upgrade::Allowed-Origins {
- "${distro_id}ESM:${distro_codename}";
+ "${distro_id}ESM:${distro_codename}";
}
-
- Given that there have been ESM apt pocket renames over the last few months,
the above ESM allowed-origin should not apply anymore and can be dropped or
replaced.
+ Given that there have been ESM apt pocket renames over the last few
+ months, the above ESM allowed-origin should not apply anymore and can be
+ dropped or replaced.
See RT #C122697 and #C121067 for the pocket/suite renames related to ESM
-
What is needed after the ESM apt pocket/suite renames:
Support for unattended upgrades for ESM for Infrastructure customers:
-
Unattended-Upgrade::Allowed-Origins {
- // Extended Security Maintenance; doesn't necessarily exist for
- // every release and this system may not have it installed, but if
- // available, the policy for updates is such that unattended-upgrades
- // should also install from here by default.
- "${distro_id}ESM:${distro_codename}-infra-security";
- "${distro_id}ESMApps:${distro_codename}-apps-security";
+ // Extended Security Maintenance; doesn't necessarily exist for
+ // every release and this system may not have it installed, but if
+ // available, the policy for updates is such that unattended-upgrades
+ // should also install from here by default.
+ "${distro_id}ESM:${distro_codename}-infra-security";
+ "${distro_id}ESMApps:${distro_codename}-apps-security";
};
+ === Confirmed proper origin on an attached Trusty instance with ESM-
+ infra enabled:
- Confirmed proper origin on an attached Trusty instance with ESM-infra enabled:
+ 500 https://esm.ubuntu.com/ubuntu/ trusty-infra-security/main amd64 Packages
+ release
v=14.04,o=UbuntuESM,a=trusty-infra-security,n=trusty,l=UbuntuESM,c=main
+ === Confirmed proper origins on Bionic for enabled ESM-infra and ESM-apps on
an AWS Ubuntu PRO instance:
+ 500 https://esm.ubuntu.com/infra/ubuntu bionic-infra-security/main amd64
Packages
+ release
v=18.04,o=UbuntuESM,a=bionic-infra-security,n=bionic,l=UbuntuESM,c=main,b=amd64
- 500 https://esm.ubuntu.com/ubuntu/ trusty-infra-security/main amd64 Packages
- release
v=14.04,o=UbuntuESM,a=trusty-infra-security,n=trusty,l=UbuntuESM,c=main
-
- Confirmed proper origins on Bionic for enabled ESM-infra and ESM-apps on an
AWS Ubuntu PRO instance:
- 500 https://esm.ubuntu.com/infra/ubuntu bionic-infra-security/main amd64
Packages
- release
v=18.04,o=UbuntuESM,a=bionic-infra-security,n=bionic,l=UbuntuESM,c=main,b=amd64
-
- 500 https://esm.ubuntu.com/apps/ubuntu bionic-apps-security/main amd64
Packages
- release
v=18.04,o=UbuntuESMApps,a=bionic-apps-security,n=bionic,l=UbuntuESMApps,c=main,b=amd64
+ 500 https://esm.ubuntu.com/apps/ubuntu bionic-apps-security/main amd64
Packages
+ release
[Touch-packages] [Bug 1859858] Re: udev has truncated ID_SERIAL value for scsi disk
** Tags added: rls-ff-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/1859858 Title: udev has truncated ID_SERIAL value for scsi disk Status in systemd package in Ubuntu: New Status in systemd source package in Focal: New Bug description: 1. root@ubuntu:/home/ubuntu# cat /etc/cloud/build.info build_name: server serial: 20200106 root@ubuntu:/home/ubuntu# lsb_release -rd Description:Ubuntu Focal Fossa (development branch) Release:20.04 2. root@ubuntu:/home/ubuntu# apt-cache policy systemd systemd: Installed: 244-3ubuntu1 Candidate: 244-3ubuntu1 Version table: *** 244-3ubuntu1 500 500 http://archive.ubuntu.com/ubuntu focal/main amd64 Packages 100 /var/lib/dpkg/status 3. ID_SERIAL value should be 322dc58dc023c7008 4. ID_SERIAL value is 3 -- Launching a qemu VM with the same extra scsi disk like so: -drive file=extra_disk_1.img,id=drv4,if=none,format=raw,index=4,cache=unsafe \ -device scsi-hd,drive=drv4,serial=0x22dc58dc023c7008,wwn=0x22dc58dc023c7008 On Focal udevadm info output: root@ubuntu:/home/ubuntu# udevadm info --query=property /dev/sdc DEVPATH=/devices/pci:00/:00:03.0/virtio0/host2/target2:0:2/2:0:2:0/block/sdc DEVNAME=/dev/sdc DEVTYPE=disk MAJOR=8 MINOR=32 SUBSYSTEM=block USEC_INITIALIZED=1497555 SCSI_TPGS=0 SCSI_TYPE=disk SCSI_VENDOR=QEMU SCSI_VENDOR_ENC=QEMU\x20\x20\x20\x20 SCSI_MODEL=QEMU_HARDDISK SCSI_MODEL_ENC=QEMU\x20HARDDISK\x20\x20\x20 SCSI_REVISION=2.5+ ID_SCSI=1 ID_SCSI_INQUIRY=1 ID_VENDOR=QEMU ID_VENDOR_ENC=QEMU\x20\x20\x20\x20 ID_MODEL=QEMU_HARDDISK ID_MODEL_ENC=QEMU\x20HARDDISK\x20\x20\x20 ID_REVISION=2.5+ ID_TYPE=disk SCSI_IDENT_SERIAL=0x22dc58dc023c7008 SCSI_IDENT_LUN_VENDOR=0x22dc58dc023c7008 SCSI_IDENT_LUN_NAA_EXT=22dc58dc023c7008 ID_WWN=0x22dc58dc023c7008 ID_WWN_WITH_EXTENSION=0x22dc58dc023c7008 ID_BUS=scsi ID_SERIAL=3 ID_SERIAL_SHORT=22dc58dc023c7008 MPATH_SBIN_PATH=/sbin DM_MULTIPATH_DEVICE_PATH=0 ID_PATH=pci-:00:03.0-scsi-0:0:2:0 ID_PATH_TAG=pci-_00_03_0-scsi-0_0_2_0 ID_FS_UUID=b20cf5c1-15ae-48a7-a5d9-dfcfd37df494 ID_FS_UUID_ENC=b20cf5c1-15ae-48a7-a5d9-dfcfd37df494 ID_FS_UUID_SUB=e06d861c-c6e2-497c-b14f-265ae37060e2 ID_FS_UUID_SUB_ENC=e06d861c-c6e2-497c-b14f-265ae37060e2 ID_FS_TYPE=btrfs ID_FS_USAGE=filesystem ID_BTRFS_READY=1 DEVLINKS=/dev/disk/by-id/scsi-3 /dev/disk/by-id/scsi-0QEMU_QEMU_HARDDISK_0x22dc58dc023c7008 /dev/disk/by-path/pci-:00:03.0-scsi-0:0:2:0 /dev/disk/by-id/wwn-0x22dc58dc023c7008 /dev/disk/by-id/scsi-SQEMU_QEMU_HARDDISK_0x22dc58dc023c7008 /dev/disk/by-uuid/b20cf5c1-15ae-48a7-a5d9-dfcfd37df494 /dev/disk/by-id/scsi-322dc58dc023c7008 TAGS=:systemd: On Bionic: root@ubuntu:~# cat /etc/cloud/build.info build_name: server serial: 20200112 root@ubuntu:~# lsb_release -rd Description:Ubuntu 18.04.3 LTS Release:18.04 root@ubuntu:~# apt-cache policy systemd systemd: Installed: 237-3ubuntu10.33 Candidate: 237-3ubuntu10.33 Version table: *** 237-3ubuntu10.33 500 500 http://archive.ubuntu.com/ubuntu bionic-updates/main amd64 Packages 100 /var/lib/dpkg/status 237-3ubuntu10.29 500 500 http://security.ubuntu.com/ubuntu bionic-security/main amd64 Packages 237-3ubuntu10 500 500 http://archive.ubuntu.com/ubuntu bionic/main amd64 Packages root@ubuntu:~# udevadm info --query=property /dev/sdc DEVLINKS=/dev/disk/by-uuid/13a8a15f-4f6b-4904-b307-339b825c445b /dev/disk/by-path/pci-:00:03.0-scsi-0:0:2:0 /dev/disk/by-id/wwn-0x22dc58dc023c7008 /dev/disk/by-id/scsi-322dc58dc023c7008 DEVNAME=/dev/sdc DEVPATH=/devices/pci:00/:00:03.0/virtio0/host2/target2:0:2/2:0:2:0/block/sdc DEVTYPE=disk ID_BTRFS_READY=1 ID_BUS=scsi ID_FS_TYPE=btrfs ID_FS_USAGE=filesystem ID_FS_UUID=13a8a15f-4f6b-4904-b307-339b825c445b ID_FS_UUID_ENC=13a8a15f-4f6b-4904-b307-339b825c445b ID_FS_UUID_SUB=81178585-f7c0-429a-b02d-aeb2f245342c ID_FS_UUID_SUB_ENC=81178585-f7c0-429a-b02d-aeb2f245342c ID_MODEL=QEMU_HARDDISK ID_MODEL_ENC=QEMU\x20HARDDISK\x20\x20\x20 ID_PATH=pci-:00:03.0-scsi-0:0:2:0 ID_PATH_TAG=pci-_00_03_0-scsi-0_0_2_0 ID_REVISION=2.5+ ID_SCSI=1 ID_SCSI_SERIAL=0x22dc58dc023c7008 ID_SERIAL=322dc58dc023c7008 ID_SERIAL_SHORT=22dc58dc023c7008 ID_TYPE=disk ID_VENDOR=QEMU ID_VENDOR_ENC=QEMU\x20\x20\x20\x20 ID_WWN=0x22dc58dc023c7008 ID_WWN_WITH_EXTENSION=0x22dc58dc023c7008 MAJOR=8 MINOR=32 SUBSYSTEM=block TAGS=:systemd: USEC_INITIALIZED=2069797 ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: udev 244-3ubuntu1 ProcVersionSignature: Ubuntu 5.3.0-24.26-lowlatency 5.3.10 Uname: Linux 5.3.0-24-lowlatency x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
[Touch-packages] [Bug 1857051] Re: Please add ${distro_id}ESM:${distro_codename}-infra-security and ${distro_id}ESM:${distro_codename}-apps-security to allowed origins (on Ubuntu)
Should previous ESM repos be removed?
Could you please share the design document for the new origins at least
on an other channel?
I saw this example somewhere, and it does not match ${distro_id}ESM:... :
o=UbuntuESMApps,a=bionic-apps-security
** Changed in: unattended-upgrades (Ubuntu)
Status: In Progress => Incomplete
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to unattended-upgrades in
Ubuntu.
https://bugs.launchpad.net/bugs/1857051
Title:
Please add ${distro_id}ESM:${distro_codename}-infra-security and
${distro_id}ESM:${distro_codename}-apps-security to allowed origins
(on Ubuntu)
Status in unattended-upgrades package in Ubuntu:
Incomplete
Status in unattended-upgrades source package in Trusty:
New
Status in unattended-upgrades source package in Xenial:
New
Status in unattended-upgrades source package in Bionic:
New
Bug description:
ESM -infra-security and -apps-security will need to
participate in unattended upgrades.
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/unattended-upgrades/+bug/1857051/+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 1857051] Re: Please add ${distro_id}ESM:${distro_codename}-infra-security and ${distro_id}ESM:${distro_codename}-apps-security to allowed origins (on Ubuntu)
https://github.com/mvo5/unattended-upgrades/pull/243
** Changed in: unattended-upgrades (Ubuntu)
Status: New => Incomplete
** Changed in: unattended-upgrades (Ubuntu)
Status: Incomplete => In Progress
** Changed in: unattended-upgrades (Ubuntu)
Importance: Undecided => High
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to unattended-upgrades in
Ubuntu.
https://bugs.launchpad.net/bugs/1857051
Title:
Please add ${distro_id}ESM:${distro_codename}-infra-security and
${distro_id}ESM:${distro_codename}-apps-security to allowed origins
(on Ubuntu)
Status in unattended-upgrades package in Ubuntu:
In Progress
Status in unattended-upgrades source package in Trusty:
New
Status in unattended-upgrades source package in Xenial:
New
Status in unattended-upgrades source package in Bionic:
New
Bug description:
ESM -infra-security and -apps-security will need to
participate in unattended upgrades.
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/unattended-upgrades/+bug/1857051/+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 1855445] Re: Touchpad is not working
Could you please check if it works when booting a previous kernel? This is not a bug in unattended-upgrades for sure, but a regression in something installed by it. ** Changed in: unattended-upgrades (Ubuntu) Status: New => Incomplete -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to unattended-upgrades in Ubuntu. https://bugs.launchpad.net/bugs/1855445 Title: Touchpad is not working Status in unattended-upgrades package in Ubuntu: Incomplete Bug description: Day before yesterday, I updated Ubuntu in my laptop, then the next morning when I try to use touch-pad it wasn't working, I switched to windows to see whether touch-pad was working or not, it was working fine. Here's the details $ xinput ⎡ Virtual core pointerid=2[master pointer (3)] ⎜ ↳ Virtual core XTEST pointer id=4[slave pointer (2)] ⎜ ↳ Logitech USB Receiver id=11 [slave pointer (2)] ⎜ ↳ SynPS/2 Synaptics TouchPad id=17 [slave pointer (2)] ⎜ ↳ Synaptics TM3252-001id=13 [slave pointer (2)] ⎣ Virtual core keyboard id=3[master keyboard (2)] ↳ Virtual core XTEST keyboard id=5[slave keyboard (3)] ↳ Power Buttonid=6[slave keyboard (3)] ↳ Video Bus id=7[slave keyboard (3)] ↳ Power Buttonid=8[slave keyboard (3)] ↳ Sleep Buttonid=9[slave keyboard (3)] ↳ Logitech USB Receiver id=10 [slave keyboard (3)] ↳ Integrated_Webcam_HD: Integrate id=12 [slave keyboard (3)] ↳ Intel HID eventsid=14 [slave keyboard (3)] ↳ Dell WMI hotkeysid=15 [slave keyboard (3)] ↳ AT Translated Set 2 keyboardid=16 [slave keyboard (3)] ↳ Logitech USB Receiver id=18 [slave keyboard (3)] $ dmesg | grep i2c [0.766631] i2c /dev entries driver [2.419114] psmouse serio1: synaptics: Your touchpad (PNP: SYN0609 PNP0f13) says it can support a different bus. If i2c-hid and hid-rmi are not used, you might want to try setting psmouse.synaptics_intertouch to 1 and report this to linux-in...@vger.kernel.org. [ 34.129216] i2c_hid i2c-DELL0792:00: i2c-DELL0792:00 supply vdd not found, using dummy regulator [ 34.837858] input: Synaptics TM3252-001 as /devices/pci:00/:00:15.0/i2c_designware.0/i2c-0/i2c-DELL0792:00/0018:06CB:7F09.0003/input/input13 [ 34.837945] hid-rmi 0018:06CB:7F09.0003: input,hidraw2: I2C HID v1.00 Mouse [DELL0792:00 06CB:7F09] on i2c-DELL0792:00 $ locate i2c-designware /lib/modules/4.15.0-70-generic/kernel/drivers/i2c/busses/i2c-designware-pci.ko /lib/modules/4.15.0-72-generic/kernel/drivers/i2c/busses/i2c-designware-pci.ko /usr/src/linux-headers-4.15.0-70/include/linux/platform_data/i2c-designware.h /usr/src/linux-headers-4.15.0-72/include/linux/platform_data/i2c-designware.h $ uname -a Linux ubuntu-vostro-14-3468 4.15.0-72-generic #81-Ubuntu SMP Tue Nov 26 12:20:02 UTC 2019 x86_64 x86_64 x86_64 GNU/Linux $ lsb_release -crid Distributor ID: Ubuntu Description: Ubuntu 18.04.3 LTS Release: 18.04 Codename: bionic To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/unattended-upgrades/+bug/1855445/+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 1859857] Re: network-manager keeps asking for wifi password can't connect to any wifi
Thanks for looking into this issue! "From what version to what version did you update?" I did just one of the regular upgrades, no upgrade to a new ubuntu version. Unfortunately, I cannot say which packages were updated. "What desktop do you use?" I am using the kubuntu flavour, thus the desktop was kde. Maybe I should note that I enabled the kubuntu-backports (kubuntu-ppa-ubuntu-backports-eoan) I added the result of journalctl -b 0. Please do not wonder, here I used another kernel as I did, when firstly reporting the bug, however, the issue is the same. Some more observations: - I tried different kernels (5.3.0-23, 5.3.0-26, 5.3.0-26-lowlatency). There is always the same behaviour. (This is in contrast to report #1859289, where lowlatency seemed to work) - I tried also to connect to a hotspot created from my mobile, this also does not work (it also used wpa password protection). - I tried to connect to a public access point without password protection. Here the wifi is working flawlessy. Best regards. ** Attachment added: "Result of journalctl -b 0" https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1859857/+attachment/5320935/+files/journald.txt -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to network-manager in Ubuntu. https://bugs.launchpad.net/bugs/1859857 Title: network-manager keeps asking for wifi password can't connect to any wifi Status in network-manager package in Ubuntu: Incomplete Bug description: This bug is the same as reported by #1859289, however I was not able to find this when using the ubuntu-bug tool. Since the last update my network-manager keeps asking me for wifi passworts, but then never connects. Password is definitely correct. Everything worked before the update. lsb_release -rd Description:Ubuntu 19.10 Release:19.10 ProblemType: Bug DistroRelease: Ubuntu 19.10 Package: network-manager 1.20.4-2ubuntu2 ProcVersionSignature: Ubuntu 5.3.0-23.25-generic 5.3.7 Uname: Linux 5.3.0-23-generic x86_64 ApportVersion: 2.20.11-0ubuntu8.2 Architecture: amd64 Date: Wed Jan 15 19:12:42 2020 IfupdownConfig: # interfaces(5) file used by ifup(8) and ifdown(8) auto lo iface lo inet loopback InstallationDate: Installed on 2019-05-27 (233 days ago) InstallationMedia: Kubuntu 19.04 "Disco Dingo" - Release amd64 (20190416) IpRoute: default via 192.168.1.1 dev enp0s25 proto dhcp metric 100 169.254.0.0/16 dev enp0s25 scope link metric 1000 192.168.1.0/24 dev enp0s25 proto kernel scope link src 192.168.1.23 metric 100 NetworkManager.state: [main] NetworkingEnabled=true WirelessEnabled=true WWANEnabled=false ProcEnviron: LANGUAGE= TERM=xterm-256color PATH=(custom, no user) LANG=de_DE.UTF-8 SHELL=/bin/bash SourcePackage: network-manager UpgradeStatus: Upgraded to eoan on 2019-10-23 (83 days ago) nmcli-nm: RUNNING VERSION STATE STARTUP CONNECTIVITY NETWORKING WIFI-HW WIFI WWAN-HW WWAN running 1.20.4 connected started full enabled enabled enabled enabled disabled To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1859857/+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 1859610] Re: python-gi/arm64 segfaults with the focal-proposed libffi version
works for me as well. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to libffi in Ubuntu. https://bugs.launchpad.net/bugs/1859610 Title: python-gi/arm64 segfaults with the focal-proposed libffi version Status in libffi package in Ubuntu: Incomplete Status in libffi source package in Focal: Incomplete Bug description: Testcase, on focal/arm64 $ sudo apt install python3-goocalendar $ python3 -c "import goocalendar ; print(goocalendar.__version__)" -> works fine install the python3-gi package from focal-proposed it segfaults in libffi Program received signal SIGSEGV, Segmentation fault. 0x in ?? () (gdb) bt #0 0x in ?? () #1 0xf7390ff8 in ffi_call_SYSV () at ../src/aarch64/sysv.S:114 #2 0xf7390634 in ffi_call_int (cif=0xa12d78, fn=, orig_rvalue=, avalue=0x0, closure=) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libffi/+bug/1859610/+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 1858802] Re: libblkid: no bcache UUID due to ambivalent detection of bcache and xfs_external_log for regular xfs in bcache backing device
LP#1845529 is now fix released (thanks @sil2100), and the SRUs for E/B/X have been uploaded. (The SRU for D is skipped as D will be EOL in 7 days, the time needed to stay in -proposed.) -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to util-linux in Ubuntu. https://bugs.launchpad.net/bugs/1858802 Title: libblkid: no bcache UUID due to ambivalent detection of bcache and xfs_external_log for regular xfs in bcache backing device Status in util-linux package in Ubuntu: In Progress Status in util-linux source package in Xenial: In Progress Status in util-linux source package in Bionic: In Progress Status in util-linux source package in Disco: In Progress Status in util-linux source package in Eoan: In Progress Status in util-linux source package in Focal: In Progress Status in util-linux package in Debian: Unknown Bug description: [Impact] * Users with an XFS filesystem on top of bcache (this is seen on some ceph, cloud deployments) might fail to reference the bcache device by UUID or other udev properties. * The journal of the regular XFS filesystem in the bcache device is incorrectly detected as an XFS external log; so two superblocks are detected (bcache and xfs_external_log). * Thus blkid fails with ambivalent superblocks detected then doesn't provide the usual udev properties (UUID, etc.) * The fix improves the probe function for XFS external log so it detects it's regular XFS and bails out. [Test Case] * See test steps detailed in comment #7 and later. - Create an XFS filesystem with the journal/log in the beginning of the bcache device (< 256K). - Stop the bcache device. - Run '$ blkid -o udev -p $BCACHE_BACKING_DEVICE'. $ sudo make-bcache -B $BACKING_DEV $ sudo mkfs.xfs -d agsize=16m -l agnum=0 -f $BCACHE_DEV $ echo 1 | sudo tee /sys/block/$(basename $BCACHE_DEV)/bcache/stop $ sudo blkid -o udev -p $BACKING_DEV [Regression Potential] * The patch only changes the detection function for XFS external log to be more general about the sector where the magic of regular XFS may be found (which is shifted inside the bcache.) * It still checks at sector zero (the only one checked previously), so this behavior didn't change. * Possible regressions are actual XFS external log devices that are not anymore detected as such. (Although that would probably indicate a different bug in libblkid.) [Other Info] * upstream commit: https://git.kernel.org/pub/scm/utils/util-linux/util-linux.git/commit/?id=d756af7d640c51ce8d1414607bd3f17eeecf2424 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/util-linux/+bug/1858802/+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 1847967] Re: oem kernel packages treated differently from generic kernel ones
I verified #9, it works as expected. -- 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/1847967 Title: oem kernel packages treated differently from generic kernel ones Status in OEM Priority Project: New Status in apport package in Ubuntu: Fix Released Status in apport source package in Bionic: In Progress Status in apport source package in Disco: In Progress Status in apport source package in Eoan: In Progress Status in apport source package in Focal: Fix Released Bug description: [SRU Justification] [Impact] When `apport-bug linux` was executed on systems with linux-oem, linux-oem-osp1 kernels, many details are not included as generic linux kernel does. Alsa info, dmesg, lspci, lsusb, DMI, etc. are missing. [Fix] Fix already merged in Focal: https://bazaar.launchpad.net/~ubuntu-core-dev/ubuntu/focal/apport/ubuntu/revision/2724 . SRU merge proposals in: * https://code.launchpad.net/~vicamo/ubuntu/bionic/apport/bug-1847967/+merge/376380 * https://code.launchpad.net/~vicamo/ubuntu/disco/apport/bug-1847967/+merge/376381 * https://code.launchpad.net/~vicamo/ubuntu/eoan/apport/bug-1847967/+merge/374263 [Test Case] 1. Boot with linux-oem or linux-oem-osp1 kernel and try to collect apport logs with: $ apport-cli --save saved.apport linux-oem-osp1 2. Make sure the report contains PCI/ALSA/DMI/Sysfs info. [Regression Potential] Low. original bug description When `apport-bug linux` was executed on systems with linux-oem, linux- oem-osp1 kernels, many details are not included as generic linux kernel does. Alsa info, dmesg, lspci, lsusb, DMI, etc. are missing. To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/1847967/+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 1857720] Re: apport-collect -p linux-oem-osp1 not get useful information
@brian-murray I verified LP: #1847967 , it works as expected. -- 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/1857720 Title: apport-collect -p linux-oem-osp1 not get useful information Status in OEM Priority Project: New Status in apport package in Ubuntu: Incomplete Bug description: This is a test of 'apport-collect -p linux-oem-osp1' LP: #1857719 test in pc enablement tools project (apport-collect -p linux-oem-osp1) This is a test of 'apport-collect -p linux' 1857718 test in pc enablement tools project (apport-collect -p linux) looks the first one not get enough information for debugging. What package should apply to 'apport-collect -p' if I would like to report a bug for machine running linux-oem-osp1 kernel? To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/1857720/+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 1847570] Re: PulseAudio automatically switches to HDMI sound output on login
So far it's fixed for me! Yay!!! -- 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/1847570 Title: PulseAudio automatically switches to HDMI sound output on login Status in PulseAudio: Fix Released Status in pulseaudio package in Ubuntu: Fix Released Status in pulseaudio source package in Eoan: Fix Released Status in pulseaudio source package in Focal: Fix Released Bug description: [Impact] On my freshly installed eoan system I have two output devices: - HDMI/DisplayPort 2 - GK208 ... - Line Out - Family 17h ... When I login into the system pulseaudio always select the "wrong" one (HDMI) and I need to go to gnome-settings/Sound/Output Device and switch to "line out". This applies to every login/logout not just reboots. [Test Case] 0. Plug in a monitor that supports HDMI audio (one that appears in your Settings>Sound) 1. Log out and in again. Verify the default audio device in Settings is still speakers or headphones. Not the monitor's HDMI audio device. [Regression Potential] The behaviour is changed back to what it was before 19.10, some users might find it inconvenient and prefer the auto switch but the feedback we got shows it's unreliable and an annoying for the majority of our users so we will got back to default to safest behaviour. The fix proposed just reverts to the same code used in PulseAudio 12 and earlier. It has also been released and verified on focal already. [Workaround] Comment out: load-module module-switch-on-port-available load-module module-switch-on-connect from /etc/pulse/default.pa To manage notifications about this bug go to: https://bugs.launchpad.net/pulseaudio/+bug/1847570/+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 1859610] Re: python-gi/arm64 segfaults with the focal-proposed libffi version
Cannot reproduce: $ uname -a Linux Mcdivitt-B0-Cartridge37 5.4.0-9-generic #12-Ubuntu SMP Mon Dec 16 22:33:31 UTC 2019 aarch64 aarch64 aarch64 GNU/Linux $ dpkg -l | grep -e libffi -e python3-gi ii libffi6:arm643.2.1-9 arm64Foreign Function Interface library runtime ii libffi7:arm643.3-2.3build1 arm64Foreign Function Interface library runtime ii python3-gi 3.34.0-3build2 arm64Python 3 bindings for gobject-introspection libraries ii python3-gi-cairo 3.34.0-3build2 arm64Python 3 Cairo bindings for the GObject library ii python3-github 1.43.7-1 all Access the full Github API v3 from Python3 ii python3-gitlab 1:1.15.0-1all Python 3 GitLab API client library $ python3 -c "import goocalendar ; print(goocalendar.__version__)" Unable to init server: Could not connect: Connection refused Unable to init server: Could not connect: Connection refused 0.5 python3-gi depends on libffi7 ** Changed in: libffi (Ubuntu Focal) Status: New => Incomplete -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to libffi in Ubuntu. https://bugs.launchpad.net/bugs/1859610 Title: python-gi/arm64 segfaults with the focal-proposed libffi version Status in libffi package in Ubuntu: Incomplete Status in libffi source package in Focal: Incomplete Bug description: Testcase, on focal/arm64 $ sudo apt install python3-goocalendar $ python3 -c "import goocalendar ; print(goocalendar.__version__)" -> works fine install the python3-gi package from focal-proposed it segfaults in libffi Program received signal SIGSEGV, Segmentation fault. 0x in ?? () (gdb) bt #0 0x in ?? () #1 0xf7390ff8 in ffi_call_SYSV () at ../src/aarch64/sysv.S:114 #2 0xf7390634 in ffi_call_int (cif=0xa12d78, fn=, orig_rvalue=, avalue=0x0, closure=) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libffi/+bug/1859610/+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 1847570] Re: PulseAudio automatically switches to HDMI sound output on login
Woot! Thanks for rolling this out all involved! \o/ Stuff like this is why I love FOSS. Now to try it out! -- 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/1847570 Title: PulseAudio automatically switches to HDMI sound output on login Status in PulseAudio: Fix Released Status in pulseaudio package in Ubuntu: Fix Released Status in pulseaudio source package in Eoan: Fix Released Status in pulseaudio source package in Focal: Fix Released Bug description: [Impact] On my freshly installed eoan system I have two output devices: - HDMI/DisplayPort 2 - GK208 ... - Line Out - Family 17h ... When I login into the system pulseaudio always select the "wrong" one (HDMI) and I need to go to gnome-settings/Sound/Output Device and switch to "line out". This applies to every login/logout not just reboots. [Test Case] 0. Plug in a monitor that supports HDMI audio (one that appears in your Settings>Sound) 1. Log out and in again. Verify the default audio device in Settings is still speakers or headphones. Not the monitor's HDMI audio device. [Regression Potential] The behaviour is changed back to what it was before 19.10, some users might find it inconvenient and prefer the auto switch but the feedback we got shows it's unreliable and an annoying for the majority of our users so we will got back to default to safest behaviour. The fix proposed just reverts to the same code used in PulseAudio 12 and earlier. It has also been released and verified on focal already. [Workaround] Comment out: load-module module-switch-on-port-available load-module module-switch-on-connect from /etc/pulse/default.pa To manage notifications about this bug go to: https://bugs.launchpad.net/pulseaudio/+bug/1847570/+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 1849859] Re: smb printing fails
Upstream committed more changes in this area, I have to check out what the latest patches look like. Upstream's intention I think was to switch wrappers to the krb5 one, which would then call smbspool if no krb5 auth is involved. -- 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/1849859 Title: smb printing fails Status in cups package in Ubuntu: Confirmed Status in samba package in Ubuntu: Confirmed Status in system-config-printer package in Ubuntu: Confirmed Bug description: when I connect to smb server (nas) permanently appears "Error while getting peer-to-peer dbus connection: Operation was cancelled" The printer at this NAS doesn't work too. "held for authentication KeyError: 'auth-info-required'" The same printer at usb port works fine. Ubuntu development version 20.04 system-config-printer version 1.5.11-4ubuntu1 smbclient version 2:4.10.7+dfsg-0ubuntu3 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/cups/+bug/1849859/+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 1830408] Re: [nouveau][XFCE] Do not see login screen after screen is blanked
Does it work better with nvidia driver? You could use another locker in 18.10 as workaround. See contents of /usr/bin/xflock4 script for hint. (You have to kill light-locker process and make it not start in "Session and Startup" dialog. -- 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/1830408 Title: [nouveau][XFCE] Do not see login screen after screen is blanked Status in lightdm package in Ubuntu: New Bug description: I've just upgraded to 18.10 from 18.04. Now when power manager (or whoever) puts the screen to blank, I cannot login, because I do not see anything. Befeore the upgrade, mouse move or keypress led to login screen. Now does not. Workaround: When I go to terminal on tty1 and then back CTRL+ALT+F7, login screen appears. Where is the problem and how to fix it please? ProblemType: Bug DistroRelease: Ubuntu 18.10 Package: xorg 1:7.7+19ubuntu8 ProcVersionSignature: Ubuntu 4.18.0-20.21-generic 4.18.20 Uname: Linux 4.18.0-20-generic x86_64 ApportVersion: 2.20.10-0ubuntu13.3 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: None CurrentDesktop: XFCE Date: Fri May 24 17:59:31 2019 DistUpgraded: 2019-05-24 13:40:45,847 ERROR got error from PostInstallScript ./xorg_fix_proprietary.py (g-exec-error-quark: Failed to execute child process “./xorg_fix_proprietary.py” (No such file or directory) (8)) DistroCodename: cosmic DistroVariant: ubuntu ExtraDebuggingInterest: Yes GraphicsCard: Intel Corporation 2nd Generation Core Processor Family Integrated Graphics Controller [8086:0116] (rev 09) (prog-if 00 [VGA controller]) Subsystem: ASUSTeK Computer Inc. 2nd Generation Core Processor Family Integrated Graphics Controller [1043:1682] NVIDIA Corporation GF119M [GeForce GT 520M] [10de:1050] (rev a1) (prog-if 00 [VGA controller]) Subsystem: ASUSTeK Computer Inc. GF119M [GeForce GT 520M] [1043:1682] InstallationDate: Installed on 2018-09-03 (263 days ago) InstallationMedia: Xubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 (20180725) MachineType: ASUSTeK Computer Inc. U36SD ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.18.0-20-generic root=UUID=aa87c0a2-5b06-40fb-82dd-fbccd7c800e6 ro quiet splash vt.handoff=1 SourcePackage: xorg Symptom: display UpgradeStatus: Upgraded to cosmic on 2019-05-24 (0 days ago) dmi.bios.date: 07/12/2011 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: U36SD.205 dmi.board.asset.tag: ATN12345678901234567 dmi.board.name: U36SD dmi.board.vendor: ASUSTeK Computer Inc. dmi.board.version: 1.0 dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: ASUSTeK Computer Inc. dmi.chassis.version: 1.0 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrU36SD.205:bd07/12/2011:svnASUSTeKComputerInc.:pnU36SD:pvr1.0:rvnASUSTeKComputerInc.:rnU36SD:rvr1.0:cvnASUSTeKComputerInc.:ct10:cvr1.0: dmi.product.family: U dmi.product.name: U36SD dmi.product.version: 1.0 dmi.sys.vendor: ASUSTeK Computer Inc. version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.95-1 version.libgl1-mesa-dri: libgl1-mesa-dri 18.2.8-0ubuntu0~18.10.2 version.libgl1-mesa-glx: libgl1-mesa-glx 18.2.8-0ubuntu0~18.10.2 version.xserver-xorg-core: xserver-xorg-core 2:1.20.1-3ubuntu2.1 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:18.1.0-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20171229-1ubuntu1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.15-3 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/lightdm/+bug/1830408/+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 1859610] Re: python-gi/arm64 segfaults with the focal-proposed libffi version
** Also affects: libffi (Ubuntu Focal) Importance: High Status: New ** Tags removed: rls-ff-incoming ** Tags added: arm64 -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to libffi in Ubuntu. https://bugs.launchpad.net/bugs/1859610 Title: python-gi/arm64 segfaults with the focal-proposed libffi version Status in libffi package in Ubuntu: New Status in libffi source package in Focal: New Bug description: Testcase, on focal/arm64 $ sudo apt install python3-goocalendar $ python3 -c "import goocalendar ; print(goocalendar.__version__)" -> works fine install the python3-gi package from focal-proposed it segfaults in libffi Program received signal SIGSEGV, Segmentation fault. 0x in ?? () (gdb) bt #0 0x in ?? () #1 0xf7390ff8 in ffi_call_SYSV () at ../src/aarch64/sysv.S:114 #2 0xf7390634 in ffi_call_int (cif=0xa12d78, fn=, orig_rvalue=, avalue=0x0, closure=) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libffi/+bug/1859610/+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 1844853] Re: IBus no longer works in Qt applications after upgrade
Hello Adam, or anyone else affected,
Accepted glib2.0 into eoan-proposed. The package will build now and be
available at
https://launchpad.net/ubuntu/+source/glib2.0/2.62.3-2~ubuntu19.10.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 and change the tag from
verification-needed-eoan to verification-done-eoan. If it does not fix
the bug for you, please add a comment stating that, and change the tag
to verification-failed-eoan. 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.
** Tags removed: verification-done-eoan
** Tags added: verification-needed-eoan
--
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/1844853
Title:
IBus no longer works in Qt applications after upgrade
Status in GLib:
Fix Released
Status in ibus:
Fix Released
Status in glib2.0 package in Ubuntu:
Fix Released
Status in ibus package in Ubuntu:
Fix Released
Status in glib2.0 source package in Xenial:
Fix Committed
Status in glib2.0 source package in Bionic:
Fix Committed
Status in glib2.0 source package in Disco:
Fix Committed
Status in glib2.0 source package in Eoan:
Fix Committed
Status in glib2.0 source package in Focal:
Fix Released
Status in ibus source package in Focal:
Fix Released
Status in glib2.0 package in Debian:
Fix Released
Bug description:
[Impact]
IBus was broken for Qt applications as a regression due to the fix of
CVE-2019-14822. As a result the IBus patch was disabled temporarily,
which fixed IBus from a usability POV.
The real fix has been made in glib2.0, and the updates in -proposed
will allow the IBus patch to be re-enabled.
[Test Case]
* On a standard Ubuntu {eoan,disco,bionic,xenial} installation
- Upgrade the glib2.0 packages from
{eoan,disco,bionic,xenial}-proposed
- Upgrade the ibus packages from
https://launchpad.net/~ubuntu-security-proposed/+archive/ubuntu/ppa
- Install some IBus input method, e.g. ibus-libpinyin
- Install some Qt application, e.g. Kate
* Relogin (maybe reboot)
* Add the input method to the input sources
* Open the Qt app and try to input something using the IBus IM
=> Find that the transliteration works as expected
[Regression Potential]
The applicable patches origin from glib upstream:
https://gitlab.gnome.org/GNOME/glib/merge_requests/1176
Consequently the changes have been reviewed by the glib maintainer, but also
tested by the IBus maintainer, by me (gunnarhj), and - of course - the author
Simon McVittie. The changes have been in Debian unstable since 2019-10-30.
[Original description]
Kubuntu Release 18.04.3 LTS
Expected behavior:
ibus continues working as before after applying security update
1.5.17-ubuntu5.1 from version 1.5.17-ubuntu5.
Observed behavior:
ibus is not usable anymore in Qt applications.
After updating ibus and the related packages ibus-gtk, ibus-gtk3,
libibus-1.0-5 and gir1.2-ibus-1.0 all from version 1.5.17-ubuntu5 to
1.5.17-ubuntu5.1, I can no longer use ibus in Qt applications. Using
shift-space no longer changes the selected input method and even when i switch
to the mozc input method in a gtk application, i can not use it in any Qt
applications.
When starting qtconfig in a terminal, I also get the following message:
Bus::open: Connect ibus failed!
IBusInputContext::createInputContext: no connection to ibus-daemon
This bug was not present in version 1.5.17-3ubuntu5 and I also
confirmed that downgrading the packages to version 1.5.17-3ubuntu4
restores ibus functionality in Qt applications.
ProblemType: Bug
DistroRelease: Ubuntu 18.04
Package: ibus 1.5.17-3ubuntu5.1
ProcVersionSignature: Ubuntu 5.0.0-30.32~18.04.1-generic 5.0.21
Uname: Linux 5.0.0-30-generic x86_64
NonfreeKernelModules: nvidia_modeset nvidia
ApportVersion: 2.20.9-0ubuntu7.7
Architecture: amd64
CurrentDesktop: KDE
Date: Sat Sep 21 07:58:56 2019
InstallationDate: Installed on 2019-06-28 (84 days ago)
InstallationMedia: Kubuntu 18.04.2 LTS "Bionic Beaver" - Release amd64
(20190210)
SourcePackage: ibus
UpgradeStatus: No upgrade log present (probably fresh install)
To manage notifications about this
[Touch-packages] [Bug 1848202] Re: Use after free in gdbus leads to eds segfaults
Hello errors.ubuntu.com, or anyone else affected, Accepted glib2.0 into eoan-proposed. The package will build now and be available at https://launchpad.net/ubuntu/+source/glib2.0/2.62.3-2~ubuntu19.10.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 and change the tag from verification-needed-eoan to verification-done-eoan. If it does not fix the bug for you, please add a comment stating that, and change the tag to verification-failed-eoan. 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. ** Tags removed: verification-done verification-done-eoan ** Tags added: verification-needed verification-needed-eoan -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to glib2.0 in Ubuntu. https://bugs.launchpad.net/bugs/1848202 Title: Use after free in gdbus leads to eds segfaults Status in GLib: Fix Released Status in glib2.0 package in Ubuntu: Fix Released Status in glib2.0 source package in Eoan: Fix Committed Bug description: [ Description ] The Ubuntu Error Tracker has been receiving reports about a problem regarding evolution-data-server. This problem was most recently seen with package version 3.34.1-1, the problem page at https://errors.ubuntu.com/problem/b1f62616406e36e521fd1fb1d2be4ac2fe9a2cda 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/. [ Fix ] This bug was fixed upstream in 2.62.2 (see the links below). That update is being issues to eoan. [ QA ] Under https://wiki.ubuntu.com/StableReleaseUpdates/GNOME, we don't need to explicitly test that this bug is fixed. Nevertheless, to verify this bug please give the desktop a good workout. Ideally install the SRU and use your machine as you would normally for a variety of tasks. Make sure there are no regressions. [ Regression potential ] 1) The changes involve mutexes and stuff, which is error prone. 2) It's GLib, a core library, so any bad regressions will be really serious for the desktop as a whole. To manage notifications about this bug go to: https://bugs.launchpad.net/glib/+bug/1848202/+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 1850932] Re: [SRU] Backport 2.62.3-2
Hello Iain, or anyone else affected, Accepted glib2.0 into eoan-proposed. The package will build now and be available at https://launchpad.net/ubuntu/+source/glib2.0/2.62.3-2~ubuntu19.10.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 and change the tag from verification-needed-eoan to verification-done-eoan. If it does not fix the bug for you, please add a comment stating that, and change the tag to verification-failed-eoan. 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. ** Tags added: verification-needed verification-needed-eoan -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to glib2.0 in Ubuntu. https://bugs.launchpad.net/bugs/1850932 Title: [SRU] Backport 2.62.3-2 Status in glib2.0 package in Ubuntu: Fix Released Status in glib2.0 source package in Eoan: Fix Committed Bug description: [ Description ] I'm creating this bug report to have a place to describe the proposed backport of glib2.0 2.62.3-2 from focal. One purpose of this backport is to fix bug #1844853. But there are several other changes. Here's the diff of NEWS: +Overview of changes in GLib 2.62.3 +== + +* Use `poll()` in `g_spawn_sync()` rather than `select()`, which is subject to + FD limits (#954) + +* Fix undefined behaviour with `g_utf8_find_prev_char()` (#1917) + +* Bugs fixed: + - #954 The g_spawn_sync() function uses select() which has limitations + - #1318 rare failure in gdbus-peer test: invalid uninstantiatable type '(null)' in cast to 'GDBusServer' + - #1897 glib 2.62.0 fails test 'test_writev_no_vectors' wih gcc7 + - #1903 use-after-free in mimeapps test causes intermittent segfault during testing + - #1916 objcopy not used from cross-compilation file in GIO tests + - #1917 Test utf8-pointer fails with static build, LTO, optimisations, and new GCC + - !1174 Backport !1164 “use-after-free fix in mimeapps test” to glib-2-62 + - !1184 Backport !1173 “gvariant: Limit recursion in g_variant_parse()” to glib-2-62 + - !1194 Backport !1176, !1183, !1188, !1191 to `glib-2-62` + - !1203 Backport !1192, !1193, !1197 Fixes for gdbus-peer tests to glib-2-62 + - !1207 Backport !1206 “goption: Relax assertion to avoid being broken by kdeinit5” to glib-2-62 + - !1215 [2.62] gdbus-peer: Specifically listen on 127.0.0.1 + - !1219 Backport !1218 “gdb: Fix GHashTable pretty printer off-by-one error” + - !1222 Backport !1221 “Add NOTE_REVOKE to the list of the monitoring events” to glib-2-62 + - !1228 Backport !1199 “gunicode: Fix UB in gutf8.c and utf8-pointer test” to glib-2-62 + + +Overview of changes in GLib 2.62.2 +== + +* Bugs fixed: + - #1896 Use after free when calling g_dbus_connection_flush_sync() in a dedicated thread + - !1154 Backport !1152 “gwinhttpvfs: Handle g_get_prgname() returning NULL” to glib-2-62 + - !1156 Backport !1146 Solaris fixes to glib-2-62 This release can be considered to be tested under https://wiki.ubuntu.com/StableReleaseUpdates/GNOME There are patches from the upstream master branch rather than this stable release: + Add-a-test-for-GDBusServer-authentication.patch + gdbus-server-auth-test-Create-temporary-directory-for-Uni.patch + gdbus-server-auth-test-Include-gcredentialsprivate.h.patch + Make-ld-executable-configurable.patch They are sensible backports which I hope are appropriate for SRU. [ QA ] The testsuite fixes will verify themselves during the build and autopkgtest. For the rest of the fixes, please exercise the desktop thoroughly. Log in, log out, run many applications and make sure there are no regressions. [ Regression potential ] test fixes> Build failures or autopkgtest failures. GLib is a central desktop library. Regressions could break any part of the desktop - so QA is important, the SRU exception notwithstanding. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/glib2.0/+bug/1850932/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More
[Touch-packages] [Bug 1858199] Re: bugs in libvdpau_radeonsi.so and amdgpu(or radeon) driver freeze the system
I have changed the system to centos7 ,the system is stable .I think It should not be a hardware problem. -- 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/1858199 Title: bugs in libvdpau_radeonsi.so and amdgpu(or radeon) driver freeze the system Status in mesa package in Ubuntu: New Bug description: 1. In 4.15 kernel serires ,vlc or mpv video player with hardware acceleration output will freeze the system in minutes ,the desktop screen display content was frozen ,but sometime the audio will continue to play for about 10 seconds to one miniute,then the system dead。I have to reset the machine to reboot. When upgrade to 5.3.24 kernel,amdgpu still hanged immediately,but play video through vdpau in radeon driver the system will no hang immediately,the freqency of hanging is about serveral times a day。 some times web browser in virtualbox guest randomly hangs the system。 2. installing amdgpu-pro driver download from amd official site (version of 18.40-697810,18.50-756341,19.10-785425,19.30-934563) are all the same problem with above. 3. remove libvdpau_radeonsi.so.1.0.0 in the system from ubuntu or installed in /opt/amdgpu by amdgpu-pro driver solved the problem . the system has never been freezing for several weeks ,but the problem happened again when I restore the libvdpau_radeonsi.so file。 4.When use amdgpu driver the vlc output sound via display output port (through an active hdmi adaptor to hdmi monitor) was glitches ,the sound seem missing or dropped in every 2~3 seconds，but when use radeon driver the sound was normal.the audio problem is the same with 4.15 kernel when using kernel 5.3.24. But mplayer sound is always good ,testing with audio output of pulseaduio and alsa ,the kernel driver only affected the sound of vlc (tested with all available audio output ),the other applications was normal. 5. Test with the ubuntu 19.10 live image desktop is the same problem。 6. My system have four monitors,graphics card is R7 360 ,recognized as (from lspci) : 6.02:00.0 VGA compatible controller: Advanced Micro Devices, Inc. [AMD/ATI] Cape Verde PRO [Radeon HD 7750/8740 / R7 250E]. infomation from uname -a : Linux smzhou-desktop 5.3.0-24-lowlatency #26~18.04.2-Ubuntu SMP PREEMPT Tue Nov 26 14:39:35 UTC 2019 x86_64 x86_64 x86_64 GNU/Linux To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mesa/+bug/1858199/+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 1859996] [NEW] pulseaudio-equalizer make pulseaudio's start fail
Public bug reported: After installing pulseaudio-equalizer package, Pulseaudio doesn't work anymore. Due to that, no device can be configured glad to KDE's sound widget: https://askubuntu.com/questions/976375/kubuntu-17-10-no-audio- devices-found-no-settings-no-sound sudo cat /var/log/syslog | grep pulseaudio [pulseaudio] module-equalizer-sink.c: module-equalizer-sink is currently unsupported, and can sometimes cause PulseAudio crashes, increased latency or audible artifacts. [pulseaudio] module-equalizer-sink.c: If you're facing audio problems, try unloading this module as a potential workaround. [pulseaudio] module-equalizer-sink.c: Master sink not found [pulseaudio] module.c: Failed to load module "module-equalizer-sink" (argument: ""): initialization failed. Also, "apt purge pulseaudio-equalizer" doesn't remove "load-module module-equalizer-sink" from the .config/pulse/default.pa so it continues to fail at start afterwards. sudo cat /var/log/syslog | grep pulseaudio [pulseaudio] ltdl-bind-now.c: Failed to open module module-equalizer-sink.so : module-equalizer-sink.so: cannot open shared object file: No such file or directory [pulseaudio] module.c: Failed to open module "module-equalizer-sink". NB: I cannot choose pulseaudio-equalizer as targeted package for this bug as it's not listed despite this: sudo apt search pulseaudio-equalizer pulseaudio-equalizer/eoan-updates 1:13.0-1ubuntu1.1 amd64 Equalizer sink module for PulseAudio sound server ** Affects: pulseaudio (Ubuntu) Importance: Undecided Status: New -- 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/1859996 Title: pulseaudio-equalizer make pulseaudio's start fail Status in pulseaudio package in Ubuntu: New Bug description: After installing pulseaudio-equalizer package, Pulseaudio doesn't work anymore. Due to that, no device can be configured glad to KDE's sound widget: https://askubuntu.com/questions/976375/kubuntu-17-10-no-audio- devices-found-no-settings-no-sound sudo cat /var/log/syslog | grep pulseaudio [pulseaudio] module-equalizer-sink.c: module-equalizer-sink is currently unsupported, and can sometimes cause PulseAudio crashes, increased latency or audible artifacts. [pulseaudio] module-equalizer-sink.c: If you're facing audio problems, try unloading this module as a potential workaround. [pulseaudio] module-equalizer-sink.c: Master sink not found [pulseaudio] module.c: Failed to load module "module-equalizer-sink" (argument: ""): initialization failed. Also, "apt purge pulseaudio-equalizer" doesn't remove "load-module module-equalizer-sink" from the .config/pulse/default.pa so it continues to fail at start afterwards. sudo cat /var/log/syslog | grep pulseaudio [pulseaudio] ltdl-bind-now.c: Failed to open module module-equalizer-sink.so : module-equalizer-sink.so: cannot open shared object file: No such file or directory [pulseaudio] module.c: Failed to open module "module-equalizer-sink". NB: I cannot choose pulseaudio-equalizer as targeted package for this bug as it's not listed despite this: sudo apt search pulseaudio-equalizer pulseaudio-equalizer/eoan-updates 1:13.0-1ubuntu1.1 amd64 Equalizer sink module for PulseAudio sound server To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1859996/+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 1850966] Re: Stuck at "Refreshing software cache" after enabling repository not updated for Eoan
How do I output all at once or in a file? It shows in pages -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to software-properties in Ubuntu. https://bugs.launchpad.net/bugs/1850966 Title: Stuck at "Refreshing software cache" after enabling repository not updated for Eoan Status in software-properties package in Ubuntu: Incomplete Bug description: Steps to reproduce: 1. Open Software and Updates 2. Go to "other software" and enable, for example, a repository disabled during upgrade to Eoan which is not updated for Eoan yet 3. Press close and then reload on the dialog that opens. 4. Refreshing software cache dialog is stuck After closing the dialogs by right clicking on the windows and the open apps bar, re opening Software and updates only shows a white square you can't interact with. Ubuntu 19.10 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/software-properties/+bug/1850966/+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 1850966] Re: Stuck at "Refreshing software cache" after enabling repository not updated for Eoan
Never mind I got it. ** Attachment added: "systemctl log" https://bugs.launchpad.net/ubuntu/+source/software-properties/+bug/1850966/+attachment/5320861/+files/1850966.txt -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to software-properties in Ubuntu. https://bugs.launchpad.net/bugs/1850966 Title: Stuck at "Refreshing software cache" after enabling repository not updated for Eoan Status in software-properties package in Ubuntu: Incomplete Bug description: Steps to reproduce: 1. Open Software and Updates 2. Go to "other software" and enable, for example, a repository disabled during upgrade to Eoan which is not updated for Eoan yet 3. Press close and then reload on the dialog that opens. 4. Refreshing software cache dialog is stuck After closing the dialogs by right clicking on the windows and the open apps bar, re opening Software and updates only shows a white square you can't interact with. Ubuntu 19.10 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/software-properties/+bug/1850966/+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 1854314] Re: Legacy directory /var/run in /lib/systemd/system/dbus.socket
** Changed in: dbus (Ubuntu) Importance: Undecided => Low ** Changed in: dbus (Ubuntu) Status: New => Fix Committed -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to dbus in Ubuntu. https://bugs.launchpad.net/bugs/1854314 Title: Legacy directory /var/run in /lib/systemd/system/dbus.socket Status in D-Bus: New Status in dbus package in Ubuntu: Fix Committed Status in dbus package in Debian: Fix Committed Bug description: dbus/focal-proposed,now 1.12.16-2ubuntu1 amd64 Re(o)curring after each new upgrade of dbus, for quite some time and still... $ dmesg|grep accordingly systemd[1]: /lib/systemd/system/dbus.socket:5: ListenStream= references a path below legacy directory /var/run/, updating /var/run/dbus/system_bus_socket → /run/dbus/system_bus_socket; please update the unit file accordingly. Originally: $cat /lib/systemd/system/dbus.socket [Unit] Description=D-Bus System Message Bus Socket [Socket] ListenStream=/var/run/dbus/system_bus_socket After change: $cat /lib/systemd/system/dbus.socket [Unit] Description=D-Bus System Message Bus Socket [Socket] ListenStream=/run/dbus/system_bus_socket To manage notifications about this bug go to: https://bugs.launchpad.net/dbus/+bug/1854314/+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 1859857] Re: network-manager keeps asking for wifi password can't connect to any wifi
Thank you for your bug report. From what version to what version did you update? What desktop do you use? Could you add your 'journalctl -b 0' log from a session where you reproduced the issue? ** Changed in: network-manager (Ubuntu) Status: New => Incomplete -- 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/1859857 Title: network-manager keeps asking for wifi password can't connect to any wifi Status in network-manager package in Ubuntu: Incomplete Bug description: This bug is the same as reported by #1859289, however I was not able to find this when using the ubuntu-bug tool. Since the last update my network-manager keeps asking me for wifi passworts, but then never connects. Password is definitely correct. Everything worked before the update. lsb_release -rd Description:Ubuntu 19.10 Release:19.10 ProblemType: Bug DistroRelease: Ubuntu 19.10 Package: network-manager 1.20.4-2ubuntu2 ProcVersionSignature: Ubuntu 5.3.0-23.25-generic 5.3.7 Uname: Linux 5.3.0-23-generic x86_64 ApportVersion: 2.20.11-0ubuntu8.2 Architecture: amd64 Date: Wed Jan 15 19:12:42 2020 IfupdownConfig: # interfaces(5) file used by ifup(8) and ifdown(8) auto lo iface lo inet loopback InstallationDate: Installed on 2019-05-27 (233 days ago) InstallationMedia: Kubuntu 19.04 "Disco Dingo" - Release amd64 (20190416) IpRoute: default via 192.168.1.1 dev enp0s25 proto dhcp metric 100 169.254.0.0/16 dev enp0s25 scope link metric 1000 192.168.1.0/24 dev enp0s25 proto kernel scope link src 192.168.1.23 metric 100 NetworkManager.state: [main] NetworkingEnabled=true WirelessEnabled=true WWANEnabled=false ProcEnviron: LANGUAGE= TERM=xterm-256color PATH=(custom, no user) LANG=de_DE.UTF-8 SHELL=/bin/bash SourcePackage: network-manager UpgradeStatus: Upgraded to eoan on 2019-10-23 (83 days ago) nmcli-nm: RUNNING VERSION STATE STARTUP CONNECTIVITY NETWORKING WIFI-HW WIFI WWAN-HW WWAN running 1.20.4 connected started full enabled enabled enabled enabled disabled To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1859857/+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 1850966] Re: Stuck at "Refreshing software cache" after enabling repository not updated for Eoan
Thank you for your bug report, could you add your 'journalctl -b 0' log after getting the issue? ** Changed in: software-properties (Ubuntu) Importance: Undecided => Low ** Changed in: software-properties (Ubuntu) Status: Confirmed => Incomplete -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to software-properties in Ubuntu. https://bugs.launchpad.net/bugs/1850966 Title: Stuck at "Refreshing software cache" after enabling repository not updated for Eoan Status in software-properties package in Ubuntu: Incomplete Bug description: Steps to reproduce: 1. Open Software and Updates 2. Go to "other software" and enable, for example, a repository disabled during upgrade to Eoan which is not updated for Eoan yet 3. Press close and then reload on the dialog that opens. 4. Refreshing software cache dialog is stuck After closing the dialogs by right clicking on the windows and the open apps bar, re opening Software and updates only shows a white square you can't interact with. Ubuntu 19.10 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/software-properties/+bug/1850966/+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 1850966] Re: Stuck at "Refreshing software cache" after enabling repository not updated for Eoan
Any update on this? I just upgraded to Ubuntu 19.10 and I see the same issue! -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to software-properties in Ubuntu. https://bugs.launchpad.net/bugs/1850966 Title: Stuck at "Refreshing software cache" after enabling repository not updated for Eoan Status in software-properties package in Ubuntu: Confirmed Bug description: Steps to reproduce: 1. Open Software and Updates 2. Go to "other software" and enable, for example, a repository disabled during upgrade to Eoan which is not updated for Eoan yet 3. Press close and then reload on the dialog that opens. 4. Refreshing software cache dialog is stuck After closing the dialogs by right clicking on the windows and the open apps bar, re opening Software and updates only shows a white square you can't interact with. Ubuntu 19.10 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/software-properties/+bug/1850966/+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 1858971] Re: SECLEVEL=2 & tls1.2-min by default are causing ftbfs / autopkgtest failures
** Changed in: python3.7 (Ubuntu) Status: New => Fix Committed ** Changed in: python2.7 (Ubuntu) Status: New => Fix Committed ** Also affects: cmake (Ubuntu) Importance: Undecided Status: New ** Changed in: cmake (Ubuntu) Status: New => Fix Committed -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to openssl in Ubuntu. https://bugs.launchpad.net/bugs/1858971 Title: SECLEVEL=2 & tls1.2-min by default are causing ftbfs / autopkgtest failures Status in cmake package in Ubuntu: Fix Committed Status in nodejs package in Ubuntu: Fix Committed Status in openssl package in Ubuntu: New Status in python2.7 package in Ubuntu: Fix Committed Status in python3.7 package in Ubuntu: Fix Committed Status in python3.8 package in Ubuntu: Fix Committed Status in ruby-openssl package in Ubuntu: Fix Committed Status in ruby2.5 package in Ubuntu: Fix Committed Bug description: SECLEVEL=2 by default is causing ftbfs / autopkgtest failure openssl switched to SECLEVEL=2 by default Causes: SSL_CTX_use_certificate: ca md too weak in ruby2.5 ruby-openssl openssl uses tls1.2-min: test_ssl failing in python2.7 ERROR: test_protocol_sslv23 (test.test_ssl.ThreadedTests) Connecting to an SSLv23 server with various client options ERROR: test_protocol_tlsv1_1 (test.test_ssl.ThreadedTests) Connecting to a TLSv1.1 server with various client options. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/cmake/+bug/1858971/+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 1859972] [NEW] UFW doesn't support SCTP
Public bug reported: It appears that UFW only supports UDP and TCP while I have a need to also manage SCTP ports. As iptables supports SCTP, I have understood that I can edit the rules by myself under /etc/ufw/, but it would be easier and less error-prone if UFW supported SCTP directly like TCP and UDP. I have also heard of DDCP together with SCTP and while I don't think I will need to touch it, I wonder could UFW support everything that iptables does and if iptables refuses something, could UFW then refuse it too? (Sorry about asking two things in one bug report.) I originally asked about SCTP in https://answers.launchpad.net/ubuntu/+source/ufw/+question/688017 and I am not sure how to transfer it into a question. ** Affects: ufw (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to ufw in Ubuntu. https://bugs.launchpad.net/bugs/1859972 Title: UFW doesn't support SCTP Status in ufw package in Ubuntu: New Bug description: It appears that UFW only supports UDP and TCP while I have a need to also manage SCTP ports. As iptables supports SCTP, I have understood that I can edit the rules by myself under /etc/ufw/, but it would be easier and less error-prone if UFW supported SCTP directly like TCP and UDP. I have also heard of DDCP together with SCTP and while I don't think I will need to touch it, I wonder could UFW support everything that iptables does and if iptables refuses something, could UFW then refuse it too? (Sorry about asking two things in one bug report.) I originally asked about SCTP in https://answers.launchpad.net/ubuntu/+source/ufw/+question/688017 and I am not sure how to transfer it into a question. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ufw/+bug/1859972/+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 1022858] Re: Guest session asks for a password after switching users
Guess what? Affects Xubuntu 19.10. What is so difficult in not asking password when guest session is concerned? -- 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/1022858 Title: Guest session asks for a password after switching users Status in lightdm package in Ubuntu: Confirmed Bug description: When I switch back to an already open guest session from my user account, I find that the guest session is locked and it asks for the Guest password (which obviously there isn't because it's a guest session!). ProblemType: Bug DistroRelease: Ubuntu 12.04 Package: gnome-session-bin 3.2.1-0ubuntu8 ProcVersionSignature: Ubuntu 3.2.0-26.41-generic 3.2.19 Uname: Linux 3.2.0-26-generic x86_64 ApportVersion: 2.0.1-0ubuntu8 Architecture: amd64 Date: Tue Jul 10 09:54:55 2012 ExecutablePath: /usr/bin/gnome-session InstallationMedia: Ubuntu 12.04 LTS "Precise Pangolin" - Release amd64 (20120425) ProcEnviron: LANGUAGE=en_GB:en PATH=(custom, no user) LANG=en_GB.UTF-8 SHELL=/bin/bash SourcePackage: gnome-session UpgradeStatus: No upgrade log present (probably fresh install) XsessionErrors: (compiz:1719): GConf-CRITICAL **: gconf_client_add_dir: assertion `gconf_valid_key (dirname, NULL)' failed --- ApportVersion: 2.0.1-0ubuntu17.1 Architecture: amd64 DistroRelease: Ubuntu 12.04 InstallationMedia: Ubuntu 12.04.1 LTS "Precise Pangolin" - Release amd64 (20120823.1) MarkForUpload: True Package: lightdm 1.2.1-0ubuntu1.1 PackageArchitecture: amd64 ProcVersionSignature: Ubuntu 3.2.0-36.57-generic 3.2.35 Tags: precise running-unity Uname: Linux 3.2.0-36-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dialout dip lpadmin plugdev sambashare sudo To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/lightdm/+bug/1022858/+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 1859952] Re: apt 1.9.6 regression
Fixed in 1.9.7, will sync later. ** Changed in: apt (Ubuntu) Status: In Progress => Fix Committed -- 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/1859952 Title: apt 1.9.6 regression Status in apt package in Ubuntu: Fix Committed Bug description: APT 1.9.6 introduced empty groups by making use of groups to deduplicate package names. This caused a problem in NewProvidesAllArch because automake was providing automake-1.16 while having the source package automake-1.16. So we found the automake-1.16 group, iterated over its empty package list, trying to store the provides (which hence never happened). To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apt/+bug/1859952/+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 1845317] Re: Add new pci-id's for CML-S, ICL
This bug was fixed in the package libdrm - 2.4.99-1ubuntu1~18.04.1 --- libdrm (2.4.99-1ubuntu1~18.04.1) bionic; urgency=medium * Backport to bionic for 18.04.4 HWE stack update. (LP: #1848522) libdrm (2.4.99-1ubuntu1) eoan; urgency=medium * intel-sync-pciids.diff: Sync pci-ids with the kernel. (LP: #1845317) -- Timo Aaltonen Mon, 21 Oct 2019 17:02:40 +0300 ** Changed in: libdrm (Ubuntu Bionic) Status: Fix Committed => Fix Released -- 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/1845317 Title: Add new pci-id's for CML-S, ICL Status in libdrm package in Ubuntu: Fix Released Status in linux package in Ubuntu: Fix Released Status in linux-oem-osp1 package in Ubuntu: Fix Released Status in mesa package in Ubuntu: Fix Released Status in libdrm source package in Bionic: Fix Released Status in linux source package in Bionic: Won't Fix Status in linux-oem-osp1 source package in Bionic: Fix Released Status in mesa source package in Bionic: Fix Released Bug description: [Impact] Comet Lake (CML) is basically same gen9 GPU as Sky Lake (SKL) (as is KBL, CFL, WHL). There are new CML-S desktop cpu's on the way, and they add three new pci-id's that need to be added across the stack in order to use the GPU properly. There's also one ICL pci-id which was added recently (not in 5.3). [Test case] The proper way to test is to have an actual machine and boot it up with the updated stack, but since these are just pci-id's with no regression potential on older hw, it should be fine to just accept them. [Regression potential] None, just adds new pci-id's to allow the new GPUs to load the proper drivers. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libdrm/+bug/1845317/+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 1848522] Re: Backport packages for 18.04.4 HWE stack
This bug was fixed in the package mesa - 19.2.1-1ubuntu1~18.04.1 --- mesa (19.2.1-1ubuntu1~18.04.1) bionic; urgency=medium * Backport to bionic for 18.04.4 HWE stack update. (LP: #1848522) * control: Build-depend on libsensors4-dev. * Disable vulkan overlay layer, needs meson 0.46. * rules: Force -DNDEBUG, meson < 0.47 is buggy and doesn't set it even if we have b_ndebug=true. (LP: 1841412) * Revert-meson-drop-Wno-foo-bug-workaround.diff: Bionic still has 0.45, so add back a workaround for it. * Revert-meson-bump-required-version-to-0.46.diff: Relax meson requirement. -- Timo Aaltonen Mon, 18 Nov 2019 20:28:40 +0200 ** Changed in: xorg-server-hwe-18.04 (Ubuntu Bionic) Status: Fix Committed => Fix Released -- 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/1848522 Title: Backport packages for 18.04.4 HWE stack Status in libclc package in Ubuntu: Invalid Status in libdrm package in Ubuntu: Invalid Status in llvm-toolchain-9 package in Ubuntu: Invalid Status in mesa package in Ubuntu: Invalid Status in xorg-server-hwe-18.04 package in Ubuntu: Invalid Status in libclc source package in Bionic: Fix Released Status in libdrm source package in Bionic: Fix Released Status in llvm-toolchain-9 source package in Bionic: Fix Released Status in mesa source package in Bionic: Fix Released Status in xorg-server-hwe-18.04 source package in Bionic: Fix Released Bug description: [Impact] These are needed for 18.04.4 images. [Test case] Boot a daily image, see that it still has the necessary stack installed and working. Check upgrade from stock bionic. [Regression potential] libdrm: very minimal chance for regressions llvm-9: a new package, no regression potential on it's own libclc: more or less just adds support for new llvm mesa: a new major release, but we'll pull the final stable release of 19.2.x series, so there shouldn't be any regressions left at that point xserver: a new git snapshot (or maybe a point-release) xorg drivers: modest updates, mainly just new ati/amdgpu [Other info] To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libclc/+bug/1848522/+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 1848522] Update Released
The verification of the Stable Release Update for mesa 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 mesa in Ubuntu. https://bugs.launchpad.net/bugs/1848522 Title: Backport packages for 18.04.4 HWE stack Status in libclc package in Ubuntu: Invalid Status in libdrm package in Ubuntu: Invalid Status in llvm-toolchain-9 package in Ubuntu: Invalid Status in mesa package in Ubuntu: Invalid Status in xorg-server-hwe-18.04 package in Ubuntu: Invalid Status in libclc source package in Bionic: Fix Released Status in libdrm source package in Bionic: Fix Released Status in llvm-toolchain-9 source package in Bionic: Fix Released Status in mesa source package in Bionic: Fix Released Status in xorg-server-hwe-18.04 source package in Bionic: Fix Released Bug description: [Impact] These are needed for 18.04.4 images. [Test case] Boot a daily image, see that it still has the necessary stack installed and working. Check upgrade from stock bionic. [Regression potential] libdrm: very minimal chance for regressions llvm-9: a new package, no regression potential on it's own libclc: more or less just adds support for new llvm mesa: a new major release, but we'll pull the final stable release of 19.2.x series, so there shouldn't be any regressions left at that point xserver: a new git snapshot (or maybe a point-release) xorg drivers: modest updates, mainly just new ati/amdgpu [Other info] To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libclc/+bug/1848522/+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 1848522] Re: Backport packages for 18.04.4 HWE stack
This bug was fixed in the package libclc - 0.2.0+git20190827-1~ubuntu18.04.1 --- libclc (0.2.0+git20190827-1~ubuntu18.04.1) bionic; urgency=medium * Backport to bionic for 18.04.4 HWE stack update. (LP: #1848522) -- Timo Aaltonen Mon, 21 Oct 2019 23:59:47 +0300 ** Changed in: mesa (Ubuntu Bionic) Status: Fix Committed => Fix Released -- 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/1848522 Title: Backport packages for 18.04.4 HWE stack Status in libclc package in Ubuntu: Invalid Status in libdrm package in Ubuntu: Invalid Status in llvm-toolchain-9 package in Ubuntu: Invalid Status in mesa package in Ubuntu: Invalid Status in xorg-server-hwe-18.04 package in Ubuntu: Invalid Status in libclc source package in Bionic: Fix Released Status in libdrm source package in Bionic: Fix Released Status in llvm-toolchain-9 source package in Bionic: Fix Released Status in mesa source package in Bionic: Fix Released Status in xorg-server-hwe-18.04 source package in Bionic: Fix Released Bug description: [Impact] These are needed for 18.04.4 images. [Test case] Boot a daily image, see that it still has the necessary stack installed and working. Check upgrade from stock bionic. [Regression potential] libdrm: very minimal chance for regressions llvm-9: a new package, no regression potential on it's own libclc: more or less just adds support for new llvm mesa: a new major release, but we'll pull the final stable release of 19.2.x series, so there shouldn't be any regressions left at that point xserver: a new git snapshot (or maybe a point-release) xorg drivers: modest updates, mainly just new ati/amdgpu [Other info] To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libclc/+bug/1848522/+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 1848522] Re: Backport packages for 18.04.4 HWE stack
This bug was fixed in the package llvm-toolchain-9 - 1:9-2~ubuntu18.04.1 --- llvm-toolchain-9 (1:9-2~ubuntu18.04.1) bionic; urgency=medium * Backport to bionic for 18.04.4 HWE stack update. (LP: #1848522) -- Timo Aaltonen Mon, 21 Oct 2019 17:13:41 +0300 ** Changed in: libclc (Ubuntu Bionic) Status: Fix Committed => Fix Released -- 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/1848522 Title: Backport packages for 18.04.4 HWE stack Status in libclc package in Ubuntu: Invalid Status in libdrm package in Ubuntu: Invalid Status in llvm-toolchain-9 package in Ubuntu: Invalid Status in mesa package in Ubuntu: Invalid Status in xorg-server-hwe-18.04 package in Ubuntu: Invalid Status in libclc source package in Bionic: Fix Released Status in libdrm source package in Bionic: Fix Released Status in llvm-toolchain-9 source package in Bionic: Fix Released Status in mesa source package in Bionic: Fix Released Status in xorg-server-hwe-18.04 source package in Bionic: Fix Released Bug description: [Impact] These are needed for 18.04.4 images. [Test case] Boot a daily image, see that it still has the necessary stack installed and working. Check upgrade from stock bionic. [Regression potential] libdrm: very minimal chance for regressions llvm-9: a new package, no regression potential on it's own libclc: more or less just adds support for new llvm mesa: a new major release, but we'll pull the final stable release of 19.2.x series, so there shouldn't be any regressions left at that point xserver: a new git snapshot (or maybe a point-release) xorg drivers: modest updates, mainly just new ati/amdgpu [Other info] To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libclc/+bug/1848522/+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 1848522] Re: Backport packages for 18.04.4 HWE stack
This bug was fixed in the package xorg-server-hwe-18.04 - 2:1.20.5+git20191008-0ubuntu1~18.04.1 --- xorg-server-hwe-18.04 (2:1.20.5+git20191008-0ubuntu1~18.04.1) bionic; urgency=medium * Backport for 18.04.4 HWE stack update. (LP: #1848522) -- Timo Aaltonen Wed, 18 Dec 2019 10:15:29 +0200 -- 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/1848522 Title: Backport packages for 18.04.4 HWE stack Status in libclc package in Ubuntu: Invalid Status in libdrm package in Ubuntu: Invalid Status in llvm-toolchain-9 package in Ubuntu: Invalid Status in mesa package in Ubuntu: Invalid Status in xorg-server-hwe-18.04 package in Ubuntu: Invalid Status in libclc source package in Bionic: Fix Released Status in libdrm source package in Bionic: Fix Released Status in llvm-toolchain-9 source package in Bionic: Fix Released Status in mesa source package in Bionic: Fix Released Status in xorg-server-hwe-18.04 source package in Bionic: Fix Released Bug description: [Impact] These are needed for 18.04.4 images. [Test case] Boot a daily image, see that it still has the necessary stack installed and working. Check upgrade from stock bionic. [Regression potential] libdrm: very minimal chance for regressions llvm-9: a new package, no regression potential on it's own libclc: more or less just adds support for new llvm mesa: a new major release, but we'll pull the final stable release of 19.2.x series, so there shouldn't be any regressions left at that point xserver: a new git snapshot (or maybe a point-release) xorg drivers: modest updates, mainly just new ati/amdgpu [Other info] To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libclc/+bug/1848522/+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 1848522] Re: Backport packages for 18.04.4 HWE stack
This bug was fixed in the package libdrm - 2.4.99-1ubuntu1~18.04.1 --- libdrm (2.4.99-1ubuntu1~18.04.1) bionic; urgency=medium * Backport to bionic for 18.04.4 HWE stack update. (LP: #1848522) libdrm (2.4.99-1ubuntu1) eoan; urgency=medium * intel-sync-pciids.diff: Sync pci-ids with the kernel. (LP: #1845317) -- Timo Aaltonen Mon, 21 Oct 2019 17:02:40 +0300 ** Changed in: libdrm (Ubuntu Bionic) Status: Fix Committed => Fix Released ** Changed in: llvm-toolchain-9 (Ubuntu Bionic) Status: Fix Committed => Fix Released -- 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/1848522 Title: Backport packages for 18.04.4 HWE stack Status in libclc package in Ubuntu: Invalid Status in libdrm package in Ubuntu: Invalid Status in llvm-toolchain-9 package in Ubuntu: Invalid Status in mesa package in Ubuntu: Invalid Status in xorg-server-hwe-18.04 package in Ubuntu: Invalid Status in libclc source package in Bionic: Fix Released Status in libdrm source package in Bionic: Fix Released Status in llvm-toolchain-9 source package in Bionic: Fix Released Status in mesa source package in Bionic: Fix Released Status in xorg-server-hwe-18.04 source package in Bionic: Fix Released Bug description: [Impact] These are needed for 18.04.4 images. [Test case] Boot a daily image, see that it still has the necessary stack installed and working. Check upgrade from stock bionic. [Regression potential] libdrm: very minimal chance for regressions llvm-9: a new package, no regression potential on it's own libclc: more or less just adds support for new llvm mesa: a new major release, but we'll pull the final stable release of 19.2.x series, so there shouldn't be any regressions left at that point xserver: a new git snapshot (or maybe a point-release) xorg drivers: modest updates, mainly just new ati/amdgpu [Other info] To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libclc/+bug/1848522/+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 1859404] Re: binutils regressed llvm-toolchain-9 and llvm-toolchain-7 bootstrap on arm64
** Changed in: binutils (Debian) Status: New => Fix Released -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to binutils in Ubuntu. https://bugs.launchpad.net/bugs/1859404 Title: binutils regressed llvm-toolchain-9 and llvm-toolchain-7 bootstrap on arm64 Status in binutils package in Ubuntu: Fix Released Status in binutils package in Debian: Fix Released Bug description: Retrying builds on bileto with the release only pocket enabled worked correctly. Still trying to figure out what can have regressed it (Debian doesn't show the issue, but probably it is affected on the same way, just his CPUs can understand the new instructions? To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/binutils/+bug/1859404/+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 1845529] Re: bash completion shows `awk: line 18: function gensub never defined` on `umount /dev/`
This bug was fixed in the package util-linux - 2.34-0.1ubuntu2.1 --- util-linux (2.34-0.1ubuntu2.1) eoan; urgency=medium * bash-completion/umount: fix completion to not require gawk be present. Thanks to Étienne Mollier for the patch. (LP: #1845529) -- Mathieu Trudel-Lapierre Wed, 11 Dec 2019 14:47:41 -0500 ** Changed in: util-linux (Ubuntu Eoan) 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/1845529 Title: bash completion shows `awk: line 18: function gensub never defined` on `umount /dev/` Status in bash-completion package in Ubuntu: Invalid Status in ubuntu-meta package in Ubuntu: Invalid Status in util-linux package in Ubuntu: Fix Released Status in bash-completion source package in Eoan: Invalid Status in gawk source package in Eoan: Invalid Status in mawk source package in Eoan: Invalid Status in ubuntu-meta source package in Eoan: Invalid Status in util-linux source package in Eoan: Fix Released Status in bash-completion source package in Focal: Invalid Status in gawk source package in Focal: Invalid Status in mawk source package in Focal: Invalid Status in ubuntu-meta source package in Focal: Invalid Status in util-linux source package in Focal: Fix Released Status in Debian: Confirmed Bug description: [Impact] Any user attempting to tab-complete from "umount /dev/" when running the bash shell. [Test cases] Steps to reproduce: 1. Install Ubuntu MATE 19.10 using minimal desktop option 2. Open terminal and enter `umount /dev/s` and then hit Expected result: * bash completion works as expected Actual results: * bash completion does not work : $ umount /dev/awk: line 18: function gensub never defined awk: line 18: function gensub never defined awk: line 18: function gensub never defined awk: line 18: function gensub never defined $ umount /meawk: line 18: function gensub never defined awk: line 18: function gensub never defined awk: line 18: function gensub never defined awk: line 18: function gensub never defined [Regression potential] Since it is limited to a single file (/usr/share/bash-completion/completions/umount) and affects only it, as well as given that it currently does not work, I estimate this as a low risk change. Things to look out for as a regression would be if another previously-working completion would fail to work (ie. what if mount stops completing correctly, and works again if the fix is backed out?). --- ProblemType: Bug DistroRelease: Ubuntu 19.10 Package: bash-completion 1:2.9-1ubuntu1 ProcVersionSignature: Ubuntu 5.3.0-10.11-generic 5.3.0-rc8 Uname: Linux 5.3.0-10-generic x86_64 ApportVersion: 2.20.11-0ubuntu7 Architecture: amd64 CurrentDesktop: MATE Date: Thu Sep 26 18:46:59 2019 Dependencies: InstallationDate: Installed on 2019-09-26 (0 days ago) InstallationMedia: Ubuntu-MATE 19.10 "Eoan Ermine" - Beta amd64 (20190926.1) PackageArchitecture: all SourcePackage: bash-completion UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bash-completion/+bug/1845529/+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 1845529] Update Released
The verification of the Stable Release Update for util-linux 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/1845529 Title: bash completion shows `awk: line 18: function gensub never defined` on `umount /dev/` Status in bash-completion package in Ubuntu: Invalid Status in ubuntu-meta package in Ubuntu: Invalid Status in util-linux package in Ubuntu: Fix Released Status in bash-completion source package in Eoan: Invalid Status in gawk source package in Eoan: Invalid Status in mawk source package in Eoan: Invalid Status in ubuntu-meta source package in Eoan: Invalid Status in util-linux source package in Eoan: Fix Released Status in bash-completion source package in Focal: Invalid Status in gawk source package in Focal: Invalid Status in mawk source package in Focal: Invalid Status in ubuntu-meta source package in Focal: Invalid Status in util-linux source package in Focal: Fix Released Status in Debian: Confirmed Bug description: [Impact] Any user attempting to tab-complete from "umount /dev/" when running the bash shell. [Test cases] Steps to reproduce: 1. Install Ubuntu MATE 19.10 using minimal desktop option 2. Open terminal and enter `umount /dev/s` and then hit Expected result: * bash completion works as expected Actual results: * bash completion does not work : $ umount /dev/awk: line 18: function gensub never defined awk: line 18: function gensub never defined awk: line 18: function gensub never defined awk: line 18: function gensub never defined $ umount /meawk: line 18: function gensub never defined awk: line 18: function gensub never defined awk: line 18: function gensub never defined awk: line 18: function gensub never defined [Regression potential] Since it is limited to a single file (/usr/share/bash-completion/completions/umount) and affects only it, as well as given that it currently does not work, I estimate this as a low risk change. Things to look out for as a regression would be if another previously-working completion would fail to work (ie. what if mount stops completing correctly, and works again if the fix is backed out?). --- ProblemType: Bug DistroRelease: Ubuntu 19.10 Package: bash-completion 1:2.9-1ubuntu1 ProcVersionSignature: Ubuntu 5.3.0-10.11-generic 5.3.0-rc8 Uname: Linux 5.3.0-10-generic x86_64 ApportVersion: 2.20.11-0ubuntu7 Architecture: amd64 CurrentDesktop: MATE Date: Thu Sep 26 18:46:59 2019 Dependencies: InstallationDate: Installed on 2019-09-26 (0 days ago) InstallationMedia: Ubuntu-MATE 19.10 "Eoan Ermine" - Beta amd64 (20190926.1) PackageArchitecture: all SourcePackage: bash-completion UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bash-completion/+bug/1845529/+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 1856428] Re: Disable TLS below 1.2 by default
** Changed in: gnutls28 (Ubuntu) Status: Fix Committed => Fix Released -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to nss in Ubuntu. https://bugs.launchpad.net/bugs/1856428 Title: Disable TLS below 1.2 by default Status in gnutls28 package in Ubuntu: Fix Released Status in golang-1.13 package in Ubuntu: New Status in nss package in Ubuntu: Fix Released Status in openssl package in Ubuntu: Fix Committed Bug description: Disable TLS 1.0, TLS1.1, DTLS1.0 As part of focal commitment, we shall disable obsolete protocols by default. Users can override this behaviour with a config file. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnutls28/+bug/1856428/+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 1847570] Update Released
The verification of the Stable Release Update for pulseaudio 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 pulseaudio in Ubuntu. https://bugs.launchpad.net/bugs/1847570 Title: PulseAudio automatically switches to HDMI sound output on login Status in PulseAudio: Fix Released Status in pulseaudio package in Ubuntu: Fix Released Status in pulseaudio source package in Eoan: Fix Released Status in pulseaudio source package in Focal: Fix Released Bug description: [Impact] On my freshly installed eoan system I have two output devices: - HDMI/DisplayPort 2 - GK208 ... - Line Out - Family 17h ... When I login into the system pulseaudio always select the "wrong" one (HDMI) and I need to go to gnome-settings/Sound/Output Device and switch to "line out". This applies to every login/logout not just reboots. [Test Case] 0. Plug in a monitor that supports HDMI audio (one that appears in your Settings>Sound) 1. Log out and in again. Verify the default audio device in Settings is still speakers or headphones. Not the monitor's HDMI audio device. [Regression Potential] The behaviour is changed back to what it was before 19.10, some users might find it inconvenient and prefer the auto switch but the feedback we got shows it's unreliable and an annoying for the majority of our users so we will got back to default to safest behaviour. The fix proposed just reverts to the same code used in PulseAudio 12 and earlier. It has also been released and verified on focal already. [Workaround] Comment out: load-module module-switch-on-port-available load-module module-switch-on-connect from /etc/pulse/default.pa To manage notifications about this bug go to: https://bugs.launchpad.net/pulseaudio/+bug/1847570/+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 1847570] Re: PulseAudio automatically switches to HDMI sound output on login
This bug was fixed in the package pulseaudio - 1:13.0-1ubuntu1.1 --- pulseaudio (1:13.0-1ubuntu1.1) eoan; urgency=medium * Add 0031-lp1847570-Revert-switch-on-connect-Do-not-ignore-HDMI-sinks.patch to revert to PulseAudio v12 behaviour and ignore monitors with HDMI ports. At least until a proper solution arrives in PulseAudio v14. (LP: #1847570) -- Daniel van Vugt Wed, 18 Dec 2019 13:26:53 +0800 ** Changed in: pulseaudio (Ubuntu Eoan) Status: Fix Committed => Fix Released -- 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/1847570 Title: PulseAudio automatically switches to HDMI sound output on login Status in PulseAudio: Fix Released Status in pulseaudio package in Ubuntu: Fix Released Status in pulseaudio source package in Eoan: Fix Released Status in pulseaudio source package in Focal: Fix Released Bug description: [Impact] On my freshly installed eoan system I have two output devices: - HDMI/DisplayPort 2 - GK208 ... - Line Out - Family 17h ... When I login into the system pulseaudio always select the "wrong" one (HDMI) and I need to go to gnome-settings/Sound/Output Device and switch to "line out". This applies to every login/logout not just reboots. [Test Case] 0. Plug in a monitor that supports HDMI audio (one that appears in your Settings>Sound) 1. Log out and in again. Verify the default audio device in Settings is still speakers or headphones. Not the monitor's HDMI audio device. [Regression Potential] The behaviour is changed back to what it was before 19.10, some users might find it inconvenient and prefer the auto switch but the feedback we got shows it's unreliable and an annoying for the majority of our users so we will got back to default to safest behaviour. The fix proposed just reverts to the same code used in PulseAudio 12 and earlier. It has also been released and verified on focal already. [Workaround] Comment out: load-module module-switch-on-port-available load-module module-switch-on-connect from /etc/pulse/default.pa To manage notifications about this bug go to: https://bugs.launchpad.net/pulseaudio/+bug/1847570/+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 1859952] [NEW] apt 1.9.6 regression
Public bug reported: APT 1.9.6 introduced empty groups by making use of groups to deduplicate package names. This caused a problem in NewProvidesAllArch because automake was providing automake-1.16 while having the source package automake-1.16. So we found the automake-1.16 group, iterated over its empty package list, trying to store the provides (which hence never happened). ** Affects: apt (Ubuntu) Importance: Critical Assignee: Julian Andres Klode (juliank) Status: In Progress ** Tags: block-proposed ** Changed in: apt (Ubuntu) Assignee: (unassigned) => Julian Andres Klode (juliank) -- 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/1859952 Title: apt 1.9.6 regression Status in apt package in Ubuntu: In Progress Bug description: APT 1.9.6 introduced empty groups by making use of groups to deduplicate package names. This caused a problem in NewProvidesAllArch because automake was providing automake-1.16 while having the source package automake-1.16. So we found the automake-1.16 group, iterated over its empty package list, trying to store the provides (which hence never happened). To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apt/+bug/1859952/+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 1762391] Re: pam_group.so is not evaluated by gnome-terminal
SRU proposal for focal. Upstream regression has been resolved and the fix is integrated in the patch. ** No longer affects: gnome-terminal (Ubuntu Eoan) ** Patch removed: "focal_systemd_244-3ubuntu4.debdiff" https://bugs.launchpad.net/systemd/+bug/1762391/+attachment/5320077/+files/focal_systemd_244-3ubuntu4.debdiff ** Patch added: "focal_systemd_244-3ubuntu4.debdiff" https://bugs.launchpad.net/systemd/+bug/1762391/+attachment/5320810/+files/focal_systemd_244-3ubuntu4.debdiff -- 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/1762391 Title: pam_group.so is not evaluated by gnome-terminal Status in systemd: New Status in systemd package in Ubuntu: In Progress Status in systemd source package in Xenial: New Status in systemd source package in Bionic: In Progress Status in systemd source package in Cosmic: Won't Fix Status in systemd source package in Eoan: In Progress Bug description: We are using Ubuntu in a university network with lots of ldap users. To automatically map ldap users/groups to local groups we are using pam_group.so. This has worked for years. With the upgrade from Xenial to Bionic /etc/security/group.conf is not evaluated anymore by gnome-terminal as it runs as systemd --user. Xterm, ssh, su, and tty* however do work as expected. Only the default gnome-terminal behaves different. According to https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=851243 and https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=756458 this might not be a bug, but a feature. Nevertheless this behavior is very unexpected when upgrading from Xenial to Bionic and therefore should at least added to the changelog. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: gnome-terminal 3.28.0-1ubuntu1 ProcVersionSignature: Ubuntu 4.15.0-10.11-generic 4.15.3 Uname: Linux 4.15.0-10-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.9-0ubuntu4 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Mon Apr 9 13:17:52 2018 InstallationDate: Installed on 2018-03-29 (11 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Alpha amd64 (20180321) SourcePackage: gnome-terminal UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/systemd/+bug/1762391/+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 1831787] Re: Bogus routes after DHCP lease change
** Changed in: systemd (Ubuntu) Status: In Progress => Fix Released -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to systemd in Ubuntu. https://bugs.launchpad.net/bugs/1831787 Title: Bogus routes after DHCP lease change Status in netplan: Invalid Status in systemd: Unknown Status in systemd package in Ubuntu: Fix Released Status in systemd source package in Bionic: In Progress Status in systemd source package in Disco: Won't Fix Status in systemd source package in Eoan: Fix Released Bug description: [impact] networkd does not remove old route(s) after DHCP address change [test case] on a system using networkd, that is connected to a network where you can control the addresses that the DHCP server provides, setup system with networkd to get address via DHCP, e.g. [Match] Name=ens3 [Network] DHCP=ipv4 (re)start networkd or reboot, so the system gets an ipv4 DHCP address, and corresponding route to the gateway. Then on the dhcp server, change the subnet to a different subnet. On the client, once its renews its DHCP address, the server will provide a new address in the new subnet, and the client will add a new default route to the new gateway address. However, the old default route to the old gateway address isn't removed. Note this also happens without changing the entire subnet, but is more subtle as shown in the original description. [regression potential] this affects how networkd handles routes, so has the potential to leave a system with partial or incorrect networking, or no networking at all. Any regression would most likely occur during networkd (re)start or during renewal of a DHCP lease, or when an interface is brought up. [other info] original description: --- Netplan config: network: version: 2 renderer: networkd ethernets: eno4: dhcp4: no eno1np0: dhcp4: no addresses: - 172.16.0.2/24 bridges: br0: dhcp4: yes interfaces: - eno4 On initial boot, machine got 10.0.15.109 IP address: May 03 13:09:41 ceph2 systemd-networkd[29349]: br0: Configured May 03 13:09:41 ceph2 systemd-networkd[29349]: br0: DHCPv4 address 10.0.15.109/23 via 10.0.15.253 At one point, DHCP server reserver this IP address and client eventually picked up new IP address: May 03 15:01:12 ceph2 systemd-networkd[1137]: br0: DHCPv4 address 10.0.15.128/23 via 10.0.15.253 This resulted in IP addresses: # ip -o a 1: loinet 127.0.0.1/8 scope host lo\ valid_lft forever preferred_lft forever 1: loinet6 ::1/128 scope host \ valid_lft forever preferred_lft forever 2: eno1np0inet 172.16.0.2/24 brd 172.16.0.255 scope global eno1np0\ valid_lft forever preferred_lft forever 2: eno1np0inet6 fe80::b226:28ff:fe53:56be/64 scope link \ valid_lft forever preferred_lft forever 6: br0inet 10.0.15.128/23 brd 10.0.15.255 scope global dynamic br0\ valid_lft 503sec preferred_lft 503sec 6: br0inet6 fe80::b8d7:5eff:fe6b:62a/64 scope link \ valid_lft forever preferred_lft forever So far, everything is fine. But, the routes on the machine are bogus: # ip r default via 10.0.15.253 dev br0 proto dhcp src 10.0.15.109 metric 100 default via 10.0.15.253 dev br0 proto dhcp src 10.0.15.128 metric 100 10.0.14.0/23 dev br0 proto kernel scope link src 10.0.15.128 10.0.15.253 dev br0 proto dhcp scope link src 10.0.15.109 metric 100 10.0.15.253 dev br0 proto dhcp scope link src 10.0.15.128 metric 100 172.16.0.0/24 dev eno1np0 proto kernel scope link src 172.16.0.2 routes with src 10.0.15.109 should have been removed when lease was renewed. I'm not sure if this is a bug in netplan or systemd. This is 18.04, systemd 37-3ubuntu10.21, netplan 0.40.1~18.04.4. To manage notifications about this bug go to: https://bugs.launchpad.net/netplan/+bug/1831787/+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 1859948] [NEW] behaviour matrix depends on how it is created
Public bug reported: In Python3 (and in Python2) the behaviour of a matrix depends on how it is created. If elements are assigned directly, it behaves as it should, but if a row is created and then several of these rows are appended to the matrix, this matrix misbehaves, even when it appears to be the same matrix as the first one. I have added a .py program that shows the bug: codevierkant_experiment.py. The same happens in Python2, and also in the newer Python3 in Ubuntu 19.10 ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: python3 3.6.7-1~18.04 ProcVersionSignature: Ubuntu 5.0.0-37.40~18.04.1-generic 5.0.21 Uname: Linux 5.0.0-37-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.9 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Thu Jan 16 10:17:39 2020 InstallationDate: Installed on 2019-09-05 (132 days ago) InstallationMedia: Ubuntu 18.04.3 LTS "Bionic Beaver" - Release amd64 (20190805) ProcEnviron: PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=nl_NL.UTF-8 SHELL=/bin/bash SourcePackage: python3-defaults UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: python3-defaults (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug bionic ** Attachment added: "codevierkant_experiment.py" https://bugs.launchpad.net/bugs/1859948/+attachment/5320805/+files/codevierkant_experiment.py -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to python3-defaults in Ubuntu. https://bugs.launchpad.net/bugs/1859948 Title: behaviour matrix depends on how it is created Status in python3-defaults package in Ubuntu: New Bug description: In Python3 (and in Python2) the behaviour of a matrix depends on how it is created. If elements are assigned directly, it behaves as it should, but if a row is created and then several of these rows are appended to the matrix, this matrix misbehaves, even when it appears to be the same matrix as the first one. I have added a .py program that shows the bug: codevierkant_experiment.py. The same happens in Python2, and also in the newer Python3 in Ubuntu 19.10 ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: python3 3.6.7-1~18.04 ProcVersionSignature: Ubuntu 5.0.0-37.40~18.04.1-generic 5.0.21 Uname: Linux 5.0.0-37-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.9 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Thu Jan 16 10:17:39 2020 InstallationDate: Installed on 2019-09-05 (132 days ago) InstallationMedia: Ubuntu 18.04.3 LTS "Bionic Beaver" - Release amd64 (20190805) ProcEnviron: PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=nl_NL.UTF-8 SHELL=/bin/bash SourcePackage: python3-defaults UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/python3-defaults/+bug/1859948/+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 1847816] Re: storage autopkgtest always fails with linux-{kvm, azure, etc} kernels that don't include scsi_debug module
** Changed in: systemd (Ubuntu Focal)
Assignee: Dan Streetman (ddstreet) => (unassigned)
** Changed in: systemd (Ubuntu Eoan)
Assignee: Dan Streetman (ddstreet) => (unassigned)
** Changed in: systemd (Ubuntu Disco)
Assignee: Dan Streetman (ddstreet) => (unassigned)
** Changed in: systemd (Ubuntu Xenial)
Assignee: Dan Streetman (ddstreet) => (unassigned)
** Changed in: systemd (Ubuntu Bionic)
Assignee: Dan Streetman (ddstreet) => (unassigned)
** Changed in: systemd (Ubuntu Xenial)
Status: In Progress => Invalid
** Changed in: systemd (Ubuntu Bionic)
Status: In Progress => Invalid
** Changed in: systemd (Ubuntu Eoan)
Status: In Progress => Invalid
** Changed in: systemd (Ubuntu Focal)
Status: In Progress => Invalid
** Changed in: systemd (Ubuntu Disco)
Status: Won't Fix => Invalid
** Description changed:
[impact]
the 'storage' autopkgtest requires the 'scsi_debug' module, and if it
can't load it (and it's not built-in), the test fails. On some custom
kernels, this module is included in the new 'linux-modules-extra-*' deb
which isn't installed by default, so the test always fails when doing a
reverse-dep autopkgtest using such a kernel's meta pkg.
[test case]
run the 'storage' autopkgtest with a custom kernel that doesn't provide
the scsi_debug module in the standard linux-modules deb, or check the
autopkgtest.u.c history, for example:
https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac
/autopkgtest-focal/focal/amd64/s/systemd/20191209_150835_237a5@/log.gz
[regression potential]
- test case skipping only, so very low if any regression potential.
+ as this modifies one of the autopkgtest --setup-commands, and assumes
+ that all custom 'linux-meta-FLAVOR' kernels have a corresponding 'linux-
+ modules-extra-FLAVOR' deb (or will match the alternate 'linux-image-
+ generic-FLAVOR' naming), a regression would most likely cause immediate
+ test failure due to failing to install the proper linux-* debs.
--
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/1847816
Title:
storage autopkgtest always fails with linux-{kvm,azure,etc} kernels
that don't include scsi_debug module
Status in autopkgtest-cloud:
New
Status in systemd package in Ubuntu:
Invalid
Status in systemd source package in Xenial:
Invalid
Status in systemd source package in Bionic:
Invalid
Status in systemd source package in Disco:
Invalid
Status in systemd source package in Eoan:
Invalid
Status in systemd source package in Focal:
Invalid
Bug description:
[impact]
the 'storage' autopkgtest requires the 'scsi_debug' module, and if it
can't load it (and it's not built-in), the test fails. On some custom
kernels, this module is included in the new 'linux-modules-extra-*'
deb which isn't installed by default, so the test always fails when
doing a reverse-dep autopkgtest using such a kernel's meta pkg.
[test case]
run the 'storage' autopkgtest with a custom kernel that doesn't
provide the scsi_debug module in the standard linux-modules deb, or
check the autopkgtest.u.c history, for example:
https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac
/autopkgtest-focal/focal/amd64/s/systemd/20191209_150835_237a5@/log.gz
[regression potential]
as this modifies one of the autopkgtest --setup-commands, and assumes
that all custom 'linux-meta-FLAVOR' kernels have a corresponding
'linux-modules-extra-FLAVOR' deb (or will match the alternate 'linux-
image-generic-FLAVOR' naming), a regression would most likely cause
immediate test failure due to failing to install the proper linux-*
debs.
To manage notifications about this bug go to:
https://bugs.launchpad.net/autopkgtest-cloud/+bug/1847816/+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 1853373] Re: Print problems for double sided, multiple copies
My printer is Epson WFC-869R Workforce series. Affected with same bug. -- 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/1853373 Title: Print problems for double sided, multiple copies Status in cups package in Ubuntu: Confirmed Bug description: My HP Envy 5030 driver in Ubuntu 19.10 allows for double sided and multiple copy printing, however, I am experiencing an issue where only one copy prints. It prints fine, double sided, but only one copy is spooled. Looking at the bug list here, there was a similar issue with Evince and LibreOffice documents back in 2010. I'm not using any office software to print my PDF file, only the in- built Document Viewer. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/cups/+bug/1853373/+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 1847816] Re: storage autopkgtest always fails with linux-{kvm, azure, etc} kernels that don't include scsi_debug module
** Merge proposal linked:
https://code.launchpad.net/~ddstreet/autopkgtest-cloud/+git/autopkgtest-cloud/+merge/377688
--
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/1847816
Title:
storage autopkgtest always fails with linux-{kvm,azure,etc} kernels
that don't include scsi_debug module
Status in autopkgtest-cloud:
New
Status in systemd package in Ubuntu:
Invalid
Status in systemd source package in Xenial:
Invalid
Status in systemd source package in Bionic:
Invalid
Status in systemd source package in Disco:
Invalid
Status in systemd source package in Eoan:
Invalid
Status in systemd source package in Focal:
Invalid
Bug description:
[impact]
the 'storage' autopkgtest requires the 'scsi_debug' module, and if it
can't load it (and it's not built-in), the test fails. On some custom
kernels, this module is included in the new 'linux-modules-extra-*'
deb which isn't installed by default, so the test always fails when
doing a reverse-dep autopkgtest using such a kernel's meta pkg.
[test case]
run the 'storage' autopkgtest with a custom kernel that doesn't
provide the scsi_debug module in the standard linux-modules deb, or
check the autopkgtest.u.c history, for example:
https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac
/autopkgtest-focal/focal/amd64/s/systemd/20191209_150835_237a5@/log.gz
[regression potential]
as this modifies one of the autopkgtest --setup-commands, and assumes
that all custom 'linux-meta-FLAVOR' kernels have a corresponding
'linux-modules-extra-FLAVOR' deb (or will match the alternate 'linux-
image-generic-FLAVOR' naming), a regression would most likely cause
immediate test failure due to failing to install the proper linux-*
debs.
To manage notifications about this bug go to:
https://bugs.launchpad.net/autopkgtest-cloud/+bug/1847816/+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 1853373] Re: Print problems for double sided, multiple copies
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: cups (Ubuntu) Status: New => Confirmed -- 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/1853373 Title: Print problems for double sided, multiple copies Status in cups package in Ubuntu: Confirmed Bug description: My HP Envy 5030 driver in Ubuntu 19.10 allows for double sided and multiple copy printing, however, I am experiencing an issue where only one copy prints. It prints fine, double sided, but only one copy is spooled. Looking at the bug list here, there was a similar issue with Evince and LibreOffice documents back in 2010. I'm not using any office software to print my PDF file, only the in- built Document Viewer. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/cups/+bug/1853373/+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 1847816] Re: storage autopkgtest always fails with linux-{kvm, azure, etc} kernels that don't include scsi_debug module
** Description changed:
[impact]
the 'storage' autopkgtest requires the 'scsi_debug' module, and if it
can't load it (and it's not built-in), the test fails. On some custom
- kernels, this module isn't built, so the test always fails when doing a
- reverse-dep autopkgtest using such a kernel.
-
- As it doesn't make sense for the custom kernels to build the scsi_debug
- module for these kernels just so the systemd autopkgtest can pass, there
- should be some kind of check in the systemd 'storage' test for a non-
- standard kernel (that doesn't include the scsi_debug module) and skip
- the test in that case.
+ kernels, this module is included in the new 'linux-modules-extra-*' deb
+ which isn't installed by default, so the test always fails when doing a
+ reverse-dep autopkgtest using such a kernel's meta pkg.
[test case]
- run the 'storage' autopkgtest with a kernel that doesn't provide the
- scsi_debug module, or check the autopkgtest.u.c history.
+ run the 'storage' autopkgtest with a custom kernel that doesn't provide
+ the scsi_debug module in the standard linux-modules deb, or check the
+ autopkgtest.u.c history, for example:
+
+
https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac
+ /autopkgtest-focal/focal/amd64/s/systemd/20191209_150835_237a5@/log.gz
[regression potential]
- test case skipping only, so very low if any regression potential
+ test case skipping only, so very low if any regression potential.
** Also affects: autopkgtest-cloud
Importance: Undecided
Status: New
** Changed in: autopkgtest-cloud
Assignee: (unassigned) => Dan Streetman (ddstreet)
--
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/1847816
Title:
storage autopkgtest always fails with linux-{kvm,azure,etc} kernels
that don't include scsi_debug module
Status in autopkgtest-cloud:
New
Status in systemd package in Ubuntu:
In Progress
Status in systemd source package in Xenial:
In Progress
Status in systemd source package in Bionic:
In Progress
Status in systemd source package in Disco:
Won't Fix
Status in systemd source package in Eoan:
In Progress
Status in systemd source package in Focal:
In Progress
Bug description:
[impact]
the 'storage' autopkgtest requires the 'scsi_debug' module, and if it
can't load it (and it's not built-in), the test fails. On some custom
kernels, this module is included in the new 'linux-modules-extra-*'
deb which isn't installed by default, so the test always fails when
doing a reverse-dep autopkgtest using such a kernel's meta pkg.
[test case]
run the 'storage' autopkgtest with a custom kernel that doesn't
provide the scsi_debug module in the standard linux-modules deb, or
check the autopkgtest.u.c history, for example:
https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac
/autopkgtest-focal/focal/amd64/s/systemd/20191209_150835_237a5@/log.gz
[regression potential]
test case skipping only, so very low if any regression potential.
To manage notifications about this bug go to:
https://bugs.launchpad.net/autopkgtest-cloud/+bug/1847816/+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
