[Touch-packages] [Bug 1701162] Re: package mount 2.29-1ubuntu2.1 failed to install/upgrade: package mount is not ready for configuration cannot configure (current status 'half-installed')
...and resolved on my system. Searched again recently for the error. Found a recommendation to try sudo apt install mount --reinstall Look at what I had tried before as noted in initial bug report. Did not try this. mount was successfully reinstalled followed by me updating the 215 packages that were pending update since this problem began. Have now successfully updated packages twice since performing this fix. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to util-linux in Ubuntu. https://bugs.launchpad.net/bugs/1701162 Title: package mount 2.29-1ubuntu2.1 failed to install/upgrade: package mount is not ready for configuration cannot configure (current status 'half-installed') Status in dpkg package in Ubuntu: New Status in util-linux package in Ubuntu: Confirmed Bug description: sudo apt upgrade fails. Output is as follows... Reading package lists... Done Building dependency tree Reading state information... Done Calculating upgrade... Done 0 upgraded, 0 newly installed, 0 to remove and 0 not upgraded. 1 not fully installed or removed. Need to get 0 B/130 kB of archives. After this operation, 0 B of additional disk space will be used. Do you want to continue? [Y/n] y dpkg: error processing package mount (--configure): package mount is not ready for configuration cannot configure (current status 'half-installed') Errors were encountered while processing: mount E: Sub-process /usr/bin/dpkg returned an error code (1) I've combed the web for a solution and tried all of the following. None of which have resolved the issue... sudo apt-get install -f sudo apt-get install --fix-broken --fix-missing sudo apt-get -f install sudo apt-get update –fix-missing sudo apt-get autoremove sudo apt-get -u dist-upgrade sudo apt --reinstall mount sudo dpkg –configure -a sudo dpkg -r -a ProblemType: Package DistroRelease: Ubuntu 17.04 Package: mount 2.29-1ubuntu2.1 ProcVersionSignature: Ubuntu 4.10.0-24.28-generic 4.10.15 Uname: Linux 4.10.0-24-generic x86_64 ApportVersion: 2.20.4-0ubuntu4.1 AptOrdering: mount:amd64: Configure NULL: ConfigurePending Architecture: amd64 Date: Thu Jun 29 00:16:17 2017 DpkgTerminalLog: dpkg: error processing package mount (--configure): package mount is not ready for configuration cannot configure (current status 'half-installed') ErrorMessage: package mount is not ready for configuration cannot configure (current status 'half-installed') InstallationDate: Installed on 2016-09-02 (300 days ago) InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 (20160420.1) RelatedPackageVersions: dpkg 1.18.10ubuntu2 apt 1.4 SourcePackage: util-linux Title: package mount 2.29-1ubuntu2.1 failed to install/upgrade: package mount is not ready for configuration cannot configure (current status 'half-installed') UpgradeStatus: Upgraded to zesty on 2017-05-20 (39 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/dpkg/+bug/1701162/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1675969] [NEW] various code running
Public bug reported: WHen I boot into Ubuntu 16.04 a ton of code runs prior to login. Ran repair broken packages from the grub loader systems utilites. Hope this makes sence to you. ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: xorg 1:7.7+13ubuntu3 ProcVersionSignature: Ubuntu 4.4.0-66.87-generic 4.4.44 Uname: Linux 4.4.0-66-generic i686 .tmp.unity_support_test.0: ApportVersion: 2.20.1-0ubuntu2.5 Architecture: i386 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: compiz CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0' CompositorUnredirectFSW: true Date: Fri Mar 24 18:04:45 2017 DistUpgraded: Fresh install DistroCodename: xenial DistroVariant: ubuntu ExtraDebuggingInterest: Yes GraphicsCard: Advanced Micro Devices, Inc. [AMD/ATI] Curacao XT [Radeon R7 370 / R9 270X/370 OEM] [1002:6810] (prog-if 00 [VGA controller]) Subsystem: PC Partner Limited / Sapphire Technology Curacao XT [Radeon R7 370 / R9 270X/370 OEM] [174b:e271] InstallationDate: Installed on 2017-03-18 (6 days ago) InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release i386 (20160420.1) MachineType: System manufacturer System Product Name ProcEnviron: LANGUAGE=en_US PATH=(custom, no user) LANG=en_US.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-66-generic root=UUID=b04480a8-c7ce-4bfc-8265-4ab6b0bfa64c ro drm.debug=0xe plymouth:debug SourcePackage: xorg UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 11/14/2012 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 1302 dmi.board.asset.tag: To Be Filled By O.E.M. dmi.board.name: M5A78L-M LX PLUS dmi.board.vendor: ASUSTeK Computer INC. dmi.board.version: Rev X.0x dmi.chassis.asset.tag: Asset-1234567890 dmi.chassis.type: 3 dmi.chassis.vendor: Chassis Manufacture dmi.chassis.version: Chassis Version dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr1302:bd11/14/2012:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKComputerINC.:rnM5A78L-MLXPLUS:rvrRevX.0x:cvnChassisManufacture:ct3:cvrChassisVersion: dmi.product.name: System Product Name dmi.product.version: System Version dmi.sys.vendor: System manufacturer version.compiz: compiz 1:0.9.12.2+16.04.20160823-0ubuntu1 version.libdrm2: libdrm2 2.4.70-1~ubuntu16.04.1 version.libgl1-mesa-dri: libgl1-mesa-dri 12.0.6-0ubuntu0.16.04.1 version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A version.libgl1-mesa-glx: libgl1-mesa-glx 12.0.6-0ubuntu0.16.04.1 version.xserver-xorg-core: xserver-xorg-core 2:1.18.4-0ubuntu0.2 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.10.1-1ubuntu2 version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.7.0-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20160325-1ubuntu1.2 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.12-1build2 xserver.bootTime: Fri Mar 24 16:45:12 2017 xserver.configfile: default xserver.devices: inputPower Button KEYBOARD, id 6 inputPower Button KEYBOARD, id 7 inputLogitech USB Optical Mouse MOUSE, id 8 inputMicrosoft Microsoft® SiderWinderTM X6 Keyboard KEYBOARD, id 9 inputMicrosoft Microsoft® SiderWinderTM X6 Keyboard KEYBOARD, id 10 xserver.errors: xserver.logfile: /var/log/Xorg.0.log xserver.version: 2:1.18.4-0ubuntu0.2 xserver.video_driver: radeon ** Affects: xorg (Ubuntu) Importance: Undecided Status: New ** Tags: apport-bug compiz-0.9 i386 ubuntu xenial -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to xorg in Ubuntu. https://bugs.launchpad.net/bugs/1675969 Title: various code running Status in xorg package in Ubuntu: New Bug description: WHen I boot into Ubuntu 16.04 a ton of code runs prior to login. Ran repair broken packages from the grub loader systems utilites. Hope this makes sence to you. ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: xorg 1:7.7+13ubuntu3 ProcVersionSignature: Ubuntu 4.4.0-66.87-generic 4.4.44 Uname: Linux 4.4.0-66-generic i686 .tmp.unity_support_test.0: ApportVersion: 2.20.1-0ubuntu2.5 Architecture: i386 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: compiz CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0' CompositorUnredirectFSW: true Date: Fri Mar 24 18:04:45 2017 DistUpgraded: Fresh install DistroCodename: xenial DistroVariant: ubuntu ExtraDebuggingInterest: Yes GraphicsCard: Advanced Micro Devices, Inc. [AMD/ATI] Curacao XT [Radeon R7 370 / R9 270X/370 OEM] [1002:6810] (prog-if 00 [VGA controller]) Subsystem: PC Partner Limited / Sapphire Technology Curacao XT [Radeon R7 370 / R9 270X/370 OEM] [174b:e271] InstallationDate: Installed on 2017-03-18 (6 days ago) InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Relea
[Touch-packages] [Bug 1675970] [NEW] various code running
Public bug reported: WHen I boot into Ubuntu 16.04 a ton of code runs prior to login. Ran repair broken packages from the grub loader systems utilites. Hope this makes sence to you. ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: xorg 1:7.7+13ubuntu3 ProcVersionSignature: Ubuntu 4.4.0-66.87-generic 4.4.44 Uname: Linux 4.4.0-66-generic i686 .tmp.unity_support_test.0: ApportVersion: 2.20.1-0ubuntu2.5 Architecture: i386 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: compiz CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0' CompositorUnredirectFSW: true Date: Fri Mar 24 18:04:45 2017 DistUpgraded: Fresh install DistroCodename: xenial DistroVariant: ubuntu ExtraDebuggingInterest: Yes GraphicsCard: Advanced Micro Devices, Inc. [AMD/ATI] Curacao XT [Radeon R7 370 / R9 270X/370 OEM] [1002:6810] (prog-if 00 [VGA controller]) Subsystem: PC Partner Limited / Sapphire Technology Curacao XT [Radeon R7 370 / R9 270X/370 OEM] [174b:e271] InstallationDate: Installed on 2017-03-18 (6 days ago) InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release i386 (20160420.1) MachineType: System manufacturer System Product Name ProcEnviron: LANGUAGE=en_US PATH=(custom, no user) LANG=en_US.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-66-generic root=UUID=b04480a8-c7ce-4bfc-8265-4ab6b0bfa64c ro drm.debug=0xe plymouth:debug SourcePackage: xorg UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 11/14/2012 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 1302 dmi.board.asset.tag: To Be Filled By O.E.M. dmi.board.name: M5A78L-M LX PLUS dmi.board.vendor: ASUSTeK Computer INC. dmi.board.version: Rev X.0x dmi.chassis.asset.tag: Asset-1234567890 dmi.chassis.type: 3 dmi.chassis.vendor: Chassis Manufacture dmi.chassis.version: Chassis Version dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr1302:bd11/14/2012:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKComputerINC.:rnM5A78L-MLXPLUS:rvrRevX.0x:cvnChassisManufacture:ct3:cvrChassisVersion: dmi.product.name: System Product Name dmi.product.version: System Version dmi.sys.vendor: System manufacturer version.compiz: compiz 1:0.9.12.2+16.04.20160823-0ubuntu1 version.libdrm2: libdrm2 2.4.70-1~ubuntu16.04.1 version.libgl1-mesa-dri: libgl1-mesa-dri 12.0.6-0ubuntu0.16.04.1 version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A version.libgl1-mesa-glx: libgl1-mesa-glx 12.0.6-0ubuntu0.16.04.1 version.xserver-xorg-core: xserver-xorg-core 2:1.18.4-0ubuntu0.2 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.10.1-1ubuntu2 version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.7.0-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20160325-1ubuntu1.2 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.12-1build2 xserver.bootTime: Fri Mar 24 16:45:12 2017 xserver.configfile: default xserver.devices: inputPower Button KEYBOARD, id 6 inputPower Button KEYBOARD, id 7 inputLogitech USB Optical Mouse MOUSE, id 8 inputMicrosoft Microsoft® SiderWinderTM X6 Keyboard KEYBOARD, id 9 inputMicrosoft Microsoft® SiderWinderTM X6 Keyboard KEYBOARD, id 10 xserver.errors: xserver.logfile: /var/log/Xorg.0.log xserver.version: 2:1.18.4-0ubuntu0.2 xserver.video_driver: radeon ** Affects: xorg (Ubuntu) Importance: Undecided Status: New ** Tags: apport-bug compiz-0.9 i386 ubuntu xenial -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to xorg in Ubuntu. https://bugs.launchpad.net/bugs/1675970 Title: various code running Status in xorg package in Ubuntu: New Bug description: WHen I boot into Ubuntu 16.04 a ton of code runs prior to login. Ran repair broken packages from the grub loader systems utilites. Hope this makes sence to you. ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: xorg 1:7.7+13ubuntu3 ProcVersionSignature: Ubuntu 4.4.0-66.87-generic 4.4.44 Uname: Linux 4.4.0-66-generic i686 .tmp.unity_support_test.0: ApportVersion: 2.20.1-0ubuntu2.5 Architecture: i386 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: compiz CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0' CompositorUnredirectFSW: true Date: Fri Mar 24 18:04:45 2017 DistUpgraded: Fresh install DistroCodename: xenial DistroVariant: ubuntu ExtraDebuggingInterest: Yes GraphicsCard: Advanced Micro Devices, Inc. [AMD/ATI] Curacao XT [Radeon R7 370 / R9 270X/370 OEM] [1002:6810] (prog-if 00 [VGA controller]) Subsystem: PC Partner Limited / Sapphire Technology Curacao XT [Radeon R7 370 / R9 270X/370 OEM] [174b:e271] InstallationDate: Installed on 2017-03-18 (6 days ago) InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Relea
[Touch-packages] [Bug 1720126]
I can confirm it now works with 112 VF. This is the most my hardware will support. Thanks, Alan -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to iproute2 in Ubuntu. https://bugs.launchpad.net/bugs/1720126 Title: [ip link] Message truncated error for large number of passthrough VFs Status in iproute2 package in Ubuntu: Fix Released Status in iproute2 source package in Trusty: Fix Committed Status in iproute2 source package in Xenial: Fix Released Status in iproute2 source package in Zesty: Fix Released Status in iproute2 package in CentOS: Fix Committed Bug description: [Impact] When querying a Physical Function netdev with a large amount of VF's (more than 30), the resulting return message can overflow the 16K netlink message buffer. This can be fixed by enabling message peeking on the socket and resizing the buffer on receive, or by simply enlarging the receive buffer. Since there's an upper limit to the number of VF's per PF, it's relatively sane to just enlarge the receive buffer. Please see the attached patch. [Test Case] # Set up 60 VF's on an SR-IOV device ip link show > /dev/null Observe the following: Message truncated Message truncated Message truncated [Regression Potential] 1) Applications relying on the broken behaviour will need to be updated, but it would be a really dubious use case. 2) Increasing the rx buffer size increases the memory footprint (but realistically, this is tiny). 3) Extra processing time is now needed to parse the larger buffer, in the case that a call to "ip link" is on the critical time path of an application, (called multiple times in a tight loop, for example), it would affect load. [Other Info] Observed on Ubuntu kernel 4.4.0-93-generic on both 14.04 and 16.04 = Ubuntu16 system stack@cluster04:~$ lsb_release -a No LSB modules are available. Distributor ID: Ubuntu Description: Ubuntu 16.04.3 LTS Release: 16.04 Codename: xenial stack@cluster04:~$ uname -r 4.4.0-93-generic stack@cluster04:~$ apt-cache policy iproute2 iproute2: Installed: 4.3.0-1ubuntu3.16.04.1 Version table: *** 4.3.0-1ubuntu3.16.04.1 500 500 http://us.archive.ubuntu.com/ubuntu xenial-updates/main amd64 Packages = Ubuntu14 system: root@boomslang:~# lsb_release -a No LSB modules are available. Distributor ID: Ubuntu Description: Ubuntu 14.04.3 LTS Release: 14.04 Codename: trusty root@boomslang:~# uname -r 4.4.0-96-generic root@boomslang:~# apt-cache policy iproute2 iproute2: Installed: 3.12.0-2ubuntu1 Version table: *** 3.12.0-2ubuntu1 0 500 http://za.archive.ubuntu.com/ubuntu/ trusty-updates/main amd64 Packages To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/iproute2/+bug/1720126/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1701162] [NEW] package mount 2.29-1ubuntu2.1 failed to install/upgrade: package mount is not ready for configuration cannot configure (current status 'half-installed')
Public bug reported: sudo apt upgrade fails. Output is as follows... Reading package lists... Done Building dependency tree Reading state information... Done Calculating upgrade... Done 0 upgraded, 0 newly installed, 0 to remove and 0 not upgraded. 1 not fully installed or removed. Need to get 0 B/130 kB of archives. After this operation, 0 B of additional disk space will be used. Do you want to continue? [Y/n] y dpkg: error processing package mount (--configure): package mount is not ready for configuration cannot configure (current status 'half-installed') Errors were encountered while processing: mount E: Sub-process /usr/bin/dpkg returned an error code (1) I've combed the web for a solution and tried all of the following. None of which have resolved the issue... sudo apt-get install -f sudo apt-get install --fix-broken --fix-missing sudo apt-get -f install sudo apt-get update –fix-missing sudo apt-get autoremove sudo apt-get -u dist-upgrade sudo apt --reinstall mount sudo dpkg –configure -a sudo dpkg -r -a ProblemType: Package DistroRelease: Ubuntu 17.04 Package: mount 2.29-1ubuntu2.1 ProcVersionSignature: Ubuntu 4.10.0-24.28-generic 4.10.15 Uname: Linux 4.10.0-24-generic x86_64 ApportVersion: 2.20.4-0ubuntu4.1 AptOrdering: mount:amd64: Configure NULL: ConfigurePending Architecture: amd64 Date: Thu Jun 29 00:16:17 2017 DpkgTerminalLog: dpkg: error processing package mount (--configure): package mount is not ready for configuration cannot configure (current status 'half-installed') ErrorMessage: package mount is not ready for configuration cannot configure (current status 'half-installed') InstallationDate: Installed on 2016-09-02 (300 days ago) InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 (20160420.1) RelatedPackageVersions: dpkg 1.18.10ubuntu2 apt 1.4 SourcePackage: util-linux Title: package mount 2.29-1ubuntu2.1 failed to install/upgrade: package mount is not ready for configuration cannot configure (current status 'half-installed') UpgradeStatus: Upgraded to zesty on 2017-05-20 (39 days ago) ** Affects: util-linux (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-package zesty -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to util-linux in Ubuntu. https://bugs.launchpad.net/bugs/1701162 Title: package mount 2.29-1ubuntu2.1 failed to install/upgrade: package mount is not ready for configuration cannot configure (current status 'half-installed') Status in util-linux package in Ubuntu: New Bug description: sudo apt upgrade fails. Output is as follows... Reading package lists... Done Building dependency tree Reading state information... Done Calculating upgrade... Done 0 upgraded, 0 newly installed, 0 to remove and 0 not upgraded. 1 not fully installed or removed. Need to get 0 B/130 kB of archives. After this operation, 0 B of additional disk space will be used. Do you want to continue? [Y/n] y dpkg: error processing package mount (--configure): package mount is not ready for configuration cannot configure (current status 'half-installed') Errors were encountered while processing: mount E: Sub-process /usr/bin/dpkg returned an error code (1) I've combed the web for a solution and tried all of the following. None of which have resolved the issue... sudo apt-get install -f sudo apt-get install --fix-broken --fix-missing sudo apt-get -f install sudo apt-get update –fix-missing sudo apt-get autoremove sudo apt-get -u dist-upgrade sudo apt --reinstall mount sudo dpkg –configure -a sudo dpkg -r -a ProblemType: Package DistroRelease: Ubuntu 17.04 Package: mount 2.29-1ubuntu2.1 ProcVersionSignature: Ubuntu 4.10.0-24.28-generic 4.10.15 Uname: Linux 4.10.0-24-generic x86_64 ApportVersion: 2.20.4-0ubuntu4.1 AptOrdering: mount:amd64: Configure NULL: ConfigurePending Architecture: amd64 Date: Thu Jun 29 00:16:17 2017 DpkgTerminalLog: dpkg: error processing package mount (--configure): package mount is not ready for configuration cannot configure (current status 'half-installed') ErrorMessage: package mount is not ready for configuration cannot configure (current status 'half-installed') InstallationDate: Installed on 2016-09-02 (300 days ago) InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 (20160420.1) RelatedPackageVersions: dpkg 1.18.10ubuntu2 apt 1.4 SourcePackage: util-linux Title: package mount 2.29-1ubuntu2.1 failed to install/upgrade: package mount is not ready for configuration cannot configure (current status 'half-installed') UpgradeStatus: Upgraded to zesty on 2017-05-20 (39 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/util-linux/+bug/1701162/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-pack
[Touch-packages] [Bug 1557261] [NEW] package binutils 2.25.1-6ubuntu1 failed to install/upgrade: package binutils is not ready for configuration cannot configure (current status 'half-installed')
Public bug reported: apt-get update on Live USB Ubuntu 15.10 ProblemType: Package DistroRelease: Ubuntu 15.10 Package: binutils 2.25.1-6ubuntu1 ProcVersionSignature: Ubuntu 4.2.0-16.19-generic 4.2.3 Uname: Linux 4.2.0-16-generic x86_64 ApportVersion: 2.19.1-0ubuntu3 Architecture: amd64 CasperVersion: 1.365 Date: Mon Mar 14 17:34:38 2016 Dependencies: gcc-5-base 5.2.1-22ubuntu2 libc6 2.21-0ubuntu4.1 libgcc1 1:5.2.1-22ubuntu2 zlib1g 1:1.2.8.dfsg-2ubuntu4 DuplicateSignature: package:binutils:2.25.1-6ubuntu1:package binutils is not ready for configuration cannot configure (current status 'half-installed') ErrorMessage: package binutils is not ready for configuration cannot configure (current status 'half-installed') LiveMediaBuild: Ubuntu 15.10 "Wily Werewolf" - Release amd64 (20151021) RelatedPackageVersions: dpkg 1.18.2ubuntu5.1 apt 1.0.10.2ubuntu1 SourcePackage: binutils Title: package binutils 2.25.1-6ubuntu1 failed to install/upgrade: package binutils is not ready for configuration cannot configure (current status 'half-installed') UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: binutils (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-package wily -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to binutils in Ubuntu. https://bugs.launchpad.net/bugs/1557261 Title: package binutils 2.25.1-6ubuntu1 failed to install/upgrade: package binutils is not ready for configuration cannot configure (current status 'half-installed') Status in binutils package in Ubuntu: New Bug description: apt-get update on Live USB Ubuntu 15.10 ProblemType: Package DistroRelease: Ubuntu 15.10 Package: binutils 2.25.1-6ubuntu1 ProcVersionSignature: Ubuntu 4.2.0-16.19-generic 4.2.3 Uname: Linux 4.2.0-16-generic x86_64 ApportVersion: 2.19.1-0ubuntu3 Architecture: amd64 CasperVersion: 1.365 Date: Mon Mar 14 17:34:38 2016 Dependencies: gcc-5-base 5.2.1-22ubuntu2 libc6 2.21-0ubuntu4.1 libgcc1 1:5.2.1-22ubuntu2 zlib1g 1:1.2.8.dfsg-2ubuntu4 DuplicateSignature: package:binutils:2.25.1-6ubuntu1:package binutils is not ready for configuration cannot configure (current status 'half-installed') ErrorMessage: package binutils is not ready for configuration cannot configure (current status 'half-installed') LiveMediaBuild: Ubuntu 15.10 "Wily Werewolf" - Release amd64 (20151021) RelatedPackageVersions: dpkg 1.18.2ubuntu5.1 apt 1.0.10.2ubuntu1 SourcePackage: binutils Title: package binutils 2.25.1-6ubuntu1 failed to install/upgrade: package binutils is not ready for configuration cannot configure (current status 'half-installed') UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/binutils/+bug/1557261/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1568084] [NEW] package unity-control-center-signon 0.1.7~+14.10.20140814-0ubuntu1 failed to install/upgrade: package is in a very bad inconsistent state; you should reinstall it
Public bug reported: i'm from Poland and I can't say English... Sorry! ProblemType: Package DistroRelease: Ubuntu 15.04 Package: unity-control-center-signon 0.1.7~+14.10.20140814-0ubuntu1 ProcVersionSignature: Ubuntu 3.19.0-56.62-generic 3.19.8-ckt15 Uname: Linux 3.19.0-56-generic i686 ApportVersion: 2.17.2-0ubuntu1.8 AptOrdering: flashplugin-installer: Install unity-control-center-signon: Configure flashplugin-installer: Configure NULL: ConfigurePending Architecture: i386 Date: Wed Apr 6 14:48:53 2016 DpkgHistoryLog: Start-Date: 2016-04-06 14:48:16 Commandline: aptdaemon role='role-install-packages' sender=':1.35' Install: flashplugin-installer:i386 (11.2.202.559ubuntu0.15.04.1) DuplicateSignature: package:unity-control-center-signon:0.1.7~+14.10.20140814-0ubuntu1:package is in a very bad inconsistent state; you should reinstall it before attempting configuration ErrorMessage: package is in a very bad inconsistent state; you should reinstall it before attempting configuration InstallationDate: Installed on 2016-03-09 (30 days ago) InstallationMedia: It RelatedPackageVersions: dpkg 1.17.25ubuntu1.1 apt 1.0.9.7ubuntu4.2 SourcePackage: gnome-control-center-signon Title: package unity-control-center-signon 0.1.7~+14.10.20140814-0ubuntu1 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: gnome-control-center-signon (Ubuntu) Importance: Undecided Status: New ** Tags: apport-package i386 vivid -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to gnome-control-center- signon in Ubuntu. https://bugs.launchpad.net/bugs/1568084 Title: package unity-control-center-signon 0.1.7~+14.10.20140814-0ubuntu1 failed to install/upgrade: package is in a very bad inconsistent state; you should reinstall it before attempting configuration Status in gnome-control-center-signon package in Ubuntu: New Bug description: i'm from Poland and I can't say English... Sorry! ProblemType: Package DistroRelease: Ubuntu 15.04 Package: unity-control-center-signon 0.1.7~+14.10.20140814-0ubuntu1 ProcVersionSignature: Ubuntu 3.19.0-56.62-generic 3.19.8-ckt15 Uname: Linux 3.19.0-56-generic i686 ApportVersion: 2.17.2-0ubuntu1.8 AptOrdering: flashplugin-installer: Install unity-control-center-signon: Configure flashplugin-installer: Configure NULL: ConfigurePending Architecture: i386 Date: Wed Apr 6 14:48:53 2016 DpkgHistoryLog: Start-Date: 2016-04-06 14:48:16 Commandline: aptdaemon role='role-install-packages' sender=':1.35' Install: flashplugin-installer:i386 (11.2.202.559ubuntu0.15.04.1) DuplicateSignature: package:unity-control-center-signon:0.1.7~+14.10.20140814-0ubuntu1:package is in a very bad inconsistent state; you should reinstall it before attempting configuration ErrorMessage: package is in a very bad inconsistent state; you should reinstall it before attempting configuration InstallationDate: Installed on 2016-03-09 (30 days ago) InstallationMedia: It RelatedPackageVersions: dpkg 1.17.25ubuntu1.1 apt 1.0.9.7ubuntu4.2 SourcePackage: gnome-control-center-signon Title: package unity-control-center-signon 0.1.7~+14.10.20140814-0ubuntu1 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/gnome-control-center-signon/+bug/1568084/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1967009] Re: Missing support for Georgian uppercase characters
The problem still persist in Ubuntu 22.04. Should I file a new issue? ** Attachment added: "ubuntu_22.04_missing_glyphs." https://bugs.launchpad.net/ubuntu/+source/fonts-dejavu/+bug/1967009/+attachment/5594565/+files/ubuntu_22.04..png -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to fonts-dejavu in Ubuntu. https://bugs.launchpad.net/bugs/1967009 Title: Missing support for Georgian uppercase characters Status in fonts-dejavu package in Ubuntu: Incomplete Bug description: Georgian uppercase letters are encoded in Unicode 11 (2018), but there are no fonts in Ubuntu that can display these characters. Version info: Ubuntu 21.04 To reproduce: 1. add Georgian keyboard layout 2. open any text editor 3. type Georgian letters, then change them to uppercase Expected: Readable text Actual result: Shows squares Some other Linux distributions switched to Google-Noto-Georgian, which covers all Georgian characters. Can it be used in Ubuntu too? To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/fonts-dejavu/+bug/1967009/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1967009] Re: Missing support for Georgian uppercase characters
** Package changed: ubuntu => fonts-dejavu (Ubuntu) -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to fonts-dejavu in Ubuntu. https://bugs.launchpad.net/bugs/1967009 Title: Missing support for Georgian uppercase characters Status in fonts-dejavu package in Ubuntu: New Bug description: Georgian uppercase letters are encoded in Unicode 11 (2018), but there are no fonts in Ubuntu that can display these characters. Version info: Ubuntu 21.04 To reproduce: 1. add Georgian keyboard layout 2. open any text editor 3. type Georgian letters, then change them to uppercase Expected: Readable text Actual result: Shows squares Some other Linux distributions switched to Google-Noto-Georgian, which covers all Georgian characters. Can it be used in Ubuntu too? To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/fonts-dejavu/+bug/1967009/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1967009] Re: Missing support for Georgian uppercase characters
It's the same situation with Ubuntu 21.10, see attached screenshot. ** Attachment added: "ubuntu_21.10_missing_glyphs.png" https://bugs.launchpad.net/ubuntu/+source/fonts-dejavu/+bug/1967009/+attachment/5574505/+files/ubuntu_21.10_missing_glyphs.png -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to fonts-dejavu in Ubuntu. https://bugs.launchpad.net/bugs/1967009 Title: Missing support for Georgian uppercase characters Status in fonts-dejavu package in Ubuntu: Incomplete Bug description: Georgian uppercase letters are encoded in Unicode 11 (2018), but there are no fonts in Ubuntu that can display these characters. Version info: Ubuntu 21.04 To reproduce: 1. add Georgian keyboard layout 2. open any text editor 3. type Georgian letters, then change them to uppercase Expected: Readable text Actual result: Shows squares Some other Linux distributions switched to Google-Noto-Georgian, which covers all Georgian characters. Can it be used in Ubuntu too? To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/fonts-dejavu/+bug/1967009/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1967009] Re: Missing support for Georgian uppercase characters
Any updates? It's planned to re-enable CSS uppercasing for Georgian -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to fonts-dejavu in Ubuntu. https://bugs.launchpad.net/bugs/1967009 Title: Missing support for Georgian uppercase characters Status in fonts-dejavu package in Ubuntu: Incomplete Bug description: Georgian uppercase letters are encoded in Unicode 11 (2018), but there are no fonts in Ubuntu that can display these characters. Version info: Ubuntu 21.04 To reproduce: 1. add Georgian keyboard layout 2. open any text editor 3. type Georgian letters, then change them to uppercase Expected: Readable text Actual result: Shows squares Some other Linux distributions switched to Google-Noto-Georgian, which covers all Georgian characters. Can it be used in Ubuntu too? To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/fonts-dejavu/+bug/1967009/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1357785] Re: apportcheckresume crashed with FileExistsError in main(): [Errno 17] File exists: '/var/crash/susres.2014-08-16_17:12:29.520047.crash'
Unity 7.3.1 -- 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/1357785 Title: apportcheckresume crashed with FileExistsError in main(): [Errno 17] File exists: '/var/crash/susres.2014-08-16_17:12:29.520047.crash' Status in “apport” package in Ubuntu: Confirmed Bug description: Crash in the init after desktop load. ProblemType: Crash DistroRelease: Ubuntu 14.10 Package: apport 2.14.5-0ubuntu4 ProcVersionSignature: Ubuntu 3.16.0-8.13-generic 3.16.0 Uname: Linux 3.16.0-8-generic i686 ApportLog: ApportVersion: 2.14.5-0ubuntu4 Architecture: i386 CrashReports: 640:0:116:9127:2014-08-16 17:12:28.520163536 -0300:2014-08-16 17:12:29.520163536 -0300:/var/crash/_usr_share_apport_apportcheckresume.0.crash 664:1000:116:0:2014-08-10 23:33:36.996171976 -0300:2014-08-10 23:33:36.996171976 -0300:/var/crash/_usr_bin_file-roller.1000.upload 640:0:116:121022:2014-08-16 17:12:29.516163613 -0300:2014-08-16 17:12:29.516163613 -0300:/var/crash/susres.2014-08-16_17:12:29.520047.crash 640:1000:116:2031262:2014-08-10 23:33:24.024112701 -0300:2014-08-10 23:33:25.024112701 -0300:/var/crash/_usr_bin_file-roller.1000.crash 600:109:116:0:2014-08-10 23:33:56.396268178 -0300:2014-08-10 23:33:56.396268178 -0300:/var/crash/_usr_bin_file-roller.1000.uploaded Date: Sat Aug 16 17:12:29 2014 ExecutablePath: /usr/share/apport/apportcheckresume InstallationDate: Installed on 2014-05-03 (105 days ago) InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Release i386 (20140417) InterpreterPath: /usr/bin/python3.4 PackageArchitecture: all ProcCmdline: /usr/bin/python3 /usr/share/apport/apportcheckresume ProcEnviron: TERM=linux PATH=(custom, no user) PythonArgs: ['/usr/share/apport/apportcheckresume'] SourcePackage: apport Title: apportcheckresume crashed with FileExistsError in main(): [Errno 17] File exists: '/var/crash/susres.2014-08-16_17:12:29.520047.crash' UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apport/+bug/1357785/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1385010] [NEW] unexpected behavior: make_resolv_conf not undefined
Public bug reported: The resolvconf package comes with /etc/dhcp/dhclient-enter- hooks.d/resolvconf which convieniently undefines make_resolve_conf (previously defined by dhclient-script) and calls resolvconf. However, the hook checks if /etc/resolv.conf is a symlink even though /sbin/resolvconf already handles this. This is problematic because it never undefines the make_resolv_conf function which dhclient-script defines itself. For me, the expect behavior would be /etc/resolv.conf never changing if resolvconf is installed and the file is not a symlink. At the very least, I think this behavior should be documented in the man pages for resolvconf. Furthermore, debian does not implement this patch and it exists starting in 12.04 until current. As far as I can tell, there's absolutely no reason to check it twice if resolvconf already implements it. It was introduced by: http://bazaar.launchpad.net/~ubuntu- branches/ubuntu/trusty/resolvconf/trusty/revision/32/etc/dhcp/dhclient- enter-hooks.d/resolvconf ** Affects: resolvconf (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to resolvconf in Ubuntu. https://bugs.launchpad.net/bugs/1385010 Title: unexpected behavior: make_resolv_conf not undefined Status in “resolvconf” package in Ubuntu: New Bug description: The resolvconf package comes with /etc/dhcp/dhclient-enter- hooks.d/resolvconf which convieniently undefines make_resolve_conf (previously defined by dhclient-script) and calls resolvconf. However, the hook checks if /etc/resolv.conf is a symlink even though /sbin/resolvconf already handles this. This is problematic because it never undefines the make_resolv_conf function which dhclient-script defines itself. For me, the expect behavior would be /etc/resolv.conf never changing if resolvconf is installed and the file is not a symlink. At the very least, I think this behavior should be documented in the man pages for resolvconf. Furthermore, debian does not implement this patch and it exists starting in 12.04 until current. As far as I can tell, there's absolutely no reason to check it twice if resolvconf already implements it. It was introduced by: http://bazaar.launchpad.net/~ubuntu- branches/ubuntu/trusty/resolvconf/trusty/revision/32/etc/dhcp /dhclient-enter-hooks.d/resolvconf To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/resolvconf/+bug/1385010/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1385010] Re: Unexpected behavior: make_resolv_conf is not undefined if /etc/resolv.conf is not a symlink
Thanks @jdthood ! I figured there could be some arcane reason why the symlink check would be there on Ubuntu but not Debian, but I couldn't fathom why after reading through the entire hook. Also, thanks for cleaning up the report! :D -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to resolvconf in Ubuntu. https://bugs.launchpad.net/bugs/1385010 Title: Unexpected behavior: make_resolv_conf is not undefined if /etc/resolv.conf is not a symlink Status in “resolvconf” package in Ubuntu: New Bug description: The resolvconf package comes with /etc/dhcp/dhclient-enter- hooks.d/resolvconf which, if /sbin/resolvconf is present, redefines the make_resolv_conf function (previously defined by dhclient-script) to send nameserver information to resolvconf instead of writing it directly to /etc/resolv.conf. However, the hook also checks if /etc/resolv.conf is a symlink. This is problematic because if /etc/resolv.conf is not a symlink then the script does not redefine make_resolv_conf() and so dhclient will overwrite /etc/resolv.conf when it configures an interface, even though the resolvconf package is installed. The behavior I would expect would be /etc/resolv.conf never changing if resolvconf is installed and /etc/resolv.conf is not a symlink. Debian implements the behavior I would expect. At the very least, I think that the different behavior in Ubuntu should be documented in the man pages for resolvconf. As far as I can tell, there's no reason to check for /etc/resolv.conf being a symlink when resolvconf itself already does that. The patch was introduced by: http://bazaar.launchpad.net/~ubuntu- branches/ubuntu/trusty/resolvconf/trusty/revision/32/etc/dhcp /dhclient-enter-hooks.d/resolvconf To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/resolvconf/+bug/1385010/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1412719] Re: wait-for-state restarts whoopsie every 30sec
Tail of dmesg.. [ 4517.664355] init: wait-for-state (whoopsienetwork-manager) main process (7481) terminated with status 100 [ 4517.720627] init: whoopsie main process (7492) terminated with status 1 [ 4517.720645] init: whoopsie main process ended, respawning ** Attachment added: "full dmesg" https://bugs.launchpad.net/hundredpapercuts/+bug/1412719/+attachment/4312567/+files/dmesg.txt -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to upstart in Ubuntu. https://bugs.launchpad.net/bugs/1412719 Title: wait-for-state restarts whoopsie every 30sec Status in One Hundred Papercuts: Confirmed Status in Upstart: Confirmed Status in upstart package in Ubuntu: Confirmed Status in whoopsie package in Ubuntu: Triaged Bug description: wait-for-state is restarting whoopsie every 30sec: [14103.317598] init: whoopsie main process ended, respawning [14133.330315] init: wait-for-state (whoopsienetwork-manager) main process (10221) terminated with status 100 [14133.396185] init: whoopsie main process (10227) terminated with status 1 [14133.396205] init: whoopsie main process ended, respawning [14163.409765] init: wait-for-state (whoopsienetwork-manager) main process (10231) terminated with status 100 [14163.468346] init: whoopsie main process (10237) terminated with status 1 [14163.468366] init: whoopsie main process ended, respawning [14193.485204] init: wait-for-state (whoopsienetwork-manager) main process (10241) terminated with status 100 [14193.560511] init: whoopsie main process (10249) terminated with status 1 [14193.560531] init: whoopsie main process ended, respawning The problem in wait-for-state.conf is this line: status $WAIT_FOR | grep -q "$TARGET_GOAL/$WAIT_STATE" && exit 0 TARGET_GOAL is either "start" or "stop". WAIT_STATE by default is "started", but there is no job status like "start/started". so WAIT_STATE needs to be something like "running" (or "waiting" for goal of "stop"). ProblemType: Bug DistroRelease: Ubuntu 15.04 Package: upstart 1.13.2-0ubuntu6 ProcVersionSignature: Ubuntu 3.18.0-9.10-generic 3.18.2 Uname: Linux 3.18.0-9-generic x86_64 ApportVersion: 2.15.1-0ubuntu2 Architecture: amd64 CurrentDesktop: Unity Date: Tue Jan 20 20:59:02 2015 InstallationDate: Installed on 2014-09-03 (139 days ago) InstallationMedia: Ubuntu 14.10 "Utopic Unicorn" - Alpha amd64 (20140902) ProcKernelCmdline: BOOT_IMAGE=/boot/vmlinuz-3.18.0-9-generic root=UUID=93e046a8-7604-4f60-a5f8-b3be22f948aa ro quiet splash vt.handoff=7 SourcePackage: upstart UpgradeStatus: No upgrade log present (probably fresh install) UpstartBugCategory: System UpstartRunningSessionVersion: upstart 1.13.2 UpstartRunningSystemVersion: init (upstart 1.13.2) modified.conffile..etc.init.wait.for.state.conf: [modified] mtime.conffile..etc.init.wait.for.state.conf: 2015-01-20T20:02:17.598668 To manage notifications about this bug go to: https://bugs.launchpad.net/hundredpapercuts/+bug/1412719/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1161388] Re: compiz crashed with SIGABRT in __libc_message()
** Tags added: utopic -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to unity in Ubuntu. https://bugs.launchpad.net/bugs/1161388 Title: compiz crashed with SIGABRT in __libc_message() Status in Unity: Confirmed Status in “unity” package in Ubuntu: Confirmed Bug description: Searching in the dash caused compiz to crash. ProblemType: Crash DistroRelease: Ubuntu 13.04 Package: unity 6.12.0daily13.03.25.1-0ubuntu1 ProcVersionSignature: Ubuntu 3.8.0-15.25-generic 3.8.4 Uname: Linux 3.8.0-15-generic x86_64 ApportVersion: 2.9.2-0ubuntu5 Architecture: amd64 Date: Thu Mar 28 09:18:17 2013 ExecutablePath: /usr/bin/compiz InstallationDate: Installed on 2012-11-13 (134 days ago) InstallationMedia: Ubuntu 12.10 "Quantal Quetzal" - Release amd64 (20121017.5) MarkForUpload: True ProcCmdline: compiz ProcEnviron: LANGUAGE=en_CA:en PATH=(custom, user) XDG_RUNTIME_DIR= LANG=en_CA.UTF-8 SHELL=/bin/bash Signal: 6 SourcePackage: unity StacktraceTop: raise () from /lib/x86_64-linux-gnu/libc.so.6 abort () from /lib/x86_64-linux-gnu/libc.so.6 ?? () from /lib/x86_64-linux-gnu/libc.so.6 __fortify_fail () from /lib/x86_64-linux-gnu/libc.so.6 ?? () from /lib/x86_64-linux-gnu/libc.so.6 Title: compiz crashed with SIGABRT in raise() UpgradeStatus: Upgraded to raring on 2013-02-13 (42 days ago) UserGroups: adm cdrom dip libvirtd lpadmin plugdev sambashare sbuild sudo To manage notifications about this bug go to: https://bugs.launchpad.net/unity/+bug/1161388/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1353564] [NEW] Installed TV Card causing Shutdown and reboot Problem
Public bug reported: System worked under ubuntu 12.1 now on shutdown it stalls and wont turn computer off. will not restart either. If card (TV Wintv ) is removed then system works. Failing to dismount the card I think is there a workaround for this ??? running win7 op system also and utilize the card , dont want to have to take card out everytime I use Ubuntu Running Ubuntu 14.04 LTS ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: xorg 1:7.7+1ubuntu8 ProcVersionSignature: Ubuntu 3.13.0-32.57-generic 3.13.11.4 Uname: Linux 3.13.0-32-generic x86_64 NonfreeKernelModules: fglrx .tmp.unity.support.test.0: ApportVersion: 2.14.1-0ubuntu3.3 Architecture: amd64 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: compiz CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0' CompositorUnredirectFSW: true Date: Wed Aug 6 10:30:30 2014 DistUpgraded: 2014-07-31 03:44:45,043 DEBUG failed to SystemUnLock() (E:Not locked) DistroCodename: trusty DistroVariant: ubuntu DkmsStatus: fglrx, 13.350.1, 3.13.0-32-generic, x86_64: installed ExtraDebuggingInterest: Yes, if not too technical GraphicsCard: Advanced Micro Devices, Inc. [AMD/ATI] Barts XT [Radeon HD 6870] [1002:6738] (prog-if 00 [VGA controller]) Subsystem: Advanced Micro Devices, Inc. [AMD/ATI] Device [1002:00d0] InstallationDate: Installed on 2014-07-28 (8 days ago) InstallationMedia: Ubuntu 13.10 "Saucy Salamander" - Release amd64 (20131016.1) MachineType: Alienware Area 51 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.0-32-generic root=UUID=7395b8c0-809d-42a1-b06d-d5329145c95e ro nopat plymouth:debug vesafb.invalid=1 quiet splash SourcePackage: xorg UpgradeStatus: Upgraded to trusty on 2014-07-31 (6 days ago) dmi.bios.date: 11/09/2010 dmi.bios.vendor: Alienware dmi.bios.version: A10 dmi.board.name: 0XDJ4C dmi.board.vendor: Alienware dmi.board.version: A00 dmi.chassis.type: 3 dmi.chassis.vendor: Alienware dmi.modalias: dmi:bvnAlienware:bvrA10:bd11/09/2010:svnAlienware:pnArea51:pvr00:rvnAlienware:rn0XDJ4C:rvrA00:cvnAlienware:ct3:cvr: dmi.product.name: Area 51 dmi.product.version: 00 dmi.sys.vendor: Alienware version.compiz: compiz 1:0.9.11.2+14.04.20140714-0ubuntu1 version.fglrx-installer: fglrx-installer N/A version.ia32-libs: ia32-libs N/A version.libdrm2: libdrm2 2.4.52-1 version.libgl1-mesa-dri: libgl1-mesa-dri 10.1.3-0ubuntu0.1 version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A version.libgl1-mesa-glx: libgl1-mesa-glx 10.1.3-0ubuntu0.1 version.xserver-xorg-core: xserver-xorg-core 2:1.15.1-0ubuntu2.1 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.8.2-1ubuntu2 version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.3.0-1ubuntu3.1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.910-0ubuntu1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.10-1ubuntu2 xserver.bootTime: Wed Aug 6 10:26:43 2014 xserver.configfile: default xserver.errors: open /dev/dri/card0: No such file or directory open /dev/fb0: No such file or directory AIGLX error: failed to open /usr/X11R6/lib64/modules/dri/fglrx_dri.so, error[/usr/X11R6/lib64/modules/dri/fglrx_dri.so: cannot open shared object file: No such file or directory] AIGLX error: failed to open /usr/lib64/dri/fglrx_dri.so, error[/usr/lib64/dri/fglrx_dri.so: cannot open shared object file: No such file or directory] AIGLX error: failed to open /usr/X11R6/lib/modules/dri/fglrx_dri.so, error[/usr/X11R6/lib/modules/dri/fglrx_dri.so: cannot open shared object file: No such file or directory] xserver.logfile: /var/log/Xorg.0.log xserver.version: 2:1.15.1-0ubuntu2.1 xserver.video_driver: fglrx ** Affects: xorg (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug compiz-0.9 trusty 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/1353564 Title: Installed TV Card causing Shutdown and reboot Problem Status in “xorg” package in Ubuntu: New Bug description: System worked under ubuntu 12.1 now on shutdown it stalls and wont turn computer off. will not restart either. If card (TV Wintv ) is removed then system works. Failing to dismount the card I think is there a workaround for this ??? running win7 op system also and utilize the card , dont want to have to take card out everytime I use Ubuntu Running Ubuntu 14.04 LTS ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: xorg 1:7.7+1ubuntu8 ProcVersionSignature: Ubuntu 3.13.0-32.57-generic 3.13.11.4 Uname: Linux 3.13.0-32-generic x86_64 NonfreeKernelModules: fglrx .tmp.unity.support.test.0: ApportVersion: 2.14.1-0ubuntu3.3 Architecture: amd64 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: compiz CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Me
[Touch-packages] [Bug 1240198] Re: Wrong keyboard layout active after booting into desktop
Same problem in 14.10 Utopic. I use dpk-reconfigure keyboard-configuration to fix the settings, but after reboot it returns to English! -- 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/1240198 Title: Wrong keyboard layout active after booting into desktop Status in “ibus” package in Ubuntu: Triaged Status in “indicator-keyboard” package in Ubuntu: Triaged Bug description: I upgraded from raring to saucy. After booting into the desktop (unity), the english keyboard layout is active, although everything on the system is set to be german (keyboard layout, language...) Switching to a virtual terminal (ctrl+alt+f1) fixes the problem and changes the layout to the german layout. all the time, the new input settings indicator says the german layout is active. locale says: LANG=de_DE.UTF-8 LANGUAGE=de_DE LC_CTYPE="de_DE.UTF-8" LC_NUMERIC="de_DE.UTF-8" LC_TIME="de_DE.UTF-8" LC_COLLATE="de_DE.UTF-8" LC_MONETARY="de_DE.UTF-8" LC_MESSAGES="de_DE.UTF-8" LC_PAPER="de_DE.UTF-8" LC_NAME="de_DE.UTF-8" LC_ADDRESS="de_DE.UTF-8" LC_TELEPHONE="de_DE.UTF-8" LC_MEASUREMENT="de_DE.UTF-8" LC_IDENTIFICATION="de_DE.UTF-8" LC_ALL= /etc/default/keyboard says: # Check /usr/share/doc/keyboard-configuration/README.Debian for # documentation on what to do after having modified this file. # The following variables describe your keyboard and can have the same # values as the XkbModel, XkbLayout, XkbVariant and XkbOptions options # in /etc/X11/xorg.conf. XKBMODEL="pc105" XKBLAYOUT="de" XKBVARIANT="" XKBOPTIONS="" # If you don't want to use the XKB layout on the console, you can # specify an alternative keymap. Make sure it will be accessible # before /usr is mounted. # KMAP=/etc/console-setup/defkeymap.kmap.gz ProblemType: Bug DistroRelease: Ubuntu 13.10 Package: indicator-keyboard 0.0.0+13.10.20131010.1-0ubuntu1 ProcVersionSignature: Ubuntu 3.11.0-12.19-generic 3.11.3 Uname: Linux 3.11.0-12-generic x86_64 ApportVersion: 2.12.5-0ubuntu2 Architecture: amd64 Date: Tue Oct 15 20:49:03 2013 InstallationDate: Installed on 2013-04-26 (171 days ago) InstallationMedia: Ubuntu 13.04 "Raring Ringtail" - Release amd64 (20130424) MarkForUpload: True SourcePackage: indicator-keyboard UpgradeStatus: Upgraded to saucy on 2013-10-13 (2 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ibus/+bug/1240198/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1808060] Re: libmirclient causes multiarch SDL2 headers to conflict with each other
Isn't the most sensible way to fix this to change the libsdl2-dev packaging to depend on libmirclient9 directly? I can't think of any sane reason to expose the Mir headers to SDL2 users. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to mir in Ubuntu. https://bugs.launchpad.net/bugs/1808060 Title: libmirclient causes multiarch SDL2 headers to conflict with each other Status in mir package in Ubuntu: Triaged Bug description: libmirclient-dev makes impossible to install both libsdl2-dev and libsdl2-dev:i386 which is essential for anyone building game related software. Seeing mir not being used at all in any of the official Ubuntu flavors, I find it strange that it was considered an acceptable solution to break a common and important workflow in favor of an experimental display server. It's probably a minor packaging bug anyway, multi-arch development headers usually don't conflict with each other. ProblemType: Bug DistroRelease: Ubuntu 18.10 Package: libmirclient-dev 0.32.1-0ubuntu1 ProcVersionSignature: Ubuntu 4.18.0-11.12-generic 4.18.12 Uname: Linux 4.18.0-11-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.10-0ubuntu13.1 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Tue Dec 11 14:25:50 2018 SourcePackage: mir UpgradeStatus: Upgraded to cosmic on 2018-11-02 (39 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mir/+bug/1808060/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1808060] Re: libmirclient causes multiarch SDL2 headers to conflict with each other
On reflection, there are several factors contributing to the problem. Addressing any one of them would resolve the problem reported. 1. none of the Mir -dev packages are co-installable 2. libsdl2-dev should not depend on libmirclient-dev 3. SDL2 is being built with mirclient support on 18.10 1 & 2 have been the case since well before 16.04 and this issue has gone undetected. If there's a reason for /2/, it's a bad one. Regardless, we ought to address /1/. 3 is pointless and likely an oversight. I'm under the impression that SDL2 dropped mirclient support upstream, but I guess that hasn't filtered through yet. In any case mirclient lost GL support in 18.04 and will not support Nvidia eglstream drivers. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to mir in Ubuntu. https://bugs.launchpad.net/bugs/1808060 Title: libmirclient causes multiarch SDL2 headers to conflict with each other Status in mir package in Ubuntu: Triaged Bug description: libmirclient-dev makes impossible to install both libsdl2-dev and libsdl2-dev:i386 which is essential for anyone building game related software. Seeing mir not being used at all in any of the official Ubuntu flavors, I find it strange that it was considered an acceptable solution to break a common and important workflow in favor of an experimental display server. It's probably a minor packaging bug anyway, multi-arch development headers usually don't conflict with each other. ProblemType: Bug DistroRelease: Ubuntu 18.10 Package: libmirclient-dev 0.32.1-0ubuntu1 ProcVersionSignature: Ubuntu 4.18.0-11.12-generic 4.18.12 Uname: Linux 4.18.0-11-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.10-0ubuntu13.1 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Tue Dec 11 14:25:50 2018 SourcePackage: mir UpgradeStatus: Upgraded to cosmic on 2018-11-02 (39 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mir/+bug/1808060/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1812976] [NEW] package cups-bsd 2.2.7-1ubuntu2.3 failed to install/upgrade: installed cups-bsd package post-installation script subprocess returned error exit status 29
Public bug reported: fails to install update ProblemType: Package DistroRelease: Ubuntu 18.04 Package: cups-bsd 2.2.7-1ubuntu2.3 Uname: Linux 4.16.0-041600-generic x86_64 NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia ApportVersion: 2.20.9-0ubuntu7.5 Architecture: amd64 CupsErrorLog: Date: Sat Jan 19 16:16:52 2019 DuplicateSignature: package:cups-bsd:2.2.7-1ubuntu2.3 Setting up cups (2.2.7-1ubuntu2.3) ... Can't locate object method "new" via package "Text::Iconv" (perhaps you forgot to load "Text::Iconv"?) at /usr/share/perl5/Debconf/Encoding.pm line 65. dpkg: error processing package cups (--configure): installed cups package post-installation script subprocess returned error exit status 29 ErrorMessage: installed cups-bsd package post-installation script subprocess returned error exit status 29 InstallationDate: Installed on 2018-10-10 (104 days ago) InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 (20180725) Lpstat: Error: command ['lpstat', '-v'] failed with exit code 1: lpstat: No destinations added. Lsusb: Bus 004 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 003 Device 002: ID 045e:0750 Microsoft Corp. Wired Keyboard 600 Bus 003 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: Micro-Star International Co., Ltd MS-7A38 Papersize: a4 ProcCmdline: BOOT_IMAGE=/boot/vmlinuz-4.16.0-041600-generic root=UUID=cf49e5d3-b698-4d18-9122-55360cb14b83 ro quiet splash vt.handoff=1 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.16.0-041600-generic root=UUID=cf49e5d3-b698-4d18-9122-55360cb14b83 ro quiet splash vt.handoff=1 Python3Details: /usr/bin/python3.6, Python 3.6.7, python3-minimal, 3.6.7-1~18.04 PythonDetails: /usr/bin/python2.7, Python 2.7.15rc1, python-minimal, 2.7.15~rc1-1 RelatedPackageVersions: dpkg 1.19.0.5ubuntu2.1 apt 1.6.6ubuntu0.1 SourcePackage: cups Title: package cups-bsd 2.2.7-1ubuntu2.3 failed to install/upgrade: installed cups-bsd package post-installation script subprocess returned error exit status 29 UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 03/20/2017 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 2.00 dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: A320M BAZOOKA (MS-7A38) dmi.board.vendor: Micro-Star International Co., Ltd dmi.board.version: 1.0 dmi.chassis.asset.tag: To be filled by O.E.M. dmi.chassis.type: 10 dmi.chassis.vendor: Micro-Star International Co., Ltd dmi.chassis.version: 1.0 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr2.00:bd03/20/2017:svnMicro-StarInternationalCo.,Ltd:pnMS-7A38:pvr1.0:rvnMicro-StarInternationalCo.,Ltd:rnA320MBAZOOKA(MS-7A38):rvr1.0:cvnMicro-StarInternationalCo.,Ltd:ct10:cvr1.0: dmi.product.family: To be filled by O.E.M. dmi.product.name: MS-7A38 dmi.product.version: 1.0 dmi.sys.vendor: Micro-Star International Co., Ltd ** Affects: cups (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 cups in Ubuntu. https://bugs.launchpad.net/bugs/1812976 Title: package cups-bsd 2.2.7-1ubuntu2.3 failed to install/upgrade: installed cups-bsd package post-installation script subprocess returned error exit status 29 Status in cups package in Ubuntu: New Bug description: fails to install update ProblemType: Package DistroRelease: Ubuntu 18.04 Package: cups-bsd 2.2.7-1ubuntu2.3 Uname: Linux 4.16.0-041600-generic x86_64 NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia ApportVersion: 2.20.9-0ubuntu7.5 Architecture: amd64 CupsErrorLog: Date: Sat Jan 19 16:16:52 2019 DuplicateSignature: package:cups-bsd:2.2.7-1ubuntu2.3 Setting up cups (2.2.7-1ubuntu2.3) ... Can't locate object method "new" via package "Text::Iconv" (perhaps you forgot to load "Text::Iconv"?) at /usr/share/perl5/Debconf/Encoding.pm line 65. dpkg: error processing package cups (--configure): installed cups package post-installation script subprocess returned error exit status 29 ErrorMessage: installed cups-bsd package post-installation script subprocess returned error exit status 29 InstallationDate: Installed on 2018-10-10 (104 days ago) InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 (20180725) Lpstat: Error: command ['lpstat', '-v'] failed with exit code 1: lpstat: No destinations added. Lsusb: Bus 004 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 003 Device 002: ID 045e:0750 Microsoft Corp. Wired Keyboard 600 Bus 003 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: Micro-Star Internation
[Touch-packages] [Bug 1769075] UdevDb.txt
apport information ** Attachment added: "UdevDb.txt" https://bugs.launchpad.net/bugs/1769075/+attachment/5136050/+files/UdevDb.txt -- 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/1769075 Title: [regression][bionic] Bluetooth keyboard battery reports 0% Status in bluez package in Ubuntu: Invalid Status in linux package in Ubuntu: Confirmed Bug description: I've recently upgraded to 18.04 from 17.10 and after the upgrade "upower -d" reports always 0% as battery percentage of the bluetooth Logitech K810 keyboard. Which is a bit annoying since I get a KDE warning on the battery. Device: /org/freedesktop/UPower/devices/keyboard_hid_34o88o5do5eo0co2f_battery native-path: hid-34:88:5d:5e:0c:2f-battery model:Logitech K810 power supply: no updated: Fri 04 May 2018 09:20:43 AM CEST (51 seconds ago) has history: yes has statistics: yes keyboard present: yes rechargeable:yes state: unknown warning-level: none percentage: 0% icon-name: 'battery-missing-symbolic' My guess is that the issue is in the bluetooth rather in the upowerd since the reporting in the /sys/devices shows battery level of 0 --- ApportVersion: 2.20.9-0ubuntu7 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: bnv1714 F pulseaudio /dev/snd/pcmC0D0p: bnv1714 F...m pulseaudio /dev/snd/controlC0: bnv1714 F pulseaudio CurrentDesktop: KDE DistroRelease: Ubuntu 18.04 HibernationDevice: RESUME=UUID=e962613c-fc88-4740-8f0a-997838d3c2cf InstallationDate: Installed on 2017-11-02 (185 days ago) InstallationMedia: Kubuntu 17.10 "Artful Aardvark" - Release amd64 (20171017.1) IwConfig: lono wireless extensions. enp0s25 no wireless extensions. MachineType: Dell Inc. Precision Tower 5810 NonfreeKernelModules: nvidia_modeset nvidia Package: linux (not installed) ProcFB: 0 VESA VGA ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.15.0-20-generic root=UUID=4940c5fe-b600-4f27-8586-c6ac06ccea99 ro vga=773 quiet ProcVersionSignature: Ubuntu 4.15.0-20.21-generic 4.15.17 RelatedPackageVersions: linux-restricted-modules-4.15.0-20-generic N/A linux-backports-modules-4.15.0-20-generic N/A linux-firmware 1.173 RfKill: 0: hci0: Bluetooth Soft blocked: no Hard blocked: no Tags: bionic Uname: Linux 4.15.0-20-generic x86_64 UpgradeStatus: Upgraded to bionic on 2018-04-30 (7 days ago) UserGroups: adm cdrom dialout dip kvm lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 05/08/2017 dmi.bios.vendor: Dell Inc. dmi.bios.version: A19 dmi.board.name: 0K240Y dmi.board.vendor: Dell Inc. dmi.board.version: A01 dmi.chassis.type: 7 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvrA19:bd05/08/2017:svnDellInc.:pnPrecisionTower5810:pvr:rvnDellInc.:rn0K240Y:rvrA01:cvnDellInc.:ct7:cvr: dmi.product.name: Precision Tower 5810 dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/1769075/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1769075] ProcInterrupts.txt
apport information ** Attachment added: "ProcInterrupts.txt" https://bugs.launchpad.net/bugs/1769075/+attachment/5136046/+files/ProcInterrupts.txt -- 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/1769075 Title: [regression][bionic] Bluetooth keyboard battery reports 0% Status in bluez package in Ubuntu: Invalid Status in linux package in Ubuntu: Confirmed Bug description: I've recently upgraded to 18.04 from 17.10 and after the upgrade "upower -d" reports always 0% as battery percentage of the bluetooth Logitech K810 keyboard. Which is a bit annoying since I get a KDE warning on the battery. Device: /org/freedesktop/UPower/devices/keyboard_hid_34o88o5do5eo0co2f_battery native-path: hid-34:88:5d:5e:0c:2f-battery model:Logitech K810 power supply: no updated: Fri 04 May 2018 09:20:43 AM CEST (51 seconds ago) has history: yes has statistics: yes keyboard present: yes rechargeable:yes state: unknown warning-level: none percentage: 0% icon-name: 'battery-missing-symbolic' My guess is that the issue is in the bluetooth rather in the upowerd since the reporting in the /sys/devices shows battery level of 0 --- ApportVersion: 2.20.9-0ubuntu7 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: bnv1714 F pulseaudio /dev/snd/pcmC0D0p: bnv1714 F...m pulseaudio /dev/snd/controlC0: bnv1714 F pulseaudio CurrentDesktop: KDE DistroRelease: Ubuntu 18.04 HibernationDevice: RESUME=UUID=e962613c-fc88-4740-8f0a-997838d3c2cf InstallationDate: Installed on 2017-11-02 (185 days ago) InstallationMedia: Kubuntu 17.10 "Artful Aardvark" - Release amd64 (20171017.1) IwConfig: lono wireless extensions. enp0s25 no wireless extensions. MachineType: Dell Inc. Precision Tower 5810 NonfreeKernelModules: nvidia_modeset nvidia Package: linux (not installed) ProcFB: 0 VESA VGA ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.15.0-20-generic root=UUID=4940c5fe-b600-4f27-8586-c6ac06ccea99 ro vga=773 quiet ProcVersionSignature: Ubuntu 4.15.0-20.21-generic 4.15.17 RelatedPackageVersions: linux-restricted-modules-4.15.0-20-generic N/A linux-backports-modules-4.15.0-20-generic N/A linux-firmware 1.173 RfKill: 0: hci0: Bluetooth Soft blocked: no Hard blocked: no Tags: bionic Uname: Linux 4.15.0-20-generic x86_64 UpgradeStatus: Upgraded to bionic on 2018-04-30 (7 days ago) UserGroups: adm cdrom dialout dip kvm lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 05/08/2017 dmi.bios.vendor: Dell Inc. dmi.bios.version: A19 dmi.board.name: 0K240Y dmi.board.vendor: Dell Inc. dmi.board.version: A01 dmi.chassis.type: 7 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvrA19:bd05/08/2017:svnDellInc.:pnPrecisionTower5810:pvr:rvnDellInc.:rn0K240Y:rvrA01:cvnDellInc.:ct7:cvr: dmi.product.name: Precision Tower 5810 dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/1769075/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1769075] WifiSyslog.txt
apport information ** Attachment added: "WifiSyslog.txt" https://bugs.launchpad.net/bugs/1769075/+attachment/5136051/+files/WifiSyslog.txt -- 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/1769075 Title: [regression][bionic] Bluetooth keyboard battery reports 0% Status in bluez package in Ubuntu: Invalid Status in linux package in Ubuntu: Confirmed Bug description: I've recently upgraded to 18.04 from 17.10 and after the upgrade "upower -d" reports always 0% as battery percentage of the bluetooth Logitech K810 keyboard. Which is a bit annoying since I get a KDE warning on the battery. Device: /org/freedesktop/UPower/devices/keyboard_hid_34o88o5do5eo0co2f_battery native-path: hid-34:88:5d:5e:0c:2f-battery model:Logitech K810 power supply: no updated: Fri 04 May 2018 09:20:43 AM CEST (51 seconds ago) has history: yes has statistics: yes keyboard present: yes rechargeable:yes state: unknown warning-level: none percentage: 0% icon-name: 'battery-missing-symbolic' My guess is that the issue is in the bluetooth rather in the upowerd since the reporting in the /sys/devices shows battery level of 0 --- ApportVersion: 2.20.9-0ubuntu7 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: bnv1714 F pulseaudio /dev/snd/pcmC0D0p: bnv1714 F...m pulseaudio /dev/snd/controlC0: bnv1714 F pulseaudio CurrentDesktop: KDE DistroRelease: Ubuntu 18.04 HibernationDevice: RESUME=UUID=e962613c-fc88-4740-8f0a-997838d3c2cf InstallationDate: Installed on 2017-11-02 (185 days ago) InstallationMedia: Kubuntu 17.10 "Artful Aardvark" - Release amd64 (20171017.1) IwConfig: lono wireless extensions. enp0s25 no wireless extensions. MachineType: Dell Inc. Precision Tower 5810 NonfreeKernelModules: nvidia_modeset nvidia Package: linux (not installed) ProcFB: 0 VESA VGA ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.15.0-20-generic root=UUID=4940c5fe-b600-4f27-8586-c6ac06ccea99 ro vga=773 quiet ProcVersionSignature: Ubuntu 4.15.0-20.21-generic 4.15.17 RelatedPackageVersions: linux-restricted-modules-4.15.0-20-generic N/A linux-backports-modules-4.15.0-20-generic N/A linux-firmware 1.173 RfKill: 0: hci0: Bluetooth Soft blocked: no Hard blocked: no Tags: bionic Uname: Linux 4.15.0-20-generic x86_64 UpgradeStatus: Upgraded to bionic on 2018-04-30 (7 days ago) UserGroups: adm cdrom dialout dip kvm lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 05/08/2017 dmi.bios.vendor: Dell Inc. dmi.bios.version: A19 dmi.board.name: 0K240Y dmi.board.vendor: Dell Inc. dmi.board.version: A01 dmi.chassis.type: 7 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvrA19:bd05/08/2017:svnDellInc.:pnPrecisionTower5810:pvr:rvnDellInc.:rn0K240Y:rvrA01:cvnDellInc.:ct7:cvr: dmi.product.name: Precision Tower 5810 dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/1769075/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1769075] Lsusb.txt
apport information ** Attachment added: "Lsusb.txt" https://bugs.launchpad.net/bugs/1769075/+attachment/5136043/+files/Lsusb.txt -- 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/1769075 Title: [regression][bionic] Bluetooth keyboard battery reports 0% Status in bluez package in Ubuntu: Invalid Status in linux package in Ubuntu: Confirmed Bug description: I've recently upgraded to 18.04 from 17.10 and after the upgrade "upower -d" reports always 0% as battery percentage of the bluetooth Logitech K810 keyboard. Which is a bit annoying since I get a KDE warning on the battery. Device: /org/freedesktop/UPower/devices/keyboard_hid_34o88o5do5eo0co2f_battery native-path: hid-34:88:5d:5e:0c:2f-battery model:Logitech K810 power supply: no updated: Fri 04 May 2018 09:20:43 AM CEST (51 seconds ago) has history: yes has statistics: yes keyboard present: yes rechargeable:yes state: unknown warning-level: none percentage: 0% icon-name: 'battery-missing-symbolic' My guess is that the issue is in the bluetooth rather in the upowerd since the reporting in the /sys/devices shows battery level of 0 --- ApportVersion: 2.20.9-0ubuntu7 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: bnv1714 F pulseaudio /dev/snd/pcmC0D0p: bnv1714 F...m pulseaudio /dev/snd/controlC0: bnv1714 F pulseaudio CurrentDesktop: KDE DistroRelease: Ubuntu 18.04 HibernationDevice: RESUME=UUID=e962613c-fc88-4740-8f0a-997838d3c2cf InstallationDate: Installed on 2017-11-02 (185 days ago) InstallationMedia: Kubuntu 17.10 "Artful Aardvark" - Release amd64 (20171017.1) IwConfig: lono wireless extensions. enp0s25 no wireless extensions. MachineType: Dell Inc. Precision Tower 5810 NonfreeKernelModules: nvidia_modeset nvidia Package: linux (not installed) ProcFB: 0 VESA VGA ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.15.0-20-generic root=UUID=4940c5fe-b600-4f27-8586-c6ac06ccea99 ro vga=773 quiet ProcVersionSignature: Ubuntu 4.15.0-20.21-generic 4.15.17 RelatedPackageVersions: linux-restricted-modules-4.15.0-20-generic N/A linux-backports-modules-4.15.0-20-generic N/A linux-firmware 1.173 RfKill: 0: hci0: Bluetooth Soft blocked: no Hard blocked: no Tags: bionic Uname: Linux 4.15.0-20-generic x86_64 UpgradeStatus: Upgraded to bionic on 2018-04-30 (7 days ago) UserGroups: adm cdrom dialout dip kvm lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 05/08/2017 dmi.bios.vendor: Dell Inc. dmi.bios.version: A19 dmi.board.name: 0K240Y dmi.board.vendor: Dell Inc. dmi.board.version: A01 dmi.chassis.type: 7 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvrA19:bd05/08/2017:svnDellInc.:pnPrecisionTower5810:pvr:rvnDellInc.:rn0K240Y:rvrA01:cvnDellInc.:ct7:cvr: dmi.product.name: Precision Tower 5810 dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/1769075/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1769075] CurrentDmesg.txt
apport information ** Attachment added: "CurrentDmesg.txt" https://bugs.launchpad.net/bugs/1769075/+attachment/5136040/+files/CurrentDmesg.txt -- 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/1769075 Title: [regression][bionic] Bluetooth keyboard battery reports 0% Status in bluez package in Ubuntu: Invalid Status in linux package in Ubuntu: Confirmed Bug description: I've recently upgraded to 18.04 from 17.10 and after the upgrade "upower -d" reports always 0% as battery percentage of the bluetooth Logitech K810 keyboard. Which is a bit annoying since I get a KDE warning on the battery. Device: /org/freedesktop/UPower/devices/keyboard_hid_34o88o5do5eo0co2f_battery native-path: hid-34:88:5d:5e:0c:2f-battery model:Logitech K810 power supply: no updated: Fri 04 May 2018 09:20:43 AM CEST (51 seconds ago) has history: yes has statistics: yes keyboard present: yes rechargeable:yes state: unknown warning-level: none percentage: 0% icon-name: 'battery-missing-symbolic' My guess is that the issue is in the bluetooth rather in the upowerd since the reporting in the /sys/devices shows battery level of 0 --- ApportVersion: 2.20.9-0ubuntu7 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: bnv1714 F pulseaudio /dev/snd/pcmC0D0p: bnv1714 F...m pulseaudio /dev/snd/controlC0: bnv1714 F pulseaudio CurrentDesktop: KDE DistroRelease: Ubuntu 18.04 HibernationDevice: RESUME=UUID=e962613c-fc88-4740-8f0a-997838d3c2cf InstallationDate: Installed on 2017-11-02 (185 days ago) InstallationMedia: Kubuntu 17.10 "Artful Aardvark" - Release amd64 (20171017.1) IwConfig: lono wireless extensions. enp0s25 no wireless extensions. MachineType: Dell Inc. Precision Tower 5810 NonfreeKernelModules: nvidia_modeset nvidia Package: linux (not installed) ProcFB: 0 VESA VGA ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.15.0-20-generic root=UUID=4940c5fe-b600-4f27-8586-c6ac06ccea99 ro vga=773 quiet ProcVersionSignature: Ubuntu 4.15.0-20.21-generic 4.15.17 RelatedPackageVersions: linux-restricted-modules-4.15.0-20-generic N/A linux-backports-modules-4.15.0-20-generic N/A linux-firmware 1.173 RfKill: 0: hci0: Bluetooth Soft blocked: no Hard blocked: no Tags: bionic Uname: Linux 4.15.0-20-generic x86_64 UpgradeStatus: Upgraded to bionic on 2018-04-30 (7 days ago) UserGroups: adm cdrom dialout dip kvm lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 05/08/2017 dmi.bios.vendor: Dell Inc. dmi.bios.version: A19 dmi.board.name: 0K240Y dmi.board.vendor: Dell Inc. dmi.board.version: A01 dmi.chassis.type: 7 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvrA19:bd05/08/2017:svnDellInc.:pnPrecisionTower5810:pvr:rvnDellInc.:rn0K240Y:rvrA01:cvnDellInc.:ct7:cvr: dmi.product.name: Precision Tower 5810 dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/1769075/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1769075] ProcCpuinfoMinimal.txt
apport information ** Attachment added: "ProcCpuinfoMinimal.txt" https://bugs.launchpad.net/bugs/1769075/+attachment/5136045/+files/ProcCpuinfoMinimal.txt -- 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/1769075 Title: [regression][bionic] Bluetooth keyboard battery reports 0% Status in bluez package in Ubuntu: Invalid Status in linux package in Ubuntu: Confirmed Bug description: I've recently upgraded to 18.04 from 17.10 and after the upgrade "upower -d" reports always 0% as battery percentage of the bluetooth Logitech K810 keyboard. Which is a bit annoying since I get a KDE warning on the battery. Device: /org/freedesktop/UPower/devices/keyboard_hid_34o88o5do5eo0co2f_battery native-path: hid-34:88:5d:5e:0c:2f-battery model:Logitech K810 power supply: no updated: Fri 04 May 2018 09:20:43 AM CEST (51 seconds ago) has history: yes has statistics: yes keyboard present: yes rechargeable:yes state: unknown warning-level: none percentage: 0% icon-name: 'battery-missing-symbolic' My guess is that the issue is in the bluetooth rather in the upowerd since the reporting in the /sys/devices shows battery level of 0 --- ApportVersion: 2.20.9-0ubuntu7 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: bnv1714 F pulseaudio /dev/snd/pcmC0D0p: bnv1714 F...m pulseaudio /dev/snd/controlC0: bnv1714 F pulseaudio CurrentDesktop: KDE DistroRelease: Ubuntu 18.04 HibernationDevice: RESUME=UUID=e962613c-fc88-4740-8f0a-997838d3c2cf InstallationDate: Installed on 2017-11-02 (185 days ago) InstallationMedia: Kubuntu 17.10 "Artful Aardvark" - Release amd64 (20171017.1) IwConfig: lono wireless extensions. enp0s25 no wireless extensions. MachineType: Dell Inc. Precision Tower 5810 NonfreeKernelModules: nvidia_modeset nvidia Package: linux (not installed) ProcFB: 0 VESA VGA ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.15.0-20-generic root=UUID=4940c5fe-b600-4f27-8586-c6ac06ccea99 ro vga=773 quiet ProcVersionSignature: Ubuntu 4.15.0-20.21-generic 4.15.17 RelatedPackageVersions: linux-restricted-modules-4.15.0-20-generic N/A linux-backports-modules-4.15.0-20-generic N/A linux-firmware 1.173 RfKill: 0: hci0: Bluetooth Soft blocked: no Hard blocked: no Tags: bionic Uname: Linux 4.15.0-20-generic x86_64 UpgradeStatus: Upgraded to bionic on 2018-04-30 (7 days ago) UserGroups: adm cdrom dialout dip kvm lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 05/08/2017 dmi.bios.vendor: Dell Inc. dmi.bios.version: A19 dmi.board.name: 0K240Y dmi.board.vendor: Dell Inc. dmi.board.version: A01 dmi.chassis.type: 7 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvrA19:bd05/08/2017:svnDellInc.:pnPrecisionTower5810:pvr:rvnDellInc.:rn0K240Y:rvrA01:cvnDellInc.:ct7:cvr: dmi.product.name: Precision Tower 5810 dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/1769075/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1769075] RfKill.txt
apport information ** Attachment added: "RfKill.txt" https://bugs.launchpad.net/bugs/1769075/+attachment/5136049/+files/RfKill.txt -- 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/1769075 Title: [regression][bionic] Bluetooth keyboard battery reports 0% Status in bluez package in Ubuntu: Invalid Status in linux package in Ubuntu: Confirmed Bug description: I've recently upgraded to 18.04 from 17.10 and after the upgrade "upower -d" reports always 0% as battery percentage of the bluetooth Logitech K810 keyboard. Which is a bit annoying since I get a KDE warning on the battery. Device: /org/freedesktop/UPower/devices/keyboard_hid_34o88o5do5eo0co2f_battery native-path: hid-34:88:5d:5e:0c:2f-battery model:Logitech K810 power supply: no updated: Fri 04 May 2018 09:20:43 AM CEST (51 seconds ago) has history: yes has statistics: yes keyboard present: yes rechargeable:yes state: unknown warning-level: none percentage: 0% icon-name: 'battery-missing-symbolic' My guess is that the issue is in the bluetooth rather in the upowerd since the reporting in the /sys/devices shows battery level of 0 --- ApportVersion: 2.20.9-0ubuntu7 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: bnv1714 F pulseaudio /dev/snd/pcmC0D0p: bnv1714 F...m pulseaudio /dev/snd/controlC0: bnv1714 F pulseaudio CurrentDesktop: KDE DistroRelease: Ubuntu 18.04 HibernationDevice: RESUME=UUID=e962613c-fc88-4740-8f0a-997838d3c2cf InstallationDate: Installed on 2017-11-02 (185 days ago) InstallationMedia: Kubuntu 17.10 "Artful Aardvark" - Release amd64 (20171017.1) IwConfig: lono wireless extensions. enp0s25 no wireless extensions. MachineType: Dell Inc. Precision Tower 5810 NonfreeKernelModules: nvidia_modeset nvidia Package: linux (not installed) ProcFB: 0 VESA VGA ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.15.0-20-generic root=UUID=4940c5fe-b600-4f27-8586-c6ac06ccea99 ro vga=773 quiet ProcVersionSignature: Ubuntu 4.15.0-20.21-generic 4.15.17 RelatedPackageVersions: linux-restricted-modules-4.15.0-20-generic N/A linux-backports-modules-4.15.0-20-generic N/A linux-firmware 1.173 RfKill: 0: hci0: Bluetooth Soft blocked: no Hard blocked: no Tags: bionic Uname: Linux 4.15.0-20-generic x86_64 UpgradeStatus: Upgraded to bionic on 2018-04-30 (7 days ago) UserGroups: adm cdrom dialout dip kvm lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 05/08/2017 dmi.bios.vendor: Dell Inc. dmi.bios.version: A19 dmi.board.name: 0K240Y dmi.board.vendor: Dell Inc. dmi.board.version: A01 dmi.chassis.type: 7 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvrA19:bd05/08/2017:svnDellInc.:pnPrecisionTower5810:pvr:rvnDellInc.:rn0K240Y:rvrA01:cvnDellInc.:ct7:cvr: dmi.product.name: Precision Tower 5810 dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/1769075/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1769075] PulseList.txt
apport information ** Attachment added: "PulseList.txt" https://bugs.launchpad.net/bugs/1769075/+attachment/5136048/+files/PulseList.txt -- 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/1769075 Title: [regression][bionic] Bluetooth keyboard battery reports 0% Status in bluez package in Ubuntu: Invalid Status in linux package in Ubuntu: Confirmed Bug description: I've recently upgraded to 18.04 from 17.10 and after the upgrade "upower -d" reports always 0% as battery percentage of the bluetooth Logitech K810 keyboard. Which is a bit annoying since I get a KDE warning on the battery. Device: /org/freedesktop/UPower/devices/keyboard_hid_34o88o5do5eo0co2f_battery native-path: hid-34:88:5d:5e:0c:2f-battery model:Logitech K810 power supply: no updated: Fri 04 May 2018 09:20:43 AM CEST (51 seconds ago) has history: yes has statistics: yes keyboard present: yes rechargeable:yes state: unknown warning-level: none percentage: 0% icon-name: 'battery-missing-symbolic' My guess is that the issue is in the bluetooth rather in the upowerd since the reporting in the /sys/devices shows battery level of 0 --- ApportVersion: 2.20.9-0ubuntu7 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: bnv1714 F pulseaudio /dev/snd/pcmC0D0p: bnv1714 F...m pulseaudio /dev/snd/controlC0: bnv1714 F pulseaudio CurrentDesktop: KDE DistroRelease: Ubuntu 18.04 HibernationDevice: RESUME=UUID=e962613c-fc88-4740-8f0a-997838d3c2cf InstallationDate: Installed on 2017-11-02 (185 days ago) InstallationMedia: Kubuntu 17.10 "Artful Aardvark" - Release amd64 (20171017.1) IwConfig: lono wireless extensions. enp0s25 no wireless extensions. MachineType: Dell Inc. Precision Tower 5810 NonfreeKernelModules: nvidia_modeset nvidia Package: linux (not installed) ProcFB: 0 VESA VGA ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.15.0-20-generic root=UUID=4940c5fe-b600-4f27-8586-c6ac06ccea99 ro vga=773 quiet ProcVersionSignature: Ubuntu 4.15.0-20.21-generic 4.15.17 RelatedPackageVersions: linux-restricted-modules-4.15.0-20-generic N/A linux-backports-modules-4.15.0-20-generic N/A linux-firmware 1.173 RfKill: 0: hci0: Bluetooth Soft blocked: no Hard blocked: no Tags: bionic Uname: Linux 4.15.0-20-generic x86_64 UpgradeStatus: Upgraded to bionic on 2018-04-30 (7 days ago) UserGroups: adm cdrom dialout dip kvm lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 05/08/2017 dmi.bios.vendor: Dell Inc. dmi.bios.version: A19 dmi.board.name: 0K240Y dmi.board.vendor: Dell Inc. dmi.board.version: A01 dmi.chassis.type: 7 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvrA19:bd05/08/2017:svnDellInc.:pnPrecisionTower5810:pvr:rvnDellInc.:rn0K240Y:rvrA01:cvnDellInc.:ct7:cvr: dmi.product.name: Precision Tower 5810 dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/1769075/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1769075] apport information
ApportVersion: 2.20.9-0ubuntu7 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC2: alan 1290 F pulseaudio /dev/snd/controlC0: alan 1290 F pulseaudio CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 18.04 InstallationDate: Installed on 2018-04-27 (10 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426) MachineType: Dell Inc. XPS 13 9360 Package: linux (not installed) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_IN SHELL=/bin/bash ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-20-generic root=UUID=3161f6a4-dd39-499c-a6f2-bbe799f75e0c ro quiet splash vt.handoff=1 ProcVersionSignature: Ubuntu 4.15.0-20.21-generic 4.15.17 RelatedPackageVersions: linux-restricted-modules-4.15.0-20-generic N/A linux-backports-modules-4.15.0-20-generic N/A linux-firmware 1.173 Tags: bionic Uname: Linux 4.15.0-20-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 01/18/2017 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.3.2 dmi.board.name: 0839Y6 dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 9 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr1.3.2:bd01/18/2017:svnDellInc.:pnXPS139360:pvr:rvnDellInc.:rn0839Y6:rvrA00:cvnDellInc.:ct9:cvr: dmi.product.family: XPS dmi.product.name: XPS 13 9360 dmi.sys.vendor: Dell Inc. -- 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/1769075 Title: [regression][bionic] Bluetooth keyboard battery reports 0% Status in bluez package in Ubuntu: Invalid Status in linux package in Ubuntu: Confirmed Bug description: I've recently upgraded to 18.04 from 17.10 and after the upgrade "upower -d" reports always 0% as battery percentage of the bluetooth Logitech K810 keyboard. Which is a bit annoying since I get a KDE warning on the battery. Device: /org/freedesktop/UPower/devices/keyboard_hid_34o88o5do5eo0co2f_battery native-path: hid-34:88:5d:5e:0c:2f-battery model:Logitech K810 power supply: no updated: Fri 04 May 2018 09:20:43 AM CEST (51 seconds ago) has history: yes has statistics: yes keyboard present: yes rechargeable:yes state: unknown warning-level: none percentage: 0% icon-name: 'battery-missing-symbolic' My guess is that the issue is in the bluetooth rather in the upowerd since the reporting in the /sys/devices shows battery level of 0 --- ApportVersion: 2.20.9-0ubuntu7 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: bnv1714 F pulseaudio /dev/snd/pcmC0D0p: bnv1714 F...m pulseaudio /dev/snd/controlC0: bnv1714 F pulseaudio CurrentDesktop: KDE DistroRelease: Ubuntu 18.04 HibernationDevice: RESUME=UUID=e962613c-fc88-4740-8f0a-997838d3c2cf InstallationDate: Installed on 2017-11-02 (185 days ago) InstallationMedia: Kubuntu 17.10 "Artful Aardvark" - Release amd64 (20171017.1) IwConfig: lono wireless extensions. enp0s25 no wireless extensions. MachineType: Dell Inc. Precision Tower 5810 NonfreeKernelModules: nvidia_modeset nvidia Package: linux (not installed) ProcFB: 0 VESA VGA ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.15.0-20-generic root=UUID=4940c5fe-b600-4f27-8586-c6ac06ccea99 ro vga=773 quiet ProcVersionSignature: Ubuntu 4.15.0-20.21-generic 4.15.17 RelatedPackageVersions: linux-restricted-modules-4.15.0-20-generic N/A linux-backports-modules-4.15.0-20-generic N/A linux-firmware 1.173 RfKill: 0: hci0: Bluetooth Soft blocked: no Hard blocked: no Tags: bionic Uname: Linux 4.15.0-20-generic x86_64 UpgradeStatus: Upgraded to bionic on 2018-04-30 (7 days ago) UserGroups: adm cdrom dialout dip kvm lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 05/08/2017 dmi.bios.vendor: Dell Inc. dmi.bios.version: A19 dmi.board.name: 0K240Y dmi.board.vendor: Dell Inc. dmi.board.version: A01 dmi.chassis.type: 7 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvrA19:bd05/08/2017:svnDellInc.:pnPrecisionTower5810:pvr:rvnDellInc.:rn0K240Y:rvrA01:cvnDellInc.:ct7:cvr: dmi.product.name: Precision Tower 5810 dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/1769075/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.laun
[Touch-packages] [Bug 1769075] IwConfig.txt
apport information ** Attachment added: "IwConfig.txt" https://bugs.launchpad.net/bugs/1769075/+attachment/5136041/+files/IwConfig.txt -- 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/1769075 Title: [regression][bionic] Bluetooth keyboard battery reports 0% Status in bluez package in Ubuntu: Invalid Status in linux package in Ubuntu: Confirmed Bug description: I've recently upgraded to 18.04 from 17.10 and after the upgrade "upower -d" reports always 0% as battery percentage of the bluetooth Logitech K810 keyboard. Which is a bit annoying since I get a KDE warning on the battery. Device: /org/freedesktop/UPower/devices/keyboard_hid_34o88o5do5eo0co2f_battery native-path: hid-34:88:5d:5e:0c:2f-battery model:Logitech K810 power supply: no updated: Fri 04 May 2018 09:20:43 AM CEST (51 seconds ago) has history: yes has statistics: yes keyboard present: yes rechargeable:yes state: unknown warning-level: none percentage: 0% icon-name: 'battery-missing-symbolic' My guess is that the issue is in the bluetooth rather in the upowerd since the reporting in the /sys/devices shows battery level of 0 --- ApportVersion: 2.20.9-0ubuntu7 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: bnv1714 F pulseaudio /dev/snd/pcmC0D0p: bnv1714 F...m pulseaudio /dev/snd/controlC0: bnv1714 F pulseaudio CurrentDesktop: KDE DistroRelease: Ubuntu 18.04 HibernationDevice: RESUME=UUID=e962613c-fc88-4740-8f0a-997838d3c2cf InstallationDate: Installed on 2017-11-02 (185 days ago) InstallationMedia: Kubuntu 17.10 "Artful Aardvark" - Release amd64 (20171017.1) IwConfig: lono wireless extensions. enp0s25 no wireless extensions. MachineType: Dell Inc. Precision Tower 5810 NonfreeKernelModules: nvidia_modeset nvidia Package: linux (not installed) ProcFB: 0 VESA VGA ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.15.0-20-generic root=UUID=4940c5fe-b600-4f27-8586-c6ac06ccea99 ro vga=773 quiet ProcVersionSignature: Ubuntu 4.15.0-20.21-generic 4.15.17 RelatedPackageVersions: linux-restricted-modules-4.15.0-20-generic N/A linux-backports-modules-4.15.0-20-generic N/A linux-firmware 1.173 RfKill: 0: hci0: Bluetooth Soft blocked: no Hard blocked: no Tags: bionic Uname: Linux 4.15.0-20-generic x86_64 UpgradeStatus: Upgraded to bionic on 2018-04-30 (7 days ago) UserGroups: adm cdrom dialout dip kvm lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 05/08/2017 dmi.bios.vendor: Dell Inc. dmi.bios.version: A19 dmi.board.name: 0K240Y dmi.board.vendor: Dell Inc. dmi.board.version: A01 dmi.chassis.type: 7 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvrA19:bd05/08/2017:svnDellInc.:pnPrecisionTower5810:pvr:rvnDellInc.:rn0K240Y:rvrA01:cvnDellInc.:ct7:cvr: dmi.product.name: Precision Tower 5810 dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/1769075/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1769075] ProcModules.txt
apport information ** Attachment added: "ProcModules.txt" https://bugs.launchpad.net/bugs/1769075/+attachment/5136047/+files/ProcModules.txt -- 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/1769075 Title: [regression][bionic] Bluetooth keyboard battery reports 0% Status in bluez package in Ubuntu: Invalid Status in linux package in Ubuntu: Confirmed Bug description: I've recently upgraded to 18.04 from 17.10 and after the upgrade "upower -d" reports always 0% as battery percentage of the bluetooth Logitech K810 keyboard. Which is a bit annoying since I get a KDE warning on the battery. Device: /org/freedesktop/UPower/devices/keyboard_hid_34o88o5do5eo0co2f_battery native-path: hid-34:88:5d:5e:0c:2f-battery model:Logitech K810 power supply: no updated: Fri 04 May 2018 09:20:43 AM CEST (51 seconds ago) has history: yes has statistics: yes keyboard present: yes rechargeable:yes state: unknown warning-level: none percentage: 0% icon-name: 'battery-missing-symbolic' My guess is that the issue is in the bluetooth rather in the upowerd since the reporting in the /sys/devices shows battery level of 0 --- ApportVersion: 2.20.9-0ubuntu7 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: bnv1714 F pulseaudio /dev/snd/pcmC0D0p: bnv1714 F...m pulseaudio /dev/snd/controlC0: bnv1714 F pulseaudio CurrentDesktop: KDE DistroRelease: Ubuntu 18.04 HibernationDevice: RESUME=UUID=e962613c-fc88-4740-8f0a-997838d3c2cf InstallationDate: Installed on 2017-11-02 (185 days ago) InstallationMedia: Kubuntu 17.10 "Artful Aardvark" - Release amd64 (20171017.1) IwConfig: lono wireless extensions. enp0s25 no wireless extensions. MachineType: Dell Inc. Precision Tower 5810 NonfreeKernelModules: nvidia_modeset nvidia Package: linux (not installed) ProcFB: 0 VESA VGA ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.15.0-20-generic root=UUID=4940c5fe-b600-4f27-8586-c6ac06ccea99 ro vga=773 quiet ProcVersionSignature: Ubuntu 4.15.0-20.21-generic 4.15.17 RelatedPackageVersions: linux-restricted-modules-4.15.0-20-generic N/A linux-backports-modules-4.15.0-20-generic N/A linux-firmware 1.173 RfKill: 0: hci0: Bluetooth Soft blocked: no Hard blocked: no Tags: bionic Uname: Linux 4.15.0-20-generic x86_64 UpgradeStatus: Upgraded to bionic on 2018-04-30 (7 days ago) UserGroups: adm cdrom dialout dip kvm lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 05/08/2017 dmi.bios.vendor: Dell Inc. dmi.bios.version: A19 dmi.board.name: 0K240Y dmi.board.vendor: Dell Inc. dmi.board.version: A01 dmi.chassis.type: 7 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvrA19:bd05/08/2017:svnDellInc.:pnPrecisionTower5810:pvr:rvnDellInc.:rn0K240Y:rvrA01:cvnDellInc.:ct7:cvr: dmi.product.name: Precision Tower 5810 dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/1769075/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1769075] AlsaInfo.txt
apport information ** Attachment added: "AlsaInfo.txt" https://bugs.launchpad.net/bugs/1769075/+attachment/5136038/+files/AlsaInfo.txt -- 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/1769075 Title: [regression][bionic] Bluetooth keyboard battery reports 0% Status in bluez package in Ubuntu: Invalid Status in linux package in Ubuntu: Confirmed Bug description: I've recently upgraded to 18.04 from 17.10 and after the upgrade "upower -d" reports always 0% as battery percentage of the bluetooth Logitech K810 keyboard. Which is a bit annoying since I get a KDE warning on the battery. Device: /org/freedesktop/UPower/devices/keyboard_hid_34o88o5do5eo0co2f_battery native-path: hid-34:88:5d:5e:0c:2f-battery model:Logitech K810 power supply: no updated: Fri 04 May 2018 09:20:43 AM CEST (51 seconds ago) has history: yes has statistics: yes keyboard present: yes rechargeable:yes state: unknown warning-level: none percentage: 0% icon-name: 'battery-missing-symbolic' My guess is that the issue is in the bluetooth rather in the upowerd since the reporting in the /sys/devices shows battery level of 0 --- ApportVersion: 2.20.9-0ubuntu7 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: bnv1714 F pulseaudio /dev/snd/pcmC0D0p: bnv1714 F...m pulseaudio /dev/snd/controlC0: bnv1714 F pulseaudio CurrentDesktop: KDE DistroRelease: Ubuntu 18.04 HibernationDevice: RESUME=UUID=e962613c-fc88-4740-8f0a-997838d3c2cf InstallationDate: Installed on 2017-11-02 (185 days ago) InstallationMedia: Kubuntu 17.10 "Artful Aardvark" - Release amd64 (20171017.1) IwConfig: lono wireless extensions. enp0s25 no wireless extensions. MachineType: Dell Inc. Precision Tower 5810 NonfreeKernelModules: nvidia_modeset nvidia Package: linux (not installed) ProcFB: 0 VESA VGA ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.15.0-20-generic root=UUID=4940c5fe-b600-4f27-8586-c6ac06ccea99 ro vga=773 quiet ProcVersionSignature: Ubuntu 4.15.0-20.21-generic 4.15.17 RelatedPackageVersions: linux-restricted-modules-4.15.0-20-generic N/A linux-backports-modules-4.15.0-20-generic N/A linux-firmware 1.173 RfKill: 0: hci0: Bluetooth Soft blocked: no Hard blocked: no Tags: bionic Uname: Linux 4.15.0-20-generic x86_64 UpgradeStatus: Upgraded to bionic on 2018-04-30 (7 days ago) UserGroups: adm cdrom dialout dip kvm lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 05/08/2017 dmi.bios.vendor: Dell Inc. dmi.bios.version: A19 dmi.board.name: 0K240Y dmi.board.vendor: Dell Inc. dmi.board.version: A01 dmi.chassis.type: 7 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvrA19:bd05/08/2017:svnDellInc.:pnPrecisionTower5810:pvr:rvnDellInc.:rn0K240Y:rvrA01:cvnDellInc.:ct7:cvr: dmi.product.name: Precision Tower 5810 dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/1769075/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1769075] Lspci.txt
apport information ** Attachment added: "Lspci.txt" https://bugs.launchpad.net/bugs/1769075/+attachment/5136042/+files/Lspci.txt -- 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/1769075 Title: [regression][bionic] Bluetooth keyboard battery reports 0% Status in bluez package in Ubuntu: Invalid Status in linux package in Ubuntu: Confirmed Bug description: I've recently upgraded to 18.04 from 17.10 and after the upgrade "upower -d" reports always 0% as battery percentage of the bluetooth Logitech K810 keyboard. Which is a bit annoying since I get a KDE warning on the battery. Device: /org/freedesktop/UPower/devices/keyboard_hid_34o88o5do5eo0co2f_battery native-path: hid-34:88:5d:5e:0c:2f-battery model:Logitech K810 power supply: no updated: Fri 04 May 2018 09:20:43 AM CEST (51 seconds ago) has history: yes has statistics: yes keyboard present: yes rechargeable:yes state: unknown warning-level: none percentage: 0% icon-name: 'battery-missing-symbolic' My guess is that the issue is in the bluetooth rather in the upowerd since the reporting in the /sys/devices shows battery level of 0 --- ApportVersion: 2.20.9-0ubuntu7 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: bnv1714 F pulseaudio /dev/snd/pcmC0D0p: bnv1714 F...m pulseaudio /dev/snd/controlC0: bnv1714 F pulseaudio CurrentDesktop: KDE DistroRelease: Ubuntu 18.04 HibernationDevice: RESUME=UUID=e962613c-fc88-4740-8f0a-997838d3c2cf InstallationDate: Installed on 2017-11-02 (185 days ago) InstallationMedia: Kubuntu 17.10 "Artful Aardvark" - Release amd64 (20171017.1) IwConfig: lono wireless extensions. enp0s25 no wireless extensions. MachineType: Dell Inc. Precision Tower 5810 NonfreeKernelModules: nvidia_modeset nvidia Package: linux (not installed) ProcFB: 0 VESA VGA ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.15.0-20-generic root=UUID=4940c5fe-b600-4f27-8586-c6ac06ccea99 ro vga=773 quiet ProcVersionSignature: Ubuntu 4.15.0-20.21-generic 4.15.17 RelatedPackageVersions: linux-restricted-modules-4.15.0-20-generic N/A linux-backports-modules-4.15.0-20-generic N/A linux-firmware 1.173 RfKill: 0: hci0: Bluetooth Soft blocked: no Hard blocked: no Tags: bionic Uname: Linux 4.15.0-20-generic x86_64 UpgradeStatus: Upgraded to bionic on 2018-04-30 (7 days ago) UserGroups: adm cdrom dialout dip kvm lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 05/08/2017 dmi.bios.vendor: Dell Inc. dmi.bios.version: A19 dmi.board.name: 0K240Y dmi.board.vendor: Dell Inc. dmi.board.version: A01 dmi.chassis.type: 7 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvrA19:bd05/08/2017:svnDellInc.:pnPrecisionTower5810:pvr:rvnDellInc.:rn0K240Y:rvrA01:cvnDellInc.:ct7:cvr: dmi.product.name: Precision Tower 5810 dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/1769075/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1769075] CRDA.txt
apport information ** Attachment added: "CRDA.txt" https://bugs.launchpad.net/bugs/1769075/+attachment/5136039/+files/CRDA.txt -- 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/1769075 Title: [regression][bionic] Bluetooth keyboard battery reports 0% Status in bluez package in Ubuntu: Invalid Status in linux package in Ubuntu: Confirmed Bug description: I've recently upgraded to 18.04 from 17.10 and after the upgrade "upower -d" reports always 0% as battery percentage of the bluetooth Logitech K810 keyboard. Which is a bit annoying since I get a KDE warning on the battery. Device: /org/freedesktop/UPower/devices/keyboard_hid_34o88o5do5eo0co2f_battery native-path: hid-34:88:5d:5e:0c:2f-battery model:Logitech K810 power supply: no updated: Fri 04 May 2018 09:20:43 AM CEST (51 seconds ago) has history: yes has statistics: yes keyboard present: yes rechargeable:yes state: unknown warning-level: none percentage: 0% icon-name: 'battery-missing-symbolic' My guess is that the issue is in the bluetooth rather in the upowerd since the reporting in the /sys/devices shows battery level of 0 --- ApportVersion: 2.20.9-0ubuntu7 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: bnv1714 F pulseaudio /dev/snd/pcmC0D0p: bnv1714 F...m pulseaudio /dev/snd/controlC0: bnv1714 F pulseaudio CurrentDesktop: KDE DistroRelease: Ubuntu 18.04 HibernationDevice: RESUME=UUID=e962613c-fc88-4740-8f0a-997838d3c2cf InstallationDate: Installed on 2017-11-02 (185 days ago) InstallationMedia: Kubuntu 17.10 "Artful Aardvark" - Release amd64 (20171017.1) IwConfig: lono wireless extensions. enp0s25 no wireless extensions. MachineType: Dell Inc. Precision Tower 5810 NonfreeKernelModules: nvidia_modeset nvidia Package: linux (not installed) ProcFB: 0 VESA VGA ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.15.0-20-generic root=UUID=4940c5fe-b600-4f27-8586-c6ac06ccea99 ro vga=773 quiet ProcVersionSignature: Ubuntu 4.15.0-20.21-generic 4.15.17 RelatedPackageVersions: linux-restricted-modules-4.15.0-20-generic N/A linux-backports-modules-4.15.0-20-generic N/A linux-firmware 1.173 RfKill: 0: hci0: Bluetooth Soft blocked: no Hard blocked: no Tags: bionic Uname: Linux 4.15.0-20-generic x86_64 UpgradeStatus: Upgraded to bionic on 2018-04-30 (7 days ago) UserGroups: adm cdrom dialout dip kvm lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 05/08/2017 dmi.bios.vendor: Dell Inc. dmi.bios.version: A19 dmi.board.name: 0K240Y dmi.board.vendor: Dell Inc. dmi.board.version: A01 dmi.chassis.type: 7 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvrA19:bd05/08/2017:svnDellInc.:pnPrecisionTower5810:pvr:rvnDellInc.:rn0K240Y:rvrA01:cvnDellInc.:ct7:cvr: dmi.product.name: Precision Tower 5810 dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/1769075/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1769075] ProcCpuinfo.txt
apport information ** Attachment added: "ProcCpuinfo.txt" https://bugs.launchpad.net/bugs/1769075/+attachment/5136044/+files/ProcCpuinfo.txt -- 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/1769075 Title: [regression][bionic] Bluetooth keyboard battery reports 0% Status in bluez package in Ubuntu: Invalid Status in linux package in Ubuntu: Confirmed Bug description: I've recently upgraded to 18.04 from 17.10 and after the upgrade "upower -d" reports always 0% as battery percentage of the bluetooth Logitech K810 keyboard. Which is a bit annoying since I get a KDE warning on the battery. Device: /org/freedesktop/UPower/devices/keyboard_hid_34o88o5do5eo0co2f_battery native-path: hid-34:88:5d:5e:0c:2f-battery model:Logitech K810 power supply: no updated: Fri 04 May 2018 09:20:43 AM CEST (51 seconds ago) has history: yes has statistics: yes keyboard present: yes rechargeable:yes state: unknown warning-level: none percentage: 0% icon-name: 'battery-missing-symbolic' My guess is that the issue is in the bluetooth rather in the upowerd since the reporting in the /sys/devices shows battery level of 0 --- ApportVersion: 2.20.9-0ubuntu7 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: bnv1714 F pulseaudio /dev/snd/pcmC0D0p: bnv1714 F...m pulseaudio /dev/snd/controlC0: bnv1714 F pulseaudio CurrentDesktop: KDE DistroRelease: Ubuntu 18.04 HibernationDevice: RESUME=UUID=e962613c-fc88-4740-8f0a-997838d3c2cf InstallationDate: Installed on 2017-11-02 (185 days ago) InstallationMedia: Kubuntu 17.10 "Artful Aardvark" - Release amd64 (20171017.1) IwConfig: lono wireless extensions. enp0s25 no wireless extensions. MachineType: Dell Inc. Precision Tower 5810 NonfreeKernelModules: nvidia_modeset nvidia Package: linux (not installed) ProcFB: 0 VESA VGA ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.15.0-20-generic root=UUID=4940c5fe-b600-4f27-8586-c6ac06ccea99 ro vga=773 quiet ProcVersionSignature: Ubuntu 4.15.0-20.21-generic 4.15.17 RelatedPackageVersions: linux-restricted-modules-4.15.0-20-generic N/A linux-backports-modules-4.15.0-20-generic N/A linux-firmware 1.173 RfKill: 0: hci0: Bluetooth Soft blocked: no Hard blocked: no Tags: bionic Uname: Linux 4.15.0-20-generic x86_64 UpgradeStatus: Upgraded to bionic on 2018-04-30 (7 days ago) UserGroups: adm cdrom dialout dip kvm lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 05/08/2017 dmi.bios.vendor: Dell Inc. dmi.bios.version: A19 dmi.board.name: 0K240Y dmi.board.vendor: Dell Inc. dmi.board.version: A01 dmi.chassis.type: 7 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvrA19:bd05/08/2017:svnDellInc.:pnPrecisionTower5810:pvr:rvnDellInc.:rn0K240Y:rvrA01:cvnDellInc.:ct7:cvr: dmi.product.name: Precision Tower 5810 dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/1769075/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1769075] Re: [regression][bionic] Bluetooth keyboard battery reports 0%
I have this issue for both my Logitech K810 Keyboard as well as my Logitech T630 Mouse. -- 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/1769075 Title: [regression][bionic] Bluetooth keyboard battery reports 0% Status in bluez package in Ubuntu: Invalid Status in linux package in Ubuntu: Confirmed Bug description: I've recently upgraded to 18.04 from 17.10 and after the upgrade "upower -d" reports always 0% as battery percentage of the bluetooth Logitech K810 keyboard. Which is a bit annoying since I get a KDE warning on the battery. Device: /org/freedesktop/UPower/devices/keyboard_hid_34o88o5do5eo0co2f_battery native-path: hid-34:88:5d:5e:0c:2f-battery model:Logitech K810 power supply: no updated: Fri 04 May 2018 09:20:43 AM CEST (51 seconds ago) has history: yes has statistics: yes keyboard present: yes rechargeable:yes state: unknown warning-level: none percentage: 0% icon-name: 'battery-missing-symbolic' My guess is that the issue is in the bluetooth rather in the upowerd since the reporting in the /sys/devices shows battery level of 0 --- ApportVersion: 2.20.9-0ubuntu7 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: bnv1714 F pulseaudio /dev/snd/pcmC0D0p: bnv1714 F...m pulseaudio /dev/snd/controlC0: bnv1714 F pulseaudio CurrentDesktop: KDE DistroRelease: Ubuntu 18.04 HibernationDevice: RESUME=UUID=e962613c-fc88-4740-8f0a-997838d3c2cf InstallationDate: Installed on 2017-11-02 (185 days ago) InstallationMedia: Kubuntu 17.10 "Artful Aardvark" - Release amd64 (20171017.1) IwConfig: lono wireless extensions. enp0s25 no wireless extensions. MachineType: Dell Inc. Precision Tower 5810 NonfreeKernelModules: nvidia_modeset nvidia Package: linux (not installed) ProcFB: 0 VESA VGA ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.15.0-20-generic root=UUID=4940c5fe-b600-4f27-8586-c6ac06ccea99 ro vga=773 quiet ProcVersionSignature: Ubuntu 4.15.0-20.21-generic 4.15.17 RelatedPackageVersions: linux-restricted-modules-4.15.0-20-generic N/A linux-backports-modules-4.15.0-20-generic N/A linux-firmware 1.173 RfKill: 0: hci0: Bluetooth Soft blocked: no Hard blocked: no Tags: bionic Uname: Linux 4.15.0-20-generic x86_64 UpgradeStatus: Upgraded to bionic on 2018-04-30 (7 days ago) UserGroups: adm cdrom dialout dip kvm lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 05/08/2017 dmi.bios.vendor: Dell Inc. dmi.bios.version: A19 dmi.board.name: 0K240Y dmi.board.vendor: Dell Inc. dmi.board.version: A01 dmi.chassis.type: 7 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvrA19:bd05/08/2017:svnDellInc.:pnPrecisionTower5810:pvr:rvnDellInc.:rn0K240Y:rvrA01:cvnDellInc.:ct7:cvr: dmi.product.name: Precision Tower 5810 dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/1769075/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1769075] Re: [regression][bionic] Bluetooth keyboard battery reports 0% (in kernel 4.15 and later)
I just noticed this. my bluetooth keyboard appears to be reporting the battery status while the bluetooth mouse doesn't. This wasnt the case earlier and both were reporting 0%. To clarify on the timeline: ubuntu 17.10 - both were reporting correctly. after installation of 18.04, both stopped. after some core updates that came in yesterday, keyboard reports. ** Attachment added: "Battery Status Screenshot" https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/1769075/+attachment/5137326/+files/battery.png -- 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/1769075 Title: [regression][bionic] Bluetooth keyboard battery reports 0% (in kernel 4.15 and later) Status in bluez package in Ubuntu: Invalid Status in linux package in Ubuntu: Confirmed Bug description: I've recently upgraded to 18.04 from 17.10 and after the upgrade "upower -d" reports always 0% as battery percentage of the bluetooth Logitech K810 keyboard. Which is a bit annoying since I get a KDE warning on the battery. Device: /org/freedesktop/UPower/devices/keyboard_hid_34o88o5do5eo0co2f_battery native-path: hid-34:88:5d:5e:0c:2f-battery model:Logitech K810 power supply: no updated: Fri 04 May 2018 09:20:43 AM CEST (51 seconds ago) has history: yes has statistics: yes keyboard present: yes rechargeable:yes state: unknown warning-level: none percentage: 0% icon-name: 'battery-missing-symbolic' My guess is that the issue is in the bluetooth rather in the upowerd since the reporting in the /sys/devices shows battery level of 0 --- ApportVersion: 2.20.9-0ubuntu7 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: bnv1714 F pulseaudio /dev/snd/pcmC0D0p: bnv1714 F...m pulseaudio /dev/snd/controlC0: bnv1714 F pulseaudio CurrentDesktop: KDE DistroRelease: Ubuntu 18.04 HibernationDevice: RESUME=UUID=e962613c-fc88-4740-8f0a-997838d3c2cf InstallationDate: Installed on 2017-11-02 (185 days ago) InstallationMedia: Kubuntu 17.10 "Artful Aardvark" - Release amd64 (20171017.1) IwConfig: lono wireless extensions. enp0s25 no wireless extensions. MachineType: Dell Inc. Precision Tower 5810 NonfreeKernelModules: nvidia_modeset nvidia Package: linux (not installed) ProcFB: 0 VESA VGA ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.15.0-20-generic root=UUID=4940c5fe-b600-4f27-8586-c6ac06ccea99 ro vga=773 quiet ProcVersionSignature: Ubuntu 4.15.0-20.21-generic 4.15.17 RelatedPackageVersions: linux-restricted-modules-4.15.0-20-generic N/A linux-backports-modules-4.15.0-20-generic N/A linux-firmware 1.173 RfKill: 0: hci0: Bluetooth Soft blocked: no Hard blocked: no Tags: bionic Uname: Linux 4.15.0-20-generic x86_64 UpgradeStatus: Upgraded to bionic on 2018-04-30 (7 days ago) UserGroups: adm cdrom dialout dip kvm lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 05/08/2017 dmi.bios.vendor: Dell Inc. dmi.bios.version: A19 dmi.board.name: 0K240Y dmi.board.vendor: Dell Inc. dmi.board.version: A01 dmi.chassis.type: 7 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvrA19:bd05/08/2017:svnDellInc.:pnPrecisionTower5810:pvr:rvnDellInc.:rn0K240Y:rvrA01:cvnDellInc.:ct7:cvr: dmi.product.name: Precision Tower 5810 dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/1769075/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1728574] Re: Xwayland fails to initialize on miral-desktop
** Changed in: mir (Ubuntu)
Status: In Progress => Fix Released
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to mir in Ubuntu.
https://bugs.launchpad.net/bugs/1728574
Title:
Xwayland fails to initialize on miral-desktop
Status in Mir:
Triaged
Status in mir package in Ubuntu:
Fix Released
Bug description:
$ miral-desktop
$ WAYLAND_DEBUG=1 miral-xrun xeyes
This outputs:
[3478171.835] -> wl_display@1.get_registry(new id wl_registry@2)
[3478171.859] -> wl_disp...@1.sync(new id wl_callback@3)
[3478171.992] wl_display@1.delete_id(3)
[3478172.018] wl_registry@2.global(1, "wl_compositor", 3)
[3478172.032] -> wl_regis...@2.bind(1, "wl_compositor", 1, new id
[unknown]@4)
[3478172.056] wl_registry@2.global(2, "wl_seat", 5)
[3478172.061] wl_registry@2.global(3, "wl_output", 2)
[3478172.065] -> wl_regis...@2.bind(3, "wl_output", 2, new id [unknown]@5)
[3478172.078] wl_registry@2.global(4, "wl_shell", 1)
[3478172.083] -> wl_regis...@2.bind(4, "wl_shell", 1, new id [unknown]@6)
[3478172.087] wl_registry@2.global(5, "wl_shm", 1)
[3478172.092] -> wl_regis...@2.bind(5, "wl_shm", 1, new id [unknown]@7)
[3478172.098] wl_registry@2.global(6, "wl_drm", 2)
[3478172.104] -> wl_regis...@2.bind(6, "wl_drm", 2, new id [unknown]@8)
[3478172.113] wl_callb...@3.done(0)
[3478172.119] -> wl_disp...@1.sync(new id wl_callback@3)
[3478172.227] wl_display@1.delete_id(3)
[3478172.248] wl_output@5.geometry(0, 0, 310, 170, 0, "Fake manufacturer",
"Fake model", 0)
[3478172.271] wl_out...@5.mode(3, 1600, 900, 59970)
[3478172.277] wl_output@5.scale(1)
[3478172.280] wl_out...@5.done()
[3478172.287] wl_drm@8.device("/dev/dri/card0")
wayland-egl: could not open /dev/dri/card0 (Permission denied)
[3478172.300] wl_drm@8.format(875713089)
[3478172.304] wl_drm@8.format(875713112)
[3478172.308] wl_drm@8.format(909199186)
[3478172.312] wl_drm@8.format(961959257)
[3478172.317] wl_drm@8.format(825316697)
[3478172.321] wl_drm@8.format(842093913)
[3478172.325] wl_drm@8.format(909202777)
[3478172.330] wl_drm@8.format(875713881)
[3478172.335] wl_drm@8.format(842094158)
[3478172.339] wl_drm@8.format(909203022)
[3478172.344] wl_drm@8.format(1448695129)
[3478172.349] wl_drm@8.capabilities(1)
[3478172.353] wl_callb...@3.done(0)
[3478172.359] -> wl_disp...@1.sync(new id wl_callback@3)
[3478172.388] wl_display@1.delete_id(3)
[3478172.399] wl_callb...@3.done(0)
[3478172.406] -> wl_disp...@1.sync(new id wl_callback@3)
[3478172.486] wl_display@1.delete_id(3)
[3478172.498] wl_callb...@3.done(0)
[3478172.502] -> wl_disp...@1.sync(new id wl_callback@3)
[3478172.532] wl_display@1.delete_id(3)
[3478172.541] wl_callb...@3.done(0)
[3478172.560] -> wl_disp...@1.sync(new id wl_callback@3)
[3478172.610] wl_display@1.delete_id(3)
[3478172.623] wl_callb...@3.done(0)
with a lot of repetition of the last three lines. X11 clients fail to
connect.
For comparison, the output when connecting to miral-app is:
[3926349.817] -> wl_display@1.get_registry(new id wl_registry@2)
[3926349.862] -> wl_disp...@1.sync(new id wl_callback@3)
[3926349.970] wl_display@1.delete_id(3)
[3926349.994] wl_registry@2.global(1, "wl_compositor", 3)
[3926350.006] -> wl_regis...@2.bind(1, "wl_compositor", 1, new id
[unknown]@4)
[3926350.025] wl_registry@2.global(2, "wl_seat", 5)
[3926350.033] wl_registry@2.global(3, "wl_output", 2)
[3926350.053] -> wl_regis...@2.bind(3, "wl_output", 2, new id [unknown]@5)
[3926350.073] wl_registry@2.global(4, "wl_shell", 1)
[3926350.078] -> wl_regis...@2.bind(4, "wl_shell", 1, new id [unknown]@6)
[3926350.083] wl_registry@2.global(5, "wl_shm", 1)
[3926350.089] -> wl_regis...@2.bind(5, "wl_shm", 1, new id [unknown]@7)
[3926350.097] wl_registry@2.global(6, "wl_drm", 2)
[3926350.101] -> wl_regis...@2.bind(6, "wl_drm", 2, new id [unknown]@8)
[3926350.106] wl_callb...@3.done(1)
[3926350.109] -> wl_disp...@1.sync(new id wl_callback@3)
[3926350.184] wl_display@1.delete_id(3)
[3926350.190] wl_output@5.geometry(0, 0, 338, 198, 0, "Fake manufacturer",
"Fake model", 0)
[3926350.201] wl_out...@5.mode(3, 1280, 750, 6)
[3926350.208] wl_output@5.scale(1)
[3926350.211] wl_out...@5.done()
[3926350.219] wl_drm@8.device("/dev/dri/renderD128")
glamor: EGL version 1.4 (DRI2):
[3926360.938] wl_drm@8.format(875713089)
[3926360.952] wl_drm@8.format(875713112)
[3926360.954] wl_drm@8.format(909199186)
[3926360.957] wl_drm@8.format(961959257)
[3926360.959] wl_drm@8.format(825316697)
[3926360.971] wl_drm@8.format(842093913)
[3926360.973] wl_drm@8.format(909202777)
[3926360.975] wl_drm@8.format(875713881)
[3926360.979] wl_drm@8.format(842094158)
[3926360.981] wl_drm@8.format(909203022)
[3926360.983] wl_drm@8.format(1448695129)
[3926360.985] wl_drm@8.capabilities(1)
[3926360.988] wl_callb...@3.done(1)
[39
[Touch-packages] [Bug 1523621] Re: [ FAILED ] NestedServer.*_cursor_* (usually NestedServer.named_cursor_image_changes_are_forwarded_to_host)
** Changed in: mir (Ubuntu) Status: Triaged => In Progress ** Changed in: mir (Ubuntu) Assignee: (unassigned) => Alan Griffiths (alan-griffiths) -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to mir in Ubuntu. https://bugs.launchpad.net/bugs/1523621 Title: [ FAILED ] NestedServer.*_cursor_* (usually NestedServer.named_cursor_image_changes_are_forwarded_to_host) Status in Mir: Triaged Status in mir package in Ubuntu: In Progress Bug description: while bin/mir_acceptance_tests --gtest_filter=NestedServer.named_cursor_image_changes_are_forwarded_to_host; do :; done fails after a few hundred iterations. NB There two are other tests that are probably manifesting the same underlying issue: NestedServer.can_hide_the_host_cursor NestedServer.animated_cursor_image_changes_are_forwarded_to_host To manage notifications about this bug go to: https://bugs.launchpad.net/mir/+bug/1523621/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1706050] Re: [testsfail] NestedServer.given_client_set_display_configuration_when_monitor_unplugs_client_can_set_display_configuration
*** This bug is a duplicate of bug 1523621 *** https://bugs.launchpad.net/bugs/1523621 ** This bug has been marked a duplicate of bug 1523621 [ FAILED ] NestedServer.*_cursor_* (usually NestedServer.named_cursor_image_changes_are_forwarded_to_host) -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to mir in Ubuntu. https://bugs.launchpad.net/bugs/1706050 Title: [testsfail] NestedServer.given_client_set_display_configuration_when_monitor_unplugs_client_can_set_display_configuration Status in Mir: New Status in mir package in Ubuntu: New Bug description: 08:52:06 9: [ RUN ] NestedServer.given_client_set_display_configuration_when_monitor_unplugs_client_can_set_display_configuration 08:52:06 9: [2017-07-24 08:52:06.185457] mirserver: Starting 08:52:06 9: [2017-07-24 08:52:06.186524] mirserver: Selected driver: mir:stub-graphics (version 0.27.0) 08:52:06 9: [2017-07-24 08:52:06.196052] mirserver: Using software cursor 08:52:06 9: [2017-07-24 08:52:06.430690] mirserver: Selected input driver: mir:stub-input (version: 0.27.0) 08:52:06 9: [2017-07-24 08:52:06.438641] mirserver: Mir version 0.27.0 08:52:06 9: [2017-07-24 08:52:06.443482] mirserver: Initial display configuration: 08:52:06 9: [2017-07-24 08:52:06.443704] mirserver: CMakeFiles CTestTestfile.cmake Makefile cmake_install.cmake mir_acceptance_tests_precompiled.hpp.gch precompiled.hpp.compileflags precompiled.hpp.compileflags.processed Output 1: VGA connected, used 08:52:06 9: [2017-07-24 08:52:06.443988] mirserver: . |_ Physical size 0.0" 0x0mm 08:52:06 9: [2017-07-24 08:52:06.444144] mirserver: . |_ Power is on 08:52:06 9: [2017-07-24 08:52:06.444331] mirserver: . |_ Current mode 640x480 60.00Hz 08:52:06 9: [2017-07-24 08:52:06.444514] mirserver: . |_ Preferred mode 640x480 60.00Hz 08:52:06 9: [2017-07-24 08:52:06.444669] mirserver: . |_ Orientation normal 08:52:06 9: [2017-07-24 08:52:06.444828] mirserver: . |_ Logical size 640x480 08:52:06 9: [2017-07-24 08:52:06.444983] mirserver: . |_ Logical position +0+0 08:52:06 9: [2017-07-24 08:52:06.445145] mirserver: . |_ Scaling factor: 1.00 08:52:06 9: [2017-07-24 08:52:06.463562] mirserver: Starting 08:52:07 9: [2017-07-24 08:52:06.995460] mirserver: Using nested cursor 08:52:07 9: [2017-07-24 08:52:07.254892] mirserver: Mir version 0.27.0 08:52:07 9: [2017-07-24 08:52:07.423622] mirserver: Initial display configuration: 08:52:07 9: [2017-07-24 08:52:07.424162] mirserver: CMakeFiles CTestTestfile.cmake Makefile cmake_install.cmake mir_acceptance_tests_precompiled.hpp.gch precompiled.hpp.compileflags precompiled.hpp.compileflags.processed Output 1: VGA connected, used 08:52:07 9: [2017-07-24 08:52:07.424372] mirserver: . |_ Physical size 0.0" 0x0mm 08:52:07 9: [2017-07-24 08:52:07.424529] mirserver: . |_ Power is on 08:52:07 9: [2017-07-24 08:52:07.424717] mirserver: . |_ Current mode 640x480 60.00Hz 08:52:07 9: [2017-07-24 08:52:07.424895] mirserver: . |_ Preferred mode 640x480 60.00Hz 08:52:07 9: [2017-07-24 08:52:07.425049] mirserver: . |_ Orientation normal 08:52:07 9: [2017-07-24 08:52:07.425207] mirserver: . |_ Logical size 640x480 08:52:07 9: [2017-07-24 08:52:07.425361] mirserver: . |_ Logical position +0+0 08:52:07 9: [2017-07-24 08:52:07.425522] mirserver: . |_ Scaling factor: 1.00 08:52:07 9: [2017-07-24 08:52:07.743892] mirserver: Session (anonymous namespace)::Client::Client((anonymous namespace)::NestedMirRunner &) applied display configuration 08:52:07 9: [2017-07-24 08:52:07.744240] mirserver: CMakeFiles CTestTestfile.cmake Makefile cmake_install.cmake mir_acceptance_tests_precompiled.hpp.gch precompiled.hpp.compileflags precompiled.hpp.compileflags.processed Output 1: VGA connected, used 08:52:07 9: [2017-07-24 08:52:07.744437] mirserver: . |_ Physical size 0.0" 0x0mm 08:52:07 9: [2017-07-24 08:52:07.744594] mirserver: . |_ Power is on 08:52:07 9: [2017-07-24 08:52:07.744780] mirserver: . |_ Current mode 640x480 60.00Hz 08:52:07 9: [2017-07-24 08:52:07.744965] mirserver: . |_ Preferred mode 640x480 60.00Hz 08:52:07 9: [2017-07-24 08:52:07.745126] mirserver: . |_ Orientation normal 08:52:07 9: [2017-07-24 08:52:07.745289] mirserver: . |_ Logical size 640x480 08:52:07 9: [2017-07-24 08:52:07.745455] mirserver: . |_ Logical position +0+0 08:52:07 9: [2017-07-24 08:52:07.745646] mirserver: . |_ Scaling factor: 1.00 08:52:07 9: [2017-07-24 08:52:07.749309] mirserver: New display configuration: 08:52:07 9: [2017-07-24 08:52:07.749661] mirserver: CMakeFiles CTestTestfile.cmake Makefile cmake_install.cmake mir_acceptance_tests_precompiled.hpp.gch precompiled.hpp.compileflags precompiled.hpp.compileflags.processed Output 1: VGA connected, used 08:52:07 9: [2017-07-24 08:52:07.751157] mirserver: . |_ Physical size 0.0" 0x0mm 08:52:07 9: [2017-07-24 08:52:07.751446] mirserver: . |_ Power is on 08:5
[Touch-packages] [Bug 1613523] Re: [ FAILED ] NestedInput.nested_event_filter_receives_keyboard_from_host
*** This bug is a duplicate of bug 1523621 *** https://bugs.launchpad.net/bugs/1523621 ** This bug has been marked a duplicate of bug 1523621 [ FAILED ] NestedServer.*_cursor_* (usually NestedServer.named_cursor_image_changes_are_forwarded_to_host) -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to mir in Ubuntu. https://bugs.launchpad.net/bugs/1613523 Title: [ FAILED ] NestedInput.nested_event_filter_receives_keyboard_from_host Status in Mir: Triaged Status in mir package in Ubuntu: Triaged Bug description: Sounds like bug 1462033 but seems different... 06:57:59 [0;32m[ RUN ] [mNestedInput.nested_event_filter_receives_keyboard_from_host 06:57:59 unknown file: Failure 06:57:59 06:57:59 Unexpected mock function call - returning default value. 06:57:59 Function call: handle(key_event(when=529970166879 (1.635846ms ago), from=1, down, code=97, scan=30, modifiers=1)) 06:57:59 Returns: false 06:57:59 Google Mock tried the following 3 expectations, but none matched: 06:57:59 06:57:59 /build/mir-CSdSFG/mir-0.24.0+vivid1833bzr3644/tests/acceptance-tests/test_nested_input.cpp:195: tried expectation #0: EXPECT_CALL(nested_event_filter, handle(mt::InputDeviceStateEvent()))... 06:57:59 Expected arg #0: input device state event 06:57:59 Actual: key_event(when=529970166879 (1.214154ms ago), from=1, down, code=97, scan=30, modifiers=1) 06:57:59 Expected: to be called once 06:57:59 Actual: never called - unsatisfied and active 06:57:59 /build/mir-CSdSFG/mir-0.24.0+vivid1833bzr3644/tests/acceptance-tests/test_nested_input.cpp:196: tried expectation #1: EXPECT_CALL(nested_event_filter, handle(mt::KeyOfScanCode(30)))... 06:57:59 Expected: all pre-requisites are satisfied 06:57:59 Actual: the following immediate pre-requisites are not satisfied: 06:57:59 /build/mir-CSdSFG/mir-0.24.0+vivid1833bzr3644/tests/acceptance-tests/test_nested_input.cpp:195: pre-requisite #0 06:57:59 (end of pre-requisites) 06:57:59 Expected: to be called at least once 06:57:59 Actual: never called - unsatisfied and active 06:57:59 /build/mir-CSdSFG/mir-0.24.0+vivid1833bzr3644/tests/acceptance-tests/test_nested_input.cpp:200: tried expectation #2: EXPECT_CALL(nested_event_filter, handle(mt::KeyOfScanCode(54)))... 06:57:59 Expected arg #0: key of scan code 54 06:57:59 Actual: key_event(when=529970166879 (1.579538ms ago), from=1, down, code=97, scan=30, modifiers=1) 06:57:59 Expected: to be called twice 06:57:59 Actual: never called - unsatisfied and active 06:57:59 [0;31m[ FAILED ] [mNestedInput.nested_event_filter_receives_keyboard_from_host (200 ms) [https://mir-jenkins.ubuntu.com/job/device-runtests- mir/1323/device_type=krillin/consoleFull] To manage notifications about this bug go to: https://bugs.launchpad.net/mir/+bug/1613523/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1658057] Re: [testsfail] ClientStartupPerformance.create_surface_and_swap
This is an irrelevant scenario: running performance tests on contended CI infrastructure that we no longer support. ** Changed in: mir (Ubuntu) Status: New => Won't Fix -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to mir in Ubuntu. https://bugs.launchpad.net/bugs/1658057 Title: [testsfail] ClientStartupPerformance.create_surface_and_swap Status in Mir: New Status in mir package in Ubuntu: Won't Fix Bug description: Given the load on our test infrastructure I'm surprised I can't find this already logged. But a client takes over 80ms to connect and post a buffer... https://mir-jenkins.ubuntu.com/job/device-runtests- mir/device_type=krillin/2747/consoleFull 10:36:31 [0;32m[ RUN ] [mClientStartupPerformance.create_surface_and_swap 10:36:31 [2017-01-20 10:36:31.089258] mirplatform: Found graphics driver: mir:android (version 0.26.0) 10:36:31 [2017-01-20 10:36:31.090885] mirplatform: Found graphics driver: mir:mesa-kms (version 0.26.0) 10:36:31 [2017-01-20 10:36:31.091082] mirplatform: Found graphics driver: mir:mesa-x11 (version 0.26.0) 10:36:31 [2017-01-20 10:36:31.092267] mirplatform: Found graphics driver: mir:stub-graphics (version 0.26.0) 10:36:31 [2017-01-20 10:36:31.092741] mirplatform: Found graphics driver: throw-on-creation (version 0.26.0) 10:36:31 [2017-01-20 10:36:31.096670] mirserver: Starting 10:36:31 [2017-01-20 10:36:31.097695] mircommon: Loading modules from: /usr/lib/arm-linux-gnueabihf/mir/server-platform 10:36:31 [2017-01-20 10:36:31.098457] mircommon: Loading module: /usr/lib/arm-linux-gnueabihf/mir/server-platform/graphics-android.so.11 10:36:31 [2017-01-20 10:36:31.098880] mircommon: Loading module: /usr/lib/arm-linux-gnueabihf/mir/server-platform/graphics-mesa-kms.so.11 10:36:31 [2017-01-20 10:36:31.104742] mircommon: Loading module: /usr/lib/arm-linux-gnueabihf/mir/server-platform/server-mesa-x11.so.11 10:36:31 [2017-01-20 10:36:31.110790] mircommon: Loading module: /usr/lib/arm-linux-gnueabihf/mir/server-platform/graphics-android.so.10 10:36:31 [2017-01-20 10:36:31.116907] mircommon: Loading module: /usr/lib/arm-linux-gnueabihf/mir/server-platform/input-evdev.so.6 10:36:31 [2017-01-20 10:36:31.121861] mircommon: Loading module: /usr/lib/arm-linux-gnueabihf/mir/server-platform/input-evdev.so.5 10:36:31 [2017-01-20 10:36:31.125046] mircommon: Loading module: /usr/lib/arm-linux-gnueabihf/mir/server-platform/graphics-dummy.so 10:36:31 [2017-01-20 10:36:31.128620] mircommon: Loading module: /usr/lib/arm-linux-gnueabihf/mir/server-platform/input-stub.so 10:36:31 [2017-01-20 10:36:31.130851] mircommon: Loading module: /usr/lib/arm-linux-gnueabihf/mir/server-platform/graphics-throw.so 10:36:31 [2017-01-20 10:36:31.132587] mirplatform: Found graphics driver: mir:android (version 0.26.0) 10:36:31 [2017-01-20 10:36:31.133711] mirplatform: Found graphics driver: mir:mesa-kms (version 0.26.0) 10:36:31 [2017-01-20 10:36:31.134136] mirplatform: Found graphics driver: mir:mesa-x11 (version 0.26.0) 10:36:31 [2017-01-20 10:36:31.134788] mirplatform: Found graphics driver: mir:stub-graphics (version 0.26.0) 10:36:31 [2017-01-20 10:36:31.135002] mirplatform: Found graphics driver: throw-on-creation (version 0.26.0) 10:36:31 [2017-01-20 10:36:31.137188] mirserver: Selected driver: mir:android (version 0.26.0) 10:36:31 [2017-01-20 10:36:31.176824] android/server: Found 1 matching egl configs 10:36:31 [2017-01-20 10:36:31.177324] android/server: Android visual ID for selected display format : 5 10:36:31 [2017-01-20 10:36:31.177446] android/server: Selected Mir display format : 3 10:36:31 [2017-01-20 10:36:31.190619] mirserver: Using software cursor 10:36:31 [2017-01-20 10:36:31.236266] mircommon: Loading modules from: /usr/lib/arm-linux-gnueabihf/mir/server-platform 10:36:31 [2017-01-20 10:36:31.237058] mircommon: Loading module: /usr/lib/arm-linux-gnueabihf/mir/server-platform/graphics-android.so.11 10:36:31 [2017-01-20 10:36:31.237595] mircommon: Loading module: /usr/lib/arm-linux-gnueabihf/mir/server-platform/graphics-mesa-kms.so.11 10:36:31 [2017-01-20 10:36:31.242185] mircommon: Loading module: /usr/lib/arm-linux-gnueabihf/mir/server-platform/server-mesa-x11.so.11 10:36:31 [2017-01-20 10:36:31.250184] mircommon: Loading module: /usr/lib/arm-linux-gnueabihf/mir/server-platform/graphics-android.so.10 10:36:31 [2017-01-20 10:36:31.256677] mircommon: Loading module: /usr/lib/arm-linux-gnueabihf/mir/server-platform/input-evdev.so.6 10:36:31 [2017-01-20 10:36:31.286060] mirserver: Selected input driver: mir:evdev-input (version: 0.26.0) 10:36:31 [2017-01-20 10:36:31.286835] mirserver: Mir version 0.26.0 10:36:31 [2017-01-20 10:36:31.304172] GLRenderer: EGL vendor: Android 10:36:31 [2017-01-20 10:36:31.304679] GLRenderer: EGL version: 1.4 Android META-EGL 10:36:31 [2017-01-20 10:36:31.304808] GLRende
[Touch-packages] [Bug 1603145] Re: CI InputEvents failure in krillin
I don't think this ever happened anywhere but krillin, and that's history. ** Changed in: mir (Ubuntu) Status: Triaged => Incomplete ** Changed in: mir Assignee: Kevin DuBois (kdub) => (unassigned) -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to mir in Ubuntu. https://bugs.launchpad.net/bugs/1603145 Title: CI InputEvents failure in krillin Status in Mir: Triaged Status in mir package in Ubuntu: Incomplete Bug description: InputEvents from mir_privileged tests is failing with a segfault. CI logs: https://mir-jenkins.ubuntu.com/job/device-runtests- mir/device_type=krillin/1055/consoleFull To manage notifications about this bug go to: https://bugs.launchpad.net/mir/+bug/1603145/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1793755] Re: [FFe] Feature freeze exception for Mir 1.0
I thought sdl2 dropped the Mir dependency back in 18.04? It hasn't worked since the "Mir EGL" patch was dropped from mesa. Anyway, I have tested some SDL2 apps with Mir 1.0.0: On 16.04 where the SDL_VIDEODRIVER=mir option is still supported they work with it. On 18.04 and 18.10 they work with SDL_VIDEODRIVER=wayland. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to mir in Ubuntu. https://bugs.launchpad.net/bugs/1793755 Title: [FFe] Feature freeze exception for Mir 1.0 Status in mir package in Ubuntu: Triaged Bug description: We'd like to get Mir 1.0 into Cosmic. It has no rdepends in the archive, but is used *from* the archive for snap builds, and we want the latest release available there. (Somewhat surprisingly!) No ABI changes in this release. The debian/changelog is maintained by us; it's a good overview of the changes. The relevant sections are: - New features . [Wayland] A configuration mechanism to select the Wayland extensions . [Wayland] Support XDG shell stable . [Wayland] Improve protocol scanner . [libmiral] Display configuration file support . [libmiral] Make the pid of external clients available . [libmiral] Add DisplayConfiguration . [console] Ensure the_console_services() is constructed only once . [console] An option to select the ConsoleServices provider . [mir-demos] Move legacy binaries out of mir-demos package . [mir-test-tools] Drop internal test binaries from mir-test-tools package . [X11] Experimental X11 support via Xwayland - Bugs fixed: . [Wayland] creating a shell_surface should associate a role immediately. (Fixes #512) . [Wayland] Default for positioner gravity . [Wayland] Use miral test framework for wlcs tests . [Wayland] Send popup configure events . [Wayland] When setting the pointer cursor apply it. (Fixes #555) . [Wayland] Hook the OutputManager into display reconfiguration notifications. (Fixes #585) . [Wayland] Remove hard coded values for output geometry (screen orientation and pixel arrangement). (Fixes #601) . [miral-kiosk] Don't allow apps to specify size of "maximized" windows. (Fixes #454) . [Mir-on-X] Fixed keyboard grab issue on Arch. (Fixes #549) . [eglstream-kms] Platform re-enabled, but no GL client support . [console] Fix VT switching with LinuxVirtualTerminal. (Fixes #499) . [console] Avoid breaking X11 desktops that have not claimed the VT from logind. (Fixes #535, #539) . [console] LogindConsoleServices: Support VT switching. (Fixes #459) . [libmiral] Parents of the active window also have focus. (Fixes #522) . Fix "sanitize" builds . Racy shutdown in miral-tests and miral_wlcs_tests. (Fixes #543) . Fix a locale initialization crash on musl . [mesa] Use both id and drm_fd as output identifier for cursor buffer as we're not sure of the uniqueness of either. (Fixes #556) . [mesa] Disconnected hardware has no modes: invent a (slow) refresh rate. (Fixes #587) . [input] Guess output for touchscreen (works with one of each). (Fixes #605) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mir/+bug/1793755/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1662357] Re: Can't use lsb_release on Ubuntu Core 16
*** This bug is a duplicate of bug 1619420 *** https://bugs.launchpad.net/bugs/1619420 Hi, why this bug is invalid ? I just ran into it after upgrading from Ubuntu 18.04 to 20.04. After finding and applying with success the fix of @shiina, I downloaded the package lsb-release_11.0.1ubuntu1_all.deb, wich still contains the line RELEASES_ORDER.sort(key=lambda n: float(n[0])) in the file /usr/share/pyshared/lsb_release.py. So, it seems there's only 2 possibilities : - the bug is still here and nobody relies anymore on lsb_release ; - there is another problem somewhere in my system. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to lsb in Ubuntu. https://bugs.launchpad.net/bugs/1662357 Title: Can't use lsb_release on Ubuntu Core 16 Status in lsb: Invalid Status in Snappy: New Status in Snappy Ubuntu Core: New Status in lsb package in Ubuntu: Invalid Bug description: brian-murray@localhost:~$ snap list Name Version Rev Developer Notes core 16.04.1 888 canonical - brian-murray@localhost:~$ lsb_release Traceback (most recent call last): File "/usr/bin/lsb_release", line 95, in main() File "/usr/bin/lsb_release", line 59, in main distinfo = lsb_release.get_distro_information() File "/usr/lib/python3/dist-packages/lsb_release.py", line 383, in get_distro_information distinfo = guess_debian_release() File "/usr/lib/python3/dist-packages/lsb_release.py", line 281, in guess_debian_release get_distro_info(distinfo['ID']) File "/usr/lib/python3/dist-packages/lsb_release.py", line 41, in get_distro_info RELEASES_ORDER.sort(key=lambda n: float(n[0])) File "/usr/lib/python3/dist-packages/lsb_release.py", line 41, in RELEASES_ORDER.sort(key=lambda n: float(n[0])) ValueError: could not convert string to float: '16.04 LTS' brian-murray@localhost:~$ lsb_release -a Traceback (most recent call last): File "/usr/bin/lsb_release", line 95, in main() File "/usr/bin/lsb_release", line 59, in main distinfo = lsb_release.get_distro_information() File "/usr/lib/python3/dist-packages/lsb_release.py", line 383, in get_distro_information distinfo = guess_debian_release() File "/usr/lib/python3/dist-packages/lsb_release.py", line 281, in guess_debian_release get_distro_info(distinfo['ID']) File "/usr/lib/python3/dist-packages/lsb_release.py", line 41, in get_distro_info RELEASES_ORDER.sort(key=lambda n: float(n[0])) File "/usr/lib/python3/dist-packages/lsb_release.py", line 41, in RELEASES_ORDER.sort(key=lambda n: float(n[0])) ValueError: could not convert string to float: '6.06 LTS' To manage notifications about this bug go to: https://bugs.launchpad.net/lsb/+bug/1662357/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1889166] Re: mir: build failure on s390x
Looking at the code, it is written correctly and handles the case where strncpy() "truncates before the terminating nul". It is unfortunate that this triggers a warning. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to mir in Ubuntu. https://bugs.launchpad.net/bugs/1889166 Title: mir: build failure on s390x Status in mir package in Ubuntu: New Bug description: Hello, looks like we are missing one "+1" from somewhere, but I don't have enough knowledge on this code... can you please have a look? in the meanwhile I'm probably going to disable that error cd /<>/build-s390x/src/miral && /usr/bin/cc -DBOOST_ALL_NO_LIB -DBOOST_DATE_TIME_DYN_LINK -DBOOST_FILESYSTEM_DYN_LINK -DBOOST_IOSTREAMS_DYN_LINK -DBOOST_PROGRAM_OPTIONS_DYN_LINK -DBOOST_SYSTEM_DYN_LINK -DEGL_NO_X11 -DLOG_NDEBUG=1 -DLTTNG_UST_HAVE_SDT_INTEGRATION -DMESA_EGL_NO_X11_HEADERS -DMIR_DRMMODEADDFB_HAS_CONST_SIGNATURE -DMIR_LOG_COMPONENT_FALLBACK=\"miral\" -DMIR_SERVER_EGL_OPENGL_API=EGL_OPENGL_ES_API -DMIR_SERVER_EGL_OPENGL_BIT=EGL_OPENGL_ES2_BIT -DMIR_SERVER_GLEXT_H="" -DMIR_SERVER_GL_H="" -DMIR_VERSION_MAJOR=1 -DMIR_VERSION_MICRO=1 -DMIR_VERSION_MINOR=7 -D_FILE_OFFSET_BITS=64 -D_GNU_SOURCE -D_GNU_SOURCE -I/<>/include/core -I/<>/include/common -I/<>/include/cookie -I/<>/src/include/common -I/<>/build-s390x/src/capnproto -I/<>/build-s390x/src/protobuf -I/<>/include/platform -I/<>/include/client -I/<>/include/server -I/<>/src/include/platform -I/<>/include/miral -I/usr/include/uuid -I/<>/include/wayland -I/<>/src/wayland/generated -g -O2 -fdebug-prefix-map=/<>=. -fstack-protector-strong -Wformat -Werror=format-security -Wdate-time -D_FORTIFY_SOURCE=2 -pthread -g -Wall -pedantic -Wextra -fPIC -Werror -flto -ffat-lto-objects -fvisibility=hidden -pthread -o CMakeFiles/miral-internal.dir/xcursor.c.o -c /<>/src/miral/xcursor.c In file included from /usr/include/string.h:495, from /<>/src/miral/xcursor.c:26: In function ‘strncpy’, inlined from ‘_XcursorAddPathElt’ at /<>/src/miral/xcursor.c:647:5, inlined from ‘_XcursorBuildFullname’ at /<>/src/miral/xcursor.c:726:5, inlined from ‘xcursor_load_theme’ at /<>/src/miral/xcursor.c:875:10: /usr/include/s390x-linux-gnu/bits/string_fortified.h:106:10: error: ‘strncpy’ output truncated before terminating nul copying 7 bytes from a string of the same length [-Werror=stringop-truncation] 106 | return __builtin___strncpy_chk (__dest, __src, __len, __bos (__dest)); | ^~ In function ‘strncpy’, inlined from ‘_XcursorAddPathElt’ at /<>/src/miral/xcursor.c:647:5, inlined from ‘_XcursorBuildFullname’ at /<>/src/miral/xcursor.c:727:5, inlined from ‘xcursor_load_theme’ at /<>/src/miral/xcursor.c:884:11: /usr/include/s390x-linux-gnu/bits/string_fortified.h:106:10: error: ‘strncpy’ output truncated before terminating nul copying 11 bytes from a string of the same length [-Werror=stringop-truncation] 106 | return __builtin___strncpy_chk (__dest, __src, __len, __bos (__dest)); | ^~ cc1: all warnings being treated as errors make[3]: *** [src/miral/CMakeFiles/miral-internal.dir/build.make:183: src/miral/CMakeFiles/miral-internal.dir/xcursor.c.o] Error 1 make[3]: *** Waiting for unfinished jobs To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mir/+bug/1889166/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1929376] [NEW] freezes on 'searching for drivers'
Public bug reported: change [printer] driver selected. then 'select printer from data base' clicked. freezes on 'searching for drivers'. choice to 'force quit' or 'wait' appears but 'searching for drivers ' message freezes over the 'force quit/wait' message. ProblemType: Bug DistroRelease: Ubuntu 20.10 Package: cups 2.3.3-3ubuntu1 ProcVersionSignature: Ubuntu 5.8.0-54.61-generic 5.8.18 Uname: Linux 5.8.0-54-generic x86_64 ApportVersion: 2.20.11-0ubuntu50.6 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Mon May 24 17:48:25 2021 InstallationDate: Installed on 2018-05-10 (1110 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426) KernLog: Lpstat: device for HP_OfficeJet_8010_series_747033_: implicitclass://HP_OfficeJet_8010_series_747033_/ device for HP_OfficeJet_Pro_6970_C04CF1_USB_: hp:/usb/OfficeJet_Pro_6970?serial=TH6C753105 device for MG5400-series: usb://Canon/MG5400%20series?serial=30D4AD&interface=1 MachineType: Hewlett-Packard 220-1010a Papersize: a4 PpdFiles: Error: command ['fgrep', '-H', '*NickName', '/etc/cups/ppd/MG5400-series.ppd', '/etc/cups/ppd/HP_OfficeJet_8010_series_747033_.ppd', '/etc/cups/ppd/HP_OfficeJet_Pro_6970_C04CF1_USB_.ppd'] failed with exit code 2: grep: /etc/cups/ppd/MG5400-series.ppd: Permission denied grep: /etc/cups/ppd/HP_OfficeJet_8010_series_747033_.ppd: Permission denied grep: /etc/cups/ppd/HP_OfficeJet_Pro_6970_C04CF1_USB_.ppd: Permission denied ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_NZ.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.8.0-54-generic root=UUID=3675aa14-c77b-4e55-9fe8-fb9631834d4b ro quiet splash vt.handoff=7 SourcePackage: cups UpgradeStatus: Upgraded to groovy on 2021-02-26 (86 days ago) dmi.bios.date: 07/21/2011 dmi.bios.release: 7.2 dmi.bios.vendor: AMI dmi.bios.version: 7.02 dmi.board.asset.tag: 3CR1351T4R dmi.board.name: 2AC3 dmi.board.vendor: PEGATRON CORPORATION dmi.board.version: 1.02A dmi.chassis.asset.tag: 3CR1351T4R dmi.chassis.type: 3 dmi.chassis.vendor: Hewlett-Packard dmi.modalias: dmi:bvnAMI:bvr7.02:bd07/21/2011:br7.2:svnHewlett-Packard:pn220-1010a:pvr1.02A:rvnPEGATRONCORPORATION:rn2AC3:rvr1.02A:cvnHewlett-Packard:ct3:cvr: dmi.product.family: 103C_53316J G=D dmi.product.name: 220-1010a dmi.product.sku: QU221AA#ABG dmi.product.version: 1.02A dmi.sys.vendor: Hewlett-Packard ** Affects: cups (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug groovy -- 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/1929376 Title: freezes on 'searching for drivers' Status in cups package in Ubuntu: New Bug description: change [printer] driver selected. then 'select printer from data base' clicked. freezes on 'searching for drivers'. choice to 'force quit' or 'wait' appears but 'searching for drivers ' message freezes over the 'force quit/wait' message. ProblemType: Bug DistroRelease: Ubuntu 20.10 Package: cups 2.3.3-3ubuntu1 ProcVersionSignature: Ubuntu 5.8.0-54.61-generic 5.8.18 Uname: Linux 5.8.0-54-generic x86_64 ApportVersion: 2.20.11-0ubuntu50.6 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Mon May 24 17:48:25 2021 InstallationDate: Installed on 2018-05-10 (1110 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426) KernLog: Lpstat: device for HP_OfficeJet_8010_series_747033_: implicitclass://HP_OfficeJet_8010_series_747033_/ device for HP_OfficeJet_Pro_6970_C04CF1_USB_: hp:/usb/OfficeJet_Pro_6970?serial=TH6C753105 device for MG5400-series: usb://Canon/MG5400%20series?serial=30D4AD&interface=1 MachineType: Hewlett-Packard 220-1010a Papersize: a4 PpdFiles: Error: command ['fgrep', '-H', '*NickName', '/etc/cups/ppd/MG5400-series.ppd', '/etc/cups/ppd/HP_OfficeJet_8010_series_747033_.ppd', '/etc/cups/ppd/HP_OfficeJet_Pro_6970_C04CF1_USB_.ppd'] failed with exit code 2: grep: /etc/cups/ppd/MG5400-series.ppd: Permission denied grep: /etc/cups/ppd/HP_OfficeJet_8010_series_747033_.ppd: Permission denied grep: /etc/cups/ppd/HP_OfficeJet_Pro_6970_C04CF1_USB_.ppd: Permission denied ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_NZ.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.8.0-54-generic root=UUID=3675aa14-c77b-4e55-9fe8-fb9631834d4b ro quiet splash vt.handoff=7 SourcePackage: cups UpgradeStatus: Upgraded to groovy on 2021-02-26 (86 days ago) dmi.bios.date: 07/21/2011 dmi.bios.release: 7.2 dmi.bios.vendor: AMI dmi.bios.version: 7.02 dmi.board.asset.tag: 3CR1351T4R dmi.board.name: 2AC3 dmi.board.vendor: PEGATRON CORPORATION dmi.board.version: 1.02A dmi.chassis.asset.tag: 3CR1351T4R dmi.chassis.type: 3 dmi.chassis.vendor
[Touch-packages] [Bug 1899103] [NEW] libpam-cap causes PAM applications to crash
Public bug reported: Install ocserv and setup for PAM authentication. On second connection, ocserv crashes due to a double free in PAM. Repro steps: 1. Create Dockerfile that installs ocserv + libpam-cap ``` FROM ubuntu:20.04 RUN apt update && apt install -y ocserv libpam-cap && apt autoremove && apt clean COPY server-cert.pem /etc/ssl/ocserv_test.cert COPY server-key.pem /etc/ssl/ocserv_test.key COPY ca-cert.pem /etc/ssl/certs/ssl-cert-snakeoil.pem COPY ocserv.conf /etc/ocserv/ocserv.conf RUN useradd test RUN echo "test\ntest" | passwd test ENV MALLOC_CHECK_=3 CMD ocserv -f -d 1 ``` 2. Build container: ``` sudo docker build -t ocserv:20.04 . ``` 3. Launch container: ``` docker run -p 443:443/tcp -p 443:443/udp -it --rm --device /dev/net/tun --cap-add net_admin ocserv:20.04 ``` 4. From another console, connect / disconnect: ``` while true; do echo test | openconnect https://localhost -u test --passwd-on-stdin --servercert pin-sha256:qBLVTyoXiFdn+0pW+eSGqnVCEnMbLigVf5vAl1ZewW4= --background && sleep 2 && pkill openconnect && sleep 2;done ``` 5. ocserv crashes: free(): invalid pointer ocserv[8]: main: main-sec-mod-cmd.c:106: command socket for sec-mod closed ocserv[8]: main: main.c:1179: error in command from sec-mod ocserv[8]: main: termination request received; waiting for children to die For more details see: https://gitlab.com/openconnect/ocserv/-/issues/361 ** Affects: libcap2 (Ubuntu) Importance: Undecided Status: New ** Attachment added: "Self-contained repro of the failure in the form of Dockerfile + config + certs" https://bugs.launchpad.net/bugs/1899103/+attachment/5419801/+files/repro.tgz -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to libcap2 in Ubuntu. https://bugs.launchpad.net/bugs/1899103 Title: libpam-cap causes PAM applications to crash Status in libcap2 package in Ubuntu: New Bug description: Install ocserv and setup for PAM authentication. On second connection, ocserv crashes due to a double free in PAM. Repro steps: 1. Create Dockerfile that installs ocserv + libpam-cap ``` FROM ubuntu:20.04 RUN apt update && apt install -y ocserv libpam-cap && apt autoremove && apt clean COPY server-cert.pem /etc/ssl/ocserv_test.cert COPY server-key.pem /etc/ssl/ocserv_test.key COPY ca-cert.pem /etc/ssl/certs/ssl-cert-snakeoil.pem COPY ocserv.conf /etc/ocserv/ocserv.conf RUN useradd test RUN echo "test\ntest" | passwd test ENV MALLOC_CHECK_=3 CMD ocserv -f -d 1 ``` 2. Build container: ``` sudo docker build -t ocserv:20.04 . ``` 3. Launch container: ``` docker run -p 443:443/tcp -p 443:443/udp -it --rm --device /dev/net/tun --cap-add net_admin ocserv:20.04 ``` 4. From another console, connect / disconnect: ``` while true; do echo test | openconnect https://localhost -u test --passwd-on-stdin --servercert pin-sha256:qBLVTyoXiFdn+0pW+eSGqnVCEnMbLigVf5vAl1ZewW4= --background && sleep 2 && pkill openconnect && sleep 2;done ``` 5. ocserv crashes: free(): invalid pointer ocserv[8]: main: main-sec-mod-cmd.c:106: command socket for sec-mod closed ocserv[8]: main: main.c:1179: error in command from sec-mod ocserv[8]: main: termination request received; waiting for children to die For more details see: https://gitlab.com/openconnect/ocserv/-/issues/361 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libcap2/+bug/1899103/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1901929] [NEW] [MS-7693, Realtek ALC1150, SPDIF Out, Internal] No sound at all
Public bug reported: Hi. I am new to ubuntu. I had sound at first then it just disappeared. I have tried to fix it. Note: When I woke ubuntu from sleep it would have no sound until I rebooted. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: alsa-base 1.0.25+dfsg-0ubuntu5 Uname: Linux 5.6.0-050600-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.10 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: alan 47711 F pulseaudio /dev/snd/controlC0: alan 47711 F pulseaudio /dev/snd/pcmC0D1p: alan 47711 F...m pulseaudio /dev/snd/controlC2: alan 47711 F pulseaudio CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Wed Oct 28 17:32:40 2020 PackageArchitecture: all SourcePackage: alsa-driver Symptom: audio Symptom_AlsaPlaybackTest: ALSA playback test through plughw:SB failed Symptom_Card: Built-in Audio - HDA ATI SB Symptom_DevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: alan 47711 F pulseaudio /dev/snd/controlC0: alan 47711 F pulseaudio /dev/snd/pcmC0D1p: alan 47711 F...m pulseaudio /dev/snd/controlC2: alan 47711 F pulseaudio Symptom_Jack: SPDIF Out, Internal Symptom_Type: No sound at all Title: [MS-7693, Realtek ALC1150, SPDIF Out, Internal] No sound at all UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 12/21/2015 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: V22.4 dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: 970 GAMING (MS-7693) dmi.board.vendor: MSI dmi.board.version: 4.0 dmi.chassis.asset.tag: To Be Filled By O.E.M. dmi.chassis.type: 3 dmi.chassis.vendor: MSI dmi.chassis.version: 4.0 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrV22.4:bd12/21/2015:svnMSI:pnMS-7693:pvr4.0:rvnMSI:rn970GAMING(MS-7693):rvr4.0:cvnMSI:ct3:cvr4.0: dmi.product.family: To be filled by O.E.M. dmi.product.name: MS-7693 dmi.product.sku: To be filled by O.E.M. dmi.product.version: 4.0 dmi.sys.vendor: MSI mtime.conffile..etc.modprobe.d.alsa-base.conf: 2020-10-28T16:45:58.098082 ** Affects: alsa-driver (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug focal -- 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/1901929 Title: [MS-7693, Realtek ALC1150, SPDIF Out, Internal] No sound at all Status in alsa-driver package in Ubuntu: New Bug description: Hi. I am new to ubuntu. I had sound at first then it just disappeared. I have tried to fix it. Note: When I woke ubuntu from sleep it would have no sound until I rebooted. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: alsa-base 1.0.25+dfsg-0ubuntu5 Uname: Linux 5.6.0-050600-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.10 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: alan 47711 F pulseaudio /dev/snd/controlC0: alan 47711 F pulseaudio /dev/snd/pcmC0D1p: alan 47711 F...m pulseaudio /dev/snd/controlC2: alan 47711 F pulseaudio CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Wed Oct 28 17:32:40 2020 PackageArchitecture: all SourcePackage: alsa-driver Symptom: audio Symptom_AlsaPlaybackTest: ALSA playback test through plughw:SB failed Symptom_Card: Built-in Audio - HDA ATI SB Symptom_DevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: alan 47711 F pulseaudio /dev/snd/controlC0: alan 47711 F pulseaudio /dev/snd/pcmC0D1p: alan 47711 F...m pulseaudio /dev/snd/controlC2: alan 47711 F pulseaudio Symptom_Jack: SPDIF Out, Internal Symptom_Type: No sound at all Title: [MS-7693, Realtek ALC1150, SPDIF Out, Internal] No sound at all UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 12/21/2015 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: V22.4 dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: 970 GAMING (MS-7693) dmi.board.vendor: MSI dmi.board.version: 4.0 dmi.chassis.asset.tag: To Be Filled By O.E.M. dmi.chassis.type: 3 dmi.chassis.vendor: MSI dmi.chassis.version: 4.0 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrV22.4:bd12/21/2015:svnMSI:pnMS-7693:pvr4.0:rvnMSI:rn970GAMING(MS-7693):rvr4.0:cvnMSI:ct3:cvr4.0: dmi.product.family: To be filled by O.E.M. dmi.product.name: MS-7693 dmi.product.sku: To be filled by O.E.M. dmi.product.version: 4.0 dmi.sys.vendor: MSI mtime.conffile..etc.modprobe.d.alsa-base.conf: 2020-10-28T16:45:58.098082 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1901929/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More
[Touch-packages] [Bug 1901929] Re: [MS-7693, Realtek ALC1150, SPDIF Out, Internal] No sound at all
Reinstalling Ubuntu. Thanks. -- 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/1901929 Title: [MS-7693, Realtek ALC1150, SPDIF Out, Internal] No sound at all Status in alsa-driver package in Ubuntu: New Bug description: Hi. I am new to ubuntu. I had sound at first then it just disappeared. I have tried to fix it. Note: When I woke ubuntu from sleep it would have no sound until I rebooted. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: alsa-base 1.0.25+dfsg-0ubuntu5 Uname: Linux 5.6.0-050600-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.10 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: alan 47711 F pulseaudio /dev/snd/controlC0: alan 47711 F pulseaudio /dev/snd/pcmC0D1p: alan 47711 F...m pulseaudio /dev/snd/controlC2: alan 47711 F pulseaudio CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Wed Oct 28 17:32:40 2020 PackageArchitecture: all SourcePackage: alsa-driver Symptom: audio Symptom_AlsaPlaybackTest: ALSA playback test through plughw:SB failed Symptom_Card: Built-in Audio - HDA ATI SB Symptom_DevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: alan 47711 F pulseaudio /dev/snd/controlC0: alan 47711 F pulseaudio /dev/snd/pcmC0D1p: alan 47711 F...m pulseaudio /dev/snd/controlC2: alan 47711 F pulseaudio Symptom_Jack: SPDIF Out, Internal Symptom_Type: No sound at all Title: [MS-7693, Realtek ALC1150, SPDIF Out, Internal] No sound at all UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 12/21/2015 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: V22.4 dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: 970 GAMING (MS-7693) dmi.board.vendor: MSI dmi.board.version: 4.0 dmi.chassis.asset.tag: To Be Filled By O.E.M. dmi.chassis.type: 3 dmi.chassis.vendor: MSI dmi.chassis.version: 4.0 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrV22.4:bd12/21/2015:svnMSI:pnMS-7693:pvr4.0:rvnMSI:rn970GAMING(MS-7693):rvr4.0:cvnMSI:ct3:cvr4.0: dmi.product.family: To be filled by O.E.M. dmi.product.name: MS-7693 dmi.product.sku: To be filled by O.E.M. dmi.product.version: 4.0 dmi.sys.vendor: MSI mtime.conffile..etc.modprobe.d.alsa-base.conf: 2020-10-28T16:45:58.098082 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1901929/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1889166] Re: mir: build failure on s390x
In src/miral/CMakeLists.txt Change: set_source_files_properties(xcursor.c PROPERTIES COMPILE_DEFINITIONS _GNU_SOURCE) to set_source_files_properties(xcursor.c PROPERTIES COMPILE_DEFINITIONS _GNU_SOURCE COMPILE_FLAGS "-Wno-error=stringop-truncation" ) -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to mir in Ubuntu. https://bugs.launchpad.net/bugs/1889166 Title: mir: build failure on s390x Status in mir package in Ubuntu: New Bug description: Hello, looks like we are missing one "+1" from somewhere, but I don't have enough knowledge on this code... can you please have a look? in the meanwhile I'm probably going to disable that error cd /<>/build-s390x/src/miral && /usr/bin/cc -DBOOST_ALL_NO_LIB -DBOOST_DATE_TIME_DYN_LINK -DBOOST_FILESYSTEM_DYN_LINK -DBOOST_IOSTREAMS_DYN_LINK -DBOOST_PROGRAM_OPTIONS_DYN_LINK -DBOOST_SYSTEM_DYN_LINK -DEGL_NO_X11 -DLOG_NDEBUG=1 -DLTTNG_UST_HAVE_SDT_INTEGRATION -DMESA_EGL_NO_X11_HEADERS -DMIR_DRMMODEADDFB_HAS_CONST_SIGNATURE -DMIR_LOG_COMPONENT_FALLBACK=\"miral\" -DMIR_SERVER_EGL_OPENGL_API=EGL_OPENGL_ES_API -DMIR_SERVER_EGL_OPENGL_BIT=EGL_OPENGL_ES2_BIT -DMIR_SERVER_GLEXT_H="" -DMIR_SERVER_GL_H="" -DMIR_VERSION_MAJOR=1 -DMIR_VERSION_MICRO=1 -DMIR_VERSION_MINOR=7 -D_FILE_OFFSET_BITS=64 -D_GNU_SOURCE -D_GNU_SOURCE -I/<>/include/core -I/<>/include/common -I/<>/include/cookie -I/<>/src/include/common -I/<>/build-s390x/src/capnproto -I/<>/build-s390x/src/protobuf -I/<>/include/platform -I/<>/include/client -I/<>/include/server -I/<>/src/include/platform -I/<>/include/miral -I/usr/include/uuid -I/<>/include/wayland -I/<>/src/wayland/generated -g -O2 -fdebug-prefix-map=/<>=. -fstack-protector-strong -Wformat -Werror=format-security -Wdate-time -D_FORTIFY_SOURCE=2 -pthread -g -Wall -pedantic -Wextra -fPIC -Werror -flto -ffat-lto-objects -fvisibility=hidden -pthread -o CMakeFiles/miral-internal.dir/xcursor.c.o -c /<>/src/miral/xcursor.c In file included from /usr/include/string.h:495, from /<>/src/miral/xcursor.c:26: In function ‘strncpy’, inlined from ‘_XcursorAddPathElt’ at /<>/src/miral/xcursor.c:647:5, inlined from ‘_XcursorBuildFullname’ at /<>/src/miral/xcursor.c:726:5, inlined from ‘xcursor_load_theme’ at /<>/src/miral/xcursor.c:875:10: /usr/include/s390x-linux-gnu/bits/string_fortified.h:106:10: error: ‘strncpy’ output truncated before terminating nul copying 7 bytes from a string of the same length [-Werror=stringop-truncation] 106 | return __builtin___strncpy_chk (__dest, __src, __len, __bos (__dest)); | ^~ In function ‘strncpy’, inlined from ‘_XcursorAddPathElt’ at /<>/src/miral/xcursor.c:647:5, inlined from ‘_XcursorBuildFullname’ at /<>/src/miral/xcursor.c:727:5, inlined from ‘xcursor_load_theme’ at /<>/src/miral/xcursor.c:884:11: /usr/include/s390x-linux-gnu/bits/string_fortified.h:106:10: error: ‘strncpy’ output truncated before terminating nul copying 11 bytes from a string of the same length [-Werror=stringop-truncation] 106 | return __builtin___strncpy_chk (__dest, __src, __len, __bos (__dest)); | ^~ cc1: all warnings being treated as errors make[3]: *** [src/miral/CMakeFiles/miral-internal.dir/build.make:183: src/miral/CMakeFiles/miral-internal.dir/xcursor.c.o] Error 1 make[3]: *** Waiting for unfinished jobs To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mir/+bug/1889166/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1523621] Re: [ FAILED ] NestedServer.*_cursor_* (usually NestedServer.named_cursor_image_changes_are_forwarded_to_host)
** Changed in: mir (Ubuntu) Status: In Progress => Invalid ** Changed in: mir Status: Triaged => Invalid -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to mir in Ubuntu. https://bugs.launchpad.net/bugs/1523621 Title: [ FAILED ] NestedServer.*_cursor_* (usually NestedServer.named_cursor_image_changes_are_forwarded_to_host) Status in Mir: Invalid Status in mir package in Ubuntu: Invalid Bug description: while bin/mir_acceptance_tests --gtest_filter=NestedServer.named_cursor_image_changes_are_forwarded_to_host; do :; done fails after a few hundred iterations. NB There two are other tests that are probably manifesting the same underlying issue: NestedServer.can_hide_the_host_cursor NestedServer.animated_cursor_image_changes_are_forwarded_to_host To manage notifications about this bug go to: https://bugs.launchpad.net/mir/+bug/1523621/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1728581] Re: "mir_demo_server --help" does not show help text
** Changed in: mir Status: In Progress => Fix Released -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to mir in Ubuntu. https://bugs.launchpad.net/bugs/1728581 Title: "mir_demo_server --help" does not show help text Status in Mir: Fix Released Status in mir package in Ubuntu: Fix Released Bug description: $ mir_demo_server --help Expect: help text output to console Actual: platforms are listed and program exits To manage notifications about this bug go to: https://bugs.launchpad.net/mir/+bug/1728581/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1669524] Re: GTK window functions `Always on Top, Move and Resize' don't work in Mir/Unity8
gtk-mir is no longer a thing ** No longer affects: unity8 (Ubuntu) ** No longer affects: qtmir (Ubuntu) ** No longer affects: mir (Ubuntu) ** No longer affects: gtk+3.0 (Ubuntu) ** No longer affects: miral ** No longer affects: mir ** Changed in: canonical-devices-system-image Status: In Progress => Invalid -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to gtk+3.0 in Ubuntu. https://bugs.launchpad.net/bugs/1669524 Title: GTK window functions `Always on Top, Move and Resize' don't work in Mir/Unity8 Status in Canonical System Image: Invalid Bug description: ubuntu 17.04 unity8 [unity8] Always on Top, Move and Resize doesn't work open solitaire, right click on the title bar (see attachement) and then select Always on Top. the app doesn't stay on top. same with Move and Resize, does nothing To manage notifications about this bug go to: https://bugs.launchpad.net/canonical-devices-system-image/+bug/1669524/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1728931] Re: [testsfail] ServerDisconnect.is_detected_by_client
** Changed in: mir (Ubuntu) Status: In Progress => Invalid ** Changed in: mir Status: In Progress => Invalid -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to mir in Ubuntu. https://bugs.launchpad.net/bugs/1728931 Title: [testsfail] ServerDisconnect.is_detected_by_client Status in Mir: Invalid Status in mir package in Ubuntu: Invalid Bug description: [ RUN ] ServerDisconnect.is_detected_by_client [2017-10-27 21:38:41.897919] mirserver: Starting [2017-10-27 21:38:41.898180] mirserver: Selected driver: mir:stub-graphics (version 0.28.1) [2017-10-27 21:38:41.908376] mirserver: Using software cursor [2017-10-27 21:38:41.912088] mirserver: Selected input driver: mir:stub-input (version: 0.28.1) [2017-10-27 21:38:41.920187] mirserver: No WaylandAllocator EGL support! error: XDG_RUNTIME_DIR not set in the environment [2017-10-27 21:38:41.922664] mirserver: Mir version 0.28.1 [2017-10-27 21:38:41.923122] mirserver: Initial display configuration: [2017-10-27 21:38:41.923141] mirserver: CTestConfig.cmake CTestTestfile.cmake mir_acceptance_tests.bin_10.xml mir_acceptance_tests.bin_11.xml mir_acceptance_tests.bin_1.xml mir_acceptance_tests.bin_2.xml mir_acceptance_tests.bin_3.xml mir_acceptance_tests.bin_4.xml mir_acceptance_tests.bin_5.xml mir_acceptance_tests.bin_6.xml mir_acceptance_tests.bin_7.xml mir_acceptance_tests.bin_8.xml mir_acceptance_tests.bin_9.xml mir_acceptance_tests.bin.xml steer.cmake Testing Output 1: VGA connected, used [2017-10-27 21:38:41.923157] mirserver: . |_ Physical size 0.0" 0x0mm [2017-10-27 21:38:41.923162] mirserver: . |_ Power is on [2017-10-27 21:38:41.923167] mirserver: . |_ Current mode 1600x1600 60.00Hz [2017-10-27 21:38:41.923172] mirserver: . |_ Preferred mode 1600x1600 60.00Hz [2017-10-27 21:38:41.923175] mirserver: . |_ Orientation normal [2017-10-27 21:38:41.923181] mirserver: . |_ Logical size 1600x1600 [2017-10-27 21:38:41.923184] mirserver: . |_ Logical position +0+0 [2017-10-27 21:38:41.923188] mirserver: . |_ Scaling factor: 1.00 [2017-10-27 21:38:41.940284] mirserver: Stopping /spread/mir/tests/mir_test_framework/interprocess_client_server_test.cpp:167: Failure Value of: result.exit_code Expected: is equal to 0 Actual: 1 (of type int) [2017-10-27 21:38:41.953366] MirWindowAPI: Caught exception at client library boundary (in window_release_helper): /spread/mir/src/client/rpc/stream_socket_transport.cpp(168): Throw in function virtual void mir::client::rpc::StreamSocketTransport::send_message(const std::vector&, const std::vector&) Dynamic exception type: boost::exception_detail::clone_impl > std::exception::what: Failed to send message to server: Broken pipe 32, "Broken pipe" [2017-10-27 21:38:41.953754] MirConnectionAPI: Caught exception at client library boundary (in mir_connection_release): /spread/mir/src/client/rpc/stream_socket_transport.cpp(168): Throw in function virtual void mir::client::rpc::StreamSocketTransport::send_message(const std::vector&, const std::vector&) Dynamic exception type: boost::exception_detail::clone_impl > std::exception::what: Failed to send message to server: Broken pipe 32, "Broken pipe" [ FAILED ] ServerDisconnect.is_detected_by_client (58 ms) To manage notifications about this bug go to: https://bugs.launchpad.net/mir/+bug/1728931/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1420334] Re: [enhancement] Missing client API for relative surface movement (e.g. dragging client-decorated windows)
** Changed in: miral Status: In Progress => Won't Fix -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to mir in Ubuntu. https://bugs.launchpad.net/bugs/1420334 Title: [enhancement] Missing client API for relative surface movement (e.g. dragging client-decorated windows) Status in Mir: Fix Released Status in MirAL: Won't Fix Status in mir package in Ubuntu: Fix Released Status in xorg-server package in Ubuntu: Won't Fix Bug description: Mir needs a client API to allow surfaces to move themselves relatively. This is required to support full client-side decorations (bug 1398849), and also other apps like Google Chrome and Gnome Nautilus which can be dragged using part of their client areas. Later additions that are so similar I think they are part of the same bug: there need to be client APIs for "always on top" and "client initiate resize". To manage notifications about this bug go to: https://bugs.launchpad.net/mir/+bug/1420334/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1945894] [NEW] Translated strings not imported from damned lies
Public bug reported: The newly translated strings in GTK does not seem to be imported from Damned Lies. GTK in Ubuntu has 50 untranslated strings in Danish but is fully translated in Damned Lies. ** Affects: gtk+3.0 (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to gtk+3.0 in Ubuntu. https://bugs.launchpad.net/bugs/1945894 Title: Translated strings not imported from damned lies Status in gtk+3.0 package in Ubuntu: New Bug description: The newly translated strings in GTK does not seem to be imported from Damned Lies. GTK in Ubuntu has 50 untranslated strings in Danish but is fully translated in Damned Lies. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gtk+3.0/+bug/1945894/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1958389]
HJ, you likely can reproduce the failue with an asan build of binutils, or using MALLOC_PERTURB_. I haven't tested the patch yet. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to binutils in Ubuntu. https://bugs.launchpad.net/bugs/1958389 Title: Jammy builds of xen segfault, but only on launchpad x86 builders Status in binutils: In Progress Status in launchpad-buildd: New Status in binutils package in Ubuntu: New Status in xen package in Ubuntu: Invalid Status in binutils source package in Jammy: New Status in xen source package in Jammy: Invalid Status in binutils package in Debian: New Bug description: FTBFS in Jammy on LP infra: https://launchpadlibrarian.net/580924961/buildlog_ubuntu-jammy-amd64.xen_4.16.0-1~ubuntu1~jammyppa4_BUILDING.txt.gz https://launchpadlibrarian.net/581060687/buildlog_ubuntu-jammy-amd64.xen_4.16.0-1~ubuntu1~jammyppa6_BUILDING.txt.gz Related PPA: https://launchpad.net/~ci-train-ppa-service/+archive/ubuntu/4760/+packages Summary: - Build reliably fails on LP - Build in local sbuild works reliably on my Laptop - Build in local VM (sizing like LP builders) works (other crashes but works) - Build on AMD server (chip more similar to LP) works reliably Failing step: On Launchpad build infrastructure it breaks on ld: $ x86_64-linux-gnu-ld -mi386pep --subsystem=10 --image-base=0x82d04000 --stack=0,0 --heap=0,0 --section-alignment=0x20 --file-alignment=0x20 --major-image-version=4 --minor-image-version=16 --major-os-version=2 --minor-os-version=0 --major-subsystem-version=2 --minor-subsystem-version=0 --no-insert-timestamp --build-id=sha1 -T efi.lds -N prelink.o /<>/xen/common/symbols-dummy.o -b pe-x86-64 efi/buildid.o -o /<>/xen/.xen.efi.0x82d04000.0 && : Segmentation fault (core dumped --- Steps to recreate (result depends on platform) # you can grab the package from https://launchpad.net/~ci-train-ppa- service/+archive/ubuntu/4760/+packages sudo vim /etc/apt/sources.list sudo apt update sudo apt dist-upgrade -y sudo apt build-dep xen sudo apt install flex bison python3-dev libpython3-dev dpkg-dev devscripts apport-retrace sudo mkdir /mnt/build sudo chmod go+w /mnt/build cd /mnt/build # copy in things from host scp xen_4.16.0-1~ubuntu1~jammyppa6.dsc xen_4.16.0-1~ubuntu1~jammyppa6.debian.tar.xz xen_4.16.0.orig.tar.bz2 ubuntu@:/mnt/build dpkg-source -x xen_4.16.0-1~ubuntu1~jammyppa6.dsc xen_4.16.0 cd xen_4.16.0 dpkg-buildpackage -i -us -uc -b --- In a jammy VM 4cpu/8G I get some avx2 crashes but the build works: Jan 19 07:41:27 j kernel: x86_64-linux-gn[130016]: segfault at 0 ip 7f189432ef3d sp 7ffc8e2361d8 error 4 in libc.so.6[7f18941bb000+194000] Jan 19 07:41:27 j kernel: Code: f8 77 c3 66 2e 0f 1f 84 00 00 00 00 00 f3 0f 1e fa 89 f8 48 89 fa c5 f9 ef c0 25 ff 0f 00 00 3d e0 0f 00 00 0f 87 33 01 00 00 fd 74 0f c5 fd d7 c1 85 c0 74 57 f3 0f bc c0 c5 f8 77 c3 66 66 #0 __strlen_avx2 () at ../sysdeps/x86_64/multiarch/strlen-avx2.S:74 74../sysdeps/x86_64/multiarch/strlen-avx2.S: No such file or directory. (gdb) bt #0 __strlen_avx2 () at ../sysdeps/x86_64/multiarch/strlen-avx2.S:74 #1 0x7fa98d63c2d0 in ?? () from /lib/x86_64-linux-gnu/libbfd-2.37.50-system.20220106.so #2 0x7fa98d6021e8 in ?? () from /lib/x86_64-linux-gnu/libbfd-2.37.50-system.20220106.so #3 0x7fa98d602509 in coff_write_alien_symbol () from /lib/x86_64-linux-gnu/libbfd-2.37.50-system.20220106.so #4 0x7fa98d6033bd in _bfd_coff_final_link () from /lib/x86_64-linux-gnu/libbfd-2.37.50-system.20220106.so #5 0x562bdaaae3bf in ?? () #6 0x7fa98d2e8fd0 in __libc_start_call_main (main=main@entry=0x562bdaaad5e0, argc=argc@entry=8, argv=argv@entry=0x7ffc797f2968) at ../sysdeps/nptl/libc_start_call_main.h:58 #7 0x7fa98d2e907d in __libc_start_main_impl (main=0x562bdaaad5e0, argc=8, argv=0x7ffc797f2968, init=, fini=, rtld_fini=, stack_end=0x7ffc797f2958) at ../csu/libc-start.c:409 #8 0x562bdaaad515 in ?? () ^^ that is a different crash than on th LP builders ! And despite those crashes the build does appear to work oO?! The same crashes I see on my local sbuild runs, the full set of one build is Jan 19 07:39:02 Keschdeichel kernel: x86_64-linux-gn[4131180]: segfault at 0 ip 7f566e8b3f3d sp 7ffde04b75a8 error 4 in libc.so.6[7f566e74+194000] Jan 19 07:39:03 Keschdeichel kernel: x86_64-linux-gn[4131332]: segfault at 0 ip 7fbba26e4f3d sp 7fffab8a5b68 error 4 in libc.so.6[7fbba2571000+194000] Jan 19 07:39:03 Keschdeichel kernel: x86_64-linux-gn[4131382]: segfault at 0 ip 7fe3681b7f3d sp 7ffcbbf16628 error 4 in libc.so.6[7fe368044000+194000] Jan 19 07:39:42 Keschdeichel kernel: x86_64-linux-gn[4134584]: segfault at 0 ip 7f241f455f3d sp 7ffd05c2e7c8 error 4 in libc.so.6[7f241f2e2000+194000]
[Touch-packages] [Bug 1958389]
Created attachment 13937 Likely fix >From the backtrace in https://bugs.debian.org/1004269 it is clear that the problem is triggered by commit e86fc4a5bc37 in which a new extrap field was added to coffcode.h combined_entry_type but is not used on anything except rs6000 coff targets. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to binutils in Ubuntu. https://bugs.launchpad.net/bugs/1958389 Title: Jammy builds of xen segfault, but only on launchpad x86 builders Status in binutils: In Progress Status in launchpad-buildd: New Status in binutils package in Ubuntu: New Status in xen package in Ubuntu: Invalid Status in binutils source package in Jammy: New Status in xen source package in Jammy: Invalid Status in binutils package in Debian: New Bug description: FTBFS in Jammy on LP infra: https://launchpadlibrarian.net/580924961/buildlog_ubuntu-jammy-amd64.xen_4.16.0-1~ubuntu1~jammyppa4_BUILDING.txt.gz https://launchpadlibrarian.net/581060687/buildlog_ubuntu-jammy-amd64.xen_4.16.0-1~ubuntu1~jammyppa6_BUILDING.txt.gz Related PPA: https://launchpad.net/~ci-train-ppa-service/+archive/ubuntu/4760/+packages Summary: - Build reliably fails on LP - Build in local sbuild works reliably on my Laptop - Build in local VM (sizing like LP builders) works (other crashes but works) - Build on AMD server (chip more similar to LP) works reliably Failing step: On Launchpad build infrastructure it breaks on ld: $ x86_64-linux-gnu-ld -mi386pep --subsystem=10 --image-base=0x82d04000 --stack=0,0 --heap=0,0 --section-alignment=0x20 --file-alignment=0x20 --major-image-version=4 --minor-image-version=16 --major-os-version=2 --minor-os-version=0 --major-subsystem-version=2 --minor-subsystem-version=0 --no-insert-timestamp --build-id=sha1 -T efi.lds -N prelink.o /<>/xen/common/symbols-dummy.o -b pe-x86-64 efi/buildid.o -o /<>/xen/.xen.efi.0x82d04000.0 && : Segmentation fault (core dumped --- Steps to recreate (result depends on platform) # you can grab the package from https://launchpad.net/~ci-train-ppa- service/+archive/ubuntu/4760/+packages sudo vim /etc/apt/sources.list sudo apt update sudo apt dist-upgrade -y sudo apt build-dep xen sudo apt install flex bison python3-dev libpython3-dev dpkg-dev devscripts apport-retrace sudo mkdir /mnt/build sudo chmod go+w /mnt/build cd /mnt/build # copy in things from host scp xen_4.16.0-1~ubuntu1~jammyppa6.dsc xen_4.16.0-1~ubuntu1~jammyppa6.debian.tar.xz xen_4.16.0.orig.tar.bz2 ubuntu@:/mnt/build dpkg-source -x xen_4.16.0-1~ubuntu1~jammyppa6.dsc xen_4.16.0 cd xen_4.16.0 dpkg-buildpackage -i -us -uc -b --- In a jammy VM 4cpu/8G I get some avx2 crashes but the build works: Jan 19 07:41:27 j kernel: x86_64-linux-gn[130016]: segfault at 0 ip 7f189432ef3d sp 7ffc8e2361d8 error 4 in libc.so.6[7f18941bb000+194000] Jan 19 07:41:27 j kernel: Code: f8 77 c3 66 2e 0f 1f 84 00 00 00 00 00 f3 0f 1e fa 89 f8 48 89 fa c5 f9 ef c0 25 ff 0f 00 00 3d e0 0f 00 00 0f 87 33 01 00 00 fd 74 0f c5 fd d7 c1 85 c0 74 57 f3 0f bc c0 c5 f8 77 c3 66 66 #0 __strlen_avx2 () at ../sysdeps/x86_64/multiarch/strlen-avx2.S:74 74../sysdeps/x86_64/multiarch/strlen-avx2.S: No such file or directory. (gdb) bt #0 __strlen_avx2 () at ../sysdeps/x86_64/multiarch/strlen-avx2.S:74 #1 0x7fa98d63c2d0 in ?? () from /lib/x86_64-linux-gnu/libbfd-2.37.50-system.20220106.so #2 0x7fa98d6021e8 in ?? () from /lib/x86_64-linux-gnu/libbfd-2.37.50-system.20220106.so #3 0x7fa98d602509 in coff_write_alien_symbol () from /lib/x86_64-linux-gnu/libbfd-2.37.50-system.20220106.so #4 0x7fa98d6033bd in _bfd_coff_final_link () from /lib/x86_64-linux-gnu/libbfd-2.37.50-system.20220106.so #5 0x562bdaaae3bf in ?? () #6 0x7fa98d2e8fd0 in __libc_start_call_main (main=main@entry=0x562bdaaad5e0, argc=argc@entry=8, argv=argv@entry=0x7ffc797f2968) at ../sysdeps/nptl/libc_start_call_main.h:58 #7 0x7fa98d2e907d in __libc_start_main_impl (main=0x562bdaaad5e0, argc=8, argv=0x7ffc797f2968, init=, fini=, rtld_fini=, stack_end=0x7ffc797f2958) at ../csu/libc-start.c:409 #8 0x562bdaaad515 in ?? () ^^ that is a different crash than on th LP builders ! And despite those crashes the build does appear to work oO?! The same crashes I see on my local sbuild runs, the full set of one build is Jan 19 07:39:02 Keschdeichel kernel: x86_64-linux-gn[4131180]: segfault at 0 ip 7f566e8b3f3d sp 7ffde04b75a8 error 4 in libc.so.6[7f566e74+194000] Jan 19 07:39:03 Keschdeichel kernel: x86_64-linux-gn[4131332]: segfault at 0 ip 7fbba26e4f3d sp 7fffab8a5b68 error 4 in libc.so.6[7fbba2571000+194000] Jan 19 07:39:03 Keschdeichel kernel: x86_64-linux-gn[4131382]: segfault at 0 ip 7fe3681b7f3d sp 7ffcbbf16628 error 4 in libc.so.6[7fe368044000+194000] Jan 19 0
[Touch-packages] [Bug 1958389]
Fixed mainline and 2.38 branch -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to binutils in Ubuntu. https://bugs.launchpad.net/bugs/1958389 Title: Jammy builds of xen segfault, but only on launchpad x86 builders Status in binutils: Fix Released Status in launchpad-buildd: New Status in binutils package in Ubuntu: Fix Released Status in xen package in Ubuntu: Invalid Status in binutils source package in Jammy: Fix Released Status in xen source package in Jammy: Invalid Status in binutils package in Debian: Fix Released Bug description: FTBFS in Jammy on LP infra: https://launchpadlibrarian.net/580924961/buildlog_ubuntu-jammy-amd64.xen_4.16.0-1~ubuntu1~jammyppa4_BUILDING.txt.gz https://launchpadlibrarian.net/581060687/buildlog_ubuntu-jammy-amd64.xen_4.16.0-1~ubuntu1~jammyppa6_BUILDING.txt.gz Related PPA: https://launchpad.net/~ci-train-ppa-service/+archive/ubuntu/4760/+packages Summary: - Build reliably fails on LP - Build in local sbuild works reliably on my Laptop - Build in local VM (sizing like LP builders) works (other crashes but works) - Build on AMD server (chip more similar to LP) works reliably Failing step: On Launchpad build infrastructure it breaks on ld: $ x86_64-linux-gnu-ld -mi386pep --subsystem=10 --image-base=0x82d04000 --stack=0,0 --heap=0,0 --section-alignment=0x20 --file-alignment=0x20 --major-image-version=4 --minor-image-version=16 --major-os-version=2 --minor-os-version=0 --major-subsystem-version=2 --minor-subsystem-version=0 --no-insert-timestamp --build-id=sha1 -T efi.lds -N prelink.o /<>/xen/common/symbols-dummy.o -b pe-x86-64 efi/buildid.o -o /<>/xen/.xen.efi.0x82d04000.0 && : Segmentation fault (core dumped --- Steps to recreate (result depends on platform) # you can grab the package from https://launchpad.net/~ci-train-ppa- service/+archive/ubuntu/4760/+packages sudo vim /etc/apt/sources.list sudo apt update sudo apt dist-upgrade -y sudo apt build-dep xen sudo apt install flex bison python3-dev libpython3-dev dpkg-dev devscripts apport-retrace sudo mkdir /mnt/build sudo chmod go+w /mnt/build cd /mnt/build # copy in things from host scp xen_4.16.0-1~ubuntu1~jammyppa6.dsc xen_4.16.0-1~ubuntu1~jammyppa6.debian.tar.xz xen_4.16.0.orig.tar.bz2 ubuntu@:/mnt/build dpkg-source -x xen_4.16.0-1~ubuntu1~jammyppa6.dsc xen_4.16.0 cd xen_4.16.0 dpkg-buildpackage -i -us -uc -b --- In a jammy VM 4cpu/8G I get some avx2 crashes but the build works: Jan 19 07:41:27 j kernel: x86_64-linux-gn[130016]: segfault at 0 ip 7f189432ef3d sp 7ffc8e2361d8 error 4 in libc.so.6[7f18941bb000+194000] Jan 19 07:41:27 j kernel: Code: f8 77 c3 66 2e 0f 1f 84 00 00 00 00 00 f3 0f 1e fa 89 f8 48 89 fa c5 f9 ef c0 25 ff 0f 00 00 3d e0 0f 00 00 0f 87 33 01 00 00 fd 74 0f c5 fd d7 c1 85 c0 74 57 f3 0f bc c0 c5 f8 77 c3 66 66 #0 __strlen_avx2 () at ../sysdeps/x86_64/multiarch/strlen-avx2.S:74 74../sysdeps/x86_64/multiarch/strlen-avx2.S: No such file or directory. (gdb) bt #0 __strlen_avx2 () at ../sysdeps/x86_64/multiarch/strlen-avx2.S:74 #1 0x7fa98d63c2d0 in ?? () from /lib/x86_64-linux-gnu/libbfd-2.37.50-system.20220106.so #2 0x7fa98d6021e8 in ?? () from /lib/x86_64-linux-gnu/libbfd-2.37.50-system.20220106.so #3 0x7fa98d602509 in coff_write_alien_symbol () from /lib/x86_64-linux-gnu/libbfd-2.37.50-system.20220106.so #4 0x7fa98d6033bd in _bfd_coff_final_link () from /lib/x86_64-linux-gnu/libbfd-2.37.50-system.20220106.so #5 0x562bdaaae3bf in ?? () #6 0x7fa98d2e8fd0 in __libc_start_call_main (main=main@entry=0x562bdaaad5e0, argc=argc@entry=8, argv=argv@entry=0x7ffc797f2968) at ../sysdeps/nptl/libc_start_call_main.h:58 #7 0x7fa98d2e907d in __libc_start_main_impl (main=0x562bdaaad5e0, argc=8, argv=0x7ffc797f2968, init=, fini=, rtld_fini=, stack_end=0x7ffc797f2958) at ../csu/libc-start.c:409 #8 0x562bdaaad515 in ?? () ^^ that is a different crash than on th LP builders ! And despite those crashes the build does appear to work oO?! The same crashes I see on my local sbuild runs, the full set of one build is Jan 19 07:39:02 Keschdeichel kernel: x86_64-linux-gn[4131180]: segfault at 0 ip 7f566e8b3f3d sp 7ffde04b75a8 error 4 in libc.so.6[7f566e74+194000] Jan 19 07:39:03 Keschdeichel kernel: x86_64-linux-gn[4131332]: segfault at 0 ip 7fbba26e4f3d sp 7fffab8a5b68 error 4 in libc.so.6[7fbba2571000+194000] Jan 19 07:39:03 Keschdeichel kernel: x86_64-linux-gn[4131382]: segfault at 0 ip 7fe3681b7f3d sp 7ffcbbf16628 error 4 in libc.so.6[7fe368044000+194000] Jan 19 07:39:42 Keschdeichel kernel: x86_64-linux-gn[4134584]: segfault at 0 ip 7f241f455f3d sp 7ffd05c2e7c8 error 4 in libc.so.6[7f241f2e2000+194000] Jan 19 07:44:57 Keschdeichel kernel: x86_64-linux-gn[4171794]: segfault
[Touch-packages] [Bug 1959085] Re: Ubuntu 21.10 boot stuck in initramfs
I just found this, I encountered this exact same issue with Jammy Desktop installer last night and filed a bug here : #1960974 -- 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/1959085 Title: Ubuntu 21.10 boot stuck in initramfs Status in initramfs-tools package in Ubuntu: Confirmed Status in zfs-linux package in Ubuntu: New Bug description: Hi, I just installed the latest Ubuntu desktop from iso file ubuntu-21.10-desktop-amd64.iso inside of VMWare workstation. I chose ZFS and native ZFS encryption of the filesystem. The installation went fine. Everything worked as expected. Then I upgraded the packages to the latest version via the Software updater. After reboot I'm stuck in the initramfs prompt. The following command fails: mount -o zfsutil -t zfs rpool/ROOT/ubuntu_gtw63h /root// Permission denied. And the system never asks me for the password to unlock the root fs. So, I'm guessing that there is something wrong with the new initramfs disk: initrd.img-5.13.0-27-generic When I reboot and select the previous version in grub: initrd.img-5.13.0-27-generic, the system asks for the password and boots without a problem. Thanks. To summarize: 1. Installed new VM using the Ubuntu iso image. Chose ZFS native encryption. Minimal install. 2. As soon as the system came up, I hit the update/upgrade prompt. Rebooted and failed to boot the new version. I didn't customize anything or installed anything extra. root@ubud01:/var# lsb_release -rd Description: Ubuntu 21.10 Release: 21.10 root@ubud01:/var# dpkg -l | grep zfs ii libzfs4linux 2.0.6-1ubuntu2 amd64OpenZFS filesystem library for Linux ii zfs-initramfs 2.0.6-1ubuntu2 amd64OpenZFS root filesystem capabilities for Linux - initramfs ii zfs-zed2.0.6-1ubuntu2 amd64OpenZFS Event Daemon ii zfsutils-linux 2.0.6-1ubuntu2 amd64command-line tools to manage OpenZFS filesystems root@ubud01:/var# dpkg -l | grep init ii busybox-initramfs 1:1.30.1-6ubuntu3.1 amd64Standalone shell setup for initramfs ii cryptsetup-initramfs 2:2.3.6-0ubuntu1 all disk encryption support - initramfs integration ii gnome-initial-setup40.4-1ubuntu1 amd64Initial GNOME system setup helper ii init 1.60build1 amd64metapackage ensuring an init system is installed ii init-system-helpers1.60build1 all helper tools for all init systems ii initramfs-tools0.140ubuntu6 all generic modular initramfs generator (automation) ii initramfs-tools-bin0.140ubuntu6 amd64binaries used by initramfs-tools ii initramfs-tools-core 0.140ubuntu6 all generic modular initramfs generator (core tools) ii libatopology2:amd641.2.4-1.1ubuntu3.1 amd64shared library for handling ALSA topology definitions ii libklibc:amd64 2.0.8-6.1ubuntu2 amd64minimal libc subset for use with initramfs ii lsb-base 11.1.0ubuntu3 all Linux Standard Base init script functionality ii ncurses-base 6.2+20201114-2build1 all basic terminal type definitions ii sysvinit-utils 2.96-7ubuntu1 amd64System-V-like utilities ii xinit 1.4.1-0ubuntu3 amd64X server initialisation tool ii zfs-initramfs 2.0.6-1ubuntu2 amd64OpenZFS root filesystem capabilities for Linux - initramfs root@ubud01:/var# zfs list NAME USED AVAIL REFER MOUNTPOINT bpool 290M 542M 96K /boot bpool/BOOT 289M 542M 96K none bpool/BOOT/ubuntu_gtw63h 288M 542M 156M /boot rpool
[Touch-packages] [Bug 1959085] Re: Ubuntu 21.10 boot stuck in initramfs
I confirmed this is happening. Here are two ways to reproduce: 1) Grabbed jammy-desktop-amd64.iso nightly build (Feb 2). Installing a system using this ISO, while choosing Encryption + ZFS lands you on this error. 2) Installed Impish using an ISO from October 12, choosing Encryption + ZFS. The system installs and boots up w/o any issues. Performed a dist- upgrade to Jammy, which resulted the system booting into initramfs with the exact same error. -- 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/1959085 Title: Ubuntu 21.10 boot stuck in initramfs Status in initramfs-tools package in Ubuntu: Confirmed Status in zfs-linux package in Ubuntu: Confirmed Bug description: Hi, I just installed the latest Ubuntu desktop from iso file ubuntu-21.10-desktop-amd64.iso inside of VMWare workstation. I chose ZFS and native ZFS encryption of the filesystem. The installation went fine. Everything worked as expected. Then I upgraded the packages to the latest version via the Software updater. After reboot I'm stuck in the initramfs prompt. The following command fails: mount -o zfsutil -t zfs rpool/ROOT/ubuntu_gtw63h /root// Permission denied. And the system never asks me for the password to unlock the root fs. So, I'm guessing that there is something wrong with the new initramfs disk: initrd.img-5.13.0-27-generic When I reboot and select the previous version in grub: initrd.img-5.13.0-27-generic, the system asks for the password and boots without a problem. Thanks. To summarize: 1. Installed new VM using the Ubuntu iso image. Chose ZFS native encryption. Minimal install. 2. As soon as the system came up, I hit the update/upgrade prompt. Rebooted and failed to boot the new version. I didn't customize anything or installed anything extra. root@ubud01:/var# lsb_release -rd Description: Ubuntu 21.10 Release: 21.10 root@ubud01:/var# dpkg -l | grep zfs ii libzfs4linux 2.0.6-1ubuntu2 amd64OpenZFS filesystem library for Linux ii zfs-initramfs 2.0.6-1ubuntu2 amd64OpenZFS root filesystem capabilities for Linux - initramfs ii zfs-zed2.0.6-1ubuntu2 amd64OpenZFS Event Daemon ii zfsutils-linux 2.0.6-1ubuntu2 amd64command-line tools to manage OpenZFS filesystems root@ubud01:/var# dpkg -l | grep init ii busybox-initramfs 1:1.30.1-6ubuntu3.1 amd64Standalone shell setup for initramfs ii cryptsetup-initramfs 2:2.3.6-0ubuntu1 all disk encryption support - initramfs integration ii gnome-initial-setup40.4-1ubuntu1 amd64Initial GNOME system setup helper ii init 1.60build1 amd64metapackage ensuring an init system is installed ii init-system-helpers1.60build1 all helper tools for all init systems ii initramfs-tools0.140ubuntu6 all generic modular initramfs generator (automation) ii initramfs-tools-bin0.140ubuntu6 amd64binaries used by initramfs-tools ii initramfs-tools-core 0.140ubuntu6 all generic modular initramfs generator (core tools) ii libatopology2:amd641.2.4-1.1ubuntu3.1 amd64shared library for handling ALSA topology definitions ii libklibc:amd64 2.0.8-6.1ubuntu2 amd64minimal libc subset for use with initramfs ii lsb-base 11.1.0ubuntu3 all Linux Standard Base init script functionality ii ncurses-base 6.2+20201114-2build1 all basic terminal type definitions ii sysvinit-utils 2.96-7ubuntu1 amd64System-V-like utilities ii xinit 1.4.1-0ubuntu3 amd64X server initialisation tool ii zfs-initramfs 2.0.6-1ubuntu2 amd64OpenZFS root filesystem capabilities for Linux - initramfs root@ubud01:/var# zfs list NAME
[Touch-packages] [Bug 40214]
Documented -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to binutils in Ubuntu. https://bugs.launchpad.net/bugs/40214 Title: ld checks for libs in wrong order. it should be inline with ld.so and check configured folders first. Status in binutils: Fix Released Status in binutils package in Ubuntu: Fix Released Bug description: if one installs a new version of a lib to /usr/local/lib and has an old version from the system in /usr/lib linking fails with gcc. it tries to link the version in /usr/lib removing the version from /usr/lib, linking works. ldd shows the right version in /usr/local/lib since the version of libtool in ubuntu does not include dependency_libs from the .la file, one has to specify the dependency libs manualy or remove the libs from /usr/lib; both merly workarounds that i dont want to use upstream. not sure what the right place for this bug is. To manage notifications about this bug go to: https://bugs.launchpad.net/binutils/+bug/40214/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1722292] Re: [FFe] Mir 0.28 release
** Summary changed: - [FFe] Mir 1.0 release + [FFe] Mir 0.28 release ** Description changed: - * New upstream release 1.0.0(https://launchpad.net/mir/+milestone/1.0.0) -- ABI summary: - . mirclient ABI unchanged at 9 - . miral ABI introduced at 2 - . mirserver ABI bumped to 45 - . mircommon ABI unchanged at 7 - . mirplatform ABI unchanged at 61 - . mirprotobuf ABI unchanged at 3 - . mirplatformgraphics ABI unchanged at 13 - . mirclientplatform ABI unchanged at 5 - . mirinputplatform ABI unchanged at 7 - . mircore ABI unchanged at 1 -- Enhancements: - . Update licences to (L)GPL3 or (L)GPL2. - . Initial support for Wayland clients - . [mir_demo_client_display_config] add orientation changing - . RPC: Don't require the server ACK client's buffer-release requests. - . Added libmirclientcpp to Mir source package - . Added libmiral to Mir source package - . Various small improvements to miral-shell example - . [libmiral, miral-shell] handle display reconfiguration better and allow -shells to customize maximized placements. - . Enable CommandLineOptions to be processed before server initialization -- Bugs fixed: - . Fix handling of invalid display configuration. (LP: #1643446) - . Move full responsibility for buffer IPC into frontend. (LP: #1395421) - . Don't destroy an IPC "closure" object when it may yet be used -(LP: #1672960) - . [mesa-kms] Respect display orientation when painting cursor. -(LP: #1610078) - . Respect cursor hotspot when hosted on Mir. (LP: #1705284) - . mcl::BufferVault: Fix lock inversion. - . Handle mir_event_type_close_window in examples (LP: #1706004), -(LP: #1705439) - . Drop BufferStream::suitable_for_cursor() - . Only notify resize events for valid surfaces (LP: #1643446) - . Don't leak DRM fds in platform-eglstream probe. - . Remove obsolete & broken example code. (LP: #1663130) - . Move buffer-release IPC to a dedicated IPC thread. (LP: #1395421) - . [NestedServerWithTwoDisplays] Look for the last of a series of -synthetic events to ensure that the queue is drained before the test -exits. (LP: #1709666) - . floating window manager allows resizing maximized windows (LP: #1704776) - . [miral-shell] doesn't work with breeze X cursor theme (LP: #1699084) - . [miral-shell] Don't allow splashscreen to be occluded (LP: #1705973) - . [miral-shell] Update maximized windows on display changes (LP: #1705695) - . Make racy DragAndDrop test reliable. (LP: #1704780) - . [libmiral] Define default window settings in one place and clamp the -actual values to avoid ldiv0. (LP: #1717061) - . [miral-kiosk] Apply fullscreen logic when hidden windows are restored. -(LP: #1717910) - . [mir-on-x11] Less annoying clipping of Mir-on-X11 window when it exceeds -display bounds. (LP: #1668599) + * New upstream release 0.28.0(https://launchpad.net/mir/+milestone/0.28.0) + - ABI summary: + . mirclient ABI unchanged at 9 + . miral ABI introduced at 2 + . mirserver ABI bumped to 45 + . mircommon ABI unchanged at 7 + . mirplatform ABI unchanged at 61 + . mirprotobuf ABI unchanged at 3 + . mirplatformgraphics ABI unchanged at 13 + . mirclientplatform ABI unchanged at 5 + . mirinputplatform ABI unchanged at 7 + . mircore ABI unchanged at 1 + - Enhancements: + . Update licences to (L)GPL3 or (L)GPL2. + . Initial support for Wayland clients + . [mir_demo_client_display_config] add orientation changing + . RPC: Don't require the server ACK client's buffer-release requests. + . Added libmirclientcpp to Mir source package + . Added libmiral to Mir source package + . Various small improvements to miral-shell example + . [libmiral, miral-shell] handle display reconfiguration better and allow + shells to customize maximized placements. + . Enable CommandLineOptions to be processed before server initialization + - Bugs fixed: + . Fix handling of invalid display configuration. (LP: #1643446) + . Move full responsibility for buffer IPC into frontend. (LP: #1395421) + . Don't destroy an IPC "closure" object when it may yet be used + (LP: #1672960) + . [mesa-kms] Respect display orientation when painting cursor. + (LP: #1610078) + . Respect cursor hotspot when hosted on Mir. (LP: #1705284) + . mcl::BufferVault: Fix lock inversion. + . Handle mir_event_type_close_window in examples (LP: #1706004), + (LP: #1705439) + . Drop BufferStream::suitable_for_cursor() + . Only notify resize events for valid surfaces (LP: #1643446) + . Don't leak DRM fds in platform-eglstream probe. + . Remove obsolete & broken example code. (LP: #1663130) + . Move buffer-release IPC t
[Touch-packages] [Bug 1722292] Re: [FFe] Mir 0.28 release
There's some additional verification of the release happening. We don't anticipate a significant delay. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to mir in Ubuntu. https://bugs.launchpad.net/bugs/1722292 Title: [FFe] Mir 0.28 release Status in mir package in Ubuntu: Confirmed Bug description: * New upstream release 0.28.0(https://launchpad.net/mir/+milestone/0.28.0) - ABI summary: . mirclient ABI unchanged at 9 . miral ABI introduced at 2 . mirserver ABI bumped to 45 . mircommon ABI unchanged at 7 . mirplatform ABI unchanged at 61 . mirprotobuf ABI unchanged at 3 . mirplatformgraphics ABI unchanged at 13 . mirclientplatform ABI unchanged at 5 . mirinputplatform ABI unchanged at 7 . mircore ABI unchanged at 1 - Enhancements: . Update licences to (L)GPL3 or (L)GPL2. . Initial support for Wayland clients . [mir_demo_client_display_config] add orientation changing . RPC: Don't require the server ACK client's buffer-release requests. . Added libmirclientcpp to Mir source package . Added libmiral to Mir source package . Various small improvements to miral-shell example . [libmiral, miral-shell] handle display reconfiguration better and allow shells to customize maximized placements. . Enable CommandLineOptions to be processed before server initialization - Bugs fixed: . Fix handling of invalid display configuration. (LP: #1643446) . Move full responsibility for buffer IPC into frontend. (LP: #1395421) . Don't destroy an IPC "closure" object when it may yet be used (LP: #1672960) . [mesa-kms] Respect display orientation when painting cursor. (LP: #1610078) . Respect cursor hotspot when hosted on Mir. (LP: #1705284) . mcl::BufferVault: Fix lock inversion. . Handle mir_event_type_close_window in examples (LP: #1706004), (LP: #1705439) . Drop BufferStream::suitable_for_cursor() . Only notify resize events for valid surfaces (LP: #1643446) . Don't leak DRM fds in platform-eglstream probe. . Remove obsolete & broken example code. (LP: #1663130) . Move buffer-release IPC to a dedicated IPC thread. (LP: #1395421) . [NestedServerWithTwoDisplays] Look for the last of a series of synthetic events to ensure that the queue is drained before the test exits. (LP: #1709666) . floating window manager allows resizing maximized windows (LP: #1704776) . [miral-shell] doesn't work with breeze X cursor theme (LP: #1699084) . [miral-shell] Don't allow splashscreen to be occluded (LP: #1705973) . [miral-shell] Update maximized windows on display changes (LP: #1705695) . Make racy DragAndDrop test reliable. (LP: #1704780) . [libmiral] Define default window settings in one place and clamp the actual values to avoid ldiv0. (LP: #1717061) . [miral-kiosk] Apply fullscreen logic when hidden windows are restored. (LP: #1717910) . [mir-on-x11] Less annoying clipping of Mir-on-X11 window when it exceeds display bounds. (LP: #1668599) See https://bileto.ubuntu.com/#/ticket/2988 for build artifacts. Install log: http://pastebin.ubuntu.com/25707752/ We've followed https://wiki.ubuntu.com/Process/Merges/TestPlans/Mir for testing. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mir/+bug/1722292/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1672960] Re: unity-system-compositor crashed with SIGSEGV in invoke() from mir::frontend::detail::ProtobufMessageProcessor::dispatch:on_new_message() from on_read_size()
** Changed in: mir Status: Fix Committed => Fix Released -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to mir in Ubuntu. https://bugs.launchpad.net/bugs/1672960 Title: unity-system-compositor crashed with SIGSEGV in invoke() from mir::frontend::detail::ProtobufMessageProcessor::dispatch:on_new_message() from on_read_size() Status in Canonical System Image: Confirmed Status in Mir: Fix Released Status in Unity System Compositor: Invalid Status in mir package in Ubuntu: Fix Released Status in unity-system-compositor package in Ubuntu: Invalid Bug description: The Ubuntu Error Tracker has been receiving reports about a problem regarding unity-system-compositor. This problem was most recently seen with package version 0.8.0+17.04.20161206-0ubuntu1, the problem page at https://errors.ubuntu.com/problem/322176398baf670e4e9e5bb140a0aed0bbf0a00e 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 you can request it at http://forms.canonical.com/reports/. To manage notifications about this bug go to: https://bugs.launchpad.net/canonical-devices-system-image/+bug/1672960/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1685186] Re: [SRU] Mir needs to be updated to 0.26 in 16.04LTS
** Description changed: [Impact] Snap development using Mir has been using the "stable phone overlay" PPA which is both inconvenient and a legacy of the cancelled Unity8 project. It would greatly simplify things if Mir were updated in the Xenial archive. [Test Case] Build a Mir client snap (e.g. lp:~albaguirre/+snap/mir-client-demos) against "Primary Ubuntu Archive" and deploy as described in https://developer.ubuntu.com/en/snappy/guides/mir-snaps/ Expected: the client apps start and are visible on screen Actual: the client apps don't start and are not visible on screen [Regression Potential] Mir has two categories of dependent project: 1 Unity8 and unity-system-compositor "server" packages 2 toolkits and other "clients" of Mir "Server" packages from the archive will stop working in the LTS as they will continue using the earlier libmirserver.so.38 (from Mir 0.21) which doesn't work with the libmirclient.so.9 from Mir 0.26. This is unimportant as these packages were provided as an "early experience", not for serious use. "Client" packages are dependent only on libmirclient.so.9 which is ABI stable. The principle type of regression would be FTBFS where APIs have been deprecated in 0.26. The linked 0.26.3 release has these deprecations disabled for 16.04. The packages are available in silo: https://bileto.ubuntu.com/#/ticket/2736 notes: A recursive search or rdependencies identifies the following packages in category 1: camera-app-autopilot gallery-app-autopilot indicator-network-autopilot indicators-client qtdeclarative5-qtmir-plugin qtmir-android qtmir-desktop qtmir-tests ubuntu-desktop-mir ubuntu-experience-tests ubuntu-pocket-desktop ubuntu-push-autopilot ubuntu-touch ubuntu-touch-session unity8 unity8-autopilot unity8-desktop-session-mir unity-scope-click-autopilot unity-system-compositor unity-system-compositor-autopilot Anyone wanting these packages should switch to the "unity8-desktop- session" preview package in 17.04 where they are far more functional. [Alternatives] - If we want to keep everything working in Xenial, we *could* bump the libmirclient SONAME to libmirclient.so.10. This would result in libmirclient9 being NBS, but continuing to work against the Mir servers available in 16.04 (until and unless they are rebuilt). + If we want to keep everything working in Xenial, we *could* bump the libmirclient SONAME to libmirclient.so.10. This would result in libmirclient9 being NBS, but continuing to work against the Mir servers available in 16.04[*] (until and unless they are rebuilt). + + However, this does not enable the desired result for IoT deployments of + toolkits (GTK, Qt etc) and other clients working against servers + (specifically miral-kiosk) built against the updated libraries. + + To work for IoT these would need to rebuilt from source - at which point + they (and their dependencies) would stop working against the servers in + category 1. + + [*] with the exception of the servers provided in mir-examples, these + would only work with clients linking against libmirclient.so.10. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to mir in Ubuntu. https://bugs.launchpad.net/bugs/1685186 Title: [SRU] Mir needs to be updated to 0.26 in 16.04LTS Status in mir package in Ubuntu: In Progress Status in mir source package in Xenial: New Bug description: [Impact] Snap development using Mir has been using the "stable phone overlay" PPA which is both inconvenient and a legacy of the cancelled Unity8 project. It would greatly simplify things if Mir were updated in the Xenial archive. [Test Case] Build a Mir client snap (e.g. lp:~albaguirre/+snap/mir-client-demos) against "Primary Ubuntu Archive" and deploy as described in https://developer.ubuntu.com/en/snappy/guides/mir-snaps/ Expected: the client apps start and are visible on screen Actual: the client apps don't start and are not visible on screen [Regression Potential] Mir has two categories of dependent project: 1 Unity8 and unity-system-compositor "server" packages 2 toolkits and other "clients" of Mir "Server" packages from the archive will stop working in the LTS as they will continue using the earlier libmirserver.so.38 (from Mir 0.21) which doesn't work with the libmirclient.so.9 from Mir 0.26. This is unimportant as these packages were provided as an "early experience", not for serious use. "Client" packages are dependent only on libmirclient.so.9 which is ABI stable. The principle type of regression would be FTBFS where APIs have been deprecated in 0.26. The linked 0.26.3 release has these deprecations disabled for 16.04. The packages are available in silo: https://bileto.ubuntu.com/#/ticket/2736 notes: A recursive search or rdependencies
[Touch-packages] [Bug 1685186] Re: [SRU] Mir needs to be updated to 0.26 in 16.04LTS
This works fine on a AMD64 desktop -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to mir in Ubuntu. https://bugs.launchpad.net/bugs/1685186 Title: [SRU] Mir needs to be updated to 0.26 in 16.04LTS Status in mir package in Ubuntu: In Progress Status in mir source package in Xenial: Fix Committed Bug description: [Impact] Snap development using Mir has been using the "stable phone overlay" PPA which is both inconvenient and a legacy of the cancelled Unity8 project. It would greatly simplify things if Mir were updated in the Xenial archive. [Test Case] Build a Mir client snap (e.g. lp:~albaguirre/+snap/mir-client-demos) against "Primary Ubuntu Archive" and deploy as described in https://developer.ubuntu.com/en/snappy/guides/mir-snaps/ Expected: the client apps start and are visible on screen Actual: the client apps don't start and are not visible on screen [Regression Potential] Mir has two categories of dependent project: 1 Unity8 and unity-system-compositor "server" packages 2 toolkits and other "clients" of Mir "Server" packages from the archive will stop working in the LTS as they will continue using the earlier libmirserver.so.38 (from Mir 0.21) which doesn't work with the libmirclient.so.9 from Mir 0.26. This is unimportant as these packages were provided as an "early experience", not for serious use. "Client" packages are dependent only on libmirclient.so.9 which is ABI stable. The principle type of regression would be FTBFS where APIs have been deprecated in 0.26. The linked 0.26.3 release has these deprecations disabled for 16.04. The packages are available in silo: https://bileto.ubuntu.com/#/ticket/2736 notes: A recursive search or rdependencies identifies the following packages in category 1: camera-app-autopilot gallery-app-autopilot indicator-network-autopilot indicators-client qtdeclarative5-qtmir-plugin qtmir-android qtmir-desktop qtmir-tests ubuntu-desktop-mir ubuntu-experience-tests ubuntu-pocket-desktop ubuntu-push-autopilot ubuntu-touch ubuntu-touch-session unity8 unity8-autopilot unity8-desktop-session-mir unity-scope-click-autopilot unity-system-compositor unity-system-compositor-autopilot Anyone wanting these packages should switch to the "unity8-desktop- session" preview package in 17.04 where they are far more functional. [Alternatives] If we want to keep everything working in Xenial, we *could* bump the libmirclient SONAME to libmirclient.so.10. This would result in libmirclient9 being NBS, but continuing to work against the Mir servers available in 16.04[*] (until and unless they are rebuilt). However, this does not enable the desired result for IoT deployments of toolkits (GTK, Qt etc) and other clients working against servers (specifically miral-kiosk) built against the updated libraries. To work for IoT these would need to rebuilt from source - at which point they (and their dependencies) would stop working against the servers in category 1. [*] with the exception of the servers provided in mir-examples, these would only work with clients linking against libmirclient.so.10. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mir/+bug/1685186/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1685186] Re: [SRU] Mir needs to be updated to 0.26 in 16.04LTS
Does the intended for the mir snaps too: lp:~saviq/mir-kiosk-apps/+git/mir-kiosk-apps/+merge/324179 lp:~saviq/mir-kiosk/+git/mir-kiosk/+merge/324180 lp:~saviq/mir-libs-snap/+git/mir-libs-snap/+merge/324197 ** Tags removed: verification-needed ** Tags added: verification-done -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to mir in Ubuntu. https://bugs.launchpad.net/bugs/1685186 Title: [SRU] Mir needs to be updated to 0.26 in 16.04LTS Status in mir package in Ubuntu: In Progress Status in mir source package in Xenial: Fix Committed Bug description: [Impact] Snap development using Mir has been using the "stable phone overlay" PPA which is both inconvenient and a legacy of the cancelled Unity8 project. It would greatly simplify things if Mir were updated in the Xenial archive. [Test Case] Build a Mir client snap (e.g. lp:~albaguirre/+snap/mir-client-demos) against "Primary Ubuntu Archive" and deploy as described in https://developer.ubuntu.com/en/snappy/guides/mir-snaps/ Expected: the client apps start and are visible on screen Actual: the client apps don't start and are not visible on screen [Regression Potential] Mir has two categories of dependent project: 1 Unity8 and unity-system-compositor "server" packages 2 toolkits and other "clients" of Mir "Server" packages from the archive will stop working in the LTS as they will continue using the earlier libmirserver.so.38 (from Mir 0.21) which doesn't work with the libmirclient.so.9 from Mir 0.26. This is unimportant as these packages were provided as an "early experience", not for serious use. "Client" packages are dependent only on libmirclient.so.9 which is ABI stable. The principle type of regression would be FTBFS where APIs have been deprecated in 0.26. The linked 0.26.3 release has these deprecations disabled for 16.04. The packages are available in silo: https://bileto.ubuntu.com/#/ticket/2736 notes: A recursive search or rdependencies identifies the following packages in category 1: camera-app-autopilot gallery-app-autopilot indicator-network-autopilot indicators-client qtdeclarative5-qtmir-plugin qtmir-android qtmir-desktop qtmir-tests ubuntu-desktop-mir ubuntu-experience-tests ubuntu-pocket-desktop ubuntu-push-autopilot ubuntu-touch ubuntu-touch-session unity8 unity8-autopilot unity8-desktop-session-mir unity-scope-click-autopilot unity-system-compositor unity-system-compositor-autopilot Anyone wanting these packages should switch to the "unity8-desktop- session" preview package in 17.04 where they are far more functional. [Alternatives] If we want to keep everything working in Xenial, we *could* bump the libmirclient SONAME to libmirclient.so.10. This would result in libmirclient9 being NBS, but continuing to work against the Mir servers available in 16.04[*] (until and unless they are rebuilt). However, this does not enable the desired result for IoT deployments of toolkits (GTK, Qt etc) and other clients working against servers (specifically miral-kiosk) built against the updated libraries. To work for IoT these would need to rebuilt from source - at which point they (and their dependencies) would stop working against the servers in category 1. [*] with the exception of the servers provided in mir-examples, these would only work with clients linking against libmirclient.so.10. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mir/+bug/1685186/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1677239] Re: mir_demo_standalone_render_overlays fails to link
** Tags removed: verification-needed ** Tags added: verification-done -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to mir in Ubuntu. https://bugs.launchpad.net/bugs/1677239 Title: mir_demo_standalone_render_overlays fails to link Status in Mir: Fix Committed Status in Mir 0.26 series: Fix Committed Status in mir package in Ubuntu: Triaged Status in mir source package in Xenial: Fix Committed Bug description: https://mir-jenkins.ubuntu.com/job/build-2-binpkg- mir/arch=amd64,compiler=gcc,platform=mesa,release=zesty/4453/console 11:41:20 [ 52%] Linking CXX executable ../../../../bin/mir_demo_standalone_render_overlays.bin 11:41:20 cd /<>/mir-0.26.1+17.04.20170209.1+zesty4503bzr4124/obj-x86_64-linux-gnu/src/platforms/android/utils && /usr/bin/cmake -E cmake_link_script CMakeFiles/mir_demo_standalone_render_overlays.dir/link.txt --verbose=1 11:41:20 /usr/lib/ccache/c++ -g -O2 -fdebug-prefix-map=/<>/mir-0.26.1+17.04.20170209.1+zesty4503bzr4124=. -fstack-protector-strong -Wformat -Werror=format-security -Wdate-time -D_FORTIFY_SOURCE=2 -pthread -g -std=c++14 -Werror -Wall -fno-strict-aliasing -pedantic -Wnon-virtual-dtor -Wextra -fPIC -flto -ffat-lto-objects -Wl,-Bsymbolic-functions -Wl,-z,relro -Wl,--as-needed -Wl,--no-undefined CMakeFiles/mir_demo_standalone_render_overlays.dir/render_overlays.cpp.o -o ../../../../bin/mir_demo_standalone_render_overlays.bin -rdynamic ../../../../lib/libmirplatform.so.16 ../../../../lib/libmircommon.so.7 ../../../capnproto/libmircapnproto.a -lkj -lcapnp ../../../../lib/libmircore.so.1 -lboost_date_time -lboost_system -lboost_program_options -lboost_filesystem -ldl -lEGL -lGLESv2 -lGLESv2 -L/lib/x86_64-linux-gnu -ludev -ludev 11:41:21 //usr/lib/x86_64-linux-gnu/libmirclient.so.9: undefined reference to `MirInputDeviceStateEvent::device_pressed_keys_for_index(unsigned long, unsigned long) const@MIR_COMMON_0.25_PRIVATE' 11:41:21 //usr/lib/x86_64-linux-gnu/libmirclient.so.9: undefined reference to `MirPointerEvent::set_x(float)@MIR_COMMON_0.25_PRIVATE' 11:41:21 //usr/lib/x86_64-linux-gnu/libmirclient.so.9: undefined reference to `MirTouchEvent::pressure(unsigned long) const@MIR_COMMON_0.25_PRIVATE' To manage notifications about this bug go to: https://bugs.launchpad.net/mir/+bug/1677239/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1677239] Re: mir_demo_standalone_render_overlays fails to link
Tested version 0.26.3+16.04.20170510-0ubuntu1 -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to mir in Ubuntu. https://bugs.launchpad.net/bugs/1677239 Title: mir_demo_standalone_render_overlays fails to link Status in Mir: Fix Committed Status in Mir 0.26 series: Fix Committed Status in mir package in Ubuntu: Triaged Status in mir source package in Xenial: Fix Committed Bug description: https://mir-jenkins.ubuntu.com/job/build-2-binpkg- mir/arch=amd64,compiler=gcc,platform=mesa,release=zesty/4453/console 11:41:20 [ 52%] Linking CXX executable ../../../../bin/mir_demo_standalone_render_overlays.bin 11:41:20 cd /<>/mir-0.26.1+17.04.20170209.1+zesty4503bzr4124/obj-x86_64-linux-gnu/src/platforms/android/utils && /usr/bin/cmake -E cmake_link_script CMakeFiles/mir_demo_standalone_render_overlays.dir/link.txt --verbose=1 11:41:20 /usr/lib/ccache/c++ -g -O2 -fdebug-prefix-map=/<>/mir-0.26.1+17.04.20170209.1+zesty4503bzr4124=. -fstack-protector-strong -Wformat -Werror=format-security -Wdate-time -D_FORTIFY_SOURCE=2 -pthread -g -std=c++14 -Werror -Wall -fno-strict-aliasing -pedantic -Wnon-virtual-dtor -Wextra -fPIC -flto -ffat-lto-objects -Wl,-Bsymbolic-functions -Wl,-z,relro -Wl,--as-needed -Wl,--no-undefined CMakeFiles/mir_demo_standalone_render_overlays.dir/render_overlays.cpp.o -o ../../../../bin/mir_demo_standalone_render_overlays.bin -rdynamic ../../../../lib/libmirplatform.so.16 ../../../../lib/libmircommon.so.7 ../../../capnproto/libmircapnproto.a -lkj -lcapnp ../../../../lib/libmircore.so.1 -lboost_date_time -lboost_system -lboost_program_options -lboost_filesystem -ldl -lEGL -lGLESv2 -lGLESv2 -L/lib/x86_64-linux-gnu -ludev -ludev 11:41:21 //usr/lib/x86_64-linux-gnu/libmirclient.so.9: undefined reference to `MirInputDeviceStateEvent::device_pressed_keys_for_index(unsigned long, unsigned long) const@MIR_COMMON_0.25_PRIVATE' 11:41:21 //usr/lib/x86_64-linux-gnu/libmirclient.so.9: undefined reference to `MirPointerEvent::set_x(float)@MIR_COMMON_0.25_PRIVATE' 11:41:21 //usr/lib/x86_64-linux-gnu/libmirclient.so.9: undefined reference to `MirTouchEvent::pressure(unsigned long) const@MIR_COMMON_0.25_PRIVATE' To manage notifications about this bug go to: https://bugs.launchpad.net/mir/+bug/1677239/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1672955] Re: unity-system-compositor crashed with SIGSEGV in libinput_device_config_accel_is_available() from libinput_device_config_accel_set_speed() from mir::input::evdev::Lib
Tested version 0.26.3+16.04.20170510-0ubuntu1 ** Tags removed: verification-needed ** Tags added: verification-done -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to mir in Ubuntu. https://bugs.launchpad.net/bugs/1672955 Title: unity-system-compositor crashed with SIGSEGV in libinput_device_config_accel_is_available() from libinput_device_config_accel_set_speed() from mir::input::evdev::LibInputDevice::apply_settings() Status in Canonical System Image: Fix Committed Status in Mir: Fix Committed Status in Mir 0.26 series: Fix Committed Status in Unity System Compositor: Invalid Status in mir package in Ubuntu: Triaged Status in unity-system-compositor package in Ubuntu: Invalid Status in mir source package in Xenial: Fix Committed Status in unity-system-compositor source package in Xenial: Invalid Bug description: The Ubuntu Error Tracker has been receiving reports about a problem regarding unity-system-compositor. This problem was most recently seen with package version 0.9.1+17.04.20170216-0ubuntu1, the problem page at https://errors.ubuntu.com/problem/fcf5550475fb0478d6eb2a307f03705ef1ed398a 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 you can request it at http://forms.canonical.com/reports/. It seems that the configuration change is requested just a moment before the device gets removed. The change actions are serialized, depending on where there memory of mir::input::DefaultDevice is allocated the segfault either occurs inside the lambda or inside underlying mir::input::LibInputDevice in the platform. The activities on input dispatch device removal and reconfiguration are serialized inside the input thread, so we just need to clean the action queue (or have multiple queues) before removing the devices. To manage notifications about this bug go to: https://bugs.launchpad.net/canonical-devices-system-image/+bug/1672955/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1675357] Re: Mir sending key repeat events continually to nested shell after VT switch (causes Unity8 lockup for a while)
Tested version 0.26.3+16.04.20170510-0ubuntu1 ** Tags removed: verification-needed ** Tags added: verification-done -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to mir in Ubuntu. https://bugs.launchpad.net/bugs/1675357 Title: Mir sending key repeat events continually to nested shell after VT switch (causes Unity8 lockup for a while) Status in Canonical System Image: In Progress Status in Mir: Fix Committed Status in Mir 0.26 series: Fix Committed Status in mir package in Ubuntu: Triaged Status in qtmir package in Ubuntu: Invalid Status in unity8 package in Ubuntu: Invalid Status in mir source package in Xenial: Fix Committed Status in qtmir source package in Xenial: Invalid Status in unity8 source package in Xenial: Invalid Bug description: Steps: * log in to unity8 * Ctrl+Alt+F* to a different vt, or log in to a different user session * go back to the unity8 vt Expected: * session is locked, but working Current: * unity8 starts spinning for a time proportional to the period it was inactive * if it was inactive long enough, it doesn't seem to recover at all It seems it's "catching up" in some way, maybe with input, maybe frames. ProblemType: Bug DistroRelease: Ubuntu 17.04 Package: unity8 8.15+17.04.20170321-0ubuntu1 [origin: LP-PPA-ci-train-ppa-service-2555] ProcVersionSignature: Ubuntu 4.10.0-13.15-generic 4.10.1 Uname: Linux 4.10.0-13-generic x86_64 NonfreeKernelModules: zfs zunicode zavl zcommon znvpair ApportVersion: 2.20.4-0ubuntu2 Architecture: amd64 CurrentDesktop: Unity:Unity7 Date: Thu Mar 23 11:36:39 2017 InstallationDate: Installed on 2016-05-06 (320 days ago) InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 (20160420.1) SourcePackage: unity8 UpgradeStatus: Upgraded to zesty on 2016-11-22 (120 days ago) Causes: The mir::input::KeyRepeatDispatcher is running inside the nested mirserver even though there is another instance running inside the host server. A few months ago qtmir used to replace the key repeater by replacing mirs dispatcher. And key repeat is not disabled within the nested server. So both the host and the nested server are producing repeat events. Now due to a logic error inside mirserver the key repeat dispatcher is not hooked up to the input device hub when running inside the nested server. The input device hub would tell the key repeater when devices get removed - i.e. due to vt switching. So it never notices that the devices go away continues to produce those events indefinitely. This applies to all currently pressed buttons. I.e. you can open an edit field and press 'w' while simultaneously pressing Ctrl+Alt+FX to switch to another VT. On return 'w' will be repeated indefinitely. To manage notifications about this bug go to: https://bugs.launchpad.net/canonical-devices-system-image/+bug/1675357/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1685186] Re: [SRU] Mir needs to be updated to 0.26 in 16.04LTS
Tested version 0.26.3+16.04.20170510-0ubuntu1 -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to mir in Ubuntu. https://bugs.launchpad.net/bugs/1685186 Title: [SRU] Mir needs to be updated to 0.26 in 16.04LTS Status in mir package in Ubuntu: In Progress Status in mir source package in Xenial: Fix Committed Bug description: [Impact] Snap development using Mir has been using the "stable phone overlay" PPA which is both inconvenient and a legacy of the cancelled Unity8 project. It would greatly simplify things if Mir were updated in the Xenial archive. [Test Case] Build a Mir client snap (e.g. lp:~albaguirre/+snap/mir-client-demos) against "Primary Ubuntu Archive" and deploy as described in https://developer.ubuntu.com/en/snappy/guides/mir-snaps/ Expected: the client apps start and are visible on screen Actual: the client apps don't start and are not visible on screen [Regression Potential] Mir has two categories of dependent project: 1 Unity8 and unity-system-compositor "server" packages 2 toolkits and other "clients" of Mir "Server" packages from the archive will stop working in the LTS as they will continue using the earlier libmirserver.so.38 (from Mir 0.21) which doesn't work with the libmirclient.so.9 from Mir 0.26. This is unimportant as these packages were provided as an "early experience", not for serious use. "Client" packages are dependent only on libmirclient.so.9 which is ABI stable. The principle type of regression would be FTBFS where APIs have been deprecated in 0.26. The linked 0.26.3 release has these deprecations disabled for 16.04. The packages are available in silo: https://bileto.ubuntu.com/#/ticket/2736 notes: A recursive search or rdependencies identifies the following packages in category 1: camera-app-autopilot gallery-app-autopilot indicator-network-autopilot indicators-client qtdeclarative5-qtmir-plugin qtmir-android qtmir-desktop qtmir-tests ubuntu-desktop-mir ubuntu-experience-tests ubuntu-pocket-desktop ubuntu-push-autopilot ubuntu-touch ubuntu-touch-session unity8 unity8-autopilot unity8-desktop-session-mir unity-scope-click-autopilot unity-system-compositor unity-system-compositor-autopilot Anyone wanting these packages should switch to the "unity8-desktop- session" preview package in 17.04 where they are far more functional. [Alternatives] If we want to keep everything working in Xenial, we *could* bump the libmirclient SONAME to libmirclient.so.10. This would result in libmirclient9 being NBS, but continuing to work against the Mir servers available in 16.04[*] (until and unless they are rebuilt). However, this does not enable the desired result for IoT deployments of toolkits (GTK, Qt etc) and other clients working against servers (specifically miral-kiosk) built against the updated libraries. To work for IoT these would need to rebuilt from source - at which point they (and their dependencies) would stop working against the servers in category 1. [*] with the exception of the servers provided in mir-examples, these would only work with clients linking against libmirclient.so.10. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mir/+bug/1685186/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1672012] Re: Unity8 crashed right clicking on vlc [terminate called after throwing an instance of 'std::out_of_range' what(): map::at]
** Changed in: mir/0.26 Milestone: 0.26.3 => None -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to mir in Ubuntu. https://bugs.launchpad.net/bugs/1672012 Title: Unity8 crashed right clicking on vlc [terminate called after throwing an instance of 'std::out_of_range' what(): map::at] Status in Canonical System Image: Confirmed Status in Mir: Incomplete Status in Mir 0.26 series: Incomplete Status in MirAL: Incomplete Status in mir package in Ubuntu: Confirmed Status in miral package in Ubuntu: Confirmed Status in qtmir package in Ubuntu: Confirmed Status in unity8 package in Ubuntu: Confirmed Bug description: ubuntu 17.04 unity8 install vlc, launch it from app drawer or launcher try to use the menu, the menu shows for a split second and closes try to right click on vlc, here it just crashes/restarts unity8 To manage notifications about this bug go to: https://bugs.launchpad.net/canonical-devices-system-image/+bug/1672012/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1693921] [NEW] package initramfs-tools 0.125ubuntu9 failed to install/upgrade: subprocess installed post-installation script returned error exit status 127
Public bug reported: occurred after first boot and update ProblemType: Package DistroRelease: Ubuntu 17.04 Package: initramfs-tools 0.125ubuntu9 ProcVersionSignature: Ubuntu 4.10.0-21.23-generic 4.10.11 Uname: Linux 4.10.0-21-generic x86_64 ApportVersion: 2.20.4-0ubuntu4.1 Architecture: amd64 Date: Fri May 26 21:21:07 2017 DuplicateSignature: package:initramfs-tools:0.125ubuntu9 Processing triggers for initramfs-tools (0.125ubuntu9) ... /var/lib/dpkg/info/initramfs-tools.postinst: 19: /var/lib/dpkg/info/initramfs-tools.postinst: update-initramfs: not found dpkg: error processing package initramfs-tools (--configure): subprocess installed post-installation script returned error exit status 127 ErrorMessage: subprocess installed post-installation script returned error exit status 127 InstallationDate: Installed on 2017-05-26 (0 days ago) InstallationMedia: Systemback Live (ulinux17) - Release amd64 PackageArchitecture: all RelatedPackageVersions: dpkg 1.18.10ubuntu2 apt 1.4 SourcePackage: initramfs-tools Title: package initramfs-tools 0.125ubuntu9 failed to install/upgrade: subprocess installed post-installation script returned error exit status 127 UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: initramfs-tools (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-package zesty -- 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/1693921 Title: package initramfs-tools 0.125ubuntu9 failed to install/upgrade: subprocess installed post-installation script returned error exit status 127 Status in initramfs-tools package in Ubuntu: New Bug description: occurred after first boot and update ProblemType: Package DistroRelease: Ubuntu 17.04 Package: initramfs-tools 0.125ubuntu9 ProcVersionSignature: Ubuntu 4.10.0-21.23-generic 4.10.11 Uname: Linux 4.10.0-21-generic x86_64 ApportVersion: 2.20.4-0ubuntu4.1 Architecture: amd64 Date: Fri May 26 21:21:07 2017 DuplicateSignature: package:initramfs-tools:0.125ubuntu9 Processing triggers for initramfs-tools (0.125ubuntu9) ... /var/lib/dpkg/info/initramfs-tools.postinst: 19: /var/lib/dpkg/info/initramfs-tools.postinst: update-initramfs: not found dpkg: error processing package initramfs-tools (--configure): subprocess installed post-installation script returned error exit status 127 ErrorMessage: subprocess installed post-installation script returned error exit status 127 InstallationDate: Installed on 2017-05-26 (0 days ago) InstallationMedia: Systemback Live (ulinux17) - Release amd64 PackageArchitecture: all RelatedPackageVersions: dpkg 1.18.10ubuntu2 apt 1.4 SourcePackage: initramfs-tools Title: package initramfs-tools 0.125ubuntu9 failed to install/upgrade: subprocess installed post-installation script returned error exit status 127 UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/initramfs-tools/+bug/1693921/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1685186] Re: [SRU] Mir needs to be updated to 0.26 in 16.04LTS
** Changed in: mir (Ubuntu) Status: Fix Released => In Progress -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to mir in Ubuntu. https://bugs.launchpad.net/bugs/1685186 Title: [SRU] Mir needs to be updated to 0.26 in 16.04LTS Status in mir package in Ubuntu: In Progress Status in mir source package in Xenial: Incomplete Bug description: [Impact] Snap development using Mir has been using the "stable phone overlay" PPA which is both inconvenient and a legacy of the cancelled Unity8 project. It would greatly simplify things if Mir were updated in the Xenial archive. [Test Case] Build a Mir client snap (e.g. lp:~albaguirre/+snap/mir-client-demos) against "Primary Ubuntu Archive" and deploy as described in https://developer.ubuntu.com/en/snappy/guides/mir-snaps/ Expected: the client apps start and are visible on screen Actual: the client apps don't start and are not visible on screen [Regression Potential] Mir has two categories of dependent project: 1 Unity8 and unity-system-compositor "server" packages 2 toolkits and other "clients" of Mir "Server" packages from the archive will stop working in the LTS as they will continue using the earlier libmirserver.so.38 (from Mir 0.21) which doesn't work with the libmirclient.so.9 from Mir 0.26. This is unimportant as these packages were provided as an "early experience", not for serious use. "Client" packages are dependent only on libmirclient.so.9 which is ABI stable. The principle type of regression would be FTBFS where APIs have been deprecated in 0.26. The linked 0.26.3 release has these deprecations disabled for 16.04. The packages are available in silo: https://bileto.ubuntu.com/#/ticket/2736 notes: A recursive search or rdependencies identifies the following packages in category 1: camera-app-autopilot gallery-app-autopilot indicator-network-autopilot indicators-client qtdeclarative5-qtmir-plugin qtmir-android qtmir-desktop qtmir-tests ubuntu-desktop-mir ubuntu-experience-tests ubuntu-pocket-desktop ubuntu-push-autopilot ubuntu-touch ubuntu-touch-session unity8 unity8-autopilot unity8-desktop-session-mir unity-scope-click-autopilot unity-system-compositor unity-system-compositor-autopilot Anyone wanting these packages should switch to the "unity8-desktop- session" preview package in 17.04 where they are far more functional. [Alternatives] If we want to keep everything working in Xenial, we *could* bump the libmirclient SONAME to libmirclient.so.10. This would result in libmirclient9 being NBS, but continuing to work against the Mir servers available in 16.04[*] (until and unless they are rebuilt). However, this does not enable the desired result for IoT deployments of toolkits (GTK, Qt etc) and other clients working against servers (specifically miral-kiosk) built against the updated libraries. To work for IoT these would need to rebuilt from source - at which point they (and their dependencies) would stop working against the servers in category 1. [*] with the exception of the servers provided in mir-examples, these would only work with clients linking against libmirclient.so.10. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mir/+bug/1685186/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1685186] Re: [SRU] Mir needs to be updated to 0.26 in 16.04LTS
Added Zesty and Yakkety as they need to have at least the version in Xenial. For Zesty this is a bugfix update, on Yakkety it has the same effect as on Xenial (of making some "early experience" downstreams a little less useful). ** Branch unlinked: lp:~alan-griffiths/mir/optional-deprecations ** Branch linked: lp:~alan-griffiths/mir/0.26.3-xenial ** Changed in: mir (Ubuntu) Status: Fix Released => In Progress -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to mir in Ubuntu. https://bugs.launchpad.net/bugs/1685186 Title: [SRU] Mir needs to be updated to 0.26 in 16.04LTS Status in mir package in Ubuntu: In Progress Status in mir source package in Xenial: In Progress Bug description: [Impact] Snap development using Mir has been using the "stable phone overlay" PPA which is both inconvenient and a legacy of the cancelled Unity8 project. It would greatly simplify things if Mir were updated in the Xenial archive. [Test Case] Build a Mir client snap (e.g. lp:~albaguirre/+snap/mir-client-demos) against "Primary Ubuntu Archive" and deploy as described in https://developer.ubuntu.com/en/snappy/guides/mir-snaps/ Expected: the client apps start and are visible on screen Actual: the client apps don't start and are not visible on screen [Regression Potential] Mir has two categories of dependent project: 1 Unity8 and unity-system-compositor "server" packages 2 toolkits and other "clients" of Mir "Server" packages from the archive will stop working in the LTS as they will continue using the earlier libmirserver.so.38 (from Mir 0.21) which doesn't work with the libmirclient.so.9 from Mir 0.26. This is unimportant as these packages were provided as an "early experience", not for serious use. "Client" packages are dependent only on libmirclient.so.9 which is ABI stable. The principle type of regression would be FTBFS where APIs have been deprecated in 0.26. The linked 0.26.3 release has these deprecations disabled for 16.04. The packages are available in silo: https://bileto.ubuntu.com/#/ticket/2736 notes: A recursive search or rdependencies identifies the following packages in category 1: camera-app-autopilot gallery-app-autopilot indicator-network-autopilot indicators-client qtdeclarative5-qtmir-plugin qtmir-android qtmir-desktop qtmir-tests ubuntu-desktop-mir ubuntu-experience-tests ubuntu-pocket-desktop ubuntu-push-autopilot ubuntu-touch ubuntu-touch-session unity8 unity8-autopilot unity8-desktop-session-mir unity-scope-click-autopilot unity-system-compositor unity-system-compositor-autopilot Anyone wanting these packages should switch to the "unity8-desktop- session" preview package in 17.04 where they are far more functional. [Alternatives] If we want to keep everything working in Xenial, we *could* bump the libmirclient SONAME to libmirclient.so.10. This would result in libmirclient9 being NBS, but continuing to work against the Mir servers available in 16.04[*] (until and unless they are rebuilt). However, this does not enable the desired result for IoT deployments of toolkits (GTK, Qt etc) and other clients working against servers (specifically miral-kiosk) built against the updated libraries. To work for IoT these would need to rebuilt from source - at which point they (and their dependencies) would stop working against the servers in category 1. [*] with the exception of the servers provided in mir-examples, these would only work with clients linking against libmirclient.so.10. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mir/+bug/1685186/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 713839] Re: keys in trusted.gpg
*** This bug is a duplicate of bug 1182932 ***
https://bugs.launchpad.net/bugs/1182932
The approach suggested here appears to have been implemented in Xenial
(Ubuntu 16.04).
After adding the Ansible PPA, I have a file
`/etc/apt/trusted.gpg.d/ansible_ubuntu_ansible.gpg`. I can also see the
Ansible key is not included in the output of:
gpg --list-keys --no-default-keyring --keyring /etc/apt/trusted.gpg
** This bug has been marked a duplicate of bug 1182932
Add PPA keys to /etc/apt/trusted.gpg.d/{owner}-{ppa}.gpg
--
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/713839
Title:
keys in trusted.gpg
Status in software-properties package in Ubuntu:
Confirmed
Bug description:
The apt-add-repository adds a new file in /etc/apt/sources.list.d and
adds the key into /etc/apt/trusted.gpg file. Why does it not use
/etc/apt/trusted.gpg.d dir?
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/software-properties/+bug/713839/+subscriptions
--
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1685186] Re: [SRU] Mir needs to be updated to 0.26 in 16.04LTS
Set back to verification-needed as we now have the binaries for all the supported releases ** Tags removed: verification-failed ** Tags added: verification-needed -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to mir in Ubuntu. https://bugs.launchpad.net/bugs/1685186 Title: [SRU] Mir needs to be updated to 0.26 in 16.04LTS Status in mir package in Ubuntu: In Progress Status in mir source package in Xenial: In Progress Status in mir source package in Yakkety: In Progress Status in mir source package in Zesty: In Progress Bug description: [Impact] Snap development using Mir has been using the "stable phone overlay" PPA which is both inconvenient and a legacy of the cancelled Unity8 project. It would greatly simplify things if Mir were updated in the Xenial archive. [Test Case] Build a Mir client snap (e.g. lp:~albaguirre/+snap/mir-client-demos) against "Primary Ubuntu Archive" and deploy as described in https://developer.ubuntu.com/en/snappy/guides/mir-snaps/ Expected: the client apps start and are visible on screen Actual: the client apps don't start and are not visible on screen [Regression Potential] Mir has two categories of dependent project: 1 Unity8 and unity-system-compositor "server" packages 2 toolkits and other "clients" of Mir "Server" packages from the archive will stop working in the LTS as they will continue using the earlier libmirserver.so.38 (from Mir 0.21) which doesn't work with the libmirclient.so.9 from Mir 0.26. This is unimportant as these packages were provided as an "early experience", not for serious use. "Client" packages are dependent only on libmirclient.so.9 which is ABI stable. The principle type of regression would be FTBFS where APIs have been deprecated in 0.26. The linked 0.26.3 release has these deprecations disabled for 16.04. The packages are available in silo: https://bileto.ubuntu.com/#/ticket/2736 notes: A recursive search or rdependencies identifies the following packages in category 1: camera-app-autopilot gallery-app-autopilot indicator-network-autopilot indicators-client qtdeclarative5-qtmir-plugin qtmir-android qtmir-desktop qtmir-tests ubuntu-desktop-mir ubuntu-experience-tests ubuntu-pocket-desktop ubuntu-push-autopilot ubuntu-touch ubuntu-touch-session unity8 unity8-autopilot unity8-desktop-session-mir unity-scope-click-autopilot unity-system-compositor unity-system-compositor-autopilot Anyone wanting these packages should switch to the "unity8-desktop- session" preview package in 17.04 where they are far more functional. [Alternatives] If we want to keep everything working in Xenial, we *could* bump the libmirclient SONAME to libmirclient.so.10. This would result in libmirclient9 being NBS, but continuing to work against the Mir servers available in 16.04[*] (until and unless they are rebuilt). However, this does not enable the desired result for IoT deployments of toolkits (GTK, Qt etc) and other clients working against servers (specifically miral-kiosk) built against the updated libraries. To work for IoT these would need to rebuilt from source - at which point they (and their dependencies) would stop working against the servers in category 1. [*] with the exception of the servers provided in mir-examples, these would only work with clients linking against libmirclient.so.10. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mir/+bug/1685186/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1696091] [NEW] When the "target" demo recieves mir_event_type_close_window it fails to exit
Public bug reported: Start mir_demo_client_target under mir_proving_server (or miral-shell, or miral-kiosk) Ensure it has focus and press Alt+F4 expect: the window disappears and the program exits actual: the window disappears and the program hangs It appears that the shutdown_handler() thread is waiting on sigwait() and the main thread is trying to join. (So, for example, Ctrl-C will still exit OK) ** Affects: mir (Ubuntu) Importance: Low Status: New -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to mir in Ubuntu. https://bugs.launchpad.net/bugs/1696091 Title: When the "target" demo recieves mir_event_type_close_window it fails to exit Status in mir package in Ubuntu: New Bug description: Start mir_demo_client_target under mir_proving_server (or miral-shell, or miral-kiosk) Ensure it has focus and press Alt+F4 expect: the window disappears and the program exits actual: the window disappears and the program hangs It appears that the shutdown_handler() thread is waiting on sigwait() and the main thread is trying to join. (So, for example, Ctrl-C will still exit OK) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mir/+bug/1696091/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1696091] Re: When the "target" demo receives mir_event_type_close_window it fails to exit
** Summary changed: - When the "target" demo recieves mir_event_type_close_window it fails to exit + When the "target" demo receives mir_event_type_close_window it fails to exit -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to mir in Ubuntu. https://bugs.launchpad.net/bugs/1696091 Title: When the "target" demo receives mir_event_type_close_window it fails to exit Status in mir package in Ubuntu: New Bug description: Start mir_demo_client_target under mir_proving_server (or miral-shell, or miral-kiosk) Ensure it has focus and press Alt+F4 expect: the window disappears and the program exits actual: the window disappears and the program hangs It appears that the shutdown_handler() thread is waiting on sigwait() and the main thread is trying to join. (So, for example, Ctrl-C will still exit OK) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mir/+bug/1696091/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1696978] Re: Mir locking up when switching VTs
** Changed in: mir Status: New => Confirmed ** Changed in: mir (Ubuntu) Status: New => Confirmed ** Changed in: mir Importance: Undecided => Low ** Changed in: mir (Ubuntu) Importance: Undecided => Low -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to mir in Ubuntu. https://bugs.launchpad.net/bugs/1696978 Title: Mir locking up when switching VTs Status in Mir: Confirmed Status in mir package in Ubuntu: Confirmed Bug description: Steps: * stop lightdm * follow https://wiki.ubuntu.com/Process/Merges/TestPlans/Mir#Test_Plan Expected: * Switching to Mir VT works Current: * When trying to switch to the Mir VT, Mir locks up trying to render, never completing, and not handling Ctrl+Alt+F* presses To manage notifications about this bug go to: https://bugs.launchpad.net/mir/+bug/1696978/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1696978] Re: Mir locking up when switching VTs
The essential step here is stopping lightdm. After which it seems Mir fails to restart compositing when the VT switches back. This scenario is low priority. ** Changed in: mir Status: Incomplete => Confirmed ** Changed in: mir (Ubuntu) Status: Incomplete => Confirmed ** Changed in: mir Importance: High => Low ** Changed in: mir (Ubuntu) Importance: High => Low -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to mir in Ubuntu. https://bugs.launchpad.net/bugs/1696978 Title: Mir locking up when switching VTs Status in Mir: Confirmed Status in mir package in Ubuntu: Confirmed Bug description: Steps: * stop lightdm * follow https://wiki.ubuntu.com/Process/Merges/TestPlans/Mir#Test_Plan Expected: * Switching to Mir VT works Current: * When trying to switch to the Mir VT, Mir locks up trying to render, never completing, and not handling Ctrl+Alt+F* presses To manage notifications about this bug go to: https://bugs.launchpad.net/mir/+bug/1696978/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1672955] Re: unity-system-compositor crashed with SIGSEGV in libinput_device_config_accel_is_available() from libinput_device_config_accel_set_speed() from mir::input::evdev::Lib
** Changed in: canonical-devices-system-image Status: Fix Committed => Fix Released ** Changed in: canonical-devices-system-image Assignee: Stephen M. Webb (bregma) => (unassigned) -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to mir in Ubuntu. https://bugs.launchpad.net/bugs/1672955 Title: unity-system-compositor crashed with SIGSEGV in libinput_device_config_accel_is_available() from libinput_device_config_accel_set_speed() from mir::input::evdev::LibInputDevice::apply_settings() Status in Canonical System Image: Fix Released Status in Mir: Fix Committed Status in Mir 0.26 series: Fix Released Status in Unity System Compositor: Invalid Status in mir package in Ubuntu: Fix Released Status in unity-system-compositor package in Ubuntu: Invalid Status in mir source package in Xenial: Fix Released Status in unity-system-compositor source package in Xenial: Invalid Status in mir source package in Yakkety: Fix Released Status in mir source package in Zesty: Fix Released Bug description: The Ubuntu Error Tracker has been receiving reports about a problem regarding unity-system-compositor. This problem was most recently seen with package version 0.9.1+17.04.20170216-0ubuntu1, the problem page at https://errors.ubuntu.com/problem/fcf5550475fb0478d6eb2a307f03705ef1ed398a 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 you can request it at http://forms.canonical.com/reports/. It seems that the configuration change is requested just a moment before the device gets removed. The change actions are serialized, depending on where there memory of mir::input::DefaultDevice is allocated the segfault either occurs inside the lambda or inside underlying mir::input::LibInputDevice in the platform. The activities on input dispatch device removal and reconfiguration are serialized inside the input thread, so we just need to clean the action queue (or have multiple queues) before removing the devices. To manage notifications about this bug go to: https://bugs.launchpad.net/canonical-devices-system-image/+bug/1672955/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1668053] Re: [unity8] kate, impossible to close "Print Preview" window
>From my perspective it is incorrect to say 'impossible to close "Print Preview" window' I can run kate in miral-shell, open the print-preview and close it (Alt-F4) fine. Now I do agree it seems daft that there's neither a "Close" button (or equivalent) on the window, nor an "X" in the titlebar, but isn't that down to a design issue? -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to unity8 in Ubuntu. https://bugs.launchpad.net/bugs/1668053 Title: [unity8] kate, impossible to close "Print Preview" window Status in Canonical System Image: New Status in Mir: Incomplete Status in Ubuntu UX: New Status in qtmir package in Ubuntu: Confirmed Status in qtubuntu package in Ubuntu: Confirmed Status in unity8 package in Ubuntu: In Progress Bug description: ubuntu 17.04 Unity 8 [unity8] kate, impossible to close "Print Preview" window see attached screenshot Print Preview window doesn't have windows controls or a close button Launch Kate, from the menu File > Print Preview try to close the window, you can't because doh To manage notifications about this bug go to: https://bugs.launchpad.net/canonical-devices-system-image/+bug/1668053/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1655997] Re: [gtk] Save as dialog: dropdown menu surface positioned wrong
Not happening with the latest gtk to land in zesty ** Changed in: miral Status: Incomplete => Invalid -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to gtk+3.0 in Ubuntu. https://bugs.launchpad.net/bugs/1655997 Title: [gtk] Save as dialog: dropdown menu surface positioned wrong Status in GTK+: Fix Committed Status in MirAL: Invalid Status in gtk+3.0 package in Ubuntu: New Bug description: Running miral-shell and gedit: 1. Burger-menu -> Save As 2. Click the "Character encoding" or "Line ending" or "All files" dropdowns Bug: child surfaces are positioned incorrectly, should be under/over the widget that invoked them To manage notifications about this bug go to: https://bugs.launchpad.net/gtk/+bug/1655997/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1668467] Re: gnome-calculator, you can open the Preferences window multiple times, making the window transparent the second time
Not happening in miral-shell with the latest gtk to land in Zesty ** Changed in: miral (Ubuntu) Status: Incomplete => Invalid ** Changed in: miral Status: Incomplete => Invalid -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to unity8 in Ubuntu. https://bugs.launchpad.net/bugs/1668467 Title: gnome-calculator, you can open the Preferences window multiple times, making the window transparent the second time Status in Canonical System Image: Confirmed Status in MirAL: Invalid Status in gtk+3.0 package in Ubuntu: Confirmed Status in miral package in Ubuntu: Invalid Status in qtmir package in Ubuntu: Incomplete Status in unity8 package in Ubuntu: Incomplete Bug description: ubuntu 17.04 unity8 gnome-calculator, you can open the Preferences window many times, making the window transparent the second time (see screenshot) it doesn't work with About or Keyboard Shortcuts, only with Preferences. To manage notifications about this bug go to: https://bugs.launchpad.net/canonical-devices-system-image/+bug/1668467/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1675138] Re: Please transition to Boost 1.62
Resolved on #ubuntu-mir... if you are fine with people uploading the package directly to the archive we can work it out, i.e. I upload a -2 as soon at 0.26.2-1 is uploaded, but then your next upload done through whatever CI should contain it. mapreri: that would work for me I have no idea how bileto (or whatever kind of CI/landing system) you are using work oh, great so, what would be the timing for 0.26.2 to land? :) mapreri: out of my hands, first QA need to approve and then someone needs to push to archive. But I'd guess the next day or two. that works just fine I'll arrange the -2 upload, will you please merge it in 0.26.3 in the meantime? AFAIK 0.26.3 doesn't exist (and likely won't). But I'll take care of it in that contingency. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to mir in Ubuntu. https://bugs.launchpad.net/bugs/1675138 Title: Please transition to Boost 1.62 Status in Mir: Fix Committed Status in Mir 0.26 series: New Status in mir package in Ubuntu: Triaged Bug description: There is an ongoing transition to Boost 1.62 and mir is one of the last affected packages: http://people.canonical.com/~ubuntu-archive/transitions/html/boost1.62.html To manage notifications about this bug go to: https://bugs.launchpad.net/mir/+bug/1675138/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1669524] Re: GTK window functions `Always on Top, Move and Resize' don't work in Mir/Unity8
** Changed in: mir Assignee: (unassigned) => Alan Griffiths (alan-griffiths) ** Changed in: mir Status: Triaged => In Progress ** Also affects: miral Importance: Undecided Status: New ** Changed in: miral Status: New => Triaged ** Changed in: miral Importance: Undecided => High -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to gtk+3.0 in Ubuntu. https://bugs.launchpad.net/bugs/1669524 Title: GTK window functions `Always on Top, Move and Resize' don't work in Mir/Unity8 Status in Canonical System Image: Confirmed Status in Mir: In Progress Status in MirAL: Triaged Status in gtk+3.0 package in Ubuntu: Confirmed Status in mir package in Ubuntu: Triaged Status in qtmir package in Ubuntu: Confirmed Status in unity8 package in Ubuntu: Confirmed Bug description: ubuntu 17.04 unity8 [unity8] Always on Top, Move and Resize doesn't work open solitaire, right click on the title bar (see attachement) and then select Always on Top. the app doesn't stay on top. same with Move and Resize, does nothing To manage notifications about this bug go to: https://bugs.launchpad.net/canonical-devices-system-image/+bug/1669524/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1669524] Re: GTK window functions `Always on Top, Move and Resize' don't work in Mir/Unity8
** Branch linked: lp:~alan-griffiths/mir/client-initiates-user-move-and- resize -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to gtk+3.0 in Ubuntu. https://bugs.launchpad.net/bugs/1669524 Title: GTK window functions `Always on Top, Move and Resize' don't work in Mir/Unity8 Status in Canonical System Image: Confirmed Status in Mir: In Progress Status in MirAL: Triaged Status in gtk+3.0 package in Ubuntu: Confirmed Status in mir package in Ubuntu: Triaged Status in qtmir package in Ubuntu: Confirmed Status in unity8 package in Ubuntu: Confirmed Bug description: ubuntu 17.04 unity8 [unity8] Always on Top, Move and Resize doesn't work open solitaire, right click on the title bar (see attachement) and then select Always on Top. the app doesn't stay on top. same with Move and Resize, does nothing To manage notifications about this bug go to: https://bugs.launchpad.net/canonical-devices-system-image/+bug/1669524/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1669524] Re: GTK window functions `Always on Top, Move and Resize' don't work in Mir/Unity8
I think there are distinct cases here: Case 1: (easy I hope) The client initiating a user-drag/resize is analogous to the existing input focus request. Vis: void mir_window_request_user_move(MirWindow* window, MirCookie const* cookie); void mir_window_request_user_resize(MirWindow* window, MirCookie const* cookie); Should be passed to the server, validated and handled by the WM policy exactly the same as: void mir_window_raise(MirWindow* window, MirCookie const* cookie); How the client decides on calling these (via a menu or not) isn't really the issue. This is addressed by lp:~alan-griffiths/mir/client-initiates-user-move- and-resize/+merge/320917 Case 2: "Always on top" would be a property of a window, the client could set (or reset) this on the MirWindowSpec. The WM policy gets to decide whether (and how) to respect this property. There's currently no support for such a property in libmirserver's SurfaceStack - so addressing that would be a pre-requisite to introducing such a property. Case 3: (comment #6) If there were some generic "window manager menu" that toolkits could request then that might be requested with a similar mechanism to case 1. But I've not seen a requirement for this (yet). -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to gtk+3.0 in Ubuntu. https://bugs.launchpad.net/bugs/1669524 Title: GTK window functions `Always on Top, Move and Resize' don't work in Mir/Unity8 Status in Canonical System Image: Confirmed Status in Mir: In Progress Status in MirAL: Triaged Status in gtk+3.0 package in Ubuntu: Confirmed Status in mir package in Ubuntu: Triaged Status in qtmir package in Ubuntu: Confirmed Status in unity8 package in Ubuntu: Confirmed Bug description: ubuntu 17.04 unity8 [unity8] Always on Top, Move and Resize doesn't work open solitaire, right click on the title bar (see attachement) and then select Always on Top. the app doesn't stay on top. same with Move and Resize, does nothing To manage notifications about this bug go to: https://bugs.launchpad.net/canonical-devices-system-image/+bug/1669524/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1665286] Re: [unity8] A ghost (shadow only) window opens with some app windows/menus
** Changed in: mir Status: Incomplete => Invalid ** Changed in: miral Status: Incomplete => Invalid ** Changed in: mir (Ubuntu) Status: Incomplete => Invalid ** Changed in: miral (Ubuntu) Status: Incomplete => Invalid -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to qtubuntu in Ubuntu. https://bugs.launchpad.net/bugs/1665286 Title: [unity8] A ghost (shadow only) window opens with some app windows/menus Status in Canonical System Image: Fix Released Status in Mir: Invalid Status in MirAL: Invalid Status in mir package in Ubuntu: Invalid Status in miral package in Ubuntu: Invalid Status in qtubuntu package in Ubuntu: Invalid Status in unity8 package in Ubuntu: Fix Released Bug description: ubuntu 17.04 unity8 - install tiled, apt install tiled - Add "X-Ubuntu-XMir-Enable=false" to /usr/share/applications/tiled.desktop so that it doesn't get launched inside an xmir wrapper - launch tiled you'll see a transparent window opened beneath the main window called "Object Types Editor" see attached screenshot To manage notifications about this bug go to: https://bugs.launchpad.net/canonical-devices-system-image/+bug/1665286/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1625397] Re: [gtk] Focus is stuck on the save as window vs the main window
** Changed in: miral Status: Incomplete => Invalid -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to gtk+3.0 in Ubuntu. https://bugs.launchpad.net/bugs/1625397 Title: [gtk] Focus is stuck on the save as window vs the main window Status in GTK+: Fix Released Status in MirAL: Invalid Status in gtk+3.0 package in Ubuntu: Fix Released Bug description: To reproduce: Open gedit in miral click save (the window should pop up) click back on the main window leaving the save window open type Expected: Text to appear in the main top most window Result: Text appears on the save as window behind the main window. I checked with mir_demo_server and same issue so this could be a gtk bug it self. Added by alan_g: As described in comment #5 this seems to be mostly a gtk-mir problem. (Where are they filed?) But there is a MirAL component (because even if gtk-mir was right, this problem would sill be seen). Added later by alan_g: The problem mentioned in lp:1626659 has been committed, everything left is a gtk-mir issue. To manage notifications about this bug go to: https://bugs.launchpad.net/gtk/+bug/1625397/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1669524] Re: GTK window functions `Always on Top, Move and Resize' don't work in Mir/Unity8
The branch that landed was only part of the solution to one of the problems ** Changed in: mir Status: Fix Committed => In Progress -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to gtk+3.0 in Ubuntu. https://bugs.launchpad.net/bugs/1669524 Title: GTK window functions `Always on Top, Move and Resize' don't work in Mir/Unity8 Status in Canonical System Image: In Progress Status in Mir: In Progress Status in MirAL: Triaged Status in gtk+3.0 package in Ubuntu: Confirmed Status in mir package in Ubuntu: Triaged Status in qtmir package in Ubuntu: Confirmed Status in unity8 package in Ubuntu: Confirmed Bug description: ubuntu 17.04 unity8 [unity8] Always on Top, Move and Resize doesn't work open solitaire, right click on the title bar (see attachement) and then select Always on Top. the app doesn't stay on top. same with Move and Resize, does nothing To manage notifications about this bug go to: https://bugs.launchpad.net/canonical-devices-system-image/+bug/1669524/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1669524] Re: GTK window functions `Always on Top, Move and Resize' don't work in Mir/Unity8
** Branch linked: lp:~alan-griffiths/mir/server-support-for-client- initiates-move -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to gtk+3.0 in Ubuntu. https://bugs.launchpad.net/bugs/1669524 Title: GTK window functions `Always on Top, Move and Resize' don't work in Mir/Unity8 Status in Canonical System Image: In Progress Status in Mir: In Progress Status in MirAL: Triaged Status in gtk+3.0 package in Ubuntu: Confirmed Status in mir package in Ubuntu: Triaged Status in qtmir package in Ubuntu: Confirmed Status in unity8 package in Ubuntu: Confirmed Bug description: ubuntu 17.04 unity8 [unity8] Always on Top, Move and Resize doesn't work open solitaire, right click on the title bar (see attachement) and then select Always on Top. the app doesn't stay on top. same with Move and Resize, does nothing To manage notifications about this bug go to: https://bugs.launchpad.net/canonical-devices-system-image/+bug/1669524/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1676879] Re: Broken stack of modal dialogs
There's no clear steps to reproduce, so I may have missed something. But I can't get these symptoms with miral-app. ** Changed in: miral Status: New => Incomplete ** Changed in: miral (Ubuntu) Status: Confirmed => Incomplete -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to qtubuntu in Ubuntu. https://bugs.launchpad.net/bugs/1676879 Title: Broken stack of modal dialogs Status in Canonical System Image: New Status in MirAL: Incomplete Status in miral package in Ubuntu: Incomplete Status in qtubuntu package in Ubuntu: Confirmed Status in unity8 package in Ubuntu: Confirmed Bug description: When multiple modal dialogs are stacked on top of each other, the topmost one is missing the window decoration (see https://imgur.com/0kVtLUB). Furthermore, after closing it, the middle modal dialog is hidden, preventing input from the main window. Launcher pips and context menu suggests the dialog is still there, albeit hidden. Results in a crash of the app after a few seconds. To manage notifications about this bug go to: https://bugs.launchpad.net/canonical-devices-system-image/+bug/1676879/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1685186] [NEW] Mir needs to be updated in 16.04 and the dependency tree trimmed
Public bug reported: Snap development using Mir has been using the "stable phone overlay" PPA which is both inconvenient and a legacy of the cancelled Unity8 project. It would greatly simplify things if Mir were updated in the Xenial archive. Mir has two categories of dependent project: 1 packages related to Unity8 (and unity-system-compositor) 2 toolkits and other "clients" of Mir We should remove the first category as it is not helpful to carry these in the LTS. The second category is dependent only on libmirclient which is ABI stable ** Affects: mir (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to mir in Ubuntu. https://bugs.launchpad.net/bugs/1685186 Title: Mir needs to be updated in 16.04 and the dependency tree trimmed Status in mir package in Ubuntu: New Bug description: Snap development using Mir has been using the "stable phone overlay" PPA which is both inconvenient and a legacy of the cancelled Unity8 project. It would greatly simplify things if Mir were updated in the Xenial archive. Mir has two categories of dependent project: 1 packages related to Unity8 (and unity-system-compositor) 2 toolkits and other "clients" of Mir We should remove the first category as it is not helpful to carry these in the LTS. The second category is dependent only on libmirclient which is ABI stable To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mir/+bug/1685186/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1685186] Re: Mir needs to be updated in 16.04 and the dependency tree trimmed
** Description changed: Snap development using Mir has been using the "stable phone overlay" PPA which is both inconvenient and a legacy of the cancelled Unity8 project. It would greatly simplify things if Mir were updated in the Xenial archive. Mir has two categories of dependent project: - 1 packages related to Unity8 (and unity-system-compositor) - 2 toolkits and other "clients" of Mir + 1 packages related to Unity8 (and unity-system-compositor) + 2 toolkits and other "clients" of Mir We should remove the first category as it is not helpful to carry these in the LTS. The second category is dependent only on libmirclient which is ABI stable + + notes: + + A recursive search or rdependencies identifies the following packages in + category 1: + + camera-app-autopilot + gallery-app-autopilot + indicator-network-autopilot + indicators-client + python3-mir-perf-framework + qtdeclarative5-qtmir-plugin + qtmir-android + qtmir-desktop + qtmir-tests + ubuntu-desktop-mir + ubuntu-experience-tests + ubuntu-pocket-desktop + ubuntu-push-autopilot + ubuntu-touch + ubuntu-touch-session + unity8 + unity8-autopilot + unity8-desktop-session-mir + unity-scope-click-autopilot + unity-system-compositor + unity-system-compositor-autopilot ** Changed in: mir (Ubuntu) Assignee: (unassigned) => Alan Griffiths (alan-griffiths) -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to mir in Ubuntu. https://bugs.launchpad.net/bugs/1685186 Title: Mir needs to be updated in 16.04 and the dependency tree trimmed Status in mir package in Ubuntu: New Bug description: Snap development using Mir has been using the "stable phone overlay" PPA which is both inconvenient and a legacy of the cancelled Unity8 project. It would greatly simplify things if Mir were updated in the Xenial archive. Mir has two categories of dependent project: 1 packages related to Unity8 (and unity-system-compositor) 2 toolkits and other "clients" of Mir We should remove the first category as it is not helpful to carry these in the LTS. The second category is dependent only on libmirclient which is ABI stable notes: A recursive search or rdependencies identifies the following packages in category 1: camera-app-autopilot gallery-app-autopilot indicator-network-autopilot indicators-client python3-mir-perf-framework qtdeclarative5-qtmir-plugin qtmir-android qtmir-desktop qtmir-tests ubuntu-desktop-mir ubuntu-experience-tests ubuntu-pocket-desktop ubuntu-push-autopilot ubuntu-touch ubuntu-touch-session unity8 unity8-autopilot unity8-desktop-session-mir unity-scope-click-autopilot unity-system-compositor unity-system-compositor-autopilot To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mir/+bug/1685186/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
