[Touch-packages] [Bug 1820944] [NEW] package openssh-server 1:7.2p2-4ubuntu2.8 failed to install/upgrade: подпроцесс установлен сценарий post-installation возвратил код ошибки 2
Public bug reported: I tried to command "sudo apt-get install ssh" ProblemType: Package DistroRelease: Ubuntu 16.04 Package: openssh-server 1:7.2p2-4ubuntu2.8 ProcVersionSignature: Ubuntu 4.15.0-46.49~16.04.1-generic 4.15.18 Uname: Linux 4.15.0-46-generic x86_64 ApportVersion: 2.20.1-0ubuntu2.18 Architecture: amd64 Date: Tue Mar 19 10:15:17 2019 ErrorMessage: подпроцесс установлен сценарий post-installation возвратил код ошибки 2 InstallationDate: Installed on 2018-08-11 (220 days ago) InstallationMedia: Ubuntu 16.04.4 LTS "Xenial Xerus" - Release amd64 (20180228) RelatedPackageVersions: dpkg 1.18.4ubuntu1.5 apt 1.2.29ubuntu0.1 SSHDConfig: Error: command ['/usr/sbin/sshd', '-T'] failed with exit code 1: /etc/ssh/sshd_config: No such file or directory SourcePackage: openssh Title: package openssh-server 1:7.2p2-4ubuntu2.8 failed to install/upgrade: подпроцесс установлен сценарий post-installation возвратил код ошибки 2 UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: openssh (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 openssh in Ubuntu. https://bugs.launchpad.net/bugs/1820944 Title: package openssh-server 1:7.2p2-4ubuntu2.8 failed to install/upgrade: подпроцесс установлен сценарий post-installation возвратил код ошибки 2 Status in openssh package in Ubuntu: New Bug description: I tried to command "sudo apt-get install ssh" ProblemType: Package DistroRelease: Ubuntu 16.04 Package: openssh-server 1:7.2p2-4ubuntu2.8 ProcVersionSignature: Ubuntu 4.15.0-46.49~16.04.1-generic 4.15.18 Uname: Linux 4.15.0-46-generic x86_64 ApportVersion: 2.20.1-0ubuntu2.18 Architecture: amd64 Date: Tue Mar 19 10:15:17 2019 ErrorMessage: подпроцесс установлен сценарий post-installation возвратил код ошибки 2 InstallationDate: Installed on 2018-08-11 (220 days ago) InstallationMedia: Ubuntu 16.04.4 LTS "Xenial Xerus" - Release amd64 (20180228) RelatedPackageVersions: dpkg 1.18.4ubuntu1.5 apt 1.2.29ubuntu0.1 SSHDConfig: Error: command ['/usr/sbin/sshd', '-T'] failed with exit code 1: /etc/ssh/sshd_config: No such file or directory SourcePackage: openssh Title: package openssh-server 1:7.2p2-4ubuntu2.8 failed to install/upgrade: подпроцесс установлен сценарий post-installation возвратил код ошибки 2 UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/openssh/+bug/1820944/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1820943] Re: no xorg
Thank you for taking the time to report this bug and helping to make Ubuntu better. It sounds like some part of the system has crashed. To help us find the cause of the crash please follow these steps: 1. Look in /var/crash for crash files and if found run: ubuntu-bug YOURFILE.crash Then tell us the ID of the newly-created bug. 2. If step 1 failed then look at https://errors.ubuntu.com/user/ID where ID is the content of file /var/lib/whoopsie/whoopsie-id on the machine. Do you find any links to recent problems on that page? If so then please send the links to us. 3. If step 2 also failed then apply the workaround from bug 994921, reboot, reproduce the crash, and retry step 1. Please take care to avoid attaching .crash files to bugs as we are unable to process them as file attachments. It would also be a security risk for yourself. ** Package changed: xorg (Ubuntu) => xorg-server (Ubuntu) ** Changed in: xorg-server (Ubuntu) Status: New => Incomplete ** Tags added: amdgpu -- 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/1820943 Title: Xorg crashes [AMDGPU(0): Failed to open amdgpu hybrid version] Status in xorg-server package in Ubuntu: Incomplete Status in xserver-xorg-video-amdgpu package in Ubuntu: Incomplete Bug description: Not able to get GUI mode in ubuntu 18.04 ... 16.04 was fine ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: xorg (not installed) ProcVersionSignature: Ubuntu 4.15.0-46.49-generic 4.15.18 Uname: Linux 4.15.0-46-generic x86_64 NonfreeKernelModules: edac_mce_amd wmi_bmof amdkfd amd_iommu_v2 amdgpu chash snd_hda_codec_realtek snd_hda_codec_hdmi snd_hda_codec_generic snd_hda_intel snd_hda_codec snd_hda_core k10temp ccp mac_hid wmi shpchp i2c_piix4 r8169 gpio_amdpt gpio_generic ApportVersion: 2.20.9-0ubuntu7.6 Architecture: amd64 Date: Tue Mar 19 20:07:07 2019 DistUpgraded: 2019-03-12 10:43:47,713 DEBUG Running PostInstallScript: './xorg_fix_proprietary.py' DistroCodename: bionic DistroVariant: ubuntu GraphicsCard: Advanced Micro Devices, Inc. [AMD/ATI] Baffin [Radeon RX 550 640SP / RX 560/560X] [1002:67ff] (rev cf) (prog-if 00 [VGA controller]) Subsystem: Micro-Star International Co., Ltd. [MSI] Baffin [Radeon RX 560] [1462:8a91] InstallationDate: Installed on 2018-01-02 (441 days ago) InstallationMedia: Ubuntu 16.04.3 LTS "Xenial Xerus" - Release amd64 (20170801) MachineType: MSI MS-7A39 ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.15.0-46-generic root=UUID=f9677da3-0933-4ea3-9270-52f9a148ad9f ro quiet splash vt.handoff=1 SourcePackage: xorg UpgradeStatus: Upgraded to bionic on 2019-03-12 (7 days ago) dmi.bios.date: 08/01/2017 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 2.80 dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: B350M GAMING PRO (MS-7A39) dmi.board.vendor: MSI dmi.board.version: 1.0 dmi.chassis.asset.tag: To be filled by O.E.M. dmi.chassis.type: 3 dmi.chassis.vendor: MSI dmi.chassis.version: 1.0 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr2.80:bd08/01/2017:svnMSI:pnMS-7A39:pvr1.0:rvnMSI:rnB350MGAMINGPRO(MS-7A39):rvr1.0:cvnMSI:ct3:cvr1.0: dmi.product.family: To be filled by O.E.M. dmi.product.name: MS-7A39 dmi.product.version: 1.0 dmi.sys.vendor: MSI version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.95-1~18.04.1 version.libgl1-mesa-dri: libgl1-mesa-dri 18.2.8-0ubuntu0~18.04.2 version.libgl1-mesa-glx: libgl1-mesa-glx N/A version.xserver-xorg-core: xserver-xorg-core 2:1.19.6-1ubuntu4.2 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 Mar 13 09:59:49 2019 xserver.configfile: default xserver.devices: xserver.logfile: /var/log/Xorg.0.log xserver.outputs: xserver.version: 2:1.19.6-1ubuntu4.2 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg-server/+bug/1820943/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1820943] Re: no xorg
>From your XorgLog.txt: [554535.191] (EE) [554535.191] (EE) Backtrace: [554535.191] (EE) 0: /usr/lib/xorg/Xorg (xorg_backtrace+0x4d) [0x5635613fd8cd] [554535.191] (EE) 1: /usr/lib/xorg/Xorg (0x563561245000+0x1bc669) [0x563561401669] [554535.191] (EE) 2: /lib/x86_64-linux-gnu/libpthread.so.0 (0x7f8bdb9c1000+0x12890) [0x7f8bdb9d3890] [554535.191] (EE) [554535.191] (EE) Segmentation fault at address 0x0 [554535.191] (EE) Fatal server error: [554535.191] (EE) Caught signal 11 (Segmentation fault). Server aborting [554535.191] (EE) -- 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/1820943 Title: Xorg crashes [AMDGPU(0): Failed to open amdgpu hybrid version] Status in xorg-server package in Ubuntu: Incomplete Status in xserver-xorg-video-amdgpu package in Ubuntu: Incomplete Bug description: Not able to get GUI mode in ubuntu 18.04 ... 16.04 was fine ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: xorg (not installed) ProcVersionSignature: Ubuntu 4.15.0-46.49-generic 4.15.18 Uname: Linux 4.15.0-46-generic x86_64 NonfreeKernelModules: edac_mce_amd wmi_bmof amdkfd amd_iommu_v2 amdgpu chash snd_hda_codec_realtek snd_hda_codec_hdmi snd_hda_codec_generic snd_hda_intel snd_hda_codec snd_hda_core k10temp ccp mac_hid wmi shpchp i2c_piix4 r8169 gpio_amdpt gpio_generic ApportVersion: 2.20.9-0ubuntu7.6 Architecture: amd64 Date: Tue Mar 19 20:07:07 2019 DistUpgraded: 2019-03-12 10:43:47,713 DEBUG Running PostInstallScript: './xorg_fix_proprietary.py' DistroCodename: bionic DistroVariant: ubuntu GraphicsCard: Advanced Micro Devices, Inc. [AMD/ATI] Baffin [Radeon RX 550 640SP / RX 560/560X] [1002:67ff] (rev cf) (prog-if 00 [VGA controller]) Subsystem: Micro-Star International Co., Ltd. [MSI] Baffin [Radeon RX 560] [1462:8a91] InstallationDate: Installed on 2018-01-02 (441 days ago) InstallationMedia: Ubuntu 16.04.3 LTS "Xenial Xerus" - Release amd64 (20170801) MachineType: MSI MS-7A39 ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.15.0-46-generic root=UUID=f9677da3-0933-4ea3-9270-52f9a148ad9f ro quiet splash vt.handoff=1 SourcePackage: xorg UpgradeStatus: Upgraded to bionic on 2019-03-12 (7 days ago) dmi.bios.date: 08/01/2017 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 2.80 dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: B350M GAMING PRO (MS-7A39) dmi.board.vendor: MSI dmi.board.version: 1.0 dmi.chassis.asset.tag: To be filled by O.E.M. dmi.chassis.type: 3 dmi.chassis.vendor: MSI dmi.chassis.version: 1.0 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr2.80:bd08/01/2017:svnMSI:pnMS-7A39:pvr1.0:rvnMSI:rnB350MGAMINGPRO(MS-7A39):rvr1.0:cvnMSI:ct3:cvr1.0: dmi.product.family: To be filled by O.E.M. dmi.product.name: MS-7A39 dmi.product.version: 1.0 dmi.sys.vendor: MSI version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.95-1~18.04.1 version.libgl1-mesa-dri: libgl1-mesa-dri 18.2.8-0ubuntu0~18.04.2 version.libgl1-mesa-glx: libgl1-mesa-glx N/A version.xserver-xorg-core: xserver-xorg-core 2:1.19.6-1ubuntu4.2 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 Mar 13 09:59:49 2019 xserver.configfile: default xserver.devices: xserver.logfile: /var/log/Xorg.0.log xserver.outputs: xserver.version: 2:1.19.6-1ubuntu4.2 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg-server/+bug/1820943/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1820943] [NEW] no xorg
Public bug reported: Not able to get GUI mode in ubuntu 18.04 ... 16.04 was fine ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: xorg (not installed) ProcVersionSignature: Ubuntu 4.15.0-46.49-generic 4.15.18 Uname: Linux 4.15.0-46-generic x86_64 NonfreeKernelModules: edac_mce_amd wmi_bmof amdkfd amd_iommu_v2 amdgpu chash snd_hda_codec_realtek snd_hda_codec_hdmi snd_hda_codec_generic snd_hda_intel snd_hda_codec snd_hda_core k10temp ccp mac_hid wmi shpchp i2c_piix4 r8169 gpio_amdpt gpio_generic ApportVersion: 2.20.9-0ubuntu7.6 Architecture: amd64 Date: Tue Mar 19 20:07:07 2019 DistUpgraded: 2019-03-12 10:43:47,713 DEBUG Running PostInstallScript: './xorg_fix_proprietary.py' DistroCodename: bionic DistroVariant: ubuntu GraphicsCard: Advanced Micro Devices, Inc. [AMD/ATI] Baffin [Radeon RX 550 640SP / RX 560/560X] [1002:67ff] (rev cf) (prog-if 00 [VGA controller]) Subsystem: Micro-Star International Co., Ltd. [MSI] Baffin [Radeon RX 560] [1462:8a91] InstallationDate: Installed on 2018-01-02 (441 days ago) InstallationMedia: Ubuntu 16.04.3 LTS "Xenial Xerus" - Release amd64 (20170801) MachineType: MSI MS-7A39 ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.15.0-46-generic root=UUID=f9677da3-0933-4ea3-9270-52f9a148ad9f ro quiet splash vt.handoff=1 SourcePackage: xorg UpgradeStatus: Upgraded to bionic on 2019-03-12 (7 days ago) dmi.bios.date: 08/01/2017 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 2.80 dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: B350M GAMING PRO (MS-7A39) dmi.board.vendor: MSI dmi.board.version: 1.0 dmi.chassis.asset.tag: To be filled by O.E.M. dmi.chassis.type: 3 dmi.chassis.vendor: MSI dmi.chassis.version: 1.0 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr2.80:bd08/01/2017:svnMSI:pnMS-7A39:pvr1.0:rvnMSI:rnB350MGAMINGPRO(MS-7A39):rvr1.0:cvnMSI:ct3:cvr1.0: dmi.product.family: To be filled by O.E.M. dmi.product.name: MS-7A39 dmi.product.version: 1.0 dmi.sys.vendor: MSI version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.95-1~18.04.1 version.libgl1-mesa-dri: libgl1-mesa-dri 18.2.8-0ubuntu0~18.04.2 version.libgl1-mesa-glx: libgl1-mesa-glx N/A version.xserver-xorg-core: xserver-xorg-core 2:1.19.6-1ubuntu4.2 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 Mar 13 09:59:49 2019 xserver.configfile: default xserver.devices: xserver.logfile: /var/log/Xorg.0.log xserver.outputs: xserver.version: 2:1.19.6-1ubuntu4.2 ** Affects: xorg (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug bionic 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/1820943 Title: no xorg Status in xorg package in Ubuntu: New Bug description: Not able to get GUI mode in ubuntu 18.04 ... 16.04 was fine ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: xorg (not installed) ProcVersionSignature: Ubuntu 4.15.0-46.49-generic 4.15.18 Uname: Linux 4.15.0-46-generic x86_64 NonfreeKernelModules: edac_mce_amd wmi_bmof amdkfd amd_iommu_v2 amdgpu chash snd_hda_codec_realtek snd_hda_codec_hdmi snd_hda_codec_generic snd_hda_intel snd_hda_codec snd_hda_core k10temp ccp mac_hid wmi shpchp i2c_piix4 r8169 gpio_amdpt gpio_generic ApportVersion: 2.20.9-0ubuntu7.6 Architecture: amd64 Date: Tue Mar 19 20:07:07 2019 DistUpgraded: 2019-03-12 10:43:47,713 DEBUG Running PostInstallScript: './xorg_fix_proprietary.py' DistroCodename: bionic DistroVariant: ubuntu GraphicsCard: Advanced Micro Devices, Inc. [AMD/ATI] Baffin [Radeon RX 550 640SP / RX 560/560X] [1002:67ff] (rev cf) (prog-if 00 [VGA controller]) Subsystem: Micro-Star International Co., Ltd. [MSI] Baffin [Radeon RX 560] [1462:8a91] InstallationDate: Installed on 2018-01-02 (441 days ago) InstallationMedia: Ubuntu 16.04.3 LTS "Xenial Xerus" - Release amd64 (20170801) MachineType: MSI MS-7A39 ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.15.0-46-generic root=UUID=f9677da3-0933-4ea3-9270-52f9a148ad9f ro quiet splash vt.handoff=1 SourcePackage: xorg UpgradeStatus: Upgraded to bionic on 2019-03-12 (7 days ago) dmi.bios.date: 08/01/2017 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 2.80 dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: B350M GAMING PRO (MS-7A39) dmi.board.vendor: MSI dmi.board.version: 1.0 dmi.chassis.asset.tag: To be filled by O.E.M. dmi.chassis.type: 3 dmi.chassis.vendor: MSI dmi.chassis.version: 1.0 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr2.80:bd08/01/2017:svnMSI:pnMS-7A39:pvr1.0:rvnMSI:rnB350MGAMINGPRO(MS-7A39):rvr1.0:cvnMSI:ct3:cvr1.0: dmi.product.family: To be filled by O.E.M. dmi.product.name: MS-7A39 dmi.product.version: 1.0
[Touch-packages] [Bug 1820920] Re: bug in intel graphic driver
Can you please explain what kind of problem you are seeing? I can't see any issues in the attached log files. ** Package changed: xorg (Ubuntu) => xorg-server (Ubuntu) ** Changed in: xorg-server (Ubuntu) Status: New => Incomplete -- 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/1820920 Title: bug in intel graphic driver Status in xorg-server package in Ubuntu: Incomplete Bug description: bug in intel graphic driver ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: xorg 1:7.7+13ubuntu3.1 ProcVersionSignature: Ubuntu 4.15.0-46.49~16.04.1-generic 4.15.18 Uname: Linux 4.15.0-46-generic x86_64 .tmp.unity_support_test.0: ApportVersion: 2.20.1-0ubuntu2.18 Architecture: amd64 BootLog: CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: compiz CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0' CompositorUnredirectFSW: true CurrentDesktop: Unity Date: Tue Mar 19 16:51:35 2019 DistUpgraded: Fresh install DistroCodename: xenial DistroVariant: ubuntu ExtraDebuggingInterest: Yes GraphicsCard: Intel Corporation Atom Processor Z36xxx/Z37xxx Series Graphics & Display [8086:0f31] (rev 0e) (prog-if 00 [VGA controller]) Subsystem: Dell Atom Processor Z36xxx/Z37xxx Series Graphics & Display [1028:0667] InstallationDate: Installed on 2018-04-22 (331 days ago) InstallationMedia: Ubuntu 16.04.3 LTS "Xenial Xerus" - Release amd64 (20170801) Lsusb: Bus 001 Device 005: ID 0bda:0129 Realtek Semiconductor Corp. RTS5129 Card Reader Controller Bus 001 Device 004: ID 0c45:64ad Microdia Bus 001 Device 003: ID 062a:5918 Creative Labs Bus 001 Device 002: ID 8087:07e6 Intel Corp. Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: Dell Inc. Inspiron 3531 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-46-generic root=UUID=a38e26f8-92a9-4bbc-8c10-74d0345513b0 ro quiet splash vt.handoff=7 SourcePackage: xorg UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 05/06/2014 dmi.bios.vendor: Dell Inc. dmi.bios.version: A01 dmi.board.name: 00FTTX dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 8 dmi.chassis.vendor: Dell Inc. dmi.chassis.version: A01 dmi.modalias: dmi:bvnDellInc.:bvrA01:bd05/06/2014:svnDellInc.:pnInspiron3531:pvrA01:rvnDellInc.:rn00FTTX:rvrA00:cvnDellInc.:ct8:cvrA01: dmi.product.family: 00 dmi.product.name: Inspiron 3531 dmi.product.version: A01 dmi.sys.vendor: Dell Inc. version.compiz: compiz 1:0.9.12.3+16.04.20180221-0ubuntu1 version.ia32-libs: ia32-libs N/A version.libdrm2: libdrm2 2.4.91-2~16.04.1 version.libgl1-mesa-dri: libgl1-mesa-dri 18.0.5-0ubuntu0~16.04.1 version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A version.libgl1-mesa-glx: libgl1-mesa-glx 18.0.5-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 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg-server/+bug/1820920/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1820883] Re: totem comma key does not go 1 frame back ["gst_segment_do_seek: assertion 'start <= stop' failed"]
** Summary changed: - totem comma key does not go 1 frame back + totem comma key does not go 1 frame back ["gst_segment_do_seek: assertion 'start <= stop' failed"] ** Also affects: gstreamer1.0 (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to gstreamer1.0 in Ubuntu. https://bugs.launchpad.net/bugs/1820883 Title: totem comma key does not go 1 frame back ["gst_segment_do_seek: assertion 'start <= stop' failed"] Status in gstreamer1.0 package in Ubuntu: New Status in totem package in Ubuntu: New Bug description: According help the ',' (comma) key should go 1 frame back. I press the ',' key once: nothing happens; press again goes forward to end video after pressing ',' the '.' (dot) key does nothing but i have a message: (totem:31585): GStreamer-CRITICAL **: 18:15:31.465: gst_segment_do_seek: assertion 'start <= stop' failed pressing dot again it goes 1 frame forward ProblemType: Bug DistroRelease: Ubuntu 19.04 Package: totem 3.32.0-1ubuntu1 ProcVersionSignature: Ubuntu 5.0.0-7.8-generic 5.0.0 Uname: Linux 5.0.0-7-generic x86_64 ApportVersion: 2.20.10-0ubuntu23 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Tue Mar 19 18:17:34 2019 ExecutablePath: /usr/bin/totem InstallationDate: Installed on 2019-03-14 (5 days ago) InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Alpha amd64 (20190314) SourcePackage: totem UpgradeStatus: No upgrade log present (probably fresh install) XorgLog: Error: [Errno 2] No such file or directory: '/var/log/Xorg.0.log' To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gstreamer1.0/+bug/1820883/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1820866] Re: File dialog extremely slow
It looks like the file dialog is being slowed by scanning network shares. Please try removing those (temporarily) and tell us if the problem goes away. Please also reproduce the problem and then run: dmesg > dmesg.txt and attach the file 'dmesg.txt' to this bug. ** Package changed: gnome-shell (Ubuntu) => gtk+3.0 (Ubuntu) ** Tags added: performance -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to gtk+3.0 in Ubuntu. https://bugs.launchpad.net/bugs/1820866 Title: File dialog extremely slow Status in gtk+3.0 package in Ubuntu: New Bug description: From any application where you have a "save as" or "open" option, the dialog displays, but it takes forever. I have a i5 with 16GB RAM and 2 SSD's, so the machine is not slow. However, if I use gedit and click open / Other documents it takes 6 to 7 seconds before the file dialog is properly displayed. This does not even get better with reuse. I opened gedit just now and the first time it took 7 seconds. Then I pressed Cancel and repeated the process - it still took more than 6 seconds before the dialog was properly displayed. Often I would only see "Other locations" and then default places (Home, Documents etc) and bookmarks (I have about 8 bookmarks of which 2 are network shares) are displayed. These items are added one by one - maybe one every half second. Often it takes a few seconds before the first location other than "Other Locations" is displayed. Even the file panel is not immediate at first and you can see how lines are added one by one. Take into account that my home folder is on an SSD, so populating a file list should be lightning fast. I have looked at the CPU activity, but it does not go over about 10% during display of open and close dialogs. Just be aware that this is not specific to gedit - all applications using gnome file dialog has the same problem. Please see the attached screen recording. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: gnome-shell 3.28.3-0ubuntu0.18.04.4 ProcVersionSignature: Ubuntu 4.15.0-46.49-generic 4.15.18 Uname: Linux 4.15.0-46-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.6 Architecture: amd64 CurrentDesktop: GNOME Date: Tue Mar 19 16:14:16 2019 DisplayManager: gdm3 GsettingsChanges: b'org.gnome.shell' b'enabled-extensions' b"['nohotcor...@azuri.free.fr', 'weather-extens...@xeked.com', 'openweather-extens...@jenslody.de']" b'org.gnome.shell' b'command-history' redacted by apport b'org.gnome.shell' b'favorite-apps' redacted by apport b'org.gnome.desktop.interface' b'gtk-im-module' b"'gtk-im-context-simple'" b'org.gnome.desktop.interface' b'clock-show-date' b'true' InstallationDate: Installed on 2018-12-02 (107 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426) 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/gtk+3.0/+bug/1820866/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1820866] [NEW] File dialog extremely slow
You have been subscribed to a public bug: >From any application where you have a "save as" or "open" option, the dialog displays, but it takes forever. I have a i5 with 16GB RAM and 2 SSD's, so the machine is not slow. However, if I use gedit and click open / Other documents it takes 6 to 7 seconds before the file dialog is properly displayed. This does not even get better with reuse. I opened gedit just now and the first time it took 7 seconds. Then I pressed Cancel and repeated the process - it still took more than 6 seconds before the dialog was properly displayed. Often I would only see "Other locations" and then default places (Home, Documents etc) and bookmarks (I have about 8 bookmarks of which 2 are network shares) are displayed. These items are added one by one - maybe one every half second. Often it takes a few seconds before the first location other than "Other Locations" is displayed. Even the file panel is not immediate at first and you can see how lines are added one by one. Take into account that my home folder is on an SSD, so populating a file list should be lightning fast. I have looked at the CPU activity, but it does not go over about 10% during display of open and close dialogs. Just be aware that this is not specific to gedit - all applications using gnome file dialog has the same problem. Please see the attached screen recording. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: gnome-shell 3.28.3-0ubuntu0.18.04.4 ProcVersionSignature: Ubuntu 4.15.0-46.49-generic 4.15.18 Uname: Linux 4.15.0-46-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.6 Architecture: amd64 CurrentDesktop: GNOME Date: Tue Mar 19 16:14:16 2019 DisplayManager: gdm3 GsettingsChanges: b'org.gnome.shell' b'enabled-extensions' b"['nohotcor...@azuri.free.fr', 'weather-extens...@xeked.com', 'openweather-extens...@jenslody.de']" b'org.gnome.shell' b'command-history' redacted by apport b'org.gnome.shell' b'favorite-apps' redacted by apport b'org.gnome.desktop.interface' b'gtk-im-module' b"'gtk-im-context-simple'" b'org.gnome.desktop.interface' b'clock-show-date' b'true' InstallationDate: Installed on 2018-12-02 (107 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426) SourcePackage: gnome-shell UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: gtk+3.0 (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 bionic -- File dialog extremely slow https://bugs.launchpad.net/bugs/1820866 You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to gtk+3.0 in Ubuntu. -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1820282] Re: FTBFS: test failure during build in lp
This bug was fixed in the package zeromq3 - 4.3.1-3ubuntu2 --- zeromq3 (4.3.1-3ubuntu2) disco; urgency=medium * d/libzmq5.symbols: revert previous symbols update, as that came from a draft API that was mistakenly enabled in a local build when a .git directory was detected. -- Andreas Hasenack Tue, 19 Mar 2019 17:01:01 + ** Changed in: zeromq3 (Ubuntu) Status: In Progress => Fix Released -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to zeromq3 in Ubuntu. https://bugs.launchpad.net/bugs/1820282 Title: FTBFS: test failure during build in lp Status in ZeroMQ: Fix Released Status in zeromq3 package in Ubuntu: Fix Released Bug description: There is a test failure that only happens in the launchpad builder, but that fails the build. https://launchpad.net/ubuntu/+source/zeromq3/4.3.1-3 From https://launchpadlibrarian.net/415162342/buildlog_ubuntu-disco- amd64.zeromq3_4.3.1-3_BUILDING.txt.gz: FAIL: tests/test_filter_ipc === test_filter_ipc: tests/testutil.hpp:142: void bounce(void*, void*): Assertion `rc == 32' failed. FAIL tests/test_filter_ipc (exit status: 134) In a local LXD amd64 build, that test passes. To manage notifications about this bug go to: https://bugs.launchpad.net/zeromq/+bug/1820282/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1789924] Re: Missing Intel GPU pci-id's
This bug was fixed in the package mesa - 18.2.8-0ubuntu0~18.10.2 --- mesa (18.2.8-0ubuntu0~18.10.2) cosmic; urgency=medium * i965-revert-enabling-softpin.diff: Don't enable softpin, causes issues on 32bit installs. (LP: #1815172) mesa (18.2.8-0ubuntu0~18.10.1) cosmic; urgency=medium * New upstream bugfix release. (LP: #1811225) - add missing gpu-id's. (LP: #1789924) * Cherry-picked from disco: Move KHR/khrplatform.h from libegl1-mesa-dev to mesa-common-dev because GL/glcorearb.h and GL/glext.h started to depend on this header too (Closes: #914167). -- Timo Aaltonen Fri, 08 Feb 2019 19:12:58 +0200 ** Changed in: mesa (Ubuntu Cosmic) Status: Fix Committed => Fix Released -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to libdrm in Ubuntu. https://bugs.launchpad.net/bugs/1789924 Title: Missing Intel GPU pci-id's Status in libdrm package in Ubuntu: Fix Released Status in linux package in Ubuntu: Fix Released Status in mesa package in Ubuntu: Fix Released Status in xorg-server package in Ubuntu: Fix Released Status in libdrm source package in Bionic: Fix Released Status in linux source package in Bionic: Fix Released Status in mesa source package in Bionic: Fix Released Status in xorg-server source package in Bionic: Fix Released Status in libdrm source package in Cosmic: Fix Released Status in linux source package in Cosmic: Fix Released Status in mesa source package in Cosmic: Fix Released Status in xorg-server source package in Cosmic: Fix Released Bug description: [Impact] There are some new Intel GPU pci-id's that need to be added to several places: 0x3E98 0x87C0 and to make future additions easier, add platform definitions for Whiskey Lake and Amber Lake too. [Test case] Check that the user session uses the proper driver on these systems, if possible. Adding new pci-id's is a trivial change which can't regress existing hw. [Regression potential] none, these just add pci-id's and platform definitions To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libdrm/+bug/1789924/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1815172] Re: Black screen on skylake after 18.0 => 18.2 update
This bug was fixed in the package mesa - 18.2.8-0ubuntu0~18.10.2 --- mesa (18.2.8-0ubuntu0~18.10.2) cosmic; urgency=medium * i965-revert-enabling-softpin.diff: Don't enable softpin, causes issues on 32bit installs. (LP: #1815172) mesa (18.2.8-0ubuntu0~18.10.1) cosmic; urgency=medium * New upstream bugfix release. (LP: #1811225) - add missing gpu-id's. (LP: #1789924) * Cherry-picked from disco: Move KHR/khrplatform.h from libegl1-mesa-dev to mesa-common-dev because GL/glcorearb.h and GL/glext.h started to depend on this header too (Closes: #914167). -- Timo Aaltonen Fri, 08 Feb 2019 19:12:58 +0200 ** Changed in: mesa (Ubuntu Cosmic) Status: Fix Committed => Fix Released -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to mesa in Ubuntu. https://bugs.launchpad.net/bugs/1815172 Title: Black screen on skylake after 18.0 => 18.2 update Status in Mesa: Fix Released Status in linux package in Ubuntu: Fix Released Status in mesa package in Ubuntu: Fix Released Status in linux source package in Bionic: New Status in mesa source package in Bionic: Fix Released Status in linux source package in Cosmic: New Status in mesa source package in Cosmic: Fix Released Bug description: [Impact] Several schools reported black screens after normally updating their Ubuntu boxes from 18.0.5-0ubuntu0~18.04.1 to 18.2.2-0ubuntu1~18.04.1. Downgrading mesa fixes the problem. lspci: 00:02.0 VGA compatible controller [0300]: Intel Corporation HD Graphics 530 [8086:1912] (rev 06) Subsystem: ASUSTeK Computer Inc. HD Graphics 530 [1043:8694]Kernel modules: i915 Unfortunately I can't find a lot of useful information, here are some bits: * systemctl --failed says "gpu-manager" and "lightdm" have failed * Xorg.log is clean: https://termbin.com/6l2b * dmesg too: https://termbin.com/ip4e * It happens on lightdm/MATE, I don't know about Ubuntu GNOME. * If one runs `xinit` from ssh, it fails with: i965: Failed to submit batchbuffer: Invalid argument This is caused by mesa assuming that soft-pinning on GEN8+ is working since kernel 4.5, but in fact this issue wasn't fixed until 4.19.3. So a proper fix would be to backport commits from 4.19.3/4.20 to fix GTT sizes/pin flags, but that's left for future. [Test case] install fixed mesa or kernel, check that the regression is fixed [Regression potential] mesa: shouldn't be any, it just reverts the change to always soft-pin (TODO kernel: adds commits from upstream stable, which have been well tested upstream by now) To manage notifications about this bug go to: https://bugs.launchpad.net/mesa/+bug/1815172/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1811225] Re: Mesa 18.2.8 stable release
This bug was fixed in the package mesa - 18.2.8-0ubuntu0~18.10.2 --- mesa (18.2.8-0ubuntu0~18.10.2) cosmic; urgency=medium * i965-revert-enabling-softpin.diff: Don't enable softpin, causes issues on 32bit installs. (LP: #1815172) mesa (18.2.8-0ubuntu0~18.10.1) cosmic; urgency=medium * New upstream bugfix release. (LP: #1811225) - add missing gpu-id's. (LP: #1789924) * Cherry-picked from disco: Move KHR/khrplatform.h from libegl1-mesa-dev to mesa-common-dev because GL/glcorearb.h and GL/glext.h started to depend on this header too (Closes: #914167). -- Timo Aaltonen Fri, 08 Feb 2019 19:12:58 +0200 ** Changed in: mesa (Ubuntu Cosmic) Status: Fix Committed => Fix Released -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to mesa in Ubuntu. https://bugs.launchpad.net/bugs/1811225 Title: Mesa 18.2.8 stable release Status in mesa package in Ubuntu: Fix Released Status in mesa source package in Bionic: Fix Released Status in mesa source package in Cosmic: Fix Released Bug description: [Impact] Ubuntu 18.10 shipped with mesa 18.2.2, and deserves to get the last point release of the series. This will also be backported to 18.04 as part of the HWE stack update. Upstream changes: 18.2.3 - Different patches for the DirectX9 and DRI state trackers. - Several fixes and workarounds for different games, inlcuding RAGE, Yakuza and The Evil Within, Wolfenstein The Old Blood ARMA 3, or No Mans Sky. - A bunch of fixes for different drivers, including r600, nouveau, radeonsi, anv, radv, virgl, i965, nvc0 or nv50. Worth to mention a fix for GPU hangs in Radeonsi. - State Trackers also get different fixes and corrections. - Finally, fixes for GLSL and NIR are also in this queue. 18.2.4 - Different fixes for different drivers: freedreno, radeonsi, swr, anv and radv. - Also there are fixes for ac, gallium, spirv and blorp. 18.2.5 - A patch for nine state tracker that fixes several crashes using nine's thread_submit feature. There are other patches to other state trackers. - A couple of patches for Meson build system, as well as for autotools. - In the drivers side, there are a couple of fixes for RADV, one regarding subgroups and another regarding conditional rendering. There are also fixes for virgl, r600, and i965. - Finally, the queue contains a couple of fixes for NIR, Wayland, and other components. 18.2.6 - Several patches fixing leaks in glsl, winsys and r600. - Improvements in the scripts that helps in preparing releases. - Added PCI IDs for Amber Lake and Whiskey Lake. - Fixes for radv, anv, i965 and vc4 drivers. - A couple of fixes in NIR backend. - Finally, several fixes in meson build system. 18.2.7 - Several patches fixing leaks in glsl, winsys and r600. - Improvements in the scripts that helps in preparing releases. - Added PCI IDs for Amber Lake and Whiskey Lake. - Fixes for radv, anv, i965 and vc4 drivers. - A couple of fixes in NIR backend. - Finally, several fixes in meson build system. 18.2.8 - Several fixes in Meson build system. - Also several fixes for st/nine subcomponent. - Patch for RADV driver that fixes a hang in Yakuza using DXVK. - There are also fixes for Virgl driver. - Added PCI IDs for VegaM, Vega20 and Vega10. [Test Case] Check on intel/radeon hw that things still work fine. [Regression potential] Mesa stable releases are tested by vendor CI systems, this is the last of the series so should be safe to update to. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mesa/+bug/1811225/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1811225] Re: Mesa 18.2.8 stable release
This bug was fixed in the package mesa - 18.2.8-0ubuntu0~18.04.2 --- mesa (18.2.8-0ubuntu0~18.04.2) bionic; urgency=medium * Backport to bionic. mesa (18.2.8-0ubuntu0~18.10.2) cosmic; urgency=medium * i965-revert-enabling-softpin.diff: Don't enable softpin, causes issues on 32bit installs. (LP: #1815172) mesa (18.2.8-0ubuntu0~18.04.1) bionic; urgency=medium * Backport to bionic. * intel-whl-aml-cfl-ids.diff: Dropped, upstream. mesa (18.2.8-0ubuntu0~18.10.1) cosmic; urgency=medium * New upstream bugfix release. (LP: #1811225) - add missing gpu-id's. (LP: #1789924) * Cherry-picked from disco: Move KHR/khrplatform.h from libegl1-mesa-dev to mesa-common-dev because GL/glcorearb.h and GL/glext.h started to depend on this header too (Closes: #914167). -- Timo Aaltonen Sat, 09 Feb 2019 00:02:44 +0200 ** Changed in: mesa (Ubuntu Bionic) Status: Fix Committed => Fix Released -- 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/1811225 Title: Mesa 18.2.8 stable release Status in mesa package in Ubuntu: Fix Released Status in mesa source package in Bionic: Fix Released Status in mesa source package in Cosmic: Fix Committed Bug description: [Impact] Ubuntu 18.10 shipped with mesa 18.2.2, and deserves to get the last point release of the series. This will also be backported to 18.04 as part of the HWE stack update. Upstream changes: 18.2.3 - Different patches for the DirectX9 and DRI state trackers. - Several fixes and workarounds for different games, inlcuding RAGE, Yakuza and The Evil Within, Wolfenstein The Old Blood ARMA 3, or No Mans Sky. - A bunch of fixes for different drivers, including r600, nouveau, radeonsi, anv, radv, virgl, i965, nvc0 or nv50. Worth to mention a fix for GPU hangs in Radeonsi. - State Trackers also get different fixes and corrections. - Finally, fixes for GLSL and NIR are also in this queue. 18.2.4 - Different fixes for different drivers: freedreno, radeonsi, swr, anv and radv. - Also there are fixes for ac, gallium, spirv and blorp. 18.2.5 - A patch for nine state tracker that fixes several crashes using nine's thread_submit feature. There are other patches to other state trackers. - A couple of patches for Meson build system, as well as for autotools. - In the drivers side, there are a couple of fixes for RADV, one regarding subgroups and another regarding conditional rendering. There are also fixes for virgl, r600, and i965. - Finally, the queue contains a couple of fixes for NIR, Wayland, and other components. 18.2.6 - Several patches fixing leaks in glsl, winsys and r600. - Improvements in the scripts that helps in preparing releases. - Added PCI IDs for Amber Lake and Whiskey Lake. - Fixes for radv, anv, i965 and vc4 drivers. - A couple of fixes in NIR backend. - Finally, several fixes in meson build system. 18.2.7 - Several patches fixing leaks in glsl, winsys and r600. - Improvements in the scripts that helps in preparing releases. - Added PCI IDs for Amber Lake and Whiskey Lake. - Fixes for radv, anv, i965 and vc4 drivers. - A couple of fixes in NIR backend. - Finally, several fixes in meson build system. 18.2.8 - Several fixes in Meson build system. - Also several fixes for st/nine subcomponent. - Patch for RADV driver that fixes a hang in Yakuza using DXVK. - There are also fixes for Virgl driver. - Added PCI IDs for VegaM, Vega20 and Vega10. [Test Case] Check on intel/radeon hw that things still work fine. [Regression potential] Mesa stable releases are tested by vendor CI systems, this is the last of the series so should be safe to update to. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mesa/+bug/1811225/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1789924] Re: Missing Intel GPU pci-id's
This bug was fixed in the package mesa - 18.2.8-0ubuntu0~18.04.2 --- mesa (18.2.8-0ubuntu0~18.04.2) bionic; urgency=medium * Backport to bionic. mesa (18.2.8-0ubuntu0~18.10.2) cosmic; urgency=medium * i965-revert-enabling-softpin.diff: Don't enable softpin, causes issues on 32bit installs. (LP: #1815172) mesa (18.2.8-0ubuntu0~18.04.1) bionic; urgency=medium * Backport to bionic. * intel-whl-aml-cfl-ids.diff: Dropped, upstream. mesa (18.2.8-0ubuntu0~18.10.1) cosmic; urgency=medium * New upstream bugfix release. (LP: #1811225) - add missing gpu-id's. (LP: #1789924) * Cherry-picked from disco: Move KHR/khrplatform.h from libegl1-mesa-dev to mesa-common-dev because GL/glcorearb.h and GL/glext.h started to depend on this header too (Closes: #914167). -- Timo Aaltonen Sat, 09 Feb 2019 00:02:44 +0200 ** Changed in: mesa (Ubuntu Bionic) Status: Fix Committed => Fix Released -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to libdrm in Ubuntu. https://bugs.launchpad.net/bugs/1789924 Title: Missing Intel GPU pci-id's Status in libdrm package in Ubuntu: Fix Released Status in linux package in Ubuntu: Fix Released Status in mesa package in Ubuntu: Fix Released Status in xorg-server package in Ubuntu: Fix Released Status in libdrm source package in Bionic: Fix Released Status in linux source package in Bionic: Fix Released Status in mesa source package in Bionic: Fix Released Status in xorg-server source package in Bionic: Fix Released Status in libdrm source package in Cosmic: Fix Released Status in linux source package in Cosmic: Fix Released Status in mesa source package in Cosmic: Fix Committed Status in xorg-server source package in Cosmic: Fix Released Bug description: [Impact] There are some new Intel GPU pci-id's that need to be added to several places: 0x3E98 0x87C0 and to make future additions easier, add platform definitions for Whiskey Lake and Amber Lake too. [Test case] Check that the user session uses the proper driver on these systems, if possible. Adding new pci-id's is a trivial change which can't regress existing hw. [Regression potential] none, these just add pci-id's and platform definitions To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libdrm/+bug/1789924/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1815172] Re: Black screen on skylake after 18.0 => 18.2 update
This bug was fixed in the package mesa - 18.2.8-0ubuntu0~18.04.2 --- mesa (18.2.8-0ubuntu0~18.04.2) bionic; urgency=medium * Backport to bionic. mesa (18.2.8-0ubuntu0~18.10.2) cosmic; urgency=medium * i965-revert-enabling-softpin.diff: Don't enable softpin, causes issues on 32bit installs. (LP: #1815172) mesa (18.2.8-0ubuntu0~18.04.1) bionic; urgency=medium * Backport to bionic. * intel-whl-aml-cfl-ids.diff: Dropped, upstream. mesa (18.2.8-0ubuntu0~18.10.1) cosmic; urgency=medium * New upstream bugfix release. (LP: #1811225) - add missing gpu-id's. (LP: #1789924) * Cherry-picked from disco: Move KHR/khrplatform.h from libegl1-mesa-dev to mesa-common-dev because GL/glcorearb.h and GL/glext.h started to depend on this header too (Closes: #914167). -- Timo Aaltonen Sat, 09 Feb 2019 00:02:44 +0200 ** Changed in: mesa (Ubuntu Bionic) Status: Fix Committed => Fix Released -- 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/1815172 Title: Black screen on skylake after 18.0 => 18.2 update Status in Mesa: Fix Released Status in linux package in Ubuntu: Fix Released Status in mesa package in Ubuntu: Fix Released Status in linux source package in Bionic: New Status in mesa source package in Bionic: Fix Released Status in linux source package in Cosmic: New Status in mesa source package in Cosmic: Fix Committed Bug description: [Impact] Several schools reported black screens after normally updating their Ubuntu boxes from 18.0.5-0ubuntu0~18.04.1 to 18.2.2-0ubuntu1~18.04.1. Downgrading mesa fixes the problem. lspci: 00:02.0 VGA compatible controller [0300]: Intel Corporation HD Graphics 530 [8086:1912] (rev 06) Subsystem: ASUSTeK Computer Inc. HD Graphics 530 [1043:8694]Kernel modules: i915 Unfortunately I can't find a lot of useful information, here are some bits: * systemctl --failed says "gpu-manager" and "lightdm" have failed * Xorg.log is clean: https://termbin.com/6l2b * dmesg too: https://termbin.com/ip4e * It happens on lightdm/MATE, I don't know about Ubuntu GNOME. * If one runs `xinit` from ssh, it fails with: i965: Failed to submit batchbuffer: Invalid argument This is caused by mesa assuming that soft-pinning on GEN8+ is working since kernel 4.5, but in fact this issue wasn't fixed until 4.19.3. So a proper fix would be to backport commits from 4.19.3/4.20 to fix GTT sizes/pin flags, but that's left for future. [Test case] install fixed mesa or kernel, check that the regression is fixed [Regression potential] mesa: shouldn't be any, it just reverts the change to always soft-pin (TODO kernel: adds commits from upstream stable, which have been well tested upstream by now) To manage notifications about this bug go to: https://bugs.launchpad.net/mesa/+bug/1815172/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1811225] Update Released
The verification of the Stable Release Update for mesa has completed successfully and the package has now been released to -updates. Subsequently, the Ubuntu Stable Release Updates Team is being unsubscribed and will not receive messages about this bug report. In the event that you encounter a regression using the package from -updates please report a new bug using ubuntu-bug and tag the bug report regression-update so we can easily find any regressions. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to mesa in Ubuntu. https://bugs.launchpad.net/bugs/1811225 Title: Mesa 18.2.8 stable release Status in mesa package in Ubuntu: Fix Released Status in mesa source package in Bionic: Fix Released Status in mesa source package in Cosmic: Fix Committed Bug description: [Impact] Ubuntu 18.10 shipped with mesa 18.2.2, and deserves to get the last point release of the series. This will also be backported to 18.04 as part of the HWE stack update. Upstream changes: 18.2.3 - Different patches for the DirectX9 and DRI state trackers. - Several fixes and workarounds for different games, inlcuding RAGE, Yakuza and The Evil Within, Wolfenstein The Old Blood ARMA 3, or No Mans Sky. - A bunch of fixes for different drivers, including r600, nouveau, radeonsi, anv, radv, virgl, i965, nvc0 or nv50. Worth to mention a fix for GPU hangs in Radeonsi. - State Trackers also get different fixes and corrections. - Finally, fixes for GLSL and NIR are also in this queue. 18.2.4 - Different fixes for different drivers: freedreno, radeonsi, swr, anv and radv. - Also there are fixes for ac, gallium, spirv and blorp. 18.2.5 - A patch for nine state tracker that fixes several crashes using nine's thread_submit feature. There are other patches to other state trackers. - A couple of patches for Meson build system, as well as for autotools. - In the drivers side, there are a couple of fixes for RADV, one regarding subgroups and another regarding conditional rendering. There are also fixes for virgl, r600, and i965. - Finally, the queue contains a couple of fixes for NIR, Wayland, and other components. 18.2.6 - Several patches fixing leaks in glsl, winsys and r600. - Improvements in the scripts that helps in preparing releases. - Added PCI IDs for Amber Lake and Whiskey Lake. - Fixes for radv, anv, i965 and vc4 drivers. - A couple of fixes in NIR backend. - Finally, several fixes in meson build system. 18.2.7 - Several patches fixing leaks in glsl, winsys and r600. - Improvements in the scripts that helps in preparing releases. - Added PCI IDs for Amber Lake and Whiskey Lake. - Fixes for radv, anv, i965 and vc4 drivers. - A couple of fixes in NIR backend. - Finally, several fixes in meson build system. 18.2.8 - Several fixes in Meson build system. - Also several fixes for st/nine subcomponent. - Patch for RADV driver that fixes a hang in Yakuza using DXVK. - There are also fixes for Virgl driver. - Added PCI IDs for VegaM, Vega20 and Vega10. [Test Case] Check on intel/radeon hw that things still work fine. [Regression potential] Mesa stable releases are tested by vendor CI systems, this is the last of the series so should be safe to update to. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mesa/+bug/1811225/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 574287] Re: tasksel: forcefully removes packages when tasks overlap
What is going on with this bug? I wanted to install SSH Server on my new Ubuntu 18.04 system, and so unchecked the things that were installed already, checked SSH Server .. and it's been busily uninstalling EVERYTHING. This is a disaster. -- 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/574287 Title: tasksel: forcefully removes packages when tasks overlap Status in apt package in Ubuntu: Invalid Status in tasksel package in Ubuntu: Confirmed Status in tasksel package in Debian: Fix Released Bug description: TEST CASE 1. Boot Lucid LiveCD 2. run "sudo tasksel" and select "virtual machine host" 3. run "sudo tasksel" and deselect "virtual machine host" 4. watch how tasksel uninstalls your system OBSERVATIONS What seems to happen is that apt vengefully removes ALL of the items associated with one task, including several base dependencies of other tasks (e.g. ubuntu-desktop) One illustrative example is the openssh-server task: This one includes the packages openssh-server, tcpd and libwrap0. From a normal ubuntu-desktop (e.g. ~liveCD) both tcpd and libwrap0 are already installed, and the task-install pulls in only openssh-server. However when the task is removed, all these three packages (openssh-server, tcpd and libwrap0) are forcefully removed. Since libwrap0 is a core dependency of gnome, a large part of gnome will be removed alongside the removal of the task. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apt/+bug/574287/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1820920] [NEW] bug in intel graphic driver
Public bug reported: bug in intel graphic driver ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: xorg 1:7.7+13ubuntu3.1 ProcVersionSignature: Ubuntu 4.15.0-46.49~16.04.1-generic 4.15.18 Uname: Linux 4.15.0-46-generic x86_64 .tmp.unity_support_test.0: ApportVersion: 2.20.1-0ubuntu2.18 Architecture: amd64 BootLog: CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: compiz CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0' CompositorUnredirectFSW: true CurrentDesktop: Unity Date: Tue Mar 19 16:51:35 2019 DistUpgraded: Fresh install DistroCodename: xenial DistroVariant: ubuntu ExtraDebuggingInterest: Yes GraphicsCard: Intel Corporation Atom Processor Z36xxx/Z37xxx Series Graphics & Display [8086:0f31] (rev 0e) (prog-if 00 [VGA controller]) Subsystem: Dell Atom Processor Z36xxx/Z37xxx Series Graphics & Display [1028:0667] InstallationDate: Installed on 2018-04-22 (331 days ago) InstallationMedia: Ubuntu 16.04.3 LTS "Xenial Xerus" - Release amd64 (20170801) Lsusb: Bus 001 Device 005: ID 0bda:0129 Realtek Semiconductor Corp. RTS5129 Card Reader Controller Bus 001 Device 004: ID 0c45:64ad Microdia Bus 001 Device 003: ID 062a:5918 Creative Labs Bus 001 Device 002: ID 8087:07e6 Intel Corp. Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: Dell Inc. Inspiron 3531 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-46-generic root=UUID=a38e26f8-92a9-4bbc-8c10-74d0345513b0 ro quiet splash vt.handoff=7 SourcePackage: xorg UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 05/06/2014 dmi.bios.vendor: Dell Inc. dmi.bios.version: A01 dmi.board.name: 00FTTX dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 8 dmi.chassis.vendor: Dell Inc. dmi.chassis.version: A01 dmi.modalias: dmi:bvnDellInc.:bvrA01:bd05/06/2014:svnDellInc.:pnInspiron3531:pvrA01:rvnDellInc.:rn00FTTX:rvrA00:cvnDellInc.:ct8:cvrA01: dmi.product.family: 00 dmi.product.name: Inspiron 3531 dmi.product.version: A01 dmi.sys.vendor: Dell Inc. version.compiz: compiz 1:0.9.12.3+16.04.20180221-0ubuntu1 version.ia32-libs: ia32-libs N/A version.libdrm2: libdrm2 2.4.91-2~16.04.1 version.libgl1-mesa-dri: libgl1-mesa-dri 18.0.5-0ubuntu0~16.04.1 version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A version.libgl1-mesa-glx: libgl1-mesa-glx 18.0.5-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 ** 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/1820920 Title: bug in intel graphic driver Status in xorg package in Ubuntu: New Bug description: bug in intel graphic driver ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: xorg 1:7.7+13ubuntu3.1 ProcVersionSignature: Ubuntu 4.15.0-46.49~16.04.1-generic 4.15.18 Uname: Linux 4.15.0-46-generic x86_64 .tmp.unity_support_test.0: ApportVersion: 2.20.1-0ubuntu2.18 Architecture: amd64 BootLog: CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: compiz CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0' CompositorUnredirectFSW: true CurrentDesktop: Unity Date: Tue Mar 19 16:51:35 2019 DistUpgraded: Fresh install DistroCodename: xenial DistroVariant: ubuntu ExtraDebuggingInterest: Yes GraphicsCard: Intel Corporation Atom Processor Z36xxx/Z37xxx Series Graphics & Display [8086:0f31] (rev 0e) (prog-if 00 [VGA controller]) Subsystem: Dell Atom Processor Z36xxx/Z37xxx Series Graphics & Display [1028:0667] InstallationDate: Installed on 2018-04-22 (331 days ago) InstallationMedia: Ubuntu 16.04.3 LTS "Xenial Xerus" - Release amd64 (20170801) Lsusb: Bus 001 Device 005: ID 0bda:0129 Realtek Semiconductor Corp. RTS5129 Card Reader Controller Bus 001 Device 004: ID 0c45:64ad Microdia Bus 001 Device 003: ID 062a:5918 Creative Labs Bus 001 Device 002: ID 8087:07e6 Intel Corp. Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: Dell Inc. Inspiron 3531 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-46-generic root=UUID=a38e26f8-92a9-4bbc-8c10-74d0345513b0 ro quiet splash vt.handoff=7 SourcePackage: xorg UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 05/06/2014 dmi.bios.vendor: Dell Inc. dmi.bios.version: A01 dmi.board.name: 00FTTX dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 8 dmi.chassis.vendor:
[Touch-packages] [Bug 1819943] Re: intel video driver not installed by default in ubuntu 19.04 (Disco)
test the ppa, would like to get that patch upstream asap ** Changed in: xorg-server (Ubuntu) Status: Triaged => Incomplete -- 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/1819943 Title: intel video driver not installed by default in ubuntu 19.04 (Disco) Status in xorg package in Ubuntu: In Progress Status in xorg-server package in Ubuntu: Incomplete Bug description: I am running intel core2duo cpu and ubuntu 18.10 is running fine. I installed GRML , copied Ubuntu 19.04 iso to the grml folder in boot directory and then updated grub. Restarted the computer and on booting the ISO no login screen appeared. However,after pressing alt + ctrl + F2, logging in at command prompt,updating apt and installing "xserver-xorg-video-intel, lightdm, and unity" I was able to get to the desktop by running the command 'sudo service lightdm start'. Command 'startx and X" gave xorg error saying server could not be connected. Command "sudo service gdm(3) start' went back to command prompt ($). This was also observed in Kubuntu and Xubuntu. In Xubuntu after installing intel video driver and running startx command i was able to get to the desktop. Whether, "xserver-xorg-video-intel" package is not being installed by default in ubuntu or support for "intel core2duo processor" has been withdrawn. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1819943/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1820140] Re: euronews plugin needs to be updated to the website changes
Hello Sebastien, or anyone else affected, Accepted grilo-plugins into cosmic-proposed. The package will build now and be available at https://launchpad.net/ubuntu/+source/grilo- plugins/0.3.8-2ubuntu1.1 in a few hours, and then in the -proposed repository. Please help us by testing this new package. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation on how to enable and use -proposed. Your feedback will aid us getting this update out to other Ubuntu users. If this package fixes the bug for you, please add a comment to this bug, mentioning the version of the package you tested and change the tag from verification-needed-cosmic to verification-done-cosmic. If it does not fix the bug for you, please add a comment stating that, and change the tag to verification-failed-cosmic. In either case, without details of your testing we will not be able to proceed. Further information regarding the verification process can be found at https://wiki.ubuntu.com/QATeam/PerformingSRUVerification . Thank you in advance for helping! N.B. The updated package will be released to -updates after the bug(s) fixed by this package have been verified and the package has been in -proposed for a minimum of 7 days. ** Changed in: grilo-plugins (Ubuntu Cosmic) Status: New => Fix Committed ** Tags added: verification-needed verification-needed-cosmic -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to grilo-plugins in Ubuntu. https://bugs.launchpad.net/bugs/1820140 Title: euronews plugin needs to be updated to the website changes Status in grilo-plugins package in Ubuntu: Fix Released Status in grilo-plugins source package in Cosmic: Fix Committed Bug description: * Impact In totem the euronews section is giving parsing error and not displaying the video content * Test case Browse the euronews channel in totem, the video should play correctly * Impact The change is updating the url in the euronews plugin which is current not working, it shouldn't be able to create a regression To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/grilo-plugins/+bug/1820140/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1820608] Re: package openssh-server 1:7.2p2-4ubuntu2.8 failed to install/upgrade: subprocess installed post-installation script returned error exit status 1
Oh, and I just now saw this: SSHDConfig: Error: command ['/usr/sbin/sshd', '-T'] failed with exit code 255: Missing privilege separation directory: /var/run/sshd That directory is created on startup, unless something else happened. Maybe your /var/run symlink is busted? Please check: ls -lad /run /var/run /var/run/sshd -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to openssh in Ubuntu. https://bugs.launchpad.net/bugs/1820608 Title: package openssh-server 1:7.2p2-4ubuntu2.8 failed to install/upgrade: subprocess installed post-installation script returned error exit status 1 Status in openssh package in Ubuntu: Incomplete Bug description: . ProblemType: Package DistroRelease: Ubuntu 16.04 Package: openssh-server 1:7.2p2-4ubuntu2.8 ProcVersionSignature: Ubuntu 4.15.0-46.49~16.04.1-generic 4.15.18 Uname: Linux 4.15.0-46-generic x86_64 ApportVersion: 2.20.1-0ubuntu2.18 Architecture: amd64 Date: Mon Mar 18 13:38:42 2019 ErrorMessage: subprocess installed post-installation script returned error exit status 1 InstallationDate: Installed on 2019-01-21 (56 days ago) InstallationMedia: Ubuntu 16.04.5 LTS "Xenial Xerus" - Release amd64 (20180731) RelatedPackageVersions: dpkg 1.18.4ubuntu1.5 apt 1.2.29ubuntu0.1 SSHDConfig: Error: command ['/usr/sbin/sshd', '-T'] failed with exit code 255: Missing privilege separation directory: /var/run/sshd SourcePackage: openssh Title: package openssh-server 1:7.2p2-4ubuntu2.8 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/openssh/+bug/1820608/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1820608] Re: package openssh-server 1:7.2p2-4ubuntu2.8 failed to install/upgrade: subprocess installed post-installation script returned error exit status 1
Thanks for filing this bug in Ubuntu. This is the error that was logged: Setting up openssh-server (1:7.2p2-4ubuntu2.8) ... Unsafe symlinks encountered in /var/run/sshd, refusing. Job for ssh.service failed because the control process exited with error code. See "systemctl status ssh.service" and "journalctl -xe" for details. invoke-rc.d: initscript ssh, action "restart" failed. ● ssh.service - OpenBSD Secure Shell server Loaded: loaded (/lib/systemd/system/ssh.service; enabled; vendor preset: enabled) Active: activating (auto-restart) (Result: exit-code) since Mon 2019-03-18 13:38:42 UTC; 31ms ago Process: 14891 ExecStartPre=/usr/sbin/sshd -t [0;1;31m(code=exited, status=255)[0m Mar 18 13:38:42 HMNRHSECP006 systemd[1]: [0;1;31mFailed to start OpenBSD Secure Shel[0m Mar 18 13:38:42 HMNRHSECP006 systemd[1]: [0;1;39mssh.service: Unit entered failed state.[0m Mar 18 13:38:42 HMNRHSECP006 systemd[1]: [0;1;39mssh.service: Failed with result 'ex[0m Hint: Some lines were ellipsized, use -l to show in full. dpkg: error processing package openssh-server (--configure): subprocess installed post-installation script returned error exit status 1 Of note, I see this line: Unsafe symlinks encountered in /var/run/sshd, refusing. But no more details were given. Could you please attach /var/log/syslog, /var/log/auth.log and the output of "sudo systemctl status -l ssh"? You can trim the logfiles to cover just March 18th. ** Changed in: openssh (Ubuntu) Status: New => Incomplete -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to openssh in Ubuntu. https://bugs.launchpad.net/bugs/1820608 Title: package openssh-server 1:7.2p2-4ubuntu2.8 failed to install/upgrade: subprocess installed post-installation script returned error exit status 1 Status in openssh package in Ubuntu: Incomplete Bug description: . ProblemType: Package DistroRelease: Ubuntu 16.04 Package: openssh-server 1:7.2p2-4ubuntu2.8 ProcVersionSignature: Ubuntu 4.15.0-46.49~16.04.1-generic 4.15.18 Uname: Linux 4.15.0-46-generic x86_64 ApportVersion: 2.20.1-0ubuntu2.18 Architecture: amd64 Date: Mon Mar 18 13:38:42 2019 ErrorMessage: subprocess installed post-installation script returned error exit status 1 InstallationDate: Installed on 2019-01-21 (56 days ago) InstallationMedia: Ubuntu 16.04.5 LTS "Xenial Xerus" - Release amd64 (20180731) RelatedPackageVersions: dpkg 1.18.4ubuntu1.5 apt 1.2.29ubuntu0.1 SSHDConfig: Error: command ['/usr/sbin/sshd', '-T'] failed with exit code 255: Missing privilege separation directory: /var/run/sshd SourcePackage: openssh Title: package openssh-server 1:7.2p2-4ubuntu2.8 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/openssh/+bug/1820608/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1769297] Re: resume from hibernation broken when resume image is autodetected
@Dmitry where would I set this resume= parameter?
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to initramfs-tools in Ubuntu.
https://bugs.launchpad.net/bugs/1769297
Title:
resume from hibernation broken when resume image is autodetected
Status in initramfs-tools package in Ubuntu:
Confirmed
Bug description:
I found a reason of non-functioning resume from hibernation when
resume partition/file is autodetected by intiramfs hook /usr/share
/initramfs-tools/hooks/resume.
Here is the scenario:
1) hook /usr/share/initramfs-tools/hooks/resume creates config
conf/conf.d/zz-resume-auto saved in initrd image, containing one variable:
RESUME=UUID=106238b0-707d-4422-866d-a7534da50702 in my case
2) during boot init script sets 'resume' variable to 'RESUME' value
from conf/conf.d/zz-resume-auto, then it executes local-premount
scripts including local-premount/resume
3) resuming script local-premount/resume
(/usr/share/initramfs-tools/scripts/local-premount/resume) tries to get resume
device major-minor numbers by these lines:
DEV=$(readlink ${resume})
DEV=/sys/class/block/${DEV##*/}/dev
if [ -r "$DEV" ]; then
read MAJMIN < "$DEV"
fi
4) next check fails and resume process silently aborts:
if [ -z "$MAJMIN" ]; then
exit 1
fi
Resuming script fails to get device major-minor because
resume=UUID=106238b0-707d-4422-866d-a7534da50702 -- it's not resolved
into device path in init script.
Commonly mentioned workaround is to explicitly specify kernel
parameter resume=UUID=106238b0-707d-4422-866d-a7534da50702 -- only in
this case init script resolves it to device path.
ProblemType: Bug
DistroRelease: Ubuntu 18.04
Package: initramfs-tools 0.130ubuntu3
Uname: Linux 4.16.6-041606-generic x86_64
ApportVersion: 2.20.9-0ubuntu7
Architecture: amd64
CurrentDesktop: ubuntu:GNOME
Date: Sat May 5 11:32:31 2018
InstallationDate: Installed on 2018-03-27 (38 days ago)
InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Alpha amd64 (20180327)
PackageArchitecture: all
SourcePackage: initramfs-tools
UpgradeStatus: No upgrade log present (probably fresh install)
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/initramfs-tools/+bug/1769297/+subscriptions
--
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1820282] Re: FTBFS: test failure during build in lp
** Changed in: zeromq Status: New => Fix Released -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to zeromq3 in Ubuntu. https://bugs.launchpad.net/bugs/1820282 Title: FTBFS: test failure during build in lp Status in ZeroMQ: Fix Released Status in zeromq3 package in Ubuntu: In Progress Bug description: There is a test failure that only happens in the launchpad builder, but that fails the build. https://launchpad.net/ubuntu/+source/zeromq3/4.3.1-3 From https://launchpadlibrarian.net/415162342/buildlog_ubuntu-disco- amd64.zeromq3_4.3.1-3_BUILDING.txt.gz: FAIL: tests/test_filter_ipc === test_filter_ipc: tests/testutil.hpp:142: void bounce(void*, void*): Assertion `rc == 32' failed. FAIL tests/test_filter_ipc (exit status: 134) In a local LXD amd64 build, that test passes. To manage notifications about this bug go to: https://bugs.launchpad.net/zeromq/+bug/1820282/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1820886] Re: Potential inconsistency due to system halt/reboot being allowed when package installation in progress
** No longer affects: landscape-client ** Description changed: [System] Any current Ubuntu Desktop/Server supported release (Trusty, Xenial, Bionic, Cosmic). [Impact] Package installation turns into an inconsistent state if system is rebooted in the middle of an apt install/upgrade. [Test Case] Scenario with Landscape: 1. Upgrade triggered from Landscape 2. User at Ubuntu Desktop reboots the box using the GUI 3. System reboots and potentially turns into an inconsistent state Scenario w/o Landscape: 1. User1 at Ubuntu Server issues "sudo apt-get upgrade" 2. User2 at Ubuntu Server issues "shutdown -r" 3. System reboots and potentially turns into an inconsistent state [Remarks] APT should automatically inhibit system halts/reboots while packages being installed/removed. A similar behavior to what is shown by unattended-upgrades. - - As a Plan B, an Ubuntu Server/Desktop with the Landscape Client - installed, should at least display warning the users that packages are - being installed. ** Description changed: [System] Any current Ubuntu Desktop/Server supported release (Trusty, Xenial, Bionic, Cosmic). [Impact] Package installation turns into an inconsistent state if system is rebooted in the middle of an apt install/upgrade. [Test Case] - Scenario with Landscape: - 1. Upgrade triggered from Landscape - 2. User at Ubuntu Desktop reboots the box using the GUI - 3. System reboots and potentially turns into an inconsistent state - - Scenario w/o Landscape: - 1. User1 at Ubuntu Server issues "sudo apt-get upgrade" - 2. User2 at Ubuntu Server issues "shutdown -r" - 3. System reboots and potentially turns into an inconsistent state + 1. User1 at Ubuntu box issues "sudo apt-get upgrade"; + 2. User2 at Ubuntu box issues "shutdown -r" or reboots it using the GUI; + 3. System reboots and potentially turns into an inconsistent state. [Remarks] APT should automatically inhibit system halts/reboots while packages being installed/removed. A similar behavior to what is shown by unattended-upgrades. -- 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/1820886 Title: Potential inconsistency due to system halt/reboot being allowed when package installation in progress Status in apt package in Ubuntu: New Bug description: [System] Any current Ubuntu Desktop/Server supported release (Trusty, Xenial, Bionic, Cosmic). [Impact] Package installation turns into an inconsistent state if system is rebooted in the middle of an apt install/upgrade. [Test Case] 1. User1 at Ubuntu box issues "sudo apt-get upgrade"; 2. User2 at Ubuntu box issues "shutdown -r" or reboots it using the GUI; 3. System reboots and potentially turns into an inconsistent state. [Remarks] APT should automatically inhibit system halts/reboots while packages being installed/removed. A similar behavior to what is shown by unattended-upgrades. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apt/+bug/1820886/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1820886] [NEW] Potential inconsistency due to system halt/reboot being allowed when package installation in progress
Public bug reported: [System] Any current Ubuntu Desktop/Server supported release (Trusty, Xenial, Bionic, Cosmic). [Impact] Package installation turns into an inconsistent state if system is rebooted in the middle of an apt install/upgrade. [Test Case] Scenario with Landscape: 1. Upgrade triggered from Landscape 2. User at Ubuntu Desktop reboots the box using the GUI 3. System reboots and potentially turns into an inconsistent state Scenario w/o Landscape: 1. User1 at Ubuntu Server issues "sudo apt-get upgrade" 2. User2 at Ubuntu Server issues "shutdown -r" 3. System reboots and potentially turns into an inconsistent state [Remarks] APT should automatically inhibit system halts/reboots while packages being installed/removed. A similar behavior to what is shown by unattended-upgrades. As a Plan B, an Ubuntu Server/Desktop with the Landscape Client installed, should at least display warning the users that packages are being installed. ** Affects: landscape-client Importance: Undecided Status: New ** Affects: apt (Ubuntu) Importance: Undecided Status: New ** Tags: sts ** Also affects: landscape-client Importance: Undecided Status: New ** Summary changed: - Inhibit system halt when package installation in progress + System halt/reboot is allowed when package installation in progress ** Summary changed: - System halt/reboot is allowed when package installation in progress + Potential inconsistency due to system halt/reboot being allowed when package installation in progress ** Tags added: sts -- 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/1820886 Title: Potential inconsistency due to system halt/reboot being allowed when package installation in progress Status in Landscape Client: New Status in apt package in Ubuntu: New Bug description: [System] Any current Ubuntu Desktop/Server supported release (Trusty, Xenial, Bionic, Cosmic). [Impact] Package installation turns into an inconsistent state if system is rebooted in the middle of an apt install/upgrade. [Test Case] Scenario with Landscape: 1. Upgrade triggered from Landscape 2. User at Ubuntu Desktop reboots the box using the GUI 3. System reboots and potentially turns into an inconsistent state Scenario w/o Landscape: 1. User1 at Ubuntu Server issues "sudo apt-get upgrade" 2. User2 at Ubuntu Server issues "shutdown -r" 3. System reboots and potentially turns into an inconsistent state [Remarks] APT should automatically inhibit system halts/reboots while packages being installed/removed. A similar behavior to what is shown by unattended-upgrades. As a Plan B, an Ubuntu Server/Desktop with the Landscape Client installed, should at least display warning the users that packages are being installed. To manage notifications about this bug go to: https://bugs.launchpad.net/landscape-client/+bug/1820886/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1820888] [NEW] unattended-upgrades may hold back upgrades due to comparing package versions by their string representation
Public bug reported: This is part of the reason why the autopkgtes installing all security updates is failing for cosmic with 1.10ubuntu1: https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac/autopkgtest-disco/disco/amd64/u/unattended-upgrades/20190318_182031_fe4fe@/log.gz ... Checking: libnss-systemd ([]) pkg libsystemd0 not in allowed origin sanity check failed ... ** Affects: unattended-upgrades (Ubuntu) Importance: Undecided Status: New -- 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/1820888 Title: unattended-upgrades may hold back upgrades due to comparing package versions by their string representation Status in unattended-upgrades package in Ubuntu: New Bug description: This is part of the reason why the autopkgtes installing all security updates is failing for cosmic with 1.10ubuntu1: https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac/autopkgtest-disco/disco/amd64/u/unattended-upgrades/20190318_182031_fe4fe@/log.gz ... Checking: libnss-systemd ([]) pkg libsystemd0 not in allowed origin sanity check failed ... To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/unattended-upgrades/+bug/1820888/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1820874] [NEW] [xenial] udev cannot identify fs uuid by builtin blkid (fixed in upstream)
Public bug reported: see upstream bug https://github.com/systemd/systemd/issues/6110 fix https://github.com/poettering/systemd/commit/e2c48187ccb9668dab9f025c9c4228e97927179f udev calls libblkid with flag BLKID_SUBLKS_BADCSUM to see all superblocks but data in filesystem could be detected as broken superblock of other filesystem: root@vla2-4101:~# wipefs -n /dev/sdf2 offset type 0xae9c36ff006nilfs2 [filesystem] LABEL: 9-627f5c82-a8f363c9-a716ffb1) ea9a210be67212ac0ae104ca29ef 2019-02-14 05: UUID: 2c205265-6164-5365-7373-696f6e49643a 0x438ext4 [filesystem] LABEL: /yt/disk5 UUID: 778742b8-1ac6-45cf-a459-2f7919ba5dd4 normal blkid is fine root@vla2-4101:~# blkid -p /dev/sdf2 /dev/sdf2: LABEL="/yt/disk5" UUID="778742b8-1ac6-45cf-a459-2f7919ba5dd4" VERSION="1.0" TYPE="ext4" USAGE="filesystem" PART_ENTRY_SCHEME="gpt" PART_ENTRY_NAME="primary" PART_ENTRY_UUID="259f0f4b-eb1e-4c34-a03d-65d04875f10c" PART_ENTRY_TYPE="ebd0a0a2-b9e5-4433-87c0-68b6b72699c7" PART_ENTRY_NUMBER="2" PART_ENTRY_OFFSET="30720" PART_ENTRY_SIZE="23435786240" PART_ENTRY_DISK="8:80" builtin blkid sees two different superblocks and cannot decide root@vla2-4101:~# udevadm test-builtin blkid /class/block/sdf2 calling: test-builtin === trie on-disk === tool version: 229 file size: 6841781 bytes header size 80 bytes strings1755245 bytes nodes 5086456 bytes Load module index Network interface NamePolicy= disabled on kernel command line, ignoring. timestamp of '/etc/systemd/network' changed timestamp of '/lib/systemd/network' changed Parsed configuration file /lib/systemd/network/99-default.link Created link configuration context. probe /dev/sdf2 raid offset=0 Unload module index Unloaded link configuration context. root@vla2-4101:~# apt-cache policy udev udev: Installed: 229-4ubuntu21.17 Candidate: 229-4ubuntu21.17 ** Affects: systemd (Ubuntu) Importance: Undecided Status: New ** Tags: xenial ** Tags added: xenial ** Summary changed: - udev cannot identify fs uuid by builtin blkid (fixed in upstream) + [xenial] udev cannot identify fs uuid by builtin blkid (fixed in upstream) -- 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/1820874 Title: [xenial] udev cannot identify fs uuid by builtin blkid (fixed in upstream) Status in systemd package in Ubuntu: New Bug description: see upstream bug https://github.com/systemd/systemd/issues/6110 fix https://github.com/poettering/systemd/commit/e2c48187ccb9668dab9f025c9c4228e97927179f udev calls libblkid with flag BLKID_SUBLKS_BADCSUM to see all superblocks but data in filesystem could be detected as broken superblock of other filesystem: root@vla2-4101:~# wipefs -n /dev/sdf2 offset type 0xae9c36ff006nilfs2 [filesystem] LABEL: 9-627f5c82-a8f363c9-a716ffb1) ea9a210be67212ac0ae104ca29ef 2019-02-14 05: UUID: 2c205265-6164-5365-7373-696f6e49643a 0x438ext4 [filesystem] LABEL: /yt/disk5 UUID: 778742b8-1ac6-45cf-a459-2f7919ba5dd4 normal blkid is fine root@vla2-4101:~# blkid -p /dev/sdf2 /dev/sdf2: LABEL="/yt/disk5" UUID="778742b8-1ac6-45cf-a459-2f7919ba5dd4" VERSION="1.0" TYPE="ext4" USAGE="filesystem" PART_ENTRY_SCHEME="gpt" PART_ENTRY_NAME="primary" PART_ENTRY_UUID="259f0f4b-eb1e-4c34-a03d-65d04875f10c" PART_ENTRY_TYPE="ebd0a0a2-b9e5-4433-87c0-68b6b72699c7" PART_ENTRY_NUMBER="2" PART_ENTRY_OFFSET="30720" PART_ENTRY_SIZE="23435786240" PART_ENTRY_DISK="8:80" builtin blkid sees two different superblocks and cannot decide root@vla2-4101:~# udevadm test-builtin blkid /class/block/sdf2 calling: test-builtin === trie on-disk === tool version: 229 file size: 6841781 bytes header size 80 bytes strings1755245 bytes nodes 5086456 bytes Load module index Network interface NamePolicy= disabled on kernel command line, ignoring. timestamp of '/etc/systemd/network' changed timestamp of '/lib/systemd/network' changed Parsed configuration file /lib/systemd/network/99-default.link Created link configuration context. probe /dev/sdf2 raid offset=0 Unload module index Unloaded link configuration context. root@vla2-4101:~# apt-cache policy udev udev: Installed: 229-4ubuntu21.17 Candidate: 229-4ubuntu21.17 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1820874/+subscriptions
[Touch-packages] [Bug 1450588] Re: [FFe] /var/log/dmesg No Longer Being Updated
>From a feature freeze POV, this is ok with me. I don't know that I agree it makes sense to reintroduce this log file now after so long if the information is available elsewhere, but I don't think I need to block this w/ release team hat. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to rsyslog in Ubuntu. https://bugs.launchpad.net/bugs/1450588 Title: [FFe] /var/log/dmesg No Longer Being Updated Status in rsyslog package in Ubuntu: New Status in systemd package in Ubuntu: Invalid Bug description: [FFe] * (re-)introduce a feature to ensure the initial (boot time) kernel messages are preserved * This existed up to Trusty (upstart) but was lost afterwards as it had no systemd coutnerpart. * It is a "new" feature since we have lacked it for so many releases and worth - a hopefully simple - ack by the release Team * It is not a new version or any change to the actual rsyslog code. Instead it just adds a new service "dmesg" that will achieve what was lost post trusty. Therefore the potential regression to the existing function should be minimal, if anything the new service might hit issues on some unexpected environments but atm that seems unlikely. * It does not add/remove Dependencies nor modify build * I ahve made upgrade/install tests as well as Ahasenack doing the same on the MP that is linked. --- After upgrading to Ubuntu 15.04 Vivid, /var/log/dmesg is no longer updated after boot. It appears that this was previously done via /etc/init/dmesg.conf To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/rsyslog/+bug/1450588/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1560286] Re: Evince displays pdf file fine, but prints colors inverted
This bug was fixed in the package cairo - 1.15.12-1ubuntu0.1 --- cairo (1.15.12-1ubuntu0.1) cosmic; urgency=medium * debian/patches/git_adobe_cmykcolors.patch: - "Revert "Correctly decode Adobe CMYK JPEGs in PDF export" From further testing and investigation it appears that many PDF viewers already have a workaround to invert Adobe CMYK JPEGs, so our generated PDFs display incorrectly with those viewers due to double-inversion. (lp: #1560286) -- Sebastien Bacher Tue, 22 Jan 2019 15:10:03 +0100 ** Changed in: cairo (Ubuntu Cosmic) Status: Fix Committed => Fix Released -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to cairo in Ubuntu. https://bugs.launchpad.net/bugs/1560286 Title: Evince displays pdf file fine, but prints colors inverted Status in cairo package in Ubuntu: Fix Released Status in cairo source package in Bionic: Fix Released Status in cairo source package in Cosmic: Fix Released Bug description: * Impact In some files images are printed with inverted colors * Test case open https://bugs.launchpad.net/ubuntu/+source/cairo/+bug/1560286/+attachment/5226857/+files/978-1-57896-287-7%20LL4%20SW%20Sem%201%20Reduced%20p.17.pdf in evince, click on the print preview, the colors should be right * Regression potential it's a change in the code dealing with specific adobe file, test opening the example in different document viewer and try with some other files (the bug has several example), they should display the correct image/colors I have several pdf files that when opened by evince, they appear to be fine until I try to print them. When I do, they print with the colors inverted (the printout looks like a photograph negative). This color inversion also occurs when viewed in the print preview screen. If I click on File > Properties, I get some information... Producer : Adobe Acrobat 15.10 Image Conversion Plug-in Creator : Adobe Acrobat 15.10 ... Format : PDF-1.6 ... I am running ubuntu 14.04 LTS ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: evince 3.10.3-0ubuntu10.2 ProcVersionSignature: Ubuntu 3.13.0-83.127-generic 3.13.11-ckt35 Uname: Linux 3.13.0-83-generic x86_64 NonfreeKernelModules: fglrx ApportVersion: 2.14.1-0ubuntu3.19 Architecture: amd64 CurrentDesktop: Unity Date: Mon Mar 21 21:01:45 2016 ExecutablePath: /usr/bin/evince InstallationDate: Installed on 2012-07-24 (1336 days ago) InstallationMedia: Ubuntu 12.04 LTS "Precise Pangolin" - Release amd64 (20120425) ProcEnviron: LANGUAGE=en_US PATH=(custom, user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: evince UpgradeStatus: Upgraded to trusty on 2014-09-29 (539 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/cairo/+bug/1560286/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1698159] Re: linux-cloud-tools version specific packages are being removed by unattended-upgrade's Remove-Unused-Dependencies
I have Unattended-Upgrade::Remove-Unused-Dependencies set to default value (false) and u-u 1.1ubuntu1.18.04.7~16.04.2 did not remove linux- hwe-cloud-tools-* package related to non-running protected kernel either. -- 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/1698159 Title: linux-cloud-tools version specific packages are being removed by unattended-upgrade's Remove-Unused-Dependencies Status in apt package in Ubuntu: Fix Released Status in unattended-upgrades package in Ubuntu: Fix Released Status in apt source package in Trusty: Triaged Status in unattended-upgrades source package in Trusty: New Status in apt source package in Xenial: Fix Released Status in unattended-upgrades source package in Xenial: Fix Committed Status in apt source package in Bionic: Fix Released Status in unattended-upgrades source package in Bionic: Fix Released Bug description: [Impact] When running kernel version 4.4.0-78 (for example) and the unattended-upgrade packages installs a new kernel 4.4.0-79 (for example) the linux-cloud-tools-4.4.0-78 and linux-cloud-tools-4.4.0-78-generic packages are removed by the Remove-Unused-Dependencies rule, because unlike "normal" kernel packages they are not excluded by /etc/apt/apt.conf.d/01autoremove-kernels. The linux-cloud-tools package has the hyper-v integration services daemons in it, so it's deletion leaves some of the integration not working. Could /etc/apt/apt.conf.d/01autoremove-kernels be updated so other hyper-v users aren't caught out by this? Thanks, Ian. [Test case (apt)] Make sure that linux-cloud-tools for protected kernels are listed in APT::NeverAutoRemove, for example, on cosmic: "^linux-cloud-tools-4\.17\.0-9-generic$"; "^linux-cloud-tools-4\.18\.0-7-generic$"; Those are in 01autoremove-kernels [Test case (unattended-upgrades)] * Check the running kernel and install relevant cloud-tools packages: # uname -a Linux x-uu-lp-1737637 4.15.0-39-generic #42-Ubuntu SMP Tue Oct 23 15:48:01 UTC 2018 x86_64 x86_64 x86_64 GNU/Linux root@x-uu-lp-1737637:~# apt-cache search 4.15.0-39-generic linux-cloud-tools-4.15.0-39-generic - Linux kernel version specific cloud tools for version 4.15.0-39 linux-headers-4.15.0-39-generic - Linux kernel headers for version 4.15.0 on 64 bit x86 SMP linux-image-4.15.0-39-generic - Signed kernel image generic linux-image-unsigned-4.15.0-39-generic - Linux kernel image for version 4.15.0 on 64 bit x86 SMP linux-modules-4.15.0-39-generic - Linux kernel extra modules for version 4.15.0 on 64 bit x86 SMP linux-modules-extra-4.15.0-39-generic - Linux kernel extra modules for version 4.15.0 on 64 bit x86 SMP # apt install linux-cloud-tools-4.15.0-39-generic Reading package lists... Done Building dependency tree Reading state information... Done The following package was automatically installed and is no longer required: libfreetype6 Use 'apt autoremove' to remove it. The following additional packages will be installed: linux-cloud-tools-common linux-hwe-cloud-tools-4.15.0-39 The following NEW packages will be installed: linux-cloud-tools-4.15.0-39-generic linux-cloud-tools-common linux-hwe-cloud-tools-4.15.0-39 0 upgraded, 3 newly installed, 0 to remove and 17 not upgraded. Need to get 119 kB of archives. After this operation, 854 kB of additional disk space will be used. Do you want to continue? [Y/n] ... * Mark them autoremovable and configure u-u to autoremove unused packages: # apt-mark auto linux-cloud-tools-4.15.0-39-generic linux-cloud-tools-4.15.0-39-generic set to automatically installed. ### set Unattended-Upgrade::Remove-Unused-Dependencies "true"; # vi /etc/apt/apt.conf.d/50unattended-upgrades * The not fixed version of u-u removes the packages: # unattended-upgrade --dry-run --verbose ... All upgrades installed Packages that are auto removed: 'libfreetype6 linux-cloud-tools-4.15.0-39-generic linux-cloud-tools-common linux-hwe-cloud-tools-4.15.0-39' Packages were successfully auto-removed # * The fixed version does not: # unattended-upgrade --dry-run --verbose Initial blacklisted packages: Initial whitelisted packages: Starting unattended upgrades script Allowed origins are: o=Ubuntu,a=xenial, o=Ubuntu,a=xenial-security, o=UbuntuESM,a=xenial Removing unused kernel packages: linux-cloud-tools-common Keeping auto-removable linux-cloud-tools-common package(s) because it would also remove the following packages which should be kept in this step: linux-cloud-tools-4.15.0-39-generic linux-hwe-cloud-tools-4.15.0-39 ... [Regression Potential] * some linux-cloud-tools will linger around, so it takes more space. [Other info] ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: unattended-upgrades 0.90ubuntu0.6
[Touch-packages] [Bug 1819615] Re: For additional hardware support, modemmanager needs to be upgraded to 1.10 on Bionic
** Changed in: modemmanager (Ubuntu Bionic) Assignee: (unassigned) => Till Kamppeter (till-kamppeter) -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to modemmanager in Ubuntu. https://bugs.launchpad.net/bugs/1819615 Title: For additional hardware support, modemmanager needs to be upgraded to 1.10 on Bionic Status in libmbim package in Ubuntu: Fix Released Status in libqmi package in Ubuntu: Fix Released Status in modemmanager package in Ubuntu: Fix Released Status in libmbim source package in Bionic: In Progress Status in libqmi source package in Bionic: In Progress Status in modemmanager source package in Bionic: In Progress Bug description: [Impact] * The new modemmanager package adds DW5820e support. * This modemmanager version is needed to support new devices. [Test Case] * install modemmanager, libmbim, and libqmi from -proposed * reboot and try WWAN function to see if any regression there. * perform general dogfooding of its reverse dependencies (network- manager, gnome-control-center etc.) [Regression Potential] * The package comes from Disco and should not have regression there. * Every new upstream release can potentially break existing dependencies if any of the required features have been changed/removed, so besides regular testing a general dogfooding session with the new modemmanager is advised. [Original Description] To have Bionic, the current LTS, working with as wide of a range of modems as possible we need to have it upgraded to the current 1.10 versions. Also the underlying libraries need to get upgraded appropriately. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libmbim/+bug/1819615/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1820860] [NEW] /usr/bin/software-properties-gtk:RuntimeError(org.freedesktop.DBus.Python.RuntimeError):on_driver_changes_cancel:_deferable:_convert_dbus_exception:_convert_dbus_e
Public bug reported: The Ubuntu Error Tracker has been receiving reports about a problem regarding software-properties. This problem was most recently seen with package version 0.97.9, the problem page at https://errors.ubuntu.com/problem/6567b1f317a885bc109de031608c5f1c675d1ae0 contains more details, including versions of packages affected, stacktrace or traceback, and individual crash reports. If you do not have access to the Ubuntu Error Tracker and are a software developer, you can request it at http://forms.canonical.com/reports/. ** Affects: software-properties (Ubuntu) Importance: Undecided Status: New ** Tags: disco -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to software-properties in Ubuntu. https://bugs.launchpad.net/bugs/1820860 Title: /usr/bin/software-properties- gtk:RuntimeError(org.freedesktop.DBus.Python.RuntimeError):on_driver_changes_cancel:_deferable:_convert_dbus_exception:_convert_dbus_exception:cancel:__call__:call_blocking:_inline_callbacks:get_uid_from_dbus_name:return_value:_inline_callbacks:_cancel:_inline_callbacks Status in software-properties package in Ubuntu: New Bug description: The Ubuntu Error Tracker has been receiving reports about a problem regarding software-properties. This problem was most recently seen with package version 0.97.9, the problem page at https://errors.ubuntu.com/problem/6567b1f317a885bc109de031608c5f1c675d1ae0 contains more details, including versions of packages affected, stacktrace or traceback, and individual crash reports. If you do not have access to the Ubuntu Error Tracker and are a software developer, you can request it at http://forms.canonical.com/reports/. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/software-properties/+bug/1820860/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1820863] [NEW] /usr/bin/software-properties-gtk:KeyError:__getitem__:on_driver_changes_finish:set_driver_action_status:__getitem__
Public bug reported: The Ubuntu Error Tracker has been receiving reports about a problem regarding software-properties. This problem was most recently seen with package version 0.97.9, the problem page at https://errors.ubuntu.com/problem/7aae2289a43859d4f1ec3b362edf284bcc6dca7a contains more details, including versions of packages affected, stacktrace or traceback, and individual crash reports. If you do not have access to the Ubuntu Error Tracker and are a software developer, you can request it at http://forms.canonical.com/reports/. ** Affects: software-properties (Ubuntu) Importance: Undecided Status: New ** Tags: cosmic disco -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to software-properties in Ubuntu. https://bugs.launchpad.net/bugs/1820863 Title: /usr/bin/software-properties- gtk:KeyError:__getitem__:on_driver_changes_finish:set_driver_action_status:__getitem__ Status in software-properties package in Ubuntu: New Bug description: The Ubuntu Error Tracker has been receiving reports about a problem regarding software-properties. This problem was most recently seen with package version 0.97.9, the problem page at https://errors.ubuntu.com/problem/7aae2289a43859d4f1ec3b362edf284bcc6dca7a contains more details, including versions of packages affected, stacktrace or traceback, and individual crash reports. If you do not have access to the Ubuntu Error Tracker and are a software developer, you can request it at http://forms.canonical.com/reports/. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/software-properties/+bug/1820863/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1820858] [NEW] /usr/bin/software-properties-gtk:RuntimeError(org.freedesktop.DBus.Python.RuntimeError):_on_clicked:_deferable:_convert_dbus_exception:_convert_dbus_exception:canc
Public bug reported: The Ubuntu Error Tracker has been receiving reports about a problem regarding software-properties. This problem was most recently seen with package version 0.97.9, the problem page at https://errors.ubuntu.com/problem/9dd1fadc5a92a7832c23ed5340c79bf6c9f88eee contains more details, including versions of packages affected, stacktrace or traceback, and individual crash reports. If you do not have access to the Ubuntu Error Tracker and are a software developer, you can request it at http://forms.canonical.com/reports/. ** Affects: software-properties (Ubuntu) Importance: Undecided Status: New ** Tags: cosmic disco -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to software-properties in Ubuntu. https://bugs.launchpad.net/bugs/1820858 Title: /usr/bin/software-properties- gtk:RuntimeError(org.freedesktop.DBus.Python.RuntimeError):_on_clicked:_deferable:_convert_dbus_exception:_convert_dbus_exception:cancel:__call__:call_blocking:_inline_callbacks:get_uid_from_dbus_name:return_value:_inline_callbacks:_cancel:_inline_callbacks Status in software-properties package in Ubuntu: New Bug description: The Ubuntu Error Tracker has been receiving reports about a problem regarding software-properties. This problem was most recently seen with package version 0.97.9, the problem page at https://errors.ubuntu.com/problem/9dd1fadc5a92a7832c23ed5340c79bf6c9f88eee contains more details, including versions of packages affected, stacktrace or traceback, and individual crash reports. If you do not have access to the Ubuntu Error Tracker and are a software developer, you can request it at http://forms.canonical.com/reports/. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/software-properties/+bug/1820858/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1820854] [NEW] Don't hide GdkWindow on grab failure
Public bug reported: I have problem when always-on-top window appears on screen or after it closing for example terminal menu panel does not react to keyboard button pressing and mouse pointer events. To recreate this problem: 1.Login into ubuntu session; 2.Open terminal; 3.Run for exmaple 'ssh-askpass' (which creates always-on-top-window); 4.Try to press terminal menu buttons (they will not respond); 5.Close 'ssh-askpass' and try again to press terminal toolbar menu buttons (they will not respond); But I found a sollution which helps application panel to react for events while showing or after closing always-on-top window here https://gitlab.gnome.org/GNOME/gtk/commit/2c8b95a518bea2192145efe11219f2e36091b37a This sollution is added to upstream in gtk3.0 for Ubuntu 18.10. I use gtk+3.0_3.22.30-1ubuntu2 version. My OS is - Ubuntu 18.04.2 LTS Release: 18.04. ** Affects: gtk+3.0 (Ubuntu) Importance: Undecided Status: Confirmed -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to gtk+3.0 in Ubuntu. https://bugs.launchpad.net/bugs/1820854 Title: Don't hide GdkWindow on grab failure Status in gtk+3.0 package in Ubuntu: Confirmed Bug description: I have problem when always-on-top window appears on screen or after it closing for example terminal menu panel does not react to keyboard button pressing and mouse pointer events. To recreate this problem: 1.Login into ubuntu session; 2.Open terminal; 3.Run for exmaple 'ssh-askpass' (which creates always-on-top-window); 4.Try to press terminal menu buttons (they will not respond); 5.Close 'ssh-askpass' and try again to press terminal toolbar menu buttons (they will not respond); But I found a sollution which helps application panel to react for events while showing or after closing always-on-top window here https://gitlab.gnome.org/GNOME/gtk/commit/2c8b95a518bea2192145efe11219f2e36091b37a This sollution is added to upstream in gtk3.0 for Ubuntu 18.10. I use gtk+3.0_3.22.30-1ubuntu2 version. My OS is - Ubuntu 18.04.2 LTS Release: 18.04. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gtk+3.0/+bug/1820854/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1820854] Re: Don't hide GdkWindow on grab failure
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: gtk+3.0 (Ubuntu) Status: New => Confirmed -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to gtk+3.0 in Ubuntu. https://bugs.launchpad.net/bugs/1820854 Title: Don't hide GdkWindow on grab failure Status in gtk+3.0 package in Ubuntu: Confirmed Bug description: I have problem when always-on-top window appears on screen or after it closing for example terminal menu panel does not react to keyboard button pressing and mouse pointer events. To recreate this problem: 1.Login into ubuntu session; 2.Open terminal; 3.Run for exmaple 'ssh-askpass' (which creates always-on-top-window); 4.Try to press terminal menu buttons (they will not respond); 5.Close 'ssh-askpass' and try again to press terminal toolbar menu buttons (they will not respond); But I found a sollution which helps application panel to react for events while showing or after closing always-on-top window here https://gitlab.gnome.org/GNOME/gtk/commit/2c8b95a518bea2192145efe11219f2e36091b37a This sollution is added to upstream in gtk3.0 for Ubuntu 18.10. I use gtk+3.0_3.22.30-1ubuntu2 version. My OS is - Ubuntu 18.04.2 LTS Release: 18.04. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gtk+3.0/+bug/1820854/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1820314] Re: [To Be Filled By O.E.M., Realtek ALC662 rev1, Green Line Out, Rear] No sound at all
BIOS setting in the video above -- 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/1820314 Title: [To Be Filled By O.E.M., Realtek ALC662 rev1, Green Line Out, Rear] No sound at all Status in alsa-driver package in Ubuntu: New Bug description: cannot hear any sound even with headphones from any of 2 rear output port (green and blue) of my asrock fm2a75m-dgs or the front unique one. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: alsa-base 1.0.25+dfsg-0ubuntu5 ProcVersionSignature: Ubuntu 4.4.0-98.121-generic 4.4.90 Uname: Linux 4.4.0-98-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.9-0ubuntu7.5 Architecture: amd64 CurrentDesktop: XFCE Date: Fri Mar 15 17:32:51 2019 InstallationDate: Installed on 2016-09-07 (918 days ago) InstallationMedia: Xubuntu 16.04 LTS "Xenial Xerus" - Release amd64 (20160420.1) PackageArchitecture: all ProcEnviron: LANGUAGE=it PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=it_IT.UTF-8 SHELL=/bin/bash SourcePackage: alsa-driver Symptom: audio Symptom_AlsaPlaybackTest: ALSA playback test through plughw:Generic failed Symptom_Card: Audio interno - HD-Audio Generic Symptom_Jack: Green Line Out, Rear Symptom_Type: No sound at all Title: [To Be Filled By O.E.M., Realtek ALC662 rev1, Green Line Out, Rear] No sound at all UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 12/01/2016 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: P2.70 dmi.board.name: FM2A75M-DGS 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.70:bd12/01/2016:svnToBeFilledByO.E.M.:pnToBeFilledByO.E.M.:pvrToBeFilledByO.E.M.:rvnASRock:rnFM2A75M-DGS: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. modified.conffile..etc.modprobe.d.alsa-base.conf: options snd-hda-intel model=auto mtime.conffile..etc.modprobe.d.alsa-base.conf: 2019-03-14T16:54:28.355882 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1820314/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1820314] Re: [To Be Filled By O.E.M., Realtek ALC662 rev1, Green Line Out, Rear] No sound at all
https://streamable.com/5j96k -- 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/1820314 Title: [To Be Filled By O.E.M., Realtek ALC662 rev1, Green Line Out, Rear] No sound at all Status in alsa-driver package in Ubuntu: New Bug description: cannot hear any sound even with headphones from any of 2 rear output port (green and blue) of my asrock fm2a75m-dgs or the front unique one. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: alsa-base 1.0.25+dfsg-0ubuntu5 ProcVersionSignature: Ubuntu 4.4.0-98.121-generic 4.4.90 Uname: Linux 4.4.0-98-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.9-0ubuntu7.5 Architecture: amd64 CurrentDesktop: XFCE Date: Fri Mar 15 17:32:51 2019 InstallationDate: Installed on 2016-09-07 (918 days ago) InstallationMedia: Xubuntu 16.04 LTS "Xenial Xerus" - Release amd64 (20160420.1) PackageArchitecture: all ProcEnviron: LANGUAGE=it PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=it_IT.UTF-8 SHELL=/bin/bash SourcePackage: alsa-driver Symptom: audio Symptom_AlsaPlaybackTest: ALSA playback test through plughw:Generic failed Symptom_Card: Audio interno - HD-Audio Generic Symptom_Jack: Green Line Out, Rear Symptom_Type: No sound at all Title: [To Be Filled By O.E.M., Realtek ALC662 rev1, Green Line Out, Rear] No sound at all UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 12/01/2016 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: P2.70 dmi.board.name: FM2A75M-DGS 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.70:bd12/01/2016:svnToBeFilledByO.E.M.:pnToBeFilledByO.E.M.:pvrToBeFilledByO.E.M.:rvnASRock:rnFM2A75M-DGS: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. modified.conffile..etc.modprobe.d.alsa-base.conf: options snd-hda-intel model=auto mtime.conffile..etc.modprobe.d.alsa-base.conf: 2019-03-14T16:54:28.355882 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1820314/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1698159] Re: linux-cloud-tools version specific packages are being removed by unattended-upgrade's Remove-Unused-Dependencies
@rbalint it says "Keeping the following auto-removable package(s) because they include linux-cloud-tools-4.15.0-39-generic which package is related to the running kernel: linux-cloud-tools-4.15.0-39-generic linux-cloud-tools-common linux-hwe-cloud-tools-4.15.0-39". So if 4.15.0-39-generic was not the running kernel, those would have been removed, even if the kernel itself was protected? -- 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/1698159 Title: linux-cloud-tools version specific packages are being removed by unattended-upgrade's Remove-Unused-Dependencies Status in apt package in Ubuntu: Fix Released Status in unattended-upgrades package in Ubuntu: Fix Released Status in apt source package in Trusty: Triaged Status in unattended-upgrades source package in Trusty: New Status in apt source package in Xenial: Fix Released Status in unattended-upgrades source package in Xenial: Fix Committed Status in apt source package in Bionic: Fix Released Status in unattended-upgrades source package in Bionic: Fix Released Bug description: [Impact] When running kernel version 4.4.0-78 (for example) and the unattended-upgrade packages installs a new kernel 4.4.0-79 (for example) the linux-cloud-tools-4.4.0-78 and linux-cloud-tools-4.4.0-78-generic packages are removed by the Remove-Unused-Dependencies rule, because unlike "normal" kernel packages they are not excluded by /etc/apt/apt.conf.d/01autoremove-kernels. The linux-cloud-tools package has the hyper-v integration services daemons in it, so it's deletion leaves some of the integration not working. Could /etc/apt/apt.conf.d/01autoremove-kernels be updated so other hyper-v users aren't caught out by this? Thanks, Ian. [Test case (apt)] Make sure that linux-cloud-tools for protected kernels are listed in APT::NeverAutoRemove, for example, on cosmic: "^linux-cloud-tools-4\.17\.0-9-generic$"; "^linux-cloud-tools-4\.18\.0-7-generic$"; Those are in 01autoremove-kernels [Test case (unattended-upgrades)] * Check the running kernel and install relevant cloud-tools packages: # uname -a Linux x-uu-lp-1737637 4.15.0-39-generic #42-Ubuntu SMP Tue Oct 23 15:48:01 UTC 2018 x86_64 x86_64 x86_64 GNU/Linux root@x-uu-lp-1737637:~# apt-cache search 4.15.0-39-generic linux-cloud-tools-4.15.0-39-generic - Linux kernel version specific cloud tools for version 4.15.0-39 linux-headers-4.15.0-39-generic - Linux kernel headers for version 4.15.0 on 64 bit x86 SMP linux-image-4.15.0-39-generic - Signed kernel image generic linux-image-unsigned-4.15.0-39-generic - Linux kernel image for version 4.15.0 on 64 bit x86 SMP linux-modules-4.15.0-39-generic - Linux kernel extra modules for version 4.15.0 on 64 bit x86 SMP linux-modules-extra-4.15.0-39-generic - Linux kernel extra modules for version 4.15.0 on 64 bit x86 SMP # apt install linux-cloud-tools-4.15.0-39-generic Reading package lists... Done Building dependency tree Reading state information... Done The following package was automatically installed and is no longer required: libfreetype6 Use 'apt autoremove' to remove it. The following additional packages will be installed: linux-cloud-tools-common linux-hwe-cloud-tools-4.15.0-39 The following NEW packages will be installed: linux-cloud-tools-4.15.0-39-generic linux-cloud-tools-common linux-hwe-cloud-tools-4.15.0-39 0 upgraded, 3 newly installed, 0 to remove and 17 not upgraded. Need to get 119 kB of archives. After this operation, 854 kB of additional disk space will be used. Do you want to continue? [Y/n] ... * Mark them autoremovable and configure u-u to autoremove unused packages: # apt-mark auto linux-cloud-tools-4.15.0-39-generic linux-cloud-tools-4.15.0-39-generic set to automatically installed. ### set Unattended-Upgrade::Remove-Unused-Dependencies "true"; # vi /etc/apt/apt.conf.d/50unattended-upgrades * The not fixed version of u-u removes the packages: # unattended-upgrade --dry-run --verbose ... All upgrades installed Packages that are auto removed: 'libfreetype6 linux-cloud-tools-4.15.0-39-generic linux-cloud-tools-common linux-hwe-cloud-tools-4.15.0-39' Packages were successfully auto-removed # * The fixed version does not: # unattended-upgrade --dry-run --verbose Initial blacklisted packages: Initial whitelisted packages: Starting unattended upgrades script Allowed origins are: o=Ubuntu,a=xenial, o=Ubuntu,a=xenial-security, o=UbuntuESM,a=xenial Removing unused kernel packages: linux-cloud-tools-common Keeping auto-removable linux-cloud-tools-common package(s) because it would also remove the following packages which should be kept in this step: linux-cloud-tools-4.15.0-39-generic linux-hwe-cloud-tools-4.15.0-39 ... [Regression Potential] *
[Touch-packages] [Bug 1675079] Re: 16.04 LTS Partition /boot fills up with Kernel images, gets underwear in a twist
@rbalint Why it does not remove linux-image-4.8.0-53-generic? -- 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/1675079 Title: 16.04 LTS Partition /boot fills up with Kernel images, gets underwear in a twist Status in unattended-upgrades package in Ubuntu: Fix Released Status in update-manager package in Ubuntu: Fix Released Status in unattended-upgrades source package in Xenial: Fix Committed Status in update-manager source package in Xenial: Fix Released Status in unattended-upgrades source package in Artful: Won't Fix Status in update-manager source package in Artful: Fix Released Bug description: [Impact] * Update-manager and unattended-upgrades install many kernel packages during the lifetime of a release but does not remove them automatically leading to those packages filling disk space potentially completely filling /boot and making the system unable to install updates or even boot. * Stable release users are impacted by this bug for years and their systems already collected many autoremovable unused kernel packages, thus they would benefit from backporting the fix greatly. * The bug is fixed by removing autoremovable (not currently booted) kernel packages when running unattended-upgrades or update-manager. Update manager offers the kernel removals when there are other updates to be installed. [Test Case] 1. Install kernel packages to be removed, mark them auto-installed and run apt's kernel hook script to make apt consider them autoremovable: sudo apt install -y linux-image-extra-4.4.0-92-generic linux-image-extra-4.4.0-93-generic sudo apt-mark auto linux-image-extra-4.4.0-92-generic linux-image-extra-4.4.0-93-generic sudo /etc/kernel/postinst.d/apt-auto-removal 2. Also downgrade a package to be upgraded: sudo apt-get install -y --allow-downgrades ca- certificates=20160104ubuntu1 3. (update-manager). Run update-manager and observe that kernel packages are offered for removal in Details of updates. sudo update-manager 4. (update-manager) Click on Install Now and observe that the kernel packages are removed. 3. (unattended-upgrades) Run unattended-upgrades manually and observe the removal of the autoremovable kernel packages: sudo unattended-upgrade -v [Regression Potential] The change may cause update-manager or unattanded-upgrades to remove used kernel packages or fail to install other package updates. [Other Info] The unattended-upgrades fix is uploaded with many other fixes and those may cause regressions in other areas in unattended-upgrades. [Original bug text] On a 16.04LTS system, the /boot partition will eventually fill with Kernel images, until the point where "apt-get autoremove" can't complete. This issue has previously been reported as fixed, but it is not fixed: https://bugs.launchpad.net/ubuntu/+source/unattended-upgrades/+bug/1357093 Generally what I see is the final kernel image that fills the drive is incompletely installed (the header package does not make it). "apt- get autoremove" tries to work, but fails. I must manually remove kernel images to free enough space. I see this on a machine used by my elderly parents, where 'Download and install updates automatically' is set. And on my home machines, where the setting is elsewhere. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/unattended-upgrades/+bug/1675079/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1820314] Re: [To Be Filled By O.E.M., Realtek ALC662 rev1, Green Line Out, Rear] No sound at all
The problem occurs even on live xubuntu 18.04 17.10 16.04 even modifying alsa-base in options snd-hda-intel model=auto or options snd-hda-intel model=asrock-mobo or options snd-hda-intel model=generic.; all on board audio port are shown as unplugged. Thus HDMI of the Nvidia GTX 1050ti seems to work perfectly when I connected to TV HDMI input (but could not steal TV 4 ever) -- 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/1820314 Title: [To Be Filled By O.E.M., Realtek ALC662 rev1, Green Line Out, Rear] No sound at all Status in alsa-driver package in Ubuntu: New Bug description: cannot hear any sound even with headphones from any of 2 rear output port (green and blue) of my asrock fm2a75m-dgs or the front unique one. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: alsa-base 1.0.25+dfsg-0ubuntu5 ProcVersionSignature: Ubuntu 4.4.0-98.121-generic 4.4.90 Uname: Linux 4.4.0-98-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.9-0ubuntu7.5 Architecture: amd64 CurrentDesktop: XFCE Date: Fri Mar 15 17:32:51 2019 InstallationDate: Installed on 2016-09-07 (918 days ago) InstallationMedia: Xubuntu 16.04 LTS "Xenial Xerus" - Release amd64 (20160420.1) PackageArchitecture: all ProcEnviron: LANGUAGE=it PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=it_IT.UTF-8 SHELL=/bin/bash SourcePackage: alsa-driver Symptom: audio Symptom_AlsaPlaybackTest: ALSA playback test through plughw:Generic failed Symptom_Card: Audio interno - HD-Audio Generic Symptom_Jack: Green Line Out, Rear Symptom_Type: No sound at all Title: [To Be Filled By O.E.M., Realtek ALC662 rev1, Green Line Out, Rear] No sound at all UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 12/01/2016 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: P2.70 dmi.board.name: FM2A75M-DGS 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.70:bd12/01/2016:svnToBeFilledByO.E.M.:pnToBeFilledByO.E.M.:pvrToBeFilledByO.E.M.:rvnASRock:rnFM2A75M-DGS: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. modified.conffile..etc.modprobe.d.alsa-base.conf: options snd-hda-intel model=auto mtime.conffile..etc.modprobe.d.alsa-base.conf: 2019-03-14T16:54:28.355882 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1820314/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1820314] Re: [To Be Filled By O.E.M., Realtek ALC662 rev1, Green Line Out, Rear] No sound at all
https://ubuntuforums.org/showthread.php?t=2414882=13845231#post13845231 -- 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/1820314 Title: [To Be Filled By O.E.M., Realtek ALC662 rev1, Green Line Out, Rear] No sound at all Status in alsa-driver package in Ubuntu: New Bug description: cannot hear any sound even with headphones from any of 2 rear output port (green and blue) of my asrock fm2a75m-dgs or the front unique one. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: alsa-base 1.0.25+dfsg-0ubuntu5 ProcVersionSignature: Ubuntu 4.4.0-98.121-generic 4.4.90 Uname: Linux 4.4.0-98-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.9-0ubuntu7.5 Architecture: amd64 CurrentDesktop: XFCE Date: Fri Mar 15 17:32:51 2019 InstallationDate: Installed on 2016-09-07 (918 days ago) InstallationMedia: Xubuntu 16.04 LTS "Xenial Xerus" - Release amd64 (20160420.1) PackageArchitecture: all ProcEnviron: LANGUAGE=it PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=it_IT.UTF-8 SHELL=/bin/bash SourcePackage: alsa-driver Symptom: audio Symptom_AlsaPlaybackTest: ALSA playback test through plughw:Generic failed Symptom_Card: Audio interno - HD-Audio Generic Symptom_Jack: Green Line Out, Rear Symptom_Type: No sound at all Title: [To Be Filled By O.E.M., Realtek ALC662 rev1, Green Line Out, Rear] No sound at all UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 12/01/2016 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: P2.70 dmi.board.name: FM2A75M-DGS 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.70:bd12/01/2016:svnToBeFilledByO.E.M.:pnToBeFilledByO.E.M.:pvrToBeFilledByO.E.M.:rvnASRock:rnFM2A75M-DGS: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. modified.conffile..etc.modprobe.d.alsa-base.conf: options snd-hda-intel model=auto mtime.conffile..etc.modprobe.d.alsa-base.conf: 2019-03-14T16:54:28.355882 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1820314/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1818802] Re: [ZenBook UX433FN_UX433FN, Realtek ALC294, Speaker, Internal] fails after a while
It* -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to pulseaudio in Ubuntu. https://bugs.launchpad.net/bugs/1818802 Title: [ZenBook UX433FN_UX433FN, Realtek ALC294, Speaker, Internal] fails after a while Status in linux package in Ubuntu: Incomplete Status in pulseaudio package in Ubuntu: Incomplete Bug description: Audio dies after few seconds, returns after few minutes and dies again filip@ux433:~$ lsb_release -rd Description: Ubuntu 18.10 Release: 18.10 ProblemType: Bug DistroRelease: Ubuntu 18.10 Package: alsa-base 1.0.25+dfsg-0ubuntu5 Uname: Linux 4.20.14-042014-generic x86_64 ApportVersion: 2.20.10-0ubuntu13.2 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: filip 8566 F pulseaudio /dev/snd/pcmC0D0p: filip 8566 F...m pulseaudio CurrentDesktop: ubuntu:GNOME Date: Wed Mar 6 10:11:01 2019 InstallationDate: Installed on 2019-01-05 (59 days ago) InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 (20180725) PackageArchitecture: all SourcePackage: alsa-driver Symptom: audio Symptom_Card: Built-in Audio - HDA Intel PCH Symptom_Jack: Speaker, Internal Symptom_PulseAudioLog: mar 06 10:04:08 ux433 dbus-daemon[3008]: [system] Activating via systemd: service name='org.freedesktop.RealtimeKit1' unit='rtkit-daemon.service' requested by ':1.37' (uid=121 pid=6142 comm="/usr/bin/pulseaudio --daemonize=no ") Symptom_Type: Sound works for a while, then breaks Title: [ZenBook UX433FN_UX433FN, Realtek ALC294, Speaker, Internal] fails after a while UpgradeStatus: Upgraded to cosmic on 2019-01-28 (36 days ago) dmi.bios.date: 11/21/2018 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: UX433FN.301 dmi.board.asset.tag: ATN12345678901234567 dmi.board.name: UX433FN dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: 1.0 dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: ASUSTeK COMPUTER INC. dmi.chassis.version: 1.0 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrUX433FN.301:bd11/21/2018:svnASUSTeKCOMPUTERINC.:pnZenBookUX433FN_UX433FN:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnUX433FN:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0: dmi.product.family: ZenBook dmi.product.name: ZenBook UX433FN_UX433FN 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/linux/+bug/1818802/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1818802] Re: [ZenBook UX433FN_UX433FN, Realtek ALC294, Speaker, Internal] fails after a while
I did return yesterday. I uploaded the files you requested before. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to pulseaudio in Ubuntu. https://bugs.launchpad.net/bugs/1818802 Title: [ZenBook UX433FN_UX433FN, Realtek ALC294, Speaker, Internal] fails after a while Status in linux package in Ubuntu: Incomplete Status in pulseaudio package in Ubuntu: Incomplete Bug description: Audio dies after few seconds, returns after few minutes and dies again filip@ux433:~$ lsb_release -rd Description: Ubuntu 18.10 Release: 18.10 ProblemType: Bug DistroRelease: Ubuntu 18.10 Package: alsa-base 1.0.25+dfsg-0ubuntu5 Uname: Linux 4.20.14-042014-generic x86_64 ApportVersion: 2.20.10-0ubuntu13.2 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: filip 8566 F pulseaudio /dev/snd/pcmC0D0p: filip 8566 F...m pulseaudio CurrentDesktop: ubuntu:GNOME Date: Wed Mar 6 10:11:01 2019 InstallationDate: Installed on 2019-01-05 (59 days ago) InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 (20180725) PackageArchitecture: all SourcePackage: alsa-driver Symptom: audio Symptom_Card: Built-in Audio - HDA Intel PCH Symptom_Jack: Speaker, Internal Symptom_PulseAudioLog: mar 06 10:04:08 ux433 dbus-daemon[3008]: [system] Activating via systemd: service name='org.freedesktop.RealtimeKit1' unit='rtkit-daemon.service' requested by ':1.37' (uid=121 pid=6142 comm="/usr/bin/pulseaudio --daemonize=no ") Symptom_Type: Sound works for a while, then breaks Title: [ZenBook UX433FN_UX433FN, Realtek ALC294, Speaker, Internal] fails after a while UpgradeStatus: Upgraded to cosmic on 2019-01-28 (36 days ago) dmi.bios.date: 11/21/2018 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: UX433FN.301 dmi.board.asset.tag: ATN12345678901234567 dmi.board.name: UX433FN dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: 1.0 dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: ASUSTeK COMPUTER INC. dmi.chassis.version: 1.0 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrUX433FN.301:bd11/21/2018:svnASUSTeKCOMPUTERINC.:pnZenBookUX433FN_UX433FN:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnUX433FN:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0: dmi.product.family: ZenBook dmi.product.name: ZenBook UX433FN_UX433FN 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/linux/+bug/1818802/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1773897]
My intention is to ask you to try adding this entry to pin-code-database.xml: -- 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/1773897 Title: [regression] Logitech M337 mice are automatically disconnected after connected Status in Bluez Utilities: Confirmed Status in OEM Priority Project: New Status in bluez package in Ubuntu: Confirmed Bug description: The BT 3.0 mouse is disconnected automatically after connected with the notebook. The fail rate is around 9/10. 1. The bug only occurs on the machine with intel 8265 module. I got three Dell XPS 13 (one is with Killer 1435, two are with intel 8265). This bug can not be reproduced on the machine with Killer 1435. 2. This bug can be reproduced since bluez 5.46. Using bluez 5.45, this bug can not be reproduced. Notebook: Dell XPS 13 Wi-Fi/BT module: intel 8265, 8087:0a2b bluez: 5.48 BT mouse: logitech M337 --- ApportVersion: 2.20.9-0ubuntu7 Architecture: amd64 CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 18.04 InstallationDate: Installed on 2018-05-29 (0 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426) InterestingModules: rfcomm bnep btusb bluetooth Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 003: ID 8087:0a2b Intel Corp. Bus 001 Device 002: ID 0bda:58f4 Realtek Semiconductor Corp. Bus 001 Device 004: ID 27c6:5385 Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: Dell Inc. XPS 13 9370 Package: bluez 5.48-0ubuntu3 [origin: unknown] PackageArchitecture: amd64 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-22-generic root=UUID=d6251f09-cbb5-4635-8f42-31e6c32f1c03 ro quiet splash vt.handoff=1 ProcVersionSignature: Ubuntu 4.15.0-22.24-generic 4.15.17 Tags: third-party-packages bionic Uname: Linux 4.15.0-22-generic x86_64 UnreportableReason: This is not an official Ubuntu package. Please remove any third party package and try again. UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 11/03/2017 dmi.bios.vendor: Dell Inc. dmi.bios.version: 0.3.13 dmi.board.name: 0173S1 dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 9 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr0.3.13:bd11/03/2017:svnDellInc.:pnXPS139370:pvr:rvnDellInc.:rn0173S1:rvrA00:cvnDellInc.:ct9:cvr: dmi.product.family: XPS dmi.product.name: XPS 13 9370 dmi.sys.vendor: Dell Inc. hciconfig: hci0:Type: Primary Bus: USB BD Address: D4:25:8B:4F:7E:D6 ACL MTU: 1021:4 SCO MTU: 96:6 UP RUNNING PSCAN ISCAN RX bytes:61781 acl:382 sco:0 events:536 errors:0 TX bytes:7985 acl:69 sco:0 commands:168 errors:0 To manage notifications about this bug go to: https://bugs.launchpad.net/bluez/+bug/1773897/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1773897]
Do you folks use gnome-control-center to pair? -- 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/1773897 Title: [regression] Logitech M337 mice are automatically disconnected after connected Status in Bluez Utilities: Confirmed Status in OEM Priority Project: New Status in bluez package in Ubuntu: Confirmed Bug description: The BT 3.0 mouse is disconnected automatically after connected with the notebook. The fail rate is around 9/10. 1. The bug only occurs on the machine with intel 8265 module. I got three Dell XPS 13 (one is with Killer 1435, two are with intel 8265). This bug can not be reproduced on the machine with Killer 1435. 2. This bug can be reproduced since bluez 5.46. Using bluez 5.45, this bug can not be reproduced. Notebook: Dell XPS 13 Wi-Fi/BT module: intel 8265, 8087:0a2b bluez: 5.48 BT mouse: logitech M337 --- ApportVersion: 2.20.9-0ubuntu7 Architecture: amd64 CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 18.04 InstallationDate: Installed on 2018-05-29 (0 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426) InterestingModules: rfcomm bnep btusb bluetooth Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 003: ID 8087:0a2b Intel Corp. Bus 001 Device 002: ID 0bda:58f4 Realtek Semiconductor Corp. Bus 001 Device 004: ID 27c6:5385 Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: Dell Inc. XPS 13 9370 Package: bluez 5.48-0ubuntu3 [origin: unknown] PackageArchitecture: amd64 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-22-generic root=UUID=d6251f09-cbb5-4635-8f42-31e6c32f1c03 ro quiet splash vt.handoff=1 ProcVersionSignature: Ubuntu 4.15.0-22.24-generic 4.15.17 Tags: third-party-packages bionic Uname: Linux 4.15.0-22-generic x86_64 UnreportableReason: This is not an official Ubuntu package. Please remove any third party package and try again. UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 11/03/2017 dmi.bios.vendor: Dell Inc. dmi.bios.version: 0.3.13 dmi.board.name: 0173S1 dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 9 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr0.3.13:bd11/03/2017:svnDellInc.:pnXPS139370:pvr:rvnDellInc.:rn0173S1:rvrA00:cvnDellInc.:ct9:cvr: dmi.product.family: XPS dmi.product.name: XPS 13 9370 dmi.sys.vendor: Dell Inc. hciconfig: hci0:Type: Primary Bus: USB BD Address: D4:25:8B:4F:7E:D6 ACL MTU: 1021:4 SCO MTU: 96:6 UP RUNNING PSCAN ISCAN RX bytes:61781 acl:382 sco:0 events:536 errors:0 TX bytes:7985 acl:69 sco:0 commands:168 errors:0 To manage notifications about this bug go to: https://bugs.launchpad.net/bluez/+bug/1773897/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1773897]
I tried the pairing via the gnome control center, command line ( bluetoothctl ) and via blueman. These were done while in a gnome session however All three attempts failed as above. -- 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/1773897 Title: [regression] Logitech M337 mice are automatically disconnected after connected Status in Bluez Utilities: Confirmed Status in OEM Priority Project: New Status in bluez package in Ubuntu: Confirmed Bug description: The BT 3.0 mouse is disconnected automatically after connected with the notebook. The fail rate is around 9/10. 1. The bug only occurs on the machine with intel 8265 module. I got three Dell XPS 13 (one is with Killer 1435, two are with intel 8265). This bug can not be reproduced on the machine with Killer 1435. 2. This bug can be reproduced since bluez 5.46. Using bluez 5.45, this bug can not be reproduced. Notebook: Dell XPS 13 Wi-Fi/BT module: intel 8265, 8087:0a2b bluez: 5.48 BT mouse: logitech M337 --- ApportVersion: 2.20.9-0ubuntu7 Architecture: amd64 CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 18.04 InstallationDate: Installed on 2018-05-29 (0 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426) InterestingModules: rfcomm bnep btusb bluetooth Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 003: ID 8087:0a2b Intel Corp. Bus 001 Device 002: ID 0bda:58f4 Realtek Semiconductor Corp. Bus 001 Device 004: ID 27c6:5385 Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: Dell Inc. XPS 13 9370 Package: bluez 5.48-0ubuntu3 [origin: unknown] PackageArchitecture: amd64 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-22-generic root=UUID=d6251f09-cbb5-4635-8f42-31e6c32f1c03 ro quiet splash vt.handoff=1 ProcVersionSignature: Ubuntu 4.15.0-22.24-generic 4.15.17 Tags: third-party-packages bionic Uname: Linux 4.15.0-22-generic x86_64 UnreportableReason: This is not an official Ubuntu package. Please remove any third party package and try again. UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 11/03/2017 dmi.bios.vendor: Dell Inc. dmi.bios.version: 0.3.13 dmi.board.name: 0173S1 dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 9 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr0.3.13:bd11/03/2017:svnDellInc.:pnXPS139370:pvr:rvnDellInc.:rn0173S1:rvrA00:cvnDellInc.:ct9:cvr: dmi.product.family: XPS dmi.product.name: XPS 13 9370 dmi.sys.vendor: Dell Inc. hciconfig: hci0:Type: Primary Bus: USB BD Address: D4:25:8B:4F:7E:D6 ACL MTU: 1021:4 SCO MTU: 96:6 UP RUNNING PSCAN ISCAN RX bytes:61781 acl:382 sco:0 events:536 errors:0 TX bytes:7985 acl:69 sco:0 commands:168 errors:0 To manage notifications about this bug go to: https://bugs.launchpad.net/bluez/+bug/1773897/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1773897]
Take a look at [1] if gnome-control-center is used: [1] https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/1773897/comments/43 -- 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/1773897 Title: [regression] Logitech M337 mice are automatically disconnected after connected Status in Bluez Utilities: Confirmed Status in OEM Priority Project: New Status in bluez package in Ubuntu: Confirmed Bug description: The BT 3.0 mouse is disconnected automatically after connected with the notebook. The fail rate is around 9/10. 1. The bug only occurs on the machine with intel 8265 module. I got three Dell XPS 13 (one is with Killer 1435, two are with intel 8265). This bug can not be reproduced on the machine with Killer 1435. 2. This bug can be reproduced since bluez 5.46. Using bluez 5.45, this bug can not be reproduced. Notebook: Dell XPS 13 Wi-Fi/BT module: intel 8265, 8087:0a2b bluez: 5.48 BT mouse: logitech M337 --- ApportVersion: 2.20.9-0ubuntu7 Architecture: amd64 CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 18.04 InstallationDate: Installed on 2018-05-29 (0 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426) InterestingModules: rfcomm bnep btusb bluetooth Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 003: ID 8087:0a2b Intel Corp. Bus 001 Device 002: ID 0bda:58f4 Realtek Semiconductor Corp. Bus 001 Device 004: ID 27c6:5385 Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: Dell Inc. XPS 13 9370 Package: bluez 5.48-0ubuntu3 [origin: unknown] PackageArchitecture: amd64 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-22-generic root=UUID=d6251f09-cbb5-4635-8f42-31e6c32f1c03 ro quiet splash vt.handoff=1 ProcVersionSignature: Ubuntu 4.15.0-22.24-generic 4.15.17 Tags: third-party-packages bionic Uname: Linux 4.15.0-22-generic x86_64 UnreportableReason: This is not an official Ubuntu package. Please remove any third party package and try again. UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 11/03/2017 dmi.bios.vendor: Dell Inc. dmi.bios.version: 0.3.13 dmi.board.name: 0173S1 dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 9 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr0.3.13:bd11/03/2017:svnDellInc.:pnXPS139370:pvr:rvnDellInc.:rn0173S1:rvrA00:cvnDellInc.:ct9:cvr: dmi.product.family: XPS dmi.product.name: XPS 13 9370 dmi.sys.vendor: Dell Inc. hciconfig: hci0:Type: Primary Bus: USB BD Address: D4:25:8B:4F:7E:D6 ACL MTU: 1021:4 SCO MTU: 96:6 UP RUNNING PSCAN ISCAN RX bytes:61781 acl:382 sco:0 events:536 errors:0 TX bytes:7985 acl:69 sco:0 commands:168 errors:0 To manage notifications about this bug go to: https://bugs.launchpad.net/bluez/+bug/1773897/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1773897]
(In reply to Kai-Heng Feng from comment #5) > Do you folks use gnome-control-center to pair? I certainly did use gnome-control-center. I've just tried again with Fedora 29 (gnome-control-center-3.30.3-1.fc29.x86_64 + bluez-5.50-3.fc29.x86_64) and out of five remove, add, force reconnect) I only received a single failure. /usr/share/gnome-bluetooth/pin-code-database.xml does not seem to have any tweak applying to this mouse. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to bluez in Ubuntu. https://bugs.launchpad.net/bugs/1773897 Title: [regression] Logitech M337 mice are automatically disconnected after connected Status in Bluez Utilities: Confirmed Status in OEM Priority Project: New Status in bluez package in Ubuntu: Confirmed Bug description: The BT 3.0 mouse is disconnected automatically after connected with the notebook. The fail rate is around 9/10. 1. The bug only occurs on the machine with intel 8265 module. I got three Dell XPS 13 (one is with Killer 1435, two are with intel 8265). This bug can not be reproduced on the machine with Killer 1435. 2. This bug can be reproduced since bluez 5.46. Using bluez 5.45, this bug can not be reproduced. Notebook: Dell XPS 13 Wi-Fi/BT module: intel 8265, 8087:0a2b bluez: 5.48 BT mouse: logitech M337 --- ApportVersion: 2.20.9-0ubuntu7 Architecture: amd64 CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 18.04 InstallationDate: Installed on 2018-05-29 (0 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426) InterestingModules: rfcomm bnep btusb bluetooth Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 003: ID 8087:0a2b Intel Corp. Bus 001 Device 002: ID 0bda:58f4 Realtek Semiconductor Corp. Bus 001 Device 004: ID 27c6:5385 Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: Dell Inc. XPS 13 9370 Package: bluez 5.48-0ubuntu3 [origin: unknown] PackageArchitecture: amd64 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-22-generic root=UUID=d6251f09-cbb5-4635-8f42-31e6c32f1c03 ro quiet splash vt.handoff=1 ProcVersionSignature: Ubuntu 4.15.0-22.24-generic 4.15.17 Tags: third-party-packages bionic Uname: Linux 4.15.0-22-generic x86_64 UnreportableReason: This is not an official Ubuntu package. Please remove any third party package and try again. UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 11/03/2017 dmi.bios.vendor: Dell Inc. dmi.bios.version: 0.3.13 dmi.board.name: 0173S1 dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 9 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr0.3.13:bd11/03/2017:svnDellInc.:pnXPS139370:pvr:rvnDellInc.:rn0173S1:rvrA00:cvnDellInc.:ct9:cvr: dmi.product.family: XPS dmi.product.name: XPS 13 9370 dmi.sys.vendor: Dell Inc. hciconfig: hci0:Type: Primary Bus: USB BD Address: D4:25:8B:4F:7E:D6 ACL MTU: 1021:4 SCO MTU: 96:6 UP RUNNING PSCAN ISCAN RX bytes:61781 acl:382 sco:0 events:536 errors:0 TX bytes:7985 acl:69 sco:0 commands:168 errors:0 To manage notifications about this bug go to: https://bugs.launchpad.net/bluez/+bug/1773897/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1334329] Re: Sound input settings not saved
I also have kind of that problem on Ubuntu 18.10. I don't want to have sound. So I mute every device. After a re boot the sound is turned back on again. It's a laptop in a dock. The system detects multiple sound devices. Internal speakers and dock output. -- 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/1334329 Title: Sound input settings not saved Status in alsa-driver package in Ubuntu: Confirmed Status in pulseaudio package in Ubuntu: Confirmed Bug description: When attempting to set my preferred sound input device, simply leaving sound preferences and going back to sound preferences, and selecting input, causes the default SPDIF to be selected again, and not the internal microphone I preferred. I made a video to demonstrate what I mean by this here: http://youtu.be/9Q9EQvLl_rA 1) The release of Ubuntu you are using, via 'lsb_release -rd' or System -> About Ubuntu 14.04 2) The version of the package you are using, via 'apt-cache policy pkgname' or by checking in Software Center I really don't know. It's just the sound preferences. 3) What you expected to happen For my selected sound input to be saved. 4) What happened instead Keeps defaulting to the top sound input ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: alsa-base 1.0.25+dfsg-0ubuntu4 ProcVersionSignature: Ubuntu 3.13.0-29.53-generic 3.13.11.2 Uname: Linux 3.13.0-29-generic x86_64 NonfreeKernelModules: wl ApportVersion: 2.14.1-0ubuntu3.2 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: brandon 23953 F pulseaudio /dev/snd/controlC0: brandon 23953 F pulseaudio CurrentDesktop: Unity Date: Wed Jun 25 11:20:14 2014 InstallationDate: Installed on 2014-04-26 (60 days ago) InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Release amd64 (20140417) PackageArchitecture: all SourcePackage: alsa-driver Symptom: audio Symptom_AlsaRecordingTest: ALSA recording test through plughw:PCH successful Symptom_Card: Caicos HDMI Audio [Radeon HD 6400 Series] - HDA ATI HDMI Symptom_PulseAudioRecordingTest: PulseAudio recording test through plughw:PCH successful Symptom_Type: None of the above Title: [HDA-Intel - HDA Intel PCH, recording] Recording problem UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 01/24/12 dmi.bios.vendor: Apple Inc. dmi.bios.version: MBP81.88Z.0047.B27.1201241646 dmi.board.asset.tag: Base Board Asset Tag# dmi.board.name: Mac-94245A3940C91C80 dmi.board.vendor: Apple Inc. dmi.board.version: MacBookPro8,2 dmi.chassis.type: 10 dmi.chassis.vendor: Apple Inc. dmi.chassis.version: Mac-94245A3940C91C80 dmi.modalias: dmi:bvnAppleInc.:bvrMBP81.88Z.0047.B27.1201241646:bd01/24/12:svnAppleInc.:pnMacBookPro8,2:pvr1.0:rvnAppleInc.:rnMac-94245A3940C91C80:rvrMacBookPro8,2:cvnAppleInc.:ct10:cvrMac-94245A3940C91C80: dmi.product.name: MacBookPro8,2 dmi.product.version: 1.0 dmi.sys.vendor: Apple Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1334329/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1780552] Re: Doesn't detected my sound card
It appears the problem here is that PulseAudio isn't running/installed. Please run this command: dpkg -l > allpackages.txt and then send us the resulting file 'allpackages.txt'. ** Package changed: alsa-driver (Ubuntu) => pulseaudio (Ubuntu) ** Changed in: pulseaudio (Ubuntu) Status: Confirmed => Incomplete ** Summary changed: - Doesn't detected my sound card + PulseAudio not running -- 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/1780552 Title: PulseAudio not running Status in pulseaudio package in Ubuntu: Incomplete Bug description: Can't turn on the audio in control Panel!! No Sound Symbol indicates in status bar!! Fix the bug soon. i using without sound since may.I am looking for a update to fix.But i Still looking to get any update from your side.I send bug report before a week.No Replays from you. Please replay me soon I'M looking for some to fix the Bug! ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: alsa-base 1.0.25+dfsg-0ubuntu5 ProcVersionSignature: Ubuntu 4.15.0-24.26-generic 4.15.18 Uname: Linux 4.15.0-24-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.2 Architecture: amd64 AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/hwC1D0', '/dev/snd/pcmC1D0c', '/dev/snd/pcmC1D0p', '/dev/snd/controlC1', '/dev/snd/by-path', '/dev/snd/hwC0D0', '/dev/snd/pcmC0D10p', '/dev/snd/pcmC0D9p', '/dev/snd/pcmC0D8p', '/dev/snd/pcmC0D7p', '/dev/snd/pcmC0D3p', '/dev/snd/controlC0', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: CurrentDesktop: ubuntu:GNOME Date: Sat Jul 7 20:49:19 2018 InstallationDate: Installed on 2018-02-11 (146 days ago) InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20180105.1) PackageArchitecture: all PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon. SourcePackage: alsa-driver Symptom: audio UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 04/22/2016 dmi.bios.vendor: Dell Inc. dmi.bios.version: A09 dmi.board.name: 0PNFDX dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 9 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvrA09:bd04/22/2016:svnDellInc.:pnInspiron3558:pvr:rvnDellInc.:rn0PNFDX:rvrA00:cvnDellInc.:ct9:cvr: dmi.product.name: Inspiron 3558 dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1780552/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1659219] Re: [Dell Inspiron 3558] Sound not working
*** This bug is a duplicate of bug 1820794 *** https://bugs.launchpad.net/bugs/1820794 Tracking in proper Ubuntu bug 1820794. ** Summary changed: - Sound not working on BackBox Linux + [Dell Inspiron 3558] Sound not working ** This bug has been marked a duplicate of bug 1820794 [Dell Inspiron 3558] PCI/internal sound card not detected -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to pulseaudio in Ubuntu. https://bugs.launchpad.net/bugs/1659219 Title: [Dell Inspiron 3558] Sound not working Status in pulseaudio package in Ubuntu: New Bug description: Description: Ubuntu 14.04.5 LTS Release: 14.04 = DISTRIB_ID=Ubuntu DISTRIB_RELEASE=14.04 DISTRIB_CODENAME=trusty DISTRIB_DESCRIPTION="Ubuntu 14.04.5 LTS" = BackBox Linux 4.7 \n \l I install BackBox Linux OS;Sound not working on my OS I try many things to do but not working. Please help me out ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: pulseaudio 1:4.0-0ubuntu11.1 ProcVersionSignature: Ubuntu 3.19.0-79.87~14.04.1-generic 3.19.8-ckt22 Uname: Linux 3.19.0-79-generic x86_64 ApportVersion: 2.14.1-0ubuntu3.23 Architecture: amd64 AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/by-path', '/dev/snd/hwC1D0', '/dev/snd/pcmC1D0c', '/dev/snd/pcmC1D0p', '/dev/snd/controlC1', '/dev/snd/hwC0D0', '/dev/snd/pcmC0D8p', '/dev/snd/pcmC0D7p', '/dev/snd/pcmC0D3p', '/dev/snd/controlC0', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: CurrentDesktop: XFCE Date: Wed Jan 25 14:39:03 2017 InstallationDate: Installed on 2017-01-24 (0 days ago) InstallationMedia: BackBox Linux 4.4 - Release amd64 PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon. SourcePackage: pulseaudio Symptom: audio UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 05/31/2016 dmi.bios.vendor: Dell Inc. dmi.bios.version: A10 dmi.board.name: 0XCR91 dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 9 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvrA10:bd05/31/2016:svnDellInc.:pnInspiron3558:pvr:rvnDellInc.:rn0XCR91:rvrA00:cvnDellInc.:ct9:cvr: dmi.product.name: Inspiron 3558 dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1659219/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1820794] Re: PCI/internal sound card not detected
According to the attached AlsaInfo.txt the kernel doesn't have a driver compatible with your internal sound card: !!Soundcards recognised by ALSA !!- --- no soundcards --- So this is a kernel bug. Please try a newer version of Ubuntu like 18.04: http://releases.ubuntu.com/18.04 ** Package changed: alsa-driver (Ubuntu) => linux (Ubuntu) ** Summary changed: - PCI/internal sound card not detected + [Dell Inspiron 3558] PCI/internal sound card not detected -- 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/1820794 Title: [Dell Inspiron 3558] PCI/internal sound card not detected Status in linux package in Ubuntu: Confirmed Bug description: SOUND ONLY PLAY VIA BLUETOOTH AND NOT IN EARPHONE OR LAPTOP ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: alsa-base 1.0.25+dfsg-0ubuntu4 ProcVersionSignature: Ubuntu 3.13.0-168.218-generic 3.13.11-ckt39 Uname: Linux 3.13.0-168-generic x86_64 ApportVersion: 2.14.1-0ubuntu3.29 Architecture: amd64 AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: CurrentDesktop: Unity Date: Tue Mar 19 10:08:35 2019 DistributionChannelDescriptor: # This is a distribution channel descriptor # For more information see http://wiki.ubuntu.com/DistributionChannelDescriptor canonical-oem-somerville-trusty-amd64-20140620-0 InstallationDate: Installed on 2015-10-29 (1236 days ago) InstallationMedia: Ubuntu 14.04 "Trusty" - Build amd64 LIVE Binary 20140620-04:25 PackageArchitecture: all SourcePackage: alsa-driver Symptom: audio Title: PCI/internal sound card not detected UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 04/22/2016 dmi.bios.vendor: Dell Inc. dmi.bios.version: A09 dmi.board.name: 0XCR91 dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 9 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvrA09:bd04/22/2016:svnDellInc.:pnInspiron3558:pvr:rvnDellInc.:rn0XCR91:rvrA00:cvnDellInc.:ct9:cvr: dmi.product.name: Inspiron 3558 dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1820794/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1777099] Re: [backport] DRM devices opened by logind stay referenced indefinitely by PID 1
** Changed in: oem-priority Status: Triaged => Fix Released -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to systemd in Ubuntu. https://bugs.launchpad.net/bugs/1777099 Title: [backport] DRM devices opened by logind stay referenced indefinitely by PID 1 Status in OEM Priority Project: Fix Released Status in systemd: Fix Released Status in systemd package in Ubuntu: Fix Released Status in systemd source package in Bionic: Fix Released Bug description: [Impact] * It should be possible to change DRM driver without rebooting. * It should be possible to correctly suspend & resume, whilst preserving driver state. * This bug is for userspace/logind fixes, required to get above working. * Related kernel change is https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1778658 * https://github.com/torvalds/linux/commit/5775b843a619b3c93f946e2b55a208d9f0f48b59 [Test Case] * Test and verify that on machines with Nvidia discrete graphics, one can change performance/power-saving modes without rebooting. [Regression Potential] * There are changes to the fd handling that are passed to logind. At worst, fd to the NVIDIA driver will still be held, and thus one would continue to not be able to switch graphics modes without rebooting. [Other Info] * original bug report: refer to https://github.com/systemd/systemd/issues/6908 we need that solution to make NVIDIA dGPU switching works. impacted issue: https://bugs.launchpad.net/somerville/+bug/1774326 To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/1777099/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1819487] Re: sshd crashed on s390x with hw crypto enabled
** Changed in: ubuntu-z-systems Status: Fix Committed => Fix Released -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to openssh in Ubuntu. https://bugs.launchpad.net/bugs/1819487 Title: sshd crashed on s390x with hw crypto enabled Status in Ubuntu on IBM z Systems: Fix Released Status in openssh package in Ubuntu: Invalid Status in openssl-ibmca package in Ubuntu: Fix Released Bug description: While using today's daily image of disco (either in z/VM or on LPAR) and enabling s309x hardware crypto support in openssh, sshd crashes with the following messages: $ ssh ubuntu@localhost The authenticity of host 'localhost (::1)' can't be established. ECDSA key fingerprint is SHA256:KoTYC0jCQPtmsOMmBW9DrCiBbkrKTL0leQ/zoIaInNw. Are you sure you want to continue connecting (yes/no)? yes Warning: Permanently added 'localhost' (ECDSA) to the list of known hosts. ubuntu@localhost's password: packet_write_wait: Connection to ::1 port 22: Broken pipe (local session is sufficient to reproduce) Steps to reproduce - on disco daily: $ lsb_release -a No LSB modules are available. Distributor ID: Ubuntu Description: Ubuntu Disco Dingo (development branch) Release: 19.04 Codename: disco $ uname -a Linux zlin42 5.0.0-7-generic #8-Ubuntu SMP Mon Mar 4 16:25:21 UTC 2019 s390x s390x s390x GNU/Linux - enable z hw crypto support for openssh on an Ubuntu host (zlin42) on s390x like this: - sudo apt-get install openssl-ibmca libica-utils libica3 - sudo tee -a /etc/ssl/openssl.cnf < /usr/share/doc/openssl-ibmca/examples/openssl.cnf.sample - sudo sed -i 's/^\(openssl_conf = openssl_def.*$\)/# \1/g' /etc/ssl/openssl.cnf - sudo sed -i '10i openssl_conf = openssl_def' /etc/ssl/openssl.cnf - afterwards ssh login attempts fail (existing session are unaffected): $ ssh ubuntu@localhost The authenticity of host 'localhost (::1)' can't be established. ECDSA key fingerprint is SHA256:KoTYC0jCQPtmsOMmBW9DrCiBbkrKTL0leQ/zoIaInNw. Are you sure you want to continue connecting (yes/no)? yes Warning: Permanently added 'localhost' (ECDSA) to the list of known hosts. ubuntu@localhost's password: packet_write_wait: Connection to ::1 port 22: Broken pipe [94629.032586] User process fault: interruption code 003b ilc:2 in libpthread-2.29.so[3ff7d48+1c000] [94629.032597] Failing address: TEID: 0800 [94629.032598] Fault in primary space mode while using user ASCE. [94629.032601] AS:0007450281c7 R3:0024 [94629.032606] CPU: 0 PID: 8183 Comm: sshd Not tainted 5.0.0-7-generic #8-Ubuntu [94629.032607] Hardware name: IBM 2964 N63 400 (LPAR) [94629.032608] User PSW : 070520018000 03ff7d48e954 [94629.032610]R:0 T:1 IO:1 EX:1 Key:0 M:1 W:0 P:1 AS:0 CC:2 PM:0 RI:0 EA:3 [94629.032611] User GPRS: 03ff7e0085c8 [94629.032612]03ff7e510108 03ff7db1c3a8 03fff857eea0 [94629.032613]03ff7e525040 02aa3f5ec090 03ff7e4916f0 03ff7e4921a8 [94629.032614]03ff7db17c18 0002 03ff7e07238a 03fff857ea20 [94629.032622] User Code: 03ff7d48e946: b9040012 lgr %r1,%r2 03ff7d48e94a: e3f0ff60ff71 lay %r15,-160(%r15) #03ff7d48e950: 4700 bc 0,0 >03ff7d48e954: 58202018 l %r2,24(%r2) 03ff7d48e958: b24f00b0 ear %r11,%a0 03ff7d48e95c: ebbb002d sllg %r11,%r11,32 03ff7d48e962: b24f00b1 ear %r11,%a1 03ff7d48e966: 5920b0d0 c %r2,208(%r11) [94629.032634] Last Breaking-Event-Address: [94629.032638] [<03ff7df773b4>] 0x3ff7df773b4 For more details see attachments ... --- ProblemType: Bug ApportVersion: 2.20.10-0ubuntu23 Architecture: s390x DistroRelease: Ubuntu 19.04 Package: openssh-server 1:7.9p1-9 PackageArchitecture: s390x ProcVersionSignature: Ubuntu 5.0.0-7.8-generic 5.0.0 SSHDConfig: Error: command ['/usr/sbin/sshd', '-T'] failed with exit code -11: Tags: disco Uname: Linux 5.0.0-7-generic s390x UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: pkcs11 _MarkForUpload: True To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-z-systems/+bug/1819487/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
