[Touch-packages] [Bug 1849055] Re: gnome-extensions fails to load after boot
Can you please run: apport-collect 1849055 to send us more information about your gnome-shell? ** Package changed: xorg (Ubuntu) => gnome-shell (Ubuntu) ** Changed in: gnome-shell (Ubuntu) Status: New => Incomplete -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to xorg in Ubuntu. https://bugs.launchpad.net/bugs/1849055 Title: gnome-extensions fails to load after boot Status in gnome-shell package in Ubuntu: Incomplete Bug description: Most of the time when I start or restart Ubuntu-19.10 the gnome-extensions that I have enabled fail to load. I am forced to go each time to gnome-tweaks to re-enable these extensions which is very frustrating. This worked fine in Ubuntu 19.04. I am using a Dell Inspiron 1420 laptop. Thank you for any help with this. ProblemType: Bug DistroRelease: Ubuntu 19.10 Package: xorg 1:7.7+19ubuntu12 ProcVersionSignature: Ubuntu 5.3.0-18.19-generic 5.3.1 Uname: Linux 5.3.0-18-generic x86_64 NonfreeKernelModules: 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 340.107 Thu May 24 21:54:01 PDT 2018 GCC version: gcc version 9.2.1 20191008 (Ubuntu 9.2.1-9ubuntu2) .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.11-0ubuntu8 Architecture: amd64 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Sun Oct 20 22:14:29 2019 DistUpgraded: Fresh install DistroCodename: eoan DistroVariant: ubuntu DkmsStatus: nvidia-340, 340.107, 5.3.0-18-generic, x86_64: installed GraphicsCard: NVIDIA Corporation G86M [GeForce 8400M GS] [10de:0427] (rev a1) (prog-if 00 [VGA controller]) Subsystem: Dell G86M [GeForce 8400M GS] [1028:01f3] InstallationDate: Installed on 2016-01-26 (1363 days ago) InstallationMedia: Ubuntu 15.10 "Wily Werewolf" - Release amd64 (20151021) MachineType: Dell Inc. Inspiron 1420 ProcEnviron: LANGUAGE=en_US PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.3.0-18-generic root=/dev/mapper/ubuntu--vg-root ro quiet splash noresume vt.handoff=7 SourcePackage: xorg Symptom: display UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 12/19/2008 dmi.bios.vendor: Dell Inc. dmi.bios.version: A10 dmi.board.name: 0Y918J dmi.board.vendor: Dell Inc. dmi.chassis.type: 8 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvrA10:bd12/19/2008:svnDellInc.:pnInspiron1420:pvr:rvnDellInc.:rn0Y918J:rvr:cvnDellInc.:ct8:cvr: dmi.product.name: Inspiron 1420 dmi.sys.vendor: Dell Inc. version.compiz: compiz 1:0.9.14.0+19.10.20190918-0ubuntu1 version.libdrm2: libdrm2 2.4.99-1ubuntu1 version.libgl1-mesa-dri: libgl1-mesa-dri 19.2.1-1ubuntu1 version.libgl1-mesa-glx: libgl1-mesa-glx 19.2.1-1ubuntu1 version.nvidia-graphics-drivers: nvidia-graphics-drivers-* N/A version.xserver-xorg-core: xserver-xorg-core 2:1.20.5+git20191008-0ubuntu1 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.10.6-1 version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.0.1-1ubuntu1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20190815-1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1 xserver.bootTime: Sun Oct 20 21:04:57 2019 xserver.configfile: default xserver.errors: xserver.logfile: /var/log/Xorg.0.log xserver.outputs: xserver.version: 2:1.20.5+git20191008-0ubuntu1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1849055/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1714178] Re: Triple 4K monitor display failed (modesetting driver limited to 8192x8192)
** Changed in: hwe-next Status: New => Fix Released -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to mesa in Ubuntu. https://bugs.launchpad.net/bugs/1714178 Title: Triple 4K monitor display failed (modesetting driver limited to 8192x8192) Status in DRI: Fix Released Status in HWE Next: Fix Released Status in X.Org X server: Unknown Status in linux package in Ubuntu: Triaged Status in linux-oem-osp1 package in Ubuntu: Fix Released Status in mesa package in Ubuntu: Fix Released Status in xorg-server package in Ubuntu: Invalid Status in linux source package in Bionic: Confirmed Status in linux-oem-osp1 source package in Bionic: Fix Released Status in mesa source package in Bionic: Fix Released Status in xorg-server source package in Bionic: Invalid Bug description: Title: Triple monitor display failed with Dell Dock (HiDPI) (modesetting) Summary: Triple monitor display failed with Dell Dock (HiDPI) (modesetting) Steps: 1. a laptop with Built-in 4K LCD 2. Cold boot system with Dell Dock connected 3. Connect a 4K monitor to Dock 4. Connect 2nd 4K monitor to Dock 5. Go to [All Settings]=>[Displays] to have the following configuration. Resolution: 4kx2k@60Hz (one Built-in LCD + two external monitors) Mirror displays: disable Expected results: Triple monitor display should works without issues Actual results: Triple monitor display failed with Dell Dock Additional information: 1. Linux distribution: Ubuntu 16.04+modesetting, 16.04.3, and 17.04 2. Laptop: Dell Precision 5520 3. Dell Business Thunderbolt Dock - TB16 https://goo.gl/vFDjpi WORKAROUND (UBUNTU 18.04+): Log in to "Ubuntu on Wayland" instead of "Ubuntu". --- .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 DistUpgraded: Fresh install DistributionChannelDescriptor: # This is a distribution channel descriptor # For more information see http://wiki.ubuntu.com/DistributionChannelDescriptor canonical-oem-somerville-xenial-amd64-20160624-2 DistroCodename: xenial DistroRelease: Ubuntu 16.04 DistroVariant: ubuntu ExtraDebuggingInterest: Yes GraphicsCard: Intel Corporation Device [8086:591d] (rev 04) (prog-if 00 [VGA controller]) Subsystem: Dell Device [1028:07bf] Subsystem: Dell Device [1028:07bf] InstallationDate: Installed on 2017-08-29 (2 days ago) InstallationMedia: Ubuntu 16.04 "Xenial" - Build amd64 LIVE Binary 20160624-10:47 MachineType: Dell Inc. Precision 5520 Package: xorg-server (not installed) ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.11.0-14-generic.efi.signed root=UUID=b79ae801-0652-4785-beaf-e8387d798948 ro acpi_rev_override quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 4.11.0-14.20~16.04.1-generic 4.11.12 Tags: xenial ubuntu compiz-0.9 Uname: Linux 4.11.0-14-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 05/08/2017 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.3.3 dmi.board.vendor: Dell Inc. dmi.chassis.type: 10 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr1.3.3:bd05/08/2017:svnDellInc.:pnPrecision5520:pvr:rvnDellInc.:rn:rvr:cvnDellInc.:ct10:cvr: dmi.product.name: Precision 5520 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.1 version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A version.libgl1-mesa-glx: libgl1-mesa-glx 17.0.7-0ubuntu0.16.04.1 version.xserver-xorg-core: xserver-xorg-core 2:1.18.4-0ubuntu0.3 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.10.1-1ubuntu2 version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.7.0-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20160325-1ubuntu1.2 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.12-1build2 To manage notifications about this bug go to: https://bugs.launchpad.net/dri/+bug/1714178/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1849055] [NEW] gnome-extensions fails to load after boot
Public bug reported: Most of the time when I start or restart Ubuntu-19.10 the gnome-extensions that I have enabled fail to load. I am forced to go each time to gnome-tweaks to re-enable these extensions which is very frustrating. This worked fine in Ubuntu 19.04. I am using a Dell Inspiron 1420 laptop. Thank you for any help with this. ProblemType: Bug DistroRelease: Ubuntu 19.10 Package: xorg 1:7.7+19ubuntu12 ProcVersionSignature: Ubuntu 5.3.0-18.19-generic 5.3.1 Uname: Linux 5.3.0-18-generic x86_64 NonfreeKernelModules: 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 340.107 Thu May 24 21:54:01 PDT 2018 GCC version: gcc version 9.2.1 20191008 (Ubuntu 9.2.1-9ubuntu2) .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.11-0ubuntu8 Architecture: amd64 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Sun Oct 20 22:14:29 2019 DistUpgraded: Fresh install DistroCodename: eoan DistroVariant: ubuntu DkmsStatus: nvidia-340, 340.107, 5.3.0-18-generic, x86_64: installed GraphicsCard: NVIDIA Corporation G86M [GeForce 8400M GS] [10de:0427] (rev a1) (prog-if 00 [VGA controller]) Subsystem: Dell G86M [GeForce 8400M GS] [1028:01f3] InstallationDate: Installed on 2016-01-26 (1363 days ago) InstallationMedia: Ubuntu 15.10 "Wily Werewolf" - Release amd64 (20151021) MachineType: Dell Inc. Inspiron 1420 ProcEnviron: LANGUAGE=en_US PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.3.0-18-generic root=/dev/mapper/ubuntu--vg-root ro quiet splash noresume vt.handoff=7 SourcePackage: xorg Symptom: display UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 12/19/2008 dmi.bios.vendor: Dell Inc. dmi.bios.version: A10 dmi.board.name: 0Y918J dmi.board.vendor: Dell Inc. dmi.chassis.type: 8 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvrA10:bd12/19/2008:svnDellInc.:pnInspiron1420:pvr:rvnDellInc.:rn0Y918J:rvr:cvnDellInc.:ct8:cvr: dmi.product.name: Inspiron 1420 dmi.sys.vendor: Dell Inc. version.compiz: compiz 1:0.9.14.0+19.10.20190918-0ubuntu1 version.libdrm2: libdrm2 2.4.99-1ubuntu1 version.libgl1-mesa-dri: libgl1-mesa-dri 19.2.1-1ubuntu1 version.libgl1-mesa-glx: libgl1-mesa-glx 19.2.1-1ubuntu1 version.nvidia-graphics-drivers: nvidia-graphics-drivers-* N/A version.xserver-xorg-core: xserver-xorg-core 2:1.20.5+git20191008-0ubuntu1 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.10.6-1 version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.0.1-1ubuntu1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20190815-1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1 xserver.bootTime: Sun Oct 20 21:04:57 2019 xserver.configfile: default xserver.errors: xserver.logfile: /var/log/Xorg.0.log xserver.outputs: xserver.version: 2:1.20.5+git20191008-0ubuntu1 ** Affects: xorg (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug eoan possible-manual-nvidia-install ubuntu -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to xorg in Ubuntu. https://bugs.launchpad.net/bugs/1849055 Title: gnome-extensions fails to load after boot Status in xorg package in Ubuntu: New Bug description: Most of the time when I start or restart Ubuntu-19.10 the gnome-extensions that I have enabled fail to load. I am forced to go each time to gnome-tweaks to re-enable these extensions which is very frustrating. This worked fine in Ubuntu 19.04. I am using a Dell Inspiron 1420 laptop. Thank you for any help with this. ProblemType: Bug DistroRelease: Ubuntu 19.10 Package: xorg 1:7.7+19ubuntu12 ProcVersionSignature: Ubuntu 5.3.0-18.19-generic 5.3.1 Uname: Linux 5.3.0-18-generic x86_64 NonfreeKernelModules: 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 340.107 Thu May 24 21:54:01 PDT 2018 GCC version: gcc version 9.2.1 20191008 (Ubuntu 9.2.1-9ubuntu2) .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
[Touch-packages] [Bug 1848587] Re: lxc 3.0.4-0ubuntu1 ADT test failure with linux 5.4.0-1.2
Looking at the linked reports, it sounds like either /dev/network_latency doesn't exist in those systems (which would differ from standard kernel behavior on Ubuntu), or there is a legitimate issue with injecting that device afterwards. In either case, likely to be a kernel config change or a kernel regression. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to lxc in Ubuntu. https://bugs.launchpad.net/bugs/1848587 Title: lxc 3.0.4-0ubuntu1 ADT test failure with linux 5.4.0-1.2 Status in lxc package in Ubuntu: New Bug description: Testing failed on: amd64: https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac/autopkgtest-eoan-canonical-kernel-team-unstable/eoan/amd64/l/lxc/20191016_150939_0f81d@/log.gz arm64: https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac/autopkgtest-eoan-canonical-kernel-team-unstable/eoan/arm64/l/lxc/20191016_152027_0f81d@/log.gz ppc64el: https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac/autopkgtest-eoan-canonical-kernel-team-unstable/eoan/ppc64el/l/lxc/20191016_150251_0f81d@/log.gz s390x: https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac/autopkgtest-eoan-canonical-kernel-team-unstable/eoan/s390x/l/lxc/20191016_150201_0f81d@/log.gz To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/lxc/+bug/1848587/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1848965] Re: Video Playback very choppy
Thank you for taking the time to report this bug and helping to make Ubuntu better. Please execute the following command only once, as it will automatically gather debugging information, in a terminal: apport-collect 1848965 When reporting bugs in the future please use apport by using 'ubuntu- bug' and the name of the package affected. You can learn more about this functionality at https://wiki.ubuntu.com/ReportingBugs. ** Tags added: bionic ** Package changed: xorg (Ubuntu) => xorg-server (Ubuntu) ** Changed in: xorg-server (Ubuntu) Status: New => Incomplete -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to xorg in Ubuntu. https://bugs.launchpad.net/bugs/1848965 Title: Video Playback very choppy Status in xorg-server package in Ubuntu: Incomplete Bug description: My laptop is HP Pavilion g7 (Intel® Core™ i5-2430M CPU with Radeon HD 6470M and Intel HD 3000 GPUs Already have played with Ubuntu on older spec desktops with no issues at all, however when when installing Ubuntu 18.04 from installation USB, had to boot with nomodeset to overcome freezing as a result of Ubuntu 18.04 not recognising/supporting these drivers Tried to search for additional drivers but none found Video handling resorts to llvmpipe (LLVM 9.0.0, 256 bits) My problem is that Video Playback is VLC very choppy in full screen mode - seems to get a little better when minimised, but effectively not usable. Have tried many threads posted regarding this problem, but nothing seems to work. Would really like to migrate my workload onto Ubuntu 18.04 operating system, but this seems to be a real non starter where i can't play video content, as video editing is a core function in my workload. Not sure if there is a solution for this, however after researching many similar threads, coupled with your in depth response to similar problems leaves me hopeful that you can point me in the right direction, or worst case scenario tell me there is no solution at all, and that I will have to stick to the hateful Windows 10 which is supported and working. 1) not sure if it is just a simple graphics acceleration problem ? 2) as flgrx no longer supported (for AMD Catalyst on Radeon HD 6470 M - can I disable this GPU somewhere on boot - as this seems to be where boot goes into a tizz. If so, how would I do this. 3) if i did this would XORG then recognise other GPU - Intel HD 3000 and give me correct rendering to eliminate choppy video I am a noob, but have been playing with Ubuntu for some time, albeit at very low level, not totally computer illiterate, but do feel I am out of my depth in trying to resolve this. It just seems odd that it works fine on much lower spec and older desktops, but that I cant get this to work on my not so outdated laptop. Ubuntu Release 18.04.3 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg-server/+bug/1848965/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1848951] Re: Xorg and gnome-shell consuming large amount of CPU
I've been working on a number of issues causing this. It is much improved in Ubuntu 19.10 but not yet quite at the point of being declared fixed. Tracking in: https://gitlab.gnome.org/GNOME/mutter/issues/283 ** Package changed: xorg (Ubuntu) => mutter (Ubuntu) ** Changed in: mutter (Ubuntu) Status: New => Confirmed ** Changed in: mutter (Ubuntu) Assignee: (unassigned) => Daniel van Vugt (vanvugt) ** Bug watch added: gitlab.gnome.org/GNOME/mutter/issues #283 https://gitlab.gnome.org/GNOME/mutter/issues/283 ** Also affects: mutter via https://gitlab.gnome.org/GNOME/mutter/issues/283 Importance: Unknown Status: Unknown ** Summary changed: - Xorg and gnome-shell consuming large amount of CPU + Xorg and gnome-shell consuming large amount of CPU when just moving the mouse -- 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/1848951 Title: High CPU when just moving the mouse Status in Mutter: Unknown Status in gnome-shell package in Ubuntu: Confirmed Status in mutter package in Ubuntu: Confirmed Status in xorg-server package in Ubuntu: Confirmed Bug description: I have installed fresh Ubuntu 18.04.03 on my PC. Previously I had Ubuntu 16.04 version but didn't have any such problems with the cpu usage. But I have saw in terminal that somehow the processes Xorg and gnome- shell use always 20% when just moving the mouse around for 18.04 version. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: xorg 1:7.7+19ubuntu7.1 ProcVersionSignature: Ubuntu 5.0.0-31.33~18.04.1-generic 5.0.21 Uname: Linux 5.0.0-31-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.7 Architecture: amd64 CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Sun Oct 20 20:54:50 2019 DistUpgraded: Fresh install DistroCodename: bionic DistroVariant: ubuntu DkmsStatus: amdgpu, 19.30-855429, 5.0.0-31-generic, x86_64: installed ExtraDebuggingInterest: No GraphicsCard: Intel Corporation Xeon E3-1200 v3/4th Gen Core Processor Integrated Graphics Controller [8086:0412] (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] Advanced Micro Devices, Inc. [AMD/ATI] Cape Verde XT [Radeon HD 7770/8760 / R7 250X] [1002:683d] (prog-if 00 [VGA controller]) Subsystem: Micro-Star International Co., Ltd. [MSI] R7770-PMD1GD5 [1462:2710] InstallationDate: Installed on 2019-10-19 (0 days ago) InstallationMedia: Ubuntu 18.04.3 LTS "Bionic Beaver" - Release amd64 (20190805) MachineType: Gigabyte Technology Co., Ltd. B85M-D2V ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.0.0-31-generic root=UUID=1df6f37d-128f-4083-bd66-0a5c437227a0 ro quiet splash vt.handoff=1 SourcePackage: xorg UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 08/06/2015 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: F2 dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: B85M-D2V dmi.board.vendor: Gigabyte Technology Co., Ltd. dmi.board.version: x.x dmi.chassis.asset.tag: To Be Filled By O.E.M. dmi.chassis.type: 3 dmi.chassis.vendor: Gigabyte Technology Co., Ltd. dmi.chassis.version: To Be Filled By O.E.M. dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrF2:bd08/06/2015:svnGigabyteTechnologyCo.,Ltd.:pnB85M-D2V:pvrTobefilledbyO.E.M.:rvnGigabyteTechnologyCo.,Ltd.:rnB85M-D2V:rvrx.x:cvnGigabyteTechnologyCo.,Ltd.:ct3:cvrToBeFilledByO.E.M.: dmi.product.family: To be filled by O.E.M. dmi.product.name: B85M-D2V dmi.product.sku: To be filled by O.E.M. dmi.product.version: To be filled by O.E.M. dmi.sys.vendor: Gigabyte Technology Co., Ltd. version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.97-1ubuntu1~18.04.1 version.libgl1-mesa-dri: libgl1-mesa-dri 19.0.8-0ubuntu0~18.04.3 version.libgl1-mesa-glx: libgl1-mesa-glx 19.0.8-0ubuntu0~18.04.3 version.xserver-xorg-core: xserver-xorg-core N/A version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati N/A version.xserver-xorg-video-intel: xserver-xorg-video-intel N/A version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau N/A To manage notifications about this bug go to: https://bugs.launchpad.net/mutter/+bug/1848951/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1848900] Re: [amdgpu] Blank display with Eoan Ermine live DVD on Ryzen 3 2200G
** Summary changed: - Blank display with Eoan Ermine live DVD on Ryzen 3 2200G + [amdgpu] Blank display with Eoan Ermine live DVD on Ryzen 3 2200G ** Package changed: xorg (Ubuntu) => xserver-xorg-video-amdgpu (Ubuntu) -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to xorg in Ubuntu. https://bugs.launchpad.net/bugs/1848900 Title: [amdgpu] Blank display with Eoan Ermine live DVD on Ryzen 3 2200G Status in xserver-xorg-video-amdgpu package in Ubuntu: New Bug description: Regression with Ryzen 3 2200G, UEFI Asrock B450 Pro4 motherboard and 55-75 Hz monitor. Booting Xubuntu 19.10 live iso with safe graphics options did give a stable desktop display, but xubuntu@xubuntu:~$ xrandr xrandr: Failed to get size of gamma for output default Screen 0: minimum 1920 x 1080, current 1920 x 1080, maximum 1920 x 1080 default connected 1920x1080+0+0 0mm x 0mm 1920x1080 77.00* xubuntu@xubuntu:~$ The monitor is only supposed to have a maximum vertical refresh rate of 75 Hz. Xrandr reports 77 Hz as the only choice. The monitor reports 60 Hz, not that I trust the monitor. Swapping monitors and running many reboots the situation seems to be... Old versions of Ubuntu (Bionic and Dingo) can handle the hardware. Standard boot sometimes gives a blank screen. Standard boot sometimes gives a badly pixelated display (Ctl-Alt-F6, Ctl-Alt-F7 temporarily improves it). Connecting a 144 Hz monitor convinces something (the firmware?) that fast refreshes are OK on a slow monitor, or at least it fails to reread and abide by the slow monitor's limitations when swapping back. Something, I don't know what, convinces the computer to run the display at 60 Hz, sometimes. The motherboard has three video ports; DP, HDMI and VGA (using an onboard DP? to VGA converter chip). The fast monitor has DP, HDMI and VGA ports, but I only experimented with the DP connection. The slow monitor has VGA and DVI-D ports. I experimented with VGA to VGA and HDMI via a passive adapter to DVI. When running in the badly pixelated mode xorg seems to think that the VGA port is "DP-1". ProblemType: Bug DistroRelease: Ubuntu 19.10 Package: xorg 1:7.7+19ubuntu12 ProcVersionSignature: Ubuntu 5.3.0-18.19-generic 5.3.1 Uname: Linux 5.3.0-18-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.20.11-0ubuntu8 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CasperVersion: 1.427 CompositorRunning: None CurrentDesktop: XFCE Date: Sun Oct 20 00:17:34 2019 DistUpgraded: Fresh install DistroCodename: eoan DistroVariant: ubuntu ExtraDebuggingInterest: Yes GraphicsCard: Advanced Micro Devices, Inc. [AMD/ATI] Raven Ridge [Radeon Vega Series / Radeon Vega Mobile Series] [1002:15dd] (rev c8) (prog-if 00 [VGA controller]) Subsystem: Advanced Micro Devices, Inc. [AMD/ATI] Raven Ridge [Radeon Vega Series / Radeon Vega Mobile Series] [1002:15dd] LiveMediaBuild: Xubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017) MachineType: To Be Filled By O.E.M. To Be Filled By O.E.M. ProcKernelCmdLine: BOOT_IMAGE=/casper/vmlinuz file=/cdrom/preseed/username.seed quiet splash nomodeset --- SourcePackage: xorg UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 07/02/2019 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: P3.40 dmi.board.name: B450 Pro4 dmi.board.vendor: ASRock dmi.chassis.asset.tag: To Be Filled By O.E.M. dmi.chassis.type: 3 dmi.chassis.vendor: To Be Filled By O.E.M. dmi.chassis.version: To Be Filled By O.E.M. dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrP3.40:bd07/02/2019:svnToBeFilledByO.E.M.:pnToBeFilledByO.E.M.:pvrToBeFilledByO.E.M.:rvnASRock:rnB450Pro4:rvr:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.: dmi.product.family: To Be Filled By O.E.M. dmi.product.name: To Be Filled By O.E.M. dmi.product.sku: To Be Filled By O.E.M. dmi.product.version: To Be Filled By O.E.M. dmi.sys.vendor: To Be Filled By O.E.M. version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.99-1ubuntu1 version.libgl1-mesa-dri: libgl1-mesa-dri 19.2.1-1ubuntu1 version.libgl1-mesa-glx: libgl1-mesa-glx N/A version.xserver-xorg-core: xserver-xorg-core 2:1.20.5+git20191008-0ubuntu1 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.0.1-1ubuntu1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20190815-1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1 xserver.bootTime: Sat Oct 19 23:52:52 2019 xserver.configfile: default xserver.errors: open /dev/dri/card0: No such file or directory open /dev/dri/card0: No such file or directory Screen 0 deleted because of no matching config section.
[Touch-packages] [Bug 1848731] Re: Audio output device changes upon unlock/login
*** This bug is a duplicate of bug 1847570 *** https://bugs.launchpad.net/bugs/1847570 Thank you for taking the time to report this bug and helping to make Ubuntu better. This particular bug has already been reported and is a duplicate of bug 1847570, so it 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. Feel free to continue to report any other bugs you may find. ** This bug has been marked a duplicate of bug 1847570 PulseAudio automatically switches to HDMI sound output on login -- 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/1848731 Title: Audio output device changes upon unlock/login Status in linux package in Ubuntu: Incomplete Status in pulseaudio package in Ubuntu: New Bug description: I have a ThinkPad X250 and updated To Ubuntu 19.10 today from 19.04. Locking/Suspending and logging in changes my audio output device. This did not happen in 19.04. How to reproduce When I lock my session with key combination "Win+L" and then unlock it again, the sound that's been playing through my headphones/speakers stops playing. When I check the audio settings, "HDMI/DisplayPort 2 - Built-in audio" is selected. When I select "Headphones - Built-in audio", sound continues playing. There is no related log output in dmesg. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1848731/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1821641] Re: [HP Elitebook 840 G1] Screen is upside down on 19.04 daily
If that's a sufficiently different issue to this then please open a new bug. -- 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/1821641 Title: [HP Elitebook 840 G1] Screen is upside down on 19.04 daily Status in linux package in Ubuntu: Confirmed Status in systemd package in Ubuntu: Confirmed Bug description: On the 19.04 daily image (2019-03-24), the screen on my laptop is completely upside down, from the moment the GUI loads. This does not happen on 18.04 and 18.10. It appears to be an accelerometer issue since holding the laptop upside down flips the image to its correct orientation - basically the functionality of the accelerometer is suddenly inverted. Please contact me if you want me to help testing the issue on my hardware. Thanks! --- ProblemType: Bug ApportVersion: 2.20.10-0ubuntu23 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: sharper1380 F pulseaudio /dev/snd/controlC1: sharper1380 F pulseaudio CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 19.04 InstallationDate: Installed on 2019-03-30 (6 days ago) InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Alpha amd64 (20190330) MachineType: Hewlett-Packard HP EliteBook 840 G1 Package: linux (not installed) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=sv_SE.UTF-8 SHELL=/bin/bash ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.0.0-8-generic root=UUID=1e4bdc5f-0616-42f3-8da2-4ec27df3fc55 ro quiet splash vt.handoff=1 ProcVersionSignature: Ubuntu 5.0.0-8.9-generic 5.0.1 RelatedPackageVersions: linux-restricted-modules-5.0.0-8-generic N/A linux-backports-modules-5.0.0-8-generic N/A linux-firmware 1.178 Tags: disco Uname: Linux 5.0.0-8-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 04/12/2018 dmi.bios.vendor: Hewlett-Packard dmi.bios.version: L71 Ver. 01.44 dmi.board.name: 198F dmi.board.vendor: Hewlett-Packard dmi.board.version: KBC Version 15.59 dmi.chassis.asset.tag: 5CG4430MGN dmi.chassis.type: 10 dmi.chassis.vendor: Hewlett-Packard dmi.modalias: dmi:bvnHewlett-Packard:bvrL71Ver.01.44:bd04/12/2018:svnHewlett-Packard:pnHPEliteBook840G1:pvrA3009DD10203:rvnHewlett-Packard:rn198F:rvrKBCVersion15.59:cvnHewlett-Packard:ct10:cvr: dmi.product.family: 103C_5336AN G=N L=BUS B=HP S=ELI dmi.product.name: HP EliteBook 840 G1 dmi.product.sku: D1F44AV dmi.product.version: A3009DD10203 dmi.sys.vendor: Hewlett-Packard To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1821641/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1791405] Re: bluetooth always in discoverable mode (security issue)
** Also affects: gnome-bluetooth (Ubuntu Focal) Importance: Medium Status: Fix Released ** Also affects: bluez (Ubuntu Focal) Importance: Undecided Status: Confirmed ** Changed in: bluez (Ubuntu Focal) Status: Confirmed => Triaged ** Changed in: bluez (Ubuntu Focal) Importance: Undecided => Medium ** Changed in: bluez (Ubuntu Eoan) Status: Fix Committed => Triaged ** Changed in: bluez (Ubuntu Eoan) Importance: Undecided => Medium ** No longer affects: bluez (Ubuntu Eoan) ** Tags added: fixed-upstream -- 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/1791405 Title: bluetooth always in discoverable mode (security issue) Status in bluez package in Ubuntu: Triaged Status in gnome-bluetooth package in Ubuntu: Fix Released Status in gnome-bluetooth source package in Bionic: Fix Released Status in gnome-bluetooth source package in Cosmic: Fix Released Status in gnome-bluetooth source package in Disco: Fix Released Status in bluez source package in Focal: Triaged Status in gnome-bluetooth source package in Focal: Fix Released Status in gnome-bluetooth package in Fedora: Won't Fix Bug description: Excerpt from a similar report (https://bugzilla.redhat.com/show_bug.cgi?id=1602985) : Opening the Bluetooth settings will make the device discoverable again, but does not make the device undiscoverable after the settings are closed (this is not intended behavior; devices should only be discoverable when the bluetooth settings UI is open). There seem to be a merge request : https://gitlab.gnome.org/GNOME/gnome-bluetooth/merge_requests/1 Could you please merge it asap, it should be treated as a security issue IMHO. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/1791405/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1846148] Re: Realtek ALC256M with DTS Audio Processing internal microphone doesn't work on Redmi Book 14 2019
Reploy #17, no, no sound could be record. all quiet. -- 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/1846148 Title: Realtek ALC256M with DTS Audio Processing internal microphone doesn't work on Redmi Book 14 2019 Status in alsa-driver package in Ubuntu: Confirmed Bug description: Sound works okay but the internal mic doesn't work. When I plug in headset, the mic on headset also doens't work. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: alsa-base 1.0.25+dfsg-0ubuntu5 ProcVersionSignature: Ubuntu 5.0.0-29.31~18.04.1-generic 5.0.21 Uname: Linux 5.0.0-29-generic x86_64 NonfreeKernelModules: wl ApportVersion: 2.20.9-0ubuntu7.7 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: lilian 1689 F pulseaudio CurrentDesktop: ubuntu:GNOME Date: Tue Oct 1 12:27:10 2019 InstallationDate: Installed on 2019-09-21 (9 days ago) InstallationMedia: Ubuntu 18.04.3 LTS "Bionic Beaver" - Release amd64 (20190805) PackageArchitecture: all SourcePackage: alsa-driver Symptom: audio Title: PCI/internal sound card not detected UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 08/19/2019 dmi.bios.vendor: TIMI dmi.bios.version: RMRCM400P0100 dmi.board.name: TM1901 dmi.board.vendor: TIMI dmi.chassis.type: 10 dmi.chassis.vendor: TIMI dmi.modalias: dmi:bvnTIMI:bvrRMRCM400P0100:bd08/19/2019:svnTIMI:pnRedmiBook14:pvr:rvnTIMI:rnTM1901:rvr:cvnTIMI:ct10:cvr: dmi.product.family: Mi Laptop dmi.product.name: RedmiBook 14 dmi.product.sku: TM1901-24822 dmi.sys.vendor: TIMI To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1846148/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1848969] [NEW] src/date-time.cpp:171:GDateTime* unity::indicator::datetime::DateTime::get() const: assertion failed: (m_dt)
Public bug reported: After upgrading to Ubuntu 19.10, indicator-datetime 15.10+19.10.20190819.1-0ubuntu1 crashes right from the start: $ /usr/lib/x86_64-linux-gnu/indicator-datetime/indicator-datetime-service (process:17641): Indicator-Datetime-WARNING **: 01:46:35.442: Unrecognized TZID: 'Etc/Utc' (process:17641): Indicator-Datetime-WARNING **: 01:46:35.442: Unrecognized TZID: 'Etc/Utc' (process:17641): Indicator-Datetime-WARNING **: 01:46:35.448: Unrecognized TZID: 'Etc/Utc' (process:17641): libecal-CRITICAL **: 01:46:35.457: e_cal_component_datetime_get_value: assertion 'dt != NULL' failed (process:17641): libecal-CRITICAL **: 01:46:35.457: e_cal_component_datetime_get_value: assertion 'dt != NULL' failed (process:17641): libical-glib-CRITICAL **: 01:46:35.457: i_cal_time_as_timet: assertion 'I_CAL_IS_TIME (tt)' failed (process:17641): libical-glib-CRITICAL **: 01:46:35.457: i_cal_time_as_timet: assertion 'I_CAL_IS_TIME (tt)' failed [...] (process:17641): libical-glib-CRITICAL **: 01:46:35.458: i_cal_time_as_timet: assertion 'I_CAL_IS_TIME (tt)' failed (process:17641): libecal-CRITICAL **: 01:46:35.458: e_cal_component_datetime_get_value: assertion 'dt != NULL' failed (process:17641): libecal-CRITICAL **: 01:46:35.458: e_cal_component_datetime_get_value: assertion 'dt != NULL' failed (process:17641): libical-glib-CRITICAL **: 01:46:35.458: i_cal_time_as_timet: assertion 'I_CAL_IS_TIME (tt)' failed (process:17641): libical-glib-CRITICAL **: 01:46:35.458: i_cal_time_as_timet: assertion 'I_CAL_IS_TIME (tt)' failed ** Indicator-Datetime:ERROR:/build/indicator-datetime-P60bPZ/indicator-datetime-15.10+19.10.20190819.1/src/date-time.cpp:171:GDateTime* unity::indicator::datetime::DateTime::get() const: assertion failed: (m_dt) Bail out! Indicator-Datetime:ERROR:/build/indicator-datetime-P60bPZ/indicator-datetime-15.10+19.10.20190819.1/src/date-time.cpp:171:GDateTime* unity::indicator::datetime::DateTime::get() const: assertion failed: (m_dt) ** Affects: indicator-datetime (Ubuntu) Importance: Critical Status: Confirmed ** Changed in: indicator-datetime (Ubuntu) Importance: Undecided => Critical -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to indicator-datetime in Ubuntu. https://bugs.launchpad.net/bugs/1848969 Title: src/date-time.cpp:171:GDateTime* unity::indicator::datetime::DateTime::get() const: assertion failed: (m_dt) Status in indicator-datetime package in Ubuntu: Confirmed Bug description: After upgrading to Ubuntu 19.10, indicator-datetime 15.10+19.10.20190819.1-0ubuntu1 crashes right from the start: $ /usr/lib/x86_64-linux-gnu/indicator-datetime/indicator-datetime-service (process:17641): Indicator-Datetime-WARNING **: 01:46:35.442: Unrecognized TZID: 'Etc/Utc' (process:17641): Indicator-Datetime-WARNING **: 01:46:35.442: Unrecognized TZID: 'Etc/Utc' (process:17641): Indicator-Datetime-WARNING **: 01:46:35.448: Unrecognized TZID: 'Etc/Utc' (process:17641): libecal-CRITICAL **: 01:46:35.457: e_cal_component_datetime_get_value: assertion 'dt != NULL' failed (process:17641): libecal-CRITICAL **: 01:46:35.457: e_cal_component_datetime_get_value: assertion 'dt != NULL' failed (process:17641): libical-glib-CRITICAL **: 01:46:35.457: i_cal_time_as_timet: assertion 'I_CAL_IS_TIME (tt)' failed (process:17641): libical-glib-CRITICAL **: 01:46:35.457: i_cal_time_as_timet: assertion 'I_CAL_IS_TIME (tt)' failed [...] (process:17641): libical-glib-CRITICAL **: 01:46:35.458: i_cal_time_as_timet: assertion 'I_CAL_IS_TIME (tt)' failed (process:17641): libecal-CRITICAL **: 01:46:35.458: e_cal_component_datetime_get_value: assertion 'dt != NULL' failed (process:17641): libecal-CRITICAL **: 01:46:35.458: e_cal_component_datetime_get_value: assertion 'dt != NULL' failed (process:17641): libical-glib-CRITICAL **: 01:46:35.458: i_cal_time_as_timet: assertion 'I_CAL_IS_TIME (tt)' failed (process:17641): libical-glib-CRITICAL **: 01:46:35.458: i_cal_time_as_timet: assertion 'I_CAL_IS_TIME (tt)' failed ** Indicator-Datetime:ERROR:/build/indicator-datetime-P60bPZ/indicator-datetime-15.10+19.10.20190819.1/src/date-time.cpp:171:GDateTime* unity::indicator::datetime::DateTime::get() const: assertion failed: (m_dt) Bail out! Indicator-Datetime:ERROR:/build/indicator-datetime-P60bPZ/indicator-datetime-15.10+19.10.20190819.1/src/date-time.cpp:171:GDateTime* unity::indicator::datetime::DateTime::get() const: assertion failed: (m_dt) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/indicator-datetime/+bug/1848969/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1848969] Re: src/date-time.cpp:171:GDateTime* unity::indicator::datetime::DateTime::get() const: assertion failed: (m_dt)
I am not the only one running into this bug: https://ubuntu- mate.community/t/clock-indicator-wont-appear-19-10/20424 ** Changed in: indicator-datetime (Ubuntu) Status: New => Confirmed -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to indicator-datetime in Ubuntu. https://bugs.launchpad.net/bugs/1848969 Title: src/date-time.cpp:171:GDateTime* unity::indicator::datetime::DateTime::get() const: assertion failed: (m_dt) Status in indicator-datetime package in Ubuntu: Confirmed Bug description: After upgrading to Ubuntu 19.10, indicator-datetime 15.10+19.10.20190819.1-0ubuntu1 crashes right from the start: $ /usr/lib/x86_64-linux-gnu/indicator-datetime/indicator-datetime-service (process:17641): Indicator-Datetime-WARNING **: 01:46:35.442: Unrecognized TZID: 'Etc/Utc' (process:17641): Indicator-Datetime-WARNING **: 01:46:35.442: Unrecognized TZID: 'Etc/Utc' (process:17641): Indicator-Datetime-WARNING **: 01:46:35.448: Unrecognized TZID: 'Etc/Utc' (process:17641): libecal-CRITICAL **: 01:46:35.457: e_cal_component_datetime_get_value: assertion 'dt != NULL' failed (process:17641): libecal-CRITICAL **: 01:46:35.457: e_cal_component_datetime_get_value: assertion 'dt != NULL' failed (process:17641): libical-glib-CRITICAL **: 01:46:35.457: i_cal_time_as_timet: assertion 'I_CAL_IS_TIME (tt)' failed (process:17641): libical-glib-CRITICAL **: 01:46:35.457: i_cal_time_as_timet: assertion 'I_CAL_IS_TIME (tt)' failed [...] (process:17641): libical-glib-CRITICAL **: 01:46:35.458: i_cal_time_as_timet: assertion 'I_CAL_IS_TIME (tt)' failed (process:17641): libecal-CRITICAL **: 01:46:35.458: e_cal_component_datetime_get_value: assertion 'dt != NULL' failed (process:17641): libecal-CRITICAL **: 01:46:35.458: e_cal_component_datetime_get_value: assertion 'dt != NULL' failed (process:17641): libical-glib-CRITICAL **: 01:46:35.458: i_cal_time_as_timet: assertion 'I_CAL_IS_TIME (tt)' failed (process:17641): libical-glib-CRITICAL **: 01:46:35.458: i_cal_time_as_timet: assertion 'I_CAL_IS_TIME (tt)' failed ** Indicator-Datetime:ERROR:/build/indicator-datetime-P60bPZ/indicator-datetime-15.10+19.10.20190819.1/src/date-time.cpp:171:GDateTime* unity::indicator::datetime::DateTime::get() const: assertion failed: (m_dt) Bail out! Indicator-Datetime:ERROR:/build/indicator-datetime-P60bPZ/indicator-datetime-15.10+19.10.20190819.1/src/date-time.cpp:171:GDateTime* unity::indicator::datetime::DateTime::get() const: assertion failed: (m_dt) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/indicator-datetime/+bug/1848969/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1787867] Re: Ubuntu 18.04 LTS bluetooth left discoverable
This is a serious security issue and it's fixed in Gnome upstream. Probably should be backported. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to indicator-bluetooth in Ubuntu. https://bugs.launchpad.net/bugs/1787867 Title: Ubuntu 18.04 LTS bluetooth left discoverable Status in indicator-bluetooth package in Ubuntu: Confirmed Bug description: Ubuntu 18.04 LTS, when Bluetooth is on, the computer stays discoverable which opens up unnecessary vulnerability surface. There should be a separate UI switch for discoverability with auto timeout. Leaving bluetooth on (using a Bluetooth mouse) should not leave the computer always discoverable. Current behavior does not match documentation https://help.ubuntu.com/stable/ubuntu-help/bluetooth- visibility.html.en, even without Bluetooth panel open, the computer is still discoverable. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/indicator-bluetooth/+bug/1787867/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1848965] [NEW] Video Playback very choppy
Public bug reported: My laptop is HP Pavilion g7 (Intel® Core™ i5-2430M CPU with Radeon HD 6470M and Intel HD 3000 GPUs Already have played with Ubuntu on older spec desktops with no issues at all, however when when installing Ubuntu 18.04 from installation USB, had to boot with nomodeset to overcome freezing as a result of Ubuntu 18.04 not recognising/supporting these drivers Tried to search for additional drivers but none found Video handling resorts to llvmpipe (LLVM 9.0.0, 256 bits) My problem is that Video Playback is VLC very choppy in full screen mode - seems to get a little better when minimised, but effectively not usable. Have tried many threads posted regarding this problem, but nothing seems to work. Would really like to migrate my workload onto Ubuntu 18.04 operating system, but this seems to be a real non starter where i can't play video content, as video editing is a core function in my workload. Not sure if there is a solution for this, however after researching many similar threads, coupled with your in depth response to similar problems leaves me hopeful that you can point me in the right direction, or worst case scenario tell me there is no solution at all, and that I will have to stick to the hateful Windows 10 which is supported and working. 1) not sure if it is just a simple graphics acceleration problem ? 2) as flgrx no longer supported (for AMD Catalyst on Radeon HD 6470 M - can I disable this GPU somewhere on boot - as this seems to be where boot goes into a tizz. If so, how would I do this. 3) if i did this would XORG then recognise other GPU - Intel HD 3000 and give me correct rendering to eliminate choppy video I am a noob, but have been playing with Ubuntu for some time, albeit at very low level, not totally computer illiterate, but do feel I am out of my depth in trying to resolve this. It just seems odd that it works fine on much lower spec and older desktops, but that I cant get this to work on my not so outdated laptop. Ubuntu Release 18.04.3 ** Affects: xorg (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/1848965 Title: Video Playback very choppy Status in xorg package in Ubuntu: New Bug description: My laptop is HP Pavilion g7 (Intel® Core™ i5-2430M CPU with Radeon HD 6470M and Intel HD 3000 GPUs Already have played with Ubuntu on older spec desktops with no issues at all, however when when installing Ubuntu 18.04 from installation USB, had to boot with nomodeset to overcome freezing as a result of Ubuntu 18.04 not recognising/supporting these drivers Tried to search for additional drivers but none found Video handling resorts to llvmpipe (LLVM 9.0.0, 256 bits) My problem is that Video Playback is VLC very choppy in full screen mode - seems to get a little better when minimised, but effectively not usable. Have tried many threads posted regarding this problem, but nothing seems to work. Would really like to migrate my workload onto Ubuntu 18.04 operating system, but this seems to be a real non starter where i can't play video content, as video editing is a core function in my workload. Not sure if there is a solution for this, however after researching many similar threads, coupled with your in depth response to similar problems leaves me hopeful that you can point me in the right direction, or worst case scenario tell me there is no solution at all, and that I will have to stick to the hateful Windows 10 which is supported and working. 1) not sure if it is just a simple graphics acceleration problem ? 2) as flgrx no longer supported (for AMD Catalyst on Radeon HD 6470 M - can I disable this GPU somewhere on boot - as this seems to be where boot goes into a tizz. If so, how would I do this. 3) if i did this would XORG then recognise other GPU - Intel HD 3000 and give me correct rendering to eliminate choppy video I am a noob, but have been playing with Ubuntu for some time, albeit at very low level, not totally computer illiterate, but do feel I am out of my depth in trying to resolve this. It just seems odd that it works fine on much lower spec and older desktops, but that I cant get this to work on my not so outdated laptop. Ubuntu Release 18.04.3 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1848965/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1848951] Re: Xorg and gnome-shell consuming large amount of CPU
** Patch removed: "Screenshot from 2019-10-20 20-01-53.png" https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1848951/+attachment/5298666/+files/Screenshot%20from%202019-10-20%2020-01-53.png -- 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/1848951 Title: Xorg and gnome-shell consuming large amount of CPU Status in xorg package in Ubuntu: New Bug description: I have installed fresh Ubuntu 18.04.03 on my PC. Previously I had Ubuntu 16.04 version but didn't have any such problems with the cpu usage. But I have saw in terminal that somehow the processes Xorg and gnome- shell use always 20% when just moving the mouse around for 18.04 version. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: xorg 1:7.7+19ubuntu7.1 ProcVersionSignature: Ubuntu 5.0.0-31.33~18.04.1-generic 5.0.21 Uname: Linux 5.0.0-31-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.7 Architecture: amd64 CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Sun Oct 20 20:54:50 2019 DistUpgraded: Fresh install DistroCodename: bionic DistroVariant: ubuntu DkmsStatus: amdgpu, 19.30-855429, 5.0.0-31-generic, x86_64: installed ExtraDebuggingInterest: No GraphicsCard: Intel Corporation Xeon E3-1200 v3/4th Gen Core Processor Integrated Graphics Controller [8086:0412] (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] Advanced Micro Devices, Inc. [AMD/ATI] Cape Verde XT [Radeon HD 7770/8760 / R7 250X] [1002:683d] (prog-if 00 [VGA controller]) Subsystem: Micro-Star International Co., Ltd. [MSI] R7770-PMD1GD5 [1462:2710] InstallationDate: Installed on 2019-10-19 (0 days ago) InstallationMedia: Ubuntu 18.04.3 LTS "Bionic Beaver" - Release amd64 (20190805) MachineType: Gigabyte Technology Co., Ltd. B85M-D2V ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.0.0-31-generic root=UUID=1df6f37d-128f-4083-bd66-0a5c437227a0 ro quiet splash vt.handoff=1 SourcePackage: xorg UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 08/06/2015 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: F2 dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: B85M-D2V dmi.board.vendor: Gigabyte Technology Co., Ltd. dmi.board.version: x.x dmi.chassis.asset.tag: To Be Filled By O.E.M. dmi.chassis.type: 3 dmi.chassis.vendor: Gigabyte Technology Co., Ltd. dmi.chassis.version: To Be Filled By O.E.M. dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrF2:bd08/06/2015:svnGigabyteTechnologyCo.,Ltd.:pnB85M-D2V:pvrTobefilledbyO.E.M.:rvnGigabyteTechnologyCo.,Ltd.:rnB85M-D2V:rvrx.x:cvnGigabyteTechnologyCo.,Ltd.:ct3:cvrToBeFilledByO.E.M.: dmi.product.family: To be filled by O.E.M. dmi.product.name: B85M-D2V dmi.product.sku: To be filled by O.E.M. dmi.product.version: To be filled by O.E.M. dmi.sys.vendor: Gigabyte Technology Co., Ltd. version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.97-1ubuntu1~18.04.1 version.libgl1-mesa-dri: libgl1-mesa-dri 19.0.8-0ubuntu0~18.04.3 version.libgl1-mesa-glx: libgl1-mesa-glx 19.0.8-0ubuntu0~18.04.3 version.xserver-xorg-core: xserver-xorg-core N/A version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati N/A version.xserver-xorg-video-intel: xserver-xorg-video-intel N/A version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau N/A To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1848951/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1848951] Re: Xorg and gnome-shell consuming large amount of CPU
The attachment "Screenshot from 2019-10-20 20-01-53.png" seems to be a patch. If it isn't, please remove the "patch" flag from the attachment, remove the "patch" tag, and if you are a member of the ~ubuntu- reviewers, unsubscribe the team. [This is an automated message performed by a Launchpad user owned by ~brian-murray, for any issues please contact him.] ** Tags added: patch -- 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/1848951 Title: Xorg and gnome-shell consuming large amount of CPU Status in xorg package in Ubuntu: New Bug description: I have installed fresh Ubuntu 18.04.03 on my PC. Previously I had Ubuntu 16.04 version but didn't have any such problems with the cpu usage. But I have saw in terminal that somehow the processes Xorg and gnome- shell use always 20% when just moving the mouse around for 18.04 version. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: xorg 1:7.7+19ubuntu7.1 ProcVersionSignature: Ubuntu 5.0.0-31.33~18.04.1-generic 5.0.21 Uname: Linux 5.0.0-31-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.7 Architecture: amd64 CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Sun Oct 20 20:54:50 2019 DistUpgraded: Fresh install DistroCodename: bionic DistroVariant: ubuntu DkmsStatus: amdgpu, 19.30-855429, 5.0.0-31-generic, x86_64: installed ExtraDebuggingInterest: No GraphicsCard: Intel Corporation Xeon E3-1200 v3/4th Gen Core Processor Integrated Graphics Controller [8086:0412] (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] Advanced Micro Devices, Inc. [AMD/ATI] Cape Verde XT [Radeon HD 7770/8760 / R7 250X] [1002:683d] (prog-if 00 [VGA controller]) Subsystem: Micro-Star International Co., Ltd. [MSI] R7770-PMD1GD5 [1462:2710] InstallationDate: Installed on 2019-10-19 (0 days ago) InstallationMedia: Ubuntu 18.04.3 LTS "Bionic Beaver" - Release amd64 (20190805) MachineType: Gigabyte Technology Co., Ltd. B85M-D2V ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.0.0-31-generic root=UUID=1df6f37d-128f-4083-bd66-0a5c437227a0 ro quiet splash vt.handoff=1 SourcePackage: xorg UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 08/06/2015 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: F2 dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: B85M-D2V dmi.board.vendor: Gigabyte Technology Co., Ltd. dmi.board.version: x.x dmi.chassis.asset.tag: To Be Filled By O.E.M. dmi.chassis.type: 3 dmi.chassis.vendor: Gigabyte Technology Co., Ltd. dmi.chassis.version: To Be Filled By O.E.M. dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrF2:bd08/06/2015:svnGigabyteTechnologyCo.,Ltd.:pnB85M-D2V:pvrTobefilledbyO.E.M.:rvnGigabyteTechnologyCo.,Ltd.:rnB85M-D2V:rvrx.x:cvnGigabyteTechnologyCo.,Ltd.:ct3:cvrToBeFilledByO.E.M.: dmi.product.family: To be filled by O.E.M. dmi.product.name: B85M-D2V dmi.product.sku: To be filled by O.E.M. dmi.product.version: To be filled by O.E.M. dmi.sys.vendor: Gigabyte Technology Co., Ltd. version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.97-1ubuntu1~18.04.1 version.libgl1-mesa-dri: libgl1-mesa-dri 19.0.8-0ubuntu0~18.04.3 version.libgl1-mesa-glx: libgl1-mesa-glx 19.0.8-0ubuntu0~18.04.3 version.xserver-xorg-core: xserver-xorg-core N/A version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati N/A version.xserver-xorg-video-intel: xserver-xorg-video-intel N/A version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau N/A To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1848951/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1848951] Re: Xorg and gnome-shell consuming large amount of CPU
** Description changed: - I have installed fresh Ubuntu 18.04.03 on my PC. + I have installed fresh Ubuntu 18.04.03 on my PC. Previously I had Ubuntu + 16.04 version but didn't have any such problems with the cpu usage. But I have saw in terminal that somehow the processes Xorg and gnome- - shell use always 20% when just moving the mouse around. + shell use always 20% when just moving the mouse around for 18.04 + version. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: xorg 1:7.7+19ubuntu7.1 ProcVersionSignature: Ubuntu 5.0.0-31.33~18.04.1-generic 5.0.21 Uname: Linux 5.0.0-31-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.7 Architecture: amd64 CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Sun Oct 20 20:54:50 2019 DistUpgraded: Fresh install DistroCodename: bionic DistroVariant: ubuntu DkmsStatus: amdgpu, 19.30-855429, 5.0.0-31-generic, x86_64: installed ExtraDebuggingInterest: No GraphicsCard: - Intel Corporation Xeon E3-1200 v3/4th Gen Core Processor Integrated Graphics Controller [8086:0412] (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] - Advanced Micro Devices, Inc. [AMD/ATI] Cape Verde XT [Radeon HD 7770/8760 / R7 250X] [1002:683d] (prog-if 00 [VGA controller]) -Subsystem: Micro-Star International Co., Ltd. [MSI] R7770-PMD1GD5 [1462:2710] + Intel Corporation Xeon E3-1200 v3/4th Gen Core Processor Integrated Graphics Controller [8086:0412] (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] + Advanced Micro Devices, Inc. [AMD/ATI] Cape Verde XT [Radeon HD 7770/8760 / R7 250X] [1002:683d] (prog-if 00 [VGA controller]) + Subsystem: Micro-Star International Co., Ltd. [MSI] R7770-PMD1GD5 [1462:2710] InstallationDate: Installed on 2019-10-19 (0 days ago) InstallationMedia: Ubuntu 18.04.3 LTS "Bionic Beaver" - Release amd64 (20190805) MachineType: Gigabyte Technology Co., Ltd. B85M-D2V ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.0.0-31-generic root=UUID=1df6f37d-128f-4083-bd66-0a5c437227a0 ro quiet splash vt.handoff=1 SourcePackage: xorg UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 08/06/2015 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: F2 dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: B85M-D2V dmi.board.vendor: Gigabyte Technology Co., Ltd. dmi.board.version: x.x dmi.chassis.asset.tag: To Be Filled By O.E.M. dmi.chassis.type: 3 dmi.chassis.vendor: Gigabyte Technology Co., Ltd. dmi.chassis.version: To Be Filled By O.E.M. dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrF2:bd08/06/2015:svnGigabyteTechnologyCo.,Ltd.:pnB85M-D2V:pvrTobefilledbyO.E.M.:rvnGigabyteTechnologyCo.,Ltd.:rnB85M-D2V:rvrx.x:cvnGigabyteTechnologyCo.,Ltd.:ct3:cvrToBeFilledByO.E.M.: dmi.product.family: To be filled by O.E.M. dmi.product.name: B85M-D2V dmi.product.sku: To be filled by O.E.M. dmi.product.version: To be filled by O.E.M. dmi.sys.vendor: Gigabyte Technology Co., Ltd. version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.97-1ubuntu1~18.04.1 version.libgl1-mesa-dri: libgl1-mesa-dri 19.0.8-0ubuntu0~18.04.3 version.libgl1-mesa-glx: libgl1-mesa-glx 19.0.8-0ubuntu0~18.04.3 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 -- 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/1848951 Title: Xorg and gnome-shell consuming large amount of CPU Status in xorg package in Ubuntu: New Bug description: I have installed fresh Ubuntu 18.04.03 on my PC. Previously I had Ubuntu 16.04 version but didn't have any such problems with the cpu usage. But I have saw in terminal that somehow the processes Xorg and gnome- shell use always 20% when just moving the mouse around for 18.04 version. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: xorg 1:7.7+19ubuntu7.1 ProcVersionSignature: Ubuntu 5.0.0-31.33~18.04.1-generic 5.0.21 Uname: Linux 5.0.0-31-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.7 Architecture: amd64 CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Sun Oct 20 20:54:50 2019 DistUpgraded: Fresh install DistroCodename: bionic DistroVariant: ubuntu DkmsStatus: amdgpu, 19.30-855429, 5.0.0-31-generic, x86_64: installed ExtraDebuggingInterest: No GraphicsCard: Intel Corporation Xeon E3-1200 v3/4th Gen Core Processor Integrated Graphics Controller [8086:0412] (rev 06) (prog-if 00 [VGA
[Touch-packages] [Bug 1848951] Re: Xorg and gnome-shell consuming large amount of CPU
** Attachment added: "Screenshot from 2019-10-20 20-05-06.png" https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1848951/+attachment/5298682/+files/Screenshot%20from%202019-10-20%2020-05-06.png -- 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/1848951 Title: Xorg and gnome-shell consuming large amount of CPU Status in xorg package in Ubuntu: New Bug description: I have installed fresh Ubuntu 18.04.03 on my PC. But I have saw in terminal that somehow the processes Xorg and gnome- shell use always 20% when just moving the mouse around. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: xorg 1:7.7+19ubuntu7.1 ProcVersionSignature: Ubuntu 5.0.0-31.33~18.04.1-generic 5.0.21 Uname: Linux 5.0.0-31-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.7 Architecture: amd64 CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Sun Oct 20 20:54:50 2019 DistUpgraded: Fresh install DistroCodename: bionic DistroVariant: ubuntu DkmsStatus: amdgpu, 19.30-855429, 5.0.0-31-generic, x86_64: installed ExtraDebuggingInterest: No GraphicsCard: Intel Corporation Xeon E3-1200 v3/4th Gen Core Processor Integrated Graphics Controller [8086:0412] (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] Advanced Micro Devices, Inc. [AMD/ATI] Cape Verde XT [Radeon HD 7770/8760 / R7 250X] [1002:683d] (prog-if 00 [VGA controller]) Subsystem: Micro-Star International Co., Ltd. [MSI] R7770-PMD1GD5 [1462:2710] InstallationDate: Installed on 2019-10-19 (0 days ago) InstallationMedia: Ubuntu 18.04.3 LTS "Bionic Beaver" - Release amd64 (20190805) MachineType: Gigabyte Technology Co., Ltd. B85M-D2V ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.0.0-31-generic root=UUID=1df6f37d-128f-4083-bd66-0a5c437227a0 ro quiet splash vt.handoff=1 SourcePackage: xorg UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 08/06/2015 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: F2 dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: B85M-D2V dmi.board.vendor: Gigabyte Technology Co., Ltd. dmi.board.version: x.x dmi.chassis.asset.tag: To Be Filled By O.E.M. dmi.chassis.type: 3 dmi.chassis.vendor: Gigabyte Technology Co., Ltd. dmi.chassis.version: To Be Filled By O.E.M. dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrF2:bd08/06/2015:svnGigabyteTechnologyCo.,Ltd.:pnB85M-D2V:pvrTobefilledbyO.E.M.:rvnGigabyteTechnologyCo.,Ltd.:rnB85M-D2V:rvrx.x:cvnGigabyteTechnologyCo.,Ltd.:ct3:cvrToBeFilledByO.E.M.: dmi.product.family: To be filled by O.E.M. dmi.product.name: B85M-D2V dmi.product.sku: To be filled by O.E.M. dmi.product.version: To be filled by O.E.M. dmi.sys.vendor: Gigabyte Technology Co., Ltd. version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.97-1ubuntu1~18.04.1 version.libgl1-mesa-dri: libgl1-mesa-dri 19.0.8-0ubuntu0~18.04.3 version.libgl1-mesa-glx: libgl1-mesa-glx 19.0.8-0ubuntu0~18.04.3 version.xserver-xorg-core: xserver-xorg-core N/A version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati N/A version.xserver-xorg-video-intel: xserver-xorg-video-intel N/A version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau N/A To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1848951/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1848951] [NEW] Xorg and gnome-shell consuming large amount of CPU
Public bug reported: I have installed fresh Ubuntu 18.04.03 on my PC. But I have saw in terminal that somehow the processes Xorg and gnome- shell use always 20% when just moving the mouse around. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: xorg 1:7.7+19ubuntu7.1 ProcVersionSignature: Ubuntu 5.0.0-31.33~18.04.1-generic 5.0.21 Uname: Linux 5.0.0-31-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.7 Architecture: amd64 CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Sun Oct 20 20:54:50 2019 DistUpgraded: Fresh install DistroCodename: bionic DistroVariant: ubuntu DkmsStatus: amdgpu, 19.30-855429, 5.0.0-31-generic, x86_64: installed ExtraDebuggingInterest: No GraphicsCard: Intel Corporation Xeon E3-1200 v3/4th Gen Core Processor Integrated Graphics Controller [8086:0412] (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] Advanced Micro Devices, Inc. [AMD/ATI] Cape Verde XT [Radeon HD 7770/8760 / R7 250X] [1002:683d] (prog-if 00 [VGA controller]) Subsystem: Micro-Star International Co., Ltd. [MSI] R7770-PMD1GD5 [1462:2710] InstallationDate: Installed on 2019-10-19 (0 days ago) InstallationMedia: Ubuntu 18.04.3 LTS "Bionic Beaver" - Release amd64 (20190805) MachineType: Gigabyte Technology Co., Ltd. B85M-D2V ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.0.0-31-generic root=UUID=1df6f37d-128f-4083-bd66-0a5c437227a0 ro quiet splash vt.handoff=1 SourcePackage: xorg UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 08/06/2015 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: F2 dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: B85M-D2V dmi.board.vendor: Gigabyte Technology Co., Ltd. dmi.board.version: x.x dmi.chassis.asset.tag: To Be Filled By O.E.M. dmi.chassis.type: 3 dmi.chassis.vendor: Gigabyte Technology Co., Ltd. dmi.chassis.version: To Be Filled By O.E.M. dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrF2:bd08/06/2015:svnGigabyteTechnologyCo.,Ltd.:pnB85M-D2V:pvrTobefilledbyO.E.M.:rvnGigabyteTechnologyCo.,Ltd.:rnB85M-D2V:rvrx.x:cvnGigabyteTechnologyCo.,Ltd.:ct3:cvrToBeFilledByO.E.M.: dmi.product.family: To be filled by O.E.M. dmi.product.name: B85M-D2V dmi.product.sku: To be filled by O.E.M. dmi.product.version: To be filled by O.E.M. dmi.sys.vendor: Gigabyte Technology Co., Ltd. version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.97-1ubuntu1~18.04.1 version.libgl1-mesa-dri: libgl1-mesa-dri 19.0.8-0ubuntu0~18.04.3 version.libgl1-mesa-glx: libgl1-mesa-glx 19.0.8-0ubuntu0~18.04.3 version.xserver-xorg-core: xserver-xorg-core N/A version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati N/A version.xserver-xorg-video-intel: xserver-xorg-video-intel N/A version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau N/A ** Affects: xorg (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug bionic ubuntu ** Patch added: "Screenshot from 2019-10-20 20-01-53.png" https://bugs.launchpad.net/bugs/1848951/+attachment/5298666/+files/Screenshot%20from%202019-10-20%2020-01-53.png -- 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/1848951 Title: Xorg and gnome-shell consuming large amount of CPU Status in xorg package in Ubuntu: New Bug description: I have installed fresh Ubuntu 18.04.03 on my PC. But I have saw in terminal that somehow the processes Xorg and gnome- shell use always 20% when just moving the mouse around. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: xorg 1:7.7+19ubuntu7.1 ProcVersionSignature: Ubuntu 5.0.0-31.33~18.04.1-generic 5.0.21 Uname: Linux 5.0.0-31-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.7 Architecture: amd64 CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Sun Oct 20 20:54:50 2019 DistUpgraded: Fresh install DistroCodename: bionic DistroVariant: ubuntu DkmsStatus: amdgpu, 19.30-855429, 5.0.0-31-generic, x86_64: installed ExtraDebuggingInterest: No GraphicsCard: Intel Corporation Xeon E3-1200 v3/4th Gen Core Processor Integrated Graphics Controller [8086:0412] (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] Advanced Micro Devices, Inc. [AMD/ATI] Cape Verde XT [Radeon HD 7770/8760 / R7 250X] [1002:683d] (prog-if 00 [VGA controller]) Subsystem: Micro-Star International Co., Ltd. [MSI] R7770-PMD1GD5 [1462:2710] InstallationDate: Installed on 2019-10-19 (0 days ago) InstallationMedia: Ubuntu 18.04.3 LTS "Bionic Beaver" - Release amd64 (20190805) MachineType: Gigabyte Technology Co., Ltd. B85M-D2V ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.0.0-31-generic
[Touch-packages] [Bug 1823550] Re: GtkSourceView (gedit - Text Editor and others) wrongly has monospaced font in dropdown (context) menu
** Tags removed: cosmic eoan -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to ubuntu-themes in Ubuntu. https://bugs.launchpad.net/bugs/1823550 Title: GtkSourceView (gedit - Text Editor and others) wrongly has monospaced font in dropdown (context) menu Status in GtkSourceView: Fix Released Status in gtk+3.0 package in Ubuntu: Invalid Status in gtksourceview3 package in Ubuntu: Invalid Status in mate-themes package in Ubuntu: Invalid Status in pluma package in Ubuntu: Invalid Status in ubuntu-mate-artwork package in Ubuntu: Fix Released Status in ubuntu-themes package in Ubuntu: Confirmed Bug description: Steps to reproduce: 1. Have Ubuntu 17.04 or later installed 2. Open any application with GtkSourceView component - such as Pluma, Gedit, Giggle, Gitg, gnome-builder and maybe others (see complete list with `apt-cache rdepends libgtksourceview-3.0-1`) 3. Click right mouse button on text zone Expected result: * dropdown menu has normal font as all other interface elements Actual result: * dropdwon menu wrongly has monospaced font Notes: * first seen in 17.04, but persists in 17.10, 18.04 LTS, 18.10, 19.04 releases. * seems to be caused by GTK3 library ProblemType: Bug DistroRelease: Ubuntu 17.04 Package: pluma 1.18.1-0ubuntu1 ProcVersionSignature: Ubuntu 4.10.0-42.46-generic 4.10.17 Uname: Linux 4.10.0-42-generic x86_64 ApportVersion: 2.20.4-0ubuntu4.10 Architecture: amd64 CurrentDesktop: MATE Date: Sun Apr 7 20:13:24 2019 InstallationDate: Installed on 2018-08-07 (243 days ago) InstallationMedia: Ubuntu-MATE 16.04.3 LTS "Xenial Xerus" - Release amd64 (20170801) SourcePackage: pluma UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/gtksourceview/+bug/1823550/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1815318] Re: mate 18.04.1 xserver won't open caja on local machine
** Tags removed: 18.04 ** Tags added: eoan focal -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to openssh in Ubuntu. https://bugs.launchpad.net/bugs/1815318 Title: mate 18.04.1 xserver won't open caja on local machine Status in Ubuntu MATE: Invalid Status in caja package in Ubuntu: Incomplete Status in openssh package in Ubuntu: Invalid Bug description: Steps to reproduce: 1. Have installed Ubuntu MATE 18.04 LTS (you know its hostname and IP - i.e. 192.168.1.162) 2. Install SSH server on Ubuntu MATE 18.04 LTS 3. Open terminal on other remote system (client) and execute command to run Caja over X forwarding: ssh -X user@192.168.1.162 caja Expected results: * Caja is shown on remote (client) screen with window title *folder (on hostname)* Actual results: * Caja is not shown on remote (client) screen, but launches on server locally. Note: this works normally if server runs Ubuntu MATE 16.04 LTS, but fails with 18.04 LTS. --- Original description below: I can open a remote terminal using ssh -X 192.168.1.162. All other gui's that I've tested opened locally except the file manager Caja. When issuing caja in the remote terminal, I get nothing locally. Caja does open on the remote machine however, just not locally. The ssh -X 18.04.1 client still works connecting to a mate 16.04 server. I've tested this on numerous mate 18.04 clients, two 16.04 servers and two 18.04 servers, all mate. Something is wonky with caja on an 18.04.1 server. Please let me know if I can provide any more information. The only file manager I've tested that works is an X file manager, xfimage. X2go works and connects to servers, SSH Connect to Server works, why isn't the remote X terminal working using caja? To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-mate/+bug/1815318/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1721955] Re: Human, Human-Clearlooks and other themes have incorrect gray window title color
** Tags removed: cosmic ** Tags added: focal -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to gtk+2.0 in Ubuntu. https://bugs.launchpad.net/bugs/1721955 Title: Human, Human-Clearlooks and other themes have incorrect gray window title color Status in community-themes package in Ubuntu: New Status in compiz package in Ubuntu: Confirmed Status in gtk+2.0 package in Ubuntu: New Status in gtk+3.0 package in Ubuntu: New Status in human-theme package in Ubuntu: Confirmed Status in marco package in Ubuntu: Invalid Status in mate-themes package in Ubuntu: Invalid Bug description: Steps to reproduce: 1. Install Ubuntu 17.10 MATE or 18.04 LTS MATE 2. Install Human theme from `human-theme` package 3. Select Human theme from `mate-control-center` Appearance Expected results: window title color is set to Ubuntu's orange (#FFBE6B) Actual results: window title color is set to different gray/silver color (#a5a5a2) Note: other themes are affected too. ProblemType: Bug DistroRelease: Ubuntu 17.10 Package: human-theme 0.39.2 ProcVersionSignature: Ubuntu 4.13.0-12.13-generic 4.13.3 Uname: Linux 4.13.0-12-generic i686 ApportVersion: 2.20.7-0ubuntu2 Architecture: i386 CurrentDesktop: MATE Date: Sat Oct 7 15:43:03 2017 InstallationDate: Installed on 2017-10-07 (0 days ago) InstallationMedia: Ubuntu-MATE 17.10 "Artful Aardvark" - Alpha i386 (20170925.1) PackageArchitecture: all SourcePackage: human-theme UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/community-themes/+bug/1721955/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1787368] Re: Caja does not show previews of text files on Bionic and newer versions
** Tags removed: cosmic ** Tags added: focal -- 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/1787368 Title: Caja does not show previews of text files on Bionic and newer versions Status in MATE Desktop: New Status in caja package in Ubuntu: Confirmed Status in gtk+3.0 package in Ubuntu: New Bug description: Steps to reproduce: 1. Install Ubuntu MATE 18.04 LTS (or upgrade from 16.04 LTS) 2. Create text file somewhere (in home folder for example) with `echo text > ~/file.txt`. 3. Open Caja in home folder Expected results: * Caja shows preview (the contents) of `file.txt` in Icon view. Actual results: * Caja does not show preview of `file.txt`. Notes: 1. all settings in Preview tab are set to *Local Only* 2. this happens on clean user profile and/or after `dconf reset -f /` and `gsettings reset-recursively org.mate.caja` 3. Problem first seen on AskUbuntu ( https://askubuntu.com/q/1065825/66509 ). ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: caja 1.20.2-4ubuntu1 ProcVersionSignature: Ubuntu 4.15.0-30.32-generic 4.15.18 Uname: Linux 4.15.0-30-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.2 Architecture: amd64 CurrentDesktop: MATE Date: Thu Aug 16 12:36:57 2018 InstallationDate: Installed on 2018-04-26 (111 days ago) InstallationMedia: Ubuntu-MATE 18.04 LTS "Bionic Beaver" - Release amd64 (20180426) SourcePackage: caja UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/mate-desktop/+bug/1787368/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1847570] Re: PulseAudio automatically switches to HDMI sound output on login
In case it's helpful, I posted a bug about this (but, perhaps, incorrectly as an ALSA problem) with my Alsa and PulseAudio information: https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1846290 Above, it was mentioned that perhaps this is regards to module-switch- on-connect. FWIW, when I was testing Fedora 31, it correctly picked my onboard sound controller rather than my HDMI monitors (which have an audio passthrough but no onboard audio capabilities/speakers of their own) from the start and never tried to switch the output device to HDMI. I have further noticed that when I try to launch games via Steam, they have no sound, even if I make sure line out is the selected sound output device in gnome-settings prior to launching Steam. I did not have this problem on 19.04, so I wonder if it's related? Any tips on how I can further investigate and maybe file a separate bug report if necessary? -- 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/1847570 Title: PulseAudio automatically switches to HDMI sound output on login Status in PulseAudio: New Status in pulseaudio package in Ubuntu: Triaged Status in pulseaudio source package in Eoan: Triaged Bug description: On my freshly installed eoan system I have two output devices: - HDMI/DisplayPort 2 - GK208 ... - Line Out - Family 17h ... When I login into the system pulseaudio always select the "wrong" one (HDMI) and I need to go to gnome-settings/Sound/Output Device and switch to "line out". This applies to every login/logout not just reboots. I would be good if it would remember this choice so that I have to do it only once. Or maybe (if that is technically possible) just output on both output devices by default - this would be even more user friendly for newbies who will have a hard time finding the right place to change this (or maybe have UI in the volume slider to select outputs if there are more than one? But anyway, my immediate concern is that it should just remember my choice :) Please let me know if I can provide more information. Happy to dig into code if needed but I will need some pointers. To manage notifications about this bug go to: https://bugs.launchpad.net/pulseaudio/+bug/1847570/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1773859] Re: upgrades to 18.04 fail
This is still broken as of today. Tried to upgrade a fully up-to-date 1604 LTS system to 1804 LTS using "do-release-upgrade" and it failed with this exact issue. Had to use the steps from comment #3 above to get it working... mv /usr/share/dbus-1/system-services/org.freedesktop.systemd1.service /usr/share/dbus-1/system-services/org.freedesktop.systemd1.service.bak apt-get -f install apt-get dist-upgrade -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to systemd-shim in Ubuntu. https://bugs.launchpad.net/bugs/1773859 Title: upgrades to 18.04 fail Status in systemd package in Ubuntu: Fix Released Status in systemd-shim package in Ubuntu: Won't Fix Status in systemd source package in Bionic: Fix Released Status in systemd-shim source package in Bionic: Won't Fix Status in systemd source package in Cosmic: Fix Released Status in systemd-shim source package in Cosmic: Won't Fix Bug description: [Impact] * Some systems fail to upgrade due to conflicts between systemd and the (now removed from the archive) systemd-shim / upstart. * Instead of trying to work out what's the problem in ordering / removal of diverts, ensure that systemd is never unpacked whilst systemd-shim/upstart are still on disk. Thus declare conflicts against systemd-shim/upstart packages in systemd package. [Test Case] * monitor drop-off of upgrades with below reported problem * Check that it is possible to upgrade to bionic's libpam-systemd from xenial with systemd-shim installed on xenial, ie. lxc launch ubuntu-daily:xenial test-shim-upgrade lxc exec test-shim-upgrade apt update apt install systemd-shim wget https://deb.debian.org/debian/pool/main/s/systemd-shim/systemd-shim_10-3_amd64.deb apt install ./systemd-shim_10-3_amd64.deb sed 's/xenial/bionic/' -i /etc/apt/sources.list apt update apt install systemd this currently passes, however, systemd-shim remains installed. It should be removed instead. Apt install systemd should have lines like this: The following packages will be REMOVED: systemd-shim ... Removing 'diversion of /usr/share/dbus-1/system-services/org.freedesktop.systemd1.service to /usr/share/dbus-1/system-services/org.freedesktop.systemd1.service.systemd by systemd-shim' ... [Regression Potential] * systemd-shim/upstart are both removed and not supported in bionic, thus forcing their removal via conflicts should bring the system into an expected state. [Other Info] * original bug report $ sudo apt upgrade Reading package lists... Done Building dependency tree Reading state information... Done Calculating upgrade... Done The following packages will be REMOVED: systemd-shim 0 upgraded, 0 newly installed, 1 to remove and 0 not upgraded. 1 not fully installed or removed. After this operation, 71.7 kB disk space will be freed. Do you want to continue? [Y/n] y (Reading database ... 63 files and directories currently installed.) Removing systemd-shim (9-1bzr4ubuntu1) ... Removing 'diversion of /usr/share/dbus-1/system-services/org.freedesktop.systemd1.service to /usr/share/dbus-1/system-services/org.freedesktop.systemd1.service.systemd by systemd-shim' dpkg-divert: error: rename involves overwriting '/usr/share/dbus-1/system-services/org.freedesktop.systemd1.service' with different file '/usr/share/dbus-1/system-services/org.freedesktop.systemd1.service.systemd', not allowed dpkg: error processing package systemd-shim (--remove): subprocess installed post-removal script returned error exit status 2 Errors were encountered while processing: systemd-shim E: Sub-process /usr/bin/dpkg returned an error code (1) Commenting out the dpkg-divert in systemd-shim's postrm solved this for me and I was about to continue the upgrade. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1773859/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1486445] Re: Lots of zeitgeist errors
It would be easier to delete comment #10 but I can't. `zeitgeist` wasn't resetting screen brightness and gamma. It was simply logging error it didn't know about application I was running to reset brightness and gamma based on time of day. I posted a solution to getting rid of zeitgeist error messages for `~/Desktop/*.desktop` applications which zeitgeist understandably knows nothing about: - https://askubuntu.com/a/1182396/307523 In summary, open Gnome Activity Log Manager / Unity Security and Privacy. Add the directory `~/Desktop` to the blacklist. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to zeitgeist in Ubuntu. https://bugs.launchpad.net/bugs/1486445 Title: Lots of zeitgeist errors Status in Zeitgeist Datahub: Confirmed Status in zeitgeist package in Ubuntu: Confirmed Bug description: $ cat /var/log/syslog shows me lots of zeitgeist-related errors. My system is behaving weird lately since the upgrade from Ubuntu 14.10 to 15.04 so I am guessing this might be related. Alright, here the relevant log entries: Aug 19 19:31:49 M1 org.gnome.zeitgeist.Engine[25838]: ** (zeitgeist-datahub:26262): WARNING **: zeitgeist-datahub.vala:212: Error during inserting events: GDBus.Error:org.gnome.zeitgeist.EngineError.InvalidArgument: Incomplete event: interpretation, manifestation and actor are required ... Aug 19 20:25:14 M1 org.gnome.zeitgeist.Engine[25838]: ** (zeitgeist-datahub:26262): WARNING **: recent-manager-provider.vala:132: Desktop file for "file:///home/michael-heuberger/.config/sublime-text-3/Projects/seeflow_live.sublime-project" was not found, exec: sublime_text, mime_type: application/octet-stream Aug 19 20:25:14 M1 org.gnome.zeitgeist.Engine[25838]: ** (zeitgeist-datahub:26262): WARNING **: recent-manager-provider.vala:132: Desktop file for "file:///home/michael-heuberger/binarykitchen/code/videomail.io/etc/ssl-certs/local/fake.crt" was not found, exec: google-chrome-stable, mime_type: application/pkix-cert Aug 19 20:25:14 M1 org.gnome.zeitgeist.Engine[25838]: ** (zeitgeist-datahub:26262): WARNING **: recent-manager-provider.vala:132: Desktop file for "file:///home/michael-heuberger/binarykitchen/code/webcamjs/demos/flash.html" was not found, exec: google-chrome-stable, mime_type: application/x-extension-html ... Aug 19 20:34:30 M1 org.gnome.zeitgeist.SimpleIndexer[25838]: ** (zeitgeist-fts:26260): WARNING **: Unable to get info on application://gnome-terminal-server.desktop Aug 19 20:37:47 M1 org.gnome.zeitgeist.SimpleIndexer[25838]: message repeated 2 times: [ ** (zeitgeist-fts:26260): WARNING **: Unable to get info on application://gnome-terminal-server.desktop] ... Aug 19 20:38:52 M1 org.gnome.zeitgeist.SimpleIndexer[25838]: ** (zeitgeist-fts:26260): WARNING **: Unable to get info on application://gnome-terminal-server.desktop Any clues how to fix all that? To manage notifications about this bug go to: https://bugs.launchpad.net/zeitgeist-datahub/+bug/1486445/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1846148] Re: Realtek ALC256M with DTS Audio Processing internal microphone doesn't work on Redmi Book 14 2019
The testing kernel in the #12 is for fixing the internal mic, so no need to test external mic plugging (#13). For #14, it is internal mic, could you record sound with internal mic? -- 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/1846148 Title: Realtek ALC256M with DTS Audio Processing internal microphone doesn't work on Redmi Book 14 2019 Status in alsa-driver package in Ubuntu: Confirmed Bug description: Sound works okay but the internal mic doesn't work. When I plug in headset, the mic on headset also doens't work. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: alsa-base 1.0.25+dfsg-0ubuntu5 ProcVersionSignature: Ubuntu 5.0.0-29.31~18.04.1-generic 5.0.21 Uname: Linux 5.0.0-29-generic x86_64 NonfreeKernelModules: wl ApportVersion: 2.20.9-0ubuntu7.7 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: lilian 1689 F pulseaudio CurrentDesktop: ubuntu:GNOME Date: Tue Oct 1 12:27:10 2019 InstallationDate: Installed on 2019-09-21 (9 days ago) InstallationMedia: Ubuntu 18.04.3 LTS "Bionic Beaver" - Release amd64 (20190805) PackageArchitecture: all SourcePackage: alsa-driver Symptom: audio Title: PCI/internal sound card not detected UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 08/19/2019 dmi.bios.vendor: TIMI dmi.bios.version: RMRCM400P0100 dmi.board.name: TM1901 dmi.board.vendor: TIMI dmi.chassis.type: 10 dmi.chassis.vendor: TIMI dmi.modalias: dmi:bvnTIMI:bvrRMRCM400P0100:bd08/19/2019:svnTIMI:pnRedmiBook14:pvr:rvnTIMI:rnTM1901:rvr:cvnTIMI:ct10:cvr: dmi.product.family: Mi Laptop dmi.product.name: RedmiBook 14 dmi.product.sku: TM1901-24822 dmi.sys.vendor: TIMI To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1846148/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1486445] Re: Lots of zeitgeist errors
Received error on Ubuntu 16.04.6 LTS this morning. I've never noticed it impacting me before but this time it reset my night time screen settings to full daylight setting. Results of `journalctl -xe | grep eyesome`: Oct 19 21:40:55 alien eyesome[25582]: Wakeup: Creating /tmp/eyesome-is-suspending Oct 20 05:21:17 alien eyesome[25788]: Wakeup: Called from suspend. Oct 20 05:21:28 alien eyesome[26826]: Daemon: Resuming: Slept 2 seconds x 5 times. Oct 20 05:21:28 alien eyesome[26829]: Daemon: Removed file: /tmp/eyesome-is-suspending Oct 20 05:29:52 alien eyesome[10076]: Sun Times: https://www.timeanddate.com/sun/canada/edmonton. Oct 20 05:30:06 alien org.gnome.zeitgeist.SimpleIndexer[2098]: ** (zeitgeist-fts:4341): WARNING **: Unable to get info on application://eyesome-cfg.desktop Oct 20 05:30:13 alien sudo[11668]: rick : TTY=unknown ; PWD=/home/rick ; USER=root ; COMMAND=/usr/local/bin/eyesome-cfg.sh Oct 20 05:30:19 alien eyesome[12296]: Wakeup: Called from eyesome-cfg.sh. Last night: 21:40:55 system suspends normally. This morning: 05:21:17 system resumes normally. 05:29:52 cron.daily gets sunrise and sunset times from internet. 05:30:06 zeitgeist.SimpleIndexer error sets screen brightness & gamma to full. 05:30:13 I have to open ~/Desktop/eyesome-cfg.desktop with sudo. 05:30:19 I have to trigger eyesome wakeup to set screens based on time. Possible Resolutions: - All kinds of links on web and in Ask Ubuntu on removing zeitgeist. - I have no need for speed improvements gained by removing. - Suggestions that removing will break nautilus and gedit is a deal breaker. - I would rather find out how to configure zeitgeist to play nicely with my data. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to zeitgeist in Ubuntu. https://bugs.launchpad.net/bugs/1486445 Title: Lots of zeitgeist errors Status in Zeitgeist Datahub: Confirmed Status in zeitgeist package in Ubuntu: Confirmed Bug description: $ cat /var/log/syslog shows me lots of zeitgeist-related errors. My system is behaving weird lately since the upgrade from Ubuntu 14.10 to 15.04 so I am guessing this might be related. Alright, here the relevant log entries: Aug 19 19:31:49 M1 org.gnome.zeitgeist.Engine[25838]: ** (zeitgeist-datahub:26262): WARNING **: zeitgeist-datahub.vala:212: Error during inserting events: GDBus.Error:org.gnome.zeitgeist.EngineError.InvalidArgument: Incomplete event: interpretation, manifestation and actor are required ... Aug 19 20:25:14 M1 org.gnome.zeitgeist.Engine[25838]: ** (zeitgeist-datahub:26262): WARNING **: recent-manager-provider.vala:132: Desktop file for "file:///home/michael-heuberger/.config/sublime-text-3/Projects/seeflow_live.sublime-project" was not found, exec: sublime_text, mime_type: application/octet-stream Aug 19 20:25:14 M1 org.gnome.zeitgeist.Engine[25838]: ** (zeitgeist-datahub:26262): WARNING **: recent-manager-provider.vala:132: Desktop file for "file:///home/michael-heuberger/binarykitchen/code/videomail.io/etc/ssl-certs/local/fake.crt" was not found, exec: google-chrome-stable, mime_type: application/pkix-cert Aug 19 20:25:14 M1 org.gnome.zeitgeist.Engine[25838]: ** (zeitgeist-datahub:26262): WARNING **: recent-manager-provider.vala:132: Desktop file for "file:///home/michael-heuberger/binarykitchen/code/webcamjs/demos/flash.html" was not found, exec: google-chrome-stable, mime_type: application/x-extension-html ... Aug 19 20:34:30 M1 org.gnome.zeitgeist.SimpleIndexer[25838]: ** (zeitgeist-fts:26260): WARNING **: Unable to get info on application://gnome-terminal-server.desktop Aug 19 20:37:47 M1 org.gnome.zeitgeist.SimpleIndexer[25838]: message repeated 2 times: [ ** (zeitgeist-fts:26260): WARNING **: Unable to get info on application://gnome-terminal-server.desktop] ... Aug 19 20:38:52 M1 org.gnome.zeitgeist.SimpleIndexer[25838]: ** (zeitgeist-fts:26260): WARNING **: Unable to get info on application://gnome-terminal-server.desktop Any clues how to fix all that? To manage notifications about this bug go to: https://bugs.launchpad.net/zeitgeist-datahub/+bug/1486445/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1620635] Re: libapparmor's aa_query_label() always returns allowed = 0 for file rules containing the "owner" conditional
Seems as if label lookup is done using dbus: https://github.com/ubports /content-hub/blob/xenial/src/com/ubuntu/content/utils.cpp#L254 -- 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/1620635 Title: libapparmor's aa_query_label() always returns allowed = 0 for file rules containing the "owner" conditional Status in AppArmor: Triaged Status in Snappy: Won't Fix Status in apparmor package in Ubuntu: Triaged Bug description: Steps to reproduce: 1. Download and compile the following sample C app that calls aa_query_label wget https://launchpadlibrarian.net/207629699/query_file.c gcc -o query_file query_file.c -l apparmor 2. Install a snap that uses the home interface, for example demo-wget: snap install demo-wget 3. Create a file in your home: touch /home/USERNAME/testfile 4. Ask apparmor if demo-wget can read that file with query_file: ./query_file snap.demo-wget.wget /home/USERNAME/testfile Expected result: output of ./query_file command is read '/home/kaleo/toto' allowed Current result: output of ./query_file command is read '/home/kaleo/toto' denied To manage notifications about this bug go to: https://bugs.launchpad.net/apparmor/+bug/1620635/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1620635] Re: libapparmor's aa_query_label() always returns allowed = 0 for file rules containing the "owner" conditional
AppArmor userspace in use: AppArmor parser version 2.10.95 -- 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/1620635 Title: libapparmor's aa_query_label() always returns allowed = 0 for file rules containing the "owner" conditional Status in AppArmor: Triaged Status in Snappy: Won't Fix Status in apparmor package in Ubuntu: Triaged Bug description: Steps to reproduce: 1. Download and compile the following sample C app that calls aa_query_label wget https://launchpadlibrarian.net/207629699/query_file.c gcc -o query_file query_file.c -l apparmor 2. Install a snap that uses the home interface, for example demo-wget: snap install demo-wget 3. Create a file in your home: touch /home/USERNAME/testfile 4. Ask apparmor if demo-wget can read that file with query_file: ./query_file snap.demo-wget.wget /home/USERNAME/testfile Expected result: output of ./query_file command is read '/home/kaleo/toto' allowed Current result: output of ./query_file command is read '/home/kaleo/toto' denied To manage notifications about this bug go to: https://bugs.launchpad.net/apparmor/+bug/1620635/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1620635] Re: libapparmor's aa_query_label() always returns allowed = 0 for file rules containing the "owner" conditional
Nothing special from what I could gather, just: -) Calling an internal utility function for getting the allow status: https://github.com/ubports/content-hub/blob/xenial/src/com/ubuntu/content/detail/transfer.cpp#L187 -) Which eventually lands here: https://github.com/ubports/content-hub/blob/xenial/src/com/ubuntu/content/utils.cpp#L354 No special pid lookups or anything. -- 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/1620635 Title: libapparmor's aa_query_label() always returns allowed = 0 for file rules containing the "owner" conditional Status in AppArmor: Triaged Status in Snappy: Won't Fix Status in apparmor package in Ubuntu: Triaged Bug description: Steps to reproduce: 1. Download and compile the following sample C app that calls aa_query_label wget https://launchpadlibrarian.net/207629699/query_file.c gcc -o query_file query_file.c -l apparmor 2. Install a snap that uses the home interface, for example demo-wget: snap install demo-wget 3. Create a file in your home: touch /home/USERNAME/testfile 4. Ask apparmor if demo-wget can read that file with query_file: ./query_file snap.demo-wget.wget /home/USERNAME/testfile Expected result: output of ./query_file command is read '/home/kaleo/toto' allowed Current result: output of ./query_file command is read '/home/kaleo/toto' denied To manage notifications about this bug go to: https://bugs.launchpad.net/apparmor/+bug/1620635/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1620635] Re: libapparmor's aa_query_label() always returns allowed = 0 for file rules containing the "owner" conditional
Alfred, which version of apparmor userspace is Ubuntu touch using? You can use apparmor_parser -V to find out -- 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/1620635 Title: libapparmor's aa_query_label() always returns allowed = 0 for file rules containing the "owner" conditional Status in AppArmor: Triaged Status in Snappy: Won't Fix Status in apparmor package in Ubuntu: Triaged Bug description: Steps to reproduce: 1. Download and compile the following sample C app that calls aa_query_label wget https://launchpadlibrarian.net/207629699/query_file.c gcc -o query_file query_file.c -l apparmor 2. Install a snap that uses the home interface, for example demo-wget: snap install demo-wget 3. Create a file in your home: touch /home/USERNAME/testfile 4. Ask apparmor if demo-wget can read that file with query_file: ./query_file snap.demo-wget.wget /home/USERNAME/testfile Expected result: output of ./query_file command is read '/home/kaleo/toto' allowed Current result: output of ./query_file command is read '/home/kaleo/toto' denied To manage notifications about this bug go to: https://bugs.launchpad.net/apparmor/+bug/1620635/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1818616] Re: gnome-keyring is not unlocked upon gdm login in disco
*** This bug is a duplicate of bug 1817128 *** https://bugs.launchpad.net/bugs/1817128 Filed report as well on Gnome: https://gitlab.gnome.org/GNOME/gnome-keyring/issues/28 Relevant components: * gdm3 3.34.1-1 * gnome-shell 3.34.1-1 * gnome-keyring 3.34.0-1 So, no lightdm, unlike this similar issue: https://github.com/canonical/lightdm/issues/70 they also suggested that the dconf may have become corrupted. I've tried as well: ``` mv .config/dconf/user ~/.config/dconf/user.bak ``` But didn't work. ** Bug watch added: gitlab.gnome.org/GNOME/gnome-keyring/issues #28 https://gitlab.gnome.org/GNOME/gnome-keyring/issues/28 ** Bug watch added: github.com/canonical/lightdm/issues #70 https://github.com/canonical/lightdm/issues/70 -- 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/1818616 Title: gnome-keyring is not unlocked upon gdm login in disco Status in gdm3 package in Ubuntu: Confirmed Status in gnome-keyring package in Ubuntu: Confirmed Status in pam package in Ubuntu: Confirmed Status in systemd package in Ubuntu: Confirmed Bug description: I'm not sure if this is a regression in my gnome-keyring, gdm3, or pam, or local configuration. As far as I recall, I should be running just "stock" configs. I did not install system with disco, but upgraded to disco throughout development series. Upon booting, and logging in through gdm3, I get a pop-up from gnome- keyring instructing me that gnome-keyring was not unlocked upon logging, and I have to re-enter the password again. The password for the account and the gnome-keyring are the same, and the keyring should be auto-unlocked. Looking at the journal, there is a red warning from gdm: Mar 05 08:15:58 ottawa gdm-password][18338]: gkr-pam: unable to locate daemon control file Looking at the code, this happens when neither GNOME_KEYRING_CONTROL nor XDG_RUNTIME_DIR are set. The messages after it are: Mar 05 08:15:58 ottawa gdm-password][18338]: gkr-pam: unable to locate daemon control file Mar 05 08:15:58 ottawa gdm-password][18338]: pam_unix(gdm-password:session): session opened for user xnox by (uid=0) Mar 05 08:15:58 ottawa systemd[1]: Created slice User Slice of UID 1000. Mar 05 08:15:58 ottawa systemd[1]: Starting User Runtime Directory /run/user/1000... Mar 05 08:15:58 ottawa systemd-logind[1376]: New session 3 of user xnox. Mar 05 08:15:58 ottawa systemd[1]: Started User Runtime Directory /run/user/1000. Mar 05 08:15:58 ottawa systemd[1]: Starting User Manager for UID 1000... Mar 05 08:15:58 ottawa systemd[18344]: pam_unix(systemd-user:session): session opened for user xnox by (uid=0) Mar 05 08:15:58 ottawa systemd[18344]: Listening on Sound System. Mar 05 08:15:58 ottawa systemd[18344]: Listening on GnuPG cryptographic agent (ssh-agent emulation). Mar 05 08:15:58 ottawa systemd[18344]: Started Pending report trigger for Ubuntu Report. Mar 05 08:15:58 ottawa systemd[18344]: Listening on GnuPG cryptographic agent and passphrase cache (restricted). Mar 05 08:15:58 ottawa systemd[18344]: Listening on GnuPG cryptographic agent and passphrase cache. Mar 05 08:15:58 ottawa systemd[18344]: Reached target Paths. Mar 05 08:15:58 ottawa systemd[18344]: Listening on GnuPG cryptographic agent and passphrase cache (access for web browsers). Mar 05 08:15:58 ottawa systemd[18344]: Reached target Timers. Mar 05 08:15:58 ottawa systemd[18344]: Listening on GnuPG network certificate management daemon. Mar 05 08:15:58 ottawa systemd[18344]: Starting D-Bus User Message Bus Socket. Mar 05 08:15:58 ottawa systemd[18344]: Listening on D-Bus User Message Bus Socket. Mar 05 08:15:58 ottawa systemd[18344]: Reached target Sockets. Mar 05 08:15:58 ottawa systemd[18344]: Reached target Basic System. Mar 05 08:15:58 ottawa systemd[1]: Started User Manager for UID 1000. Mar 05 08:15:58 ottawa systemd[18344]: Started Emacs text editor. Mar 05 08:15:58 ottawa systemd[18344]: Reached target Default. Mar 05 08:15:58 ottawa systemd[18344]: Startup finished in 72ms. Mar 05 08:15:58 ottawa systemd[1]: Started Session 3 of user xnox. I don't believe GNOME_KEYRING_CONTROL used to be set, however I do see that XDG_RUNTIME_DIR to be created and set by logind. From the above logs I can see that it happens _after_ gdm-password is done. So It seems like something has changed in the stack, and gdm login / libpam-gnome-keyring no longer use systemd-logind PAM module to be part of the PAM session. But I'm not sure what has changed to cause this (gdm, gnome-keyring, pam, systemd). Am I the only one with this issue? ProblemType: Bug DistroRelease: Ubuntu 19.04 Package: gnome-keyring 3.31.90-1ubuntu1 ProcVersionSignature: Ubuntu 4.19.0-13.14-generic 4.19.20 Uname: Linux 4.19.0-13-generic x86_64 NonfreeKernelModules: zfs
[Touch-packages] [Bug 1620635] Re: libapparmor's aa_query_label() always returns allowed = 0 for file rules containing the "owner" conditional
How is content hub looking up the confinement (label) of the task. Are you using pids, looking through /proc//, using aa_gettaskcon? This will help with creating an interface wrapper for query_label so we can pass the needed information to the kernel. -- 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/1620635 Title: libapparmor's aa_query_label() always returns allowed = 0 for file rules containing the "owner" conditional Status in AppArmor: Triaged Status in Snappy: Won't Fix Status in apparmor package in Ubuntu: Triaged Bug description: Steps to reproduce: 1. Download and compile the following sample C app that calls aa_query_label wget https://launchpadlibrarian.net/207629699/query_file.c gcc -o query_file query_file.c -l apparmor 2. Install a snap that uses the home interface, for example demo-wget: snap install demo-wget 3. Create a file in your home: touch /home/USERNAME/testfile 4. Ask apparmor if demo-wget can read that file with query_file: ./query_file snap.demo-wget.wget /home/USERNAME/testfile Expected result: output of ./query_file command is read '/home/kaleo/toto' allowed Current result: output of ./query_file command is read '/home/kaleo/toto' denied To manage notifications about this bug go to: https://bugs.launchpad.net/apparmor/+bug/1620635/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1848731] Re: Audio output device changes upon unlock/login
** Also affects: pulseaudio (Ubuntu) Importance: Undecided Status: New -- 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/1848731 Title: Audio output device changes upon unlock/login Status in linux package in Ubuntu: Incomplete Status in pulseaudio package in Ubuntu: New Bug description: I have a ThinkPad X250 and updated To Ubuntu 19.10 today from 19.04. Locking/Suspending and logging in changes my audio output device. This did not happen in 19.04. How to reproduce When I lock my session with key combination "Win+L" and then unlock it again, the sound that's been playing through my headphones/speakers stops playing. When I check the audio settings, "HDMI/DisplayPort 2 - Built-in audio" is selected. When I select "Headphones - Built-in audio", sound continues playing. There is no related log output in dmesg. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1848731/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1620635] Re: libapparmor's aa_query_label() always returns allowed = 0 for file rules containing the "owner" conditional
We're hitting this bug in UBports Ubuntu Touch on the Sony Xperia X (4.4 kernel, xenial AppArmor) as in #6 and #12, apps using content-hub to request files from a confined application fail receiving the file due to aa_query_label returning a denial before trying transfering a file. -- 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/1620635 Title: libapparmor's aa_query_label() always returns allowed = 0 for file rules containing the "owner" conditional Status in AppArmor: Triaged Status in Snappy: Won't Fix Status in apparmor package in Ubuntu: Triaged Bug description: Steps to reproduce: 1. Download and compile the following sample C app that calls aa_query_label wget https://launchpadlibrarian.net/207629699/query_file.c gcc -o query_file query_file.c -l apparmor 2. Install a snap that uses the home interface, for example demo-wget: snap install demo-wget 3. Create a file in your home: touch /home/USERNAME/testfile 4. Ask apparmor if demo-wget can read that file with query_file: ./query_file snap.demo-wget.wget /home/USERNAME/testfile Expected result: output of ./query_file command is read '/home/kaleo/toto' allowed Current result: output of ./query_file command is read '/home/kaleo/toto' denied To manage notifications about this bug go to: https://bugs.launchpad.net/apparmor/+bug/1620635/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1846148] Re: Realtek ALC256M with DTS Audio Processing internal microphone doesn't work on Redmi Book 14 2019
also dmesg ** Attachment added: "dmesg.txt" https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1846148/+attachment/5298555/+files/dmesg.txt -- 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/1846148 Title: Realtek ALC256M with DTS Audio Processing internal microphone doesn't work on Redmi Book 14 2019 Status in alsa-driver package in Ubuntu: Confirmed Bug description: Sound works okay but the internal mic doesn't work. When I plug in headset, the mic on headset also doens't work. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: alsa-base 1.0.25+dfsg-0ubuntu5 ProcVersionSignature: Ubuntu 5.0.0-29.31~18.04.1-generic 5.0.21 Uname: Linux 5.0.0-29-generic x86_64 NonfreeKernelModules: wl ApportVersion: 2.20.9-0ubuntu7.7 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: lilian 1689 F pulseaudio CurrentDesktop: ubuntu:GNOME Date: Tue Oct 1 12:27:10 2019 InstallationDate: Installed on 2019-09-21 (9 days ago) InstallationMedia: Ubuntu 18.04.3 LTS "Bionic Beaver" - Release amd64 (20190805) PackageArchitecture: all SourcePackage: alsa-driver Symptom: audio Title: PCI/internal sound card not detected UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 08/19/2019 dmi.bios.vendor: TIMI dmi.bios.version: RMRCM400P0100 dmi.board.name: TM1901 dmi.board.vendor: TIMI dmi.chassis.type: 10 dmi.chassis.vendor: TIMI dmi.modalias: dmi:bvnTIMI:bvrRMRCM400P0100:bd08/19/2019:svnTIMI:pnRedmiBook14:pvr:rvnTIMI:rnTM1901:rvr:cvnTIMI:ct10:cvr: dmi.product.family: Mi Laptop dmi.product.name: RedmiBook 14 dmi.product.sku: TM1901-24822 dmi.sys.vendor: TIMI To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1846148/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1846148] Re: Realtek ALC256M with DTS Audio Processing internal microphone doesn't work on Redmi Book 14 2019
** Attachment added: "alsa-info.txt.10.20" https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1846148/+attachment/5298554/+files/alsa-info.txt.10.20 -- 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/1846148 Title: Realtek ALC256M with DTS Audio Processing internal microphone doesn't work on Redmi Book 14 2019 Status in alsa-driver package in Ubuntu: Confirmed Bug description: Sound works okay but the internal mic doesn't work. When I plug in headset, the mic on headset also doens't work. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: alsa-base 1.0.25+dfsg-0ubuntu5 ProcVersionSignature: Ubuntu 5.0.0-29.31~18.04.1-generic 5.0.21 Uname: Linux 5.0.0-29-generic x86_64 NonfreeKernelModules: wl ApportVersion: 2.20.9-0ubuntu7.7 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: lilian 1689 F pulseaudio CurrentDesktop: ubuntu:GNOME Date: Tue Oct 1 12:27:10 2019 InstallationDate: Installed on 2019-09-21 (9 days ago) InstallationMedia: Ubuntu 18.04.3 LTS "Bionic Beaver" - Release amd64 (20190805) PackageArchitecture: all SourcePackage: alsa-driver Symptom: audio Title: PCI/internal sound card not detected UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 08/19/2019 dmi.bios.vendor: TIMI dmi.bios.version: RMRCM400P0100 dmi.board.name: TM1901 dmi.board.vendor: TIMI dmi.chassis.type: 10 dmi.chassis.vendor: TIMI dmi.modalias: dmi:bvnTIMI:bvrRMRCM400P0100:bd08/19/2019:svnTIMI:pnRedmiBook14:pvr:rvnTIMI:rnTM1901:rvr:cvnTIMI:ct10:cvr: dmi.product.family: Mi Laptop dmi.product.name: RedmiBook 14 dmi.product.sku: TM1901-24822 dmi.sys.vendor: TIMI To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1846148/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1846148] Re: Realtek ALC256M with DTS Audio Processing internal microphone doesn't work on Redmi Book 14 2019
** Attachment added: "Screenshot from 2019-10-20 18-17-27.png" https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1846148/+attachment/5298553/+files/Screenshot%20from%202019-10-20%2018-17-27.png -- 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/1846148 Title: Realtek ALC256M with DTS Audio Processing internal microphone doesn't work on Redmi Book 14 2019 Status in alsa-driver package in Ubuntu: Confirmed Bug description: Sound works okay but the internal mic doesn't work. When I plug in headset, the mic on headset also doens't work. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: alsa-base 1.0.25+dfsg-0ubuntu5 ProcVersionSignature: Ubuntu 5.0.0-29.31~18.04.1-generic 5.0.21 Uname: Linux 5.0.0-29-generic x86_64 NonfreeKernelModules: wl ApportVersion: 2.20.9-0ubuntu7.7 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: lilian 1689 F pulseaudio CurrentDesktop: ubuntu:GNOME Date: Tue Oct 1 12:27:10 2019 InstallationDate: Installed on 2019-09-21 (9 days ago) InstallationMedia: Ubuntu 18.04.3 LTS "Bionic Beaver" - Release amd64 (20190805) PackageArchitecture: all SourcePackage: alsa-driver Symptom: audio Title: PCI/internal sound card not detected UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 08/19/2019 dmi.bios.vendor: TIMI dmi.bios.version: RMRCM400P0100 dmi.board.name: TM1901 dmi.board.vendor: TIMI dmi.chassis.type: 10 dmi.chassis.vendor: TIMI dmi.modalias: dmi:bvnTIMI:bvrRMRCM400P0100:bd08/19/2019:svnTIMI:pnRedmiBook14:pvr:rvnTIMI:rnTM1901:rvr:cvnTIMI:ct10:cvr: dmi.product.family: Mi Laptop dmi.product.name: RedmiBook 14 dmi.product.sku: TM1901-24822 dmi.sys.vendor: TIMI To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1846148/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1846148] Re: Realtek ALC256M with DTS Audio Processing internal microphone doesn't work on Redmi Book 14 2019
The behavior is different with the test kernel. please find the screenshot and the alsa-info below. ** Attachment added: "Screenshot from 2019-10-20 18-18-34.png" https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1846148/+attachment/5298552/+files/Screenshot%20from%202019-10-20%2018-18-34.png -- 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/1846148 Title: Realtek ALC256M with DTS Audio Processing internal microphone doesn't work on Redmi Book 14 2019 Status in alsa-driver package in Ubuntu: Confirmed Bug description: Sound works okay but the internal mic doesn't work. When I plug in headset, the mic on headset also doens't work. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: alsa-base 1.0.25+dfsg-0ubuntu5 ProcVersionSignature: Ubuntu 5.0.0-29.31~18.04.1-generic 5.0.21 Uname: Linux 5.0.0-29-generic x86_64 NonfreeKernelModules: wl ApportVersion: 2.20.9-0ubuntu7.7 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: lilian 1689 F pulseaudio CurrentDesktop: ubuntu:GNOME Date: Tue Oct 1 12:27:10 2019 InstallationDate: Installed on 2019-09-21 (9 days ago) InstallationMedia: Ubuntu 18.04.3 LTS "Bionic Beaver" - Release amd64 (20190805) PackageArchitecture: all SourcePackage: alsa-driver Symptom: audio Title: PCI/internal sound card not detected UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 08/19/2019 dmi.bios.vendor: TIMI dmi.bios.version: RMRCM400P0100 dmi.board.name: TM1901 dmi.board.vendor: TIMI dmi.chassis.type: 10 dmi.chassis.vendor: TIMI dmi.modalias: dmi:bvnTIMI:bvrRMRCM400P0100:bd08/19/2019:svnTIMI:pnRedmiBook14:pvr:rvnTIMI:rnTM1901:rvr:cvnTIMI:ct10:cvr: dmi.product.family: Mi Laptop dmi.product.name: RedmiBook 14 dmi.product.sku: TM1901-24822 dmi.sys.vendor: TIMI To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1846148/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1848008] Re: eoan needs iproute2 v5.3.0
** Tags added: upgrade-software-version -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to iproute2 in Ubuntu. https://bugs.launchpad.net/bugs/1848008 Title: eoan needs iproute2 v5.3.0 Status in iproute2 package in Ubuntu: New Bug description: As eoan will ship a 5.3 kernel it needs iproute v5.3.0. There are important updates, e.g. to the 'rdma' command which are needed in order to activate certain kernel features. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/iproute2/+bug/1848008/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1848916] [NEW] software-properties-gtk don't started
Public bug reported: Xubuntu 20.04, software-properties-gtk don't started ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: software-properties-gtk 0.98.5 ProcVersionSignature: Ubuntu 5.3.0-18.19-generic 5.3.1 Uname: Linux 5.3.0-18-generic x86_64 ApportVersion: 2.20.11-0ubuntu8 Architecture: amd64 Date: Sun Oct 20 11:55:28 2019 InstallationDate: Installed on 2019-10-07 (12 days ago) InstallationMedia: Xubuntu 18.04.2 LTS "Bionic Beaver" - Release amd64 (20190210) PackageArchitecture: all SourcePackage: software-properties UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: software-properties (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug focal -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to software-properties in Ubuntu. https://bugs.launchpad.net/bugs/1848916 Title: software-properties-gtk don't started Status in software-properties package in Ubuntu: New Bug description: Xubuntu 20.04, software-properties-gtk don't started ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: software-properties-gtk 0.98.5 ProcVersionSignature: Ubuntu 5.3.0-18.19-generic 5.3.1 Uname: Linux 5.3.0-18-generic x86_64 ApportVersion: 2.20.11-0ubuntu8 Architecture: amd64 Date: Sun Oct 20 11:55:28 2019 InstallationDate: Installed on 2019-10-07 (12 days ago) InstallationMedia: Xubuntu 18.04.2 LTS "Bionic Beaver" - Release amd64 (20190210) PackageArchitecture: all 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/software-properties/+bug/1848916/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1818616] Re: gnome-keyring is not unlocked upon gdm login in disco
*** This bug is a duplicate of bug 1817128 *** https://bugs.launchpad.net/bugs/1817128 I've reproduced this bug on eoan-ermine. See my comments on the related bug report #1817128 -- 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/1818616 Title: gnome-keyring is not unlocked upon gdm login in disco Status in gdm3 package in Ubuntu: Confirmed Status in gnome-keyring package in Ubuntu: Confirmed Status in pam package in Ubuntu: Confirmed Status in systemd package in Ubuntu: Confirmed Bug description: I'm not sure if this is a regression in my gnome-keyring, gdm3, or pam, or local configuration. As far as I recall, I should be running just "stock" configs. I did not install system with disco, but upgraded to disco throughout development series. Upon booting, and logging in through gdm3, I get a pop-up from gnome- keyring instructing me that gnome-keyring was not unlocked upon logging, and I have to re-enter the password again. The password for the account and the gnome-keyring are the same, and the keyring should be auto-unlocked. Looking at the journal, there is a red warning from gdm: Mar 05 08:15:58 ottawa gdm-password][18338]: gkr-pam: unable to locate daemon control file Looking at the code, this happens when neither GNOME_KEYRING_CONTROL nor XDG_RUNTIME_DIR are set. The messages after it are: Mar 05 08:15:58 ottawa gdm-password][18338]: gkr-pam: unable to locate daemon control file Mar 05 08:15:58 ottawa gdm-password][18338]: pam_unix(gdm-password:session): session opened for user xnox by (uid=0) Mar 05 08:15:58 ottawa systemd[1]: Created slice User Slice of UID 1000. Mar 05 08:15:58 ottawa systemd[1]: Starting User Runtime Directory /run/user/1000... Mar 05 08:15:58 ottawa systemd-logind[1376]: New session 3 of user xnox. Mar 05 08:15:58 ottawa systemd[1]: Started User Runtime Directory /run/user/1000. Mar 05 08:15:58 ottawa systemd[1]: Starting User Manager for UID 1000... Mar 05 08:15:58 ottawa systemd[18344]: pam_unix(systemd-user:session): session opened for user xnox by (uid=0) Mar 05 08:15:58 ottawa systemd[18344]: Listening on Sound System. Mar 05 08:15:58 ottawa systemd[18344]: Listening on GnuPG cryptographic agent (ssh-agent emulation). Mar 05 08:15:58 ottawa systemd[18344]: Started Pending report trigger for Ubuntu Report. Mar 05 08:15:58 ottawa systemd[18344]: Listening on GnuPG cryptographic agent and passphrase cache (restricted). Mar 05 08:15:58 ottawa systemd[18344]: Listening on GnuPG cryptographic agent and passphrase cache. Mar 05 08:15:58 ottawa systemd[18344]: Reached target Paths. Mar 05 08:15:58 ottawa systemd[18344]: Listening on GnuPG cryptographic agent and passphrase cache (access for web browsers). Mar 05 08:15:58 ottawa systemd[18344]: Reached target Timers. Mar 05 08:15:58 ottawa systemd[18344]: Listening on GnuPG network certificate management daemon. Mar 05 08:15:58 ottawa systemd[18344]: Starting D-Bus User Message Bus Socket. Mar 05 08:15:58 ottawa systemd[18344]: Listening on D-Bus User Message Bus Socket. Mar 05 08:15:58 ottawa systemd[18344]: Reached target Sockets. Mar 05 08:15:58 ottawa systemd[18344]: Reached target Basic System. Mar 05 08:15:58 ottawa systemd[1]: Started User Manager for UID 1000. Mar 05 08:15:58 ottawa systemd[18344]: Started Emacs text editor. Mar 05 08:15:58 ottawa systemd[18344]: Reached target Default. Mar 05 08:15:58 ottawa systemd[18344]: Startup finished in 72ms. Mar 05 08:15:58 ottawa systemd[1]: Started Session 3 of user xnox. I don't believe GNOME_KEYRING_CONTROL used to be set, however I do see that XDG_RUNTIME_DIR to be created and set by logind. From the above logs I can see that it happens _after_ gdm-password is done. So It seems like something has changed in the stack, and gdm login / libpam-gnome-keyring no longer use systemd-logind PAM module to be part of the PAM session. But I'm not sure what has changed to cause this (gdm, gnome-keyring, pam, systemd). Am I the only one with this issue? ProblemType: Bug DistroRelease: Ubuntu 19.04 Package: gnome-keyring 3.31.90-1ubuntu1 ProcVersionSignature: Ubuntu 4.19.0-13.14-generic 4.19.20 Uname: Linux 4.19.0-13-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.20.10-0ubuntu21 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Tue Mar 5 08:22:01 2019 InstallationDate: Installed on 2016-01-26 (1134 days ago) InstallationMedia: Ubuntu-Server 16.04 LTS "Xenial Xerus" - Alpha amd64 (20160125) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: gnome-keyring UpgradeStatus: Upgraded to disco on 2019-01-15 (48 days ago) To manage notifications about this bug go to:
[Touch-packages] [Bug 1818616] Re: gnome-keyring is not unlocked upon gdm login in disco
*** This bug is a duplicate of bug 1817128 *** https://bugs.launchpad.net/bugs/1817128 Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: systemd (Ubuntu) Status: New => Confirmed -- 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/1818616 Title: gnome-keyring is not unlocked upon gdm login in disco Status in gdm3 package in Ubuntu: Confirmed Status in gnome-keyring package in Ubuntu: Confirmed Status in pam package in Ubuntu: Confirmed Status in systemd package in Ubuntu: Confirmed Bug description: I'm not sure if this is a regression in my gnome-keyring, gdm3, or pam, or local configuration. As far as I recall, I should be running just "stock" configs. I did not install system with disco, but upgraded to disco throughout development series. Upon booting, and logging in through gdm3, I get a pop-up from gnome- keyring instructing me that gnome-keyring was not unlocked upon logging, and I have to re-enter the password again. The password for the account and the gnome-keyring are the same, and the keyring should be auto-unlocked. Looking at the journal, there is a red warning from gdm: Mar 05 08:15:58 ottawa gdm-password][18338]: gkr-pam: unable to locate daemon control file Looking at the code, this happens when neither GNOME_KEYRING_CONTROL nor XDG_RUNTIME_DIR are set. The messages after it are: Mar 05 08:15:58 ottawa gdm-password][18338]: gkr-pam: unable to locate daemon control file Mar 05 08:15:58 ottawa gdm-password][18338]: pam_unix(gdm-password:session): session opened for user xnox by (uid=0) Mar 05 08:15:58 ottawa systemd[1]: Created slice User Slice of UID 1000. Mar 05 08:15:58 ottawa systemd[1]: Starting User Runtime Directory /run/user/1000... Mar 05 08:15:58 ottawa systemd-logind[1376]: New session 3 of user xnox. Mar 05 08:15:58 ottawa systemd[1]: Started User Runtime Directory /run/user/1000. Mar 05 08:15:58 ottawa systemd[1]: Starting User Manager for UID 1000... Mar 05 08:15:58 ottawa systemd[18344]: pam_unix(systemd-user:session): session opened for user xnox by (uid=0) Mar 05 08:15:58 ottawa systemd[18344]: Listening on Sound System. Mar 05 08:15:58 ottawa systemd[18344]: Listening on GnuPG cryptographic agent (ssh-agent emulation). Mar 05 08:15:58 ottawa systemd[18344]: Started Pending report trigger for Ubuntu Report. Mar 05 08:15:58 ottawa systemd[18344]: Listening on GnuPG cryptographic agent and passphrase cache (restricted). Mar 05 08:15:58 ottawa systemd[18344]: Listening on GnuPG cryptographic agent and passphrase cache. Mar 05 08:15:58 ottawa systemd[18344]: Reached target Paths. Mar 05 08:15:58 ottawa systemd[18344]: Listening on GnuPG cryptographic agent and passphrase cache (access for web browsers). Mar 05 08:15:58 ottawa systemd[18344]: Reached target Timers. Mar 05 08:15:58 ottawa systemd[18344]: Listening on GnuPG network certificate management daemon. Mar 05 08:15:58 ottawa systemd[18344]: Starting D-Bus User Message Bus Socket. Mar 05 08:15:58 ottawa systemd[18344]: Listening on D-Bus User Message Bus Socket. Mar 05 08:15:58 ottawa systemd[18344]: Reached target Sockets. Mar 05 08:15:58 ottawa systemd[18344]: Reached target Basic System. Mar 05 08:15:58 ottawa systemd[1]: Started User Manager for UID 1000. Mar 05 08:15:58 ottawa systemd[18344]: Started Emacs text editor. Mar 05 08:15:58 ottawa systemd[18344]: Reached target Default. Mar 05 08:15:58 ottawa systemd[18344]: Startup finished in 72ms. Mar 05 08:15:58 ottawa systemd[1]: Started Session 3 of user xnox. I don't believe GNOME_KEYRING_CONTROL used to be set, however I do see that XDG_RUNTIME_DIR to be created and set by logind. From the above logs I can see that it happens _after_ gdm-password is done. So It seems like something has changed in the stack, and gdm login / libpam-gnome-keyring no longer use systemd-logind PAM module to be part of the PAM session. But I'm not sure what has changed to cause this (gdm, gnome-keyring, pam, systemd). Am I the only one with this issue? ProblemType: Bug DistroRelease: Ubuntu 19.04 Package: gnome-keyring 3.31.90-1ubuntu1 ProcVersionSignature: Ubuntu 4.19.0-13.14-generic 4.19.20 Uname: Linux 4.19.0-13-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.20.10-0ubuntu21 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Tue Mar 5 08:22:01 2019 InstallationDate: Installed on 2016-01-26 (1134 days ago) InstallationMedia: Ubuntu-Server 16.04 LTS "Xenial Xerus" - Alpha amd64 (20160125) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: gnome-keyring UpgradeStatus: Upgraded to disco on 2019-01-15 (48 days ago) To manage
[Touch-packages] [Bug 1818616] Re: gnome-keyring is not unlocked upon gdm login in disco
*** This bug is a duplicate of bug 1817128 *** https://bugs.launchpad.net/bugs/1817128 Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: pam (Ubuntu) Status: New => Confirmed -- 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/1818616 Title: gnome-keyring is not unlocked upon gdm login in disco Status in gdm3 package in Ubuntu: Confirmed Status in gnome-keyring package in Ubuntu: Confirmed Status in pam package in Ubuntu: Confirmed Status in systemd package in Ubuntu: Confirmed Bug description: I'm not sure if this is a regression in my gnome-keyring, gdm3, or pam, or local configuration. As far as I recall, I should be running just "stock" configs. I did not install system with disco, but upgraded to disco throughout development series. Upon booting, and logging in through gdm3, I get a pop-up from gnome- keyring instructing me that gnome-keyring was not unlocked upon logging, and I have to re-enter the password again. The password for the account and the gnome-keyring are the same, and the keyring should be auto-unlocked. Looking at the journal, there is a red warning from gdm: Mar 05 08:15:58 ottawa gdm-password][18338]: gkr-pam: unable to locate daemon control file Looking at the code, this happens when neither GNOME_KEYRING_CONTROL nor XDG_RUNTIME_DIR are set. The messages after it are: Mar 05 08:15:58 ottawa gdm-password][18338]: gkr-pam: unable to locate daemon control file Mar 05 08:15:58 ottawa gdm-password][18338]: pam_unix(gdm-password:session): session opened for user xnox by (uid=0) Mar 05 08:15:58 ottawa systemd[1]: Created slice User Slice of UID 1000. Mar 05 08:15:58 ottawa systemd[1]: Starting User Runtime Directory /run/user/1000... Mar 05 08:15:58 ottawa systemd-logind[1376]: New session 3 of user xnox. Mar 05 08:15:58 ottawa systemd[1]: Started User Runtime Directory /run/user/1000. Mar 05 08:15:58 ottawa systemd[1]: Starting User Manager for UID 1000... Mar 05 08:15:58 ottawa systemd[18344]: pam_unix(systemd-user:session): session opened for user xnox by (uid=0) Mar 05 08:15:58 ottawa systemd[18344]: Listening on Sound System. Mar 05 08:15:58 ottawa systemd[18344]: Listening on GnuPG cryptographic agent (ssh-agent emulation). Mar 05 08:15:58 ottawa systemd[18344]: Started Pending report trigger for Ubuntu Report. Mar 05 08:15:58 ottawa systemd[18344]: Listening on GnuPG cryptographic agent and passphrase cache (restricted). Mar 05 08:15:58 ottawa systemd[18344]: Listening on GnuPG cryptographic agent and passphrase cache. Mar 05 08:15:58 ottawa systemd[18344]: Reached target Paths. Mar 05 08:15:58 ottawa systemd[18344]: Listening on GnuPG cryptographic agent and passphrase cache (access for web browsers). Mar 05 08:15:58 ottawa systemd[18344]: Reached target Timers. Mar 05 08:15:58 ottawa systemd[18344]: Listening on GnuPG network certificate management daemon. Mar 05 08:15:58 ottawa systemd[18344]: Starting D-Bus User Message Bus Socket. Mar 05 08:15:58 ottawa systemd[18344]: Listening on D-Bus User Message Bus Socket. Mar 05 08:15:58 ottawa systemd[18344]: Reached target Sockets. Mar 05 08:15:58 ottawa systemd[18344]: Reached target Basic System. Mar 05 08:15:58 ottawa systemd[1]: Started User Manager for UID 1000. Mar 05 08:15:58 ottawa systemd[18344]: Started Emacs text editor. Mar 05 08:15:58 ottawa systemd[18344]: Reached target Default. Mar 05 08:15:58 ottawa systemd[18344]: Startup finished in 72ms. Mar 05 08:15:58 ottawa systemd[1]: Started Session 3 of user xnox. I don't believe GNOME_KEYRING_CONTROL used to be set, however I do see that XDG_RUNTIME_DIR to be created and set by logind. From the above logs I can see that it happens _after_ gdm-password is done. So It seems like something has changed in the stack, and gdm login / libpam-gnome-keyring no longer use systemd-logind PAM module to be part of the PAM session. But I'm not sure what has changed to cause this (gdm, gnome-keyring, pam, systemd). Am I the only one with this issue? ProblemType: Bug DistroRelease: Ubuntu 19.04 Package: gnome-keyring 3.31.90-1ubuntu1 ProcVersionSignature: Ubuntu 4.19.0-13.14-generic 4.19.20 Uname: Linux 4.19.0-13-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.20.10-0ubuntu21 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Tue Mar 5 08:22:01 2019 InstallationDate: Installed on 2016-01-26 (1134 days ago) InstallationMedia: Ubuntu-Server 16.04 LTS "Xenial Xerus" - Alpha amd64 (20160125) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: gnome-keyring UpgradeStatus: Upgraded to disco on 2019-01-15 (48 days ago) To manage notifications
[Touch-packages] [Bug 1818616] Re: gnome-keyring is not unlocked upon gdm login in disco
*** This bug is a duplicate of bug 1817128 *** https://bugs.launchpad.net/bugs/1817128 Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: gnome-keyring (Ubuntu) Status: New => Confirmed -- 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/1818616 Title: gnome-keyring is not unlocked upon gdm login in disco Status in gdm3 package in Ubuntu: Confirmed Status in gnome-keyring package in Ubuntu: Confirmed Status in pam package in Ubuntu: Confirmed Status in systemd package in Ubuntu: Confirmed Bug description: I'm not sure if this is a regression in my gnome-keyring, gdm3, or pam, or local configuration. As far as I recall, I should be running just "stock" configs. I did not install system with disco, but upgraded to disco throughout development series. Upon booting, and logging in through gdm3, I get a pop-up from gnome- keyring instructing me that gnome-keyring was not unlocked upon logging, and I have to re-enter the password again. The password for the account and the gnome-keyring are the same, and the keyring should be auto-unlocked. Looking at the journal, there is a red warning from gdm: Mar 05 08:15:58 ottawa gdm-password][18338]: gkr-pam: unable to locate daemon control file Looking at the code, this happens when neither GNOME_KEYRING_CONTROL nor XDG_RUNTIME_DIR are set. The messages after it are: Mar 05 08:15:58 ottawa gdm-password][18338]: gkr-pam: unable to locate daemon control file Mar 05 08:15:58 ottawa gdm-password][18338]: pam_unix(gdm-password:session): session opened for user xnox by (uid=0) Mar 05 08:15:58 ottawa systemd[1]: Created slice User Slice of UID 1000. Mar 05 08:15:58 ottawa systemd[1]: Starting User Runtime Directory /run/user/1000... Mar 05 08:15:58 ottawa systemd-logind[1376]: New session 3 of user xnox. Mar 05 08:15:58 ottawa systemd[1]: Started User Runtime Directory /run/user/1000. Mar 05 08:15:58 ottawa systemd[1]: Starting User Manager for UID 1000... Mar 05 08:15:58 ottawa systemd[18344]: pam_unix(systemd-user:session): session opened for user xnox by (uid=0) Mar 05 08:15:58 ottawa systemd[18344]: Listening on Sound System. Mar 05 08:15:58 ottawa systemd[18344]: Listening on GnuPG cryptographic agent (ssh-agent emulation). Mar 05 08:15:58 ottawa systemd[18344]: Started Pending report trigger for Ubuntu Report. Mar 05 08:15:58 ottawa systemd[18344]: Listening on GnuPG cryptographic agent and passphrase cache (restricted). Mar 05 08:15:58 ottawa systemd[18344]: Listening on GnuPG cryptographic agent and passphrase cache. Mar 05 08:15:58 ottawa systemd[18344]: Reached target Paths. Mar 05 08:15:58 ottawa systemd[18344]: Listening on GnuPG cryptographic agent and passphrase cache (access for web browsers). Mar 05 08:15:58 ottawa systemd[18344]: Reached target Timers. Mar 05 08:15:58 ottawa systemd[18344]: Listening on GnuPG network certificate management daemon. Mar 05 08:15:58 ottawa systemd[18344]: Starting D-Bus User Message Bus Socket. Mar 05 08:15:58 ottawa systemd[18344]: Listening on D-Bus User Message Bus Socket. Mar 05 08:15:58 ottawa systemd[18344]: Reached target Sockets. Mar 05 08:15:58 ottawa systemd[18344]: Reached target Basic System. Mar 05 08:15:58 ottawa systemd[1]: Started User Manager for UID 1000. Mar 05 08:15:58 ottawa systemd[18344]: Started Emacs text editor. Mar 05 08:15:58 ottawa systemd[18344]: Reached target Default. Mar 05 08:15:58 ottawa systemd[18344]: Startup finished in 72ms. Mar 05 08:15:58 ottawa systemd[1]: Started Session 3 of user xnox. I don't believe GNOME_KEYRING_CONTROL used to be set, however I do see that XDG_RUNTIME_DIR to be created and set by logind. From the above logs I can see that it happens _after_ gdm-password is done. So It seems like something has changed in the stack, and gdm login / libpam-gnome-keyring no longer use systemd-logind PAM module to be part of the PAM session. But I'm not sure what has changed to cause this (gdm, gnome-keyring, pam, systemd). Am I the only one with this issue? ProblemType: Bug DistroRelease: Ubuntu 19.04 Package: gnome-keyring 3.31.90-1ubuntu1 ProcVersionSignature: Ubuntu 4.19.0-13.14-generic 4.19.20 Uname: Linux 4.19.0-13-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.20.10-0ubuntu21 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Tue Mar 5 08:22:01 2019 InstallationDate: Installed on 2016-01-26 (1134 days ago) InstallationMedia: Ubuntu-Server 16.04 LTS "Xenial Xerus" - Alpha amd64 (20160125) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: gnome-keyring UpgradeStatus: Upgraded to disco on 2019-01-15 (48 days ago) To manage
[Touch-packages] [Bug 1818616] Re: gnome-keyring is not unlocked upon gdm login in disco
*** This bug is a duplicate of bug 1817128 *** https://bugs.launchpad.net/bugs/1817128 Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: gdm3 (Ubuntu) Status: New => Confirmed -- 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/1818616 Title: gnome-keyring is not unlocked upon gdm login in disco Status in gdm3 package in Ubuntu: Confirmed Status in gnome-keyring package in Ubuntu: Confirmed Status in pam package in Ubuntu: Confirmed Status in systemd package in Ubuntu: Confirmed Bug description: I'm not sure if this is a regression in my gnome-keyring, gdm3, or pam, or local configuration. As far as I recall, I should be running just "stock" configs. I did not install system with disco, but upgraded to disco throughout development series. Upon booting, and logging in through gdm3, I get a pop-up from gnome- keyring instructing me that gnome-keyring was not unlocked upon logging, and I have to re-enter the password again. The password for the account and the gnome-keyring are the same, and the keyring should be auto-unlocked. Looking at the journal, there is a red warning from gdm: Mar 05 08:15:58 ottawa gdm-password][18338]: gkr-pam: unable to locate daemon control file Looking at the code, this happens when neither GNOME_KEYRING_CONTROL nor XDG_RUNTIME_DIR are set. The messages after it are: Mar 05 08:15:58 ottawa gdm-password][18338]: gkr-pam: unable to locate daemon control file Mar 05 08:15:58 ottawa gdm-password][18338]: pam_unix(gdm-password:session): session opened for user xnox by (uid=0) Mar 05 08:15:58 ottawa systemd[1]: Created slice User Slice of UID 1000. Mar 05 08:15:58 ottawa systemd[1]: Starting User Runtime Directory /run/user/1000... Mar 05 08:15:58 ottawa systemd-logind[1376]: New session 3 of user xnox. Mar 05 08:15:58 ottawa systemd[1]: Started User Runtime Directory /run/user/1000. Mar 05 08:15:58 ottawa systemd[1]: Starting User Manager for UID 1000... Mar 05 08:15:58 ottawa systemd[18344]: pam_unix(systemd-user:session): session opened for user xnox by (uid=0) Mar 05 08:15:58 ottawa systemd[18344]: Listening on Sound System. Mar 05 08:15:58 ottawa systemd[18344]: Listening on GnuPG cryptographic agent (ssh-agent emulation). Mar 05 08:15:58 ottawa systemd[18344]: Started Pending report trigger for Ubuntu Report. Mar 05 08:15:58 ottawa systemd[18344]: Listening on GnuPG cryptographic agent and passphrase cache (restricted). Mar 05 08:15:58 ottawa systemd[18344]: Listening on GnuPG cryptographic agent and passphrase cache. Mar 05 08:15:58 ottawa systemd[18344]: Reached target Paths. Mar 05 08:15:58 ottawa systemd[18344]: Listening on GnuPG cryptographic agent and passphrase cache (access for web browsers). Mar 05 08:15:58 ottawa systemd[18344]: Reached target Timers. Mar 05 08:15:58 ottawa systemd[18344]: Listening on GnuPG network certificate management daemon. Mar 05 08:15:58 ottawa systemd[18344]: Starting D-Bus User Message Bus Socket. Mar 05 08:15:58 ottawa systemd[18344]: Listening on D-Bus User Message Bus Socket. Mar 05 08:15:58 ottawa systemd[18344]: Reached target Sockets. Mar 05 08:15:58 ottawa systemd[18344]: Reached target Basic System. Mar 05 08:15:58 ottawa systemd[1]: Started User Manager for UID 1000. Mar 05 08:15:58 ottawa systemd[18344]: Started Emacs text editor. Mar 05 08:15:58 ottawa systemd[18344]: Reached target Default. Mar 05 08:15:58 ottawa systemd[18344]: Startup finished in 72ms. Mar 05 08:15:58 ottawa systemd[1]: Started Session 3 of user xnox. I don't believe GNOME_KEYRING_CONTROL used to be set, however I do see that XDG_RUNTIME_DIR to be created and set by logind. From the above logs I can see that it happens _after_ gdm-password is done. So It seems like something has changed in the stack, and gdm login / libpam-gnome-keyring no longer use systemd-logind PAM module to be part of the PAM session. But I'm not sure what has changed to cause this (gdm, gnome-keyring, pam, systemd). Am I the only one with this issue? ProblemType: Bug DistroRelease: Ubuntu 19.04 Package: gnome-keyring 3.31.90-1ubuntu1 ProcVersionSignature: Ubuntu 4.19.0-13.14-generic 4.19.20 Uname: Linux 4.19.0-13-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.20.10-0ubuntu21 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Tue Mar 5 08:22:01 2019 InstallationDate: Installed on 2016-01-26 (1134 days ago) InstallationMedia: Ubuntu-Server 16.04 LTS "Xenial Xerus" - Alpha amd64 (20160125) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: gnome-keyring UpgradeStatus: Upgraded to disco on 2019-01-15 (48 days ago) To manage notifications
[Touch-packages] [Bug 1312673] Re: software-properties-gtk crashed with aptsources.distro.NoDistroTemplateException in get_sources(): Error: could not find a distribution template for Ubuntu/bionic
software-properties-gtk crashed with aptsources.distro.NoDistroTemplateException in get_sources(): Error: could not find a distribution template for Ubuntu/focal -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to python-apt in Ubuntu. https://bugs.launchpad.net/bugs/1312673 Title: software-properties-gtk crashed with aptsources.distro.NoDistroTemplateException in get_sources(): Error: could not find a distribution template for Ubuntu/bionic Status in python-apt package in Ubuntu: Fix Released Bug description: lsb_release -rd Description:Ubuntu Utopic Unicorn (development branch) Release:14.10 apt-cache policy software-properties-gtk software-properties-gtk: Installed: 0.92.37 Candidate: 0.92.37 Version table: *** 0.92.37 0 500 http://archive.ubuntu.com/ubuntu/ trusty-proposed/main amd64 Packages 100 /var/lib/dpkg/status 0.92.36 0 500 http://archive.ubuntu.com/ubuntu/ trusty/main amd64 Packages ProblemType: Crash DistroRelease: Ubuntu 14.10 Package: software-properties-gtk 0.92.37 Uname: Linux 3.14.0-999-generic x86_64 ApportVersion: 2.14.1-0ubuntu3 Architecture: amd64 Date: Fri Apr 25 19:27:37 2014 ExecutablePath: /usr/bin/software-properties-gtk InstallationDate: Installed on 2012-09-30 (572 days ago) InstallationMedia: Ubuntu 12.04.1 LTS "Precise Pangolin" - Release amd64 (20120817.1) InterpreterPath: /usr/bin/python3.4 PackageArchitecture: all ProcCmdline: /usr/bin/python3 /usr/bin/software-properties-gtk --open-tab 2 --toplevel 62914567 PythonArgs: ['/usr/bin/software-properties-gtk', '--open-tab', '2', '--toplevel', '62914567'] SourcePackage: software-properties Title: software-properties-gtk crashed with aptsources.distro.NoDistroTemplateException in get_sources(): Error: could not find a distribution template for Ubuntu/utopic UpgradeStatus: Upgraded to utopic on 2013-11-10 (165 days ago) UserGroups: To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/python-apt/+bug/1312673/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1848849] Re: Lightdm fails to undo quoting for Exec key
** Package changed: unity-settings-daemon (Ubuntu) => lightdm (Ubuntu) ** Package changed: lightdm (Ubuntu) => lightdm -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to lightdm in Ubuntu. https://bugs.launchpad.net/bugs/1848849 Title: Lightdm fails to undo quoting for Exec key Status in Light Display Manager: New Bug description: According to spec/documentation, "implementations must undo quoting before expanding field codes and before passing the argument to the executable program." https://developer.gnome.org/desktop-entry-spec/#exec-variables lightdm fails to do so and passes the double-quote characters to the executable program. Consider the following files: myecho: #!/bin/bash echo "$1" > /tmp/cmd /usr/share/xsessions/test.desktop: [Desktop Entry] Name=Test Comment=This is a test session Type=Application Exec=myecho "argument" myecho is to be located somewhere in the PATH. When trying to start a desktop session defined by test.desktop, as a result of running myecho, the first command-line argument from the Exec is written to /tmp/cmd. Here is where lightdm is wrong: Starting the 'test' session under lightdm causes '"argument"' (without the surrounding single quotes) to be written to /tmp/cmd. The correct string should be 'argument' (without the surrounding single quotes). If the double-quotes are removed from the Exec line, lightdm behaves normally and 'argument' is written. A practical consequence of this bug is that users can't use "bash -c" to run multiple commands when special characters (including spaces) are needed in the argument after "-c". It seems that the user must resort to a wrapper script because of this bug. $ lsb_release -rd Description: Ubuntu 19.04 Release: 19.04 $ apt-cache policy lightdm lightdm: Installed: 1.28.0-0ubuntu1 Candidate: 1.28.0-0ubuntu1 Version table: *** 1.28.0-0ubuntu1 500 500 http://mirrors.yun-idc.com/ubuntu disco/universe amd64 Packages 100 /var/lib/dpkg/status To manage notifications about this bug go to: https://bugs.launchpad.net/lightdm/+bug/1848849/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
