[Touch-packages] [Bug 1801871] [NEW] package apparmor 2.12-4ubuntu5.1 failed to install/upgrade: package is in a very bad inconsistent state; you should reinstall it before attempting configuration
Public bug reported: Problem detected while installing docker. ProblemType: Package DistroRelease: Ubuntu 18.04 Package: apparmor 2.12-4ubuntu5.1 ProcVersionSignature: Ubuntu 4.15.0-34.37-generic 4.15.18 Uname: Linux 4.15.0-34-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.2 AptOrdering: apt-transport-https:amd64: Install NULL: ConfigurePending Architecture: amd64 Date: Tue Nov 6 12:53:18 2018 DpkgHistoryLog: Start-Date: 2018-11-06 12:53:18 Commandline: apt-get install apt-transport-https ca-certificates Requested-By: pheonix (1000) Install: apt-transport-https:amd64 (1.6.3ubuntu0.1) DuplicateSignature: package:apparmor:2.12-4ubuntu5.1 Setting up apt-transport-https (1.6.3ubuntu0.1) ... dpkg: error processing package apparmor (--configure): package is in a very bad inconsistent state; you should ErrorMessage: package is in a very bad inconsistent state; you should reinstall it before attempting configuration InstallationDate: Installed on 2018-05-28 (161 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426) KernLog: ProcKernelCmdline: BOOT_IMAGE=/vmlinuz-4.15.0-34-generic root=UUID=75a7c2c0-5434-4b80-8a3e-40b17cebdfda ro quiet splash vt.handoff=1 Python3Details: /usr/bin/python3.6, Python 3.6.5, python3-minimal, 3.6.5-3 PythonDetails: /usr/bin/python2.7, Python 2.7.15rc1, python-minimal, 2.7.15~rc1-1 RelatedPackageVersions: dpkg 1.19.0.5ubuntu2 apt 1.6.3ubuntu0.1 SourcePackage: apparmor Syslog: Title: package apparmor 2.12-4ubuntu5.1 failed to install/upgrade: package is in a very bad inconsistent state; you should reinstall it before attempting configuration UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: apparmor (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 apparmor in Ubuntu. https://bugs.launchpad.net/bugs/1801871 Title: package apparmor 2.12-4ubuntu5.1 failed to install/upgrade: package is in a very bad inconsistent state; you should reinstall it before attempting configuration Status in apparmor package in Ubuntu: New Bug description: Problem detected while installing docker. ProblemType: Package DistroRelease: Ubuntu 18.04 Package: apparmor 2.12-4ubuntu5.1 ProcVersionSignature: Ubuntu 4.15.0-34.37-generic 4.15.18 Uname: Linux 4.15.0-34-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.2 AptOrdering: apt-transport-https:amd64: Install NULL: ConfigurePending Architecture: amd64 Date: Tue Nov 6 12:53:18 2018 DpkgHistoryLog: Start-Date: 2018-11-06 12:53:18 Commandline: apt-get install apt-transport-https ca-certificates Requested-By: pheonix (1000) Install: apt-transport-https:amd64 (1.6.3ubuntu0.1) DuplicateSignature: package:apparmor:2.12-4ubuntu5.1 Setting up apt-transport-https (1.6.3ubuntu0.1) ... dpkg: error processing package apparmor (--configure): package is in a very bad inconsistent state; you should ErrorMessage: package is in a very bad inconsistent state; you should reinstall it before attempting configuration InstallationDate: Installed on 2018-05-28 (161 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426) KernLog: ProcKernelCmdline: BOOT_IMAGE=/vmlinuz-4.15.0-34-generic root=UUID=75a7c2c0-5434-4b80-8a3e-40b17cebdfda ro quiet splash vt.handoff=1 Python3Details: /usr/bin/python3.6, Python 3.6.5, python3-minimal, 3.6.5-3 PythonDetails: /usr/bin/python2.7, Python 2.7.15rc1, python-minimal, 2.7.15~rc1-1 RelatedPackageVersions: dpkg 1.19.0.5ubuntu2 apt 1.6.3ubuntu0.1 SourcePackage: apparmor Syslog: Title: package apparmor 2.12-4ubuntu5.1 failed to install/upgrade: package is in a very bad inconsistent state; you should reinstall it before attempting configuration UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apparmor/+bug/1801871/+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 1801871] Re: package apparmor 2.12-4ubuntu5.1 failed to install/upgrade: package is in a very bad inconsistent state; you should reinstall it before attempting configuration
** Tags removed: need-duplicate-check -- 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/1801871 Title: package apparmor 2.12-4ubuntu5.1 failed to install/upgrade: package is in a very bad inconsistent state; you should reinstall it before attempting configuration Status in apparmor package in Ubuntu: New Bug description: Problem detected while installing docker. ProblemType: Package DistroRelease: Ubuntu 18.04 Package: apparmor 2.12-4ubuntu5.1 ProcVersionSignature: Ubuntu 4.15.0-34.37-generic 4.15.18 Uname: Linux 4.15.0-34-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.2 AptOrdering: apt-transport-https:amd64: Install NULL: ConfigurePending Architecture: amd64 Date: Tue Nov 6 12:53:18 2018 DpkgHistoryLog: Start-Date: 2018-11-06 12:53:18 Commandline: apt-get install apt-transport-https ca-certificates Requested-By: pheonix (1000) Install: apt-transport-https:amd64 (1.6.3ubuntu0.1) DuplicateSignature: package:apparmor:2.12-4ubuntu5.1 Setting up apt-transport-https (1.6.3ubuntu0.1) ... dpkg: error processing package apparmor (--configure): package is in a very bad inconsistent state; you should ErrorMessage: package is in a very bad inconsistent state; you should reinstall it before attempting configuration InstallationDate: Installed on 2018-05-28 (161 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426) KernLog: ProcKernelCmdline: BOOT_IMAGE=/vmlinuz-4.15.0-34-generic root=UUID=75a7c2c0-5434-4b80-8a3e-40b17cebdfda ro quiet splash vt.handoff=1 Python3Details: /usr/bin/python3.6, Python 3.6.5, python3-minimal, 3.6.5-3 PythonDetails: /usr/bin/python2.7, Python 2.7.15rc1, python-minimal, 2.7.15~rc1-1 RelatedPackageVersions: dpkg 1.19.0.5ubuntu2 apt 1.6.3ubuntu0.1 SourcePackage: apparmor Syslog: Title: package apparmor 2.12-4ubuntu5.1 failed to install/upgrade: package is in a very bad inconsistent state; you should reinstall it before attempting configuration UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apparmor/+bug/1801871/+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 1754693] Re: Xwayland crashed with SIGABRT in st_renderbuffer_delete() [often when running Skype or Slack snaps]
Now tracking in both: https://errors.ubuntu.com/problem/01a80d2110a46f6b6d857ce814079646e695f4ca https://errors.ubuntu.com/problem/a1e7fe67e388164abd73462b322cb79ac2773fae ** Description changed: https://errors.ubuntu.com/problem/01a80d2110a46f6b6d857ce814079646e695f4ca + https://errors.ubuntu.com/problem/a1e7fe67e388164abd73462b322cb79ac2773fae --- Steps to reproduce: Install 'slack' snap: sudo snap install slack --classic Run slack: slack Instacrash. ProblemType: Crash DistroRelease: Ubuntu 18.04 Package: xwayland 2:1.19.6-1ubuntu2 ProcVersionSignature: Ubuntu 4.15.0-10.11-generic 4.15.3 Uname: Linux 4.15.0-10-generic x86_64 .tmp.unity_support_test.0: ApportVersion: 2.20.8-0ubuntu10 Architecture: amd64 CompizPlugins: [core,composite,opengl,decor,mousepoll,grid,vpswitch,compiztoolbox,imgpng,gnomecompat,regex,move,place,resize,snap,unitymtgrabhandles,wall,animation,session,expo,workarounds,fade,ezoom,scale,unityshell] CompositorRunning: None CurrentDesktop: GNOME Date: Fri Mar 9 10:31:06 2018 DistUpgraded: 2018-03-06 13:58:47,853 DEBUG Running PostInstallScript: './xorg_fix_proprietary.py' DistroCodename: bionic DistroVariant: ubuntu EcryptfsInUse: Yes ExecutablePath: /usr/bin/Xwayland ExtraDebuggingInterest: Yes, including running git bisection searches GraphicsCard: Intel Corporation Xeon E3-1200 v3/4th Gen Core Processor Integrated Graphics Controller [8086:0412] (rev 06) (prog-if 00 [VGA controller]) Subsystem: ASUSTeK Computer Inc. Xeon E3-1200 v3/4th Gen Core Processor Integrated Graphics Controller [1043:8534] MachineType: ASUS All Series ProcCmdline: /usr/bin/Xwayland :0 -rootless -terminate -accessx -core -listen 4 -listen 5 -displayfd 6 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-10-generic root=UUID=cd444f9d-672e-4d7b-aea8-657fff0ea1f4 ro quiet splash crashkernel=384M-:128M crashkernel=384M-:128M crashkernel=384M-:128M nomdmonddf nomdmonisw crashkernel=384M-:128M nomdmonddf nomdmonisw crashkernel=384M-:128M nomdmonddf nomdmonisw crashkernel=384M-:128M nomdmonddf nomdmonisw crashkernel=384M-:128M nomdmonddf nomdmonisw crashkernel=384M-:128M nomdmonddf nomdmonisw crashkernel=384M-:128M nomdmonddf nomdmonisw crashkernel=384M-:128M crashkernel=384M-:128M crashkernel=384M-:128M crashkernel=384M-:128M crashkernel=384M-:128M crashkernel=384M-:128M crashkernel=384M-:128M crashkernel=384M-:128M crashkernel=384M-:128M crashkernel=384M-:128M crashkernel=384M-:128M crashkernel=384M-:128M crashkernel=384M-:128M crashkernel=384M-:128M vt.handoff=1 Signal: 6 SourcePackage: xorg-server StacktraceTop: ?? () from /usr/lib/x86_64-linux-gnu/dri/swrast_dri.so ?? () from /usr/lib/x86_64-linux-gnu/dri/swrast_dri.so ?? () from /usr/lib/x86_64-linux-gnu/dri/swrast_dri.so ?? () from /usr/lib/x86_64-linux-gnu/dri/swrast_dri.so ?? () from /usr/lib/x86_64-linux-gnu/dri/swrast_dri.so Title: Xwayland crashed with SIGABRT UpgradeStatus: Upgraded to bionic on 2018-03-06 (2 days ago) UserGroups: adm admin audio cdrom chroot-admin dialout dip egbuild fax floppy fuse libvirt libvirtd lpadmin lxd plugdev sambashare sudo tape video wireshark dmi.bios.date: 10/27/2015 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 2702 dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: Z97-PRO dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: Rev 1.xx dmi.chassis.asset.tag: To Be Filled By O.E.M. dmi.chassis.type: 3 dmi.chassis.vendor: To Be Filled By O.E.M. dmi.chassis.version: To Be Filled By O.E.M. dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr2702:bd10/27/2015:svnASUS:pnAllSeries:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnZ97-PRO:rvrRev1.xx:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.: dmi.product.family: ASUS MB dmi.product.name: All Series dmi.product.version: System Version dmi.sys.vendor: ASUS version.compiz: compiz 1:0.9.13.1+18.04.20180302-0ubuntu1 version.libdrm2: libdrm2 2.4.90-1 version.libgl1-mesa-dri: libgl1-mesa-dri 18.0.0~rc4-1ubuntu3 version.libgl1-mesa-glx: libgl1-mesa-glx 18.0.0~rc4-1ubuntu3 version.xserver-xorg-core: xserver-xorg-core 2:1.19.6-1ubuntu2 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.10.5-1ubuntu1 version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.10.0-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20171229-1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.15-2 xserver.bootTime: Mon Oct 16 18:18:18 2017 xserver.configfile: default xserver.devices: xserver.logfile: /var/log/Xorg.0.log xserver.outputs: xserver.version: 2:1.19.3-1ubuntu1.2 ** Summary changed: - Xwayland crashed with SIGABRT in st_renderbuffer_delete() [often when running Skype or Slack snaps] + Xwayland/Xorg crashed with SIGABRT in st_renderbuffer_delete() [often when running Skype or Slack snaps] ** Summary changed: -
[Touch-packages] [Bug 1754693] Re: Xwayland crashed with SIGABRT in st_renderbuffer_delete() [often when running Skype or Slack snaps]
I have the same issue on 18.04, Wayland: ``` $ snap list skype Name VersionRev Tracking Publisher Notes skype 8.33.0.41 63 stableskype✓ classic ``` -- 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/1754693 Title: Xwayland crashed with SIGABRT in st_renderbuffer_delete() [often when running Skype or Slack snaps] Status in mesa package in Ubuntu: Confirmed Status in xorg-server package in Ubuntu: Confirmed Bug description: https://errors.ubuntu.com/problem/01a80d2110a46f6b6d857ce814079646e695f4ca --- Steps to reproduce: Install 'slack' snap: sudo snap install slack --classic Run slack: slack Instacrash. ProblemType: Crash DistroRelease: Ubuntu 18.04 Package: xwayland 2:1.19.6-1ubuntu2 ProcVersionSignature: Ubuntu 4.15.0-10.11-generic 4.15.3 Uname: Linux 4.15.0-10-generic x86_64 .tmp.unity_support_test.0: ApportVersion: 2.20.8-0ubuntu10 Architecture: amd64 CompizPlugins: [core,composite,opengl,decor,mousepoll,grid,vpswitch,compiztoolbox,imgpng,gnomecompat,regex,move,place,resize,snap,unitymtgrabhandles,wall,animation,session,expo,workarounds,fade,ezoom,scale,unityshell] CompositorRunning: None CurrentDesktop: GNOME Date: Fri Mar 9 10:31:06 2018 DistUpgraded: 2018-03-06 13:58:47,853 DEBUG Running PostInstallScript: './xorg_fix_proprietary.py' DistroCodename: bionic DistroVariant: ubuntu EcryptfsInUse: Yes ExecutablePath: /usr/bin/Xwayland ExtraDebuggingInterest: Yes, including running git bisection searches GraphicsCard: Intel Corporation Xeon E3-1200 v3/4th Gen Core Processor Integrated Graphics Controller [8086:0412] (rev 06) (prog-if 00 [VGA controller]) Subsystem: ASUSTeK Computer Inc. Xeon E3-1200 v3/4th Gen Core Processor Integrated Graphics Controller [1043:8534] MachineType: ASUS All Series ProcCmdline: /usr/bin/Xwayland :0 -rootless -terminate -accessx -core -listen 4 -listen 5 -displayfd 6 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-10-generic root=UUID=cd444f9d-672e-4d7b-aea8-657fff0ea1f4 ro quiet splash crashkernel=384M-:128M crashkernel=384M-:128M crashkernel=384M-:128M nomdmonddf nomdmonisw crashkernel=384M-:128M nomdmonddf nomdmonisw crashkernel=384M-:128M nomdmonddf nomdmonisw crashkernel=384M-:128M nomdmonddf nomdmonisw crashkernel=384M-:128M nomdmonddf nomdmonisw crashkernel=384M-:128M nomdmonddf nomdmonisw crashkernel=384M-:128M nomdmonddf nomdmonisw crashkernel=384M-:128M crashkernel=384M-:128M crashkernel=384M-:128M crashkernel=384M-:128M crashkernel=384M-:128M crashkernel=384M-:128M crashkernel=384M-:128M crashkernel=384M-:128M crashkernel=384M-:128M crashkernel=384M-:128M crashkernel=384M-:128M crashkernel=384M-:128M crashkernel=384M-:128M crashkernel=384M-:128M vt.handoff=1 Signal: 6 SourcePackage: xorg-server StacktraceTop: ?? () from /usr/lib/x86_64-linux-gnu/dri/swrast_dri.so ?? () from /usr/lib/x86_64-linux-gnu/dri/swrast_dri.so ?? () from /usr/lib/x86_64-linux-gnu/dri/swrast_dri.so ?? () from /usr/lib/x86_64-linux-gnu/dri/swrast_dri.so ?? () from /usr/lib/x86_64-linux-gnu/dri/swrast_dri.so Title: Xwayland crashed with SIGABRT UpgradeStatus: Upgraded to bionic on 2018-03-06 (2 days ago) UserGroups: adm admin audio cdrom chroot-admin dialout dip egbuild fax floppy fuse libvirt libvirtd lpadmin lxd plugdev sambashare sudo tape video wireshark dmi.bios.date: 10/27/2015 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 2702 dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: Z97-PRO dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: Rev 1.xx dmi.chassis.asset.tag: To Be Filled By O.E.M. dmi.chassis.type: 3 dmi.chassis.vendor: To Be Filled By O.E.M. dmi.chassis.version: To Be Filled By O.E.M. dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr2702:bd10/27/2015:svnASUS:pnAllSeries:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnZ97-PRO:rvrRev1.xx:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.: dmi.product.family: ASUS MB dmi.product.name: All Series dmi.product.version: System Version dmi.sys.vendor: ASUS version.compiz: compiz 1:0.9.13.1+18.04.20180302-0ubuntu1 version.libdrm2: libdrm2 2.4.90-1 version.libgl1-mesa-dri: libgl1-mesa-dri 18.0.0~rc4-1ubuntu3 version.libgl1-mesa-glx: libgl1-mesa-glx 18.0.0~rc4-1ubuntu3 version.xserver-xorg-core: xserver-xorg-core 2:1.19.6-1ubuntu2 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.10.5-1ubuntu1 version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.10.0-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20171229-1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.15-2 xserver.bootTime: Mon Oct 16 18:18:18 2017 xserver.configfile: default xserver.devices: xserver.logfile: /var/log/Xorg.0.log xserver.outputs:
[Touch-packages] [Bug 1801642] Re: Bluetooth mouse sleeps after 5 seconds of inactivity
I see. There are two "Good" unknown autosuspend USB devices, not sure which one is my mouse. I can't find it in "Bad" either. Anyhow, the issue seems resolved currently. -- 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/1801642 Title: Bluetooth mouse sleeps after 5 seconds of inactivity Status in bluez package in Ubuntu: Invalid Bug description: I'm having bluetooth mouse lag issue. After leaving it stationary for 5 seconds, I have to move it for 2 seconds before the pointer starts moving. I recently upgraded to Cosmic 3 days ago (from Bionic). There was no issue in the first 3 days, including after suspend/restart/shutdown. This issue only appears starting today. I tried: 1. Running 'bluetoothctl' and then 'scan off'. The command failed to run with 'Failed to stop discovery: org.bluez.Error.Failed'. 2. modprobe -r btusb, then modprobe it again. 3. sudo sh -c 'echo N > /sys/module/drm_kms_helper/parameters/poll' 4. Disabling wifi. $ apt-cache policy bluez 5.50-0ubuntu1 $uname -a; lspci -nnk | grep -iA2 net; lsusb; dmesg | grep -i bluetooth; dmesg | grep -i firmware; lsmod | grep bluetooth 4.18.0-10-generic #11 02:00.0 Network controller [0280]: Intel Corporation Wireless 7260 [8086:08b1] (rev 73) Subsystem: Intel Corporation Dual Band Wireless-N 7260 [8086:4460] Kernel driver in use: iwlwifi 03:00.1 Ethernet controller [0200]: Realtek Semiconductor Co., Ltd. RTL8111/8168/8411 PCI Express Gigabit Ethernet Controller [10ec:8168] (rev 12) Subsystem: Dell RTL8111/8168/8411 PCI Express Gigabit Ethernet Controller [1028:05f9] Kernel driver in use: r8169 Kernel modules: r8169 Bus 001 Device 002: ID 8087:8000 Intel Corp. Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Bus 003 Device 003: ID 17e9:4301 DisplayLink Bus 003 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 002 Device 047: ID 04f3:0206 Elan Microelectronics Corp. Bus 002 Device 006: ID 8087:07dc Intel Corp. Bus 002 Device 034: ID 0461:4d51 Primax Electronics, Ltd 0Y357C PMX-MMOCZUL (B) [Dell Laser Mouse] Bus 002 Device 118: ID 0853:0132 Topre Corporation Bus 002 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub [ 287.361153] hid-generic 0005:046D:B012.0005: input,hidraw2: BLUETOOTH HID v0.14 Keyboard [MX Master] on FC:F8:AE:33:C7:31 bluetooth 548864 33 btrtl,btintel,btbcm,bnep,btusb,rfcomm ecdh_generic 24576 2 bluetooth ProblemType: Bug DistroRelease: Ubuntu 18.10 Package: bluez 5.50-0ubuntu1 ProcVersionSignature: Ubuntu 4.18.0-10.11-generic 4.18.12 Uname: Linux 4.18.0-10-generic x86_64 ApportVersion: 2.20.10-0ubuntu13 Architecture: amd64 CurrentDesktop: MATE Date: Mon Nov 5 13:40:01 2018 InstallationDate: Installed on 2018-07-08 (119 days ago) InstallationMedia: Ubuntu-MATE 18.04 LTS "Bionic Beaver" - Release amd64 (20180426) InterestingModules: rfcomm bnep btusb bluetooth MachineType: Dell Inc. Inspiron 7537 ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.18.0-10-generic root=/dev/mapper/ubuntu--mate--vg-root ro ipv6.disable=1 quiet splash i915.enable_psr=0 SourcePackage: bluez UpgradeStatus: Upgraded to cosmic on 2018-11-02 (3 days ago) dmi.bios.date: 10/31/2013 dmi.bios.vendor: Dell Inc. dmi.bios.version: A05 dmi.board.name: 07PF9F dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 8 dmi.chassis.vendor: Dell Inc. dmi.chassis.version: 0.1 dmi.modalias: dmi:bvnDellInc.:bvrA05:bd10/31/2013:svnDellInc.:pnInspiron7537:pvr:rvnDellInc.:rn07PF9F:rvrA00:cvnDellInc.:ct8:cvr0.1: dmi.product.family: Shark Bay ULT dmi.product.name: Inspiron 7537 dmi.product.sku: Inspiron 7537 dmi.sys.vendor: Dell Inc. hciconfig: hci0:Type: Primary Bus: USB BD Address: FC:F8:AE:33:C7:31 ACL MTU: 1021:5 SCO MTU: 96:5 UP RUNNING RX bytes:2380 acl:32 sco:0 events:208 errors:0 TX bytes:28560 acl:29 sco:0 commands:170 errors:0 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/1801642/+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 1794544] Re: [SRU] 2.56.3
Version 2.56.3 installed here from proposed, works properly. marco@tricky:/tmp:✓ $ apt-cache policy libglib2.0-0 libglib2.0-0: Installato: 2.56.3-0ubuntu0.18.04.1 Candidato: 2.56.3-0ubuntu0.18.04.1 Tabella versione: *** 2.56.3-0ubuntu0.18.04.1 100 500 http://archive.ubuntu.com/ubuntu bionic-proposed/main amd64 Packages 2.56.2-0ubuntu0.18.04.2 500 500 http://archive.ubuntu.com/ubuntu bionic-updates/main amd64 Packages 500 http://archive.ubuntu.com/ubuntu bionic-security/main amd64 Packages 2.56.1-2ubuntu1 500 500 http://archive.ubuntu.com/ubuntu bionic/main amd64 Packages ** Tags removed: verification-needed verification-needed-bionic ** Tags added: verification-done verification-done-bionic -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to glib2.0 in Ubuntu. https://bugs.launchpad.net/bugs/1794544 Title: [SRU] 2.56.3 Status in glib2.0 package in Ubuntu: Fix Released Status in glib2.0 source package in Bionic: Fix Committed Bug description: [ Description ] The third stable release in the 2.56 series. [ QA ] Upstream release, so QA already performed by maintainers https://wiki.ubuntu.com/StableReleaseUpdates/GNOME This upload will trigger many autopkgtests that we expect to not be regressed by this upload. [ Regression potential ] Various fixes in multiple places so multiple apps could be affected. * New upstream release (LP: #xxx) + The documentation for G_GNUC_MALLOC has changed to be more restrictive to avoid miscompilations; you should check whether any uses of it in your code are appropriate + Fix cancellation of g_subprocess_communicate_async() calls + Bug fixes: + /network-monitor/create-in-thread fails in (LXC) containers on glib-2-56 + GBookmarkFile: nullptr access in current_element + GBookmarkFile: heap-buffer-overflow in g_utf8_get_char + Backport g_subprocess_communicate() cancellation fixes from !266 to glib-2-56 (LP: #1789476) + Many uses of G_GNUC_MALLOC are incorrect + Test for BROKEN_IP_MREQ_SOURCE_STRUCT is broken on Windows / Mingw + Fix persistent CI failure on glib-2-56 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/glib2.0/+bug/1794544/+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 1799007] Re: [System76 Oryx Pro] no sound after 18.10 upgrade
The PulseAudio developers should be able to help you with more advanced debugging. You can log a bug to get help from them at: https://gitlab.freedesktop.org/groups/pulseaudio/-/issues -- 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/1799007 Title: [System76 Oryx Pro] no sound after 18.10 upgrade Status in pulseaudio package in Ubuntu: Triaged Bug description: After upgrading to 18.10, the sound in my System76 Oryx Pro no longer works, it no longer shows any of the audio output devices, not even the builtin HDMI which usually always shows. Not sure what happened, but this is a major regression and needs to be fixed. Note that this isn't the same as the bug with Timidity taking exclusive soundcard access (https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1797714) as I don't have any timidity packages installed. --- ProblemType: Bug ApportVersion: 2.20.10-0ubuntu13 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: tessa 11703 F pulseaudio /dev/snd/controlC0: tessa 11703 F pulseaudio /dev/snd/pcmC0D0c: tessa 11703 F...m pulseaudio /dev/snd/pcmC0D0p: tessa 11703 F...m pulseaudio CurrentDesktop: pop:GNOME DistroRelease: Pop!_OS 18.10 InstallationDate: Installed on 2018-03-05 (230 days ago) InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20180105.1) NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair nvidia_modeset nvidia Package: pulseaudio 1:12.2-0ubuntu4 [origin: Ubuntu] PackageArchitecture: amd64 ProcVersionSignature: Ubuntu 4.18.0-10.11-generic 4.18.12 PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: Daemon not responding. Tags: third-party-packages cosmic Uname: Linux 4.18.0-10-generic x86_64 UnreportableReason: This is not an official Pop!_OS package. Please remove any third party package and try again. UpgradeStatus: Upgraded to cosmic on 2018-10-18 (3 days ago) UserGroups: adm audio cdrom chrome-remote-desktop dip docker libvirt lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 02/20/2017 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 1.05.02dRSA2 dmi.board.asset.tag: Tag 12345 dmi.board.name: Oryx Pro dmi.board.vendor: System76 dmi.board.version: oryp3-ess dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: System76 dmi.chassis.version: N/A dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr1.05.02dRSA2:bd02/20/2017:svnSystem76:pnOryxPro:pvroryp3-ess:rvnSystem76:rnOryxPro:rvroryp3-ess:cvnSystem76:ct10:cvrN/A: dmi.product.family: Not Applicable dmi.product.name: Oryx Pro dmi.product.sku: Not Applicable dmi.product.version: oryp3-ess dmi.sys.vendor: System76 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1799007/+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 1797862] Re: Cannot turn off keyboard backlight
Maybe merge with bug 1791372? ** No longer affects: upower (Ubuntu) -- 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/1797862 Title: Cannot turn off keyboard backlight Status in linux package in Ubuntu: Confirmed Bug description: /sys/class/leds $ ls asus-wireless::airplane input10::capslock input10::compose input10::kana input10::numlock input10::scrolllock input4::capslock input4::numlock input4::scrolllock phy0-led There isn't any asus kbd backlight folder. `xset led off` doesn't work for me. And I can only use fn to control volume (f1/f2/f3). The leds kills my battery $ sudo dmidecode -t 1; lsb_release -a # dmidecode 3.1 Getting SMBIOS data from sysfs. SMBIOS 3.0.0 present. Handle 0x0001, DMI type 1, 27 bytes System Information Manufacturer: ASUSTeK COMPUTER INC. Product Name: FX503VD Version: 1.0 Serial Number: H9NRCX00M803374 UUID: 524E3948-5843-3030-4D38-30373441 Wake-up Type: Power Switch SKU Number: Family: FX No LSB modules are available. Distributor ID: Ubuntu Description: Ubuntu Cosmic Cuttlefish (development branch) Release: 18.10 Codename: cosmic ProblemType: Bug DistroRelease: Ubuntu 18.10 Package: xorg 1:7.7+19ubuntu8 ProcVersionSignature: Ubuntu 4.18.0-10.11-generic 4.18.12 Uname: Linux 4.18.0-10-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia .proc.driver.nvidia.gpus..01.00.0: Error: [Errno 21] 是一个目录: '/proc/driver/nvidia/gpus/:01:00.0' .proc.driver.nvidia.registry: Binary: "" .proc.driver.nvidia.version: NVRM version: NVIDIA UNIX x86_64 Kernel Module 390.87 Tue Aug 21 12:33:05 PDT 2018 GCC version: gcc version 8.2.0 (Ubuntu 8.2.0-7ubuntu1) ApportVersion: 2.20.10-0ubuntu11 Architecture: amd64 BootLog: Error: [Errno 13] 权限不够: '/var/log/boot.log' CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Mon Oct 15 17:13:35 2018 DistUpgraded: Fresh install DistroCodename: cosmic DistroVariant: ubuntu DkmsStatus: nvidia, 390.87, 4.18.0-10-generic, x86_64: installed nvidia, 390.87, 4.18.0-9-generic, x86_64: installed ExtraDebuggingInterest: Yes, if not too technical GraphicsCard: Intel Corporation Device [8086:591b] (rev 04) (prog-if 00 [VGA controller]) Subsystem: ASUSTeK Computer Inc. Device [1043:1b90] Subsystem: ASUSTeK Computer Inc. GP107M [GeForce GTX 1050 Mobile] [1043:1b90] InstallationDate: Installed on 2018-10-10 (4 days ago) InstallationMedia: Ubuntu 18.10 "Cosmic Cuttlefish" - Beta amd64 (20180927) Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 004: ID 0b05:1869 ASUSTek Computer, Inc. Bus 001 Device 003: ID 13d3:5666 IMC Networks Bus 001 Device 002: ID 8087:0a2b Intel Corp. Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: ASUSTeK COMPUTER INC. FX503VD ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.18.0-10-generic root=UUID=ad490863-aaf6-49d0-8508-514c07335e07 ro nouveau.runpm=0 SourcePackage: xorg UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 10/03/2017 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: FX503VD.302 dmi.board.asset.tag: ATN12345678901234567 dmi.board.name: FX503VD dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: 1.0 dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: ASUSTeK COMPUTER INC. dmi.chassis.version: 1.0 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrFX503VD.302:bd10/03/2017:svnASUSTeKCOMPUTERINC.:pnFX503VD:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnFX503VD:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0: dmi.product.family: FX dmi.product.name: FX503VD dmi.product.version: 1.0 dmi.sys.vendor: ASUSTeK COMPUTER INC. version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.95-1 version.libgl1-mesa-dri: libgl1-mesa-dri 18.2.2-0ubuntu1 version.libgl1-mesa-glx: libgl1-mesa-glx 18.2.2-0ubuntu1 version.nvidia-graphics-drivers: nvidia-graphics-drivers-* N/A version.xserver-xorg-core: xserver-xorg-core 2:1.20.1-3ubuntu2 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:18.1.0-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20171229-1ubuntu1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.15-3 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1797862/+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 1789476] Re: glib apps using GSubprocess communicate might crash on g_subprocess_communicate_cancelled
Test case works as expected. marco@tricky:/tmp:✓ $ apt-cache policy libglib2.0-0 libglib2.0-0: Installato: 2.56.3-0ubuntu0.18.04.1 Candidato: 2.56.3-0ubuntu0.18.04.1 Tabella versione: *** 2.56.3-0ubuntu0.18.04.1 100 500 http://archive.ubuntu.com/ubuntu bionic-proposed/main amd64 Packages 2.56.2-0ubuntu0.18.04.2 500 500 http://archive.ubuntu.com/ubuntu bionic-updates/main amd64 Packages 500 http://archive.ubuntu.com/ubuntu bionic-security/main amd64 Packages 2.56.1-2ubuntu1 500 500 http://archive.ubuntu.com/ubuntu bionic/main amd64 Packages marco@tricky:/tmp:✓ $ gjs /tmp/subprocess-cancelled.js (gjs:8606): Gjs-WARNING **: 22:08:37.297: JS ERROR: Gio.IOErrorEnum: L'operazione è stata annullata @/tmp/subprocess-cancelled.js:10:5 @/tmp/subprocess-cancelled.js:16:5 ** Tags removed: verification-needed verification-needed-bionic ** Tags added: verification-done verification-done-bionic -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to glib2.0 in Ubuntu. https://bugs.launchpad.net/bugs/1789476 Title: glib apps using GSubprocess communicate might crash on g_subprocess_communicate_cancelled Status in glib2.0 package in Ubuntu: Fix Released Status in glib2.0 source package in Bionic: Fix Committed Bug description: [ Impact ] Glib apps using subprocess communicate and cancellable is cancelled crashes [ Test case ] Run the attached example with gjs subprocess-cancelled.js Should not crash, or running: valgrind gjs subprocess-cancelled.js should not return any read error (as the one mentioned below) [ Regression potential ] Really low, the only thing that could happen is that the subprocess isn't really cancelled. --- Fixed upstream in https://gitlab.gnome.org/GNOME/glib/merge_requests/266 #0 g_cancellable_cancel (cancellable=0x6) at ../../glib/gio/gcancellable.c:486 #1 0x77ab8d1d in g_subprocess_communicate_cancelled (user_data=) at ../../glib/gio/gsubprocess.c:1535 -- ==25871== Memcheck, a memory error detector ==25871== Copyright (C) 2002-2017, and GNU GPL'd, by Julian Seward et al. ==25871== Using Valgrind-3.13.0 and LibVEX; rerun with -h for copyright info ==25871== Command: gjs /tmp/subprocess-cancelled.js ==25871== ==25871== Warning: set address range perms: large range [0x377ee1e21000, 0x377f21e21000) (noaccess) ==25871== Invalid read of size 8 ==25871==at 0x4EC5604: g_subprocess_communicate_cancelled (gsubprocess.c:1535) ==25871==by 0x547A0F4: g_main_dispatch (gmain.c:3177) ==25871==by 0x547A0F4: g_main_context_dispatch (gmain.c:3830) ==25871==by 0x547A4BF: g_main_context_iterate.isra.26 (gmain.c:3903) ==25871==by 0x547A54B: g_main_context_iteration (gmain.c:3964) ==25871==by 0x6C4EDAD: ffi_call_unix64 (in /usr/lib/x86_64-linux-gnu/libffi.so.6.0.4) ==25871==by 0x6C4E71E: ffi_call (in /usr/lib/x86_64-linux-gnu/libffi.so.6.0.4) ==25871==by 0x5775607: ??? (in /usr/lib/libgjs.so.0.0.0) ==25871==by 0x5776F53: ??? (in /usr/lib/libgjs.so.0.0.0) ==25871==by 0x8A3FF6B: CallJSNative (jscntxtinlines.h:239) ==25871==by 0x8A3FF6B: js::InternalCallOrConstruct(JSContext*, JS::CallArgs const&, js::MaybeConstruct) (Interpreter.cpp:447) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/glib2.0/+bug/1789476/+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 1799007] Re: [System76 Oryx Pro] no sound after 18.10 upgrade
I've already tried reinstalling pulseaudio, and it doesn't do anything. I can't really afford to reinstall my work laptop right now, I really need it to just, you know, work. ;) but I also need working sound so I'm not really sure what to do. is there really no way to debug pulseaudio and why it's broken? if not, are there supported alternate audio servers for ubuntu which will work with everything? -- 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/1799007 Title: [System76 Oryx Pro] no sound after 18.10 upgrade Status in pulseaudio package in Ubuntu: Triaged Bug description: After upgrading to 18.10, the sound in my System76 Oryx Pro no longer works, it no longer shows any of the audio output devices, not even the builtin HDMI which usually always shows. Not sure what happened, but this is a major regression and needs to be fixed. Note that this isn't the same as the bug with Timidity taking exclusive soundcard access (https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1797714) as I don't have any timidity packages installed. --- ProblemType: Bug ApportVersion: 2.20.10-0ubuntu13 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: tessa 11703 F pulseaudio /dev/snd/controlC0: tessa 11703 F pulseaudio /dev/snd/pcmC0D0c: tessa 11703 F...m pulseaudio /dev/snd/pcmC0D0p: tessa 11703 F...m pulseaudio CurrentDesktop: pop:GNOME DistroRelease: Pop!_OS 18.10 InstallationDate: Installed on 2018-03-05 (230 days ago) InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20180105.1) NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair nvidia_modeset nvidia Package: pulseaudio 1:12.2-0ubuntu4 [origin: Ubuntu] PackageArchitecture: amd64 ProcVersionSignature: Ubuntu 4.18.0-10.11-generic 4.18.12 PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: Daemon not responding. Tags: third-party-packages cosmic Uname: Linux 4.18.0-10-generic x86_64 UnreportableReason: This is not an official Pop!_OS package. Please remove any third party package and try again. UpgradeStatus: Upgraded to cosmic on 2018-10-18 (3 days ago) UserGroups: adm audio cdrom chrome-remote-desktop dip docker libvirt lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 02/20/2017 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 1.05.02dRSA2 dmi.board.asset.tag: Tag 12345 dmi.board.name: Oryx Pro dmi.board.vendor: System76 dmi.board.version: oryp3-ess dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: System76 dmi.chassis.version: N/A dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr1.05.02dRSA2:bd02/20/2017:svnSystem76:pnOryxPro:pvroryp3-ess:rvnSystem76:rnOryxPro:rvroryp3-ess:cvnSystem76:ct10:cvrN/A: dmi.product.family: Not Applicable dmi.product.name: Oryx Pro dmi.product.sku: Not Applicable dmi.product.version: oryp3-ess dmi.sys.vendor: System76 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1799007/+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 1758035] Re: [regression] gnome-shell crashed with SIGTRAP in g_realloc_n() from g_log_structured()
That sounds plausible. Also there are zero reports of this crash after gnome-shell 3.28.0. So zero crashes in Ubuntu 18.10, and zero crashes since the final release of Ubuntu 18.04. The only systems still crashing seem to be pre-release bionic systems that haven't been updated for most of the year. I think this looks fixed already. Maybe fixed as early as the final release of 18.04. ** Changed in: glib2.0 (Ubuntu) Assignee: Daniel van Vugt (vanvugt) => (unassigned) ** Changed in: glib2.0 (Ubuntu Bionic) Assignee: Daniel van Vugt (vanvugt) => (unassigned) ** Changed in: gnome-shell (Ubuntu) Assignee: Daniel van Vugt (vanvugt) => (unassigned) ** Changed in: gnome-shell (Ubuntu Bionic) Assignee: Daniel van Vugt (vanvugt) => (unassigned) ** Changed in: glib2.0 (Ubuntu) Status: Confirmed => Incomplete ** Changed in: glib2.0 (Ubuntu Bionic) Status: Confirmed => Incomplete ** Changed in: gnome-shell (Ubuntu) Status: Confirmed => Incomplete ** Changed in: gnome-shell (Ubuntu Bionic) Status: Confirmed => Incomplete ** Changed in: glib2.0 (Ubuntu) Status: Incomplete => Fix Released ** Changed in: glib2.0 (Ubuntu Bionic) Status: Incomplete => Fix Released ** Changed in: gnome-shell (Ubuntu) Status: Incomplete => Fix Released ** Changed in: gnome-shell (Ubuntu Bionic) Status: Incomplete => Fix Released -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to glib2.0 in Ubuntu. https://bugs.launchpad.net/bugs/1758035 Title: [regression] gnome-shell crashed with SIGTRAP in g_realloc_n() from g_log_structured() Status in glib2.0 package in Ubuntu: Fix Released Status in gnome-shell package in Ubuntu: Fix Released Status in glib2.0 source package in Bionic: Fix Released Status in gnome-shell source package in Bionic: Fix Released Bug description: https://errors.ubuntu.com/problem/bf61cf0ebedaacbd48f7c12574f551fea3f706c7 https://errors.ubuntu.com/problem/bc2bd5031309e8cf2314785805634f998452e937 https://errors.ubuntu.com/problem/f30049f514bf17053fe0461bf2b0890e46ad32dd --- Freshly installed bionic. ProblemType: Crash DistroRelease: Ubuntu 18.04 Package: gnome-shell 3.28.0-0ubuntu1 ProcVersionSignature: Ubuntu 4.15.0-12.13-generic 4.15.7 Uname: Linux 4.15.0-12-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.8-0ubuntu10 Architecture: amd64 CurrentDesktop: GNOME-Greeter:GNOME Date: Thu Mar 22 12:22:58 2018 DisplayManager: gdm3 ExecutablePath: /usr/bin/gnome-shell GsettingsChanges: InstallationDate: Installed on 2018-03-22 (0 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Alpha amd64 (20180321) ProcCmdline: /usr/bin/gnome-shell Signal: 5 SourcePackage: gnome-shell StacktraceTop: g_realloc_n () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 g_log_structured () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 ?? () Title: gnome-shell crashed with signal 5 in g_realloc_n() UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/glib2.0/+bug/1758035/+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 1738153] Re: need backport the new scancode of dell-wmi for Microphone mute hotkey to xenial
** Changed in: oem-priority/xenial 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/1738153 Title: need backport the new scancode of dell-wmi for Microphone mute hotkey to xenial Status in OEM Priority Project: Fix Released Status in OEM Priority Project xenial series: Fix Released Status in systemd package in Ubuntu: Fix Released Status in systemd source package in Xenial: Fix Released Status in systemd source package in Artful: Won't Fix Bug description: [Impact] dell-wmi expend the scan code of Microphone mute hotkey from 0x150 to 0x100150, so need to add a new mapping for it. related commit: https://github.com/systemd/systemd/pull/5012 [Test Case] 1. install the udev package which applied patch. 2. check if Microphone mute hotkey works. 3. if it not works, please provide the log of evtest. [Regression Potential] low regression potential, because it just add one more mapping. also affect: LP: #1736352 LP: #1740080 LP: #1734609 To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/1738153/+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 1801540] Re: Microphone distorted sound on ALC892
Probably the FreeBSD is working as Windows, they use the software de- noise filter when users record sound. Please test with "pactl load-module module-echo-cancel", then choose echo-cancelled record device from gnome-sound-setting->input tab. Now record sth, and play it. Is it better now? If there is sth in the kernel driver to introduce the noise, the thing I can figure out so far is change the micbias reference voltag: Right now the reference for two mics: Rear Mic: Pin-ctls: 0x21: IN VREF_50 Front Mic: Pin-ctls: 0x24: IN VREF_80 You can try to set them with different value like "HIZ 50 GRD 80 100", maybe some value can improve the sound quality. The patch_realtek.c has some sample code to set verf. -- 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/1801540 Title: Microphone distorted sound on ALC892 Status in linux package in Ubuntu: Incomplete Status in pulseaudio package in Ubuntu: New Bug description: Not sure if I'll report this upstream but there is definitely an issue with microphone recording on my desktop, this is not happening on my laptop which has a different codec. Already tried all workarounds possible, no luck. Only with my desktop with this particular motherboard. No issues in Windows, the sound recorded in there is distorted and has some static and robotic tone on high-pitch. alsa-info on the attachments To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1801540/+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 1739931] Re: Separator lines in shell popup menus are too faint to see
** Changed in: gnome-shell (Ubuntu Bionic) Status: New => Fix Committed ** Changed in: gnome-shell (Ubuntu Bionic) Status: Fix Committed => In Progress ** Changed in: gnome-shell (Ubuntu Bionic) Importance: Undecided => Low -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to ubuntu-themes in Ubuntu. https://bugs.launchpad.net/bugs/1739931 Title: Separator lines in shell popup menus are too faint to see Status in gnome-shell package in Ubuntu: Fix Released Status in gnome-shell-extension-ubuntu-dock package in Ubuntu: Won't Fix Status in ubuntu-themes package in Ubuntu: Won't Fix Status in gnome-shell source package in Bionic: In Progress Status in gnome-shell-extension-ubuntu-dock source package in Bionic: Won't Fix Status in ubuntu-themes source package in Bionic: Won't Fix Bug description: [ Impact ] Separators in gnome-shell menuitems are not visible [ Test case ] 1. Right - Click on a dock icon 2. Separators between menu items should be visible [ Regression potential ] Nothing known when I click on the dock icons, some of the lines in the popup menus are blank and some of them appear to be incorrect. see top left of attached screenshot. ProblemType: BugDistroRelease: Ubuntu 17.10 Package: nautilus 1:3.26.0-0ubuntu1 ProcVersionSignature: Ubuntu 4.13.0-16.19-generic 4.13.4 Uname: Linux 4.13.0-16-generic x86_64 ApportVersion: 2.20.7-0ubuntu3.6 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Sat Dec 23 22:24:40 2017 InstallationDate: Installed on 2016-08-18 (492 days ago) InstallationMedia: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 (20160719) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bashSourcePackage: nautilus UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1739931/+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 1801832] [NEW] Input method toggled when using the numeric pad
Public bug reported: Ubuntu 18.04 LTS During the Chinese character input mode, when I enter numbers using the numeric pad, the input method will be switched to English automatically, which is very annoying. Any suggestions? ** Affects: ibus (Ubuntu) Importance: Undecided Status: New ** Package changed: epiphany-browser (Ubuntu) => ibus (Ubuntu) ** Summary changed: - Input method toggled when entering numbers with the numeric pad + Input method toggled when using the numeric pad -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to ibus in Ubuntu. https://bugs.launchpad.net/bugs/1801832 Title: Input method toggled when using the numeric pad Status in ibus package in Ubuntu: New Bug description: Ubuntu 18.04 LTS During the Chinese character input mode, when I enter numbers using the numeric pad, the input method will be switched to English automatically, which is very annoying. Any suggestions? To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ibus/+bug/1801832/+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 1799064] Re: Bluetooth (ISSC USB dongle) refuses to power on after cosmic upgrade (works in kernel 4.15.0, but fails in 4.16 onward)
Can kernel parameter "usbcore.enable_autosuspend=0" workaround the issue? -- 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/1799064 Title: Bluetooth (ISSC USB dongle) refuses to power on after cosmic upgrade (works in kernel 4.15.0, but fails in 4.16 onward) Status in bluez package in Ubuntu: Invalid Status in linux package in Ubuntu: Confirmed Bug description: After upgrading from bionic to cosmic, Bluetooth has stopped working. It has worked fine for several versions before. Error message from syslog is: Failed to set mode: Failed (0x03) Which according to various random forum posts seems to suggest the device is not powering on. Powering on manually also does not work: % bluetoothctl Agent registered [bluetooth]# power on Failed to set power on: org.bluez.Error.Failed And results in the same set mode failure getting logged again in syslog. hciconfig reports the device as down: % sudo hciconfig hci0: Type: Primary Bus: USB BD Address: 00:11:67:00:00:00 ACL MTU: 1021:4 SCO MTU: 48:10 DOWN RX bytes:498 acl:0 sco:0 events:21 errors:0 TX bytes:101 acl:0 sco:0 commands:24 errors:0 And, again, it refuses to power on: % sudo hciconfig hci0 up Can't init device hci0: Connection timed out (110) rfkill does not appear to be blocking it: % rfkill list 0: hci0: Bluetooth Soft blocked: no Hard blocked: no 1: phy0: Wireless LAN Soft blocked: no Hard blocked: no And systemd-rfkill.service is masked: ~ % sudo systemctl status systemd-rfkill.service ● systemd-rfkill.service Loaded: masked (Reason: Unit systemd-rfkill.service is masked.) [..] The system does not have tlp installed. I have tried numerous reboots, power offs, and moving the USB Bluetooth adapter to different ports, with no change in result. I have also tried unloading and loading btusb. The adapter is a cheap noname thing off of eBay, I trust the system report will provide every possibly interesting detail about it. ProblemType: Bug DistroRelease: Ubuntu 18.10 Package: bluez 5.50-0ubuntu1 ProcVersionSignature: Ubuntu 4.18.0-10.11-generic 4.18.12 Uname: Linux 4.18.0-10-generic x86_64 NonfreeKernelModules: nvidia ApportVersion: 2.20.10-0ubuntu13 Architecture: amd64 Date: Sun Oct 21 17:22:28 2018 InterestingModules: rfcomm bnep btusb bluetooth MachineType: ASUSTeK Computer INC. EB1501P ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.18.0-10-generic root=UUID=515746f5-9b4c-4148-8e1e-012df202f447 ro splash quiet username=autostart,nodiskmount loglevel=0 vt.handoff=1 SourcePackage: bluez UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 01/02/2012 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 0501 dmi.board.asset.tag: To Be Filled By O.E.M. dmi.board.name: EB1501P dmi.board.vendor: ASUSTeK Computer INC. dmi.board.version: Rev 1.xx dmi.chassis.asset.tag: Asset-1234567890 dmi.chassis.type: 3 dmi.chassis.vendor: Chassis Manufacture dmi.chassis.version: Chassis Version dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr0501:bd01/02/2012:svnASUSTeKComputerINC.:pnEB1501P:pvrSystemVersion:rvnASUSTeKComputerINC.:rnEB1501P:rvrRev1.xx:cvnChassisManufacture:ct3:cvrChassisVersion: dmi.product.family: Eee Family dmi.product.name: EB1501P dmi.product.sku: To Be Filled By O.E.M. dmi.product.version: System Version dmi.sys.vendor: ASUSTeK Computer INC. hciconfig: hci0:Type: Primary Bus: USB BD Address: 00:11:67:00:00:00 ACL MTU: 1021:4 SCO MTU: 48:10 DOWN RX bytes:498 acl:0 sco:0 events:21 errors:0 TX bytes:95 acl:0 sco:0 commands:22 errors:0 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/1799064/+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 1801642] Re: Bluetooth mouse sleeps after 5 seconds of inactivity
I think you're looking at the wrong line there. The line you want is: Autosuspend for USB device ... It sounds like the line for your mouse says "Good", which is actually bad news. Because it means the kernel is powering down the USB device for power savings. So a delay is expected. Make sure the line for your mouse says "Bad" Bad Autosuspend for USB device ... so that it doesn't go to sleep. :) -- 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/1801642 Title: Bluetooth mouse sleeps after 5 seconds of inactivity Status in bluez package in Ubuntu: Invalid Bug description: I'm having bluetooth mouse lag issue. After leaving it stationary for 5 seconds, I have to move it for 2 seconds before the pointer starts moving. I recently upgraded to Cosmic 3 days ago (from Bionic). There was no issue in the first 3 days, including after suspend/restart/shutdown. This issue only appears starting today. I tried: 1. Running 'bluetoothctl' and then 'scan off'. The command failed to run with 'Failed to stop discovery: org.bluez.Error.Failed'. 2. modprobe -r btusb, then modprobe it again. 3. sudo sh -c 'echo N > /sys/module/drm_kms_helper/parameters/poll' 4. Disabling wifi. $ apt-cache policy bluez 5.50-0ubuntu1 $uname -a; lspci -nnk | grep -iA2 net; lsusb; dmesg | grep -i bluetooth; dmesg | grep -i firmware; lsmod | grep bluetooth 4.18.0-10-generic #11 02:00.0 Network controller [0280]: Intel Corporation Wireless 7260 [8086:08b1] (rev 73) Subsystem: Intel Corporation Dual Band Wireless-N 7260 [8086:4460] Kernel driver in use: iwlwifi 03:00.1 Ethernet controller [0200]: Realtek Semiconductor Co., Ltd. RTL8111/8168/8411 PCI Express Gigabit Ethernet Controller [10ec:8168] (rev 12) Subsystem: Dell RTL8111/8168/8411 PCI Express Gigabit Ethernet Controller [1028:05f9] Kernel driver in use: r8169 Kernel modules: r8169 Bus 001 Device 002: ID 8087:8000 Intel Corp. Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Bus 003 Device 003: ID 17e9:4301 DisplayLink Bus 003 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 002 Device 047: ID 04f3:0206 Elan Microelectronics Corp. Bus 002 Device 006: ID 8087:07dc Intel Corp. Bus 002 Device 034: ID 0461:4d51 Primax Electronics, Ltd 0Y357C PMX-MMOCZUL (B) [Dell Laser Mouse] Bus 002 Device 118: ID 0853:0132 Topre Corporation Bus 002 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub [ 287.361153] hid-generic 0005:046D:B012.0005: input,hidraw2: BLUETOOTH HID v0.14 Keyboard [MX Master] on FC:F8:AE:33:C7:31 bluetooth 548864 33 btrtl,btintel,btbcm,bnep,btusb,rfcomm ecdh_generic 24576 2 bluetooth ProblemType: Bug DistroRelease: Ubuntu 18.10 Package: bluez 5.50-0ubuntu1 ProcVersionSignature: Ubuntu 4.18.0-10.11-generic 4.18.12 Uname: Linux 4.18.0-10-generic x86_64 ApportVersion: 2.20.10-0ubuntu13 Architecture: amd64 CurrentDesktop: MATE Date: Mon Nov 5 13:40:01 2018 InstallationDate: Installed on 2018-07-08 (119 days ago) InstallationMedia: Ubuntu-MATE 18.04 LTS "Bionic Beaver" - Release amd64 (20180426) InterestingModules: rfcomm bnep btusb bluetooth MachineType: Dell Inc. Inspiron 7537 ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.18.0-10-generic root=/dev/mapper/ubuntu--mate--vg-root ro ipv6.disable=1 quiet splash i915.enable_psr=0 SourcePackage: bluez UpgradeStatus: Upgraded to cosmic on 2018-11-02 (3 days ago) dmi.bios.date: 10/31/2013 dmi.bios.vendor: Dell Inc. dmi.bios.version: A05 dmi.board.name: 07PF9F dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 8 dmi.chassis.vendor: Dell Inc. dmi.chassis.version: 0.1 dmi.modalias: dmi:bvnDellInc.:bvrA05:bd10/31/2013:svnDellInc.:pnInspiron7537:pvr:rvnDellInc.:rn07PF9F:rvrA00:cvnDellInc.:ct8:cvr0.1: dmi.product.family: Shark Bay ULT dmi.product.name: Inspiron 7537 dmi.product.sku: Inspiron 7537 dmi.sys.vendor: Dell Inc. hciconfig: hci0:Type: Primary Bus: USB BD Address: FC:F8:AE:33:C7:31 ACL MTU: 1021:5 SCO MTU: 96:5 UP RUNNING RX bytes:2380 acl:32 sco:0 events:208 errors:0 TX bytes:28560 acl:29 sco:0 commands:170 errors:0 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/1801642/+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 1801832] [NEW] Input method toggled when entering numbers with the numeric pad
You have been subscribed to a public bug: Ubuntu 18.04 LTS During the Chinese character input mode, when I enter numbers using the numeric pad, the input method will be switched to English automatically, which is very annoying. Any suggestions? ** Affects: ibus (Ubuntu) Importance: Undecided Status: New -- Input method toggled when entering numbers with the numeric pad https://bugs.launchpad.net/bugs/1801832 You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to ibus in Ubuntu. -- 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 1799064] Status changed to Confirmed
This change was made by a bot. ** Changed in: linux (Ubuntu) Status: New => Confirmed -- 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/1799064 Title: Bluetooth (ISSC USB dongle) refuses to power on after cosmic upgrade (works in kernel 4.15.0, but fails in 4.16 onward) Status in bluez package in Ubuntu: Invalid Status in linux package in Ubuntu: Confirmed Bug description: After upgrading from bionic to cosmic, Bluetooth has stopped working. It has worked fine for several versions before. Error message from syslog is: Failed to set mode: Failed (0x03) Which according to various random forum posts seems to suggest the device is not powering on. Powering on manually also does not work: % bluetoothctl Agent registered [bluetooth]# power on Failed to set power on: org.bluez.Error.Failed And results in the same set mode failure getting logged again in syslog. hciconfig reports the device as down: % sudo hciconfig hci0: Type: Primary Bus: USB BD Address: 00:11:67:00:00:00 ACL MTU: 1021:4 SCO MTU: 48:10 DOWN RX bytes:498 acl:0 sco:0 events:21 errors:0 TX bytes:101 acl:0 sco:0 commands:24 errors:0 And, again, it refuses to power on: % sudo hciconfig hci0 up Can't init device hci0: Connection timed out (110) rfkill does not appear to be blocking it: % rfkill list 0: hci0: Bluetooth Soft blocked: no Hard blocked: no 1: phy0: Wireless LAN Soft blocked: no Hard blocked: no And systemd-rfkill.service is masked: ~ % sudo systemctl status systemd-rfkill.service ● systemd-rfkill.service Loaded: masked (Reason: Unit systemd-rfkill.service is masked.) [..] The system does not have tlp installed. I have tried numerous reboots, power offs, and moving the USB Bluetooth adapter to different ports, with no change in result. I have also tried unloading and loading btusb. The adapter is a cheap noname thing off of eBay, I trust the system report will provide every possibly interesting detail about it. ProblemType: Bug DistroRelease: Ubuntu 18.10 Package: bluez 5.50-0ubuntu1 ProcVersionSignature: Ubuntu 4.18.0-10.11-generic 4.18.12 Uname: Linux 4.18.0-10-generic x86_64 NonfreeKernelModules: nvidia ApportVersion: 2.20.10-0ubuntu13 Architecture: amd64 Date: Sun Oct 21 17:22:28 2018 InterestingModules: rfcomm bnep btusb bluetooth MachineType: ASUSTeK Computer INC. EB1501P ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.18.0-10-generic root=UUID=515746f5-9b4c-4148-8e1e-012df202f447 ro splash quiet username=autostart,nodiskmount loglevel=0 vt.handoff=1 SourcePackage: bluez UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 01/02/2012 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 0501 dmi.board.asset.tag: To Be Filled By O.E.M. dmi.board.name: EB1501P dmi.board.vendor: ASUSTeK Computer INC. dmi.board.version: Rev 1.xx dmi.chassis.asset.tag: Asset-1234567890 dmi.chassis.type: 3 dmi.chassis.vendor: Chassis Manufacture dmi.chassis.version: Chassis Version dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr0501:bd01/02/2012:svnASUSTeKComputerINC.:pnEB1501P:pvrSystemVersion:rvnASUSTeKComputerINC.:rnEB1501P:rvrRev1.xx:cvnChassisManufacture:ct3:cvrChassisVersion: dmi.product.family: Eee Family dmi.product.name: EB1501P dmi.product.sku: To Be Filled By O.E.M. dmi.product.version: System Version dmi.sys.vendor: ASUSTeK Computer INC. hciconfig: hci0:Type: Primary Bus: USB BD Address: 00:11:67:00:00:00 ACL MTU: 1021:4 SCO MTU: 48:10 DOWN RX bytes:498 acl:0 sco:0 events:21 errors:0 TX bytes:95 acl:0 sco:0 commands:22 errors:0 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/1799064/+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 1799007] Re: [System76 Oryx Pro] no sound after 18.10 upgrade
Yes, I suspected as much. System76 wouldn't ship a laptop without working audio on Ubuntu. It sounds like that machine has gone through a couple of upgrades: DistroRelease: Pop!_OS 18.10 InstallationDate: Installed on 2018-03-05 (230 days ago) InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20180105.1) I can't tell what has been broken in the process, but it does look like pulseaudio since 'pacmd' isn't working for you. I suggest: (a) Try to reinstall pulseaudio packages, like: sudo apt install --reinstall pulseaudio or (b) Back up your data and then reinstall fresh from http://releases.ubuntu.com/18.10/ We may never know what went wrong on the machine before 18.10 reaches end of life in July 2019. ** Changed in: pulseaudio (Ubuntu) Status: Incomplete => Triaged ** Changed in: pulseaudio (Ubuntu) Importance: Undecided => Medium -- 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/1799007 Title: [System76 Oryx Pro] no sound after 18.10 upgrade Status in pulseaudio package in Ubuntu: Triaged Bug description: After upgrading to 18.10, the sound in my System76 Oryx Pro no longer works, it no longer shows any of the audio output devices, not even the builtin HDMI which usually always shows. Not sure what happened, but this is a major regression and needs to be fixed. Note that this isn't the same as the bug with Timidity taking exclusive soundcard access (https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1797714) as I don't have any timidity packages installed. --- ProblemType: Bug ApportVersion: 2.20.10-0ubuntu13 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: tessa 11703 F pulseaudio /dev/snd/controlC0: tessa 11703 F pulseaudio /dev/snd/pcmC0D0c: tessa 11703 F...m pulseaudio /dev/snd/pcmC0D0p: tessa 11703 F...m pulseaudio CurrentDesktop: pop:GNOME DistroRelease: Pop!_OS 18.10 InstallationDate: Installed on 2018-03-05 (230 days ago) InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20180105.1) NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair nvidia_modeset nvidia Package: pulseaudio 1:12.2-0ubuntu4 [origin: Ubuntu] PackageArchitecture: amd64 ProcVersionSignature: Ubuntu 4.18.0-10.11-generic 4.18.12 PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: Daemon not responding. Tags: third-party-packages cosmic Uname: Linux 4.18.0-10-generic x86_64 UnreportableReason: This is not an official Pop!_OS package. Please remove any third party package and try again. UpgradeStatus: Upgraded to cosmic on 2018-10-18 (3 days ago) UserGroups: adm audio cdrom chrome-remote-desktop dip docker libvirt lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 02/20/2017 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 1.05.02dRSA2 dmi.board.asset.tag: Tag 12345 dmi.board.name: Oryx Pro dmi.board.vendor: System76 dmi.board.version: oryp3-ess dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: System76 dmi.chassis.version: N/A dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr1.05.02dRSA2:bd02/20/2017:svnSystem76:pnOryxPro:pvroryp3-ess:rvnSystem76:rnOryxPro:rvroryp3-ess:cvnSystem76:ct10:cvrN/A: dmi.product.family: Not Applicable dmi.product.name: Oryx Pro dmi.product.sku: Not Applicable dmi.product.version: oryp3-ess dmi.sys.vendor: System76 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1799007/+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 1799064] Re: Bluetooth refuses to power on after cosmic upgrade (works in kernel 4.15.0, but fails in 4.16 onward)
** Summary changed: - Bluetooth refuses to power on after cosmic upgrade + Bluetooth refuses to power on after cosmic upgrade (works in kernel 4.15.0, but fails in 4.16 onward) ** Changed in: linux (Ubuntu) Status: Incomplete => New ** Changed in: bluez (Ubuntu) Status: Incomplete => Invalid ** Summary changed: - Bluetooth refuses to power on after cosmic upgrade (works in kernel 4.15.0, but fails in 4.16 onward) + Bluetooth (ISSC USB dongle) refuses to power on after cosmic upgrade (works in kernel 4.15.0, but fails in 4.16 onward) -- 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/1799064 Title: Bluetooth (ISSC USB dongle) refuses to power on after cosmic upgrade (works in kernel 4.15.0, but fails in 4.16 onward) Status in bluez package in Ubuntu: Invalid Status in linux package in Ubuntu: New Bug description: After upgrading from bionic to cosmic, Bluetooth has stopped working. It has worked fine for several versions before. Error message from syslog is: Failed to set mode: Failed (0x03) Which according to various random forum posts seems to suggest the device is not powering on. Powering on manually also does not work: % bluetoothctl Agent registered [bluetooth]# power on Failed to set power on: org.bluez.Error.Failed And results in the same set mode failure getting logged again in syslog. hciconfig reports the device as down: % sudo hciconfig hci0: Type: Primary Bus: USB BD Address: 00:11:67:00:00:00 ACL MTU: 1021:4 SCO MTU: 48:10 DOWN RX bytes:498 acl:0 sco:0 events:21 errors:0 TX bytes:101 acl:0 sco:0 commands:24 errors:0 And, again, it refuses to power on: % sudo hciconfig hci0 up Can't init device hci0: Connection timed out (110) rfkill does not appear to be blocking it: % rfkill list 0: hci0: Bluetooth Soft blocked: no Hard blocked: no 1: phy0: Wireless LAN Soft blocked: no Hard blocked: no And systemd-rfkill.service is masked: ~ % sudo systemctl status systemd-rfkill.service ● systemd-rfkill.service Loaded: masked (Reason: Unit systemd-rfkill.service is masked.) [..] The system does not have tlp installed. I have tried numerous reboots, power offs, and moving the USB Bluetooth adapter to different ports, with no change in result. I have also tried unloading and loading btusb. The adapter is a cheap noname thing off of eBay, I trust the system report will provide every possibly interesting detail about it. ProblemType: Bug DistroRelease: Ubuntu 18.10 Package: bluez 5.50-0ubuntu1 ProcVersionSignature: Ubuntu 4.18.0-10.11-generic 4.18.12 Uname: Linux 4.18.0-10-generic x86_64 NonfreeKernelModules: nvidia ApportVersion: 2.20.10-0ubuntu13 Architecture: amd64 Date: Sun Oct 21 17:22:28 2018 InterestingModules: rfcomm bnep btusb bluetooth MachineType: ASUSTeK Computer INC. EB1501P ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.18.0-10-generic root=UUID=515746f5-9b4c-4148-8e1e-012df202f447 ro splash quiet username=autostart,nodiskmount loglevel=0 vt.handoff=1 SourcePackage: bluez UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 01/02/2012 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 0501 dmi.board.asset.tag: To Be Filled By O.E.M. dmi.board.name: EB1501P dmi.board.vendor: ASUSTeK Computer INC. dmi.board.version: Rev 1.xx dmi.chassis.asset.tag: Asset-1234567890 dmi.chassis.type: 3 dmi.chassis.vendor: Chassis Manufacture dmi.chassis.version: Chassis Version dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr0501:bd01/02/2012:svnASUSTeKComputerINC.:pnEB1501P:pvrSystemVersion:rvnASUSTeKComputerINC.:rnEB1501P:rvrRev1.xx:cvnChassisManufacture:ct3:cvrChassisVersion: dmi.product.family: Eee Family dmi.product.name: EB1501P dmi.product.sku: To Be Filled By O.E.M. dmi.product.version: System Version dmi.sys.vendor: ASUSTeK Computer INC. hciconfig: hci0:Type: Primary Bus: USB BD Address: 00:11:67:00:00:00 ACL MTU: 1021:4 SCO MTU: 48:10 DOWN RX bytes:498 acl:0 sco:0 events:21 errors:0 TX bytes:95 acl:0 sco:0 commands:22 errors:0 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/1799064/+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 1747175] Re: [Inspiron 5559, Realtek ALC3234, Black Headphone Out, Front] No sound at all
My problem is with Intel on board sound. alsamixer shows as: [PCH]: HDA-Intel - HDA Intel PCH │ │ HDA Intel PCH at 0xdc24 irq 127 │ Unable to raise the indicated level on either of the Speaker channels. The alsamixer display for those stays at 00. -- 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/1747175 Title: [Inspiron 5559, Realtek ALC3234, Black Headphone Out, Front] No sound at all Status in alsa-driver package in Ubuntu: Confirmed Bug description: My internal speaker works fine People say it is a problem of ALSADRIVER Headphone jack works in windows Issue lies with ubuntu ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: alsa-base 1.0.25+dfsg-0ubuntu5 ProcVersionSignature: Ubuntu 4.4.0-112.135-lowlatency 4.4.98 Uname: Linux 4.4.0-112-lowlatency x86_64 ApportVersion: 2.20.1-0ubuntu2.15 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: harish 2674 F pulseaudio CurrentDesktop: XFCE Date: Sat Feb 3 23:42:53 2018 InstallationDate: Installed on 2016-07-06 (577 days ago) InstallationMedia: Ubuntu-Studio 16.04 LTS "Xenial Xerus" - Release amd64 (20160420.1) PackageArchitecture: all SourcePackage: alsa-driver Symptom: audio Symptom_AlsaPlaybackTest: ALSA playback test through plughw:PCH failed Symptom_Card: Built-in Audio - HDA Intel PCH Symptom_DevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: harish 2674 F pulseaudio Symptom_Jack: Black Headphone Out, Front Symptom_Type: No sound at all Title: [Inspiron 5559, Realtek ALC3234, Black Headphone Out, Front] No sound at all UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 08/25/2016 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.2.3 dmi.board.name: 04D1V1 dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 9 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr1.2.3:bd08/25/2016:svnDellInc.:pnInspiron5559:pvr:rvnDellInc.:rn04D1V1:rvrA00:cvnDellInc.:ct9:cvr: dmi.product.name: Inspiron 5559 dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1747175/+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 1801642] Re: Bluetooth mouse sleeps after 5 seconds of inactivity
** Summary changed: - Bluetooth mouse sleep after 5 seconds of inactivity + Bluetooth mouse sleeps after 5 seconds of inactivity -- 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/1801642 Title: Bluetooth mouse sleeps after 5 seconds of inactivity Status in bluez package in Ubuntu: Invalid Bug description: I'm having bluetooth mouse lag issue. After leaving it stationary for 5 seconds, I have to move it for 2 seconds before the pointer starts moving. I recently upgraded to Cosmic 3 days ago (from Bionic). There was no issue in the first 3 days, including after suspend/restart/shutdown. This issue only appears starting today. I tried: 1. Running 'bluetoothctl' and then 'scan off'. The command failed to run with 'Failed to stop discovery: org.bluez.Error.Failed'. 2. modprobe -r btusb, then modprobe it again. 3. sudo sh -c 'echo N > /sys/module/drm_kms_helper/parameters/poll' 4. Disabling wifi. $ apt-cache policy bluez 5.50-0ubuntu1 $uname -a; lspci -nnk | grep -iA2 net; lsusb; dmesg | grep -i bluetooth; dmesg | grep -i firmware; lsmod | grep bluetooth 4.18.0-10-generic #11 02:00.0 Network controller [0280]: Intel Corporation Wireless 7260 [8086:08b1] (rev 73) Subsystem: Intel Corporation Dual Band Wireless-N 7260 [8086:4460] Kernel driver in use: iwlwifi 03:00.1 Ethernet controller [0200]: Realtek Semiconductor Co., Ltd. RTL8111/8168/8411 PCI Express Gigabit Ethernet Controller [10ec:8168] (rev 12) Subsystem: Dell RTL8111/8168/8411 PCI Express Gigabit Ethernet Controller [1028:05f9] Kernel driver in use: r8169 Kernel modules: r8169 Bus 001 Device 002: ID 8087:8000 Intel Corp. Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Bus 003 Device 003: ID 17e9:4301 DisplayLink Bus 003 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 002 Device 047: ID 04f3:0206 Elan Microelectronics Corp. Bus 002 Device 006: ID 8087:07dc Intel Corp. Bus 002 Device 034: ID 0461:4d51 Primax Electronics, Ltd 0Y357C PMX-MMOCZUL (B) [Dell Laser Mouse] Bus 002 Device 118: ID 0853:0132 Topre Corporation Bus 002 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub [ 287.361153] hid-generic 0005:046D:B012.0005: input,hidraw2: BLUETOOTH HID v0.14 Keyboard [MX Master] on FC:F8:AE:33:C7:31 bluetooth 548864 33 btrtl,btintel,btbcm,bnep,btusb,rfcomm ecdh_generic 24576 2 bluetooth ProblemType: Bug DistroRelease: Ubuntu 18.10 Package: bluez 5.50-0ubuntu1 ProcVersionSignature: Ubuntu 4.18.0-10.11-generic 4.18.12 Uname: Linux 4.18.0-10-generic x86_64 ApportVersion: 2.20.10-0ubuntu13 Architecture: amd64 CurrentDesktop: MATE Date: Mon Nov 5 13:40:01 2018 InstallationDate: Installed on 2018-07-08 (119 days ago) InstallationMedia: Ubuntu-MATE 18.04 LTS "Bionic Beaver" - Release amd64 (20180426) InterestingModules: rfcomm bnep btusb bluetooth MachineType: Dell Inc. Inspiron 7537 ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.18.0-10-generic root=/dev/mapper/ubuntu--mate--vg-root ro ipv6.disable=1 quiet splash i915.enable_psr=0 SourcePackage: bluez UpgradeStatus: Upgraded to cosmic on 2018-11-02 (3 days ago) dmi.bios.date: 10/31/2013 dmi.bios.vendor: Dell Inc. dmi.bios.version: A05 dmi.board.name: 07PF9F dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 8 dmi.chassis.vendor: Dell Inc. dmi.chassis.version: 0.1 dmi.modalias: dmi:bvnDellInc.:bvrA05:bd10/31/2013:svnDellInc.:pnInspiron7537:pvr:rvnDellInc.:rn07PF9F:rvrA00:cvnDellInc.:ct8:cvr0.1: dmi.product.family: Shark Bay ULT dmi.product.name: Inspiron 7537 dmi.product.sku: Inspiron 7537 dmi.sys.vendor: Dell Inc. hciconfig: hci0:Type: Primary Bus: USB BD Address: FC:F8:AE:33:C7:31 ACL MTU: 1021:5 SCO MTU: 96:5 UP RUNNING RX bytes:2380 acl:32 sco:0 events:208 errors:0 TX bytes:28560 acl:29 sco:0 commands:170 errors:0 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/1801642/+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 1358762] Re: Included gzip 1.2.4 has several vulnerabilities
** CVE added: https://cve.mitre.org/cgi-bin/cvename.cgi?name=2001-1228 -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to klibc in Ubuntu. https://bugs.launchpad.net/bugs/1358762 Title: Included gzip 1.2.4 has several vulnerabilities Status in klibc: New Status in klibc package in Ubuntu: Confirmed Bug description: The included gzip version is quite old (version 1.2.4) and has several security vulnerabilities. Check http://web.nvd.nist.gov/view/vuln/search- results?adv_search=true=on_version=cpe:/a:gnu:gzip:1.2.4 for example. I explicitly checked for CVE-2001-1228, which was not fixed by a patch in the klibc package, so I assume the other vulnerabilities are not fixed either. I think it would be a good idea to update the included gzip to a current version. To manage notifications about this bug go to: https://bugs.launchpad.net/klibc/+bug/1358762/+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 1801642] Re: Bluetooth mouse sleep after 5 seconds of inactivity
Ok, after another waking from suspend, the issue comes back again. powertop shows "Bluetooth device interface status" is good. I can't identify which entry is the mouse, but the only bad USB devices are the keyboard and touchscreen. Installing powertop somehow resolve this issue (for now). I'll check again tomorrow. I'll close this report if no issue in a week. -- 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/1801642 Title: Bluetooth mouse sleep after 5 seconds of inactivity Status in bluez package in Ubuntu: Invalid Bug description: I'm having bluetooth mouse lag issue. After leaving it stationary for 5 seconds, I have to move it for 2 seconds before the pointer starts moving. I recently upgraded to Cosmic 3 days ago (from Bionic). There was no issue in the first 3 days, including after suspend/restart/shutdown. This issue only appears starting today. I tried: 1. Running 'bluetoothctl' and then 'scan off'. The command failed to run with 'Failed to stop discovery: org.bluez.Error.Failed'. 2. modprobe -r btusb, then modprobe it again. 3. sudo sh -c 'echo N > /sys/module/drm_kms_helper/parameters/poll' 4. Disabling wifi. $ apt-cache policy bluez 5.50-0ubuntu1 $uname -a; lspci -nnk | grep -iA2 net; lsusb; dmesg | grep -i bluetooth; dmesg | grep -i firmware; lsmod | grep bluetooth 4.18.0-10-generic #11 02:00.0 Network controller [0280]: Intel Corporation Wireless 7260 [8086:08b1] (rev 73) Subsystem: Intel Corporation Dual Band Wireless-N 7260 [8086:4460] Kernel driver in use: iwlwifi 03:00.1 Ethernet controller [0200]: Realtek Semiconductor Co., Ltd. RTL8111/8168/8411 PCI Express Gigabit Ethernet Controller [10ec:8168] (rev 12) Subsystem: Dell RTL8111/8168/8411 PCI Express Gigabit Ethernet Controller [1028:05f9] Kernel driver in use: r8169 Kernel modules: r8169 Bus 001 Device 002: ID 8087:8000 Intel Corp. Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Bus 003 Device 003: ID 17e9:4301 DisplayLink Bus 003 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 002 Device 047: ID 04f3:0206 Elan Microelectronics Corp. Bus 002 Device 006: ID 8087:07dc Intel Corp. Bus 002 Device 034: ID 0461:4d51 Primax Electronics, Ltd 0Y357C PMX-MMOCZUL (B) [Dell Laser Mouse] Bus 002 Device 118: ID 0853:0132 Topre Corporation Bus 002 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub [ 287.361153] hid-generic 0005:046D:B012.0005: input,hidraw2: BLUETOOTH HID v0.14 Keyboard [MX Master] on FC:F8:AE:33:C7:31 bluetooth 548864 33 btrtl,btintel,btbcm,bnep,btusb,rfcomm ecdh_generic 24576 2 bluetooth ProblemType: Bug DistroRelease: Ubuntu 18.10 Package: bluez 5.50-0ubuntu1 ProcVersionSignature: Ubuntu 4.18.0-10.11-generic 4.18.12 Uname: Linux 4.18.0-10-generic x86_64 ApportVersion: 2.20.10-0ubuntu13 Architecture: amd64 CurrentDesktop: MATE Date: Mon Nov 5 13:40:01 2018 InstallationDate: Installed on 2018-07-08 (119 days ago) InstallationMedia: Ubuntu-MATE 18.04 LTS "Bionic Beaver" - Release amd64 (20180426) InterestingModules: rfcomm bnep btusb bluetooth MachineType: Dell Inc. Inspiron 7537 ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.18.0-10-generic root=/dev/mapper/ubuntu--mate--vg-root ro ipv6.disable=1 quiet splash i915.enable_psr=0 SourcePackage: bluez UpgradeStatus: Upgraded to cosmic on 2018-11-02 (3 days ago) dmi.bios.date: 10/31/2013 dmi.bios.vendor: Dell Inc. dmi.bios.version: A05 dmi.board.name: 07PF9F dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 8 dmi.chassis.vendor: Dell Inc. dmi.chassis.version: 0.1 dmi.modalias: dmi:bvnDellInc.:bvrA05:bd10/31/2013:svnDellInc.:pnInspiron7537:pvr:rvnDellInc.:rn07PF9F:rvrA00:cvnDellInc.:ct8:cvr0.1: dmi.product.family: Shark Bay ULT dmi.product.name: Inspiron 7537 dmi.product.sku: Inspiron 7537 dmi.sys.vendor: Dell Inc. hciconfig: hci0:Type: Primary Bus: USB BD Address: FC:F8:AE:33:C7:31 ACL MTU: 1021:5 SCO MTU: 96:5 UP RUNNING RX bytes:2380 acl:32 sco:0 events:208 errors:0 TX bytes:28560 acl:29 sco:0 commands:170 errors:0 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/1801642/+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 1786574] Re: remove i2c-i801 from blacklist
** Changed in: hwe-next Status: Fix Committed => Fix Released -- 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/1786574 Title: remove i2c-i801 from blacklist Status in HWE Next: Fix Released Status in OEM Priority Project: New Status in kmod package in Ubuntu: Fix Committed Status in kmod source package in Xenial: Fix Released Status in kmod source package in Bionic: Fix Released Status in kmod source package in Cosmic: Fix Released Bug description: SRU justification [Impact] Many modern notebooks need i2c-i801 kernel module to function, but it is blacklisted by /etc/modprobe/blacklist.conf, which gives a very poor user experience. [Test case] 1. Install Ubuntu 2. Check touchpad works or not 3. Install the fixed kmod package 4. Confirm touchpad works [Regression Potential] i2c-i801 was blacklisted due to bug 16602. The user complains an HP Compaq nc6000 notebook cannot suspend without blacklisting i2c-i801. While this is a way to workaround the suspend issue, the proper fix should be in linux kernel. Since nc6000 was a machine sold in 2004, it is too difficult to find someone to verify if it will regress due to this SRU. The rationale to blacklist it is: https://bugs.launchpad.net/ubuntu/+source/hotplug/+bug/16602/comments/5, however it is no longer valid nowadays on modern computers. Besides, there look like to be a quirk in linux kernel that fixes it: https://github.com/torvalds/linux/blame/master/drivers/pci/quirks.c#L1434 [Other Info] rationale of i2c_i801 driver blacklist: https://answers.launchpad.net/ubuntu/+source/kmod/+question/269329 --- Original bug report: We have a Lenovo Thinkpad machine that requires i2c-i801 kernel module to work, but it is listed in /etc/modprobe/blacklist.conf in Ubuntu. To use the touchpad, users have to remove the i2c-i801 line manually. i2c-i801 in blacklist.conf is a very old workaround to fix HP compaq nc6000 (Bug #16602), this module should be removed from blacklist. There is also another bug (Bug #1475945) that needs this module for Acer trackpad to work. To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/1786574/+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 1795921] Re: Out-of-Bounds write in systemd-networkd dhcpv6 option handling
@yassine-mrabet - In general, Ubuntu does not upgrade major versions of
software and instead backports security fixes to the current version -
also we track CVEs independently in our own CVE tracker - in this case
please see https://people.canonical.com/~ubuntu-
security/cve/2018/CVE-2018-15688.html
Here you can see this is resolved for bionic in version 237-3ubuntu10.4
which is available in the bionic-security pocket. So simply doing an
'sudo apt-get update && sudo apt-get upgrade' should make this
available.
--
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/1795921
Title:
Out-of-Bounds write in systemd-networkd dhcpv6 option handling
Status in systemd package in Ubuntu:
Confirmed
Bug description:
systemd-networkd contains a DHCPv6 client which is written from
scratch and can be spawned automatically on managed interfaces when
IPv6 router advertisement are received:
"Note that DHCPv6 will by default be triggered by Router Advertisement, if
that is enabled, regardless of this parameter. By enabling DHCPv6 support
explicitly, the DHCPv6 client will be started regardless of the presence of
routers on the link, or what flags the routers pass"
(https://www.freedesktop.org/software/systemd/man/systemd.network.html)
The function dhcp6_option_append_ia function is used to encode Identity
Associations received by the server into the options buffer of an outgoing
DHCPv6 packet:
//
https://github.com/systemd/systemd/blob/master/src/libsystemd-network/dhcp6-option.c#L82
int dhcp6_option_append_ia(uint8_t **buf, size_t *buflen, DHCP6IA *ia) {
uint16_t len;
uint8_t *ia_hdr;
size_t iaid_offset, ia_buflen, ia_addrlen = 0;
DHCP6Address *addr;
int r;
assert_return(buf && *buf && buflen && ia, -EINVAL);
switch (ia->type) {
case SD_DHCP6_OPTION_IA_NA:
len = DHCP6_OPTION_IA_NA_LEN;
iaid_offset = offsetof(DHCP6IA, ia_na);
break;
case SD_DHCP6_OPTION_IA_TA:
len = DHCP6_OPTION_IA_TA_LEN;
iaid_offset = offsetof(DHCP6IA, ia_ta);
break;
default:
return -EINVAL;
}
A: if (*buflen < len)
return -ENOBUFS;
ia_hdr = *buf;
ia_buflen = *buflen;
*buf += sizeof(DHCP6Option);
B: *buflen -= sizeof(DHCP6Option);
C: memcpy(*buf, (char*) ia + iaid_offset, len);
*buf += len;
D: *buflen -= len;
E:LIST_FOREACH(addresses, addr, ia->addresses) {
r = option_append_hdr(buf, buflen, SD_DHCP6_OPTION_IAADDR,
sizeof(addr->iaaddr));
if (r < 0)
return r;
memcpy(*buf, >iaaddr, sizeof(addr->iaaddr));
*buf += sizeof(addr->iaaddr);
*buflen -= sizeof(addr->iaaddr);
ia_addrlen += sizeof(DHCP6Option) + sizeof(addr->iaaddr);
}
r = option_append_hdr(_hdr, _buflen, ia->type, len +
ia_addrlen);
if (r < 0)
return r;
return 0;
}
The function receives a pointer to the option buffer buf, it's remaining size
buflen and the IA to be added to the buffer. While the check at (A) tries to
ensure that the buffer has enough space left to store the IA option, it does
not take the additional 4 bytes from the DHCP6Option header into account (B).
Due to this the memcpy at (C) can go out-of-bound and *buflen can underflow in
(D) giving an attacker a very powerful and largely controlled OOB heap write
starting at (E).
The overflow can be triggered relatively easy by advertising a DHCPv6
server with a server-id >= 493 characters long. This will trigger the
following code once the client tries to create a REQUEST message:
//https://github.com/systemd/systemd/blob/7bcf8123c0305131ace02480763377af974924ef/src/libsystemd-network/sd-dhcp6-client.c#L493
case DHCP6_STATE_REQUEST:
case DHCP6_STATE_RENEW:
if (client->state == DHCP6_STATE_REQUEST)
message->type = DHCP6_REQUEST;
else
message->type = DHCP6_RENEW;
A: r = dhcp6_option_append(, ,
SD_DHCP6_OPTION_SERVERID,
client->lease->serverid_len,
client->lease->serverid);
if (r < 0)
return r;
if (FLAGS_SET(client->request, DHCP6_REQUEST_IA_NA)) {
B: r = dhcp6_option_append_ia(, ,
>lease->ia);
if (r < 0)
[Touch-packages] [Bug 1801128] Re: OpenSSH 7.7 -w tunnel bug
For simplicity, here's the patch that fixes this bug (and is included in
openssh 7.8):
diff --git a/openbsd-compat/port-net.c b/openbsd-compat/port-net.c
index 7050629c..bb535626 100644
--- a/openbsd-compat/port-net.c
+++ b/openbsd-compat/port-net.c
@@ -185,7 +185,7 @@ sys_tun_open(int tun, int mode, char **ifname)
else
debug("%s: %s mode %d fd %d", __func__, ifr.ifr_name, mode, fd);
- if (ifname != NULL && (*ifname = strdup(ifr.ifr_name)))
+ if (ifname != NULL && (*ifname = strdup(ifr.ifr_name)) == NULL)
goto failed;
return (fd);
@@ -272,7 +272,7 @@ sys_tun_open(int tun, int mode, char **ifname)
goto failed;
}
- if (ifname != NULL && (*ifname = strdup(ifr.ifr_name)))
+ if (ifname != NULL && (*ifname = strdup(ifr.ifr_name)) == NULL)
goto failed;
close(sock);
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to openssh in Ubuntu.
https://bugs.launchpad.net/bugs/1801128
Title:
OpenSSH 7.7 -w tunnel bug
Status in openssh package in Ubuntu:
New
Bug description:
Just upgraded to cosmic, which picks up OpenSSH 7.7.
OpenSSH 7.7 has known bug
https://bugzilla.mindrot.org/show_bug.cgi?id=2855 which is fixed in
OpenSSH 7.8. It's a regression that completely breaks -w tunneling.
The OpenSSH bug contains a trivial two-line patch to fix the bug. I
downloaded the Ubuntu openssh package source, applied the patch and
rebuilt, and can confirm that is does fix the problem.
Any chance we could get this patch backported to Cosmic?
ProblemType: Bug
DistroRelease: Ubuntu 18.10
Package: openssh-client 1:7.7p1-4
ProcVersionSignature: Ubuntu 4.18.0-10.11-generic 4.18.12
Uname: Linux 4.18.0-10-generic x86_64
ApportVersion: 2.20.10-0ubuntu13
Architecture: amd64
Date: Thu Nov 1 09:36:16 2018
ProcEnviron:
TERM=xterm-256color
PATH=(custom, no user)
XDG_RUNTIME_DIR=
LANG=en_US.UTF-8
SHELL=/bin/bash
RelatedPackageVersions:
ssh-askpass N/A
libpam-sshN/A
keychain N/A
ssh-askpass-gnome N/A
SSHClientVersion: OpenSSH_7.7p1 Ubuntu-4, OpenSSL 1.0.2n 7 Dec 2017
SourcePackage: openssh
UpgradeStatus: Upgraded to cosmic on 2018-11-01 (0 days ago)
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/openssh/+bug/1801128/+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 1760569] Re: Nautilus crashes in g_free -> g_bookmark_file_move_item -> gtk_recent_manager_move_item -> nautilus_recent_update_file_moved
** Also affects: glib2.0 (Ubuntu) Importance: Undecided Status: New ** Changed in: glib2.0 (Ubuntu) Status: New => In Progress ** Changed in: glib2.0 (Ubuntu) Importance: Undecided => Medium ** Changed in: glib2.0 (Ubuntu) Assignee: (unassigned) => Marco Trevisan (Treviño) (3v1n0) ** Description changed: - Unknown circumstances + Happens when there's a "rename" to a file to its same value, no known + reproducer though. + + Upstream fix: https://gitlab.gnome.org/GNOME/glib/merge_requests/456 https://errors.ubuntu.com/problem/1aa40f9ef3a1f77a05e71d0a69351c2ae5a7fb45 https://errors.ubuntu.com/problem/9f0f3a1aee06700bc4ac107754f909801c4641b9 - ProblemType: CrashDistroRelease: Ubuntu 18.04 Package: nautilus 1:3.26.3-0ubuntu1 ProcVersionSignature: Ubuntu 4.15.0-13.14-generic 4.15.10 Uname: Linux 4.15.0-13-generic x86_64 ApportVersion: 2.20.9-0ubuntu2 Architecture: amd64 AssertionMessage: munmap_chunk(): invalid pointer CurrentDesktop: ubuntu:GNOME Date: Mon Apr 2 09:04:45 2018 ExecutablePath: /usr/bin/nautilus GsettingsChanges: b'org.gnome.nautilus.preferences' b'default-folder-viewer' b"'list-view'" b'org.gnome.nautilus.window-state' b'sidebar-width' b'223' b'org.gnome.nautilus.window-state' b'geometry' b"'890x550+117+77'" b'org.gnome.nautilus.window-state' b'maximized' b'true' InstallationDate: Installed on 2018-03-31 (2 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Alpha amd64 (20180329) ProcCmdline: /usr/bin/nautilus --gapplication-service ProcEnviron: XDG_RUNTIME_DIR= SHELL=/bin/bash LANGUAGE=en_GB:en PATH=(custom, no user) - LANG=en_GB.UTF-8 - Signal: 6SourcePackage: nautilus + LANG=en_GB.UTF-8Signal: 6SourcePackage: nautilus StacktraceTop: __libc_message (action=action@entry=do_abort, fmt=fmt@entry=0x7f1a46fcfb9a "%s\n") at ../sysdeps/posix/libc_fatal.c:181 malloc_printerr (str=str@entry=0x7f1a46fd17a8 "munmap_chunk(): invalid pointer") at malloc.c:5350 munmap_chunk (p=0x55f2e55b71f0) at malloc.c:2846 __GI___libc_free (mem=0x55f2e55b7200) at malloc.c:3117 g_bookmark_file_move_item () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 Title: nautilus assert failure: munmap_chunk(): invalid pointer UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo usr_lib_nautilus: -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to glib2.0 in Ubuntu. https://bugs.launchpad.net/bugs/1760569 Title: Nautilus crashes in g_free -> g_bookmark_file_move_item -> gtk_recent_manager_move_item -> nautilus_recent_update_file_moved Status in glib2.0 package in Ubuntu: In Progress Status in nautilus package in Ubuntu: Triaged Bug description: Happens when there's a "rename" to a file to its same value, no known reproducer though. Upstream fix: https://gitlab.gnome.org/GNOME/glib/merge_requests/456 https://errors.ubuntu.com/problem/1aa40f9ef3a1f77a05e71d0a69351c2ae5a7fb45 https://errors.ubuntu.com/problem/9f0f3a1aee06700bc4ac107754f909801c4641b9 ProblemType: CrashDistroRelease: Ubuntu 18.04 Package: nautilus 1:3.26.3-0ubuntu1 ProcVersionSignature: Ubuntu 4.15.0-13.14-generic 4.15.10 Uname: Linux 4.15.0-13-generic x86_64 ApportVersion: 2.20.9-0ubuntu2 Architecture: amd64 AssertionMessage: munmap_chunk(): invalid pointer CurrentDesktop: ubuntu:GNOME Date: Mon Apr 2 09:04:45 2018 ExecutablePath: /usr/bin/nautilus GsettingsChanges: b'org.gnome.nautilus.preferences' b'default-folder-viewer' b"'list-view'" b'org.gnome.nautilus.window-state' b'sidebar-width' b'223' b'org.gnome.nautilus.window-state' b'geometry' b"'890x550+117+77'" b'org.gnome.nautilus.window-state' b'maximized' b'true' InstallationDate: Installed on 2018-03-31 (2 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Alpha amd64 (20180329) ProcCmdline: /usr/bin/nautilus --gapplication-service ProcEnviron: XDG_RUNTIME_DIR= SHELL=/bin/bash LANGUAGE=en_GB:en PATH=(custom, no user) LANG=en_GB.UTF-8Signal: 6SourcePackage: nautilus StacktraceTop: __libc_message (action=action@entry=do_abort, fmt=fmt@entry=0x7f1a46fcfb9a "%s\n") at ../sysdeps/posix/libc_fatal.c:181 malloc_printerr (str=str@entry=0x7f1a46fd17a8 "munmap_chunk(): invalid pointer") at malloc.c:5350 munmap_chunk (p=0x55f2e55b71f0) at malloc.c:2846 __GI___libc_free (mem=0x55f2e55b7200) at malloc.c:3117 g_bookmark_file_move_item () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 Title: nautilus assert failure: munmap_chunk(): invalid pointer UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo usr_lib_nautilus: To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/glib2.0/+bug/1760569/+subscriptions -- Mailing list:
[Touch-packages] [Bug 1740894] Re: KEY_RFKILL is not passed to userspace
@Sebastien: Yes, enable/disable airplane mode works from gnome-control-center. It also works to disalbe it from the Gnome panel manu. (Remember that it previously also could be enabled and disabled with the dedicated Fn+Pos1 key as long as xkb-data was 2.23). As for the verification-failed: I obviously accept the maintainers' decision. If you think that the xkb-data update is the right path forward despite this regression, by all means please go ahead. It would be good to fix the regression though. It seems that a very similar machine is sold as a Developer Edition with Ubuntu (Dell Precision 5530, https://bartongeorge.io/2018/05/24/welcome-the-new-dell-precision- developer-editions/) The failed disable of the airplane mode (i.e., failed re-enable of Wifi/BT) leaves this in journalctl: Nov 06 00:00:49 chronic systemd[1]: Starting Load/Save RF Kill Switch Status... Nov 06 00:00:49 chronic NetworkManager[777]: [1541458849.3593] manager: rfkill: WiFi now enabled by radio killswitch Nov 06 00:00:49 chronic systemd[1]: Started Load/Save RF Kill Switch Status. Nov 06 00:00:50 chronic kernel: ath10k_pci :02:00.0: Unknown eventid: 118809 Nov 06 00:00:50 chronic kernel: ath10k_pci :02:00.0: Unknown eventid: 90118 Nov 06 00:00:50 chronic kernel: IPv6: ADDRCONF(NETDEV_UP): wlp2s0: link is not ready Nov 06 00:00:50 chronic NetworkManager[777]: [1541458850.2459] device (wlp2s0): device not up after timeout! Nov 06 00:00:50 chronic NetworkManager[777]: [1541458850.2462] manager: rfkill: WiFi now disabled by radio killswitch Nov 06 00:00:50 chronic NetworkManager[777]: [1541458850.2514] manager: rfkill: WWAN hardware radio set enabled Nov 06 00:00:50 chronic NetworkManager[777]: [1541458850.2516] audit: op="radio-control" arg="wwan-enabled" pid=2286 uid=1000 result="success" Nov 06 00:00:50 chronic NetworkManager[777]: [1541458850.2584] manager: rfkill: WWAN hardware radio set disabled Nov 06 00:00:50 chronic NetworkManager[777]: [1541458850.2586] audit: op="radio-control" arg="wwan-enabled" pid=2286 uid=1000 result="success" -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to libxkbcommon in Ubuntu. https://bugs.launchpad.net/bugs/1740894 Title: KEY_RFKILL is not passed to userspace Status in libxkbcommon package in Ubuntu: Fix Released Status in xkeyboard-config package in Ubuntu: Fix Released Status in xorgproto package in Ubuntu: Fix Released Status in xkeyboard-config source package in Bionic: Fix Committed Status in xkeyboard-config source package in Cosmic: Fix Committed Bug description: * Impact the airplane mode key doesn't work in GNOME * Test case Use a laptop with a key to activate airplane mode, it should toggle the corresponding mode on/off when used * Regression potential The change adds a new key definition but doesn't touch any existing one, nothing specific to test out of the new key working - There are a couple things going on, that could be fixed by a Debian or Ubuntu maintainer: - libxkbdcommon needs to be updated from 0.7.1 to 0.7.2. This introduces the RFKill key: https://lists.freedesktop.org/archives /wayland-devel/2017-August/034721.html - x11-proto needs a new release. This commit added RFKill, but it is not in a release: https://cgit.freedesktop.org/xorg/proto/xproto/commit/?id=98a32d328e7195e12c38baa877917335bceffbaf - Likely other X11 packages need to be rebuilt. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libxkbcommon/+bug/1740894/+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 1799007] Re: [System76 Oryx Pro] no sound after 18.10 upgrade
Booting off USB, sound works fine, soundcards show up correctly. So... it's something that got messed up in the upgrade from 18.04, I guess? -- 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/1799007 Title: [System76 Oryx Pro] no sound after 18.10 upgrade Status in pulseaudio package in Ubuntu: Incomplete Bug description: After upgrading to 18.10, the sound in my System76 Oryx Pro no longer works, it no longer shows any of the audio output devices, not even the builtin HDMI which usually always shows. Not sure what happened, but this is a major regression and needs to be fixed. Note that this isn't the same as the bug with Timidity taking exclusive soundcard access (https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1797714) as I don't have any timidity packages installed. --- ProblemType: Bug ApportVersion: 2.20.10-0ubuntu13 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: tessa 11703 F pulseaudio /dev/snd/controlC0: tessa 11703 F pulseaudio /dev/snd/pcmC0D0c: tessa 11703 F...m pulseaudio /dev/snd/pcmC0D0p: tessa 11703 F...m pulseaudio CurrentDesktop: pop:GNOME DistroRelease: Pop!_OS 18.10 InstallationDate: Installed on 2018-03-05 (230 days ago) InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20180105.1) NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair nvidia_modeset nvidia Package: pulseaudio 1:12.2-0ubuntu4 [origin: Ubuntu] PackageArchitecture: amd64 ProcVersionSignature: Ubuntu 4.18.0-10.11-generic 4.18.12 PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: Daemon not responding. Tags: third-party-packages cosmic Uname: Linux 4.18.0-10-generic x86_64 UnreportableReason: This is not an official Pop!_OS package. Please remove any third party package and try again. UpgradeStatus: Upgraded to cosmic on 2018-10-18 (3 days ago) UserGroups: adm audio cdrom chrome-remote-desktop dip docker libvirt lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 02/20/2017 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 1.05.02dRSA2 dmi.board.asset.tag: Tag 12345 dmi.board.name: Oryx Pro dmi.board.vendor: System76 dmi.board.version: oryp3-ess dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: System76 dmi.chassis.version: N/A dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr1.05.02dRSA2:bd02/20/2017:svnSystem76:pnOryxPro:pvroryp3-ess:rvnSystem76:rnOryxPro:rvroryp3-ess:cvnSystem76:ct10:cvrN/A: dmi.product.family: Not Applicable dmi.product.name: Oryx Pro dmi.product.sku: Not Applicable dmi.product.version: oryp3-ess dmi.sys.vendor: System76 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1799007/+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 1780767] Re: Some tests are flaky due to timeout
The i386 and amd64 autopkgtests passed for Ubuntu 18.04 with the new version of apport in -proposed. http://autopkgtest.ubuntu.com/packages/a/apport/bionic/amd64 http://autopkgtest.ubuntu.com/packages/a/apport/bionic/i386 ** Tags removed: verification-needed verification-needed-bionic ** Tags added: verification-done verification-done-bionic -- 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/1780767 Title: Some tests are flaky due to timeout Status in apport package in Ubuntu: Fix Released Status in apport source package in Bionic: Fix Committed Bug description: The autopkgtests are sometimes passing, sometimes stuck for more than 2h: http://autopkgtest.ubuntu.com/packages/apport/cosmic/amd64. It's blocking randomly on different tests. All tests that are stucked, implements closing a request via a timeout (and then, executing "run"). The bet is that the timeout is short enough (1s) so that, when autopkgtests infra is busy, time to execute the bash subcommand is taking more than a second, and so "dismissing" is ran before execution happens and the whole testsuite hangs. There are few instances of setting this timeout function: $ grep eout_add_sec test/* test/test_ui_gtk.py:GLib.timeout_add_seconds(1, cont) test/test_ui_gtk.py:GLib.timeout_add_seconds(1, cont) test/test_ui_gtk.py:GLib.timeout_add_seconds(1, cont) test/test_ui_gtk.py:GLib.timeout_add_seconds(1, c) test/test_ui_gtk.py:GLib.timeout_add_seconds(1, c) Short term solution could be to increase the timeout. Long term would be to eliminate this potential race implementing cancelling differently. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apport/+bug/1780767/+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 1796550] Re: [regression] Keyboard brightness control keys (down/up) don't work in cosmic (upower 0.99.8)
This bug was fixed in the package upower - 0.99.8-2ubuntu0.1 --- upower (0.99.8-2ubuntu0.1) cosmic; urgency=medium * debian/patches/git_access_sys.patch: - Fix upower's keyboard backlight support (lp: #1796550) -- Sebastien Bacher Thu, 25 Oct 2018 13:31:01 +0200 ** Changed in: upower (Ubuntu Cosmic) Status: Fix Committed => Fix Released -- 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/1796550 Title: [regression] Keyboard brightness control keys (down/up) don't work in cosmic (upower 0.99.8) Status in linux package in Ubuntu: Invalid Status in upower package in Ubuntu: Fix Released Status in upower source package in Cosmic: Fix Released Bug description: * Impact keyboard backlight control keys don't work in cosmic * Test case On a laptop with keyboard backlight and keys to control the level, try using the keys, they should change the level * Regression potential The change is to lift some systemd process restriction, have extra access shouldn't create issue but check that other features like suspend, battery pourcentage report, etc keep working --- https://gitlab.freedesktop.org/upower/upower/issues/73 --- On laptops with two separate (down,up) keys to control the backlit keyboard, both keys seem to do nothing. The OSD for the backlit keyboard is displayed but no progress bar and no actual effect to the backlight. Almost as if the shell only understands laptops with a single key for controlling the keyboard backlight... Bug verified in cosmic on: * Asus UX331UAL * Apple Macbook Pro 12,1 * Apple Macbook Air All of them have these keys and they all fail in the same way. However it is not a kernel bug. The kernel interface (/sys/class/leds/*::kbd_backlight/*) works when I write to it directly. This seems to be a problem with Gnome Shell only. ProblemType: Bug DistroRelease: Ubuntu 18.10 Package: gnome-shell 3.30.0-3ubuntu1 ProcVersionSignature: Ubuntu 4.18.0-8.9-generic 4.18.7 Uname: Linux 4.18.0-8-generic x86_64 ApportVersion: 2.20.10-0ubuntu11 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Sun Oct 7 13:41:50 2018 DisplayManager: gdm3 InstallationDate: Installed on 2018-09-11 (25 days ago) InstallationMedia: Ubuntu 18.10 "Cosmic Cuttlefish" - Alpha amd64 (20180822) SourcePackage: gnome-shell UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1796550/+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 1796550] Update Released
The verification of the Stable Release Update for upower has completed successfully and the package has now been released to -updates. Subsequently, the Ubuntu Stable Release Updates Team is being unsubscribed and will not receive messages about this bug report. In the event that you encounter a regression using the package from -updates please report a new bug using ubuntu-bug and tag the bug report regression-update so we can easily find any regressions. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to upower in Ubuntu. https://bugs.launchpad.net/bugs/1796550 Title: [regression] Keyboard brightness control keys (down/up) don't work in cosmic (upower 0.99.8) Status in linux package in Ubuntu: Invalid Status in upower package in Ubuntu: Fix Released Status in upower source package in Cosmic: Fix Released Bug description: * Impact keyboard backlight control keys don't work in cosmic * Test case On a laptop with keyboard backlight and keys to control the level, try using the keys, they should change the level * Regression potential The change is to lift some systemd process restriction, have extra access shouldn't create issue but check that other features like suspend, battery pourcentage report, etc keep working --- https://gitlab.freedesktop.org/upower/upower/issues/73 --- On laptops with two separate (down,up) keys to control the backlit keyboard, both keys seem to do nothing. The OSD for the backlit keyboard is displayed but no progress bar and no actual effect to the backlight. Almost as if the shell only understands laptops with a single key for controlling the keyboard backlight... Bug verified in cosmic on: * Asus UX331UAL * Apple Macbook Pro 12,1 * Apple Macbook Air All of them have these keys and they all fail in the same way. However it is not a kernel bug. The kernel interface (/sys/class/leds/*::kbd_backlight/*) works when I write to it directly. This seems to be a problem with Gnome Shell only. ProblemType: Bug DistroRelease: Ubuntu 18.10 Package: gnome-shell 3.30.0-3ubuntu1 ProcVersionSignature: Ubuntu 4.18.0-8.9-generic 4.18.7 Uname: Linux 4.18.0-8-generic x86_64 ApportVersion: 2.20.10-0ubuntu11 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Sun Oct 7 13:41:50 2018 DisplayManager: gdm3 InstallationDate: Installed on 2018-09-11 (25 days ago) InstallationMedia: Ubuntu 18.10 "Cosmic Cuttlefish" - Alpha amd64 (20180822) SourcePackage: gnome-shell UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1796550/+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 1801805] [NEW] pdf printer provided by cups-pdf has disappeared since update to 18.04
Public bug reported: Since the update from Ubuntu 16.n to Ubuntu 18.04 the PDF printer functionality provided by cups-pdf has disappeared (on several machines). The "printer" just disappeared from the list of available printers. In all cases the functionality worked properly before. It is possible to install or re-install the cups-pdf via "apt-get install" and it does run the install. However, the "printer" remains unavailable, no trace. There is no error message visible of whatever kind. Printing from applications using Cups-PDF-printer is no longer possible because there is no Cups-PDF printer no more. Same bug applies to 18.10, too. Please advise how to get back the PDF printer functionality in 18.04. ProblemType: Bug DistroRelease: Ubuntu 18.10 Package: cups 2.2.8-5ubuntu1 ProcVersionSignature: Ubuntu 4.18.0-7.8-generic 4.18.5 Uname: Linux 4.18.0-7-generic x86_64 ApportVersion: 2.20.10-0ubuntu13.1 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Mon Nov 5 23:12:26 2018 InstallationDate: Installed on 2016-09-02 (793 days ago) InstallationMedia: Ubuntu 14.04.4 LTS "Trusty Tahr" - Release amd64 (20160217.1) KernLog: [ 871.633929] audit: type=1400 audit(1541455672.543:64): apparmor="DENIED" operation="open" profile="/usr/lib/telepathy/mission-control-5" name="/usr/local/lib/libgcrypt.so.20.1.3" pid=6089 comm="mission-control" requested_mask="r" denied_mask="r" fsuid=1002 ouid=0 [ 871.634375] audit: type=1400 audit(1541455672.543:65): apparmor="DENIED" operation="open" profile="/usr/lib/telepathy/mission-control-5" name="/usr/local/lib/libgpg-error.so.0.20.0" pid=6089 comm="mission-control" requested_mask="r" denied_mask="r" fsuid=1002 ouid=0 Lpstat: device for DESKJET-990C-2: hp:/usb/DeskJet_990C?serial=ES0B81C11DLG device for Hewlett-Packard-HP-LaserJet-MFP-M725: hp:/net/HP_LaserJet_MFP_M725?zc=NPI02EAAF device for HP-LaserJet-5: socket://192.168.22.65:9100 Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 003: ID 8087:0a2b Intel Corp. Bus 001 Device 002: ID 04f2:b563 Chicony Electronics Co., Ltd Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: FUJITSU LIFEBOOK A556/G Papersize: a4 PpdFiles: Error: command ['fgrep', '-H', '*NickName', '/etc/cups/ppd/DESKJET-990C-2.ppd', '/etc/cups/ppd/Hewlett-Packard-HP-LaserJet-MFP-M725.ppd', '/etc/cups/ppd/HP-LaserJet-5.ppd'] failed with exit code 2: grep: /etc/cups/ppd/DESKJET-990C-2.ppd: Permission denied grep: /etc/cups/ppd/Hewlett-Packard-HP-LaserJet-MFP-M725.ppd: Permission denied grep: /etc/cups/ppd/HP-LaserJet-5.ppd: Permission denied ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.18.0-7-generic root=UUID=1f7b9a32-c877-4663-b036-c761cde32cfd ro plymouth:debug drm.debug=0xe SourcePackage: cups UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 09/22/2016 dmi.bios.vendor: FUJITSU // Insyde Software Corp. dmi.bios.version: Version 1.18 dmi.board.name: FJNBB47 dmi.board.vendor: FUJITSU dmi.chassis.type: 10 dmi.chassis.vendor: FUJITSU dmi.chassis.version: LIFEBOOK A556/G dmi.modalias: dmi:bvnFUJITSU//InsydeSoftwareCorp.:bvrVersion1.18:bd09/22/2016:svnFUJITSU:pnLIFEBOOKA556/G:pvr:rvnFUJITSU:rnFJNBB47:rvr:cvnFUJITSU:ct10:cvrLIFEBOOKA556/G: dmi.product.family: LIFEBOOK-FTS dmi.product.name: LIFEBOOK A556/G dmi.sys.vendor: FUJITSU ** Affects: cups (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug cosmic -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to cups in Ubuntu. https://bugs.launchpad.net/bugs/1801805 Title: pdf printer provided by cups-pdf has disappeared since update to 18.04 Status in cups package in Ubuntu: New Bug description: Since the update from Ubuntu 16.n to Ubuntu 18.04 the PDF printer functionality provided by cups-pdf has disappeared (on several machines). The "printer" just disappeared from the list of available printers. In all cases the functionality worked properly before. It is possible to install or re-install the cups-pdf via "apt-get install" and it does run the install. However, the "printer" remains unavailable, no trace. There is no error message visible of whatever kind. Printing from applications using Cups-PDF-printer is no longer possible because there is no Cups-PDF printer no more. Same bug applies to 18.10, too. Please advise how to get back the PDF printer functionality in 18.04. ProblemType: Bug DistroRelease: Ubuntu 18.10 Package: cups 2.2.8-5ubuntu1 ProcVersionSignature: Ubuntu 4.18.0-7.8-generic 4.18.5 Uname: Linux 4.18.0-7-generic x86_64 ApportVersion: 2.20.10-0ubuntu13.1 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Mon Nov 5 23:12:26 2018 InstallationDate: Installed on 2016-09-02 (793 days ago) InstallationMedia: Ubuntu 14.04.4 LTS "Trusty Tahr" - Release amd64 (20160217.1) KernLog: [ 871.633929] audit: type=1400
[Touch-packages] [Bug 1760220] Re: ubuntu-bug with program path says as a snap does not belong to a package
This also works as intended on Ubuntu 18.04.
bdmurray@clean-bionic-amd64:~$ ubuntu-bug /snap/bin/juju
Usage: ubuntu-bug [options] [symptom|pid|package|program path|.apport/.crash
file]
ubuntu-bug: error: /snap/bin/juju does not belong to a package.
bdmurray@clean-bionic-amd64:~$ sudo apt install apport-gtk
Reading package lists... Done
Building dependency tree
Reading state information... Done
The following additional packages will be installed:
python3-apport
The following packages will be upgraded:
apport-gtk python3-apport
2 upgraded, 0 newly installed, 0 to remove and 270 not upgraded.
Need to get 91.4 kB of archives.
After this operation, 6,144 B of additional disk space will be used.
Do you want to continue? [Y/n] Y
Get:1 http://archive.ubuntu.com/ubuntu bionic-proposed/main amd64
python3-apport all 2.20.9-0ubuntu7.5 [81.6 kB]
Get:2 http://archive.ubuntu.com/ubuntu bionic-proposed/main amd64 apport-gtk
all 2.20.9-0ubuntu7.5 [9,704 B]
Fetched 91.4 kB in 1s (98.0 kB/s)
(Reading database ... 166001 files and directories currently installed.)
Preparing to unpack .../python3-apport_2.20.9-0ubuntu7.5_all.deb ...
Unpacking python3-apport (2.20.9-0ubuntu7.5) over (2.20.9-0ubuntu7.2) ...
Preparing to unpack .../apport-gtk_2.20.9-0ubuntu7.5_all.deb ...
Unpacking apport-gtk (2.20.9-0ubuntu7.5) over (2.20.9-0ubuntu7.2) ...
Processing triggers for mime-support (3.60ubuntu1) ...
Processing triggers for desktop-file-utils (0.23-1ubuntu3.18.04.1) ...
Setting up python3-apport (2.20.9-0ubuntu7.5) ...
Processing triggers for gnome-menus (3.13.3-11ubuntu1.1) ...
Setting up apport-gtk (2.20.9-0ubuntu7.5) ...
bdmurray@clean-bionic-amd64:~$ ubuntu-bug /snap/bin/juju
Usage: ubuntu-bug [options] [symptom|pid|package|program path|.apport/.crash
file]
ubuntu-bug: error: /snap/bin/juju is provided by a snap. No contact
address has been provided; visit the forum at
https://forum.snapcraft.io/ for help.
** Tags removed: verification-needed-bionic
** Tags added: verification-done-bionic
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to apport in Ubuntu.
https://bugs.launchpad.net/bugs/1760220
Title:
ubuntu-bug with program path says as a snap does not belong to a
package
Status in apport package in Ubuntu:
Fix Released
Status in apport source package in Bionic:
Fix Committed
Status in apport source package in Cosmic:
Fix Committed
Bug description:
[Impact]
ubuntu-bug responds with a misleading statement asked to report a bug about
an executable path which starts with /snap/bin and the response is different
than if you were to use the snap name e.g. ubuntu-bug juju
[Test Case]
1) Run ubuntu-bug /snap/bin/juju
2) Read "/snap/bin/juju does not belong to a package"
With the version of apport in -proposed you'll receive a more
informative message about where you might get help regarding the issue
you are experiencing.
[Regression Potential]
The new code only affects executables that start with '/snap/bin' so the only
danger is if the newly added code contains an error which would cause a
traceback.
Original Report
---
apport's ui.py file contains the following code:
809 # executable?
810 elif '/' in self.args[0]:
811 pkg = apport.packaging.get_file_package(self.args[0])
812 if not pkg:
813 optparser.error('%s does not belong to a package.' %
self.args[0])
814 sys.exit(1)
815 self.args = []
816 self.options.filebug = True
817 self.options.package = pkg
This will not provide any useful information about what to do if the
'executable' is provided by a snap. Information similar to
https://code.launchpad.net/~juliank/ubuntu/bionic/apport/snap/+merge/342207
should be provided if the path is from a snap.
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/apport/+bug/1760220/+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 1799026] Re: Trojitá plaintext emails are displayed letter by letter
This bug was fixed in the package qtwebkit-opensource-src - 5.212.0~alpha2-12ubuntu1.1 --- qtwebkit-opensource-src (5.212.0~alpha2-12ubuntu1.1) cosmic; urgency=medium * Fix resizing the FrameView, which fixes plaintext emails in Trojitá (LP: #1799026). * Build with -fpermissive to (hopefully) solve the i386 FTBFS. * Update symbols from build logs. -- Simon Quigley Sun, 21 Oct 2018 01:11:18 -0500 ** Changed in: qtwebkit-opensource-src (Ubuntu Cosmic) Status: Fix Committed => Fix Released -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to qtwebkit-opensource-src in Ubuntu. https://bugs.launchpad.net/bugs/1799026 Title: Trojitá plaintext emails are displayed letter by letter Status in qtwebkit-opensource-src package in Ubuntu: Fix Released Status in qtwebkit-opensource-src source package in Cosmic: Fix Released Bug description: [Impact] Without this fix, when viewing plaintext emails in Trojitá, each letter is on its own line, making it difficult to read messages at best. Two fixes from upstream QtWebkit can fix this problem. [Test Case] Open any email when signed into an IMAP server with Trojitá, and if the email is an HTML email, select the "Plaintext" tab if it isn't selected already. It should be displayed normally, with a regular sized font. [Regression Potential] Little to none. If another QtWebkit-using package depends on the way this has already worked in an unsafe way, it could break, but this is unlikely. I could also see how it could potential to break if the email is very, very, very large, because it has to refresh the view, but at most you would expect some slowness. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/qtwebkit-opensource-src/+bug/1799026/+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 1799026] Update Released
The verification of the Stable Release Update for qtwebkit-opensource- src has completed successfully and the package has now been released to -updates. Subsequently, the Ubuntu Stable Release Updates Team is being unsubscribed and will not receive messages about this bug report. In the event that you encounter a regression using the package from -updates please report a new bug using ubuntu-bug and tag the bug report regression-update so we can easily find any regressions. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to qtwebkit-opensource-src in Ubuntu. https://bugs.launchpad.net/bugs/1799026 Title: Trojitá plaintext emails are displayed letter by letter Status in qtwebkit-opensource-src package in Ubuntu: Fix Released Status in qtwebkit-opensource-src source package in Cosmic: Fix Released Bug description: [Impact] Without this fix, when viewing plaintext emails in Trojitá, each letter is on its own line, making it difficult to read messages at best. Two fixes from upstream QtWebkit can fix this problem. [Test Case] Open any email when signed into an IMAP server with Trojitá, and if the email is an HTML email, select the "Plaintext" tab if it isn't selected already. It should be displayed normally, with a regular sized font. [Regression Potential] Little to none. If another QtWebkit-using package depends on the way this has already worked in an unsafe way, it could break, but this is unlikely. I could also see how it could potential to break if the email is very, very, very large, because it has to refresh the view, but at most you would expect some slowness. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/qtwebkit-opensource-src/+bug/1799026/+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 1786574] Re: remove i2c-i801 from blacklist
This bug was fixed in the package kmod - 22-1ubuntu5.1 --- kmod (22-1ubuntu5.1) xenial; urgency=medium * Remove i2c_i801 from d/modprobe.d/blacklist.conf. (LP: #1786574) -- Michael Hudson-Doyle Wed, 24 Oct 2018 12:20:23 +1300 -- 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/1786574 Title: remove i2c-i801 from blacklist Status in HWE Next: Fix Committed Status in OEM Priority Project: New Status in kmod package in Ubuntu: Fix Committed Status in kmod source package in Xenial: Fix Released Status in kmod source package in Bionic: Fix Released Status in kmod source package in Cosmic: Fix Released Bug description: SRU justification [Impact] Many modern notebooks need i2c-i801 kernel module to function, but it is blacklisted by /etc/modprobe/blacklist.conf, which gives a very poor user experience. [Test case] 1. Install Ubuntu 2. Check touchpad works or not 3. Install the fixed kmod package 4. Confirm touchpad works [Regression Potential] i2c-i801 was blacklisted due to bug 16602. The user complains an HP Compaq nc6000 notebook cannot suspend without blacklisting i2c-i801. While this is a way to workaround the suspend issue, the proper fix should be in linux kernel. Since nc6000 was a machine sold in 2004, it is too difficult to find someone to verify if it will regress due to this SRU. The rationale to blacklist it is: https://bugs.launchpad.net/ubuntu/+source/hotplug/+bug/16602/comments/5, however it is no longer valid nowadays on modern computers. Besides, there look like to be a quirk in linux kernel that fixes it: https://github.com/torvalds/linux/blame/master/drivers/pci/quirks.c#L1434 [Other Info] rationale of i2c_i801 driver blacklist: https://answers.launchpad.net/ubuntu/+source/kmod/+question/269329 --- Original bug report: We have a Lenovo Thinkpad machine that requires i2c-i801 kernel module to work, but it is listed in /etc/modprobe/blacklist.conf in Ubuntu. To use the touchpad, users have to remove the i2c-i801 line manually. i2c-i801 in blacklist.conf is a very old workaround to fix HP compaq nc6000 (Bug #16602), this module should be removed from blacklist. There is also another bug (Bug #1475945) that needs this module for Acer trackpad to work. To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/1786574/+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 1786574] Update Released
The verification of the Stable Release Update for kmod has completed successfully and the package has now been released to -updates. Subsequently, the Ubuntu Stable Release Updates Team is being unsubscribed and will not receive messages about this bug report. In the event that you encounter a regression using the package from -updates please report a new bug using ubuntu-bug and tag the bug report regression-update so we can easily find any regressions. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to kmod in Ubuntu. https://bugs.launchpad.net/bugs/1786574 Title: remove i2c-i801 from blacklist Status in HWE Next: Fix Committed Status in OEM Priority Project: New Status in kmod package in Ubuntu: Fix Committed Status in kmod source package in Xenial: Fix Released Status in kmod source package in Bionic: Fix Released Status in kmod source package in Cosmic: Fix Released Bug description: SRU justification [Impact] Many modern notebooks need i2c-i801 kernel module to function, but it is blacklisted by /etc/modprobe/blacklist.conf, which gives a very poor user experience. [Test case] 1. Install Ubuntu 2. Check touchpad works or not 3. Install the fixed kmod package 4. Confirm touchpad works [Regression Potential] i2c-i801 was blacklisted due to bug 16602. The user complains an HP Compaq nc6000 notebook cannot suspend without blacklisting i2c-i801. While this is a way to workaround the suspend issue, the proper fix should be in linux kernel. Since nc6000 was a machine sold in 2004, it is too difficult to find someone to verify if it will regress due to this SRU. The rationale to blacklist it is: https://bugs.launchpad.net/ubuntu/+source/hotplug/+bug/16602/comments/5, however it is no longer valid nowadays on modern computers. Besides, there look like to be a quirk in linux kernel that fixes it: https://github.com/torvalds/linux/blame/master/drivers/pci/quirks.c#L1434 [Other Info] rationale of i2c_i801 driver blacklist: https://answers.launchpad.net/ubuntu/+source/kmod/+question/269329 --- Original bug report: We have a Lenovo Thinkpad machine that requires i2c-i801 kernel module to work, but it is listed in /etc/modprobe/blacklist.conf in Ubuntu. To use the touchpad, users have to remove the i2c-i801 line manually. i2c-i801 in blacklist.conf is a very old workaround to fix HP compaq nc6000 (Bug #16602), this module should be removed from blacklist. There is also another bug (Bug #1475945) that needs this module for Acer trackpad to work. To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/1786574/+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 1786574] Re: remove i2c-i801 from blacklist
This bug was fixed in the package kmod - 24-1ubuntu3.1 --- kmod (24-1ubuntu3.1) bionic; urgency=medium * Remove i2c_i801 from d/modprobe.d/blacklist.conf. (LP: #1786574) -- Michael Hudson-Doyle Wed, 24 Oct 2018 12:20:23 +1300 ** Changed in: kmod (Ubuntu Bionic) Status: Fix Committed => Fix Released ** Changed in: kmod (Ubuntu Xenial) Status: Fix Committed => Fix Released -- 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/1786574 Title: remove i2c-i801 from blacklist Status in HWE Next: Fix Committed Status in OEM Priority Project: New Status in kmod package in Ubuntu: Fix Committed Status in kmod source package in Xenial: Fix Released Status in kmod source package in Bionic: Fix Released Status in kmod source package in Cosmic: Fix Released Bug description: SRU justification [Impact] Many modern notebooks need i2c-i801 kernel module to function, but it is blacklisted by /etc/modprobe/blacklist.conf, which gives a very poor user experience. [Test case] 1. Install Ubuntu 2. Check touchpad works or not 3. Install the fixed kmod package 4. Confirm touchpad works [Regression Potential] i2c-i801 was blacklisted due to bug 16602. The user complains an HP Compaq nc6000 notebook cannot suspend without blacklisting i2c-i801. While this is a way to workaround the suspend issue, the proper fix should be in linux kernel. Since nc6000 was a machine sold in 2004, it is too difficult to find someone to verify if it will regress due to this SRU. The rationale to blacklist it is: https://bugs.launchpad.net/ubuntu/+source/hotplug/+bug/16602/comments/5, however it is no longer valid nowadays on modern computers. Besides, there look like to be a quirk in linux kernel that fixes it: https://github.com/torvalds/linux/blame/master/drivers/pci/quirks.c#L1434 [Other Info] rationale of i2c_i801 driver blacklist: https://answers.launchpad.net/ubuntu/+source/kmod/+question/269329 --- Original bug report: We have a Lenovo Thinkpad machine that requires i2c-i801 kernel module to work, but it is listed in /etc/modprobe/blacklist.conf in Ubuntu. To use the touchpad, users have to remove the i2c-i801 line manually. i2c-i801 in blacklist.conf is a very old workaround to fix HP compaq nc6000 (Bug #16602), this module should be removed from blacklist. There is also another bug (Bug #1475945) that needs this module for Acer trackpad to work. To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/1786574/+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 1786574] Re: remove i2c-i801 from blacklist
This bug was fixed in the package kmod - 25-1ubuntu1.1 --- kmod (25-1ubuntu1.1) cosmic; urgency=medium * Remove i2c_i801 from d/modprobe.d/blacklist.conf. (LP: #1786574) -- Michael Hudson-Doyle Wed, 24 Oct 2018 12:20:23 +1300 ** Changed in: kmod (Ubuntu Cosmic) Status: Fix Committed => Fix Released -- 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/1786574 Title: remove i2c-i801 from blacklist Status in HWE Next: Fix Committed Status in OEM Priority Project: New Status in kmod package in Ubuntu: Fix Committed Status in kmod source package in Xenial: Fix Released Status in kmod source package in Bionic: Fix Released Status in kmod source package in Cosmic: Fix Released Bug description: SRU justification [Impact] Many modern notebooks need i2c-i801 kernel module to function, but it is blacklisted by /etc/modprobe/blacklist.conf, which gives a very poor user experience. [Test case] 1. Install Ubuntu 2. Check touchpad works or not 3. Install the fixed kmod package 4. Confirm touchpad works [Regression Potential] i2c-i801 was blacklisted due to bug 16602. The user complains an HP Compaq nc6000 notebook cannot suspend without blacklisting i2c-i801. While this is a way to workaround the suspend issue, the proper fix should be in linux kernel. Since nc6000 was a machine sold in 2004, it is too difficult to find someone to verify if it will regress due to this SRU. The rationale to blacklist it is: https://bugs.launchpad.net/ubuntu/+source/hotplug/+bug/16602/comments/5, however it is no longer valid nowadays on modern computers. Besides, there look like to be a quirk in linux kernel that fixes it: https://github.com/torvalds/linux/blame/master/drivers/pci/quirks.c#L1434 [Other Info] rationale of i2c_i801 driver blacklist: https://answers.launchpad.net/ubuntu/+source/kmod/+question/269329 --- Original bug report: We have a Lenovo Thinkpad machine that requires i2c-i801 kernel module to work, but it is listed in /etc/modprobe/blacklist.conf in Ubuntu. To use the touchpad, users have to remove the i2c-i801 line manually. i2c-i801 in blacklist.conf is a very old workaround to fix HP compaq nc6000 (Bug #16602), this module should be removed from blacklist. There is also another bug (Bug #1475945) that needs this module for Acer trackpad to work. To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/1786574/+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 1799007] Re: [System76 Oryx Pro] no sound after 18.10 upgrade
Ahh yes, there everything is in /dev/snd, so really starting to feel like a pulseaudio bug. $ ls /dev/snd by-pathcontrolC1 hwC1D0pcmC0D0p pcmC1D3p pcmC1D8p timer controlC0 hwC0D0 pcmC0D0c pcmC0D1p pcmC1D7p seq I'll try the USB boot thing this aft and get back to you. -- 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/1799007 Title: [System76 Oryx Pro] no sound after 18.10 upgrade Status in pulseaudio package in Ubuntu: Incomplete Bug description: After upgrading to 18.10, the sound in my System76 Oryx Pro no longer works, it no longer shows any of the audio output devices, not even the builtin HDMI which usually always shows. Not sure what happened, but this is a major regression and needs to be fixed. Note that this isn't the same as the bug with Timidity taking exclusive soundcard access (https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1797714) as I don't have any timidity packages installed. --- ProblemType: Bug ApportVersion: 2.20.10-0ubuntu13 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: tessa 11703 F pulseaudio /dev/snd/controlC0: tessa 11703 F pulseaudio /dev/snd/pcmC0D0c: tessa 11703 F...m pulseaudio /dev/snd/pcmC0D0p: tessa 11703 F...m pulseaudio CurrentDesktop: pop:GNOME DistroRelease: Pop!_OS 18.10 InstallationDate: Installed on 2018-03-05 (230 days ago) InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20180105.1) NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair nvidia_modeset nvidia Package: pulseaudio 1:12.2-0ubuntu4 [origin: Ubuntu] PackageArchitecture: amd64 ProcVersionSignature: Ubuntu 4.18.0-10.11-generic 4.18.12 PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: Daemon not responding. Tags: third-party-packages cosmic Uname: Linux 4.18.0-10-generic x86_64 UnreportableReason: This is not an official Pop!_OS package. Please remove any third party package and try again. UpgradeStatus: Upgraded to cosmic on 2018-10-18 (3 days ago) UserGroups: adm audio cdrom chrome-remote-desktop dip docker libvirt lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 02/20/2017 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 1.05.02dRSA2 dmi.board.asset.tag: Tag 12345 dmi.board.name: Oryx Pro dmi.board.vendor: System76 dmi.board.version: oryp3-ess dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: System76 dmi.chassis.version: N/A dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr1.05.02dRSA2:bd02/20/2017:svnSystem76:pnOryxPro:pvroryp3-ess:rvnSystem76:rnOryxPro:rvroryp3-ess:cvnSystem76:ct10:cvrN/A: dmi.product.family: Not Applicable dmi.product.name: Oryx Pro dmi.product.sku: Not Applicable dmi.product.version: oryp3-ess dmi.sys.vendor: System76 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1799007/+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 1801762] Re: Dual-signed things should be easy to verify with one key
I've created a shell wrapper than might be useful for this called "gpgpv-multisig" which is a multi-call executable. Given /usr/bin/gpgv- multisig ln -s gpgv-multisig /usr/bin/gpgv-aptkeys and called as 'gpgv-aptkeys' it will assume the keyring to be used is /etc/apt/trusted.gpg (set by APT_KEYRING). Returns the same exit codes as detailed in man gpgv(1): 0 = all signatures good 1 = at least one signature good 2 = no signatures good Many configuration variables can be over-ridden from the environment but adopt sensible defaults. ** Attachment added: "Shell script wrapping gpgv for multi-signature gpgv" https://bugs.launchpad.net/ubuntu/+source/ubuntu-release-upgrader/+bug/1801762/+attachment/5209443/+files/gpgv-multisig -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to apt in Ubuntu. https://bugs.launchpad.net/bugs/1801762 Title: Dual-signed things should be easy to verify with one key Status in apt package in Ubuntu: New Status in debmirror package in Ubuntu: New Status in gnupg2 package in Ubuntu: New Status in ubuntu-keyring package in Ubuntu: New Status in ubuntu-release-upgrader package in Ubuntu: New Bug description: As part of Ubuntu key rotation strategy, we rely on dual-signing (inline, or detached) such that validation with at least one key available in a keyring should be trusted, without using web-of-trust. However, it seems to be only correctly so far implemented by the apt's gpgv method. Ideally, we should ship an easy enough to use the helper that is `like gpgv` to use, and possibly reusing apt's gpgv code and/or exposing it via apt-key's verify. The problem seems to be that 1 good sig + 1 no public key available, results in gpgv exiting with 2, instead of 0 or 1. Ideally it should be easy enough to use gpgv/gpg to verify that at least one signature is good, and decrypt/extract signed contents only. More details and reproducers to follow. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apt/+bug/1801762/+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 1098959] Re: 12.10 Bluetooth Battery Indicator Interferes with Bluetooth Mouse Moves
This issue has either re-appeared or has remained a latent issue in Ubuntu 18.10. My Bluetooth keyboard (Samsung AA-SK2NWBB/US) and BLE mouse (Logitech MX Anywhere 2) would connect after startup, work for a couple minutes (or number of keystrokes?) and then the Bluetooth would enter a seemingly unrecoverable state. Disabling upowerd via "sudo systemctl disable upower" seems to solve the issue. -- 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/1098959 Title: 12.10 Bluetooth Battery Indicator Interferes with Bluetooth Mouse Moves Status in gnome-power: New Status in indicator-power package in Ubuntu: Confirmed Bug description: A fully updated (Jan 11, 2013) Ubuntu 12.10 allows the bluetooth mouse to "connect" but fails to move the cursor. The bluetooth battery indicator is created and works. If bluetooth is turned on just before mouse connection is attempted (before the battery indicator shows the mouse battery), sometimes there is mouse cursor movement for a fraction of a second. One time, a mouse onnection succeeded, and at that time, the battery indicator for the mouse no longer reported the current battery state (switching batteries of different charges no longer accurately indicated the battery charge). hcidump reports the mouse moves, but the cursor does nothing, nor do clicks. ** The mouse does work if the battery indicator is killed soon after boot before bluetooth is turned on.** Taking a wild guess, the bluetooth battery indicator handler is not re-queueing the mouse moves it sees while looking for the battery info. Additionally, the mouse handler, when it rarely gets a position before the battery handler is not re-queuing the battery messages. Equipment: HP V3000, with Nvidia 6150 running driver version 304.51, root on 8G usb. Bus 002 Device 002: ID 03f0:171d Hewlett-Packard Bluetooth 2.0 Interface [Broadcom BCM2045], Generic Bluetooth mouse Broadcom 4311 wireless running the b43 driver with the firmware supplied from package firmware-b43-installer. xorg.conf file was originally absent, but copying one from my 12.04 installation made no difference. ProblemType: Bug DistroRelease: Ubuntu 12.10 Package: indicator-power 12.10.2-0ubuntu1 ProcVersionSignature: Ubuntu 3.5.0-21.32-generic 3.5.7.1 Uname: Linux 3.5.0-21-generic i686 NonfreeKernelModules: nvidia ApportVersion: 2.6.1-0ubuntu9 Architecture: i386 Date: Sat Jan 12 12:03:51 2013 MarkForUpload: True ProcEnviron: TERM=xterm PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: indicator-power UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-power/+bug/1098959/+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 1780767] Re: Some tests are flaky due to timeout
Hello Didier, or anyone else affected, Accepted apport into bionic-proposed. The package will build now and be available at https://launchpad.net/ubuntu/+source/apport/2.20.9-0ubuntu7.5 in a few hours, and then in the -proposed repository. Please help us by testing this new package. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation on how to enable and use -proposed. Your feedback will aid us getting this update out to other Ubuntu users. If this package fixes the bug for you, please add a comment to this bug, mentioning the version of the package you tested and change the tag from verification-needed-bionic to verification-done-bionic. If it does not fix the bug for you, please add a comment stating that, and change the tag to verification-failed-bionic. In either case, without details of your testing we will not be able to proceed. Further information regarding the verification process can be found at https://wiki.ubuntu.com/QATeam/PerformingSRUVerification . Thank you in advance for helping! N.B. The updated package will be released to -updates after the bug(s) fixed by this package have been verified and the package has been in -proposed for a minimum of 7 days. ** Changed in: apport (Ubuntu Bionic) Status: In Progress => Fix Committed ** Tags added: verification-needed verification-needed-bionic -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to apport in Ubuntu. https://bugs.launchpad.net/bugs/1780767 Title: Some tests are flaky due to timeout Status in apport package in Ubuntu: Fix Released Status in apport source package in Bionic: Fix Committed Bug description: The autopkgtests are sometimes passing, sometimes stuck for more than 2h: http://autopkgtest.ubuntu.com/packages/apport/cosmic/amd64. It's blocking randomly on different tests. All tests that are stucked, implements closing a request via a timeout (and then, executing "run"). The bet is that the timeout is short enough (1s) so that, when autopkgtests infra is busy, time to execute the bash subcommand is taking more than a second, and so "dismissing" is ran before execution happens and the whole testsuite hangs. There are few instances of setting this timeout function: $ grep eout_add_sec test/* test/test_ui_gtk.py:GLib.timeout_add_seconds(1, cont) test/test_ui_gtk.py:GLib.timeout_add_seconds(1, cont) test/test_ui_gtk.py:GLib.timeout_add_seconds(1, cont) test/test_ui_gtk.py:GLib.timeout_add_seconds(1, c) test/test_ui_gtk.py:GLib.timeout_add_seconds(1, c) Short term solution could be to increase the timeout. Long term would be to eliminate this potential race implementing cancelling differently. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apport/+bug/1780767/+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 1760220] Re: ubuntu-bug with program path says as a snap does not belong to a package
Hello Brian, or anyone else affected,
Accepted apport into bionic-proposed. The package will build now and be
available at
https://launchpad.net/ubuntu/+source/apport/2.20.9-0ubuntu7.5 in a few
hours, and then in the -proposed repository.
Please help us by testing this new package. See
https://wiki.ubuntu.com/Testing/EnableProposed for documentation on how
to enable and use -proposed. Your feedback will aid us getting this
update out to other Ubuntu users.
If this package fixes the bug for you, please add a comment to this bug,
mentioning the version of the package you tested and change the tag from
verification-needed-bionic to verification-done-bionic. If it does not
fix the bug for you, please add a comment stating that, and change the
tag to verification-failed-bionic. In either case, without details of
your testing we will not be able to proceed.
Further information regarding the verification process can be found at
https://wiki.ubuntu.com/QATeam/PerformingSRUVerification . Thank you in
advance for helping!
N.B. The updated package will be released to -updates after the bug(s)
fixed by this package have been verified and the package has been in
-proposed for a minimum of 7 days.
** Changed in: apport (Ubuntu Bionic)
Status: In Progress => Fix Committed
** Tags added: verification-needed-bionic
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to apport in Ubuntu.
https://bugs.launchpad.net/bugs/1760220
Title:
ubuntu-bug with program path says as a snap does not belong to a
package
Status in apport package in Ubuntu:
Fix Released
Status in apport source package in Bionic:
Fix Committed
Status in apport source package in Cosmic:
Fix Committed
Bug description:
[Impact]
ubuntu-bug responds with a misleading statement asked to report a bug about
an executable path which starts with /snap/bin and the response is different
than if you were to use the snap name e.g. ubuntu-bug juju
[Test Case]
1) Run ubuntu-bug /snap/bin/juju
2) Read "/snap/bin/juju does not belong to a package"
With the version of apport in -proposed you'll receive a more
informative message about where you might get help regarding the issue
you are experiencing.
[Regression Potential]
The new code only affects executables that start with '/snap/bin' so the only
danger is if the newly added code contains an error which would cause a
traceback.
Original Report
---
apport's ui.py file contains the following code:
809 # executable?
810 elif '/' in self.args[0]:
811 pkg = apport.packaging.get_file_package(self.args[0])
812 if not pkg:
813 optparser.error('%s does not belong to a package.' %
self.args[0])
814 sys.exit(1)
815 self.args = []
816 self.options.filebug = True
817 self.options.package = pkg
This will not provide any useful information about what to do if the
'executable' is provided by a snap. Information similar to
https://code.launchpad.net/~juliank/ubuntu/bionic/apport/snap/+merge/342207
should be provided if the path is from a snap.
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/apport/+bug/1760220/+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 1799064] Re: Bluetooth refuses to power on after cosmic upgrade
Works in 4.15.0, but fails in 4.16.18 and 4.17.19. I don't have time right now to try earlier point releases (plus this is an infuriatingly slow system), but hope this helps narrow it down a bit, at least. A few other observations: * Unplugging and replugging the dongle, and then restarting bluetooth.service, makes it work in otherwise failing kernels. Doing just one of these does not seem sufficient. * I've also tried a different bluetooth dongle (another no-name thing from eBay), with the same result, so this does not seem hardware specific. * The behavior is consistent across different USB ports. -- 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/1799064 Title: Bluetooth refuses to power on after cosmic upgrade Status in bluez package in Ubuntu: Incomplete Status in linux package in Ubuntu: Incomplete Bug description: After upgrading from bionic to cosmic, Bluetooth has stopped working. It has worked fine for several versions before. Error message from syslog is: Failed to set mode: Failed (0x03) Which according to various random forum posts seems to suggest the device is not powering on. Powering on manually also does not work: % bluetoothctl Agent registered [bluetooth]# power on Failed to set power on: org.bluez.Error.Failed And results in the same set mode failure getting logged again in syslog. hciconfig reports the device as down: % sudo hciconfig hci0: Type: Primary Bus: USB BD Address: 00:11:67:00:00:00 ACL MTU: 1021:4 SCO MTU: 48:10 DOWN RX bytes:498 acl:0 sco:0 events:21 errors:0 TX bytes:101 acl:0 sco:0 commands:24 errors:0 And, again, it refuses to power on: % sudo hciconfig hci0 up Can't init device hci0: Connection timed out (110) rfkill does not appear to be blocking it: % rfkill list 0: hci0: Bluetooth Soft blocked: no Hard blocked: no 1: phy0: Wireless LAN Soft blocked: no Hard blocked: no And systemd-rfkill.service is masked: ~ % sudo systemctl status systemd-rfkill.service ● systemd-rfkill.service Loaded: masked (Reason: Unit systemd-rfkill.service is masked.) [..] The system does not have tlp installed. I have tried numerous reboots, power offs, and moving the USB Bluetooth adapter to different ports, with no change in result. I have also tried unloading and loading btusb. The adapter is a cheap noname thing off of eBay, I trust the system report will provide every possibly interesting detail about it. ProblemType: Bug DistroRelease: Ubuntu 18.10 Package: bluez 5.50-0ubuntu1 ProcVersionSignature: Ubuntu 4.18.0-10.11-generic 4.18.12 Uname: Linux 4.18.0-10-generic x86_64 NonfreeKernelModules: nvidia ApportVersion: 2.20.10-0ubuntu13 Architecture: amd64 Date: Sun Oct 21 17:22:28 2018 InterestingModules: rfcomm bnep btusb bluetooth MachineType: ASUSTeK Computer INC. EB1501P ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.18.0-10-generic root=UUID=515746f5-9b4c-4148-8e1e-012df202f447 ro splash quiet username=autostart,nodiskmount loglevel=0 vt.handoff=1 SourcePackage: bluez UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 01/02/2012 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 0501 dmi.board.asset.tag: To Be Filled By O.E.M. dmi.board.name: EB1501P dmi.board.vendor: ASUSTeK Computer INC. dmi.board.version: Rev 1.xx dmi.chassis.asset.tag: Asset-1234567890 dmi.chassis.type: 3 dmi.chassis.vendor: Chassis Manufacture dmi.chassis.version: Chassis Version dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr0501:bd01/02/2012:svnASUSTeKComputerINC.:pnEB1501P:pvrSystemVersion:rvnASUSTeKComputerINC.:rnEB1501P:rvrRev1.xx:cvnChassisManufacture:ct3:cvrChassisVersion: dmi.product.family: Eee Family dmi.product.name: EB1501P dmi.product.sku: To Be Filled By O.E.M. dmi.product.version: System Version dmi.sys.vendor: ASUSTeK Computer INC. hciconfig: hci0:Type: Primary Bus: USB BD Address: 00:11:67:00:00:00 ACL MTU: 1021:4 SCO MTU: 48:10 DOWN RX bytes:498 acl:0 sco:0 events:21 errors:0 TX bytes:95 acl:0 sco:0 commands:22 errors:0 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/1799064/+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 1760220] Re: ubuntu-bug with program path says as a snap does not belong to a package
This works as expected on cosmic.
$ apt-cache policy apport
apport:
Installed: 2.20.10-0ubuntu13
Candidate: 2.20.10-0ubuntu13.1
Version table:
2.20.10-0ubuntu13.1 500
500 http://ubuntu.osuosl.org/ubuntu cosmic-proposed/main amd64 Packages
500 http://ubuntu.osuosl.org/ubuntu cosmic-proposed/main i386 Packages
*** 2.20.10-0ubuntu13 500
500 http://192.168.10.7/ubuntu cosmic/main amd64 Packages
500 http://192.168.10.7/ubuntu cosmic/main i386 Packages
100 /var/lib/dpkg/status
[ 11:45AM 10233 ] [
bdmurray@speedy:~/source-trees/ubuntu-archive-tools/upstream ]
$ ubuntu-bug /snap/bin/juju
Usage: ubuntu-bug [options] [symptom|pid|package|program path|.apport/.crash
file]
ubuntu-bug: error: /snap/bin/juju is provided by a snap published by
canonical. Contact them via http://jujucharms.com for help.
** Tags removed: verification-needed-cosmic
** Tags added: verification-done-cosmic
--
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/1760220
Title:
ubuntu-bug with program path says as a snap does not belong to a
package
Status in apport package in Ubuntu:
Fix Released
Status in apport source package in Bionic:
In Progress
Status in apport source package in Cosmic:
Fix Committed
Bug description:
[Impact]
ubuntu-bug responds with a misleading statement asked to report a bug about
an executable path which starts with /snap/bin and the response is different
than if you were to use the snap name e.g. ubuntu-bug juju
[Test Case]
1) Run ubuntu-bug /snap/bin/juju
2) Read "/snap/bin/juju does not belong to a package"
With the version of apport in -proposed you'll receive a more
informative message about where you might get help regarding the issue
you are experiencing.
[Regression Potential]
The new code only affects executables that start with '/snap/bin' so the only
danger is if the newly added code contains an error which would cause a
traceback.
Original Report
---
apport's ui.py file contains the following code:
809 # executable?
810 elif '/' in self.args[0]:
811 pkg = apport.packaging.get_file_package(self.args[0])
812 if not pkg:
813 optparser.error('%s does not belong to a package.' %
self.args[0])
814 sys.exit(1)
815 self.args = []
816 self.options.filebug = True
817 self.options.package = pkg
This will not provide any useful information about what to do if the
'executable' is provided by a snap. Information similar to
https://code.launchpad.net/~juliank/ubuntu/bionic/apport/snap/+merge/342207
should be provided if the path is from a snap.
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/apport/+bug/1760220/+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 1752053] Re: nvidia-390 fails to boot graphical display
The uncommenting #WaylandEnable=false worked a treat for me as with the previous posters. This is the answer to this problem and needs pinning to the thread! -- 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/1752053 Title: nvidia-390 fails to boot graphical display Status in mesa package in Ubuntu: Fix Released Status in nvidia-graphics-drivers-390 package in Ubuntu: Fix Released Status in xserver-xorg-video-nouveau package in Ubuntu: Invalid Bug description: I'm using Bionic with the new 4.15 kernel. I've been using the nvidia-384 driver with no problem for a while. Today I issued "sudo apt-get upgrade" and I was prompted to upgrade the nvidia driver to the nvidia-390. After installing the driver and rebooting, I was only able to boot in to the tty terminal. The graphical display failed to boot. I have had similar problems with nvidia driver version 390 with Arch Linux and with Open Suse Tumbleweed. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mesa/+bug/1752053/+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 1659339] Re: "libmtp error: Could not send object" when copying a file to MTP folder
I had this error while copying a file to my phone. The file name was "Do You Hear What I Hear?.mp3" It stopped copying 2 mb into the 2.4 mb file. I removed the question mark from the file name and it copied perfectly. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to mtp in Ubuntu. https://bugs.launchpad.net/bugs/1659339 Title: "libmtp error: Could not send object" when copying a file to MTP folder Status in Linux Mint: New Status in mtp package in Ubuntu: Confirmed Bug description: Linux Mint 17.2/17.3/18/18.1 (problem arises in all of these). I connect my Android phone over MTP, LM opens the folder (for example "mtp://[usb:001,005]/Almacenamiento%20del%20tel%C3%A9fono"), then I try to copy a file from my filesystem to the phone. I get a window that says: Error while copying "foo.png".//There was an error copying the file into mtp://[usb:001,005]/Almacenamiento%20del%20tel%C3%A9fono/.//libmtp error: Could not send object info.//Cancel/Skip. I think that the copy operation should proceed and having my file "foo.png" in phone's memory. The problem happens always, indeed the copy never worked for me in any of the LM versions mentioned above, that is, from the very first time I used LM. I can read (copy) files from the phone to the laptop, and I can delete files from the phone. $ lsusb Bus 002 Device 002: ID 13b1:0041 Linksys Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 003: ID 064e:9700 Suyin Corp. Asus Integrated Webcam Bus 001 Device 005: ID 0bb4:0c02 HTC (High Tech Computer Corp.) Dream / ADP1 / G1 / Magic / Tattoo (Debug) Bus 001 Device 002: ID 0458:00f2 KYE Systems Corp. (Mouse Systems) Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub To manage notifications about this bug go to: https://bugs.launchpad.net/linuxmint/+bug/1659339/+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 1801540] Re: Microphone distorted sound on ALC892
1) Happens with both Front mic and Rear mic. 2) No, it still sounds bad. Something I found is that on FreeBSD is working fine. -- 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/1801540 Title: Microphone distorted sound on ALC892 Status in linux package in Ubuntu: Incomplete Status in pulseaudio package in Ubuntu: New Bug description: Not sure if I'll report this upstream but there is definitely an issue with microphone recording on my desktop, this is not happening on my laptop which has a different codec. Already tried all workarounds possible, no luck. Only with my desktop with this particular motherboard. No issues in Windows, the sound recorded in there is distorted and has some static and robotic tone on high-pitch. alsa-info on the attachments To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1801540/+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 1766969] Re: DNS cannot be resolved in Public / Hotel / Starbucks WiFi Hotspot
** Changed in: systemd (Ubuntu Artful) Status: Confirmed => Won't Fix -- 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/1766969 Title: DNS cannot be resolved in Public / Hotel / Starbucks WiFi Hotspot Status in systemd package in Ubuntu: Fix Released Status in systemd source package in Artful: Won't Fix Status in systemd source package in Bionic: Fix Released Status in systemd source package in Cosmic: Fix Released Bug description: [Impact] * More captive portals have been discovered that do not handle DNS requests with D0 set. * Thus extend previous aruba-networks fix from https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1727237 by retrying all NXDOMAIN results with lower feature levels just in case. [Test Case] * systemd-resolved something-nonexistant.ubuntu.com * monitor the logs, and check that the transaction has been downgraded multiple times and tried at least once at a feature level below D0. There should be a downgrade message in the log. * Note, it will be cached, thus one may need to call $ systemd-resolved --flush-caches [Regression Potential] * Legitimate NXDOMAIN queries will now take longer, as they will be retried multiple times with different features sets until an answer is found. At that point the query will be cached and will return quickly. This is needed to work-around bad captive portals that do not support dns queries with D0. Post-captive portal, the feature level can usually be cranked back up and it does after a grace period. [Other Info] * Original bug report I was asked to create a new bug for this in https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1727237 as it seems to be a different issue. I have installed the nightly image of Kubuntu Bionic from 25th of April. There systemd is in version 237-3ubuntu10. When connecting to the wifi hotspot in my hotel (Quality Hotel Augsburg) I cannot open the hotspot landing page that should give me access to the WIFI. With Windows and on an Iphone it's working. For the following distributions I can confirm it not working: Kubuntu 17.10 Kubuntu 18.04 (nightly image 25th of April 2018) The logs were taken on 18.04. Workaround: sudo systemctl disable systemd-resolved.service sudo service systemd-resolved stop sudo rm /etc/resolv.conf sudo nano /etc/NetworkManager/NetworkManager.conf >> add "dns=default" under [main] sudo service network-manager restart Then I can connect to the WIFI and I see the login page in Firefox. To capture some data I did the following: - connect to Hotspot - enter golem.de Case 1: Fresh default Kubuntu install With a default Kubuntu install it does not work. I can connect to the WIFI and get IP and DNS from DHCP but I cannot resolve any hostname. When trying to open the router ip directly in the browser it forwards to hotsplots.de which cannot be resolved. Case 2: With aforementioned Workaround I connect to the wifi, I open firefox and the login page shows up (if I havent been connected yet. In the capture I already was able to connect to the hotspot which allows immediately to connect to the webpage) PS: I'll be in this hotel till Friday 27th if more information are required. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1766969/+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 1752656] Re: Please SRU archive keyrings to older releases
** Description changed: While not necessarily a critical issue for the Ubuntu keyrings, as Debian uses newer keys periodically, it becomes impossible with the default keyrings to verify the latest Debian archive files. It seems reasonable to ensure the keyring contents in all releases are the same, as the latest release is reflecting the latest archives. + + Related: bug 1801725 -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to ubuntu-keyring in Ubuntu. https://bugs.launchpad.net/bugs/1752656 Title: Please SRU archive keyrings to older releases Status in debian-archive-keyring package in Ubuntu: New Status in ubuntu-keyring package in Ubuntu: New Bug description: While not necessarily a critical issue for the Ubuntu keyrings, as Debian uses newer keys periodically, it becomes impossible with the default keyrings to verify the latest Debian archive files. It seems reasonable to ensure the keyring contents in all releases are the same, as the latest release is reflecting the latest archives. Related: bug 1801725 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/debian-archive-keyring/+bug/1752656/+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 1801770] [NEW] /usr/bin/gdb:11:iterate_over_symtabs:collect_symtabs_from_filename:create_sals_line_offset:convert_linespec_to_sals:parse_linespec
Public bug reported: The Ubuntu Error Tracker has been receiving reports about a problem regarding gdb. This problem was most recently seen with package version 8.1-0ubuntu3, the problem page at https://errors.ubuntu.com/problem/04ece8063085fce50f8809e11d4432f3f6d8d7a7 contains more details, including versions of packages affected, stacktrace or traceback, and individual crash reports. If you do not have access to the Ubuntu Error Tracker and are a software developer, you can request it at http://forms.canonical.com/reports/. ** Affects: gdb (Ubuntu) Importance: Undecided Status: New ** Tags: artful bionic kylin-14.10 quantal saucy trusty utopic vivid wily xenial yakkety zesty -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to gdb in Ubuntu. https://bugs.launchpad.net/bugs/1801770 Title: /usr/bin/gdb:11:iterate_over_symtabs:collect_symtabs_from_filename:create_sals_line_offset:convert_linespec_to_sals:parse_linespec Status in gdb package in Ubuntu: New Bug description: The Ubuntu Error Tracker has been receiving reports about a problem regarding gdb. This problem was most recently seen with package version 8.1-0ubuntu3, the problem page at https://errors.ubuntu.com/problem/04ece8063085fce50f8809e11d4432f3f6d8d7a7 contains more details, including versions of packages affected, stacktrace or traceback, and individual crash reports. If you do not have access to the Ubuntu Error Tracker and are a software developer, you can request it at http://forms.canonical.com/reports/. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gdb/+bug/1801770/+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 1801522] Re: Ubuntu 18.10 boots into black screen
** Package changed: bash (Ubuntu) => gdm3 (Ubuntu) -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to bash in Ubuntu. https://bugs.launchpad.net/bugs/1801522 Title: Ubuntu 18.10 boots into black screen Status in gdm3 package in Ubuntu: New Bug description: I just upgraded from Ubuntu 18.04 to Ubuntu 18.10 on a Windows 10 dual boot machine. The machine has a Nvidia GeForce GTX 1080 GPU. I have tried to diagnose and fix the problem using prior posted solutions, such as video card issues with nomodeset(https://askubuntu.com/questions/162075/my-computer-boots- to-a-black-screen-what-options-do-i-have-to-fix-it and https://askubuntu.com/questions/1087559/cant-boot-ubuntu-properly- after-dual-boot-installation-with-windows-10) but this did not work, and the boot script no longer contains "quiet splash" anyways. Also in the boot script I set acpi = off but then I get another error, perhaps for another thread (PKCS#7 signature not signed with a trusted key), and the boot instead crashes on this error. In recovery mode (4.18.0-10-generic) I tried running fsck but could not unmount the partition. I am using 97% of my bootloader partition so I ran recovery mode's clean but that also did not fix the issue. I am not sure what else I should try - I anxiously await and appreciate any further guidance you may have. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gdm3/+bug/1801522/+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 1801762] [NEW] Dual-signed things should be easy to verify with one key
Public bug reported: As part of Ubuntu key rotation strategy, we rely on dual-signing (inline, or detached) such that validation with at least one key available in a keyring should be trusted, without using web-of-trust. However, it seems to be only correctly so far implemented by the apt's gpgv method. Ideally, we should ship an easy enough to use the helper that is `like gpgv` to use, and possibly reusing apt's gpgv code and/or exposing it via apt-key's verify. The problem seems to be that 1 good sig + 1 no public key available, results in gpgv exiting with 2, instead of 0 or 1. Ideally it should be easy enough to use gpgv/gpg to verify that at least one signature is good, and decrypt/extract signed contents only. More details and reproducers to follow. ** Affects: apt (Ubuntu) Importance: Undecided Status: New ** Affects: debmirror (Ubuntu) Importance: Undecided Status: New ** Affects: gnupg2 (Ubuntu) Importance: Undecided Status: New ** Affects: ubuntu-keyring (Ubuntu) Importance: Undecided Status: New ** Affects: ubuntu-release-upgrader (Ubuntu) Importance: Undecided Status: New ** Also affects: gnupg2 (Ubuntu) Importance: Undecided Status: New ** Also affects: apt (Ubuntu) Importance: Undecided Status: New ** Also affects: debmirror (Ubuntu) Importance: Undecided Status: New ** Also affects: ubuntu-release-upgrader (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to ubuntu-keyring in Ubuntu. https://bugs.launchpad.net/bugs/1801762 Title: Dual-signed things should be easy to verify with one key Status in apt package in Ubuntu: New Status in debmirror package in Ubuntu: New Status in gnupg2 package in Ubuntu: New Status in ubuntu-keyring package in Ubuntu: New Status in ubuntu-release-upgrader package in Ubuntu: New Bug description: As part of Ubuntu key rotation strategy, we rely on dual-signing (inline, or detached) such that validation with at least one key available in a keyring should be trusted, without using web-of-trust. However, it seems to be only correctly so far implemented by the apt's gpgv method. Ideally, we should ship an easy enough to use the helper that is `like gpgv` to use, and possibly reusing apt's gpgv code and/or exposing it via apt-key's verify. The problem seems to be that 1 good sig + 1 no public key available, results in gpgv exiting with 2, instead of 0 or 1. Ideally it should be easy enough to use gpgv/gpg to verify that at least one signature is good, and decrypt/extract signed contents only. More details and reproducers to follow. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apt/+bug/1801762/+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 1801747] Re: External display not recognized, internal one goes to black
Did this issue start happening after an update/upgrade? Was there a prior kernel version where you were not having this particular problem? Would it be possible for you to test the latest upstream kernel? Refer to https://wiki.ubuntu.com/KernelMainlineBuilds . Please test the latest v4.19 kernel[0]. If this bug is fixed in the mainline kernel, please add the following tag 'kernel-fixed-upstream'. If the mainline kernel does not fix this bug, please add the tag: 'kernel-bug-exists-upstream'. Once testing of the upstream kernel is complete, please mark this bug as "Confirmed". Thanks in advance. [0] http://kernel.ubuntu.com/~kernel-ppa/mainline/v4.19.1 ** Also affects: linux (Ubuntu) Importance: Undecided Status: New ** Changed in: linux (Ubuntu) Status: New => Incomplete ** Package changed: xorg (Ubuntu) => xorg-server (Ubuntu) -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to xorg in Ubuntu. https://bugs.launchpad.net/bugs/1801747 Title: External display not recognized, internal one goes to black Status in linux package in Ubuntu: Incomplete Status in xorg-server package in Ubuntu: New Bug description: Hi, I have 10 notebooks HP 1410s on which I replace XP/Vista with Ubuntu 18.04.1 I face a problem on ALL of them, as soon as I connect an external screen, doesn't matter VGA or HDMI, the internal screen goes black, only mouse icon is their, blinking from time to time but reacting. External screen does show nothing but there is no "no signal" info what means that source is recognized. As soon as I release the video cable from external display, the internal one come back to live after few seconds. The BIOS was updated to latest available. Daniel tootai@hirondelle:~$ lsb_release -rd Description: Ubuntu 18.04.1 LTS Release: 18.04 ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: xorg 1:7.7+19ubuntu7.1 ProcVersionSignature: Ubuntu 4.15.0-36.39-generic 4.15.18 Uname: Linux 4.15.0-36-generic x86_64 NonfreeKernelModules: wl ApportVersion: 2.20.9-0ubuntu7.4 Architecture: amd64 CompositorRunning: None Date: Mon Nov 5 16:30:38 2018 DistUpgraded: Fresh install DistroCodename: bionic DistroVariant: ubuntu DkmsStatus: bcmwl, 6.30.223.271+bdcom, 4.15.0-29-generic, x86_64: installed bcmwl, 6.30.223.271+bdcom, 4.15.0-36-generic, x86_64: installed ExtraDebuggingInterest: Yes GraphicsCard: Intel Corporation Mobile 4 Series Chipset Integrated Graphics Controller [8086:2a42] (rev 07) (prog-if 00 [VGA controller]) Subsystem: Hewlett-Packard Company Mobile 4 Series Chipset Integrated Graphics Controller [103c:3072] Subsystem: Hewlett-Packard Company Mobile 4 Series Chipset Integrated Graphics Controller [103c:3072] InstallationDate: Installed on 2018-10-19 (17 days ago) InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 (20180725) MachineType: Hewlett-Packard HP ProBook 4510s ProcEnviron: TERM=xterm-256color PATH=(custom, no user) LANG=fr_FR.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-36-generic root=UUID=6ddf18e3-f14e-4d1c-b2fd-ae58c6f697ed ro quiet splash vt.handoff=1 SourcePackage: xorg Symptom: display UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 12/02/2010 dmi.bios.vendor: Hewlett-Packard dmi.bios.version: 68PZI Ver. F.18 dmi.board.name: 3072 dmi.board.vendor: Hewlett-Packard dmi.board.version: KBC Version 24.0F dmi.chassis.asset.tag: CNU0012B8R dmi.chassis.type: 10 dmi.chassis.vendor: Hewlett-Packard dmi.modalias: dmi:bvnHewlett-Packard:bvr68PZIVer.F.18:bd12/02/2010:svnHewlett-Packard:pnHPProBook4510s:pvrF.18:rvnHewlett-Packard:rn3072:rvrKBCVersion24.0F:cvnHewlett-Packard:ct10:cvr: dmi.product.family: 103C_5336AN dmi.product.name: HP ProBook 4510s dmi.product.version: F.18 dmi.sys.vendor: Hewlett-Packard version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.91-2 version.libgl1-mesa-dri: libgl1-mesa-dri 18.0.5-0ubuntu0~18.04.1 version.libgl1-mesa-glx: libgl1-mesa-glx 18.0.5-0ubuntu0~18.04.1 version.xserver-xorg-core: xserver-xorg-core 2:1.19.6-1ubuntu4 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:18.0.1-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20171229-1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.15-2 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1801747/+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 1164016] Re: restore type-ahead find
I think the change is interesting - what seems annoying is to force the user - not letting us choose. In my case - installing back the old nautilus. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to ubuntu-settings in Ubuntu. https://bugs.launchpad.net/bugs/1164016 Title: restore type-ahead find Status in Nautilus: Expired Status in nautilus package in Ubuntu: Fix Released Status in ubuntu-settings package in Ubuntu: Fix Released Bug description: GNOME removed type-ahead find in Nautilus 3.6, not without controversy: https://mail.gnome.org/archives/nautilus- list/2012-August/msg2.html Now when you type in a Nautilus window, Nautilus immediately performs a search in the current directory and all its subdirectories. I personally find this annoying. If I want to search, I'll click the search icon. Often I'm looking at a long directory listing and simply want to jump to a certain point in it, and type-ahead find works great for that. Would Ubuntu consider patching type-ahead find back in? To manage notifications about this bug go to: https://bugs.launchpad.net/nautilus/+bug/1164016/+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 1801744] Re: package linux-image-4.4.0-139-generic 4.4.0-139.165 failed to install/upgrade: run-parts: /etc/kernel/postinst.d/initramfs-tools exited with return code 1
** Tags removed: need-duplicate-check -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to initramfs-tools in Ubuntu. https://bugs.launchpad.net/bugs/1801744 Title: package linux-image-4.4.0-139-generic 4.4.0-139.165 failed to install/upgrade: run-parts: /etc/kernel/postinst.d/initramfs-tools exited with return code 1 Status in initramfs-tools package in Ubuntu: New Bug description: don't know ProblemType: Package DistroRelease: Ubuntu 16.04 Package: linux-image-4.4.0-139-generic 4.4.0-139.165 ProcVersionSignature: Ubuntu 4.4.0-139.165-generic 4.4.160 Uname: Linux 4.4.0-139-generic x86_64 ApportVersion: 2.20.1-0ubuntu2.18 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: jaideep1604 F pulseaudio /dev/snd/controlC0: jaideep1604 F pulseaudio Date: Fri Nov 2 23:55:21 2018 ErrorMessage: run-parts: /etc/kernel/postinst.d/initramfs-tools exited with return code 1 HibernationDevice: RESUME=UUID=0dfe2ba1-25bb-463c-b5f0-85897090f1d1 InstallationDate: Installed on 2016-04-19 (930 days ago) InstallationMedia: Ubuntu 14.04.3 LTS "Trusty Tahr" - Beta amd64 (20150805) MachineType: LENOVO INVALID ProcFB: 0 radeondrmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.4.0-139-generic.efi.signed root=/dev/mapper/ubuntu--vg-root ro quiet splash vt.handoff=7 PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon. RelatedPackageVersions: grub-pc N/A SourcePackage: initramfs-tools Title: package linux-image-4.4.0-139-generic 4.4.0-139.165 failed to install/upgrade: run-parts: /etc/kernel/postinst.d/initramfs-tools exited with return code 1 UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 04/30/2015 dmi.bios.vendor: LENOVO dmi.bios.version: A2CN36WW(V2.04) dmi.board.asset.tag: No Asset Tag dmi.board.name: VIUU4 dmi.board.vendor: LENOVO dmi.board.version: 3192 PRO dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: INVALID dmi.modalias: dmi:bvnLENOVO:bvrA2CN36WW(V2.04):bd04/30/2015:svnLENOVO:pnINVALID:pvrINVALID:rvnLENOVO:rnVIUU4:rvr3192PRO:cvnLENOVO:ct10:cvrINVALID: dmi.product.name: INVALID dmi.product.version: INVALID dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/initramfs-tools/+bug/1801744/+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 1751252] Re: [regression] ubiquity crashed in debconf.py:104 with ValueError: invalid literal for int() with base 10: ''
Untargetting from cairo/bionic, the ubiquity fix is enough there
** No longer affects: cairo (Ubuntu Bionic)
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to cairo in Ubuntu.
https://bugs.launchpad.net/bugs/1751252
Title:
[regression] ubiquity crashed in debconf.py:104 with ValueError:
invalid literal for int() with base 10: ''
Status in cairo:
Unknown
Status in OEM Priority Project:
Fix Released
Status in cairo package in Ubuntu:
In Progress
Status in ubiquity package in Ubuntu:
Fix Released
Status in ubiquity source package in Bionic:
Fix Released
Bug description:
* Impact
The Ubuntu installer crashes on some machines (seems more often on hiDPI
machines (QHD/UHD etc)).
* Test case
Try installing Ubuntu on an hidpi machine, it should complete installation
instead of crashing.
* Regression potential
The fix in ubiquity touches the code handle uid drop/privilege, that can have
unexpected side effects so we need proper/complete testing of the installer
--
Update: Actually the crash occurs on slow-ish systems due to a race
condition. It's not strictly only hi-DPI machines - that's just the
most common place it is experienced.
---
https://errors.ubuntu.com/problem/82f7f7e7923663c7b2123c7f1f49af29f6ff4d77
https://errors.ubuntu.com/problem/735a2b847e0eeab6c8a7b954de5110e43889be15
https://errors.ubuntu.com/problem/dcd4c9da5ee0cc6d36324446e0e49d39705c90b7
https://errors.ubuntu.com/problem/cb82f70f9ede07369e8104da9ddf87e28b42257d
https://errors.ubuntu.com/problem/84a5563af3d2b85f098da832ece4cb8450bfd524
---
WORKAROUND:
1. Boot into the live session.
2. Settings > Devices > Displays > Scale = 100%
3. Click Apply.
4. Proceed with installation: Click "Install Ubuntu 18.04 LTS".
---
Crashed in a VM in the middle of installation. The host is Bionic up
to date.
From the journal
Feb 23 12:52:27 ubuntu kernel: traps: ubiquity[2646] trap int3
ip:7f5a76936961 sp:7ffde5090c50 error:0 in
libglib-2.0.so.0.5400.1[7f5a768e6000+111000]
Feb 23 12:52:41 ubuntu /install.py[6858]: Exception during installation:
Feb 23 12:52:41 ubuntu /install.py[6858]: Traceback (most recent call last):
Feb 23 12:52:41 ubuntu /install.py[6858]: File
"/usr/share/ubiquity/install.py", line 757, in
Feb 23 12:52:41 ubuntu /install.py[6858]: install.run()
Feb 23 12:52:41 ubuntu /install.py[6858]: File
"/usr/share/ubiquity/install.py", line 135, in run
Feb 23 12:52:41 ubuntu /install.py[6858]: self.copy_all()
Feb 23 12:52:41 ubuntu /install.py[6858]: File
"/usr/share/ubiquity/install.py", line 505, in copy_all
Feb 23 12:52:41 ubuntu /install.py[6858]: self.db.progress('SET', 10 +
copy_progress)
Feb 23 12:52:41 ubuntu /install.py[6858]: File
"/usr/lib/python3/dist-packages/debconf.py", line 83, in
Feb 23 12:52:41 ubuntu /install.py[6858]: lambda *args, **kw:
self.command(command, *args, **kw))
Feb 23 12:52:41 ubuntu /install.py[6858]: File
"/usr/lib/python3/dist-packages/debconf.py", line 104, in command
Feb 23 12:52:41 ubuntu /install.py[6858]: status = int(status)
Feb 23 12:52:41 ubuntu /install.py[6858]: ValueError: invalid literal for
int() with base 10: ''
ProblemType: Crash
DistroRelease: Ubuntu 18.04
Package: ubiquity 18.04.1
ProcVersionSignature: Ubuntu 4.13.0-32.35-generic 4.13.13
Uname: Linux 4.13.0-32-generic x86_64
ApportVersion: 2.20.8-0ubuntu10
Architecture: amd64
CasperVersion: 1.388
Date: Fri Feb 23 12:52:28 2018
ExecutablePath: /usr/lib/ubiquity/bin/ubiquity
InstallCmdLine: file=/cdrom/preseed/ubuntu.seed boot=casper
initrd=/casper/initrd.lz quiet splash --- keyboard-configuration/layoutcode=fr
keyboard-configuration/variantcode=oss
InterpreterPath: /usr/bin/python3.6
LiveMediaBuild: Ubuntu 18.04 LTS "Bionic Beaver" - Alpha amd64 (20180222)
ProcCmdline: /usr/bin/python3 /usr/lib/ubiquity/bin/ubiquity -d
ProcEnviron:
TERM=xterm-256color
PATH=(custom, no user)
LANG=C.UTF-8
SHELL=/bin/bash
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
Signal: 5
SourcePackage: ubiquity
StacktraceTop:
?? () from /usr/lib/x86_64-linux-gnu/libX11.so.6
?? () from /usr/lib/x86_64-linux-gnu/libX11.so.6
_XEventsQueued () from /usr/lib/x86_64-linux-gnu/libX11.so.6
XPending () from /usr/lib/x86_64-linux-gnu/libX11.so.6
?? () from /usr/lib/x86_64-linux-gnu/libgdk-3.so.0
Title: ubiquity crashed with signal 5 in _XEventsQueued()
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups:
To manage notifications about this bug go to:
https://bugs.launchpad.net/cairo/+bug/1751252/+subscriptions
--
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
[Touch-packages] [Bug 1801747] [NEW] External display not recognized, internal one goes to black
Public bug reported: Hi, I have 10 notebooks HP 1410s on which I replace XP/Vista with Ubuntu 18.04.1 I face a problem on ALL of them, as soon as I connect an external screen, doesn't matter VGA or HDMI, the internal screen goes black, only mouse icon is their, blinking from time to time but reacting. External screen does show nothing but there is no "no signal" info what means that source is recognized. As soon as I release the video cable from external display, the internal one come back to live after few seconds. The BIOS was updated to latest available. Daniel tootai@hirondelle:~$ lsb_release -rd Description:Ubuntu 18.04.1 LTS Release:18.04 ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: xorg 1:7.7+19ubuntu7.1 ProcVersionSignature: Ubuntu 4.15.0-36.39-generic 4.15.18 Uname: Linux 4.15.0-36-generic x86_64 NonfreeKernelModules: wl ApportVersion: 2.20.9-0ubuntu7.4 Architecture: amd64 CompositorRunning: None Date: Mon Nov 5 16:30:38 2018 DistUpgraded: Fresh install DistroCodename: bionic DistroVariant: ubuntu DkmsStatus: bcmwl, 6.30.223.271+bdcom, 4.15.0-29-generic, x86_64: installed bcmwl, 6.30.223.271+bdcom, 4.15.0-36-generic, x86_64: installed ExtraDebuggingInterest: Yes GraphicsCard: Intel Corporation Mobile 4 Series Chipset Integrated Graphics Controller [8086:2a42] (rev 07) (prog-if 00 [VGA controller]) Subsystem: Hewlett-Packard Company Mobile 4 Series Chipset Integrated Graphics Controller [103c:3072] Subsystem: Hewlett-Packard Company Mobile 4 Series Chipset Integrated Graphics Controller [103c:3072] InstallationDate: Installed on 2018-10-19 (17 days ago) InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 (20180725) MachineType: Hewlett-Packard HP ProBook 4510s ProcEnviron: TERM=xterm-256color PATH=(custom, no user) LANG=fr_FR.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-36-generic root=UUID=6ddf18e3-f14e-4d1c-b2fd-ae58c6f697ed ro quiet splash vt.handoff=1 SourcePackage: xorg Symptom: display UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 12/02/2010 dmi.bios.vendor: Hewlett-Packard dmi.bios.version: 68PZI Ver. F.18 dmi.board.name: 3072 dmi.board.vendor: Hewlett-Packard dmi.board.version: KBC Version 24.0F dmi.chassis.asset.tag: CNU0012B8R dmi.chassis.type: 10 dmi.chassis.vendor: Hewlett-Packard dmi.modalias: dmi:bvnHewlett-Packard:bvr68PZIVer.F.18:bd12/02/2010:svnHewlett-Packard:pnHPProBook4510s:pvrF.18:rvnHewlett-Packard:rn3072:rvrKBCVersion24.0F:cvnHewlett-Packard:ct10:cvr: dmi.product.family: 103C_5336AN dmi.product.name: HP ProBook 4510s dmi.product.version: F.18 dmi.sys.vendor: Hewlett-Packard version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.91-2 version.libgl1-mesa-dri: libgl1-mesa-dri 18.0.5-0ubuntu0~18.04.1 version.libgl1-mesa-glx: libgl1-mesa-glx 18.0.5-0ubuntu0~18.04.1 version.xserver-xorg-core: xserver-xorg-core 2:1.19.6-1ubuntu4 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:18.0.1-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20171229-1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.15-2 ** Affects: xorg (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug bionic ubuntu -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to xorg in Ubuntu. https://bugs.launchpad.net/bugs/1801747 Title: External display not recognized, internal one goes to black Status in xorg package in Ubuntu: New Bug description: Hi, I have 10 notebooks HP 1410s on which I replace XP/Vista with Ubuntu 18.04.1 I face a problem on ALL of them, as soon as I connect an external screen, doesn't matter VGA or HDMI, the internal screen goes black, only mouse icon is their, blinking from time to time but reacting. External screen does show nothing but there is no "no signal" info what means that source is recognized. As soon as I release the video cable from external display, the internal one come back to live after few seconds. The BIOS was updated to latest available. Daniel tootai@hirondelle:~$ lsb_release -rd Description: Ubuntu 18.04.1 LTS Release: 18.04 ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: xorg 1:7.7+19ubuntu7.1 ProcVersionSignature: Ubuntu 4.15.0-36.39-generic 4.15.18 Uname: Linux 4.15.0-36-generic x86_64 NonfreeKernelModules: wl ApportVersion: 2.20.9-0ubuntu7.4 Architecture: amd64 CompositorRunning: None Date: Mon Nov 5 16:30:38 2018 DistUpgraded: Fresh install DistroCodename: bionic DistroVariant: ubuntu DkmsStatus: bcmwl, 6.30.223.271+bdcom, 4.15.0-29-generic, x86_64: installed bcmwl, 6.30.223.271+bdcom, 4.15.0-36-generic, x86_64: installed ExtraDebuggingInterest: Yes GraphicsCard: Intel Corporation Mobile 4 Series Chipset Integrated Graphics Controller
[Touch-packages] [Bug 1742997] Re: Newly installed applications are not showing in "Installed"
** Changed in: packagekit (Ubuntu) Status: New => Invalid ** Changed in: packagekit (Ubuntu Bionic) Status: New => Invalid -- 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/1742997 Title: Newly installed applications are not showing in "Installed" Status in GNOME Software: Expired Status in gnome-software package in Ubuntu: Fix Released Status in packagekit package in Ubuntu: Invalid Status in gnome-software source package in Bionic: Confirmed Status in packagekit source package in Bionic: Invalid Bug description: If you install any application using GNOME Software (Ubuntu Software), the newly installed application is not displayed on the "Installed" tab. It starts showing after the next system reboot. Steps to Reproduce: 1. Find any application that is not installed and install it. 2. Switch to the "Installed" tab and try to find the newly installed application. To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-software/+bug/1742997/+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 1801744] [NEW] package linux-image-4.4.0-139-generic 4.4.0-139.165 failed to install/upgrade: run-parts: /etc/kernel/postinst.d/initramfs-tools exited with return code 1
Public bug reported: don't know ProblemType: Package DistroRelease: Ubuntu 16.04 Package: linux-image-4.4.0-139-generic 4.4.0-139.165 ProcVersionSignature: Ubuntu 4.4.0-139.165-generic 4.4.160 Uname: Linux 4.4.0-139-generic x86_64 ApportVersion: 2.20.1-0ubuntu2.18 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: jaideep1604 F pulseaudio /dev/snd/controlC0: jaideep1604 F pulseaudio Date: Fri Nov 2 23:55:21 2018 ErrorMessage: run-parts: /etc/kernel/postinst.d/initramfs-tools exited with return code 1 HibernationDevice: RESUME=UUID=0dfe2ba1-25bb-463c-b5f0-85897090f1d1 InstallationDate: Installed on 2016-04-19 (930 days ago) InstallationMedia: Ubuntu 14.04.3 LTS "Trusty Tahr" - Beta amd64 (20150805) MachineType: LENOVO INVALID ProcFB: 0 radeondrmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.4.0-139-generic.efi.signed root=/dev/mapper/ubuntu--vg-root ro quiet splash vt.handoff=7 PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon. RelatedPackageVersions: grub-pc N/A SourcePackage: initramfs-tools Title: package linux-image-4.4.0-139-generic 4.4.0-139.165 failed to install/upgrade: run-parts: /etc/kernel/postinst.d/initramfs-tools exited with return code 1 UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 04/30/2015 dmi.bios.vendor: LENOVO dmi.bios.version: A2CN36WW(V2.04) dmi.board.asset.tag: No Asset Tag dmi.board.name: VIUU4 dmi.board.vendor: LENOVO dmi.board.version: 3192 PRO dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: INVALID dmi.modalias: dmi:bvnLENOVO:bvrA2CN36WW(V2.04):bd04/30/2015:svnLENOVO:pnINVALID:pvrINVALID:rvnLENOVO:rnVIUU4:rvr3192PRO:cvnLENOVO:ct10:cvrINVALID: dmi.product.name: INVALID dmi.product.version: INVALID dmi.sys.vendor: LENOVO ** Affects: initramfs-tools (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-package package-from-proposed third-party-packages xenial -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to initramfs-tools in Ubuntu. https://bugs.launchpad.net/bugs/1801744 Title: package linux-image-4.4.0-139-generic 4.4.0-139.165 failed to install/upgrade: run-parts: /etc/kernel/postinst.d/initramfs-tools exited with return code 1 Status in initramfs-tools package in Ubuntu: New Bug description: don't know ProblemType: Package DistroRelease: Ubuntu 16.04 Package: linux-image-4.4.0-139-generic 4.4.0-139.165 ProcVersionSignature: Ubuntu 4.4.0-139.165-generic 4.4.160 Uname: Linux 4.4.0-139-generic x86_64 ApportVersion: 2.20.1-0ubuntu2.18 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: jaideep1604 F pulseaudio /dev/snd/controlC0: jaideep1604 F pulseaudio Date: Fri Nov 2 23:55:21 2018 ErrorMessage: run-parts: /etc/kernel/postinst.d/initramfs-tools exited with return code 1 HibernationDevice: RESUME=UUID=0dfe2ba1-25bb-463c-b5f0-85897090f1d1 InstallationDate: Installed on 2016-04-19 (930 days ago) InstallationMedia: Ubuntu 14.04.3 LTS "Trusty Tahr" - Beta amd64 (20150805) MachineType: LENOVO INVALID ProcFB: 0 radeondrmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.4.0-139-generic.efi.signed root=/dev/mapper/ubuntu--vg-root ro quiet splash vt.handoff=7 PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon. RelatedPackageVersions: grub-pc N/A SourcePackage: initramfs-tools Title: package linux-image-4.4.0-139-generic 4.4.0-139.165 failed to install/upgrade: run-parts: /etc/kernel/postinst.d/initramfs-tools exited with return code 1 UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 04/30/2015 dmi.bios.vendor: LENOVO dmi.bios.version: A2CN36WW(V2.04) dmi.board.asset.tag: No Asset Tag dmi.board.name: VIUU4 dmi.board.vendor: LENOVO dmi.board.version: 3192 PRO dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: INVALID dmi.modalias: dmi:bvnLENOVO:bvrA2CN36WW(V2.04):bd04/30/2015:svnLENOVO:pnINVALID:pvrINVALID:rvnLENOVO:rnVIUU4:rvr3192PRO:cvnLENOVO:ct10:cvrINVALID: dmi.product.name: INVALID dmi.product.version: INVALID dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/initramfs-tools/+bug/1801744/+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 1797649] Re: receive authentication canceled in terminal when changing options in "Other Software"
Works as expected in Xubuntu 18.10. Must be something in the ubuntu- session policykit/PAM/systemd auth? -- 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/1797649 Title: receive authentication canceled in terminal when changing options in "Other Software" Status in software-properties package in Ubuntu: Confirmed Bug description: I've tried to disable some PPAs in the "Other Software" tab of software-properties and whenever I check a box for the first time I get a message in the terminal about "ERROR:root:Authentication canceled, changes have not been saved" (although an authentication dialog has not appeared) and the dialog box greys out. However, frequently upon clicking the box for a second time (when it is greyed out) I am then presented with an authentication dialog. This seems quite odd. I've tested this the following versions of software-properties-gtk. 0.96.24.32.5 from bionic 0.26.27 from cosmic To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/software-properties/+bug/1797649/+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 1740894] Re: KEY_RFKILL is not passed to userspace
@Mario, does disable/enabling airplane mode works if done from gnome- control-center (the wifi panel has the control)? Not sure that qualify as a verification-failed though, the fix there is to make the key being recognized, and that seems to work. The fact that the backend fails to re-enable is probably another problem. Also could you attach your journalctl log after getting the "fail to re- enable" issue? -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to libxkbcommon in Ubuntu. https://bugs.launchpad.net/bugs/1740894 Title: KEY_RFKILL is not passed to userspace Status in libxkbcommon package in Ubuntu: Fix Released Status in xkeyboard-config package in Ubuntu: Fix Released Status in xorgproto package in Ubuntu: Fix Released Status in xkeyboard-config source package in Bionic: Fix Committed Status in xkeyboard-config source package in Cosmic: Fix Committed Bug description: * Impact the airplane mode key doesn't work in GNOME * Test case Use a laptop with a key to activate airplane mode, it should toggle the corresponding mode on/off when used * Regression potential The change adds a new key definition but doesn't touch any existing one, nothing specific to test out of the new key working - There are a couple things going on, that could be fixed by a Debian or Ubuntu maintainer: - libxkbdcommon needs to be updated from 0.7.1 to 0.7.2. This introduces the RFKill key: https://lists.freedesktop.org/archives /wayland-devel/2017-August/034721.html - x11-proto needs a new release. This commit added RFKill, but it is not in a release: https://cgit.freedesktop.org/xorg/proto/xproto/commit/?id=98a32d328e7195e12c38baa877917335bceffbaf - Likely other X11 packages need to be rebuilt. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libxkbcommon/+bug/1740894/+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 1795921] Re: Out-of-Bounds write in systemd-networkd dhcpv6 option handling
Hi,
There is still no updates available on bionic : according to
security.gentoo.org affected versions < 'systemd-239', while candidate
in bionic-updates is '237-3ubuntu10.3'. Is there any manual method to
fix it, while waiting for the updated version ?
Source: https://security.gentoo.org/glsa/201810-10
--
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/1795921
Title:
Out-of-Bounds write in systemd-networkd dhcpv6 option handling
Status in systemd package in Ubuntu:
Confirmed
Bug description:
systemd-networkd contains a DHCPv6 client which is written from
scratch and can be spawned automatically on managed interfaces when
IPv6 router advertisement are received:
"Note that DHCPv6 will by default be triggered by Router Advertisement, if
that is enabled, regardless of this parameter. By enabling DHCPv6 support
explicitly, the DHCPv6 client will be started regardless of the presence of
routers on the link, or what flags the routers pass"
(https://www.freedesktop.org/software/systemd/man/systemd.network.html)
The function dhcp6_option_append_ia function is used to encode Identity
Associations received by the server into the options buffer of an outgoing
DHCPv6 packet:
//
https://github.com/systemd/systemd/blob/master/src/libsystemd-network/dhcp6-option.c#L82
int dhcp6_option_append_ia(uint8_t **buf, size_t *buflen, DHCP6IA *ia) {
uint16_t len;
uint8_t *ia_hdr;
size_t iaid_offset, ia_buflen, ia_addrlen = 0;
DHCP6Address *addr;
int r;
assert_return(buf && *buf && buflen && ia, -EINVAL);
switch (ia->type) {
case SD_DHCP6_OPTION_IA_NA:
len = DHCP6_OPTION_IA_NA_LEN;
iaid_offset = offsetof(DHCP6IA, ia_na);
break;
case SD_DHCP6_OPTION_IA_TA:
len = DHCP6_OPTION_IA_TA_LEN;
iaid_offset = offsetof(DHCP6IA, ia_ta);
break;
default:
return -EINVAL;
}
A: if (*buflen < len)
return -ENOBUFS;
ia_hdr = *buf;
ia_buflen = *buflen;
*buf += sizeof(DHCP6Option);
B: *buflen -= sizeof(DHCP6Option);
C: memcpy(*buf, (char*) ia + iaid_offset, len);
*buf += len;
D: *buflen -= len;
E:LIST_FOREACH(addresses, addr, ia->addresses) {
r = option_append_hdr(buf, buflen, SD_DHCP6_OPTION_IAADDR,
sizeof(addr->iaaddr));
if (r < 0)
return r;
memcpy(*buf, >iaaddr, sizeof(addr->iaaddr));
*buf += sizeof(addr->iaaddr);
*buflen -= sizeof(addr->iaaddr);
ia_addrlen += sizeof(DHCP6Option) + sizeof(addr->iaaddr);
}
r = option_append_hdr(_hdr, _buflen, ia->type, len +
ia_addrlen);
if (r < 0)
return r;
return 0;
}
The function receives a pointer to the option buffer buf, it's remaining size
buflen and the IA to be added to the buffer. While the check at (A) tries to
ensure that the buffer has enough space left to store the IA option, it does
not take the additional 4 bytes from the DHCP6Option header into account (B).
Due to this the memcpy at (C) can go out-of-bound and *buflen can underflow in
(D) giving an attacker a very powerful and largely controlled OOB heap write
starting at (E).
The overflow can be triggered relatively easy by advertising a DHCPv6
server with a server-id >= 493 characters long. This will trigger the
following code once the client tries to create a REQUEST message:
//https://github.com/systemd/systemd/blob/7bcf8123c0305131ace02480763377af974924ef/src/libsystemd-network/sd-dhcp6-client.c#L493
case DHCP6_STATE_REQUEST:
case DHCP6_STATE_RENEW:
if (client->state == DHCP6_STATE_REQUEST)
message->type = DHCP6_REQUEST;
else
message->type = DHCP6_RENEW;
A: r = dhcp6_option_append(, ,
SD_DHCP6_OPTION_SERVERID,
client->lease->serverid_len,
client->lease->serverid);
if (r < 0)
return r;
if (FLAGS_SET(client->request, DHCP6_REQUEST_IA_NA)) {
B: r = dhcp6_option_append_ia(, ,
>lease->ia);
if (r < 0)
return r;
}
optlen starts with the value 512 and gets decreased to 15 (512 - 493 -
4) after the call in A. As 15 > DHCP6_OPTION_IA_NA_LEN but 15 <
(DHCP6_OPTION_IA_NA_LEN + 4)
[Touch-packages] [Bug 1801522] Re: Ubuntu 18.10 boots into black screen
** Package changed: ubuntu => bash (Ubuntu) -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to bash in Ubuntu. https://bugs.launchpad.net/bugs/1801522 Title: Ubuntu 18.10 boots into black screen Status in bash package in Ubuntu: New Bug description: I just upgraded from Ubuntu 18.04 to Ubuntu 18.10 on a Windows 10 dual boot machine. The machine has a Nvidia GeForce GTX 1080 GPU. I have tried to diagnose and fix the problem using prior posted solutions, such as video card issues with nomodeset(https://askubuntu.com/questions/162075/my-computer-boots- to-a-black-screen-what-options-do-i-have-to-fix-it and https://askubuntu.com/questions/1087559/cant-boot-ubuntu-properly- after-dual-boot-installation-with-windows-10) but this did not work, and the boot script no longer contains "quiet splash" anyways. Also in the boot script I set acpi = off but then I get another error, perhaps for another thread (PKCS#7 signature not signed with a trusted key), and the boot instead crashes on this error. In recovery mode (4.18.0-10-generic) I tried running fsck but could not unmount the partition. I am using 97% of my bootloader partition so I ran recovery mode's clean but that also did not fix the issue. I am not sure what else I should try - I anxiously await and appreciate any further guidance you may have. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bash/+bug/1801522/+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 1801522] [NEW] Ubuntu 18.10 boots into black screen
You have been subscribed to a public bug: I just upgraded from Ubuntu 18.04 to Ubuntu 18.10 on a Windows 10 dual boot machine. The machine has a Nvidia GeForce GTX 1080 GPU. I have tried to diagnose and fix the problem using prior posted solutions, such as video card issues with nomodeset(https://askubuntu.com/questions/162075/my-computer-boots-to-a -black-screen-what-options-do-i-have-to-fix-it and https://askubuntu.com/questions/1087559/cant-boot-ubuntu-properly-after- dual-boot-installation-with-windows-10) but this did not work, and the boot script no longer contains "quiet splash" anyways. Also in the boot script I set acpi = off but then I get another error, perhaps for another thread (PKCS#7 signature not signed with a trusted key), and the boot instead crashes on this error. In recovery mode (4.18.0-10-generic) I tried running fsck but could not unmount the partition. I am using 97% of my bootloader partition so I ran recovery mode's clean but that also did not fix the issue. I am not sure what else I should try - I anxiously await and appreciate any further guidance you may have. ** Affects: bash (Ubuntu) Importance: Undecided Status: New ** Tags: bot-comment -- Ubuntu 18.10 boots into black screen https://bugs.launchpad.net/bugs/1801522 You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to bash in Ubuntu. -- 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 1801716] Re: Xorg freeze (black screen after ubuntu logo during boot)
Did this issue start happening after an update/upgrade? Was there a prior kernel version where you were not having this particular problem? Would it be possible for you to test the latest upstream kernel? Refer to https://wiki.ubuntu.com/KernelMainlineBuilds . Please test the latest v4.19 kernel[0]. If this bug is fixed in the mainline kernel, please add the following tag 'kernel-fixed-upstream'. If the mainline kernel does not fix this bug, please add the tag: 'kernel-bug-exists-upstream'. Once testing of the upstream kernel is complete, please mark this bug as "Confirmed". Thanks in advance. [0] http://kernel.ubuntu.com/~kernel-ppa/mainline/v4.19 ** Also affects: linux (Ubuntu) Importance: Undecided Status: New ** Changed in: linux (Ubuntu) Status: New => Incomplete ** Package changed: xorg (Ubuntu) => xorg-server (Ubuntu) -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to xorg in Ubuntu. https://bugs.launchpad.net/bugs/1801716 Title: Xorg freeze (black screen after ubuntu logo during boot) Status in linux package in Ubuntu: Incomplete Status in xorg-server package in Ubuntu: New Bug description: I experienced this bug ever since I have upgraded my laptop from 16.04. But it got resolved in my last update after I reported the bug. However, I forgot to go back to Launchpad to mark it as resolved and now the problem comes again after I just updated the system. So, as the title stated, I can't get in the system due to the infinite black screen I am facing. I am only able to report this bug under the recovery mode. Besides, there's something wrong with the lock screen too. I can't get back to the system if I just put the system into "sleep mode". Black screen again! What's worst, the brightness of my display can't be adjusted as well! I feel like being blind at night! Please help!!! Thank you! And I think there might be the compatibility problem between my laptop and the new desktop -- Gnome, which is the default in 18.04. What should do? I really love using Ubuntu, as I really learned a lot in these days I used it as my study os for CS. Any help is appreciated, thanks in advance! ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: xorg 1:7.7+19ubuntu7.1 Uname: Linux 4.17.0-041700rc3-generic x86_64 .tmp.unity_support_test.1: ApportVersion: 2.20.9-0ubuntu7.4 Architecture: amd64 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Mon Nov 5 19:49:36 2018 DistUpgraded: Fresh install DistroCodename: bionic DistroVariant: ubuntu ExtraDebuggingInterest: Yes, if not too technical GpuHangFrequency: Continuously GpuHangReproducibility: Yes, I can easily reproduce it GpuHangStarted: Today GraphicsCard: Intel Corporation HD Graphics 5300 [8086:161e] (rev 08) (prog-if 00 [VGA controller]) Subsystem: ASUSTeK Computer Inc. HD Graphics 5300 [1043:15fd] InstallationDate: Installed on 2018-04-04 (215 days ago) InstallationMedia: Ubuntu 16.04.4 LTS "Xenial Xerus" - Release amd64 (20180228) MachineType: ASUSTeK COMPUTER INC. T300FA ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.17.0-041700rc3-generic root=UUID=63fcbd04-ec8b-462c-ba66-4f45c229353c ro recovery nomodeset Renderer: Software SourcePackage: xorg Symptom: display Title: Xorg freeze UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 09/01/2015 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: T300FA.214 dmi.board.asset.tag: ATN12345678901234567 dmi.board.name: T300FA dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: 1.0 dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: ASUSTeK COMPUTER INC. dmi.chassis.version: 1.0 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrT300FA.214:bd09/01/2015:svnASUSTeKCOMPUTERINC.:pnT300FA:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnT300FA:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0: dmi.product.family: T dmi.product.name: T300FA dmi.product.version: 1.0 dmi.sys.vendor: ASUSTeK COMPUTER INC. version.compiz: compiz 1:0.9.13.1+18.04.20180302-0ubuntu1 version.libdrm2: libdrm2 2.4.91-2 version.libgl1-mesa-dri: libgl1-mesa-dri 18.0.5-0ubuntu0~18.04.1 version.libgl1-mesa-glx: libgl1-mesa-glx 18.0.5-0ubuntu0~18.04.1 version.xserver-xorg-core: xserver-xorg-core 2:1.19.6-1ubuntu4.2 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.10.5-1ubuntu1 version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:18.0.1-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20171229-1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.15-2 xserver.bootTime: Tue Nov 6 03:47:33 2018 xserver.configfile: default xserver.errors: open /dev/dri/card0: No such file or directory open
[Touch-packages] [Bug 1801716] [NEW] Xorg freeze (black screen after ubuntu logo during boot)
Public bug reported: I experienced this bug ever since I have upgraded my laptop from 16.04. But it got resolved in my last update after I reported the bug. However, I forgot to go back to Launchpad to mark it as resolved and now the problem comes again after I just updated the system. So, as the title stated, I can't get in the system due to the infinite black screen I am facing. I am only able to report this bug under the recovery mode. Besides, there's something wrong with the lock screen too. I can't get back to the system if I just put the system into "sleep mode". Black screen again! What's worst, the brightness of my display can't be adjusted as well! I feel like being blind at night! Please help!!! Thank you! And I think there might be the compatibility problem between my laptop and the new desktop -- Gnome, which is the default in 18.04. What should do? I really love using Ubuntu, as I really learned a lot in these days I used it as my study os for CS. Any help is appreciated, thanks in advance! ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: xorg 1:7.7+19ubuntu7.1 Uname: Linux 4.17.0-041700rc3-generic x86_64 .tmp.unity_support_test.1: ApportVersion: 2.20.9-0ubuntu7.4 Architecture: amd64 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Mon Nov 5 19:49:36 2018 DistUpgraded: Fresh install DistroCodename: bionic DistroVariant: ubuntu ExtraDebuggingInterest: Yes, if not too technical GpuHangFrequency: Continuously GpuHangReproducibility: Yes, I can easily reproduce it GpuHangStarted: Today GraphicsCard: Intel Corporation HD Graphics 5300 [8086:161e] (rev 08) (prog-if 00 [VGA controller]) Subsystem: ASUSTeK Computer Inc. HD Graphics 5300 [1043:15fd] InstallationDate: Installed on 2018-04-04 (215 days ago) InstallationMedia: Ubuntu 16.04.4 LTS "Xenial Xerus" - Release amd64 (20180228) MachineType: ASUSTeK COMPUTER INC. T300FA ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.17.0-041700rc3-generic root=UUID=63fcbd04-ec8b-462c-ba66-4f45c229353c ro recovery nomodeset Renderer: Software SourcePackage: xorg Symptom: display Title: Xorg freeze UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 09/01/2015 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: T300FA.214 dmi.board.asset.tag: ATN12345678901234567 dmi.board.name: T300FA dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: 1.0 dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: ASUSTeK COMPUTER INC. dmi.chassis.version: 1.0 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrT300FA.214:bd09/01/2015:svnASUSTeKCOMPUTERINC.:pnT300FA:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnT300FA:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0: dmi.product.family: T dmi.product.name: T300FA dmi.product.version: 1.0 dmi.sys.vendor: ASUSTeK COMPUTER INC. version.compiz: compiz 1:0.9.13.1+18.04.20180302-0ubuntu1 version.libdrm2: libdrm2 2.4.91-2 version.libgl1-mesa-dri: libgl1-mesa-dri 18.0.5-0ubuntu0~18.04.1 version.libgl1-mesa-glx: libgl1-mesa-glx 18.0.5-0ubuntu0~18.04.1 version.xserver-xorg-core: xserver-xorg-core 2:1.19.6-1ubuntu4.2 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.10.5-1ubuntu1 version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:18.0.1-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20171229-1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.15-2 xserver.bootTime: Tue Nov 6 03:47:33 2018 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.19.6-1ubuntu4.2 ** Affects: xorg (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug bionic freeze ubuntu -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to xorg in Ubuntu. https://bugs.launchpad.net/bugs/1801716 Title: Xorg freeze (black screen after ubuntu logo during boot) Status in xorg package in Ubuntu: New Bug description: I experienced this bug ever since I have upgraded my laptop from 16.04. But it got resolved in my last update after I reported the bug. However, I forgot to go back to Launchpad to mark it as resolved and now the problem comes again after I just updated the system. So, as the title stated, I can't get in the system due to the infinite black screen I am facing. I am only able to report this bug under the recovery mode. Besides, there's something wrong with the lock screen too. I can't get back to the system if I just put the system into "sleep mode". Black screen again! What's worst, the brightness of my display can't be adjusted as well! I feel like being blind at
[Touch-packages] [Bug 1770082] Re: systemd-networkd not renaming devices on boot
@Mathieu: I reinstalled my Virtualbox VM (using the ubuntu-18.04-server-
amd64.iso image) and tested again and the result was the same.
netplan config:
ubuntu@ubuntu:~$ cat /etc/netplan/01-netcfg.yaml
# This file describes the network interfaces available on your system
# For more information, see netplan(5).
network:
version: 2
renderer: networkd
ethernets:
eth0:
match:
macaddress: 08:00:27:f0:97:15
set-name: eth0
dhcp4: yes
Result after reboot:
ubuntu@ubuntu:~$ ip address show
1: lo: mtu 65536 qdisc noqueue state UNKNOWN group
default qlen 1000
link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00
inet 127.0.0.1/8 scope host lo
valid_lft forever preferred_lft forever
inet6 ::1/128 scope host
valid_lft forever preferred_lft forever
2: eth0: mtu 1500 qdisc noop state DOWN group default
qlen 1000
link/ether 08:00:27:f0:97:15 brd ff:ff:ff:ff:ff:ff
As you can see, the interface is successfully renamed, but the IP
address is not applied.
Do you have an idea why it works with the ubuntu-18.04-live-server-
amd64.iso image and not with ubuntu-18.04-server-amd64.iso? Perhaps it
depends on something from cloud-init package?
--
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/1770082
Title:
systemd-networkd not renaming devices on boot
Status in netplan:
Fix Released
Status in cloud-init package in Ubuntu:
Confirmed
Status in netplan.io package in Ubuntu:
Fix Released
Status in nplan package in Ubuntu:
Fix Released
Status in systemd package in Ubuntu:
Confirmed
Status in nplan source package in Xenial:
Fix Released
Status in netplan.io source package in Bionic:
Fix Committed
Status in netplan.io source package in Cosmic:
Fix Committed
Bug description:
[Impact]
Systems relying on renaming network interfaces at boot and when 'netplan
apply' is run.
[Test case]
- Write a new netplan YAML (adjusting for current system as necessary):
network:
version: 2
ethernets:
ens3:
dhcp4: true
match:
macaddress: 52:54:00:de:bd:f6
set-name: myif0
- Bring down interface : 'ip link set dev ens3 down'
- Run 'netplan apply'
- Verify that the device is correctly renamed to 'myif0'.
- Reboot.
- Make sure the device is correctly renamed to 'myif0'.
[Regression potential]
Changes in rename logic to add udev rules may otherwise impact applying
different settings to the network interfaces. Changes in settings on network
interfaces, missing parameters (especially on bonds, bridges) should be
investigated as potential regressions. Other failures to apply network settings
might also happen if there's a race between applying renames via the udev
rules, and using the new names to apply configuration changes to the interfaces.
=== systemd issue ===
Renaming devices doesn't seem to work.
If I disable all other network configuration and create
/etc/systemd/network/10-network.link with:
[Match]
MACAddress=52:54:00:c1:c9:bb
[Link]
Name=myiface3
I expect this to cause the device with that MAC address to be renamed
to myiface3. However, when I reboot, I instead see:
$ ip l
1: lo: mtu 65536 qdisc noqueue state UNKNOWN mode
DEFAULT group default qlen 1000
link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00
2: ens3: mtu 1500 qdisc noop state DOWN mode DEFAULT
group default qlen 1000
link/ether 52:54:00:c1:c9:bb brd ff:ff:ff:ff:ff:ff
The device is not renamed.
This link file is pretty much identical to Example 2 in
https://www.freedesktop.org/software/systemd/man/systemd.link.html.
The renaming does work if I boot with net.ifnames=0, and oddly, it
also works if I unbind the device and rebind it as netplan apply does.
No setting of NamePolicy seems to help.
=== Original Bug ==
'set-name:' doesn't change the name of a network interface on boot, it
only works when you do netplan apply.
Say I take this 50-cloud-init.yaml file:
# This file is generated from information provided by
# the datasource. Changes to it will not persist across an instance.
# To disable cloud-init's network configuration capabilities, write a file
# /etc/cloud/cloud.cfg.d/99-disable-network-config.cfg with the following:
# network: {config: disabled}
network:
version: 2
ethernets:
ens3:
dhcp4: true
match:
macaddress: 52:54:00:de:bd:f6
set-name: ens3
Say I change set-name to 'myiface3' and reboot. I expect that the
device will be called myiface3 and brought up fine with dhcp. However,
instead I see:
$ ip a
1: lo: mtu 65536 qdisc noqueue state UNKNOWN group
default qlen 1000
link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00
inet 127.0.0.1/8 scope host lo
[Touch-packages] [Bug 1801383] Re: the WifiSyslog apport hook (used in firefox/tb) includes SSID informations
** Changed in: firefox (Ubuntu) Assignee: (unassigned) => Olivier Tilloy (osomon) -- 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/1801383 Title: the WifiSyslog apport hook (used in firefox/tb) includes SSID informations Status in apport package in Ubuntu: New Status in firefox package in Ubuntu: New Status in thunderbird package in Ubuntu: New Bug description: When I apport-bug certain packages such as firefox for example, it uploads the WifiSyslog.txt file. The WifiSyslog may contain a list of all system connections enumerated in /etc/NetworkManager/system-connections, i.e. all SSIDs the user has ever connected to that are found in the system-connections. This is a serious privacy risk and completely unnecessary information for most bug reports. Should either remove WifiSyslog as a requirement for packages that don't need it (should I report this to https://bugs.launchpad.net/ubuntu/+source/firefox/ ?), or redact information that may contain usernames and SSIDs from the log file. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: apport 2.20.9-0ubuntu7.4 ProcVersionSignature: User Name 4.15.0-38.41-generic 4.15.18 Uname: Linux 4.15.0-38-generic x86_64 ApportLog: ApportVersion: 2.20.9-0ubuntu7.4 Architecture: amd64 CrashReports: 640:1000:117:62475:2018-11-01 19:17:29.982295751 -0400:2018-11-01 19:17:30.982295751 -0400:/var/crash/_usr_bin_gnome-screenshot.1000.crash CurrentDesktop: ubuntu:GNOME Date: Fri Nov 2 11:24:20 2018 EcryptfsInUse: Yes InstallationDate: Installed on 2018-09-12 (50 days ago) InstallationMedia: Ubuntu 16.04.5 LTS "Xenial Xerus" - Release amd64 (20180731) PackageArchitecture: all ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: apport UpgradeStatus: Upgraded to bionic on 2018-09-28 (34 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apport/+bug/1801383/+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 1801383] Re: apport uploading WifiSyslog to public bug reports is a major privacy risk
** Also affects: firefox (Ubuntu) Importance: Undecided Status: New ** Also affects: thunderbird (Ubuntu) Importance: Undecided Status: New ** Summary changed: - apport uploading WifiSyslog to public bug reports is a major privacy risk + the WifiSyslog apport hook (used in firefox/tb) includes SSID informations -- 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/1801383 Title: the WifiSyslog apport hook (used in firefox/tb) includes SSID informations Status in apport package in Ubuntu: New Status in firefox package in Ubuntu: New Status in thunderbird package in Ubuntu: New Bug description: When I apport-bug certain packages such as firefox for example, it uploads the WifiSyslog.txt file. The WifiSyslog may contain a list of all system connections enumerated in /etc/NetworkManager/system-connections, i.e. all SSIDs the user has ever connected to that are found in the system-connections. This is a serious privacy risk and completely unnecessary information for most bug reports. Should either remove WifiSyslog as a requirement for packages that don't need it (should I report this to https://bugs.launchpad.net/ubuntu/+source/firefox/ ?), or redact information that may contain usernames and SSIDs from the log file. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: apport 2.20.9-0ubuntu7.4 ProcVersionSignature: User Name 4.15.0-38.41-generic 4.15.18 Uname: Linux 4.15.0-38-generic x86_64 ApportLog: ApportVersion: 2.20.9-0ubuntu7.4 Architecture: amd64 CrashReports: 640:1000:117:62475:2018-11-01 19:17:29.982295751 -0400:2018-11-01 19:17:30.982295751 -0400:/var/crash/_usr_bin_gnome-screenshot.1000.crash CurrentDesktop: ubuntu:GNOME Date: Fri Nov 2 11:24:20 2018 EcryptfsInUse: Yes InstallationDate: Installed on 2018-09-12 (50 days ago) InstallationMedia: Ubuntu 16.04.5 LTS "Xenial Xerus" - Release amd64 (20180731) PackageArchitecture: all ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: apport UpgradeStatus: Upgraded to bionic on 2018-09-28 (34 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apport/+bug/1801383/+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 1801383] Re: apport uploading WifiSyslog to public bug reports is a major privacy risk
Thank you for your bug report, that indeed seems an issue What apport does is provide a 'attach_wifi' that includes "report['WifiSyslog'] = recent_syslog(re.compile(r'(NetworkManager|modem-manager|dhclient|kernel|wpa_supplicant)(\[\d+\])?:'))" Some though - the n-m stack should probably not include those info in syslog/journal by default - the apport hook should anonymize the log in that such info are there - firefox/tb uses that function, maybe that's not needed? -- 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/1801383 Title: the WifiSyslog apport hook (used in firefox/tb) includes SSID informations Status in apport package in Ubuntu: New Status in firefox package in Ubuntu: New Status in thunderbird package in Ubuntu: New Bug description: When I apport-bug certain packages such as firefox for example, it uploads the WifiSyslog.txt file. The WifiSyslog may contain a list of all system connections enumerated in /etc/NetworkManager/system-connections, i.e. all SSIDs the user has ever connected to that are found in the system-connections. This is a serious privacy risk and completely unnecessary information for most bug reports. Should either remove WifiSyslog as a requirement for packages that don't need it (should I report this to https://bugs.launchpad.net/ubuntu/+source/firefox/ ?), or redact information that may contain usernames and SSIDs from the log file. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: apport 2.20.9-0ubuntu7.4 ProcVersionSignature: User Name 4.15.0-38.41-generic 4.15.18 Uname: Linux 4.15.0-38-generic x86_64 ApportLog: ApportVersion: 2.20.9-0ubuntu7.4 Architecture: amd64 CrashReports: 640:1000:117:62475:2018-11-01 19:17:29.982295751 -0400:2018-11-01 19:17:30.982295751 -0400:/var/crash/_usr_bin_gnome-screenshot.1000.crash CurrentDesktop: ubuntu:GNOME Date: Fri Nov 2 11:24:20 2018 EcryptfsInUse: Yes InstallationDate: Installed on 2018-09-12 (50 days ago) InstallationMedia: Ubuntu 16.04.5 LTS "Xenial Xerus" - Release amd64 (20180731) PackageArchitecture: all ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: apport UpgradeStatus: Upgraded to bionic on 2018-09-28 (34 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apport/+bug/1801383/+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 1801383] Re: apport uploading WifiSyslog to public bug reports is a major privacy risk
** Information type changed from Private Security to Public Security -- 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/1801383 Title: apport uploading WifiSyslog to public bug reports is a major privacy risk Status in apport package in Ubuntu: New Bug description: When I apport-bug certain packages such as firefox for example, it uploads the WifiSyslog.txt file. The WifiSyslog may contain a list of all system connections enumerated in /etc/NetworkManager/system-connections, i.e. all SSIDs the user has ever connected to that are found in the system-connections. This is a serious privacy risk and completely unnecessary information for most bug reports. Should either remove WifiSyslog as a requirement for packages that don't need it (should I report this to https://bugs.launchpad.net/ubuntu/+source/firefox/ ?), or redact information that may contain usernames and SSIDs from the log file. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: apport 2.20.9-0ubuntu7.4 ProcVersionSignature: User Name 4.15.0-38.41-generic 4.15.18 Uname: Linux 4.15.0-38-generic x86_64 ApportLog: ApportVersion: 2.20.9-0ubuntu7.4 Architecture: amd64 CrashReports: 640:1000:117:62475:2018-11-01 19:17:29.982295751 -0400:2018-11-01 19:17:30.982295751 -0400:/var/crash/_usr_bin_gnome-screenshot.1000.crash CurrentDesktop: ubuntu:GNOME Date: Fri Nov 2 11:24:20 2018 EcryptfsInUse: Yes InstallationDate: Installed on 2018-09-12 (50 days ago) InstallationMedia: Ubuntu 16.04.5 LTS "Xenial Xerus" - Release amd64 (20180731) PackageArchitecture: all ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: apport UpgradeStatus: Upgraded to bionic on 2018-09-28 (34 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apport/+bug/1801383/+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 1801410] Re: Icons.keep.flashing
Thanks for taking the time to report this bug and helping to make Ubuntu better. We appreciate the difficulties you are facing, but this appears to be a "regular" (non-security) bug. I have unmarked it as a security issue since this bug does not show evidence of allowing attackers to cross privilege boundaries nor directly cause loss of data/privacy. Please feel free to report any other bugs you may find. ** Information type changed from Private Security to Public -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to xorg in Ubuntu. https://bugs.launchpad.net/bugs/1801410 Title: Icons.keep.flashing Status in xorg package in Ubuntu: New Bug description: lost.use.of.space.key very.slow.internet.connection Icons.keep.flashing ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: xorg 1:7.7+19ubuntu7.1 ProcVersionSignature: Ubuntu 4.15.0-36.39-generic 4.15.18 Uname: Linux 4.15.0-36-generic x86_64 .tmp.unity_support_test.0: ApportVersion: 2.20.9-0ubuntu7.4 Architecture: amd64 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: None Date: Fri Nov 2 09:56:43 2018 DistUpgraded: 2018-11-01 23:04:23,218 DEBUG icon theme changed, re-reading DistroCodename: bionic DistroVariant: ubuntu ExtraDebuggingInterest: Yes, including running git bisection searches GraphicsCard: Intel Corporation 2nd Generation Core Processor Family Integrated Graphics Controller [8086:0126] (rev 09) (prog-if 00 [VGA controller]) Subsystem: Lenovo 2nd Generation Core Processor Family Integrated Graphics Controller (ThinkPad T520) [17aa:21cf] InstallationDate: Installed on 2017-09-21 (407 days ago) InstallationMedia: Ubuntu 16.04.3 LTS "Xenial Xerus" - Release amd64 (20170801) MachineType: LENOVO 42424WU ProcEnviron: PATH=(custom, no user) LANG=en_US.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-36-generic root=UUID=4a4b8720-cf83-49dd-b18a-63b77499e529 ro quiet splash vt.handoff=1 SourcePackage: xorg UpgradeStatus: Upgraded to bionic on 2018-11-02 (0 days ago) dmi.bios.date: 11/24/2011 dmi.bios.vendor: LENOVO dmi.bios.version: 8AET55WW (1.35 ) dmi.board.asset.tag: Not Available dmi.board.name: 42424WU dmi.board.vendor: LENOVO dmi.board.version: Not Available dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: Not Available dmi.modalias: dmi:bvnLENOVO:bvr8AET55WW(1.35):bd11/24/2011:svnLENOVO:pn42424WU:pvrThinkPadT520:rvnLENOVO:rn42424WU:rvrNotAvailable:cvnLENOVO:ct10:cvrNotAvailable: dmi.product.family: ThinkPad T520 dmi.product.name: 42424WU dmi.product.version: ThinkPad T520 dmi.sys.vendor: LENOVO version.compiz: compiz 1:0.9.13.1+18.04.20180302-0ubuntu1 version.libdrm2: libdrm2 2.4.91-2 version.libgl1-mesa-dri: libgl1-mesa-dri 18.0.5-0ubuntu0~18.04.1 version.libgl1-mesa-glx: libgl1-mesa-glx 18.0.5-0ubuntu0~18.04.1 version.xserver-xorg-core: xserver-xorg-core 2:1.19.6-1ubuntu4.2 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.10.5-1ubuntu1 version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:18.0.1-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20171229-1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.15-2 xserver.bootTime: Thu Nov 1 10:46:56 2018 xserver.configfile: default xserver.errors: xserver.logfile: /var/log/Xorg.0.log xserver.version: 2:1.19.6-1ubuntu4.1~16.04.2 xserver.video_driver: modeset To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1801410/+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 1801572] Re: package libdrm-nouveau2 2.4.95-1 failed to install/upgrade: trying to overwrite shared '/usr/share/doc/libdrm-nouveau2/changelog.Debian.gz', which is different from
looks like your mirror doesn't provide i386 builds, so use another one if necessary ** Changed in: libdrm (Ubuntu) Status: New => Invalid -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to libdrm in Ubuntu. https://bugs.launchpad.net/bugs/1801572 Title: package libdrm-nouveau2 2.4.95-1 failed to install/upgrade: trying to overwrite shared '/usr/share/doc/libdrm-nouveau2/changelog.Debian.gz', which is different from other instances of package libdrm- nouveau2:i386 Status in libdrm package in Ubuntu: Invalid Bug description: dik@dik-HP-Notebook:~$ sudo apt install youtube-dl [sudo] password for dik: Reading package lists... Done Building dependency tree Reading state information... Done You might want to run 'apt --fix-broken install' to correct these. The following packages have unmet dependencies: libdrm-nouveau2 : Breaks: libdrm-nouveau2:i386 (!= 2.4.95-1) but 2.4.95-1~18.04.1~ppa1 is to be installed libdrm-nouveau2:i386 : Breaks: libdrm-nouveau2 (!= 2.4.95-1~18.04.1~ppa1) but 2.4.95-1 is to be installed E: Unmet dependencies. Try 'apt --fix-broken install' with no packages (or specify a solution). dik@dik-HP-Notebook:~$ apt --fix-broken install E: Could not open lock file /var/lib/dpkg/lock-frontend - open (13: Permission denied) E: Unable to acquire the dpkg frontend lock (/var/lib/dpkg/lock-frontend), are you root? dik@dik-HP-Notebook:~$ sudo apt autoremove Reading package lists... Done Building dependency tree Reading state information... Done You might want to run 'apt --fix-broken install' to correct these. The following packages have unmet dependencies: libdrm-nouveau2 : Breaks: libdrm-nouveau2:i386 (!= 2.4.95-1) but 2.4.95-1~18.04.1~ppa1 is installed libdrm-nouveau2:i386 : Breaks: libdrm-nouveau2 (!= 2.4.95-1~18.04.1~ppa1) but 2.4.95-1 is installed E: Unmet dependencies. Try 'apt --fix-broken install' with no packages (or specify a solution). dik@dik-HP-Notebook:~$ sudo -i root@dik-HP-Notebook:~# apt --fix-broken install Reading package lists... Done Building dependency tree Reading state information... Done Correcting dependencies... Done The following additional packages will be installed: libdrm-nouveau2:i386 The following packages will be upgraded: libdrm-nouveau2:i386 1 upgraded, 0 newly installed, 0 to remove and 0 not upgraded. 2 not fully installed or removed. Need to get 0 B/18.2 kB of archives. After this operation, 0 B of additional disk space will be used. Do you want to continue? [Y/n] y (Reading database ... 131268 files and directories currently installed.) Preparing to unpack .../libdrm-nouveau2_2.4.95-1_i386.deb ... Unpacking libdrm-nouveau2:i386 (2.4.95-1) over (2.4.95-1~18.04.1~ppa1) ... dpkg: error processing archive /var/cache/apt/archives/libdrm-nouveau2_2.4.95-1_i386.deb (--unpack): trying to overwrite shared '/usr/share/doc/libdrm-nouveau2/changelog.Debian.gz', which is different from other instances of package libdrm-nouveau2:i386 Errors were encountered while processing: /var/cache/apt/archives/libdrm-nouveau2_2.4.95-1_i386.deb E: Sub-process /usr/bin/dpkg returned an error code (1) root@dik-HP-Notebook:~# ^C ProblemType: Package DistroRelease: Ubuntu 18.10 Package: libdrm-nouveau2 2.4.95-1 ProcVersionSignature: Ubuntu 4.18.0-10.11-generic 4.18.12 Uname: Linux 4.18.0-10-generic x86_64 ApportVersion: 2.20.10-0ubuntu13 Architecture: amd64 CompositorRunning: None Date: Sun Nov 4 12:18:49 2018 DistUpgraded: Fresh install DistroCodename: cosmic DistroVariant: ubuntu DpkgTerminalLog: Preparing to unpack .../0-libdrm-nouveau2_2.4.95-1_i386.deb ... Unpacking libdrm-nouveau2:i386 (2.4.95-1) over (2.4.95-1~18.04.1~ppa1) ... [1mdpkg:[0m error processing archive /tmp/apt-dpkg-install-rK5YA4/0-libdrm-nouveau2_2.4.95-1_i386.deb (--unpack): trying to overwrite shared '/usr/share/doc/libdrm-nouveau2/changelog.Debian.gz', which is different from other instances of package libdrm-nouveau2:i386 ErrorMessage: trying to overwrite shared '/usr/share/doc/libdrm-nouveau2/changelog.Debian.gz', which is different from other instances of package libdrm-nouveau2:i386 GraphicsCard: Intel Corporation Skylake GT2 [HD Graphics 520] [8086:1916] (rev 07) (prog-if 00 [VGA controller]) Subsystem: Hewlett-Packard Company Skylake GT2 [HD Graphics 520] [103c:81ec] Subsystem: Hewlett-Packard Company Sun XT [Radeon HD 8670A/8670M/8690M / R5 M330 / M430 / R7 M520] [103c:81ec] InstallationDate: Installed on 2018-11-03 (0 days ago) InstallationMedia: Ubuntu 18.10 "Cosmic Cuttlefish" - Release amd64 (20181017.3) Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 003: ID 064e:c346 Suyin Corp. Bus 001 Device 002: ID 0bda:b008 Realtek Semiconductor Corp. Bus 001 Device 001:
