[Touch-packages] [Bug 1833536] Autopkgtest regression report (qtbase-opensource-src/5.9.5+dfsg-0ubuntu2.3)
All autopkgtests for the newly accepted qtbase-opensource-src (5.9.5+dfsg-0ubuntu2.3) for bionic have finished running. There have been regressions in tests triggered by the package. Please visit the sru report page and investigate the failures. https://people.canonical.com/~ubuntu-archive/pending-sru.html#bionic -- 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 Committed 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] Autopkgtest regression report (qtbase-opensource-src/5.9.5+dfsg-0ubuntu2.3)
All autopkgtests for the newly accepted qtbase-opensource-src (5.9.5+dfsg-0ubuntu2.3) for bionic have finished running. There have been regressions in tests triggered by the package. Please visit the sru report page and investigate the failures. https://people.canonical.com/~ubuntu-archive/pending-sru.html#bionic -- 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 Committed 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 1830169] Re: lvm udev rule fails to call systemd-run
Successfully verified on bionic - adjusting verification-needed-bionic
tag.
** Attachment added: "verification-bionic.txt"
https://bugs.launchpad.net/ubuntu/+source/lvm2/+bug/1830169/+attachment/5274489/+files/verification-bionic.txt
** Tags removed: verification-needed-bionic
** Tags added: verification-done-bionic
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to lvm2 in Ubuntu.
https://bugs.launchpad.net/bugs/1830169
Title:
lvm udev rule fails to call systemd-run
Status in Ubuntu on IBM z Systems:
Fix Committed
Status in lvm2 package in Ubuntu:
Fix Released
Status in lvm2 source package in Xenial:
Fix Committed
Status in lvm2 source package in Bionic:
Fix Committed
Status in lvm2 source package in Cosmic:
Fix Released
Status in lvm2 source package in Disco:
Fix Released
Status in lvm2 source package in Eoan:
Fix Released
Bug description:
[Impact]
Judging from the rule, this probably means that volumes do not disappear when
the physical volume disappears.
[Test case]
Not available. But since it's just a path fix, it should not be a problem.
[Regression potential]
Removal might now actually work correctly, but it's not entirely clear how
that could cause a regression.
[Other info]
In /lib/udev/rules.d/69-lvm-metad.rules file, it calls /bin/systemd-run
command during removal ---
ACTION!="remove", ENV{LVM_PV_GONE}=="1", RUN+="/bin/systemd-run /sbin/lvm
pvscan --cache $major:$minor", GOTO="lvm_end"
But /bin/systemd-run is not found, in fact systemd-run is in /usr/bin
/systemd-run.
xx:~$ cat /etc/issue
Ubuntu 18.04.2 LTS \n \l
xx:~$ ls /bin/systemd-run
ls: cannot access '/bin/systemd-run': No such file or directory
xx:~$ ls /usr/bin/systemd-run
/usr/bin/systemd-run
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu-z-systems/+bug/1830169/+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 1832458] Re: [SRU] 2.60.3
This bug was fixed in the package glib-networking - 2.60.3-1~ubuntu19.04.1 --- glib-networking (2.60.3-1~ubuntu19.04.1) disco; urgency=medium * No-change backport from experimental / eoan to disco to SRU this stable update. glib-networking (2.60.3-1) experimental; urgency=medium * New upstream release (LP: #1832458) - Fix clobbering of the thread-default main context after certificate verification failure during async handshakes since 2.60.1 - Fix GTlsDatabase initialization failures in OpenSSL backend due to uninitialized memory use - Fix minor leak of ALPN protocols - OpenSSL backend now defaults to system trust store - Fix client auth failure error with GnuTLS 3.6.7 * gnutls-Handle-new-GNUTLS_E_CERTIFICATE_REQUIRED.patch: Drop. It's in this upstream release. -- Iain Lane Wed, 12 Jun 2019 10:12:46 +0100 ** Changed in: glib-networking (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 glib-networking in Ubuntu. https://bugs.launchpad.net/bugs/1832458 Title: [SRU] 2.60.3 Status in glib-networking package in Ubuntu: Fix Released Status in glib-networking source package in Disco: Fix Released Bug description: [ Description ] Upstream have release 2.60.3 in the 2.60 series [ QA ] Upstream release, so QA already performed by maintainers https://wiki.ubuntu.com/StableReleaseUpdates/GNOME Make sure no autopkgtests are regressed by this upload. Suggestion for something explicit to test would be epiphany on secure websites. [ Regression potential ] A broken glib-networking could affect various applications' ability to use networking properly, particularly TLS. [ Upstream NEWS ] 2.60.3 - June 9, 2019 = - Fix clobbering of the thread-default main context after certificate verification failure during async handshakes since 2.60.1 (#85) - Fix GTlsDatabase initialization failures in OpenSSL backend due to uninitialized memory use - Fix minor leak of ALPN protocols 2.60.2 - May 2, 2019 - OpenSSL backend now defaults to system trust store (#62) - Fix client auth failure error with GnuTLS 3.6.7 (#70) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/glib-networking/+bug/1832458/+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 1832458] Update Released
The verification of the Stable Release Update for glib-networking 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 glib-networking in Ubuntu. https://bugs.launchpad.net/bugs/1832458 Title: [SRU] 2.60.3 Status in glib-networking package in Ubuntu: Fix Released Status in glib-networking source package in Disco: Fix Released Bug description: [ Description ] Upstream have release 2.60.3 in the 2.60 series [ QA ] Upstream release, so QA already performed by maintainers https://wiki.ubuntu.com/StableReleaseUpdates/GNOME Make sure no autopkgtests are regressed by this upload. Suggestion for something explicit to test would be epiphany on secure websites. [ Regression potential ] A broken glib-networking could affect various applications' ability to use networking properly, particularly TLS. [ Upstream NEWS ] 2.60.3 - June 9, 2019 = - Fix clobbering of the thread-default main context after certificate verification failure during async handshakes since 2.60.1 (#85) - Fix GTlsDatabase initialization failures in OpenSSL backend due to uninitialized memory use - Fix minor leak of ALPN protocols 2.60.2 - May 2, 2019 - OpenSSL backend now defaults to system trust store (#62) - Fix client auth failure error with GnuTLS 3.6.7 (#70) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/glib-networking/+bug/1832458/+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 1834782] Re: ASUS Zenbook UX433FN: sound stops working after a couple of seconds
This looks like it's a driver/kernel related issue, can you explain to me how the sound could be working for a couple of seconds and then stops? -- 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/1834782 Title: ASUS Zenbook UX433FN: sound stops working after a couple of seconds Status in linux-firmware package in Ubuntu: New Status in linux-hwe package in Ubuntu: New Status in linux-hwe-edge package in Ubuntu: New Status in pulseaudio package in Ubuntu: Invalid Bug description: Issue: whichever sound-related action (sound +/- media keys, spotify song, youtube vid in browser,...) I do, the sound works OK for about 2-3 seconds, and then stops and becomes silent. The interesting thing is that when I stop playing the audio (ie close the browser tab with a song), after a while when I try aain the sound works again. Yet still for just the few secs. Environment: up-to-date Ubuntu 18.04, tried -hwe, hwe-edge kernels. This is a regression, the sound used to work OK on this machine, and nothing significant related to sound has changed since. Thank you for looking into this bug! --- ProblemType: Bug ApportVersion: 2.20.9-0ubuntu7.6 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: mmm 28065 F pulseaudio CurrentDesktop: KDE CurrentDmesg: Error: command ['dmesg'] failed with exit code 1: dmesg: read kernel buffer failed: Operation not permitted Dependencies: DistroRelease: KDE neon 18.04 InstallationDate: Installed on 2012-12-23 (2380 days ago) InstallationMedia: Kubuntu 12.10 "Quantal Quetzal" - Release amd64 (20121017.1) Package: pulseaudio PackageArchitecture: all ProcVersionSignature: Ubuntu 4.18.0-25.26~18.04.1-generic 4.18.20 Tags: bionic wayland-session third-party-packages wayland-session Uname: Linux 4.18.0-25-generic x86_64 UnreportableReason: Toto není oficiální KDE balík. Prosíme odstraňte všechny balíky třetích stran a zkuste to znovu. UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm libvirtd lpadmin netdev plugdev sudo video _MarkForUpload: True dmi.bios.date: 04/24/2019 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: UX433FN.306 dmi.board.asset.tag: ATN12345678901234567 dmi.board.name: UX433FN dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: 1.0 dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: ASUSTeK COMPUTER INC. dmi.chassis.version: 1.0 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrUX433FN.306:bd04/24/2019:svnASUSTeKCOMPUTERINC.:pnZenBookUX433FN_UX433FN:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnUX433FN:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0: dmi.product.family: ZenBook dmi.product.name: ZenBook UX433FN_UX433FN dmi.product.version: 1.0 dmi.sys.vendor: ASUSTeK COMPUTER INC. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-firmware/+bug/1834782/+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
Hello William, or anyone else affected, Accepted qtbase-opensource-src into disco-proposed. The package will build now and be available at https://launchpad.net/ubuntu/+source /qtbase-opensource-src/5.12.2+dfsg-4ubuntu1.1 in a few hours, and then in the -proposed repository. Please help us by testing this new package. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation on how to enable and use -proposed. Your feedback will aid us getting this update out to other Ubuntu users. If this package fixes the bug for you, please add a comment to this bug, mentioning the version of the package you tested and change the tag from verification-needed-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: qtbase-opensource-src (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 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: In Progress Status in qtbase-opensource-src source package in Disco: Fix Committed 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
[Touch-packages] [Bug 1531184] Re: [SRU] dnsmasq doesn't start on boot because its interface isn't up yet
The reference paelzer references is related to Ubuntu 14.04. In Ubuntu 18.04, "/etc/netplan/01-network-manager-all.yaml" defaults all network device management to NetworkManager. Therefore any solution will have to be to NetworkManager's systemd service file. My solution which I've tested and consistently raises dnsmasq up only after the interfaces are up in 18.04 is as follows: sed -i 's/After=network.target/After=NetworkManager-wait- online.service/' /lib/systemd/system/dnsmasq.service The 18.04 askubuntu related link is: https://askubuntu.com/questions/1124530/systemd-starts-dnsmasq-before-starting-network-manager/1154727#1154727 -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to dnsmasq in Ubuntu. https://bugs.launchpad.net/bugs/1531184 Title: [SRU] dnsmasq doesn't start on boot because its interface isn't up yet Status in One Hundred Papercuts: Confirmed Status in dnsmasq package in Ubuntu: Confirmed Status in dnsmasq package in Debian: New Bug description: [Impact] TBD [Test Case] TBD [Regression Potential] The fix is just configuring the order of service startup, so is unlikely to create any regressions. Things to watch would be service related misbehaviors and general availability of the dnsmasq functionality. [Fix] https://bugs.debian.org/cgi-bin/bugreport.cgi?att=1;bug=774970;filename=774970-network-online.debdiff;msg=22 [Discussion] [Original Report] My dnsmasq instance uses "interface=br-vz0" and the interface br-vz0 is managed manually in /etc/network/interfaces. During boot, dnsmasq is started before br-vz0 is created and this causes dnsmasq to exit: Jan 5 08:56:16 simon-laptop dnsmasq[1008]: dnsmasq: unknown interface br-vz0 Jan 5 08:56:16 simon-laptop dnsmasq[1008]: unknown interface br-vz0 Jan 5 08:56:16 simon-laptop dnsmasq[1008]: FAILED to start up Jan 5 08:56:17 simon-laptop NetworkManager[937]: NetworkManager (version 1.0.4) is starting... ... Jan 5 08:56:18 simon-laptop NetworkManager[937]: interface-parser: parsing file /etc/network/interfaces ... Jan 5 08:56:18 simon-laptop NetworkManager[937]: found bridge ports none for br-vz0 Jan 5 08:56:18 simon-laptop NetworkManager[937]: adding bridge port none to eni_ifaces Jan 5 08:56:18 simon-laptop NetworkManager[937]: management mode: unmanaged ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: dnsmasq 2.75-1 ProcVersionSignature: Ubuntu 4.3.0-5.16-generic 4.3.3 Uname: Linux 4.3.0-5-generic x86_64 ApportVersion: 2.19.3-0ubuntu2 Architecture: amd64 CurrentDesktop: Unity Date: Tue Jan 5 09:53:30 2016 PackageArchitecture: all SourcePackage: dnsmasq UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/hundredpapercuts/+bug/1531184/+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 1834836] [NEW] graphics driver doesnt install
Public bug reported: brightness button does not work neither does the system shows intel grahics nor amd ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: xorg 1:7.7+19ubuntu7.1 ProcVersionSignature: Ubuntu 4.18.0-22.23~18.04.1-generic 4.18.20 Uname: Linux 4.18.0-22-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.6 Architecture: amd64 CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Mon Jul 1 14:27:03 2019 DistUpgraded: Fresh install DistroCodename: bionic DistroVariant: ubuntu ExtraDebuggingInterest: I just need to know a workaround GraphicsCard: Intel Corporation HD Graphics 620 [8086:5916] (rev 02) (prog-if 00 [VGA controller]) Subsystem: Dell HD Graphics 620 [1028:0767] Subsystem: Dell Radeon R7 M445 [1028:0767] InstallationDate: Installed on 2019-06-19 (11 days ago) InstallationMedia: Ubuntu 18.04.2 LTS "Bionic Beaver" - Release amd64 (20190210) Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 004: ID 8087:0a2a Intel Corp. Bus 001 Device 003: ID 0bda:0129 Realtek Semiconductor Corp. RTS5129 Card Reader Controller Bus 001 Device 002: ID 0bda:568a Realtek Semiconductor Corp. Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: Dell Inc. Inspiron 5567 ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz root=UUID=5362bffc-ce49-49e3-91eb-535ce68e4dc8 verbose nomodeset SourcePackage: xorg UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 01/09/2019 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.2.7 dmi.board.name: 05VRRG dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 10 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr1.2.7:bd01/09/2019:svnDellInc.:pnInspiron5567:pvr:rvnDellInc.:rn05VRRG:rvrA00:cvnDellInc.:ct10:cvr: dmi.product.family: Inspiron dmi.product.name: Inspiron 5567 dmi.product.sku: 0767 dmi.sys.vendor: Dell Inc. version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.98+git1906281830.cecedc~oibaf~b version.libgl1-mesa-dri: libgl1-mesa-dri 19.2~git1906301930.75d8b4~oibaf~b version.libgl1-mesa-glx: libgl1-mesa-glx 19.2~git1906301930.75d8b4~oibaf~b version.xserver-xorg-core: xserver-xorg-core N/A version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati N/A version.xserver-xorg-video-intel: xserver-xorg-video-intel N/A version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau N/A ** Affects: xorg (Ubuntu) Importance: Low Status: Incomplete ** Tags: amd64 apport-bug bionic third-party-packages ubuntu -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to xorg in Ubuntu. https://bugs.launchpad.net/bugs/1834836 Title: graphics driver doesnt install Status in xorg package in Ubuntu: Incomplete Bug description: brightness button does not work neither does the system shows intel grahics nor amd ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: xorg 1:7.7+19ubuntu7.1 ProcVersionSignature: Ubuntu 4.18.0-22.23~18.04.1-generic 4.18.20 Uname: Linux 4.18.0-22-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.6 Architecture: amd64 CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Mon Jul 1 14:27:03 2019 DistUpgraded: Fresh install DistroCodename: bionic DistroVariant: ubuntu ExtraDebuggingInterest: I just need to know a workaround GraphicsCard: Intel Corporation HD Graphics 620 [8086:5916] (rev 02) (prog-if 00 [VGA controller]) Subsystem: Dell HD Graphics 620 [1028:0767] Subsystem: Dell Radeon R7 M445 [1028:0767] InstallationDate: Installed on 2019-06-19 (11 days ago) InstallationMedia: Ubuntu 18.04.2 LTS "Bionic Beaver" - Release amd64 (20190210) Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 004: ID 8087:0a2a Intel Corp. Bus 001 Device 003: ID 0bda:0129 Realtek Semiconductor Corp. RTS5129 Card Reader Controller Bus 001 Device 002: ID 0bda:568a Realtek Semiconductor Corp. Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: Dell Inc. Inspiron 5567 ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz root=UUID=5362bffc-ce49-49e3-91eb-535ce68e4dc8 verbose nomodeset SourcePackage: xorg UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 01/09/2019 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.2.7 dmi.board.name: 05VRRG dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 10 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr1.2.7:bd01/09/2019:svnDellInc.:pnInspiron5567:pvr:rvnDellInc.:rn05VRRG:rvrA00:cvnDellInc.:ct10:cvr: dmi.product.family: Inspiron dmi.product.name: Inspiron 5567 dmi.product.sku: 0767 dmi.sys.vendor: Dell Inc. version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.98+git1906281830.cecedc~oibaf~b version.libgl1-mesa-dri: libgl1-mesa-dri 19.2~git1906301930.75d8b4~oibaf~b
[Touch-packages] [Bug 1833793] Re: Updating to 19.04 audio keeps clicking when nothing is playing audio
** Changed in: alsa-driver (Ubuntu) Importance: Undecided => High ** Changed in: alsa-driver (Ubuntu) Status: New => Incomplete -- 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/1833793 Title: Updating to 19.04 audio keeps clicking when nothing is playing audio Status in alsa-driver package in Ubuntu: Incomplete Bug description: My Ubuntu version: Ubuntu 19.04 My sound card: Intel Corporation 82801H (ICH8 Family) HD Audio Controller (rev 02) What I expect to happen: Sound is absolutely quiet when no audio is playing What happens now: Audio output starts clicking every second incredibly annoyingly and loud. What previously happened on Ubuntu 18.10: I heard the click twice during boot and then it worked properly (without clicking during the time it should have been silent) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1833793/+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 1834836] Re: graphics driver doesnt install
Thank you for taking the time to report this bug and helping to make Ubuntu better. The issue you are reporting is an upstream one and it would be nice if somebody having it could send the bug to the developers of the software by following the instructions at https://wiki.ubuntu.com/Bugs/Upstream/GNOME. If you have done so, please tell us the number of the upstream bug (or the link), so we can add a bugwatch that will inform us about its status. Thanks in advance. ** Changed in: xorg (Ubuntu) Importance: Undecided => Low ** Changed in: xorg (Ubuntu) Status: New => Incomplete -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to xorg in Ubuntu. https://bugs.launchpad.net/bugs/1834836 Title: Brightness controls don't work on Dell Inspiron 5567 Status in linux package in Ubuntu: Incomplete Bug description: brightness button does not work neither does the system shows intel grahics nor amd ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: xorg 1:7.7+19ubuntu7.1 ProcVersionSignature: Ubuntu 4.18.0-22.23~18.04.1-generic 4.18.20 Uname: Linux 4.18.0-22-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.6 Architecture: amd64 CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Mon Jul 1 14:27:03 2019 DistUpgraded: Fresh install DistroCodename: bionic DistroVariant: ubuntu ExtraDebuggingInterest: I just need to know a workaround GraphicsCard: Intel Corporation HD Graphics 620 [8086:5916] (rev 02) (prog-if 00 [VGA controller]) Subsystem: Dell HD Graphics 620 [1028:0767] Subsystem: Dell Radeon R7 M445 [1028:0767] InstallationDate: Installed on 2019-06-19 (11 days ago) InstallationMedia: Ubuntu 18.04.2 LTS "Bionic Beaver" - Release amd64 (20190210) Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 004: ID 8087:0a2a Intel Corp. Bus 001 Device 003: ID 0bda:0129 Realtek Semiconductor Corp. RTS5129 Card Reader Controller Bus 001 Device 002: ID 0bda:568a Realtek Semiconductor Corp. Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: Dell Inc. Inspiron 5567 ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz root=UUID=5362bffc-ce49-49e3-91eb-535ce68e4dc8 verbose nomodeset SourcePackage: xorg UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 01/09/2019 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.2.7 dmi.board.name: 05VRRG dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 10 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr1.2.7:bd01/09/2019:svnDellInc.:pnInspiron5567:pvr:rvnDellInc.:rn05VRRG:rvrA00:cvnDellInc.:ct10:cvr: dmi.product.family: Inspiron dmi.product.name: Inspiron 5567 dmi.product.sku: 0767 dmi.sys.vendor: Dell Inc. version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.98+git1906281830.cecedc~oibaf~b version.libgl1-mesa-dri: libgl1-mesa-dri 19.2~git1906301930.75d8b4~oibaf~b version.libgl1-mesa-glx: libgl1-mesa-glx 19.2~git1906301930.75d8b4~oibaf~b version.xserver-xorg-core: xserver-xorg-core N/A version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati N/A version.xserver-xorg-video-intel: xserver-xorg-video-intel N/A version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau N/A To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1834836/+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 1834836] Re: Brightness controls don't work on Dell Inspiron 5567
Also, your kernel is booted with modesetting disabled. Please remove the 'nomodeset' kernel parameter and then run: sudo update-initramfs and reboot. Does brightness now work? If not then please re-run: ls -l /sys/class/backlight/ and tell us what it says. ** Package changed: xorg (Ubuntu) => linux (Ubuntu) -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to xorg in Ubuntu. https://bugs.launchpad.net/bugs/1834836 Title: Brightness controls don't work on Dell Inspiron 5567 Status in linux package in Ubuntu: Incomplete Bug description: brightness button does not work neither does the system shows intel grahics nor amd ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: xorg 1:7.7+19ubuntu7.1 ProcVersionSignature: Ubuntu 4.18.0-22.23~18.04.1-generic 4.18.20 Uname: Linux 4.18.0-22-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.6 Architecture: amd64 CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Mon Jul 1 14:27:03 2019 DistUpgraded: Fresh install DistroCodename: bionic DistroVariant: ubuntu ExtraDebuggingInterest: I just need to know a workaround GraphicsCard: Intel Corporation HD Graphics 620 [8086:5916] (rev 02) (prog-if 00 [VGA controller]) Subsystem: Dell HD Graphics 620 [1028:0767] Subsystem: Dell Radeon R7 M445 [1028:0767] InstallationDate: Installed on 2019-06-19 (11 days ago) InstallationMedia: Ubuntu 18.04.2 LTS "Bionic Beaver" - Release amd64 (20190210) Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 004: ID 8087:0a2a Intel Corp. Bus 001 Device 003: ID 0bda:0129 Realtek Semiconductor Corp. RTS5129 Card Reader Controller Bus 001 Device 002: ID 0bda:568a Realtek Semiconductor Corp. Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: Dell Inc. Inspiron 5567 ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz root=UUID=5362bffc-ce49-49e3-91eb-535ce68e4dc8 verbose nomodeset SourcePackage: xorg UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 01/09/2019 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.2.7 dmi.board.name: 05VRRG dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 10 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr1.2.7:bd01/09/2019:svnDellInc.:pnInspiron5567:pvr:rvnDellInc.:rn05VRRG:rvrA00:cvnDellInc.:ct10:cvr: dmi.product.family: Inspiron dmi.product.name: Inspiron 5567 dmi.product.sku: 0767 dmi.sys.vendor: Dell Inc. version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.98+git1906281830.cecedc~oibaf~b version.libgl1-mesa-dri: libgl1-mesa-dri 19.2~git1906301930.75d8b4~oibaf~b version.libgl1-mesa-glx: libgl1-mesa-glx 19.2~git1906301930.75d8b4~oibaf~b version.xserver-xorg-core: xserver-xorg-core N/A version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati N/A version.xserver-xorg-video-intel: xserver-xorg-video-intel N/A version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau N/A To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1834836/+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 1834836] Re: Brightness controls don't work on Dell Inspiron 5567
Please: 1. Remove the 'oidbaf' PPA from your machine. It is not supported by Ubuntu. 2. Run this command and tell us what result you see: ls -l /sys/class/backlight/ ** Summary changed: - graphics driver doesnt install + Brightness controls don't work on Dell Inspiron 5567 -- 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/1834836 Title: Brightness controls don't work on Dell Inspiron 5567 Status in linux package in Ubuntu: Incomplete Bug description: brightness button does not work neither does the system shows intel grahics nor amd ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: xorg 1:7.7+19ubuntu7.1 ProcVersionSignature: Ubuntu 4.18.0-22.23~18.04.1-generic 4.18.20 Uname: Linux 4.18.0-22-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.6 Architecture: amd64 CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Mon Jul 1 14:27:03 2019 DistUpgraded: Fresh install DistroCodename: bionic DistroVariant: ubuntu ExtraDebuggingInterest: I just need to know a workaround GraphicsCard: Intel Corporation HD Graphics 620 [8086:5916] (rev 02) (prog-if 00 [VGA controller]) Subsystem: Dell HD Graphics 620 [1028:0767] Subsystem: Dell Radeon R7 M445 [1028:0767] InstallationDate: Installed on 2019-06-19 (11 days ago) InstallationMedia: Ubuntu 18.04.2 LTS "Bionic Beaver" - Release amd64 (20190210) Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 004: ID 8087:0a2a Intel Corp. Bus 001 Device 003: ID 0bda:0129 Realtek Semiconductor Corp. RTS5129 Card Reader Controller Bus 001 Device 002: ID 0bda:568a Realtek Semiconductor Corp. Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: Dell Inc. Inspiron 5567 ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz root=UUID=5362bffc-ce49-49e3-91eb-535ce68e4dc8 verbose nomodeset SourcePackage: xorg UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 01/09/2019 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.2.7 dmi.board.name: 05VRRG dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 10 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr1.2.7:bd01/09/2019:svnDellInc.:pnInspiron5567:pvr:rvnDellInc.:rn05VRRG:rvrA00:cvnDellInc.:ct10:cvr: dmi.product.family: Inspiron dmi.product.name: Inspiron 5567 dmi.product.sku: 0767 dmi.sys.vendor: Dell Inc. version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.98+git1906281830.cecedc~oibaf~b version.libgl1-mesa-dri: libgl1-mesa-dri 19.2~git1906301930.75d8b4~oibaf~b version.libgl1-mesa-glx: libgl1-mesa-glx 19.2~git1906301930.75d8b4~oibaf~b version.xserver-xorg-core: xserver-xorg-core N/A version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati N/A version.xserver-xorg-video-intel: xserver-xorg-video-intel N/A version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau N/A To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1834836/+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] Autopkgtest regression report (qtbase-opensource-src/5.12.2+dfsg-4ubuntu1.1)
All autopkgtests for the newly accepted qtbase-opensource-src (5.12.2+dfsg-4ubuntu1.1) for disco have finished running. There have been regressions in tests triggered by the package. Please visit the sru report page and investigate the failures. https://people.canonical.com/~ubuntu-archive/pending-sru.html#disco -- 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 Committed 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 1830169] Please test proposed package
Hello bugproxy, or anyone else affected,
Accepted lvm2 into xenial-proposed. The package will build now and be
available at
https://launchpad.net/ubuntu/+source/lvm2/2.02.133-1ubuntu10.1 in a few
hours, and then in the -proposed repository.
Please help us by testing this new package. See
https://wiki.ubuntu.com/Testing/EnableProposed for documentation on how
to enable and use -proposed. Your feedback will aid us getting this
update out to other Ubuntu users.
If this package fixes the bug for you, please add a comment to this bug,
mentioning the version of the package you tested and change the tag from
verification-needed-xenial to verification-done-xenial. If it does not
fix the bug for you, please add a comment stating that, and change the
tag to verification-failed-xenial. 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.
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to lvm2 in Ubuntu.
https://bugs.launchpad.net/bugs/1830169
Title:
lvm udev rule fails to call systemd-run
Status in Ubuntu on IBM z Systems:
Fix Committed
Status in lvm2 package in Ubuntu:
Fix Released
Status in lvm2 source package in Xenial:
Fix Committed
Status in lvm2 source package in Bionic:
Fix Committed
Status in lvm2 source package in Cosmic:
Fix Released
Status in lvm2 source package in Disco:
Fix Released
Status in lvm2 source package in Eoan:
Fix Released
Bug description:
[Impact]
Judging from the rule, this probably means that volumes do not disappear when
the physical volume disappears.
[Test case]
Not available. But since it's just a path fix, it should not be a problem.
[Regression potential]
Removal might now actually work correctly, but it's not entirely clear how
that could cause a regression.
[Other info]
In /lib/udev/rules.d/69-lvm-metad.rules file, it calls /bin/systemd-run
command during removal ---
ACTION!="remove", ENV{LVM_PV_GONE}=="1", RUN+="/bin/systemd-run /sbin/lvm
pvscan --cache $major:$minor", GOTO="lvm_end"
But /bin/systemd-run is not found, in fact systemd-run is in /usr/bin
/systemd-run.
xx:~$ cat /etc/issue
Ubuntu 18.04.2 LTS \n \l
xx:~$ ls /bin/systemd-run
ls: cannot access '/bin/systemd-run': No such file or directory
xx:~$ ls /usr/bin/systemd-run
/usr/bin/systemd-run
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu-z-systems/+bug/1830169/+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 1830169] Re: lvm udev rule fails to call systemd-run
Hello bugproxy, or anyone else affected,
Accepted lvm2 into bionic-proposed. The package will build now and be
available at
https://launchpad.net/ubuntu/+source/lvm2/2.02.176-4.1ubuntu3.18.04.1 in
a few hours, and then in the -proposed repository.
Please help us by testing this new package. See
https://wiki.ubuntu.com/Testing/EnableProposed for documentation on how
to enable and use -proposed. Your feedback will aid us getting this
update out to other Ubuntu users.
If this package fixes the bug for you, please add a comment to this bug,
mentioning the version of the package you tested and change the tag from
verification-needed-bionic to verification-done-bionic. If it does not
fix the bug for you, please add a comment stating that, and change the
tag to verification-failed-bionic. 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: lvm2 (Ubuntu Bionic)
Status: In Progress => Fix Committed
** Tags added: verification-needed-bionic
** Changed in: lvm2 (Ubuntu Xenial)
Status: In Progress => Fix Committed
** Tags added: verification-needed-xenial
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to lvm2 in Ubuntu.
https://bugs.launchpad.net/bugs/1830169
Title:
lvm udev rule fails to call systemd-run
Status in Ubuntu on IBM z Systems:
Fix Committed
Status in lvm2 package in Ubuntu:
Fix Released
Status in lvm2 source package in Xenial:
Fix Committed
Status in lvm2 source package in Bionic:
Fix Committed
Status in lvm2 source package in Cosmic:
Fix Released
Status in lvm2 source package in Disco:
Fix Released
Status in lvm2 source package in Eoan:
Fix Released
Bug description:
[Impact]
Judging from the rule, this probably means that volumes do not disappear when
the physical volume disappears.
[Test case]
Not available. But since it's just a path fix, it should not be a problem.
[Regression potential]
Removal might now actually work correctly, but it's not entirely clear how
that could cause a regression.
[Other info]
In /lib/udev/rules.d/69-lvm-metad.rules file, it calls /bin/systemd-run
command during removal ---
ACTION!="remove", ENV{LVM_PV_GONE}=="1", RUN+="/bin/systemd-run /sbin/lvm
pvscan --cache $major:$minor", GOTO="lvm_end"
But /bin/systemd-run is not found, in fact systemd-run is in /usr/bin
/systemd-run.
xx:~$ cat /etc/issue
Ubuntu 18.04.2 LTS \n \l
xx:~$ ls /bin/systemd-run
ls: cannot access '/bin/systemd-run': No such file or directory
xx:~$ ls /usr/bin/systemd-run
/usr/bin/systemd-run
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu-z-systems/+bug/1830169/+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] Please test proposed package
Hello Norbert, or anyone else affected, Accepted qtbase-opensource-src into bionic-proposed. The package will build now and be available at https://launchpad.net/ubuntu/+source /qtbase-opensource-src/5.9.5+dfsg-0ubuntu2.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-bionic to verification-done-bionic. If it does not fix the bug for you, please add a comment stating that, and change the tag to verification-failed-bionic. 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. -- 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 Committed 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] Re: Qt5 incorrectly interpret keypresses from remote VNC keyboard
The two patches seem a bit big (with all that refactoring), but I guess I didn't see any follow up changes to this code upstream. Also, with the regression potential well defined, I'm inclined to accept it. ** Changed in: qtbase-opensource-src (Ubuntu Bionic) Status: New => Fix Committed ** Tags added: verification-needed verification-needed-bionic -- 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 Committed 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 1833536] Re: QuiteRSS crashes intermittently
Hello William, or anyone else affected, Accepted qtbase-opensource-src into bionic-proposed. The package will build now and be available at https://launchpad.net/ubuntu/+source /qtbase-opensource-src/5.9.5+dfsg-0ubuntu2.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-bionic to verification-done-bionic. If it does not fix the bug for you, please add a comment stating that, and change the tag to verification-failed-bionic. 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: qtbase-opensource-src (Ubuntu Bionic) Status: In Progress => Fix Committed ** Tags added: verification-needed-bionic -- 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 Committed 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
[Touch-packages] [Bug 1828892] Re: systemctl - alias service reports inactive while aliased is active
Verification on Xenial. Repeating test case from description. - Test case 1 - libvirtd alias service : libvirtd aliased service : libvirt-bin # ls -la libvirtd.service lrwxrwxrwx 1 root root 39 Mar 21 16:27 libvirtd.service -> /lib/systemd/system/libvirt-bin.service # systemctl is-active libvirtd active # systemctl is-active libvirt-bin active - Test case 2 - sshd alias service : sshd aliased service : ssh # ls -la sshd.service lrwxrwxrwx 1 root root 31 Mar 21 14:39 sshd.service -> /lib/systemd/system/ssh.service # systemctl is-active sshd active # systemctl is-active ssh active # dpkg -l | grep systemd ii libpam-systemd:amd64 229-4ubuntu21.22 amd64system and service manager - PAM module ii libsystemd0:amd64229-4ubuntu21.22 amd64systemd utility library ii systemd 229-4ubuntu21.22 amd64system and service manager ii systemd-sysv 229-4ubuntu21.22 amd64system and service manager - SysV links ** Tags removed: verification-needed verification-needed-xenial ** Tags added: verification-done verification-done-xenial -- 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/1828892 Title: systemctl - alias service reports inactive while aliased is active Status in systemd package in Ubuntu: Fix Released Status in systemd source package in Xenial: Fix Committed Bug description: [Impact] 'systemctl is-active' command reports an alias service as inactive even though the aliased service is active. Currently the 'systemctl is-active' command does not load units to minimise its effect on the system (i.e. that a monitoring command does not itself alter the state of the system). However, this behaviour leads to inconsistencies when services are aliased. [Test case] - Test case 1 - libvirtd alias service : libvirtd aliased service : libvirt-bin /etc/systemd/system$ ls -la libvirtd.service lrwxrwxrwx 1 root root 39 May 13 20:49 libvirtd.service -> /lib/systemd/system/libvirt-bin.service $ systemctl is-active libvirtd inactive $ systemctl is-active libvirt-bin active - Test case 2 - sshd alias service : sshd aliased service : ssh /ect/systemd/system$ ls -la sshd.service lrwxrwxrwx 1 root root 31 Mar 19 19:44 sshd.service -> /lib/systemd/system/ssh.service $ systemctl is-active sshd inactive $ systemctl is-active ssh active [Regression Potential] This fix may result into systemctl reporting inconsistent information concerning the status of a service. [Other] Upstream issue : https://github.com/systemd/systemd/issues/7875 Upstream fix : https://github.com/systemd/systemd/pull/7997 Xenial is affected, fix exists on Bionic onward. $ lsb_release -rd Description: Ubuntu 16.04.6 LTS Release: 16.04 $ apt-cache policy systemd systemd: Installed: 229-4ubuntu21.21 Candidate: 229-4ubuntu21.21 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1828892/+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 1830169] Comment bridged from LTC Bugzilla
--- Comment From heinz-werner_se...@de.ibm.com 2019-07-01 05:17 EDT---
@Canonical: What is the current assumption for providing this update for
Xenial, and Bionic? Many thx in advance
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to lvm2 in Ubuntu.
https://bugs.launchpad.net/bugs/1830169
Title:
lvm udev rule fails to call systemd-run
Status in Ubuntu on IBM z Systems:
Fix Committed
Status in lvm2 package in Ubuntu:
Fix Released
Status in lvm2 source package in Xenial:
In Progress
Status in lvm2 source package in Bionic:
In Progress
Status in lvm2 source package in Cosmic:
Fix Released
Status in lvm2 source package in Disco:
Fix Released
Status in lvm2 source package in Eoan:
Fix Released
Bug description:
[Impact]
Judging from the rule, this probably means that volumes do not disappear when
the physical volume disappears.
[Test case]
Not available. But since it's just a path fix, it should not be a problem.
[Regression potential]
Removal might now actually work correctly, but it's not entirely clear how
that could cause a regression.
[Other info]
In /lib/udev/rules.d/69-lvm-metad.rules file, it calls /bin/systemd-run
command during removal ---
ACTION!="remove", ENV{LVM_PV_GONE}=="1", RUN+="/bin/systemd-run /sbin/lvm
pvscan --cache $major:$minor", GOTO="lvm_end"
But /bin/systemd-run is not found, in fact systemd-run is in /usr/bin
/systemd-run.
xx:~$ cat /etc/issue
Ubuntu 18.04.2 LTS \n \l
xx:~$ ls /bin/systemd-run
ls: cannot access '/bin/systemd-run': No such file or directory
xx:~$ ls /usr/bin/systemd-run
/usr/bin/systemd-run
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu-z-systems/+bug/1830169/+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 1834795] Re: xubuntu ethernet does not reconnect unless computer restarted, after power off/on modem or manually off/on "enable networking"
Thank you for your bug report, could you add your journalctl -b 0 log after getting the issue? ** Changed in: network-manager (Ubuntu) Importance: Undecided => Low ** Changed in: network-manager (Ubuntu) Status: New => Incomplete -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to network-manager in Ubuntu. https://bugs.launchpad.net/bugs/1834795 Title: xubuntu ethernet does not reconnect unless computer restarted, after power off/on modem or manually off/on "enable networking" Status in network-manager package in Ubuntu: Incomplete Bug description: Xubuntu 19.04, 64bit, encrypted drive, using a desktop computer with ethernet to connect. Connects fine. Use openvpn also (from terminal). When the modem is turned off and on, or when the modem remains on but the ethernet connection is disabled (by unticking) and then ticking again "enable networking" in the applet taskbar, the connection does not re-establish. This is irregardless of the vpn, which even if i turn off, will not affect the lack of reconnection. If i ping bing.com, after trying to reconnect, I get back one response, but no multiple responses. ping bing.com PING bing.com (204.79.197.200) 56(84) bytes of data. This is slightly different to no connection being present, as then I would not even get back a single ping: "ping: bing.com: Temporary failure in name resolution" The only way to get a connection back is by restarting the system. And then it works fine. This is not an issue for ubuntu mate 19.04. The reconnection works fine, with no restart required. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1834795/+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 1830169] Re: lvm udev rule fails to call systemd-run
@hws as the status says on launchpad, both xenial and bionic are "in
progress". Awaiting SRU team reviews to be accepted into -proposed.
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to lvm2 in Ubuntu.
https://bugs.launchpad.net/bugs/1830169
Title:
lvm udev rule fails to call systemd-run
Status in Ubuntu on IBM z Systems:
Fix Committed
Status in lvm2 package in Ubuntu:
Fix Released
Status in lvm2 source package in Xenial:
In Progress
Status in lvm2 source package in Bionic:
In Progress
Status in lvm2 source package in Cosmic:
Fix Released
Status in lvm2 source package in Disco:
Fix Released
Status in lvm2 source package in Eoan:
Fix Released
Bug description:
[Impact]
Judging from the rule, this probably means that volumes do not disappear when
the physical volume disappears.
[Test case]
Not available. But since it's just a path fix, it should not be a problem.
[Regression potential]
Removal might now actually work correctly, but it's not entirely clear how
that could cause a regression.
[Other info]
In /lib/udev/rules.d/69-lvm-metad.rules file, it calls /bin/systemd-run
command during removal ---
ACTION!="remove", ENV{LVM_PV_GONE}=="1", RUN+="/bin/systemd-run /sbin/lvm
pvscan --cache $major:$minor", GOTO="lvm_end"
But /bin/systemd-run is not found, in fact systemd-run is in /usr/bin
/systemd-run.
xx:~$ cat /etc/issue
Ubuntu 18.04.2 LTS \n \l
xx:~$ ls /bin/systemd-run
ls: cannot access '/bin/systemd-run': No such file or directory
xx:~$ ls /usr/bin/systemd-run
/usr/bin/systemd-run
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu-z-systems/+bug/1830169/+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 1834782] Re: ASUS Zenbook UX433FN: sound stops working after a couple of seconds
** Changed in: linux-firmware (Ubuntu) Status: Incomplete => New ** Changed in: linux-hwe (Ubuntu) Status: Incomplete => New ** Changed in: linux-hwe-edge (Ubuntu) Status: Incomplete => New -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to pulseaudio in Ubuntu. https://bugs.launchpad.net/bugs/1834782 Title: ASUS Zenbook UX433FN: sound stops working after a couple of seconds Status in linux-firmware package in Ubuntu: New Status in linux-hwe package in Ubuntu: New Status in linux-hwe-edge package in Ubuntu: New Status in pulseaudio package in Ubuntu: Invalid Bug description: Issue: whichever sound-related action (sound +/- media keys, spotify song, youtube vid in browser,...) I do, the sound works OK for about 2-3 seconds, and then stops and becomes silent. The interesting thing is that when I stop playing the audio (ie close the browser tab with a song), after a while when I try aain the sound works again. Yet still for just the few secs. Environment: up-to-date Ubuntu 18.04, tried -hwe, hwe-edge kernels. This is a regression, the sound used to work OK on this machine, and nothing significant related to sound has changed since. Thank you for looking into this bug! --- ProblemType: Bug ApportVersion: 2.20.9-0ubuntu7.6 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: mmm 28065 F pulseaudio CurrentDesktop: KDE CurrentDmesg: Error: command ['dmesg'] failed with exit code 1: dmesg: read kernel buffer failed: Operation not permitted Dependencies: DistroRelease: KDE neon 18.04 InstallationDate: Installed on 2012-12-23 (2380 days ago) InstallationMedia: Kubuntu 12.10 "Quantal Quetzal" - Release amd64 (20121017.1) Package: pulseaudio PackageArchitecture: all ProcVersionSignature: Ubuntu 4.18.0-25.26~18.04.1-generic 4.18.20 Tags: bionic wayland-session third-party-packages wayland-session Uname: Linux 4.18.0-25-generic x86_64 UnreportableReason: Toto není oficiální KDE balík. Prosíme odstraňte všechny balíky třetích stran a zkuste to znovu. UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm libvirtd lpadmin netdev plugdev sudo video _MarkForUpload: True dmi.bios.date: 04/24/2019 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: UX433FN.306 dmi.board.asset.tag: ATN12345678901234567 dmi.board.name: UX433FN dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: 1.0 dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: ASUSTeK COMPUTER INC. dmi.chassis.version: 1.0 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrUX433FN.306:bd04/24/2019:svnASUSTeKCOMPUTERINC.:pnZenBookUX433FN_UX433FN:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnUX433FN:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0: dmi.product.family: ZenBook dmi.product.name: ZenBook UX433FN_UX433FN dmi.product.version: 1.0 dmi.sys.vendor: ASUSTeK COMPUTER INC. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-firmware/+bug/1834782/+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 1834832] [NEW] printer keeps on printing and it is rubish
Public bug reported: Xerox Phaser-3435 printer starts will not stop and the print job is not showing to close,as well as that it is just spitting out rubbish on the pages,windows may be coming back. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: cups 2.2.7-1ubuntu2.6 ProcVersionSignature: Ubuntu 4.15.0-54.58-generic 4.15.18 Uname: Linux 4.15.0-54-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.6 Architecture: amd64 CupsErrorLog: CurrentDesktop: ubuntu:GNOME Date: Mon Jul 1 17:58:08 2019 InstallationDate: Installed on 2019-01-06 (175 days ago) InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 (20180725) Lpstat: device for Phaser-3435: usb://Xerox/Phaser%203435?serial=RVX451472 Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 004: ID 045e:0084 Microsoft Corp. Basic Optical Mouse Bus 001 Device 003: ID 046d:c52b Logitech, Inc. Unifying Receiver Bus 001 Device 005: ID 0bda:0103 Realtek Semiconductor Corp. USB 2.0 Card Reader Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: Gigabyte Technology Co., Ltd. B250M-HD3 Papersize: a4 PpdFiles: Error: command ['fgrep', '-H', '*NickName', '/etc/cups/ppd/Phaser-3435.ppd'] failed with exit code 2: grep: /etc/cups/ppd/Phaser-3435.ppd: Permission denied ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-54-generic root=UUID=063c3aa1-dc53-4693-882d-d4fe078115f5 ro quiet splash vt.handoff=1 SourcePackage: cups UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 04/10/2018 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: F9 dmi.board.asset.tag: Default string dmi.board.name: B250M-HD3-CF dmi.board.vendor: Gigabyte Technology Co., Ltd. dmi.board.version: x.x dmi.chassis.asset.tag: Default string dmi.chassis.type: 3 dmi.chassis.vendor: Default string dmi.chassis.version: Default string dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrF9:bd04/10/2018:svnGigabyteTechnologyCo.,Ltd.:pnB250M-HD3:pvrDefaultstring:rvnGigabyteTechnologyCo.,Ltd.:rnB250M-HD3-CF:rvrx.x:cvnDefaultstring:ct3:cvrDefaultstring: dmi.product.family: Default string dmi.product.name: B250M-HD3 dmi.product.version: Default string dmi.sys.vendor: Gigabyte Technology Co., Ltd. ** Affects: cups (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug bionic -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to cups in Ubuntu. https://bugs.launchpad.net/bugs/1834832 Title: printer keeps on printing and it is rubish Status in cups package in Ubuntu: New Bug description: Xerox Phaser-3435 printer starts will not stop and the print job is not showing to close,as well as that it is just spitting out rubbish on the pages,windows may be coming back. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: cups 2.2.7-1ubuntu2.6 ProcVersionSignature: Ubuntu 4.15.0-54.58-generic 4.15.18 Uname: Linux 4.15.0-54-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.6 Architecture: amd64 CupsErrorLog: CurrentDesktop: ubuntu:GNOME Date: Mon Jul 1 17:58:08 2019 InstallationDate: Installed on 2019-01-06 (175 days ago) InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 (20180725) Lpstat: device for Phaser-3435: usb://Xerox/Phaser%203435?serial=RVX451472 Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 004: ID 045e:0084 Microsoft Corp. Basic Optical Mouse Bus 001 Device 003: ID 046d:c52b Logitech, Inc. Unifying Receiver Bus 001 Device 005: ID 0bda:0103 Realtek Semiconductor Corp. USB 2.0 Card Reader Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: Gigabyte Technology Co., Ltd. B250M-HD3 Papersize: a4 PpdFiles: Error: command ['fgrep', '-H', '*NickName', '/etc/cups/ppd/Phaser-3435.ppd'] failed with exit code 2: grep: /etc/cups/ppd/Phaser-3435.ppd: Permission denied ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-54-generic root=UUID=063c3aa1-dc53-4693-882d-d4fe078115f5 ro quiet splash vt.handoff=1 SourcePackage: cups UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 04/10/2018 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: F9 dmi.board.asset.tag: Default string dmi.board.name: B250M-HD3-CF dmi.board.vendor: Gigabyte Technology Co., Ltd. dmi.board.version: x.x dmi.chassis.asset.tag: Default string dmi.chassis.type: 3 dmi.chassis.vendor: Default string dmi.chassis.version: Default string dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrF9:bd04/10/2018:svnGigabyteTechnologyCo.,Ltd.:pnB250M-HD3:pvrDefaultstring:rvnGigabyteTechnologyCo.,Ltd.:rnB250M-HD3-CF:rvrx.x:cvnDefaultstring:ct3:cvrDefaultstring: dmi.product.family: Default string dmi.product.name: B250M-HD3 dmi.product.version: Default string dmi.sys.vendor: Gigabyte Technology Co., Ltd. To manage notifications about this bug go to:
[Touch-packages] [Bug 1830169] Re: lvm udev rule fails to call systemd-run
Turns out xenial binaries were not affected at all because they were
built with --disable-udev-systemd-background-jobs
** No longer affects: lvm2 (Ubuntu Xenial)
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to lvm2 in Ubuntu.
https://bugs.launchpad.net/bugs/1830169
Title:
lvm udev rule fails to call systemd-run
Status in Ubuntu on IBM z Systems:
Fix Committed
Status in lvm2 package in Ubuntu:
Fix Released
Status in lvm2 source package in Bionic:
Fix Committed
Status in lvm2 source package in Cosmic:
Fix Released
Status in lvm2 source package in Disco:
Fix Released
Status in lvm2 source package in Eoan:
Fix Released
Bug description:
[Impact]
Judging from the rule, this probably means that volumes do not disappear when
the physical volume disappears.
[Test case]
Not available. But since it's just a path fix, it should not be a problem.
[Regression potential]
Removal might now actually work correctly, but it's not entirely clear how
that could cause a regression.
[Other info]
In /lib/udev/rules.d/69-lvm-metad.rules file, it calls /bin/systemd-run
command during removal ---
ACTION!="remove", ENV{LVM_PV_GONE}=="1", RUN+="/bin/systemd-run /sbin/lvm
pvscan --cache $major:$minor", GOTO="lvm_end"
But /bin/systemd-run is not found, in fact systemd-run is in /usr/bin
/systemd-run.
xx:~$ cat /etc/issue
Ubuntu 18.04.2 LTS \n \l
xx:~$ ls /bin/systemd-run
ls: cannot access '/bin/systemd-run': No such file or directory
xx:~$ ls /usr/bin/systemd-run
/usr/bin/systemd-run
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu-z-systems/+bug/1830169/+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 1833039] Re: 18.04/Apache2: rejecting client initiated renegotiation due to openssl 1.1.1
** Description changed: + [Impact] + + * An explanation of the effects of the bug on users and + + * justification for backporting the fix to the stable release. + + * In addition, it is helpful, but not required, to include an +explanation of how the upload fixes this bug. + + [Test Case] + + * detailed instructions how to reproduce the bug + + * these should allow someone who is not familiar with the affected +package to reproduce the bug and verify that the updated package fixes +the problem. + + [Regression Potential] + + * discussion of how regressions are most likely to manifest as a result + of this change. + + * It is assumed that any SRU candidate patch is well-tested before +upload and has a low overall risk of regression, but it's important +to make the effort to think about what ''could'' happen in the +event of a regression. + + * This both shows the SRU team that the risks have been considered, +and provides guidance to testers in regression-testing the SRU. + + [Other Info] + + * Anything else you think is useful to include + * Anticipate questions from users, SRU, +1 maintenance, security teams and the Technical Board + * and address these questions in advance + + + [Original Description] I am using Apache2 with client certificate authentication. Since recently (last week) and without any configuration changes, the following errors occur frequently: AH02042: rejecting client initiated renegotiation Client connections are very slow and sometimes it takes more than a minute until a weg page can be opened in the browser. Before installation of the latest security fixes last week, this error did not occur. Could it be related to https://bugs.launchpad.net/ubuntu/+source/apache2/+bug/1803689? - System information: Description:Ubuntu 18.04.2 LTS Release:18.04 apache2: - Installiert: 2.4.29-1ubuntu4.6 - Installationskandidat: 2.4.29-1ubuntu4.6 - Versionstabelle: - *** 2.4.29-1ubuntu4.6 500 - 500 http://de.archive.ubuntu.com/ubuntu bionic-updates/main amd64 Packages - 500 http://security.ubuntu.com/ubuntu bionic-security/main amd64 Packages - 100 /var/lib/dpkg/status - 2.4.29-1ubuntu4 500 - 500 http://de.archive.ubuntu.com/ubuntu bionic/main amd64 Packages + Installiert: 2.4.29-1ubuntu4.6 + Installationskandidat: 2.4.29-1ubuntu4.6 + Versionstabelle: + *** 2.4.29-1ubuntu4.6 500 + 500 http://de.archive.ubuntu.com/ubuntu bionic-updates/main amd64 Packages + 500 http://security.ubuntu.com/ubuntu bionic-security/main amd64 Packages + 100 /var/lib/dpkg/status + 2.4.29-1ubuntu4 500 + 500 http://de.archive.ubuntu.com/ubuntu bionic/main amd64 Packages openssl: - Installiert: 1.1.1-1ubuntu2.1~18.04.2 - Installationskandidat: 1.1.1-1ubuntu2.1~18.04.2 - Versionstabelle: - *** 1.1.1-1ubuntu2.1~18.04.2 500 - 500 http://de.archive.ubuntu.com/ubuntu bionic-updates/main amd64 Packages - 100 /var/lib/dpkg/status - 1.1.0g-2ubuntu4.3 500 - 500 http://security.ubuntu.com/ubuntu bionic-security/main amd64 Packages - 1.1.0g-2ubuntu4 500 - 500 http://de.archive.ubuntu.com/ubuntu bionic/main amd64 Packages + Installiert: 1.1.1-1ubuntu2.1~18.04.2 + Installationskandidat: 1.1.1-1ubuntu2.1~18.04.2 + Versionstabelle: + *** 1.1.1-1ubuntu2.1~18.04.2 500 + 500 http://de.archive.ubuntu.com/ubuntu bionic-updates/main amd64 Packages + 100 /var/lib/dpkg/status + 1.1.0g-2ubuntu4.3 500 + 500 http://security.ubuntu.com/ubuntu bionic-security/main amd64 Packages + 1.1.0g-2ubuntu4 500 + 500 http://de.archive.ubuntu.com/ubuntu bionic/main amd64 Packages ** Description changed: [Impact] - * An explanation of the effects of the bug on users and + * An explanation of the effects of the bug on users and - * justification for backporting the fix to the stable release. + * justification for backporting the fix to the stable release. - * In addition, it is helpful, but not required, to include an -explanation of how the upload fixes this bug. + * In addition, it is helpful, but not required, to include an + explanation of how the upload fixes this bug. [Test Case] - * detailed instructions how to reproduce the bug + It helps if you have lxd up and running. Otherwise, a VM or even bare + metal host also works, as long as you stick to the "ubuntu" hostname. - * these should allow someone who is not familiar with the affected -package to reproduce the bug and verify that the updated package fixes -the problem. + Launch a container for the release you are testing. The command below is for bionic: + $ lxc launch ubuntu-daily:bionic ubuntu + + Enter the container as root: + $ lxc exec ubuntu bash + + Verify hostname is "ubuntu": + # hostname + ubuntu + +
[Touch-packages] [Bug 1833039] Re: 18.04/Apache2: rejecting client initiated renegotiation due to openssl 1.1.1
fake CA
** Description changed:
[Impact]
+ Under the following conditions, https connections using client cert
authentication will suffer a long delay (15s or more if modreqtimeout is
disabled):
+ * TLSv1.2
+ * client certificate authentication in use
+ * a Location, Directory, or other such block defining the client certificate
authentication for that block only, differing from the SSL vhost as a whole
- * An explanation of the effects of the bug on users and
+ This was triggered by the OpenSSL 1.1.1 SRU and was caused by this
+ openssl change in SSL_MODE_AUTO_RETRY from disabled to enabled by
+ default:
+
https://github.com/openssl/openssl/blob/a4a90a8a3bdcb9336b5c9c15da419e99a87bc6ed/CHANGES#L121-L130
- * justification for backporting the fix to the stable release.
-
- * In addition, it is helpful, but not required, to include an
- explanation of how the upload fixes this bug.
[Test Case]
It helps if you have lxd up and running. Otherwise, a VM or even bare
metal host also works, as long as you stick to the "ubuntu" hostname.
Launch a container for the release you are testing. The command below is for
bionic:
$ lxc launch ubuntu-daily:bionic ubuntu
Enter the container as root:
$ lxc exec ubuntu bash
Verify hostname is "ubuntu":
# hostname
ubuntu
Install apache2:
apt update && apt install apache2
Download the following files from this bug report and place them in
/etc/apache2:
ubuntu.pem
ubuntu.key
cacert.pem
Download the client certificate and key files and place them in /root:
client-auth.key
client-auth.pem
Adjust permissions of the key file:
chmod 0640 /etc/apache2/ubuntu.key
chgrp www-data /etc/apache2/ubuntu.key
Create this vhost file (caution, lines may wrap, in particular LogFormat: it
should be one long line):
cat > /etc/apache2/sites-available/cert-auth-test.conf <
-
- LogLevel info ssl:warn
- ServerAdmin webmaster@localhost
- DocumentRoot /var/www/html
- LogFormat "%h %l %u %t \"%r\" %>s %O \"%{Referer}i\"
\"%{User-Agent}i\" protocol=%{SSL_PROTOCOL}x commonName=%{SSL_CLIENT_S_DN_CN}x"
combined-ssl
- ErrorLog \${APACHE_LOG_DIR}/error.log
- CustomLog \${APACHE_LOG_DIR}/access.log combined-ssl
- SSLEngine on
- SSLCertificateFile /etc/apache2/ubuntu.pem
- SSLCertificateKeyFile /etc/apache2/ubuntu.key
- SSLCACertificateFile /etc/apache2/cacert.pem
-
- SSLOptions +StdEnvVars
-
-
- SSLOptions +StdEnvVars
-
-
- SSLVerifyClient require
- Require ssl-verify-client
-
-
+
+ LogLevel info ssl:warn
+ ServerAdmin webmaster@localhost
+ DocumentRoot /var/www/html
+ LogFormat "%h %l %u %t \"%r\" %>s %O \"%{Referer}i\"
\"%{User-Agent}i\" protocol=%{SSL_PROTOCOL}x commonName=%{SSL_CLIENT_S_DN_CN}x"
combined-ssl
+ ErrorLog \${APACHE_LOG_DIR}/error.log
+ CustomLog \${APACHE_LOG_DIR}/access.log combined-ssl
+ SSLEngine on
+ SSLCertificateFile /etc/apache2/ubuntu.pem
+ SSLCertificateKeyFile /etc/apache2/ubuntu.key
+ SSLCACertificateFile /etc/apache2/cacert.pem
+
+ SSLOptions +StdEnvVars
+
+
+ SSLOptions +StdEnvVars
+
+
+ SSLVerifyClient require
+ Require ssl-verify-client
+
+
EOF
Enable the ssl module and this new vhost we just created:
a2enmod ssl && a2ensite cert-auth-test.conf
Restart apache2:
systemctl restart apache2
If at this stage you try the following command, it will fail like this
because no client certificate was provided:
# curl --output /dev/null https://ubuntu/ --cacert /etc/apache2/cacert.pem
- % Total% Received % Xferd Average Speed TimeTime Time
Current
- Dload Upload Total SpentLeft Speed
- 0 00 00 0 0 0 --:--:-- --:--:-- --:--:-- 0
+ % Total% Received % Xferd Average Speed TimeTime Time
Current
+ Dload Upload Total SpentLeft Speed
+ 0 00 00 0 0 0 --:--:-- --:--:-- --:--:-- 0
curl: (56) OpenSSL SSL_read: error:14094410:SSL
routines:ssl3_read_bytes:sslv3 alert handshake failure, errno 0
And the apache error log will confirm the reason:
[Mon Jul 01 14:10:23.312645 2019] [ssl:error] [pid 1685:tid 140326396421888]
SSL Library Error: error:1417C0C7:SSL
routines:tls_process_client_certificate:peer did not return a certificate -- No
CAs known to server for verification?
-
Now retry, but providing the client certificate and key files, and forcing
TLSv1.2 just to be sure. Due to the bug, the command will stall for about 15
seconds, but the index.html
[Touch-packages] [Bug 1833039] Re: 18.04/Apache2: rejecting client initiated renegotiation due to openssl 1.1.1
server key
** Attachment added: "ubuntu.key"
https://bugs.launchpad.net/ubuntu/+source/apache2/+bug/1833039/+attachment/5274494/+files/ubuntu.key
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to openssl in Ubuntu.
https://bugs.launchpad.net/bugs/1833039
Title:
18.04/Apache2: rejecting client initiated renegotiation due to openssl
1.1.1
Status in apache2 package in Ubuntu:
Confirmed
Status in openssl package in Ubuntu:
Incomplete
Status in apache2 source package in Bionic:
Confirmed
Status in apache2 source package in Cosmic:
Confirmed
Bug description:
[Impact]
Under the following conditions, https connections using client cert
authentication will suffer a long delay (15s or more if modreqtimeout is
disabled):
* TLSv1.2
* client certificate authentication in use
* a Location, Directory, or other such block defining the client certificate
authentication for that block only, differing from the SSL vhost as a whole
This was triggered by the OpenSSL 1.1.1 SRU and was caused by this
openssl change in SSL_MODE_AUTO_RETRY from disabled to enabled by
default:
https://github.com/openssl/openssl/blob/a4a90a8a3bdcb9336b5c9c15da419e99a87bc6ed/CHANGES#L121-L130
[Test Case]
It helps if you have lxd up and running. Otherwise, a VM or even bare
metal host also works, as long as you stick to the "ubuntu" hostname.
Launch a container for the release you are testing. The command below is for
bionic:
$ lxc launch ubuntu-daily:bionic ubuntu
Enter the container as root:
$ lxc exec ubuntu bash
Verify hostname is "ubuntu":
# hostname
ubuntu
Install apache2:
apt update && apt install apache2
Download the following files from this bug report and place them in
/etc/apache2:
cd /etc/apache2
wget
https://bugs.launchpad.net/ubuntu/+source/apache2/+bug/1833039/+attachment/5274492/+files/cacert.pem
https://bugs.launchpad.net/ubuntu/+source/apache2/+bug/1833039/+attachment/5274493/+files/ubuntu.pem
https://bugs.launchpad.net/ubuntu/+source/apache2/+bug/1833039/+attachment/5274494/+files/ubuntu.key
Adjust permissions of the key file:
chmod 0640 /etc/apache2/ubuntu.key
chgrp www-data /etc/apache2/ubuntu.key
Download the client certificate and key files and place them in /root:
client-auth.key
client-auth.pem
Create this vhost file (caution, lines may wrap, in particular LogFormat: it
should be one long line):
cat > /etc/apache2/sites-available/cert-auth-test.conf <
LogLevel info ssl:warn
ServerAdmin webmaster@localhost
DocumentRoot /var/www/html
LogFormat "%h %l %u %t \"%r\" %>s %O \"%{Referer}i\"
\"%{User-Agent}i\" protocol=%{SSL_PROTOCOL}x commonName=%{SSL_CLIENT_S_DN_CN}x"
combined-ssl
ErrorLog \${APACHE_LOG_DIR}/error.log
CustomLog \${APACHE_LOG_DIR}/access.log combined-ssl
SSLEngine on
SSLCertificateFile /etc/apache2/ubuntu.pem
SSLCertificateKeyFile /etc/apache2/ubuntu.key
SSLCACertificateFile /etc/apache2/cacert.pem
SSLOptions +StdEnvVars
SSLOptions +StdEnvVars
SSLVerifyClient require
Require ssl-verify-client
EOF
Enable the ssl module and this new vhost we just created:
a2enmod ssl && a2ensite cert-auth-test.conf
Restart apache2:
systemctl restart apache2
If at this stage you try the following command, it will fail like this
because no client certificate was provided:
# curl --output /dev/null https://ubuntu/ --cacert /etc/apache2/cacert.pem
% Total% Received % Xferd Average Speed TimeTime Time
Current
Dload Upload Total SpentLeft Speed
0 00 00 0 0 0 --:--:-- --:--:-- --:--:-- 0
curl: (56) OpenSSL SSL_read: error:14094410:SSL
routines:ssl3_read_bytes:sslv3 alert handshake failure, errno 0
And the apache error log will confirm the reason:
[Mon Jul 01 14:10:23.312645 2019] [ssl:error] [pid 1685:tid 140326396421888]
SSL Library Error: error:1417C0C7:SSL
routines:tls_process_client_certificate:peer did not return a certificate -- No
CAs known to server for verification?
Now retry, but providing the client certificate and key files, and forcing
TLSv1.2 just to be sure. Due to the bug, the command will stall for about 15
seconds, but the index.html file will be downloaded:
# rm -f index.html
# curl --output index.html https://ubuntu/ --cacert /etc/apache2/cacert.pem
--cert client-auth.pem --key client-auth.key --tlsv1.2
% Total% Received % Xferd Average Speed TimeTime Time
Current
Dload Upload Total SpentLeft Speed
100 10918 100 109180 0706 0 0:00:15 0:00:15 --:--:-- 2579
# ll
[Touch-packages] [Bug 1833039] Re: 18.04/Apache2: rejecting client initiated renegotiation due to openssl 1.1.1
server certificate
** Attachment added: "ubuntu.pem"
https://bugs.launchpad.net/ubuntu/+source/apache2/+bug/1833039/+attachment/5274493/+files/ubuntu.pem
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to openssl in Ubuntu.
https://bugs.launchpad.net/bugs/1833039
Title:
18.04/Apache2: rejecting client initiated renegotiation due to openssl
1.1.1
Status in apache2 package in Ubuntu:
Confirmed
Status in openssl package in Ubuntu:
Incomplete
Status in apache2 source package in Bionic:
Confirmed
Status in apache2 source package in Cosmic:
Confirmed
Bug description:
[Impact]
Under the following conditions, https connections using client cert
authentication will suffer a long delay (15s or more if modreqtimeout is
disabled):
* TLSv1.2
* client certificate authentication in use
* a Location, Directory, or other such block defining the client certificate
authentication for that block only, differing from the SSL vhost as a whole
This was triggered by the OpenSSL 1.1.1 SRU and was caused by this
openssl change in SSL_MODE_AUTO_RETRY from disabled to enabled by
default:
https://github.com/openssl/openssl/blob/a4a90a8a3bdcb9336b5c9c15da419e99a87bc6ed/CHANGES#L121-L130
[Test Case]
It helps if you have lxd up and running. Otherwise, a VM or even bare
metal host also works, as long as you stick to the "ubuntu" hostname.
Launch a container for the release you are testing. The command below is for
bionic:
$ lxc launch ubuntu-daily:bionic ubuntu
Enter the container as root:
$ lxc exec ubuntu bash
Verify hostname is "ubuntu":
# hostname
ubuntu
Install apache2:
apt update && apt install apache2
Download the following files from this bug report and place them in
/etc/apache2:
cd /etc/apache2
wget
https://bugs.launchpad.net/ubuntu/+source/apache2/+bug/1833039/+attachment/5274492/+files/cacert.pem
https://bugs.launchpad.net/ubuntu/+source/apache2/+bug/1833039/+attachment/5274493/+files/ubuntu.pem
https://bugs.launchpad.net/ubuntu/+source/apache2/+bug/1833039/+attachment/5274494/+files/ubuntu.key
Adjust permissions of the key file:
chmod 0640 /etc/apache2/ubuntu.key
chgrp www-data /etc/apache2/ubuntu.key
Download the client certificate and key files and place them in /root:
client-auth.key
client-auth.pem
Create this vhost file (caution, lines may wrap, in particular LogFormat: it
should be one long line):
cat > /etc/apache2/sites-available/cert-auth-test.conf <
LogLevel info ssl:warn
ServerAdmin webmaster@localhost
DocumentRoot /var/www/html
LogFormat "%h %l %u %t \"%r\" %>s %O \"%{Referer}i\"
\"%{User-Agent}i\" protocol=%{SSL_PROTOCOL}x commonName=%{SSL_CLIENT_S_DN_CN}x"
combined-ssl
ErrorLog \${APACHE_LOG_DIR}/error.log
CustomLog \${APACHE_LOG_DIR}/access.log combined-ssl
SSLEngine on
SSLCertificateFile /etc/apache2/ubuntu.pem
SSLCertificateKeyFile /etc/apache2/ubuntu.key
SSLCACertificateFile /etc/apache2/cacert.pem
SSLOptions +StdEnvVars
SSLOptions +StdEnvVars
SSLVerifyClient require
Require ssl-verify-client
EOF
Enable the ssl module and this new vhost we just created:
a2enmod ssl && a2ensite cert-auth-test.conf
Restart apache2:
systemctl restart apache2
If at this stage you try the following command, it will fail like this
because no client certificate was provided:
# curl --output /dev/null https://ubuntu/ --cacert /etc/apache2/cacert.pem
% Total% Received % Xferd Average Speed TimeTime Time
Current
Dload Upload Total SpentLeft Speed
0 00 00 0 0 0 --:--:-- --:--:-- --:--:-- 0
curl: (56) OpenSSL SSL_read: error:14094410:SSL
routines:ssl3_read_bytes:sslv3 alert handshake failure, errno 0
And the apache error log will confirm the reason:
[Mon Jul 01 14:10:23.312645 2019] [ssl:error] [pid 1685:tid 140326396421888]
SSL Library Error: error:1417C0C7:SSL
routines:tls_process_client_certificate:peer did not return a certificate -- No
CAs known to server for verification?
Now retry, but providing the client certificate and key files, and forcing
TLSv1.2 just to be sure. Due to the bug, the command will stall for about 15
seconds, but the index.html file will be downloaded:
# rm -f index.html
# curl --output index.html https://ubuntu/ --cacert /etc/apache2/cacert.pem
--cert client-auth.pem --key client-auth.key --tlsv1.2
% Total% Received % Xferd Average Speed TimeTime Time
Current
Dload Upload Total SpentLeft Speed
100 10918 100 109180 0706 0 0:00:15 0:00:15 --:--:-- 2579
[Touch-packages] [Bug 1833039] Re: 18.04/Apache2: rejecting client initiated renegotiation due to openssl 1.1.1
client key
** Attachment added: "client-auth.key"
https://bugs.launchpad.net/ubuntu/+source/apache2/+bug/1833039/+attachment/5274496/+files/client-auth.key
** Description changed:
[Impact]
Under the following conditions, https connections using client cert
authentication will suffer a long delay (15s or more if modreqtimeout is
disabled):
* TLSv1.2
* client certificate authentication in use
* a Location, Directory, or other such block defining the client certificate
authentication for that block only, differing from the SSL vhost as a whole
This was triggered by the OpenSSL 1.1.1 SRU and was caused by this
openssl change in SSL_MODE_AUTO_RETRY from disabled to enabled by
default:
https://github.com/openssl/openssl/blob/a4a90a8a3bdcb9336b5c9c15da419e99a87bc6ed/CHANGES#L121-L130
-
[Test Case]
It helps if you have lxd up and running. Otherwise, a VM or even bare
metal host also works, as long as you stick to the "ubuntu" hostname.
Launch a container for the release you are testing. The command below is for
bionic:
$ lxc launch ubuntu-daily:bionic ubuntu
Enter the container as root:
$ lxc exec ubuntu bash
Verify hostname is "ubuntu":
# hostname
ubuntu
Install apache2:
apt update && apt install apache2
Download the following files from this bug report and place them in
/etc/apache2:
- ubuntu.pem
- ubuntu.key
- cacert.pem
+ cd /etc/apache2
+ wget
https://bugs.launchpad.net/ubuntu/+source/apache2/+bug/1833039/+attachment/5274492/+files/cacert.pem
https://bugs.launchpad.net/ubuntu/+source/apache2/+bug/1833039/+attachment/5274493/+files/ubuntu.pem
https://bugs.launchpad.net/ubuntu/+source/apache2/+bug/1833039/+attachment/5274494/+files/ubuntu.key
+
+ Adjust permissions of the key file:
+ chmod 0640 /etc/apache2/ubuntu.key
+ chgrp www-data /etc/apache2/ubuntu.key
Download the client certificate and key files and place them in /root:
client-auth.key
client-auth.pem
- Adjust permissions of the key file:
- chmod 0640 /etc/apache2/ubuntu.key
- chgrp www-data /etc/apache2/ubuntu.key
Create this vhost file (caution, lines may wrap, in particular LogFormat: it
should be one long line):
cat > /etc/apache2/sites-available/cert-auth-test.conf <
LogLevel info ssl:warn
ServerAdmin webmaster@localhost
DocumentRoot /var/www/html
LogFormat "%h %l %u %t \"%r\" %>s %O \"%{Referer}i\"
\"%{User-Agent}i\" protocol=%{SSL_PROTOCOL}x commonName=%{SSL_CLIENT_S_DN_CN}x"
combined-ssl
ErrorLog \${APACHE_LOG_DIR}/error.log
CustomLog \${APACHE_LOG_DIR}/access.log combined-ssl
SSLEngine on
SSLCertificateFile /etc/apache2/ubuntu.pem
SSLCertificateKeyFile /etc/apache2/ubuntu.key
SSLCACertificateFile /etc/apache2/cacert.pem
SSLOptions +StdEnvVars
SSLOptions +StdEnvVars
SSLVerifyClient require
Require ssl-verify-client
EOF
Enable the ssl module and this new vhost we just created:
a2enmod ssl && a2ensite cert-auth-test.conf
Restart apache2:
systemctl restart apache2
If at this stage you try the following command, it will fail like this
because no client certificate was provided:
# curl --output /dev/null https://ubuntu/ --cacert /etc/apache2/cacert.pem
% Total% Received % Xferd Average Speed TimeTime Time
Current
Dload Upload Total SpentLeft Speed
0 00 00 0 0 0 --:--:-- --:--:-- --:--:-- 0
curl: (56) OpenSSL SSL_read: error:14094410:SSL
routines:ssl3_read_bytes:sslv3 alert handshake failure, errno 0
And the apache error log will confirm the reason:
[Mon Jul 01 14:10:23.312645 2019] [ssl:error] [pid 1685:tid 140326396421888]
SSL Library Error: error:1417C0C7:SSL
routines:tls_process_client_certificate:peer did not return a certificate -- No
CAs known to server for verification?
Now retry, but providing the client certificate and key files, and forcing
TLSv1.2 just to be sure. Due to the bug, the command will stall for about 15
seconds, but the index.html file will be downloaded:
# rm -f index.html
# curl --output index.html https://ubuntu/ --cacert /etc/apache2/cacert.pem
--cert client-auth.pem --key client-auth.key --tlsv1.2
% Total% Received % Xferd Average Speed TimeTime Time
Current
Dload Upload Total SpentLeft Speed
100 10918 100 109180 0706 0 0:00:15 0:00:15 --:--:-- 2579
# ll index.html
-rw-r--r-- 1 root root 10918 Jul 1 14:15 index.html
Apache will log this in the error.log file:
[Mon Jul 01 14:15:38.014784 2019] [reqtimeout:info] [pid 1685:tid
140326278772480] [client 10.0.100.215:35108] AH01382: Request body read timeout
That
[Touch-packages] [Bug 1833039] Re: 18.04/Apache2: rejecting client initiated renegotiation due to openssl 1.1.1
client certificate
** Attachment added: "client-auth.pem"
https://bugs.launchpad.net/ubuntu/+source/apache2/+bug/1833039/+attachment/5274495/+files/client-auth.pem
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to openssl in Ubuntu.
https://bugs.launchpad.net/bugs/1833039
Title:
18.04/Apache2: rejecting client initiated renegotiation due to openssl
1.1.1
Status in apache2 package in Ubuntu:
Confirmed
Status in openssl package in Ubuntu:
Incomplete
Status in apache2 source package in Bionic:
Confirmed
Status in apache2 source package in Cosmic:
Confirmed
Bug description:
[Impact]
Under the following conditions, https connections using client cert
authentication will suffer a long delay (15s or more if modreqtimeout is
disabled):
* TLSv1.2
* client certificate authentication in use
* a Location, Directory, or other such block defining the client certificate
authentication for that block only, differing from the SSL vhost as a whole
This was triggered by the OpenSSL 1.1.1 SRU and was caused by this
openssl change in SSL_MODE_AUTO_RETRY from disabled to enabled by
default:
https://github.com/openssl/openssl/blob/a4a90a8a3bdcb9336b5c9c15da419e99a87bc6ed/CHANGES#L121-L130
[Test Case]
It helps if you have lxd up and running. Otherwise, a VM or even bare
metal host also works, as long as you stick to the "ubuntu" hostname.
Launch a container for the release you are testing. The command below is for
bionic:
$ lxc launch ubuntu-daily:bionic ubuntu
Enter the container as root:
$ lxc exec ubuntu bash
Verify hostname is "ubuntu":
# hostname
ubuntu
Install apache2:
apt update && apt install apache2
Download the following files from this bug report and place them in
/etc/apache2:
cd /etc/apache2
wget
https://bugs.launchpad.net/ubuntu/+source/apache2/+bug/1833039/+attachment/5274492/+files/cacert.pem
https://bugs.launchpad.net/ubuntu/+source/apache2/+bug/1833039/+attachment/5274493/+files/ubuntu.pem
https://bugs.launchpad.net/ubuntu/+source/apache2/+bug/1833039/+attachment/5274494/+files/ubuntu.key
Adjust permissions of the key file:
chmod 0640 /etc/apache2/ubuntu.key
chgrp www-data /etc/apache2/ubuntu.key
Download the client certificate and key files and place them in /root:
client-auth.key
client-auth.pem
Create this vhost file (caution, lines may wrap, in particular LogFormat: it
should be one long line):
cat > /etc/apache2/sites-available/cert-auth-test.conf <
LogLevel info ssl:warn
ServerAdmin webmaster@localhost
DocumentRoot /var/www/html
LogFormat "%h %l %u %t \"%r\" %>s %O \"%{Referer}i\"
\"%{User-Agent}i\" protocol=%{SSL_PROTOCOL}x commonName=%{SSL_CLIENT_S_DN_CN}x"
combined-ssl
ErrorLog \${APACHE_LOG_DIR}/error.log
CustomLog \${APACHE_LOG_DIR}/access.log combined-ssl
SSLEngine on
SSLCertificateFile /etc/apache2/ubuntu.pem
SSLCertificateKeyFile /etc/apache2/ubuntu.key
SSLCACertificateFile /etc/apache2/cacert.pem
SSLOptions +StdEnvVars
SSLOptions +StdEnvVars
SSLVerifyClient require
Require ssl-verify-client
EOF
Enable the ssl module and this new vhost we just created:
a2enmod ssl && a2ensite cert-auth-test.conf
Restart apache2:
systemctl restart apache2
If at this stage you try the following command, it will fail like this
because no client certificate was provided:
# curl --output /dev/null https://ubuntu/ --cacert /etc/apache2/cacert.pem
% Total% Received % Xferd Average Speed TimeTime Time
Current
Dload Upload Total SpentLeft Speed
0 00 00 0 0 0 --:--:-- --:--:-- --:--:-- 0
curl: (56) OpenSSL SSL_read: error:14094410:SSL
routines:ssl3_read_bytes:sslv3 alert handshake failure, errno 0
And the apache error log will confirm the reason:
[Mon Jul 01 14:10:23.312645 2019] [ssl:error] [pid 1685:tid 140326396421888]
SSL Library Error: error:1417C0C7:SSL
routines:tls_process_client_certificate:peer did not return a certificate -- No
CAs known to server for verification?
Now retry, but providing the client certificate and key files, and forcing
TLSv1.2 just to be sure. Due to the bug, the command will stall for about 15
seconds, but the index.html file will be downloaded:
# rm -f index.html
# curl --output index.html https://ubuntu/ --cacert /etc/apache2/cacert.pem
--cert client-auth.pem --key client-auth.key --tlsv1.2
% Total% Received % Xferd Average Speed TimeTime Time
Current
Dload Upload Total SpentLeft Speed
100 10918 100 109180 0706 0 0:00:15 0:00:15
[Touch-packages] [Bug 1831775] Re: ss seems broken when using multiple filters in the same cmdline
Marking cosmic as won't fix due to its EOL. Only thing here is SRU to Disco. This will become important whenever CTDB merge happens and SRU is done on bug: https://bugs.launchpad.net/ubuntu/+source/samba/+bug/722201 ** Changed in: iproute2 (Ubuntu Cosmic) Status: In Progress => Won't Fix -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to iproute2 in Ubuntu. https://bugs.launchpad.net/bugs/1831775 Title: ss seems broken when using multiple filters in the same cmdline Status in iproute2 package in Ubuntu: Fix Released Status in iproute2 source package in Cosmic: Won't Fix Status in iproute2 source package in Disco: In Progress Status in iproute2 source package in Eoan: Fix Released Bug description: [Impact] * ss won't be able to run commands with single filters inside parentheses, like: "( sport == :X )", for example. * A workaround is to remove "( )" from single filters, since it looks the issue does not affect 2 filters being put together in the same parentheses, like: " ( X and Y ) and Y " instead of ( X and Y ) and ( Y )". * CTDB is unable to use ss filter to obtain nodes public IP addresses in order to fail over services (LP: #722201). [Test Case] * Having an Ubuntu Cosmic, Disco or Eoan, try to execute the following command: $ ss -tn state established "( src [172.16.17.2] || src [172.16.17.3] )" "( sport == :2049 )" Independent of the IPs or ports being used. Copying and pasting the command should be enough for you to know if you are affected. Bad Result: ss: bison bellows (while parsing filter): "syntax error!" Sorry. Usage: ss [ OPTIONS ] ss [ OPTIONS ] [ FILTER ] -h, --help this message ... Expected Result: Recv-QSend-Q Local Address:Port Peer Address:Port ... * test case was discovered during CTDB scripts execution [Regression Potential] * biggest risk would be to affect ss interpreter (worst case scenario). * the proposed patch is based in upstream fix and was tested against the same issue reported as the reproducer (above) and some other generic ss commands. * any problem here is unlikely to change iproute2 most important command interpreter, "ip", since the patch is applied against ss code. [Other Info] ORIGINAL DESCRIPTION: Investigating an issue for CTDB (LP: #722201), after suggesting a fix on ss syntax to CTDB upstream project, we discovered that "ss" seems to be broken in Ubuntu since Ubuntu Cosmic: # Debian Sid inaddy@workstation:~$ ss -tn state established "( src [172.16.17.2] || src [172.16.17.3] )" "( sport == :2049 )" Recv-QSend-Q Local Address:Port Peer Address:Port # Ubuntu Ubuntu 16.04 LTS (Xenial Xerus) (c)inaddy@xenial:~$ ss -tn state established "( src [172.16.17.2] || src [172.16.17.3] )" "( sport == :2049 )" Recv-Q Send-QLocal Address:Port Peer Address:Port # Ubuntu 18.04 LTS (Bionic Beaver) (c)inaddy@bionic:~$ ss -tn state established "( src [172.16.17.2] || src [172.16.17.3] )" "( sport == :2049 )" Recv-Q Send-Q Local Address:Port Peer Address:Port # Ubuntu 18.10 (Cosmic Cuttlefish) (c)inaddy@cosmic:~$ ss -tn state established "( src [172.16.17.2] || src [172.16.17.3] )" "( sport == :2049 )" ss: bison bellows (while parsing filter): "syntax error!" Sorry. Usage: ss [ OPTIONS ] ss [ OPTIONS ] [ FILTER ] -h, --help this message # Ubuntu 19.04 (Disco Dingo) (c)inaddy@disco:~$ ss -tn state established "( src [172.16.17.2] || src [172.16.17.3] )" "( sport == :2049 )" ss: bison bellows (while parsing filter): "syntax error!" Sorry. Usage: ss [ OPTIONS ] ss [ OPTIONS ] [ FILTER ] # Ubuntu 19.10 (Eoan Ermine) (c)inaddy@eoan:~$ ss -tn state established "( src [172.16.17.2] || src [172.16.17.3] )" "( sport == :2049 )" ss: bison bellows (while parsing filter): "syntax error!" Sorry. Usage: ss [ OPTIONS ] ss [ OPTIONS ] [ FILTER ] I have generated a pkg using upstream iproute2 source code and it does not suffer the issue. I have generated a package using Ubuntu cosmic source package, without debian/patches/*, and verified the issue still persists (not being introduced by any of our packages, and being present if vanilla upstream version used in Cosmic). To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/iproute2/+bug/1831775/+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 1833039] Re: 18.04/Apache2: rejecting client initiated renegotiation due to openssl 1.1.1
** Description changed:
[Impact]
- Under the following conditions, https connections using client cert
authentication will suffer a long delay (15s or more if modreqtimeout is
disabled):
+ Under the following conditions, https connections using client cert
authentication will suffer a long delay (about 15s if modreqtimeout is enabled,
more if it is disabled):
* TLSv1.2
* client certificate authentication in use
* a Location, Directory, or other such block defining the client certificate
authentication for that block only, differing from the SSL vhost as a whole
This was triggered by the OpenSSL 1.1.1 SRU and was caused by this
openssl change in SSL_MODE_AUTO_RETRY from disabled to enabled by
default:
https://github.com/openssl/openssl/blob/a4a90a8a3bdcb9336b5c9c15da419e99a87bc6ed/CHANGES#L121-L130
[Test Case]
It helps if you have lxd up and running. Otherwise, a VM or even bare
metal host also works, as long as you stick to the "ubuntu" hostname.
Launch a container for the release you are testing. The command below is for
bionic:
$ lxc launch ubuntu-daily:bionic ubuntu
Enter the container as root:
$ lxc exec ubuntu bash
Verify hostname is "ubuntu":
# hostname
ubuntu
Install apache2:
apt update && apt install apache2
Download the following files from this bug report and place them in
/etc/apache2:
cd /etc/apache2
wget
https://bugs.launchpad.net/ubuntu/+source/apache2/+bug/1833039/+attachment/5274492/+files/cacert.pem
https://bugs.launchpad.net/ubuntu/+source/apache2/+bug/1833039/+attachment/5274493/+files/ubuntu.pem
https://bugs.launchpad.net/ubuntu/+source/apache2/+bug/1833039/+attachment/5274494/+files/ubuntu.key
Adjust permissions of the key file:
chmod 0640 /etc/apache2/ubuntu.key
chgrp www-data /etc/apache2/ubuntu.key
Download the client certificate and key files and place them in /root:
client-auth.key
client-auth.pem
-
Create this vhost file (caution, lines may wrap, in particular LogFormat: it
should be one long line):
cat > /etc/apache2/sites-available/cert-auth-test.conf <
LogLevel info ssl:warn
ServerAdmin webmaster@localhost
DocumentRoot /var/www/html
LogFormat "%h %l %u %t \"%r\" %>s %O \"%{Referer}i\"
\"%{User-Agent}i\" protocol=%{SSL_PROTOCOL}x commonName=%{SSL_CLIENT_S_DN_CN}x"
combined-ssl
ErrorLog \${APACHE_LOG_DIR}/error.log
CustomLog \${APACHE_LOG_DIR}/access.log combined-ssl
SSLEngine on
SSLCertificateFile /etc/apache2/ubuntu.pem
SSLCertificateKeyFile /etc/apache2/ubuntu.key
SSLCACertificateFile /etc/apache2/cacert.pem
SSLOptions +StdEnvVars
SSLOptions +StdEnvVars
SSLVerifyClient require
Require ssl-verify-client
EOF
Enable the ssl module and this new vhost we just created:
a2enmod ssl && a2ensite cert-auth-test.conf
Restart apache2:
systemctl restart apache2
If at this stage you try the following command, it will fail like this
because no client certificate was provided:
# curl --output /dev/null https://ubuntu/ --cacert /etc/apache2/cacert.pem
% Total% Received % Xferd Average Speed TimeTime Time
Current
Dload Upload Total SpentLeft Speed
0 00 00 0 0 0 --:--:-- --:--:-- --:--:-- 0
curl: (56) OpenSSL SSL_read: error:14094410:SSL
routines:ssl3_read_bytes:sslv3 alert handshake failure, errno 0
And the apache error log will confirm the reason:
[Mon Jul 01 14:10:23.312645 2019] [ssl:error] [pid 1685:tid 140326396421888]
SSL Library Error: error:1417C0C7:SSL
routines:tls_process_client_certificate:peer did not return a certificate -- No
CAs known to server for verification?
Now retry, but providing the client certificate and key files, and forcing
TLSv1.2 just to be sure. Due to the bug, the command will stall for about 15
seconds, but the index.html file will be downloaded:
# rm -f index.html
# curl --output index.html https://ubuntu/ --cacert /etc/apache2/cacert.pem
--cert client-auth.pem --key client-auth.key --tlsv1.2
% Total% Received % Xferd Average Speed TimeTime Time
Current
Dload Upload Total SpentLeft Speed
100 10918 100 109180 0706 0 0:00:15 0:00:15 --:--:-- 2579
# ll index.html
-rw-r--r-- 1 root root 10918 Jul 1 14:15 index.html
Apache will log this in the error.log file:
[Mon Jul 01 14:15:38.014784 2019] [reqtimeout:info] [pid 1685:tid
140326278772480] [client 10.0.100.215:35108] AH01382: Request body read timeout
That is due to modreqtimeout kicking in.
In the access.log file, we will have the request:
10.0.100.215 - - [01/Jul/2019:14:15:22 +] "GET /
[Touch-packages] [Bug 1833236] Re: whoopsie ftbfs in eoan
The commit in https://code.launchpad.net/~seb128/whoopsie/nm-build- fix/+merge/369536 should fix the build issue, when testing that the package build fails due to an error in the drop privilege test though... -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to whoopsie in Ubuntu. https://bugs.launchpad.net/bugs/1833236 Title: whoopsie ftbfs in eoan Status in whoopsie package in Ubuntu: New Status in whoopsie source package in Eoan: New Bug description: whoopsie ftbfs in eoan https://launchpad.net/ubuntu/+archive/test- rebuild-20190614/+build/17048048/+files/buildlog_ubuntu-eoan- amd64.whoopsie_0.2.64_BUILDING.txt.gz dh_auto_build make -j1 make[1]: Entering directory '/<>' Package NetworkManager was not found in the pkg-config search path. Perhaps you should add the directory containing `NetworkManager.pc' to the PKG_CONFIG_PATH environment variable No package 'NetworkManager' found cc -std=c99 -c -g -Ilib -Wall -Werror -Os -DVERSION=\"0.2.64\" -fPIC -g -O2 -fdebug-prefix-map=/<>=. -fstack-protector-strong -Wformat -Werror=format-security -Wdate-time -D_FORTIFY_SOURCE=2 -o src/whoopsie.o src/whoopsie.c src/whoopsie.c:26:10: fatal error: glib.h: No such file or directory #include ^~~~ compilation terminated. make[1]: *** [Makefile:58: src/whoopsie.o] Error 1 make[1]: Leaving directory '/<>' dh_auto_build: make -j1 returned exit code 2 make: *** [debian/rules:17: build] Error 2 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/whoopsie/+bug/1833236/+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 1830479] Re: testcases expect first kernel log line, but not always in logs
** Changed in: systemd (Debian) Status: New => Fix Committed -- 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/1830479 Title: testcases expect first kernel log line, but not always in logs Status in systemd package in Ubuntu: New Status in systemd source package in Xenial: Won't Fix Status in systemd source package in Bionic: New Status in systemd source package in Cosmic: New 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 Committed Bug description: [impact] boot-and-services and cmdline-upstart-boot expect the first(ish) kernel log line to be in the system logs, but that is not guaranteed to be in the logs. [test case] run autopkgtest on arm64 with the current kernel, whose kernel log size is too small for journald or rsyslogd to capture the first kernel log messages. [regression potential] low; testcase fix only. [other info] the specific cause of this currently is too-small kernel log buffer size on arm64, which is being fixed in bug 1824864, but increasing amounts of boot time logging may cause a failure again, or custom kernel configs with small log buffers. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1830479/+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 1833039] Re: 18.04/Apache2: rejecting client initiated renegotiation due to openssl 1.1.1
** Description changed:
[Impact]
Under the following conditions, https connections using client cert
authentication will suffer a long delay (about 15s if modreqtimeout is enabled,
more if it is disabled):
* TLSv1.2
* client certificate authentication in use
* a Location, Directory, or other such block defining the client certificate
authentication for that block only, differing from the SSL vhost as a whole
This was triggered by the OpenSSL 1.1.1 SRU and was caused by this
openssl change in SSL_MODE_AUTO_RETRY from disabled to enabled by
default:
https://github.com/openssl/openssl/blob/a4a90a8a3bdcb9336b5c9c15da419e99a87bc6ed/CHANGES#L121-L130
[Test Case]
It helps if you have lxd up and running. Otherwise, a VM or even bare
metal host also works, as long as you stick to the "ubuntu" hostname.
Launch a container for the release you are testing. The command below is for
bionic:
$ lxc launch ubuntu-daily:bionic ubuntu
Enter the container as root:
$ lxc exec ubuntu bash
Verify hostname is "ubuntu":
# hostname
ubuntu
Install apache2:
apt update && apt install apache2
Download the following files from this bug report and place them in
/etc/apache2:
cd /etc/apache2
wget
https://bugs.launchpad.net/ubuntu/+source/apache2/+bug/1833039/+attachment/5274492/+files/cacert.pem
https://bugs.launchpad.net/ubuntu/+source/apache2/+bug/1833039/+attachment/5274493/+files/ubuntu.pem
https://bugs.launchpad.net/ubuntu/+source/apache2/+bug/1833039/+attachment/5274494/+files/ubuntu.key
Adjust permissions of the key file:
chmod 0640 /etc/apache2/ubuntu.key
chgrp www-data /etc/apache2/ubuntu.key
Download the client certificate and key files and place them in /root:
client-auth.key
client-auth.pem
Create this vhost file (caution, lines may wrap, in particular LogFormat: it
should be one long line):
cat > /etc/apache2/sites-available/cert-auth-test.conf <
LogLevel info ssl:warn
ServerAdmin webmaster@localhost
DocumentRoot /var/www/html
LogFormat "%h %l %u %t \"%r\" %>s %O \"%{Referer}i\"
\"%{User-Agent}i\" protocol=%{SSL_PROTOCOL}x commonName=%{SSL_CLIENT_S_DN_CN}x"
combined-ssl
ErrorLog \${APACHE_LOG_DIR}/error.log
CustomLog \${APACHE_LOG_DIR}/access.log combined-ssl
SSLEngine on
SSLCertificateFile /etc/apache2/ubuntu.pem
SSLCertificateKeyFile /etc/apache2/ubuntu.key
SSLCACertificateFile /etc/apache2/cacert.pem
SSLOptions +StdEnvVars
SSLOptions +StdEnvVars
SSLVerifyClient require
Require ssl-verify-client
EOF
Enable the ssl module and this new vhost we just created:
a2enmod ssl && a2ensite cert-auth-test.conf
Restart apache2:
systemctl restart apache2
If at this stage you try the following command, it will fail like this
because no client certificate was provided:
# curl --output /dev/null https://ubuntu/ --cacert /etc/apache2/cacert.pem
% Total% Received % Xferd Average Speed TimeTime Time
Current
Dload Upload Total SpentLeft Speed
0 00 00 0 0 0 --:--:-- --:--:-- --:--:-- 0
curl: (56) OpenSSL SSL_read: error:14094410:SSL
routines:ssl3_read_bytes:sslv3 alert handshake failure, errno 0
And the apache error log will confirm the reason:
[Mon Jul 01 14:10:23.312645 2019] [ssl:error] [pid 1685:tid 140326396421888]
SSL Library Error: error:1417C0C7:SSL
routines:tls_process_client_certificate:peer did not return a certificate -- No
CAs known to server for verification?
Now retry, but providing the client certificate and key files, and forcing
TLSv1.2 just to be sure. Due to the bug, the command will stall for about 15
seconds, but the index.html file will be downloaded:
# rm -f index.html
# curl --output index.html https://ubuntu/ --cacert /etc/apache2/cacert.pem
--cert client-auth.pem --key client-auth.key --tlsv1.2
% Total% Received % Xferd Average Speed TimeTime Time
Current
Dload Upload Total SpentLeft Speed
100 10918 100 109180 0706 0 0:00:15 0:00:15 --:--:-- 2579
# ll index.html
-rw-r--r-- 1 root root 10918 Jul 1 14:15 index.html
Apache will log this in the error.log file:
[Mon Jul 01 14:15:38.014784 2019] [reqtimeout:info] [pid 1685:tid
140326278772480] [client 10.0.100.215:35108] AH01382: Request body read timeout
That is due to modreqtimeout kicking in.
In the access.log file, we will have the request:
10.0.100.215 - - [01/Jul/2019:14:15:22 +] "GET / HTTP/1.1" 200 16544 "-"
"curl/7.58.0" protocol=TLSv1.2 commonName=client-auth
The protocol and commonName parts confirm the protocol that was used, and
[Touch-packages] [Bug 1833236] Re: whoopsie ftbfs in eoan
(the test/build doesn't fail in a ppa so probably a chroot/env issue) -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to whoopsie in Ubuntu. https://bugs.launchpad.net/bugs/1833236 Title: whoopsie ftbfs in eoan Status in whoopsie package in Ubuntu: New Status in whoopsie source package in Eoan: New Bug description: whoopsie ftbfs in eoan https://launchpad.net/ubuntu/+archive/test- rebuild-20190614/+build/17048048/+files/buildlog_ubuntu-eoan- amd64.whoopsie_0.2.64_BUILDING.txt.gz dh_auto_build make -j1 make[1]: Entering directory '/<>' Package NetworkManager was not found in the pkg-config search path. Perhaps you should add the directory containing `NetworkManager.pc' to the PKG_CONFIG_PATH environment variable No package 'NetworkManager' found cc -std=c99 -c -g -Ilib -Wall -Werror -Os -DVERSION=\"0.2.64\" -fPIC -g -O2 -fdebug-prefix-map=/<>=. -fstack-protector-strong -Wformat -Werror=format-security -Wdate-time -D_FORTIFY_SOURCE=2 -o src/whoopsie.o src/whoopsie.c src/whoopsie.c:26:10: fatal error: glib.h: No such file or directory #include ^~~~ compilation terminated. make[1]: *** [Makefile:58: src/whoopsie.o] Error 1 make[1]: Leaving directory '/<>' dh_auto_build: make -j1 returned exit code 2 make: *** [debian/rules:17: build] Error 2 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/whoopsie/+bug/1833236/+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 1833039] Re: 18.04/Apache2: rejecting client initiated renegotiation due to openssl 1.1.1
** Description changed:
[Impact]
Under the following conditions, https connections using client cert
authentication will suffer a long delay (about 15s if modreqtimeout is enabled,
more if it is disabled):
* TLSv1.2
* client certificate authentication in use
* a Location, Directory, or other such block defining the client certificate
authentication for that block only, differing from the SSL vhost as a whole
This was triggered by the OpenSSL 1.1.1 SRU and was caused by this
openssl change in SSL_MODE_AUTO_RETRY from disabled to enabled by
default:
https://github.com/openssl/openssl/blob/a4a90a8a3bdcb9336b5c9c15da419e99a87bc6ed/CHANGES#L121-L130
[Test Case]
It helps if you have lxd up and running. Otherwise, a VM or even bare
metal host also works, as long as you stick to the "ubuntu" hostname.
Launch a container for the release you are testing. The command below is for
bionic:
$ lxc launch ubuntu-daily:bionic ubuntu
Enter the container as root:
$ lxc exec ubuntu bash
Verify hostname is "ubuntu":
# hostname
ubuntu
Install apache2:
apt update && apt install apache2
Download the following files from this bug report and place them in
/etc/apache2:
cd /etc/apache2
wget
https://bugs.launchpad.net/ubuntu/+source/apache2/+bug/1833039/+attachment/5274492/+files/cacert.pem
https://bugs.launchpad.net/ubuntu/+source/apache2/+bug/1833039/+attachment/5274493/+files/ubuntu.pem
https://bugs.launchpad.net/ubuntu/+source/apache2/+bug/1833039/+attachment/5274494/+files/ubuntu.key
Adjust permissions of the key file:
chmod 0640 /etc/apache2/ubuntu.key
chgrp www-data /etc/apache2/ubuntu.key
Download the client certificate and key files and place them in /root:
+ cd /root
+ wget
https://bugs.launchpad.net/ubuntu/+source/apache2/+bug/1833039/+attachment/5274495/+files/client-auth.pem
https://bugs.launchpad.net/ubuntu/+source/apache2/+bug/1833039/+attachment/5274496/+files/client-auth.key
client-auth.key
client-auth.pem
Create this vhost file (caution, lines may wrap, in particular LogFormat: it
should be one long line):
cat > /etc/apache2/sites-available/cert-auth-test.conf <
LogLevel info ssl:warn
ServerAdmin webmaster@localhost
DocumentRoot /var/www/html
LogFormat "%h %l %u %t \"%r\" %>s %O \"%{Referer}i\"
\"%{User-Agent}i\" protocol=%{SSL_PROTOCOL}x commonName=%{SSL_CLIENT_S_DN_CN}x"
combined-ssl
ErrorLog \${APACHE_LOG_DIR}/error.log
CustomLog \${APACHE_LOG_DIR}/access.log combined-ssl
SSLEngine on
SSLCertificateFile /etc/apache2/ubuntu.pem
SSLCertificateKeyFile /etc/apache2/ubuntu.key
SSLCACertificateFile /etc/apache2/cacert.pem
SSLOptions +StdEnvVars
SSLOptions +StdEnvVars
SSLVerifyClient require
Require ssl-verify-client
EOF
Enable the ssl module and this new vhost we just created:
a2enmod ssl && a2ensite cert-auth-test.conf
Restart apache2:
systemctl restart apache2
If at this stage you try the following command, it will fail like this
because no client certificate was provided:
# curl --output /dev/null https://ubuntu/ --cacert /etc/apache2/cacert.pem
% Total% Received % Xferd Average Speed TimeTime Time
Current
Dload Upload Total SpentLeft Speed
0 00 00 0 0 0 --:--:-- --:--:-- --:--:-- 0
curl: (56) OpenSSL SSL_read: error:14094410:SSL
routines:ssl3_read_bytes:sslv3 alert handshake failure, errno 0
And the apache error log will confirm the reason:
[Mon Jul 01 14:10:23.312645 2019] [ssl:error] [pid 1685:tid 140326396421888]
SSL Library Error: error:1417C0C7:SSL
routines:tls_process_client_certificate:peer did not return a certificate -- No
CAs known to server for verification?
Now retry, but providing the client certificate and key files, and forcing
TLSv1.2 just to be sure. Due to the bug, the command will stall for about 15
seconds, but the index.html file will be downloaded:
# rm -f index.html
# curl --output index.html https://ubuntu/ --cacert /etc/apache2/cacert.pem
--cert client-auth.pem --key client-auth.key --tlsv1.2
% Total% Received % Xferd Average Speed TimeTime Time
Current
Dload Upload Total SpentLeft Speed
100 10918 100 109180 0706 0 0:00:15 0:00:15 --:--:-- 2579
# ll index.html
-rw-r--r-- 1 root root 10918 Jul 1 14:15 index.html
Apache will log this in the error.log file:
[Mon Jul 01 14:15:38.014784 2019] [reqtimeout:info] [pid 1685:tid
140326278772480] [client 10.0.100.215:35108] AH01382: Request body read timeout
That is due to modreqtimeout kicking in.
In the access.log file, we will
[Touch-packages] [Bug 1833039] Re: 18.04/Apache2: rejecting client initiated renegotiation due to openssl 1.1.1
** Merge proposal linked:
https://code.launchpad.net/~ahasenack/ubuntu/+source/apache2/+git/apache2/+merge/369541
** Merge proposal linked:
https://code.launchpad.net/~ahasenack/ubuntu/+source/apache2/+git/apache2/+merge/369542
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to openssl in Ubuntu.
https://bugs.launchpad.net/bugs/1833039
Title:
18.04/Apache2: rejecting client initiated renegotiation due to openssl
1.1.1
Status in apache2 package in Ubuntu:
Fix Released
Status in openssl package in Ubuntu:
Invalid
Status in apache2 source package in Bionic:
In Progress
Status in apache2 source package in Cosmic:
In Progress
Bug description:
[Impact]
Under the following conditions, https connections using client cert
authentication will suffer a long delay (about 15s if modreqtimeout is enabled,
more if it is disabled):
* TLSv1.2
* client certificate authentication in use
* a Location, Directory, or other such block defining the client certificate
authentication for that block only, differing from the SSL vhost as a whole
This was triggered by the OpenSSL 1.1.1 SRU and was caused by this
openssl change in SSL_MODE_AUTO_RETRY from disabled to enabled by
default:
https://github.com/openssl/openssl/blob/a4a90a8a3bdcb9336b5c9c15da419e99a87bc6ed/CHANGES#L121-L130
[Test Case]
It helps if you have lxd up and running. Otherwise, a VM or even bare
metal host also works, as long as you stick to the "ubuntu" hostname.
Launch a container for the release you are testing. The command below is for
bionic:
$ lxc launch ubuntu-daily:bionic ubuntu
Enter the container as root:
$ lxc exec ubuntu bash
Verify hostname is "ubuntu":
# hostname
ubuntu
Install apache2:
apt update && apt install apache2
Download the following files from this bug report and place them in
/etc/apache2:
cd /etc/apache2
wget
https://bugs.launchpad.net/ubuntu/+source/apache2/+bug/1833039/+attachment/5274492/+files/cacert.pem
https://bugs.launchpad.net/ubuntu/+source/apache2/+bug/1833039/+attachment/5274493/+files/ubuntu.pem
https://bugs.launchpad.net/ubuntu/+source/apache2/+bug/1833039/+attachment/5274494/+files/ubuntu.key
Adjust permissions of the key file:
chmod 0640 /etc/apache2/ubuntu.key
chgrp www-data /etc/apache2/ubuntu.key
Download the client certificate and key files and place them in /root:
cd /root
wget
https://bugs.launchpad.net/ubuntu/+source/apache2/+bug/1833039/+attachment/5274495/+files/client-auth.pem
https://bugs.launchpad.net/ubuntu/+source/apache2/+bug/1833039/+attachment/5274496/+files/client-auth.key
Create this vhost file (caution, lines may wrap, in particular LogFormat: it
should be one long line):
cat > /etc/apache2/sites-available/cert-auth-test.conf <
LogLevel info ssl:warn
ServerAdmin webmaster@localhost
DocumentRoot /var/www/html
LogFormat "%h %l %u %t \"%r\" %>s %O \"%{Referer}i\"
\"%{User-Agent}i\" protocol=%{SSL_PROTOCOL}x commonName=%{SSL_CLIENT_S_DN_CN}x"
combined-ssl
ErrorLog \${APACHE_LOG_DIR}/error.log
CustomLog \${APACHE_LOG_DIR}/access.log combined-ssl
SSLEngine on
SSLCertificateFile /etc/apache2/ubuntu.pem
SSLCertificateKeyFile /etc/apache2/ubuntu.key
SSLCACertificateFile /etc/apache2/cacert.pem
SSLOptions +StdEnvVars
SSLOptions +StdEnvVars
SSLVerifyClient require
Require ssl-verify-client
EOF
Enable the ssl module and this new vhost we just created:
a2enmod ssl && a2ensite cert-auth-test.conf
Restart apache2:
systemctl restart apache2
If at this stage you try the following command, it will fail like this
because no client certificate was provided:
# curl --output /dev/null https://ubuntu/ --cacert /etc/apache2/cacert.pem
% Total% Received % Xferd Average Speed TimeTime Time
Current
Dload Upload Total SpentLeft Speed
0 00 00 0 0 0 --:--:-- --:--:-- --:--:-- 0
curl: (56) OpenSSL SSL_read: error:14094410:SSL
routines:ssl3_read_bytes:sslv3 alert handshake failure, errno 0
And the apache error log will confirm the reason:
[Mon Jul 01 14:10:23.312645 2019] [ssl:error] [pid 1685:tid 140326396421888]
SSL Library Error: error:1417C0C7:SSL
routines:tls_process_client_certificate:peer did not return a certificate -- No
CAs known to server for verification?
Now retry, but providing the client certificate and key files, and forcing
TLSv1.2 just to be sure. Due to the bug, the command will stall for about 15
seconds, but the index.html file will be downloaded:
# rm -f index.html
# curl --output index.html https://ubuntu/ --cacert /etc/apache2/cacert.pem
[Touch-packages] [Bug 1829829] Re: Ubuntu CI has been flaky for a week
> That PR on GitHub hasn't been merged yet so I think it's too soon to
turn those tests off.
ack - I closed the MR to debian to blacklist them.
> Apparently on Ubuntu CI the tests are still run one by one
yep. I'll look at how Centos runs them to see if we can run them in
parallel on Ubuntu as well; that should really significantly speed up
the overall test time.
> could anyone either bump up the timeout or turn the test off?
The overall timeout is set from autopkgtest.ubuntu.com, so the test itself
can't request a longer timeout IIUC, but it could be marked as a "long running":
https://git.launchpad.net/autopkgtest-cloud/tree/worker-config-production/worker.conf#n20
The default timeout is 10,000s, while long running tests get 40,000s. However,
that's over 11 hours; I'd much rather work to get test runs under the default
10,000s (~3 hours).
Let's see if we can get the 'upstream' tests parallelized, I think that
would avoid ever exceeding the main test timeout, except for actual hung
test cases.
> would it be OK to mention that you maintain Ubuntu CI at
> https://www.freedesktop.org/wiki/Software/systemd/autopkgtest
it looks like @laney is listed there, which is probably appropriate (he
has admin access to the test systems, while I don't), but if you want to
add me as a contact for systemd Ubuntu-CI that's fine with me.
--
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/1829829
Title:
Ubuntu CI has been flaky for a week
Status in systemd package in Ubuntu:
Confirmed
Bug description:
It was originally reported in
https://github.com/systemd/systemd/pull/12583#issuecomment-492949206 5 days
ago. To judge from the logs VMs can't be rebooted there:
```
Ubuntu 18.04.2 LTS autopkgtest ttyS0
autopkgtest login:
---
--- nova show 91e76a78-d05c-412a-b383-55a26010ae69
(adt-bionic-amd64-systemd-upstream-20190516-051604) --
+--++
| Property | Value
|
+--++
| OS-DCF:diskConfig| MANUAL
|
| OS-EXT-AZ:availability_zone | nova
|
| OS-EXT-SRV-ATTR:host | euler
|
| OS-EXT-SRV-ATTR:hypervisor_hostname | euler.lcy01.scalingstack
|
| OS-EXT-SRV-ATTR:instance_name| instance-003d216a
|
| OS-EXT-STS:power_state | 1
|
| OS-EXT-STS:task_state| -
|
| OS-EXT-STS:vm_state | active
|
| OS-SRV-USG:launched_at | 2019-05-16T07:00:42.00
|
| OS-SRV-USG:terminated_at | -
|
| accessIPv4 |
|
| accessIPv6 |
|
| config_drive |
|
| created | 2019-05-16T07:00:33Z
|
| flavor | autopkgtest
(f878e70e-9991-46e0-ba02-8ea159a71656) |
| hostId |
1722c5f2face86c3fc9f338ae96835924721512372342f664e6941bd
|
| id | 91e76a78-d05c-412a-b383-55a26010ae69
|
| image|
adt/ubuntu-bionic-amd64-server-20190516.img
(d00bf12c-467e-433f-a4f5-15720f13bff1) |
| key_name |
testbed-juju-prod-ues-proposed-migration-machine-11
|
| metadata | {}
[Touch-packages] [Bug 1829829] Re: Ubuntu CI has been flaky for a week
>From https://github.com/systemd/systemd/issues/12268#issuecomment-506953576
looks like TEST-30 is actually failing due to service start timeout (of 25
seconds); this test should be added to the blacklist until we can get it
reliably passing.
** Bug watch added: github.com/systemd/systemd/issues #12268
https://github.com/systemd/systemd/issues/12268
--
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/1829829
Title:
Ubuntu CI has been flaky for a week
Status in systemd package in Ubuntu:
Confirmed
Bug description:
It was originally reported in
https://github.com/systemd/systemd/pull/12583#issuecomment-492949206 5 days
ago. To judge from the logs VMs can't be rebooted there:
```
Ubuntu 18.04.2 LTS autopkgtest ttyS0
autopkgtest login:
---
--- nova show 91e76a78-d05c-412a-b383-55a26010ae69
(adt-bionic-amd64-systemd-upstream-20190516-051604) --
+--++
| Property | Value
|
+--++
| OS-DCF:diskConfig| MANUAL
|
| OS-EXT-AZ:availability_zone | nova
|
| OS-EXT-SRV-ATTR:host | euler
|
| OS-EXT-SRV-ATTR:hypervisor_hostname | euler.lcy01.scalingstack
|
| OS-EXT-SRV-ATTR:instance_name| instance-003d216a
|
| OS-EXT-STS:power_state | 1
|
| OS-EXT-STS:task_state| -
|
| OS-EXT-STS:vm_state | active
|
| OS-SRV-USG:launched_at | 2019-05-16T07:00:42.00
|
| OS-SRV-USG:terminated_at | -
|
| accessIPv4 |
|
| accessIPv6 |
|
| config_drive |
|
| created | 2019-05-16T07:00:33Z
|
| flavor | autopkgtest
(f878e70e-9991-46e0-ba02-8ea159a71656) |
| hostId |
1722c5f2face86c3fc9f338ae96835924721512372342f664e6941bd
|
| id | 91e76a78-d05c-412a-b383-55a26010ae69
|
| image|
adt/ubuntu-bionic-amd64-server-20190516.img
(d00bf12c-467e-433f-a4f5-15720f13bff1) |
| key_name |
testbed-juju-prod-ues-proposed-migration-machine-11
|
| metadata | {}
|
| name |
adt-bionic-amd64-systemd-upstream-20190516-051604
|
| net_ues_proposed_migration network | 10.42.40.13
|
| os-extended-volumes:volumes_attached | []
|
| progress | 0
|
| security_groups | autopkgtest@lcy01-27.secgroup
|
| status | ACTIVE
|
| tenant_id| afaef86b96dd4828a1ed5ee395ea1421
|
| updated | 2019-05-16T07:00:42Z
[Touch-packages] [Bug 1822776] Re: [SRU] Apply Bash 4.4.20 to fix cpu spinning on built-in wait
Hi halfgaar, just checking in on how the testing has been coming along? -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to bash in Ubuntu. https://bugs.launchpad.net/bugs/1822776 Title: [SRU] Apply Bash 4.4.20 to fix cpu spinning on built-in wait Status in bash package in Ubuntu: Fix Released Status in bash source package in Bionic: Fix Committed Status in bash source package in Cosmic: Fix Committed Bug description: [Impact] Long running bash loops that create and reap processes will crash, hanging at 100% CPU. [Test Case] A PPA with the proposed fix included is at: https://launchpad.net/~bryce/+archive/ubuntu/bash-sru-19-010-1 Install the PPA with the fix via: sudo add-apt-repository ppa:bryce/bash-sru-19-010-1 sudo apt-get update sudo apt-get install bash Run this loop for a few days/weeks: #!/bin/bash while true; do sleep 0.5 & wait done It will eventually cause the 'wait' statement to hang, consuming 100% after some indeterminate amount of time, dependent on how fast PIDs are cycled in the machine. The Bash bug report mentions longer running loops, but it seems hash collisions are the cause, meaning it's just a matter of chance, influenced by how fast PIDs are cycled on the machine. [Regression Potential] The fix has been reviewed and accepted upstream. The patch adds a test at time of pid determination for if the pid is already in use and if so, skip it and pick a different one. This does change behavior slightly in that different pid numbers will be generated in rare cases, but nothing should depend on how pids are generated, as the behavior is not specified to be anything but random. The patch adds a new warning message, "bgp_delete: LOOP: psi (%d) == storage[psi].bucket_next", but this only shows when the original bug would have been triggered. Using 'apt-get source bash' to get the original source version, I created a deb that includes the 4.4.20 patch and have been running it since April 2nd. The 100% CPU spinning is solved, and no other regressions have been observed. Ubuntu 18.04 is already at 4.4.19, which is one patch level behind, so this involves linearly progressing to the next version (so not skipping patches). [Fix] Official patch to fix, and to bump to 4.4.20: http://ftp.gnu.org/gnu/bash/bash-4.4-patches/bash44-020 The newest Ubuntu tar.xz with patches I could find at: http://archive.ubuntu.com/ubuntu/pool/main/b/bash/ also didn't have the 4.4.20 patch, so it seems no Ubuntu release has the fix yet. Although not completely sure, this problem seems to have been introduced in the 4.4 version of Bash, so in term of LTS versions, 18.04 and up are affected. [Original Report] Bash pre-4.4.20 has a bug in its PID hash table that causes spin-loops when spawning sub processes and waiting for them. There is a fix: https://ftp.gnu.org/gnu/bash/bash-4.4-patches/bash44-020 Our application started being affected (locking up) by this since migrating from Ubuntu 14.04 to 18.04. Ubuntu 14.04 has bash 4.3.11(1), Ubuntu 18.04 has bash 4.4.19 (that is, when running 'bash --version', because of their unusual versions as patches, apt shows it as 4.4.18-2ubuntu1). The 4.4-020 version needs to be included. I think it's actually quite critical. A justification for including the fix would be that a standard language feature in a script language is broken, and that it's indeterminate when it breaks. Considering the wide spread use of bash, I'm surprised not more people have reported issues. My and a client started having issues with independently of each other very soon after upgrading to an affected version. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bash/+bug/1822776/+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 1833236] Re: whoopsie ftbfs in eoan
** Branch linked: lp:whoopsie -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to whoopsie in Ubuntu. https://bugs.launchpad.net/bugs/1833236 Title: whoopsie ftbfs in eoan Status in whoopsie package in Ubuntu: New Status in whoopsie source package in Eoan: New Bug description: whoopsie ftbfs in eoan https://launchpad.net/ubuntu/+archive/test- rebuild-20190614/+build/17048048/+files/buildlog_ubuntu-eoan- amd64.whoopsie_0.2.64_BUILDING.txt.gz dh_auto_build make -j1 make[1]: Entering directory '/<>' Package NetworkManager was not found in the pkg-config search path. Perhaps you should add the directory containing `NetworkManager.pc' to the PKG_CONFIG_PATH environment variable No package 'NetworkManager' found cc -std=c99 -c -g -Ilib -Wall -Werror -Os -DVERSION=\"0.2.64\" -fPIC -g -O2 -fdebug-prefix-map=/<>=. -fstack-protector-strong -Wformat -Werror=format-security -Wdate-time -D_FORTIFY_SOURCE=2 -o src/whoopsie.o src/whoopsie.c src/whoopsie.c:26:10: fatal error: glib.h: No such file or directory #include ^~~~ compilation terminated. make[1]: *** [Makefile:58: src/whoopsie.o] Error 1 make[1]: Leaving directory '/<>' dh_auto_build: make -j1 returned exit code 2 make: *** [debian/rules:17: build] Error 2 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/whoopsie/+bug/1833236/+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 1513528] Re: /usr/bin/software-properties-gtk:KeyError:__getitem__:__getitem__:show_drivers:set_driver_action_status:__getitem__
** Changed in: software-properties (Ubuntu) Status: New => Confirmed -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to software-properties in Ubuntu. https://bugs.launchpad.net/bugs/1513528 Title: /usr/bin/software-properties- gtk:KeyError:__getitem__:__getitem__:show_drivers:set_driver_action_status:__getitem__ Status in software-properties package in Ubuntu: Confirmed Bug description: The Ubuntu Error Tracker has been receiving reports about a problem regarding software-properties. This problem was most recently seen with version 0.96.13.1, the problem page at https://errors.ubuntu.com/problem/9de02a9f290237dd5c83e9cc73db340a544b362d contains more details. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/software-properties/+bug/1513528/+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 1834957] [NEW] Automatic generated printer in CUPS
Public bug reported: The automatic generated printer don't work. It is possible to use Settings and add the printer. It is possible to delete the faulty printer in Setting, but every time the printer is turned on the faulty printer is generated again. It is also possible to use Settings to block the printer, but after login the printer is activated again. There is also notifications about the printout until the printout is canceled. ProblemType: Bug DistroRelease: Ubuntu 19.10 Package: cups 2.2.10-6ubuntu1 ProcVersionSignature: Ubuntu 5.0.0-17.18-generic 5.0.8 Uname: Linux 5.0.0-17-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu3 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Mon Jul 1 19:23:17 2019 InstallationDate: Installed on 2019-07-01 (0 days ago) InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Alpha amd64 (20190701) Lpstat: device for Brother_HL_3140CW_series: implicitclass://Brother_HL_3140CW_series/ MachineType: Gigabyte Technology Co., Ltd. GA-990FXA-UD3 Papersize: a4 PpdFiles: Error: command ['fgrep', '-H', '*NickName', '/etc/cups/ppd/Brother_HL_3140CW_series.ppd'] failed with exit code 2: grep: /etc/cups/ppd/Brother_HL_3140CW_series.ppd: Permission denied ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.0.0-17-generic root=UUID=27f650c7-e62f-48f9-acce-c3c8e92f109e ro quiet splash vt.handoff=1 SourcePackage: cups UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 10/13/2011 dmi.bios.vendor: Award Software International, Inc. dmi.bios.version: F5 dmi.board.name: GA-990FXA-UD3 dmi.board.vendor: Gigabyte Technology Co., Ltd. dmi.board.version: x.x dmi.chassis.type: 3 dmi.chassis.vendor: Gigabyte Technology Co., Ltd. dmi.modalias: dmi:bvnAwardSoftwareInternational,Inc.:bvrF5:bd10/13/2011:svnGigabyteTechnologyCo.,Ltd.:pnGA-990FXA-UD3:pvr:rvnGigabyteTechnologyCo.,Ltd.:rnGA-990FXA-UD3:rvrx.x:cvnGigabyteTechnologyCo.,Ltd.:ct3:cvr: dmi.product.name: GA-990FXA-UD3 dmi.sys.vendor: Gigabyte Technology Co., Ltd. ** Affects: cups (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug eoan -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to cups in Ubuntu. https://bugs.launchpad.net/bugs/1834957 Title: Automatic generated printer in CUPS Status in cups package in Ubuntu: New Bug description: The automatic generated printer don't work. It is possible to use Settings and add the printer. It is possible to delete the faulty printer in Setting, but every time the printer is turned on the faulty printer is generated again. It is also possible to use Settings to block the printer, but after login the printer is activated again. There is also notifications about the printout until the printout is canceled. ProblemType: Bug DistroRelease: Ubuntu 19.10 Package: cups 2.2.10-6ubuntu1 ProcVersionSignature: Ubuntu 5.0.0-17.18-generic 5.0.8 Uname: Linux 5.0.0-17-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu3 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Mon Jul 1 19:23:17 2019 InstallationDate: Installed on 2019-07-01 (0 days ago) InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Alpha amd64 (20190701) Lpstat: device for Brother_HL_3140CW_series: implicitclass://Brother_HL_3140CW_series/ MachineType: Gigabyte Technology Co., Ltd. GA-990FXA-UD3 Papersize: a4 PpdFiles: Error: command ['fgrep', '-H', '*NickName', '/etc/cups/ppd/Brother_HL_3140CW_series.ppd'] failed with exit code 2: grep: /etc/cups/ppd/Brother_HL_3140CW_series.ppd: Permission denied ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.0.0-17-generic root=UUID=27f650c7-e62f-48f9-acce-c3c8e92f109e ro quiet splash vt.handoff=1 SourcePackage: cups UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 10/13/2011 dmi.bios.vendor: Award Software International, Inc. dmi.bios.version: F5 dmi.board.name: GA-990FXA-UD3 dmi.board.vendor: Gigabyte Technology Co., Ltd. dmi.board.version: x.x dmi.chassis.type: 3 dmi.chassis.vendor: Gigabyte Technology Co., Ltd. dmi.modalias: dmi:bvnAwardSoftwareInternational,Inc.:bvrF5:bd10/13/2011:svnGigabyteTechnologyCo.,Ltd.:pnGA-990FXA-UD3:pvr:rvnGigabyteTechnologyCo.,Ltd.:rnGA-990FXA-UD3:rvrx.x:cvnGigabyteTechnologyCo.,Ltd.:ct3:cvr: dmi.product.name: GA-990FXA-UD3 dmi.sys.vendor: Gigabyte Technology Co., Ltd. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/cups/+bug/1834957/+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 1829829] Re: Ubuntu CI has been flaky for a week
Looking at the latest 20 i386 tests, I see failing tests for 12888, 12884, 12912, 12918, and 12919. PR 12884 looks like it's adding a new test, TEST-35, so I'll assume that test just needs more work. PR 12888 failed once, but there are 3 later tests that all pass, so I assume it's ok now. PR 12919 appears to have failed while building upstream systemd, so I assume that's a problem with the PR. PR 12912 passed once, but then was run again and failed due to TEST-34 timing out. PR 12918 failed also with TEST-34 timing out. However, these aren't failing because they just didn't have enough time to run. They are failing because they are running "systemd-run --wait" but the --wait never completes, even though the service finishes. This is what I was talking about before when I mentioned that dbus (bus-api- system) appears to be crashing/restarting. Note in the failing test upstream-stdout: $ grep -E '(bus-api-system|run-u7)' upstream-stdout ... run-u7.service: Installed new job run-u7.service/start as 322 run-u7.service: Enqueued job run-u7.service/start as 322 Bus bus-api-system: changing state RUNNING → CLOSING Bus bus-api-system: changing state CLOSING → CLOSED Bus bus-api-system: changing state UNSET → OPENING Bus bus-api-system: changing state OPENING → AUTHENTICATING run-u7.service: Failed to set 'memory.min' attribute on '/system.slice/run-u7.service' to '0': No such file or directory run-u7.service: Failed to set 'memory.swap.max' attribute on '/system.slice/run-u7.service' to 'max': No such file or directory run-u7.service: Failed to set 'memory.oom.group' attribute on '/system.slice/run-u7.service' to '0': No such file or directory run-u7.service: Passing 0 fds to service run-u7.service: About to execute: /usr/bin/test -f /var/lib/zzz/test run-u7.service: Forked /usr/bin/test as 274 run-u7.service: Changed dead -> runningFound pre-existing private StateDirectory= directory /var/lib/private/zzz, migrating to /var/lib/zzz. run-u7.service: Job 322 run-u7.service/start finished, result=done run-u7.service: Executing: /usr/bin/test -f /var/lib/zzz/testsystemd-journald.service: Got notification message from PID 210 (WATCHDOG=1) run-u7.service: Child 274 belongs to run-u7.service. run-u7.service: Main process exited, code=exited, status=0/SUCCESS run-u7.service: Succeeded. run-u7.service: Changed running -> dead run-u7.service: Consumed 59ms CPU time. run-u7.service: Collecting. Bus bus-api-system: changing state AUTHENTICATING → HELLO Bus bus-api-system: changing state HELLO → RUNNING It looks like bus-api-system is down when the service completes, and the notification that it finished never reaches the system-run --wait caller (the testsuite), so the testsuite just hangs doing nothing until the test timeout. -- 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/1829829 Title: Ubuntu CI has been flaky for a week Status in systemd package in Ubuntu: Confirmed Bug description: It was originally reported in https://github.com/systemd/systemd/pull/12583#issuecomment-492949206 5 days ago. To judge from the logs VMs can't be rebooted there: ``` Ubuntu 18.04.2 LTS autopkgtest ttyS0 autopkgtest login: --- --- nova show 91e76a78-d05c-412a-b383-55a26010ae69 (adt-bionic-amd64-systemd-upstream-20190516-051604) -- +--++ | Property | Value | +--++ | OS-DCF:diskConfig| MANUAL | | OS-EXT-AZ:availability_zone | nova | | OS-EXT-SRV-ATTR:host | euler | | OS-EXT-SRV-ATTR:hypervisor_hostname | euler.lcy01.scalingstack | | OS-EXT-SRV-ATTR:instance_name| instance-003d216a | | OS-EXT-STS:power_state | 1 | | OS-EXT-STS:task_state| - | | OS-EXT-STS:vm_state | active | | OS-SRV-USG:launched_at | 2019-05-16T07:00:42.00
[Touch-packages] [Bug 1833236] Re: whoopsie ftbfs in eoan
** Changed in: whoopsie (Ubuntu Eoan) Status: New => Fix Committed -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to whoopsie in Ubuntu. https://bugs.launchpad.net/bugs/1833236 Title: whoopsie ftbfs in eoan Status in whoopsie package in Ubuntu: Fix Committed Status in whoopsie source package in Eoan: Fix Committed Bug description: whoopsie ftbfs in eoan https://launchpad.net/ubuntu/+archive/test- rebuild-20190614/+build/17048048/+files/buildlog_ubuntu-eoan- amd64.whoopsie_0.2.64_BUILDING.txt.gz dh_auto_build make -j1 make[1]: Entering directory '/<>' Package NetworkManager was not found in the pkg-config search path. Perhaps you should add the directory containing `NetworkManager.pc' to the PKG_CONFIG_PATH environment variable No package 'NetworkManager' found cc -std=c99 -c -g -Ilib -Wall -Werror -Os -DVERSION=\"0.2.64\" -fPIC -g -O2 -fdebug-prefix-map=/<>=. -fstack-protector-strong -Wformat -Werror=format-security -Wdate-time -D_FORTIFY_SOURCE=2 -o src/whoopsie.o src/whoopsie.c src/whoopsie.c:26:10: fatal error: glib.h: No such file or directory #include ^~~~ compilation terminated. make[1]: *** [Makefile:58: src/whoopsie.o] Error 1 make[1]: Leaving directory '/<>' dh_auto_build: make -j1 returned exit code 2 make: *** [debian/rules:17: build] Error 2 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/whoopsie/+bug/1833236/+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 1833039] Re: 18.04/Apache2: rejecting client initiated renegotiation due to openssl 1.1.1
** Description changed:
[Impact]
Under the following conditions, https connections using client cert
authentication will suffer a long delay (about 15s if modreqtimeout is enabled,
more if it is disabled):
* TLSv1.2
* client certificate authentication in use
* a Location, Directory, or other such block defining the client certificate
authentication for that block only, differing from the SSL vhost as a whole
This was triggered by the OpenSSL 1.1.1 SRU and was caused by this
openssl change in SSL_MODE_AUTO_RETRY from disabled to enabled by
default:
https://github.com/openssl/openssl/blob/a4a90a8a3bdcb9336b5c9c15da419e99a87bc6ed/CHANGES#L121-L130
[Test Case]
It helps if you have lxd up and running. Otherwise, a VM or even bare
metal host also works, as long as you stick to the "ubuntu" hostname.
Launch a container for the release you are testing. The command below is for
bionic:
$ lxc launch ubuntu-daily:bionic ubuntu
Enter the container as root:
$ lxc exec ubuntu bash
Verify hostname is "ubuntu":
# hostname
ubuntu
Install apache2:
apt update && apt install apache2
Download the following files from this bug report and place them in
/etc/apache2:
cd /etc/apache2
wget
https://bugs.launchpad.net/ubuntu/+source/apache2/+bug/1833039/+attachment/5274492/+files/cacert.pem
https://bugs.launchpad.net/ubuntu/+source/apache2/+bug/1833039/+attachment/5274493/+files/ubuntu.pem
https://bugs.launchpad.net/ubuntu/+source/apache2/+bug/1833039/+attachment/5274494/+files/ubuntu.key
Adjust permissions of the key file:
chmod 0640 /etc/apache2/ubuntu.key
chgrp www-data /etc/apache2/ubuntu.key
Download the client certificate and key files and place them in /root:
cd /root
wget
https://bugs.launchpad.net/ubuntu/+source/apache2/+bug/1833039/+attachment/5274495/+files/client-auth.pem
https://bugs.launchpad.net/ubuntu/+source/apache2/+bug/1833039/+attachment/5274496/+files/client-auth.key
- client-auth.key
- client-auth.pem
Create this vhost file (caution, lines may wrap, in particular LogFormat: it
should be one long line):
cat > /etc/apache2/sites-available/cert-auth-test.conf <
LogLevel info ssl:warn
ServerAdmin webmaster@localhost
DocumentRoot /var/www/html
LogFormat "%h %l %u %t \"%r\" %>s %O \"%{Referer}i\"
\"%{User-Agent}i\" protocol=%{SSL_PROTOCOL}x commonName=%{SSL_CLIENT_S_DN_CN}x"
combined-ssl
ErrorLog \${APACHE_LOG_DIR}/error.log
CustomLog \${APACHE_LOG_DIR}/access.log combined-ssl
SSLEngine on
SSLCertificateFile /etc/apache2/ubuntu.pem
SSLCertificateKeyFile /etc/apache2/ubuntu.key
SSLCACertificateFile /etc/apache2/cacert.pem
SSLOptions +StdEnvVars
SSLOptions +StdEnvVars
SSLVerifyClient require
Require ssl-verify-client
EOF
Enable the ssl module and this new vhost we just created:
a2enmod ssl && a2ensite cert-auth-test.conf
Restart apache2:
systemctl restart apache2
If at this stage you try the following command, it will fail like this
because no client certificate was provided:
# curl --output /dev/null https://ubuntu/ --cacert /etc/apache2/cacert.pem
% Total% Received % Xferd Average Speed TimeTime Time
Current
Dload Upload Total SpentLeft Speed
0 00 00 0 0 0 --:--:-- --:--:-- --:--:-- 0
curl: (56) OpenSSL SSL_read: error:14094410:SSL
routines:ssl3_read_bytes:sslv3 alert handshake failure, errno 0
And the apache error log will confirm the reason:
[Mon Jul 01 14:10:23.312645 2019] [ssl:error] [pid 1685:tid 140326396421888]
SSL Library Error: error:1417C0C7:SSL
routines:tls_process_client_certificate:peer did not return a certificate -- No
CAs known to server for verification?
Now retry, but providing the client certificate and key files, and forcing
TLSv1.2 just to be sure. Due to the bug, the command will stall for about 15
seconds, but the index.html file will be downloaded:
# rm -f index.html
# curl --output index.html https://ubuntu/ --cacert /etc/apache2/cacert.pem
--cert client-auth.pem --key client-auth.key --tlsv1.2
% Total% Received % Xferd Average Speed TimeTime Time
Current
Dload Upload Total SpentLeft Speed
100 10918 100 109180 0706 0 0:00:15 0:00:15 --:--:-- 2579
# ll index.html
-rw-r--r-- 1 root root 10918 Jul 1 14:15 index.html
Apache will log this in the error.log file:
[Mon Jul 01 14:15:38.014784 2019] [reqtimeout:info] [pid 1685:tid
140326278772480] [client 10.0.100.215:35108] AH01382: Request body read timeout
That is due to modreqtimeout kicking in.
In the access.log file, we will
[Touch-packages] [Bug 1834494] Re: latest bzip2 reports crc errors incorrectly
I did test the patch suggested and can confirm that it fixes the issue. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to bzip2 in Ubuntu. https://bugs.launchpad.net/bugs/1834494 Title: latest bzip2 reports crc errors incorrectly Status in bzip2: New Status in bzip2 package in Ubuntu: Confirmed Status in bzip2 source package in Xenial: New Status in bzip2 source package in Bionic: New Status in bzip2 source package in Cosmic: New Status in bzip2 source package in Disco: New Status in bzip2 package in Debian: Confirmed Bug description: I just got the bzip2 1.0.6-8.1ubuntu0.1 updates pushed to my machine and am now having problems with some .tbz2 archives. In particular, I can no longer extract this one: https://developer.nvidia.com/embedded/dlc/l4t-jetson-xavier-driver- package-31-1-0 Downloading this and running: bunzip2 -tvv Jetson_Linux_R31.1.0_aarch64.tbz2 ...yields a CRC error. The previous version of bunzip2 does not report any errors with this archive. To manage notifications about this bug go to: https://bugs.launchpad.net/bzip2/+bug/1834494/+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 69724] Re: Mawk does not support Posix character classes in expressions
why indeed -- 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/69724 Title: Mawk does not support Posix character classes in expressions Status in mawk package in Ubuntu: Confirmed Status in mawk package in Debian: Confirmed Bug description: Binary package hint: mawk Mawk does not support Posix character classes, such as [:upper:] and [:lower:], in regular expressions. This makes it more difficult to write portable Awk scripts (since [A-Z] match lower-case characters in Gawk using non-English locales) E.G.: $ echo x | mawk '/[[:lower:]]/' $ echo x | gawk '/[[:lower:]]/' x $ Attached is a patch to fix this issue. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mawk/+bug/69724/+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 1833039] Re: 18.04/Apache2: rejecting client initiated renegotiation due to openssl 1.1.1
** Changed in: apache2 (Ubuntu Cosmic)
Assignee: (unassigned) => Andreas Hasenack (ahasenack)
** Changed in: apache2 (Ubuntu Bionic)
Assignee: (unassigned) => Andreas Hasenack (ahasenack)
** Changed in: apache2 (Ubuntu Bionic)
Importance: Undecided => High
** Changed in: apache2 (Ubuntu Cosmic)
Importance: Undecided => High
** Changed in: apache2 (Ubuntu)
Importance: Undecided => Critical
** Changed in: apache2 (Ubuntu)
Status: Confirmed => Fix Released
** Changed in: apache2 (Ubuntu)
Importance: Critical => High
** Changed in: apache2 (Ubuntu Bionic)
Status: Confirmed => In Progress
** Changed in: apache2 (Ubuntu Cosmic)
Status: Confirmed => In Progress
** Changed in: openssl (Ubuntu)
Status: Incomplete => Invalid
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to openssl in Ubuntu.
https://bugs.launchpad.net/bugs/1833039
Title:
18.04/Apache2: rejecting client initiated renegotiation due to openssl
1.1.1
Status in apache2 package in Ubuntu:
Fix Released
Status in openssl package in Ubuntu:
Invalid
Status in apache2 source package in Bionic:
In Progress
Status in apache2 source package in Cosmic:
In Progress
Bug description:
[Impact]
Under the following conditions, https connections using client cert
authentication will suffer a long delay (about 15s if modreqtimeout is enabled,
more if it is disabled):
* TLSv1.2
* client certificate authentication in use
* a Location, Directory, or other such block defining the client certificate
authentication for that block only, differing from the SSL vhost as a whole
This was triggered by the OpenSSL 1.1.1 SRU and was caused by this
openssl change in SSL_MODE_AUTO_RETRY from disabled to enabled by
default:
https://github.com/openssl/openssl/blob/a4a90a8a3bdcb9336b5c9c15da419e99a87bc6ed/CHANGES#L121-L130
[Test Case]
It helps if you have lxd up and running. Otherwise, a VM or even bare
metal host also works, as long as you stick to the "ubuntu" hostname.
Launch a container for the release you are testing. The command below is for
bionic:
$ lxc launch ubuntu-daily:bionic ubuntu
Enter the container as root:
$ lxc exec ubuntu bash
Verify hostname is "ubuntu":
# hostname
ubuntu
Install apache2:
apt update && apt install apache2
Download the following files from this bug report and place them in
/etc/apache2:
cd /etc/apache2
wget
https://bugs.launchpad.net/ubuntu/+source/apache2/+bug/1833039/+attachment/5274492/+files/cacert.pem
https://bugs.launchpad.net/ubuntu/+source/apache2/+bug/1833039/+attachment/5274493/+files/ubuntu.pem
https://bugs.launchpad.net/ubuntu/+source/apache2/+bug/1833039/+attachment/5274494/+files/ubuntu.key
Adjust permissions of the key file:
chmod 0640 /etc/apache2/ubuntu.key
chgrp www-data /etc/apache2/ubuntu.key
Download the client certificate and key files and place them in /root:
cd /root
wget
https://bugs.launchpad.net/ubuntu/+source/apache2/+bug/1833039/+attachment/5274495/+files/client-auth.pem
https://bugs.launchpad.net/ubuntu/+source/apache2/+bug/1833039/+attachment/5274496/+files/client-auth.key
Create this vhost file (caution, lines may wrap, in particular LogFormat: it
should be one long line):
cat > /etc/apache2/sites-available/cert-auth-test.conf <
LogLevel info ssl:warn
ServerAdmin webmaster@localhost
DocumentRoot /var/www/html
LogFormat "%h %l %u %t \"%r\" %>s %O \"%{Referer}i\"
\"%{User-Agent}i\" protocol=%{SSL_PROTOCOL}x commonName=%{SSL_CLIENT_S_DN_CN}x"
combined-ssl
ErrorLog \${APACHE_LOG_DIR}/error.log
CustomLog \${APACHE_LOG_DIR}/access.log combined-ssl
SSLEngine on
SSLCertificateFile /etc/apache2/ubuntu.pem
SSLCertificateKeyFile /etc/apache2/ubuntu.key
SSLCACertificateFile /etc/apache2/cacert.pem
SSLOptions +StdEnvVars
SSLOptions +StdEnvVars
SSLVerifyClient require
Require ssl-verify-client
EOF
Enable the ssl module and this new vhost we just created:
a2enmod ssl && a2ensite cert-auth-test.conf
Restart apache2:
systemctl restart apache2
If at this stage you try the following command, it will fail like this
because no client certificate was provided:
# curl --output /dev/null https://ubuntu/ --cacert /etc/apache2/cacert.pem
% Total% Received % Xferd Average Speed TimeTime Time
Current
Dload Upload Total SpentLeft Speed
0 00 00 0 0 0 --:--:-- --:--:-- --:--:-- 0
curl: (56) OpenSSL SSL_read: error:14094410:SSL
routines:ssl3_read_bytes:sslv3 alert handshake failure, errno 0
And the apache error log will confirm the reason:
[Touch-packages] [Bug 1829829] Re: Ubuntu CI has been flaky for a week
> it looks like @laney is listed there, which is probably appropriate
(he has admin access to the test systems, while I don't)
My understanding is that @laney can help with the infrastructure where
the tests are run. What usually happens on Ubuntu CI for the most part
has nothing to do with the infrastructure. I'd say it's pretty stable
except that for about a month if I recall correctly it failed to report
the statuses of PRs but it was fixed by @laney in
https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1817344.
Regarding TEST-34 on i386, could you open an issue on GitHub? It could
probably be kept on the list as well until it's fixed.
--
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/1829829
Title:
Ubuntu CI has been flaky for a week
Status in systemd package in Ubuntu:
Confirmed
Bug description:
It was originally reported in
https://github.com/systemd/systemd/pull/12583#issuecomment-492949206 5 days
ago. To judge from the logs VMs can't be rebooted there:
```
Ubuntu 18.04.2 LTS autopkgtest ttyS0
autopkgtest login:
---
--- nova show 91e76a78-d05c-412a-b383-55a26010ae69
(adt-bionic-amd64-systemd-upstream-20190516-051604) --
+--++
| Property | Value
|
+--++
| OS-DCF:diskConfig| MANUAL
|
| OS-EXT-AZ:availability_zone | nova
|
| OS-EXT-SRV-ATTR:host | euler
|
| OS-EXT-SRV-ATTR:hypervisor_hostname | euler.lcy01.scalingstack
|
| OS-EXT-SRV-ATTR:instance_name| instance-003d216a
|
| OS-EXT-STS:power_state | 1
|
| OS-EXT-STS:task_state| -
|
| OS-EXT-STS:vm_state | active
|
| OS-SRV-USG:launched_at | 2019-05-16T07:00:42.00
|
| OS-SRV-USG:terminated_at | -
|
| accessIPv4 |
|
| accessIPv6 |
|
| config_drive |
|
| created | 2019-05-16T07:00:33Z
|
| flavor | autopkgtest
(f878e70e-9991-46e0-ba02-8ea159a71656) |
| hostId |
1722c5f2face86c3fc9f338ae96835924721512372342f664e6941bd
|
| id | 91e76a78-d05c-412a-b383-55a26010ae69
|
| image|
adt/ubuntu-bionic-amd64-server-20190516.img
(d00bf12c-467e-433f-a4f5-15720f13bff1) |
| key_name |
testbed-juju-prod-ues-proposed-migration-machine-11
|
| metadata | {}
|
| name |
adt-bionic-amd64-systemd-upstream-20190516-051604
|
| net_ues_proposed_migration network | 10.42.40.13
|
| os-extended-volumes:volumes_attached | []
|
| progress | 0
|
| security_groups | autopkgtest@lcy01-27.secgroup
|
| status
[Touch-packages] [Bug 1556439] Re: pulseaudio crashed with SIGABRT in pa_sink_input_assert_ref() from pa_sink_input_finish_move() from pa_sink_move_all_finish() from card_set_profile() from pa_card_se
Debdiff for proposed SRU. ** Changed in: pulseaudio (Ubuntu Bionic) Status: In Progress => Fix Committed ** Patch added: "pulseaudio_11.1-1ubuntu7.3.debdiff" https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1556439/+attachment/5274373/+files/pulseaudio_11.1-1ubuntu7.3.debdiff -- 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/1556439 Title: pulseaudio crashed with SIGABRT in pa_sink_input_assert_ref() from pa_sink_input_finish_move() from pa_sink_move_all_finish() from card_set_profile() from pa_card_set_profile Status in PulseAudio: Fix Released Status in pulseaudio package in Ubuntu: Fix Released Status in pulseaudio source package in Bionic: Fix Committed Bug description: [Impact] https://errors.ubuntu.com/problem/a83a007593c81501c4fbb4e9ac0f47e0b3880d17 This is one of the top pulseaudio crashes in Ubuntu 18.04 according to: https://errors.ubuntu.com/?release=Ubuntu%2018.04=pulseaudio=year [Test Case] No manual test case known. Just watch errors.ubuntu.com to check for recurrences. [Regression Potential] Low. The fix is already in PulseAudio 12 so has been used in Ubuntu 18.10 and later for a year so far. [Original Report] Changing between Logitech G933 digital and analog and Logitech G930 digital and analog ProblemType: Crash DistroRelease: Ubuntu 16.04 Package: pulseaudio 1:8.0-0ubuntu2 ProcVersionSignature: Ubuntu 4.4.0-12.28-generic 4.4.4 Uname: Linux 4.4.0-12-generic x86_64 NonfreeKernelModules: nvidia_uvm nvidia_modeset wl nvidia ApportVersion: 2.20-0ubuntu3 Architecture: amd64 CurrentDesktop: Unity Date: Sat Mar 12 17:20:34 2016 EcryptfsInUse: Yes ExecutablePath: /usr/bin/pulseaudio InstallationDate: Installed on 2016-02-22 (19 days ago) InstallationMedia: Ubuntu 15.10 "Wily Werewolf" - Release amd64 (20151021) ProcCmdline: /usr/bin/pulseaudio --start --log-target=syslog ProcEnviron: PATH=(custom, no user) SHELL=/bin/bash LANG=sv_SE.UTF-8 LANGUAGE=sv XDG_RUNTIME_DIR= Signal: 6 SourcePackage: pulseaudio StacktraceTop: pa_sink_input_finish_move () from /usr/lib/x86_64-linux-gnu/pulseaudio/libpulsecore-8.0.so pa_sink_move_all_finish () from /usr/lib/x86_64-linux-gnu/pulseaudio/libpulsecore-8.0.so ?? () from /usr/lib/pulse-8.0/modules/module-alsa-card.so pa_card_set_profile () from /usr/lib/x86_64-linux-gnu/pulseaudio/libpulsecore-8.0.so ?? () from /usr/lib/pulse-8.0/modules/libprotocol-native.so Title: pulseaudio crashed with SIGABRT in pa_sink_input_finish_move() UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo dmi.bios.date: 09/30/2015 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 2001 dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: X99-DELUXE dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: Rev 1.xx 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.:bvr2001:bd09/30/2015:svnASUS:pnAllSeries:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnX99-DELUXE:rvrRev1.xx:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.: dmi.product.name: All Series dmi.product.version: System Version dmi.sys.vendor: ASUS To manage notifications about this bug go to: https://bugs.launchpad.net/pulseaudio/+bug/1556439/+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 1834782] Re: ASUS Zenbook UX433FN: sound stops working after a couple of seconds
> the last working version was linux-hwe-edge 5.0.0-19 and the first broken version is linux-hwe-edge 5.0.0-20. yes, correct. > I'm a little confused because you reported this bug using kernel 4.18.0-25-generic. Was there another regression in the 4.18 series? yes. Audio used to work on both hwe (4.18) and hwe-edge (5.0) versions, and is broken with the latest version on both. For 5.0 I had the backup -19 version left over, so it was the easiest to test. -- 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/1834782 Title: ASUS Zenbook UX433FN: sound stops working after a couple of seconds Status in linux-firmware package in Ubuntu: Incomplete Status in linux-hwe package in Ubuntu: Incomplete Status in linux-hwe-edge package in Ubuntu: Incomplete Status in pulseaudio package in Ubuntu: Invalid Bug description: Issue: whichever sound-related action (sound +/- media keys, spotify song, youtube vid in browser,...) I do, the sound works OK for about 2-3 seconds, and then stops and becomes silent. The interesting thing is that when I stop playing the audio (ie close the browser tab with a song), after a while when I try aain the sound works again. Yet still for just the few secs. Environment: up-to-date Ubuntu 18.04, tried -hwe, hwe-edge kernels. This is a regression, the sound used to work OK on this machine, and nothing significant related to sound has changed since. Thank you for looking into this bug! --- ProblemType: Bug ApportVersion: 2.20.9-0ubuntu7.6 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: mmm 28065 F pulseaudio CurrentDesktop: KDE CurrentDmesg: Error: command ['dmesg'] failed with exit code 1: dmesg: read kernel buffer failed: Operation not permitted Dependencies: DistroRelease: KDE neon 18.04 InstallationDate: Installed on 2012-12-23 (2380 days ago) InstallationMedia: Kubuntu 12.10 "Quantal Quetzal" - Release amd64 (20121017.1) Package: pulseaudio PackageArchitecture: all ProcVersionSignature: Ubuntu 4.18.0-25.26~18.04.1-generic 4.18.20 Tags: bionic wayland-session third-party-packages wayland-session Uname: Linux 4.18.0-25-generic x86_64 UnreportableReason: Toto není oficiální KDE balík. Prosíme odstraňte všechny balíky třetích stran a zkuste to znovu. UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm libvirtd lpadmin netdev plugdev sudo video _MarkForUpload: True dmi.bios.date: 04/24/2019 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: UX433FN.306 dmi.board.asset.tag: ATN12345678901234567 dmi.board.name: UX433FN dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: 1.0 dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: ASUSTeK COMPUTER INC. dmi.chassis.version: 1.0 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrUX433FN.306:bd04/24/2019:svnASUSTeKCOMPUTERINC.:pnZenBookUX433FN_UX433FN:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnUX433FN:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0: dmi.product.family: ZenBook dmi.product.name: ZenBook UX433FN_UX433FN dmi.product.version: 1.0 dmi.sys.vendor: ASUSTeK COMPUTER INC. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-firmware/+bug/1834782/+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 1777094] Re: dnsmasq started too early, not getting all interfaces
*** This bug is a duplicate of bug 1531184 *** https://bugs.launchpad.net/bugs/1531184 Hi Terrence, yeah and while yours is still NetworkManager specific it is still essentially the same as bug 1531184 - making this a dup to have all on one. ** This bug has been marked a duplicate of bug 1531184 [SRU] dnsmasq doesn't start on boot because its interface isn't up yet -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to dnsmasq in Ubuntu. https://bugs.launchpad.net/bugs/1777094 Title: dnsmasq started too early, not getting all interfaces Status in dnsmasq package in Ubuntu: Confirmed Status in netplan.io package in Ubuntu: Expired Bug description: Hi, I'm still struggling with 18.04 and the move from ifupdown to netplan. I am running a local virtual linux bridge as a network for several virtual machines and containers, which is to be serviced with dhcp and dns by dnsmasq. Conforming to latest designs from Ubuntu the bridge is now started by netplan and configured in /etc/netplan/60-vlan0.yaml straightforward. Since there is no ifupdown-scripts anymore, I've configured the default dnsmasq daemon in /etc/dnsmasq.d/vlan0 to offer dhcp for that bridge. This works only when started manually. When booting ubuntu the normal way, the bridge is correctly generated, and dnsmasq is running, but it does *not* offer DNS for the bridge and does not occupy its port 53. But just a manual systemctl restart dnsmasq.service make it run as expected, then everything is fine. So my guess is that my configuration is correct, but dnsmasq simply started to early, i.e. before the bridge is created, and thus does not see the bridge when starting up. There's something wrong in the dependencies of the startup configuration. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: dnsmasq 2.79-1 ProcVersionSignature: Ubuntu 4.15.0-23.25-generic 4.15.18 Uname: Linux 4.15.0-23-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.20.9-0ubuntu7.2 Architecture: amd64 CurrentDesktop: LXDE Date: Fri Jun 15 10:59:43 2018 InstallationDate: Installed on 2018-04-30 (45 days ago) InstallationMedia: Lubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426) PackageArchitecture: all SourcePackage: dnsmasq UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/dnsmasq/+bug/1777094/+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 1833039] Re: 18.04/Apache2: rejecting client initiated renegotiation due to openssl 1.1.1
@Andreas Hasenack: Many thanks - the patches from your PPA worked. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to openssl in Ubuntu. https://bugs.launchpad.net/bugs/1833039 Title: 18.04/Apache2: rejecting client initiated renegotiation due to openssl 1.1.1 Status in apache2 package in Ubuntu: Confirmed Status in openssl package in Ubuntu: Incomplete Status in apache2 source package in Bionic: Confirmed Status in apache2 source package in Cosmic: Confirmed Bug description: I am using Apache2 with client certificate authentication. Since recently (last week) and without any configuration changes, the following errors occur frequently: AH02042: rejecting client initiated renegotiation Client connections are very slow and sometimes it takes more than a minute until a weg page can be opened in the browser. Before installation of the latest security fixes last week, this error did not occur. Could it be related to https://bugs.launchpad.net/ubuntu/+source/apache2/+bug/1803689? System information: Description:Ubuntu 18.04.2 LTS Release:18.04 apache2: Installiert: 2.4.29-1ubuntu4.6 Installationskandidat: 2.4.29-1ubuntu4.6 Versionstabelle: *** 2.4.29-1ubuntu4.6 500 500 http://de.archive.ubuntu.com/ubuntu bionic-updates/main amd64 Packages 500 http://security.ubuntu.com/ubuntu bionic-security/main amd64 Packages 100 /var/lib/dpkg/status 2.4.29-1ubuntu4 500 500 http://de.archive.ubuntu.com/ubuntu bionic/main amd64 Packages openssl: Installiert: 1.1.1-1ubuntu2.1~18.04.2 Installationskandidat: 1.1.1-1ubuntu2.1~18.04.2 Versionstabelle: *** 1.1.1-1ubuntu2.1~18.04.2 500 500 http://de.archive.ubuntu.com/ubuntu bionic-updates/main amd64 Packages 100 /var/lib/dpkg/status 1.1.0g-2ubuntu4.3 500 500 http://security.ubuntu.com/ubuntu bionic-security/main amd64 Packages 1.1.0g-2ubuntu4 500 500 http://de.archive.ubuntu.com/ubuntu bionic/main amd64 Packages To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apache2/+bug/1833039/+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 1556439] Re: pulseaudio crashed with SIGABRT in pa_sink_input_assert_ref() from pa_sink_input_finish_move() from pa_sink_move_all_finish() from card_set_profile() from pa_card_se
** Description changed: [Impact] https://errors.ubuntu.com/problem/a83a007593c81501c4fbb4e9ac0f47e0b3880d17 This is one of the top pulseaudio crashes in Ubuntu 18.04 according to: - https://errors.ubuntu.com/?release=Ubuntu%2018.04=pulseaudio=month + https://errors.ubuntu.com/?release=Ubuntu%2018.04=pulseaudio=year [Test Case] No manual test case known. We just wait and watch errors.ubuntu.com to see where the most crashes are. [Regression Potential] Low. The fix is already in PulseAudio 12 so has been used in Ubuntu 18.10 and later for a year so far. [Original Report] Changing between Logitech G933 digital and analog and Logitech G930 digital and analog ProblemType: Crash DistroRelease: Ubuntu 16.04 Package: pulseaudio 1:8.0-0ubuntu2 ProcVersionSignature: Ubuntu 4.4.0-12.28-generic 4.4.4 Uname: Linux 4.4.0-12-generic x86_64 NonfreeKernelModules: nvidia_uvm nvidia_modeset wl nvidia ApportVersion: 2.20-0ubuntu3 Architecture: amd64 CurrentDesktop: Unity Date: Sat Mar 12 17:20:34 2016 EcryptfsInUse: Yes ExecutablePath: /usr/bin/pulseaudio InstallationDate: Installed on 2016-02-22 (19 days ago) InstallationMedia: Ubuntu 15.10 "Wily Werewolf" - Release amd64 (20151021) ProcCmdline: /usr/bin/pulseaudio --start --log-target=syslog ProcEnviron: PATH=(custom, no user) SHELL=/bin/bash LANG=sv_SE.UTF-8 LANGUAGE=sv XDG_RUNTIME_DIR= Signal: 6 SourcePackage: pulseaudio StacktraceTop: pa_sink_input_finish_move () from /usr/lib/x86_64-linux-gnu/pulseaudio/libpulsecore-8.0.so pa_sink_move_all_finish () from /usr/lib/x86_64-linux-gnu/pulseaudio/libpulsecore-8.0.so ?? () from /usr/lib/pulse-8.0/modules/module-alsa-card.so pa_card_set_profile () from /usr/lib/x86_64-linux-gnu/pulseaudio/libpulsecore-8.0.so ?? () from /usr/lib/pulse-8.0/modules/libprotocol-native.so Title: pulseaudio crashed with SIGABRT in pa_sink_input_finish_move() UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo dmi.bios.date: 09/30/2015 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 2001 dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: X99-DELUXE dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: Rev 1.xx 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.:bvr2001:bd09/30/2015:svnASUS:pnAllSeries:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnX99-DELUXE:rvrRev1.xx:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.: dmi.product.name: All Series dmi.product.version: System Version dmi.sys.vendor: ASUS ** Description changed: [Impact] https://errors.ubuntu.com/problem/a83a007593c81501c4fbb4e9ac0f47e0b3880d17 This is one of the top pulseaudio crashes in Ubuntu 18.04 according to: https://errors.ubuntu.com/?release=Ubuntu%2018.04=pulseaudio=year [Test Case] - No manual test case known. We just wait and watch errors.ubuntu.com to - see where the most crashes are. + No manual test case known. Just watch errors.ubuntu.com to check for + recurrences. [Regression Potential] Low. The fix is already in PulseAudio 12 so has been used in Ubuntu 18.10 and later for a year so far. [Original Report] Changing between Logitech G933 digital and analog and Logitech G930 digital and analog ProblemType: Crash DistroRelease: Ubuntu 16.04 Package: pulseaudio 1:8.0-0ubuntu2 ProcVersionSignature: Ubuntu 4.4.0-12.28-generic 4.4.4 Uname: Linux 4.4.0-12-generic x86_64 NonfreeKernelModules: nvidia_uvm nvidia_modeset wl nvidia ApportVersion: 2.20-0ubuntu3 Architecture: amd64 CurrentDesktop: Unity Date: Sat Mar 12 17:20:34 2016 EcryptfsInUse: Yes ExecutablePath: /usr/bin/pulseaudio InstallationDate: Installed on 2016-02-22 (19 days ago) InstallationMedia: Ubuntu 15.10 "Wily Werewolf" - Release amd64 (20151021) ProcCmdline: /usr/bin/pulseaudio --start --log-target=syslog ProcEnviron: PATH=(custom, no user) SHELL=/bin/bash LANG=sv_SE.UTF-8 LANGUAGE=sv XDG_RUNTIME_DIR= Signal: 6 SourcePackage: pulseaudio StacktraceTop: pa_sink_input_finish_move () from /usr/lib/x86_64-linux-gnu/pulseaudio/libpulsecore-8.0.so pa_sink_move_all_finish () from /usr/lib/x86_64-linux-gnu/pulseaudio/libpulsecore-8.0.so ?? () from /usr/lib/pulse-8.0/modules/module-alsa-card.so pa_card_set_profile () from /usr/lib/x86_64-linux-gnu/pulseaudio/libpulsecore-8.0.so ?? () from /usr/lib/pulse-8.0/modules/libprotocol-native.so Title: pulseaudio crashed with SIGABRT in pa_sink_input_finish_move() UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo dmi.bios.date: 09/30/2015 dmi.bios.vendor: American Megatrends Inc.
[Touch-packages] [Bug 1663528] Re: pulseaudio assert failure: pulseaudio: mixer.c:929: snd_mixer_elem_get_callback_private: Assertion `mixer' failed.
Patch proposed in bug 1556439. ** Changed in: pulseaudio (Ubuntu Bionic) Status: In Progress => Fix Committed ** Description changed: [Impact] https://errors.ubuntu.com/problem/a8bcc8185d5b1da4614bcdcf99daf57011bf9250 https://errors.ubuntu.com/problem/5e10f78db7c4d1d3ab1cd6cd5d0b7cda2299eaad https://errors.ubuntu.com/problem/0f07e226e7db1d0fb140736a956760871e695669 This is one of the top pulseaudio crashes in Ubuntu 18.04 according to: https://errors.ubuntu.com/?release=Ubuntu%2018.04=pulseaudio=year [Test Case] No manual test case known. Just watch errors.ubuntu.com to check for recurrences. [Regression Potential] Low. The fix is already in PulseAudio 12 so has been used in Ubuntu 18.10 and later for a year so far. + + [Other Info] + SRU sponsorship tracked in bug 1556439. [Original Report] Sidenote: Imediatly got that crash after the apt-xapian-index one ( lp:1663524 ); does not know if it can exist a possible relationship between them. Got an other crash, and that time 'sound' is fully lost (pulseaudio not reloaded). Wonder if lp:1662860 can be concerned. ProblemType: Crash DistroRelease: Ubuntu 17.04 Package: pulseaudio 1:10.0-1ubuntu1 ProcVersionSignature: Ubuntu 4.9.0-16.17-generic 4.9.6 Uname: Linux 4.9.0-16-generic x86_64 NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia ApportVersion: 2.20.4-0ubuntu2 Architecture: amd64 AssertionMessage: pulseaudio: mixer.c:929: snd_mixer_elem_get_callback_private: Assertion `mixer' failed. AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: oem4084 F pulseaudio /dev/snd/controlC0: oem4084 F pulseaudio CurrentDesktop: GNOME Date: Fri Feb 10 09:55:45 2017 ExecutablePath: /usr/bin/pulseaudio ProcCmdline: /usr/bin/pulseaudio --start --log-target=syslog ProcEnviron: LANGUAGE=en_GB:en PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_GB.UTF-8 SHELL=/bin/bash Signal: 6 SourcePackage: pulseaudio StacktraceTop: __assert_fail_base (fmt=, assertion=assertion@entry=0x7f92818e7188 "mixer", file=file@entry=0x7f92818e7419 "mixer.c", line=line@entry=929, function=function@entry=0x7f92818e76a0 "snd_mixer_elem_get_callback_private") at assert.c:92 __GI___assert_fail (assertion=0x7f92818e7188 "mixer", file=0x7f92818e7419 "mixer.c", line=929, function=0x7f92818e76a0 "snd_mixer_elem_get_callback_private") at assert.c:101 snd_mixer_elem_get_callback_private () from /usr/lib/x86_64-linux-gnu/libasound.so.2 ?? () from /usr/lib/pulse-10.0/modules/module-alsa-card.so ?? () from /usr/lib/pulse-10.0/modules/module-alsa-card.so Title: pulseaudio assert failure: pulseaudio: mixer.c:929: snd_mixer_elem_get_callback_private: Assertion `mixer' failed. UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom colord dip lpadmin nvidia-persistenced plugdev sambashare sudo users dmi.bios.date: 07/22/2010 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 3002 dmi.board.asset.tag: To Be Filled By O.E.M. dmi.board.name: P5W DH Deluxe dmi.board.vendor: ASUSTeK Computer INC. dmi.board.version: Rev 1.xx dmi.chassis.asset.tag: Asset-1234567890 dmi.chassis.type: 3 dmi.chassis.vendor: Chassis Manufacture dmi.chassis.version: Chassis Version dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr3002:bd07/22/2010:svnASUSTEKCOMPUTERINC:pnP5WDHDeluxe:pvrSystemVersion:rvnASUSTeKComputerINC.:rnP5WDHDeluxe:rvrRev1.xx:cvnChassisManufacture:ct3:cvrChassisVersion: dmi.product.name: P5W DH Deluxe dmi.product.version: System Version dmi.sys.vendor: ASUSTEK COMPUTER INC ** Description changed: [Impact] https://errors.ubuntu.com/problem/a8bcc8185d5b1da4614bcdcf99daf57011bf9250 https://errors.ubuntu.com/problem/5e10f78db7c4d1d3ab1cd6cd5d0b7cda2299eaad https://errors.ubuntu.com/problem/0f07e226e7db1d0fb140736a956760871e695669 This is one of the top pulseaudio crashes in Ubuntu 18.04 according to: https://errors.ubuntu.com/?release=Ubuntu%2018.04=pulseaudio=year [Test Case] No manual test case known. Just watch errors.ubuntu.com to check for recurrences. [Regression Potential] Low. The fix is already in PulseAudio 12 so has been used in Ubuntu 18.10 and later for a year so far. [Other Info] + SRU sponsorship tracked in bug 1556439. [Original Report] Sidenote: Imediatly got that crash after the apt-xapian-index one ( lp:1663524 ); does not know if it can exist a possible relationship between them. Got an other crash, and that time 'sound' is fully lost (pulseaudio not reloaded). Wonder if lp:1662860 can be concerned. ProblemType: Crash DistroRelease: Ubuntu 17.04 Package: pulseaudio 1:10.0-1ubuntu1 ProcVersionSignature: Ubuntu 4.9.0-16.17-generic 4.9.6 Uname: Linux 4.9.0-16-generic x86_64 NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia
[Touch-packages] [Bug 1531184] Re: [SRU] dnsmasq doesn't start on boot because its interface isn't up yet
Added bug 1777094 as a dup which is about the same issue (and essentially the same suggested solution). Also related on askubuntu: https://askubuntu.com/questions/536787/dnsmasq-starting-before-eth0-is-ready-and-therefore-not-binding -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to dnsmasq in Ubuntu. https://bugs.launchpad.net/bugs/1531184 Title: [SRU] dnsmasq doesn't start on boot because its interface isn't up yet Status in One Hundred Papercuts: Confirmed Status in dnsmasq package in Ubuntu: Confirmed Status in dnsmasq package in Debian: New Bug description: [Impact] TBD [Test Case] TBD [Regression Potential] The fix is just configuring the order of service startup, so is unlikely to create any regressions. Things to watch would be service related misbehaviors and general availability of the dnsmasq functionality. [Fix] https://bugs.debian.org/cgi-bin/bugreport.cgi?att=1;bug=774970;filename=774970-network-online.debdiff;msg=22 [Discussion] [Original Report] My dnsmasq instance uses "interface=br-vz0" and the interface br-vz0 is managed manually in /etc/network/interfaces. During boot, dnsmasq is started before br-vz0 is created and this causes dnsmasq to exit: Jan 5 08:56:16 simon-laptop dnsmasq[1008]: dnsmasq: unknown interface br-vz0 Jan 5 08:56:16 simon-laptop dnsmasq[1008]: unknown interface br-vz0 Jan 5 08:56:16 simon-laptop dnsmasq[1008]: FAILED to start up Jan 5 08:56:17 simon-laptop NetworkManager[937]: NetworkManager (version 1.0.4) is starting... ... Jan 5 08:56:18 simon-laptop NetworkManager[937]: interface-parser: parsing file /etc/network/interfaces ... Jan 5 08:56:18 simon-laptop NetworkManager[937]: found bridge ports none for br-vz0 Jan 5 08:56:18 simon-laptop NetworkManager[937]: adding bridge port none to eni_ifaces Jan 5 08:56:18 simon-laptop NetworkManager[937]: management mode: unmanaged ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: dnsmasq 2.75-1 ProcVersionSignature: Ubuntu 4.3.0-5.16-generic 4.3.3 Uname: Linux 4.3.0-5-generic x86_64 ApportVersion: 2.19.3-0ubuntu2 Architecture: amd64 CurrentDesktop: Unity Date: Tue Jan 5 09:53:30 2016 PackageArchitecture: all SourcePackage: dnsmasq UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/hundredpapercuts/+bug/1531184/+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 1834782] Re: ASUS Zenbook UX433FN: sound stops working after a couple of seconds
Hi Daniel, good riddance! Already the previous version of hwe-edge (which I had as auto-backup in /boot) works ok. > an you please try some older (or newer) kernel versions from here: # uname -a Linux mmm-U2442 5.0.0-19-generic #20~18.04.1-Ubuntu SMP Thu Jun 20 12:17:14 UTC 2019 x86_64 x86_64 x86_64 GNU/Linux If I understand this, the 5.0.0-19 -> 5.0.0-20 is only difference in Ubuntu additional patchset, so it should be easier to review the breaking patch (?) Please note I'm having othert trouble with the kernel/microcode, therefore I'm running newest BIOS/FW https://bugs.launchpad.net/ubuntu/+source/intel-microcode/+bug/1829620 Thank you very much for helping me with this bug, -- 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/1834782 Title: ASUS Zenbook UX433FN: sound stops working after a couple of seconds Status in linux-firmware package in Ubuntu: Incomplete Status in linux-hwe package in Ubuntu: Incomplete Status in linux-hwe-edge package in Ubuntu: Incomplete Status in pulseaudio package in Ubuntu: Invalid Bug description: Issue: whichever sound-related action (sound +/- media keys, spotify song, youtube vid in browser,...) I do, the sound works OK for about 2-3 seconds, and then stops and becomes silent. The interesting thing is that when I stop playing the audio (ie close the browser tab with a song), after a while when I try aain the sound works again. Yet still for just the few secs. Environment: up-to-date Ubuntu 18.04, tried -hwe, hwe-edge kernels. This is a regression, the sound used to work OK on this machine, and nothing significant related to sound has changed since. Thank you for looking into this bug! --- ProblemType: Bug ApportVersion: 2.20.9-0ubuntu7.6 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: mmm 28065 F pulseaudio CurrentDesktop: KDE CurrentDmesg: Error: command ['dmesg'] failed with exit code 1: dmesg: read kernel buffer failed: Operation not permitted Dependencies: DistroRelease: KDE neon 18.04 InstallationDate: Installed on 2012-12-23 (2380 days ago) InstallationMedia: Kubuntu 12.10 "Quantal Quetzal" - Release amd64 (20121017.1) Package: pulseaudio PackageArchitecture: all ProcVersionSignature: Ubuntu 4.18.0-25.26~18.04.1-generic 4.18.20 Tags: bionic wayland-session third-party-packages wayland-session Uname: Linux 4.18.0-25-generic x86_64 UnreportableReason: Toto není oficiální KDE balík. Prosíme odstraňte všechny balíky třetích stran a zkuste to znovu. UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm libvirtd lpadmin netdev plugdev sudo video _MarkForUpload: True dmi.bios.date: 04/24/2019 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: UX433FN.306 dmi.board.asset.tag: ATN12345678901234567 dmi.board.name: UX433FN dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: 1.0 dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: ASUSTeK COMPUTER INC. dmi.chassis.version: 1.0 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrUX433FN.306:bd04/24/2019:svnASUSTeKCOMPUTERINC.:pnZenBookUX433FN_UX433FN:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnUX433FN:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0: dmi.product.family: ZenBook dmi.product.name: ZenBook UX433FN_UX433FN dmi.product.version: 1.0 dmi.sys.vendor: ASUSTeK COMPUTER INC. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-firmware/+bug/1834782/+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 1663528] Re: pulseaudio assert failure: pulseaudio: mixer.c:929: snd_mixer_elem_get_callback_private: Assertion `mixer' failed.
** Description changed: [Impact] https://errors.ubuntu.com/problem/a8bcc8185d5b1da4614bcdcf99daf57011bf9250 https://errors.ubuntu.com/problem/5e10f78db7c4d1d3ab1cd6cd5d0b7cda2299eaad https://errors.ubuntu.com/problem/0f07e226e7db1d0fb140736a956760871e695669 This is one of the top pulseaudio crashes in Ubuntu 18.04 according to: - https://errors.ubuntu.com/?release=Ubuntu%2018.04=pulseaudio=month + https://errors.ubuntu.com/?release=Ubuntu%2018.04=pulseaudio=year [Test Case] No manual test case known. We just wait and watch errors.ubuntu.com to see where the most crashes are. [Regression Potential] Low. The fix is already in PulseAudio 12 so has been used in Ubuntu 18.10 and later for a year so far. [Original Report] Sidenote: Imediatly got that crash after the apt-xapian-index one ( lp:1663524 ); does not know if it can exist a possible relationship between them. Got an other crash, and that time 'sound' is fully lost (pulseaudio not reloaded). Wonder if lp:1662860 can be concerned. ProblemType: Crash DistroRelease: Ubuntu 17.04 Package: pulseaudio 1:10.0-1ubuntu1 ProcVersionSignature: Ubuntu 4.9.0-16.17-generic 4.9.6 Uname: Linux 4.9.0-16-generic x86_64 NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia ApportVersion: 2.20.4-0ubuntu2 Architecture: amd64 AssertionMessage: pulseaudio: mixer.c:929: snd_mixer_elem_get_callback_private: Assertion `mixer' failed. AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: oem4084 F pulseaudio /dev/snd/controlC0: oem4084 F pulseaudio CurrentDesktop: GNOME Date: Fri Feb 10 09:55:45 2017 ExecutablePath: /usr/bin/pulseaudio ProcCmdline: /usr/bin/pulseaudio --start --log-target=syslog ProcEnviron: LANGUAGE=en_GB:en PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_GB.UTF-8 SHELL=/bin/bash Signal: 6 SourcePackage: pulseaudio StacktraceTop: __assert_fail_base (fmt=, assertion=assertion@entry=0x7f92818e7188 "mixer", file=file@entry=0x7f92818e7419 "mixer.c", line=line@entry=929, function=function@entry=0x7f92818e76a0 "snd_mixer_elem_get_callback_private") at assert.c:92 __GI___assert_fail (assertion=0x7f92818e7188 "mixer", file=0x7f92818e7419 "mixer.c", line=929, function=0x7f92818e76a0 "snd_mixer_elem_get_callback_private") at assert.c:101 snd_mixer_elem_get_callback_private () from /usr/lib/x86_64-linux-gnu/libasound.so.2 ?? () from /usr/lib/pulse-10.0/modules/module-alsa-card.so ?? () from /usr/lib/pulse-10.0/modules/module-alsa-card.so Title: pulseaudio assert failure: pulseaudio: mixer.c:929: snd_mixer_elem_get_callback_private: Assertion `mixer' failed. UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom colord dip lpadmin nvidia-persistenced plugdev sambashare sudo users dmi.bios.date: 07/22/2010 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 3002 dmi.board.asset.tag: To Be Filled By O.E.M. dmi.board.name: P5W DH Deluxe dmi.board.vendor: ASUSTeK Computer INC. dmi.board.version: Rev 1.xx dmi.chassis.asset.tag: Asset-1234567890 dmi.chassis.type: 3 dmi.chassis.vendor: Chassis Manufacture dmi.chassis.version: Chassis Version dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr3002:bd07/22/2010:svnASUSTEKCOMPUTERINC:pnP5WDHDeluxe:pvrSystemVersion:rvnASUSTeKComputerINC.:rnP5WDHDeluxe:rvrRev1.xx:cvnChassisManufacture:ct3:cvrChassisVersion: dmi.product.name: P5W DH Deluxe dmi.product.version: System Version dmi.sys.vendor: ASUSTEK COMPUTER INC ** Description changed: [Impact] https://errors.ubuntu.com/problem/a8bcc8185d5b1da4614bcdcf99daf57011bf9250 https://errors.ubuntu.com/problem/5e10f78db7c4d1d3ab1cd6cd5d0b7cda2299eaad https://errors.ubuntu.com/problem/0f07e226e7db1d0fb140736a956760871e695669 This is one of the top pulseaudio crashes in Ubuntu 18.04 according to: https://errors.ubuntu.com/?release=Ubuntu%2018.04=pulseaudio=year [Test Case] - No manual test case known. We just wait and watch errors.ubuntu.com to - see where the most crashes are. + No manual test case known. Just watch errors.ubuntu.com to check for + recurrences. [Regression Potential] Low. The fix is already in PulseAudio 12 so has been used in Ubuntu 18.10 and later for a year so far. [Original Report] Sidenote: Imediatly got that crash after the apt-xapian-index one ( lp:1663524 ); does not know if it can exist a possible relationship between them. Got an other crash, and that time 'sound' is fully lost (pulseaudio not reloaded). Wonder if lp:1662860 can be concerned. ProblemType: Crash DistroRelease: Ubuntu 17.04 Package: pulseaudio 1:10.0-1ubuntu1 ProcVersionSignature: Ubuntu 4.9.0-16.17-generic 4.9.6 Uname: Linux 4.9.0-16-generic x86_64 NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia ApportVersion: 2.20.4-0ubuntu2
[Touch-packages] [Bug 1834782] Re: ASUS Zenbook UX433FN: sound stops working after a couple of seconds
Thanks. It sounds like you are saying that the last working version was linux- hwe-edge 5.0.0-19 and the first broken version is linux-hwe-edge 5.0.0-20. Is that right? I'm a little confused because you reported this bug using kernel 4.18.0-25-generic. Was there another regression in the 4.18 series? ** Tags added: regression-update -- 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/1834782 Title: ASUS Zenbook UX433FN: sound stops working after a couple of seconds Status in linux-firmware package in Ubuntu: Incomplete Status in linux-hwe package in Ubuntu: Incomplete Status in linux-hwe-edge package in Ubuntu: Incomplete Status in pulseaudio package in Ubuntu: Invalid Bug description: Issue: whichever sound-related action (sound +/- media keys, spotify song, youtube vid in browser,...) I do, the sound works OK for about 2-3 seconds, and then stops and becomes silent. The interesting thing is that when I stop playing the audio (ie close the browser tab with a song), after a while when I try aain the sound works again. Yet still for just the few secs. Environment: up-to-date Ubuntu 18.04, tried -hwe, hwe-edge kernels. This is a regression, the sound used to work OK on this machine, and nothing significant related to sound has changed since. Thank you for looking into this bug! --- ProblemType: Bug ApportVersion: 2.20.9-0ubuntu7.6 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: mmm 28065 F pulseaudio CurrentDesktop: KDE CurrentDmesg: Error: command ['dmesg'] failed with exit code 1: dmesg: read kernel buffer failed: Operation not permitted Dependencies: DistroRelease: KDE neon 18.04 InstallationDate: Installed on 2012-12-23 (2380 days ago) InstallationMedia: Kubuntu 12.10 "Quantal Quetzal" - Release amd64 (20121017.1) Package: pulseaudio PackageArchitecture: all ProcVersionSignature: Ubuntu 4.18.0-25.26~18.04.1-generic 4.18.20 Tags: bionic wayland-session third-party-packages wayland-session Uname: Linux 4.18.0-25-generic x86_64 UnreportableReason: Toto není oficiální KDE balík. Prosíme odstraňte všechny balíky třetích stran a zkuste to znovu. UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm libvirtd lpadmin netdev plugdev sudo video _MarkForUpload: True dmi.bios.date: 04/24/2019 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: UX433FN.306 dmi.board.asset.tag: ATN12345678901234567 dmi.board.name: UX433FN dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: 1.0 dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: ASUSTeK COMPUTER INC. dmi.chassis.version: 1.0 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrUX433FN.306:bd04/24/2019:svnASUSTeKCOMPUTERINC.:pnZenBookUX433FN_UX433FN:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnUX433FN:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0: dmi.product.family: ZenBook dmi.product.name: ZenBook UX433FN_UX433FN dmi.product.version: 1.0 dmi.sys.vendor: ASUSTeK COMPUTER INC. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-firmware/+bug/1834782/+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 1690026] Re: pulseaudio crashed with SIGABRT in pa_sconv_s16le_from_f32ne_sse2() from convert_to_work_format() from pa_resampler_run() from pa_sink_input_peek() from fill_mix_inf
** Tags removed: artful kylin-15.04 vivid wily yakkety zesty ** Tags added: cosmic disco -- 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/1690026 Title: pulseaudio crashed with SIGABRT in pa_sconv_s16le_from_f32ne_sse2() from convert_to_work_format() from pa_resampler_run() from pa_sink_input_peek() from fill_mix_info() Status in pulseaudio package in Ubuntu: Confirmed Bug description: The Ubuntu Error Tracker has been receiving reports about a problem regarding pulseaudio. This problem was most recently seen with package version 1:10.0-1ubuntu2, the problem page at https://errors.ubuntu.com/problem/09eaa7a762edd70e8a3d904cb32f366b3c3211a1 contains more details, including versions of packages affected, stacktrace or traceback, and individual crash reports. If you do not have access to the Ubuntu Error Tracker you can request it at http://forms.canonical.com/reports/. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1690026/+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
