[Touch-packages] [Bug 1836301] Re: package base-files 9.4ubuntu4.9 failed to install/upgrade: subprocess installed post-installation script returned error exit status 127
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: base-files (Ubuntu) Status: New => Confirmed -- 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/1836301 Title: package base-files 9.4ubuntu4.9 failed to install/upgrade: subprocess installed post-installation script returned error exit status 127 Status in base-files package in Ubuntu: Confirmed Bug description: Update failed ProblemType: Package DistroRelease: Ubuntu 16.04 Package: base-files 9.4ubuntu4.9 ProcVersionSignature: Ubuntu 4.4.0-88.111-generic 4.4.76 Uname: Linux 4.4.0-88-generic i686 ApportVersion: 2.20.1-0ubuntu2.19 Architecture: i386 Date: Fri Jul 12 07:35:11 2019 Dependencies: DuplicateSignature: package:base-files:9.4ubuntu4.9 Setting up base-files (9.4ubuntu4.9) ... /var/lib/dpkg/info/base-files.postinst: 131: /var/lib/dpkg/info/base-files.postinst: Automatically: not found dpkg: error processing package base-files (--configure): subprocess installed post-installation script returned error exit status 127 ErrorMessage: subprocess installed post-installation script returned error exit status 127 InstallationDate: Installed on 2012-04-28 (2630 days ago) InstallationMedia: Ubuntu 12.04 LTS "Precise Pangolin" - Release i386 (20120423) RelatedPackageVersions: dpkg 1.18.4ubuntu1.5 apt 1.2.32 SourcePackage: base-files Title: package base-files 9.4ubuntu4.9 failed to install/upgrade: subprocess installed post-installation script returned error exit status 127 UpgradeStatus: Upgraded to xenial on 2017-04-19 (813 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/base-files/+bug/1836301/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1833476] Re: libssl1.1 version 1.1.1-1ubuntu2.1~18.04.2 breaks nginx ssl tests
After upgrade to OpenSSL 1.1.1 I get this err_ssl_version_interference error in chrome. running nginx -V I got this: nginx -V nginx version: nginx/1.14.0 (Ubuntu) built with OpenSSL 1.1.0g 2 Nov 2017 (running with OpenSSL 1.1.1 11 Sep 2018) TLS SNI support enabled so I don't know where the problem from. please see https://trac.nginx.org/nginx/ticket/1654 ** Bug watch added: trac.nginx.org/nginx/ #1654 http://trac.nginx.org/nginx/ticket/1654 -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to openssl in Ubuntu. https://bugs.launchpad.net/bugs/1833476 Title: libssl1.1 version 1.1.1-1ubuntu2.1~18.04.2 breaks nginx ssl tests Status in nginx package in Ubuntu: Incomplete Status in openssl package in Ubuntu: New Bug description: Many nginx ssl tests pass with libssl1.1 version 1.1.0g-2ubuntu4.3 but fail when libssl1.1 is updated to version 1.1.1-1ubuntu2.1~18.04.2. Repro steps: 1. Create control Dockerfile: == FROM ubuntu:18.04 RUN apt-get update -y && \ apt-get upgrade -y && \ apt-get install -y git nginx-core xdg-utils openssl=1.1.0g-2ubuntu4.3 libnet-ssleay-perl=1.84-1build1 libio-socket-ssl-perl=2.056-1 libssl1.1=1.1.0g-2ubuntu4.3 RUN git clone https://github.com/nginx/nginx-tests.git WORKDIR /nginx-tests ENV TEST_NGINX_BINARY=/usr/sbin/nginx ENV TEST_NGINX_MODULES=/usr/lib/nginx/modules USER www-data ENTRYPOINT ["prove", "."] == 2. Run the command in a directory with only the Dockerfile: docker build -t nginx_image . && docker run --rm -it nginx_image 3. See output: == Test Summary Report --- ./grpc_request_buffering.t (Wstat: 512 Tests: 14 Failed: 2) Failed tests: 11-12 Non-zero exit status: 2 ./h2_server_tokens.t (Wstat: 1536 Tests: 14 Failed: 6) Failed tests: 1-2, 7-8, 10-11 Non-zero exit status: 6 ./upstream_ip_hash_ipv6.t(Wstat: 512 Tests: 0 Failed: 0) Non-zero exit status: 2 Parse errors: No plan found in TAP output Files=346, Tests=3782, 317 wallclock secs ( 1.87 usr 0.78 sys + 35.84 cusr 16.99 csys = 55.48 CPU) Result: FAIL == 4. Create new Dockerfile (only difference is updating libssl1.1): == FROM ubuntu:18.04 RUN apt-get update -y && \ apt-get upgrade -y && \ apt-get install -y git nginx-core xdg-utils openssl=1.1.0g-2ubuntu4.3 libnet-ssleay-perl=1.84-1build1 libio-socket-ssl-perl=2.056-1 libssl1.1=1.1.1-1ubuntu2.1~18.04.2 RUN git clone https://github.com/nginx/nginx-tests.git WORKDIR /nginx-tests ENV TEST_NGINX_BINARY=/usr/sbin/nginx ENV TEST_NGINX_MODULES=/usr/lib/nginx/modules USER www-data ENTRYPOINT ["prove", "."] == 5. See output == Test Summary Report --- ./grpc_request_buffering.t (Wstat: 512 Tests: 14 Failed: 2) Failed tests: 11-12 Non-zero exit status: 2 ./h2_server_tokens.t (Wstat: 1536 Tests: 14 Failed: 6) Failed tests: 1-2, 7-8, 10-11 Non-zero exit status: 6 ./mail_ssl.t (Wstat: 768 Tests: 22 Failed: 3) Failed tests: 3, 5-6 Non-zero exit status: 3 ./proxy_ssl.t(Wstat: 512 Tests: 9 Failed: 2) Failed tests: 4-5 Non-zero exit status: 2 ./stream_proxy_ssl.t (Wstat: 512 Tests: 8 Failed: 2) Failed tests: 4-5 Non-zero exit status: 2 ./stream_ssl.t (Wstat: 768 Tests: 9 Failed: 3) Failed tests: 2, 4-5 Non-zero exit status: 3 ./stream_upstream_zone_ssl.t (Wstat: 768 Tests: 11 Failed: 3) Failed tests: 4-5, 9 Non-zero exit status: 3 ./upstream_ip_hash_ipv6.t(Wstat: 512 Tests: 0 Failed: 0) Non-zero exit status: 2 Parse errors: No plan found in TAP output ./upstream_zone_ssl.t(Wstat: 768 Tests: 11 Failed: 3) Failed tests: 4-5, 9 Non-zero exit status: 3 Files=346, Tests=3764, 317 wallclock secs ( 2.00 usr 0.73 sys + 36.49 cusr 16.91 csys = 56.13 CPU) Result: FAIL == New failures: mail_ssl.t, proxy_ssl.t, stream_proxy_ssl.t, stream_ssl.t, stream_upstream_zone_ssl.t, upstream_zone_ssl.t. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nginx/+bug/1833476/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad
[Touch-packages] [Bug 1836301] Re: package base-files 9.4ubuntu4.9 failed to install/upgrade: subprocess installed post-installation script returned error exit status 127
*** This bug is a duplicate of bug 1836236 *** https://bugs.launchpad.net/bugs/1836236 ** This bug has been marked a duplicate of bug 1836236 9.4ubuntu4.9: Broken package because of missing "#" @ /var/lib/dpkg/info/base-files.postinst +131 -- 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/1836301 Title: package base-files 9.4ubuntu4.9 failed to install/upgrade: subprocess installed post-installation script returned error exit status 127 Status in base-files package in Ubuntu: Confirmed Bug description: Update failed ProblemType: Package DistroRelease: Ubuntu 16.04 Package: base-files 9.4ubuntu4.9 ProcVersionSignature: Ubuntu 4.4.0-88.111-generic 4.4.76 Uname: Linux 4.4.0-88-generic i686 ApportVersion: 2.20.1-0ubuntu2.19 Architecture: i386 Date: Fri Jul 12 07:35:11 2019 Dependencies: DuplicateSignature: package:base-files:9.4ubuntu4.9 Setting up base-files (9.4ubuntu4.9) ... /var/lib/dpkg/info/base-files.postinst: 131: /var/lib/dpkg/info/base-files.postinst: Automatically: not found dpkg: error processing package base-files (--configure): subprocess installed post-installation script returned error exit status 127 ErrorMessage: subprocess installed post-installation script returned error exit status 127 InstallationDate: Installed on 2012-04-28 (2630 days ago) InstallationMedia: Ubuntu 12.04 LTS "Precise Pangolin" - Release i386 (20120423) RelatedPackageVersions: dpkg 1.18.4ubuntu1.5 apt 1.2.32 SourcePackage: base-files Title: package base-files 9.4ubuntu4.9 failed to install/upgrade: subprocess installed post-installation script returned error exit status 127 UpgradeStatus: Upgraded to xenial on 2017-04-19 (813 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/base-files/+bug/1836301/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1836328] [NEW] unattended-upgrades should not be enabled by default
Public bug reported: The unattended-upgrades package and the whole concept of upgrading software automatically behind user's back is HARMFUL and the service/timer should NOT be enabled by default. It harms experience even for novice users with applications like Firefox preventing opening links until you restart it (which is terribad if you're in the middle of some work and don't want to do that at THAT particular moment!), and some other applications crashing in some cases, especially applications that run sub-processes interactively or on timers/cronjobs -- where updates to their libs or other dependencies create error states due to version/API/ABI mismatches. Please do not enable the service/timer by default and leave it to advanced users to enable assuming they understand the consequences. The same problem plagues snaps but that's a different bug report I suppose. ** Affects: unattended-upgrades (Ubuntu) Importance: Undecided Status: Confirmed ** Tags: bionic -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to unattended-upgrades in Ubuntu. https://bugs.launchpad.net/bugs/1836328 Title: unattended-upgrades should not be enabled by default Status in unattended-upgrades package in Ubuntu: Confirmed Bug description: The unattended-upgrades package and the whole concept of upgrading software automatically behind user's back is HARMFUL and the service/timer should NOT be enabled by default. It harms experience even for novice users with applications like Firefox preventing opening links until you restart it (which is terribad if you're in the middle of some work and don't want to do that at THAT particular moment!), and some other applications crashing in some cases, especially applications that run sub-processes interactively or on timers/cronjobs -- where updates to their libs or other dependencies create error states due to version/API/ABI mismatches. Please do not enable the service/timer by default and leave it to advanced users to enable assuming they understand the consequences. The same problem plagues snaps but that's a different bug report I suppose. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/unattended-upgrades/+bug/1836328/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1836328] Re: unattended-upgrades should not be enabled by default
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: unattended-upgrades (Ubuntu) Status: New => Confirmed -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to unattended-upgrades in Ubuntu. https://bugs.launchpad.net/bugs/1836328 Title: unattended-upgrades should not be enabled by default Status in unattended-upgrades package in Ubuntu: Confirmed Bug description: The unattended-upgrades package and the whole concept of upgrading software automatically behind user's back is HARMFUL and the service/timer should NOT be enabled by default. It harms experience even for novice users with applications like Firefox preventing opening links until you restart it (which is terribad if you're in the middle of some work and don't want to do that at THAT particular moment!), and some other applications crashing in some cases, especially applications that run sub-processes interactively or on timers/cronjobs -- where updates to their libs or other dependencies create error states due to version/API/ABI mismatches. Please do not enable the service/timer by default and leave it to advanced users to enable assuming they understand the consequences. The same problem plagues snaps but that's a different bug report I suppose. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/unattended-upgrades/+bug/1836328/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1551623] Re: [SRU] package gconf2 3.2.6-3ubuntu6 failed to install/upgrade: dependency problems - leaving triggers unprocessed
Oh, nice. Maybe then gconf patches won't be needed. (Still need to fix FTBFS in Bionic, bug 1834211.) -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to gconf in Ubuntu. https://bugs.launchpad.net/bugs/1551623 Title: [SRU] package gconf2 3.2.6-3ubuntu6 failed to install/upgrade: dependency problems - leaving triggers unprocessed Status in gconf package in Ubuntu: Triaged Bug description: [Impact] During system upgrades, triggers for gconf2 might activate too early, while some of its dependencies aren't configured yet. This happens several times in a loop and stops the upgrade in the end. The attached debdiffs fix this issue by changing interest to interest- noawait in debian/gconf2.triggers file. The triggers will now activate near the end of upgrade. In addition, the debdiff for Bionic also contains a fix for FTBFS (bug 1834211). [Test Case] Triggers for gconf2 are usually activated on changes in /usr/share/GConf/gsettings folder, so the main Ubuntu edition (with GNOME) is most suitable for reproducing the issue. To reproduce it, install that edition, apply all updates, then try upgrading to the next release. [Regression Potential] None, interest-noawait trigger is known to work well in other packages (comment 31). [Other Info] Even if Cosmic goes EOL next month, the fix for it might be worth it for release upgrades. [Original Description] When upgrading from 15.10 to 16.04Beta (2016-03-01), this error occured, alongside many others related to systemd and gnome. Notice that despite all warnings and errors, finally, the system remained functional. ProblemType: Package DistroRelease: Ubuntu 16.04 Package: gconf2 3.2.6-3ubuntu6 ProcVersionSignature: Ubuntu 4.4.0-8.23-generic 4.4.2 Uname: Linux 4.4.0-8-generic x86_64 ApportVersion: 2.20-0ubuntu3 Architecture: amd64 Date: Tue Mar 1 09:21:15 2016 ErrorMessage: dependency problems - leaving triggers unprocessed InstallationDate: Installed on 2015-10-04 (148 days ago) InstallationMedia: Ubuntu 15.10 "Wily Werewolf" - Alpha amd64 (20151002) RelatedPackageVersions: dpkg 1.18.4ubuntu1 apt 1.2.3 SourcePackage: gconf Title: package gconf2 3.2.6-3ubuntu6 failed to install/upgrade: dependency problems - leaving triggers unprocessed UpgradeStatus: Upgraded to xenial on 2016-03-01 (0 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gconf/+bug/1551623/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1835809] Re: AMD Ryzen 3000 series fails to boot
Hi, I can confirm now that newly installed 19.04 on 3400G is booting without any problems. -- 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/1835809 Title: AMD Ryzen 3000 series fails to boot Status in systemd package in Ubuntu: In Progress Status in systemd source package in Disco: Fix Committed Status in systemd source package in Eoan: In Progress Bug description: [Impact] * Systems with AMD Ryzen 3000 series CPUs don't boot. [Test Case] * Boot with fixed systemd on an AMD Ryzen 3000 series system. [Regression Potential] * The fix itself is very small, it ignores known to be faulty random values returned by the rdrand instruction and use a different random source. Those values can still be returned by a properly working rdrand implementation in 2 in 2^32 cases on 32 bit arches and in 2 in 2^64 cases on 64 bit arches, but the fallback to the other random source ensures that in those rare occasions a random number can be generated. [Original Bug Text] On the new AMD Ryzen 3000 series CPUs, there is an issue with systemd preventing the boot process from completing. This issue does not affect the older systemd version in 18.04, but affects the 19.04 version. Here is a screenshot showing what happens: https://www.phoronix.net/image.php?id=ryzen-3700x-3900x-linux&image=amd_zen2_14_show I am currently testing a patch to systemd, derived from this pull request: https://github.com/systemd/systemd/pull/12536 This is a high severity issue, as I do not believe there is no potential workaround without either a firmware update or an ISO respin. I have attached a rebase of the potential patch on the current 19.04 version of systemd for reference. I will provide more details after testing. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1835809/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1836328] Re: unattended-upgrades should not be enabled by default
** Bug watch added: Debian Bug tracker #902653 https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=902653 ** Also affects: unattended-upgrades (Debian) via https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=902653 Importance: Unknown Status: Unknown ** Changed in: unattended-upgrades (Ubuntu) Status: Confirmed => Won't Fix -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to unattended-upgrades in Ubuntu. https://bugs.launchpad.net/bugs/1836328 Title: unattended-upgrades should not be enabled by default Status in unattended-upgrades package in Ubuntu: Won't Fix Status in unattended-upgrades package in Debian: Unknown Bug description: The unattended-upgrades package and the whole concept of upgrading software automatically behind user's back is HARMFUL and the service/timer should NOT be enabled by default. It harms experience even for novice users with applications like Firefox preventing opening links until you restart it (which is terribad if you're in the middle of some work and don't want to do that at THAT particular moment!), and some other applications crashing in some cases, especially applications that run sub-processes interactively or on timers/cronjobs -- where updates to their libs or other dependencies create error states due to version/API/ABI mismatches. Please do not enable the service/timer by default and leave it to advanced users to enable assuming they understand the consequences. The same problem plagues snaps but that's a different bug report I suppose. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/unattended-upgrades/+bug/1836328/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1836328] Re: unattended-upgrades should not be enabled by default
Individual packages can be fixed to deal with being upgraded while their executables are running. W3m for example keeps running fine and in my past experience Firefox just told the user to restart it but kept running. There is automation in place to ensure restarting services relying in shared libraries for software packaged in Ubuntu, but there is nut much unattended-upgrades can do to help software surviving upgrades in case the software is not packaged as a .deb. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to unattended-upgrades in Ubuntu. https://bugs.launchpad.net/bugs/1836328 Title: unattended-upgrades should not be enabled by default Status in unattended-upgrades package in Ubuntu: Won't Fix Status in unattended-upgrades package in Debian: Unknown Bug description: The unattended-upgrades package and the whole concept of upgrading software automatically behind user's back is HARMFUL and the service/timer should NOT be enabled by default. It harms experience even for novice users with applications like Firefox preventing opening links until you restart it (which is terribad if you're in the middle of some work and don't want to do that at THAT particular moment!), and some other applications crashing in some cases, especially applications that run sub-processes interactively or on timers/cronjobs -- where updates to their libs or other dependencies create error states due to version/API/ABI mismatches. Please do not enable the service/timer by default and leave it to advanced users to enable assuming they understand the consequences. The same problem plagues snaps but that's a different bug report I suppose. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/unattended-upgrades/+bug/1836328/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1836328] Re: unattended-upgrades should not be enabled by default
s/closed to/close to/ . -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to unattended-upgrades in Ubuntu. https://bugs.launchpad.net/bugs/1836328 Title: unattended-upgrades should not be enabled by default Status in unattended-upgrades package in Ubuntu: Won't Fix Status in unattended-upgrades package in Debian: Unknown Bug description: The unattended-upgrades package and the whole concept of upgrading software automatically behind user's back is HARMFUL and the service/timer should NOT be enabled by default. It harms experience even for novice users with applications like Firefox preventing opening links until you restart it (which is terribad if you're in the middle of some work and don't want to do that at THAT particular moment!), and some other applications crashing in some cases, especially applications that run sub-processes interactively or on timers/cronjobs -- where updates to their libs or other dependencies create error states due to version/API/ABI mismatches. Please do not enable the service/timer by default and leave it to advanced users to enable assuming they understand the consequences. The same problem plagues snaps but that's a different bug report I suppose. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/unattended-upgrades/+bug/1836328/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1836328] Re: unattended-upgrades should not be enabled by default
Unfortunately you can't fix individual packages, and you're a bit wrong about Firefox. Yes it keeps running, but does not open new tabs/sub- processes until it's restarted, so effectively it's in a crippled state, which depending on your what you're working with through it, maybe constitute a Denial of Service. The simplest solution is not to change underlying software without user intervention, by default. An information system that modified its own code, unexpectedly without user intervention (which happens here as the user is not warned there's an update and asked if they want to proceed), is effectively a compromised system and that behavior is closed to malware. Please reconsider removing unattended-upgrades operating by default. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to unattended-upgrades in Ubuntu. https://bugs.launchpad.net/bugs/1836328 Title: unattended-upgrades should not be enabled by default Status in unattended-upgrades package in Ubuntu: Won't Fix Status in unattended-upgrades package in Debian: Unknown Bug description: The unattended-upgrades package and the whole concept of upgrading software automatically behind user's back is HARMFUL and the service/timer should NOT be enabled by default. It harms experience even for novice users with applications like Firefox preventing opening links until you restart it (which is terribad if you're in the middle of some work and don't want to do that at THAT particular moment!), and some other applications crashing in some cases, especially applications that run sub-processes interactively or on timers/cronjobs -- where updates to their libs or other dependencies create error states due to version/API/ABI mismatches. Please do not enable the service/timer by default and leave it to advanced users to enable assuming they understand the consequences. The same problem plagues snaps but that's a different bug report I suppose. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/unattended-upgrades/+bug/1836328/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 991002] Re: Use the modern English name Bangla instead of Bengali for the language code bn
** Changed in: gnome-desktop Status: New => Fix Released -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to ibus in Ubuntu. https://bugs.launchpad.net/bugs/991002 Title: Use the modern English name Bangla instead of Bengali for the language code bn Status in CLDR: Fix Released Status in GLibC: Fix Released Status in gnome-desktop: Fix Released Status in ibus: Fix Released Status in xkeyboard-config: Fix Released Status in gnome-control-center package in Ubuntu: Fix Released Status in ibus package in Ubuntu: Fix Released Status in iso-codes package in Ubuntu: Fix Released Status in langpack-locales package in Ubuntu: Fix Released Status in language-selector package in Ubuntu: Fix Released Status in localechooser package in Ubuntu: Fix Released Status in xkeyboard-config package in Ubuntu: Fix Released Status in iso-codes package in Debian: Fix Released Status in xkeyboard-config package in Debian: Fix Released Bug description: The official name for the state language for Bangladesh is Bangla, as detailed on section 3, part 1 of the Bangladesh constitution (http://www1.umn.edu/humanrts/research/bangladesh-constitution.pdf). However, language selector continues to refer to this language as Bengali (Bangladeh). While Bengali has been historically used as the english name for the language during colonial periods, the name 'Bangla' is more widely used nowadays. It is also the name with which native speakers identify the language. This package uses Bengali(Bangladesh) as the identifier for language code bn-BD. Please change the name to Bangla(Bangladesh). ProblemType: Bug DistroRelease: Ubuntu 12.04 Package: language-selector-gnome 0.79 ProcVersionSignature: Ubuntu 3.2.0-23.36-generic 3.2.14 Uname: Linux 3.2.0-23-generic x86_64 ApportVersion: 2.0.1-0ubuntu5 Architecture: amd64 Date: Sun Apr 29 16:14:25 2012 PackageArchitecture: all ProcEnviron: LANGUAGE=bn_BD:bn:en_IN:en_GB:en PATH=(custom, no user) LANG=bn_BD.UTF-8 SHELL=/bin/bash SourcePackage: language-selector UpgradeStatus: Upgraded to precise on 2012-03-19 (41 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/cldr/+bug/991002/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1835581] Re: networkd-dhcp4 does not set prefsrc for dhcp-provided classless or static routes
** Changed in: systemd Status: Unknown => Fix Released -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to systemd in Ubuntu. https://bugs.launchpad.net/bugs/1835581 Title: networkd-dhcp4 does not set prefsrc for dhcp-provided classless or static routes Status in systemd: Fix Released Status in systemd package in Ubuntu: In Progress Status in systemd source package in Bionic: In Progress Status in systemd source package in Cosmic: In Progress Status in systemd source package in Disco: In Progress Status in systemd source package in Eoan: In Progress Bug description: [impact] the systemd networkd dhcp4 client sets the prefsrc for the default route added when a dhcp server provides only the gateway; but if the dhcp server provides classless route(s), those are configured instead, and the prefsrc is not set for those. Normally this is ok, but if the dhcp client system has other address(es) configured on the interface using dhcp, then the src for packets sent through a classless/static route might not be the same as the address provided by the dhcp server. If the gateway/router provided in the dhcp classless/static route(s) only allows traffic from the address provided to the dhcp client, then traffic from the dhcp client may be dropped by the gateway/router. [test case] set up a dhcp server system (e.g. ubuntu with dnsmasq installed and configured) and a dhcp client system. For example on the dhcp server, use this dnsmasq config: interface=ens8 bind-interfaces domain=test,10.10.0.0/24 dhcp-option=42,10.10.0.1 dhcp-range=test,10.10.0.10,10.10.0.100,1h On the dhcp client system, use networkd config such as: $ cat /etc/systemd/network/80-ens8.network [Match] Name=ens8 [Network] DHCP=ipv4 LinkLocalAddressing=ipv6 Address=10.10.0.5/24 Reboot the client, or restart networkd, and it should result in: $ ip -4 a show ens8 3: ens8: mtu 1500 qdisc fq_codel state UP group default qlen 1000 inet 10.10.0.5/24 brd 10.10.0.255 scope global ens8 valid_lft forever preferred_lft forever inet 10.10.0.75/24 brd 10.10.0.255 scope global secondary dynamic ens8 valid_lft 3580sec preferred_lft 3580sec $ ip r default via 10.10.0.1 dev ens8 proto dhcp src 10.10.0.75 metric 1024 10.10.0.0/24 dev ens8 proto kernel scope link src 10.10.0.5 10.10.0.1 dev ens8 proto dhcp scope link src 10.10.0.75 metric 1024 Note that, because networkd completes the static ip configuration before the dhcp reply is returned and processed, the static address is used for the subnet-local routing. But for global routing through the gateway, the dhcp-provided address is used: $ ip r get 1.1.1.1 1.1.1.1 via 10.10.0.1 dev ens8 src 10.10.0.75 uid 1000 Now on the server, add a classless route: dhcp-option=121,0.0.0.0/0,10.10.0.1 and restart dnsmasq on the server. Then on the client, reboot. It should now have: $ ip -4 a show ens8 3: ens8: mtu 1500 qdisc fq_codel state UP group default qlen 1000 inet 10.10.0.5/24 brd 10.10.0.255 scope global ens8 valid_lft forever preferred_lft forever inet 10.10.0.75/24 brd 10.10.0.255 scope global secondary dynamic ens8 valid_lft 3585sec preferred_lft 3585sec $ ip r default via 10.10.0.1 dev ens8 proto dhcp metric 1024 10.10.0.0/24 dev ens8 proto kernel scope link src 10.10.0.5 Now, the global route will use the static address, not the dhcp- provided address: $ ip r get 1.1.1.1 1.1.1.1 via 10.10.0.1 dev ens8 src 10.10.0.5 uid 1000 If the router, 10.10.0.1, only will forward traffic sent from the dhcp address it provided, 10.10.0.75, then this configuration will result in the client being unable to reach anything through the router, because all its packets will have a source address of 10.10.0.5, which the router would drop/reject. [regression potential] this only affects dhcp routes provided by a dhcp server using the 'static' or 'classless' route dhcp options. Since this behavior is currently the default when a system doesn't add static address(es) to interfaces that also get dhcp addresses, this is likely not a change in behavior for the vast majority of systems. And any systems that do add static address(es) would usually be able to route through a gateway from either the dhcp-provided, or static, address. So the regression potential for this change should be low. [other info] TBD To manage notifications about this bug go to: https://bugs.launchpad.net/systemd/+bug/1835581/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1836328] Re: unattended-upgrades should not be enabled by default
** Changed in: unattended-upgrades (Debian) Status: Unknown => Won't Fix -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to unattended-upgrades in Ubuntu. https://bugs.launchpad.net/bugs/1836328 Title: unattended-upgrades should not be enabled by default Status in unattended-upgrades package in Ubuntu: Won't Fix Status in unattended-upgrades package in Debian: Won't Fix Bug description: The unattended-upgrades package and the whole concept of upgrading software automatically behind user's back is HARMFUL and the service/timer should NOT be enabled by default. It harms experience even for novice users with applications like Firefox preventing opening links until you restart it (which is terribad if you're in the middle of some work and don't want to do that at THAT particular moment!), and some other applications crashing in some cases, especially applications that run sub-processes interactively or on timers/cronjobs -- where updates to their libs or other dependencies create error states due to version/API/ABI mismatches. Please do not enable the service/timer by default and leave it to advanced users to enable assuming they understand the consequences. The same problem plagues snaps but that's a different bug report I suppose. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/unattended-upgrades/+bug/1836328/+subscriptions -- Mailing list: https://launchpad.net/~touch-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"
** Tags added: id-5d2752b415f430133d5cd4a1 -- 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 Status in software-properties source package in Eoan: 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 1836258] Re: Update hyperlink when enabling UCA
Thanks Peter. I'll get this SRU'd. Marked as Low since it doesn't affect any functionality but I do think it needs fixing as it's just not clean. ** Changed in: software-properties (Ubuntu) Status: New => Triaged ** Changed in: software-properties (Ubuntu) Importance: Undecided => Low -- 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/1836258 Title: Update hyperlink when enabling UCA Status in software-properties package in Ubuntu: Triaged Bug description: When enabling UCA a hyperlink is printed: $ sudo add-apt-repository cloud-archive:train-proposed Ubuntu Cloud Archive for OpenStack Train [proposed] More info: https://wiki.ubuntu.com/ServerTeam/CloudArchive Press [ENTER] to continue or Ctrl-c to cancel adding it. The hyperlink redirects to: https://wiki.ubuntu.com/OpenStack/CloudArchive so it should just be corrected at the source: https://git.launchpad.net/ubuntu/+source/software- properties/tree/softwareproperties/cloudarchive.py#n50 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/software-properties/+bug/1836258/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1836258] Re: Update hyperlink when enabling UCA
** Also affects: software-properties (Ubuntu Eoan) Importance: Low Status: Triaged ** Also affects: software-properties (Ubuntu Bionic) Importance: Undecided Status: New ** Changed in: software-properties (Ubuntu Bionic) Status: New => Triaged ** Changed in: software-properties (Ubuntu Bionic) Importance: Undecided => Low ** Also affects: software-properties (Ubuntu Xenial) Importance: Undecided Status: New ** Changed in: software-properties (Ubuntu Xenial) Status: New => Triaged ** Changed in: software-properties (Ubuntu Xenial) Importance: Undecided => Low -- 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/1836258 Title: Update hyperlink when enabling UCA Status in software-properties package in Ubuntu: Triaged Status in software-properties source package in Xenial: Triaged Status in software-properties source package in Bionic: Triaged Status in software-properties source package in Eoan: Triaged Bug description: When enabling UCA a hyperlink is printed: $ sudo add-apt-repository cloud-archive:train-proposed Ubuntu Cloud Archive for OpenStack Train [proposed] More info: https://wiki.ubuntu.com/ServerTeam/CloudArchive Press [ENTER] to continue or Ctrl-c to cancel adding it. The hyperlink redirects to: https://wiki.ubuntu.com/OpenStack/CloudArchive so it should just be corrected at the source: https://git.launchpad.net/ubuntu/+source/software- properties/tree/softwareproperties/cloudarchive.py#n50 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/software-properties/+bug/1836258/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1835809] Re: AMD Ryzen 3000 series fails to boot
AMD released a BIOS fix: https://www.phoronix.com/scan.php?page=news_item&px=AMD-Releases-Linux- Zen2-Fix&utm_source=feedburner&utm_medium=feed&utm_campaign=Feed%3A+Phoronix+%28Phoronix%29 -- 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/1835809 Title: AMD Ryzen 3000 series fails to boot Status in systemd package in Ubuntu: In Progress Status in systemd source package in Disco: Fix Committed Status in systemd source package in Eoan: In Progress Bug description: [Impact] * Systems with AMD Ryzen 3000 series CPUs don't boot. [Test Case] * Boot with fixed systemd on an AMD Ryzen 3000 series system. [Regression Potential] * The fix itself is very small, it ignores known to be faulty random values returned by the rdrand instruction and use a different random source. Those values can still be returned by a properly working rdrand implementation in 2 in 2^32 cases on 32 bit arches and in 2 in 2^64 cases on 64 bit arches, but the fallback to the other random source ensures that in those rare occasions a random number can be generated. [Original Bug Text] On the new AMD Ryzen 3000 series CPUs, there is an issue with systemd preventing the boot process from completing. This issue does not affect the older systemd version in 18.04, but affects the 19.04 version. Here is a screenshot showing what happens: https://www.phoronix.net/image.php?id=ryzen-3700x-3900x-linux&image=amd_zen2_14_show I am currently testing a patch to systemd, derived from this pull request: https://github.com/systemd/systemd/pull/12536 This is a high severity issue, as I do not believe there is no potential workaround without either a firmware update or an ISO respin. I have attached a rebase of the potential patch on the current 19.04 version of systemd for reference. I will provide more details after testing. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1835809/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1768539] Re: Conflicts between / and /usr
** Bug watch added: Debian Bug tracker #914716 https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=914716 ** Also affects: molly-guard (Debian) via https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=914716 Importance: Unknown Status: Unknown -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to pm-utils in Ubuntu. https://bugs.launchpad.net/bugs/1768539 Title: Conflicts between / and /usr Status in molly-guard package in Ubuntu: New Status in neutron-vpnaas package in Ubuntu: Fix Released Status in pm-utils package in Ubuntu: Fix Committed Status in safe-rm package in Ubuntu: Fix Released Status in molly-guard package in Debian: Unknown Status in pm-utils package in Debian: Fix Released Status in safe-rm package in Debian: Fix Released Bug description: bin/rm and usr/bin/rm conflict between coreutils and safe-rm --- Not a conflict, but these just look weird: neutron-vpnaas ships these in python-neutron-vpnaas etc/neutron/rootwrap.d/vpnaas.filters usr/etc/neutron/rootwrap.d/vpnaas.filters --- pm-utils and molly-guard conflict on: sbin/pm-hibernate usr/sbin/pm-hibernate sbin/pm-suspend usr/sbin/pm-suspend sbin/pm-suspend-hybrid usr/sbin/pm-suspend-hybrid To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/molly-guard/+bug/1768539/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1809247] Re: SetReportCrashes to true dbus call failed
Could we get this fix pushed out into the repositories? It can be pretty annoying and confusing to users if you have other issues which cause application crashes fairly frequently. For users to fix this: 1) Press Ctrl+Alt+T to open a terminal 2) Enter this command: sudo apt install whoopsie-preferences -- 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/1809247 Title: SetReportCrashes to true dbus call failed Status in apport package in Ubuntu: Fix Released Status in apport source package in Disco: Fix Released Bug description: The following copied from screenshot 2018-12-20 11-50-53 Saving crash reporting state failed, Can't set auto auto or never reporting mode. Command '['/usr/bin/gdbus','call','-y','-d', 'com.ubuntu.WhoopsiePreferences','-o','/com/ubuntu/ WhoopsiePreferences','-m', 'com.ubuntu.WhoopsiePreferences.SetReportCrashes', 'true']' returned non-zero exit status 1. ProblemType: Package DistroRelease: Ubuntu 18.04 Package: linux-headers-4.15.0-43 4.15.0-43.46 ProcVersionSignature: Ubuntu 4.15.0-42.45-generic 4.15.18 Uname: Linux 4.15.0-42-generic i686 ApportVersion: 2.20.9-0ubuntu7.5 Architecture: i386 Date: Thu Dec 20 11:22:53 2018 Dependencies: DuplicateSignature: package:linux-headers-4.15.0-43:4.15.0-43.46 Unpacking linux-modules-extra-4.15.0-43-generic (4.15.0-43.46) ... dpkg: error processing archive /tmp/apt-dpkg-install-OeaFpG/04-linux-modules-extra-4.15.0-43-generic_4.15.0-43.46_i386.deb (--unpack): unable to open '/lib/modules/4.15.0-43-generic/kernel/drivers/infiniband/hw/cxgb4/iw_cxgb4.ko.dpkg-new': Operation not permitted ErrorMessage: unable to create new file '/var/lib/dpkg/info/linux-headers-4.15.0-43.list-new': Operation not permitted InstallationDate: Installed on 2017-12-03 (382 days ago) InstallationMedia: Lubuntu 17.10 "Artful Aardvark" - Release i386 (20171017.1) PackageArchitecture: all Python3Details: /usr/bin/python3.6, Python 3.6.7, python3-minimal, 3.6.7-1~18.04 PythonDetails: N/A RelatedPackageVersions: dpkg 1.19.0.5ubuntu2.1 apt 1.6.6 SourcePackage: linux Title: package linux-headers-4.15.0-43 4.15.0-43.46 failed to install/upgrade: unable to create new file '/var/lib/dpkg/info/linux-headers-4.15.0-43.list-new': Operation not permitted UpgradeStatus: Upgraded to bionic on 2018-09-18 (92 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apport/+bug/1809247/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1836258] Re: Update hyperlink when enabling UCA
Fixed package versions have been uploaded to eoan, bionic unapproved queue [1], and xenial unapproved queue [2]. [1] https://launchpad.net/ubuntu/bionic/+queue?queue_state=1&queue_text=software-properties [2] https://launchpad.net/ubuntu/xenial/+queue?queue_state=1&queue_text=software-properties ** Description changed: + [Impact] When enabling UCA a hyperlink is printed: - $ sudo add-apt-repository cloud-archive:train-proposed - Ubuntu Cloud Archive for OpenStack Train [proposed] - More info: https://wiki.ubuntu.com/ServerTeam/CloudArchive + $ sudo add-apt-repository cloud-archive:train-proposed + Ubuntu Cloud Archive for OpenStack Train [proposed] + More info: https://wiki.ubuntu.com/ServerTeam/CloudArchive Press [ENTER] to continue or Ctrl-c to cancel adding it. The hyperlink redirects to: https://wiki.ubuntu.com/OpenStack/CloudArchive so it should just be corrected at the source: https://git.launchpad.net/ubuntu/+source/software- properties/tree/softwareproperties/cloudarchive.py#n50 + + [Test Case] + The "More info:" link should be https://wiki.ubuntu.com/OpenStack/CloudArchive, for example: + + root@b1:~# sudo add-apt-repository cloud-archive:queens + Ubuntu Cloud Archive for OpenStack Queens + More info: https://wiki.ubuntu.com/OpenStack/CloudArchive + Press [ENTER] to continue or Ctrl-c to cancel adding it. + + [Regression Potential] + This change is extremely minimal as it only updates a string that points to a wiki URL. -- 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/1836258 Title: Update hyperlink when enabling UCA Status in software-properties package in Ubuntu: Triaged Status in software-properties source package in Xenial: Triaged Status in software-properties source package in Bionic: Triaged Status in software-properties source package in Eoan: Triaged Bug description: [Impact] When enabling UCA a hyperlink is printed: $ sudo add-apt-repository cloud-archive:train-proposed Ubuntu Cloud Archive for OpenStack Train [proposed] More info: https://wiki.ubuntu.com/ServerTeam/CloudArchive Press [ENTER] to continue or Ctrl-c to cancel adding it. The hyperlink redirects to: https://wiki.ubuntu.com/OpenStack/CloudArchive so it should just be corrected at the source: https://git.launchpad.net/ubuntu/+source/software- properties/tree/softwareproperties/cloudarchive.py#n50 [Test Case] The "More info:" link should be https://wiki.ubuntu.com/OpenStack/CloudArchive, for example: root@b1:~# sudo add-apt-repository cloud-archive:queens Ubuntu Cloud Archive for OpenStack Queens More info: https://wiki.ubuntu.com/OpenStack/CloudArchive Press [ENTER] to continue or Ctrl-c to cancel adding it. [Regression Potential] This change is extremely minimal as it only updates a string that points to a wiki URL. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/software-properties/+bug/1836258/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1668771] Re: systemd-resolved negative caching for extended period of time
I've made a proposal to change the resolved.conf Cache option to a tri- state "no, no-negative, yes" values. [0] If a lookup returns SERVFAIL systemd-resolved will cache the result for 30s (See 201d995), however, there are several use cases on which this condition is not acceptable (See #5552 comments) and the only workaround would be to disable cache entirely or flush it , which isn't optimal. This change adds the 'no-negative' option when set it avoids putting in cache negative answers but still works the same heuristics for positive answers. [0] https://github.com/systemd/systemd/pull/13047 ** Changed in: systemd (Ubuntu) Importance: Undecided => High ** Changed in: systemd (Ubuntu) Status: Confirmed => In Progress -- 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/1668771 Title: systemd-resolved negative caching for extended period of time Status in systemd: New Status in systemd package in Ubuntu: In Progress Bug description: 231-9ubuntu3 If a DNS lookup returns SERVFAIL, systemd-resolved seems to cache the result for very long (infinity?). I have to restart systemd-resolved to have the negative caching purged. After SERVFAIL DNS server issue has been resolved, chromium/firefox still returns DNS error despite host can correctly resolve the name. To manage notifications about this bug go to: https://bugs.launchpad.net/systemd/+bug/1668771/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1836418] [NEW] No HDMI audio device after resume, but pacmd list-cards sees it
Public bug reported: After suspend/resume, the HDMI audio device is missing from Sound Settings and pavucontrol. 'pacmd list-cards' still shows the device. This on Ubuntu 18.04.2 LTS 18.04 kernel 5.2.0-rc6-19.06.26.amdgpu.ubuntu ** Affects: pulseaudio (Ubuntu) Importance: Undecided Status: New ** Attachment added: "Output of pacmd list-cards" https://bugs.launchpad.net/bugs/1836418/+attachment/5276828/+files/list-card.txt ** Summary changed: - No HDMI audio device after resume, but pacmd list-card sees it + No HDMI audio device after resume, but pacmd list-cards sees it ** Description changed: After suspend/resume, the HDMI audio device is missing from Sound Settings and pavucontrol. - 'pacmd list-card' still shows the device. - + 'pacmd list-cards' still shows the device. This on Ubuntu 18.04.2 LTS 18.04 kernel 5.2.0-rc6-19.06.26.amdgpu.ubuntu -- 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/1836418 Title: No HDMI audio device after resume, but pacmd list-cards sees it Status in pulseaudio package in Ubuntu: New Bug description: After suspend/resume, the HDMI audio device is missing from Sound Settings and pavucontrol. 'pacmd list-cards' still shows the device. This on Ubuntu 18.04.2 LTS 18.04 kernel 5.2.0-rc6-19.06.26.amdgpu.ubuntu To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1836418/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1832108] Re: unmkinitramfs fails with lz4 compressed initrds
@xnox, Could you SRU this to bionic too? It becomes problematic to try to probe at an initramfs file from eoan when you're in bionic otherwise. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to initramfs-tools in Ubuntu. https://bugs.launchpad.net/bugs/1832108 Title: unmkinitramfs fails with lz4 compressed initrds Status in initramfs-tools package in Ubuntu: Fix Released Status in initramfs-tools source package in Cosmic: In Progress Status in initramfs-tools source package in Disco: Fix Released Status in initramfs-tools package in Debian: New Bug description: [Impact] * Cannot unpack initrds compressed with lz4 due to changes in lz4 [Test Case] $ sudo apt install initramfs-tools lz4 file $ mkinitramfs -c lz4 -o foo.img $ lsinitramfs foo.img cpio: premature end of archive [Regression Potential] * New lz4cat is more strict w.r.t. enforcing file name extensions, thus the fix is to feed a stream to lz4cat instead of asking it to open a file. The performance impact should be similar between both methods of reading file contents during ls/unmk-initramfs time. [Other Info] Original bug report: unmkinitramfs fails with lz4 compressed initrds Note: $ lz4cat -t unmkinitramfs_Cz6Yl9 File extension doesn't match expected LZ4_EXTENSION (.lz4); will not process file: unmkinitramfs_Cz6Yl9 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/initramfs-tools/+bug/1832108/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1768230] Re: Long time booting : Failed to connect to lvmetad. Falling back to device scanning.
I'm experiencing this on Linux Mint 19.1 fully updated and NOT encrypted disk or home. This is an LVM install though. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to initramfs-tools in Ubuntu. https://bugs.launchpad.net/bugs/1768230 Title: Long time booting : Failed to connect to lvmetad. Falling back to device scanning. Status in initramfs-tools package in Ubuntu: Fix Released Status in ubiquity package in Ubuntu: Fix Released Status in initramfs-tools source package in Bionic: Fix Released Status in ubiquity source package in Bionic: Fix Released Bug description: [SRU Justification] A regression in initramfs-tools causes it to autogenerate config in the initramfs saying to resume from any available swap devices, but references the swap device by UUID, which is not a canonical form for referring to LVM volumes (because of snapshotting, they are not unique). Ubiquity also generates a file in /etc at install time which references the swap partition in the same way. Since the lvm2 initramfs hooks also only activate precisely those LVs that are detected as needed at boot, this adds an inappropriate 30-second boot delay to any system with swap on LVM, which includes any desktop system that was configured with LVM (but not full-disk encryption) at install time. [Test case] 1. Install using the "Use LVM" option in the desktop installer. 4. Reboot. 5. Verify that dmesg shows a 30-second delay before mounting the root filesystem. 6. Install initramfs-tools from bionic-proposed. 7. Reboot. 8. Verify that dmesg no longer shows a 30-second delay before mounting the root filesystem. 9. Install using the bionic daily image that contains the ubiquity from bionic-proposed. 10. Reboot. 11. Verify that /etc/initramfs-tools/conf.d/resume is not present and that there is no delay before mounting the root filesystem. [Regression potential] This makes changes to shell scripts, and shell is a perilous language. An unnoticed bug could cause all initramfs generation, and thus all kernel installation, to fail for some users. A regression could also cause a user to lose hiberation support that they currently have. [Original description] After choosing "Erase disk and install ubuntu" + "Use LVM with the new Ubuntu installation", the system is very slow to reboot. It shows the message : "WARNING:Failed to connect to lvmetad. Falling back to device scanning.", then waits 32 seconds, then continues as it should. I think this is a ubiquity bug, since the d-i based installer is not affected. - ubuntu-18.04-desktop-amd64.iso (a55353d837cbf7bc006cf49eeff05ae5044e757498e30643a9199b9a25bc9a34) : affected - xubuntu-18.04-desktop-amd64.iso (7c24318d3b1de1efd584b5aea034ce1aafd2d0f06c59812d989a5fc95bf947e3) : affected - ubuntu-18.04-server-amd64.iso (a7f5c7b0cdd0e9560d78f1e47660e066353bb8a79eb78d1fc3f4ea62a07e6cbc) : not affected To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/initramfs-tools/+bug/1768230/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1836258] Re: Update hyperlink when enabling UCA
This bug was fixed in the package software-properties - 0.98.5 --- software-properties (0.98.5) eoan; urgency=medium * cloudarchive: Update outdated WEB_LINK that is presented when cloud archive is enabled (LP: #1836258). -- Corey Bryant Fri, 12 Jul 2019 10:02:43 -0400 ** Changed in: software-properties (Ubuntu Eoan) Status: Triaged => Fix Released -- 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/1836258 Title: Update hyperlink when enabling UCA Status in software-properties package in Ubuntu: Fix Released Status in software-properties source package in Xenial: Triaged Status in software-properties source package in Bionic: Triaged Status in software-properties source package in Eoan: Fix Released Bug description: [Impact] When enabling UCA a hyperlink is printed: $ sudo add-apt-repository cloud-archive:train-proposed Ubuntu Cloud Archive for OpenStack Train [proposed] More info: https://wiki.ubuntu.com/ServerTeam/CloudArchive Press [ENTER] to continue or Ctrl-c to cancel adding it. The hyperlink redirects to: https://wiki.ubuntu.com/OpenStack/CloudArchive so it should just be corrected at the source: https://git.launchpad.net/ubuntu/+source/software- properties/tree/softwareproperties/cloudarchive.py#n50 [Test Case] The "More info:" link should be https://wiki.ubuntu.com/OpenStack/CloudArchive, for example: root@b1:~# sudo add-apt-repository cloud-archive:queens Ubuntu Cloud Archive for OpenStack Queens More info: https://wiki.ubuntu.com/OpenStack/CloudArchive Press [ENTER] to continue or Ctrl-c to cancel adding it. [Regression Potential] This change is extremely minimal as it only updates a string that points to a wiki URL. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/software-properties/+bug/1836258/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1836427] [NEW] Trying to install Alps MD1000 printer on my Ubuntu 16.04 desktop with pci express parallel card istalled.
Public bug reported: Was able to get printer to work on a computer with Ubuntu and a parallel port on motherboard. Thanks for any ideas on the problem.I am not very versed in command line. Boyd ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: cups 2.1.3-4ubuntu0.9 ProcVersionSignature: Ubuntu 4.15.0-54.58~16.04.1-generic 4.15.18 Uname: Linux 4.15.0-54-generic x86_64 ApportVersion: 2.20.1-0ubuntu2.19 Architecture: amd64 CurrentDesktop: Unity Date: Fri Jul 12 15:44:26 2019 InstallationDate: Installed on 2018-04-13 (455 days ago) InstallationMedia: Ubuntu 16.04.4 LTS "Xenial Xerus" - Release amd64 (20180228) Lpstat: device for ALPS-MD-1000-T-03: parallel:/dev/lp0 device for Brother-MFC-7860DW: dnssd://Brother%20MFC-7860DW._pdl-datastream._tcp.local/ device for Hewlett-Packard-HP-Color-LaserJet-CP1518ni: hp:/net/HP_Color_LaserJet_CP1518ni?ip=192.168.1.15 MachineType: Gateway DX4860 Papersize: letter PpdFiles: Error: command ['fgrep', '-H', '*NickName', '/etc/cups/ppd/ALPS-MD-1000-T-03.ppd', '/etc/cups/ppd/Hewlett-Packard-HP-Color-LaserJet-CP1518ni.ppd', '/etc/cups/ppd/Brother-MFC-7860DW.ppd'] failed with exit code 2: grep: /etc/cups/ppd/ALPS-MD-1000-T-03.ppd: Permission denied grep: /etc/cups/ppd/Hewlett-Packard-HP-Color-LaserJet-CP1518ni.ppd: Permission denied grep: /etc/cups/ppd/Brother-MFC-7860DW.ppd: Permission denied ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.15.0-54-generic root=UUID=5c82fc7d-a18d-4365-baec-e9d75d27f225 ro quiet splash vt.handoff=7 SourcePackage: cups UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 04/18/2012 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: P03-A3 dmi.board.name: DX4860 dmi.board.vendor: Gateway dmi.board.version: 1.01 dmi.chassis.type: 3 dmi.chassis.vendor: Gateway dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrP03-A3:bd04/18/2012:svnGateway:pnDX4860:pvr:rvnGateway:rnDX4860:rvr1.01:cvnGateway:ct3:cvr: dmi.product.family: Gateway Desktop dmi.product.name: DX4860 dmi.sys.vendor: Gateway ** Affects: cups (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug xenial -- 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/1836427 Title: Trying to install Alps MD1000 printer on my Ubuntu 16.04 desktop with pci express parallel card istalled. Status in cups package in Ubuntu: New Bug description: Was able to get printer to work on a computer with Ubuntu and a parallel port on motherboard. Thanks for any ideas on the problem.I am not very versed in command line. Boyd ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: cups 2.1.3-4ubuntu0.9 ProcVersionSignature: Ubuntu 4.15.0-54.58~16.04.1-generic 4.15.18 Uname: Linux 4.15.0-54-generic x86_64 ApportVersion: 2.20.1-0ubuntu2.19 Architecture: amd64 CurrentDesktop: Unity Date: Fri Jul 12 15:44:26 2019 InstallationDate: Installed on 2018-04-13 (455 days ago) InstallationMedia: Ubuntu 16.04.4 LTS "Xenial Xerus" - Release amd64 (20180228) Lpstat: device for ALPS-MD-1000-T-03: parallel:/dev/lp0 device for Brother-MFC-7860DW: dnssd://Brother%20MFC-7860DW._pdl-datastream._tcp.local/ device for Hewlett-Packard-HP-Color-LaserJet-CP1518ni: hp:/net/HP_Color_LaserJet_CP1518ni?ip=192.168.1.15 MachineType: Gateway DX4860 Papersize: letter PpdFiles: Error: command ['fgrep', '-H', '*NickName', '/etc/cups/ppd/ALPS-MD-1000-T-03.ppd', '/etc/cups/ppd/Hewlett-Packard-HP-Color-LaserJet-CP1518ni.ppd', '/etc/cups/ppd/Brother-MFC-7860DW.ppd'] failed with exit code 2: grep: /etc/cups/ppd/ALPS-MD-1000-T-03.ppd: Permission denied grep: /etc/cups/ppd/Hewlett-Packard-HP-Color-LaserJet-CP1518ni.ppd: Permission denied grep: /etc/cups/ppd/Brother-MFC-7860DW.ppd: Permission denied ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.15.0-54-generic root=UUID=5c82fc7d-a18d-4365-baec-e9d75d27f225 ro quiet splash vt.handoff=7 SourcePackage: cups UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 04/18/2012 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: P03-A3 dmi.board.name: DX4860 dmi.board.vendor: Gateway dmi.board.version: 1.01 dmi.chassis.type: 3 dmi.chassis.vendor: Gateway dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrP03-A3:bd04/18/2012:svnGateway:pnDX4860:pvr:rvnGateway:rnDX4860:rvr1.01:cvnGateway:ct3:cvr: dmi.product.family: Gateway Desktop dmi.product.name: DX4860 dmi.sys.vendor: Gateway To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/cups/+bug/1836427/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1829401] Re: gi.repository.GLib.GError: pk-client-error-quark: could not do untrusted question as no klass support
** Tags added: rls-ee-incoming
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to packagekit in Ubuntu.
https://bugs.launchpad.net/bugs/1829401
Title:
gi.repository.GLib.GError: pk-client-error-quark: could not do
untrusted question as no klass support
Status in packagekit package in Ubuntu:
Triaged
Status in packagekit source package in Eoan:
Triaged
Bug description:
The Ubuntu Error Tracker has been receiving reports about a problem regarding
software-properties. This problem was most recently seen with package version
0.98.2, the problem page at
https://errors.ubuntu.com/problem/300ff7bf9068dc50ace4c5db5c4a34ba0dfc926d
contains more details, including versions of packages affected, stacktrace or
traceback, and individual crash reports.
If you do not have access to the Ubuntu Error Tracker and are a software
developer, you can request it at http://forms.canonical.com/reports/.
[Back trace]
Traceback (most recent call last):
File
"/usr/lib/python3/dist-packages/softwareproperties/gtk/DialogCacheOutdated.py",
line 86, in on_pktask_finish
results = self._pktask.generic_finish(result)
gi.repository.GLib.GError: pk-client-error-quark: could not do untrusted
question as no klass support (8)
During handling of the above exception, another exception occurred:
Traceback (most recent call last):
File
"/usr/lib/python3/dist-packages/softwareproperties/gtk/DialogCacheOutdated.py",
line 89, in on_pktask_finish
Gtk.ButtonsType.CANCEL, _("Error while refreshing cache"))
File "/usr/lib/python3/dist-packages/gi/overrides/__init__.py", line 319,
in new_init
return super_init_func(self, **new_kwargs)
File "/usr/lib/python3/dist-packages/gi/overrides/Gtk.py", line 575, in
__init__
self._init(*args, **new_kwargs)
File "/usr/lib/python3/dist-packages/gi/overrides/__init__.py", line 319,
in new_init
return super_init_func(self, **new_kwargs)
File "/usr/lib/python3/dist-packages/gi/overrides/Gtk.py", line 521, in
__init__
_window_init(self, *args, **kwargs)
File "/usr/lib/python3/dist-packages/gi/overrides/__init__.py", line 319,
in new_init
return super_init_func(self, **new_kwargs)
TypeError: could not convert value for property `transient_for' from
DialogCacheOutdated to GtkWindow
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/packagekit/+bug/1829401/+subscriptions
--
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1829401] Re: gi.repository.GLib.GError: pk-client-error-quark: could not do untrusted question as no klass support
** Tags removed: rls-ee-incoming
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to packagekit in Ubuntu.
https://bugs.launchpad.net/bugs/1829401
Title:
gi.repository.GLib.GError: pk-client-error-quark: could not do
untrusted question as no klass support
Status in packagekit package in Ubuntu:
Triaged
Status in packagekit source package in Eoan:
Triaged
Bug description:
The Ubuntu Error Tracker has been receiving reports about a problem regarding
software-properties. This problem was most recently seen with package version
0.98.2, the problem page at
https://errors.ubuntu.com/problem/300ff7bf9068dc50ace4c5db5c4a34ba0dfc926d
contains more details, including versions of packages affected, stacktrace or
traceback, and individual crash reports.
If you do not have access to the Ubuntu Error Tracker and are a software
developer, you can request it at http://forms.canonical.com/reports/.
[Back trace]
Traceback (most recent call last):
File
"/usr/lib/python3/dist-packages/softwareproperties/gtk/DialogCacheOutdated.py",
line 86, in on_pktask_finish
results = self._pktask.generic_finish(result)
gi.repository.GLib.GError: pk-client-error-quark: could not do untrusted
question as no klass support (8)
During handling of the above exception, another exception occurred:
Traceback (most recent call last):
File
"/usr/lib/python3/dist-packages/softwareproperties/gtk/DialogCacheOutdated.py",
line 89, in on_pktask_finish
Gtk.ButtonsType.CANCEL, _("Error while refreshing cache"))
File "/usr/lib/python3/dist-packages/gi/overrides/__init__.py", line 319,
in new_init
return super_init_func(self, **new_kwargs)
File "/usr/lib/python3/dist-packages/gi/overrides/Gtk.py", line 575, in
__init__
self._init(*args, **new_kwargs)
File "/usr/lib/python3/dist-packages/gi/overrides/__init__.py", line 319,
in new_init
return super_init_func(self, **new_kwargs)
File "/usr/lib/python3/dist-packages/gi/overrides/Gtk.py", line 521, in
__init__
_window_init(self, *args, **kwargs)
File "/usr/lib/python3/dist-packages/gi/overrides/__init__.py", line 319,
in new_init
return super_init_func(self, **new_kwargs)
TypeError: could not convert value for property `transient_for' from
DialogCacheOutdated to GtkWindow
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/packagekit/+bug/1829401/+subscriptions
--
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1836434] [NEW] can not able to browse site which needed adobe flash player and latest graphic drivers
Public bug reported: can not able to browse site which needed adobe flash player and latest graphic drivers. and also can't ab;e to access the settings of ubuntu ProblemType: Bug DistroRelease: Ubuntu 19.04 Package: xorg 1:7.7+19ubuntu12 ProcVersionSignature: Ubuntu 5.0.0-20.21-generic 5.0.8 Uname: Linux 5.0.0-20-generic x86_64 ApportVersion: 2.20.10-0ubuntu27.1 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Sat Jul 13 10:39:46 2019 DistUpgraded: 2019-05-23 11:48:24,738 ERROR got error from PostInstallScript ./xorg_fix_proprietary.py (g-exec-error-quark: Failed to execute child process “./xorg_fix_proprietary.py” (No such file or directory) (8)) DistroCodename: disco DistroVariant: ubuntu DkmsStatus: anbox, 1, 5.0.0-19-generic, x86_64: installed anbox, 1, 5.0.0-20-generic, x86_64: installed ExtraDebuggingInterest: Yes, including running git bisection searches GraphicsCard: NVIDIA Corporation GF119 [GeForce GT 610] [10de:104a] (rev a1) (prog-if 00 [VGA controller]) Subsystem: ASUSTeK Computer Inc. GF119 [GeForce GT 610] [1043:8496] InstallationDate: Installed on 2019-04-15 (88 days ago) InstallationMedia: Ubuntu 18.10 "Cosmic Cuttlefish" - Release amd64 (20181017.3) MachineType: To Be Filled By O.E.M. To Be Filled By O.E.M. ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.0.0-20-generic root=UUID=fe96674e-a634-4474-9fab-b79d0d3d0a5b ro quiet splash vt.handoff=1 SourcePackage: xorg UpgradeStatus: Upgraded to disco on 2019-05-23 (50 days ago) dmi.bios.date: 03/27/2017 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: P1.20 dmi.board.name: H91M-XT PLUS dmi.board.vendor: ASRock dmi.chassis.asset.tag: To Be Filled By O.E.M. dmi.chassis.type: 3 dmi.chassis.vendor: To Be Filled By O.E.M. dmi.chassis.version: To Be Filled By O.E.M. dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrP1.20:bd03/27/2017:svnToBeFilledByO.E.M.:pnToBeFilledByO.E.M.:pvrToBeFilledByO.E.M.:rvnASRock:rnH91M-XTPLUS:rvr:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.: dmi.product.family: To Be Filled By O.E.M. dmi.product.name: To Be Filled By O.E.M. dmi.product.sku: To Be Filled By O.E.M. dmi.product.version: To Be Filled By O.E.M. dmi.sys.vendor: To Be Filled By O.E.M. version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.97-1ubuntu1 version.libgl1-mesa-dri: libgl1-mesa-dri 19.0.2-1ubuntu1.1 version.libgl1-mesa-glx: libgl1-mesa-glx N/A version.xserver-xorg-core: xserver-xorg-core 2:1.20.4-1ubuntu3 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.0.1-0ubuntu1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20180925-2 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1 ** Affects: xorg (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug disco ubuntu -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to xorg in Ubuntu. https://bugs.launchpad.net/bugs/1836434 Title: can not able to browse site which needed adobe flash player and latest graphic drivers Status in xorg package in Ubuntu: New Bug description: can not able to browse site which needed adobe flash player and latest graphic drivers. and also can't ab;e to access the settings of ubuntu ProblemType: Bug DistroRelease: Ubuntu 19.04 Package: xorg 1:7.7+19ubuntu12 ProcVersionSignature: Ubuntu 5.0.0-20.21-generic 5.0.8 Uname: Linux 5.0.0-20-generic x86_64 ApportVersion: 2.20.10-0ubuntu27.1 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Sat Jul 13 10:39:46 2019 DistUpgraded: 2019-05-23 11:48:24,738 ERROR got error from PostInstallScript ./xorg_fix_proprietary.py (g-exec-error-quark: Failed to execute child process “./xorg_fix_proprietary.py” (No such file or directory) (8)) DistroCodename: disco DistroVariant: ubuntu DkmsStatus: anbox, 1, 5.0.0-19-generic, x86_64: installed anbox, 1, 5.0.0-20-generic, x86_64: installed ExtraDebuggingInterest: Yes, including running git bisection searches GraphicsCard: NVIDIA Corporation GF119 [GeForce GT 610] [10de:104a] (rev a1) (prog-if 00 [VGA controller]) Subsystem: ASUSTeK Computer Inc. GF119 [GeForce GT 610] [1043:8496] InstallationDate: Installed on 2019-04-15 (88 days ago) InstallationMedia: Ubuntu 18.10 "Cosmic Cuttlefish" - Release amd64 (20181017.3) MachineType: To Be Filled By O.E.M. To Be Filled By O.E.M. ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.0.0-20-generic root=UUID=fe96674e-a634-4474-9fab-b79d0d3d0a5b ro quiet splash vt.handoff=1 SourcePackage: xorg UpgradeStatus: Upgraded to disco on 2019-05-23 (50 days ago) dmi.bios.date: 03/27/2017 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: P1.20 dmi.board.name: H91M-XT
