[Touch-packages] [Bug 1832651] Re: jackdbus fails to start: cannot allocate memory
I am also affected by this bug as it seems. I am also unable to start jackd2: Thu Jul 4 08:17:50 2019: JACK server starting in realtime mode with priority 99 Thu Jul 4 08:17:50 2019: self-connect-mode is "Don't restrict self connect requests" Thu Jul 4 08:17:50 2019: ERROR: Cannot lock down 82280346 byte memory area (Cannot allocate memory) My systemd is: hcw@nvidion:~$ dpkg -l systemd +++-==-==--= ii systemd240-6ubuntu5.1 amd64system and service manager So is there a workaround / upgrade path? I dont want do wait 4 months before i can start podcasting. 8-< Kind regards Hauke -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to jackd2 in Ubuntu. https://bugs.launchpad.net/bugs/1832651 Title: jackdbus fails to start: cannot allocate memory Status in systemd: Fix Released Status in jackd2 package in Ubuntu: Invalid Status in systemd package in Ubuntu: Confirmed Status in jackd2 source package in Eoan: Invalid Status in systemd source package in Eoan: Confirmed Bug description: The `.log/jack/jackdbus.log` shows the following after trying to start/restart jack using "Ubuntu Studio Controls" (also tried using `jack_control start`): ERROR: Cannot lock down 82280346 byte memory area (Cannot allocate memory) This is a fresh install of Ubuntu Studio 19.04, installed via USB. The first thing I did after installing was check to see if jack was running, but unfortunately it's not working. The error would seem to indicate that I'm not in the `audio` group, however checking `groups` shows that I am in the audio group. ProblemType: Bug DistroRelease: Ubuntu 19.04 Package: jackd2 1.9.12~dfsg-2build1 ProcVersionSignature: Ubuntu 5.0.0-13.14-lowlatency 5.0.6 Uname: Linux 5.0.0-13-lowlatency x86_64 ApportVersion: 2.20.10-0ubuntu27 Architecture: amd64 CurrentDesktop: GNOME Date: Wed Jun 12 18:13:25 2019 InstallationDate: Installed on 2019-06-12 (0 days ago) InstallationMedia: Ubuntu-Studio 19.04 "Disco Dingo" - Release amd64 (20190416) ProcEnviron: TERM=xterm PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.utf8 SHELL=/bin/bash SourcePackage: jackd2 UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/systemd/+bug/1832651/+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 1759950]
I assume that /xfce4-power-manager/logind-handle-lid-switch needs to be set to 'false'. $ xfconf-query -c xfce4-power-manager -p /xfce4-power-manager/logind- handle-lid-switch -s false -- 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/1759950 Title: Lid-close suspend: blank screen when switching to user session Status in Light-Locker: New Status in Xfce4 Power Manager: Confirmed Status in light-locker package in Ubuntu: Incomplete Status in systemd package in Ubuntu: New Status in xfce4-power-manager package in Ubuntu: Confirmed Status in xfce4-settings package in Ubuntu: New Status in xubuntu-default-settings package in Ubuntu: New Bug description: I'm currently testing Xubuntu 18.04 after a do-release-upgrade from 16.04. I discovered a very weird issue. When doing S3 sleep via closing the lid, on resume the lock screen appears, I authenticate, but as soon as it switches to the user session the screen goes blank - not even a backlight. Switching to other ttys works and they display correctly but the GUI user session remains blank. If the system is manually suspended (not using the lid), then resumed either by opening the lid or pressing the power button, the GUI user session is fine. I narrowed it down to xfce4-power-manager and discovered disabling the lock-screen cured the issue. I cloned the repository and reviewed commits between 1.7 and 1.8. Fortunately there aren't many. Looking at 6365683 "Proper exit status for light-locker-command" I suspected the change in the SetActive return value, and reverted it. After a build/install cycle I've found the system now behaves correctly so I think the change should be reverted. I've created an issue upstream for this at https://github.com/the-cavalry/light-locker/issues/108 To manage notifications about this bug go to: https://bugs.launchpad.net/light-locker/+bug/1759950/+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 1831498] Re: radeonsi: GTK elements become invisible in some applications (GIMP, LibreOffice)
and disco still works on my hardware ** Tags removed: verification-needed verification-needed-disco ** Tags added: verification-done verification-done-disco -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to mesa in Ubuntu. https://bugs.launchpad.net/bugs/1831498 Title: radeonsi: GTK elements become invisible in some applications (GIMP, LibreOffice) Status in mesa package in Ubuntu: Fix Released Status in mesa source package in Bionic: Fix Released Status in mesa source package in Disco: Fix Committed Bug description: [impact] imported from https://bugs.freedesktop.org/show_bug.cgi?id=110355 : "I am currently experiencing some issues with GTK elements (GtkMenuItem, GtkMenu) becoming invisible with GIMP and LibreOffice. I am currently using radeonsi+glamor and I'm on Arch Linux (x86_64). My hardware is a Ryzen 5 2400G APU with vega graphics." [test case] test that GIMP/Libreoffice work fine on AMD Vega/Raven [regression potential] the fix/workaround is already in mesa 19.0.4, shouldn't regress anything To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mesa/+bug/1831498/+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 1814611] Re: ubuntu-bug never (any longer) opens browser window
A quick fix could be to document at https://help.ubuntu.com/community/ReportingBugs that the error reporting must be switch on first. On top of that, ubuntu-bug could output a warning message that the error reporting must be switched on first (and how/where this can be done). -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to apport in Ubuntu. https://bugs.launchpad.net/bugs/1814611 Title: ubuntu-bug never (any longer) opens browser window Status in apport package in Ubuntu: Confirmed Bug description: Ubuntu 18.04.1 LTS, X11 gnome session. For some reason ubuntu-bug no longer opens a browser window, so it is not possible to enter useful bug detauls, or even know the bug number. After prompting whether or not to Send the report, clicking "Send" just closes appport and nothing else ever happens. The exit status of "ubuntu-bug" is zero. This worked fine before, but it has been many months since I tried to submit a bug. strace shows many stat calls on plausible browser paths, including the one that is correct (/usr/bin/firefox, which returned a successful stat call). I'll attach the trace output from strace -f -o /tmp/strace.log ubuntu-bug apport To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apport/+bug/1814611/+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 1833793] Re: Updating to 19.04 audio keeps clicking when nothing is playing audio
Need you to collect some logs, then let us see if it can be fixed through kernel driver. This bug is missing log files that will aid in diagnosing the problem. While running an Ubuntu kernel (not a mainline or third-party kernel) please enter the following command in a terminal window: apport-collect 1833793 and then change the status of the bug to 'Confirmed'. If, due to the nature of the issue you have encountered, you are unable to run this command, please add a comment stating that fact and change the bug status to 'Confirmed'. This change has been made by an automated script, maintained by the Ubuntu Kernel Team. ** Package changed: alsa-driver (Ubuntu) => linux (Ubuntu) -- 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 linux 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/linux/+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 1814611] Re: ubuntu-bug never (any longer) opens browser window
For this to work, I had to enable the error reporting switch in system settings/privacy protection. With error reporting enabled, the browser window opened. This is not a bug, but I'm not very happy with the behaviour: - Having error reporting switched off, I should be able to enforce it via CLI. There should be a corresponding parameter like --ignore-reporting-disabled. (OPT-IN) - OR: Ignoring the disabled reporting should be the default when executing ubuntu-bug manually. (OPT-OUT). If ubuntu-bug was _not_ started manually might require another parameter like --check-reporting-enabled. Unwanted behaviour is: - I have to switch error reporting on (plus, I have to know this by myself!) - ... do my stuff with ubuntu-bug - Switch error reporting off again -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to apport in Ubuntu. https://bugs.launchpad.net/bugs/1814611 Title: ubuntu-bug never (any longer) opens browser window Status in apport package in Ubuntu: Confirmed Bug description: Ubuntu 18.04.1 LTS, X11 gnome session. For some reason ubuntu-bug no longer opens a browser window, so it is not possible to enter useful bug detauls, or even know the bug number. After prompting whether or not to Send the report, clicking "Send" just closes appport and nothing else ever happens. The exit status of "ubuntu-bug" is zero. This worked fine before, but it has been many months since I tried to submit a bug. strace shows many stat calls on plausible browser paths, including the one that is correct (/usr/bin/firefox, which returned a successful stat call). I'll attach the trace output from strace -f -o /tmp/strace.log ubuntu-bug apport To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apport/+bug/1814611/+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 1814611] Re: ubuntu-bug never (any longer) opens browser window
Documentation says (after having pressed the "send" button): "Apport will then upload the problem information to Launchpad, and a new browser window will then open to inform you that the bug report is being processed." https://help.ubuntu.com/community/ReportingBugs -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to apport in Ubuntu. https://bugs.launchpad.net/bugs/1814611 Title: ubuntu-bug never (any longer) opens browser window Status in apport package in Ubuntu: Confirmed Bug description: Ubuntu 18.04.1 LTS, X11 gnome session. For some reason ubuntu-bug no longer opens a browser window, so it is not possible to enter useful bug detauls, or even know the bug number. After prompting whether or not to Send the report, clicking "Send" just closes appport and nothing else ever happens. The exit status of "ubuntu-bug" is zero. This worked fine before, but it has been many months since I tried to submit a bug. strace shows many stat calls on plausible browser paths, including the one that is correct (/usr/bin/firefox, which returned a successful stat call). I'll attach the trace output from strace -f -o /tmp/strace.log ubuntu-bug apport To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apport/+bug/1814611/+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 1814611] Re: ubuntu-bug never (any longer) opens browser window
I'm using ubuntu 18.04 with all updates installed. When I type ubuntu-bug gnome-applets then it does not open the browser window when I click on the "send" button. When i type xdg-open http://bugs.launchpad.net then the corresponding page opens perfectly fine in Firefox 67.0.4. This is pretty much consistent with the previous description. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to apport in Ubuntu. https://bugs.launchpad.net/bugs/1814611 Title: ubuntu-bug never (any longer) opens browser window Status in apport package in Ubuntu: Confirmed Bug description: Ubuntu 18.04.1 LTS, X11 gnome session. For some reason ubuntu-bug no longer opens a browser window, so it is not possible to enter useful bug detauls, or even know the bug number. After prompting whether or not to Send the report, clicking "Send" just closes appport and nothing else ever happens. The exit status of "ubuntu-bug" is zero. This worked fine before, but it has been many months since I tried to submit a bug. strace shows many stat calls on plausible browser paths, including the one that is correct (/usr/bin/firefox, which returned a successful stat call). I'll attach the trace output from strace -f -o /tmp/strace.log ubuntu-bug apport To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apport/+bug/1814611/+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 1814611] Re: ubuntu-bug never (any longer) opens browser window
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: apport (Ubuntu) Status: New => Confirmed -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to apport in Ubuntu. https://bugs.launchpad.net/bugs/1814611 Title: ubuntu-bug never (any longer) opens browser window Status in apport package in Ubuntu: Confirmed Bug description: Ubuntu 18.04.1 LTS, X11 gnome session. For some reason ubuntu-bug no longer opens a browser window, so it is not possible to enter useful bug detauls, or even know the bug number. After prompting whether or not to Send the report, clicking "Send" just closes appport and nothing else ever happens. The exit status of "ubuntu-bug" is zero. This worked fine before, but it has been many months since I tried to submit a bug. strace shows many stat calls on plausible browser paths, including the one that is correct (/usr/bin/firefox, which returned a successful stat call). I'll attach the trace output from strace -f -o /tmp/strace.log ubuntu-bug apport To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apport/+bug/1814611/+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 1833793] Re: Updating to 19.04 audio keeps clicking when nothing is playing audio
@hui.wang Your suggestion worked and you saved my sanity. Thank you so much. Could Ubuntu developers please sort out the power saving, so that the sound card actually shuts down instead of continuous clicking (reinitialization?), just for the sake of others on this chipset. -- 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 1834994] Re: rsync: --xattrs is extremely slow
** Tags added: patch -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to rsync in Ubuntu. https://bugs.launchpad.net/bugs/1834994 Title: rsync: --xattrs is extremely slow Status in rsync package in Ubuntu: New Bug description: Ubuntu 16.04 LTS repositories contain only rsync version 3.1.1: $ apt policy rsync rsync: Installed: 3.1.1-3ubuntu1.2 Candidate: 3.1.1-3ubuntu1.2 Version table: *** 3.1.1-3ubuntu1.2 500 500 http://fi.archive.ubuntu.com/ubuntu xenial-updates/main amd64 Packages 500 http://security.ubuntu.com/ubuntu xenial-security/main amd64 Packages 100 /var/lib/dpkg/status 3.1.1-3ubuntu1 500 500 http://fi.archive.ubuntu.com/ubuntu xenial/main amd64 Packages However, this version has a bug where flag --xattrs causes very very high CPU usage if source contains lots of unique extended attributes. I'm trying to sync 13 TB (roughly 6.5 M files) with extended attributes and this bug seems to make this slower and slower as the time goes by. The system has been copying the stuff for three weeks (!) now. It's getting slower every day but still seems to make progress so I try to run it to completion. First couple of terabytes suggested that this sync operation should have taken around 4 days. The source directory is used by glusterfs which creates checksums as extended attributes and practically every file has different checksum. Please, update rsync package on Ubuntu 16.04 to 3.1.2-2 or later. See also: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=799143 ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: rsync 3.1.1-3ubuntu1.2 ProcVersionSignature: Ubuntu 4.15.0-51.55~16.04.1-lowlatency 4.15.18 Uname: Linux 4.15.0-51-lowlatency x86_64 NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia ApportVersion: 2.20.1-0ubuntu2.18 Architecture: amd64 CurrentDesktop: MATE Date: Tue Jul 2 09:07:49 2019 InstallationDate: Installed on 2015-02-23 (1589 days ago) InstallationMedia: Ubuntu 14.04.2 LTS "Trusty Tahr" - Release amd64 (20150218.1) SourcePackage: rsync UpgradeStatus: Upgraded to xenial on 2016-06-10 (1116 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/rsync/+bug/1834994/+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 1835181] Re: OpenLDAP LDAP_OPT_X_TLS_REQUIRE_CERT handling differences between ldaps:// and ldap:// with STARTTLS
** Information type changed from Private Security to Public -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to openldap in Ubuntu. https://bugs.launchpad.net/bugs/1835181 Title: OpenLDAP LDAP_OPT_X_TLS_REQUIRE_CERT handling differences between ldaps:// and ldap:// with STARTTLS Status in openldap package in Ubuntu: New Bug description: This is the same bug as https://bugs.launchpad.net/ubuntu/+source/openldap/+bug/1547927 which has been closed. Tested and confirmed present with vivid, wily, xenial and bionic Also logged with openldap as http://www.openldap.org/its/index.cgi/Incoming?id=8374 however I think that this is a packaging issue caused by using GNUTLS rather than OpenSSL. Important: to replicate the issue you need to connect to an LDAP server which presents a certificate with a CN that DOES NOT MATCH the connection URI passed to the OpenLDAP client. In practice, this is simple enough to achieve by using the IP address of a server rather than the FQDN. The core of the issue is that the handling of the LDAP_OPT_X_TLS_REQUIRE_CERT option appears to be different between servers accessed via ldaps:// and ldap:// (plus STARTTLS) URIs. When accessing server with an invalid certificate, the results are: ldaps:// never OK hard Error: can't contact LDAP server demand Error: can't contact LDAP server allow OK tryError: can't contact LDAP server ldap:// plus explicit ldap_start_tls_s() never OK hard OK demand OK allow OK tryOK Based on all the documentation, the results should be the same between approaches. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/openldap/+bug/1835181/+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 1835135] Re: FIPS OpenSSL crashes Python2 hashlib
Like python3, python2 should check the return value of EVP_DigestInit. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to python2.7 in Ubuntu. https://bugs.launchpad.net/bugs/1835135 Title: FIPS OpenSSL crashes Python2 hashlib Status in python2.7 package in Ubuntu: Triaged Bug description: If Ubuntu/Canonical's FIPS-compliant OpenSSL is initialized with SSL_library_init, then Python2's hashlib bindings for MD5 can trigger a SIGSEGV via a NULL pointer dereference (if calling the .update method) or a SIGABRT (if passing input to the constructor or passing no input and invoking the .final method). This happens if, for example, PyOpenSSL is imported before hashlib. Canonical's FIPS patches for OpenSSL introduce some odd behavior that arguably should be revisited, but the (TL;DR) core bug is that Python2 hashlib doesn't properly check the return value of EVP_DigestInit, preventing hashlib from falling back to it's internal MD5 implementation and instead setting things up for use of the MD5 context to trigger SIGSEGV or SIGABRT. Python3 correctly checks the return value, so the fix is to backport the relevant code into Python2 (see python2.7-2.7.12/Modules/_hashopenssl.c). See attached good.py and bad.py files which exhibit the import order- dependent crashing issue. See attached fips-md5-python-init-bug.c which shows the FIPS OpenSSL behaviors that conditionally tickle the Python2 bug. The C file also contains a much more detailed description of the Python2 bug and other behavior which I'd rather not repeat here. I discovered this bug investigating an issue with the third-party apt- boto-s3 package. See https://github.com/boto/boto3/issues/2021 Note that this bug effects Splunk, Inc, which has a corporate Ubuntu Advantage license. My login account is attached to a different, single-seat license. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/python2.7/+bug/1835135/+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 1835135] Re: FIPS OpenSSL crashes Python2 hashlib
The assessment is accurate. FIPS 140-2 does not allow MD5 except for use in PRF. Thus the OpenSSL_add_all_digests in fips openssl does not include MD5. However, SSL_library_init() does include MD5 but only for use in calculating the PRF. Notice in tls1_P_hash() in ssl/t1_enc.c the flag, EVP_MD_CTX_FLAG_NON_FIPS_ALLOW, is set in the context to permit this use of MD5. Apps wishing to calculate their own PRF can do the same. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to python2.7 in Ubuntu. https://bugs.launchpad.net/bugs/1835135 Title: FIPS OpenSSL crashes Python2 hashlib Status in python2.7 package in Ubuntu: Triaged Bug description: If Ubuntu/Canonical's FIPS-compliant OpenSSL is initialized with SSL_library_init, then Python2's hashlib bindings for MD5 can trigger a SIGSEGV via a NULL pointer dereference (if calling the .update method) or a SIGABRT (if passing input to the constructor or passing no input and invoking the .final method). This happens if, for example, PyOpenSSL is imported before hashlib. Canonical's FIPS patches for OpenSSL introduce some odd behavior that arguably should be revisited, but the (TL;DR) core bug is that Python2 hashlib doesn't properly check the return value of EVP_DigestInit, preventing hashlib from falling back to it's internal MD5 implementation and instead setting things up for use of the MD5 context to trigger SIGSEGV or SIGABRT. Python3 correctly checks the return value, so the fix is to backport the relevant code into Python2 (see python2.7-2.7.12/Modules/_hashopenssl.c). See attached good.py and bad.py files which exhibit the import order- dependent crashing issue. See attached fips-md5-python-init-bug.c which shows the FIPS OpenSSL behaviors that conditionally tickle the Python2 bug. The C file also contains a much more detailed description of the Python2 bug and other behavior which I'd rather not repeat here. I discovered this bug investigating an issue with the third-party apt- boto-s3 package. See https://github.com/boto/boto3/issues/2021 Note that this bug effects Splunk, Inc, which has a corporate Ubuntu Advantage license. My login account is attached to a different, single-seat license. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/python2.7/+bug/1835135/+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 1835135] Re: FIPS OpenSSL crashes Python2 hashlib
Investigating -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to python2.7 in Ubuntu. https://bugs.launchpad.net/bugs/1835135 Title: FIPS OpenSSL crashes Python2 hashlib Status in python2.7 package in Ubuntu: Triaged Bug description: If Ubuntu/Canonical's FIPS-compliant OpenSSL is initialized with SSL_library_init, then Python2's hashlib bindings for MD5 can trigger a SIGSEGV via a NULL pointer dereference (if calling the .update method) or a SIGABRT (if passing input to the constructor or passing no input and invoking the .final method). This happens if, for example, PyOpenSSL is imported before hashlib. Canonical's FIPS patches for OpenSSL introduce some odd behavior that arguably should be revisited, but the (TL;DR) core bug is that Python2 hashlib doesn't properly check the return value of EVP_DigestInit, preventing hashlib from falling back to it's internal MD5 implementation and instead setting things up for use of the MD5 context to trigger SIGSEGV or SIGABRT. Python3 correctly checks the return value, so the fix is to backport the relevant code into Python2 (see python2.7-2.7.12/Modules/_hashopenssl.c). See attached good.py and bad.py files which exhibit the import order- dependent crashing issue. See attached fips-md5-python-init-bug.c which shows the FIPS OpenSSL behaviors that conditionally tickle the Python2 bug. The C file also contains a much more detailed description of the Python2 bug and other behavior which I'd rather not repeat here. I discovered this bug investigating an issue with the third-party apt- boto-s3 package. See https://github.com/boto/boto3/issues/2021 Note that this bug effects Splunk, Inc, which has a corporate Ubuntu Advantage license. My login account is attached to a different, single-seat license. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/python2.7/+bug/1835135/+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 1834994] Re: rsync: --xattrs is extremely slow
This issue was fixed in Debian with the attached patch from upstream. SRU process prohibits version jumps so would reject directly updating the rsync package on Ubuntu 16.04 to 3.2.2-2. However, if you can define a test case to reliably reproduce the bug, then it may be possible to get the specific patch accepted. Would you be willing to help draft a set of steps to reproduce the bug - preferably something that can be performed within a few minutes or an hour, as opposed to a few weeks (else it'll be too hard for folks to test)? You can see other steps required for filing an SRU at https://wiki.ubuntu.com/StableReleaseUpdates. Anything you can do towards making this bug report fulfill those requirements will make it more likely for this to get attention. One of the potential problems in this case is that the patch is rather large so may be harder to review. SRU's tend to go faster when the patch is just a few lines. ** Patch added: "speedup-xattrs.diff" https://bugs.launchpad.net/ubuntu/+source/rsync/+bug/1834994/+attachment/5274955/+files/speedup-xattrs.diff -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to rsync in Ubuntu. https://bugs.launchpad.net/bugs/1834994 Title: rsync: --xattrs is extremely slow Status in rsync package in Ubuntu: New Bug description: Ubuntu 16.04 LTS repositories contain only rsync version 3.1.1: $ apt policy rsync rsync: Installed: 3.1.1-3ubuntu1.2 Candidate: 3.1.1-3ubuntu1.2 Version table: *** 3.1.1-3ubuntu1.2 500 500 http://fi.archive.ubuntu.com/ubuntu xenial-updates/main amd64 Packages 500 http://security.ubuntu.com/ubuntu xenial-security/main amd64 Packages 100 /var/lib/dpkg/status 3.1.1-3ubuntu1 500 500 http://fi.archive.ubuntu.com/ubuntu xenial/main amd64 Packages However, this version has a bug where flag --xattrs causes very very high CPU usage if source contains lots of unique extended attributes. I'm trying to sync 13 TB (roughly 6.5 M files) with extended attributes and this bug seems to make this slower and slower as the time goes by. The system has been copying the stuff for three weeks (!) now. It's getting slower every day but still seems to make progress so I try to run it to completion. First couple of terabytes suggested that this sync operation should have taken around 4 days. The source directory is used by glusterfs which creates checksums as extended attributes and practically every file has different checksum. Please, update rsync package on Ubuntu 16.04 to 3.1.2-2 or later. See also: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=799143 ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: rsync 3.1.1-3ubuntu1.2 ProcVersionSignature: Ubuntu 4.15.0-51.55~16.04.1-lowlatency 4.15.18 Uname: Linux 4.15.0-51-lowlatency x86_64 NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia ApportVersion: 2.20.1-0ubuntu2.18 Architecture: amd64 CurrentDesktop: MATE Date: Tue Jul 2 09:07:49 2019 InstallationDate: Installed on 2015-02-23 (1589 days ago) InstallationMedia: Ubuntu 14.04.2 LTS "Trusty Tahr" - Release amd64 (20150218.1) SourcePackage: rsync UpgradeStatus: Upgraded to xenial on 2016-06-10 (1116 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/rsync/+bug/1834994/+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 1835315] [NEW] Vulkan funcionality broken when mesa is compiled with LLVM 8 in some programs
Public bug reported: Ubuntu version: 18.04.2 LTS Mesa version: 19.0.2 Mesa-vulkan-driver version: 19.0.2, POLARIS10, DRM 3.27.0, 5.0.0-20-generic, LLVM 8.0.0) Video card: AMD RX 580 8GB, There is an issue when the Vulkan mesa RADV drivers are compiled with LLVM 8, due to an LLVM 8 bug, resulting in no visual output in some programs using the RADV Vulkan backend Upgrading to a mesa build compiled with LLVM 9, or reverting back to the bionic version from bionic-updates (which uses LLVM 6) fixes the problem. Using the AMDVLK vulkan driver workarounds the problem too. The program I have personally tested is RPCS3 I could put additional info about the LLVM bug but at this moment I do not have the upstream reference ** Affects: mesa (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to mesa in Ubuntu. https://bugs.launchpad.net/bugs/1835315 Title: Vulkan funcionality broken when mesa is compiled with LLVM 8 in some programs Status in mesa package in Ubuntu: New Bug description: Ubuntu version: 18.04.2 LTS Mesa version: 19.0.2 Mesa-vulkan-driver version: 19.0.2, POLARIS10, DRM 3.27.0, 5.0.0-20-generic, LLVM 8.0.0) Video card: AMD RX 580 8GB, There is an issue when the Vulkan mesa RADV drivers are compiled with LLVM 8, due to an LLVM 8 bug, resulting in no visual output in some programs using the RADV Vulkan backend Upgrading to a mesa build compiled with LLVM 9, or reverting back to the bionic version from bionic-updates (which uses LLVM 6) fixes the problem. Using the AMDVLK vulkan driver workarounds the problem too. The program I have personally tested is RPCS3 I could put additional info about the LLVM bug but at this moment I do not have the upstream reference To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mesa/+bug/1835315/+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 1835257] Re: update tzdata package to 2019b
Brazil will become a critical in November this year due DST change. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to tzdata in Ubuntu. https://bugs.launchpad.net/bugs/1835257 Title: update tzdata package to 2019b Status in tzdata package in Ubuntu: New Bug description: Update tzdata package to 2019b. https://mm.icann.org/pipermail/tz-announce/2019-July/56.html To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/tzdata/+bug/1835257/+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 1835297] Re: Precision 7730 smart card reader does not work out of box
Hi Ludovic, I can provide the output as soon as I get back in front of that machine; I'm referring to the built in smart card reader in a Dell Precision 7730 mobile workstation. It's a Broadcom BCM58102PB0KFBG smart card reader, my apologies. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to pcsc-lite in Ubuntu. https://bugs.launchpad.net/bugs/1835297 Title: Precision 7730 smart card reader does not work out of box Status in pcsc-lite package in Ubuntu: New Bug description: The Canonical certified smart card reader will not function until the following commands are run: sudo mkdir /tmp/USH cd /tmp/USH sudo mkdir debs cd debs sudo wget https://http.kali.org/pool/main/p/pcsc-lite/libpcsclite- dev_1.8.24-1_amd64.deb sudo wget https://http.kali.org/pool/main/p/pcsc- lite/libpcsclite1_1.8.24-1_amd64.deb sudo wget https://http.kali.org/pool/main/p/pcsc- lite/pcscd_1.8.24-1_amd64.deb sudo wget https://http.kali.org/pool/main/p/pcsc-tools/pcsc- tools_1.5.4-1_amd64.deb cd .. sudo apt-get -f install -y sudo apt purge lib-pcsc* pcscd* -y sudo apt install ./debs/*.deb --install-recommends -y sudo apt-get install libusb-1.0-0-dev sudo wget https://alioth- archive.debian.org/releases/pcsclite/ccid/1.4.25/ccid-1.4.25.tar.bz2 sudo tar xvfj ccid-*.tar.bz2 cd ccid-1.4.25/ ./configure sudo make sudo make install sudo cp src/92_pcscd_ccid.rules /etc/udev/rules.d/ sudo systemctl restart pcscd sudo systemctl status pcscd sudo pcsc_scan Additionally, the following commands, which do the same thing as the above in a cleaner way, do NOT resolve the issue in both the OEM and public image: sudo apt install -y libpcsclite-dev libpcsclite1 pcscd pcsc-tools libusb-1.0-0 libusb-1.0-0-dev libccid libacsccid1 sudo systemctl restart pcscd sudo systemctl status pcscd sudo pcsc_scan To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/pcsc-lite/+bug/1835297/+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 1835297] Re: Precision 7730 smart card reader does not work out of box
I have no idea what the "Precision 7730 smart card reader". Can you add here the output of the "lsusb" command? -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to pcsc-lite in Ubuntu. https://bugs.launchpad.net/bugs/1835297 Title: Precision 7730 smart card reader does not work out of box Status in pcsc-lite package in Ubuntu: New Bug description: The Canonical certified smart card reader will not function until the following commands are run: sudo mkdir /tmp/USH cd /tmp/USH sudo mkdir debs cd debs sudo wget https://http.kali.org/pool/main/p/pcsc-lite/libpcsclite- dev_1.8.24-1_amd64.deb sudo wget https://http.kali.org/pool/main/p/pcsc- lite/libpcsclite1_1.8.24-1_amd64.deb sudo wget https://http.kali.org/pool/main/p/pcsc- lite/pcscd_1.8.24-1_amd64.deb sudo wget https://http.kali.org/pool/main/p/pcsc-tools/pcsc- tools_1.5.4-1_amd64.deb cd .. sudo apt-get -f install -y sudo apt purge lib-pcsc* pcscd* -y sudo apt install ./debs/*.deb --install-recommends -y sudo apt-get install libusb-1.0-0-dev sudo wget https://alioth- archive.debian.org/releases/pcsclite/ccid/1.4.25/ccid-1.4.25.tar.bz2 sudo tar xvfj ccid-*.tar.bz2 cd ccid-1.4.25/ ./configure sudo make sudo make install sudo cp src/92_pcscd_ccid.rules /etc/udev/rules.d/ sudo systemctl restart pcscd sudo systemctl status pcscd sudo pcsc_scan Additionally, the following commands, which do the same thing as the above in a cleaner way, do NOT resolve the issue in both the OEM and public image: sudo apt install -y libpcsclite-dev libpcsclite1 pcscd pcsc-tools libusb-1.0-0 libusb-1.0-0-dev libccid libacsccid1 sudo systemctl restart pcscd sudo systemctl status pcscd sudo pcsc_scan To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/pcsc-lite/+bug/1835297/+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 1834494] Re: latest bzip2 reports crc errors incorrectly
Thanks a lot @Mark for the quick fix! :) ** Changed in: bzip2 (Ubuntu) Status: Confirmed => In Progress -- 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: In Progress 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 1835297] [NEW] Precision 7730 smart card reader does not work out of box
Public bug reported: The Canonical certified smart card reader will not function until the following commands are run: sudo mkdir /tmp/USH cd /tmp/USH sudo mkdir debs cd debs sudo wget https://http.kali.org/pool/main/p/pcsc-lite/libpcsclite- dev_1.8.24-1_amd64.deb sudo wget https://http.kali.org/pool/main/p/pcsc- lite/libpcsclite1_1.8.24-1_amd64.deb sudo wget https://http.kali.org/pool/main/p/pcsc- lite/pcscd_1.8.24-1_amd64.deb sudo wget https://http.kali.org/pool/main/p/pcsc-tools/pcsc- tools_1.5.4-1_amd64.deb cd .. sudo apt-get -f install -y sudo apt purge lib-pcsc* pcscd* -y sudo apt install ./debs/*.deb --install-recommends -y sudo apt-get install libusb-1.0-0-dev sudo wget https://alioth- archive.debian.org/releases/pcsclite/ccid/1.4.25/ccid-1.4.25.tar.bz2 sudo tar xvfj ccid-*.tar.bz2 cd ccid-1.4.25/ ./configure sudo make sudo make install sudo cp src/92_pcscd_ccid.rules /etc/udev/rules.d/ sudo systemctl restart pcscd sudo systemctl status pcscd sudo pcsc_scan Additionally, the following commands, which do the same thing as the above in a cleaner way, do NOT resolve the issue in both the OEM and public image: sudo apt install -y libpcsclite-dev libpcsclite1 pcscd pcsc-tools libusb-1.0-0 libusb-1.0-0-dev libccid libacsccid1 sudo systemctl restart pcscd sudo systemctl status pcscd sudo pcsc_scan ** Affects: pcsc-lite (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to pcsc-lite in Ubuntu. https://bugs.launchpad.net/bugs/1835297 Title: Precision 7730 smart card reader does not work out of box Status in pcsc-lite package in Ubuntu: New Bug description: The Canonical certified smart card reader will not function until the following commands are run: sudo mkdir /tmp/USH cd /tmp/USH sudo mkdir debs cd debs sudo wget https://http.kali.org/pool/main/p/pcsc-lite/libpcsclite- dev_1.8.24-1_amd64.deb sudo wget https://http.kali.org/pool/main/p/pcsc- lite/libpcsclite1_1.8.24-1_amd64.deb sudo wget https://http.kali.org/pool/main/p/pcsc- lite/pcscd_1.8.24-1_amd64.deb sudo wget https://http.kali.org/pool/main/p/pcsc-tools/pcsc- tools_1.5.4-1_amd64.deb cd .. sudo apt-get -f install -y sudo apt purge lib-pcsc* pcscd* -y sudo apt install ./debs/*.deb --install-recommends -y sudo apt-get install libusb-1.0-0-dev sudo wget https://alioth- archive.debian.org/releases/pcsclite/ccid/1.4.25/ccid-1.4.25.tar.bz2 sudo tar xvfj ccid-*.tar.bz2 cd ccid-1.4.25/ ./configure sudo make sudo make install sudo cp src/92_pcscd_ccid.rules /etc/udev/rules.d/ sudo systemctl restart pcscd sudo systemctl status pcscd sudo pcsc_scan Additionally, the following commands, which do the same thing as the above in a cleaner way, do NOT resolve the issue in both the OEM and public image: sudo apt install -y libpcsclite-dev libpcsclite1 pcscd pcsc-tools libusb-1.0-0 libusb-1.0-0-dev libccid libacsccid1 sudo systemctl restart pcscd sudo systemctl status pcscd sudo pcsc_scan To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/pcsc-lite/+bug/1835297/+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 1830914] Re: software-properties-gtk does not run at all!
weird, why would that change makes a difference if the imports are not
failing? are you sure it's the same issue?
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to software-properties in
Ubuntu.
https://bugs.launchpad.net/bugs/1830914
Title:
software-properties-gtk does not run at all!
Status in software-properties package in Ubuntu:
Incomplete
Bug description:
software-properties-gtk does not even start!
$ software-properties-gtk --debug
ENABLED COMPS: {'universe', 'main'}
INTERNET COMPS: {'universe', 'main'}
MAIN SOURCES
URI: http://archive.ubuntu.com/ubuntu
Comps: ['main']
Enabled: True
Valid: True
MatchURI: archive.ubuntu.com/ubuntu
BaseURI: http://archive.ubuntu.com/ubuntu
URI: http://archive.ubuntu.com/ubuntu
Comps: ['universe']
Enabled: True
Valid: True
MatchURI: archive.ubuntu.com/ubuntu
BaseURI: http://archive.ubuntu.com/ubuntu
CHILD SOURCES
URI: http://archive.ubuntu.com/ubuntu
Comps: ['main']
Enabled: True
Valid: True
MatchURI: archive.ubuntu.com/ubuntu
BaseURI: None
URI: http://archive.ubuntu.com/ubuntu
Comps: ['universe']
Enabled: True
Valid: True
MatchURI: archive.ubuntu.com/ubuntu
BaseURI: None
URI: http://archive.ubuntu.com/ubuntu
Comps: ['main']
Enabled: True
Valid: True
MatchURI: archive.ubuntu.com/ubuntu|security.ubuntu.com
BaseURI: http://security.ubuntu.com/ubuntu/
URI: http://archive.ubuntu.com/ubuntu
Comps: ['universe']
Enabled: True
Valid: True
MatchURI: archive.ubuntu.com/ubuntu|security.ubuntu.com
BaseURI: http://security.ubuntu.com/ubuntu/
URI: http://archive.ubuntu.com/ubuntu
Comps: ['universe', 'main']
Enabled: True
Valid: True
MatchURI: archive.ubuntu.com/ubuntu
BaseURI: None
CDROM SOURCES
SOURCE CODE SOURCES
DISABLED SOURCES
ISV
Traceback (most recent call last):
File "/usr/bin/software-properties-gtk", line 100, in
app = SoftwarePropertiesGtk(datadir=options.data_dir, options=options,
file=file)
File
"/usr/lib/python3/dist-packages/softwareproperties/gtk/SoftwarePropertiesGtk.py",
line 200, in __init__
self.init_livepatch()
File
"/usr/lib/python3/dist-packages/softwareproperties/gtk/SoftwarePropertiesGtk.py",
line 1482, in init_livepatch
self.livepatch_page = LivepatchPage(self)
File
"/usr/lib/python3/dist-packages/softwareproperties/gtk/LivepatchPage.py", line
51, in __init__
self._lps = LivepatchService()
File
"/usr/lib/python3/dist-packages/softwareproperties/LivepatchService.py", line
93, in __init__
self._session = requests_unixsocket.Session()
NameError: name 'requests_unixsocket' is not defined
{Exited with code 1.}
$ lsb_release -a
No LSB modules are available.
Distributor ID: Ubuntu
Description: Ubuntu 19.04
Release: 19.04
Codename: disco
$ dpkg-query -l software-properties-gtk python3-requests-unixsocket
Desired=Unknown/Install/Remove/Purge/Hold
| Status=Not/Inst/Conf-files/Unpacked/halF-conf/Half-inst/trig-aWait/Trig-pend
|/ Err?=(none)/Reinst-required (Status,Err: uppercase=bad)
||/ NameVersion Architecture Description
+++-===---===
ii python3-requests-unixsocket 0.1.5-3 all Use requests to
talk HTTP via a UNIX domain socket - Python 3.x
ii software-properties-gtk 0.97.11 all manage the
repositories that you install software from (gtk)
$ sudo apt-get update
{Works.}
$ sudo apt-get dist-upgrade
{Works.}
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/software-properties/+bug/1830914/+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 1835257] Re: update tzdata package to 2019b
** Changed in: tzdata (Ubuntu) Importance: Undecided => High ** Tags added: rls-bb-incoming rls-dd-incoming rls-ee-incoming -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to tzdata in Ubuntu. https://bugs.launchpad.net/bugs/1835257 Title: update tzdata package to 2019b Status in tzdata package in Ubuntu: New Bug description: Update tzdata package to 2019b. https://mm.icann.org/pipermail/tz-announce/2019-July/56.html To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/tzdata/+bug/1835257/+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 1827253] Re: [apparmor] missing 'mr' on binary for usage on containers
This bug was fixed in the package rsyslog - 8.1901.0-1ubuntu2 --- rsyslog (8.1901.0-1ubuntu2) eoan; urgency=medium [ Simon Deziel ] * d/usr.sbin.rsyslogd: allow reading/mmap'ing rsyslog binary This is required for usage inside containers (LP: #1827253) -- Christian Ehrhardt Wed, 03 Jul 2019 16:34:41 +0200 ** Changed in: rsyslog (Ubuntu) Status: In Progress => Fix Released -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to rsyslog in Ubuntu. https://bugs.launchpad.net/bugs/1827253 Title: [apparmor] missing 'mr' on binary for usage on containers Status in rsyslog package in Ubuntu: Fix Released Bug description: Issue description: Enabling the rsyslog (disabled by default) Apparmor profile causes rsyslog to fail to start when running *inside a container*. Steps to reproduce: 1) Create a 'eoan' container called rs1 here: lxc launch ubuntu-daily:e rs1 2) Enter the container lxc shell rs1 3) Enable apparmor profile rm /etc/apparmor.d/disable/usr.sbin.rsyslogd apparmor_parser -r -T -W /etc/apparmor.d/usr.sbin.rsyslogd systemctl restart rsyslog 4) notice rsyslog failed to start systemctl status rsyslog Workaround: echo ' /usr/sbin/rsyslogd mr,' >> /etc/apparmor.d/local/usr.sbin.rsyslogd apparmor_parser -r -T -W /etc/apparmor.d/usr.sbin.rsyslogd systemctl restart rsyslog Additional information: root@rs1:~# uname -a Linux rs1 4.15.0-48-generic #51-Ubuntu SMP Wed Apr 3 08:28:49 UTC 2019 x86_64 x86_64 x86_64 GNU/Linux root@rs1:~# lsb_release -rd Description: Ubuntu Eoan EANIMAL (development branch) Release: 19.10 root@rs1:~# dpkg -l| grep -wE 'apparmor|rsyslog' ii apparmor 2.13.2-9ubuntu6 amd64user-space parser utility for AppArmor ii rsyslog 8.32.0-1ubuntu7 amd64reliable system and kernel logging daemon ProblemType: Bug DistroRelease: Ubuntu 19.10 Package: rsyslog 8.32.0-1ubuntu7 ProcVersionSignature: Ubuntu 4.15.0-48.51-generic 4.15.18 Uname: Linux 4.15.0-48-generic x86_64 ApportVersion: 2.20.10-0ubuntu27 Architecture: amd64 Date: Wed May 1 17:36:29 2019 ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: rsyslog UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/rsyslog/+bug/1827253/+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 1830914] Re: software-properties-gtk does not run at all!
@seb128
I am seeing the same issue after I upgraded to 19.04.
The output of both the commands you requested is a new line (shown below)
sved@sveddt:~$ python3 -c 'import dateutil.parser'
sved@sveddt:~$ python3 -c 'import requests_unixsocket'
sved@sveddt:~$
--
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/1830914
Title:
software-properties-gtk does not run at all!
Status in software-properties package in Ubuntu:
Incomplete
Bug description:
software-properties-gtk does not even start!
$ software-properties-gtk --debug
ENABLED COMPS: {'universe', 'main'}
INTERNET COMPS: {'universe', 'main'}
MAIN SOURCES
URI: http://archive.ubuntu.com/ubuntu
Comps: ['main']
Enabled: True
Valid: True
MatchURI: archive.ubuntu.com/ubuntu
BaseURI: http://archive.ubuntu.com/ubuntu
URI: http://archive.ubuntu.com/ubuntu
Comps: ['universe']
Enabled: True
Valid: True
MatchURI: archive.ubuntu.com/ubuntu
BaseURI: http://archive.ubuntu.com/ubuntu
CHILD SOURCES
URI: http://archive.ubuntu.com/ubuntu
Comps: ['main']
Enabled: True
Valid: True
MatchURI: archive.ubuntu.com/ubuntu
BaseURI: None
URI: http://archive.ubuntu.com/ubuntu
Comps: ['universe']
Enabled: True
Valid: True
MatchURI: archive.ubuntu.com/ubuntu
BaseURI: None
URI: http://archive.ubuntu.com/ubuntu
Comps: ['main']
Enabled: True
Valid: True
MatchURI: archive.ubuntu.com/ubuntu|security.ubuntu.com
BaseURI: http://security.ubuntu.com/ubuntu/
URI: http://archive.ubuntu.com/ubuntu
Comps: ['universe']
Enabled: True
Valid: True
MatchURI: archive.ubuntu.com/ubuntu|security.ubuntu.com
BaseURI: http://security.ubuntu.com/ubuntu/
URI: http://archive.ubuntu.com/ubuntu
Comps: ['universe', 'main']
Enabled: True
Valid: True
MatchURI: archive.ubuntu.com/ubuntu
BaseURI: None
CDROM SOURCES
SOURCE CODE SOURCES
DISABLED SOURCES
ISV
Traceback (most recent call last):
File "/usr/bin/software-properties-gtk", line 100, in
app = SoftwarePropertiesGtk(datadir=options.data_dir, options=options,
file=file)
File
"/usr/lib/python3/dist-packages/softwareproperties/gtk/SoftwarePropertiesGtk.py",
line 200, in __init__
self.init_livepatch()
File
"/usr/lib/python3/dist-packages/softwareproperties/gtk/SoftwarePropertiesGtk.py",
line 1482, in init_livepatch
self.livepatch_page = LivepatchPage(self)
File
"/usr/lib/python3/dist-packages/softwareproperties/gtk/LivepatchPage.py", line
51, in __init__
self._lps = LivepatchService()
File
"/usr/lib/python3/dist-packages/softwareproperties/LivepatchService.py", line
93, in __init__
self._session = requests_unixsocket.Session()
NameError: name 'requests_unixsocket' is not defined
{Exited with code 1.}
$ lsb_release -a
No LSB modules are available.
Distributor ID: Ubuntu
Description: Ubuntu 19.04
Release: 19.04
Codename: disco
$ dpkg-query -l software-properties-gtk python3-requests-unixsocket
Desired=Unknown/Install/Remove/Purge/Hold
| Status=Not/Inst/Conf-files/Unpacked/halF-conf/Half-inst/trig-aWait/Trig-pend
|/ Err?=(none)/Reinst-required (Status,Err: uppercase=bad)
||/ NameVersion Architecture Description
+++-===---===
ii python3-requests-unixsocket 0.1.5-3 all Use requests to
talk HTTP via a UNIX domain socket - Python 3.x
ii software-properties-gtk 0.97.11 all manage the
repositories that you install software from (gtk)
$ sudo apt-get update
{Works.}
$ sudo apt-get dist-upgrade
{Works.}
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/software-properties/+bug/1830914/+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 1835257] Re: update tzdata package to 2019b
** Tags added: upgrade-software-version -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to tzdata in Ubuntu. https://bugs.launchpad.net/bugs/1835257 Title: update tzdata package to 2019b Status in tzdata package in Ubuntu: New Bug description: Update tzdata package to 2019b. https://mm.icann.org/pipermail/tz-announce/2019-July/56.html To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/tzdata/+bug/1835257/+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 1718658] Re: ecryptfs-mount-private fails to initialize ecryptfs keys
I have just encountered this issue on 18.04 with Linux 4.15.0-54-generic. The proposed workaround does not work for 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/1718658 Title: ecryptfs-mount-private fails to initialize ecryptfs keys Status in ecryptfs-utils package in Ubuntu: Confirmed Status in systemd package in Ubuntu: Confirmed Bug description: ecryptfs-mount-private fails to mount the ecryptfs after the 1st reboot after creating the ecryptfs by ecryptfs-setup-private. After the unsucessful attempt dmesg contains: [ 1265.695388] Could not find key with description: [] [ 1265.695393] process_request_key_err: No key [ 1265.695394] Could not find valid key in user session keyring for sig specified in mount option: [] [ 1265.695395] One or more global auth toks could not properly register; rc = [-2] [ 1265.695396] Error parsing options; rc = [-2] Note: The correct key ID has been replaced in the "". I also accidentally found an workaround - just running ecrytpfs- manager and then the ecryptfs-mount-private (it does not ask for password for the second time and mounts the ecryptfs correctly): host:~$ ecryptfs-manager eCryptfs key management menu --- 1. Add passphrase key to keyring 2. Add public key to keyring 3. Generate new public/private keypair 4. Exit Make selection: 4 host:~$ ls Private/ Access-Your-Private-Data.desktop README.txt host:~$ ecryptfs-mount-private host:~$ ls Private/ To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ecryptfs-utils/+bug/1718658/+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 1829968] Re: motd [on at least some instances] does not auto-update daily
The timer is still incorrect as we can see here: $ systemctl list-timers --all NEXT LEFT LAST PASSED UNIT ACTIVATES Wed 2019-07-03 10:31:55 PDT 36min leftWed 2019-07-03 09:31:58 PDT 23min ago anacron.timeranacron.service Wed 2019-07-03 11:53:16 PDT 1h 57min left Tue 2019-07-02 22:48:05 PDT 11h ago apt-daily.timer apt-daily.service Wed 2019-07-03 15:28:41 PDT 5h 33min left Tue 2019-07-02 15:28:41 PDT 18h ago systemd-tmpfiles-clean.timer systemd-tmpfiles-clea Wed 2019-07-03 22:07:28 PDT 12h left Tue 2019-07-02 01:10:22 PDT 1 day 8h ago mdmonitor-oneshot.timer mdmonitor-oneshot.ser Thu 2019-07-04 00:00:00 PDT 14h left Wed 2019-07-03 00:00:01 PDT 9h ago logrotate.timer logrotate.service Thu 2019-07-04 00:00:00 PDT 14h left Wed 2019-07-03 00:00:01 PDT 9h ago man-db.timer man-db.service Thu 2019-07-04 06:45:10 PDT 20h left Wed 2019-07-03 06:18:41 PDT 3h 36min ago apt-daily-upgrade.timer apt-daily-upgrade.ser Sun 2019-07-07 03:10:43 PDT 3 days left Sun 2019-06-30 03:11:23 PDT 3 days ago e2scrub_all.timere2scrub_all.service Sun 2019-07-07 23:51:21 PDT 4 days left Mon 2019-06-24 15:03:57 PDT 1 weeks 1 days ago mdcheck_start.timer mdcheck_start.service Mon 2019-07-08 00:00:00 PDT 4 days left Mon 2019-07-01 00:00:01 PDT 2 days ago fstrim.timer fstrim.service n/a n/a n/a n/a mdcheck_continue.timer mdcheck_continue.serv n/a n/a Tue 2019-06-25 04:05:23 PDT 1 weeks 1 days ago motd-news.timer motd-news.service n/a n/a n/a n/a snapd.snap-repair.timer snapd.snap-repair.ser n/a n/a Mon 2019-06-24 15:13:25 PDT 1 weeks 1 days ago ureadahead-stop.timerureadahead-stop.servi 14 timers listed. [ 9:55AM 11039 ] [ bdmurray@impulse:~/source-trees/daisy/trunk ] $ systemctl status motd-news.timer ● motd-news.timer - Message of the Day Loaded: loaded (/lib/systemd/system/motd-news.timer; enabled; vendor preset: enabled) Active: active (elapsed) since Mon 2019-06-24 15:12:33 PDT; 1 weeks 1 days ago Trigger: n/a Jun 24 15:12:33 impulse systemd[1]: Started Message of the Day. [ 9:56AM 11041 ] [ bdmurray@impulse:~/source-trees/daisy/trunk ] $ apt-cache policy base-files base-files: Installed: 10.2ubuntu3 Candidate: 10.2ubuntu3 Version table: *** 10.2ubuntu3 500 500 http://192.168.10.7/ubuntu eoan/main amd64 Packages 100 /var/lib/dpkg/status ** Changed in: base-files (Ubuntu Eoan) Status: Fix Released => In Progress -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to base-files in Ubuntu. https://bugs.launchpad.net/bugs/1829968 Title: motd [on at least some instances] does not auto-update daily Status in base-files package in Ubuntu: In Progress Status in base-files source package in Bionic: Triaged Status in base-files source package in Cosmic: New Status in base-files source package in Disco: New Status in base-files source package in Eoan: In Progress Bug description: [Impact] motd-news timer is not properly configured and may not run regularly so long running systems will not get an updated motd [Test Case] The system being tested must have curl installed - base-files does not depend on it because reasons. 1) Run 'systemctl status mot-news.timer' 2) Observe that the Trigger section is n/a With the version of the package from -proposed the Trigger section should instead contain something like the following: Trigger: Mon 2019-06-17 11:42:25 PDT; 20min left One should also wait to ensure that the trigger actually ran and that /var/cache/motd-news has been updated. [Regression Potential] I can't think of any on the client side as the job wasn't working at all but it may cause extra load on the motd server. Original Description I have a VM running on AWS. It was launched on May 9th: $ uptime 05:26:21 up 12 days, 6:34, 1 user, load average: 0.00, 0.00, 0.00 $ date Wed May 22 05:26:24 UTC 2019 I touched none of the system defaults, and yet the motd has not updated automatically. $ ls -l /var/cache/motd-news -rw-r--r-- 1 root root 0 May 9 22:53 /var/cache/motd-news The systemd timer unit looks like this: $ systemctl status motd-news.timer ● motd-news.timer - Message of the Day Loaded: loaded (/lib/systemd/system/motd-news.timer; enabled; vendor preset: enabled) Active: active (elapsed) since Thu 2
[Touch-packages] [Bug 1834494] Re: latest bzip2 reports crc errors incorrectly
Yes, there was one testcase that wasn't handled by the patch. There is an updated patch that handles both the original file and the new testcase. https://sourceware.org/ml/bzip2-devel/2019-q3/msg7.html ** Patch added: "Accept as many selectors as the file format allows" https://bugs.launchpad.net/ubuntu/+source/bzip2/+bug/1834494/+attachment/5274916/+files/0001-Accept-as-many-selectors-as-the-file-format-allows.patch -- 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
Re: [Touch-packages] [Bug 1827253] Re: [apparmor] missing 'mr' on binary for usage on containers
On 2019-07-03 10:47 a.m., Christian Ehrhardt wrote: > I feel bad that this hung around so log, but today I saw it and gave it a > review. > This is building in Eoan now. No worries for the delay, I know where to find you if something more critical is taking too long to my taste ;) Thank you Christian! Regards, Simon -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to rsyslog in Ubuntu. https://bugs.launchpad.net/bugs/1827253 Title: [apparmor] missing 'mr' on binary for usage on containers Status in rsyslog package in Ubuntu: In Progress Bug description: Issue description: Enabling the rsyslog (disabled by default) Apparmor profile causes rsyslog to fail to start when running *inside a container*. Steps to reproduce: 1) Create a 'eoan' container called rs1 here: lxc launch ubuntu-daily:e rs1 2) Enter the container lxc shell rs1 3) Enable apparmor profile rm /etc/apparmor.d/disable/usr.sbin.rsyslogd apparmor_parser -r -T -W /etc/apparmor.d/usr.sbin.rsyslogd systemctl restart rsyslog 4) notice rsyslog failed to start systemctl status rsyslog Workaround: echo ' /usr/sbin/rsyslogd mr,' >> /etc/apparmor.d/local/usr.sbin.rsyslogd apparmor_parser -r -T -W /etc/apparmor.d/usr.sbin.rsyslogd systemctl restart rsyslog Additional information: root@rs1:~# uname -a Linux rs1 4.15.0-48-generic #51-Ubuntu SMP Wed Apr 3 08:28:49 UTC 2019 x86_64 x86_64 x86_64 GNU/Linux root@rs1:~# lsb_release -rd Description: Ubuntu Eoan EANIMAL (development branch) Release: 19.10 root@rs1:~# dpkg -l| grep -wE 'apparmor|rsyslog' ii apparmor 2.13.2-9ubuntu6 amd64user-space parser utility for AppArmor ii rsyslog 8.32.0-1ubuntu7 amd64reliable system and kernel logging daemon ProblemType: Bug DistroRelease: Ubuntu 19.10 Package: rsyslog 8.32.0-1ubuntu7 ProcVersionSignature: Ubuntu 4.15.0-48.51-generic 4.15.18 Uname: Linux 4.15.0-48-generic x86_64 ApportVersion: 2.20.10-0ubuntu27 Architecture: amd64 Date: Wed May 1 17:36:29 2019 ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: rsyslog UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/rsyslog/+bug/1827253/+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 1827253] Re: [apparmor] missing 'mr' on binary for usage on containers
This actually is a perfect bug: - simple case - solution on a silver plate - only changing d/* content - already ubuntu Delta I feel bad that this hung around so log, but today I saw it and gave it a review. This is building in Eoan now. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to rsyslog in Ubuntu. https://bugs.launchpad.net/bugs/1827253 Title: [apparmor] missing 'mr' on binary for usage on containers Status in rsyslog package in Ubuntu: In Progress Bug description: Issue description: Enabling the rsyslog (disabled by default) Apparmor profile causes rsyslog to fail to start when running *inside a container*. Steps to reproduce: 1) Create a 'eoan' container called rs1 here: lxc launch ubuntu-daily:e rs1 2) Enter the container lxc shell rs1 3) Enable apparmor profile rm /etc/apparmor.d/disable/usr.sbin.rsyslogd apparmor_parser -r -T -W /etc/apparmor.d/usr.sbin.rsyslogd systemctl restart rsyslog 4) notice rsyslog failed to start systemctl status rsyslog Workaround: echo ' /usr/sbin/rsyslogd mr,' >> /etc/apparmor.d/local/usr.sbin.rsyslogd apparmor_parser -r -T -W /etc/apparmor.d/usr.sbin.rsyslogd systemctl restart rsyslog Additional information: root@rs1:~# uname -a Linux rs1 4.15.0-48-generic #51-Ubuntu SMP Wed Apr 3 08:28:49 UTC 2019 x86_64 x86_64 x86_64 GNU/Linux root@rs1:~# lsb_release -rd Description: Ubuntu Eoan EANIMAL (development branch) Release: 19.10 root@rs1:~# dpkg -l| grep -wE 'apparmor|rsyslog' ii apparmor 2.13.2-9ubuntu6 amd64user-space parser utility for AppArmor ii rsyslog 8.32.0-1ubuntu7 amd64reliable system and kernel logging daemon ProblemType: Bug DistroRelease: Ubuntu 19.10 Package: rsyslog 8.32.0-1ubuntu7 ProcVersionSignature: Ubuntu 4.15.0-48.51-generic 4.15.18 Uname: Linux 4.15.0-48-generic x86_64 ApportVersion: 2.20.10-0ubuntu27 Architecture: amd64 Date: Wed May 1 17:36:29 2019 ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: rsyslog UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/rsyslog/+bug/1827253/+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 1832882] Re: libcurl-gnutls segfaults spotify client
I can confirm this issue as well. Although for the workaround, libcurl3-gnutls_7.64.0-3 is no longer available from http://http.us.debian.org/debian/pool/main/c/curl/, but installing libcurl3-gnutls_7.64.0-4 works just as well. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to curl in Ubuntu. https://bugs.launchpad.net/bugs/1832882 Title: libcurl-gnutls segfaults spotify client Status in curl package in Ubuntu: Fix Released Status in curl source package in Disco: Confirmed Bug description: The latest release of Spotify client segfaults in libcurl-gnutls as can be read in this thread on spotify support forum: https://community.spotify.com/t5/Desktop-Linux/Ubuntu-19-04-deb-package-segfault/td-p/4761479 According to one participant the work-around is to install debian packages libgnutls30_3.6.8-1_amd64.deb and libcurl3-gnutls_7.64.0-3_amd64.deb Ubuntu 19.04 version of the packages: libgnutls30 3.6.5-2ubuntu1.1 libcurl3-gnutls 7.64.0-2ubuntu1.1 As the bug can be resolved by installing debian packages, I assume Ubuntu's version of the packages is at fault and should be upgraded to match debian's level as soon as possible. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/curl/+bug/1832882/+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 1835257] [NEW] update tzdata package to 2019b
Public bug reported: Update tzdata package to 2019b. https://mm.icann.org/pipermail/tz-announce/2019-July/56.html ** Affects: tzdata (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to tzdata in Ubuntu. https://bugs.launchpad.net/bugs/1835257 Title: update tzdata package to 2019b Status in tzdata package in Ubuntu: New Bug description: Update tzdata package to 2019b. https://mm.icann.org/pipermail/tz-announce/2019-July/56.html To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/tzdata/+bug/1835257/+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 1827253] Re: [apparmor] missing 'mr' on binary for usage on containers
** Changed in: rsyslog (Ubuntu) Status: New => In Progress -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to rsyslog in Ubuntu. https://bugs.launchpad.net/bugs/1827253 Title: [apparmor] missing 'mr' on binary for usage on containers Status in rsyslog package in Ubuntu: In Progress Bug description: Issue description: Enabling the rsyslog (disabled by default) Apparmor profile causes rsyslog to fail to start when running *inside a container*. Steps to reproduce: 1) Create a 'eoan' container called rs1 here: lxc launch ubuntu-daily:e rs1 2) Enter the container lxc shell rs1 3) Enable apparmor profile rm /etc/apparmor.d/disable/usr.sbin.rsyslogd apparmor_parser -r -T -W /etc/apparmor.d/usr.sbin.rsyslogd systemctl restart rsyslog 4) notice rsyslog failed to start systemctl status rsyslog Workaround: echo ' /usr/sbin/rsyslogd mr,' >> /etc/apparmor.d/local/usr.sbin.rsyslogd apparmor_parser -r -T -W /etc/apparmor.d/usr.sbin.rsyslogd systemctl restart rsyslog Additional information: root@rs1:~# uname -a Linux rs1 4.15.0-48-generic #51-Ubuntu SMP Wed Apr 3 08:28:49 UTC 2019 x86_64 x86_64 x86_64 GNU/Linux root@rs1:~# lsb_release -rd Description: Ubuntu Eoan EANIMAL (development branch) Release: 19.10 root@rs1:~# dpkg -l| grep -wE 'apparmor|rsyslog' ii apparmor 2.13.2-9ubuntu6 amd64user-space parser utility for AppArmor ii rsyslog 8.32.0-1ubuntu7 amd64reliable system and kernel logging daemon ProblemType: Bug DistroRelease: Ubuntu 19.10 Package: rsyslog 8.32.0-1ubuntu7 ProcVersionSignature: Ubuntu 4.15.0-48.51-generic 4.15.18 Uname: Linux 4.15.0-48-generic x86_64 ApportVersion: 2.20.10-0ubuntu27 Architecture: amd64 Date: Wed May 1 17:36:29 2019 ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: rsyslog UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/rsyslog/+bug/1827253/+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 1834128] Re: Multiple sshd services cannot be executed
I'm sorry, your answer doesn't help complete this bug report, so I'm setting the status back to Incomplete. You may find it helpful to read "How to report bugs effectively" http://www.chiark.greenend.org.uk/~sgtatham/bugs.html. We'd be grateful if you would then provide a more complete description of the *problem* that you're describing. In particular, I expect your report to first demonstrate the *problem*, not assume a solution. It will help if your problem statement includes the headings "Steps to reproduce", "Expected behaviour" and "Actual behaviour". Until you have done this I don't expect that your report will make any progress. Once you've done that, please change the bug status back to New. Until you've done that, please leave the bug status as Incomplete. ** Changed in: openssh (Ubuntu) Status: New => Incomplete -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to openssh in Ubuntu. https://bugs.launchpad.net/bugs/1834128 Title: Multiple sshd services cannot be executed Status in openssh package in Ubuntu: Incomplete Bug description: OpenSSH 7.6p1 Ubuntu 18.04.2 (LTS) (Bionic) See also Ticket #1831765, #1690485, and #1832110 regarding the path of the privilege separation directory (aka: /run/sshd). The current Debian installer sets the RuntimeDirectory=sshd (i.e. /run/sshd) in sshd.service (i.e. /lib/systemd/system/sshd.service) and sshd@.service (i.e. /lib/systemd/system/sshd@.service). This is not the best means of implementing this service. The problem is that the systemd deletes the RuntimeDirectory resource as soon as the service is stopped. When this happens, other sshd services will fault since the privileged separation directory is no longer there. We need to modify the configuration as follows: 1) Create /usr/lib/tmpfiles.d/sshd.conf that defines the /run/sshd directory with root:root as the owner and the protection of 0755. 2) Change the assignment of the RuntimeDirectory in sshd.service to something other than sshd (i.e. /run/sshd). 3) Change the assignment of the RuntimeDirectory in sshd@.service to something other than sshd (i.e. /run/sshd). Both OpenSSH and Ubuntu have declined to provision a means of adjusting the Privilege Separation directory. Since both teams do not want to address this, we need to have a means of implementing multiple instance sshd invocation using systemd and avoiding using the RuntimeDirectory assignment of /run/sshd. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/openssh/+bug/1834128/+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 1834128] Re: Multiple sshd services cannot be executed
The way I created this was to implement 2 sshd services called wan_sshd and lan_sshd. I used the existing sshd.service files as templates. See attached files. This solution reliably works using Ubuntu 18.04.2 LTS with OpenSSH 7.6p1. Addition things I had to do: 1) Delete the sshd.service, sshd.socket, and sshd@.service in the /lib/systemd/system directory. 2) Perform a "sudo systemctl disable ssh". All this does is delete the links to the files in step #1. 3) Delete the /etc/rc*.d/S01ssh files. 4) Delete the /etc/init.d/ssh 5) Replace the /etc/default/ssh with the ssh.default in the ZIP file. 6) Delete the /etc/ssh/sshd_config. Add the sshd_*_config files from the ZIP file. 7) Add the wan_sshd* and lan_sshd* files to the /lib/systemd/system directory from the ZIP file. NOTE: Files called _at.service should be renamed to @.service. 8) Generate your own key files and make appropriate changes to the sshd_*_config files. 9) Add the usr_lib_tmpfiles_d.conf from the ZIP file as /usr/lib/tmpfiles.d/sshd.conf 10) Reboot the machine and make sure /run/sshd exists BEFORE enabling the 2 services. I make the assumption that the reader has the skill set to use systemctl to get the services started. I also assume the reader has the skill set to edit a shsd_*_config file. ** Attachment added: "Files from my server that work." https://bugs.launchpad.net/ubuntu/+source/openssh/+bug/1834128/+attachment/5274899/+files/SampleDualServer.zip ** Changed in: openssh (Ubuntu) Status: Incomplete => New -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to openssh in Ubuntu. https://bugs.launchpad.net/bugs/1834128 Title: Multiple sshd services cannot be executed Status in openssh package in Ubuntu: New Bug description: OpenSSH 7.6p1 Ubuntu 18.04.2 (LTS) (Bionic) See also Ticket #1831765, #1690485, and #1832110 regarding the path of the privilege separation directory (aka: /run/sshd). The current Debian installer sets the RuntimeDirectory=sshd (i.e. /run/sshd) in sshd.service (i.e. /lib/systemd/system/sshd.service) and sshd@.service (i.e. /lib/systemd/system/sshd@.service). This is not the best means of implementing this service. The problem is that the systemd deletes the RuntimeDirectory resource as soon as the service is stopped. When this happens, other sshd services will fault since the privileged separation directory is no longer there. We need to modify the configuration as follows: 1) Create /usr/lib/tmpfiles.d/sshd.conf that defines the /run/sshd directory with root:root as the owner and the protection of 0755. 2) Change the assignment of the RuntimeDirectory in sshd.service to something other than sshd (i.e. /run/sshd). 3) Change the assignment of the RuntimeDirectory in sshd@.service to something other than sshd (i.e. /run/sshd). Both OpenSSH and Ubuntu have declined to provision a means of adjusting the Privilege Separation directory. Since both teams do not want to address this, we need to have a means of implementing multiple instance sshd invocation using systemd and avoiding using the RuntimeDirectory assignment of /run/sshd. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/openssh/+bug/1834128/+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 1834128] Re: Multiple sshd services cannot be executed
NOTE: Even though this is listed as a low priority and an unusual configuration, the addition of /usr/lib/tmpfiles.d/sshd.conf and changing the RuntimeDirectory=sshd_service in the sshd.service file is a better solution that does not conflict with Upstream implementations. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to openssh in Ubuntu. https://bugs.launchpad.net/bugs/1834128 Title: Multiple sshd services cannot be executed Status in openssh package in Ubuntu: New Bug description: OpenSSH 7.6p1 Ubuntu 18.04.2 (LTS) (Bionic) See also Ticket #1831765, #1690485, and #1832110 regarding the path of the privilege separation directory (aka: /run/sshd). The current Debian installer sets the RuntimeDirectory=sshd (i.e. /run/sshd) in sshd.service (i.e. /lib/systemd/system/sshd.service) and sshd@.service (i.e. /lib/systemd/system/sshd@.service). This is not the best means of implementing this service. The problem is that the systemd deletes the RuntimeDirectory resource as soon as the service is stopped. When this happens, other sshd services will fault since the privileged separation directory is no longer there. We need to modify the configuration as follows: 1) Create /usr/lib/tmpfiles.d/sshd.conf that defines the /run/sshd directory with root:root as the owner and the protection of 0755. 2) Change the assignment of the RuntimeDirectory in sshd.service to something other than sshd (i.e. /run/sshd). 3) Change the assignment of the RuntimeDirectory in sshd@.service to something other than sshd (i.e. /run/sshd). Both OpenSSH and Ubuntu have declined to provision a means of adjusting the Privilege Separation directory. Since both teams do not want to address this, we need to have a means of implementing multiple instance sshd invocation using systemd and avoiding using the RuntimeDirectory assignment of /run/sshd. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/openssh/+bug/1834128/+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 1834129] Re: Presence of sshd_config mandatory
Thanks for updating the bug! I'll close it now. ** Changed in: openssh (Ubuntu) Status: Incomplete => Invalid -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to openssh in Ubuntu. https://bugs.launchpad.net/bugs/1834129 Title: Presence of sshd_config mandatory Status in openssh package in Ubuntu: Invalid Bug description: OpenSSH 7.9p1 Ubuntu 18..04.2 (LTS) If a sshd daemon is started with a "-f my_sshd_config" command-line specification the sshd process still requires the existence of the sshd_config. The bug is somewhere in one of the forked processes started when an external client attempts a connection. Since the sshd_config file does not exists, an external client connection cannot be started. Solution: If I "touch /etc/ssh/sshd_config" then the lock-up issue goes away and I am successfully able to login. Bug: If the sshd configuration file is specified in the command line execution of the daeomon, then this should be the only file that should be required. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/openssh/+bug/1834129/+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 1834129] Re: Presence of sshd_config mandatory
I was able to confirm that this was not a bug. I did a fresh build of 18.04.2 LTS server, and it appears to work just fine. My bad. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to openssh in Ubuntu. https://bugs.launchpad.net/bugs/1834129 Title: Presence of sshd_config mandatory Status in openssh package in Ubuntu: Incomplete Bug description: OpenSSH 7.9p1 Ubuntu 18..04.2 (LTS) If a sshd daemon is started with a "-f my_sshd_config" command-line specification the sshd process still requires the existence of the sshd_config. The bug is somewhere in one of the forked processes started when an external client attempts a connection. Since the sshd_config file does not exists, an external client connection cannot be started. Solution: If I "touch /etc/ssh/sshd_config" then the lock-up issue goes away and I am successfully able to login. Bug: If the sshd configuration file is specified in the command line execution of the daeomon, then this should be the only file that should be required. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/openssh/+bug/1834129/+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 1824111] Re: Backport packages for 18.04.3 HWE stack
This bug was fixed in the package mesa - 19.0.2-1ubuntu1.1~18.04.1 --- mesa (19.0.2-1ubuntu1.1~18.04.1) bionic; urgency=medium * Backport to bionic. mesa (19.0.2-1ubuntu1.1) disco; urgency=medium * radeon-rework-gfx9-scissor-workaround.diff: Fix invisible elements with GTK on Vega/Raven. (LP: #1831498) mesa (19.0.2-1ubuntu1~18.04.1) bionic; urgency=medium * Backport to bionic for 18.04.3 HWE stack update. (LP: #1824111) * control: Build-depend on libsensors4-dev. -- Timo Aaltonen Tue, 04 Jun 2019 00:10:13 +0300 ** Changed in: mesa (Ubuntu Bionic) Status: Fix Committed => Fix Released -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to mesa in Ubuntu. https://bugs.launchpad.net/bugs/1824111 Title: Backport packages for 18.04.3 HWE stack Status in OEM Priority Project: Confirmed Status in libclc package in Ubuntu: Invalid Status in libdrm package in Ubuntu: Invalid Status in llvm-toolchain-8 package in Ubuntu: Invalid Status in mesa package in Ubuntu: Invalid Status in libclc source package in Bionic: Fix Released Status in libdrm source package in Bionic: Fix Released Status in llvm-toolchain-8 source package in Bionic: Fix Released Status in mesa source package in Bionic: Fix Released Status in xorg-server-hwe-18.04 source package in Bionic: Fix Released Status in xserver-xorg-video-amdgpu-hwe-18.04 source package in Bionic: Fix Released Status in xserver-xorg-video-ati-hwe-18.04 source package in Bionic: Fix Released Status in xserver-xorg-video-nouveau-hwe-18.04 source package in Bionic: Fix Released Bug description: [Impact] These are needed for 18.04.3 images. [Test case] Boot a daily image, see that it still has the necessary stack installed and working. Check upgrade from stock bionic. [Regression potential] libdrm: very minimal chance for regressions llvm-8: a new package, no regression potential on it's own libclc: more or less just adds support for new llvm mesa: a new major release, but we'll pull the final stable release of 19.0.x series, so there shouldn't be any regressions left at that point xserver: a new minor release xorg drivers: modest updates, mainly just new ati/amdgpu [Other info] To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/1824111/+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 1821863] Re: Need to add Intel CML related pci-id's
This bug was fixed in the package mesa - 19.0.2-1ubuntu1.1~18.04.1 --- mesa (19.0.2-1ubuntu1.1~18.04.1) bionic; urgency=medium * Backport to bionic. mesa (19.0.2-1ubuntu1.1) disco; urgency=medium * radeon-rework-gfx9-scissor-workaround.diff: Fix invisible elements with GTK on Vega/Raven. (LP: #1831498) mesa (19.0.2-1ubuntu1~18.04.1) bionic; urgency=medium * Backport to bionic for 18.04.3 HWE stack update. (LP: #1824111) * control: Build-depend on libsensors4-dev. -- Timo Aaltonen Tue, 04 Jun 2019 00:10:13 +0300 ** Changed in: mesa (Ubuntu Bionic) Status: Fix Committed => Fix Released -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to mesa in Ubuntu. https://bugs.launchpad.net/bugs/1821863 Title: Need to add Intel CML related pci-id's Status in libdrm package in Ubuntu: Fix Released Status in linux package in Ubuntu: Fix Released Status in linux-oem package in Ubuntu: Fix Released Status in mesa package in Ubuntu: Fix Released Status in xorg-server package in Ubuntu: Fix Released Status in libdrm source package in Bionic: Fix Released Status in linux source package in Bionic: Invalid Status in linux-oem source package in Bionic: Fix Released Status in mesa source package in Bionic: Fix Released Status in xorg-server source package in Bionic: Fix Released Status in libdrm source package in Disco: Fix Released Status in linux source package in Disco: Fix Released Status in linux-oem source package in Disco: Fix Released Status in mesa source package in Disco: Fix Released Status in xorg-server source package in Disco: Fix Released Bug description: [Impact] Please make it happen in the coming oem-kernel as there will be a flood of Intel Comet Lake (CML) platforms that would need it. Thank you. The same is needed for the rest of the stack. CML is basically another iteration of Skylake/Kabylake/Coffee Lake, and doesn't need other changes than pci-id's and support for the PCH (similar to Cannon point, already supported by the kernel). [Test case] Test that i915 graphics works on CML. [Regression potential] None really, these only add a bunch of new pci-id's across the stack. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libdrm/+bug/1821863/+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 1831498] Re: radeonsi: GTK elements become invisible in some applications (GIMP, LibreOffice)
This bug was fixed in the package mesa - 19.0.2-1ubuntu1.1~18.04.1 --- mesa (19.0.2-1ubuntu1.1~18.04.1) bionic; urgency=medium * Backport to bionic. mesa (19.0.2-1ubuntu1.1) disco; urgency=medium * radeon-rework-gfx9-scissor-workaround.diff: Fix invisible elements with GTK on Vega/Raven. (LP: #1831498) mesa (19.0.2-1ubuntu1~18.04.1) bionic; urgency=medium * Backport to bionic for 18.04.3 HWE stack update. (LP: #1824111) * control: Build-depend on libsensors4-dev. -- Timo Aaltonen Tue, 04 Jun 2019 00:10:13 +0300 ** Changed in: mesa (Ubuntu Bionic) Status: Fix Committed => Fix Released -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to mesa in Ubuntu. https://bugs.launchpad.net/bugs/1831498 Title: radeonsi: GTK elements become invisible in some applications (GIMP, LibreOffice) Status in mesa package in Ubuntu: Fix Released Status in mesa source package in Bionic: Fix Released Status in mesa source package in Disco: Fix Committed Bug description: [impact] imported from https://bugs.freedesktop.org/show_bug.cgi?id=110355 : "I am currently experiencing some issues with GTK elements (GtkMenuItem, GtkMenu) becoming invisible with GIMP and LibreOffice. I am currently using radeonsi+glamor and I'm on Arch Linux (x86_64). My hardware is a Ryzen 5 2400G APU with vega graphics." [test case] test that GIMP/Libreoffice work fine on AMD Vega/Raven [regression potential] the fix/workaround is already in mesa 19.0.4, shouldn't regress anything To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mesa/+bug/1831498/+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 1821863] Re: Need to add Intel CML related pci-id's
This bug was fixed in the package libdrm - 2.4.97-1ubuntu1~18.04.1 --- libdrm (2.4.97-1ubuntu1~18.04.1) bionic; urgency=medium * Backport to bionic for 18.04.3 HWE stack update. (LP: #1824111) -- Timo Aaltonen Wed, 10 Apr 2019 13:54:06 +0300 ** Changed in: libdrm (Ubuntu Bionic) Status: New => Fix Released -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to mesa in Ubuntu. https://bugs.launchpad.net/bugs/1821863 Title: Need to add Intel CML related pci-id's Status in libdrm package in Ubuntu: Fix Released Status in linux package in Ubuntu: Fix Released Status in linux-oem package in Ubuntu: Fix Released Status in mesa package in Ubuntu: Fix Released Status in xorg-server package in Ubuntu: Fix Released Status in libdrm source package in Bionic: Fix Released Status in linux source package in Bionic: Invalid Status in linux-oem source package in Bionic: Fix Released Status in mesa source package in Bionic: Fix Committed Status in xorg-server source package in Bionic: Fix Released Status in libdrm source package in Disco: Fix Released Status in linux source package in Disco: Fix Released Status in linux-oem source package in Disco: Fix Released Status in mesa source package in Disco: Fix Released Status in xorg-server source package in Disco: Fix Released Bug description: [Impact] Please make it happen in the coming oem-kernel as there will be a flood of Intel Comet Lake (CML) platforms that would need it. Thank you. The same is needed for the rest of the stack. CML is basically another iteration of Skylake/Kabylake/Coffee Lake, and doesn't need other changes than pci-id's and support for the PCH (similar to Cannon point, already supported by the kernel). [Test case] Test that i915 graphics works on CML. [Regression potential] None really, these only add a bunch of new pci-id's across the stack. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libdrm/+bug/1821863/+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 1824111] Re: Backport packages for 18.04.3 HWE stack
This bug was fixed in the package libclc - 0.2.0+git20190306-1~ubuntu18.04.1 --- libclc (0.2.0+git20190306-1~ubuntu18.04.1) bionic; urgency=medium * Backport to bionic for 18.04.3 HWE stack update. (LP: #1824111) -- Timo Aaltonen Wed, 10 Apr 2019 13:52:07 +0300 ** Changed in: xorg-server-hwe-18.04 (Ubuntu Bionic) Status: Fix Committed => Fix Released -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to mesa in Ubuntu. https://bugs.launchpad.net/bugs/1824111 Title: Backport packages for 18.04.3 HWE stack Status in OEM Priority Project: Confirmed Status in libclc package in Ubuntu: Invalid Status in libdrm package in Ubuntu: Invalid Status in llvm-toolchain-8 package in Ubuntu: Invalid Status in mesa package in Ubuntu: Invalid Status in libclc source package in Bionic: Fix Released Status in libdrm source package in Bionic: Fix Released Status in llvm-toolchain-8 source package in Bionic: Fix Released Status in mesa source package in Bionic: Fix Committed Status in xorg-server-hwe-18.04 source package in Bionic: Fix Released Status in xserver-xorg-video-amdgpu-hwe-18.04 source package in Bionic: Fix Released Status in xserver-xorg-video-ati-hwe-18.04 source package in Bionic: Fix Released Status in xserver-xorg-video-nouveau-hwe-18.04 source package in Bionic: Fix Released Bug description: [Impact] These are needed for 18.04.3 images. [Test case] Boot a daily image, see that it still has the necessary stack installed and working. Check upgrade from stock bionic. [Regression potential] libdrm: very minimal chance for regressions llvm-8: a new package, no regression potential on it's own libclc: more or less just adds support for new llvm mesa: a new major release, but we'll pull the final stable release of 19.0.x series, so there shouldn't be any regressions left at that point xserver: a new minor release xorg drivers: modest updates, mainly just new ati/amdgpu [Other info] To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/1824111/+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 1824111] Update Released
The verification of the Stable Release Update for llvm-toolchain-8 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 mesa in Ubuntu. https://bugs.launchpad.net/bugs/1824111 Title: Backport packages for 18.04.3 HWE stack Status in OEM Priority Project: Confirmed Status in libclc package in Ubuntu: Invalid Status in libdrm package in Ubuntu: Invalid Status in llvm-toolchain-8 package in Ubuntu: Invalid Status in mesa package in Ubuntu: Invalid Status in libclc source package in Bionic: Fix Released Status in libdrm source package in Bionic: Fix Released Status in llvm-toolchain-8 source package in Bionic: Fix Released Status in mesa source package in Bionic: Fix Committed Status in xorg-server-hwe-18.04 source package in Bionic: Fix Released Status in xserver-xorg-video-amdgpu-hwe-18.04 source package in Bionic: Fix Released Status in xserver-xorg-video-ati-hwe-18.04 source package in Bionic: Fix Released Status in xserver-xorg-video-nouveau-hwe-18.04 source package in Bionic: Fix Released Bug description: [Impact] These are needed for 18.04.3 images. [Test case] Boot a daily image, see that it still has the necessary stack installed and working. Check upgrade from stock bionic. [Regression potential] libdrm: very minimal chance for regressions llvm-8: a new package, no regression potential on it's own libclc: more or less just adds support for new llvm mesa: a new major release, but we'll pull the final stable release of 19.0.x series, so there shouldn't be any regressions left at that point xserver: a new minor release xorg drivers: modest updates, mainly just new ati/amdgpu [Other info] To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/1824111/+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 1824111] Re: Backport packages for 18.04.3 HWE stack
This bug was fixed in the package libdrm - 2.4.97-1ubuntu1~18.04.1 --- libdrm (2.4.97-1ubuntu1~18.04.1) bionic; urgency=medium * Backport to bionic for 18.04.3 HWE stack update. (LP: #1824111) -- Timo Aaltonen Wed, 10 Apr 2019 13:54:06 +0300 ** Changed in: libdrm (Ubuntu Bionic) Status: Fix Committed => Fix Released ** Changed in: libclc (Ubuntu Bionic) Status: Fix Committed => Fix Released -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to mesa in Ubuntu. https://bugs.launchpad.net/bugs/1824111 Title: Backport packages for 18.04.3 HWE stack Status in OEM Priority Project: Confirmed Status in libclc package in Ubuntu: Invalid Status in libdrm package in Ubuntu: Invalid Status in llvm-toolchain-8 package in Ubuntu: Invalid Status in mesa package in Ubuntu: Invalid Status in libclc source package in Bionic: Fix Released Status in libdrm source package in Bionic: Fix Released Status in llvm-toolchain-8 source package in Bionic: Fix Released Status in mesa source package in Bionic: Fix Committed Status in xorg-server-hwe-18.04 source package in Bionic: Fix Released Status in xserver-xorg-video-amdgpu-hwe-18.04 source package in Bionic: Fix Released Status in xserver-xorg-video-ati-hwe-18.04 source package in Bionic: Fix Released Status in xserver-xorg-video-nouveau-hwe-18.04 source package in Bionic: Fix Released Bug description: [Impact] These are needed for 18.04.3 images. [Test case] Boot a daily image, see that it still has the necessary stack installed and working. Check upgrade from stock bionic. [Regression potential] libdrm: very minimal chance for regressions llvm-8: a new package, no regression potential on it's own libclc: more or less just adds support for new llvm mesa: a new major release, but we'll pull the final stable release of 19.0.x series, so there shouldn't be any regressions left at that point xserver: a new minor release xorg drivers: modest updates, mainly just new ati/amdgpu [Other info] To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/1824111/+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 1824111] Re: Backport packages for 18.04.3 HWE stack
This bug was fixed in the package xorg-server-hwe-18.04 - 2:1.20.4-1ubuntu3~18.04.1 --- xorg-server-hwe-18.04 (2:1.20.4-1ubuntu3~18.04.1) bionic; urgency=medium * Backport for 18.04.3 HWE stack update. (LP: #1824111) -- Timo Aaltonen Thu, 02 May 2019 11:06:54 +0300 ** Changed in: xserver-xorg-video-nouveau-hwe-18.04 (Ubuntu Bionic) Status: Fix Committed => Fix Released -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to mesa in Ubuntu. https://bugs.launchpad.net/bugs/1824111 Title: Backport packages for 18.04.3 HWE stack Status in OEM Priority Project: Confirmed Status in libclc package in Ubuntu: Invalid Status in libdrm package in Ubuntu: Invalid Status in llvm-toolchain-8 package in Ubuntu: Invalid Status in mesa package in Ubuntu: Invalid Status in libclc source package in Bionic: Fix Released Status in libdrm source package in Bionic: Fix Released Status in llvm-toolchain-8 source package in Bionic: Fix Released Status in mesa source package in Bionic: Fix Committed Status in xorg-server-hwe-18.04 source package in Bionic: Fix Released Status in xserver-xorg-video-amdgpu-hwe-18.04 source package in Bionic: Fix Released Status in xserver-xorg-video-ati-hwe-18.04 source package in Bionic: Fix Released Status in xserver-xorg-video-nouveau-hwe-18.04 source package in Bionic: Fix Released Bug description: [Impact] These are needed for 18.04.3 images. [Test case] Boot a daily image, see that it still has the necessary stack installed and working. Check upgrade from stock bionic. [Regression potential] libdrm: very minimal chance for regressions llvm-8: a new package, no regression potential on it's own libclc: more or less just adds support for new llvm mesa: a new major release, but we'll pull the final stable release of 19.0.x series, so there shouldn't be any regressions left at that point xserver: a new minor release xorg drivers: modest updates, mainly just new ati/amdgpu [Other info] To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/1824111/+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 1824111] Re: Backport packages for 18.04.3 HWE stack
This bug was fixed in the package xserver-xorg-video-amdgpu-hwe-18.04 - 19.0.1-1~18.04.1 --- xserver-xorg-video-amdgpu-hwe-18.04 (19.0.1-1~18.04.1) bionic; urgency=medium * Backport for 18.04.3 HWE stack update. (LP: #1824111) -- Timo Aaltonen Wed, 29 May 2019 13:19:12 +0300 -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to mesa in Ubuntu. https://bugs.launchpad.net/bugs/1824111 Title: Backport packages for 18.04.3 HWE stack Status in OEM Priority Project: Confirmed Status in libclc package in Ubuntu: Invalid Status in libdrm package in Ubuntu: Invalid Status in llvm-toolchain-8 package in Ubuntu: Invalid Status in mesa package in Ubuntu: Invalid Status in libclc source package in Bionic: Fix Released Status in libdrm source package in Bionic: Fix Released Status in llvm-toolchain-8 source package in Bionic: Fix Released Status in mesa source package in Bionic: Fix Committed Status in xorg-server-hwe-18.04 source package in Bionic: Fix Released Status in xserver-xorg-video-amdgpu-hwe-18.04 source package in Bionic: Fix Released Status in xserver-xorg-video-ati-hwe-18.04 source package in Bionic: Fix Released Status in xserver-xorg-video-nouveau-hwe-18.04 source package in Bionic: Fix Released Bug description: [Impact] These are needed for 18.04.3 images. [Test case] Boot a daily image, see that it still has the necessary stack installed and working. Check upgrade from stock bionic. [Regression potential] libdrm: very minimal chance for regressions llvm-8: a new package, no regression potential on it's own libclc: more or less just adds support for new llvm mesa: a new major release, but we'll pull the final stable release of 19.0.x series, so there shouldn't be any regressions left at that point xserver: a new minor release xorg drivers: modest updates, mainly just new ati/amdgpu [Other info] To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/1824111/+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 1824111] Re: Backport packages for 18.04.3 HWE stack
This bug was fixed in the package xserver-xorg-video-nouveau-hwe-18.04 - 1:1.0.16-1~18.04.1 --- xserver-xorg-video-nouveau-hwe-18.04 (1:1.0.16-1~18.04.1) bionic; urgency=medium * Backport for 18.04.3 HWE stack update. (LP: #1824111) -- Timo Aaltonen Wed, 29 May 2019 13:19:20 +0300 ** Changed in: xserver-xorg-video-ati-hwe-18.04 (Ubuntu Bionic) Status: Fix Committed => Fix Released -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to mesa in Ubuntu. https://bugs.launchpad.net/bugs/1824111 Title: Backport packages for 18.04.3 HWE stack Status in OEM Priority Project: Confirmed Status in libclc package in Ubuntu: Invalid Status in libdrm package in Ubuntu: Invalid Status in llvm-toolchain-8 package in Ubuntu: Invalid Status in mesa package in Ubuntu: Invalid Status in libclc source package in Bionic: Fix Released Status in libdrm source package in Bionic: Fix Released Status in llvm-toolchain-8 source package in Bionic: Fix Released Status in mesa source package in Bionic: Fix Committed Status in xorg-server-hwe-18.04 source package in Bionic: Fix Released Status in xserver-xorg-video-amdgpu-hwe-18.04 source package in Bionic: Fix Released Status in xserver-xorg-video-ati-hwe-18.04 source package in Bionic: Fix Released Status in xserver-xorg-video-nouveau-hwe-18.04 source package in Bionic: Fix Released Bug description: [Impact] These are needed for 18.04.3 images. [Test case] Boot a daily image, see that it still has the necessary stack installed and working. Check upgrade from stock bionic. [Regression potential] libdrm: very minimal chance for regressions llvm-8: a new package, no regression potential on it's own libclc: more or less just adds support for new llvm mesa: a new major release, but we'll pull the final stable release of 19.0.x series, so there shouldn't be any regressions left at that point xserver: a new minor release xorg drivers: modest updates, mainly just new ati/amdgpu [Other info] To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/1824111/+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 1824111] Re: Backport packages for 18.04.3 HWE stack
This bug was fixed in the package xserver-xorg-video-ati-hwe-18.04 - 1:19.0.1-0ubuntu1~18.04.1 --- xserver-xorg-video-ati-hwe-18.04 (1:19.0.1-0ubuntu1~18.04.1) bionic; urgency=medium * Backport for 18.04.3 HWE stack update. (LP: #1824111) -- Timo Aaltonen Wed, 29 May 2019 13:19:14 +0300 ** Changed in: xserver-xorg-video-amdgpu-hwe-18.04 (Ubuntu Bionic) Status: Fix Committed => Fix Released -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to mesa in Ubuntu. https://bugs.launchpad.net/bugs/1824111 Title: Backport packages for 18.04.3 HWE stack Status in OEM Priority Project: Confirmed Status in libclc package in Ubuntu: Invalid Status in libdrm package in Ubuntu: Invalid Status in llvm-toolchain-8 package in Ubuntu: Invalid Status in mesa package in Ubuntu: Invalid Status in libclc source package in Bionic: Fix Released Status in libdrm source package in Bionic: Fix Released Status in llvm-toolchain-8 source package in Bionic: Fix Released Status in mesa source package in Bionic: Fix Committed Status in xorg-server-hwe-18.04 source package in Bionic: Fix Released Status in xserver-xorg-video-amdgpu-hwe-18.04 source package in Bionic: Fix Released Status in xserver-xorg-video-ati-hwe-18.04 source package in Bionic: Fix Released Status in xserver-xorg-video-nouveau-hwe-18.04 source package in Bionic: Fix Released Bug description: [Impact] These are needed for 18.04.3 images. [Test case] Boot a daily image, see that it still has the necessary stack installed and working. Check upgrade from stock bionic. [Regression potential] libdrm: very minimal chance for regressions llvm-8: a new package, no regression potential on it's own libclc: more or less just adds support for new llvm mesa: a new major release, but we'll pull the final stable release of 19.0.x series, so there shouldn't be any regressions left at that point xserver: a new minor release xorg drivers: modest updates, mainly just new ati/amdgpu [Other info] To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/1824111/+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 1834226] Re: update-notifier doesn't respect "automatically check for updates: Never"
This continues to happen, more aggressively on 19.04 than on previous versions. This system popped up with updates today has been running 19.04 the longest of all my systems with "never" as the selected option and it just keeps checking for updates. I've got two processes seemingly related, one was started by init 14921 1 0 08:37 tty2 00:00:15 /usr/bin/python3 /usr/bin/update- manager --no-update --no-focus-on-map The other must be the gui who has the gnome-session-binary as the parent process 2351 1704 0 08:28 tty2 00:00:00 update-notifier -- 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/1834226 Title: update-notifier doesn't respect "automatically check for updates: Never" Status in software-properties package in Ubuntu: New Bug description: This has been a long-standing problem with various ubuntu installations, and I'm sensing some reticence in doing anything about it. This attitude also seems to be purposeful to try to cajole updates on people who make bad choices due to confusion/fud/paranoia. apt install fails due to: E: Could not get lock /var/lib/dpkg/lock-frontend - open (11: Resource temporarily unavailable) E: Unable to acquire the dpkg frontend lock (/var/lib/dpkg/lock-frontend), is another process using it? A great deal of networking is taking place despite setting automatic upgrades to "never". Cycling this doesn't seem to do anything. This action is hostile to programmers and the setting should be respected. Wisdom on threads is to let it update until it's out of updates, and then it supposedly respects the "never" flag, but the experience I'm having is much more non-deterministic. have been using 19.04 for weeks now and still get the background notifier using data and getting in the way of aptitude package installations. I prefer manual update && upgrade once my code is ready to push. Is there another way around this or are people just living with it? To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/software-properties/+bug/1834226/+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 1831498] Update Released
The verification of the Stable Release Update for mesa 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 mesa in Ubuntu. https://bugs.launchpad.net/bugs/1831498 Title: radeonsi: GTK elements become invisible in some applications (GIMP, LibreOffice) Status in mesa package in Ubuntu: Fix Released Status in mesa source package in Bionic: Fix Committed Status in mesa source package in Disco: Fix Committed Bug description: [impact] imported from https://bugs.freedesktop.org/show_bug.cgi?id=110355 : "I am currently experiencing some issues with GTK elements (GtkMenuItem, GtkMenu) becoming invisible with GIMP and LibreOffice. I am currently using radeonsi+glamor and I'm on Arch Linux (x86_64). My hardware is a Ryzen 5 2400G APU with vega graphics." [test case] test that GIMP/Libreoffice work fine on AMD Vega/Raven [regression potential] the fix/workaround is already in mesa 19.0.4, shouldn't regress anything To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mesa/+bug/1831498/+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 1824111] Re: Backport packages for 18.04.3 HWE stack
This bug was fixed in the package llvm-toolchain-8 - 1:8-3~ubuntu18.04.1 --- llvm-toolchain-8 (1:8-3~ubuntu18.04.1) bionic; urgency=medium * Backport to bionic for 18.04.3 HWE stack update. (LP: #1824111) -- Timo Aaltonen Wed, 10 Apr 2019 11:46:43 +0300 ** Changed in: llvm-toolchain-8 (Ubuntu Bionic) Status: Fix Committed => Fix Released -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to mesa in Ubuntu. https://bugs.launchpad.net/bugs/1824111 Title: Backport packages for 18.04.3 HWE stack Status in OEM Priority Project: Confirmed Status in libclc package in Ubuntu: Invalid Status in libdrm package in Ubuntu: Invalid Status in llvm-toolchain-8 package in Ubuntu: Invalid Status in mesa package in Ubuntu: Invalid Status in libclc source package in Bionic: Fix Released Status in libdrm source package in Bionic: Fix Released Status in llvm-toolchain-8 source package in Bionic: Fix Released Status in mesa source package in Bionic: Fix Committed Status in xorg-server-hwe-18.04 source package in Bionic: Fix Released Status in xserver-xorg-video-amdgpu-hwe-18.04 source package in Bionic: Fix Released Status in xserver-xorg-video-ati-hwe-18.04 source package in Bionic: Fix Released Status in xserver-xorg-video-nouveau-hwe-18.04 source package in Bionic: Fix Released Bug description: [Impact] These are needed for 18.04.3 images. [Test case] Boot a daily image, see that it still has the necessary stack installed and working. Check upgrade from stock bionic. [Regression potential] libdrm: very minimal chance for regressions llvm-8: a new package, no regression potential on it's own libclc: more or less just adds support for new llvm mesa: a new major release, but we'll pull the final stable release of 19.0.x series, so there shouldn't be any regressions left at that point xserver: a new minor release xorg drivers: modest updates, mainly just new ati/amdgpu [Other info] To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/1824111/+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 1727202] Re: [17.10 regression] AppArmor ntp denial: Failed name lookup - disconnected path
With chrony taking over for ntpd and the usage of openntpd dropping next to none this really became less and less important over time. It is fixed in ntpd and not affecting chrony. For openntp it seems to be an issue but we wait for a reply to comment #34 as far as I read through the updates. Updating tasks to reflect that. ** Changed in: openntpd (Ubuntu) Status: Confirmed => Incomplete ** Changed in: openntpd (Ubuntu Bionic) Status: Confirmed => Won't Fix ** Changed in: openntpd (Ubuntu) Importance: Undecided => Low ** Tags removed: server-next -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to ntp in Ubuntu. https://bugs.launchpad.net/bugs/1727202 Title: [17.10 regression] AppArmor ntp denial: Failed name lookup - disconnected path Status in ntp package in Ubuntu: Fix Released Status in openntpd package in Ubuntu: Incomplete Status in ntp source package in Artful: Fix Released Status in openntpd source package in Artful: Won't Fix Status in ntp source package in Bionic: Fix Released Status in openntpd source package in Bionic: Won't Fix Bug description: [Impact] * NTP has new isolation features which makes it trigger apparmor issues. * Those apparmor issues not only clutter the log and make other things less readable, they also prevent ntp from reporting its actual messages. * Fix is opening the apparmor profile to follow ntp through the disconnect by the isolation feature. [Test Case] * This is hard to trigger, but then also not. Which means it is not entirely sorted out when it triggers and when not, but the following does trigger it in tests of Pitti and also mine (while at the same time sometimes it does not - mabye I had other guests or kvm instead of lxd) * First install ntp in Artful (or above unless fixed) * Install ntp and check demsg for denies * Once an issue triggers instead of the error in syslog you'll see the apparmor Deny like: apparmor="DENIED" operation="sendmsg" info="Failed name lookup - disconnected path" error=-13 profile="/usr/sbin/ntpd" name="run/systemd/journal/dev-log" pid=5600 comm="ntpd" requested_mask="w" denied_mask="w" fsuid=0 ouid=0 [Regression Potential] * We are slightly opening up the apparmor profile which is far lower risk than adding more constraints. So safe from that POV. * OTOH one could think this might be a security issue, but in fact this isn't a new suggestion if you take a look at [1] with an ack by Seth of the Security Team. [Other Info] * n/a [1]: https://lists.ubuntu.com/archives/apparmor/2015-May/007858.html Merely installing and starting ntp.service in Ubuntu 17.10 now causes this AppArmor violation: audit: type=1400 audit(1508915894.215:25): apparmor="DENIED" operation="sendmsg" info="Failed name lookup - disconnected path" error=-13 profile="/usr/sbin/ntpd" name="run/systemd/journal/dev-log" pid=5600 comm="ntpd" requested_mask="w" denied_mask="w" fsuid=0 ouid=0 (many times). This hasn't happened in earlier Ubuntu releases yet. This was spotted by Cockpit's integration tests, as our "ubuntu- stable" image now moved to 17.10 after its release. ProblemType: Bug DistroRelease: Ubuntu 17.10 Package: ntp 1:4.2.8p10+dfsg-5ubuntu3 ProcVersionSignature: Ubuntu 4.13.0-16.19-generic 4.13.4 Uname: Linux 4.13.0-16-generic x86_64 ApportVersion: 2.20.7-0ubuntu3 Architecture: amd64 Date: Wed Oct 25 03:19:34 2017 SourcePackage: ntp UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ntp/+bug/1727202/+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 1778073] Re: dnsmasq and resolvconf hangs on start
** Tags removed: server-next -- 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/1778073 Title: dnsmasq and resolvconf hangs on start Status in dnsmasq package in Ubuntu: Incomplete Status in dnsmasq package in Debian: New Bug description: I installed today dnsmasq and I use resolvconf in background. Problem is, that systemd takes 1 minute or so after service start and than reports: root@proxy:~# service dnsmasq status dnsmasq.service - dnsmasq - A lightweight DHCP and caching DNS server Loaded: loaded (/lib/systemd/system/dnsmasq.service; enabled; vendor preset: enabled) Drop-In: /run/systemd/generator/dnsmasq.service.d 50-dnsmasq-$named.conf, 50-insserv.conf-$named.conf Active: failed (Result: timeout) since Do 2018-06-21 15:58:13 CEST; 2min 10s ago Process: 3295 ExecStop=/etc/init.d/dnsmasq systemd-stop-resolvconf (code=killed, signal=TERM) Process: 3865 ExecStartPost=/etc/init.d/dnsmasq systemd-start-resolvconf (code=killed, signal=TERM) Process: 3837 ExecStart=/etc/init.d/dnsmasq systemd-exec (code=exited, status=0/SUCCESS) Process: 3825 ExecStartPre=/usr/sbin/dnsmasq --test (code=exited, status=0/SUCCESS) Main PID: 3862 (code=exited, status=0/SUCCESS) Jun 21 15:56:43 proxy dnsmasq[3862]: Benutze Namensserver 192.168.23.1#53 Jun 21 15:56:43 proxy dnsmasq[3865]: * Awakening mail retriever agent: Jun 21 15:56:43 proxy dnsmasq[3865]:...done. Jun 21 15:56:43 proxy postfix[3951]: Postfix is running with backwards-compatible default settings Jun 21 15:56:43 proxy postfix[3951]: See http://www.postfix.org/COMPATIBILITY_README.html for details Jun 21 15:56:43 proxy postfix[3951]: To disable backwards compatibility use "postconf compatibility_level=2" and "postfix reload" Jun 21 15:58:13 proxy systemd[1]: dnsmasq.service: Start-post operation timed out. Stopping. Jun 21 15:58:13 proxy systemd[1]: Failed to start dnsmasq - A lightweight DHCP and caching DNS server. Jun 21 15:58:13 proxy systemd[1]: dnsmasq.service: Unit entered failed state. Jun 21 15:58:13 proxy systemd[1]: dnsmasq.service: Failed with result 'timeout'. when I look into the start script /etc/init.d/dnsmasq there is a func systemd-start-resolvconf which points to start-resolvconf. There is this part: for interface in $DNSMASQ_EXCEPT do [ $interface = lo ] && return done Before I had not defined DNSMASQ_EXCEPT in /etc/defaults/dnsmasq. Problem is, that this part MUST be faulty! When I commend it out, I can start dnsmasq! It looks like it loops forever there?! Also if I define DNSMASQ_EXCEPT to my listen interface, it works - but is is really needed? I found a other user which had the same problem: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=871958 ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: dnsmasq 2.75-1ubuntu0.16.04.4 [modified: etc/default/dnsmasq] ProcVersionSignature: Ubuntu 4.15.0-23.25~16.04.1-generic 4.15.18 Uname: Linux 4.15.0-23-generic x86_64 ApportVersion: 2.20.1-0ubuntu2.18 Architecture: amd64 Date: Thu Jun 21 16:12:14 2018 InstallationDate: Installed on 2017-02-27 (479 days ago) InstallationMedia: Ubuntu-Server 16.04.2 LTS "Xenial Xerus" - Release amd64 (20170215.8) PackageArchitecture: all ProcEnviron: TERM=xterm SHELL=/bin/bash PATH=(custom, no user) LANG=de_DE.UTF-8 SourcePackage: dnsmasq UpgradeStatus: No upgrade log present (probably fresh install) mtime.conffile..etc.default.dnsmasq: 2018-06-21T16:07:24.818774 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/dnsmasq/+bug/1778073/+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 1821625] Re: systemd 237-3ubuntu10.14 ADT test failure on Bionic ppc64el (test-seccomp)
This bug is awaiting verification that the kernel in -proposed solves
the problem. Please test the kernel and update this bug with the
results. If the problem is solved, change the tag 'verification-needed-
bionic' to 'verification-done-bionic'. If the problem still exists,
change the tag 'verification-needed-bionic' to 'verification-failed-
bionic'.
If verification is not done by 5 working days from today, this fix will
be dropped from the source code, and this bug will be closed.
See https://wiki.ubuntu.com/Testing/EnableProposed for documentation how
to enable and use -proposed. Thank you!
** Tags added: verification-needed-bionic
--
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/1821625
Title:
systemd 237-3ubuntu10.14 ADT test failure on Bionic ppc64el (test-
seccomp)
Status in libseccomp package in Ubuntu:
Incomplete
Status in linux package in Ubuntu:
Fix Released
Status in systemd package in Ubuntu:
Invalid
Status in libseccomp source package in Bionic:
Incomplete
Status in linux source package in Bionic:
Fix Committed
Status in systemd source package in Bionic:
Invalid
Bug description:
Starting with systemd 237-3ubuntu10.14, the testcase test-seccomp is
failing on Bionic on ppc64el with the error messages:
Operating on architecture: ppc
Failed to add n/a() rule for architecture ppc, skipping: Bad address
Operating on architecture: ppc64
Failed to add n/a() rule for architecture ppc64, skipping: Bad address
Operating on architecture: ppc64-le
Failed to add n/a() rule for architecture ppc64-le, skipping: Numerical
argument out of domain
Assertion 'p == MAP_FAILED' failed at ../src/test/test-seccomp.c:413,
function test_memory_deny_write_execute_mmap(). Aborting.
memoryseccomp-mmap terminated by signal ABRT.
Assertion 'wait_for_terminate_and_check("memoryseccomp-mmap", pid, WAIT_LOG)
== EXIT_SUCCESS' failed at ../src/test/test-seccomp.c:427, function
test_memory_deny_write_execute_mmap(). Aborting.
Aborted (core dumped)
FAIL: test-seccomp (code: 134)
Full logs at:
https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac/autopkgtest-bionic/bionic/ppc64el/s/systemd/20190302_025135_d0e38@/log.gz
The testcase passed with systemd version 237-3ubuntu10.13 running on the same
4.15.0-45 kernel on ppc64el:
https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac/autopkgtest-bionic/bionic/ppc64el/s/systemd/20190228_154406_6b12f@/log.gz
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/libseccomp/+bug/1821625/+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 1833231] Re: cups ftbfs in eoan (amd64 only)
Is this still relevant? According to https://launchpad.net/ubuntu/+source/cups/2.2.10-6ubuntu1 the CUPS 2.2.10-6ubuntu1 package has built on all platforms. ** Changed in: cups (Ubuntu) Status: New => Incomplete -- 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/1833231 Title: cups ftbfs in eoan (amd64 only) Status in cups package in Ubuntu: Incomplete Bug description: cups ftbfs in eoan (amd64 only) in a test rebuild: https://launchpadlibrarian.net/428250411/buildlog_ubuntu-eoan- amd64.cups_2.2.10-6ubuntu1_BUILDING.txt.gz E [14/Jun/2019:14:46:57.037970 +] Unknown default SystemGroup "lpadmin". PASS: 8 warning messages. PASS: 0 notice messages. PASS: 760 info messages. PASS: 24065 debug messages. PASS: 25573 debug2 messages. Copied log file "access_log-2019-06-14-buildd" to test directory. Copied log file "debug_log-2019-06-14-buildd" to test directory. Copied log file "error_log-2019-06-14-buildd" to test directory. Copied log file "page_log-2019-06-14-buildd" to test directory. Copied report file "cups-str-2019-06-14-buildd.html" to test directory. 1 tests failed. make[2]: *** [Makefile:257: check] Error 1 make[2]: Leaving directory '/<>' make[1]: *** [debian/rules:201: override_dh_auto_test] Error 2 make[1]: Leaving directory '/<>' make: *** [debian/rules:17: build] Error 2 dpkg-buildpackage: error: debian/rules build subprocess returned exit status 2 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/cups/+bug/1833231/+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 1835135] Re: FIPS OpenSSL crashes Python2 hashlib
Thanks for bringing this up. The FIPS team is aware of it and will address this. ** Changed in: python2.7 (Ubuntu) Status: New => Triaged ** Changed in: python2.7 (Ubuntu) Importance: Undecided => High -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to python2.7 in Ubuntu. https://bugs.launchpad.net/bugs/1835135 Title: FIPS OpenSSL crashes Python2 hashlib Status in python2.7 package in Ubuntu: Triaged Bug description: If Ubuntu/Canonical's FIPS-compliant OpenSSL is initialized with SSL_library_init, then Python2's hashlib bindings for MD5 can trigger a SIGSEGV via a NULL pointer dereference (if calling the .update method) or a SIGABRT (if passing input to the constructor or passing no input and invoking the .final method). This happens if, for example, PyOpenSSL is imported before hashlib. Canonical's FIPS patches for OpenSSL introduce some odd behavior that arguably should be revisited, but the (TL;DR) core bug is that Python2 hashlib doesn't properly check the return value of EVP_DigestInit, preventing hashlib from falling back to it's internal MD5 implementation and instead setting things up for use of the MD5 context to trigger SIGSEGV or SIGABRT. Python3 correctly checks the return value, so the fix is to backport the relevant code into Python2 (see python2.7-2.7.12/Modules/_hashopenssl.c). See attached good.py and bad.py files which exhibit the import order- dependent crashing issue. See attached fips-md5-python-init-bug.c which shows the FIPS OpenSSL behaviors that conditionally tickle the Python2 bug. The C file also contains a much more detailed description of the Python2 bug and other behavior which I'd rather not repeat here. I discovered this bug investigating an issue with the third-party apt- boto-s3 package. See https://github.com/boto/boto3/issues/2021 Note that this bug effects Splunk, Inc, which has a corporate Ubuntu Advantage license. My login account is attached to a different, single-seat license. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/python2.7/+bug/1835135/+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 1831498] Re: radeonsi: GTK elements become invisible in some applications (GIMP, LibreOffice)
Verified on Kubuntu 18.04.2 64bit from the -proposed repository. Everything, including Gimp and LibreOffice, looks OK. Yay! ** 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 mesa in Ubuntu. https://bugs.launchpad.net/bugs/1831498 Title: radeonsi: GTK elements become invisible in some applications (GIMP, LibreOffice) Status in mesa package in Ubuntu: Fix Released Status in mesa source package in Bionic: Fix Committed Status in mesa source package in Disco: Fix Committed Bug description: [impact] imported from https://bugs.freedesktop.org/show_bug.cgi?id=110355 : "I am currently experiencing some issues with GTK elements (GtkMenuItem, GtkMenu) becoming invisible with GIMP and LibreOffice. I am currently using radeonsi+glamor and I'm on Arch Linux (x86_64). My hardware is a Ryzen 5 2400G APU with vega graphics." [test case] test that GIMP/Libreoffice work fine on AMD Vega/Raven [regression potential] the fix/workaround is already in mesa 19.0.4, shouldn't regress anything To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mesa/+bug/1831498/+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 1827417] Re: Ubuntu 16.04 - EMU10K1 / CT4832 lost ability to listen stereo on headphones - there is upmixed surround only.
** Changed in: linux (Ubuntu) Status: Expired => Incomplete ** Changed in: pulseaudio (Ubuntu) Status: Expired => Incomplete -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to pulseaudio in Ubuntu. https://bugs.launchpad.net/bugs/1827417 Title: Ubuntu 16.04 - EMU10K1 / CT4832 lost ability to listen stereo on headphones - there is upmixed surround only. Status in linux package in Ubuntu: Incomplete Status in pulseaudio package in Ubuntu: Incomplete Bug description: Hello, I have a problem - after one of the updates (sorry for being not precise - I can only track it back to the time I have been surely listening something on headphones - it has to be beginning of this year because last time I have been listening more on my SB Live for sure was in last one-two weeks of February 2019 - I have suddenly lost "stereo" on my headphones. I have speakers connected to on-board sound card and headphones connected to SB Live Value for few years, so I did not mess with outputs or something - one day I changed Audacious output to SbLive in pavucontrol (as usually) and that time the sound was weirdly filtered. I have found that this must be "surround upmix" which I do not need and tried to disable it, enable-remixing = no and the same for "LFE remixing" in /etc/pulse/daemon.conf did not work. It does not matter what configuration I choose in pavucontrol- analog stereo duplex, "analog stereo output", "Analog surround 5.1" or 4.1 - for all "Analog output" scenarios the output is the same except for "mono" (no sound at all). I have tried do "skip" pulseaudio choosing "ALSA" output in Audacious + the alsa configuration for stereo but the upmix is still present. I have followed the old thread in Launchpad Answers: https://answers.launchpad.net/ubuntu/+source/alsa-driver/+question/169428 = Hello, i'm on ubuntu 16.04LTS (AMD64, with emu10k1 based soundcard) and since the last update I have similar problem - I have lost ability to listen stereo music on my Soundblaster Live Value (i use earphones). Even system sounds , web browser content and mp3 files are up-mixed. Few days ago it was no problem to choose "analag stereo output" in pavucontrol, now it seems that at this output have rear surround channel only (as I suppose, there is "stereo" but vocals are like heard from the other room and there is sometimes reverb as in the bathroom) :/. I had tried adding "set enable-remixing=no" in both /etc/pulse/daemon.conf and in the home directory configuration file without success. I have purged pulseaudio but with the ALSA there is the same problem, I have tried purging alsa and reinstalling without effect. So i thought that it can be emu10k1 driver specific, after digging in the network for solutions I have had tried adding "hint.emu10kx.0.multichannel_disabled " to the module configuration file without visible (or rather soundible ;) effect. I have tried to check EMU10K1 configuration with aweset, but it gives error message, so maybe the bad magic sits somewhere around? aweset /dev/sequencer: No such file or directory Once again - everything worked fine until the last update. I use xubuntu desktop as my machine is quite old, in despair I have installed unity to find the sound settings / speaker configuration etc and button to "disable all effects" as I have seen somewhere, but there were no such options. Help me Obi Wan Kenobi, you're my only hope... = I have next tried to follow the path from ubuntu sound troubleshooting guide, I have purged everything, installed back and now I'm here again with this "upmix" on SBLive! Value. Thanks in advance for help :) Tom --- ApportVersion: 2.20.1-0ubuntu2.18 Architecture: amd64 CurrentDesktop: XFCE DistroRelease: Ubuntu 16.04 HibernationDevice: RESUME=UUID=654027ee-6ab0-41ba-8537-452da07cda0e InstallationDate: Installed on 2011-10-07 (2765 days ago) InstallationMedia: Ubuntu 10.04.3 LTS "Lucid Lynx" - Release amd64 (20110720.1) IwConfig: lono wireless extensions. lxcbr0no wireless extensions. eth0 no wireless extensions. MachineType: Gigabyte Technology Co., Ltd. M68MT-S2 Package: pulseaudio 1:8.0-0ubuntu3.10 PackageArchitecture: amd64 ProcFB: 0 nouveaufb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-146-generic root=UUID=4559c496-f083-41a2-ad7c-1e03334389fd ro plymouth usbcore.autosuspend=-1 ProcVersionSignature: Ubuntu 4.4.0-146.172-generic 4.4.177 RelatedPackageVersions: linux-restricted-modules-4.4.0-146-generic N/A linux-backports-modules-4.4.0-146-generic N/A linux-firmware 1.157.21 RfKill: Tags: xenial third-party-packages xenial Uname: Linux 4.4.0-146-generic x86_64 UpgradeS
Re: [Touch-packages] [Bug 1827417] Re: Ubuntu 16.04 - EMU10K1 / CT4832 lost ability to listen stereo on headphones - there is upmixed surround only.
Hello, thank You for reply, I can try with new compilation during weekend, but as my machine is quite old can I try with one of the older /lighter/ LTS desktop (or would it be nonsense in case of this issue)? I.e Lubuntu 16.04 or Xubuntu 16.04 ? Best Regards Tomasz Grabarczyk On 7/3/19 7:41 AM, Kai-Heng Feng wrote: > Sorry for the late reply. > > Have you tried latest latest Ubuntu ISO? > http://cdimages.ubuntu.com/daily-live/current/ > -- 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/1827417 Title: Ubuntu 16.04 - EMU10K1 / CT4832 lost ability to listen stereo on headphones - there is upmixed surround only. Status in linux package in Ubuntu: Expired Status in pulseaudio package in Ubuntu: Expired Bug description: Hello, I have a problem - after one of the updates (sorry for being not precise - I can only track it back to the time I have been surely listening something on headphones - it has to be beginning of this year because last time I have been listening more on my SB Live for sure was in last one-two weeks of February 2019 - I have suddenly lost "stereo" on my headphones. I have speakers connected to on-board sound card and headphones connected to SB Live Value for few years, so I did not mess with outputs or something - one day I changed Audacious output to SbLive in pavucontrol (as usually) and that time the sound was weirdly filtered. I have found that this must be "surround upmix" which I do not need and tried to disable it, enable-remixing = no and the same for "LFE remixing" in /etc/pulse/daemon.conf did not work. It does not matter what configuration I choose in pavucontrol- analog stereo duplex, "analog stereo output", "Analog surround 5.1" or 4.1 - for all "Analog output" scenarios the output is the same except for "mono" (no sound at all). I have tried do "skip" pulseaudio choosing "ALSA" output in Audacious + the alsa configuration for stereo but the upmix is still present. I have followed the old thread in Launchpad Answers: https://answers.launchpad.net/ubuntu/+source/alsa-driver/+question/169428 = Hello, i'm on ubuntu 16.04LTS (AMD64, with emu10k1 based soundcard) and since the last update I have similar problem - I have lost ability to listen stereo music on my Soundblaster Live Value (i use earphones). Even system sounds , web browser content and mp3 files are up-mixed. Few days ago it was no problem to choose "analag stereo output" in pavucontrol, now it seems that at this output have rear surround channel only (as I suppose, there is "stereo" but vocals are like heard from the other room and there is sometimes reverb as in the bathroom) :/. I had tried adding "set enable-remixing=no" in both /etc/pulse/daemon.conf and in the home directory configuration file without success. I have purged pulseaudio but with the ALSA there is the same problem, I have tried purging alsa and reinstalling without effect. So i thought that it can be emu10k1 driver specific, after digging in the network for solutions I have had tried adding "hint.emu10kx.0.multichannel_disabled " to the module configuration file without visible (or rather soundible ;) effect. I have tried to check EMU10K1 configuration with aweset, but it gives error message, so maybe the bad magic sits somewhere around? aweset /dev/sequencer: No such file or directory Once again - everything worked fine until the last update. I use xubuntu desktop as my machine is quite old, in despair I have installed unity to find the sound settings / speaker configuration etc and button to "disable all effects" as I have seen somewhere, but there were no such options. Help me Obi Wan Kenobi, you're my only hope... = I have next tried to follow the path from ubuntu sound troubleshooting guide, I have purged everything, installed back and now I'm here again with this "upmix" on SBLive! Value. Thanks in advance for help :) Tom --- ApportVersion: 2.20.1-0ubuntu2.18 Architecture: amd64 CurrentDesktop: XFCE DistroRelease: Ubuntu 16.04 HibernationDevice: RESUME=UUID=654027ee-6ab0-41ba-8537-452da07cda0e InstallationDate: Installed on 2011-10-07 (2765 days ago) InstallationMedia: Ubuntu 10.04.3 LTS "Lucid Lynx" - Release amd64 (20110720.1) IwConfig: lono wireless extensions. lxcbr0no wireless extensions. eth0 no wireless extensions. MachineType: Gigabyte Technology Co., Ltd. M68MT-S2 Package: pulseaudio 1:8.0-0ubuntu3.10 PackageArchitecture: amd64 ProcFB: 0 nouveaufb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-146-generic root=UUID=4559c496-f083-41a2-ad7c-1e03334389fd ro plymouth usbcore.autosuspend=-1 ProcVersionSignature: Ubuntu 4.4.0-146.172-gen
