[Bug 2000063] Re: rdp password changes if autologin
Yes please must fix. Headless Ubuntu is quite the most used form of Ubuntu used in my workplace. This issue is quite the non-starter to proliferate usage to less technical team members -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/263 Title: rdp password changes if autologin To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/meta-gnome3/+bug/263/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2000063] Re: rdp password changes if autologin
Yes please must fix. Headless Ubuntu is quite the most used form of Ubuntu used in my workplace. This issue is quite the non-starter to proliferate usage to less technical team members -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/263 Title: rdp password changes if autologin To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/meta-gnome3/+bug/263/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2061713] [NEW] ASUS Battery Won't Charge if Plugged in While Suspended
Public bug reported: When running Ubuntu (or any other linux distro i've tried) the laptop will not charge if it is plugged in while suspended. Charging works find if the laptop is awake, or if it is shut down. It also works properly when running windows which makes me think its not a hardware problem but a linux issue. The charge status doesn't seem to update at all when the computer is suspended. If it is charging when its put to sleep then the charge LED on the side is lit, and if I then unplug the charger the LED doesn't turn off until the computer is woken up. If the computer is plugged in while sleeping I know it isn't charging even though the light doesn't turn on because I have left it overnight and the battery stays at the same percentage. I've been unable to find any information about what could be causing this issue. My Laptop is an ASUS Zenbook Flip UX461UA Ubuntu Version: Description:Ubuntu 22.04.4 LTS Release:22.04 I'm not sure what package would be causing this. What I expect to be happening: The battery should start charging if its plugged in while suspended What happened instead: Battery doesn't charge and charging indicator doesn't change until the computer is woken up ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: linux-image-6.5.0-27-generic 6.5.0-27.28~22.04.1 ProcVersionSignature: Ubuntu 6.5.0-27.28~22.04.1-generic 6.5.13 Uname: Linux 6.5.0-27-generic x86_64 ApportVersion: 2.20.11-0ubuntu82.5 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Mon Apr 15 23:21:17 2024 InstallationDate: Installed on 2024-04-16 (0 days ago) InstallationMedia: Ubuntu 22.04.4 LTS "Jammy Jellyfish" - Release amd64 (20240220) SourcePackage: linux-signed-hwe-6.5 UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: ubuntu Importance: Undecided Status: New ** Tags: amd64 apport-bug jammy wayland-session -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2061713 Title: ASUS Battery Won't Charge if Plugged in While Suspended To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+bug/2061713/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2060136] [NEW] Include paftools.js
Public bug reported: Some software, such as https://github.com/mritchielab/FLAMES, requires paftools.js (in addition to minimap2) for converting annotation to bed12 files. It appears that paftools.js is not packaged with minimap2: ``` $ dpkg -L minimap2 /. /usr /usr/bin /usr/bin/minimap2 /usr/share /usr/share/doc /usr/share/doc/minimap2 /usr/share/doc/minimap2/changelog.Debian.gz /usr/share/doc/minimap2/copyright /usr/share/doc/minimap2/minimap2.pdf /usr/share/doc/minimap2/run-unit-test /usr/share/doc/minimap2/test /usr/share/doc/minimap2/test/MT-human.fa.gz /usr/share/doc/minimap2/test/MT-orang.fa.gz /usr/share/doc/minimap2/test/q-inv.fa.gz /usr/share/doc/minimap2/test/q2.fa /usr/share/doc/minimap2/test/t-inv.fa.gz /usr/share/doc/minimap2/test/t2.fa /usr/share/doc/minimap2/test_script /usr/share/doc-base /usr/share/doc-base/minimap2.minimap2 /usr/share/man /usr/share/man/man1 /usr/share/man/man1/minimap2.1.gz ``` It would be helpful if paftools.js were installed along with the minimap2 executable. ** Affects: minimap2 (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2060136 Title: Include paftools.js To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/minimap2/+bug/2060136/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2055037] Re: [amdgpu] My screen randomly starts flickering
Hello again Daniel, Thank you very again much for your help and again, my apologies for being unable to reply to your sooner. I have found recently that my laptop, the Lenovo V145-15AST has stopped suffering from a flickering screen. I have used the laptop extensively for normal work and the problem has disappeared. There have been two updates during the course of our discussion. Although I'm finding it difficult to give you any detailed information as typing "lsb_release -a" at the terminal only results in; No LSB modules are available. Distributor ID: Ubuntu Description:Ubuntu 22.04.4 LTS Release:22.04 Codename: jammy I'm not sure how to let you know what was installed during the two updates, as I'm sure that would help. Many thanks again for all of your help in this matter, Nick. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2055037 Title: [amdgpu] My screen randomly starts flickering To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-hwe-6.5/+bug/2055037/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2055037] Re: My screen radomly starts flickering
Hello Daniel, Thank you for your reply, and I apologise for not getting back to you sooner. In you comment above you mention a typo and a work around, but in which file should I make these changes? please excuse my ignorance in case I have missed something. Many Thanks, Nick. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2055037 Title: My screen radomly starts flickering To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-hwe-6.5/+bug/2055037/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2055037] [NEW] My screen radomly starts flickering
Public bug reported: Hello, I recently installed Ubuntu 22.04.4 on a Lenovo V145-15AST laptop. Randomly, the screen will start flickering. I have found that pulling the power cable out sometimes solves the issue ! But even so, with the power cable out the screen can still start flickering. It's completely random, but very distracting. I am treating this as a bug as I have looked at the options in "Settings > Screen Display" and non of those seem to make any difference. Also I previously tried to install Linux Mint 21.3 and in that case, while booting from the usb stick, I got the welcome to linux mint menu which allows me various options and I select "Start Linux Mint" After that the spinning mint logo appears, then a small mouse pointer on a black screen then the screen goes into some sort of error, a black screen with a few lines at the top. Selecting "Start linux mint in compatability mode" does boot to mint but then the trackpad does not work. I have included this reference to Linux Mint as I believe mint is based on Ubuntu. Many thanks, Nick. ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: xorg 1:7.7+23ubuntu2 ProcVersionSignature: Ubuntu 6.5.0-21.21~22.04.1-generic 6.5.8 Uname: Linux 6.5.0-21-generic x86_64 ApportVersion: 2.20.11-0ubuntu82.5 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CasperMD5CheckResult: pass CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Mon Feb 26 09:33:11 2024 DistUpgraded: Fresh install DistroCodename: jammy DistroVariant: ubuntu ExtraDebuggingInterest: Yes, if not too technical GraphicsCard: Advanced Micro Devices, Inc. [AMD/ATI] Stoney [Radeon R2/R3/R4/R5 Graphics] [1002:98e4] (rev da) (prog-if 00 [VGA controller]) Subsystem: Lenovo Stoney [Radeon R2/R3/R4/R5 Graphics] [17aa:39ec] Subsystem: Lenovo Topaz XT [Radeon R7 M260/M265 / M340/M360 / M440/M445 / 530/535 / 620/625 Mobile] [17aa:39ec] InstallationDate: Installed on 2024-02-24 (1 days ago) InstallationMedia: Ubuntu 22.04.4 LTS "Jammy Jellyfish" - Release amd64 (20240220) MachineType: LENOVO 81MT ProcEnviron: LANGUAGE=en_GB:en PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_GB.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-6.5.0-21-generic root=UUID=e078d5fc-6eaf-4e92-9388-969fa8b6f6db ro 1915.enable_psr=0 SourcePackage: xorg Symptom: display UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 01/12/2021 dmi.bios.release: 2.27 dmi.bios.vendor: LENOVO dmi.bios.version: 8ZCN27WW(V2.06) dmi.board.asset.tag: NO Asset Tag dmi.board.name: LNVNB161216 dmi.board.vendor: LENOVO dmi.board.version: SDK0J40709 WIN dmi.chassis.asset.tag: NO Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: Lenovo V145-15AST dmi.ec.firmware.release: 2.27 dmi.modalias: dmi:bvnLENOVO:bvr8ZCN27WW(V2.06):bd01/12/2021:br2.27:efr2.27:svnLENOVO:pn81MT:pvrLenovoV145-15AST:rvnLENOVO:rnLNVNB161216:rvrSDK0J40709WIN:cvnLENOVO:ct10:cvrLenovoV145-15AST:skuLENOVO_MT_81MT_BU_idea_FM_V145-15AST: dmi.product.family: V145-15AST dmi.product.name: 81MT dmi.product.sku: LENOVO_MT_81MT_BU_idea_FM_V145-15AST dmi.product.version: Lenovo V145-15AST dmi.sys.vendor: LENOVO version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.113-2~ubuntu0.22.04.1 version.libgl1-mesa-dri: libgl1-mesa-dri 23.2.1-1ubuntu3.1~22.04.2 version.libgl1-mesa-glx: libgl1-mesa-glx N/A version.xserver-xorg-core: xserver-xorg-core 2:21.1.4-2ubuntu1.7~22.04.8 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-2ubuntu1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20210115-1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.17-2build1 ** Affects: xorg (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug jammy ubuntu wayland-session -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2055037 Title: My screen radomly starts flickering To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/2055037/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1976518] [NEW] Cannot launch kubuntu-driver-manager on 22.04 Wayland
Public bug reported: On a new installation of Kubuntu 22.04, running Wayland, I am unable to launch the Additional Drivers tool. If I try to do so from either the KDE settings or command line I receive the following errors: sudo kubuntu-driver-manager Authorization required, but no authorization protocol specified qt.qpa.xcb: could not connect to display :0 qt.qpa.plugin: Could not load the Qt platform plugin "xcb" in "" even though it was found. This application failed to start because no Qt platform plugin could be initialized. Reinstalling the application may fix this problem. Available platform plugins are: eglfs, linuxfb, minimal, minimalegl, offscreen, vnc, wayland-egl, wayland, wayland-xcomposite-egl, wayland- xcomposite-glx, xcb. Re-installing with the following command has not helped: sudo apt install --reinstall kubuntu-settings-desktop ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: kubuntu-settings-desktop 1:22.04.10 ProcVersionSignature: Ubuntu 5.15.0-33.34-generic 5.15.30 Uname: Linux 5.15.0-33-generic x86_64 ApportVersion: 2.20.11-0ubuntu82.1 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: KDE Date: Wed Jun 1 15:20:28 2022 InstallationDate: Installed on 2022-06-01 (0 days ago) InstallationMedia: Kubuntu 22.04 LTS "Jammy Jellyfish" - Release amd64 (20220419) PackageArchitecture: all SourcePackage: kubuntu-settings UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: kubuntu-settings (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug jammy wayland-session ** Description changed: On a new installation of Kubuntu 22.04, running Wayland, I am unable to launch the Additional Drivers tool. If I try to do so from either the KDE settings or command line I receive the following errors: - sudo kubuntu-driver-manager + sudo kubuntu-driver-manager Authorization required, but no authorization protocol specified qt.qpa.xcb: could not connect to display :0 qt.qpa.plugin: Could not load the Qt platform plugin "xcb" in "" even though it was found. This application failed to start because no Qt platform plugin could be initialized. Reinstalling the application may fix this problem. Available platform plugins are: eglfs, linuxfb, minimal, minimalegl, offscreen, vnc, wayland-egl, wayland, wayland-xcomposite-egl, wayland- xcomposite-glx, xcb. Re-installing with the following command has not helped: - sudo apt install --reinstall sudo kubuntu-settings-desktop + sudo apt install --reinstall kubuntu-settings-desktop ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: kubuntu-settings-desktop 1:22.04.10 ProcVersionSignature: Ubuntu 5.15.0-33.34-generic 5.15.30 Uname: Linux 5.15.0-33-generic x86_64 ApportVersion: 2.20.11-0ubuntu82.1 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: KDE Date: Wed Jun 1 15:20:28 2022 InstallationDate: Installed on 2022-06-01 (0 days ago) InstallationMedia: Kubuntu 22.04 LTS "Jammy Jellyfish" - Release amd64 (20220419) PackageArchitecture: all SourcePackage: kubuntu-settings UpgradeStatus: No upgrade log present (probably fresh install) -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1976518 Title: Cannot launch kubuntu-driver-manager on 22.04 Wayland To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/kubuntu-settings/+bug/1976518/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1970056] Re: Ubuntu 22.04 unable to mount root partition
@ Haresh Samnani (harry6x): Yes, for me things are back to normal. The laptop boots up normally and the touchpad works normally as well. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1970056 Title: Ubuntu 22.04 unable to mount root partition To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1970056/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1970056] Re: Ubuntu 22.04 unable to mount root partition
Things are back to normal in kernel version 5.18. Laptop boots normally and touchpad works! -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1970056 Title: Ubuntu 22.04 unable to mount root partition To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1970056/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1974237] Re: Telegram Desktop crashes when switching between accounts.
*** This bug is a duplicate of bug 1967673 *** https://bugs.launchpad.net/bugs/1967673 ** This bug has been marked a duplicate of bug 1967673 coredump when attempting to use menu options -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1974237 Title: Telegram Desktop crashes when switching between accounts. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/telegram-desktop/+bug/1974237/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
Re: [Bug 1964710] Re: XSS vulnerability in row_create
Hello! I have tested the fixes in a virtual machine and here are the results. Current version in Impish does not work at all and 1.9.8.2-1ubuntu0.21.10.1 version fixes the problems and is not vulnerable to the XSS in the newRows parameter. Current version for Focal is vulnerable and 1.9.8.2-1ubuntu0.20.04.1 fixes the issue. Although, version in Bionic 1.9.7.1-1ubuntu0.1 has the XSS flaw though the POST parameter 'num', it is hardly exploitable because of CSRF protection. An attacker needs to know somehow a token before he could inject malicious code. In fact, I found other problem with the current version, the file /etc/apache/conf-available/phpliteadmin.conf contains "Depends: php7.0" magic comment that is blocking it from automatic activation by the postinst script. It would be great to replace digit 7.0 with 7.2. Since the original issue is mitigated, let me propose one more one-liner fix. 樂 ** Patch added: "phpliteadmin_1.9.7.1-1ubuntu0.2.debdiff" https://bugs.launchpad.net/bugs/1964710/+attachment/5592042/+files/phpliteadmin_1.9.7.1-1ubuntu0.2.debdiff -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1964710 Title: XSS vulnerability in row_create To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/phpliteadmin/+bug/1964710/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1970056] Re: Ubuntu 22.04 unable to mount root partition
@pstassinos (pstassinos) As a workaround try installing kernel 5.13.19 from https://kernel.ubuntu.com/~kernel-ppa/mainline/ -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1970056 Title: Ubuntu 22.04 unable to mount root partition To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1970056/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1958267] Re: "Connection failed" for WPA Enterprise network eduroam
I recently upgraded to 22.04 on a fresh install and ran into this bug. I am a network administrator at my work and was able to determine on the authentication server was seeing TLS related errors. I made the changes supplied by user nfalse and was able to connect right away. I am willing to test new packages to help squash this behavior. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1958267 Title: "Connection failed" for WPA Enterprise network eduroam To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/wpa/+bug/1958267/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1970056] Re: Ubuntu 22.04 unable to mount root partition
** Changed in: linux (Ubuntu) Status: Incomplete => Confirmed -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1970056 Title: Ubuntu 22.04 unable to mount root partition To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1970056/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1968929] Re: Missing Wayland login option on NVIDIA systems
I can confirm on my Dell XPS15 9570 with hybrid Intel / NVIDIA graphics in on-demand mode that the proposed fix has allowed me to select Wayland in the log-in screen. Thanks. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1968929 Title: Missing Wayland login option on NVIDIA systems To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/1968929/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1970056] WifiSyslog.txt
apport information ** Attachment added: "WifiSyslog.txt" https://bugs.launchpad.net/bugs/1970056/+attachment/5583082/+files/WifiSyslog.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1970056 Title: Ubuntu 22.04 unable to mount root partition To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1970056/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1970056] acpidump.txt
apport information ** Attachment added: "acpidump.txt" https://bugs.launchpad.net/bugs/1970056/+attachment/5583083/+files/acpidump.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1970056 Title: Ubuntu 22.04 unable to mount root partition To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1970056/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1970056] PulseList.txt
apport information ** Attachment added: "PulseList.txt" https://bugs.launchpad.net/bugs/1970056/+attachment/5583079/+files/PulseList.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1970056 Title: Ubuntu 22.04 unable to mount root partition To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1970056/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1970056] UdevDb.txt
apport information ** Attachment added: "UdevDb.txt" https://bugs.launchpad.net/bugs/1970056/+attachment/5583081/+files/UdevDb.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1970056 Title: Ubuntu 22.04 unable to mount root partition To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1970056/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1970056] ProcInterrupts.txt
apport information ** Attachment added: "ProcInterrupts.txt" https://bugs.launchpad.net/bugs/1970056/+attachment/5583077/+files/ProcInterrupts.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1970056 Title: Ubuntu 22.04 unable to mount root partition To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1970056/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1970056] RfKill.txt
apport information ** Attachment added: "RfKill.txt" https://bugs.launchpad.net/bugs/1970056/+attachment/5583080/+files/RfKill.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1970056 Title: Ubuntu 22.04 unable to mount root partition To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1970056/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1970056] ProcModules.txt
apport information ** Attachment added: "ProcModules.txt" https://bugs.launchpad.net/bugs/1970056/+attachment/5583078/+files/ProcModules.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1970056 Title: Ubuntu 22.04 unable to mount root partition To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1970056/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1970056] ProcCpuinfoMinimal.txt
apport information ** Attachment added: "ProcCpuinfoMinimal.txt" https://bugs.launchpad.net/bugs/1970056/+attachment/5583075/+files/ProcCpuinfoMinimal.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1970056 Title: Ubuntu 22.04 unable to mount root partition To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1970056/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1970056] PaInfo.txt
apport information ** Attachment added: "PaInfo.txt" https://bugs.launchpad.net/bugs/1970056/+attachment/5583073/+files/PaInfo.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1970056 Title: Ubuntu 22.04 unable to mount root partition To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1970056/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1970056] ProcEnviron.txt
apport information ** Attachment added: "ProcEnviron.txt" https://bugs.launchpad.net/bugs/1970056/+attachment/5583076/+files/ProcEnviron.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1970056 Title: Ubuntu 22.04 unable to mount root partition To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1970056/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1970056] Lsusb-v.txt
apport information ** Attachment added: "Lsusb-v.txt" https://bugs.launchpad.net/bugs/1970056/+attachment/5583072/+files/Lsusb-v.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1970056 Title: Ubuntu 22.04 unable to mount root partition To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1970056/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1970056] Lspci-vt.txt
apport information ** Attachment added: "Lspci-vt.txt" https://bugs.launchpad.net/bugs/1970056/+attachment/5583070/+files/Lspci-vt.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1970056 Title: Ubuntu 22.04 unable to mount root partition To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1970056/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1970056] Lspci.txt
apport information ** Attachment added: "Lspci.txt" https://bugs.launchpad.net/bugs/1970056/+attachment/5583069/+files/Lspci.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1970056 Title: Ubuntu 22.04 unable to mount root partition To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1970056/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1970056] ProcCpuinfo.txt
apport information ** Attachment added: "ProcCpuinfo.txt" https://bugs.launchpad.net/bugs/1970056/+attachment/5583074/+files/ProcCpuinfo.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1970056 Title: Ubuntu 22.04 unable to mount root partition To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1970056/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1970056] IwConfig.txt
apport information ** Attachment added: "IwConfig.txt" https://bugs.launchpad.net/bugs/1970056/+attachment/5583068/+files/IwConfig.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1970056 Title: Ubuntu 22.04 unable to mount root partition To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1970056/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1970056] Lsusb-t.txt
apport information ** Attachment added: "Lsusb-t.txt" https://bugs.launchpad.net/bugs/1970056/+attachment/5583071/+files/Lsusb-t.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1970056 Title: Ubuntu 22.04 unable to mount root partition To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1970056/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1970056] CurrentDmesg.txt
apport information ** Attachment added: "CurrentDmesg.txt" https://bugs.launchpad.net/bugs/1970056/+attachment/5583067/+files/CurrentDmesg.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1970056 Title: Ubuntu 22.04 unable to mount root partition To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1970056/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1970056] CRDA.txt
apport information ** Attachment added: "CRDA.txt" https://bugs.launchpad.net/bugs/1970056/+attachment/5583066/+files/CRDA.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1970056 Title: Ubuntu 22.04 unable to mount root partition To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1970056/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1970056] Re: Ubuntu 22.04 unable to mount root partition
apport information ** Tags added: apport-collected jammy ** Description changed: After updating from Kubuntu 21.10 to Kubuntu 22.04, boot drops to a (initramfs) prompt/busybox. When I type "exit" I get the "Gave up waiting for root file system device" error message and "ALERT! UUID=[nvme drive UUID] does not exist. Dropping to a shell!" I can still boot into KDE when selecting the older kernel version 5.13.0-40-lowlatency. I have tried the newer kernel versions 5.15.025-generic, 5.15.0.24-lowlatency, 5.17.4-051421-generic and 5.14.21-051421-lowlatency and all have produced the same problem. When removing the the "pci=nocrs" kernel paramater in Grub for these newer versions, the system boots into KDE but the touchpad does not work. Kernel version 5.13.0-40-lowlatency boots into KDE without removing the "pci=nocrs" parameter and everything works as expected, including the touchpad. - My hardware is a Lenovo ideapad lenovo ideapad 3 15IIL05, Processors: 8 - × Intel® Core™ i5-1035G4 CPU @ 1.10GHz, Memory: 7,3 GiB of RAM, Graphics - Processor: Mesa Intel® Iris® Plus Graphics. I have upgraded the hard - drive that came with the machine to a Kingston SA2000M8500G 465,8GiB - nvme drive. + My hardware is a Lenovo ideapad lenovo ideapad 3 15IIL05, Processors: 8 × Intel® Core™ i5-1035G4 CPU @ 1.10GHz, Memory: 7,3 GiB of RAM, Graphics Processor: Mesa Intel® Iris® Plus Graphics. I have upgraded the hard drive that came with the machine to a Kingston SA2000M8500G 465,8GiB nvme drive. + --- + ProblemType: Bug + ApportVersion: 2.20.11-0ubuntu82 + Architecture: amd64 + AudioDevicesInUse: + USERPID ACCESS COMMAND + /dev/snd/controlC0: nick 2376 F jackdbus + /dev/snd/pcmC0D0c: nick 2376 F...m jackdbus + /dev/snd/pcmC0D0p: nick 2376 F...m jackdbus + /dev/snd/seq:nick 2801 F a2jmidid + CasperMD5CheckResult: unknown + CurrentDesktop: KDE + DistroRelease: Ubuntu 22.04 + InstallationDate: Installed on 2020-12-27 (483 days ago) + InstallationMedia: Kubuntu 20.10 "Groovy Gorilla" - Release amd64 (20201022) + Lsusb: + Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub + Bus 001 Device 002: ID 174f:1176 Syntek Integrated Camera + Bus 001 Device 003: ID 8087:0026 Intel Corp. AX201 Bluetooth + Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub + MachineType: LENOVO 81WE + Package: linux (not installed) + ProcFB: 0 i915drmfb + ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.15.0-25-generic root=UUID=5a0515ea-30d8-4412-ad65-8abbd8be949f ro quiet splash + ProcVersionSignature: Ubuntu 5.15.0-25.25-generic 5.15.30 + RelatedPackageVersions: + linux-restricted-modules-5.15.0-25-generic N/A + linux-backports-modules-5.15.0-25-generic N/A + linux-firmware 20220329.git681281e4-0ubuntu1 + Tags: jammy + Uname: Linux 5.15.0-25-generic x86_64 + UpgradeStatus: No upgrade log present (probably fresh install) + UserGroups: adm audio cdrom dip libvirt lpadmin lxd plugdev sambashare sudo www-data + _MarkForUpload: True + dmi.bios.date: 08/10/2020 + dmi.bios.release: 1.40 + dmi.bios.vendor: LENOVO + dmi.bios.version: EMCN40WW + dmi.board.asset.tag: NO Asset Tag + dmi.board.name: LNVNB161216 + dmi.board.vendor: LENOVO + dmi.board.version: SDK0R32866 WIN + dmi.chassis.asset.tag: NO Asset Tag + dmi.chassis.type: 10 + dmi.chassis.vendor: LENOVO + dmi.chassis.version: IdeaPad 3 15IIL05 + dmi.ec.firmware.release: 1.40 + dmi.modalias: dmi:bvnLENOVO:bvrEMCN40WW:bd08/10/2020:br1.40:efr1.40:svnLENOVO:pn81WE:pvrIdeaPad315IIL05:rvnLENOVO:rnLNVNB161216:rvrSDK0R32866WIN:cvnLENOVO:ct10:cvrIdeaPad315IIL05:skuLENOVO_MT_81WE_BU_idea_FM_IdeaPad315IIL05: + dmi.product.family: IdeaPad 3 15IIL05 + dmi.product.name: 81WE + dmi.product.sku: LENOVO_MT_81WE_BU_idea_FM_IdeaPad 3 15IIL05 + dmi.product.version: IdeaPad 3 15IIL05 + dmi.sys.vendor: LENOVO ** Attachment added: "AlsaInfo.txt" https://bugs.launchpad.net/bugs/1970056/+attachment/5583065/+files/AlsaInfo.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1970056 Title: Ubuntu 22.04 unable to mount root partition To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1970056/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1970056] Re: Ubuntu 22.04 unable to mount root partition
** Package changed: ubuntu => linux (Ubuntu) -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1970056 Title: Ubuntu 22.04 unable to mount root partition To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1970056/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1970056] [NEW] Ubuntu 22.04 unable to mount root partition
Public bug reported: After updating from Kubuntu 21.10 to Kubuntu 22.04, boot drops to a (initramfs) prompt/busybox. When I type "exit" I get the "Gave up waiting for root file system device" error message and "ALERT! UUID=[nvme drive UUID] does not exist. Dropping to a shell!" I can still boot into KDE when selecting the older kernel version 5.13.0-40-lowlatency. I have tried the newer kernel versions 5.15.025-generic, 5.15.0.24-lowlatency, 5.17.4-051421-generic and 5.14.21-051421-lowlatency and all have produced the same problem. When removing the the "pci=nocrs" kernel paramater in Grub for these newer versions, the system boots into KDE but the touchpad does not work. Kernel version 5.13.0-40-lowlatency boots into KDE without removing the "pci=nocrs" parameter and everything works as expected, including the touchpad. My hardware is a Lenovo ideapad lenovo ideapad 3 15IIL05, Processors: 8 × Intel® Core™ i5-1035G4 CPU @ 1.10GHz, Memory: 7,3 GiB of RAM, Graphics Processor: Mesa Intel® Iris® Plus Graphics. I have upgraded the hard drive that came with the machine to a Kingston SA2000M8500G 465,8GiB nvme drive. ** Affects: ubuntu Importance: Undecided Status: New ** Summary changed: - Kernel 5.15 and later doesn't mount root partition + Kernel 5.15 and later doesn't mount root partition (Ubuntu 22.04) ** Summary changed: - Kernel 5.15 and later doesn't mount root partition (Ubuntu 22.04) + Ubuntu 22.04 unable to mount root partition -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1970056 Title: Ubuntu 22.04 unable to mount root partition To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+bug/1970056/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1968588] [NEW] Cannot create or add VPN in connection editor
Public bug reported: In 22.04 I am unable to create a new VPN in network manager and nm- connection-editor. After filing in the entire form the save button remains disabled! watching the terminal provides this error: Cannot save connection due to error: Invalid setting General: connection.interface-name: '': interface name must not be empty Seems like the form validator is not looking at the right field! ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: network-manager-gnome 1.24.0-1ubuntu3 ProcVersionSignature: Ubuntu 5.15.0-25.25-generic 5.15.30 Uname: Linux 5.15.0-25-generic x86_64 ApportVersion: 2.20.11-0ubuntu80 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Mon Apr 11 10:49:34 2022 ExecutablePath: /usr/bin/nm-connection-editor InstallationDate: Installed on 2022-04-09 (1 days ago) InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Beta amd64 (20220329.1) IpRoute: default via 10.0.2.2 dev enp0s3 proto dhcp metric 100 10.0.2.0/24 dev enp0s3 proto kernel scope link src 10.0.2.15 metric 100 169.254.0.0/16 dev enp0s3 scope link metric 1000 IwConfig: lono wireless extensions. enp0s3no wireless extensions. ProcEnviron: SHELL=/bin/bash LANG=en_US.UTF-8 TERM=xterm-256color XDG_RUNTIME_DIR= PATH=(custom, no user) RfKill: SourcePackage: network-manager-applet UpgradeStatus: No upgrade log present (probably fresh install) nmcli-con: NAMEUUID TYPE TIMESTAMP TIMESTAMP-REAL AUTOCONNECT AUTOCONNECT-PRIORITY READONLY DBUS-PATH ACTIVE DEVICE STATE ACTIVE-PATH SLAVE FILENAME Wired connection 1 31e61843-ef5f-31e8-96a2-cf86d47e015c ethernet 1649688323 Mon 11 Apr 2022 10:45:23 AM EDT yes -999 no /org/freedesktop/NetworkManager/Settings/1 yes enp0s3 activated /org/freedesktop/NetworkManager/ActiveConnection/1 -- /run/NetworkManager/system-connections/Wired connection 1.nmconnection nmcli-dev: DEVICE TYPE STATE IP4-CONNECTIVITY IP6-CONNECTIVITY DBUS-PATH CONNECTION CON-UUID CON-PATH enp0s3 ethernet connected full limited /org/freedesktop/NetworkManager/Devices/2 Wired connection 1 31e61843-ef5f-31e8-96a2-cf86d47e015c /org/freedesktop/NetworkManager/ActiveConnection/1 lo loopback unmanaged unknown unknown /org/freedesktop/NetworkManager/Devices/1 -- -- -- nmcli-nm: RUNNING VERSION STATE STARTUP CONNECTIVITY NETWORKING WIFI-HW WIFI WWAN-HW WWAN running 1.36.4 connected started full enabled enabled enabled enabled enabled ** Affects: network-manager-applet (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug jammy wayland-session -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1968588 Title: Cannot create or add VPN in connection editor To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/network-manager-applet/+bug/1968588/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1968588] Re: Cannot create or add VPN in connection editor
This also affects the UI connection manager! I merely provided the nm- connection-editor error as you get no error in the UI, the Apply button just remains disabled. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1968588 Title: Cannot create or add VPN in connection editor To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/network-manager-applet/+bug/1968588/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1968537] [NEW] python3.10 clears cli history at exit
Public bug reported: python3.10 overwrites the ~/.python_history file with line '_HiStOrY_V2_' effectively clearing any command line history. Steps to reproduce: 1. Run python3.10 interpreter, type there 'copyright()' command (with no quotes). 2. Exit by pressing Ctrl-D. 3. Run the interpreter again. 4. Press Up arrow to see previous command. Expected behaviour: 1. You see early typed 'copyright()' in the command line. Actual behaviour: 1. Nothing appears, CLI history is clean. ** Affects: python3.10 (Ubuntu) Importance: Undecided Status: New ** Tags: impish -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1968537 Title: python3.10 clears cli history at exit To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/python3.10/+bug/1968537/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1967673] Re: coredump when attempting to use menu options
** Bug watch added: Debian Bug tracker #1008156 https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1008156 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1967673 Title: coredump when attempting to use menu options To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/telegram-desktop/+bug/1967673/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
Re: [Bug 1967673] Re: coredump when attempting to use menu options
M Conrad, I tried retracing coredump from the file you attached. And I can conclude this issue is similar to https://bugs.debian.org/1008156. You can even test a workaround from there. sudo apt-get install libjemalloc2 LD_PRELOAD=libjemalloc.so.2 telegram-desktop Please be careful, you've published crash-dump that in theory may contain secret cookie allowing access to your Telegram session. You'd better terminate it (or them, if you had logged to several accounts) via Settings > Three dots in top-right > Log out. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1967673 Title: coredump when attempting to use menu options To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/telegram-desktop/+bug/1967673/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1967597] [NEW] Evolution cannot get Gmail authorisation
Public bug reported: I have upgraded from 21.10 to 22.04 beta and am trying to set-up Evolution. Right now I am trying to add my Gmail account using the new account wizard. I insert my name and gmail address and then Evolution tries to connect to the GMail authorization page to allow me to enter my password. This opens in a new window and I would expect to see a small embedded web page where I enter my GMail credentials. Instead the window opens but where the embedded web page should be is instead just a small box showing a URL to the Google service. This URL shortly disappears and I am unable to proceed. All I can do is cancel out of the wizard and the account never gets added. One thought which may be relevant is I recently had MS Edge installed and previously I have been able to add an account. I have recently removed this and so instead have just the snap of Firefox installed. Might there be a dependency of Evolution on a browser to provide this web view, and in which case might it not be able to get it from the snap of Firefox? Just a guess. Thanks. ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: evolution 3.44.0-1 ProcVersionSignature: Ubuntu 5.15.0-23.23-generic 5.15.27 Uname: Linux 5.15.0-23-generic x86_64 ApportVersion: 2.20.11-0ubuntu80 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Sat Apr 2 07:19:34 2022 InstallationDate: Installed on 2022-03-01 (31 days ago) InstallationMedia: Ubuntu 21.10 "Impish Indri" - Release amd64 (20211012) SourcePackage: evolution UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: evolution (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug jammy wayland-session ** Attachment added: "Evolution_Gmail_Error.png" https://bugs.launchpad.net/bugs/1967597/+attachment/5576019/+files/Evolution_Gmail_Error.png -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1967597 Title: Evolution cannot get Gmail authorisation To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/evolution/+bug/1967597/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1967596] [NEW] Gnome on-screen keyboard unreliable
Public bug reported: I have upgrade from 21.10 to 22.04 Beta on my Microsoft Surface Go 2 tablet. I generally use it via the tough screen but I also have a type cover I can attach. There are a number of instances where the on-screen keyboard does not appear or does not prove the required input. Examples are as follows: - Firefox (snap) - trying to enter credentials into the Bitwarden extension. Tapping into the text fields does not bring up the keyboard. - Pycharm (snap) - creating a new project in the start-up wizard, tapping in the filename box does not bring up the on screen keyboard. - When you lock the tablet and then try to unlock it via the Gnome unlock screen, tapping in the password box does bring up the keyboard but any keys pressed do not appear in the password box. All of the above can be worked around by attaching the Type Cover and using the physical keyboard. If I an collect any diagnostic data for this please send me the instructions ans I'll see what I can do. Thanks ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: gnome-shell 42.0-1ubuntu1 ProcVersionSignature: Ubuntu 5.15.0-23.23-generic 5.15.27 Uname: Linux 5.15.0-23-generic x86_64 ApportVersion: 2.20.11-0ubuntu80 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Sat Apr 2 07:08:40 2022 DisplayManager: gdm3 InstallationDate: Installed on 2022-03-01 (31 days ago) InstallationMedia: Ubuntu 21.10 "Impish Indri" - Release amd64 (20211012) RelatedPackageVersions: mutter-common 42.0-1ubuntu1 SourcePackage: gnome-shell UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: gnome-shell (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug jammy wayland-session -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1967596 Title: Gnome on-screen keyboard unreliable To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1967596/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1967341] Re: System freeze during upgrade from 21.10 to 22.04 beta
Yes there is - I have just attached it. ** Attachment added: "_usr_bin_do-release-upgrade.0.crash" https://bugs.launchpad.net/ubuntu/+source/ubuntu-release-upgrader/+bug/1967341/+attachment/5575353/+files/_usr_bin_do-release-upgrade.0.crash -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1967341 Title: System freeze during upgrade from 21.10 to 22.04 beta To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubuntu-release-upgrader/+bug/1967341/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1967341] [NEW] System freeze during upgrade from 21.10 to 22.04 beta
Public bug reported: I am running two laptops with 21.10 and have upgraded both to 22.04 using the following commands: sudo apt update; sudo apt upgrade sudo update-manager -d THe update manager wizard starts fine and gets about half way through installing new packages. At this point the screen went blank with just a cursor, followed by my Dell system logo (i.e. looking as if it was rebooting). However the system had frozen at this point and required a power cycle to recover. I then used the grub menu to access the restore session and used the dpkg repair option to complete the package installations. When done I rebooted the laptops and the upgrade appears to have completed OK. This will need to be investigated and solved for mainstream release as most users will not wish to manually restore the upgrade in this way. Thanks Nick ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: ubuntu-release-upgrader-core 1:22.04.7 ProcVersionSignature: Ubuntu 5.15.0-23.23-generic 5.15.27 Uname: Linux 5.15.0-23-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu79 Architecture: amd64 CasperMD5CheckResult: pass CrashDB: ubuntu CurrentDesktop: ubuntu:GNOME Date: Thu Mar 31 18:54:11 2022 InstallationDate: Installed on 2022-02-28 (31 days ago) InstallationMedia: Ubuntu 21.10 "Impish Indri" - Release amd64 (20211012) PackageArchitecture: all SourcePackage: ubuntu-release-upgrader Symptom: ubuntu-release-upgrader UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: ubuntu-release-upgrader (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug dist-upgrade jammy third-party-packages wayland-session -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1967341 Title: System freeze during upgrade from 21.10 to 22.04 beta To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubuntu-release-upgrader/+bug/1967341/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1965558] Re: Cannot change wallpaper by right-clicking image in dark theme
I've just tried this fix in Jammy nightly and it works for me. Thanks! -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1965558 Title: Cannot change wallpaper by right-clicking image in dark theme To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nautilus/+bug/1965558/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1965556] Re: Gnome dialogues light on dark theme with custom highlight color
Just updated my VM with today's updates and the problem seems fixed now. ** Changed in: yaru-theme (Ubuntu) Status: New => Fix Released -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1965556 Title: Gnome dialogues light on dark theme with custom highlight color To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/yaru-theme/+bug/1965556/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1965558] [NEW] Cannot change wallpaper by right-clicking image in dark theme
Public bug reported: With the light theme enabled, you can set the desktop wallpaper by right-clicking on an image file's icon in the file manager and selecting "Set As Wallpaper". When you do this the Desktop wallpaper changes straight away. Now change to dark theme and repeat the above steps. The wallpaper never changes. You can however change the wallpaper fine using Gnome settings -> Appearance. Thanks Nick ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: gnome-control-center 1:41.4-1ubuntu6 ProcVersionSignature: Ubuntu 5.15.0-22.22-generic 5.15.19 Uname: Linux 5.15.0-22-generic x86_64 ApportVersion: 2.20.11-0ubuntu79 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Fri Mar 18 16:14:38 2022 InstallationDate: Installed on 2022-02-28 (18 days ago) InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Alpha amd64 (20220228) SourcePackage: gnome-control-center UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: gnome-control-center (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug jammy -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1965558 Title: Cannot change wallpaper by right-clicking image in dark theme To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-control-center/+bug/1965558/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1965556] [NEW] Gnome dialogues light on dark theme with custom highlight color
Public bug reported: I think I have found a bug in the way the Gnome shell theme reacts to setting a custom highlight color when the dark theme is enabled. Specifically in the Gnome settings, Appearance page, do the following: Select dark theme. Keep the default highlight colour (orange) Now click on the date / time in the Gnome top bar. This menu is dark. Go back to Gnome settings and choose a custom color (i.e. red). Click the date / time again and the menu is now light. Expected results: Should the menus remain dark to follow the dark theme? The new theme & wallpaper looks awesome by the way! Great work. Thanks Nick ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: yaru-theme-gnome-shell 22.04.2 ProcVersionSignature: Ubuntu 5.15.0-22.22-generic 5.15.19 Uname: Linux 5.15.0-22-generic x86_64 ApportVersion: 2.20.11-0ubuntu79 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Fri Mar 18 15:28:18 2022 Dependencies: InstallationDate: Installed on 2022-02-28 (18 days ago) InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Alpha amd64 (20220228) PackageArchitecture: all SourcePackage: yaru-theme UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: yaru-theme (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug jammy -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1965556 Title: Gnome dialogues light on dark theme with custom highlight color To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/yaru-theme/+bug/1965556/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1964710] Re: XSS vulnerability in row_create
** CVE added: https://cve.mitre.org/cgi-bin/cvename.cgi?name=2021-46709 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1964710 Title: XSS vulnerability in row_create To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/phpliteadmin/+bug/1964710/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1964710] Re: XSS vulnerability in row_create
** Description changed: On 21 August 2021, it was publicly reported a little XSS vulnerability in the phpLiteAdmin script packaged in Ubuntu. The following versions of the phpliteadmin package are affected. - * 1.9.8.2-1 echoes GET parameter newRows to HTML with no properly -escaping nor conversion. - * 1.9.7.1-1ubuntu0.1 does similar with POST parameter num. + * 1.9.8.2-1 echoes GET parameter newRows to HTML with no properly + escaping nor conversion. + * 1.9.7.1-1ubuntu0.1 does similar with POST parameter num. + + Upstream bug report: + https://bitbucket.org/phpliteadmin/public/issues/399/xss-vulnerability -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1964710 Title: XSS vulnerability in row_create To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/phpliteadmin/+bug/1964710/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1964708] Re: Fatal error: Uncaught Error: Class "MicroTimer" not found in /usr/share/phpliteadmin/phpliteadmin.php:475
** Patch added: "phpliteadmin_1.9.8.2-1ubuntu0.21.10.1.debdiff" https://bugs.launchpad.net/ubuntu/+source/phpliteadmin/+bug/1964708/+attachment/5568399/+files/phpliteadmin_1.9.8.2-1ubuntu0.21.10.1.debdiff ** Description changed: + [Impact] phpLiteAdmin does not function in Ubuntu 21.10 (Impish Indri). + [Test Plan] Prerequisites: 1. Have the package installed along with php-cli. -$ sudo apt-get install php-cli phpliteadmin + $ sudo apt-get install php-cli phpliteadmin Steps to reproduce: 1. Cd to the package directory and run PHP server as www-data user. -$ cd /usr/share/phpliteadmin -$ sudo -u www-data php -S localhost:8080 + $ cd /usr/share/phpliteadmin + $ sudo -u www-data php -S localhost:8080 2. Open http://localhost:8080/phpliteadmin.php in browser. Actual behavior: 1. No output into browser. 2. Fatal errors in terminal. [Sun Mar 13 12:49:08 2022] 127.0.0.1:55128 Accepted [Sun Mar 13 12:49:08 2022] PHP Fatal error: Uncaught Error: Class "MicroTimer" not found in /usr/share/phpliteadmin/phpliteadmin.php:475 Stack trace: #0 {main} - thrown in /usr/share/phpliteadmin/phpliteadmin.php on line 475 + thrown in /usr/share/phpliteadmin/phpliteadmin.php on line 475 [Sun Mar 13 12:49:08 2022] 127.0.0.1:55128 [500]: GET /phpliteadmin.php - Uncaught Error: Class "MicroTimer" not found in /usr/share/phpliteadmin/phpliteadmin.php:475 Stack trace: #0 {main} - thrown in /usr/share/phpliteadmin/phpliteadmin.php on line 475 + thrown in /usr/share/phpliteadmin/phpliteadmin.php on line 475 [Sun Mar 13 12:49:08 2022] 127.0.0.1:55128 Closing Expected behavior: 1. phpLiteAdmin would work under PHP 8.0.8 which is default in Ubuntu 21.10. + + [Where problems could occur] + Leaf package. Only minimal patch set applied from development branch. ** Summary changed: - Fatal error: Uncaught Error: Class "MicroTimer" not found in /usr/share/phpliteadmin/phpliteadmin.php:475 + SRU: Fatal error: Uncaught Error: Class "MicroTimer" not found in /usr/share/phpliteadmin/phpliteadmin.php:475 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1964708 Title: SRU: Fatal error: Uncaught Error: Class "MicroTimer" not found in /usr/share/phpliteadmin/phpliteadmin.php:475 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/phpliteadmin/+bug/1964708/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1964710] Re: XSS vulnerability in row_create
** Patch added: "phpliteadmin_1.9.7.1-1ubuntu0.2.debdiff" https://bugs.launchpad.net/ubuntu/+source/phpliteadmin/+bug/1964710/+attachment/5568398/+files/phpliteadmin_1.9.7.1-1ubuntu0.2.debdiff ** Information type changed from Public to Public Security -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1964710 Title: XSS vulnerability in row_create To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/phpliteadmin/+bug/1964710/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1964710] Re: XSS vulnerability in row_create
** Patch added: "phpliteadmin_1.9.8.2-1ubuntu0.20.04.1.debdiff" https://bugs.launchpad.net/ubuntu/+source/phpliteadmin/+bug/1964710/+attachment/5568397/+files/phpliteadmin_1.9.8.2-1ubuntu0.20.04.1.debdiff -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1964710 Title: XSS vulnerability in row_create To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/phpliteadmin/+bug/1964710/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1964710] [NEW] XSS vulnerability in row_create
Public bug reported: On 21 August 2021, it was publicly reported a little XSS vulnerability in the phpLiteAdmin script packaged in Ubuntu. The following versions of the phpliteadmin package are affected. * 1.9.8.2-1 echoes GET parameter newRows to HTML with no properly escaping nor conversion. * 1.9.7.1-1ubuntu0.1 does similar with POST parameter num. ** Affects: phpliteadmin (Ubuntu) Importance: Undecided Status: New ** Tags: bionic focal -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1964710 Title: XSS vulnerability in row_create To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/phpliteadmin/+bug/1964710/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1964708] [NEW] Fatal error: Uncaught Error: Class "MicroTimer" not found in /usr/share/phpliteadmin/phpliteadmin.php:475
Public bug reported: phpLiteAdmin does not function in Ubuntu 21.10 (Impish Indri). Prerequisites: 1. Have the package installed along with php-cli. $ sudo apt-get install php-cli phpliteadmin Steps to reproduce: 1. Cd to the package directory and run PHP server as www-data user. $ cd /usr/share/phpliteadmin $ sudo -u www-data php -S localhost:8080 2. Open http://localhost:8080/phpliteadmin.php in browser. Actual behavior: 1. No output into browser. 2. Fatal errors in terminal. [Sun Mar 13 12:49:08 2022] 127.0.0.1:55128 Accepted [Sun Mar 13 12:49:08 2022] PHP Fatal error: Uncaught Error: Class "MicroTimer" not found in /usr/share/phpliteadmin/phpliteadmin.php:475 Stack trace: #0 {main} thrown in /usr/share/phpliteadmin/phpliteadmin.php on line 475 [Sun Mar 13 12:49:08 2022] 127.0.0.1:55128 [500]: GET /phpliteadmin.php - Uncaught Error: Class "MicroTimer" not found in /usr/share/phpliteadmin/phpliteadmin.php:475 Stack trace: #0 {main} thrown in /usr/share/phpliteadmin/phpliteadmin.php on line 475 [Sun Mar 13 12:49:08 2022] 127.0.0.1:55128 Closing Expected behavior: 1. phpLiteAdmin would work under PHP 8.0.8 which is default in Ubuntu 21.10. ** Affects: phpliteadmin (Ubuntu) Importance: Undecided Status: New ** Tags: impish -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1964708 Title: Fatal error: Uncaught Error: Class "MicroTimer" not found in /usr/share/phpliteadmin/phpliteadmin.php:475 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/phpliteadmin/+bug/1964708/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1964706] [NEW] FFe: Sync phpliteadmin 1.9.8.2-2 (universe) from Debian unstable (main)
Public bug reported: Please sync phpliteadmin 1.9.8.2-2 (universe) from Debian unstable (main) Explanation of FeatureFreeze exception: This revision fixes failures under PHP 8 which is now default in Ubuntu. It also fixes a little XSS vulnerability in the row_create action handler. Apart from the fixes, there is a .desktop entry with an icon for quick access from system menu. I would prefer to do full sync rather than split development branches picking the fixes out. Changelog entries since current jammy version 1.9.8.2-1: phpliteadmin (1.9.8.2-2) unstable; urgency=medium * Update link in the debian/control file to moved Salsa repository. * Switch to Application type of .desktop entry. (Closes: #960693) * New Substr-may-be-empty.patch to fix build with PHP 8. (Closes: #1005441) * Fix runtime errors under PHP 8. - New patches: + Nonexistent-get_magic_quotes_gpc.patch + Classes-before-index.patch + Deprecated-each-function.patch + PDO-errmode-silent.patch - Remove number 7 from Apache config. * New Negative-parseSize.patch * New Fix-newRows-XSS.patch. * Add upstream metadata. * Include icon. * Switch to Debhelper compatibility level 13. * Bump Standards Version to 4.6.0, no mandatory changes. -- Nicholas Guriev Sat, 12 Mar 2022 21:02:51 +0300 ** Affects: phpliteadmin (Ubuntu) Importance: Undecided Status: New ** Description changed: Please sync phpliteadmin 1.9.8.2-2 (universe) from Debian unstable (main) Explanation of FeatureFreeze exception: - This revision fixes failures under PHP 8 which is now default in Ubuntu. It - also fixes a little XSS vulnerability in the row_create action handler. Apart - from the fixes, there is a .desktop entry with an icon for quick access from - system menu. + This revision fixes failures under PHP 8 which is now default in Ubuntu. + It also fixes a little XSS vulnerability in the row_create action + handler. Apart from the fixes, there is a .desktop entry with an icon + for quick access from system menu. - I would prefer to do full sync rather than split development branches picking - the fixes out. + I would prefer to do full sync rather than split development branches + picking the fixes out. Changelog entries since current jammy version 1.9.8.2-1: phpliteadmin (1.9.8.2-2) unstable; urgency=medium - * Update link in the debian/control file to moved Salsa repository. - * Switch to Application type of .desktop entry. (Closes: #960693) - * New Substr-may-be-empty.patch to fix build with PHP 8. (Closes: #1005441) - * Fix runtime errors under PHP 8. - - New patches: - + Nonexistent-get_magic_quotes_gpc.patch - + Classes-before-index.patch - + Deprecated-each-function.patch - + PDO-errmode-silent.patch - - Remove number 7 from Apache config. - * New Negative-parseSize.patch - * New Fix-newRows-XSS.patch. - * Add upstream metadata. - * Include icon. - * Switch to Debhelper compatibility level 13. - * Bump Standards Version to 4.6.0, no mandatory changes. + * Update link in the debian/control file to moved Salsa repository. + * Switch to Application type of .desktop entry. (Closes: #960693) + * New Substr-may-be-empty.patch to fix build with PHP 8. (Closes: #1005441) + * Fix runtime errors under PHP 8. + - New patches: + + Nonexistent-get_magic_quotes_gpc.patch + + Classes-before-index.patch + + Deprecated-each-function.patch + + PDO-errmode-silent.patch + - Remove number 7 from Apache config. + * New Negative-parseSize.patch + * New Fix-newRows-XSS.patch. + * Add upstream metadata. + * Include icon. + * Switch to Debhelper compatibility level 13. + * Bump Standards Version to 4.6.0, no mandatory changes. - -- Nicholas Guriev Sat, 12 Mar 2022 21:02:51 +0300 + -- Nicholas Guriev Sat, 12 Mar 2022 21:02:51 +0300 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1964706 Title: FFe: Sync phpliteadmin 1.9.8.2-2 (universe) from Debian unstable (main) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/phpliteadmin/+bug/1964706/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1910938] Re: Text is missing from shell panel and menus
Just got a new Lenovo Thinkpad and using Ubuntu 20.04, and I think I'm seeing a very similar issue. After leaving the laptop on for so long eventually a ton of the text menues and displays either show NO text at all, or half of the characters are missing. I'll attempt a screenshot the next time it happens, it doesn't take longer than a day it seems as already reported. I also use Discord so I wonder if that is part of the culprit as well. Will try using without Discord for about a day. I have found a simple logout/login is enough to fix all text menues. So it doesn't seem a full reboot is strictly necessary. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1910938 Title: Text is missing from shell panel and menus To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1910938/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1963592] [NEW] XSS Remotely
*** This bug is a security vulnerability *** Public security bug reported: NSA DHS FBI CIA AND ALL OTHER Government AGENCIES That DEAL WITH NATIONAL SECURITY AND OR CYBER SECURITIES ABLE TO TAKE OVER ACCOUNT AND ANDROID PLATFORM WITH ANOTHER OS REMOTELY AND BOOTSTRAP A SIDE CAR THIER SYSTEM WITH YOUR ANDROID PAIRING IT WITH THE ATTACKERS SYSTEM THE USER INTERFACE THAT IS ON OTHER DISTRIBUTORS PLATFORMS BOOTSYRAP OR SIDE CAR HAS THE ABILITY TO CHANGE YOUR U DOWNLOAD THE PACKAGES AND THE UI AND OS WITH THERE SYSTEM TO A Different OS AND UI WHILE HAVING FULL ACCESS TO MY ANDROID ALL THE WHILE. MY Original DEVICES ROLE IS SET AT NULL SO THAT SSNDING EMAILS AND SYNC DATA TO BACK UP DOESNT BACK UP ONLY TO THERE FOLDERS THE ATTACKER HAS THREE ACCOUNTS THAT ARE THE SAME AS MINE SO THEY CAROUSEL AND EACH ACCOUNT HAS CERTAIN ROLES IN THE PERMISSIONS. OF THE APPS ON THE ANDROID WHOLE THE ATTACKER CAN MAKE ME NULL WHILE REMOTELY HOSTING THERE CLOUD SERVER. THROUGH MY PHONE THE ADDED SYSTEM THEY PUT ON MY PHONE IS ON A CLOUD SERVER WHILE THE PLAYSTORES APP IS THE SOCKET FOR THE ATTACKER TO GAIN ACCESS Using SYSTEM AS A CLOUD SERVER AND THEN MY PHONES APP THAT PREBUILT WITH THE Manufactures APP IS RUNNING THE OTHER CLOUD IN THE BACK GROUND OF THE ATTACKERS OS SO THEY CAN INJECT CODE SO THEY use use java to XSS illegal codeb A RBITRATION CODE ON WEBSITES COPYRIGHTS ON MANUFACTURES THAT HAVE THE PLATFORMS AND USER INTERFACES IVE SEEN ON MY LG PHONE ARE APPLE Microsoft AMAZON LINUX CHROMEBOOK AND MANY SITES AS WELL THERE REMOTE SIGNAL COMES FROM A SATILITE SIGNAL RECIEVED AND TRANSMITS THE SIGNAL INORDER TO ACTIVATE THE eSim for a second signal done through radio ** Affects: openbios-sparc (Ubuntu) Importance: Undecided Status: New ** Information type changed from Private Security to Public Security -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1963592 Title: XSS Remotely To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/openbios-sparc/+bug/1963592/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1943369] Re: mate-screensaver crashed with SIGSEGV in matemenu_tree_item_ref()
This bug should be considered as security critical. I've just run into the bug, the crash happened when screensaver was active and my laptop unlocked by itself. It'd be great to backport the fix to impish. ||/ Name Version Architecture Description +++--===--= ii mate-screensaver 1.26.0-0ubuntu1 amd64MATE screen saver and locker ii libmate-menu2:amd64 1.26.0-0ubuntu1 amd64implementation of the freedesktop menu specification for MATE (library) dmesg output: [ +5,223792] mate-screensave[44854]: segfault at 0 ip 7ff03ff20b07 sp 7ffce1a529a8 error 6 in libmate-menu.so.2.4.9[7ff03ff1d000+d000] [ +0,26] Code: da fe ff ff e8 8a d6 ff ff 66 2e 0f 1f 84 00 00 00 00 00 f3 0f 1e fa 48 89 f8 f0 83 07 01 c3 0f 1f 40 00 f3 0f 1e fa 48 89 f8 83 07 01 c3 0f 1f 40 00 f3 0f 1e fa f0 83 2f 01 74 06 c3 0f 1f ** Information type changed from Public to Public Security -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1943369 Title: mate-screensaver crashed with SIGSEGV in matemenu_tree_item_ref() To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mate-menus/+bug/1943369/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1955904] Re: Sync glibmm2.4 2.66.2-1 (main) from Debian unstable (main)
** Changed in: glibmm2.4 (Ubuntu) Status: New => Fix Released -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1955904 Title: Sync glibmm2.4 2.66.2-1 (main) from Debian unstable (main) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/glibmm2.4/+bug/1955904/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1960188] [NEW] Ubuntu crashed when I did a restart
Public bug reported: Ubuntu crashed when I did a restart, so I was in the process of reinstalling ubuntu when it also crashed and generated a crash report ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: ubiquity 20.04.15.17 ProcVersionSignature: Ubuntu 5.11.0-27.29~20.04.1-generic 5.11.22 Uname: Linux 5.11.0-27-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.20.11-0ubuntu27.18 Architecture: amd64 CasperMD5CheckResult: pass CasperVersion: 1.445.1 CurrentDesktop: ubuntu:GNOME Date: Mon Feb 7 13:41:42 2022 InstallCmdLine: file=/cdrom/preseed/ubuntu.seed initrd=/casper/initrd quiet splash --- maybe-ubiquity LiveMediaBuild: Ubuntu 20.04.3 LTS "Focal Fossa" - Release amd64 (20210819) ProcEnviron: LANGUAGE=en_AU.UTF-8 PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_AU.UTF-8 LC_NUMERIC=C.UTF-8 SourcePackage: ubiquity UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: ubiquity (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug focal ubiquity-20.04.15.17 ubuntu -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1960188 Title: Ubuntu crashed when I did a restart To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubiquity/+bug/1960188/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1946808] Re: zfs fails reverting to a previous snapshot on reboot when selected on grub
I can also confirm this proposed update fixes my scenario I reports in duplicate bug 1959522. Many thanks. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1946808 Title: zfs fails reverting to a previous snapshot on reboot when selected on grub To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/zfs-linux/+bug/1946808/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1959522] Re: 21.10 Impish ZFS revert snapshot via grub menu fails consistently
*** This bug is a duplicate of bug 1946808 *** https://bugs.launchpad.net/bugs/1946808 As described in bug 1946808 I have enabled impish-proposed updates, applied all updates, and rebooted. I then sudo apt purge neofetch to create a testable ZFS snapshot and reboot. I am now able to successfully roll-back this change vat the ZFS snapshot using the GRUB history menu, and so it appears for my tests at least that the proposed update solves this. Nice one! Thanks Nick -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1959522 Title: 21.10 Impish ZFS revert snapshot via grub menu fails consistently To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/zfs-linux/+bug/1959522/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1894329] Re: ZFS revert from grub menu not working.
Possible duplicate on Impish: https://bugs.launchpad.net/ubuntu/+source/zfs-linux/+bug/1959522 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1894329 Title: ZFS revert from grub menu not working. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/zfs-linux/+bug/1894329/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1959522] Re: 21.10 Impish ZFS revert snapshot via grub menu fails consistently
Just spun-up a couple of Gnome Boxes to test this. 21.10 fails as per my description whereas 20.04.03 LTS works fine. Just to be clear I am selecting to revert the snapshot at the top of the list each time (this is the snapshot taken just before neofetch is installed). Meanwhile my main laptop where I first experienced this problem no longer boots and so I am re-installing with the LTS, so for me this is a nasty issue. I do have another test machine and am happy to collect data if required but as I say this can easily be duplicated. Thanks Nick -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1959522 Title: 21.10 Impish ZFS revert snapshot via grub menu fails consistently To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/zfs-linux/+bug/1959522/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1959522] Re: 21.10 Impish ZFS revert snapshot via grub menu fails consistently
Rough guess this relates to the zfs-Linux package. ** Package changed: ubuntu => zfs-linux (Ubuntu) -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1959522 Title: 21.10 Impish ZFS revert snapshot via grub menu fails consistently To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/zfs-linux/+bug/1959522/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1959522] Re: 21.10 Impish ZFS revert snapshot via grub menu fails consistently
** Description changed: This issue seems similar to 1894329 but I can reproduce this consistently in 21.10. Problem description: Unable to reliably revert ZFS snapshots via the Grub menu in Ubuntu 21.10. When attempting a revert I am usually dropped to the emergency mode and have to force a reboot. After that it can take a number of attempts to get the system to reboot to the desktop. Steps to reproduce: Install Ubuntu 21.10 on Intel 64bit with ZFS selected as the filesystem. Do not encrypt. Install all updates. ZFS snapshot is taken automatically. Reboot. Install a simple package i.e. sudo apt install neofetch. Another ZFS snapshot is taken automatically. Reboot and enter the GRUB menu. Enter History menu. - Select Revert to an earlier snapshot. In my case I select the snapshot taken after neofetch was installed. + Select Revert to an earlier snapshot. In my case I select the snapshot taken before neofetch was installed. Select install system files only. Do not select the recovery mode option. System now boots and ends up dropping into emergency mode. I can duplicate this on three different installs. - Expected outcome: The snapshot is correctly reverted and the system boots without user interaction into the snapshot. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1959522 Title: 21.10 Impish ZFS revert snapshot via grub menu fails consistently To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+bug/1959522/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1959522] [NEW] 21.10 Impish ZFS revert snapshot via grub menu fails consistently
Public bug reported: This issue seems similar to 1894329 but I can reproduce this consistently in 21.10. Problem description: Unable to reliably revert ZFS snapshots via the Grub menu in Ubuntu 21.10. When attempting a revert I am usually dropped to the emergency mode and have to force a reboot. After that it can take a number of attempts to get the system to reboot to the desktop. Steps to reproduce: Install Ubuntu 21.10 on Intel 64bit with ZFS selected as the filesystem. Do not encrypt. Install all updates. ZFS snapshot is taken automatically. Reboot. Install a simple package i.e. sudo apt install neofetch. Another ZFS snapshot is taken automatically. Reboot and enter the GRUB menu. Enter History menu. Select Revert to an earlier snapshot. In my case I select the snapshot taken after neofetch was installed. Select install system files only. Do not select the recovery mode option. System now boots and ends up dropping into emergency mode. I can duplicate this on three different installs. Expected outcome: The snapshot is correctly reverted and the system boots without user interaction into the snapshot. ** Affects: ubuntu Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1959522 Title: 21.10 Impish ZFS revert snapshot via grub menu fails consistently To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+bug/1959522/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1942699] Re: SRU: Update Telegram Desktop to 3.1.1
** Tags removed: verification-needed verification-needed-focal ** Tags added: verification-done-focal -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1942699 Title: SRU: Update Telegram Desktop to 3.1.1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libtgowt/+bug/1942699/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
Re: [Bug 1942699] Re: SRU: Update Telegram Desktop to 3.1.1
Hi1 Thank you everyone for participating! I can confirm that version 3.1.1+ds-1~ubuntu20.04.1 of the telegram-desktop package in focal-proposed works okay. I successfully ran the test from the bug description. To verify update of the libtgowt package with the static library, I did two peer-to-peer calls, incoming and outcoming, and I also checked group video chats. They all work as expected. No glitches with UI were noticed, which might appear due to a lower Qt version. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1942699 Title: SRU: Update Telegram Desktop to 3.1.1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libtgowt/+bug/1942699/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1955044] Re: [SRU] /usr/include/glibmm-2.4/glibmm/variant.h:956:24: error: expected unqualified-id before ‘)’ token
** Description changed: There are compilation errors when I try to include the header under C++20 and run default compiler, GCC 11. This is reproducible in Ubuntu 21.10 (Impish Indri) or Ubuntu devel (Jammy Jellyfish) but not in Ubuntu 21.04 (Impish Indri) or Debian unstable. And this is effecting building of the telegram-desktop package. mymedia@barberry:~$ g++ -x c++ -std=gnu++20 -include glibmm.h - <<< 'int main(){}' `pkg-config --cflags --libs glibmm-2.4` -o /dev/null In file included from /usr/include/glibmm-2.4/glibmm/containerhandle_shared.h:23, from /usr/include/glibmm-2.4/glibmm/arrayhandle.h:21, from /usr/include/glibmm-2.4/glibmm.h:92, from : /usr/include/glibmm-2.4/glibmm/variant.h:956:24: error: expected unqualified-id before ‘)’ token 956 | Variant(); |^ /usr/include/glibmm-2.4/glibmm/variant.h:1017:25: error: expected unqualified-id before ‘)’ token 1017 | Variant< Variant >(); | ^ /usr/include/glibmm-2.4/glibmm/variant.h:1070:26: error: expected unqualified-id before ‘)’ token 1070 | Variant(); | ^ /usr/include/glibmm-2.4/glibmm/variant.h:1240:24: error: expected unqualified-id before ‘)’ token 1240 | Variant(); |^ /usr/include/glibmm-2.4/glibmm/variant.h:1286:30: error: expected unqualified-id before ‘)’ token 1286 | Variant< std::pair >() | ^ /usr/include/glibmm-2.4/glibmm/variant.h:1335:29: error: expected unqualified-id before ‘)’ token 1335 | Variant< std::vector >() | ^ /usr/include/glibmm-2.4/glibmm/variant.h:1404:41: error: expected unqualified-id before ‘)’ token 1404 | Variant< std::vector >(); | ^ /usr/include/glibmm-2.4/glibmm/variant.h:1530:39: error: expected unqualified-id before ‘)’ token 1530 | Variant< std::vector >(); | ^ /usr/include/glibmm-2.4/glibmm/variant.h:1606:29: error: expected unqualified-id before ‘)’ token 1606 | Variant< std::map >() | ^ /usr/include/glibmm-2.4/glibmm/variant.h:1679:33: error: expected unqualified-id before ‘)’ token 1679 | Variant>() | ^ In file included from /usr/include/glibmm-2.4/glibmm/variant.h:1742, from /usr/include/glibmm-2.4/glibmm/containerhandle_shared.h:23, from /usr/include/glibmm-2.4/glibmm/arrayhandle.h:21, from /usr/include/glibmm-2.4/glibmm.h:92, from : /usr/include/glibmm-2.4/glibmm/variant_basictypes.h:23:17: error: expected unqualified-id before ‘)’ token 23 | Variant() | ^ /usr/include/glibmm-2.4/glibmm/variant_basictypes.h:66:26: error: expected unqualified-id before ‘)’ token 66 | Variant() | ^ /usr/include/glibmm-2.4/glibmm/variant_basictypes.h:109:19: error: expected unqualified-id before ‘)’ token 109 | Variant() | ^ /usr/include/glibmm-2.4/glibmm/variant_basictypes.h:152:20: error: expected unqualified-id before ‘)’ token 152 | Variant() |^ /usr/include/glibmm-2.4/glibmm/variant_basictypes.h:195:19: error: expected unqualified-id before ‘)’ token 195 | Variant() | ^ /usr/include/glibmm-2.4/glibmm/variant_basictypes.h:244:20: error: expected unqualified-id before ‘)’ token 244 | Variant() |^ /usr/include/glibmm-2.4/glibmm/variant_basictypes.h:287:19: error: expected unqualified-id before ‘)’ token 287 | Variant() | ^ /usr/include/glibmm-2.4/glibmm/variant_basictypes.h:330:20: error: expected unqualified-id before ‘)’ token 330 | Variant() |^ /usr/include/glibmm-2.4/glibmm/variant_basictypes.h:373:19: error: expected unqualified-id before ‘)’ token 373 | Variant() | ^ In file included from /usr/include/glibmm-2.4/glibmm/containerhandle_shared.h:23, from /usr/include/glibmm-2.4/glibmm/arrayhandle.h:21, from /usr/include/glibmm-2.4/glibmm.h:92, from : /usr/include/glibmm-2.4/glibmm/variant.h:1751:1: error: no declaration matches ‘Glib::Variant >::Variant()’ 1751 | Variant< Variant >::Variant() | ^ In file included from /usr/include/glibmm-2.4/glibmm/containerhandle_shared.h:23, from /usr/include/glibmm-2.4/glibmm/arrayhandle.h:21, from /usr/include/glibmm-2.4/glibmm.h:92, from : /usr/include/glibmm-2.4/glibmm/variant.h:1026:12: note: candidate is:
[Bug 1955044] Re: /usr/include/glibmm-2.4/glibmm/variant.h:956:24: error: expected unqualified-id before ‘)’ token
** Description changed: - There are compilation errors when I try to include the header under C++20. + There are compilation errors when I try to include the header under C++20 and run default compiler, GCC 11. This is reproducible in Ubuntu 21.10 (Impish Indri) or Ubuntu devel (Jammy Jellyfish) but not in Ubuntu 21.04 (Impish Indri) or Debian unstable. And this is effecting building of the telegram-desktop package. - mymedia@barberry:~$ g++ -x c++ -std=gnu++20 -include glibmm.h - <<< 'int main(){}' `pkg-config --cflags --libs glibmm-2.4` -o /dev/null + mymedia@barberry:~$ g++ -x c++ -std=gnu++20 -include glibmm.h - <<< 'int main(){}' `pkg-config --cflags --libs glibmm-2.4` -o /dev/null In file included from /usr/include/glibmm-2.4/glibmm/containerhandle_shared.h:23, - from /usr/include/glibmm-2.4/glibmm/arrayhandle.h:21, - from /usr/include/glibmm-2.4/glibmm.h:92, - from : + from /usr/include/glibmm-2.4/glibmm/arrayhandle.h:21, + from /usr/include/glibmm-2.4/glibmm.h:92, + from : /usr/include/glibmm-2.4/glibmm/variant.h:956:24: error: expected unqualified-id before ‘)’ token - 956 | Variant(); - |^ + 956 | Variant(); + |^ /usr/include/glibmm-2.4/glibmm/variant.h:1017:25: error: expected unqualified-id before ‘)’ token - 1017 | Variant< Variant >(); - | ^ + 1017 | Variant< Variant >(); + | ^ /usr/include/glibmm-2.4/glibmm/variant.h:1070:26: error: expected unqualified-id before ‘)’ token - 1070 | Variant(); - | ^ + 1070 | Variant(); + | ^ /usr/include/glibmm-2.4/glibmm/variant.h:1240:24: error: expected unqualified-id before ‘)’ token - 1240 | Variant(); - |^ + 1240 | Variant(); + |^ /usr/include/glibmm-2.4/glibmm/variant.h:1286:30: error: expected unqualified-id before ‘)’ token - 1286 | Variant< std::pair >() - | ^ + 1286 | Variant< std::pair >() + | ^ /usr/include/glibmm-2.4/glibmm/variant.h:1335:29: error: expected unqualified-id before ‘)’ token - 1335 | Variant< std::vector >() - | ^ + 1335 | Variant< std::vector >() + | ^ /usr/include/glibmm-2.4/glibmm/variant.h:1404:41: error: expected unqualified-id before ‘)’ token - 1404 | Variant< std::vector >(); - | ^ + 1404 | Variant< std::vector >(); + | ^ /usr/include/glibmm-2.4/glibmm/variant.h:1530:39: error: expected unqualified-id before ‘)’ token - 1530 | Variant< std::vector >(); - | ^ + 1530 | Variant< std::vector >(); + | ^ /usr/include/glibmm-2.4/glibmm/variant.h:1606:29: error: expected unqualified-id before ‘)’ token - 1606 | Variant< std::map >() - | ^ + 1606 | Variant< std::map >() + | ^ /usr/include/glibmm-2.4/glibmm/variant.h:1679:33: error: expected unqualified-id before ‘)’ token - 1679 | Variant>() - | ^ + 1679 | Variant>() + | ^ In file included from /usr/include/glibmm-2.4/glibmm/variant.h:1742, - from /usr/include/glibmm-2.4/glibmm/containerhandle_shared.h:23, - from /usr/include/glibmm-2.4/glibmm/arrayhandle.h:21, - from /usr/include/glibmm-2.4/glibmm.h:92, - from : + from /usr/include/glibmm-2.4/glibmm/containerhandle_shared.h:23, + from /usr/include/glibmm-2.4/glibmm/arrayhandle.h:21, + from /usr/include/glibmm-2.4/glibmm.h:92, + from : /usr/include/glibmm-2.4/glibmm/variant_basictypes.h:23:17: error: expected unqualified-id before ‘)’ token -23 | Variant() - | ^ + 23 | Variant() + | ^ /usr/include/glibmm-2.4/glibmm/variant_basictypes.h:66:26: error: expected unqualified-id before ‘)’ token -66 | Variant() - | ^ + 66 | Variant() + | ^ /usr/include/glibmm-2.4/glibmm/variant_basictypes.h:109:19: error: expected unqualified-id before ‘)’ token - 109 | Variant() - | ^ + 109 | Variant() + | ^ /usr/include/glibmm-2.4/glibmm/variant_basictypes.h:152:20: error: expected unqualified-id before ‘)’ token - 152 | Variant() - |^ + 152 | Variant() + |^
[Bug 1955044] Re: /usr/include/glibmm-2.4/glibmm/variant.h:956:24: error: expected unqualified-id before ‘)’ token
** Patch added: "glibmm2.4_2.64.2-2ubuntu0.1.debdiff" https://bugs.launchpad.net/ubuntu/+source/glibmm2.4/+bug/1955044/+attachment/5550025/+files/glibmm2.4_2.64.2-2ubuntu0.1.debdiff ** Patch removed: "glibmm2.4_2.64.2-2ubuntu0.1.debdiff" https://bugs.launchpad.net/ubuntu/+source/glibmm2.4/+bug/1955044/+attachment/5550018/+files/glibmm2.4_2.64.2-2ubuntu0.1.debdiff -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1955044 Title: /usr/include/glibmm-2.4/glibmm/variant.h:956:24: error: expected unqualified-id before ‘)’ token To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/glibmm2.4/+bug/1955044/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1955044] Re: /usr/include/glibmm-2.4/glibmm/variant.h:956:24: error: expected unqualified-id before ‘)’ token
** Patch added: "glibmm2.4_2.64.2-2ubuntu0.1.debdiff" https://bugs.launchpad.net/ubuntu/+source/glibmm2.4/+bug/1955044/+attachment/5550018/+files/glibmm2.4_2.64.2-2ubuntu0.1.debdiff -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1955044 Title: /usr/include/glibmm-2.4/glibmm/variant.h:956:24: error: expected unqualified-id before ‘)’ token To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/glibmm2.4/+bug/1955044/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1955904] [NEW] Sync glibmm2.4 2.66.2-1 (main) from Debian unstable (main)
Public bug reported: Please sync glibmm2.4 2.66.2-1 (main) from Debian unstable (main) The version 2.66.1 has an important fix of #1955044 Upstream discussion of the issue: https://mail.gnome.org/archives/gtkmm-list/2021-May/msg7.html Changelog entries since current jammy version 2.64.2-2build1: glibmm2.4 (2.66.2-1) unstable; urgency=high * New upstream release - Fix jackd segfault (Closes: #994969) -- Jeremy Bicha Sun, 10 Oct 2021 20:58:47 -0400 glibmm2.4 (2.66.1-1) unstable; urgency=medium * New upstream release * Build with meson * Build-Depend on glib-networking * debian/rules: Drop unneeded -Wl,--as-needed * Bump debhelper-compat to 13 -- Jeremy Bicha Sun, 19 Sep 2021 09:22:18 -0400 ** Affects: glibmm2.4 (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1955904 Title: Sync glibmm2.4 2.66.2-1 (main) from Debian unstable (main) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/glibmm2.4/+bug/1955904/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1955044] Re: /usr/include/glibmm-2.4/glibmm/variant.h:956:24: error: expected unqualified-id before ‘)’ token
This is already fixed in upstream. Please apply their patch. https://gitlab.gnome.org/GNOME/glibmm/-/merge_requests/50/diffs -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1955044 Title: /usr/include/glibmm-2.4/glibmm/variant.h:956:24: error: expected unqualified-id before ‘)’ token To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/glibmm2.4/+bug/1955044/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1955736] Re: Lintian does not see source packages in non-English directories
This bug report is about 2.104.0ubuntu* versions. 2.111.0ubuntu2 from jammy-proposed works okay. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1955736 Title: Lintian does not see source packages in non-English directories To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/lintian/+bug/1955736/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1955736] [NEW] Lintian does not see source packages in non-English directories
Public bug reported: Lintian in Ubuntu Hirsute Hippo (21.04), Impish Indri (21.10), Jammy Jellyfish (22.04) fails to process source packages in directories with non-ASCI symbols. mymedia@barberry:/tmp/tmp.K4nSmYElkt/test/тест/測試$ apt-get source hello mymedia@barberry:/tmp/tmp.K4nSmYElkt/test/тест/測試$ lintian hello_2.10-2ubuntu3.dsc Skipping hello_2.10-2ubuntu3.dsc: /tmp/tmp.K4nSmYElkt/test/тест/測試/hello_2.10-2ubuntu3.debian.tar.xz does not exist, exiting mymedia@barberry:/tmp/tmp.K4nSmYElkt/test/тест/測試$ LANG=C stat /tmp/tmp.K4nSmYElkt/test/тест/測試/hello_2.10-2ubuntu3.debian.tar.xz File: /tmp/tmp.K4nSmYElkt/test/тест/測試/hello_2.10-2ubuntu3.debian.tar.xz Size: 6760Blocks: 16 IO Block: 4096 regular file Device: fd00h/64768dInode: 11019168Links: 1 Access: (0644/-rw-r--r--) Uid: ( 1000/ mymedia) Gid: ( 1000/ mymedia) Access: 2021-12-25 14:33:37.569009910 +0300 Modify: 2021-06-18 14:13:45.0 +0300 Change: 2021-12-25 14:33:37.353007104 +0300 Birth: 2021-12-25 14:33:37.353007104 +0300 ** Affects: lintian (Ubuntu) Importance: Undecided Status: New ** Tags: hirsute impish jammy -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1955736 Title: Lintian does not see source packages in non-English directories To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/lintian/+bug/1955736/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1955044] [NEW] /usr/include/glibmm-2.4/glibmm/variant.h:956:24: error: expected unqualified-id before ‘)’ token
Public bug reported: There are compilation errors when I try to include the header under C++20. This is reproducible in Ubuntu 21.10 (Impish Indri) or Ubuntu devel (Jammy Jellyfish) but not in Ubuntu 21.04 (Impish Indri) or Debian unstable. And this is effecting building of the telegram-desktop package. mymedia@barberry:~$ g++ -x c++ -std=gnu++20 -include glibmm.h - <<< 'int main(){}' `pkg-config --cflags --libs glibmm-2.4` -o /dev/null In file included from /usr/include/glibmm-2.4/glibmm/containerhandle_shared.h:23, from /usr/include/glibmm-2.4/glibmm/arrayhandle.h:21, from /usr/include/glibmm-2.4/glibmm.h:92, from : /usr/include/glibmm-2.4/glibmm/variant.h:956:24: error: expected unqualified-id before ‘)’ token 956 | Variant(); |^ /usr/include/glibmm-2.4/glibmm/variant.h:1017:25: error: expected unqualified-id before ‘)’ token 1017 | Variant< Variant >(); | ^ /usr/include/glibmm-2.4/glibmm/variant.h:1070:26: error: expected unqualified-id before ‘)’ token 1070 | Variant(); | ^ /usr/include/glibmm-2.4/glibmm/variant.h:1240:24: error: expected unqualified-id before ‘)’ token 1240 | Variant(); |^ /usr/include/glibmm-2.4/glibmm/variant.h:1286:30: error: expected unqualified-id before ‘)’ token 1286 | Variant< std::pair >() | ^ /usr/include/glibmm-2.4/glibmm/variant.h:1335:29: error: expected unqualified-id before ‘)’ token 1335 | Variant< std::vector >() | ^ /usr/include/glibmm-2.4/glibmm/variant.h:1404:41: error: expected unqualified-id before ‘)’ token 1404 | Variant< std::vector >(); | ^ /usr/include/glibmm-2.4/glibmm/variant.h:1530:39: error: expected unqualified-id before ‘)’ token 1530 | Variant< std::vector >(); | ^ /usr/include/glibmm-2.4/glibmm/variant.h:1606:29: error: expected unqualified-id before ‘)’ token 1606 | Variant< std::map >() | ^ /usr/include/glibmm-2.4/glibmm/variant.h:1679:33: error: expected unqualified-id before ‘)’ token 1679 | Variant>() | ^ In file included from /usr/include/glibmm-2.4/glibmm/variant.h:1742, from /usr/include/glibmm-2.4/glibmm/containerhandle_shared.h:23, from /usr/include/glibmm-2.4/glibmm/arrayhandle.h:21, from /usr/include/glibmm-2.4/glibmm.h:92, from : /usr/include/glibmm-2.4/glibmm/variant_basictypes.h:23:17: error: expected unqualified-id before ‘)’ token 23 | Variant() | ^ /usr/include/glibmm-2.4/glibmm/variant_basictypes.h:66:26: error: expected unqualified-id before ‘)’ token 66 | Variant() | ^ /usr/include/glibmm-2.4/glibmm/variant_basictypes.h:109:19: error: expected unqualified-id before ‘)’ token 109 | Variant() | ^ /usr/include/glibmm-2.4/glibmm/variant_basictypes.h:152:20: error: expected unqualified-id before ‘)’ token 152 | Variant() |^ /usr/include/glibmm-2.4/glibmm/variant_basictypes.h:195:19: error: expected unqualified-id before ‘)’ token 195 | Variant() | ^ /usr/include/glibmm-2.4/glibmm/variant_basictypes.h:244:20: error: expected unqualified-id before ‘)’ token 244 | Variant() |^ /usr/include/glibmm-2.4/glibmm/variant_basictypes.h:287:19: error: expected unqualified-id before ‘)’ token 287 | Variant() | ^ /usr/include/glibmm-2.4/glibmm/variant_basictypes.h:330:20: error: expected unqualified-id before ‘)’ token 330 | Variant() |^ /usr/include/glibmm-2.4/glibmm/variant_basictypes.h:373:19: error: expected unqualified-id before ‘)’ token 373 | Variant() | ^ In file included from /usr/include/glibmm-2.4/glibmm/containerhandle_shared.h:23, from /usr/include/glibmm-2.4/glibmm/arrayhandle.h:21, from /usr/include/glibmm-2.4/glibmm.h:92, from : /usr/include/glibmm-2.4/glibmm/variant.h:1751:1: error: no declaration matches ‘Glib::Variant >::Variant()’ 1751 | Variant< Variant >::Variant() | ^ In file included from /usr/include/glibmm-2.4/glibmm/containerhandle_shared.h:23, from /usr/include/glibmm-2.4/glibmm/arrayhandle.h:21, from /usr/include/glibmm-2.4/glibmm.h:92, from : /usr/include/glibmm-2.4/glibmm/variant.h:1026:12: note: candidate is: ‘Glib::Variant >::Variant(GVariant*, bool)’ 1026 | explicit Variant< Variant >(GVariant* castitem, bool take_a_reference = false); |^
Re: [Bug 1943369] Re: mate-screensaver crashed with SIGSEGV in matemenu_tree_item_ref()
On Чт, 2021-12-09 at 20:38 +, John E Bowman wrote: > Dual monitors ViewSonic 22" monitors dimming for no reason that I can > determine. have to reboot to clear problem. > You can call to xrandr(1) to set monitors brightness back to one. Something like: xrandr --output eDP-1 --brightness 1 --output DP-1 --brightness 1 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1943369 Title: mate-screensaver crashed with SIGSEGV in matemenu_tree_item_ref() To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mate-menus/+bug/1943369/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1823299] Re: Package out of date
*** This bug is a duplicate of bug 1942699 *** https://bugs.launchpad.net/bugs/1942699 ** This bug has been marked a duplicate of bug 1942699 SRU: Update Telegram Desktop to 3.1.1 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1823299 Title: Package out of date To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/telegram-desktop/+bug/1823299/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1926165] Re: Bass speakers not enabled on Lenovo Yoga 9i
Thanks for posting the fix, I tired it out on my Yoga 9 14ITL5 on both the Fedora 35 5.14.18-300.fc35.x86_64 kernel and the Ubuntu 21.10 5.13.0-19-generic kernel with minimal luck. With DAC1 and DAC2 at maximum, the rear speaker sounds like nothing is coming out of it. When DAC1 is turned down to 0, there is audio coming out of the rear speaker, however, the audio output quality is rather poor and tinny. Looking at the kernel source, https://github.com/torvalds/linux/commit/9ebaef0540a981093bce5df15af32354d32391d9 it appears that the kernel version the fix was first released in was 5.13rc4 and looks to appear in all newer tags, so the fix should be in use on my system. Based on the experiences shown above, what I'm experiencing doesn't seem to be the right behaviour. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1926165 Title: Bass speakers not enabled on Lenovo Yoga 9i To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1926165/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1950877] [NEW] Cannot write boot record in final phase of install
Public bug reported: At the last phase of the installation, it fail to write some boot record in /dev/sda Maybe I need to choose /dev/sda1 or something ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: ubiquity 21.10.10 ProcVersionSignature: Ubuntu 5.13.0-19.19-generic 5.13.14 Uname: Linux 5.13.0-19-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.20.11-0ubuntu70 Architecture: amd64 CasperMD5CheckResult: pass CasperVersion: 1.465 CurrentDesktop: ubuntu:GNOME Date: Sat Nov 13 17:44:20 2021 InstallCmdLine: BOOT_IMAGE=/casper/vmlinuz file=/cdrom/preseed/ubuntu.seed maybe-ubiquity quiet splash --- LiveMediaBuild: Ubuntu 22.04 LTS "Jammy Jellyfish" - Alpha amd64 (20211105) ProcEnviron: LANGUAGE=en_CA.UTF-8 PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_CA.UTF-8 LC_NUMERIC=C.UTF-8 RebootRequiredPkgs: Error: path contained symlinks. SourcePackage: grub-installer UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: grub-installer (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug jammy ubiquity-21.10.10 ubuntu -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1950877 Title: Cannot write boot record in final phase of install To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/grub-installer/+bug/1950877/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1950834] [NEW] System crash loop randomly.
Public bug reported: The systems seems to crash loop randomly.Audio logs loop at a 2 second interval(approximate). Release:21.10 Package: Ubuntu Base (Released on Nov 1 via software updater) Kernel:5.13.0-22-generic ProblemType: Bug DistroRelease: Ubuntu 21.10 Package: ubuntu-release-upgrader-core 1:21.10.8 ProcVersionSignature: Ubuntu 5.13.0-22.22-generic 5.13.19 Uname: Linux 5.13.0-22-generic x86_64 ApportVersion: 2.20.11-0ubuntu71 Architecture: amd64 CasperMD5CheckResult: unknown CrashDB: ubuntu CurrentDesktop: ubuntu:GNOME Date: Fri Nov 12 16:32:21 2021 InstallationDate: Installed on 2017-03-09 (1709 days ago) InstallationMedia: Ubuntu 16.04.2 LTS "Xenial Xerus" - Release amd64 (20170215.2) PackageArchitecture: all ProcEnviron: LANGUAGE=en_US PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: ubuntu-release-upgrader Symptom: release-upgrade UpgradeStatus: No upgrade log present (probably fresh install) VarLogDistupgradeTermlog: ** Affects: ubuntu-release-upgrader (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug dist-upgrade impish third-party-packages -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1950834 Title: System crash loop randomly. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubuntu-release-upgrader/+bug/1950834/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1885574] Re: Lenovo Ideapad S740 touchscreen is not working
I have a Lenovo Ideapad S740-15IRH and the touchscreen does not work in linux on any distro even with the latest kernel 5.14.14. Is it possible to fix this? ** Changed in: linux (Ubuntu) Status: Expired => Confirmed -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1885574 Title: Lenovo Ideapad S740 touchscreen is not working To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1885574/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1939174] Re: GRUB2 can't boot Linux on HP Dragonfly G2
*** This bug is a duplicate of bug 1939988 *** https://bugs.launchpad.net/bugs/1939988 Okay wait a minute, it IS possible to install Ubuntu by writing the ISO to the bootable key with dd from a machine running Linux. I used dd like so: `sudo dd bs=4M if=/home/noctua/Downloads/ubuntu-21.10-desktop- amd64.iso of=/dev/sdb conv=fdatasync status=progress` and I was amazed that Ubuntu actually booted. It took some time to boot, but I was able to use the installer successfully and I can confirm Ubuntu 21.10 works fine on the Elite Dragonfly G2 (disable PSR using i915.enable_psr=0 in the GRUB config kernel boot parameters after installation to eliminate screen tear and lag). Definitely try doing that. It seems like the HP system firmware has a flaw with being unable to boot certain things. Given that the Fedora USB creator writes the raw ISO to the key, this might be why a Fedora USB key works. I still think this is a flaw that needs to be fixed, but at least there is a workaround. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1939174 Title: GRUB2 can't boot Linux on HP Dragonfly G2 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/grub2-unsigned/+bug/1939174/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1939988] Re: GRUB2 can't boot Linux on HP Dragonfly G2
Okay wait a minute, it IS possible to install Ubuntu by writing the ISO to the bootable key with dd from a machine running Linux. I used dd like so: `sudo dd bs=4M if=/home/noctua/Downloads/ubuntu-21.10-desktop- amd64.iso of=/dev/sdb conv=fdatasync status=progress` and I was amazed that Ubuntu actually booted. It took some time to boot, but I was able to use the installer successfully and I can confirm Ubuntu 21.10 works fine on the Elite Dragonfly G2 (disable PSR using i915.enable_psr=0 in the GRUB config kernel boot parameters after installation to eliminate screen tear and lag). Definitely try doing that. It seems like the HP system firmware has a flaw with being unable to boot certain things. Given that the Fedora USB creator writes the raw ISO to the key, this might be why a Fedora USB key works. I still think this is a flaw that needs to be fixed, but at least there is a workaround. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1939988 Title: GRUB2 can't boot Linux on HP Dragonfly G2 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/grub2/+bug/1939988/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1939174] Re: GRUB2 can't boot Linux on HP Dragonfly G2
*** This bug is a duplicate of bug 1939988 *** https://bugs.launchpad.net/bugs/1939988 This issue affects me as well on the HP Elite Dragonfly G2. It's really awful, I can't even start the boot process on a Ubuntu live installer. It doesn't seem to matter how I format the USB drive either. I have Fedora 34 installed but I cannot boot Ubuntu 20.04, 20.10, 21.04, or 21.10 at all. When selecting an entry with GRUB on a Ubuntu live key, I just get a black screen with a blinking white cursor at the top. What could be the problem? I regret buying this machine immensely, it has issues already with charging and wifi. It seems that the firmware won't allow us to boot Ubuntu or Debian or really any non-Fedora/RHEL distribution. On Parted Magic, I get an "out of memory" error immediately and cannot boot the image. I think this is also what is happening with the Ubuntu live image. Is the firmware reporting available memory incorrectly when attempting to boot or blocking initramfs over a certain size? Is it possible to fix this? Honestly I'm so upset at HP for introducing firmware bugs like this. No one in their right mind would design system firmware like this to prevent the booting of Linux. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1939174 Title: GRUB2 can't boot Linux on HP Dragonfly G2 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/grub2-unsigned/+bug/1939174/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1939988] Re: GRUB2 can't boot Linux on HP Dragonfly G2
This issue affects me as well on the HP Elite Dragonfly G2. It's really awful, I can't even start the boot process on a Ubuntu live installer. It doesn't seem to matter how I format the USB drive either. I have Fedora 34 installed but I cannot boot Ubuntu 20.04, 20.10, 21.04, or 21.10 at all. When selecting an entry with GRUB on a Ubuntu live key, I just get a black screen with a blinking white cursor at the top. What could be the problem? I regret buying this machine immensely, it has issues already with charging and wifi. It seems that the firmware won't allow us to boot Ubuntu or Debian or really any non-Fedora/RHEL distribution. On Parted Magic, I get an "out of memory" error immediately and cannot boot the image. I think this is also what is happening with the Ubuntu live image. Is the firmware reporting available memory incorrectly when attempting to boot or blocking initramfs over a certain size? Is it possible to fix this? Honestly I'm so upset at HP for introducing firmware bugs like this. No one in their right mind would design system firmware like this to prevent the booting of Linux. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1939988 Title: GRUB2 can't boot Linux on HP Dragonfly G2 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/grub2/+bug/1939988/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1942699] Re: SRU: Update Telegram Desktop to 2.9.2
** Description changed: [Impact] - The newer version of Telegram Desktop, 2.9.2, has support new features - that are worth to bring in Ubuntu (video calls, voice chats, several - pinned messages, multiple accounts, comments in channels, auto-deleting - messages, simple image editor). + The newer version of Telegram Desktop, 3.1.1, which is currently in + Ubuntu 21.10 (Impish Indri), provides an important support for 64-bit + user identifiers. In the next few weeks will register users with UID + more than 2 ³¹ - 1 (maximal 32-bit signed number). These users will be + unseen in ancient versions. + + This version also brings many new features including video calls, voice + chats, streaming platform, several pinned messages, multiple accounts, + comments in channels, auto-deleting messages, simple image editor. + Unfortunately, it is huge task to extract an isolated patch which is + responsible for 32-bit to 64-bit migration. I suggest, on an upstream + author's advice, to do full update of the package. Given the nature of the project, it make sense to do regular updates in order to adjust changes of Telegram service and its server protocol. [Test Plan] - Most testing burden rests with the upstream team. I can do smoke tests - of the new features. + 1. Login as a new user with ID over the bound on a test server. +* Provided that you are not logged in, start the app, go to Settings, + type blindly `testmode`. +* Use any number matching the next format: +999661, where X means + any digit. +* Provide auth code 1. +* Choose random account name if needed, then click the "Sign Up" + button. + 2. Make sure you have gotten a long UID. +* Look into an mtp_*.txt debug log. + 3. Login as an old user in another application instance. +* Use phone +999661 and the same auth code. + 4. The new user writes messages to the old user. The second one receives +them regardless of ancient version. + 5. The old user writes messages to the new user. The second one receives +none of them until the old user updates their application. [Regression Potential] Leaf package. Most potential issues are occasional crashes of the application. The new version also offers OpenGL acceleration, but I am going to disable it by default to reduce hardware related problems. [Other Info] The libtgowt source package need to be backported before. It caries a static library for support Telegram calls. Changes in the library do not apply immediately and require recompiling of the telegram-desktop package to be in effect. ** Summary changed: - SRU: Update Telegram Desktop to 2.9.2 + SRU: Update Telegram Desktop to 3.1.1 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1942699 Title: SRU: Update Telegram Desktop to 3.1.1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libtgowt/+bug/1942699/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
Re: [Bug 1942699] Re: SRU: Update Telegram Desktop to 2.9.2
Alexey Klimenko and I checked it out on a test server and found that: * A new 64-bit user is unable to login with Telegram Desktop before v3.0.2 (beta version, was not packaged). * A 32-bit user with the old app do not see a new user, instead the one of them sees @UnsupportedUser64Bot, not real account. * An old user is unable to write to a new user, but a new one can. This is like simplex communication. * An old user can't distinguish different new users. They all write in the same dialog. * New users do not appear on contact list in the old app. There may be other issues. But as for "stop working", I overestimated. Existing installations will continue to work but with degraded operability. There are two rather big commits which introduce 133 scheme layer with a fix for 64-bit UIDs. https://github.com/telegramdesktop/tdesktop/commit/a6c98f4bb44c8a5f55f86ea80f932a5d0a8be1e3 https://github.com/telegramdesktop/tdesktop/commit/e4e5c4a1d23a271dd2b38d6925917b50932191ad Unfortunately, they do not apply cleanly against versions currently in Ubuntu, 2.1.7 or 2.6.1. Adapting the patches will be a pretty difficult task with unreliable result. John Preston, an upstream author, suggested to do a full update of the package. I know Ubuntu has backports pocket for so huge updates. But it seems the backporting process is not started yet. On Вс, 2021-10-10 at 16:46 +, Robie Basak wrote: > Users who prefer the other side of the trade-off already > have that choice via the telegram-desktop snap. Sorry, I do not use snapd. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1942699 Title: SRU: Update Telegram Desktop to 2.9.2 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libtgowt/+bug/1942699/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1942699] Re: SRU: Update Telegram Desktop to 2.9.2
Hello! In the next few weeks, Telegram will migrate from 32-bit user identifiers to 64-bit ones. Version 3.1 is the minimal that supports UIDs over 2 ³¹ - 1. Older version may stop working for new registered users. I think it is worth to have this version in Ubuntu. At least, SRU policy admits such updates. But for now, we should sync version 3.1.1-ds-1 from Debian sid. And then we get a chance to update the LTS release. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1942699 Title: SRU: Update Telegram Desktop to 2.9.2 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libtgowt/+bug/1942699/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1945853] Re: mate-screensaver crashed with SIGSEGV in matemenu_tree_item_ref()
*** This bug is a duplicate of bug 1943369 *** https://bugs.launchpad.net/bugs/1943369 Norbert, I tested an .iso image with VirtualBox and saw Apport window when I was going to turn off the virtual machine. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1945853 Title: mate-screensaver crashed with SIGSEGV in matemenu_tree_item_ref() To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/glib2.0/+bug/1945853/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1898291] Re: Disabled items indistinguishable from active
This is still the issue of Ubuntu MATE 21.10 (Impish Indri) as I tested with a daliy live .iso image either with the Ambiant-MATE or the Yaru- MATE-light themes. ** Changed in: vala-panel-appmenu (Ubuntu) Status: Expired => New ** Also affects: appmenu-registrar (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1898291 Title: Disabled items indistinguishable from active To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/appmenu-registrar/+bug/1898291/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1945853] Re: mate-screensaver crashed with SIGSEGV in matemenu_tree_item_ref()
*** This bug is a duplicate of bug 1943369 *** https://bugs.launchpad.net/bugs/1943369 ** Description changed: - I found this casually when I was testing the latest Ubuntu MATE 21.04 + I found this casually when I was testing the latest Ubuntu MATE 21.10 Beta. I have no idea what may cause the crash. ProblemType: Crash DistroRelease: Ubuntu 21.10 Package: mate-screensaver 1.26.0-0ubuntu1 ProcVersionSignature: Ubuntu 5.13.0-16.16-generic 5.13.13 Uname: Linux 5.13.0-16-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.20.11-0ubuntu69 Architecture: amd64 CasperMD5CheckResult: pass CasperVersion: 1.465 CurrentDesktop: MATE Date: Sat Oct 2 07:53:08 2021 ExecutablePath: /usr/bin/mate-screensaver ExecutableTimestamp: 1629565330 LiveMediaBuild: Ubuntu-MATE 21.10 "Impish Indri" - Beta amd64 (20211002) ProcCmdline: mate-screensaver ProcCwd: /home/ubuntu-mate ProcEnviron: - PATH=(custom, no user) - XDG_RUNTIME_DIR= - LANG=en_US.UTF-8 - SHELL=/bin/bash + PATH=(custom, no user) + XDG_RUNTIME_DIR= + LANG=en_US.UTF-8 + SHELL=/bin/bash SegvAnalysis: - Segfault happened at: 0x7fc222155b07 : lock addl $0x1,(%rdi) - PC (0x7fc222155b07) ok - source "$0x1" ok - destination "(%rdi)" (0x) not located in a known VMA region (needed writable region)! + Segfault happened at: 0x7fc222155b07 : lock addl $0x1,(%rdi) + PC (0x7fc222155b07) ok + source "$0x1" ok + destination "(%rdi)" (0x) not located in a known VMA region (needed writable region)! SegvReason: writing NULL VMA Signal: 11 SourcePackage: mate-screensaver StacktraceTop: - matemenu_tree_item_ref () from /lib/x86_64-linux-gnu/libmate-menu.so.2 - gs_theme_manager_lookup_theme_info () - ?? () - ?? () - g_closure_invoke () from /lib/x86_64-linux-gnu/libgobject-2.0.so.0 + matemenu_tree_item_ref () from /lib/x86_64-linux-gnu/libmate-menu.so.2 + gs_theme_manager_lookup_theme_info () + ?? () + ?? () + g_closure_invoke () from /lib/x86_64-linux-gnu/libgobject-2.0.so.0 Title: mate-screensaver crashed with SIGSEGV in matemenu_tree_item_ref() UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo separator: -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1945853 Title: mate-screensaver crashed with SIGSEGV in matemenu_tree_item_ref() To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mate-screensaver/+bug/1945853/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1898295] Re: One-pixel intervals between windows
Unfortunately, marco 1.26.0 still has the issue either with the Ambian- MATE theme or with the Yaru-MATE-light theme. I retested with the latest .iso live image of Ubuntu MATE 21.10 (Impish Indri) Daily Build. ** Changed in: marco (Ubuntu) Status: Expired => New -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1898295 Title: One-pixel intervals between windows To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/marco/+bug/1898295/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1898292] Re: Last item highlighted instead of app name
Unfortunately, the issue is still present in Ubuntu MATE 21.10 (Impish Indri) Daily Build ** Also affects: appmenu-registrar (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1898292 Title: Last item highlighted instead of app name To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/appmenu-registrar/+bug/1898292/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1945853] [NEW] mate-screensaver crashed with SIGSEGV in matemenu_tree_item_ref()
*** This bug is a duplicate of bug 1943369 *** https://bugs.launchpad.net/bugs/1943369 Public bug reported: I found this casually when I was testing the latest Ubuntu MATE 21.04 Beta. I have no idea what may cause the crash. ProblemType: Crash DistroRelease: Ubuntu 21.10 Package: mate-screensaver 1.26.0-0ubuntu1 ProcVersionSignature: Ubuntu 5.13.0-16.16-generic 5.13.13 Uname: Linux 5.13.0-16-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.20.11-0ubuntu69 Architecture: amd64 CasperMD5CheckResult: pass CasperVersion: 1.465 CurrentDesktop: MATE Date: Sat Oct 2 07:53:08 2021 ExecutablePath: /usr/bin/mate-screensaver ExecutableTimestamp: 1629565330 LiveMediaBuild: Ubuntu-MATE 21.10 "Impish Indri" - Beta amd64 (20211002) ProcCmdline: mate-screensaver ProcCwd: /home/ubuntu-mate ProcEnviron: PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SegvAnalysis: Segfault happened at: 0x7fc222155b07 : lock addl $0x1,(%rdi) PC (0x7fc222155b07) ok source "$0x1" ok destination "(%rdi)" (0x) not located in a known VMA region (needed writable region)! SegvReason: writing NULL VMA Signal: 11 SourcePackage: mate-screensaver StacktraceTop: matemenu_tree_item_ref () from /lib/x86_64-linux-gnu/libmate-menu.so.2 gs_theme_manager_lookup_theme_info () ?? () ?? () g_closure_invoke () from /lib/x86_64-linux-gnu/libgobject-2.0.so.0 Title: mate-screensaver crashed with SIGSEGV in matemenu_tree_item_ref() UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo separator: ** Affects: mate-screensaver (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-crash impish ** Information type changed from Private to Public -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1945853 Title: mate-screensaver crashed with SIGSEGV in matemenu_tree_item_ref() To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mate-screensaver/+bug/1945853/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs