[Desktop-packages] [Bug 2018672] Re: Gnome 44: GDM background configurable with gsettings
This probably went into: gnome-shell (45~rc-0ubuntu1) mantic; urgency=medium but I can't tell because Salsa hasn't been updated recently. ** Changed in: gnome-shell (Ubuntu) Status: Fix Committed => Fix Released -- 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/2018672 Title: Gnome 44: GDM background configurable with gsettings Status in gnome-shell package in Ubuntu: Fix Released Status in gnome-shell source package in Lunar: New Bug description: [Description] The prior implementation of exposing the login screen background setting via `gsettings` is not working as expected in Gnome 44 and Ubuntu 23.04. Specifically, the background image is infact set, however, the default Gnome theme appears as an overlay on top of the com.ubuntu.login-screen schema. This appears as the default grey background with a remarkably high alpha value of 0.975 from my inspection. If you set a very high contrast background image, you can just make out the outline in beneath the greeter. My expectation would be that we can set the greeter parameters using the provided gsettings keys, and set the background-color to transparent to only display the configured background-picture-uri key. gdm@zen:~$ gsettings list-keys com.ubuntu.login-screen background-color background-picture-uri background-repeat background-size [Test Case] 1. Boot a desktop session 2. Verify that the default aubergine background is displayed in the greeter. 3. Login as the administrator of the machine 4. Install systemd-container 5. Switch to the GDM user: $ sudo machinectl shell gdm@ /bin/bash 6. Apply a different background with the command: $ gsettings set com.ubuntu.login-screen background-picture-uri 'file:///usr/share/backgrounds/Lunar-lobster-side_by_Gixo-light.png' 7. Logout 8. Verify that the image 'Lunar-lobster-side_by_Gixo-light.png' is displayed as the background of the greeter. 9. Observe the remaining grey overlay with high alpha value. After login, the background image is briefly displayed without the overlay before initiating the user gnome shell session. [Further Investigation] PRATAP-KUMAR has done some excellent work overcoming this with their GitHub project, and it appears that modifying the Gnome theme with this script correctly sets the transparency. However, perhaps there are two layers to the greeter, and even though the background image is set, the additional layer is not exposed for configuration via gsettings. https://github.com/PRATAP-KUMAR/ubuntu-gdm-set- background/blob/main/ubuntu-gdm-set- background-23.04-transparent#L168-L171 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/2018672/+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 1740771] Re: the screen keeps locking while I watch video (missing support for Wayland's idle_inhibit_unstable_v1)
** Changed in: mutter (Ubuntu) Status: Fix Committed => Fix Released -- 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/1740771 Title: the screen keeps locking while I watch video (missing support for Wayland's idle_inhibit_unstable_v1) Status in MPV: Fix Released Status in Mutter: Fix Released Status in mpv package in Ubuntu: Fix Released Status in mutter package in Ubuntu: Fix Released Bug description: Upstream: https://gitlab.gnome.org/GNOME/mutter/issues/20 --- Reproducibility: 100% reproducible steps to reproduce: 1. $ mpv -fv anyvideo_long_enough.anyformat 2. now please refrain from any mouse/keyboard activity, wait for the screensaver to activate 3. screensaver activates problem: the screensaver activates desired behaviour: the screensaver shouldn't activate long description: Hello, the screen keeps locking while I watch video with mpv. Basically the screensaver gets activated. but according to man mpv: --heartbeat-cmd= WARNING: This option is redundant with Lua scripting. Further, it shouldn't be needed for disabling screensaver anyway, since mpv will call xdg-screensaver when using X11 backend. As a consequence this option has been deprecated with no direct replacement. ... That all said as the screen getting locked contradicts the manpage, I consider this a bug. Thank you for the fix in advance. ProblemType: Bug DistroRelease: Ubuntu 17.10 Package: mpv 0.26.0-3ubuntu1 ProcVersionSignature: Ubuntu 4.13.0-21.24-generic 4.13.13 Uname: Linux 4.13.0-21-generic x86_64 ApportVersion: 2.20.7-0ubuntu3.6 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Mon Jan 1 19:10:42 2018 InstallationDate: Installed on 2017-12-25 (7 days ago) InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20171018) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=hu_HU.UTF-8 SHELL=/bin/bash SourcePackage: mpv UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/mpv/+bug/1740771/+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 2033566] Re: Cursor drawn incorrectly on portrait mode
** Changed in: mutter (Ubuntu) Status: Fix Committed => Fix Released -- 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/2033566 Title: Cursor drawn incorrectly on portrait mode Status in Mutter: Fix Released Status in mutter package in Ubuntu: Fix Released Bug description: On 23.10 Ubuntu Mantic Minotaur (development branch). Noticed this when upgrading to gnome-shell 45~beta.1-0ubuntu2 While the cursor itself behaves normally on portrait mode (I can fully drag around windows and click on things normally), how it's drawn is not. It seems like the cursor is being drawn as if the monitor is in landscape mode? When moving my invisible up and down cursor near the top of my Portrait Right monitor, the drawn cursor on the top moving left and right. Moving the cursor to the top of my monitor causes the drawn one to hit the right side, and moving my cursor downwards causes the drawn one to go off-screen to the left. In Portrait Right at least, my monitor is physically vertical but the "monitor" that the mouse was drawn on is rotated 90 degrees clockwise with the top right corner aligned. Notably, the mouse is the correct orientation. Both the built in screen recorder (when it isn't crashing) and OBS with a Screen Capture (PipeWire) source both capture the cursor drawn correctly. ProblemType: Bug DistroRelease: Ubuntu 23.10 Package: gnome-shell 45~beta.1-0ubuntu2 ProcVersionSignature: Ubuntu 6.3.0-7.7-generic 6.3.5 Uname: Linux 6.3.0-7-generic x86_64 ApportVersion: 2.27.0-0ubuntu2 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Wed Aug 30 20:17:47 2023 DisplayManager: gdm3 InstallationDate: Installed on 2023-08-30 (1 days ago) InstallationMedia: Ubuntu 23.10 "Mantic Minotaur" - Daily amd64 (20230829) ProcEnviron: LANG=en_US.UTF-8 PATH=(custom, no user) SHELL=/bin/bash TERM=xterm-256color XDG_RUNTIME_DIR= RelatedPackageVersions: mutter-common 45~beta.1-1ubuntu1 SourcePackage: gnome-shell UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/mutter/+bug/2033566/+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 2033901] Re: gnome-shell regularly showing the "Oops! Something went wrong/ logout" screen after Alt-F2 r RET
** Changed in: mutter (Ubuntu) Status: Fix Committed => Fix Released -- 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/2033901 Title: gnome-shell regularly showing the "Oops! Something went wrong/ logout" screen after Alt-F2 r RET Status in Mutter: Unknown Status in mutter package in Ubuntu: Fix Released Bug description: With the most recent Mantic updates gnome-shell is regularly, but not every time, crashing and showing me the "Oops!" screen and forcing a logout when I type Alt-F2 r RET (using X11, obviously, since AFAIK that still isn't supported in Wayland). ProblemType: Bug DistroRelease: Ubuntu 23.10 Package: gnome-shell 45~beta.1-0ubuntu2 ProcVersionSignature: Ubuntu 6.3.0-7.7-generic 6.3.5 Uname: Linux 6.3.0-7-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.27.0-0ubuntu2 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: ubuntu:GNOME Date: Fri Sep 1 09:57:07 2023 DisplayManager: gdm3 InstallationDate: Installed on 2019-01-02 (1703 days ago) InstallationMedia: Ubuntu 18.10 "Cosmic Cuttlefish" - Release amd64 (20181017.3) RelatedPackageVersions: mutter-common 45~beta.1-1ubuntu1 SourcePackage: gnome-shell UpgradeStatus: Upgraded to mantic on 2023-05-20 (104 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/mutter/+bug/2033901/+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 2034602] Re: Some GTK4 apps don't respect dark theme
** Package changed: gnome-control-center (Ubuntu) => libadwaita-1 (Ubuntu) -- 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/2034602 Title: Some GTK4 apps don't respect dark theme Status in libadwaita-1 package in Ubuntu: New Bug description: I set the dark theme on the Settings, but just the Shell and GTK3 apps (Terminator) respect this change. The GNOME Control Center and the Text Editor keep using the light theme. I deleted my ~/.config/dconf directory, and after that everything became white (understandable, since that's the default theme), but I couldn't change. I think it's something related to GTK4 apps. ProblemType: Bug DistroRelease: Ubuntu 23.10 Package: gnome-control-center 1:45~rc-1ubuntu2 Uname: Linux 6.5.1-zabbly+ x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.27.0-0ubuntu2 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Wed Sep 6 14:00:59 2023 InstallationDate: Installed on 2021-11-26 (649 days ago) InstallationMedia: Ubuntu 21.10 "Impish Indri" - Release amd64 (20211012) SourcePackage: gnome-control-center UpgradeStatus: Upgraded to mantic on 2023-08-18 (20 days ago) modified.conffile..etc.default.apport: # set this to 0 to disable apport, or to 1 to enable it # you can temporarily override this with # sudo service apport start force_start=1 enabled=0 mtime.conffile..etc.default.apport: 2022-05-22T10:55:32.223191 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libadwaita-1/+bug/2034602/+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 1987209] Re: gnome-shell (Wayland) crashes with SIGSEGV when screen locker activates (jj), immediately after meta_workspace_get_work_area_for_monitor: assertion 'logical_monito
No, your bug 2034619 is not related to this. -- 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/1987209 Title: gnome-shell (Wayland) crashes with SIGSEGV when screen locker activates (jj), immediately after meta_workspace_get_work_area_for_monitor: assertion 'logical_monitor != NULL' failed Status in gnome-shell package in Ubuntu: Expired Bug description: Hi, On my Ubuntu 22.04 (migrated from 20.04 few days ago), I have a problem with the automatic lock screen which doesn't lock my session but closes it (and all opened applications in my session are closed too of course). In fact, I think the session is not really closed but there is some crash of gnome shell (see below). Maybe it's important, I have *2* monitors (more convenient for my tired eyes): * HP 24er (24") * ASUS MX279 (27") Theses 2 monitors are connected via a HDMI port, each on a dedicated card "Radeon Pro WX 3100" (1 card per monitor, so I have 2 same model cards "Radeon Pro WX 3100"). Here is my setting in "Privacy" > "Screen", to test quickly the automatic lock screen: ``` Blank Screen Delay: 1 minute Automatic Screen Lock: Automatic Screen Lock Delay: 30 seconds Lock Screen on Suspend: Show Notifications on Lock Screen: ``` Note: I have tested with a fresh and new Unix account, just created for the test (by `sudo adduser foo`) and the problem is present too. Below, you can see the output of the `journalctl -eb` where: 1. about ~13:02:50, screens begins to be blank, 2. about ~13:03:20, the automatic lock screen should start. As you can see below, "Aug 21 13:03:19 => gnome-shell: segfault": ``` Aug 21 13:00:39 flhpz4 PackageKit[2197]: resolve transaction /25167_acdeacea from uid 1000 finished with success after 229ms Aug 21 13:00:39 flhpz4 PackageKit[2197]: resolve transaction /25168_badabacd from uid 1000 finished with success after 235ms Aug 21 13:00:40 flhpz4 systemd[37743]: Started Application launched by gnome-shell. Aug 21 13:01:09 flhpz4 systemd[1]: systemd-timedated.service: Deactivated successfully. Aug 21 13:02:58 flhpz4 update-notifier[43667]: gtk_widget_get_scale_factor: assertion 'GTK_IS_WIDGET (widget)' failed Aug 21 13:02:58 flhpz4 update-notifier[43667]: gtk_widget_get_scale_factor: assertion 'GTK_IS_WIDGET (widget)' failed Aug 21 13:03:19 flhpz4 gnome-shell[37898]: meta_monitor_manager_get_logical_monitor_from_number: assertion '(unsigned int) number < g_list_length (manager->logical_monitors)' failed Aug 21 13:03:19 flhpz4 gnome-shell[37898]: meta_workspace_get_work_area_for_monitor: assertion 'logical_monitor != NULL' failed Aug 21 13:03:19 flhpz4 gnome-shell[37898]: meta_monitor_manager_get_logical_monitor_from_number: assertion '(unsigned int) number < g_list_length (manager->logical_monitors)' failed Aug 21 13:03:19 flhpz4 gnome-shell[37898]: meta_workspace_get_work_area_for_monitor: assertion 'logical_monitor != NULL' failed Aug 21 13:03:19 flhpz4 kernel: gnome-shell[37898]: segfault at 55a109404860 ip 55a109404860 sp 7fff85039338 error 15 Aug 21 13:03:20 flhpz4 kernel: Code: 00 00 21 00 00 00 00 00 00 00 69 6e 73 65 6e 73 69 74 69 76 65 00 00 00 00 00 6f 75 74 00 00 00 00 00 21 00 00 00 00 00 00 00 <00> 66 18 84 0d 7f 00 00 00 00 00 00 00 00 00 00 20 00 00 00 00 00 Aug 21 13:03:19 flhpz4 gsd-color[38044]: failed to find device: property match 'XRANDR_name'='DP-3' does not exist Aug 21 13:03:20 flhpz4 rtkit-daemon[1801]: Supervising 7 threads of 3 processes of 1 users. Aug 21 13:03:20 flhpz4 rtkit-daemon[1801]: Successfully made thread 47682 of process 37752 owned by '1000' RT at priority 5. Aug 21 13:03:20 flhpz4 rtkit-daemon[1801]: Supervising 8 threads of 3 processes of 1 users. Aug 21 13:03:21 flhpz4 gnome-calendar[47524]: Error reading events from display: Broken pipe Aug 21 13:03:21 flhpz4 evolution-alarm[38073]: Error reading events from display: Broken pipe Aug 21 13:03:21 flhpz4 seahorse[47526]: Error reading events from display: Broken pipe Aug 21 13:03:21 flhpz4 xdg-desktop-por[38284]: Error reading events from display: Broken pipe Aug 21 13:03:21 flhpz4 xdg-desktop-por[38239]: Error reading events from display: Broken pipe Aug 21 13:03:21 flhpz4 unknown[38050]: Error reading events from display: Broken pipe Aug 21 13:03:21 flhpz4 terminator[46053]: Error reading events from display: Connection reset by peer Aug 21 13:03:21 flhpz4 gsd-wacom[38078]: Error reading events from display: Broken pipe Aug 21 13:03:21 flhpz4 firefox[46499]: Error reading events from display: Broken pipe Aug 21 13:03:21 flhpz4 systemd[37743]: org.gnome.SettingsDaemon.Keyboard.service: Main process exited, code=exited, status=1/FAILURE Aug 21 13:03:21 flhpz4 systemd[37743]: xdg-desktop-portal-gnome.service: Main process exited, code=exited,
[Desktop-packages] [Bug 2034105] Re: Cursor didn't show up in X session when output from amd dgpu
Verified on SKU with AMD Navi3.x dgpu, the issue is fixed. Test environment: CID 202307-31876 $ uname -a Linux u-Precision-7875-Tower 6.5.0-1003-oem #3-Ubuntu SMP PREEMPT_DYNAMIC Mon Aug 28 15:04:22 UTC 2023 x86_64 x86_64 x86_64 GNU/Linux ~$ lspci | grep -i vga 03:00.0 VGA compatible controller: Advanced Micro Devices, Inc. [AMD/ATI] Device 7489 $ apt policy xserver-xorg-video-amdgpu xserver-xorg-video-amdgpu: Installed: 22.0.0-1ubuntu0.2 Candidate: 22.0.0-1ubuntu0.2 Version table: *** 22.0.0-1ubuntu0.2 500 500 http://tw.archive.ubuntu.com/ubuntu jammy-proposed/main amd64 Packages 100 /var/lib/dpkg/status ** Tags removed: verification-needed verification-needed-jammy ** Tags added: verification-done verification-done-jammy -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to xserver-xorg-video-amdgpu in Ubuntu. https://bugs.launchpad.net/bugs/2034105 Title: Cursor didn't show up in X session when output from amd dgpu Status in OEM Priority Project: New Status in xserver-xorg-video-amdgpu package in Ubuntu: Fix Released Status in xserver-xorg-video-amdgpu source package in Jammy: Fix Committed Bug description: [ Impact ] * There is no cursor in Xorg session when output from AMD Navi3.x dgpu [ Test Plan ] * Test on the DT with AMD Navi3.x dgpu * Attach external monitor to AMD Navi3.x dgpu * Switch to Xorg session when login * Check if cursor is appeared and works properly [ Where problems could occur ] * The implementation checks DRM_CAP_CURSOR_WIDTH and DRM_CAP_CURSOR_HEIGHT and fallback to original implementation if kernel can't report the caps. * The user might see different cursor size after the patch applied, since the driver will ask kernel for it but not the hard coded one. [ Other Info ] * Upstream commit: https://cgit.freedesktop.org/xorg/driver/xf86-video-amdgpu/commit/?id=9c959fac3af28d191105f63236096ad456dca614 * The patch has been included in mantic and lunar already To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/2034105/+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 2034472] Re: Not supported by GNOME 45
It looks like Ubuntu does package 'gnome-shell-extension-manager' and it works. It's only the 'Upgrade Assistant' page that is wrong for Ubuntu. We may choose to patch it in future, or you can just ignore it. ** Summary changed: - Not supported by GNOME 45 + gnome-shell-extension-manager Upgrade Assistant says 'Unsupported' for Ubuntu extensions ** Package changed: gnome-shell-extension-ubuntu-dock (Ubuntu) => gnome- shell-extension-manager (Ubuntu) ** Changed in: gnome-shell-extension-manager (Ubuntu) Importance: Undecided => Low ** Changed in: gnome-shell-extension-manager (Ubuntu) Status: Incomplete => Confirmed ** Changed in: gnome-shell-extension-manager (Ubuntu) Status: Confirmed => Won't Fix ** Changed in: gnome-shell-extension-manager (Ubuntu) Status: Won't Fix => Opinion -- 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/2034472 Title: gnome-shell-extension-manager Upgrade Assistant says 'Unsupported' for Ubuntu extensions Status in gnome-shell-extension-manager package in Ubuntu: Opinion Bug description: Extension Manager - Upgrade Assistant Report Currently on: GNOME 45.beta.1 Upgrading to: GNOME 45 On upgrading to GNOME 45, 1 out of 5 currently installed extensions will be compatible (20%). User-Installed Extensions: 'Battery Indicator Icon' by Deminder Extension ID: battery-indicator-icon@Deminder Supported: No System Extensions: 'Ubuntu Dock' by didrocks Extension ID: ubuntu-d...@ubuntu.com Supported: No 'Ubuntu Tiling Assistant' by (null) Extension ID: tiling-assist...@ubuntu.com Supported: Unknown 'Desktop Icons NG (DING)' by rastersoft Extension ID: d...@rastersoft.com Supported: Yes 'Ubuntu AppIndicators' by didrocks Extension ID: ubuntu-appindicat...@ubuntu.com Supported: No To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell-extension-manager/+bug/2034472/+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 2017734] Re: package libgdk-pixbuf-2.0-0:amd64 2.42.10+dfsg-1build1 failed to install/upgrade: triggers looping, abandoned
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: gdk-pixbuf (Ubuntu) Status: New => Confirmed -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gdk-pixbuf in Ubuntu. https://bugs.launchpad.net/bugs/2017734 Title: package libgdk-pixbuf-2.0-0:amd64 2.42.10+dfsg-1build1 failed to install/upgrade: triggers looping, abandoned Status in gdk-pixbuf package in Ubuntu: Confirmed Bug description: Upgrade from Ubuntu 22.10 to 23.04 on iMac 5k 2014 ProblemType: Package DistroRelease: Ubuntu 23.04 Package: libgdk-pixbuf-2.0-0:amd64 2.42.10+dfsg-1build1 ProcVersionSignature: Ubuntu 5.19.0-41.42-generic 5.19.17 Uname: Linux 5.19.0-41-generic x86_64 NonfreeKernelModules: wl ApportVersion: 2.26.1-0ubuntu2 Architecture: amd64 CasperMD5CheckResult: pass Date: Wed Apr 26 08:57:37 2023 ErrorMessage: triggers looping, abandoned InstallationDate: Installed on 2023-01-24 (91 days ago) InstallationMedia: Ubuntu 22.04.1 LTS "Jammy Jellyfish" - Release amd64 (20220809.1) Python3Details: /usr/bin/python3.11, Python 3.11.2, python3-minimal, 3.11.2-1 PythonDetails: N/A RebootRequiredPkgs: Error: path contained symlinks. RelatedPackageVersions: dpkg 1.21.21ubuntu1 apt 2.6.0 SourcePackage: gdk-pixbuf Title: package libgdk-pixbuf-2.0-0:amd64 2.42.10+dfsg-1build1 failed to install/upgrade: triggers looping, abandoned UpgradeStatus: Upgraded to lunar on 2023-04-26 (0 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gdk-pixbuf/+bug/2017734/+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 1877038] Re: [upstream] Firefox lacks FIDO2 support with Yubikeys
** Bug watch added: Mozilla Bugzilla #1846836 https://bugzilla.mozilla.org/show_bug.cgi?id=1846836 -- 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/1877038 Title: [upstream] Firefox lacks FIDO2 support with Yubikeys Status in Mozilla Firefox: Confirmed Status in firefox package in Ubuntu: Triaged Bug description: Ubuntu LTS versions affected. "Passwordless" authentications with Yubikeys using Firefox don't work with FIDO2. Tested both with the yubikey software packages from the bionic/universe repo and those from the vendor https://www.yubico.com/ To manage notifications about this bug go to: https://bugs.launchpad.net/firefox/+bug/1877038/+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]
Is this still reproducible with the latest 115.2 release? We went through some pretty in-depth optimization and it should behave much better. Even more improvements are on the horizon in the upcoming betas. -- 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 1877038]
I just tested nightly build which includes fix of [~~1846836~~](https://bugzilla.mozilla.org/show_bug.cgi?id=1846836) and it worked like a charm, restore FF114's behavior. Is there plan backport to 115ESR? -- 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/1877038 Title: [upstream] Firefox lacks FIDO2 support with Yubikeys Status in Mozilla Firefox: Confirmed Status in firefox package in Ubuntu: Triaged Bug description: Ubuntu LTS versions affected. "Passwordless" authentications with Yubikeys using Firefox don't work with FIDO2. Tested both with the yubikey software packages from the bionic/universe repo and those from the vendor https://www.yubico.com/ To manage notifications about this bug go to: https://bugs.launchpad.net/firefox/+bug/1877038/+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]
With these settings reverted back to normal >gfx.webrender.all >gfx.webrender.force-disabled > > Switch the first one to false (it was already switched to false) and the > second one to true (I switched this one manually) > everything works smooths and no cpu usage jumps happen. I can still reproduce unusual high CPU usage. There is no perceptible lag, but CPU usage still jumps to about 75 % on my end. To compare, continuous scrolling of websites in Firefox, even complex ones, consumes less than 25 % of CPU. So, the claim “behave much better” might be true, but the mouse-over effect still seems excessively wasteful of resources. -- 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 1704002] Re: Missing icon for mono speakers
The symlinks are broken from Focal or before. The icons exist in Yaru. ** Tags added: bitesize focal jammy lunar mantic -- 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/1704002 Title: Missing icon for mono speakers Status in gnome-control-center: Confirmed Status in gnome-control-center package in Ubuntu: Fix Released Bug description: For mono speakers (e.g. Bluetooth HFP/HSP profiles) there is no icon, and so the default missing icon is shown. We don't have assets for a mono speaker. To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-control-center/+bug/1704002/+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 1987209] Re: gnome-shell (Wayland) crashes with SIGSEGV when screen locker activates (jj), immediately after meta_workspace_get_work_area_for_monitor: assertion 'logical_monito
I have this issue on Ubuntu 23.10. Lock screen works only with an external monitor connected. Otherwise the session is ended and the user is logged out and brought to the gdm screen. Let me know what logs you need. -- 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/1987209 Title: gnome-shell (Wayland) crashes with SIGSEGV when screen locker activates (jj), immediately after meta_workspace_get_work_area_for_monitor: assertion 'logical_monitor != NULL' failed Status in gnome-shell package in Ubuntu: Expired Bug description: Hi, On my Ubuntu 22.04 (migrated from 20.04 few days ago), I have a problem with the automatic lock screen which doesn't lock my session but closes it (and all opened applications in my session are closed too of course). In fact, I think the session is not really closed but there is some crash of gnome shell (see below). Maybe it's important, I have *2* monitors (more convenient for my tired eyes): * HP 24er (24") * ASUS MX279 (27") Theses 2 monitors are connected via a HDMI port, each on a dedicated card "Radeon Pro WX 3100" (1 card per monitor, so I have 2 same model cards "Radeon Pro WX 3100"). Here is my setting in "Privacy" > "Screen", to test quickly the automatic lock screen: ``` Blank Screen Delay: 1 minute Automatic Screen Lock: Automatic Screen Lock Delay: 30 seconds Lock Screen on Suspend: Show Notifications on Lock Screen: ``` Note: I have tested with a fresh and new Unix account, just created for the test (by `sudo adduser foo`) and the problem is present too. Below, you can see the output of the `journalctl -eb` where: 1. about ~13:02:50, screens begins to be blank, 2. about ~13:03:20, the automatic lock screen should start. As you can see below, "Aug 21 13:03:19 => gnome-shell: segfault": ``` Aug 21 13:00:39 flhpz4 PackageKit[2197]: resolve transaction /25167_acdeacea from uid 1000 finished with success after 229ms Aug 21 13:00:39 flhpz4 PackageKit[2197]: resolve transaction /25168_badabacd from uid 1000 finished with success after 235ms Aug 21 13:00:40 flhpz4 systemd[37743]: Started Application launched by gnome-shell. Aug 21 13:01:09 flhpz4 systemd[1]: systemd-timedated.service: Deactivated successfully. Aug 21 13:02:58 flhpz4 update-notifier[43667]: gtk_widget_get_scale_factor: assertion 'GTK_IS_WIDGET (widget)' failed Aug 21 13:02:58 flhpz4 update-notifier[43667]: gtk_widget_get_scale_factor: assertion 'GTK_IS_WIDGET (widget)' failed Aug 21 13:03:19 flhpz4 gnome-shell[37898]: meta_monitor_manager_get_logical_monitor_from_number: assertion '(unsigned int) number < g_list_length (manager->logical_monitors)' failed Aug 21 13:03:19 flhpz4 gnome-shell[37898]: meta_workspace_get_work_area_for_monitor: assertion 'logical_monitor != NULL' failed Aug 21 13:03:19 flhpz4 gnome-shell[37898]: meta_monitor_manager_get_logical_monitor_from_number: assertion '(unsigned int) number < g_list_length (manager->logical_monitors)' failed Aug 21 13:03:19 flhpz4 gnome-shell[37898]: meta_workspace_get_work_area_for_monitor: assertion 'logical_monitor != NULL' failed Aug 21 13:03:19 flhpz4 kernel: gnome-shell[37898]: segfault at 55a109404860 ip 55a109404860 sp 7fff85039338 error 15 Aug 21 13:03:20 flhpz4 kernel: Code: 00 00 21 00 00 00 00 00 00 00 69 6e 73 65 6e 73 69 74 69 76 65 00 00 00 00 00 6f 75 74 00 00 00 00 00 21 00 00 00 00 00 00 00 <00> 66 18 84 0d 7f 00 00 00 00 00 00 00 00 00 00 20 00 00 00 00 00 Aug 21 13:03:19 flhpz4 gsd-color[38044]: failed to find device: property match 'XRANDR_name'='DP-3' does not exist Aug 21 13:03:20 flhpz4 rtkit-daemon[1801]: Supervising 7 threads of 3 processes of 1 users. Aug 21 13:03:20 flhpz4 rtkit-daemon[1801]: Successfully made thread 47682 of process 37752 owned by '1000' RT at priority 5. Aug 21 13:03:20 flhpz4 rtkit-daemon[1801]: Supervising 8 threads of 3 processes of 1 users. Aug 21 13:03:21 flhpz4 gnome-calendar[47524]: Error reading events from display: Broken pipe Aug 21 13:03:21 flhpz4 evolution-alarm[38073]: Error reading events from display: Broken pipe Aug 21 13:03:21 flhpz4 seahorse[47526]: Error reading events from display: Broken pipe Aug 21 13:03:21 flhpz4 xdg-desktop-por[38284]: Error reading events from display: Broken pipe Aug 21 13:03:21 flhpz4 xdg-desktop-por[38239]: Error reading events from display: Broken pipe Aug 21 13:03:21 flhpz4 unknown[38050]: Error reading events from display: Broken pipe Aug 21 13:03:21 flhpz4 terminator[46053]: Error reading events from display: Connection reset by peer Aug 21 13:03:21 flhpz4 gsd-wacom[38078]: Error reading events from display: Broken pipe Aug 21 13:03:21 flhpz4 firefox[46499]: Error reading events from display: Broken pipe Aug 21 13:03:21 flhpz4 systemd[37743]:
[Desktop-packages] [Bug 2034579] Re: [FFe] Use tecla to display keyboard layouts
** Description changed: Explanation of FeatureFreeze exception === - GNOME 45 includes a new keyboard layout viewer named Tecla to replace gkbd-keyboard-display (old and written in GTK3). The Main Inclusion Request for this was approved but I reverted the switch in the gnome-control-center, gnome-initial-setup, and gnome-shell packaging because the first release of Tecla crashed with some keyboard layouts. That issue has been fixed for the gnome-control-center integration. + GNOME 45 includes a new keyboard layout viewer named Tecla to replace gkbd-keyboard-display (old and written in GTK3). The Main Inclusion Request for this was approved in LP: #2026774 but I reverted the switch in the gnome-control-center, gnome-initial-setup, and gnome-shell packaging because the first release of Tecla crashed with some keyboard layouts. That issue has been fixed for the gnome-control-center & gnome-initial-setup integration. Specific changes 1. Drop the Tecla patch from gnome-control-center and gnome-initial-setup 2. Have gnome-control-center and gnome-initial-setup depend on Tecla - 3. Promote Tecla to main + 3. Promote Tecla to main. The approved MIR is https://launchpad.net/bugs/2026774 (Both 1 and 2 have been done in Debian Unstable now.) Later changes = In my testing with GNOME Shell 45 Beta, there are still some issues with the Tecla integration. I'll file those issues upstream and we'd like to be able to switch GNOME Shell to use Tecla later this cycle. We would… 4. Drop the Tecla patch from gnome-shell 5. Have gnome-shell depend on Tecla 6. Demote libgnomekbd to Universe Testing Done I successfully completed Test Case 1 and the first 5 steps of Test Case 2 from https://wiki.ubuntu.com/DesktopTeam/TestPlans/gjs -- 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/2034579 Title: [FFe] Use tecla to display keyboard layouts Status in gnome-control-center package in Ubuntu: New Bug description: Explanation of FeatureFreeze exception === GNOME 45 includes a new keyboard layout viewer named Tecla to replace gkbd-keyboard-display (old and written in GTK3). The Main Inclusion Request for this was approved in LP: #2026774 but I reverted the switch in the gnome-control-center, gnome-initial-setup, and gnome-shell packaging because the first release of Tecla crashed with some keyboard layouts. That issue has been fixed for the gnome-control-center & gnome-initial-setup integration. Specific changes 1. Drop the Tecla patch from gnome-control-center and gnome-initial-setup 2. Have gnome-control-center and gnome-initial-setup depend on Tecla 3. Promote Tecla to main. The approved MIR is https://launchpad.net/bugs/2026774 (Both 1 and 2 have been done in Debian Unstable now.) Later changes = In my testing with GNOME Shell 45 Beta, there are still some issues with the Tecla integration. I'll file those issues upstream and we'd like to be able to switch GNOME Shell to use Tecla later this cycle. We would… 4. Drop the Tecla patch from gnome-shell 5. Have gnome-shell depend on Tecla 6. Demote libgnomekbd to Universe Testing Done I successfully completed Test Case 1 and the first 5 steps of Test Case 2 from https://wiki.ubuntu.com/DesktopTeam/TestPlans/gjs To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-control-center/+bug/2034579/+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 2034615] [NEW] xdg-desktop-portal crashed with SIGSEGV when attaching the file from local disk in browser
Public bug reported:
ThreadStacktrace:
.
Thread 7 (Thread 0x7fcef893e640 (LWP 22858)):
#0 0x7fcefcb87868 in __GI___clock_nanosleep (clock_id=clock_id@entry=0,
flags=flags@entry=0, req=req@entry=0x7fcef893dcb0,
rem=rem@entry=0x7fcef893dcb0) at ../sysdeps/unix/sysv/linux/clock_nanosleep.c:78
sc_cancel_oldtype = 0
sc_ret =
r =
#1 0x7fcefcb8c6e7 in __GI___nanosleep (req=req@entry=0x7fcef893dcb0,
rem=rem@entry=0x7fcef893dcb0) at ../sysdeps/unix/sysv/linux/nanosleep.c:25
ret =
#2 0x7fcefcb8c61e in __sleep (seconds=0) at ../sysdeps/posix/sleep.c:55
save_errno = 0
max = 4294967295
ts = {tv_sec = 26, tv_nsec = 541872717}
#3 0x563877d2cc43 in ?? ()
No symbol table info available.
#4 0x7fcefce17a51 in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
No symbol table info available.
#5 0x7fcefcb36b43 in start_thread (arg=) at
./nptl/pthread_create.c:442
ret =
pd =
out =
unwind_buf = {cancel_jmp_buf = {{jmp_buf = {140730024450480,
-8082956545549480131, 140526910432832, 11, 140526979606608, 140730024450832,
8092512230473125693, 8092520745904164669}, mask_was_saved = 0}}, priv = {pad =
{0x0, 0x0, 0x0, 0x0}, data = {prev = 0x0, cleanup = 0x0, canceltype = 0}}}
not_first_call =
#6 0x7fcefcbc8a00 in clone3 () at
../sysdeps/unix/sysv/linux/x86_64/clone3.S:81
No locals.
.
Thread 6 (Thread 0x7fcefb54a640 (LWP 22818)):
#0 0x7fcefcbbad7f in __GI___poll (fds=0x5638789233f0, nfds=3, timeout=-1)
at ../sysdeps/unix/sysv/linux/poll.c:29
sc_ret = -516
sc_cancel_oldtype = 0
sc_ret =
#1 0x7fcefce3e1f6 in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
No symbol table info available.
#2 0x7fcefcde82b3 in g_main_loop_run () from
/lib/x86_64-linux-gnu/libglib-2.0.so.0
No symbol table info available.
#3 0x7fcefd04207a in ?? () from /lib/x86_64-linux-gnu/libgio-2.0.so.0
No symbol table info available.
#4 0x7fcefce17a51 in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
No symbol table info available.
#5 0x7fcefcb36b43 in start_thread (arg=) at
./nptl/pthread_create.c:442
ret =
pd =
out =
unwind_buf = {cancel_jmp_buf = {{jmp_buf = {140730024450816,
-8082956545549480131, 140526956619328, 11, 140526979606608, 140730024451168,
8092519319316647741, 8092520745904164669}, mask_was_saved = 0}}, priv = {pad =
{0x0, 0x0, 0x0, 0x0}, data = {prev = 0x0, cleanup = 0x0, canceltype = 0}}}
not_first_call =
#6 0x7fcefcbc8a00 in clone3 () at
../sysdeps/unix/sysv/linux/x86_64/clone3.S:81
No locals.
.
Thread 5 (Thread 0x7fcefbf58640 (LWP 22817)):
#0 0x7fcefcbbad7f in __GI___poll (fds=0x5638789112a0, nfds=2,
timeout=3717) at ../sysdeps/unix/sysv/linux/poll.c:29
sc_ret = -516
sc_cancel_oldtype = 0
sc_ret =
#1 0x7fcefce3e1f6 in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
No symbol table info available.
#2 0x7fcefcde63e3 in g_main_context_iteration () from
/lib/x86_64-linux-gnu/libglib-2.0.so.0
No symbol table info available.
#3 0x7fcefcde6431 in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
No symbol table info available.
#4 0x7fcefce17a51 in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
No symbol table info available.
#5 0x7fcefcb36b43 in start_thread (arg=) at
./nptl/pthread_create.c:442
ret =
pd =
out =
unwind_buf = {cancel_jmp_buf = {{jmp_buf = {140730024445888,
-8082956545549480131, 140526967162432, 2, 140526979606608, 140730024446240,
8092517946000854845, 8092520745904164669}, mask_was_saved = 0}}, priv = {pad =
{0x0, 0x0, 0x0, 0x0}, data = {prev = 0x0, cleanup = 0x0, canceltype = 0}}}
not_first_call =
#6 0x7fcefcbc8a00 in clone3 () at
../sysdeps/unix/sysv/linux/x86_64/clone3.S:81
No locals.
.
Thread 4 (Thread 0x7fcef913f640 (LWP 22857)):
#0 0x7fcefcbc7fde in epoll_wait (epfd=15, events=0x7fcef913e880,
maxevents=32, timeout=-1) at ../sysdeps/unix/sysv/linux/epoll_wait.c:30
sc_ret = -4
sc_cancel_oldtype = 0
sc_ret =
#1 0x7fcef92ac918 in ?? () from
/usr/lib/x86_64-linux-gnu/spa-0.2/support/libspa-support.so
No symbol table info available.
#2 0x7fcef929fd7c in ?? () from
/usr/lib/x86_64-linux-gnu/spa-0.2/support/libspa-support.so
No symbol table info available.
#3 0x7fcefd144226 in ?? () from /lib/x86_64-linux-gnu/libpipewire-0.3.so.0
No symbol table info available.
#4 0x7fcefcb36b43 in start_thread (arg=) at
./nptl/pthread_create.c:442
ret =
pd =
out =
unwind_buf = {cancel_jmp_buf = {{jmp_buf = {140730024449328,
-8082956545549480131, 140526918825536, 0, 140526979606608, 140730024449680,
8092515527397396285, 8092520745904164669}, mask_was_saved = 0}}, priv = {pad =
{0x0, 0x0, 0x0, 0x0}, data = {prev = 0x0,
[Desktop-packages] [Bug 2034602] Re: Some GTK4 apps don't respect dark theme
** Package changed: ubuntu => gnome-control-center (Ubuntu) -- 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/2034602 Title: Some GTK4 apps don't respect dark theme Status in gnome-control-center package in Ubuntu: New Bug description: I set the dark theme on the Settings, but just the Shell and GTK3 apps (Terminator) respect this change. The GNOME Control Center and the Text Editor keep using the light theme. I deleted my ~/.config/dconf directory, and after that everything became white (understandable, since that's the default theme), but I couldn't change. I think it's something related to GTK4 apps. ProblemType: Bug DistroRelease: Ubuntu 23.10 Package: gnome-control-center 1:45~rc-1ubuntu2 Uname: Linux 6.5.1-zabbly+ x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.27.0-0ubuntu2 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Wed Sep 6 14:00:59 2023 InstallationDate: Installed on 2021-11-26 (649 days ago) InstallationMedia: Ubuntu 21.10 "Impish Indri" - Release amd64 (20211012) SourcePackage: gnome-control-center UpgradeStatus: Upgraded to mantic on 2023-08-18 (20 days ago) modified.conffile..etc.default.apport: # set this to 0 to disable apport, or to 1 to enable it # you can temporarily override this with # sudo service apport start force_start=1 enabled=0 mtime.conffile..etc.default.apport: 2022-05-22T10:55:32.223191 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-control-center/+bug/2034602/+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 2034602] [NEW] Some GTK4 apps don't respect dark theme
You have been subscribed to a public bug: I set the dark theme on the Settings, but just the Shell and GTK3 apps (Terminator) respect this change. The GNOME Control Center and the Text Editor keep using the light theme. I deleted my ~/.config/dconf directory, and after that everything became white (understandable, since that's the default theme), but I couldn't change. I think it's something related to GTK4 apps. ProblemType: Bug DistroRelease: Ubuntu 23.10 Package: gnome-control-center 1:45~rc-1ubuntu2 Uname: Linux 6.5.1-zabbly+ x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.27.0-0ubuntu2 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Wed Sep 6 14:00:59 2023 InstallationDate: Installed on 2021-11-26 (649 days ago) InstallationMedia: Ubuntu 21.10 "Impish Indri" - Release amd64 (20211012) SourcePackage: gnome-control-center UpgradeStatus: Upgraded to mantic on 2023-08-18 (20 days ago) modified.conffile..etc.default.apport: # set this to 0 to disable apport, or to 1 to enable it # you can temporarily override this with # sudo service apport start force_start=1 enabled=0 mtime.conffile..etc.default.apport: 2022-05-22T10:55:32.223191 ** Affects: gnome-control-center (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug mantic third-party-packages -- Some GTK4 apps don't respect dark theme https://bugs.launchpad.net/bugs/2034602 You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-control-center in Ubuntu. -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 2034579] Re: [FFe] Use tecla to display keyboard layouts
** Changed in: gnome-control-center (Ubuntu) Status: Incomplete => New ** Description changed: Explanation of FeatureFreeze exception === GNOME 45 includes a new keyboard layout viewer named Tecla to replace gkbd-keyboard-display (old and written in GTK3). The Main Inclusion Request for this was approved but I reverted the switch in the gnome-control-center, gnome-initial-setup, and gnome-shell packaging because the first release of Tecla crashed with some keyboard layouts. That issue has been fixed for the gnome-control-center integration. Specific changes - Drop the Tecla patch from gnome-control-center and gnome-initial-setup - Have gnome-control-center and gnome-initial-setup depend on Tecla - Promote Tecla to main + 1. Drop the Tecla patch from gnome-control-center and gnome-initial-setup + 2. Have gnome-control-center and gnome-initial-setup depend on Tecla + 3. Promote Tecla to main + + (Both 1 and 2 have been done in Debian Unstable now.) Later changes = In my testing with GNOME Shell 45 Beta, there are still some issues with the Tecla integration. I'll file those issues upstream and we'd like to be able to switch GNOME Shell to use Tecla later this cycle. We would… - Drop the Tecla patch from gnome-shell - Have gnome-shell depend on Tecla - Demote libgnomekbd to Universe + 4. Drop the Tecla patch from gnome-shell + 5. Have gnome-shell depend on Tecla + 6. Demote libgnomekbd to Universe Testing Done I successfully completed Test Case 1 and the first 5 steps of Test Case 2 from https://wiki.ubuntu.com/DesktopTeam/TestPlans/gjs -- 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/2034579 Title: [FFe] Use tecla to display keyboard layouts Status in gnome-control-center package in Ubuntu: New Bug description: Explanation of FeatureFreeze exception === GNOME 45 includes a new keyboard layout viewer named Tecla to replace gkbd-keyboard-display (old and written in GTK3). The Main Inclusion Request for this was approved but I reverted the switch in the gnome-control-center, gnome-initial-setup, and gnome-shell packaging because the first release of Tecla crashed with some keyboard layouts. That issue has been fixed for the gnome-control-center integration. Specific changes 1. Drop the Tecla patch from gnome-control-center and gnome-initial-setup 2. Have gnome-control-center and gnome-initial-setup depend on Tecla 3. Promote Tecla to main (Both 1 and 2 have been done in Debian Unstable now.) Later changes = In my testing with GNOME Shell 45 Beta, there are still some issues with the Tecla integration. I'll file those issues upstream and we'd like to be able to switch GNOME Shell to use Tecla later this cycle. We would… 4. Drop the Tecla patch from gnome-shell 5. Have gnome-shell depend on Tecla 6. Demote libgnomekbd to Universe Testing Done I successfully completed Test Case 1 and the first 5 steps of Test Case 2 from https://wiki.ubuntu.com/DesktopTeam/TestPlans/gjs To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-control-center/+bug/2034579/+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 1865226] Re: gdm-smartcard pam config needs to be updated for Ubuntu and installed
Also, this but is missing the SRU template, in case the sssd upload I mentioned in my previous comment is really addressing this bug. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-settings-daemon in Ubuntu. https://bugs.launchpad.net/bugs/1865226 Title: gdm-smartcard pam config needs to be updated for Ubuntu and installed Status in GNOME Settings Daemon: Fix Released Status in gdm3 package in Ubuntu: Fix Released Status in gnome-settings-daemon package in Ubuntu: Fix Released Status in gdm3 source package in Focal: In Progress Status in gnome-settings-daemon source package in Focal: In Progress Status in gdm3 package in Debian: Fix Released Bug description: the pam profile for gdm-smartcard is missing. gdm refuses to login with a smartcard. Looking at ubuntu/+source/gdm3, other pam files are pregenerated into debian/ and installed from there; gdm-smartcard is left out. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: gdm3 3.28.3-0ubuntu18.04.4 ProcVersionSignature: Ubuntu 5.3.0-24.26~18.04.2-generic 5.3.10 Uname: Linux 5.3.0-24-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair nvidia_modeset nvidia ApportVersion: 2.20.9-0ubuntu7.11 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Fri Feb 28 14:30:30 2020 InstallationDate: Installed on 2016-05-23 (1376 days ago) InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 (20160420.1) SourcePackage: gdm3 UpgradeStatus: No upgrade log present (probably fresh install) mtime.conffile..etc.gdm3.Xsession: 2018-04-27T11:41:04.766901 To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-settings-daemon/+bug/1865226/+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 2028081] Re: tecla crashed with SIGSEGV in xkb_keymap_ref()
This bug was fixed in the package tecla - 45~rc-1 --- tecla (45~rc-1) unstable; urgency=medium * New upstream release - Fixes crash with some keyboard layouts (Closes: #1043456, LP: #2028081) - Fixes mismatched LICENSE file (LP: #2026761) -- Jeremy Bícha Wed, 06 Sep 2023 08:42:46 -0400 ** Changed in: tecla (Ubuntu) Status: New => Fix Released -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to tecla in Ubuntu. https://bugs.launchpad.net/bugs/2028081 Title: tecla crashed with SIGSEGV in xkb_keymap_ref() Status in Tecla: Fix Released Status in tecla package in Ubuntu: Fix Released Bug description: I cherry-pick the recent "switch to tecla" commits for both gnome-control-center and gnome-shell (and logged out and logged back to use the updated gnome-shell). I then ran sudo apt install language-pack-gnome-fr tecla I ran gnome-control-center from my terminal, switched to the Keyboard panel, then added the Input Source French (AZERTY). I then clicked ⋮ and chose View Keyboard Layout (next to French (AZERTY). I got this error in my terminal and tecla did not start. xkbcommon: ERROR: Couldn't find file "symbols/azerty" in include paths xkbcommon: ERROR: 1 include paths searched: xkbcommon: ERROR: /usr/share/X11/xkb xkbcommon: ERROR: 4 include paths could not be added: xkbcommon: ERROR: /home/jeremy/.config/xkb xkbcommon: ERROR: /home/jeremy/.config/xkb xkbcommon: ERROR: /home/jeremy/.xkb xkbcommon: ERROR: /etc/xkb xkbcommon: ERROR: Abandoning symbols file "(unnamed)" xkbcommon: ERROR: Failed to compile xkb_symbols xkbcommon: ERROR: Failed to compile keymap I get the same problem with GNOME Shell's keyboard layout switcher. Things do work fine with my default English (US) keyboard layout. ProblemType: Crash DistroRelease: Ubuntu 23.10 Package: tecla 45~alpha-2 ProcVersionSignature: Ubuntu 6.3.0-7.7-generic 6.3.5 Uname: Linux 6.3.0-7-generic x86_64 ApportVersion: 2.26.1-0ubuntu3 Architecture: amd64 CasperMD5CheckResult: pass CrashCounter: 1 CurrentDesktop: ubuntu:GNOME Date: Tue Jul 18 14:31:23 2023 ExecutablePath: /usr/bin/tecla InstallationDate: Installed on 2023-07-18 (0 days ago) InstallationMedia: Ubuntu 23.10 "Mantic Minotaur" - Daily amd64 (20230718) ProcCmdline: tecla fr+azerty ProcEnviron: LANG=en_US.UTF-8 PATH=(custom, no user) SHELL=/bin/bash TERM=xterm-256color XDG_RUNTIME_DIR= SegvAnalysis: Segfault happened at: 0x7fbfc1ca9d74 : addl $0x1,0x8(%rdi) PC (0x7fbfc1ca9d74) ok source "$0x1" ok destination "0x8(%rdi)" (0x0008) not located in a known VMA region (needed writable region)! SegvReason: writing NULL VMA Signal: 11 SourcePackage: tecla StacktraceTop: xkb_keymap_ref () from /lib/x86_64-linux-gnu/libxkbcommon.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: tecla crashed with SIGSEGV in xkb_keymap_ref() UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sudo users separator: To manage notifications about this bug go to: https://bugs.launchpad.net/tecla/+bug/2028081/+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 2026761] Re: Mismatched LICENSE file
This bug was fixed in the package tecla - 45~rc-1 --- tecla (45~rc-1) unstable; urgency=medium * New upstream release - Fixes crash with some keyboard layouts (Closes: #1043456, LP: #2028081) - Fixes mismatched LICENSE file (LP: #2026761) -- Jeremy Bícha Wed, 06 Sep 2023 08:42:46 -0400 ** Changed in: tecla (Ubuntu) Status: Triaged => Fix Released -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to tecla in Ubuntu. https://bugs.launchpad.net/bugs/2026761 Title: Mismatched LICENSE file Status in Tecla: Fix Released Status in tecla package in Ubuntu: Fix Released Bug description: See the upstream issue To manage notifications about this bug go to: https://bugs.launchpad.net/tecla/+bug/2026761/+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 1865226] Re: gdm-smartcard pam config needs to be updated for Ubuntu and installed
There is an sssd package in focal-unapproved that points at this bug, with this d/changelog snippet: * debian/patches: Backport patches atches to support properly GDM smartcard login (LP: #1865226) (sic) But there is no sssd task in this bug. I also don't see a gdm3 upload to focal unapproved, nor gnome-settings- daemon. Can somebody please clarify this situation? What is needed in focal to fix this bug? -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-settings-daemon in Ubuntu. https://bugs.launchpad.net/bugs/1865226 Title: gdm-smartcard pam config needs to be updated for Ubuntu and installed Status in GNOME Settings Daemon: Fix Released Status in gdm3 package in Ubuntu: Fix Released Status in gnome-settings-daemon package in Ubuntu: Fix Released Status in gdm3 source package in Focal: In Progress Status in gnome-settings-daemon source package in Focal: In Progress Status in gdm3 package in Debian: Fix Released Bug description: the pam profile for gdm-smartcard is missing. gdm refuses to login with a smartcard. Looking at ubuntu/+source/gdm3, other pam files are pregenerated into debian/ and installed from there; gdm-smartcard is left out. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: gdm3 3.28.3-0ubuntu18.04.4 ProcVersionSignature: Ubuntu 5.3.0-24.26~18.04.2-generic 5.3.10 Uname: Linux 5.3.0-24-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair nvidia_modeset nvidia ApportVersion: 2.20.9-0ubuntu7.11 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Fri Feb 28 14:30:30 2020 InstallationDate: Installed on 2016-05-23 (1376 days ago) InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 (20160420.1) SourcePackage: gdm3 UpgradeStatus: No upgrade log present (probably fresh install) mtime.conffile..etc.gdm3.Xsession: 2018-04-27T11:41:04.766901 To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-settings-daemon/+bug/1865226/+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 2031406] Re: [MIR] libei
build test failures are no longer ignored on s390x ** No longer affects: mutter (Ubuntu) -- 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/2031406 Title: [MIR] libei Status in libei package in Ubuntu: Fix Released Bug description: [Availability] - The package libei is already in Ubuntu universe. - The package libei builds for the architectures it is designed to work on. - Link to package https://launchpad.net/ubuntu/+source/libei [Rationale] - The package libei is required in Ubuntu main as a new required dependency for Mutter 45 - The package libei will generally be useful for a large part of our user base - The package libei is a new runtime dependency of package mutter that we already support - There is no other/better way to solve this that is already in main or should go universe->main instead of this. The package libei is required in Ubuntu main no later than August 17 due to Ubuntu 23.10 Feature Freeze. Obviously, that's an unrealistic deadline but the dependency is in mantic-proposed now (some other work is necessary for mutter to migrate out of mantic-proposed). It might be possible to temporarily vendor libei into Mutter. [Security] - No CVEs/security issues in this software in the past (new software, only packaged now in Ubuntu) - no `suid` or `sgid` binaries - no executables in `/sbin` and `/usr/sbin` - Package does not install services, timers or recurring jobs - Packages does not open privileged ports (ports < 1024). - Package does not expose any external endpoints - Packages does not contain extensions to security-sensitive software (filters, scanners, plugins, UI skins, ...) libei is a library for emulated input. It can forward physical or logical device input for use by things like GNOME Remote Desktop or sandboxed apps or for fake input for automated actions (like could be done with xdotool). [Quality assurance - function/usage] - The package works well right after install [Quality assurance - maintenance] - The package is maintained well in Debian/Ubuntu/Upstream and does not have too many, long-term & critical, open bugs - Ubuntu https://bugs.launchpad.net/ubuntu/+source/libei/ - Debian https://bugs.debian.org/cgi-bin/pkgreport.cgi?src=libei (not in Debian yet) - Upstream https://gitlab.freedesktop.org/libinput/libei/-/issues [Quality assurance - testing] - The package runs a test suite on build time, if it fails it makes the build fail, link to build log https://launchpad.net/ubuntu/+source/libei/1.0.0-0ubuntu2 Note that the build test failures are temporarily ignored on s390x which is not a supported Ubuntu Desktop architecture, but the issue has been reported upstream and is being worked on: https://gitlab.freedesktop.org/libinput/libei/-/issues/41 - The package does not run an autopkgtest because we haven't written one yet. We may run upstream's build test with our autopkgtest architecture. - Some tests using libei also have been added to Mutter and we do run Mutter's tests both at build time and as installed tests with autopkgtest https://gitlab.gnome.org/GNOME/mutter/-/merge_requests/2628/commits [Quality assurance - packaging] - debian/watch is present and works - debian/control defines a correct Maintainer field - Please link to a recent build log of the package https://launchpad.net/ubuntu/+source/libei/1.0.0-0ubuntu2 - Please attach the full output you have got from `lintian --pedantic` as an extra post to this bug. - Lintian overrides are not present - This package does not rely on obsolete or about to be demoted packages. - This package has no python2 or GTK2 dependencies - The package will be installed by default, but does not ask debconf questions higher than medium - Packaging and build is easy, link to debian/rules https://salsa.debian.org/jbicha/libei/-/blob/debian-unstable/debian/rules [UI standards] - Application is not end-user facing (does not need translation) [Dependencies] - No further depends or recommends dependencies that are not yet in main [Standards compliance] - This package correctly follows FHS and Debian Policy [Maintenance/Owner] - Owning Team will be Desktop Packages - Team is not yet, but will subscribe to the package before promotion - This does not use static builds - The team Desktop Packages is aware of the implications of vendored code and (as alerted by the security team) commits to provide updates and backports to the security team for any affected vendored code for the lifetime of the release (including ESM). Currently, the libei packaging includes a vendored copy of munit since munit is not packaged for Debian or Ubuntu yet. This is an optional build-time dependency only used by the test suite and does not add any run-time dependencies.
[Desktop-packages] [Bug 2034472] Re: Not supported by GNOME 45
packages installed ** Attachment added: "packages.txt" https://bugs.launchpad.net/ubuntu/+source/gnome-shell-extension-ubuntu-dock/+bug/2034472/+attachment/5698029/+files/packages.txt -- 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/2034472 Title: Not supported by GNOME 45 Status in gnome-shell-extension-ubuntu-dock package in Ubuntu: Incomplete Bug description: Extension Manager - Upgrade Assistant Report Currently on: GNOME 45.beta.1 Upgrading to: GNOME 45 On upgrading to GNOME 45, 1 out of 5 currently installed extensions will be compatible (20%). User-Installed Extensions: 'Battery Indicator Icon' by Deminder Extension ID: battery-indicator-icon@Deminder Supported: No System Extensions: 'Ubuntu Dock' by didrocks Extension ID: ubuntu-d...@ubuntu.com Supported: No 'Ubuntu Tiling Assistant' by (null) Extension ID: tiling-assist...@ubuntu.com Supported: Unknown 'Desktop Icons NG (DING)' by rastersoft Extension ID: d...@rastersoft.com Supported: Yes 'Ubuntu AppIndicators' by didrocks Extension ID: ubuntu-appindicat...@ubuntu.com Supported: No To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell-extension-ubuntu-dock/+bug/2034472/+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 2034472] Re: Not supported by GNOME 45
please find the attached files as requested ** Attachment added: "journal.txt" https://bugs.launchpad.net/ubuntu/+source/gnome-shell-extension-ubuntu-dock/+bug/2034472/+attachment/5698028/+files/journal.txt -- 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/2034472 Title: Not supported by GNOME 45 Status in gnome-shell-extension-ubuntu-dock package in Ubuntu: Incomplete Bug description: Extension Manager - Upgrade Assistant Report Currently on: GNOME 45.beta.1 Upgrading to: GNOME 45 On upgrading to GNOME 45, 1 out of 5 currently installed extensions will be compatible (20%). User-Installed Extensions: 'Battery Indicator Icon' by Deminder Extension ID: battery-indicator-icon@Deminder Supported: No System Extensions: 'Ubuntu Dock' by didrocks Extension ID: ubuntu-d...@ubuntu.com Supported: No 'Ubuntu Tiling Assistant' by (null) Extension ID: tiling-assist...@ubuntu.com Supported: Unknown 'Desktop Icons NG (DING)' by rastersoft Extension ID: d...@rastersoft.com Supported: Yes 'Ubuntu AppIndicators' by didrocks Extension ID: ubuntu-appindicat...@ubuntu.com Supported: No To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell-extension-ubuntu-dock/+bug/2034472/+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 2033967] Re: Laptop screen blinked, no tty works and 200 dmesg errors per second
** Changed in: mesa Status: Unknown => 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/2033967 Title: Laptop screen blinked, no tty works and 200 dmesg errors per second Status in Mesa: Fix Released Status in linux-hwe-6.2 package in Ubuntu: Invalid Status in mesa package in Ubuntu: New Bug description: I was using my laptop and suddenly the screen blinked. After that, all I could do was to move the mouse, no interaction worked. Trying to change to a TTY would open the black screen but the text cursor wasn't blinking and nothing happened. I accessed the laptop via SSH and used: screen env DISPLAY=:0 xfwm4 --vblank=xpresent --replace To reload xfwm4. After that, the graphical interface started working again. However, no TTY is accessible and there are 200 dmesg errors per second. These are the errors that repeat endlessly: [43959.444682] amdgpu :06:00.0: amdgpu: couldn't schedule ib on ring [43959.444688] [drm:amdgpu_job_run [amdgpu]] *ERROR* Error scheduling IBs (-22) And while I was writing this report, another problem happened: [44566.016330] [drm:amdgpu_job_timedout [amdgpu]] *ERROR* ring vcn_enc0 timeout, signaled seq=2, emitted seq=6 [44566.016553] [drm:amdgpu_job_timedout [amdgpu]] *ERROR* Process information: process obs pid 38687 thread obs:cs0 pid 38694 [44566.016748] amdgpu :06:00.0: amdgpu: GPU reset begin! [44566.317039] [drm] Register(0) [mmUVD_POWER_STATUS] failed to reach value 0x0001 != 0x0002 [44566.525640] [drm] Register(0) [mmUVD_RB_RPTR] failed to reach value 0x0100 != 0x [44566.728577] [drm] Register(0) [mmUVD_POWER_STATUS] failed to reach value 0x0001 != 0x0002 [44566.731204] [ cut here ] [44566.731205] WARNING: CPU: 15 PID: 29333 at drivers/gpu/drm/amd/amdgpu/amdgpu_irq.c:600 amdgpu_irq_put+0xa4/0xc0 [amdgpu] [44566.731429] Modules linked in: tls wireguard curve25519_x86_64 libchacha20poly1305 chacha_x86_64 poly1305_x86_64 libcurve25519_generic libchacha ip6_udp_tunnel udp_tunnel nvme_fabrics veth bridge stp llc zfs(PO) zunicode(PO) zzstd(O) zlua(O) zavl(PO) icp(PO) zcommon(PO) znvpair(PO) spl(O) rfcomm snd_seq_dummy snd_hrtimer vhost_vsock vmw_vsock_virtio_transport_common vhost vhost_iotlb vsock cmac algif_hash algif_skcipher af_alg bnep zram binfmt_misc nls_iso8859_1 nft_masq snd_sof_amd_rembrandt snd_sof_amd_renoir snd_hda_codec_realtek snd_sof_amd_acp snd_hda_codec_generic snd_sof_pci ledtrig_audio snd_sof_xtensa_dsp snd_hda_codec_hdmi snd_sof snd_hda_intel snd_sof_utils snd_intel_dspcfg snd_soc_core snd_intel_sdw_acpi snd_compress nft_limit snd_hda_codec intel_rapl_msr ac97_bus intel_rapl_common snd_hda_core snd_pcm_dmaengine snd_hwdep edac_mce_amd snd_pci_ps btusb snd_seq_midi btrtl snd_rpl_pci_acp6x kvm_amd snd_seq_midi_event btbcm snd_acp_pci btintel btmtk snd_rawmidi uvcvideo [44566.731465] snd_pci_acp6x nf_log_syslog rtw89_8852ae kvm videobuf2_vmalloc bluetooth snd_pcm videobuf2_memops snd_seq rtw89_8852a irqbypass snd_pci_acp5x videobuf2_v4l2 ecdh_generic snd_seq_device snd_rn_pci_acp3x joydev nft_log input_leds rapl videobuf2_common serio_raw snd_timer wmi_bmof hid_multitouch ecc snd_acp_config rtw89_pci snd_soc_acpi snd k10temp rtw89_core snd_pci_acp3x soundcore ideapad_laptop ccp sparse_keymap platform_profile mac_hid nft_ct nvidia_uvm(PO) nft_chain_nat nf_nat sch_fq_codel nf_conntrack nf_defrag_ipv6 nf_defrag_ipv4 cuse msr parport_pc nf_tables ppdev lp nfnetlink parport ramoops pstore_blk reed_solomon pstore_zone efi_pstore autofs4 btrfs blake2b_generic dm_crypt raid10 raid456 async_raid6_recov async_memcpy async_pq async_xor async_tx xor raid6_pq libcrc32c raid1 raid0 multipath linear overlay v4l2loopback(O) videodev mc virt_wifi virtio_net net_failover failover virtio_gpu virtio_dma_buf drm_shmem_helper z3fold rndis_host cdc_ether usbnet bfq at h10k_pci [44566.731504] ath10k_core ath mac80211 libarc4 cfg80211 usb_storage nbd mii nvidia_drm(PO) nvidia_modeset(PO) usbhid nvidia(PO) amdgpu iommu_v2 drm_buddy gpu_sched i2c_algo_bit drm_ttm_helper ttm drm_display_helper cec rc_core drm_kms_helper crct10dif_pclmul syscopyarea crc32_pclmul polyval_clmulni sysfillrect polyval_generic hid_generic nvme sysimgblt ghash_clmulni_intel drm sha512_ssse3 aesni_intel i2c_hid_acpi crypto_simd xhci_pci nvme_core cryptd r8169 video i2c_piix4 i2c_hid xhci_pci_renesas nvme_common realtek wmi hid [44566.731529] CPU: 15 PID: 29333 Comm: kworker/u32:1 Tainted: PW O 6.2.0-31-generic #31~22.04.1-Ubuntu [44566.731531] Hardware name: LENOVO 82MJ/LNVNB161216, BIOS H3CN36WW(V2.06) 09/30/2022 [44566.731533] Workqueue: amdgpu-reset-dev drm_sched_job_timedout [gpu_sched] [44566.731539] RIP: 0010:amdgpu_irq_put+0xa4/0xc0 [amdgpu] [44566.731702] Code: 31 f6 31 ff c3 cc cc cc cc 44 89
[Desktop-packages] [Bug 2031433] Re: webkit2gtk 2.41.90 fails to build on riscv64
** Changed in: webkit2gtk (Ubuntu)
Status: Triaged => Fix Committed
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to webkit2gtk in Ubuntu.
https://bugs.launchpad.net/bugs/2031433
Title:
webkit2gtk 2.41.90 fails to build on riscv64
Status in Webkit:
Confirmed
Status in webkit2gtk package in Ubuntu:
Fix Committed
Bug description:
- webkitgtk 2.41.90
- Ubuntu 23.10
-
https://salsa.debian.org/webkit-team/webkit/-/blob/wk2/experimental/debian/rules
-
https://salsa.debian.org/webkit-team/webkit/-/blob/wk2/experimental/debian/control
webkitgtk 2.41.90 fails to build on riscv64 but seems to build ok on
our other architectures.
Full build log
---
https://launchpad.net/ubuntu/+source/webkit2gtk/2.41.90-1ubuntu1
Build log excerpt
--
In file included from
JavaScriptCore/DerivedSources/unified-sources/UnifiedSource-15db4ad9-1.cpp:1:
/<>/Source/JavaScriptCore/wasm/WasmB3IRGenerator.cpp: In member
function
‘JSC::Wasm::B3IRGenerator::PartialResult
JSC::Wasm::B3IRGenerator::addI32Popcnt(ExpressionType, JSC::B3::Variable*&)’:
/<>/Source/JavaScriptCore/wasm/WasmB3IRGenerator.cpp:5214:25:
error: ‘supportsCountPopulation’ is not a member of ‘JSC::MacroAssembler’
5214 | if (MacroAssembler::supportsCountPopulation()) {
| ^~~
/<>/Source/JavaScriptCore/wasm/WasmB3IRGenerator.cpp: In lambda
function:
/<>/Source/JavaScriptCore/wasm/WasmB3IRGenerator.cpp:5224:17:
error: ‘class JSC::CCallHelpers’ has no member named ‘countPopulation32’
5224 | jit.countPopulation32(params[1].gpr(), params[0].gpr(),
params.fpScratch(0));
| ^
/<>/Source/JavaScriptCore/wasm/WasmB3IRGenerator.cpp: In member
function
‘JSC::Wasm::B3IRGenerator::PartialResult
JSC::Wasm::B3IRGenerator::addI64Popcnt(ExpressionType, JSC::B3::Variable*&)’:
/<>/Source/JavaScriptCore/wasm/WasmB3IRGenerator.cpp:5241:25:
error: ‘supportsCountPopulation’ is not a member of ‘JSC::MacroAssembler’
5241 | if (MacroAssembler::supportsCountPopulation()) {
| ^~~
/<>/Source/JavaScriptCore/wasm/WasmB3IRGenerator.cpp: In lambda
function:
/<>/Source/JavaScriptCore/wasm/WasmB3IRGenerator.cpp:5251:17:
error: ‘class JSC::CCallHelpers’ has no member named ‘countPopulation64’
5251 | jit.countPopulation64(params[1].gpr(), params[0].gpr(),
params.fpScratch(0));
| ^
To manage notifications about this bug go to:
https://bugs.launchpad.net/webkit/+bug/2031433/+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 2033967] Re: Laptop screen blinked, no tty works and 200 dmesg errors per second
I believe this likely needs the VCN fixes from https://gitlab.freedesktop.org/mesa/mesa/-/issues/9728 backported. ** Bug watch added: gitlab.freedesktop.org/mesa/mesa/-/issues #9728 https://gitlab.freedesktop.org/mesa/mesa/-/issues/9728 ** Also affects: mesa (Ubuntu) Importance: Undecided Status: New ** Changed in: linux-hwe-6.2 (Ubuntu) Status: New => Invalid ** Also affects: mesa via https://gitlab.freedesktop.org/mesa/mesa/-/issues/9728 Importance: Unknown Status: Unknown -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to mesa in Ubuntu. https://bugs.launchpad.net/bugs/2033967 Title: Laptop screen blinked, no tty works and 200 dmesg errors per second Status in Mesa: Unknown Status in linux-hwe-6.2 package in Ubuntu: Invalid Status in mesa package in Ubuntu: New Bug description: I was using my laptop and suddenly the screen blinked. After that, all I could do was to move the mouse, no interaction worked. Trying to change to a TTY would open the black screen but the text cursor wasn't blinking and nothing happened. I accessed the laptop via SSH and used: screen env DISPLAY=:0 xfwm4 --vblank=xpresent --replace To reload xfwm4. After that, the graphical interface started working again. However, no TTY is accessible and there are 200 dmesg errors per second. These are the errors that repeat endlessly: [43959.444682] amdgpu :06:00.0: amdgpu: couldn't schedule ib on ring [43959.444688] [drm:amdgpu_job_run [amdgpu]] *ERROR* Error scheduling IBs (-22) And while I was writing this report, another problem happened: [44566.016330] [drm:amdgpu_job_timedout [amdgpu]] *ERROR* ring vcn_enc0 timeout, signaled seq=2, emitted seq=6 [44566.016553] [drm:amdgpu_job_timedout [amdgpu]] *ERROR* Process information: process obs pid 38687 thread obs:cs0 pid 38694 [44566.016748] amdgpu :06:00.0: amdgpu: GPU reset begin! [44566.317039] [drm] Register(0) [mmUVD_POWER_STATUS] failed to reach value 0x0001 != 0x0002 [44566.525640] [drm] Register(0) [mmUVD_RB_RPTR] failed to reach value 0x0100 != 0x [44566.728577] [drm] Register(0) [mmUVD_POWER_STATUS] failed to reach value 0x0001 != 0x0002 [44566.731204] [ cut here ] [44566.731205] WARNING: CPU: 15 PID: 29333 at drivers/gpu/drm/amd/amdgpu/amdgpu_irq.c:600 amdgpu_irq_put+0xa4/0xc0 [amdgpu] [44566.731429] Modules linked in: tls wireguard curve25519_x86_64 libchacha20poly1305 chacha_x86_64 poly1305_x86_64 libcurve25519_generic libchacha ip6_udp_tunnel udp_tunnel nvme_fabrics veth bridge stp llc zfs(PO) zunicode(PO) zzstd(O) zlua(O) zavl(PO) icp(PO) zcommon(PO) znvpair(PO) spl(O) rfcomm snd_seq_dummy snd_hrtimer vhost_vsock vmw_vsock_virtio_transport_common vhost vhost_iotlb vsock cmac algif_hash algif_skcipher af_alg bnep zram binfmt_misc nls_iso8859_1 nft_masq snd_sof_amd_rembrandt snd_sof_amd_renoir snd_hda_codec_realtek snd_sof_amd_acp snd_hda_codec_generic snd_sof_pci ledtrig_audio snd_sof_xtensa_dsp snd_hda_codec_hdmi snd_sof snd_hda_intel snd_sof_utils snd_intel_dspcfg snd_soc_core snd_intel_sdw_acpi snd_compress nft_limit snd_hda_codec intel_rapl_msr ac97_bus intel_rapl_common snd_hda_core snd_pcm_dmaengine snd_hwdep edac_mce_amd snd_pci_ps btusb snd_seq_midi btrtl snd_rpl_pci_acp6x kvm_amd snd_seq_midi_event btbcm snd_acp_pci btintel btmtk snd_rawmidi uvcvideo [44566.731465] snd_pci_acp6x nf_log_syslog rtw89_8852ae kvm videobuf2_vmalloc bluetooth snd_pcm videobuf2_memops snd_seq rtw89_8852a irqbypass snd_pci_acp5x videobuf2_v4l2 ecdh_generic snd_seq_device snd_rn_pci_acp3x joydev nft_log input_leds rapl videobuf2_common serio_raw snd_timer wmi_bmof hid_multitouch ecc snd_acp_config rtw89_pci snd_soc_acpi snd k10temp rtw89_core snd_pci_acp3x soundcore ideapad_laptop ccp sparse_keymap platform_profile mac_hid nft_ct nvidia_uvm(PO) nft_chain_nat nf_nat sch_fq_codel nf_conntrack nf_defrag_ipv6 nf_defrag_ipv4 cuse msr parport_pc nf_tables ppdev lp nfnetlink parport ramoops pstore_blk reed_solomon pstore_zone efi_pstore autofs4 btrfs blake2b_generic dm_crypt raid10 raid456 async_raid6_recov async_memcpy async_pq async_xor async_tx xor raid6_pq libcrc32c raid1 raid0 multipath linear overlay v4l2loopback(O) videodev mc virt_wifi virtio_net net_failover failover virtio_gpu virtio_dma_buf drm_shmem_helper z3fold rndis_host cdc_ether usbnet bfq at h10k_pci [44566.731504] ath10k_core ath mac80211 libarc4 cfg80211 usb_storage nbd mii nvidia_drm(PO) nvidia_modeset(PO) usbhid nvidia(PO) amdgpu iommu_v2 drm_buddy gpu_sched i2c_algo_bit drm_ttm_helper ttm drm_display_helper cec rc_core drm_kms_helper crct10dif_pclmul syscopyarea crc32_pclmul polyval_clmulni sysfillrect polyval_generic hid_generic nvme sysimgblt ghash_clmulni_intel drm sha512_ssse3 aesni_intel i2c_hid_acpi crypto_simd xhci_pci nvme_core cryptd r8169 video i2c_piix4 i2c_hid
[Desktop-packages] [Bug 2034596] Re: nautilus-share depends on apturl in focal and jammy
** Description changed: nautilus-share and apturl in every other case are dependencies of metapackages. apturl is not a dependency of nautilus-share upstream. + libpam-smbpass is not a dependency. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to nautilus-share in Ubuntu. https://bugs.launchpad.net/bugs/2034596 Title: nautilus-share depends on apturl in focal and jammy Status in nautilus-share package in Ubuntu: New Bug description: nautilus-share and apturl in every other case are dependencies of metapackages. apturl is not a dependency of nautilus-share upstream. libpam-smbpass is not a dependency. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nautilus-share/+bug/2034596/+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 2034596] [NEW] nautilus-share depends on apturl in focal and jammy
Public bug reported: nautilus-share and apturl in every other case are dependencies of metapackages. apturl is not a dependency of nautilus-share upstream. ** Affects: nautilus-share (Ubuntu) Importance: Undecided Status: New ** Tags: bloat focal jammy packaging ubuntu-meta ** Description changed: nautilus-share and apturl in every other case are dependencies of - metapackages. + metapackages. apturl is not a dependency of nautilus-share upstream. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to nautilus-share in Ubuntu. https://bugs.launchpad.net/bugs/2034596 Title: nautilus-share depends on apturl in focal and jammy Status in nautilus-share package in Ubuntu: New Bug description: nautilus-share and apturl in every other case are dependencies of metapackages. apturl is not a dependency of nautilus-share upstream. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nautilus-share/+bug/2034596/+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 2034592] Re: Broken theming
Attached screenshot of libreoffice-writer exhibiting the problem ** Attachment added: "Screenshot from 2023-09-06 16-00-18.png" https://bugs.launchpad.net/ubuntu/+source/libreoffice/+bug/2034592/+attachment/5698013/+files/Screenshot%20from%202023-09-06%2016-00-18.png -- 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/2034592 Title: Broken theming Status in libreoffice package in Ubuntu: New Bug description: The libreoffice suite from the apt repositories exhibit broken theming with very antiquated UI elements. Unsure if it's related but the apps are running via XWayland. libreoffice-writer: Installed: 4:7.5.6~rc2-0ubuntu1 Candidate: 4:7.5.6~rc2-0ubuntu1 Version table: *** 4:7.5.6~rc2-0ubuntu1 500 500 http://gb.archive.ubuntu.com/ubuntu mantic/main amd64 Packages 100 /var/lib/dpkg/status ProblemType: Bug DistroRelease: Ubuntu 23.10 Package: libreoffice-writer 4:7.5.6~rc2-0ubuntu1 ProcVersionSignature: Ubuntu 6.3.0-7.7-generic 6.3.5 Uname: Linux 6.3.0-7-generic x86_64 ApportVersion: 2.27.0-0ubuntu2 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Wed Sep 6 15:49:44 2023 InstallationDate: Installed on 2022-03-31 (524 days ago) InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Beta amd64 (20220329.1) SourcePackage: libreoffice UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libreoffice/+bug/2034592/+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 2034592] [NEW] Broken theming
Public bug reported: The libreoffice suite from the apt repositories exhibit broken theming with very antiquated UI elements. Unsure if it's related but the apps are running via XWayland. libreoffice-writer: Installed: 4:7.5.6~rc2-0ubuntu1 Candidate: 4:7.5.6~rc2-0ubuntu1 Version table: *** 4:7.5.6~rc2-0ubuntu1 500 500 http://gb.archive.ubuntu.com/ubuntu mantic/main amd64 Packages 100 /var/lib/dpkg/status ProblemType: Bug DistroRelease: Ubuntu 23.10 Package: libreoffice-writer 4:7.5.6~rc2-0ubuntu1 ProcVersionSignature: Ubuntu 6.3.0-7.7-generic 6.3.5 Uname: Linux 6.3.0-7-generic x86_64 ApportVersion: 2.27.0-0ubuntu2 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Wed Sep 6 15:49:44 2023 InstallationDate: Installed on 2022-03-31 (524 days ago) InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Beta amd64 (20220329.1) SourcePackage: libreoffice UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: libreoffice (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug mantic wayland-session -- 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/2034592 Title: Broken theming Status in libreoffice package in Ubuntu: New Bug description: The libreoffice suite from the apt repositories exhibit broken theming with very antiquated UI elements. Unsure if it's related but the apps are running via XWayland. libreoffice-writer: Installed: 4:7.5.6~rc2-0ubuntu1 Candidate: 4:7.5.6~rc2-0ubuntu1 Version table: *** 4:7.5.6~rc2-0ubuntu1 500 500 http://gb.archive.ubuntu.com/ubuntu mantic/main amd64 Packages 100 /var/lib/dpkg/status ProblemType: Bug DistroRelease: Ubuntu 23.10 Package: libreoffice-writer 4:7.5.6~rc2-0ubuntu1 ProcVersionSignature: Ubuntu 6.3.0-7.7-generic 6.3.5 Uname: Linux 6.3.0-7-generic x86_64 ApportVersion: 2.27.0-0ubuntu2 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Wed Sep 6 15:49:44 2023 InstallationDate: Installed on 2022-03-31 (524 days ago) InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Beta amd64 (20220329.1) SourcePackage: libreoffice UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libreoffice/+bug/2034592/+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 2034263] Re: Does not detect hotplugged storage device 8TB SSD
** Summary changed: - Does not detect hotplugged storage device + Does not detect hotplugged storage device 8TB SSD -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gvfs in Ubuntu. https://bugs.launchpad.net/bugs/2034263 Title: Does not detect hotplugged storage device 8TB SSD Status in gvfs package in Ubuntu: New Bug description: This SSD Drive works well in Windows 11, but is not mounted in Ubuntu 22.04 neither Ubuntu 23.04. Windows 11 can read and write files in a 2GB partition, but Ubuntu shows it as unknown() and does not mount it. In Disks application, trying to format the partition with NTFS, there is an error message: Error wiping device: Failed to probe the device '/dev/sdd1' (udisks-error-quark, 0) Portable SSD: USB3.1 Type-C 8TB ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: gvfs 1.48.2-0ubuntu1 ProcVersionSignature: Ubuntu 6.2.0-31.31~22.04.1-generic 6.2.15 Uname: Linux 6.2.0-31-generic x86_64 ApportVersion: 2.20.11-0ubuntu82.5 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Tue Sep 5 12:49:03 2023 HotplugNewDevices: /dev/sdd1 /dev/sdd HotplugNewMounts: InstallationDate: Installed on 2022-11-25 (283 days ago) InstallationMedia: Ubuntu 22.04.1 LTS "Jammy Jellyfish" - Release amd64 (20220809.1) ProcEnviron: LANGUAGE=pt_BR:pt:en PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=pt_BR.UTF-8 SHELL=/bin/bash SourcePackage: gvfs Symptom: storage Title: Does not detect hotplugged storage device UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gvfs/+bug/2034263/+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 2034472] Re: Not supported by GNOME 45
I believe the gnome-shell-extension-manager app is reporting based on the extensions published on the extensions.gnome.org website. That website is irrelevant for Ubuntu users since we distribute these extensions directly in Ubuntu instead of through that website. -- 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/2034472 Title: Not supported by GNOME 45 Status in gnome-shell-extension-ubuntu-dock package in Ubuntu: Incomplete Bug description: Extension Manager - Upgrade Assistant Report Currently on: GNOME 45.beta.1 Upgrading to: GNOME 45 On upgrading to GNOME 45, 1 out of 5 currently installed extensions will be compatible (20%). User-Installed Extensions: 'Battery Indicator Icon' by Deminder Extension ID: battery-indicator-icon@Deminder Supported: No System Extensions: 'Ubuntu Dock' by didrocks Extension ID: ubuntu-d...@ubuntu.com Supported: No 'Ubuntu Tiling Assistant' by (null) Extension ID: tiling-assist...@ubuntu.com Supported: Unknown 'Desktop Icons NG (DING)' by rastersoft Extension ID: d...@rastersoft.com Supported: Yes 'Ubuntu AppIndicators' by didrocks Extension ID: ubuntu-appindicat...@ubuntu.com Supported: No To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell-extension-ubuntu-dock/+bug/2034472/+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 1956102] Re: Time for the US is shown in 24h format. It should be 12h with AM/PM
** Tags removed: kinetic ubuntu-22.04 ubuntu-desktop ** Tags added: mantic ubuntu-meta -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gsettings-desktop-schemas in Ubuntu. https://bugs.launchpad.net/bugs/1956102 Title: Time for the US is shown in 24h format. It should be 12h with AM/PM Status in GSettings Desktop Schemas: New Status in One Hundred Papercuts: New Status in gsettings-desktop-schemas package in Ubuntu: In Progress Status in subiquity package in Ubuntu: Won't Fix Status in gsettings-desktop-schemas package in Debian: New Bug description: Source- https://time.gov/ To manage notifications about this bug go to: https://bugs.launchpad.net/gsettings-desktop-schemas/+bug/1956102/+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 2034579] Re: [FFe] Use tecla to display keyboard layouts
** 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/2034579 Title: [FFe] Use tecla to display keyboard layouts Status in gnome-control-center package in Ubuntu: Incomplete Bug description: Explanation of FeatureFreeze exception === GNOME 45 includes a new keyboard layout viewer named Tecla to replace gkbd-keyboard-display (old and written in GTK3). The Main Inclusion Request for this was approved but I reverted the switch in the gnome-control-center, gnome-initial-setup, and gnome-shell packaging because the first release of Tecla crashed with some keyboard layouts. That issue has been fixed for the gnome-control-center integration. Specific changes Drop the Tecla patch from gnome-control-center and gnome-initial-setup Have gnome-control-center and gnome-initial-setup depend on Tecla Promote Tecla to main Later changes = In my testing with GNOME Shell 45 Beta, there are still some issues with the Tecla integration. I'll file those issues upstream and we'd like to be able to switch GNOME Shell to use Tecla later this cycle. We would… Drop the Tecla patch from gnome-shell Have gnome-shell depend on Tecla Demote libgnomekbd to Universe Testing Done I successfully completed Test Case 1 and the first 5 steps of Test Case 2 from https://wiki.ubuntu.com/DesktopTeam/TestPlans/gjs To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-control-center/+bug/2034579/+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 1956109] Re: printer-driver-ptouch is included with multiple metapackages for the minimal install
** Description changed: - A label printer driver is a recommended dependency of many desktop, - core, and minimal ubuntu and spin metapackages. It is also installed - with the minimal Ubuntu ISO option. Should this hardware be included - with the minimal install and should it be in multiple, overlapping - metapackages? If so, why? + A label printer driver is a recommended dependency in many metapackages. + It is also installed with the minimal Ubuntu ISO option. ** Tags removed: kinetic ubuntu-22.04 ** Tags added: mantic packaging ubuntu-meta -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to ubuntu-meta in Ubuntu. https://bugs.launchpad.net/bugs/1956109 Title: printer-driver-ptouch is included with multiple metapackages for the minimal install Status in ubuntu-mate-meta package in Ubuntu: New Status in ubuntu-meta package in Ubuntu: New Status in xubuntu-meta package in Ubuntu: New Bug description: A label printer driver is a recommended dependency in many metapackages. It is also installed with the minimal Ubuntu ISO option. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubuntu-mate-meta/+bug/1956109/+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 1956110] Re: upower requires libimobiledevice6 as a dependency
** Tags removed: kinetic ubuntu-22.04 ** Tags added: mantic -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to upower in Ubuntu. https://bugs.launchpad.net/bugs/1956110 Title: upower requires libimobiledevice6 as a dependency Status in libimobiledevice package in Ubuntu: New Status in upower package in Ubuntu: New Bug description: An iPhone library is required to have power management required by Gnome. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libimobiledevice/+bug/1956110/+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 2034579] [NEW] [FFe] Use tecla to display keyboard layouts
Public bug reported: Explanation of FeatureFreeze exception === GNOME 45 includes a new keyboard layout viewer named Tecla to replace gkbd-keyboard-display (old and written in GTK3). The Main Inclusion Request for this was approved but I reverted the switch in the gnome-control-center, gnome-initial-setup, and gnome-shell packaging because the first release of Tecla crashed with some keyboard layouts. That issue has been fixed for the gnome-control-center integration. Specific changes Drop the Tecla patch from gnome-control-center and gnome-initial-setup Have gnome-control-center and gnome-initial-setup depend on Tecla Promote Tecla to main Later changes = In my testing with GNOME Shell 45 Beta, there are still some issues with the Tecla integration. I'll file those issues upstream and we'd like to be able to switch GNOME Shell to use Tecla later this cycle. We would… Drop the Tecla patch from gnome-shell Have gnome-shell depend on Tecla Demote libgnomekbd to Universe Testing Done I successfully completed Test Case 1 and the first 5 steps of Test Case 2 from https://wiki.ubuntu.com/DesktopTeam/TestPlans/gjs ** Affects: gnome-control-center (Ubuntu) Importance: Undecided Status: New ** Tags: mantic -- 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/2034579 Title: [FFe] Use tecla to display keyboard layouts Status in gnome-control-center package in Ubuntu: New Bug description: Explanation of FeatureFreeze exception === GNOME 45 includes a new keyboard layout viewer named Tecla to replace gkbd-keyboard-display (old and written in GTK3). The Main Inclusion Request for this was approved but I reverted the switch in the gnome-control-center, gnome-initial-setup, and gnome-shell packaging because the first release of Tecla crashed with some keyboard layouts. That issue has been fixed for the gnome-control-center integration. Specific changes Drop the Tecla patch from gnome-control-center and gnome-initial-setup Have gnome-control-center and gnome-initial-setup depend on Tecla Promote Tecla to main Later changes = In my testing with GNOME Shell 45 Beta, there are still some issues with the Tecla integration. I'll file those issues upstream and we'd like to be able to switch GNOME Shell to use Tecla later this cycle. We would… Drop the Tecla patch from gnome-shell Have gnome-shell depend on Tecla Demote libgnomekbd to Universe Testing Done I successfully completed Test Case 1 and the first 5 steps of Test Case 2 from https://wiki.ubuntu.com/DesktopTeam/TestPlans/gjs To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-control-center/+bug/2034579/+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 1956100] Re: tracker-extract requires libtotem-plparser18
** Tags removed: kinetic ubuntu-22.04 ubuntu-desktop ubuntu-desktop-minimal ** Tags added: mantic packaging ubuntu-meta -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to totem in Ubuntu. https://bugs.launchpad.net/bugs/1956100 Title: tracker-extract requires libtotem-plparser18 Status in totem package in Ubuntu: New Status in tracker-miners package in Ubuntu: New Bug description: Even when Totem is not installed from a minimal desktop installation, tracker-extract keeps libtotem-plparser18 and subsequently libtotem- parser-common as required dependencies. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/totem/+bug/1956100/+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 2033901] Re: gnome-shell regularly showing the "Oops! Something went wrong/ logout" screen after Alt-F2 r RET
** Also affects: mutter via https://gitlab.gnome.org/GNOME/mutter/-/issues/2852 Importance: Unknown Status: Unknown ** Package changed: gnome-shell (Ubuntu) => mutter (Ubuntu) ** Changed in: mutter (Ubuntu) Status: Incomplete => Fix Committed ** Tags added: fixed-in-mutter-45.rc fixed-upstream -- 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/2033901 Title: gnome-shell regularly showing the "Oops! Something went wrong/ logout" screen after Alt-F2 r RET Status in Mutter: Unknown Status in mutter package in Ubuntu: Fix Committed Bug description: With the most recent Mantic updates gnome-shell is regularly, but not every time, crashing and showing me the "Oops!" screen and forcing a logout when I type Alt-F2 r RET (using X11, obviously, since AFAIK that still isn't supported in Wayland). ProblemType: Bug DistroRelease: Ubuntu 23.10 Package: gnome-shell 45~beta.1-0ubuntu2 ProcVersionSignature: Ubuntu 6.3.0-7.7-generic 6.3.5 Uname: Linux 6.3.0-7-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.27.0-0ubuntu2 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: ubuntu:GNOME Date: Fri Sep 1 09:57:07 2023 DisplayManager: gdm3 InstallationDate: Installed on 2019-01-02 (1703 days ago) InstallationMedia: Ubuntu 18.10 "Cosmic Cuttlefish" - Release amd64 (20181017.3) RelatedPackageVersions: mutter-common 45~beta.1-1ubuntu1 SourcePackage: gnome-shell UpgradeStatus: Upgraded to mantic on 2023-05-20 (104 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/mutter/+bug/2033901/+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 2033643] Re: [SRU] libreoffice 7.5.6 for lunar
** Description changed: [Impact] * LibreOffice 7.5.6 is in its sixth bugfix release of the 7.5 line: https://wiki.documentfoundation.org/ReleasePlan/7.5#7.5.6_release - * Version 7.5.5 is currently released in lunar. For a list of fixed bugs compared to 7.5.5 see the list of bugs fixed in the release candidates of 7.5.6 (that's a total of ? bugs): + * Version 7.5.5 is currently released in lunar. For a list of fixed bugs compared to 7.5.5 see the list of bugs fixed in the release candidates of 7.5.6 (that's a total of 53 bugs): https://wiki.documentfoundation.org/Releases/7.5.6/RC1#List_of_fixed_bugs https://wiki.documentfoundation.org/Releases/7.5.6/RC2#List_of_fixed_bugs 7.5.6 RC2 is identical to the 7.5.6 release * Given the nature of the project, the complexity of the codebase and the high level of quality assurance upstream, it is preferable to SRU a minor release rather than cherry-pick selected bug fixes. [Testing] * Upstream testing. Bugs fixed upstream typically include unit/regression tests, and the release itself is extensively exercised (both in an automated manner and manually). * A recent set of upstream's automated jenkins testing can be found here: https://ci.libreoffice.org/job/gerrit_75/1671/ * More information about the upstream QA testing can be found here: * Automated tests https://wiki.documentfoundation.org/QA/Testing/Automated_Tests * Automated UI tests https://wiki.documentfoundation.org/Development/UITests * Regression tests https://wiki.documentfoundation.org/QA/Testing/Regression_Tests * Feature tests https://wiki.documentfoundation.org/QA/Testing/Feature_Tests * Launchpad testing. The libreoffice packages include autopkgtests that were run and verified as passing. Tested build can be found at https://launchpad.net/~libreoffice/+archive/ubuntu/libreoffice-prereleases/+sourcepub/15135055/+listing-archive-extra * [amd64] https://autopkgtest.ubuntu.com/results/autopkgtest-lunar-libreoffice-libreoffice-prereleases/lunar/amd64/libr/libreoffice/20230901_205756_d4783@/log.gz * [arm64] https://autopkgtest.ubuntu.com/results/autopkgtest-lunar-libreoffice-libreoffice-prereleases/lunar/arm64/libr/libreoffice/20230902_020105_e2774@/log.gz * [armhf] https://autopkgtest.ubuntu.com/results/autopkgtest-lunar-libreoffice-libreoffice-prereleases/lunar/armhf/libr/libreoffice/20230901_185845_d6d5b@/log.gz * [ppc64el] https://autopkgtest.ubuntu.com/results/autopkgtest-lunar-libreoffice-libreoffice-prereleases/lunar/ppc64el/libr/libreoffice/20230901_174418_b7c30@/log.gz * [riscv64] not available * [s390x] https://autopkgtest.ubuntu.com/results/autopkgtest-lunar-libreoffice-libreoffice-prereleases/lunar/s390x/libr/libreoffice/20230901_201014_90e5e@/log.gz * General smoke testing of all the applications in the office suite were carried out by going through the manual testplan as documented by: https://wiki.ubuntu.com/Process/Merges/TestPlans/libreoffice [Regression Potential] - * A minor release with a total of ? bug fixes always carries the + * A minor release with a total of 53 bug fixes always carries the potential for introducing regressions, even though it is a bugfix-only release, meaning that no new features were added, and no existing features were removed. * A combination of autopkgtests and careful smoke testing as described above should provide reasonable confidence that no regressions sneaked in.a -- 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/2033643 Title: [SRU] libreoffice 7.5.6 for lunar Status in libreoffice package in Ubuntu: Fix Released Status in libreoffice source package in Lunar: New Bug description: [Impact] * LibreOffice 7.5.6 is in its sixth bugfix release of the 7.5 line: https://wiki.documentfoundation.org/ReleasePlan/7.5#7.5.6_release * Version 7.5.5 is currently released in lunar. For a list of fixed bugs compared to 7.5.5 see the list of bugs fixed in the release candidates of 7.5.6 (that's a total of 53 bugs): https://wiki.documentfoundation.org/Releases/7.5.6/RC1#List_of_fixed_bugs https://wiki.documentfoundation.org/Releases/7.5.6/RC2#List_of_fixed_bugs 7.5.6 RC2 is identical to the 7.5.6 release * Given the nature of the project, the complexity of the codebase and the high level of quality assurance upstream, it is preferable to SRU a minor release rather than cherry-pick selected bug fixes. [Testing] * Upstream testing. Bugs fixed upstream typically include unit/regression tests, and the release itself is extensively exercised (both in an automated manner and manually). * A recent set of upstream's automated jenkins testing can be found here:
[Desktop-packages] [Bug 2034105] Re: Cursor didn't show up in X session when output from amd dgpu
Hello Kai-Chuan, or anyone else affected, Accepted xserver-xorg-video-amdgpu into jammy-proposed. The package will build now and be available at https://launchpad.net/ubuntu/+source/xserver-xorg-video- amdgpu/22.0.0-1ubuntu0.2 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. ** Tags added: verification-needed verification-needed-jammy -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to xserver-xorg-video-amdgpu in Ubuntu. https://bugs.launchpad.net/bugs/2034105 Title: Cursor didn't show up in X session when output from amd dgpu Status in OEM Priority Project: New Status in xserver-xorg-video-amdgpu package in Ubuntu: Fix Released Status in xserver-xorg-video-amdgpu source package in Jammy: Fix Committed Bug description: [ Impact ] * There is no cursor in Xorg session when output from AMD Navi3.x dgpu [ Test Plan ] * Test on the DT with AMD Navi3.x dgpu * Attach external monitor to AMD Navi3.x dgpu * Switch to Xorg session when login * Check if cursor is appeared and works properly [ Where problems could occur ] * The implementation checks DRM_CAP_CURSOR_WIDTH and DRM_CAP_CURSOR_HEIGHT and fallback to original implementation if kernel can't report the caps. * The user might see different cursor size after the patch applied, since the driver will ask kernel for it but not the hard coded one. [ Other Info ] * Upstream commit: https://cgit.freedesktop.org/xorg/driver/xf86-video-amdgpu/commit/?id=9c959fac3af28d191105f63236096ad456dca614 * The patch has been included in mantic and lunar already To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/2034105/+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 2034105] Re: Cursor didn't show up in X session when output from amd dgpu
Reuploaded -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to xserver-xorg-video-amdgpu in Ubuntu. https://bugs.launchpad.net/bugs/2034105 Title: Cursor didn't show up in X session when output from amd dgpu Status in OEM Priority Project: New Status in xserver-xorg-video-amdgpu package in Ubuntu: Fix Released Status in xserver-xorg-video-amdgpu source package in Jammy: Fix Committed Bug description: [ Impact ] * There is no cursor in Xorg session when output from AMD Navi3.x dgpu [ Test Plan ] * Test on the DT with AMD Navi3.x dgpu * Attach external monitor to AMD Navi3.x dgpu * Switch to Xorg session when login * Check if cursor is appeared and works properly [ Where problems could occur ] * The implementation checks DRM_CAP_CURSOR_WIDTH and DRM_CAP_CURSOR_HEIGHT and fallback to original implementation if kernel can't report the caps. * The user might see different cursor size after the patch applied, since the driver will ask kernel for it but not the hard coded one. [ Other Info ] * Upstream commit: https://cgit.freedesktop.org/xorg/driver/xf86-video-amdgpu/commit/?id=9c959fac3af28d191105f63236096ad456dca614 * The patch has been included in mantic and lunar already To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/2034105/+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 2034105] Re: Cursor didn't show up in X session when output from amd dgpu
Re-upload debdiff for jammy ** Attachment removed: "xserver-xorg-video-amdgpu_22.0.0-1ubuntu0.2.debdiff" https://bugs.launchpad.net/ubuntu/+source/xserver-xorg-video-amdgpu/+bug/2034105/+attachment/5697675/+files/xserver-xorg-video-amdgpu_22.0.0-1ubuntu0.2.debdiff ** Attachment added: "xserver-xorg-video-amdgpu_22.0.0-1ubuntu0.2.debdiff" https://bugs.launchpad.net/bugs/2034105/+attachment/5697871/+files/xserver-xorg-video-amdgpu_22.0.0-1ubuntu0.2.debdiff -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to xserver-xorg-video-amdgpu in Ubuntu. https://bugs.launchpad.net/bugs/2034105 Title: Cursor didn't show up in X session when output from amd dgpu Status in OEM Priority Project: New Status in xserver-xorg-video-amdgpu package in Ubuntu: Fix Released Status in xserver-xorg-video-amdgpu source package in Jammy: Fix Committed Bug description: [ Impact ] * There is no cursor in Xorg session when output from AMD Navi3.x dgpu [ Test Plan ] * Test on the DT with AMD Navi3.x dgpu * Attach external monitor to AMD Navi3.x dgpu * Switch to Xorg session when login * Check if cursor is appeared and works properly [ Where problems could occur ] * The implementation checks DRM_CAP_CURSOR_WIDTH and DRM_CAP_CURSOR_HEIGHT and fallback to original implementation if kernel can't report the caps. * The user might see different cursor size after the patch applied, since the driver will ask kernel for it but not the hard coded one. [ Other Info ] * Upstream commit: https://cgit.freedesktop.org/xorg/driver/xf86-video-amdgpu/commit/?id=9c959fac3af28d191105f63236096ad456dca614 * The patch has been included in mantic and lunar already To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/2034105/+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 1882466] Re: mythtv frontend crash when calling glClear in iris driver
Great, let's mark it as fixed, then. ** Changed in: mesa (Ubuntu) Status: Incomplete => 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/1882466 Title: mythtv frontend crash when calling glClear in iris driver Status in mesa package in Ubuntu: Fix Released Bug description: on startup, mythfrontend crashes repeatedly when calling glClear - the following traceback: Core was generated by `/usr/bin/mythfrontend.real'. Program terminated with signal SIGSEGV, Segmentation fault. #0 0x7f9495ca0838 in ?? () from /usr/lib/x86_64-linux-gnu/dri/iris_dri.so [Current thread is 1 (Thread 0x7f9551e59940 (LWP 4164))] (gdb) bt #0 0x7f9495ca0838 in ?? () from /usr/lib/x86_64-linux-gnu/dri/iris_dri.so #1 0x7f9495ca2ebf in ?? () from /usr/lib/x86_64-linux-gnu/dri/iris_dri.so #2 0x7f9495e65de4 in ?? () from /usr/lib/x86_64-linux-gnu/dri/iris_dri.so #3 0x7f9495c7ce5d in ?? () from /usr/lib/x86_64-linux-gnu/dri/iris_dri.so #4 0x7f9495c7da95 in ?? () from /usr/lib/x86_64-linux-gnu/dri/iris_dri.so #5 0x7f94952bc774 in ?? () from /usr/lib/x86_64-linux-gnu/dri/iris_dri.so #6 0x7f955f79e713 in QOpenGLFunctions::glClear (this=0x555cb36e8160, mask=16384) at /usr/include/x86_64-linux-gnu/qt5/QtGui/qopenglfunctions.h:628 #7 0x7f955f798090 in MythRenderOpenGL::ClearFramebuffer ( this=0x555cb36e8150) at opengl/mythrenderopengl.cpp:801 #8 0x7f955f78a3f2 in MythOpenGLPainter::Begin (this=0x555cb398dac0, Parent=0x555cb399d1d0) at opengl/mythpainteropengl.cpp:136 I can work around this problem with this: export MESA_LOADER_DRIVER_OVERRIDE=i965 (then running mythfrontend works fine) sorry for the lack of debug symbols in iris_dri.so if there is a .deb around with a debug version i can generate the traceback again not sure if the problem belongs to iris_dri.so or to mythfrontend but I put it here due to the workaround. $ lsb_release -rd Description: Ubuntu 20.04 LTS Release: 20.04 $ apt-cache policy libgl1-mesa-dri libgl1-mesa-dri: Installed: 20.0.4-2ubuntu1 Candidate: 20.0.4-2ubuntu1 Version table: *** 20.0.4-2ubuntu1 500 500 http://archive.ubuntu.com/ubuntu focal/main amd64 Packages 100 /var/lib/dpkg/status To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mesa/+bug/1882466/+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 2034105] Proposed package upload rejected
An upload of xserver-xorg-video-amdgpu to jammy-proposed has been rejected from the upload queue for the following reason: "This looks good, but you've included two slightly different versions of the patch? Please re-upload with just one :)". -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to xserver-xorg-video-amdgpu in Ubuntu. https://bugs.launchpad.net/bugs/2034105 Title: Cursor didn't show up in X session when output from amd dgpu Status in OEM Priority Project: New Status in xserver-xorg-video-amdgpu package in Ubuntu: Fix Released Status in xserver-xorg-video-amdgpu source package in Jammy: Fix Committed Bug description: [ Impact ] * There is no cursor in Xorg session when output from AMD Navi3.x dgpu [ Test Plan ] * Test on the DT with AMD Navi3.x dgpu * Attach external monitor to AMD Navi3.x dgpu * Switch to Xorg session when login * Check if cursor is appeared and works properly [ Where problems could occur ] * The implementation checks DRM_CAP_CURSOR_WIDTH and DRM_CAP_CURSOR_HEIGHT and fallback to original implementation if kernel can't report the caps. * The user might see different cursor size after the patch applied, since the driver will ask kernel for it but not the hard coded one. [ Other Info ] * Upstream commit: https://cgit.freedesktop.org/xorg/driver/xf86-video-amdgpu/commit/?id=9c959fac3af28d191105f63236096ad456dca614 * The patch has been included in mantic and lunar already To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/2034105/+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
