[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
[Touch-packages] [Bug 1848849] [NEW] Lightdm fails to undo quoting for Exec key
You have been subscribed to a public bug: 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 ** Affects: lightdm (Ubuntu) Importance: Undecided Status: New -- Lightdm fails to undo quoting for Exec key https://bugs.launchpad.net/bugs/1848849 You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to lightdm in Ubuntu. -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1797717] Re: fstrim -av tries to trim read only mounted ntfs-3g and fails
** Tags added: eoan -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to util-linux in Ubuntu. https://bugs.launchpad.net/bugs/1797717 Title: fstrim -av tries to trim read only mounted ntfs-3g and fails Status in util-linux package in Ubuntu: Confirmed Bug description: If I run sudo fstrim -av I see: /media/SSD_Data: 2 GiB (2145820672 bytes) trimmed fstrim: /media/Win7: FITRIM ioctl failed: Bad file descriptor /: 26.9 GiB (28823887872 bytes) trimmed /media/SSD_Data is read-write mounted NTFS via ntfs-3g, and /media/Win7 is read-only mounted NTFS, also via ntfs-3g. Lines from fstab: UUID=censored /media/SSD_Data ntfs-3g rw,noatime,nofail,big_writes,windows_names,nosuid,nodev,allow_other,hide_hid_files,inherit,noexec 0 0 UUID=censored /media/Win7 ntfs-3g ro,nofail,big_writes,windows_names,nosuid,nodev,allow_other,noexec,hide_hid_files 0 0 If I do sudo umount /media/Win7 and then sudo mount -o rw /media/Win7 then sudo fstrim -av takes longer and succeeds for all filesystems. So, it seems the read only is the problem. This seems cosmetic, but it causes periodic runs of fstrim via systemd to report failures. ProblemType: Bug DistroRelease: Ubuntu 18.10 Package: util-linux 2.32-0.1ubuntu1 ProcVersionSignature: Ubuntu 4.18.0-8.9-generic 4.18.7 Uname: Linux 4.18.0-8-generic x86_64 NonfreeKernelModules: nvidia ApportVersion: 2.20.10-0ubuntu11 Architecture: amd64 CurrentDesktop: XFCE Date: Sat Oct 13 15:25:41 2018 SourcePackage: util-linux UpgradeStatus: Upgraded to cosmic on 2018-10-11 (2 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/util-linux/+bug/1797717/+subscriptions -- Mailing list: https://launchpad.net/~touch-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: blank display with Eoan Ermine live DVD on Rysen 2200G
** Attachment added: ""journalctl -b -1" (failed boot) for other user" https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1848900/+attachment/5298524/+files/jj9k.log ** Summary changed: - blank display with Eoan Ermine live DVD on Rysen 2200G + Blank display with Eoan Ermine live DVD on Ryzen 3 2200G -- 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: Blank display with Eoan Ermine live DVD on Ryzen 3 2200G Status in xorg 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 d
[Touch-packages] [Bug 1848900] Re: blank display with Eoan Ermine live DVD on Rysen 2200G
I was supporting another Xubuntu 19.10 user on AMD Ryzen 3 2200G (Gigabyte Technology Co., Ltd. B450 AORUS M/B450 AORUS M, BIOS F2 08/08/2018) today, whose log of a failed (standard) boot (to black screen) showed kernel: WARNING: CPU: 2 PID: 255 at drivers/gpu/drm/amd/amdgpu/../display/dc/dcn10/dcn10_hw_sequencer.c:932 dcn10_verify_allow_pstate_change_high.cold+0xc/0x23d [amdgpu] which seems to be discussed at https://bugs.freedesktop.org/show_bug.cgi?id=109628 ** Bug watch added: freedesktop.org Bugzilla #109628 https://bugs.freedesktop.org/show_bug.cgi?id=109628 -- 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: Blank display with Eoan Ermine live DVD on Ryzen 3 2200G Status in xorg 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.xser
[Touch-packages] [Bug 1848180] Re: LVM initrd fails to activate btrfs multidevice root
I have a similar setup, but LVM is wrapped in LUKS as well. When I was dropped to the initramfs shell during boot (after entering the LUKS passphrase), I think this was how I got the system to start: /sbin/lvm vgchange -a y mount -o subvol=root /dev/mapper/(one-of-the-root-volumes) /root exit I can confirm next time I restart. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to lvm2 in Ubuntu. https://bugs.launchpad.net/bugs/1848180 Title: LVM initrd fails to activate btrfs multidevice root Status in lvm2 package in Ubuntu: Confirmed Bug description: I have two lvm volumes (/dev/mapper/raid-btrfs and /dev/mapper/fast- btrfs) in two different volume groups. I have created a btrfs (raid1) filesystem on top of them and that's my root filesystem. If i define it by UUID in the root= kernel argument, i just hit bug #1574333. Forcing my root to "/dev/mapper/fast-btrfs" by defining GRUB_DEVICE in /etc/default/grub works around that bug. The problem now is that initrd is only activating the device given as root= argument, leaving the other inactive; consequently the btrfs mount fails to find its second device and the system fails to boot giving up at initramfs prompt. Manually adding a line to activate also 2nd device at the bottom of /usr/share/initramfs-tools/scripts/local-top/lvm2 and rebuilding the initramfs works around this issue too, but i suppose my mods will be washed away by next package upgrade. Here is the result: > activate "$ROOT" > activate "$resume" > activate "/dev/mapper/raid-btrfs" Proposed solution: I understand this is an uncommon setup and correctly handling multidevice LVM roots is complicated, please just add a configuration option to manually define/append the list of volume groups to be activated at initrd time. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/lvm2/+bug/1848180/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1848180] Re: LVM initrd fails to activate btrfs multidevice root
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: lvm2 (Ubuntu) Status: New => Confirmed -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to lvm2 in Ubuntu. https://bugs.launchpad.net/bugs/1848180 Title: LVM initrd fails to activate btrfs multidevice root Status in lvm2 package in Ubuntu: Confirmed Bug description: I have two lvm volumes (/dev/mapper/raid-btrfs and /dev/mapper/fast- btrfs) in two different volume groups. I have created a btrfs (raid1) filesystem on top of them and that's my root filesystem. If i define it by UUID in the root= kernel argument, i just hit bug #1574333. Forcing my root to "/dev/mapper/fast-btrfs" by defining GRUB_DEVICE in /etc/default/grub works around that bug. The problem now is that initrd is only activating the device given as root= argument, leaving the other inactive; consequently the btrfs mount fails to find its second device and the system fails to boot giving up at initramfs prompt. Manually adding a line to activate also 2nd device at the bottom of /usr/share/initramfs-tools/scripts/local-top/lvm2 and rebuilding the initramfs works around this issue too, but i suppose my mods will be washed away by next package upgrade. Here is the result: > activate "$ROOT" > activate "$resume" > activate "/dev/mapper/raid-btrfs" Proposed solution: I understand this is an uncommon setup and correctly handling multidevice LVM roots is complicated, please just add a configuration option to manually define/append the list of volume groups to be activated at initrd time. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/lvm2/+bug/1848180/+subscriptions -- Mailing list: https://launchpad.net/~touch-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] [NEW] blank display with Eoan Ermine live DVD on Rysen 2200G
Public bug reported: 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. 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 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: blank display with Eoan Ermine live DVD on Rysen 2200G Status in xorg 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
[Touch-packages] [Bug 1833114] Re: print page dialog latency when trying to cancel or to save
This problem does not affect a brand new user if I create one. So it is maybe to do with having upgraded, and having old settings? How do I reset the relevant settings? -- 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/1833114 Title: print page dialog latency when trying to cancel or to save Status in chromium-browser package in Ubuntu: New Status in gtk+3.0 package in Ubuntu: Confirmed Bug description: Since less than a month ago, using the print page dialog (which for me defaults to saving as PDF) is outlandishly slow. Once opened, if I try to close it (click cancel / press Esc) or to use it (click Save or press Enter), there is no visible response, and my system hangs for 10 seconds. After that though, the operation concludes successfully and things return to normal. This did not used to happen. Closing or submitting the print-to-PDF used to result in the pop-up window closing immediately and the browser regaining responsiveness. ProblemType: Bug DistroRelease: Ubuntu 19.04 Package: chromium-browser 74.0.3729.169-0ubuntu0.19.04.1 ProcVersionSignature: Ubuntu 5.0.0-16.17-generic 5.0.8 Uname: Linux 5.0.0-16-generic x86_64 ApportVersion: 2.20.10-0ubuntu27 Architecture: amd64 CurrentDesktop: ubuntu:GNOME DRM.card0-DP-1: enabled: disabled dpms: Off status: disconnected edid-base64: modes: DRM.card0-DP-2: enabled: disabled dpms: Off status: disconnected edid-base64: modes: DRM.card0-DP-5: enabled: enabled dpms: On status: connected edid-base64: AP///wAEchAEyHEQUQsZAQSlRyh4PiVfqFRNnyUOT1O/74BxT4FAgYCBwIEAlQCzANHATdAAoPBwPoAwIDUAxY8hAAAaBHQAMPJwWoCwWIoAxY8hAAAa/QAdTB+gPAEKICAgICAg/ABCMzI2SEsKICAgICAgAQwCAxzhT5ACAwQFBgcBERITFBUWHyMJBweDAQAAAjqAGHE4LUBYLEUAxY8hAAAeAR2AGHEcFiBYLCUAxY8hAACeAR0AclHQHiBuKFUAxY8hAAAejArQiiDgLRAQPpYAxY8hAAAYVl4AoKCgKVAwIDUAxI8hAAAa modes: 3840x2160 3840x2160 2560x1440 1920x1080 1920x1080 1920x1080 1920x1080 1680x1050 1280x1024 1280x1024 1440x900 1280x960 1280x800 1152x864 1280x720 1280x720 1280x720 1280x720 1024x768 1024x768 1024x768 832x624 800x600 800x600 800x600 800x600 720x576 720x576 720x480 720x480 720x480 720x480 720x480 640x480 640x480 640x480 640x480 640x480 640x480 720x400 DRM.card0-DP-6: enabled: disabled dpms: On status: connected edid-base64: AP///wAQrAngTEFNMAkPAQPOKxt46gGVo1dMnCUSUFSlSwCBgHFPAQEBAQEBAQEBAQEBfC6QoGAaHkAwIDYAsg4RAAAa/wBUNjEzMDUzMjBNQUwK/QA4Sx5TDgAKICAgICAg/ABERUxMIDIwMDVGUFcKAAM= modes: 1680x1050 1280x1024 1280x1024 1152x864 1024x768 1024x768 800x600 800x600 640x480 640x480 720x400 DRM.card0-DP-7: enabled: disabled dpms: On status: disconnected edid-base64: modes: DRM.card0-HDMI-A-1: enabled: disabled dpms: Off status: disconnected edid-base64: modes: DRM.card0-HDMI-A-2: enabled: disabled dpms: Off status: disconnected edid-base64: modes: DRM.card0-eDP-1: enabled: enabled dpms: On status: connected edid-base64: AP///wAGrz0TACYXAQSVHxF4AoflpFZQniYNUFQBAQEBAQEBAQEBAQEBAQEBFDeAuHA4JEAQED4ANa0QAAAYDwAg/gBBVU8KICAgICAgICAg/gBCMTQwSEFOMDEuMyAKAHo= modes: 1920x1080 Date: Mon Jun 17 14:03:12 2019 Desktop-Session: 'ubuntu' '/etc/xdg/xdg-ubuntu:/etc/xdg' '/usr/share/ubuntu:/usr/local/share:/usr/share:/var/lib/snapd/desktop' DetectedPlugins: EcryptfsInUse: Yes Env: 'None' 'None' InstallationDate: Installed on 2019-01-24 (144 days ago) InstallationMedia: Ubuntu 18.10 "Cosmic Cuttlefish" - Release amd64 (20181017.3) InstalledPlugins: Load-Avg-1min: 3.09 Load-Processes-Running-Percent: 0.1% MachineType: LENOVO 20BXCTO1WW ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.0.0-16-generic root=UUID=a6081f39-700f-4698-bda4-464e53d9d229 ro quiet splash vt.handoff=1 SourcePackage: chromium-browser UpgradeStatus: Upgraded to disco on 2019-05-29 (19 days ago) dmi.bios.date: 09/13/2017 dmi.bios.vendor: LENOVO dmi.bios.version: JBET66WW (1.30 ) dmi.board.asset.tag: Not Available dmi.board.name: 20BXCTO1WW dmi.board.vendor: LENOVO dmi.board.version: SDK0J40697 WIN dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: None dmi.modalias: dmi:bvnLENOVO:bvrJBET66WW(1.30):bd09/13/2017:svnLENOVO:pn20BXCTO1WW:pvrThinkPadT450s:rvnLENOVO:rn20BXCTO1WW:rvrSDK0J40697WIN:cvnLENOVO:ct10:cvrNone: dmi.product.family: ThinkPad T450s dmi.product.name: 20BXCTO1WW dmi.product.sku: LENOVO_MT_20BX_BU_Think_FM_ThinkPad T450s dmi.product.version: ThinkPad T450s dmi.sys.vendor: LENOVO modified.conffile..etc.default.chromium-browser: [deleted] To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/1833114/+subscription
[Touch-packages] [Bug 1554099] Re: Changing what action for security updates unusable
gedit /etc/apt/apt.conf.d/10periodic Set "0" to APT::Periodic::Unattended-Upgrade "0"; I test ok and pass -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to unattended-upgrades in Ubuntu. https://bugs.launchpad.net/bugs/1554099 Title: Changing what action for security updates unusable Status in software-properties package in Ubuntu: Fix Released Status in unattended-upgrades package in Ubuntu: Invalid Status in software-properties source package in Xenial: Fix Released Status in unattended-upgrades source package in Xenial: Invalid Bug description: Open software-properties. Important security updates is not enabled on install. Secondly - it is not possible to change the action to take with security updates even if it is enabled (note: I enabled security updates, reloaded cache and restarted software-properties before trying to change the action) eg - the Display Immediately/Download automatically/Download and install automatically ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: software-properties-gtk 0.96.18 ProcVersionSignature: Ubuntu 4.4.0-10.25-generic 4.4.3 Uname: Linux 4.4.0-10-generic x86_64 ApportVersion: 2.20-0ubuntu3 Architecture: amd64 CurrentDesktop: XFCE Date: Mon Mar 7 15:35:24 2016 InstallationDate: Installed on 2016-03-07 (0 days ago) InstallationMedia: Xubuntu 16.04 LTS "Xenial Xerus" - Alpha amd64 (20160307) 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/1554099/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1846557] Re: Unable to debug any kernel on i386 qemu machine
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: gdb (Ubuntu) Status: New => Confirmed -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to gdb in Ubuntu. https://bugs.launchpad.net/bugs/1846557 Title: Unable to debug any kernel on i386 qemu machine Status in gdb package in Ubuntu: Confirmed Bug description: Hi, On my x86_64 machine [running Ubuntu 18.04.3 LTS] with gdb version 'Ubuntu 8.1-0ubuntu3' I could happily debug any kernel running on a i386 qemu VM (qemu-system-i386) by just doing the following: > target remote localhost:1234 > b term.c:694 and then, when the breakpoint was hit I used to observe output like: > Breakpoint 1, term_action_use_alt_buffer (t=0xc017514c , use_alt_buffer=true) > at /home/vlad/dev/tilck/kernel/char/tty/term.c:694 And then I was able to do `s`, `si` or `c`, exactly like with regular user applications. With the newest update of gdb, version 'Ubuntu 8.1-0ubuntu3.1', instead, something is broken. By doing the same things I observe: > (gdb) b term.c:693 > warning: Breakpoint address adjusted from 0xc01158fe to 0xc01158fe. Which seems (and actually is) a bad sign, for what comes later. [why do you need to change the address? why do you want to extend it to 64-bit for a 32-bit machine?? mmm..] GDB detects the breakpoint, but in a weird way: Program received signal SIGTRAP, Trace/breakpoint trap. term_action_use_alt_buffer (t=0xc017514c , use_alt_buffer=true) At this point, I'm able to read the memory and the variables BUT, I cannot continue the execution, NOR doing any kind of step. The commands apparently don't get delivered to the remote side (QEMU), or they get delivered in a wrong way somehow. Example output: (gdb) b 709 warning: Breakpoint address adjusted from 0xc0115a45 to 0xc0115a45. Breakpoint 2 at 0xc0115a45: file /home/vlad/dev/tilck/kernel/char/tty/term.c, line 709. (gdb) c Continuing. Program received signal SIGTRAP, Trace/breakpoint trap. term_action_use_alt_buffer (t=0xc017514c , use_alt_buffer=true) at /home/vlad/dev/tilck/kernel/char/tty/term.c:693 693t->alt_buf = kmalloc(sizeof(u16) * t->rows * t->cols); (gdb) c Continuing. Program received signal SIGTRAP, Trace/breakpoint trap. term_action_use_alt_buffer (t=0xc017514c , use_alt_buffer=true) at /home/vlad/dev/tilck/kernel/char/tty/term.c:693 693t->alt_buf = kmalloc(sizeof(u16) * t->rows * t->cols); (gdb) c Continuing. As you see, the whole QEMU VM is stuck until I quit GDB. Note: I downgraded exclusively GDB back to version 'Ubuntu 8.1-0ubuntu3' in order to check if the problem would be fixed and it is. I'm sure the problem has been introduced in this specific version 'Ubuntu 8.1-0ubuntu3.1' and it's *not* related with QEMU *nor* with the kernel that is being debugged. It's totally independent from that. Final remark: note that I'm running gdb on x86_64 machine, while I'm debugging a kernel running on a i386 (virtual) machine. I believe that the cross-arch scenario almost certainly has something to do with the bug, as it happened in the past on both sides (qemu and gdb). Thanks a lot, Vlad To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gdb/+bug/1846557/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1848865] [NEW] Spurious "key_press_event" when focus on entry widget using LANG=th_TH.UTF-8
Public bug reported: GTK+3 will emit spurious "key_press_event" if the focus is currently on "GtkEntry" and the locale is set to th_TH.UTF-8. This issue seems to disappear if the locale is set to something else (tested with C.UTF-8 and en_US.UTF-8), and the presence of iBus and gnome-shell affects this. Step to reproduce: 1. Boot into Xubuntu. Install package "language-pack-th" (for locale) and "libgtk-3-dev" for compiling demo program. 2. Download & compile the demo program "gtk3-entry-keyboard-event" attached in this bug. (The program is licensed under MIT.) 3. Run the program with LANG=th_TH.UTF-8. The window will contain an input box on top and a button on the bottom. 4. Click in the input box, then press a key on the keyboard. The program will print one line for each "key_press_event" delivered to the window, with keyval and hardware_keycode. Expected result: only a single line is printed. For example for "a": "window: 0x0061 0x0026" Actual result: - With LANG=th_TH.UTF-8, two lines are printed. The first line is the above line, while the second line has both values as zero: "window: 00 00" - If, instead, the locale is LANG=C.UTF-8, the program will print only one line as expected. - If iBus is installed and enabled, then 2 lines are printed with both lines containing the same code, no matter which locale it runs under. - If this same program is run in Gnome-based Ubuntu session, then only one line is printed no matter which locale it runs under. This program is tested on Fedora and Manjaro with the correct result. Thus, this issue is Ubuntu-specific. I've tested it on Ubuntu 19.10 with pretty much the same result, except the iBus case is now working correctly. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: libgtk-3-0 3.22.30-1ubuntu4 ProcVersionSignature: Ubuntu 4.15.0-65.74-generic 4.15.18 Uname: Linux 4.15.0-65-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.7 Architecture: amd64 CurrentDesktop: XFCE Date: Sat Oct 19 18:06:23 2019 InstallationDate: Installed on 2018-05-03 (533 days ago) InstallationMedia: Xubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426) SourcePackage: gtk+3.0 UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: gtk+3.0 (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug bionic ** Attachment added: "The demo program demonstrating the bug." https://bugs.launchpad.net/bugs/1848865/+attachment/5298410/+files/gtk3-entry-keyboard-event.c -- 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/1848865 Title: Spurious "key_press_event" when focus on entry widget using LANG=th_TH.UTF-8 Status in gtk+3.0 package in Ubuntu: New Bug description: GTK+3 will emit spurious "key_press_event" if the focus is currently on "GtkEntry" and the locale is set to th_TH.UTF-8. This issue seems to disappear if the locale is set to something else (tested with C.UTF-8 and en_US.UTF-8), and the presence of iBus and gnome-shell affects this. Step to reproduce: 1. Boot into Xubuntu. Install package "language-pack-th" (for locale) and "libgtk-3-dev" for compiling demo program. 2. Download & compile the demo program "gtk3-entry-keyboard-event" attached in this bug. (The program is licensed under MIT.) 3. Run the program with LANG=th_TH.UTF-8. The window will contain an input box on top and a button on the bottom. 4. Click in the input box, then press a key on the keyboard. The program will print one line for each "key_press_event" delivered to the window, with keyval and hardware_keycode. Expected result: only a single line is printed. For example for "a": "window: 0x0061 0x0026" Actual result: - With LANG=th_TH.UTF-8, two lines are printed. The first line is the above line, while the second line has both values as zero: "window: 00 00" - If, instead, the locale is LANG=C.UTF-8, the program will print only one line as expected. - If iBus is installed and enabled, then 2 lines are printed with both lines containing the same code, no matter which locale it runs under. - If this same program is run in Gnome-based Ubuntu session, then only one line is printed no matter which locale it runs under. This program is tested on Fedora and Manjaro with the correct result. Thus, this issue is Ubuntu-specific. I've tested it on Ubuntu 19.10 with pretty much the same result, except the iBus case is now working correctly. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: libgtk-3-0 3.22.30-1ubuntu4 ProcVersionSignature: Ubuntu 4.15.0-65.74-generic 4.15.18 Uname: Linux 4.15.0-65-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.7 Architecture: amd64 CurrentDesktop: XFCE Date: Sat Oct 19 18:06:23 2019 InstallationDate: Installed on 2018-05-03 (533 days ago) InstallationMedia: Xubuntu 18.04 LTS "Bionic Bea
[Touch-packages] [Bug 1848862] [NEW] HP Elitebook 840 G1 - 19.10 - Microphone mute key does not work
Public bug reported: I just installed Ubuntu 19.10 on my HP Elitebook 840 G1. Switching from Windows to Ubuntu for personal use. The mic does not enable/disable with FN+F8 combo and the light is constantly on. I found the following solution to my problem. However, I do not know how to implement it in Ubuntu 19.10 (new to Ubuntu and generally not as techinical). https://wiki.archlinux.org/index.php/HP_EliteBook_840_G1#Enable_the_microphone_muting_key 1. Would greatly appreciate if someone could point me to step by step instructions to install the code from the link above. I can report back if this resolve the issue. 2. Also, is there a way to incorporate a fix for this issue with HP laptops in Ubuntu going forward? When I was searching for a fix, I found this to be a widespread issue with various HP laptops and Ubuntu dating back a couple years. Many thanks. ** Affects: systemd (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to systemd in Ubuntu. https://bugs.launchpad.net/bugs/1848862 Title: HP Elitebook 840 G1 - 19.10 - Microphone mute key does not work Status in systemd package in Ubuntu: New Bug description: I just installed Ubuntu 19.10 on my HP Elitebook 840 G1. Switching from Windows to Ubuntu for personal use. The mic does not enable/disable with FN+F8 combo and the light is constantly on. I found the following solution to my problem. However, I do not know how to implement it in Ubuntu 19.10 (new to Ubuntu and generally not as techinical). https://wiki.archlinux.org/index.php/HP_EliteBook_840_G1#Enable_the_microphone_muting_key 1. Would greatly appreciate if someone could point me to step by step instructions to install the code from the link above. I can report back if this resolve the issue. 2. Also, is there a way to incorporate a fix for this issue with HP laptops in Ubuntu going forward? When I was searching for a fix, I found this to be a widespread issue with various HP laptops and Ubuntu dating back a couple years. Many thanks. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1848862/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1835521] Re: [regression] Windows flicker to black when resizing (Intel Apollo Lake)
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: mutter (Ubuntu) Status: New => Confirmed -- 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/1835521 Title: [regression] Windows flicker to black when resizing (Intel Apollo Lake) Status in Mutter: New Status in gnome-shell package in Ubuntu: Confirmed Status in mesa package in Ubuntu: Confirmed Status in mutter package in Ubuntu: Confirmed Bug description: I see the black zones, small windows breaks. For additional details, I use eoan-proposed and eoan-backports packages. You can see this problem in my video: https://photos.app.goo.gl/3rvLkqJj6hZwSscw9 ProblemType: Bug DistroRelease: Ubuntu 19.10 Package: gnome-shell 3.32.2-2ubuntu1 ProcVersionSignature: Ubuntu 5.0.0-20.21-generic 5.0.8 Uname: Linux 5.0.0-20-generic x86_64 ApportVersion: 2.20.11-0ubuntu3 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Fri Jul 5 13:39:13 2019 DisplayManager: gdm3 InstallationDate: Installed on 2019-07-01 (3 days ago) InstallationMedia: ProcEnviron: LANGUAGE=ru_UA:ru PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=ru_UA.UTF-8 SHELL=/bin/bash RelatedPackageVersions: mutter-common 3.32.2+git20190626-1ubuntu1 SourcePackage: gnome-shell UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/mutter/+bug/1835521/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1835521] Re: [regression] Windows flicker to black when resizing (Intel Apollo Lake)
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: gnome-shell (Ubuntu) Status: New => Confirmed -- 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/1835521 Title: [regression] Windows flicker to black when resizing (Intel Apollo Lake) Status in Mutter: New Status in gnome-shell package in Ubuntu: Confirmed Status in mesa package in Ubuntu: Confirmed Status in mutter package in Ubuntu: Confirmed Bug description: I see the black zones, small windows breaks. For additional details, I use eoan-proposed and eoan-backports packages. You can see this problem in my video: https://photos.app.goo.gl/3rvLkqJj6hZwSscw9 ProblemType: Bug DistroRelease: Ubuntu 19.10 Package: gnome-shell 3.32.2-2ubuntu1 ProcVersionSignature: Ubuntu 5.0.0-20.21-generic 5.0.8 Uname: Linux 5.0.0-20-generic x86_64 ApportVersion: 2.20.11-0ubuntu3 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Fri Jul 5 13:39:13 2019 DisplayManager: gdm3 InstallationDate: Installed on 2019-07-01 (3 days ago) InstallationMedia: ProcEnviron: LANGUAGE=ru_UA:ru PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=ru_UA.UTF-8 SHELL=/bin/bash RelatedPackageVersions: mutter-common 3.32.2+git20190626-1ubuntu1 SourcePackage: gnome-shell UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/mutter/+bug/1835521/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1835521] Re: [regression] Windows flicker to black when resizing (Intel Apollo Lake)
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: mesa (Ubuntu) Status: New => Confirmed -- 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/1835521 Title: [regression] Windows flicker to black when resizing (Intel Apollo Lake) Status in Mutter: New Status in gnome-shell package in Ubuntu: Confirmed Status in mesa package in Ubuntu: Confirmed Status in mutter package in Ubuntu: Confirmed Bug description: I see the black zones, small windows breaks. For additional details, I use eoan-proposed and eoan-backports packages. You can see this problem in my video: https://photos.app.goo.gl/3rvLkqJj6hZwSscw9 ProblemType: Bug DistroRelease: Ubuntu 19.10 Package: gnome-shell 3.32.2-2ubuntu1 ProcVersionSignature: Ubuntu 5.0.0-20.21-generic 5.0.8 Uname: Linux 5.0.0-20-generic x86_64 ApportVersion: 2.20.11-0ubuntu3 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Fri Jul 5 13:39:13 2019 DisplayManager: gdm3 InstallationDate: Installed on 2019-07-01 (3 days ago) InstallationMedia: ProcEnviron: LANGUAGE=ru_UA:ru PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=ru_UA.UTF-8 SHELL=/bin/bash RelatedPackageVersions: mutter-common 3.32.2+git20190626-1ubuntu1 SourcePackage: gnome-shell UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/mutter/+bug/1835521/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1390792] Re: Synaptic Other Software tab jumps/scrolls to top when a repository check box is clicked
** Also affects: gtk+3.0 (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to gtk+3.0 in Ubuntu. https://bugs.launchpad.net/bugs/1390792 Title: Synaptic Other Software tab jumps/scrolls to top when a repository check box is clicked Status in gtk+3.0 package in Ubuntu: New Status in software-properties package in Ubuntu: Confirmed Status in synaptic package in Ubuntu: Confirmed Bug description: In Synaptic's Software & Updates window, clicking the check box for a repository in the Other Software tab causes the list of repositories to jump to the top of the list. The scroll position of the list is instantly lost, disorienting the user, and hiding the fact that the click did anything, until the user scrolls back down to find the item that was clicked. This is only noticeable when there are enough repositories in the list to require scrolling. Finding the clicked repository again is especially difficult when all of them look nearly identical, as is the case when they're all PPAs with no comment string. (Every item in the list is just a long URL that looks very similar to the others.) It's even worse when there are both package and source URLs for each repo. This is especially problematic when updating the repo URLs after a distribution upgrade, because it's a very repetitive task, and the scroll window jumps and loses its place every single time. Ubuntu 14.04.1 LTS synaptic 0.81.1ubuntu1 amd64 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gtk+3.0/+bug/1390792/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1323285] Re: Tab for "Other software" repositories isn't usable with keyboard
Got this bug on 19.10. Only "Remove" button has mnemonics (), but "Add" and "Edit" do not have keyboard mnemonics/accelerators. So I'm unable to edit repository only by using keyboard. ** Tags removed: cosmic i386 ** Tags added: disco eoan xenial -- 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/1323285 Title: Tab for "Other software" repositories isn't usable with keyboard Status in software-properties package in Ubuntu: Confirmed Bug description: The "other software" tab isn't keyboard-accessible. The list of software repositories can be navigated using the keyboard instead of a mouse. However it's not possible to enable/disable the repositories. Neither Enter nor Space have any effect on the checkboxes. ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: software-properties-gtk 0.92.37.1 ProcVersionSignature: Ubuntu 3.13.0-24.47-generic 3.13.9 Uname: Linux 3.13.0-24-generic i686 ApportVersion: 2.14.1-0ubuntu3.2 Architecture: i386 CurrentDesktop: LXDE Date: Mon May 26 13:54:08 2014 PackageArchitecture: all SourcePackage: software-properties UpgradeStatus: Upgraded to trusty on 2014-05-22 (4 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/software-properties/+bug/1323285/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1390792] Re: Synaptic Other Software tab jumps/scrolls to top when a repository check box is clicked
** Tags added: bionic disco eoan xenial -- 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/1390792 Title: Synaptic Other Software tab jumps/scrolls to top when a repository check box is clicked Status in software-properties package in Ubuntu: Confirmed Status in synaptic package in Ubuntu: Confirmed Bug description: In Synaptic's Software & Updates window, clicking the check box for a repository in the Other Software tab causes the list of repositories to jump to the top of the list. The scroll position of the list is instantly lost, disorienting the user, and hiding the fact that the click did anything, until the user scrolls back down to find the item that was clicked. This is only noticeable when there are enough repositories in the list to require scrolling. Finding the clicked repository again is especially difficult when all of them look nearly identical, as is the case when they're all PPAs with no comment string. (Every item in the list is just a long URL that looks very similar to the others.) It's even worse when there are both package and source URLs for each repo. This is especially problematic when updating the repo URLs after a distribution upgrade, because it's a very repetitive task, and the scroll window jumps and loses its place every single time. Ubuntu 14.04.1 LTS synaptic 0.81.1ubuntu1 amd64 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/software-properties/+bug/1390792/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1261945] Re: When editing PPAs, software-properties sometimes scrolls back to the top of the list
Got this bug on 19.10 with dozen PPAs added. ** Tags added: bionic disco eoan xenial -- 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/1261945 Title: When editing PPAs, software-properties sometimes scrolls back to the top of the list Status in software-properties package in Ubuntu: Confirmed Bug description: I use software-properties quite frequently, and particularly extensive use when I upgrade my system (as I have recently done). Whilst working my way through the long list of PPA who's names have been branded with Canonical's infernal 'disabled during upgrade to saucy' appendage, I've noticed that every so often (quite frequently, but not always) when I edit a PPA somewhere down the list, I'll be returned to software-properties main dialogue scrolled back to the top of the list. This, as I am sure you can imagine, is quite annoying, especially when working ones way through a long list of PPA, having to find your way back to where you were, and positively infuriating when coupled with the effects of bug 1261942. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/software-properties/+bug/1261945/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
