[Touch-packages] [Bug 1766169] Re: systemd-journald crashed with SIGABRT in __GI___pthread_timedjoin_ex()
*** This bug is a duplicate of bug 1754214 *** https://bugs.launchpad.net/bugs/1754214 Thank you for taking the time to report this crash and helping to make this software better. This particular crash has already been reported and is a duplicate of bug #1754214, so is being marked as such. Please look at the other bug report to see if there is any missing information that you can provide, or to see if there is a workaround for the bug. Additionally, any further discussion regarding the bug should occur in the other report. Please continue to report any other bugs you may find. ** Attachment removed: "CoreDump.gz" https://bugs.launchpad.net/bugs/1766169/+attachment/5125727/+files/CoreDump.gz ** Attachment removed: "Disassembly.txt" https://bugs.launchpad.net/bugs/1766169/+attachment/5125730/+files/Disassembly.txt ** Attachment removed: "ProcMaps.txt" https://bugs.launchpad.net/bugs/1766169/+attachment/5125737/+files/ProcMaps.txt ** Attachment removed: "ProcStatus.txt" https://bugs.launchpad.net/bugs/1766169/+attachment/5125739/+files/ProcStatus.txt ** Attachment removed: "Registers.txt" https://bugs.launchpad.net/bugs/1766169/+attachment/5125740/+files/Registers.txt ** Attachment removed: "Stacktrace.txt" https://bugs.launchpad.net/bugs/1766169/+attachment/5125741/+files/Stacktrace.txt ** Attachment removed: "ThreadStacktrace.txt" https://bugs.launchpad.net/bugs/1766169/+attachment/5125742/+files/ThreadStacktrace.txt ** This bug has been marked a duplicate of private bug 1754214 ** Information type changed from Private to Public ** Tags removed: need-amd64-retrace -- 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/1766169 Title: systemd-journald crashed with SIGABRT in __GI___pthread_timedjoin_ex() Status in systemd package in Ubuntu: New Bug description: non-tech person - no further info ProblemType: Crash DistroRelease: Ubuntu 18.04 Package: systemd 237-3ubuntu8 ProcVersionSignature: Ubuntu 4.15.0-15.16-generic 4.15.15 Uname: Linux 4.15.0-15-generic x86_64 ApportVersion: 2.20.9-0ubuntu5 Architecture: amd64 CrashCounter: 1 Date: Mon Apr 23 06:52:09 2018 ExecutablePath: /lib/systemd/systemd-journald InstallationDate: Installed on 2018-03-28 (25 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Alpha amd64 (20180327) MachineType: LENOVO 20KHCTO1WW ProcCmdline: /lib/systemd/systemd-journald ProcEnviron: LANG=en_GB.UTF-8 LANGUAGE=en_GB:en PATH=(custom, no user) ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.15.0-15-generic.efi.signed root=/dev/mapper/ubuntu--vg-root ro quiet splash vt.handoff=1 Signal: 6 SourcePackage: systemd StacktraceTop: __GI___pthread_timedjoin_ex (threadid=13976813136, thread_return=0x0, abstime=0x0, block=) at pthread_join_common.c:89 ?? () from /lib/systemd/libsystemd-shared-237.so ?? () from /lib/systemd/libsystemd-shared-237.so journal_file_append_object () from /lib/systemd/libsystemd-shared-237.so ?? () from /lib/systemd/libsystemd-shared-237.so SystemdDelta: [EXTENDED] /lib/systemd/system/rc-local.service → /lib/systemd/system/rc-local.service.d/debian.conf [EXTENDED] /lib/systemd/system/user@.service → /lib/systemd/system/user@.service.d/timeout.conf 2 overridden configuration files found. Title: systemd-journald crashed with SIGABRT in __GI___pthread_timedjoin_ex() UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: dmi.bios.date: 02/27/2018 dmi.bios.vendor: LENOVO dmi.bios.version: N23ET37W (1.12 ) dmi.board.asset.tag: Not Available dmi.board.name: 20KHCTO1WW dmi.board.vendor: LENOVO dmi.board.version: SDK0J40697 WIN dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: None dmi.modalias: dmi:bvnLENOVO:bvrN23ET37W(1.12):bd02/27/2018:svnLENOVO:pn20KHCTO1WW:pvrThinkPadX1Carbon6th:rvnLENOVO:rn20KHCTO1WW:rvrSDK0J40697WIN:cvnLENOVO:ct10:cvrNone: dmi.product.family: ThinkPad X1 Carbon 6th dmi.product.name: 20KHCTO1WW dmi.product.version: ThinkPad X1 Carbon 6th dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1766169/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1766063] Re: mm (Myanmar / Burmese) for zawgyi keyboard layout
Not sure what you consider was done. That repository imports automatically from the upstream one. What I said, i.e. that it will be included in the xkb-data package only in 18.10, still stands. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to xkeyboard-config in Ubuntu. https://bugs.launchpad.net/bugs/1766063 Title: mm (Myanmar / Burmese) for zawgyi keyboard layout Status in xkeyboard-config: Fix Released Status in xkeyboard-config package in Ubuntu: Triaged Status in xkeyboard-config package in Arch Linux: New Status in xkeyboard-config package in CentOS: New Status in xkeyboard-config package in Debian: Fix Released Status in xkeyboard-config package in Fedora: New Status in xkeyboard-config package in Gentoo Linux: New Status in xkeyboard-config package in Unity Linux: New Bug description: https://bugs.freedesktop.org/show_bug.cgi?id=106169 New Keyboard Layout addition in Myanmar / Burmese --- New Keyboard Layout --- Added New Keyboard Layout - Burmese Zawgyi Keyboard This is similar to Burmese MM. Its most popular keyboard in Burmese. To manage notifications about this bug go to: https://bugs.launchpad.net/xkeyboard-config/+bug/1766063/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1766160] [NEW] package libavahi-common3:amd64 0.6.32~rc+dfsg-1ubuntu2 failed to install/upgrade: le paquet libavahi-common3:amd64 n'est pas prêt pour la configuration configurat
Public bug reported: new user and i speak french ProblemType: Package DistroRelease: Ubuntu 16.04 Package: libavahi-common3:amd64 0.6.32~rc+dfsg-1ubuntu2 ProcVersionSignature: Ubuntu 4.13.0-38.43~16.04.1-generic 4.13.16 Uname: Linux 4.13.0-38-generic x86_64 ApportVersion: 2.20.1-0ubuntu2.16 Architecture: amd64 Date: Sun Apr 22 22:29:27 2018 Dependencies: gcc-6-base 6.0.1-0ubuntu1 libavahi-common-data 0.6.32~rc+dfsg-1ubuntu2.1 libc6 2.23-0ubuntu10 libgcc1 1:6.0.1-0ubuntu1 ErrorMessage: le paquet libavahi-common3:amd64 n'est pas prêt pour la configuration configuration impossible (état actuel « half-installed ») InstallationDate: Installed on 2018-02-10 (71 days ago) InstallationMedia: Ubuntu 16.04.3 LTS "Xenial Xerus" - Release amd64 (20170801) RelatedPackageVersions: dpkg 1.18.4ubuntu1.4 apt 1.2.26 SourcePackage: avahi Title: package libavahi-common3:amd64 0.6.32~rc+dfsg-1ubuntu2 failed to install/upgrade: le paquet libavahi-common3:amd64 n'est pas prêt pour la configuration configuration impossible (état actuel « half-installed ») UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: avahi (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-package xenial -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to avahi in Ubuntu. https://bugs.launchpad.net/bugs/1766160 Title: package libavahi-common3:amd64 0.6.32~rc+dfsg-1ubuntu2 failed to install/upgrade: le paquet libavahi-common3:amd64 n'est pas prêt pour la configuration configuration impossible (état actuel « half- installed ») Status in avahi package in Ubuntu: New Bug description: new user and i speak french ProblemType: Package DistroRelease: Ubuntu 16.04 Package: libavahi-common3:amd64 0.6.32~rc+dfsg-1ubuntu2 ProcVersionSignature: Ubuntu 4.13.0-38.43~16.04.1-generic 4.13.16 Uname: Linux 4.13.0-38-generic x86_64 ApportVersion: 2.20.1-0ubuntu2.16 Architecture: amd64 Date: Sun Apr 22 22:29:27 2018 Dependencies: gcc-6-base 6.0.1-0ubuntu1 libavahi-common-data 0.6.32~rc+dfsg-1ubuntu2.1 libc6 2.23-0ubuntu10 libgcc1 1:6.0.1-0ubuntu1 ErrorMessage: le paquet libavahi-common3:amd64 n'est pas prêt pour la configuration configuration impossible (état actuel « half-installed ») InstallationDate: Installed on 2018-02-10 (71 days ago) InstallationMedia: Ubuntu 16.04.3 LTS "Xenial Xerus" - Release amd64 (20170801) RelatedPackageVersions: dpkg 1.18.4ubuntu1.4 apt 1.2.26 SourcePackage: avahi Title: package libavahi-common3:amd64 0.6.32~rc+dfsg-1ubuntu2 failed to install/upgrade: le paquet libavahi-common3:amd64 n'est pas prêt pour la configuration configuration impossible (état actuel « half-installed ») UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/avahi/+bug/1766160/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1766158] [NEW] package ca-certificates 20180409 failed to install/upgrade: triggers looping, abandoned
Public bug reported: 16.04 to 18.04 update bug ProblemType: Package DistroRelease: Ubuntu 18.04 Package: ca-certificates 20180409 ProcVersionSignature: Ubuntu 4.15.0-15.16-generic 4.15.15 Uname: Linux 4.15.0-15-generic x86_64 ApportVersion: 2.20.9-0ubuntu6 Architecture: amd64 Date: Sun Apr 22 22:48:25 2018 DistributionChannelDescriptor: # This is a distribution channel descriptor # For more information see http://wiki.ubuntu.com/DistributionChannelDescriptor canonical-oem-somerville-xenial-amd64-20160624-2 ErrorMessage: triggers looping, abandoned InstallationDate: Installed on 2018-04-03 (19 days ago) InstallationMedia: Ubuntu 16.04 "Xenial" - Build amd64 LIVE Binary 20160624-10:47 PackageArchitecture: all Python3Details: /usr/bin/python3.6, Python 3.6.5, python3-minimal, 3.6.5-3 PythonDetails: /usr/bin/python2.7, Python 2.7.15rc1, python-minimal, 2.7.15~rc1-1 RelatedPackageVersions: dpkg 1.19.0.5ubuntu2 apt 1.6.1 SourcePackage: ca-certificates Title: package ca-certificates 20180409 failed to install/upgrade: triggers looping, abandoned UpgradeStatus: Upgraded to bionic on 2018-04-03 (19 days ago) ** Affects: ca-certificates (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-package bionic -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to ca-certificates in Ubuntu. https://bugs.launchpad.net/bugs/1766158 Title: package ca-certificates 20180409 failed to install/upgrade: triggers looping, abandoned Status in ca-certificates package in Ubuntu: New Bug description: 16.04 to 18.04 update bug ProblemType: Package DistroRelease: Ubuntu 18.04 Package: ca-certificates 20180409 ProcVersionSignature: Ubuntu 4.15.0-15.16-generic 4.15.15 Uname: Linux 4.15.0-15-generic x86_64 ApportVersion: 2.20.9-0ubuntu6 Architecture: amd64 Date: Sun Apr 22 22:48:25 2018 DistributionChannelDescriptor: # This is a distribution channel descriptor # For more information see http://wiki.ubuntu.com/DistributionChannelDescriptor canonical-oem-somerville-xenial-amd64-20160624-2 ErrorMessage: triggers looping, abandoned InstallationDate: Installed on 2018-04-03 (19 days ago) InstallationMedia: Ubuntu 16.04 "Xenial" - Build amd64 LIVE Binary 20160624-10:47 PackageArchitecture: all Python3Details: /usr/bin/python3.6, Python 3.6.5, python3-minimal, 3.6.5-3 PythonDetails: /usr/bin/python2.7, Python 2.7.15rc1, python-minimal, 2.7.15~rc1-1 RelatedPackageVersions: dpkg 1.19.0.5ubuntu2 apt 1.6.1 SourcePackage: ca-certificates Title: package ca-certificates 20180409 failed to install/upgrade: triggers looping, abandoned UpgradeStatus: Upgraded to bionic on 2018-04-03 (19 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ca-certificates/+bug/1766158/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1688364] Re: Non existent host causes 100% cpu utilization by systemd-resolved and dnsmasq
[Expired for dnsmasq (Ubuntu) because there has been no activity for 60 days.] ** Changed in: dnsmasq (Ubuntu) Status: Incomplete => Expired -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to resolvconf in Ubuntu. https://bugs.launchpad.net/bugs/1688364 Title: Non existent host causes 100% cpu utilization by systemd-resolved and dnsmasq Status in dnsmasq package in Ubuntu: Expired Status in network-manager package in Ubuntu: Expired Status in resolvconf package in Ubuntu: Expired Bug description: May 04 13:32:07 cannon-fodder dnsmasq[8101]: query[A] cf.shareasimage.com from 127.0.0.1 May 04 13:32:07 cannon-fodder dnsmasq[8101]: forwarded cf.shareasimage.com to 127.0.0.53 May 04 13:32:07 cannon-fodder dnsmasq[8101]: query[A] cf.shareasimage.com from 127.0.0.1 May 04 13:32:07 cannon-fodder dnsmasq[8101]: forwarded cf.shareasimage.com to 127.0.0.53 May 04 13:32:07 cannon-fodder dnsmasq[8101]: query[A] googletagservices.com from 127.0.0.1 May 04 13:32:07 cannon-fodder dnsmasq[8101]: forwarded googletagservices.com to 127.0.0.53 May 04 13:32:07 cannon-fodder dnsmasq[8101]: query[A] cf.shareasimage.com from 127.0.0.1 May 04 13:32:07 cannon-fodder dnsmasq[8101]: forwarded cf.shareasimage.com to 127.0.0.53 May 04 13:32:07 cannon-fodder dnsmasq[8101]: query[A] cf.shareasimage.com from 127.0.0.1 May 04 13:32:07 cannon-fodder dnsmasq[8101]: forwarded cf.shareasimage.com to 127.0.0.53 May 04 13:32:07 cannon-fodder dnsmasq[8101]: query[A] googletagservices.com from 127.0.0.1 May 04 13:32:07 cannon-fodder dnsmasq[8101]: forwarded googletagservices.com to 127.0.0.53 May 04 13:32:07 cannon-fodder dnsmasq[8101]: query[A] cf.shareasimage.com from 127.0.0.1 May 04 13:32:07 cannon-fodder dnsmasq[8101]: forwarded cf.shareasimage.com to 127.0.0.53 May 04 13:32:07 cannon-fodder dnsmasq[8101]: query[A] cf.shareasimage.com from 127.0.0.1 May 04 13:32:07 cannon-fodder dnsmasq[8101]: forwarded cf.shareasimage.com to 127.0.0.53 May 04 13:32:07 cannon-fodder dnsmasq[8101]: query[A] googletagservices.com from 127.0.0.1 May 04 13:32:07 cannon-fodder dnsmasq[8101]: forwarded googletagservices.com to 127.0.0.53 May 04 13:32:07 cannon-fodder dnsmasq[8101]: query[A] cf.shareasimage.com from 127.0.0.1 May 04 13:32:07 cannon-fodder dnsmasq[8101]: forwarded cf.shareasimage.com to 127.0.0.53 May 04 13:32:07 cannon-fodder dnsmasq[8101]: query[A] cf.shareasimage.com from 127.0.0.1 May 04 13:32:07 cannon-fodder dnsmasq[8101]: forwarded cf.shareasimage.com to 127.0.0.53 May 04 13:32:07 cannon-fodder dnsmasq[8101]: query[A] googletagservices.com from 127.0.0.1 May 04 13:32:07 cannon-fodder dnsmasq[8101]: forwarded googletagservices.com to 127.0.0.53 May 04 13:32:07 cannon-fodder dnsmasq[8101]: query[A] cf.shareasimage.com from 127.0.0.1 May 04 13:32:07 cannon-fodder dnsmasq[8101]: forwarded cf.shareasimage.com to 127.0.0.53 May 04 13:32:07 cannon-fodder dnsmasq[8101]: query[A] cf.shareasimage.com from 127.0.0.1 May 04 13:32:07 cannon-fodder dnsmasq[8101]: forwarded cf.shareasimage.com to 127.0.0.53 May 04 13:32:07 cannon-fodder dnsmasq[8101]: query[A] googletagservices.com from 127.0.0.1 May 04 13:32:07 cannon-fodder dnsmasq[8101]: forwarded googletagservices.com to 127.0.0.53 May 04 13:32:07 cannon-fodder dnsmasq[8101]: query[A] cf.shareasimage.com from 127.0.0.1 May 04 13:32:07 cannon-fodder dnsmasq[8101]: forwarded cf.shareasimage.com to 127.0.0.53 May 04 13:32:07 cannon-fodder dnsmasq[8101]: query[A] cf.shareasimage.com from 127.0.0.1 May 04 13:32:07 cannon-fodder dnsmasq[8101]: forwarded cf.shareasimage.com to 127.0.0.53 May 04 13:32:07 cannon-fodder dnsmasq[8101]: query[A] googletagservices.com from 127.0.0.1 May 04 13:32:07 cannon-fodder dnsmasq[8101]: forwarded googletagservices.com to 127.0.0.53 May 04 13:32:07 cannon-fodder dnsmasq[8101]: query[A] cf.shareasimage.com from 127.0.0.1 May 04 13:32:07 cannon-fodder dnsmasq[8101]: forwarded cf.shareasimage.com to 127.0.0.53 May 04 13:32:07 cannon-fodder dnsmasq[8101]: query[A] cf.shareasimage.com from 127.0.0.1 May 04 13:32:07 cannon-fodder dnsmasq[8101]: forwarded cf.shareasimage.com to 127.0.0.53 May 04 13:32:07 cannon-fodder dnsmasq[8101]: query[A] googletagservices.com from 127.0.0.1 May 04 13:32:07 cannon-fodder dnsmasq[8101]: forwarded googletagservices.com to 127.0.0.53 May 04 13:32:07 cannon-fodder dnsmasq[8101]: query[A] cf.shareasimage.com from 127.0.0.1 May 04 13:32:07 cannon-fodder dnsmasq[8101]: forwarded cf.shareasimage.com to 127.0.0.53 May 04 13:32:07 cannon-fodder dnsmasq[8101]: query[A] cf.shareasimage.com from 127.0.0.1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/dnsmasq/+bug/1688364/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubsc
[Touch-packages] [Bug 1688364] Re: Non existent host causes 100% cpu utilization by systemd-resolved and dnsmasq
[Expired for network-manager (Ubuntu) because there has been no activity for 60 days.] ** Changed in: network-manager (Ubuntu) Status: Incomplete => Expired -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to resolvconf in Ubuntu. https://bugs.launchpad.net/bugs/1688364 Title: Non existent host causes 100% cpu utilization by systemd-resolved and dnsmasq Status in dnsmasq package in Ubuntu: Expired Status in network-manager package in Ubuntu: Expired Status in resolvconf package in Ubuntu: Expired Bug description: May 04 13:32:07 cannon-fodder dnsmasq[8101]: query[A] cf.shareasimage.com from 127.0.0.1 May 04 13:32:07 cannon-fodder dnsmasq[8101]: forwarded cf.shareasimage.com to 127.0.0.53 May 04 13:32:07 cannon-fodder dnsmasq[8101]: query[A] cf.shareasimage.com from 127.0.0.1 May 04 13:32:07 cannon-fodder dnsmasq[8101]: forwarded cf.shareasimage.com to 127.0.0.53 May 04 13:32:07 cannon-fodder dnsmasq[8101]: query[A] googletagservices.com from 127.0.0.1 May 04 13:32:07 cannon-fodder dnsmasq[8101]: forwarded googletagservices.com to 127.0.0.53 May 04 13:32:07 cannon-fodder dnsmasq[8101]: query[A] cf.shareasimage.com from 127.0.0.1 May 04 13:32:07 cannon-fodder dnsmasq[8101]: forwarded cf.shareasimage.com to 127.0.0.53 May 04 13:32:07 cannon-fodder dnsmasq[8101]: query[A] cf.shareasimage.com from 127.0.0.1 May 04 13:32:07 cannon-fodder dnsmasq[8101]: forwarded cf.shareasimage.com to 127.0.0.53 May 04 13:32:07 cannon-fodder dnsmasq[8101]: query[A] googletagservices.com from 127.0.0.1 May 04 13:32:07 cannon-fodder dnsmasq[8101]: forwarded googletagservices.com to 127.0.0.53 May 04 13:32:07 cannon-fodder dnsmasq[8101]: query[A] cf.shareasimage.com from 127.0.0.1 May 04 13:32:07 cannon-fodder dnsmasq[8101]: forwarded cf.shareasimage.com to 127.0.0.53 May 04 13:32:07 cannon-fodder dnsmasq[8101]: query[A] cf.shareasimage.com from 127.0.0.1 May 04 13:32:07 cannon-fodder dnsmasq[8101]: forwarded cf.shareasimage.com to 127.0.0.53 May 04 13:32:07 cannon-fodder dnsmasq[8101]: query[A] googletagservices.com from 127.0.0.1 May 04 13:32:07 cannon-fodder dnsmasq[8101]: forwarded googletagservices.com to 127.0.0.53 May 04 13:32:07 cannon-fodder dnsmasq[8101]: query[A] cf.shareasimage.com from 127.0.0.1 May 04 13:32:07 cannon-fodder dnsmasq[8101]: forwarded cf.shareasimage.com to 127.0.0.53 May 04 13:32:07 cannon-fodder dnsmasq[8101]: query[A] cf.shareasimage.com from 127.0.0.1 May 04 13:32:07 cannon-fodder dnsmasq[8101]: forwarded cf.shareasimage.com to 127.0.0.53 May 04 13:32:07 cannon-fodder dnsmasq[8101]: query[A] googletagservices.com from 127.0.0.1 May 04 13:32:07 cannon-fodder dnsmasq[8101]: forwarded googletagservices.com to 127.0.0.53 May 04 13:32:07 cannon-fodder dnsmasq[8101]: query[A] cf.shareasimage.com from 127.0.0.1 May 04 13:32:07 cannon-fodder dnsmasq[8101]: forwarded cf.shareasimage.com to 127.0.0.53 May 04 13:32:07 cannon-fodder dnsmasq[8101]: query[A] cf.shareasimage.com from 127.0.0.1 May 04 13:32:07 cannon-fodder dnsmasq[8101]: forwarded cf.shareasimage.com to 127.0.0.53 May 04 13:32:07 cannon-fodder dnsmasq[8101]: query[A] googletagservices.com from 127.0.0.1 May 04 13:32:07 cannon-fodder dnsmasq[8101]: forwarded googletagservices.com to 127.0.0.53 May 04 13:32:07 cannon-fodder dnsmasq[8101]: query[A] cf.shareasimage.com from 127.0.0.1 May 04 13:32:07 cannon-fodder dnsmasq[8101]: forwarded cf.shareasimage.com to 127.0.0.53 May 04 13:32:07 cannon-fodder dnsmasq[8101]: query[A] cf.shareasimage.com from 127.0.0.1 May 04 13:32:07 cannon-fodder dnsmasq[8101]: forwarded cf.shareasimage.com to 127.0.0.53 May 04 13:32:07 cannon-fodder dnsmasq[8101]: query[A] googletagservices.com from 127.0.0.1 May 04 13:32:07 cannon-fodder dnsmasq[8101]: forwarded googletagservices.com to 127.0.0.53 May 04 13:32:07 cannon-fodder dnsmasq[8101]: query[A] cf.shareasimage.com from 127.0.0.1 May 04 13:32:07 cannon-fodder dnsmasq[8101]: forwarded cf.shareasimage.com to 127.0.0.53 May 04 13:32:07 cannon-fodder dnsmasq[8101]: query[A] cf.shareasimage.com from 127.0.0.1 May 04 13:32:07 cannon-fodder dnsmasq[8101]: forwarded cf.shareasimage.com to 127.0.0.53 May 04 13:32:07 cannon-fodder dnsmasq[8101]: query[A] googletagservices.com from 127.0.0.1 May 04 13:32:07 cannon-fodder dnsmasq[8101]: forwarded googletagservices.com to 127.0.0.53 May 04 13:32:07 cannon-fodder dnsmasq[8101]: query[A] cf.shareasimage.com from 127.0.0.1 May 04 13:32:07 cannon-fodder dnsmasq[8101]: forwarded cf.shareasimage.com to 127.0.0.53 May 04 13:32:07 cannon-fodder dnsmasq[8101]: query[A] cf.shareasimage.com from 127.0.0.1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/dnsmasq/+bug/1688364/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launc
[Touch-packages] [Bug 1688364] Re: Non existent host causes 100% cpu utilization by systemd-resolved and dnsmasq
[Expired for resolvconf (Ubuntu) because there has been no activity for 60 days.] ** Changed in: resolvconf (Ubuntu) Status: Incomplete => Expired -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to resolvconf in Ubuntu. https://bugs.launchpad.net/bugs/1688364 Title: Non existent host causes 100% cpu utilization by systemd-resolved and dnsmasq Status in dnsmasq package in Ubuntu: Expired Status in network-manager package in Ubuntu: Expired Status in resolvconf package in Ubuntu: Expired Bug description: May 04 13:32:07 cannon-fodder dnsmasq[8101]: query[A] cf.shareasimage.com from 127.0.0.1 May 04 13:32:07 cannon-fodder dnsmasq[8101]: forwarded cf.shareasimage.com to 127.0.0.53 May 04 13:32:07 cannon-fodder dnsmasq[8101]: query[A] cf.shareasimage.com from 127.0.0.1 May 04 13:32:07 cannon-fodder dnsmasq[8101]: forwarded cf.shareasimage.com to 127.0.0.53 May 04 13:32:07 cannon-fodder dnsmasq[8101]: query[A] googletagservices.com from 127.0.0.1 May 04 13:32:07 cannon-fodder dnsmasq[8101]: forwarded googletagservices.com to 127.0.0.53 May 04 13:32:07 cannon-fodder dnsmasq[8101]: query[A] cf.shareasimage.com from 127.0.0.1 May 04 13:32:07 cannon-fodder dnsmasq[8101]: forwarded cf.shareasimage.com to 127.0.0.53 May 04 13:32:07 cannon-fodder dnsmasq[8101]: query[A] cf.shareasimage.com from 127.0.0.1 May 04 13:32:07 cannon-fodder dnsmasq[8101]: forwarded cf.shareasimage.com to 127.0.0.53 May 04 13:32:07 cannon-fodder dnsmasq[8101]: query[A] googletagservices.com from 127.0.0.1 May 04 13:32:07 cannon-fodder dnsmasq[8101]: forwarded googletagservices.com to 127.0.0.53 May 04 13:32:07 cannon-fodder dnsmasq[8101]: query[A] cf.shareasimage.com from 127.0.0.1 May 04 13:32:07 cannon-fodder dnsmasq[8101]: forwarded cf.shareasimage.com to 127.0.0.53 May 04 13:32:07 cannon-fodder dnsmasq[8101]: query[A] cf.shareasimage.com from 127.0.0.1 May 04 13:32:07 cannon-fodder dnsmasq[8101]: forwarded cf.shareasimage.com to 127.0.0.53 May 04 13:32:07 cannon-fodder dnsmasq[8101]: query[A] googletagservices.com from 127.0.0.1 May 04 13:32:07 cannon-fodder dnsmasq[8101]: forwarded googletagservices.com to 127.0.0.53 May 04 13:32:07 cannon-fodder dnsmasq[8101]: query[A] cf.shareasimage.com from 127.0.0.1 May 04 13:32:07 cannon-fodder dnsmasq[8101]: forwarded cf.shareasimage.com to 127.0.0.53 May 04 13:32:07 cannon-fodder dnsmasq[8101]: query[A] cf.shareasimage.com from 127.0.0.1 May 04 13:32:07 cannon-fodder dnsmasq[8101]: forwarded cf.shareasimage.com to 127.0.0.53 May 04 13:32:07 cannon-fodder dnsmasq[8101]: query[A] googletagservices.com from 127.0.0.1 May 04 13:32:07 cannon-fodder dnsmasq[8101]: forwarded googletagservices.com to 127.0.0.53 May 04 13:32:07 cannon-fodder dnsmasq[8101]: query[A] cf.shareasimage.com from 127.0.0.1 May 04 13:32:07 cannon-fodder dnsmasq[8101]: forwarded cf.shareasimage.com to 127.0.0.53 May 04 13:32:07 cannon-fodder dnsmasq[8101]: query[A] cf.shareasimage.com from 127.0.0.1 May 04 13:32:07 cannon-fodder dnsmasq[8101]: forwarded cf.shareasimage.com to 127.0.0.53 May 04 13:32:07 cannon-fodder dnsmasq[8101]: query[A] googletagservices.com from 127.0.0.1 May 04 13:32:07 cannon-fodder dnsmasq[8101]: forwarded googletagservices.com to 127.0.0.53 May 04 13:32:07 cannon-fodder dnsmasq[8101]: query[A] cf.shareasimage.com from 127.0.0.1 May 04 13:32:07 cannon-fodder dnsmasq[8101]: forwarded cf.shareasimage.com to 127.0.0.53 May 04 13:32:07 cannon-fodder dnsmasq[8101]: query[A] cf.shareasimage.com from 127.0.0.1 May 04 13:32:07 cannon-fodder dnsmasq[8101]: forwarded cf.shareasimage.com to 127.0.0.53 May 04 13:32:07 cannon-fodder dnsmasq[8101]: query[A] googletagservices.com from 127.0.0.1 May 04 13:32:07 cannon-fodder dnsmasq[8101]: forwarded googletagservices.com to 127.0.0.53 May 04 13:32:07 cannon-fodder dnsmasq[8101]: query[A] cf.shareasimage.com from 127.0.0.1 May 04 13:32:07 cannon-fodder dnsmasq[8101]: forwarded cf.shareasimage.com to 127.0.0.53 May 04 13:32:07 cannon-fodder dnsmasq[8101]: query[A] cf.shareasimage.com from 127.0.0.1 May 04 13:32:07 cannon-fodder dnsmasq[8101]: forwarded cf.shareasimage.com to 127.0.0.53 May 04 13:32:07 cannon-fodder dnsmasq[8101]: query[A] googletagservices.com from 127.0.0.1 May 04 13:32:07 cannon-fodder dnsmasq[8101]: forwarded googletagservices.com to 127.0.0.53 May 04 13:32:07 cannon-fodder dnsmasq[8101]: query[A] cf.shareasimage.com from 127.0.0.1 May 04 13:32:07 cannon-fodder dnsmasq[8101]: forwarded cf.shareasimage.com to 127.0.0.53 May 04 13:32:07 cannon-fodder dnsmasq[8101]: query[A] cf.shareasimage.com from 127.0.0.1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/dnsmasq/+bug/1688364/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net U
[Touch-packages] [Bug 1766063] Re: mm (Myanmar / Burmese) for zawgyi keyboard layout
Done https://bazaar.launchpad.net/~alexeyten/xkeyboard-config/master/revision/1961 -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to xkeyboard-config in Ubuntu. https://bugs.launchpad.net/bugs/1766063 Title: mm (Myanmar / Burmese) for zawgyi keyboard layout Status in xkeyboard-config: Fix Released Status in xkeyboard-config package in Ubuntu: Triaged Status in xkeyboard-config package in Arch Linux: New Status in xkeyboard-config package in CentOS: New Status in xkeyboard-config package in Debian: Fix Released Status in xkeyboard-config package in Fedora: New Status in xkeyboard-config package in Gentoo Linux: New Status in xkeyboard-config package in Unity Linux: New Bug description: https://bugs.freedesktop.org/show_bug.cgi?id=106169 New Keyboard Layout addition in Myanmar / Burmese --- New Keyboard Layout --- Added New Keyboard Layout - Burmese Zawgyi Keyboard This is similar to Burmese MM. Its most popular keyboard in Burmese. To manage notifications about this bug go to: https://bugs.launchpad.net/xkeyboard-config/+bug/1766063/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1762465] Re: Nautilus sidebar theming is confusing
Same as the design of the side bar in http://news.google.com - one background for icons and labels. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to ubuntu-themes in Ubuntu. https://bugs.launchpad.net/bugs/1762465 Title: Nautilus sidebar theming is confusing Status in Ubuntu theme: Confirmed Status in ubuntu-themes package in Ubuntu: Confirmed Bug description: The new theming of the Nautilus sidebar is confusing to users. The icons and the icon labels have a different background colour, and when a specific location is selected the background colour of the selected icon changes to be the same as the background colour of the labels, while the other icons have a darker background colour. This is giving the impression that the text labels are a hierarchy of the icon, rather than simply being labels associated with each icon. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-themes/+bug/1762465/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 994921] Re: 'ubuntu-bug /var/crash/app.crash' (and even more so, 'apport-cli -c /var/crash/app.crash') should still allow manual bug filing in stable releases
I've just logged bug 1766148 to resolve the above in Gnome Shell.
--
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/994921
Title:
'ubuntu-bug /var/crash/app.crash' (and even more so, 'apport-cli -c
/var/crash/app.crash') should still allow manual bug filing in stable
releases
Status in apport package in Ubuntu:
Won't Fix
Status in apport source package in Precise:
Won't Fix
Status in apport source package in Quantal:
Won't Fix
Bug description:
---
WORKAROUND:
comment out line 23 ("'problem_types': ['Bug', 'Package'],") in
'/etc/apport/crashdb.conf'.
---
The crash database work has made it much harder for users to enable apport
bug filing for crashes in stable Ubuntu releases, even for those who could
otherwise contribute useful bug reports. "Comment out line 23 of
/etc/apport/crashdb.conf" is not particularly straightforward.
One thing that would mitigate this is if the users could still run one of the
following commands to manually submit a bug report about a given crash:
1) 'ubuntu-bug /var/crash/application.crash';
2) and even more so, 'apport-cli -c /var/crash/app.crash' (as for now, it
quietly exits without explanation after pressing the 'S' key instead of sending
a crash report, as stated in duplicate bug #992064).
The fact that this is also disabled by the crashdb settings is a tad
inconvenient. I think the manual command should be allowed to work even
post-release.
---
ProblemType: Bug
DistroRelease: Ubuntu 12.04
Package: apport 2.0.1-0ubuntu7
ProcVersionSignature: Ubuntu 3.2.0-24.37-generic 3.2.14
Uname: Linux 3.2.0-24-generic x86_64
ApportVersion: 2.0.1-0ubuntu7
Architecture: amd64
CheckboxSubmission: 017452a27eca3c8b498abbfa5ef91db9
CheckboxSystem: ecaaad6fa1e0799a0aa1126bf620f39e
Date: Fri May 4 17:17:43 2012
InstallationMedia: Ubuntu 10.04.1 LTS "Lucid Lynx" - Release amd64
(20100816.1)
PackageArchitecture: all
ProcEnviron:
TERM=xterm
PATH=(custom, user)
LANG=en_US.UTF-8
SHELL=/bin/bash
SourcePackage: apport
UpgradeStatus: Upgraded to precise on 2011-11-08 (178 days ago)
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/apport/+bug/994921/+subscriptions
--
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 994921] Re: 'ubuntu-bug /var/crash/app.crash' (and even more so, 'apport-cli -c /var/crash/app.crash') should still allow manual bug filing in stable releases
I think it might be possible for any user to see their own automatic
crash reports, but the process is a little obfuscated.
If you're using Unity then you can open:
System Settings >
Security & Privacy >
Diagnostics >
Show Previous Reports
But I can't find any such option in gnome-control-center or 18.04. So
you then have to make the link yourself:
https://errors.ubuntu.com/user/ID
where ID is the contents of /var/lib/whoopsie/whoopsie-id
So you can try running this command to open it:
xdg-open https://errors.ubuntu.com/user/`sudo cat /var/lib/whoopsie
/whoopsie-id`
--
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/994921
Title:
'ubuntu-bug /var/crash/app.crash' (and even more so, 'apport-cli -c
/var/crash/app.crash') should still allow manual bug filing in stable
releases
Status in apport package in Ubuntu:
Won't Fix
Status in apport source package in Precise:
Won't Fix
Status in apport source package in Quantal:
Won't Fix
Bug description:
---
WORKAROUND:
comment out line 23 ("'problem_types': ['Bug', 'Package'],") in
'/etc/apport/crashdb.conf'.
---
The crash database work has made it much harder for users to enable apport
bug filing for crashes in stable Ubuntu releases, even for those who could
otherwise contribute useful bug reports. "Comment out line 23 of
/etc/apport/crashdb.conf" is not particularly straightforward.
One thing that would mitigate this is if the users could still run one of the
following commands to manually submit a bug report about a given crash:
1) 'ubuntu-bug /var/crash/application.crash';
2) and even more so, 'apport-cli -c /var/crash/app.crash' (as for now, it
quietly exits without explanation after pressing the 'S' key instead of sending
a crash report, as stated in duplicate bug #992064).
The fact that this is also disabled by the crashdb settings is a tad
inconvenient. I think the manual command should be allowed to work even
post-release.
---
ProblemType: Bug
DistroRelease: Ubuntu 12.04
Package: apport 2.0.1-0ubuntu7
ProcVersionSignature: Ubuntu 3.2.0-24.37-generic 3.2.14
Uname: Linux 3.2.0-24-generic x86_64
ApportVersion: 2.0.1-0ubuntu7
Architecture: amd64
CheckboxSubmission: 017452a27eca3c8b498abbfa5ef91db9
CheckboxSystem: ecaaad6fa1e0799a0aa1126bf620f39e
Date: Fri May 4 17:17:43 2012
InstallationMedia: Ubuntu 10.04.1 LTS "Lucid Lynx" - Release amd64
(20100816.1)
PackageArchitecture: all
ProcEnviron:
TERM=xterm
PATH=(custom, user)
LANG=en_US.UTF-8
SHELL=/bin/bash
SourcePackage: apport
UpgradeStatus: Upgraded to precise on 2011-11-08 (178 days ago)
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/apport/+bug/994921/+subscriptions
--
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 994921] Re: 'ubuntu-bug /var/crash/app.crash' (and even more so, 'apport-cli -c /var/crash/app.crash') should still allow manual bug filing in stable releases
Maybe the real problem is that reporters are unable to link to their
errors.ubuntu.com report (because if one doesn't have access then one
doesn't have _any_ access, as I understand it)?
https://bugs.launchpad.net/ubuntu/+source/apport/+bug/994921/comments/33
If the original justification still stands (linked above) then maybe
support for users viewing their own reports in e.u.c (so they can link
to them) would be useful, or perhaps Ubuntu should make Launchpad scale
to mass crash reports somehow...
--
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/994921
Title:
'ubuntu-bug /var/crash/app.crash' (and even more so, 'apport-cli -c
/var/crash/app.crash') should still allow manual bug filing in stable
releases
Status in apport package in Ubuntu:
Won't Fix
Status in apport source package in Precise:
Won't Fix
Status in apport source package in Quantal:
Won't Fix
Bug description:
---
WORKAROUND:
comment out line 23 ("'problem_types': ['Bug', 'Package'],") in
'/etc/apport/crashdb.conf'.
---
The crash database work has made it much harder for users to enable apport
bug filing for crashes in stable Ubuntu releases, even for those who could
otherwise contribute useful bug reports. "Comment out line 23 of
/etc/apport/crashdb.conf" is not particularly straightforward.
One thing that would mitigate this is if the users could still run one of the
following commands to manually submit a bug report about a given crash:
1) 'ubuntu-bug /var/crash/application.crash';
2) and even more so, 'apport-cli -c /var/crash/app.crash' (as for now, it
quietly exits without explanation after pressing the 'S' key instead of sending
a crash report, as stated in duplicate bug #992064).
The fact that this is also disabled by the crashdb settings is a tad
inconvenient. I think the manual command should be allowed to work even
post-release.
---
ProblemType: Bug
DistroRelease: Ubuntu 12.04
Package: apport 2.0.1-0ubuntu7
ProcVersionSignature: Ubuntu 3.2.0-24.37-generic 3.2.14
Uname: Linux 3.2.0-24-generic x86_64
ApportVersion: 2.0.1-0ubuntu7
Architecture: amd64
CheckboxSubmission: 017452a27eca3c8b498abbfa5ef91db9
CheckboxSystem: ecaaad6fa1e0799a0aa1126bf620f39e
Date: Fri May 4 17:17:43 2012
InstallationMedia: Ubuntu 10.04.1 LTS "Lucid Lynx" - Release amd64
(20100816.1)
PackageArchitecture: all
ProcEnviron:
TERM=xterm
PATH=(custom, user)
LANG=en_US.UTF-8
SHELL=/bin/bash
SourcePackage: apport
UpgradeStatus: Upgraded to precise on 2011-11-08 (178 days ago)
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/apport/+bug/994921/+subscriptions
--
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1765978] Re: Xubuntu 18.04: key to switch monitors brings up whiskermenu; can't switch monitor
** Package changed: wayland (Ubuntu) => xfce (Ubuntu) -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to wayland in Ubuntu. https://bugs.launchpad.net/bugs/1765978 Title: Xubuntu 18.04: key to switch monitors brings up whiskermenu; can't switch monitor Status in xfce package in Ubuntu: New Bug description: Using Xubuntu 18.04 daily on Notebook product: 80UD (LENOVO_MT_80UD_BU_idea_FM_Lenovo ideapad 110-15ISK) vendor: LENOVO version: Lenovo ideapad 110-15ISK serial: MP16LZHW width: 64 bits Linux Xubuntu-18-04 4.15.0-13-generic #14-Ubuntu SMP Sat Mar 17 13:44:27 UTC 2018 x86_64 x86_64 x86_64 GNU/Linux When an extra monitor is connected (through HDMI) pressing fn+f10 should only bring up a menu to switch monitors. But instead whiskermenu is opened before the monitor-switching-menu. No other fn+function key shows the same behaviour where it brings up anything else before it does what it is supposed to do.. I have the super key mapped to open whiskermenu. Please see: http://i.imgur.com/t0Jmzy6.png to see what I 'm seeing when pressing fn+f10. Actionparsnip suggests I report this as a bug against wayland. If there's more information I can provide, please let me know. Is this a bug? If so: which part of the system is likely to be doing this? To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xfce/+bug/1765978/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1718238] Re: Giant terminal icon is blocking out the Terminal window buttons
Confirmed by Brad and duplicate bug 1765704 that this bug is not fixed. ** Changed in: mutter (Ubuntu) Status: Fix Released => Confirmed ** Changed in: gnome-shell (Ubuntu) Status: Invalid => Confirmed ** Tags added: bionic -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to ubuntu-themes in Ubuntu. https://bugs.launchpad.net/bugs/1718238 Title: Giant terminal icon is blocking out the Terminal window buttons Status in gnome-shell package in Ubuntu: Confirmed Status in mutter package in Ubuntu: Confirmed Status in ubuntu-themes package in Ubuntu: Invalid Bug description: Upstream: https://gitlab.gnome.org/GNOME/mutter/issues/23 ProblemType: Bug DistroRelease: Ubuntu 17.10 Package: light-themes 16.10+17.10.20170918-0ubuntu1 ProcVersionSignature: Ubuntu 4.12.0-13.14-generic 4.12.10 Uname: Linux 4.12.0-13-generic x86_64 ApportVersion: 2.20.7-0ubuntu1 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Tue Sep 19 12:47:51 2017 InstallationDate: Installed on 2017-09-19 (0 days ago) InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Alpha amd64 (20170917) PackageArchitecture: all SourcePackage: ubuntu-themes UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1718238/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1765704] Re: bug in application menu icon in terminal
*** This bug is a duplicate of bug 1718238 *** https://bugs.launchpad.net/bugs/1718238 ** This bug has been marked a duplicate of bug 1718238 Giant terminal icon is blocking out the Terminal window buttons -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to ubuntu-themes in Ubuntu. https://bugs.launchpad.net/bugs/1765704 Title: bug in application menu icon in terminal Status in ubuntu-themes package in Ubuntu: New Bug description: /home/initu/Imagens/Captura de tela de 2018-04-19 18-23-01.png ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: light-themes 16.10+18.04.20180328-0ubuntu1 ProcVersionSignature: Ubuntu 4.15.0-15.16-generic 4.15.15 Uname: Linux 4.15.0-15-generic x86_64 ApportVersion: 2.20.9-0ubuntu5 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Fri Apr 20 10:06:27 2018 InstallationDate: Installed on 2018-04-06 (13 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Beta amd64 (20180404) PackageArchitecture: all SourcePackage: ubuntu-themes UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubuntu-themes/+bug/1765704/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1759795] Re: Unreadable text in dconf-editor header-bar when searching.
** Changed in: ubuntu-themes Status: In Progress => Fix Released ** Changed in: dconf-editor (Ubuntu) Status: Confirmed => Invalid -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to ubuntu-themes in Ubuntu. https://bugs.launchpad.net/bugs/1759795 Title: Unreadable text in dconf-editor header-bar when searching. Status in Ubuntu theme: Fix Released Status in dconf-editor package in Ubuntu: Invalid Status in ubuntu-themes package in Ubuntu: Fix Released Bug description: Screenshot attached. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-themes/+bug/1759795/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1760818] Re: gedit and gnome-calculator transparency/graphics corruption issue
Sounds like some config setting inherited from upgrades is triggering this. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to ubuntu-themes in Ubuntu. https://bugs.launchpad.net/bugs/1760818 Title: gedit and gnome-calculator transparency/graphics corruption issue Status in mutter package in Ubuntu: Confirmed Status in ubuntu-themes package in Ubuntu: Confirmed Bug description: In a "Ubuntu" (Xorg) session on 18.04 gedit and gnome-calculator suffer from a graphics issue where parts of their windows hold parts of wallpaper or other windows' contents as background. See attached screenshot. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: light-themes 16.10+18.04.20180328-0ubuntu1 ProcVersionSignature: Ubuntu 4.15.0-13.14-generic 4.15.10 Uname: Linux 4.15.0-13-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.20.9-0ubuntu2 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Tue Apr 3 09:12:31 2018 PackageArchitecture: all SourcePackage: ubuntu-themes UpgradeStatus: Upgraded to bionic on 2018-02-07 (54 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mutter/+bug/1760818/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1762465] Re: Nautilus sidebar theming is confusing
I think there are just too many columns. The icons and labels should have the same background colour. So one column instead of two. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to ubuntu-themes in Ubuntu. https://bugs.launchpad.net/bugs/1762465 Title: Nautilus sidebar theming is confusing Status in Ubuntu theme: Confirmed Status in ubuntu-themes package in Ubuntu: Confirmed Bug description: The new theming of the Nautilus sidebar is confusing to users. The icons and the icon labels have a different background colour, and when a specific location is selected the background colour of the selected icon changes to be the same as the background colour of the labels, while the other icons have a darker background colour. This is giving the impression that the text labels are a hierarchy of the icon, rather than simply being labels associated with each icon. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-themes/+bug/1762465/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1748147] Re: Upgrading systemd sets incorrect permissions on /var/log/
** No longer affects: systemd (Ubuntu) ** No longer affects: rsyslog (Ubuntu) -- 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/1748147 Title: Upgrading systemd sets incorrect permissions on /var/log/ Status in debhelper: New Status in debhelper package in Ubuntu: New Bug description: Upgrading or reinstalling the systemd package when using rsyslogd results in bad permissions (0755 instead of 0775) being set on /var/log/. As a consequence of this, rsyslogd can no longer create new files within this directory, resulting in lost log messages. The default configuration of rsyslogd provided by Ubuntu runs the daemon as syslog:syslog and sets ownership of /var/log to syslog:adm with mode 0775. Systemd's default tmpfiles configuration sets /var/log to 0755 in /usr/lib/tmpfiles.d/var.conf, however this is overridden in /usr/lib/tmpfiles.d/00rsyslog.conf which is provided by package rsyslog. It looks as though an upgrade of the systemd package fails to take /usr/lib/tmpfiles.d/00rsyslog.conf into account, as demonstrated below. This results in /var/log receiving mode 0755 instead of the expected 0775: nick @ log2.be1.ams1:~ $ lsb_release -a No LSB modules are available. Distributor ID: Ubuntu Description: Ubuntu 16.04.3 LTS Release: 16.04 Codename: xenial nick @ log2.be1.ams1:~ $ apt policy systemd systemd: Installed: 229-4ubuntu21.1 Candidate: 229-4ubuntu21.1 Version table: *** 229-4ubuntu21.1 500 500 http://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 229-4ubuntu4 500 500 http://archive.ubuntu.com/ubuntu xenial/main amd64 Packages nick @ log2.be1.ams1:~ $ apt policy rsyslog rsyslog: Installed: 8.16.0-1ubuntu3 Candidate: 8.16.0-1ubuntu3 Version table: *** 8.16.0-1ubuntu3 500 500 http://archive.ubuntu.com/ubuntu xenial/main amd64 Packages 100 /var/lib/dpkg/status nick @ log2.be1.ams1:~ $ grep -F /var/log /usr/lib/tmpfiles.d/var.conf d /var/log 0755 - - - f /var/log/wtmp 0664 root utmp - f /var/log/btmp 0600 root utmp - nick @ log2.be1.ams1:~ $ cat /usr/lib/tmpfiles.d/00rsyslog.conf # Override systemd's default tmpfiles.d/var.conf to make /var/log writable by # the syslog group, so that rsyslog can run as user. # See tmpfiles.d(5) for details. # Type PathMode UID GID Age Argument d /var/log 0775 root syslog - nick @ log2.be1.ams1:~ $ ls -ld /var/log drwxrwxr-x 8 root syslog 4096 Feb 7 13:45 /var/log nick @ log2.be1.ams1:~ $ sudo apt install --reinstall systemd Reading package lists... Done Building dependency tree Reading state information... Done 0 upgraded, 0 newly installed, 1 reinstalled, 0 to remove and 7 not upgraded. Need to get 3,634 kB of archives. After this operation, 0 B of additional disk space will be used. Get:1 http://archive.ubuntu.com/ubuntu xenial-updates/main amd64 systemd amd64 229-4ubuntu21.1 [3,634 kB] Fetched 3,634 kB in 0s (24.3 MB/s) (Reading database ... 86614 files and directories currently installed.) Preparing to unpack .../systemd_229-4ubuntu21.1_amd64.deb ... Unpacking systemd (229-4ubuntu21.1) over (229-4ubuntu21.1) ... Processing triggers for dbus (1.10.6-1ubuntu3.3) ... Processing triggers for ureadahead (0.100.0-19) ... Processing triggers for man-db (2.7.5-1) ... Setting up systemd (229-4ubuntu21.1) ... addgroup: The group `systemd-journal' already exists as a system group. Exiting. nick @ log2.be1.ams1:~ $ ls -ld /var/log drwxr-xr-x 8 root syslog 4096 Feb 7 13:45 /var/log To manage notifications about this bug go to: https://bugs.launchpad.net/debhelper/+bug/1748147/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1766140] [NEW] OpenGL Renderer window appears in tab list when playing a video
Public bug reported: Every time a web page plays a video in Epiphany, a window named "OpenGL Renderer" appears in the gnome-shell alt-tab list (but not in the overview), one for each video. If I have several pages open with several videos, I get several of these phantom windows. Selecting the window in the list does nothing. This started happening sometime during the beta, it didn't happen under 17.10 or after first upgrading to 18.04. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: epiphany-browser 3.28.1-1ubuntu1 ProcVersionSignature: Ubuntu 4.15.0-15.16-generic 4.15.15 Uname: Linux 4.15.0-15-generic x86_64 ApportVersion: 2.20.9-0ubuntu6 Architecture: amd64 CurrentDesktop: GNOME Date: Mon Apr 23 10:51:07 2018 InstallationDate: Installed on 2015-07-22 (1005 days ago) InstallationMedia: Ubuntu-GNOME 15.04 "Vivid Vervet" - Release amd64 (20150422) SourcePackage: epiphany-browser UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: epiphany-browser (Ubuntu) Importance: Undecided Status: New ** Affects: gst-plugins-base1.0 (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug bionic wayland-session ** Also affects: gst-plugins-base1.0 (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to gst-plugins-base1.0 in Ubuntu. https://bugs.launchpad.net/bugs/1766140 Title: OpenGL Renderer window appears in tab list when playing a video Status in epiphany-browser package in Ubuntu: New Status in gst-plugins-base1.0 package in Ubuntu: New Bug description: Every time a web page plays a video in Epiphany, a window named "OpenGL Renderer" appears in the gnome-shell alt-tab list (but not in the overview), one for each video. If I have several pages open with several videos, I get several of these phantom windows. Selecting the window in the list does nothing. This started happening sometime during the beta, it didn't happen under 17.10 or after first upgrading to 18.04. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: epiphany-browser 3.28.1-1ubuntu1 ProcVersionSignature: Ubuntu 4.15.0-15.16-generic 4.15.15 Uname: Linux 4.15.0-15-generic x86_64 ApportVersion: 2.20.9-0ubuntu6 Architecture: amd64 CurrentDesktop: GNOME Date: Mon Apr 23 10:51:07 2018 InstallationDate: Installed on 2015-07-22 (1005 days ago) InstallationMedia: Ubuntu-GNOME 15.04 "Vivid Vervet" - Release amd64 (20150422) SourcePackage: epiphany-browser UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/epiphany-browser/+bug/1766140/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1670031] Re: Wireless driver (QCA-9377) not working properly
>sudo sed -i 's/wifi.powersave = 3/wifi.powersave = 2/' /etc/NetworkManager/conf.d/default-wifi-powersave-on.conf It doesn't work. Transmission speed is very poor even after that. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to network-manager in Ubuntu. https://bugs.launchpad.net/bugs/1670031 Title: Wireless driver (QCA-9377) not working properly Status in network-manager package in Ubuntu: New Bug description: Hello guys, I have Lenovo Ideapad 500S-13ISK. It is bundled with Qualcomm Atheros QCA-9377 (rev 30) 802.11ac wireless card. Currently I have running Ubuntu 16.10 with all security updates. Wireless is dropping constantly. I tried different GNU/Linux distributions but the result is either same or worse. I assume is something related to NetworkManager and eventually Systemd. The thing is that I loose signal at some point but the network manager indicates that I have connection. After toggling Airplane mode it manages to continue to work properly but I am loosing the list with wireless connections which are available to be. For some reason it starts to show that I am connected through cable, instead of wireless. The only two ways to resolve constant drops in the signal I found is to toggle Airplane mode or restart NetworkManager. Both results to wrong indication and disables me from choosing another network. ➜ ~ lsb_release -rd Description: Ubuntu 16.10 Release: 16.10 ➜ ~ apt-cache policy network-manager network-manager: Installed: 1.2.4-0ubuntu1 Candidate: 1.2.4-0ubuntu1 Version table: *** 1.2.4-0ubuntu1 500 500 http://bg.archive.ubuntu.com/ubuntu yakkety/main amd64 Packages 100 /var/lib/dpkg/status To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1670031/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1766129] [NEW] Clicking any checkbox freezes the program
Public bug reported: Upgraded to 18.04 today and clicking any checkbox in Software & Updates freezes the program (at least, in the Communitheme Wayland session (`snap install communitheme --edge` 0.1 (73))). ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: software-properties-gtk 0.96.24.32.1 ProcVersionSignature: Ubuntu 4.15.0-15.16-generic 4.15.15 Uname: Linux 4.15.0-15-generic x86_64 ApportVersion: 2.20.9-0ubuntu6 Architecture: amd64 CurrentDesktop: communitheme:ubuntu:GNOME Date: Sun Apr 22 23:52:47 2018 InstallationDate: Installed on 2017-08-03 (262 days ago) InstallationMedia: Ubuntu 17.04 "Zesty Zapus" - Release amd64 (20170412) PackageArchitecture: all SourcePackage: software-properties UpgradeStatus: Upgraded to bionic on 2018-04-22 (0 days ago) ** Affects: software-properties (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug bionic wayland-session ** Description changed: Upgraded to 18.04 today and clicking any checkbox in Software & Updates - freezes the program. + freezes the program (at least, in the Communitheme Wayland session + (`snap install communitheme --edge` 0.1 (73))). ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: software-properties-gtk 0.96.24.32.1 ProcVersionSignature: Ubuntu 4.15.0-15.16-generic 4.15.15 Uname: Linux 4.15.0-15-generic x86_64 ApportVersion: 2.20.9-0ubuntu6 Architecture: amd64 CurrentDesktop: communitheme:ubuntu:GNOME Date: Sun Apr 22 23:52:47 2018 InstallationDate: Installed on 2017-08-03 (262 days ago) InstallationMedia: Ubuntu 17.04 "Zesty Zapus" - Release amd64 (20170412) PackageArchitecture: all SourcePackage: software-properties UpgradeStatus: Upgraded to bionic on 2018-04-22 (0 days ago) -- 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/1766129 Title: Clicking any checkbox freezes the program Status in software-properties package in Ubuntu: New Bug description: Upgraded to 18.04 today and clicking any checkbox in Software & Updates freezes the program (at least, in the Communitheme Wayland session (`snap install communitheme --edge` 0.1 (73))). ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: software-properties-gtk 0.96.24.32.1 ProcVersionSignature: Ubuntu 4.15.0-15.16-generic 4.15.15 Uname: Linux 4.15.0-15-generic x86_64 ApportVersion: 2.20.9-0ubuntu6 Architecture: amd64 CurrentDesktop: communitheme:ubuntu:GNOME Date: Sun Apr 22 23:52:47 2018 InstallationDate: Installed on 2017-08-03 (262 days ago) InstallationMedia: Ubuntu 17.04 "Zesty Zapus" - Release amd64 (20170412) PackageArchitecture: all SourcePackage: software-properties UpgradeStatus: Upgraded to bionic on 2018-04-22 (0 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/software-properties/+bug/1766129/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1764087] Re: Wrongly boots into low graphics mode
Thanks for the workaround to make wifi work - that could come in useful. I'm unsure whether your display info is relevant or not. As far as I am aware I only have one graphics controller/card/GPU integrated into the Processor - Intel® Core™ i5 CPU M 520 @ 2.40GHz × 4 and that is Intel® Ironlake Mobile with just the laptop screen as a monitor. Your output suggests 2 and/or 2 monitors? For completeness I add the following:- sudo lshw -c display *-display description: VGA compatible controller product: Core Processor Integrated Graphics Controller vendor: Intel Corporation physical id: 2 bus info: pci@:00:02.0 version: 02 width: 64 bits clock: 33MHz capabilities: msi pm vga_controller bus_master cap_list rom configuration: driver=i915 latency=0 resources: irq:26 memory:f200-f23f memory:d000-dfff ioport:1800(size=8) memory:c-d -- 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/1764087 Title: Wrongly boots into low graphics mode Status in xorg package in Ubuntu: New Bug description: Description: Ubuntu 16.04.4 LTS Release: 16.04 Lenovo T410 with VGA compatible controller [0300]: Intel Corporation Core Processor Integrated Graphics Controller [8086:0046] (rev 02) Booting from latest kernel ThinkPad-T410 4.13.0-38-generic #43~16.04.1-Ubuntu SMP Wed Mar 14 17:48:43 UTC 2018 x86_64 x86_64 x86_64 GNU/Linux goes into low graphics mode and also effects wi-fi connection insofar as it does not connect to my router. Whereas booting from 4.13.0-37-generic #42~16.04.1-Ubuntu SMP Wed Mar 7 16:03:28 UTC 2018 x86_64 x86_64 x86_64 GNU/Linux works most of the time but occasionally has the same effects. I have had to submit this report after booting from 4.13.0.37 in order to submit bug. ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: xorg 1:7.7+13ubuntu3 ProcVersionSignature: Ubuntu 4.13.0-37.42~16.04.1-generic 4.13.13 Uname: Linux 4.13.0-37-generic x86_64 .tmp.unity_support_test.0: ApportVersion: 2.20.1-0ubuntu2.15 Architecture: amd64 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: compiz CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0' CompositorUnredirectFSW: true CurrentDesktop: Unity Date: Sun Apr 15 10:40:31 2018 DistUpgraded: Fresh install DistroCodename: xenial DistroVariant: ubuntu ExtraDebuggingInterest: Yes, if not too technical GraphicsCard: Intel Corporation Core Processor Integrated Graphics Controller [8086:0046] (rev 02) (prog-if 00 [VGA controller]) Subsystem: Lenovo Core Processor Integrated Graphics Controller [17aa:215a] InstallationDate: Installed on 2016-09-24 (567 days ago) InstallationMedia: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 (20160719) MachineType: LENOVO 2519Y11 ProcEnviron: LANGUAGE=en_GB:en PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_GB.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.13.0-37-generic root=UUID=58d362c2-ed1e-479b-84f5-e5d8a782b08f ro quiet splash vt.handoff=7 SourcePackage: xorg Symptom: display UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 02/14/2013 dmi.bios.vendor: LENOVO dmi.bios.version: 6IET85WW (1.45 ) dmi.board.name: 2519Y11 dmi.board.vendor: LENOVO dmi.board.version: Not Available dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: Not Available dmi.modalias: dmi:bvnLENOVO:bvr6IET85WW(1.45):bd02/14/2013:svnLENOVO:pn2519Y11:pvrThinkPadT410:rvnLENOVO:rn2519Y11:rvrNotAvailable:cvnLENOVO:ct10:cvrNotAvailable: dmi.product.family: ThinkPad T410 dmi.product.name: 2519Y11 dmi.product.version: ThinkPad T410 dmi.sys.vendor: LENOVO version.compiz: compiz 1:0.9.12.3+16.04.20180221-0ubuntu1 version.ia32-libs: ia32-libs N/A version.libdrm2: libdrm2 2.4.83-1~16.04.1 version.libgl1-mesa-dri: libgl1-mesa-dri 17.2.8-0ubuntu0~16.04.1 version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A version.libgl1-mesa-glx: libgl1-mesa-glx 17.2.8-0ubuntu0~16.04.1 version.xserver-xorg-core: xserver-xorg-core N/A version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati N/A version.xserver-xorg-video-intel: xserver-xorg-video-intel N/A version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau N/A xserver.bootTime: Sun Apr 15 08:52:27 2018 xserver.configfile: default xserver.errors: xserver.logfile: /var/log/Xorg.0.log xserver.version: 2:1.19.5-0ubuntu2~16.04.1 xserver.video_driver: modeset To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg/+
[Touch-packages] [Bug 1766128] [NEW] [, Analog Devices AD1981, Green Speaker, Internal] No sound at all
Public bug reported: For some strange reason, my laptop does not have the speakers on the output sound options, only headphones - they work fine, but I have no sound on the PC's speakers ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: alsa-base 1.0.25+dfsg-0ubuntu5 ProcVersionSignature: Ubuntu 4.4.0-119.143-generic 4.4.114 Uname: Linux 4.4.0-119-generic x86_64 NonfreeKernelModules: wl ApportVersion: 2.20.1-0ubuntu2.16 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: antonio9072 F pulseaudio CurrentDesktop: Unity Date: Sun Apr 22 23:20:59 2018 InstallationDate: Installed on 2017-09-14 (220 days ago) InstallationMedia: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 (20160719) PackageArchitecture: all SourcePackage: alsa-driver Symptom: audio Symptom_AlsaPlaybackTest: ALSA playback test through plughw:Intel failed Symptom_Card: Built-in Audio - HDA Intel Symptom_DevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: antonio9072 F pulseaudio Symptom_Jack: Green Speaker, Internal Symptom_Type: No sound at all Title: [, Analog Devices AD1981, Green Speaker, Internal] No sound at all UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 08/20/2008 dmi.bios.vendor: Hewlett-Packard dmi.bios.version: 68MSP Ver. F.0D dmi.board.name: 30C9 dmi.board.vendor: Hewlett-Packard dmi.board.version: KBC Version 75.28 dmi.chassis.type: 10 dmi.chassis.vendor: Hewlett-Packard dmi.modalias: dmi:bvnHewlett-Packard:bvr68MSPVer.F.0D:bd08/20/2008:svnHewlett-Packard:pn:pvrF.0D:rvnHewlett-Packard:rn30C9:rvrKBCVersion75.28:cvnHewlett-Packard:ct10:cvr: dmi.product.version: F.0D dmi.sys.vendor: Hewlett-Packard ** Affects: alsa-driver (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 alsa-driver in Ubuntu. https://bugs.launchpad.net/bugs/1766128 Title: [, Analog Devices AD1981, Green Speaker, Internal] No sound at all Status in alsa-driver package in Ubuntu: New Bug description: For some strange reason, my laptop does not have the speakers on the output sound options, only headphones - they work fine, but I have no sound on the PC's speakers ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: alsa-base 1.0.25+dfsg-0ubuntu5 ProcVersionSignature: Ubuntu 4.4.0-119.143-generic 4.4.114 Uname: Linux 4.4.0-119-generic x86_64 NonfreeKernelModules: wl ApportVersion: 2.20.1-0ubuntu2.16 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: antonio9072 F pulseaudio CurrentDesktop: Unity Date: Sun Apr 22 23:20:59 2018 InstallationDate: Installed on 2017-09-14 (220 days ago) InstallationMedia: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 (20160719) PackageArchitecture: all SourcePackage: alsa-driver Symptom: audio Symptom_AlsaPlaybackTest: ALSA playback test through plughw:Intel failed Symptom_Card: Built-in Audio - HDA Intel Symptom_DevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: antonio9072 F pulseaudio Symptom_Jack: Green Speaker, Internal Symptom_Type: No sound at all Title: [, Analog Devices AD1981, Green Speaker, Internal] No sound at all UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 08/20/2008 dmi.bios.vendor: Hewlett-Packard dmi.bios.version: 68MSP Ver. F.0D dmi.board.name: 30C9 dmi.board.vendor: Hewlett-Packard dmi.board.version: KBC Version 75.28 dmi.chassis.type: 10 dmi.chassis.vendor: Hewlett-Packard dmi.modalias: dmi:bvnHewlett-Packard:bvr68MSPVer.F.0D:bd08/20/2008:svnHewlett-Packard:pn:pvrF.0D:rvnHewlett-Packard:rn30C9:rvrKBCVersion75.28:cvnHewlett-Packard:ct10:cvr: dmi.product.version: F.0D dmi.sys.vendor: Hewlett-Packard To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1766128/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1761630] Re: journald takes over /dev/log in bionic, impacts usability of syslog querying
Removing systemd task, as the fixes are only needed in the rsyslog
package w.r.t. permissions used.
** No longer affects: systemd (Ubuntu Bionic)
** No longer affects: systemd (Ubuntu)
--
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/1761630
Title:
journald takes over /dev/log in bionic, impacts usability of syslog
querying
Status in rsyslog package in Ubuntu:
Fix Committed
Status in rsyslog source package in Bionic:
Fix Committed
Bug description:
In bionic, /dev/log is now owned by systemd-journald.
$ sudo fuser -v /dev/log
USERPID ACCESS COMMAND
/run/systemd/journal/dev-log:
root 1 F systemd
root628 F systemd-journal
$
This is ok; there are good reasons to want to do this. (Timestamp
precision that's not dependent on the syslog protocol; logging
available earlier in boot and later at shutdown; unified queriability
of logs around services.)
The logfiles previously populated by rsyslog under /var/log are now
empty (no longer being updated, and the previous files logrotated
away):
$ ls -l /var/log/auth.log
-rw-r- 1 syslog adm 0 Mar 25 00:06 /var/log/auth.log
$
This is also ok, we don't really want log data duplicated in two
places on the system; so since we now have persistent journal under
/var/log/journal, we don't want to also create these plaintext files
by default.
However, it's not clear that this is by design, rather than by
accident. rsyslog is still /configured/ to log to these files; it
just isn't receiving any data because it no longer controls the
socket.
$ sudo lsof -p 852|grep DGRAM
rsyslogd 852 syslog3u unix 0x8e5680435000 0t0351
/run/systemd/journal/syslog type=DGRAM
$
Dimitri and I have discussed that rsyslog should continue to function,
so that users who have remote syslogging configured can still make use
of this. It looks like currently this is not the case, because
journald is not forwarding to rsyslog.
That is not ok.
What is also not ok is that, now that logs are only being written to
the journal by default instead of to syslog files, querying these logs
by syslog priority only works if you know the syslog facility by
number (and, afaics, you can only filter by one syslog facility at a
time). So whereas before, you could find mail logs by looking in
/var/log/mail.log by default, you now have to know to run 'journalctl
SYSLOG_FACILITY=2'; and if you want a view of what was previously in
/var/log/syslog (i.e. filtering out non-syslog systemd logs, it seems
the most compact way to express this is 'journalctl --system
SYSLOG_FACILITY={0,1,2,3,5,6,7,8,9,11,12,13,14,15,16,17,18,19,20,21,22,23}'.
This is really not good. Admins have never needed to know the mapping
of symbolic names to facility numbers to work with syslog; this throws
away 30 years of convention with log handling.
If we are going to store the logs in the journal by default, I think
there needs to be a way to query the logs using symbolic names
consistent with syslog(3) and /etc/rsyslog.d/50-default.conf.
I don't think we can release with things in the current state.
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/rsyslog/+bug/1761630/+subscriptions
--
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1766108] Re: Battery indicator crashes when unchecking "Show Percentage in Menu Bar"
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: mate-panel (Ubuntu) Status: New => Confirmed -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to indicator-power in Ubuntu. https://bugs.launchpad.net/bugs/1766108 Title: Battery indicator crashes when unchecking "Show Percentage in Menu Bar" Status in ubuntu-mate: New Status in indicator-power package in Ubuntu: Confirmed Status in mate-indicator-applet package in Ubuntu: Confirmed Status in mate-panel package in Ubuntu: Confirmed Bug description: Steps to reproduce: 1. Click on the battery indicator. 2. Click "Show Percentage on Menu Bar" to enable it. 3. Do it again to disable it. 4. Battery indicator disappears Output from dmesg: [ 613.877855] mate-panel[1604]: segfault at 1c ip 7f51b23daa20 sp 7ffe8df7f5d8 error 4 in libcairo.so.2.11510.0[7f51b236c000+118000] [ 749.662960] mate-panel[2930]: segfault at 38 ip 7fc98aa82300 sp 7fffa5290f68 error 4 in libgdk-3.so.0.2200.30[7fc98aa3b000+eb000] [ 775.815530] mate-panel[3127]: segfault at 1c ip 7fc317b61a20 sp 7ffea6e1f028 error 4 in libcairo.so.2.11510.0[7fc317af3000+118000] [ 816.504199] mate-panel[3225]: segfault at 38 ip 7fa314f0e300 sp 7fffa993f928 error 4 in libgdk-3.so.0.2200.30[7fa314ec7000+eb000] [ 841.353444] mate-panel[3363]: segfault at 38 ip 7fbc86c4a300 sp 7ffd6b3a5d58 error 4 in libgdk-3.so.0.2200.30[7fbc86c03000+eb000] To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-mate/+bug/1766108/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1766108] Re: Battery indicator crashes when unchecking "Show Percentage in Menu Bar"
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: mate-indicator-applet (Ubuntu) Status: New => Confirmed -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to indicator-power in Ubuntu. https://bugs.launchpad.net/bugs/1766108 Title: Battery indicator crashes when unchecking "Show Percentage in Menu Bar" Status in ubuntu-mate: New Status in indicator-power package in Ubuntu: Confirmed Status in mate-indicator-applet package in Ubuntu: Confirmed Status in mate-panel package in Ubuntu: Confirmed Bug description: Steps to reproduce: 1. Click on the battery indicator. 2. Click "Show Percentage on Menu Bar" to enable it. 3. Do it again to disable it. 4. Battery indicator disappears Output from dmesg: [ 613.877855] mate-panel[1604]: segfault at 1c ip 7f51b23daa20 sp 7ffe8df7f5d8 error 4 in libcairo.so.2.11510.0[7f51b236c000+118000] [ 749.662960] mate-panel[2930]: segfault at 38 ip 7fc98aa82300 sp 7fffa5290f68 error 4 in libgdk-3.so.0.2200.30[7fc98aa3b000+eb000] [ 775.815530] mate-panel[3127]: segfault at 1c ip 7fc317b61a20 sp 7ffea6e1f028 error 4 in libcairo.so.2.11510.0[7fc317af3000+118000] [ 816.504199] mate-panel[3225]: segfault at 38 ip 7fa314f0e300 sp 7fffa993f928 error 4 in libgdk-3.so.0.2200.30[7fa314ec7000+eb000] [ 841.353444] mate-panel[3363]: segfault at 38 ip 7fbc86c4a300 sp 7ffd6b3a5d58 error 4 in libgdk-3.so.0.2200.30[7fbc86c03000+eb000] To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-mate/+bug/1766108/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1766108] Re: Battery indicator crashes when unchecking "Show Percentage in Menu Bar"
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: indicator-power (Ubuntu) Status: New => Confirmed -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to indicator-power in Ubuntu. https://bugs.launchpad.net/bugs/1766108 Title: Battery indicator crashes when unchecking "Show Percentage in Menu Bar" Status in ubuntu-mate: New Status in indicator-power package in Ubuntu: Confirmed Status in mate-indicator-applet package in Ubuntu: Confirmed Status in mate-panel package in Ubuntu: Confirmed Bug description: Steps to reproduce: 1. Click on the battery indicator. 2. Click "Show Percentage on Menu Bar" to enable it. 3. Do it again to disable it. 4. Battery indicator disappears Output from dmesg: [ 613.877855] mate-panel[1604]: segfault at 1c ip 7f51b23daa20 sp 7ffe8df7f5d8 error 4 in libcairo.so.2.11510.0[7f51b236c000+118000] [ 749.662960] mate-panel[2930]: segfault at 38 ip 7fc98aa82300 sp 7fffa5290f68 error 4 in libgdk-3.so.0.2200.30[7fc98aa3b000+eb000] [ 775.815530] mate-panel[3127]: segfault at 1c ip 7fc317b61a20 sp 7ffea6e1f028 error 4 in libcairo.so.2.11510.0[7fc317af3000+118000] [ 816.504199] mate-panel[3225]: segfault at 38 ip 7fa314f0e300 sp 7fffa993f928 error 4 in libgdk-3.so.0.2200.30[7fa314ec7000+eb000] [ 841.353444] mate-panel[3363]: segfault at 38 ip 7fbc86c4a300 sp 7ffd6b3a5d58 error 4 in libgdk-3.so.0.2200.30[7fbc86c03000+eb000] To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-mate/+bug/1766108/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1765923] Re: Nvidia driver leads to black screen on bionic 18.04 SDDM LightDM bug?
** Tags removed: kubuntu ** Tags added: nvidia sddm -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to apt in Ubuntu. https://bugs.launchpad.net/bugs/1765923 Title: Nvidia driver leads to black screen on bionic 18.04 SDDM LightDM bug? Status in apt package in Ubuntu: New Status in nvidia-graphics-drivers-390 package in Ubuntu: New Status in sddm package in Ubuntu: New Bug description: Using the April 19th daily build of Kubuntu 18.04 I installed the Nvidia drivers via the following command. sudo ubuntu-drivers autoinstall The install process proceeds fine and after a logout process I get a black screen. I tried this on the April 17th daily build of bionic and a reboot also results in a black screen. The following is a question which was submitted by a Ubuntu 17.10 user: QUOTE After I installed latest Nvidia driver-390 and tried to boot after shutting down once I faced a black screen problem. since, I'm a noob but something related to nvidia drivers couldn't be started. Then I followed https://askubuntu.com/a/968692/802490 While following these instructions re-installing of nvidia drivers failed. The only things that worked is purging the drivers and changing "WaylandEnable=false" in (/etc/gdm3/custom.conf). Now, I want to re-install nvidia drivers again but I'm afraid that this will lead to that problem again. Can anyone help in re-installing the driver such that I won't face that problem? END QUOTE THE WORK AROUND Use Ctrl-Alt-f6 to get to a login prompt. Login run "startx" The x server will start and Nvidia drivers will function. THE PROBLEM When I try to run SDDM I get an error (Which I will try to copy down to add to this bug when I am on a different computer than the one I am reporting the bug about.). Installing lightDM does not work... it installs but is either will not run or will not actually start a x session. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apt/+bug/1765923/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1764087] Re: Wrongly boots into low graphics mode
This sounds like the error that I'm getting. I did a system update on 19th April. Ubuntu 16.04. Lenovo T61. Is display info (see below) relevant to the bug? As a workaround the following command makes the wifi work: sudo service network-manager restart *-display:0 description: VGA compatible controller product: Mobile GM965/GL960 Integrated Graphics Controller (primary) vendor: Intel Corporation physical id: 2 bus info: pci@:00:02.0 version: 0c width: 64 bits clock: 33MHz capabilities: msi pm vga_controller bus_master cap_list rom configuration: driver=i915 latency=0 resources: irq:16 memory:f810-f81f memory:e000-efff ioport:1800(size=8) memory:c-d *-display:1 UNCLAIMED description: Display controller product: Mobile GM965/GL960 Integrated Graphics Controller (secondary) vendor: Intel Corporation physical id: 2.1 bus info: pci@:00:02.1 version: 0c width: 64 bits clock: 33MHz capabilities: pm bus_master cap_list configuration: latency=0 resources: memory:f820-f82f -- 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/1764087 Title: Wrongly boots into low graphics mode Status in xorg package in Ubuntu: New Bug description: Description: Ubuntu 16.04.4 LTS Release: 16.04 Lenovo T410 with VGA compatible controller [0300]: Intel Corporation Core Processor Integrated Graphics Controller [8086:0046] (rev 02) Booting from latest kernel ThinkPad-T410 4.13.0-38-generic #43~16.04.1-Ubuntu SMP Wed Mar 14 17:48:43 UTC 2018 x86_64 x86_64 x86_64 GNU/Linux goes into low graphics mode and also effects wi-fi connection insofar as it does not connect to my router. Whereas booting from 4.13.0-37-generic #42~16.04.1-Ubuntu SMP Wed Mar 7 16:03:28 UTC 2018 x86_64 x86_64 x86_64 GNU/Linux works most of the time but occasionally has the same effects. I have had to submit this report after booting from 4.13.0.37 in order to submit bug. ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: xorg 1:7.7+13ubuntu3 ProcVersionSignature: Ubuntu 4.13.0-37.42~16.04.1-generic 4.13.13 Uname: Linux 4.13.0-37-generic x86_64 .tmp.unity_support_test.0: ApportVersion: 2.20.1-0ubuntu2.15 Architecture: amd64 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: compiz CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0' CompositorUnredirectFSW: true CurrentDesktop: Unity Date: Sun Apr 15 10:40:31 2018 DistUpgraded: Fresh install DistroCodename: xenial DistroVariant: ubuntu ExtraDebuggingInterest: Yes, if not too technical GraphicsCard: Intel Corporation Core Processor Integrated Graphics Controller [8086:0046] (rev 02) (prog-if 00 [VGA controller]) Subsystem: Lenovo Core Processor Integrated Graphics Controller [17aa:215a] InstallationDate: Installed on 2016-09-24 (567 days ago) InstallationMedia: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 (20160719) MachineType: LENOVO 2519Y11 ProcEnviron: LANGUAGE=en_GB:en PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_GB.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.13.0-37-generic root=UUID=58d362c2-ed1e-479b-84f5-e5d8a782b08f ro quiet splash vt.handoff=7 SourcePackage: xorg Symptom: display UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 02/14/2013 dmi.bios.vendor: LENOVO dmi.bios.version: 6IET85WW (1.45 ) dmi.board.name: 2519Y11 dmi.board.vendor: LENOVO dmi.board.version: Not Available dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: Not Available dmi.modalias: dmi:bvnLENOVO:bvr6IET85WW(1.45):bd02/14/2013:svnLENOVO:pn2519Y11:pvrThinkPadT410:rvnLENOVO:rn2519Y11:rvrNotAvailable:cvnLENOVO:ct10:cvrNotAvailable: dmi.product.family: ThinkPad T410 dmi.product.name: 2519Y11 dmi.product.version: ThinkPad T410 dmi.sys.vendor: LENOVO version.compiz: compiz 1:0.9.12.3+16.04.20180221-0ubuntu1 version.ia32-libs: ia32-libs N/A version.libdrm2: libdrm2 2.4.83-1~16.04.1 version.libgl1-mesa-dri: libgl1-mesa-dri 17.2.8-0ubuntu0~16.04.1 version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A version.libgl1-mesa-glx: libgl1-mesa-glx 17.2.8-0ubuntu0~16.04.1 version.xserver-xorg-core: xserver-xorg-core N/A version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati N/A version.xserver-xorg-video-intel: xserver-xorg-video-intel N/A version.xserv
[Touch-packages] [Bug 1762818] Re: Regression: Upgrading from 17.10 to 18.04 reduces resolution available on monitor
A victim of some other fix. This regression can be prevented by adding amdgpu.dc=0 to the kernel command line. -- 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/1762818 Title: Regression: Upgrading from 17.10 to 18.04 reduces resolution available on monitor Status in xorg package in Ubuntu: New Bug description: Symptom: booting 18.04 kernel reduces resolution available while 17.10 kernel (on 18.04) does not I have a 3 identical monitor setup - all at 2560x1600 native resolution. If I boot the current 18.04 kernel 4.15.0-13-generic then the third monitor does not have the native resolution available. If I reboot with the last 17.10 kernel 4.13.0-37-generic then all monitors have the native resolution available. On the video card the monitors are connected to HDMI, DisplayPort and DVI. On the monitors themselves the connectors are HDMI, DisplayPort and HDMI. (3rd monitor is using DVI to HDMI cable.) Xorg logs show identical EDID information between the kernels. 18.04's just decides to not make 2560x1600 available, having 2048x1080 or 1920x1200 as the highest. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: xorg 1:7.7+19ubuntu6 ProcVersionSignature: Ubuntu 4.15.0-13.14-generic 4.15.10 Uname: Linux 4.15.0-13-generic x86_64 ApportVersion: 2.20.9-0ubuntu4 Architecture: amd64 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: None CurrentDesktop: XFCE Date: Tue Apr 10 12:17:31 2018 DistUpgraded: 2018-03-31 12:24:30,098 DEBUG Running PostInstallScript: './xorg_fix_proprietary.py' DistroCodename: bionic DistroVariant: ubuntu ExtraDebuggingInterest: Yes GraphicsCard: Advanced Micro Devices, Inc. [AMD/ATI] Baffin [Radeon RX 460] [1002:67ef] (rev e5) (prog-if 00 [VGA controller]) Subsystem: Gigabyte Technology Co., Ltd Baffin [Radeon RX 460/560D / Pro 450/455/460/560] [1458:230a] LightdmGreeterLogOld: ** Message: Starting lightdm-gtk-greeter 2.0.1 (Aug 7 2015, 01:24:18) ** Message: [Configuration] Reading file: /etc/lightdm/lightdm-gtk-greeter.conf.d/01_ubuntu.conf ** Message: [Configuration] Reading file: /etc/lightdm/lightdm-gtk-greeter.conf.d/30_xubuntu.conf ** Message: [Configuration] Reading file: /etc/lightdm/lightdm-gtk-greeter.conf upstart: indicator-application main process (1456) killed by TERM signal MachineType: Supermicro C7Z170-SQ ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.15.0-13-generic root=UUID=725712a6-f0e0-4da1-b3d1-746a233eb459 ro rootflags=subvol=@ SourcePackage: xorg Symptom: display UpgradeStatus: Upgraded to bionic on 2018-03-31 (9 days ago) dmi.bios.date: 12/19/2016 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 2.0 dmi.board.asset.tag: Default string dmi.board.name: C7Z170-SQ dmi.board.vendor: Supermicro dmi.board.version: 1.01A dmi.chassis.asset.tag: Default string dmi.chassis.type: 17 dmi.chassis.vendor: Supermicro dmi.chassis.version: 0123456789 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr2.0:bd12/19/2016:svnSupermicro:pnC7Z170-SQ:pvr0123456789:rvnSupermicro:rnC7Z170-SQ:rvr1.01A:cvnSupermicro:ct17:cvr0123456789: dmi.product.family: Default string dmi.product.name: C7Z170-SQ dmi.product.version: 0123456789 dmi.sys.vendor: Supermicro version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.91-2 version.libgl1-mesa-dri: libgl1-mesa-dri 18.0.0~rc5-1ubuntu1 version.libgl1-mesa-glx: libgl1-mesa-glx 18.0.0~rc5-1ubuntu1 version.xserver-xorg-core: xserver-xorg-core 2:1.19.6-1ubuntu3 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.10.5-1ubuntu1 version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:18.0.1-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20171229-1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.15-2 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1762818/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1751293] Re: libfreetype6 2.8.1 cause nasty font glitches in atom editor
This also effects other electron apps such as Discord. The fix for users is to downgrade from freetype 2.8.1 to freetype 2.8. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to freetype in Ubuntu. https://bugs.launchpad.net/bugs/1751293 Title: libfreetype6 2.8.1 cause nasty font glitches in atom editor Status in freetype package in Ubuntu: Invalid Bug description: Main bugreport: https://github.com/atom/atom/issues/15737 Problem can be reproduced with 2.8.1-0.1ubuntu2, but it disappears on libfreetype6=2.8-0.2ubuntu2.1. I don't know about root cause, but may be holding back on 2.8-0 in bionic may be a great idea? ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: libfreetype6 2.8-0.2ubuntu2.1 ProcVersionSignature: Ubuntu 4.15.0-10.11-generic 4.15.3 Uname: Linux 4.15.0-10-generic x86_64 ApportVersion: 2.20.8-0ubuntu10 Architecture: amd64 CurrentDesktop: X-Cinnamon Date: Fri Feb 23 16:42:14 2018 Dependencies: gcc-8-base 8-20180208-0ubuntu1 libc6 2.26-0ubuntu2.1 libgcc1 1:8-20180208-0ubuntu1 libpng16-16 1.6.34-1 zlib1g 1:1.2.11.dfsg-0ubuntu2 DistributionChannelDescriptor: # This is a distribution channel descriptor # For more information see http://wiki.ubuntu.com/DistributionChannelDescriptor canonical-oem-somerville-xenial-amd64-20160624-2 EcryptfsInUse: Yes InstallationDate: Installed on 2017-06-22 (246 days ago) InstallationMedia: Ubuntu 16.04 "Xenial" - Build amd64 LIVE Binary 20160624-10:47 SourcePackage: freetype UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/freetype/+bug/1751293/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1766119] [NEW] package ca-certificates 20180409 failed to install/upgrade: installed ca-certificates package post-installation script subprocess returned error exit status 1
Public bug reported: installing ubuntu 18.04 says to me that the ca-certificates cant be installed ProblemType: Package DistroRelease: Ubuntu 18.04 Package: ca-certificates 20180409 ProcVersionSignature: Ubuntu 4.15.0-15.16-generic 4.15.15 Uname: Linux 4.15.0-15-generic x86_64 ApportVersion: 2.20.9-0ubuntu6 Architecture: amd64 Date: Sun Apr 22 13:29:09 2018 ErrorMessage: installed ca-certificates package post-installation script subprocess returned error exit status 1 InstallationDate: Installed on 2017-12-01 (142 days ago) InstallationMedia: Ubuntu 16.04.3 LTS "Xenial Xerus" - Release amd64 (20170801) PackageArchitecture: all Python3Details: /usr/bin/python3.6, Python 3.6.5, python3-minimal, 3.6.5-3 PythonDetails: /usr/bin/python2.7, Python 2.7.15rc1, python-minimal, 2.7.15~rc1-1 RelatedPackageVersions: dpkg 1.19.0.5ubuntu2 apt 1.6.1 SourcePackage: ca-certificates Title: package ca-certificates 20180409 failed to install/upgrade: installed ca-certificates package post-installation script subprocess returned error exit status 1 UpgradeStatus: Upgraded to bionic on 2018-04-22 (0 days ago) ** Affects: ca-certificates (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-package bionic -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to ca-certificates in Ubuntu. https://bugs.launchpad.net/bugs/1766119 Title: package ca-certificates 20180409 failed to install/upgrade: installed ca-certificates package post-installation script subprocess returned error exit status 1 Status in ca-certificates package in Ubuntu: New Bug description: installing ubuntu 18.04 says to me that the ca-certificates cant be installed ProblemType: Package DistroRelease: Ubuntu 18.04 Package: ca-certificates 20180409 ProcVersionSignature: Ubuntu 4.15.0-15.16-generic 4.15.15 Uname: Linux 4.15.0-15-generic x86_64 ApportVersion: 2.20.9-0ubuntu6 Architecture: amd64 Date: Sun Apr 22 13:29:09 2018 ErrorMessage: installed ca-certificates package post-installation script subprocess returned error exit status 1 InstallationDate: Installed on 2017-12-01 (142 days ago) InstallationMedia: Ubuntu 16.04.3 LTS "Xenial Xerus" - Release amd64 (20170801) PackageArchitecture: all Python3Details: /usr/bin/python3.6, Python 3.6.5, python3-minimal, 3.6.5-3 PythonDetails: /usr/bin/python2.7, Python 2.7.15rc1, python-minimal, 2.7.15~rc1-1 RelatedPackageVersions: dpkg 1.19.0.5ubuntu2 apt 1.6.1 SourcePackage: ca-certificates Title: package ca-certificates 20180409 failed to install/upgrade: installed ca-certificates package post-installation script subprocess returned error exit status 1 UpgradeStatus: Upgraded to bionic on 2018-04-22 (0 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ca-certificates/+bug/1766119/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1766110] [NEW] package libperl5.26 5.26.0-8ubuntu1 [modified: usr/share/doc/libperl5.26/changelog.Debian.gz] failed to install/upgrade: tentative de remplacement de « /usr/share/
Public bug reported: dpkg: erreur de traitement de l'archive /var/cache/apt/archives/libperl5.26_5.26.0-8ubuntu1.1_amd64.deb (--unpack) : tentative de remplacement de « /usr/share/doc/libperl5.26/changelog.Debian.gz », qui est différent d'autres instances du paquet libperl5.26:amd64 Préparation du dépaquetage de .../perl_5.26.0-8ubuntu1.1_amd64.deb ... Dépaquetage de perl (5.26.0-8ubuntu1.1) sur (5.26.0-8ubuntu1) ... Préparation du dépaquetage de .../perl-base_5.26.0-8ubuntu1.1_amd64.deb ... Dépaquetage de perl-base (5.26.0-8ubuntu1.1) sur (5.26.0-8ubuntu1) ... Des erreurs ont été rencontrées pendant l'exécution : /var/cache/apt/archives/libperl5.26_5.26.0-8ubuntu1.1_amd64.deb E: Sub-process /usr/bin/dpkg returned an error code (1) ProblemType: Package DistroRelease: Ubuntu 17.10 Package: libperl5.26 5.26.0-8ubuntu1 [modified: usr/share/doc/libperl5.26/changelog.Debian.gz] ProcVersionSignature: Ubuntu 4.13.0-38.43-generic 4.13.16 Uname: Linux 4.13.0-38-generic x86_64 ApportVersion: 2.20.7-0ubuntu3.7 Architecture: amd64 Date: Sun Apr 22 19:35:46 2018 ErrorMessage: tentative de remplacement de « /usr/share/doc/libperl5.26/changelog.Debian.gz », qui est différent d'autres instances du paquet libperl5.26:amd64 InstallationDate: Installed on 2017-10-26 (178 days ago) InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20171018) Python3Details: /usr/bin/python3.6, Python 3.6.3, python3-minimal, 3.6.3-0ubuntu2 PythonDetails: /usr/bin/python2.7, Python 2.7.14, python-minimal, 2.7.14-2ubuntu1 RelatedPackageVersions: dpkg 1.18.24ubuntu1 apt 1.5.1 SourcePackage: perl Title: package libperl5.26 5.26.0-8ubuntu1 [modified: usr/share/doc/libperl5.26/changelog.Debian.gz] failed to install/upgrade: tentative de remplacement de « /usr/share/doc/libperl5.26/changelog.Debian.gz », qui est différent d'autres instances du paquet libperl5.26:amd64 UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: perl (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-package artful -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to perl in Ubuntu. https://bugs.launchpad.net/bugs/1766110 Title: package libperl5.26 5.26.0-8ubuntu1 [modified: usr/share/doc/libperl5.26/changelog.Debian.gz] failed to install/upgrade: tentative de remplacement de « /usr/share/doc/libperl5.26/changelog.Debian.gz », qui est différent d'autres instances du paquet libperl5.26:amd64 Status in perl package in Ubuntu: New Bug description: dpkg: erreur de traitement de l'archive /var/cache/apt/archives/libperl5.26_5.26.0-8ubuntu1.1_amd64.deb (--unpack) : tentative de remplacement de « /usr/share/doc/libperl5.26/changelog.Debian.gz », qui est différent d'autres instances du paquet libperl5.26:amd64 Préparation du dépaquetage de .../perl_5.26.0-8ubuntu1.1_amd64.deb ... Dépaquetage de perl (5.26.0-8ubuntu1.1) sur (5.26.0-8ubuntu1) ... Préparation du dépaquetage de .../perl-base_5.26.0-8ubuntu1.1_amd64.deb ... Dépaquetage de perl-base (5.26.0-8ubuntu1.1) sur (5.26.0-8ubuntu1) ... Des erreurs ont été rencontrées pendant l'exécution : /var/cache/apt/archives/libperl5.26_5.26.0-8ubuntu1.1_amd64.deb E: Sub-process /usr/bin/dpkg returned an error code (1) ProblemType: Package DistroRelease: Ubuntu 17.10 Package: libperl5.26 5.26.0-8ubuntu1 [modified: usr/share/doc/libperl5.26/changelog.Debian.gz] ProcVersionSignature: Ubuntu 4.13.0-38.43-generic 4.13.16 Uname: Linux 4.13.0-38-generic x86_64 ApportVersion: 2.20.7-0ubuntu3.7 Architecture: amd64 Date: Sun Apr 22 19:35:46 2018 ErrorMessage: tentative de remplacement de « /usr/share/doc/libperl5.26/changelog.Debian.gz », qui est différent d'autres instances du paquet libperl5.26:amd64 InstallationDate: Installed on 2017-10-26 (178 days ago) InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20171018) Python3Details: /usr/bin/python3.6, Python 3.6.3, python3-minimal, 3.6.3-0ubuntu2 PythonDetails: /usr/bin/python2.7, Python 2.7.14, python-minimal, 2.7.14-2ubuntu1 RelatedPackageVersions: dpkg 1.18.24ubuntu1 apt 1.5.1 SourcePackage: perl Title: package libperl5.26 5.26.0-8ubuntu1 [modified: usr/share/doc/libperl5.26/changelog.Debian.gz] failed to install/upgrade: tentative de remplacement de « /usr/share/doc/libperl5.26/changelog.Debian.gz », qui est différent d'autres instances du paquet libperl5.26:amd64 UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/perl/+bug/1766110/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1766108] [NEW] Battery indicator crashes when unchecking "Show Percentage in Menu Bar"
Public bug reported: Steps to reproduce: 1. Click on the battery indicator. 2. Click "Show Percentage on Menu Bar" to enable it. 3. Do it again to disable it. 4. Battery indicator disappears Output from dmesg: [ 613.877855] mate-panel[1604]: segfault at 1c ip 7f51b23daa20 sp 7ffe8df7f5d8 error 4 in libcairo.so.2.11510.0[7f51b236c000+118000] [ 749.662960] mate-panel[2930]: segfault at 38 ip 7fc98aa82300 sp 7fffa5290f68 error 4 in libgdk-3.so.0.2200.30[7fc98aa3b000+eb000] [ 775.815530] mate-panel[3127]: segfault at 1c ip 7fc317b61a20 sp 7ffea6e1f028 error 4 in libcairo.so.2.11510.0[7fc317af3000+118000] [ 816.504199] mate-panel[3225]: segfault at 38 ip 7fa314f0e300 sp 7fffa993f928 error 4 in libgdk-3.so.0.2200.30[7fa314ec7000+eb000] [ 841.353444] mate-panel[3363]: segfault at 38 ip 7fbc86c4a300 sp 7ffd6b3a5d58 error 4 in libgdk-3.so.0.2200.30[7fbc86c03000+eb000] ** Affects: ubuntu-mate Importance: Undecided Status: New ** Affects: indicator-power (Ubuntu) Importance: Undecided Status: New ** Affects: mate-indicator-applet (Ubuntu) Importance: Undecided Status: New ** Affects: mate-panel (Ubuntu) Importance: Undecided Status: New ** Also affects: indicator-power (Ubuntu) Importance: Undecided Status: New ** Also affects: mate-indicator-applet (Ubuntu) Importance: Undecided Status: New ** Also affects: mate-panel (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to indicator-power in Ubuntu. https://bugs.launchpad.net/bugs/1766108 Title: Battery indicator crashes when unchecking "Show Percentage in Menu Bar" Status in ubuntu-mate: New Status in indicator-power package in Ubuntu: New Status in mate-indicator-applet package in Ubuntu: New Status in mate-panel package in Ubuntu: New Bug description: Steps to reproduce: 1. Click on the battery indicator. 2. Click "Show Percentage on Menu Bar" to enable it. 3. Do it again to disable it. 4. Battery indicator disappears Output from dmesg: [ 613.877855] mate-panel[1604]: segfault at 1c ip 7f51b23daa20 sp 7ffe8df7f5d8 error 4 in libcairo.so.2.11510.0[7f51b236c000+118000] [ 749.662960] mate-panel[2930]: segfault at 38 ip 7fc98aa82300 sp 7fffa5290f68 error 4 in libgdk-3.so.0.2200.30[7fc98aa3b000+eb000] [ 775.815530] mate-panel[3127]: segfault at 1c ip 7fc317b61a20 sp 7ffea6e1f028 error 4 in libcairo.so.2.11510.0[7fc317af3000+118000] [ 816.504199] mate-panel[3225]: segfault at 38 ip 7fa314f0e300 sp 7fffa993f928 error 4 in libgdk-3.so.0.2200.30[7fa314ec7000+eb000] [ 841.353444] mate-panel[3363]: segfault at 38 ip 7fbc86c4a300 sp 7ffd6b3a5d58 error 4 in libgdk-3.so.0.2200.30[7fbc86c03000+eb000] To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-mate/+bug/1766108/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1766106] [NEW] ntp.ubuntu.com not reliable, but used in standard configuration
Public bug reported: In systemd-timesyncd ntp.ubuntu.com is used as fall back ntp server. However, one of the addresses it resolves to is not available for quite some while: [...] Apr 14 07:37:42 singold systemd-timesyncd[773]: Timed out waiting for reply from [2001:67c:1560:8003::c8]:123 (ntp.ubuntu.com). Apr 14 08:10:45 singold systemd-timesyncd[773]: Timed out waiting for reply from [2001:67c:1560:8003::c8]:123 (ntp.ubuntu.com). Apr 15 08:20:48 singold systemd-timesyncd[802]: Timed out waiting for reply from [2001:67c:1560:8003::c8]:123 (ntp.ubuntu.com). Apr 15 12:47:56 singold systemd-timesyncd[842]: Timed out waiting for reply from [2001:67c:1560:8003::c8]:123 (ntp.ubuntu.com). Apr 16 07:39:05 singold systemd-timesyncd[842]: Timed out waiting for reply from [2001:67c:1560:8003::c8]:123 (ntp.ubuntu.com). Apr 18 18:11:05 singold systemd-timesyncd[842]: Timed out waiting for reply from [2001:67c:1560:8003::c8]:123 (ntp.ubuntu.com). Apr 19 23:45:04 singold systemd-timesyncd[758]: Timed out waiting for reply from [2001:67c:1560:8003::c8]:123 (ntp.ubuntu.com). Apr 20 14:20:46 singold systemd-timesyncd[758]: Timed out waiting for reply from [2001:67c:1560:8003::c8]:123 (ntp.ubuntu.com). Apr 21 09:42:45 singold systemd-timesyncd[758]: Timed out waiting for reply from [2001:67c:1560:8003::c8]:123 (ntp.ubuntu.com). Apr 22 09:41:52 singold systemd-timesyncd[672]: Timed out waiting for reply from [2001:67c:1560:8003::c8]:123 (ntp.ubuntu.com). Apr 22 09:47:03 singold systemd-timesyncd[672]: Timed out waiting for reply from [2001:67c:1560:8003::c8]:123 (ntp.ubuntu.com). [...] It turns out that from all the A and records ntp.ubuntu.com resolves the, 2001:67c:1560:8003::c8 seems to be constantly down. This leads to time synchronisation problems for people using IPv6, as it seems timesyncd keeps returning to the same server over and over again, instead of trying the other ones DNS returns. A practical solution to this would be to simply remove 2001:67c:1560:8003::c8 from the DNS entry for ntp.ubuntu.com. ** Affects: systemd (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to systemd in Ubuntu. https://bugs.launchpad.net/bugs/1766106 Title: ntp.ubuntu.com not reliable, but used in standard configuration Status in systemd package in Ubuntu: New Bug description: In systemd-timesyncd ntp.ubuntu.com is used as fall back ntp server. However, one of the addresses it resolves to is not available for quite some while: [...] Apr 14 07:37:42 singold systemd-timesyncd[773]: Timed out waiting for reply from [2001:67c:1560:8003::c8]:123 (ntp.ubuntu.com). Apr 14 08:10:45 singold systemd-timesyncd[773]: Timed out waiting for reply from [2001:67c:1560:8003::c8]:123 (ntp.ubuntu.com). Apr 15 08:20:48 singold systemd-timesyncd[802]: Timed out waiting for reply from [2001:67c:1560:8003::c8]:123 (ntp.ubuntu.com). Apr 15 12:47:56 singold systemd-timesyncd[842]: Timed out waiting for reply from [2001:67c:1560:8003::c8]:123 (ntp.ubuntu.com). Apr 16 07:39:05 singold systemd-timesyncd[842]: Timed out waiting for reply from [2001:67c:1560:8003::c8]:123 (ntp.ubuntu.com). Apr 18 18:11:05 singold systemd-timesyncd[842]: Timed out waiting for reply from [2001:67c:1560:8003::c8]:123 (ntp.ubuntu.com). Apr 19 23:45:04 singold systemd-timesyncd[758]: Timed out waiting for reply from [2001:67c:1560:8003::c8]:123 (ntp.ubuntu.com). Apr 20 14:20:46 singold systemd-timesyncd[758]: Timed out waiting for reply from [2001:67c:1560:8003::c8]:123 (ntp.ubuntu.com). Apr 21 09:42:45 singold systemd-timesyncd[758]: Timed out waiting for reply from [2001:67c:1560:8003::c8]:123 (ntp.ubuntu.com). Apr 22 09:41:52 singold systemd-timesyncd[672]: Timed out waiting for reply from [2001:67c:1560:8003::c8]:123 (ntp.ubuntu.com). Apr 22 09:47:03 singold systemd-timesyncd[672]: Timed out waiting for reply from [2001:67c:1560:8003::c8]:123 (ntp.ubuntu.com). [...] It turns out that from all the A and records ntp.ubuntu.com resolves the, 2001:67c:1560:8003::c8 seems to be constantly down. This leads to time synchronisation problems for people using IPv6, as it seems timesyncd keeps returning to the same server over and over again, instead of trying the other ones DNS returns. A practical solution to this would be to simply remove 2001:67c:1560:8003::c8 from the DNS entry for ntp.ubuntu.com. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1766106/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1766063] Re: mm (Myanmar / Burmese) for zawgyi keyboard layout
Thanks for your report and your patch! However, this is too late for Ubuntu 18.04, which will be released in a few days. Many users change xkb-data files to set up personal keyboard configuration, and we don't do stable release updates of this package unless absolutely necessary, since it would overwrite such changes. I see that it was included upstream, so the new Burmese layout variant will most likely be included in Ubuntu 18.10. ** Changed in: xkeyboard-config (Ubuntu) Importance: Undecided => Wishlist ** Changed in: xkeyboard-config (Ubuntu) Status: Fix Committed => Triaged ** Changed in: xkeyboard-config (Ubuntu) Milestone: None => later ** Changed in: xkeyboard-config (Ubuntu) Assignee: kokoye2007 (kokoye2007) => (unassigned) -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to xkeyboard-config in Ubuntu. https://bugs.launchpad.net/bugs/1766063 Title: mm (Myanmar / Burmese) for zawgyi keyboard layout Status in xkeyboard-config: Fix Released Status in xkeyboard-config package in Ubuntu: Triaged Status in xkeyboard-config package in Arch Linux: New Status in xkeyboard-config package in CentOS: New Status in xkeyboard-config package in Debian: Fix Released Status in xkeyboard-config package in Fedora: New Status in xkeyboard-config package in Gentoo Linux: New Status in xkeyboard-config package in Unity Linux: New Bug description: https://bugs.freedesktop.org/show_bug.cgi?id=106169 New Keyboard Layout addition in Myanmar / Burmese --- New Keyboard Layout --- Added New Keyboard Layout - Burmese Zawgyi Keyboard This is similar to Burmese MM. Its most popular keyboard in Burmese. To manage notifications about this bug go to: https://bugs.launchpad.net/xkeyboard-config/+bug/1766063/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1766063] Re: mm (Myanmar / Burmese) for zawgyi keyboard layout
** Changed in: xkeyboard-config (Ubuntu) Assignee: (unassigned) => kokoye2007 (kokoye2007) ** Changed in: xkeyboard-config (Ubuntu) Status: New => Fix Committed -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to xkeyboard-config in Ubuntu. https://bugs.launchpad.net/bugs/1766063 Title: mm (Myanmar / Burmese) for zawgyi keyboard layout Status in xkeyboard-config: Fix Released Status in xkeyboard-config package in Ubuntu: Fix Committed Status in xkeyboard-config package in Arch Linux: New Status in xkeyboard-config package in CentOS: New Status in xkeyboard-config package in Debian: Fix Released Status in xkeyboard-config package in Fedora: New Status in xkeyboard-config package in Gentoo Linux: New Status in xkeyboard-config package in Unity Linux: New Bug description: https://bugs.freedesktop.org/show_bug.cgi?id=106169 New Keyboard Layout addition in Myanmar / Burmese --- New Keyboard Layout --- Added New Keyboard Layout - Burmese Zawgyi Keyboard This is similar to Burmese MM. Its most popular keyboard in Burmese. To manage notifications about this bug go to: https://bugs.launchpad.net/xkeyboard-config/+bug/1766063/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1766063] Re: mm (Myanmar / Burmese) for zawgyi keyboard layout
** Changed in: xkeyboard-config Status: Confirmed => Fix Released ** Changed in: xkeyboard-config (Debian) Status: Confirmed => Fix Released -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to xkeyboard-config in Ubuntu. https://bugs.launchpad.net/bugs/1766063 Title: mm (Myanmar / Burmese) for zawgyi keyboard layout Status in xkeyboard-config: Fix Released Status in xkeyboard-config package in Ubuntu: New Status in xkeyboard-config package in Arch Linux: New Status in xkeyboard-config package in CentOS: New Status in xkeyboard-config package in Debian: Fix Released Status in xkeyboard-config package in Fedora: New Status in xkeyboard-config package in Gentoo Linux: New Status in xkeyboard-config package in Unity Linux: New Bug description: https://bugs.freedesktop.org/show_bug.cgi?id=106169 New Keyboard Layout addition in Myanmar / Burmese --- New Keyboard Layout --- Added New Keyboard Layout - Burmese Zawgyi Keyboard This is similar to Burmese MM. Its most popular keyboard in Burmese. To manage notifications about this bug go to: https://bugs.launchpad.net/xkeyboard-config/+bug/1766063/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1766063] Re: mm (Myanmar / Burmese) for zawgyi keyboard layout
** Also affects: xkeyboard-config (Arch Linux) Importance: Undecided Status: New ** Also affects: xkeyboard-config (Gentoo Linux) Importance: Undecided Status: New ** Also affects: xkeyboard-config (CentOS) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to xkeyboard-config in Ubuntu. https://bugs.launchpad.net/bugs/1766063 Title: mm (Myanmar / Burmese) for zawgyi keyboard layout Status in xkeyboard-config: Confirmed Status in xkeyboard-config package in Ubuntu: New Status in xkeyboard-config package in Arch Linux: New Status in xkeyboard-config package in CentOS: New Status in xkeyboard-config package in Debian: Confirmed Status in xkeyboard-config package in Fedora: New Status in xkeyboard-config package in Gentoo Linux: New Status in xkeyboard-config package in Unity Linux: New Bug description: https://bugs.freedesktop.org/show_bug.cgi?id=106169 New Keyboard Layout addition in Myanmar / Burmese --- New Keyboard Layout --- Added New Keyboard Layout - Burmese Zawgyi Keyboard This is similar to Burmese MM. Its most popular keyboard in Burmese. To manage notifications about this bug go to: https://bugs.launchpad.net/xkeyboard-config/+bug/1766063/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1766063] Re: mm (Myanmar / Burmese) for zawgyi keyboard layout
** Branch linked: lp:~kokoye2007/xkeyboard-config/xkeyboard-config -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to xkeyboard-config in Ubuntu. https://bugs.launchpad.net/bugs/1766063 Title: mm (Myanmar / Burmese) for zawgyi keyboard layout Status in xkeyboard-config: Confirmed Status in xkeyboard-config package in Ubuntu: New Status in xkeyboard-config package in Arch Linux: New Status in xkeyboard-config package in Debian: Confirmed Status in xkeyboard-config package in Fedora: New Status in xkeyboard-config package in Gentoo Linux: New Status in xkeyboard-config package in Unity Linux: New Bug description: https://bugs.freedesktop.org/show_bug.cgi?id=106169 New Keyboard Layout addition in Myanmar / Burmese --- New Keyboard Layout --- Added New Keyboard Layout - Burmese Zawgyi Keyboard This is similar to Burmese MM. Its most popular keyboard in Burmese. To manage notifications about this bug go to: https://bugs.launchpad.net/xkeyboard-config/+bug/1766063/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1764858] Re: Can't update / install / delete packages
@Vasily: I solved my issue by force-extracting the content of the libzstd1 deb archive. That restored the missing shared library and after that everything seems to work as it should again (all updates installed). # dpkg-deb -x /var/cache/apt/archives/libzstd1_1.3.3+dfsg- 2ubuntu1_amd64.deb / maybe the same work-around would work for you -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to apt in Ubuntu. https://bugs.launchpad.net/bugs/1764858 Title: Can't update / install / delete packages Status in apt package in Ubuntu: Incomplete Bug description: Description: Ubuntu Bionic Beaver (development branch) Release: 18.04 After todays upgrade: vasily@vasily-desktop:~$ sudo apt-get update [sudo] пароль для vasily: apt-get: error while loading shared libraries: libzstd.so.1: cannot open shared object file: No such file or directory To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apt/+bug/1764858/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1760566] Re: mesa does not include vaExportSurfaceHandle support for vaapi
we're probably too close to the release to get 18.0.1 merged, but it will come as an SRU -- 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/1760566 Title: mesa does not include vaExportSurfaceHandle support for vaapi Status in mesa package in Ubuntu: Confirmed Bug description: Ubuntu prepares to ship libva 2.1 and mesa 18.x for Bionic. Mesa misses one tiny patch to make modern AMD GPUs work with VAAPI on wayland / gbm / mir. We tried to get this into final 18.0 but was not yet accepted. The change itself is a minor. Without it a certain feature is not available. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mesa/+bug/1760566/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1766077] [NEW] Power Save Blank Screen Resoration Ubuntu 18.04
Public bug reported: After Blank Screen has time operated, Display screens can be re-energized but only to a display of colored noise all over them. To recover the machine must be turned of and restarted from scratch. The problem can be bypassed by deactivating the Screen Blank feature and only using the suspend mode to avoid having to use a forced power off and loosing data. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: xorg 1:7.7+19ubuntu7 ProcVersionSignature: Ubuntu 4.15.0-15.16-generic 4.15.15 Uname: Linux 4.15.0-15-generic x86_64 ApportVersion: 2.20.9-0ubuntu6 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Sun Apr 22 08:16:38 2018 DistUpgraded: Fresh install DistroCodename: bionic DistroVariant: ubuntu ExtraDebuggingInterest: Yes GraphicsCard: Advanced Micro Devices, Inc. [AMD/ATI] Oland [Radeon HD 8570 / R7 240/340 OEM] [1002:6611] (prog-if 00 [VGA controller]) Subsystem: ASUSTeK Computer Inc. Oland [Radeon HD 8570 / R7 240/340 OEM] [1043:869e] InstallationDate: Installed on 2018-03-27 (26 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Alpha amd64 (20180325) MachineType: ASUSTeK COMPUTER INC. M52BC_M32BC ProcEnviron: LANGUAGE=en_CA:en PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_CA.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-15-generic.efi.signed root=UUID=ea31804e-9cf0-469c-803d-f52d3c3797a3 ro quiet splash vt.handoff=1 SourcePackage: xorg Symptom: display UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 08/12/2015 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 0401 dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: M52BC_M32BC dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: Rev 1.xx dmi.chassis.asset.tag: To Be Filled By O.E.M. dmi.chassis.type: 3 dmi.chassis.vendor: To Be Filled By O.E.M. dmi.chassis.version: To Be Filled By O.E.M. dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr0401:bd08/12/2015:svnASUSTeKCOMPUTERINC.:pnM52BC_M32BC:pvrTobefilledbyO.E.M.:rvnASUSTeKCOMPUTERINC.:rnM52BC_M32BC:rvrRev1.xx:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.: dmi.product.family: Desktop dmi.product.name: M52BC_M32BC dmi.product.version: To be filled by O.E.M. dmi.sys.vendor: ASUSTeK COMPUTER INC. version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.91-2 version.libgl1-mesa-dri: libgl1-mesa-dri 18.0.0~rc5-1ubuntu1 version.libgl1-mesa-glx: libgl1-mesa-glx 18.0.0~rc5-1ubuntu1 version.xserver-xorg-core: xserver-xorg-core 2:1.19.6-1ubuntu4 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:18.0.1-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20171229-1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.15-2 ** Affects: xorg (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug bionic 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/1766077 Title: Power Save Blank Screen Resoration Ubuntu 18.04 Status in xorg package in Ubuntu: New Bug description: After Blank Screen has time operated, Display screens can be re-energized but only to a display of colored noise all over them. To recover the machine must be turned of and restarted from scratch. The problem can be bypassed by deactivating the Screen Blank feature and only using the suspend mode to avoid having to use a forced power off and loosing data. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: xorg 1:7.7+19ubuntu7 ProcVersionSignature: Ubuntu 4.15.0-15.16-generic 4.15.15 Uname: Linux 4.15.0-15-generic x86_64 ApportVersion: 2.20.9-0ubuntu6 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Sun Apr 22 08:16:38 2018 DistUpgraded: Fresh install DistroCodename: bionic DistroVariant: ubuntu ExtraDebuggingInterest: Yes GraphicsCard: Advanced Micro Devices, Inc. [AMD/ATI] Oland [Radeon HD 8570 / R7 240/340 OEM] [1002:6611] (prog-if 00 [VGA controller]) Subsystem: ASUSTeK Computer Inc. Oland [Radeon HD 8570 / R7 240/340 OEM] [1043:869e] InstallationDate: Installed on 2018-03-27 (26 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Alpha amd64 (20180325) MachineType: ASUSTeK COMPUTER INC. M52BC_M32BC ProcEnviron: LANGUAGE=en_CA:en PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_CA.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-15-generic.efi.signed root=UUID=ea31804e-9cf0-469c-803d-f52d3c3797a3 ro quiet splash vt.handoff=1 SourcePackage: xorg Symptom: display UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date:
[Touch-packages] [Bug 1184387] Re: while playing video computer becomes unresponsive
** This bug is no longer a duplicate of bug 1750947 pulseaudio print lots of error when selecting unavailable profile -- 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/1184387 Title: while playing video computer becomes unresponsive Status in alsa-driver package in Ubuntu: New Bug description: When I was playing a flash video the screen froze and the audio continued a bit and then stopped for a minute or so and then started for a few seconds again. I was able to ssh into my laptop and save the logs. Syslog said: pulseaudio[2242]: [alsa-sink] alsa-util.c: snd_pcm_avail() returned a value that is exceptionally large: 591416 bytes (3352 ms). pulseaudio[2242]: [alsa-sink] alsa-util.c: Most likely this is a bug in the ALSA driver 'snd_hda_intel'. Please report this issue to the ALSA developers. so I did. The full logs are attached. This bug happens often but I can't reliably reproduce it and it seems very random. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1184387/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1717714] Re: @{pid} variable broken on systems with pid_max more than 6 digits
** Changed in: apparmor
Status: Fix Committed => Fix Released
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to apparmor in Ubuntu.
https://bugs.launchpad.net/bugs/1717714
Title:
@{pid} variable broken on systems with pid_max more than 6 digits
Status in AppArmor:
Fix Released
Status in AppArmor 2.11 series:
Fix Committed
Status in apparmor package in Ubuntu:
Fix Released
Status in apparmor source package in Trusty:
Fix Released
Status in apparmor source package in Xenial:
Fix Released
Status in apparmor source package in Artful:
Fix Released
Status in apparmor source package in Bionic:
Fix Released
Status in apparmor package in Debian:
Fix Released
Bug description:
[Impact]
If PID is larger than 6 digits apparmor denies process which only
affect 64-bit systems[1] where the PID_MAX_LIMIT can be generated up
to 7 digits at the maximum.
This fix is committed, but not released. so all supporting version are
affected.
[1] - man 5 proc
--
/proc/sys/kernel/pid_max (since Linux 2.5.34)
This file specifies the value at which PIDs wrap around (i.e., the value in
this file is one greater than the maximum PID). PIDs greater than this value
are not allocated; thus, the value in this file also acts as a system-wide
limit on the total number of processes and threads. The default value for this
file, 32768, results in the same range of PIDs as on ear‐lier kernels. On
32-bit platforms, 32768 is the maximum value for pid_max. On 64-bit systems,
pid_max can be set to any value up to 2^22 (PID_MAX_LIMIT, approximately 4
million).
--
[Test Case]
1. making pid over 6 digits
#!/bin/bash
for i in {1..100}
do
touch t
done
2. snap install --dangerous core_16-2.29.4.2_amd64.snap ( snap core
16-2.30 avoids using /proc/PID/cmdline, so need to use older version
3. you can see DENIED msgs in syslog
4. change /etc/apparmor.d/tunables/kernelvars
5. service apparmor restart
6. service snapd restart
7. DENIED is gone
This is one way, can't reproduce this issue again even if you change
back to original kernelvars, and restart snapd
OR
instead of Seyeong's touch approach, things can be manually change to
7 digits range via sysctl as long as the values are below
approximately 4 millions :
Example:
$ sysctl -w kernel.pid_max=300
$ sysctl -w kernel.ns_last_pid=100
[Regression]
* This is a minor/trivial fix which changes the pid regex only, allowing 7
digits PID instead of only 6 digits PID, we don't think there is any potential
regression.
* If a regression arise, which we highly doubt, one can quickly revert
the change manually and restart the service by modifying
"/etc/apparmor.d/tunables/kernelvars" file to its original state
(before this SRU).
[Others]
* Upstream commit:
https://gitlab.com/apparmor/apparmor/commit/630cb2a981cdc731847e8fdaafc45bcd337fe747
http://bazaar.launchpad.net/~apparmor-dev/apparmor/master/revision/3722
* Debian bug:
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=886732
* commit 630cb2a981cdc731847e8fdaafc45bcd337fe747
Author: Vincas Dargis
Date: Sat Sep 30 15:28:15 2017 +0300
Allow seven digit pid
* Affecting releases : TXZAB
--
$ git describe --contains 630cb2a9
v2.11.95~5^2
$ rmadison apparmor
apparmor | 2.8.95~2430-0ubuntu5 | trusty
apparmor | 2.10.95-0ubuntu2.6~14.04.1 | trusty-security
apparmor | 2.10.95-0ubuntu2.6~14.04.1 | trusty-updates
apparmor | 2.10.95-0ubuntu2 | xenial
apparmor | 2.10.95-0ubuntu2.6 | xenial-security
apparmor | 2.10.95-0ubuntu2.7 | xenial-updates
apparmor | 2.11.0-2ubuntu4| zesty
apparmor | 2.11.0-2ubuntu17 | artful
apparmor | 2.11.0-2ubuntu18 | bionic
$ rmadison -u debian apparmor
apparmor | 2.11.1-4 | unstable
--
[Original Description]
If your kernel.pid_max sysctl is set higher than the default, say at 7
digits, the @{pid} variable no longer matches all pids, causing some
breakage in any profile using it.
@{pid} is defined in /etc/apparmor.d/tunables:
@{pid}={[1-9],[1-9][0-9],[1-9][0-9][0-9],[1-9][0-9][0-9][0-9],[1-9][0-9][0-9][0-9][0-9],[1-9][0-9][0-9][0-9][0-9][0-9]}
It only covers up to 6 digits.
This Ubuntu 17.04 system has:
kernel.pid_max = 4194303
And is showing
type=1400 audit(1505588857.828:792): apparmor="DENIED" operation="open"
profile="libvirt-55e9e12c-e6dc-4f56-a547-8514cf7d9bf3"
name="/proc/2168180/task/2769256/comm" pid=2168180 comm="qemu-system-x86"
requested_mask="wr" deni
Re: [Touch-packages] [Bug 1677924] Re: Local privilege escalation via guest user login
Sorry for being ignorant about this, but I don't know where to look I looked at Bugzilla for Kernel.org and it doesn't show there Where should I look? On Sun, Apr 22, 2018 at 2:24 PM, Oliver Grawert wrote: > This security fix seems to have caused some fallout ... see bug 1733557 > > -- > You received this bug notification because you are subscribed to the bug > report. > https://bugs.launchpad.net/bugs/1677924 > > Title: > Local privilege escalation via guest user login > > Status in Light Display Manager: > Fix Released > Status in Light Display Manager 1.18 series: > Fix Released > Status in Light Display Manager 1.20 series: > Fix Released > Status in Light Display Manager 1.22 series: > Fix Released > Status in lightdm package in Ubuntu: > Fix Released > Status in lightdm source package in Xenial: > Fix Released > Status in lightdm source package in Yakkety: > Fix Released > Status in lightdm source package in Zesty: > Fix Released > > Bug description: > It was discovered that a local attacker could watch for lightdm's > guest-account script to create a /tmp/guest-XX file and then quickly > create > the lowercase representation of the guest user's home directory before > lightdm > could. This allowed the attacker to have control of the guest user's home > directory and, subsequently, gain control of an arbitrary directory in the > filesystem which could lead to privilege escalation. > > To manage notifications about this bug go to: > https://bugs.launchpad.net/lightdm/+bug/1677924/+subscriptions -- Thanks, Noam Rathaus Beyond Security PGP Key ID: 7EF920D3C045D63F (Exp 2019-03) -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to lightdm in Ubuntu. https://bugs.launchpad.net/bugs/1677924 Title: Local privilege escalation via guest user login Status in Light Display Manager: Fix Released Status in Light Display Manager 1.18 series: Fix Released Status in Light Display Manager 1.20 series: Fix Released Status in Light Display Manager 1.22 series: Fix Released Status in lightdm package in Ubuntu: Fix Released Status in lightdm source package in Xenial: Fix Released Status in lightdm source package in Yakkety: Fix Released Status in lightdm source package in Zesty: Fix Released Bug description: It was discovered that a local attacker could watch for lightdm's guest-account script to create a /tmp/guest-XX file and then quickly create the lowercase representation of the guest user's home directory before lightdm could. This allowed the attacker to have control of the guest user's home directory and, subsequently, gain control of an arbitrary directory in the filesystem which could lead to privilege escalation. To manage notifications about this bug go to: https://bugs.launchpad.net/lightdm/+bug/1677924/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1730536] Re: "Unable to open external link" in Evince when google-chrome-unstable is the default browser
Fixed in AppArmor 2.12 ** Changed in: apparmor Status: Fix Committed => Fix Released -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to apparmor in Ubuntu. https://bugs.launchpad.net/bugs/1730536 Title: "Unable to open external link" in Evince when google-chrome-unstable is the default browser Status in AppArmor: Fix Released Status in apparmor package in Ubuntu: Fix Released Status in apparmor package in Debian: Confirmed Bug description: TO REPRODUCE: I attempt to open a URL from a PDF document in Evince. EXPECTED: The browser opens the URL. OBSERVED: I'm shown an error message: Unable to open external link Failed to execute child process “/usr/bin/google-chrome-unstable” (Permission denied) journalctl shows: Nov 06 19:19:18 khaeru-laptop audit[22110]: AVC apparmor="DENIED" operation="exec" profile="/usr/bin/evince" name="/opt/google/chrome-unstable/google-chrome-unstable" pid=22110 comm="evince" requested_mask="x" denied_mask="x" fsuid=1000 ouid=0 Nov 06 19:19:18 khaeru-laptop kernel: audit: type=1400 audit(1510013958.773:590): apparmor="DENIED" operation="exec" profile="/usr/bin/evince" name="/opt/google/chrome-unstable/google-chrome-unstable" pid=22110 comm="evince" requested_mask="x" denied_mask="x" fsuid=1000 ouid=0 EXTRA INFORMATION: - As the messages imply, I'm using Google Chrome "unstable". - The file /usr/bin/google-chrome-unstable …is symlinked to: /opt/google/chrome-unstable/google-chrome-unstable - I note that previous bugs, eg. bug #964510, resulted in lines being added to /etc/apparmor.d/abstractions/ubuntu-helpers that refer to paths in /opt/google/chrome/. This directory does not exist on my system. $ lsb_release -rd && apt-cache policy apparmor evince google-chrome-unstable Description:Ubuntu 17.10 Release:17.10 apparmor: Installed: 2.11.0-2ubuntu17 Candidate: 2.11.0-2ubuntu17 Version table: *** 2.11.0-2ubuntu17 500 500 http://us.archive.ubuntu.com/ubuntu artful/main amd64 Packages 100 /var/lib/dpkg/status evince: Installed: 3.26.0-1 Candidate: 3.26.0-1 Version table: *** 3.26.0-1 500 500 http://us.archive.ubuntu.com/ubuntu artful/main amd64 Packages 100 /var/lib/dpkg/status google-chrome-unstable: Installed: 64.0.3251.0-1 Candidate: 64.0.3253.3-1 Version table: 64.0.3253.3-1 500 500 http://dl.google.com/linux/chrome/deb stable/main amd64 Packages *** 64.0.3251.0-1 100 100 /var/lib/dpkg/status ProblemType: Bug DistroRelease: Ubuntu 17.10 Package: apparmor 2.11.0-2ubuntu17 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.1 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Mon Nov 6 19:20:34 2017 EcryptfsInUse: Yes InstallationDate: Installed on 2017-10-11 (26 days ago) InstallationMedia: Ubuntu 17.04 "Zesty Zapus" - Release amd64 (20170412) ProcKernelCmdline: BOOT_IMAGE=/boot/vmlinuz-4.13.0-16-generic.efi.signed root=UUID=39ca3c53-0313-4699-a5da-403522e2ff14 ro quiet splash vt.handoff=7 SourcePackage: apparmor Syslog: UpgradeStatus: Upgraded to artful on 2017-10-19 (18 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/apparmor/+bug/1730536/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1590561] Re: webbrowser-app crashes on startup on fresh zesty Unity8: No suitable EGL configs found
** Changed in: apparmor Status: Fix Committed => Fix Released -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to apparmor in Ubuntu. https://bugs.launchpad.net/bugs/1590561 Title: webbrowser-app crashes on startup on fresh zesty Unity8: No suitable EGL configs found Status in AppArmor: Fix Released Status in Canonical System Image: Fix Released Status in Oxide: Invalid Status in apparmor package in Ubuntu: Fix Released Status in unity8 package in Ubuntu: Invalid Status in webbrowser-app package in Ubuntu: Fix Released Bug description: When trying to start webbrowser-app a unresponsive window appears and after a few moments it crashes. ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: webbrowser-app 0.23+16.04.20160413-0ubuntu1 ProcVersionSignature: Ubuntu 4.4.0-22.40-generic 4.4.8 Uname: Linux 4.4.0-22-generic x86_64 NonfreeKernelModules: nvidia_uvm nvidia_modeset nvidia ApportVersion: 2.20.1-0ubuntu2 Architecture: amd64 CurrentDesktop: Unity Date: Wed Jun 8 22:56:35 2016 InstallationDate: Installed on 2016-04-28 (41 days ago) InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 (20160420.1) SourcePackage: webbrowser-app UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/apparmor/+bug/1590561/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1766074] [NEW] unity 7.4.5.5+16.04.20180221-0ubuntu1 Crash
Public bug reported: /usr/lib/x86_64-linux-gnu/unity/compiz-config-profile-setter ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: xorg 1:7.7+13ubuntu3 ProcVersionSignature: Ubuntu 4.4.0-119.143-generic 4.4.114 Uname: Linux 4.4.0-119-generic x86_64 .tmp.unity_support_test.1: ApportVersion: 2.20.1-0ubuntu2.16 Architecture: amd64 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: compiz CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0' CompositorUnredirectFSW: true Date: Sun Apr 22 12:58:12 2018 DistUpgraded: Fresh install DistroCodename: xenial DistroVariant: ubuntu ExtraDebuggingInterest: Yes, if not too technical GraphicsCard: Intel Corporation 82Q963/Q965 Integrated Graphics Controller [8086:2992] (rev 02) (prog-if 00 [VGA controller]) Subsystem: Hewlett-Packard Company 82Q963/Q965 Integrated Graphics Controller [103c:2808] InstallationDate: Installed on 2014-08-29 (1331 days ago) InstallationMedia: Ubuntu 14.04.1 LTS "Trusty Tahr" - Release amd64 (20140722.2) MachineType: Hewlett-Packard HP Compaq dc5700 Microtower ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-119-generic root=UUID=364b6e92-64f0-41cf-a72c-57b437758d52 ro recovery nomodeset Renderer: Software SourcePackage: xorg UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 04/13/2007 dmi.bios.vendor: Hewlett-Packard dmi.bios.version: 786E2 v02.04 dmi.board.name: 0A60h dmi.board.vendor: Hewlett-Packard dmi.chassis.asset.tag: CZC7424GG3 dmi.chassis.type: 6 dmi.chassis.vendor: Hewlett-Packard dmi.modalias: dmi:bvnHewlett-Packard:bvr786E2v02.04:bd04/13/2007:svnHewlett-Packard:pnHPCompaqdc5700Microtower:pvr:rvnHewlett-Packard:rn0A60h:rvr:cvnHewlett-Packard:ct6:cvr: dmi.product.name: HP Compaq dc5700 Microtower dmi.sys.vendor: Hewlett-Packard version.compiz: compiz 1:0.9.12.3+16.04.20180221-0ubuntu1 version.ia32-libs: ia32-libs N/A version.libdrm2: libdrm2 2.4.83-1~16.04.1 version.libgl1-mesa-dri: libgl1-mesa-dri 17.2.8-0ubuntu0~16.04.1 version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A version.libgl1-mesa-glx: libgl1-mesa-glx 17.2.8-0ubuntu0~16.04.1 version.xserver-xorg-core: xserver-xorg-core 2:1.18.4-0ubuntu0.7 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.10.1-1ubuntu2 version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.7.0-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20160325-1ubuntu1.2 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.12-1build2 xserver.bootTime: Sun Apr 22 12:56:18 2018 xserver.configfile: default xserver.logfile: /var/log/Xorg.0.log xserver.version: 2:1.18.4-0ubuntu0.7 ** Affects: xorg (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug compiz-0.9 ubuntu xenial -- 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/1766074 Title: unity 7.4.5.5+16.04.20180221-0ubuntu1 Crash Status in xorg package in Ubuntu: New Bug description: /usr/lib/x86_64-linux-gnu/unity/compiz-config-profile-setter ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: xorg 1:7.7+13ubuntu3 ProcVersionSignature: Ubuntu 4.4.0-119.143-generic 4.4.114 Uname: Linux 4.4.0-119-generic x86_64 .tmp.unity_support_test.1: ApportVersion: 2.20.1-0ubuntu2.16 Architecture: amd64 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: compiz CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0' CompositorUnredirectFSW: true Date: Sun Apr 22 12:58:12 2018 DistUpgraded: Fresh install DistroCodename: xenial DistroVariant: ubuntu ExtraDebuggingInterest: Yes, if not too technical GraphicsCard: Intel Corporation 82Q963/Q965 Integrated Graphics Controller [8086:2992] (rev 02) (prog-if 00 [VGA controller]) Subsystem: Hewlett-Packard Company 82Q963/Q965 Integrated Graphics Controller [103c:2808] InstallationDate: Installed on 2014-08-29 (1331 days ago) InstallationMedia: Ubuntu 14.04.1 LTS "Trusty Tahr" - Release amd64 (20140722.2) MachineType: Hewlett-Packard HP Compaq dc5700 Microtower ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-119-generic root=UUID=364b6e92-64f0-41cf-a72c-57b437758d52 ro recovery nomodeset Renderer: Software SourcePackage: xorg UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 04/13/2007 dmi.bios.vendor: Hewlett-Packard dmi.bios.version: 786E2 v02.04 dmi.board.name: 0A60h dmi.board.vendor: Hewlett-Packard dmi.chassis.asset.tag: CZC7424GG3 dmi.chassis.type: 6 dmi.chassis.vendor: Hewlett-Packard dmi.modalias: dmi:bvnHewlett-Packard:bvr786E2v02.04:bd04/13/2007:svnHewlett-Packard:pnHPCompaqdc5700Microtower:pvr:rvnHewlett-Packard:rn0A60h:rvr:cvnHewlett-Packard:ct6:cvr: dmi.product.name: HP Compaq dc5700 Microtower dmi.sy
[Touch-packages] [Bug 1668892] Re: CVE-2017-6507: apparmor service restarts and package upgrades unload privately managed profiles
** Changed in: apparmor Status: Fix Committed => Fix Released -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to apparmor in Ubuntu. https://bugs.launchpad.net/bugs/1668892 Title: CVE-2017-6507: apparmor service restarts and package upgrades unload privately managed profiles Status in AppArmor: Fix Released Status in AppArmor 2.10 series: Fix Released Status in AppArmor 2.11 series: Fix Released Status in AppArmor 2.9 series: Fix Released Status in apparmor package in Ubuntu: Fix Released Bug description: Restarting the apparmor init script, upstart job, or systemd service has historically removed all loaded profiles unknown to the well-known profile locations. In upstream AppArmor terms, this is /etc/apparmor.d/ but Ubuntu also adds additional locations. This behavior has previously caused a problem where libvirt-managed profiles would be unloaded upon "restarting AppArmor": https://launchpad.net/bugs/702774 Stéphane Graber created this bug report after he noticed that the same behavior was causing similar problems with lxd-manager profiles. In addition, AppArmor distro packaging may trigger an "AppArmor restart" when installing a new version of AppArmor, resulting in the same profile removal problem. This is true for the Debian/Ubuntu packaging. The upstream AppArmor team has decided to remove this functionality from the AppArmor restart logic to prevent a similar issue happening with the next external project that needs to privately manage their own set of AppArmor profiles. === Original Bug Report === Apparmor package upgrades unloads all LXD apparmor profiles, making all LXD containers unconfined. Example: # Create an unprivileged and a privileged container stgraber@dakara:~/data/code/lxc/lxd (stgraber/master)$ lxc launch ubuntu:16.04 c1 Creating c1 Starting c1 stgraber@dakara:~/data/code/lxc/lxd (stgraber/master)$ lxc launch ubuntu:16.04 c2 -c security.privileged=true Creating c2 Starting c2 # Look at their apparmor profiles (expected values) stgraber@dakara:~/data/code/lxc/lxd (stgraber/master)$ cat /proc/$(lxc info c1 | grep Pid | sed "s/Pid: //g")/attr/current lxd-c1_//&:lxd-c1_://unconfined (enforce) stgraber@dakara:~/data/code/lxc/lxd (stgraber/master)$ cat /proc/$(lxc info c2 | grep Pid | sed "s/Pid: //g")/attr/current lxd-c2_//&:lxd-c2_://unconfined (enforce) # Apply an apparmor upgrade stgraber@dakara:~/data/code/lxc/lxd (stgraber/master)$ sudo apt upgrade Reading package lists... Done Building dependency tree Reading state information... Done Calculating upgrade... Done The following packages will be upgraded: apparmor 1 upgraded, 0 newly installed, 0 to remove and 0 not upgraded. Need to get 493 kB of archives. After this operation, 8,192 B of additional disk space will be used. Do you want to continue? [Y/n] Get:1 http://us.archive.ubuntu.com/ubuntu zesty/main amd64 apparmor amd64 2.11.0-2ubuntu1 [493 kB] Fetched 493 kB in 0s (34.9 MB/s) Preconfiguring packages ... (Reading database ... 221457 files and directories currently installed.) Preparing to unpack .../apparmor_2.11.0-2ubuntu1_amd64.deb ... Unpacking apparmor (2.11.0-2ubuntu1) over (2.10.95-4ubuntu5.1) ... Processing triggers for ureadahead (0.100.0-19) ... Setting up apparmor (2.11.0-2ubuntu1) ... Installing new version of config file /etc/apparmor.d/abstractions/X ... Installing new version of config file /etc/apparmor.d/abstractions/authentication ... Installing new version of config file /etc/apparmor.d/abstractions/base ... Installing new version of config file /etc/apparmor.d/abstractions/dbus-session-strict ... Installing new version of config file /etc/apparmor.d/abstractions/gnome ... Installing new version of config file /etc/apparmor.d/abstractions/nameservice ... Installing new version of config file /etc/apparmor.d/abstractions/php5 ... Installing new version of config file /etc/apparmor.d/abstractions/samba ... Installing new version of config file /etc/apparmor.d/abstractions/ssl_certs ... Installing new version of config file /etc/apparmor.d/abstractions/ssl_keys ... Installing new version of config file /etc/apparmor.d/abstractions/ubuntu-browsers ... Installing new version of config file /etc/apparmor.d/abstractions/ubuntu-helpers ... Installing new version of config file /etc/apparmor.d/abstractions/user-mail ... update-rc.d: warning: start and stop actions are no longer supported; falling back to defaults Skipping profile in /etc/apparmor.d/disable: usr.sbin.rsyslogd Skipping profile in /etc/apparmor.d/disable: usr.sbin.sssd Processing triggers for systemd (232-18ubuntu1) ... Processing triggers for man-db (2.7.6.1-1) ... # And look at the now unconfined containers stgraber@dakara:~/data/code/lxc/lxd (stgraber/master)$ cat /proc/$(lxc info c1 |
[Touch-packages] [Bug 1677924] Re: Local privilege escalation via guest user login
This security fix seems to have caused some fallout ... see bug 1733557 -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to lightdm in Ubuntu. https://bugs.launchpad.net/bugs/1677924 Title: Local privilege escalation via guest user login Status in Light Display Manager: Fix Released Status in Light Display Manager 1.18 series: Fix Released Status in Light Display Manager 1.20 series: Fix Released Status in Light Display Manager 1.22 series: Fix Released Status in lightdm package in Ubuntu: Fix Released Status in lightdm source package in Xenial: Fix Released Status in lightdm source package in Yakkety: Fix Released Status in lightdm source package in Zesty: Fix Released Bug description: It was discovered that a local attacker could watch for lightdm's guest-account script to create a /tmp/guest-XX file and then quickly create the lowercase representation of the guest user's home directory before lightdm could. This allowed the attacker to have control of the guest user's home directory and, subsequently, gain control of an arbitrary directory in the filesystem which could lead to privilege escalation. To manage notifications about this bug go to: https://bugs.launchpad.net/lightdm/+bug/1677924/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1766073] [NEW] boot up hangs on a blank scrIeen
Public bug reported: I have had booting problems shortly after upgrading to V. 17. I can get the machine to boot using F2. Once I get the desktop, everything works fine. Thanks! ProblemType: Bug DistroRelease: Ubuntu 17.10 Package: xorg 1:7.7+19ubuntu3 ProcVersionSignature: Ubuntu 4.13.0-38.43-generic 4.13.16 Uname: Linux 4.13.0-38-generic i686 .tmp.unity_support_test.1: ApportVersion: 2.20.7-0ubuntu3.8 Architecture: i386 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: None Date: Sun Apr 22 07:08:17 2018 DistUpgraded: 2018-04-04 22:30:53,199 DEBUG icon theme changed, re-reading DistroCodename: artful DistroVariant: ubuntu DkmsStatus: i915-4.6.3-4.4.0, 1: added ExtraDebuggingInterest: Yes, if not too technical GraphicsCard: Intel Corporation Mobile GM965/GL960 Integrated Graphics Controller (primary) [8086:2a02] (rev 03) (prog-if 00 [VGA controller]) Subsystem: Acer Incorporated [ALI] Mobile GM965/GL960 Integrated Graphics Controller (primary) [1025:011e] Subsystem: Acer Incorporated [ALI] Mobile GM965/GL960 Integrated Graphics Controller (secondary) [1025:011e] InstallationDate: Installed on 2016-08-02 (627 days ago) InstallationMedia: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release i386 (20160719) MachineType: Acer Aspire 5720 ProcEnviron: PATH=(custom, no user) LANG=en_US.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.13.0-38-generic root=UUID=e4631648-f8d1-4d71-af95-43fe3ed0cef7 ro recovery nomodeset Renderer: Software SourcePackage: xorg UpgradeStatus: Upgraded to artful on 2018-04-05 (17 days ago) dmi.bios.date: 11/09/2007 dmi.bios.vendor: Acer dmi.bios.version: V1.21 dmi.board.asset.tag: Base Board Asset Tag dmi.board.name: Nettiling dmi.board.vendor: Acer dmi.board.version: V1.21 dmi.chassis.type: 1 dmi.chassis.vendor: Acer dmi.chassis.version: V1.21 dmi.modalias: dmi:bvnAcer:bvrV1.21:bd11/09/2007:svnAcer:pnAspire5720:pvrV1.21:rvnAcer:rnNettiling:rvrV1.21:cvnAcer:ct1:cvrV1.21: dmi.product.family: None dmi.product.name: Aspire 5720 dmi.product.version: V1.21 dmi.sys.vendor: Acer version.compiz: compiz 1:0.9.13.1+17.10.20170901-0ubuntu1 version.libdrm2: libdrm2 2.4.83-1 version.libgl1-mesa-dri: libgl1-mesa-dri 17.2.8-0ubuntu0~17.10.1 version.libgl1-mesa-glx: libgl1-mesa-glx 17.2.8-0ubuntu0~17.10.1 version.xserver-xorg-core: xserver-xorg-core 2:1.19.5-0ubuntu2 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.10.5-1ubuntu1 version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.10.0-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20170309-0ubuntu1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.15-2 xserver.bootTime: Sun Apr 22 07:06:00 2018 xserver.configfile: default xserver.logfile: /var/log/Xorg.0.log xserver.version: 2:1.19.5-0ubuntu2 ** Affects: xorg (Ubuntu) Importance: Undecided Status: New ** Tags: apport-bug artful i386 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/1766073 Title: boot up hangs on a blank scrIeen Status in xorg package in Ubuntu: New Bug description: I have had booting problems shortly after upgrading to V. 17. I can get the machine to boot using F2. Once I get the desktop, everything works fine. Thanks! ProblemType: Bug DistroRelease: Ubuntu 17.10 Package: xorg 1:7.7+19ubuntu3 ProcVersionSignature: Ubuntu 4.13.0-38.43-generic 4.13.16 Uname: Linux 4.13.0-38-generic i686 .tmp.unity_support_test.1: ApportVersion: 2.20.7-0ubuntu3.8 Architecture: i386 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: None Date: Sun Apr 22 07:08:17 2018 DistUpgraded: 2018-04-04 22:30:53,199 DEBUG icon theme changed, re-reading DistroCodename: artful DistroVariant: ubuntu DkmsStatus: i915-4.6.3-4.4.0, 1: added ExtraDebuggingInterest: Yes, if not too technical GraphicsCard: Intel Corporation Mobile GM965/GL960 Integrated Graphics Controller (primary) [8086:2a02] (rev 03) (prog-if 00 [VGA controller]) Subsystem: Acer Incorporated [ALI] Mobile GM965/GL960 Integrated Graphics Controller (primary) [1025:011e] Subsystem: Acer Incorporated [ALI] Mobile GM965/GL960 Integrated Graphics Controller (secondary) [1025:011e] InstallationDate: Installed on 2016-08-02 (627 days ago) InstallationMedia: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release i386 (20160719) MachineType: Acer Aspire 5720 ProcEnviron: PATH=(custom, no user) LANG=en_US.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.13.0-38-generic root=UUID=e4631648-f8d1-4d71-af95-43fe3ed0cef7 ro recovery nomodeset Renderer: Software SourcePackage: xorg UpgradeStatus: Upgraded to artful on 2018-04-05 (17 days ago) dmi.bios.date: 11/09/2007 dmi.bios.vendor: Acer dmi.bios.version: V1.21
[Touch-packages] [Bug 1766063] Re: mm (Myanmar / Burmese) for zawgyi keyboard layout
** Changed in: xkeyboard-config Status: Unknown => Confirmed ** Changed in: xkeyboard-config (Debian) Status: Unknown => Confirmed ** Changed in: xkeyboard-config Importance: Unknown => Medium ** Changed in: xkeyboard-config (Debian) Importance: Unknown => Medium -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to xkeyboard-config in Ubuntu. https://bugs.launchpad.net/bugs/1766063 Title: mm (Myanmar / Burmese) for zawgyi keyboard layout Status in xkeyboard-config: Confirmed Status in xkeyboard-config package in Ubuntu: New Status in xkeyboard-config package in Debian: Confirmed Status in xkeyboard-config package in Fedora: New Status in xkeyboard-config package in Unity Linux: New Bug description: https://bugs.freedesktop.org/show_bug.cgi?id=106169 New Keyboard Layout addition in Myanmar / Burmese --- New Keyboard Layout --- Added New Keyboard Layout - Burmese Zawgyi Keyboard This is similar to Burmese MM. Its most popular keyboard in Burmese. To manage notifications about this bug go to: https://bugs.launchpad.net/xkeyboard-config/+bug/1766063/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1203711] Re: uninitialised list pointer in configuration directory handling
nie wiem co powiedzieć
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to lightdm in Ubuntu.
https://bugs.launchpad.net/bugs/1203711
Title:
uninitialised list pointer in configuration directory handling
Status in Light Display Manager:
Fix Released
Status in lightdm package in Ubuntu:
Fix Released
Bug description:
We seem to have an uninitialised GList pointer in the directory
handling for the configuration directory.
main(...)
[...]
if (config_d_dir)
{
GDir *dir;
GList *files, *link;
[...]
files = g_list_append (files, g_strdup (name));
[...]
}
This leads to SIGSEGV during startup. Oddly this is rarely triggered,
I would expect this to be common.
To manage notifications about this bug go to:
https://bugs.launchpad.net/lightdm/+bug/1203711/+subscriptions
--
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1766063] [NEW] mm (Myanmar / Burmese) for zawgyi keyboard layout
Public bug reported: https://bugs.freedesktop.org/show_bug.cgi?id=106169 New Keyboard Layout addition in Myanmar / Burmese --- New Keyboard Layout --- Added New Keyboard Layout - Burmese Zawgyi Keyboard This is similar to Burmese MM. Its most popular keyboard in Burmese. ** Affects: xkeyboard-config Importance: Unknown Status: Unknown ** Affects: xkeyboard-config (Ubuntu) Importance: Undecided Status: New ** Affects: xkeyboard-config (Debian) Importance: Unknown Status: Unknown ** Affects: xkeyboard-config (Fedora) Importance: Undecided Status: New ** Affects: xkeyboard-config (Unity Linux) Importance: Undecided Status: New ** Tags: xkeyboard-config ** Branch linked: lp:~kokoye2007/xkeyboard-config/xkeyboard-config ** Tags added: keyboard ** Description changed: https://bugs.freedesktop.org/show_bug.cgi?id=106169 + + + New Keyboard Layout addition in Myanmar / Burmese + + --- New Keyboard Layout --- + + Added New Keyboard Layout - Burmese Zawgyi Keyboard + This is similar to Burmese MM. + Its most popular keyboard in Burmese. ** Tags removed: keyboard ** Tags added: xkeyboard-config ** Also affects: xkeyboard-config (Fedora) Importance: Undecided Status: New ** Bug watch added: freedesktop.org Bugzilla #106169 https://bugs.freedesktop.org/show_bug.cgi?id=106169 ** Also affects: xkeyboard-config (Debian) via https://bugs.freedesktop.org/show_bug.cgi?id=106169 Importance: Unknown Status: Unknown ** Also affects: xkeyboard-config (Unity Linux) Importance: Undecided Status: New ** Also affects: xkeyboard-config via https://bugs.freedesktop.org/show_bug.cgi?id=106169 Importance: Unknown Status: Unknown -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to xkeyboard-config in Ubuntu. https://bugs.launchpad.net/bugs/1766063 Title: mm (Myanmar / Burmese) for zawgyi keyboard layout Status in xkeyboard-config: Unknown Status in xkeyboard-config package in Ubuntu: New Status in xkeyboard-config package in Debian: Unknown Status in xkeyboard-config package in Fedora: New Status in xkeyboard-config package in Unity Linux: New Bug description: https://bugs.freedesktop.org/show_bug.cgi?id=106169 New Keyboard Layout addition in Myanmar / Burmese --- New Keyboard Layout --- Added New Keyboard Layout - Burmese Zawgyi Keyboard This is similar to Burmese MM. Its most popular keyboard in Burmese. To manage notifications about this bug go to: https://bugs.launchpad.net/xkeyboard-config/+bug/1766063/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
