[Touch-packages] [Bug 1918970] Re: Unable to netboot Ubuntu 18.04 and older on an IBM Z DPM Partition - no manual nor automatic qeth device configuration
** Tags added: bot-stop-nagging -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to initramfs-tools in Ubuntu. https://bugs.launchpad.net/bugs/1918970 Title: Unable to netboot Ubuntu 18.04 and older on an IBM Z DPM Partition - no manual nor automatic qeth device configuration Status in MAAS: New Status in Ubuntu on IBM z Systems: New Status in initramfs-tools package in Ubuntu: New Status in linux package in Ubuntu: Incomplete Status in s390-tools package in Ubuntu: New Bug description: I tried to deploy Ubuntu 18.04 with the GA-18.04 kernel on an IBM Z14 DPM Partition. The initrd fails to bring up network and thus fails to boot in MAAS. I haven't tried older versions of Ubuntu but suspect they also have the same bug. mount: mounting /dev on /root/dev failed: No such file or directory done. mount: mounting /run on /root/run failed: No such file or directory run-init: current directory on the same filesystem as the root: error 0 Target filesystem doesn't have requested /sbin/init. run-init: current directory on the same filesystem as the root: error 0 run-init: current directory on the same filesystem as the root: error 0 run-init: current directory on the same filesystem as the root: error 0 run-init: current directory on the same filesystem as the root: error 0 run-init: current directory on the same filesystem as the root: error 0 chvt: can't open console No init found. Try passing init= bootarg. Couldn't get a file descriptor referring to the console /scripts/panic/console_setup: line 133: can't create /dev/tty1: No such device o r address /scripts/panic/console_setup: line 1: can't open /dev/tty1: No such device or ad dress /scripts/panic/console_setup: line 1: can't create /dev/tty2: No such device or address /scripts/panic/console_setup: line 1: can't open /dev/tty2: No such device or ad dress /scripts/panic/console_setup: line 1: can't create /dev/tty3: No such device or address /scripts/panic/console_setup: line 1: can't open /dev/tty3: No such device or ad dress /scripts/panic/console_setup: line 1: can't create /dev/tty4: No such device or address /scripts/panic/console_setup: line 1: can't open /dev/tty4: No such device or ad dress /scripts/panic/console_setup: line 1: can't create /dev/tty5: No such device or address /scripts/panic/console_setup: line 1: can't open /dev/tty5: No such device or ad dress /scripts/panic/console_setup: line 1: can't create /dev/tty6: No such device or address /scripts/panic/console_setup: line 1: can't open /dev/tty6: No such device or ad dress BusyBox v1.27.2 (Ubuntu 1:1.27.2-2ubuntu3.3) built-in shell (ash) Enter 'help' for a list of built-in commands. (initramfs) [6n [ 78.114530] random: crng init done [ 78.114538] random: 7 urandom warning(s) missed due to ratelimiting To manage notifications about this bug go to: https://bugs.launchpad.net/maas/+bug/1918970/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1607680] Re: High precision touchpad scrolling doesn't work in GTK-on-Mir
Launchpad has imported 4 comments from the remote bug at https://bugzilla.gnome.org/show_bug.cgi?id=769554. If you reply to an imported comment from within Launchpad, your comment will be sent to the remote bug automatically. Read more about Launchpad's inter-bugtracker facilities at https://help.launchpad.net/InterBugTracking. On 2016-08-05T12:41:10+00:00 Andreas Pokorny wrote: Created attachment 332799 Do not filter out small touchpad scroll motions When scrolling with a touchpad the left-right direction seems to be wrong, and it seems to be less smooth than with X11 or qt-mir clients. This is probably because mir provides scroll motion in rotary ticks - which are usually been translated as 15-times larger than touchpad motion units. The attached patch resolves the problem. Reply at: https://bugs.launchpad.net/ubuntu/+source/gtk+3.0/+bug/1607680/comments/2 On 2016-08-12T14:50:46+00:00 Fakey wrote: Review of attachment 332799: Looks OK, can we leave the -delta_y alone though? ::: gdk/mir/gdkmireventsource.c @@ +198,3 @@ event->scroll.direction = GDK_SCROLL_SMOOTH; + event->scroll.delta_x = delta_x; + event->scroll.delta_y = delta_y; Yes, for me this fixes the horizontal smooth scrolling, but breaks the vertical smooth scrolling. I guess there's some disparity between the vertical scroll direction in Mir and GTK+? Can we undo the second change here? Reply at: https://bugs.launchpad.net/ubuntu/+source/gtk+3.0/+bug/1607680/comments/3 On 2016-08-12T15:31:08+00:00 Andreas Pokorny wrote: (In reply to William Hua from comment #1) > Review of attachment 332799 [details] [review]: > > Looks OK, can we leave the -delta_y alone though? > > ::: gdk/mir/gdkmireventsource.c > @@ +198,3 @@ >event->scroll.direction = GDK_SCROLL_SMOOTH; > + event->scroll.delta_x = delta_x; > + event->scroll.delta_y = delta_y; > > Yes, for me this fixes the horizontal smooth scrolling, but breaks the > vertical smooth scrolling. I guess there's some disparity between the > vertical scroll direction in Mir and GTK+? Can we undo the second change > here? I do not know what direction is positive or negative. A user can customize that via server side options. We can keep it -delta_y. I just hope this will be in the end common across toolktis. Reply at: https://bugs.launchpad.net/ubuntu/+source/gtk+3.0/+bug/1607680/comments/4 On 2016-08-13T23:32:23+00:00 Andreas Pokorny wrote: Created attachment 333250 [PATCH] Do not filter out small scroll event fractions Reply at: https://bugs.launchpad.net/ubuntu/+source/gtk+3.0/+bug/1607680/comments/5 ** Changed in: gtk Status: Unknown => Fix Released ** Changed in: gtk Importance: Unknown => Medium -- 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/1607680 Title: High precision touchpad scrolling doesn't work in GTK-on-Mir Status in GTK+: Fix Released Status in gtk+3.0 package in Ubuntu: In Progress Bug description: Smooth touchpad scrolling doesn't work in GTK-on-Mir Touchpad scrolling is instead jumpy and unresponsive. gdk/mir/gdkmireventsource.c ignores smaller scroll motion values even though the underlying gdk interface would support small floating point scroll motions To manage notifications about this bug go to: https://bugs.launchpad.net/gtk/+bug/1607680/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1915870] Re: gnome-shell/gnome-session-check-accelerated-gl-helper crashed with SIGSEGV in cso_destroy_context() [r300_dri.so]
Yeah there is evidence of 20.04 being affected. Let's request a fix for that... https://errors.ubuntu.com/problem/c76f314823adbacaa005aa034510a367c71cfba9 https://errors.ubuntu.com/problem/35c53f75f68baaccadc33449627e02b9baa88af8 https://errors.ubuntu.com/problem/f6956d240018bd2fb8295a12d0fed40384d8d56a https://errors.ubuntu.com/problem/c23f346a06424ffbecab46c825c5925b0193b535 https://errors.ubuntu.com/problem/79ac9a1b5b3a80e017cee6d476dbb6eae884eda6 ** Tags added: rls-ff-incoming -- 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/1915870 Title: gnome-shell/gnome-session-check-accelerated-gl-helper crashed with SIGSEGV in cso_destroy_context() [r300_dri.so] Status in Mesa: Unknown Status in mesa package in Ubuntu: Fix Released Status in mesa package in Fedora: Confirmed Bug description: Graphical user interface is not coming up upon start. Only SSH is possible. lsb_release -rd: Description: Ubuntu 20.10 Release: 20.10 dmesg: [ 11.985343] gnome-session-c[1013]: segfault at 0 ip sp 7fff7679ca48 error 14 in gnome-session-check-accelerated-gl-helper[56020e238000+2000] [ 11.985352] Code: Unable to access opcode bytes at RIP 0xffd6. [ 14.216117] gnome-shell[1094]: segfault at 0 ip sp 7ffeddff9f88 error 14 [ 14.216122] Code: Unable to access opcode bytes at RIP 0xffd6. [ 15.316292] gnome-shell[1109]: segfault at 0 ip sp 7ffc70716198 error 14 [ 15.316297] Code: Unable to access opcode bytes at RIP 0xffd6. apt-cache policy: gnome-session: Installed: (none) Candidate: 3.38.0-1ubuntu1 Version table: 3.38.0-1ubuntu1 500 500 http://de.archive.ubuntu.com/ubuntu groovy/main amd64 Packages 500 http://de.archive.ubuntu.com/ubuntu groovy/main i386 Packages gnome-session-bin: Installed: 3.38.0-1ubuntu1 Candidate: 3.38.0-1ubuntu1 Version table: *** 3.38.0-1ubuntu1 500 500 http://de.archive.ubuntu.com/ubuntu groovy/main amd64 Packages 100 /var/lib/dpkg/status gnome-session-common: Installed: 3.38.0-1ubuntu1 Candidate: 3.38.0-1ubuntu1 Version table: *** 3.38.0-1ubuntu1 500 500 http://de.archive.ubuntu.com/ubuntu groovy/main amd64 Packages 500 http://de.archive.ubuntu.com/ubuntu groovy/main i386 Packages 100 /var/lib/dpkg/status /var/crash: see attachment To manage notifications about this bug go to: https://bugs.launchpad.net/mesa/+bug/1915870/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1915870] Re: gnome-shell/gnome-session-check-accelerated-gl-helper crashed with SIGSEGV in cso_destroy_context() [r300_dri.so]
When will mesa (21.0.0-1) be available for ubuntu 20.04? if it be -- 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/1915870 Title: gnome-shell/gnome-session-check-accelerated-gl-helper crashed with SIGSEGV in cso_destroy_context() [r300_dri.so] Status in Mesa: Unknown Status in mesa package in Ubuntu: Fix Released Status in mesa package in Fedora: Confirmed Bug description: Graphical user interface is not coming up upon start. Only SSH is possible. lsb_release -rd: Description: Ubuntu 20.10 Release: 20.10 dmesg: [ 11.985343] gnome-session-c[1013]: segfault at 0 ip sp 7fff7679ca48 error 14 in gnome-session-check-accelerated-gl-helper[56020e238000+2000] [ 11.985352] Code: Unable to access opcode bytes at RIP 0xffd6. [ 14.216117] gnome-shell[1094]: segfault at 0 ip sp 7ffeddff9f88 error 14 [ 14.216122] Code: Unable to access opcode bytes at RIP 0xffd6. [ 15.316292] gnome-shell[1109]: segfault at 0 ip sp 7ffc70716198 error 14 [ 15.316297] Code: Unable to access opcode bytes at RIP 0xffd6. apt-cache policy: gnome-session: Installed: (none) Candidate: 3.38.0-1ubuntu1 Version table: 3.38.0-1ubuntu1 500 500 http://de.archive.ubuntu.com/ubuntu groovy/main amd64 Packages 500 http://de.archive.ubuntu.com/ubuntu groovy/main i386 Packages gnome-session-bin: Installed: 3.38.0-1ubuntu1 Candidate: 3.38.0-1ubuntu1 Version table: *** 3.38.0-1ubuntu1 500 500 http://de.archive.ubuntu.com/ubuntu groovy/main amd64 Packages 100 /var/lib/dpkg/status gnome-session-common: Installed: 3.38.0-1ubuntu1 Candidate: 3.38.0-1ubuntu1 Version table: *** 3.38.0-1ubuntu1 500 500 http://de.archive.ubuntu.com/ubuntu groovy/main amd64 Packages 500 http://de.archive.ubuntu.com/ubuntu groovy/main i386 Packages 100 /var/lib/dpkg/status /var/crash: see attachment To manage notifications about this bug go to: https://bugs.launchpad.net/mesa/+bug/1915870/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1921829] Re: [rtl8821ce] Bluetooth not working
I can't seem to reproduce the problem in Ubuntu 21.04 here so it seems to be machine-specific. And indeed the log in comment #5 is showing some kernel crashes in rtl8821ce that might be relevant. ** Summary changed: - Bluetooth not working + [rtl8821ce] Bluetooth not working ** Package changed: bluez (Ubuntu) => linux (Ubuntu) -- 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/1921829 Title: [rtl8821ce] [10ec:c821] Bluetooth not working Status in linux package in Ubuntu: Incomplete Bug description: It's impossible to activate the Bluetooth, putting the switch to ON does nothing, when re-entering the Bluetooth settings it's still OFF. ProblemType: Bug DistroRelease: Ubuntu 21.04 Package: gnome-control-center 1:3.38.5-1ubuntu1 ProcVersionSignature: Ubuntu 5.11.0-11.12-generic 5.11.0 Uname: Linux 5.11.0-11-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu61 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: ubuntu:GNOME Date: Tue Mar 30 08:11:43 2021 ExecutablePath: /usr/bin/gnome-control-center InstallationDate: Installed on 2020-09-15 (195 days ago) InstallationMedia: Ubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731) SourcePackage: gnome-control-center UpgradeStatus: Upgraded to hirsute on 2021-03-19 (10 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1921829/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1607680] Re: High precision touchpad scrolling doesn't work in GTK-on-Mir
** Bug watch added: bugzilla.gnome.org/ #769554 https://bugzilla.gnome.org/show_bug.cgi?id=769554 ** Changed in: gtk Importance: Medium => Unknown ** Changed in: gtk Status: Fix Released => Unknown ** Changed in: gtk Remote watch: GNOME Bug Tracker #769554 => bugzilla.gnome.org/ #769554 -- 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/1607680 Title: High precision touchpad scrolling doesn't work in GTK-on-Mir Status in GTK+: Unknown Status in gtk+3.0 package in Ubuntu: In Progress Bug description: Smooth touchpad scrolling doesn't work in GTK-on-Mir Touchpad scrolling is instead jumpy and unresponsive. gdk/mir/gdkmireventsource.c ignores smaller scroll motion values even though the underlying gdk interface would support small floating point scroll motions To manage notifications about this bug go to: https://bugs.launchpad.net/gtk/+bug/1607680/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1922047] Re: Touchpad scrolling is 1.5x faster on Wayland than on X11
I wonder if this relates to https://bugzilla.mozilla.org/show_bug.cgi?id=1610477 ... ** Bug watch added: Mozilla Bugzilla #1610477 https://bugzilla.mozilla.org/show_bug.cgi?id=1610477 ** Also affects: mutter via https://gitlab.gnome.org/GNOME/mutter/-/issues/1731 Importance: Unknown Status: Unknown ** No longer affects: gnome-shell (Ubuntu) ** Also affects: gtk+3.0 (Ubuntu) Importance: Undecided Status: New ** Bug watch added: gitlab.gnome.org/GNOME/gtk/-/issues #1308 https://gitlab.gnome.org/GNOME/gtk/-/issues/1308 ** Bug watch added: gitlab.gnome.org/GNOME/gtk/-/issues #3631 https://gitlab.gnome.org/GNOME/gtk/-/issues/3631 -- 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/1922047 Title: Touchpad scrolling is 1.5x faster on Wayland than on X11 Status in Mutter: Unknown Status in gtk+3.0 package in Ubuntu: New Status in mutter package in Ubuntu: New Bug description: This is an issue which has troubled me for a while. Anecdotally, scrolling feels way too fast in GNOME on Wayland compared to on X11. I finally tested it semi-scientifically, and it seems like GNOME on Wayland scrolls almost exactly 1.5x faster than GNOME on X11. I tested this by testing how many lines are scrolled from a full two- finger touchpad swipe from the bottom of my touchpad to the top of my touchpad, and logged a few attempts in both X and Wayland. I kept track of the results in this spreadsheet: https://docs.google.com/spreadsheets/d/17EaBM5Pgt7GdnnzcN2Vchk4kfT7IZ6i4qZ0zpVRGLhc/edit?usp=sharing I scrolled in one of my own GTK applications (https://github.com/mortie/lograt) because it lets me easily see how many lines I scrolled. Attach is a video of one full scroll on X11 and one full scroll on Wayland. This testing was performed on a Dell XPS 13 9343, but I've also used Ubuntu on a Dell XPS 9575 where GNOME Wayland scrolling also feels way too fast. I don't have other hardware to test on. This has been an issue on both Ubuntu 20.10 and Ubuntu 21.04. ProblemType: Bug DistroRelease: Ubuntu 21.04 Package: gnome-shell 3.38.4-1ubuntu1 ProcVersionSignature: Ubuntu 5.11.0-13.14-generic 5.11.7 Uname: Linux 5.11.0-13-generic x86_64 ApportVersion: 2.20.11-0ubuntu61 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: ubuntu:GNOME Date: Wed Mar 31 11:44:04 2021 DisplayManager: gdm3 InstallationDate: Installed on 2019-11-21 (495 days ago) InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017) RelatedPackageVersions: mutter-common 3.38.4-1ubuntu1 SourcePackage: gnome-shell UpgradeStatus: Upgraded to hirsute on 2021-03-16 (14 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/mutter/+bug/1922047/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1922047] Re: Touchpad scrolling is 1.5x faster on Wayland than on X11
GTK in general (not just Wayland) does have poor touchpad scrolling. That's being tracked in: https://gitlab.gnome.org/GNOME/gtk/-/issues/1308 https://gitlab.gnome.org/GNOME/gtk/-/issues/3631 As for Wayland being faster than X11, I wonder if it's related to: https://bugzilla.mozilla.org/show_bug.cgi?id=1610477 -- 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/1922047 Title: Touchpad scrolling is 1.5x faster on Wayland than on X11 Status in Mutter: Unknown Status in gtk+3.0 package in Ubuntu: New Status in mutter package in Ubuntu: New Bug description: This is an issue which has troubled me for a while. Anecdotally, scrolling feels way too fast in GNOME on Wayland compared to on X11. I finally tested it semi-scientifically, and it seems like GNOME on Wayland scrolls almost exactly 1.5x faster than GNOME on X11. I tested this by testing how many lines are scrolled from a full two- finger touchpad swipe from the bottom of my touchpad to the top of my touchpad, and logged a few attempts in both X and Wayland. I kept track of the results in this spreadsheet: https://docs.google.com/spreadsheets/d/17EaBM5Pgt7GdnnzcN2Vchk4kfT7IZ6i4qZ0zpVRGLhc/edit?usp=sharing I scrolled in one of my own GTK applications (https://github.com/mortie/lograt) because it lets me easily see how many lines I scrolled. Attach is a video of one full scroll on X11 and one full scroll on Wayland. This testing was performed on a Dell XPS 13 9343, but I've also used Ubuntu on a Dell XPS 9575 where GNOME Wayland scrolling also feels way too fast. I don't have other hardware to test on. This has been an issue on both Ubuntu 20.10 and Ubuntu 21.04. ProblemType: Bug DistroRelease: Ubuntu 21.04 Package: gnome-shell 3.38.4-1ubuntu1 ProcVersionSignature: Ubuntu 5.11.0-13.14-generic 5.11.7 Uname: Linux 5.11.0-13-generic x86_64 ApportVersion: 2.20.11-0ubuntu61 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: ubuntu:GNOME Date: Wed Mar 31 11:44:04 2021 DisplayManager: gdm3 InstallationDate: Installed on 2019-11-21 (495 days ago) InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017) RelatedPackageVersions: mutter-common 3.38.4-1ubuntu1 SourcePackage: gnome-shell UpgradeStatus: Upgraded to hirsute on 2021-03-16 (14 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/mutter/+bug/1922047/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1873895] Re: Regression: block staircase display with side-by-side monitors of different pixel widths
Fixed in Xfwm4 4.14.2 ** Also affects: libxcb (Ubuntu Focal) Importance: Undecided Status: New ** Also affects: xfwm4 (Ubuntu Focal) Importance: Undecided Status: New ** Also affects: xserver-xorg-video-amdgpu (Ubuntu Focal) Importance: Undecided Status: New ** Also affects: libxcb (Ubuntu Groovy) Importance: Undecided Status: New ** Also affects: xfwm4 (Ubuntu Groovy) Importance: Undecided Status: New ** Also affects: xserver-xorg-video-amdgpu (Ubuntu Groovy) Importance: Undecided Status: New ** Changed in: xfwm4 (Ubuntu Groovy) Status: New => Fix Released -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to libxcb in Ubuntu. https://bugs.launchpad.net/bugs/1873895 Title: Regression: block staircase display with side-by-side monitors of different pixel widths Status in Linux: Unknown Status in libxcb package in Ubuntu: Confirmed Status in xfwm4 package in Ubuntu: Confirmed Status in xserver-xorg-video-amdgpu package in Ubuntu: Confirmed Status in libxcb source package in Focal: New Status in xfwm4 source package in Focal: New Status in xserver-xorg-video-amdgpu source package in Focal: New Status in libxcb source package in Groovy: New Status in xfwm4 source package in Groovy: Fix Released Status in xserver-xorg-video-amdgpu source package in Groovy: New Bug description: Update based on further research. This only happens when the secondary external display is operating at a different pixel width to the internal. In this case eDP is 1920x1080 whereas the external HDMI-A-0 is natively 1680x1050. It is caused by xfwm4's recent switch from using glx to xpresent for AMD GPUs. The underlying bug is in the AMD driver. I was able to reproduce on an external 1920x1200 display only when it was set to a non-native 1680x1050 resolution. --- Two identical Lenovo E495 laptops with 20.04 installed. The problem occurred initially on the laptop that is having package upgrades applied regularly. With dual monitors and the external monitor placed left or right the display has a blocked staircase effect shown in the attached photograph, and seems related to https://gitlab.freedesktop.org/xorg/driver/xf86-video- amdgpu/-/issues/10 More detailed investigation suggests it only happens when the X coordinate of the two monitors is different. The symptom looks like an off-by-one error because it appears as if the display is divided into, say, 10 rows and 15 columns but the first row has 16 'columns' worth of blocks on it and so wraps to the beginning of the 2nd row, and so on. On the laptop without package upgrades being applied this didn't happen. So I upgraded it (314 packages) and restarted and it too sees the same problem. I suspected libxcomposite1 and downgraded it to 1:0.4.5-0ubuntu1 but that didn't solve it. I now suspect libxcb but so far haven't been able to prove it. --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu27 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CasperMD5CheckResult: skip CompositorRunning: None CurrentDesktop: XFCE DistUpgraded: Fresh install DistroCodename: focal DistroRelease: Ubuntu 20.04 DistroVariant: ubuntu GraphicsCard: Advanced Micro Devices, Inc. [AMD/ATI] Picasso [1002:15d8] (rev c1) (prog-if 00 [VGA controller]) Subsystem: Lenovo ThinkPad E595 [17aa:5124] InstallationDate: Installed on 2020-04-08 (11 days ago) InstallationMedia: Xubuntu 20.04 LTS "Focal Fossa" - Beta amd64 (20200408) MachineType: LENOVO 20NECTO1WW Package: xserver-xorg-video-amdgpu 19.1.0-1 PackageArchitecture: amd64 ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.4.0-21-generic root=/dev/mapper/ELLOE000-rootfs ro acpi_osi=! "acpi_osi=Windows 2016" quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 5.4.0-21.25-generic 5.4.27 Tags: focal ubuntu ubuntu Uname: Linux 5.4.0-21-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip libvirt lp lpadmin lxd plugdev sambashare sudo users _MarkForUpload: True dmi.bios.date: 12/23/2019 dmi.bios.vendor: LENOVO dmi.bios.version: R11ET32W (1.12 ) dmi.board.asset.tag: Not Available dmi.board.name: 20NECTO1WW dmi.board.vendor: LENOVO dmi.board.version: Not Defined dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: None dmi.modalias: dmi:bvnLENOVO:bvrR11ET32W(1.12):bd12/23/2019:svnLENOVO:pn20NECTO1WW:pvrThinkPadE495:rvnLENOVO:rn20NECTO1WW:rvrNotDefined:cvnLENOVO:ct10:cvrNone: dmi.product.family: ThinkPad E495 dmi.product.name: 20NECTO1WW dmi.product.sku: LENOVO_MT_20NE_BU_Think_FM_ThinkPad E495 dmi.product.version: ThinkPad E495 dmi.sys.vendor: LENOVO version.compiz: compiz N/A version.libdrm2: libdrm2
[Touch-packages] [Bug 1912331] Re: Many interfaces lead to "kernel receive buffer overrun"
Increasing the ReceiveBuffer=128M or ReceiveBuffer=512M didn't solve the problem for me. I'm interested to systemd patched backported to focal too. See my config files. ** Attachment added: "config files" https://bugs.launchpad.net/systemd/+bug/1912331/+attachment/5482905/+files/config.zip -- 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/1912331 Title: Many interfaces lead to "kernel receive buffer overrun" Status in systemd: Fix Released Status in systemd package in Ubuntu: Fix Released Status in systemd source package in Focal: Invalid Status in systemd source package in Groovy: Fix Released Bug description: This is about a systemd-networkd bug, described here: https://github.com/systemd/systemd/issues/14417 There's a patch available: https://github.com/systemd/systemd/pull/16982 Can this be backported to Focal? To manage notifications about this bug go to: https://bugs.launchpad.net/systemd/+bug/1912331/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1792231] Re: openssh-client: 'DISPLAY "(null)" invalid; disabling X11 forwarding'
14.04 has transitioned off Standard Support to Extended Security Maintenance (https://ubuntu.com/blog/ubuntu-14-04-trusty-tahr) as of April 2019. Under ESM the focus for changes is more on security vulnerabilities in non-desktop packages. Since this issue sounds to be more on the cosmetic side, I don't think this fits in the ESM update policies. But, I'll attach the patch for future reference. ** Patch added: "avoid_ugly_display_null_invalid_with_x11.patch" https://bugs.launchpad.net/ubuntu/+source/openssh/+bug/1792231/+attachment/5482868/+files/avoid_ugly_display_null_invalid_with_x11.patch ** Changed in: openssh (Ubuntu Trusty) Status: Triaged => Won't Fix ** Tags removed: server-next -- 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/1792231 Title: openssh-client: 'DISPLAY "(null)" invalid; disabling X11 forwarding' Status in openssh package in Ubuntu: Fix Released Status in openssh source package in Trusty: Won't Fix Status in openssh package in Debian: Fix Released Bug description: affects ubuntu/openssh Hi, This bug is present in openssh in ubuntu trusty, I haven't tested other releases. When X11 forwarding is enabled (via ssh_config, or via -X), but no DISPLAY is available, ssh client produces this warning: DISPLAY "(null)" invalid; disabling X11 forwarding root@ubuntu-trusty:/# unset DISPLAY ; ssh -X ubuntu@localhost 'dpkg -l openssh-client | grep ii' ubuntu@localhost's password: DISPLAY "(null)" invalid; disabling X11 forwarding ii openssh-client 1:6.6p1-2ubuntu2.10 amd64secure shell (SSH) client, for secure access to remote machines The bug was introduced by the changes to fix CVE-2016-1908. This upstream change fixes it: https://anongit.mindrot.org/openssh.git/commit/?id=5658ef2501e785fbbdf5de2dc33b1ff7a4dca73a See https://bugs.debian.org/908652 Cheers, -- S To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/openssh/+bug/1792231/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1922130] [NEW] Request addition of Fedora / Redhat "sftp-force-permissions" patch
Public bug reported: Fedora / Redhat ships openssh with a patch which adds "-m force permission" flag to sftp-server. This is quite a common feature request / support request on the various stackexchange sites - https://superuser.com/questions/332284/in-sftp- how-to-set-the-default-permission-for-all-files-in-a-folder You will see that someone has answered "add -m" there which is indeed the simplest answer by a distance but unfortunately it's a non standard patch: https://src.fedoraproject.org/rpms/openssh/blob/f34/f/openssh-6.7p1 -sftp-force-permission.patch This I think should supersede #563216 because they have been shipping this in production presumably since at least 2015 (I see it in fedora 22 branch), so it is a known stable patch compared to the one suggested there. ** Affects: openssh (Ubuntu) Importance: Undecided Status: New -- 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/1922130 Title: Request addition of Fedora / Redhat "sftp-force-permissions" patch Status in openssh package in Ubuntu: New Bug description: Fedora / Redhat ships openssh with a patch which adds "-m force permission" flag to sftp-server. This is quite a common feature request / support request on the various stackexchange sites - https://superuser.com/questions/332284 /in-sftp-how-to-set-the-default-permission-for-all-files-in-a-folder You will see that someone has answered "add -m" there which is indeed the simplest answer by a distance but unfortunately it's a non standard patch: https://src.fedoraproject.org/rpms/openssh/blob/f34/f/openssh-6.7p1 -sftp-force-permission.patch This I think should supersede #563216 because they have been shipping this in production presumably since at least 2015 (I see it in fedora 22 branch), so it is a known stable patch compared to the one suggested there. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/openssh/+bug/1922130/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1481804] Re: LightDM's guest-account script should disable screen lock universally for guest sessions
You are welcome Gunner! You are right about the guest feature being deprecated. I stopped using the guest feature soon after filing the bug report. -- 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/1481804 Title: LightDM's guest-account script should disable screen lock universally for guest sessions Status in lightdm package in Ubuntu: Fix Released Bug description: Is it feasible to include in /usr/sbin/guest-account script some commands to disable screen lock for guest sessions? It should include several commands, depending on Ubuntu flavour. Examples: Ubuntu MATE (uses mate-screensaver) gsettings set org.mate.screensaver lock-enabled false Xubuntu and others (use light-locker) gsettings set apps.light-locker light-locker-enabled false gsettings set apps.light-locker late-locking false gsettings set apps.light-locker lock-on-lid false gsettings set apps.light-locker lock-on-suspend false To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/lightdm/+bug/1481804/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1481804] Re: LightDM's guest-account script should disable screen lock universally for guest sessions
** Tags added: bionic focal groovy hirsute -- 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/1481804 Title: LightDM's guest-account script should disable screen lock universally for guest sessions Status in lightdm package in Ubuntu: Fix Released Bug description: Is it feasible to include in /usr/sbin/guest-account script some commands to disable screen lock for guest sessions? It should include several commands, depending on Ubuntu flavour. Examples: Ubuntu MATE (uses mate-screensaver) gsettings set org.mate.screensaver lock-enabled false Xubuntu and others (use light-locker) gsettings set apps.light-locker light-locker-enabled false gsettings set apps.light-locker late-locking false gsettings set apps.light-locker lock-on-lid false gsettings set apps.light-locker lock-on-suspend false To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/lightdm/+bug/1481804/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1775088] Re: Ubuntu Mate guest session locked out when switching from another account
** Tags added: focal groovy hirsute -- 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/1775088 Title: Ubuntu Mate guest session locked out when switching from another account Status in Ubuntu MATE: New Status in lightdm package in Ubuntu: Confirmed Bug description: ATTN: Ubuntu Mate Developers Description: Ubuntu 18.04 LTS Release: 18.04 lightdm: Installed: 1.26.0-0ubuntu1 Candidate: 1.26.0-0ubuntu1 Version table: *** 1.26.0-0ubuntu1 500 500 http://us.archive.ubuntu.com/ubuntu bionic/universe amd64 Packages 100 /var/lib/dpkg/status In Ubuntu Mate 18.04 LTS LightDM, I created a file in /etc/lightdm/lightdm.conf, with the line: allow-guest=true This allows me to log into a guest session. The issue is when I try to switch between the guest session and a normal session and back. Switching from guest session to the normal user session is fine. LightDM asks for the normal user password. However, when I try to switch from the normal user to back to the guest session I am asked for password as well. This is the problem as the guest session has no known password. The unlock window has a 'Switch User" button along with Cancel, etc. Clicking the "Switch User" button takes me to the standard LightDM screen. There I can select from the normal user and the guest. However, selecting guest here opens a new guest session, and does not take me back to the guest session already open. This looks like an old bug https://bugs.launchpad.net/bugs/1481804 ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: lightdm 1.26.0-0ubuntu1 ProcVersionSignature: Ubuntu 4.15.0-22.24-generic 4.15.17 Uname: Linux 4.15.0-22-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.1 Architecture: amd64 CurrentDesktop: MATE Date: Mon Jun 4 17:46:33 2018 InstallationDate: Installed on 2018-05-31 (4 days ago) InstallationMedia: Ubuntu-MATE 18.04 LTS "Bionic Beaver" - Release amd64 (20180426) SourcePackage: lightdm UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-mate/+bug/1775088/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1481804] Re: LightDM's guest-account script should disable screen lock universally for guest sessions
Thanks Sushenjit. I just added a comment on the other bug. -- 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/1481804 Title: LightDM's guest-account script should disable screen lock universally for guest sessions Status in lightdm package in Ubuntu: Fix Released Bug description: Is it feasible to include in /usr/sbin/guest-account script some commands to disable screen lock for guest sessions? It should include several commands, depending on Ubuntu flavour. Examples: Ubuntu MATE (uses mate-screensaver) gsettings set org.mate.screensaver lock-enabled false Xubuntu and others (use light-locker) gsettings set apps.light-locker light-locker-enabled false gsettings set apps.light-locker late-locking false gsettings set apps.light-locker lock-on-lid false gsettings set apps.light-locker lock-on-suspend false To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/lightdm/+bug/1481804/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1918970] Missing required logs.
This bug is missing log files that will aid in diagnosing the problem. While running an Ubuntu kernel (not a mainline or third-party kernel) please enter the following command in a terminal window: apport-collect 1918970 and then change the status of the bug to 'Confirmed'. If, due to the nature of the issue you have encountered, you are unable to run this command, please add a comment stating that fact and change the bug status to 'Confirmed'. This change has been made by an automated script, maintained by the Ubuntu Kernel Team. ** Changed in: linux (Ubuntu) Status: New => Incomplete -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to initramfs-tools in Ubuntu. https://bugs.launchpad.net/bugs/1918970 Title: Unable to netboot Ubuntu 18.04 and older on an IBM Z DPM Partition - no manual nor automatic qeth device configuration Status in MAAS: New Status in Ubuntu on IBM z Systems: New Status in initramfs-tools package in Ubuntu: New Status in linux package in Ubuntu: Incomplete Status in s390-tools package in Ubuntu: New Bug description: I tried to deploy Ubuntu 18.04 with the GA-18.04 kernel on an IBM Z14 DPM Partition. The initrd fails to bring up network and thus fails to boot in MAAS. I haven't tried older versions of Ubuntu but suspect they also have the same bug. mount: mounting /dev on /root/dev failed: No such file or directory done. mount: mounting /run on /root/run failed: No such file or directory run-init: current directory on the same filesystem as the root: error 0 Target filesystem doesn't have requested /sbin/init. run-init: current directory on the same filesystem as the root: error 0 run-init: current directory on the same filesystem as the root: error 0 run-init: current directory on the same filesystem as the root: error 0 run-init: current directory on the same filesystem as the root: error 0 run-init: current directory on the same filesystem as the root: error 0 chvt: can't open console No init found. Try passing init= bootarg. Couldn't get a file descriptor referring to the console /scripts/panic/console_setup: line 133: can't create /dev/tty1: No such device o r address /scripts/panic/console_setup: line 1: can't open /dev/tty1: No such device or ad dress /scripts/panic/console_setup: line 1: can't create /dev/tty2: No such device or address /scripts/panic/console_setup: line 1: can't open /dev/tty2: No such device or ad dress /scripts/panic/console_setup: line 1: can't create /dev/tty3: No such device or address /scripts/panic/console_setup: line 1: can't open /dev/tty3: No such device or ad dress /scripts/panic/console_setup: line 1: can't create /dev/tty4: No such device or address /scripts/panic/console_setup: line 1: can't open /dev/tty4: No such device or ad dress /scripts/panic/console_setup: line 1: can't create /dev/tty5: No such device or address /scripts/panic/console_setup: line 1: can't open /dev/tty5: No such device or ad dress /scripts/panic/console_setup: line 1: can't create /dev/tty6: No such device or address /scripts/panic/console_setup: line 1: can't open /dev/tty6: No such device or ad dress BusyBox v1.27.2 (Ubuntu 1:1.27.2-2ubuntu3.3) built-in shell (ash) Enter 'help' for a list of built-in commands. (initramfs) [6n [ 78.114530] random: crng init done [ 78.114538] random: 7 urandom warning(s) missed due to ratelimiting To manage notifications about this bug go to: https://bugs.launchpad.net/maas/+bug/1918970/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1775088] Re: Ubuntu Mate guest session locked out when switching from another account
I had a brief look at this using the latest daily build ISO for Ubuntu MATE 21.04. lightdm has code for disabling the MATE screensaver. I confirmed that it works by opening a terminal window within a guest session: $ gsettings get org.mate.screensaver lock-enabled false But I could still reproduce the issue, i.e. I switched to my regular user and then when trying to switch back to the guest session it prompted me for the non-existing password. We should keep in mind that the guest session feature is deprecated and disabled by default: https://askubuntu.com/q/915415 AFAIK nobody makes any effort any longer to make sure it keeps working when software is upgraded. ** Changed in: lightdm (Ubuntu) Importance: Undecided => Low ** Changed in: lightdm (Ubuntu) Status: New => Confirmed -- 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/1775088 Title: Ubuntu Mate guest session locked out when switching from another account Status in Ubuntu MATE: New Status in lightdm package in Ubuntu: Confirmed Bug description: ATTN: Ubuntu Mate Developers Description: Ubuntu 18.04 LTS Release: 18.04 lightdm: Installed: 1.26.0-0ubuntu1 Candidate: 1.26.0-0ubuntu1 Version table: *** 1.26.0-0ubuntu1 500 500 http://us.archive.ubuntu.com/ubuntu bionic/universe amd64 Packages 100 /var/lib/dpkg/status In Ubuntu Mate 18.04 LTS LightDM, I created a file in /etc/lightdm/lightdm.conf, with the line: allow-guest=true This allows me to log into a guest session. The issue is when I try to switch between the guest session and a normal session and back. Switching from guest session to the normal user session is fine. LightDM asks for the normal user password. However, when I try to switch from the normal user to back to the guest session I am asked for password as well. This is the problem as the guest session has no known password. The unlock window has a 'Switch User" button along with Cancel, etc. Clicking the "Switch User" button takes me to the standard LightDM screen. There I can select from the normal user and the guest. However, selecting guest here opens a new guest session, and does not take me back to the guest session already open. This looks like an old bug https://bugs.launchpad.net/bugs/1481804 ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: lightdm 1.26.0-0ubuntu1 ProcVersionSignature: Ubuntu 4.15.0-22.24-generic 4.15.17 Uname: Linux 4.15.0-22-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.1 Architecture: amd64 CurrentDesktop: MATE Date: Mon Jun 4 17:46:33 2018 InstallationDate: Installed on 2018-05-31 (4 days ago) InstallationMedia: Ubuntu-MATE 18.04 LTS "Bionic Beaver" - Release amd64 (20180426) SourcePackage: lightdm UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-mate/+bug/1775088/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1918970] Re: Unable to netboot Ubuntu 18.04 and older on an IBM Z DPM Partition - no manual nor automatic qeth device configuration
in response to comment #2) That would be indeed a valid approach (and I think we already had that once in the z13s prototype), since we run in such a situation always on a system in DPM mode, were one usually have only selected devices configured (compared to a system in PR/SM classic mode, where one often heavily shares devices). -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to initramfs-tools in Ubuntu. https://bugs.launchpad.net/bugs/1918970 Title: Unable to netboot Ubuntu 18.04 and older on an IBM Z DPM Partition - no manual nor automatic qeth device configuration Status in MAAS: New Status in Ubuntu on IBM z Systems: New Status in initramfs-tools package in Ubuntu: New Status in linux package in Ubuntu: New Status in s390-tools package in Ubuntu: New Bug description: I tried to deploy Ubuntu 18.04 with the GA-18.04 kernel on an IBM Z14 DPM Partition. The initrd fails to bring up network and thus fails to boot in MAAS. I haven't tried older versions of Ubuntu but suspect they also have the same bug. mount: mounting /dev on /root/dev failed: No such file or directory done. mount: mounting /run on /root/run failed: No such file or directory run-init: current directory on the same filesystem as the root: error 0 Target filesystem doesn't have requested /sbin/init. run-init: current directory on the same filesystem as the root: error 0 run-init: current directory on the same filesystem as the root: error 0 run-init: current directory on the same filesystem as the root: error 0 run-init: current directory on the same filesystem as the root: error 0 run-init: current directory on the same filesystem as the root: error 0 chvt: can't open console No init found. Try passing init= bootarg. Couldn't get a file descriptor referring to the console /scripts/panic/console_setup: line 133: can't create /dev/tty1: No such device o r address /scripts/panic/console_setup: line 1: can't open /dev/tty1: No such device or ad dress /scripts/panic/console_setup: line 1: can't create /dev/tty2: No such device or address /scripts/panic/console_setup: line 1: can't open /dev/tty2: No such device or ad dress /scripts/panic/console_setup: line 1: can't create /dev/tty3: No such device or address /scripts/panic/console_setup: line 1: can't open /dev/tty3: No such device or ad dress /scripts/panic/console_setup: line 1: can't create /dev/tty4: No such device or address /scripts/panic/console_setup: line 1: can't open /dev/tty4: No such device or ad dress /scripts/panic/console_setup: line 1: can't create /dev/tty5: No such device or address /scripts/panic/console_setup: line 1: can't open /dev/tty5: No such device or ad dress /scripts/panic/console_setup: line 1: can't create /dev/tty6: No such device or address /scripts/panic/console_setup: line 1: can't open /dev/tty6: No such device or ad dress BusyBox v1.27.2 (Ubuntu 1:1.27.2-2ubuntu3.3) built-in shell (ash) Enter 'help' for a list of built-in commands. (initramfs) [6n [ 78.114530] random: crng init done [ 78.114538] random: 7 urandom warning(s) missed due to ratelimiting To manage notifications about this bug go to: https://bugs.launchpad.net/maas/+bug/1918970/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1918970] Re: Unable to netboot Ubuntu 18.04 and older on an IBM Z DPM Partition - no manual nor automatic qeth device configuration
** Changed in: linux (Ubuntu) Status: Incomplete => New -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to initramfs-tools in Ubuntu. https://bugs.launchpad.net/bugs/1918970 Title: Unable to netboot Ubuntu 18.04 and older on an IBM Z DPM Partition - no manual nor automatic qeth device configuration Status in MAAS: New Status in Ubuntu on IBM z Systems: New Status in initramfs-tools package in Ubuntu: New Status in linux package in Ubuntu: New Status in s390-tools package in Ubuntu: New Bug description: I tried to deploy Ubuntu 18.04 with the GA-18.04 kernel on an IBM Z14 DPM Partition. The initrd fails to bring up network and thus fails to boot in MAAS. I haven't tried older versions of Ubuntu but suspect they also have the same bug. mount: mounting /dev on /root/dev failed: No such file or directory done. mount: mounting /run on /root/run failed: No such file or directory run-init: current directory on the same filesystem as the root: error 0 Target filesystem doesn't have requested /sbin/init. run-init: current directory on the same filesystem as the root: error 0 run-init: current directory on the same filesystem as the root: error 0 run-init: current directory on the same filesystem as the root: error 0 run-init: current directory on the same filesystem as the root: error 0 run-init: current directory on the same filesystem as the root: error 0 chvt: can't open console No init found. Try passing init= bootarg. Couldn't get a file descriptor referring to the console /scripts/panic/console_setup: line 133: can't create /dev/tty1: No such device o r address /scripts/panic/console_setup: line 1: can't open /dev/tty1: No such device or ad dress /scripts/panic/console_setup: line 1: can't create /dev/tty2: No such device or address /scripts/panic/console_setup: line 1: can't open /dev/tty2: No such device or ad dress /scripts/panic/console_setup: line 1: can't create /dev/tty3: No such device or address /scripts/panic/console_setup: line 1: can't open /dev/tty3: No such device or ad dress /scripts/panic/console_setup: line 1: can't create /dev/tty4: No such device or address /scripts/panic/console_setup: line 1: can't open /dev/tty4: No such device or ad dress /scripts/panic/console_setup: line 1: can't create /dev/tty5: No such device or address /scripts/panic/console_setup: line 1: can't open /dev/tty5: No such device or ad dress /scripts/panic/console_setup: line 1: can't create /dev/tty6: No such device or address /scripts/panic/console_setup: line 1: can't open /dev/tty6: No such device or ad dress BusyBox v1.27.2 (Ubuntu 1:1.27.2-2ubuntu3.3) built-in shell (ash) Enter 'help' for a list of built-in commands. (initramfs) [6n [ 78.114530] random: crng init done [ 78.114538] random: 7 urandom warning(s) missed due to ratelimiting To manage notifications about this bug go to: https://bugs.launchpad.net/maas/+bug/1918970/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1920640] Re: EXPKEYSIG C8CAB6595FDFF622 Ubuntu Debug Symbol Archive Automatic Signing Key (2016)
More that a week was needed for this trivial harmless fix to go through this nonsensical bureaucracy. The ubuntu update procedure is broken. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to ubuntu-keyring in Ubuntu. https://bugs.launchpad.net/bugs/1920640 Title: EXPKEYSIG C8CAB6595FDFF622 Ubuntu Debug Symbol Archive Automatic Signing Key (2016) Status in ubuntu-keyring package in Ubuntu: Fix Released Status in ubuntu-keyring source package in Bionic: Fix Released Status in ubuntu-keyring source package in Focal: Fix Released Status in ubuntu-keyring source package in Groovy: Fix Released Status in ubuntu-keyring source package in Hirsute: Fix Released Bug description: [Impact] * Cannot update apt metadata from ddebs.ubuntu.com whilst using ubuntu-dbgsym-keyring package [Test Plan] * Install ubuntu-dbgsym-keyring package * Add ddebs.ubuntu.com repository for your release * sudo apt update must be successful * Install ubuntu-dbgsym-keyring package * Install and use `apt-key list` and check that there is no expiry on the dbgsym key I.e. bad output /etc/apt/trusted.gpg.d/ubuntu-keyring-2016-dbgsym.gpg - pub rsa4096 2016-03-21 [SC] [expired: 2021-03-20] F2ED C64D C5AE E1F6 B9C6 21F0 C8CA B659 5FDF F622 uid [ expired] Ubuntu Debug Symbol Archive Automatic Signing Key (2016) Good output has no [date] in the pub line. [Where problems could occur] * At the moment the signature was bumped by one year * Meaning this issue will occur again in 2022 * Instead the key must be set to not expire & new round of SRUs issued [Other Info] * Original bug report The public key used by the debugging symbols repository /usr/share/keyrings/ubuntu-dbgsym-keyring.gpg from the package ubuntu- dbgsym-keyring expired. $ apt policy ubuntu-dbgsym-keyring ubuntu-dbgsym-keyring: Installed: 2020.02.11.2 Candidate: 2020.02.11.2 Version table: *** 2020.02.11.2 500 500 http://archive.ubuntu.com/ubuntu focal/main amd64 Packages 500 http://archive.ubuntu.com/ubuntu focal/main i386 Packages 100 /var/lib/dpkg/status $ gpg --no-default-keyring --keyring /usr/share/keyrings/ubuntu-dbgsym-keyring.gpg --list-keys /usr/share/keyrings/ubuntu-dbgsym-keyring.gpg - pub rsa4096 2016-03-21 [SC] [expired: 2021-03-20] F2EDC64DC5AEE1F6B9C621F0C8CAB6595FDFF622 uid [ expired] Ubuntu Debug Symbol Archive Automatic Signing Key (2016) Error message on "apt update": E: The repository 'http://ddebs.ubuntu.com bionic-updates Release' is not signed. N: Updating from such a repository can't be done securely, and is therefore disabled by default. N: See apt-secure(8) manpage for repository creation and user configuration details. W: GPG error: http://ddebs.ubuntu.com bionic Release: The following signatures were invalid: EXPKEYSIG C8CAB6595FDFF622 Ubuntu Debug Symbol Archive Automatic Signing Key (2016) E: The repository 'http://ddebs.ubuntu.com bionic Release' is not signed. N: Updating from such a repository can't be done securely, and is therefore disabled by default. N: See apt-secure(8) manpage for repository creation and user configuration details. W: GPG error: http://ddebs.ubuntu.com bionic-proposed Release: The following signatures were invalid: EXPKEYSIG C8CAB6595FDFF622 Ubuntu Debug Symbol Archive Automatic Signing Key (2016) E: The repository 'http://ddebs.ubuntu.com bionic-proposed Release' is not signed. N: Updating from such a repository can't be done securely, and is therefore disabled by default. N: See apt-secure(8) manpage for repository creation and user configuration details. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubuntu-keyring/+bug/1920640/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1918970] Missing required logs.
This bug is missing log files that will aid in diagnosing the problem. While running an Ubuntu kernel (not a mainline or third-party kernel) please enter the following command in a terminal window: apport-collect 1918970 and then change the status of the bug to 'Confirmed'. If, due to the nature of the issue you have encountered, you are unable to run this command, please add a comment stating that fact and change the bug status to 'Confirmed'. This change has been made by an automated script, maintained by the Ubuntu Kernel Team. ** Changed in: linux (Ubuntu) Status: New => Incomplete ** Tags added: bionic -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to initramfs-tools in Ubuntu. https://bugs.launchpad.net/bugs/1918970 Title: Unable to netboot Ubuntu 18.04 and older on an IBM Z DPM Partition - no manual nor automatic qeth device configuration Status in MAAS: New Status in Ubuntu on IBM z Systems: New Status in initramfs-tools package in Ubuntu: New Status in linux package in Ubuntu: Incomplete Status in s390-tools package in Ubuntu: New Bug description: I tried to deploy Ubuntu 18.04 with the GA-18.04 kernel on an IBM Z14 DPM Partition. The initrd fails to bring up network and thus fails to boot in MAAS. I haven't tried older versions of Ubuntu but suspect they also have the same bug. mount: mounting /dev on /root/dev failed: No such file or directory done. mount: mounting /run on /root/run failed: No such file or directory run-init: current directory on the same filesystem as the root: error 0 Target filesystem doesn't have requested /sbin/init. run-init: current directory on the same filesystem as the root: error 0 run-init: current directory on the same filesystem as the root: error 0 run-init: current directory on the same filesystem as the root: error 0 run-init: current directory on the same filesystem as the root: error 0 run-init: current directory on the same filesystem as the root: error 0 chvt: can't open console No init found. Try passing init= bootarg. Couldn't get a file descriptor referring to the console /scripts/panic/console_setup: line 133: can't create /dev/tty1: No such device o r address /scripts/panic/console_setup: line 1: can't open /dev/tty1: No such device or ad dress /scripts/panic/console_setup: line 1: can't create /dev/tty2: No such device or address /scripts/panic/console_setup: line 1: can't open /dev/tty2: No such device or ad dress /scripts/panic/console_setup: line 1: can't create /dev/tty3: No such device or address /scripts/panic/console_setup: line 1: can't open /dev/tty3: No such device or ad dress /scripts/panic/console_setup: line 1: can't create /dev/tty4: No such device or address /scripts/panic/console_setup: line 1: can't open /dev/tty4: No such device or ad dress /scripts/panic/console_setup: line 1: can't create /dev/tty5: No such device or address /scripts/panic/console_setup: line 1: can't open /dev/tty5: No such device or ad dress /scripts/panic/console_setup: line 1: can't create /dev/tty6: No such device or address /scripts/panic/console_setup: line 1: can't open /dev/tty6: No such device or ad dress BusyBox v1.27.2 (Ubuntu 1:1.27.2-2ubuntu3.3) built-in shell (ash) Enter 'help' for a list of built-in commands. (initramfs) [6n [ 78.114530] random: crng init done [ 78.114538] random: 7 urandom warning(s) missed due to ratelimiting To manage notifications about this bug go to: https://bugs.launchpad.net/maas/+bug/1918970/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1918970] Re: Unable to netboot Ubuntu 18.04 and older on an IBM Z DPM Partition - no manual nor automatic qeth device configuration
Alternative to all of the above, you could choose to "enable all the devices" hack on 18.04. Aka if the MAAS initrd includes a script to do `chzdev -e --all` by default on 18.04. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to initramfs-tools in Ubuntu. https://bugs.launchpad.net/bugs/1918970 Title: Unable to netboot Ubuntu 18.04 and older on an IBM Z DPM Partition - no manual nor automatic qeth device configuration Status in MAAS: New Status in Ubuntu on IBM z Systems: New Status in initramfs-tools package in Ubuntu: New Status in linux package in Ubuntu: New Status in s390-tools package in Ubuntu: New Bug description: I tried to deploy Ubuntu 18.04 with the GA-18.04 kernel on an IBM Z14 DPM Partition. The initrd fails to bring up network and thus fails to boot in MAAS. I haven't tried older versions of Ubuntu but suspect they also have the same bug. mount: mounting /dev on /root/dev failed: No such file or directory done. mount: mounting /run on /root/run failed: No such file or directory run-init: current directory on the same filesystem as the root: error 0 Target filesystem doesn't have requested /sbin/init. run-init: current directory on the same filesystem as the root: error 0 run-init: current directory on the same filesystem as the root: error 0 run-init: current directory on the same filesystem as the root: error 0 run-init: current directory on the same filesystem as the root: error 0 run-init: current directory on the same filesystem as the root: error 0 chvt: can't open console No init found. Try passing init= bootarg. Couldn't get a file descriptor referring to the console /scripts/panic/console_setup: line 133: can't create /dev/tty1: No such device o r address /scripts/panic/console_setup: line 1: can't open /dev/tty1: No such device or ad dress /scripts/panic/console_setup: line 1: can't create /dev/tty2: No such device or address /scripts/panic/console_setup: line 1: can't open /dev/tty2: No such device or ad dress /scripts/panic/console_setup: line 1: can't create /dev/tty3: No such device or address /scripts/panic/console_setup: line 1: can't open /dev/tty3: No such device or ad dress /scripts/panic/console_setup: line 1: can't create /dev/tty4: No such device or address /scripts/panic/console_setup: line 1: can't open /dev/tty4: No such device or ad dress /scripts/panic/console_setup: line 1: can't create /dev/tty5: No such device or address /scripts/panic/console_setup: line 1: can't open /dev/tty5: No such device or ad dress /scripts/panic/console_setup: line 1: can't create /dev/tty6: No such device or address /scripts/panic/console_setup: line 1: can't open /dev/tty6: No such device or ad dress BusyBox v1.27.2 (Ubuntu 1:1.27.2-2ubuntu3.3) built-in shell (ash) Enter 'help' for a list of built-in commands. (initramfs) [6n [ 78.114530] random: crng init done [ 78.114538] random: 7 urandom warning(s) missed due to ratelimiting To manage notifications about this bug go to: https://bugs.launchpad.net/maas/+bug/1918970/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1918970] Re: Unable to boot Ubuntu 18.04 and older on an IBM Z DPM Partition
In https://launchpad.net/ubuntu/+source/initramfs-tools/0.133ubuntu3 in eoan+ manual chzdev -e got added to activate qeth devices, if they have been specified in the ip= command, i.e. if enc300 is the device in the ip= command. This has not been backported to bionic. To boot without specifying the device name, i.e. with just mac address one will need automatic chzdev device configuration via /sys/firmware/sclp_sd/config/data that was added in s390-tools v2.5.0 fist available in cosmic+ but that also needs kernel support for sclp_sd driver to exist, i.e first added in v4.16. Thus if one wants this support one will need to backport 1) initramfs-tools changes 2) s390-tools changes 3) linux sclp_sd driver from linux-hwe to GA ** Also affects: initramfs-tools (Ubuntu) Importance: Undecided Status: New ** Also affects: s390-tools (Ubuntu) Importance: Undecided Status: New ** Also affects: linux (Ubuntu) Importance: Undecided Status: New ** Summary changed: - Unable to boot Ubuntu 18.04 and older on an IBM Z DPM Partition + Unable to netboot Ubuntu 18.04 and older on an IBM Z DPM Partition - no manual nor automatic qeth device configuration -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to initramfs-tools in Ubuntu. https://bugs.launchpad.net/bugs/1918970 Title: Unable to netboot Ubuntu 18.04 and older on an IBM Z DPM Partition - no manual nor automatic qeth device configuration Status in MAAS: New Status in Ubuntu on IBM z Systems: New Status in initramfs-tools package in Ubuntu: New Status in linux package in Ubuntu: New Status in s390-tools package in Ubuntu: New Bug description: I tried to deploy Ubuntu 18.04 with the GA-18.04 kernel on an IBM Z14 DPM Partition. The initrd fails to bring up network and thus fails to boot in MAAS. I haven't tried older versions of Ubuntu but suspect they also have the same bug. mount: mounting /dev on /root/dev failed: No such file or directory done. mount: mounting /run on /root/run failed: No such file or directory run-init: current directory on the same filesystem as the root: error 0 Target filesystem doesn't have requested /sbin/init. run-init: current directory on the same filesystem as the root: error 0 run-init: current directory on the same filesystem as the root: error 0 run-init: current directory on the same filesystem as the root: error 0 run-init: current directory on the same filesystem as the root: error 0 run-init: current directory on the same filesystem as the root: error 0 chvt: can't open console No init found. Try passing init= bootarg. Couldn't get a file descriptor referring to the console /scripts/panic/console_setup: line 133: can't create /dev/tty1: No such device o r address /scripts/panic/console_setup: line 1: can't open /dev/tty1: No such device or ad dress /scripts/panic/console_setup: line 1: can't create /dev/tty2: No such device or address /scripts/panic/console_setup: line 1: can't open /dev/tty2: No such device or ad dress /scripts/panic/console_setup: line 1: can't create /dev/tty3: No such device or address /scripts/panic/console_setup: line 1: can't open /dev/tty3: No such device or ad dress /scripts/panic/console_setup: line 1: can't create /dev/tty4: No such device or address /scripts/panic/console_setup: line 1: can't open /dev/tty4: No such device or ad dress /scripts/panic/console_setup: line 1: can't create /dev/tty5: No such device or address /scripts/panic/console_setup: line 1: can't open /dev/tty5: No such device or ad dress /scripts/panic/console_setup: line 1: can't create /dev/tty6: No such device or address /scripts/panic/console_setup: line 1: can't open /dev/tty6: No such device or ad dress BusyBox v1.27.2 (Ubuntu 1:1.27.2-2ubuntu3.3) built-in shell (ash) Enter 'help' for a list of built-in commands. (initramfs) [6n [ 78.114530] random: crng init done [ 78.114538] random: 7 urandom warning(s) missed due to ratelimiting To manage notifications about this bug go to: https://bugs.launchpad.net/maas/+bug/1918970/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1858092] Re: Network Manager not saving OpenVPN password
I'm running Kubuntu 20.04 (NetworkManager 1.22.10) and this problem exists. I have an openconnect VPN and despite enabling "Store passwords", the password is never stored. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to network-manager in Ubuntu. https://bugs.launchpad.net/bugs/1858092 Title: Network Manager not saving OpenVPN password Status in NetworkManager: Fix Released Status in network-manager package in Ubuntu: Fix Released Status in network-manager source package in Eoan: Fix Released Status in network-manager source package in Focal: Fix Released Bug description: [impact] network-manager no longer correctly saves VPN passwords [test case] on a 19.10 (or later) system, configure a VPN with network-manager and provide a password that it should save. On next connection, it will prompt for a password again. [regression potential] as this adjusts how n-m handles connections with secrets/passwords, any regression would likely cause secrets to fail to be stored for later use, and/or failure to correctly use the secrets at all to setup the connection. [scope] This is needed only in eoan. The patch: https://gitlab.freedesktop.org/NetworkManager/NetworkManager/commit/cf557bf06f344bdbcd775dce35daa42335c645d7 is included in the 1.20.6 release: https://gitlab.freedesktop.org/NetworkManager/NetworkManager/issues/230#note_283402 focal-proposed currently has version 1.20.8, so this patch is already included in focal. This bug was introduced after version 1.18.2: https://gitlab.freedesktop.org/NetworkManager/NetworkManager/issues/230#note_235976 disco-updates has version 1.60.0, so this patch is not needed in disco or earlier. [other info] original description: --- Hi everyone, After upgrading to kubuntu 19.10 I can't save the VPN password using Store password for this user only. It seems the integration with the kwallet is failing somehow... The system logs seem to show that everything went ok, but the password is not saved: jan 02 11:40:40 NetworkManager[5530]: [1577965240.2166] audit: op="connection-update" uuid="4c05-911a-1d9161f05a19" name="ovpn" args="vpn.secrets" pid=14142 uid=1000 result="success" This also happens with a clean install. Operating System: Kubuntu 19.10 KDE Plasma Version: 5.16.5 KDE Frameworks Version: 5.62.0 Qt Version: 5.12.4 Kernel Version: 5.3.0-24-generic OS Type: 64-bit To manage notifications about this bug go to: https://bugs.launchpad.net/network-manager/+bug/1858092/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1481804] Re: LightDM's guest-account script should disable screen lock universally for guest sessions
@Jarno I found the bug report I had filed. https://bugs.launchpad.net/ubuntu/+source/lightdm/+bug/1775088 -- 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/1481804 Title: LightDM's guest-account script should disable screen lock universally for guest sessions Status in lightdm package in Ubuntu: Fix Released Bug description: Is it feasible to include in /usr/sbin/guest-account script some commands to disable screen lock for guest sessions? It should include several commands, depending on Ubuntu flavour. Examples: Ubuntu MATE (uses mate-screensaver) gsettings set org.mate.screensaver lock-enabled false Xubuntu and others (use light-locker) gsettings set apps.light-locker light-locker-enabled false gsettings set apps.light-locker late-locking false gsettings set apps.light-locker lock-on-lid false gsettings set apps.light-locker lock-on-suspend false To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/lightdm/+bug/1481804/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1481804] Re: LightDM's guest-account script should disable screen lock universally for guest sessions
@Jarnos I thought I did, but apparently I did not. I gave up on the guest user setup after this bug and since then moved from LightDM to GDM. -- 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/1481804 Title: LightDM's guest-account script should disable screen lock universally for guest sessions Status in lightdm package in Ubuntu: Fix Released Bug description: Is it feasible to include in /usr/sbin/guest-account script some commands to disable screen lock for guest sessions? It should include several commands, depending on Ubuntu flavour. Examples: Ubuntu MATE (uses mate-screensaver) gsettings set org.mate.screensaver lock-enabled false Xubuntu and others (use light-locker) gsettings set apps.light-locker light-locker-enabled false gsettings set apps.light-locker late-locking false gsettings set apps.light-locker lock-on-lid false gsettings set apps.light-locker lock-on-suspend false To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/lightdm/+bug/1481804/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1920640] Re: EXPKEYSIG C8CAB6595FDFF622 Ubuntu Debug Symbol Archive Automatic Signing Key (2016)
This bug was fixed in the package ubuntu-keyring - 2018.09.18.1~18.04.2 --- ubuntu-keyring (2018.09.18.1~18.04.2) bionic; urgency=medium * Remove expiry of the ddebs.ubuntu.com key. LP: #1920640 -- Dimitri John Ledkov Mon, 29 Mar 2021 15:33:14 +0100 -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to ubuntu-keyring in Ubuntu. https://bugs.launchpad.net/bugs/1920640 Title: EXPKEYSIG C8CAB6595FDFF622 Ubuntu Debug Symbol Archive Automatic Signing Key (2016) Status in ubuntu-keyring package in Ubuntu: Fix Released Status in ubuntu-keyring source package in Bionic: Fix Released Status in ubuntu-keyring source package in Focal: Fix Released Status in ubuntu-keyring source package in Groovy: Fix Released Status in ubuntu-keyring source package in Hirsute: Fix Released Bug description: [Impact] * Cannot update apt metadata from ddebs.ubuntu.com whilst using ubuntu-dbgsym-keyring package [Test Plan] * Install ubuntu-dbgsym-keyring package * Add ddebs.ubuntu.com repository for your release * sudo apt update must be successful * Install ubuntu-dbgsym-keyring package * Install and use `apt-key list` and check that there is no expiry on the dbgsym key I.e. bad output /etc/apt/trusted.gpg.d/ubuntu-keyring-2016-dbgsym.gpg - pub rsa4096 2016-03-21 [SC] [expired: 2021-03-20] F2ED C64D C5AE E1F6 B9C6 21F0 C8CA B659 5FDF F622 uid [ expired] Ubuntu Debug Symbol Archive Automatic Signing Key (2016) Good output has no [date] in the pub line. [Where problems could occur] * At the moment the signature was bumped by one year * Meaning this issue will occur again in 2022 * Instead the key must be set to not expire & new round of SRUs issued [Other Info] * Original bug report The public key used by the debugging symbols repository /usr/share/keyrings/ubuntu-dbgsym-keyring.gpg from the package ubuntu- dbgsym-keyring expired. $ apt policy ubuntu-dbgsym-keyring ubuntu-dbgsym-keyring: Installed: 2020.02.11.2 Candidate: 2020.02.11.2 Version table: *** 2020.02.11.2 500 500 http://archive.ubuntu.com/ubuntu focal/main amd64 Packages 500 http://archive.ubuntu.com/ubuntu focal/main i386 Packages 100 /var/lib/dpkg/status $ gpg --no-default-keyring --keyring /usr/share/keyrings/ubuntu-dbgsym-keyring.gpg --list-keys /usr/share/keyrings/ubuntu-dbgsym-keyring.gpg - pub rsa4096 2016-03-21 [SC] [expired: 2021-03-20] F2EDC64DC5AEE1F6B9C621F0C8CAB6595FDFF622 uid [ expired] Ubuntu Debug Symbol Archive Automatic Signing Key (2016) Error message on "apt update": E: The repository 'http://ddebs.ubuntu.com bionic-updates Release' is not signed. N: Updating from such a repository can't be done securely, and is therefore disabled by default. N: See apt-secure(8) manpage for repository creation and user configuration details. W: GPG error: http://ddebs.ubuntu.com bionic Release: The following signatures were invalid: EXPKEYSIG C8CAB6595FDFF622 Ubuntu Debug Symbol Archive Automatic Signing Key (2016) E: The repository 'http://ddebs.ubuntu.com bionic Release' is not signed. N: Updating from such a repository can't be done securely, and is therefore disabled by default. N: See apt-secure(8) manpage for repository creation and user configuration details. W: GPG error: http://ddebs.ubuntu.com bionic-proposed Release: The following signatures were invalid: EXPKEYSIG C8CAB6595FDFF622 Ubuntu Debug Symbol Archive Automatic Signing Key (2016) E: The repository 'http://ddebs.ubuntu.com bionic-proposed Release' is not signed. N: Updating from such a repository can't be done securely, and is therefore disabled by default. N: See apt-secure(8) manpage for repository creation and user configuration details. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubuntu-keyring/+bug/1920640/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1920640] Update Released
The verification of the Stable Release Update for ubuntu-keyring has completed successfully and the package is now being released to -updates. Subsequently, the Ubuntu Stable Release Updates Team is being unsubscribed and will not receive messages about this bug report. In the event that you encounter a regression using the package from -updates please report a new bug using ubuntu-bug and tag the bug report regression-update so we can easily find any regressions. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to ubuntu-keyring in Ubuntu. https://bugs.launchpad.net/bugs/1920640 Title: EXPKEYSIG C8CAB6595FDFF622 Ubuntu Debug Symbol Archive Automatic Signing Key (2016) Status in ubuntu-keyring package in Ubuntu: Fix Released Status in ubuntu-keyring source package in Bionic: Fix Released Status in ubuntu-keyring source package in Focal: Fix Released Status in ubuntu-keyring source package in Groovy: Fix Released Status in ubuntu-keyring source package in Hirsute: Fix Released Bug description: [Impact] * Cannot update apt metadata from ddebs.ubuntu.com whilst using ubuntu-dbgsym-keyring package [Test Plan] * Install ubuntu-dbgsym-keyring package * Add ddebs.ubuntu.com repository for your release * sudo apt update must be successful * Install ubuntu-dbgsym-keyring package * Install and use `apt-key list` and check that there is no expiry on the dbgsym key I.e. bad output /etc/apt/trusted.gpg.d/ubuntu-keyring-2016-dbgsym.gpg - pub rsa4096 2016-03-21 [SC] [expired: 2021-03-20] F2ED C64D C5AE E1F6 B9C6 21F0 C8CA B659 5FDF F622 uid [ expired] Ubuntu Debug Symbol Archive Automatic Signing Key (2016) Good output has no [date] in the pub line. [Where problems could occur] * At the moment the signature was bumped by one year * Meaning this issue will occur again in 2022 * Instead the key must be set to not expire & new round of SRUs issued [Other Info] * Original bug report The public key used by the debugging symbols repository /usr/share/keyrings/ubuntu-dbgsym-keyring.gpg from the package ubuntu- dbgsym-keyring expired. $ apt policy ubuntu-dbgsym-keyring ubuntu-dbgsym-keyring: Installed: 2020.02.11.2 Candidate: 2020.02.11.2 Version table: *** 2020.02.11.2 500 500 http://archive.ubuntu.com/ubuntu focal/main amd64 Packages 500 http://archive.ubuntu.com/ubuntu focal/main i386 Packages 100 /var/lib/dpkg/status $ gpg --no-default-keyring --keyring /usr/share/keyrings/ubuntu-dbgsym-keyring.gpg --list-keys /usr/share/keyrings/ubuntu-dbgsym-keyring.gpg - pub rsa4096 2016-03-21 [SC] [expired: 2021-03-20] F2EDC64DC5AEE1F6B9C621F0C8CAB6595FDFF622 uid [ expired] Ubuntu Debug Symbol Archive Automatic Signing Key (2016) Error message on "apt update": E: The repository 'http://ddebs.ubuntu.com bionic-updates Release' is not signed. N: Updating from such a repository can't be done securely, and is therefore disabled by default. N: See apt-secure(8) manpage for repository creation and user configuration details. W: GPG error: http://ddebs.ubuntu.com bionic Release: The following signatures were invalid: EXPKEYSIG C8CAB6595FDFF622 Ubuntu Debug Symbol Archive Automatic Signing Key (2016) E: The repository 'http://ddebs.ubuntu.com bionic Release' is not signed. N: Updating from such a repository can't be done securely, and is therefore disabled by default. N: See apt-secure(8) manpage for repository creation and user configuration details. W: GPG error: http://ddebs.ubuntu.com bionic-proposed Release: The following signatures were invalid: EXPKEYSIG C8CAB6595FDFF622 Ubuntu Debug Symbol Archive Automatic Signing Key (2016) E: The repository 'http://ddebs.ubuntu.com bionic-proposed Release' is not signed. N: Updating from such a repository can't be done securely, and is therefore disabled by default. N: See apt-secure(8) manpage for repository creation and user configuration details. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubuntu-keyring/+bug/1920640/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1920640] Re: EXPKEYSIG C8CAB6595FDFF622 Ubuntu Debug Symbol Archive Automatic Signing Key (2016)
This bug was fixed in the package ubuntu-keyring - 2020.02.11.4 --- ubuntu-keyring (2020.02.11.4) focal; urgency=medium * Remove expiry of the ddebs.ubuntu.com key. LP: #1920640 -- Dimitri John Ledkov Mon, 29 Mar 2021 15:29:33 +0100 ** Changed in: ubuntu-keyring (Ubuntu Focal) Status: Fix Committed => Fix Released ** Changed in: ubuntu-keyring (Ubuntu Bionic) Status: Fix Committed => Fix Released -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to ubuntu-keyring in Ubuntu. https://bugs.launchpad.net/bugs/1920640 Title: EXPKEYSIG C8CAB6595FDFF622 Ubuntu Debug Symbol Archive Automatic Signing Key (2016) Status in ubuntu-keyring package in Ubuntu: Fix Released Status in ubuntu-keyring source package in Bionic: Fix Released Status in ubuntu-keyring source package in Focal: Fix Released Status in ubuntu-keyring source package in Groovy: Fix Released Status in ubuntu-keyring source package in Hirsute: Fix Released Bug description: [Impact] * Cannot update apt metadata from ddebs.ubuntu.com whilst using ubuntu-dbgsym-keyring package [Test Plan] * Install ubuntu-dbgsym-keyring package * Add ddebs.ubuntu.com repository for your release * sudo apt update must be successful * Install ubuntu-dbgsym-keyring package * Install and use `apt-key list` and check that there is no expiry on the dbgsym key I.e. bad output /etc/apt/trusted.gpg.d/ubuntu-keyring-2016-dbgsym.gpg - pub rsa4096 2016-03-21 [SC] [expired: 2021-03-20] F2ED C64D C5AE E1F6 B9C6 21F0 C8CA B659 5FDF F622 uid [ expired] Ubuntu Debug Symbol Archive Automatic Signing Key (2016) Good output has no [date] in the pub line. [Where problems could occur] * At the moment the signature was bumped by one year * Meaning this issue will occur again in 2022 * Instead the key must be set to not expire & new round of SRUs issued [Other Info] * Original bug report The public key used by the debugging symbols repository /usr/share/keyrings/ubuntu-dbgsym-keyring.gpg from the package ubuntu- dbgsym-keyring expired. $ apt policy ubuntu-dbgsym-keyring ubuntu-dbgsym-keyring: Installed: 2020.02.11.2 Candidate: 2020.02.11.2 Version table: *** 2020.02.11.2 500 500 http://archive.ubuntu.com/ubuntu focal/main amd64 Packages 500 http://archive.ubuntu.com/ubuntu focal/main i386 Packages 100 /var/lib/dpkg/status $ gpg --no-default-keyring --keyring /usr/share/keyrings/ubuntu-dbgsym-keyring.gpg --list-keys /usr/share/keyrings/ubuntu-dbgsym-keyring.gpg - pub rsa4096 2016-03-21 [SC] [expired: 2021-03-20] F2EDC64DC5AEE1F6B9C621F0C8CAB6595FDFF622 uid [ expired] Ubuntu Debug Symbol Archive Automatic Signing Key (2016) Error message on "apt update": E: The repository 'http://ddebs.ubuntu.com bionic-updates Release' is not signed. N: Updating from such a repository can't be done securely, and is therefore disabled by default. N: See apt-secure(8) manpage for repository creation and user configuration details. W: GPG error: http://ddebs.ubuntu.com bionic Release: The following signatures were invalid: EXPKEYSIG C8CAB6595FDFF622 Ubuntu Debug Symbol Archive Automatic Signing Key (2016) E: The repository 'http://ddebs.ubuntu.com bionic Release' is not signed. N: Updating from such a repository can't be done securely, and is therefore disabled by default. N: See apt-secure(8) manpage for repository creation and user configuration details. W: GPG error: http://ddebs.ubuntu.com bionic-proposed Release: The following signatures were invalid: EXPKEYSIG C8CAB6595FDFF622 Ubuntu Debug Symbol Archive Automatic Signing Key (2016) E: The repository 'http://ddebs.ubuntu.com bionic-proposed Release' is not signed. N: Updating from such a repository can't be done securely, and is therefore disabled by default. N: See apt-secure(8) manpage for repository creation and user configuration details. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubuntu-keyring/+bug/1920640/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1920640] Re: EXPKEYSIG C8CAB6595FDFF622 Ubuntu Debug Symbol Archive Automatic Signing Key (2016)
This bug was fixed in the package ubuntu-keyring - 2020.06.17.3 --- ubuntu-keyring (2020.06.17.3) groovy; urgency=medium * Remove expiry of the ddebs.ubuntu.com key. LP: #1920640 -- Dimitri John Ledkov Mon, 29 Mar 2021 15:28:00 +0100 ** Changed in: ubuntu-keyring (Ubuntu Groovy) Status: Fix Committed => Fix Released -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to ubuntu-keyring in Ubuntu. https://bugs.launchpad.net/bugs/1920640 Title: EXPKEYSIG C8CAB6595FDFF622 Ubuntu Debug Symbol Archive Automatic Signing Key (2016) Status in ubuntu-keyring package in Ubuntu: Fix Released Status in ubuntu-keyring source package in Bionic: Fix Released Status in ubuntu-keyring source package in Focal: Fix Released Status in ubuntu-keyring source package in Groovy: Fix Released Status in ubuntu-keyring source package in Hirsute: Fix Released Bug description: [Impact] * Cannot update apt metadata from ddebs.ubuntu.com whilst using ubuntu-dbgsym-keyring package [Test Plan] * Install ubuntu-dbgsym-keyring package * Add ddebs.ubuntu.com repository for your release * sudo apt update must be successful * Install ubuntu-dbgsym-keyring package * Install and use `apt-key list` and check that there is no expiry on the dbgsym key I.e. bad output /etc/apt/trusted.gpg.d/ubuntu-keyring-2016-dbgsym.gpg - pub rsa4096 2016-03-21 [SC] [expired: 2021-03-20] F2ED C64D C5AE E1F6 B9C6 21F0 C8CA B659 5FDF F622 uid [ expired] Ubuntu Debug Symbol Archive Automatic Signing Key (2016) Good output has no [date] in the pub line. [Where problems could occur] * At the moment the signature was bumped by one year * Meaning this issue will occur again in 2022 * Instead the key must be set to not expire & new round of SRUs issued [Other Info] * Original bug report The public key used by the debugging symbols repository /usr/share/keyrings/ubuntu-dbgsym-keyring.gpg from the package ubuntu- dbgsym-keyring expired. $ apt policy ubuntu-dbgsym-keyring ubuntu-dbgsym-keyring: Installed: 2020.02.11.2 Candidate: 2020.02.11.2 Version table: *** 2020.02.11.2 500 500 http://archive.ubuntu.com/ubuntu focal/main amd64 Packages 500 http://archive.ubuntu.com/ubuntu focal/main i386 Packages 100 /var/lib/dpkg/status $ gpg --no-default-keyring --keyring /usr/share/keyrings/ubuntu-dbgsym-keyring.gpg --list-keys /usr/share/keyrings/ubuntu-dbgsym-keyring.gpg - pub rsa4096 2016-03-21 [SC] [expired: 2021-03-20] F2EDC64DC5AEE1F6B9C621F0C8CAB6595FDFF622 uid [ expired] Ubuntu Debug Symbol Archive Automatic Signing Key (2016) Error message on "apt update": E: The repository 'http://ddebs.ubuntu.com bionic-updates Release' is not signed. N: Updating from such a repository can't be done securely, and is therefore disabled by default. N: See apt-secure(8) manpage for repository creation and user configuration details. W: GPG error: http://ddebs.ubuntu.com bionic Release: The following signatures were invalid: EXPKEYSIG C8CAB6595FDFF622 Ubuntu Debug Symbol Archive Automatic Signing Key (2016) E: The repository 'http://ddebs.ubuntu.com bionic Release' is not signed. N: Updating from such a repository can't be done securely, and is therefore disabled by default. N: See apt-secure(8) manpage for repository creation and user configuration details. W: GPG error: http://ddebs.ubuntu.com bionic-proposed Release: The following signatures were invalid: EXPKEYSIG C8CAB6595FDFF622 Ubuntu Debug Symbol Archive Automatic Signing Key (2016) E: The repository 'http://ddebs.ubuntu.com bionic-proposed Release' is not signed. N: Updating from such a repository can't be done securely, and is therefore disabled by default. N: See apt-secure(8) manpage for repository creation and user configuration details. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubuntu-keyring/+bug/1920640/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1921829] Re: Bluetooth not working
The issue is not due to the settings if the command line is failing, reassigning but it could be a kernel or driver problem, it could be worth trying to boot an older or newer kernel to try ** Package changed: gnome-control-center (Ubuntu) => bluez (Ubuntu) ** Changed in: bluez (Ubuntu) Status: Incomplete => New -- 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/1921829 Title: Bluetooth not working Status in bluez package in Ubuntu: New Bug description: It's impossible to activate the Bluetooth, putting the switch to ON does nothing, when re-entering the Bluetooth settings it's still OFF. ProblemType: Bug DistroRelease: Ubuntu 21.04 Package: gnome-control-center 1:3.38.5-1ubuntu1 ProcVersionSignature: Ubuntu 5.11.0-11.12-generic 5.11.0 Uname: Linux 5.11.0-11-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu61 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: ubuntu:GNOME Date: Tue Mar 30 08:11:43 2021 ExecutablePath: /usr/bin/gnome-control-center InstallationDate: Installed on 2020-09-15 (195 days ago) InstallationMedia: Ubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731) SourcePackage: gnome-control-center UpgradeStatus: Upgraded to hirsute on 2021-03-19 (10 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/1921829/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1921829] [NEW] Bluetooth not working
You have been subscribed to a public bug: It's impossible to activate the Bluetooth, putting the switch to ON does nothing, when re-entering the Bluetooth settings it's still OFF. ProblemType: Bug DistroRelease: Ubuntu 21.04 Package: gnome-control-center 1:3.38.5-1ubuntu1 ProcVersionSignature: Ubuntu 5.11.0-11.12-generic 5.11.0 Uname: Linux 5.11.0-11-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu61 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: ubuntu:GNOME Date: Tue Mar 30 08:11:43 2021 ExecutablePath: /usr/bin/gnome-control-center InstallationDate: Installed on 2020-09-15 (195 days ago) InstallationMedia: Ubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731) SourcePackage: gnome-control-center UpgradeStatus: Upgraded to hirsute on 2021-03-19 (10 days ago) ** Affects: bluez (Ubuntu) Importance: Low Status: New ** Tags: amd64 apport-bug hirsute -- Bluetooth not working https://bugs.launchpad.net/bugs/1921829 You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to bluez 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 1481804] Re: LightDM's guest-account script should disable screen lock universally for guest sessions
@Sushenjit did you file a bug report? -- 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/1481804 Title: LightDM's guest-account script should disable screen lock universally for guest sessions Status in lightdm package in Ubuntu: Fix Released Bug description: Is it feasible to include in /usr/sbin/guest-account script some commands to disable screen lock for guest sessions? It should include several commands, depending on Ubuntu flavour. Examples: Ubuntu MATE (uses mate-screensaver) gsettings set org.mate.screensaver lock-enabled false Xubuntu and others (use light-locker) gsettings set apps.light-locker light-locker-enabled false gsettings set apps.light-locker late-locking false gsettings set apps.light-locker lock-on-lid false gsettings set apps.light-locker lock-on-suspend false To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/lightdm/+bug/1481804/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
Re: [Touch-packages] [Bug 1920665] Re: Ubiquity KDE crash on try/install and from live session with "malloc(): unaligned tcache chunk detected"
On 31/03/2021 14:21, Timo Aaltonen wrote: > Can ubiquity be run manually? Or there would need to be another > reproducer for this, otherwise bisecting mesa would be impossible. Ubiquity can be run from the command line in a terminal to reproduce. You also do not have to do it from a ISO live session, but can install 'ubiquity' and 'ubiquity-frontend-kde' on a installed hirsute VM. -- 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/1920665 Title: Ubiquity KDE crash on try/install and from live session with "malloc(): unaligned tcache chunk detected" Status in mesa package in Ubuntu: Confirmed Status in ubiquity package in Ubuntu: Confirmed Status in mesa source package in Hirsute: Confirmed Status in ubiquity source package in Hirsute: Confirmed Bug description: ProblemType: Bug DistroRelease: Ubuntu 21.04 Package: ubiquity 21.04.11 ProcVersionSignature: Ubuntu 5.11.0-11.12-generic 5.11.0 Uname: Linux 5.11.0-11-generic x86_64 ApportVersion: 2.20.11-0ubuntu60 Architecture: amd64 CasperMD5CheckResult: pass CasperVersion: 1.460 CurrentDesktop: KDE Date: Sun Mar 21 11:53:44 2021 InstallCmdLine: BOOT_IMAGE=/casper/vmlinuz file=/cdrom/preseed/kubuntu.seed maybe-ubiquity quiet splash --- LiveMediaBuild: Kubuntu 21.04 "Hirsute Hippo" - Alpha amd64 (20210321) SourcePackage: ubiquity UpgradeStatus: No upgrade log present (probably fresh install) Since approximately 16/03/2021 ubiquity from maybe-ubiquity (try install screen) and from the live session is crashing on launch or shortly after. Cases where the crash can be triggered: - Using a Virtualbox VM, where graphics acceleration is handled by mesa with LLVMPIPE - Start the ISO on real hardware in 'safe graphics mode' Cases where the crash is not encountered: - Start the ISO on real intel (HD graphics) hardware with full acceleration. NOTE: The crash can be avoided by downgrading MESA 21.0.x packages to the previous 20.3.4 in hirsute. Try/Install crash: Screen fails to start, or starts then crashes on any user action. The user is presented with: "Installation failed - The installer encountered an unrecoverable error. A desktop session will now be run so that you may investigate the problem or try installing again" Live session crash: The installer does not start from the desktop icon. Starting ubiquity from the terminal results in an "Aborted (core dumped)" message and nothing else. An example /var/log/installer/debug log from a session where both crashes were triggered is below. /var/log/installer/debug Ubiquity 21.04.11 TEXT If more than one person will use this computer, you can set up multiple accounts after installation. TEXT Enter the same password twice, so that it can be checked for typing errors. TEXT The name it uses when it talks to other computers. TEXT Enter the same password twice, so that it can be checked for typing errors. TEXT Enter the same password twice, so that it can be checked for typing errors. TEXT If more than one person will use this computer, you can set up multiple accounts after installation. TEXT Enter the same password twice, so that it can be checked for typing errors. TEXT The name it uses when it talks to other computers. QSocketNotifier: Invalid socket 17 and type 'Read', disabling... QSocketNotifier: Invalid socket 17 and type 'Write', disabling... QSocketNotifier: Invalid socket 17 and type 'Exception', disabling... Your console font configuration will be updated the next time your system boots. If you want to update it now, run 'setupcon' from a virtual console. update-initramfs is disabled since running on read-only media debconf: DbDriver "passwords" warning: could not open /var/cache/debconf/passwords.dat: Permission denied munmap_chunk(): invalid pointer Ubiquity 21.04.11 QStandardPaths: XDG_RUNTIME_DIR not set, defaulting to '/tmp/runtime-kubuntu' QStandardPaths: XDG_RUNTIME_DIR not set, defaulting to '/tmp/runtime-kubuntu' QStandardPaths: XDG_RUNTIME_DIR not set, defaulting to '/tmp/runtime-kubuntu' TEXT If more than one person will use this computer, you can set up multiple accounts after installation. TEXT Enter the same password twice, so that it can be checked for typing errors. TEXT The name it uses when it talks to other computers. TEXT Enter the same password twice, so that it can be checked for typing errors. malloc(): unaligned tcache chunk detected To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mesa/+bug/1920665/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1920665] Re: Ubiquity KDE crash on try/install and from live session with "malloc(): unaligned tcache chunk detected"
Can ubiquity be run manually? Or there would need to be another reproducer for this, otherwise bisecting mesa would be impossible. -- 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/1920665 Title: Ubiquity KDE crash on try/install and from live session with "malloc(): unaligned tcache chunk detected" Status in mesa package in Ubuntu: Confirmed Status in ubiquity package in Ubuntu: Confirmed Status in mesa source package in Hirsute: Confirmed Status in ubiquity source package in Hirsute: Confirmed Bug description: ProblemType: Bug DistroRelease: Ubuntu 21.04 Package: ubiquity 21.04.11 ProcVersionSignature: Ubuntu 5.11.0-11.12-generic 5.11.0 Uname: Linux 5.11.0-11-generic x86_64 ApportVersion: 2.20.11-0ubuntu60 Architecture: amd64 CasperMD5CheckResult: pass CasperVersion: 1.460 CurrentDesktop: KDE Date: Sun Mar 21 11:53:44 2021 InstallCmdLine: BOOT_IMAGE=/casper/vmlinuz file=/cdrom/preseed/kubuntu.seed maybe-ubiquity quiet splash --- LiveMediaBuild: Kubuntu 21.04 "Hirsute Hippo" - Alpha amd64 (20210321) SourcePackage: ubiquity UpgradeStatus: No upgrade log present (probably fresh install) Since approximately 16/03/2021 ubiquity from maybe-ubiquity (try install screen) and from the live session is crashing on launch or shortly after. Cases where the crash can be triggered: - Using a Virtualbox VM, where graphics acceleration is handled by mesa with LLVMPIPE - Start the ISO on real hardware in 'safe graphics mode' Cases where the crash is not encountered: - Start the ISO on real intel (HD graphics) hardware with full acceleration. NOTE: The crash can be avoided by downgrading MESA 21.0.x packages to the previous 20.3.4 in hirsute. Try/Install crash: Screen fails to start, or starts then crashes on any user action. The user is presented with: "Installation failed - The installer encountered an unrecoverable error. A desktop session will now be run so that you may investigate the problem or try installing again" Live session crash: The installer does not start from the desktop icon. Starting ubiquity from the terminal results in an "Aborted (core dumped)" message and nothing else. An example /var/log/installer/debug log from a session where both crashes were triggered is below. /var/log/installer/debug Ubiquity 21.04.11 TEXT If more than one person will use this computer, you can set up multiple accounts after installation. TEXT Enter the same password twice, so that it can be checked for typing errors. TEXT The name it uses when it talks to other computers. TEXT Enter the same password twice, so that it can be checked for typing errors. TEXT Enter the same password twice, so that it can be checked for typing errors. TEXT If more than one person will use this computer, you can set up multiple accounts after installation. TEXT Enter the same password twice, so that it can be checked for typing errors. TEXT The name it uses when it talks to other computers. QSocketNotifier: Invalid socket 17 and type 'Read', disabling... QSocketNotifier: Invalid socket 17 and type 'Write', disabling... QSocketNotifier: Invalid socket 17 and type 'Exception', disabling... Your console font configuration will be updated the next time your system boots. If you want to update it now, run 'setupcon' from a virtual console. update-initramfs is disabled since running on read-only media debconf: DbDriver "passwords" warning: could not open /var/cache/debconf/passwords.dat: Permission denied munmap_chunk(): invalid pointer Ubiquity 21.04.11 QStandardPaths: XDG_RUNTIME_DIR not set, defaulting to '/tmp/runtime-kubuntu' QStandardPaths: XDG_RUNTIME_DIR not set, defaulting to '/tmp/runtime-kubuntu' QStandardPaths: XDG_RUNTIME_DIR not set, defaulting to '/tmp/runtime-kubuntu' TEXT If more than one person will use this computer, you can set up multiple accounts after installation. TEXT Enter the same password twice, so that it can be checked for typing errors. TEXT The name it uses when it talks to other computers. TEXT Enter the same password twice, so that it can be checked for typing errors. malloc(): unaligned tcache chunk detected To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mesa/+bug/1920665/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1922082] [NEW] Exec binary '/usr/libexec/evolution-data-server/evolution-alarm-notify' does not exist: No such file or directory
Public bug reported: On ppc64le and Ubuntu 20.10 with *evolution-data-server* 3.38.1-1, the logs contain, when starting an Xfce session over X2Go. [98982.444956] systemd-xdg-autostart-generator[297820]: Exec binary '/usr/libexec/evolution-data-server/evolution-alarm-notify' does not exist: No such file or directory [98982.444963] systemd-xdg-autostart-generator[297820]: Not generating service for XDG autostart app-org.gnome.Evolution\x2dalarm\x2dnotify-autostart.service, error parsing Exec= line: No such file or directory The executable is missing. $ dpkg -S /usr/libexec/evolution-data-server/evolution-alarm-notify dpkg-query: no path found matching pattern /usr/libexec/evolution-data-server/evolution-alarm-notify (In Debian sid/unstable it is present.) ** Affects: evolution-data-server (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to evolution-data-server in Ubuntu. https://bugs.launchpad.net/bugs/1922082 Title: Exec binary '/usr/libexec/evolution-data-server/evolution-alarm- notify' does not exist: No such file or directory Status in evolution-data-server package in Ubuntu: New Bug description: On ppc64le and Ubuntu 20.10 with *evolution-data-server* 3.38.1-1, the logs contain, when starting an Xfce session over X2Go. [98982.444956] systemd-xdg-autostart-generator[297820]: Exec binary '/usr/libexec/evolution-data-server/evolution-alarm-notify' does not exist: No such file or directory [98982.444963] systemd-xdg-autostart-generator[297820]: Not generating service for XDG autostart app-org.gnome.Evolution\x2dalarm\x2dnotify-autostart.service, error parsing Exec= line: No such file or directory The executable is missing. $ dpkg -S /usr/libexec/evolution-data-server/evolution-alarm-notify dpkg-query: no path found matching pattern /usr/libexec/evolution-data-server/evolution-alarm-notify (In Debian sid/unstable it is present.) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/evolution-data-server/+bug/1922082/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1274613] Re: module-bluetooth-discover does not load on login
I still have this problem :( module-bluetooth-discover module initialization failed. It's instructed to load in /etc/pulse/default.pa, but is not loaded when the system is started up. It's also not able to be manually loaded. Help!! D: -- 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/1274613 Title: module-bluetooth-discover does not load on login Status in pulseaudio package in Ubuntu: Triaged Bug description: The following lines appear in /etc/pulse/default.pa, which I have not modified: .ifexists module-bluetooth-discover.so load-module module-bluetooth-discover .endif Expected: module-bluetooth-discover is loaded on login, as configured. Observed: pulseaudio's module-bluetooth-discover does not load on login. My system does not detect and set up sinks when I connect to Bluetooth devices (including an A2DP speaker and a headset). If I issue, in a terminal window: $ pactl load-module module-bluetooth-discover 24 …then the devices are detected and sinks set up correctly. $ lsb_release -rd && apt-cache policy pulseaudio-module-bluetooth Description:Ubuntu 13.10 Release:13.10 pulseaudio-module-bluetooth: Installed: 1:4.0-0ubuntu6 Candidate: 1:4.0-0ubuntu6 Version table: *** 1:4.0-0ubuntu6 0 500 http://mirrors.mit.edu/ubuntu/ saucy/main amd64 Packages 100 /var/lib/dpkg/status ProblemType: Bug DistroRelease: Ubuntu 13.10 Package: pulseaudio 1:4.0-0ubuntu6 ProcVersionSignature: Ubuntu 3.11.0-17.30-generic 3.11.10.3 Uname: Linux 3.11.0-17-generic x86_64 ApportVersion: 2.12.5-0ubuntu2.2 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: khaeru 2051 F pulseaudio Date: Thu Jan 30 12:18:50 2014 EcryptfsInUse: Yes InstallationDate: Installed on 2012-10-29 (457 days ago) InstallationMedia: Ubuntu 12.10 "Quantal Quetzal" - Release amd64 (20121017.5) MarkForUpload: True SourcePackage: pulseaudio UpgradeStatus: Upgraded to saucy on 2013-09-11 (140 days ago) dmi.bios.date: 05/15/2013 dmi.bios.vendor: Dell Inc. dmi.bios.version: A09 dmi.board.name: 085VR5 dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 8 dmi.chassis.vendor: Dell Inc. dmi.chassis.version: 0.1 dmi.modalias: dmi:bvnDellInc.:bvrA09:bd05/15/2013:svnDellInc.:pnDellSystemXPSL322X:pvr:rvnDellInc.:rn085VR5:rvrA00:cvnDellInc.:ct8:cvr0.1: dmi.product.name: Dell System XPS L322X dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1274613/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1922025] [NEW] package initramfs-tools 0.136ubuntu6.3 failed to install/upgrade: 已安装 initramfs-tools 软件包 post-installation 脚本 子进程返回错误状态 1
Public bug reported: linux-image-5.8.0-48-generic also appear in the error list. ProblemType: Package DistroRelease: Ubuntu 20.04 Package: initramfs-tools 0.136ubuntu6.3 ProcVersionSignature: Ubuntu 5.8.0-48.54~20.04.1-generic 5.8.18 Uname: Linux 5.8.0-48-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu27.16 Architecture: amd64 CasperMD5CheckResult: skip Date: Wed Mar 31 16:19:59 2021 ErrorMessage: 已安装 initramfs-tools 软件包 post-installation 脚本 子进程返回错误状态 1 InstallationDate: Installed on 2021-02-16 (43 days ago) InstallationMedia: Ubuntu 20.04.2.0 LTS "Focal Fossa" - Release amd64 (20210209.1) PackageArchitecture: all Python3Details: /usr/bin/python3.8, Python 3.8.5, python3-minimal, 3.8.2-0ubuntu2 PythonDetails: N/A RelatedPackageVersions: dpkg 1.19.7ubuntu3 apt 2.0.4 SourcePackage: initramfs-tools Title: package initramfs-tools 0.136ubuntu6.3 failed to install/upgrade: 已安装 initramfs-tools 软件包 post-installation 脚本 子进程返回错误状态 1 UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: initramfs-tools (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-package focal -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to initramfs-tools in Ubuntu. https://bugs.launchpad.net/bugs/1922025 Title: package initramfs-tools 0.136ubuntu6.3 failed to install/upgrade: 已安装 initramfs-tools 软件包 post-installation 脚本 子进程返回错误状态 1 Status in initramfs-tools package in Ubuntu: New Bug description: linux-image-5.8.0-48-generic also appear in the error list. ProblemType: Package DistroRelease: Ubuntu 20.04 Package: initramfs-tools 0.136ubuntu6.3 ProcVersionSignature: Ubuntu 5.8.0-48.54~20.04.1-generic 5.8.18 Uname: Linux 5.8.0-48-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu27.16 Architecture: amd64 CasperMD5CheckResult: skip Date: Wed Mar 31 16:19:59 2021 ErrorMessage: 已安装 initramfs-tools 软件包 post-installation 脚本 子进程返回错误状态 1 InstallationDate: Installed on 2021-02-16 (43 days ago) InstallationMedia: Ubuntu 20.04.2.0 LTS "Focal Fossa" - Release amd64 (20210209.1) PackageArchitecture: all Python3Details: /usr/bin/python3.8, Python 3.8.5, python3-minimal, 3.8.2-0ubuntu2 PythonDetails: N/A RelatedPackageVersions: dpkg 1.19.7ubuntu3 apt 2.0.4 SourcePackage: initramfs-tools Title: package initramfs-tools 0.136ubuntu6.3 failed to install/upgrade: 已安装 initramfs-tools 软件包 post-installation 脚本 子进程返回错误状态 1 UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/initramfs-tools/+bug/1922025/+subscriptions -- Mailing list: https://launchpad.net/~touch-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 due to systemd-shim
I also had this problem. I was upgrading from 16 LTS -> 18 LTS -> 20 LTS
sudo mv
/usr/share/dbus-1/system-services/org.freedesktop.systemd1.service{,.bak}
sudo apt purge systemd-shim
Do you want to continue? [Y/n] y
Abort.
(Not sure why that happened and I had to run it again to actually get it to
purge).
sudo apt-get update
sudo apt-get upgrade
(Software updater upgrade button does nothing...)
The following packages have been kept back:
python-oauthlib python-openssl
sudo apt-get remove python-oauthlib python-openssl
Then it worked from GUI
--
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 due to systemd-shim
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 388605] Re: [MIR] rsyslog
Yeah, that should be ok we have the buy in from everyone involved that it is fine to promote in past releases. ** Changed in: rsyslog (Ubuntu Groovy) Status: New => Fix Committed ** Changed in: rsyslog (Ubuntu Focal) Status: New => Fix Committed ** Changed in: rsyslog (Ubuntu Bionic) Status: New => Fix Committed -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to rsyslog in Ubuntu. https://bugs.launchpad.net/bugs/388605 Title: [MIR] rsyslog Status in rsyslog package in Ubuntu: Fix Released Status in rsyslog source package in Bionic: Fix Committed Status in rsyslog source package in Focal: Fix Committed Status in rsyslog source package in Groovy: Fix Committed Status in rsyslog source package in Hirsute: Fix Released Bug description: Binary package hint: rsyslog We want to make rsyslog the new default syslogger. See https://wiki.ubuntu.com/MainInclusionReport/rsyslog To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/rsyslog/+bug/388605/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
