[Touch-packages] [Bug 1716857] Re: nvidia-drm.modeset=1, gdm3 and optimus laptop results in no external monitors detected by Xorg
Closed due to no reply after 5 months. If anyone still experiences problems then please open new bugs for them using the 'ubuntu-bug' command. ** Changed in: nvidia-graphics-drivers-470 (Ubuntu) Status: Incomplete => Won't Fix ** Changed in: systemd (Ubuntu) Status: Incomplete => Won't Fix -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to systemd in Ubuntu. https://bugs.launchpad.net/bugs/1716857 Title: nvidia-drm.modeset=1, gdm3 and optimus laptop results in no external monitors detected by Xorg Status in gdm3 package in Ubuntu: Opinion Status in nvidia-graphics-drivers-375 package in Ubuntu: Won't Fix Status in nvidia-graphics-drivers-418 package in Ubuntu: Won't Fix Status in nvidia-graphics-drivers-430 package in Ubuntu: Won't Fix Status in nvidia-graphics-drivers-435 package in Ubuntu: Won't Fix Status in nvidia-graphics-drivers-470 package in Ubuntu: Won't Fix Status in systemd package in Ubuntu: Won't Fix Bug description: Context: 17.10 development packages, nvidia binary driver 375, modeset=1 for the nvidia driver. ubuntu desktop (gnome shell), fresh install ThinkPad W520 in Nvidia Optimus bios mode. Nvidia profile. Result: no external monitors are detected. xrandr does not even list them as disconnected (normally it would list five external disconnected monitors) lsmod shows that nvidia driver is loaded and the modesetting is working at some level because there is no tearing on the laptop panel Note: modeset=1 is the only way to get flicker-free graphics on the laptop panel. modeset=1 is not the default setting but it is highly desirable. It works if lightdm is used which is why I have reported this against gdm3 My sessions in this configuration have mostly crashed after a few minutes with a gdm3 fail whale message in syslog but nothing else looks interesting. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gdm3/+bug/1716857/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1948339] Re: Logon screen can be bypassed using various shortcuts
hirsute (21.04) is EOL, but Thank you for your research @Bastian ** Tags removed: hirsute -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to lightdm in Ubuntu. https://bugs.launchpad.net/bugs/1948339 Title: Logon screen can be bypassed using various shortcuts Status in Ubuntu MATE: New Status in arctica-greeter package in Ubuntu: New Status in lightdm package in Ubuntu: New Status in mate-settings-daemon package in Ubuntu: New Bug description: Hi, my little daughter discovered a logon screen bypass in Ubuntu Mate 21.10 after hitting the keyboard for a while. It turns out that several keyboard shortcuts are allowed while Ubuntu Mate is locked (arctica-greeter): - Mod4 + S (mate-search-tool) - Mod4 + E (Open Caja / File Explorer) - CTRL + Shift + Esc (mate-system-monitor) - PRNT (Screenshot) All of the mentioned shortcuts could be used to spawn a file explorer (Caja) or various other binaries as user "lightdm", who owns the logon screen. Although an interactive terminal like mate-terminal, xterm, lxterm etc. could not be opened directly, there are various options to run commands as the lightdm user, for example by creating a shell script using "caja", and execute it directly using the GUI. I've attached Proof-of-Concept GIFs for all shortcuts mentioned above. There might be additional shortcuts that could be used to achieve the same, however I'm not aware about every shortcut that is configured, but I suppose that the root cause is located somewhere in arctica- greeter, rather than within every single binary launched by shortcuts. The bug was reproduced on a fresh installation of Ubuntu Mate 21.10. I haven't tested other versions of Ubuntu Mate yet. Please find additional version details below: $ apt-cache policy lightdm lightdm: Installed: 1.30.0-0ubuntu4 Candidate: 1.30.0-0ubuntu4 Version table: *** 1.30.0-0ubuntu4 500 500 http://de.archive.ubuntu.com/ubuntu impish/universe amd64 Packages 100 /var/lib/dpkg/status $ apt-cache policy arctica-greeter arctica-greeter: Installed: 0.99.1.5-2nmu1 Candidate: 0.99.1.5-2nmu1 Version table: *** 0.99.1.5-2nmu1 500 500 http://de.archive.ubuntu.com/ubuntu impish/universe amd64 Packages 100 /var/lib/dpkg/status Thanks, Basti To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-mate/+bug/1948339/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1504724] Re: lightdm crashed with SIGSEGV in munmap()
Thank you for reporting this bug to Ubuntu. Ubuntu 15.10 (wily) reached end-of-life on July 28, 2016. See this document for currently supported Ubuntu releases: https://wiki.ubuntu.com/Releases We appreciate that this bug may be old and you might not be interested in discussing it any more. But if you are then please upgrade to the latest Ubuntu version and re-test. If you then find the bug is still present in the newer Ubuntu version, please add a comment here telling us which new version it is in. ** Changed in: lightdm (Ubuntu) Status: Triaged => Incomplete -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to lightdm in Ubuntu. https://bugs.launchpad.net/bugs/1504724 Title: lightdm crashed with SIGSEGV in munmap() Status in lightdm package in Ubuntu: Incomplete Bug description: crash at startup ProblemType: Crash DistroRelease: Ubuntu 15.10 Package: lightdm 1.16.3-0ubuntu1 ProcVersionSignature: Ubuntu 4.2.0-15.18-generic 4.2.3 Uname: Linux 4.2.0-15-generic x86_64 NonfreeKernelModules: nvidia ApportVersion: 2.19.1-0ubuntu2 Architecture: amd64 Date: Fri Oct 9 23:46:03 2015 ExecutablePath: /usr/sbin/lightdm LightdmGreeterLog: ** Message: Starting lightdm-gtk-greeter 2.0.1 (Aug 7 2015, 01:24:18) ** Message: [Configuration] Reading file: /etc/lightdm/lightdm-gtk-greeter.conf.d/01_ubuntu.conf ** Message: [Configuration] Reading file: /etc/lightdm/lightdm-gtk-greeter.conf.d/99_ubuntu-mate.conf ** Message: [Configuration] Reading file: /etc/lightdm/lightdm-gtk-greeter.conf upstart: indicator-application main process (2433) terminated with status 1 LightdmGreeterLogOld: ** Message: Starting lightdm-gtk-greeter 2.0.1 (Aug 7 2015, 01:24:18) ** Message: [Configuration] Reading file: /etc/lightdm/lightdm-gtk-greeter.conf.d/01_ubuntu.conf ** Message: [Configuration] Reading file: /etc/lightdm/lightdm-gtk-greeter.conf.d/99_ubuntu-mate.conf ** Message: [Configuration] Reading file: /etc/lightdm/lightdm-gtk-greeter.conf upstart: indicator-application main process (2426) killed by TERM signal ProcCmdline: lightdm --session-child 12 19 ProcEnviron: TERM=linux PATH=(custom, no user) SegvAnalysis: Segfault happened at: 0x7f8c59f0fb94 <_dl_fini+452>: add0x8(%rax),%r12 PC (0x7f8c59f0fb94) ok source "0x8(%rax)" (0x7f8c4a545e08) not located in a known VMA region (needed readable region)! destination "%r12" ok SegvReason: reading unknown VMA Signal: 11 SourcePackage: lightdm StacktraceTop: munmap () at ../sysdeps/unix/syscall-template.S:81 _dl_unmap_segments (l=0x1d2c910, l=0x1d2c910) at ./dl-unmap-segments.h:32 _dl_unmap (map=map@entry=0x1d2c910) at ../sysdeps/x86_64/tlsdesc.c:140 _dl_close_worker (map=map@entry=0x1d2c440) at dl-close.c:641 _dl_close_worker (map=0x1d2c440) at dl-close.c:125 Title: lightdm crashed with SIGSEGV in munmap() UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/lightdm/+bug/1504724/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1950697] Re: gray desktop or login loop
Thank you for taking the time to report this bug and helping to make Ubuntu better. Bug reporting is mostly about finding & fixing problems thus preventing future users from hitting the same bug. I suspect a Support site would be more appropriate, eg. https://answers.launchpad.net/ubuntu. You can also find help with your problem in the support forum of your local Ubuntu community http://loco.ubuntu.com/ or asking at https://askubuntu.com or https://ubuntuforums.org, or for more support options please look at https://discourse.ubuntu.com/t/community-support/709 -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to lightdm in Ubuntu. https://bugs.launchpad.net/bugs/1950697 Title: gray desktop or login loop Status in lightdm package in Ubuntu: New Bug description: I'm using Ubuntu 20.04 (all upgrades) I was using MATE until I decided to go back to budgie since MATE started hogging system resources. after removing MATE and trying to login with budgie I only get a gray screen. I reinstalled lightdm, budgie desktop, nvidia drivers, etc. the only desktop environment that I can use is GNOME(Metacity) ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: lightdm 1.30.0-0ubuntu4~20.04.1 ProcVersionSignature: Ubuntu 5.4.0-90.101-generic 5.4.148 Uname: Linux 5.4.0-90-generic x86_64 NonfreeKernelModules: wl nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu27.21 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: GNOME-Flashback:GNOME Date: Thu Nov 11 15:45:05 2021 InstallationDate: Installed on 2017-08-04 (1560 days ago) InstallationMedia: Ubuntu-Budgie 17.04 "Zesty Zapus" - Release amd64 (20170412) LightdmConfig: [Seat:*] autologin-guest=false #autologin-user=diego #autologin-user-timeout=0 SourcePackage: lightdm UpgradeStatus: No upgrade log present (probably fresh install) modified.conffile..etc.default.apport: # set this to 0 to disable apport, or to 1 to enable it # you can temporarily override this with # sudo service apport start force_start=1 enabled=0 mtime.conffile..etc.default.apport: 2019-10-31T12:18:08.840234 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/lightdm/+bug/1950697/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1962818] Re: Jammy Jellyfish LightDM is frozen after long period of inactivity
** Changed in: lightdm (Ubuntu) Status: Incomplete => New -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to lightdm in Ubuntu. https://bugs.launchpad.net/bugs/1962818 Title: Jammy Jellyfish LightDM is frozen after long period of inactivity Status in lightdm package in Ubuntu: New Bug description: Jammy Jellyfish LightDM is frozen after long period of inactivity Latest updates installed, has been happening since first install 2 weeks ago. Upon using the laptop after over night or coming back from work, the screen is frozen. I can move the mouse around but click is unresponsive. To resolve the issue, I ctrl=alt=f2 in order to log into a shell then restart the LightDM services. Those equals signs should be a plus, however it appears my shift key is not working so I will log another bug for that. I am using an XFCE environment. Description: Ubuntu Jammy Jellyfish (development branch) Release: 22.04 lightdm: Installed: 1.30.0-0ubuntu5 Candidate: 1.30.0-0ubuntu5 Version table: *** 1.30.0-0ubuntu5 500 500 http://au.archive.ubuntu.com/ubuntu jammy/universe amd64 Packages 100 /var/lib/dpkg/status --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu78 Architecture: amd64 CasperMD5CheckResult: unknown DistroRelease: Ubuntu 22.04 InstallationDate: Installed on 2022-01-16 (45 days ago) InstallationMedia: Xubuntu 20.04.3 LTS "Focal Fossa" - Release amd64 (20210819.1) Package: lightdm 1.30.0-0ubuntu5 PackageArchitecture: amd64 ProcEnviron: LANGUAGE=en_AU:en TERM=xterm-256color PATH=(custom, no user) LANG=en_AU.UTF-8 SHELL=/bin/bash ProcVersionSignature: Ubuntu 5.15.0-18.18-generic 5.15.12 Tags: jammy Uname: Linux 5.15.0-18-generic x86_64 UpgradeStatus: Upgraded to jammy on 2022-02-18 (13 days ago) UserGroups: N/A _MarkForUpload: True To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/lightdm/+bug/1962818/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1240336] Re: After release upgrade, the user loses permissions for several basic actions in the system
Thank you for reporting this bug to Ubuntu. Ubuntu 16.04 (xenial) reached end-of-standard-support on April 29, 2021. Ubuntu 14.04 (trusty) reached end-of-standard-support on April 25, 2019. See this document for currently supported Ubuntu releases: https://wiki.ubuntu.com/Releases We appreciate that this bug may be old and you might not be interested in discussing it any more. But if you are then please upgrade to the latest Ubuntu version and re-test. If you then find the bug is still present in the newer Ubuntu version, please add a comment here telling us which new version it is in. ** Changed in: lightdm (Ubuntu) Status: Triaged => Incomplete ** Changed in: lxdm (Ubuntu) Status: Triaged => Incomplete ** Changed in: policykit-desktop-privileges (Ubuntu) Status: Triaged => Incomplete -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to lightdm in Ubuntu. https://bugs.launchpad.net/bugs/1240336 Title: After release upgrade, the user loses permissions for several basic actions in the system Status in gdm3 package in Ubuntu: Won't Fix Status in lightdm package in Ubuntu: Incomplete Status in lxdm package in Ubuntu: Incomplete Status in policykit-desktop-privileges package in Ubuntu: Incomplete Bug description: HOW TO REPRODUCE: - Upgrade Ubuntu to the next release. RESULT: - The user looses permissions for several basic actions in the system. ProblemType: Bug DistroRelease: Ubuntu 13.10 Package: policykit-desktop-privileges 0.16 ProcVersionSignature: Ubuntu 3.11.0-12.19-generic 3.11.3 Uname: Linux 3.11.0-12-generic x86_64 ApportVersion: 2.12.5-0ubuntu2 Architecture: amd64 Date: Tue Oct 15 20:20:55 2013 InstallationDate: Installed on 2013-10-09 (7 days ago) InstallationMedia: Ubuntu 13.10 "Saucy Salamander" - Beta amd64 (20131008) MarkForUpload: True PackageArchitecture: all ProcEnviron: LANGUAGE=en_US TERM=xterm PATH=(custom, no user) LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: policykit-desktop-privileges UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gdm3/+bug/1240336/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1473149] Re: Lightdm refuses to work after installing kubuntu-desktop
Thank you for reporting this bug to Ubuntu. Ubuntu 15.04 (vivid) reached end-of-life on February 4, 2016. See this document for currently supported Ubuntu releases: https://wiki.ubuntu.com/Releases We appreciate that this bug may be old and you might not be interested in discussing it any more. But if you are then please upgrade to the latest Ubuntu version and re-test. If you then find the bug is still present in the newer Ubuntu version, please add a comment here telling us which new version it is in. ** Changed in: lightdm (Ubuntu) Status: Triaged => Incomplete -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to lightdm in Ubuntu. https://bugs.launchpad.net/bugs/1473149 Title: Lightdm refuses to work after installing kubuntu-desktop Status in lightdm package in Ubuntu: Incomplete Bug description: After installing kubuntu-desktop meta package I saw a prompt telling me that both sddm and lightdm are available and I am forced to choose one between them.so I chose lightdm.on the next reboot I was unable to use GUI. After 2-3 weeks,I retried using sudo dpkg-reconfigure lightdm and selected lightdm.still fails to run GUI. sddm works fine and is able to handle both Plasma and Unity. Ubuntu 15.04 with lightdm 1.14.2-0ubuntu1 ProblemType: Bug DistroRelease: Ubuntu 15.04 Package: lightdm 1.14.2-0ubuntu1 ProcVersionSignature: Ubuntu 3.19.0-22.22-generic 3.19.8-ckt1 Uname: Linux 3.19.0-22-generic x86_64 NonfreeKernelModules: nvidia ApportVersion: 2.17.2-0ubuntu1.1 Architecture: amd64 CurrentDesktop: KDE Date: Thu Jul 9 21:15:22 2015 InstallationDate: Installed on 2015-06-09 (30 days ago) InstallationMedia: Ubuntu 15.04 "Vivid Vervet" - Release amd64 (20150422) SourcePackage: lightdm UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/lightdm/+bug/1473149/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1963600] [NEW] On upgrade, systemctl and lightdm stop working, leaving the system in a degraded state
Public bug reported: When updating systemd on Jammy or when upgrading Focal to Jammy, it was noticed that when systemd restarts, it will crash lightdm. What is strange is that lightdm never restarts, new ttys don't start and systemctl stops working. I would tell the system get in a degraded state with this particular crash: no easy way to restore the graphical interface, no way to start new ttys and systemctl don't work. When trying to restart lightdm using systemctl, I get the following: Failed to get properties: Failed to activate service 'org.freedesktop.systemd1': timed out (service_start_timeout=25000ms) The upgrade process is still running in the background, but it's hard to return to the graphical interface. I believe this can be a dangerous situation, as the user would be compelled to reboot the system to get the graphical interface back, cancelling the upgrade in the middle of the process and very likely breaking the system. This happened on three different computers, with three different installs. I'm reporting from the computer where this happened first. ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: systemd 249.10-0ubuntu1 ProcVersionSignature: Ubuntu 5.15.0-22.22-generic 5.15.19 Uname: Linux 5.15.0-22-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.20.11-0ubuntu78 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: XFCE Date: Thu Mar 3 23:42:03 2022 InstallationDate: Installed on 2017-06-13 (1724 days ago) InstallationMedia: Xubuntu 17.04 "Zesty Zapus" - Release amd64 (20170412) MachineType: LENOVO 80UG ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.15.0-22-generic root=UUID=6b4ae5c0-c78c-49a6-a1ba-029192618a7a ro quiet kvm.ignore_msrs=1 kvm.report_ignored_msrs=0 kvm.halt_poll_ns=0 kvm.halt_poll_ns_grow=0 i915.enable_gvt=1 nbd.nbds_max=2 nbd.max_part=127 mtrr_gran_size=128M mtrr_chunk_size=256M log_buf_len=128M zswap.enabled=1 zswap.zpool=z3fold usbhid.quirks=0x0079:0x0006:0x10 SourcePackage: systemd SystemdFailedUnits: Error: command ['systemctl', 'status', '--full', '●'] failed with exit code 4: Invalid unit name "●" escaped as "\xe2\x97\x8f" (maybe you should use systemd-escape?). Unit \xe2\x97\x8f.service could not be found. UpgradeStatus: Upgraded to jammy on 2019-12-22 (802 days ago) dmi.bios.date: 08/09/2018 dmi.bios.release: 1.45 dmi.bios.vendor: LENOVO dmi.bios.version: 0XCN45WW dmi.board.asset.tag: NO Asset Tag dmi.board.name: Toronto 4A2 dmi.board.vendor: LENOVO dmi.board.version: SDK0J40679 WIN dmi.chassis.asset.tag: NO Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: Lenovo ideapad 310-14ISK dmi.ec.firmware.release: 1.45 dmi.modalias: dmi:bvnLENOVO:bvr0XCN45WW:bd08/09/2018:br1.45:efr1.45:svnLENOVO:pn80UG:pvrLenovoideapad310-14ISK:rvnLENOVO:rnToronto4A2:rvrSDK0J40679WIN:cvnLENOVO:ct10:cvrLenovoideapad310-14ISK:skuLENOVO_MT_80UG_BU_idea_FM_Lenovoideapad310-14ISK: dmi.product.family: IDEAPAD dmi.product.name: 80UG dmi.product.sku: LENOVO_MT_80UG_BU_idea_FM_Lenovo ideapad 310-14ISK dmi.product.version: Lenovo ideapad 310-14ISK dmi.sys.vendor: LENOVO modified.conffile..etc.cron.daily.apport: [deleted] ** Affects: systemd (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug jammy third-party-packages -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to systemd in Ubuntu. https://bugs.launchpad.net/bugs/1963600 Title: On upgrade, systemctl and lightdm stop working, leaving the system in a degraded state Status in systemd package in Ubuntu: New Bug description: When updating systemd on Jammy or when upgrading Focal to Jammy, it was noticed that when systemd restarts, it will crash lightdm. What is strange is that lightdm never restarts, new ttys don't start and systemctl stops working. I would tell the system get in a degraded state with this particular crash: no easy way to restore the graphical interface, no way to start new ttys and systemctl don't work. When trying to restart lightdm using systemctl, I get the following: Failed to get properties: Failed to activate service 'org.freedesktop.systemd1': timed out (service_start_timeout=25000ms) The upgrade process is still running in the background, but it's hard to return to the graphical interface. I believe this can be a dangerous situation, as the user would be compelled to reboot the system to get the graphical interface back, cancelling the upgrade in the middle of the process and very likely breaking the system. This happened on three different computers, with three different installs. I'm reporting from the computer where this happened first. ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: systemd 249.10-0ubuntu1 ProcVersionSignature: Ubuntu 5.15.0-22.22-generic 5.15.19 Uname: Linux 5.15.0-22-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp
[Touch-packages] [Bug 1963595] [NEW] package linux-firmware 1.187.26 failed to install/upgrade: el subproceso instalado paquete linux-firmware script post-installation devolvió el código de salida de
Public bug reported: When I updated packages from repos, this error appear. ProblemType: Package DistroRelease: Ubuntu 20.04 Package: linux-firmware 1.187.26 ProcVersionSignature: Ubuntu 4.15.0-70.79-generic 4.15.18 Uname: Linux 4.15.0-70-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu27.21 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: gdm1499 F pulseaudio rolando2050 F pulseaudio CasperMD5CheckResult: skip Date: Wed Mar 2 00:24:54 2022 Dependencies: ErrorMessage: el subproceso instalado paquete linux-firmware script post-installation devolvió el código de salida de error 1 HibernationDevice: RESUME=UUID=8bf13fc7-285e-42ac-a5aa-730d1ecadca1 InstallationDate: Installed on 2018-04-27 (1406 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426) Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 005: ID 04ca:3018 Lite-On Technology Corp. Bus 001 Device 003: ID 13d3:5a01 IMC Networks USB2.0 VGA UVC WebCam Bus 001 Device 002: ID 062a:4c01 MosArt Semiconductor Corp. 2.4G Keyboard Mouse Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: ASUSTeK COMPUTER INC. X542UN PackageArchitecture: all ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.15.0-70-generic root=UUID=d72ca49b-f913-4292-9cb4-fa7e3d62ff1d ro quiet splash vt.handoff=7 PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon. Python3Details: /usr/bin/python3.8, Python 3.8.10, python3-minimal, 3.8.2-0ubuntu2 PythonDetails: /usr/bin/python2.7, Python 2.7.18, python-is-python2, 2.7.17-4 RelatedPackageVersions: grub-pc N/A SourcePackage: initramfs-tools Title: package linux-firmware 1.187.26 failed to install/upgrade: el subproceso instalado paquete linux-firmware script post-installation devolvió el código de salida de error 1 UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 09/19/2017 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: X542UN.300 dmi.board.asset.tag: ATN12345678901234567 dmi.board.name: X542UN dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: 1.0 dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: ASUSTeK COMPUTER INC. dmi.chassis.version: 1.0 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrX542UN.300:bd09/19/2017:svnASUSTeKCOMPUTERINC.:pnX542UN:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnX542UN:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0: dmi.product.family: X dmi.product.name: X542UN dmi.product.version: 1.0 dmi.sys.vendor: ASUSTeK COMPUTER INC. ** Affects: initramfs-tools (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-package focal -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to initramfs-tools in Ubuntu. https://bugs.launchpad.net/bugs/1963595 Title: package linux-firmware 1.187.26 failed to install/upgrade: el subproceso instalado paquete linux-firmware script post-installation devolvió el código de salida de error 1 Status in initramfs-tools package in Ubuntu: New Bug description: When I updated packages from repos, this error appear. ProblemType: Package DistroRelease: Ubuntu 20.04 Package: linux-firmware 1.187.26 ProcVersionSignature: Ubuntu 4.15.0-70.79-generic 4.15.18 Uname: Linux 4.15.0-70-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu27.21 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: gdm1499 F pulseaudio rolando2050 F pulseaudio CasperMD5CheckResult: skip Date: Wed Mar 2 00:24:54 2022 Dependencies: ErrorMessage: el subproceso instalado paquete linux-firmware script post-installation devolvió el código de salida de error 1 HibernationDevice: RESUME=UUID=8bf13fc7-285e-42ac-a5aa-730d1ecadca1 InstallationDate: Installed on 2018-04-27 (1406 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426) Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 005: ID 04ca:3018 Lite-On Technology Corp. Bus 001 Device 003: ID 13d3:5a01 IMC Networks USB2.0 VGA UVC WebCam Bus 001 Device 002: ID 062a:4c01 MosArt Semiconductor Corp. 2.4G Keyboard Mouse Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: ASUSTeK COMPUTER INC. X542UN PackageArchitecture: all ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.15.0-70-generic root=UUID=d72ca49b-f913-4292-9cb4-fa7e3d62ff1d ro quiet splash vt.handoff=7 PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon. Python3Details:
[Touch-packages] [Bug 1949621] Re: modemmanager/libmbim cannot make use of Quectel EM120
For Today, the version of MondemManager in jammy 1.18.6 -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to modemmanager in Ubuntu. https://bugs.launchpad.net/bugs/1949621 Title: modemmanager/libmbim cannot make use of Quectel EM120 Status in libmbim package in Ubuntu: New Status in modemmanager package in Ubuntu: New Bug description: As reported on https://gitlab.freedesktop.org/mobile- broadband/ModemManager/-/issues/402, this modem (shipped in many new Lenovo ThinkPad laptops) requires some specific handling as others new modems to performs FCC unlock procedure. A fix has been merged upstream: https://gitlab.freedesktop.org/mobile- broadband/libmbim/-/merge_requests/125/diffs Can we expect to see that merged in the current Ubuntu 21.10 ? I understand it might require a backport, since they merged it against 1.26 and it does not seems to apply cleanly on 1.24. I also suspect upgrading libmbim to 1.26 is not acceptable for impish release. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libmbim/+bug/1949621/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1958019]
> In order to make work the nvidia drivers in the 17-rc6 im just change in > "more drivers" option of ubuntu, the current versión of the nvidia driver > for another (511 to 470 for example). > Im using hybrid graphics mode in the bios. Great discovery on enabling the NVidia drivers under Ubuntu. A side note for Kubuntu users, run: sudo software-properties-qt Then toggle the driver version on the Additional Drivers tab. A second note. In order to boot into discrete graphics mode, change the profile to "nvidia" either in NVidia settings or command line: sudo prime-select nvidia Reboot into BIOS and select the dedicated graphics option. I assigned the following command to a shortcut key to boot reboot directly to BIOS: systemctl reboot --firmware-setup -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to alsa-driver in Ubuntu. https://bugs.launchpad.net/bugs/1958019 Title: [Lenovo Legion7 16ACHg6 82N6, Realtek ALC287, Speaker, Internal] No sound at all Status in sound-2.6 (alsa-kernel): Confirmed Status in alsa-driver package in Ubuntu: Confirmed Bug description: On my Lenovo Legion-7-16ACHg6 laptop I can't hear any sound by internal speakers, but it work by headphones connected to standard jack aux. uname -r 5.11.0-44-generic ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: alsa-base 1.0.25+dfsg-0ubuntu5 ProcVersionSignature: Ubuntu 5.11.0-44.48~20.04.2-generic 5.11.22 Uname: Linux 5.11.0-44-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu27.21 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC2: i3draven 1266 F pulseaudio /dev/snd/controlC0: i3draven 1266 F pulseaudio /dev/snd/controlC1: i3draven 1266 F pulseaudio /dev/snd/pcmC1D0p: i3draven 1266 F...m pulseaudio CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Sat Jan 15 15:10:53 2022 InstallationDate: Installed on 2021-10-11 (96 days ago) InstallationMedia: Ubuntu 20.04.3 LTS "Focal Fossa" - Release amd64 (20210819) PackageArchitecture: all SourcePackage: alsa-driver Symptom: audio Symptom_AlsaPlaybackTest: ALSA playback test through plughw:Generic failed Symptom_Card: Family 17h (Models 10h-1fh) HD Audio Controller - HD-Audio Generic Symptom_DevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC2: i3draven 1266 F pulseaudio /dev/snd/controlC0: i3draven 1266 F pulseaudio /dev/snd/controlC1: i3draven 1266 F pulseaudio /dev/snd/pcmC1D0p: i3draven 1266 F...m pulseaudio Symptom_Jack: Speaker, Internal Symptom_Type: No sound at all Title: [82N6, Realtek ALC287, Speaker, Internal] No sound at all UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 11/08/2021 dmi.bios.release: 1.49 dmi.bios.vendor: LENOVO dmi.bios.version: GKCN49WW dmi.board.asset.tag: NO Asset Tag dmi.board.name: LNVNB161216 dmi.board.vendor: LENOVO dmi.board.version: SDK0R32862 WIN dmi.chassis.asset.tag: NO Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: Legion 7 16ACHg6 dmi.ec.firmware.release: 1.49 dmi.modalias: dmi:bvnLENOVO:bvrGKCN49WW:bd11/08/2021:br1.49:efr1.49:svnLENOVO:pn82N6:pvrLegion716ACHg6:skuLENOVO_MT_82N6_BU_idea_FM_Legion716ACHg6:rvnLENOVO:rnLNVNB161216:rvrSDK0R32862WIN:cvnLENOVO:ct10:cvrLegion716ACHg6: dmi.product.family: Legion 7 16ACHg6 dmi.product.name: 82N6 dmi.product.sku: LENOVO_MT_82N6_BU_idea_FM_Legion 7 16ACHg6 dmi.product.version: Legion 7 16ACHg6 dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/sound-2.6/+bug/1958019/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1962807] Re: segfault in libgtk-x11-2.0.so.0 with several programs
Figured how to get the virtualbox gdb run. ** Attachment added: "gdb-virtualbox.txt" https://bugs.launchpad.net/ubuntu/+source/gtk+2.0/+bug/1962807/+attachment/5565368/+files/gdb-virtualbox.txt -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to gtk+2.0 in Ubuntu. https://bugs.launchpad.net/bugs/1962807 Title: segfault in libgtk-x11-2.0.so.0 with several programs Status in gtk+2.0 package in Ubuntu: Incomplete Bug description: Today I have been encountering segfaults in fcl and virtualbox: Mar 2 07:20:40 Z560 kernel: [817210.808918] show_signal_msg: 12 callbacks suppressed Mar 2 07:20:40 Z560 kernel: [817210.808922] fcl[933482]: segfault at 7fb98814fdb8 ip 7fb96efab218 sp 7ffc4a89b918 error 4 in libgtk-x11-2.0.so.0.2400.32[7fb96ed5b000+27] Mar 2 07:20:40 Z560 kernel: [817210.808932] Code: 79 db ff 48 83 c4 20 5b 5d 41 5c c3 66 0f 1f 44 00 00 48 8b b7 90 00 00 79 48 89 d7 e9 c1 a1 db 58 90 f3 0f 1e fa 48 83 d9 18 <48> 8b 05 99 4b 1a 19 48 89 44 24 08 48 8b 5d 24 08 48 85 c0 74 12 Mar 2 07:20:40 Z560 systemd[1]: Created slice system-systemd\x2dcoredump.slice. Mar 2 07:20:40 Z560 systemd[1]: Started Process Core Dump (PID 933484/UID 0). Mar 2 07:20:40 Z560 systemd-coredump[933485]: Process 933482 (fcl) of user 1000 dumped core.#012#012Stack trace of thread 933482:#012#0 0x7fb96efab218 gtk_option_menu_get_type (libgtk-x11-2.0.so.0 + 0x2b4218)#012#1 0x0002 n/a (n/a + 0x0) Mar 2 07:20:40 Z560 systemd[1]: systemd-coredump@0-933484-0.service: Succeeded. and: Mar 2 07:51:19 Z560 kernel: [819049.877381] VirtualBox[936782]: segfault at 7ff8860b4db8 ip 7ff86cf10218 sp 7ffdd1a53758 error 4 in libgtk-x11-2.0.so.0.2400.32[7ff86ccc+27] Mar 2 07:51:19 Z560 kernel: [819049.877395] Code: 79 db ff 48 83 c4 20 5b 5d 41 5c c3 66 0f 1f 44 00 00 48 8b b7 90 00 00 79 48 89 d7 e9 c1 a1 db 58 90 f3 0f 1e fa 48 83 d9 18 <48> 8b 05 99 4b 1a 19 48 89 44 24 08 48 8b 5d 24 08 48 85 c0 74 12 Mar 2 07:51:19 Z560 systemd[1]: Started Process Core Dump (PID 936794/UID 0). Mar 2 07:51:19 Z560 systemd-coredump[936795]: Process 936782 (VirtualBox) of user 1000 dumped core.#012#012Stack trace of thread 936782:#012#0 0x7ff86cf10218 gtk_option_menu_get_type (libgtk-x11-2.0.so.0 + 0x2b4218)#012#1 0x0002 n/a (n/a + 0x0) Mar 2 07:51:19 Z560 systemd[1]: systemd-coredump@10-936794-0.service: Succeeded. As this library has not changed I am assuming the problem is with one of the libraries it depends upon. Several packages were updated in the past few days, I believe including some that may be the cause of the problem. I have attached a zip with my /var/log/apt/term.log and history.log for inspection. Version of library is 2.24.32-4ubuntu4 and library file is dated 2021-03-31 here. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gtk+2.0/+bug/1962807/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1962807] Re: segfault in libgtk-x11-2.0.so.0 with several programs
Regarding falling back to earlier releases, I have created a local repository on my system. Given this I should be able to place the back- level packages and then force those versions in synaptic. I am not experienced in reading the gdb output, but it seems to me that the call which generates the segfault is from libgail.so and libgail was among those updated on 1 March from ..ubuntu1 to ..ubuntu1.1 version. Given this, would it make sense for me to back-level that one package? Perhaps all those updated to ..ubunto1.1 from ..ubuntu1, which includes gtk updates? I don't want to create more problems by missing co-dependencies in version levels, so I will wait for your guidance before I proceed further. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to gtk+2.0 in Ubuntu. https://bugs.launchpad.net/bugs/1962807 Title: segfault in libgtk-x11-2.0.so.0 with several programs Status in gtk+2.0 package in Ubuntu: Incomplete Bug description: Today I have been encountering segfaults in fcl and virtualbox: Mar 2 07:20:40 Z560 kernel: [817210.808918] show_signal_msg: 12 callbacks suppressed Mar 2 07:20:40 Z560 kernel: [817210.808922] fcl[933482]: segfault at 7fb98814fdb8 ip 7fb96efab218 sp 7ffc4a89b918 error 4 in libgtk-x11-2.0.so.0.2400.32[7fb96ed5b000+27] Mar 2 07:20:40 Z560 kernel: [817210.808932] Code: 79 db ff 48 83 c4 20 5b 5d 41 5c c3 66 0f 1f 44 00 00 48 8b b7 90 00 00 79 48 89 d7 e9 c1 a1 db 58 90 f3 0f 1e fa 48 83 d9 18 <48> 8b 05 99 4b 1a 19 48 89 44 24 08 48 8b 5d 24 08 48 85 c0 74 12 Mar 2 07:20:40 Z560 systemd[1]: Created slice system-systemd\x2dcoredump.slice. Mar 2 07:20:40 Z560 systemd[1]: Started Process Core Dump (PID 933484/UID 0). Mar 2 07:20:40 Z560 systemd-coredump[933485]: Process 933482 (fcl) of user 1000 dumped core.#012#012Stack trace of thread 933482:#012#0 0x7fb96efab218 gtk_option_menu_get_type (libgtk-x11-2.0.so.0 + 0x2b4218)#012#1 0x0002 n/a (n/a + 0x0) Mar 2 07:20:40 Z560 systemd[1]: systemd-coredump@0-933484-0.service: Succeeded. and: Mar 2 07:51:19 Z560 kernel: [819049.877381] VirtualBox[936782]: segfault at 7ff8860b4db8 ip 7ff86cf10218 sp 7ffdd1a53758 error 4 in libgtk-x11-2.0.so.0.2400.32[7ff86ccc+27] Mar 2 07:51:19 Z560 kernel: [819049.877395] Code: 79 db ff 48 83 c4 20 5b 5d 41 5c c3 66 0f 1f 44 00 00 48 8b b7 90 00 00 79 48 89 d7 e9 c1 a1 db 58 90 f3 0f 1e fa 48 83 d9 18 <48> 8b 05 99 4b 1a 19 48 89 44 24 08 48 8b 5d 24 08 48 85 c0 74 12 Mar 2 07:51:19 Z560 systemd[1]: Started Process Core Dump (PID 936794/UID 0). Mar 2 07:51:19 Z560 systemd-coredump[936795]: Process 936782 (VirtualBox) of user 1000 dumped core.#012#012Stack trace of thread 936782:#012#0 0x7ff86cf10218 gtk_option_menu_get_type (libgtk-x11-2.0.so.0 + 0x2b4218)#012#1 0x0002 n/a (n/a + 0x0) Mar 2 07:51:19 Z560 systemd[1]: systemd-coredump@10-936794-0.service: Succeeded. As this library has not changed I am assuming the problem is with one of the libraries it depends upon. Several packages were updated in the past few days, I believe including some that may be the cause of the problem. I have attached a zip with my /var/log/apt/term.log and history.log for inspection. Version of library is 2.24.32-4ubuntu4 and library file is dated 2021-03-31 here. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gtk+2.0/+bug/1962807/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1962818] LightdmUsersConfig.txt
apport information ** Attachment added: "LightdmUsersConfig.txt" https://bugs.launchpad.net/bugs/1962818/+attachment/5565347/+files/LightdmUsersConfig.txt -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to lightdm in Ubuntu. https://bugs.launchpad.net/bugs/1962818 Title: Jammy Jellyfish LightDM is frozen after long period of inactivity Status in lightdm package in Ubuntu: Incomplete Bug description: Jammy Jellyfish LightDM is frozen after long period of inactivity Latest updates installed, has been happening since first install 2 weeks ago. Upon using the laptop after over night or coming back from work, the screen is frozen. I can move the mouse around but click is unresponsive. To resolve the issue, I ctrl=alt=f2 in order to log into a shell then restart the LightDM services. Those equals signs should be a plus, however it appears my shift key is not working so I will log another bug for that. I am using an XFCE environment. Description: Ubuntu Jammy Jellyfish (development branch) Release: 22.04 lightdm: Installed: 1.30.0-0ubuntu5 Candidate: 1.30.0-0ubuntu5 Version table: *** 1.30.0-0ubuntu5 500 500 http://au.archive.ubuntu.com/ubuntu jammy/universe amd64 Packages 100 /var/lib/dpkg/status --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu78 Architecture: amd64 CasperMD5CheckResult: unknown DistroRelease: Ubuntu 22.04 InstallationDate: Installed on 2022-01-16 (45 days ago) InstallationMedia: Xubuntu 20.04.3 LTS "Focal Fossa" - Release amd64 (20210819.1) Package: lightdm 1.30.0-0ubuntu5 PackageArchitecture: amd64 ProcEnviron: LANGUAGE=en_AU:en TERM=xterm-256color PATH=(custom, no user) LANG=en_AU.UTF-8 SHELL=/bin/bash ProcVersionSignature: Ubuntu 5.15.0-18.18-generic 5.15.12 Tags: jammy Uname: Linux 5.15.0-18-generic x86_64 UpgradeStatus: Upgraded to jammy on 2022-02-18 (13 days ago) UserGroups: N/A _MarkForUpload: True To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/lightdm/+bug/1962818/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1962818] ProcCpuinfoMinimal.txt
apport information ** Attachment added: "ProcCpuinfoMinimal.txt" https://bugs.launchpad.net/bugs/1962818/+attachment/5565348/+files/ProcCpuinfoMinimal.txt -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to lightdm in Ubuntu. https://bugs.launchpad.net/bugs/1962818 Title: Jammy Jellyfish LightDM is frozen after long period of inactivity Status in lightdm package in Ubuntu: Incomplete Bug description: Jammy Jellyfish LightDM is frozen after long period of inactivity Latest updates installed, has been happening since first install 2 weeks ago. Upon using the laptop after over night or coming back from work, the screen is frozen. I can move the mouse around but click is unresponsive. To resolve the issue, I ctrl=alt=f2 in order to log into a shell then restart the LightDM services. Those equals signs should be a plus, however it appears my shift key is not working so I will log another bug for that. I am using an XFCE environment. Description: Ubuntu Jammy Jellyfish (development branch) Release: 22.04 lightdm: Installed: 1.30.0-0ubuntu5 Candidate: 1.30.0-0ubuntu5 Version table: *** 1.30.0-0ubuntu5 500 500 http://au.archive.ubuntu.com/ubuntu jammy/universe amd64 Packages 100 /var/lib/dpkg/status --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu78 Architecture: amd64 CasperMD5CheckResult: unknown DistroRelease: Ubuntu 22.04 InstallationDate: Installed on 2022-01-16 (45 days ago) InstallationMedia: Xubuntu 20.04.3 LTS "Focal Fossa" - Release amd64 (20210819.1) Package: lightdm 1.30.0-0ubuntu5 PackageArchitecture: amd64 ProcEnviron: LANGUAGE=en_AU:en TERM=xterm-256color PATH=(custom, no user) LANG=en_AU.UTF-8 SHELL=/bin/bash ProcVersionSignature: Ubuntu 5.15.0-18.18-generic 5.15.12 Tags: jammy Uname: Linux 5.15.0-18-generic x86_64 UpgradeStatus: Upgraded to jammy on 2022-02-18 (13 days ago) UserGroups: N/A _MarkForUpload: True To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/lightdm/+bug/1962818/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1962818] Re: Jammy Jellyfish LightDM is frozen after long period of inactivity
apport information ** Tags added: apport-collected jammy ** Description changed: Jammy Jellyfish LightDM is frozen after long period of inactivity Latest updates installed, has been happening since first install 2 weeks ago. Upon using the laptop after over night or coming back from work, the screen is frozen. I can move the mouse around but click is unresponsive. To resolve the issue, I ctrl=alt=f2 in order to log into a shell then restart the LightDM services. Those equals signs should be a plus, however it appears my shift key is not working so I will log another bug for that. I am using an XFCE environment. Description: Ubuntu Jammy Jellyfish (development branch) Release: 22.04 lightdm: Installed: 1.30.0-0ubuntu5 Candidate: 1.30.0-0ubuntu5 Version table: *** 1.30.0-0ubuntu5 500 500 http://au.archive.ubuntu.com/ubuntu jammy/universe amd64 Packages 100 /var/lib/dpkg/status + --- + ProblemType: Bug + ApportVersion: 2.20.11-0ubuntu78 + Architecture: amd64 + CasperMD5CheckResult: unknown + DistroRelease: Ubuntu 22.04 + InstallationDate: Installed on 2022-01-16 (45 days ago) + InstallationMedia: Xubuntu 20.04.3 LTS "Focal Fossa" - Release amd64 (20210819.1) + Package: lightdm 1.30.0-0ubuntu5 + PackageArchitecture: amd64 + ProcEnviron: + LANGUAGE=en_AU:en + TERM=xterm-256color + PATH=(custom, no user) + LANG=en_AU.UTF-8 + SHELL=/bin/bash + ProcVersionSignature: Ubuntu 5.15.0-18.18-generic 5.15.12 + Tags: jammy + Uname: Linux 5.15.0-18-generic x86_64 + UpgradeStatus: Upgraded to jammy on 2022-02-18 (13 days ago) + UserGroups: N/A + _MarkForUpload: True ** Attachment added: "Dependencies.txt" https://bugs.launchpad.net/bugs/1962818/+attachment/5565346/+files/Dependencies.txt -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to lightdm in Ubuntu. https://bugs.launchpad.net/bugs/1962818 Title: Jammy Jellyfish LightDM is frozen after long period of inactivity Status in lightdm package in Ubuntu: Incomplete Bug description: Jammy Jellyfish LightDM is frozen after long period of inactivity Latest updates installed, has been happening since first install 2 weeks ago. Upon using the laptop after over night or coming back from work, the screen is frozen. I can move the mouse around but click is unresponsive. To resolve the issue, I ctrl=alt=f2 in order to log into a shell then restart the LightDM services. Those equals signs should be a plus, however it appears my shift key is not working so I will log another bug for that. I am using an XFCE environment. Description: Ubuntu Jammy Jellyfish (development branch) Release: 22.04 lightdm: Installed: 1.30.0-0ubuntu5 Candidate: 1.30.0-0ubuntu5 Version table: *** 1.30.0-0ubuntu5 500 500 http://au.archive.ubuntu.com/ubuntu jammy/universe amd64 Packages 100 /var/lib/dpkg/status --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu78 Architecture: amd64 CasperMD5CheckResult: unknown DistroRelease: Ubuntu 22.04 InstallationDate: Installed on 2022-01-16 (45 days ago) InstallationMedia: Xubuntu 20.04.3 LTS "Focal Fossa" - Release amd64 (20210819.1) Package: lightdm 1.30.0-0ubuntu5 PackageArchitecture: amd64 ProcEnviron: LANGUAGE=en_AU:en TERM=xterm-256color PATH=(custom, no user) LANG=en_AU.UTF-8 SHELL=/bin/bash ProcVersionSignature: Ubuntu 5.15.0-18.18-generic 5.15.12 Tags: jammy Uname: Linux 5.15.0-18-generic x86_64 UpgradeStatus: Upgraded to jammy on 2022-02-18 (13 days ago) UserGroups: N/A _MarkForUpload: True To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/lightdm/+bug/1962818/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1962807] Re: segfault in libgtk-x11-2.0.so.0 with several programs
I attempted to use gdb on virtualbox first, but received errors. Given this I was able to provide what you wanted with fcl. Hopefully it will provide you with enough information to diagnose the problem. ** Attachment added: "gdb-fcl.txt" https://bugs.launchpad.net/ubuntu/+source/gtk+2.0/+bug/1962807/+attachment/5565328/+files/gdb-fcl.txt -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to gtk+2.0 in Ubuntu. https://bugs.launchpad.net/bugs/1962807 Title: segfault in libgtk-x11-2.0.so.0 with several programs Status in gtk+2.0 package in Ubuntu: Incomplete Bug description: Today I have been encountering segfaults in fcl and virtualbox: Mar 2 07:20:40 Z560 kernel: [817210.808918] show_signal_msg: 12 callbacks suppressed Mar 2 07:20:40 Z560 kernel: [817210.808922] fcl[933482]: segfault at 7fb98814fdb8 ip 7fb96efab218 sp 7ffc4a89b918 error 4 in libgtk-x11-2.0.so.0.2400.32[7fb96ed5b000+27] Mar 2 07:20:40 Z560 kernel: [817210.808932] Code: 79 db ff 48 83 c4 20 5b 5d 41 5c c3 66 0f 1f 44 00 00 48 8b b7 90 00 00 79 48 89 d7 e9 c1 a1 db 58 90 f3 0f 1e fa 48 83 d9 18 <48> 8b 05 99 4b 1a 19 48 89 44 24 08 48 8b 5d 24 08 48 85 c0 74 12 Mar 2 07:20:40 Z560 systemd[1]: Created slice system-systemd\x2dcoredump.slice. Mar 2 07:20:40 Z560 systemd[1]: Started Process Core Dump (PID 933484/UID 0). Mar 2 07:20:40 Z560 systemd-coredump[933485]: Process 933482 (fcl) of user 1000 dumped core.#012#012Stack trace of thread 933482:#012#0 0x7fb96efab218 gtk_option_menu_get_type (libgtk-x11-2.0.so.0 + 0x2b4218)#012#1 0x0002 n/a (n/a + 0x0) Mar 2 07:20:40 Z560 systemd[1]: systemd-coredump@0-933484-0.service: Succeeded. and: Mar 2 07:51:19 Z560 kernel: [819049.877381] VirtualBox[936782]: segfault at 7ff8860b4db8 ip 7ff86cf10218 sp 7ffdd1a53758 error 4 in libgtk-x11-2.0.so.0.2400.32[7ff86ccc+27] Mar 2 07:51:19 Z560 kernel: [819049.877395] Code: 79 db ff 48 83 c4 20 5b 5d 41 5c c3 66 0f 1f 44 00 00 48 8b b7 90 00 00 79 48 89 d7 e9 c1 a1 db 58 90 f3 0f 1e fa 48 83 d9 18 <48> 8b 05 99 4b 1a 19 48 89 44 24 08 48 8b 5d 24 08 48 85 c0 74 12 Mar 2 07:51:19 Z560 systemd[1]: Started Process Core Dump (PID 936794/UID 0). Mar 2 07:51:19 Z560 systemd-coredump[936795]: Process 936782 (VirtualBox) of user 1000 dumped core.#012#012Stack trace of thread 936782:#012#0 0x7ff86cf10218 gtk_option_menu_get_type (libgtk-x11-2.0.so.0 + 0x2b4218)#012#1 0x0002 n/a (n/a + 0x0) Mar 2 07:51:19 Z560 systemd[1]: systemd-coredump@10-936794-0.service: Succeeded. As this library has not changed I am assuming the problem is with one of the libraries it depends upon. Several packages were updated in the past few days, I believe including some that may be the cause of the problem. I have attached a zip with my /var/log/apt/term.log and history.log for inspection. Version of library is 2.24.32-4ubuntu4 and library file is dated 2021-03-31 here. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gtk+2.0/+bug/1962807/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1962807] Re: segfault in libgtk-x11-2.0.so.0 with several programs
Could you try to follow https://wiki.ubuntu.com/Backtrace to provide more details on the crash? The log suggest you didn't update much but that includes glibc, do you know your way around dpkg and apt enough to try to go back to the binary packages from https://launchpad.net/ubuntu/+source/glibc/2.31-0ubuntu9.5 and see if that resolves your issue? -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to gtk+2.0 in Ubuntu. https://bugs.launchpad.net/bugs/1962807 Title: segfault in libgtk-x11-2.0.so.0 with several programs Status in gtk+2.0 package in Ubuntu: Incomplete Bug description: Today I have been encountering segfaults in fcl and virtualbox: Mar 2 07:20:40 Z560 kernel: [817210.808918] show_signal_msg: 12 callbacks suppressed Mar 2 07:20:40 Z560 kernel: [817210.808922] fcl[933482]: segfault at 7fb98814fdb8 ip 7fb96efab218 sp 7ffc4a89b918 error 4 in libgtk-x11-2.0.so.0.2400.32[7fb96ed5b000+27] Mar 2 07:20:40 Z560 kernel: [817210.808932] Code: 79 db ff 48 83 c4 20 5b 5d 41 5c c3 66 0f 1f 44 00 00 48 8b b7 90 00 00 79 48 89 d7 e9 c1 a1 db 58 90 f3 0f 1e fa 48 83 d9 18 <48> 8b 05 99 4b 1a 19 48 89 44 24 08 48 8b 5d 24 08 48 85 c0 74 12 Mar 2 07:20:40 Z560 systemd[1]: Created slice system-systemd\x2dcoredump.slice. Mar 2 07:20:40 Z560 systemd[1]: Started Process Core Dump (PID 933484/UID 0). Mar 2 07:20:40 Z560 systemd-coredump[933485]: Process 933482 (fcl) of user 1000 dumped core.#012#012Stack trace of thread 933482:#012#0 0x7fb96efab218 gtk_option_menu_get_type (libgtk-x11-2.0.so.0 + 0x2b4218)#012#1 0x0002 n/a (n/a + 0x0) Mar 2 07:20:40 Z560 systemd[1]: systemd-coredump@0-933484-0.service: Succeeded. and: Mar 2 07:51:19 Z560 kernel: [819049.877381] VirtualBox[936782]: segfault at 7ff8860b4db8 ip 7ff86cf10218 sp 7ffdd1a53758 error 4 in libgtk-x11-2.0.so.0.2400.32[7ff86ccc+27] Mar 2 07:51:19 Z560 kernel: [819049.877395] Code: 79 db ff 48 83 c4 20 5b 5d 41 5c c3 66 0f 1f 44 00 00 48 8b b7 90 00 00 79 48 89 d7 e9 c1 a1 db 58 90 f3 0f 1e fa 48 83 d9 18 <48> 8b 05 99 4b 1a 19 48 89 44 24 08 48 8b 5d 24 08 48 85 c0 74 12 Mar 2 07:51:19 Z560 systemd[1]: Started Process Core Dump (PID 936794/UID 0). Mar 2 07:51:19 Z560 systemd-coredump[936795]: Process 936782 (VirtualBox) of user 1000 dumped core.#012#012Stack trace of thread 936782:#012#0 0x7ff86cf10218 gtk_option_menu_get_type (libgtk-x11-2.0.so.0 + 0x2b4218)#012#1 0x0002 n/a (n/a + 0x0) Mar 2 07:51:19 Z560 systemd[1]: systemd-coredump@10-936794-0.service: Succeeded. As this library has not changed I am assuming the problem is with one of the libraries it depends upon. Several packages were updated in the past few days, I believe including some that may be the cause of the problem. I have attached a zip with my /var/log/apt/term.log and history.log for inspection. Version of library is 2.24.32-4ubuntu4 and library file is dated 2021-03-31 here. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gtk+2.0/+bug/1962807/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1962807] Re: segfault in libgtk-x11-2.0.so.0 with several programs
The two programs are completely broken for me at this time. I use them on a daily basis, so this is a real problem for me. There may be additional broken programs that I have yet to encounter, but I have not hit any others yet. Given the behavior started suddenly yesterday after years of operation I suspect that an update to one of the dependencies of the library where the crash occurs is the cause. I am not a developer, and thus unable to track this down personally. Given my suspicions I attached a zip containing the update logs in hopes someone with the proper tools can identify the problem. I should be able to back out the particular change once it is identified. If you need further information please let me know. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to gtk+2.0 in Ubuntu. https://bugs.launchpad.net/bugs/1962807 Title: segfault in libgtk-x11-2.0.so.0 with several programs Status in gtk+2.0 package in Ubuntu: Incomplete Bug description: Today I have been encountering segfaults in fcl and virtualbox: Mar 2 07:20:40 Z560 kernel: [817210.808918] show_signal_msg: 12 callbacks suppressed Mar 2 07:20:40 Z560 kernel: [817210.808922] fcl[933482]: segfault at 7fb98814fdb8 ip 7fb96efab218 sp 7ffc4a89b918 error 4 in libgtk-x11-2.0.so.0.2400.32[7fb96ed5b000+27] Mar 2 07:20:40 Z560 kernel: [817210.808932] Code: 79 db ff 48 83 c4 20 5b 5d 41 5c c3 66 0f 1f 44 00 00 48 8b b7 90 00 00 79 48 89 d7 e9 c1 a1 db 58 90 f3 0f 1e fa 48 83 d9 18 <48> 8b 05 99 4b 1a 19 48 89 44 24 08 48 8b 5d 24 08 48 85 c0 74 12 Mar 2 07:20:40 Z560 systemd[1]: Created slice system-systemd\x2dcoredump.slice. Mar 2 07:20:40 Z560 systemd[1]: Started Process Core Dump (PID 933484/UID 0). Mar 2 07:20:40 Z560 systemd-coredump[933485]: Process 933482 (fcl) of user 1000 dumped core.#012#012Stack trace of thread 933482:#012#0 0x7fb96efab218 gtk_option_menu_get_type (libgtk-x11-2.0.so.0 + 0x2b4218)#012#1 0x0002 n/a (n/a + 0x0) Mar 2 07:20:40 Z560 systemd[1]: systemd-coredump@0-933484-0.service: Succeeded. and: Mar 2 07:51:19 Z560 kernel: [819049.877381] VirtualBox[936782]: segfault at 7ff8860b4db8 ip 7ff86cf10218 sp 7ffdd1a53758 error 4 in libgtk-x11-2.0.so.0.2400.32[7ff86ccc+27] Mar 2 07:51:19 Z560 kernel: [819049.877395] Code: 79 db ff 48 83 c4 20 5b 5d 41 5c c3 66 0f 1f 44 00 00 48 8b b7 90 00 00 79 48 89 d7 e9 c1 a1 db 58 90 f3 0f 1e fa 48 83 d9 18 <48> 8b 05 99 4b 1a 19 48 89 44 24 08 48 8b 5d 24 08 48 85 c0 74 12 Mar 2 07:51:19 Z560 systemd[1]: Started Process Core Dump (PID 936794/UID 0). Mar 2 07:51:19 Z560 systemd-coredump[936795]: Process 936782 (VirtualBox) of user 1000 dumped core.#012#012Stack trace of thread 936782:#012#0 0x7ff86cf10218 gtk_option_menu_get_type (libgtk-x11-2.0.so.0 + 0x2b4218)#012#1 0x0002 n/a (n/a + 0x0) Mar 2 07:51:19 Z560 systemd[1]: systemd-coredump@10-936794-0.service: Succeeded. As this library has not changed I am assuming the problem is with one of the libraries it depends upon. Several packages were updated in the past few days, I believe including some that may be the cause of the problem. I have attached a zip with my /var/log/apt/term.log and history.log for inspection. Version of library is 2.24.32-4ubuntu4 and library file is dated 2021-03-31 here. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gtk+2.0/+bug/1962807/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1962818] Re: Jammy Jellyfish LightDM is frozen after long period of inactivity
Thank you for taking the time to report this bug and helping to make Ubuntu better. Please execute the following command only once, as it will automatically gather debugging information, in a terminal: apport-collect 1962818 When reporting bugs in the future please use apport by using 'ubuntu- bug' and the name of the package affected. You can learn more about this functionality at https://wiki.ubuntu.com/ReportingBugs. ** Changed in: lightdm (Ubuntu) Status: New => Incomplete -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to lightdm in Ubuntu. https://bugs.launchpad.net/bugs/1962818 Title: Jammy Jellyfish LightDM is frozen after long period of inactivity Status in lightdm package in Ubuntu: Incomplete Bug description: Jammy Jellyfish LightDM is frozen after long period of inactivity Latest updates installed, has been happening since first install 2 weeks ago. Upon using the laptop after over night or coming back from work, the screen is frozen. I can move the mouse around but click is unresponsive. To resolve the issue, I ctrl=alt=f2 in order to log into a shell then restart the LightDM services. Those equals signs should be a plus, however it appears my shift key is not working so I will log another bug for that. I am using an XFCE environment. Description: Ubuntu Jammy Jellyfish (development branch) Release: 22.04 lightdm: Installed: 1.30.0-0ubuntu5 Candidate: 1.30.0-0ubuntu5 Version table: *** 1.30.0-0ubuntu5 500 500 http://au.archive.ubuntu.com/ubuntu jammy/universe amd64 Packages 100 /var/lib/dpkg/status To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/lightdm/+bug/1962818/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1962133] Re: Intermittent very low fps(sometimes zero) with few specific h264 and h265 RTSP input streams sources when used with gst-v4l2 based gstreamer-1.0(version gst-1.14.5)
Please attach the reproducing pipeline; it's a bit tricky to organise access to Jetson hardware to the right people, so if you had a reproducer that we could run without Jetson hardware, that would be best! -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to gst-plugins-base1.0 in Ubuntu. https://bugs.launchpad.net/bugs/1962133 Title: Intermittent very low fps(sometimes zero) with few specific h264 and h265 RTSP input streams sources when used with gst-v4l2 based gstreamer-1.0(version gst-1.14.5) decode pipeline Status in Gstreamer1.0: Unknown Status in gst-plugins-base1.0 package in Ubuntu: Fix Released Status in gst-plugins-base1.0 source package in Bionic: New Bug description: Few specific h264 and h265 RTSP input streams sources when used with nvidia specific gst-v4l2 based gstreamer-1.0 (version gst-1.14 and ubuntu-18.04) decode pipeline intermittently yields very low fps (in the range of [~0/1 fps]). Issue seems caused by the gst_video_decoder_drain_out function erroneously getting called inside gst_video_decoder_chain_forward function. Required changes to fix the issue seems available with gst-1.16 and to resolve the issue need to backport the relevant OSS fixes from gst-1.16 to gst-1.14 on ubuntu-18.04. The mentioned issue was reported on with: https://bugzilla.gnome.org/show_bug.cgi?id=796771 Corresponding fix was incorporated with below: https://github.com/GStreamer/gst-plugins-base/commit/62cb08404b9bd055c45cc1d5b71141e927ad748a We need to backport above fix on top of gst-1.14.5 on ubuntu-18.04 in order to have out-of-box fix available with default gstreamer-1.0 version 1.14 on ubuntu-18.04 To manage notifications about this bug go to: https://bugs.launchpad.net/gstreamer1.0/+bug/1962133/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1962134] Re: Resolve "GStreamer-CRITICAL **: 13:33:23.770: gst_buffer_resize_range: assertion 'bufmax >= bufoffs + offset + size' failed" warning on gstreamer version 1.16 on ubu
Hi Kunal, It might be tricky to organise testing on Jetson platforms for people that will prepare the fix. In any case, could you share instructions to reproduce? If there's a way to craft a test pipeline that trigger the issue without Jetson hardware, that would be best. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to gstreamer1.0 in Ubuntu. https://bugs.launchpad.net/bugs/1962134 Title: Resolve "GStreamer-CRITICAL **: 13:33:23.770: gst_buffer_resize_range: assertion 'bufmax >= bufoffs + offset + size' failed" warning on gstreamer version 1.16 on ubuntu-20.04 Status in gstreamer1.0 package in Ubuntu: Fix Released Status in gstreamer1.0 source package in Bionic: New Status in gstreamer1.0 source package in Focal: New Bug description: Following gstreamer critical warning observed on gstreamer version 1.16 on ubuntu-20.04 with nvidia specific gst-v4l2 decoder pipeline: "GStreamer-CRITICAL **: 13:33:23.770: gst_buffer_resize_range: assertion 'bufmax >= bufoffs + offset + size' failed" It seems fix for the issue is already incorporated on gstreamer version 1.18 with below: https://gitlab.freedesktop.org/gstreamer/gstreamer/-/commit/a1b41b2b2493069365a8274c6a544e6799a5a8df We need to backport above fix on top of gst-1.16 on ubuntu-20.04 in order to have out-of-box fix available with default gstreamer-1.0 version 1.16 on ubuntu-20.04 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gstreamer1.0/+bug/1962134/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1960458] Re: patch git_socket_dir.patch causing FTBFS in gspell
This bug was fixed in the package at-spi2-core - 2.42.0-2ubuntu3.1 --- at-spi2-core (2.42.0-2ubuntu3.1) jammy; urgency=medium * debian/patches/git_socket_dir.patch: - include some extra fixes from upstream to better handling non existing directories and relative paths (lp: #1960458) -- Sebastien Bacher Tue, 15 Feb 2022 18:29:33 +0100 ** Changed in: at-spi2-core (Ubuntu) Status: New => Fix Released -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to at-spi2-core in Ubuntu. https://bugs.launchpad.net/bugs/1960458 Title: patch git_socket_dir.patch causing FTBFS in gspell Status in at-spi2-core package in Ubuntu: Fix Released Bug description: With this patch applied gspell is FTBFS with the following errors: Bail out! dbind-FATAL-WARNING: Couldn't connect to accessibility bus: Failed to connect to socket debian/home/.cache/at-spi/bus: No such file or directory I removed the patch and rebuilt this package in a PPA. When built against this PPA, gpsell is able to build again. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/at-spi2-core/+bug/1960458/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1947099] Re: ipconfig does not honour user-requested timeouts in some cases
Hi Robie, The user story here is about improving the time it takes to boot a Bionic instance on Oracle Cloud in a specific bare metal shape, called BM.GPU4.8. This is a pretty large instance, with 18x Ethernet controller [0200]: Mellanox Technologies MT28800 Family [ConnectX-5 Ex] [15b3:1019]: https://www.oracle.com/uk/cloud/compute/gpu.html Comparing the time it takes to boot Bionic with a CentOS instance we can see a big delta both in kernel and userspace: CentOS: Startup finished in 4min 3.548s (firmware) + 2min 23.525s (loader) + 3min 17.984s (kernel) + 1min 37.825s (initrd) + 38.723s (userspace) = 12min 1.608s multi-user.target reached after 38.714s in userspace Ubuntu: Startup finished in 4min 621ms (firmware) + 2min 23.174s (loader) + 7min 34.767s (kernel) + 5min 48.219s (userspace) = 19min 46.782s graphical.target reached after 5min 47.854s in userspace The userspace difference is a cloud-init problem that is being handled by other launchpad bugs. Here we are trying to focus on the kernel difference, which further was narrowed down to be related to klibc and it is what we are trying to address with this bug. Some details: Looking into details, here are the dmesg output from CentOS and Ubuntu, for kernel comparison: Ubuntu: https://pastebin.canonical.com/p/X7GFVjdV3b/ CentOS: https://pastebin.canonical.com/p/gNhFwJjyjw/ Looking there, one area that looks promising is around mlx5_core driver, where Ubuntu spends 218 seconds, while CentOS spends 44 seconds Khalid did a nice job investigating and found that the problem came from ipconfig from initramfs. Here are the details: The delay from the kernel side is due to the fact that every interface (18 in total) takes over 10 seconds each to initialize. The interfaces are brought up and used for DHCP as part of the iscsi initialization, during the initramfs stage. Specifically the script ```/usr/share/initramfs-tools/scripts/local-top/iscsi``` which is included in the initramfs and is installed as part of open-iscsi To initialize the network interfaces this script calls other helper functions that are part of the initramfs, specifically "configure_networking" in ```/usr/share/initramfs- tools/scripts/functions``` which is installed as part of initramfs- tools-core. The configure_networking function initializes networking by looping over all interfaces and issuing this call: ``` ipconfig -t 2 ``` where it is calling the ipconfig utility (part of klibc-utils) which also gets bundled in the initramfs. The -t 2 specifies a timeout of 2 seconds. This ipconfig tool attempts to perform DHCP on the given interface, within the specified timeout (always 2 seconds for each interface) Normally, ipconfig does not perform only one DHCP attempt - it performs multiple DHCP attempts, each attempt waiting for an exponentially increasing amount of time (1s, 2s, 4s, ..etc) up until the total amount of time has passed that is equal the user-specified timeout (2 in this case, so it should wait 1 second, followed by 1 second, for a total of 2 seconds). However, it appears ipconfig has a bug. In case it encounters an error sending a DHCP request on an interface (which is the case for 17 out of the 18 interfaces on this instance), it attempts to "try again later" and sets a timer of 10 seconds for the next attempt - ignoring completely the user-specified value (2 seconds). I believe this is a bug in ipconfig and have a working fix to limit the delay to the user- specified timeout so each interface actually takes a maximum of 2 seconds for initialization, even in error cases. The above is for bionic, which has the reported problem. In focal, even though the kernel and klibc-utils are identical to bionic, the version of initramfs-tools-core is different. In the focal version, configure_networking() has been reworked to avoid using ipconfig entirely. Instead, it uses ```dhclient```. And instead of doing that 18 times, dhclient is called only once with the full list of interfaces, as such: ``` dhclient -v -1 -cf /etc/dhcp/dhclient.conf.2 -pf /tmp/dhclient.pid.2 -4 enp12s0f0np0 enp12s0f1np1 enp138s0f0np0 enp138s0f1np1 enp148s0f0np0 enp148s0f1np1 enp195s0f0np0 enp195s0f1np1 enp209s0f0np0 enp209s0f1np1 enp22s0f0np0 enp22s0f1np1 enp45s0f0np0 enp45s0f1np1 enp72s0f0np0 enp72s0f1np1 enp76s0f0np0 enp76s0f1np1 ``` dhclient does DHCP on all those interfaces at the same time, asynchronously, and it daemonizes (goes in the background) as soon as it gets a DHCP response which happens relatively quickly (on interface enp45s0f0np0 usually) and so the boot-up continues *much* faster compared to bionic (180+ seconds are reduced to just 5-10 seconds). I'm sure there might be other use cases, but this is what we have been reported and are trying to work with. I hope this helps clarifying. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to klibc in Ubuntu. https://bugs.launchpad.net/bugs/1947099
[Touch-packages] [Bug 1778073] Re: dnsmasq and resolvconf hangs on start
** Changed in: dnsmasq (Ubuntu) Assignee: Paride Legovini (paride) => (unassigned) -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to dnsmasq in Ubuntu. https://bugs.launchpad.net/bugs/1778073 Title: dnsmasq and resolvconf hangs on start Status in dnsmasq package in Ubuntu: Incomplete Status in dnsmasq package in Debian: New Bug description: I installed today dnsmasq and I use resolvconf in background. Problem is, that systemd takes 1 minute or so after service start and than reports: root@proxy:~# service dnsmasq status dnsmasq.service - dnsmasq - A lightweight DHCP and caching DNS server Loaded: loaded (/lib/systemd/system/dnsmasq.service; enabled; vendor preset: enabled) Drop-In: /run/systemd/generator/dnsmasq.service.d 50-dnsmasq-$named.conf, 50-insserv.conf-$named.conf Active: failed (Result: timeout) since Do 2018-06-21 15:58:13 CEST; 2min 10s ago Process: 3295 ExecStop=/etc/init.d/dnsmasq systemd-stop-resolvconf (code=killed, signal=TERM) Process: 3865 ExecStartPost=/etc/init.d/dnsmasq systemd-start-resolvconf (code=killed, signal=TERM) Process: 3837 ExecStart=/etc/init.d/dnsmasq systemd-exec (code=exited, status=0/SUCCESS) Process: 3825 ExecStartPre=/usr/sbin/dnsmasq --test (code=exited, status=0/SUCCESS) Main PID: 3862 (code=exited, status=0/SUCCESS) Jun 21 15:56:43 proxy dnsmasq[3862]: Benutze Namensserver 192.168.23.1#53 Jun 21 15:56:43 proxy dnsmasq[3865]: * Awakening mail retriever agent: Jun 21 15:56:43 proxy dnsmasq[3865]:...done. Jun 21 15:56:43 proxy postfix[3951]: Postfix is running with backwards-compatible default settings Jun 21 15:56:43 proxy postfix[3951]: See http://www.postfix.org/COMPATIBILITY_README.html for details Jun 21 15:56:43 proxy postfix[3951]: To disable backwards compatibility use "postconf compatibility_level=2" and "postfix reload" Jun 21 15:58:13 proxy systemd[1]: dnsmasq.service: Start-post operation timed out. Stopping. Jun 21 15:58:13 proxy systemd[1]: Failed to start dnsmasq - A lightweight DHCP and caching DNS server. Jun 21 15:58:13 proxy systemd[1]: dnsmasq.service: Unit entered failed state. Jun 21 15:58:13 proxy systemd[1]: dnsmasq.service: Failed with result 'timeout'. when I look into the start script /etc/init.d/dnsmasq there is a func systemd-start-resolvconf which points to start-resolvconf. There is this part: for interface in $DNSMASQ_EXCEPT do [ $interface = lo ] && return done Before I had not defined DNSMASQ_EXCEPT in /etc/defaults/dnsmasq. Problem is, that this part MUST be faulty! When I commend it out, I can start dnsmasq! It looks like it loops forever there?! Also if I define DNSMASQ_EXCEPT to my listen interface, it works - but is is really needed? I found a other user which had the same problem: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=871958 ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: dnsmasq 2.75-1ubuntu0.16.04.4 [modified: etc/default/dnsmasq] ProcVersionSignature: Ubuntu 4.15.0-23.25~16.04.1-generic 4.15.18 Uname: Linux 4.15.0-23-generic x86_64 ApportVersion: 2.20.1-0ubuntu2.18 Architecture: amd64 Date: Thu Jun 21 16:12:14 2018 InstallationDate: Installed on 2017-02-27 (479 days ago) InstallationMedia: Ubuntu-Server 16.04.2 LTS "Xenial Xerus" - Release amd64 (20170215.8) PackageArchitecture: all ProcEnviron: TERM=xterm SHELL=/bin/bash PATH=(custom, no user) LANG=de_DE.UTF-8 SourcePackage: dnsmasq UpgradeStatus: No upgrade log present (probably fresh install) mtime.conffile..etc.default.dnsmasq: 2018-06-21T16:07:24.818774 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/dnsmasq/+bug/1778073/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1962346] Re: Ubuntu reboots instead of powering off if a software updates exists
I can say, that I have this dialog only if I have a flatpak updates, not apt updates. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to packagekit in Ubuntu. https://bugs.launchpad.net/bugs/1962346 Title: Ubuntu reboots instead of powering off if a software updates exists Status in gnome-shell package in Ubuntu: New Status in packagekit package in Ubuntu: New Bug description: When I want to turn off a computer, I got a checkbox "Install deferred updates" (see screenshot, I'm not sure if my back-translation is correct). If the checkbox is checked, Ubuntu box reboots instead of powering off. It is not "rebopot to install updates". It just reboots to desktop again. If I uncheck the box, it powers off normally. ProblemType: Bug DistroRelease: Ubuntu 21.10 Package: gnome-shell 40.5-1ubuntu2 ProcVersionSignature: Ubuntu 5.13.0-27.29-generic 5.13.19 Uname: Linux 5.13.0-27-generic x86_64 ApportVersion: 2.20.11-0ubuntu71 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: ubuntu:GNOME Date: Sat Feb 26 00:05:44 2022 DisplayManager: gdm3 ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=ru_RU.UTF-8 SHELL=/bin/bash RelatedPackageVersions: mutter-common 40.5-1ubuntu3~21.10.1 SourcePackage: gnome-shell UpgradeStatus: Upgraded to impish on 2022-01-11 (45 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1962346/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1962836] Re: [NJ50_70CU, Realtek ALC256, Speaker, Internal] No sounds after Resume
Alsa info after suspend http://alsa- project.org/db/?f=5616145ad14337953bcf0df255cc83693c829e2d -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to alsa-driver in Ubuntu. https://bugs.launchpad.net/bugs/1962836 Title: [NJ50_70CU, Realtek ALC256, Speaker, Internal] No sounds after Resume Status in alsa-driver package in Ubuntu: New Bug description: How to reproduce : - With internal speakers - play sound - suspend laptop - Resume - Play sound : no sound but the meter moves and the sound card is selected ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: alsa-base 1.0.25+dfsg-0ubuntu5 ProcVersionSignature: Ubuntu 5.13.0-30.33~20.04.1-generic 5.13.19 Uname: Linux 5.13.0-30-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.21 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: oem2268 F pulseaudio /dev/snd/pcmC0D0c: oem2268 F...m pulseaudio /dev/snd/pcmC0D0p: oem2268 F...m pulseaudio CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Thu Mar 3 12:12:49 2022 InstallationDate: Installed on 2022-03-02 (0 days ago) InstallationMedia: Ubuntu 20.04.4 LTS "Focal Fossa" - Release amd64 (20220223) PackageArchitecture: all ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=fr_FR.UTF-8 SHELL=/bin/bash SourcePackage: alsa-driver Symptom: audio Symptom_AlsaPlaybackTest: ALSA playback test through plughw:PCH failed Symptom_Card: Audio interne - HDA Intel PCH Symptom_Jack: Speaker, Internal Symptom_Type: None of the above Title: [NJ50_70CU, Realtek ALC256, Speaker, Internal] Playback problem UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 10/24/2019 dmi.bios.release: 7.18 dmi.bios.vendor: INSYDE Corp. dmi.bios.version: 1.07.18I dmi.board.asset.tag: Tag 12345 dmi.board.name: NJ50_70CU dmi.board.vendor: Notebook dmi.board.version: Not Applicable dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: Notebook dmi.chassis.version: N/A dmi.ec.firmware.release: 7.12 dmi.modalias: dmi:bvnINSYDECorp.:bvr1.07.18I:bd10/24/2019:br7.18:efr7.12:svnNotebook:pnNJ50_70CU:pvrNotApplicable:rvnNotebook:rnNJ50_70CU:rvrNotApplicable:cvnNotebook:ct10:cvrN/A:skuNotApplicable: dmi.product.family: Not Applicable dmi.product.name: NJ50_70CU dmi.product.sku: Not Applicable dmi.product.version: Not Applicable dmi.sys.vendor: Notebook mtime.conffile..etc.modprobe.d.alsa-base.conf: 2022-03-03T11:48:35.145684 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1962836/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1962836] [NEW] [NJ50_70CU, Realtek ALC256, Speaker, Internal] No sounds after Resume
Public bug reported: How to reproduce : - With internal speakers - play sound - suspend laptop - Resume - Play sound : no sound but the meter moves and the sound card is selected ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: alsa-base 1.0.25+dfsg-0ubuntu5 ProcVersionSignature: Ubuntu 5.13.0-30.33~20.04.1-generic 5.13.19 Uname: Linux 5.13.0-30-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.21 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: oem2268 F pulseaudio /dev/snd/pcmC0D0c: oem2268 F...m pulseaudio /dev/snd/pcmC0D0p: oem2268 F...m pulseaudio CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Thu Mar 3 12:12:49 2022 InstallationDate: Installed on 2022-03-02 (0 days ago) InstallationMedia: Ubuntu 20.04.4 LTS "Focal Fossa" - Release amd64 (20220223) PackageArchitecture: all ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=fr_FR.UTF-8 SHELL=/bin/bash SourcePackage: alsa-driver Symptom: audio Symptom_AlsaPlaybackTest: ALSA playback test through plughw:PCH failed Symptom_Card: Audio interne - HDA Intel PCH Symptom_Jack: Speaker, Internal Symptom_Type: None of the above Title: [NJ50_70CU, Realtek ALC256, Speaker, Internal] Playback problem UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 10/24/2019 dmi.bios.release: 7.18 dmi.bios.vendor: INSYDE Corp. dmi.bios.version: 1.07.18I dmi.board.asset.tag: Tag 12345 dmi.board.name: NJ50_70CU dmi.board.vendor: Notebook dmi.board.version: Not Applicable dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: Notebook dmi.chassis.version: N/A dmi.ec.firmware.release: 7.12 dmi.modalias: dmi:bvnINSYDECorp.:bvr1.07.18I:bd10/24/2019:br7.18:efr7.12:svnNotebook:pnNJ50_70CU:pvrNotApplicable:rvnNotebook:rnNJ50_70CU:rvrNotApplicable:cvnNotebook:ct10:cvrN/A:skuNotApplicable: dmi.product.family: Not Applicable dmi.product.name: NJ50_70CU dmi.product.sku: Not Applicable dmi.product.version: Not Applicable dmi.sys.vendor: Notebook mtime.conffile..etc.modprobe.d.alsa-base.conf: 2022-03-03T11:48:35.145684 ** Affects: alsa-driver (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug focal -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to alsa-driver in Ubuntu. https://bugs.launchpad.net/bugs/1962836 Title: [NJ50_70CU, Realtek ALC256, Speaker, Internal] No sounds after Resume Status in alsa-driver package in Ubuntu: New Bug description: How to reproduce : - With internal speakers - play sound - suspend laptop - Resume - Play sound : no sound but the meter moves and the sound card is selected ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: alsa-base 1.0.25+dfsg-0ubuntu5 ProcVersionSignature: Ubuntu 5.13.0-30.33~20.04.1-generic 5.13.19 Uname: Linux 5.13.0-30-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.21 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: oem2268 F pulseaudio /dev/snd/pcmC0D0c: oem2268 F...m pulseaudio /dev/snd/pcmC0D0p: oem2268 F...m pulseaudio CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Thu Mar 3 12:12:49 2022 InstallationDate: Installed on 2022-03-02 (0 days ago) InstallationMedia: Ubuntu 20.04.4 LTS "Focal Fossa" - Release amd64 (20220223) PackageArchitecture: all ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=fr_FR.UTF-8 SHELL=/bin/bash SourcePackage: alsa-driver Symptom: audio Symptom_AlsaPlaybackTest: ALSA playback test through plughw:PCH failed Symptom_Card: Audio interne - HDA Intel PCH Symptom_Jack: Speaker, Internal Symptom_Type: None of the above Title: [NJ50_70CU, Realtek ALC256, Speaker, Internal] Playback problem UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 10/24/2019 dmi.bios.release: 7.18 dmi.bios.vendor: INSYDE Corp. dmi.bios.version: 1.07.18I dmi.board.asset.tag: Tag 12345 dmi.board.name: NJ50_70CU dmi.board.vendor: Notebook dmi.board.version: Not Applicable dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: Notebook dmi.chassis.version: N/A dmi.ec.firmware.release: 7.12 dmi.modalias: dmi:bvnINSYDECorp.:bvr1.07.18I:bd10/24/2019:br7.18:efr7.12:svnNotebook:pnNJ50_70CU:pvrNotApplicable:rvnNotebook:rnNJ50_70CU:rvrNotApplicable:cvnNotebook:ct10:cvrN/A:skuNotApplicable: dmi.product.family: Not Applicable dmi.product.name: NJ50_70CU dmi.product.sku: Not Applicable dmi.product.version: Not Applicable dmi.sys.vendor: Notebook mtime.conffile..etc.modprobe.d.alsa-base.conf: 2022-03-03T11:48:35.145684 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1962836/+subscriptions -- Mailing list:
[Touch-packages] [Bug 1962346] Re: Ubuntu reboots instead of powering off if a software updates exists
I wonder if you need to install gnome-software Deb maybe. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to packagekit in Ubuntu. https://bugs.launchpad.net/bugs/1962346 Title: Ubuntu reboots instead of powering off if a software updates exists Status in gnome-shell package in Ubuntu: New Status in packagekit package in Ubuntu: New Bug description: When I want to turn off a computer, I got a checkbox "Install deferred updates" (see screenshot, I'm not sure if my back-translation is correct). If the checkbox is checked, Ubuntu box reboots instead of powering off. It is not "rebopot to install updates". It just reboots to desktop again. If I uncheck the box, it powers off normally. ProblemType: Bug DistroRelease: Ubuntu 21.10 Package: gnome-shell 40.5-1ubuntu2 ProcVersionSignature: Ubuntu 5.13.0-27.29-generic 5.13.19 Uname: Linux 5.13.0-27-generic x86_64 ApportVersion: 2.20.11-0ubuntu71 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: ubuntu:GNOME Date: Sat Feb 26 00:05:44 2022 DisplayManager: gdm3 ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=ru_RU.UTF-8 SHELL=/bin/bash RelatedPackageVersions: mutter-common 40.5-1ubuntu3~21.10.1 SourcePackage: gnome-shell UpgradeStatus: Upgraded to impish on 2022-01-11 (45 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1962346/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1962346] Re: Ubuntu reboots instead of powering off if a software updates exists
No I am not familiar with this feature. I also can't seem to trigger it in jammy (reported in impish). Even when I have updates awaiting installation it just powers off when told to. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to packagekit in Ubuntu. https://bugs.launchpad.net/bugs/1962346 Title: Ubuntu reboots instead of powering off if a software updates exists Status in gnome-shell package in Ubuntu: New Status in packagekit package in Ubuntu: New Bug description: When I want to turn off a computer, I got a checkbox "Install deferred updates" (see screenshot, I'm not sure if my back-translation is correct). If the checkbox is checked, Ubuntu box reboots instead of powering off. It is not "rebopot to install updates". It just reboots to desktop again. If I uncheck the box, it powers off normally. ProblemType: Bug DistroRelease: Ubuntu 21.10 Package: gnome-shell 40.5-1ubuntu2 ProcVersionSignature: Ubuntu 5.13.0-27.29-generic 5.13.19 Uname: Linux 5.13.0-27-generic x86_64 ApportVersion: 2.20.11-0ubuntu71 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: ubuntu:GNOME Date: Sat Feb 26 00:05:44 2022 DisplayManager: gdm3 ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=ru_RU.UTF-8 SHELL=/bin/bash RelatedPackageVersions: mutter-common 40.5-1ubuntu3~21.10.1 SourcePackage: gnome-shell UpgradeStatus: Upgraded to impish on 2022-01-11 (45 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1962346/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1962346] Re: Ubuntu reboots instead of powering off if a software updates exists
@Daniel, do you have any idea what changed that the option starting to show only now on Ubuntu sessions? -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to packagekit in Ubuntu. https://bugs.launchpad.net/bugs/1962346 Title: Ubuntu reboots instead of powering off if a software updates exists Status in gnome-shell package in Ubuntu: New Status in packagekit package in Ubuntu: New Bug description: When I want to turn off a computer, I got a checkbox "Install deferred updates" (see screenshot, I'm not sure if my back-translation is correct). If the checkbox is checked, Ubuntu box reboots instead of powering off. It is not "rebopot to install updates". It just reboots to desktop again. If I uncheck the box, it powers off normally. ProblemType: Bug DistroRelease: Ubuntu 21.10 Package: gnome-shell 40.5-1ubuntu2 ProcVersionSignature: Ubuntu 5.13.0-27.29-generic 5.13.19 Uname: Linux 5.13.0-27-generic x86_64 ApportVersion: 2.20.11-0ubuntu71 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: ubuntu:GNOME Date: Sat Feb 26 00:05:44 2022 DisplayManager: gdm3 ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=ru_RU.UTF-8 SHELL=/bin/bash RelatedPackageVersions: mutter-common 40.5-1ubuntu3~21.10.1 SourcePackage: gnome-shell UpgradeStatus: Upgraded to impish on 2022-01-11 (45 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1962346/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1961859] Re: When we install ModemManager1.16.6 and others, this will lead to ubuntu can not enter into GNOME UI.
Hi: Let me double check and reply for you later.Tks. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to modemmanager in Ubuntu. https://bugs.launchpad.net/bugs/1961859 Title: When we install ModemManager1.16.6 and others, this will lead to ubuntu can not enter into GNOME UI. Status in modemmanager package in Ubuntu: Incomplete Bug description: 1. We use sourcecode to install ModemManger1.16.6 2. Ubuntu can not enter UI. 3. We capture log and picture and add these on the attachment. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/modemmanager/+bug/1961859/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1961859] Re: When we install ModemManager1.16.6 and others, this will lead to ubuntu can not enter into GNOME UI.
The log has errors like boltd[712]: /usr/libexec/boltd: symbol lookup error: /usr/libexec/boltd: undefined symbol: g_log_structured_standard could you share the output of $ ldd -r /usr/libexec/boltd it sounds like an old version of glib has been installed taking of the ubuntu version? ** Changed in: modemmanager (Ubuntu) Status: Confirmed => Incomplete -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to modemmanager in Ubuntu. https://bugs.launchpad.net/bugs/1961859 Title: When we install ModemManager1.16.6 and others, this will lead to ubuntu can not enter into GNOME UI. Status in modemmanager package in Ubuntu: Incomplete Bug description: 1. We use sourcecode to install ModemManger1.16.6 2. Ubuntu can not enter UI. 3. We capture log and picture and add these on the attachment. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/modemmanager/+bug/1961859/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1962542] Re: [jammy] Bluetooth headphones unable to connect after suspend in BlueZ 5.63
I just tested this version on jammy and my headset now will reconnect after a suspend without problems. Thanks so much for cherry-picking those patches! -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to bluez in Ubuntu. https://bugs.launchpad.net/bugs/1962542 Title: [jammy] Bluetooth headphones unable to connect after suspend in BlueZ 5.63 Status in Bluez Utilities: Fix Released Status in bluez package in Ubuntu: Fix Released Bug description: Bose quietcomfort 35 is a common headset that can no longer connect to a jammy system after just one suspend. This started at the end of January but just now really debugging the issue. Side note that my bluetooth mouse works fine without problem after any amount of suspends. The headset is only trying to connect to the jammy system (no other bluetooth devices it's paired with has active bluetooth, to isolate only the jammy <-> headset issue). This is jammy running on a T590, up to date, not proposed. heather@fenrir:~$ dpkg -l | grep bluetooth ii gir1.2-gnomebluetooth-1.0:amd643.34.5-4 amd64Introspection data for GnomeBluetooth ii gnome-bluetooth3.34.5-4 amd64GNOME Bluetooth tools ii libbluetooth-dev:amd64 5.63-0ubuntu1 amd64Development files for using the BlueZ Linux Bluetooth library ii libbluetooth3:amd645.63-0ubuntu1 amd64Library to use the BlueZ Linux Bluetooth stack ii libgnome-bluetooth13:amd64 3.34.5-4 amd64GNOME Bluetooth tools - support library ii pulseaudio-module-bluetooth1:15.99.1+dfsg1-1ubuntu1 amd64Bluetooth module for PulseAudio sound server On a fresh boot (not suspended yet), I can connect the headset successfully. Here are the logs of that: Mar 01 09:44:02 fenrir kernel: input: Bose QuietComfort 35 (AVRCP) as /devices/virtual/input/input30 Mar 01 09:44:02 fenrir systemd-logind[1570]: Watching system buttons on /dev/input/event22 (Bose QuietComfort 35 (AVRCP)) Mar 01 09:44:03 fenrir NetworkManager[1536]: [1646124243.8660] platform-linux: do-add-ip6-address[3: fe80::c1bc:a705:9e66:e0d0]: failure 13 (Permission denied) Mar 01 09:44:04 fenrir bluetoothd[1532]: /org/bluez/hci0/dev_60_AB_D2_07_DB_9F/fd0: fd(32) ready Mar 01 09:44:04 fenrir rtkit-daemon[2349]: Supervising 6 threads of 3 processes of 1 users. Mar 01 09:44:04 fenrir rtkit-daemon[2349]: Successfully made thread 5660 of process 2708 owned by '1000' RT at priority 5. Mar 01 09:44:04 fenrir rtkit-daemon[2349]: Supervising 7 threads of 3 processes of 1 users. Mar 01 09:44:04 fenrir pulseaudio[2708]: org.freedesktop.DBus.Properties.Get /org/bluez/hci0/dev_60_AB_D2_07_DB_9F/fd0 Volume failed: org.freedesktop.DBus.Error.InvalidArgs: No such property 'Volume' Mar 01 09:44:04 fenrir pulseaudio[2708]: Battery Level: 70% Mar 01 09:44:04 fenrir pulseaudio[2708]: Dock Status: undocked But then if I close the laptop lid and reopen, login, and try to connect the headset the device is found invalid with the following logs: Mar 01 00:47:08 fenrir kernel: input: Bose QuietComfort 35 (AVRCP) as /devices/virtual/input/input152 Mar 01 00:47:08 fenrir pulseaudio[253956]: Information about device /org/bluez/hci0/dev_60_AB_D2_07_DB_9F is invalid Mar 01 00:47:08 fenrir bluetoothd[40741]: profiles/audio/media.c:endpoint_reply() Endpoint replied with an error: org.bluez.Error.InvalidArguments Mar 01 00:47:08 fenrir pulseaudio[253956]: Information about device /org/bluez/hci0/dev_60_AB_D2_07_DB_9F is invalid Mar 01 00:47:08 fenrir bluetoothd[40741]: profiles/audio/media.c:endpoint_reply() Endpoint replied with an error: org.bluez.Error.InvalidArguments Mar 01 00:47:08 fenrir systemd-logind[1545]: Watching system buttons on /dev/input/event19 (Bose QuietComfort 35 (AVRCP)) Mar 01 00:47:09 fenrir pulseaudio[253956]: Information about device /org/bluez/hci0/dev_60_AB_D2_07_DB_9F is invalid Mar 01 00:47:09 fenrir bluetoothd[40741]: profiles/audio/media.c:endpoint_reply() Endpoint replied with an error: org.bluez.Error.InvalidArguments Mar 01 00:47:09 fenrir pulseaudio[253956]: Information about device /org/bluez/hci0/dev_60_AB_D2_07_DB_9F is invalid Mar 01 00:47:09 fenrir bluetoothd[40741]: profiles/audio/media.c:endpoint_reply() Endpoint replied with an error: org.bluez.Error.InvalidArguments Mar 01 00:47:09 fenrir pulseaudio[253956]: Device doesn't exist for /org/bluez/hci0/dev_60_AB_D2_07_DB_9F Mar 01 00:47:09 fenrir bluetoothd[40741]: src/profile.c:new_conn_reply() Hands-Free Voice gateway replied with an error: org.bluez.Error.InvalidArguments, Unable to handle new connection Mar 01 00:47:09
[Touch-packages] [Bug 1960736] Re: Libnss3 doesn't log SEC_ERROR_UNKNOWN_PKCS11_ERROR properly ( NSS error code: -8018 )
Hello, Thanks for filing this bug and helping us get better. I tried to take a look into this but I can't seem to be able to reproduce this. Do you have a set of steps so that I can reproduce this, maybe? Without being able to reproduce the above issue, I am not sure how much I/we might be able to help but we try our best. :) Let us know the same and please change the status of the bug to "New" again once you do that and we'll be happy to take a look again! \o/ ** Changed in: nss (Ubuntu) Status: New => Incomplete -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to nss in Ubuntu. https://bugs.launchpad.net/bugs/1960736 Title: Libnss3 doesn't log SEC_ERROR_UNKNOWN_PKCS11_ERROR properly ( NSS error code: -8018 ) Status in nss package in Ubuntu: Incomplete Bug description: I've got the issue with Google Chrome not recognizing any of SSL/TSL certificates as trusted. When I look into certificate checksums it's renders all bytes of it as NULL bytes. I'm aware Google Chrome is proprietary but it depends on ubuntu provided libnss3-package. And libnss provides very nigmatic error code -8018: `/opt/google/chrome$ google-chrome [23391:23426:0213/133531.202486:ERROR:nss_util.cc(286)] After loading Root Certs, loaded==false: NSS error code: -8018 [23434:23434:0213/133531.266711:ERROR:sandbox_linux.cc(377)] InitializeSandbox() called with multiple threads in process gpu-process. [23391:23427:0213/133531.313065:ERROR:cert_verify_proc_builtin.cc(681)] CertVerifyProcBuiltin for accounts.google.com failed: - Certificate i=3 (CN=GlobalSign Root CA,OU=Root CA,O=GlobalSign nv-sa,C=BE) - ERROR: No matching issuer found ' When trying to enter this particular error code into search engine nothing is found. So my suggestion with this bug is to make it more transparent by providing information to what happened - it seems other bug codes has better error messages. To get SEC_ERROR_UNKNOWN_PKCS11_ERROR string I was force to download source code and manually calculate offsets. Another issue is if failing to initialize PKCS11 token should make whole SSL/TLS crypto invalid ? I'm not sure if this is libnss or Google Chrome issue but it behaves differently in Chromium browser with same libnss so I assume either of two is doing better - it's worth to review this from security perspective. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: libnss3 2:3.35-2ubuntu2.13 Uname: Linux 5.10.0-051000rc6-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.27 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Sun Feb 13 13:33:51 2022 Dependencies: gcc-8-base 8.4.0-1ubuntu1~18.04 libc6 2.27-3ubuntu1.5 [origin: LP-PPA-ubuntu-security-proposed] libgcc1 1:8.4.0-1ubuntu1~18.04 libnspr4 2:4.18-1ubuntu1 libsqlite3-0 3.22.0-1ubuntu0.4 InstallationDate: Installed on 2015-05-08 (2473 days ago) InstallationMedia: Ubuntu 15.04 "Vivid Vervet" - Release amd64 (20150422) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=pl_PL.UTF-8 SHELL=/bin/bash SourcePackage: nss UpgradeStatus: Upgraded to bionic on 2018-08-26 (1266 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nss/+bug/1960736/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
