[Desktop-packages] [Bug 2015219] Re: ASUS COMPUTER INC laptop
The 'kisak' PPA you are using is not supported and likely to cause graphics bugs. Please remove the 'kisak' PPA from your system and then continue to log bugs for any problems you find. ** Package changed: xorg (Ubuntu) => ubuntu ** Changed in: ubuntu Status: Incomplete => Invalid -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to xorg in Ubuntu. https://bugs.launchpad.net/bugs/2015219 Title: ASUS COMPUTER INC laptop Status in Ubuntu: Invalid Bug description: ASUS COMPUTER INC laptop reboot and restart too slow xorg drivers my laptop working too slow ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: xorg 1:7.7+23ubuntu2 ProcVersionSignature: Ubuntu 5.19.0-38.39~22.04.1-generic 5.19.17 Uname: Linux 5.19.0-38-generic x86_64 ApportVersion: 2.20.11-0ubuntu82.3 Architecture: amd64 BootLog: Error: [Errno 13] Lupa evätty: '/var/log/boot.log' CasperMD5CheckResult: pass CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Tue Apr 4 14:09:21 2023 DistUpgraded: Fresh install DistroCodename: jammy DistroVariant: ubuntu DpkgLog: ExtraDebuggingInterest: Yes, including running git bisection searches GraphicsCard: Intel Corporation Atom/Celeron/Pentium Processor x5-E8000/J3xxx/N3xxx Integrated Graphics Controller [8086:22b1] (rev 21) (prog-if 00 [VGA controller]) Subsystem: ASUSTeK Computer Inc. Atom/Celeron/Pentium Processor x5-E8000/J3xxx/N3xxx Integrated Graphics Controller [1043:1d5d] InstallationDate: Installed on 2023-03-13 (22 days ago) InstallationMedia: Ubuntu 22.04.2 LTS "Jammy Jellyfish" - Release amd64 (20230223) MachineType: ASUSTeK COMPUTER INC. E402SA ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.19.0-38-generic root=UUID=45b0810a-3f7a-47d9-9368-7204c1732d88 ro quiet splash vt.handoff=7 SourcePackage: xorg UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 12/14/2015 dmi.bios.release: 5.6 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: E402SA.208 dmi.board.asset.tag: ATN12345678901234567 dmi.board.name: E402SA dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: 1.0 dmi.chassis.asset.tag: ATN12345678901234567 dmi.chassis.type: 10 dmi.chassis.vendor: ASUSTeK COMPUTER INC. dmi.chassis.version: 1.0 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrE402SA.208:bd12/14/2015:br5.6:svnASUSTeKCOMPUTERINC.:pnE402SA:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnE402SA:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0:skuASUS-NotebookSKU: dmi.product.family: E dmi.product.name: E402SA dmi.product.sku: ASUS-NotebookSKU dmi.product.version: 1.0 dmi.sys.vendor: ASUSTeK COMPUTER INC. version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.113-2~ubuntu0.22.04.1 version.libgl1-mesa-dri: libgl1-mesa-dri 23.0.1~kisak1~j version.libgl1-mesa-glx: libgl1-mesa-glx N/A version.xserver-xorg-core: xserver-xorg-core 2:21.1.3-2ubuntu2.9 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-2ubuntu1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20210115-1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.17-2build1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+bug/2015219/+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 956120] Re: gnome-shell crashed with SIGSEGV in g_type_check_instance_is_a()
This bug has been closed for 6 years so probably shouldn't be recycled. If you're experiencing a similar crash in 23.04 then please report it by running: ubuntu-bug /var/crash/YOURFILE.crash -- 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/956120 Title: gnome-shell crashed with SIGSEGV in g_type_check_instance_is_a() Status in gnome-shell package in Ubuntu: Invalid Bug description: Shell crash right after closing an application window (Synaptic). ProblemType: Crash DistroRelease: Ubuntu 12.04 Package: gnome-shell 3.3.90-0ubuntu1 ProcVersionSignature: Ubuntu 3.2.0-18.29-generic-pae 3.2.9 Uname: Linux 3.2.0-18-generic-pae i686 ApportVersion: 1.94.1-0ubuntu2 Architecture: i386 CrashCounter: 1 Date: Thu Mar 15 17:36:50 2012 ExecutablePath: /usr/bin/gnome-shell InstallationMedia: Kubuntu 12.04 LTS "Precise Pangolin" - Alpha i386 (20120211) ProcCmdline: /usr/bin/gnome-shell SegvAnalysis: Segfault happened at: 0xb7241ad0 : testb $0x4,0xe(%edi) PC (0xb7241ad0) ok source "$0x4" ok destination "0xe(%edi)" (0xc009fa22) not located in a known VMA region (needed writable region)! SegvReason: writing unknown VMA Signal: 11 SourcePackage: gnome-shell StacktraceTop: g_type_check_instance_is_a () from /usr/lib/i386-linux-gnu/libgobject-2.0.so.0 g_object_unref () from /usr/lib/i386-linux-gnu/libgobject-2.0.so.0 ?? () from /usr/lib/gnome-shell/libgnome-shell.so g_simple_async_result_complete () from /usr/lib/i386-linux-gnu/libgio-2.0.so.0 ?? () from /usr/lib/i386-linux-gnu/libgio-2.0.so.0 Title: gnome-shell crashed with SIGSEGV in g_type_check_instance_is_a() UpgradeStatus: Upgraded to precise on 2012-03-13 (2 days ago) UserGroups: adm cdrom dip lpadmin netdev plugdev sambashare sudo To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/956120/+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 1998267] Re: glib not aware of snap confinement
Hello Robert, or anyone else affected, Accepted glib2.0 into jammy-proposed. The package will build now and be available at https://launchpad.net/ubuntu/+source/glib2.0/2.72.4-0ubuntu2 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- jammy to verification-done-jammy. If it does not fix the bug for you, please add a comment stating that, and change the tag to verification- failed-jammy. 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. ** Changed in: glib2.0 (Ubuntu Jammy) Status: New => Fix Committed ** Tags added: verification-needed verification-needed-jammy -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to glib2.0 in Ubuntu. https://bugs.launchpad.net/bugs/1998267 Title: glib not aware of snap confinement Status in glib2.0 package in Ubuntu: Fix Released Status in glib2.0 source package in Jammy: Fix Committed Status in glib2.0 source package in Kinetic: Won't Fix Status in glib2.0 source package in Lunar: Fix Released Bug description: [ Impact] glib is not aware of snap confinement and this causes the internal logic to decide when to use portals to not work as designed. One important case is the gsettings backend, which should use a keyfile when confined rather than using dconf. When using a fully confined desktop this is required, as dconf is not suitable for sharing between snaps. This has been fixed in glib main: https://gitlab.gnome.org/GNOME/glib/-/merge_requests/3020 [ Test Plan ] (requires a core snap running the updated glib). 1. Install gnome-calculator snap: $ snap install gnome-calculator 2. Disconnect gsettings interface: $ snap disconnect gnome-calculator:gsettings 3. Run gnome-calculator 4. Change mode from basic to advanced 5. Close and re-open gnome-calculator Expected result: Mode change remembered on second run. gnome-calculator settings written to ~/snap/gnome-calculator/current/.config/glib-2.0/settings/keyfile Observed result: Mode change not remembered on second run, errors shown in console about accessing dconf: (gnome-calculator:1031938): dconf-CRITICAL **: 14:08:56.034: unable to create file '/run/user/1000/snap.gnome-calculator/dconf/user': Permission denied. dconf will not work properly. [ Where problems could occur ] - New bug introduced in glib causing a crash. - Security issue introduced in glib due to accessing snapctl. - Unexpected behaviour change when running snaps with updated glib. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/glib2.0/+bug/1998267/+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 2015264] Re: gnome-shell
Thanks for the bug report. Please explain what kind of problem you are experiencing. -- 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/2015264 Title: gnome-shell Status in gnome-shell package in Ubuntu: Incomplete Bug description: gnome-shell fix ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: gnome-shell 42.5-0ubuntu1 ProcVersionSignature: Ubuntu 5.19.0-38.39~22.04.1-generic 5.19.17 Uname: Linux 5.19.0-38-generic x86_64 ApportVersion: 2.20.11-0ubuntu82.3 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Tue Apr 4 18:22:35 2023 DisplayManager: gdm3 InstallationDate: Installed on 2023-03-12 (23 days ago) InstallationMedia: Ubuntu 22.04.2 LTS "Jammy Jellyfish" - Release amd64 (20230223) ProcEnviron: PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=fi_FI.UTF-8 SHELL=/bin/bash RelatedPackageVersions: mutter-common 42.5-0ubuntu1 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/2015264/+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 1774053] Re: Missing characters in gnome-shell after lock screen
If your primary GPU is Nvidia then bug 1876632 is more likely your issue. -- 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/1774053 Title: Missing characters in gnome-shell after lock screen Status in GNOME Shell: New Status in gnome-shell package in Ubuntu: Confirmed Status in mutter package in Ubuntu: Confirmed Bug description: I locked my screen, came back from lunch, and found that about half the characters in the lock screen were missing. After I logged back in, half the characters in the desktop were missing (https://drive.google.com/file/d/1mIDF4_jY0PIFOT53FoOOVoTY1BWeaNfy/view?usp=sharing). Chrome and Nautilus are not missing any characters, just the system UI. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: gnome-shell 3.28.1-0ubuntu2 ProcVersionSignature: Ubuntu 4.15.0-22.24-generic 4.15.17 Uname: Linux 4.15.0-22-generic x86_64 NonfreeKernelModules: wl nvidia_modeset nvidia ApportVersion: 2.20.9-0ubuntu7 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Tue May 29 12:25:58 2018 DisplayManager: gdm3 GsettingsChanges: b'org.gnome.shell' b'enabled-extensions' b"['ubuntu-d...@ubuntu.com', 'ubuntu-appindicat...@ubuntu.com']" b'org.gnome.shell' b'favorite-apps' redacted by apport b'org.gnome.desktop.interface' b'gtk-im-module' b"'gtk-im-context-simple'" b'org.gnome.desktop.interface' b'clock-show-seconds' b'true' b'org.gnome.desktop.interface' b'clock-show-date' b'true' InstallationDate: Installed on 2018-04-10 (48 days ago) InstallationMedia: Ubuntu 16.04.4 LTS "Xenial Xerus" - Release amd64 (20180228) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: gnome-shell UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-shell/+bug/1774053/+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 1698287] Re: VA-API fails to initialize in a Gnome Shell Wayland session
Actually we can say Fix Committed to Chromium now because it's a snap and the fixed libva has been added to it: https://code.launchpad.net/~hectorcao/chromium-browser/+git/chromium- browser/+merge/440311 ** Changed in: chromium-browser (Ubuntu) Status: Won't Fix => Fix Committed ** Changed in: chromium-browser (Ubuntu) Assignee: (unassigned) => Hector CAO (hectorcao) -- 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/1698287 Title: VA-API fails to initialize in a Gnome Shell Wayland session Status in Libva: Fix Released Status in Mutter: Fix Released Status in Totem: Expired Status in VLC media player: New Status in chromium-browser package in Ubuntu: Fix Committed Status in gst-plugins-bad1.0 package in Ubuntu: Fix Released Status in gst-plugins-base1.0 package in Ubuntu: Fix Committed Status in gstreamer-vaapi package in Ubuntu: Won't Fix Status in libva package in Ubuntu: Fix Released Status in mpv package in Ubuntu: Fix Released Status in steam package in Ubuntu: Confirmed Bug description: The Intel i965 VA-API driver works well in Xorg sessions (Unity7 and Gnome Shell). But it refuses to load when in a Wayland session: $ totem bbb_sunflower_1080p_60fps_normal.mp4 libva error: va_getDriverName() failed with unknown libva error,driver_name=(null) $ env LIBVA_DRIVER_NAME=i965 totem bbb_sunflower_1080p_60fps_normal.mp4 totem: intel_driver.c:112: intel_driver_init: Assertion `VA_CHECK_DRM_AUTH_TYPE(ctx, VA_DRM_AUTH_DRI1) || VA_CHECK_DRM_AUTH_TYPE(ctx, VA_DRM_AUTH_DRI2) || VA_CHECK_DRM_AUTH_TYPE(ctx, VA_DRM_AUTH_CUSTOM)' failed. Aborted (core dumped) $ gst-play-1.0 bbb_sunflower_1080p_60fps_normal.mp4 Press 'k' to see a list of keyboard shortcuts. Now playing /home/dan/Videos/bbb_sunflower_1080p_60fps_normal.mp4 Redistribute latency... Redistribute latency... ERROR Internal error: could not render surface for file:///home/dan/Videos/bbb_sunflower_1080p_60fps_normal.mp4 ERROR debug information: ../../../gst/vaapi/gstvaapisink.c(1482): gst_vaapisink_show_frame_unlocked (): /GstPlayBin:playbin/GstPlaySink:playsink/GstBin:vbin/GstVaapiSink:vaapisink0 WORKAROUNDS: * Use weston instead of gnome-shell; or * $ env -uDISPLAY totem ... # but creates corruption -> bug 1701463 * $ env GST_GL_WINDOW=wayland totem ... # but creates corruption -> bug 1701463 * $ env GST_GL_WINDOW=wayland gst-play-1.0 --videosink glimagesink ... * $ env -uDISPLAY mpv --hwdec --opengl-backend=wayland ... ProblemType: Bug DistroRelease: Ubuntu 17.10 Package: i965-va-driver 1.8.1-1 ProcVersionSignature: Ubuntu 4.10.0-22.24-generic 4.10.15 Uname: Linux 4.10.0-22-generic x86_64 ApportVersion: 2.20.5-0ubuntu4 Architecture: amd64 Date: Fri Jun 16 13:40:38 2017 InstallationDate: Installed on 2017-05-03 (44 days ago) InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Alpha amd64 (20170502) SourcePackage: intel-vaapi-driver UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/libva/+bug/1698287/+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 956120] Re: gnome-shell crashed with SIGSEGV in g_type_check_instance_is_a()
It also affects Ubuntu 23.04 -- 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/956120 Title: gnome-shell crashed with SIGSEGV in g_type_check_instance_is_a() Status in gnome-shell package in Ubuntu: Invalid Bug description: Shell crash right after closing an application window (Synaptic). ProblemType: Crash DistroRelease: Ubuntu 12.04 Package: gnome-shell 3.3.90-0ubuntu1 ProcVersionSignature: Ubuntu 3.2.0-18.29-generic-pae 3.2.9 Uname: Linux 3.2.0-18-generic-pae i686 ApportVersion: 1.94.1-0ubuntu2 Architecture: i386 CrashCounter: 1 Date: Thu Mar 15 17:36:50 2012 ExecutablePath: /usr/bin/gnome-shell InstallationMedia: Kubuntu 12.04 LTS "Precise Pangolin" - Alpha i386 (20120211) ProcCmdline: /usr/bin/gnome-shell SegvAnalysis: Segfault happened at: 0xb7241ad0 : testb $0x4,0xe(%edi) PC (0xb7241ad0) ok source "$0x4" ok destination "0xe(%edi)" (0xc009fa22) not located in a known VMA region (needed writable region)! SegvReason: writing unknown VMA Signal: 11 SourcePackage: gnome-shell StacktraceTop: g_type_check_instance_is_a () from /usr/lib/i386-linux-gnu/libgobject-2.0.so.0 g_object_unref () from /usr/lib/i386-linux-gnu/libgobject-2.0.so.0 ?? () from /usr/lib/gnome-shell/libgnome-shell.so g_simple_async_result_complete () from /usr/lib/i386-linux-gnu/libgio-2.0.so.0 ?? () from /usr/lib/i386-linux-gnu/libgio-2.0.so.0 Title: gnome-shell crashed with SIGSEGV in g_type_check_instance_is_a() UpgradeStatus: Upgraded to precise on 2012-03-13 (2 days ago) UserGroups: adm cdrom dip lpadmin netdev plugdev sambashare sudo To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/956120/+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 1959747]
I tried the latest Thunderbird 112 beta 6 and unfortunately the situation is still the same. I also managed to capture a profile of simply moving the mouse cursor vertically across the message pane window. My CPU usage goes up to 25% (on a 4-core CPU) while doing so: https://share.firefox.dev/3zvwCZH -- 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-102 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 and later. 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 1987976]
*** Bug 1825991 has been marked as a duplicate of this bug. *** -- 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/1987976 Title: firefox black window Status in Mozilla Firefox: Confirmed Status in Mutter: New Status in firefox package in Ubuntu: Confirmed Status in mutter package in Ubuntu: Confirmed Bug description: nicolas@nicolas-fixe:~$ lsb_release -rd Description: Ubuntu 22.04.1 LTS Release: 22.04 nicolas@nicolas-fixe:~$ apt-cache policy firefox firefox: Installé : 1:1snap1-0ubuntu2 Candidat : 1:1snap1-0ubuntu2 Table de version : *** 1:1snap1-0ubuntu2 500 500 http://fr.archive.ubuntu.com/ubuntu jammy/main amd64 Packages 100 /var/lib/dpkg/status When I boot Ubuntu and start Firefox, the Firefox's window is totally black. See attachment. I am at your disposal to answer any question you have. ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: firefox 1:1snap1-0ubuntu2 ProcVersionSignature: Ubuntu 5.15.0-46.49-generic 5.15.39 Uname: Linux 5.15.0-46-generic x86_64 ApportVersion: 2.20.11-0ubuntu82.1 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Sun Aug 28 12:42:29 2022 InstallationDate: Installed on 2022-08-25 (2 days ago) InstallationMedia: Ubuntu 22.04.1 LTS "Jammy Jellyfish" - Release amd64 (20220809.1) ProcEnviron: PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=fr_FR.UTF-8 SHELL=/bin/bash Snap.Changes: aucun changement trouvé SourcePackage: firefox UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/firefox/+bug/1987976/+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 2012287] Re: GNOME Characters search provider for GNOME Shell 44 crashes
seeing this on Ubuntu 23.04 -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-characters in Ubuntu. https://bugs.launchpad.net/bugs/2012287 Title: GNOME Characters search provider for GNOME Shell 44 crashes Status in GNOME Characters: Fix Released Status in gjs package in Ubuntu: Confirmed Status in gnome-characters package in Ubuntu: Triaged Bug description: Test Case - 1. From Ubuntu 22.10, install Lunar's glib 2.76.1 2. Log out 3. Log back in 4. Open the GNOME Shell Activities Overview and type the word smile 5. Close the Activities Overview What Happens In my case, if I repeat 4 and 5 several times, I will eventually get an apport crash popup dialog reporting that the GNOME Shell search provider for GNOME Characters has crashed. Other Info -- This isn't a gjs bug, but I'm leaving the gjs task open since I think apport looks for it. ProblemType: Crash DistroRelease: Ubuntu 23.04 Package: gjs 1.75.90-1 Uname: Linux 6.1.0-16-generic x86_64 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Mon Mar 20 23:04:59 2023 ExecutablePath: /usr/bin/gjs-console ExecutableTimestamp: 1678210639 ProcCmdline: /usr/bin/gjs-console /usr/bin/gnome-characters --gapplication-service ProcCwd: /home/solomax Signal: 6 SourcePackage: gjs UserGroups: adm cdrom dip docker lpadmin lxd plugdev sambashare sudo To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-characters/+bug/2012287/+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 2013122] Re: LO icons unable to deal with accent colors
This bug was fixed in the package libreoffice - 4:7.5.2-0ubuntu1 --- libreoffice (4:7.5.2-0ubuntu1) lunar; urgency=medium * New upstream release * Install all yaru icon variants (LP: #2013122) * Bump yaru source to "2023-03-31" -- Rico Tzschichholz Fri, 31 Mar 2023 15:25:17 +0200 ** Changed in: libreoffice (Ubuntu) Status: Fix Committed => Fix Released -- 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/2013122 Title: LO icons unable to deal with accent colors Status in libreoffice package in Ubuntu: Fix Released Bug description: OS: lunar libreoffice: 7.5.2~rc1-0ubuntu1 If a user selects a Yaru accent color (Settings -> Appearance -> purple), the icons of Libreoffice are no longer the expected Yaru icons. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libreoffice/+bug/2013122/+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 1979096] Re: gnome-shell search can't launch apps if dock auto-hide is enabled
This is still an issue with 22.04.2 LTS. If both dock auto-hide and 200% scaling are enabled, search results can not be clicked. Changing either setting allows clicking. Installed gnome-shell-extension-ubuntu-dock version is 72~ubuntu5.22.04.1 -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-shell-extension-ubuntu-dock in Ubuntu. https://bugs.launchpad.net/bugs/1979096 Title: gnome-shell search can't launch apps if dock auto-hide is enabled Status in Dash to dock: Fix Released Status in gnome-shell package in Ubuntu: Triaged Status in gnome-shell-extension-ubuntu-dock package in Ubuntu: Fix Released Status in gnome-shell-extension-ubuntu-dock source package in Jammy: Confirmed Bug description: The problem happens, when I enable the dock to hide automatically. With this enabled, it is not possible to run the programs through the search. But when disabled, it is possible to search and run the programs. Here's the video of the problem. ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: xorg 1:7.7+23ubuntu2 ProcVersionSignature: Ubuntu 5.15.0-39.42-generic 5.15.35 Uname: Linux 5.15.0-39-generic x86_64 ApportVersion: 2.20.11-0ubuntu82.1 Architecture: amd64 BootLog: Error: [Errno 13] Permissão negada: '/var/log/boot.log' CasperMD5CheckResult: unknown CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Fri Jun 17 18:21:45 2022 DistUpgraded: 2022-04-21 13:52:59,951 DEBUG Running PostInstallScript: '/usr/lib/ubuntu-advantage/upgrade_lts_contract.py' DistroCodename: jammy DistroVariant: ubuntu DkmsStatus: v4l2loopback/0.12.5, 5.15.0-37-generic, x86_64: installed v4l2loopback/0.12.5, 5.15.0-39-generic, x86_64: installed ExtraDebuggingInterest: I just need to know a workaround GraphicsCard: Advanced Micro Devices, Inc. [AMD/ATI] RS780L [Radeon 3000] [1002:9616] (prog-if 00 [VGA controller]) Subsystem: ASUSTeK Computer Inc. RS780L [Radeon 3000] [1043:8388] InstallationDate: Installed on 2021-04-15 (428 days ago) InstallationMedia: Ubuntu 20.04.2.0 LTS "Focal Fossa" - Release amd64 (20210209.1) MachineType: System manufacturer System Product Name ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.15.0-39-generic root=UUID=7e3c483e-6d02-4fc2-be0e-48207eb147eb ro quiet splash vt.handoff=7 SourcePackage: xorg Symptom: display UpgradeStatus: Upgraded to jammy on 2022-04-21 (57 days ago) dmi.bios.date: 03/04/2017 dmi.bios.release: 8.15 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 1201 dmi.board.asset.tag: To Be Filled By O.E.M. dmi.board.name: M5A78L-M LX/BR dmi.board.vendor: ASUSTeK Computer INC. dmi.board.version: Rev X.0x dmi.chassis.asset.tag: Asset-1234567890 dmi.chassis.type: 3 dmi.chassis.vendor: Chassis Manufacture dmi.chassis.version: Chassis Version dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr1201:bd03/04/2017:br8.15:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKComputerINC.:rnM5A78L-MLX/BR:rvrRevX.0x:cvnChassisManufacture:ct3:cvrChassisVersion:skuToBeFilledByO.E.M.: dmi.product.family: To Be Filled By O.E.M. dmi.product.name: System Product Name dmi.product.sku: To Be Filled By O.E.M. dmi.product.version: System Version dmi.sys.vendor: System manufacturer version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.110-1ubuntu1 version.libgl1-mesa-dri: libgl1-mesa-dri 22.0.1-1ubuntu2.1 version.libgl1-mesa-glx: libgl1-mesa-glx 22.0.1-1ubuntu2.1 version.xserver-xorg-core: xserver-xorg-core 2:21.1.3-2ubuntu2 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-2build3 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20210115-1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.17-2build1 To manage notifications about this bug go to: https://bugs.launchpad.net/dash-to-dock/+bug/1979096/+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 2015262] Re: gnome-control-center
Thank you for taking the time to report this bug and helping to make Ubuntu better. Unfortunately, we cannot work on this bug because your description didn't include enough information. You may find it helpful to read "How to report bugs effectively" http://www.chiark.greenend.org.uk/~sgtatham/bugs.html. We'd be grateful if you would then provide a more complete description of the problem. We have instructions on debugging some types of problems at http://wiki.ubuntu.com/DebuggingProcedures. At a minimum, we need: 1. The specific steps or actions you took that caused you to encounter the problem. 2. The behavior you expected. 3. The behavior you actually encountered (in as much detail as possible). Please also ensure that you include the release and flavour of Ubuntu that you are using. Thank you! ** Changed in: gnome-control-center (Ubuntu) Importance: Undecided => Low -- 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/2015262 Title: gnome-control-center Status in gnome-control-center package in Ubuntu: Incomplete Bug description: gnome-control-center logs fix ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: gnome-control-center 1:41.7-0ubuntu0.22.04.6 ProcVersionSignature: Ubuntu 5.19.0-38.39~22.04.1-generic 5.19.17 Uname: Linux 5.19.0-38-generic x86_64 ApportVersion: 2.20.11-0ubuntu82.3 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Tue Apr 4 18:21:28 2023 InstallationDate: Installed on 2023-03-12 (23 days ago) InstallationMedia: Ubuntu 22.04.2 LTS "Jammy Jellyfish" - Release amd64 (20230223) ProcEnviron: PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=fi_FI.UTF-8 SHELL=/bin/bash SourcePackage: gnome-control-center UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-control-center/+bug/2015262/+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 2015267] Re: gnome-system-monitor
Thank you for taking the time to report this bug and helping to make Ubuntu better. Unfortunately, we cannot work on this bug because your description didn't include enough information. You may find it helpful to read "How to report bugs effectively" http://www.chiark.greenend.org.uk/~sgtatham/bugs.html. We'd be grateful if you would then provide a more complete description of the problem. We have instructions on debugging some types of problems at http://wiki.ubuntu.com/DebuggingProcedures. At a minimum, we need: 1. The specific steps or actions you took that caused you to encounter the problem. 2. The behavior you expected. 3. The behavior you actually encountered (in as much detail as possible). Please also ensure that you include the release and flavour of Ubuntu that you are using. Thank you! ** Changed in: gnome-system-monitor (Ubuntu) Importance: Undecided => Low -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-system-monitor in Ubuntu. https://bugs.launchpad.net/bugs/2015267 Title: gnome-system-monitor Status in gnome-system-monitor package in Ubuntu: Incomplete Bug description: gnome-system-monitor fix bug ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: gnome-system-monitor 42.0-1 ProcVersionSignature: Ubuntu 5.19.0-38.39~22.04.1-generic 5.19.17 Uname: Linux 5.19.0-38-generic x86_64 ApportVersion: 2.20.11-0ubuntu82.3 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Tue Apr 4 18:25:40 2023 InstallationDate: Installed on 2023-03-12 (23 days ago) InstallationMedia: Ubuntu 22.04.2 LTS "Jammy Jellyfish" - Release amd64 (20230223) ProcEnviron: PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=fi_FI.UTF-8 SHELL=/bin/bash SourcePackage: gnome-system-monitor UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-system-monitor/+bug/2015267/+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 2015289] [NEW] Websites getting lost the logged sessions
Public bug reported: I updated to Firefox 112 from the Mozilla Team PPA and a strange thing happened: Almost all (but not all) websites I had logged in (like Netflix and Google) lost the session and I had to re-login. After I rebooted the computer (forced closing the Firefox) I had to log in again. ** Affects: firefox (Ubuntu) Importance: Undecided Status: New ** 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/2015289 Title: Websites getting lost the logged sessions Status in firefox package in Ubuntu: New Bug description: I updated to Firefox 112 from the Mozilla Team PPA and a strange thing happened: Almost all (but not all) websites I had logged in (like Netflix and Google) lost the session and I had to re-login. After I rebooted the computer (forced closing the Firefox) I had to log in again. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/firefox/+bug/2015289/+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 2015289] [NEW] Websites getting lost the logged sessions
You have been subscribed to a public bug: I updated to Firefox 112 from the Mozilla Team PPA and a strange thing happened: Almost all (but not all) websites I had logged in (like Netflix and Google) lost the session and I had to re-login. After I rebooted the computer (forced closing the Firefox) I had to log in again. ** Affects: firefox (Ubuntu) Importance: Undecided Status: New -- Websites getting lost the logged sessions https://bugs.launchpad.net/bugs/2015289 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 2015255] Re: Backlight regulation don't work
** Package changed: ubuntu => xorg (Ubuntu) -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to xorg in Ubuntu. https://bugs.launchpad.net/bugs/2015255 Title: Backlight regulation don't work Status in xorg package in Ubuntu: New Bug description: Hello. I trying different fresh live USB: 20.04, 22.04, 22.10 and 23.04-beta Only 23.04-beta can't adjust brightness level of display backlight on my laptop (lenovo legion 5 17ach6h). Processor: AMD Ryzen™ 7 5800H with Radeon™ Graphics × 16 Graphics: AMD Radeon™ Graphics / AMD Radeon™ Graphics ProblemType: Bug DistroRelease: Ubuntu 23.04 Package: xorg 1:7.7+23ubuntu2 ProcVersionSignature: Ubuntu 6.2.0-18.18-generic 6.2.6 Uname: Linux 6.2.0-18-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.26.0-0ubuntu2 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CasperMD5CheckResult: pass CasperVersion: 1.480 CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Tue Apr 4 14:17:45 2023 DistUpgraded: Fresh install DistroCodename: lunar DistroVariant: ubuntu ExtraDebuggingInterest: Yes GraphicsCard: NVIDIA Corporation GA104M [GeForce RTX 3070 Mobile / Max-Q] [10de:24dd] (rev a1) (prog-if 00 [VGA controller]) Subsystem: Lenovo GA104M [GeForce RTX 3070 Mobile / Max-Q] [17aa:3a4e] Advanced Micro Devices, Inc. [AMD/ATI] Cezanne [Radeon Vega Series / Radeon Vega Mobile Series] [1002:1638] (rev c5) (prog-if 00 [VGA controller]) Subsystem: Lenovo Cezanne [Radeon Vega Series / Radeon Vega Mobile Series] [17aa:3a4e] LiveMediaBuild: Ubuntu 23.04 "Lunar Lobster" - Beta amd64 (20230329) MachineType: LENOVO 82JY ProcEnviron: LANG=C.UTF-8 PATH=(custom, no user) SHELL=/bin/bash TERM=xterm-256color XDG_RUNTIME_DIR= ProcKernelCmdLine: BOOT_IMAGE=/casper/vmlinuz layerfs-path=minimal.standard.live.squashfs --- quiet splash SourcePackage: xorg Symptom: display UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 11/21/2022 dmi.bios.release: 1.59 dmi.bios.vendor: LENOVO dmi.bios.version: GKCN59WW 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: Legion 5 17ACH6H dmi.ec.firmware.release: 1.59 dmi.modalias: dmi:bvnLENOVO:bvrGKCN59WW:bd11/21/2022:br1.59:efr1.59:svnLENOVO:pn82JY:pvrLegion517ACH6H:rvnLENOVO:rnLNVNB161216:rvrNODPK:cvnLENOVO:ct10:cvrLegion517ACH6H:skuLENOVO_MT_82JY_BU_idea_FM_Legion517ACH6H: dmi.product.family: Legion 5 17ACH6H dmi.product.name: 82JY dmi.product.sku: LENOVO_MT_82JY_BU_idea_FM_Legion 5 17ACH6H dmi.product.version: Legion 5 17ACH6H dmi.sys.vendor: LENOVO version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.114-1 version.libgl1-mesa-dri: libgl1-mesa-dri 23.0.1-1ubuntu1 version.libgl1-mesa-glx: libgl1-mesa-glx N/A version.xserver-xorg-core: xserver-xorg-core 2:21.1.7-1ubuntu2 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-3 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20210115-1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.17-2build1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/2015255/+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 2015255] [NEW] Backlight regulation don't work
You have been subscribed to a public bug: Hello. I trying different fresh live USB: 20.04, 22.04, 22.10 and 23.04-beta Only 23.04-beta can't adjust brightness level of display backlight on my laptop (lenovo legion 5 17ach6h). Processor: AMD Ryzen™ 7 5800H with Radeon™ Graphics × 16 Graphics: AMD Radeon™ Graphics / AMD Radeon™ Graphics ProblemType: Bug DistroRelease: Ubuntu 23.04 Package: xorg 1:7.7+23ubuntu2 ProcVersionSignature: Ubuntu 6.2.0-18.18-generic 6.2.6 Uname: Linux 6.2.0-18-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.26.0-0ubuntu2 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CasperMD5CheckResult: pass CasperVersion: 1.480 CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Tue Apr 4 14:17:45 2023 DistUpgraded: Fresh install DistroCodename: lunar DistroVariant: ubuntu ExtraDebuggingInterest: Yes GraphicsCard: NVIDIA Corporation GA104M [GeForce RTX 3070 Mobile / Max-Q] [10de:24dd] (rev a1) (prog-if 00 [VGA controller]) Subsystem: Lenovo GA104M [GeForce RTX 3070 Mobile / Max-Q] [17aa:3a4e] Advanced Micro Devices, Inc. [AMD/ATI] Cezanne [Radeon Vega Series / Radeon Vega Mobile Series] [1002:1638] (rev c5) (prog-if 00 [VGA controller]) Subsystem: Lenovo Cezanne [Radeon Vega Series / Radeon Vega Mobile Series] [17aa:3a4e] LiveMediaBuild: Ubuntu 23.04 "Lunar Lobster" - Beta amd64 (20230329) MachineType: LENOVO 82JY ProcEnviron: LANG=C.UTF-8 PATH=(custom, no user) SHELL=/bin/bash TERM=xterm-256color XDG_RUNTIME_DIR= ProcKernelCmdLine: BOOT_IMAGE=/casper/vmlinuz layerfs-path=minimal.standard.live.squashfs --- quiet splash SourcePackage: xorg Symptom: display UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 11/21/2022 dmi.bios.release: 1.59 dmi.bios.vendor: LENOVO dmi.bios.version: GKCN59WW 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: Legion 5 17ACH6H dmi.ec.firmware.release: 1.59 dmi.modalias: dmi:bvnLENOVO:bvrGKCN59WW:bd11/21/2022:br1.59:efr1.59:svnLENOVO:pn82JY:pvrLegion517ACH6H:rvnLENOVO:rnLNVNB161216:rvrNODPK:cvnLENOVO:ct10:cvrLegion517ACH6H:skuLENOVO_MT_82JY_BU_idea_FM_Legion517ACH6H: dmi.product.family: Legion 5 17ACH6H dmi.product.name: 82JY dmi.product.sku: LENOVO_MT_82JY_BU_idea_FM_Legion 5 17ACH6H dmi.product.version: Legion 5 17ACH6H dmi.sys.vendor: LENOVO version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.114-1 version.libgl1-mesa-dri: libgl1-mesa-dri 23.0.1-1ubuntu1 version.libgl1-mesa-glx: libgl1-mesa-glx N/A version.xserver-xorg-core: xserver-xorg-core 2:21.1.7-1ubuntu2 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-3 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20210115-1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.17-2build1 ** Affects: xorg (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug lunar ubuntu -- Backlight regulation don't work https://bugs.launchpad.net/bugs/2015255 You received this bug notification because you are a member of Desktop Packages, which is subscribed to xorg 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 2015273] [NEW] Errors in syslog cant update stage views actor because it needs an allocation
Public bug reported: switch from wayland to xorg and error started. ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: gnome-shell 42.5-0ubuntu1 ProcVersionSignature: Ubuntu 5.19.0-38.39~22.04.1-generic 5.19.17 Uname: Linux 5.19.0-38-generic x86_64 ApportVersion: 2.20.11-0ubuntu82.3 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Tue Apr 4 08:37:09 2023 DisplayManager: gdm3 InstallationDate: Installed on 2023-03-18 (17 days ago) InstallationMedia: Ubuntu 22.04.1 LTS "Jammy Jellyfish" - Release amd64 (20220809.1) RelatedPackageVersions: mutter-common 42.5-0ubuntu1 SourcePackage: gnome-shell UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: gnome-shell (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug jammy -- 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/2015273 Title: Errors in syslog cant update stage views actor because it needs an allocation Status in gnome-shell package in Ubuntu: New Bug description: switch from wayland to xorg and error started. ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: gnome-shell 42.5-0ubuntu1 ProcVersionSignature: Ubuntu 5.19.0-38.39~22.04.1-generic 5.19.17 Uname: Linux 5.19.0-38-generic x86_64 ApportVersion: 2.20.11-0ubuntu82.3 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Tue Apr 4 08:37:09 2023 DisplayManager: gdm3 InstallationDate: Installed on 2023-03-18 (17 days ago) InstallationMedia: Ubuntu 22.04.1 LTS "Jammy Jellyfish" - Release amd64 (20220809.1) RelatedPackageVersions: mutter-common 42.5-0ubuntu1 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/2015273/+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 2015266] [NEW] gnome-remote-desktop
Public bug reported: gnome-remote-desktop fix working fast ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: gnome-remote-desktop 42.7-0ubuntu1 ProcVersionSignature: Ubuntu 5.19.0-38.39~22.04.1-generic 5.19.17 Uname: Linux 5.19.0-38-generic x86_64 ApportVersion: 2.20.11-0ubuntu82.3 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Tue Apr 4 18:24:41 2023 InstallationDate: Installed on 2023-03-12 (23 days ago) InstallationMedia: Ubuntu 22.04.2 LTS "Jammy Jellyfish" - Release amd64 (20230223) ProcEnviron: PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=fi_FI.UTF-8 SHELL=/bin/bash SourcePackage: gnome-remote-desktop UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: gnome-remote-desktop (Ubuntu) Importance: Undecided Status: Incomplete ** Tags: amd64 apport-bug jammy third-party-packages wayland-session ** Changed in: gnome-remote-desktop (Ubuntu) Status: New => Incomplete -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-remote-desktop in Ubuntu. https://bugs.launchpad.net/bugs/2015266 Title: gnome-remote-desktop Status in gnome-remote-desktop package in Ubuntu: Incomplete Bug description: gnome-remote-desktop fix working fast ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: gnome-remote-desktop 42.7-0ubuntu1 ProcVersionSignature: Ubuntu 5.19.0-38.39~22.04.1-generic 5.19.17 Uname: Linux 5.19.0-38-generic x86_64 ApportVersion: 2.20.11-0ubuntu82.3 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Tue Apr 4 18:24:41 2023 InstallationDate: Installed on 2023-03-12 (23 days ago) InstallationMedia: Ubuntu 22.04.2 LTS "Jammy Jellyfish" - Release amd64 (20230223) ProcEnviron: PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=fi_FI.UTF-8 SHELL=/bin/bash SourcePackage: gnome-remote-desktop UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-remote-desktop/+bug/2015266/+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 2015267] [NEW] gnome-system-monitor
Public bug reported: gnome-system-monitor fix bug ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: gnome-system-monitor 42.0-1 ProcVersionSignature: Ubuntu 5.19.0-38.39~22.04.1-generic 5.19.17 Uname: Linux 5.19.0-38-generic x86_64 ApportVersion: 2.20.11-0ubuntu82.3 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Tue Apr 4 18:25:40 2023 InstallationDate: Installed on 2023-03-12 (23 days ago) InstallationMedia: Ubuntu 22.04.2 LTS "Jammy Jellyfish" - Release amd64 (20230223) ProcEnviron: PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=fi_FI.UTF-8 SHELL=/bin/bash SourcePackage: gnome-system-monitor UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: gnome-system-monitor (Ubuntu) Importance: Undecided Status: Incomplete ** Tags: amd64 apport-bug jammy wayland-session ** Changed in: gnome-system-monitor (Ubuntu) Status: New => Incomplete -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-system-monitor in Ubuntu. https://bugs.launchpad.net/bugs/2015267 Title: gnome-system-monitor Status in gnome-system-monitor package in Ubuntu: Incomplete Bug description: gnome-system-monitor fix bug ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: gnome-system-monitor 42.0-1 ProcVersionSignature: Ubuntu 5.19.0-38.39~22.04.1-generic 5.19.17 Uname: Linux 5.19.0-38-generic x86_64 ApportVersion: 2.20.11-0ubuntu82.3 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Tue Apr 4 18:25:40 2023 InstallationDate: Installed on 2023-03-12 (23 days ago) InstallationMedia: Ubuntu 22.04.2 LTS "Jammy Jellyfish" - Release amd64 (20230223) ProcEnviron: PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=fi_FI.UTF-8 SHELL=/bin/bash SourcePackage: gnome-system-monitor UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-system-monitor/+bug/2015267/+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 2015259] [NEW] printer driver
Public bug reported: HP deskjet 2600 series driver cups ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: cups 2.4.1op1-1ubuntu4.1 ProcVersionSignature: Ubuntu 5.19.0-38.39~22.04.1-generic 5.19.17 Uname: Linux 5.19.0-38-generic x86_64 ApportVersion: 2.20.11-0ubuntu82.3 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Tue Apr 4 18:18:12 2023 InstallationDate: Installed on 2023-03-12 (23 days ago) InstallationMedia: Ubuntu 22.04.2 LTS "Jammy Jellyfish" - Release amd64 (20230223) KernLog: Lpstat: device for HP_DeskJet_2600_series_D60582_USB: implicitclass://HP_DeskJet_2600_series_D60582_USB/ MachineType: MSI MS-7817 Papersize: a4 PpdFiles: Error: command ['fgrep', '-H', '*NickName', '/etc/cups/ppd/HP_DeskJet_2600_series_D60582_USB.ppd'] failed with exit code 2: grep: /etc/cups/ppd/HP_DeskJet_2600_series_D60582_USB.ppd: Permission denied ProcEnviron: PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=fi_FI.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.19.0-38-generic root=UUID=7937a7b0-31fc-4dec-b3c2-51df4e876c20 ro quiet splash vt.handoff=7 SourcePackage: cups UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 04/21/2015 dmi.bios.release: 4.6 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: V10.9 dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: B85M-E45 (MS-7817) dmi.board.vendor: MSI dmi.board.version: 2.0 dmi.chassis.asset.tag: To be filled by O.E.M. dmi.chassis.type: 3 dmi.chassis.vendor: MSI dmi.chassis.version: 2.0 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrV10.9:bd04/21/2015:br4.6:svnMSI:pnMS-7817:pvr2.0:rvnMSI:rnB85M-E45(MS-7817):rvr2.0:cvnMSI:ct3:cvr2.0:skuTobefilledbyO.E.M.: dmi.product.family: To be filled by O.E.M. dmi.product.name: MS-7817 dmi.product.sku: To be filled by O.E.M. dmi.product.version: 2.0 dmi.sys.vendor: MSI ** Affects: cups (Ubuntu) Importance: Undecided Status: Incomplete ** Tags: amd64 apport-bug jammy wayland-session ** Changed in: cups (Ubuntu) Status: New => Incomplete -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to cups in Ubuntu. https://bugs.launchpad.net/bugs/2015259 Title: printer driver Status in cups package in Ubuntu: Incomplete Bug description: HP deskjet 2600 series driver cups ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: cups 2.4.1op1-1ubuntu4.1 ProcVersionSignature: Ubuntu 5.19.0-38.39~22.04.1-generic 5.19.17 Uname: Linux 5.19.0-38-generic x86_64 ApportVersion: 2.20.11-0ubuntu82.3 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Tue Apr 4 18:18:12 2023 InstallationDate: Installed on 2023-03-12 (23 days ago) InstallationMedia: Ubuntu 22.04.2 LTS "Jammy Jellyfish" - Release amd64 (20230223) KernLog: Lpstat: device for HP_DeskJet_2600_series_D60582_USB: implicitclass://HP_DeskJet_2600_series_D60582_USB/ MachineType: MSI MS-7817 Papersize: a4 PpdFiles: Error: command ['fgrep', '-H', '*NickName', '/etc/cups/ppd/HP_DeskJet_2600_series_D60582_USB.ppd'] failed with exit code 2: grep: /etc/cups/ppd/HP_DeskJet_2600_series_D60582_USB.ppd: Permission denied ProcEnviron: PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=fi_FI.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.19.0-38-generic root=UUID=7937a7b0-31fc-4dec-b3c2-51df4e876c20 ro quiet splash vt.handoff=7 SourcePackage: cups UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 04/21/2015 dmi.bios.release: 4.6 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: V10.9 dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: B85M-E45 (MS-7817) dmi.board.vendor: MSI dmi.board.version: 2.0 dmi.chassis.asset.tag: To be filled by O.E.M. dmi.chassis.type: 3 dmi.chassis.vendor: MSI dmi.chassis.version: 2.0 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrV10.9:bd04/21/2015:br4.6:svnMSI:pnMS-7817:pvr2.0:rvnMSI:rnB85M-E45(MS-7817):rvr2.0:cvnMSI:ct3:cvr2.0:skuTobefilledbyO.E.M.: dmi.product.family: To be filled by O.E.M. dmi.product.name: MS-7817 dmi.product.sku: To be filled by O.E.M. dmi.product.version: 2.0 dmi.sys.vendor: MSI To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/cups/+bug/2015259/+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 2015262] [NEW] gnome-control-center
Public bug reported: gnome-control-center logs fix ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: gnome-control-center 1:41.7-0ubuntu0.22.04.6 ProcVersionSignature: Ubuntu 5.19.0-38.39~22.04.1-generic 5.19.17 Uname: Linux 5.19.0-38-generic x86_64 ApportVersion: 2.20.11-0ubuntu82.3 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Tue Apr 4 18:21:28 2023 InstallationDate: Installed on 2023-03-12 (23 days ago) InstallationMedia: Ubuntu 22.04.2 LTS "Jammy Jellyfish" - Release amd64 (20230223) ProcEnviron: PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=fi_FI.UTF-8 SHELL=/bin/bash SourcePackage: gnome-control-center UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: gnome-control-center (Ubuntu) Importance: Undecided Status: Incomplete ** Tags: amd64 apport-bug jammy third-party-packages wayland-session ** Changed in: gnome-control-center (Ubuntu) Status: New => Incomplete -- 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/2015262 Title: gnome-control-center Status in gnome-control-center package in Ubuntu: Incomplete Bug description: gnome-control-center logs fix ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: gnome-control-center 1:41.7-0ubuntu0.22.04.6 ProcVersionSignature: Ubuntu 5.19.0-38.39~22.04.1-generic 5.19.17 Uname: Linux 5.19.0-38-generic x86_64 ApportVersion: 2.20.11-0ubuntu82.3 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Tue Apr 4 18:21:28 2023 InstallationDate: Installed on 2023-03-12 (23 days ago) InstallationMedia: Ubuntu 22.04.2 LTS "Jammy Jellyfish" - Release amd64 (20230223) ProcEnviron: PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=fi_FI.UTF-8 SHELL=/bin/bash SourcePackage: gnome-control-center UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-control-center/+bug/2015262/+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 2015264] [NEW] gnome-shell
Public bug reported: gnome-shell fix ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: gnome-shell 42.5-0ubuntu1 ProcVersionSignature: Ubuntu 5.19.0-38.39~22.04.1-generic 5.19.17 Uname: Linux 5.19.0-38-generic x86_64 ApportVersion: 2.20.11-0ubuntu82.3 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Tue Apr 4 18:22:35 2023 DisplayManager: gdm3 InstallationDate: Installed on 2023-03-12 (23 days ago) InstallationMedia: Ubuntu 22.04.2 LTS "Jammy Jellyfish" - Release amd64 (20230223) ProcEnviron: PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=fi_FI.UTF-8 SHELL=/bin/bash RelatedPackageVersions: mutter-common 42.5-0ubuntu1 SourcePackage: gnome-shell UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: gnome-shell (Ubuntu) Importance: Undecided Status: Incomplete ** Tags: amd64 apport-bug jammy third-party-packages wayland-session ** 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/2015264 Title: gnome-shell Status in gnome-shell package in Ubuntu: Incomplete Bug description: gnome-shell fix ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: gnome-shell 42.5-0ubuntu1 ProcVersionSignature: Ubuntu 5.19.0-38.39~22.04.1-generic 5.19.17 Uname: Linux 5.19.0-38-generic x86_64 ApportVersion: 2.20.11-0ubuntu82.3 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Tue Apr 4 18:22:35 2023 DisplayManager: gdm3 InstallationDate: Installed on 2023-03-12 (23 days ago) InstallationMedia: Ubuntu 22.04.2 LTS "Jammy Jellyfish" - Release amd64 (20230223) ProcEnviron: PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=fi_FI.UTF-8 SHELL=/bin/bash RelatedPackageVersions: mutter-common 42.5-0ubuntu1 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/2015264/+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 2006500] Re: gnome-control-center crashed with SIGSEGV in cc_display_config_manager_get_night_light_supported()
the fix has been commited upstream now ** Changed in: gnome-control-center (Ubuntu) Status: In Progress => Fix Committed -- 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/2006500 Title: gnome-control-center crashed with SIGSEGV in cc_display_config_manager_get_night_light_supported() Status in gnome-control-center: Unknown Status in gnome-control-center package in Ubuntu: Fix Committed Bug description: https://errors.ubuntu.com/problem/c917df7aa152ef3144e7356e4290c799e31475b3 gnome-control-center crashed when i try change refresh rate to other value than 60 Hz. Its crash after I tap keep changes ProblemType: Crash DistroRelease: Ubuntu 23.04 Package: gnome-control-center 1:44~alpha-0ubuntu1 ProcVersionSignature: Ubuntu 5.19.0-21.21-generic 5.19.7 Uname: Linux 5.19.0-21-generic x86_64 ApportVersion: 2.24.0-0ubuntu2 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Tue Feb 7 19:59:50 2023 ExecutablePath: /usr/bin/gnome-control-center InstallationDate: Installed on 2023-02-07 (0 days ago) InstallationMedia: Ubuntu 23.04 "Lunar Lobster" - Alpha amd64 (20221209) JournalErrors: lut 07 19:59:50 hostname kernel: show_signal_msg: 4 callbacks suppressed ProcCmdline: gnome-control-center SegvAnalysis: Segfault happened at: 0x55a5f2b496d4:mov(%rdi),%rax PC (0x55a5f2b496d4) ok source "(%rdi)" (0x) not located in a known VMA region (needed readable region)! destination "%rax" ok SegvReason: reading NULL VMA Signal: 11 SourcePackage: gnome-control-center StacktraceTop: ?? () g_closure_invoke () from /lib/x86_64-linux-gnu/libgobject-2.0.so.0 ?? () from /lib/x86_64-linux-gnu/libgobject-2.0.so.0 g_signal_emit_valist () from /lib/x86_64-linux-gnu/libgobject-2.0.so.0 g_signal_emit () from /lib/x86_64-linux-gnu/libgobject-2.0.so.0 Title: gnome-control-center crashed with SIGSEGV in g_closure_invoke() UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo users separator: To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-control-center/+bug/2006500/+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 2015248] [NEW] network-manager
Public bug reported: network-manager update and upgrades ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: network-manager 1.36.6-0ubuntu2 ProcVersionSignature: Ubuntu 5.19.0-38.39~22.04.1-generic 5.19.17 Uname: Linux 5.19.0-38-generic x86_64 ApportVersion: 2.20.11-0ubuntu82.3 Architecture: amd64 CRDA: N/A CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Tue Apr 4 17:25:11 2023 InstallationDate: Installed on 2023-03-12 (23 days ago) InstallationMedia: Ubuntu 22.04.2 LTS "Jammy Jellyfish" - Release amd64 (20230223) IpRoute: default via 84.251.176.1 dev enp2s0 proto dhcp metric 100 84.251.176.0/20 dev enp2s0 proto kernel scope link src 84.251.176.197 metric 100 169.254.0.0/16 dev enp2s0 scope link metric 1000 IwConfig: lono wireless extensions. enp2s0no wireless extensions. ProcEnviron: PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=fi_FI.UTF-8 SHELL=/bin/bash RfKill: SourcePackage: network-manager UpgradeStatus: No upgrade log present (probably fresh install) nmcli-con: NAME UUID TYPE TIMESTAMP TIMESTAMP-REAL AUTOCONNECT AUTOCONNECT-PRIORITY READONLY DBUS-PATH ACTIVE DEVICE STATE ACTIVE-PATH SLAVE FILENAME Kiinteä yhteys 1 075e5092-900f-3823-87fc-11d64ba859ae ethernet 1680618099 ti 4. huhtikuuta 2023 17.21.39 yes -999 no /org/freedesktop/NetworkManager/Settings/1 yes enp2s0 activated /org/freedesktop/NetworkManager/ActiveConnection/1 -- /run/NetworkManager/system-connections/Kiinteä yhteys 1.nmconnection nmcli-dev: DEVICE TYPE STATE IP4-CONNECTIVITY IP6-CONNECTIVITY DBUS-PATH CONNECTIONCON-UUID CON-PATH enp2s0 ethernet connected full limited /org/freedesktop/NetworkManager/Devices/2 Kiinteä yhteys 1 075e5092-900f-3823-87fc-11d64ba859ae /org/freedesktop/NetworkManager/ActiveConnection/1 lo loopback unmanaged unknown unknown /org/freedesktop/NetworkManager/Devices/1 ---- -- nmcli-nm: RUNNING VERSION STATE STARTUP CONNECTIVITY NETWORKING WIFI-HW WIFI WWAN-HW WWAN running 1.36.6 connected started full enabled enabled enabled enabled enabled ** Affects: network-manager (Ubuntu) Importance: Undecided Status: Incomplete ** Tags: amd64 apport-bug jammy wayland-session ** Changed in: network-manager (Ubuntu) Status: New => Incomplete -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to network-manager in Ubuntu. https://bugs.launchpad.net/bugs/2015248 Title: network-manager Status in network-manager package in Ubuntu: Incomplete Bug description: network-manager update and upgrades ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: network-manager 1.36.6-0ubuntu2 ProcVersionSignature: Ubuntu 5.19.0-38.39~22.04.1-generic 5.19.17 Uname: Linux 5.19.0-38-generic x86_64 ApportVersion: 2.20.11-0ubuntu82.3 Architecture: amd64 CRDA: N/A CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Tue Apr 4 17:25:11 2023 InstallationDate: Installed on 2023-03-12 (23 days ago) InstallationMedia: Ubuntu 22.04.2 LTS "Jammy Jellyfish" - Release amd64 (20230223) IpRoute: default via 84.251.176.1 dev enp2s0 proto dhcp metric 100 84.251.176.0/20 dev enp2s0 proto kernel scope link src 84.251.176.197 metric 100 169.254.0.0/16 dev enp2s0 scope link metric 1000 IwConfig: lono wireless extensions. enp2s0no wireless extensions. ProcEnviron: PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=fi_FI.UTF-8 SHELL=/bin/bash RfKill: SourcePackage: network-manager UpgradeStatus: No upgrade log present (probably fresh install) nmcli-con: NAME UUID TYPE TIMESTAMP TIMESTAMP-REAL AUTOCONNECT AUTOCONNECT-PRIORITY READONLY DBUS-PATH ACTIVE DEVICE STATE ACTIVE-PATH SLAVE FILENAME Kiinteä yhteys 1 075e5092-900f-3823-87fc-11d64ba859ae ethernet 1680618099 ti 4. huhtikuuta 2023 17.21.39 yes -999 no /org/freedesktop/NetworkManager/Settings/1 yes enp2s0 activated /org/freedesktop/NetworkManager/ActiveConnection/1 -- /run/NetworkManager/system-connections/Kiinteä yhteys 1.nmconnection nmcli-dev: DEVICE TYPE STATE IP4-CONNECTIVITY IP6-CONNECTIVITY DBUS-PATH
[Desktop-packages] [Bug 2015251] [NEW] hp printer
Public bug reported: hp printer driver ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: hplip 3.21.12+dfsg0-1 ProcVersionSignature: Ubuntu 5.19.0-38.39~22.04.1-generic 5.19.17 Uname: Linux 5.19.0-38-generic x86_64 ApportVersion: 2.20.11-0ubuntu82.3 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Tue Apr 4 17:30:55 2023 InstallationDate: Installed on 2023-03-12 (23 days ago) InstallationMedia: Ubuntu 22.04.2 LTS "Jammy Jellyfish" - Release amd64 (20230223) Lpstat: device for HP_DeskJet_2600_series_D60582_USB: implicitclass://HP_DeskJet_2600_series_D60582_USB/ MachineType: MSI MS-7817 Papersize: a4 PpdFiles: Error: command ['fgrep', '-H', '*NickName', '/etc/cups/ppd/HP_DeskJet_2600_series_D60582_USB.ppd'] failed with exit code 2: grep: /etc/cups/ppd/HP_DeskJet_2600_series_D60582_USB.ppd: Permission denied ProcEnviron: PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=fi_FI.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.19.0-38-generic root=UUID=7937a7b0-31fc-4dec-b3c2-51df4e876c20 ro quiet splash vt.handoff=7 SourcePackage: hplip UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 04/21/2015 dmi.bios.release: 4.6 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: V10.9 dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: B85M-E45 (MS-7817) dmi.board.vendor: MSI dmi.board.version: 2.0 dmi.chassis.asset.tag: To be filled by O.E.M. dmi.chassis.type: 3 dmi.chassis.vendor: MSI dmi.chassis.version: 2.0 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrV10.9:bd04/21/2015:br4.6:svnMSI:pnMS-7817:pvr2.0:rvnMSI:rnB85M-E45(MS-7817):rvr2.0:cvnMSI:ct3:cvr2.0:skuTobefilledbyO.E.M.: dmi.product.family: To be filled by O.E.M. dmi.product.name: MS-7817 dmi.product.sku: To be filled by O.E.M. dmi.product.version: 2.0 dmi.sys.vendor: MSI ** Affects: hplip (Ubuntu) Importance: Undecided Status: Incomplete ** Tags: amd64 apport-bug jammy wayland-session ** Changed in: hplip (Ubuntu) Status: New => Incomplete -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to hplip in Ubuntu. https://bugs.launchpad.net/bugs/2015251 Title: hp printer Status in hplip package in Ubuntu: Incomplete Bug description: hp printer driver ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: hplip 3.21.12+dfsg0-1 ProcVersionSignature: Ubuntu 5.19.0-38.39~22.04.1-generic 5.19.17 Uname: Linux 5.19.0-38-generic x86_64 ApportVersion: 2.20.11-0ubuntu82.3 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Tue Apr 4 17:30:55 2023 InstallationDate: Installed on 2023-03-12 (23 days ago) InstallationMedia: Ubuntu 22.04.2 LTS "Jammy Jellyfish" - Release amd64 (20230223) Lpstat: device for HP_DeskJet_2600_series_D60582_USB: implicitclass://HP_DeskJet_2600_series_D60582_USB/ MachineType: MSI MS-7817 Papersize: a4 PpdFiles: Error: command ['fgrep', '-H', '*NickName', '/etc/cups/ppd/HP_DeskJet_2600_series_D60582_USB.ppd'] failed with exit code 2: grep: /etc/cups/ppd/HP_DeskJet_2600_series_D60582_USB.ppd: Permission denied ProcEnviron: PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=fi_FI.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.19.0-38-generic root=UUID=7937a7b0-31fc-4dec-b3c2-51df4e876c20 ro quiet splash vt.handoff=7 SourcePackage: hplip UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 04/21/2015 dmi.bios.release: 4.6 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: V10.9 dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: B85M-E45 (MS-7817) dmi.board.vendor: MSI dmi.board.version: 2.0 dmi.chassis.asset.tag: To be filled by O.E.M. dmi.chassis.type: 3 dmi.chassis.vendor: MSI dmi.chassis.version: 2.0 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrV10.9:bd04/21/2015:br4.6:svnMSI:pnMS-7817:pvr2.0:rvnMSI:rnB85M-E45(MS-7817):rvr2.0:cvnMSI:ct3:cvr2.0:skuTobefilledbyO.E.M.: dmi.product.family: To be filled by O.E.M. dmi.product.name: MS-7817 dmi.product.sku: To be filled by O.E.M. dmi.product.version: 2.0 dmi.sys.vendor: MSI To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/hplip/+bug/2015251/+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 2015252] [NEW] printer simple-scan
Public bug reported: HP deskjet 2600 series simple scan driver logs ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: simple-scan 42.0-1 ProcVersionSignature: Ubuntu 5.19.0-38.39~22.04.1-generic 5.19.17 Uname: Linux 5.19.0-38-generic x86_64 ApportVersion: 2.20.11-0ubuntu82.3 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Tue Apr 4 17:32:27 2023 InstallationDate: Installed on 2023-03-12 (23 days ago) InstallationMedia: Ubuntu 22.04.2 LTS "Jammy Jellyfish" - Release amd64 (20230223) MachineType: MSI MS-7817 ProcEnviron: PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=fi_FI.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.19.0-38-generic root=UUID=7937a7b0-31fc-4dec-b3c2-51df4e876c20 ro quiet splash vt.handoff=7 SourcePackage: simple-scan UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 04/21/2015 dmi.bios.release: 4.6 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: V10.9 dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: B85M-E45 (MS-7817) dmi.board.vendor: MSI dmi.board.version: 2.0 dmi.chassis.asset.tag: To be filled by O.E.M. dmi.chassis.type: 3 dmi.chassis.vendor: MSI dmi.chassis.version: 2.0 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrV10.9:bd04/21/2015:br4.6:svnMSI:pnMS-7817:pvr2.0:rvnMSI:rnB85M-E45(MS-7817):rvr2.0:cvnMSI:ct3:cvr2.0:skuTobefilledbyO.E.M.: dmi.product.family: To be filled by O.E.M. dmi.product.name: MS-7817 dmi.product.sku: To be filled by O.E.M. dmi.product.version: 2.0 dmi.sys.vendor: MSI ** Affects: simple-scan (Ubuntu) Importance: Undecided Status: Incomplete ** Tags: amd64 apport-bug jammy third-party-packages wayland-session ** Changed in: simple-scan (Ubuntu) Status: New => Incomplete -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to simple-scan in Ubuntu. https://bugs.launchpad.net/bugs/2015252 Title: printer simple-scan Status in simple-scan package in Ubuntu: Incomplete Bug description: HP deskjet 2600 series simple scan driver logs ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: simple-scan 42.0-1 ProcVersionSignature: Ubuntu 5.19.0-38.39~22.04.1-generic 5.19.17 Uname: Linux 5.19.0-38-generic x86_64 ApportVersion: 2.20.11-0ubuntu82.3 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Tue Apr 4 17:32:27 2023 InstallationDate: Installed on 2023-03-12 (23 days ago) InstallationMedia: Ubuntu 22.04.2 LTS "Jammy Jellyfish" - Release amd64 (20230223) MachineType: MSI MS-7817 ProcEnviron: PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=fi_FI.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.19.0-38-generic root=UUID=7937a7b0-31fc-4dec-b3c2-51df4e876c20 ro quiet splash vt.handoff=7 SourcePackage: simple-scan UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 04/21/2015 dmi.bios.release: 4.6 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: V10.9 dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: B85M-E45 (MS-7817) dmi.board.vendor: MSI dmi.board.version: 2.0 dmi.chassis.asset.tag: To be filled by O.E.M. dmi.chassis.type: 3 dmi.chassis.vendor: MSI dmi.chassis.version: 2.0 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrV10.9:bd04/21/2015:br4.6:svnMSI:pnMS-7817:pvr2.0:rvnMSI:rnB85M-E45(MS-7817):rvr2.0:cvnMSI:ct3:cvr2.0:skuTobefilledbyO.E.M.: dmi.product.family: To be filled by O.E.M. dmi.product.name: MS-7817 dmi.product.sku: To be filled by O.E.M. dmi.product.version: 2.0 dmi.sys.vendor: MSI To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/simple-scan/+bug/2015252/+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 2012902] Re: netplan plugin: generated NM config when using globbing will be used for only one connection
** Also affects: netplan Importance: Undecided Status: New ** Changed in: netplan Status: New => Triaged ** Changed in: netplan Importance: Undecided => Medium -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to network-manager in Ubuntu. https://bugs.launchpad.net/bugs/2012902 Title: netplan plugin: generated NM config when using globbing will be used for only one connection Status in netplan: Triaged Status in network-manager package in Ubuntu: New Bug description: There is a mismatch between what netplan expresses when using globbing in a netplan file and what NM understands when using a match setting. For instance: network: version: 2 ethernets: all-en: match: name: "en*" dhcp4: true Generates a NM connection in /run/NetworkManager/system-connections: ... [match] interface-name=en*; ... But an NM connection can only match one interface, so if two interfaces like ens2 and ens3 exist, only one of them will be configured, even though the netplan configuration is expected to be applied to both. Solving this might involve generating one NM connection in the netplan plugin per detected interface. To manage notifications about this bug go to: https://bugs.launchpad.net/netplan/+bug/2012902/+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 2013107] Re: [lunar] GNOME does not display high contrast app icons
It looks like indeed a bug due to the new Icon theme support, in GNOME Shell though. ** Changed in: yaru-theme (Ubuntu) Status: New => Won't Fix -- 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/2013107 Title: [lunar] GNOME does not display high contrast app icons Status in Yaru Theme: New Status in gnome-shell package in Ubuntu: Triaged Status in gnome-themes-extra package in Ubuntu: Invalid Status in yaru-theme package in Ubuntu: Won't Fix Bug description: gnome-accessibility-themes (3.28-2ubuntu1) offers an incomplete set of high contrast icons, resulting in a very inconsistent look when the user enables Accessibility > Seeing > High Contrast from gnome- control-center. A screenshot showing of the current sad state of affairs is attached. To manage notifications about this bug go to: https://bugs.launchpad.net/yaru/+bug/2013107/+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 2015237] [NEW] evince logs
Public bug reported: evince logs kernel ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: evince 42.3-0ubuntu3 ProcVersionSignature: Ubuntu 5.19.0-38.39~22.04.1-generic 5.19.17 Uname: Linux 5.19.0-38-generic x86_64 ApportVersion: 2.20.11-0ubuntu82.3 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Tue Apr 4 15:49:21 2023 InstallationDate: Installed on 2023-03-12 (23 days ago) InstallationMedia: Ubuntu 22.04.2 LTS "Jammy Jellyfish" - Release amd64 (20230223) KernLog: ProcEnviron: PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=fi_FI.UTF-8 SHELL=/bin/bash SourcePackage: evince UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: evince (Ubuntu) Importance: Undecided Status: Incomplete ** Tags: amd64 apport-bug jammy wayland-session ** Changed in: evince (Ubuntu) Status: New => Incomplete -- 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/2015237 Title: evince logs Status in evince package in Ubuntu: Incomplete Bug description: evince logs kernel ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: evince 42.3-0ubuntu3 ProcVersionSignature: Ubuntu 5.19.0-38.39~22.04.1-generic 5.19.17 Uname: Linux 5.19.0-38-generic x86_64 ApportVersion: 2.20.11-0ubuntu82.3 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Tue Apr 4 15:49:21 2023 InstallationDate: Installed on 2023-03-12 (23 days ago) InstallationMedia: Ubuntu 22.04.2 LTS "Jammy Jellyfish" - Release amd64 (20230223) KernLog: ProcEnviron: PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=fi_FI.UTF-8 SHELL=/bin/bash SourcePackage: evince UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/evince/+bug/2015237/+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 938751] Re: Images are washed out or colors are skewed in some apps (particularly Image Viewer and Chrome)
** Changed in: eog Status: Unknown => New -- 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/938751 Title: Images are washed out or colors are skewed in some apps (particularly Image Viewer and Chrome) Status in Eye of GNOME: New Status in GNOME Shell: New Status in chromium-browser package in Ubuntu: Confirmed Status in colord package in Ubuntu: Confirmed Status in eog package in Ubuntu: Confirmed Status in inkscape package in Ubuntu: Confirmed Bug description: Images are washed out or colors are skewed in some apps, notably Chrome/Chromium and Image Viewer (eog). Workaround: 1. Settings > Colour > turn off the toggle switch for your monitor. 2. Restart any affected apps. Originally reported in https://bugzilla.gnome.org/show_bug.cgi?id=675645 To manage notifications about this bug go to: https://bugs.launchpad.net/eog/+bug/938751/+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 2012282] Re: [gnome-shell 44~rc-1ubuntu2, Ubuntu 23.04 (development branch)] Wrong background color in application folders
** Changed in: yaru-theme (Ubuntu) Status: Fix Committed => Fix Released -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to yaru-theme in Ubuntu. https://bugs.launchpad.net/bugs/2012282 Title: [gnome-shell 44~rc-1ubuntu2, Ubuntu 23.04 (development branch)] Wrong background color in application folders Status in Yaru Theme: Unknown Status in yaru-theme package in Ubuntu: Fix Released Bug description: Problem summary: After upgrading from Ubuntu 22.10 to Ubuntu 23.04 (development branch) the gnome-shell application folders background is shown in white color instead of dark grey color making impossible to read it's contents. I'm using the default Ubuntu theming. I've attached two screenshots: - Ubuntu_22_10_OK.png: where you can see that application folder background is dark grey as expected. - Ubuntu_23_04_BAD.png: where you can see that application folder background is white and content is unreadable. Additional data: System Model: Raspberry Pi 4 Model B Rev 1.4 8Gb Kernel: Linux fpgrpi 5.19.0-1015-raspi #22-Ubuntu SMP PREEMPT Mon Mar 6 10:35:33 UTC 2023 aarch64 aarch64 aarch64 GNU/Linux # lsb_release -rd No LSB modules are available. Description: Ubuntu Lunar Lobster (development branch) Release: 23.04 # apt-cache policy gnome-shell gnome-shell: Instalados: 44~rc-1ubuntu2 Candidato: 44~rc-1ubuntu2 Tabla de versión: *** 44~rc-1ubuntu2 500 500 http://ports.ubuntu.com/ubuntu-ports lunar/main arm64 Packages 100 /var/lib/dpkg/status To manage notifications about this bug go to: https://bugs.launchpad.net/yaru/+bug/2012282/+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 2015228] [NEW] Bluetooth not working rfkill Soft blocked: yes
Public bug reported: Hi Devs, Hope you're all keeping well. The problem I have is similar to: https://answers.launchpad.net/ubuntu/+question/699306 Basically Bluetooth doesn't work on installed Ubuntu 22.04.2 neither the laptop (Dell Inspirion 7577) internal device (Intel 8265) or a USB dongle (not sure it was recommended for raspberry pi and works on desktop with 22.04 just fine: 0a12:0001 Cambridge Silicon Radio, Ltd Bluetooth Dongle (HCI mode). It works fine in a live USB image on the same laptop. I get the following with rfkill: rfkill list all 1: hci1: Bluetooth Soft blocked: yes Hard blocked: no 2: phy0: Wireless LAN Soft blocked: no Hard blocked: no 3: hci0: Bluetooth Soft blocked: yes Hard blocked: no - Unblocking with rfkill doesn't work - Restarting bluetooth doesn't work - Getting another device doesn't work I recall having issues with WiFi around the time I got the laptop, and recall changing settings for that - but I couldn't tell you what they were (~2017 ish). Plus I believe I've reinstalled since then due to an SSD failure. It has been upgraded from LTS to LTS since 18.04 though. Any thoughts, ideas, or questions, I'm more than happy to try anything, or even help as much as possible to help get this resolved, its been going on for a couple of years now and mainly ignored it because I was mostly fine without, but I really need it to work now and appreciate any help on this. Thanks so much in advance, love you all for the work you do. ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: bluetooth (not installed) ProcVersionSignature: Ubuntu 5.15.0-69.76-generic 5.15.87 Uname: Linux 5.15.0-69-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu82.3 Architecture: amd64 CasperMD5CheckResult: unknown Date: Tue Apr 4 12:47:27 2023 InstallationDate: Installed on 2020-04-09 (1089 days ago) InstallationMedia: Ubuntu 18.04.4 LTS "Bionic Beaver" - Release amd64 (20200203.1) InterestingModules: rfcomm bnep btusb bluetooth MachineType: Dell Inc. Inspiron 7577 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.15.0-69-generic root=UUID=761c1e7a-7759-4f7d-a985-33c7654bccad ro quiet splash vt.handoff=7 SourcePackage: bluez UpgradeStatus: Upgraded to jammy on 2023-01-12 (82 days ago) dmi.bios.date: 03/18/2022 dmi.bios.release: 1.17 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.17.0 dmi.board.name: 0XCNGT dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 10 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr1.17.0:bd03/18/2022:br1.17:svnDellInc.:pnInspiron7577:pvr:rvnDellInc.:rn0XCNGT:rvrA00:cvnDellInc.:ct10:cvr:sku07FA: dmi.product.family: Inspiron dmi.product.name: Inspiron 7577 dmi.product.sku: 07FA dmi.sys.vendor: Dell Inc. ** Affects: bluez (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug jammy -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to bluez in Ubuntu. https://bugs.launchpad.net/bugs/2015228 Title: Bluetooth not working rfkill Soft blocked: yes Status in bluez package in Ubuntu: New Bug description: Hi Devs, Hope you're all keeping well. The problem I have is similar to: https://answers.launchpad.net/ubuntu/+question/699306 Basically Bluetooth doesn't work on installed Ubuntu 22.04.2 neither the laptop (Dell Inspirion 7577) internal device (Intel 8265) or a USB dongle (not sure it was recommended for raspberry pi and works on desktop with 22.04 just fine: 0a12:0001 Cambridge Silicon Radio, Ltd Bluetooth Dongle (HCI mode). It works fine in a live USB image on the same laptop. I get the following with rfkill: rfkill list all 1: hci1: Bluetooth Soft blocked: yes Hard blocked: no 2: phy0: Wireless LAN Soft blocked: no Hard blocked: no 3: hci0: Bluetooth Soft blocked: yes Hard blocked: no - Unblocking with rfkill doesn't work - Restarting bluetooth doesn't work - Getting another device doesn't work I recall having issues with WiFi around the time I got the laptop, and recall changing settings for that - but I couldn't tell you what they were (~2017 ish). Plus I believe I've reinstalled since then due to an SSD failure. It has been upgraded from LTS to LTS since 18.04 though. Any thoughts, ideas, or questions, I'm more than happy to try anything, or even help as much as possible to help get this resolved, its been going on for a couple of years now and mainly ignored it because I was mostly fine without, but I really need it to work now and appreciate any help on this. Thanks so much in advance, love you all for the work you do. ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: bluetooth (not installed) ProcVersionSignature: Ubuntu 5.15.0-69.76-generic 5.15.87 Uname: Linux 5.15.0-69-generic x86_64 NonfreeKernelModules: nvidia_modeset
[Desktop-packages] [Bug 2015219] Re: ASUS COMPUTER INC laptop
** Changed in: xorg (Ubuntu) Status: New => Incomplete -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to xorg in Ubuntu. https://bugs.launchpad.net/bugs/2015219 Title: ASUS COMPUTER INC laptop Status in xorg package in Ubuntu: Incomplete Bug description: ASUS COMPUTER INC laptop reboot and restart too slow xorg drivers my laptop working too slow ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: xorg 1:7.7+23ubuntu2 ProcVersionSignature: Ubuntu 5.19.0-38.39~22.04.1-generic 5.19.17 Uname: Linux 5.19.0-38-generic x86_64 ApportVersion: 2.20.11-0ubuntu82.3 Architecture: amd64 BootLog: Error: [Errno 13] Lupa evätty: '/var/log/boot.log' CasperMD5CheckResult: pass CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Tue Apr 4 14:09:21 2023 DistUpgraded: Fresh install DistroCodename: jammy DistroVariant: ubuntu DpkgLog: ExtraDebuggingInterest: Yes, including running git bisection searches GraphicsCard: Intel Corporation Atom/Celeron/Pentium Processor x5-E8000/J3xxx/N3xxx Integrated Graphics Controller [8086:22b1] (rev 21) (prog-if 00 [VGA controller]) Subsystem: ASUSTeK Computer Inc. Atom/Celeron/Pentium Processor x5-E8000/J3xxx/N3xxx Integrated Graphics Controller [1043:1d5d] InstallationDate: Installed on 2023-03-13 (22 days ago) InstallationMedia: Ubuntu 22.04.2 LTS "Jammy Jellyfish" - Release amd64 (20230223) MachineType: ASUSTeK COMPUTER INC. E402SA ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.19.0-38-generic root=UUID=45b0810a-3f7a-47d9-9368-7204c1732d88 ro quiet splash vt.handoff=7 SourcePackage: xorg UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 12/14/2015 dmi.bios.release: 5.6 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: E402SA.208 dmi.board.asset.tag: ATN12345678901234567 dmi.board.name: E402SA dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: 1.0 dmi.chassis.asset.tag: ATN12345678901234567 dmi.chassis.type: 10 dmi.chassis.vendor: ASUSTeK COMPUTER INC. dmi.chassis.version: 1.0 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrE402SA.208:bd12/14/2015:br5.6:svnASUSTeKCOMPUTERINC.:pnE402SA:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnE402SA:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0:skuASUS-NotebookSKU: dmi.product.family: E dmi.product.name: E402SA dmi.product.sku: ASUS-NotebookSKU dmi.product.version: 1.0 dmi.sys.vendor: ASUSTeK COMPUTER INC. version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.113-2~ubuntu0.22.04.1 version.libgl1-mesa-dri: libgl1-mesa-dri 23.0.1~kisak1~j version.libgl1-mesa-glx: libgl1-mesa-glx N/A version.xserver-xorg-core: xserver-xorg-core 2:21.1.3-2ubuntu2.9 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-2ubuntu1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20210115-1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.17-2build1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/2015219/+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 2015219] [NEW] ASUS COMPUTER INC laptop
Public bug reported: ASUS COMPUTER INC laptop reboot and restart too slow xorg drivers my laptop working too slow ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: xorg 1:7.7+23ubuntu2 ProcVersionSignature: Ubuntu 5.19.0-38.39~22.04.1-generic 5.19.17 Uname: Linux 5.19.0-38-generic x86_64 ApportVersion: 2.20.11-0ubuntu82.3 Architecture: amd64 BootLog: Error: [Errno 13] Lupa evätty: '/var/log/boot.log' CasperMD5CheckResult: pass CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Tue Apr 4 14:09:21 2023 DistUpgraded: Fresh install DistroCodename: jammy DistroVariant: ubuntu DpkgLog: ExtraDebuggingInterest: Yes, including running git bisection searches GraphicsCard: Intel Corporation Atom/Celeron/Pentium Processor x5-E8000/J3xxx/N3xxx Integrated Graphics Controller [8086:22b1] (rev 21) (prog-if 00 [VGA controller]) Subsystem: ASUSTeK Computer Inc. Atom/Celeron/Pentium Processor x5-E8000/J3xxx/N3xxx Integrated Graphics Controller [1043:1d5d] InstallationDate: Installed on 2023-03-13 (22 days ago) InstallationMedia: Ubuntu 22.04.2 LTS "Jammy Jellyfish" - Release amd64 (20230223) MachineType: ASUSTeK COMPUTER INC. E402SA ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.19.0-38-generic root=UUID=45b0810a-3f7a-47d9-9368-7204c1732d88 ro quiet splash vt.handoff=7 SourcePackage: xorg UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 12/14/2015 dmi.bios.release: 5.6 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: E402SA.208 dmi.board.asset.tag: ATN12345678901234567 dmi.board.name: E402SA dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: 1.0 dmi.chassis.asset.tag: ATN12345678901234567 dmi.chassis.type: 10 dmi.chassis.vendor: ASUSTeK COMPUTER INC. dmi.chassis.version: 1.0 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrE402SA.208:bd12/14/2015:br5.6:svnASUSTeKCOMPUTERINC.:pnE402SA:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnE402SA:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0:skuASUS-NotebookSKU: dmi.product.family: E dmi.product.name: E402SA dmi.product.sku: ASUS-NotebookSKU dmi.product.version: 1.0 dmi.sys.vendor: ASUSTeK COMPUTER INC. version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.113-2~ubuntu0.22.04.1 version.libgl1-mesa-dri: libgl1-mesa-dri 23.0.1~kisak1~j version.libgl1-mesa-glx: libgl1-mesa-glx N/A version.xserver-xorg-core: xserver-xorg-core 2:21.1.3-2ubuntu2.9 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-2ubuntu1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20210115-1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.17-2build1 ** Affects: xorg (Ubuntu) Importance: Undecided Status: Incomplete ** Tags: amd64 apport-bug jammy third-party-packages ubuntu wayland-session -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to xorg in Ubuntu. https://bugs.launchpad.net/bugs/2015219 Title: ASUS COMPUTER INC laptop Status in xorg package in Ubuntu: Incomplete Bug description: ASUS COMPUTER INC laptop reboot and restart too slow xorg drivers my laptop working too slow ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: xorg 1:7.7+23ubuntu2 ProcVersionSignature: Ubuntu 5.19.0-38.39~22.04.1-generic 5.19.17 Uname: Linux 5.19.0-38-generic x86_64 ApportVersion: 2.20.11-0ubuntu82.3 Architecture: amd64 BootLog: Error: [Errno 13] Lupa evätty: '/var/log/boot.log' CasperMD5CheckResult: pass CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Tue Apr 4 14:09:21 2023 DistUpgraded: Fresh install DistroCodename: jammy DistroVariant: ubuntu DpkgLog: ExtraDebuggingInterest: Yes, including running git bisection searches GraphicsCard: Intel Corporation Atom/Celeron/Pentium Processor x5-E8000/J3xxx/N3xxx Integrated Graphics Controller [8086:22b1] (rev 21) (prog-if 00 [VGA controller]) Subsystem: ASUSTeK Computer Inc. Atom/Celeron/Pentium Processor x5-E8000/J3xxx/N3xxx Integrated Graphics Controller [1043:1d5d] InstallationDate: Installed on 2023-03-13 (22 days ago) InstallationMedia: Ubuntu 22.04.2 LTS "Jammy Jellyfish" - Release amd64 (20230223) MachineType: ASUSTeK COMPUTER INC. E402SA ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.19.0-38-generic root=UUID=45b0810a-3f7a-47d9-9368-7204c1732d88 ro quiet splash vt.handoff=7 SourcePackage: xorg UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 12/14/2015 dmi.bios.release: 5.6 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: E402SA.208 dmi.board.asset.tag: ATN12345678901234567 dmi.board.name: E402SA dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: 1.0 dmi.chassis.asset.tag: ATN12345678901234567 dmi.chassis.type: 10 dmi.chassis.vendor: ASUSTeK COMPUTER INC. dmi.chassis.version: 1.0 dmi.modalias:
[Desktop-packages] [Bug 2006500] Re: gnome-control-center crashed with SIGSEGV in cc_display_config_manager_get_night_light_supported()
In progress upstream: https://gitlab.gnome.org/GNOME/gnome-control- center/-/merge_requests/1762 ** Description changed: + https://errors.ubuntu.com/problem/c917df7aa152ef3144e7356e4290c799e31475b3 + gnome-control-center crashed when i try change refresh rate to other value than 60 Hz. Its crash after I tap keep changes ProblemType: Crash DistroRelease: Ubuntu 23.04 Package: gnome-control-center 1:44~alpha-0ubuntu1 ProcVersionSignature: Ubuntu 5.19.0-21.21-generic 5.19.7 Uname: Linux 5.19.0-21-generic x86_64 ApportVersion: 2.24.0-0ubuntu2 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Tue Feb 7 19:59:50 2023 ExecutablePath: /usr/bin/gnome-control-center InstallationDate: Installed on 2023-02-07 (0 days ago) InstallationMedia: Ubuntu 23.04 "Lunar Lobster" - Alpha amd64 (20221209) JournalErrors: lut 07 19:59:50 hostname kernel: show_signal_msg: 4 callbacks suppressed ProcCmdline: gnome-control-center SegvAnalysis: - Segfault happened at: 0x55a5f2b496d4:mov(%rdi),%rax - PC (0x55a5f2b496d4) ok - source "(%rdi)" (0x) not located in a known VMA region (needed readable region)! - destination "%rax" ok + Segfault happened at: 0x55a5f2b496d4:mov(%rdi),%rax + PC (0x55a5f2b496d4) ok + source "(%rdi)" (0x) not located in a known VMA region (needed readable region)! + destination "%rax" ok SegvReason: reading NULL VMA Signal: 11 SourcePackage: gnome-control-center StacktraceTop: - ?? () - g_closure_invoke () from /lib/x86_64-linux-gnu/libgobject-2.0.so.0 - ?? () from /lib/x86_64-linux-gnu/libgobject-2.0.so.0 - g_signal_emit_valist () from /lib/x86_64-linux-gnu/libgobject-2.0.so.0 - g_signal_emit () from /lib/x86_64-linux-gnu/libgobject-2.0.so.0 + ?? () + g_closure_invoke () from /lib/x86_64-linux-gnu/libgobject-2.0.so.0 + ?? () from /lib/x86_64-linux-gnu/libgobject-2.0.so.0 + g_signal_emit_valist () from /lib/x86_64-linux-gnu/libgobject-2.0.so.0 + g_signal_emit () from /lib/x86_64-linux-gnu/libgobject-2.0.so.0 Title: gnome-control-center crashed with SIGSEGV in g_closure_invoke() UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo users separator: ** Also affects: gnome-control-center via https://gitlab.gnome.org/GNOME/gnome-control-center/-/issues/2333 Importance: Unknown Status: Unknown ** Changed in: gnome-control-center (Ubuntu) Status: Triaged => In Progress -- 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/2006500 Title: gnome-control-center crashed with SIGSEGV in cc_display_config_manager_get_night_light_supported() Status in gnome-control-center: Unknown Status in gnome-control-center package in Ubuntu: In Progress Bug description: https://errors.ubuntu.com/problem/c917df7aa152ef3144e7356e4290c799e31475b3 gnome-control-center crashed when i try change refresh rate to other value than 60 Hz. Its crash after I tap keep changes ProblemType: Crash DistroRelease: Ubuntu 23.04 Package: gnome-control-center 1:44~alpha-0ubuntu1 ProcVersionSignature: Ubuntu 5.19.0-21.21-generic 5.19.7 Uname: Linux 5.19.0-21-generic x86_64 ApportVersion: 2.24.0-0ubuntu2 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Tue Feb 7 19:59:50 2023 ExecutablePath: /usr/bin/gnome-control-center InstallationDate: Installed on 2023-02-07 (0 days ago) InstallationMedia: Ubuntu 23.04 "Lunar Lobster" - Alpha amd64 (20221209) JournalErrors: lut 07 19:59:50 hostname kernel: show_signal_msg: 4 callbacks suppressed ProcCmdline: gnome-control-center SegvAnalysis: Segfault happened at: 0x55a5f2b496d4:mov(%rdi),%rax PC (0x55a5f2b496d4) ok source "(%rdi)" (0x) not located in a known VMA region (needed readable region)! destination "%rax" ok SegvReason: reading NULL VMA Signal: 11 SourcePackage: gnome-control-center StacktraceTop: ?? () g_closure_invoke () from /lib/x86_64-linux-gnu/libgobject-2.0.so.0 ?? () from /lib/x86_64-linux-gnu/libgobject-2.0.so.0 g_signal_emit_valist () from /lib/x86_64-linux-gnu/libgobject-2.0.so.0 g_signal_emit () from /lib/x86_64-linux-gnu/libgobject-2.0.so.0 Title: gnome-control-center crashed with SIGSEGV in g_closure_invoke() UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo users separator: To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-control-center/+bug/2006500/+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 2015218] Re: /usr/libexec/ayatana-indicator-messages/ayatana-indicator-messages-service:11:ACT_IS_USER:_act_user_update_from_object_path:fetch_user_incrementally:on_find_user_b
*** This bug is a duplicate of bug 2012879 *** https://bugs.launchpad.net/bugs/2012879 ** This bug has been marked a duplicate of bug 2012879 indicator-messages-service crashed with SIGSEGV in ACT_IS_USER() from _act_user_update_from_object_path() from fetch_user_incrementally() from on_find_user_by_name_finished() from g_task_return_now() -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to ayatana-indicator-messages in Ubuntu. https://bugs.launchpad.net/bugs/2015218 Title: /usr/libexec/ayatana-indicator-messages/ayatana-indicator-messages- service:11:ACT_IS_USER:_act_user_update_from_object_path:fetch_user_incrementally:on_find_user_by_name_finished:g_task_return_now Status in ayatana-indicator-messages package in Ubuntu: New Bug description: The Ubuntu Error Tracker has been receiving reports about a problem regarding ayatana-indicator-messages. This problem was most recently seen with package version 22.9.0-1, the problem page at https://errors.ubuntu.com/problem/c068c002f0e2d03cb35cbae65bb611d9af61d7fb contains more details, including versions of packages affected, stacktrace or traceback, and individual crash reports. If you do not have access to the Ubuntu Error Tracker and are a software developer, you can request it at http://forms.canonical.com/reports/. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ayatana-indicator-messages/+bug/2015218/+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 2015054] Re: /usr/bin/gnome-control-center:11:cc_display_config_manager_get_night_light_supported:dialog_update_state:g_closure_invoke:signal_emit_unlocked_R:g_signal_emit_vali
*** This bug is a duplicate of bug 2006500 *** https://bugs.launchpad.net/bugs/2006500 ** This bug has been marked a duplicate of bug 2006500 gnome-control-center crashed with SIGSEGV in cc_display_config_manager_get_night_light_supported() -- 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/2015054 Title: /usr/bin/gnome-control- center:11:cc_display_config_manager_get_night_light_supported:dialog_update_state:g_closure_invoke:signal_emit_unlocked_R:g_signal_emit_valist Status in gnome-control-center package in Ubuntu: Invalid Bug description: The Ubuntu Error Tracker has been receiving reports about a problem regarding gnome-control-center. This problem was most recently seen with package version 1:44.0-1ubuntu4, the problem page at https://errors.ubuntu.com/problem/c917df7aa152ef3144e7356e4290c799e31475b3 contains more details, including versions of packages affected, stacktrace or traceback, and individual crash reports. If you do not have access to the Ubuntu Error Tracker and are a software developer, you can request it at http://forms.canonical.com/reports/. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-control-center/+bug/2015054/+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 2015218] [NEW] /usr/libexec/ayatana-indicator-messages/ayatana-indicator-messages-service:11:ACT_IS_USER:_act_user_update_from_object_path:fetch_user_incrementally:on_find_user
*** This bug is a duplicate of bug 2012879 *** https://bugs.launchpad.net/bugs/2012879 Public bug reported: The Ubuntu Error Tracker has been receiving reports about a problem regarding ayatana-indicator-messages. This problem was most recently seen with package version 22.9.0-1, the problem page at https://errors.ubuntu.com/problem/c068c002f0e2d03cb35cbae65bb611d9af61d7fb contains more details, including versions of packages affected, stacktrace or traceback, and individual crash reports. If you do not have access to the Ubuntu Error Tracker and are a software developer, you can request it at http://forms.canonical.com/reports/. ** Affects: ayatana-indicator-messages (Ubuntu) Importance: Undecided Status: New ** Tags: jammy kinetic kylin-22.04 lunar -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to ayatana-indicator-messages in Ubuntu. https://bugs.launchpad.net/bugs/2015218 Title: /usr/libexec/ayatana-indicator-messages/ayatana-indicator-messages- service:11:ACT_IS_USER:_act_user_update_from_object_path:fetch_user_incrementally:on_find_user_by_name_finished:g_task_return_now Status in ayatana-indicator-messages package in Ubuntu: New Bug description: The Ubuntu Error Tracker has been receiving reports about a problem regarding ayatana-indicator-messages. This problem was most recently seen with package version 22.9.0-1, the problem page at https://errors.ubuntu.com/problem/c068c002f0e2d03cb35cbae65bb611d9af61d7fb contains more details, including versions of packages affected, stacktrace or traceback, and individual crash reports. If you do not have access to the Ubuntu Error Tracker and are a software developer, you can request it at http://forms.canonical.com/reports/. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ayatana-indicator-messages/+bug/2015218/+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 1974293] Re: gnome-shell crashed on logout with SIGSEGV in js::gc::Cell::storeBuffer() from js::gc::PostWriteBarrierImpl()
And from a core file on lunar:
(gdb) bt -full
#0 __pthread_kill_implementation (no_tid=0, signo=11, threadid=) at ./nptl/pthread_kill.c:44
tid =
ret = 0
pd =
old_mask = {__val = {11}}
ret =
#1 __pthread_kill_internal (signo=11, threadid=) at
./nptl/pthread_kill.c:78
#2 __GI___pthread_kill (threadid=, signo=signo@entry=11) at
./nptl/pthread_kill.c:89
#3 0x7f464d03c406 in __GI_raise (sig=sig@entry=11) at
../sysdeps/posix/raise.c:26
ret =
#4 0x56282c4afaea in dump_gjs_stack_on_signal_handler (signo=11) at
../src/main.c:495
sa = {__sigaction_handler = {sa_handler = 0x56282c4af730
, sa_sigaction = 0x56282c4af730
}, sa_mask = {__val = {0 }},
sa_flags = 0, sa_restorer = 0x0}
i =
#5 0x7f464d03c4b0 in () at
/lib/x86_64-linux-gnu/libc.so.6
#6 0x7f464ad8d344 in js::gc::Cell::storeBuffer() const (this=, this=) at /usr/src/mozjs102-102.9.0-1/js/src/gc/Cell.h:357
buffer = 0x0
#7 js::gc::PostWriteBarrierImpl(void*, JSObject*, JSObject*)
(next=, prev=, cellp=) at
/usr/src/mozjs102-102.9.0-1/js/src/gc/StoreBuffer.h:646
buffer = 0x0
#8 js::gc::PostWriteBarrier(js::SavedFrame**, js::SavedFrame*,
js::SavedFrame*) (next=, prev=, vp=) at /usr/src/mozjs102-102.9.0-1/js/src/gc/StoreBuffer.h:658
#9 js::InternalBarrierMethods::postBarrier(js::SavedFrame**, js::SavedFrame*, js::SavedFrame*)
(next=, prev=, vp=0x7f4630022da0) at
/usr/src/mozjs102-102.9.0-1/js/src/gc/Barrier.h:350
#10 js::InternalBarrierMethods::postBarrier(js::SavedFrame**, js::SavedFrame*, js::SavedFrame*)
(vp=0x7f4630022da0, prev=, next=) at
/usr/src/mozjs102-102.9.0-1/js/src/gc/Barrier.h:349
#11 0x7f464d91f721 in js::BarrierMethods::postWriteBarrier(JSObject**, JSObject*, JSObject*) (next=0x0,
prev=, vp=0x7f4630022da0) at
/usr/include/mozjs-102/js/RootingAPI.h:795
p = 0x7f4630022da0
#12 JS::Heap::postWriteBarrier(JSObject* const&, JSObject* const&)
(next=, prev=@0x7f4630022da0: 0x1c8a30a483a0,
this=0x7f4630022da0, this=, prev=,
next=)
at /usr/include/mozjs-102/js/RootingAPI.h:376
p = 0x7f4630022da0
#13 JS::Heap::~Heap() (this=0x7f4630022da0, this=) at
/usr/include/mozjs-102/js/RootingAPI.h:338
p = 0x7f4630022da0
#14 mozilla::detail::VectorImpl, 0ul,
js::SystemAllocPolicy, false>::destroy(JS::Heap*,
JS::Heap*) (aEnd=0x7f4630022da8, aBegin=) at
/usr/include/mozjs-102/mozilla/Vector.h:65
p = 0x7f4630022da0
#15 mozilla::Vector, 0ul, js::SystemAllocPolicy>::~Vector()
(this=0x56282d2db9d8, this=) at
/usr/include/mozjs-102/mozilla/Vector.h:901
#16 JS::GCVector, 0ul, js::SystemAllocPolicy>::~GCVector()
(this=0x56282d2db9d8, this=) at
/usr/include/mozjs-102/js/GCVector.h:43
#17 GjsContextPrivate::~GjsContextPrivate() (this=0x56282d2db960,
this=) at
/usr/src/gjs-1.76.0-1/obj-x86_64-linux-gnu/../gjs/context.cpp:487
#18 0x7f464d9211e3 in gjs_context_finalize(GObject*)
(object=0x56282d2dbae0) at
/usr/src/gjs-1.76.0-1/obj-x86_64-linux-gnu/../gjs/context.cpp:500
gjs =
#19 0x7f464e02ee4c in g_object_unref (_object=0x56282d2dbae0) at
../../../gobject/gobject.c:3938
weak_locations =
nqueue = 0x56282d8fc5c0
object = 0x56282d2dbae0
old_ref =
__func__ = "g_object_unref"
#20 0x7f464dc2508d in _shell_global_destroy_gjs_context (self=) at ../src/shell-global.c:752
_pp =
_ptr =
#21 0x56282c4af00f in main (argc=, argv=) at
../src/main.c:776
context = 0x56282cd4e780
debug_flags_string = 0x56282d06c7b0
"backtrace-aborts:backtrace-math-errors:backtrace-crashes-all:backtrace-all"
error = 0x0
shell_debug =
ecode = 0
(gdb)
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to gjs in Ubuntu.
https://bugs.launchpad.net/bugs/1974293
Title:
gnome-shell crashed on logout with SIGSEGV in
js::gc::Cell::storeBuffer() from
js::gc::PostWriteBarrierImpl()
Status in gjs:
New
Status in OEM Priority Project:
Confirmed
Status in gjs package in Ubuntu:
Confirmed
Status in gnome-shell package in Ubuntu:
In Progress
Status in mozjs102 package in Ubuntu:
Confirmed
Status in mozjs91 package in Ubuntu:
Confirmed
Status in gnome-shell package in Fedora:
Confirmed
Bug description:
https://errors.ubuntu.com/problem/256d1c0d1aad03bb024b525f4c80868e8f6a85b4
https://errors.ubuntu.com/problem/b1669e114babda005eb5a6414867a0eb7293f7e7
Description: Ubuntu 22.04 LTS
Release: 22.04
ProblemType: Crash
DistroRelease: Ubuntu 22.04
Package: gnome-shell 42.0-2ubuntu1
ProcVersionSignature: Ubuntu 5.15.0-30.31-generic 5.15.30
Uname: Linux 5.15.0-30-generic x86_64
ApportVersion: 2.20.11-0ubuntu82
Architecture: amd64
CasperMD5CheckResult: pass
CurrentDesktop: ubuntu:GNOME
Date: Fri May 20 16:06:35 2022
DisplayManager: gdm3
ExecutablePath: /usr/bin/gnome-shell
ExecutableTimestamp: 1649813447
InstallationDate:
[Desktop-packages] [Bug 1974293] Re: gnome-shell crashed on logout with SIGSEGV in js::gc::Cell::storeBuffer() from js::gc::PostWriteBarrierImpl()
Debugging the release binaries in lunar is the only way I can capture
the crash:
Thread 1 "gnome-shell" received signal SIGSEGV, Segmentation fault.
0x7fd27998d344 in js::gc::Cell::storeBuffer (this=,
this=) at /usr/src/mozjs102-102.9.0-1/js/src/gc/Cell.h:357
357 inline StoreBuffer* Cell::storeBuffer() const { return
chunk()->storeBuffer; }
(gdb) bt
#0 0x7fd27998d344 in js::gc::Cell::storeBuffer() const
(this=, this=)
at /usr/src/mozjs102-102.9.0-1/js/src/gc/Cell.h:357
#1 js::gc::PostWriteBarrierImpl(void*, JSObject*, JSObject*)
(next=, prev=, cellp=)
at /usr/src/mozjs102-102.9.0-1/js/src/gc/StoreBuffer.h:646
#2 js::gc::PostWriteBarrier(js::SavedFrame**, js::SavedFrame*,
js::SavedFrame*)
(next=, prev=, vp=)
at /usr/src/mozjs102-102.9.0-1/js/src/gc/StoreBuffer.h:658
#3 js::InternalBarrierMethods::postBarrier(js::SavedFrame**, js::SavedFrame*, js::SavedFrame*)
(next=, prev=, vp=0x5647cc6bff20)
at /usr/src/mozjs102-102.9.0-1/js/src/gc/Barrier.h:350
#4 js::InternalBarrierMethods::postBarrier(js::SavedFrame**, js::SavedFrame*, js::SavedFrame*)
(vp=0x5647cc6bff20, prev=, next=)
at /usr/src/mozjs102-102.9.0-1/js/src/gc/Barrier.h:349
(gdb) frame 5
No frame at level 5.
(gdb) frame 6
No frame at level 6.
(gdb)
Not sure why I only get 4 frames in gdb.
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to gjs in Ubuntu.
https://bugs.launchpad.net/bugs/1974293
Title:
gnome-shell crashed on logout with SIGSEGV in
js::gc::Cell::storeBuffer() from
js::gc::PostWriteBarrierImpl()
Status in gjs:
New
Status in OEM Priority Project:
Confirmed
Status in gjs package in Ubuntu:
Confirmed
Status in gnome-shell package in Ubuntu:
In Progress
Status in mozjs102 package in Ubuntu:
Confirmed
Status in mozjs91 package in Ubuntu:
Confirmed
Status in gnome-shell package in Fedora:
Confirmed
Bug description:
https://errors.ubuntu.com/problem/256d1c0d1aad03bb024b525f4c80868e8f6a85b4
https://errors.ubuntu.com/problem/b1669e114babda005eb5a6414867a0eb7293f7e7
Description: Ubuntu 22.04 LTS
Release: 22.04
ProblemType: Crash
DistroRelease: Ubuntu 22.04
Package: gnome-shell 42.0-2ubuntu1
ProcVersionSignature: Ubuntu 5.15.0-30.31-generic 5.15.30
Uname: Linux 5.15.0-30-generic x86_64
ApportVersion: 2.20.11-0ubuntu82
Architecture: amd64
CasperMD5CheckResult: pass
CurrentDesktop: ubuntu:GNOME
Date: Fri May 20 16:06:35 2022
DisplayManager: gdm3
ExecutablePath: /usr/bin/gnome-shell
ExecutableTimestamp: 1649813447
InstallationDate: Installed on 2022-05-05 (14 days ago)
InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Release amd64
(20220419)
ProcCmdline: /usr/bin/gnome-shell
ProcCwd: /home/ubuntu
RelatedPackageVersions: mutter-common 42.0-3ubuntu2
Signal: 11
SourcePackage: gnome-shell
StacktraceTop:
?? () from /lib/x86_64-linux-gnu/libmozjs-91.so.0
?? () from /lib/x86_64-linux-gnu/libgjs.so.0
?? () from /lib/x86_64-linux-gnu/libgjs.so.0
g_object_unref () from /lib/x86_64-linux-gnu/libgobject-2.0.so.0
?? ()
Title: gnome-shell crashed with SIGSEGV in g_object_unref()
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/gjs/+bug/1974293/+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 2015183] Re: Invalid read of size 8 in gnome-shell from accountsservice: free_fetch_user_request (act-user-manager.c:1717) from on_find_user_by_name_finished (act-user-manager.
** Description changed: I don't experience crashes but valgrind gnome-shell reports: - ==15231== Invalid read of size 8 - ==15231==at 0x4D2D599: g_type_check_instance_is_fundamentally_a (in /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0.7600.1) - ==15231==by 0x4D149EA: g_object_set_data (in /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0.7600.1) - ==15231==by 0x363DCFD9: free_fetch_user_request (act-user-manager.c:1717) - ==15231==by 0x363E3E7F: on_find_user_by_name_finished (act-user-manager.c:1192) - ==15231==by 0x4BCE612: ??? (in /usr/lib/x86_64-linux-gnu/libgio-2.0.so.0.7600.1) - ==15231==by 0x4BD2042: ??? (in /usr/lib/x86_64-linux-gnu/libgio-2.0.so.0.7600.1) - ==15231==by 0x4C382AB: ??? (in /usr/lib/x86_64-linux-gnu/libgio-2.0.so.0.7600.1) - ==15231==by 0x4BCE612: ??? (in /usr/lib/x86_64-linux-gnu/libgio-2.0.so.0.7600.1) - ==15231==by 0x4BD2042: ??? (in /usr/lib/x86_64-linux-gnu/libgio-2.0.so.0.7600.1) - ==15231==by 0x4C28801: ??? (in /usr/lib/x86_64-linux-gnu/libgio-2.0.so.0.7600.1) - ==15231==by 0x4BCE612: ??? (in /usr/lib/x86_64-linux-gnu/libgio-2.0.so.0.7600.1) - ==15231==by 0x4BCE64C: ??? (in /usr/lib/x86_64-linux-gnu/libgio-2.0.so.0.7600.1) - ==15231== Address 0x3063be20 is 0 bytes inside a block of size 64 free'd - ==15231==at 0x484620F: free (in /usr/libexec/valgrind/vgpreload_memcheck-amd64-linux.so) - ==15231==by 0x4D2C66B: g_type_free_instance (in /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0.7600.1) - ==15231==by 0x4D1A0A6: g_object_notify (in /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0.7600.1) - ==15231==by 0x363E3519: UnknownInlinedFun (act-user.c:562) - ==15231==by 0x363E3519: UnknownInlinedFun (act-user.c:557) - ==15231==by 0x363E3519: _act_user_update_from_object_path (act-user.c:1346) - ==15231==by 0x363E3C3F: fetch_user_incrementally (act-user-manager.c:1804) - ==15231==by 0x363E3E7F: on_find_user_by_name_finished (act-user-manager.c:1192) - ==15231==by 0x4BCE612: ??? (in /usr/lib/x86_64-linux-gnu/libgio-2.0.so.0.7600.1) - ==15231==by 0x4BD2042: ??? (in /usr/lib/x86_64-linux-gnu/libgio-2.0.so.0.7600.1) - ==15231==by 0x4C382AB: ??? (in /usr/lib/x86_64-linux-gnu/libgio-2.0.so.0.7600.1) - ==15231==by 0x4BCE612: ??? (in /usr/lib/x86_64-linux-gnu/libgio-2.0.so.0.7600.1) - ==15231==by 0x4BD2042: ??? (in /usr/lib/x86_64-linux-gnu/libgio-2.0.so.0.7600.1) - ==15231==by 0x4C28801: ??? (in /usr/lib/x86_64-linux-gnu/libgio-2.0.so.0.7600.1) - ==15231== Block was alloc'd at - ==15231==at 0x4848A13: calloc (in /usr/libexec/valgrind/vgpreload_memcheck-amd64-linux.so) - ==15231==by 0x4DB5550: g_malloc0 (in /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0.7600.1) - ==15231==by 0x4D31B7C: g_type_create_instance (in /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0.7600.1) - ==15231==by 0x4D1920F: ??? (in /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0.7600.1) - ==15231==by 0x4D1A7B7: g_object_new_with_properties (in /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0.7600.1) - ==15231==by 0x4D1B560: g_object_new (in /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0.7600.1) - ==15231==by 0x363DE5F1: create_new_user (act-user-manager.c:707) - ==15231==by 0x363E41D8: act_user_manager_get_user (act-user-manager.c:1896) - ==15231==by 0x5DDE8B5: ??? (in /usr/lib/x86_64-linux-gnu/libffi.so.8.1.2) - ==15231==by 0x5DDB34C: ??? (in /usr/lib/x86_64-linux-gnu/libffi.so.8.1.2) - ==15231==by 0x5DDDF32: ffi_call (in /usr/lib/x86_64-linux-gnu/libffi.so.8.1.2) - ==15231==by 0x4F28BD8: ??? (in /usr/lib/x86_64-linux-gnu/libgjs.so.0.0.0) + ==33999== Invalid read of size 8 + ==33999==at 0x4D2D599: g_type_check_instance_is_fundamentally_a (gtype.c:4164) + ==33999==by 0x4D149EA: g_object_set_data (gobject.c:4242) + ==33999==by 0x363DCFD9: free_fetch_user_request (act-user-manager.c:1717) + ==33999==by 0x363E3E7F: on_find_user_by_name_finished (act-user-manager.c:1192) + ==33999==by 0x4BCE612: g_task_return_now (gtask.c:1309) + ==33999==by 0x4BD2042: UnknownInlinedFun (gtask.c:1378) + ==33999==by 0x4BD2042: g_task_return (gtask.c:1335) + ==33999==by 0x4C382AB: reply_cb (gdbusproxy.c:2571) + ==33999==by 0x4BCE612: g_task_return_now (gtask.c:1309) + ==33999==by 0x4BD2042: UnknownInlinedFun (gtask.c:1378) + ==33999==by 0x4BD2042: g_task_return (gtask.c:1335) + ==33999==by 0x4C28801: g_dbus_connection_call_done (gdbusconnection.c:5885) + ==33999==by 0x4BCE612: g_task_return_now (gtask.c:1309) + ==33999==by 0x4BCE64C: complete_in_idle_cb (gtask.c:1323) + ==33999== Address 0xb966c30 is 0 bytes inside a block of size 64 free'd + ==33999==at 0x484620F: free (vg_replace_malloc.c:872) + ==33999==by 0x4D2C66B: g_type_free_instance (gtype.c:2062) + ==33999==by 0x4D1A0A6: UnknownInlinedFun (gobject.c:1556) + ==33999==by 0x4D1A0A6: g_object_notify (gobject.c:1602) + ==33999==by 0x363E3519:
[Desktop-packages] [Bug 1086783] Re: New PolicyKit 0.106 changes configuration file format
The newer versions added support for duktape and security team reviewed and acked the corresponding MIR bug #1997417 now, moving forward we need to address the MIR team feedback on duktape, migrate our rules to the new format and resolve the autopkgtest issues found in the lunar cycle ** Description changed: From the NEWS file: This is polkit 0.106. There's a major change in this release which is a switch from .pkla files (keyfile-format) to .rules files (JavaScript). - - We may want to hold off on the new version because it requires rewriting - the configuration files, and adds a dependency on mozjs185, which will - need a MIR (and getting a MIR may be problematic) -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to policykit-1 in Ubuntu. https://bugs.launchpad.net/bugs/1086783 Title: New PolicyKit 0.106 changes configuration file format Status in policykit-1 package in Ubuntu: Triaged Status in policykit-1 package in Debian: Fix Released Bug description: From the NEWS file: This is polkit 0.106. There's a major change in this release which is a switch from .pkla files (keyfile-format) to .rules files (JavaScript). To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/policykit-1/+bug/1086783/+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 1698287] Re: VA-API fails to initialize in a Gnome Shell Wayland session
** Changed in: libva Status: Unknown => Fix Released -- 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/1698287 Title: VA-API fails to initialize in a Gnome Shell Wayland session Status in Libva: Fix Released Status in Mutter: Fix Released Status in Totem: Expired Status in VLC media player: New Status in chromium-browser package in Ubuntu: Won't Fix Status in gst-plugins-bad1.0 package in Ubuntu: Fix Released Status in gst-plugins-base1.0 package in Ubuntu: Fix Committed Status in gstreamer-vaapi package in Ubuntu: Won't Fix Status in libva package in Ubuntu: Fix Released Status in mpv package in Ubuntu: Fix Released Status in steam package in Ubuntu: Confirmed Bug description: The Intel i965 VA-API driver works well in Xorg sessions (Unity7 and Gnome Shell). But it refuses to load when in a Wayland session: $ totem bbb_sunflower_1080p_60fps_normal.mp4 libva error: va_getDriverName() failed with unknown libva error,driver_name=(null) $ env LIBVA_DRIVER_NAME=i965 totem bbb_sunflower_1080p_60fps_normal.mp4 totem: intel_driver.c:112: intel_driver_init: Assertion `VA_CHECK_DRM_AUTH_TYPE(ctx, VA_DRM_AUTH_DRI1) || VA_CHECK_DRM_AUTH_TYPE(ctx, VA_DRM_AUTH_DRI2) || VA_CHECK_DRM_AUTH_TYPE(ctx, VA_DRM_AUTH_CUSTOM)' failed. Aborted (core dumped) $ gst-play-1.0 bbb_sunflower_1080p_60fps_normal.mp4 Press 'k' to see a list of keyboard shortcuts. Now playing /home/dan/Videos/bbb_sunflower_1080p_60fps_normal.mp4 Redistribute latency... Redistribute latency... ERROR Internal error: could not render surface for file:///home/dan/Videos/bbb_sunflower_1080p_60fps_normal.mp4 ERROR debug information: ../../../gst/vaapi/gstvaapisink.c(1482): gst_vaapisink_show_frame_unlocked (): /GstPlayBin:playbin/GstPlaySink:playsink/GstBin:vbin/GstVaapiSink:vaapisink0 WORKAROUNDS: * Use weston instead of gnome-shell; or * $ env -uDISPLAY totem ... # but creates corruption -> bug 1701463 * $ env GST_GL_WINDOW=wayland totem ... # but creates corruption -> bug 1701463 * $ env GST_GL_WINDOW=wayland gst-play-1.0 --videosink glimagesink ... * $ env -uDISPLAY mpv --hwdec --opengl-backend=wayland ... ProblemType: Bug DistroRelease: Ubuntu 17.10 Package: i965-va-driver 1.8.1-1 ProcVersionSignature: Ubuntu 4.10.0-22.24-generic 4.10.15 Uname: Linux 4.10.0-22-generic x86_64 ApportVersion: 2.20.5-0ubuntu4 Architecture: amd64 Date: Fri Jun 16 13:40:38 2017 InstallationDate: Installed on 2017-05-03 (44 days ago) InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Alpha amd64 (20170502) SourcePackage: intel-vaapi-driver UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/libva/+bug/1698287/+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 2015061] Re: [nvidia][lunar] Corrupted/missing windows title background when opening windows
Yup, I have seen a few (rare and random this time) crashes when pressing the Activities corner button (or super shortcut key). It indeed restarts quickly after that, but I assumed it was linked to https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1968383 Let me know if I can provide any other info or help :) -- 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/2015061 Title: [nvidia][lunar] Corrupted/missing windows title background when opening windows Status in mutter package in Ubuntu: New Bug description: Since upgrading to Ubuntu 23.04 (from 22.10), the title bar of some apps are corrupted when the windows first open. As soon as I de-focus and re-focus them, the title bar starts working mostly correctly. You'll find a screenshot attached. Basically, the window just repeats the pattern of the edge, until it is de-focused, and then it will properly draw the "window inactive" background color. When the window is de-focused, clicking the title bar won't focus it, although double- clicking on it will maximize it. I need to click within the window body to focus it. Edit: Looking at the screenshot file, it seems like the screenshot even assumed the title bar was actually transparent (the alpha channel of the status bar is 0 in the screenshot!) All GNOME settings were reset using dconf after upgrade, and custom themes have been removed (this is all Yaru defaults). This is happening with almost all apps, including Terminator or Thunderbird. Gnome package versions: ii gir1.2-gnomeautoar-0.1:amd640.4.4-1 amd64GObject introspection data for GnomeAutoar ii gir1.2-gnomebg-4.0:amd6444.0-1 amd64Introspection data for GnomeBG (GTK 4) ii gir1.2-gnomebluetooth-3.0:amd64 42.5-3 amd64Introspection data for GnomeBluetooth ii gir1.2-gnomedesktop-3.0:amd64 44.0-1 amd64Introspection data for GnomeDesktop (GTK 3) ii gir1.2-gnomedesktop-4.0:amd64 44.0-1 amd64Introspection data for GnomeDesktop (GTK 4) ii gkbd-capplet3.28.1-1 amd64GNOME control center tools for libgnomekbd ii gnome-accessibility-themes 3.28-2ubuntu1 all High Contrast GTK 2 theme and icons ii gnome-bluetooth-3-common42.5-3 all GNOME Bluetooth 3 common files ii gnome-bluetooth-sendto 42.5-3 amd64GNOME Bluetooth Send To app ii gnome-calculator 1:44.0-1ubuntu1amd64 GNOME desktop calculator ii gnome-calendar 44.0-1 amd64Calendar application for GNOME ii gnome-characters44.0-1 amd64character map application ii gnome-control-center 1:44.0-1ubuntu4amd64 utilities to configure the GNOME desktop ii gnome-control-center-data 1:44.0-1ubuntu4all configuration applets for GNOME - data files ii gnome-control-center-faces 1:44.0-1ubuntu4all utilities to configure the GNOME desktop - faces images ii gnome-desktop3-data 44.0-1 all Common files for GNOME desktop apps ii gnome-disk-utility 44.0-1ubuntu1 amd64manage and configure disk drives and media ii gnome-font-viewer 44.0-1 amd64font viewer for GNOME ii gnome-initial-setup 44.0-1ubuntu1
[Desktop-packages] [Bug 2009767] Re: External HDMI monitor is laggy on NVIDIA-525 reverse PRIME system
https://launchpad.net/ubuntu/+source/nvidia-graphics- drivers-525/525.105.17-0ubuntu1 ** Changed in: nvidia-graphics-drivers-525 (Ubuntu) Status: Confirmed => Fix Committed ** Also affects: xorg-server (Ubuntu Focal) Importance: Undecided Status: New ** Also affects: nvidia-graphics-drivers-525 (Ubuntu Focal) Importance: Undecided Status: New ** Also affects: xorg-server (Ubuntu Lunar) Importance: High Status: Fix Released ** Also affects: nvidia-graphics-drivers-525 (Ubuntu Lunar) Importance: Undecided Status: Fix Committed ** Also affects: xorg-server (Ubuntu Bionic) Importance: Undecided Status: New ** Also affects: nvidia-graphics-drivers-525 (Ubuntu Bionic) Importance: Undecided Status: New ** Changed in: nvidia-graphics-drivers-525 (Ubuntu Kinetic) Status: Confirmed => Fix Committed ** Changed in: nvidia-graphics-drivers-525 (Ubuntu Jammy) Status: New => Fix Committed ** Changed in: nvidia-graphics-drivers-525 (Ubuntu Focal) Status: New => Fix Committed ** Changed in: nvidia-graphics-drivers-525 (Ubuntu Bionic) Status: New => Fix Committed -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to xorg-server in Ubuntu. https://bugs.launchpad.net/bugs/2009767 Title: External HDMI monitor is laggy on NVIDIA-525 reverse PRIME system Status in OEM Priority Project: New Status in nvidia-graphics-drivers-525 package in Ubuntu: Fix Committed Status in xorg-server package in Ubuntu: Fix Released Status in nvidia-graphics-drivers-525 source package in Bionic: Fix Committed Status in xorg-server source package in Bionic: New Status in nvidia-graphics-drivers-525 source package in Focal: Fix Committed Status in xorg-server source package in Focal: New Status in nvidia-graphics-drivers-525 source package in Jammy: Fix Committed Status in xorg-server source package in Jammy: In Progress Status in nvidia-graphics-drivers-525 source package in Kinetic: Fix Committed Status in xorg-server source package in Kinetic: Fix Released Status in nvidia-graphics-drivers-525 source package in Lunar: Fix Committed Status in xorg-server source package in Lunar: Fix Released Bug description: [Impact] NVIDIA driver has a hardcoded version check to see if a bug has been fixed in the xserver version. It does not help to backport the fix to the jammy xserver, as the driver has no way to check if the fix is there or not. We need to backport xorg-server from kinetic to jammy. [Test case] install xserver update, check that lagginess is gone [Regression potential] This is a backport of kinetic xorg-server to jammy, with 34 new upstream commits of which three were already backported due to CVE's, and a bugfix. 18 commits only touch darwin/XQuartz and won't affect us. As such, there should be a low chance of things breaking. Here's a list of the remaining 12 commits with above filtered out: 6bf62381d0a1fb5 xserver 21.1.4 855b96a85bc0711 xfree86: Fix event data alignment in inputtest driver b713e717c34d539 dix: Correctly save replayed event into GrabInfoRec cd3d21d8c44a35c xkb: fix XkbSetMap when changing a keysym without changing a keytype f575524314e9f20 Revert "os: Try to discover the current seat with the XDG_SEAT var first" 433f53a1a08390a tests: Fix build failure from missing micmap.c 3868f364728ae0c xf86-input-inputtest: Fix build on systems without SOCK_NONBLOCK afcaaac96767d77 print_edid: Fix a format string error 663af2f17eec2cc X11Application: Ensure TIS operations are done on the main thread bd3564cf377deac rootless: Dead code removal (ROOTLESS_REDISPLAY_DELAY is already defined) 53173fdab492f0f render: Fix build with gcc 12 69774044716039f present: Check for NULL to prevent crash --- original info [Summary] When the graphic mode is on-demand mode and plug in the monitor to HDMI port, there are two issue occures: 1. External monitor's screen is very laggy in external monitor mode only. 2. External monitor's screen sometimes (~50%) will be black in join display mode. [Steps to reproduce] 1. Boot in OS 2. Plug in the external monitor in HDMI port 3. Find the cursor moving in external monitor is laggy [Workaround] Downgrade to NVIDIA driver 515. [Additional information] Feedback from NV: An NVIDIA driver built with the features needed to get rid of the laggy monitor problem causes Xorg 1.21.1.3 to crash. There's a patch for Xorg to fix the crash (https://gitlab.freedesktop.org/xorg/xserver/-/issues/1275) and it was first included in the 1.21.1.4 release. Since the older X servers crash, NVIDIA deliberately does a version check in the driver and enables these features for Xorg servers that are known to work, i.e. 1.21.1.4 or higher. This unfortunately prevents backporting the fix to 1.21.1.3. Engineering has chosen this approach since a crash
[Desktop-packages] [Bug 2015061] Re: [nvidia][lunar] Corrupted/missing windows title background when opening windows
These messages: avril 02 18:51:02 mana gnome-shell[33312]: Failed to create offscreen effect framebuffer: Failed to create an OpenGL framebuffer object avril 02 18:51:02 mana gnome-shell[33312]: Failed to create offscreen effect framebuffer: Failed to create an OpenGL framebuffer object avril 02 18:51:02 mana kernel: gnome-shell[33312]: segfault at 1 ip 7fc6e255ceac sp 7ffd13b5ba70 error 4 in libnvidia-glcore.so.530.41.03[7fc6e1701000+25e5000] may relate to bug 2012225 happening. But when it does the whole shell will crash (and restart quickly, hopefully). So it's possible the entire problem here is bug 2012225 occurring and the new gnome-shell not being able to recover the window decoration state automatically. -- 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/2015061 Title: [nvidia][lunar] Corrupted/missing windows title background when opening windows Status in mutter package in Ubuntu: New Bug description: Since upgrading to Ubuntu 23.04 (from 22.10), the title bar of some apps are corrupted when the windows first open. As soon as I de-focus and re-focus them, the title bar starts working mostly correctly. You'll find a screenshot attached. Basically, the window just repeats the pattern of the edge, until it is de-focused, and then it will properly draw the "window inactive" background color. When the window is de-focused, clicking the title bar won't focus it, although double- clicking on it will maximize it. I need to click within the window body to focus it. Edit: Looking at the screenshot file, it seems like the screenshot even assumed the title bar was actually transparent (the alpha channel of the status bar is 0 in the screenshot!) All GNOME settings were reset using dconf after upgrade, and custom themes have been removed (this is all Yaru defaults). This is happening with almost all apps, including Terminator or Thunderbird. Gnome package versions: ii gir1.2-gnomeautoar-0.1:amd640.4.4-1 amd64GObject introspection data for GnomeAutoar ii gir1.2-gnomebg-4.0:amd6444.0-1 amd64Introspection data for GnomeBG (GTK 4) ii gir1.2-gnomebluetooth-3.0:amd64 42.5-3 amd64Introspection data for GnomeBluetooth ii gir1.2-gnomedesktop-3.0:amd64 44.0-1 amd64Introspection data for GnomeDesktop (GTK 3) ii gir1.2-gnomedesktop-4.0:amd64 44.0-1 amd64Introspection data for GnomeDesktop (GTK 4) ii gkbd-capplet3.28.1-1 amd64GNOME control center tools for libgnomekbd ii gnome-accessibility-themes 3.28-2ubuntu1 all High Contrast GTK 2 theme and icons ii gnome-bluetooth-3-common42.5-3 all GNOME Bluetooth 3 common files ii gnome-bluetooth-sendto 42.5-3 amd64GNOME Bluetooth Send To app ii gnome-calculator 1:44.0-1ubuntu1amd64 GNOME desktop calculator ii gnome-calendar 44.0-1 amd64Calendar application for GNOME ii gnome-characters44.0-1 amd64character map application ii gnome-control-center 1:44.0-1ubuntu4amd64 utilities to configure the GNOME desktop ii gnome-control-center-data 1:44.0-1ubuntu4all configuration applets for GNOME - data files ii gnome-control-center-faces 1:44.0-1ubuntu4all utilities to configure the GNOME desktop - faces images ii gnome-desktop3-data 44.0-1 all Common files for GNOME desktop apps ii
[Desktop-packages] [Bug 2015061] Re: [nvidia][lunar] Corrupted/missing windows title background when opening windows
Thanks. I wonder if the new window decorator (mutter-x11-frames) is mistakenly running on the NVIDIA GPU when it should be running on Intel by default. ** Changed in: mutter (Ubuntu) Status: Incomplete => New -- 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/2015061 Title: [nvidia][lunar] Corrupted/missing windows title background when opening windows Status in mutter package in Ubuntu: New Bug description: Since upgrading to Ubuntu 23.04 (from 22.10), the title bar of some apps are corrupted when the windows first open. As soon as I de-focus and re-focus them, the title bar starts working mostly correctly. You'll find a screenshot attached. Basically, the window just repeats the pattern of the edge, until it is de-focused, and then it will properly draw the "window inactive" background color. When the window is de-focused, clicking the title bar won't focus it, although double- clicking on it will maximize it. I need to click within the window body to focus it. Edit: Looking at the screenshot file, it seems like the screenshot even assumed the title bar was actually transparent (the alpha channel of the status bar is 0 in the screenshot!) All GNOME settings were reset using dconf after upgrade, and custom themes have been removed (this is all Yaru defaults). This is happening with almost all apps, including Terminator or Thunderbird. Gnome package versions: ii gir1.2-gnomeautoar-0.1:amd640.4.4-1 amd64GObject introspection data for GnomeAutoar ii gir1.2-gnomebg-4.0:amd6444.0-1 amd64Introspection data for GnomeBG (GTK 4) ii gir1.2-gnomebluetooth-3.0:amd64 42.5-3 amd64Introspection data for GnomeBluetooth ii gir1.2-gnomedesktop-3.0:amd64 44.0-1 amd64Introspection data for GnomeDesktop (GTK 3) ii gir1.2-gnomedesktop-4.0:amd64 44.0-1 amd64Introspection data for GnomeDesktop (GTK 4) ii gkbd-capplet3.28.1-1 amd64GNOME control center tools for libgnomekbd ii gnome-accessibility-themes 3.28-2ubuntu1 all High Contrast GTK 2 theme and icons ii gnome-bluetooth-3-common42.5-3 all GNOME Bluetooth 3 common files ii gnome-bluetooth-sendto 42.5-3 amd64GNOME Bluetooth Send To app ii gnome-calculator 1:44.0-1ubuntu1amd64 GNOME desktop calculator ii gnome-calendar 44.0-1 amd64Calendar application for GNOME ii gnome-characters44.0-1 amd64character map application ii gnome-control-center 1:44.0-1ubuntu4amd64 utilities to configure the GNOME desktop ii gnome-control-center-data 1:44.0-1ubuntu4all configuration applets for GNOME - data files ii gnome-control-center-faces 1:44.0-1ubuntu4all utilities to configure the GNOME desktop - faces images ii gnome-desktop3-data 44.0-1 all Common files for GNOME desktop apps ii gnome-disk-utility 44.0-1ubuntu1 amd64manage and configure disk drives and media ii gnome-font-viewer 44.0-1 amd64font viewer for GNOME ii gnome-initial-setup 44.0-1ubuntu1 amd64Initial GNOME system setup helper ii
[Desktop-packages] [Bug 1698287] Re: VA-API fails to initialize in a Gnome Shell Wayland session
Chromium is a "Won't Fix". Under Xwayland it should work automatically with the introduction of libva 2.17.0. And under native Wayland there is no bug. ** Changed in: chromium-browser (Ubuntu) Status: Confirmed => Won't Fix -- 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/1698287 Title: VA-API fails to initialize in a Gnome Shell Wayland session Status in Libva: Unknown Status in Mutter: Fix Released Status in Totem: Expired Status in VLC media player: New Status in chromium-browser package in Ubuntu: Won't Fix Status in gst-plugins-bad1.0 package in Ubuntu: Fix Released Status in gst-plugins-base1.0 package in Ubuntu: Fix Committed Status in gstreamer-vaapi package in Ubuntu: Won't Fix Status in libva package in Ubuntu: Fix Released Status in mpv package in Ubuntu: Fix Released Status in steam package in Ubuntu: Confirmed Bug description: The Intel i965 VA-API driver works well in Xorg sessions (Unity7 and Gnome Shell). But it refuses to load when in a Wayland session: $ totem bbb_sunflower_1080p_60fps_normal.mp4 libva error: va_getDriverName() failed with unknown libva error,driver_name=(null) $ env LIBVA_DRIVER_NAME=i965 totem bbb_sunflower_1080p_60fps_normal.mp4 totem: intel_driver.c:112: intel_driver_init: Assertion `VA_CHECK_DRM_AUTH_TYPE(ctx, VA_DRM_AUTH_DRI1) || VA_CHECK_DRM_AUTH_TYPE(ctx, VA_DRM_AUTH_DRI2) || VA_CHECK_DRM_AUTH_TYPE(ctx, VA_DRM_AUTH_CUSTOM)' failed. Aborted (core dumped) $ gst-play-1.0 bbb_sunflower_1080p_60fps_normal.mp4 Press 'k' to see a list of keyboard shortcuts. Now playing /home/dan/Videos/bbb_sunflower_1080p_60fps_normal.mp4 Redistribute latency... Redistribute latency... ERROR Internal error: could not render surface for file:///home/dan/Videos/bbb_sunflower_1080p_60fps_normal.mp4 ERROR debug information: ../../../gst/vaapi/gstvaapisink.c(1482): gst_vaapisink_show_frame_unlocked (): /GstPlayBin:playbin/GstPlaySink:playsink/GstBin:vbin/GstVaapiSink:vaapisink0 WORKAROUNDS: * Use weston instead of gnome-shell; or * $ env -uDISPLAY totem ... # but creates corruption -> bug 1701463 * $ env GST_GL_WINDOW=wayland totem ... # but creates corruption -> bug 1701463 * $ env GST_GL_WINDOW=wayland gst-play-1.0 --videosink glimagesink ... * $ env -uDISPLAY mpv --hwdec --opengl-backend=wayland ... ProblemType: Bug DistroRelease: Ubuntu 17.10 Package: i965-va-driver 1.8.1-1 ProcVersionSignature: Ubuntu 4.10.0-22.24-generic 4.10.15 Uname: Linux 4.10.0-22-generic x86_64 ApportVersion: 2.20.5-0ubuntu4 Architecture: amd64 Date: Fri Jun 16 13:40:38 2017 InstallationDate: Installed on 2017-05-03 (44 days ago) InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Alpha amd64 (20170502) SourcePackage: intel-vaapi-driver UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/libva/+bug/1698287/+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 1698287] Re: VA-API fails to initialize in a Gnome Shell Wayland session
Libva 2.17.0 added support for DRI3: https://github.com/intel/libva/pull/614 so that's in lunar ** No longer affects: libva ** Bug watch added: github.com/intel/libva/issues #79 https://github.com/intel/libva/issues/79 ** Also affects: libva via https://github.com/intel/libva/issues/79 Importance: Unknown Status: Unknown ** Changed in: libva (Ubuntu) Status: Triaged => Fix Released ** No longer affects: mutter (Ubuntu) -- 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/1698287 Title: VA-API fails to initialize in a Gnome Shell Wayland session Status in Libva: Unknown Status in Mutter: Fix Released Status in Totem: Expired Status in VLC media player: New Status in chromium-browser package in Ubuntu: Won't Fix Status in gst-plugins-bad1.0 package in Ubuntu: Fix Released Status in gst-plugins-base1.0 package in Ubuntu: Fix Committed Status in gstreamer-vaapi package in Ubuntu: Won't Fix Status in libva package in Ubuntu: Fix Released Status in mpv package in Ubuntu: Fix Released Status in steam package in Ubuntu: Confirmed Bug description: The Intel i965 VA-API driver works well in Xorg sessions (Unity7 and Gnome Shell). But it refuses to load when in a Wayland session: $ totem bbb_sunflower_1080p_60fps_normal.mp4 libva error: va_getDriverName() failed with unknown libva error,driver_name=(null) $ env LIBVA_DRIVER_NAME=i965 totem bbb_sunflower_1080p_60fps_normal.mp4 totem: intel_driver.c:112: intel_driver_init: Assertion `VA_CHECK_DRM_AUTH_TYPE(ctx, VA_DRM_AUTH_DRI1) || VA_CHECK_DRM_AUTH_TYPE(ctx, VA_DRM_AUTH_DRI2) || VA_CHECK_DRM_AUTH_TYPE(ctx, VA_DRM_AUTH_CUSTOM)' failed. Aborted (core dumped) $ gst-play-1.0 bbb_sunflower_1080p_60fps_normal.mp4 Press 'k' to see a list of keyboard shortcuts. Now playing /home/dan/Videos/bbb_sunflower_1080p_60fps_normal.mp4 Redistribute latency... Redistribute latency... ERROR Internal error: could not render surface for file:///home/dan/Videos/bbb_sunflower_1080p_60fps_normal.mp4 ERROR debug information: ../../../gst/vaapi/gstvaapisink.c(1482): gst_vaapisink_show_frame_unlocked (): /GstPlayBin:playbin/GstPlaySink:playsink/GstBin:vbin/GstVaapiSink:vaapisink0 WORKAROUNDS: * Use weston instead of gnome-shell; or * $ env -uDISPLAY totem ... # but creates corruption -> bug 1701463 * $ env GST_GL_WINDOW=wayland totem ... # but creates corruption -> bug 1701463 * $ env GST_GL_WINDOW=wayland gst-play-1.0 --videosink glimagesink ... * $ env -uDISPLAY mpv --hwdec --opengl-backend=wayland ... ProblemType: Bug DistroRelease: Ubuntu 17.10 Package: i965-va-driver 1.8.1-1 ProcVersionSignature: Ubuntu 4.10.0-22.24-generic 4.10.15 Uname: Linux 4.10.0-22-generic x86_64 ApportVersion: 2.20.5-0ubuntu4 Architecture: amd64 Date: Fri Jun 16 13:40:38 2017 InstallationDate: Installed on 2017-05-03 (44 days ago) InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Alpha amd64 (20170502) SourcePackage: intel-vaapi-driver UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/libva/+bug/1698287/+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 2015061] Re: [nvidia][lunar] Corrupted/missing windows title background when opening windows
Output of lspci -k Please note that this happens consistently, it's not random or a rare occurrence. After boot, opening Thunderbird for example makes it lack the title bar background immediately. ** Attachment added: "lspcik.txt" https://bugs.launchpad.net/ubuntu/+source/mutter/+bug/2015061/+attachment/5660750/+files/lspcik.txt -- 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/2015061 Title: [nvidia][lunar] Corrupted/missing windows title background when opening windows Status in mutter package in Ubuntu: Incomplete Bug description: Since upgrading to Ubuntu 23.04 (from 22.10), the title bar of some apps are corrupted when the windows first open. As soon as I de-focus and re-focus them, the title bar starts working mostly correctly. You'll find a screenshot attached. Basically, the window just repeats the pattern of the edge, until it is de-focused, and then it will properly draw the "window inactive" background color. When the window is de-focused, clicking the title bar won't focus it, although double- clicking on it will maximize it. I need to click within the window body to focus it. Edit: Looking at the screenshot file, it seems like the screenshot even assumed the title bar was actually transparent (the alpha channel of the status bar is 0 in the screenshot!) All GNOME settings were reset using dconf after upgrade, and custom themes have been removed (this is all Yaru defaults). This is happening with almost all apps, including Terminator or Thunderbird. Gnome package versions: ii gir1.2-gnomeautoar-0.1:amd640.4.4-1 amd64GObject introspection data for GnomeAutoar ii gir1.2-gnomebg-4.0:amd6444.0-1 amd64Introspection data for GnomeBG (GTK 4) ii gir1.2-gnomebluetooth-3.0:amd64 42.5-3 amd64Introspection data for GnomeBluetooth ii gir1.2-gnomedesktop-3.0:amd64 44.0-1 amd64Introspection data for GnomeDesktop (GTK 3) ii gir1.2-gnomedesktop-4.0:amd64 44.0-1 amd64Introspection data for GnomeDesktop (GTK 4) ii gkbd-capplet3.28.1-1 amd64GNOME control center tools for libgnomekbd ii gnome-accessibility-themes 3.28-2ubuntu1 all High Contrast GTK 2 theme and icons ii gnome-bluetooth-3-common42.5-3 all GNOME Bluetooth 3 common files ii gnome-bluetooth-sendto 42.5-3 amd64GNOME Bluetooth Send To app ii gnome-calculator 1:44.0-1ubuntu1amd64 GNOME desktop calculator ii gnome-calendar 44.0-1 amd64Calendar application for GNOME ii gnome-characters44.0-1 amd64character map application ii gnome-control-center 1:44.0-1ubuntu4amd64 utilities to configure the GNOME desktop ii gnome-control-center-data 1:44.0-1ubuntu4all configuration applets for GNOME - data files ii gnome-control-center-faces 1:44.0-1ubuntu4all utilities to configure the GNOME desktop - faces images ii gnome-desktop3-data 44.0-1 all Common files for GNOME desktop apps ii gnome-disk-utility 44.0-1ubuntu1 amd64manage and configure disk drives and media ii gnome-font-viewer 44.0-1 amd64font viewer for GNOME ii gnome-initial-setup
[Desktop-packages] [Bug 2015061] Re: [nvidia][lunar] Corrupted/missing windows title background when opening windows
Output of journalctl -b0 ** Attachment added: "journal.txt" https://bugs.launchpad.net/ubuntu/+source/mutter/+bug/2015061/+attachment/5660743/+files/journal.txt -- 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/2015061 Title: [nvidia][lunar] Corrupted/missing windows title background when opening windows Status in mutter package in Ubuntu: Incomplete Bug description: Since upgrading to Ubuntu 23.04 (from 22.10), the title bar of some apps are corrupted when the windows first open. As soon as I de-focus and re-focus them, the title bar starts working mostly correctly. You'll find a screenshot attached. Basically, the window just repeats the pattern of the edge, until it is de-focused, and then it will properly draw the "window inactive" background color. When the window is de-focused, clicking the title bar won't focus it, although double- clicking on it will maximize it. I need to click within the window body to focus it. Edit: Looking at the screenshot file, it seems like the screenshot even assumed the title bar was actually transparent (the alpha channel of the status bar is 0 in the screenshot!) All GNOME settings were reset using dconf after upgrade, and custom themes have been removed (this is all Yaru defaults). This is happening with almost all apps, including Terminator or Thunderbird. Gnome package versions: ii gir1.2-gnomeautoar-0.1:amd640.4.4-1 amd64GObject introspection data for GnomeAutoar ii gir1.2-gnomebg-4.0:amd6444.0-1 amd64Introspection data for GnomeBG (GTK 4) ii gir1.2-gnomebluetooth-3.0:amd64 42.5-3 amd64Introspection data for GnomeBluetooth ii gir1.2-gnomedesktop-3.0:amd64 44.0-1 amd64Introspection data for GnomeDesktop (GTK 3) ii gir1.2-gnomedesktop-4.0:amd64 44.0-1 amd64Introspection data for GnomeDesktop (GTK 4) ii gkbd-capplet3.28.1-1 amd64GNOME control center tools for libgnomekbd ii gnome-accessibility-themes 3.28-2ubuntu1 all High Contrast GTK 2 theme and icons ii gnome-bluetooth-3-common42.5-3 all GNOME Bluetooth 3 common files ii gnome-bluetooth-sendto 42.5-3 amd64GNOME Bluetooth Send To app ii gnome-calculator 1:44.0-1ubuntu1amd64 GNOME desktop calculator ii gnome-calendar 44.0-1 amd64Calendar application for GNOME ii gnome-characters44.0-1 amd64character map application ii gnome-control-center 1:44.0-1ubuntu4amd64 utilities to configure the GNOME desktop ii gnome-control-center-data 1:44.0-1ubuntu4all configuration applets for GNOME - data files ii gnome-control-center-faces 1:44.0-1ubuntu4all utilities to configure the GNOME desktop - faces images ii gnome-desktop3-data 44.0-1 all Common files for GNOME desktop apps ii gnome-disk-utility 44.0-1ubuntu1 amd64manage and configure disk drives and media ii gnome-font-viewer 44.0-1 amd64font viewer for GNOME ii gnome-initial-setup 44.0-1ubuntu1 amd64Initial GNOME system setup helper ii gnome-keyring
[Desktop-packages] [Bug 2015182] Re: Add support for Adreno a690
thanks, merged and waiting for the point-release before uploading ** Changed in: mesa (Ubuntu) Status: New => In Progress -- 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/2015182 Title: Add support for Adreno a690 Status in mesa package in Ubuntu: In Progress Bug description: The Lenovo X13s ARM laptop contains an Adreno a690 GPU. Please add Mesa support for this GPU. This landed in upstream Mesa here: https://gitlab.freedesktop.org/mesa/mesa/-/merge_requests/21573 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mesa/+bug/2015182/+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 2006669] Re: Asynchronous wait on fence ... timed out (hint:intel_atomic_commit_ready [i915])
lunar should have everything ** Changed in: mesa (Ubuntu Lunar) Status: Confirmed => Fix Released -- 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/2006669 Title: Asynchronous wait on fence ... timed out (hint:intel_atomic_commit_ready [i915]) Status in mesa package in Ubuntu: Fix Released Status in mesa source package in Jammy: Confirmed Status in mesa source package in Kinetic: Confirmed Status in mesa source package in Lunar: Fix Released Bug description: GUI hard lock during zoom session and gnome-terminal kern.log shows a mix of errors __ kernel: [ 3627.948545] Asynchronous wait on fence :00:02.0:gnome-shell[4236]:40810 timed out (hint:intel_atomic_commit_ready [i915]) kernel: [ 3631.063832] i915 :00:02.0: [drm] GPU HANG: ecode 12:1:85db, in chrome [5521] kernel: [ 3631.064218] i915 :00:02.0: [drm] Resetting chip for stopped heartbeat on rcs0 kernel: [ 3631.165642] i915 :00:02.0: [drm] chrome[5521] context reset due to GPU hang kernel: [ 3631.165719] i915 :00:02.0: [drm] GuC firmware i915/adlp_guc_70.1.1.bin version 70.1 kernel: [ 3631.165725] i915 :00:02.0: [drm] HuC firmware i915/tgl_huc_7.9.3.bin version 7.9 kernel: [ 3631.187377] i915 :00:02.0: [drm] HuC authenticated kernel: [ 3631.187670] i915 :00:02.0: [drm] GuC submission enabled kernel: [ 3631.187672] i915 :00:02.0: [drm] GuC SLPC enabled ___ I suspect this issue to be upstream: https://gitlab.freedesktop.org/mesa/mesa/-/issues/7755 upstream commit: https://gitlab.freedesktop.org/mesa/mesa/-/merge_requests/20169/commits?commit_id=b9403b1c477e7af04114ae6a4e16ca370e22253c#d6ffde011ad32c6371611e7d64affaeb21b6b217 Reproducer: Although I don't have my own reproducer, the upstream mesa reproducer does trigger a hang on my machine. Upstream Reproducer: Open https://kartikmandhang.netlify.app/ when it loads, you will see pikachu. Press "S", he will go back. My whole system freezes from this in Wayland, regardless of the browser. Kernel: 6.0.0-1008-oem Mesa: 22.2.5-0ubuntu0.1~22.04.1 ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: libgl1-mesa-dri 22.2.5-0ubuntu0.1~22.04.1 ProcVersionSignature: Ubuntu 6.0.0-1008.8-oem 6.0.9 Uname: Linux 6.0.0-1008-oem x86_64 ApportVersion: 2.20.11-0ubuntu82.3 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CasperMD5CheckResult: pass CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Wed Feb 8 21:40:19 2023 DistUpgraded: Fresh install DistroCodename: jammy DistroVariant: ubuntu ExtraDebuggingInterest: Yes, including running git bisection searches GraphicsCard: Intel Corporation Alder Lake-P Integrated Graphics Controller [8086:46a6] (rev 0c) (prog-if 00 [VGA controller]) Subsystem: Dell Device [1028:0b1a] Subsystem: Dell Device [1028:0b1a] InstallationDate: Installed on 2022-07-13 (211 days ago) InstallationMedia: Ubuntu-Server 22.04 LTS "Jammy Jellyfish" - Release amd64 (20220421) MachineType: Dell Inc. Precision 5570 ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-6.0.0-1008-oem root=/dev/mapper/ubuntu--vg-ubuntu--lv ro pcie_aspm=force quiet splash mem_sleep_default=deep vt.handoff=7 SourcePackage: mesa UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 11/21/2022 dmi.bios.release: 1.9 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.9.1 dmi.board.name: 03M8N5 dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 10 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr1.9.1:bd11/21/2022:br1.9:svnDellInc.:pnPrecision5570:pvr:rvnDellInc.:rn03M8N5:rvrA00:cvnDellInc.:ct10:cvr:sku0B1A: dmi.product.family: Precision dmi.product.name: Precision 5570 dmi.product.sku: 0B1A dmi.sys.vendor: Dell Inc. version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.113-2~ubuntu0.22.04.1 version.libgl1-mesa-dri: libgl1-mesa-dri 22.2.5-0ubuntu0.1~22.04.1 version.libgl1-mesa-glx: libgl1-mesa-glx 22.2.5-0ubuntu0.1~22.04.1 version.xserver-xorg-core: xserver-xorg-core 2:21.1.3-2ubuntu2.7 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-2ubuntu1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20210115-1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.17-2build1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mesa/+bug/2006669/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to :
[Desktop-packages] [Bug 2009767] Re: External HDMI monitor is laggy on NVIDIA-525 reverse PRIME system
** Description changed: + [Impact] + NVIDIA driver has a hardcoded version check to see if a bug has been fixed in the xserver version. It does not help to backport the fix to the jammy xserver, as the driver has no way to check if the fix is there or not. + + We need to backport xorg-server from kinetic to jammy. + + [Test case] + install xserver update, check that lagginess is gone + + [Regression potential] + This is a backport of kinetic xorg-server to jammy, with 34 new upstream commits of which three were already backported due to CVE's, and a bugfix. 18 commits only touch darwin/XQuartz and won't affect us. As such, there should be a low chance of things breaking. Here's a list of the remaining 12 commits with above filtered out: + + 6bf62381d0a1fb5 xserver 21.1.4 + 855b96a85bc0711 xfree86: Fix event data alignment in inputtest driver + b713e717c34d539 dix: Correctly save replayed event into GrabInfoRec + cd3d21d8c44a35c xkb: fix XkbSetMap when changing a keysym without changing a keytype + f575524314e9f20 Revert "os: Try to discover the current seat with the XDG_SEAT var first" + 433f53a1a08390a tests: Fix build failure from missing micmap.c + 3868f364728ae0c xf86-input-inputtest: Fix build on systems without SOCK_NONBLOCK + afcaaac96767d77 print_edid: Fix a format string error + 663af2f17eec2cc X11Application: Ensure TIS operations are done on the main thread + bd3564cf377deac rootless: Dead code removal (ROOTLESS_REDISPLAY_DELAY is already defined) + 53173fdab492f0f render: Fix build with gcc 12 + 69774044716039f present: Check for NULL to prevent crash + + + --- original info + [Summary] When the graphic mode is on-demand mode and plug in the monitor to HDMI port, there are two issue occures: 1. External monitor's screen is very laggy in external monitor mode only. - 2. External monitor's screen sometimes (~50%) will be blak in join display mode. + 2. External monitor's screen sometimes (~50%) will be black in join display mode. [Steps to reproduce] 1. Boot in OS 2. Plug in the external monitor in HDMI port 3. Find the cursor moving in external monitor is laggy [Workaround] Downgrade to NVIDIA driver 515. [Additional information] Feedback from NV: An NVIDIA driver built with the features needed to get rid of the laggy monitor problem causes Xorg 1.21.1.3 to crash. There's a patch for Xorg to fix the crash (https://gitlab.freedesktop.org/xorg/xserver/-/issues/1275) and it was first included in the 1.21.1.4 release. Since the older X servers crash, NVIDIA deliberately does a version check in the driver and enables these features for Xorg servers that are known to work, i.e. 1.21.1.4 or higher. This unfortunately prevents backporting the fix to 1.21.1.3. Engineering has chosen this approach since a crash is worse than the low FPS lag and the user might lose work merely by plugging/unplugging displays. If it was about a performance degradation, slight corruption, or something non-fatal, we wouldn't need to check Xorg version ** Changed in: xorg-server (Ubuntu Jammy) Status: Confirmed => In Progress -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to xorg-server in Ubuntu. https://bugs.launchpad.net/bugs/2009767 Title: External HDMI monitor is laggy on NVIDIA-525 reverse PRIME system Status in OEM Priority Project: New Status in nvidia-graphics-drivers-525 package in Ubuntu: Confirmed Status in xorg-server package in Ubuntu: Fix Released Status in nvidia-graphics-drivers-525 source package in Jammy: New Status in xorg-server source package in Jammy: In Progress Status in nvidia-graphics-drivers-525 source package in Kinetic: Confirmed Status in xorg-server source package in Kinetic: Fix Released Bug description: [Impact] NVIDIA driver has a hardcoded version check to see if a bug has been fixed in the xserver version. It does not help to backport the fix to the jammy xserver, as the driver has no way to check if the fix is there or not. We need to backport xorg-server from kinetic to jammy. [Test case] install xserver update, check that lagginess is gone [Regression potential] This is a backport of kinetic xorg-server to jammy, with 34 new upstream commits of which three were already backported due to CVE's, and a bugfix. 18 commits only touch darwin/XQuartz and won't affect us. As such, there should be a low chance of things breaking. Here's a list of the remaining 12 commits with above filtered out: 6bf62381d0a1fb5 xserver 21.1.4 855b96a85bc0711 xfree86: Fix event data alignment in inputtest driver b713e717c34d539 dix: Correctly save replayed event into GrabInfoRec cd3d21d8c44a35c xkb: fix XkbSetMap when changing a keysym without changing a keytype f575524314e9f20 Revert "os: Try to discover the current seat with the XDG_SEAT var first" 433f53a1a08390a tests: Fix build failure from missing micmap.c
[Desktop-packages] [Bug 2015182] Re: Add support for Adreno a690
Test packages: https://launchpad.net/~juergh/+archive/ubuntu/mesa ** Description changed: - The Lenovo X13s ARM laptop contains an Ardeno a690 GPU. Please add Mesa + The Lenovo X13s ARM laptop contains an Adreno a690 GPU. Please add Mesa support for this GPU. This landed in upstream Mesa here: https://gitlab.freedesktop.org/mesa/mesa/-/merge_requests/21573 -- 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/2015182 Title: Add support for Adreno a690 Status in mesa package in Ubuntu: New Bug description: The Lenovo X13s ARM laptop contains an Adreno a690 GPU. Please add Mesa support for this GPU. This landed in upstream Mesa here: https://gitlab.freedesktop.org/mesa/mesa/-/merge_requests/21573 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mesa/+bug/2015182/+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 2015182] Re: Add support for Adreno a690
** Attachment added: "mesa_23.0.1-1ubuntu1_23.0.1-1ubuntu2.diff.gz" https://bugs.launchpad.net/ubuntu/+source/mesa/+bug/2015182/+attachment/5660728/+files/mesa_23.0.1-1ubuntu1_23.0.1-1ubuntu2.diff.gz -- 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/2015182 Title: Add support for Adreno a690 Status in mesa package in Ubuntu: New Bug description: The Lenovo X13s ARM laptop contains an Adreno a690 GPU. Please add Mesa support for this GPU. This landed in upstream Mesa here: https://gitlab.freedesktop.org/mesa/mesa/-/merge_requests/21573 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mesa/+bug/2015182/+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 2015182] [NEW] Add support for Adreno a690
Public bug reported: The Lenovo X13s ARM laptop contains an Adreno a690 GPU. Please add Mesa support for this GPU. This landed in upstream Mesa here: https://gitlab.freedesktop.org/mesa/mesa/-/merge_requests/21573 ** Affects: mesa (Ubuntu) Importance: Undecided Status: New -- 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/2015182 Title: Add support for Adreno a690 Status in mesa package in Ubuntu: New Bug description: The Lenovo X13s ARM laptop contains an Adreno a690 GPU. Please add Mesa support for this GPU. This landed in upstream Mesa here: https://gitlab.freedesktop.org/mesa/mesa/-/merge_requests/21573 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mesa/+bug/2015182/+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 2015183] [NEW] Invalid read of size 8 in gnome-shell from accountsservice: free_fetch_user_request (act-user-manager.c:1717) from on_find_user_by_name_finished (act-user-manage
Public bug reported: I don't experience crashes but valgrind gnome-shell reports: ==15231== Invalid read of size 8 ==15231==at 0x4D2D599: g_type_check_instance_is_fundamentally_a (in /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0.7600.1) ==15231==by 0x4D149EA: g_object_set_data (in /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0.7600.1) ==15231==by 0x363DCFD9: free_fetch_user_request (act-user-manager.c:1717) ==15231==by 0x363E3E7F: on_find_user_by_name_finished (act-user-manager.c:1192) ==15231==by 0x4BCE612: ??? (in /usr/lib/x86_64-linux-gnu/libgio-2.0.so.0.7600.1) ==15231==by 0x4BD2042: ??? (in /usr/lib/x86_64-linux-gnu/libgio-2.0.so.0.7600.1) ==15231==by 0x4C382AB: ??? (in /usr/lib/x86_64-linux-gnu/libgio-2.0.so.0.7600.1) ==15231==by 0x4BCE612: ??? (in /usr/lib/x86_64-linux-gnu/libgio-2.0.so.0.7600.1) ==15231==by 0x4BD2042: ??? (in /usr/lib/x86_64-linux-gnu/libgio-2.0.so.0.7600.1) ==15231==by 0x4C28801: ??? (in /usr/lib/x86_64-linux-gnu/libgio-2.0.so.0.7600.1) ==15231==by 0x4BCE612: ??? (in /usr/lib/x86_64-linux-gnu/libgio-2.0.so.0.7600.1) ==15231==by 0x4BCE64C: ??? (in /usr/lib/x86_64-linux-gnu/libgio-2.0.so.0.7600.1) ==15231== Address 0x3063be20 is 0 bytes inside a block of size 64 free'd ==15231==at 0x484620F: free (in /usr/libexec/valgrind/vgpreload_memcheck-amd64-linux.so) ==15231==by 0x4D2C66B: g_type_free_instance (in /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0.7600.1) ==15231==by 0x4D1A0A6: g_object_notify (in /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0.7600.1) ==15231==by 0x363E3519: UnknownInlinedFun (act-user.c:562) ==15231==by 0x363E3519: UnknownInlinedFun (act-user.c:557) ==15231==by 0x363E3519: _act_user_update_from_object_path (act-user.c:1346) ==15231==by 0x363E3C3F: fetch_user_incrementally (act-user-manager.c:1804) ==15231==by 0x363E3E7F: on_find_user_by_name_finished (act-user-manager.c:1192) ==15231==by 0x4BCE612: ??? (in /usr/lib/x86_64-linux-gnu/libgio-2.0.so.0.7600.1) ==15231==by 0x4BD2042: ??? (in /usr/lib/x86_64-linux-gnu/libgio-2.0.so.0.7600.1) ==15231==by 0x4C382AB: ??? (in /usr/lib/x86_64-linux-gnu/libgio-2.0.so.0.7600.1) ==15231==by 0x4BCE612: ??? (in /usr/lib/x86_64-linux-gnu/libgio-2.0.so.0.7600.1) ==15231==by 0x4BD2042: ??? (in /usr/lib/x86_64-linux-gnu/libgio-2.0.so.0.7600.1) ==15231==by 0x4C28801: ??? (in /usr/lib/x86_64-linux-gnu/libgio-2.0.so.0.7600.1) ==15231== Block was alloc'd at ==15231==at 0x4848A13: calloc (in /usr/libexec/valgrind/vgpreload_memcheck-amd64-linux.so) ==15231==by 0x4DB5550: g_malloc0 (in /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0.7600.1) ==15231==by 0x4D31B7C: g_type_create_instance (in /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0.7600.1) ==15231==by 0x4D1920F: ??? (in /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0.7600.1) ==15231==by 0x4D1A7B7: g_object_new_with_properties (in /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0.7600.1) ==15231==by 0x4D1B560: g_object_new (in /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0.7600.1) ==15231==by 0x363DE5F1: create_new_user (act-user-manager.c:707) ==15231==by 0x363E41D8: act_user_manager_get_user (act-user-manager.c:1896) ==15231==by 0x5DDE8B5: ??? (in /usr/lib/x86_64-linux-gnu/libffi.so.8.1.2) ==15231==by 0x5DDB34C: ??? (in /usr/lib/x86_64-linux-gnu/libffi.so.8.1.2) ==15231==by 0x5DDDF32: ffi_call (in /usr/lib/x86_64-linux-gnu/libffi.so.8.1.2) ==15231==by 0x4F28BD8: ??? (in /usr/lib/x86_64-linux-gnu/libgjs.so.0.0.0) ProblemType: Bug DistroRelease: Ubuntu 23.04 Package: accountsservice 22.08.8-1ubuntu5 ProcVersionSignature: Ubuntu 6.2.0-18.18-generic 6.2.6 Uname: Linux 6.2.0-18-generic x86_64 ApportVersion: 2.26.0-0ubuntu2 Architecture: amd64 CasperMD5CheckResult: pass Date: Tue Apr 4 14:29:55 2023 InstallationDate: Installed on 2022-11-28 (126 days ago) InstallationMedia: Ubuntu 23.04 "Lunar Lobster" - Alpha amd64 (20221126) SourcePackage: accountsservice UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: accountsservice (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug lunar ** Summary changed: - Invalid read of size 8 from accountsservice: free_fetch_user_request (act-user-manager.c:1717) from on_find_user_by_name_finished (act-user-manager.c:1192) + Invalid read of size 8 in gnome-shell from accountsservice: free_fetch_user_request (act-user-manager.c:1717) from on_find_user_by_name_finished (act-user-manager.c:1192) ** Description changed: - I don't experience crashes but Valgrind still reports: + I don't experience crashes but valgrind gnome-shell reports: ==15231== Invalid read of size 8 ==15231==at 0x4D2D599: g_type_check_instance_is_fundamentally_a (in /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0.7600.1) ==15231==by 0x4D149EA: g_object_set_data (in /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0.7600.1) ==15231==by
[Desktop-packages] [Bug 2015181] nautilus crashed with signal 7 in g_main_context_dispatch()
StacktraceTop: nautilus_view_model_get_item_from_file (self=0x55bc174bd047, file=) at ../src/nautilus-view-model.c:392 on_clipboard_contents_received (source_object=, res=, user_data=) at ../src/nautilus-list-base.c:1316 g_task_return_now (task=0x55b94d014ab0) at ../../../gio/gtask.c:1309 complete_in_idle_cb (task=0x55b94d014ab0) at ../../../gio/gtask.c:1323 g_main_dispatch (context=0x55b949b47930) at ../../../glib/gmain.c:3460 ** Tags removed: need-amd64-retrace -- 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/2015181 Title: nautilus crashed with signal 7 in g_main_context_dispatch() Status in nautilus package in Ubuntu: New Bug description: Just started gedit but no recent operations with nautilus. ProblemType: Crash DistroRelease: Ubuntu 23.04 Package: nautilus 1:44.0-1ubuntu1 ProcVersionSignature: Ubuntu 6.2.0-18.18-generic 6.2.6 Uname: Linux 6.2.0-18-generic x86_64 ApportVersion: 2.26.0-0ubuntu2 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Tue Apr 4 07:57:12 2023 ExecutablePath: /usr/bin/nautilus GsettingsChanges: b'org.gnome.nautilus.preferences' b'migrated-gtk-settings' b'true' b'org.gnome.nautilus.window-state' b'initial-size' b'(1099, 732)' InstallationDate: Installed on 2023-03-31 (3 days ago) InstallationMedia: Ubuntu 23.04 "Lunar Lobster" - Beta amd64 (20230329) JournalErrors: -- No entries -- ProcCmdline: /usr/bin/nautilus --gapplication-service ProcEnviron: LANG=en_US.UTF-8 PATH=(custom, no user) SHELL=/bin/bash XDG_RUNTIME_DIR= Signal: 7 SourcePackage: nautilus StacktraceTop: ?? () ?? () from /lib/x86_64-linux-gnu/libgio-2.0.so.0 ?? () from /lib/x86_64-linux-gnu/libgio-2.0.so.0 g_main_context_dispatch () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 Title: nautilus crashed with signal 7 in g_main_context_dispatch() UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sudo users separator: usr_lib_nautilus: file-roller 43.0-1 nautilus-extension-gnome-terminal 3.48.0-1ubuntu1 nautilus-image-converter 0.4.0-2 nautilus-share0.7.5-0.3 python3-nautilus 4.0-1build1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nautilus/+bug/2015181/+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 1968040] Re: Blanked screen doesn't wake up after locking [drmModeAtomicCommit: Argument invalide] [drmModeAtomicCommit: Invalid argument]
Someone please help us to find the cause of this bug by: 1. Remove all workarounds. 2. Add kernel parameter: drm.debug=0xff 3. Add to /etc/environment: MUTTER_DEBUG=kms 4. Reboot. 5. Reproduce the bug. 6. Run: journalctl -b0 > journal.txt 7. Attach the resulting text file here. -- 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/1968040 Title: Blanked screen doesn't wake up after locking [drmModeAtomicCommit: Argument invalide] [drmModeAtomicCommit: Invalid argument] Status in GNOME Shell: New Status in Mutter: New Status in mutter package in Ubuntu: Confirmed Bug description: [ Workaround ] Add to /etc/environment (in Ubuntu 22.04): MUTTER_DEBUG_ENABLE_ATOMIC_KMS=0 or in Ubuntu 22.10 and later: MUTTER_DEBUG_FORCE_KMS_MODE=simple and then reboot. [ Original report ] (initially reported as a comment on bug #1965085, and split into a separate bug report) After I lock my screen and let it blank, moving the mouse or pressing any key on the keyboard won't wake it up. The only reliable workaround I've found is to press Ctrl+Alt+F1. That's on a fully up-to-date jammy, my hardware is an Intel NUC with a single Samsung monitor connected with a standard HDMI cable. This is a regression that started happening yesterday (2022-04-05) if I can remember correctly (I do apply pending updates at least once daily). ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: gdm3 42.0-1ubuntu2 ProcVersionSignature: Ubuntu 5.15.0-25.25-generic 5.15.30 Uname: Linux 5.15.0-25-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.20.11-0ubuntu80 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: ubuntu:GNOME Date: Wed Apr 6 15:19:30 2022 InstallationDate: Installed on 2020-09-16 (566 days ago) InstallationMedia: Ubuntu 20.10 "Groovy Gorilla" - Alpha amd64 (20200910) SourcePackage: gdm3 UpgradeStatus: Upgraded to jammy on 2022-03-19 (17 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-shell/+bug/1968040/+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 1974293] Re: gnome-shell crashed on logout with SIGSEGV in js::gc::Cell::storeBuffer() from js::gc::PostWriteBarrierImpl()
** Changed in: gnome-shell (Ubuntu) Status: Confirmed => In Progress ** Tags added: dt-469 -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gjs in Ubuntu. https://bugs.launchpad.net/bugs/1974293 Title: gnome-shell crashed on logout with SIGSEGV in js::gc::Cell::storeBuffer() from js::gc::PostWriteBarrierImpl() Status in gjs: New Status in OEM Priority Project: Confirmed Status in gjs package in Ubuntu: Confirmed Status in gnome-shell package in Ubuntu: In Progress Status in mozjs102 package in Ubuntu: Confirmed Status in mozjs91 package in Ubuntu: Confirmed Status in gnome-shell package in Fedora: Confirmed Bug description: https://errors.ubuntu.com/problem/256d1c0d1aad03bb024b525f4c80868e8f6a85b4 https://errors.ubuntu.com/problem/b1669e114babda005eb5a6414867a0eb7293f7e7 Description: Ubuntu 22.04 LTS Release: 22.04 ProblemType: Crash DistroRelease: Ubuntu 22.04 Package: gnome-shell 42.0-2ubuntu1 ProcVersionSignature: Ubuntu 5.15.0-30.31-generic 5.15.30 Uname: Linux 5.15.0-30-generic x86_64 ApportVersion: 2.20.11-0ubuntu82 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Fri May 20 16:06:35 2022 DisplayManager: gdm3 ExecutablePath: /usr/bin/gnome-shell ExecutableTimestamp: 1649813447 InstallationDate: Installed on 2022-05-05 (14 days ago) InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Release amd64 (20220419) ProcCmdline: /usr/bin/gnome-shell ProcCwd: /home/ubuntu RelatedPackageVersions: mutter-common 42.0-3ubuntu2 Signal: 11 SourcePackage: gnome-shell StacktraceTop: ?? () from /lib/x86_64-linux-gnu/libmozjs-91.so.0 ?? () from /lib/x86_64-linux-gnu/libgjs.so.0 ?? () from /lib/x86_64-linux-gnu/libgjs.so.0 g_object_unref () from /lib/x86_64-linux-gnu/libgobject-2.0.so.0 ?? () Title: gnome-shell crashed with SIGSEGV in g_object_unref() 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/gjs/+bug/1974293/+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 2004475] Re: Archive type selection drop-down in archive creation window is clipped
** Changed in: nautilus Status: Unknown => Fix Released -- 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/2004475 Title: Archive type selection drop-down in archive creation window is clipped Status in Nautilus: Fix Released Status in nautilus package in Ubuntu: Fix Released Status in nautilus source package in Jammy: In Progress Bug description: Impact -- (see LP: #2013338 for nautilus 42.6 SRU for jammy, which should fix this) When you try to change type of the archive that you'd like to create the drop-down list is clipped from the left, which contains most important information about the type that you try to select. At the same time archive creation window has a fixed size and cannot be resized. See screenshot. Upstream bug: https://gitlab.gnome.org/GNOME/nautilus/-/issues/2018 Test Case - Log into "Ubuntu on Xorg". Run nautilus, right-click on any file or folder, and select Compress... In the newly opened Create Archive dialog, click on the file extension so that a popup menu is opened. The expected behaviour is that the popup would display correctly and in full. With this bug present, the popup appears clipped/cropped. To reproduce the bug, might need to set the screen resolution low, or enable Accessibility > Seeing > Large Text from gnome-control-center. -- ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: nautilus 1:42.2-0ubuntu2.1 ProcVersionSignature: Ubuntu 5.15.0-60.66-generic 5.15.78 Uname: Linux 5.15.0-60-generic x86_64 ApportVersion: 2.20.11-0ubuntu82.3 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: ubuntu:GNOME Date: Wed Feb 1 16:40:30 2023 InstallationDate: Installed on 2020-11-24 (799 days ago) InstallationMedia: Ubuntu 18.04.3 LTS "Bionic Beaver" - Release amd64 (20190805) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=ru_RU.UTF-8 SHELL=/bin/bash SourcePackage: nautilus UpgradeStatus: Upgraded to jammy on 2023-01-18 (14 days ago) usr_lib_nautilus: file-roller 3.42.0-1 nautilus-extension-gnome-terminal 3.44.0-1ubuntu1 nautilus-share0.7.3-2ubuntu6 python3-nautilus 1.2.3-3.1build1 To manage notifications about this bug go to: https://bugs.launchpad.net/nautilus/+bug/2004475/+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 2012733] Re: Unthemed and unscaled titlebars for server-side decorations in GNOME 44 Xorg sessions
** Changed in: mutter Status: Unknown => New -- 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/2012733 Title: Unthemed and unscaled titlebars for server-side decorations in GNOME 44 Xorg sessions Status in Mutter: New Status in Yaru Theme: Unknown Status in mutter package in Ubuntu: Fix Committed Status in yaru-theme package in Ubuntu: In Progress Bug description: Hi, Nvidia 530 (graphics ppa), dGPU mode, GS 44, Lunar X1 session: If I launch Synaptic or ChessX, eg., the title bar is Adwaita-styled (greyish + icons). No issue with GNOME apps (and some other like FF or TB snaps, etc.). Wayland session: all is ok (except many other bugs!) To manage notifications about this bug go to: https://bugs.launchpad.net/mutter/+bug/2012733/+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 2015181] [NEW] nautilus crashed with signal 7 in g_main_context_dispatch()
Public bug reported: Just started gedit but no recent operations with nautilus. ProblemType: Crash DistroRelease: Ubuntu 23.04 Package: nautilus 1:44.0-1ubuntu1 ProcVersionSignature: Ubuntu 6.2.0-18.18-generic 6.2.6 Uname: Linux 6.2.0-18-generic x86_64 ApportVersion: 2.26.0-0ubuntu2 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Tue Apr 4 07:57:12 2023 ExecutablePath: /usr/bin/nautilus GsettingsChanges: b'org.gnome.nautilus.preferences' b'migrated-gtk-settings' b'true' b'org.gnome.nautilus.window-state' b'initial-size' b'(1099, 732)' InstallationDate: Installed on 2023-03-31 (3 days ago) InstallationMedia: Ubuntu 23.04 "Lunar Lobster" - Beta amd64 (20230329) JournalErrors: -- No entries -- ProcCmdline: /usr/bin/nautilus --gapplication-service ProcEnviron: LANG=en_US.UTF-8 PATH=(custom, no user) SHELL=/bin/bash XDG_RUNTIME_DIR= Signal: 7 SourcePackage: nautilus StacktraceTop: ?? () ?? () from /lib/x86_64-linux-gnu/libgio-2.0.so.0 ?? () from /lib/x86_64-linux-gnu/libgio-2.0.so.0 g_main_context_dispatch () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 Title: nautilus crashed with signal 7 in g_main_context_dispatch() UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sudo users separator: usr_lib_nautilus: file-roller 43.0-1 nautilus-extension-gnome-terminal 3.48.0-1ubuntu1 nautilus-image-converter 0.4.0-2 nautilus-share0.7.5-0.3 python3-nautilus 4.0-1build1 ** Affects: nautilus (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-crash lunar need-amd64-retrace wayland-session ** Information type changed from Private to Public -- 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/2015181 Title: nautilus crashed with signal 7 in g_main_context_dispatch() Status in nautilus package in Ubuntu: New Bug description: Just started gedit but no recent operations with nautilus. ProblemType: Crash DistroRelease: Ubuntu 23.04 Package: nautilus 1:44.0-1ubuntu1 ProcVersionSignature: Ubuntu 6.2.0-18.18-generic 6.2.6 Uname: Linux 6.2.0-18-generic x86_64 ApportVersion: 2.26.0-0ubuntu2 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Tue Apr 4 07:57:12 2023 ExecutablePath: /usr/bin/nautilus GsettingsChanges: b'org.gnome.nautilus.preferences' b'migrated-gtk-settings' b'true' b'org.gnome.nautilus.window-state' b'initial-size' b'(1099, 732)' InstallationDate: Installed on 2023-03-31 (3 days ago) InstallationMedia: Ubuntu 23.04 "Lunar Lobster" - Beta amd64 (20230329) JournalErrors: -- No entries -- ProcCmdline: /usr/bin/nautilus --gapplication-service ProcEnviron: LANG=en_US.UTF-8 PATH=(custom, no user) SHELL=/bin/bash XDG_RUNTIME_DIR= Signal: 7 SourcePackage: nautilus StacktraceTop: ?? () ?? () from /lib/x86_64-linux-gnu/libgio-2.0.so.0 ?? () from /lib/x86_64-linux-gnu/libgio-2.0.so.0 g_main_context_dispatch () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 Title: nautilus crashed with signal 7 in g_main_context_dispatch() UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sudo users separator: usr_lib_nautilus: file-roller 43.0-1 nautilus-extension-gnome-terminal 3.48.0-1ubuntu1 nautilus-image-converter 0.4.0-2 nautilus-share0.7.5-0.3 python3-nautilus 4.0-1build1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nautilus/+bug/2015181/+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
