[Touch-packages] [Bug 1751716] [NEW] [Aspire 6930G, Realtek ALC888, Speaker, Internal] Sound is distorted
Public bug reported: After installing recent updates to sound libraries (see log below) sound is distorted, sounds like over-steered, especially right channel (I use build-in speakers with "stereo sound" option [BTW: I cannot get working sub-woofer]). == Upgrade log: Start-Date: 2018-02-26 07:52:58 Commandline: apt upgrade Requested-By: x (1000) Upgrade: libpulsedsp:amd64 (1:8.0-0ubuntu3.7, 1:8.0-0ubuntu3.8), grub-common:amd64 (2.02~beta2-36ubuntu3.16, 2.02~beta2-36ubuntu3.17), pulseaudio:amd64 (1:8.0-0ubuntu3.7, 1:8.0-0ubuntu3.8), python-apt-common:amd64 (1.1.0~beta1build1, 1.1.0~beta1ubuntu0.16.04.1), grub2-common:amd64 (2.02~beta2-36ubuntu3.16, 2.02~beta2-36ubuntu3.17), grub-pc:amd64 (2.02~beta2-36ubuntu3.16, 2.02~beta2-36ubuntu3.17), grub-pc-bin:amd64 (2.02~beta2-36ubuntu3.16, 2.02~beta2-36ubuntu3.17), ubuntu-drivers-common:amd64 (1:0.4.17.3, 1:0.4.17.6), python3-distupgrade:amd64 (1:16.04.23, 1:16.04.24), libpulse0:amd64 (1:8.0-0ubuntu3.7, 1:8.0-0ubuntu3.8), libpulse0:i386 (1:8.0-0ubuntu3.7, 1:8.0-0ubuntu3.8), ubuntu-release-upgrader-core:amd64 (1:16.04.23, 1:16.04.24), libpulse-mainloop-glib0:amd64 (1:8.0-0ubuntu3.7, 1:8.0-0ubuntu3.8), pulseaudio-module-x11:amd64 (1:8.0-0ubuntu3.7, 1:8.0-0ubuntu3.8), ubuntu-release-upgrader-gtk:amd64 (1:16.04.23, 1:16.04.24), pulseaudio-module-bluetooth:amd64 (1:8.0-0ubuntu3.7, 1:8.0-0ubuntu3.8), opera-stable:amd64 (51.0.2830.34, 51.0.2830.40), pulseaudio-utils:amd64 (1:8.0-0ubuntu3.7, 1:8.0-0ubuntu3.8), python3-apt:amd64 (1.1.0~beta1build1, 1.1.0~beta1ubuntu0.16.04.1), base-files:amd64 (9.4ubuntu4.5, 9.4ubuntu4.6) End-Date: 2018-02-26 07:58:28 ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: alsa-base 1.0.25+dfsg-0ubuntu5 ProcVersionSignature: Ubuntu 4.4.0-116.140-generic 4.4.98 Uname: Linux 4.4.0-116-generic x86_64 NonfreeKernelModules: nvidia_uvm nvidia ApportVersion: 2.20.1-0ubuntu2.15 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: radek 2730 F pulseaudio CurrentDesktop: Unity Date: Mon Feb 26 08:19:21 2018 InstallationDate: Installed on 2017-11-10 (107 days ago) InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 (20160420.1) PackageArchitecture: all SourcePackage: alsa-driver Symptom: audio Symptom_AlsaPlaybackTest: ALSA playback test through plughw:Intel failed Symptom_Card: Built-in Audio - HDA Intel Symptom_Jack: Speaker, Internal Symptom_Type: Digital clip or distortion, or "overdriven" sound Title: [Aspire 6930G, Realtek ALC888, Speaker, Internal] Sound is distorted UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 08/14/2008 dmi.bios.vendor: Acer dmi.bios.version: v0.3120 dmi.board.name: Makalu dmi.board.vendor: Acer, Inc. dmi.board.version: Not Applicable dmi.chassis.type: 1 dmi.chassis.vendor: Acer, Inc. dmi.chassis.version: N/A dmi.modalias: dmi:bvnAcer:bvrv0.3120:bd08/14/2008:svnAcer,inc.:pnAspire6930G:pvrNotApplicable:rvnAcer,Inc.:rnMakalu:rvrNotApplicable:cvnAcer,Inc.:ct1:cvrN/A: dmi.product.name: Aspire 6930G dmi.product.version: Not Applicable dmi.sys.vendor: Acer, inc. ** 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/1751716 Title: [Aspire 6930G, Realtek ALC888, Speaker, Internal] Sound is distorted Status in alsa-driver package in Ubuntu: New Bug description: After installing recent updates to sound libraries (see log below) sound is distorted, sounds like over-steered, especially right channel (I use build-in speakers with "stereo sound" option [BTW: I cannot get working sub-woofer]). == Upgrade log: Start-Date: 2018-02-26 07:52:58 Commandline: apt upgrade Requested-By: x (1000) Upgrade: libpulsedsp:amd64 (1:8.0-0ubuntu3.7, 1:8.0-0ubuntu3.8), grub-common:amd64 (2.02~beta2-36ubuntu3.16, 2.02~beta2-36ubuntu3.17), pulseaudio:amd64 (1:8.0-0ubuntu3.7, 1:8.0-0ubuntu3.8), python-apt-common:amd64 (1.1.0~beta1build1, 1.1.0~beta1ubuntu0.16.04.1), grub2-common:amd64 (2.02~beta2-36ubuntu3.16, 2.02~beta2-36ubuntu3.17), grub-pc:amd64 (2.02~beta2-36ubuntu3.16, 2.02~beta2-36ubuntu3.17), grub-pc-bin:amd64 (2.02~beta2-36ubuntu3.16, 2.02~beta2-36ubuntu3.17), ubuntu-drivers-common:amd64 (1:0.4.17.3, 1:0.4.17.6), python3-distupgrade:amd64 (1:16.04.23, 1:16.04.24), libpulse0:amd64 (1:8.0-0ubuntu3.7, 1:8.0-0ubuntu3.8), libpulse0:i386 (1:8.0-0ubuntu3.7, 1:8.0-0ubuntu3.8), ubuntu-release-upgrader-core:amd64 (1:16.04.23, 1:16.04.24), libpulse-mainloop-glib0:amd64 (1:8.0-0ubuntu3.7, 1:8.0-0ubuntu3.8), pulseaudio-module-x11:amd64 (1:8.0-0ubuntu3.7, 1:8.0-0ubuntu3.8), ubuntu-release-upgrader-gtk:amd64 (1:16.04.23, 1:16.04.24), pulseaudio-module-bluetooth:amd64 (1:8.0-0ubuntu3.7, 1:8.0-0ubuntu3.8), opera-stable:amd64 (51.0
[Touch-packages] [Bug 1750586] Re: package python-minimal 2.7.12-1~16.04 failed to install/upgrade: subprocess installed post-installation script returned error exit status 1
I have three packages under /usr/share/python, I think they are all company specific packages. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to python-defaults in Ubuntu. https://bugs.launchpad.net/bugs/1750586 Title: package python-minimal 2.7.12-1~16.04 failed to install/upgrade: subprocess installed post-installation script returned error exit status 1 Status in python-defaults package in Ubuntu: Confirmed Bug description: There seems to be a dependency snarl: python-minimal is already the newest version (2.7.12-1~16.04). python-minimal set to manually installed. You might want to run 'apt-get -f install' to correct these: The following packages have unmet dependencies: python : PreDepends: python-minimal (= 2.7.11-1) but 2.7.12-1~16.04 is to be installed python-all : Depends: python (= 2.7.12-1~16.04) but 2.7.11-1 is to be installed python-all-dev : Depends: python (= 2.7.12-1~16.04) but 2.7.11-1 is to be installed Depends: libpython-all-dev (= 2.7.12-1~16.04) but 2.7.11-1 is to be installed python-dev : Depends: python (= 2.7.12-1~16.04) but 2.7.11-1 is to be installed Depends: libpython-dev (= 2.7.12-1~16.04) but 2.7.11-1 is to be installed E: Unmet dependencies. Try 'apt-get -f install' with no packages (or specify a solution). apt-get -f install tries to set up python-minimal (2.7.12-1~16.04) and returns 1. ProblemType: Package DistroRelease: Ubuntu 16.04 Package: python-minimal 2.7.12-1~16.04 ProcVersionSignature: Ubuntu 4.4.0-109.132-generic 4.4.98 Uname: Linux 4.4.0-109-generic x86_64 NonfreeKernelModules: nvidia_uvm nvidia ApportVersion: 2.20.1-0ubuntu2.15 Architecture: amd64 Date: Tue Feb 20 08:48:01 2018 DuplicateSignature: package:python-minimal:2.7.12-1~16.04 Setting up python-minimal (2.7.12-1~16.04) ... dpkg: error processing package python-minimal (--configure): subprocess installed post-installation script returned error exit status 1 ErrorMessage: subprocess installed post-installation script returned error exit status 1 InstallationDate: Installed on 2016-10-23 (484 days ago) InstallationMedia: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 (20160719) RelatedPackageVersions: dpkg 1.18.4ubuntu1.3 apt 1.2.25 SourcePackage: python-defaults Title: package python-minimal 2.7.12-1~16.04 failed to install/upgrade: subprocess installed post-installation script returned error exit status 1 UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/python-defaults/+bug/1750586/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1751712] Re: packagekitd crashed with SIGSEGV in AptIntf::providesCodec()
*** This bug is a duplicate of bug 1739916 *** https://bugs.launchpad.net/bugs/1739916 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 #1739916, 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/1751712/+attachment/5063242/+files/CoreDump.gz ** Attachment removed: "Disassembly.txt" https://bugs.launchpad.net/bugs/1751712/+attachment/5063244/+files/Disassembly.txt ** Attachment removed: "ProcMaps.txt" https://bugs.launchpad.net/bugs/1751712/+attachment/5063247/+files/ProcMaps.txt ** Attachment removed: "ProcStatus.txt" https://bugs.launchpad.net/bugs/1751712/+attachment/5063248/+files/ProcStatus.txt ** Attachment removed: "Registers.txt" https://bugs.launchpad.net/bugs/1751712/+attachment/5063249/+files/Registers.txt ** Attachment removed: "Stacktrace.txt" https://bugs.launchpad.net/bugs/1751712/+attachment/5063250/+files/Stacktrace.txt ** Attachment removed: "ThreadStacktrace.txt" https://bugs.launchpad.net/bugs/1751712/+attachment/5063251/+files/ThreadStacktrace.txt ** This bug has been marked a duplicate of private bug 1739916 ** 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 packagekit in Ubuntu. https://bugs.launchpad.net/bugs/1751712 Title: packagekitd crashed with SIGSEGV in AptIntf::providesCodec() Status in packagekit package in Ubuntu: New Bug description: internal error when opening ProblemType: Crash DistroRelease: Ubuntu 18.04 Package: packagekit 1.1.7-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 Date: Mon Feb 26 08:13:17 2018 ExecutablePath: /usr/lib/packagekit/packagekitd InstallationDate: Installed on 2018-02-21 (4 days ago) InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20180105.1) ProcCmdline: /usr/lib/packagekit/packagekitd ProcEnviron: LANG=en_AU.UTF-8 LANGUAGE=en_AU:en PATH=(custom, no user) SHELL=/bin/sh SegvAnalysis: Segfault happened at: 0x7f148b964476 <__strlen_sse2+38>: movdqu (%rax),%xmm4 PC (0x7f148b964476) ok source "(%rax)" (0x7f14ce3fe631) not located in a known VMA region (needed readable region)! destination "%xmm4" ok Stack memory exhausted (SP below stack segment) SegvReason: reading unknown VMA Signal: 11 SourcePackage: packagekit StacktraceTop: AptIntf::providesCodec(PkgList&, char**) () from /usr/lib/x86_64-linux-gnu/packagekit-backend/libpk_backend_aptcc.so ?? () from /usr/lib/x86_64-linux-gnu/packagekit-backend/libpk_backend_aptcc.so ?? () ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 start_thread (arg=0x7f1476456700) at pthread_create.c:465 Title: packagekitd crashed with SIGSEGV in AptIntf::providesCodec() UpgradeStatus: Upgraded to bionic on 2018-02-23 (2 days ago) UserGroups: To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/packagekit/+bug/1751712/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 405294] Re: A2DP Bluetooth audio skips terribly ["Skipping NNN us (= MMM bytes) in audio stream"]
Saleh: Thanks. Your system appears to be using: 03:00.0 Network controller: Broadcom Corporation BCM43142 802.11b/g/n (rev 01) Subsystem: XAVi Technologies Corp. BCM43142 802.11b/g/n Kernel driver in use: wl Kernel modules: bcma, wl Please try uninstalling package 'bcmwl-kernel-source', reboot, and assuming your wifi+bluetooth still works, please retest bluetooth audio performance and repeat 'lspci -k'. - EVERYONE ELSE STILL AFFECTED BY THIS BUG: Please try disabling your wifi, and then assuming bluetooth still works, tell us if the problem persists with wifi disabled. Please also provide output from 'lspci -k' and 'lsusb' on your machine. ** Changed in: bluez (Ubuntu) Status: Confirmed => Incomplete ** Changed in: linux (Ubuntu) Status: Confirmed => Incomplete ** Changed in: pulseaudio (Ubuntu) Status: Confirmed => Incomplete -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to bluez in Ubuntu. https://bugs.launchpad.net/bugs/405294 Title: A2DP Bluetooth audio skips terribly ["Skipping NNN us (= MMM bytes) in audio stream"] Status in PulseAudio: Confirmed Status in bluez package in Ubuntu: Incomplete Status in linux package in Ubuntu: Incomplete Status in pulseaudio package in Ubuntu: Incomplete Bug description: As I upgraded to the Karmic alpha, bluetooth audio (via a2dp) stopped working properly. It was working fine in Jaunty. My headphones are detected and configured by pulse, but the audio skips as if it's spending half of each second paused. Music is buffered so that after I click stop on rhythmbox (or whatever--it happens with whatever player I use) the audio continues until it's caught up. syslog is full of the following lines: Jul 27 08:55:45 carlin1 pulseaudio[3218]: alsa-source.c: Increasing minimal latency to 1.00 ms Jul 27 08:55:46 carlin1 pulseaudio[3218]: module-bluetooth-device.c: Skipping 15128 us (= 2668 bytes) in audio stream Jul 27 08:55:46 carlin1 pulseaudio[3218]: module-bluetooth-device.c: Skipping 36586 us (= 6452 bytes) in audio stream Jul 27 08:55:46 carlin1 pulseaudio[3218]: module-bluetooth-device.c: Skipping 35593 us (= 6276 bytes) in audio stream Jul 27 08:55:46 carlin1 pulseaudio[3218]: module-bluetooth-device.c: Skipping 36597 us (= 6452 bytes) in audio stream Jul 27 08:55:46 carlin1 pulseaudio[3218]: module-bluetooth-device.c: Skipping 32601 us (= 5748 bytes) in audio stream Jul 27 08:55:46 carlin1 pulseaudio[3218]: module-bluetooth-device.c: Skipping 32589 us (= 5748 bytes) in audio stream This is with bluez 4.45-0ubuntu4 pulseaudio1:0.9.15-4ubuntu2 0 pulseaudio version 1:0.9.16~test2-0ubuntu1~ppa3 from ubuntu-audio-dev didn't help. To manage notifications about this bug go to: https://bugs.launchpad.net/pulseaudio/+bug/405294/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 798962] Re: g-c-c "automatic login" settings not working with lightdm
** Changed in: accountsservice Status: Confirmed => Won't Fix -- 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/798962 Title: g-c-c "automatic login" settings not working with lightdm Status in accountsservice: Won't Fix Status in accountsservice package in Ubuntu: Fix Released Status in lightdm package in Ubuntu: Invalid Status in accountsservice source package in Oneiric: Fix Released Status in lightdm source package in Oneiric: Invalid Bug description: Binary package hint: gnome-control-center sytem, user accounts, select user, unlock, enter sudo pw, change "Automatic Login" to Yes, close window. drill into it, "Automatic Login" is No. Set to yes again, reboot, not logged in. ProblemType: Bug DistroRelease: Ubuntu 11.10 Package: gnome-control-center 1:3.0.2-1ubuntu4 ProcVersionSignature: Ubuntu 3.0-1.2-generic 3.0.0-rc3 Uname: Linux 3.0-1-generic x86_64 Architecture: amd64 Date: Fri Jun 17 16:01:44 2011 ExecutablePath: /usr/bin/gnome-control-center ProcEnviron: SHELL=/bin/bash PATH=(custom, user) LANGUAGE=en_US: LANG=en_US SourcePackage: gnome-control-center UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/accountsservice/+bug/798962/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 405294] Re: A2DP Bluetooth audio skips terribly ["Skipping NNN us (= MMM bytes) in audio stream"]
@Daniel van Vugt (vanvugt), here's my output! $ lspci -k 00:00.0 Host bridge: Intel Corporation 3rd Gen Core processor DRAM Controller (rev 09) Subsystem: Toshiba America Info Systems 3rd Gen Core processor DRAM Controller Kernel driver in use: ivb_uncore 00:02.0 VGA compatible controller: Intel Corporation 3rd Gen Core processor Graphics Controller (rev 09) Subsystem: Toshiba America Info Systems 3rd Gen Core processor Graphics Controller Kernel driver in use: i915 Kernel modules: i915 00:14.0 USB controller: Intel Corporation 7 Series/C210 Series Chipset Family USB xHCI Host Controller (rev 04) Subsystem: Toshiba America Info Systems 7 Series/C210 Series Chipset Family USB xHCI Host Controller Kernel driver in use: xhci_hcd 00:16.0 Communication controller: Intel Corporation 7 Series/C210 Series Chipset Family MEI Controller #1 (rev 04) Subsystem: Toshiba America Info Systems 7 Series/C210 Series Chipset Family MEI Controller Kernel driver in use: mei_me Kernel modules: mei_me 00:1a.0 USB controller: Intel Corporation 7 Series/C210 Series Chipset Family USB Enhanced Host Controller #2 (rev 04) Subsystem: Toshiba America Info Systems 7 Series/C210 Series Chipset Family USB Enhanced Host Controller Kernel driver in use: ehci-pci 00:1b.0 Audio device: Intel Corporation 7 Series/C210 Series Chipset Family High Definition Audio Controller (rev 04) Subsystem: Toshiba America Info Systems 7 Series/C210 Series Chipset Family High Definition Audio Controller Kernel driver in use: snd_hda_intel Kernel modules: snd_hda_intel 00:1c.0 PCI bridge: Intel Corporation 7 Series/C210 Series Chipset Family PCI Express Root Port 1 (rev c4) Kernel driver in use: pcieport Kernel modules: shpchp 00:1c.1 PCI bridge: Intel Corporation 7 Series/C210 Series Chipset Family PCI Express Root Port 2 (rev c4) Kernel driver in use: pcieport Kernel modules: shpchp 00:1c.2 PCI bridge: Intel Corporation 7 Series/C210 Series Chipset Family PCI Express Root Port 3 (rev c4) Kernel driver in use: pcieport Kernel modules: shpchp 00:1c.3 PCI bridge: Intel Corporation 7 Series/C210 Series Chipset Family PCI Express Root Port 4 (rev c4) Kernel driver in use: pcieport Kernel modules: shpchp 00:1d.0 USB controller: Intel Corporation 7 Series/C210 Series Chipset Family USB Enhanced Host Controller #1 (rev 04) Subsystem: Toshiba America Info Systems 7 Series/C210 Series Chipset Family USB Enhanced Host Controller Kernel driver in use: ehci-pci 00:1f.0 ISA bridge: Intel Corporation HM76 Express Chipset LPC Controller (rev 04) Subsystem: Toshiba America Info Systems HM76 Express Chipset LPC Controller Kernel driver in use: lpc_ich Kernel modules: lpc_ich 00:1f.2 SATA controller: Intel Corporation 7 Series Chipset Family 6-port SATA Controller [AHCI mode] (rev 04) Subsystem: Toshiba America Info Systems 7 Series Chipset Family 6-port SATA Controller [AHCI mode] Kernel driver in use: ahci Kernel modules: ahci 00:1f.3 SMBus: Intel Corporation 7 Series/C210 Series Chipset Family SMBus Controller (rev 04) Subsystem: Toshiba America Info Systems 7 Series/C210 Series Chipset Family SMBus Controller Kernel modules: i2c_i801 02:00.0 Unassigned class [ff00]: Realtek Semiconductor Co., Ltd. RTS5229 PCI Express Card Reader (rev 01) Subsystem: Toshiba America Info Systems RTS5229 PCI Express Card Reader Kernel driver in use: rtsx_pci Kernel modules: rtsx_pci 03:00.0 Network controller: Broadcom Corporation BCM43142 802.11b/g/n (rev 01) Subsystem: XAVi Technologies Corp. BCM43142 802.11b/g/n Kernel driver in use: wl Kernel modules: bcma, wl 04:00.0 Ethernet controller: Realtek Semiconductor Co., Ltd. RTL8101/2/6E PCI Express Fast/Gigabit Ethernet controller (rev 07) Subsystem: Toshiba America Info Systems RTL8101/2/6E PCI Express Fast/Gigabit Ethernet controller Kernel driver in use: r8169 Kernel modules: r8169 -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to bluez in Ubuntu. https://bugs.launchpad.net/bugs/405294 Title: A2DP Bluetooth audio skips terribly ["Skipping NNN us (= MMM bytes) in audio stream"] Status in PulseAudio: Confirmed Status in bluez package in Ubuntu: Confirmed Status in linux package in Ubuntu: Confirmed Status in pulseaudio package in Ubuntu: Confirmed Bug description: As I upgraded to the Karmic alpha, bluetooth audio (via a2dp) stopped working properly. It was working fine in Jaunty. My headphones are detected and configured by pulse, but the audio skips as if it's spending half of each second paused. Music is buffered so that after I click stop on rhythmbox (or whatever--it happens with w
[Touch-packages] [Bug 1751689] Re: apparmor="DENIED" operation="open" profile="libreoffice-soffice" name="/etc/sane.d/dll.d/hplip"
I believe the xsane crash is from me running it in a terminal and not exiting nicely. I just closed the terminal before shutting it down. -- 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/1751689 Title: apparmor="DENIED" operation="open" profile="libreoffice-soffice" name="/etc/sane.d/dll.d/hplip" Status in apport package in Ubuntu: New Bug description: currently able to scan with xsane utility. libreoffice is not able to scan because it cannot find the scanner. log shows Feb 25 21:44:34 know kernel: [ 2224.752585] audit: type=1400 audit(1519613074.593:93): apparmor="DENIED" operation="open" profile="libreoffice-soffice" name="/etc/sane.d/dll.d/hplip" pid=23827 comm="soffice.bin" requested_mask="r" denied_mask="r" fsuid=1001 ouid=0 Feb 25 21:44:34 know kernel: [ 2224.752589] audit: type=1400 audit(1519613074.593:94): apparmor="DENIED" operation="open" profile="libreoffice-soffice" name="/etc/sane.d/dll.conf" pid=23827 comm="soffice.bin" requested_mask="r" denied_mask="r" fsuid=1001 ouid=0 Feb 25 21:44:34 know kernel: [ 2224.752591] audit: type=1400 audit(1519613074.593:95): apparmor="DENIED" operation="open" profile="libreoffice-soffice" name="/home/darla/.so_sane_state" pid=23827 comm="soffice.bin" requested_mask="r" denied_mask="r" fsuid=1001 ouid=1001 this stopped working after latest "do-release-upgrade" ProblemType: Bug DistroRelease: Ubuntu 17.10 Package: apport 2.20.7-0ubuntu3.7 ProcVersionSignature: Ubuntu 4.13.0-36.40-generic 4.13.13 Uname: Linux 4.13.0-36-generic x86_64 NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia ApportVersion: 2.20.7-0ubuntu3.7 Architecture: amd64 CrashReports: 664:1001:121:0:2018-02-25 21:41:06.022625011 -0500:2018-02-25 21:41:06.022625011 -0500:/var/crash/_usr_bin_xsane.1001.upload 600:112:121:0:2018-02-25 21:41:10.086691806 -0500:2018-02-25 21:41:10.086691806 -0500:/var/crash/_usr_bin_xsane.1001.uploaded 640:1001:121:1939286:2018-02-25 21:41:05.022624969 -0500:2018-02-25 21:41:06.122626654 -0500:/var/crash/_usr_bin_xsane.1001.crash 640:1001:121:14271279:2018-02-25 20:56:20.565849525 -0500:2018-02-25 20:57:09.433475929 -0500:/var/crash/_usr_bin_ckb.1001.crash CurrentDesktop: XFCE Date: Sun Feb 25 22:00:01 2018 InstallationDate: Installed on 2017-04-19 (312 days ago) InstallationMedia: Xubuntu 17.04 "Zesty Zapus" - Release amd64 (20170412) PackageArchitecture: all SourcePackage: apport UpgradeStatus: Upgraded to artful on 2018-02-06 (20 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apport/+bug/1751689/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1751689] [NEW] apparmor="DENIED" operation="open" profile="libreoffice-soffice" name="/etc/sane.d/dll.d/hplip"
Public bug reported: currently able to scan with xsane utility. libreoffice is not able to scan because it cannot find the scanner. log shows Feb 25 21:44:34 know kernel: [ 2224.752585] audit: type=1400 audit(1519613074.593:93): apparmor="DENIED" operation="open" profile="libreoffice-soffice" name="/etc/sane.d/dll.d/hplip" pid=23827 comm="soffice.bin" requested_mask="r" denied_mask="r" fsuid=1001 ouid=0 Feb 25 21:44:34 know kernel: [ 2224.752589] audit: type=1400 audit(1519613074.593:94): apparmor="DENIED" operation="open" profile="libreoffice-soffice" name="/etc/sane.d/dll.conf" pid=23827 comm="soffice.bin" requested_mask="r" denied_mask="r" fsuid=1001 ouid=0 Feb 25 21:44:34 know kernel: [ 2224.752591] audit: type=1400 audit(1519613074.593:95): apparmor="DENIED" operation="open" profile="libreoffice-soffice" name="/home/darla/.so_sane_state" pid=23827 comm="soffice.bin" requested_mask="r" denied_mask="r" fsuid=1001 ouid=1001 this stopped working after latest "do-release-upgrade" ProblemType: Bug DistroRelease: Ubuntu 17.10 Package: apport 2.20.7-0ubuntu3.7 ProcVersionSignature: Ubuntu 4.13.0-36.40-generic 4.13.13 Uname: Linux 4.13.0-36-generic x86_64 NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia ApportVersion: 2.20.7-0ubuntu3.7 Architecture: amd64 CrashReports: 664:1001:121:0:2018-02-25 21:41:06.022625011 -0500:2018-02-25 21:41:06.022625011 -0500:/var/crash/_usr_bin_xsane.1001.upload 600:112:121:0:2018-02-25 21:41:10.086691806 -0500:2018-02-25 21:41:10.086691806 -0500:/var/crash/_usr_bin_xsane.1001.uploaded 640:1001:121:1939286:2018-02-25 21:41:05.022624969 -0500:2018-02-25 21:41:06.122626654 -0500:/var/crash/_usr_bin_xsane.1001.crash 640:1001:121:14271279:2018-02-25 20:56:20.565849525 -0500:2018-02-25 20:57:09.433475929 -0500:/var/crash/_usr_bin_ckb.1001.crash CurrentDesktop: XFCE Date: Sun Feb 25 22:00:01 2018 InstallationDate: Installed on 2017-04-19 (312 days ago) InstallationMedia: Xubuntu 17.04 "Zesty Zapus" - Release amd64 (20170412) PackageArchitecture: all SourcePackage: apport UpgradeStatus: Upgraded to artful on 2018-02-06 (20 days ago) ** Affects: apport (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug artful -- 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/1751689 Title: apparmor="DENIED" operation="open" profile="libreoffice-soffice" name="/etc/sane.d/dll.d/hplip" Status in apport package in Ubuntu: New Bug description: currently able to scan with xsane utility. libreoffice is not able to scan because it cannot find the scanner. log shows Feb 25 21:44:34 know kernel: [ 2224.752585] audit: type=1400 audit(1519613074.593:93): apparmor="DENIED" operation="open" profile="libreoffice-soffice" name="/etc/sane.d/dll.d/hplip" pid=23827 comm="soffice.bin" requested_mask="r" denied_mask="r" fsuid=1001 ouid=0 Feb 25 21:44:34 know kernel: [ 2224.752589] audit: type=1400 audit(1519613074.593:94): apparmor="DENIED" operation="open" profile="libreoffice-soffice" name="/etc/sane.d/dll.conf" pid=23827 comm="soffice.bin" requested_mask="r" denied_mask="r" fsuid=1001 ouid=0 Feb 25 21:44:34 know kernel: [ 2224.752591] audit: type=1400 audit(1519613074.593:95): apparmor="DENIED" operation="open" profile="libreoffice-soffice" name="/home/darla/.so_sane_state" pid=23827 comm="soffice.bin" requested_mask="r" denied_mask="r" fsuid=1001 ouid=1001 this stopped working after latest "do-release-upgrade" ProblemType: Bug DistroRelease: Ubuntu 17.10 Package: apport 2.20.7-0ubuntu3.7 ProcVersionSignature: Ubuntu 4.13.0-36.40-generic 4.13.13 Uname: Linux 4.13.0-36-generic x86_64 NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia ApportVersion: 2.20.7-0ubuntu3.7 Architecture: amd64 CrashReports: 664:1001:121:0:2018-02-25 21:41:06.022625011 -0500:2018-02-25 21:41:06.022625011 -0500:/var/crash/_usr_bin_xsane.1001.upload 600:112:121:0:2018-02-25 21:41:10.086691806 -0500:2018-02-25 21:41:10.086691806 -0500:/var/crash/_usr_bin_xsane.1001.uploaded 640:1001:121:1939286:2018-02-25 21:41:05.022624969 -0500:2018-02-25 21:41:06.122626654 -0500:/var/crash/_usr_bin_xsane.1001.crash 640:1001:121:14271279:2018-02-25 20:56:20.565849525 -0500:2018-02-25 20:57:09.433475929 -0500:/var/crash/_usr_bin_ckb.1001.crash CurrentDesktop: XFCE Date: Sun Feb 25 22:00:01 2018 InstallationDate: Installed on 2017-04-19 (312 days ago) InstallationMedia: Xubuntu 17.04 "Zesty Zapus" - Release amd64 (20170412) PackageArchitecture: all SourcePackage: apport UpgradeStatus: Upgraded to artful on 2018-02-06 (20 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apport/+bug/1751689/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : h
[Touch-packages] [Bug 1750379] Re: Distortion Realtek ALC887
Thanks. I wonder if your system has Over-Amplification stuck on (even if the GUI says otherwise). Can you please look at Settings > Sound and make sure that: 1. 'Over-Amplification' = OFF 2. Lower the value of 'Output volume' Can you find some combination of settings there that avoids the distortion? -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to pulseaudio in Ubuntu. https://bugs.launchpad.net/bugs/1750379 Title: Distortion Realtek ALC887 Status in linux package in Ubuntu: Incomplete Status in pulseaudio package in Ubuntu: Incomplete Bug description: Sounds can distort even when not amplified. Amplification worked well for years before recent PulseAudio update. The audio is Realtek ALC887 under an IntelG41 Chipset with GA-G41M-Combo main board; Description: Ubuntu Bionic Beaver (development branch) Release: 18.04 I am seeking to engage upstream for April LTS release. Windows have abandoned this esoteric hardware! Please Ubuntu! Keep a C2D user going! ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: pulseaudio 1:11.1-1ubuntu6 ProcVersionSignature: Ubuntu 4.13.0-32.35-generic 4.13.13 Uname: Linux 4.13.0-32-generic x86_64 NonfreeKernelModules: nvidia_uvm nvidia ApportVersion: 2.20.8-0ubuntu10 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: fleamour 1049 F pulseaudio /dev/snd/controlC2: fleamour 1049 F pulseaudio /dev/snd/controlC0: fleamour 1049 F pulseaudio CurrentDesktop: ubuntu:GNOME Date: Mon Feb 19 13:54:33 2018 InstallationDate: Installed on 2018-02-19 (0 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Alpha amd64 (20180214) ProcEnviron: LANGUAGE=en_GB:en PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_GB.UTF-8 SHELL=/bin/bash SourcePackage: pulseaudio UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 10/25/2012 dmi.bios.vendor: Award Software International, Inc. dmi.bios.version: FB dmi.board.name: G41M-Combo dmi.board.vendor: Gigabyte Technology Co., Ltd. dmi.board.version: x.x dmi.chassis.type: 3 dmi.chassis.vendor: Gigabyte Technology Co., Ltd. dmi.modalias: dmi:bvnAwardSoftwareInternational,Inc.:bvrFB:bd10/25/2012:svnGigabyteTechnologyCo.,Ltd.:pnG41M-Combo:pvr:rvnGigabyteTechnologyCo.,Ltd.:rnG41M-Combo:rvrx.x:cvnGigabyteTechnologyCo.,Ltd.:ct3:cvr: dmi.product.name: G41M-Combo dmi.sys.vendor: Gigabyte Technology Co., Ltd. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1750379/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1640139] Re: package libpulse0 (not installed) failed to install/upgrade: trying to overwrite shared '/etc/pulse/client.conf', which is different from other instances of package
** Tags added: artful -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to pulseaudio in Ubuntu. https://bugs.launchpad.net/bugs/1640139 Title: package libpulse0 (not installed) failed to install/upgrade: trying to overwrite shared '/etc/pulse/client.conf', which is different from other instances of package libpulse0:i386 Status in One Hundred Papercuts: Confirmed Status in pulseaudio package in Ubuntu: Confirmed Bug description: # lsb_release -a No LSB modules are available. Distributor ID: Ubuntu Description: Ubuntu 16.04.1 LTS Release: 16.04 Codename: xenial # uname -a Linux rotem-laptop 4.4.0-45-generic #66-Ubuntu SMP Wed Oct 19 14:12:37 UTC 2016 x86_64 x86_64 x86_64 GNU/Linux tried removing pulseaudio ProblemType: Package DistroRelease: Ubuntu 16.04 Package: libpulse0 (not installed) ProcVersionSignature: Ubuntu 4.4.0-45.66-generic 4.4.21 Uname: Linux 4.4.0-45-generic x86_64 ApportVersion: 2.20.1-0ubuntu2.1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: rotemfo2383 F pulseaudio /dev/snd/controlC0: rotemfo2383 F pulseaudio Date: Tue Nov 8 12:46:09 2016 DuplicateSignature: package:libpulse0:(not installed) Unpacking libpulse0:i386 (1:8.0-0ubuntu3) ... dpkg: error processing archive /var/cache/apt/archives/libpulse0_1%3a8.0-0ubuntu3_i386.deb (--unpack): trying to overwrite shared '/etc/pulse/client.conf', which is different from other instances of package libpulse0:i386 ErrorMessage: trying to overwrite shared '/etc/pulse/client.conf', which is different from other instances of package libpulse0:i386 InstallationDate: Installed on 2016-10-25 (14 days ago) InstallationMedia: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 (20160719) PulseList: Error: command ['pacmd', 'list'] failed with exit code 127: pacmd: error while loading shared libraries: libpulse.so.0: cannot open shared object file: No such file or directory RelatedPackageVersions: dpkg 1.18.4ubuntu1.1 apt 1.2.12~ubuntu16.04.1 SourcePackage: pulseaudio Title: package libpulse0 (not installed) failed to install/upgrade: trying to overwrite shared '/etc/pulse/client.conf', which is different from other instances of package libpulse0:i386 UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 05/17/2016 dmi.bios.vendor: Dell Inc. dmi.bios.version: A13 dmi.board.vendor: Dell Inc. dmi.chassis.type: 9 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvrA13:bd05/17/2016:svnDellInc.:pnLatitudeE7450:pvr:rvnDellInc.:rn:rvr:cvnDellInc.:ct9:cvr: dmi.product.name: Latitude E7450 dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/hundredpapercuts/+bug/1640139/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1751367] Re: package libpulse0 1:10.0-2ubuntu3.1 failed to install/upgrade: trying to overwrite shared '/etc/pulse/client.conf', which is different from other instances of packag
*** This bug is a duplicate of bug 1640139 *** https://bugs.launchpad.net/bugs/1640139 That is odd. And I can see no recent reason for it in the latest diff: https://launchpadlibrarian.net/356975252/pulseaudio_1%3A10.0-2ubuntu3_1%3A10.0-2ubuntu3.1.diff.gz So the most likely explanation is that it's a pre-existing bug. A theory seemingly confirmed by bug 1640139. ** This bug has been marked a duplicate of bug 1640139 package libpulse0 (not installed) failed to install/upgrade: trying to overwrite shared '/etc/pulse/client.conf', which is different from other instances of package libpulse0:i386 -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to pulseaudio in Ubuntu. https://bugs.launchpad.net/bugs/1751367 Title: package libpulse0 1:10.0-2ubuntu3.1 failed to install/upgrade: trying to overwrite shared '/etc/pulse/client.conf', which is different from other instances of package libpulse0:i386 Status in dpkg package in Ubuntu: New Status in pulseaudio package in Ubuntu: New Bug description: SRU fails to unpack due to reported changes to a conffile of a library installed in a multiarch configuration. ProblemType: Package DistroRelease: Ubuntu 17.10 Package: libpulse0 1:10.0-2ubuntu3.1 ProcVersionSignature: Ubuntu 4.13.0-32.35-generic 4.13.13 Uname: Linux 4.13.0-32-generic x86_64 NonfreeKernelModules: zfs zunicode zavl zcommon znvpair ApportVersion: 2.20.7-0ubuntu3.7 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: vorlon 6459 F pulseaudio /dev/snd/pcmC0D0p: vorlon 6459 F...m pulseaudio /dev/snd/controlC0: gdm5976 F pulseaudio vorlon 6459 F pulseaudio Date: Fri Feb 23 13:03:48 2018 DuplicateSignature: package:libpulse0:1:10.0-2ubuntu3.1 Unpacking libpulse0:i386 (1:10.0-2ubuntu3.1) over (1:10.0-2ubuntu3) ... dpkg: error processing archive /tmp/apt-dpkg-install-dJjkB5/058-libpulse0_1%3a10.0-2ubuntu3.1_i386.deb (--unpack): trying to overwrite shared '/etc/pulse/client.conf', which is different from other instances of package libpulse0:i386 ErrorMessage: trying to overwrite shared '/etc/pulse/client.conf', which is different from other instances of package libpulse0:i386 InstallationDate: Installed on 2010-09-24 (2709 days ago) InstallationMedia: Ubuntu 10.04.1 LTS "Lucid Lynx" - Release amd64 (20100816.1) PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon. 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: pulseaudio Title: package libpulse0 1:10.0-2ubuntu3.1 failed to install/upgrade: trying to overwrite shared '/etc/pulse/client.conf', which is different from other instances of package libpulse0:i386 UpgradeStatus: Upgraded to artful on 2017-10-19 (127 days ago) dmi.bios.date: 10/25/2013 dmi.bios.vendor: LENOVO dmi.bios.version: G2ET97WW (2.57 ) dmi.board.asset.tag: Not Available dmi.board.name: 2306CTO dmi.board.vendor: LENOVO dmi.board.version: Not Defined dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: Not Available dmi.modalias: dmi:bvnLENOVO:bvrG2ET97WW(2.57):bd10/25/2013:svnLENOVO:pn2306CTO:pvrThinkPadX230:rvnLENOVO:rn2306CTO:rvrNotDefined:cvnLENOVO:ct10:cvrNotAvailable: dmi.product.family: ThinkPad X230 dmi.product.name: 2306CTO dmi.product.version: ThinkPad X230 dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/dpkg/+bug/1751367/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1749472] Re: mesa 18.0.0 will cause rendering errors in Qt applications
That would be the ideal way to do it because the fix is already installable in the CI Train PPA for the next Qt transition: https://launchpad.net/~ci-train-ppa- service/+archive/ubuntu/3113/+packages That should be in -proposed before Feature Freeze, if not before then. Is there a compelling case to get this in *now* and not wait the (maybe) two days? -- 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/1749472 Title: mesa 18.0.0 will cause rendering errors in Qt applications Status in mesa package in Ubuntu: New Status in mesa source package in Bionic: New Bug description: From: https://bugreports.qt.io/browse/QTBUG-66348 ** extract ** The `QOpenGLShaderProgram` class in Qt can be used to compile and link OpenGL shaders. If the `GL_ARB_get_program_binary` OpenGL extension is available, it can cache those shaders on disk (~/.cache/qtshadercache). The i965 driver in Mesa supports this extension since version 18.0.0. When the shader is loaded using the `glProgramBinary` function, OpenGL can refuse it if for example some hardware or software component changed. Mesa refuses binaries that were created by any other build of Mesa (using among other things the build_id of the library). If the shader is refused, Qt should fallback to compiling it from sources, but it incorrectly calls glLinkProgram first. The glLinkProgram succeeds, because it actually links 0 shaders together. That is allowed in OpenGL compatibility profile and the resulting program works as a fixed pipeline. Which of course does not render as expected. This causes rendering errors in Qt applications every time Mesa is updated since version 18.0.0. For example white screen in sddm. This issue was originally reported in openSUSE (https://bugzilla.opensuse.org/show_bug.cgi?id=1080578). ** end extract ** As this potentially effects Qt applications, and could even render display manager login unusable, this should be a blocking bug in mesa and Qt until Qt mitigations patches pass codereview and can be included in Qtbase for 18.04. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mesa/+bug/1749472/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1749472] Re: mesa 18.0.0 will cause rendering errors in Qt applications
Is it possible to get just this fix in to bionic now without needing to do an entire Qt transition? The mesa transition has been blocking multiple GNOME transitions for a week and a half already. -- 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/1749472 Title: mesa 18.0.0 will cause rendering errors in Qt applications Status in mesa package in Ubuntu: New Status in mesa source package in Bionic: New Bug description: From: https://bugreports.qt.io/browse/QTBUG-66348 ** extract ** The `QOpenGLShaderProgram` class in Qt can be used to compile and link OpenGL shaders. If the `GL_ARB_get_program_binary` OpenGL extension is available, it can cache those shaders on disk (~/.cache/qtshadercache). The i965 driver in Mesa supports this extension since version 18.0.0. When the shader is loaded using the `glProgramBinary` function, OpenGL can refuse it if for example some hardware or software component changed. Mesa refuses binaries that were created by any other build of Mesa (using among other things the build_id of the library). If the shader is refused, Qt should fallback to compiling it from sources, but it incorrectly calls glLinkProgram first. The glLinkProgram succeeds, because it actually links 0 shaders together. That is allowed in OpenGL compatibility profile and the resulting program works as a fixed pipeline. Which of course does not render as expected. This causes rendering errors in Qt applications every time Mesa is updated since version 18.0.0. For example white screen in sddm. This issue was originally reported in openSUSE (https://bugzilla.opensuse.org/show_bug.cgi?id=1080578). ** end extract ** As this potentially effects Qt applications, and could even render display manager login unusable, this should be a blocking bug in mesa and Qt until Qt mitigations patches pass codereview and can be included in Qtbase for 18.04. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mesa/+bug/1749472/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1751679] Re: apport-gtk crashed with SIGSEGV
*** This bug is a duplicate of bug 1552577 *** https://bugs.launchpad.net/bugs/1552577 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 #1552577, 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/1751679/+attachment/5063112/+files/CoreDump.gz ** Attachment removed: "Disassembly.txt" https://bugs.launchpad.net/bugs/1751679/+attachment/5063114/+files/Disassembly.txt ** Attachment removed: "ProcMaps.txt" https://bugs.launchpad.net/bugs/1751679/+attachment/5063118/+files/ProcMaps.txt ** Attachment removed: "ProcStatus.txt" https://bugs.launchpad.net/bugs/1751679/+attachment/5063119/+files/ProcStatus.txt ** Attachment removed: "Registers.txt" https://bugs.launchpad.net/bugs/1751679/+attachment/5063120/+files/Registers.txt ** Attachment removed: "Stacktrace.txt" https://bugs.launchpad.net/bugs/1751679/+attachment/5063121/+files/Stacktrace.txt ** Attachment removed: "ThreadStacktrace.txt" https://bugs.launchpad.net/bugs/1751679/+attachment/5063122/+files/ThreadStacktrace.txt ** This bug has been marked a duplicate of bug 1552577 apport-gtk crashed with SIGSEGV in _gtk_style_provider_private_get_settings(provider=0x0) [gtkstyleproviderprivate.c:123] ** 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 apport in Ubuntu. https://bugs.launchpad.net/bugs/1751679 Title: apport-gtk crashed with SIGSEGV Status in apport package in Ubuntu: New Bug description: Crashed when opening snap package for VLC (this is running in a virtualbox vm) ProblemType: Crash DistroRelease: Ubuntu 18.04 Package: apport-gtk 2.20.8-0ubuntu10 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 CrashReports: 640:1000:118:6960656:2018-02-25 20:00:21.647302389 -0500:2018-02-25 20:00:22.647302389 -0500:/var/crash/_usr_share_apport_apport-gtk.1000.crash 640:1000:118:153988757:2018-02-25 20:00:15.559302330 -0500:2018-02-25 20:00:16.559302330 -0500:/var/crash/_usr_bin_compiz.1000.crash CurrentDesktop: Unity:Unity7:ubuntu Date: Sun Feb 25 20:00:18 2018 ExecutablePath: /usr/share/apport/apport-gtk InstallationDate: Installed on 2018-02-25 (0 days ago) InstallationMedia: Ubuntu 18.04.0 2018.02.02 amd64 "Bionic Beaver Unity-Desktop" InterpreterPath: /usr/bin/python3.6 PackageArchitecture: all ProcCmdline: /usr/bin/python3 /usr/share/apport/apport-gtk Python3Details: /usr/bin/python3.6, Python 3.6.4+, python3-minimal, 3.6.4-1 PythonDetails: /home/mark/Error: command ['which', 'python'] failed with exit code 1:, Error: [Errno 2] No such file or directory: "/home/mark/Error: command ['which', 'python'] failed with exit code 1:": "/home/mark/Error: command ['which', 'python'] failed with exit code 1:", unpackaged SegvAnalysis: Segfault happened at: 0x7f7f9aca4569:mov(%rbx),%rdi PC (0x7f7f9aca4569) ok source "(%rbx)" (0x) not located in a known VMA region (needed readable region)! destination "%rdi" ok SegvReason: reading NULL VMA Signal: 11 SourcePackage: apport StacktraceTop: ?? () from /usr/lib/x86_64-linux-gnu/libgtk-3.so.0 ?? () from /usr/lib/x86_64-linux-gnu/libgtk-3.so.0 ?? () from /usr/lib/x86_64-linux-gnu/libgtk-3.so.0 ?? () from /usr/lib/x86_64-linux-gnu/libgtk-3.so.0 ?? () from /usr/lib/x86_64-linux-gnu/libgtk-3.so.0 Title: apport-gtk crashed with SIGSEGV UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apport/+bug/1751679/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1579580] Re: ureadahead reports relative path errors in journalctl output
running 18.04. saw a massiv syslog file and running grep -i uread /var/log/syslog.1|grep -i "Feb 25 12" |wc -l: > 63197 i dont think we need this to make syslog extra big for no reason. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to ureadahead in Ubuntu. https://bugs.launchpad.net/bugs/1579580 Title: ureadahead reports relative path errors in journalctl output Status in ureadahead package in Ubuntu: Confirmed Bug description: ureadahead reports relative path errors in my journalctl output. This is currently 4368 lines of useless annoyances in my logs. To see if you have this problem, run: journalctl -b | grep ureadahead | grep relative | wc -l Thanks ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: ureadahead 0.100.0-19 ProcVersionSignature: Ubuntu 4.4.0-22.39-generic 4.4.8 Uname: Linux 4.4.0-22-generic x86_64 NonfreeKernelModules: zfs zunicode zcommon znvpair zavl ApportVersion: 2.20.1-0ubuntu2 Architecture: amd64 Date: Sun May 8 15:55:18 2016 InstallationDate: Installed on 2016-04-04 (34 days ago) InstallationMedia: Ubuntu-Server 16.04 LTS "Xenial Xerus" - Beta amd64 (20160325) ProcEnviron: TERM=linux PATH=(custom, no user) LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: ureadahead UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ureadahead/+bug/1579580/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1750937] Re: 4.4.0-116 Kernel update on 2/21 breaks Nvidia drivers (on 14.04 and 16.04)
The instructions provided by @cjjefcoat also fixed it for me. -- 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/1750937 Title: 4.4.0-116 Kernel update on 2/21 breaks Nvidia drivers (on 14.04 and 16.04) Status in linux package in Ubuntu: Confirmed Status in nvidia-graphics-drivers-384 package in Ubuntu: Confirmed Status in xorg package in Ubuntu: Confirmed Bug description: Running fine with nvidia-384 until this kernel update came along. When booted into the new kernel, got super low resolution and nvidia- settings was missing most of its functionality - could not change resolution. Rebooted into 4.4.0-112 kernel and all was well. The root cause of the problem has been found to be installing the -116 kernel without a sufficiently updated version of gcc. In my case, my system received the gcc update AFTER the kernel update. Uninstalling the -116 kernel and reinstalling it with the updated version of gcc solved the problem for me. ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: xorg 1:7.7+1ubuntu8.1 ProcVersionSignature: Ubuntu 4.4.0-112.135~14.04.1-generic 4.4.98 Uname: Linux 4.4.0-112-generic x86_64 NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia .proc.driver.nvidia.registry: Binary: "" .proc.driver.nvidia.version: NVRM version: NVIDIA UNIX x86_64 Kernel Module 384.111 Tue Dec 19 23:51:45 PST 2017 GCC version: gcc version 4.8.4 (Ubuntu 4.8.4-2ubuntu1~14.04.3) ApportVersion: 2.14.1-0ubuntu3.27 Architecture: amd64 CurrentDesktop: LXDE Date: Wed Feb 21 19:23:39 2018 DistUpgraded: Fresh install DistroCodename: trusty DistroVariant: ubuntu DkmsStatus: bbswitch, 0.7, 4.4.0-112-generic, x86_64: installed bbswitch, 0.7, 4.4.0-116-generic, x86_64: installed nvidia-384, 384.111, 4.4.0-112-generic, x86_64: installed nvidia-384, 384.111, 4.4.0-116-generic, x86_64: installed GraphicsCard: NVIDIA Corporation Device [10de:1c82] (rev a1) (prog-if 00 [VGA controller]) Subsystem: eVga.com. Corp. Device [3842:6253] InstallationDate: Installed on 2015-03-03 (1086 days ago) InstallationMedia: Ubuntu 14.04.2 LTS "Trusty Tahr" - Release amd64 (20150218.1) MachineType: ASUSTeK COMPUTER INC. M11AD ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-112-generic root=UUID=5a88d2a1-0a24-415b-adc2-28435b13248a ro quiet splash vt.handoff=7 SourcePackage: xorg Symptom: display UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 08/15/2013 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 0302 dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: M11AD dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: Rev X.0x dmi.chassis.asset.tag: Asset-1234567890 dmi.chassis.type: 3 dmi.chassis.vendor: Chassis Manufacture dmi.chassis.version: Chassis Version dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr0302:bd08/15/2013:svnASUSTeKCOMPUTERINC.:pnM11AD:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnM11AD:rvrRevX.0x:cvnChassisManufacture:ct3:cvrChassisVersion: dmi.product.name: M11AD dmi.product.version: System Version dmi.sys.vendor: ASUSTeK COMPUTER INC. version.compiz: compiz 1:0.9.11.3+14.04.20160425-0ubuntu1 version.ia32-libs: ia32-libs N/A version.libdrm2: libdrm2 2.4.67-1ubuntu0.14.04.2 version.libgl1-mesa-dri: libgl1-mesa-dri N/A version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A version.libgl1-mesa-glx: libgl1-mesa-glx N/A version.nvidia-graphics-drivers: nvidia-graphics-drivers N/A 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: Wed Feb 21 18:48:14 2018 xserver.configfile: default xserver.errors: xserver.logfile: /var/log/Xorg.0.log xserver.outputs: xserver.version: 2:1.18.3-1ubuntu2.3~trusty4 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1750937/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1751673] [NEW] nm-applet[3607]: gtk_widget_destroy: assertion 'GTK_IS_WIDGET (widget)' failed
Public bug reported: running 18.04 this message is spamming into syslog: > nm-applet[3607]: gtk_widget_destroy: assertion 'GTK_IS_WIDGET (widget)' failed ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: network-manager 1.8.4-1ubuntu4 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: Unity:Unity7:ubuntu Date: Mon Feb 26 01:16:49 2018 IfupdownConfig: # interfaces(5) file used by ifup(8) and ifdown(8) auto lo iface lo inet loopback InstallationDate: Installed on 2013-09-28 (1611 days ago) InstallationMedia: Ubuntu 13.10 "Saucy Salamander" - Beta amd64 (20130925.1) IpRoute: default via 192.168.1.1 dev wlan1 proto static metric 600 169.254.0.0/16 dev wlan1 scope link metric 1000 192.168.1.0/24 dev wlan1 proto kernel scope link src 192.168.1.34 metric 600 NetworkManager.state: [main] NetworkingEnabled=true WirelessEnabled=true WWANEnabled=false SourcePackage: network-manager UpgradeStatus: Upgraded to bionic on 2018-01-12 (44 days ago) modified.conffile..etc.polkit-1.localauthority.50-local.d.org.freedesktop.NetworkManager.pkla: [deleted] nmcli-dev: DEVICE TYPE STATE DBUS-PATH CONNECTION CON-UUID CON-PATH wlan1 wifi connected /org/freedesktop/NetworkManager/Devices/3 k2l 7df024b1-9b89-4f95-84c1-03188bb67f77 /org/freedesktop/NetworkManager/ActiveConnection/1 EC:88:92:02:17:7D btdisconnected /org/freedesktop/NetworkManager/Devices/4 -- -- -- eth1 ethernet unavailable /org/freedesktop/NetworkManager/Devices/2 -- -- -- lo loopback unmanaged /org/freedesktop/NetworkManager/Devices/1 -- -- -- nmcli-nm: RUNNING VERSION STATE STARTUP CONNECTIVITY NETWORKING WIFI-HW WIFI WWAN-HW WWAN running 1.8.4connected started full enabled enabled enabled enabled disabled ** Affects: network-manager (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug bionic -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to network-manager in Ubuntu. https://bugs.launchpad.net/bugs/1751673 Title: nm-applet[3607]: gtk_widget_destroy: assertion 'GTK_IS_WIDGET (widget)' failed Status in network-manager package in Ubuntu: New Bug description: running 18.04 this message is spamming into syslog: > nm-applet[3607]: gtk_widget_destroy: assertion 'GTK_IS_WIDGET (widget)' failed ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: network-manager 1.8.4-1ubuntu4 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: Unity:Unity7:ubuntu Date: Mon Feb 26 01:16:49 2018 IfupdownConfig: # interfaces(5) file used by ifup(8) and ifdown(8) auto lo iface lo inet loopback InstallationDate: Installed on 2013-09-28 (1611 days ago) InstallationMedia: Ubuntu 13.10 "Saucy Salamander" - Beta amd64 (20130925.1) IpRoute: default via 192.168.1.1 dev wlan1 proto static metric 600 169.254.0.0/16 dev wlan1 scope link metric 1000 192.168.1.0/24 dev wlan1 proto kernel scope link src 192.168.1.34 metric 600 NetworkManager.state: [main] NetworkingEnabled=true WirelessEnabled=true WWANEnabled=false SourcePackage: network-manager UpgradeStatus: Upgraded to bionic on 2018-01-12 (44 days ago) modified.conffile..etc.polkit-1.localauthority.50-local.d.org.freedesktop.NetworkManager.pkla: [deleted] nmcli-dev: DEVICE TYPE STATE DBUS-PATH CONNECTION CON-UUID CON-PATH wlan1 wifi connected /org/freedesktop/NetworkManager/Devices/3 k2l 7df024b1-9b89-4f95-84c1-03188bb67f77 /org/freedesktop/NetworkManager/ActiveConnection/1 EC:88:92:02:17:7D btdisconnected /org/freedesktop/NetworkManager/Devices/4 -- -- -- eth1 ethernet unavailable /org/freedesktop/NetworkManager/Devices/2 -- -- -- lo loopback unmanaged /org/freedesktop/NetworkManager/Devices/1 -- -- -- nmcli-nm: RUNNING VERSION STATE STARTUP CONNECTIVIT
[Touch-packages] [Bug 1715749] Re: Intermittent black screen on HP EliteBook 840 G1
And the screen just went black again. I haven’t rebooted since I changed the settings; I will report if I still experience issues after a reboot, just to be sure. -- 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/1715749 Title: Intermittent black screen on HP EliteBook 840 G1 Status in xorg package in Ubuntu: Incomplete Bug description: Once every couple hours, the internal laptop display goes black for a few seconds. This was reproducible: + With the laptop connected to a port replicator and the external display connected into the port replicator DP port via DP-DVI adapter. The external display remains on during this time. + With the laptop not connected into a port replicator but connected to an external display. The external display remains on during this time. + With the laptop not connected to either a port replicator or an external display. The hard disk was originally installed with Ubuntu MATE 14.10 in a HP EliteBook 6930p, upgraded to 15.04, 15.10 and eventually 16.04 and finally moved to the EliteBook 840 G1. The problem started immediately after the drive move. ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: xorg 1:7.7+13ubuntu3 ProcVersionSignature: Ubuntu 4.4.0-93.116-generic 4.4.79 Uname: Linux 4.4.0-93-generic x86_64 ApportVersion: 2.20.1-0ubuntu2.10 Architecture: amd64 CurrentDesktop: MATE Date: Fri Sep 8 00:53:24 2017 EcryptfsInUse: Yes InstallationDate: Installed on 2014-12-09 (1002 days ago) InstallationMedia: Ubuntu MATE 14.10 "Utopic Unicorn" - amd64 (20141023) SourcePackage: xorg UpgradeStatus: No upgrade log present (probably fresh install) --- ApportVersion: 2.20.1-0ubuntu2.15 Architecture: amd64 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: None CurrentDesktop: MATE DistUpgraded: Fresh install DistroCodename: xenial DistroRelease: Ubuntu 16.04 DistroVariant: ubuntu EcryptfsInUse: Yes ExtraDebuggingInterest: Yes, if not too technical GraphicsCard: Intel Corporation Haswell-ULT Integrated Graphics Controller [8086:0a16] (rev 0b) (prog-if 00 [VGA controller]) Subsystem: Hewlett-Packard Company Haswell-ULT Integrated Graphics Controller [103c:198f] InstallationDate: Installed on 2014-12-09 (1158 days ago) InstallationMedia: Ubuntu MATE 14.10 "Utopic Unicorn" - amd64 (20141023) MachineType: Hewlett-Packard HP EliteBook 840 G1 Package: xorg 1:7.7+13ubuntu3 PackageArchitecture: amd64 ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.4.0-112-generic root=/dev/mapper/ubuntu--vg-root ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 4.4.0-112.135-generic 4.4.98 Tags: xenial ubuntu Uname: Linux 4.4.0-112-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dialout dip lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 05/23/2016 dmi.bios.vendor: Hewlett-Packard dmi.bios.version: L71 Ver. 01.37 dmi.board.name: 198F dmi.board.vendor: Hewlett-Packard dmi.board.version: KBC Version 15.59 dmi.chassis.asset.tag: CNU407CM0V dmi.chassis.type: 10 dmi.chassis.vendor: Hewlett-Packard dmi.modalias: dmi:bvnHewlett-Packard:bvrL71Ver.01.37:bd05/23/2016:svnHewlett-Packard:pnHPEliteBook840G1:pvrA3009DD10203:rvnHewlett-Packard:rn198F:rvrKBCVersion15.59:cvnHewlett-Packard:ct10:cvr: dmi.product.name: HP EliteBook 840 G1 dmi.product.version: A3009DD10203 dmi.sys.vendor: Hewlett-Packard version.compiz: compiz 1:0.9.12.2+16.04.20160823-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.4-0ubuntu1~16.04.4 version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A version.libgl1-mesa-glx: libgl1-mesa-glx 17.2.4-0ubuntu1~16.04.4 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 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1715749/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1751666] Re: perl crashed with SIGABRT in _dbus_abort()
*** This bug is a duplicate of bug 1743216 *** https://bugs.launchpad.net/bugs/1743216 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 #1743216, 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/1751666/+attachment/5063006/+files/CoreDump.gz ** Attachment removed: "Disassembly.txt" https://bugs.launchpad.net/bugs/1751666/+attachment/5063008/+files/Disassembly.txt ** Attachment removed: "ProcMaps.txt" https://bugs.launchpad.net/bugs/1751666/+attachment/5063012/+files/ProcMaps.txt ** Attachment removed: "ProcStatus.txt" https://bugs.launchpad.net/bugs/1751666/+attachment/5063013/+files/ProcStatus.txt ** Attachment removed: "Registers.txt" https://bugs.launchpad.net/bugs/1751666/+attachment/5063014/+files/Registers.txt ** Attachment removed: "Stacktrace.txt" https://bugs.launchpad.net/bugs/1751666/+attachment/5063015/+files/Stacktrace.txt ** Attachment removed: "ThreadStacktrace.txt" https://bugs.launchpad.net/bugs/1751666/+attachment/5063016/+files/ThreadStacktrace.txt ** This bug has been marked a duplicate of private bug 1743216 ** 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 perl in Ubuntu. https://bugs.launchpad.net/bugs/1751666 Title: perl crashed with SIGABRT in _dbus_abort() Status in perl package in Ubuntu: New Bug description: Opened QT Creator Opened a already existing project It didn't list the files related to the project. I closed and opened QT Creator again, and went into the same project. It worked. Random crash window that didn't affect QT creator currently. ProblemType: Crash DistroRelease: Ubuntu 18.04 Package: perl-base 5.26.1-4build1 ProcVersionSignature: Ubuntu 4.13.0-32.35-generic 4.13.13 Uname: Linux 4.13.0-32-generic x86_64 ApportVersion: 2.20.8-0ubuntu8 Architecture: amd64 CurrentDesktop: Budgie:GNOME Date: Sun Feb 25 23:47:13 2018 ExecutablePath: /usr/bin/perl InstallationDate: Installed on 2018-02-22 (3 days ago) InstallationMedia: Ubuntu-Budgie 18.04 LTS "Bionic Beaver" - Alpha amd64 (20180212) ProcEnviron: LANGUAGE=en_US:en PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash Signal: 6 SourcePackage: perl StacktraceTop: _dbus_abort () from /lib/x86_64-linux-gnu/libdbus-1.so.3 _dbus_warn_check_failed () from /lib/x86_64-linux-gnu/libdbus-1.so.3 dbus_message_iter_append_basic () from /lib/x86_64-linux-gnu/libdbus-1.so.3 ?? () from /usr/lib/x86_64-linux-gnu/perl5/5.26/auto/Net/DBus/DBus.so Perl_pp_entersub () Title: perl crashed with SIGABRT in _dbus_abort() UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/perl/+bug/1751666/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1715749] Re: Intermittent black screen on HP EliteBook 840 G1
I just set the screen timeout to Never; dimming was already disabled. I did this only for the AC profile, not the battery profile, as I’m on AC power most of the time. I’ll report back if the screen goes black again (or if it doesn’t happen for a while). -- 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/1715749 Title: Intermittent black screen on HP EliteBook 840 G1 Status in xorg package in Ubuntu: Incomplete Bug description: Once every couple hours, the internal laptop display goes black for a few seconds. This was reproducible: + With the laptop connected to a port replicator and the external display connected into the port replicator DP port via DP-DVI adapter. The external display remains on during this time. + With the laptop not connected into a port replicator but connected to an external display. The external display remains on during this time. + With the laptop not connected to either a port replicator or an external display. The hard disk was originally installed with Ubuntu MATE 14.10 in a HP EliteBook 6930p, upgraded to 15.04, 15.10 and eventually 16.04 and finally moved to the EliteBook 840 G1. The problem started immediately after the drive move. ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: xorg 1:7.7+13ubuntu3 ProcVersionSignature: Ubuntu 4.4.0-93.116-generic 4.4.79 Uname: Linux 4.4.0-93-generic x86_64 ApportVersion: 2.20.1-0ubuntu2.10 Architecture: amd64 CurrentDesktop: MATE Date: Fri Sep 8 00:53:24 2017 EcryptfsInUse: Yes InstallationDate: Installed on 2014-12-09 (1002 days ago) InstallationMedia: Ubuntu MATE 14.10 "Utopic Unicorn" - amd64 (20141023) SourcePackage: xorg UpgradeStatus: No upgrade log present (probably fresh install) --- ApportVersion: 2.20.1-0ubuntu2.15 Architecture: amd64 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: None CurrentDesktop: MATE DistUpgraded: Fresh install DistroCodename: xenial DistroRelease: Ubuntu 16.04 DistroVariant: ubuntu EcryptfsInUse: Yes ExtraDebuggingInterest: Yes, if not too technical GraphicsCard: Intel Corporation Haswell-ULT Integrated Graphics Controller [8086:0a16] (rev 0b) (prog-if 00 [VGA controller]) Subsystem: Hewlett-Packard Company Haswell-ULT Integrated Graphics Controller [103c:198f] InstallationDate: Installed on 2014-12-09 (1158 days ago) InstallationMedia: Ubuntu MATE 14.10 "Utopic Unicorn" - amd64 (20141023) MachineType: Hewlett-Packard HP EliteBook 840 G1 Package: xorg 1:7.7+13ubuntu3 PackageArchitecture: amd64 ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.4.0-112-generic root=/dev/mapper/ubuntu--vg-root ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 4.4.0-112.135-generic 4.4.98 Tags: xenial ubuntu Uname: Linux 4.4.0-112-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dialout dip lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 05/23/2016 dmi.bios.vendor: Hewlett-Packard dmi.bios.version: L71 Ver. 01.37 dmi.board.name: 198F dmi.board.vendor: Hewlett-Packard dmi.board.version: KBC Version 15.59 dmi.chassis.asset.tag: CNU407CM0V dmi.chassis.type: 10 dmi.chassis.vendor: Hewlett-Packard dmi.modalias: dmi:bvnHewlett-Packard:bvrL71Ver.01.37:bd05/23/2016:svnHewlett-Packard:pnHPEliteBook840G1:pvrA3009DD10203:rvnHewlett-Packard:rn198F:rvrKBCVersion15.59:cvnHewlett-Packard:ct10:cvr: dmi.product.name: HP EliteBook 840 G1 dmi.product.version: A3009DD10203 dmi.sys.vendor: Hewlett-Packard version.compiz: compiz 1:0.9.12.2+16.04.20160823-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.4-0ubuntu1~16.04.4 version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A version.libgl1-mesa-glx: libgl1-mesa-glx 17.2.4-0ubuntu1~16.04.4 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 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1715749/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1688018] Re: DNS server from vpn connection is not being used after network-manager upgrade to 1.2.6
The script in #37 didn't work for me, as the interface name was "tun0". The following slightly modified script seems to work OK so far: # cat 99-openconnect-dnsmasq-bug #!/bin/bash set -e # force restart of dnsmasq on vpn connect # See https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1688018 echo "Running lame bug 1688018 workaround. Args: $*" if [[ "$1" =~ "tun0" ]] && [ $2 = "up" ] then if [ -e /var/run/NetworkManager/dnsmasq.pid ] then /bin/kill -15 $(cat /var/run/NetworkManager/dnsmasq.pid) fi fi -- 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/1688018 Title: DNS server from vpn connection is not being used after network-manager upgrade to 1.2.6 Status in network-manager package in Ubuntu: Triaged Status in network-manager source package in Xenial: In Progress Status in network-manager source package in Yakkety: Triaged Bug description: This was initially opened as #1671606 then later duped to #1639776. Discussion in #1639776 indicate that we need new bug for this so I am opening one ... Please don't mark this as duplicate to #1639776 or other similar bug report. We already lost several months and we are again at beginning ... TL;DR; -> network-manager-1.2.2-0ubuntu0.16.04.4 use DNS defined by VPN (correct). network-manager-1.2.6-0ubuntu0.16.04.1 use DNS from DHCP instead of one defined by VPN (wrong). DNS resolver should query only DNS servers defined by VPN while connection is active. = Test steps / result: - upgraded network-manager to 1.2.6-0ubuntu0.16.04.1 (dnsmasq-base-2.75-1ubuntu0.16.04.2) - restated my laptop to ensure clean start - connected to VPN using openconnect / network-manager-openconnect-gnome Observed results -> DNS queries are forwarded only to DNS servers defined by LAN connection (this is wrong / connection not working at all) - "killall dnsmasq" - dnsmasq get automatically restarted by system Observed results -> most of the the queries are forwarded to DNS servers defined by VPN, but lot of queries get forwarded to DNS servers defined by LAN connection (this is still wrong / DNS leaks, attacker can hijack connection even if VPN is enabled) - I downgraded back network-manager to 1.2.2-0ubuntu0.16.04.4 (dnsmasq-base stay same) - restated my laptop to ensure clean test - connected to same VPN using openconnect Observed results -> DNS queries are forwarded only to DNS servers defined by VPN connection. There are no leaks to LAN DNS server (this is correct behavior). = Paul Smith requested additional details in #1639776. Here are: * If you're using IPv4 vs. IPv6 -> IPv4 only. I have IPv6 set to ignore on all network definition (lan / wifi /vpn) * If you have checked or unchecked the "Use this connection only for resources on its network" -> unchecked on all nw definition * If you have this checked, try unchecking it and see if that makes a difference -> no change if I toggle this option. Behavior is same. * When you say "DNS lookups" please be clear about whether the hostnames being looked up are public (e.g., www.google.com or whatever), on your local LAN, or in the network accessed via the VPN. Does it make a difference which one you choose? -> No difference. * Are you using fully-qualified hostnames, or relying on the DNS domain search path? Does it make a difference if you do it differently? -> I normaly use FQDN due to nature of HTTPs cert validation. I don't see difference when I try same using hostname + domain search. = I am using openconnect (cisco) and openvpn. Test result are by using openconnect but I saw same behaviour also while using openvpn. = Thanks Lukas To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1688018/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1715749] Re: Intermittent black screen on HP EliteBook 840 G1
Michael von Glasow, if you disable the laptop turning the screen off or dimming after inactivity via the GUI, does this still happen? ** Description changed: - Once every few hours, the internal laptop display goes black for a few - seconds. The external display remains on during this time. + Once every couple hours, the internal laptop display goes black for a + few seconds. - This was reproducible with the laptop connected to a port replicator and - the external display connected into the port replicator DP port via DP- - DVI adapter, and with the laptop not connected into a port replicator - but connected to an external display. + This was reproducible: + + With the laptop connected to a port replicator and the external display connected into the port replicator DP port via DP-DVI adapter. The external display remains on during this time. + + With the laptop not connected into a port replicator but connected to an external display. The external display remains on during this time. + + With the laptop not connected to either a port replicator or an external display. The hard disk was originally installed with Ubuntu MATE 14.10 in a HP EliteBook 6930p, upgraded to 15.04, 15.10 and eventually 16.04 and finally moved to the EliteBook 840 G1. The problem started immediately after the drive move. ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: xorg 1:7.7+13ubuntu3 ProcVersionSignature: Ubuntu 4.4.0-93.116-generic 4.4.79 Uname: Linux 4.4.0-93-generic x86_64 ApportVersion: 2.20.1-0ubuntu2.10 Architecture: amd64 CurrentDesktop: MATE Date: Fri Sep 8 00:53:24 2017 EcryptfsInUse: Yes InstallationDate: Installed on 2014-12-09 (1002 days ago) InstallationMedia: Ubuntu MATE 14.10 "Utopic Unicorn" - amd64 (20141023) SourcePackage: xorg UpgradeStatus: No upgrade log present (probably fresh install) --- ApportVersion: 2.20.1-0ubuntu2.15 Architecture: amd64 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: None CurrentDesktop: MATE DistUpgraded: Fresh install DistroCodename: xenial DistroRelease: Ubuntu 16.04 DistroVariant: ubuntu EcryptfsInUse: Yes ExtraDebuggingInterest: Yes, if not too technical GraphicsCard: Intel Corporation Haswell-ULT Integrated Graphics Controller [8086:0a16] (rev 0b) (prog-if 00 [VGA controller]) Subsystem: Hewlett-Packard Company Haswell-ULT Integrated Graphics Controller [103c:198f] InstallationDate: Installed on 2014-12-09 (1158 days ago) InstallationMedia: Ubuntu MATE 14.10 "Utopic Unicorn" - amd64 (20141023) MachineType: Hewlett-Packard HP EliteBook 840 G1 Package: xorg 1:7.7+13ubuntu3 PackageArchitecture: amd64 ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.4.0-112-generic root=/dev/mapper/ubuntu--vg-root ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 4.4.0-112.135-generic 4.4.98 Tags: xenial ubuntu Uname: Linux 4.4.0-112-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dialout dip lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 05/23/2016 dmi.bios.vendor: Hewlett-Packard dmi.bios.version: L71 Ver. 01.37 dmi.board.name: 198F dmi.board.vendor: Hewlett-Packard dmi.board.version: KBC Version 15.59 dmi.chassis.asset.tag: CNU407CM0V dmi.chassis.type: 10 dmi.chassis.vendor: Hewlett-Packard dmi.modalias: dmi:bvnHewlett-Packard:bvrL71Ver.01.37:bd05/23/2016:svnHewlett-Packard:pnHPEliteBook840G1:pvrA3009DD10203:rvnHewlett-Packard:rn198F:rvrKBCVersion15.59:cvnHewlett-Packard:ct10:cvr: dmi.product.name: HP EliteBook 840 G1 dmi.product.version: A3009DD10203 dmi.sys.vendor: Hewlett-Packard version.compiz: compiz 1:0.9.12.2+16.04.20160823-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.4-0ubuntu1~16.04.4 version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A version.libgl1-mesa-glx: libgl1-mesa-glx 17.2.4-0ubuntu1~16.04.4 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 -- 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/1715749 Title: Intermittent black screen on HP EliteBook 840 G1 Status in xorg package in Ubuntu: Incomplete Bug description: Once every couple hours, the internal laptop display goes black for a few seconds. This was reproducible: + With the laptop connected to a port replicator and the external display connected into the port replicato
[Touch-packages] [Bug 1751657] [NEW] man journalctl gives info about -g option not present in command
Public bug reported: man journalctl documents a --grep option, however: $ journalctl -g a journalctl: invalid option -- 'g' $ journalctl --grep a Compiled without pattern matching support ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: systemd 237-3ubuntu3 ProcVersionSignature: Ubuntu 4.15.0-10.11-generic 4.15.3 Uname: Linux 4.15.0-10-generic x86_64 NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia ApportVersion: 2.20.8-0ubuntu10 Architecture: amd64 Date: Sun Feb 25 21:53:29 2018 InstallationDate: Installed on 2017-06-21 (248 days ago) InstallationMedia: Ubuntu 17.04 "Zesty Zapus" - Release amd64 (20170412) Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 002: ID 0cf3:e300 Atheros Communications, Inc. Bus 001 Device 003: ID 0c45:6713 Microdia Bus 001 Device 004: ID 10d7:1102 Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: Dell Inc. XPS 15 9560 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-10-generic.efi.signed root=UUID=18bdf6ee-e85b-4eb2-8fd1-68cf15fe1167 ro quiet splash acpi_rev_override=5 pci=noaer vt.handoff=1 SourcePackage: systemd UpgradeStatus: Upgraded to bionic on 2018-02-17 (8 days ago) dmi.bios.date: 12/15/2017 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.7.0 dmi.board.name: 05FFDN dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 10 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr1.7.0:bd12/15/2017:svnDellInc.:pnXPS159560:pvr:rvnDellInc.:rn05FFDN:rvrA00:cvnDellInc.:ct10:cvr: dmi.product.family: XPS dmi.product.name: XPS 15 9560 dmi.sys.vendor: Dell Inc. ** Affects: systemd (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug bionic -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to systemd in Ubuntu. https://bugs.launchpad.net/bugs/1751657 Title: man journalctl gives info about -g option not present in command Status in systemd package in Ubuntu: New Bug description: man journalctl documents a --grep option, however: $ journalctl -g a journalctl: invalid option -- 'g' $ journalctl --grep a Compiled without pattern matching support ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: systemd 237-3ubuntu3 ProcVersionSignature: Ubuntu 4.15.0-10.11-generic 4.15.3 Uname: Linux 4.15.0-10-generic x86_64 NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia ApportVersion: 2.20.8-0ubuntu10 Architecture: amd64 Date: Sun Feb 25 21:53:29 2018 InstallationDate: Installed on 2017-06-21 (248 days ago) InstallationMedia: Ubuntu 17.04 "Zesty Zapus" - Release amd64 (20170412) Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 002: ID 0cf3:e300 Atheros Communications, Inc. Bus 001 Device 003: ID 0c45:6713 Microdia Bus 001 Device 004: ID 10d7:1102 Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: Dell Inc. XPS 15 9560 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-10-generic.efi.signed root=UUID=18bdf6ee-e85b-4eb2-8fd1-68cf15fe1167 ro quiet splash acpi_rev_override=5 pci=noaer vt.handoff=1 SourcePackage: systemd UpgradeStatus: Upgraded to bionic on 2018-02-17 (8 days ago) dmi.bios.date: 12/15/2017 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.7.0 dmi.board.name: 05FFDN dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 10 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr1.7.0:bd12/15/2017:svnDellInc.:pnXPS159560:pvr:rvnDellInc.:rn05FFDN:rvrA00:cvnDellInc.:ct10:cvr: dmi.product.family: XPS dmi.product.name: XPS 15 9560 dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1751657/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1751653] [NEW] Minecraft makes Ubuntu GNOME extremely slow
Public bug reported: Hi! I've had Ubuntu 16 with Unity on my children's older computer and Minecraft (downloaded and installed from Software Center) worked just fine. I then did a clean install to Ubuntu 17 with GNOME and downloaded and installed Minecraft in the same way, but when the final Minecraft playwindow pops up Ubuntu is really slow and hardly respond. After I installed Unity and run it instead of GNOME, everything worked great again. Maybe Java OpenJDK doesn't work well with GNOME? Is this something you can fix? I would prefer to run the preinstalled GNOME instead of Unity, especially since GNOME is the choice for Ubuntu from now on, and I'm planning on upgrading to the upcoming version 18 of Ubuntu. Thank you for a nice operating system otherwise. Best regards, Ken Karlsson ProblemType: Bug DistroRelease: Ubuntu 17.10 Package: xorg 1:7.7+19ubuntu3 ProcVersionSignature: Ubuntu 4.13.0-36.40-generic 4.13.13 Uname: Linux 4.13.0-36-generic x86_64 .tmp.unity_support_test.0: ApportVersion: 2.20.7-0ubuntu3.7 Architecture: amd64 CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Sun Feb 25 21:29:43 2018 DistUpgraded: Fresh install DistroCodename: artful DistroVariant: ubuntu ExtraDebuggingInterest: Yes GraphicsCard: Advanced Micro Devices, Inc. [AMD/ATI] RS880M [Mobility Radeon HD 4225/4250] [1002:9712] (prog-if 00 [VGA controller]) Subsystem: Hewlett-Packard Company RS880M [Mobility Radeon HD 4225/4250] [103c:148b] InstallationDate: Installed on 2018-02-24 (1 days ago) InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20180105.1) MachineType: Hewlett-Packard HP Pavilion dm1 Notebook PC ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.13.0-36-generic root=UUID=b6ec7597-5a12-45d5-910b-2fb46d3cfd23 ro quiet splash vt.handoff=7 SourcePackage: xorg Symptom: display UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 09/15/2010 dmi.bios.vendor: Hewlett-Packard dmi.bios.version: F.15 dmi.board.asset.tag: Base Board Asset Tag dmi.board.name: 148B dmi.board.vendor: Hewlett-Packard dmi.board.version: 80.14 dmi.chassis.type: 10 dmi.chassis.vendor: Hewlett-Packard dmi.chassis.version: N/A dmi.modalias: dmi:bvnHewlett-Packard:bvrF.15:bd09/15/2010:svnHewlett-Packard:pnHPPaviliondm1NotebookPC:pvr049B102432032:rvnHewlett-Packard:rn148B:rvr80.14:cvnHewlett-Packard:ct10:cvrN/A: dmi.product.family: 103C_5335KV dmi.product.name: HP Pavilion dm1 Notebook PC dmi.product.version: 049B102432032 dmi.sys.vendor: Hewlett-Packard 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 N/A 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 ** Affects: xorg (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug artful performance ubuntu wayland-session -- 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/1751653 Title: Minecraft makes Ubuntu GNOME extremely slow Status in xorg package in Ubuntu: New Bug description: Hi! I've had Ubuntu 16 with Unity on my children's older computer and Minecraft (downloaded and installed from Software Center) worked just fine. I then did a clean install to Ubuntu 17 with GNOME and downloaded and installed Minecraft in the same way, but when the final Minecraft playwindow pops up Ubuntu is really slow and hardly respond. After I installed Unity and run it instead of GNOME, everything worked great again. Maybe Java OpenJDK doesn't work well with GNOME? Is this something you can fix? I would prefer to run the preinstalled GNOME instead of Unity, especially since GNOME is the choice for Ubuntu from now on, and I'm planning on upgrading to the upcoming version 18 of Ubuntu. Thank you for a nice operating system otherwise. Best regards, Ken Karlsson ProblemType: Bug DistroRelease: Ubuntu 17.10 Package: xorg 1:7.7+19ubuntu3 ProcVersionSignature: Ubuntu 4.13.0-36.40-generic 4.13.13 Uname: Linux 4.13.0-36-generic x86_64 .tmp.unity_support_test.0: ApportVersion: 2.20.7-0ubuntu3.7 Architecture: amd64 CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Sun Feb 25 21:29:43 2018 DistUpgraded: Fresh install DistroCodename: artful DistroVariant: ubuntu ExtraDebuggingInterest: Yes GraphicsCard: Advanced Micro Devices, Inc. [AMD/ATI] RS880M [Mobility Radeon HD 4225/4250] [1002:9712] (prog-if 00 [VGA controller]) Subsystem: Hewlett-Packard Company
[Touch-packages] [Bug 1751644] Re: package dbus 1.12.2-1ubuntu1 failed to install/upgrade: triggers looping, abandoned
** Tags removed: need-duplicate-check -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to dbus in Ubuntu. https://bugs.launchpad.net/bugs/1751644 Title: package dbus 1.12.2-1ubuntu1 failed to install/upgrade: triggers looping, abandoned Status in dbus package in Ubuntu: New Bug description: Ubuntu 18.04 (beta) package dbus 1.12.2-1 ProblemType: Package DistroRelease: Ubuntu 18.04 Package: dbus 1.12.2-1ubuntu1 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 Date: Sun Feb 25 04:24:01 2018 ErrorMessage: triggers looping, abandoned InstallationDate: Installed on 2018-02-19 (6 days ago) InstallationMedia: Xubuntu 17.10 "Artful Aardvark" - Release amd64 (20180105) Python3Details: /usr/bin/python3.6, Python 3.6.4+, python3-minimal, 3.6.4-1 PythonDetails: /usr/bin/python2.7, Python 2.7.14+, python-minimal, 2.7.14-4 RelatedPackageVersions: dpkg 1.19.0.5ubuntu1 apt 1.6~alpha7ubuntu2 SourcePackage: dbus Title: package dbus 1.12.2-1ubuntu1 failed to install/upgrade: triggers looping, abandoned UpgradeStatus: Upgraded to bionic on 2018-02-25 (0 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/dbus/+bug/1751644/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1751644] [NEW] package dbus 1.12.2-1ubuntu1 failed to install/upgrade: triggers looping, abandoned
Public bug reported: Ubuntu 18.04 (beta) package dbus 1.12.2-1 ProblemType: Package DistroRelease: Ubuntu 18.04 Package: dbus 1.12.2-1ubuntu1 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 Date: Sun Feb 25 04:24:01 2018 ErrorMessage: triggers looping, abandoned InstallationDate: Installed on 2018-02-19 (6 days ago) InstallationMedia: Xubuntu 17.10 "Artful Aardvark" - Release amd64 (20180105) Python3Details: /usr/bin/python3.6, Python 3.6.4+, python3-minimal, 3.6.4-1 PythonDetails: /usr/bin/python2.7, Python 2.7.14+, python-minimal, 2.7.14-4 RelatedPackageVersions: dpkg 1.19.0.5ubuntu1 apt 1.6~alpha7ubuntu2 SourcePackage: dbus Title: package dbus 1.12.2-1ubuntu1 failed to install/upgrade: triggers looping, abandoned UpgradeStatus: Upgraded to bionic on 2018-02-25 (0 days ago) ** Affects: dbus (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 dbus in Ubuntu. https://bugs.launchpad.net/bugs/1751644 Title: package dbus 1.12.2-1ubuntu1 failed to install/upgrade: triggers looping, abandoned Status in dbus package in Ubuntu: New Bug description: Ubuntu 18.04 (beta) package dbus 1.12.2-1 ProblemType: Package DistroRelease: Ubuntu 18.04 Package: dbus 1.12.2-1ubuntu1 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 Date: Sun Feb 25 04:24:01 2018 ErrorMessage: triggers looping, abandoned InstallationDate: Installed on 2018-02-19 (6 days ago) InstallationMedia: Xubuntu 17.10 "Artful Aardvark" - Release amd64 (20180105) Python3Details: /usr/bin/python3.6, Python 3.6.4+, python3-minimal, 3.6.4-1 PythonDetails: /usr/bin/python2.7, Python 2.7.14+, python-minimal, 2.7.14-4 RelatedPackageVersions: dpkg 1.19.0.5ubuntu1 apt 1.6~alpha7ubuntu2 SourcePackage: dbus Title: package dbus 1.12.2-1ubuntu1 failed to install/upgrade: triggers looping, abandoned UpgradeStatus: Upgraded to bionic on 2018-02-25 (0 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/dbus/+bug/1751644/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1650036] Re: Some mkv files report error
That version is now dead http://news.softpedia.com/news/ubuntu-17-04-zesty-zapus-has-reached-end-of-life-upgrade-to-ubuntu-17-10-now-519360.shtml ** Changed in: gstreamer1.0 (Ubuntu) Status: New => Invalid -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to gstreamer1.0 in Ubuntu. https://bugs.launchpad.net/bugs/1650036 Title: Some mkv files report error Status in gstreamer1.0 package in Ubuntu: Invalid Bug description: Playing some video files - especially mkv files sees totem report Internal Data Stream error Grabbed http://trailers.divx.com/divx_prod/profiles/WiegelesHeliSki_DivXPlus_19Mbps.mkv to test. running totem from terminal gets: totem (totem:12124): Gtk-WARNING **: Failed to get the GNOME session proxy: The name org.gnome.SessionManager is not owned (totem:12124): Gtk-WARNING **: Calling org.xfce.Session.Manager.Inhibit failed: GDBus.Error:org.freedesktop.DBus.Error.UnknownMethod: Method "Inhibit" with signature "susu" on interface "org.xfce.Session.Manager" doesn't exist (totem:12124): Totem-WARNING **: Failed to reset the playback rate to 1.0 (totem:12124): GLib-GObject-WARNING **: invalid (NULL) pointer instance (totem:12124): GLib-GObject-CRITICAL **: g_signal_handlers_disconnect_matched: assertion 'G_TYPE_CHECK_INSTANCE (instance)' failed (totem:12124): GLib-GObject-WARNING **: invalid (NULL) pointer instance (totem:12124): GLib-GObject-CRITICAL **: g_signal_handlers_disconnect_matched: assertion 'G_TYPE_CHECK_INSTANCE (instance)' failed (totem:12124): GLib-GObject-WARNING **: invalid (NULL) pointer instance (totem:12124): GLib-GObject-CRITICAL **: g_signal_handlers_disconnect_matched: assertion 'G_TYPE_CHECK_INSTANCE (instance)' failed (totem:12124): Totem-CRITICAL **: totem_object_empty_menu_section: assertion 'TOTEM_IS_OBJECT (totem)' failed ProblemType: Bug DistroRelease: Ubuntu 17.04 Package: libgstreamer1.0-0 1.10.2-1 ProcVersionSignature: Ubuntu 4.9.0-10.11-generic 4.9.0-rc8 Uname: Linux 4.9.0-10-generic x86_64 ApportVersion: 2.20.3-0ubuntu8 Architecture: amd64 CurrentDesktop: XFCE Date: Wed Dec 14 21:57:45 2016 InstallationDate: Installed on 2016-06-11 (186 days ago) InstallationMedia: Xubuntu 16.10 "Yakkety Yak" - Alpha amd64 (20160611) SourcePackage: gstreamer1.0 UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gstreamer1.0/+bug/1650036/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1650794] Re: Ubuntu server 17.04 fails dns on first boot
That version is now dead http://news.softpedia.com/news/ubuntu-17-04-zesty-zapus-has-reached-end-of-life-upgrade-to-ubuntu-17-10-now-519360.shtml ** Changed in: ubuntu-meta (Ubuntu) Status: Confirmed => Invalid -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to ubuntu-meta in Ubuntu. https://bugs.launchpad.net/bugs/1650794 Title: Ubuntu server 17.04 fails dns on first boot Status in ubuntu-meta package in Ubuntu: Invalid Bug description: apt-get update fails after first boot when network interface is managed by ifup On a fresh install apt-get update fails: apt-get update … Could not resolve 'us.archive.ubuntu.com' ping also fails: ping -c1 -W1 us.archive.ubuntu.com ping: us.archive.ubuntu.com: Name or service not known but dig works: dig us.archive.ubuntu.com a +short 91.189.91.23 GETAROUND: - after each dhcp, do ifdown-ifup: sudo ifdown ens3; sudo ifup ens3 ProblemType: Bug DistroRelease: Ubuntu 17.04 Package: ubuntu-server 1.375 ProcVersionSignature: Ubuntu 4.8.0-30.32-generic 4.8.6 Uname: Linux 4.8.0-30-generic x86_64 ApportVersion: 2.20.4-0ubuntu1 Architecture: amd64 Date: Sat Dec 17 11:28:41 2016 InstallationDate: Installed on 2016-12-17 (0 days ago) InstallationMedia: Ubuntu-Server 17.04 "Zesty Zapus" - Alpha amd64 (20161217) ProcEnviron: TERM=screen PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: ubuntu-meta UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubuntu-meta/+bug/1650794/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1650927] Re: accessing local ethernet is possible, accessing internet is not possible (Ubuntu MATE 17.04, ppc)
That version is now dead http://news.softpedia.com/news/ubuntu-17-04-zesty-zapus-has-reached-end-of-life-upgrade-to-ubuntu-17-10-now-519360.shtml ** Changed in: network-manager (Ubuntu) Status: Confirmed => Invalid -- 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/1650927 Title: accessing local ethernet is possible, accessing internet is not possible (Ubuntu MATE 17.04, ppc) Status in network-manager package in Ubuntu: Invalid Bug description: Access to local ethernet is possible (e.g. ping 192.168.2.2), access to internet is not possible: ping: ports.ubuntu.com: Name or service not known ping: www.google.com: Name or service not known It does not matter if my PowerBook G4 is connected via WLAN or ethernet, the effect is the same. ProblemType: Bug DistroRelease: Ubuntu 17.04 Package: network-manager 1.4.2-2ubuntu4 ProcVersionSignature: Ubuntu 4.9.0-11.12-powerpc-smp 4.9.0 Uname: Linux 4.9.0-11-powerpc-smp ppc ApportVersion: 2.20.4-0ubuntu1 Architecture: powerpc CasperVersion: 1.379 Date: Thu Nov 3 18:13:07 2016 IfupdownConfig: # interfaces(5) file used by ifup(8) and ifdown(8) auto lo iface lo inet loopback IpRoute: default via 192.168.3.1 dev wlP1p17s0 proto static metric 600 169.254.0.0/16 dev wlP1p17s0 scope link metric 1000 192.168.3.0/24 dev wlP1p17s0 proto kernel scope link src 192.168.3.2 metric 600 LiveMediaBuild: Ubuntu-MATE 17.04 "Zesty Zapus" - Alpha powerpc (20161218) NetworkManager.conf: [main] plugins=ifupdown,keyfile [ifupdown] managed=false NetworkManager.state: [main] NetworkingEnabled=true WirelessEnabled=true WWANEnabled=true ProcEnviron: LANG=en_US.UTF-8 SHELL=/bin/bash TERM=xterm PATH=(custom, no user) SourcePackage: network-manager UpgradeStatus: No upgrade log present (probably fresh install) nmcli-con: NAMEUUID TYPE TIMESTAMP TIMESTAMP-REAL AUTOCONNECT AUTOCONNECT-PRIORITY READONLY DBUS-PATH ACTIVE DEVICE STATE ACTIVE-PATH Carcosa 82f9a6ba-8a34-4aa8-8bba-6520f8b73c62 802-11-wireless 1478196808 Thu 03 Nov 2016 06:13:28 PM UTC yes 0 no/org/freedesktop/NetworkManager/Settings/1 yes wlP1p17s0 activated /org/freedesktop/NetworkManager/ActiveConnection/4 Wired connection 1 1a0d2e10-42f2-3154-b4f6-dfbec067bff3 802-3-ethernet 1478196172 Thu 03 Nov 2016 06:02:52 PM UTC yes 4294966297 no/org/freedesktop/NetworkManager/Settings/0 no -- -- -- nmcli-dev: DEVICETYPE STATEDBUS-PATH CONNECTION CON-UUID CON-PATH wlP1p17s0 wifi connected /org/freedesktop/NetworkManager/Devices/2 Carcosa 82f9a6ba-8a34-4aa8-8bba-6520f8b73c62 /org/freedesktop/NetworkManager/ActiveConnection/4 enP2p36s15f0 ethernet unavailable /org/freedesktop/NetworkManager/Devices/1 -- -- -- loloopback unmanaged /org/freedesktop/NetworkManager/Devices/0 -- -- -- nmcli-nm: RUNNING VERSION STATE STARTUP CONNECTIVITY NETWORKING WIFI-HW WIFI WWAN-HW WWAN running 1.4.2connected started full enabled enabled enabled enabled enabled To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1650927/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1650961] Re: ERROR:connection_factory_impl.cc(367)] Failed to connect to MCS endpoint with error -106
That version is now dead http://news.softpedia.com/news/ubuntu-17-04-zesty-zapus-has-reached-end-of-life-upgrade-to-ubuntu-17-10-now-519360.shtml ** Changed in: apport (Ubuntu) Status: Confirmed => Invalid -- 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/1650961 Title: ERROR:connection_factory_impl.cc(367)] Failed to connect to MCS endpoint with error -106 Status in apport package in Ubuntu: Invalid Bug description: caravena@caravena-530U3C-530U4C:~$ ubuntu-bug linux caravena@caravena-530U3C-530U4C:~$ [12375:12409:1218/134054:ERROR:nss_util.cc(809)] After loading Root Certs, loaded==false: NSS error code: -8018 Se creó una nueva ventana en la sesión existente del navegador. [7185:7220:1218/142107:ERROR:connection_factory_impl.cc(367)] Failed to connect to MCS endpoint with error -106 [7185:7318:1218/142111:ERROR:get_updates_processor.cc(242)] PostClientToServerMessage() failed during GetUpdates [7185:7318:1218/142115:ERROR:get_updates_processor.cc(242)] PostClientToServerMessage() failed during GetUpdates [7185:7220:1218/142117:ERROR:connection_factory_impl.cc(367)] Failed to connect to MCS endpoint with error -105 [7185:7220:1218/143613:ERROR:connection_factory_impl.cc(367)] Failed to connect to MCS endpoint with error -106 [7185:7318:1218/144540:ERROR:get_updates_processor.cc(242)] PostClientToServerMessage() failed during GetUpdates [7185:7220:1218/145430:ERROR:connection_factory_impl.cc(367)] Failed to connect to MCS endpoint with error -106 [7185:7318:1218/162533:ERROR:get_updates_processor.cc(242)] PostClientToServerMessage() failed during GetUpdates [7185:7220:1218/162540:ERROR:connection_factory_impl.cc(367)] Failed to connect to MCS endpoint with error -21 [7185:7318:1218/162540:ERROR:get_updates_processor.cc(242)] PostClientToServerMessage() failed during GetUpdates caravena@caravena-530U3C-530U4C:~$ ubuntu-bug linux caravena@caravena-530U3C-530U4C:~$ [18327:18362:1218/165822:ERROR:nss_util.cc(809)] After loading Root Certs, loaded==false: NSS error code: -8018 ProblemType: Bug DistroRelease: Ubuntu 17.04 Package: apport 2.20.4-0ubuntu1 ProcVersionSignature: Ubuntu 4.9.0-11.12-generic 4.9.0 Uname: Linux 4.9.0-11-generic x86_64 ApportVersion: 2.20.4-0ubuntu1 Architecture: amd64 CurrentDesktop: GNOME Date: Sun Dec 18 17:32:53 2016 InstallationDate: Installed on 2015-07-26 (511 days ago) InstallationMedia: Ubuntu-GNOME 15.10 "Wily Werewolf" - Alpha amd64 (20150723) PackageArchitecture: all SourcePackage: apport UpgradeStatus: Upgraded to zesty on 2016-10-29 (50 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apport/+bug/1650961/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1654490] Re: gdm3 won't work on 17.04
That version is now dead http://news.softpedia.com/news/ubuntu-17-04-zesty-zapus-has-reached-end-of-life-upgrade-to-ubuntu-17-10-now-519360.shtml ** Changed in: xorg (Ubuntu) Status: Confirmed => Invalid -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to xorg in Ubuntu. https://bugs.launchpad.net/bugs/1654490 Title: gdm3 won't work on 17.04 Status in xorg package in Ubuntu: Invalid Bug description: I am not able to log into the display manager using gdm3 and UbuntuGNOME 17.04. I had to install lightdm reconfigure it with dpkg- reconfigure gdm3 and do it again after getting the message that I need to --configure it, which resolved in an error. than I had to sudo service lightdm start and was able to login. weston also won't let me log in. I am using an Nvidia 1050TI which I changed when running this system. Before using the 1050TI I was using a GT210. The Error appeared after changing the cards I think. I am using the 375.26 driver from http://ppa.launchpad.net/graphics-drivers/ppa/ubuntu ProblemType: Bug DistroRelease: Ubuntu 17.04 Package: xorg 1:7.7+16ubuntu2 ProcVersionSignature: Ubuntu 4.9.0-11.12-generic 4.9.0 Uname: Linux 4.9.0-11-generic x86_64 NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia .proc.driver.nvidia.gpus..01.00.0: Error: [Errno 21] Ist ein Verzeichnis: '/proc/driver/nvidia/gpus/:01:00.0' .proc.driver.nvidia.registry: Binary: "" .proc.driver.nvidia.version: NVRM version: NVIDIA UNIX x86_64 Kernel Module 375.26 Thu Dec 8 18:36:43 PST 2016 GCC version: gcc version 6.3.0 20161229 (Ubuntu 6.3.0-2ubuntu1) .proc.driver.nvidia.warnings.fbdev: Your system is not currently configured to drive a VGA console on the primary VGA device. The NVIDIA Linux graphics driver requires the use of a text-mode VGA console. Use of other console drivers including, but not limited to, vesafb, may result in corruption and stability problems, and is not supported. .tmp.unity_support_test.0: ApportVersion: 2.20.4-0ubuntu1 Architecture: amd64 BootLog: CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: None Date: Fri Jan 6 06:40:13 2017 DistUpgraded: Fresh install DistroCodename: zesty DistroVariant: ubuntu DkmsStatus: bbswitch, 0.8, 4.9.0-11-generic, x86_64: installed nvidia-375, 375.26, 4.9.0-11-generic, x86_64: installed GraphicsCard: NVIDIA Corporation GP107 [GeForce GTX 1050 Ti] [10de:1c82] (rev a1) (prog-if 00 [VGA controller]) Subsystem: Gigabyte Technology Co., Ltd GP107 [GeForce GTX 1050 Ti] [1458:3729] InstallationDate: Installed on 2016-10-15 (82 days ago) InstallationMedia: Ubuntu-GNOME 16.10 "Yakkety Yak" - Release amd64 (20161012.1) MachineType: System manufacturer System Product Name ProcEnviron: LANGUAGE=de_DE PATH=(custom, no user) LANG=de_DE.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.9.0-11-generic root=UUID=f22a5adb-6406-46d2-98b5-7a3db6e8d489 ro quiet splash vt.handoff=7 SourcePackage: xorg UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 03/17/2014 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 1307 dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: P8H77-V LE dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: Rev X.0x dmi.chassis.asset.tag: Asset-1234567890 dmi.chassis.type: 3 dmi.chassis.vendor: Chassis Manufacture dmi.chassis.version: Chassis Version dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr1307:bd03/17/2014:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnP8H77-VLE:rvrRevX.0x:cvnChassisManufacture:ct3:cvrChassisVersion: dmi.product.name: System Product Name dmi.product.version: System Version dmi.sys.vendor: System manufacturer version.compiz: compiz 1:0.9.13.1+17.04.20161114.1-0ubuntu1 version.ia32-libs: ia32-libs N/A version.libdrm2: libdrm2 2.4.74-1 version.libgl1-mesa-dri: libgl1-mesa-dri 13.0.2-1ubuntu1 version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A version.libgl1-mesa-glx: libgl1-mesa-glx 13.0.2-1ubuntu1 version.nvidia-graphics-drivers: nvidia-graphics-drivers-* N/A version.xserver-xorg-core: xserver-xorg-core 2:1.18.4-1ubuntu9 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.10.2-1ubuntu1 version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.8.0-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20160706-1ubuntu1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.13-1 xserver.bootTime: Fri Jan 6 06:36:36 2017 xserver.configfile: default xserver.errors: xserver.logfile: /var/log/Xorg.0.log xserver.outputs: xserver.version: 2:1.18.4-1ubuntu9 To manage notifications about this bug go to: https://bugs.la
[Touch-packages] [Bug 1654563] Re: OSK jumping up and down on click/touch
That version is now dead http://news.softpedia.com/news/ubuntu-17-04-zesty-zapus-has-reached-end-of-life-upgrade-to-ubuntu-17-10-now-519360.shtml ** Changed in: ubuntu-keyboard (Ubuntu) Status: New => Invalid -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to ubuntu-keyboard in Ubuntu. https://bugs.launchpad.net/bugs/1654563 Title: OSK jumping up and down on click/touch Status in ubuntu-keyboard package in Ubuntu: Invalid Bug description: After having forced the OSK to show on a zesty desktop (http://paste.ubuntu.com/23752185/) I found it jumping up and down on input events. ProblemType: Bug DistroRelease: Ubuntu 17.04 Package: ubuntu-keyboard 0.100+17.04.20161223-0ubuntu1 ProcVersionSignature: Ubuntu 4.9.0-11.12-generic 4.9.0 Uname: Linux 4.9.0-11-generic x86_64 NonfreeKernelModules: zfs zunicode zavl zcommon znvpair ApportVersion: 2.20.4-0ubuntu1 Architecture: amd64 CurrentDesktop: Unity Date: Fri Jan 6 14:51:55 2017 InstallationDate: Installed on 2016-05-06 (244 days ago) InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 (20160420.1) SourcePackage: ubuntu-keyboard UpgradeStatus: Upgraded to zesty on 2016-11-22 (45 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubuntu-keyboard/+bug/1654563/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1655263] Re: package fonts-arphic-ukai (not installed) failed to install/upgrade: subprocess installed post-removal script returned error exit status 12
That version is now dead http://news.softpedia.com/news/ubuntu-17-04-zesty-zapus-has-reached-end-of-life-upgrade-to-ubuntu-17-10-now-519360.shtml ** Changed in: fonts-arphic-ukai (Ubuntu) Status: New => Invalid -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to fonts-arphic-ukai in Ubuntu. https://bugs.launchpad.net/bugs/1655263 Title: package fonts-arphic-ukai (not installed) failed to install/upgrade: subprocess installed post-removal script returned error exit status 12 Status in fonts-arphic-ukai package in Ubuntu: Invalid Bug description: whenever i start my pc always showing this window ProblemType: Package DistroRelease: Ubuntu 17.04 Package: fonts-arphic-ukai (not installed) ProcVersionSignature: Ubuntu 4.9.0-11.12-generic 4.9.0 Uname: Linux 4.9.0-11-generic x86_64 ApportVersion: 2.20.4-0ubuntu1 Architecture: amd64 Date: Mon Jan 9 18:12:23 2017 DuplicateSignature: package:fonts-arphic-ukai:(not installed) Removing fonts-arphic-ukai (0.2.20080216.2-4ubuntu2) ... open2: fork failed: Cannot allocate memory at /usr/share/perl5/Debconf/ConfModule.pm line 59. dpkg: error processing package fonts-arphic-ukai (--remove): subprocess installed post-removal script returned error exit status 12 ErrorMessage: subprocess installed post-removal script returned error exit status 12 RelatedPackageVersions: dpkg 1.18.10ubuntu1 apt 1.4~beta3 SourcePackage: fonts-arphic-ukai Title: package fonts-arphic-ukai (not installed) failed to install/upgrade: subprocess installed post-removal script returned error exit status 12 UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/fonts-arphic-ukai/+bug/1655263/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1655631] Re: Internal Microphone works on 16.04, but not on ZZ
That version is now dead http://news.softpedia.com/news/ubuntu-17-04-zesty-zapus-has-reached-end-of-life-upgrade-to-ubuntu-17-10-now-519360.shtml ** Changed in: alsa-driver (Ubuntu) Status: New => Invalid -- 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/1655631 Title: Internal Microphone works on 16.04, but not on ZZ Status in alsa-driver package in Ubuntu: Invalid Bug description: My microphone (built in, or using the plug-in jack) works just fine in 16.04 with the Kubuntu backports PPA, but not in ZZ. This is in two partitions on the same laptop. I think System Settings multimedia looks the same in both 16.04 and ZZ. Since it is the same piece of HW, and with the backports, I assume the app layer is almost identical between 16.04 and ZZ, I wonder if it is lower down in the stack. On 16.04, uname -a: Linux mparillo-HP-EliteBook-8440p 4.4.0-57-generic #78-Ubuntu SMP On ZZ, uname -a: Linux mparillo-HP-EliteBook-8440p 4.9.0-11-generic #12-Ubuntu SMP lspci: 00:1b.0 Audio device: Intel Corporation 5 Series/3400 Series Chipset High Definition Audio (rev 05) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1655631/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1656100] Re: Unable to remove signing keys using gnome-software-properties
That version is now dead http://news.softpedia.com/news/ubuntu-17-04-zesty-zapus-has-reached-end-of-life-upgrade-to-ubuntu-17-10-now-519360.shtml ** Changed in: software-properties (Ubuntu) Status: Confirmed => Invalid ** Changed in: ubuntu-gnome Status: New => Invalid -- 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/1656100 Title: Unable to remove signing keys using gnome-software-properties Status in Ubuntu GNOME: Invalid Status in software-properties package in Ubuntu: Invalid Bug description: I have found that on Ubuntu GNOME 16.10 with GNOME 3.22 that I am unable to remove signing keys in the Authentication tab. If I select a key I wish to remove and click the Remove button, either nothing will happen, or it will ask me for authentication, upon giving it the correct password all that will happen is it will deselect the key I select, but at no point will it actually remove it, which is rather annoying. ProblemType: Bug DistroRelease: Ubuntu 16.10 Package: software-properties-gtk 0.96.24.7 ProcVersionSignature: Ubuntu 4.8.0-34.36-generic 4.8.11 Uname: Linux 4.8.0-34-generic x86_64 ApportVersion: 2.20.3-0ubuntu8.2 Architecture: amd64 CurrentDesktop: GNOME Date: Thu Jan 12 21:35:55 2017 InstallationDate: Installed on 2017-01-09 (3 days ago) InstallationMedia: Ubuntu-GNOME 16.10 "Yakkety Yak" - Release amd64 (20161012.1) PackageArchitecture: all SourcePackage: software-properties UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-gnome/+bug/1656100/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1750937] Re: 4.4.0-116 Kernel update on 2/21 breaks Nvidia drivers (on 14.04 and 16.04)
Following instructions provided by @cjjefcoat, I managed to get kernel -116 running. It turns out that just removing the "ppa:ubuntu-toolchain-r/test" ppa and reinstalling the gcc-4.8 wasn't sufficient to get it downgraded to "gcc (Ubuntu 4.8.4-2ubuntu1~14.04.4) 4.8.4". Anyway, *purging* the ppa did the trick. Thanks! -- 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/1750937 Title: 4.4.0-116 Kernel update on 2/21 breaks Nvidia drivers (on 14.04 and 16.04) Status in linux package in Ubuntu: Confirmed Status in nvidia-graphics-drivers-384 package in Ubuntu: Confirmed Status in xorg package in Ubuntu: Confirmed Bug description: Running fine with nvidia-384 until this kernel update came along. When booted into the new kernel, got super low resolution and nvidia- settings was missing most of its functionality - could not change resolution. Rebooted into 4.4.0-112 kernel and all was well. The root cause of the problem has been found to be installing the -116 kernel without a sufficiently updated version of gcc. In my case, my system received the gcc update AFTER the kernel update. Uninstalling the -116 kernel and reinstalling it with the updated version of gcc solved the problem for me. ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: xorg 1:7.7+1ubuntu8.1 ProcVersionSignature: Ubuntu 4.4.0-112.135~14.04.1-generic 4.4.98 Uname: Linux 4.4.0-112-generic x86_64 NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia .proc.driver.nvidia.registry: Binary: "" .proc.driver.nvidia.version: NVRM version: NVIDIA UNIX x86_64 Kernel Module 384.111 Tue Dec 19 23:51:45 PST 2017 GCC version: gcc version 4.8.4 (Ubuntu 4.8.4-2ubuntu1~14.04.3) ApportVersion: 2.14.1-0ubuntu3.27 Architecture: amd64 CurrentDesktop: LXDE Date: Wed Feb 21 19:23:39 2018 DistUpgraded: Fresh install DistroCodename: trusty DistroVariant: ubuntu DkmsStatus: bbswitch, 0.7, 4.4.0-112-generic, x86_64: installed bbswitch, 0.7, 4.4.0-116-generic, x86_64: installed nvidia-384, 384.111, 4.4.0-112-generic, x86_64: installed nvidia-384, 384.111, 4.4.0-116-generic, x86_64: installed GraphicsCard: NVIDIA Corporation Device [10de:1c82] (rev a1) (prog-if 00 [VGA controller]) Subsystem: eVga.com. Corp. Device [3842:6253] InstallationDate: Installed on 2015-03-03 (1086 days ago) InstallationMedia: Ubuntu 14.04.2 LTS "Trusty Tahr" - Release amd64 (20150218.1) MachineType: ASUSTeK COMPUTER INC. M11AD ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-112-generic root=UUID=5a88d2a1-0a24-415b-adc2-28435b13248a ro quiet splash vt.handoff=7 SourcePackage: xorg Symptom: display UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 08/15/2013 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 0302 dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: M11AD dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: Rev X.0x dmi.chassis.asset.tag: Asset-1234567890 dmi.chassis.type: 3 dmi.chassis.vendor: Chassis Manufacture dmi.chassis.version: Chassis Version dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr0302:bd08/15/2013:svnASUSTeKCOMPUTERINC.:pnM11AD:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnM11AD:rvrRevX.0x:cvnChassisManufacture:ct3:cvrChassisVersion: dmi.product.name: M11AD dmi.product.version: System Version dmi.sys.vendor: ASUSTeK COMPUTER INC. version.compiz: compiz 1:0.9.11.3+14.04.20160425-0ubuntu1 version.ia32-libs: ia32-libs N/A version.libdrm2: libdrm2 2.4.67-1ubuntu0.14.04.2 version.libgl1-mesa-dri: libgl1-mesa-dri N/A version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A version.libgl1-mesa-glx: libgl1-mesa-glx N/A version.nvidia-graphics-drivers: nvidia-graphics-drivers N/A 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: Wed Feb 21 18:48:14 2018 xserver.configfile: default xserver.errors: xserver.logfile: /var/log/Xorg.0.log xserver.outputs: xserver.version: 2:1.18.3-1ubuntu2.3~trusty4 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1750937/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1751595] [NEW] package libunity9 7.1.4+17.10.20170605-0ubuntu1 failed to install/upgrade: tentative de remplacement de « /usr/bin/unity-scope-loader », qui est différent d'autres
Public bug reported: i don't know ProblemType: Package DistroRelease: Ubuntu 17.10 Package: libunity9 7.1.4+17.10.20170605-0ubuntu1 ProcVersionSignature: Ubuntu 4.13.0-30.33-generic 4.13.13 Uname: Linux 4.13.0-30-generic x86_64 ApportVersion: 2.20.7-0ubuntu3.7 AptOrdering: libunity9:i386: Install NULL: ConfigurePending Architecture: amd64 Date: Sun Feb 25 16:03:21 2018 ErrorMessage: tentative de remplacement de « /usr/bin/unity-scope-loader », qui est différent d'autres instances du paquet libunity9:i386 InstallationDate: Installed on 2017-06-02 (267 days ago) InstallationMedia: Ubuntu 16.10 "Yakkety Yak" - Release amd64 (20161012.2) 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: libunity Title: package libunity9 7.1.4+17.10.20170605-0ubuntu1 failed to install/upgrade: tentative de remplacement de « /usr/bin/unity-scope-loader », qui est différent d'autres instances du paquet libunity9:i386 UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: libunity (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 libunity in Ubuntu. https://bugs.launchpad.net/bugs/1751595 Title: package libunity9 7.1.4+17.10.20170605-0ubuntu1 failed to install/upgrade: tentative de remplacement de « /usr/bin/unity-scope- loader », qui est différent d'autres instances du paquet libunity9:i386 Status in libunity package in Ubuntu: New Bug description: i don't know ProblemType: Package DistroRelease: Ubuntu 17.10 Package: libunity9 7.1.4+17.10.20170605-0ubuntu1 ProcVersionSignature: Ubuntu 4.13.0-30.33-generic 4.13.13 Uname: Linux 4.13.0-30-generic x86_64 ApportVersion: 2.20.7-0ubuntu3.7 AptOrdering: libunity9:i386: Install NULL: ConfigurePending Architecture: amd64 Date: Sun Feb 25 16:03:21 2018 ErrorMessage: tentative de remplacement de « /usr/bin/unity-scope-loader », qui est différent d'autres instances du paquet libunity9:i386 InstallationDate: Installed on 2017-06-02 (267 days ago) InstallationMedia: Ubuntu 16.10 "Yakkety Yak" - Release amd64 (20161012.2) 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: libunity Title: package libunity9 7.1.4+17.10.20170605-0ubuntu1 failed to install/upgrade: tentative de remplacement de « /usr/bin/unity-scope-loader », qui est différent d'autres instances du paquet libunity9:i386 UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libunity/+bug/1751595/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 743710] Re: man page and --help are inconsistent
** Tags added: manpage -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to patch in Ubuntu. https://bugs.launchpad.net/bugs/743710 Title: man page and --help are inconsistent Status in patch package in Ubuntu: New Bug description: Binary package hint: patch man patch shows "-pnum" and "-g num" - once with a space and once without. patch --help shows "-p NUM" and "-g NUM", so it always uses spaces, and it has NUM instead of num patch --version patch 2.6 ProblemType: Bug DistroRelease: Ubuntu 10.10 Package: patch 2.6-2ubuntu1 ProcVersionSignature: Ubuntu 2.6.35-28.49-generic 2.6.35.11 Uname: Linux 2.6.35-28-generic x86_64 NonfreeKernelModules: fglrx Architecture: amd64 Date: Sun Mar 27 18:21:34 2011 EcryptfsInUse: Yes InstallationMedia: Kubuntu 10.04 "Lucid Lynx" - Beta amd64 (20100318) ProcEnviron: LANGUAGE= PATH=(custom, no user) LANG=de_DE.UTF-8 SHELL=/bin/bash SourcePackage: patch To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/patch/+bug/743710/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1690861] Re: typo of descripiton in README
The typo has been fixed, upstream and in patch 2.7.6-1 on Ubuntu bionic. ** Changed in: patch (Ubuntu) Status: Confirmed => Fix Released -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to patch in Ubuntu. https://bugs.launchpad.net/bugs/1690861 Title: typo of descripiton in README Status in Patch: Unknown Status in patch package in Ubuntu: Fix Released Bug description: Line 19 of /usr/share/doc/patch/README contains "descripiton". ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: patch 2.7.1-4ubuntu2.3 Uname: Linux 3.4.0+ x86_64 ApportVersion: 2.14.1-0ubuntu3.23 Architecture: amd64 Date: Mon May 15 18:40:47 2017 Dependencies: gcc-4.9-base 4.9.3-0ubuntu4 libc6 2.19-0ubuntu6.11 libgcc1 1:4.9.3-0ubuntu4 multiarch-support 2.19-0ubuntu6.11 ProcEnviron: Error: [Errno 2] No such file or directory: '/proc/62/environ' SourcePackage: patch UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/patch/+bug/1690861/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1751593] [NEW] Weird black border flickres around windows.
Public bug reported: Whenever I open any new window, a black border around the window appears for a fraction of a second (like a flicker). Although this doesn't happen very frequently, happens around 3-4 times out of 10. This is most noticeable when I right click on Desktop and click on "Open terminal". I can replicate this bug every time when I open terminal this way. Also, when I open terminal by pressing Control+Alt+T, the caption buttons kind of grey out after the flicker and are un-clickable. They look as if the window is not at focus. Workaround is to switch to another window (Alt+Tab) and then switch back to terminal. ProblemType: Bug DistroRelease: Ubuntu 17.10 Package: xorg (not installed) ProcVersionSignature: Ubuntu 4.13.0-36.40-generic 4.13.13 Uname: Linux 4.13.0-36-generic x86_64 ApportVersion: 2.20.7-0ubuntu3.7 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Sun Feb 25 19:58:24 2018 InstallationDate: Installed on 2018-02-13 (11 days ago) InstallationMedia: Ubuntu 16.04.2 LTS "Xenial Xerus" - Release amd64 (20170215.2) SourcePackage: xorg Symptom: display UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: xorg (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug artful wayland-session ** Attachment added: "Screenshot (1).png" https://bugs.launchpad.net/bugs/1751593/+attachment/5062586/+files/Screenshot%20%281%29.png -- 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/1751593 Title: Weird black border flickres around windows. Status in xorg package in Ubuntu: New Bug description: Whenever I open any new window, a black border around the window appears for a fraction of a second (like a flicker). Although this doesn't happen very frequently, happens around 3-4 times out of 10. This is most noticeable when I right click on Desktop and click on "Open terminal". I can replicate this bug every time when I open terminal this way. Also, when I open terminal by pressing Control+Alt+T, the caption buttons kind of grey out after the flicker and are un-clickable. They look as if the window is not at focus. Workaround is to switch to another window (Alt+Tab) and then switch back to terminal. ProblemType: Bug DistroRelease: Ubuntu 17.10 Package: xorg (not installed) ProcVersionSignature: Ubuntu 4.13.0-36.40-generic 4.13.13 Uname: Linux 4.13.0-36-generic x86_64 ApportVersion: 2.20.7-0ubuntu3.7 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Sun Feb 25 19:58:24 2018 InstallationDate: Installed on 2018-02-13 (11 days ago) InstallationMedia: Ubuntu 16.04.2 LTS "Xenial Xerus" - Release amd64 (20170215.2) SourcePackage: xorg Symptom: display UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1751593/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1750937] Re: 4.4.0-116 Kernel update on 2/21 breaks Nvidia drivers (on 14.04 and 16.04)
Hello, just had the same experience :( not so funny, Thanks to you all, I just downloaded linux-image- extra-4.4.0-116-generic_4.4.0-116.140_amd64.deb via internet on my mobile , then copy paste to pc, and installed manualy (sudo dpkg -i linux-image-extra-4.4.0-116-generic_4.4.0-116.140_amd64.deb) , after reboot all good, back in business baby :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/1750937 Title: 4.4.0-116 Kernel update on 2/21 breaks Nvidia drivers (on 14.04 and 16.04) Status in linux package in Ubuntu: Confirmed Status in nvidia-graphics-drivers-384 package in Ubuntu: Confirmed Status in xorg package in Ubuntu: Confirmed Bug description: Running fine with nvidia-384 until this kernel update came along. When booted into the new kernel, got super low resolution and nvidia- settings was missing most of its functionality - could not change resolution. Rebooted into 4.4.0-112 kernel and all was well. The root cause of the problem has been found to be installing the -116 kernel without a sufficiently updated version of gcc. In my case, my system received the gcc update AFTER the kernel update. Uninstalling the -116 kernel and reinstalling it with the updated version of gcc solved the problem for me. ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: xorg 1:7.7+1ubuntu8.1 ProcVersionSignature: Ubuntu 4.4.0-112.135~14.04.1-generic 4.4.98 Uname: Linux 4.4.0-112-generic x86_64 NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia .proc.driver.nvidia.registry: Binary: "" .proc.driver.nvidia.version: NVRM version: NVIDIA UNIX x86_64 Kernel Module 384.111 Tue Dec 19 23:51:45 PST 2017 GCC version: gcc version 4.8.4 (Ubuntu 4.8.4-2ubuntu1~14.04.3) ApportVersion: 2.14.1-0ubuntu3.27 Architecture: amd64 CurrentDesktop: LXDE Date: Wed Feb 21 19:23:39 2018 DistUpgraded: Fresh install DistroCodename: trusty DistroVariant: ubuntu DkmsStatus: bbswitch, 0.7, 4.4.0-112-generic, x86_64: installed bbswitch, 0.7, 4.4.0-116-generic, x86_64: installed nvidia-384, 384.111, 4.4.0-112-generic, x86_64: installed nvidia-384, 384.111, 4.4.0-116-generic, x86_64: installed GraphicsCard: NVIDIA Corporation Device [10de:1c82] (rev a1) (prog-if 00 [VGA controller]) Subsystem: eVga.com. Corp. Device [3842:6253] InstallationDate: Installed on 2015-03-03 (1086 days ago) InstallationMedia: Ubuntu 14.04.2 LTS "Trusty Tahr" - Release amd64 (20150218.1) MachineType: ASUSTeK COMPUTER INC. M11AD ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-112-generic root=UUID=5a88d2a1-0a24-415b-adc2-28435b13248a ro quiet splash vt.handoff=7 SourcePackage: xorg Symptom: display UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 08/15/2013 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 0302 dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: M11AD dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: Rev X.0x dmi.chassis.asset.tag: Asset-1234567890 dmi.chassis.type: 3 dmi.chassis.vendor: Chassis Manufacture dmi.chassis.version: Chassis Version dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr0302:bd08/15/2013:svnASUSTeKCOMPUTERINC.:pnM11AD:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnM11AD:rvrRevX.0x:cvnChassisManufacture:ct3:cvrChassisVersion: dmi.product.name: M11AD dmi.product.version: System Version dmi.sys.vendor: ASUSTeK COMPUTER INC. version.compiz: compiz 1:0.9.11.3+14.04.20160425-0ubuntu1 version.ia32-libs: ia32-libs N/A version.libdrm2: libdrm2 2.4.67-1ubuntu0.14.04.2 version.libgl1-mesa-dri: libgl1-mesa-dri N/A version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A version.libgl1-mesa-glx: libgl1-mesa-glx N/A version.nvidia-graphics-drivers: nvidia-graphics-drivers N/A 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: Wed Feb 21 18:48:14 2018 xserver.configfile: default xserver.errors: xserver.logfile: /var/log/Xorg.0.log xserver.outputs: xserver.version: 2:1.18.3-1ubuntu2.3~trusty4 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1750937/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1750937] Re: 4.4.0-116 Kernel update on 2/21 breaks Nvidia drivers (on 14.04 and 16.04)
Hello, just had the same experience :( not so funny, Thanks to you all, I just donloaded 116 and installed manualy, after reboot all good, back in business baby :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/1750937 Title: 4.4.0-116 Kernel update on 2/21 breaks Nvidia drivers (on 14.04 and 16.04) Status in linux package in Ubuntu: Confirmed Status in nvidia-graphics-drivers-384 package in Ubuntu: Confirmed Status in xorg package in Ubuntu: Confirmed Bug description: Running fine with nvidia-384 until this kernel update came along. When booted into the new kernel, got super low resolution and nvidia- settings was missing most of its functionality - could not change resolution. Rebooted into 4.4.0-112 kernel and all was well. The root cause of the problem has been found to be installing the -116 kernel without a sufficiently updated version of gcc. In my case, my system received the gcc update AFTER the kernel update. Uninstalling the -116 kernel and reinstalling it with the updated version of gcc solved the problem for me. ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: xorg 1:7.7+1ubuntu8.1 ProcVersionSignature: Ubuntu 4.4.0-112.135~14.04.1-generic 4.4.98 Uname: Linux 4.4.0-112-generic x86_64 NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia .proc.driver.nvidia.registry: Binary: "" .proc.driver.nvidia.version: NVRM version: NVIDIA UNIX x86_64 Kernel Module 384.111 Tue Dec 19 23:51:45 PST 2017 GCC version: gcc version 4.8.4 (Ubuntu 4.8.4-2ubuntu1~14.04.3) ApportVersion: 2.14.1-0ubuntu3.27 Architecture: amd64 CurrentDesktop: LXDE Date: Wed Feb 21 19:23:39 2018 DistUpgraded: Fresh install DistroCodename: trusty DistroVariant: ubuntu DkmsStatus: bbswitch, 0.7, 4.4.0-112-generic, x86_64: installed bbswitch, 0.7, 4.4.0-116-generic, x86_64: installed nvidia-384, 384.111, 4.4.0-112-generic, x86_64: installed nvidia-384, 384.111, 4.4.0-116-generic, x86_64: installed GraphicsCard: NVIDIA Corporation Device [10de:1c82] (rev a1) (prog-if 00 [VGA controller]) Subsystem: eVga.com. Corp. Device [3842:6253] InstallationDate: Installed on 2015-03-03 (1086 days ago) InstallationMedia: Ubuntu 14.04.2 LTS "Trusty Tahr" - Release amd64 (20150218.1) MachineType: ASUSTeK COMPUTER INC. M11AD ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-112-generic root=UUID=5a88d2a1-0a24-415b-adc2-28435b13248a ro quiet splash vt.handoff=7 SourcePackage: xorg Symptom: display UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 08/15/2013 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 0302 dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: M11AD dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: Rev X.0x dmi.chassis.asset.tag: Asset-1234567890 dmi.chassis.type: 3 dmi.chassis.vendor: Chassis Manufacture dmi.chassis.version: Chassis Version dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr0302:bd08/15/2013:svnASUSTeKCOMPUTERINC.:pnM11AD:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnM11AD:rvrRevX.0x:cvnChassisManufacture:ct3:cvrChassisVersion: dmi.product.name: M11AD dmi.product.version: System Version dmi.sys.vendor: ASUSTeK COMPUTER INC. version.compiz: compiz 1:0.9.11.3+14.04.20160425-0ubuntu1 version.ia32-libs: ia32-libs N/A version.libdrm2: libdrm2 2.4.67-1ubuntu0.14.04.2 version.libgl1-mesa-dri: libgl1-mesa-dri N/A version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A version.libgl1-mesa-glx: libgl1-mesa-glx N/A version.nvidia-graphics-drivers: nvidia-graphics-drivers N/A 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: Wed Feb 21 18:48:14 2018 xserver.configfile: default xserver.errors: xserver.logfile: /var/log/Xorg.0.log xserver.outputs: xserver.version: 2:1.18.3-1ubuntu2.3~trusty4 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1750937/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1751198] Re: The problem is with ethernet. After sometime ethernet network doesn't work. LAN works well but internet connectivity has problem. I can connect to same network via w
Please attach `dmesg` when this issue happens, thanks! -- 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/1751198 Title: The problem is with ethernet. After sometime ethernet network doesn't work. LAN works well but internet connectivity has problem. I can connect to same network via wifi and there is no problem. Bu through Ethernet for this particular machine I am seeing this problem. Status in network-manager package in Ubuntu: New Bug description: The problem is with ethernet. After sometime ethernet network doesn't work. LAN works well but internet connectivity has problem. I can connect to same network via wifi and there is no problem. Bu through Ethernet for this particular machine I am seeing this problem. With 16.04 there was no issue at all. ProblemType: Bug DistroRelease: Ubuntu 17.10 Package: network-manager 1.8.4-1ubuntu3 [modified: usr/lib/NetworkManager/conf.d/10-globally-managed-devices.conf] ProcVersionSignature: Ubuntu 4.13.0-36.40-generic 4.13.13 Uname: Linux 4.13.0-36-generic x86_64 ApportVersion: 2.20.7-0ubuntu3.7 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Fri Feb 23 11:52:12 2018 IpRoute: default via 10.100.10.1 dev eno1 proto static metric 20100 10.100.10.0/23 dev eno1 proto kernel scope link src 10.100.11.8 metric 100 169.254.0.0/16 dev eno1 scope link metric 1000 169.254.0.0/16 dev eno1 scope link metric 1001 192.168.122.0/24 dev virbr0 proto kernel scope link src 192.168.122.1 linkdown NetworkManager.state: [main] NetworkingEnabled=true WirelessEnabled=true WWANEnabled=true RfKill: SourcePackage: network-manager UpgradeStatus: No upgrade log present (probably fresh install) mtime.conffile..etc.NetworkManager.NetworkManager.conf: 2018-01-08T14:11:20.564841 nmcli-dev: DEVICE TYPE STATE DBUS-PATH CONNECTION CON-UUID CON-PATH virbr0 bridgeconnected /org/freedesktop/NetworkManager/Devices/3 virbr0 f7ed1838-6b56-4032-99f9-602539799a67 /org/freedesktop/NetworkManager/ActiveConnection/2 eno1ethernet connected /org/freedesktop/NetworkManager/Devices/2 Wired connection 1 84d5092f-8385-491c-acab-38e47bc5ffc5 /org/freedesktop/NetworkManager/ActiveConnection/16 lo loopback unmanaged /org/freedesktop/NetworkManager/Devices/1 -- ---- virbr0-nic tun unmanaged /org/freedesktop/NetworkManager/Devices/4 -- ---- nmcli-nm: RUNNING VERSION STATE STARTUP CONNECTIVITY NETWORKING WIFI-HW WIFI WWAN-HW WWAN running 1.8.4connected started limited enabled enabled enabled enabled enabled To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1751198/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1750474] Re: package libkmod2 22-1ubuntu5 [modified: usr/share/doc/libkmod2/changelog.Debian.gz] failed to install/upgrade: trying to overwrite shared '/usr/share/doc/libkmod2/ch
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: kmod (Ubuntu) Status: New => Confirmed -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to kmod in Ubuntu. https://bugs.launchpad.net/bugs/1750474 Title: package libkmod2 22-1ubuntu5 [modified: usr/share/doc/libkmod2/changelog.Debian.gz] failed to install/upgrade: trying to overwrite shared '/usr/share/doc/libkmod2/changelog.Debian.gz', which is different from other instances of package libkmod2:i386 Status in kmod package in Ubuntu: Confirmed Bug description: I'm not sure if this is a new bug or not but I haven't been able to install new software for quite some time. ProblemType: Package DistroRelease: Ubuntu 16.04 Package: libkmod2 22-1ubuntu5 [modified: usr/share/doc/libkmod2/changelog.Debian.gz] ProcVersionSignature: Ubuntu 4.4.0-89.112-generic 4.4.76 Uname: Linux 4.4.0-89-generic x86_64 NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia ApportVersion: 2.20.1-0ubuntu2.10 Architecture: amd64 Date: Mon Feb 19 19:31:53 2018 Dependencies: gcc-6-base 6.0.1-0ubuntu1 libc6 2.23-0ubuntu9 libgcc1 1:6.0.1-0ubuntu1 DpkgHistoryLog: Start-Date: 2018-02-19 19:31:46 Commandline: apt-get -f install Requested-By: robert (1000) Install: libkmod2:i386 (22-1ubuntu5, automatic) Upgrade: udev:amd64 (229-4ubuntu19, 229-4ubuntu21.1), libudev1:amd64 (229-4ubuntu19, 229-4ubuntu21.1), libudev1:i386 (229-4ubuntu19, 229-4ubuntu21.1), libudev-dev:i386 (229-4ubuntu19, 229-4ubuntu21.1) DpkgTerminalLog: Preparing to unpack .../libkmod2_22-1ubuntu5_i386.deb ... Unpacking libkmod2:i386 (22-1ubuntu5) ... dpkg: error processing archive /var/cache/apt/archives/libkmod2_22-1ubuntu5_i386.deb (--unpack): trying to overwrite shared '/usr/share/doc/libkmod2/changelog.Debian.gz', which is different from other instances of package libkmod2:i386 DuplicateSignature: package:libkmod2:22-1ubuntu5 [modified: usr/share/doc/libkmod2/changelog.Debian.gz] Unpacking libkmod2:i386 (22-1ubuntu5) ... dpkg: error processing archive /var/cache/apt/archives/libkmod2_22-1ubuntu5_i386.deb (--unpack): trying to overwrite shared '/usr/share/doc/libkmod2/changelog.Debian.gz', which is different from other instances of package libkmod2:i386 ErrorMessage: trying to overwrite shared '/usr/share/doc/libkmod2/changelog.Debian.gz', which is different from other instances of package libkmod2:i386 InstallationDate: Installed on 2017-03-28 (328 days ago) InstallationMedia: Ubuntu 14.04.3 LTS "Trusty Tahr" - Beta amd64 (20150805) RelatedPackageVersions: dpkg 1.18.4ubuntu1.2 apt 1.2.24 SourcePackage: kmod Title: package libkmod2 22-1ubuntu5 [modified: usr/share/doc/libkmod2/changelog.Debian.gz] failed to install/upgrade: trying to overwrite shared '/usr/share/doc/libkmod2/changelog.Debian.gz', which is different from other instances of package libkmod2:i386 UpgradeStatus: Upgraded to xenial on 2017-07-05 (229 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/kmod/+bug/1750474/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1751402] Re: abstraction/nameservice should include allow access to /var/lib/sss/mc/initgroups
FTR this was already added upstream in commit 84cd523d8c which is part of AppArmor v2.12. So i'll be fixed whenever Ubuntu upgrades to 2.12 :) ** Also affects: apparmor Importance: Undecided Status: New ** Changed in: apparmor Status: New => 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/1751402 Title: abstraction/nameservice should include allow access to /var/lib/sss/mc/initgroups Status in AppArmor: Fix Released Status in apparmor package in Ubuntu: New Bug description: From https://bugs.launchpad.net/ubuntu/+source/unbound/+bug/1749931/comments/4: [2794367.925181] apparmor="DENIED" operation="open" profile="/usr/sbin/unbound" name="/var/lib/sss/mc/initgroups" pid=5111 comm="unbound" requested_mask="r" denied_mask="r" fsuid=0 ouid=0 The unbound AA profile includes abstractions/nameservice which already has some rules for files under /var/lib/sss/mc. I think that adding "/var/lib/sss/mc/initgroups r" to abstractions/nameservice would make sense: $ diff -Naur abstractions/nameservice.orig abstractions/nameservice --- abstractions/nameservice.orig 2018-02-24 02:19:24.310884300 + +++ abstractions/nameservice 2018-02-24 02:20:10.578785312 + @@ -30,6 +30,7 @@ # and the nss plugin also needs to talk to a pipe /var/lib/sss/mc/group r, /var/lib/sss/mc/passwd r, + /var/lib/sss/mc/initgroups r, /var/lib/sss/pipes/nss rw, /etc/resolv.confr, To manage notifications about this bug go to: https://bugs.launchpad.net/apparmor/+bug/1751402/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
Re: [Touch-packages] [Bug 1659953] Re: package ca-certificates 20161130 failed to install/upgrade: triggers looping, abandoned
😂😂😂 Von meiner Samsung Gear S3 gesendet.Von meinem Samsung Galaxy S8+ Smartphone gesendet. Ursprüngliche Nachricht Von: dino99 <1659...@bugs.launchpad.net> Datum: 25.02.18 11:58 (GMT+01:00) An: schweitzeronl...@gmail.com Betreff: [Bug 1659953] Re: package ca-certificates 20161130 failed to install/upgrade: triggers looping, abandoned That version is now dead http://news.softpedia.com/news/ubuntu-17-04-zesty-zapus-has-reached-end-of-life-upgrade-to-ubuntu-17-10-now-519360.shtml ** Changed in: ca-certificates (Ubuntu) Status: New => Invalid -- You received this bug notification because you are subscribed to the bug report. https://bugs.launchpad.net/bugs/1659953 Title: package ca-certificates 20161130 failed to install/upgrade: triggers looping, abandoned Status in ca-certificates package in Ubuntu: Invalid Bug description: . ProblemType: Package DistroRelease: Ubuntu 17.04 Package: ca-certificates 20161130 Uname: Linux 4.9.6-040906-generic x86_64 NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia ApportVersion: 2.20.4-0ubuntu1 Architecture: amd64 Date: Fri Jan 27 22:09:16 2017 ErrorMessage: triggers looping, abandoned InstallationDate: Installed on 2017-01-27 (0 days ago) InstallationMedia: Xubuntu 16.10 "Yakkety Yak" - Release amd64 (20161012.2) PackageArchitecture: all RelatedPackageVersions: dpkg 1.18.10ubuntu1 apt 1.4~beta4ubuntu1 SourcePackage: ca-certificates Title: package ca-certificates 20161130 failed to install/upgrade: triggers looping, abandoned UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ca-certificates/+bug/1659953/+subscriptions -- 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/1659953 Title: package ca-certificates 20161130 failed to install/upgrade: triggers looping, abandoned Status in ca-certificates package in Ubuntu: Invalid Bug description: . ProblemType: Package DistroRelease: Ubuntu 17.04 Package: ca-certificates 20161130 Uname: Linux 4.9.6-040906-generic x86_64 NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia ApportVersion: 2.20.4-0ubuntu1 Architecture: amd64 Date: Fri Jan 27 22:09:16 2017 ErrorMessage: triggers looping, abandoned InstallationDate: Installed on 2017-01-27 (0 days ago) InstallationMedia: Xubuntu 16.10 "Yakkety Yak" - Release amd64 (20161012.2) PackageArchitecture: all RelatedPackageVersions: dpkg 1.18.10ubuntu1 apt 1.4~beta4ubuntu1 SourcePackage: ca-certificates Title: package ca-certificates 20161130 failed to install/upgrade: triggers looping, abandoned UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ca-certificates/+bug/1659953/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1658250] Re: Window positions change in nonsensical ways when a secondary display is moved above the primary
That version is now dead http://news.softpedia.com/news/ubuntu-17-04-zesty-zapus-has-reached-end-of-life-upgrade-to-ubuntu-17-10-now-519360.shtml ** Changed in: xorg (Ubuntu) Status: New => Invalid -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to xorg in Ubuntu. https://bugs.launchpad.net/bugs/1658250 Title: Window positions change in nonsensical ways when a secondary display is moved above the primary Status in xorg package in Ubuntu: Invalid Bug description: Most commonly, they'll be partway on the upper monitor, but mostly on the bottom. But sometimes, they'll be halfway off the screen on the bottom monitor. New windows are sometimes created in slightly odd places as well; usually, the titlebar will be on the top screen and the rest of the window on the bottom, meaning the gnome-shell bar is obscuring part of the window. Windows that are maximized when the change is made aren't affected. ProblemType: Bug DistroRelease: Ubuntu 17.04 Package: xorg 1:7.7+16ubuntu2 ProcVersionSignature: Ubuntu 4.9.0-11.12-generic 4.9.0 Uname: Linux 4.9.0-11-generic x86_64 ApportVersion: 2.20.4-0ubuntu1 Architecture: amd64 BootLog: CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: None CurrentDesktop: GNOME Date: Fri Jan 20 18:09:51 2017 DistUpgraded: 2017-01-17 21:44:12,781 DEBUG Running PostInstallScript: './xorg_fix_proprietary.py' DistroCodename: zesty DistroVariant: ubuntu ExtraDebuggingInterest: Yes GraphicsCard: Subsystem: ASUSTeK Computer Inc. Xeon E3-1200 v3/4th Gen Core Processor Integrated Graphics Controller [1043:8534] Advanced Micro Devices, Inc. [AMD/ATI] Ellesmere [Radeon RX 470/480] [1002:67df] (rev c7) (prog-if 00 [VGA controller]) Subsystem: XFX Pine Group Inc. Radeon RX 480 [1682:9480] InstallationDate: Installed on 2017-01-17 (3 days ago) InstallationMedia: Ubuntu-GNOME 16.04.1 LTS "Xenial Xerus" - Release amd64 (20160720) MachineType: ASUS All Series ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.9.0-11-generic root=UUID=638d73c8-aa0e-423b-907c-6bbb2c237275 ro i915.modeset=0 quiet splash vt.handoff=7 Renderer: Software SourcePackage: xorg Symptom: display UpgradeStatus: Upgraded to zesty on 2017-01-18 (2 days ago) dmi.bios.date: 08/07/2014 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 2004 dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: H87M-E dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: Rev X.0x dmi.chassis.asset.tag: Asset-1234567890 dmi.chassis.type: 3 dmi.chassis.vendor: Chassis Manufacture dmi.chassis.version: Chassis Version dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr2004:bd08/07/2014:svnASUS:pnAllSeries:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnH87M-E:rvrRevX.0x:cvnChassisManufacture:ct3:cvrChassisVersion: dmi.product.name: All Series dmi.product.version: System Version dmi.sys.vendor: ASUS version.compiz: compiz N/A version.ia32-libs: ia32-libs N/A version.libdrm2: libdrm2 2.4.74-1 version.libgl1-mesa-dri: libgl1-mesa-dri 13.0.3-1ubuntu2 version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A version.libgl1-mesa-glx: libgl1-mesa-glx 13.0.3-1ubuntu2 version.xserver-xorg-core: xserver-xorg-core 2:1.18.4-1ubuntu7 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.10.2-1ubuntu1 version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.8.0-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20160706-1ubuntu1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau N/A xserver.bootTime: Mon Jan 16 20:46:55 2017 xserver.configfile: default xserver.errors: open /dev/dri/card0: No such file or directory open /dev/dri/card0: No such file or directory Screen 0 deleted because of no matching config section. AIGLX: reverting to software rendering xserver.logfile: /var/log/Xorg.0.log xserver.outputs: xserver.version: 2:1.18.4-0ubuntu0.2 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1658250/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1658706] Re: version in pkgconfig file (0.2) older than packaging version (0.3.x)
That version is now dead http://news.softpedia.com/news/ubuntu-17-04-zesty-zapus-has-reached-end-of-life-upgrade-to-ubuntu-17-10-now-519360.shtml ** Changed in: content-hub (Ubuntu) Status: Confirmed => Invalid -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to content-hub in Ubuntu. https://bugs.launchpad.net/bugs/1658706 Title: version in pkgconfig file (0.2) older than packaging version (0.3.x) Status in content-hub package in Ubuntu: Invalid Bug description: Version in the pkgconfig file is 0.2 Version of libcontent-hub according to the debian packaging is 0.3.x The minor version should match at least, no? To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/content-hub/+bug/1658706/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1659130] Re: Battery indicator doesn't change the status when I plug the charger
That version is now dead http://news.softpedia.com/news/ubuntu-17-04-zesty-zapus-has-reached-end-of-life-upgrade-to-ubuntu-17-10-now-519360.shtml ** Changed in: upower (Ubuntu) Status: New => Invalid -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to upower in Ubuntu. https://bugs.launchpad.net/bugs/1659130 Title: Battery indicator doesn't change the status when I plug the charger Status in upower package in Ubuntu: Invalid Bug description: When I plug the charger, the battery indicator doesn't change to "charging" until the battery increase at least one level. -- You can try plugin and unplugging your charger. ProblemType: Bug DistroRelease: Ubuntu 17.04 Package: evince 3.22.1-2ubuntu1 ProcVersionSignature: Ubuntu 4.9.0-15.16-generic 4.9.5 Uname: Linux 4.9.0-15-generic x86_64 NonfreeKernelModules: nvidia_drm nvidia_modeset nvidia ApportVersion: 2.20.4-0ubuntu1 Architecture: amd64 CurrentDesktop: Unity Date: Tue Jan 24 23:23:00 2017 InstallationDate: Installed on 2017-01-08 (16 days ago) InstallationMedia: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 (20160719) ProcEnviron: LANGUAGE=es PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=es_ES.UTF-8 SHELL=/bin/bash SourcePackage: evince UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/upower/+bug/1659130/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1658273] Re: Failed to preset unit: Unit file /etc/systemd/system/samba-ad-dc.service is masked.
Just checked on Bionic, and the output is clean now. ** Changed in: systemd (Ubuntu) Status: Confirmed => Fix Released ** Changed in: samba (Ubuntu) Status: Confirmed => Fix Released -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to systemd in Ubuntu. https://bugs.launchpad.net/bugs/1658273 Title: Failed to preset unit: Unit file /etc/systemd/system/samba-ad- dc.service is masked. Status in samba package in Ubuntu: Fix Released Status in systemd package in Ubuntu: Fix Released Bug description: On a standalone desktop running zesty with a gnome-shell session, when upgrading the samba packages, i get: Setting up samba (2:4.4.5+dfsg-2ubuntu7) ... Failed to preset unit: Unit file /etc/systemd/system/samba-ad-dc.service is masked. /usr/bin/deb-systemd-helper: error: systemctl preset failed on samba-ad-dc.service: No such file or directory note: ubuntu-bug ask questions about a possible windows relationship, but there is no option for a standalone system like that one; so as samba is installed to satisfy qemu, these questions completly ignore such case and send inappropriate report. and smbd still crashing on cold boot ( lp:1658293 ) (standalone desktop) note2: a more recent Debian version seems workaround that output: samba (2:4.4.5+dfsg-3) [ Mathieu Parent ] * Remove /etc/systemd/system/samba-ad-dc.service (from postinst) on purge. Closes: #832352 and samba (2:4.4.6+dfsg-1) Only fix PIDFile in {nmbd,samba-ad-dc,smbd,winbind}.service (i.e. not ctdb.service) Closes: #838000. and samba (2:4.4.6+dfsg-2) * Remove uses of tevent internals. This fixes segfault. Closes: #840382, #840298. http://metadata.ftp-master.debian.org/changelogs/main/s/samba/samba_4.5.2+dfsg-2_changelog ... time to get package synced To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/samba/+bug/1658273/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1659953] Re: package ca-certificates 20161130 failed to install/upgrade: triggers looping, abandoned
That version is now dead http://news.softpedia.com/news/ubuntu-17-04-zesty-zapus-has-reached-end-of-life-upgrade-to-ubuntu-17-10-now-519360.shtml ** Changed in: ca-certificates (Ubuntu) Status: New => Invalid -- 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/1659953 Title: package ca-certificates 20161130 failed to install/upgrade: triggers looping, abandoned Status in ca-certificates package in Ubuntu: Invalid Bug description: . ProblemType: Package DistroRelease: Ubuntu 17.04 Package: ca-certificates 20161130 Uname: Linux 4.9.6-040906-generic x86_64 NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia ApportVersion: 2.20.4-0ubuntu1 Architecture: amd64 Date: Fri Jan 27 22:09:16 2017 ErrorMessage: triggers looping, abandoned InstallationDate: Installed on 2017-01-27 (0 days ago) InstallationMedia: Xubuntu 16.10 "Yakkety Yak" - Release amd64 (20161012.2) PackageArchitecture: all RelatedPackageVersions: dpkg 1.18.10ubuntu1 apt 1.4~beta4ubuntu1 SourcePackage: ca-certificates Title: package ca-certificates 20161130 failed to install/upgrade: triggers looping, abandoned UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ca-certificates/+bug/1659953/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1660341] Re: Video driver not found
That version is now dead http://news.softpedia.com/news/ubuntu-17-04-zesty-zapus-has-reached-end-of-life-upgrade-to-ubuntu-17-10-now-519360.shtml ** Changed in: xorg (Ubuntu) Status: New => Invalid -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to xorg in Ubuntu. https://bugs.launchpad.net/bugs/1660341 Title: Video driver not found Status in xorg package in Ubuntu: Invalid Bug description: Drive video not found ProblemType: Bug DistroRelease: Ubuntu 17.04 Package: xorg 1:7.7+16ubuntu2 ProcVersionSignature: Ubuntu 4.9.0-12.13-generic 4.9.2 Uname: Linux 4.9.0-12-generic x86_64 .tmp.unity_support_test.0: ApportVersion: 2.20.4-0ubuntu1 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: Mon Jan 30 11:43:21 2017 DistUpgraded: 2017-01-18 12:06:54,796 DEBUG running apport_crash() DistroCodename: zesty DistroVariant: ubuntu ExtraDebuggingInterest: Yes, including running git bisection searches GraphicsCard: Intel Corporation 2nd Generation Core Processor Family Integrated Graphics Controller [8086:0102] (rev 09) (prog-if 00 [VGA controller]) Subsystem: ASUSTeK Computer Inc. 2nd Generation Core Processor Family Integrated Graphics Controller [1043:844d] InstallationDate: Installed on 2016-10-04 (117 days ago) InstallationMedia: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 (20160719) MachineType: System manufacturer System Product Name ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.9.0-12-generic root=UUID=205cc203-ef14-482c-b2ef-e4fb30d94968 ro text splash vga=791 i915.modeset=1 i915.i915_enable_rc6=1 i915.semaphores=1 pcie_aspm=force vt.handoff=7 SourcePackage: xorg UpgradeStatus: Upgraded to zesty on 2017-01-18 (11 days ago) dmi.bios.date: 05/13/2013 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 4307 dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: P8H61-M LE/BR dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: Rev x.0x dmi.chassis.asset.tag: Asset-1234567890 dmi.chassis.type: 3 dmi.chassis.vendor: Chassis Manufacture dmi.chassis.version: Chassis Version dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr4307:bd05/13/2013:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnP8H61-MLE/BR:rvrRevx.0x:cvnChassisManufacture:ct3:cvrChassisVersion: dmi.product.name: System Product Name dmi.product.version: System Version dmi.sys.vendor: System manufacturer version.compiz: compiz 1:0.9.13.1+17.04.20170109-0ubuntu1 version.ia32-libs: ia32-libs N/A version.libdrm2: libdrm2 2.4.74+git20170126.5403cb39-0ubuntu0ricotz version.libgl1-mesa-dri: libgl1-mesa-dri 17.0.0~git20170126+17.0.d283ec0a-0ubuntu0ricotz version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A version.libgl1-mesa-glx: libgl1-mesa-glx 17.0.0~git20170126+17.0.d283ec0a-0ubuntu0ricotz version.xserver-xorg-core: xserver-xorg-core 2:1.18.4-1ubuntu7 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.10.2-1ubuntu1 version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.8.99+git20161127.487aa62a-0ubuntu0ricotz version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20161127.bde94605-0ubuntu0ricotz2 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.13+git20161127.1516d35b-0ubuntu0ricotz xserver.bootTime: Mon Jan 30 10:05:52 2017 xserver.configfile: default xserver.errors: Screen 0 deleted because of no matching config section. Device(s) detected, but none match those in the config file. Screen 0 deleted because of no matching config section. xserver.logfile: /var/log/Xorg.0.log xserver.outputs: OutputDP-1 HDMI-1 VGA-1 xserver.version: 2:1.18.4-1ubuntu7 xserver.video_driver: modeset To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1660341/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1662020] Re: package ca-certificates 20161130 failed to install/upgrade: triggers looping, abandoned
That version is now dead http://news.softpedia.com/news/ubuntu-17-04-zesty-zapus-has-reached-end-of-life-upgrade-to-ubuntu-17-10-now-519360.shtml ** Changed in: ca-certificates (Ubuntu) Status: New => Invalid -- 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/1662020 Title: package ca-certificates 20161130 failed to install/upgrade: triggers looping, abandoned Status in ca-certificates package in Ubuntu: Invalid Bug description: I dont know what is failing, if anything, but a big report kept popping up so I figured I would submit it for you guys ProblemType: Package DistroRelease: Ubuntu 17.04 Package: ca-certificates 20161130 ProcVersionSignature: Ubuntu 4.9.0-16.17-generic 4.9.6 Uname: Linux 4.9.0-16-generic x86_64 ApportVersion: 2.20.4-0ubuntu2 Architecture: amd64 Date: Sun Feb 5 17:11:09 2017 ErrorMessage: triggers looping, abandoned InstallationDate: Installed on 2017-02-05 (0 days ago) InstallationMedia: Ubuntu-GNOME 17.04 "Zesty Zapus" - Alpha amd64 (20170126) PackageArchitecture: all RelatedPackageVersions: dpkg 1.18.10ubuntu1 apt 1.4~beta4ubuntu1 SourcePackage: ca-certificates Title: package ca-certificates 20161130 failed to install/upgrade: triggers looping, abandoned UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ca-certificates/+bug/1662020/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1663292] Re: In zesty, unity scope fails to connect to zeitgeist
That version is now dead http://news.softpedia.com/news/ubuntu-17-04-zesty-zapus-has-reached-end-of-life-upgrade-to-ubuntu-17-10-now-519360.shtml ** Changed in: zeitgeist (Ubuntu) Status: Confirmed => Invalid -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to zeitgeist in Ubuntu. https://bugs.launchpad.net/bugs/1663292 Title: In zesty, unity scope fails to connect to zeitgeist Status in zeitgeist package in Ubuntu: Invalid Bug description: Description: Ubuntu Zesty Zapus (development branch) Release: 17.04 Since I installed 17.04 (fresh install), first use of the main unity scope takes a long time (timeout ?). After some time, it works. Looking at the logs in syslog, I've spotted these lines: unity-scope-loa[9221]: daemon.vala:: Error performing search '': Erreur lors de l'appel de StartServiceByName pour org.gnome.zeitgeist.Engine : Le délai d'attente est dépassé Feb 9 16:50:02 franck-ThinkPad-T430s unity-scope-hom[9210]: unity-master-scope.vala:114: Unable to search scope: 'Le délai d'attente est dépassé' Feb 9 16:50:02 franck-ThinkPad-T430s unity-files-dae[9223]: index.vala:61: Unable to connect to Zeitgeist FTS: Erreur lors de l'appel de StartServiceByName pour org.gnome.zeitgeist.Engine : Le délai d'attente est dépassé Feb 9 16:51:12 franck-ThinkPad-T430s dbus-daemon[7051]: Failed to activate service 'org.gnome.zeitgeist.Engine': timed out ProblemType: Bug DistroRelease: Ubuntu 17.04 Package: zeitgeist (not installed) ProcVersionSignature: Ubuntu 4.9.0-15.16-generic 4.9.5 Uname: Linux 4.9.0-15-generic x86_64 NonfreeKernelModules: zfs zunicode zavl zcommon znvpair ApportVersion: 2.20.4-0ubuntu2 Architecture: amd64 CurrentDesktop: Unity Date: Thu Feb 9 16:55:58 2017 InstallationDate: Installed on 2017-02-01 (7 days ago) InstallationMedia: Ubuntu 17.04 "Zesty Zapus" - Alpha amd64 (20170201) SourcePackage: zeitgeist UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/zeitgeist/+bug/1663292/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1663421] Re: systemd-udevd crashed with SIGABRT in __open_nocancel()
That version is now dead http://news.softpedia.com/news/ubuntu-17-04-zesty-zapus-has-reached-end-of-life-upgrade-to-ubuntu-17-10-now-519360.shtml ** Changed in: systemd (Ubuntu) Status: Confirmed => Invalid -- 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/1663421 Title: systemd-udevd crashed with SIGABRT in __open_nocancel() Status in systemd package in Ubuntu: Invalid Bug description: Description: Ubuntu Zesty Zapus (development branch) Release: 17.04 Destro: Ubuntu Mate Windows manager: Marco(compton GPU compositor) Video card: Radeon RX 460 4GB 128bit OpenGL vendor string: X.Org I get this error after usb-gtk-creator finish to upload a os on a usb stick. ProblemType: Crash DistroRelease: Ubuntu 17.04 Package: udev 232-8 ProcVersionSignature: Ubuntu 4.9.0-15.16-generic 4.9.5 Uname: Linux 4.9.0-15-generic x86_64 ApportVersion: 2.20.4-0ubuntu2 Architecture: amd64 Date: Fri Feb 10 01:30:13 2017 ExecutablePath: /lib/systemd/systemd-udevd InstallationDate: Installed on 2017-02-06 (3 days ago) InstallationMedia: Ubuntu-MATE 17.04 "Zesty Zapus" - Alpha amd64 (20170125) MachineType: To Be Filled By O.E.M. To Be Filled By O.E.M. ProcCmdline: /lib/systemd/systemd-udevd ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.9.0-15-generic.efi.signed root=UUID=8b97de22-0e3b-4da0-8676-7c8865800def ro quiet splash vt.handoff=7 Signal: 6 SourcePackage: systemd StacktraceTop: __open_nocancel () at ../sysdeps/unix/syscall-template.S:84 ?? () ?? () ?? () ?? () Title: systemd-udevd crashed with SIGABRT in __open_nocancel() UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: dmi.bios.date: 05/05/2016 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: P1.40 dmi.board.name: A88M-G/3.1 dmi.board.vendor: ASRock dmi.chassis.asset.tag: To Be Filled By O.E.M. dmi.chassis.type: 3 dmi.chassis.vendor: To Be Filled By O.E.M. dmi.chassis.version: To Be Filled By O.E.M. dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrP1.40:bd05/05/2016:svnToBeFilledByO.E.M.:pnToBeFilledByO.E.M.:pvrToBeFilledByO.E.M.:rvnASRock:rnA88M-G/3.1:rvr:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.: dmi.product.name: To Be Filled By O.E.M. dmi.product.version: To Be Filled By O.E.M. dmi.sys.vendor: To Be Filled By O.E.M. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1663421/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1655839] Re: [FTBFS] amd64 build of heimdal 7.1.0+dfsg-9 FAIL: test_rfc3961
That version is now dead http://news.softpedia.com/news/ubuntu-17-04-zesty-zapus-has-reached-end-of-life-upgrade-to-ubuntu-17-10-now-519360.shtml ** Changed in: libtool (Ubuntu) Status: New => Invalid -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to heimdal in Ubuntu. https://bugs.launchpad.net/bugs/1655839 Title: [FTBFS] amd64 build of heimdal 7.1.0+dfsg-9 FAIL: test_rfc3961 Status in heimdal package in Ubuntu: Fix Released Status in libtool package in Ubuntu: Invalid Bug description: A few builds have failed: amd64, ppc64el & s390x for Zesty proposed for example amd64 fails on test_rfc3961 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/heimdal/+bug/1655839/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1665471] Re: unknown, auto pop-up ????
That version is now dead http://news.softpedia.com/news/ubuntu-17-04-zesty-zapus-has-reached-end-of-life-upgrade-to-ubuntu-17-10-now-519360.shtml ** Changed in: hud (Ubuntu) Status: New => Invalid -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to hud in Ubuntu. https://bugs.launchpad.net/bugs/1665471 Title: unknown, auto pop-up Status in hud package in Ubuntu: Invalid Bug description: The message states problem with 17.04, we're not even there yet. This 16.10 version loaded corrupt from the beginning, can't find how to get around it. The initial download came up with a green screen, blew out all OS capability. Found a server version from the UK, it loaded OK. I'm not real savay with terminal applications, however, I got it to work. I would simply like to have a 'stable' OS, like it's always been until this time. Any suggestion would be appreciated. I have desktop on my other machine, but CD writer is missing, and I can't install one. Seems that any download OS I try won't install properly, and I don't know why. I'm waiting for 17.04, but in the meantime, it's very frustrating..and your help 'forums' don'tActually this is even the first time the 'send report' thing has actually worked...I've not had any problems with any version until this. I'm considering downloading 16.04 and starting over, but I'd rather not have to do all that work, as I'm just a 'casual user, and 'basic' OS works just fine for me. Any information, suggestions, etc., would be greatly appreciated...Thank you.. ProblemType: Crash DistroRelease: Ubuntu 17.04 Package: hud 14.10+17.04.20170106.1-0ubuntu1 ProcVersionSignature: Ubuntu 4.9.0-15.16-generic 4.9.5 Uname: Linux 4.9.0-15-generic i686 ApportVersion: 2.20.4-0ubuntu2 Architecture: i386 CurrentDesktop: Unity Date: Thu Feb 16 13:27:43 2017 ExecutablePath: /usr/lib/i386-linux-gnu/hud/hud-service InstallationDate: Installed on 2016-12-22 (55 days ago) InstallationMedia: Ubuntu 16.10 "Yakkety Yak" - Release i386 (20161012.2) ProcCmdline: /usr/lib/i386-linux-gnu/hud/hud-service ProcEnviron: LANG=en_US.UTF-8 LANGUAGE=en_US PATH=(custom, user) SHELL=/bin/bash XDG_RUNTIME_DIR= SegvAnalysis: Segfault happened at: 0xb7730a74:mov$0xa7,%ah PC (0xb7730a74) in non-executable VMA region: 0xb773-0xb7731000 rw-p /lib/i386-linux-gnu/ld-2.24.so source "$0xa7" ok destination "%ah" ok SegvReason: executing writable VMA /lib/i386-linux-gnu/ld-2.24.so Signal: 11 SourcePackage: hud Stacktrace: #0 0xb7730a74 in ?? () No symbol table info available. Backtrace stopped: Cannot access memory at address 0x7 StacktraceTop: ?? () Title: hud-service crashed with SIGSEGV UpgradeStatus: Upgraded to zesty on 2016-12-23 (55 days ago) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/hud/+bug/1665471/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1665700] Re: package udev 232-17ubuntu1 failed to install/upgrade: subprocess installed post-installation script returned error exit status 1
That version is now dead http://news.softpedia.com/news/ubuntu-17-04-zesty-zapus-has-reached-end-of-life-upgrade-to-ubuntu-17-10-now-519360.shtml ** Changed in: systemd (Ubuntu) Status: Confirmed => Invalid -- 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/1665700 Title: package udev 232-17ubuntu1 failed to install/upgrade: subprocess installed post-installation script returned error exit status 1 Status in systemd package in Ubuntu: Invalid Bug description: The failure when performing a sequence of upgrades in terminal mode. ProblemType: Package DistroRelease: Ubuntu 17.04 Package: udev 232-17ubuntu1 ProcVersionSignature: Ubuntu 4.9.0-15.16-generic 4.9.5 Uname: Linux 4.9.0-15-generic i686 ApportVersion: 2.20.4-0ubuntu2 Architecture: i386 Date: Fri Feb 17 15:55:37 2017 ErrorMessage: subprocess installed post-installation script returned error exit status 1 InstallationDate: Installed on 2017-02-05 (11 days ago) InstallationMedia: Ubuntu 17.04 "Zesty Zapus" - Alpha i386 (20170205) Lsusb: Bus 001 Device 002: ID 80ee:0021 VirtualBox USB Tablet Bus 001 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub MachineType: innotek GmbH VirtualBox ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.9.0-15-generic root=UUID=11130cf7-bb23-4b4b-ba3a-abb78fe90b47 ro quiet splash RelatedPackageVersions: dpkg 1.18.10ubuntu1 apt 1.4~beta4ubuntu1 SourcePackage: systemd Title: package udev 232-17ubuntu1 failed to install/upgrade: subprocess installed post-installation script returned error exit status 1 UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 12/01/2006 dmi.bios.vendor: innotek GmbH dmi.bios.version: VirtualBox dmi.board.name: VirtualBox dmi.board.vendor: Oracle Corporation dmi.board.version: 1.2 dmi.chassis.type: 1 dmi.chassis.vendor: Oracle Corporation dmi.modalias: dmi:bvninnotekGmbH:bvrVirtualBox:bd12/01/2006:svninnotekGmbH:pnVirtualBox:pvr1.2:rvnOracleCorporation:rnVirtualBox:rvr1.2:cvnOracleCorporation:ct1:cvr: dmi.product.name: VirtualBox dmi.product.version: 1.2 dmi.sys.vendor: innotek GmbH To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1665700/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1665937] Re: dont know
That version is now dead http://news.softpedia.com/news/ubuntu-17-04-zesty-zapus-has-reached-end-of-life-upgrade-to-ubuntu-17-10-now-519360.shtml ** Changed in: xorg (Ubuntu) Status: New => Invalid -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to xorg in Ubuntu. https://bugs.launchpad.net/bugs/1665937 Title: dont know Status in xorg package in Ubuntu: Invalid Bug description: dont know ProblemType: Bug DistroRelease: Ubuntu 17.04 Package: xorg 1:7.7+13ubuntu4 ProcVersionSignature: Ubuntu 4.8.0-38.41-generic 4.8.17 Uname: Linux 4.8.0-38-generic x86_64 NonfreeKernelModules: wl .tmp.unity_support_test.0: ApportVersion: 2.20.3-0ubuntu8.2 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: Sat Feb 18 23:33:55 2017 DistUpgraded: Fresh install DistroCodename: zesty DistroVariant: ubuntu DkmsStatus: bcmwl, 6.30.223.271+bdcom, 4.8.0-37-generic, x86_64: installed bcmwl, 6.30.223.271+bdcom, 4.8.0-38-generic, x86_64: installed GraphicsCard: Advanced Micro Devices, Inc. [AMD/ATI] Mullins [Radeon R4/R5 Graphics] [1002:9851] (rev 45) (prog-if 00 [VGA controller]) Subsystem: Hewlett-Packard Company Mullins [Radeon R4/R5 Graphics] [103c:80cc] InstallationDate: Installed on 2017-02-05 (13 days ago) InstallationMedia: Ubuntu 16.10 "Yakkety Yak" - Release amd64 (20161012.2) MachineType: HP HP Notebook ProcEnviron: LANGUAGE=it PATH=(custom, no user) LANG=it_IT.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.8.0-38-generic.efi.signed root=UUID=52cfa011-b036-4d70-a659-1b38827257de ro quiet splash vt.handoff=7 SourcePackage: xorg UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 12/01/2015 dmi.bios.vendor: Insyde dmi.bios.version: F.1F dmi.board.asset.tag: Base Board Asset Tag dmi.board.name: 80CC dmi.board.vendor: HP dmi.board.version: 99.45 dmi.chassis.asset.tag: Chassis Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: HP dmi.chassis.version: Chassis Version dmi.modalias: dmi:bvnInsyde:bvrF.1F:bd12/01/2015:svnHP:pnHPNotebook:pvrType1ProductConfigId:rvnHP:rn80CC:rvr99.45:cvnHP:ct10:cvrChassisVersion: dmi.product.name: HP Notebook dmi.product.version: Type1ProductConfigId dmi.sys.vendor: HP version.compiz: compiz 1:0.9.13.0+16.10.20160818.2-0ubuntu2 version.ia32-libs: ia32-libs N/A version.libdrm2: libdrm2 2.4.70-1 version.libgl1-mesa-dri: libgl1-mesa-dri 12.0.6-0ubuntu0.16.10.1 version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A version.libgl1-mesa-glx: libgl1-mesa-glx 12.0.6-0ubuntu0.16.10.1 version.xserver-xorg-core: xserver-xorg-core 2:1.18.4-1ubuntu6.1 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.10.2-1ubuntu1 version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.7.1-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20160706-1ubuntu1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.12-2 xserver.bootTime: Sat Feb 18 20:38:13 2017 xserver.configfile: default xserver.errors: RADEON(G0): [XvMC] Failed to initialize extension. xserver.logfile: /var/log/Xorg.0.log xserver.version: 2:1.18.4-1ubuntu6.1 xserver.video_driver: radeon To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1665937/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1743015] Re: Support for SystemD 236+ in 18.04
SystemD 237-3ubuntu3 is now available in Ubuntu bionci https://bugs.launchpad.net/ubuntu/+source/systemd/237-3ubuntu3 ** Changed in: systemd (Ubuntu) Status: Confirmed => Fix Released -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to systemd in Ubuntu. https://bugs.launchpad.net/bugs/1743015 Title: Support for SystemD 236+ in 18.04 Status in systemd package in Ubuntu: Fix Released Bug description: SystemD 236+ seems to add support for writing to files from unit definitions based on https://github.com/systemd/systemd/pull/7198. This is very helpful when migrating legacy logging integrations from 14.04/upstart which is already writing to separate files. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1743015/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1667659] Re: signon-ui crashed with SIGSEGV in QWindow::show()
That version is now dead http://news.softpedia.com/news/ubuntu-17-04-zesty-zapus-has-reached-end-of-life-upgrade-to-ubuntu-17-10-now-519360.shtml ** Changed in: signon-ui (Ubuntu) Status: Confirmed => Invalid -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to signon-ui in Ubuntu. https://bugs.launchpad.net/bugs/1667659 Title: signon-ui crashed with SIGSEGV in QWindow::show() Status in signon-ui package in Ubuntu: Invalid Bug description: NA ProblemType: Crash DistroRelease: Ubuntu 17.04 Package: signon-ui-x11 0.17+17.04.20161109-0ubuntu1 Uname: Linux 4.10.0-041000-lowlatency x86_64 ApportVersion: 2.20.4-0ubuntu2 Architecture: amd64 CrashCounter: 1 CurrentDesktop: Unity:Unity7 Date: Fri Feb 24 18:45:43 2017 ExecutablePath: /usr/bin/signon-ui InstallationDate: Installed on 2017-02-24 (0 days ago) InstallationMedia: Ubuntu 17.04 "Zesty Zapus" - Alpha amd64 (20170224) ProcCmdline: /usr/bin/signon-ui SegvAnalysis: Segfault happened at: 0x7f5ae5b478de <_ZN7QWindow4showEv+14>:mov 0x8(%rbx),%rax PC (0x7f5ae5b478de) ok source "0x8(%rbx)" (0x0008) not located in a known VMA region (needed readable region)! destination "%rax" ok SegvReason: reading NULL VMA Signal: 11 SourcePackage: signon-ui StacktraceTop: QWindow::show() () from /usr/lib/x86_64-linux-gnu/libQt5Gui.so.5 ?? () ?? () ?? () ?? () Title: signon-ui crashed with SIGSEGV in QWindow::show() UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/signon-ui/+bug/1667659/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1667807] Re: The third 1.10 bug-fix release (1.10.4) was released on 23 February 2017
That version is now dead http://news.softpedia.com/news/ubuntu-17-04-zesty-zapus-has-reached-end-of-life-upgrade-to-ubuntu-17-10-now-519360.shtml ** Changed in: gstreamer1.0 (Ubuntu) Status: New => Invalid -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to gstreamer1.0 in Ubuntu. https://bugs.launchpad.net/bugs/1667807 Title: The third 1.10 bug-fix release (1.10.4) was released on 23 February 2017 Status in gstreamer1.0 package in Ubuntu: Invalid Bug description: https://gstreamer.freedesktop.org/releases/1.10/#1.10.4 ProblemType: Bug DistroRelease: Ubuntu 17.04 Package: libgstreamer1.0-0 1.10.3-1 ProcVersionSignature: Ubuntu 4.10.0-8.10-generic 4.10.0-rc8 Uname: Linux 4.10.0-8-generic x86_64 ApportVersion: 2.20.4-0ubuntu2 Architecture: amd64 CurrentDesktop: GNOME Date: Fri Feb 24 17:50:00 2017 InstallationDate: Installed on 2015-07-26 (579 days ago) InstallationMedia: Ubuntu-GNOME 15.10 "Wily Werewolf" - Alpha amd64 (20150723) SourcePackage: gstreamer1.0 UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gstreamer1.0/+bug/1667807/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1668527] Re: after locking the screen remains black forever.
That version is now dead http://news.softpedia.com/news/ubuntu-17-04-zesty-zapus-has-reached-end-of-life-upgrade-to-ubuntu-17-10-now-519360.shtml ** Changed in: lightdm (Ubuntu) Status: New => Invalid -- 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/1668527 Title: after locking the screen remains black forever. Status in lightdm package in Ubuntu: Invalid Bug description: after locking the screen remains black forever. lsb_release -rd Description: Ubuntu Zesty Zapus (development branch) Release: 17.04 apt-cache policy lightdm lightdm: Installed: 1.21.5-0ubuntu1 Candidate: 1.21.5-0ubuntu1 Version table: *** 1.21.5-0ubuntu1 500 500 http://fi.archive.ubuntu.com/ubuntu zesty/main amd64 Packages 100 /var/lib/dpkg/status ProblemType: Bug DistroRelease: Ubuntu 17.04 Package: lightdm 1.21.5-0ubuntu1 ProcVersionSignature: Ubuntu 4.10.0-8.10-generic 4.10.0-rc8 Uname: Linux 4.10.0-8-generic x86_64 ApportVersion: 2.20.4-0ubuntu2 Architecture: amd64 Date: Tue Feb 28 11:32:13 2017 InstallationDate: Installed on 2014-04-21 (1043 days ago) InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Release amd64 (20140417) SourcePackage: lightdm UpgradeStatus: No upgrade log present (probably fresh install) mtime.conffile..etc.pam.d.lightdm: 2016-04-16T15:45:25.000214 mtime.conffile..etc.pam.d.lightdm-greeter: 2016-04-16T15:45:05.232214 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/lightdm/+bug/1668527/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1668679] Re: indicator-network-secret-agent crashed with SIGSEGV in do_lookup_x()
That version is now dead http://news.softpedia.com/news/ubuntu-17-04-zesty-zapus-has-reached-end-of-life-upgrade-to-ubuntu-17-10-now-519360.shtml ** Changed in: indicator-network (Ubuntu) Status: Confirmed => Invalid -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to indicator-network in Ubuntu. https://bugs.launchpad.net/bugs/1668679 Title: indicator-network-secret-agent crashed with SIGSEGV in do_lookup_x() Status in indicator-network package in Ubuntu: Invalid Bug description: One of 3 bugs poppedout after xorg`s crash (when unity8 starting) (And then re/startx was needed) ProblemType: Crash DistroRelease: Ubuntu 17.04 Package: indicator-network 0.9.0+17.04.20170116-0ubuntu1 ProcVersionSignature: Ubuntu 4.10.0-8.10-generic 4.10.0-rc8 Uname: Linux 4.10.0-8-generic i686 ApportVersion: 2.20.4-0ubuntu2 Architecture: i386 CurrentDesktop: Unity:Unity8 Date: Tue Feb 28 16:10:27 2017 ExecutablePath: /usr/lib/i386-linux-gnu/indicator-network/indicator-network-secret-agent ExecutableTimestamp: 1484574095 InstallationDate: Installed on 2015-09-22 (525 days ago) InstallationMedia: Ubuntu 14.04.3 LTS "Trusty Tahr" - Beta i386 (20150917) ProcCmdline: /usr/lib/i386-linux-gnu/indicator-network/indicator-network-secret-agent ProcCwd: /home/ytrew8 ProcEnviron: LANGUAGE=pl_PL PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=pl_PL.UTF-8 SHELL=/bin/bash SegvAnalysis: Segfault happened at: 0xb7746eba : mov0x4(%eax),%ebx PC (0xb7746eba) ok source "0x4(%eax)" (0x03ec) not located in a known VMA region (needed readable region)! destination "%ebx" ok SegvReason: reading NULL VMA Signal: 11 SourcePackage: indicator-network Stacktrace: #0 do_lookup_x (undef_name=0x0, new_hash=1, old_hash=0xbfbe816b, ref=0x0, result=0x1fa1, scope=0x3e8, i=152, version=0xb7746e30 , flags=-1226508230, skip=0xb72ec8ba, type_class=0, undef_map=0x5b) at dl-lookup.c:361 n = list = #1 0x in ?? () No symbol table info available. StacktraceTop: do_lookup_x (undef_name=0x0, new_hash=1, old_hash=0xbfbe816b, ref=0x0, result=0x1fa1, scope=0x3e8, i=152, version=0xb7746e30 , flags=-1226508230, skip=0xb72ec8ba, type_class=0, undef_map=0x5b) at dl-lookup.c:361 ?? () Title: indicator-network-secret-agent crashed with SIGSEGV in do_lookup_x() UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip libvirt libvirtd lpadmin plugdev sambashare sudo To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/indicator-network/+bug/1668679/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1668485] Re: Xorg intel blank screen
That version is now dead http://news.softpedia.com/news/ubuntu-17-04-zesty-zapus-has-reached-end-of-life-upgrade-to-ubuntu-17-10-now-519360.shtml ** Changed in: xserver-xorg-video-intel (Ubuntu) Status: New => Invalid ** Changed in: xorg (Ubuntu) Status: New => Invalid -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to xorg in Ubuntu. https://bugs.launchpad.net/bugs/1668485 Title: Xorg intel blank screen Status in xorg package in Ubuntu: Invalid Status in xserver-xorg-video-intel package in Ubuntu: Invalid Bug description: I have an Hybrid graphics card, my lspci output for then is: 00:02.0 VGA compatible controller: Intel Corporation HD Graphics 530 (rev 06) 02:00.0 3D controller: NVIDIA Corporation GM107M [GeForce GTX 960M] (rev a2) Once installed nvidia drivre, things work fine (instead they don't with noveau). But my problem is using intel driver. This is parte of my xorg.conf for nvidia (complete file is attached). Section "ServerLayout" Identifier "layout" Screen 0 "nvidia" Inactive "intel" EndSection I have installed xserver-xorg-video-intel and just change xorg.conf Section "ServerLayout" Identifier "layout" Screen 0 "intel" Inactive "nvidia" EndSection this way, when restarting, I get frozen blank screen while booting, and can't do anything other than pressing the power button and and reboot. So, I have to start in recovery mode, only way I can work in terminal, and change xorg. ProblemType: Bug DistroRelease: Ubuntu 17.04 Package: xorg 1:7.7+16ubuntu2 ProcVersionSignature: Ubuntu 4.10.0-8.10-generic 4.10.0-rc8 Uname: Linux 4.10.0-8-generic x86_64 NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia ApportVersion: 2.20.4-0ubuntu2 Architecture: amd64 CurrentDesktop: KDE Date: Tue Feb 28 00:33:16 2017 InstallationDate: Installed on 2017-02-15 (12 days ago) InstallationMedia: Kubuntu 17.04 "Zesty Zapus" - Alpha amd64 (20170125.3) SourcePackage: xorg UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1668485/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1669643] Re: Wifi WPA2-PSK 4-Way Handshake Faliure
That version is now dead http://news.softpedia.com/news/ubuntu-17-04-zesty-zapus-has-reached-end-of-life-upgrade-to-ubuntu-17-10-now-519360.shtml ** Changed in: wpa (Ubuntu) Status: New => Invalid -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to wpa in Ubuntu. https://bugs.launchpad.net/bugs/1669643 Title: Wifi WPA2-PSK 4-Way Handshake Faliure Status in wpa package in Ubuntu: Invalid Bug description: After I upgraded to Ubuntu 17.04 yesterday, I started having this problem. My device will only connect to unsecured (public) WiFi networks. I tried booting into an older series kernel (4.8.0) and the issue persisted. I ran `sudo systemctl status network-manager` and got this: device (wlx501ac505fcbc): supplicant interface state: associating -> 4-way handshake sup-iface[0x55eb41e5bc20,wlx501ac505fcbc]: connection disconnected (reason 15) device (wlx501ac505fcbc): supplicant interface state: 4-way handshake -> disconnected device (wlx501ac505fcbc): Activation: (wifi) disconnected during association, asking for new key device (wlx501ac505fcbc): state change: config -> need-auth (reason 'supplicant-disconnect') [50 60 8] device (wlx501ac505fcbc): supplicant interface state: disconnected -> inactive ProblemType: Bug DistroRelease: Ubuntu 17.04 Package: network-manager 1.4.4-1ubuntu2 ProcVersionSignature: Ubuntu 4.10.0-11.13-generic 4.10.1 Uname: Linux 4.10.0-11-generic x86_64 ApportVersion: 2.20.4-0ubuntu2 Architecture: amd64 CurrentDesktop: GNOME Date: Thu Mar 2 20:55:59 2017 IfupdownConfig: # interfaces(5) file used by ifup(8) and ifdown(8) auto lo iface lo inet loopback InstallationDate: Installed on 2017-01-04 (58 days ago) InstallationMedia: Ubuntu-GNOME 16.10 "Yakkety Yak" - Release amd64 (20161012.1) IpRoute: default via 192.168.42.129 dev enp0s20u2 proto static metric 100 169.254.0.0/16 dev enp0s20u2 scope link metric 1000 192.168.42.0/24 dev enp0s20u2 proto kernel scope link src 192.168.42.246 metric 100 NetworkManager.conf: [main] plugins=ifupdown,keyfile [ifupdown] managed=false NetworkManager.state: [main] NetworkingEnabled=true WirelessEnabled=true WWANEnabled=true PciNetwork: ProcEnviron: PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: network-manager UpgradeStatus: No upgrade log present (probably fresh install) nmcli-dev: DEVICE TYPE STATE DBUS-PATH CONNECTION CON-UUID CON-PATH enp0s20u2 ethernet connected /org/freedesktop/NetworkManager/Devices/4 Wired connection 1 474aac38-e4d8-4102-b2eb-c5cc6bdb17aa /org/freedesktop/NetworkManager/ActiveConnection/1 AC:37:43:7C:B4:57 btdisconnected /org/freedesktop/NetworkManager/Devices/3 -- -- -- wlx501ac505fcbcwifi disconnected /org/freedesktop/NetworkManager/Devices/2 -- -- -- lo loopback unmanaged /org/freedesktop/NetworkManager/Devices/0 -- -- -- nmcli-nm: RUNNING VERSION STATE STARTUP CONNECTIVITY NETWORKING WIFI-HW WIFI WWAN-HW WWAN running 1.4.4connected started full enabled enabled enabled enabled enabled To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/wpa/+bug/1669643/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1670432] Re: Xorg freeze
That version is now dead http://news.softpedia.com/news/ubuntu-17-04-zesty-zapus-has-reached-end-of-life-upgrade-to-ubuntu-17-10-now-519360.shtml ** Changed in: xorg (Ubuntu) Status: New => Invalid -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to xorg in Ubuntu. https://bugs.launchpad.net/bugs/1670432 Title: Xorg freeze Status in xorg package in Ubuntu: Invalid Bug description: Freezes the computer in the log in and also when entering the screen saver. ProblemType: Bug DistroRelease: Ubuntu 17.04 Package: xorg 1:7.7+16ubuntu2 ProcVersionSignature: Ubuntu 4.10.0-9.11-generic 4.10.0 Uname: Linux 4.10.0-9-generic x86_64 .tmp.unity_support_test.0: ApportVersion: 2.20.4-0ubuntu2 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: Mon Mar 6 14:13:14 2017 DistUpgraded: Fresh install DistroCodename: zesty DistroVariant: ubuntu DkmsStatus: virtualbox, 5.1.14, 4.10.0-9-generic, x86_64: installed ExtraDebuggingInterest: Yes, if not too technical GpuHangFrequency: Several times a day GpuHangReproducibility: Occurs more often under certain circumstances GpuHangStarted: Since before I upgraded GraphicsCard: NVIDIA Corporation GT218 [GeForce 210] [10de:0a65] (rev a2) (prog-if 00 [VGA controller]) Subsystem: ZOTAC International (MCO) Ltd. GT218 [GeForce 210] [19da:7222] InstallationDate: Installed on 2015-07-06 (608 days ago) InstallationMedia: Ubuntu 15.04 "Vivid Vervet" - Release amd64 (20150422) MachineType: Gigabyte Technology Co., Ltd. To be filled by O.E.M. ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.10.0-9-generic root=UUID=5898c70a-eebd-44a1-b634-56c69c8a4914 ro quiet splash vt.handoff=7 SourcePackage: xorg Symptom: display Title: Xorg freeze UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 02/25/2013 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: FC dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: H61M-S1 dmi.board.vendor: Gigabyte Technology Co., Ltd. dmi.board.version: x.x dmi.chassis.asset.tag: To Be Filled By O.E.M. dmi.chassis.type: 3 dmi.chassis.vendor: Gigabyte Technology Co., Ltd. dmi.chassis.version: To Be Filled By O.E.M. dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrFC:bd02/25/2013:svnGigabyteTechnologyCo.,Ltd.:pnTobefilledbyO.E.M.:pvrTobefilledbyO.E.M.:rvnGigabyteTechnologyCo.,Ltd.:rnH61M-S1:rvrx.x:cvnGigabyteTechnologyCo.,Ltd.:ct3:cvrToBeFilledByO.E.M.: dmi.product.name: To be filled by O.E.M. dmi.product.version: To be filled by O.E.M. dmi.sys.vendor: Gigabyte Technology Co., Ltd. version.compiz: compiz 1:0.9.13.1+17.04.20170109-0ubuntu1 version.ia32-libs: ia32-libs N/A version.libdrm2: libdrm2 2.4.75-1 version.libgl1-mesa-dri: libgl1-mesa-dri 13.0.4-1ubuntu1 version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A version.libgl1-mesa-glx: libgl1-mesa-glx 13.0.4-1ubuntu1 version.xserver-xorg-core: xserver-xorg-core 2:1.18.4-1ubuntu9 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.10.2-1ubuntu1 version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.8.0-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20160706-1ubuntu1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.13-1 xserver.bootTime: Mon Mar 6 13:21:05 2017 xserver.configfile: default xserver.errors: Failed to load module "nvidia" (module does not exist, 0) Failed to load module "nvidia" (module does not exist, 0) xserver.logfile: /var/log/Xorg.0.log xserver.version: 2:1.18.4-1ubuntu9 xserver.video_driver: nouveau To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1670432/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1671980] Re: NA
That version is now dead http://news.softpedia.com/news/ubuntu-17-04-zesty-zapus-has-reached-end-of-life-upgrade-to-ubuntu-17-10-now-519360.shtml ** Changed in: xorg (Ubuntu) Status: New => Invalid -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to xorg in Ubuntu. https://bugs.launchpad.net/bugs/1671980 Title: NA Status in xorg package in Ubuntu: Invalid Bug description: NA ProblemType: Bug DistroRelease: Ubuntu 17.04 Package: xorg 1:7.7+16ubuntu2 Uname: Linux 4.11.0-041100rc1-lowlatency x86_64 .tmp.unity_support_test.0: ApportVersion: 2.20.4-0ubuntu2 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:Unity7 Date: Sat Mar 11 08:42:10 2017 DistUpgraded: Fresh install DistroCodename: zesty DistroVariant: ubuntu GraphicsCard: Intel Corporation Atom Processor Z36xxx/Z37xxx Series Graphics & Display [8086:0f31] (rev 0e) (prog-if 00 [VGA controller]) Subsystem: Acer Incorporated [ALI] Atom Processor Z36xxx/Z37xxx Series Graphics & Display [1025:0933] InstallationDate: Installed on 2017-02-24 (14 days ago) InstallationMedia: Ubuntu 17.04 "Zesty Zapus" - Alpha amd64 (20170224) Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 003: ID 04f2:b469 Chicony Electronics Co., Ltd Bus 001 Device 004: ID 1d57:0001 Xenta Bus 001 Device 002: ID 05e3:0608 Genesys Logic, Inc. Hub Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: Acer Aspire ES1-111M ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.11.0-041100rc1-lowlatency root=UUID=2cbb00b6-fbd7-4e61-9dff-2469ff2e5569 ro quiet splash vt.handoff=7 SourcePackage: xorg UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 07/22/2014 dmi.bios.vendor: Insyde Corp. dmi.bios.version: V1.03 dmi.board.asset.tag: Type2 - Board Asset Tag dmi.board.name: R2 dmi.board.vendor: Acer dmi.board.version: Type2 - A01 Board Version dmi.chassis.type: 10 dmi.chassis.vendor: Chassis Manufacturer dmi.chassis.version: Chassis Version dmi.modalias: dmi:bvnInsydeCorp.:bvrV1.03:bd07/22/2014:svnAcer:pnAspireES1-111M:pvrV1.03:rvnAcer:rnR2:rvrType2-A01BoardVersion:cvnChassisManufacturer:ct10:cvrChassisVersion: dmi.product.name: Aspire ES1-111M dmi.product.version: V1.03 dmi.sys.vendor: Acer version.compiz: compiz 1:0.9.13.1+17.04.20170109-0ubuntu1 version.ia32-libs: ia32-libs N/A version.libdrm2: libdrm2 2.4.75-1 version.libgl1-mesa-dri: libgl1-mesa-dri 17.0.0-1ubuntu1 version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A version.libgl1-mesa-glx: libgl1-mesa-glx 17.0.0-1ubuntu1 version.xserver-xorg-core: xserver-xorg-core 2:1.18.4-1ubuntu9 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.8.0-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20160706-1ubuntu1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.13-1 xserver.bootTime: Sat Mar 11 08:19:55 2017 xserver.configfile: default xserver.errors: xserver.logfile: /var/log/Xorg.0.log xserver.version: 2:1.18.4-1ubuntu9 xserver.video_driver: modeset To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1671980/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1672468] Re: Problema na reinicialização
That version is now dead http://news.softpedia.com/news/ubuntu-17-04-zesty-zapus-has-reached-end-of-life-upgrade-to-ubuntu-17-10-now-519360.shtml ** Changed in: xorg (Ubuntu) Status: New => Invalid -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to xorg in Ubuntu. https://bugs.launchpad.net/bugs/1672468 Title: Problema na reinicialização Status in xorg package in Ubuntu: Invalid Bug description: Quando eu faço a reinicialização do sistema, geralmente da problema não reconhecendo a rede wi-fi, e, tenho que reiniciar o sistema novamente. quando isso acontece, ele não reconhece o teclado e tenho que dá um resete, é quando ele reconhece o teclado novamente e tenho que corrigir erro para poder entrar no sistema, isso só acontece no disktop. Já vinha acontecendo no 16.04 e incrível que pareça no 15.04!!! por favor me ajudem qual a melhor configuração para o teclado, pois não reconhece todas as teclas, tento da um print no botão do teclado e não funciona, só consigo da print com o mause ou rato indo no menu e clicando em captura de tela. ProblemType: Bug DistroRelease: Ubuntu 17.04 Package: xorg 1:7.7+16ubuntu2 ProcVersionSignature: Ubuntu 4.10.0-13.15-generic 4.10.1 Uname: Linux 4.10.0-13-generic x86_64 ApportVersion: 2.20.4-0ubuntu2 Architecture: amd64 Date: Mon Mar 13 14:43:34 2017 DistroCodename: zesty DistroVariant: ubuntu InstallationDate: Installed on 2017-03-03 (9 days ago) InstallationMedia: Ubuntu-Budgie 17.04 "Zesty Zapus" - Alpha amd64 (20170219) ProcEnviron: LANGUAGE=pt_BR:pt:en PATH=(custom, no user) LANG=pt_BR.UTF-8 SHELL=/bin/bash SourcePackage: xorg UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1672468/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1672537] Re: Too many dependencies for GtkInspector
That version is now dead http://news.softpedia.com/news/ubuntu-17-04-zesty-zapus-has-reached-end-of-life-upgrade-to-ubuntu-17-10-now-519360.shtml ** Changed in: gtk+3.0 (Ubuntu) Status: New => Invalid -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to gtk+3.0 in Ubuntu. https://bugs.launchpad.net/bugs/1672537 Title: Too many dependencies for GtkInspector Status in gtk+3.0 package in Ubuntu: Invalid Bug description: I want to use GtkInspector in my GTK development through GObject Introspection in Python. So I need to enable the GtkInspector: $ gsettings set org.gtk.Settings.Debug enable-inspector-keybinding true No such schema 'org.gtk.Settings.Debug' Apparently I need the 'libgtk-3-dev' package. $ sudo apt-get install libgtk-3-dev Reading package lists... Done Building dependency tree Reading state information... Done The following additional packages will be installed: gir1.2-gtk-3.0 icu-devtools libatk-bridge2.0-dev libatk1.0-dev libatspi2.0-dev libcairo2-dev libcontent-hub-glib-dev libcontent-hub-glib0 libdrm-dev libegl1-mesa-dev libepoxy-dev libfontconfig1-dev libfreetype6-dev libgail-3-0 libgdk-pixbuf2.0-dev libglib2.0-dev libglib2.0-dev-bin libgraphite2-dev libgtk-3-0 libgtk-3-common libharfbuzz-dev libharfbuzz-gobject0 libice-dev libicu-dev libmirclient-dev libmircommon-dev libmircookie-dev libmircore-dev libpango1.0-dev libpcre3-dev libpcrecpp0v5 libpixman-1-dev libpng-dev libpng-tools libprotobuf-dev libpthread-stubs0-dev libsm-dev libwayland-bin libwayland-dev libx11-dev libx11-doc libx11-xcb-dev libxau-dev libxcb-dri2-0-dev libxcb-dri3-dev libxcb-glx0-dev libxcb-present-dev libxcb-randr0-dev libxcb-render0-dev libxcb-shape0-dev libxcb-shm0-dev libxcb-sync-dev libxcb-xfixes0-dev libxcb1-dev libxcomposite-dev libxcursor-dev libxdamage-dev libxdmcp-dev libxext-dev libxfixes-dev libxft-dev libxi-dev libxinerama-dev libxkbcommon-dev libxrandr-dev libxrender-dev libxshmfence-dev libxtst-dev libxxf86vm-dev wayland-protocols x11proto-composite-dev x11proto-core-dev x11proto-damage-dev x11proto-dri2-dev x11proto-fixes-dev x11proto-gl-dev x11proto-input-dev x11proto-kb-dev x11proto-randr-dev x11proto-record-dev x11proto-render-dev x11proto-xext-dev x11proto-xf86vidmode-dev x11proto-xinerama-dev xorg-sgml-doctools xtrans-dev zlib1g-dev It wants to pull in 84 new packages. This seems like excessive coupling. I have no interest in compiling anything from source, all I want is to use the GtkInspector. ProblemType: Bug DistroRelease: Ubuntu 17.04 Package: libgtk-3-dev (not installed) ProcVersionSignature: Ubuntu 4.10.0-11.13-generic 4.10.1 Uname: Linux 4.10.0-11-generic x86_64 ApportVersion: 2.20.4-0ubuntu2 Architecture: amd64 CurrentDesktop: GNOME-Classic:GNOME Date: Mon Mar 13 22:03:39 2017 InstallationDate: Installed on 2013-12-26 (1172 days ago) InstallationMedia: Ubuntu 13.10 "Saucy Salamander" - Release amd64 (20131016.1) SourcePackage: gtk+3.0 UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gtk+3.0/+bug/1672537/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1673203] Re: computer suspend test
That version is now dead http://news.softpedia.com/news/ubuntu-17-04-zesty-zapus-has-reached-end-of-life-upgrade-to-ubuntu-17-10-now-519360.shtml ** Changed in: xorg (Ubuntu) Status: New => Invalid -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to xorg in Ubuntu. https://bugs.launchpad.net/bugs/1673203 Title: computer suspend test Status in xorg package in Ubuntu: Invalid Bug description: it did not pass the test. ProblemType: Bug DistroRelease: Ubuntu 17.04 Package: xorg 1:7.7+16ubuntu2 Uname: Linux 4.10.3-041003-generic x86_64 NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia .proc.driver.nvidia.gpus..03.00.0: Error: [Errno 21] Is a directory: '/proc/driver/nvidia/gpus/:03:00.0' .proc.driver.nvidia.gpus..04.00.0: Error: [Errno 21] Is a directory: '/proc/driver/nvidia/gpus/:04:00.0' .proc.driver.nvidia.gpus..07.00.0: Error: [Errno 21] Is a directory: '/proc/driver/nvidia/gpus/:07:00.0' .proc.driver.nvidia.gpus..08.00.0: Error: [Errno 21] Is a directory: '/proc/driver/nvidia/gpus/:08:00.0' .proc.driver.nvidia.registry: Binary: "" .proc.driver.nvidia.version: NVRM version: NVIDIA UNIX x86_64 Kernel Module 378.13 Tue Feb 7 20:10:06 PST 2017 GCC version: gcc version 6.3.0 20170221 (Ubuntu 6.3.0-8ubuntu1) .proc.driver.nvidia.warnings.fbdev: Your system is not currently configured to drive a VGA console on the primary VGA device. The NVIDIA Linux graphics driver requires the use of a text-mode VGA console. Use of other console drivers including, but not limited to, vesafb, may result in corruption and stability problems, and is not supported. .tmp.unity_support_test.0: ApportVersion: 2.20.4-0ubuntu2 Architecture: amd64 BootLog: CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: compiz CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0' CompositorUnredirectFSW: true Date: Wed Mar 15 20:47:35 2017 DistUpgraded: Fresh install DistroCodename: zesty DistroVariant: ubuntu DkmsStatus: bbswitch, 0.8, 4.10.0-11-generic, x86_64: installed bbswitch, 0.8, 4.10.3-041003-generic, x86_64: installed nvidia-378, 378.13, 4.10.0-11-generic, x86_64: installed nvidia-378, 378.13, 4.10.3-041003-generic, x86_64: installed InstallationDate: Installed on 2017-03-14 (1 days ago) InstallationMedia: Ubuntu 17.04 "Zesty Zapus" - Alpha amd64 (20170313) MachineType: ASUS All Series ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.10.3-041003-generic root=UUID=7a6125bf-be4d-4307-8e61-4b93c1566ea0 ro quiet splash vt.handoff=7 SourcePackage: xorg UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 08/18/2016 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 3402 dmi.board.asset.tag: Default string dmi.board.name: X99-A dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: Rev 1.xx dmi.chassis.asset.tag: Default string dmi.chassis.type: 3 dmi.chassis.vendor: Default string dmi.chassis.version: Default string dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr3402:bd08/18/2016:svnASUS:pnAllSeries:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnX99-A:rvrRev1.xx:cvnDefaultstring:ct3:cvrDefaultstring: dmi.product.name: All Series dmi.product.version: System Version dmi.sys.vendor: ASUS version.compiz: compiz 1:0.9.13.1+17.04.20170109-0ubuntu1 version.ia32-libs: ia32-libs N/A version.libdrm2: libdrm2 2.4.75-1ubuntu1 version.libgl1-mesa-dri: libgl1-mesa-dri 13.0.4-1ubuntu1 version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A version.libgl1-mesa-glx: libgl1-mesa-glx 13.0.4-1ubuntu1 version.nvidia-graphics-drivers: nvidia-graphics-drivers-* N/A version.xserver-xorg-core: xserver-xorg-core 2:1.18.4-1ubuntu9 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.8.0-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20160706-1ubuntu1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.13-1 xserver.bootTime: Wed Mar 15 20:45:54 2017 xserver.configfile: /etc/X11/xorg.conf xserver.errors: xserver.logfile: /var/log/Xorg.0.log xserver.outputs: xserver.version: 2:1.18.4-1ubuntu9 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1673203/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1751547] [NEW] Bionic freeze at power off
Public bug reported: Hi, I give try of ubuntu bionic 18.04 lts yesterday, once press power off button the screen freeze and not turn off, tested on Lenovo thinkpad p71 ** Affects: indicator-power (Ubuntu) Importance: Undecided Status: New ** Tags: bionic -- 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/1751547 Title: Bionic freeze at power off Status in indicator-power package in Ubuntu: New Bug description: Hi, I give try of ubuntu bionic 18.04 lts yesterday, once press power off button the screen freeze and not turn off, tested on Lenovo thinkpad p71 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/indicator-power/+bug/1751547/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1671802] Re: package humanity-icon-theme 0.6.10 failed to install/upgrade: package humanity-icon-theme is not ready for configuration cannot configure (current status 'half-insta
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: humanity-icon-theme (Ubuntu) Status: New => Confirmed -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to humanity-icon-theme in Ubuntu. https://bugs.launchpad.net/bugs/1671802 Title: package humanity-icon-theme 0.6.10 failed to install/upgrade: package humanity-icon-theme is not ready for configuration cannot configure (current status 'half-installed') Status in humanity-icon-theme package in Ubuntu: Confirmed Bug description: I am not able to install anything because of this ProblemType: Package DistroRelease: Ubuntu 16.04 Package: humanity-icon-theme 0.6.10 ProcVersionSignature: Ubuntu 4.4.0-59.80-generic 4.4.35 Uname: Linux 4.4.0-59-generic x86_64 ApportVersion: 2.20.1-0ubuntu2.5 AptOrdering: network-manager-openvpn: Install humanity-icon-theme: Configure network-manager-openvpn: Configure NULL: ConfigurePending Architecture: amd64 Date: Wed Mar 8 16:56:37 2017 DuplicateSignature: package:humanity-icon-theme:0.6.10 Processing triggers for dbus (1.10.6-1ubuntu3.3) ... dpkg: error processing package humanity-icon-theme (--configure): package humanity-icon-theme is not ready for configuration ErrorMessage: package humanity-icon-theme is not ready for configuration cannot configure (current status 'half-installed') InstallationDate: Installed on 2016-11-11 (118 days ago) InstallationMedia: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 (20160719) PackageArchitecture: all RelatedPackageVersions: dpkg 1.18.4ubuntu1.1 apt 1.2.19 SourcePackage: humanity-icon-theme Title: package humanity-icon-theme 0.6.10 failed to install/upgrade: package humanity-icon-theme is not ready for configuration cannot configure (current status 'half-installed') UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/humanity-icon-theme/+bug/1671802/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp