[Touch-packages] [Bug 1812161] Re: Screen backlight control does not work in Disco on Dell XPS 9560
Ah, yes, Kai-Heng Feng probably makes a better point in comment #2. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to upower in Ubuntu. https://bugs.launchpad.net/bugs/1812161 Title: Screen backlight control does not work in Disco on Dell XPS 9560 Status in linux package in Ubuntu: Incomplete Status in upower package in Ubuntu: Incomplete Bug description: When I press the screen backlight up/down buttons, gnome-shell pops up the backlight control window saying that the backlight is being adjusted, but the actual screen brightness does not change. The problem is that gnome is adjusting /sys/class/backlight/acpi_video0/brightness instead of /sys/class/backlight/intel_backlight/brightness. If I manually change the latter as root with, say: root@xps-9560:~ echo 600 > /sys/class/backlight/intel_backlight/brightness then the brightness changes. The brightness control worked fine in Cosmic on this laptop, so this is a regression. ProblemType: Bug DistroRelease: Ubuntu 19.04 Package: xorg 1:7.7+19ubuntu8 ProcVersionSignature: Ubuntu 4.18.0-13.14-generic 4.18.17 Uname: Linux 4.18.0-13-generic x86_64 .tmp.unity_support_test.0: ApportVersion: 2.20.10-0ubuntu18 Architecture: amd64 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Thu Jan 17 14:47:37 2019 DistUpgraded: 2019-01-15 23:10:12,938 DEBUG Running PostInstallScript: './xorg_fix_proprietary.py' DistroCodename: disco DistroVariant: ubuntu DkmsStatus: bbswitch, 0.8, 4.18.0-13-generic, x86_64: installed bbswitch, 0.8, 4.20.0-042000-generic, x86_64: installed bbswitch, 0.8, 4.20.3-042003-generic, x86_64: installed nvidia, 415.27, 4.20.0-042000-generic, x86_64: installed nvidia, 415.27, 4.20.3-042003-generic, x86_64: installed ExtraDebuggingInterest: Yes GraphicsCard: Intel Corporation Device [8086:591b] (rev 04) (prog-if 00 [VGA controller]) Subsystem: Dell Device [1028:07be] Subsystem: Dell GP107M [GeForce GTX 1050 Mobile] [1028:07be] InstallationDate: Installed on 2017-08-16 (518 days ago) InstallationMedia: Ubuntu 17.04 "Zesty Zapus" - Release amd64 (20170412) MachineType: Dell Inc. XPS 15 9560 ProcKernelCmdLine: BOOT_IMAGE=/@/boot/vmlinuz-4.18.0-13-generic root=UUID=0eb64261-6dff-464a-8373-596794c1fafe ro rootflags=subvol=@ quiet splash acpi_rev_override=5 scsi_mod.use_blk_mq=1 i915.modeset=1 nouveau.runpm=0 rcutree.rcu_idle_gp_delay=1 acpi_osi=! "acpi_osi=Windows 2009" SourcePackage: xorg Symptom: display UpgradeStatus: Upgraded to disco on 2019-01-15 (1 days ago) dmi.bios.date: 10/02/2018 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.12.1 dmi.board.name: 05FFDN dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 10 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr1.12.1:bd10/02/2018:svnDellInc.:pnXPS159560:pvr:rvnDellInc.:rn05FFDN:rvrA00:cvnDellInc.:ct10:cvr: dmi.product.family: XPS dmi.product.name: XPS 15 9560 dmi.product.sku: 07BE dmi.sys.vendor: Dell Inc. version.compiz: compiz 1:0.9.13.1+19.04.20190103-0ubuntu1 version.libdrm2: libdrm2 2.4.95-1 version.libgl1-mesa-dri: libgl1-mesa-dri 18.2.8-2ubuntu1 version.libgl1-mesa-glx: libgl1-mesa-glx 18.2.8-2ubuntu1 version.xserver-xorg-core: xserver-xorg-core 2:1.20.3-1ubuntu1 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:18.1.0-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel N/A version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.15-3 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1812161/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1812161] Re: Screen backlight control does not work in Disco on Dell XPS 9560
Please remove all acpi* kernel parameters and see if it helps. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to upower in Ubuntu. https://bugs.launchpad.net/bugs/1812161 Title: Screen backlight control does not work in Disco on Dell XPS 9560 Status in linux package in Ubuntu: Incomplete Status in upower package in Ubuntu: Incomplete Bug description: When I press the screen backlight up/down buttons, gnome-shell pops up the backlight control window saying that the backlight is being adjusted, but the actual screen brightness does not change. The problem is that gnome is adjusting /sys/class/backlight/acpi_video0/brightness instead of /sys/class/backlight/intel_backlight/brightness. If I manually change the latter as root with, say: root@xps-9560:~ echo 600 > /sys/class/backlight/intel_backlight/brightness then the brightness changes. The brightness control worked fine in Cosmic on this laptop, so this is a regression. ProblemType: Bug DistroRelease: Ubuntu 19.04 Package: xorg 1:7.7+19ubuntu8 ProcVersionSignature: Ubuntu 4.18.0-13.14-generic 4.18.17 Uname: Linux 4.18.0-13-generic x86_64 .tmp.unity_support_test.0: ApportVersion: 2.20.10-0ubuntu18 Architecture: amd64 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Thu Jan 17 14:47:37 2019 DistUpgraded: 2019-01-15 23:10:12,938 DEBUG Running PostInstallScript: './xorg_fix_proprietary.py' DistroCodename: disco DistroVariant: ubuntu DkmsStatus: bbswitch, 0.8, 4.18.0-13-generic, x86_64: installed bbswitch, 0.8, 4.20.0-042000-generic, x86_64: installed bbswitch, 0.8, 4.20.3-042003-generic, x86_64: installed nvidia, 415.27, 4.20.0-042000-generic, x86_64: installed nvidia, 415.27, 4.20.3-042003-generic, x86_64: installed ExtraDebuggingInterest: Yes GraphicsCard: Intel Corporation Device [8086:591b] (rev 04) (prog-if 00 [VGA controller]) Subsystem: Dell Device [1028:07be] Subsystem: Dell GP107M [GeForce GTX 1050 Mobile] [1028:07be] InstallationDate: Installed on 2017-08-16 (518 days ago) InstallationMedia: Ubuntu 17.04 "Zesty Zapus" - Release amd64 (20170412) MachineType: Dell Inc. XPS 15 9560 ProcKernelCmdLine: BOOT_IMAGE=/@/boot/vmlinuz-4.18.0-13-generic root=UUID=0eb64261-6dff-464a-8373-596794c1fafe ro rootflags=subvol=@ quiet splash acpi_rev_override=5 scsi_mod.use_blk_mq=1 i915.modeset=1 nouveau.runpm=0 rcutree.rcu_idle_gp_delay=1 acpi_osi=! "acpi_osi=Windows 2009" SourcePackage: xorg Symptom: display UpgradeStatus: Upgraded to disco on 2019-01-15 (1 days ago) dmi.bios.date: 10/02/2018 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.12.1 dmi.board.name: 05FFDN dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 10 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr1.12.1:bd10/02/2018:svnDellInc.:pnXPS159560:pvr:rvnDellInc.:rn05FFDN:rvrA00:cvnDellInc.:ct10:cvr: dmi.product.family: XPS dmi.product.name: XPS 15 9560 dmi.product.sku: 07BE dmi.sys.vendor: Dell Inc. version.compiz: compiz 1:0.9.13.1+19.04.20190103-0ubuntu1 version.libdrm2: libdrm2 2.4.95-1 version.libgl1-mesa-dri: libgl1-mesa-dri 18.2.8-2ubuntu1 version.libgl1-mesa-glx: libgl1-mesa-glx 18.2.8-2ubuntu1 version.xserver-xorg-core: xserver-xorg-core 2:1.20.3-1ubuntu1 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:18.1.0-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel N/A version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.15-3 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1812161/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1812161] Re: Screen backlight control does not work in Disco on Dell XPS 9560
Rocko, You seem to have some newer kernels installed. Does booting those have the same problem? Also, maybe you can try downgrading to cosmic's upower version: https://launchpad.net/ubuntu/+source/upower/0.99.8-2ubuntu0.1 to see if it was a regression in upower. ** Changed in: linux (Ubuntu) Status: New => Incomplete ** Changed in: upower (Ubuntu) Status: New => Incomplete -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to upower in Ubuntu. https://bugs.launchpad.net/bugs/1812161 Title: Screen backlight control does not work in Disco on Dell XPS 9560 Status in linux package in Ubuntu: Incomplete Status in upower package in Ubuntu: Incomplete Bug description: When I press the screen backlight up/down buttons, gnome-shell pops up the backlight control window saying that the backlight is being adjusted, but the actual screen brightness does not change. The problem is that gnome is adjusting /sys/class/backlight/acpi_video0/brightness instead of /sys/class/backlight/intel_backlight/brightness. If I manually change the latter as root with, say: root@xps-9560:~ echo 600 > /sys/class/backlight/intel_backlight/brightness then the brightness changes. The brightness control worked fine in Cosmic on this laptop, so this is a regression. ProblemType: Bug DistroRelease: Ubuntu 19.04 Package: xorg 1:7.7+19ubuntu8 ProcVersionSignature: Ubuntu 4.18.0-13.14-generic 4.18.17 Uname: Linux 4.18.0-13-generic x86_64 .tmp.unity_support_test.0: ApportVersion: 2.20.10-0ubuntu18 Architecture: amd64 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Thu Jan 17 14:47:37 2019 DistUpgraded: 2019-01-15 23:10:12,938 DEBUG Running PostInstallScript: './xorg_fix_proprietary.py' DistroCodename: disco DistroVariant: ubuntu DkmsStatus: bbswitch, 0.8, 4.18.0-13-generic, x86_64: installed bbswitch, 0.8, 4.20.0-042000-generic, x86_64: installed bbswitch, 0.8, 4.20.3-042003-generic, x86_64: installed nvidia, 415.27, 4.20.0-042000-generic, x86_64: installed nvidia, 415.27, 4.20.3-042003-generic, x86_64: installed ExtraDebuggingInterest: Yes GraphicsCard: Intel Corporation Device [8086:591b] (rev 04) (prog-if 00 [VGA controller]) Subsystem: Dell Device [1028:07be] Subsystem: Dell GP107M [GeForce GTX 1050 Mobile] [1028:07be] InstallationDate: Installed on 2017-08-16 (518 days ago) InstallationMedia: Ubuntu 17.04 "Zesty Zapus" - Release amd64 (20170412) MachineType: Dell Inc. XPS 15 9560 ProcKernelCmdLine: BOOT_IMAGE=/@/boot/vmlinuz-4.18.0-13-generic root=UUID=0eb64261-6dff-464a-8373-596794c1fafe ro rootflags=subvol=@ quiet splash acpi_rev_override=5 scsi_mod.use_blk_mq=1 i915.modeset=1 nouveau.runpm=0 rcutree.rcu_idle_gp_delay=1 acpi_osi=! "acpi_osi=Windows 2009" SourcePackage: xorg Symptom: display UpgradeStatus: Upgraded to disco on 2019-01-15 (1 days ago) dmi.bios.date: 10/02/2018 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.12.1 dmi.board.name: 05FFDN dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 10 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr1.12.1:bd10/02/2018:svnDellInc.:pnXPS159560:pvr:rvnDellInc.:rn05FFDN:rvrA00:cvnDellInc.:ct10:cvr: dmi.product.family: XPS dmi.product.name: XPS 15 9560 dmi.product.sku: 07BE dmi.sys.vendor: Dell Inc. version.compiz: compiz 1:0.9.13.1+19.04.20190103-0ubuntu1 version.libdrm2: libdrm2 2.4.95-1 version.libgl1-mesa-dri: libgl1-mesa-dri 18.2.8-2ubuntu1 version.libgl1-mesa-glx: libgl1-mesa-glx 18.2.8-2ubuntu1 version.xserver-xorg-core: xserver-xorg-core 2:1.20.3-1ubuntu1 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:18.1.0-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel N/A version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.15-3 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1812161/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1812161] Re: Screen backlight control does not work in Disco on Dell XPS 9560
** Package changed: xorg (Ubuntu) => linux (Ubuntu) ** Also affects: upower (Ubuntu) Importance: Undecided Status: New -- 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/1812161 Title: Screen backlight control does not work in Disco on Dell XPS 9560 Status in linux package in Ubuntu: Incomplete Status in upower package in Ubuntu: Incomplete Bug description: When I press the screen backlight up/down buttons, gnome-shell pops up the backlight control window saying that the backlight is being adjusted, but the actual screen brightness does not change. The problem is that gnome is adjusting /sys/class/backlight/acpi_video0/brightness instead of /sys/class/backlight/intel_backlight/brightness. If I manually change the latter as root with, say: root@xps-9560:~ echo 600 > /sys/class/backlight/intel_backlight/brightness then the brightness changes. The brightness control worked fine in Cosmic on this laptop, so this is a regression. ProblemType: Bug DistroRelease: Ubuntu 19.04 Package: xorg 1:7.7+19ubuntu8 ProcVersionSignature: Ubuntu 4.18.0-13.14-generic 4.18.17 Uname: Linux 4.18.0-13-generic x86_64 .tmp.unity_support_test.0: ApportVersion: 2.20.10-0ubuntu18 Architecture: amd64 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Thu Jan 17 14:47:37 2019 DistUpgraded: 2019-01-15 23:10:12,938 DEBUG Running PostInstallScript: './xorg_fix_proprietary.py' DistroCodename: disco DistroVariant: ubuntu DkmsStatus: bbswitch, 0.8, 4.18.0-13-generic, x86_64: installed bbswitch, 0.8, 4.20.0-042000-generic, x86_64: installed bbswitch, 0.8, 4.20.3-042003-generic, x86_64: installed nvidia, 415.27, 4.20.0-042000-generic, x86_64: installed nvidia, 415.27, 4.20.3-042003-generic, x86_64: installed ExtraDebuggingInterest: Yes GraphicsCard: Intel Corporation Device [8086:591b] (rev 04) (prog-if 00 [VGA controller]) Subsystem: Dell Device [1028:07be] Subsystem: Dell GP107M [GeForce GTX 1050 Mobile] [1028:07be] InstallationDate: Installed on 2017-08-16 (518 days ago) InstallationMedia: Ubuntu 17.04 "Zesty Zapus" - Release amd64 (20170412) MachineType: Dell Inc. XPS 15 9560 ProcKernelCmdLine: BOOT_IMAGE=/@/boot/vmlinuz-4.18.0-13-generic root=UUID=0eb64261-6dff-464a-8373-596794c1fafe ro rootflags=subvol=@ quiet splash acpi_rev_override=5 scsi_mod.use_blk_mq=1 i915.modeset=1 nouveau.runpm=0 rcutree.rcu_idle_gp_delay=1 acpi_osi=! "acpi_osi=Windows 2009" SourcePackage: xorg Symptom: display UpgradeStatus: Upgraded to disco on 2019-01-15 (1 days ago) dmi.bios.date: 10/02/2018 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.12.1 dmi.board.name: 05FFDN dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 10 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr1.12.1:bd10/02/2018:svnDellInc.:pnXPS159560:pvr:rvnDellInc.:rn05FFDN:rvrA00:cvnDellInc.:ct10:cvr: dmi.product.family: XPS dmi.product.name: XPS 15 9560 dmi.product.sku: 07BE dmi.sys.vendor: Dell Inc. version.compiz: compiz 1:0.9.13.1+19.04.20190103-0ubuntu1 version.libdrm2: libdrm2 2.4.95-1 version.libgl1-mesa-dri: libgl1-mesa-dri 18.2.8-2ubuntu1 version.libgl1-mesa-glx: libgl1-mesa-glx 18.2.8-2ubuntu1 version.xserver-xorg-core: xserver-xorg-core 2:1.20.3-1ubuntu1 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:18.1.0-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel N/A version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.15-3 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1812161/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1812161] [NEW] Screen backlight control does not work in Disco on Dell XPS 9560
Public bug reported: When I press the screen backlight up/down buttons, gnome-shell pops up the backlight control window saying that the backlight is being adjusted, but the actual screen brightness does not change. The problem is that gnome is adjusting /sys/class/backlight/acpi_video0/brightness instead of /sys/class/backlight/intel_backlight/brightness. If I manually change the latter as root with, say: root@xps-9560:~ echo 600 > /sys/class/backlight/intel_backlight/brightness then the brightness changes. The brightness control worked fine in Cosmic on this laptop, so this is a regression. ProblemType: Bug DistroRelease: Ubuntu 19.04 Package: xorg 1:7.7+19ubuntu8 ProcVersionSignature: Ubuntu 4.18.0-13.14-generic 4.18.17 Uname: Linux 4.18.0-13-generic x86_64 .tmp.unity_support_test.0: ApportVersion: 2.20.10-0ubuntu18 Architecture: amd64 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Thu Jan 17 14:47:37 2019 DistUpgraded: 2019-01-15 23:10:12,938 DEBUG Running PostInstallScript: './xorg_fix_proprietary.py' DistroCodename: disco DistroVariant: ubuntu DkmsStatus: bbswitch, 0.8, 4.18.0-13-generic, x86_64: installed bbswitch, 0.8, 4.20.0-042000-generic, x86_64: installed bbswitch, 0.8, 4.20.3-042003-generic, x86_64: installed nvidia, 415.27, 4.20.0-042000-generic, x86_64: installed nvidia, 415.27, 4.20.3-042003-generic, x86_64: installed ExtraDebuggingInterest: Yes GraphicsCard: Intel Corporation Device [8086:591b] (rev 04) (prog-if 00 [VGA controller]) Subsystem: Dell Device [1028:07be] Subsystem: Dell GP107M [GeForce GTX 1050 Mobile] [1028:07be] InstallationDate: Installed on 2017-08-16 (518 days ago) InstallationMedia: Ubuntu 17.04 "Zesty Zapus" - Release amd64 (20170412) MachineType: Dell Inc. XPS 15 9560 ProcKernelCmdLine: BOOT_IMAGE=/@/boot/vmlinuz-4.18.0-13-generic root=UUID=0eb64261-6dff-464a-8373-596794c1fafe ro rootflags=subvol=@ quiet splash acpi_rev_override=5 scsi_mod.use_blk_mq=1 i915.modeset=1 nouveau.runpm=0 rcutree.rcu_idle_gp_delay=1 acpi_osi=! "acpi_osi=Windows 2009" SourcePackage: xorg Symptom: display UpgradeStatus: Upgraded to disco on 2019-01-15 (1 days ago) dmi.bios.date: 10/02/2018 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.12.1 dmi.board.name: 05FFDN dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 10 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr1.12.1:bd10/02/2018:svnDellInc.:pnXPS159560:pvr:rvnDellInc.:rn05FFDN:rvrA00:cvnDellInc.:ct10:cvr: dmi.product.family: XPS dmi.product.name: XPS 15 9560 dmi.product.sku: 07BE dmi.sys.vendor: Dell Inc. version.compiz: compiz 1:0.9.13.1+19.04.20190103-0ubuntu1 version.libdrm2: libdrm2 2.4.95-1 version.libgl1-mesa-dri: libgl1-mesa-dri 18.2.8-2ubuntu1 version.libgl1-mesa-glx: libgl1-mesa-glx 18.2.8-2ubuntu1 version.xserver-xorg-core: xserver-xorg-core 2:1.20.3-1ubuntu1 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:18.1.0-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel N/A version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.15-3 ** Affects: xorg (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug disco gnome-shell regression reproducible third-party-packages ubuntu ** Tags added: gnome-shell -- 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/1812161 Title: Screen backlight control does not work in Disco on Dell XPS 9560 Status in xorg package in Ubuntu: New Bug description: When I press the screen backlight up/down buttons, gnome-shell pops up the backlight control window saying that the backlight is being adjusted, but the actual screen brightness does not change. The problem is that gnome is adjusting /sys/class/backlight/acpi_video0/brightness instead of /sys/class/backlight/intel_backlight/brightness. If I manually change the latter as root with, say: root@xps-9560:~ echo 600 > /sys/class/backlight/intel_backlight/brightness then the brightness changes. The brightness control worked fine in Cosmic on this laptop, so this is a regression. ProblemType: Bug DistroRelease: Ubuntu 19.04 Package: xorg 1:7.7+19ubuntu8 ProcVersionSignature: Ubuntu 4.18.0-13.14-generic 4.18.17 Uname: Linux 4.18.0-13-generic x86_64 .tmp.unity_support_test.0: ApportVersion: 2.20.10-0ubuntu18 Architecture: amd64 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Thu Jan 17 14:47:37 2019 DistUpgraded: 2019-01-15 23:10:12,938 DEBUG Running PostInstallScript: './xorg_fix_proprietary.py' DistroCodename: disco DistroVariant: ubuntu DkmsStatus: bbswitch, 0.8, 4.18.0-13-generic, x86_64: instal
[Touch-packages] [Bug 1725455] Re: Login screen invisible / UI hanging when both 4K monitors connected via Displayport MST (docking station)
Thank you for reporting this bug to Ubuntu. Ubuntu 17.10 (artful) reached end-of-life on July 19, 2018. See this document for currently supported Ubuntu releases: https://wiki.ubuntu.com/Releases We appreciate that this bug may be old and you might not be interested in discussing it any more. But if you are then please upgrade to the latest Ubuntu version and re-test. If you then find the bug is still present in the newer Ubuntu version, please add a comment here telling us which new version it is in and change the bug status to Confirmed. ** Package changed: xorg (Ubuntu) => gnome-shell (Ubuntu) ** Changed in: gnome-shell (Ubuntu) Status: New => Won't Fix -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to xorg in Ubuntu. https://bugs.launchpad.net/bugs/1725455 Title: Login screen invisible / UI hanging when both 4K monitors connected via Displayport MST (docking station) Status in gnome-shell package in Ubuntu: Won't Fix Bug description: I am experiencing serious issues after upgrading to Ubuntu 17.10 (coming from 17.04 with Gnome, kernel 4.13). I have 2 x 4K (Asus PB279Q) monitors, connected to a Lenovo Ultra Dock (containing 2 x Displayport via MST), where the Lenovo T550 is connected onto it. Both monitors were working perfectly fine at 30Hz simultaneously in an extended desktop, 4K resolution in my old setup with Gnome for over half a year (since kernel 4.10 blink issues on 4K were solved, i used this setup since then). However after upgrading to 17.10 using the new Gnome interface: When the laptop is connected to the Lenovo Ultra Dock (to work on both monitors), the system is hanging and becoming unresponsive. The mouse pointer is freezing and the only way is to do a hard-reboot. I have checked the monitor settings, it's displayed at 60Hz when active, and it appears I am never able to use both monitors simultaneously. When I get 1 monitor working (disconnecting the 2nd monitor from the MST port), after rebooting it works fine. I tried to put settings of the 4K manually on 30Hz, reconnecting, but the system hangs again. I have tried several combinations. It results in a blank (purple) screen and hanging mouse (see attachment). I tried also with the installation-iso to run a fresh 17.10 and tried the same, the symptoms are similar. I suspect that must be an issue with the Displayport MST on dual 4K setups in the new 17.10. When I connect 1 x 4K monitor to the rear displayport of the Lenovo Ultra Dock (there are 2 for MST on the rear, so I disconnected the other) *and* when I connect the other 4K monitor on the separate displayport of the T550 itself instead, it works 100% fine! Shortly: based on my knowledge that must definitely be some issue with the MST displayport functionality itself, that is unable to recognize/identify both 4K monitors when connected to the dock's both displayport connections? ProblemType: Bug DistroRelease: Ubuntu 17.10 Package: xorg 1:7.7+19ubuntu3 Uname: Linux 4.13.4-041304-generic x86_64 .tmp.unity_support_test.0: ApportVersion: 2.20.7-0ubuntu3 Architecture: amd64 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Fri Oct 20 21:10:50 2017 DistUpgraded: 2017-10-19 21:54:53,162 DEBUG icon theme changed, re-reading DistroCodename: artful DistroVariant: ubuntu ExtraDebuggingInterest: I just need to know a workaround GraphicsCard: Intel Corporation HD Graphics 5500 [8086:1616] (rev 09) (prog-if 00 [VGA controller]) Subsystem: Lenovo HD Graphics 5500 [17aa:2225] Subsystem: Lenovo GM108M [GeForce 940M] [17aa:2225] InstallationDate: Installed on 2017-04-16 (186 days ago) InstallationMedia: Ubuntu 17.04 "Zesty Zapus" - Release amd64 (20170412) MachineType: LENOVO 20CKCTO1WW ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.13.4-041304-generic root=UUID=9fcc7f4c-35c0-4297-9c98-4dac9acee798 ro quiet splash vt.handoff=7 SourcePackage: xorg Symptom: display UpgradeStatus: Upgraded to artful on 2017-10-19 (0 days ago) dmi.bios.date: 09/13/2017 dmi.bios.vendor: LENOVO dmi.bios.version: N11ET42W (1.18 ) dmi.board.asset.tag: Not Available dmi.board.name: 20CKCTO1WW dmi.board.vendor: LENOVO dmi.board.version: SDK0E50512 STD dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: None dmi.modalias: dmi:bvnLENOVO:bvrN11ET42W(1.18):bd09/13/2017:svnLENOVO:pn20CKCTO1WW:pvrThinkPadT550:rvnLENOVO:rn20CKCTO1WW:rvrSDK0E50512STD:cvnLENOVO:ct10:cvrNone: dmi.product.family: ThinkPad T550 dmi.product.name: 20CKCTO1WW dmi.product.version: ThinkPad T550 dmi.sys.vendor: LENOVO version.compiz: compiz 1:0.9.13.1+17.10.20170901-0ubuntu1 version.libdrm2: libdrm2 2.4.83-1 version.libgl1-mesa-dri: libgl1-mesa-dr
[Touch-packages] [Bug 1726682] Re: Xorg freeze
Thank you for reporting this bug to Ubuntu. Ubuntu 17.10 (artful) reached end-of-life on July 19, 2018. See this document for currently supported Ubuntu releases: https://wiki.ubuntu.com/Releases We appreciate that this bug may be old and you might not be interested in discussing it any more. But if you are then please upgrade to the latest Ubuntu version and re-test. If you then find the bug is still present in the newer Ubuntu version, please add a comment here telling us which new version it is in and change the bug status to Confirmed. ** Package changed: xorg (Ubuntu) => xorg-server (Ubuntu) ** Changed in: xorg-server (Ubuntu) Status: New => Won't Fix -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to xorg in Ubuntu. https://bugs.launchpad.net/bugs/1726682 Title: Xorg freeze Status in xorg-server package in Ubuntu: Won't Fix Bug description: This problem occur: - when I input USB stick - When I have click about system (more details of Ubuntu) - Using normally, so open a video then system log off or freeze. I try Ctrl + Shft + F1 or Ctrl + Shift + F2 but it goes to the GDM login screen. ProblemType: Bug DistroRelease: Ubuntu 17.10 Package: xorg 1:7.7+19ubuntu3 ProcVersionSignature: Ubuntu 4.13.0-16.19-generic 4.13.4 Uname: Linux 4.13.0-16-generic x86_64 ApportVersion: 2.20.7-0ubuntu3 Architecture: amd64 BootLog: CompositorRunning: None CurrentDesktop: GNOME Date: Tue Oct 24 00:44:02 2017 DistUpgraded: Fresh install DistroCodename: artful DistroVariant: ubuntu ExtraDebuggingInterest: Yes, if not too technical GpuHangFrequency: Several times a day GpuHangReproducibility: Occurs more often under certain circumstances GpuHangStarted: Immediately after installing this version of Ubuntu GraphicsCard: Intel Corporation HD Graphics 5500 [8086:1616] (rev 09) (prog-if 00 [VGA controller]) Subsystem: Samsung Electronics Co Ltd HD Graphics 5500 [144d:c755] InstallationDate: Installed on 2017-10-19 (4 days ago) InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20171018) MachineType: SAMSUNG ELECTRONICS CO., LTD. 370E4K ProcKernelCmdLine: BOOT_IMAGE=/@/boot/vmlinuz-4.13.0-16-generic.efi.signed root=UUID=b04e4fad-4a52-4169-9ba3-0786c9a0ab39 ro rootflags=subvol=@ quiet splash vt.handoff=7 SourcePackage: xorg Symptom: display Title: Xorg freeze UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 03/11/2016 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: P06RCX.075.160311.JJ dmi.board.asset.tag: No Asset Tag dmi.board.name: NP370E4K-KW3BR dmi.board.vendor: SAMSUNG ELECTRONICS CO., LTD. dmi.board.version: SGL8537A0C-C01-G001-S0001+10.0.10240 dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 9 dmi.chassis.vendor: SAMSUNG ELECTRONICS CO., LTD. dmi.chassis.version: N/A dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrP06RCX.075.160311.JJ:bd03/11/2016:svnSAMSUNGELECTRONICSCO.,LTD.:pn370E4K:pvrP06RCX:rvnSAMSUNGELECTRONICSCO.,LTD.:rnNP370E4K-KW3BR:rvrSGL8537A0C-C01-G001-S0001+10.0.10240:cvnSAMSUNGELECTRONICSCO.,LTD.:ct9:cvrN/A: dmi.product.family: SAMSUNG ATIV dmi.product.name: 370E4K dmi.product.version: P06RCX dmi.sys.vendor: SAMSUNG ELECTRONICS CO., LTD. version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.83-1 version.libgl1-mesa-dri: libgl1-mesa-dri 17.2.2-0ubuntu1 version.libgl1-mesa-glx: libgl1-mesa-glx 17.2.2-0ubuntu1 version.xserver-xorg-core: xserver-xorg-core 2:1.19.5-0ubuntu2 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.10.0-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20170309-0ubuntu1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.15-2 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg-server/+bug/1726682/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1725295] Re: intel graphics G41 not loaded - ubuntu 17.10
Thank you for reporting this bug to Ubuntu. Ubuntu 17.10 (artful) reached end-of-life on July 19, 2018. See this document for currently supported Ubuntu releases: https://wiki.ubuntu.com/Releases We appreciate that this bug may be old and you might not be interested in discussing it any more. But if you are then please upgrade to the latest Ubuntu version and re-test. If you then find the bug is still present in the newer Ubuntu version, please add a comment here telling us which new version it is in and change the bug status to Confirmed. ** Package changed: xorg (Ubuntu) => ubuntu ** Changed in: ubuntu Status: New => Won't Fix -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to xorg in Ubuntu. https://bugs.launchpad.net/bugs/1725295 Title: intel graphics G41 not loaded - ubuntu 17.10 Status in Ubuntu: Won't Fix Bug description: i installed Ubuntu 17.10...although live cd recognized my intel Graphics g41...after i install system on my pc hard disk...the g41 is not recgnized at all leading to very slow and laggy system. ProblemType: Bug DistroRelease: Ubuntu 17.10 Package: xorg 1:7.7+19ubuntu3 ProcVersionSignature: Ubuntu 4.13.0-16.19-generic 4.13.4 Uname: Linux 4.13.0-16-generic x86_64 ApportVersion: 2.20.7-0ubuntu3 Architecture: amd64 CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Fri Oct 20 16:44:45 2017 DistUpgraded: Fresh install DistroCodename: artful DistroVariant: ubuntu ExtraDebuggingInterest: I just need to know a workaround GraphicsCard: Intel Corporation 4 Series Chipset Integrated Graphics Controller [8086:2e32] (rev 03) (prog-if 00 [VGA controller]) Subsystem: Gigabyte Technology Co., Ltd 4 Series Chipset Integrated Graphics Controller [1458:d000] InstallationDate: Installed on 2017-10-20 (0 days ago) InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20171018) MachineType: Gigabyte Technology Co., Ltd. G41M-ES2L ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.13.0-16-generic root=UUID=9567769a-462e-45a3-ba49-c4a12bf24b16 ro quiet splash vt.handoff=7 SourcePackage: xorg UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 11/04/2009 dmi.bios.vendor: Award Software International, Inc. dmi.bios.version: F6 dmi.board.name: G41M-ES2L dmi.board.vendor: Gigabyte Technology Co., Ltd. dmi.chassis.type: 3 dmi.chassis.vendor: Gigabyte Technology Co., Ltd. dmi.modalias: dmi:bvnAwardSoftwareInternational,Inc.:bvrF6:bd11/04/2009:svnGigabyteTechnologyCo.,Ltd.:pnG41M-ES2L:pvr:rvnGigabyteTechnologyCo.,Ltd.:rnG41M-ES2L:rvr:cvnGigabyteTechnologyCo.,Ltd.:ct3:cvr: dmi.product.name: G41M-ES2L dmi.sys.vendor: Gigabyte Technology Co., Ltd. version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.83-1 version.libgl1-mesa-dri: libgl1-mesa-dri 17.2.2-0ubuntu1 version.libgl1-mesa-glx: libgl1-mesa-glx 17.2.2-0ubuntu1 version.xserver-xorg-core: xserver-xorg-core 2:1.19.5-0ubuntu2 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.10.0-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20170309-0ubuntu1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.15-2 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+bug/1725295/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1725169] Re: Black Screen after Upgrade from Kubuntu 17.04 to 17.10
Thank you for reporting this bug to Ubuntu. Ubuntu 17.10 (artful) reached end-of-life on July 19, 2018. See this document for currently supported Ubuntu releases: https://wiki.ubuntu.com/Releases We appreciate that this bug may be old and you might not be interested in discussing it any more. But if you are then please upgrade to the latest Ubuntu version and re-test. If you then find the bug is still present in the newer Ubuntu version, please add a comment here telling us which new version it is in and change the bug status to Confirmed. ** Package changed: xorg (Ubuntu) => ubuntu ** Changed in: ubuntu Status: Confirmed => Won't Fix -- 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/1725169 Title: Black Screen after Upgrade from Kubuntu 17.04 to 17.10 Status in Ubuntu: Won't Fix Bug description: I just upgraded Kubuntu from 17.04 to 17.10 on two machines with the same Result: After reboot, the first kernel in grub was 'linux-image-4.13.0-16-lowlatency'. This kernel does not work with the nvidia-grafic-card and lead to a black screen. After purging this kernel in a tty-session it booted up smothely. I think this can help many others. ProblemType: Bug DistroRelease: Ubuntu 17.10 Package: xorg 1:7.7+19ubuntu3 ProcVersionSignature: Ubuntu 4.13.0-16.19-generic 4.13.4 Uname: Linux 4.13.0-16-generic x86_64 NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia .proc.driver.nvidia.gpus..01.00.0: Error: [Errno 21] Ist ein Verzeichnis: '/proc/driver/nvidia/gpus/:01:00.0' .proc.driver.nvidia.registry: Binary: "" .proc.driver.nvidia.version: NVRM version: NVIDIA UNIX x86_64 Kernel Module 384.90 Tue Sep 19 19:17:35 PDT 2017 GCC version: gcc version 7.2.0 (Ubuntu 7.2.0-8ubuntu3) .proc.driver.nvidia.warnings.fbdev: Your system is not currently configured to drive a VGA console on the primary VGA device. The NVIDIA Linux graphics driver requires the use of a text-mode VGA console. Use of other console drivers including, but not limited to, vesafb, may result in corruption and stability problems, and is not supported. ApportVersion: 2.20.7-0ubuntu3 Architecture: amd64 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: None CurrentDesktop: KDE Date: Fri Oct 20 09:57:26 2017 DistUpgraded: 2017-10-20 08:57:01,633 DEBUG Running PostInstallScript: './xorg_fix_proprietary.py' DistroCodename: artful DistroVariant: kubuntu DkmsStatus: bbswitch, 0.8, 4.13.0-16-generic, x86_64: installed nvidia-384, 384.90, 4.13.0-16-generic, x86_64: installed ExtraDebuggingInterest: No GraphicsCard: NVIDIA Corporation GM107 [GeForce GTX 750 Ti] [10de:1380] (rev a2) (prog-if 00 [VGA controller]) Subsystem: Gigabyte Technology Co., Ltd GM107 [GeForce GTX 750 Ti] [1458:362d] InstallationDate: Installed on 2016-12-23 (300 days ago) InstallationMedia: Kubuntu 16.10 "Yakkety Yak" - Release amd64 (20161012.1) Lsusb: Bus 004 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 003 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 002: ID 062a:4102 Creative Labs Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: Gigabyte Technology Co., Ltd. Z170X-Gaming 3 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.13.0-16-generic root=UUID=99e6e2ce-07c5-4553-be22-2ccd3c3a73cc ro quiet splash vt.handoff=7 SourcePackage: xorg Symptom: display UpgradeStatus: Upgraded to artful on 2017-10-20 (0 days ago) dmi.bios.date: 06/30/2017 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: F22d dmi.board.asset.tag: Default string dmi.board.name: Z170X-Gaming 3 dmi.board.vendor: Gigabyte Technology Co., Ltd. dmi.board.version: x.x dmi.chassis.asset.tag: Default string dmi.chassis.type: 3 dmi.chassis.vendor: Default string dmi.chassis.version: Default string dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrF22d:bd06/30/2017:svnGigabyteTechnologyCo.,Ltd.:pnZ170X-Gaming3:pvrDefaultstring:rvnGigabyteTechnologyCo.,Ltd.:rnZ170X-Gaming3:rvrx.x:cvnDefaultstring:ct3:cvrDefaultstring: dmi.product.family: Default string dmi.product.name: Z170X-Gaming 3 dmi.product.version: Default string dmi.sys.vendor: Gigabyte Technology Co., Ltd. version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.83-1 version.libgl1-mesa-dri: libgl1-mesa-dri 17.2.2-0ubuntu1 version.libgl1-mesa-glx: libgl1-mesa-glx 17.2.2-0ubuntu1 version.nvidia-graphics-drivers: nvidia-graphics-drivers-* N/A version.xserver-xorg-core: xserver-xorg-core 2:1.19.5-0ubuntu2 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.10.5-1ubuntu1 version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.10.0-1 version.xser
[Touch-packages] [Bug 1725785] Re: video card not recognized after install on my PC.-ubuntu 17.10
Thank you for reporting this bug to Ubuntu. Ubuntu 17.10 (artful) reached end-of-life on July 19, 2018. See this document for currently supported Ubuntu releases: https://wiki.ubuntu.com/Releases We appreciate that this bug may be old and you might not be interested in discussing it any more. But if you are then please upgrade to the latest Ubuntu version and re-test. If you then find the bug is still present in the newer Ubuntu version, please add a comment here telling us which new version it is in and change the bug status to Confirmed. ** Package changed: xorg (Ubuntu) => ubuntu ** Changed in: ubuntu Status: New => Won't Fix -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to xorg in Ubuntu. https://bugs.launchpad.net/bugs/1725785 Title: video card not recognized after install on my PC.-ubuntu 17.10 Status in Ubuntu: Won't Fix Bug description: I have Intel G41 video card...which is recognized by all previous versions of Ubuntu,,but not recognized by Ubuntu 17.10...though the live CD version recognize it normally.it appear in system setting/about as unknown...this leads to very slow and laggy system. ProblemType: Bug DistroRelease: Ubuntu 17.10 Package: xorg 1:7.7+19ubuntu3 ProcVersionSignature: Ubuntu 4.13.0-16.19-generic 4.13.4 Uname: Linux 4.13.0-16-generic x86_64 .tmp.unity_support_test.0: ApportVersion: 2.20.7-0ubuntu3 Architecture: amd64 CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Sat Oct 21 21:17:26 2017 DistUpgraded: 2017-10-21 15:55:23,430 DEBUG icon theme changed, re-reading DistroCodename: artful DistroVariant: ubuntu GraphicsCard: Intel Corporation 4 Series Chipset Integrated Graphics Controller [8086:2e32] (rev 03) (prog-if 00 [VGA controller]) Subsystem: Gigabyte Technology Co., Ltd 4 Series Chipset Integrated Graphics Controller [1458:d000] InstallationDate: Installed on 2017-10-21 (0 days ago) InstallationMedia: Ubuntu 17.04 "Zesty Zapus" - Release amd64 (20170412) MachineType: Gigabyte Technology Co., Ltd. G41M-ES2L ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.13.0-16-generic root=UUID=70de525a-6d7f-41e7-b119-16941407f3bf ro quiet splash vt.handoff=7 SourcePackage: xorg Symptom: display UpgradeStatus: Upgraded to artful on 2017-10-21 (0 days ago) dmi.bios.date: 11/04/2009 dmi.bios.vendor: Award Software International, Inc. dmi.bios.version: F6 dmi.board.name: G41M-ES2L dmi.board.vendor: Gigabyte Technology Co., Ltd. dmi.chassis.type: 3 dmi.chassis.vendor: Gigabyte Technology Co., Ltd. dmi.modalias: dmi:bvnAwardSoftwareInternational,Inc.:bvrF6:bd11/04/2009:svnGigabyteTechnologyCo.,Ltd.:pnG41M-ES2L:pvr:rvnGigabyteTechnologyCo.,Ltd.:rnG41M-ES2L:rvr:cvnGigabyteTechnologyCo.,Ltd.:ct3:cvr: dmi.product.name: G41M-ES2L dmi.sys.vendor: Gigabyte Technology Co., Ltd. version.compiz: compiz 1:0.9.13.1+17.10.20170901-0ubuntu1 version.libdrm2: libdrm2 2.4.83-1 version.libgl1-mesa-dri: libgl1-mesa-dri 17.2.2-0ubuntu1 version.libgl1-mesa-glx: libgl1-mesa-glx 17.2.2-0ubuntu1 version.xserver-xorg-core: xserver-xorg-core 2:1.19.5-0ubuntu2 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.10.0-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20170309-0ubuntu1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.15-2 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+bug/1725785/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1724979] Re: system freeze when activating my 3rd display
Thank you for reporting this bug to Ubuntu. Ubuntu 17.10 (artful) reached end-of-life on July 19, 2018. See this document for currently supported Ubuntu releases: https://wiki.ubuntu.com/Releases We appreciate that this bug may be old and you might not be interested in discussing it any more. But if you are then please upgrade to the latest Ubuntu version and re-test. If you then find the bug is still present in the newer Ubuntu version, please add a comment here telling us which new version it is in and change the bug status to Confirmed. ** Package changed: xorg (Ubuntu) => xorg-server (Ubuntu) ** Changed in: xorg-server (Ubuntu) Status: New => Won't Fix -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to xorg in Ubuntu. https://bugs.launchpad.net/bugs/1724979 Title: system freeze when activating my 3rd display Status in xorg-server package in Ubuntu: Won't Fix Bug description: On Windows I use all three displays without issue, but I can only seem to activate any 2 of my 3 displays in Ubuntu. The moment I activate the 3rd, the system freezes. It may also be worth noting that due to this I have been disabling my built-in laptop display and leaving my two larger desktop displays active. When I open my laptop the whole system freezes and has to be power cycled. ProblemType: Bug DistroRelease: Ubuntu 17.10 Package: xorg 1:7.7+19ubuntu3 ProcVersionSignature: Ubuntu 4.13.0-16.19-generic 4.13.4 Uname: Linux 4.13.0-16-generic x86_64 ApportVersion: 2.20.7-0ubuntu3 Architecture: amd64 CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Thu Oct 19 13:48:32 2017 DistUpgraded: Fresh install DistroCodename: artful DistroVariant: ubuntu ExtraDebuggingInterest: Yes, if not too technical GraphicsCard: Intel Corporation 3rd Gen Core processor Graphics Controller [8086:0166] (rev 09) (prog-if 00 [VGA controller]) Subsystem: Lenovo 3rd Gen Core processor Graphics Controller [17aa:2203] InstallationDate: Installed on 2017-10-19 (0 days ago) InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20171018) MachineType: LENOVO 343522U ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.13.0-16-generic.efi.signed root=UUID=df6662ff-9496-4ff5-8165-82efdbf0b335 ro quiet splash vt.handoff=7 SourcePackage: xorg Symptom: display UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 05/28/2014 dmi.bios.vendor: LENOVO dmi.bios.version: GCET99WW (2.59 ) dmi.board.asset.tag: Not Available dmi.board.name: 343522U dmi.board.vendor: LENOVO dmi.board.version: Not Defined dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: Not Available dmi.modalias: dmi:bvnLENOVO:bvrGCET99WW(2.59):bd05/28/2014:svnLENOVO:pn343522U:pvrThinkPadX230Tablet:rvnLENOVO:rn343522U:rvrNotDefined:cvnLENOVO:ct10:cvrNotAvailable: dmi.product.family: ThinkPad X230 Tablet dmi.product.name: 343522U dmi.product.version: ThinkPad X230 Tablet dmi.sys.vendor: LENOVO version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.83-1 version.libgl1-mesa-dri: libgl1-mesa-dri 17.2.2-0ubuntu1 version.libgl1-mesa-glx: libgl1-mesa-glx 17.2.2-0ubuntu1 version.xserver-xorg-core: xserver-xorg-core 2:1.19.5-0ubuntu2 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.10.0-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20170309-0ubuntu1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.15-2 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg-server/+bug/1724979/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1725069] Re: Login GUI missing after upgrade 17.04 to 17.10
Thank you for reporting this bug to Ubuntu. Ubuntu 17.10 (artful) reached end-of-life on July 19, 2018. See this document for currently supported Ubuntu releases: https://wiki.ubuntu.com/Releases We appreciate that this bug may be old and you might not be interested in discussing it any more. But if you are then please upgrade to the latest Ubuntu version and re-test. If you then find the bug is still present in the newer Ubuntu version, please add a comment here telling us which new version it is in and change the bug status to Confirmed. ** Package changed: xorg (Ubuntu) => ubuntu ** Changed in: ubuntu Status: New => Won't Fix -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to xorg in Ubuntu. https://bugs.launchpad.net/bugs/1725069 Title: Login GUI missing after upgrade 17.04 to 17.10 Status in Ubuntu: Won't Fix Bug description: - system upgrade kubuntu 17.04 to 17.10 (without error message) - system /user/home encrypted with LVM LUKS - reboot - no Login GUI appears - login via user+password+startx works How to login with GUI? ProblemType: Bug DistroRelease: Ubuntu 17.10 Package: xorg 1:7.7+19ubuntu3 ProcVersionSignature: Ubuntu 4.13.0-16.19-generic 4.13.4 Uname: Linux 4.13.0-16-generic x86_64 ApportVersion: 2.20.7-0ubuntu3 Architecture: amd64 CompositorRunning: None CurrentDesktop: KDE Date: Fri Oct 20 01:52:19 2017 DistUpgraded: 2017-10-09 22:21:36,596 DEBUG failed to SystemUnLock() (E:Nicht gesperrt) DistroCodename: artful DistroVariant: kubuntu EcryptfsInUse: Yes GraphicsCard: Intel Corporation HD Graphics 530 [8086:1912] (rev 06) (prog-if 00 [VGA controller]) Subsystem: ASUSTeK Computer Inc. HD Graphics 530 [1043:8694] InstallationDate: Installed on 2017-08-28 (52 days ago) InstallationMedia: Kubuntu 17.04 "Zesty Zapus" - Release amd64 (20170412) MachineType: System manufacturer System Product Name ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.13.0-16-generic.efi.signed root=/dev/mapper/kubuntu--vg-root ro quiet splash vt.handoff=7 SourcePackage: xorg UpgradeStatus: Upgraded to artful on 2017-10-09 (10 days ago) dmi.bios.date: 12/27/2016 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 3016 dmi.board.asset.tag: Default string dmi.board.name: H170-PRO/USB 3.1 dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: Rev X.0x dmi.chassis.asset.tag: Default string dmi.chassis.type: 3 dmi.chassis.vendor: Default string dmi.chassis.version: Default string dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr3016:bd12/27/2016:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnH170-PRO/USB3.1:rvrRevX.0x:cvnDefaultstring:ct3:cvrDefaultstring: dmi.product.family: To be filled by O.E.M. dmi.product.name: System Product Name dmi.product.version: System Version dmi.sys.vendor: System manufacturer version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.83-1 version.libgl1-mesa-dri: libgl1-mesa-dri 17.2.2-0ubuntu1 version.libgl1-mesa-glx: libgl1-mesa-glx 17.2.2-0ubuntu1 version.xserver-xorg-core: xserver-xorg-core 2:1.19.5-0ubuntu2 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.10.0-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20170309-0ubuntu1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.15-2 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+bug/1725069/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1725949] Re: nouveau drivers fails to start a wayland session and fallback to x11
Thank you for reporting this bug to Ubuntu. Ubuntu 17.10 (artful) reached end-of-life on July 19, 2018. See this document for currently supported Ubuntu releases: https://wiki.ubuntu.com/Releases We appreciate that this bug may be old and you might not be interested in discussing it any more. But if you are then please upgrade to the latest Ubuntu version and re-test. If you then find the bug is still present in the newer Ubuntu version, please add a comment here telling us which new version it is in and change the bug status to Confirmed. ** Package changed: xorg (Ubuntu) => mutter (Ubuntu) ** Changed in: mutter (Ubuntu) Status: New => Won't Fix -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to xorg in Ubuntu. https://bugs.launchpad.net/bugs/1725949 Title: nouveau drivers fails to start a wayland session and fallback to x11 Status in mutter package in Ubuntu: Won't Fix Bug description: I have a Nvidia GTX 670. I tried the nouveau driver. At boot, it takes a unusual long time then finally shows me gdm3 and everything is working after. But echo $XDG_SESSION_TYPE is set to "x11". Reading the logs, I can see that after multiple failures to launch wayland, it falls back to X11. I added an attachement of journalctl -b -1 where it fails with nouveau (I'm filling the bug after reinstalling nvidia proprietary driver). lspci -v 01:00.0 VGA compatible controller: NVIDIA Corporation GK104 [GeForce GTX 670] (rev a1) (prog-if 00 [VGA controller]) Subsystem: eVga.com. Corp. GK104 [GeForce GTX 670] Flags: bus master, fast devsel, latency 0, IRQ 29 Memory at f600 (32-bit, non-prefetchable) [size=16M] Memory at e800 (64-bit, prefetchable) [size=128M] Memory at f000 (64-bit, prefetchable) [size=32M] I/O ports at e000 [size=128] [virtual] Expansion ROM at 000c [disabled] [size=128K] Capabilities: Kernel driver in use: nvidia Kernel modules: nvidiafb, nouveau, nvidia_384_drm, nvidia_384 ProblemType: Bug DistroRelease: Ubuntu 17.10 Package: xorg 1:7.7+19ubuntu3 ProcVersionSignature: Ubuntu 4.13.0-16.19-generic 4.13.4 Uname: Linux 4.13.0-16-generic x86_64 NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia .proc.driver.nvidia.gpus..01.00.0: Error: [Errno 21] Is a directory: '/proc/driver/nvidia/gpus/:01:00.0' .proc.driver.nvidia.registry: Binary: "" .proc.driver.nvidia.version: NVRM version: NVIDIA UNIX x86_64 Kernel Module 384.90 Tue Sep 19 19:17:35 PDT 2017 GCC version: gcc version 7.2.0 (Ubuntu 7.2.0-8ubuntu3) .proc.driver.nvidia.warnings.fbdev: Your system is not currently configured to drive a VGA console on the primary VGA device. The NVIDIA Linux graphics driver requires the use of a text-mode VGA console. Use of other console drivers including, but not limited to, vesafb, may result in corruption and stability problems, and is not supported. ApportVersion: 2.20.7-0ubuntu3 Architecture: amd64 BootLog: [[0;32m OK [0m] Started LSB: Speech Dispatcher. [[0;32m OK [0m] Started LSB: automatic crash report generation. CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Sun Oct 22 11:37:08 2017 DistUpgraded: Fresh install DistroCodename: artful DistroVariant: ubuntu DkmsStatus: bbswitch, 0.8, 4.13.0-16-generic, x86_64: installed nvidia-384, 384.90, 4.13.0-16-generic, x86_64: installed ExtraDebuggingInterest: Yes GraphicsCard: NVIDIA Corporation GK104 [GeForce GTX 670] [10de:1189] (rev a1) (prog-if 00 [VGA controller]) Subsystem: eVga.com. Corp. GK104 [GeForce GTX 670] [3842:2678] InstallationDate: Installed on 2017-09-17 (34 days ago) InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Alpha amd64 (20170915) MachineType: System manufacturer System Product Name ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.13.0-16-generic root=UUID=567a9b2b-0864-450e-9cfe-dab7a54b9fce ro rootflags=subvol=@ quiet splash vt.handoff=7 SourcePackage: xorg Symptom: display UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 09/28/2012 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 0501 dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: P8Z77-V LX2 dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: Rev X.0x dmi.chassis.asset.tag: Asset-1234567890 dmi.chassis.type: 3 dmi.chassis.vendor: Chassis Manufacture dmi.chassis.version: Chassis Version dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr0501:bd09/28/2012:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnP8Z77-VLX2:rvrRevX.0x:cvnChassisManufacture:ct3:cvrChassisVersion: dmi.product.family: To be filled by O.E.M. dmi.product.name: System Product Name dm
[Touch-packages] [Bug 1725360] Re: Secondary display can not be set
Thank you for reporting this bug to Ubuntu. Ubuntu 17.10 (artful) reached end-of-life on July 19, 2018. See this document for currently supported Ubuntu releases: https://wiki.ubuntu.com/Releases We appreciate that this bug may be old and you might not be interested in discussing it any more. But if you are then please upgrade to the latest Ubuntu version and re-test. If you then find the bug is still present in the newer Ubuntu version, please add a comment here telling us which new version it is in and change the bug status to Confirmed. ** Package changed: xorg (Ubuntu) => gnome-shell (Ubuntu) ** Changed in: gnome-shell (Ubuntu) Status: New => Won't Fix -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to xorg in Ubuntu. https://bugs.launchpad.net/bugs/1725360 Title: Secondary display can not be set Status in gnome-shell package in Ubuntu: Won't Fix Bug description: The position of the secondary display can not be applied with scales of 200% and 300%. Can be modified with scale of 100% after modified some other configuration like Single Display scale. After set a new position of the secondary display (with 100% scale) is not possible to change the scale maintaining the actual position. Using also Nvidia driver 384.90 ProblemType: Bug DistroRelease: Ubuntu 17.10 Package: xorg 1:7.7+19ubuntu3 ProcVersionSignature: Ubuntu 4.13.0-16.19-generic 4.13.4 Uname: Linux 4.13.0-16-generic x86_64 NonfreeKernelModules: wl nvidia_uvm nvidia_drm nvidia_modeset nvidia .proc.driver.nvidia.gpus..01.00.0: Error: [Errno 21] Is a directory: '/proc/driver/nvidia/gpus/:01:00.0' .proc.driver.nvidia.registry: Binary: "" .proc.driver.nvidia.version: NVRM version: NVIDIA UNIX x86_64 Kernel Module 384.90 Tue Sep 19 19:17:35 PDT 2017 GCC version: gcc version 7.2.0 (Ubuntu 7.2.0-8ubuntu3) .tmp.unity_support_test.0: ApportVersion: 2.20.7-0ubuntu3 Architecture: amd64 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Fri Oct 20 14:02:12 2017 DistUpgraded: 2017-10-20 13:15:46,366 DEBUG icon theme changed, re-reading DistroCodename: artful DistroVariant: ubuntu ExtraDebuggingInterest: Yes, including running git bisection searches GraphicsCard: Intel Corporation 4th Gen Core Processor Integrated Graphics Controller [8086:0416] (rev 06) (prog-if 00 [VGA controller]) Subsystem: Lenovo 4th Gen Core Processor Integrated Graphics Controller [17aa:3978] Subsystem: Lenovo GM107M [GeForce GTX 960M] [17aa:3978] InstallationDate: Installed on 2017-08-23 (57 days ago) InstallationMedia: Ubuntu 17.04 "Zesty Zapus" - Release amd64 (20170412) LightdmDisplayLog: (II) Server terminated successfully (0). Closing log file. MachineType: LENOVO 20349 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.13.0-16-generic.efi.signed root=UUID=0f865fdf-a3ef-4fd1-88f3-80f6ca16ef1c ro quiet splash vt.handoff=7 SourcePackage: xorg Symptom: display UpgradeStatus: Upgraded to artful on 2017-10-20 (0 days ago) dmi.bios.date: 02/11/2015 dmi.bios.vendor: LENOVO dmi.bios.version: 9ECN37WW(V2.01) dmi.board.asset.tag: 31900058WIN dmi.board.name: Lenovo Y50-70 Touch dmi.board.vendor: LENOVO dmi.board.version: 31900058WIN dmi.chassis.asset.tag: 31900058WIN dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: Lenovo Y50-70 Touch dmi.modalias: dmi:bvnLENOVO:bvr9ECN37WW(V2.01):bd02/11/2015:svnLENOVO:pn20349:pvrLenovoY50-70Touch:rvnLENOVO:rnLenovoY50-70Touch:rvr31900058WIN:cvnLENOVO:ct10:cvrLenovoY50-70Touch: dmi.product.family: IDEAPAD dmi.product.name: 20349 dmi.product.version: Lenovo Y50-70 Touch dmi.sys.vendor: LENOVO version.compiz: compiz 1:0.9.13.1+17.10.20170901-0ubuntu1 version.libdrm2: libdrm2 2.4.83-1 version.libgl1-mesa-dri: libgl1-mesa-dri 17.2.2-0ubuntu1 version.libgl1-mesa-glx: libgl1-mesa-glx 17.2.2-0ubuntu1 version.nvidia-graphics-drivers: nvidia-graphics-drivers-* N/A version.xserver-xorg-core: xserver-xorg-core 2:1.19.5-0ubuntu2 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.10.0-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20170309-0ubuntu1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.15-2 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1725360/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1724966] Re: Settings - Display - Primary Display selection does not allow selection of available entries
Thank you for reporting this bug to Ubuntu. Ubuntu 17.10 (artful) reached end-of-life on July 19, 2018. See this document for currently supported Ubuntu releases: https://wiki.ubuntu.com/Releases We appreciate that this bug may be old and you might not be interested in discussing it any more. But if you are then please upgrade to the latest Ubuntu version and re-test. If you then find the bug is still present in the newer Ubuntu version, please add a comment here telling us which new version it is in and change the bug status to Confirmed. ** Package changed: xorg (Ubuntu) => gnome-control-center (Ubuntu) ** Changed in: gnome-control-center (Ubuntu) Status: New => Won't Fix -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to xorg in Ubuntu. https://bugs.launchpad.net/bugs/1724966 Title: Settings - Display - Primary Display selection does not allow selection of available entries Status in gnome-control-center package in Ubuntu: Won't Fix Bug description: Settings - Display - Primary Displayoffers me a choice of 3 displays. Clicking on any of the non checked displays does nothing. NOTE: My other 2 displays are currently disabled and likely shouldn't be showing up in this list. ProblemType: Bug DistroRelease: Ubuntu 17.10 Package: xorg 1:7.7+19ubuntu3 ProcVersionSignature: Ubuntu 4.13.0-16.19-generic 4.13.4 Uname: Linux 4.13.0-16-generic x86_64 ApportVersion: 2.20.7-0ubuntu3 Architecture: amd64 CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Thu Oct 19 13:27:08 2017 DistUpgraded: Fresh install DistroCodename: artful DistroVariant: ubuntu ExtraDebuggingInterest: Yes, if not too technical GraphicsCard: Intel Corporation 3rd Gen Core processor Graphics Controller [8086:0166] (rev 09) (prog-if 00 [VGA controller]) Subsystem: Lenovo 3rd Gen Core processor Graphics Controller [17aa:2203] InstallationDate: Installed on 2017-10-19 (0 days ago) InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20171018) MachineType: LENOVO 343522U ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.13.0-16-generic.efi.signed root=UUID=df6662ff-9496-4ff5-8165-82efdbf0b335 ro quiet splash vt.handoff=7 SourcePackage: xorg Symptom: display UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 05/28/2014 dmi.bios.vendor: LENOVO dmi.bios.version: GCET99WW (2.59 ) dmi.board.asset.tag: Not Available dmi.board.name: 343522U dmi.board.vendor: LENOVO dmi.board.version: Not Defined dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: Not Available dmi.modalias: dmi:bvnLENOVO:bvrGCET99WW(2.59):bd05/28/2014:svnLENOVO:pn343522U:pvrThinkPadX230Tablet:rvnLENOVO:rn343522U:rvrNotDefined:cvnLENOVO:ct10:cvrNotAvailable: dmi.product.family: ThinkPad X230 Tablet dmi.product.name: 343522U dmi.product.version: ThinkPad X230 Tablet dmi.sys.vendor: LENOVO version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.83-1 version.libgl1-mesa-dri: libgl1-mesa-dri 17.2.2-0ubuntu1 version.libgl1-mesa-glx: libgl1-mesa-glx 17.2.2-0ubuntu1 version.xserver-xorg-core: xserver-xorg-core 2:1.19.5-0ubuntu2 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.10.0-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20170309-0ubuntu1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.15-2 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-control-center/+bug/1724966/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1727696] Re: System does not shut down without Ctrl+Alt+F7
Thank you for reporting this bug to Ubuntu. Ubuntu 17.10 (artful) reached end-of-life on July 19, 2018. See this document for currently supported Ubuntu releases: https://wiki.ubuntu.com/Releases We appreciate that this bug may be old and you might not be interested in discussing it any more. But if you are then please upgrade to the latest Ubuntu version and re-test. If you then find the bug is still present in the newer Ubuntu version, please add a comment here telling us which new version it is in and change the bug status to Confirmed. ** Package changed: xorg (Ubuntu) => ubuntu ** Changed in: ubuntu Status: Confirmed => Won't Fix -- 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/1727696 Title: System does not shut down without Ctrl+Alt+F7 Status in Ubuntu: Won't Fix Bug description: This is a fresh 17.10 installation, for some reason defaulting to Xorg instead of wayland (no choice given in the login screen). Anyway, shutting down from X session doesn't work. Screen stays blank black, cursor blinking in top left corner. Seems like it's stuck there forever (haven't had patience to wait long enough). Found a workaround: in the black screen cursor blinking state above, hit Ctrl+Alt+F7. One second or so after that, the system shuts down cleanly every time. ProblemType: Bug DistroRelease: Ubuntu 17.10 Package: xorg 1:7.7+19ubuntu3 ProcVersionSignature: Ubuntu 4.13.0-16.19-generic 4.13.4 Uname: Linux 4.13.0-16-generic x86_64 ApportVersion: 2.20.7-0ubuntu3.1 Architecture: amd64 BootLog: /dev/sda1: clean, 153154/2842624 files, 1254197/11368960 blocks CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Thu Oct 26 14:27:05 2017 DistUpgraded: Fresh install DistroCodename: artful DistroVariant: ubuntu ExtraDebuggingInterest: Yes, if not too technical GraphicsCard: Intel Corporation 3rd Gen Core processor Graphics Controller [8086:0166] (rev 09) (prog-if 00 [VGA controller]) Subsystem: ASUSTeK Computer Inc. N56VZ [1043:2103] NVIDIA Corporation GK107M [GeForce GT 650M] [10de:0fd1] (rev a1) (prog-if 00 [VGA controller]) Subsystem: ASUSTeK Computer Inc. N56VZ [1043:2103] InstallationDate: Installed on 2017-10-26 (0 days ago) InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20171018) MachineType: ASUSTeK COMPUTER INC. N56VZ ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.13.0-16-generic root=UUID=be8c6652-102f-4bc2-9739-4c7954b40a80 ro quiet splash vt.handoff=7 SourcePackage: xorg Symptom: display UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 05/22/2013 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: N56VZ.217 dmi.board.asset.tag: ATN12345678901234567 dmi.board.name: N56VZ 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.:bvrN56VZ.217:bd05/22/2013:svnASUSTeKCOMPUTERINC.:pnN56VZ:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnN56VZ:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0: dmi.product.family: N dmi.product.name: N56VZ dmi.product.version: 1.0 dmi.sys.vendor: ASUSTeK COMPUTER INC. version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.83-1 version.libgl1-mesa-dri: libgl1-mesa-dri 17.2.2-0ubuntu1 version.libgl1-mesa-glx: libgl1-mesa-glx 17.2.2-0ubuntu1 version.xserver-xorg-core: xserver-xorg-core 2:1.19.5-0ubuntu2 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.10.0-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20170309-0ubuntu1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.15-2 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+bug/1727696/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1694820] Re: Problem Driver
Thank you for reporting this bug to Ubuntu. Ubuntu 17.10 (artful) reached end-of-life on July 19, 2018. See this document for currently supported Ubuntu releases: https://wiki.ubuntu.com/Releases We appreciate that this bug may be old and you might not be interested in discussing it any more. But if you are then please upgrade to the latest Ubuntu version and re-test. If you then find the bug is still present in the newer Ubuntu version, please add a comment here telling us which new version it is in and change the bug status to Confirmed. ** Changed in: xorg (Ubuntu) Status: New => Won't Fix -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to xorg in Ubuntu. https://bugs.launchpad.net/bugs/1694820 Title: Problem Driver Status in xorg package in Ubuntu: Won't Fix Bug description: Hello, Attach image ProblemType: Bug DistroRelease: Ubuntu 17.10 Package: xorg 1:7.7+19ubuntu1 ProcVersionSignature: Ubuntu 4.10.0-21.23-generic 4.10.11 Uname: Linux 4.10.0-21-generic x86_64 ApportVersion: 2.20.5-0ubuntu4 Architecture: amd64 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: None CurrentDesktop: GNOME Date: Wed May 31 16:16:18 2017 DistUpgraded: 2017-05-15 15:48:11,029 DEBUG Running PostInstallScript: './xorg_fix_proprietary.py' DistroCodename: artful DistroVariant: ubuntu DkmsStatus: vhba, 20161009, 4.10.0-20-generic, x86_64: installed vhba, 20161009, 4.10.0-21-generic, x86_64: installed GraphicsCard: Intel Corporation 2nd Generation Core Processor Family Integrated Graphics Controller [8086:0116] (rev 09) (prog-if 00 [VGA controller]) Subsystem: Samsung Electronics Co Ltd 2nd Generation Core Processor Family Integrated Graphics Controller [144d:c0d7] InstallationDate: Installed on 2015-07-26 (675 days ago) InstallationMedia: Ubuntu-GNOME 15.10 "Wily Werewolf" - Alpha amd64 (20150723) MachineType: SAMSUNG ELECTRONICS CO., LTD. 530U3C/530U4C ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.10.0-21-generic root=UUID=4f4435ca-b877-47a5-9065-3dd624c0514e ro rootflags=subvol=@ quiet splash vt.handoff=7 SourcePackage: xorg UpgradeStatus: Upgraded to artful on 2017-05-15 (16 days ago) dmi.bios.date: 04/15/2013 dmi.bios.vendor: Phoenix Technologies Ltd. dmi.bios.version: P14AAJ dmi.board.asset.tag: Base Board Asset Tag dmi.board.name: SAMSUNG_NP1234567890 dmi.board.vendor: SAMSUNG ELECTRONICS CO., LTD. dmi.board.version: FAB1 dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 9 dmi.chassis.vendor: SAMSUNG ELECTRONICS CO., LTD. dmi.chassis.version: 0.1 dmi.modalias: dmi:bvnPhoenixTechnologiesLtd.:bvrP14AAJ:bd04/15/2013:svnSAMSUNGELECTRONICSCO.,LTD.:pn530U3C/530U4C:pvr0.1:rvnSAMSUNGELECTRONICSCO.,LTD.:rnSAMSUNG_NP1234567890:rvrFAB1:cvnSAMSUNGELECTRONICSCO.,LTD.:ct9:cvr0.1: dmi.product.name: 530U3C/530U4C dmi.product.version: 0.1 dmi.sys.vendor: SAMSUNG ELECTRONICS CO., LTD. version.compiz: compiz N/A version.ia32-libs: ia32-libs N/A version.libdrm2: libdrm2 2.4.80-1 version.libgl1-mesa-dri: libgl1-mesa-dri 17.1.0-1ubuntu1 version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A version.libgl1-mesa-glx: libgl1-mesa-glx 17.1.0-1ubuntu1 version.xserver-xorg-core: xserver-xorg-core 2:1.19.3-1ubuntu1 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.10.5-1ubuntu1 version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.9.0-0ubuntu1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20170309-0ubuntu1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.14-0ubuntu1 xserver.bootTime: Thu Mar 10 13:48:25 2016 xserver.configfile: default xserver.errors: xserver.logfile: /var/log/Xorg.0.log xserver.outputs: xserver.version: 2:1.17.3-2ubuntu4 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1694820/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1697789] Re: Xorg: page allocation failure: order:0, mode:0x14210d2(GFP_HIGHUSER|__GFP_NORETRY|__GFP_RECLAIMABLE), nodemask=(null)
Thank you for reporting this bug to Ubuntu. Ubuntu 17.10 (artful) reached end-of-life on July 19, 2018. See this document for currently supported Ubuntu releases: https://wiki.ubuntu.com/Releases We appreciate that this bug may be old and you might not be interested in discussing it any more. But if you are then please upgrade to the latest Ubuntu version and re-test. If you then find the bug is still present in the newer Ubuntu version, please add a comment here telling us which new version it is in and change the bug status to Confirmed. ** Package changed: xorg (Ubuntu) => linux (Ubuntu) ** Changed in: linux (Ubuntu) Status: Confirmed => Won't Fix -- 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/1697789 Title: Xorg: page allocation failure: order:0, mode:0x14210d2(GFP_HIGHUSER|__GFP_NORETRY|__GFP_RECLAIMABLE), nodemask=(null) Status in X.Org X server: Unknown Status in linux package in Ubuntu: Won't Fix Status in xorg-server package in Arch Linux: New Bug description: dmesg: [23559.058500] Xorg: page allocation failure: order:0, mode:0x14210d2(GFP_HIGHUSER|__GFP_NORETRY|__GFP_RECLAIMABLE), nodemask=(null) [23559.058509] Xorg cpuset=/ mems_allowed=0 [23559.058516] CPU: 1 PID: 1797 Comm: Xorg Not tainted 4.12.0-041200rc5-generic #201706112031 [23559.058517] Hardware name: SAMSUNG ELECTRONICS CO., LTD. 530U3C/530U4C/SAMSUNG_NP1234567890, BIOS P14AAJ 04/15/2013 [23559.058519] Call Trace: [23559.058528] dump_stack+0x63/0x8d [23559.058532] warn_alloc+0x114/0x1c0 [23559.058535] __alloc_pages_slowpath+0xe07/0xe10 [23559.058539] __alloc_pages_nodemask+0x233/0x250 [23559.058543] alloc_pages_vma+0xab/0x250 [23559.058547] shmem_alloc_page+0x70/0xc0 [23559.058550] ? __radix_tree_insert+0x45/0x220 [23559.058553] ? __vm_enough_memory+0x29/0x130 [23559.058555] shmem_alloc_and_acct_page+0x72/0x1b0 [23559.058558] ? find_get_entry+0x1e/0xc0 [23559.058561] shmem_getpage_gfp+0x195/0xbd0 [23559.058564] shmem_read_mapping_page_gfp+0x44/0x80 [23559.058611] i915_gem_object_get_pages_gtt+0x204/0x5a0 [i915] [23559.058643] i915_gem_object_get_pages+0x20/0x60 [i915] [23559.058673] __i915_gem_object_get_pages+0x5c/0x70 [i915] [23559.058706] __i915_vma_do_pin+0x1c6/0x3a0 [i915] [23559.058737] i915_gem_execbuffer_reserve_vma.isra.29+0x14d/0x1b0 [i915] [23559.058765] i915_gem_execbuffer_reserve.isra.30+0x3b7/0x3e0 [i915] [23559.058794] i915_gem_do_execbuffer.isra.36+0x577/0x16c0 [i915] [23559.058799] ? unix_stream_recvmsg+0x54/0x70 [23559.058801] ? unix_state_double_lock+0x70/0x70 [23559.058830] i915_gem_execbuffer2+0x96/0x1b0 [i915] [23559.058849] drm_ioctl+0x216/0x4c0 [drm] [23559.058877] ? i915_gem_execbuffer+0x2f0/0x2f0 [i915] [23559.058881] ? __remove_hrtimer+0x3c/0x70 [23559.058885] do_vfs_ioctl+0xa3/0x600 [23559.05] ? do_setitimer+0xe0/0x240 [23559.058891] ? SyS_setitimer+0xf1/0x120 [23559.058894] SyS_ioctl+0x79/0x90 [23559.058897] entry_SYSCALL_64_fastpath+0x1e/0xa9 [23559.058900] RIP: 0033:0x7fd8c5c7e987 [23559.058901] RSP: 002b:7ffd494ac738 EFLAGS: 0246 ORIG_RAX: 0010 [23559.058904] RAX: ffda RBX: 0006 RCX: 7fd8c5c7e987 [23559.058905] RDX: 7ffd494ac790 RSI: 40406469 RDI: 000c [23559.058907] RBP: 0028 R08: 0001 R09: 000c [23559.058908] R10: 0001 R11: 0246 R12: 0040 [23559.058909] R13: 0008 R14: 5581c086a6c0 R15: [23559.058912] Mem-Info: [23559.058918] active_anon:1016643 inactive_anon:298858 isolated_anon:0 active_file:395940 inactive_file:1147459 isolated_file:0 unevictable:129 dirty:124022 writeback:21146 unstable:0 slab_reclaimable:57926 slab_unreclaimable:23062 mapped:283483 shmem:248113 pagetables:23247 bounce:0 free:29069 free_pcp:245 free_cma:0 [23559.058923] Node 0 active_anon:4066572kB inactive_anon:1195432kB active_file:1583760kB inactive_file:4589836kB unevictable:516kB isolated(anon):0kB isolated(file):0kB mapped:1133932kB dirty:496088kB writeback:84584kB shmem:992452kB shmem_thp: 0kB shmem_pmdmapped: 0kB anon_thp: 976896kB writeback_tmp:0kB unstable:0kB all_unreclaimable? no [23559.058924] Node 0 DMA free:15360kB min:84kB low:104kB high:124kB active_anon:0kB inactive_anon:0kB active_file:0kB inactive_file:0kB unevictable:0kB writepending:0kB present:15984kB managed:15360kB mlocked:0kB slab_reclaimable:0kB slab_unreclaimable:0kB kernel_stack:0kB pagetables:0kB bounce:0kB free_pcp:0kB local_pcp:0kB free_cma:0kB [23559.058930] lowmem_reserve[]: 0 3226 11726 11726 11726 [23559.058935] Node 0 DMA32 free:52176kB min:18568kB low:23208kB high:27848kB active_anon:7
[Touch-packages] [Bug 1721957] Re: Blur on topbar
Thank you for reporting this bug to Ubuntu. Ubuntu 17.10 (artful) reached end-of-life on July 19, 2018. See this document for currently supported Ubuntu releases: https://wiki.ubuntu.com/Releases We appreciate that this bug may be old and you might not be interested in discussing it any more. But if you are then please upgrade to the latest Ubuntu version and re-test. If you then find the bug is still present in the newer Ubuntu version, please add a comment here telling us which new version it is in and change the bug status to Confirmed. ** Package changed: xorg (Ubuntu) => gnome-shell (Ubuntu) ** Changed in: gnome-shell (Ubuntu) Status: New => Won't Fix -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to xorg in Ubuntu. https://bugs.launchpad.net/bugs/1721957 Title: Blur on topbar Status in gnome-shell package in Ubuntu: Won't Fix Bug description: Hi, after dist-upgrade today (07-out-17) , when I touch any window on topbar this fonts go blur Tks! ProblemType: Bug DistroRelease: Ubuntu 17.10 Package: xorg 1:7.7+19ubuntu2 ProcVersionSignature: Ubuntu 4.13.0-12.13-generic 4.13.3 Uname: Linux 4.13.0-12-generic x86_64 ApportVersion: 2.20.7-0ubuntu2 Architecture: amd64 CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Sat Oct 7 09:47:40 2017 DistUpgraded: Fresh install DistroCodename: artful DistroVariant: ubuntu ExtraDebuggingInterest: No GraphicsCard: Intel Corporation Xeon E3-1200 v3/4th Gen Core Processor Integrated Graphics Controller [8086:0402] (rev 06) (prog-if 00 [VGA controller]) Subsystem: Gigabyte Technology Co., Ltd Xeon E3-1200 v3/4th Gen Core Processor Integrated Graphics Controller [1458:d000] NVIDIA Corporation GK208 [GeForce GT 710B] [10de:128b] (rev a1) (prog-if 00 [VGA controller]) Subsystem: eVga.com. Corp. GK208 [GeForce GT 710B] [3842:2713] InstallationDate: Installed on 2017-10-05 (1 days ago) InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Alpha amd64 (20170925) MachineType: Gigabyte Technology Co., Ltd. H81M-S1 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.13.0-12-generic root=UUID=6b8e8b1b-5097-43df-80ee-a740e4d429bb ro quiet splash vt.handoff=7 SourcePackage: xorg Symptom: display UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 06/20/2014 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: FF dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: H81M-S1 dmi.board.vendor: Gigabyte Technology Co., Ltd. dmi.board.version: x.x dmi.chassis.asset.tag: To Be Filled By O.E.M. dmi.chassis.type: 3 dmi.chassis.vendor: Gigabyte Technology Co., Ltd. dmi.chassis.version: To Be Filled By O.E.M. dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrFF:bd06/20/2014:svnGigabyteTechnologyCo.,Ltd.:pnH81M-S1:pvrTobefilledbyO.E.M.:rvnGigabyteTechnologyCo.,Ltd.:rnH81M-S1:rvrx.x:cvnGigabyteTechnologyCo.,Ltd.:ct3:cvrToBeFilledByO.E.M.: dmi.product.family: To be filled by O.E.M. dmi.product.name: H81M-S1 dmi.product.version: To be filled by O.E.M. dmi.sys.vendor: Gigabyte Technology Co., Ltd. version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.83-1 version.libgl1-mesa-dri: libgl1-mesa-dri 17.2.2-0ubuntu1 version.libgl1-mesa-glx: libgl1-mesa-glx 17.2.2-0ubuntu1 version.xserver-xorg-core: xserver-xorg-core 2:1.19.3-1ubuntu7 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.10.0-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20170309-0ubuntu1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.15-2 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1721957/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1722355] Re: Despite power/display settings on never, screen turns off
Thank you for reporting this bug to Ubuntu. Ubuntu 17.10 (artful) reached end-of-life on July 19, 2018. See this document for currently supported Ubuntu releases: https://wiki.ubuntu.com/Releases We appreciate that this bug may be old and you might not be interested in discussing it any more. But if you are then please upgrade to the latest Ubuntu version and re-test. If you then find the bug is still present in the newer Ubuntu version, please add a comment here telling us which new version it is in and change the bug status to Confirmed. ** Package changed: xorg (Ubuntu) => xorg-server (Ubuntu) ** Changed in: xorg-server (Ubuntu) Status: New => Won't Fix ** Also affects: nvidia-graphics-drivers-384 (Ubuntu) Importance: Undecided Status: New ** Changed in: nvidia-graphics-drivers-384 (Ubuntu) Status: New => Won't Fix -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to xorg in Ubuntu. https://bugs.launchpad.net/bugs/1722355 Title: Despite power/display settings on never, screen turns off Status in nvidia-graphics-drivers-384 package in Ubuntu: Won't Fix Status in xorg-server package in Ubuntu: Won't Fix Bug description: Running 17.10 64bit on Syx/MSI 16Gb desktop with Geforce GTX950 on Samsung monitor. When left unattended, screen blanks after a few minutes, as if it was set to. Wakes with no issues, but sometimes i find that it has logged me out. I have triple-checked all settings and see no problem there. Problem began a few days ago after a recent update. Thanks ProblemType: Bug DistroRelease: Ubuntu 17.10 Package: xorg 1:7.7+19ubuntu2 ProcVersionSignature: Ubuntu 4.13.0-12.13-generic 4.13.3 Uname: Linux 4.13.0-12-generic x86_64 NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia .proc.driver.nvidia.gpus..01.00.0: Error: [Errno 21] Is a directory: '/proc/driver/nvidia/gpus/:01:00.0' .proc.driver.nvidia.registry: Binary: "" .proc.driver.nvidia.version: NVRM version: NVIDIA UNIX x86_64 Kernel Module 384.90 Tue Sep 19 19:17:35 PDT 2017 GCC version: gcc version 7.2.0 (Ubuntu 7.2.0-8ubuntu2) .proc.driver.nvidia.warnings.fbdev: Your system is not currently configured to drive a VGA console on the primary VGA device. The NVIDIA Linux graphics driver requires the use of a text-mode VGA console. Use of other console drivers including, but not limited to, vesafb, may result in corruption and stability problems, and is not supported. .tmp.unity_support_test.0: ApportVersion: 2.20.7-0ubuntu2 Architecture: amd64 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Mon Oct 9 12:57:46 2017 DistUpgraded: Fresh install DistroCodename: artful DistroVariant: ubuntu ExtraDebuggingInterest: Yes GraphicsCard: NVIDIA Corporation GM206 [GeForce GTX 950] [10de:1402] (rev a1) (prog-if 00 [VGA controller]) Subsystem: eVga.com. Corp. GM206 [GeForce GTX 950] [3842:2957] InstallationDate: Installed on 2017-04-07 (184 days ago) InstallationMedia: Ubuntu 17.04 "Zesty Zapus" - Beta amd64 (20170321) MachineType: MSI MS-7673 ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.13.0-12-generic root=UUID=7aaf85cc-4052-49d5-ba13-4e3a8c8ff17d ro quiet splash vt.handoff=7 SourcePackage: xorg Symptom: display UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 08/31/2011 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: V1.28B6 dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: P67A-C43 (MS-7673) 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.:bvrV1.28B6:bd08/31/2011:svnMSI:pnMS-7673:pvr1.0:rvnMSI:rnP67A-C43(MS-7673):rvr1.0:cvnMSI:ct3:cvr1.0: dmi.product.family: To be filled by O.E.M. dmi.product.name: MS-7673 dmi.product.version: 1.0 dmi.sys.vendor: MSI version.compiz: compiz 1:0.9.13.1+17.10.20170901-0ubuntu1 version.libdrm2: libdrm2 2.4.83-1 version.libgl1-mesa-dri: libgl1-mesa-dri 17.2.2-0ubuntu1 version.libgl1-mesa-glx: libgl1-mesa-glx 17.2.2-0ubuntu1 version.nvidia-graphics-drivers: nvidia-graphics-drivers-* N/A version.xserver-xorg-core: xserver-xorg-core 2:1.19.3-1ubuntu7 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.10.0-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20170309-0ubuntu1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.15-2 xserver.bootTime: Mon Oct 9 12:44:58 2017 xserver.configfile: default
[Touch-packages] [Bug 1703476] Re: Touchpad
Thank you for reporting this bug to Ubuntu. Ubuntu 17.10 (artful) reached end-of-life on July 19, 2018. See this document for currently supported Ubuntu releases: https://wiki.ubuntu.com/Releases We appreciate that this bug may be old and you might not be interested in discussing it any more. But if you are then please upgrade to the latest Ubuntu version and re-test. If you then find the bug is still present in the newer Ubuntu version, please add a comment here telling us which new version it is in and change the bug status to Confirmed. ** Package changed: xorg (Ubuntu) => xorg-server (Ubuntu) ** Changed in: xorg-server (Ubuntu) Status: Confirmed => Won't Fix -- 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/1703476 Title: Touchpad Status in xorg-server package in Ubuntu: Won't Fix Bug description: My touchpad does not work, Ubuntu recognizes, but nothing I found on the internet makes it work. NOTE: It stopped working in update 16.04. But I managed to fix it, but after it upgraded to 17.04 it did not work anymore. ProblemType: Bug DistroRelease: Ubuntu 17.10 Package: xorg 1:7.7+19ubuntu1 Uname: Linux 4.11.7-041107-generic x86_64 .tmp.unity_support_test.0: ApportVersion: 2.20.5-0ubuntu5 Architecture: amd64 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: None Date: Mon Jul 10 20:26:00 2017 DistUpgraded: 2017-07-03 19:51:16,271 DEBUG icon theme changed, re-reading DistroCodename: artful DistroVariant: ubuntu ExtraDebuggingInterest: I just need to know a workaround GraphicsCard: Intel Corporation Atom/Celeron/Pentium Processor x5-E8000/J3xxx/N3xxx Integrated Graphics Controller [8086:22b1] (rev 21) (prog-if 00 [VGA controller]) Subsystem: Dell Atom/Celeron/Pentium Processor x5-E8000/J3xxx/N3xxx Integrated Graphics Controller [1028:06d8] InstallationDate: Installed on 2017-07-01 (9 days ago) InstallationMedia: Ubuntu 17.04 "Zesty Zapus" - Release amd64 (20170412) MachineType: Dell Inc. Inspiron 5452 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.11.7-041107-generic root=UUID=7e39baf8-6108-4b98-ae8c-f2b21bdbbfbe ro i8042.nopnp quiet splash vt.handoff=7 SourcePackage: xorg UpgradeStatus: Upgraded to artful on 2017-07-03 (7 days ago) dmi.bios.date: 04/25/2016 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.4.1 dmi.board.name: 0F77J1 dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 8 dmi.chassis.vendor: Dell Inc. dmi.chassis.version: 1.4.1 dmi.modalias: dmi:bvnDellInc.:bvr1.4.1:bd04/25/2016:svnDellInc.:pnInspiron5452:pvr1.4.1:rvnDellInc.:rn0F77J1:rvrA00:cvnDellInc.:ct8:cvr1.4.1: dmi.product.name: Inspiron 5452 dmi.product.version: 1.4.1 dmi.sys.vendor: Dell Inc. version.compiz: compiz 1:0.9.13.1+17.10.20170704-0ubuntu1 version.ia32-libs: ia32-libs N/A version.libdrm2: libdrm2 2.4.81-2 version.libgl1-mesa-dri: libgl1-mesa-dri 17.1.4-1ubuntu1 version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A version.libgl1-mesa-glx: libgl1-mesa-glx 17.1.4-1ubuntu1 version.xserver-xorg-core: xserver-xorg-core 2:1.19.3-1ubuntu2 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.9.0-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20170309-0ubuntu1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.15-2 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg-server/+bug/1703476/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1704616] Re: Display settings mess up when screens rearranged in xfce-display-settings
Thank you for reporting this bug to Ubuntu. Ubuntu 17.10 (artful) reached end-of-life on July 19, 2018. See this document for currently supported Ubuntu releases: https://wiki.ubuntu.com/Releases We appreciate that this bug may be old and you might not be interested in discussing it any more. But if you are then please upgrade to the latest Ubuntu version and re-test. If you then find the bug is still present in the newer Ubuntu version, please add a comment here telling us which new version it is in and change the bug status to Confirmed. ** Package changed: xorg (Ubuntu) => xorg-server (Ubuntu) ** Changed in: xorg-server (Ubuntu) Status: New => Won't Fix -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to xorg in Ubuntu. https://bugs.launchpad.net/bugs/1704616 Title: Display settings mess up when screens rearranged in xfce-display- settings Status in xorg-server package in Ubuntu: Won't Fix Bug description: I have a Dell 1280x1024 19" screen and Sony 1366x768 32" screen. Due to the ports they are connected to on the video card they appear by default in xfce-display-settings in the reverse to their physical layout. On previous versions of Xubuntu there has not been any problem with rearranging the display order. On artful I can only get things to work properly if I leave the display order to the default. If I try to rearrange the display order on artful all sorts of weird things happen. The 19" screen only uses two thirds of its vertical height to display the picture, the rest is drawn as white. The taskbar disappears completely. The mouse has to be on the opposite screen to the one where you are working in order to be able to click on anything. ProblemType: Bug DistroRelease: Ubuntu 17.10 Package: xorg 1:7.7+19ubuntu1 ProcVersionSignature: Ubuntu 4.10.0-26.30-generic 4.10.17 Uname: Linux 4.10.0-26-generic x86_64 ApportVersion: 2.20.5-0ubuntu5 Architecture: amd64 CurrentDesktop: XFCE Date: Sun Jul 16 16:27:49 2017 InstallationDate: Installed on 2017-07-16 (0 days ago) InstallationMedia: Xubuntu 17.10 "Artful Aardvark" - Alpha amd64 (20170704) SourcePackage: xorg Symptom: display UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg-server/+bug/1704616/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1704805] Re: All titlebars are corrupt
Thank you for reporting this bug to Ubuntu. Ubuntu 17.10 (artful) reached end-of-life on July 19, 2018. See this document for currently supported Ubuntu releases: https://wiki.ubuntu.com/Releases We appreciate that this bug may be old and you might not be interested in discussing it any more. But if you are then please upgrade to the latest Ubuntu version and re-test. If you then find the bug is still present in the newer Ubuntu version, please add a comment here telling us which new version it is in and change the bug status to Confirmed. ** Package changed: xorg (Ubuntu) => xorg-server (Ubuntu) ** Changed in: xorg-server (Ubuntu) Status: New => Won't Fix -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to xorg in Ubuntu. https://bugs.launchpad.net/bugs/1704805 Title: All titlebars are corrupt Status in xorg-server package in Ubuntu: Won't Fix Bug description: After today's artful dist-ugprade, all titlebars are corrupted. The fonts show only squares. ProblemType: Bug DistroRelease: Ubuntu 17.10 Package: xorg 1:7.7+19ubuntu1 ProcVersionSignature: Ubuntu 4.11.0-10.15-generic 4.11.8 Uname: Linux 4.11.0-10-generic x86_64 .tmp.unity_support_test.0: ApportVersion: 2.20.5-0ubuntu5 Architecture: amd64 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: None CurrentDesktop: GNOME Date: Mon Jul 17 10:49:00 2017 DistUpgraded: Fresh install DistroCodename: artful DistroVariant: ubuntu GraphicsCard: VMware SVGA II Adapter [15ad:0405] (prog-if 00 [VGA controller]) Subsystem: VMware SVGA II Adapter [15ad:0405] InstallationDate: Installed on 2016-11-07 (251 days ago) InstallationMedia: Ubuntu 17.04 "Zesty Zapus" - Alpha amd64 (20161107) Lsusb: Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Bus 002 Device 003: ID 0e0f:0002 VMware, Inc. Virtual USB Hub Bus 002 Device 002: ID 0e0f:0003 VMware, Inc. Virtual Mouse Bus 002 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub MachineType: VMware, Inc. VMware Virtual Platform ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.11.0-10-generic root=UUID=ec4bce78-74fa-43dc-af9e-b26a9a2d562a ro SourcePackage: xorg Symptom: display UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 07/02/2015 dmi.bios.vendor: Phoenix Technologies LTD dmi.bios.version: 6.00 dmi.board.name: 440BX Desktop Reference Platform dmi.board.vendor: Intel Corporation dmi.board.version: None dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 1 dmi.chassis.vendor: No Enclosure dmi.chassis.version: N/A dmi.modalias: dmi:bvnPhoenixTechnologiesLTD:bvr6.00:bd07/02/2015:svnVMware,Inc.:pnVMwareVirtualPlatform:pvrNone:rvnIntelCorporation:rn440BXDesktopReferencePlatform:rvrNone:cvnNoEnclosure:ct1:cvrN/A: dmi.product.name: VMware Virtual Platform dmi.product.version: None dmi.sys.vendor: VMware, Inc. version.compiz: compiz 1:0.9.13.1+17.10.20170704-0ubuntu1 version.ia32-libs: ia32-libs N/A version.libdrm2: libdrm2 2.4.81-2 version.libgl1-mesa-dri: libgl1-mesa-dri 17.1.2-2ubuntu2 version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A version.libgl1-mesa-glx: libgl1-mesa-glx 17.1.2-2ubuntu2 version.xserver-xorg-core: xserver-xorg-core 2:1.19.3-1ubuntu2 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.10.5-1ubuntu1 version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.9.0-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20170309-0ubuntu1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.15-2 xserver.bootTime: Tue Dec 13 11:21:08 2016 xserver.configfile: default xserver.devices: inputPower Button KEYBOARD, id 6 inputVMware VMware Virtual USB Mouse MOUSE, id 7 inputAT Translated Set 2 keyboard KEYBOARD, id 8 inputVirtualPS/2 VMware VMMouse MOUSE, id 9 inputVirtualPS/2 VMware VMMouse MOUSE, id 10 xserver.errors: No surface to present from. xserver.logfile: /var/log/Xorg.0.log xserver.outputs: Output Virtual2Virtual3Virtual4Virtual5Virtual6 Virtual7Virtual8 xserver.version: 2:1.18.4-1ubuntu7 xserver.video_driver: vmware To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg-server/+bug/1704805/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1718996] Re: Problem logging-in after switch to sddm
Thank you for reporting this bug to Ubuntu. Ubuntu 17.10 (artful) reached end-of-life on July 19, 2018. See this document for currently supported Ubuntu releases: https://wiki.ubuntu.com/Releases We appreciate that this bug may be old and you might not be interested in discussing it any more. But if you are then please upgrade to the latest Ubuntu version and re-test. If you then find the bug is still present in the newer Ubuntu version, please add a comment here telling us which new version it is in and change the bug status to Confirmed. ** Changed in: xorg (Ubuntu) Status: New => Won't Fix -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to xorg in Ubuntu. https://bugs.launchpad.net/bugs/1718996 Title: Problem logging-in after switch to sddm Status in xorg package in Ubuntu: Won't Fix Bug description: After the latest update to Lubuntu 'Next' 16.10, I was asked which display manager I would like to have. I switched from lightm to sddm but was greeted by the following message after boot-up: Xsession: unsupported number of arguments (5): falling back to default session. I desperately tried to click 'okay' but it refused to do anything. A switch to the terminal with Ctr+Alt+F1 and a dpkg-reconfigure lightm command later, my problem was 'solved' by re-enabling light-dm. I'm using auto log-on if that matters/helps. ProblemType: Bug DistroRelease: Ubuntu 17.10 Package: xorg (not installed) ProcVersionSignature: Ubuntu 4.13.0-11.12-generic 4.13.1 Uname: Linux 4.13.0-11-generic x86_64 ApportVersion: 2.20.7-0ubuntu1 Architecture: amd64 CompositorRunning: None CurrentDesktop: LXQt Date: Fri Sep 22 20:41:41 2017 DistUpgraded: Fresh install DistroCodename: artful DistroVariant: ubuntu ExtraDebuggingInterest: Yes, if not too technical GpuHangFrequency: This is the first time GraphicsCard: Intel Corporation Atom Processor Z36xxx/Z37xxx Series Graphics & Display [8086:0f31] (rev 0e) (prog-if 00 [VGA controller]) Subsystem: Acer Incorporated [ALI] Atom Processor Z36xxx/Z37xxx Series Graphics & Display [1025:0937] InstallationDate: Installed on 2017-07-02 (82 days ago) InstallationMedia: Lubuntu-Next 17.10 "Artful Aardvark" - Alpha amd64 (20170628.1) MachineType: Packard Bell Easynote ENTG71BM ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.13.0-11-generic.efi.signed root=UUID=c7bd6b27-9d6c-46d2-9b13-199930fc0f85 ro quiet splash vt.handoff=7 SourcePackage: xorg Symptom: display Title: Xorg freeze UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 10/24/2014 dmi.bios.vendor: Insyde Corp. dmi.bios.version: V1.09 dmi.board.asset.tag: Type2 - Board Asset Tag dmi.board.name: Easynote ENTG71BM dmi.board.vendor: Packard Bell dmi.board.version: V1.09 dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: Packard Bell dmi.chassis.version: V1.09 dmi.modalias: dmi:bvnInsydeCorp.:bvrV1.09:bd10/24/2014:svnPackardBell:pnEasynoteENTG71BM:pvrV1.09:rvnPackardBell:rnEasynoteENTG71BM:rvrV1.09:cvnPackardBell:ct10:cvrV1.09: dmi.product.family: BayTrail dmi.product.name: Easynote ENTG71BM dmi.product.version: V1.09 dmi.sys.vendor: Packard Bell version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.82-1 version.libgl1-mesa-dri: libgl1-mesa-dri 17.2.1-0ubuntu1 version.libgl1-mesa-glx: libgl1-mesa-glx 17.2.1-0ubuntu1 version.xserver-xorg-core: xserver-xorg-core 2:1.19.3-1ubuntu6 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.9.0-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20170309-0ubuntu1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.15-2 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1718996/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1711037] Re: Screen intermittently flickers
Thank you for reporting this bug to Ubuntu. Ubuntu 17.10 (artful) reached end-of-life on July 19, 2018. See this document for currently supported Ubuntu releases: https://wiki.ubuntu.com/Releases We appreciate that this bug may be old and you might not be interested in discussing it any more. But if you are then please upgrade to the latest Ubuntu version and re-test. If you then find the bug is still present in the newer Ubuntu version, please add a comment here telling us which new version it is in and change the bug status to Confirmed. ** Package changed: xorg (Ubuntu) => xorg-server (Ubuntu) ** Changed in: xorg-server (Ubuntu) Status: New => Won't Fix -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to xorg in Ubuntu. https://bugs.launchpad.net/bugs/1711037 Title: Screen intermittently flickers Status in xorg-server package in Ubuntu: Won't Fix Bug description: Using both my nvidia and radeon cards my 2560x1600 display flickers. The screen is fine in Windows. This only seems to happen when I run the open source driver. Additionally, if I drop that screen to a lower 16:10 resolution like 1920x1200 it goes black. ProblemType: Bug DistroRelease: Ubuntu 17.10 Package: xorg 1:7.7+19ubuntu1 ProcVersionSignature: Ubuntu 4.11.0-13.19-generic 4.11.12 Uname: Linux 4.11.0-13-generic x86_64 ApportVersion: 2.20.6-0ubuntu5 Architecture: amd64 CompositorRunning: None CurrentDesktop: GNOME Date: Tue Aug 15 22:32:41 2017 DistUpgraded: Fresh install DistroCodename: artful DistroVariant: ubuntu DkmsStatus: bbswitch, 0.8, 4.11.0-10-generic, x86_64: installed bbswitch, 0.8, 4.11.0-13-generic, x86_64: installed nvidia-384, 384.59, 4.11.0-10-generic, x86_64: installed nvidia-384, 384.59, 4.11.0-13-generic, x86_64: installed ExtraDebuggingInterest: Yes GraphicsCard: Advanced Micro Devices, Inc. [AMD/ATI] Baffin [Polaris11] [1002:67ff] (rev cf) (prog-if 00 [VGA controller]) Subsystem: Micro-Star International Co., Ltd. [MSI] Baffin [Polaris11] [1462:8a91] InstallationDate: Installed on 2017-08-07 (9 days ago) InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Alpha amd64 (20170805) MachineType: System manufacturer System Product Name ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.11.0-13-generic root=UUID=adb3a033-d515-4dfb-97d6-7c0ef12879cf ro quiet splash vt.handoff=7 SourcePackage: xorg Symptom: display UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 07/22/2010 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 1807 dmi.board.asset.tag: To Be Filled By O.E.M. dmi.board.name: P7P55D DELUXE dmi.board.vendor: ASUSTeK Computer INC. dmi.board.version: Rev 1.xx dmi.chassis.asset.tag: Asset-1234567890 dmi.chassis.type: 3 dmi.chassis.vendor: Chassis Manufacture dmi.chassis.version: Chassis Version dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr1807:bd07/22/2010:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKComputerINC.:rnP7P55DDELUXE:rvrRev1.xx:cvnChassisManufacture:ct3:cvrChassisVersion: dmi.product.name: System Product Name dmi.product.version: System Version dmi.sys.vendor: System manufacturer version.compiz: compiz N/A version.ia32-libs: ia32-libs N/A version.libdrm2: libdrm2 2.4.82-1 version.libgl1-mesa-dri: libgl1-mesa-dri 17.1.4-1ubuntu1 version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A version.libgl1-mesa-glx: libgl1-mesa-glx 17.1.4-1ubuntu1 version.xserver-xorg-core: xserver-xorg-core 2:1.19.3-1ubuntu2 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.9.0-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20170309-0ubuntu1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.15-2 xserver.bootTime: Mon Aug 14 07:40:51 2017 xserver.configfile: default xserver.errors: xserver.logfile: /var/log/Xorg.0.log xserver.outputs: xserver.version: 2:1.19.3-1ubuntu2 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg-server/+bug/1711037/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1714140] Re: Fresh OEM install, xorg failed to start after user setup was performed.
Thank you for reporting this bug to Ubuntu. Ubuntu 17.10 (artful) reached end-of-life on July 19, 2018. See this document for currently supported Ubuntu releases: https://wiki.ubuntu.com/Releases We appreciate that this bug may be old and you might not be interested in discussing it any more. But if you are then please upgrade to the latest Ubuntu version and re-test. If you then find the bug is still present in the newer Ubuntu version, please add a comment here telling us which new version it is in and change the bug status to Confirmed. ** Package changed: xorg (Ubuntu) => xorg-server (Ubuntu) ** Changed in: xorg-server (Ubuntu) Status: Confirmed => Won't Fix -- 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/1714140 Title: Fresh OEM install, xorg failed to start after user setup was performed. Status in xorg-server package in Ubuntu: Won't Fix Bug description: While testing OEM install, the live boot, vendor update boot, and boot to end user setup worked fine. After entering credentials and performing final user setup, the subsequent reboot resulted in a terminal login prompt. After logging in at the prompt, startx was required to continue the boot process. All subsequent reboots have been fine. ProblemType: Bug DistroRelease: Ubuntu 17.10 Package: xorg 1:7.7+19ubuntu1 ProcVersionSignature: Ubuntu 4.12.0-11.12-generic 4.12.5 Uname: Linux 4.12.0-11-generic x86_64 NonfreeKernelModules: nvidia_uvm nvidia ApportVersion: 2.20.6-0ubuntu7 Architecture: amd64 CurrentDesktop: KDE Date: Wed Aug 30 20:50:15 2017 InstallationDate: Installed on 2017-08-29 (2 days ago) InstallationMedia: Kubuntu 17.10 "Artful Aardvark" - Alpha amd64 (20170828.1) SourcePackage: xorg UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg-server/+bug/1714140/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1722987] Re: screen brightness control is backwards
Thank you for reporting this bug to Ubuntu. Ubuntu 17.10 (artful) reached end-of-life on July 19, 2018. See this document for currently supported Ubuntu releases: https://wiki.ubuntu.com/Releases We appreciate that this bug may be old and you might not be interested in discussing it any more. But if you are then please upgrade to the latest Ubuntu version and re-test. If you then find the bug is still present in the newer Ubuntu version, please add a comment here telling us which new version it is in and change the bug status to Confirmed. ** Package changed: xorg (Ubuntu) => linux (Ubuntu) ** Changed in: linux (Ubuntu) Status: New => Won't Fix -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to xorg in Ubuntu. https://bugs.launchpad.net/bugs/1722987 Title: screen brightness control is backwards Status in linux package in Ubuntu: Won't Fix Bug description: Increase brightness key on my keyboard (func-f3) makes the screen more dim. Decrease brightness key on my keyboard (func-f2) makes the screen more bright. The gnome-shell on-screen display of brightness is backwards also. I see on google search results that this was a problem with older kernels. I guess the problem is back / possible regression. ProblemType: Bug DistroRelease: Ubuntu 17.10 Package: xorg 1:7.7+19ubuntu2 ProcVersionSignature: Ubuntu 4.13.0-15.16-generic 4.13.4 Uname: Linux 4.13.0-15-generic x86_64 ApportVersion: 2.20.7-0ubuntu2 Architecture: amd64 CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Wed Oct 11 20:52:44 2017 DistUpgraded: Fresh install DistroCodename: artful DistroVariant: ubuntu ExtraDebuggingInterest: Yes, if not too technical GraphicsCard: Intel Corporation Atom Processor Z36xxx/Z37xxx Series Graphics & Display [8086:0f31] (rev 0e) (prog-if 00 [VGA controller]) Subsystem: Hewlett-Packard Company Atom Processor Z36xxx/Z37xxx Series Graphics & Display [103c:2209] InstallationDate: Installed on 2017-10-08 (3 days ago) InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Alpha amd64 (20170926) Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 005: ID 0cf3:3121 Atheros Communications, Inc. Bus 001 Device 003: ID 1a40:0101 Terminus Technology Inc. Hub Bus 001 Device 002: ID 05c8:036e Cheng Uei Precision Industry Co., Ltd (Foxlink) Webcam Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: Hewlett-Packard HP Pavilion 11 x360 PC ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.13.0-15-generic.efi.signed root=UUID=3db6d4f1-3d95-4b8c-93d1-ab9465947670 ro quiet splash vt.handoff=7 SourcePackage: xorg Symptom: display UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 11/11/2014 dmi.bios.vendor: Insyde dmi.bios.version: F.15 dmi.board.asset.tag: Type2 - Board Asset Tag dmi.board.name: 2209 dmi.board.vendor: Hewlett-Packard dmi.board.version: 57.37 dmi.chassis.asset.tag: Chassis Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: Hewlett-Packard dmi.chassis.version: Chassis Version dmi.modalias: dmi:bvnInsyde:bvrF.15:bd11/11/2014:svnHewlett-Packard:pnHPPavilion11x360PC:pvr096F100800405F00010420180:rvnHewlett-Packard:rn2209:rvr57.37:cvnHewlett-Packard:ct10:cvrChassisVersion: dmi.product.family: 103C_5335KV G=N L=CON B=HP S=PAV X=MIN dmi.product.name: HP Pavilion 11 x360 PC dmi.product.version: 096F100800405F00010420180 dmi.sys.vendor: Hewlett-Packard version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.83-1 version.libgl1-mesa-dri: libgl1-mesa-dri 17.2.2-0ubuntu1 version.libgl1-mesa-glx: libgl1-mesa-glx 17.2.2-0ubuntu1 version.xserver-xorg-core: xserver-xorg-core 2:1.19.3-1ubuntu7 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.10.0-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20170309-0ubuntu1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.15-2 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1722987/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1724933] Re: I can't adjust display brightness
Thank you for reporting this bug to Ubuntu. Ubuntu 17.10 (artful) reached end-of-life on July 19, 2018. See this document for currently supported Ubuntu releases: https://wiki.ubuntu.com/Releases We appreciate that this bug may be old and you might not be interested in discussing it any more. But if you are then please upgrade to the latest Ubuntu version and re-test. If you then find the bug is still present in the newer Ubuntu version, please add a comment here telling us which new version it is in and change the bug status to Confirmed. ** Package changed: xorg (Ubuntu) => ubuntu ** Changed in: ubuntu Status: Confirmed => Won't Fix -- 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/1724933 Title: I can't adjust display brightness Status in Ubuntu: Won't Fix Bug description: I'm using HP Pavilion DV6. After upgrade to Ubuntu 17.10 from 17.04 I can't adjust display brightness. when I press F2|F3 keys icon brightness appears, the controller moves but the brightness doesn't change. ProblemType: Bug DistroRelease: Ubuntu 17.10 Package: xorg 1:7.7+19ubuntu3 ProcVersionSignature: Ubuntu 4.13.0-16.19-generic 4.13.4 Uname: Linux 4.13.0-16-generic x86_64 NonfreeKernelModules: wl .tmp.unity_support_test.0: ApportVersion: 2.20.7-0ubuntu3 Architecture: amd64 CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Thu Oct 19 22:14:51 2017 DistUpgraded: 2017-10-19 21:15:33,861 DEBUG Running PostInstallScript: './xorg_fix_proprietary.py' DistroCodename: artful DistroVariant: ubuntu DkmsStatus: bcmwl, 6.30.223.271+bdcom, 4.10.0-37-generic, x86_64: installed bcmwl, 6.30.223.271+bdcom, 4.13.0-16-generic, x86_64: installed ExtraDebuggingInterest: Yes GraphicsCard: Intel Corporation 2nd Generation Core Processor Family Integrated Graphics Controller [8086:0116] (rev 09) (prog-if 00 [VGA controller]) Subsystem: Hewlett-Packard Company 2nd Generation Core Processor Family Integrated Graphics Controller [103c:3388] Advanced Micro Devices, Inc. [AMD/ATI] Whistler [Radeon HD 6730M/6770M/7690M XT] [1002:6740] (rev ff) (prog-if ff) InstallationDate: Installed on 2017-06-18 (123 days ago) InstallationMedia: Ubuntu 17.04 "Zesty Zapus" - Release amd64 (20170412) MachineType: Hewlett-Packard HP Pavilion dv6 Notebook PC ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.13.0-16-generic root=/dev/mapper/ubuntu--vg-root ro quiet splash vt.handoff=7 SourcePackage: xorg Symptom: display UpgradeStatus: Upgraded to artful on 2017-10-19 (0 days ago) dmi.bios.date: 04/25/2011 dmi.bios.vendor: Hewlett-Packard dmi.bios.version: F.13 dmi.board.asset.tag: Base Board Asset Tag dmi.board.name: 3388 dmi.board.vendor: Hewlett-Packard dmi.board.version: 10.25 dmi.chassis.asset.tag: Chassis Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: Hewlett-Packard dmi.chassis.version: Chassis Version dmi.modalias: dmi:bvnHewlett-Packard:bvrF.13:bd04/25/2011:svnHewlett-Packard:pnHPPaviliondv6NotebookPC:pvr058F1124471610100:rvnHewlett-Packard:rn3388:rvr10.25:cvnHewlett-Packard:ct10:cvrChassisVersion: dmi.product.family: 103C_5335KV G=N L=CON B=HP S=PAV dmi.product.name: HP Pavilion dv6 Notebook PC dmi.product.version: 058F1124471610100 dmi.sys.vendor: Hewlett-Packard version.compiz: compiz 1:0.9.13.1+17.10.20170901-0ubuntu1 version.libdrm2: libdrm2 2.4.83-1 version.libgl1-mesa-dri: libgl1-mesa-dri 17.2.2-0ubuntu1 version.libgl1-mesa-glx: libgl1-mesa-glx 17.2.2-0ubuntu1 version.xserver-xorg-core: xserver-xorg-core 2:1.19.5-0ubuntu2 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.10.0-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20170309-0ubuntu1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.15-2 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+bug/1724933/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1724307] Re: [Dell XPS 13 9360] Mouse cursor flickers with one external monitor connected via HDMI+Wavlink WL-UG39DK1V
** Package changed: xorg (Ubuntu) => xorg-server (Ubuntu) ** Tags removed: artful zesty -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to xorg in Ubuntu. https://bugs.launchpad.net/bugs/1724307 Title: [Dell XPS 13 9360] Mouse cursor flickers with one external monitor connected via HDMI+Wavlink WL-UG39DK1V Status in xorg-server package in Ubuntu: Triaged Bug description: When I connect my laptop to my DisplayLink based device with USB (Wavlink universal USB 3.0 docking station https://www.wavlink.com/en/product/150 WL-UG39DK1V), and connect the Wavlink to my AOC E2775SJ Monitor via HDMI, the mouse icon flickers as per the following video: https://launchpadlibrarian.net/346625588/20171121_131417.mp4 Only if the mouse is on the laptop monitor, it can vanish for several minutes, but remains active. Animations/overlays or typing inside a Chrome window causes the mouse pointer to flicker more often. If there is no interaction or animation, the mouse pointer remains static and drawn. Monitor 1: 1920 x 1080 - Laptop's Native Monitor Monitor 2: 1920 x 1080 - DisplayLink (USB) connected AOC E2775SJ Monitor This issue doesn't happen if I don't connect my laptop to an external monitor via the Wavlink device. This issue is reproducible with DisplayLink driver 1.4, and 1.3.54. This issue is reproducible with Ubuntu 16.04, 17.04, and 17.10 x64. I've reported this to DisplayLink via: https://displaylink.org/forum/showthread.php?p=84713#post84713 WORKAROUND: Use GNOME Flashback (Metacity) session. WORKAROUND: In the GUI go to All Settings > Screen Display > for the primary monitor change Rotation from Normal to any of the following: Clockwise Anti-clockwise 180 degrees ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: xorg 1:7.7+13ubuntu3 ProcVersionSignature: Ubuntu 4.10.0-37.41~16.04.1-generic 4.10.17 Uname: Linux 4.10.0-37-generic x86_64 .tmp.unity_support_test.0: ApportVersion: 2.20.1-0ubuntu2.10 Architecture: amd64 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: compiz CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0' CompositorUnredirectFSW: true CurrentDesktop: Unity Date: Tue Oct 17 10:01:55 2017 DistUpgraded: Fresh install DistroCodename: xenial DistroVariant: ubuntu ExtraDebuggingInterest: Yes, if not too technical GraphicsCard: Intel Corporation Device [8086:5917] (rev 07) (prog-if 00 [VGA controller]) Subsystem: Dell Device [1028:082a] InstallationDate: Installed on 2017-10-16 (0 days ago) InstallationMedia: Ubuntu 16.04.3 LTS "Xenial Xerus" - Release amd64 (20170801) MachineType: Dell Inc. XPS 13 9360 ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.10.0-37-generic.efi.signed root=/dev/mapper/ubuntu--vg-root ro quiet splash vt.handoff=7 SourcePackage: xorg UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 08/18/2017 dmi.bios.vendor: Dell Inc. dmi.bios.version: 2.2.1 dmi.board.name: 05FPM2 dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 9 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr2.2.1:bd08/18/2017:svnDellInc.:pnXPS139360:pvr:rvnDellInc.:rn05FPM2:rvrA00:cvnDellInc.:ct9:cvr: dmi.product.name: XPS 13 9360 dmi.sys.vendor: Dell Inc. version.compiz: compiz 1:0.9.12.2+16.04.20160823-0ubuntu1 version.ia32-libs: ia32-libs N/A version.libdrm2: libdrm2 2.4.76-1~ubuntu16.04.1 version.libgl1-mesa-dri: libgl1-mesa-dri 17.0.7-0ubuntu0.16.04.2 version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A version.libgl1-mesa-glx: libgl1-mesa-glx 17.0.7-0ubuntu0.16.04.2 version.xserver-xorg-core: xserver-xorg-core N/A version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati N/A version.xserver-xorg-video-intel: xserver-xorg-video-intel N/A version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau N/A xserver.bootTime: Tue Oct 17 09:39:15 2017 xserver.configfile: default xserver.errors: modeset(G0): glamor initialization failed xserver.logfile: /var/log/Xorg.0.log xserver.outputs: product id5193 vendor SHP xserver.version: 2:1.19.3-1ubuntu1~16.04.3 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg-server/+bug/1724307/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1722974] Re: Wayland xorg not scalling screens properly
Thank you for reporting this bug to Ubuntu. Ubuntu 17.10 (artful) reached end-of-life on July 19, 2018. See this document for currently supported Ubuntu releases: https://wiki.ubuntu.com/Releases We appreciate that this bug may be old and you might not be interested in discussing it any more. But if you are then please upgrade to the latest Ubuntu version and re-test. If you then find the bug is still present in the newer Ubuntu version, please add a comment here telling us which new version it is in and change the bug status to Confirmed. ** Package changed: xorg (Ubuntu) => gnome-shell (Ubuntu) ** Changed in: gnome-shell (Ubuntu) Status: New => Won't Fix -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to xorg in Ubuntu. https://bugs.launchpad.net/bugs/1722974 Title: Wayland xorg not scalling screens properly Status in gnome-shell package in Ubuntu: Won't Fix Bug description: When I try scale the screen on my xps 15 9560 core i7 screen 4k the image start to flap and sometimes the screen stay all black. I tried use the nvidia driver but still doesn't work and when I try scale using the settings option, the button "apply" disapear. Additional monitor used: Dell U2715Hc with 2K resolution. ProblemType: Bug DistroRelease: Ubuntu 17.10 Package: xorg 1:7.7+19ubuntu2 ProcVersionSignature: Ubuntu 4.13.0-15.16-generic 4.13.4 Uname: Linux 4.13.0-15-generic x86_64 NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia .proc.driver.nvidia.gpus..01.00.0: Error: [Errno 21] Is a directory: '/proc/driver/nvidia/gpus/:01:00.0' .proc.driver.nvidia.registry: Binary: "" .proc.driver.nvidia.version: NVRM version: NVIDIA UNIX x86_64 Kernel Module 384.90 Tue Sep 19 19:17:35 PDT 2017 GCC version: gcc version 7.2.0 (Ubuntu 7.2.0-8ubuntu2) ApportVersion: 2.20.7-0ubuntu2 Architecture: amd64 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Thu Oct 12 12:50:54 2017 DistUpgraded: Fresh install DistroCodename: artful DistroVariant: ubuntu ExtraDebuggingInterest: Yes GraphicsCard: Intel Corporation Device [8086:591b] (rev 04) (prog-if 00 [VGA controller]) Subsystem: Dell Device [1028:07be] Subsystem: Dell GP107M [GeForce GTX 1050 Mobile] [1028:07be] InstallationDate: Installed on 2017-10-10 (1 days ago) InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Alpha amd64 (20170926) MachineType: Dell Inc. XPS 15 9560 ProcEnviron: LANGUAGE=en_AU:en PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_AU.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.13.0-15-generic root=UUID=cdd76ef8-2ee7-4962-b264-6671cf81976b ro quiet splash vt.handoff=7 SourcePackage: xorg UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 08/30/2017 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.5.0 dmi.board.name: 05FFDN dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 10 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr1.5.0:bd08/30/2017:svnDellInc.:pnXPS159560:pvr:rvnDellInc.:rn05FFDN:rvrA00:cvnDellInc.:ct10:cvr: dmi.product.family: XPS dmi.product.name: XPS 15 9560 dmi.sys.vendor: Dell Inc. version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.83-1 version.libgl1-mesa-dri: libgl1-mesa-dri 17.2.2-0ubuntu1 version.libgl1-mesa-glx: libgl1-mesa-glx 17.2.2-0ubuntu1 version.nvidia-graphics-drivers: nvidia-graphics-drivers-* N/A version.xserver-xorg-core: xserver-xorg-core 2:1.19.3-1ubuntu7 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.10.0-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20170309-0ubuntu1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.15-2 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1722974/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1723766] Re: online account addition broken in KDE
Thank you for reporting this bug to Ubuntu. Ubuntu 17.10 (artful) reached end-of-life on July 19, 2018. See this document for currently supported Ubuntu releases: https://wiki.ubuntu.com/Releases We appreciate that this bug may be old and you might not be interested in discussing it any more. But if you are then please upgrade to the latest Ubuntu version and re-test. If you then find the bug is still present in the newer Ubuntu version, please add a comment here telling us which new version it is in and change the bug status to Confirmed. ** Package changed: xorg (Ubuntu) => ubuntu ** Changed in: ubuntu Status: New => Won't Fix -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to xorg in Ubuntu. https://bugs.launchpad.net/bugs/1723766 Title: online account addition broken in KDE Status in Ubuntu: Won't Fix Bug description: When trying to create a google account, I get an error dialog with the following message- "There was an error while trying to process the request: userActionFinished error: 2" When adding twitter account, NOTHING happens- it does nothing but no errror messages. Seems to be in a loop until I kill the window. ProblemType: Bug DistroRelease: Ubuntu 17.10 Package: xorg 1:7.7+19ubuntu3 ProcVersionSignature: Ubuntu 4.13.0-15.16-generic 4.13.4 Uname: Linux 4.13.0-15-generic x86_64 ApportVersion: 2.20.7-0ubuntu3 Architecture: amd64 CompositorRunning: None CurrentDesktop: KDE Date: Sun Oct 15 13:37:48 2017 DistUpgraded: Fresh install DistroCodename: artful DistroVariant: kubuntu EcryptfsInUse: Yes ExtraDebuggingInterest: I just need to know a workaround GraphicsCard: Advanced Micro Devices, Inc. [AMD/ATI] Carrizo [1002:9874] (rev ca) (prog-if 00 [VGA controller]) Subsystem: Hewlett-Packard Company Carrizo [103c:823c] InstallationDate: Installed on 2017-10-06 (9 days ago) InstallationMedia: Kubuntu 17.10 "Artful Aardvark" - Alpha amd64 (20170926) MachineType: HP HP ProBook 455 G4 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.13.0-15-generic.efi.signed root=UUID=4e60dd5c-ac20-4521-954d-ada9641962e4 ro quiet splash vt.handoff=7 SourcePackage: xorg Symptom: display UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 06/09/2017 dmi.bios.vendor: HP dmi.bios.version: P84 Ver. 01.04 dmi.board.name: 823C dmi.board.vendor: HP dmi.board.version: KBC Version 37.65 dmi.chassis.asset.tag: 5CD7376NFH dmi.chassis.type: 10 dmi.chassis.vendor: HP dmi.modalias: dmi:bvnHP:bvrP84Ver.01.04:bd06/09/2017:svnHP:pnHPProBook455G4:pvr:rvnHP:rn823C:rvrKBCVersion37.65:cvnHP:ct10:cvr: dmi.product.family: 103C_5336AN HP ProBook dmi.product.name: HP ProBook 455 G4 dmi.sys.vendor: HP version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.83-1 version.libgl1-mesa-dri: libgl1-mesa-dri 17.2.2-0ubuntu1 version.libgl1-mesa-glx: libgl1-mesa-glx 17.2.2-0ubuntu1 version.xserver-xorg-core: xserver-xorg-core 2:1.19.4-1ubuntu2 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.10.0-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20170309-0ubuntu1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.15-2 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+bug/1723766/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1724610] Re: Logitech G15 keyboard non-responsive in GUI
Thank you for reporting this bug to Ubuntu. Ubuntu 17.10 (artful) reached end-of-life on July 19, 2018. See this document for currently supported Ubuntu releases: https://wiki.ubuntu.com/Releases We appreciate that this bug may be old and you might not be interested in discussing it any more. But if you are then please upgrade to the latest Ubuntu version and re-test. If you then find the bug is still present in the newer Ubuntu version, please add a comment here telling us which new version it is in and change the bug status to Confirmed. ** Package changed: xorg (Ubuntu) => ubuntu ** Changed in: ubuntu Status: New => Won't Fix -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to xorg in Ubuntu. https://bugs.launchpad.net/bugs/1724610 Title: Logitech G15 keyboard non-responsive in GUI Status in Ubuntu: Won't Fix Bug description: Two people have determined (independently) that upon upgrading to 17.10, their keyboards no longer respond once past the login to the X-11 environment. Upon further experimentation, using a different keyboard corrects the issue, as does performing a suspend and resume after login. This has been an issue for months, not newly introduced. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+bug/1724610/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1713628] Re: [Elecom M-TC01DBM] Unable to remap gesture
Thank you for reporting this bug to Ubuntu. Ubuntu 17.10 (artful) reached end-of-life on July 19, 2018. See this document for currently supported Ubuntu releases: https://wiki.ubuntu.com/Releases We appreciate that this bug may be old and you might not be interested in discussing it any more. But if you are then please upgrade to the latest Ubuntu version and re-test. If you then find the bug is still present in the newer Ubuntu version, please add a comment here telling us which new version it is in and change the bug status to Confirmed. ** Changed in: xorg (Ubuntu) Status: New => Won't Fix -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to xorg in Ubuntu. https://bugs.launchpad.net/bugs/1713628 Title: [Elecom M-TC01DBM] Unable to remap gesture Status in xorg package in Ubuntu: Won't Fix Bug description: I have wireless touch mouse. Partially it detected as a keyboard, and i can't remap this gesture. This gesture has defined combination, but I want to change them. --- ApportVersion: 2.20.7-0ubuntu3.7 Architecture: amd64 CurrentDesktop: Unity:Unity7:ubuntu DistUpgraded: 2017-10-22 03:24:40,960 DEBUG Running PostInstallScript: './xorg_fix_proprietary.py' DistroCodename: artful DistroRelease: Ubuntu 17.10 DistroVariant: ubuntu InstallationDate: Installed on 2017-04-19 (299 days ago) InstallationMedia: Ubuntu 17.04 "Zesty Zapus" - Release amd64 (20170412) MachineType: ASUS All Series Package: xorg 1:7.7+19ubuntu3 PackageArchitecture: amd64 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.13.0-32-generic root=UUID=de0c719d-9c77-4098-be9a-79519000f93e ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 4.13.0-32.35-generic 4.13.13 Tags: artful ubuntu Uname: Linux 4.13.0-32-generic x86_64 UpgradeStatus: Upgraded to artful on 2017-10-22 (114 days ago) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo vboxusers _MarkForUpload: True dmi.bios.date: 01/13/2017 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 3505 dmi.board.asset.tag: Default string dmi.board.name: X99-A dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: Rev 1.xx dmi.chassis.asset.tag: Default string dmi.chassis.type: 3 dmi.chassis.vendor: Default string dmi.chassis.version: Default string dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr3505:bd01/13/2017:svnASUS:pnAllSeries:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnX99-A:rvrRev1.xx:cvnDefaultstring:ct3:cvrDefaultstring: dmi.product.family: ASUS MB dmi.product.name: All Series dmi.product.version: System Version dmi.sys.vendor: ASUS version.compiz: compiz 1:0.9.13.1+17.10.20170901-0ubuntu1 version.libdrm2: libdrm2 2.4.83-1 version.libgl1-mesa-dri: libgl1-mesa-dri 17.2.4-0ubuntu1~17.10.2 version.libgl1-mesa-glx: libgl1-mesa-glx 17.2.4-0ubuntu1~17.10.2 version.xserver-xorg-core: xserver-xorg-core 2:1.19.5-0ubuntu2 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.10.0-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20170309-0ubuntu1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.15-2 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1713628/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1812150] [NEW] qhelpgenerator and qcollectiongenerator will not run
Public bug reported: I have qttols5-dev-tools installed, which provides a qthelpgenerator implementation. But when I try to run qhelpgenerator (or qcollectiongenerator) through their usual /usr/bin shims, it errors out: janke@ubuntu:~/local/repos/octave-addons-chrono/doc$ dpkg -S /usr/lib/x86_64-linux-gnu/qt5/bin/qhelpgenerator qttools5-dev-tools: /usr/lib/x86_64-linux-gnu/qt5/bin/qhelpgenerator janke@ubuntu:~/local/repos/octave-addons-chrono/doc$ ls -l /usr/lib/x86_64-linux-gnu/qt5/bin/qhelpgenerator lrwxrwxrwx 1 root root 31 Apr 14 2018 /usr/lib/x86_64-linux-gnu/qt5/bin/qhelpgenerator -> ../../../qt5/bin/qhelpgenerator janke@ubuntu:~/local/repos/octave-addons-chrono/doc$ which qhelpgenerator /usr/bin/qhelpgenerator janke@ubuntu:~/local/repos/octave-addons-chrono/doc$ ls -l /usr/bin/qhelpgenerator lrwxrwxrwx 1 root root 9 Dec 21 2017 /usr/bin/qhelpgenerator -> qtchooser janke@ubuntu:~/local/repos/octave-addons-chrono/doc$ qhelpgenerator -v qhelpgenerator: could not find a Qt installation of '' janke@ubuntu:~/local/repos/octave-addons-chrono/doc$ qcollectiongenerator -v qcollectiongenerator: could not find a Qt installation of '' janke@ubuntu:~/local/repos/octave-addons-chrono/doc$ Running them directly works: janke@ubuntu:~/local/repos/octave-addons-chrono/doc$ /usr/lib/x86_64-linux-gnu/qt5/bin/qhelpgenerator -v Qt Help Generator version 1.0 (Qt 5.9.5) janke@ubuntu:~/local/repos/octave-addons-chrono/doc$ /usr/lib/x86_64-linux-gnu/qt5/bin/qcollectiongenerator -v Qt Collection Generator version 1.0 (Qt 5.9.5) But most software will locate the /usr/bin shims instead of this actual binary. Looks like a problem with qtchooser? ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: qtchooser 64-ga1b6736-5 ProcVersionSignature: Ubuntu 4.15.0-29.31-generic 4.15.18 Uname: Linux 4.15.0-29-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.2 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Wed Jan 16 20:00:43 2019 Dependencies: gcc-8-base 8.2.0-1ubuntu2~18.04 libc6 2.27-3ubuntu1 libgcc1 1:8.2.0-1ubuntu2~18.04 libstdc++6 8.2.0-1ubuntu2~18.04 InstallationDate: Installed on 2019-01-15 (1 days ago) InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 (20180725) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: qtchooser UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: qtchooser (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug bionic -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to qtchooser in Ubuntu. https://bugs.launchpad.net/bugs/1812150 Title: qhelpgenerator and qcollectiongenerator will not run Status in qtchooser package in Ubuntu: New Bug description: I have qttols5-dev-tools installed, which provides a qthelpgenerator implementation. But when I try to run qhelpgenerator (or qcollectiongenerator) through their usual /usr/bin shims, it errors out: janke@ubuntu:~/local/repos/octave-addons-chrono/doc$ dpkg -S /usr/lib/x86_64-linux-gnu/qt5/bin/qhelpgenerator qttools5-dev-tools: /usr/lib/x86_64-linux-gnu/qt5/bin/qhelpgenerator janke@ubuntu:~/local/repos/octave-addons-chrono/doc$ ls -l /usr/lib/x86_64-linux-gnu/qt5/bin/qhelpgenerator lrwxrwxrwx 1 root root 31 Apr 14 2018 /usr/lib/x86_64-linux-gnu/qt5/bin/qhelpgenerator -> ../../../qt5/bin/qhelpgenerator janke@ubuntu:~/local/repos/octave-addons-chrono/doc$ which qhelpgenerator /usr/bin/qhelpgenerator janke@ubuntu:~/local/repos/octave-addons-chrono/doc$ ls -l /usr/bin/qhelpgenerator lrwxrwxrwx 1 root root 9 Dec 21 2017 /usr/bin/qhelpgenerator -> qtchooser janke@ubuntu:~/local/repos/octave-addons-chrono/doc$ qhelpgenerator -v qhelpgenerator: could not find a Qt installation of '' janke@ubuntu:~/local/repos/octave-addons-chrono/doc$ qcollectiongenerator -v qcollectiongenerator: could not find a Qt installation of '' janke@ubuntu:~/local/repos/octave-addons-chrono/doc$ Running them directly works: janke@ubuntu:~/local/repos/octave-addons-chrono/doc$ /usr/lib/x86_64-linux-gnu/qt5/bin/qhelpgenerator -v Qt Help Generator version 1.0 (Qt 5.9.5) janke@ubuntu:~/local/repos/octave-addons-chrono/doc$ /usr/lib/x86_64-linux-gnu/qt5/bin/qcollectiongenerator -v Qt Collection Generator version 1.0 (Qt 5.9.5) But most software will locate the /usr/bin shims instead of this actual binary. Looks like a problem with qtchooser? ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: qtchooser 64-ga1b6736-5 ProcVersionSignature: Ubuntu 4.15.0-29.31-generic 4.15.18 Uname: Linux 4.15.0-29-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.2 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Wed Jan 16 20:00:43 2019 Dependencies: gcc-8-base 8.2.0-1ubuntu2~18.04 libc6 2.27-3ubuntu1 libgcc1 1:8.2.0-1ubuntu2~18.04 libstdc++6 8.2.0-1ubuntu2~18.04 I
[Touch-packages] [Bug 1812143] Re: gsettings-desktop-schemas 3.31 breaks mutter 3.30
** Description changed: We need to package mutter 3.31 and add a Breaks: mutter < 3.31 to gsettings-desktop-schemas. Running gsettings-desktop-schemas 3.31 with mutter 3.30 will result in gdm/gnome-shell being unable to start. Also, ukwm is a fork of mutter so the Kylin devs need to backport the relevant commits from mutter. The problematic gsettings commit was: https://gitlab.gnome.org/GNOME/gsettings-desktop-schemas/commit/c7eee129c I think the mutter commits can be found at https://gitlab.gnome.org/GNOME/mutter/merge_requests/133 + + We could easily add a dummy key with the old name but I'm thinking the + way forward is just to package the newer mutter. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to gsettings-desktop-schemas in Ubuntu. https://bugs.launchpad.net/bugs/1812143 Title: gsettings-desktop-schemas 3.31 breaks mutter 3.30 Status in gsettings-desktop-schemas package in Ubuntu: Triaged Status in mutter package in Ubuntu: Triaged Status in ukwm package in Ubuntu: New Bug description: We need to package mutter 3.31 and add a Breaks: mutter < 3.31 to gsettings-desktop-schemas. Running gsettings-desktop-schemas 3.31 with mutter 3.30 will result in gdm/gnome-shell being unable to start. Also, ukwm is a fork of mutter so the Kylin devs need to backport the relevant commits from mutter. The problematic gsettings commit was: https://gitlab.gnome.org/GNOME/gsettings-desktop-schemas/commit/c7eee129c I think the mutter commits can be found at https://gitlab.gnome.org/GNOME/mutter/merge_requests/133 We could easily add a dummy key with the old name but I'm thinking the way forward is just to package the newer mutter. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gsettings-desktop-schemas/+bug/1812143/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1521989] Re: Please remove libzeitgeist from the archive
** Description changed: libzeitgeist-1.0-1 is superseded by libzeitgeist-2.0-0 which is built by zeitgeist with a slightly different API. All rpdends must transition to it: - nautilus, unity-china-video-scope, unity-lens-applications, unity-lens-video, unity-scope-video-remote + unity-china-video-scope, unity-lens-applications, unity-lens-video -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to libzeitgeist in Ubuntu. https://bugs.launchpad.net/bugs/1521989 Title: Please remove libzeitgeist from the archive Status in libzeitgeist package in Ubuntu: New Bug description: libzeitgeist-1.0-1 is superseded by libzeitgeist-2.0-0 which is built by zeitgeist with a slightly different API. All rpdends must transition to it: unity-china-video-scope, unity-lens-applications, unity-lens-video To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libzeitgeist/+bug/1521989/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1811999] Re: [USB-Audio - Audioengine D3, playback] fails after a while (a second)
Maybe it works in that other system because 18.10 contains some bug fix that is missing from your first system (that is 18.04). I think more likely though it's just that your first system physically isn't maintaining a clean USB connection. If that's a software problem then this is a kernel bug but it sounds more like a hardware problem to me: [ 5937.978117] usb 1-1.4.2: USB disconnect, device number 16 Please try a different USB port, and/or a different machine that is running 18.04 rather than 18.10. ** Package changed: alsa-driver (Ubuntu) => linux (Ubuntu) ** Changed in: linux (Ubuntu) Status: New => Incomplete -- 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/1811999 Title: [USB-Audio - Audioengine D3, playback] fails after a while (a second) Status in linux package in Ubuntu: Incomplete Bug description: USB DAC stops playing sound after a second. I had problem with kernel 4.15. So, I tried upgrading to 4.19 but still issue persists. I think, we might need to add it to sound/usb/quirks.c I see following in dmesg [ 5937.978117] usb 1-1.4.2: USB disconnect, device number 16 [ 5955.721597] usb 1-1.4.1: new full-speed USB device number 17 using xhci_hcd [ 5956.302910] usb 1-1.4.1: New USB device found, idVendor=2912, idProduct=120b, bcdDevice= 1.0c [ 5956.302917] usb 1-1.4.1: New USB device strings: Mfr=1, Product=2, SerialNumber=3 [ 5956.302921] usb 1-1.4.1: Product: Audioengine D3 [ 5956.302926] usb 1-1.4.1: Manufacturer: Audioengine [ 5956.302929] usb 1-1.4.1: SerialNumber: Audioengine [ 5956.320621] usb 1-1.4.1: 1:1: cannot get freq at ep 0x1 [ 5956.920844] usb 1-1.4.1: 1:1: cannot get freq at ep 0x1 [ 5956.938929] usb 1-1.4.1: 1:1: cannot get freq at ep 0x1 And lsusb -v has following entry for the device. Bus 001 Device 017: ID 2912:120b Couldn't open device, some information will be missing Device Descriptor: bLength18 bDescriptorType 1 bcdUSB 1.00 bDeviceClass0 (Defined at Interface level) bDeviceSubClass 0 bDeviceProtocol 0 bMaxPacketSize0 8 idVendor 0x2912 idProduct 0x120b bcdDevice1.0c iManufacturer 1 iProduct2 iSerial 3 bNumConfigurations 1 Configuration Descriptor: bLength 9 bDescriptorType 2 wTotalLength 131 bNumInterfaces 2 bConfigurationValue 1 iConfiguration 0 bmAttributes 0x80 (Bus Powered) MaxPower 200mA Interface Descriptor: bLength 9 bDescriptorType 4 bInterfaceNumber0 bAlternateSetting 0 bNumEndpoints 0 bInterfaceClass 1 Audio bInterfaceSubClass 1 Control Device bInterfaceProtocol 0 iInterface 0 AudioControl Interface Descriptor: bLength 9 bDescriptorType36 bDescriptorSubtype 1 (HEADER) bcdADC 1.00 wTotalLength 43 bInCollection 1 baInterfaceNr( 0) 1 AudioControl Interface Descriptor: bLength12 bDescriptorType36 bDescriptorSubtype 2 (INPUT_TERMINAL) bTerminalID 5 wTerminalType 0x0101 USB Streaming bAssocTerminal 0 bNrChannels 2 wChannelConfig 0x0003 Left Front (L) Right Front (R) iChannelNames 0 iTerminal 0 AudioControl Interface Descriptor: bLength13 bDescriptorType36 bDescriptorSubtype 6 (FEATURE_UNIT) bUnitID 7 bSourceID 5 bControlSize2 bmaControls( 0) 0x01 bmaControls( 0) 0x00 Mute Control bmaControls( 1) 0x02 bmaControls( 1) 0x00 Volume Control bmaControls( 2) 0x02 bmaControls( 2) 0x00 Volume Control iFeature0 AudioControl Interface Descriptor: bLength 9 bDescriptorType36 bDescriptorSubtype 3 (OUTPUT_TERMINAL) bTerminalID 8 wTerminalType 0x0301 Speaker bAssocTerminal 0 bSourceID 7 iTerminal 0 Interface Descriptor: bLength 9 bDescriptorType
[Touch-packages] [Bug 1812143] [NEW] gsettings-desktop-schemas 3.31 breaks mutter 3.30
Public bug reported: We need to package mutter 3.31 and add a Breaks: mutter < 3.31 to gsettings-desktop-schemas. Running gsettings-desktop-schemas 3.31 with mutter 3.30 will result in gdm/gnome-shell being unable to start. Also, ukwm is a fork of mutter so the Kylin devs need to backport the relevant commits from mutter. The problematic gsettings commit was: https://gitlab.gnome.org/GNOME/gsettings-desktop-schemas/commit/c7eee129c I think the mutter commits can be found at https://gitlab.gnome.org/GNOME/mutter/merge_requests/133 ** Affects: gsettings-desktop-schemas (Ubuntu) Importance: High Status: Triaged ** Affects: mutter (Ubuntu) Importance: High Status: Triaged ** Affects: ukwm (Ubuntu) Importance: High Status: New ** Tags: block-proposed disco ** Changed in: gsettings-desktop-schemas (Ubuntu) Status: New => Triaged ** Also affects: mutter (Ubuntu) Importance: Undecided Status: New ** Changed in: mutter (Ubuntu) Importance: Undecided => High ** Changed in: mutter (Ubuntu) Status: New => Triaged ** Also affects: ukwm (Ubuntu) Importance: Undecided Status: New ** Changed in: ukwm (Ubuntu) Importance: Undecided => High -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to gsettings-desktop-schemas in Ubuntu. https://bugs.launchpad.net/bugs/1812143 Title: gsettings-desktop-schemas 3.31 breaks mutter 3.30 Status in gsettings-desktop-schemas package in Ubuntu: Triaged Status in mutter package in Ubuntu: Triaged Status in ukwm package in Ubuntu: New Bug description: We need to package mutter 3.31 and add a Breaks: mutter < 3.31 to gsettings-desktop-schemas. Running gsettings-desktop-schemas 3.31 with mutter 3.30 will result in gdm/gnome-shell being unable to start. Also, ukwm is a fork of mutter so the Kylin devs need to backport the relevant commits from mutter. The problematic gsettings commit was: https://gitlab.gnome.org/GNOME/gsettings-desktop-schemas/commit/c7eee129c I think the mutter commits can be found at https://gitlab.gnome.org/GNOME/mutter/merge_requests/133 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gsettings-desktop-schemas/+bug/1812143/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1811979] Re: My bluetooth is not working since i am using ubuntu 18.04, it works fine in windows 7
It appears that you do have Bluetooth hardware (Ralink corp. RT3290), but it is turned off: 2: hp-bluetooth: Bluetooth Soft blocked: yes Hard blocked: no Maybe it's staying off because the kernel driver isn't up to scratch yet in 18.04, or missing firmware. To test this theory please try installing a newer kernel from: https://kernel.ubuntu.com/~kernel-ppa/mainline/?C=N;O=D ** Summary changed: - My bluetooth is not working since i am using ubuntu 14.04,it works fine in windows 7 + My bluetooth is not working since i am using ubuntu 18.04, it works fine in windows 7 ** Also affects: linux (Ubuntu) Importance: Undecided Status: New ** Changed in: bluez (Ubuntu) Status: New => Invalid ** Changed in: linux (Ubuntu) Status: New => Incomplete ** Summary changed: - My bluetooth is not working since i am using ubuntu 18.04, it works fine in windows 7 + My bluetooth (RT3290) is not working since i am using ubuntu 18.04, it works fine in windows 7 -- 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/1811979 Title: My bluetooth (RT3290) is not working since i am using ubuntu 18.04, it works fine in windows 7 Status in bluez package in Ubuntu: Invalid Status in linux package in Ubuntu: Incomplete Bug description: bluetooth network in my ubuntu is not working.actually the on button in the setting does not turn bluetooth button in to ON, it remains OFF even if i click on it.i already installed bluez and blueman . i am using this version of ubuntu Description:Ubuntu 18.04.1 LTS Release:18.04 ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: bluetooth (not installed) ProcVersionSignature: Ubuntu 4.15.0-43.46-generic 4.15.18 Uname: Linux 4.15.0-43-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.5 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Wed Jan 16 15:10:56 2019 InterestingModules: bluetooth MachineType: Hewlett-Packard HP 15 Notebook PC ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-43-generic root=UUID=1a5a1726-0948-424a-a01e-de88efc704ca ro quiet splash vt.handoff=1 SourcePackage: bluez UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 05/21/2014 dmi.bios.vendor: Insyde dmi.bios.version: F.18 dmi.board.asset.tag: Type2 - Board Asset Tag dmi.board.name: 226E dmi.board.vendor: Hewlett-Packard dmi.board.version: 74.19 dmi.chassis.asset.tag: Chassis Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: Hewlett-Packard dmi.chassis.version: Chassis Version dmi.modalias: dmi:bvnInsyde:bvrF.18:bd05/21/2014:svnHewlett-Packard:pnHP15NotebookPC:pvr0991100600087:rvnHewlett-Packard:rn226E:rvr74.19:cvnHewlett-Packard:ct10:cvrChassisVersion: dmi.product.family: 103C_5335KV G=N L=CON B=HP S=PAV dmi.product.name: HP 15 Notebook PC dmi.product.version: 0991100600087 dmi.sys.vendor: Hewlett-Packard hciconfig: To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/1811979/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1811902] Re: Echo cancelation should be enabled by default
Yes in that case it sounds like a potential enhancement request that Firefox or other apps using PulseAudio could implement. -- 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/1811902 Title: Echo cancelation should be enabled by default Status in pulseaudio package in Ubuntu: Opinion Bug description: Echo cancellation is a basic feature for anything where you are using a video or audio conference. According to instructions like these: https://bugs.launchpad.net/elementaryos/+bug/1682253 https://wiki.archlinux.org/index.php/PulseAudio/Troubleshooting#Enable_Echo/Noise-Cancellation https://medium.com/@tim_73574/ubuntu-microphone-noise-cancellation-and-volume-auto-adjusted-issue-2c79678542bb There is now enough support in pulseaudio to do this well, but it's just not enabled by default. Users shouldn't need to fish around for strange things to add to config files. More complete defaults should be included. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: pulseaudio 1:11.1-1ubuntu7.1 ProcVersionSignature: Ubuntu 4.15.0-43.46-generic 4.15.18 Uname: Linux 4.15.0-43-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.5 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/pcmC0D0p: pedrocr2684 F...m pulseaudio /dev/snd/controlC0: pedrocr2684 F pulseaudio CurrentDesktop: ubuntu:GNOME Date: Tue Jan 15 23:45:10 2019 InstallationDate: Installed on 2018-05-31 (229 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426) SourcePackage: pulseaudio UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 03/22/2018 dmi.bios.vendor: LENOVO dmi.bios.version: N1CET66W (1.34 ) dmi.board.asset.tag: Not Available dmi.board.name: 20FAS5TS00 dmi.board.vendor: LENOVO dmi.board.version: SDK0J40697 WIN dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: None dmi.modalias: dmi:bvnLENOVO:bvrN1CET66W(1.34):bd03/22/2018:svnLENOVO:pn20FAS5TS00:pvrThinkPadT460s:rvnLENOVO:rn20FAS5TS00:rvrSDK0J40697WIN:cvnLENOVO:ct10:cvrNone: dmi.product.family: ThinkPad T460s dmi.product.name: 20FAS5TS00 dmi.product.version: ThinkPad T460s dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1811902/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1811902] Re: Echo cancelation should be enabled by default
Yes in that case it sounds like an potential enhancement request that Firefox or other apps using PulseAudio could implement. ** Changed in: pulseaudio (Ubuntu) Status: Incomplete => Opinion -- 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/1811902 Title: Echo cancelation should be enabled by default Status in pulseaudio package in Ubuntu: Opinion Bug description: Echo cancellation is a basic feature for anything where you are using a video or audio conference. According to instructions like these: https://bugs.launchpad.net/elementaryos/+bug/1682253 https://wiki.archlinux.org/index.php/PulseAudio/Troubleshooting#Enable_Echo/Noise-Cancellation https://medium.com/@tim_73574/ubuntu-microphone-noise-cancellation-and-volume-auto-adjusted-issue-2c79678542bb There is now enough support in pulseaudio to do this well, but it's just not enabled by default. Users shouldn't need to fish around for strange things to add to config files. More complete defaults should be included. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: pulseaudio 1:11.1-1ubuntu7.1 ProcVersionSignature: Ubuntu 4.15.0-43.46-generic 4.15.18 Uname: Linux 4.15.0-43-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.5 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/pcmC0D0p: pedrocr2684 F...m pulseaudio /dev/snd/controlC0: pedrocr2684 F pulseaudio CurrentDesktop: ubuntu:GNOME Date: Tue Jan 15 23:45:10 2019 InstallationDate: Installed on 2018-05-31 (229 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426) SourcePackage: pulseaudio UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 03/22/2018 dmi.bios.vendor: LENOVO dmi.bios.version: N1CET66W (1.34 ) dmi.board.asset.tag: Not Available dmi.board.name: 20FAS5TS00 dmi.board.vendor: LENOVO dmi.board.version: SDK0J40697 WIN dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: None dmi.modalias: dmi:bvnLENOVO:bvrN1CET66W(1.34):bd03/22/2018:svnLENOVO:pn20FAS5TS00:pvrThinkPadT460s:rvnLENOVO:rn20FAS5TS00:rvrSDK0J40697WIN:cvnLENOVO:ct10:cvrNone: dmi.product.family: ThinkPad T460s dmi.product.name: 20FAS5TS00 dmi.product.version: ThinkPad T460s dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1811902/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1763940] Re: Pressing Print Screen in keyboard makes Rhythmbox go to sleep
** Description changed: + https://gitlab.freedesktop.org/pulseaudio/pulseaudio/issues/8 + + --- + Steps: 1. Start Rhythmbox and play music 2. Press Print Screen in keyboard 3. Music stops and cannot be played again in Rhythmbox 4. If the music does not stop from the first time try step 2 again and again until it stops I can navigate the UI of Rhythmbox, but I cannot play music. I have to kill the sleeping process in order to play music. I can reproduce this bug in Totem and Clementine too. Clementine and Totem present this error: pa_stream_writable_size() failed: Connection terminated This bug affects Bionic too. ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: pulseaudio 1:8.0-0ubuntu3.8 ProcVersionSignature: Ubuntu 4.4.0-119.143-generic 4.4.114 Uname: Linux 4.4.0-119-generic x86_64 ApportVersion: 2.20.1-0ubuntu2.16 Architecture: amd64 AudioDevicesInUse: - USERPID ACCESS COMMAND - /dev/snd/controlC0: amr9438 F pulseaudio + USERPID ACCESS COMMAND + /dev/snd/controlC0: amr9438 F pulseaudio CurrentDesktop: Unity Date: Sat Apr 14 14:42:55 2018 InstallationDate: Installed on 2017-06-21 (296 days ago) InstallationMedia: Ubuntu 16.04.2 LTS "Xenial Xerus" - Release amd64 (20170215.2) SourcePackage: pulseaudio UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 04/08/2011 dmi.bios.vendor: Award Software International, Inc. dmi.bios.version: F2 dmi.board.name: GA-78LMT-S2P dmi.board.vendor: Gigabyte Technology Co., Ltd. dmi.chassis.type: 3 dmi.chassis.vendor: Gigabyte Technology Co., Ltd. dmi.modalias: dmi:bvnAwardSoftwareInternational,Inc.:bvrF2:bd04/08/2011:svnGigabyteTechnologyCo.,Ltd.:pnGA-78LMT-S2P:pvr:rvnGigabyteTechnologyCo.,Ltd.:rnGA-78LMT-S2P:rvr:cvnGigabyteTechnologyCo.,Ltd.:ct3:cvr: dmi.product.name: GA-78LMT-S2P dmi.sys.vendor: Gigabyte Technology Co., Ltd. modified.conffile..etc.pulse.daemon.conf: [modified] modified.conffile..etc.xdg.autostart.pulseaudio.desktop: [modified] mtime.conffile..etc.pulse.daemon.conf: 2017-07-04T15:49:08 mtime.conffile..etc.xdg.autostart.pulseaudio.desktop: 2017-06-22T13:08:09 -- 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/1763940 Title: Pressing Print Screen in keyboard makes Rhythmbox go to sleep Status in PulseAudio: Unknown Status in pulseaudio package in Ubuntu: New Status in rhythmbox package in Ubuntu: Invalid Bug description: https://gitlab.freedesktop.org/pulseaudio/pulseaudio/issues/8 --- Steps: 1. Start Rhythmbox and play music 2. Press Print Screen in keyboard 3. Music stops and cannot be played again in Rhythmbox 4. If the music does not stop from the first time try step 2 again and again until it stops I can navigate the UI of Rhythmbox, but I cannot play music. I have to kill the sleeping process in order to play music. I can reproduce this bug in Totem and Clementine too. Clementine and Totem present this error: pa_stream_writable_size() failed: Connection terminated This bug affects Bionic too. ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: pulseaudio 1:8.0-0ubuntu3.8 ProcVersionSignature: Ubuntu 4.4.0-119.143-generic 4.4.114 Uname: Linux 4.4.0-119-generic x86_64 ApportVersion: 2.20.1-0ubuntu2.16 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: amr9438 F pulseaudio CurrentDesktop: Unity Date: Sat Apr 14 14:42:55 2018 InstallationDate: Installed on 2017-06-21 (296 days ago) InstallationMedia: Ubuntu 16.04.2 LTS "Xenial Xerus" - Release amd64 (20170215.2) SourcePackage: pulseaudio UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 04/08/2011 dmi.bios.vendor: Award Software International, Inc. dmi.bios.version: F2 dmi.board.name: GA-78LMT-S2P dmi.board.vendor: Gigabyte Technology Co., Ltd. dmi.chassis.type: 3 dmi.chassis.vendor: Gigabyte Technology Co., Ltd. dmi.modalias: dmi:bvnAwardSoftwareInternational,Inc.:bvrF2:bd04/08/2011:svnGigabyteTechnologyCo.,Ltd.:pnGA-78LMT-S2P:pvr:rvnGigabyteTechnologyCo.,Ltd.:rnGA-78LMT-S2P:rvr:cvnGigabyteTechnologyCo.,Ltd.:ct3:cvr: dmi.product.name: GA-78LMT-S2P dmi.sys.vendor: Gigabyte Technology Co., Ltd. modified.conffile..etc.pulse.daemon.conf: [modified] modified.conffile..etc.xdg.autostart.pulseaudio.desktop: [modified] mtime.conffile..etc.pulse.daemon.conf: 2017-07-04T15:49:08 mtime.conffile..etc.xdg.autostart.pulseaudio.desktop: 2017-06-22T13:08:09 To manage notifications about this bug go to: https://bugs.launchpad.net/pulseaudio/+bug/1763940/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More he
[Touch-packages] [Bug 273049] Re: update-manager should guest an estimative of upgrade size to prevent running out of free disk
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: update-manager (Ubuntu) Status: New => Confirmed -- 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/273049 Title: update-manager should guest an estimative of upgrade size to prevent running out of free disk Status in apt package in Ubuntu: Invalid Status in update-manager package in Ubuntu: Confirmed Bug description: Binary package hint: update-manager This is a wishbug! When users upgrade to the development version using update-manager -d or do-release-upgrade -d stats should be collected and sent to some kind of archive (after user allows them to) so that a approximated size necessary can be calculated in order to prevent running out of free disk on future dist upgrades by users (either still on development versions or Stable releases). A rough number can be the size of the packages plus the necessary amount unpack. We could tie the old kernel clean up (last good kernel [1]) with update-manager so more disk can be freed up in case there ain't enough free disk. This ticket groups from #106804, #221855 and "595473 Related blueprint: cleanup-cruft [2] [1] https://wiki.ubuntu.com/KernelTeam/removing-old-kernels [2] https://blueprints.edge.launchpad.net/ubuntu/+spec/cleanup-cruft To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apt/+bug/273049/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1812132] [NEW] Does not return results with files that have hyphens in the filename
Public bug reported: On Ubuntu 18.04 using the `vanilla-gnome-desktop` session (i.e. Gnome Shell), tracker does not return any files if there is a hyphen (-) in the search string. To recreate: - Create a file named `foo-bar`. - Press to open Overview. - Type foo. Observe that the `foo-bar` file appears. - Type foo-. Observe that the overview says "No results." This is a regression as files with hyphens in the filename were included in search results in 16.04. ** Affects: tracker (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to tracker in Ubuntu. https://bugs.launchpad.net/bugs/1812132 Title: Does not return results with files that have hyphens in the filename Status in tracker package in Ubuntu: New Bug description: On Ubuntu 18.04 using the `vanilla-gnome-desktop` session (i.e. Gnome Shell), tracker does not return any files if there is a hyphen (-) in the search string. To recreate: - Create a file named `foo-bar`. - Press to open Overview. - Type foo. Observe that the `foo-bar` file appears. - Type foo-. Observe that the overview says "No results." This is a regression as files with hyphens in the filename were included in search results in 16.04. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/tracker/+bug/1812132/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1812132] Re: Does not return results with files that have hyphens in the filename
Note: This only occurs if the file is in a search location that was manually added. For example: - Open the Settings app - Select Search in the left hand sidebar - Ensure Files is On - Press the gear at the lower right of the dialog to open Search Locations - Select the Other tab - Add a new search location, for example ~/projects/ This bug seems to only affect files in such locations. If, for example, Home is On in the Places tab, files with dashes appear in search results. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to tracker in Ubuntu. https://bugs.launchpad.net/bugs/1812132 Title: Does not return results with files that have hyphens in the filename Status in tracker package in Ubuntu: New Bug description: On Ubuntu 18.04 using the `vanilla-gnome-desktop` session (i.e. Gnome Shell), tracker does not return any files if there is a hyphen (-) in the search string. To recreate: - Create a file named `foo-bar`. - Press to open Overview. - Type foo. Observe that the `foo-bar` file appears. - Type foo-. Observe that the overview says "No results." This is a regression as files with hyphens in the filename were included in search results in 16.04. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/tracker/+bug/1812132/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1652101] Re: Can't create nested AppArmor namespaces
>From what I understand, LXD is moving toward SNAP LXD as a default, so not being able to run SNAP in an LXD container configured for "nesting": re - lxc config set security.nesting true Is basically going to prevent LXD from being used for Nested Containers. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to apparmor in Ubuntu. https://bugs.launchpad.net/bugs/1652101 Title: Can't create nested AppArmor namespaces Status in AppArmor: Confirmed Status in apparmor package in Ubuntu: Confirmed Status in linux package in Ubuntu: Confirmed Bug description: A user with CAP_MAC_ADMIN in the init namespace can create an AppArmor policy namespace and load a profile belonging to that AppArmor namespace. Once that's done, the user can confine a process with that namespaced AppArmor profile and enter into a user namespace. That process can then load additional AppArmor profiles inside of the AppArmor and user namespace. Here's an example: We need to set up the namespace, n1, and load the profile, p1. $ export rules="file, signal, unix, dbus, ptrace, mount, pivot_root, capability," $ sudo mkdir /sys/kernel/security/apparmor/policy/namespaces/n1 $ echo "profile p1 { $rules }" | sudo apparmor_parser -qrn n1 Now we enter into confinement using the AppArmor namespace and profile and then enter into an unprivileged user namespace $ aa-exec -n n1 -p p1 -- unshare -Ur We can now load profiles as the privileged user inside of the unprivileged user namespace # echo "profile test {}" | apparmor_parser -qr The reason for this bug report is that we cannot create a nested AppArmor policy namespace inside of the unprivileged user namespace # mkdir /sys/kernel/security/apparmor/policy/namespaces/n1/namespaces/p1 mkdir: cannot create directory ‘/sys/kernel/security/apparmor/policy/namespaces/n1/namespaces/p1’: Permission denied If that worked, we could adjust LXD to read /sys/kernel/security/apparmor/.ns_name to get the current AppArmor namespace, then create a new namespace under the current namespace, and leverage the nested namespace for its nested containers. To manage notifications about this bug go to: https://bugs.launchpad.net/apparmor/+bug/1652101/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1787729] Re: apport-autoreport.service fails if whoopsie isn't running
The lines have been added to: /lib/systemd/system/apport-autoreport.service --- [Unit] [...] Wants=whoopsie.service After=whoopsie.service ** Attachment added: "$ cat /lib/systemd/system/apport-autoreport.service" https://bugs.launchpad.net/ubuntu/+source/apport/+bug/1787729/+attachment/5229777/+files/apport-autoreport.service.txt -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to apport in Ubuntu. https://bugs.launchpad.net/bugs/1787729 Title: apport-autoreport.service fails if whoopsie isn't running Status in apport package in Ubuntu: In Progress Status in apport source package in Cosmic: In Progress Bug description: Impact -- If automatic crash reporting is enabled and apport-autoreport.service starts before whoopsie on boot then crash reports that happened during shutdown or start up will not be automatically uploaded to the error tracker. Test Case - 1) install apport-noui 2) sudo service apport stop 3) modify /usr/share/apport/whoopsie-upload-all to exit(1) thereby recreating the situation where whoopsie isn't running. I did this by copying lines 159,160 to 161,162 and unindenting them. N.B. this isn't necessary if you are on a system where whoopsie is starting after apport. 4) touch /var/crash/my.crash 5) reboot 5) run 'systemctl status apport-autoreport.service' and observe it failed because whoopsie isn't running When testing the proposed version of apport you'll want to revert the changes you made to whoopsie-upload-all. With the version of apport from -proposed you should no longer see the failure message for the apport-autoreport.service. The best test case is just having an affected system test the package from -proposed though. Regression Potential We are clearly fixing something that was a mistake in the original service so there is little chance for regression. ProblemType: BugDistroRelease: Ubuntu 18.10 Package: apport 2.20.10-0ubuntu7 Uname: Linux 4.18.3-041803-generic x86_64 ApportLog: ApportVersion: 2.20.10-0ubuntu7 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Sat Aug 18 11:48:00 2018 InstallationDate: Installed on 2017-10-13 (308 days ago) InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Alpha amd64 (20170926) PackageArchitecture: allSourcePackage: apport UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apport/+bug/1787729/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1787729] Re: apport-autoreport.service fails if whoopsie isn't running
I rebooted the notebook, and reviewed the service: 'systemctl status apport-autoreport.service': ● apport-autoreport.service - Process error reports when automatic reporting is enabled Loaded: loaded (/lib/systemd/system/apport-autoreport.service; static; vendor preset: enabled) Active: inactive (dead) since Wed 2019-01-16 19:04:59 -03; 10min ago Process: 2959 ExecStart=/usr/share/apport/whoopsie-upload-all (code=exited, status=0/SUCCESS) Main PID: 2959 (code=exited, status=0/SUCCESS) For me, it works well. ** Attachment added: "$ systemctl status apport-autoreport.service" https://bugs.launchpad.net/ubuntu/+source/apport/+bug/1787729/+attachment/5229775/+files/systemctl_status_apport-autoreport.service.txt -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to apport in Ubuntu. https://bugs.launchpad.net/bugs/1787729 Title: apport-autoreport.service fails if whoopsie isn't running Status in apport package in Ubuntu: In Progress Status in apport source package in Cosmic: In Progress Bug description: Impact -- If automatic crash reporting is enabled and apport-autoreport.service starts before whoopsie on boot then crash reports that happened during shutdown or start up will not be automatically uploaded to the error tracker. Test Case - 1) install apport-noui 2) sudo service apport stop 3) modify /usr/share/apport/whoopsie-upload-all to exit(1) thereby recreating the situation where whoopsie isn't running. I did this by copying lines 159,160 to 161,162 and unindenting them. N.B. this isn't necessary if you are on a system where whoopsie is starting after apport. 4) touch /var/crash/my.crash 5) reboot 5) run 'systemctl status apport-autoreport.service' and observe it failed because whoopsie isn't running When testing the proposed version of apport you'll want to revert the changes you made to whoopsie-upload-all. With the version of apport from -proposed you should no longer see the failure message for the apport-autoreport.service. The best test case is just having an affected system test the package from -proposed though. Regression Potential We are clearly fixing something that was a mistake in the original service so there is little chance for regression. ProblemType: BugDistroRelease: Ubuntu 18.10 Package: apport 2.20.10-0ubuntu7 Uname: Linux 4.18.3-041803-generic x86_64 ApportLog: ApportVersion: 2.20.10-0ubuntu7 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Sat Aug 18 11:48:00 2018 InstallationDate: Installed on 2017-10-13 (308 days ago) InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Alpha amd64 (20170926) PackageArchitecture: allSourcePackage: apport UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apport/+bug/1787729/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1808508] Re: Valgrind doesn't work in disco [Fatal error at startup: a function redirection which is mandatory for this platform-tool combination cannot be set up.]
A fix for this bug was uploaded on the 10th but didn't seem to migrate out of -proposed. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to base-files in Ubuntu. https://bugs.launchpad.net/bugs/1808508 Title: Valgrind doesn't work in disco [Fatal error at startup: a function redirection which is mandatory for this platform-tool combination cannot be set up.] Status in base-files package in Ubuntu: Won't Fix Status in valgrind package in Ubuntu: Triaged Bug description: $ valgrind /bin/ls ==25995== Memcheck, a memory error detector ==25995== Copyright (C) 2002-2017, and GNU GPL'd, by Julian Seward et al. ==25995== Using Valgrind-3.14.0 and LibVEX; rerun with -h for copyright info ==25995== Command: /bin/ls ==25995== valgrind: Fatal error at startup: a function redirection valgrind: which is mandatory for this platform-tool combination valgrind: cannot be set up. Details of the redirection are: valgrind: valgrind: A must-be-redirected function valgrind: whose name matches the pattern: strlen valgrind: in an object with soname matching: ld-linux-x86-64.so.2 valgrind: was not found whilst processing valgrind: symbols from the object with soname: ld-linux-x86-64.so.2 valgrind: valgrind: Possible fixes: (1, short term): install glibc's debuginfo valgrind: package on this machine. (2, longer term): ask the packagers valgrind: for your Linux distribution to please in future ship a non- valgrind: stripped ld.so (or whatever the dynamic linker .so is called) valgrind: that exports the above-named function using the standard valgrind: calling conventions for this platform. The package you need valgrind: to install for fix (1) is called valgrind: valgrind:On Debian, Ubuntu: libc6-dbg valgrind:On SuSE, openSuSE, Fedora, RHEL: glibc-debuginfo valgrind: valgrind: Note that if you are debugging a 32 bit process on a valgrind: 64 bit system, you will need a corresponding 32 bit debuginfo valgrind: package (e.g. libc6-dbg:i386). valgrind: valgrind: Cannot continue -- exiting now. Sorry. ProblemType: Bug DistroRelease: Ubuntu 19.04 Package: valgrind 1:3.14.0-0ubuntu3 ProcVersionSignature: Ubuntu 4.18.0-11.12-generic 4.18.12 Uname: Linux 4.18.0-11-generic x86_64 ApportVersion: 2.20.10-0ubuntu14 Architecture: amd64 Date: Fri Dec 14 17:06:03 2018 InstallationDate: Installed on 2018-12-04 (10 days ago) InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Alpha amd64 (20181203) SourcePackage: valgrind UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/base-files/+bug/1808508/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1787729] Re: apport-autoreport.service fails if whoopsie isn't running
I just updated to apport 2.20.10-0ubuntu19 ** Attachment added: "$ dpkg -l | grep apport" https://bugs.launchpad.net/ubuntu/+source/apport/+bug/1787729/+attachment/5229748/+files/dpkg_-l_+_grep_apport.txt -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to apport in Ubuntu. https://bugs.launchpad.net/bugs/1787729 Title: apport-autoreport.service fails if whoopsie isn't running Status in apport package in Ubuntu: In Progress Status in apport source package in Cosmic: In Progress Bug description: Impact -- If automatic crash reporting is enabled and apport-autoreport.service starts before whoopsie on boot then crash reports that happened during shutdown or start up will not be automatically uploaded to the error tracker. Test Case - 1) install apport-noui 2) sudo service apport stop 3) modify /usr/share/apport/whoopsie-upload-all to exit(1) thereby recreating the situation where whoopsie isn't running. I did this by copying lines 159,160 to 161,162 and unindenting them. N.B. this isn't necessary if you are on a system where whoopsie is starting after apport. 4) touch /var/crash/my.crash 5) reboot 5) run 'systemctl status apport-autoreport.service' and observe it failed because whoopsie isn't running When testing the proposed version of apport you'll want to revert the changes you made to whoopsie-upload-all. With the version of apport from -proposed you should no longer see the failure message for the apport-autoreport.service. The best test case is just having an affected system test the package from -proposed though. Regression Potential We are clearly fixing something that was a mistake in the original service so there is little chance for regression. ProblemType: BugDistroRelease: Ubuntu 18.10 Package: apport 2.20.10-0ubuntu7 Uname: Linux 4.18.3-041803-generic x86_64 ApportLog: ApportVersion: 2.20.10-0ubuntu7 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Sat Aug 18 11:48:00 2018 InstallationDate: Installed on 2017-10-13 (308 days ago) InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Alpha amd64 (20170926) PackageArchitecture: allSourcePackage: apport UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apport/+bug/1787729/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1763940] Re: Pressing Print Screen in keyboard makes Rhythmbox go to sleep
** Changed in: rhythmbox (Ubuntu) Status: New => Invalid -- 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/1763940 Title: Pressing Print Screen in keyboard makes Rhythmbox go to sleep Status in PulseAudio: Unknown Status in pulseaudio package in Ubuntu: New Status in rhythmbox package in Ubuntu: Invalid Bug description: Steps: 1. Start Rhythmbox and play music 2. Press Print Screen in keyboard 3. Music stops and cannot be played again in Rhythmbox 4. If the music does not stop from the first time try step 2 again and again until it stops I can navigate the UI of Rhythmbox, but I cannot play music. I have to kill the sleeping process in order to play music. I can reproduce this bug in Totem and Clementine too. Clementine and Totem present this error: pa_stream_writable_size() failed: Connection terminated This bug affects Bionic too. ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: pulseaudio 1:8.0-0ubuntu3.8 ProcVersionSignature: Ubuntu 4.4.0-119.143-generic 4.4.114 Uname: Linux 4.4.0-119-generic x86_64 ApportVersion: 2.20.1-0ubuntu2.16 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: amr9438 F pulseaudio CurrentDesktop: Unity Date: Sat Apr 14 14:42:55 2018 InstallationDate: Installed on 2017-06-21 (296 days ago) InstallationMedia: Ubuntu 16.04.2 LTS "Xenial Xerus" - Release amd64 (20170215.2) SourcePackage: pulseaudio UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 04/08/2011 dmi.bios.vendor: Award Software International, Inc. dmi.bios.version: F2 dmi.board.name: GA-78LMT-S2P dmi.board.vendor: Gigabyte Technology Co., Ltd. dmi.chassis.type: 3 dmi.chassis.vendor: Gigabyte Technology Co., Ltd. dmi.modalias: dmi:bvnAwardSoftwareInternational,Inc.:bvrF2:bd04/08/2011:svnGigabyteTechnologyCo.,Ltd.:pnGA-78LMT-S2P:pvr:rvnGigabyteTechnologyCo.,Ltd.:rnGA-78LMT-S2P:rvr:cvnGigabyteTechnologyCo.,Ltd.:ct3:cvr: dmi.product.name: GA-78LMT-S2P dmi.sys.vendor: Gigabyte Technology Co., Ltd. modified.conffile..etc.pulse.daemon.conf: [modified] modified.conffile..etc.xdg.autostart.pulseaudio.desktop: [modified] mtime.conffile..etc.pulse.daemon.conf: 2017-07-04T15:49:08 mtime.conffile..etc.xdg.autostart.pulseaudio.desktop: 2017-06-22T13:08:09 To manage notifications about this bug go to: https://bugs.launchpad.net/pulseaudio/+bug/1763940/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1768364] Re: Combo boxes close immediately after opening
** Changed in: rhythmbox (Ubuntu) Status: New => Invalid -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to gtk+3.0 in Ubuntu. https://bugs.launchpad.net/bugs/1768364 Title: Combo boxes close immediately after opening Status in gtk+3.0 package in Ubuntu: New Status in rhythmbox package in Ubuntu: Invalid Bug description: Sometimes when a select box is clicked, it opens and then closes almost immediately. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: gnome-shell 3.28.1-0ubuntu2 ProcVersionSignature: Ubuntu 4.15.0-20.21-generic 4.15.17 Uname: Linux 4.15.0-20-generic x86_64 ApportVersion: 2.20.9-0ubuntu7 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Tue May 1 14:39:28 2018 DisplayManager: gdm3 GsettingsChanges: b'org.gnome.shell' b'app-picker-view' b'uint32 1' b'org.gnome.shell' b'favorite-apps' redacted by apport b'org.gnome.desktop.interface' b'gtk-im-module' b"'gtk-im-context-simple'" InstallationDate: Installed on 2018-04-27 (4 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/1768364/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1652101] Re: Can't create nested AppArmor namespaces
** Also affects: apparmor Importance: Undecided Status: New ** Changed in: apparmor Status: New => Confirmed ** Changed in: apparmor Importance: Undecided => Medium -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to apparmor in Ubuntu. https://bugs.launchpad.net/bugs/1652101 Title: Can't create nested AppArmor namespaces Status in AppArmor: Confirmed Status in apparmor package in Ubuntu: Confirmed Status in linux package in Ubuntu: Confirmed Bug description: A user with CAP_MAC_ADMIN in the init namespace can create an AppArmor policy namespace and load a profile belonging to that AppArmor namespace. Once that's done, the user can confine a process with that namespaced AppArmor profile and enter into a user namespace. That process can then load additional AppArmor profiles inside of the AppArmor and user namespace. Here's an example: We need to set up the namespace, n1, and load the profile, p1. $ export rules="file, signal, unix, dbus, ptrace, mount, pivot_root, capability," $ sudo mkdir /sys/kernel/security/apparmor/policy/namespaces/n1 $ echo "profile p1 { $rules }" | sudo apparmor_parser -qrn n1 Now we enter into confinement using the AppArmor namespace and profile and then enter into an unprivileged user namespace $ aa-exec -n n1 -p p1 -- unshare -Ur We can now load profiles as the privileged user inside of the unprivileged user namespace # echo "profile test {}" | apparmor_parser -qr The reason for this bug report is that we cannot create a nested AppArmor policy namespace inside of the unprivileged user namespace # mkdir /sys/kernel/security/apparmor/policy/namespaces/n1/namespaces/p1 mkdir: cannot create directory ‘/sys/kernel/security/apparmor/policy/namespaces/n1/namespaces/p1’: Permission denied If that worked, we could adjust LXD to read /sys/kernel/security/apparmor/.ns_name to get the current AppArmor namespace, then create a new namespace under the current namespace, and leverage the nested namespace for its nested containers. To manage notifications about this bug go to: https://bugs.launchpad.net/apparmor/+bug/1652101/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1727908] Re: Software & Updates application does not permit changes on the "Other Software" tab
the gnome-shell error is a bit weird, maybe there is an issue on this component ** Also affects: gnome-shell (Ubuntu) Importance: Undecided Status: New -- 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/1727908 Title: Software & Updates application does not permit changes on the "Other Software" tab Status in gnome-shell package in Ubuntu: New Status in software-properties package in Ubuntu: Confirmed Bug description: On the "Other Software" tab, I am unable to select "Canonical Partners". Similarly, the other checkboxes on the "Other Software" can not be clicked. Clicking on a checkbox has no effect, and a dialog requesting the admin password is not presented. However, activating or deactivating checkboxes on other tabs causes an authorization dialog to be presented to the user. I experience this bug in an an Xorg session. sources.list and sources.list.d have the following permissions: -rw-r--r-- 1 root root 2897 Oct 26 22:35 sources.list drwxr-xr-x 2 root root 4096 Oct 26 21:29 sources.list.d All files in sources.list.d have the following permissions as this example: -rw-r--r-- 1 root root 189 Oct 25 21:50 google-chrome.list $ lsb_release -rd Description: Ubuntu 17.10 Release: 17.10 $ apt-cache policy software-properties-gtk software-properties-gtk: Installed: 0.96.24.17 Candidate: 0.96.24.17 Version table: *** 0.96.24.17 500 500 http://us.archive.ubuntu.com/ubuntu artful/main amd64 Packages 500 http://us.archive.ubuntu.com/ubuntu artful/main i386 Packages 100 /var/lib/dpkg/status ProblemType: Bug DistroRelease: Ubuntu 17.10 Package: software-properties-gtk 0.96.24.17 ProcVersionSignature: Ubuntu 4.13.0-16.19-generic 4.13.4 Uname: Linux 4.13.0-16-generic x86_64 NonfreeKernelModules: wl nvidia_uvm nvidia_drm nvidia_modeset nvidia ApportVersion: 2.20.7-0ubuntu3.1 Architecture: amd64 CurrentDesktop: GNOME Date: Thu Oct 26 22:45:09 2017 InstallationDate: Installed on 2017-10-26 (1 days ago) InstallationMedia: Ubuntu 17.10.0 2017.10.25 amd64 "Custom Artful Aardvark" PackageArchitecture: all ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: software-properties UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1727908/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1760349] Re: Cannot log in to public open Wifi connection because not being redirected to login site
Thank you for your bug report, that's not a network-manager issue though, there is no need to create that file since the package already provides a binary with that configuration 'network-manager-config- connectivity-ubuntu' which is installed by default on Ubuntu. The issue could be that Kubuntu doesn't install that package by default though, which would be a problem to bring to the kubuntu team ** Changed in: network-manager (Ubuntu) Importance: Undecided => Low ** Changed in: network-manager (Ubuntu) Status: Confirmed => Invalid -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to network-manager in Ubuntu. https://bugs.launchpad.net/bugs/1760349 Title: Cannot log in to public open Wifi connection because not being redirected to login site Status in network-manager package in Ubuntu: Invalid Bug description: I have noticed that Kubuntu 18.04 (Bionic Beaver) does not login to public Wifi hotspots without wifi security, that require login through a web page. I don't know if this is reproducible on arbitrary public networks, or only on the few I tried. The solution was as follows: - Create file /etc/NetworkManager/conf.d/20-connectivity-debian.conf (you'll need root or sudo). - Add the following lines as recommended by Guruprasad (https://www.lguruprasad.in/blog/2015/07/21/enabling-captive-portal-detection-in-gnome-3-14-on-debian-jessie/): [connectivity] uri=http://network-test.debian.org/nm response=NetworkManager is online interval=300 - Restart the network manager with service network-manager restart (will need sudo or root again). This is a very annoying and unnecessary default behavior it seems. Maybe a good idea to fix it. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: network-manager 1.10.6-2ubuntu1 ProcVersionSignature: Ubuntu 4.15.0-13.14-generic 4.15.10 Uname: Linux 4.15.0-13-generic x86_64 ApportVersion: 2.20.9-0ubuntu2 Architecture: amd64 CurrentDesktop: KDE Date: Sat Mar 31 22:48:21 2018 IfupdownConfig: # interfaces(5) file used by ifup(8) and ifdown(8) auto lo iface lo inet loopback InstallationDate: Installed on 2018-02-18 (41 days ago) InstallationMedia: Kubuntu 18.04 LTS "Bionic Beaver" - Alpha amd64 (20180218) IpRoute: default via 10.129.249.1 dev wlp1s0 proto dhcp metric 600 10.129.249.0/24 dev wlp1s0 proto kernel scope link src 10.129.249.35 metric 600 169.254.0.0/16 dev wlp1s0 scope link metric 1000 NetworkManager.state: [main] NetworkingEnabled=true WirelessEnabled=true WWANEnabled=true ProcEnviron: LANGUAGE= PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=de_DE.UTF-8 SHELL=/bin/bash RfKill: 0: phy0: Wireless LAN Soft blocked: no Hard blocked: no SourcePackage: network-manager UpgradeStatus: No upgrade log present (probably fresh install) nmcli-dev: DEVICE TYPE STATE DBUS-PATH CONNECTION CON-UUID CON-PATH wlp1s0 wifi connected /org/freedesktop/NetworkManager/Devices/2 SuedtirolSpot_1 c4464785-b548-4655-b06b-48a0aec06a87 /org/freedesktop/NetworkManager/ActiveConnection/3 lo loopback unmanaged /org/freedesktop/NetworkManager/Devices/1 -- ---- nmcli-nm: RUNNING VERSION STATE STARTUP CONNECTIVITY NETWORKING WIFI-HW WIFI WWAN-HW WWAN running 1.10.6 connected started full enabled enabled enabled enabled enabled To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1760349/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1811999] Re: [USB-Audio - Audioengine D3, playback] fails after a while (a second)
Okay, I am confused now. I have another system for with usb DAC works just fine. Distributor ID: Ubuntu Description:Ubuntu 18.10 Release:18.10 Codename: cosmic Linux 4.18.0-13-generic x86_64 And dmesg show me same issue: [ 3649.034233] usb 3-1: new full-speed USB device number 2 using xhci_hcd [ 3649.651192] usb 3-1: New USB device found, idVendor=2912, idProduct=120b, bcdDevice= 1.0c [ 3649.651199] usb 3-1: New USB device strings: Mfr=1, Product=2, SerialNumber=3 [ 3649.651204] usb 3-1: Product: Audioengine D3 [ 3649.651208] usb 3-1: Manufacturer: Audioengine [ 3649.651212] usb 3-1: SerialNumber: Audioengine [ 3649.696266] usb 3-1: 1:1: cannot get freq at ep 0x1 [ 3649.719070] usbcore: registered new interface driver snd-usb-audio [ 3649.762678] usb 3-1: 1:1: cannot get freq at ep 0x1 [ 3649.785497] usb 3-1: 1:1: cannot get freq at ep 0x1 -- 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/1811999 Title: [USB-Audio - Audioengine D3, playback] fails after a while (a second) Status in alsa-driver package in Ubuntu: New Bug description: USB DAC stops playing sound after a second. I had problem with kernel 4.15. So, I tried upgrading to 4.19 but still issue persists. I think, we might need to add it to sound/usb/quirks.c I see following in dmesg [ 5937.978117] usb 1-1.4.2: USB disconnect, device number 16 [ 5955.721597] usb 1-1.4.1: new full-speed USB device number 17 using xhci_hcd [ 5956.302910] usb 1-1.4.1: New USB device found, idVendor=2912, idProduct=120b, bcdDevice= 1.0c [ 5956.302917] usb 1-1.4.1: New USB device strings: Mfr=1, Product=2, SerialNumber=3 [ 5956.302921] usb 1-1.4.1: Product: Audioengine D3 [ 5956.302926] usb 1-1.4.1: Manufacturer: Audioengine [ 5956.302929] usb 1-1.4.1: SerialNumber: Audioengine [ 5956.320621] usb 1-1.4.1: 1:1: cannot get freq at ep 0x1 [ 5956.920844] usb 1-1.4.1: 1:1: cannot get freq at ep 0x1 [ 5956.938929] usb 1-1.4.1: 1:1: cannot get freq at ep 0x1 And lsusb -v has following entry for the device. Bus 001 Device 017: ID 2912:120b Couldn't open device, some information will be missing Device Descriptor: bLength18 bDescriptorType 1 bcdUSB 1.00 bDeviceClass0 (Defined at Interface level) bDeviceSubClass 0 bDeviceProtocol 0 bMaxPacketSize0 8 idVendor 0x2912 idProduct 0x120b bcdDevice1.0c iManufacturer 1 iProduct2 iSerial 3 bNumConfigurations 1 Configuration Descriptor: bLength 9 bDescriptorType 2 wTotalLength 131 bNumInterfaces 2 bConfigurationValue 1 iConfiguration 0 bmAttributes 0x80 (Bus Powered) MaxPower 200mA Interface Descriptor: bLength 9 bDescriptorType 4 bInterfaceNumber0 bAlternateSetting 0 bNumEndpoints 0 bInterfaceClass 1 Audio bInterfaceSubClass 1 Control Device bInterfaceProtocol 0 iInterface 0 AudioControl Interface Descriptor: bLength 9 bDescriptorType36 bDescriptorSubtype 1 (HEADER) bcdADC 1.00 wTotalLength 43 bInCollection 1 baInterfaceNr( 0) 1 AudioControl Interface Descriptor: bLength12 bDescriptorType36 bDescriptorSubtype 2 (INPUT_TERMINAL) bTerminalID 5 wTerminalType 0x0101 USB Streaming bAssocTerminal 0 bNrChannels 2 wChannelConfig 0x0003 Left Front (L) Right Front (R) iChannelNames 0 iTerminal 0 AudioControl Interface Descriptor: bLength13 bDescriptorType36 bDescriptorSubtype 6 (FEATURE_UNIT) bUnitID 7 bSourceID 5 bControlSize2 bmaControls( 0) 0x01 bmaControls( 0) 0x00 Mute Control bmaControls( 1) 0x02 bmaControls( 1) 0x00 Volume Control bmaControls( 2) 0x02 bmaControls( 2) 0x00 Volume Control iFeature0 AudioControl Interface Descriptor: bLength 9 bDescriptorType36 bDescriptorSubtype 3 (OUTPUT_TERMINAL) bTerminalID 8
[Touch-packages] [Bug 1787729] Re: apport-autoreport.service fails if whoopsie isn't running
** Changed in: apport (Ubuntu Cosmic) Status: Triaged => In Progress ** Changed in: apport (Ubuntu Cosmic) Assignee: (unassigned) => Brian Murray (brian-murray) -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to apport in Ubuntu. https://bugs.launchpad.net/bugs/1787729 Title: apport-autoreport.service fails if whoopsie isn't running Status in apport package in Ubuntu: In Progress Status in apport source package in Cosmic: In Progress Bug description: Impact -- If automatic crash reporting is enabled and apport-autoreport.service starts before whoopsie on boot then crash reports that happened during shutdown or start up will not be automatically uploaded to the error tracker. Test Case - 1) install apport-noui 2) sudo service apport stop 3) modify /usr/share/apport/whoopsie-upload-all to exit(1) thereby recreating the situation where whoopsie isn't running. I did this by copying lines 159,160 to 161,162 and unindenting them. N.B. this isn't necessary if you are on a system where whoopsie is starting after apport. 4) touch /var/crash/my.crash 5) reboot 5) run 'systemctl status apport-autoreport.service' and observe it failed because whoopsie isn't running When testing the proposed version of apport you'll want to revert the changes you made to whoopsie-upload-all. With the version of apport from -proposed you should no longer see the failure message for the apport-autoreport.service. The best test case is just having an affected system test the package from -proposed though. Regression Potential We are clearly fixing something that was a mistake in the original service so there is little chance for regression. ProblemType: BugDistroRelease: Ubuntu 18.10 Package: apport 2.20.10-0ubuntu7 Uname: Linux 4.18.3-041803-generic x86_64 ApportLog: ApportVersion: 2.20.10-0ubuntu7 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Sat Aug 18 11:48:00 2018 InstallationDate: Installed on 2017-10-13 (308 days ago) InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Alpha amd64 (20170926) PackageArchitecture: allSourcePackage: apport UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apport/+bug/1787729/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1787729] Re: apport-autoreport.service fails if whoopsie isn't running
** Description changed: Impact -- If automatic crash reporting is enabled and apport-autoreport.service starts before whoopsie on boot then crash reports that happened during shutdown or start up will not be automatically uploaded to the error tracker. Test Case - 1) install apport-noui 2) sudo service apport stop 3) modify /usr/share/apport/whoopsie-upload-all to exit(1) thereby recreating the situation where whoopsie isn't running. I did this by copying lines 159,160 to 161,162 and unindenting them. N.B. this isn't necessary if you are on a system where whoopsie is starting after apport. 4) touch /var/crash/my.crash 5) reboot 5) run 'systemctl status apport-autoreport.service' and observe it failed because whoopsie isn't running When testing the proposed version of apport you'll want to revert the changes you made to whoopsie-upload-all. With the version of apport from -proposed you should no longer see the failure message for the apport- autoreport.service. The best test case is just having an affected system test the package from -proposed though. Regression Potential We are clearly fixing something that was a mistake in the original service so there is little chance for regression. - Hello, - - Attached image. - - Regards, - -- - Cristian Aravena Romero (caravena) + ProblemType: BugDistroRelease: Ubuntu 18.10 Package: apport 2.20.10-0ubuntu7 Uname: Linux 4.18.3-041803-generic x86_64 ApportLog: ApportVersion: 2.20.10-0ubuntu7 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Sat Aug 18 11:48:00 2018 InstallationDate: Installed on 2017-10-13 (308 days ago) InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Alpha amd64 (20170926) PackageArchitecture: allSourcePackage: apport UpgradeStatus: No upgrade log present (probably fresh install) -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to apport in Ubuntu. https://bugs.launchpad.net/bugs/1787729 Title: apport-autoreport.service fails if whoopsie isn't running Status in apport package in Ubuntu: In Progress Status in apport source package in Cosmic: In Progress Bug description: Impact -- If automatic crash reporting is enabled and apport-autoreport.service starts before whoopsie on boot then crash reports that happened during shutdown or start up will not be automatically uploaded to the error tracker. Test Case - 1) install apport-noui 2) sudo service apport stop 3) modify /usr/share/apport/whoopsie-upload-all to exit(1) thereby recreating the situation where whoopsie isn't running. I did this by copying lines 159,160 to 161,162 and unindenting them. N.B. this isn't necessary if you are on a system where whoopsie is starting after apport. 4) touch /var/crash/my.crash 5) reboot 5) run 'systemctl status apport-autoreport.service' and observe it failed because whoopsie isn't running When testing the proposed version of apport you'll want to revert the changes you made to whoopsie-upload-all. With the version of apport from -proposed you should no longer see the failure message for the apport-autoreport.service. The best test case is just having an affected system test the package from -proposed though. Regression Potential We are clearly fixing something that was a mistake in the original service so there is little chance for regression. ProblemType: BugDistroRelease: Ubuntu 18.10 Package: apport 2.20.10-0ubuntu7 Uname: Linux 4.18.3-041803-generic x86_64 ApportLog: ApportVersion: 2.20.10-0ubuntu7 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Sat Aug 18 11:48:00 2018 InstallationDate: Installed on 2017-10-13 (308 days ago) InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Alpha amd64 (20170926) PackageArchitecture: allSourcePackage: apport UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apport/+bug/1787729/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1787729] Re: apport-autoreport.service fails if whoopsie isn't running
** Description changed: + Impact + -- + If automatic crash reporting is enabled and apport-autoreport.service starts before whoopsie on boot then crash reports that happened during shutdown or start up will not be automatically uploaded to the error tracker. + Test Case - 1) install apport-noui 2) sudo service apport stop 3) modify /usr/share/apport/whoopsie-upload-all to exit(1) thereby recreating the situation where whoopsie isn't running. I did this by copying lines 159,160 to 161,162 and unindenting them. N.B. this isn't necessary if you are on a system where whoopsie is starting after apport. 4) touch /var/crash/my.crash 5) reboot 5) run 'systemctl status apport-autoreport.service' and observe it failed because whoopsie isn't running When testing the proposed version of apport you'll want to revert the changes you made to whoopsie-upload-all. With the version of apport from -proposed you should no longer see the failure message for the apport- autoreport.service. The best test case is just having an affected system test the package from -proposed though. Regression Potential We are clearly fixing something that was a mistake in the original service so there is little chance for regression. Hello, Attached image. Regards, -- Cristian Aravena Romero (caravena) ProblemType: BugDistroRelease: Ubuntu 18.10 Package: apport 2.20.10-0ubuntu7 Uname: Linux 4.18.3-041803-generic x86_64 ApportLog: ApportVersion: 2.20.10-0ubuntu7 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Sat Aug 18 11:48:00 2018 InstallationDate: Installed on 2017-10-13 (308 days ago) InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Alpha amd64 (20170926) PackageArchitecture: allSourcePackage: apport UpgradeStatus: No upgrade log present (probably fresh install) -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to apport in Ubuntu. https://bugs.launchpad.net/bugs/1787729 Title: apport-autoreport.service fails if whoopsie isn't running Status in apport package in Ubuntu: In Progress Status in apport source package in Cosmic: Triaged Bug description: Impact -- If automatic crash reporting is enabled and apport-autoreport.service starts before whoopsie on boot then crash reports that happened during shutdown or start up will not be automatically uploaded to the error tracker. Test Case - 1) install apport-noui 2) sudo service apport stop 3) modify /usr/share/apport/whoopsie-upload-all to exit(1) thereby recreating the situation where whoopsie isn't running. I did this by copying lines 159,160 to 161,162 and unindenting them. N.B. this isn't necessary if you are on a system where whoopsie is starting after apport. 4) touch /var/crash/my.crash 5) reboot 5) run 'systemctl status apport-autoreport.service' and observe it failed because whoopsie isn't running When testing the proposed version of apport you'll want to revert the changes you made to whoopsie-upload-all. With the version of apport from -proposed you should no longer see the failure message for the apport-autoreport.service. The best test case is just having an affected system test the package from -proposed though. Regression Potential We are clearly fixing something that was a mistake in the original service so there is little chance for regression. Hello, Attached image. Regards, -- Cristian Aravena Romero (caravena) ProblemType: BugDistroRelease: Ubuntu 18.10 Package: apport 2.20.10-0ubuntu7 Uname: Linux 4.18.3-041803-generic x86_64 ApportLog: ApportVersion: 2.20.10-0ubuntu7 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Sat Aug 18 11:48:00 2018 InstallationDate: Installed on 2017-10-13 (308 days ago) InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Alpha amd64 (20170926) PackageArchitecture: allSourcePackage: apport UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apport/+bug/1787729/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1787729] Re: apport-autoreport.service fails if whoopsie isn't running
** Description changed: Test Case - 1) install apport-noui 2) sudo service apport stop 3) modify /usr/share/apport/whoopsie-upload-all to exit(1) thereby recreating the situation where whoopsie isn't running. I did this by copying lines 159,160 to 161,162 and unindenting them. N.B. this isn't necessary if you are on a system where whoopsie is starting after apport. 4) touch /var/crash/my.crash 5) reboot 5) run 'systemctl status apport-autoreport.service' and observe it failed because whoopsie isn't running When testing the proposed version of apport you'll want to revert the changes you made to whoopsie-upload-all. With the version of apport from -proposed you should no longer see the failure message for the apport- - autoreport.service. + autoreport.service. The best test case is just having an affected system + test the package from -proposed though. Regression Potential - We are clearly fixing something that was a mistake in the original service so there is little chance for regression. + We are clearly fixing something that was a mistake in the original service so there is little chance for regression. Hello, Attached image. Regards, -- Cristian Aravena Romero (caravena) ProblemType: BugDistroRelease: Ubuntu 18.10 Package: apport 2.20.10-0ubuntu7 Uname: Linux 4.18.3-041803-generic x86_64 ApportLog: ApportVersion: 2.20.10-0ubuntu7 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Sat Aug 18 11:48:00 2018 InstallationDate: Installed on 2017-10-13 (308 days ago) InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Alpha amd64 (20170926) PackageArchitecture: allSourcePackage: apport UpgradeStatus: No upgrade log present (probably fresh install) -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to apport in Ubuntu. https://bugs.launchpad.net/bugs/1787729 Title: apport-autoreport.service fails if whoopsie isn't running Status in apport package in Ubuntu: In Progress Status in apport source package in Cosmic: Triaged Bug description: Test Case - 1) install apport-noui 2) sudo service apport stop 3) modify /usr/share/apport/whoopsie-upload-all to exit(1) thereby recreating the situation where whoopsie isn't running. I did this by copying lines 159,160 to 161,162 and unindenting them. N.B. this isn't necessary if you are on a system where whoopsie is starting after apport. 4) touch /var/crash/my.crash 5) reboot 5) run 'systemctl status apport-autoreport.service' and observe it failed because whoopsie isn't running When testing the proposed version of apport you'll want to revert the changes you made to whoopsie-upload-all. With the version of apport from -proposed you should no longer see the failure message for the apport-autoreport.service. The best test case is just having an affected system test the package from -proposed though. Regression Potential We are clearly fixing something that was a mistake in the original service so there is little chance for regression. Hello, Attached image. Regards, -- Cristian Aravena Romero (caravena) ProblemType: BugDistroRelease: Ubuntu 18.10 Package: apport 2.20.10-0ubuntu7 Uname: Linux 4.18.3-041803-generic x86_64 ApportLog: ApportVersion: 2.20.10-0ubuntu7 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Sat Aug 18 11:48:00 2018 InstallationDate: Installed on 2017-10-13 (308 days ago) InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Alpha amd64 (20170926) PackageArchitecture: allSourcePackage: apport UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apport/+bug/1787729/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1812095] Re: console login loop after entering username followed by RETURN
Setting the password again you'll have a login, but you cant type in your password. After typing your login name followed by RETURN password is immediately left. Looks like the entered RETURN is kept and all subsequent calls see RETURN and just quit. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to shadow in Ubuntu. https://bugs.launchpad.net/bugs/1812095 Title: console login loop after entering username followed by RETURN Status in shadow package in Ubuntu: New Bug description: login: password: Just do nothing. About two seconds later ... login: password: login: password: login: password: After this being displayed three times: "Too many failure" or so and login is restarting. You cant login at all. Only solution: clear the password for the account you want to login with. ProblemType: Bug DistroRelease: Ubuntu 18.10 Package: login 1:4.5-1ubuntu1 ProcVersionSignature: Ubuntu 4.18.0-14.15-generic 4.18.20 Uname: Linux 4.18.0-14-generic x86_64 ApportVersion: 2.20.10-0ubuntu13.1 Architecture: amd64 CurrentDesktop: XFCE Date: Wed Jan 16 19:34:30 2019 InstallationDate: Installed on 2011-10-19 (2645 days ago) InstallationMedia: Xubuntu 11.10 "Oneiric Ocelot" - Release amd64 (20111012) SourcePackage: shadow UpgradeStatus: Upgraded to cosmic on 2018-11-03 (74 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/shadow/+bug/1812095/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1787729] Re: apport-autoreport.service fails if whoopsie isn't running
** Description changed: + Test Case + - + 1) install apport-noui + 2) sudo service apport stop + 3) modify /usr/share/apport/whoopsie-upload-all to exit(1) thereby recreating the situation where whoopsie isn't running. I did this by copying lines 159,160 to 161,162 and unindenting them. N.B. this isn't necessary if you are on a system where whoopsie is starting after apport. + 4) touch /var/crash/my.crash + 5) reboot + 5) run 'systemctl status apport-autoreport.service' and observe it failed because whoopsie isn't running + + When testing the proposed version of apport you'll want to revert the + changes you made to whoopsie-upload-all. With the version of apport from + -proposed you should no longer see the failure message for the apport- + autoreport.service. + + Regression Potential + + We are clearly fixing something that was a mistake in the original service so there is little chance for regression. + Hello, Attached image. Regards, -- Cristian Aravena Romero (caravena) - ProblemType: Bug - DistroRelease: Ubuntu 18.10 + ProblemType: BugDistroRelease: Ubuntu 18.10 Package: apport 2.20.10-0ubuntu7 Uname: Linux 4.18.3-041803-generic x86_64 ApportLog: - + ApportVersion: 2.20.10-0ubuntu7 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Sat Aug 18 11:48:00 2018 InstallationDate: Installed on 2017-10-13 (308 days ago) InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Alpha amd64 (20170926) - PackageArchitecture: all - SourcePackage: apport + PackageArchitecture: allSourcePackage: apport UpgradeStatus: No upgrade log present (probably fresh install) -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to apport in Ubuntu. https://bugs.launchpad.net/bugs/1787729 Title: apport-autoreport.service fails if whoopsie isn't running Status in apport package in Ubuntu: In Progress Status in apport source package in Cosmic: Triaged Bug description: Test Case - 1) install apport-noui 2) sudo service apport stop 3) modify /usr/share/apport/whoopsie-upload-all to exit(1) thereby recreating the situation where whoopsie isn't running. I did this by copying lines 159,160 to 161,162 and unindenting them. N.B. this isn't necessary if you are on a system where whoopsie is starting after apport. 4) touch /var/crash/my.crash 5) reboot 5) run 'systemctl status apport-autoreport.service' and observe it failed because whoopsie isn't running When testing the proposed version of apport you'll want to revert the changes you made to whoopsie-upload-all. With the version of apport from -proposed you should no longer see the failure message for the apport-autoreport.service. Regression Potential We are clearly fixing something that was a mistake in the original service so there is little chance for regression. Hello, Attached image. Regards, -- Cristian Aravena Romero (caravena) ProblemType: BugDistroRelease: Ubuntu 18.10 Package: apport 2.20.10-0ubuntu7 Uname: Linux 4.18.3-041803-generic x86_64 ApportLog: ApportVersion: 2.20.10-0ubuntu7 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Sat Aug 18 11:48:00 2018 InstallationDate: Installed on 2017-10-13 (308 days ago) InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Alpha amd64 (20170926) PackageArchitecture: allSourcePackage: apport UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apport/+bug/1787729/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1812095] [NEW] console login loop after entering username followed by RETURN
Public bug reported: login: password: Just do nothing. About two seconds later ... login: password: login: password: login: password: After this being displayed three times: "Too many failure" or so and login is restarting. You cant login at all. Only solution: clear the password for the account you want to login with. ProblemType: Bug DistroRelease: Ubuntu 18.10 Package: login 1:4.5-1ubuntu1 ProcVersionSignature: Ubuntu 4.18.0-14.15-generic 4.18.20 Uname: Linux 4.18.0-14-generic x86_64 ApportVersion: 2.20.10-0ubuntu13.1 Architecture: amd64 CurrentDesktop: XFCE Date: Wed Jan 16 19:34:30 2019 InstallationDate: Installed on 2011-10-19 (2645 days ago) InstallationMedia: Xubuntu 11.10 "Oneiric Ocelot" - Release amd64 (20111012) SourcePackage: shadow UpgradeStatus: Upgraded to cosmic on 2018-11-03 (74 days ago) ** Affects: shadow (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug cosmic -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to shadow in Ubuntu. https://bugs.launchpad.net/bugs/1812095 Title: console login loop after entering username followed by RETURN Status in shadow package in Ubuntu: New Bug description: login: password: Just do nothing. About two seconds later ... login: password: login: password: login: password: After this being displayed three times: "Too many failure" or so and login is restarting. You cant login at all. Only solution: clear the password for the account you want to login with. ProblemType: Bug DistroRelease: Ubuntu 18.10 Package: login 1:4.5-1ubuntu1 ProcVersionSignature: Ubuntu 4.18.0-14.15-generic 4.18.20 Uname: Linux 4.18.0-14-generic x86_64 ApportVersion: 2.20.10-0ubuntu13.1 Architecture: amd64 CurrentDesktop: XFCE Date: Wed Jan 16 19:34:30 2019 InstallationDate: Installed on 2011-10-19 (2645 days ago) InstallationMedia: Xubuntu 11.10 "Oneiric Ocelot" - Release amd64 (20111012) SourcePackage: shadow UpgradeStatus: Upgraded to cosmic on 2018-11-03 (74 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/shadow/+bug/1812095/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1787729] Re: apport-autoreport.service fails if whoopsie isn't running
** Also affects: apport (Ubuntu Cosmic) Importance: Undecided Status: New ** Changed in: apport (Ubuntu Cosmic) Status: New => Triaged ** Changed in: apport (Ubuntu Cosmic) Importance: Undecided => High -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to apport in Ubuntu. https://bugs.launchpad.net/bugs/1787729 Title: apport-autoreport.service fails if whoopsie isn't running Status in apport package in Ubuntu: In Progress Status in apport source package in Cosmic: Triaged Bug description: Hello, Attached image. Regards, -- Cristian Aravena Romero (caravena) ProblemType: Bug DistroRelease: Ubuntu 18.10 Package: apport 2.20.10-0ubuntu7 Uname: Linux 4.18.3-041803-generic x86_64 ApportLog: ApportVersion: 2.20.10-0ubuntu7 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Sat Aug 18 11:48:00 2018 InstallationDate: Installed on 2017-10-13 (308 days ago) InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Alpha amd64 (20170926) PackageArchitecture: all SourcePackage: apport UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apport/+bug/1787729/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1787729] Re: apport-autoreport.service fails if whoopsie isn't running
Excellent Brian! Thank you for your work! -- Cristian Aravena Romero (caravena) -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to apport in Ubuntu. https://bugs.launchpad.net/bugs/1787729 Title: apport-autoreport.service fails if whoopsie isn't running Status in apport package in Ubuntu: In Progress Status in apport source package in Cosmic: Triaged Bug description: Hello, Attached image. Regards, -- Cristian Aravena Romero (caravena) ProblemType: Bug DistroRelease: Ubuntu 18.10 Package: apport 2.20.10-0ubuntu7 Uname: Linux 4.18.3-041803-generic x86_64 ApportLog: ApportVersion: 2.20.10-0ubuntu7 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Sat Aug 18 11:48:00 2018 InstallationDate: Installed on 2017-10-13 (308 days ago) InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Alpha amd64 (20170926) PackageArchitecture: all SourcePackage: apport UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apport/+bug/1787729/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1787729] Re: apport-autoreport.service fails if whoopsie isn't running
** Summary changed: - [FAILED] Failed to start Process error reports when automatic reporting is enabled. + apport-autoreport.service fails if whoopsie isn't running -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to apport in Ubuntu. https://bugs.launchpad.net/bugs/1787729 Title: apport-autoreport.service fails if whoopsie isn't running Status in apport package in Ubuntu: In Progress Status in apport source package in Cosmic: Triaged Bug description: Hello, Attached image. Regards, -- Cristian Aravena Romero (caravena) ProblemType: Bug DistroRelease: Ubuntu 18.10 Package: apport 2.20.10-0ubuntu7 Uname: Linux 4.18.3-041803-generic x86_64 ApportLog: ApportVersion: 2.20.10-0ubuntu7 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Sat Aug 18 11:48:00 2018 InstallationDate: Installed on 2017-10-13 (308 days ago) InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Alpha amd64 (20170926) PackageArchitecture: all SourcePackage: apport UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apport/+bug/1787729/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1811531] Re: remote execution vulnerability
** Changed in: zeromq3 (Ubuntu) Status: New => Fix Committed -- 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/1811531 Title: remote execution vulnerability Status in zeromq3 package in Ubuntu: Fix Committed Status in zeromq3 package in Debian: Fix Released Status in zeromq package in Suse: Unknown Bug description: Dear Maintainer, A remote execution vulnerability has been reported in zeromq. Full details can be found on the upstream issue tracker [1]. The issue is fixed in upstream version v4.3.1, just released, or with the attached patch which is targeted for v4.2.5 (bionic and cosmic). The latest version will hopefully arrive in disco via debian unstable soon, but I would recommend patching older releases. As mentioned in the upstream tracker and the changelog, the issue can be mitigated by ASLR and by authentication via CURVE/GSSAPI. As far as I am aware no CVEs have been assigned nor have been requested as of now. [1] https://github.com/zeromq/libzmq/issues/3351 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/zeromq3/+bug/1811531/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1760349] Re: Cannot log in to public open Wifi connection because not being redirected to login site
** Description changed: I have noticed that Kubuntu 18.04 (Bionic Beaver) does not login to public Wifi hotspots without wifi security, that require login through a web page. I don't know if this is reproducible on arbitrary public networks, or only on the few I tried. The solution was as follows: - Create file /etc/NetworkManager/conf.d/20-connectivity-debian.conf (you'll need root or sudo). - Add the following lines as recommended by Guruprasad (https://www.lguruprasad.in/blog/2015/07/21/enabling-captive-portal-detection-in-gnome-3-14-on-debian-jessie/): [connectivity] uri=http://network-test.debian.org/nm response=NetworkManager is online interval=300 - Restart the network manager with service network-manager restart (will need sudo or root again). This is a very annoying and unnecessary default behavior it seems. Maybe a good idea to fix it. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: network-manager 1.10.6-2ubuntu1 ProcVersionSignature: Ubuntu 4.15.0-13.14-generic 4.15.10 Uname: Linux 4.15.0-13-generic x86_64 ApportVersion: 2.20.9-0ubuntu2 Architecture: amd64 CurrentDesktop: KDE Date: Sat Mar 31 22:48:21 2018 IfupdownConfig: - # interfaces(5) file used by ifup(8) and ifdown(8) - auto lo - iface lo inet loopback + # interfaces(5) file used by ifup(8) and ifdown(8) + auto lo + iface lo inet loopback InstallationDate: Installed on 2018-02-18 (41 days ago) InstallationMedia: Kubuntu 18.04 LTS "Bionic Beaver" - Alpha amd64 (20180218) IpRoute: - default via 10.129.249.1 dev wlp1s0 proto dhcp metric 600 - 10.129.249.0/24 dev wlp1s0 proto kernel scope link src 10.129.249.35 metric 600 - 169.254.0.0/16 dev wlp1s0 scope link metric 1000 + default via 10.129.249.1 dev wlp1s0 proto dhcp metric 600 + 10.129.249.0/24 dev wlp1s0 proto kernel scope link src 10.129.249.35 metric 600 + 169.254.0.0/16 dev wlp1s0 scope link metric 1000 NetworkManager.state: - [main] - NetworkingEnabled=true - WirelessEnabled=true - WWANEnabled=true + [main] + NetworkingEnabled=true + WirelessEnabled=true + WWANEnabled=true ProcEnviron: - LANGUAGE= - PATH=(custom, no user) - XDG_RUNTIME_DIR= - LANG=de_DE.UTF-8 - SHELL=/bin/bash + LANGUAGE= + PATH=(custom, no user) + XDG_RUNTIME_DIR= + LANG=de_DE.UTF-8 + SHELL=/bin/bash RfKill: - 0: phy0: Wireless LAN - Soft blocked: no - Hard blocked: no + 0: phy0: Wireless LAN + Soft blocked: no + Hard blocked: no SourcePackage: network-manager UpgradeStatus: No upgrade log present (probably fresh install) nmcli-dev: - DEVICE TYPE STATE DBUS-PATH CONNECTION CON-UUID CON-PATH - wlp1s0 wifi connected /org/freedesktop/NetworkManager/Devices/2 SuedtirolSpot_1 c4464785-b548-4655-b06b-48a0aec06a87 /org/freedesktop/NetworkManager/ActiveConnection/3 - lo loopback unmanaged /org/freedesktop/NetworkManager/Devices/1 -- ---- + DEVICE TYPE STATE DBUS-PATH CONNECTION CON-UUID CON-PATH + wlp1s0 wifi connected /org/freedesktop/NetworkManager/Devices/2 SuedtirolSpot_1 c4464785-b548-4655-b06b-48a0aec06a87 /org/freedesktop/NetworkManager/ActiveConnection/3 + lo loopback unmanaged /org/freedesktop/NetworkManager/Devices/1 -- ---- nmcli-nm: - RUNNING VERSION STATE STARTUP CONNECTIVITY NETWORKING WIFI-HW WIFI WWAN-HW WWAN - running 1.10.6 connected started full enabled enabled enabled enabled enabled + RUNNING VERSION STATE STARTUP CONNECTIVITY NETWORKING WIFI-HW WIFI WWAN-HW WWAN + running 1.10.6 connected started full enabled enabled enabled enabled enabled -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to network-manager in Ubuntu. https://bugs.launchpad.net/bugs/1760349 Title: Cannot log in to public open Wifi connection because not being redirected to login site Status in network-manager package in Ubuntu: Confirmed Bug description: I have noticed that Kubuntu 18.04 (Bionic Beaver) does not login to public Wifi hotspots without wifi security, that require login through a web page. I don't know if this is reproducible on arbitrary public networks, or only on the few I tried. The solution was as follows: - Create file /etc/NetworkManager/conf.d/20-connectivity-debian.conf (you'll need root or sudo). - Add the following lines as recommended by Guruprasad (https://www.lguruprasad.in/blog/2015/07/21/enabling-captive-portal-detection-in-gnome-3-14-on-debian-jessie/): [connectivity] uri=http://network-test.debian.org/nm response=NetworkManager is
[Touch-packages] [Bug 1787729] Re: [FAILED] Failed to start Process error reports when automatic reporting is enabled.
** Changed in: apport (Ubuntu) Assignee: (unassigned) => Brian Murray (brian-murray) ** Changed in: apport (Ubuntu) Status: Triaged => In Progress -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to apport in Ubuntu. https://bugs.launchpad.net/bugs/1787729 Title: apport-autoreport.service fails if whoopsie isn't running Status in apport package in Ubuntu: In Progress Bug description: Hello, Attached image. Regards, -- Cristian Aravena Romero (caravena) ProblemType: Bug DistroRelease: Ubuntu 18.10 Package: apport 2.20.10-0ubuntu7 Uname: Linux 4.18.3-041803-generic x86_64 ApportLog: ApportVersion: 2.20.10-0ubuntu7 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Sat Aug 18 11:48:00 2018 InstallationDate: Installed on 2017-10-13 (308 days ago) InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Alpha amd64 (20170926) PackageArchitecture: all SourcePackage: apport UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apport/+bug/1787729/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1811531]
Thanks for opening the ticket and attaching the patch. I've generated a new version for bionic and cosmic, both can be found here: https://launchpad.net/~ubuntu-security-proposed/+archive/ubuntu/ppa/+packages?field.name_filter=zeromq3 Would anyone mind testing it before we release it? Thanks -- 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/1811531 Title: remote execution vulnerability Status in zeromq3 package in Ubuntu: New Status in zeromq3 package in Debian: Fix Released Status in zeromq package in Suse: Unknown Bug description: Dear Maintainer, A remote execution vulnerability has been reported in zeromq. Full details can be found on the upstream issue tracker [1]. The issue is fixed in upstream version v4.3.1, just released, or with the attached patch which is targeted for v4.2.5 (bionic and cosmic). The latest version will hopefully arrive in disco via debian unstable soon, but I would recommend patching older releases. As mentioned in the upstream tracker and the changelog, the issue can be mitigated by ASLR and by authentication via CURVE/GSSAPI. As far as I am aware no CVEs have been assigned nor have been requested as of now. [1] https://github.com/zeromq/libzmq/issues/3351 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/zeromq3/+bug/1811531/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1811531]
Thanks for opening the ticket and attaching the patch. -- 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/1811531 Title: remote execution vulnerability Status in zeromq3 package in Ubuntu: New Status in zeromq3 package in Debian: Fix Released Status in zeromq package in Suse: Unknown Bug description: Dear Maintainer, A remote execution vulnerability has been reported in zeromq. Full details can be found on the upstream issue tracker [1]. The issue is fixed in upstream version v4.3.1, just released, or with the attached patch which is targeted for v4.2.5 (bionic and cosmic). The latest version will hopefully arrive in disco via debian unstable soon, but I would recommend patching older releases. As mentioned in the upstream tracker and the changelog, the issue can be mitigated by ASLR and by authentication via CURVE/GSSAPI. As far as I am aware no CVEs have been assigned nor have been requested as of now. [1] https://github.com/zeromq/libzmq/issues/3351 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/zeromq3/+bug/1811531/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1778844] Re: nvme multipath does not report path relationships
I have pushed a version of initramfs-tools to my ppa that seems to fix the problem. Can IBM test it? add-apt-repository ppa:cascardo/kdump2 It's a version for bionic. Only initramfs-tools should come from this source. kdump-tools and makedumpfile should be from bionic-updates or bionic. After that, remove the initrd images from /var/lib/kdump/, reboot, then test the crash. So: add-apt-repository ppa:cascardo/kdump2 apt install initramfs-tools rm /var/lib/kdump/initr* reboot After reboot: echo 1 > /proc/sys/kernel/sysrq echo c > /proc/sysrq-trigger -- 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/1778844 Title: nvme multipath does not report path relationships Status in The Ubuntu-power-systems project: In Progress Status in initramfs-tools package in Ubuntu: Confirmed Status in linux package in Ubuntu: Confirmed Status in makedumpfile package in Ubuntu: Invalid Status in initramfs-tools source package in Bionic: Confirmed Status in linux source package in Bionic: Confirmed Status in makedumpfile source package in Bionic: Invalid Status in initramfs-tools source package in Cosmic: Confirmed Status in linux source package in Cosmic: Confirmed Status in makedumpfile source package in Cosmic: Invalid Bug description: Problem Description: === After triggering crash ,kdump is not working & system enters into initramfs state Steps to re-create: == >. woo is installed ubuntu180401 kernel root@woo:~# uname -a Linux woo 4.15.0-23-generic #25-Ubuntu SMP Wed May 23 17:59:00 UTC 2018 ppc64le ppc64le ppc64le GNU/Linux root@woo:~# >. Crashkernel value as below root@woo:~# free -h totalusedfree shared buff/cache available Mem: 503G2.0G501G 13M279M 499G Swap: 2.0G 0B2.0G root@woo:~# cat /proc/cmdline root=UUID=45bb7eb2-4c61-425d-8bf9-4e6f16829ddb ro splash quiet crashkernel=8192M > kdump status root@woo:~# kdump-config status current state : ready to kdump root@woo:~# kdump-config show DUMP_MODE:kdump USE_KDUMP:1 KDUMP_SYSCTL: kernel.panic_on_oops=1 KDUMP_COREDIR:/var/crash crashkernel addr: /var/lib/kdump/vmlinuz: symbolic link to /boot/vmlinux-4.15.0-23-generic kdump initrd: /var/lib/kdump/initrd.img: symbolic link to /var/lib/kdump/initrd.img-4.15.0-23-generic current state:ready to kdump kexec command: /sbin/kexec -p --command-line="root=UUID=45bb7eb2-4c61-425d-8bf9-4e6f16829ddb ro splash quiet nr_cpus=1 systemd.unit=kdump-tools.service irqpoll noirqdistrib nousb" --initrd=/var/lib/kdump/initrd.img /var/lib/kdump/vmlinuz root@woo:~# dmesg | grep Reser [0.00] Reserving 8192MB of memory at 128MB for crashkernel (System RAM: 524288MB) [0.00] cma: Reserved 26224 MiB at 0x20399500 [3.545490] Copyright (C) 2017-2018 Broadcom. All Rights Reserved. The term "Broadcom" refers to Broadcom Limited and/or its subsidiaries. > Triggered crash root@woo:~# echo 1 > /proc/sys/kernel/sysrq root@woo:~# echo c > /proc/sysrq-trigger [ 73.056308] sysrq: SysRq : Trigger a crash [ 73.056357] Unable to handle kernel paging request for data at address 0x [ 73.056459] Faulting instruction address: 0xc07f24c8 [ 73.056543] Oops: Kernel access of bad area, sig: 11 [#1] [ 73.056609] LE SMP NR_CPUS=2048 NUMA PowerNV [ 73.056668] Modules linked in: rdma_ucm(OE) ib_ucm(OE) rdma_cm(OE) iw_cm(OE) ib_ipoib(OE) ib_cm(OE) ib_uverbs(OE) ib_umad(OE) esp6_offload esp6 esp4_offload esp4 xfrm_algo mlx5_fpga_tools(OE) mlx4_en(OE) mlx4_ib(OE) mlx4_core(OE) rpcsec_gss_krb5 nfsv4 nfs fscache binfmt_misc idt_89hpesx vmx_crypto crct10dif_vpmsum ofpart cmdlinepart ipmi_powernv ipmi_devintf at24 powernv_flash ipmi_msghandler ibmpowernv mtd opal_prd uio_pdrv_genirq uio nfsd auth_rpcgss nfs_acl lockd sch_fq_codel grace sunrpc knem(OE) ip_tables x_tables autofs4 btrfs xor zstd_compress raid6_pq mlx5_ib(OE) ib_core(OE) nouveau lpfc ast i2c_algo_bit ttm mlx5_core(OE) drm_kms_helper mlxfw(OE) nvmet_fc devlink syscopyarea nvmet mlx_compat(OE) sysfillrect cxl nvme_fc sysimgblt fb_sys_fops nvme_fabrics nvme ahci crc32c_vpmsum drm scsi_transport_fc [ 73.057601] tg3 libahci nvme_core pnv_php [ 73.057652] CPU: 44 PID: 4626 Comm: bash Tainted: G OE 4.15.0-23-generic #25-Ubuntu [ 73.057767] NIP: c07f24c8 LR: c07f3568 CTR: c07f24a0 [ 73.057868] REGS: c03f8269f9f0 TRAP: 0300 Tainted: G OE (4.15.0-23-generic) [ 73.057986] MSR: 90009033 CR: 2822 XER: 2004 [ 73.058099] CFAR: c07f3564 DAR: DSISR: 4200 SOFTE: 1 [ 73.058099] GPR00: c00
[Touch-packages] [Bug 1793876] Re: software-properties-qt/kde does not show in menus
(unsubscribing sponsors, it's not ready to be uploaded) -- 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/1793876 Title: software-properties-qt/kde does not show in menus Status in software-properties package in Ubuntu: Confirmed Bug description: Cosmic and Bionic Desktop file sets: NoDisplay=true resulting in no software sources menu entry in KDE menu. This was probably just about ok when Plasma Discover was able to launch this via a menu item in its options, but at least for Plasma 5.13 this is currently broken, and Discover's built-in source selection has further issues. Plus many users decide not to use Discover at all, and even uninstall it altogether. Not withstanding all that, it is just desirable that someone can just type "software" or "sources" in to the search box in Plasma's main menu and find the menu item/launcher for this and use software- properties without having to go a more complicated path. Solution is simply removing the "NoDisplay=true" line from the .desktop file To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/software-properties/+bug/1793876/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1658921] Re: NetworkManager does not manage wired connection
*** This bug is a duplicate of bug 1676547 *** https://bugs.launchpad.net/bugs/1676547 This issue is still alive and well in 2019. I encountered it while upgrading from 18.04 to 18.10. Advice from comment six resolved it, but it wasted several hours of my time. Please apply a fix or at least more thorough log messages so that medium to low skill users like myself can solve this problem for themselves. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to network-manager in Ubuntu. https://bugs.launchpad.net/bugs/1658921 Title: NetworkManager does not manage wired connection Status in network-manager package in Ubuntu: Confirmed Bug description: NetworkManager does not manage my wired eth0 connection, no matter how I set /etc/network/interfaces or /etc/NetworkManager/NetworkManager.conf Using ubuntu 16.04, /etc/network/interfaces only managed lo, and [ifupdown] section of NetworkManager.conf had set managed=false. With these same settings, after upgrading to ubuntu 16.10, eth0 appears as unmanaged in nm-applet. If I modify /etc/network/interfaces and add auto eth0 iface eth0 inet dhcp And set managed=true in NetworkManager.conf [ifupdown] section, eth0 is still unmanaged despite it does get an IP from DHCP server. This is happening in my five computers (two laptops and three desktops). To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1658921/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1644996] Re: logrotate config uses syslog group
This bug doesn't exist in Debian, it's only Ubuntu related workaround for Ubuntu 14.04 (Trusty), see LP bug #1258202 logrotate (3.8.6-1ubuntu2) trusty; urgency=low * debian/logrotate.conf: use group 'syslog' by default when rotating logs, otherwise logrotate will refuse to rotate logs in /var/log whose owning group is now syslog instead of root. LP: #1258202. -- Steve LangasekThu, 05 Dec 2013 10:35:47 -0800 Ubuntu developers, please change /etc/logrotate.conf line su root syslog to su root adm Or maybe we can remove this line from /etc/logrotate.conf , because in Debian logrotate package there are no such line since 2013 ... ** Tags added: bionic regression-release xenial -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to logrotate in Ubuntu. https://bugs.launchpad.net/bugs/1644996 Title: logrotate config uses syslog group Status in logrotate package in Ubuntu: Confirmed Bug description: The default logrotate config uses the "syslog" group. > # use the syslog group by default, since this is the owning group > # of /var/log/syslog. > su root syslog This is not correct anymore since 16.04, because: 1. "syslog" group doesn't exist on a stock Ubuntu 16.04 system, it only gets installed via rsyslog 2. The owning group is actually "adm". This results in logrotate terminating with the following error during cron.daily run: run-parts -v /etc/cron.daily run-parts: executing /etc/cron.daily/logrotate error: /etc/logrotate.conf:7 unknown group 'syslog' And can be fixed by changing syslog to adm group. This is not present when rsyslog is installed, but only because that package creates the syslog group. This is a common bug in lighter environments, like Docker, where syslog-ng is a common choice instead of rsyslog, like in this issue: https://github.com/phusion/baseimage-docker/issues/338 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/logrotate/+bug/1644996/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1811902] Re: Echo cancelation should be enabled by default
I agree with your point so won't be opening a bug to change the defaults. But it should be easy to enable somewhere in the GUI sound settings at least for specific applications. Video conferencing like appear.in is only really usable with headphones because of this. Adjusting text config files is not a good user experience. And I suspect most people only care about the microphone because of these kinds of uses. According to this: https://gitlab.freedesktop.org/pulseaudio/pulseaudio/issues/196 It's possible for apps to request echo cancelation with 'filter.want =echo-cancel' so maybe this is actually a bug in firefox? -- 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/1811902 Title: Echo cancelation should be enabled by default Status in pulseaudio package in Ubuntu: Incomplete Bug description: Echo cancellation is a basic feature for anything where you are using a video or audio conference. According to instructions like these: https://bugs.launchpad.net/elementaryos/+bug/1682253 https://wiki.archlinux.org/index.php/PulseAudio/Troubleshooting#Enable_Echo/Noise-Cancellation https://medium.com/@tim_73574/ubuntu-microphone-noise-cancellation-and-volume-auto-adjusted-issue-2c79678542bb There is now enough support in pulseaudio to do this well, but it's just not enabled by default. Users shouldn't need to fish around for strange things to add to config files. More complete defaults should be included. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: pulseaudio 1:11.1-1ubuntu7.1 ProcVersionSignature: Ubuntu 4.15.0-43.46-generic 4.15.18 Uname: Linux 4.15.0-43-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.5 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/pcmC0D0p: pedrocr2684 F...m pulseaudio /dev/snd/controlC0: pedrocr2684 F pulseaudio CurrentDesktop: ubuntu:GNOME Date: Tue Jan 15 23:45:10 2019 InstallationDate: Installed on 2018-05-31 (229 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426) SourcePackage: pulseaudio UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 03/22/2018 dmi.bios.vendor: LENOVO dmi.bios.version: N1CET66W (1.34 ) dmi.board.asset.tag: Not Available dmi.board.name: 20FAS5TS00 dmi.board.vendor: LENOVO dmi.board.version: SDK0J40697 WIN dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: None dmi.modalias: dmi:bvnLENOVO:bvrN1CET66W(1.34):bd03/22/2018:svnLENOVO:pn20FAS5TS00:pvrThinkPadT460s:rvnLENOVO:rn20FAS5TS00:rvrSDK0J40697WIN:cvnLENOVO:ct10:cvrNone: dmi.product.family: ThinkPad T460s dmi.product.name: 20FAS5TS00 dmi.product.version: ThinkPad T460s dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1811902/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1811248] Re: systemd--networkd mounts denied for lxc guest
This issue accelerating/cascading to the extent that that the lxc arch linux guest is now entirely dead https://bugs.archlinux.org/task/61428 -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to apparmor in Ubuntu. https://bugs.launchpad.net/bugs/1811248 Title: systemd--networkd mounts denied for lxc guest Status in apparmor package in Ubuntu: New Bug description: Host unbuntu cosmic | lxc 3.0.3 | aa 2.12 | systemd 239-7 Guest Arch Linux | systemd 240.0 After having upgraded in the guest systemd from 239.370 to 240.0 the host's AA is exhibiting > audit: type=1400 audit(1547125168.853:722): apparmor="DENIED" operation="mount" info="failed flags match" error=-13 profile="lxc- container-default-cgns" name="/" pid=8426 comm="(networkd)" flags="rw, rslave" and the guest > systemd-networkd.service: Failed to set up mount namespacing: Permission denied > systemd-networkd.service: Failed at step NAMESPACE spawning /usr/lib/systemd/systemd-networkd: Permission denied According to lxc bug tracker https://github.com/lxc/lxc/issues/2778 > While we'd like to allow such mounts we cannot do so until the apparmor_parser is fixed to handle them correctly. other cross references https://github.com/systemd/systemd/issues/11371 https://bugs.archlinux.org/task/61313 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apparmor/+bug/1811248/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1778984] Re: Parse error of /etc/apparmor.d/tunables/home.d/ubuntu after unattended-upgrades
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: apparmor (Ubuntu) Status: New => Confirmed -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to apparmor in Ubuntu. https://bugs.launchpad.net/bugs/1778984 Title: Parse error of /etc/apparmor.d/tunables/home.d/ubuntu after unattended-upgrades Status in apparmor package in Ubuntu: Confirmed Bug description: Environment: DISTRIB_ID=Ubuntu DISTRIB_RELEASE=16.04 DISTRIB_CODENAME=xenial DISTRIB_DESCRIPTION="Ubuntu 16.04.2 LTS" NAME="Ubuntu" VERSION="16.04.2 LTS (Xenial Xerus)" ID=ubuntu ID_LIKE=debian PRETTY_NAME="Ubuntu 16.04.2 LTS" VERSION_ID="16.04" HOME_URL="http://www.ubuntu.com/"; SUPPORT_URL="http://help.ubuntu.com/"; BUG_REPORT_URL="http://bugs.launchpad.net/ubuntu/"; VERSION_CODENAME=xenial UBUNTU_CODENAME=xenial Docker Details: Client: Version: 17.06.2-ce API version: 1.30 Go version: go1.8.3 Git commit: cec0b72 Built:Tue Sep 5 20:00:17 2017 OS/Arch: linux/amd64 Server: Version: 17.06.2-ce API version: 1.30 (minimum version 1.12) Go version: go1.8.3 Git commit: cec0b72 Built:Tue Sep 5 19:59:11 2017 OS/Arch: linux/amd64 Experimental: false Problem: Docker containers will not restart due error /etc/apparmor.d/tunables/home.d/ubuntu at line 7: Found unexpected character: '' How to recreate problem: 1. initiate unattended upgrades: sudo unattened-upgrades -d 2. Wait until Apparmor is installing... Installing new version of config file /etc/init.d/apparmor ... Installing new version of config file /etc/init/apparmor.conf ... update-rc.d: warning: start and stop actions are no longer supported; falling back to defaults Skipping profile in /etc/apparmor.d/disable: usr.sbin.rsyslogd 3. Pull the power from the computer to simulate a complete power failure. 4. Plug the system back in and try to restart a docker container using "sudo docker restart Error upon attempting to restart docker container: Error response from daemon: Cannot restart container updater-nodejs: AppArmor enabled on system but the docker-default profile could not be loaded: running /sbin/apparmor_parser apparmor_parser -Kr /var/lib/docker/tmp/docker-default480199246 failed with output: AppArmor parser error for /var/lib/docker/tmp/docker-default480199246 in /etc/apparmor.d/tunables/home.d/ubuntu at line 7: Found unexpected character: '' error: exit status 1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apparmor/+bug/1778984/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1778984] Re: Parse error of /etc/apparmor.d/tunables/home.d/ubuntu after unattended-upgrades
I followed previous hint , but issue still occurs. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to apparmor in Ubuntu. https://bugs.launchpad.net/bugs/1778984 Title: Parse error of /etc/apparmor.d/tunables/home.d/ubuntu after unattended-upgrades Status in apparmor package in Ubuntu: Confirmed Bug description: Environment: DISTRIB_ID=Ubuntu DISTRIB_RELEASE=16.04 DISTRIB_CODENAME=xenial DISTRIB_DESCRIPTION="Ubuntu 16.04.2 LTS" NAME="Ubuntu" VERSION="16.04.2 LTS (Xenial Xerus)" ID=ubuntu ID_LIKE=debian PRETTY_NAME="Ubuntu 16.04.2 LTS" VERSION_ID="16.04" HOME_URL="http://www.ubuntu.com/"; SUPPORT_URL="http://help.ubuntu.com/"; BUG_REPORT_URL="http://bugs.launchpad.net/ubuntu/"; VERSION_CODENAME=xenial UBUNTU_CODENAME=xenial Docker Details: Client: Version: 17.06.2-ce API version: 1.30 Go version: go1.8.3 Git commit: cec0b72 Built:Tue Sep 5 20:00:17 2017 OS/Arch: linux/amd64 Server: Version: 17.06.2-ce API version: 1.30 (minimum version 1.12) Go version: go1.8.3 Git commit: cec0b72 Built:Tue Sep 5 19:59:11 2017 OS/Arch: linux/amd64 Experimental: false Problem: Docker containers will not restart due error /etc/apparmor.d/tunables/home.d/ubuntu at line 7: Found unexpected character: '' How to recreate problem: 1. initiate unattended upgrades: sudo unattened-upgrades -d 2. Wait until Apparmor is installing... Installing new version of config file /etc/init.d/apparmor ... Installing new version of config file /etc/init/apparmor.conf ... update-rc.d: warning: start and stop actions are no longer supported; falling back to defaults Skipping profile in /etc/apparmor.d/disable: usr.sbin.rsyslogd 3. Pull the power from the computer to simulate a complete power failure. 4. Plug the system back in and try to restart a docker container using "sudo docker restart Error upon attempting to restart docker container: Error response from daemon: Cannot restart container updater-nodejs: AppArmor enabled on system but the docker-default profile could not be loaded: running /sbin/apparmor_parser apparmor_parser -Kr /var/lib/docker/tmp/docker-default480199246 failed with output: AppArmor parser error for /var/lib/docker/tmp/docker-default480199246 in /etc/apparmor.d/tunables/home.d/ubuntu at line 7: Found unexpected character: '' error: exit status 1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apparmor/+bug/1778984/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1811999] [NEW] [USB-Audio - Audioengine D3, playback] fails after a while (a second)
Public bug reported: USB DAC stops playing sound after a second. I had problem with kernel 4.15. So, I tried upgrading to 4.19 but still issue persists. I think, we might need to add it to sound/usb/quirks.c I see following in dmesg [ 5937.978117] usb 1-1.4.2: USB disconnect, device number 16 [ 5955.721597] usb 1-1.4.1: new full-speed USB device number 17 using xhci_hcd [ 5956.302910] usb 1-1.4.1: New USB device found, idVendor=2912, idProduct=120b, bcdDevice= 1.0c [ 5956.302917] usb 1-1.4.1: New USB device strings: Mfr=1, Product=2, SerialNumber=3 [ 5956.302921] usb 1-1.4.1: Product: Audioengine D3 [ 5956.302926] usb 1-1.4.1: Manufacturer: Audioengine [ 5956.302929] usb 1-1.4.1: SerialNumber: Audioengine [ 5956.320621] usb 1-1.4.1: 1:1: cannot get freq at ep 0x1 [ 5956.920844] usb 1-1.4.1: 1:1: cannot get freq at ep 0x1 [ 5956.938929] usb 1-1.4.1: 1:1: cannot get freq at ep 0x1 And lsusb -v has following entry for the device. Bus 001 Device 017: ID 2912:120b Couldn't open device, some information will be missing Device Descriptor: bLength18 bDescriptorType 1 bcdUSB 1.00 bDeviceClass0 (Defined at Interface level) bDeviceSubClass 0 bDeviceProtocol 0 bMaxPacketSize0 8 idVendor 0x2912 idProduct 0x120b bcdDevice1.0c iManufacturer 1 iProduct2 iSerial 3 bNumConfigurations 1 Configuration Descriptor: bLength 9 bDescriptorType 2 wTotalLength 131 bNumInterfaces 2 bConfigurationValue 1 iConfiguration 0 bmAttributes 0x80 (Bus Powered) MaxPower 200mA Interface Descriptor: bLength 9 bDescriptorType 4 bInterfaceNumber0 bAlternateSetting 0 bNumEndpoints 0 bInterfaceClass 1 Audio bInterfaceSubClass 1 Control Device bInterfaceProtocol 0 iInterface 0 AudioControl Interface Descriptor: bLength 9 bDescriptorType36 bDescriptorSubtype 1 (HEADER) bcdADC 1.00 wTotalLength 43 bInCollection 1 baInterfaceNr( 0) 1 AudioControl Interface Descriptor: bLength12 bDescriptorType36 bDescriptorSubtype 2 (INPUT_TERMINAL) bTerminalID 5 wTerminalType 0x0101 USB Streaming bAssocTerminal 0 bNrChannels 2 wChannelConfig 0x0003 Left Front (L) Right Front (R) iChannelNames 0 iTerminal 0 AudioControl Interface Descriptor: bLength13 bDescriptorType36 bDescriptorSubtype 6 (FEATURE_UNIT) bUnitID 7 bSourceID 5 bControlSize2 bmaControls( 0) 0x01 bmaControls( 0) 0x00 Mute Control bmaControls( 1) 0x02 bmaControls( 1) 0x00 Volume Control bmaControls( 2) 0x02 bmaControls( 2) 0x00 Volume Control iFeature0 AudioControl Interface Descriptor: bLength 9 bDescriptorType36 bDescriptorSubtype 3 (OUTPUT_TERMINAL) bTerminalID 8 wTerminalType 0x0301 Speaker bAssocTerminal 0 bSourceID 7 iTerminal 0 Interface Descriptor: bLength 9 bDescriptorType 4 bInterfaceNumber1 bAlternateSetting 0 bNumEndpoints 0 bInterfaceClass 1 Audio bInterfaceSubClass 2 Streaming bInterfaceProtocol 0 iInterface 0 Interface Descriptor: bLength 9 bDescriptorType 4 bInterfaceNumber1 bAlternateSetting 1 bNumEndpoints 2 bInterfaceClass 1 Audio bInterfaceSubClass 2 Streaming bInterfaceProtocol 0 iInterface 0 AudioStreaming Interface Descriptor: bLength 7 bDescriptorType36 bDescriptorSubtype 1 (AS_GENERAL) bTerminalLink 5 bDelay 1 frames wFormatTag 1 PCM AudioStreaming Interface Descriptor: bLength20 bDescriptorType36 bDescriptorSubtype 2 (FORMAT_TYPE) bFormatType 1 (FORMAT_TYPE_I) bNrChannels 2 bSubframeSize 3 bBitResolution
[Touch-packages] [Bug 1811861] Re: incorrect permissions on /var/log after debootstrap
Sorry for the noise, it seems this is not related to rsyslog after all. In our install process we are moving /var/log to another partition (mounted in /data/) and then symlink it to /var/log. Permissions are set up properly and work while the system is running. When the system is rebooted though there is an unknown process changing the permissions of /data/log, my best guess something related to systemd. When we bind mount /data/log in /var/log directory we don't have this issue though. -- 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/1811861 Title: incorrect permissions on /var/log after debootstrap Status in rsyslog package in Ubuntu: New Bug description: we are debootstrapping a full bionic distribution into a directory. After debootstrapping the permissions on /var/log are incorrect, causing rsyslog to fail because it cannot write into the directory to create the various files. Also, in the postinst of the rsyslog package I see that systemd-tmpfiles is attempted to be used to create the files defined in /usr/lib/tmpfiles.d/00rsyslog.conf, but from what I can tell this will never work because of the systemd-tmpfiles manpage: --create If this option is passed, all files and directories marked with f, F, w, d, D, v, p, L, c, b, m in the configuration files are created or written to. Files and directories marked with z, Z, t, T, a, and A have their ownership, access mode and security labels set. Since the files are configured with type "z" only ownership, access mode and security will be updated. # lsb_release -rd Description: Ubuntu 18.04.1 LTS Release: 18.04 # apt-cache policy rsyslog rsyslog: Installed: 8.32.0-1ubuntu4 Candidate: 8.32.0-1ubuntu4 Version table: *** 8.32.0-1ubuntu4 100 100 /var/lib/dpkg/status To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/rsyslog/+bug/1811861/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1811447] Re: update-initramfs generates wrong RESUME if no swap + zram
** Changed in: initramfs-tools (Debian) Status: Unknown => Fix Released -- 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/1811447 Title: update-initramfs generates wrong RESUME if no swap + zram Status in initramfs-tools package in Ubuntu: Confirmed Status in initramfs-tools package in Debian: Fix Released Bug description: On a system with swap disabled (removed from /etc/fstab) and package zram-config installed update-initramfs -u will emit something like following: I: The initramfs will attempt to resume from /dev/zram1 I: (UUID=1d4b8573-7eee-43c9-a02a-10a65fc17b8a) I: Set the RESUME variable to override this. Obviously, resuming from zram device without actual non-volatile storage is not going to work. update-initramfs should be fixed to ignore /dev/zram* because otherwise the user must e.g. create file /etc/initramfs-tools/conf.d/resume-none with case-sensitive contents RESUME=none to workaround the issue, which may be a bit hard to guess from the above notice only. See also, somewhat related bug: 1781746 ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: initramfs-tools 0.130ubuntu3.6 ProcVersionSignature: Ubuntu 4.18.0-13.14~18.04.1-lowlatency 4.18.17 Uname: Linux 4.18.0-13-lowlatency x86_64 ApportVersion: 2.20.9-0ubuntu7.5 Architecture: amd64 Date: Fri Jan 11 19:10:41 2019 EcryptfsInUse: Yes InstallationDate: Installed on 2019-01-05 (6 days ago) InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 (20180725) 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/1811447/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1811580] Re: systemd fails to start sshd at reboot
@ Spas Spasov (spaszspasov) Your kernel is out of date. Please upgrade the kernel, or contact the host administrators to apply at least https://wiki.openvz.org/Download/kernel/rhel6/042stab134.7 ** Changed in: systemd (Ubuntu) Status: Confirmed => Incomplete ** Description changed: + So far reported issues turned out to be: + - obsolete/buggy/vulnerable 3rd party provided kernels + - bad permissions on / + + Please ensure / is owned by root:root. + Please ensure you are running up to date kernels. + + + === + Ubuntu 16.04.5, systemd 229-4ubuntu21.15 The latest systemd update has somehow changed the method it uses to start 'ssh.service' i.e. 'sshd'. systemd fails to start sshd if /etc/ssh/sshd_config contains "UsePrivilegeSeparation yes" and /var/run/sshd/ does not already exist. Being as this is the default, virtually EVERY Ubuntu 16.04 server in the world has UsePrivilegeSeparation set to yes. Furthermore, at the time when the user performs 'apt upgrade' and receives the newest version of systemd, /var/run/sshd/ already exists, so sshd successfully reloads for as long as the server doesn't get rebooted. BUT, as soon as the server is rebooted for any reason, /var/run/sshd/ gets cleaned away, and sshd fails to start, causing the remote user to be completely locked out of his system. This is a MAJOR issue for millions of VPS servers worldwide, as they are all about to get locked out of their servers and potentially lose data. The next reboot is a ticking time bomb waiting to spring. The bomb can be defused by implicitly setting 'UsePrivilegeSeparation no' in /etc/ssh/sshd_config, however unsuspecting administrators are bound to be caught out by the millions. I got caught by it in the middle of setting up a new server yesterday, and it took a whole day to find the source. The appropriate fix would be to ensure that systemd can successfully 'start ssh.service' even when 'UsePrivilegeSeparation yes' is set. systemd needs to test that /var/run/sshd/ exists before starting sshd, just as the init.d script for sshd does. openssl could also be patched so that UsePrivilegeSeparation is no longer enabled by default, however that is not going to solve the problem for millions of pre-existing config files. Only an update to openssl to force-override that flag to 'no' would solve the problem. Thus systemd still needs to be responsible for ensuring that it inits sshd properly by ensuring that /var/run/sshd/ exists before it sends the 'start' command. -- 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/1811580 Title: systemd fails to start sshd at reboot Status in systemd package in Ubuntu: Incomplete Bug description: So far reported issues turned out to be: - obsolete/buggy/vulnerable 3rd party provided kernels - bad permissions on / Please ensure / is owned by root:root. Please ensure you are running up to date kernels. === Ubuntu 16.04.5, systemd 229-4ubuntu21.15 The latest systemd update has somehow changed the method it uses to start 'ssh.service' i.e. 'sshd'. systemd fails to start sshd if /etc/ssh/sshd_config contains "UsePrivilegeSeparation yes" and /var/run/sshd/ does not already exist. Being as this is the default, virtually EVERY Ubuntu 16.04 server in the world has UsePrivilegeSeparation set to yes. Furthermore, at the time when the user performs 'apt upgrade' and receives the newest version of systemd, /var/run/sshd/ already exists, so sshd successfully reloads for as long as the server doesn't get rebooted. BUT, as soon as the server is rebooted for any reason, /var/run/sshd/ gets cleaned away, and sshd fails to start, causing the remote user to be completely locked out of his system. This is a MAJOR issue for millions of VPS servers worldwide, as they are all about to get locked out of their servers and potentially lose data. The next reboot is a ticking time bomb waiting to spring. The bomb can be defused by implicitly setting 'UsePrivilegeSeparation no' in /etc/ssh/sshd_config, however unsuspecting administrators are bound to be caught out by the millions. I got caught by it in the middle of setting up a new server yesterday, and it took a whole day to find the source. The appropriate fix would be to ensure that systemd can successfully 'start ssh.service' even when 'UsePrivilegeSeparation yes' is set. systemd needs to test that /var/run/sshd/ exists before starting sshd, just as the init.d script for sshd does. openssl could also be patched so that UsePrivilegeSeparation is no longer enabled by default, however that is not going to solve the problem for millions of pre- existing config files. Only an update to openssl to force-override that flag to 'no' would solve the problem. Thus systemd still needs to be responsible for
[Touch-packages] [Bug 1811580] Re: systemd fails to start sshd at reboot
@ David (dasoto) Please report bad permissions to whoever is distributing the "NVIDIA Jetson TX2 users" installation you are using. Maybe there are some upgrade hooks that could be shipped by packages install in that installation to fix / mitigate this issue. -- 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/1811580 Title: systemd fails to start sshd at reboot Status in systemd package in Ubuntu: Incomplete Bug description: So far reported issues turned out to be: - obsolete/buggy/vulnerable 3rd party provided kernels - bad permissions on / Please ensure / is owned by root:root. Please ensure you are running up to date kernels. === Ubuntu 16.04.5, systemd 229-4ubuntu21.15 The latest systemd update has somehow changed the method it uses to start 'ssh.service' i.e. 'sshd'. systemd fails to start sshd if /etc/ssh/sshd_config contains "UsePrivilegeSeparation yes" and /var/run/sshd/ does not already exist. Being as this is the default, virtually EVERY Ubuntu 16.04 server in the world has UsePrivilegeSeparation set to yes. Furthermore, at the time when the user performs 'apt upgrade' and receives the newest version of systemd, /var/run/sshd/ already exists, so sshd successfully reloads for as long as the server doesn't get rebooted. BUT, as soon as the server is rebooted for any reason, /var/run/sshd/ gets cleaned away, and sshd fails to start, causing the remote user to be completely locked out of his system. This is a MAJOR issue for millions of VPS servers worldwide, as they are all about to get locked out of their servers and potentially lose data. The next reboot is a ticking time bomb waiting to spring. The bomb can be defused by implicitly setting 'UsePrivilegeSeparation no' in /etc/ssh/sshd_config, however unsuspecting administrators are bound to be caught out by the millions. I got caught by it in the middle of setting up a new server yesterday, and it took a whole day to find the source. The appropriate fix would be to ensure that systemd can successfully 'start ssh.service' even when 'UsePrivilegeSeparation yes' is set. systemd needs to test that /var/run/sshd/ exists before starting sshd, just as the init.d script for sshd does. openssl could also be patched so that UsePrivilegeSeparation is no longer enabled by default, however that is not going to solve the problem for millions of pre- existing config files. Only an update to openssl to force-override that flag to 'no' would solve the problem. Thus systemd still needs to be responsible for ensuring that it inits sshd properly by ensuring that /var/run/sshd/ exists before it sends the 'start' command. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1811580/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1811447] Re: update-initramfs generates wrong RESUME if no swap + zram
This issue is fixed in Debian since July 2018 - initramfs-tools version 0.132, please accept this simple, 3 lines patch from Debian into Ubuntu 18.04 : https://salsa.debian.org/kernel-team/initramfs- tools/commit/312393b0cf1231125eeff3d1a2b6b778a935c21d Look at bug #1781746 for more info. ** Bug watch added: Debian Bug tracker #861228 https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=861228 ** Also affects: initramfs-tools (Debian) via https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=861228 Importance: Unknown Status: Unknown -- 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/1811447 Title: update-initramfs generates wrong RESUME if no swap + zram Status in initramfs-tools package in Ubuntu: Confirmed Status in initramfs-tools package in Debian: Unknown Bug description: On a system with swap disabled (removed from /etc/fstab) and package zram-config installed update-initramfs -u will emit something like following: I: The initramfs will attempt to resume from /dev/zram1 I: (UUID=1d4b8573-7eee-43c9-a02a-10a65fc17b8a) I: Set the RESUME variable to override this. Obviously, resuming from zram device without actual non-volatile storage is not going to work. update-initramfs should be fixed to ignore /dev/zram* because otherwise the user must e.g. create file /etc/initramfs-tools/conf.d/resume-none with case-sensitive contents RESUME=none to workaround the issue, which may be a bit hard to guess from the above notice only. See also, somewhat related bug: 1781746 ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: initramfs-tools 0.130ubuntu3.6 ProcVersionSignature: Ubuntu 4.18.0-13.14~18.04.1-lowlatency 4.18.17 Uname: Linux 4.18.0-13-lowlatency x86_64 ApportVersion: 2.20.9-0ubuntu7.5 Architecture: amd64 Date: Fri Jan 11 19:10:41 2019 EcryptfsInUse: Yes InstallationDate: Installed on 2019-01-05 (6 days ago) InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 (20180725) 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/1811447/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1811447] Re: update-initramfs generates wrong RESUME if no swap + zram
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: initramfs-tools (Ubuntu) Status: New => Confirmed -- 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/1811447 Title: update-initramfs generates wrong RESUME if no swap + zram Status in initramfs-tools package in Ubuntu: Confirmed Status in initramfs-tools package in Debian: Unknown Bug description: On a system with swap disabled (removed from /etc/fstab) and package zram-config installed update-initramfs -u will emit something like following: I: The initramfs will attempt to resume from /dev/zram1 I: (UUID=1d4b8573-7eee-43c9-a02a-10a65fc17b8a) I: Set the RESUME variable to override this. Obviously, resuming from zram device without actual non-volatile storage is not going to work. update-initramfs should be fixed to ignore /dev/zram* because otherwise the user must e.g. create file /etc/initramfs-tools/conf.d/resume-none with case-sensitive contents RESUME=none to workaround the issue, which may be a bit hard to guess from the above notice only. See also, somewhat related bug: 1781746 ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: initramfs-tools 0.130ubuntu3.6 ProcVersionSignature: Ubuntu 4.18.0-13.14~18.04.1-lowlatency 4.18.17 Uname: Linux 4.18.0-13-lowlatency x86_64 ApportVersion: 2.20.9-0ubuntu7.5 Architecture: amd64 Date: Fri Jan 11 19:10:41 2019 EcryptfsInUse: Yes InstallationDate: Installed on 2019-01-05 (6 days ago) InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 (20180725) 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/1811447/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1804280] Re: intermittent periods of packet loss and high latency
Persists on a freshly reinstalled system. Output from ping -i6 [host] follows. Note the spike in ping time and high packet loss. 64 bytes from [host]: icmp_seq=3833 ttl=64 time=0.223 ms 64 bytes from [host]: icmp_seq=3834 ttl=64 time=0.212 ms 64 bytes from [host]: icmp_seq=3835 ttl=64 time=0.156 ms 64 bytes from [host]: icmp_seq=3836 ttl=64 time=0.347 ms 64 bytes from [host]: icmp_seq=3837 ttl=64 time=0.216 ms 64 bytes from [host]: icmp_seq=3838 ttl=64 time=0.316 ms 64 bytes from [host]: icmp_seq=3839 ttl=64 time=0.320 ms 64 bytes from [host]: icmp_seq=3840 ttl=64 time=0.168 ms 64 bytes from [host]: icmp_seq=3841 ttl=64 time=336 ms 64 bytes from [host]: icmp_seq=3843 ttl=64 time=216 ms 64 bytes from [host]: icmp_seq=3845 ttl=64 time=515 ms 64 bytes from [host]: icmp_seq=3846 ttl=64 time=423 ms 64 bytes from [host]: icmp_seq=3847 ttl=64 time=498 ms 64 bytes from [host]: icmp_seq=3849 ttl=64 time=569 ms 64 bytes from [host]: icmp_seq=3851 ttl=64 time=532 ms 64 bytes from [host]: icmp_seq=3853 ttl=64 time=496 ms 64 bytes from [host]: icmp_seq=3855 ttl=64 time=502 ms 64 bytes from [host]: icmp_seq=3857 ttl=64 time=424 ms 64 bytes from [host]: icmp_seq=3859 ttl=64 time=346 ms 64 bytes from [host]: icmp_seq=3861 ttl=64 time=352 ms 64 bytes from [host]: icmp_seq=3863 ttl=64 time=358 ms 64 bytes from [host]: icmp_seq=3865 ttl=64 time=573 ms 64 bytes from [host]: icmp_seq=3867 ttl=64 time=495 ms 64 bytes from [host]: icmp_seq=3869 ttl=64 time=627 ms 64 bytes from [host]: icmp_seq=3871 ttl=64 time=465 ms 64 bytes from [host]: icmp_seq=3873 ttl=64 time=261 ms 64 bytes from [host]: icmp_seq=3875 ttl=64 time=518 ms 64 bytes from [host]: icmp_seq=3877 ttl=64 time=440 ms 64 bytes from [host]: icmp_seq=3879 ttl=64 time=400 ms 64 bytes from [host]: icmp_seq=3881 ttl=64 time=410 ms 64 bytes from [host]: icmp_seq=3883 ttl=64 time=542 ms 64 bytes from [host]: icmp_seq=3885 ttl=64 time=338 ms 64 bytes from [host]: icmp_seq=3887 ttl=64 time=511 ms 64 bytes from [host]: icmp_seq=3889 ttl=64 time=475 ms 64 bytes from [host]: icmp_seq=3891 ttl=64 time=230 ms 64 bytes from [host]: icmp_seq=3893 ttl=64 time=571 ms 64 bytes from [host]: icmp_seq=3894 ttl=64 time=564 ms 64 bytes from [host]: icmp_seq=3896 ttl=64 time=598 ms 64 bytes from [host]: icmp_seq=3898 ttl=64 time=604 ms 64 bytes from [host]: icmp_seq=3900 ttl=64 time=317 ms 64 bytes from [host]: icmp_seq=3902 ttl=64 time=239 ms 64 bytes from [host]: icmp_seq=3904 ttl=64 time=538 ms 64 bytes from [host]: icmp_seq=3906 ttl=64 time=795 ms 64 bytes from [host]: icmp_seq=3907 ttl=64 time=453 ms 64 bytes from [host]: icmp_seq=3909 ttl=64 time=571 ms 64 bytes from [host]: icmp_seq=3911 ttl=64 time=535 ms 64 bytes from [host]: icmp_seq=3913 ttl=64 time=373 ms 64 bytes from [host]: icmp_seq=3915 ttl=64 time=463 ms 64 bytes from [host]: icmp_seq=3917 ttl=64 time=385 ms 64 bytes from [host]: icmp_seq=3919 ttl=64 time=265 ms 64 bytes from [host]: icmp_seq=3921 ttl=64 time=564 ms 64 bytes from [host]: icmp_seq=3923 ttl=64 time=444 ms 64 bytes from [host]: icmp_seq=3925 ttl=64 time=367 ms 64 bytes from [host]: icmp_seq=3927 ttl=64 time=0.123 ms 64 bytes from [host]: icmp_seq=3928 ttl=64 time=0.284 ms 64 bytes from [host]: icmp_seq=3929 ttl=64 time=0.239 ms 64 bytes from [host]: icmp_seq=3930 ttl=64 time=0.214 ms 64 bytes from [host]: icmp_seq=3931 ttl=64 time=0.280 ms 64 bytes from [host]: icmp_seq=3932 ttl=64 time=0.314 ms 64 bytes from [host]: icmp_seq=3933 ttl=64 time=0.318 ms 64 bytes from [host]: icmp_seq=3934 ttl=64 time=0.318 ms 64 bytes from [host]: icmp_seq=3935 ttl=64 time=0.312 ms 64 bytes from [host]: icmp_seq=3936 ttl=64 time=0.218 ms 64 bytes from [host]: icmp_seq=3937 ttl=64 time=0.221 ms 64 bytes from [host]: icmp_seq=3938 ttl=64 time=0.308 ms 64 bytes from [host]: icmp_seq=3939 ttl=64 time=0.329 ms 64 bytes from [host]: icmp_seq=3940 ttl=64 time=0.244 ms 64 bytes from [host]: icmp_seq=3941 ttl=64 time=0.235 ms 64 bytes from [host]: icmp_seq=3942 ttl=64 time=0.250 ms 64 bytes from [host]: icmp_seq=3943 ttl=64 time=0.309 ms 64 bytes from [host]: icmp_seq=3944 ttl=64 time=0.132 ms 64 bytes from [host]: icmp_seq=3945 ttl=64 time=0.228 ms 64 bytes from [host]: icmp_seq=3946 ttl=64 time=0.223 ms 64 bytes from [host]: icmp_seq=3947 ttl=64 time=0.202 ms 64 bytes from [host]: icmp_seq=3948 ttl=64 time=0.211 ms 64 bytes from [host]: icmp_seq=3949 ttl=64 time=0.245 ms 64 bytes from [host]: icmp_seq=3950 ttl=64 time=0.248 ms 64 bytes from [host]: icmp_seq=3951 ttl=64 time=0.186 ms 64 bytes from [host]: icmp_seq=3952 ttl=64 time=0.192 ms 64 bytes from [host]: icmp_seq=3953 ttl=64 time=0.321 ms 64 bytes from [host]: icmp_seq=3954 ttl=64 time=0.231 ms 64 bytes from [host]: icmp_seq=3955 ttl=64 time=0.309 ms 64 bytes from [host]: icmp_seq=3956 ttl=64 time=0.307 ms 64 bytes from [host]: icmp_seq=3957 ttl=64 time=0.154 ms 64 bytes from [host]: icmp_seq=3958 ttl=64 time=0.189 ms 64 bytes from [host]: icmp_seq=3959 ttl=64 time=0.303 ms 64 bytes from [host]: icmp_seq=3960 ttl=64 time=0.197 m
[Touch-packages] [Bug 1666432] Re: Internet drops every few minutes on wired and wireless connection
Persists on a freshly reinstalled system. Output from ping -i6 [host] follows. Note the spike in ping time and high packet loss. 64 bytes from [host]: icmp_seq=3833 ttl=64 time=0.223 ms 64 bytes from [host]: icmp_seq=3834 ttl=64 time=0.212 ms 64 bytes from [host]: icmp_seq=3835 ttl=64 time=0.156 ms 64 bytes from [host]: icmp_seq=3836 ttl=64 time=0.347 ms 64 bytes from [host]: icmp_seq=3837 ttl=64 time=0.216 ms 64 bytes from [host]: icmp_seq=3838 ttl=64 time=0.316 ms 64 bytes from [host]: icmp_seq=3839 ttl=64 time=0.320 ms 64 bytes from [host]: icmp_seq=3840 ttl=64 time=0.168 ms 64 bytes from [host]: icmp_seq=3841 ttl=64 time=336 ms 64 bytes from [host]: icmp_seq=3843 ttl=64 time=216 ms 64 bytes from [host]: icmp_seq=3845 ttl=64 time=515 ms 64 bytes from [host]: icmp_seq=3846 ttl=64 time=423 ms 64 bytes from [host]: icmp_seq=3847 ttl=64 time=498 ms 64 bytes from [host]: icmp_seq=3849 ttl=64 time=569 ms 64 bytes from [host]: icmp_seq=3851 ttl=64 time=532 ms 64 bytes from [host]: icmp_seq=3853 ttl=64 time=496 ms 64 bytes from [host]: icmp_seq=3855 ttl=64 time=502 ms 64 bytes from [host]: icmp_seq=3857 ttl=64 time=424 ms 64 bytes from [host]: icmp_seq=3859 ttl=64 time=346 ms 64 bytes from [host]: icmp_seq=3861 ttl=64 time=352 ms 64 bytes from [host]: icmp_seq=3863 ttl=64 time=358 ms 64 bytes from [host]: icmp_seq=3865 ttl=64 time=573 ms 64 bytes from [host]: icmp_seq=3867 ttl=64 time=495 ms 64 bytes from [host]: icmp_seq=3869 ttl=64 time=627 ms 64 bytes from [host]: icmp_seq=3871 ttl=64 time=465 ms 64 bytes from [host]: icmp_seq=3873 ttl=64 time=261 ms 64 bytes from [host]: icmp_seq=3875 ttl=64 time=518 ms 64 bytes from [host]: icmp_seq=3877 ttl=64 time=440 ms 64 bytes from [host]: icmp_seq=3879 ttl=64 time=400 ms 64 bytes from [host]: icmp_seq=3881 ttl=64 time=410 ms 64 bytes from [host]: icmp_seq=3883 ttl=64 time=542 ms 64 bytes from [host]: icmp_seq=3885 ttl=64 time=338 ms 64 bytes from [host]: icmp_seq=3887 ttl=64 time=511 ms 64 bytes from [host]: icmp_seq=3889 ttl=64 time=475 ms 64 bytes from [host]: icmp_seq=3891 ttl=64 time=230 ms 64 bytes from [host]: icmp_seq=3893 ttl=64 time=571 ms 64 bytes from [host]: icmp_seq=3894 ttl=64 time=564 ms 64 bytes from [host]: icmp_seq=3896 ttl=64 time=598 ms 64 bytes from [host]: icmp_seq=3898 ttl=64 time=604 ms 64 bytes from [host]: icmp_seq=3900 ttl=64 time=317 ms 64 bytes from [host]: icmp_seq=3902 ttl=64 time=239 ms 64 bytes from [host]: icmp_seq=3904 ttl=64 time=538 ms 64 bytes from [host]: icmp_seq=3906 ttl=64 time=795 ms 64 bytes from [host]: icmp_seq=3907 ttl=64 time=453 ms 64 bytes from [host]: icmp_seq=3909 ttl=64 time=571 ms 64 bytes from [host]: icmp_seq=3911 ttl=64 time=535 ms 64 bytes from [host]: icmp_seq=3913 ttl=64 time=373 ms 64 bytes from [host]: icmp_seq=3915 ttl=64 time=463 ms 64 bytes from [host]: icmp_seq=3917 ttl=64 time=385 ms 64 bytes from [host]: icmp_seq=3919 ttl=64 time=265 ms 64 bytes from [host]: icmp_seq=3921 ttl=64 time=564 ms 64 bytes from [host]: icmp_seq=3923 ttl=64 time=444 ms 64 bytes from [host]: icmp_seq=3925 ttl=64 time=367 ms 64 bytes from [host]: icmp_seq=3927 ttl=64 time=0.123 ms 64 bytes from [host]: icmp_seq=3928 ttl=64 time=0.284 ms 64 bytes from [host]: icmp_seq=3929 ttl=64 time=0.239 ms 64 bytes from [host]: icmp_seq=3930 ttl=64 time=0.214 ms 64 bytes from [host]: icmp_seq=3931 ttl=64 time=0.280 ms 64 bytes from [host]: icmp_seq=3932 ttl=64 time=0.314 ms 64 bytes from [host]: icmp_seq=3933 ttl=64 time=0.318 ms 64 bytes from [host]: icmp_seq=3934 ttl=64 time=0.318 ms 64 bytes from [host]: icmp_seq=3935 ttl=64 time=0.312 ms 64 bytes from [host]: icmp_seq=3936 ttl=64 time=0.218 ms 64 bytes from [host]: icmp_seq=3937 ttl=64 time=0.221 ms 64 bytes from [host]: icmp_seq=3938 ttl=64 time=0.308 ms 64 bytes from [host]: icmp_seq=3939 ttl=64 time=0.329 ms 64 bytes from [host]: icmp_seq=3940 ttl=64 time=0.244 ms 64 bytes from [host]: icmp_seq=3941 ttl=64 time=0.235 ms 64 bytes from [host]: icmp_seq=3942 ttl=64 time=0.250 ms 64 bytes from [host]: icmp_seq=3943 ttl=64 time=0.309 ms 64 bytes from [host]: icmp_seq=3944 ttl=64 time=0.132 ms 64 bytes from [host]: icmp_seq=3945 ttl=64 time=0.228 ms 64 bytes from [host]: icmp_seq=3946 ttl=64 time=0.223 ms 64 bytes from [host]: icmp_seq=3947 ttl=64 time=0.202 ms 64 bytes from [host]: icmp_seq=3948 ttl=64 time=0.211 ms 64 bytes from [host]: icmp_seq=3949 ttl=64 time=0.245 ms 64 bytes from [host]: icmp_seq=3950 ttl=64 time=0.248 ms 64 bytes from [host]: icmp_seq=3951 ttl=64 time=0.186 ms 64 bytes from [host]: icmp_seq=3952 ttl=64 time=0.192 ms 64 bytes from [host]: icmp_seq=3953 ttl=64 time=0.321 ms 64 bytes from [host]: icmp_seq=3954 ttl=64 time=0.231 ms 64 bytes from [host]: icmp_seq=3955 ttl=64 time=0.309 ms 64 bytes from [host]: icmp_seq=3956 ttl=64 time=0.307 ms 64 bytes from [host]: icmp_seq=3957 ttl=64 time=0.154 ms 64 bytes from [host]: icmp_seq=3958 ttl=64 time=0.189 ms 64 bytes from [host]: icmp_seq=3959 ttl=64 time=0.303 ms 64 bytes from [host]: icmp_seq=3960 ttl=64 time=0.197 m
[Touch-packages] [Bug 1811979] [NEW] My bluetooth is not working since i am using ubuntu 14.04, it works fine in windows 7
Public bug reported: bluetooth network in my ubuntu is not working.actually the on button in the setting does not turn bluetooth button in to ON, it remains OFF even if i click on it.i already installed bluez and blueman . i am using this version of ubuntu Description:Ubuntu 18.04.1 LTS Release:18.04 ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: bluetooth (not installed) ProcVersionSignature: Ubuntu 4.15.0-43.46-generic 4.15.18 Uname: Linux 4.15.0-43-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.5 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Wed Jan 16 15:10:56 2019 InterestingModules: bluetooth MachineType: Hewlett-Packard HP 15 Notebook PC ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-43-generic root=UUID=1a5a1726-0948-424a-a01e-de88efc704ca ro quiet splash vt.handoff=1 SourcePackage: bluez UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 05/21/2014 dmi.bios.vendor: Insyde dmi.bios.version: F.18 dmi.board.asset.tag: Type2 - Board Asset Tag dmi.board.name: 226E dmi.board.vendor: Hewlett-Packard dmi.board.version: 74.19 dmi.chassis.asset.tag: Chassis Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: Hewlett-Packard dmi.chassis.version: Chassis Version dmi.modalias: dmi:bvnInsyde:bvrF.18:bd05/21/2014:svnHewlett-Packard:pnHP15NotebookPC:pvr0991100600087:rvnHewlett-Packard:rn226E:rvr74.19:cvnHewlett-Packard:ct10:cvrChassisVersion: dmi.product.family: 103C_5335KV G=N L=CON B=HP S=PAV dmi.product.name: HP 15 Notebook PC dmi.product.version: 0991100600087 dmi.sys.vendor: Hewlett-Packard hciconfig: ** Affects: bluez (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug bionic -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to bluez in Ubuntu. https://bugs.launchpad.net/bugs/1811979 Title: My bluetooth is not working since i am using ubuntu 14.04,it works fine in windows 7 Status in bluez package in Ubuntu: New Bug description: bluetooth network in my ubuntu is not working.actually the on button in the setting does not turn bluetooth button in to ON, it remains OFF even if i click on it.i already installed bluez and blueman . i am using this version of ubuntu Description:Ubuntu 18.04.1 LTS Release:18.04 ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: bluetooth (not installed) ProcVersionSignature: Ubuntu 4.15.0-43.46-generic 4.15.18 Uname: Linux 4.15.0-43-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.5 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Wed Jan 16 15:10:56 2019 InterestingModules: bluetooth MachineType: Hewlett-Packard HP 15 Notebook PC ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-43-generic root=UUID=1a5a1726-0948-424a-a01e-de88efc704ca ro quiet splash vt.handoff=1 SourcePackage: bluez UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 05/21/2014 dmi.bios.vendor: Insyde dmi.bios.version: F.18 dmi.board.asset.tag: Type2 - Board Asset Tag dmi.board.name: 226E dmi.board.vendor: Hewlett-Packard dmi.board.version: 74.19 dmi.chassis.asset.tag: Chassis Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: Hewlett-Packard dmi.chassis.version: Chassis Version dmi.modalias: dmi:bvnInsyde:bvrF.18:bd05/21/2014:svnHewlett-Packard:pnHP15NotebookPC:pvr0991100600087:rvnHewlett-Packard:rn226E:rvr74.19:cvnHewlett-Packard:ct10:cvrChassisVersion: dmi.product.family: 103C_5335KV G=N L=CON B=HP S=PAV dmi.product.name: HP 15 Notebook PC dmi.product.version: 0991100600087 dmi.sys.vendor: Hewlett-Packard hciconfig: To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/1811979/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1811966] Re: ibus-daemon crashed with SIGABRT
*** This bug is a duplicate of bug 1545811 *** https://bugs.launchpad.net/bugs/1545811 Thank you for taking the time to report this crash and helping to make this software better. This particular crash has already been reported and is a duplicate of bug #1545811, so is being marked as such. Please look at the other bug report to see if there is any missing information that you can provide, or to see if there is a workaround for the bug. Additionally, any further discussion regarding the bug should occur in the other report. Please continue to report any other bugs you may find. ** Attachment removed: "CoreDump.gz" https://bugs.launchpad.net/bugs/1811966/+attachment/5229571/+files/CoreDump.gz ** Attachment removed: "Disassembly.txt" https://bugs.launchpad.net/bugs/1811966/+attachment/5229573/+files/Disassembly.txt ** Attachment removed: "ProcMaps.txt" https://bugs.launchpad.net/bugs/1811966/+attachment/5229576/+files/ProcMaps.txt ** Attachment removed: "ProcStatus.txt" https://bugs.launchpad.net/bugs/1811966/+attachment/5229577/+files/ProcStatus.txt ** Attachment removed: "Registers.txt" https://bugs.launchpad.net/bugs/1811966/+attachment/5229578/+files/Registers.txt ** Attachment removed: "Stacktrace.txt" https://bugs.launchpad.net/bugs/1811966/+attachment/5229579/+files/Stacktrace.txt ** Attachment removed: "ThreadStacktrace.txt" https://bugs.launchpad.net/bugs/1811966/+attachment/5229580/+files/ThreadStacktrace.txt ** This bug has been marked a duplicate of private bug 1545811 ** Information type changed from Private to Public ** Tags removed: need-amd64-retrace -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to ibus in Ubuntu. https://bugs.launchpad.net/bugs/1811966 Title: ibus-daemon crashed with SIGABRT Status in ibus package in Ubuntu: New Bug description: I have this error message via making each boot of Ubuntu. ProblemType: Crash DistroRelease: Ubuntu 19.04 Package: ibus 1.5.19-1ubuntu1 ProcVersionSignature: Ubuntu 4.18.0-11.12-generic 4.18.12 Uname: Linux 4.18.0-11-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.10-0ubuntu18 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Thu Jan 10 23:11:06 2019 ExecutablePath: /usr/bin/ibus-daemon InstallationDate: Installed on 2018-04-29 (261 days ago) InstallationMedia: Kubuntu 18.04 LTS "Bionic Beaver" - Alpha amd64 (20180421.1) ProcCmdline: ibus-daemon --xim --panel disable ProcEnviron: PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=it_IT.UTF-8 SHELL=/bin/bash Signal: 6 SourcePackage: ibus StacktraceTop: () at /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0 g_assertion_message_expr () at /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0 () () () at /usr/lib/x86_64-linux-gnu/libgio-2.0.so.0 Title: ibus-daemon crashed with SIGABRT UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ibus/+bug/1811966/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1811580] Re: systemd fails to start sshd at reboot
I'm experiencing the same problem with Ubuntu 16.04.5 on OpenVZ (with kernel: 2.6.32-042stab127.2). The workaround that I found is to edit `/usr/lib/tmpfiles.d/sshd.conf` in the following way: d /run/sshd 0755 root root Here is the question on askubuntu.com, where my case decribed in more details: https://askubuntu.com/q/1109934/566421 -- 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/1811580 Title: systemd fails to start sshd at reboot Status in systemd package in Ubuntu: Confirmed Bug description: Ubuntu 16.04.5, systemd 229-4ubuntu21.15 The latest systemd update has somehow changed the method it uses to start 'ssh.service' i.e. 'sshd'. systemd fails to start sshd if /etc/ssh/sshd_config contains "UsePrivilegeSeparation yes" and /var/run/sshd/ does not already exist. Being as this is the default, virtually EVERY Ubuntu 16.04 server in the world has UsePrivilegeSeparation set to yes. Furthermore, at the time when the user performs 'apt upgrade' and receives the newest version of systemd, /var/run/sshd/ already exists, so sshd successfully reloads for as long as the server doesn't get rebooted. BUT, as soon as the server is rebooted for any reason, /var/run/sshd/ gets cleaned away, and sshd fails to start, causing the remote user to be completely locked out of his system. This is a MAJOR issue for millions of VPS servers worldwide, as they are all about to get locked out of their servers and potentially lose data. The next reboot is a ticking time bomb waiting to spring. The bomb can be defused by implicitly setting 'UsePrivilegeSeparation no' in /etc/ssh/sshd_config, however unsuspecting administrators are bound to be caught out by the millions. I got caught by it in the middle of setting up a new server yesterday, and it took a whole day to find the source. The appropriate fix would be to ensure that systemd can successfully 'start ssh.service' even when 'UsePrivilegeSeparation yes' is set. systemd needs to test that /var/run/sshd/ exists before starting sshd, just as the init.d script for sshd does. openssl could also be patched so that UsePrivilegeSeparation is no longer enabled by default, however that is not going to solve the problem for millions of pre- existing config files. Only an update to openssl to force-override that flag to 'no' would solve the problem. Thus systemd still needs to be responsible for ensuring that it inits sshd properly by ensuring that /var/run/sshd/ exists before it sends the 'start' command. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1811580/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1776173] Re: qt print dialog shipped with bionic ignores printer defaults
1) I confirm that the gray-scale printing option is completely ignored and that the printer prints always in color (this is definitively a bug). 2) I confirm that an option to select the printer tray is missing (though I think this may be a limitation in the qt version shipped with bionic). 3) I would like to add that okular "scales down" when printing A4 pdf documents, which badly breaks some flows. For instance, pages of the same document printed on the same printer with okular and any other linux PDF viewer do not align and cannot be mixed; flows needing accurate placement of cropmarks are broken (this is also a bug). Probably these should be new bugs, though. Still I wonder if moving to the current qt 5.9.7 from the bionic 5.9.5 could improve the situation. In the end qt 5.9 is a long term release with only bugfixes applied and it should be relatively safe to track it rather than introducing downstream patches. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to qtbase-opensource-src in Ubuntu. https://bugs.launchpad.net/bugs/1776173 Title: qt print dialog shipped with bionic ignores printer defaults Status in qtbase-opensource-src package in Ubuntu: Confirmed Bug description: All kde applications shipped with ubuntu and particularly kubuntu bionic print via the qt print dialog, that, unfortunately, does not seem to respect the defaults set for the printer. Specifically, every time one starts to print the "duplex" option gets reset to "none" even for those printers that were configured for "long edge" duplex by default. This may lead to a huge *waste of paper*: people print, expecting the duplex, do not get it, throw away the printout and reprint, for a total of 3 times the paper usage if the print dialog respected the default. See also https://bugs.kde.org/show_bug.cgi?id=395150 As a final comment and in general, I think that Bionic should be updated to use the QT 5.11 print subsystem (from 5.9.5) as soon as possible (at least via a kubuntu ppa). The QT 5 print dialog has always been extremely poor, with no possibility to provide information about things like print quality and resolution, paper type, stapling (for printers supporting it), etc. Now, QT 5.11 has finally a better print dialog and it would be great if the bionic users could use it. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: libqt5widgets5 5.9.5+dfsg-0ubuntu1 ProcVersionSignature: Ubuntu 4.15.0-22.24-generic 4.15.17 Uname: Linux 4.15.0-22-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.2 Architecture: amd64 CurrentDesktop: KDE Date: Mon Jun 11 10:23:53 2018 EcryptfsInUse: Yes InstallationDate: Installed on 2013-12-12 (1641 days ago) InstallationMedia: Kubuntu 13.10 "Saucy Salamander" - Release amd64 (20131016.1) SourcePackage: qtbase-opensource-src UpgradeStatus: Upgraded to bionic on 2018-06-08 (2 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/qtbase-opensource-src/+bug/1776173/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1776173] Re: qt print dialog shipped with bionic ignores printer defaults
On my system there are more missing or broken options (not only the duplex problem) in the qt print dialog. On my bionic system i found the following other problems: - the printers are always on color mode, instead of gray-scale. - the option to select the input tray is missing. - the borders can't set smaller then the default. it would be good if not only the duplex option would be fixed. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to qtbase-opensource-src in Ubuntu. https://bugs.launchpad.net/bugs/1776173 Title: qt print dialog shipped with bionic ignores printer defaults Status in qtbase-opensource-src package in Ubuntu: Confirmed Bug description: All kde applications shipped with ubuntu and particularly kubuntu bionic print via the qt print dialog, that, unfortunately, does not seem to respect the defaults set for the printer. Specifically, every time one starts to print the "duplex" option gets reset to "none" even for those printers that were configured for "long edge" duplex by default. This may lead to a huge *waste of paper*: people print, expecting the duplex, do not get it, throw away the printout and reprint, for a total of 3 times the paper usage if the print dialog respected the default. See also https://bugs.kde.org/show_bug.cgi?id=395150 As a final comment and in general, I think that Bionic should be updated to use the QT 5.11 print subsystem (from 5.9.5) as soon as possible (at least via a kubuntu ppa). The QT 5 print dialog has always been extremely poor, with no possibility to provide information about things like print quality and resolution, paper type, stapling (for printers supporting it), etc. Now, QT 5.11 has finally a better print dialog and it would be great if the bionic users could use it. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: libqt5widgets5 5.9.5+dfsg-0ubuntu1 ProcVersionSignature: Ubuntu 4.15.0-22.24-generic 4.15.17 Uname: Linux 4.15.0-22-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.2 Architecture: amd64 CurrentDesktop: KDE Date: Mon Jun 11 10:23:53 2018 EcryptfsInUse: Yes InstallationDate: Installed on 2013-12-12 (1641 days ago) InstallationMedia: Kubuntu 13.10 "Saucy Salamander" - Release amd64 (20131016.1) SourcePackage: qtbase-opensource-src UpgradeStatus: Upgraded to bionic on 2018-06-08 (2 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/qtbase-opensource-src/+bug/1776173/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1811812] Re: Util-linux will not install - unmet dependendies
This is definitely not an invalid bug report. It is not a support request nor spam. Steve wrote: "util-linux will be migratable to the disco release pocket". This simply is not true. This bug is for util-linux_2.33.1-0.1ubuntu1 and this package cannot be installed (not migratable to release pocket) due to the unmet dependencies. I know very well the recommendations for proposed repos. However, it surely is better that the bug is fixed before the package enters into release repos. If you do not want bug reports to be written, then what is this forum or page there for? ** Summary changed: - Util-linux will not install - unmet dependendies + Util-linux_2.33.1-0.1ubuntu1 will not install - unmet dependendies -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to util-linux in Ubuntu. https://bugs.launchpad.net/bugs/1811812 Title: Util-linux_2.33.1-0.1ubuntu1 will not install - unmet dependendies Status in util-linux package in Ubuntu: New Bug description: Package util-linux (2.33.1-0.1ubuntu1) cannot be installed due to unmet dependencies. Util-linux depends on login (>=1:4.5-1.1~) but the latest installable version is login (1:4.5-1ubuntu1). To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/util-linux/+bug/1811812/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1811812] Re: Util-linux will not install - unmet dependendies
** Changed in: util-linux (Ubuntu) Status: Invalid => New -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to util-linux in Ubuntu. https://bugs.launchpad.net/bugs/1811812 Title: Util-linux_2.33.1-0.1ubuntu1 will not install - unmet dependendies Status in util-linux package in Ubuntu: New Bug description: Package util-linux (2.33.1-0.1ubuntu1) cannot be installed due to unmet dependencies. Util-linux depends on login (>=1:4.5-1.1~) but the latest installable version is login (1:4.5-1ubuntu1). To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/util-linux/+bug/1811812/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp