[Desktop-packages] [Bug 1959599] Re: gnome-shell freezes upon trying to login
[Expired for gnome-shell (Ubuntu) because there has been no activity for 60 days.] ** Changed in: gnome-shell (Ubuntu) Status: Incomplete => Expired -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-shell in Ubuntu. https://bugs.launchpad.net/bugs/1959599 Title: gnome-shell freezes upon trying to login Status in gnome-shell package in Ubuntu: Expired Bug description: On Impish 21.10, gnome-shell freezes up when trying to login, specifically after I have typed in my password and hit enter. I have seen this both when logging in after the display shuts itself off after whatever the automatic timeout is, and also after manually locking the screen. This is the stack trace I see from gnome-shell at the time it freezes up: https://pastebin.ubuntu.com/p/9RcnnT32Nf/ The freeze was at 09:58:16 in the log. In this specific instance I just force rebooted the machine, in the other instance this happened to me, I let it sit and see if it would recover but it had not recovered after an hour or two. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1959599/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1967565] Re: upower takes long time to detect laptop AC charger plugged in
Thank you for your suggestion. I have reported the issue upstream here: https://gitlab.freedesktop.org/upower/upower/-/issues/179 ** Bug watch added: gitlab.freedesktop.org/upower/upower/-/issues #179 https://gitlab.freedesktop.org/upower/upower/-/issues/179 -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to upower in Ubuntu. https://bugs.launchpad.net/bugs/1967565 Title: upower takes long time to detect laptop AC charger plugged in Status in upower package in Ubuntu: New Bug description: upower takes a really long time (around 1-2 minutes) to detect when an AC charger is plugged-in. 'upower -d' shows battery state as discharging after AC charger is plugged-in. 'systemctl restart upower.service' would update the status immediately as charging. Otherwise, it takes 1-2 minutes before upower updates the status. Laptop Model: Acer Aspire E15 E5-573G-56JN Laptop battery and AC charger is not faulty as the charging/discharging status gets correctly detected when using Windows 10. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: upower 0.99.11-1build2 ProcVersionSignature: Ubuntu 5.13.0-39.44~20.04.1-generic 5.13.19 Uname: Linux 5.13.0-39-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.21 Architecture: amd64 CasperMD5CheckResult: skip Date: Fri Apr 1 23:07:12 2022 ExecutablePath: /usr/lib/upower/upowerd InstallationDate: Installed on 2022-04-01 (0 days ago) InstallationMedia: Ubuntu 20.04.4 LTS "Focal Fossa" - Release amd64 (20220223) ProcEnviron: LANG=en_IN LANGUAGE=en_IN:en PATH=(custom, no user) SourcePackage: upower UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/upower/+bug/1967565/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1967594] [NEW] Blurry when using fractional scaling on HiDPI.
Public bug reported: I'm using join-display with an built-in laptop HiDPI screen and an external 1920x1080 screens. I set fractional scaling 200% on HiDPI one and 100% on 1920x1080 one. The emacs window on 1920x1080 screen displays clearly, but blurs on the HiDPI one. If I switched to non-fractional scaling(still 200%, 100%), then it does not blur, but only the top-left area of my HiDPI screen displays while the remaining area is black. ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: emacs 1:27.1+1-3ubuntu5 ProcVersionSignature: Ubuntu 5.15.0-23.23-generic 5.15.27 Uname: Linux 5.15.0-23-generic x86_64 ApportVersion: 2.20.11-0ubuntu80 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: ubuntu:GNOME Date: Sat Apr 2 11:50:31 2022 InstallationDate: Installed on 2022-02-15 (46 days ago) InstallationMedia: Ubuntu 20.04.3 LTS "Focal Fossa" - Release amd64 (20210819) PackageArchitecture: all SourcePackage: emacs UpgradeStatus: Upgraded to jammy on 2022-04-02 (0 days ago) ** Affects: emacs (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug jammy third-party-packages wayland-session ** Attachment added: "blurry screenshot" https://bugs.launchpad.net/bugs/1967594/+attachment/5576009/+files/hidpi.png -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to emacs in Ubuntu. https://bugs.launchpad.net/bugs/1967594 Title: Blurry when using fractional scaling on HiDPI. Status in emacs package in Ubuntu: New Bug description: I'm using join-display with an built-in laptop HiDPI screen and an external 1920x1080 screens. I set fractional scaling 200% on HiDPI one and 100% on 1920x1080 one. The emacs window on 1920x1080 screen displays clearly, but blurs on the HiDPI one. If I switched to non-fractional scaling(still 200%, 100%), then it does not blur, but only the top-left area of my HiDPI screen displays while the remaining area is black. ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: emacs 1:27.1+1-3ubuntu5 ProcVersionSignature: Ubuntu 5.15.0-23.23-generic 5.15.27 Uname: Linux 5.15.0-23-generic x86_64 ApportVersion: 2.20.11-0ubuntu80 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: ubuntu:GNOME Date: Sat Apr 2 11:50:31 2022 InstallationDate: Installed on 2022-02-15 (46 days ago) InstallationMedia: Ubuntu 20.04.3 LTS "Focal Fossa" - Release amd64 (20210819) PackageArchitecture: all SourcePackage: emacs UpgradeStatus: Upgraded to jammy on 2022-04-02 (0 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/emacs/+bug/1967594/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1871538] Autopkgtest regression report (systemd/248.3-1ubuntu8.5)
All autopkgtests for the newly accepted systemd (248.3-1ubuntu8.5) for impish have finished running. The following regressions have been reported in tests triggered by the package: snapd/2.54.3+21.10.1ubuntu0.2 (s390x, ppc64el, arm64, amd64) casper/1.465 (amd64) tpm2-abrmd/unknown (ppc64el) corosync-qdevice/unknown (ppc64el) nftables/unknown (ppc64el) udisks2/2.9.4-1 (arm64) diaspora-installer/0.7.15.0+debian1 (arm64, s390x) systemd/248.3-1ubuntu8.5 (armhf) swupdate/2020.11-2 (s390x) munin/2.0.57-1ubuntu1 (arm64, amd64) Please visit the excuses page listed below and investigate the failures, proceeding afterwards as per the StableReleaseUpdates policy regarding autopkgtest regressions [1]. https://people.canonical.com/~ubuntu-archive/proposed- migration/impish/update_excuses.html#systemd [1] https://wiki.ubuntu.com/StableReleaseUpdates#Autopkgtest_Regressions Thank you! -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-shell in Ubuntu. https://bugs.launchpad.net/bugs/1871538 Title: dbus timeout-ed during an upgrade, taking services down including gdm Status in D-Bus: Unknown Status in systemd: New Status in accountsservice package in Ubuntu: Invalid Status in dbus package in Ubuntu: Invalid Status in gnome-shell package in Ubuntu: Invalid Status in systemd package in Ubuntu: Fix Released Status in accountsservice source package in Focal: Invalid Status in dbus source package in Focal: Invalid Status in gnome-shell source package in Focal: Invalid Status in systemd source package in Focal: Fix Committed Status in accountsservice source package in Groovy: Invalid Status in dbus source package in Groovy: Invalid Status in gnome-shell source package in Groovy: Invalid Status in accountsservice source package in Hirsute: Invalid Status in dbus source package in Hirsute: Won't Fix Status in gnome-shell source package in Hirsute: Invalid Status in accountsservice source package in Impish: Invalid Status in dbus source package in Impish: Invalid Status in gnome-shell source package in Impish: Invalid Status in systemd source package in Impish: Fix Committed Status in accountsservice source package in Jammy: Invalid Status in dbus source package in Jammy: Invalid Status in gnome-shell source package in Jammy: Invalid Status in systemd source package in Jammy: Fix Released Bug description: [Impact] * There's currently a deadlock between PID 1 and dbus-daemon: in some cases dbus-daemon will do NSS lookups (which are blocking) at the same time PID 1 synchronously blocks on some call to dbus-daemon (e.g. `GetConnectionUnixUser` DBus call). Let's break that by setting SYSTEMD_NSS_DYNAMIC_BYPASS=1 env var for dbus-daemon, which will disable synchronously blocking varlink calls from nss-systemd to PID 1. * This can lead to delayed boot times * It can also lead to dbus-daemon being killed/re-started, taking down other services with it, like GDM, killing user sessions on the way (e.g. on installing updates) [Test Plan] * This bug is really hard to reproduce, as can be seen from the multi-year long discussion at https://github.com/systemd/systemd/issues/15316 * Canonical's CPC team has the ability to reproduce this issue (with a relatively high probability) in their Azure test environment, due to the specific setup they are using * So our test plan is to ask CPC (@gjolly) for confirmation if the issue is fixed. [Where problems could occur] * This fix touches the communication between systemd and dbus daemon, especially the NSS lookup, so if something is broken the (user-)name resolution could be broken. * As a workaround dbus-daemon could be replaced by dbus-broker, which never showed this issue or the behaviour could be changed back by using the `SYSTEMD_NSS_DYNAMIC_BYPASS` env variable, like this: #/etc/systemd/system/dbus.service.d/override.conf [Service] Environment=SYSTEMD_NSS_DYNAMIC_BYPASS=0 [Other Info] * Fixed upstream (v251) in https://github.com/systemd/systemd/pull/22552 === Original Description === This morning I found my computer on the login screen. But not the one of the screen log, no a new one - so something must have crashed. Logging in again confirmed that all apps were gone and the gnome shell was brought down what seems like triggered by a background update o accountsservice. As always things are not perfectly clear :-/ The following goes *back* in time through my logs one by one. Multiple apps crashed at 06:09, but we will find later that this is a follow on issue of the underlying gnome/X/... recycling. -rw-r- 1 paelzer whoopsie 52962868 Apr 8 06:09 _usr_bin_konversation.1000.crash -rw-r- 1 paelzer whoopsie 986433 Apr 8 06:09 _usr_lib_x86_64-linux-gnu_libexec_drkonqi.1000.crash rdkit was failing fast and giving up (that will be a
[Desktop-packages] [Bug 1967521] Re: Test binaries in libsndfile-dev package
Ok, thank you. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to libsndfile in Ubuntu. https://bugs.launchpad.net/bugs/1967521 Title: Test binaries in libsndfile-dev package Status in libsndfile package in Ubuntu: New Bug description: There are programs from the libsndfile test suite in dev package. Should they be there? To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libsndfile/+bug/1967521/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1967587] Re: udisksd assert failure: malloc_consolidate(): unaligned fastbin chunk detected
*** This bug is a duplicate of bug 1955758 *** https://bugs.launchpad.net/bugs/1955758 Thank you for taking the time to report this crash and helping to make this software better. This particular crash has already been reported and is a duplicate of bug #1955758, so is being marked as such. Please look at the other bug report to see if there is any missing information that you can provide, or to see if there is a workaround for the bug. Additionally, any further discussion regarding the bug should occur in the other report. Please continue to report any other bugs you may find. ** Attachment removed: "CoreDump.gz" https://bugs.launchpad.net/bugs/1967587/+attachment/5575918/+files/CoreDump.gz ** Attachment removed: "Disassembly.txt" https://bugs.launchpad.net/bugs/1967587/+attachment/5575921/+files/Disassembly.txt ** Attachment removed: "ProcMaps.txt" https://bugs.launchpad.net/bugs/1967587/+attachment/5575932/+files/ProcMaps.txt ** Attachment removed: "ProcStatus.txt" https://bugs.launchpad.net/bugs/1967587/+attachment/5575934/+files/ProcStatus.txt ** Attachment removed: "Registers.txt" https://bugs.launchpad.net/bugs/1967587/+attachment/5575935/+files/Registers.txt ** Attachment removed: "Stacktrace.txt" https://bugs.launchpad.net/bugs/1967587/+attachment/5575936/+files/Stacktrace.txt ** Attachment removed: "ThreadStacktrace.txt" https://bugs.launchpad.net/bugs/1967587/+attachment/5575937/+files/ThreadStacktrace.txt ** This bug has been marked a duplicate of private bug 1955758 ** Information type changed from Private to Public ** Tags removed: need-amd64-retrace -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to udisks2 in Ubuntu. https://bugs.launchpad.net/bugs/1967587 Title: udisksd assert failure: malloc_consolidate(): unaligned fastbin chunk detected Status in udisks2 package in Ubuntu: New Bug description: Happens after every new login ProblemType: Crash DistroRelease: Ubuntu 22.04 Package: udisks2 2.9.4-1 ProcVersionSignature: Ubuntu 5.15.0-23.23-generic 5.15.27 Uname: Linux 5.15.0-23-generic x86_64 ApportVersion: 2.20.11-0ubuntu80 Architecture: amd64 AssertionMessage: malloc_consolidate(): unaligned fastbin chunk detected CasperMD5CheckResult: pass CustomUdevRuleFiles: 70-snap.firefox.rules 70-snap.snap-store.rules 70-snap.snapd.rules 70-snap.snapd-desktop-integration.rules Date: Tue Mar 29 00:54:26 2022 ExecutablePath: /usr/libexec/udisks2/udisksd InstallationDate: Installed on 2022-03-29 (3 days ago) InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Alpha amd64 (20220324.3) MachineType: Hewlett-Packard HP Compaq 8200 Elite SFF PC ProcCmdline: /usr/libexec/udisks2/udisksd ProcEnviron: LANG=en_US.UTF-8 PATH=(custom, no user) ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.15.0-23-generic root=/dev/mapper/vgubuntu-root ro quiet splash vt.handoff=7 Signal: 6 SourcePackage: udisks2 StacktraceTop: __libc_message (action=action@entry=do_abort, fmt=fmt@entry=0x7f0c10384b8c "%s\n") at ../sysdeps/posix/libc_fatal.c:155 malloc_printerr (str=str@entry=0x7f0c103875d8 "malloc_consolidate(): unaligned fastbin chunk detected") at ./malloc/malloc.c:5664 malloc_consolidate (av=av@entry=0x7f0c103c2c80 ) at ./malloc/malloc.c:4750 _int_free (av=0x7f0c103c2c80 , p=0x55d9f8aa59a0, have_lock=) at ./malloc/malloc.c:4674 __GI___libc_free (mem=) at ./malloc/malloc.c:3391 Title: udisksd assert failure: malloc_consolidate(): unaligned fastbin chunk detected UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: N/A dmi.bios.date: 11/10/2011 dmi.bios.release: 2.15 dmi.bios.vendor: Hewlett-Packard dmi.bios.version: J01 v02.15 dmi.board.asset.tag: 2UA23514LJ dmi.board.name: 1495 dmi.board.vendor: Hewlett-Packard dmi.chassis.asset.tag: 2UA23514LJ dmi.chassis.type: 6 dmi.chassis.vendor: Hewlett-Packard dmi.modalias: dmi:bvnHewlett-Packard:bvrJ01v02.15:bd11/10/2011:br2.15:svnHewlett-Packard:pnHPCompaq8200EliteSFFPC:pvr:rvnHewlett-Packard:rn1495:rvr:cvnHewlett-Packard:ct6:cvr:skuH0E56EP#ABA: dmi.product.family: 103C_53307F G=D dmi.product.name: HP Compaq 8200 Elite SFF PC dmi.product.sku: H0E56EP#ABA dmi.sys.vendor: Hewlett-Packard separator: To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/udisks2/+bug/1967587/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1966571] Re: libva error: /usr/lib/x86_64-linux-gnu/dri/i965_drv_video.so init failed
Ubuntu 22.04. I still have this problem intel-media-va-driver 22.3.0 tigerlake laptop $ apt-cache show intel-media-va-driver Package: intel-media-va-driver Architecture: amd64 Version: 22.3.0+dfsg1-1 tim@ochre:~$ vainfo libva info: VA-API version 1.14.0 libva info: Trying to open /usr/lib/x86_64-linux-gnu/dri/iHD_drv_video.so libva info: Found init function __vaDriverInit_1_14 libva error: /usr/lib/x86_64-linux-gnu/dri/iHD_drv_video.so init failed libva info: va_openDriver() returns 1 libva info: Trying to open /usr/lib/x86_64-linux-gnu/dri/i965_drv_video.so libva info: Found init function __vaDriverInit_1_10 libva error: /usr/lib/x86_64-linux-gnu/dri/i965_drv_video.so init failed libva info: va_openDriver() returns -1 vaInitialize failed with error code -1 (unknown libva error),exit tim@ochre:~$ -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to mesa in Ubuntu. https://bugs.launchpad.net/bugs/1966571 Title: libva error: /usr/lib/x86_64-linux-gnu/dri/i965_drv_video.so init failed Status in intel-media-driver package in Ubuntu: Fix Released Status in intel-media-driver-non-free package in Ubuntu: Fix Released Status in mesa package in Ubuntu: Invalid Bug description: I noticed that it upgraded mesa to 22.x and now video acceleration is not working due to: ❯ vainfo libva info: VA-API version 1.14.0 libva info: Trying to open /usr/lib/x86_64-linux-gnu/dri/iHD_drv_video.so libva info: Found init function __vaDriverInit_1_14 libva error: /usr/lib/x86_64-linux-gnu/dri/iHD_drv_video.so init failed libva info: va_openDriver() returns 1 libva info: Trying to open /usr/lib/x86_64-linux-gnu/dri/i965_drv_video.so libva info: Found init function __vaDriverInit_1_10 libva error: /usr/lib/x86_64-linux-gnu/dri/i965_drv_video.so init failed libva info: va_openDriver() returns -1 vaInitialize failed with error code -1 (unknown libva error),exit ~/Desktop ❯ inxi -G Graphics: Device-1: Intel driver: i915 v: kernel Device-2: Generalplus GENERAL WEBCAM type: USB driver: snd-usb-audio,uvcvideo Display: x11 server: X.Org v: 1.21.1.3 driver: X: loaded: modesetting unloaded: fbdev,vesa gpu: i915 resolution: 3840x2160~60Hz OpenGL: renderer: Mesa Intel UHD Graphics P630 (CML GT2) v: 4.6 Mesa 22.0.0 I tried rebuilding the i965-va-driver, and it's still the same. ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: mesa-vdpau-drivers 22.0.0-0ubuntu2 ProcVersionSignature: Ubuntu 5.15.0-23.23-generic 5.15.27 Uname: Linux 5.15.0-23-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.20.11-0ubuntu79 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CasperMD5CheckResult: pass CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Sun Mar 27 10:37:41 2022 DistUpgraded: 2022-01-18 23:59:55,390 DEBUG Running PostInstallScript: '/usr/lib/ubuntu-advantage/upgrade_lts_contract.py' DistroCodename: jammy DistroVariant: ubuntu DkmsStatus: rtl88x2bu/5.8.7.1, 5.15.0-18-generic, x86_64: installed rtl88x2bu/5.8.7.1, 5.15.0-22-generic, x86_64: installed rtl88x2bu/5.8.7.1, 5.15.0-23-generic, x86_64: installed rtl88x2bu/5.8.7.1, 5.17.0-xanmod1, x86_64: installed ExtraDebuggingInterest: Yes GraphicsCard: Intel Corporation Device [8086:9bc6] (rev 05) (prog-if 00 [VGA controller]) Subsystem: ASUSTeK Computer Inc. Device [1043:8694] InstallationDate: Installed on 2021-10-05 (172 days ago) InstallationMedia: Ubuntu-Server 21.10 "Impish Indri" - Beta amd64 (20211004) MachineType: ASUS System Product Name ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_PH.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.15.0-23-generic root=UUID=018d5b69-accd-451b-a6f7-2027f791ea0e ro quiet splash vt.handoff=7 SourcePackage: mesa UpgradeStatus: Upgraded to jammy on 2022-01-18 (67 days ago) dmi.bios.date: 07/08/2021 dmi.bios.release: 23.1 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 2301 dmi.board.asset.tag: Default string dmi.board.name: Pro WS W480-ACE dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: Rev 1.xx dmi.chassis.asset.tag: Default string dmi.chassis.type: 3 dmi.chassis.vendor: Default string dmi.chassis.version: Default string dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr2301:bd07/08/2021:br23.1:svnASUS:pnSystemProductName:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnProWSW480-ACE:rvrRev1.xx:cvnDefaultstring:ct3:cvrDefaultstring:skuSKU: dmi.product.family: To be filled by O.E.M. dmi.product.name: System Product Name dmi.product.sku: SKU dmi.product.version: System Version dmi.sys.vendor: ASUS version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.110-1ubuntu1 version.libgl1-mesa-dri: libgl1-mesa-dri 22.0.0-0ubuntu2
[Desktop-packages] [Bug 1967585] [NEW] Failed to start ZSYS daemon service (panic: runtime error)
Public bug reported: After upgrading from 0.5.8 to 0.5.8build2 this bug started appearing. Previously I was facing bug 1966818 ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: zsys 0.5.8build2 ProcVersionSignature: Ubuntu 5.15.0-23.23-generic 5.15.27 Uname: Linux 5.15.0-23-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu80 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Sat Apr 2 02:04:01 2022 InstallationDate: Installed on 2022-02-23 (37 days ago) InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Alpha amd64 (20220223) Mounts: Error: [Errno 40] Zu viele Ebenen aus symbolischen Links: '/proc/mounts' ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=de_DE.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/BOOT/ubuntu_m9rbzq@/vmlinuz-5.15.0-23-generic root=ZFS=rpool/ROOT/ubuntu_m9rbzq ro nvidia-drm.modeset=1 pci=realloc,assign-busses,hpbussize=0x33 RelatedPackageVersions: zfs-initramfs 2.1.2-1ubuntu3 zfsutils-linux 2.1.2-1ubuntu3 SourcePackage: zsys 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. -- 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: No upgrade log present (probably fresh install) ZFSImportedPools: NAMESIZE ALLOC FREE CKPOINT EXPANDSZ FRAGCAP DEDUPHEALTH ALTROOT bpool 1.88G 1.08G 816M- -10%57% 1.00xONLINE - qpool 7.27T 1.08M 7.27T- - 0% 0% 1.00xONLINE - rpool 1.84T 315G 1.54T- - 4%16% 1.00xONLINE - ZFSListcache-bpool: bpool /boot off on on off on off on off - none- - - - - - - - bpool/BOOT noneoff on on off on off on off - none- - - - - - - - bpool/BOOT/ubuntu_m9rbzq /boot on on on off on off on off - none- - - - - - - - ZFSListcache-qpool: qpool /qpool on on on on on off on off qpool file:///run/keystore/rpool/system.key - - - - - - - - ZSYSDump: Error: command ['zsysctl', 'service', 'dump'] failed with exit code 1: level=error msg="couldn't connect to zsys daemon: connection error: desc = \"transport: Error while dialing dial unix /run/zsysd.sock: connect: connection refused\"" ** Affects: zsys (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug jammy wayland-session -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to zsys in Ubuntu. https://bugs.launchpad.net/bugs/1967585 Title: Failed to start ZSYS daemon service (panic: runtime error) Status in zsys package in Ubuntu: New Bug description: After upgrading from 0.5.8 to 0.5.8build2 this bug started appearing. Previously I was facing bug 1966818 ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: zsys 0.5.8build2 ProcVersionSignature: Ubuntu 5.15.0-23.23-generic 5.15.27 Uname: Linux 5.15.0-23-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu80 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Sat Apr 2 02:04:01 2022 InstallationDate: Installed on 2022-02-23 (37 days ago) InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Alpha amd64 (20220223) Mounts: Error: [Errno 40] Zu viele Ebenen aus symbolischen Links: '/proc/mounts' ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=de_DE.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/BOOT/ubuntu_m9rbzq@/vmlinuz-5.15.0-23-generic root=ZFS=rpool/ROOT/ubuntu_m9rbzq ro nvidia-drm.modeset=1 pci=realloc,assign-busses,hpbussize=0x33 RelatedPackageVersions: zfs-initramfs 2.1.2-1ubuntu3 zfsutils-linux 2.1.2-1ubuntu3 SourcePackage: zsys 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. -- Error: command ['systemctl', 'status', '--full', '●'] failed with exit code 4: Invalid unit name "●" escaped as "\xe2\x97\x8f" (maybe you should use systemd-escape?).
[Desktop-packages] [Bug 1967580] Re: Gnome not loading on boot after fresh install.
** Package changed: ubuntu => gnome-shell (Ubuntu) -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-shell in Ubuntu. https://bugs.launchpad.net/bugs/1967580 Title: Gnome not loading on boot after fresh install. Status in gnome-shell package in Ubuntu: New Bug description: After fresh install. I am getting no login screen. Screen blanks out. Had to open command to submit bug. Was able to startx via command prompt. ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: gnome-shell 42~beta-1ubuntu3 ProcVersionSignature: Ubuntu 5.15.0-23.23-generic 5.15.27 Uname: Linux 5.15.0-23-generic x86_64 ApportVersion: 2.20.11-0ubuntu79 Architecture: amd64 CasperMD5CheckResult: pass Date: Fri Apr 1 17:54:03 2022 DisplayManager: gdm3 GsettingsChanges: InstallationDate: Installed on 2022-04-01 (0 days ago) InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Beta amd64 (20220329.1) ProcEnviron: TERM=linux PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash RelatedPackageVersions: mutter-common 42~beta-1ubuntu2 SourcePackage: gnome-shell UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1967580/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1967580] [NEW] Gnome not loading on boot after fresh install.
You have been subscribed to a public bug: After fresh install. I am getting no login screen. Screen blanks out. Had to open command to submit bug. Was able to startx via command prompt. ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: gnome-shell 42~beta-1ubuntu3 ProcVersionSignature: Ubuntu 5.15.0-23.23-generic 5.15.27 Uname: Linux 5.15.0-23-generic x86_64 ApportVersion: 2.20.11-0ubuntu79 Architecture: amd64 CasperMD5CheckResult: pass Date: Fri Apr 1 17:54:03 2022 DisplayManager: gdm3 GsettingsChanges: InstallationDate: Installed on 2022-04-01 (0 days ago) InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Beta amd64 (20220329.1) ProcEnviron: TERM=linux PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash RelatedPackageVersions: mutter-common 42~beta-1ubuntu2 SourcePackage: gnome-shell UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: gnome-shell (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug jammy -- Gnome not loading on boot after fresh install. https://bugs.launchpad.net/bugs/1967580 You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-shell in Ubuntu. -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1966418] Re: [jammy regression] Evolution does not display message content anymore
** Changed in: webkit Status: Confirmed => Unknown -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to mesa in Ubuntu. https://bugs.launchpad.net/bugs/1966418 Title: [jammy regression] Evolution does not display message content anymore Status in Gnome DevHelp: Invalid Status in Mesa: Unknown Status in Webkit: Unknown Status in epiphany-browser package in Ubuntu: Invalid Status in evolution package in Ubuntu: Invalid Status in gnome-control-center package in Ubuntu: Invalid Status in liferea package in Ubuntu: Invalid Status in mesa package in Ubuntu: Confirmed Status in webkit2gtk package in Ubuntu: Confirmed Bug description: Impact -- All webkit using apps for affected users display a blank screen. Original Bug Report --- Evolution has suddenly stopped displaying message contents on the last 24h. Starting it up from the command line shows this output: ``` EGLDisplay Initialization failed: EGL_NOT_INITIALIZED Cannot create EGL context: invalid display (last error: EGL_SUCCESS) ``` I don't know if it's related, but googling around shows some webkitgtk hits on this error. The email contents are however clickable. They're just not rendered to screen (see attached file). Deleting the evolution folders from `~/.config`, `~/.cache` and `~/.local/share` does not help. Email accounts are all google, configured through gnome online accounts. Workaround #1 - You can run the app from the command line with WEBKIT_DISABLE_COMPOSITING_MODE=1 evolution (Replace evolution with the name of the webkit app you are trying to use) Workaround #2 - Log out. Select your name on the login screen. Click the gear button and choose Ubuntu on Xorg. Enter your password to finish logging in. ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: evolution 3.44.0-1 ProcVersionSignature: Ubuntu 5.15.0-23.23-generic 5.15.27 Uname: Linux 5.15.0-23-generic x86_64 ApportVersion: 2.20.11-0ubuntu79 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: sway Date: Fri Mar 25 10:55:49 2022 SourcePackage: evolution UpgradeStatus: Upgraded to jammy on 2022-03-01 (24 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/devhelp/+bug/1966418/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1966418]
(In reply to Marian Rainer-Harbach from comment #7) > This issue occurs on my machine as well, which has an AMD GPU. So it does > not seem to be directly related to the graphics driver in use. Beware: if you're not certain the issue is caused by the same mesa 21.3 -> 22.0 upgrade, you might have a different underlying issue. Anyway, I'm going to close this as MOVED since the issue is being tracked by mesa now and it seems unlikely that WebKit developers will be able to help more. We can reopen if the mesa issue gets closed. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to mesa in Ubuntu. https://bugs.launchpad.net/bugs/1966418 Title: [jammy regression] Evolution does not display message content anymore Status in Gnome DevHelp: Invalid Status in Mesa: Unknown Status in Webkit: Unknown Status in epiphany-browser package in Ubuntu: Invalid Status in evolution package in Ubuntu: Invalid Status in gnome-control-center package in Ubuntu: Invalid Status in liferea package in Ubuntu: Invalid Status in mesa package in Ubuntu: Confirmed Status in webkit2gtk package in Ubuntu: Confirmed Bug description: Impact -- All webkit using apps for affected users display a blank screen. Original Bug Report --- Evolution has suddenly stopped displaying message contents on the last 24h. Starting it up from the command line shows this output: ``` EGLDisplay Initialization failed: EGL_NOT_INITIALIZED Cannot create EGL context: invalid display (last error: EGL_SUCCESS) ``` I don't know if it's related, but googling around shows some webkitgtk hits on this error. The email contents are however clickable. They're just not rendered to screen (see attached file). Deleting the evolution folders from `~/.config`, `~/.cache` and `~/.local/share` does not help. Email accounts are all google, configured through gnome online accounts. Workaround #1 - You can run the app from the command line with WEBKIT_DISABLE_COMPOSITING_MODE=1 evolution (Replace evolution with the name of the webkit app you are trying to use) Workaround #2 - Log out. Select your name on the login screen. Click the gear button and choose Ubuntu on Xorg. Enter your password to finish logging in. ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: evolution 3.44.0-1 ProcVersionSignature: Ubuntu 5.15.0-23.23-generic 5.15.27 Uname: Linux 5.15.0-23-generic x86_64 ApportVersion: 2.20.11-0ubuntu79 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: sway Date: Fri Mar 25 10:55:49 2022 SourcePackage: evolution UpgradeStatus: Upgraded to jammy on 2022-03-01 (24 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/devhelp/+bug/1966418/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1966418]
This issue occurs on my machine as well, which has an AMD GPU. So it does not seem to be directly related to the graphics driver in use. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to mesa in Ubuntu. https://bugs.launchpad.net/bugs/1966418 Title: [jammy regression] Evolution does not display message content anymore Status in Gnome DevHelp: Invalid Status in Mesa: Unknown Status in Webkit: Unknown Status in epiphany-browser package in Ubuntu: Invalid Status in evolution package in Ubuntu: Invalid Status in gnome-control-center package in Ubuntu: Invalid Status in liferea package in Ubuntu: Invalid Status in mesa package in Ubuntu: Confirmed Status in webkit2gtk package in Ubuntu: Confirmed Bug description: Impact -- All webkit using apps for affected users display a blank screen. Original Bug Report --- Evolution has suddenly stopped displaying message contents on the last 24h. Starting it up from the command line shows this output: ``` EGLDisplay Initialization failed: EGL_NOT_INITIALIZED Cannot create EGL context: invalid display (last error: EGL_SUCCESS) ``` I don't know if it's related, but googling around shows some webkitgtk hits on this error. The email contents are however clickable. They're just not rendered to screen (see attached file). Deleting the evolution folders from `~/.config`, `~/.cache` and `~/.local/share` does not help. Email accounts are all google, configured through gnome online accounts. Workaround #1 - You can run the app from the command line with WEBKIT_DISABLE_COMPOSITING_MODE=1 evolution (Replace evolution with the name of the webkit app you are trying to use) Workaround #2 - Log out. Select your name on the login screen. Click the gear button and choose Ubuntu on Xorg. Enter your password to finish logging in. ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: evolution 3.44.0-1 ProcVersionSignature: Ubuntu 5.15.0-23.23-generic 5.15.27 Uname: Linux 5.15.0-23-generic x86_64 ApportVersion: 2.20.11-0ubuntu79 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: sway Date: Fri Mar 25 10:55:49 2022 SourcePackage: evolution UpgradeStatus: Upgraded to jammy on 2022-03-01 (24 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/devhelp/+bug/1966418/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1965673] Re: Object 0x... of type IBusText has been finalized while it was still owned by gjs, this is due to invalid memory management
Sounds like https://github.com/ibus/ibus/pull/2394 might fix the issue? -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to ibus in Ubuntu. https://bugs.launchpad.net/bugs/1965673 Title: Object 0x... of type IBusText has been finalized while it was still owned by gjs, this is due to invalid memory management Status in ibus: Unknown Status in gnome-shell package in Ubuntu: Confirmed Status in ibus package in Ubuntu: Confirmed Bug description: Ubuntu 22.04 development branch @ 20/03/2022 Journal logs spam a lot of lines like these: mrt 20 13:36:38 R00TB00K gnome-shell[3452]: Object 0x7f896cf7cad0 of type IBusText has been finalized while it was still owned by gjs, this is due to invalid memory management. mrt 20 13:36:38 R00TB00K gnome-shell[3452]: Object 0x557a992efd20 of type IBusText has been finalized while it was still owned by gjs, this is due to invalid memory management Probably regression bug upstream: https://gitlab.gnome.org/GNOME/gnome-shell/-/issues/5147 ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: gnome-shell 42~beta-1ubuntu2 ProcVersionSignature: Ubuntu 5.15.0-22.22-generic 5.15.19 Uname: Linux 5.15.0-22-generic x86_64 ApportVersion: 2.20.11-0ubuntu79 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: ubuntu:GNOME Date: Sun Mar 20 13:34:37 2022 DisplayManager: gdm3 RelatedPackageVersions: mutter-common 42~beta-1ubuntu2 SourcePackage: gnome-shell UpgradeStatus: No upgrade log present (probably fresh install) mtime.conffile..etc.xdg.autostart.gnome-shell-overrides-migration.desktop: 2021-10-23T19:12:47.175230 To manage notifications about this bug go to: https://bugs.launchpad.net/ibus/+bug/1965673/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1871538] Autopkgtest regression report (systemd/248.3-1ubuntu8.4)
All autopkgtests for the newly accepted systemd (248.3-1ubuntu8.4) for impish have finished running. The following regressions have been reported in tests triggered by the package: systemd/248.3-1ubuntu8.4 (arm64, ppc64el) Please visit the excuses page listed below and investigate the failures, proceeding afterwards as per the StableReleaseUpdates policy regarding autopkgtest regressions [1]. https://people.canonical.com/~ubuntu-archive/proposed- migration/impish/update_excuses.html#systemd [1] https://wiki.ubuntu.com/StableReleaseUpdates#Autopkgtest_Regressions Thank you! -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-shell in Ubuntu. https://bugs.launchpad.net/bugs/1871538 Title: dbus timeout-ed during an upgrade, taking services down including gdm Status in D-Bus: Unknown Status in systemd: New Status in accountsservice package in Ubuntu: Invalid Status in dbus package in Ubuntu: Invalid Status in gnome-shell package in Ubuntu: Invalid Status in systemd package in Ubuntu: Fix Released Status in accountsservice source package in Focal: Invalid Status in dbus source package in Focal: Invalid Status in gnome-shell source package in Focal: Invalid Status in systemd source package in Focal: Fix Committed Status in accountsservice source package in Groovy: Invalid Status in dbus source package in Groovy: Invalid Status in gnome-shell source package in Groovy: Invalid Status in accountsservice source package in Hirsute: Invalid Status in dbus source package in Hirsute: Won't Fix Status in gnome-shell source package in Hirsute: Invalid Status in accountsservice source package in Impish: Invalid Status in dbus source package in Impish: Invalid Status in gnome-shell source package in Impish: Invalid Status in systemd source package in Impish: Fix Committed Status in accountsservice source package in Jammy: Invalid Status in dbus source package in Jammy: Invalid Status in gnome-shell source package in Jammy: Invalid Status in systemd source package in Jammy: Fix Released Bug description: [Impact] * There's currently a deadlock between PID 1 and dbus-daemon: in some cases dbus-daemon will do NSS lookups (which are blocking) at the same time PID 1 synchronously blocks on some call to dbus-daemon (e.g. `GetConnectionUnixUser` DBus call). Let's break that by setting SYSTEMD_NSS_DYNAMIC_BYPASS=1 env var for dbus-daemon, which will disable synchronously blocking varlink calls from nss-systemd to PID 1. * This can lead to delayed boot times * It can also lead to dbus-daemon being killed/re-started, taking down other services with it, like GDM, killing user sessions on the way (e.g. on installing updates) [Test Plan] * This bug is really hard to reproduce, as can be seen from the multi-year long discussion at https://github.com/systemd/systemd/issues/15316 * Canonical's CPC team has the ability to reproduce this issue (with a relatively high probability) in their Azure test environment, due to the specific setup they are using * So our test plan is to ask CPC (@gjolly) for confirmation if the issue is fixed. [Where problems could occur] * This fix touches the communication between systemd and dbus daemon, especially the NSS lookup, so if something is broken the (user-)name resolution could be broken. * As a workaround dbus-daemon could be replaced by dbus-broker, which never showed this issue or the behaviour could be changed back by using the `SYSTEMD_NSS_DYNAMIC_BYPASS` env variable, like this: #/etc/systemd/system/dbus.service.d/override.conf [Service] Environment=SYSTEMD_NSS_DYNAMIC_BYPASS=0 [Other Info] * Fixed upstream (v251) in https://github.com/systemd/systemd/pull/22552 === Original Description === This morning I found my computer on the login screen. But not the one of the screen log, no a new one - so something must have crashed. Logging in again confirmed that all apps were gone and the gnome shell was brought down what seems like triggered by a background update o accountsservice. As always things are not perfectly clear :-/ The following goes *back* in time through my logs one by one. Multiple apps crashed at 06:09, but we will find later that this is a follow on issue of the underlying gnome/X/... recycling. -rw-r- 1 paelzer whoopsie 52962868 Apr 8 06:09 _usr_bin_konversation.1000.crash -rw-r- 1 paelzer whoopsie 986433 Apr 8 06:09 _usr_lib_x86_64-linux-gnu_libexec_drkonqi.1000.crash rdkit was failing fast and giving up (that will be a different bug, it just seems broken on my system): Apr 08 06:10:13 Keschdeichel systemd[1]: Started RealtimeKit Scheduling Policy Service. Apr 08 06:10:13 Keschdeichel rtkit-daemon[1729333]: Successfully called chroot. Apr 08 06:10:13 Keschdeichel rtkit-daemon[1729333]: Successfully dropped
[Desktop-packages] [Bug 1959747]
Running on Fedora-35, with KDE, Radeon RX6600, and Thunderbird 91.7.0, I can confirm that the above suggested fix does *NOT* solve the high-cpu usage problem. Even after setting "gfx.webrender.force-disabled" to "true" (and confirming "gfx.webrender.all" to be "false"), moving the mouse over either the message list or the folder list results in high cpu usage and much sluggishness; I can easily move the mouse more than fast enough to have the "hover highlight" not be able to keep up. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to thunderbird in Ubuntu. https://bugs.launchpad.net/bugs/1959747 Title: [upstream] Very high CPU and slow responsiveness in Thunderbird 91 Status in Mozilla Thunderbird: Confirmed Status in thunderbird package in Ubuntu: Triaged Bug description: Very high CPU and slow responsiveness in Thunderbird 91.5.0. Just moving the mouse cursor over a message list results in 365% CPU for me. I had to set this in the config editor to fix it: gfx.webrender.force-disabled = TRUE Upstream bug: https://bugzilla.mozilla.org/show_bug.cgi?id=1730423 To manage notifications about this bug go to: https://bugs.launchpad.net/thunderbird/+bug/1959747/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1871538] Please test proposed package
Hello Christian, or anyone else affected, Accepted systemd into impish-proposed. The package will build now and be available at https://launchpad.net/ubuntu/+source/systemd/248.3-1ubuntu8.5 in a few hours, and then in the -proposed repository. Please help us by testing this new package. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation on how to enable and use -proposed. Your feedback will aid us getting this update out to other Ubuntu users. If this package fixes the bug for you, please add a comment to this bug, mentioning the version of the package you tested, what testing has been performed on the package and change the tag from verification-needed- impish to verification-done-impish. If it does not fix the bug for you, please add a comment stating that, and change the tag to verification- failed-impish. In either case, without details of your testing we will not be able to proceed. Further information regarding the verification process can be found at https://wiki.ubuntu.com/QATeam/PerformingSRUVerification . Thank you in advance for helping! N.B. The updated package will be released to -updates after the bug(s) fixed by this package have been verified and the package has been in -proposed for a minimum of 7 days. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-shell in Ubuntu. https://bugs.launchpad.net/bugs/1871538 Title: dbus timeout-ed during an upgrade, taking services down including gdm Status in D-Bus: Unknown Status in systemd: New Status in accountsservice package in Ubuntu: Invalid Status in dbus package in Ubuntu: Invalid Status in gnome-shell package in Ubuntu: Invalid Status in systemd package in Ubuntu: Fix Released Status in accountsservice source package in Focal: Invalid Status in dbus source package in Focal: Invalid Status in gnome-shell source package in Focal: Invalid Status in systemd source package in Focal: Fix Committed Status in accountsservice source package in Groovy: Invalid Status in dbus source package in Groovy: Invalid Status in gnome-shell source package in Groovy: Invalid Status in accountsservice source package in Hirsute: Invalid Status in dbus source package in Hirsute: Won't Fix Status in gnome-shell source package in Hirsute: Invalid Status in accountsservice source package in Impish: Invalid Status in dbus source package in Impish: Invalid Status in gnome-shell source package in Impish: Invalid Status in systemd source package in Impish: Fix Committed Status in accountsservice source package in Jammy: Invalid Status in dbus source package in Jammy: Invalid Status in gnome-shell source package in Jammy: Invalid Status in systemd source package in Jammy: Fix Released Bug description: [Impact] * There's currently a deadlock between PID 1 and dbus-daemon: in some cases dbus-daemon will do NSS lookups (which are blocking) at the same time PID 1 synchronously blocks on some call to dbus-daemon (e.g. `GetConnectionUnixUser` DBus call). Let's break that by setting SYSTEMD_NSS_DYNAMIC_BYPASS=1 env var for dbus-daemon, which will disable synchronously blocking varlink calls from nss-systemd to PID 1. * This can lead to delayed boot times * It can also lead to dbus-daemon being killed/re-started, taking down other services with it, like GDM, killing user sessions on the way (e.g. on installing updates) [Test Plan] * This bug is really hard to reproduce, as can be seen from the multi-year long discussion at https://github.com/systemd/systemd/issues/15316 * Canonical's CPC team has the ability to reproduce this issue (with a relatively high probability) in their Azure test environment, due to the specific setup they are using * So our test plan is to ask CPC (@gjolly) for confirmation if the issue is fixed. [Where problems could occur] * This fix touches the communication between systemd and dbus daemon, especially the NSS lookup, so if something is broken the (user-)name resolution could be broken. * As a workaround dbus-daemon could be replaced by dbus-broker, which never showed this issue or the behaviour could be changed back by using the `SYSTEMD_NSS_DYNAMIC_BYPASS` env variable, like this: #/etc/systemd/system/dbus.service.d/override.conf [Service] Environment=SYSTEMD_NSS_DYNAMIC_BYPASS=0 [Other Info] * Fixed upstream (v251) in https://github.com/systemd/systemd/pull/22552 === Original Description === This morning I found my computer on the login screen. But not the one of the screen log, no a new one - so something must have crashed. Logging in again confirmed that all apps were gone and the gnome shell was brought down what seems like triggered by a background update o accountsservice. As always things are not perfectly clear :-/ The following goes *back* in time through my logs one by one. Multiple
[Desktop-packages] [Bug 1967335] Re: Brightness is not show in desktop mode
** Package changed: ubuntu => gnome-control-center (Ubuntu) ** Changed in: gnome-control-center (Ubuntu) Importance: Undecided => Low ** Changed in: gnome-control-center (Ubuntu) Status: New => Triaged ** Bug watch added: gitlab.gnome.org/GNOME/gnome-control-center/-/issues #1209 https://gitlab.gnome.org/GNOME/gnome-control-center/-/issues/1209 ** Also affects: gnome-control-center via https://gitlab.gnome.org/GNOME/gnome-control-center/-/issues/1209 Importance: Unknown Status: Unknown -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-control-center in Ubuntu. https://bugs.launchpad.net/bugs/1967335 Title: Brightness is not show in desktop mode Status in gnome-control-center: Unknown Status in gnome-control-center package in Ubuntu: Triaged Bug description: The brightness level control is visible only on a notebook, but it is not visible on the desktop version. The brightness of both my monitors are excessive and I must be turning down and up from the rear buttons, I would prefer that I could manipulate the brightness from the control panel like with the notebook version. For some reason this control disappears in the desktop version. At the moment I must use xrand to lower the brightness manually, although when I lock the computer or restart it the brightness is restored and I must be running those commands multiple times during the day. ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: evince 42.1-1 ProcVersionSignature: Ubuntu 5.15.0-23.23-generic 5.15.27 Uname: Linux 5.15.0-23-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.20.11-0ubuntu79 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Thu Mar 31 13:35:45 2022 InstallationDate: Installed on 2022-03-30 (0 days ago) InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Alpha amd64 (20220326) SourcePackage: evince UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-control-center/+bug/1967335/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1967335] [NEW] Brightness is not show in desktop mode
You have been subscribed to a public bug: The brightness level control is visible only on a notebook, but it is not visible on the desktop version. The brightness of both my monitors are excessive and I must be turning down and up from the rear buttons, I would prefer that I could manipulate the brightness from the control panel like with the notebook version. For some reason this control disappears in the desktop version. At the moment I must use xrand to lower the brightness manually, although when I lock the computer or restart it the brightness is restored and I must be running those commands multiple times during the day. ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: evince 42.1-1 ProcVersionSignature: Ubuntu 5.15.0-23.23-generic 5.15.27 Uname: Linux 5.15.0-23-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.20.11-0ubuntu79 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Thu Mar 31 13:35:45 2022 InstallationDate: Installed on 2022-03-30 (0 days ago) InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Alpha amd64 (20220326) SourcePackage: evince UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: gnome-control-center (Ubuntu) Importance: Low Status: Triaged ** Tags: amd64 apport-bug jammy -- Brightness is not show in desktop mode https://bugs.launchpad.net/bugs/1967335 You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-control-center in Ubuntu. -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1871538] Re: dbus timeout-ed during an upgrade, taking services down including gdm
The autopkgtest regressions blocking systemd 245.4-4ubuntu3.16 in focal- proposed have been resolved. The regressions appear to have been related to recent autopkgtest infrastructure issues, and retrying the tests resolved the issues. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-shell in Ubuntu. https://bugs.launchpad.net/bugs/1871538 Title: dbus timeout-ed during an upgrade, taking services down including gdm Status in D-Bus: Unknown Status in systemd: New Status in accountsservice package in Ubuntu: Invalid Status in dbus package in Ubuntu: Invalid Status in gnome-shell package in Ubuntu: Invalid Status in systemd package in Ubuntu: Fix Released Status in accountsservice source package in Focal: Invalid Status in dbus source package in Focal: Invalid Status in gnome-shell source package in Focal: Invalid Status in systemd source package in Focal: Fix Committed Status in accountsservice source package in Groovy: Invalid Status in dbus source package in Groovy: Invalid Status in gnome-shell source package in Groovy: Invalid Status in accountsservice source package in Hirsute: Invalid Status in dbus source package in Hirsute: Won't Fix Status in gnome-shell source package in Hirsute: Invalid Status in accountsservice source package in Impish: Invalid Status in dbus source package in Impish: Invalid Status in gnome-shell source package in Impish: Invalid Status in systemd source package in Impish: Fix Committed Status in accountsservice source package in Jammy: Invalid Status in dbus source package in Jammy: Invalid Status in gnome-shell source package in Jammy: Invalid Status in systemd source package in Jammy: Fix Released Bug description: [Impact] * There's currently a deadlock between PID 1 and dbus-daemon: in some cases dbus-daemon will do NSS lookups (which are blocking) at the same time PID 1 synchronously blocks on some call to dbus-daemon (e.g. `GetConnectionUnixUser` DBus call). Let's break that by setting SYSTEMD_NSS_DYNAMIC_BYPASS=1 env var for dbus-daemon, which will disable synchronously blocking varlink calls from nss-systemd to PID 1. * This can lead to delayed boot times * It can also lead to dbus-daemon being killed/re-started, taking down other services with it, like GDM, killing user sessions on the way (e.g. on installing updates) [Test Plan] * This bug is really hard to reproduce, as can be seen from the multi-year long discussion at https://github.com/systemd/systemd/issues/15316 * Canonical's CPC team has the ability to reproduce this issue (with a relatively high probability) in their Azure test environment, due to the specific setup they are using * So our test plan is to ask CPC (@gjolly) for confirmation if the issue is fixed. [Where problems could occur] * This fix touches the communication between systemd and dbus daemon, especially the NSS lookup, so if something is broken the (user-)name resolution could be broken. * As a workaround dbus-daemon could be replaced by dbus-broker, which never showed this issue or the behaviour could be changed back by using the `SYSTEMD_NSS_DYNAMIC_BYPASS` env variable, like this: #/etc/systemd/system/dbus.service.d/override.conf [Service] Environment=SYSTEMD_NSS_DYNAMIC_BYPASS=0 [Other Info] * Fixed upstream (v251) in https://github.com/systemd/systemd/pull/22552 === Original Description === This morning I found my computer on the login screen. But not the one of the screen log, no a new one - so something must have crashed. Logging in again confirmed that all apps were gone and the gnome shell was brought down what seems like triggered by a background update o accountsservice. As always things are not perfectly clear :-/ The following goes *back* in time through my logs one by one. Multiple apps crashed at 06:09, but we will find later that this is a follow on issue of the underlying gnome/X/... recycling. -rw-r- 1 paelzer whoopsie 52962868 Apr 8 06:09 _usr_bin_konversation.1000.crash -rw-r- 1 paelzer whoopsie 986433 Apr 8 06:09 _usr_lib_x86_64-linux-gnu_libexec_drkonqi.1000.crash rdkit was failing fast and giving up (that will be a different bug, it just seems broken on my system): Apr 08 06:10:13 Keschdeichel systemd[1]: Started RealtimeKit Scheduling Policy Service. Apr 08 06:10:13 Keschdeichel rtkit-daemon[1729333]: Successfully called chroot. Apr 08 06:10:13 Keschdeichel rtkit-daemon[1729333]: Successfully dropped privileges. Apr 08 06:10:13 Keschdeichel rtkit-daemon[1729333]: Successfully limited resources. Apr 08 06:10:13 Keschdeichel rtkit-daemon[1729333]: pthread_create failed: Resource temporarily unavailable Apr 08 06:10:13 Keschdeichel rtkit-daemon[1729333]: Canary thread running. Apr 08 06:10:13 Keschdeichel rtkit-daemon[1729333]: Exiting canary
[Desktop-packages] [Bug 1967574] Re: yelp crashed with SIGSEGV
*** This bug is a duplicate of bug 1966524 *** https://bugs.launchpad.net/bugs/1966524 Thank you for taking the time to report this crash and helping to make this software better. This particular crash has already been reported and is a duplicate of bug #1966524, so is being marked as such. Please look at the other bug report to see if there is any missing information that you can provide, or to see if there is a workaround for the bug. Additionally, any further discussion regarding the bug should occur in the other report. Please continue to report any other bugs you may find. ** Package changed: ubuntu => yelp (Ubuntu) ** Attachment removed: "CoreDump.gz" https://bugs.launchpad.net/bugs/1967574/+attachment/5575858/+files/CoreDump.gz ** Attachment removed: "Disassembly.txt" https://bugs.launchpad.net/bugs/1967574/+attachment/5575860/+files/Disassembly.txt ** Attachment removed: "ProcMaps.txt" https://bugs.launchpad.net/bugs/1967574/+attachment/5575864/+files/ProcMaps.txt ** Attachment removed: "ProcStatus.txt" https://bugs.launchpad.net/bugs/1967574/+attachment/5575865/+files/ProcStatus.txt ** Attachment removed: "Registers.txt" https://bugs.launchpad.net/bugs/1967574/+attachment/5575866/+files/Registers.txt ** Attachment removed: "Stacktrace.txt" https://bugs.launchpad.net/bugs/1967574/+attachment/5575867/+files/Stacktrace.txt ** Attachment removed: "ThreadStacktrace.txt" https://bugs.launchpad.net/bugs/1967574/+attachment/5575868/+files/ThreadStacktrace.txt ** This bug has been marked a duplicate of bug 1966524 yelp crashed with SIGSEGV in WebKit::WaylandCompositor::Buffer::createImage ** Information type changed from Private to Public ** Tags removed: need-amd64-retrace -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to yelp in Ubuntu. https://bugs.launchpad.net/bugs/1967574 Title: yelp crashed with SIGSEGV Status in yelp package in Ubuntu: New Bug description: lsb_release -rd Description: Ubuntu Jammy Jellyfish (development branch) Release: 22.04 apt-cache policy yelp yelp: Installed: 42.0-1 Candidate: 42.0-1 Version table: *** 42.0-1 500 500 http://fr.archive.ubuntu.com/ubuntu jammy/main amd64 Packages 100 /var/lib/dpkg/status I expected to launch Yelp but got a crash. ProblemType: Crash DistroRelease: Ubuntu 22.04 Package: yelp 42.0-1 ProcVersionSignature: Ubuntu 5.15.0-23.23-generic 5.15.27 Uname: Linux 5.15.0-23-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu80 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Fri Apr 1 21:25:49 2022 ExecutablePath: /usr/bin/yelp InstallationDate: Installed on 2022-04-01 (0 days ago) InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Beta amd64 (20220329.1) ProcCmdline: yelp SegvAnalysis: Segfault happened at: 0x7fb86d3fd30b:mov0x8,%rax PC (0x7fb86d3fd30b) ok source "0x8" (0x0008) not located in a known VMA region (needed readable region)! destination "%rax" ok SegvReason: reading NULL VMA Signal: 11 SourcePackage: yelp StacktraceTop: ?? () from /lib/x86_64-linux-gnu/libwebkit2gtk-4.0.so.37 ?? () from /lib/x86_64-linux-gnu/libffi.so.8 ?? () from /lib/x86_64-linux-gnu/libffi.so.8 ?? () from /lib/x86_64-linux-gnu/libwayland-server.so.0 ?? () from /lib/x86_64-linux-gnu/libwayland-server.so.0 Title: yelp crashed with SIGSEGV UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo separator: To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/yelp/+bug/1967574/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1967539] Re: All file downloads fail
I can confirm that this is not just related to firefox and snap. After adding the Brave browser, I am unable to be prompted to save downloaded files. The prompt does not appear. I have heard that this is also apparent in Chrome. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to firefox in Ubuntu. https://bugs.launchpad.net/bugs/1967539 Title: All file downloads fail Status in firefox package in Ubuntu: New Bug description: Moving to the snap version results in all file download failing. Message is just "failed". ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: firefox 1:1snap1-0ubuntu2 Uname: Linux 5.16.0-18.2-liquorix-amd64 x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu80 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: KDE Date: Fri Apr 1 15:56:13 2022 InstallationDate: Installed on 2017-12-06 (1577 days ago) InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20171018) RebootRequiredPkgs: Error: path contained symlinks. Snap.Changes: no changes found SourcePackage: firefox UpgradeStatus: Upgraded to jammy on 2021-12-08 (114 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/firefox/+bug/1967539/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1963628] Re: Force IIO_SENSOR_PROXY_TYPE to iio-buffer-als for some Dell models
I've gone ahead and sponsored this, thanks for making the changes.
$ dput iio-sensor-proxy_2.8-1ubuntu2_source.changes
Trying to upload package to ubuntu
Checking signature on .changes
gpg: /tmp/pkgs/focal/iio-sensor-proxy_2.8-1ubuntu2_source.changes: Valid
signature from 1E918B66765B3E31
Checking signature on .dsc
gpg: /tmp/pkgs/focal/iio-sensor-proxy_2.8-1ubuntu2.dsc: Valid signature from
1E918B66765B3E31
Uploading to ubuntu (via ftp to upload.ubuntu.com):
Uploading iio-sensor-proxy_2.8-1ubuntu2.dsc: done.
Uploading iio-sensor-proxy_2.8-1ubuntu2.debian.tar.xz: done.
Uploading iio-sensor-proxy_2.8-1ubuntu2_source.buildinfo: done.
Uploading iio-sensor-proxy_2.8-1ubuntu2_source.changes: done.
Successfully uploaded packages.
** Changed in: iio-sensor-proxy (Ubuntu Focal)
Status: New => In Progress
** Changed in: iio-sensor-proxy (Ubuntu Focal)
Importance: Undecided => High
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to iio-sensor-proxy in Ubuntu.
https://bugs.launchpad.net/bugs/1963628
Title:
Force IIO_SENSOR_PROXY_TYPE to iio-buffer-als for some Dell models
Status in OEM Priority Project:
New
Status in iio-sensor-proxy package in Ubuntu:
Fix Released
Status in iio-sensor-proxy source package in Focal:
In Progress
Bug description:
We are encountering issues, that when enabling some Dell laptops, the readings
from iio-poll-als are unstable, or could freeze on certain value. On these
systems they have ENV{IIO_SENSOR_PROXY_TYPE}="iio-poll-als iio-buffer-als",
and
removing iio-poll-als makes reading stable.
This adds workaround to the affected Dell laptop models which may equip with
ALS.
[Impact]
* Only models matching the same device BIOS IDs are affected.
[Test Plan]
* Pick devices which BIOS IDs are listed in the patch, and test
whether it's ambient light sensors are working properly without
unexpected brightness flickers.
[Where problems could occur]
* Machines matching the same BIOS ID, either having ALS built-in or
not, but attached ambient light sensors externally (for example,
ColorHug ALS) might experience failures.
[Other Info]
* Upstream merge request:
https://gitlab.freedesktop.org/hadess/iio-sensor-proxy/-/merge_requests/352
To manage notifications about this bug go to:
https://bugs.launchpad.net/oem-priority/+bug/1963628/+subscriptions
--
Mailing list: https://launchpad.net/~desktop-packages
Post to : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-packages
More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1967521] Re: Test binaries in libsndfile-dev package
it was added on purpose in Debian it seems to be able to use it for autopkgtest https://salsa.debian.org/multimedia-team/libsndfile/-/commit/ce47c46e but it might make sense to have them split in another binary, you should report that to Debian -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to libsndfile in Ubuntu. https://bugs.launchpad.net/bugs/1967521 Title: Test binaries in libsndfile-dev package Status in libsndfile package in Ubuntu: New Bug description: There are programs from the libsndfile test suite in dev package. Should they be there? To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libsndfile/+bug/1967521/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1966613] Re: Navigating with arrow keys broken for RTL text
** Changed in: pango1.0 (Ubuntu) Status: In Progress => Fix Committed -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to pango1.0 in Ubuntu. https://bugs.launchpad.net/bugs/1966613 Title: Navigating with arrow keys broken for RTL text Status in Pango: Unknown Status in pango1.0 package in Ubuntu: Fix Committed Bug description: RTL text renders fine, and navigating within a line with the arrow keys works as expected. However, using the left and right arrow keys to move to the next or previous lines is broken. To reproduce: 1. Open gnome-text-editor and paste the following into its window: זוהי השורה הראשונה זוהי השורה השנייה זוהי השורה השלישית make sure it is aligned to the right, as it should. 2. place the caret in the middle of the 2nd line. 3. With the arrows, move the caret to the left of the line (its end). 4. Press the left arrow key one more time. Expected results: 1. The caret moves to the right hand side of the next line. Actual results: 1. The caret moves to the left hand side of the previous line. The same issue exists in reverse: if you move the caret with the arrow keys to the right of the line (its beginning) and press the right arrow key one more time, it will move to the right hand side of the next line instead of the left hand side of the previous line, as it should. This make navigation in RTL files highly uncomfortable. ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: gnome-text-editor 42.0-2 ProcVersionSignature: Ubuntu 5.15.0-23.23-generic 5.15.27 Uname: Linux 5.15.0-23-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu79 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Mon Mar 28 03:09:24 2022 InstallationDate: Installed on 2022-01-31 (55 days ago) InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Alpha amd64 (20220126) SourcePackage: gnome-text-editor UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/pango/+bug/1966613/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1967565] Re: upower takes long time to detect laptop AC charger plugged in
Thank you for your bug report, could you report the issue upstream on https://gitlab.freedesktop.org/upower/upower/-/issues ? ** Changed in: upower (Ubuntu) Importance: Undecided => Low -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to upower in Ubuntu. https://bugs.launchpad.net/bugs/1967565 Title: upower takes long time to detect laptop AC charger plugged in Status in upower package in Ubuntu: New Bug description: upower takes a really long time (around 1-2 minutes) to detect when an AC charger is plugged-in. 'upower -d' shows battery state as discharging after AC charger is plugged-in. 'systemctl restart upower.service' would update the status immediately as charging. Otherwise, it takes 1-2 minutes before upower updates the status. Laptop Model: Acer Aspire E15 E5-573G-56JN Laptop battery and AC charger is not faulty as the charging/discharging status gets correctly detected when using Windows 10. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: upower 0.99.11-1build2 ProcVersionSignature: Ubuntu 5.13.0-39.44~20.04.1-generic 5.13.19 Uname: Linux 5.13.0-39-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.21 Architecture: amd64 CasperMD5CheckResult: skip Date: Fri Apr 1 23:07:12 2022 ExecutablePath: /usr/lib/upower/upowerd InstallationDate: Installed on 2022-04-01 (0 days ago) InstallationMedia: Ubuntu 20.04.4 LTS "Focal Fossa" - Release amd64 (20220223) ProcEnviron: LANG=en_IN LANGUAGE=en_IN:en PATH=(custom, no user) SourcePackage: upower UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/upower/+bug/1967565/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1965964] Re: an error has occurred while searching for drivers
*** This bug is a duplicate of bug 1964880 ***
https://bugs.launchpad.net/bugs/1964880
** This bug has been marked a duplicate of bug 1964880
software-properties-gtk crashed with AttributeError in
packages_for_modalias(): 'Cache' object has no attribute 'packages'
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to software-properties in Ubuntu.
https://bugs.launchpad.net/bugs/1965964
Title:
an error has occurred while searching for drivers
Status in software-properties package in Ubuntu:
Confirmed
Bug description:
when going to additional drivers it says an error has occurred while
searching for drivers. I am using Ubuntu 22.04.
software-properties-gtk:
Installed: 0.99.19
/usr/lib/python3/dist-packages/softwareproperties/gtk/SoftwarePropertiesGtk.py:49:
PyGIWarning: Handy was imported without specifying a version first. Use
gi.require_version('Handy', '1') before import to ensure that the right version
gets loaded.
from gi.repository import GObject, Gdk, Gtk, Gio, GLib, Handy
Traceback (most recent call last):
File
"/usr/lib/python3/dist-packages/softwareproperties/gtk/SoftwarePropertiesGtk.py",
line 1380, in detect_drivers
self.devices = detect.system_device_drivers(self.apt_cache)
File "/usr/lib/python3/dist-packages/UbuntuDrivers/detect.py", line 752, in
system_device_drivers
for pkg, pkginfo in system_driver_packages(apt_cache, sys_path,
File "/usr/lib/python3/dist-packages/UbuntuDrivers/detect.py", line 448, in
system_driver_packages
for p in packages_for_modalias(apt_cache, alias):
File "/usr/lib/python3/dist-packages/UbuntuDrivers/detect.py", line 200, in
packages_for_modalias
apt_cache_hash = hash(package.get_fullname() for package in
apt_cache.packages)
AttributeError: 'Cache' object has no attribute 'packages'
ProblemType: Bug
DistroRelease: Ubuntu 22.04
Package: software-properties-gtk 0.99.19
ProcVersionSignature: Ubuntu 5.15.0-23.23-generic 5.15.27
Uname: Linux 5.15.0-23-generic x86_64
NonfreeKernelModules: nvidia_modeset nvidia
ApportVersion: 2.20.11-0ubuntu79
Architecture: amd64
CasperMD5CheckResult: pass
CurrentDesktop: ubuntu:GNOME
Date: Tue Mar 22 15:57:06 2022
InstallationDate: Installed on 2022-03-22 (0 days ago)
InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Alpha amd64 (20220321)
PackageArchitecture: all
ProcEnviron:
LANGUAGE=en_GB:en
PATH=(custom, no user)
XDG_RUNTIME_DIR=
LANG=en_GB.UTF-8
SHELL=/bin/bash
SourcePackage: software-properties
UpgradeStatus: No upgrade log present (probably fresh install)
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/software-properties/+bug/1965964/+subscriptions
--
Mailing list: https://launchpad.net/~desktop-packages
Post to : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-packages
More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1965857] Re: software-properties-gtk crashed with AttributeError in packages_for_modalias(): 'Cache' object has no attribute 'packages'
*** This bug is a duplicate of bug 1964880 *** https://bugs.launchpad.net/bugs/1964880 ** This bug has been marked a duplicate of bug 1964880 software-properties-gtk crashed with AttributeError in packages_for_modalias(): 'Cache' object has no attribute 'packages' -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to software-properties in Ubuntu. https://bugs.launchpad.net/bugs/1965857 Title: software-properties-gtk crashed with AttributeError in packages_for_modalias(): 'Cache' object has no attribute 'packages' Status in software-properties package in Ubuntu: New Bug description: live patch not active ProblemType: Crash DistroRelease: Ubuntu 22.04 Package: software-properties-gtk 0.99.19 ProcVersionSignature: Ubuntu 5.15.0-23.23-generic 5.15.27 Uname: Linux 5.15.0-23-generic x86_64 ApportVersion: 2.20.11-0ubuntu79 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: ubuntu:GNOME Date: Tue Mar 22 10:22:47 2022 ExecutablePath: /usr/bin/software-properties-gtk InstallationDate: Installed on 2020-04-25 (695 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) InterpreterPath: /usr/bin/python3.10 PackageArchitecture: all ProcCmdline: /usr/bin/python3 /usr/bin/software-properties-gtk --open-tab=6 ProcEnviron: LANGUAGE=en_IN:en PATH=(custom, user) XDG_RUNTIME_DIR= LANG=en_IN SHELL=/bin/bash Python3Details: /usr/bin/python3.10, Python 3.10.3, python3-minimal, 3.10.1-0ubuntu2 PythonArgs: ['/usr/bin/software-properties-gtk', '--open-tab=6'] PythonDetails: N/A SourcePackage: software-properties Title: software-properties-gtk crashed with AttributeError in packages_for_modalias(): 'Cache' object has no attribute 'packages' UpgradeStatus: Upgraded to jammy on 2022-02-12 (37 days ago) UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/software-properties/+bug/1965857/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1967175] Re: Righ click on links menu doesn't render 99.0.4844.84
this is possibly duplicate of bug #1961606, sorry if it makes the difference to the reported issue I experience the bug only when right clicking text links. When I right click images or image links or bookmarks etc. it renders the menu as expected Processor + Graphics AMD Ryzen 5 3550H with Radeon Vega Mobile Gfx 05:00.0 VGA compatible controller: Advanced Micro Devices, Inc. [AMD/ATI] Picasso (rev c2) -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to chromium-browser in Ubuntu. https://bugs.launchpad.net/bugs/1967175 Title: Righ click on links menu doesn't render 99.0.4844.84 Status in chromium-browser package in Ubuntu: New Bug description: snap info chromium name: chromium summary: Chromium web browser, open-source version of Chrome publisher: Canonical✓ store-url: https://snapcraft.io/chromium contact: https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bugs?field.tag=snap license: unset description: | An open-source browser project that aims to build a safer, faster, and more stable way for all Internet users to experience the web. commands: - chromium.chromedriver - chromium snap-id: XKEcBqPM06H1Z7zGOdG5fbICuf8NWK5R tracking: latest/stable refresh-date: 3 days ago, at 10:51 EEST channels: latest/stable:99.0.4844.84 2022-03-26 (1945) 141MB - latest/candidate: 99.0.4844.84 2022-03-26 (1945) 141MB - latest/beta: 100.0.4896.46 2022-03-18 (1943) 137MB - latest/edge: 101.0.4951.7 2022-03-28 (1947) 139MB - installed: 99.0.4844.84 (1945) 141MB - lsb_release -rd Description: Ubuntu 20.04.4 LTS Release: 20.04 Right clicking web links with text or link buttons is expected to open a menu. However the right click menu doesn't render. Instead right clicking opens a black background (without any text/shape). Right clicking link with plain image works (https://askubuntu.com/) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/1967175/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1967571] Re: udisksd assert failure: malloc_consolidate(): unaligned fastbin chunk detected
*** This bug is a duplicate of bug 1955758 *** https://bugs.launchpad.net/bugs/1955758 Thank you for taking the time to report this crash and helping to make this software better. This particular crash has already been reported and is a duplicate of bug #1955758, so is being marked as such. Please look at the other bug report to see if there is any missing information that you can provide, or to see if there is a workaround for the bug. Additionally, any further discussion regarding the bug should occur in the other report. Please continue to report any other bugs you may find. ** Attachment removed: "CoreDump.gz" https://bugs.launchpad.net/bugs/1967571/+attachment/5575817/+files/CoreDump.gz ** Attachment removed: "Disassembly.txt" https://bugs.launchpad.net/bugs/1967571/+attachment/5575820/+files/Disassembly.txt ** Attachment removed: "ProcMaps.txt" https://bugs.launchpad.net/bugs/1967571/+attachment/5575831/+files/ProcMaps.txt ** Attachment removed: "ProcStatus.txt" https://bugs.launchpad.net/bugs/1967571/+attachment/5575833/+files/ProcStatus.txt ** Attachment removed: "Registers.txt" https://bugs.launchpad.net/bugs/1967571/+attachment/5575834/+files/Registers.txt ** Attachment removed: "Stacktrace.txt" https://bugs.launchpad.net/bugs/1967571/+attachment/5575835/+files/Stacktrace.txt ** Attachment removed: "ThreadStacktrace.txt" https://bugs.launchpad.net/bugs/1967571/+attachment/5575836/+files/ThreadStacktrace.txt ** This bug has been marked a duplicate of private bug 1955758 ** Information type changed from Private to Public ** Tags removed: need-amd64-retrace -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to udisks2 in Ubuntu. https://bugs.launchpad.net/bugs/1967571 Title: udisksd assert failure: malloc_consolidate(): unaligned fastbin chunk detected Status in udisks2 package in Ubuntu: New Bug description: Occurred after upgrade from 20.04 to Jammy beta (1 April 2022). ProblemType: Crash DistroRelease: Ubuntu 22.04 Package: udisks2 2.9.4-1 ProcVersionSignature: Ubuntu 5.15.0-23.23-generic 5.15.27 Uname: Linux 5.13.0-39-generic x86_64 ApportVersion: 2.20.11-0ubuntu80 Architecture: amd64 AssertionMessage: malloc_consolidate(): unaligned fastbin chunk detected CasperMD5CheckResult: unknown CustomUdevRuleFiles: 70-snap.snapd.rules 70-snap.snap-store.rules 70-snap.firefox.rules 70-snap.chromium.rules Date: Fri Apr 1 19:41:40 2022 ExecutablePath: /usr/libexec/udisks2/udisksd InstallationDate: Installed on 2022-03-28 (4 days ago) InstallationMedia: Ubuntu 20.04.4 LTS "Focal Fossa" - Release amd64 (20220223) MachineType: Framework Laptop ProcCmdline: /usr/libexec/udisks2/udisksd ProcEnviron: LANG=en_GB.UTF-8 LANGUAGE=en_GB:en PATH=(custom, no user) ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.15.0-23-generic root=/dev/mapper/LVMvg-ubuntu ro quiet splash resume=UUID=a3d57aca-0115-477a-b163-07b3364b14a5 resume_offset=2396160 vt.handoff=7 Signal: 6 SourcePackage: udisks2 StacktraceTop: __libc_message (action=action@entry=do_abort, fmt=fmt@entry=0x7ff9833c5b8c "%s\n") at ../sysdeps/posix/libc_fatal.c:155 malloc_printerr (str=str@entry=0x7ff9833c85d8 "malloc_consolidate(): unaligned fastbin chunk detected") at ./malloc/malloc.c:5664 malloc_consolidate (av=av@entry=0x7ff983403c80 ) at ./malloc/malloc.c:4750 _int_free (av=0x7ff983403c80 , p=0x557992635b10, have_lock=) at ./malloc/malloc.c:4674 __GI___libc_free (mem=) at ./malloc/malloc.c:3391 Title: udisksd assert failure: malloc_consolidate(): unaligned fastbin chunk detected UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: N/A dmi.bios.date: 12/14/2021 dmi.bios.release: 3.7 dmi.bios.vendor: INSYDE Corp. dmi.bios.version: 03.07 dmi.board.asset.tag: * dmi.board.name: FRANBMCP0A dmi.board.vendor: Framework dmi.board.version: AA dmi.chassis.asset.tag: FRANBMCPAA144500EE dmi.chassis.type: 10 dmi.chassis.vendor: Framework dmi.chassis.version: AA dmi.modalias: dmi:bvnINSYDECorp.:bvr03.07:bd12/14/2021:br3.7:svnFramework:pnLaptop:pvrAA:rvnFramework:rnFRANBMCP0A:rvrAA:cvnFramework:ct10:cvrAA:skuFRANBMCP0A: dmi.product.family: FRANBMCP dmi.product.name: Laptop dmi.product.sku: FRANBMCP0A dmi.product.version: AA dmi.sys.vendor: Framework separator: To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/udisks2/+bug/1967571/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1967568] Re: gnome-shell crashed with SIGSEGV in meta_window_get_window_type()
*** This bug is a duplicate of bug 1965897 *** https://bugs.launchpad.net/bugs/1965897 Thank you for taking the time to report this crash and helping to make this software better. This particular crash has already been reported and is a duplicate of bug #1965897, so is being marked as such. Please look at the other bug report to see if there is any missing information that you can provide, or to see if there is a workaround for the bug. Additionally, any further discussion regarding the bug should occur in the other report. Please continue to report any other bugs you may find. ** Attachment removed: "CoreDump.gz" https://bugs.launchpad.net/bugs/1967568/+attachment/5575798/+files/CoreDump.gz ** Attachment removed: "Disassembly.txt" https://bugs.launchpad.net/bugs/1967568/+attachment/5575800/+files/Disassembly.txt ** Attachment removed: "ProcMaps.txt" https://bugs.launchpad.net/bugs/1967568/+attachment/5575804/+files/ProcMaps.txt ** Attachment removed: "ProcStatus.txt" https://bugs.launchpad.net/bugs/1967568/+attachment/5575805/+files/ProcStatus.txt ** Attachment removed: "Registers.txt" https://bugs.launchpad.net/bugs/1967568/+attachment/5575806/+files/Registers.txt ** Attachment removed: "Stacktrace.txt" https://bugs.launchpad.net/bugs/1967568/+attachment/5575809/+files/Stacktrace.txt ** Attachment removed: "ThreadStacktrace.txt" https://bugs.launchpad.net/bugs/1967568/+attachment/5575810/+files/ThreadStacktrace.txt ** This bug has been marked a duplicate of bug 1965897 gnome-shell crashed with SIGSEGV in meta_window_get_window_type(window=NULL) from meta_window_actor_queue_destroy() from meta_compositor_real_remove_window() from meta_window_unmanage() from meta_display_unmanage_windows() ** Information type changed from Private to Public ** Tags removed: need-amd64-retrace -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-shell in Ubuntu. https://bugs.launchpad.net/bugs/1967568 Title: gnome-shell crashed with SIGSEGV in meta_window_get_window_type() Status in gnome-shell package in Ubuntu: New Bug description: Press Alt+F2 Press r Press Enter X11 session gnome-shell restart causes this crash ProblemType: Crash DistroRelease: Ubuntu 22.04 Package: gnome-shell 42.0-1ubuntu1 Uname: Linux 5.17.1-xanmod1 x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu80 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Fri Apr 1 23:44:21 2022 DisplayManager: gdm3 ExecutablePath: /usr/bin/gnome-shell InstallationDate: Installed on 2022-04-01 (0 days ago) InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Beta amd64 (20220329.1) ProcCmdline: /usr/bin/gnome-shell ProcEnviron: LANG=en_IN LANGUAGE=en_IN:en PATH=(custom, user) SHELL=/bin/bash XDG_RUNTIME_DIR= RelatedPackageVersions: mutter-common 42.0-1ubuntu1 Signal: 11 SourcePackage: gnome-shell StacktraceTop: meta_window_get_window_type () from /lib/x86_64-linux-gnu/libmutter-10.so.0 ?? () from /lib/x86_64-linux-gnu/libmutter-10.so.0 ?? () from /lib/x86_64-linux-gnu/libmutter-10.so.0 meta_display_close () from /lib/x86_64-linux-gnu/libmutter-10.so.0 shell_global_reexec_self () from /usr/lib/gnome-shell/libgnome-shell.so Title: gnome-shell crashed with SIGSEGV in meta_window_get_window_type() UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip libvirt lpadmin lxd plugdev sambashare sudo separator: To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1967568/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1966127] Re: ubuntu-desktop-minimal pulls gnome-session which is in universe
** Changed in: ubuntu-meta (Ubuntu) Status: New => Invalid ** Changed in: gdm3 (Ubuntu) Status: New => In Progress ** Changed in: gdm3 (Ubuntu) Importance: Undecided => Low -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to ubuntu-meta in Ubuntu. https://bugs.launchpad.net/bugs/1966127 Title: ubuntu-desktop-minimal pulls gnome-session which is in universe Status in gdm3 package in Ubuntu: In Progress Status in ubuntu-meta package in Ubuntu: Invalid Bug description: ubuntu-desktop-minimal is in main but installing it pulls gnome- session from universe. Here is how to reproduce it: 1) Create a Jammy VM: $ lxc launch images:ubuntu/jammy jammy-vm --vm 2) Enter the Jammy VM: $ lxc shell jammy-vm 3) Install ubuntu-desktop-minimal root@jammy-vm:~# apt-get update ... root@jammy-vm:~# apt-get install -V ubuntu-desktop-minimal ... Get:726 http://archive.ubuntu.com/ubuntu jammy/main amd64 libxfont2 amd64 1:2.0.5-1 [94.7 kB] Get:727 http://archive.ubuntu.com/ubuntu jammy/main amd64 xwayland amd64 2:22.1.0-1 [932 kB] Get:728 http://archive.ubuntu.com/ubuntu jammy/universe amd64 gnome-session all 42.0-1ubuntu1 [15.2 kB] Get:729 http://archive.ubuntu.com/ubuntu jammy/main amd64 yaru-theme-gnome-shell all 22.04.2 [66.4 kB] Get:730 http://archive.ubuntu.com/ubuntu jammy/main amd64 ubuntu-session all 42.0-1ubuntu1 [5,418 B] ... 4) Check the policy of packages: root@jammy-vm:~# apt-cache policy ubuntu-desktop-minimal gnome-session ubuntu-desktop-minimal: Installed: 1.478 Candidate: 1.478 Version table: *** 1.478 500 500 http://archive.ubuntu.com/ubuntu jammy/main amd64 Packages 100 /var/lib/dpkg/status gnome-session: Installed: 42.0-1ubuntu1 Candidate: 42.0-1ubuntu1 Version table: *** 42.0-1ubuntu1 500 500 http://archive.ubuntu.com/ubuntu jammy/universe amd64 Packages 100 /var/lib/dpkg/status Both should be from main. Additional information: root@jammy-vm:~# lsb_release -rd Description: Ubuntu Jammy Jellyfish (development branch) Release: 22.04 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gdm3/+bug/1966127/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1966613] Re: Navigating with arrow keys broken for RTL text
** Also affects: gnome-text-editor via https://gitlab.gnome.org/GNOME/gnome-text-editor/-/issues/344 Importance: Unknown Status: Unknown ** Package changed: gnome-text-editor (Ubuntu) => pango1.0 (Ubuntu) ** Changed in: pango1.0 (Ubuntu) Status: New => Triaged ** Project changed: gnome-text-editor => pango ** Changed in: pango1.0 (Ubuntu) Status: Triaged => In Progress ** Changed in: pango1.0 (Ubuntu) Importance: Undecided => High -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to pango1.0 in Ubuntu. https://bugs.launchpad.net/bugs/1966613 Title: Navigating with arrow keys broken for RTL text Status in Pango: Unknown Status in pango1.0 package in Ubuntu: In Progress Bug description: RTL text renders fine, and navigating within a line with the arrow keys works as expected. However, using the left and right arrow keys to move to the next or previous lines is broken. To reproduce: 1. Open gnome-text-editor and paste the following into its window: זוהי השורה הראשונה זוהי השורה השנייה זוהי השורה השלישית make sure it is aligned to the right, as it should. 2. place the caret in the middle of the 2nd line. 3. With the arrows, move the caret to the left of the line (its end). 4. Press the left arrow key one more time. Expected results: 1. The caret moves to the right hand side of the next line. Actual results: 1. The caret moves to the left hand side of the previous line. The same issue exists in reverse: if you move the caret with the arrow keys to the right of the line (its beginning) and press the right arrow key one more time, it will move to the right hand side of the next line instead of the left hand side of the previous line, as it should. This make navigation in RTL files highly uncomfortable. ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: gnome-text-editor 42.0-2 ProcVersionSignature: Ubuntu 5.15.0-23.23-generic 5.15.27 Uname: Linux 5.15.0-23-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu79 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Mon Mar 28 03:09:24 2022 InstallationDate: Installed on 2022-01-31 (55 days ago) InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Alpha amd64 (20220126) SourcePackage: gnome-text-editor UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/pango/+bug/1966613/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1967155] Re: Update gnome-online-accounts to 3.44
** Changed in: gnome-online-accounts (Ubuntu) Status: In Progress => Fix Committed -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-online-accounts in Ubuntu. https://bugs.launchpad.net/bugs/1967155 Title: Update gnome-online-accounts to 3.44 Status in gnome-online-accounts package in Ubuntu: Fix Committed Bug description: Minimal tracking bug if needed. https://gitlab.gnome.org/GNOME/gnome-online- accounts/-/blob/master/NEWS https://gitlab.gnome.org/GNOME/gnome-online- accounts/-/compare/3.43.1...master?from_project_id=1666 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-online-accounts/+bug/1967155/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1966613] [NEW] Navigating with arrow keys broken for RTL text
You have been subscribed to a public bug: RTL text renders fine, and navigating within a line with the arrow keys works as expected. However, using the left and right arrow keys to move to the next or previous lines is broken. To reproduce: 1. Open gnome-text-editor and paste the following into its window: זוהי השורה הראשונה זוהי השורה השנייה זוהי השורה השלישית make sure it is aligned to the right, as it should. 2. place the caret in the middle of the 2nd line. 3. With the arrows, move the caret to the left of the line (its end). 4. Press the left arrow key one more time. Expected results: 1. The caret moves to the right hand side of the next line. Actual results: 1. The caret moves to the left hand side of the previous line. The same issue exists in reverse: if you move the caret with the arrow keys to the right of the line (its beginning) and press the right arrow key one more time, it will move to the right hand side of the next line instead of the left hand side of the previous line, as it should. This make navigation in RTL files highly uncomfortable. ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: gnome-text-editor 42.0-2 ProcVersionSignature: Ubuntu 5.15.0-23.23-generic 5.15.27 Uname: Linux 5.15.0-23-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu79 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Mon Mar 28 03:09:24 2022 InstallationDate: Installed on 2022-01-31 (55 days ago) InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Alpha amd64 (20220126) SourcePackage: gnome-text-editor UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: gnome-text-editor Importance: Unknown Status: Unknown ** Affects: pango1.0 (Ubuntu) Importance: Undecided Status: Triaged ** Tags: amd64 apport-bug jammy rtl -- Navigating with arrow keys broken for RTL text https://bugs.launchpad.net/bugs/1966613 You received this bug notification because you are a member of Desktop Packages, which is subscribed to pango1.0 in Ubuntu. -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1965696] ProcCpuinfoMinimal.txt
apport information ** Attachment added: "ProcCpuinfoMinimal.txt" https://bugs.launchpad.net/bugs/1965696/+attachment/5575787/+files/ProcCpuinfoMinimal.txt -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-shell in Ubuntu. https://bugs.launchpad.net/bugs/1965696 Title: Shell keyboard navigation (after pressing Ctrl+Alt+Tab) doesn't work in Xorg sessions Status in GNOME Shell: Unknown Status in gnome-shell package in Ubuntu: Confirmed Bug description: As of 2 days ago, I can no longer quickly get to system controls such as the Top Bar using the keyboard. According to the keyboard shortcuts settings window, I should be able to press "CTRL+Alt+Tab" to access these controls. When I press this key combination, I'm told by the Orca screen reader that I'm on the Top Bar. When I release the keys, focus jumps back to the window I was in before. I do not know if this is the case without Orca running. I'm unable to test without Orca running. I've reset Gnome settings, with no change. ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: gnome-shell 42~beta-1ubuntu3 Uname: Linux 5.16.11-76051611-generic x86_64 ApportVersion: 2.20.11-0ubuntu79 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: ubuntu:GNOME Date: Sun Mar 20 13:01:07 2022 DisplayManager: gdm3 InstallationDate: Installed on 2018-04-30 (1420 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180425.1) ProcEnviron: TERM=screen PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash RelatedPackageVersions: mutter-common 42~beta-1ubuntu2 SourcePackage: gnome-shell UpgradeStatus: No upgrade log present (probably fresh install) --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu80 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: ubuntu:GNOME DisplayManager: gdm3 DistroRelease: Ubuntu 22.04 InstallationDate: Installed on 2018-04-30 (1432 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180425.1) Package: gnome-shell 42.0-1ubuntu1 PackageArchitecture: amd64 ProcEnviron: TERM=screen PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash RelatedPackageVersions: mutter-common 42.0-1ubuntu1 Tags: third-party-packages jammy Uname: Linux 5.16.11-76051611-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm audio cdrom dialout dip input lpadmin plugdev sambashare sudo vboxusers wireshark _MarkForUpload: True --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu80 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: ubuntu:GNOME DisplayManager: gdm3 DistroRelease: Ubuntu 22.04 InstallationDate: Installed on 2018-04-30 (1432 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180425.1) Package: gnome-shell 42.0-1ubuntu1 PackageArchitecture: amd64 ProcEnviron: TERM=screen PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash RelatedPackageVersions: mutter-common 42.0-1ubuntu1 Tags: third-party-packages jammy Uname: Linux 5.16.11-76051611-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm audio cdrom dialout dip input lpadmin plugdev sambashare sudo vboxusers wireshark _MarkForUpload: True To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-shell/+bug/1965696/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1965696] ShellJournal.txt
apport information ** Attachment added: "ShellJournal.txt" https://bugs.launchpad.net/bugs/1965696/+attachment/5575788/+files/ShellJournal.txt -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-shell in Ubuntu. https://bugs.launchpad.net/bugs/1965696 Title: Shell keyboard navigation (after pressing Ctrl+Alt+Tab) doesn't work in Xorg sessions Status in GNOME Shell: Unknown Status in gnome-shell package in Ubuntu: Confirmed Bug description: As of 2 days ago, I can no longer quickly get to system controls such as the Top Bar using the keyboard. According to the keyboard shortcuts settings window, I should be able to press "CTRL+Alt+Tab" to access these controls. When I press this key combination, I'm told by the Orca screen reader that I'm on the Top Bar. When I release the keys, focus jumps back to the window I was in before. I do not know if this is the case without Orca running. I'm unable to test without Orca running. I've reset Gnome settings, with no change. ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: gnome-shell 42~beta-1ubuntu3 Uname: Linux 5.16.11-76051611-generic x86_64 ApportVersion: 2.20.11-0ubuntu79 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: ubuntu:GNOME Date: Sun Mar 20 13:01:07 2022 DisplayManager: gdm3 InstallationDate: Installed on 2018-04-30 (1420 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180425.1) ProcEnviron: TERM=screen PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash RelatedPackageVersions: mutter-common 42~beta-1ubuntu2 SourcePackage: gnome-shell UpgradeStatus: No upgrade log present (probably fresh install) --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu80 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: ubuntu:GNOME DisplayManager: gdm3 DistroRelease: Ubuntu 22.04 InstallationDate: Installed on 2018-04-30 (1432 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180425.1) Package: gnome-shell 42.0-1ubuntu1 PackageArchitecture: amd64 ProcEnviron: TERM=screen PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash RelatedPackageVersions: mutter-common 42.0-1ubuntu1 Tags: third-party-packages jammy Uname: Linux 5.16.11-76051611-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm audio cdrom dialout dip input lpadmin plugdev sambashare sudo vboxusers wireshark _MarkForUpload: True --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu80 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: ubuntu:GNOME DisplayManager: gdm3 DistroRelease: Ubuntu 22.04 InstallationDate: Installed on 2018-04-30 (1432 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180425.1) Package: gnome-shell 42.0-1ubuntu1 PackageArchitecture: amd64 ProcEnviron: TERM=screen PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash RelatedPackageVersions: mutter-common 42.0-1ubuntu1 Tags: third-party-packages jammy Uname: Linux 5.16.11-76051611-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm audio cdrom dialout dip input lpadmin plugdev sambashare sudo vboxusers wireshark _MarkForUpload: True To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-shell/+bug/1965696/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1965696] ShellJournal.txt
apport information ** Attachment added: "ShellJournal.txt" https://bugs.launchpad.net/bugs/1965696/+attachment/5575784/+files/ShellJournal.txt ** Description changed: As of 2 days ago, I can no longer quickly get to system controls such as the Top Bar using the keyboard. According to the keyboard shortcuts settings window, I should be able to press "CTRL+Alt+Tab" to access these controls. When I press this key combination, I'm told by the Orca screen reader that I'm on the Top Bar. When I release the keys, focus jumps back to the window I was in before. I do not know if this is the case without Orca running. I'm unable to test without Orca running. I've reset Gnome settings, with no change. ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: gnome-shell 42~beta-1ubuntu3 Uname: Linux 5.16.11-76051611-generic x86_64 ApportVersion: 2.20.11-0ubuntu79 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: ubuntu:GNOME Date: Sun Mar 20 13:01:07 2022 DisplayManager: gdm3 InstallationDate: Installed on 2018-04-30 (1420 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180425.1) ProcEnviron: TERM=screen PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash RelatedPackageVersions: mutter-common 42~beta-1ubuntu2 SourcePackage: gnome-shell UpgradeStatus: No upgrade log present (probably fresh install) --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu80 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: ubuntu:GNOME DisplayManager: gdm3 DistroRelease: Ubuntu 22.04 InstallationDate: Installed on 2018-04-30 (1432 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180425.1) Package: gnome-shell 42.0-1ubuntu1 PackageArchitecture: amd64 ProcEnviron: TERM=screen PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash RelatedPackageVersions: mutter-common 42.0-1ubuntu1 Tags: third-party-packages jammy Uname: Linux 5.16.11-76051611-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm audio cdrom dialout dip input lpadmin plugdev sambashare sudo vboxusers wireshark _MarkForUpload: True + --- + ProblemType: Bug + ApportVersion: 2.20.11-0ubuntu80 + Architecture: amd64 + CasperMD5CheckResult: unknown + CurrentDesktop: ubuntu:GNOME + DisplayManager: gdm3 + DistroRelease: Ubuntu 22.04 + InstallationDate: Installed on 2018-04-30 (1432 days ago) + InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180425.1) + Package: gnome-shell 42.0-1ubuntu1 + PackageArchitecture: amd64 + ProcEnviron: + TERM=screen + PATH=(custom, no user) + XDG_RUNTIME_DIR= + LANG=en_US.UTF-8 + SHELL=/bin/bash + RelatedPackageVersions: mutter-common 42.0-1ubuntu1 + Tags: third-party-packages jammy + Uname: Linux 5.16.11-76051611-generic x86_64 + UpgradeStatus: No upgrade log present (probably fresh install) + UserGroups: adm audio cdrom dialout dip input lpadmin plugdev sambashare sudo vboxusers wireshark + _MarkForUpload: True -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-shell in Ubuntu. https://bugs.launchpad.net/bugs/1965696 Title: Shell keyboard navigation (after pressing Ctrl+Alt+Tab) doesn't work in Xorg sessions Status in GNOME Shell: Unknown Status in gnome-shell package in Ubuntu: Confirmed Bug description: As of 2 days ago, I can no longer quickly get to system controls such as the Top Bar using the keyboard. According to the keyboard shortcuts settings window, I should be able to press "CTRL+Alt+Tab" to access these controls. When I press this key combination, I'm told by the Orca screen reader that I'm on the Top Bar. When I release the keys, focus jumps back to the window I was in before. I do not know if this is the case without Orca running. I'm unable to test without Orca running. I've reset Gnome settings, with no change. ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: gnome-shell 42~beta-1ubuntu3 Uname: Linux 5.16.11-76051611-generic x86_64 ApportVersion: 2.20.11-0ubuntu79 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: ubuntu:GNOME Date: Sun Mar 20 13:01:07 2022 DisplayManager: gdm3 InstallationDate: Installed on 2018-04-30 (1420 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180425.1) ProcEnviron: TERM=screen PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash RelatedPackageVersions: mutter-common 42~beta-1ubuntu2 SourcePackage: gnome-shell UpgradeStatus: No upgrade log present (probably fresh install) --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu80 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: ubuntu:GNOME DisplayManager: gdm3 DistroRelease: Ubuntu 22.04
[Desktop-packages] [Bug 1965696] GsettingsChanges.txt
apport information ** Attachment added: "GsettingsChanges.txt" https://bugs.launchpad.net/bugs/1965696/+attachment/5575786/+files/GsettingsChanges.txt -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-shell in Ubuntu. https://bugs.launchpad.net/bugs/1965696 Title: Shell keyboard navigation (after pressing Ctrl+Alt+Tab) doesn't work in Xorg sessions Status in GNOME Shell: Unknown Status in gnome-shell package in Ubuntu: Confirmed Bug description: As of 2 days ago, I can no longer quickly get to system controls such as the Top Bar using the keyboard. According to the keyboard shortcuts settings window, I should be able to press "CTRL+Alt+Tab" to access these controls. When I press this key combination, I'm told by the Orca screen reader that I'm on the Top Bar. When I release the keys, focus jumps back to the window I was in before. I do not know if this is the case without Orca running. I'm unable to test without Orca running. I've reset Gnome settings, with no change. ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: gnome-shell 42~beta-1ubuntu3 Uname: Linux 5.16.11-76051611-generic x86_64 ApportVersion: 2.20.11-0ubuntu79 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: ubuntu:GNOME Date: Sun Mar 20 13:01:07 2022 DisplayManager: gdm3 InstallationDate: Installed on 2018-04-30 (1420 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180425.1) ProcEnviron: TERM=screen PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash RelatedPackageVersions: mutter-common 42~beta-1ubuntu2 SourcePackage: gnome-shell UpgradeStatus: No upgrade log present (probably fresh install) --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu80 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: ubuntu:GNOME DisplayManager: gdm3 DistroRelease: Ubuntu 22.04 InstallationDate: Installed on 2018-04-30 (1432 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180425.1) Package: gnome-shell 42.0-1ubuntu1 PackageArchitecture: amd64 ProcEnviron: TERM=screen PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash RelatedPackageVersions: mutter-common 42.0-1ubuntu1 Tags: third-party-packages jammy Uname: Linux 5.16.11-76051611-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm audio cdrom dialout dip input lpadmin plugdev sambashare sudo vboxusers wireshark _MarkForUpload: True --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu80 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: ubuntu:GNOME DisplayManager: gdm3 DistroRelease: Ubuntu 22.04 InstallationDate: Installed on 2018-04-30 (1432 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180425.1) Package: gnome-shell 42.0-1ubuntu1 PackageArchitecture: amd64 ProcEnviron: TERM=screen PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash RelatedPackageVersions: mutter-common 42.0-1ubuntu1 Tags: third-party-packages jammy Uname: Linux 5.16.11-76051611-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm audio cdrom dialout dip input lpadmin plugdev sambashare sudo vboxusers wireshark _MarkForUpload: True To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-shell/+bug/1965696/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1965696] Dependencies.txt
apport information ** Attachment added: "Dependencies.txt" https://bugs.launchpad.net/bugs/1965696/+attachment/5575785/+files/Dependencies.txt -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-shell in Ubuntu. https://bugs.launchpad.net/bugs/1965696 Title: Shell keyboard navigation (after pressing Ctrl+Alt+Tab) doesn't work in Xorg sessions Status in GNOME Shell: Unknown Status in gnome-shell package in Ubuntu: Confirmed Bug description: As of 2 days ago, I can no longer quickly get to system controls such as the Top Bar using the keyboard. According to the keyboard shortcuts settings window, I should be able to press "CTRL+Alt+Tab" to access these controls. When I press this key combination, I'm told by the Orca screen reader that I'm on the Top Bar. When I release the keys, focus jumps back to the window I was in before. I do not know if this is the case without Orca running. I'm unable to test without Orca running. I've reset Gnome settings, with no change. ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: gnome-shell 42~beta-1ubuntu3 Uname: Linux 5.16.11-76051611-generic x86_64 ApportVersion: 2.20.11-0ubuntu79 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: ubuntu:GNOME Date: Sun Mar 20 13:01:07 2022 DisplayManager: gdm3 InstallationDate: Installed on 2018-04-30 (1420 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180425.1) ProcEnviron: TERM=screen PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash RelatedPackageVersions: mutter-common 42~beta-1ubuntu2 SourcePackage: gnome-shell UpgradeStatus: No upgrade log present (probably fresh install) --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu80 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: ubuntu:GNOME DisplayManager: gdm3 DistroRelease: Ubuntu 22.04 InstallationDate: Installed on 2018-04-30 (1432 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180425.1) Package: gnome-shell 42.0-1ubuntu1 PackageArchitecture: amd64 ProcEnviron: TERM=screen PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash RelatedPackageVersions: mutter-common 42.0-1ubuntu1 Tags: third-party-packages jammy Uname: Linux 5.16.11-76051611-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm audio cdrom dialout dip input lpadmin plugdev sambashare sudo vboxusers wireshark _MarkForUpload: True --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu80 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: ubuntu:GNOME DisplayManager: gdm3 DistroRelease: Ubuntu 22.04 InstallationDate: Installed on 2018-04-30 (1432 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180425.1) Package: gnome-shell 42.0-1ubuntu1 PackageArchitecture: amd64 ProcEnviron: TERM=screen PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash RelatedPackageVersions: mutter-common 42.0-1ubuntu1 Tags: third-party-packages jammy Uname: Linux 5.16.11-76051611-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm audio cdrom dialout dip input lpadmin plugdev sambashare sudo vboxusers wireshark _MarkForUpload: True To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-shell/+bug/1965696/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1965696] ProcCpuinfoMinimal.txt
apport information ** Attachment added: "ProcCpuinfoMinimal.txt" https://bugs.launchpad.net/bugs/1965696/+attachment/5575783/+files/ProcCpuinfoMinimal.txt -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-shell in Ubuntu. https://bugs.launchpad.net/bugs/1965696 Title: Shell keyboard navigation (after pressing Ctrl+Alt+Tab) doesn't work in Xorg sessions Status in GNOME Shell: Unknown Status in gnome-shell package in Ubuntu: Confirmed Bug description: As of 2 days ago, I can no longer quickly get to system controls such as the Top Bar using the keyboard. According to the keyboard shortcuts settings window, I should be able to press "CTRL+Alt+Tab" to access these controls. When I press this key combination, I'm told by the Orca screen reader that I'm on the Top Bar. When I release the keys, focus jumps back to the window I was in before. I do not know if this is the case without Orca running. I'm unable to test without Orca running. I've reset Gnome settings, with no change. ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: gnome-shell 42~beta-1ubuntu3 Uname: Linux 5.16.11-76051611-generic x86_64 ApportVersion: 2.20.11-0ubuntu79 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: ubuntu:GNOME Date: Sun Mar 20 13:01:07 2022 DisplayManager: gdm3 InstallationDate: Installed on 2018-04-30 (1420 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180425.1) ProcEnviron: TERM=screen PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash RelatedPackageVersions: mutter-common 42~beta-1ubuntu2 SourcePackage: gnome-shell UpgradeStatus: No upgrade log present (probably fresh install) --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu80 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: ubuntu:GNOME DisplayManager: gdm3 DistroRelease: Ubuntu 22.04 InstallationDate: Installed on 2018-04-30 (1432 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180425.1) Package: gnome-shell 42.0-1ubuntu1 PackageArchitecture: amd64 ProcEnviron: TERM=screen PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash RelatedPackageVersions: mutter-common 42.0-1ubuntu1 Tags: third-party-packages jammy Uname: Linux 5.16.11-76051611-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm audio cdrom dialout dip input lpadmin plugdev sambashare sudo vboxusers wireshark _MarkForUpload: True --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu80 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: ubuntu:GNOME DisplayManager: gdm3 DistroRelease: Ubuntu 22.04 InstallationDate: Installed on 2018-04-30 (1432 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180425.1) Package: gnome-shell 42.0-1ubuntu1 PackageArchitecture: amd64 ProcEnviron: TERM=screen PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash RelatedPackageVersions: mutter-common 42.0-1ubuntu1 Tags: third-party-packages jammy Uname: Linux 5.16.11-76051611-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm audio cdrom dialout dip input lpadmin plugdev sambashare sudo vboxusers wireshark _MarkForUpload: True To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-shell/+bug/1965696/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1965696] Re: Shell keyboard navigation (after pressing Ctrl+Alt+Tab) doesn't work in Xorg sessions
apport information ** Tags added: apport-collected ** Description changed: As of 2 days ago, I can no longer quickly get to system controls such as the Top Bar using the keyboard. According to the keyboard shortcuts settings window, I should be able to press "CTRL+Alt+Tab" to access these controls. When I press this key combination, I'm told by the Orca screen reader that I'm on the Top Bar. When I release the keys, focus jumps back to the window I was in before. I do not know if this is the case without Orca running. I'm unable to test without Orca running. I've reset Gnome settings, with no change. ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: gnome-shell 42~beta-1ubuntu3 Uname: Linux 5.16.11-76051611-generic x86_64 ApportVersion: 2.20.11-0ubuntu79 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: ubuntu:GNOME Date: Sun Mar 20 13:01:07 2022 DisplayManager: gdm3 InstallationDate: Installed on 2018-04-30 (1420 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180425.1) ProcEnviron: TERM=screen PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash RelatedPackageVersions: mutter-common 42~beta-1ubuntu2 SourcePackage: gnome-shell UpgradeStatus: No upgrade log present (probably fresh install) + --- + ProblemType: Bug + ApportVersion: 2.20.11-0ubuntu80 + Architecture: amd64 + CasperMD5CheckResult: unknown + CurrentDesktop: ubuntu:GNOME + DisplayManager: gdm3 + DistroRelease: Ubuntu 22.04 + InstallationDate: Installed on 2018-04-30 (1432 days ago) + InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180425.1) + Package: gnome-shell 42.0-1ubuntu1 + PackageArchitecture: amd64 + ProcEnviron: + TERM=screen + PATH=(custom, no user) + XDG_RUNTIME_DIR= + LANG=en_US.UTF-8 + SHELL=/bin/bash + RelatedPackageVersions: mutter-common 42.0-1ubuntu1 + Tags: third-party-packages jammy + Uname: Linux 5.16.11-76051611-generic x86_64 + UpgradeStatus: No upgrade log present (probably fresh install) + UserGroups: adm audio cdrom dialout dip input lpadmin plugdev sambashare sudo vboxusers wireshark + _MarkForUpload: True ** Attachment added: "Dependencies.txt" https://bugs.launchpad.net/bugs/1965696/+attachment/5575781/+files/Dependencies.txt -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-shell in Ubuntu. https://bugs.launchpad.net/bugs/1965696 Title: Shell keyboard navigation (after pressing Ctrl+Alt+Tab) doesn't work in Xorg sessions Status in GNOME Shell: Unknown Status in gnome-shell package in Ubuntu: Confirmed Bug description: As of 2 days ago, I can no longer quickly get to system controls such as the Top Bar using the keyboard. According to the keyboard shortcuts settings window, I should be able to press "CTRL+Alt+Tab" to access these controls. When I press this key combination, I'm told by the Orca screen reader that I'm on the Top Bar. When I release the keys, focus jumps back to the window I was in before. I do not know if this is the case without Orca running. I'm unable to test without Orca running. I've reset Gnome settings, with no change. ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: gnome-shell 42~beta-1ubuntu3 Uname: Linux 5.16.11-76051611-generic x86_64 ApportVersion: 2.20.11-0ubuntu79 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: ubuntu:GNOME Date: Sun Mar 20 13:01:07 2022 DisplayManager: gdm3 InstallationDate: Installed on 2018-04-30 (1420 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180425.1) ProcEnviron: TERM=screen PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash RelatedPackageVersions: mutter-common 42~beta-1ubuntu2 SourcePackage: gnome-shell UpgradeStatus: No upgrade log present (probably fresh install) --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu80 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: ubuntu:GNOME DisplayManager: gdm3 DistroRelease: Ubuntu 22.04 InstallationDate: Installed on 2018-04-30 (1432 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180425.1) Package: gnome-shell 42.0-1ubuntu1 PackageArchitecture: amd64 ProcEnviron: TERM=screen PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash RelatedPackageVersions: mutter-common 42.0-1ubuntu1 Tags: third-party-packages jammy Uname: Linux 5.16.11-76051611-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm audio cdrom dialout dip input lpadmin plugdev sambashare sudo vboxusers wireshark _MarkForUpload: True --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu80 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: ubuntu:GNOME DisplayManager: gdm3
[Desktop-packages] [Bug 1965696] GsettingsChanges.txt
apport information ** Attachment added: "GsettingsChanges.txt" https://bugs.launchpad.net/bugs/1965696/+attachment/5575782/+files/GsettingsChanges.txt -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-shell in Ubuntu. https://bugs.launchpad.net/bugs/1965696 Title: Shell keyboard navigation (after pressing Ctrl+Alt+Tab) doesn't work in Xorg sessions Status in GNOME Shell: Unknown Status in gnome-shell package in Ubuntu: Confirmed Bug description: As of 2 days ago, I can no longer quickly get to system controls such as the Top Bar using the keyboard. According to the keyboard shortcuts settings window, I should be able to press "CTRL+Alt+Tab" to access these controls. When I press this key combination, I'm told by the Orca screen reader that I'm on the Top Bar. When I release the keys, focus jumps back to the window I was in before. I do not know if this is the case without Orca running. I'm unable to test without Orca running. I've reset Gnome settings, with no change. ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: gnome-shell 42~beta-1ubuntu3 Uname: Linux 5.16.11-76051611-generic x86_64 ApportVersion: 2.20.11-0ubuntu79 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: ubuntu:GNOME Date: Sun Mar 20 13:01:07 2022 DisplayManager: gdm3 InstallationDate: Installed on 2018-04-30 (1420 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180425.1) ProcEnviron: TERM=screen PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash RelatedPackageVersions: mutter-common 42~beta-1ubuntu2 SourcePackage: gnome-shell UpgradeStatus: No upgrade log present (probably fresh install) --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu80 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: ubuntu:GNOME DisplayManager: gdm3 DistroRelease: Ubuntu 22.04 InstallationDate: Installed on 2018-04-30 (1432 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180425.1) Package: gnome-shell 42.0-1ubuntu1 PackageArchitecture: amd64 ProcEnviron: TERM=screen PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash RelatedPackageVersions: mutter-common 42.0-1ubuntu1 Tags: third-party-packages jammy Uname: Linux 5.16.11-76051611-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm audio cdrom dialout dip input lpadmin plugdev sambashare sudo vboxusers wireshark _MarkForUpload: True --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu80 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: ubuntu:GNOME DisplayManager: gdm3 DistroRelease: Ubuntu 22.04 InstallationDate: Installed on 2018-04-30 (1432 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180425.1) Package: gnome-shell 42.0-1ubuntu1 PackageArchitecture: amd64 ProcEnviron: TERM=screen PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash RelatedPackageVersions: mutter-common 42.0-1ubuntu1 Tags: third-party-packages jammy Uname: Linux 5.16.11-76051611-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm audio cdrom dialout dip input lpadmin plugdev sambashare sudo vboxusers wireshark _MarkForUpload: True To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-shell/+bug/1965696/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1966786] Re: login screen shown twice with VirtualBox Guest Additions
To be clear in my opinion it is not a problem of Virtualbox, since I run over 15 modern Linux distros in Virtualbox VMs and none has the same issue. That is true for Fedora 35 and 36 Beta also with Gnome 42. No problems with Ubuntu 20.04, Xubuntu 22.04; Ubuntu Budgie 22.04, Ubuntu Mate 22.04, Peppermint 11; Linux Mint 20.3 etc etc. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-shell in Ubuntu. https://bugs.launchpad.net/bugs/1966786 Title: login screen shown twice with VirtualBox Guest Additions Status in gdm3 package in Ubuntu: Confirmed Status in gnome-shell package in Ubuntu: Confirmed Bug description: The login screen is shown twice and I have to supply the password twice. The system works normally afterwards. When I select auto-login in the settings still one login screen is shown. gdm.service - GNOME Display Manager Loaded: loaded (/lib/systemd/system/gdm.service; static) Active: active (running) since Mon 2022-03-28 11:47:32 AST; 6min ago Process: 1885 ExecStartPre=/usr/share/gdm/generate-config (code=exited, status=0/SUCCESS) Main PID: 1915 (gdm3) Tasks: 3 (limit: 2291) Memory: 5.0M CPU: 125ms CGroup: /system.slice/gdm.service └─1915 /usr/sbin/gdm3 mar 28 11:47:32 vm-ubuntu-2204 systemd[1]: Starting GNOME Display Manager... mar 28 11:47:32 vm-ubuntu-2204 systemd[1]: Started GNOME Display Manager. mar 28 11:47:32 vm-ubuntu-2204 gdm-launch-environment][1921]: pam_unix(gdm-launch-environment:session): session opened for user gdm(uid=125) by (uid=0) mar 28 11:47:40 vm-ubuntu-2204 gdm-password][2290]: gkr-pam: unable to locate daemon control file mar 28 11:47:40 vm-ubuntu-2204 gdm-password][2290]: gkr-pam: stashed password to try later in open session mar 28 11:47:40 vm-ubuntu-2204 gdm-password][2290]: pam_unix(gdm-password:session): session opened for user bertadmin(uid=1000) by (uid=0) mar 28 11:47:40 vm-ubuntu-2204 gdm-password][2290]: gkr-pam: gnome-keyring-daemon started properly and unlocked keyring mar 28 11:47:57 vm-ubuntu-2204 gdm3[1915]: Gdm: Child process -1937 was already dead. ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: gdm3 42.0-1ubuntu1 ProcVersionSignature: Ubuntu 5.15.0-23.23-generic 5.15.27 Uname: Linux 5.15.0-23-generic x86_64 ApportVersion: 2.20.11-0ubuntu79 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: ubuntu:GNOME Date: Mon Mar 28 11:48:17 2022 InstallationDate: Installed on 2020-01-25 (793 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Alpha amd64 (20200124) SourcePackage: gdm3 UpgradeStatus: Upgraded to jammy on 2022-03-23 (4 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gdm3/+bug/1966786/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1967565] [NEW] upower takes long time to detect laptop AC charger plugged in
Public bug reported: upower takes a really long time (around 1-2 minutes) to detect when an AC charger is plugged-in. 'upower -d' shows battery state as discharging after AC charger is plugged-in. 'systemctl restart upower.service' would update the status immediately as charging. Otherwise, it takes 1-2 minutes before upower updates the status. Laptop Model: Acer Aspire E15 E5-573G-56JN Laptop battery and AC charger is not faulty as the charging/discharging status gets correctly detected when using Windows 10. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: upower 0.99.11-1build2 ProcVersionSignature: Ubuntu 5.13.0-39.44~20.04.1-generic 5.13.19 Uname: Linux 5.13.0-39-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.21 Architecture: amd64 CasperMD5CheckResult: skip Date: Fri Apr 1 23:07:12 2022 ExecutablePath: /usr/lib/upower/upowerd InstallationDate: Installed on 2022-04-01 (0 days ago) InstallationMedia: Ubuntu 20.04.4 LTS "Focal Fossa" - Release amd64 (20220223) ProcEnviron: LANG=en_IN LANGUAGE=en_IN:en PATH=(custom, no user) SourcePackage: upower UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: upower (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug focal upower ** Attachment added: "upower_incorrect_discharging.txt" https://bugs.launchpad.net/bugs/1967565/+attachment/5575774/+files/upower_incorrect_discharging.txt ** Description changed: - upower takes a really long time (around 1-2 minutes) to detect when an AC charger is plugged-in. + upower takes a really long time (around 1-2 minutes) to detect when an AC charger is plugged-in. 'upower -d' shows battery state as discharging after AC charger is plugged-in. 'systemctl restart upower.service' would update the status immediately as charging. Otherwise, it takes 1-2 minutes before upower updates the status. - Distro: Ubuntu 20.04.4 Laptop Model: Acer Aspire E15 E5-573G-56JN Laptop battery and AC charger is not faulty as the charging/discharging status gets correctly detected when using Windows 10. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: upower 0.99.11-1build2 ProcVersionSignature: Ubuntu 5.13.0-39.44~20.04.1-generic 5.13.19 Uname: Linux 5.13.0-39-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.21 Architecture: amd64 CasperMD5CheckResult: skip Date: Fri Apr 1 23:07:12 2022 ExecutablePath: /usr/lib/upower/upowerd InstallationDate: Installed on 2022-04-01 (0 days ago) InstallationMedia: Ubuntu 20.04.4 LTS "Focal Fossa" - Release amd64 (20220223) ProcEnviron: - LANG=en_IN - LANGUAGE=en_IN:en - PATH=(custom, no user) + LANG=en_IN + LANGUAGE=en_IN:en + PATH=(custom, no user) SourcePackage: upower UpgradeStatus: No upgrade log present (probably fresh install) -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to upower in Ubuntu. https://bugs.launchpad.net/bugs/1967565 Title: upower takes long time to detect laptop AC charger plugged in Status in upower package in Ubuntu: New Bug description: upower takes a really long time (around 1-2 minutes) to detect when an AC charger is plugged-in. 'upower -d' shows battery state as discharging after AC charger is plugged-in. 'systemctl restart upower.service' would update the status immediately as charging. Otherwise, it takes 1-2 minutes before upower updates the status. Laptop Model: Acer Aspire E15 E5-573G-56JN Laptop battery and AC charger is not faulty as the charging/discharging status gets correctly detected when using Windows 10. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: upower 0.99.11-1build2 ProcVersionSignature: Ubuntu 5.13.0-39.44~20.04.1-generic 5.13.19 Uname: Linux 5.13.0-39-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.21 Architecture: amd64 CasperMD5CheckResult: skip Date: Fri Apr 1 23:07:12 2022 ExecutablePath: /usr/lib/upower/upowerd InstallationDate: Installed on 2022-04-01 (0 days ago) InstallationMedia: Ubuntu 20.04.4 LTS "Focal Fossa" - Release amd64 (20220223) ProcEnviron: LANG=en_IN LANGUAGE=en_IN:en PATH=(custom, no user) SourcePackage: upower UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/upower/+bug/1967565/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1967557] Re: udisksd assert failure: malloc_consolidate(): unaligned fastbin chunk detected
*** This bug is a duplicate of bug 1955758 *** https://bugs.launchpad.net/bugs/1955758 Thank you for taking the time to report this crash and helping to make this software better. This particular crash has already been reported and is a duplicate of bug #1955758, so is being marked as such. Please look at the other bug report to see if there is any missing information that you can provide, or to see if there is a workaround for the bug. Additionally, any further discussion regarding the bug should occur in the other report. Please continue to report any other bugs you may find. ** Attachment removed: "CoreDump.gz" https://bugs.launchpad.net/bugs/1967557/+attachment/5575744/+files/CoreDump.gz ** Attachment removed: "Disassembly.txt" https://bugs.launchpad.net/bugs/1967557/+attachment/5575747/+files/Disassembly.txt ** Attachment removed: "ProcMaps.txt" https://bugs.launchpad.net/bugs/1967557/+attachment/5575758/+files/ProcMaps.txt ** Attachment removed: "ProcStatus.txt" https://bugs.launchpad.net/bugs/1967557/+attachment/5575760/+files/ProcStatus.txt ** Attachment removed: "Registers.txt" https://bugs.launchpad.net/bugs/1967557/+attachment/5575761/+files/Registers.txt ** Attachment removed: "Stacktrace.txt" https://bugs.launchpad.net/bugs/1967557/+attachment/5575762/+files/Stacktrace.txt ** Attachment removed: "ThreadStacktrace.txt" https://bugs.launchpad.net/bugs/1967557/+attachment/5575763/+files/ThreadStacktrace.txt ** This bug has been marked a duplicate of private bug 1955758 ** Information type changed from Private to Public ** Tags removed: need-amd64-retrace -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to udisks2 in Ubuntu. https://bugs.launchpad.net/bugs/1967557 Title: udisksd assert failure: malloc_consolidate(): unaligned fastbin chunk detected Status in udisks2 package in Ubuntu: New Bug description: system error after login ProblemType: Crash DistroRelease: Ubuntu 22.04 Package: udisks2 2.9.4-1 ProcVersionSignature: Ubuntu 5.15.0-23.23-generic 5.15.27 Uname: Linux 5.15.0-23-generic x86_64 ApportVersion: 2.20.11-0ubuntu80 Architecture: amd64 AssertionMessage: malloc_consolidate(): unaligned fastbin chunk detected CasperMD5CheckResult: pass CrashCounter: 1 CustomUdevRuleFiles: 70-snap.snapd-desktop-integration.rules 70-snap.snap-store.rules 70-snap.firefox.rules 70-snap.snapd.rules Date: Fri Apr 1 09:28:13 2022 ExecutablePath: /usr/libexec/udisks2/udisksd InstallationDate: Installed on 2022-03-25 (7 days ago) InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Alpha amd64 (20220324.3) MachineType: LENOVO 20BE003AUS ProcCmdline: /usr/libexec/udisks2/udisksd ProcEnviron: LANG=en_US.UTF-8 PATH=(custom, no user) ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.15.0-23-generic root=/dev/mapper/vgubuntu-root ro quiet splash vt.handoff=7 Signal: 6 SourcePackage: udisks2 StacktraceTop: __libc_message (action=action@entry=do_abort, fmt=fmt@entry=0x7fbba6deab8c "%s\n") at ../sysdeps/posix/libc_fatal.c:155 malloc_printerr (str=str@entry=0x7fbba6ded5d8 "malloc_consolidate(): unaligned fastbin chunk detected") at ./malloc/malloc.c:5664 malloc_consolidate (av=av@entry=0x7fbba6e28c80 ) at ./malloc/malloc.c:4750 _int_free (av=0x7fbba6e28c80 , p=0x55c8ef9adaf0, have_lock=) at ./malloc/malloc.c:4674 __GI___libc_free (mem=) at ./malloc/malloc.c:3391 Title: udisksd assert failure: malloc_consolidate(): unaligned fastbin chunk detected UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: N/A dmi.bios.date: 03/16/2016 dmi.bios.release: 2.23 dmi.bios.vendor: LENOVO dmi.bios.version: GMET75WW (2.23 ) dmi.board.asset.tag: Not Available dmi.board.name: 20BE003AUS dmi.board.vendor: LENOVO dmi.board.version: 0B98417 WIN dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: Not Available dmi.ec.firmware.release: 1.14 dmi.modalias: dmi:bvnLENOVO:bvrGMET75WW(2.23):bd03/16/2016:br2.23:efr1.14:svnLENOVO:pn20BE003AUS:pvrThinkPadT540p:rvnLENOVO:rn20BE003AUS:rvr0B98417WIN:cvnLENOVO:ct10:cvrNotAvailable:skuLENOVO_MT_20BE: dmi.product.family: ThinkPad T540p dmi.product.name: 20BE003AUS dmi.product.sku: LENOVO_MT_20BE dmi.product.version: ThinkPad T540p dmi.sys.vendor: LENOVO separator: To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/udisks2/+bug/1967557/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1653828] Re: Grammatical mistake in package description
This bug was fixed in the package xserver-xorg-video-intel -
2:2.99.917+git20210115-1
---
xserver-xorg-video-intel (2:2.99.917+git20210115-1) unstable; urgency=medium
* New upstream snapshot.
* Build against xserver 21.1.
* rules: Disable building with lto.
* control: Bump debhelper-compat to 13, policy to 4.6.0.
* Update README.source for salsa.
* watch: Update upstream git url.
-- Timo Aaltonen Wed, 09 Feb 2022 12:51:46 +0200
** Changed in: xserver-xorg-video-intel (Ubuntu)
Status: Confirmed => Fix Released
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to xserver-xorg-video-intel in Ubuntu.
https://bugs.launchpad.net/bugs/1653828
Title:
Grammatical mistake in package description
Status in xserver-xorg-video-intel package in Ubuntu:
Fix Released
Bug description:
This is an excerpt from the description of the package:
The use of this driver is discouraged if your hw is new enough (ca.
2007 and newer). You can try uninstalling this driver and let the
server use it's builtin modesetting driver instead.
Obviously, "it's" should be "its"; "builtin" also should be "built-
in", and "hw" probably should be all caps ("HW").
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/xserver-xorg-video-intel/+bug/1653828/+subscriptions
--
Mailing list: https://launchpad.net/~desktop-packages
Post to : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-packages
More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1967500] Re: kazam installation in 22.04 mate
Fixed on the libayatana-appindicator side. ** No longer affects: ubuntu-mate ** Also affects: libayatana-appindicator (Ubuntu) Importance: Undecided Status: New ** Changed in: libayatana-appindicator (Ubuntu) Status: New => Fix Released ** Changed in: kazam (Ubuntu) Status: Confirmed => Invalid -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to libayatana-appindicator in Ubuntu. https://bugs.launchpad.net/bugs/1967500 Title: kazam installation in 22.04 mate Status in kazam package in Ubuntu: Invalid Status in libayatana-appindicator package in Ubuntu: Fix Released Bug description: In Ubuntu Mate 22.04 I try to install KAZAM but I receive an error indication that dependencies can't be solved. gstreamer1.0-plugins- good When i try to install it via Synaptic it works after repairing broken packages libayatana-appindicator 3-1 (00.5.90.77) (info not given by software boutique) after that i remove kazam via synaptic and tried to reinstall it via software boutique and it works conclusion : software boutique doesn't give the correct info to solve the problem To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/kazam/+bug/1967500/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1888942]
The severity field for this bug is relatively low, S4. However, the bug has 5 duplicates. :adw, could you consider increasing the bug severity? For more information, please visit [auto_nag documentation](https://wiki.mozilla.org/Release_Management/autonag#severity_underestimated.py). -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to firefox in Ubuntu. https://bugs.launchpad.net/bugs/1888942 Title: marked url in firefox by using one click isn't copied to clipboard, only with a triple mouse-click Status in Mozilla Firefox: Confirmed Status in firefox package in Ubuntu: Invalid Bug description: Hi, if I click in an url in firefox, the whole url ist marked, i.e. highlighted. If I now use a click on the mousewheel to paste the content of the clipboard into another software, I discover that the url wasn't copied into the clipboard - the previous content ist filled in. That's confusing to me. I would expect: If I can mark an url in Firefox with a single mouse-click, which looks like a marking with a triple click, then it should be copied also in the clipboard. That would be a consisting behavior. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: firefox 78.0.2+build2-0ubuntu0.20.04.1 ProcVersionSignature: Ubuntu 5.4.0-40.44-generic 5.4.44 Uname: Linux 5.4.0-40-generic x86_64 AddonCompatCheckDisabled: False ApportVersion: 2.20.11-0ubuntu27.4 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: matthias 1453 F pulseaudio /dev/snd/controlC1: matthias 1453 F pulseaudio /dev/snd/pcmC1D0c: matthias 1453 F...m pulseaudio /dev/snd/pcmC1D0p: matthias 1453 F...m pulseaudio BuildID: 20200708170202 CasperMD5CheckResult: skip Channel: Unavailable CurrentDesktop: ubuntu:GNOME Date: Sat Jul 25 16:44:27 2020 DefaultProfileExtensions: extensions.sqlite corrupt or missing DefaultProfileIncompatibleExtensions: Unavailable (corrupt or non-existant compatibility.ini or extensions.sqlite) DefaultProfileLocales: extensions.sqlite corrupt or missing DefaultProfilePrefErrors: Unexpected character ',' before close parenthesis @ /usr/lib/firefox/omni.ja:greprefs.js:730 DefaultProfilePrefSources: prefs.js DefaultProfileThemes: extensions.sqlite corrupt or missing ExecutablePath: /usr/lib/firefox/firefox ForcedLayersAccel: False InstallationDate: Installed on 2020-04-24 (92 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) IpRoute: default via 192.168.11.1 dev wlp4s0 proto dhcp metric 600 169.254.0.0/16 dev wlp4s0 scope link metric 1000 192.168.11.0/24 dev wlp4s0 proto kernel scope link src 192.168.11.66 metric 600 Profile1Extensions: extensions.sqlite corrupt or missing Profile1IncompatibleExtensions: Unavailable (corrupt or non-existant compatibility.ini or extensions.sqlite) Profile1Locales: extensions.sqlite corrupt or missing Profile1PrefErrors: Unexpected character ',' before close parenthesis @ /usr/lib/firefox/omni.ja:greprefs.js:730 Profile1PrefSources: prefs.js Profile1Themes: extensions.sqlite corrupt or missing Profiles: Profile1 - LastVersion=74.0.1/20200403064753 (Out of date) Profile0 (Default) - LastVersion=78.0.2/20200708170202 (In use) RunningIncompatibleAddons: False SourcePackage: firefox UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 11/12/2019 dmi.bios.vendor: LENOVO dmi.bios.version: N14ET53W (1.31 ) dmi.board.asset.tag: Not Available dmi.board.name: 20BTS06G0J dmi.board.vendor: LENOVO dmi.board.version: SDK0E50510 WIN dmi.chassis.asset.tag: R90GJVAH dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: None dmi.modalias: dmi:bvnLENOVO:bvrN14ET53W(1.31):bd11/12/2019:svnLENOVO:pn20BTS06G0J:pvrThinkPadX1Carbon3rd:rvnLENOVO:rn20BTS06G0J:rvrSDK0E50510WIN:cvnLENOVO:ct10:cvrNone: dmi.product.family: ThinkPad X1 Carbon 3rd dmi.product.name: 20BTS06G0J dmi.product.sku: LENOVO_MT_20BT_BU_Think_FM_ThinkPad X1 Carbon 3rd dmi.product.version: ThinkPad X1 Carbon 3rd dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/firefox/+bug/1888942/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1888942]
As of 91.7.0esr the issue is still there. Focussing the address bar which has the URL selected doesn't copy the content to primary selection. Using the triple click workaround is different from all other Linux and Gtk applications. It is also different from browsers like Palemoon. Any selection is going to be copied to primary selection according to ICCCM and freedesktop.org: https://specifications.freedesktop.org/clipboards-spec/clipboards-latest.txt -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to firefox in Ubuntu. https://bugs.launchpad.net/bugs/1888942 Title: marked url in firefox by using one click isn't copied to clipboard, only with a triple mouse-click Status in Mozilla Firefox: Confirmed Status in firefox package in Ubuntu: Invalid Bug description: Hi, if I click in an url in firefox, the whole url ist marked, i.e. highlighted. If I now use a click on the mousewheel to paste the content of the clipboard into another software, I discover that the url wasn't copied into the clipboard - the previous content ist filled in. That's confusing to me. I would expect: If I can mark an url in Firefox with a single mouse-click, which looks like a marking with a triple click, then it should be copied also in the clipboard. That would be a consisting behavior. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: firefox 78.0.2+build2-0ubuntu0.20.04.1 ProcVersionSignature: Ubuntu 5.4.0-40.44-generic 5.4.44 Uname: Linux 5.4.0-40-generic x86_64 AddonCompatCheckDisabled: False ApportVersion: 2.20.11-0ubuntu27.4 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: matthias 1453 F pulseaudio /dev/snd/controlC1: matthias 1453 F pulseaudio /dev/snd/pcmC1D0c: matthias 1453 F...m pulseaudio /dev/snd/pcmC1D0p: matthias 1453 F...m pulseaudio BuildID: 20200708170202 CasperMD5CheckResult: skip Channel: Unavailable CurrentDesktop: ubuntu:GNOME Date: Sat Jul 25 16:44:27 2020 DefaultProfileExtensions: extensions.sqlite corrupt or missing DefaultProfileIncompatibleExtensions: Unavailable (corrupt or non-existant compatibility.ini or extensions.sqlite) DefaultProfileLocales: extensions.sqlite corrupt or missing DefaultProfilePrefErrors: Unexpected character ',' before close parenthesis @ /usr/lib/firefox/omni.ja:greprefs.js:730 DefaultProfilePrefSources: prefs.js DefaultProfileThemes: extensions.sqlite corrupt or missing ExecutablePath: /usr/lib/firefox/firefox ForcedLayersAccel: False InstallationDate: Installed on 2020-04-24 (92 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) IpRoute: default via 192.168.11.1 dev wlp4s0 proto dhcp metric 600 169.254.0.0/16 dev wlp4s0 scope link metric 1000 192.168.11.0/24 dev wlp4s0 proto kernel scope link src 192.168.11.66 metric 600 Profile1Extensions: extensions.sqlite corrupt or missing Profile1IncompatibleExtensions: Unavailable (corrupt or non-existant compatibility.ini or extensions.sqlite) Profile1Locales: extensions.sqlite corrupt or missing Profile1PrefErrors: Unexpected character ',' before close parenthesis @ /usr/lib/firefox/omni.ja:greprefs.js:730 Profile1PrefSources: prefs.js Profile1Themes: extensions.sqlite corrupt or missing Profiles: Profile1 - LastVersion=74.0.1/20200403064753 (Out of date) Profile0 (Default) - LastVersion=78.0.2/20200708170202 (In use) RunningIncompatibleAddons: False SourcePackage: firefox UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 11/12/2019 dmi.bios.vendor: LENOVO dmi.bios.version: N14ET53W (1.31 ) dmi.board.asset.tag: Not Available dmi.board.name: 20BTS06G0J dmi.board.vendor: LENOVO dmi.board.version: SDK0E50510 WIN dmi.chassis.asset.tag: R90GJVAH dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: None dmi.modalias: dmi:bvnLENOVO:bvrN14ET53W(1.31):bd11/12/2019:svnLENOVO:pn20BTS06G0J:pvrThinkPadX1Carbon3rd:rvnLENOVO:rn20BTS06G0J:rvrSDK0E50510WIN:cvnLENOVO:ct10:cvrNone: dmi.product.family: ThinkPad X1 Carbon 3rd dmi.product.name: 20BTS06G0J dmi.product.sku: LENOVO_MT_20BT_BU_Think_FM_ThinkPad X1 Carbon 3rd dmi.product.version: ThinkPad X1 Carbon 3rd dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/firefox/+bug/1888942/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1967535] Re: [81BG, Realtek ALC236, Mic, Internal] Recording problem
** Package changed: ubuntu => alsa-driver (Ubuntu) -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to alsa-driver in Ubuntu. https://bugs.launchpad.net/bugs/1967535 Title: [81BG, Realtek ALC236, Mic, Internal] Recording problem Status in alsa-driver package in Ubuntu: New Bug description: HI, im kinda new to linux-ubuntu im using it for like 6 month. my issue is that by default my integrated laptop microphone not working. in order to make it work i have to use pulseaudio software and everytime i boot my laptop i have to do pulseaudio --kill and pulseaudio --start in order to make the microphone working. and thats really frustrating, and the really really weird part of the issue is that now while i was trying to report this issue i pressed alt + f2 and then typed ubuntu-bug and then a windows got opened and it asked me to record my voice and then when i recorded my voice, the app played my voice back and i could hear my voice clearly i didnt even started pulseaudio. so i was shocked ! i thought it got fixed for a moment but no it seems like it only worked for the ubuntu-bug report app p.s : sorry for my messy english its not my native language ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: alsa-base 1.0.25+dfsg-0ubuntu5 ProcVersionSignature: Ubuntu 5.13.0-37.42~20.04.1-generic 5.13.19 Uname: Linux 5.13.0-37-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu27.21 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: sasha 1967 F pulseaudio /dev/snd/pcmC0D0c: sasha 1967 F...m pulseaudio /dev/snd/pcmC0D0p: sasha 1967 F...m pulseaudio CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Fri Apr 1 18:57:31 2022 InstallationDate: Installed on 2021-09-13 (200 days ago) InstallationMedia: Ubuntu 20.04.2.0 LTS "Focal Fossa" - Release amd64 (20210209.1) PackageArchitecture: all SourcePackage: alsa-driver Symptom: audio Symptom_AlsaRecordingTest: ALSA recording test through plughw:PCH successful Symptom_Card: Built-in Audio - HDA Intel PCH Symptom_Jack: Mic, Internal Symptom_PulseAudioRecordingTest: PulseAudio recording test through plughw:PCH successful Symptom_Type: None of the above Title: [81BG, Realtek ALC236, Mic, Internal] Recording problem UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 01/23/2018 dmi.bios.release: 1.23 dmi.bios.vendor: LENOVO dmi.bios.version: 6JCN23WW dmi.board.asset.tag: NO Asset Tag dmi.board.name: LNVNB161216 dmi.board.vendor: LENOVO dmi.board.version: NO DPK dmi.chassis.asset.tag: NO Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: Lenovo ideapad 320-15IKB dmi.ec.firmware.release: 1.23 dmi.modalias: dmi:bvnLENOVO:bvr6JCN23WW:bd01/23/2018:br1.23:efr1.23:svnLENOVO:pn81BG:pvrLenovoideapad320-15IKB:rvnLENOVO:rnLNVNB161216:rvrNODPK:cvnLENOVO:ct10:cvrLenovoideapad320-15IKB:skuLENOVO_MT_81BG_BU_idea_FM_ideapad320-15IKB: dmi.product.family: ideapad 320-15IKB dmi.product.name: 81BG dmi.product.sku: LENOVO_MT_81BG_BU_idea_FM_ideapad 320-15IKB dmi.product.version: Lenovo ideapad 320-15IKB dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1967535/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1967535] [NEW] [81BG, Realtek ALC236, Mic, Internal] Recording problem
You have been subscribed to a public bug: HI, im kinda new to linux-ubuntu im using it for like 6 month. my issue is that by default my integrated laptop microphone not working. in order to make it work i have to use pulseaudio software and everytime i boot my laptop i have to do pulseaudio --kill and pulseaudio --start in order to make the microphone working. and thats really frustrating, and the really really weird part of the issue is that now while i was trying to report this issue i pressed alt + f2 and then typed ubuntu-bug and then a windows got opened and it asked me to record my voice and then when i recorded my voice, the app played my voice back and i could hear my voice clearly i didnt even started pulseaudio. so i was shocked ! i thought it got fixed for a moment but no it seems like it only worked for the ubuntu-bug report app p.s : sorry for my messy english its not my native language ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: alsa-base 1.0.25+dfsg-0ubuntu5 ProcVersionSignature: Ubuntu 5.13.0-37.42~20.04.1-generic 5.13.19 Uname: Linux 5.13.0-37-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu27.21 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: sasha 1967 F pulseaudio /dev/snd/pcmC0D0c: sasha 1967 F...m pulseaudio /dev/snd/pcmC0D0p: sasha 1967 F...m pulseaudio CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Fri Apr 1 18:57:31 2022 InstallationDate: Installed on 2021-09-13 (200 days ago) InstallationMedia: Ubuntu 20.04.2.0 LTS "Focal Fossa" - Release amd64 (20210209.1) PackageArchitecture: all SourcePackage: alsa-driver Symptom: audio Symptom_AlsaRecordingTest: ALSA recording test through plughw:PCH successful Symptom_Card: Built-in Audio - HDA Intel PCH Symptom_Jack: Mic, Internal Symptom_PulseAudioRecordingTest: PulseAudio recording test through plughw:PCH successful Symptom_Type: None of the above Title: [81BG, Realtek ALC236, Mic, Internal] Recording problem UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 01/23/2018 dmi.bios.release: 1.23 dmi.bios.vendor: LENOVO dmi.bios.version: 6JCN23WW dmi.board.asset.tag: NO Asset Tag dmi.board.name: LNVNB161216 dmi.board.vendor: LENOVO dmi.board.version: NO DPK dmi.chassis.asset.tag: NO Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: Lenovo ideapad 320-15IKB dmi.ec.firmware.release: 1.23 dmi.modalias: dmi:bvnLENOVO:bvr6JCN23WW:bd01/23/2018:br1.23:efr1.23:svnLENOVO:pn81BG:pvrLenovoideapad320-15IKB:rvnLENOVO:rnLNVNB161216:rvrNODPK:cvnLENOVO:ct10:cvrLenovoideapad320-15IKB:skuLENOVO_MT_81BG_BU_idea_FM_ideapad320-15IKB: dmi.product.family: ideapad 320-15IKB dmi.product.name: 81BG dmi.product.sku: LENOVO_MT_81BG_BU_idea_FM_ideapad 320-15IKB dmi.product.version: Lenovo ideapad 320-15IKB dmi.sys.vendor: LENOVO ** Affects: alsa-driver (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug focal third-party-packages -- [81BG, Realtek ALC236, Mic, Internal] Recording problem https://bugs.launchpad.net/bugs/1967535 You received this bug notification because you are a member of Desktop Packages, which is subscribed to alsa-driver in Ubuntu. -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1964547] Re: [apt] Firefox 98 installed from apt cannot Play YouTube
The same bug? @osomon https://www.reddit.com/r/firefox/comments/t9s7mj/playing_videos_in_arch_linux_suddenly_fails_with/ -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to firefox in Ubuntu. https://bugs.launchpad.net/bugs/1964547 Title: [apt] Firefox 98 installed from apt cannot Play YouTube Status in firefox package in Ubuntu: Incomplete Bug description: • Ubuntu 21.10 (64 bit) • Firefox 98 installed via apt (cookies & cache have been cleared) • Kernel 5.13.0-30-generic x86_64 • Tried on both wayland and X11 session → same result Steps to reproduce: (1) Visit https://www.youtube.com (2) Choose one of the video Actual Result: Video doesn't play What Expected: Video Play normally Previously it was normal on Firefox 97 (apt version) Tried installing Firefox 98 Snap version and it works normally To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/firefox/+bug/1964547/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1967539] [NEW] All file downloads fail
Public bug reported: Moving to the snap version results in all file download failing. Message is just "failed". ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: firefox 1:1snap1-0ubuntu2 Uname: Linux 5.16.0-18.2-liquorix-amd64 x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu80 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: KDE Date: Fri Apr 1 15:56:13 2022 InstallationDate: Installed on 2017-12-06 (1577 days ago) InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20171018) RebootRequiredPkgs: Error: path contained symlinks. Snap.Changes: no changes found SourcePackage: firefox UpgradeStatus: Upgraded to jammy on 2021-12-08 (114 days ago) ** Affects: firefox (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug jammy third-party-packages -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to firefox in Ubuntu. https://bugs.launchpad.net/bugs/1967539 Title: All file downloads fail Status in firefox package in Ubuntu: New Bug description: Moving to the snap version results in all file download failing. Message is just "failed". ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: firefox 1:1snap1-0ubuntu2 Uname: Linux 5.16.0-18.2-liquorix-amd64 x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu80 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: KDE Date: Fri Apr 1 15:56:13 2022 InstallationDate: Installed on 2017-12-06 (1577 days ago) InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20171018) RebootRequiredPkgs: Error: path contained symlinks. Snap.Changes: no changes found SourcePackage: firefox UpgradeStatus: Upgraded to jammy on 2021-12-08 (114 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/firefox/+bug/1967539/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1967456] Re: Jammy didn't use nvidia driver when executing firefox
** Tags added: snap -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to firefox in Ubuntu. https://bugs.launchpad.net/bugs/1967456 Title: Jammy didn't use nvidia driver when executing firefox Status in OEM Priority Project: New Status in firefox package in Ubuntu: Confirmed Bug description: [Reproduce step] 1. Install Jammy beta. 2. Install Nvidia driver by ubuntu-driver install. 3. Connect monitor to dGPU output port. 4. Run firefox, type "about:support" in url, and check column "GPU #1" [Expected result] should see nvidia driver info. [Actual result] still use llvmpipe [Info] OS version: Ubuntu Jammy Jellyfish (development branch) Device: HP Z2 Mini G5 workstation CID: 202008-28179 Wayland in use. ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: linux-image-5.15.0-23-generic 5.15.0-23.23 ProcVersionSignature: Ubuntu 5.15.0-23.23-generic 5.15.27 Uname: Linux 5.15.0-23-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu79 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: u 1186 F pulseaudio /dev/snd/controlC1: u 1186 F pulseaudio CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Fri Apr 1 00:07:47 2022 InstallationDate: Installed on 2022-04-01 (0 days ago) InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Beta amd64 (20220329.1) MachineType: HP HP Z2 Mini G5 Workstation ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcFB: 0 EFI VGA ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.15.0-23-generic root=UUID=adaf5521-655d-454a-9bad-ef17619a51f2 ro quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-5.15.0-23-generic N/A linux-backports-modules-5.15.0-23-generic N/A linux-firmware 20220314.gitcd01f857-0ubuntu2 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 07/02/2020 dmi.bios.release: 0.1 dmi.bios.vendor: HP dmi.bios.version: S50 Ver. 01.00.01 dmi.board.name: 8754 dmi.board.vendor: HP dmi.board.version: KBC Version 09.08.03 dmi.chassis.type: 2 dmi.chassis.vendor: HP dmi.ec.firmware.release: 9.8 dmi.modalias: dmi:bvnHP:bvrS50Ver.01.00.01:bd07/02/2020:br0.1:efr9.8:svnHP:pnHPZ2MiniG5Workstation:pvr:rvnHP:rn8754:rvrKBCVersion09.08.03:cvnHP:ct2:cvr:sku9JD38AV: dmi.product.family: 103C_53335X HP Workstation dmi.product.name: HP Z2 Mini G5 Workstation dmi.product.sku: 9JD38AV dmi.sys.vendor: HP To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/1967456/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1794064] Re: Clicking a hyperlink in a PDF fails to open it if the default browser is a snap
** Tags added: rls-jj-incoming -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to evince in Ubuntu. https://bugs.launchpad.net/bugs/1794064 Title: Clicking a hyperlink in a PDF fails to open it if the default browser is a snap Status in apparmor package in Ubuntu: Confirmed Status in evince package in Ubuntu: Triaged Status in evince package in Debian: New Bug description: This is related to bug #1792648. After fixing that one (see discussion at https://salsa.debian.org/gnome-team/evince/merge_requests/1), clicking a hyperlink in a PDF opens it correctly if the default browser is a well-known application (such as /usr/bin/firefox), but it fails to do so if the default browser is a snap (e.g. the chromium snap). This is not a recent regression, it's not working on bionic either. ProblemType: Bug DistroRelease: Ubuntu 18.10 Package: evince 3.30.0-2 ProcVersionSignature: Ubuntu 4.18.0-7.8-generic 4.18.5 Uname: Linux 4.18.0-7-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.20.10-0ubuntu11 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Mon Sep 24 12:28:06 2018 EcryptfsInUse: Yes InstallationDate: Installed on 2016-07-02 (813 days ago) InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 (20160420.1) SourcePackage: evince UpgradeStatus: Upgraded to cosmic on 2018-09-14 (9 days ago) modified.conffile..etc.apparmor.d.abstractions.evince: [modified] mtime.conffile..etc.apparmor.d.abstractions.evince: 2018-09-24T11:35:41.904158 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apparmor/+bug/1794064/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1967520] Re: Firefox snap : unable to open weblink from pdf
*** This bug is a duplicate of bug 1794064 *** https://bugs.launchpad.net/bugs/1794064 ** This bug has been marked a duplicate of bug 1794064 Clicking a hyperlink in a PDF fails to open it if the default browser is a snap -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to firefox in Ubuntu. https://bugs.launchpad.net/bugs/1967520 Title: Firefox snap : unable to open weblink from pdf Status in firefox package in Ubuntu: New Bug description: The new firefox snap in jammy is unable to open weblink included in pdf (for example using evince). Steps to reproduce: 1. clean install of jammy 2. download the following pdf: https://packaging.ubuntu.com/ubuntu-packaging-guide.pdf 3. open this pdf with evince 4. go to page 6 and click on the link "The new account help page". 5. the link is not opened in firefox The same behavior occurs for any weblink in any pdf. In Ubuntu 20.04 this is working fine. The chromium snap has the same problem. This seems to be a problem with AppArmor and snap. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/firefox/+bug/1967520/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1967521] Re: Test binaries in libsndfile-dev package
** Changed in: libsndfile (Ubuntu) Importance: Undecided => Low -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to libsndfile in Ubuntu. https://bugs.launchpad.net/bugs/1967521 Title: Test binaries in libsndfile-dev package Status in libsndfile package in Ubuntu: New Bug description: There are programs from the libsndfile test suite in dev package. Should they be there? To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libsndfile/+bug/1967521/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 880563] Re: Gnomine corrupted
** Changed in: gnome-games (Ubuntu) Status: New => Fix Released -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to the bug report. https://bugs.launchpad.net/bugs/880563 Title: Gnomine corrupted Status in gnome-games package in Ubuntu: Fix Released Bug description: System: Ubuntu 11.10 with both gnome desktop and xfce desktop installed, fully updated Start the system as Xubuntu, that is, with the xfce desktop When selecting Applications Menu > Games > Mines (gnomine) - two instances of the gnomine process are launched simultaneously - the application does not remember its most recent display settings (that is, size of the application on the screen on the previous exit) - specifically, on every start-up gnomine appears as a diminutive application with tiny buttons, the smallest screen rendering of the game available. Note: Under Ubuntu 11.04, this behaviour did not occur, and the application ran properly without any problems (one process instance, and remembering its size on screen on exit). To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-games/+bug/880563/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1966786] Re: login screen shown twice with VirtualBox Guest Additions
VBoxGuestAdditions_6.1.26.iso gives the same issue. Removing the guest additions with `sudo ./VBoxLinuxAdditions.run uninstall` fixes the double login. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-shell in Ubuntu. https://bugs.launchpad.net/bugs/1966786 Title: login screen shown twice with VirtualBox Guest Additions Status in gdm3 package in Ubuntu: Confirmed Status in gnome-shell package in Ubuntu: Confirmed Bug description: The login screen is shown twice and I have to supply the password twice. The system works normally afterwards. When I select auto-login in the settings still one login screen is shown. gdm.service - GNOME Display Manager Loaded: loaded (/lib/systemd/system/gdm.service; static) Active: active (running) since Mon 2022-03-28 11:47:32 AST; 6min ago Process: 1885 ExecStartPre=/usr/share/gdm/generate-config (code=exited, status=0/SUCCESS) Main PID: 1915 (gdm3) Tasks: 3 (limit: 2291) Memory: 5.0M CPU: 125ms CGroup: /system.slice/gdm.service └─1915 /usr/sbin/gdm3 mar 28 11:47:32 vm-ubuntu-2204 systemd[1]: Starting GNOME Display Manager... mar 28 11:47:32 vm-ubuntu-2204 systemd[1]: Started GNOME Display Manager. mar 28 11:47:32 vm-ubuntu-2204 gdm-launch-environment][1921]: pam_unix(gdm-launch-environment:session): session opened for user gdm(uid=125) by (uid=0) mar 28 11:47:40 vm-ubuntu-2204 gdm-password][2290]: gkr-pam: unable to locate daemon control file mar 28 11:47:40 vm-ubuntu-2204 gdm-password][2290]: gkr-pam: stashed password to try later in open session mar 28 11:47:40 vm-ubuntu-2204 gdm-password][2290]: pam_unix(gdm-password:session): session opened for user bertadmin(uid=1000) by (uid=0) mar 28 11:47:40 vm-ubuntu-2204 gdm-password][2290]: gkr-pam: gnome-keyring-daemon started properly and unlocked keyring mar 28 11:47:57 vm-ubuntu-2204 gdm3[1915]: Gdm: Child process -1937 was already dead. ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: gdm3 42.0-1ubuntu1 ProcVersionSignature: Ubuntu 5.15.0-23.23-generic 5.15.27 Uname: Linux 5.15.0-23-generic x86_64 ApportVersion: 2.20.11-0ubuntu79 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: ubuntu:GNOME Date: Mon Mar 28 11:48:17 2022 InstallationDate: Installed on 2020-01-25 (793 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Alpha amd64 (20200124) SourcePackage: gdm3 UpgradeStatus: Upgraded to jammy on 2022-03-23 (4 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gdm3/+bug/1966786/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1966786] Re: login screen shown twice
It's the VirtualBox Guest Additions that triggers this bug. With the latest VBoxGuestAdditions_6.1.32.iso and before. It's not the `sudo apt install build-essential dkms` that need to be run to install the Guest Additions. ** Summary changed: - login screen shown twice + login screen shown twice with VirtualBox Guest Additions -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-shell in Ubuntu. https://bugs.launchpad.net/bugs/1966786 Title: login screen shown twice with VirtualBox Guest Additions Status in gdm3 package in Ubuntu: Confirmed Status in gnome-shell package in Ubuntu: Confirmed Bug description: The login screen is shown twice and I have to supply the password twice. The system works normally afterwards. When I select auto-login in the settings still one login screen is shown. gdm.service - GNOME Display Manager Loaded: loaded (/lib/systemd/system/gdm.service; static) Active: active (running) since Mon 2022-03-28 11:47:32 AST; 6min ago Process: 1885 ExecStartPre=/usr/share/gdm/generate-config (code=exited, status=0/SUCCESS) Main PID: 1915 (gdm3) Tasks: 3 (limit: 2291) Memory: 5.0M CPU: 125ms CGroup: /system.slice/gdm.service └─1915 /usr/sbin/gdm3 mar 28 11:47:32 vm-ubuntu-2204 systemd[1]: Starting GNOME Display Manager... mar 28 11:47:32 vm-ubuntu-2204 systemd[1]: Started GNOME Display Manager. mar 28 11:47:32 vm-ubuntu-2204 gdm-launch-environment][1921]: pam_unix(gdm-launch-environment:session): session opened for user gdm(uid=125) by (uid=0) mar 28 11:47:40 vm-ubuntu-2204 gdm-password][2290]: gkr-pam: unable to locate daemon control file mar 28 11:47:40 vm-ubuntu-2204 gdm-password][2290]: gkr-pam: stashed password to try later in open session mar 28 11:47:40 vm-ubuntu-2204 gdm-password][2290]: pam_unix(gdm-password:session): session opened for user bertadmin(uid=1000) by (uid=0) mar 28 11:47:40 vm-ubuntu-2204 gdm-password][2290]: gkr-pam: gnome-keyring-daemon started properly and unlocked keyring mar 28 11:47:57 vm-ubuntu-2204 gdm3[1915]: Gdm: Child process -1937 was already dead. ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: gdm3 42.0-1ubuntu1 ProcVersionSignature: Ubuntu 5.15.0-23.23-generic 5.15.27 Uname: Linux 5.15.0-23-generic x86_64 ApportVersion: 2.20.11-0ubuntu79 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: ubuntu:GNOME Date: Mon Mar 28 11:48:17 2022 InstallationDate: Installed on 2020-01-25 (793 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Alpha amd64 (20200124) SourcePackage: gdm3 UpgradeStatus: Upgraded to jammy on 2022-03-23 (4 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gdm3/+bug/1966786/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1967456] Re: Jammy didn't use nvidia driver when executing firefox
** Also affects: oem-priority Importance: Undecided Status: New -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to firefox in Ubuntu. https://bugs.launchpad.net/bugs/1967456 Title: Jammy didn't use nvidia driver when executing firefox Status in OEM Priority Project: New Status in firefox package in Ubuntu: Confirmed Bug description: [Reproduce step] 1. Install Jammy beta. 2. Install Nvidia driver by ubuntu-driver install. 3. Connect monitor to dGPU output port. 4. Run firefox, type "about:support" in url, and check column "GPU #1" [Expected result] should see nvidia driver info. [Actual result] still use llvmpipe [Info] OS version: Ubuntu Jammy Jellyfish (development branch) Device: HP Z2 Mini G5 workstation CID: 202008-28179 Wayland in use. ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: linux-image-5.15.0-23-generic 5.15.0-23.23 ProcVersionSignature: Ubuntu 5.15.0-23.23-generic 5.15.27 Uname: Linux 5.15.0-23-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu79 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: u 1186 F pulseaudio /dev/snd/controlC1: u 1186 F pulseaudio CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Fri Apr 1 00:07:47 2022 InstallationDate: Installed on 2022-04-01 (0 days ago) InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Beta amd64 (20220329.1) MachineType: HP HP Z2 Mini G5 Workstation ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcFB: 0 EFI VGA ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.15.0-23-generic root=UUID=adaf5521-655d-454a-9bad-ef17619a51f2 ro quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-5.15.0-23-generic N/A linux-backports-modules-5.15.0-23-generic N/A linux-firmware 20220314.gitcd01f857-0ubuntu2 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 07/02/2020 dmi.bios.release: 0.1 dmi.bios.vendor: HP dmi.bios.version: S50 Ver. 01.00.01 dmi.board.name: 8754 dmi.board.vendor: HP dmi.board.version: KBC Version 09.08.03 dmi.chassis.type: 2 dmi.chassis.vendor: HP dmi.ec.firmware.release: 9.8 dmi.modalias: dmi:bvnHP:bvrS50Ver.01.00.01:bd07/02/2020:br0.1:efr9.8:svnHP:pnHPZ2MiniG5Workstation:pvr:rvnHP:rn8754:rvrKBCVersion09.08.03:cvnHP:ct2:cvr:sku9JD38AV: dmi.product.family: 103C_53335X HP Workstation dmi.product.name: HP Z2 Mini G5 Workstation dmi.product.sku: 9JD38AV dmi.sys.vendor: HP To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/1967456/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1963804] Re: nvidia on a HP Pavilion tx1000 laptop - corrupt graphics
This also happens on Ubuntu 22.04 beta (x86_64). I have a workaround which appears to overcome the graphics corruption problems on this system... Using information gleaned from:- https://linuxconfig.org/how-to-disable-blacklist-nouveau-nvidia-driver-on-ubuntu-20-04-focal-fossa-linux I performed these commands:- sudo bash -c "echo blacklist nouveau > /etc/modprobe.d/blacklist-nvidia-nouveau.conf" sudo bash -c "echo options nouveau modeset=0 >> /etc/modprobe.d/blacklist-nvidia-nouveau.conf" And ensured that /etc/modprobe.d/blacklist-nvidia-nouveau.conf contained the right informaiton:- cat /etc/modprobe.d/blacklist-nvidia-nouveau.conf And the file should contain:- blacklist nouveau options nouveau modeset=0 Then this command is used to finish things off. sudo update-initramfs -u Then I rebooted and the graphics corruption appears to be eliminated. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to xserver-xorg-video-nouveau in Ubuntu. https://bugs.launchpad.net/bugs/1963804 Title: nvidia on a HP Pavilion tx1000 laptop - corrupt graphics Status in xserver-xorg-video-nouveau package in Ubuntu: New Bug description: Screen gets corrupted. The GNOME time at the top of the screen tends to get corrupted - it looks like the graphics are being logically "OR"ed onto the existing frame buffer. On one occasion, the entire wallpaper was corrupted. In other occasions, the system menu contents are partly corrupted. ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: xserver-xorg-video-nouveau 1:1.0.17-1build1 ProcVersionSignature: Ubuntu 5.15.0-18.18-generic 5.15.12 Uname: Linux 5.15.0-18-generic x86_64 NonfreeKernelModules: wl ApportVersion: 2.20.11-0ubuntu78 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CasperMD5CheckResult: pass CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Sun Mar 6 11:38:13 2022 DistUpgraded: Fresh install DistroCodename: jammy DistroVariant: ubuntu DkmsStatus: bcmwl/6.30.223.271+bdcom, 5.15.0-18-generic, x86_64: installed ExtraDebuggingInterest: Yes GraphicsCard: NVIDIA Corporation C51 [GeForce Go 6150] [10de:0244] (rev a2) (prog-if 00 [VGA controller]) Subsystem: Hewlett-Packard Company C51 [GeForce Go 6150] [103c:30bf] InstallationDate: Installed on 2022-03-05 (0 days ago) InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Alpha amd64 (20220228) MachineType: Hewlett-Packard HP Pavilion tx1000 (GT493EA#ABU) ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.15.0-18-generic root=UUID=3e8eba22-2d30-448c-8101-365b0b24d856 ro quiet splash vt.handoff=7 SourcePackage: xserver-xorg-video-nouveau UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 06/08/2007 dmi.bios.release: 15.19 dmi.bios.vendor: Hewlett-Packard dmi.bios.version: F.13A0 dmi.board.name: 30BF dmi.board.vendor: Quanta dmi.board.version: 69.27 dmi.chassis.type: 10 dmi.chassis.vendor: Quanta dmi.chassis.version: N/A dmi.ec.firmware.release: 105.39 dmi.modalias: dmi:bvnHewlett-Packard:bvrF.13A0:bd06/08/2007:br15.19:efr105.39:svnHewlett-Packard:pnHPPaviliontx1000(GT493EA#ABU):pvrRev1:rvnQuanta:rn30BF:rvr69.27:cvnQuanta:ct10:cvrN/A:sku: dmi.product.family: 103C_5335KV dmi.product.name: HP Pavilion tx1000 (GT493EA#ABU) dmi.product.version: Rev 1 dmi.sys.vendor: Hewlett-Packard version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.109-2ubuntu1 version.libgl1-mesa-dri: libgl1-mesa-dri 21.3.5-1ubuntu1 version.libgl1-mesa-glx: libgl1-mesa-glx N/A version.xserver-xorg-core: xserver-xorg-core 2:1.20.14-1ubuntu1 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-2build1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20200714-1ubuntu2 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.17-1build1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xserver-xorg-video-nouveau/+bug/1963804/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1967520] Re: Firefox snap : unable to open weblink from pdf
Might be the same as: https://bugs.launchpad.net/ubuntu/+source/firefox/+bug/1826793 -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to firefox in Ubuntu. https://bugs.launchpad.net/bugs/1967520 Title: Firefox snap : unable to open weblink from pdf Status in firefox package in Ubuntu: New Bug description: The new firefox snap in jammy is unable to open weblink included in pdf (for example using evince). Steps to reproduce: 1. clean install of jammy 2. download the following pdf: https://packaging.ubuntu.com/ubuntu-packaging-guide.pdf 3. open this pdf with evince 4. go to page 6 and click on the link "The new account help page". 5. the link is not opened in firefox The same behavior occurs for any weblink in any pdf. In Ubuntu 20.04 this is working fine. The chromium snap has the same problem. This seems to be a problem with AppArmor and snap. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/firefox/+bug/1967520/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1967521] [NEW] Test binaries in libsndfile-dev package
Public bug reported: There are programs from the libsndfile test suite in dev package. Should they be there? ** Affects: libsndfile (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to libsndfile in Ubuntu. https://bugs.launchpad.net/bugs/1967521 Title: Test binaries in libsndfile-dev package Status in libsndfile package in Ubuntu: New Bug description: There are programs from the libsndfile test suite in dev package. Should they be there? To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libsndfile/+bug/1967521/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1967520] [NEW] Firefox snap : unable to open weblink from pdf
Public bug reported: The new firefox snap in jammy is unable to open weblink included in pdf (for example using evince). Steps to reproduce: 1. clean install of jammy 2. download the following pdf: https://packaging.ubuntu.com/ubuntu-packaging-guide.pdf 3. open this pdf with evince 4. go to page 6 and click on the link "The new account help page". 5. the link is not opened in firefox The same behavior occurs for any weblink in any pdf. In Ubuntu 20.04 this is working fine. The chromium snap has the same problem. This seems to be a problem with AppArmor and snap. ** Affects: firefox (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to firefox in Ubuntu. https://bugs.launchpad.net/bugs/1967520 Title: Firefox snap : unable to open weblink from pdf Status in firefox package in Ubuntu: New Bug description: The new firefox snap in jammy is unable to open weblink included in pdf (for example using evince). Steps to reproduce: 1. clean install of jammy 2. download the following pdf: https://packaging.ubuntu.com/ubuntu-packaging-guide.pdf 3. open this pdf with evince 4. go to page 6 and click on the link "The new account help page". 5. the link is not opened in firefox The same behavior occurs for any weblink in any pdf. In Ubuntu 20.04 this is working fine. The chromium snap has the same problem. This seems to be a problem with AppArmor and snap. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/firefox/+bug/1967520/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1736222] Re: speech-dispatcher distorts all sound
I still see this error on Ubuntu 21.10 with speech-dispatcher 0.10.2-2build1 so the fix @linmanfu mentions unfortunately did not help. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to speech-dispatcher in Ubuntu. https://bugs.launchpad.net/bugs/1736222 Title: speech-dispatcher distorts all sound Status in speech-dispatcher package in Ubuntu: Confirmed Bug description: So, a brand new computer running Ubuntu 16.04.3 LTS. In hardinfo summary, my audio adapters are • HDA-Intel - HDA Intel HDMI • HDA-Intel - HDA Intel PCH • HDA-Intel - HDA NVidia In detail: Intel Corporation Xeon E3-1200 v3/4th Gen Core Processor HD Audio Controller (rev 06) Memory 16kb (non-prefetchable), snd_hda_intel As soon as I load a website in Firefox that utilizes speech-dispatcher (fimfiction.net) all sounds get distorted, whether I click a paragraph for TTS reading or not. The problem seems to go away if I don't use the site after a while. When I close down Firefox the problem still lingers a bit, but maybe not as long. One thing I did which seemed faster was close down everything, then load what I wanted to listen to (Skype, Discord), and if it still persisted I would go into "Sound Settings" and after a few blinks in that window the sound is normal again. While the site is open, according to "Sound Settings" (from the speaker icon menu) and Pulse Audio Volume Controller (pavu) there are 4 copies of this package. Muting them did not help the problem, but moving one of them, and a very specific one, from the "Built-in Audio Analog Stereo" to something else like HDA NVidia (HDMI 3) seems to be a workaround. Just so you know, I do not use the HDMI cable for sound, but instead use the "headphones" jack. If you need any more details, I'll try to provide them. /Edward To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/speech-dispatcher/+bug/1736222/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1967254] Re: webkit2gtk 2.36.0-1 fails to built on amd64
Solved by: * Reduce the number of parallel build jobs on Ubuntu's amd64 ** Changed in: webkit2gtk (Ubuntu) Status: New => Fix Released -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to webkit2gtk in Ubuntu. https://bugs.launchpad.net/bugs/1967254 Title: webkit2gtk 2.36.0-1 fails to built on amd64 Status in webkit2gtk package in Ubuntu: Fix Released Bug description: Got this error: ninja: build stopped: subcommand failed. dh_auto_build: error: cd build-soup2 && LC_ALL=C.UTF-8 ninja -j4 -v returned exit code 1 make[1]: *** [debian/rules:204: override_dh_auto_build] Error 25 make[1]: Leaving directory '/<>' make: *** [debian/rules:183: binary] Error 2 dpkg-buildpackage: error: debian/rules binary subprocess returned exit status 2 https://launchpadlibrarian.net/593778486/buildlog_ubuntu-jammy-amd64.webkit2gtk_2.36.0-1_BUILDING.txt.gz To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/webkit2gtk/+bug/1967254/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1779890] Re: Nautilus does not use a valid Kerberos ticket when accessing Samba share
I tried this to check if the problem is really the slow writing of the kerberos ticket to the disk: disable the workaround in /etc/systemd/user/gvfs-daemon.service reboot the slow machine connect to the slow machine with ssh as "aduser" (a kerberos ticket is acquired and written to /tmp/krb5cc_1136602666_6v25tM and gvfsd is started) from the ssh session: killall gvfsd login as aduser in the normal graphical console of the slow machine After login, Nemo is able to browse the network without asking username and password. Note, however, that after login, the /tmp/krb5cc_1136602666_6v25tM ticket is replaced by a new one and it is not possible to browse the network every time a new reboot and a new login is made. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gvfs in Ubuntu. https://bugs.launchpad.net/bugs/1779890 Title: Nautilus does not use a valid Kerberos ticket when accessing Samba share Status in gvfs: Unknown Status in gvfs package in Ubuntu: Triaged Bug description: Nautilus prompts for username and password when accessing a Samba share on a network drive, despite having a perfectly valid unexpired Kerberos ticket. The Kerberos ticket is obtained automatically at logon by authentication against a Samba Active Directory server (Samba AD-DC). Accessing the same Samba share with the same Kerberos ticket via "smbclient //host/sharename -k" works fine. One known workaround is: "nautilus -q", and then "killall gvfsd". After that, accessing the Samba share with Nautilus works normally as it should. I did not experience this issue in Ubuntu 16.04. It appears that a regression was introduced somewhere between 16.04 and 18.04. The issue is quite annoying and confusing for the users who are used to accessing Samba shares on the network drive without being prompted for their username and password. The issue appears to manifest itself usually not on the first access to a Samba share, but on subsequent accesses after a system reboot or upon user logout/login. Strangely, removing ~/.cache/ibus/bus/registry file before user login appears to fix the issue for the current user session, but then the problem reappears upon subsequent user logins or after a system reboot. Nemo appears to have the same problem as Nautilus. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: gvfs-daemons 1.36.1-0ubuntu1 ProcVersionSignature: Ubuntu 4.15.0-24.26-generic 4.15.18 Uname: Linux 4.15.0-24-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.9-0ubuntu7.2 Architecture: amd64 Date: Tue Jul 3 11:12:06 2018 ExecutablePath: /usr/lib/gvfs/gvfsd InstallationDate: Installed on 2018-04-27 (66 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426) ProcEnviron: LANG=en_CA.UTF-8 PATH=(custom, no user) SHELL=/bin/bash XDG_RUNTIME_DIR= SourcePackage: gvfs UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/gvfs/+bug/1779890/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1966115] Re: wrong icon used with the new branding
This bug was fixed in the package gnome-initial-setup - 42.0.1-1ubuntu2 --- gnome-initial-setup (42.0.1-1ubuntu2) jammy; urgency=medium * debian/patches/ubuntu-distributor-logo.patch: - replace another use of the wrong logo (lp: #1966115) -- Sebastien Bacher Tue, 29 Mar 2022 09:35:08 +0200 ** Changed in: gnome-initial-setup (Ubuntu) Status: Fix Committed => Fix Released -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-initial-setup in Ubuntu. https://bugs.launchpad.net/bugs/1966115 Title: wrong icon used with the new branding Status in gnome-initial-setup package in Ubuntu: Fix Released Bug description: Since the updated ubuntu branding has landed, the icon isn't just the logo. See attached screenshot To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-initial-setup/+bug/1966115/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1967487] Re: gnome-shell crashed with signal 5 in g_log_structured_array()
*** This bug is a duplicate of bug 1967486 *** https://bugs.launchpad.net/bugs/1967486 Thank you for taking the time to report this crash and helping to make this software better. This particular crash has already been reported and is a duplicate of bug #1967486, so is being marked as such. Please look at the other bug report to see if there is any missing information that you can provide, or to see if there is a workaround for the bug. Additionally, any further discussion regarding the bug should occur in the other report. Please continue to report any other bugs you may find. ** Attachment removed: "CoreDump.gz" https://bugs.launchpad.net/bugs/1967487/+attachment/5575582/+files/CoreDump.gz ** Attachment removed: "Disassembly.txt" https://bugs.launchpad.net/bugs/1967487/+attachment/5575584/+files/Disassembly.txt ** Attachment removed: "ProcMaps.txt" https://bugs.launchpad.net/bugs/1967487/+attachment/5575588/+files/ProcMaps.txt ** Attachment removed: "ProcStatus.txt" https://bugs.launchpad.net/bugs/1967487/+attachment/5575589/+files/ProcStatus.txt ** Attachment removed: "Registers.txt" https://bugs.launchpad.net/bugs/1967487/+attachment/5575590/+files/Registers.txt ** Attachment removed: "Stacktrace.txt" https://bugs.launchpad.net/bugs/1967487/+attachment/5575592/+files/Stacktrace.txt ** Attachment removed: "ThreadStacktrace.txt" https://bugs.launchpad.net/bugs/1967487/+attachment/5575593/+files/ThreadStacktrace.txt ** This bug has been marked a duplicate of private bug 1967486 ** Information type changed from Private to Public ** Tags removed: need-amd64-retrace -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-shell in Ubuntu. https://bugs.launchpad.net/bugs/1967487 Title: gnome-shell crashed with signal 5 in g_log_structured_array() Status in gnome-shell package in Ubuntu: New Bug description: crash happens when trying to connect external display ProblemType: Crash DistroRelease: Ubuntu 22.04 Package: gnome-shell 42.0-1ubuntu1 ProcVersionSignature: Ubuntu 5.15.0-23.23-generic 5.15.27 Uname: Linux 5.15.0-23-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu80 Architecture: amd64 CasperMD5CheckResult: pass CrashCounter: 1 CurrentDesktop: ubuntu:GNOME Date: Fri Apr 1 10:36:15 2022 DisplayManager: gdm3 ExecutablePath: /usr/bin/gnome-shell InstallationDate: Installed on 2022-02-25 (34 days ago) InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Alpha amd64 (20220224) ProcCmdline: /usr/bin/gnome-shell ProcEnviron: LANG=en_GB.UTF-8 LANGUAGE=en_GB:en PATH=(custom, no username) SHELL=/bin/bash XDG_RUNTIME_DIR= RelatedPackageVersions: mutter-common 42.0-1ubuntu1 Signal: 5 SourcePackage: gnome-shell StacktraceTop: g_log_structured_array () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 g_log_default_handler () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 ?? () g_logv () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 g_log () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 Title: gnome-shell crashed with signal 5 in g_log_structured_array() UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo separator: To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1967487/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1208091] Re: scanimage assert failure: *** Error in `scanimage': double free or corruption (top): 0x0000000002598130 ***
upstream changed and the patch no longer applies cleanly. Requesting
code inspection from someone who understands C.
https://gitlab.com/sane-project/backends/-/blob/master/backend/net.c
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to sane-backends in Ubuntu.
https://bugs.launchpad.net/bugs/1208091
Title:
scanimage assert failure: *** Error in `scanimage': double free or
corruption (top): 0x02598130 ***
Status in sane-backends package in Ubuntu:
Incomplete
Status in sane-backends package in Debian:
Fix Released
Bug description:
Similar errors occur when the normal user runs this command
Accessing sacnner using network, setup notes are here
http://ubuntuforums.org/showthread.php?t=1519201
My other virtualbox client has no issue here
the server is running xubuntu 13.04
This output is from the saucy client
www-data@127.0.0.1:/home/www-data/PHP-Scanner-Server$ scanimage -f
"{\"ID\":%i,\"INUSE\":0,\"DEVICE\":\"%d\",\"NAME\":\"%v %m %t\"},"
{"ID":0,"INUSE":0,"DEVICE":"net:10.0.0.50:plustek:libusb:003:002","NAME":"UMAX
3400 flatbed
scanner"},{"ID":1,"INUSE":0,"DEVICE":"net:10.0.0.50:hpaio:/usb/Deskjet_F4400_series?serial=CN05DC61TP05C5","NAME":"Hewlett-Packard
Deskjet_F4400_series all-in-one"},
www-data@127.0.0.1:/home/www-data/PHP-Scanner-Server$ scanimage --help -d
'net:10.0.0.50:plustek:libusb:003:002'
*** Error in `scanimage': double free or corruption (top): 0x02598130
***
=== Backtrace: =
/lib/x86_64-linux-gnu/libc.so.6(+0x80996)[0x7f4379829996]
/lib/x86_64-linux-gnu/libc.so.6(fclose+0x14d)[0x7f43798179bd]
/lib/x86_64-linux-gnu/libnss_files.so.2(_nss_files_getservbyname_r+0x11b)[0x7f4373df7adb]
/lib/x86_64-linux-gnu/libc.so.6(getservbyname_r+0xd2)[0x7f43798bf022]
/lib/x86_64-linux-gnu/libc.so.6(+0xcb72b)[0x7f437987472b]
/lib/x86_64-linux-gnu/libc.so.6(+0xcba93)[0x7f4379874a93]
/lib/x86_64-linux-gnu/libc.so.6(getaddrinfo+0xf4)[0x7f4379878d74]
/usr/lib/x86_64-linux-gnu/sane/libsane-net.so.1(+0x6c3c)[0x7f437939cc3c]
/usr/lib/x86_64-linux-gnu/sane/libsane-net.so.1(sane_net_init+0x428)[0x7f437939d438]
/usr/lib/x86_64-linux-gnu/libsane.so.1(+0x3b00)[0x7f4379b73b00]
/usr/lib/x86_64-linux-gnu/libsane.so.1(sane_dll_open+0xe2)[0x7f4379b74842]
scanimage[0x401fa8]
/lib/x86_64-linux-gnu/libc.so.6(__libc_start_main+0xf5)[0x7f43797cade5]
scanimage[0x403924]
=== Memory map:
0040-0040a000 r-xp 08:01 1355
/usr/bin/scanimage
0060a000-0060b000 r--p a000 08:01 1355
/usr/bin/scanimage
0060b000-0060c000 rw-p b000 08:01 1355
/usr/bin/scanimage
0258d000-025ae000 rw-p 00:00 0
[heap]
7f4373bdd000-7f4373bf2000 r-xp 08:01 1604
/lib/x86_64-linux-gnu/libgcc_s.so.1
7f4373bf2000-7f4373df1000 ---p 00015000 08:01 1604
/lib/x86_64-linux-gnu/libgcc_s.so.1
7f4373df1000-7f4373df2000 r--p 00014000 08:01 1604
/lib/x86_64-linux-gnu/libgcc_s.so.1
7f4373df2000-7f4373df3000 rw-p 00015000 08:01 1604
/lib/x86_64-linux-gnu/libgcc_s.so.1
7f4373df3000-7f4373dff000 r-xp 08:01 1621
/lib/x86_64-linux-gnu/libnss_files-2.17.so
7f4373dff000-7f4373ffe000 ---p c000 08:01 1621
/lib/x86_64-linux-gnu/libnss_files-2.17.so
7f4373ffe000-7f4373fff000 r--p b000 08:01 1621
/lib/x86_64-linux-gnu/libnss_files-2.17.so
7f4373fff000-7f437400 rw-p c000 08:01 1621
/lib/x86_64-linux-gnu/libnss_files-2.17.so
7f437400-7f4374021000 rw-p 00:00 0
7f4374021000-7f437800 ---p 00:00 0
7f437810e000-7f437810f000 ---p 00:00 0
7f437810f000-7f437890f000 rw-p 00:00 0
[stack:17829]
7f437890f000-7f4378916000 r-xp 08:01 1615
/lib/x86_64-linux-gnu/librt-2.17.so
7f4378916000-7f4378b15000 ---p 7000 08:01 1615
/lib/x86_64-linux-gnu/librt-2.17.so
7f4378b15000-7f4378b16000 r--p 6000 08:01 1615
/lib/x86_64-linux-gnu/librt-2.17.so
7f4378b16000-7f4378b17000 rw-p 7000 08:01 1615
/lib/x86_64-linux-gnu/librt-2.17.so
7f4378b17000-7f4378b5b000 r-xp 08:01 5920
/lib/x86_64-linux-gnu/libdbus-1.so.3.7.4
7f4378b5b000-7f4378d5a000 ---p 00044000 08:01 5920
/lib/x86_64-linux-gnu/libdbus-1.so.3.7.4
7f4378d5a000-7f4378d5b000 r--p 00043000 08:01 5920
/lib/x86_64-linux-gnu/libdbus-1.so.3.7.4
7f4378d5b000-7f4378d5c000 rw-p 00044000 08:01 5920
/lib/x86_64-linux-gnu/libdbus-1.so.3.7.4
7f4378d5c000-7f4378d73000 r-xp 08:01 1617
[Desktop-packages] [Bug 1967030] Re: [NUC11PAHi7, Realtek ALC256, Mic, Internal] Behringer 1202USB mixer's default usb audio driver clicks
20.04 After upgrading to 5.13.0-39-generic, the same effect is observed. Bus 002 Device 004: ID 08bb:2902 Texas Instruments PCM2902 Audio Codec fix cat ~/.config/pulse/daemon.conf default-sample-rate = 48000 alternate-sample-rate = 48000 avoid-resampling = no -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to alsa-driver in Ubuntu. https://bugs.launchpad.net/bugs/1967030 Title: [NUC11PAHi7, Realtek ALC256, Mic, Internal] Behringer 1202USB mixer's default usb audio driver clicks Status in alsa-driver package in Ubuntu: New Bug description: maybe pulseaudio, maybe alsa, i don't know. I have a stock kubuntu 21.10 (except for 2 files where i used a "too old" fix that didn't work) Any audio going to my Behringer 1202USB mixer has clicks about 2 per second. That mixer is crackly on startup and shutdown but is new. Could be something to do with powersaving? This is a fresh install of kubuntu on my ibm nuc11i7. I've tried Fedora kde and no repeated clicking. Windows doesn't click. But Fedora kde is junk - can't even connect to github :( Other devices going thru the mixer don't click. Just the usb audio. Other audio devices on kubuntu like hdmi or bluetooth audio work fine. This is maddening :) click click click click... others have the issue too. See... https://www.reddit.com/r/linuxaudio/comments/tko0i6/sudden_issue_with_audio_interface_clicking_at/i2ntx7s/?context=3 please help me :) ProblemType: Bug DistroRelease: Ubuntu 21.10 Package: alsa-base 1.0.25+dfsg-0ubuntu7 ProcVersionSignature: Ubuntu 5.13.0-39.44-generic 5.13.19 Uname: Linux 5.13.0-39-generic x86_64 ApportVersion: 2.20.11-0ubuntu71 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: sh 988 F pulseaudio /dev/snd/controlC2: sh 988 F pulseaudio CasperMD5CheckResult: pass CurrentDesktop: KDE Date: Tue Mar 29 18:54:40 2022 InstallationDate: Installed on 2022-03-27 (2 days ago) InstallationMedia: Kubuntu 21.10 "Impish Indri" - Release amd64 (20211012) PackageArchitecture: all SourcePackage: alsa-driver Symptom: audio Symptom_Card: Built-in Audio - HDA Intel PCH Symptom_Jack: Mic, Internal Symptom_PulseAudioLog: Symptom_Type: Volume slider, or mixer problems Title: [NUC11PAHi7, Realtek ALC256, Mic, Internal] volume slider problem UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 11/13/2020 dmi.bios.release: 0.35 dmi.bios.vendor: Intel Corp. dmi.bios.version: PATGL357.0035.2020.1113.1353 dmi.board.name: NUC11PABi7 dmi.board.vendor: Intel Corporation dmi.board.version: K90104-302 dmi.chassis.type: 35 dmi.chassis.vendor: Intel Corporation dmi.chassis.version: 2.0 dmi.ec.firmware.release: 3.1 dmi.modalias: dmi:bvnIntelCorp.:bvrPATGL357.0035.2020.1113.1353:bd11/13/2020:br0.35:efr3.1:svnIntel(R)ClientSystems:pnNUC11PAHi7:pvrM15513-302:rvnIntelCorporation:rnNUC11PABi7:rvrK90104-302:cvnIntelCorporation:ct35:cvr2.0:skuRNUC11PAHi7000: dmi.product.family: PA dmi.product.name: NUC11PAHi7 dmi.product.sku: RNUC11PAHi7000 dmi.product.version: M15513-302 dmi.sys.vendor: Intel(R) Client Systems 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: 2022-03-27T14:12:12.368562 mtime.conffile..etc.modprobe.d.alsa-base.conf: 2022-03-27T16:41:56.751936 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1967030/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1967488] [NEW] Chromium stable snap don't work on Wayland (NVIDIA 510.60.02 driver)
Public bug reported: Hi I'm testing the Ubuntu 22.04 beta with wayland and when I try to open the Chromium browser (stable snap package), only see a black window. If I switch from Wayland to Xorg, everything is normal again. I tried to delete the profile folder , but I have the same result. ** Affects: chromium-browser (Ubuntu) Importance: Undecided Status: New ** Tags: chromium snap wayland xorg -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to chromium-browser in Ubuntu. https://bugs.launchpad.net/bugs/1967488 Title: Chromium stable snap don't work on Wayland (NVIDIA 510.60.02 driver) Status in chromium-browser package in Ubuntu: New Bug description: Hi I'm testing the Ubuntu 22.04 beta with wayland and when I try to open the Chromium browser (stable snap package), only see a black window. If I switch from Wayland to Xorg, everything is normal again. I tried to delete the profile folder , but I have the same result. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/1967488/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1967109] Re: Xubuntu Docs installed at /usr/share/xubuntu-docs/index.html is not accessible with firefox snap
I submitted an update to the interface: https://github.com/snapcore/snapd/pull/11615 ** Also affects: snapd Importance: Undecided Status: New ** Changed in: snapd Status: New => In Progress ** Changed in: snapd Assignee: (unassigned) => Olivier Tilloy (osomon) -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to firefox in Ubuntu. https://bugs.launchpad.net/bugs/1967109 Title: Xubuntu Docs installed at /usr/share/xubuntu-docs/index.html is not accessible with firefox snap Status in snapd: In Progress Status in firefox package in Ubuntu: Triaged Status in xubuntu-default-settings package in Ubuntu: Triaged Status in firefox source package in Jammy: Triaged Status in xubuntu-default-settings source package in Jammy: Triaged Bug description: Xubuntu's documentation is stored at /usr/share/xubuntu- docs/index.html The firefox snap is not able to access this file. To manage notifications about this bug go to: https://bugs.launchpad.net/snapd/+bug/1967109/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1967485] [NEW] LibreOffice Writer gets stuck
Public bug reported: When editing an odt file (in English & Hebrew) the program often stalls (becomes unresponsive). This is a new bug -- only since a few weeks ago. For years before all was fine. Sometimes the stall is only for a couple of minutes, and then resumes (like right now). At other times I can't even kill it from the system monitor, and must reboot the computer. ProblemType: Bug DistroRelease: Ubuntu 21.10 Package: libreoffice-core 1:7.2.6-0ubuntu0.21.10.1 ProcVersionSignature: Ubuntu 5.13.0-39.44-generic 5.13.19 Uname: Linux 5.13.0-39-generic x86_64 ApportVersion: 2.20.11-0ubuntu71 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: KDE Date: Fri Apr 1 12:37:35 2022 ExecutablePath: /usr/lib/libreoffice/program/soffice.bin InstallationDate: Installed on 2021-06-15 (289 days ago) InstallationMedia: Kubuntu 21.04 "Hirsute Hippo" - Release amd64 (20210420) ProcEnviron: LANGUAGE=en_US:he PATH=(custom, user) XDG_RUNTIME_DIR= LANG=en_IL.UTF-8 SHELL=/bin/bash SourcePackage: libreoffice UpgradeStatus: Upgraded to impish on 2022-01-12 (78 days ago) ** Affects: libreoffice (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug impish -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to libreoffice in Ubuntu. https://bugs.launchpad.net/bugs/1967485 Title: LibreOffice Writer gets stuck Status in libreoffice package in Ubuntu: New Bug description: When editing an odt file (in English & Hebrew) the program often stalls (becomes unresponsive). This is a new bug -- only since a few weeks ago. For years before all was fine. Sometimes the stall is only for a couple of minutes, and then resumes (like right now). At other times I can't even kill it from the system monitor, and must reboot the computer. ProblemType: Bug DistroRelease: Ubuntu 21.10 Package: libreoffice-core 1:7.2.6-0ubuntu0.21.10.1 ProcVersionSignature: Ubuntu 5.13.0-39.44-generic 5.13.19 Uname: Linux 5.13.0-39-generic x86_64 ApportVersion: 2.20.11-0ubuntu71 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: KDE Date: Fri Apr 1 12:37:35 2022 ExecutablePath: /usr/lib/libreoffice/program/soffice.bin InstallationDate: Installed on 2021-06-15 (289 days ago) InstallationMedia: Kubuntu 21.04 "Hirsute Hippo" - Release amd64 (20210420) ProcEnviron: LANGUAGE=en_US:he PATH=(custom, user) XDG_RUNTIME_DIR= LANG=en_IL.UTF-8 SHELL=/bin/bash SourcePackage: libreoffice UpgradeStatus: Upgraded to impish on 2022-01-12 (78 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libreoffice/+bug/1967485/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1966930] Re: Cannot drag tabs with mouse
*** This bug is a duplicate of bug 1964541 ***
https://bugs.launchpad.net/bugs/1964541
Status changed to 'Confirmed' because the bug affects multiple users.
** Changed in: firefox (Ubuntu)
Status: New => Confirmed
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to firefox in Ubuntu.
https://bugs.launchpad.net/bugs/1966930
Title:
Cannot drag tabs with mouse
Status in firefox package in Ubuntu:
Confirmed
Bug description:
When testing firefox 98.0.2 from the snap on the Ubuntu for Raspberry
Pi pre-installed desktop image (using Wayland), I noted that I'm
unable to drag'n'drop tabs to re-order them, or detach them into
separate windows. I can re-order tabs with the Ctrl+Shift+Pg{Up,Dn}
keyboard short-cuts, but not with the mouse.
This occurred both in the default configuration (with tabs in the
title bar's area), and in my preferred configuration (with the title
bar displayed above the tabs bar).
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/firefox/+bug/1966930/+subscriptions
--
Mailing list: https://launchpad.net/~desktop-packages
Post to : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-packages
More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1967480] Re: GUI error in "compress file". Menu content is wider than menu window.
Thanks, indeed that was also reported in https://gitlab.gnome.org/GNOME/nautilus/-/issues/2018 and is fixed upstream now and will be in the 42.1 update https://gitlab.gnome.org/GNOME/nautilus/-/commit/441124cf ** Bug watch added: gitlab.gnome.org/GNOME/nautilus/-/issues #2018 https://gitlab.gnome.org/GNOME/nautilus/-/issues/2018 ** Changed in: nautilus (Ubuntu) Importance: Undecided => Low ** Changed in: nautilus (Ubuntu) Status: New => Fix Committed -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to nautilus in Ubuntu. https://bugs.launchpad.net/bugs/1967480 Title: GUI error in "compress file". Menu content is wider than menu window. Status in nautilus package in Ubuntu: Fix Committed Bug description: When I click "compress.." from Nautilus, the menu that allows to change compression format is obscured (screen attached) Description: Ubuntu Jammy Jellyfish (development branch) Release: 22.04 ii gnome-sushi 41.0-3 amd64sushi is a quick previewer for nautilus ii libnautilus-extension1a:amd64 1:42.0-1ubuntu2 amd64libraries for nautilus components - runtime version ii nautilus 1:42.0-1ubuntu2 amd64file manager and graphical shell for GNOME ii nautilus-data 1:42.0-1ubuntu2 all data files for nautilus ii nautilus-extension-gnome-terminal 3.44.0-1ubuntu1 amd64GNOME terminal emulator application - Nautilus extension ii nautilus-sendto 3.8.6-4 amd64easily send files via email from within Nautilus ii nautilus-share0.7.3-2ubuntu5 amd64Nautilus extension to share folder using Samba ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: nautilus 1:42.0-1ubuntu2 ProcVersionSignature: Ubuntu 5.15.0-23.23-generic 5.15.27 Uname: Linux 5.15.0-23-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu80 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: ubuntu:GNOME Date: Fri Apr 1 10:43:11 2022 RebootRequiredPkgs: Error: path contained symlinks. SourcePackage: nautilus UpgradeStatus: Upgraded to jammy on 2022-03-19 (13 days ago) modified.conffile..etc.apport.crashdb.conf: [modified] mtime.conffile..etc.apport.crashdb.conf: 2021-05-03T18:07:38.595923 usr_lib_nautilus: evince42.1-1 file-roller 3.42.0-1 nautilus-extension-gnome-terminal 3.44.0-1ubuntu1 nautilus-share0.7.3-2ubuntu5 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nautilus/+bug/1967480/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1966808] Re: [amdgpu][radeon] gnome-shell Wayland sessions fail to start (Failed to lock front buffer on /dev/dri/card1: drmModeAddFB2WithModifiers failed: Invalid argument)
I installed 22.04 today on a machine with an AMD GPU. I have libmutter-10-0 42.0-1ubuntu1 and I still encountered the problem. Setting MUTTER_DEBUG_USE_KMS_MODIFIERS=0 is still necessary in 42.0-1ubuntu1. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-shell in Ubuntu. https://bugs.launchpad.net/bugs/1966808 Title: [amdgpu][radeon] gnome-shell Wayland sessions fail to start (Failed to lock front buffer on /dev/dri/card1: drmModeAddFB2WithModifiers failed: Invalid argument) Status in gnome-shell package in Ubuntu: Triaged Status in mutter package in Ubuntu: Triaged Bug description: Wayland started crashing for me on upgrade to Jammy, which I'm aware is currently in alpha. gdm was crashing, and changing to lightdm addressed this issue. If I select 'Ubuntu on Xorg' - I can login without problems. If I select Wayland instead, I just get a black screen, and I have to kill gnome-session from a virtual console. ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: gnome-shell 42~beta-1ubuntu3 ProcVersionSignature: Ubuntu 5.15.0-23.23-generic 5.15.27 Uname: Linux 5.15.0-23-generic x86_64 ApportVersion: 2.20.11-0ubuntu79 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Mon Mar 28 15:23:51 2022 DisplayManager: lightdm InstallationDate: Installed on 2022-03-19 (9 days ago) InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Alpha amd64 (20220318) RelatedPackageVersions: mutter-common 42~beta-1ubuntu2 SourcePackage: gnome-shell UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1966808/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1967480] [NEW] GUI error in "compress file". Menu content is wider than menu window.
Public bug reported: When I click "compress.." from Nautilus, the menu that allows to change compression format is obscured (screen attached) Description:Ubuntu Jammy Jellyfish (development branch) Release:22.04 ii gnome-sushi 41.0-3 amd64sushi is a quick previewer for nautilus ii libnautilus-extension1a:amd64 1:42.0-1ubuntu2 amd64libraries for nautilus components - runtime version ii nautilus 1:42.0-1ubuntu2 amd64file manager and graphical shell for GNOME ii nautilus-data 1:42.0-1ubuntu2 all data files for nautilus ii nautilus-extension-gnome-terminal 3.44.0-1ubuntu1 amd64GNOME terminal emulator application - Nautilus extension ii nautilus-sendto 3.8.6-4 amd64easily send files via email from within Nautilus ii nautilus-share0.7.3-2ubuntu5 amd64Nautilus extension to share folder using Samba ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: nautilus 1:42.0-1ubuntu2 ProcVersionSignature: Ubuntu 5.15.0-23.23-generic 5.15.27 Uname: Linux 5.15.0-23-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu80 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: ubuntu:GNOME Date: Fri Apr 1 10:43:11 2022 RebootRequiredPkgs: Error: path contained symlinks. SourcePackage: nautilus UpgradeStatus: Upgraded to jammy on 2022-03-19 (13 days ago) modified.conffile..etc.apport.crashdb.conf: [modified] mtime.conffile..etc.apport.crashdb.conf: 2021-05-03T18:07:38.595923 usr_lib_nautilus: evince42.1-1 file-roller 3.42.0-1 nautilus-extension-gnome-terminal 3.44.0-1ubuntu1 nautilus-share0.7.3-2ubuntu5 ** Affects: nautilus (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug jammy third-party-packages ** Attachment added: "Screenshot from 2022-04-01 10-41-07.png" https://bugs.launchpad.net/bugs/1967480/+attachment/5575557/+files/Screenshot%20from%202022-04-01%2010-41-07.png -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to nautilus in Ubuntu. https://bugs.launchpad.net/bugs/1967480 Title: GUI error in "compress file". Menu content is wider than menu window. Status in nautilus package in Ubuntu: New Bug description: When I click "compress.." from Nautilus, the menu that allows to change compression format is obscured (screen attached) Description: Ubuntu Jammy Jellyfish (development branch) Release: 22.04 ii gnome-sushi 41.0-3 amd64sushi is a quick previewer for nautilus ii libnautilus-extension1a:amd64 1:42.0-1ubuntu2 amd64libraries for nautilus components - runtime version ii nautilus 1:42.0-1ubuntu2 amd64file manager and graphical shell for GNOME ii nautilus-data 1:42.0-1ubuntu2 all data files for nautilus ii nautilus-extension-gnome-terminal 3.44.0-1ubuntu1 amd64GNOME terminal emulator application - Nautilus extension ii nautilus-sendto 3.8.6-4 amd64easily send files via email from within Nautilus ii nautilus-share0.7.3-2ubuntu5 amd64Nautilus extension to share folder using Samba ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: nautilus 1:42.0-1ubuntu2 ProcVersionSignature: Ubuntu 5.15.0-23.23-generic 5.15.27 Uname: Linux 5.15.0-23-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu80 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: ubuntu:GNOME Date: Fri Apr 1 10:43:11 2022 RebootRequiredPkgs: Error: path contained symlinks. SourcePackage: nautilus UpgradeStatus: Upgraded to jammy on 2022-03-19 (13 days ago) modified.conffile..etc.apport.crashdb.conf: [modified] mtime.conffile..etc.apport.crashdb.conf: 2021-05-03T18:07:38.595923 usr_lib_nautilus: evince42.1-1 file-roller 3.42.0-1 nautilus-extension-gnome-terminal 3.44.0-1ubuntu1 nautilus-share0.7.3-2ubuntu5 To
[Desktop-packages] [Bug 1967456] Re: Jammy didn't use nvidia driver when executing firefox
I just filed lp:1967478 before finding this issue... There might be additional information there. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to firefox in Ubuntu. https://bugs.launchpad.net/bugs/1967456 Title: Jammy didn't use nvidia driver when executing firefox Status in firefox package in Ubuntu: Confirmed Bug description: [Reproduce step] 1. Install Jammy beta. 2. Install Nvidia driver by ubuntu-driver install. 3. Connect monitor to dGPU output port. 4. Run firefox, type "about:support" in url, and check column "GPU #1" [Expected result] should see nvidia driver info. [Actual result] still use llvmpipe [Info] OS version: Ubuntu Jammy Jellyfish (development branch) Device: HP Z2 Mini G5 workstation CID: 202008-28179 Wayland in use. ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: linux-image-5.15.0-23-generic 5.15.0-23.23 ProcVersionSignature: Ubuntu 5.15.0-23.23-generic 5.15.27 Uname: Linux 5.15.0-23-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu79 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: u 1186 F pulseaudio /dev/snd/controlC1: u 1186 F pulseaudio CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Fri Apr 1 00:07:47 2022 InstallationDate: Installed on 2022-04-01 (0 days ago) InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Beta amd64 (20220329.1) MachineType: HP HP Z2 Mini G5 Workstation ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcFB: 0 EFI VGA ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.15.0-23-generic root=UUID=adaf5521-655d-454a-9bad-ef17619a51f2 ro quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-5.15.0-23-generic N/A linux-backports-modules-5.15.0-23-generic N/A linux-firmware 20220314.gitcd01f857-0ubuntu2 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 07/02/2020 dmi.bios.release: 0.1 dmi.bios.vendor: HP dmi.bios.version: S50 Ver. 01.00.01 dmi.board.name: 8754 dmi.board.vendor: HP dmi.board.version: KBC Version 09.08.03 dmi.chassis.type: 2 dmi.chassis.vendor: HP dmi.ec.firmware.release: 9.8 dmi.modalias: dmi:bvnHP:bvrS50Ver.01.00.01:bd07/02/2020:br0.1:efr9.8:svnHP:pnHPZ2MiniG5Workstation:pvr:rvnHP:rn8754:rvrKBCVersion09.08.03:cvnHP:ct2:cvr:sku9JD38AV: dmi.product.family: 103C_53335X HP Workstation dmi.product.name: HP Z2 Mini G5 Workstation dmi.product.sku: 9JD38AV dmi.sys.vendor: HP To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/firefox/+bug/1967456/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1967478] Re: Discrete GPU is not used even when using "Launch using dedicated graphics card" option
*** This bug is a duplicate of bug 1967456 ***
https://bugs.launchpad.net/bugs/1967456
** Summary changed:
- Dsicrete GPU is not used even when using "Launch using dedicated graphics
card" option
+ Discrete GPU is not used even when using "Launch using dedicated graphics
card" option
** This bug has been marked a duplicate of bug 1967456
Jammy didn't use nvidia driver when executing firefox
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to firefox in Ubuntu.
https://bugs.launchpad.net/bugs/1967478
Title:
Discrete GPU is not used even when using "Launch using dedicated
graphics card" option
Status in firefox package in Ubuntu:
New
Bug description:
Image: 22.04 beta
Device: Dell Precision 7760 (with NVIDIA Corporation GA104GLM [RTX A5000
Mobile] GPU)
Desktop: GNOME running Wayland
Firefox snap: 98.0.2-1 (1154)
Summary
===
Firefox, a snap application, does not see the Discrete GPU, even when
run using the appropriate option ("Launch using Discrete Graphics
Card"). The problem does not seem to happen with non-snap
applications.
Steps to reproduce
==
1. Install 22.04 beta image using third party software (nvidia proprietary
drivers)
2. Launch Firefox by left-clicking on the icon
3. Go to about:support, and check the GPU information
4. Close Firefox
5. Right click on Firefox icon, and select "Launch using Discrete Graphics
Card"
6. Repeat step 3
Expected result
===
In step 3, the Active GPU should be the Integrated GPU (in my case, Intel).
In step 6, the Active GPU should be the Discrete GPU (in my case, Nvidia).
Actual result
=
In both step 3 and step 6, the active GPU is the integrated one:
Graphics
GPU #1
Active: Yes
Description: Mesa Intel(R) UHD Graphics (TGL GT1)
Vendor ID: 0x8086
Device ID: 0x9a70
Driver Vendor: mesa/iris
Driver Version: 21.0.3.0
RAM: 0
GPU #2
Active: No
Vendor ID: 0x10de
Device ID: 0x24b6
It might be a snap problem, because if I run the same test with a non-snap
application (e.g. Terminal), it works as expected:
1. Open the terminal application, and run (you may have to install
mesa-utils package):
$ glxinfo | grep "OpenGL vendor"
OpenGL vendor string: Intel
2. Close the terminal, right click on its icon, select "Launch using
Discrete Graphics Card" and repeat step 1:
$ glxinfo | grep "OpenGL vendor"
OpenGL vendor string: NVIDIA Corporation
ProblemType: Bug
DistroRelease: Ubuntu 22.04
Package: firefox 1:1snap1-0ubuntu2
ProcVersionSignature: Ubuntu 5.15.0-23.23-generic 5.15.27
Uname: Linux 5.15.0-23-generic x86_64
NonfreeKernelModules: nvidia_modeset nvidia
ApportVersion: 2.20.11-0ubuntu80
Architecture: amd64
CasperMD5CheckResult: pass
CurrentDesktop: ubuntu:GNOME
Date: Fri Apr 1 15:46:39 2022
InstallationDate: Installed on 2022-04-01 (0 days ago)
InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Beta amd64
(20220329.1)
Snap.Changes: no changes found
SourcePackage: firefox
UpgradeStatus: No upgrade log present (probably fresh install)
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/firefox/+bug/1967478/+subscriptions
--
Mailing list: https://launchpad.net/~desktop-packages
Post to : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-packages
More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1966317] Re: gvfsd-fuse crashed with SIGABRT in __pthread_setname_np()
it's probably a consequence of bug #1962036, seems dbus is going down on update taking the graphical session with it -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gvfs in Ubuntu. https://bugs.launchpad.net/bugs/1966317 Title: gvfsd-fuse crashed with SIGABRT in __pthread_setname_np() Status in gvfs package in Ubuntu: Confirmed Bug description: I encountered this crash during a dist-upgrade from impish to jammy, i.e. running `do-release-upgrade --devel-release`. My desktop session crashed, and my VM can no longer boot the desktop (but I can ssh still). ProblemType: Crash DistroRelease: Ubuntu 21.10 Package: gvfs-fuse 1.47.91-1ubuntu1 ProcVersionSignature: Ubuntu 5.13.0-28.31-generic 5.13.19 Uname: Linux 5.13.0-28-generic x86_64 ApportVersion: 2.20.11-0ubuntu71 Architecture: amd64 CasperMD5CheckMismatches: ./boot/grub/grub.cfg CasperMD5CheckResult: fail Date: Thu Mar 24 12:10:04 2022 ExecutablePath: /usr/libexec/gvfsd-fuse ExecutableTimestamp: 1615801987 InstallationDate: Installed on 2022-02-02 (49 days ago) InstallationMedia: Ubuntu 21.10 "Impish Indri" - Release amd64 (20211012) ProcCmdline: /usr/libexec/gvfsd-fuse /run/user/1000/gvfs -f -o big_writes ProcCwd: /home/nr ProcEnviron: LANG=en_US.UTF-8 PATH=(custom, no user) SHELL=/bin/bash XDG_RUNTIME_DIR= Signal: 6 SourcePackage: gvfs StacktraceTop: __pthread_setname_np (th=1251, name=0x6 ) at ./nptl/pthread_setname.c:32 ?? () Title: gvfsd-fuse crashed with SIGABRT in __pthread_setname_np() UpgradeStatus: Upgraded to impish on 2022-03-24 (0 days ago) UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo separator: To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gvfs/+bug/1966317/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1967478] Re: Dsicrete GPU is not used even when using "Launch using dedicated graphics card" option
More logs coming from sosreport.
** Attachment added: "sosreport-u-Precision-7760-2022-04-01-jgighrk.tar.xz"
https://bugs.launchpad.net/ubuntu/+source/firefox/+bug/1967478/+attachment/5575550/+files/sosreport-u-Precision-7760-2022-04-01-jgighrk.tar.xz
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to firefox in Ubuntu.
https://bugs.launchpad.net/bugs/1967478
Title:
Dsicrete GPU is not used even when using "Launch using dedicated
graphics card" option
Status in firefox package in Ubuntu:
New
Bug description:
Image: 22.04 beta
Device: Dell Precision 7760 (with NVIDIA Corporation GA104GLM [RTX A5000
Mobile] GPU)
Desktop: GNOME running Wayland
Firefox snap: 98.0.2-1 (1154)
Summary
===
Firefox, a snap application, does not see the Discrete GPU, even when
run using the appropriate option ("Launch using Discrete Graphics
Card"). The problem does not seem to happen with non-snap
applications.
Steps to reproduce
==
1. Install 22.04 beta image using third party software (nvidia proprietary
drivers)
2. Launch Firefox by left-clicking on the icon
3. Go to about:support, and check the GPU information
4. Close Firefox
5. Right click on Firefox icon, and select "Launch using Discrete Graphics
Card"
6. Repeat step 3
Expected result
===
In step 3, the Active GPU should be the Integrated GPU (in my case, Intel).
In step 6, the Active GPU should be the Discrete GPU (in my case, Nvidia).
Actual result
=
In both step 3 and step 6, the active GPU is the integrated one:
Graphics
GPU #1
Active: Yes
Description: Mesa Intel(R) UHD Graphics (TGL GT1)
Vendor ID: 0x8086
Device ID: 0x9a70
Driver Vendor: mesa/iris
Driver Version: 21.0.3.0
RAM: 0
GPU #2
Active: No
Vendor ID: 0x10de
Device ID: 0x24b6
It might be a snap problem, because if I run the same test with a non-snap
application (e.g. Terminal), it works as expected:
1. Open the terminal application, and run (you may have to install
mesa-utils package):
$ glxinfo | grep "OpenGL vendor"
OpenGL vendor string: Intel
2. Close the terminal, right click on its icon, select "Launch using
Discrete Graphics Card" and repeat step 1:
$ glxinfo | grep "OpenGL vendor"
OpenGL vendor string: NVIDIA Corporation
ProblemType: Bug
DistroRelease: Ubuntu 22.04
Package: firefox 1:1snap1-0ubuntu2
ProcVersionSignature: Ubuntu 5.15.0-23.23-generic 5.15.27
Uname: Linux 5.15.0-23-generic x86_64
NonfreeKernelModules: nvidia_modeset nvidia
ApportVersion: 2.20.11-0ubuntu80
Architecture: amd64
CasperMD5CheckResult: pass
CurrentDesktop: ubuntu:GNOME
Date: Fri Apr 1 15:46:39 2022
InstallationDate: Installed on 2022-04-01 (0 days ago)
InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Beta amd64
(20220329.1)
Snap.Changes: no changes found
SourcePackage: firefox
UpgradeStatus: No upgrade log present (probably fresh install)
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/firefox/+bug/1967478/+subscriptions
--
Mailing list: https://launchpad.net/~desktop-packages
Post to : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-packages
More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1967478] [NEW] Dsicrete GPU is not used even when using "Launch using dedicated graphics card" option
Public bug reported:
Image: 22.04 beta
Device: Dell Precision 7760 (with NVIDIA Corporation GA104GLM [RTX A5000
Mobile] GPU)
Desktop: GNOME running Wayland
Firefox snap: 98.0.2-1 (1154)
Summary
===
Firefox, a snap application, does not see the Discrete GPU, even when
run using the appropriate option ("Launch using Discrete Graphics
Card"). The problem does not seem to happen with non-snap applications.
Steps to reproduce
==
1. Install 22.04 beta image using third party software (nvidia proprietary
drivers)
2. Launch Firefox by left-clicking on the icon
3. Go to about:support, and check the GPU information
4. Close Firefox
5. Right click on Firefox icon, and select "Launch using Discrete Graphics Card"
6. Repeat step 3
Expected result
===
In step 3, the Active GPU should be the Integrated GPU (in my case, Intel).
In step 6, the Active GPU should be the Discrete GPU (in my case, Nvidia).
Actual result
=
In both step 3 and step 6, the active GPU is the integrated one:
Graphics
GPU #1
Active: Yes
Description: Mesa Intel(R) UHD Graphics (TGL GT1)
Vendor ID: 0x8086
Device ID: 0x9a70
Driver Vendor: mesa/iris
Driver Version: 21.0.3.0
RAM: 0
GPU #2
Active: No
Vendor ID: 0x10de
Device ID: 0x24b6
It might be a snap problem, because if I run the same test with a non-snap
application (e.g. Terminal), it works as expected:
1. Open the terminal application, and run (you may have to install mesa-
utils package):
$ glxinfo | grep "OpenGL vendor"
OpenGL vendor string: Intel
2. Close the terminal, right click on its icon, select "Launch using
Discrete Graphics Card" and repeat step 1:
$ glxinfo | grep "OpenGL vendor"
OpenGL vendor string: NVIDIA Corporation
ProblemType: Bug
DistroRelease: Ubuntu 22.04
Package: firefox 1:1snap1-0ubuntu2
ProcVersionSignature: Ubuntu 5.15.0-23.23-generic 5.15.27
Uname: Linux 5.15.0-23-generic x86_64
NonfreeKernelModules: nvidia_modeset nvidia
ApportVersion: 2.20.11-0ubuntu80
Architecture: amd64
CasperMD5CheckResult: pass
CurrentDesktop: ubuntu:GNOME
Date: Fri Apr 1 15:46:39 2022
InstallationDate: Installed on 2022-04-01 (0 days ago)
InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Beta amd64 (20220329.1)
Snap.Changes: no changes found
SourcePackage: firefox
UpgradeStatus: No upgrade log present (probably fresh install)
** Affects: firefox (Ubuntu)
Importance: Undecided
Status: New
** Tags: amd64 apport-bug jammy wayland-session
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to firefox in Ubuntu.
https://bugs.launchpad.net/bugs/1967478
Title:
Dsicrete GPU is not used even when using "Launch using dedicated
graphics card" option
Status in firefox package in Ubuntu:
New
Bug description:
Image: 22.04 beta
Device: Dell Precision 7760 (with NVIDIA Corporation GA104GLM [RTX A5000
Mobile] GPU)
Desktop: GNOME running Wayland
Firefox snap: 98.0.2-1 (1154)
Summary
===
Firefox, a snap application, does not see the Discrete GPU, even when
run using the appropriate option ("Launch using Discrete Graphics
Card"). The problem does not seem to happen with non-snap
applications.
Steps to reproduce
==
1. Install 22.04 beta image using third party software (nvidia proprietary
drivers)
2. Launch Firefox by left-clicking on the icon
3. Go to about:support, and check the GPU information
4. Close Firefox
5. Right click on Firefox icon, and select "Launch using Discrete Graphics
Card"
6. Repeat step 3
Expected result
===
In step 3, the Active GPU should be the Integrated GPU (in my case, Intel).
In step 6, the Active GPU should be the Discrete GPU (in my case, Nvidia).
Actual result
=
In both step 3 and step 6, the active GPU is the integrated one:
Graphics
GPU #1
Active: Yes
Description: Mesa Intel(R) UHD Graphics (TGL GT1)
Vendor ID: 0x8086
Device ID: 0x9a70
Driver Vendor: mesa/iris
Driver Version: 21.0.3.0
RAM: 0
GPU #2
Active: No
Vendor ID: 0x10de
Device ID: 0x24b6
It might be a snap problem, because if I run the same test with a non-snap
application (e.g. Terminal), it works as expected:
1. Open the terminal application, and run (you may have to install
mesa-utils package):
$ glxinfo | grep "OpenGL vendor"
OpenGL vendor string: Intel
2. Close the terminal, right click on its icon, select "Launch using
Discrete Graphics Card" and repeat step 1:
$ glxinfo | grep "OpenGL vendor"
OpenGL vendor string: NVIDIA Corporation
ProblemType: Bug
DistroRelease: Ubuntu 22.04
Package: firefox 1:1snap1-0ubuntu2
ProcVersionSignature: Ubuntu 5.15.0-23.23-generic 5.15.27
Uname: Linux 5.15.0-23-generic x86_64
NonfreeKernelModules: nvidia_modeset nvidia
ApportVersion: 2.20.11-0ubuntu80
Architecture: amd64
CasperMD5CheckResult: pass
CurrentDesktop: ubuntu:GNOME
Date:
[Desktop-packages] [Bug 1963836] Re: package pipewire-pulse 0.3.47-3~ubuntu22.04 failed to install/upgrade: trying to overwrite '/usr/share/man/man1/pipewire-pulse.1.gz', which is also in package pipe
This is a packaging bug with pipewire-pulse and pipewire-bin from the PPA, not with official packages. Please report it to the PPA maintainer. The manpage should be installed in pipewire-pulse where the related bin is, not in pipewire-bin. ** Changed in: pipewire (Ubuntu) Status: New => Invalid -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to pipewire in Ubuntu. https://bugs.launchpad.net/bugs/1963836 Title: package pipewire-pulse 0.3.47-3~ubuntu22.04 failed to install/upgrade: trying to overwrite '/usr/share/man/man1/pipewire-pulse.1.gz', which is also in package pipewire-bin 0.3.47-3~ubuntu22.04 Status in pipewire package in Ubuntu: Invalid Bug description: Description: Ubuntu Jammy Jellyfish (development branch) Release: 22.04 pipewire-pulse: Installed: 0.3.47-3~ubuntu22.04 Candidate: 0.3.48-1ubuntu1 Version table: 0.3.48-1ubuntu1 500 500 http://it.archive.ubuntu.com/ubuntu jammy/universe amd64 Packages *** 0.3.47-3~ubuntu22.04 500 500 http://ppa.launchpad.net/pipewire-debian/pipewire-upstream/ubuntu jammy/main amd64 Packages 100 /var/lib/dpkg/status ProblemType: Package DistroRelease: Ubuntu 22.04 Package: pipewire-pulse 0.3.47-3~ubuntu22.04 ProcVersionSignature: Ubuntu 5.15.0-18.18-generic 5.15.12 Uname: Linux 5.15.0-18-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu78 Architecture: amd64 CasperMD5CheckResult: pass Date: Sun Mar 6 20:05:39 2022 DpkgTerminalLog: Preparing to unpack .../00-pipewire-pulse_0.3.48-1ubuntu1_amd64.deb ... Unpacking pipewire-pulse (0.3.48-1ubuntu1) over (0.3.47-3~ubuntu22.04) ... dpkg: error processing archive /tmp/apt-dpkg-install-tiBpp8/00-pipewire-pulse_0.3.48-1ubuntu1_amd64.deb (--unpack): trying to overwrite '/usr/share/man/man1/pipewire-pulse.1.gz', which is also in package pipewire-bin 0.3.47-3~ubuntu22.04 DuplicateSignature: package:pipewire-pulse:0.3.47-3~ubuntu22.04 Unpacking pipewire-pulse (0.3.48-1ubuntu1) over (0.3.47-3~ubuntu22.04) ... dpkg: error processing archive /tmp/apt-dpkg-install-tiBpp8/00-pipewire-pulse_0.3.48-1ubuntu1_amd64.deb (--unpack): trying to overwrite '/usr/share/man/man1/pipewire-pulse.1.gz', which is also in package pipewire-bin 0.3.47-3~ubuntu22.04 ErrorMessage: trying to overwrite '/usr/share/man/man1/pipewire-pulse.1.gz', which is also in package pipewire-bin 0.3.47-3~ubuntu22.04 InstallationDate: Installed on 2022-02-13 (20 days ago) InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Alpha amd64 (20220116) Python3Details: /usr/bin/python3.10, Python 3.10.2, python3-minimal, 3.10.1-0ubuntu1 PythonDetails: N/A RelatedPackageVersions: dpkg 1.21.1ubuntu1 apt 2.3.15build1 SourcePackage: pipewire Title: package pipewire-pulse 0.3.47-3~ubuntu22.04 failed to install/upgrade: trying to overwrite '/usr/share/man/man1/pipewire-pulse.1.gz', which is also in package pipewire-bin 0.3.47-3~ubuntu22.04 UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/pipewire/+bug/1963836/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1967471] Re: Artifacts when any window is being minimized to tray (on the second or more tries)
Please also run: lspci -k > lspci.txt journalctl -b0 > journal.txt and attach the resulting text files here. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-shell in Ubuntu. https://bugs.launchpad.net/bugs/1967471 Title: Artifacts when any window is being minimized to tray (on the second or more tries) Status in gnome-shell package in Ubuntu: Incomplete Bug description: sudo update and sudo apt full-upgrade have been performed as well. Video screen has been attached ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: gnome-shell 42.0-1ubuntu1 ProcVersionSignature: Ubuntu 5.15.0-23.23-generic 5.15.27 Uname: Linux 5.15.0-23-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.20.11-0ubuntu80 Architecture: amd64 CasperMD5CheckResult: pass CasperVersion: 1.468 CurrentDesktop: ubuntu:GNOME Date: Fri Apr 1 07:36:46 2022 DisplayManager: gdm3 LiveMediaBuild: Ubuntu 22.04 LTS "Jammy Jellyfish" - Beta amd64 (20220329.1) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=ru_RU.UTF-8 SHELL=/bin/bash RebootRequiredPkgs: Error: path contained symlinks. RelatedPackageVersions: mutter-common 42.0-1ubuntu1 SourcePackage: gnome-shell UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1967471/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1967471] Re: Artifacts when any window is being minimized to tray (on the second or more tries)
Please attach the video again using simple Latin lettering (Launchpad can't handle Cyrillic filenames). ** Changed in: gnome-shell (Ubuntu) Status: New => Incomplete -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-shell in Ubuntu. https://bugs.launchpad.net/bugs/1967471 Title: Artifacts when any window is being minimized to tray (on the second or more tries) Status in gnome-shell package in Ubuntu: Incomplete Bug description: sudo update and sudo apt full-upgrade have been performed as well. Video screen has been attached ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: gnome-shell 42.0-1ubuntu1 ProcVersionSignature: Ubuntu 5.15.0-23.23-generic 5.15.27 Uname: Linux 5.15.0-23-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.20.11-0ubuntu80 Architecture: amd64 CasperMD5CheckResult: pass CasperVersion: 1.468 CurrentDesktop: ubuntu:GNOME Date: Fri Apr 1 07:36:46 2022 DisplayManager: gdm3 LiveMediaBuild: Ubuntu 22.04 LTS "Jammy Jellyfish" - Beta amd64 (20220329.1) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=ru_RU.UTF-8 SHELL=/bin/bash RebootRequiredPkgs: Error: path contained symlinks. RelatedPackageVersions: mutter-common 42.0-1ubuntu1 SourcePackage: gnome-shell UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1967471/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1967290] Re: USB Kyb and Mouse hangs "Suspend" ?
It sounds like gnome-shell (or something) has frozen or crashed, not so much a problem with the peripherals. Please: 1. Run this command to collect more system info: apport-collect 1967290 2. Follow these instructions to check for crashes: https://wiki.ubuntu.com/Bugs/Responses#Missing_a_crash_report_or_having_a_.crash_attachment ** Package changed: gnome-session (Ubuntu) => gnome-shell (Ubuntu) ** Changed in: gnome-shell (Ubuntu) Status: New => Incomplete -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-shell in Ubuntu. https://bugs.launchpad.net/bugs/1967290 Title: USB Kyb and Mouse hangs "Suspend" ? Status in gnome-shell package in Ubuntu: Incomplete Bug description: Hi, My email is: zolt...@geograph.co.za My system is: root@gs00:/home/geograph# uname -a Linux gs00 5.15.0-23-generic #23-Ubuntu SMP Fri Mar 11 14:54:05 UTC 2022 x86_64 x86_64 x86_64 GNU/Linux I update this beta sometime twice per day, and this problem persists. I have 1 monitor with 2 inputs. One input is dedicated to my laptop and the other to this jammy system. I have separate USB Kyb/Mouse HW connected directly to each of these computers (so they are never disconnected). I have my power settings set to never logout/lockscreen etc. and I can leave the system for long periods with no typing or mouse movements as long as I do not switch the monitor input away from jammy. If I switch the monitor over to get signal from the laptop and then some time later switch it back to the jammy desktop, I find that the Kyb/Mouse connected to jammy is non-active even though the Kyb & Mouse lights are on. I have tried replugging the Kyb/Mouse. I have to reboot the system to get control of its Kyb & Mouse. I do get lots of these messages in syslog (so suspect a GDK problem). Thanks and regards, Zoltan. Mar 31 14:46:06 gs00 gnome-shell[3873]: message repeated 3 times: [ DING: (gjs:578106): Gdk-CRITICAL **: 14:46:06.187: gdk_monitor_get_scale_factor: assertion 'GDK_IS_MONITOR (monitor)' failed] Mar 31 14:46:06 gs00 gnome-shell[3873]: DING: (gjs:578106): Gdk-CRITICAL **: 14:46:06.194: gdk_monitor_get_workarea: assertion 'GDK_IS_MONITOR (monitor)' failed Mar 31 14:46:06 gs00 gnome-shell[3873]: DING: GNOME nautilus 42.0 Mar 31 14:46:06 gs00 gnome-shell[3873]: DING: (gjs:578106): Gdk-CRITICAL **: 14:46:06.208: gdk_monitor_get_workarea: assertion 'GDK_IS_MONITOR (monitor)' failed Mar 31 14:46:07 gs00 gnome-shell[3873]: DING: (gjs:578106): Gdk-CRITICAL **: 14:46:07.215: gdk_monitor_get_scale_factor: assertion 'GDK_IS_MONITOR (monitor)' failed Mar 31 14:46:07 gs00 gnome-shell[3873]: message repeated 8 times: [ DING: (gjs:578106): Gdk-CRITICAL **: 14:46:07.215: gdk_monitor_get_scale_factor: assertion 'GDK_IS_MONITOR (monitor)' failed] Mar 31 14:46:07 gs00 gnome-shell[3873]: DING: (gjs:578106): Gdk-CRITICAL **: 14:46:07.216: gdk_monitor_get_scale_factor: assertion 'GDK_IS_MONITOR (monitor)' failed Mar 31 14:46:07 gs00 gnome-shell[3873]: message repeated 30 times: [ DING: (gjs:578106): Gdk-CRITICAL **: 14:46:07.216: gdk_monitor_get_scale_factor: assertion 'GDK_IS_MONITOR (monitor)' failed] Mar 31 14:46:07 gs00 gnome-shell[3873]: DING: (gjs:578106): Gdk-CRITICAL **: 14:46:07.217: gdk_monitor_get_scale_factor: assertion 'GDK_IS_MONITOR (monitor)' failed Mar 31 14:46:07 gs00 gnome-shell[3873]: message repeated 39 times: [ DING: (gjs:578106): Gdk-CRITICAL **: 14:46:07.217: gdk_monitor_get_scale_factor: assertion 'GDK_IS_MONITOR (monitor)' failed] Mar 31 14:46:07 gs00 gnome-shell[3873]: DING: (gjs:578106): Gdk-CRITICAL **: 14:46:07.218: gdk_monitor_get_scale_factor: assertion 'GDK_IS_MONITOR (monitor)' failed Mar 31 14:46:07 gs00 gnome-shell[3873]: message repeated 2 times: [ DING: (gjs:578106): Gdk-CRITICAL **: 14:46:07.218: gdk_monitor_get_scale_factor: assertion 'GDK_IS_MONITOR (monitor)' failed] Mar 31 14:46:07 gs00 gnome-shell[3873]: DING: Not enough space to add icons Mar 31 14:46:07 gs00 gnome-shell[3873]: DING: (gjs:578106): Gdk-CRITICAL **: 14:46:07.223: gdk_monitor_get_scale_factor: assertion 'GDK_IS_MONITOR (monitor)' failed Mar 31 14:46:07 gs00 gnome-shell[3873]: message repeated 48 times: [ DING: (gjs:578106): Gdk-CRITICAL **: 14:46:07.223: gdk_monitor_get_scale_factor: assertion 'GDK_IS_MONITOR (monitor)' failed] Mar 31 14:46:07 gs00 gnome-shell[3873]: DING: Detected async api for thumbnails Mar 31 14:46:07 gs00 gnome-shell[3873]: DING: (gjs:578138): Gdk-CRITICAL **: 14:46:07.480: gdk_monitor_get_scale_factor: assertion 'GDK_IS_MONITOR (monitor)' failed Mar 31 14:46:07 gs00 gnome-shell[3873]: message repeated 4 times: [ DING: (gjs:578138): Gdk-CRITICAL **: 14:46:07.480: gdk_monitor_get_scale_factor: assertion 'GDK_IS_MONITOR (monitor)' failed] Mar 31 14:46:07 gs00 gnome-shell[3873]: DING: (gjs:578138): Gdk-CRITICAL **: 14:46:07.481:
[Desktop-packages] [Bug 1967274] Re: Screen sometimes can't update on Intel Alder Lake GPUs [Failed to post KMS update: CRTC property (GAMMA_LUT) not found]
Confirmed with fresh installed Jammy release(5.15.0-23). After the
screen dim, the backlight power is off,
"/sys/class/backlight/intel_backlight/bl_power", and can't echo 0 to it
to light up.
Switch vt(ctrl+alt+F1) works, and then I can turn off and turn on the backlight
by
echo 4 | sudo tee /sys/class/backlight/intel_backlight/bl_power
echo 0 | sudo tee /sys/class/backlight/intel_backlight/bl_power
Close the lid and then open it, got the same behavior as meta+l, can't
turn on the backlight.
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to mutter in Ubuntu.
https://bugs.launchpad.net/bugs/1967274
Title:
Screen sometimes can't update on Intel Alder Lake GPUs [Failed to post
KMS update: CRTC property (GAMMA_LUT) not found]
Status in Mutter:
Unknown
Status in OEM Priority Project:
New
Status in linux package in Ubuntu:
Triaged
Status in mutter package in Ubuntu:
Triaged
Bug description:
Screen can't turn back on by clicking keyboard after screen off by meta + l
key.
Try to do VT switch can make the screen back, some error poped when I try to
wake up screen.
gnome-shell[1666]: Failed to post KMS update: CRTC property (GAMMA_LUT) not
found
gnome-shell[1666]: Failed to post KMS update: CRTC property (GAMMA_LUT) not
found
gnome-shell[1666]: Failed to post KMS update: drmModeAtomicCommit: Invalid
argument
gnome-shell[1666]: Failed to post KMS update: drmModeAtomicCommit: Invalid
argument
gnome-shell[1666]: Failed to post KMS update: drmModeAtomicCommit: Invalid
argument
---
ProblemType: Bug
ApportVersion: 2.20.11-0ubuntu79
Architecture: amd64
CasperMD5CheckResult: pass
CurrentDesktop: ubuntu:GNOME
DisplayManager: gdm3
DistroRelease: Ubuntu 22.04
GsettingsChanges:
b'org.gnome.shell' b'welcome-dialog-last-shown-version' b"'42.beta'"
b'org.gnome.desktop.input-sources' b'sources' b"[('xkb', 'us')]"
b'org.gnome.desktop.interface' b'gtk-im-module' b"'gtk-im-context-simple'"
b'org.gnome.desktop.privacy' b'report-technical-problems' b'true'
InstallationDate: Installed on 2022-03-31 (0 days ago)
InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Alpha amd64 (20220326)
Package: gnome-shell 42~beta-1ubuntu3 [origin: unknown]
PackageArchitecture: amd64
ProcVersionSignature: Ubuntu 5.15.0-23.23-generic 5.15.27
RelatedPackageVersions: mutter-common 42~beta-1ubuntu2
Tags: wayland-session jammy third-party-packages
Uname: Linux 5.15.0-23-generic x86_64
UnreportableReason: This does not seem to be an official Ubuntu package.
Please retry after updating the indexes of available packages, if that does not
work then remove related third party packages and try again.
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo
_MarkForUpload: True
To manage notifications about this bug go to:
https://bugs.launchpad.net/mutter/+bug/1967274/+subscriptions
--
Mailing list: https://launchpad.net/~desktop-packages
Post to : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-packages
More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1967471] [NEW] Artifacts when any window is being minimized to tray (on the second or more tries)
Public bug reported: sudo update and sudo apt full-upgrade have been performed as well. Video screen has been attached ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: gnome-shell 42.0-1ubuntu1 ProcVersionSignature: Ubuntu 5.15.0-23.23-generic 5.15.27 Uname: Linux 5.15.0-23-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.20.11-0ubuntu80 Architecture: amd64 CasperMD5CheckResult: pass CasperVersion: 1.468 CurrentDesktop: ubuntu:GNOME Date: Fri Apr 1 07:36:46 2022 DisplayManager: gdm3 LiveMediaBuild: Ubuntu 22.04 LTS "Jammy Jellyfish" - Beta amd64 (20220329.1) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=ru_RU.UTF-8 SHELL=/bin/bash RebootRequiredPkgs: Error: path contained symlinks. RelatedPackageVersions: mutter-common 42.0-1ubuntu1 SourcePackage: gnome-shell UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: gnome-shell (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug jammy ** Attachment added: "Запись экрана от 01.04.2022 07:34:56.webm" https://bugs.launchpad.net/bugs/1967471/+attachment/5575524/+files/%D0%97%D0%B0%D0%BF%D0%B8%D1%81%D1%8C%20%D1%8D%D0%BA%D1%80%D0%B0%D0%BD%D0%B0%20%D0%BE%D1%82%2001.04.2022%2007%3A34%3A56.webm -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-shell in Ubuntu. https://bugs.launchpad.net/bugs/1967471 Title: Artifacts when any window is being minimized to tray (on the second or more tries) Status in gnome-shell package in Ubuntu: New Bug description: sudo update and sudo apt full-upgrade have been performed as well. Video screen has been attached ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: gnome-shell 42.0-1ubuntu1 ProcVersionSignature: Ubuntu 5.15.0-23.23-generic 5.15.27 Uname: Linux 5.15.0-23-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.20.11-0ubuntu80 Architecture: amd64 CasperMD5CheckResult: pass CasperVersion: 1.468 CurrentDesktop: ubuntu:GNOME Date: Fri Apr 1 07:36:46 2022 DisplayManager: gdm3 LiveMediaBuild: Ubuntu 22.04 LTS "Jammy Jellyfish" - Beta amd64 (20220329.1) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=ru_RU.UTF-8 SHELL=/bin/bash RebootRequiredPkgs: Error: path contained symlinks. RelatedPackageVersions: mutter-common 42.0-1ubuntu1 SourcePackage: gnome-shell UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1967471/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1967274] Re: Screen sometimes can't update on Intel Alder Lake GPUs [Failed to post KMS update: CRTC property (GAMMA_LUT) not found]
Yes this is an Alder Lake issue which seems to have originated in the
kernel. But at the same time we should make mutter more robust to handle
missing driver features.
Tracking in https://gitlab.gnome.org/GNOME/mutter/-/issues/2197
** Summary changed:
- Screen can't turn on after screen off [Failed to post KMS update: CRTC
property (GAMMA_LUT) not found]
+ Screen sometimes can't update on Intel Alder Lake GPUs [Failed to post KMS
update: CRTC property (GAMMA_LUT) not found]
** Changed in: mutter (Ubuntu)
Status: Incomplete => Confirmed
** No longer affects: gnome-shell (Ubuntu)
** Bug watch added: gitlab.gnome.org/GNOME/mutter/-/issues #2197
https://gitlab.gnome.org/GNOME/mutter/-/issues/2197
** Also affects: mutter via
https://gitlab.gnome.org/GNOME/mutter/-/issues/2197
Importance: Unknown
Status: Unknown
** Changed in: mutter (Ubuntu)
Importance: Undecided => High
** Also affects: linux (Ubuntu)
Importance: Undecided
Status: New
** Changed in: linux (Ubuntu)
Status: New => Confirmed
** Changed in: linux (Ubuntu)
Importance: Undecided => High
** Changed in: mutter (Ubuntu)
Status: Confirmed => Triaged
** Changed in: linux (Ubuntu)
Status: Confirmed => Triaged
** Tags added: rls-jj-incoming
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to gnome-shell in Ubuntu.
https://bugs.launchpad.net/bugs/1967274
Title:
Screen sometimes can't update on Intel Alder Lake GPUs [Failed to post
KMS update: CRTC property (GAMMA_LUT) not found]
Status in Mutter:
Unknown
Status in OEM Priority Project:
New
Status in linux package in Ubuntu:
Triaged
Status in mutter package in Ubuntu:
Triaged
Bug description:
Screen can't turn back on by clicking keyboard after screen off by meta + l
key.
Try to do VT switch can make the screen back, some error poped when I try to
wake up screen.
gnome-shell[1666]: Failed to post KMS update: CRTC property (GAMMA_LUT) not
found
gnome-shell[1666]: Failed to post KMS update: CRTC property (GAMMA_LUT) not
found
gnome-shell[1666]: Failed to post KMS update: drmModeAtomicCommit: Invalid
argument
gnome-shell[1666]: Failed to post KMS update: drmModeAtomicCommit: Invalid
argument
gnome-shell[1666]: Failed to post KMS update: drmModeAtomicCommit: Invalid
argument
---
ProblemType: Bug
ApportVersion: 2.20.11-0ubuntu79
Architecture: amd64
CasperMD5CheckResult: pass
CurrentDesktop: ubuntu:GNOME
DisplayManager: gdm3
DistroRelease: Ubuntu 22.04
GsettingsChanges:
b'org.gnome.shell' b'welcome-dialog-last-shown-version' b"'42.beta'"
b'org.gnome.desktop.input-sources' b'sources' b"[('xkb', 'us')]"
b'org.gnome.desktop.interface' b'gtk-im-module' b"'gtk-im-context-simple'"
b'org.gnome.desktop.privacy' b'report-technical-problems' b'true'
InstallationDate: Installed on 2022-03-31 (0 days ago)
InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Alpha amd64 (20220326)
Package: gnome-shell 42~beta-1ubuntu3 [origin: unknown]
PackageArchitecture: amd64
ProcVersionSignature: Ubuntu 5.15.0-23.23-generic 5.15.27
RelatedPackageVersions: mutter-common 42~beta-1ubuntu2
Tags: wayland-session jammy third-party-packages
Uname: Linux 5.15.0-23-generic x86_64
UnreportableReason: This does not seem to be an official Ubuntu package.
Please retry after updating the indexes of available packages, if that does not
work then remove related third party packages and try again.
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo
_MarkForUpload: True
To manage notifications about this bug go to:
https://bugs.launchpad.net/mutter/+bug/1967274/+subscriptions
--
Mailing list: https://launchpad.net/~desktop-packages
Post to : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-packages
More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1783202] Re: Build Firefox with gpsd location provider support (--enable-gpsd)
Trying to build firefox with gpsd support: "ERROR: Package libgps was not found in the pkg-config search path" but i have libgps-dev and libgps installed and are in pkg-config path version is >= 3.11 -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to firefox in Ubuntu. https://bugs.launchpad.net/bugs/1783202 Title: Build Firefox with gpsd location provider support (--enable-gpsd) Status in firefox package in Ubuntu: Confirmed Bug description: Firefox 50+ has support for gpsd, see https://bugzilla.mozilla.org/show_bug.cgi?id=1250922 That would allow users with a GPS device to use the provided GPS data for the Geolocation API within the browser - not by default (in stable release builds), but only after explicitly setting 'geo.location.use_gpsd' to 'true' in about:config. Which is a good thing, as no defaults change. However that support has to be enabled with the build flag --enable-gpsd. As you can see in toolkit/moz.configure the only thing that is needed to build Firefox with gpsd support is libgps-dev installed on the build system: https://hg.mozilla.org/mozilla-central/file/ccfd7b716a91/toolkit/moz.configure#l550 If you want to dig deeper here are the three changes that brought gpsd support: https://hg.mozilla.org/mozilla-central/rev/76b04196acce https://hg.mozilla.org/mozilla-central/rev/a1a42e8d66e9 https://hg.mozilla.org/mozilla-central/rev/457be633b6cc There is not much magic here: When users switch on the flag 'geo.location.use_gpsd', Firefox tries to get the position from gpsd, if no location information is received from GPS within a few seconds, as fallback Mozilla Location Service provides a position instead. The position however will be updated once GPS is ready. If GPS fails, MLS will take over again until GPS has been restored. The only thing you might want to be aware of is that on non-release builds, the gpsd location provider is enabled by default, meaning 'geo.location.use_gpsd' is 'true' (see revision a1a42e8d66e9) because Firefox devs want to give it some testing. However that shouldn't be an issue, because as described, MLS acts as fallback after a few seconds anyway. What do you think? To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/firefox/+bug/1783202/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1967456] Re: Jammy didn't use nvidia driver when executing firefox
the issue is not likely a kernel one, reassigning to firefox ** Package changed: linux (Ubuntu) => firefox (Ubuntu) -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to firefox in Ubuntu. https://bugs.launchpad.net/bugs/1967456 Title: Jammy didn't use nvidia driver when executing firefox Status in firefox package in Ubuntu: Confirmed Bug description: [Reproduce step] 1. Install Jammy beta. 2. Install Nvidia driver by ubuntu-driver install. 3. Connect monitor to dGPU output port. 4. Run firefox, type "about:support" in url, and check column "GPU #1" [Expected result] should see nvidia driver info. [Actual result] still use llvmpipe [Info] OS version: Ubuntu Jammy Jellyfish (development branch) Device: HP Z2 Mini G5 workstation CID: 202008-28179 Wayland in use. ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: linux-image-5.15.0-23-generic 5.15.0-23.23 ProcVersionSignature: Ubuntu 5.15.0-23.23-generic 5.15.27 Uname: Linux 5.15.0-23-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu79 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: u 1186 F pulseaudio /dev/snd/controlC1: u 1186 F pulseaudio CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Fri Apr 1 00:07:47 2022 InstallationDate: Installed on 2022-04-01 (0 days ago) InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Beta amd64 (20220329.1) MachineType: HP HP Z2 Mini G5 Workstation ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcFB: 0 EFI VGA ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.15.0-23-generic root=UUID=adaf5521-655d-454a-9bad-ef17619a51f2 ro quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-5.15.0-23-generic N/A linux-backports-modules-5.15.0-23-generic N/A linux-firmware 20220314.gitcd01f857-0ubuntu2 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 07/02/2020 dmi.bios.release: 0.1 dmi.bios.vendor: HP dmi.bios.version: S50 Ver. 01.00.01 dmi.board.name: 8754 dmi.board.vendor: HP dmi.board.version: KBC Version 09.08.03 dmi.chassis.type: 2 dmi.chassis.vendor: HP dmi.ec.firmware.release: 9.8 dmi.modalias: dmi:bvnHP:bvrS50Ver.01.00.01:bd07/02/2020:br0.1:efr9.8:svnHP:pnHPZ2MiniG5Workstation:pvr:rvnHP:rn8754:rvrKBCVersion09.08.03:cvnHP:ct2:cvr:sku9JD38AV: dmi.product.family: 103C_53335X HP Workstation dmi.product.name: HP Z2 Mini G5 Workstation dmi.product.sku: 9JD38AV dmi.sys.vendor: HP To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/firefox/+bug/1967456/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1967274] Re: Screen can't turn on after screen off [Failed to post KMS update: CRTC property (GAMMA_LUT) not found]
MUTTER_DEBUG_DISABLE_TRIPLE_BUFFERING=1 can still reproduce the issue.
MUTTER_DEBUG_ENABLE_ATOMIC_KMS=0 gdm3 can't up successfully.
** Attachment added: "drminfo.txt"
https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1967274/+attachment/5575522/+files/drminfo.txt
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to gnome-shell in Ubuntu.
https://bugs.launchpad.net/bugs/1967274
Title:
Screen can't turn on after screen off [Failed to post KMS update: CRTC
property (GAMMA_LUT) not found]
Status in OEM Priority Project:
New
Status in gnome-shell package in Ubuntu:
Incomplete
Status in mutter package in Ubuntu:
Incomplete
Bug description:
Screen can't turn back on by clicking keyboard after screen off by meta + l
key.
Try to do VT switch can make the screen back, some error poped when I try to
wake up screen.
gnome-shell[1666]: Failed to post KMS update: CRTC property (GAMMA_LUT) not
found
gnome-shell[1666]: Failed to post KMS update: CRTC property (GAMMA_LUT) not
found
gnome-shell[1666]: Failed to post KMS update: drmModeAtomicCommit: Invalid
argument
gnome-shell[1666]: Failed to post KMS update: drmModeAtomicCommit: Invalid
argument
gnome-shell[1666]: Failed to post KMS update: drmModeAtomicCommit: Invalid
argument
---
ProblemType: Bug
ApportVersion: 2.20.11-0ubuntu79
Architecture: amd64
CasperMD5CheckResult: pass
CurrentDesktop: ubuntu:GNOME
DisplayManager: gdm3
DistroRelease: Ubuntu 22.04
GsettingsChanges:
b'org.gnome.shell' b'welcome-dialog-last-shown-version' b"'42.beta'"
b'org.gnome.desktop.input-sources' b'sources' b"[('xkb', 'us')]"
b'org.gnome.desktop.interface' b'gtk-im-module' b"'gtk-im-context-simple'"
b'org.gnome.desktop.privacy' b'report-technical-problems' b'true'
InstallationDate: Installed on 2022-03-31 (0 days ago)
InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Alpha amd64 (20220326)
Package: gnome-shell 42~beta-1ubuntu3 [origin: unknown]
PackageArchitecture: amd64
ProcVersionSignature: Ubuntu 5.15.0-23.23-generic 5.15.27
RelatedPackageVersions: mutter-common 42~beta-1ubuntu2
Tags: wayland-session jammy third-party-packages
Uname: Linux 5.15.0-23-generic x86_64
UnreportableReason: This does not seem to be an official Ubuntu package.
Please retry after updating the indexes of available packages, if that does not
work then remove related third party packages and try again.
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo
_MarkForUpload: True
To manage notifications about this bug go to:
https://bugs.launchpad.net/oem-priority/+bug/1967274/+subscriptions
--
Mailing list: https://launchpad.net/~desktop-packages
Post to : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-packages
More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1967456] [NEW] Jammy didn't use nvidia driver when executing firefox
You have been subscribed to a public bug: [Reproduce step] 1. Install Jammy beta. 2. Install Nvidia driver by ubuntu-driver install. 3. Connect monitor to dGPU output port. 4. Run firefox, type "about:support" in url, and check column "GPU #1" [Expected result] should see nvidia driver info. [Actual result] still use llvmpipe [Info] OS version: Ubuntu Jammy Jellyfish (development branch) Device: HP Z2 Mini G5 workstation CID: 202008-28179 Wayland in use. ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: linux-image-5.15.0-23-generic 5.15.0-23.23 ProcVersionSignature: Ubuntu 5.15.0-23.23-generic 5.15.27 Uname: Linux 5.15.0-23-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu79 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: u 1186 F pulseaudio /dev/snd/controlC1: u 1186 F pulseaudio CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Fri Apr 1 00:07:47 2022 InstallationDate: Installed on 2022-04-01 (0 days ago) InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Beta amd64 (20220329.1) MachineType: HP HP Z2 Mini G5 Workstation ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcFB: 0 EFI VGA ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.15.0-23-generic root=UUID=adaf5521-655d-454a-9bad-ef17619a51f2 ro quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-5.15.0-23-generic N/A linux-backports-modules-5.15.0-23-generic N/A linux-firmware 20220314.gitcd01f857-0ubuntu2 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 07/02/2020 dmi.bios.release: 0.1 dmi.bios.vendor: HP dmi.bios.version: S50 Ver. 01.00.01 dmi.board.name: 8754 dmi.board.vendor: HP dmi.board.version: KBC Version 09.08.03 dmi.chassis.type: 2 dmi.chassis.vendor: HP dmi.ec.firmware.release: 9.8 dmi.modalias: dmi:bvnHP:bvrS50Ver.01.00.01:bd07/02/2020:br0.1:efr9.8:svnHP:pnHPZ2MiniG5Workstation:pvr:rvnHP:rn8754:rvrKBCVersion09.08.03:cvnHP:ct2:cvr:sku9JD38AV: dmi.product.family: 103C_53335X HP Workstation dmi.product.name: HP Z2 Mini G5 Workstation dmi.product.sku: 9JD38AV dmi.sys.vendor: HP ** Affects: firefox (Ubuntu) Importance: Undecided Status: Confirmed ** Tags: amd64 apport-bug jammy jiayi oem-priority wayland-session -- Jammy didn't use nvidia driver when executing firefox https://bugs.launchpad.net/bugs/1967456 You received this bug notification because you are a member of Desktop Packages, which is subscribed to firefox in Ubuntu. -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1967274] Re: Screen can't turn on after screen off [Failed to post KMS update: CRTC property (GAMMA_LUT) not found]
** Tags added: jiayi originate-from-1967462
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to gnome-shell in Ubuntu.
https://bugs.launchpad.net/bugs/1967274
Title:
Screen can't turn on after screen off [Failed to post KMS update: CRTC
property (GAMMA_LUT) not found]
Status in OEM Priority Project:
New
Status in gnome-shell package in Ubuntu:
Incomplete
Status in mutter package in Ubuntu:
Incomplete
Bug description:
Screen can't turn back on by clicking keyboard after screen off by meta + l
key.
Try to do VT switch can make the screen back, some error poped when I try to
wake up screen.
gnome-shell[1666]: Failed to post KMS update: CRTC property (GAMMA_LUT) not
found
gnome-shell[1666]: Failed to post KMS update: CRTC property (GAMMA_LUT) not
found
gnome-shell[1666]: Failed to post KMS update: drmModeAtomicCommit: Invalid
argument
gnome-shell[1666]: Failed to post KMS update: drmModeAtomicCommit: Invalid
argument
gnome-shell[1666]: Failed to post KMS update: drmModeAtomicCommit: Invalid
argument
---
ProblemType: Bug
ApportVersion: 2.20.11-0ubuntu79
Architecture: amd64
CasperMD5CheckResult: pass
CurrentDesktop: ubuntu:GNOME
DisplayManager: gdm3
DistroRelease: Ubuntu 22.04
GsettingsChanges:
b'org.gnome.shell' b'welcome-dialog-last-shown-version' b"'42.beta'"
b'org.gnome.desktop.input-sources' b'sources' b"[('xkb', 'us')]"
b'org.gnome.desktop.interface' b'gtk-im-module' b"'gtk-im-context-simple'"
b'org.gnome.desktop.privacy' b'report-technical-problems' b'true'
InstallationDate: Installed on 2022-03-31 (0 days ago)
InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Alpha amd64 (20220326)
Package: gnome-shell 42~beta-1ubuntu3 [origin: unknown]
PackageArchitecture: amd64
ProcVersionSignature: Ubuntu 5.15.0-23.23-generic 5.15.27
RelatedPackageVersions: mutter-common 42~beta-1ubuntu2
Tags: wayland-session jammy third-party-packages
Uname: Linux 5.15.0-23-generic x86_64
UnreportableReason: This does not seem to be an official Ubuntu package.
Please retry after updating the indexes of available packages, if that does not
work then remove related third party packages and try again.
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo
_MarkForUpload: True
To manage notifications about this bug go to:
https://bugs.launchpad.net/oem-priority/+bug/1967274/+subscriptions
--
Mailing list: https://launchpad.net/~desktop-packages
Post to : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-packages
More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1967274] Re: Screen can't turn on after screen off [Failed to post KMS update: CRTC property (GAMMA_LUT) not found]
Please also run:
sudo drm_info > drminfo.txt
and attach the resulting text file here.
** Bug watch removed: gitlab.gnome.org/GNOME/mutter/-/issues #2005
https://gitlab.gnome.org/GNOME/mutter/-/issues/2005
** Bug watch removed: gitlab.gnome.org/GNOME/mutter/-/issues #2197
https://gitlab.gnome.org/GNOME/mutter/-/issues/2197
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to gnome-shell in Ubuntu.
https://bugs.launchpad.net/bugs/1967274
Title:
Screen can't turn on after screen off [Failed to post KMS update: CRTC
property (GAMMA_LUT) not found]
Status in OEM Priority Project:
New
Status in gnome-shell package in Ubuntu:
Incomplete
Status in mutter package in Ubuntu:
Incomplete
Bug description:
Screen can't turn back on by clicking keyboard after screen off by meta + l
key.
Try to do VT switch can make the screen back, some error poped when I try to
wake up screen.
gnome-shell[1666]: Failed to post KMS update: CRTC property (GAMMA_LUT) not
found
gnome-shell[1666]: Failed to post KMS update: CRTC property (GAMMA_LUT) not
found
gnome-shell[1666]: Failed to post KMS update: drmModeAtomicCommit: Invalid
argument
gnome-shell[1666]: Failed to post KMS update: drmModeAtomicCommit: Invalid
argument
gnome-shell[1666]: Failed to post KMS update: drmModeAtomicCommit: Invalid
argument
---
ProblemType: Bug
ApportVersion: 2.20.11-0ubuntu79
Architecture: amd64
CasperMD5CheckResult: pass
CurrentDesktop: ubuntu:GNOME
DisplayManager: gdm3
DistroRelease: Ubuntu 22.04
GsettingsChanges:
b'org.gnome.shell' b'welcome-dialog-last-shown-version' b"'42.beta'"
b'org.gnome.desktop.input-sources' b'sources' b"[('xkb', 'us')]"
b'org.gnome.desktop.interface' b'gtk-im-module' b"'gtk-im-context-simple'"
b'org.gnome.desktop.privacy' b'report-technical-problems' b'true'
InstallationDate: Installed on 2022-03-31 (0 days ago)
InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Alpha amd64 (20220326)
Package: gnome-shell 42~beta-1ubuntu3 [origin: unknown]
PackageArchitecture: amd64
ProcVersionSignature: Ubuntu 5.15.0-23.23-generic 5.15.27
RelatedPackageVersions: mutter-common 42~beta-1ubuntu2
Tags: wayland-session jammy third-party-packages
Uname: Linux 5.15.0-23-generic x86_64
UnreportableReason: This does not seem to be an official Ubuntu package.
Please retry after updating the indexes of available packages, if that does not
work then remove related third party packages and try again.
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo
_MarkForUpload: True
To manage notifications about this bug go to:
https://bugs.launchpad.net/oem-priority/+bug/1967274/+subscriptions
--
Mailing list: https://launchpad.net/~desktop-packages
Post to : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-packages
More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1964120] Re: gnome-shell crashed with SIGSEGV at ?+a7c called from (Cannot access memory at address [in stack])
I think the final address ending in a7c is probably raise() so that may not be useful information. This is starting to smell like stack corruption. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-shell in Ubuntu. https://bugs.launchpad.net/bugs/1964120 Title: gnome-shell crashed with SIGSEGV at ?+a7c called from (Cannot access memory at address [in stack]) Status in gnome-shell package in Ubuntu: Confirmed Bug description: The Desktop has some issues but it was not showable ProblemType: Crash DistroRelease: Ubuntu 22.04 Package: gnome-shell 42~beta-1ubuntu1 Uname: Linux 5.16.12-051612-generic x86_64 ApportVersion: 2.20.11-0ubuntu78 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Mon Mar 7 12:12:08 2022 DisplayManager: gdm3 ExecutablePath: /usr/bin/gnome-shell InstallationDate: Installed on 2022-03-04 (4 days ago) InstallationMedia: Ubuntu 21.10 "Impish Indri" - Release amd64 (20211012) ProcCmdline: /usr/bin/gnome-shell ProcEnviron: LANG=de_DE.UTF-8 PATH=(custom, user) SHELL=/bin/bash XDG_RUNTIME_DIR= RelatedPackageVersions: mutter-common 42~beta-1ubuntu1 Signal: 11 SourcePackage: gnome-shell Stacktrace: #0 0x7f0d7aec5a7c in ?? () No symbol table info available. Backtrace stopped: Cannot access memory at address 0x7ffce8d834a0 StacktraceTop: ?? () Title: gnome-shell crashed with SIGSEGV UpgradeStatus: Upgraded to jammy on 2022-03-04 (4 days ago) UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo separator: To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1964120/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1964120] Re: gnome-shell crashed with SIGSEGV at ?+a7c called from [Cannot access memory at address]
All the duplicates seem to get stuck at addresses in [stack] according to ProcMaps.txt. The crash reports all say "Backtrace stopped: Cannot access memory at address", but ProcMaps.txt seems to indicate it's a valid stack address (read-write memory, but not executable). ** Summary changed: - gnome-shell crashed with SIGSEGV at ?+a7c called from [heap address] + gnome-shell crashed with SIGSEGV at ?+a7c called from [Cannot access memory at address] ** Summary changed: - gnome-shell crashed with SIGSEGV at ?+a7c called from [Cannot access memory at address] + gnome-shell crashed with SIGSEGV at ?+a7c called from (Cannot access memory at address [in stack]) -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-shell in Ubuntu. https://bugs.launchpad.net/bugs/1964120 Title: gnome-shell crashed with SIGSEGV at ?+a7c called from (Cannot access memory at address [in stack]) Status in gnome-shell package in Ubuntu: Confirmed Bug description: The Desktop has some issues but it was not showable ProblemType: Crash DistroRelease: Ubuntu 22.04 Package: gnome-shell 42~beta-1ubuntu1 Uname: Linux 5.16.12-051612-generic x86_64 ApportVersion: 2.20.11-0ubuntu78 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Mon Mar 7 12:12:08 2022 DisplayManager: gdm3 ExecutablePath: /usr/bin/gnome-shell InstallationDate: Installed on 2022-03-04 (4 days ago) InstallationMedia: Ubuntu 21.10 "Impish Indri" - Release amd64 (20211012) ProcCmdline: /usr/bin/gnome-shell ProcEnviron: LANG=de_DE.UTF-8 PATH=(custom, user) SHELL=/bin/bash XDG_RUNTIME_DIR= RelatedPackageVersions: mutter-common 42~beta-1ubuntu1 Signal: 11 SourcePackage: gnome-shell Stacktrace: #0 0x7f0d7aec5a7c in ?? () No symbol table info available. Backtrace stopped: Cannot access memory at address 0x7ffce8d834a0 StacktraceTop: ?? () Title: gnome-shell crashed with SIGSEGV UpgradeStatus: Upgraded to jammy on 2022-03-04 (4 days ago) UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo separator: To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1964120/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
