[Touch-packages] [Bug 1837700] Re: Dell system takes a long time to connect network with external dock
** Changed in: oem-priority 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/1837700 Title: Dell system takes a long time to connect network with external dock Status in HWE Next: New Status in OEM Priority Project: Fix Released Status in systemd package in Ubuntu: Fix Released Status in systemd source package in Bionic: Fix Released Status in systemd source package in Disco: Fix Released Status in systemd source package in Eoan: Fix Released Bug description: update for SRU process: [Impact] 1. On system featured mac passthrough, e.g., Dell/Lenovo laptop, or system occasionally install two USB ethernet with same MAC address, the system will suffer 90 seconds for network interface renaming mechanism before the last USB ethernet interface to activate. [Test Case] 1. Install ubuntu on Dell laptop. 2. Connect the Dell laptop with two Realtek 8153 USB ethernet dongle. Users can observe the last one will take 90 seconds for renaming to rename0. 3. Users can also find that the two USB ethernet have the same MAC address. [Regression Potential] To resolve the issue, drop a debian patch from systemd package. The debian patch is to revert an upstream commit to support 75-persistent-net-generator.rules udev rule. Since the udev rule is deprecated, the regression potential should be relatively low. --- Dell has a feature called MAC addrss passthrough[1] that would force usb ethernet adapters to be assigned with a predefined MAC address stored in BIOS or so. This feature has been landed to mainline kernel in driver r8152[2]. So whenever a r8152 managed device is plugged into Dell devices with MAC addrss passthrough enabled, this driver will set NIC MAC to a predefined one. And some Dell devices have already one built-in r8152 NIC port. On these devices, when a second r8152 NIC is plugged in, a Debian originated udev rules file 73-usb-net-by-mac.rules[3] will invoke udev built-in command `net_id` to give a persistent name, and that will be based on MAC address. However, since the system has already initialized the built-in r8152 NIC with that name, renaming the second interface with this name will always fail. While Debian still carries a patch called "Revert-udev-network-device- renaming-immediately-give.patch"[4] that tries to keep support of already deprecated "75-persistent-net-generator.rules" based interface renaming mechanism, this patch also propagated into Ubuntu[5]. This patch will retry renaming with a 90 seconds timeout when the error code is -EEXIST, so the uevent processing will always be blocked in the last ifrename step in the victim system. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: udev 237-3ubuntu10.24 [modified: lib/udev/rules.d/50-firmware.rules lib/udev/rules.d/50-udev-default.rules lib/udev/rules.d/73-special-net-names.rules lib/udev/rules.d/73-usb-net-by-mac.rules] ProcVersionSignature: Ubuntu 4.15.0-1043.48-oem 4.15.18 Uname: Linux 4.15.0-1043-oem x86_64 ApportVersion: 2.20.9-0ubuntu7.2 Architecture: amd64 CurrentDesktop: ubuntu:GNOME CustomUdevRuleFiles: 70-snap.core.rules 95-oem-hotkey-osd.rules Date: Wed Jul 24 15:30:59 2019 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-jorah+X90 InstallationDate: Installed on 2019-07-03 (20 days ago) InstallationMedia: Ubuntu 18.04 "Bionic" - Build amd64 LIVE Binary 20180608-09:38 MachineType: Dell Inc. Latitude 7424 Rugged Extreme ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-1043-oem.efi.signed root=UUID=5da90c85-3500-49a2-b989-71a604f9eec4 ro mem_sleep_default=deep quiet splash systemd.log_level=debug udev.log-priority=debug log_buf_len=8M vt.handoff=1 SourcePackage: systemd UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 05/27/2019 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.5.0 dmi.board.name: 0Y7FK3 dmi.board.vendor: Dell Inc. dmi.board.version: X03 dmi.chassis.type: 10 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr1.5.0:bd05/27/2019:svnDellInc.:pnLatitude7424RuggedExtreme:pvr:rvnDellInc.:rn0Y7FK3:rvrX03:cvnDellInc.:ct10:cvr: dmi.product.family: Latitude dmi.product.name: Latitude 7424 Rugged Extreme dmi.sys.vendor: Dell Inc. [1]: https://www.dell.com/support/article/tw/zh/twdhs1/sln301147/what-is-mac-address-pass-through?lang=en [2]: https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/tree/drivers/net/usb/r8152.c [3]: https://salsa.debian.org/systemd-team/systemd/blob/master/debian/extra/rules/73-usb-net-by-mac.rules [4]:
[Touch-packages] [Bug 1710863] Re: Question dialog showing "text" as the question.
I just experienced this on Kubuntu 19.04. It made me very reluctant to press the "Yes" button, as I had no idea what would happen... So I think for the usability of the tool, it would be quite important to fix this. ** Changed in: apport (Ubuntu) Status: Invalid => Confirmed -- 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/1710863 Title: Question dialog showing "text" as the question. Status in apport package in Ubuntu: Confirmed Bug description: Screenshot that would not disappoint "thedailywtf.com" When running apport-collect 1706052, After authenticating, I got the following dialog on the screen. Just in order to report the bug to #1706052 , I selected "Yes", and you can see all the stuff it uploaded to that bug. Using Kubuntu 17.04. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apport/+bug/1710863/+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 1842284] [NEW] initramfs does not copy ehci-platform
Public bug reported: ehci-platform is the USB host driver for several platform and also available in Xenial HWE kernel, but initramfs does not copy it into initrd and system can not boot from USB storage on that machine. ** Affects: initramfs-tools (Ubuntu) Importance: Undecided Status: New ** Affects: initramfs-tools (Ubuntu Xenial) Importance: Undecided Status: New ** Also affects: initramfs-tools (Ubuntu Xenial) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to initramfs-tools in Ubuntu. https://bugs.launchpad.net/bugs/1842284 Title: initramfs does not copy ehci-platform Status in initramfs-tools package in Ubuntu: New Status in initramfs-tools source package in Xenial: New Bug description: ehci-platform is the USB host driver for several platform and also available in Xenial HWE kernel, but initramfs does not copy it into initrd and system can not boot from USB storage on that machine. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/initramfs-tools/+bug/1842284/+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 1589289] Update Released
The verification of the Stable Release Update for util-linux has completed successfully and the package has now been 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 util-linux in Ubuntu. https://bugs.launchpad.net/bugs/1589289 Title: fstrim: cannot open /dev/.lxd-mounts: Permission denied Status in util-linux package in Ubuntu: Fix Released Status in util-linux source package in Xenial: Fix Committed Status in util-linux source package in Bionic: Fix Committed Status in util-linux source package in Disco: Fix Released Status in util-linux package in Debian: Unknown Bug description: [Impact] fstrim weekly cronjob output in an unprivileged LXD container: /etc/cron.weekly/fstrim: fstrim: cannot open /dev/.lxd-mounts: Permission denied fstrim: /dev/fuse: not a directory fstrim: /dev/lxd: FITRIM ioctl failed: Operation not permitted There is a github issue: https://github.com/lxc/lxd/issues/2030 The outcome is that it's purely an fstrim misbehaviour, it could be smarter. Stephane Graber comment: As all of this is handled by the kernel, there isn't anything we can do about it in LXD. I think fstrim should be made slightly more clever: * Don't run on bind-mounts (you can detect bind-mounts by parsing /proc/self/mountinfo instead of /proc/mounts) * Maybe not be as noisy on expected errors like EACCES, EPERM and ENOENT, only log actual failures which would likely be EINVAL or memory related errors. ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: util-linux 2.27.1-6ubuntu3 ProcVersionSignature: Ubuntu 4.4.0-21.37-generic 4.4.6 Uname: Linux 4.4.0-21-generic x86_64 ApportVersion: 2.20.1-0ubuntu2.1 Architecture: amd64 Date: Sun Jun 5 19:49:04 2016 ProcEnviron: LANGUAGE=en_US:en TERM=xterm PATH=(custom, no user) LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: util-linux UpgradeStatus: No upgrade log present (probably fresh install) [Test Case] * Ubuntu lxd container * Wait for the scheduled fstrim run (X: cronjob, B and late: systemd timer) * fstrim will run and report errors "Operation not permitted" "Permission denied", ... Container shouldn't run fstrim, it should only be run at host level. [Potential Regression] None, the change will only block fstrim to be automatically run at scheduled time. One can still run fstrim on a container manually, even if there is no purpose of doing that. Xenial uses the cronjob approach /etc/cron.weekly/fstrim Bionic and late switched to a systemd timer. 2 differents fixes (one for X, and one for B and late) will be needed, but they'll do same thing, which prevent fstrim to automatically run if inside a container both fixes using systemd-virt-detect. [Other Informations] * The systemd timer change upstream PR: https://github.com/karelzak/util-linux/pull/841 https://github.com/karelzak/util-linux/commit/0280d31a2bd6292acd9a4b86d0f6b5feb275a618 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/util-linux/+bug/1589289/+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 1048430] Re: "dnsmasq not available on the bus"
Just had the same problem on a embedded system with network-manager system install. I had to disable use of an IPv4 setting called "never- default" when I set it to "true" this bug occurred. Might be the problem. -- 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/1048430 Title: "dnsmasq not available on the bus" Status in network-manager package in Ubuntu: Confirmed Bug description: Dnsmasq seems to be having some issues. This occurs whenever I try to connect to my wireless network; sometimes it only happens once, but sometimes the error loops for a while. Sep 9 17:43:51 bkerensa NetworkManager[935]: DNS: starting dnsmasq... Sep 9 17:43:51 bkerensa NetworkManager[935]: [1347237831.899067] [nm-dns-dnsmasq.c:390] update(): dnsmasq not available on the bus, can't update servers. Sep 9 17:43:51 bkerensa NetworkManager[935]: [1347237831.899142] [nm-dns-dnsmasq.c:392] update(): dnsmasq owner not found on bus: Could not get owner of name 'org.freedesktop.NetworkManager.dnsmasq': no such name Sep 9 17:43:51 bkerensa NetworkManager[935]: DNS: plugin dnsmasq update failed Sep 9 17:43:51 bkerensa NetworkManager[935]: ((null)): writing resolv.conf to /sbin/resolvconf ProblemType: Bug DistroRelease: Ubuntu 12.10 Package: dnsmasq (not installed) ProcVersionSignature: Ubuntu 3.5.0-13.14-generic 3.5.3 Uname: Linux 3.5.0-13-generic x86_64 ApportVersion: 2.5.1-0ubuntu7 Architecture: amd64 Date: Sun Sep 9 17:47:22 2012 EcryptfsInUse: Yes InstallationMedia: Ubuntu 12.04 LTS "Precise Pangolin" - Release amd64 (20120425) ProcEnviron: TERM=xterm PATH=(custom, no user) LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: dnsmasq UpgradeStatus: Upgraded to quantal on 2012-08-08 (32 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1048430/+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 1833536] Re: QuiteRSS crashes intermittently
This bug was fixed in the package qtbase-opensource-src - 5.12.2+dfsg- 4ubuntu1.1 --- qtbase-opensource-src (5.12.2+dfsg-4ubuntu1.1) disco; urgency=medium * Backport upstream patch to fix nullptr dereference in HTTP handler (LP: #1833536). -- Dmitry Shachnev Tue, 25 Jun 2019 13:23:10 +0300 ** Changed in: qtbase-opensource-src (Ubuntu Disco) Status: Fix Committed => Fix Released -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to qtbase-opensource-src in Ubuntu. https://bugs.launchpad.net/bugs/1833536 Title: QuiteRSS crashes intermittently Status in qtbase-opensource-src package in Ubuntu: Fix Released Status in qtbase-opensource-src source package in Bionic: Fix Committed Status in qtbase-opensource-src source package in Disco: Fix Released Bug description: [Impact] This bug affects QuiteRSS and other Qt applications, like plasma-discover (see https://bugs.kde.org/show_bug.cgi?id=402848) and qbittorrent (see bug 1814375). All they crash with similar stack traces. [Test Case] 1. Open QuiteRSS. 2. Leave it running for several hours. 3. It should not crash. [Proposed Fix] The proposed fix is a backport of the following commit from upstream 5.12 branch: https://code.qt.io/cgit/qt/qtbase.git/commit/?id=e431a3ac027915db [Regression Potential] This patch adds an additional check before re-sending the request. Regressions chance is minimal, but the potential regressions may be that the request is not re-sent where it was re-sent with the previous code. [Original Description] After opening QuiteRSS it will run until crash happens. This happens intermittently within the hour usually. (gdb) bt #0 QHttpNetworkConnectionChannel::sendRequest (this=) at access/qhttpnetworkconnectionchannel.cpp:238 #1 0x730deca2 in QHttpNetworkConnectionPrivate::_q_startNextRequest ( this=0x7fff480d4a20) at access/qhttpnetworkconnection.cpp:1015 #2 0x72736122 in QObject::event (this=0x7fff48da89b0, e=) at kernel/qobject.cpp:1247 #3 0x76f2482c in QApplicationPrivate::notify_helper(QObject*, QEvent*) () from /usr/lib/x86_64-linux-gnu/libQt5Widgets.so.5 #4 0x76f2c0f4 in QApplication::notify(QObject*, QEvent*) () from /usr/lib/x86_64-linux-gnu/libQt5Widgets.so.5 #5 0x727069a8 in QCoreApplication::notifyInternal2 ( receiver=0x7fff48da89b0, event=event@entry=0x7fff494233b0) at kernel/qcoreapplication.cpp:1024 #6 0x7270911d in QCoreApplication::sendEvent (event=0x7fff494233b0, receiver=) at ../../include/QtCore/../../src/corelib/kernel/qcoreapplication.h:233 #7 QCoreApplicationPrivate::sendPostedEvents (receiver=receiver@entry=0x0, event_type=event_type@entry=0, data=0x7fff60008e90) at kernel/qcoreapplication.cpp:1699 #8 0x727096a8 in QCoreApplication::sendPostedEvents ( receiver=receiver@entry=0x0, event_type=event_type@entry=0) at kernel/qcoreapplication.cpp:1553 #9 0x727602c3 in postEventSourceDispatch (s=0x7fff48003f10) at kernel/qeventdispatcher_glib.cpp:276 #10 0x7fffece96317 in g_main_context_dispatch () from /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0 #11 0x7fffece96550 in ?? () from /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0 #12 0x7fffece965dc in g_main_context_iteration () from /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0 #13 0x7275f8ef in QEventDispatcherGlib::processEvents ( this=0x7fff48000b20, flags=...) at kernel/qeventdispatcher_glib.cpp:423 #14 0x727049ea in QEventLoop::exec (this=this@entry=0x7fff4fffec60, flags=..., flags@entry=...) at kernel/qeventloop.cpp:212 #15 0x7252322a in QThread::exec (this=) at thread/qthread.cpp:515 #16 0x7252816d in QThreadPrivate::start (arg=0x7fff60008a20) at thread/qthread_unix.cpp:368 #17 0x722646db in start_thread (arg=0x7fff4700) at pthread_create.c:463 #18 0x719ec88f in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:95 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/qtbase-opensource-src/+bug/1833536/+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 1833536] Update Released
The verification of the Stable Release Update for qtbase-opensource-src has completed successfully and the package has now been 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 qtbase-opensource-src in Ubuntu. https://bugs.launchpad.net/bugs/1833536 Title: QuiteRSS crashes intermittently Status in qtbase-opensource-src package in Ubuntu: Fix Released Status in qtbase-opensource-src source package in Bionic: Fix Committed Status in qtbase-opensource-src source package in Disco: Fix Released Bug description: [Impact] This bug affects QuiteRSS and other Qt applications, like plasma-discover (see https://bugs.kde.org/show_bug.cgi?id=402848) and qbittorrent (see bug 1814375). All they crash with similar stack traces. [Test Case] 1. Open QuiteRSS. 2. Leave it running for several hours. 3. It should not crash. [Proposed Fix] The proposed fix is a backport of the following commit from upstream 5.12 branch: https://code.qt.io/cgit/qt/qtbase.git/commit/?id=e431a3ac027915db [Regression Potential] This patch adds an additional check before re-sending the request. Regressions chance is minimal, but the potential regressions may be that the request is not re-sent where it was re-sent with the previous code. [Original Description] After opening QuiteRSS it will run until crash happens. This happens intermittently within the hour usually. (gdb) bt #0 QHttpNetworkConnectionChannel::sendRequest (this=) at access/qhttpnetworkconnectionchannel.cpp:238 #1 0x730deca2 in QHttpNetworkConnectionPrivate::_q_startNextRequest ( this=0x7fff480d4a20) at access/qhttpnetworkconnection.cpp:1015 #2 0x72736122 in QObject::event (this=0x7fff48da89b0, e=) at kernel/qobject.cpp:1247 #3 0x76f2482c in QApplicationPrivate::notify_helper(QObject*, QEvent*) () from /usr/lib/x86_64-linux-gnu/libQt5Widgets.so.5 #4 0x76f2c0f4 in QApplication::notify(QObject*, QEvent*) () from /usr/lib/x86_64-linux-gnu/libQt5Widgets.so.5 #5 0x727069a8 in QCoreApplication::notifyInternal2 ( receiver=0x7fff48da89b0, event=event@entry=0x7fff494233b0) at kernel/qcoreapplication.cpp:1024 #6 0x7270911d in QCoreApplication::sendEvent (event=0x7fff494233b0, receiver=) at ../../include/QtCore/../../src/corelib/kernel/qcoreapplication.h:233 #7 QCoreApplicationPrivate::sendPostedEvents (receiver=receiver@entry=0x0, event_type=event_type@entry=0, data=0x7fff60008e90) at kernel/qcoreapplication.cpp:1699 #8 0x727096a8 in QCoreApplication::sendPostedEvents ( receiver=receiver@entry=0x0, event_type=event_type@entry=0) at kernel/qcoreapplication.cpp:1553 #9 0x727602c3 in postEventSourceDispatch (s=0x7fff48003f10) at kernel/qeventdispatcher_glib.cpp:276 #10 0x7fffece96317 in g_main_context_dispatch () from /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0 #11 0x7fffece96550 in ?? () from /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0 #12 0x7fffece965dc in g_main_context_iteration () from /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0 #13 0x7275f8ef in QEventDispatcherGlib::processEvents ( this=0x7fff48000b20, flags=...) at kernel/qeventdispatcher_glib.cpp:423 #14 0x727049ea in QEventLoop::exec (this=this@entry=0x7fff4fffec60, flags=..., flags@entry=...) at kernel/qeventloop.cpp:212 #15 0x7252322a in QThread::exec (this=) at thread/qthread.cpp:515 #16 0x7252816d in QThreadPrivate::start (arg=0x7fff60008a20) at thread/qthread_unix.cpp:368 #17 0x722646db in start_thread (arg=0x7fff4700) at pthread_create.c:463 #18 0x719ec88f in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:95 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/qtbase-opensource-src/+bug/1833536/+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 1589289] Re: fstrim: cannot open /dev/.lxd-mounts: Permission denied
This bug was fixed in the package util-linux - 2.33.1-0.1ubuntu3 --- util-linux (2.33.1-0.1ubuntu3) disco; urgency=medium * d/p/prevent-fstrim-inside-container.patch: - Prevent fstrim to run inside a container environment. (LP: #1589289) -- Eric Desrochers Thu, 22 Aug 2019 23:40:49 + ** Changed in: util-linux (Ubuntu Disco) Status: Fix Committed => Fix Released -- 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/1589289 Title: fstrim: cannot open /dev/.lxd-mounts: Permission denied Status in util-linux package in Ubuntu: Fix Released Status in util-linux source package in Xenial: Fix Committed Status in util-linux source package in Bionic: Fix Released Status in util-linux source package in Disco: Fix Released Status in util-linux package in Debian: Unknown Bug description: [Impact] fstrim weekly cronjob output in an unprivileged LXD container: /etc/cron.weekly/fstrim: fstrim: cannot open /dev/.lxd-mounts: Permission denied fstrim: /dev/fuse: not a directory fstrim: /dev/lxd: FITRIM ioctl failed: Operation not permitted There is a github issue: https://github.com/lxc/lxd/issues/2030 The outcome is that it's purely an fstrim misbehaviour, it could be smarter. Stephane Graber comment: As all of this is handled by the kernel, there isn't anything we can do about it in LXD. I think fstrim should be made slightly more clever: * Don't run on bind-mounts (you can detect bind-mounts by parsing /proc/self/mountinfo instead of /proc/mounts) * Maybe not be as noisy on expected errors like EACCES, EPERM and ENOENT, only log actual failures which would likely be EINVAL or memory related errors. ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: util-linux 2.27.1-6ubuntu3 ProcVersionSignature: Ubuntu 4.4.0-21.37-generic 4.4.6 Uname: Linux 4.4.0-21-generic x86_64 ApportVersion: 2.20.1-0ubuntu2.1 Architecture: amd64 Date: Sun Jun 5 19:49:04 2016 ProcEnviron: LANGUAGE=en_US:en TERM=xterm PATH=(custom, no user) LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: util-linux UpgradeStatus: No upgrade log present (probably fresh install) [Test Case] * Ubuntu lxd container * Wait for the scheduled fstrim run (X: cronjob, B and late: systemd timer) * fstrim will run and report errors "Operation not permitted" "Permission denied", ... Container shouldn't run fstrim, it should only be run at host level. [Potential Regression] None, the change will only block fstrim to be automatically run at scheduled time. One can still run fstrim on a container manually, even if there is no purpose of doing that. Xenial uses the cronjob approach /etc/cron.weekly/fstrim Bionic and late switched to a systemd timer. 2 differents fixes (one for X, and one for B and late) will be needed, but they'll do same thing, which prevent fstrim to automatically run if inside a container both fixes using systemd-virt-detect. [Other Informations] * The systemd timer change upstream PR: https://github.com/karelzak/util-linux/pull/841 https://github.com/karelzak/util-linux/commit/0280d31a2bd6292acd9a4b86d0f6b5feb275a618 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/util-linux/+bug/1589289/+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 1589289] Re: fstrim: cannot open /dev/.lxd-mounts: Permission denied
This bug was fixed in the package util-linux - 2.31.1-0.4ubuntu3.4 --- util-linux (2.31.1-0.4ubuntu3.4) bionic; urgency=medium * d/p/prevent-fstrim-inside-container.patch: - Prevent fstrim to run inside a container environment. (LP: #1589289) -- Eric Desrochers Thu, 22 Aug 2019 23:47:46 + ** Changed in: util-linux (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 util-linux in Ubuntu. https://bugs.launchpad.net/bugs/1589289 Title: fstrim: cannot open /dev/.lxd-mounts: Permission denied Status in util-linux package in Ubuntu: Fix Released Status in util-linux source package in Xenial: Fix Committed Status in util-linux source package in Bionic: Fix Released Status in util-linux source package in Disco: Fix Released Status in util-linux package in Debian: Unknown Bug description: [Impact] fstrim weekly cronjob output in an unprivileged LXD container: /etc/cron.weekly/fstrim: fstrim: cannot open /dev/.lxd-mounts: Permission denied fstrim: /dev/fuse: not a directory fstrim: /dev/lxd: FITRIM ioctl failed: Operation not permitted There is a github issue: https://github.com/lxc/lxd/issues/2030 The outcome is that it's purely an fstrim misbehaviour, it could be smarter. Stephane Graber comment: As all of this is handled by the kernel, there isn't anything we can do about it in LXD. I think fstrim should be made slightly more clever: * Don't run on bind-mounts (you can detect bind-mounts by parsing /proc/self/mountinfo instead of /proc/mounts) * Maybe not be as noisy on expected errors like EACCES, EPERM and ENOENT, only log actual failures which would likely be EINVAL or memory related errors. ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: util-linux 2.27.1-6ubuntu3 ProcVersionSignature: Ubuntu 4.4.0-21.37-generic 4.4.6 Uname: Linux 4.4.0-21-generic x86_64 ApportVersion: 2.20.1-0ubuntu2.1 Architecture: amd64 Date: Sun Jun 5 19:49:04 2016 ProcEnviron: LANGUAGE=en_US:en TERM=xterm PATH=(custom, no user) LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: util-linux UpgradeStatus: No upgrade log present (probably fresh install) [Test Case] * Ubuntu lxd container * Wait for the scheduled fstrim run (X: cronjob, B and late: systemd timer) * fstrim will run and report errors "Operation not permitted" "Permission denied", ... Container shouldn't run fstrim, it should only be run at host level. [Potential Regression] None, the change will only block fstrim to be automatically run at scheduled time. One can still run fstrim on a container manually, even if there is no purpose of doing that. Xenial uses the cronjob approach /etc/cron.weekly/fstrim Bionic and late switched to a systemd timer. 2 differents fixes (one for X, and one for B and late) will be needed, but they'll do same thing, which prevent fstrim to automatically run if inside a container both fixes using systemd-virt-detect. [Other Informations] * The systemd timer change upstream PR: https://github.com/karelzak/util-linux/pull/841 https://github.com/karelzak/util-linux/commit/0280d31a2bd6292acd9a4b86d0f6b5feb275a618 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/util-linux/+bug/1589289/+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 1841915] Re: black screen, unresponsive, after logout from gnome Wayland session
Setting gdm3 to debugging mode reveals: Sep 02 17:31:01 kab systemd-logind[794]: Failed to restore VT, ignoring: Input/output error Full debug log attached. ** Attachment added: "eoan-wayland-logout-hang-verbose.txt.gz" https://bugs.launchpad.net/ubuntu/+source/gdm3/+bug/1841915/+attachment/5286186/+files/eoan-wayland-logout-hang-verbose.txt.gz ** Also affects: systemd (Ubuntu) Importance: Undecided Status: New ** 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/1841915 Title: black screen, unresponsive, after logout from gnome Wayland session Status in gdm3 package in Ubuntu: Confirmed Status in gnome-shell package in Ubuntu: Confirmed Status in systemd package in Ubuntu: Confirmed Bug description: on logout the screen is black, the system is unresponsive and has to be restarted. (Untested by me yet, but I expect ssh-ing in and restarting gdm would work.) I believe this may be already reported upstream here: https://bugzilla.redhat.com/show_bug.cgi?id=1745554 That's why I've reported this against gdm3 even though I honestly don't know if it might be a gnome-shell, gnome-session or mutter based error. (FWIW without the upstream bug to link to I'd maybe suspect gnome-shell first.) NB: This machine's conf has AutomaticLogin enabled, but another machine also on 19.10 does not, and it's showing the same thing. On *this* machine I found that the *first* time I logged out, it was OK, but not the second time. On the other machine, it fails first time too. It's as if the gdm login screen can appear exactly once. That (and being on gnome 3.33) is why I don't think this is a dupe of #1824588. Nothing appears in /var/crash as a result of this. ProblemType: Bug DistroRelease: Ubuntu 19.10 Package: gdm3 3.33.90-1ubuntu1 ProcVersionSignature: Ubuntu 5.2.0-13.14-generic 5.2.8 Uname: Linux 5.2.0-13-generic x86_64 ApportVersion: 2.20.11-0ubuntu7 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Thu Aug 29 10:51:22 2019 InstallationDate: Installed on 2018-09-11 (351 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Alpha amd64 (20180214) SourcePackage: gdm3 UpgradeStatus: Upgraded to eoan on 2019-07-16 (43 days ago) mtime.conffile..etc.gdm3.custom.conf: 2019-07-17T00:07:04.528641 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gdm3/+bug/1841915/+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 1589289] Re: fstrim: cannot open /dev/.lxd-mounts: Permission denied
As for xenial's chromium-browser test failures - could you please file a bug about the failing architectures? I would then include the bug number in the hint. This way we won't forget about the test issues. -- 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/1589289 Title: fstrim: cannot open /dev/.lxd-mounts: Permission denied Status in util-linux package in Ubuntu: Fix Released Status in util-linux source package in Xenial: Fix Committed Status in util-linux source package in Bionic: Fix Released Status in util-linux source package in Disco: Fix Released Status in util-linux package in Debian: Unknown Bug description: [Impact] fstrim weekly cronjob output in an unprivileged LXD container: /etc/cron.weekly/fstrim: fstrim: cannot open /dev/.lxd-mounts: Permission denied fstrim: /dev/fuse: not a directory fstrim: /dev/lxd: FITRIM ioctl failed: Operation not permitted There is a github issue: https://github.com/lxc/lxd/issues/2030 The outcome is that it's purely an fstrim misbehaviour, it could be smarter. Stephane Graber comment: As all of this is handled by the kernel, there isn't anything we can do about it in LXD. I think fstrim should be made slightly more clever: * Don't run on bind-mounts (you can detect bind-mounts by parsing /proc/self/mountinfo instead of /proc/mounts) * Maybe not be as noisy on expected errors like EACCES, EPERM and ENOENT, only log actual failures which would likely be EINVAL or memory related errors. ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: util-linux 2.27.1-6ubuntu3 ProcVersionSignature: Ubuntu 4.4.0-21.37-generic 4.4.6 Uname: Linux 4.4.0-21-generic x86_64 ApportVersion: 2.20.1-0ubuntu2.1 Architecture: amd64 Date: Sun Jun 5 19:49:04 2016 ProcEnviron: LANGUAGE=en_US:en TERM=xterm PATH=(custom, no user) LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: util-linux UpgradeStatus: No upgrade log present (probably fresh install) [Test Case] * Ubuntu lxd container * Wait for the scheduled fstrim run (X: cronjob, B and late: systemd timer) * fstrim will run and report errors "Operation not permitted" "Permission denied", ... Container shouldn't run fstrim, it should only be run at host level. [Potential Regression] None, the change will only block fstrim to be automatically run at scheduled time. One can still run fstrim on a container manually, even if there is no purpose of doing that. Xenial uses the cronjob approach /etc/cron.weekly/fstrim Bionic and late switched to a systemd timer. 2 differents fixes (one for X, and one for B and late) will be needed, but they'll do same thing, which prevent fstrim to automatically run if inside a container both fixes using systemd-virt-detect. [Other Informations] * The systemd timer change upstream PR: https://github.com/karelzak/util-linux/pull/841 https://github.com/karelzak/util-linux/commit/0280d31a2bd6292acd9a4b86d0f6b5feb275a618 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/util-linux/+bug/1589289/+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 1401474] Re: [Dell Inspiron 7737] The power indicator won't be available until the adapter connected / disconnected
Didn't see this issue with Bionic. Closing it. ** Changed in: indicator-power (Ubuntu) Status: Confirmed => Fix Released -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to indicator-power in Ubuntu. https://bugs.launchpad.net/bugs/1401474 Title: [Dell Inspiron 7737] The power indicator won't be available until the adapter connected / disconnected Status in indicator-power package in Ubuntu: Fix Released Bug description: CID: 201306-13869 Dell Inspiron 7737 The power indicator on this system only appears after you connect or disconnect it from the adapter. After it appears, reboot it will make the indicator disappear again. ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: indicator-power 12.10.6+14.04.20140411-0ubuntu1 ProcVersionSignature: Ubuntu 3.13.0-43.72-generic 3.13.11.11 Uname: Linux 3.13.0-43-generic x86_64 ApportVersion: 2.14.1-0ubuntu3.6 Architecture: amd64 CurrentDesktop: Unity Date: Thu Dec 11 05:06:39 2014 InstallationDate: Installed on 2014-12-11 (0 days ago) InstallationMedia: Ubuntu 14.04.1 LTS "Trusty Tahr" - Release amd64 (20140722.2) SourcePackage: indicator-power UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/indicator-power/+bug/1401474/+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 1842255] Re: package libnss3:amd64 2:3.28.4-0ubuntu0.16.04.6 [origin: Ubuntu] failed to install/upgrade: package libnss3:amd64 is already installed and configured
Thanks for your report. From this line of the Bug Description: DistroRelease: elementary 0.4.1 it seems that you are not experiencing this issue with Ubuntu, but with elementary OS. We are not able to investigate problems or provide support for operating systems different from Ubuntu, even if they derive from Ubuntu, like in this case. Since we use this bug tracker to track bugs in Ubuntu, I'm marking this bug as Invalid. If you believe this is actually a bug in Ubuntu and that elementary OS is inheriting it, please file a new bug report with all the logs generated and captured on an Ubuntu system. Thanks! ** Changed in: nss (Ubuntu) Status: New => Invalid -- 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/1842255 Title: package libnss3:amd64 2:3.28.4-0ubuntu0.16.04.6 [origin: Ubuntu] failed to install/upgrade: package libnss3:amd64 is already installed and configured Status in nss package in Ubuntu: Invalid Bug description: No more ProblemType: Package DistroRelease: elementary 0.4.1 Package: libnss3:amd64 2:3.28.4-0ubuntu0.16.04.6 ProcVersionSignature: Ubuntu 4.15.0-58.64~16.04.1-generic 4.15.18 Uname: Linux 4.15.0-58-generic x86_64 ApportVersion: 2.20.1-0ubuntu2.19 AptdaemonVersion: 1.1.1+bzr982-0ubuntu14.1 Architecture: amd64 Date: Sun Sep 1 13:00:20 2019 DuplicateSignature: package:libnss3:amd64:2:3.28.4-0ubuntu0.16.04.6 [origin: Ubuntu] Removing linux-modules-4.15.0-43-generic (4.15.0-43.46~16.04.1) ... dpkg: error processing package libnss3-nssdb (--configure): package libnss3-nssdb is already installed and configured ErrorMessage: package libnss3:amd64 is already installed and configured InstallationDate: Installed on 2018-05-26 (463 days ago) InstallationMedia: elementary OS 0.4.1 "Loki" - Stable amd64 (20180214) RelatedPackageVersions: dpkg 1.18.4ubuntu1.6 apt 1.2.32 SourcePackage: nss Title: package libnss3:amd64 2:3.28.4-0ubuntu0.16.04.6 [origin: Ubuntu] failed to install/upgrade: package libnss3:amd64 is already installed and configured UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nss/+bug/1842255/+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 1842310] [NEW] ip kvm interface appears as mounted device with errors
Public bug reported: I have an Avocent IP KVM with DSAVIQ-USB2 interfaces attached to my servers. Ive updated udev which is now at version 241. I am now seeing: Generating grub configuration file ... /dev/sdb: open failed: No medium found /dev/sdc: open failed: No medium found /dev/sdb: open failed: No medium found /dev/sdc: open failed: No medium found /dev/sdb: open failed: No medium found /dev/sdc: open failed: No medium found /dev/sdb: open failed: No medium found /dev/sdc: open failed: No medium found /dev/sdb: open failed: No medium found /dev/sdc: open failed: No medium found /dev/sdb: open failed: No medium found /dev/sdc: open failed: No medium found /dev/sdb: open failed: No medium found /dev/sdc: open failed: No medium found /dev/sdb: open failed: No medium found /dev/sdc: open failed: No medium found /dev/sdb: open failed: No medium found /dev/sdc: open failed: No medium found /dev/sdb: open failed: No medium found /dev/sdc: open failed: No medium found Found linux image: /boot/vmlinuz-5.0.21-1-pve Found initrd image: /boot/initrd.img-5.0.21-1-pve /dev/sdb: open failed: No medium found /dev/sdc: open failed: No medium found /dev/sdb: open failed: No medium found /dev/sdc: open failed: No medium found /dev/sdb: open failed: No medium found /dev/sdc: open failed: No medium found /dev/sdb: open failed: No medium found /dev/sdc: open failed: No medium found /dev/sdb: open failed: No medium found /dev/sdc: open failed: No medium found /dev/sdb: open failed: No medium found /dev/sdc: open failed: No medium found /dev/sdb: open failed: No medium found /dev/sdc: open failed: No medium found /dev/sdb: open failed: No medium found /dev/sdc: open failed: No medium found Found linux image: /boot/vmlinuz-4.15.18-20-pve Found initrd image: /boot/initrd.img-4.15.18-20-pve Found linux image: /boot/vmlinuz-4.15.18-12-pve Found initrd image: /boot/initrd.img-4.15.18-12-pve /dev/sdb: open failed: No medium found /dev/sdc: open failed: No medium found /dev/sdb: open failed: No medium found /dev/sdc: open failed: No medium found /dev/sdb: open failed: No medium found /dev/sdc: open failed: No medium found /dev/sdb: open failed: No medium found /dev/sdc: open failed: No medium found /dev/sdb: open failed: No medium found /dev/sdc: open failed: No medium found /dev/sdb: open failed: No medium found /dev/sdc: open failed: No medium found /dev/sdb: open failed: No medium found /dev/sdc: open failed: No medium found /dev/sdb: open failed: No medium found /dev/sdc: open failed: No medium found /dev/sdb: open failed: No medium found /dev/sdc: open failed: No medium found /dev/sdb: open failed: No medium found /dev/sdc: open failed: No medium found Found memtest86+ image: /boot/memtest86+.bin Found memtest86+ multiboot image: /boot/memtest86+_multiboot.bin done One device was an IPMI mounted ISO and the second is my Avocent IP KVM interface. Once I unmounted the IPMI ISO I am only seeing errors for /dev/sdb for the KVM interface. This is a new issue that was not present before upgrading my system. This error is also preventing my QEMU vm with pci-passthrough from starting. I see the same error when attempting to start my vm. ** Affects: initramfs-tools (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to initramfs-tools in Ubuntu. https://bugs.launchpad.net/bugs/1842310 Title: ip kvm interface appears as mounted device with errors Status in initramfs-tools package in Ubuntu: New Bug description: I have an Avocent IP KVM with DSAVIQ-USB2 interfaces attached to my servers. Ive updated udev which is now at version 241. I am now seeing: Generating grub configuration file ... /dev/sdb: open failed: No medium found /dev/sdc: open failed: No medium found /dev/sdb: open failed: No medium found /dev/sdc: open failed: No medium found /dev/sdb: open failed: No medium found /dev/sdc: open failed: No medium found /dev/sdb: open failed: No medium found /dev/sdc: open failed: No medium found /dev/sdb: open failed: No medium found /dev/sdc: open failed: No medium found /dev/sdb: open failed: No medium found /dev/sdc: open failed: No medium found /dev/sdb: open failed: No medium found /dev/sdc: open failed: No medium found /dev/sdb: open failed: No medium found /dev/sdc: open failed: No medium found /dev/sdb: open failed: No medium found /dev/sdc: open failed: No medium found /dev/sdb: open failed: No medium found /dev/sdc: open failed: No medium found Found linux image: /boot/vmlinuz-5.0.21-1-pve Found initrd image: /boot/initrd.img-5.0.21-1-pve /dev/sdb: open failed: No medium found /dev/sdc: open failed: No medium found /dev/sdb: open failed: No medium found /dev/sdc: open failed:
[Touch-packages] [Bug 1754671] Re: Full-tunnel VPN DNS leakage regression
Launchpad has imported 73 comments from the remote bug at
https://bugzilla.gnome.org/show_bug.cgi?id=746422.
If you reply to an imported comment from within Launchpad, your comment
will be sent to the remote bug automatically. Read more about
Launchpad's inter-bugtracker facilities at
https://help.launchpad.net/InterBugTracking.
On 2015-03-18T22:30:03+00:00 Dcbw-y wrote:
If the VPN routes all traffic (eg, its ipv4.never-default=false) that
usually indicates that the VPN's nameservers should be used instead of
the parent interface's nameservers, since the parent interface's
nameservers would be accessed over the VPN anyway (since it's routing
all traffic).
But with dns=dnsmasq, the dnsmasq plugin always does split DNS
regardless of the never-default value of the VPN's IPv4 config:
/* Use split DNS for VPN configs */
for (iter = (GSList *) vpn_configs; iter; iter = g_slist_next (iter)) {
if (NM_IS_IP4_CONFIG (iter->data))
add_ip4_config (conf, NM_IP4_CONFIG (iter->data), TRUE);
else if (NM_IS_IP6_CONFIG (iter->data))
add_ip6_config (conf, NM_IP6_CONFIG (iter->data), TRUE);
}
instead I think that each config should be added with split DNS only if
ipv4.never-default=true for that config. That would ensure that when
the VPN was routing all traffic, split DNS was not used, but when the
VPN was not routing all traffic, split DNS was used.
If the user really does want to use the parent interface's nameservers
even though they will be contacted over the VPN, they can either add
custom dnsmasq options to /etc/NetworkManager/dnsmasq.d or enter them
manually for the connection.
ISTR that the behavior I'm suggesting was always intended, but
apparently we changed that behavior a long time ago and possibly didn't
realize it?
Reply at: https://bugs.launchpad.net/ubuntu/+source/network-
manager/+bug/1754671/comments/0
On 2015-03-19T11:15:43+00:00 Psimerda wrote:
In my opinion it is useful to use split DNS view in all cases and only
use never-default setting to decide the global DNS.
Rationale: There is no such think as sending all traffic across VPN,
only default route traffic, i.e. traffic for which there's no specific
route over a specific interface. As specific routes (as found in the
routing table) are still used even with default route over VPN, I
believe that specific zones (as found in per-connection lists of
domains) should be maintained as well.
Reply at: https://bugs.launchpad.net/ubuntu/+source/network-
manager/+bug/1754671/comments/1
On 2015-03-20T07:58:02+00:00 warthog9 wrote:
Pavel, I'll admit to not 100% following what you've suggested, so please
excuse me if I've horribly miss-understood. I disagree with the
assertion that "There is no such think as sending all traffic across
VPN". The parent interface's adapter will have a local route mainly so
you can get to the gateway, as well as a route for vpn endpoint you need
to push traffic at however, there are some mitigating circumstances that
forcing split-dns, so that the DNS on the VPN is ONLY serving the search
spaces pushed, is actually exactly the opposite of what a user likely
wants and/or causes some rather broken behavior.
- VPNs can, and often do, have IP space overlap issues. So if the
parent interface's network you are on happens to be in the
10.0.0.0/255.255.252.0 (gateway 10.0.0.1, DNS server 10.0.0.2 &
10.0.0.3) ip range, and the VPN uses 10.0.1.0/255.255.255.0, you can end
up in some very screwed up situation. This is actually taken from a
real world scenario (which is why I learned of the change to default to
split DNS at all). If you are routing all traffic over the VPN you now
have lost access to the two parent interface's DNS servers, and with
split DNS you now have *NO* DNS access at all. As it currently stands
the only way to fix this is to either manually edit /etc/resolv.conf or
to restart NM without dnsmasq.
- DNS is not equal at all locations, which your assumption about split
DNS I think assumes. DNS zones mean that something that resolves
externally one way, may resolve completely differently (and
potentially). example.com, to an external resolver may go to a coloed
and public instance, while the same dns entry from an internal dns
server may not. Assuming the VPN only pushes a search of
internal.example.com, but doesn't push a search for example.com (making
the assumption that people will just type it), the internal site is now
unreachable. Keeping in mind I'm talking about VPNs, and those are
typically used in more corporate environments where you are dealing with
corporate IT departments.
- In a more casual environment, lets say a hotel, part of the reasons to
use a VPN is because the u
[Touch-packages] [Bug 1714178] Re: Triple 4K monitor display failed (modesetting driver limited to 8192x8192)
This bug was fixed in the package linux-oem-osp1 - 5.0.0-1020.22 --- linux-oem-osp1 (5.0.0-1020.22) bionic; urgency=medium * bionic/linux-oem-osp1: 5.0.0-1020.22 -proposed tracker (LP: #1840815) [ Ubuntu: 5.0.0-27.28 ] * disco/linux: 5.0.0-27.28 -proposed tracker (LP: #1840816) * [Potential Regression] System crashes when running ftrace test in ubuntu_kernel_selftests (LP: #1840750) - x86/kprobes: Set instruction page as executable -- Timo Aaltonen Thu, 22 Aug 2019 13:55:10 +0300 ** Changed in: linux-oem-osp1 (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/1714178 Title: Triple 4K monitor display failed (modesetting driver limited to 8192x8192) Status in DRI: Fix Released Status in HWE Next: New Status in X.Org X server: Unknown Status in linux package in Ubuntu: Triaged Status in linux-oem-osp1 package in Ubuntu: New Status in mesa package in Ubuntu: Fix Released Status in xorg-server package in Ubuntu: Invalid Status in linux source package in Bionic: Confirmed Status in linux-oem-osp1 source package in Bionic: Fix Released Status in mesa source package in Bionic: Fix Released Status in xorg-server source package in Bionic: Invalid Bug description: Title: Triple monitor display failed with Dell Dock (HiDPI) (modesetting) Summary: Triple monitor display failed with Dell Dock (HiDPI) (modesetting) Steps: 1. a laptop with Built-in 4K LCD 2. Cold boot system with Dell Dock connected 3. Connect a 4K monitor to Dock 4. Connect 2nd 4K monitor to Dock 5. Go to [All Settings]=>[Displays] to have the following configuration. Resolution: 4kx2k@60Hz (one Built-in LCD + two external monitors) Mirror displays: disable Expected results: Triple monitor display should works without issues Actual results: Triple monitor display failed with Dell Dock Additional information: 1. Linux distribution: Ubuntu 16.04+modesetting, 16.04.3, and 17.04 2. Laptop: Dell Precision 5520 3. Dell Business Thunderbolt Dock - TB16 https://goo.gl/vFDjpi WORKAROUND (UBUNTU 18.04+): Log in to "Ubuntu on Wayland" instead of "Ubuntu". --- .tmp.unity_support_test.0: ApportVersion: 2.20.1-0ubuntu2.10 Architecture: amd64 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: compiz CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0' CompositorUnredirectFSW: true CurrentDesktop: Unity DistUpgraded: Fresh install DistributionChannelDescriptor: # This is a distribution channel descriptor # For more information see http://wiki.ubuntu.com/DistributionChannelDescriptor canonical-oem-somerville-xenial-amd64-20160624-2 DistroCodename: xenial DistroRelease: Ubuntu 16.04 DistroVariant: ubuntu ExtraDebuggingInterest: Yes GraphicsCard: Intel Corporation Device [8086:591d] (rev 04) (prog-if 00 [VGA controller]) Subsystem: Dell Device [1028:07bf] Subsystem: Dell Device [1028:07bf] InstallationDate: Installed on 2017-08-29 (2 days ago) InstallationMedia: Ubuntu 16.04 "Xenial" - Build amd64 LIVE Binary 20160624-10:47 MachineType: Dell Inc. Precision 5520 Package: xorg-server (not installed) ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.11.0-14-generic.efi.signed root=UUID=b79ae801-0652-4785-beaf-e8387d798948 ro acpi_rev_override quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 4.11.0-14.20~16.04.1-generic 4.11.12 Tags: xenial ubuntu compiz-0.9 Uname: Linux 4.11.0-14-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 05/08/2017 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.3.3 dmi.board.vendor: Dell Inc. dmi.chassis.type: 10 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr1.3.3:bd05/08/2017:svnDellInc.:pnPrecision5520:pvr:rvnDellInc.:rn:rvr:cvnDellInc.:ct10:cvr: dmi.product.name: Precision 5520 dmi.sys.vendor: Dell Inc. version.compiz: compiz 1:0.9.12.2+16.04.20160823-0ubuntu1 version.ia32-libs: ia32-libs N/A version.libdrm2: libdrm2 2.4.76-1~ubuntu16.04.1 version.libgl1-mesa-dri: libgl1-mesa-dri 17.0.7-0ubuntu0.16.04.1 version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A version.libgl1-mesa-glx: libgl1-mesa-glx 17.0.7-0ubuntu0.16.04.1 version.xserver-xorg-core: xserver-xorg-core 2:1.18.4-0ubuntu0.3 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.10.1-1ubuntu2 version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.7.0-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20160325-1ubuntu1.2 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.12-1build2 To manage notification
[Touch-packages] [Bug 1494897] Re: various apps abort on assertion - g_file_monitor_source_handle_event: code should not be reached
Launchpad has imported 19 comments from the remote bug at
https://bugzilla.gnome.org/show_bug.cgi?id=776147.
If you reply to an imported comment from within Launchpad, your comment
will be sent to the remote bug automatically. Read more about
Launchpad's inter-bugtracker facilities at
https://help.launchpad.net/InterBugTracking.
On 2016-12-15T18:58:19+00:00 aaronfranke wrote:
Line 430 of gio/glocalfilemonitor.c doesn't handle case
G_FILE_MONITOR_EVENT_MOVED, crashing many programs.
The list of programs affected includes but is not limited to:
xfdesktop
https://bugs.launchpad.net/ubuntu/+source/xfdesktop4/+bug/1598360
pcmanfm https://bugs.launchpad.net/ubuntu/+source/pcmanfm/+bug/1598488
and caja https://bugs.launchpad.net/ubuntu/+source/caja/+bug/1598359
The affected code can be found at
https://github.com/GNOME/glib/blob/master/gio/glocalfilemonitor.c and
looks like this:
switch (event_type)
{
(other conditions are located here)
case G_FILE_MONITOR_EVENT_MOVED:
/* was never available in this API */
default:
g_assert_not_reached ();
}
This matches with the g_assertion_message() crash that these programs
are experiencing. So, I think we've found the culprit, and the solution
would be to do something to handle case G_FILE_MONITOR_EVENT_MOVED so
that these programs do not crash. Alternatively, if this API function
should never be used, then the maintainers of these programs should be
notified of this easily reproducible bug and be shown how to fix it.
Right now, many packages that come default on major distros such as
Ubuntu flavors are completely broken.
Reply at:
https://bugs.launchpad.net/ubuntu/+source/glib2.0/+bug/1494897/comments/7
On 2017-11-10T01:22:55+00:00 Bugzilla-tecnocode wrote:
*** Bug 790148 has been marked as a duplicate of this bug. ***
Reply at:
https://bugs.launchpad.net/ubuntu/+source/glib2.0/+bug/1494897/comments/10
On 2017-11-10T01:35:07+00:00 Robert Ayrapetyan wrote:
Why not to move:
case G_FILE_MONITOR_EVENT_MOVED:
under:
case G_FILE_MONITOR_EVENT_RENAMED:
so they will handle same way (because they are *almost* same right?).
G_FILE_MONITOR_EVENT_RENAMED branch even operates with names like
"G_FILE_MONITOR_WATCH_MOVES" and "G_FILE_MONITOR_SEND_MOVED" internally.
Apparently "was never available in this API" is not true because of the
list of affected apps.
Reply at:
https://bugs.launchpad.net/ubuntu/+source/glib2.0/+bug/1494897/comments/11
On 2017-11-10T15:12:26+00:00 Bugzilla-tecnocode wrote:
Created attachment 363349
kqueue: Fix invalid emission of G_FILE_MONITOR_EVENT_MOVED event
That event is deprecated, and the kqueue backend can’t provide enough
information to go alongside the event (i.e. the name of the new file).
Use G_FILE_MONITOR_EVENT_DELETED instead.
Quite disappointed in the kqueue documentation for this: I cannot find a
single piece of documentation or example about how NOTE_RENAME is
supposed to communicate the new name of the file.
If it turns out that this is possible, the code can be amended again in
future. At least now it doesn’t abort.
Signed-off-by: Philip Withnall
Reply at:
https://bugs.launchpad.net/ubuntu/+source/glib2.0/+bug/1494897/comments/12
On 2017-11-10T15:29:14+00:00 Bugzilla-tecnocode wrote:
(In reply to Robert from comment #2)
> Why not to move:
> case G_FILE_MONITOR_EVENT_MOVED:
>
> under:
> case G_FILE_MONITOR_EVENT_RENAMED:
>
> so they will handle same way (because they are *almost* same right?).
> G_FILE_MONITOR_EVENT_RENAMED branch even operates with names like
> "G_FILE_MONITOR_WATCH_MOVES" and "G_FILE_MONITOR_SEND_MOVED" internally.
Because that would be fixing the symptom of the problem, rather than the
underlying cause. This problem hasn’t been fixed already because
nobody’s found time to investigate it yet.
> Apparently "was never available in this API" is not true because of the list
> of affected apps.
I just spent a bit of time looking into it, and it seems this is caused
by the kqueue backend sending through an invalid event. I’ve attached a
patch for that.
If you weren’t using FreeBSD (or another system which uses kqueue, like
OS X), please let me know. There’s a potential bug in the inotify
backend where a -1 return value from ih_mask_to_EventFlags() can be
passed through to g_file_monitor_source_handle_event(), but I’m not 100%
sure that’s possible due to other checks beforehand.
Reply at:
https://bugs.launchpad.net/ubuntu/+source/glib2.0/+bug/1494897/comments/13
On 2017-11-10T15:49:29+00:00 Robert Ayrapetyan wrote:
Hm, I thou
[Touch-packages] [Bug 1624317] Re: systemd-resolved breaks VPN with split-horizon DNS
Launchpad has imported 28 comments from the remote bug at https://bugzilla.gnome.org/show_bug.cgi?id=783569. If you reply to an imported comment from within Launchpad, your comment will be sent to the remote bug automatically. Read more about Launchpad's inter-bugtracker facilities at https://help.launchpad.net/InterBugTracking. On 2017-06-08T19:17:14+00:00 Nicholas Stommel wrote: Created attachment 353426 fixes DNS leaks over some NM-VPN connections using systemd-resolved I have patched the Network Manager to fix DNS leaks over network-manger VPN links (like those created with network-manager-openvpn) when using systemd-resolved as the default dns-manger/resolver on Ubuntu. This addresses some critical security concerns with DNS leaks over NM-VPN links. Please see the following high-priority bug at launchpad: https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1624317 There, I attached a patch for the current version of the network manager on Ubuntu 17.04 (1.4.4-1ubuntu3 zesty). Per request of kai.heng.f...@canonical.com on launchpad, I have patched the latest upstream source, made sure that it compiles correctly without warnings, and attached it here. So far, this is known to solve DNS leaks with network-manager-openvpn but could also solve DNS leaks for other VPNs that use TUN, TAP, or Cisco GRE network interfaces through the network-manager. It would be great to backport this fix to the current Ubuntu distribution! Reply at: https://bugs.launchpad.net/network- manager/+bug/1624317/comments/75 On 2017-06-09T07:51:45+00:00 Thomas Haller wrote: there is ipv4.dns-priority setting Quoting `man nm-settings`: "Intra-connection DNS priority. The relative priority to be used when determining the order of DNS servers in resolv.conf. A lower value means that servers will be on top of the file. Zero selects the default value, which is 50 for VPNs and 100 for other connections. Note that the priority is to order DNS settings for multiple active connections. It does not disambiguate multiple DNS servers within the same connection profile. For that, just specify the DNS servers in the desired order. When multiple devices have configurations with the same priority, the one with an active default route will be preferred. Note that when using dns=dnsmasq the order is meaningless since dnsmasq forwards queries to all known servers at the same time. Negative values have the special effect of excluding other configurations with a greater priority value; so in presence of at least a negative priority, only DNS servers from connections with the lowest priority value will be used." Why is that not the right solution? Reply at: https://bugs.launchpad.net/network- manager/+bug/1624317/comments/77 On 2017-06-09T08:07:38+00:00 Bgalvani wrote: Hi, in addition to what Thomas said, I think it is wrong to assume the connection is a VPN based on the link type, since you can have non-VPN tun/tap/gre/gretap connections as well, and they are affected by this patch. Also, it seems to me that commit [1] should already fix the leak for VPNs that don't get the default route... did you try if git master of NM is still affected by this bug? If it is, can you please attach the output of 'nmcli connection show ' for the VPN, and the output of 'systemd-resolve --status'? I mean, without your patch, to verify why the existing commit is not working. Thanks! [1] https://cgit.freedesktop.org/NetworkManager/NetworkManager/commit/?id=c4864ba63f4a13e9938a978787490005f5ba48fb Reply at: https://bugs.launchpad.net/network- manager/+bug/1624317/comments/78 On 2017-06-09T16:30:24+00:00 Nicholas Stommel wrote: Oh, sorry I didn't think of that :/ I suppose that commit is a better fix. I'll see if that works instead. Reply at: https://bugs.launchpad.net/network- manager/+bug/1624317/comments/79 On 2017-06-09T21:07:27+00:00 Nicholas Stommel wrote: Created attachment 353487 current version of nm-systemd-resolved.c in Ubuntu network manager Wait...that commit from [1] is already found in the zesty version of network-manager 1.4.4-1ubuntu3. See attachment. This suggests that if this is still an issue on Ubuntu 17.04, the problem is still present and unsolved. [1] https://cgit.freedesktop.org/NetworkManager/NetworkManager/commit/?id=c4864ba63f4a13e9938a978787490005f5ba48fb Reply at: https://bugs.launchpad.net/network- manager/+bug/1624317/comments/81 On 2017-06-09T21:58:24+00:00 Nicholas Stommel wrote: So the issue persists I believe. Unfortunately I just broke totally broke my ins
[Touch-packages] [Bug 1833536] Re: QuiteRSS crashes intermittently
This bug was fixed in the package qtbase-opensource-src - 5.9.5+dfsg- 0ubuntu2.3 --- qtbase-opensource-src (5.9.5+dfsg-0ubuntu2.3) bionic; urgency=medium * Backport upstream patch to fix nullptr dereference in HTTP handler (LP: #1833536). qtbase-opensource-src (5.9.5+dfsg-0ubuntu2.2) bionic; urgency=medium * Backport two upstream patches to support legacy X11 keymaps (LP: #1831505). -- Dmitry Shachnev Thu, 20 Jun 2019 13:59:52 +0300 ** Changed in: qtbase-opensource-src (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 qtbase-opensource-src in Ubuntu. https://bugs.launchpad.net/bugs/1833536 Title: QuiteRSS crashes intermittently Status in qtbase-opensource-src package in Ubuntu: Fix Released Status in qtbase-opensource-src source package in Bionic: Fix Released Status in qtbase-opensource-src source package in Disco: Fix Released Bug description: [Impact] This bug affects QuiteRSS and other Qt applications, like plasma-discover (see https://bugs.kde.org/show_bug.cgi?id=402848) and qbittorrent (see bug 1814375). All they crash with similar stack traces. [Test Case] 1. Open QuiteRSS. 2. Leave it running for several hours. 3. It should not crash. [Proposed Fix] The proposed fix is a backport of the following commit from upstream 5.12 branch: https://code.qt.io/cgit/qt/qtbase.git/commit/?id=e431a3ac027915db [Regression Potential] This patch adds an additional check before re-sending the request. Regressions chance is minimal, but the potential regressions may be that the request is not re-sent where it was re-sent with the previous code. [Original Description] After opening QuiteRSS it will run until crash happens. This happens intermittently within the hour usually. (gdb) bt #0 QHttpNetworkConnectionChannel::sendRequest (this=) at access/qhttpnetworkconnectionchannel.cpp:238 #1 0x730deca2 in QHttpNetworkConnectionPrivate::_q_startNextRequest ( this=0x7fff480d4a20) at access/qhttpnetworkconnection.cpp:1015 #2 0x72736122 in QObject::event (this=0x7fff48da89b0, e=) at kernel/qobject.cpp:1247 #3 0x76f2482c in QApplicationPrivate::notify_helper(QObject*, QEvent*) () from /usr/lib/x86_64-linux-gnu/libQt5Widgets.so.5 #4 0x76f2c0f4 in QApplication::notify(QObject*, QEvent*) () from /usr/lib/x86_64-linux-gnu/libQt5Widgets.so.5 #5 0x727069a8 in QCoreApplication::notifyInternal2 ( receiver=0x7fff48da89b0, event=event@entry=0x7fff494233b0) at kernel/qcoreapplication.cpp:1024 #6 0x7270911d in QCoreApplication::sendEvent (event=0x7fff494233b0, receiver=) at ../../include/QtCore/../../src/corelib/kernel/qcoreapplication.h:233 #7 QCoreApplicationPrivate::sendPostedEvents (receiver=receiver@entry=0x0, event_type=event_type@entry=0, data=0x7fff60008e90) at kernel/qcoreapplication.cpp:1699 #8 0x727096a8 in QCoreApplication::sendPostedEvents ( receiver=receiver@entry=0x0, event_type=event_type@entry=0) at kernel/qcoreapplication.cpp:1553 #9 0x727602c3 in postEventSourceDispatch (s=0x7fff48003f10) at kernel/qeventdispatcher_glib.cpp:276 #10 0x7fffece96317 in g_main_context_dispatch () from /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0 #11 0x7fffece96550 in ?? () from /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0 #12 0x7fffece965dc in g_main_context_iteration () from /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0 #13 0x7275f8ef in QEventDispatcherGlib::processEvents ( this=0x7fff48000b20, flags=...) at kernel/qeventdispatcher_glib.cpp:423 #14 0x727049ea in QEventLoop::exec (this=this@entry=0x7fff4fffec60, flags=..., flags@entry=...) at kernel/qeventloop.cpp:212 #15 0x7252322a in QThread::exec (this=) at thread/qthread.cpp:515 #16 0x7252816d in QThreadPrivate::start (arg=0x7fff60008a20) at thread/qthread_unix.cpp:368 #17 0x722646db in start_thread (arg=0x7fff4700) at pthread_create.c:463 #18 0x719ec88f in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:95 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/qtbase-opensource-src/+bug/1833536/+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 1831505] Re: Qt5 incorrectly interpret keypresses from remote VNC keyboard
This bug was fixed in the package qtbase-opensource-src - 5.9.5+dfsg- 0ubuntu2.3 --- qtbase-opensource-src (5.9.5+dfsg-0ubuntu2.3) bionic; urgency=medium * Backport upstream patch to fix nullptr dereference in HTTP handler (LP: #1833536). qtbase-opensource-src (5.9.5+dfsg-0ubuntu2.2) bionic; urgency=medium * Backport two upstream patches to support legacy X11 keymaps (LP: #1831505). -- Dmitry Shachnev Thu, 20 Jun 2019 13:59:52 +0300 ** Changed in: qtbase-opensource-src (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 qtbase-opensource-src in Ubuntu. https://bugs.launchpad.net/bugs/1831505 Title: Qt5 incorrectly interpret keypresses from remote VNC keyboard Status in qtbase-opensource-src package in Ubuntu: Fix Released Status in qtbase-opensource-src source package in Bionic: Fix Released Status in qtbase-opensource-src package in Debian: Fix Released Bug description: [Impact] Qt applications incorrectly interpret keyboard input when running over some VNC clients such as TightVNC. [Test Case] 1. Have Ubuntu 18.04 LTS installed with VNC server 2. Connect to Ubuntu 18.04 LTS from other machine with VNC client 3. Launch any Qt5 based application such as `assistant`, `kate` or `retext` 4. Press keyboard combination on VNC client Expected results: all keypresses are recognized successfully Actual results: * produces `1` * produces `5` * <`> produces `p` * and are not working * all letters are messed [Proposed Fix] The proposed fix is a backport of two upstream commits: the second being the actual fix, the first one is some refactoring of the code to make it easier to write the second. The commits are: - https://code.qt.io/cgit/qt/qtbase.git/commit/?id=f8b164e1c37ca901 - https://code.qt.io/cgit/qt/qtbase.git/commit/?id=3edcd9420e3ad661 [Regression Potential] Most of the new code is triggered only when the keymap is missing rules, models, or layout (i.e. rmlvo_is_incomplete == true). This minimizes the risk of regressions when working with simple X11 server. In any case, the potential regressions will be related to input handling. [Other Info] Note: only Qt applications are affected, the GTK-based work as expected (including Chromium from which I write this bug-report) ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: qt5-assistant 5.9.5-0ubuntu1 Uname: Linux 4.4.78-perf+ aarch64 NonfreeKernelModules: wlan exfat ApportVersion: 2.20.9-0ubuntu7 Architecture: armhf CurrentDesktop: MATE Date: Tue Jun 4 00:46:55 2019 ProcEnviron: TERM=xterm PATH=(custom, no user) LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: qttools-opensource-src UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/qtbase-opensource-src/+bug/1831505/+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 1831505] Update Released
The verification of the Stable Release Update for qtbase-opensource-src has completed successfully and the package has now been 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 qtbase-opensource-src in Ubuntu. https://bugs.launchpad.net/bugs/1831505 Title: Qt5 incorrectly interpret keypresses from remote VNC keyboard Status in qtbase-opensource-src package in Ubuntu: Fix Released Status in qtbase-opensource-src source package in Bionic: Fix Released Status in qtbase-opensource-src package in Debian: Fix Released Bug description: [Impact] Qt applications incorrectly interpret keyboard input when running over some VNC clients such as TightVNC. [Test Case] 1. Have Ubuntu 18.04 LTS installed with VNC server 2. Connect to Ubuntu 18.04 LTS from other machine with VNC client 3. Launch any Qt5 based application such as `assistant`, `kate` or `retext` 4. Press keyboard combination on VNC client Expected results: all keypresses are recognized successfully Actual results: * produces `1` * produces `5` * <`> produces `p` * and are not working * all letters are messed [Proposed Fix] The proposed fix is a backport of two upstream commits: the second being the actual fix, the first one is some refactoring of the code to make it easier to write the second. The commits are: - https://code.qt.io/cgit/qt/qtbase.git/commit/?id=f8b164e1c37ca901 - https://code.qt.io/cgit/qt/qtbase.git/commit/?id=3edcd9420e3ad661 [Regression Potential] Most of the new code is triggered only when the keymap is missing rules, models, or layout (i.e. rmlvo_is_incomplete == true). This minimizes the risk of regressions when working with simple X11 server. In any case, the potential regressions will be related to input handling. [Other Info] Note: only Qt applications are affected, the GTK-based work as expected (including Chromium from which I write this bug-report) ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: qt5-assistant 5.9.5-0ubuntu1 Uname: Linux 4.4.78-perf+ aarch64 NonfreeKernelModules: wlan exfat ApportVersion: 2.20.9-0ubuntu7 Architecture: armhf CurrentDesktop: MATE Date: Tue Jun 4 00:46:55 2019 ProcEnviron: TERM=xterm PATH=(custom, no user) LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: qttools-opensource-src UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/qtbase-opensource-src/+bug/1831505/+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 1837443] Re: [Power9][Witherspoon dd2.3] unable to set hwclock
Thanks to Dimitri for pointing out that the comment #2 is not designed to actually SET the HW Clock from the host, but to ALLOW the HW Clock to be set with /sbin/hwclock. I had completely missed this. Next step is to try the sequence described in comment #2 (on the BMC and also on the host), and then retry using /sbin/hwclock on the host to change the HW clock time. ** Changed in: ubuntu-power-systems Status: Triaged => In Progress -- 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/1837443 Title: [Power9][Witherspoon dd2.3] unable to set hwclock Status in The Ubuntu-power-systems project: In Progress Status in util-linux package in Ubuntu: New Bug description: On the upgraded witherspoon Power9 system we are unable to set hwclock. ubuntu@bobone:~$ uname -a Linux bobone 5.0.0-20-generic #21-Ubuntu SMP Mon Jun 24 09:31:42 UTC 2019 ppc64le ppc64le ppc64le GNU/Linux ubuntu@bobone:~$ cat /etc/issue Ubuntu 19.04 \n \l ubuntu@bobone:~$ date Mon Jul 22 18:25:04 UTC 2019 ubuntu@bobone:~$ sudo /sbin/hwclock --set --date "2004/11/22 04:10:00"; sleep 5s; sudo /sbin/hwclock 2019-07-22 18:25:26.799805+00:00 ubuntu@bobone:~$ ubuntu@bobone:~$ sudo /sbin/hwclock --set --date "2004/11/22 04:10:00"; sleep 5s; sudo /sbin/hwclock --verbose hwclock from util-linux 2.33.1 System Time: 1563820048.938797 Trying to open: /dev/rtc0 Using the rtc interface to the clock. Last drift adjustment done at 1101096600 seconds after 1969 Last calibration done at 1101096600 seconds after 1969 Hardware clock is on UTC time Assuming hardware clock is kept in UTC time. Waiting for clock tick... ioctl(4, RTC_UIE_ON, 0): Invalid argument Waiting in loop for time from /dev/rtc0 to change ...got clock tick Time read from Hardware Clock: 2019/07/22 18:27:29 Hw clock time : 2019/07/22 18:27:29 = 1563820049 seconds since 1969 Time since last adjustment is 462723449 seconds Calculated Hardware Clock drift is 0.00 seconds 2019-07-22 18:27:28.877732+00:00 ubuntu@bobone:~$ To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-power-systems/+bug/1837443/+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 1837926] Re: snapd snap ftbfs in eoan due to python-apt regression
python-apt is fixed, and actually snapd will stay on xenial for now. ** Changed in: snapd (Ubuntu Eoan) Status: New => Fix Released ** Changed in: snapd (Ubuntu Eoan) Status: Fix Released => Invalid -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to python-apt in Ubuntu. https://bugs.launchpad.net/bugs/1837926 Title: snapd snap ftbfs in eoan due to python-apt regression Status in python-apt package in Ubuntu: Fix Released Status in snapd package in Ubuntu: Invalid Status in python-apt source package in Eoan: Fix Released Status in snapd source package in Eoan: Invalid Bug description: snapd snap FTBFS in launchpad snap build due to python-apt regression in eoan https://launchpad.net/~xnox/+snap/snapd/+build/626157 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/python-apt/+bug/1837926/+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 1840699] Re: Caps-lock doesn't work correctly in Old Hungarian layout
** Changed in: xkeyboard-config Status: Unknown => Fix Released -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to xkeyboard-config in Ubuntu. https://bugs.launchpad.net/bugs/1840699 Title: Caps-lock doesn't work correctly in Old Hungarian layout Status in xkeyboard-config: Fix Released Status in xkeyboard-config package in Ubuntu: In Progress Bug description: Xkeyboard-config's version 2.27 resolves this problem To manage notifications about this bug go to: https://bugs.launchpad.net/xkeyboard-config/+bug/1840699/+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 1835521] Re: [regression] Windows flicker to black when resizing (Intel Apollo Lake)
** Changed in: mutter Status: Unknown => New -- 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/1835521 Title: [regression] Windows flicker to black when resizing (Intel Apollo Lake) Status in Mutter: New Status in gnome-shell package in Ubuntu: New Status in mesa package in Ubuntu: New Status in mutter package in Ubuntu: New Bug description: I see the black zones, small windows breaks. For additional details, I use eoan-proposed and eoan-backports packages. You can see this problem in my video: https://photos.app.goo.gl/3rvLkqJj6hZwSscw9 ProblemType: Bug DistroRelease: Ubuntu 19.10 Package: gnome-shell 3.32.2-2ubuntu1 ProcVersionSignature: Ubuntu 5.0.0-20.21-generic 5.0.8 Uname: Linux 5.0.0-20-generic x86_64 ApportVersion: 2.20.11-0ubuntu3 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Fri Jul 5 13:39:13 2019 DisplayManager: gdm3 InstallationDate: Installed on 2019-07-01 (3 days ago) InstallationMedia: ProcEnviron: LANGUAGE=ru_UA:ru PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=ru_UA.UTF-8 SHELL=/bin/bash RelatedPackageVersions: mutter-common 3.32.2+git20190626-1ubuntu1 SourcePackage: gnome-shell UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/mutter/+bug/1835521/+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 1828134] Re: Wifi not working after suspend/resume cycle
** Changed in: network-manager Status: Unknown => New -- 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/1828134 Title: Wifi not working after suspend/resume cycle Status in NetworkManager: New Status in linux package in Ubuntu: Confirmed Status in network-manager package in Ubuntu: New Bug description: About 75% of the time for the past few weeks (I don't have a time where this started), my wifi is not working after resume from suspend. I'm happy to provide more debugging info if needed. I have tried an rmmod/modprobe on on the iwlwifi,iwlmvm modules just to see after the resume, and didn't re-enable the card. The symptoms are, the wlp4so interface is DOWN, I can't bring it up. gnome-network-manager widget turning the interface off/on doesn't work. I don't see anything glaring in dmesg. ProblemType: Bug DistroRelease: Ubuntu 19.04 Package: linux-image-generic 5.0.0.14.15 ProcVersionSignature: Ubuntu 5.0.0-14.15-generic 5.0.6 Uname: Linux 5.0.0-14-generic x86_64 ApportVersion: 2.20.10-0ubuntu27 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: dpb4587 F pulseaudio CurrentDesktop: ubuntu:GNOME Date: Tue May 7 18:49:01 2019 InstallationDate: Installed on 2018-06-18 (323 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426) MachineType: LENOVO 20HRCTO1WW ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.0.0-14-generic root=UUID=fa64d67d-26bf-4c42-a12f-c45b6ea5117c ro quiet splash vt.handoff=1 RelatedPackageVersions: linux-restricted-modules-5.0.0-14-generic N/A linux-backports-modules-5.0.0-14-generic N/A linux-firmware1.178 SourcePackage: linux UpgradeStatus: Upgraded to disco on 2019-03-15 (53 days ago) dmi.bios.date: 02/14/2019 dmi.bios.vendor: LENOVO dmi.bios.version: N1MET52W(1.37) dmi.board.asset.tag: Not Available dmi.board.name: 20HRCTO1WW dmi.board.vendor: LENOVO dmi.board.version: Not Defined dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: None dmi.modalias: dmi:bvnLENOVO:bvrN1MET52W(1.37):bd02/14/2019:svnLENOVO:pn20HRCTO1WW:pvrThinkPadX1Carbon5th:rvnLENOVO:rn20HRCTO1WW:rvrNotDefined:cvnLENOVO:ct10:cvrNone: dmi.product.family: ThinkPad X1 Carbon 5th dmi.product.name: 20HRCTO1WW dmi.product.sku: LENOVO_MT_20HR_BU_Think_FM_ThinkPad X1 Carbon 5th dmi.product.version: ThinkPad X1 Carbon 5th dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/network-manager/+bug/1828134/+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 1726129] Re: nautilus crashed with SIGSEGV in widget_needs_widget_path
** Changed in: nautilus Status: Unknown => New -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to gtk+3.0 in Ubuntu. https://bugs.launchpad.net/bugs/1726129 Title: nautilus crashed with SIGSEGV in widget_needs_widget_path Status in Nautilus: New Status in gtk+3.0 package in Ubuntu: New Status in nautilus package in Ubuntu: Triaged Bug description: https://gitlab.gnome.org/GNOME/nautilus/issues/1190 --- https://errors.ubuntu.com/problem/7c06cf06fd970ce31033f0d775b3adf97559e4ea ProblemType: Crash DistroRelease: Ubuntu 17.10 Package: nautilus 1:3.26.0-0ubuntu1 ProcVersionSignature: Ubuntu 4.13.0-16.19-generic 4.13.4 Uname: Linux 4.13.0-16-generic x86_64 ApportVersion: 2.20.7-0ubuntu3 Architecture: amd64 CrashCounter: 1 CurrentDesktop: Budgie:GNOME Date: Sun Oct 22 15:30:05 2017 ExecutablePath: /usr/bin/nautilus InstallationDate: Installed on 2017-10-19 (3 days ago) InstallationMedia: Ubuntu-Budgie 17.10 "Artful Aardvark" - Release amd64 (20171017.1) ProcCmdline: nautilus --new-window ProcEnviron: LANGUAGE=en_US PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SegvAnalysis: Segfault happened at: 0x7fe0115bd2a4:mov0x380(%rax),%rax PC (0x7fe0115bd2a4) ok source "0x380(%rax)" (0x0380) not located in a known VMA region (needed readable region)! destination "%rax" ok SegvReason: reading NULL VMA Signal: 11 SourcePackage: nautilus StacktraceTop: ?? () from /usr/lib/x86_64-linux-gnu/libgtk-3.so.0 ?? () from /usr/lib/x86_64-linux-gnu/libgtk-3.so.0 ?? () from /usr/lib/x86_64-linux-gnu/libgtk-3.so.0 ?? () from /usr/lib/x86_64-linux-gnu/libgtk-3.so.0 ?? () from /usr/lib/x86_64-linux-gnu/libgtk-3.so.0 Title: nautilus crashed with SIGSEGV UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo To manage notifications about this bug go to: https://bugs.launchpad.net/nautilus/+bug/1726129/+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 1841654] Re: Consider replacing mawk with gawk in main
Updated the description to include links to your current snapshots.
Sorry for not finding them in the first place.
** Description changed:
For POSIX compatibility reasons Ubuntu ships with mawk ("Mike's awk" =
mawk) in main. There is an awk-symlink to mawk, thus mawk is the
official awk implementation in Ubuntu.
== Reasons against keeping mawk ==
*The mawk package is synced from debian and it is heavily
undermaintained: Debian (and thus Ubuntu) still ships version 1.3.3-17,
the same version at least since oldoldstable:
https://packages.debian.org/search?searchon=names&keywords=mawk
*maintainer Thomas E. Dickey (https://invisible-island.net/mawk/) called
officially out that Debian "neglected" mawk in 2014 ("As noted, mawk has
been neglected by some packagers (see for example this
http://bugs.debian.org/cgi-bin/pkgreport.cgi?package=mawk)". And Debian
(and Ubuntu) still ship the same version five years later
*Most other distributions ship mawk at least in its last official
incarnation 1.3.4 in their repositories. Dickey lists AIX, Fedora,
FinkPorts (Mac OS X), FreeBSD port, Gentoo, HPUX, MacPorts (Mac OS X),
- NetBSD pkgsrc/lang, OpenCSW (Solaris). That version is from 2014 and at
- first it looked like it wasn't developed anymore:
- https://github.com/ThomasDickey/mawk-20140914/commits/master A recent
- comment by Thomas Dickey below indicates that he is still maintaining
- mawk.
+ NetBSD pkgsrc/lang, OpenCSW (Solaris). That version is from 2014 but
+ updated snapshots are released in regular intervals. The current
+ snapshot is from February 2019: https://github.com/ThomasDickey/mawk-
+ snapshots/blob/ab13a164013940e90c0b1ad36a039feae06a0b65/CHANGES
*A planned rewrite mawk2 was planned by original author Mike Brennan in
2016 but obviously came to nothing:
https://github.com/ploxiln/mawk-2/commits/master
*Thus mawk sits in Ubuntu main in a version published upstream in 2009
and celebrates its 10th anniversary of negligence. In a state that
Debian was called out for 5 years ago.
*This year it is 10 years unmaintained and largely untouched. At the end
of the next LTS-support-cycle we can celebrate 15 years of not
supporting it.
*awk is included in Linux for POSIX standard compliance. Mawk is known
to be fast and small but it is the implementation that is farthest from
being POSIX compliant, missing things like named character classes like
[[:space:]] within its EREs.
== Reasons for gawk as a replacement ==
*It is the official GNU awk implementation and known to work well with
the rest of the GNU userland.
*It is actively maintained with the last version 5.01 shipping in June,
2019 (even if Ubuntu will obviously still ship 4.2 for Eoan).
*It is mostly compliant with the POSIX standard.
*Most other distributions ship it as the standard POSIX implementation,
with a awk symlink. So it had security reviews already by Red Hat and
others.
== Possible problems with switching to gawk in time for Ubuntu 20.4 ==
- It might need to be MIRed by the Ubuntu security team and a review
might take some time. So I filed this bug early with Eoan not yet out of
the door.
- It is much larger than mawk, the Ubuntu package is 1600 kB in size,
while mawk is only about 190KB. Thus some might want to split out some
basic functionality to save size. Like what is vim-tiny to vim. To start
gawk in --traditional or --posix mode and disable the extensions at
compile time might be a good start to reduce the size. See:
https://www.gnu.org/software/gawk/manual/html_node/Additional-
Configuration-Options.html#Additional-Configuration-Options
=
ProblemType: Bug
DistroRelease: Ubuntu 19.04
Package: mawk 1.3.3-17ubuntu3
ProcVersionSignature: Ubuntu 5.0.0-27.28-generic 5.0.21
Uname: Linux 5.0.0-27-generic x86_64
ApportVersion: 2.20.10-0ubuntu27.1
Architecture: amd64
CurrentDesktop: ubuntu:GNOME
Date: Tue Aug 27 20:12:11 2019
Dependencies:
gcc-9-base 9.1.0-2ubuntu2~19.04
libc6 2.29-0ubuntu2
libgcc1 1:9.1.0-2ubuntu2~19.04
libidn2-0 2.0.5-1
libunistring2 0.9.10-1ubuntu2
InstallationDate: Installed on 2018-02-23 (550 days ago)
InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Alpha amd64 (20180214)
ProcEnviron:
LANGUAGE=de_AT:de
PATH=(custom, no user)
XDG_RUNTIME_DIR=
LANG=de_AT.UTF-8
SHELL=/bin/bash
SourcePackage: mawk
UpgradeStatus: No upgrade log present (probably fresh install)
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to mawk in Ubuntu.
https://bugs.launchpad.net/bugs/1841654
Title:
Consider replacing mawk with gawk in main
Status in mawk package in Ubuntu:
New
Bug description:
For POSIX compatibility reasons Ubuntu ships with mawk ("Mike's awk" =
mawk) in main. There is
[Touch-packages] [Bug 1576844] Re: Touchpad/Trackpad freezes then eventually unfreezes (repeatedly)
Same issue with Ubuntu 19.04 and Dell Latitude 5500. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to xorg in Ubuntu. https://bugs.launchpad.net/bugs/1576844 Title: Touchpad/Trackpad freezes then eventually unfreezes (repeatedly) Status in xorg package in Ubuntu: Confirmed Bug description: $ lsb_release -rd Description: Ubuntu 16.04 LTS Release: 16.04 Several times yesterday and today (April 28-29, 2016) the touchpad (trackpad) on the Dell XPS 13 9343 has frozen. Other functions (keyboard, screen, etc.) have been fine but the pointer has been frozen in place. Then after 1-3 minutes functionality returns. Thank you very much for your assistance and I'd be happy to provide more information. ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: xorg 1:7.7+13ubuntu3 ProcVersionSignature: Ubuntu 4.4.0-22.38-generic 4.4.8 Uname: Linux 4.4.0-22-generic x86_64 NonfreeKernelModules: wl .tmp.unity_support_test.0: ApportVersion: 2.20.1-0ubuntu2 Architecture: amd64 BootLog: CompizPlugins: [core,composite,opengl,cube,rotate] CompositorRunning: None CurrentDesktop: GNOME-Flashback:Unity Date: Fri Apr 29 16:09:32 2016 DistUpgraded: 2016-04-27 15:53:13,798 DEBUG icon theme changed, re-reading DistroCodename: xenial DistroVariant: ubuntu DkmsStatus: bcmwl, 6.30.223.248+bdcom, 4.2.0-36-generic, x86_64: installed bcmwl, 6.30.223.248+bdcom, 4.4.0-22-generic, x86_64: installed ExtraDebuggingInterest: Yes, if not too technical GraphicsCard: Intel Corporation Broadwell-U Integrated Graphics [8086:1616] (rev 09) (prog-if 00 [VGA controller]) Subsystem: Dell Broadwell-U Integrated Graphics [1028:0665] InstallationDate: Installed on 2015-08-06 (267 days ago) InstallationMedia: Ubuntu 15.04 "Vivid Vervet" - Release amd64 (20150422) MachineType: Dell Inc. XPS 13 9343 ProcEnviron: LANGUAGE=en_US PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.4.0-22-generic root=/dev/mapper/ubuntu--vg-root ro quiet splash vt.handoff=7 SourcePackage: xorg UpgradeStatus: Upgraded to xenial on 2016-04-27 (2 days ago) dmi.bios.date: 07/14/2015 dmi.bios.vendor: Dell Inc. dmi.bios.version: A05 dmi.board.name: 0TM99H dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 9 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvrA05:bd07/14/2015:svnDellInc.:pnXPS139343:pvr:rvnDellInc.:rn0TM99H:rvrA00:cvnDellInc.:ct9:cvr: dmi.product.name: XPS 13 9343 dmi.sys.vendor: Dell Inc. version.compiz: compiz 1:0.9.12.2+16.04.20160415-0ubuntu1 version.ia32-libs: ia32-libs N/A version.libdrm2: libdrm2 2.4.67-1 version.libgl1-mesa-dri: libgl1-mesa-dri 11.2.0-1ubuntu2 version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A version.libgl1-mesa-glx: libgl1-mesa-glx 11.2.0-1ubuntu2 version.xserver-xorg-core: xserver-xorg-core 2:1.18.3-1ubuntu2 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.10.1-1ubuntu2 version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.7.0-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20160325-1ubuntu1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.12-1build2 xserver.bootTime: Wed Apr 27 15:54:22 2016 xserver.configfile: default xserver.logfile: /var/log/Xorg.0.log xserver.outputs: product id5152 vendor SHP xserver.version: 2:1.18.3-1ubuntu2 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1576844/+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 1592514] Re: 3G usb Card - mmcli and network manager broken compatibility
Unbelieveable, but this bug still exists! I have the Compaq Mini 700, which has the Qualcommm Gobi 1000 (which is sold from HP as the un2400 and has the MDM1000 chipset). It took until 18.04 until this network card could get activated under Linux at all, but due to this bug, it wasn't possible to get a connection up. Same error messages as posted before. I had to modify the script a bit, but it works like this (currently writing with a connection established by it): [code] #!/bin/bash mmcli -m 0 -b 0 --connect ifconfig wwan0 up mmcli -m 0 -b 0 dhclient -d wwan0 & echo "nameserver 8.8.8.8" >> /etc/resolv.conf [/code] -- 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/1592514 Title: 3G usb Card - mmcli and network manager broken compatibility Status in network-manager package in Ubuntu: Confirmed Bug description: This bug is specific to "ipv4 only" 3g providers Here is syslog Jun 14 19:26:12 Latitude-E5440 NetworkManager[758]: [1465928772.9535] device (cdc-wdm1): Activation: starting connection 'XXXx X / XXX XXX XXX' (1554021e-ff2e-44f9-8e2d-c16cae73bfe0) Jun 14 19:26:12 Latitude-E5440 NetworkManager[758]: [1465928772.9538] audit: op="connection-activate" uuid="1554021e-ff2e-44f9-8e2d-c16cae73bfe0" name="XXXx X / XXX XXX XXX" pid=1663 uid=1000 result="success" Jun 14 19:26:12 Latitude-E5440 NetworkManager[758]: [1465928772.9542] device (cdc-wdm1): state change: disconnected -> prepare (reason 'none') [30 40 0] Jun 14 19:26:12 Latitude-E5440 ModemManager[675]: Simple connect started... Jun 14 19:26:12 Latitude-E5440 ModemManager[675]: Simple connect state (4/8): Wait to get fully enabled Jun 14 19:26:12 Latitude-E5440 ModemManager[675]: Simple connect state (5/8): Register Jun 14 19:26:12 Latitude-E5440 ModemManager[675]: Simple connect state (6/8): Bearer Jun 14 19:26:12 Latitude-E5440 ModemManager[675]: Simple connect state (7/8): Connect Jun 14 19:26:12 Latitude-E5440 ModemManager[675]: Modem /org/freedesktop/ModemManager1/Modem/2: state changed (registered -> connecting) Jun 14 19:26:15 Latitude-E5440 ModemManager[675]: error: couldn't get current settings: Cannot send message: QMI service 'wds' version '1.2' required, got version '1.1' Jun 14 19:26:15 Latitude-E5440 ModemManager[675]: Modem /org/freedesktop/ModemManager1/Modem/2: state changed (connecting -> connected) Jun 14 19:26:15 Latitude-E5440 ModemManager[675]: Simple connect state (8/8): All done Jun 14 19:26:15 Latitude-E5440 NetworkManager[758]: [1465928775.2418] (cdc-wdm1): failed to connect modem: invalid bearer IP configuration Jun 14 19:26:15 Latitude-E5440 NetworkManager[758]: [1465928775.2419] device (cdc-wdm1): state change: prepare -> failed (reason 'config-failed') [40 120 4] Jun 14 19:26:15 Latitude-E5440 NetworkManager[758]: [1465928775.2421] policy: disabling autoconnect for connection 'Tunisie Télécom / TUNTEL WEB DATA'. Jun 14 19:26:15 Latitude-E5440 NetworkManager[758]: [1465928775.2423] device (cdc-wdm1): Activation: failed for connection 'Tunisie Télécom / TUNTEL WEB DATA' Jun 14 19:26:15 Latitude-E5440 NetworkManager[758]: [1465928775.2428] device (cdc-wdm1): state change: failed -> disconnected (reason 'none') [120 30 0] Jun 14 19:26:15 Latitude-E5440 ModemManager[675]: Modem /org/freedesktop/ModemManager1/Modem/2: state changed (connected -> disconnecting) Jun 14 19:26:15 Latitude-E5440 ModemManager[675]: Modem /org/freedesktop/ModemManager1/Modem/2: state changed (disconnecting -> registered) i managed to make it work using this shell script #!/bin/bash mmcli -m 0 -b $1 --connect ifconfig wwp0s29u1u8u3i3 up mmcli -m 0 -b $1 dhclient -d wwp0s29u1u8u3i3 & echo "nameserver 8.8.8.8" >> /etc/resolv.conf i also disabled ipv6 with gui To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1592514/+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 1756595] Re: disk space info inadvertently provides all installed snaps
** Description changed: - When apport is reporting a crash, it includes the output of the "df" - utility, to list the free disk space information per mount point. + [Impact] + When apport is reporting a crash, it includes the output of the "df" utility, to list the free disk space information per mount point. That output nowadays will inadvertently include all snaps that the user may have installed, including their revision numbers. Here is a simple df output: andreas@nsn7:~$ df Filesystem 1K-blocksUsed Available Use% Mounted on udev 8119680 0 8119680 0% /dev tmpfs 16301561828 1628328 1% /run nsn7/ROOT/ubuntu433084288 2500608 430583680 1% / tmpfs 8150776 1 8131888 1% /dev/shm tmpfs5120 4 5116 1% /run/lock tmpfs 8150776 0 8150776 0% /sys/fs/cgroup nsn7/var/log430763136 179456 430583680 1% /var/log nsn7/var/tmp430583808 128 430583680 1% /var/tmp /dev/sda2 1032088 160336871752 16% /boot /dev/sda1 5232482720520528 1% /boot/efi nsn7/home 430651264 67584 430583680 1% /home nsn7/var/cache 430653312 69632 430583680 1% /var/cache nsn7/var/mail 430583808 128 430583680 1% /var/mail nsn7/var/spool 430583808 128 430583680 1% /var/spool tmpfs 1630152 16 1630136 1% /run/user/120 tmpfs 100 0 100 0% /var/lib/lxd/shmounts tmpfs 100 0 100 0% /var/lib/lxd/devlxd tmpfs 1630152 36 1630116 1% /run/user/1000 nsn7/lxd/containers/squid-ds216 431444096 860416 430583680 1% /var/lib/lxd/storage-pools/default/containers/squid-ds216 /dev/loop0 83712 83712 0 100% /snap/core/4206 /dev/loop1 102144 102144 0 100% /snap/git-ubuntu/402 You can see I have the core snap at revision 4206, and git-ubuntu at revision 402. There are already many bug reports in launchpad where one can see this information. Granted, the user can review it, refuse to send this data, etc. This bug is about the unexpectedness of having that information in the disk space data. If the user sees a prompt like "Would you like to include disk free space information in your report?", or "Would you like to include the output of the df(1) command in your report?", that doesn't immediately translate to "Would you like to include disk free space information and a list of all installed snaps and their revision numbers in your report?". + + [Test case] + N/A + + [Regression potential] + Fix consists of adding -x squashfs to df output, so might hide other non-snap squashfs images. -- 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/1756595 Title: disk space info inadvertently provides all installed snaps Status in apport package in Ubuntu: Invalid Status in apt package in Ubuntu: Fix Released Status in apport source package in Bionic: Invalid Status in apt source package in Bionic: Triaged Status in apport source package in Disco: New Status in apt source package in Disco: Fix Committed Status in apport source package in Eoan: Invalid Status in apt source package in Eoan: Fix Released Bug description: [Impact] When apport is reporting a crash, it includes the output of the "df" utility, to list the free disk space information per mount point. That output nowadays will inadvertently include all snaps that the user may have installed, including their revision numbers. Here is a simple df output: andreas@nsn7:~$ df Filesystem 1K-blocksUsed Available Use% Mounted on udev 8119680 0 8119680 0% /dev tmpfs 16301561828 1628328 1% /run nsn7/ROOT/ubuntu433084288 2500608 430583680 1% / tmpfs 8150776 1 8131888 1% /dev/shm tmpfs5120 4 5116 1% /run/lock tmpfs 8150776 0 8150776 0% /sys/fs/cgroup nsn7/var/log430763136 179456 430583680 1% /var/log nsn7/var/tmp430583808 128 430583680 1% /var/tmp /dev/sda2 1032088 160336871752 16% /boot /dev/sda1 5232482720520528 1% /boot/efi nsn7/home
[Touch-packages] [Bug 1756595] Re: disk space info inadvertently provides all installed snaps
Hello Andreas, or anyone else affected, Accepted apt into disco-proposed. The package will build now and be available at https://launchpad.net/ubuntu/+source/apt/1.8.3 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-disco to verification-done-disco. If it does not fix the bug for you, please add a comment stating that, and change the tag to verification-failed-disco. In either case, without details of your testing we will not be able to proceed. Further information regarding the verification process can be found at https://wiki.ubuntu.com/QATeam/PerformingSRUVerification . Thank you in advance for helping! N.B. The updated package will be released to -updates after the bug(s) fixed by this package have been verified and the package has been in -proposed for a minimum of 7 days. ** Changed in: apt (Ubuntu Disco) Status: Triaged => Fix Committed ** Tags added: verification-needed verification-needed-disco -- 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/1756595 Title: disk space info inadvertently provides all installed snaps Status in apport package in Ubuntu: Invalid Status in apt package in Ubuntu: Fix Released Status in apport source package in Bionic: Invalid Status in apt source package in Bionic: Triaged Status in apport source package in Disco: New Status in apt source package in Disco: Fix Committed Status in apport source package in Eoan: Invalid Status in apt source package in Eoan: Fix Released Bug description: [Impact] When apport is reporting a crash, it includes the output of the "df" utility, to list the free disk space information per mount point. That output nowadays will inadvertently include all snaps that the user may have installed, including their revision numbers. Here is a simple df output: andreas@nsn7:~$ df Filesystem 1K-blocksUsed Available Use% Mounted on udev 8119680 0 8119680 0% /dev tmpfs 16301561828 1628328 1% /run nsn7/ROOT/ubuntu433084288 2500608 430583680 1% / tmpfs 8150776 1 8131888 1% /dev/shm tmpfs5120 4 5116 1% /run/lock tmpfs 8150776 0 8150776 0% /sys/fs/cgroup nsn7/var/log430763136 179456 430583680 1% /var/log nsn7/var/tmp430583808 128 430583680 1% /var/tmp /dev/sda2 1032088 160336871752 16% /boot /dev/sda1 5232482720520528 1% /boot/efi nsn7/home 430651264 67584 430583680 1% /home nsn7/var/cache 430653312 69632 430583680 1% /var/cache nsn7/var/mail 430583808 128 430583680 1% /var/mail nsn7/var/spool 430583808 128 430583680 1% /var/spool tmpfs 1630152 16 1630136 1% /run/user/120 tmpfs 100 0 100 0% /var/lib/lxd/shmounts tmpfs 100 0 100 0% /var/lib/lxd/devlxd tmpfs 1630152 36 1630116 1% /run/user/1000 nsn7/lxd/containers/squid-ds216 431444096 860416 430583680 1% /var/lib/lxd/storage-pools/default/containers/squid-ds216 /dev/loop0 83712 83712 0 100% /snap/core/4206 /dev/loop1 102144 102144 0 100% /snap/git-ubuntu/402 You can see I have the core snap at revision 4206, and git-ubuntu at revision 402. There are already many bug reports in launchpad where one can see this information. Granted, the user can review it, refuse to send this data, etc. This bug is about the unexpectedness of having that information in the disk space data. If the user sees a prompt like "Would you like to include disk free space information in your report?", or "Would you like to include the output of the df(1) command in your report?", that doesn't immediately translate to "Would you like to include disk free space information and a list of all installed snaps and their revision numbers in your report?". [Test case] N/A [Regression potential] Fix consists of adding -x squashfs to df output, so might hide other non-snap squashfs images. To manage notifications about this bug go to
[Touch-packages] [Bug 1838771] Re: http:Fix Host header in proxied https connections
Hello Eric, or anyone else affected, Accepted apt into disco-proposed. The package will build now and be available at https://launchpad.net/ubuntu/+source/apt/1.8.3 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-disco to verification-done-disco. If it does not fix the bug for you, please add a comment stating that, and change the tag to verification-failed-disco. In either case, without details of your testing we will not be able to proceed. Further information regarding the verification process can be found at https://wiki.ubuntu.com/QATeam/PerformingSRUVerification . Thank you in advance for helping! N.B. The updated package will be released to -updates after the bug(s) fixed by this package have been verified and the package has been in -proposed for a minimum of 7 days. ** Changed in: apt (Ubuntu Disco) Status: In Progress => Fix Committed ** Tags added: verification-needed verification-needed-disco -- 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/1838771 Title: http:Fix Host header in proxied https connections Status in apt package in Ubuntu: Fix Released Status in apt source package in Bionic: In Progress Status in apt source package in Disco: Fix Committed Bug description: [Impact] Currently CONNECT requests use the name of the proxy as Host value, instead of the origin server's name. According to RFC 2616 "The Host field value MUST represent the naming authority of the origin server or gateway given by the original URL." The current implementation causes problems with some proxy vendors. This commit[0] fixes this. [0] - https://salsa.debian.org/apt- team/apt/commit/86d4d98060f36c7e71c34af20a1193a75496ef72#54d3193c5d10a0032c80c3a6d3f069507265547f [Test Case] Here's one reproducer an impacted user brought to my attention: # /etc/environment http_proxy="http://internal:8080"; https_proxy="http://interal:8080"; To support application development activities in-house, I had to configure Azure CLI APT repository following the instructions from "https://docs.microsoft.com/en-us/cli/azure/install-azure-cli-apt?view =azure-cli-latest": $ sudo apt-get update $ sudo apt-get install curl apt-transport-https lsb-release gnupg $ curl -sL https://packages.microsoft.com/keys/microsoft.asc | \ $ gpg --dearmor | \ $ sudo tee /etc/apt/trusted.gpg.d/microsoft.asc.gpg > /dev/null $ AZ_REPO=$(lsb_release -cs) $ echo "deb [arch=amd64] https://packages.microsoft.com/repos/azure-cli/ $ $ AZ_REPO main" | \ $ sudo tee /etc/apt/sources.list.d/azure-cli.list $ sudo apt update In the final "apt update" command, APT respects system-wide network proxy variables and successfully fetched Canonical repository data over HTTP. However, it was unable to fetch the newly added Microsoft packages repository served via HTTPS. By using Wireshark to examine the HTTPS request made by APT, the request body reveals as: CONNECT packages.microsoft.com:443 HTTP/1.1\r\n Host: internal:8080\r\n User-Agent: Debian APT-HTTP/1.3 (1.6.11)\r\n ... ... There also is an automated test case in the package that runs as part of autopkgtest that tests a scenario like this, see the commit. [Regression Potential] * Fix already in debian, and Eoan * Has been reviewed/approved by juliank * A test package (pre-sru) has been provided to an impacted user, and he confirms it solves the situation. [Other Info] # salsa $ git describe --contains 86d4d98060f36c7e71c34af20a1193a75496ef72 1.9.0~8 # rmadison apt => apt | 1.6.11 | bionic-updates | source, amd64, arm64, armhf, i386, ppc64el, s390x => apt | 1.8.1 | disco-updates | source, amd64, arm64, armhf, i386, ppc64el, s390x apt | 1.9.1 | eoan | source, amd64, arm64, armhf, i386, ppc64el, s390x To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apt/+bug/1838771/+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 1829860] Re: APT unlocks in same order as it locks
Hello Julian, or anyone else affected, Accepted apt into disco-proposed. The package will build now and be available at https://launchpad.net/ubuntu/+source/apt/1.8.3 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-disco to verification-done-disco. If it does not fix the bug for you, please add a comment stating that, and change the tag to verification-failed-disco. In either case, without details of your testing we will not be able to proceed. Further information regarding the verification process can be found at https://wiki.ubuntu.com/QATeam/PerformingSRUVerification . Thank you in advance for helping! N.B. The updated package will be released to -updates after the bug(s) fixed by this package have been verified and the package has been in -proposed for a minimum of 7 days. ** Changed in: apt (Ubuntu Disco) Status: In Progress => Fix Committed ** Tags added: verification-needed verification-needed-disco -- 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/1829860 Title: APT unlocks in same order as it locks Status in apt package in Ubuntu: Fix Released Status in apt source package in Xenial: New Status in apt source package in Bionic: New Status in apt source package in Disco: Fix Committed Bug description: [Impact] APT releases the locks in the same order it acquires them, rather than reverse order. Given that we have no waiting for locks, this is not _super_ problematic, but it might be wrong: You'd get a lock failure on dpkg's lock, rather than lock-frontend. [Test case] Watch lock release with strace and see that it unlocks the right way. [Regression potential] Some other locking races or something? To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apt/+bug/1829860/+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 1829861] Re: handle TLS session renegotiation
Hello Julian, or anyone else affected, Accepted apt into disco-proposed. The package will build now and be available at https://launchpad.net/ubuntu/+source/apt/1.8.3 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-disco to verification-done-disco. If it does not fix the bug for you, please add a comment stating that, and change the tag to verification-failed-disco. In either case, without details of your testing we will not be able to proceed. Further information regarding the verification process can be found at https://wiki.ubuntu.com/QATeam/PerformingSRUVerification . Thank you in advance for helping! N.B. The updated package will be released to -updates after the bug(s) fixed by this package have been verified and the package has been in -proposed for a minimum of 7 days. ** Changed in: apt (Ubuntu Disco) Status: In Progress => Fix Committed ** Tags added: verification-needed verification-needed-disco -- 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/1829861 Title: handle TLS session renegotiation Status in apt package in Ubuntu: Fix Released Status in apt source package in Bionic: New Status in apt source package in Disco: Fix Committed Status in apt source package in Eoan: Fix Released Bug description: [Impact] TLS sessions can renegotiate keys, but APT does not support it; meaning their HTTPS connections stop working. [Test case] We don't really have a reproducer. You'd need a server that re-negotiates by path; e.g. because it requires a a certain client certificate for a certain path. We know it does not break other use cases, having run that for quite some time in eoan and Debian stretch, and the patch was tested by the patch submitter @ Akamai (see https://github.com/Debian/apt/pull/93). [Regression potential] - Could we get stuck on renegotiation? To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apt/+bug/1829861/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 164640]
good post. http://www.winmilliongame.com http://www.gtagame100.com http://www.subway-game.com http://www.zumagame100.com -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to fontconfig in Ubuntu. https://bugs.launchpad.net/bugs/164640 Title: Build Firefox 3 against a subpixel-patched cairo Status in Fontconfig: Fix Released Status in libcairo: Unknown Status in fontconfig package in Ubuntu: Fix Released Status in libcairo package in Ubuntu: Fix Released Status in xulrunner-1.9 package in Ubuntu: Fix Released Bug description: Binary package hint: firefox-3.0 In Ubuntu 7.10 and newer, Firefox 3.0 looks out of place with subpixel rendering enabled, due to the fact that it uses an unpatched, bundled version of Cairo. The patch should be ported to Cairo 1.5 and applied in the firefox-3.0 package. To manage notifications about this bug go to: https://bugs.launchpad.net/fontconfig/+bug/164640/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 164640]
It was nice to get update on the patch for LCD filtering from SuSE builds shared by David Turner, one of the freetype2 upstream developers that means a lot for users to refer his concern about regarding the LCD filtering and the Cairo patch are all on a public. Caroline, http://www.personalstatementfolks.co.uk/ -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to fontconfig in Ubuntu. https://bugs.launchpad.net/bugs/164640 Title: Build Firefox 3 against a subpixel-patched cairo Status in Fontconfig: Fix Released Status in libcairo: Unknown Status in fontconfig package in Ubuntu: Fix Released Status in libcairo package in Ubuntu: Fix Released Status in xulrunner-1.9 package in Ubuntu: Fix Released Bug description: Binary package hint: firefox-3.0 In Ubuntu 7.10 and newer, Firefox 3.0 looks out of place with subpixel rendering enabled, due to the fact that it uses an unpatched, bundled version of Cairo. The patch should be ported to Cairo 1.5 and applied in the firefox-3.0 package. To manage notifications about this bug go to: https://bugs.launchpad.net/fontconfig/+bug/164640/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1840725] Re: Microphone not working in Ubuntu 18.04.3 LTS on new hp-spectre-x360-convertible-15 laptop
@hui.wang Sorry for the late response. I have now managed to make my headset mic work permanently. I had to add the following line to the file /etc/modprobe.d/alsa-base.conf: options snd-hda-intel model=alc295-hp-x360 However, after doing this, a week later my speakers stopped working and I had to change some pin mappings using alsa-tools-gui: specifically I used Pin 0x14 for Internal Speaker (LFE) and Pin 0x1e for Internal Speaker. So right now, my speakers work, my headset(mic + sound) works and only my internal mic does not work. I am still unable to run the dump program in Windows. However, I can tell you that my laptop has Intel Smart Sound Technology(SST). I read somewhere that Ubuntu still does not have proper support for that although I may have misunderstood what I read. So I am not sure. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to alsa-driver in Ubuntu. https://bugs.launchpad.net/bugs/1840725 Title: Microphone not working in Ubuntu 18.04.3 LTS on new hp- spectre-x360-convertible-15 laptop Status in alsa-driver package in Ubuntu: New Bug description: Internal Microphone does not work in Ubuntu 18.04.3 LTS in a new hp- spectre-x360-convertible-15 laptop. The microphone works perfectly on Windows 10 (present in Dual boot mode). Initially, Internal Microphone was not even detected but installing alsa-tools-gui and overriding pin 0x12 to the Internal Microphone fixed that issue. [Pin 0x13 does not work and causes static in a headphone if it is plugged in.] Microphone is not able to pick up any sound. I changed levels/settings in alsamixer, pavucontrol without any success: In alsamixer: Experimented with levels ranging from very low to very high for Internal Mic, Capture, etc. In pavucontrol: Set the Internal Mic as a fallback device, unlocked the channels for the mic, experimented with reducing the level for one of the channels (reduced right mic level to Silence while keeping the left mic level normal/high and vice versa). alsa-info: http://alsa-project.org/db/?f=cf6d3ccc6372f955da7d99df07afbcb31d5a6c7f arecord -l List of CAPTURE Hardware Devices card 0: PCH [HDA Intel PCH], device 0: ALC285 Analog [ALC285 Analog] Subdevices: 1/1 Subdevice #0: subdevice #0 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1840725/+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 1836809] Re: segfault when CCD are present in two different HOG services
Launchpad has imported 2 comments from the remote bug at https://bugzilla.kernel.org/show_bug.cgi?id=204201. If you reply to an imported comment from within Launchpad, your comment will be sent to the remote bug automatically. Read more about Launchpad's inter-bugtracker facilities at https://help.launchpad.net/InterBugTracking. On 2019-07-17T09:53:30+00:00 mathieu.stephan wrote: Created attachment 283773 callstacks Hello everyone, We are currently developing a device that contains two HID services. That device, as it is right now, is properly functioning on Windows & Android. However, when pairing the device on Linux running bluez 5.50 we do get segfaults (see attached files). Our bluetooth device has 4 services : 1 battery service, 2 HID Over Gatt services and 1 device information service. With trial and error, we managed to find that we wouldn't get any crash as long as only 1 HOG service was present. Here's the interesting part. The two HOG services are made as follows: - standard keyboard over gatt: protocole mode / report map / 1 INPUT report / boot INPUT + OUTPUT / HID information / HID Control point - raw HID over gatt : report map / 1 INPUT report / 1 OUTPUT report / HID information / HID control point Looking at the write_ccc in the call stacks we wondered if the callbacks subscribing to notifications for the INPUT reports were causing this issue. We therefore changed the raw HID over gatt (and its report map) to remove the INPUT report and change it into 1 OUTPUT report (leading to 2 OUTPUT reports): no crash. We therefore hypothesize that the segfault occurs when subscribing to notification on a second HOG service.. Reply at: https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/1836809/comments/3 On 2019-08-05T04:56:38+00:00 mathieu.stephan wrote: Hello, We have done some further investigation. During device pairing bluez is crashing. >From debugging I can see the 2 hog services with the correct attributes, then >one of the 2 hog services is reaching ref_count 0, hence it is getting freed, >but on the next read bluez is trying to use a corrupted hog service and during >reading its attributes we are receiving the segfault. With normal behavior the next step would be "Report characteristic descriptor written: notifications enabled", but crashes right before that. Reply at: https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/1836809/comments/11 ** Changed in: bluez Status: Unknown => Confirmed ** Changed in: bluez Importance: Unknown => Medium -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to bluez in Ubuntu. https://bugs.launchpad.net/bugs/1836809 Title: segfault when CCD are present in two different HOG services Status in Bluez Utilities: Confirmed Status in bluez package in Ubuntu: Triaged Bug description: Hello everyone, We are currently developing a device that contains two HID services. That device, as it is right now, is properly functioning on Windows & Android. However, when pairing the device on Linux running bluez 5.50 we do get segfaults (see attached files). Our bluetooth device has 4 services : 1 battery service, 2 HID Over Gatt services and 1 device information service. With trial and error, we managed to find that we wouldn't get any crash as long as only 1 HOG service was present. Here's the interesting part. The two HOG services are made as follows: - standard keyboard over gatt: protocole mode / report map / 1 INPUT report / boot INPUT + OUTPUT / HID information / HID Control point - raw HID over gatt : report map / 1 INPUT report / 1 OUTPUT report / HID information / HID control point Looking at the write_ccc in the call stacks we wondered if the callbacks subscribing to notifications for the INPUT reports were causing this issue. We therefore changed the raw HID over gatt (and its report map) to remove the INPUT report and change it into 1 OUTPUT report (leading to 2 OUTPUT reports): no crash. We therefore hypothesize that the segfault occurs when subscribing to notification on a second HOG service... To manage notifications about this bug go to: https://bugs.launchpad.net/bluez/+bug/1836809/+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 1428121] Re: Intel HDMI Audio not working with IOMMU enabled
Launchpad has imported 96 comments from the remote bug at https://bugzilla.kernel.org/show_bug.cgi?id=60769. If you reply to an imported comment from within Launchpad, your comment will be sent to the remote bug automatically. Read more about Launchpad's inter-bugtracker facilities at https://help.launchpad.net/InterBugTracking. On 2013-08-19T15:15:18+00:00 patrakov wrote: I built a new desktop PC based on the Gigabyte H87N-WIFI motherboard. It has one DVI and two HDMI outputs. However, I cannot get any sound over HDMI. The same OS image works perfectly on my laptop that also has an HDMI output. This is not a pulseaudio problem, because the following command (with a 5-second wav file) takes a lot more than 5 seconds, and spams the kernel log with "playback write error (DMA or IRQ trouble?)": pasuspender -- aplay -D hdmi:0,0 /usr/share/sounds/startup3.wav I will attach more information to this bug. Reply at: https://bugs.launchpad.net/ubuntu/+source/alsa- driver/+bug/1428121/comments/0 On 2013-08-19T15:18:57+00:00 patrakov wrote: Created attachment 107242 alsa-info.sh output The relevant card is 00:03.0 (Intel Haswell HDMI) Reply at: https://bugs.launchpad.net/ubuntu/+source/alsa- driver/+bug/1428121/comments/1 On 2013-08-19T15:19:48+00:00 patrakov wrote: Created attachment 107243 Kernel config Reply at: https://bugs.launchpad.net/ubuntu/+source/alsa- driver/+bug/1428121/comments/2 On 2013-08-19T15:20:34+00:00 patrakov wrote: Created attachment 107245 Full dmesg Reply at: https://bugs.launchpad.net/ubuntu/+source/alsa- driver/+bug/1428121/comments/3 On 2013-08-21T07:12:29+00:00 patrakov wrote: Created attachment 107267 Full dmesg after BIOS update It was suggested that I update the BIOS and retry with -D hw:0,7. It didn't help, I still get the "playback write error (DMA or IRQ trouble?)" even with the F4 version of the BIOS. Reply at: https://bugs.launchpad.net/ubuntu/+source/alsa- driver/+bug/1428121/comments/4 On 2013-08-31T09:00:16+00:00 patrakov wrote: Created attachment 107373 /proc/interrupts, three times On IRC, ohsix asked me for /proc/interrupts. Here is what I did: cat /proc/interrupts > interrupts.txt pasuspender -- aplay -D hw:1,0 /usr/share/sounds/startup3.wav # works, plays through analog output cat /proc/interrupts >> interrupts.txt pasuspender -- aplay -D hw:0,3 /usr/share/sounds/startup3.wav # hangs => ctrl+c cat /proc/interrupts >> interrupts.txt Reply at: https://bugs.launchpad.net/ubuntu/+source/alsa- driver/+bug/1428121/comments/5 On 2013-09-05T07:16:59+00:00 mengdong.lin wrote: Backup info from Alexander: "according to the log, this machine claims to have three HDMI outputs, while in fact it has one DVI (possibly wired for HDMI, at least ELD is successfully transferred over it) and two "real" HDMI. All of them fail to transfer audio in the same way." Reply at: https://bugs.launchpad.net/ubuntu/+source/alsa- driver/+bug/1428121/comments/6 On 2013-09-09T13:25:46+00:00 patrakov wrote: More info possibly relevant to this bug: the board appears to have general IRQ problems. 1. The analog audio sometimes stutters. There is the following message in dmesg while playing a DVD (note: this is about the different card!): [ 2158.573591] hda-intel: IRQ timing workaround is activated for card #1. Suggest a bigger bdl_pos_adj. 2. Sometimes the keyboard or mouse exhibits lags (characters get delayed or the cursor sticks for several hundred milliseconds, while other screen updates appear as they should). Initially I attributed them to the fact that they are wireless (and that's the first time I use a wireless keyboard and mouse) and suspected interference from some unknown source. But, given the above IRQ-related message, I decided to tell you about that, too. Reply at: https://bugs.launchpad.net/ubuntu/+source/alsa- driver/+bug/1428121/comments/7 On 2013-09-10T15:18:30+00:00 superquad.vortex2 wrote: your still have deadlock and oops 1.351918] == [1.351989] [ INFO: possible circular locking dependency detected ] [1.352056] 3.11.0-rc5+ #1 Not tainted [1.352122] --- [1.352195] crda/311 is trying to acquire lock: [1.352383] microcode: CPU5 sig=0x306c3, pf=0x2, revision=0x9 [1.352258] (genl
[Touch-packages] [Bug 297143]
I don't see this issue on FF 51, Linux Mint 18 KDE edition. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to xorg in Ubuntu. https://bugs.launchpad.net/bugs/297143 Title: Xorg eats processor cycles while waiting for slow Internet Status in Mozilla Firefox: Invalid Status in Mozilla Thunderbird: New Status in X.Org X server: Invalid Status in xorg package in Ubuntu: Invalid Bug description: Top shows that xorg is using >40% of CPU when there's no reason for it to be doing so. High CPU usage by xorg seems to be associated with slow/flaky Internet, e.g. slow sending of email with Thunderbird or slow loading of Launchpad in Firefox over a WiFi connection. It seems like xorg goes mental until it receives notification that the Internet transfer has completed successfully. At least Thunderbird and Firefox are involved, wget doesn't cause the same problem. I'm using an up-to-date Hardy (64-bit) on a Sony Vaio SZ650 (intel 965 graphics) and iwlagn / iwl4965 WiFi. To manage notifications about this bug go to: https://bugs.launchpad.net/firefox/+bug/297143/+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 297143]
I don't use Linux anymore so I cannot respond to the question. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to xorg in Ubuntu. https://bugs.launchpad.net/bugs/297143 Title: Xorg eats processor cycles while waiting for slow Internet Status in Mozilla Firefox: Invalid Status in Mozilla Thunderbird: New Status in X.Org X server: Invalid Status in xorg package in Ubuntu: Invalid Bug description: Top shows that xorg is using >40% of CPU when there's no reason for it to be doing so. High CPU usage by xorg seems to be associated with slow/flaky Internet, e.g. slow sending of email with Thunderbird or slow loading of Launchpad in Firefox over a WiFi connection. It seems like xorg goes mental until it receives notification that the Internet transfer has completed successfully. At least Thunderbird and Firefox are involved, wget doesn't cause the same problem. I'm using an up-to-date Hardy (64-bit) on a Sony Vaio SZ650 (intel 965 graphics) and iwlagn / iwl4965 WiFi. To manage notifications about this bug go to: https://bugs.launchpad.net/firefox/+bug/297143/+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 297143]
No longer a Linux user. At least one that could be helpful here, as my one Linux machine is too much old and basic. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to xorg in Ubuntu. https://bugs.launchpad.net/bugs/297143 Title: Xorg eats processor cycles while waiting for slow Internet Status in Mozilla Firefox: Invalid Status in Mozilla Thunderbird: New Status in X.Org X server: Invalid Status in xorg package in Ubuntu: Invalid Bug description: Top shows that xorg is using >40% of CPU when there's no reason for it to be doing so. High CPU usage by xorg seems to be associated with slow/flaky Internet, e.g. slow sending of email with Thunderbird or slow loading of Launchpad in Firefox over a WiFi connection. It seems like xorg goes mental until it receives notification that the Internet transfer has completed successfully. At least Thunderbird and Firefox are involved, wget doesn't cause the same problem. I'm using an up-to-date Hardy (64-bit) on a Sony Vaio SZ650 (intel 965 graphics) and iwlagn / iwl4965 WiFi. To manage notifications about this bug go to: https://bugs.launchpad.net/firefox/+bug/297143/+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 297143]
WFM per comment 12 -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to xorg in Ubuntu. https://bugs.launchpad.net/bugs/297143 Title: Xorg eats processor cycles while waiting for slow Internet Status in Mozilla Firefox: Invalid Status in Mozilla Thunderbird: New Status in X.Org X server: Invalid Status in xorg package in Ubuntu: Invalid Bug description: Top shows that xorg is using >40% of CPU when there's no reason for it to be doing so. High CPU usage by xorg seems to be associated with slow/flaky Internet, e.g. slow sending of email with Thunderbird or slow loading of Launchpad in Firefox over a WiFi connection. It seems like xorg goes mental until it receives notification that the Internet transfer has completed successfully. At least Thunderbird and Firefox are involved, wget doesn't cause the same problem. I'm using an up-to-date Hardy (64-bit) on a Sony Vaio SZ650 (intel 965 graphics) and iwlagn / iwl4965 WiFi. To manage notifications about this bug go to: https://bugs.launchpad.net/firefox/+bug/297143/+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 297143]
(In reply to Javi Rueda from comment #8) > I have been CC'd here. Now I am just wondering why :/ :\ I guess ... does this happen with normal speed network? I.E. does this really only happen with a slow network? -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to xorg in Ubuntu. https://bugs.launchpad.net/bugs/297143 Title: Xorg eats processor cycles while waiting for slow Internet Status in Mozilla Firefox: Invalid Status in Mozilla Thunderbird: New Status in X.Org X server: Invalid Status in xorg package in Ubuntu: Invalid Bug description: Top shows that xorg is using >40% of CPU when there's no reason for it to be doing so. High CPU usage by xorg seems to be associated with slow/flaky Internet, e.g. slow sending of email with Thunderbird or slow loading of Launchpad in Firefox over a WiFi connection. It seems like xorg goes mental until it receives notification that the Internet transfer has completed successfully. At least Thunderbird and Firefox are involved, wget doesn't cause the same problem. I'm using an up-to-date Hardy (64-bit) on a Sony Vaio SZ650 (intel 965 graphics) and iwlagn / iwl4965 WiFi. To manage notifications about this bug go to: https://bugs.launchpad.net/firefox/+bug/297143/+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 297143]
Do you see it with current version 50? (In reply to mrthefter from comment #3) > I'm fairly sure that the compositor changes will improve this situation ... > bug 374980 This is clearly unlikely to happen. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to xorg in Ubuntu. https://bugs.launchpad.net/bugs/297143 Title: Xorg eats processor cycles while waiting for slow Internet Status in Mozilla Firefox: Invalid Status in Mozilla Thunderbird: New Status in X.Org X server: Invalid Status in xorg package in Ubuntu: Invalid Bug description: Top shows that xorg is using >40% of CPU when there's no reason for it to be doing so. High CPU usage by xorg seems to be associated with slow/flaky Internet, e.g. slow sending of email with Thunderbird or slow loading of Launchpad in Firefox over a WiFi connection. It seems like xorg goes mental until it receives notification that the Internet transfer has completed successfully. At least Thunderbird and Firefox are involved, wget doesn't cause the same problem. I'm using an up-to-date Hardy (64-bit) on a Sony Vaio SZ650 (intel 965 graphics) and iwlagn / iwl4965 WiFi. To manage notifications about this bug go to: https://bugs.launchpad.net/firefox/+bug/297143/+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 297143] Re: Xorg eats processor cycles while waiting for slow Internet
** Changed in: firefox Status: Confirmed => Invalid -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to xorg in Ubuntu. https://bugs.launchpad.net/bugs/297143 Title: Xorg eats processor cycles while waiting for slow Internet Status in Mozilla Firefox: Invalid Status in Mozilla Thunderbird: New Status in X.Org X server: Invalid Status in xorg package in Ubuntu: Invalid Bug description: Top shows that xorg is using >40% of CPU when there's no reason for it to be doing so. High CPU usage by xorg seems to be associated with slow/flaky Internet, e.g. slow sending of email with Thunderbird or slow loading of Launchpad in Firefox over a WiFi connection. It seems like xorg goes mental until it receives notification that the Internet transfer has completed successfully. At least Thunderbird and Firefox are involved, wget doesn't cause the same problem. I'm using an up-to-date Hardy (64-bit) on a Sony Vaio SZ650 (intel 965 graphics) and iwlagn / iwl4965 WiFi. To manage notifications about this bug go to: https://bugs.launchpad.net/firefox/+bug/297143/+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 1720519] Re: KDE/Kubuntu: Module "module-switch-on-connect" should be loaded once at most. Refusing to load.
** Changed in: pulseaudio Status: New => 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/1720519 Title: KDE/Kubuntu: Module "module-switch-on-connect" should be loaded once at most. Refusing to load. Status in PulseAudio: Fix Released Status in pulseaudio package in Ubuntu: Won't Fix Bug description: Pulseaudio daemon does not start after the update to Kubuntu 17.10 beta2, because the module fails to load although it is there. From 'pulseaudio -vv' E: [pulseaudio] module.c: Module "module-switch-on-connect" should be loaded once at most. Refusing to load. E: [pulseaudio] main.c: Module load failed. E: [pulseaudio] main.c: Failed to initialize daemon. PS sorry I am not a seasoned bug reporter. Let me know if I can provide more info. ProblemType: Bug DistroRelease: Ubuntu 17.10 Package: pulseaudio 1:10.0-2ubuntu3 ProcVersionSignature: Ubuntu 4.13.0-12.13-generic 4.13.3 Uname: Linux 4.13.0-12-generic x86_64 ApportVersion: 2.20.7-0ubuntu1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/pcmC0D0p: ben2809 F...m chrome /dev/snd/controlC0: ben2809 F chrome /dev/snd/timer: ben2809 f chrome CurrentDesktop: KDE Date: Sat Sep 30 11:20:55 2017 InstallationDate: Installed on 2017-04-07 (175 days ago) InstallationMedia: Kubuntu 17.04 "Zesty Zapus" - Beta amd64 (20170321) PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon. SourcePackage: pulseaudio UpgradeStatus: Upgraded to artful on 2017-09-30 (0 days ago) dmi.bios.date: 10/29/2015 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: P1.10 dmi.board.name: B150M-ITX dmi.board.vendor: ASRock dmi.chassis.asset.tag: To Be Filled By O.E.M. dmi.chassis.type: 3 dmi.chassis.vendor: To Be Filled By O.E.M. dmi.chassis.version: To Be Filled By O.E.M. dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrP1.10:bd10/29/2015:svnToBeFilledByO.E.M.:pnToBeFilledByO.E.M.:pvrToBeFilledByO.E.M.:rvnASRock:rnB150M-ITX:rvr:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.: dmi.product.family: To Be Filled By O.E.M. dmi.product.name: To Be Filled By O.E.M. dmi.product.version: To Be Filled By O.E.M. dmi.sys.vendor: To Be Filled By O.E.M. To manage notifications about this bug go to: https://bugs.launchpad.net/pulseaudio/+bug/1720519/+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 1835622]
*** Bug 15741 has been marked as a duplicate of this bug. *** -- 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/1835622 Title: Cannot start desktop session with compositor enabled Status in Xfwm4: Invalid Status in mesa package in Ubuntu: Confirmed Status in xfwm4 package in Ubuntu: Invalid Bug description: I cannot login to the Xfce desktop session anymore. in ~/.xsession- errors there's the message: xfwm4: ../src/mesa/drivers/dri/i965/intel_mipmap_tree.c:1285: intel_miptree_match_image: Assertion `image->TexObject->Target == mt->target' failed. Earlier today Mesa was upgraded via bionic-updates from 18.2 to 19.0. I'm running Xubuntu 18.04 and I'm also using the Xubuntu Staging PPA with xfwm4 4.13.3 To manage notifications about this bug go to: https://bugs.launchpad.net/xfwm4/+bug/1835622/+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 1841978] Re: package login 1:4.2-3.1ubuntu5 failed to install/upgrade: package login is already installed and configured
Thanks for taking the time to report this bug and helping to make Ubuntu better. We appreciate the difficulties you are facing, but this appears to be a "regular" (non-security) bug. I have unmarked it as a security issue since this bug does not show evidence of allowing attackers to cross privilege boundaries nor directly cause loss of data/privacy. Please feel free to report any other bugs you may find. ** Information type changed from Private Security to Public -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to shadow in Ubuntu. https://bugs.launchpad.net/bugs/1841978 Title: package login 1:4.2-3.1ubuntu5 failed to install/upgrade: package login is already installed and configured Status in shadow package in Ubuntu: New Bug description: i was delete "lp" from "passwd-shadow- ProblemType: Package DistroRelease: Ubuntu 16.04 Package: login 1:4.2-3.1ubuntu5.3 ProcVersionSignature: Ubuntu 4.8.0-36.36~16.04.1-generic 4.8.11 Uname: Linux 4.8.0-36-generic x86_64 ApportVersion: 2.20.1-0ubuntu2.5 AptdaemonVersion: 1.1.1+bzr982-0ubuntu14 Architecture: amd64 Date: Thu Aug 29 14:09:48 2019 ErrorMessage: package login is already installed and configured InstallationDate: Installed on 2019-08-29 (0 days ago) InstallationMedia: Ubuntu 16.04.2 LTS "Xenial Xerus" - Release amd64 (20170215.2) RelatedPackageVersions: dpkg 1.18.4ubuntu1.1 apt 1.2.19 SourcePackage: shadow Title: package login 1:4.2-3.1ubuntu5 failed to install/upgrade: package login is already installed and configured UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/shadow/+bug/1841978/+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 1835622]
See also bug 14475 -- 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/1835622 Title: Cannot start desktop session with compositor enabled Status in Xfwm4: Invalid Status in mesa package in Ubuntu: Confirmed Status in xfwm4 package in Ubuntu: Invalid Bug description: I cannot login to the Xfce desktop session anymore. in ~/.xsession- errors there's the message: xfwm4: ../src/mesa/drivers/dri/i965/intel_mipmap_tree.c:1285: intel_miptree_match_image: Assertion `image->TexObject->Target == mt->target' failed. Earlier today Mesa was upgraded via bionic-updates from 18.2 to 19.0. I'm running Xubuntu 18.04 and I'm also using the Xubuntu Staging PPA with xfwm4 4.13.3 To manage notifications about this bug go to: https://bugs.launchpad.net/xfwm4/+bug/1835622/+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 1835622]
*** Bug 15765 has been marked as a duplicate of this bug. *** -- 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/1835622 Title: Cannot start desktop session with compositor enabled Status in Xfwm4: Invalid Status in mesa package in Ubuntu: Confirmed Status in xfwm4 package in Ubuntu: Invalid Bug description: I cannot login to the Xfce desktop session anymore. in ~/.xsession- errors there's the message: xfwm4: ../src/mesa/drivers/dri/i965/intel_mipmap_tree.c:1285: intel_miptree_match_image: Assertion `image->TexObject->Target == mt->target' failed. Earlier today Mesa was upgraded via bionic-updates from 18.2 to 19.0. I'm running Xubuntu 18.04 and I'm also using the Xubuntu Staging PPA with xfwm4 4.13.3 To manage notifications about this bug go to: https://bugs.launchpad.net/xfwm4/+bug/1835622/+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 1794033]
Hello Yoshinori Gento >I got how to reproduce. Does this mean that you could provide an apitrace or somekind of reproducer? It would be really helpful. -- 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/1794033 Title: i965: Failed to submit batchbuffer: Bad address Status in mesa package in Ubuntu: Confirmed Status in xserver-xorg-video-intel package in Fedora: Incomplete Bug description: cpu: Intel® Core™ i5-7500 CPU @ 3.40GHz × 4 gpu: Intel® HD Graphics 630 (Kaby Lake GT2) 00:00.0 Host bridge: Intel Corporation Intel Kaby Lake Host Bridge (rev 05) 00:02.0 VGA compatible controller: Intel Corporation HD Graphics 630 (rev 04) 00:08.0 System peripheral: Intel Corporation Skylake Gaussian Mixture Model xserver-xorg-video-intel: Installed: 2:2.99.917+git20171229-1 Candidate: 2:2.99.917+git20171229-1 ubuntu: 18.04 LTS bionic gnome: 3.28.2 gdm3: Installed: 3.28.2-0ubuntu1.4 Candidate: 3.28.2-0ubuntu1.4 os type: 64 bit kernel: Linux eva1 4.15.0-30-generic #32-Ubuntu SMP Thu Jul 26 17:42:43 UTC 2018 x86_64 x86_64 x86_64 GNU/Linux mesa-va-drivers: Installed: 18.0.5-0ubuntu0~18.04.1 Candidate: 18.0.5-0ubuntu0~18.04.1 from syslog: Sep 24 04:08:16 eva /usr/lib/gdm3/gdm-x-session[1170]: i965: Failed to submit batchbuffer: Bad address Sep 24 04:08:21 eva gnome-terminal-[2597]: gnome-terminal-server: Fatal IO error 11 (Resource temporarily unavailable) on X server :0. Sep 24 04:08:22 eva [2541]: update-notifier: Fatal IO error 11 (Resource temporarily unavailable) on X server :0. Sep 24 04:08:22 eva at-spi-bus-launcher[1274]: XIO: fatal IO error 11 (Resource temporarily unavailable) on X server ":0" - but (followed by pages upon pages of applications within gnome failing.) nothing in kern.log around that time. Singular gnome crash, taking down all applications running within it. Not yet reproduced. gdm successfully started a new session afterwards. Was definitely in a palermoon session on some website or other. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mesa/+bug/1794033/+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 1794033]
(In reply to Denis from comment #28) > Hello Yoshinori Gento > > >I got how to reproduce. > Does this mean that you could provide an apitrace or somekind of reproducer? > It would be really helpful. Hello Denis I didn't produce an apitrace nor reproducer. I updated kernel to 4.19.57. Then, this problem became hard to occur, but still occurs. -- 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/1794033 Title: i965: Failed to submit batchbuffer: Bad address Status in mesa package in Ubuntu: Confirmed Status in xserver-xorg-video-intel package in Fedora: Incomplete Bug description: cpu: Intel® Core™ i5-7500 CPU @ 3.40GHz × 4 gpu: Intel® HD Graphics 630 (Kaby Lake GT2) 00:00.0 Host bridge: Intel Corporation Intel Kaby Lake Host Bridge (rev 05) 00:02.0 VGA compatible controller: Intel Corporation HD Graphics 630 (rev 04) 00:08.0 System peripheral: Intel Corporation Skylake Gaussian Mixture Model xserver-xorg-video-intel: Installed: 2:2.99.917+git20171229-1 Candidate: 2:2.99.917+git20171229-1 ubuntu: 18.04 LTS bionic gnome: 3.28.2 gdm3: Installed: 3.28.2-0ubuntu1.4 Candidate: 3.28.2-0ubuntu1.4 os type: 64 bit kernel: Linux eva1 4.15.0-30-generic #32-Ubuntu SMP Thu Jul 26 17:42:43 UTC 2018 x86_64 x86_64 x86_64 GNU/Linux mesa-va-drivers: Installed: 18.0.5-0ubuntu0~18.04.1 Candidate: 18.0.5-0ubuntu0~18.04.1 from syslog: Sep 24 04:08:16 eva /usr/lib/gdm3/gdm-x-session[1170]: i965: Failed to submit batchbuffer: Bad address Sep 24 04:08:21 eva gnome-terminal-[2597]: gnome-terminal-server: Fatal IO error 11 (Resource temporarily unavailable) on X server :0. Sep 24 04:08:22 eva [2541]: update-notifier: Fatal IO error 11 (Resource temporarily unavailable) on X server :0. Sep 24 04:08:22 eva at-spi-bus-launcher[1274]: XIO: fatal IO error 11 (Resource temporarily unavailable) on X server ":0" - but (followed by pages upon pages of applications within gnome failing.) nothing in kern.log around that time. Singular gnome crash, taking down all applications running within it. Not yet reproduced. gdm successfully started a new session afterwards. Was definitely in a palermoon session on some website or other. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mesa/+bug/1794033/+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 1842349] [NEW] Reconsider conditions for setting language and formats
Public bug reported: In connection with the upgrade to 0.6.50 (bug #1789502) the fallback values from /etc/default/locale were set on initialization. While that addresses some aspects of the upstream changes, a need remains to reconsider the conditions in user_change_language_authorized_cb() and user_change_formats_locale_authorized_cb(). Currently it does not take into account if variables were previously set in ~/.pam_environment or not. ** Affects: accountsservice (Ubuntu) Importance: Medium Assignee: Gunnar Hjalmarsson (gunnarhj) Status: In Progress -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to accountsservice in Ubuntu. https://bugs.launchpad.net/bugs/1842349 Title: Reconsider conditions for setting language and formats Status in accountsservice package in Ubuntu: In Progress Bug description: In connection with the upgrade to 0.6.50 (bug #1789502) the fallback values from /etc/default/locale were set on initialization. While that addresses some aspects of the upstream changes, a need remains to reconsider the conditions in user_change_language_authorized_cb() and user_change_formats_locale_authorized_cb(). Currently it does not take into account if variables were previously set in ~/.pam_environment or not. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/accountsservice/+bug/1842349/+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 1813587] Re: libunistring and libidn ftbfs on 18.04 LTS
** Changed in: libunistring (Debian) Status: New => Fix Released -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to libidn in Ubuntu. https://bugs.launchpad.net/bugs/1813587 Title: libunistring and libidn ftbfs on 18.04 LTS Status in libidn package in Ubuntu: Fix Released Status in libunistring package in Ubuntu: Fix Released Status in libidn source package in Bionic: Fix Released Status in libunistring source package in Bionic: Fix Released Status in libidn source package in Cosmic: Fix Released Status in libunistring source package in Cosmic: Fix Released Status in libunistring package in Debian: Fix Released Bug description: Impact -- libunistring doesn't build from source which means someone would need to fix that problem before fixing any bugs in the libunistring package for Ubuntu 18.04 LTS. Test Case - Does libunistring build successfully? Regression Potential We are simply backporting the workaround we applied in Ubuntu 19.04. Original Bug Report --- according to http://people.canonical.com/~doko/ftbfs-report/test-rebuild-20181222-bionic.html libunistring ftbfs. FAIL: test-thread_create glthread_create failed FAIL test-thread_create (exit status: 1) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libidn/+bug/1813587/+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 1757730] Re: Please port your package away from Qt 4
** Changed in: libdbusmenu-qt (Debian) Status: New => Fix Released -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to libdbusmenu-qt in Ubuntu. https://bugs.launchpad.net/bugs/1757730 Title: Please port your package away from Qt 4 Status in libdbusmenu-qt package in Ubuntu: New Status in libdbusmenu-qt package in Debian: Fix Released Bug description: Currently Qt 4 has been dead upstream and we are starting to have problems maintaining it, like for example in the OpenSSL 1.1 support case. Following in the footsteps of Debian[1], all packages directly or indirectly depending on qt4-x11 (like this one) must either get ported to Qt 5 and uploaded to the development release or get removed (by means of demotion to -proposed or removal of the package) before the 19.04 release. If it is possible to port your package by the 18.10 release, please do so. If you have any questions about porting or this transition, please ask in #ubuntu-qt (preferred) or directly ping me [1] https://wiki.debian.org/Qt4Removal To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libdbusmenu-qt/+bug/1757730/+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 1794033] Re: i965: Failed to submit batchbuffer: Bad address
** Changed in: xserver-xorg-video-intel (Fedora) Status: Confirmed => 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/1794033 Title: i965: Failed to submit batchbuffer: Bad address Status in mesa package in Ubuntu: Confirmed Status in xserver-xorg-video-intel package in Fedora: Incomplete Bug description: cpu: Intel® Core™ i5-7500 CPU @ 3.40GHz × 4 gpu: Intel® HD Graphics 630 (Kaby Lake GT2) 00:00.0 Host bridge: Intel Corporation Intel Kaby Lake Host Bridge (rev 05) 00:02.0 VGA compatible controller: Intel Corporation HD Graphics 630 (rev 04) 00:08.0 System peripheral: Intel Corporation Skylake Gaussian Mixture Model xserver-xorg-video-intel: Installed: 2:2.99.917+git20171229-1 Candidate: 2:2.99.917+git20171229-1 ubuntu: 18.04 LTS bionic gnome: 3.28.2 gdm3: Installed: 3.28.2-0ubuntu1.4 Candidate: 3.28.2-0ubuntu1.4 os type: 64 bit kernel: Linux eva1 4.15.0-30-generic #32-Ubuntu SMP Thu Jul 26 17:42:43 UTC 2018 x86_64 x86_64 x86_64 GNU/Linux mesa-va-drivers: Installed: 18.0.5-0ubuntu0~18.04.1 Candidate: 18.0.5-0ubuntu0~18.04.1 from syslog: Sep 24 04:08:16 eva /usr/lib/gdm3/gdm-x-session[1170]: i965: Failed to submit batchbuffer: Bad address Sep 24 04:08:21 eva gnome-terminal-[2597]: gnome-terminal-server: Fatal IO error 11 (Resource temporarily unavailable) on X server :0. Sep 24 04:08:22 eva [2541]: update-notifier: Fatal IO error 11 (Resource temporarily unavailable) on X server :0. Sep 24 04:08:22 eva at-spi-bus-launcher[1274]: XIO: fatal IO error 11 (Resource temporarily unavailable) on X server ":0" - but (followed by pages upon pages of applications within gnome failing.) nothing in kern.log around that time. Singular gnome crash, taking down all applications running within it. Not yet reproduced. gdm successfully started a new session afterwards. Was definitely in a palermoon session on some website or other. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mesa/+bug/1794033/+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 1837580] Re: memlock is not set
** Changed in: systemd (Debian) Status: Unknown => New -- 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/1837580 Title: memlock is not set Status in systemd package in Ubuntu: New Status in systemd package in Debian: New Bug description: I discovered this in relation to jack, which installs /etc/security/limits.d/audio.conf, containing: @audio - rtprio 95 @audio - memlockunlimited For a user in the audio group: $ulimit -l -r max locked memory (kbytes, -l) 65536 real-time priority (-r) 95 So jack (run as user via qjackctl) reports: ERROR: Cannot lock down 82280346 byte memory area (Cannot allocate memory) but does not report that it cannot set real-time priority, which it does if run by a user not in the audio group. I also tried putting the line in /etc/security/limits.conf, and trying a number rather than "unlimited", but it didn't help. Also reported independently here: https://askubuntu.com/questions/1142943/ulimit-unlimited-cannot-set ProblemType: Bug DistroRelease: Ubuntu 19.04 Package: libpam-modules:amd64 1.3.1-5ubuntu1 ProcVersionSignature: Ubuntu 5.0.0-20.21-lowlatency 5.0.8 Uname: Linux 5.0.0-20-lowlatency x86_64 ApportVersion: 2.20.10-0ubuntu27.1 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Tue Jul 23 15:07:52 2019 InstallationDate: Installed on 2016-10-25 (1000 days ago) InstallationMedia: Ubuntu 16.10 "Yakkety Yak" - Release amd64 (20161012.2) SourcePackage: pam UpgradeStatus: Upgraded to disco on 2019-07-19 (3 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1837580/+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 1842212] Re: I can't change "Formats" in "Language and Region"
** Changed in: accountsservice (Ubuntu) Status: Triaged => Fix Committed ** Changed in: accountsservice (Ubuntu) Assignee: (unassigned) => Gunnar Hjalmarsson (gunnarhj) -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to accountsservice in Ubuntu. https://bugs.launchpad.net/bugs/1842212 Title: I can't change "Formats" in "Language and Region" Status in accountsservice package in Ubuntu: Fix Committed Bug description: If I try to change format from "Ukraine" to "United Kingdom", system offers me to restart to complete the changes, but after this actions I don't see any changes. ProblemType: Bug DistroRelease: Ubuntu 19.10 Package: gnome-control-center 1:3.33.90-1ubuntu2 ProcVersionSignature: Ubuntu 5.2.0-15.16-generic 5.2.9 Uname: Linux 5.2.0-15-generic x86_64 ApportVersion: 2.20.11-0ubuntu7 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Sun Sep 1 17:12:15 2019 InstallationDate: Installed on 2019-09-01 (0 days ago) InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Alpha amd64 (20190830) SourcePackage: gnome-control-center UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/accountsservice/+bug/1842212/+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 595501] Re: iptables rules for NAT may break ufw setups
** Changed in: libvirt Status: Confirmed => Won't Fix -- 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/595501 Title: iptables rules for NAT may break ufw setups Status in libvirt: Won't Fix Status in libvirt package in Ubuntu: Invalid Status in ufw package in Ubuntu: Triaged Bug description: Hi there If one tries to use libvirt vms with a NATed network, libvirtd will insert iptables rules before the earliest ufw rules (ufw-before- forward) in the FORWARD chain, and so breaks ufw semantics. It would be nice if libvirt could have a special handling for the rules if ufw is present. Thanks! ProblemType: Bug DistroRelease: Ubuntu 10.04 Package: libvirt-bin 0.7.5-5ubuntu27 ProcVersionSignature: Ubuntu 2.6.32-22.36-server 2.6.32.11+drm33.2 Uname: Linux 2.6.32-22-server x86_64 Architecture: amd64 Date: Thu Jun 17 16:10:39 2010 ProcEnviron: PATH=(custom, user) LANG=en_US.UTF-8 SHELL=/bin/zsh SourcePackage: libvirt To manage notifications about this bug go to: https://bugs.launchpad.net/libvirt/+bug/595501/+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 595501]
This series moves all libvirt rules into separate chains: https://www.redhat.com/archives/libvir- list/2018-November/msg00018.html This makes it practical to install rules ahead of libvirt's rules in iptables default chains, without risk of libvirt constantly inserting more rules in front. -- 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/595501 Title: iptables rules for NAT may break ufw setups Status in libvirt: Won't Fix Status in libvirt package in Ubuntu: Invalid Status in ufw package in Ubuntu: Triaged Bug description: Hi there If one tries to use libvirt vms with a NATed network, libvirtd will insert iptables rules before the earliest ufw rules (ufw-before- forward) in the FORWARD chain, and so breaks ufw semantics. It would be nice if libvirt could have a special handling for the rules if ufw is present. Thanks! ProblemType: Bug DistroRelease: Ubuntu 10.04 Package: libvirt-bin 0.7.5-5ubuntu27 ProcVersionSignature: Ubuntu 2.6.32-22.36-server 2.6.32.11+drm33.2 Uname: Linux 2.6.32-22-server x86_64 Architecture: amd64 Date: Thu Jun 17 16:10:39 2010 ProcEnviron: PATH=(custom, user) LANG=en_US.UTF-8 SHELL=/bin/zsh SourcePackage: libvirt To manage notifications about this bug go to: https://bugs.launchpad.net/libvirt/+bug/595501/+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 595501]
That code landed upstream, so I guess this is fixed nowadays -- 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/595501 Title: iptables rules for NAT may break ufw setups Status in libvirt: Won't Fix Status in libvirt package in Ubuntu: Invalid Status in ufw package in Ubuntu: Triaged Bug description: Hi there If one tries to use libvirt vms with a NATed network, libvirtd will insert iptables rules before the earliest ufw rules (ufw-before- forward) in the FORWARD chain, and so breaks ufw semantics. It would be nice if libvirt could have a special handling for the rules if ufw is present. Thanks! ProblemType: Bug DistroRelease: Ubuntu 10.04 Package: libvirt-bin 0.7.5-5ubuntu27 ProcVersionSignature: Ubuntu 2.6.32-22.36-server 2.6.32.11+drm33.2 Uname: Linux 2.6.32-22-server x86_64 Architecture: amd64 Date: Thu Jun 17 16:10:39 2010 ProcEnviron: PATH=(custom, user) LANG=en_US.UTF-8 SHELL=/bin/zsh SourcePackage: libvirt To manage notifications about this bug go to: https://bugs.launchpad.net/libvirt/+bug/595501/+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 1829861] Autopkgtest regression report (apt/1.8.3)
All autopkgtests for the newly accepted apt (1.8.3) for disco have finished running. The following regressions have been reported in tests triggered by the package: auto-apt-proxy/11 (armhf) reprotest/0.7.8 (amd64) 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/disco/update_excuses.html#apt [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 apt in Ubuntu. https://bugs.launchpad.net/bugs/1829861 Title: handle TLS session renegotiation Status in apt package in Ubuntu: Fix Released Status in apt source package in Bionic: New Status in apt source package in Disco: Fix Committed Status in apt source package in Eoan: Fix Released Bug description: [Impact] TLS sessions can renegotiate keys, but APT does not support it; meaning their HTTPS connections stop working. [Test case] We don't really have a reproducer. You'd need a server that re-negotiates by path; e.g. because it requires a a certain client certificate for a certain path. We know it does not break other use cases, having run that for quite some time in eoan and Debian stretch, and the patch was tested by the patch submitter @ Akamai (see https://github.com/Debian/apt/pull/93). [Regression potential] - Could we get stuck on renegotiation? To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apt/+bug/1829861/+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 1838771] Autopkgtest regression report (apt/1.8.3)
All autopkgtests for the newly accepted apt (1.8.3) for disco have finished running. The following regressions have been reported in tests triggered by the package: auto-apt-proxy/11 (armhf) reprotest/0.7.8 (amd64) 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/disco/update_excuses.html#apt [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 apt in Ubuntu. https://bugs.launchpad.net/bugs/1838771 Title: http:Fix Host header in proxied https connections Status in apt package in Ubuntu: Fix Released Status in apt source package in Bionic: In Progress Status in apt source package in Disco: Fix Committed Bug description: [Impact] Currently CONNECT requests use the name of the proxy as Host value, instead of the origin server's name. According to RFC 2616 "The Host field value MUST represent the naming authority of the origin server or gateway given by the original URL." The current implementation causes problems with some proxy vendors. This commit[0] fixes this. [0] - https://salsa.debian.org/apt- team/apt/commit/86d4d98060f36c7e71c34af20a1193a75496ef72#54d3193c5d10a0032c80c3a6d3f069507265547f [Test Case] Here's one reproducer an impacted user brought to my attention: # /etc/environment http_proxy="http://internal:8080"; https_proxy="http://interal:8080"; To support application development activities in-house, I had to configure Azure CLI APT repository following the instructions from "https://docs.microsoft.com/en-us/cli/azure/install-azure-cli-apt?view =azure-cli-latest": $ sudo apt-get update $ sudo apt-get install curl apt-transport-https lsb-release gnupg $ curl -sL https://packages.microsoft.com/keys/microsoft.asc | \ $ gpg --dearmor | \ $ sudo tee /etc/apt/trusted.gpg.d/microsoft.asc.gpg > /dev/null $ AZ_REPO=$(lsb_release -cs) $ echo "deb [arch=amd64] https://packages.microsoft.com/repos/azure-cli/ $ $ AZ_REPO main" | \ $ sudo tee /etc/apt/sources.list.d/azure-cli.list $ sudo apt update In the final "apt update" command, APT respects system-wide network proxy variables and successfully fetched Canonical repository data over HTTP. However, it was unable to fetch the newly added Microsoft packages repository served via HTTPS. By using Wireshark to examine the HTTPS request made by APT, the request body reveals as: CONNECT packages.microsoft.com:443 HTTP/1.1\r\n Host: internal:8080\r\n User-Agent: Debian APT-HTTP/1.3 (1.6.11)\r\n ... ... There also is an automated test case in the package that runs as part of autopkgtest that tests a scenario like this, see the commit. [Regression Potential] * Fix already in debian, and Eoan * Has been reviewed/approved by juliank * A test package (pre-sru) has been provided to an impacted user, and he confirms it solves the situation. [Other Info] # salsa $ git describe --contains 86d4d98060f36c7e71c34af20a1193a75496ef72 1.9.0~8 # rmadison apt => apt | 1.6.11 | bionic-updates | source, amd64, arm64, armhf, i386, ppc64el, s390x => apt | 1.8.1 | disco-updates | source, amd64, arm64, armhf, i386, ppc64el, s390x apt | 1.9.1 | eoan | source, amd64, arm64, armhf, i386, ppc64el, s390x To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apt/+bug/1838771/+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 1756595] Autopkgtest regression report (apt/1.8.3)
All autopkgtests for the newly accepted apt (1.8.3) for disco have finished running. The following regressions have been reported in tests triggered by the package: auto-apt-proxy/11 (armhf) reprotest/0.7.8 (amd64) 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/disco/update_excuses.html#apt [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 apt in Ubuntu. https://bugs.launchpad.net/bugs/1756595 Title: disk space info inadvertently provides all installed snaps Status in apport package in Ubuntu: Invalid Status in apt package in Ubuntu: Fix Released Status in apport source package in Bionic: Invalid Status in apt source package in Bionic: Triaged Status in apport source package in Disco: New Status in apt source package in Disco: Fix Committed Status in apport source package in Eoan: Invalid Status in apt source package in Eoan: Fix Released Bug description: [Impact] When apport is reporting a crash, it includes the output of the "df" utility, to list the free disk space information per mount point. That output nowadays will inadvertently include all snaps that the user may have installed, including their revision numbers. Here is a simple df output: andreas@nsn7:~$ df Filesystem 1K-blocksUsed Available Use% Mounted on udev 8119680 0 8119680 0% /dev tmpfs 16301561828 1628328 1% /run nsn7/ROOT/ubuntu433084288 2500608 430583680 1% / tmpfs 8150776 1 8131888 1% /dev/shm tmpfs5120 4 5116 1% /run/lock tmpfs 8150776 0 8150776 0% /sys/fs/cgroup nsn7/var/log430763136 179456 430583680 1% /var/log nsn7/var/tmp430583808 128 430583680 1% /var/tmp /dev/sda2 1032088 160336871752 16% /boot /dev/sda1 5232482720520528 1% /boot/efi nsn7/home 430651264 67584 430583680 1% /home nsn7/var/cache 430653312 69632 430583680 1% /var/cache nsn7/var/mail 430583808 128 430583680 1% /var/mail nsn7/var/spool 430583808 128 430583680 1% /var/spool tmpfs 1630152 16 1630136 1% /run/user/120 tmpfs 100 0 100 0% /var/lib/lxd/shmounts tmpfs 100 0 100 0% /var/lib/lxd/devlxd tmpfs 1630152 36 1630116 1% /run/user/1000 nsn7/lxd/containers/squid-ds216 431444096 860416 430583680 1% /var/lib/lxd/storage-pools/default/containers/squid-ds216 /dev/loop0 83712 83712 0 100% /snap/core/4206 /dev/loop1 102144 102144 0 100% /snap/git-ubuntu/402 You can see I have the core snap at revision 4206, and git-ubuntu at revision 402. There are already many bug reports in launchpad where one can see this information. Granted, the user can review it, refuse to send this data, etc. This bug is about the unexpectedness of having that information in the disk space data. If the user sees a prompt like "Would you like to include disk free space information in your report?", or "Would you like to include the output of the df(1) command in your report?", that doesn't immediately translate to "Would you like to include disk free space information and a list of all installed snaps and their revision numbers in your report?". [Test case] N/A [Regression potential] Fix consists of adding -x squashfs to df output, so might hide other non-snap squashfs images. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apport/+bug/1756595/+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 1829860] Autopkgtest regression report (apt/1.8.3)
All autopkgtests for the newly accepted apt (1.8.3) for disco have finished running. The following regressions have been reported in tests triggered by the package: auto-apt-proxy/11 (armhf) reprotest/0.7.8 (amd64) 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/disco/update_excuses.html#apt [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 apt in Ubuntu. https://bugs.launchpad.net/bugs/1829860 Title: APT unlocks in same order as it locks Status in apt package in Ubuntu: Fix Released Status in apt source package in Xenial: New Status in apt source package in Bionic: New Status in apt source package in Disco: Fix Committed Bug description: [Impact] APT releases the locks in the same order it acquires them, rather than reverse order. Given that we have no waiting for locks, this is not _super_ problematic, but it might be wrong: You'd get a lock failure on dpkg's lock, rather than lock-frontend. [Test case] Watch lock release with strace and see that it unlocks the right way. [Regression potential] Some other locking races or something? To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apt/+bug/1829860/+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 1842352] [NEW] autopkgtest: boot-and-services test fails in armhf containers
Public bug reported: https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac /autopkgtest-eoan/eoan/armhf/s/systemd/20190902_092319_bc0af@/log.gz ... test_udev (__main__.ServicesTest) ... skipped 'udev does not work in containers' == ERROR: test_profile (__main__.AppArmorTest) AppArmor confined unit -- Traceback (most recent call last): File "/tmp/autopkgtest.3bj70k/build.TYC/src/debian/tests/boot-and-services", line 286, in test_profile subprocess.check_call(['apparmor_parser', '-r', '-v', aa_profile.name]) File "/usr/lib/python3.7/subprocess.py", line 347, in check_call raise CalledProcessError(retcode, cmd) subprocess.CalledProcessError: Command '['apparmor_parser', '-r', '-v', '/tmp/aa_violator.hg3olay4']' returned non-zero exit status 243. -- Ran 23 tests in 5.848s FAILED (errors=1, skipped=5) ... ** Affects: systemd (Ubuntu) Importance: Low Status: New ** Changed in: systemd (Ubuntu) Importance: Undecided => Low -- 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/1842352 Title: autopkgtest: boot-and-services test fails in armhf containers Status in systemd package in Ubuntu: New Bug description: https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac /autopkgtest-eoan/eoan/armhf/s/systemd/20190902_092319_bc0af@/log.gz ... test_udev (__main__.ServicesTest) ... skipped 'udev does not work in containers' == ERROR: test_profile (__main__.AppArmorTest) AppArmor confined unit -- Traceback (most recent call last): File "/tmp/autopkgtest.3bj70k/build.TYC/src/debian/tests/boot-and-services", line 286, in test_profile subprocess.check_call(['apparmor_parser', '-r', '-v', aa_profile.name]) File "/usr/lib/python3.7/subprocess.py", line 347, in check_call raise CalledProcessError(retcode, cmd) subprocess.CalledProcessError: Command '['apparmor_parser', '-r', '-v', '/tmp/aa_violator.hg3olay4']' returned non-zero exit status 243. -- Ran 23 tests in 5.848s FAILED (errors=1, skipped=5) ... To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1842352/+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 1841296] Re: Update to 2.4.3 next cycle
** Changed in: libshout (Debian) Status: Unknown => New -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to libshout in Ubuntu. https://bugs.launchpad.net/bugs/1841296 Title: Update to 2.4.3 next cycle Status in libshout package in Ubuntu: Triaged Status in libshout package in Debian: New Bug description: The new version includes new features and since we are in feature freeze now it's not for this cycle To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libshout/+bug/1841296/+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 1842212] Re: I can't change "Formats" in "Language and Region"
This bug was fixed in the package accountsservice - 0.6.55-0ubuntu6 --- accountsservice (0.6.55-0ubuntu6) eoan; urgency=medium * debian/patches/0010-set-language.patch: - Call user_locale_validate() separately and not as an argument when calling some other function. The latter has worked fine previously, but with latest gcc the arguments were not passed properly (LP: #1842212). -- Gunnar Hjalmarsson Mon, 02 Sep 2019 20:35:00 +0200 ** Changed in: accountsservice (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 accountsservice in Ubuntu. https://bugs.launchpad.net/bugs/1842212 Title: I can't change "Formats" in "Language and Region" Status in accountsservice package in Ubuntu: Fix Released Bug description: If I try to change format from "Ukraine" to "United Kingdom", system offers me to restart to complete the changes, but after this actions I don't see any changes. ProblemType: Bug DistroRelease: Ubuntu 19.10 Package: gnome-control-center 1:3.33.90-1ubuntu2 ProcVersionSignature: Ubuntu 5.2.0-15.16-generic 5.2.9 Uname: Linux 5.2.0-15-generic x86_64 ApportVersion: 2.20.11-0ubuntu7 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Sun Sep 1 17:12:15 2019 InstallationDate: Installed on 2019-09-01 (0 days ago) InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Alpha amd64 (20190830) SourcePackage: gnome-control-center UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/accountsservice/+bug/1842212/+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 1841412] Re: Build with NDEBUG again
the build log shows -DNDEBUG is passed on https://launchpadlibrarian.net/439432849/buildlog_ubuntu-bionic- amd64.mesa_19.0.8-0ubuntu0~18.04.2_BUILDING.txt.gz ** Tags removed: verification-needed verification-needed-bionic ** Tags added: verification-done verification-done-bionic -- 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/1841412 Title: Build with NDEBUG again Status in mesa package in Ubuntu: Invalid Status in mesa source package in Bionic: Fix Committed Bug description: [Impact] Mesa is now built with meson, and it turns out that meson < 0.47.0 (commit 7c4736d27f4c5d7 to be exact) doesn't handle command line options properly which means that -Db_ndebug=true didn't have any effect when mesa is built on bionic. This means that some asserts are enabled, and at least nouveau is affected. [Test case] chech the build log that -DNDEBUG is passed [Regression potential] none really, it just adds a build flag which should've been there To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mesa/+bug/1841412/+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 1797882]
I am currently using Debian 10 Buster with Wayland. This problem is not existing anymore at this release. Wayland no longer uses an extra fence register if dual monitor is used. The wrong reservation of fence registers at intel_blit.c still exists, but does not harm, because the limit of 14 usable fence registers is very safe. A limit of 15 might be possible, if reservation at intel_blit.c is unbugged. -- 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/1797882 Title: At dual monitor intel_do_flush_locked failed: Resource deadlock avoided Status in Mesa: Confirmed Status in gnome-shell package in Ubuntu: Won't Fix Status in mesa package in Ubuntu: Won't Fix Bug description: Using ubuntu wayland with dual monitors, configured above each other. Dock is configured at both displays, not hiding. Icons for "terminal" and "libreofffice Writer" are present at the dock. Start terminal on primary screen by mouseclick on dock. Start libreoffice Writer on primary screen by mouseclick on dock. Terminate libreoffice Witer by mouseclick on X. Repeat the starting and stopping of Writer. Login-screen will appear. Syslog shows: Oct 15 00:09:51 Gert2 org.gnome.Shell.desktop[5892]: intel_do_flush_locked failed: Resource deadlock avoided Oct 15 00:09:51 Gert2 gnome-terminal-[6439]: Error reading events from display: Connection reset by peer Oct 15 00:09:51 Gert2 systemd[5755]: gnome-terminal-server.service: Main process exited, code=exited, status=1/FAILURE This problem doesnot occur in a dual monitor-session without wayland. It also doesnot occur, if only one monitor used with wayland It also doesnot occur, if the dock is only present at the primary screen. It also doesnot occur if second started application is present at the dock and doesnot add an icon to the dock (as libreoffice does). All other dual monitor/dock configurations seem to have this problem. No idea if this is helpful info, but the used graphics card does not support OpenGL version 2.1: Oct 15 00:02:32 Gert2 org.gnome.Shell.desktop[4426]: Require OpenGL version 2.1 or later. Oct 15 00:02:32 Gert2 org.gnome.Shell.desktop[4426]: Failed to initialize glamor Oct 15 00:02:32 Gert2 org.gnome.Shell.desktop[4426]: Failed to initialize glamor, falling back to sw glxinfo: OpenGL vendor string: VMware, Inc. OpenGL renderer string: llvmpipe (LLVM 7.0, 128 bits) OpenGL core profile version string: 3.3 (Core Profile) Mesa 18.2.2 OpenGL core profile shading language version string: 3.30 OpenGL core profile context flags: (none) OpenGL core profile profile mask: core profile OpenGL core profile extensions: OpenGL version string: 3.1 Mesa 18.2.2 OpenGL shading language version string: 1.40 OpenGL context flags: (none) OpenGL extensions: OpenGL ES profile version string: OpenGL ES 3.0 Mesa 18.2.2 OpenGL ES profile shading language version string: OpenGL ES GLSL ES 3.00 OpenGL ES profile extensions: ProblemType: Bug DistroRelease: Ubuntu 18.10 Package: gnome-shell 3.30.1-2ubuntu1 ProcVersionSignature: Ubuntu 4.18.0-10.11-generic 4.18.12 Uname: Linux 4.18.0-10-generic i686 ApportVersion: 2.20.10-0ubuntu13 Architecture: i386 CurrentDesktop: ubuntu:GNOME Date: Mon Oct 15 13:25:10 2018 DisplayManager: gdm3 GsettingsChanges: b'org.gnome.shell' b'command-history' redacted by apport b'org.gnome.shell' b'app-picker-view' b'uint32 1' b'org.gnome.shell' b'favorite-apps' redacted by apport b'org.gnome.desktop.interface' b'gtk-im-module' b"'gtk-im-context-simple'" ProcEnviron: LANGUAGE=en_US:en PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: gnome-shell UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/mesa/+bug/1797882/+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 1829805] Re: update-initramfs -k all -c does not create initrd images anymore
** Changed in: initramfs-tools (Debian) Status: Unknown => New -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to initramfs-tools in Ubuntu. https://bugs.launchpad.net/bugs/1829805 Title: update-initramfs -k all -c does not create initrd images anymore Status in calamares-settings-ubuntu package in Ubuntu: Fix Released Status in initramfs-tools package in Ubuntu: Triaged Status in initramfs-tools package in Debian: New Bug description: Context: The live environment appears to function properly and install proceeds as expected with no noticeable errors. Expected results: After a system reboot the virtual machine enters the graphical environment Actual Results: After rebooting the virtual machine a kernel panic error screen appears. I will attempt to attach the screenshot after submitting this bug report. The collected data is from the live environment as the installed environment will not boot. lubuntu@lubuntu:~$ lsb_release -a No LSB modules are available. Distributor ID: Ubuntu Description:Ubuntu Eoan Ermine (development branch) Release:19.10 Codename: eoan lubuntu@lubuntu:~$ apt-cache policy grub2 grub2: Installed: (none) Candidate: 2.02+dfsg1-12ubuntu2 Version table: 2.02+dfsg1-12ubuntu2 500 500 cdrom://Lubuntu 19.10 _Eoan Ermine_ - Alpha amd64 (20190519) eoan/universe amd64 Packages 500 http://archive.ubuntu.com/ubuntu eoan/universe amd64 Packages ProblemType: Bug DistroRelease: Ubuntu 19.10 Package: grub2 (not installed) ProcVersionSignature: Ubuntu 5.0.0-13.14-generic 5.0.6 Uname: Linux 5.0.0-13-generic x86_64 ApportVersion: 2.20.10-0ubuntu27 Architecture: amd64 CasperVersion: 1.407 CurrentDesktop: LXQt Date: Tue May 21 00:30:39 2019 LiveMediaBuild: Lubuntu 19.10 "Eoan Ermine" - Alpha amd64 (20190519) SourcePackage: grub2 UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/calamares-settings-ubuntu/+bug/1829805/+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 1829347] Re: systemd autopkgtest 'storage' fails adding/rmmoding scsi_debug
** Changed in: systemd (Debian)
Status: New => Fix Released
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to systemd in Ubuntu.
https://bugs.launchpad.net/bugs/1829347
Title:
systemd autopkgtest 'storage' fails adding/rmmoding scsi_debug
Status in systemd package in Ubuntu:
Won't Fix
Status in systemd source package in Bionic:
Won't Fix
Status in systemd source package in Cosmic:
Won't Fix
Status in systemd source package in Disco:
Won't Fix
Status in systemd source package in Eoan:
Won't Fix
Status in systemd package in Debian:
Fix Released
Bug description:
[impact]
systemd autopkgtest fails
[test case]
run systemd autopkgtest, check for output like:
LUKS device with "tmp" option ... rmmod: ERROR: Module scsi_debug is in use
FAIL
==
FAIL: test_luks_tmp (__main__.CryptsetupTest)
LUKS device with "tmp" option
--
Traceback (most recent call last):
File "/tmp/autopkgtest.It858Q/build.e7O/src/debian/tests/storage", line 59,
in setUp
self.fail('%s exists already' % self.plaintext_dev)
AssertionError: /dev/mapper/testcrypt1 exists already
or for older releases something like:
autopkgtest [19:27:26]: test storage: [---
modprobe: FATAL: Module scsi_debug not found in directory
/lib/modules/4.18.0-1011-kvm
ERROR
==
ERROR: setUpClass (__main__.CryptsetupTest)
--
Traceback (most recent call last):
File "/tmp/autopkgtest.azsL0q/build.Hbd/src/debian/tests/storage", line 21,
in setUpClass
subprocess.check_call(['modprobe', 'scsi_debug'])
File "/usr/lib/python3.6/subprocess.py", line 291, in check_call
raise CalledProcessError(retcode, cmd)
subprocess.CalledProcessError: Command '['modprobe', 'scsi_debug']' returned
non-zero exit status 1.
this has attempted to be fixed in disco/eoan so the output is a bit
different across different releases, but all of them have the common
point of failing to modprobe or rmmod the scsi_debug module, which by
itself doesn't indicate a failure.
[regression potential]
low; this is fixing a testcase only.
[other info]
fixing test case that generally causes the failed rmmod in bug 1831459
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1829347/+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 1833479] Re: libjack-jackd2-0 double close on a failure to connect to jackd which causes crashes in multithreaded programs
** Changed in: jackd2 (Debian) Status: Unknown => Confirmed -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to jackd2 in Ubuntu. https://bugs.launchpad.net/bugs/1833479 Title: libjack-jackd2-0 double close on a failure to connect to jackd which causes crashes in multithreaded programs Status in jackd2 package in Ubuntu: Confirmed Status in jackd2 package in Debian: Confirmed Bug description: After upgrading to Ubuntu 19.04, I started experiencing sporadic crashes in kodi when turning my AV receiver on. Ubuntu 19.04 upgraded alsa-plugins to 1.1.8. For alsa-plugins >= 1.1.7, the ALSA jack plugin is enabled by default in /etc/alsa/conf.d/50-jack.conf. The crashes are caused by a race condition when kodi's audio engine thread is enumerating the ALSA sound devices, and the udev thread is enumerating the udev devices triggered by the sound device add from turning the AVR on. When enumerating the ALSA jack plugin device, it tries to connect to connect to jackd. Since I don't have jackd installed, it fails to connect. libjack closes the socket on error, and then closes it again in it's cleanup code. Since it's closing the same file descriptor twice, it interacts with other threads that have potentially opened file descriptors, and causes the crash. This same bug could potentially affect other multi-threaded programs that enumerate ALSA devices. Fix committed upstream: https://github.com/jackaudio/jack2/commit/dad4b5702782eef3bd66e3c3f4fefaaae3571208 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/jackd2/+bug/1833479/+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 1801540]
Created attachment 283647 alsa-info on MSI B450 TOMAHAWK (with Realtek ALC892) I also had the same problem with the MSI B450 Tomahawk and Ryzen 2600, I managed some time ago to make the audio output sound acceptable but the mic in default config makes a lot of noise, and after configuring pulse there's still a static noise constantly running, I had to resort to buying a cheap USB Audio Card. I also reported some time ago that I had audio issues on another thread relative to the ALC892. -- 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/1801540 Title: Microphone distorted sound on ALC892/1220 on AMD chipsets Status in Linux: Confirmed Status in linux package in Ubuntu: Won't Fix Status in pulseaudio package in Ubuntu: Won't Fix Bug description: Not sure if I'll report this upstream but there is definitely an issue with microphone recording on my desktop, this is not happening on my laptop which has a different codec. Already tried all workarounds possible, no luck. Only with my desktop with this particular motherboard. No issues in Windows, the sound recorded in there is distorted and has some static and robotic tone on high-pitch. alsa-info on the attachments To manage notifications about this bug go to: https://bugs.launchpad.net/linux/+bug/1801540/+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 1801540]
Just adding to the list of people noting that the ALC1220 has problems as well. I have an MSI MPG X570 Gaming Edge Wifi board, with the newest X570 chipset. The audio is unusable because of this bug - a very noticeable crackle on the input side. Output is OK. The volume of the microphone input is insanely loud - it seems to be WAY to highly amplified. Ah well, the old soundblaster will live on into the new machine I guess. -- 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/1801540 Title: Microphone distorted sound on ALC892/1220 on AMD chipsets Status in Linux: Confirmed Status in linux package in Ubuntu: Won't Fix Status in pulseaudio package in Ubuntu: Won't Fix Bug description: Not sure if I'll report this upstream but there is definitely an issue with microphone recording on my desktop, this is not happening on my laptop which has a different codec. Already tried all workarounds possible, no luck. Only with my desktop with this particular motherboard. No issues in Windows, the sound recorded in there is distorted and has some static and robotic tone on high-pitch. alsa-info on the attachments To manage notifications about this bug go to: https://bugs.launchpad.net/linux/+bug/1801540/+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 1801540]
Manjaro 18.04 with kernel 4.19, Asrock B350 Gaming ITX/ac, Ryzen 1600, Realtek ALC1220. Both input and output are with crackling. After some tweaks in pulse daemon (changing in sample rate) input cracks are gone, but in output its still here. Also this fixes are heavy on CPU, resulting in stutters in mediacontent and gaming. -- 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/1801540 Title: Microphone distorted sound on ALC892/1220 on AMD chipsets Status in Linux: Confirmed Status in linux package in Ubuntu: Won't Fix Status in pulseaudio package in Ubuntu: Won't Fix Bug description: Not sure if I'll report this upstream but there is definitely an issue with microphone recording on my desktop, this is not happening on my laptop which has a different codec. Already tried all workarounds possible, no luck. Only with my desktop with this particular motherboard. No issues in Windows, the sound recorded in there is distorted and has some static and robotic tone on high-pitch. alsa-info on the attachments To manage notifications about this bug go to: https://bugs.launchpad.net/linux/+bug/1801540/+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 1801540]
Well, it's still not clear who to blame. Practically seen, the problem appears on a certain Realtek codecs just because there are such codec chips on the market for major mobos. Except for a few vendors (like Apple), all boards are equipped with Realtek codecs. So, I still suspect the problem being in HD-audio controller -- the AMD chipset side. Can people check whether any of workarounds have any effect? For example, - Make sure the existing quirks for ATI boards: Check the PCI device ID of your HD-audio controller connected to the onboard analog audio. You may have multiple HD-audio controller entries, and one of them is for HDMI and another for the onboard audio. The table in sound/pci/hda/hda_intel.c indicates the type and the quirk. The AMD one should be with AZX_DCAPS_PRESET_ATI_SB. - Disable the page caching. This can be done by passing snoop=0 option. But maybe it's more interesting to forcibly disable the cache while keeping the PCI snoop enabled, e.g. apply a patch like: --- a/sound/pci/hda/hda_intel.c +++ b/sound/pci/hda/hda_intel.c @@ -1681,6 +1681,7 @@ static int azx_create(struct snd_card *card, struct pci_dev *pci, chip->single_cmd = single_cmd; azx_check_snoop_available(chip); + chip->uc_buffer = true; // XXX if (bdl_pos_adj[dev] < 0) - Adjust more quirk bits: AZX_DCAPS_PRESET_ATI_SB contains AZX_DCAPS_NO_TCSL. Try to remove this flag, for example. Also, add more flags, e.g. AZX_DCAPS_NO_MSI, AZX_DCAPS_NO_MSI64, AZX_DCAPS_NO_64BIT, AZX_DCAPS_4K-BDLE_BOUNDARY. - Try different sample rates, format, period and buffer sizes: At best test with aplay / arecord with -Dhw option to skip pulseaudio. (You can run it over pasuspender.) Check various parameters, e.g. 44.1k vs 48kHz, S16_LE vs S32_LE. Try to align the period size and the buffer size to be 4kB. -- 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/1801540 Title: Microphone distorted sound on ALC892/1220 on AMD chipsets Status in Linux: Confirmed Status in linux package in Ubuntu: Won't Fix Status in pulseaudio package in Ubuntu: Won't Fix Bug description: Not sure if I'll report this upstream but there is definitely an issue with microphone recording on my desktop, this is not happening on my laptop which has a different codec. Already tried all workarounds possible, no luck. Only with my desktop with this particular motherboard. No issues in Windows, the sound recorded in there is distorted and has some static and robotic tone on high-pitch. alsa-info on the attachments To manage notifications about this bug go to: https://bugs.launchpad.net/linux/+bug/1801540/+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 1801540]
(In reply to Takashi Iwai from comment #127)
> Hm, interesting, AZX_DCAPS_POSFIX_LPIB basically sets the position reporting
> based on LPIB instead of the position buffer. I thought the position buffer
> isn't available or unreliable on non-Intel chips, but it might be different
> on the recent AMD one.
Contrary to what Ernst experienced, removing AZX_DCAPS_POSFIX_LPIB
completely broke audio on my system (ASUS PRIME X470, also 1022:1457),
so I guess it's still unreliable as you mentioned.
Was looking through the pci_ids array in sound/pci/hda/hda_intel.c and
noticed that my audio controller (1022:1457) isn't listed.
The only thing I can see that would match is the following, which seems
to be intended for AMD GPUs.
{ PCI_DEVICE(PCI_VENDOR_ID_AMD, PCI_ANY_ID),
.class = PCI_CLASS_MULTIMEDIA_HD_AUDIO << 8,
.class_mask = 0xff,
.driver_data = AZX_DRIVER_GENERIC | AZX_DCAPS_PRESET_ATI_HDMI },
--
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/1801540
Title:
Microphone distorted sound on ALC892/1220 on AMD chipsets
Status in Linux:
Confirmed
Status in linux package in Ubuntu:
Won't Fix
Status in pulseaudio package in Ubuntu:
Won't Fix
Bug description:
Not sure if I'll report this upstream but there is definitely an issue
with microphone recording on my desktop, this is not happening on my
laptop which has a different codec.
Already tried all workarounds possible, no luck. Only with my desktop
with this particular motherboard. No issues in Windows, the sound
recorded in there is distorted and has some static and robotic tone on
high-pitch.
alsa-info on the attachments
To manage notifications about this bug go to:
https://bugs.launchpad.net/linux/+bug/1801540/+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 1801540]
Created attachment 283955 1022 1457 patch Here's exactly what I did, on a 5.2.0-rc5 base. Note that it's just AZX_DRIVER_GENERIC and then the contents of ATI_SB without AZX_DCAPS_POSFIX_LPIB. -- 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/1801540 Title: Microphone distorted sound on ALC892/1220 on AMD chipsets Status in Linux: Confirmed Status in linux package in Ubuntu: Won't Fix Status in pulseaudio package in Ubuntu: Won't Fix Bug description: Not sure if I'll report this upstream but there is definitely an issue with microphone recording on my desktop, this is not happening on my laptop which has a different codec. Already tried all workarounds possible, no luck. Only with my desktop with this particular motherboard. No issues in Windows, the sound recorded in there is distorted and has some static and robotic tone on high-pitch. alsa-info on the attachments To manage notifications about this bug go to: https://bugs.launchpad.net/linux/+bug/1801540/+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 1801540]
That's bad that the chipset shows inconsistent behavior. How did you test exactly and how it's broken without AZX_DCAPS_POSFIX_LPIB? As mentioned in comment 125, the first thing to do is to assure your PCI device listed in the azx_ids[] table explicitly. If not, create an entry to pass like: .driver_data = AZX_DRIVER_GENERIC | AZX_DCAPS_PRESET_ATI_SB This should be defined before the generic catch-all entry mentioned in comment 128. I guess this entry addition won't suffice by itself, but this at least aligns with the older AMD chipset, and we can test by adjusting the AZX_DCAPS_PRESET_ATI_SB definition. Then try other parameters mentioned in comment 125, or play with AZX_DCAPS_POSFIX_* or position_fix option. -- 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/1801540 Title: Microphone distorted sound on ALC892/1220 on AMD chipsets Status in Linux: Confirmed Status in linux package in Ubuntu: Won't Fix Status in pulseaudio package in Ubuntu: Won't Fix Bug description: Not sure if I'll report this upstream but there is definitely an issue with microphone recording on my desktop, this is not happening on my laptop which has a different codec. Already tried all workarounds possible, no luck. Only with my desktop with this particular motherboard. No issues in Windows, the sound recorded in there is distorted and has some static and robotic tone on high-pitch. alsa-info on the attachments To manage notifications about this bug go to: https://bugs.launchpad.net/linux/+bug/1801540/+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 1801540]
Then possibly the playback needs LPIB while the capture position buffer? A patch like below... -- 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/1801540 Title: Microphone distorted sound on ALC892/1220 on AMD chipsets Status in Linux: Confirmed Status in linux package in Ubuntu: Won't Fix Status in pulseaudio package in Ubuntu: Won't Fix Bug description: Not sure if I'll report this upstream but there is definitely an issue with microphone recording on my desktop, this is not happening on my laptop which has a different codec. Already tried all workarounds possible, no luck. Only with my desktop with this particular motherboard. No issues in Windows, the sound recorded in there is distorted and has some static and robotic tone on high-pitch. alsa-info on the attachments To manage notifications about this bug go to: https://bugs.launchpad.net/linux/+bug/1801540/+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 1801540]
Created attachment 283961 A test patch for PCI 1022:1457 -- 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/1801540 Title: Microphone distorted sound on ALC892/1220 on AMD chipsets Status in Linux: Confirmed Status in linux package in Ubuntu: Won't Fix Status in pulseaudio package in Ubuntu: Won't Fix Bug description: Not sure if I'll report this upstream but there is definitely an issue with microphone recording on my desktop, this is not happening on my laptop which has a different codec. Already tried all workarounds possible, no luck. Only with my desktop with this particular motherboard. No issues in Windows, the sound recorded in there is distorted and has some static and robotic tone on high-pitch. alsa-info on the attachments To manage notifications about this bug go to: https://bugs.launchpad.net/linux/+bug/1801540/+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 1801540]
Thanks for the pointer Tiwai!
The problem on my board at least seems to be AZX_DCAPS_POSFIX_LPIB,
which seems to get enabled by default. Some of the HDMI entries further
down?
My chip is called 1022:1457 so I did something like this:
/* AMD X370 */
{ PCI_DEVICE(0x1022, 0x1457),
.driver_data = AZX_DRIVER_GENERIC | AZX_DCAPS_NO_TCSEL |
AZX_DCAPS_SYNC_WRITE | AZX_DCAPS_SNOOP_TYPE(ATI) },
Not sure what to call the entry.
I didn't notice any change with SYNC_WRITE on or off really.
Here's a way to list the pciid of you sound chip btw:
lspci | grep "HD Audio" | cut -d " " -f 1 | xargs sudo lspci -n -s
--
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/1801540
Title:
Microphone distorted sound on ALC892/1220 on AMD chipsets
Status in Linux:
Confirmed
Status in linux package in Ubuntu:
Won't Fix
Status in pulseaudio package in Ubuntu:
Won't Fix
Bug description:
Not sure if I'll report this upstream but there is definitely an issue
with microphone recording on my desktop, this is not happening on my
laptop which has a different codec.
Already tried all workarounds possible, no luck. Only with my desktop
with this particular motherboard. No issues in Windows, the sound
recorded in there is distorted and has some static and robotic tone on
high-pitch.
alsa-info on the attachments
To manage notifications about this bug go to:
https://bugs.launchpad.net/linux/+bug/1801540/+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 1801540]
(In reply to David from comment #134) > Tried the patch on kernel 4.19.60, no sound on input. Here it is working (5.2.2), but it's worse than before. I will try to play with parameters now. Thanks for the base patch, Tiwai. I'll see if with some parameters above something will change. However, right now the left channel from my front headphone jack is still not working. -- 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/1801540 Title: Microphone distorted sound on ALC892/1220 on AMD chipsets Status in Linux: Confirmed Status in linux package in Ubuntu: Won't Fix Status in pulseaudio package in Ubuntu: Won't Fix Bug description: Not sure if I'll report this upstream but there is definitely an issue with microphone recording on my desktop, this is not happening on my laptop which has a different codec. Already tried all workarounds possible, no luck. Only with my desktop with this particular motherboard. No issues in Windows, the sound recorded in there is distorted and has some static and robotic tone on high-pitch. alsa-info on the attachments To manage notifications about this bug go to: https://bugs.launchpad.net/linux/+bug/1801540/+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 1801540]
Tried the patch on kernel 4.19.60, no sound on input. -- 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/1801540 Title: Microphone distorted sound on ALC892/1220 on AMD chipsets Status in Linux: Confirmed Status in linux package in Ubuntu: Won't Fix Status in pulseaudio package in Ubuntu: Won't Fix Bug description: Not sure if I'll report this upstream but there is definitely an issue with microphone recording on my desktop, this is not happening on my laptop which has a different codec. Already tried all workarounds possible, no luck. Only with my desktop with this particular motherboard. No issues in Windows, the sound recorded in there is distorted and has some static and robotic tone on high-pitch. alsa-info on the attachments To manage notifications about this bug go to: https://bugs.launchpad.net/linux/+bug/1801540/+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 1801540]
Hmm ok I didn't test very properly, the crackle is gone but there seems to be some timing issues with playback, it doesn't sound correctly anymore. :-) -- 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/1801540 Title: Microphone distorted sound on ALC892/1220 on AMD chipsets Status in Linux: Confirmed Status in linux package in Ubuntu: Won't Fix Status in pulseaudio package in Ubuntu: Won't Fix Bug description: Not sure if I'll report this upstream but there is definitely an issue with microphone recording on my desktop, this is not happening on my laptop which has a different codec. Already tried all workarounds possible, no luck. Only with my desktop with this particular motherboard. No issues in Windows, the sound recorded in there is distorted and has some static and robotic tone on high-pitch. alsa-info on the attachments To manage notifications about this bug go to: https://bugs.launchpad.net/linux/+bug/1801540/+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 1801540]
Hm, interesting, AZX_DCAPS_POSFIX_LPIB basically sets the position reporting based on LPIB instead of the position buffer. I thought the position buffer isn't available or unreliable on non-Intel chips, but it might be different on the recent AMD one. FWIW, you can change the behavior via position_fix option, too. This is an array for multiple instances, so be careful if you have multiple HD-audio devices (likely on AMD). If you pass a non-default value (e.g. 2, which means to forcibly use the position buffer) to the second card, pass like position_fix=,2 note the comma before "2". AZX_DCAPS_SYNC_WRITE should be likely OK. It essentially enables the sync after each write for the codec communication stability, i.e. it assures each command verb is executed and waiting for the response of that command. We're going to enable this flag even for Intel chipsets, too. -- 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/1801540 Title: Microphone distorted sound on ALC892/1220 on AMD chipsets Status in Linux: Confirmed Status in linux package in Ubuntu: Won't Fix Status in pulseaudio package in Ubuntu: Won't Fix Bug description: Not sure if I'll report this upstream but there is definitely an issue with microphone recording on my desktop, this is not happening on my laptop which has a different codec. Already tried all workarounds possible, no luck. Only with my desktop with this particular motherboard. No issues in Windows, the sound recorded in there is distorted and has some static and robotic tone on high-pitch. alsa-info on the attachments To manage notifications about this bug go to: https://bugs.launchpad.net/linux/+bug/1801540/+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 1801540]
Tried quite a lot of different combination of quirks and older or latest bios with the provided patch, nothing helps. The noise frequency changes, but it is still unusable. -- 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/1801540 Title: Microphone distorted sound on ALC892/1220 on AMD chipsets Status in Linux: Confirmed Status in linux package in Ubuntu: Won't Fix Status in pulseaudio package in Ubuntu: Won't Fix Bug description: Not sure if I'll report this upstream but there is definitely an issue with microphone recording on my desktop, this is not happening on my laptop which has a different codec. Already tried all workarounds possible, no luck. Only with my desktop with this particular motherboard. No issues in Windows, the sound recorded in there is distorted and has some static and robotic tone on high-pitch. alsa-info on the attachments To manage notifications about this bug go to: https://bugs.launchpad.net/linux/+bug/1801540/+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 1801540]
(In reply to Takashi Iwai from comment #132) > Then possibly the playback needs LPIB while the capture position buffer? > A patch like below... Nope, that didn't work. Playback was fine and recording was still crackling. Is everyone affected here on 1022:1457 btw? -- 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/1801540 Title: Microphone distorted sound on ALC892/1220 on AMD chipsets Status in Linux: Confirmed Status in linux package in Ubuntu: Won't Fix Status in pulseaudio package in Ubuntu: Won't Fix Bug description: Not sure if I'll report this upstream but there is definitely an issue with microphone recording on my desktop, this is not happening on my laptop which has a different codec. Already tried all workarounds possible, no luck. Only with my desktop with this particular motherboard. No issues in Windows, the sound recorded in there is distorted and has some static and robotic tone on high-pitch. alsa-info on the attachments To manage notifications about this bug go to: https://bugs.launchpad.net/linux/+bug/1801540/+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 1801540]
Any additional option that we can try to fix this issue, besides trying to contact AMD again for the chipset docs? -- 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/1801540 Title: Microphone distorted sound on ALC892/1220 on AMD chipsets Status in Linux: Confirmed Status in linux package in Ubuntu: Won't Fix Status in pulseaudio package in Ubuntu: Won't Fix Bug description: Not sure if I'll report this upstream but there is definitely an issue with microphone recording on my desktop, this is not happening on my laptop which has a different codec. Already tried all workarounds possible, no luck. Only with my desktop with this particular motherboard. No issues in Windows, the sound recorded in there is distorted and has some static and robotic tone on high-pitch. alsa-info on the attachments To manage notifications about this bug go to: https://bugs.launchpad.net/linux/+bug/1801540/+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 1801540]
(In reply to Ernst Sjöstrand from comment #137) > (In reply to Takashi Iwai from comment #132) > > Then possibly the playback needs LPIB while the capture position buffer? > > A patch like below... > > Nope, that didn't work. Playback was fine and recording was still crackling. > > Is everyone affected here on 1022:1457 btw? >From me yes, but if you check the posted alsa-config, most of them are 1022:1457. Mine is the same. -- 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/1801540 Title: Microphone distorted sound on ALC892/1220 on AMD chipsets Status in Linux: Confirmed Status in linux package in Ubuntu: Won't Fix Status in pulseaudio package in Ubuntu: Won't Fix Bug description: Not sure if I'll report this upstream but there is definitely an issue with microphone recording on my desktop, this is not happening on my laptop which has a different codec. Already tried all workarounds possible, no luck. Only with my desktop with this particular motherboard. No issues in Windows, the sound recorded in there is distorted and has some static and robotic tone on high-pitch. alsa-info on the attachments To manage notifications about this bug go to: https://bugs.launchpad.net/linux/+bug/1801540/+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 1801540]
Created attachment 284085 Test patch with all DCAPS enabled for 1022:1457 -- 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/1801540 Title: Microphone distorted sound on ALC892/1220 on AMD chipsets Status in Linux: Confirmed Status in linux package in Ubuntu: Won't Fix Status in pulseaudio package in Ubuntu: Won't Fix Bug description: Not sure if I'll report this upstream but there is definitely an issue with microphone recording on my desktop, this is not happening on my laptop which has a different codec. Already tried all workarounds possible, no luck. Only with my desktop with this particular motherboard. No issues in Windows, the sound recorded in there is distorted and has some static and robotic tone on high-pitch. alsa-info on the attachments To manage notifications about this bug go to: https://bugs.launchpad.net/linux/+bug/1801540/+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 1801540]
(In reply to Takashi Iwai from comment #143) > The crucial point isn't about the DCAPS changes. Rather other points, e.g. > setting the non-cache mode *in addition* to the DCAPS changes, trying with > different formats, rates, period/buffer sizes on the modified setup, etc. > And all these combos. > > Basically, adding putting DCAPS* flags don't make sense because some of them > are mutual exclusive. Rather what I asked is to test to enable each DCAPS_* > one by one. But this test doesn't look so promising, so it'd be needed only > to make sure for now. > > Also, position_fix and bdl_pos_adj are another interesting parameters. The > test patch recently provided was based on the information about the > position_fix matters... > > Above all, the primary tests must be done via aplay/arecord with -Dhw > option, not with PulseAudio. > > *** > > What we need to know at this point is whether the problem happens at > transferring the data itself, the update timing problem, or some problem in > the codec side. > > The common problems in the past are mostly the first two items: the first > one is usually influenced by the memory cache coherency, and the second one > is the LPIB reporting / position buffer instability or the FIFO size > management. Both might be mixed together, too. > > I mentioned to test with aplay/arecord because PA is very sensible > especially about the second (timing) problem. If aplay/arecord -Dhw with a > large buffer and period works, it implies that the data transfer itself is > fine, for example. > > So, we still need to gather the facts. For that, the precise information > about *what* you tested is important. "I tested all" doesn't give you any > clue, after all ;) Found a combination of parameters that seems to fix the issue with arecord, at least for 30 seconds, regardless of the sample rate (eg. 44100, 48000 or 192000, all now are clear recordings) is: pasuspender -- arecord -D hw:1,0 -f S32_LE -r44100 -d 10 -N -c 2 /tmp/test.wav The key parameters required are S32_LE as a format and the non blocking mode -N, otherwise the issue is still present. I hope that this will help to track down the issue. If other people here want to try it out to see if this fix their audio problems, that would be useful as well. -- 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/1801540 Title: Microphone distorted sound on ALC892/1220 on AMD chipsets Status in Linux: Confirmed Status in linux package in Ubuntu: Won't Fix Status in pulseaudio package in Ubuntu: Won't Fix Bug description: Not sure if I'll report this upstream but there is definitely an issue with microphone recording on my desktop, this is not happening on my laptop which has a different codec. Already tried all workarounds possible, no luck. Only with my desktop with this particular motherboard. No issues in Windows, the sound recorded in there is distorted and has some static and robotic tone on high-pitch. alsa-info on the attachments To manage notifications about this bug go to: https://bugs.launchpad.net/linux/+bug/1801540/+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 1801540]
Hm, that's werid. Basically non-blocking mode matters only at opening
the PCM device (whether the stream is busy or not), and it shouldn't
influence on the running stream. Maybe it's a timing issue, like other
tests failed sometimes...
Did you already try using non-cached buffer in addition to the ATI-SB snooping?
Try the change like the below:
--- a/sound/pci/hda/hda_intel.c
+++ b/sound/pci/hda/hda_intel.c
@@ -1986,7 +1986,7 @@ static int dma_alloc_pages(struct hdac_bus *bus,
{
struct azx *chip = bus_to_azx(bus);
- if (!azx_snoop(chip) && type == SNDRV_DMA_TYPE_DEV)
+ if (/*!azx_snoop(chip) &&*/ type == SNDRV_DMA_TYPE_DEV)
type = SNDRV_DMA_TYPE_DEV_UC;
return snd_dma_alloc_pages(type, bus->dev, size, buf);
}
@@ -2002,7 +2002,7 @@ static void pcm_mmap_prepare(struct snd_pcm_substream
*substream,
#ifdef CONFIG_X86
struct azx_pcm *apcm = snd_pcm_substream_chip(substream);
struct azx *chip = apcm->chip;
- if (chip->uc_buffer)
+ if (1 /*chip->uc_buffer*/)
area->vm_page_prot = pgprot_writecombine(area->vm_page_prot);
#endif
}
--
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/1801540
Title:
Microphone distorted sound on ALC892/1220 on AMD chipsets
Status in Linux:
Confirmed
Status in linux package in Ubuntu:
Won't Fix
Status in pulseaudio package in Ubuntu:
Won't Fix
Bug description:
Not sure if I'll report this upstream but there is definitely an issue
with microphone recording on my desktop, this is not happening on my
laptop which has a different codec.
Already tried all workarounds possible, no luck. Only with my desktop
with this particular motherboard. No issues in Windows, the sound
recorded in there is distorted and has some static and robotic tone on
high-pitch.
alsa-info on the attachments
To manage notifications about this bug go to:
https://bugs.launchpad.net/linux/+bug/1801540/+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 1801540]
(In reply to Takashi Iwai from comment #145)
> Hm, that's werid. Basically non-blocking mode matters only at opening the
> PCM device (whether the stream is busy or not), and it shouldn't influence
> on the running stream. Maybe it's a timing issue, like other tests failed
> sometimes...
>
> Did you already try using non-cached buffer in addition to the ATI-SB
> snooping?
> Try the change like the below:
>
> --- a/sound/pci/hda/hda_intel.c
> +++ b/sound/pci/hda/hda_intel.c
> @@ -1986,7 +1986,7 @@ static int dma_alloc_pages(struct hdac_bus *bus,
> {
> struct azx *chip = bus_to_azx(bus);
>
> - if (!azx_snoop(chip) && type == SNDRV_DMA_TYPE_DEV)
> + if (/*!azx_snoop(chip) &&*/ type == SNDRV_DMA_TYPE_DEV)
> type = SNDRV_DMA_TYPE_DEV_UC;
> return snd_dma_alloc_pages(type, bus->dev, size, buf);
> }
> @@ -2002,7 +2002,7 @@ static void pcm_mmap_prepare(struct snd_pcm_substream
> *substream,
> #ifdef CONFIG_X86
> struct azx_pcm *apcm = snd_pcm_substream_chip(substream);
> struct azx *chip = apcm->chip;
> - if (chip->uc_buffer)
> + if (1 /*chip->uc_buffer*/)
> area->vm_page_prot = pgprot_writecombine(area->vm_page_prot);
> #endif
> }
Yes, the issue is still present. I've applied attachment 283955 and your
last patch together.
--
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/1801540
Title:
Microphone distorted sound on ALC892/1220 on AMD chipsets
Status in Linux:
Confirmed
Status in linux package in Ubuntu:
Won't Fix
Status in pulseaudio package in Ubuntu:
Won't Fix
Bug description:
Not sure if I'll report this upstream but there is definitely an issue
with microphone recording on my desktop, this is not happening on my
laptop which has a different codec.
Already tried all workarounds possible, no luck. Only with my desktop
with this particular motherboard. No issues in Windows, the sound
recorded in there is distorted and has some static and robotic tone on
high-pitch.
alsa-info on the attachments
To manage notifications about this bug go to:
https://bugs.launchpad.net/linux/+bug/1801540/+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 1801540]
The crucial point isn't about the DCAPS changes. Rather other points, e.g. setting the non-cache mode *in addition* to the DCAPS changes, trying with different formats, rates, period/buffer sizes on the modified setup, etc. And all these combos. Basically, adding putting DCAPS* flags don't make sense because some of them are mutual exclusive. Rather what I asked is to test to enable each DCAPS_* one by one. But this test doesn't look so promising, so it'd be needed only to make sure for now. Also, position_fix and bdl_pos_adj are another interesting parameters. The test patch recently provided was based on the information about the position_fix matters... Above all, the primary tests must be done via aplay/arecord with -Dhw option, not with PulseAudio. *** What we need to know at this point is whether the problem happens at transferring the data itself, the update timing problem, or some problem in the codec side. The common problems in the past are mostly the first two items: the first one is usually influenced by the memory cache coherency, and the second one is the LPIB reporting / position buffer instability or the FIFO size management. Both might be mixed together, too. I mentioned to test with aplay/arecord because PA is very sensible especially about the second (timing) problem. If aplay/arecord -Dhw with a large buffer and period works, it implies that the data transfer itself is fine, for example. So, we still need to gather the facts. For that, the precise information about *what* you tested is important. "I tested all" doesn't give you any clue, after all ;) -- 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/1801540 Title: Microphone distorted sound on ALC892/1220 on AMD chipsets Status in Linux: Confirmed Status in linux package in Ubuntu: Won't Fix Status in pulseaudio package in Ubuntu: Won't Fix Bug description: Not sure if I'll report this upstream but there is definitely an issue with microphone recording on my desktop, this is not happening on my laptop which has a different codec. Already tried all workarounds possible, no luck. Only with my desktop with this particular motherboard. No issues in Windows, the sound recorded in there is distorted and has some static and robotic tone on high-pitch. alsa-info on the attachments To manage notifications about this bug go to: https://bugs.launchpad.net/linux/+bug/1801540/+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 1801540]
Also, did anyone try different position_fix options, e.g. 5,5 or 4,4? 4,4 should be equivalent with my previous test patch, so it's not expected to work. But it's still interesting to know whether the recording with such an option proceeds at all. If the stream can be recorded for the expected length, no matter whether it's noisy or not, it means that the position buffer does work in some level. OTOH, if the stream can't be recorded at all (e.g. you get the DMA or stall error), the position buffer is broken on AMD platform. -- 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/1801540 Title: Microphone distorted sound on ALC892/1220 on AMD chipsets Status in Linux: Confirmed Status in linux package in Ubuntu: Won't Fix Status in pulseaudio package in Ubuntu: Won't Fix Bug description: Not sure if I'll report this upstream but there is definitely an issue with microphone recording on my desktop, this is not happening on my laptop which has a different codec. Already tried all workarounds possible, no luck. Only with my desktop with this particular motherboard. No issues in Windows, the sound recorded in there is distorted and has some static and robotic tone on high-pitch. alsa-info on the attachments To manage notifications about this bug go to: https://bugs.launchpad.net/linux/+bug/1801540/+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 1801540]
No need for retest, bdl_pos_adj is merely a shot-in-the-dark, and likely breaks something else :) -- 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/1801540 Title: Microphone distorted sound on ALC892/1220 on AMD chipsets Status in Linux: Confirmed Status in linux package in Ubuntu: Won't Fix Status in pulseaudio package in Ubuntu: Won't Fix Bug description: Not sure if I'll report this upstream but there is definitely an issue with microphone recording on my desktop, this is not happening on my laptop which has a different codec. Already tried all workarounds possible, no luck. Only with my desktop with this particular motherboard. No issues in Windows, the sound recorded in there is distorted and has some static and robotic tone on high-pitch. alsa-info on the attachments To manage notifications about this bug go to: https://bugs.launchpad.net/linux/+bug/1801540/+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
