[Desktop-packages] [Bug 2019776] Re: If gnome-shell is started directly (instead of through gnome-session), it might deadlock with no output to the screen
This is handled via https://gitlab.gnome.org/GNOME/gnome-
shell/-/merge_requests/3293
** Changed in: gnome-shell (Ubuntu)
Importance: Undecided => Medium
** Changed in: gnome-shell (Ubuntu)
Assignee: (unassigned) => Marco Trevisan (Treviño) (3v1n0)
** Changed in: gnome-shell (Ubuntu)
Status: New => In Progress
--
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/2019776
Title:
If gnome-shell is started directly (instead of through gnome-session),
it might deadlock with no output to the screen
Status in GNOME Shell:
New
Status in OEM Priority Project:
New
Status in gnome-shell package in Ubuntu:
In Progress
Bug description:
If gnome-shell is launched directly instead of launched through gnome-
session, the process spawning `ibus-daemon` might cause deadlock and
unable to start the graphics.
Since `ibusManager.js` checks whether service
`org.freedesktop.IBus.session.GNOME.service` exists. In our case with
Ubuntu ubiquity, we've turned off `gnome-session.service` so that the
check failed and gnome-shell spawns `ibus-daemon` after the check.
I tried using gdb to gnome-shell and discovered it's hanging in a
child process spawning `ibus-daemon`, but is still in child_setup of
`Glib.spawn_async` function:
```
root@dell-desktop:/home/oem# cat /tmp/log
== Stack trace for context 0x5584da793180 ==
#0 5584dbd2d478 i resource:///org/gnome/shell/misc/ibusManager.js:119
(2776aa47bfb0 @ 12)
#1 5584dbd2d3a8 i resource:///org/gnome/shell/misc/ibusManager.js:114
(2776aa47bf60 @ 426)
#2 5584dbd2d308 i resource:///org/gnome/shell/misc/ibusManager.js:90
(2776aa47bec0 @ 162)
#3 5584dbd2d268 i self-hosted:689 (34e3dc212650 @ 15)
```
which is, in ibusManager.js:
```
const [success_, pid] = GLib.spawn_async(
null, cmdLine, env,
GLib.SpawnFlags.SEARCH_PATH |
GLib.SpawnFlags.DO_NOT_REAP_CHILD,
() => {
try {
global.context.restore_rlimit_nofile(); # <- here
} catch (err) {
}
}
);
```
Further code tracing found out that the deadlock is not during the
execution of the function (`restore_rlimit_nofile`) but the access to
the GObject (probably `global.context`).
Currently my propose to work around this issue is to add a 5 second
`setTimeout` to the caller of `_spawn` function in `ibusManager.js`.
I've lost debugging information but I can try reproducing the issue
and give the backtrace from gdb if needed.
To manage notifications about this bug go to:
https://bugs.launchpad.net/gnome-shell/+bug/2019776/+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 2059819] Re: Regression: Jammy to Noble, right clicking on some icons shows dropdown on left side of screen
** Description changed: + [ Impact ] + In ubuntu jammy and previous releases, right clicking on appindicator icons brings up the menu below the appindicator with appropriate gnome theming. In ubuntu noble, right clicking on some appindicator icons (example: barrier) results in the menu appearing on the left side of the screen without proper theming. See attached image. + + [ Test case ] + + Note: this only tests the appindicator-side that may have lead to + "activating" the application, it's not something that will fix the + applications issues that is a QT bug. + + 1. Start a QT application with indicator +(after gnome-shell has started; e.g. clementine, barrier...) + 2. The applindicator menu with shell theme should appear + 3. No activation happens on the application (e.g. the window is not opened) + + [ Regression potential ] + + Mouse events aren't properly exposed to the indicators ** Changed in: gnome-shell-extension-appindicator (Ubuntu) Status: New => Fix Committed ** Also affects: gnome-shell (Ubuntu Noble) Importance: Undecided Status: New ** Also affects: qtbase-opensource-src (Ubuntu Noble) Importance: Undecided Status: New ** Also affects: gnome-shell-extension-appindicator (Ubuntu Noble) Importance: Undecided Status: New -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-shell-extension-appindicator in Ubuntu. https://bugs.launchpad.net/bugs/2059819 Title: Regression: Jammy to Noble, right clicking on some icons shows dropdown on left side of screen Status in Ubuntu AppIndicators: Fix Released Status in gnome-shell package in Ubuntu: In Progress Status in gnome-shell-extension-appindicator package in Ubuntu: Fix Committed Status in qtbase-opensource-src package in Ubuntu: Confirmed Status in gnome-shell source package in Noble: New Status in gnome-shell-extension-appindicator source package in Noble: New Status in qtbase-opensource-src source package in Noble: New Bug description: [ Impact ] In ubuntu jammy and previous releases, right clicking on appindicator icons brings up the menu below the appindicator with appropriate gnome theming. In ubuntu noble, right clicking on some appindicator icons (example: barrier) results in the menu appearing on the left side of the screen without proper theming. See attached image. [ Test case ] Note: this only tests the appindicator-side that may have lead to "activating" the application, it's not something that will fix the applications issues that is a QT bug. 1. Start a QT application with indicator (after gnome-shell has started; e.g. clementine, barrier...) 2. The applindicator menu with shell theme should appear 3. No activation happens on the application (e.g. the window is not opened) [ Regression potential ] Mouse events aren't properly exposed to the indicators To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-shell-extension-appindicator/+bug/2059819/+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 2039543] Re: Miss placed Hexchat icon when switching workspaces
** Changed in: gnome-shell (Ubuntu) Status: In Progress => Fix Committed -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-shell-extension-appindicator in Ubuntu. https://bugs.launchpad.net/bugs/2039543 Title: Miss placed Hexchat icon when switching workspaces Status in Ubuntu AppIndicators: New Status in gnome-shell package in Ubuntu: Fix Committed Status in gnome-shell-extension-appindicator package in Ubuntu: Won't Fix Bug description: While switching workspaces, Hexchat icon in the app indicator appears bigger than the normal and in a wrong position then disappears. Please check the attached screen cast for details. ProblemType: Bug DistroRelease: Ubuntu 23.10 Package: gnome-shell-extension-appindicator 57-1 ProcVersionSignature: Ubuntu 6.5.0-9.9-generic 6.5.3 Uname: Linux 6.5.0-9-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.27.0-0ubuntu5 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Tue Oct 17 11:17:05 2023 InstallationDate: Installed on 2023-10-12 (5 days ago) InstallationMedia: Ubuntu 23.10 "Mantic Minotaur" - Release amd64 (20231011) PackageArchitecture: all SourcePackage: gnome-shell-extension-appindicator UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-shell-extension-appindicator/+bug/2039543/+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 2039543] Re: Miss placed Hexchat icon when switching workspaces
** Changed in: gnome-shell-extension-appindicator (Ubuntu) Status: Confirmed => Won't Fix ** Also affects: gnome-shell (Ubuntu) Importance: Undecided Status: New ** Changed in: gnome-shell (Ubuntu) Assignee: (unassigned) => Marco Trevisan (Treviño) (3v1n0) ** Changed in: gnome-shell (Ubuntu) Importance: Undecided => Medium ** Changed in: gnome-shell (Ubuntu) Status: New => In Progress -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-shell-extension-appindicator in Ubuntu. https://bugs.launchpad.net/bugs/2039543 Title: Miss placed Hexchat icon when switching workspaces Status in Ubuntu AppIndicators: New Status in gnome-shell package in Ubuntu: In Progress Status in gnome-shell-extension-appindicator package in Ubuntu: Won't Fix Bug description: While switching workspaces, Hexchat icon in the app indicator appears bigger than the normal and in a wrong position then disappears. Please check the attached screen cast for details. ProblemType: Bug DistroRelease: Ubuntu 23.10 Package: gnome-shell-extension-appindicator 57-1 ProcVersionSignature: Ubuntu 6.5.0-9.9-generic 6.5.3 Uname: Linux 6.5.0-9-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.27.0-0ubuntu5 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Tue Oct 17 11:17:05 2023 InstallationDate: Installed on 2023-10-12 (5 days ago) InstallationMedia: Ubuntu 23.10 "Mantic Minotaur" - Release amd64 (20231011) PackageArchitecture: all SourcePackage: gnome-shell-extension-appindicator UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-shell-extension-appindicator/+bug/2039543/+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 2059818] Re: Regression: Jammy to Noble, set_label no longer functions
** Description changed: + [ Impact ] + In ubuntu jammy and previous releases, set_label can be used to set the text to display instead of an appindicator icon. In ubuntu noble set_label no longer functions at all. https://gjs-docs.gnome.org/appindicator301~0.1/appindicator3.indicator#method-set_label + + [ Test Case ] + + - Download the test indicator and its dependencies: + * wget https://github.com/ubuntu/gnome-shell-extension-appindicator/blob/master/indicator-test-tool/testTool.js + * apt install gir1.2-appindicator3-0.1 + + - Run the test indicator: + gjs -m testTool.js + + - Ensure the indicator icon shows up (it has an ubuntu icon) + - Click on it and activate the "Set Label" item + - A random numeric label should show next to the icon + + [ Regression potential ] + + The icon is not visible anymore -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-shell-extension-appindicator in Ubuntu. https://bugs.launchpad.net/bugs/2059818 Title: Regression: Jammy to Noble, set_label no longer functions Status in gnome-shell-extension-appindicator package in Ubuntu: In Progress Bug description: [ Impact ] In ubuntu jammy and previous releases, set_label can be used to set the text to display instead of an appindicator icon. In ubuntu noble set_label no longer functions at all. https://gjs-docs.gnome.org/appindicator301~0.1/appindicator3.indicator#method-set_label [ Test Case ] - Download the test indicator and its dependencies: * wget https://github.com/ubuntu/gnome-shell-extension-appindicator/blob/master/indicator-test-tool/testTool.js * apt install gir1.2-appindicator3-0.1 - Run the test indicator: gjs -m testTool.js - Ensure the indicator icon shows up (it has an ubuntu icon) - Click on it and activate the "Set Label" item - A random numeric label should show next to the icon [ Regression potential ] The icon is not visible anymore To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell-extension-appindicator/+bug/2059818/+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 2042844] Re: JS ERROR: Gio.DBusError: GDBus.Error:org.freedesktop.DBus.Error.Failed: error occurred in AboutToShow
** Description changed: + [ Impact ] + With several indicator icons (Chrome, Slack, 1Password) a GDBus.Error systemd error message appears with each iteration of a left-click of any impacted indicator icon prior to the icon's menu appearing. Ubuntu Mantic 23.10, gnome-shell 45.0-1ubuntu2, gnome-shell-extension- appindicator 57-1 Also reported upstream here: https://github.com/ubuntu/gnome-shell- extension-appindicator/issues/445 Nov 06 08:32:20 ubuntu-mantic gnome-shell[3927]: JS ERROR: Gio.DBusError: GDBus.Error:org.freedesktop.DBus.Error.Failed: error occurred in AboutToShow - _promisify/proto[asyncFunc]/ Fix Committed ** Changed in: gnome-shell-extension-appindicator (Ubuntu) Importance: Undecided => Low ** Changed in: gnome-shell-extension-appindicator (Ubuntu) Assignee: (unassigned) => Marco Trevisan (Treviño) (3v1n0) ** Also affects: gnome-shell-extension-appindicator (Ubuntu Noble) Importance: Low Assignee: Marco Trevisan (Treviño) (3v1n0) Status: Fix Committed -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-shell-extension-appindicator in Ubuntu. https://bugs.launchpad.net/bugs/2042844 Title: JS ERROR: Gio.DBusError: GDBus.Error:org.freedesktop.DBus.Error.Failed: error occurred in AboutToShow Status in gnome-shell-extension-appindicator package in Ubuntu: Fix Committed Status in gnome-shell-extension-appindicator source package in Noble: Fix Committed Bug description: [ Impact ] With several indicator icons (Chrome, Slack, 1Password) a GDBus.Error systemd error message appears with each iteration of a left-click of any impacted indicator icon prior to the icon's menu appearing. Ubuntu Mantic 23.10, gnome-shell 45.0-1ubuntu2, gnome-shell-extension- appindicator 57-1 Also reported upstream here: https://github.com/ubuntu/gnome-shell- extension-appindicator/issues/445 Nov 06 08:32:20 ubuntu-mantic gnome-shell[3927]: JS ERROR: Gio.DBusError: GDBus.Error:org.freedesktop.DBus.Error.Failed: error occurred in AboutToShow _promisify/proto[asyncFunc]/https://bugs.launchpad.net/ubuntu/+source/gnome-shell-extension-appindicator/+bug/2042844/+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 2059818] Re: Regression: Jammy to Noble, set_label no longer functions
** Changed in: gnome-shell-extension-appindicator (Ubuntu) Status: New => In Progress ** Changed in: gnome-shell-extension-appindicator (Ubuntu) Importance: Undecided => High ** Changed in: gnome-shell-extension-appindicator (Ubuntu) Assignee: (unassigned) => Marco Trevisan (Treviño) (3v1n0) -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-shell-extension-appindicator in Ubuntu. https://bugs.launchpad.net/bugs/2059818 Title: Regression: Jammy to Noble, set_label no longer functions Status in gnome-shell-extension-appindicator package in Ubuntu: In Progress Bug description: [ Impact ] In ubuntu jammy and previous releases, set_label can be used to set the text to display instead of an appindicator icon. In ubuntu noble set_label no longer functions at all. https://gjs-docs.gnome.org/appindicator301~0.1/appindicator3.indicator#method-set_label [ Test Case ] - Download the test indicator and its dependencies: * wget https://github.com/ubuntu/gnome-shell-extension-appindicator/blob/master/indicator-test-tool/testTool.js * apt install gir1.2-appindicator3-0.1 - Run the test indicator: gjs -m testTool.js - Ensure the indicator icon shows up (it has an ubuntu icon) - Click on it and activate the "Set Label" item - A random numeric label should show next to the icon [ Regression potential ] The icon is not visible anymore To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell-extension-appindicator/+bug/2059818/+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 2060816] Re: App grid icon is Ubuntu logo, need to find override
Marcos, Are you sure that you're running the latest version of the yaru-icon- theme *and* of the ubuntu-dock? Also are you running the ubuntu session? If one of these conditions aren't met, then the normal icon will be shown. -- 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/2060816 Title: App grid icon is Ubuntu logo, need to find override Status in Yaru Theme: Fix Released Status in edubuntu-artwork package in Ubuntu: Fix Released Status in gnome-shell-extension-ubuntu-dock package in Ubuntu: Fix Released Status in yaru-theme package in Ubuntu: Fix Released Bug description: The app grid icon is now the Ubuntu logo. We need to find a way to override this to the Edubuntu logo. To manage notifications about this bug go to: https://bugs.launchpad.net/yaru/+bug/2060816/+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 1993054] Re: USB key eject does not eject
Handled as https://github.com/micheleg/dash-to-dock/pull/2200 ** Also affects: gnome-shell-extension-ubuntu-dock (Ubuntu Noble) Importance: Low Assignee: Marco Trevisan (Treviño) (3v1n0) Status: In Progress ** Also affects: gnome-shell-extension-ubuntu-dock (Ubuntu Jammy) Importance: Undecided Status: New -- 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/1993054 Title: USB key eject does not eject Status in gnome-shell-extension-ubuntu-dock package in Ubuntu: In Progress Status in gnome-shell-extension-ubuntu-dock source package in Jammy: New Status in gnome-shell-extension-ubuntu-dock source package in Noble: In Progress Bug description: I insert an USB key: icon appear in the dock and in the nautilus sidebar with title and a small arrow right click on icon in the dock and select 'Eject': the icon disappear in the dock but does NOT disappear from the nautilus sidebar click on the arrow near the icon in nautilus sidebar: the icon disappear and I see a message in notification area with: '... USB flash memory ... can be removed' problem happens when org.gnome.shell.extensions.dash-to-dock show-mounts-only-mounted is set to TRUE the problem does not occur if show-mounts-only-mounted is set to FALSE ProblemType: Bug DistroRelease: Ubuntu 22.10 Package: gnome-shell-extension-ubuntu-dock 74ubuntu2 ProcVersionSignature: Ubuntu 5.19.0-21.21-generic 5.19.7 Uname: Linux 5.19.0-21-generic x86_64 ApportVersion: 2.23.1-0ubuntu3 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Sun Oct 16 09:48:16 2022 InstallationDate: Installed on 2022-09-30 (15 days ago) InstallationMedia: Ubuntu 22.10 "Kinetic Kudu" - Beta amd64 (20220927.1) PackageArchitecture: all SourcePackage: gnome-shell-extension-ubuntu-dock UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell-extension-ubuntu-dock/+bug/1993054/+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 1993054] Re: USB key eject does not eject
Ok, found the reason finally and a way to reproduce... Thanks for the logging and to the https://github.com/xairy/raw- gadget/tree/master/dummy_hcd kernel module that allowed me to simulate more USB storage devices (together with g_mass_storage) for better fine- tuning of their specs :) ** Changed in: gnome-shell-extension-ubuntu-dock (Ubuntu) Status: Confirmed => In Progress -- 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/1993054 Title: USB key eject does not eject Status in gnome-shell-extension-ubuntu-dock package in Ubuntu: In Progress Bug description: I insert an USB key: icon appear in the dock and in the nautilus sidebar with title and a small arrow right click on icon in the dock and select 'Eject': the icon disappear in the dock but does NOT disappear from the nautilus sidebar click on the arrow near the icon in nautilus sidebar: the icon disappear and I see a message in notification area with: '... USB flash memory ... can be removed' problem happens when org.gnome.shell.extensions.dash-to-dock show-mounts-only-mounted is set to TRUE the problem does not occur if show-mounts-only-mounted is set to FALSE ProblemType: Bug DistroRelease: Ubuntu 22.10 Package: gnome-shell-extension-ubuntu-dock 74ubuntu2 ProcVersionSignature: Ubuntu 5.19.0-21.21-generic 5.19.7 Uname: Linux 5.19.0-21-generic x86_64 ApportVersion: 2.23.1-0ubuntu3 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Sun Oct 16 09:48:16 2022 InstallationDate: Installed on 2022-09-30 (15 days ago) InstallationMedia: Ubuntu 22.10 "Kinetic Kudu" - Beta amd64 (20220927.1) PackageArchitecture: all SourcePackage: gnome-shell-extension-ubuntu-dock UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell-extension-ubuntu-dock/+bug/1993054/+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 1993054] Re: USB key eject does not eject
Mh, the trace gives me some info, but the weird thing is that I can't figure out when those calls such as eject_with_operation are happening... Let me try again if I can reproduce, otherwise maybe when you've time (next week though), ping me at @3v1n0:matrix.org so that maybe we can do some more interactive debugging :) -- 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/1993054 Title: USB key eject does not eject Status in gnome-shell-extension-ubuntu-dock package in Ubuntu: Confirmed Bug description: I insert an USB key: icon appear in the dock and in the nautilus sidebar with title and a small arrow right click on icon in the dock and select 'Eject': the icon disappear in the dock but does NOT disappear from the nautilus sidebar click on the arrow near the icon in nautilus sidebar: the icon disappear and I see a message in notification area with: '... USB flash memory ... can be removed' problem happens when org.gnome.shell.extensions.dash-to-dock show-mounts-only-mounted is set to TRUE the problem does not occur if show-mounts-only-mounted is set to FALSE ProblemType: Bug DistroRelease: Ubuntu 22.10 Package: gnome-shell-extension-ubuntu-dock 74ubuntu2 ProcVersionSignature: Ubuntu 5.19.0-21.21-generic 5.19.7 Uname: Linux 5.19.0-21-generic x86_64 ApportVersion: 2.23.1-0ubuntu3 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Sun Oct 16 09:48:16 2022 InstallationDate: Installed on 2022-09-30 (15 days ago) InstallationMedia: Ubuntu 22.10 "Kinetic Kudu" - Beta amd64 (20220927.1) PackageArchitecture: all SourcePackage: gnome-shell-extension-ubuntu-dock UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell-extension-ubuntu-dock/+bug/1993054/+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 1993054] Re: USB key eject does not eject
It was ok but I was missing a change, try with this https://pastebin.ubuntu.com/p/G4KpfFrTBt/plain/ ? -- 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/1993054 Title: USB key eject does not eject Status in gnome-shell-extension-ubuntu-dock package in Ubuntu: Confirmed Bug description: I insert an USB key: icon appear in the dock and in the nautilus sidebar with title and a small arrow right click on icon in the dock and select 'Eject': the icon disappear in the dock but does NOT disappear from the nautilus sidebar click on the arrow near the icon in nautilus sidebar: the icon disappear and I see a message in notification area with: '... USB flash memory ... can be removed' problem happens when org.gnome.shell.extensions.dash-to-dock show-mounts-only-mounted is set to TRUE the problem does not occur if show-mounts-only-mounted is set to FALSE ProblemType: Bug DistroRelease: Ubuntu 22.10 Package: gnome-shell-extension-ubuntu-dock 74ubuntu2 ProcVersionSignature: Ubuntu 5.19.0-21.21-generic 5.19.7 Uname: Linux 5.19.0-21-generic x86_64 ApportVersion: 2.23.1-0ubuntu3 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Sun Oct 16 09:48:16 2022 InstallationDate: Installed on 2022-09-30 (15 days ago) InstallationMedia: Ubuntu 22.10 "Kinetic Kudu" - Beta amd64 (20220927.1) PackageArchitecture: all SourcePackage: gnome-shell-extension-ubuntu-dock UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell-extension-ubuntu-dock/+bug/1993054/+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 1993054] Re: USB key eject does not eject
No, no... Just copy the content of https://paste.ubuntu.com/p/kdbxSDVSps/plain/ as /usr/share/gnome-shell/extensions/ubuntu-d...@ubuntu.com/locations.js and restart the session. Then attach here the content of journalctl /usr/bin/gnome-shell After the issue has shown -- 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/1993054 Title: USB key eject does not eject Status in gnome-shell-extension-ubuntu-dock package in Ubuntu: Confirmed Bug description: I insert an USB key: icon appear in the dock and in the nautilus sidebar with title and a small arrow right click on icon in the dock and select 'Eject': the icon disappear in the dock but does NOT disappear from the nautilus sidebar click on the arrow near the icon in nautilus sidebar: the icon disappear and I see a message in notification area with: '... USB flash memory ... can be removed' problem happens when org.gnome.shell.extensions.dash-to-dock show-mounts-only-mounted is set to TRUE the problem does not occur if show-mounts-only-mounted is set to FALSE ProblemType: Bug DistroRelease: Ubuntu 22.10 Package: gnome-shell-extension-ubuntu-dock 74ubuntu2 ProcVersionSignature: Ubuntu 5.19.0-21.21-generic 5.19.7 Uname: Linux 5.19.0-21-generic x86_64 ApportVersion: 2.23.1-0ubuntu3 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Sun Oct 16 09:48:16 2022 InstallationDate: Installed on 2022-09-30 (15 days ago) InstallationMedia: Ubuntu 22.10 "Kinetic Kudu" - Beta amd64 (20220927.1) PackageArchitecture: all SourcePackage: gnome-shell-extension-ubuntu-dock UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell-extension-ubuntu-dock/+bug/1993054/+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 2062388] [NEW] Datemenu border radius is too big and not consistent with quicsettings
Public bug reported: As visible in https://i.imgur.com/sdzlLai.png ** Affects: yaru-theme (Ubuntu) Importance: Medium Assignee: Marco Trevisan (Treviño) (3v1n0) Status: In Progress -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to yaru-theme in Ubuntu. https://bugs.launchpad.net/bugs/2062388 Title: Datemenu border radius is too big and not consistent with quicsettings Status in yaru-theme package in Ubuntu: In Progress Bug description: As visible in https://i.imgur.com/sdzlLai.png To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/yaru-theme/+bug/2062388/+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 1993054] Re: USB key eject does not eject
Can you please check if doing something like this can provide some
useful logging bits to journalctl /usr/bin/gnome-shell ?
diff --git a/locations.js b/locations.js
index 9795f3fd..8b19959c 100644
--- a/locations.js
+++ b/locations.js
@@ -447,6 +447,8 @@ class MountableVolumeAppInfo extends LocationAppInfo {
});
this._signalsHandler = new Utils.GlobalSignalsHandler();
+print('Cancellable', this.cancellable, cancellable, 'cancelled',
this.cancellable?.is_cancelled());
+cancellable?.connect(c => logError(c, 'Cancellable cancelled'));
const updateAndMonitor = () => {
this._update();
@@ -629,12 +631,15 @@ class MountableVolumeAppInfo extends LocationAppInfo {
const operation = new
ShellMountOperation.ShellMountOperation(removable);
try {
if (action === 'mount') {
+print(action, 'Cancellable', this.cancellable, 'cancelled',
this.cancellable?.is_cancelled());
await this.volume.mount(Gio.MountMountFlags.NONE,
operation.mountOp,
this.cancellable);
} else if (action === 'unmount') {
+print(action, 'Cancellable', this.cancellable, 'cancelled',
this.cancellable?.is_cancelled());
await
this.mount.unmount_with_operation(Gio.MountUnmountFlags.FORCE,
operation.mountOp, this.cancellable);
} else if (action === 'eject') {
+print(action, 'Cancellable', this.cancellable, 'cancelled',
this.cancellable?.is_cancelled());
await
removable.eject_with_operation(Gio.MountUnmountFlags.FORCE,
operation.mountOp, this.cancellable);
} else {
--
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/1993054
Title:
USB key eject does not eject
Status in gnome-shell-extension-ubuntu-dock package in Ubuntu:
Confirmed
Bug description:
I insert an USB key:
icon appear in the dock and in the nautilus sidebar with title and a small
arrow
right click on icon in the dock and select 'Eject':
the icon disappear in the dock but does NOT disappear from the nautilus
sidebar
click on the arrow near the icon in nautilus sidebar:
the icon disappear and I see a message in notification area with: '... USB
flash memory ... can be removed'
problem happens when org.gnome.shell.extensions.dash-to-dock
show-mounts-only-mounted is set to TRUE
the problem does not occur if show-mounts-only-mounted is set to FALSE
ProblemType: Bug
DistroRelease: Ubuntu 22.10
Package: gnome-shell-extension-ubuntu-dock 74ubuntu2
ProcVersionSignature: Ubuntu 5.19.0-21.21-generic 5.19.7
Uname: Linux 5.19.0-21-generic x86_64
ApportVersion: 2.23.1-0ubuntu3
Architecture: amd64
CasperMD5CheckResult: pass
CurrentDesktop: ubuntu:GNOME
Date: Sun Oct 16 09:48:16 2022
InstallationDate: Installed on 2022-09-30 (15 days ago)
InstallationMedia: Ubuntu 22.10 "Kinetic Kudu" - Beta amd64 (20220927.1)
PackageArchitecture: all
SourcePackage: gnome-shell-extension-ubuntu-dock
UpgradeStatus: No upgrade log present (probably fresh install)
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-shell-extension-ubuntu-dock/+bug/1993054/+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 2061985] Re: Other users are also highlighted although unselected
** Changed in: gnome-shell (Ubuntu) Status: Confirmed => Opinion ** Changed in: yaru-theme (Ubuntu) Status: Confirmed => Opinion -- 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/2061985 Title: Other users are also highlighted although unselected Status in gnome-shell package in Ubuntu: Opinion Status in yaru-theme package in Ubuntu: Opinion Bug description: If there is more than one user available, both are highlighted in gray, although only one is highlighted with a orange border. Ubuntu 24.04, gdm 46.0-2ubuntu1. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/2061985/+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 2062178] Re: Disable location services in gnome-control-center
> Nightcolor uses geoclue which is disabled by default and I guess users will have to use the google option when the time comes ( not necessarily easy, but an option. ) We do not have location settings in systemsettings. Using google for example is an option but that requires admin access, while the g-c-c side controls whether applications have permit to access to geoclue -- 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/2062178 Title: Disable location services in gnome-control-center Status in gnome-control-center: New Status in gnome-control-center package in Ubuntu: In Progress Status in gnome-control-center package in Debian: Unknown Bug description: Impact -- Mozilla Location Services will be closed to all third parties (including Ubuntu, GNOME, KDE, etc.) on June 12, 2024. Unfortunately, there does not appear to be any suitable replacement for our typical desktop and laptop users. (Mobile devices like phones may have GPS that could be used but those devices would only rarely be using Ubuntu and gnome-control-center.) To avoid later UI changes and disruption only a few months from now, the Ubuntu Desktop team would prefer to disable location services before Ubuntu 24.04 LTS is released. Details --- Specifically, this hides - Privacy & Security > Location - Date & Time > Automatic Timezone - Displays > Night Light > Schedule > Sunrise to Sunset + This last one wasn't done yet, but I expect it for gnome-control-center 46.1 which will be an SRU https://gitlab.gnome.org/GNOME/gnome-control-center/-/issues/3014 Other Info -- https://gitlab.gnome.org/GNOME/gnome-control-center/-/issues/2959 gnome-control-center 46.1 to be released in a few days will also disable Location Services by default but with a build-time option for distros who have different deadlines and user profiles. If an alternative location provider is found that works well enough for our users, we intend to re-enable this feature with a Stable Release Update if possible. Because of this issue, Ubuntu has disabled the Location page in gnome- initial-setup for 24.04 LTS already. To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-control-center/+bug/2062178/+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 2060659] Re: X11 fractional scaling support is missing in 46.0
fossfreedom, probably magpie should use a different schema name though and *always* conflict with mutter, no? -- 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/2060659 Title: X11 fractional scaling support is missing in 46.0 Status in magpie package in Ubuntu: New Status in mutter package in Ubuntu: In Progress Bug description: X11 fractional scaling support is missing in mutter/gnome-shell 46.0 https://salsa.debian.org/gnome- team/mutter/-/commit/414010ddef06757000175c30238371739199d29a To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/magpie/+bug/2060659/+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 2061985] Re: Other users are also highlighted although unselected
Well that's the focus ring, IIRC Is there also without yaru so it doesn't seem a downstream (only) bug (if any to me): https://imgur.com/N6E5R1q.png -- 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/2061985 Title: Other users are also highlighted although unselected Status in gnome-shell package in Ubuntu: Confirmed Status in yaru-theme package in Ubuntu: Confirmed Bug description: If there is more than one user available, both are highlighted in gray, although only one is highlighted with a orange border. Ubuntu 24.04, gdm 46.0-2ubuntu1. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/2061985/+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 2062178] Re: Disable location services in gnome-control-center
> Unfortunately, there does not appear to be any suitable replacement for our typical desktop and laptop users. When mozilla service is not used, GeoIP is used instead. It's not perfect (especially if using a VPN) but it's good enough to provide features such as automatic-timezone and night light. -- 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/2062178 Title: Disable location services in gnome-control-center Status in gnome-control-center: New Status in gnome-control-center package in Ubuntu: In Progress Status in gnome-control-center package in Debian: Unknown Bug description: Impact -- Mozilla Location Services will be closed to all third parties (including Ubuntu, GNOME, KDE, etc.) on June 12, 2024. Unfortunately, there does not appear to be any suitable replacement for our typical desktop and laptop users. (Mobile devices like phones may have GPS that could be used but those devices would only rarely be using Ubuntu and gnome-control-center.) To avoid later UI changes and disruption only a few months from now, the Ubuntu Desktop team would prefer to disable location services before Ubuntu 24.04 LTS is released. Details --- Specifically, this hides - Privacy & Security > Location - Date & Time > Automatic Timezone - Displays > Night Light > Schedule > Sunrise to Sunset + This last one wasn't done yet, but I expect it for gnome-control-center 46.1 which will be an SRU https://gitlab.gnome.org/GNOME/gnome-control-center/-/issues/3014 Other Info -- https://gitlab.gnome.org/GNOME/gnome-control-center/-/issues/2959 gnome-control-center 46.1 to be released in a few days will also disable Location Services by default but with a build-time option for distros who have different deadlines and user profiles. If an alternative location provider is found that works well enough for our users, we intend to re-enable this feature with a Stable Release Update if possible. Because of this issue, Ubuntu has disabled the Location page in gnome- initial-setup for 24.04 LTS already. To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-control-center/+bug/2062178/+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 2060659] Re: X11 fractional scaling support is missing in 46.0
** Changed in: mutter (Ubuntu) Status: Confirmed => In Progress -- 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/2060659 Title: X11 fractional scaling support is missing in 46.0 Status in mutter package in Ubuntu: In Progress Bug description: X11 fractional scaling support is missing in mutter/gnome-shell 46.0 https://salsa.debian.org/gnome- team/mutter/-/commit/414010ddef06757000175c30238371739199d29a To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mutter/+bug/2060659/+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 2062078] [NEW] Mouse animations do not follow accent colors
Public bug reported: This is a regression from previous releases, the mouse animations do not follow the user-selected accent color The missing assets needs to be regenerated with this script: - https://gitlab.gnome.org/-/snippets/5549 Sources are: - https://gitlab.gnome.org/Teams/Design/settings-mockups/-/commits/master/mouse-and-touchpad/src/mouse-touchpad-v2.blend ** Affects: gnome-control-center (Ubuntu) Importance: Medium Assignee: Marco Trevisan (Treviño) (3v1n0) Status: In Progress -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-control-center in Ubuntu. https://bugs.launchpad.net/bugs/2062078 Title: Mouse animations do not follow accent colors Status in gnome-control-center package in Ubuntu: In Progress Bug description: This is a regression from previous releases, the mouse animations do not follow the user-selected accent color The missing assets needs to be regenerated with this script: - https://gitlab.gnome.org/-/snippets/5549 Sources are: - https://gitlab.gnome.org/Teams/Design/settings-mockups/-/commits/master/mouse-and-touchpad/src/mouse-touchpad-v2.blend To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-control-center/+bug/2062078/+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 2060816] Re: App grid icon is Ubuntu logo, need to find override
** Changed in: gnome-shell-extension-ubuntu-dock (Ubuntu) Status: In Progress => Fix Committed -- 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/2060816 Title: App grid icon is Ubuntu logo, need to find override Status in Yaru Theme: Fix Released Status in edubuntu-artwork package in Ubuntu: Fix Committed Status in gnome-shell-extension-ubuntu-dock package in Ubuntu: Fix Committed Status in yaru-theme package in Ubuntu: Fix Committed Bug description: The app grid icon is now the Ubuntu logo. We need to find a way to override this to the Edubuntu logo. To manage notifications about this bug go to: https://bugs.launchpad.net/yaru/+bug/2060816/+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 2061729] Re: Ubuntu Dock icon highlight is practically invisible when a white or grey window is behind it
** Changed in: yaru-theme (Ubuntu) Importance: Undecided => Low ** Changed in: yaru-theme (Ubuntu) Assignee: (unassigned) => Marco Trevisan (Treviño) (3v1n0) ** Changed in: yaru-theme (Ubuntu) Status: New => In Progress ** Changed in: gnome-shell-extension-ubuntu-dock (Ubuntu) Status: New => Won't Fix -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-shell-extension-ubuntu-dock in Ubuntu. https://bugs.launchpad.net/bugs/2061729 Title: Ubuntu Dock icon highlight is practically invisible when a white or grey window is behind it Status in gnome-shell-extension-ubuntu-dock package in Ubuntu: Won't Fix Status in yaru-theme package in Ubuntu: In Progress Bug description: Ubuntu Dock icon highlight is practically invisible when a white or grey window is behind it (like when autohide is enabled). To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell-extension-ubuntu-dock/+bug/2061729/+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 2062046] [NEW] Nautilus icons are not using yaru theme
Public bug reported: As reported upstream: https://github.com/ubuntu/yaru/issues/4055 The nautilus search icons are using adwaita theme, and they don't fit well with the whole system theme. ** Affects: yaru-theme (Ubuntu) Importance: Medium Assignee: Marco Trevisan (Treviño) (3v1n0) Status: Fix Committed -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to yaru-theme in Ubuntu. https://bugs.launchpad.net/bugs/2062046 Title: Nautilus icons are not using yaru theme Status in yaru-theme package in Ubuntu: Fix Committed Bug description: As reported upstream: https://github.com/ubuntu/yaru/issues/4055 The nautilus search icons are using adwaita theme, and they don't fit well with the whole system theme. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/yaru-theme/+bug/2062046/+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 2062044] [NEW] Dock icons for focused applications are not highlighted
Public bug reported: The icon for the application that is currently focused should be highlighted but this is not the case in noble. ** Affects: yaru-theme (Ubuntu) Importance: Medium Assignee: Marco Trevisan (Treviño) (3v1n0) Status: In Progress -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to yaru-theme in Ubuntu. https://bugs.launchpad.net/bugs/2062044 Title: Dock icons for focused applications are not highlighted Status in yaru-theme package in Ubuntu: In Progress Bug description: The icon for the application that is currently focused should be highlighted but this is not the case in noble. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/yaru-theme/+bug/2062044/+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 2058819] Re: gnome-shell-extension-ubuntu-dock -dock asymmetrical
** Changed in: yaru-theme (Ubuntu) Status: Fix Committed => Fix Released -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to yaru-theme in Ubuntu. https://bugs.launchpad.net/bugs/2058819 Title: gnome-shell-extension-ubuntu-dock -dock asymmetrical Status in yaru-theme package in Ubuntu: Fix Released Bug description: gnome-shell-extension-ubuntu-dock 89ubuntu3 installed from https://ppa.launchpadcontent.net/ubuntu-desktop/ppa/ubuntu noble/main amd64 Packages icons are not centered in the dock. See attachment. The Ubuntu icon at bottom is centered. Note: I don't know if it's appropriate to open a bug for a PPA program. ProblemType: Bug DistroRelease: Ubuntu 24.04 Package: gnome-shell-extension-ubuntu-dock 89ubuntu3 ProcVersionSignature: Ubuntu 6.8.0-11.11-generic 6.8.0-rc4 Uname: Linux 6.8.0-11-generic x86_64 ApportVersion: 2.28.0-0ubuntu1 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Sat Mar 23 19:31:51 2024 InstallationDate: Installed on 2024-03-10 (13 days ago) InstallationMedia: Ubuntu 24.04 LTS "Noble Numbat" - Daily amd64 (20240310) PackageArchitecture: all ProcEnviron: LANG=en_US.UTF-8 PATH=(custom, no user) SHELL=/bin/bash TERM=xterm-256color XDG_RUNTIME_DIR= RebootRequiredPkgs: Error: path contained symlinks. SourcePackage: gnome-shell-extension-ubuntu-dock UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/yaru-theme/+bug/2058819/+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 2060816] Re: App grid icon is Ubuntu logo, need to find override
FYI we're going to provide a way to override this by defining a new
gnome shell session (you can inherit the ubuntu one) and the icon should
be named `view-app-grid-${currentMode}-symbolic` e.g. `view-app-grid-
edubuntu-symbolic`, otherwise the default (view-app-grid-symbolic) will
be used
** Also affects: gnome-shell-extension-ubuntu-dock (Ubuntu)
Importance: Undecided
Status: New
** Changed in: gnome-shell-extension-ubuntu-dock (Ubuntu)
Assignee: (unassigned) => Marco Trevisan (Treviño) (3v1n0)
** Changed in: gnome-shell-extension-ubuntu-dock (Ubuntu)
Status: New => In Progress
** Changed in: yaru-theme (Ubuntu)
Status: Triaged => Fix Committed
--
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/2060816
Title:
App grid icon is Ubuntu logo, need to find override
Status in Yaru Theme:
Fix Released
Status in edubuntu-artwork package in Ubuntu:
Fix Committed
Status in gnome-shell-extension-ubuntu-dock package in Ubuntu:
In Progress
Status in yaru-theme package in Ubuntu:
Fix Committed
Bug description:
The app grid icon is now the Ubuntu logo. We need to find a way to
override this to the Edubuntu logo.
To manage notifications about this bug go to:
https://bugs.launchpad.net/yaru/+bug/2060816/+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 2060575] Re: gnome-keyring fails to automatically unlock login keyring after recent updates in noble
** Changed in: gnome-shell (Ubuntu) Status: In Progress => Fix Committed -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-keyring in Ubuntu. https://bugs.launchpad.net/bugs/2060575 Title: gnome-keyring fails to automatically unlock login keyring after recent updates in noble Status in gdm3 package in Ubuntu: Opinion Status in gnome-keyring package in Ubuntu: Won't Fix Status in gnome-shell package in Ubuntu: Fix Committed Bug description: After installing recent updates in 24.04, upon logging in the gnome- shell based UI pops up saying that the login keyring was not unlocked and asking for the users password to be input to unlock it. Similarly a second, non-gnome-shell based UI is also present asking the same thing. Will try and get a screenshot to attach. ProblemType: Bug DistroRelease: Ubuntu 24.04 Package: libpam-gnome-keyring 46.1-2build1 ProcVersionSignature: Ubuntu 6.8.0-22.22-generic 6.8.1 Uname: Linux 6.8.0-22-generic x86_64 NonfreeKernelModules: zfs ApportVersion: 2.28.0-0ubuntu1 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Tue Apr 9 06:16:46 2024 InstallationDate: Installed on 2021-08-03 (980 days ago) InstallationMedia: Ubuntu 21.10 "Impish Indri" - Alpha amd64 (20210802) RebootRequiredPkgs: Error: path contained symlinks. SourcePackage: gnome-keyring UpgradeStatus: Upgraded to noble on 2024-01-31 (68 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gdm3/+bug/2060575/+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 2061153] Re: No login prompt or user list on login screen [JS ERROR: TypeError: this._button is undefined]
** Changed in: gnome-shell (Ubuntu) Status: In Progress => Fix Committed -- 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/2061153 Title: No login prompt or user list on login screen [JS ERROR: TypeError: this._button is undefined] Status in gnome-shell package in Ubuntu: Fix Committed Bug description: I installed the 24.04 beta ISO (the version from 2024-04-12) on a HyperV VM. Running through the installer itself seemed fine, but after rebooting GDM seemed to start but doesn't offer any users to login with. Not even an "Other" button. GDM itself has definitely started, as the current time is visible at the top of the screen, and the network and accessibility icons are visible at the top right of the screen. But the center of the screen is blank. If I manually mount the drive and examine the journal logs, I see a "JS Error" from gnome-shell that seems likely to be related: Apr 12 14:47:29 jwilcox-u24b gnome-shell[1735]: Starting Authd!!! Apr 12 14:47:29 jwilcox-u24b gnome-shell[1735]: JS ERROR: TypeError: this._button is undefined _createSessionMenuButton@resource:///org/gnome/shell/gdm/loginDialog.js:663:13 _init@resource:///org/gnome/shell/gdm/loginDialog.js:589:14 LoginDialog@resource:///org/gnome/shell/gdm/loginDialog.js:487:4 _ensureUnlockDialog@resource:///org/gnome/shell/ui/screenShield.js:472:28 showDialog@resource:///org/gnome/shell/ui/screenShield.js:404:14 _initializeUI/<@resource:///org/gnome/shell/ui/main.js:317:26 _prepareStartupAnimation@resource:///org/gnome/shell/ui/layout.js:764:18 _loadBackground/signalIdhttps://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/2061153/+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 2060575] Re: gnome-keyring fails to automatically unlock login keyring after recent updates in noble
** Also affects: gnome-shell (Ubuntu) Importance: Undecided Status: New ** Changed in: gnome-shell (Ubuntu) Status: New => In Progress ** Changed in: gnome-shell (Ubuntu) Importance: Undecided => High ** Changed in: gnome-shell (Ubuntu) Assignee: (unassigned) => Marco Trevisan (Treviño) (3v1n0) ** Changed in: gdm3 (Ubuntu) Status: Confirmed => Opinion -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-keyring in Ubuntu. https://bugs.launchpad.net/bugs/2060575 Title: gnome-keyring fails to automatically unlock login keyring after recent updates in noble Status in gdm3 package in Ubuntu: Opinion Status in gnome-keyring package in Ubuntu: Won't Fix Status in gnome-shell package in Ubuntu: In Progress Bug description: After installing recent updates in 24.04, upon logging in the gnome- shell based UI pops up saying that the login keyring was not unlocked and asking for the users password to be input to unlock it. Similarly a second, non-gnome-shell based UI is also present asking the same thing. Will try and get a screenshot to attach. ProblemType: Bug DistroRelease: Ubuntu 24.04 Package: libpam-gnome-keyring 46.1-2build1 ProcVersionSignature: Ubuntu 6.8.0-22.22-generic 6.8.1 Uname: Linux 6.8.0-22-generic x86_64 NonfreeKernelModules: zfs ApportVersion: 2.28.0-0ubuntu1 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Tue Apr 9 06:16:46 2024 InstallationDate: Installed on 2021-08-03 (980 days ago) InstallationMedia: Ubuntu 21.10 "Impish Indri" - Alpha amd64 (20210802) RebootRequiredPkgs: Error: path contained symlinks. SourcePackage: gnome-keyring UpgradeStatus: Upgraded to noble on 2024-01-31 (68 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gdm3/+bug/2060575/+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 2060575] Re: gnome-keyring fails to automatically unlock login keyring after recent updates in noble
** Changed in: gdm3 (Ubuntu) Assignee: (unassigned) => Marco Trevisan (Treviño) (3v1n0) ** Changed in: gnome-keyring (Ubuntu) Status: Triaged => Won't Fix -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-keyring in Ubuntu. https://bugs.launchpad.net/bugs/2060575 Title: gnome-keyring fails to automatically unlock login keyring after recent updates in noble Status in gdm3 package in Ubuntu: Confirmed Status in gnome-keyring package in Ubuntu: Won't Fix Bug description: After installing recent updates in 24.04, upon logging in the gnome- shell based UI pops up saying that the login keyring was not unlocked and asking for the users password to be input to unlock it. Similarly a second, non-gnome-shell based UI is also present asking the same thing. Will try and get a screenshot to attach. ProblemType: Bug DistroRelease: Ubuntu 24.04 Package: libpam-gnome-keyring 46.1-2build1 ProcVersionSignature: Ubuntu 6.8.0-22.22-generic 6.8.1 Uname: Linux 6.8.0-22-generic x86_64 NonfreeKernelModules: zfs ApportVersion: 2.28.0-0ubuntu1 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Tue Apr 9 06:16:46 2024 InstallationDate: Installed on 2021-08-03 (980 days ago) InstallationMedia: Ubuntu 21.10 "Impish Indri" - Alpha amd64 (20210802) RebootRequiredPkgs: Error: path contained symlinks. SourcePackage: gnome-keyring UpgradeStatus: Upgraded to noble on 2024-01-31 (68 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gdm3/+bug/2060575/+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 2061216] Re: Everything freezes when I alt+tab from a fullscreen application
It could be ibus-related Also try to get a backtrace following (the last part of) this: - https://wiki.gnome.org/Projects/GnomeShell/Debugging#Acquiring_a_backtrace_of_a_running_GNOME_Shell_in_automated_mode Then provide the logs -- 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/2061216 Title: Everything freezes when I alt+tab from a fullscreen application Status in gnome-shell package in Ubuntu: Incomplete Bug description: When I alt-tab from a fulscreen window and click on the window I want to go to with my mouse, the entire desktop freezes, instead of just opening the window I'm trying to go to. I can move my mouse around and audio is still playing, but everything is unresponsive. Version of Ubuntu: Ubuntu 22.04.4 LTS To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/2061216/+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 2061153] Re: No login prompt after installing in HyperV
** Changed in: gnome-shell (Ubuntu) Status: New => In Progress ** Changed in: gnome-shell (Ubuntu) Assignee: (unassigned) => Marco Trevisan (Treviño) (3v1n0) -- 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/2061153 Title: No login prompt after installing in HyperV Status in gnome-shell package in Ubuntu: In Progress Bug description: I installed the 24.04 beta ISO (the version from 2024-04-12) on a HyperV VM. Running through the installer itself seemed fine, but after rebooting GDM seemed to start but doesn't offer any users to login with. Not even an "Other" button. GDM itself has definitely started, as the current time is visible at the top of the screen, and the network and accessibility icons are visible at the top right of the screen. But the center of the screen is blank. If I manually mount the drive and examine the journal logs, I see a "JS Error" from gnome-shell that seems likely to be related: Apr 12 14:47:29 jwilcox-u24b gnome-shell[1735]: Starting Authd!!! Apr 12 14:47:29 jwilcox-u24b gnome-shell[1735]: JS ERROR: TypeError: this._button is undefined _createSessionMenuButton@resource:///org/gnome/shell/gdm/loginDialog.js:663:13 _init@resource:///org/gnome/shell/gdm/loginDialog.js:589:14 LoginDialog@resource:///org/gnome/shell/gdm/loginDialog.js:487:4 _ensureUnlockDialog@resource:///org/gnome/shell/ui/screenShield.js:472:28 showDialog@resource:///org/gnome/shell/ui/screenShield.js:404:14 _initializeUI/<@resource:///org/gnome/shell/ui/main.js:317:26 _prepareStartupAnimation@resource:///org/gnome/shell/ui/layout.js:764:18 _loadBackground/signalIdhttps://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/2061153/+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 2061355] Re: fractional scaling does not work on X11
** Package changed: gnome-shell (Ubuntu) => 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/2061355 Title: fractional scaling does not work on X11 Status in mutter package in Ubuntu: New Bug description: On the Noble Beta version, Fractional scaling does not work on Xorg/Gnome. I can neither enable it through the control center nor the gsettings. Please advice. It works on Wayland, but somehow QT applications including VS Code are hazy. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mutter/+bug/2061355/+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
Sorry, I missed the previous comments. > Do I read the gnome-settings-daemon patches correctly, and this actually just entirely drops support for auth via NSS? So the regression potential is that if someone has set up auth via a custom system nss database, this *will* break login for them? Well, yes that's a regression potential that may indeed be mentioned, it's also something that we never supported though, since that required some extra setup in various places (write a gdm pam configuration, create the NSS database and configure pam-pkcs11/pam_sss). But indeed it could potentially affect someone who went through all this. However... The SSSD side of this (lp:1905790), if one had configured a NSS database in the canonical location, it will be migrated (using this tool https://github.com/3v1n0/nss-database-pem-exporter). So, it's quite a remote possibility but worth to mention in a clearer way (it was somewhat written already). > Unrelatedly, patches like smartcard-Use-autopointers.patch and smartcard-manager-Use-mutex-auto-lockers-when-convenient.patch are the sort of refactoring patches that we prefer not to see in SRUs. I don't think they're a blocker, but they make reviewing more difficult Let me know if I should drop them, one reason why they were added is that they were part of the upstream changes too, and so it made easier to ensure that we're both in the same line if problems may happen, making easier to backport patches in future if needed. -- 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 sssd package in Ubuntu: Fix Released Status in gdm3 source package in Focal: In Progress Status in gnome-settings-daemon source package in Focal: Incomplete Status in sssd source package in Focal: In Progress Status in gdm3 package in Debian: Fix Released Bug description: [ Impact ] 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. [ Test case ] 1. When in GDM, insert a smartcard 2. The GDM interface should require for an user 3. The user should be set (or empty may be provided, depending on sssd configuration) 4. The smartcard PIN should be requested and once introduce the user must login. Note that this requires configuring sssd before, a simple local configuration could require having sssd.conf filled with: ```ini [sssd] enable_files_domain = True services = pam [certmap/implicit_files/$USER] matchrule = .*YOUR CARD IDENTIFIER* [pam] pam_cert_auth = True ``` The UI authentication can also be simulated via pamtester: # Must be ran as user sudo apt install pamtester pamtester -v gdm-smartcard $USER authenticate Expected output is + pamtester -v gdm-smartcard ubuntu authenticate pamtester: invoking pam_start(gdm-smartcard, ubuntu, ...) pamtester: performing operation - authenticate PIN for Test Organization Sub Int Token: pamtester: successfully authenticated --- Alternatively, if no smartcard or hardware is available, this can be tested and simulated using these scripts (they will reset the system setup at each run, but it's suggested to run them in a VM, lxd container or in a test installation): https://gist.github.com/3v1n0/287d02ca8e03936f1c7bba992173d47a - sudo apt install gdm3 pamtester softhsm2 openssl wget sssd gnutls-bin && \ sudo apt-mark auto gdm3 pamtester softhsm2 openssl wget sssd gnutls-bin - wget https://gist.github.com/3v1n0/287d02ca8e03936f1c7bba992173d47a/raw/sssd-gdm-smartcard-pam-auth-tester.sh - wget https://gist.github.com/3v1n0/287d02ca8e03936f1c7bba992173d47a/raw/sssd-softhism2-certificates-tests.sh - sudo bash ./sssd-gdm-smartcard-pam-auth-tester.sh The script will generate some fake CA authority, issue some certificates, will install them in some software-based smartcards (using softhsm2) and test that they work properly to login with gdm- smartcard. Using `WAIT` environment variable set (to any value) will make it to restart gdm at each iteration so that an user can try to access, using the username that launched the script and the pin of 123456. [ Regression potential ] Smartcard authentication using custom methods using via a custom configured system nss database may not work anymore. --- ProblemType: BugDistroRelease: 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
[Desktop-packages] [Bug 2037604] Re: Backport packages for 22.04.4 HWE stack
I can test this too if needed, I've a AMD® Ryzen 7 pro 7840u with radeon 780m graphics (phoenix). -- 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/2037604 Title: Backport packages for 22.04.4 HWE stack Status in directx-headers package in Ubuntu: Invalid Status in mesa package in Ubuntu: Invalid Status in rust-bindgen package in Ubuntu: Invalid Status in rust-clang-sys package in Ubuntu: Invalid Status in directx-headers source package in Jammy: Fix Committed Status in mesa source package in Jammy: Fix Committed Status in rust-bindgen source package in Jammy: Invalid Status in rust-clang-sys source package in Jammy: Invalid Bug description: [Impact] The graphics HWE stack from mantic needs to be backported for 22.04.4 directx-headers - build-dep of the new Mesa mesa - new major release (23.2.x) - new HW support, Meteor Lake.. [Test case] We want to cover at least 2-3 different, widely used and already previously supported GPU generations from both AMD and Intel which are supported by this release, as those are the ones that cover most bases; nouveau users tend to switch to the NVIDIA blob after installation. No need to test ancient GPU's supported by mesa-amber. And best to focus on the newer generations (~5y and newer) as the older ones are less likely to break at this point. - AMD: Vega, Navi1x (RX5000*), Navi2x (RX6000*), Navi3x (RX7000*) - Intel: gen9 (SKL/APL/KBL/CFL/WHL/CML), gen11 (ICL), gen12 (TGL/RKL/RPL/DG2) Install the new packages and run some tests: - check that the desktop is still using hw acceleration and hasn't fallen back to swrast/llvmpipe - run freely available benchmarks that torture the GPU (Unigine Heaven/Valley/Superposition) - run some games from Steam if possible and in each case check that there is no gfx corruption happening or worse. Note that upstream releases have already been tested for OpenGL and Vulkan conformance by their CI. [Where things could go wrong] This is a major update of Mesa, there could be regressions but we'll try to catch any with testing. And since it shares bugs with mantic, we'd already know if there are serious issues. We will backport the final 23.2.x at a later stage, the first backport is needed for enabling Intel Meteor Lake. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/directx-headers/+bug/2037604/+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 1933027] Re: Gdm3 with smartcard asks for login/smartcard pin even if there is no smartcard authentication enabled
By default GDM switches to smartcard mode once one is plugged in, smartcard auth can be disabled at gdm level though, by changing the gsettings. sudo -u gdm env -u XDG_RUNTIME_DIR -u DISPLAY DCONF_PROFILE=gdm dbus-run-session \ gsettings set org.gnome.login-screen enable-smartcard-authentication false -- 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/1933027 Title: Gdm3 with smartcard asks for login/smartcard pin even if there is no smartcard authentication enabled Status in gdm3 package in Ubuntu: Confirmed Status in gnome-shell package in Ubuntu: Confirmed Bug description: I use my Ubuntu PC with Yubikey almost always plugged in. It provides several security token interfaces, such as U2F, GPG smartcard, proprieritary Yubico interfaces (of which I mostly use TOTP codes), and also PIV smartcard. However, I haven't configured a PIV smartcard on it. Whenever I login into the system having Yubikey plugged in, I'm prompted for login name, and then for PIN for some smartcard while also being asked to plug in one. This is very misleading on several layers: 1. I have the device providing smartcard plugged id, 2. But it's not the smartcard GDM would think it is as it's not configured properly, 3. There are no local smartcard-authenticating users right now in the system, 3. There are no remote authentication systems configured on the system (so no ActiveDirectory-smartcard logins or such). If I unplug the token UX goes back on old good track. Given the circumstances above, I'd consider that GDM (and, on my bet, any PAM configuration it uses) shouldn't offer to login using smartcard if there is no way to actually do so. I feel something is off here, so I'm reporting a bug. It could be an upstream problem though; it also could be an upstream SSSD problem, or all combined. I believe there is a more clear user experience: 1. GDM should display users that can login into the system, as it always does (if configured). It may also provide entering other login name (also if configured). This is GDM usually does without smartcards altogether. 2. When user is chosen (from the list or manually typed in), check can this user even authenticate with smartcards (i.e. if any of available smartcards is actually recognised for this user). If so, then ask for PIN. Else, don't show anything about smartcards at all (this includes when SSSD is not configured for any AD or related and this user has no local smartcard configuration). This can switch there & back based on device events. I've seen other OS doing this. Ubuntu/Gnome session doesn't ask me for PIN for a smartcard on a lock screen, so I guess it doesn't support it at all or correctly finds out it can't be used. Even more, I couldn't find a way to actually add my smartcard as a local login method. ProblemType: Bug DistroRelease: Ubuntu 21.04 Package: gdm3 3.38.2.1-2ubuntu1 ProcVersionSignature: Ubuntu 5.11.0-18.19-generic 5.11.17 Uname: Linux 5.11.0-18-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu65.1 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: ubuntu:GNOME Date: Sun Jun 20 14:02:02 2021 InstallationDate: Installed on 2017-03-05 (1567 days ago) InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 (20160420.1) ProcEnviron: TERM=tmux-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=ru_RU.UTF-8 SHELL=/bin/bash SourcePackage: gdm3 UpgradeStatus: Upgraded to hirsute on 2021-05-13 (37 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gdm3/+bug/1933027/+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 2038783] Re: Exit code of locations mount script is not respecting error
** Description changed: [ Impact ] When mounting an external location a script is used to get the current default app for a type, its return error is parsed by the dock to provide users a feedback, but the returned code is not valid in case of error. [ Test case ] Run: gjs -m /usr/share/gnome-shell/extensions/ubuntu-d...@ubuntu.com/locationsWorker.js handler file:///foo/bar/baz echo $? - An error should be shown and the return code should be 15 + An error should be shown and the return code should be 1 Doing instead gjs -m /usr/share/gnome-shell/extensions/ubuntu-d...@ubuntu.com/locationsWorker.js handler file://$HOME echo $? The file manager desktop-id should be printed and the script should return 0. [ Regression Potential ] Some locations may not have a default handler and so not being launched -- 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/2038783 Title: Exit code of locations mount script is not respecting error Status in gnome-shell-extension-ubuntu-dock package in Ubuntu: Fix Released Status in gnome-shell-extension-ubuntu-dock source package in Mantic: Fix Committed Bug description: [ Impact ] When mounting an external location a script is used to get the current default app for a type, its return error is parsed by the dock to provide users a feedback, but the returned code is not valid in case of error. [ Test case ] Run: gjs -m /usr/share/gnome-shell/extensions/ubuntu-d...@ubuntu.com/locationsWorker.js handler file:///foo/bar/baz echo $? An error should be shown and the return code should be 1 Doing instead gjs -m /usr/share/gnome-shell/extensions/ubuntu-d...@ubuntu.com/locationsWorker.js handler file://$HOME echo $? The file manager desktop-id should be printed and the script should return 0. [ Regression Potential ] Some locations may not have a default handler and so not being launched To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell-extension-ubuntu-dock/+bug/2038783/+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 2038783] Re: Exit code of locations mount script is not respecting error
** Description changed: [ Impact ] When mounting an external location a script is used to get the current default app for a type, its return error is parsed by the dock to provide users a feedback, but the returned code is not valid in case of error. [ Test case ] Run: - gjs -m /usr/share/gnome-shell/extensions/ubuntu-d...@ubuntu.com/locationsWorker.js /foo/bar/baz - echo $? + gjs -m /usr/share/gnome-shell/extensions/ubuntu-d...@ubuntu.com/locationsWorker.js handler /foo/bar/baz + echo $? An error should be shown and the return code should be 15 Doing instead - gjs -m /usr/share/gnome-shell/extensions/ubuntu-d...@ubuntu.com/locationsWorker.js $HOME - echo $? + gjs -m /usr/share/gnome-shell/extensions/ubuntu-d...@ubuntu.com/locationsWorker.js handler $HOME + echo $? The file manager desktop-id should be printed and the script should return 0. [ Regression Potential ] Some locations may not have a default handler and so not being launched ** Description changed: [ Impact ] When mounting an external location a script is used to get the current default app for a type, its return error is parsed by the dock to provide users a feedback, but the returned code is not valid in case of error. [ Test case ] Run: - gjs -m /usr/share/gnome-shell/extensions/ubuntu-d...@ubuntu.com/locationsWorker.js handler /foo/bar/baz + gjs -m /usr/share/gnome-shell/extensions/ubuntu-d...@ubuntu.com/locationsWorker.js handler file:///foo/bar/baz echo $? An error should be shown and the return code should be 15 Doing instead - gjs -m /usr/share/gnome-shell/extensions/ubuntu-d...@ubuntu.com/locationsWorker.js handler $HOME + gjs -m /usr/share/gnome-shell/extensions/ubuntu-d...@ubuntu.com/locationsWorker.js handler file://$HOME echo $? The file manager desktop-id should be printed and the script should return 0. [ Regression Potential ] Some locations may not have a default handler and so not being launched -- 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/2038783 Title: Exit code of locations mount script is not respecting error Status in gnome-shell-extension-ubuntu-dock package in Ubuntu: Fix Released Status in gnome-shell-extension-ubuntu-dock source package in Mantic: Fix Committed Bug description: [ Impact ] When mounting an external location a script is used to get the current default app for a type, its return error is parsed by the dock to provide users a feedback, but the returned code is not valid in case of error. [ Test case ] Run: gjs -m /usr/share/gnome-shell/extensions/ubuntu-d...@ubuntu.com/locationsWorker.js handler file:///foo/bar/baz echo $? An error should be shown and the return code should be 15 Doing instead gjs -m /usr/share/gnome-shell/extensions/ubuntu-d...@ubuntu.com/locationsWorker.js handler file://$HOME echo $? The file manager desktop-id should be printed and the script should return 0. [ Regression Potential ] Some locations may not have a default handler and so not being launched To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell-extension-ubuntu-dock/+bug/2038783/+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 2034664] Re: Meta.Rectangle is deprecated, use Mtk.Rectangle instead
Corrado, I think this is not a big deal. The deprecation warning is just a warning, so everything should still work even when using Meta instead of Mtk. This is an update that we can also get at later point, so I think Utkarsh is fine to wait (and I also was expecting this to happen, thus I adapted the bug report to the SRU template). ** Description changed: [ Impact ] The gnome-shell 45.rc log fills with: Meta.Rectangle is deprecated, use Mtk.Rectangle instead [ Test case ] Run ubuntu with ubuntu extensions enabled (only). journalctl /usr/bin/gnome-shell should not contain any reference to Meta.Rectangle deprecation [ Regression potential ] - Introspected types are not defined and so extensions my try to use + Introspected types are not defined and so extensions may try to use undefined code. -- 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/2034664 Title: Meta.Rectangle is deprecated, use Mtk.Rectangle instead Status in gnome-shell-extension-tiling-assistant package in Ubuntu: Fix Released Status in gnome-shell-extension-ubuntu-dock package in Ubuntu: Fix Committed Bug description: [ Impact ] The gnome-shell 45.rc log fills with: Meta.Rectangle is deprecated, use Mtk.Rectangle instead [ Test case ] Run ubuntu with ubuntu extensions enabled (only). journalctl /usr/bin/gnome-shell should not contain any reference to Meta.Rectangle deprecation [ Regression potential ] Introspected types are not defined and so extensions may try to use undefined code. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell-extension-tiling-assistant/+bug/2034664/+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 2033688] Re: [mantic] gnome-shell fails to follow accent colours
** Description changed: - When accent colors are selected in gnome-control-center, gnome-shell - fails to follow with the exception of blue and orange. Screenshots - attached. + Impact + -- + When accent colors are selected in gnome-control-center, gnome-shell fails to follow with the exception of blue and orange. Screenshots attached. Test Case - 1. Open the Settings app 2. Switch to the Appearance page 3. Choose the Purple color 4. Click the quick settings area in the far right side of GNOME Shell's top bar 5. The highlights should be purple What Happens Instead The highlights are still orange - ProblemType: Bug - DistroRelease: Ubuntu 23.10 + Regression Potential + + Themes for default accent color or for high-contrast theme are not generated properly. + + + --- + + ProblemType: BugDistroRelease: 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: pass CurrentDesktop: ubuntu:GNOME Date: Thu Aug 31 13:50:24 2023 DisplayManager: gdm3 InstallationDate: Installed on 2023-03-04 (180 days ago) InstallationMedia: Edubuntu 23.04 "Lunar Lobster" - Alpha amd64 Binary-1 (20230304) - RelatedPackageVersions: mutter-common 45~beta.1-1ubuntu1 - SourcePackage: gnome-shell + RelatedPackageVersions: mutter-common 45~beta.1-1ubuntu1SourcePackage: gnome-shell UpgradeStatus: No upgrade log present (probably fresh install) -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-shell in Ubuntu. https://bugs.launchpad.net/bugs/2033688 Title: [mantic] gnome-shell fails to follow accent colours Status in Yaru Theme: New Status in gnome-shell package in Ubuntu: Triaged Status in yaru-theme package in Ubuntu: In Progress Status in gnome-shell source package in Mantic: Won't Fix Bug description: Impact -- When accent colors are selected in gnome-control-center, gnome-shell fails to follow with the exception of blue and orange. Screenshots attached. Test Case - 1. Open the Settings app 2. Switch to the Appearance page 3. Choose the Purple color 4. Click the quick settings area in the far right side of GNOME Shell's top bar 5. The highlights should be purple What Happens Instead The highlights are still orange Regression Potential Themes for default accent color or for high-contrast theme are not generated properly. --- ProblemType: BugDistroRelease: 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: pass CurrentDesktop: ubuntu:GNOME Date: Thu Aug 31 13:50:24 2023 DisplayManager: gdm3 InstallationDate: Installed on 2023-03-04 (180 days ago) InstallationMedia: Edubuntu 23.04 "Lunar Lobster" - Alpha amd64 Binary-1 (20230304) RelatedPackageVersions: mutter-common 45~beta.1-1ubuntu1SourcePackage: gnome-shell UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/yaru/+bug/2033688/+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 2038788] [NEW] some gnome-control-center icons are not using the yaru style
Public bug reported: [ Impact ] Some symbolic icons in Settings are not using the yaru theme [ Test case ] - Open gnome-control-center - Ensure the symbolic icons are using the yaru themed icons. In particular check: - Camera - Microphone - Location - Lock screen - Thunderbolt [ Regression potential ] Icons in gnome-control-center are missing ** Affects: yaru-theme (Ubuntu) Importance: Medium Status: In Progress -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to yaru-theme in Ubuntu. https://bugs.launchpad.net/bugs/2038788 Title: some gnome-control-center icons are not using the yaru style Status in yaru-theme package in Ubuntu: In Progress Bug description: [ Impact ] Some symbolic icons in Settings are not using the yaru theme [ Test case ] - Open gnome-control-center - Ensure the symbolic icons are using the yaru themed icons. In particular check: - Camera - Microphone - Location - Lock screen - Thunderbolt [ Regression potential ] Icons in gnome-control-center are missing To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/yaru-theme/+bug/2038788/+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 2038787] [NEW] gnome-shell panel height is wrong
Public bug reported: [ Impact ] Gnome shell panel height is less than it should be, making it less usable when interacting with widgets. [ Test case ] - Ensure the panel is at least 2.2em as GNOME upstream one does [ Regression potential ] Panel uses too much space ** Affects: yaru-theme (Ubuntu) Importance: Medium Status: In Progress ** Description changed: [ Impact ] Gnome shell panel height is less than it should be, making it less usable when interacting with widgets. [ Test case ] - - Ensure the panel is at least 2.2em + - Ensure the panel is at least 2.2em as GNOME upstream one does [ Regression potential ] - Panel uses more space + Panel uses too much space -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to yaru-theme in Ubuntu. https://bugs.launchpad.net/bugs/2038787 Title: gnome-shell panel height is wrong Status in yaru-theme package in Ubuntu: In Progress Bug description: [ Impact ] Gnome shell panel height is less than it should be, making it less usable when interacting with widgets. [ Test case ] - Ensure the panel is at least 2.2em as GNOME upstream one does [ Regression potential ] Panel uses too much space To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/yaru-theme/+bug/2038787/+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 2038786] [NEW] Shell light theme inputs background is wrong
Public bug reported: [ Impact ] When using the light theme, the entries background in dialogs use a wrong color, see https://user- images.githubusercontent.com/36476595/265630410-43552087-082c-4e33-97fa- bb145cc6dcc7.png [ Test case ] - Enable a light theme - Press Alt+F2 to see the runner dialog - The background of the entries should be white [ Regression potential ] Entries text is not readable ** Affects: yaru-theme (Ubuntu) Importance: Medium Status: In Progress -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to yaru-theme in Ubuntu. https://bugs.launchpad.net/bugs/2038786 Title: Shell light theme inputs background is wrong Status in yaru-theme package in Ubuntu: In Progress Bug description: [ Impact ] When using the light theme, the entries background in dialogs use a wrong color, see https://user- images.githubusercontent.com/36476595/265630410-43552087-082c-4e33-97fa- bb145cc6dcc7.png [ Test case ] - Enable a light theme - Press Alt+F2 to see the runner dialog - The background of the entries should be white [ Regression potential ] Entries text is not readable To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/yaru-theme/+bug/2038786/+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 2038785] [NEW] Shell uses Wrong focus ring color
Public bug reported: [ Impact ] Focus ring color in text entries is wrong, see https://user- images.githubusercontent.com/36476595/265629691-5d485a46-7041-4b19-a4b4-abdcc6c73027.png [ Test case ] - Open gnome-shell overview, focus the search entry - The color should match the accent and be clearly visible [ Regression potential ] Focus ring is not visible or has wrong color ** Affects: yaru-theme (Ubuntu) Importance: Undecided Status: In Progress -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to yaru-theme in Ubuntu. https://bugs.launchpad.net/bugs/2038785 Title: Shell uses Wrong focus ring color Status in yaru-theme package in Ubuntu: In Progress Bug description: [ Impact ] Focus ring color in text entries is wrong, see https://user- images.githubusercontent.com/36476595/265629691-5d485a46-7041-4b19-a4b4-abdcc6c73027.png [ Test case ] - Open gnome-shell overview, focus the search entry - The color should match the accent and be clearly visible [ Regression potential ] Focus ring is not visible or has wrong color To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/yaru-theme/+bug/2038785/+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 2038784] [NEW] Gnome Shell Sound volume slider thumb border is cropped, using wrong color shade
Public bug reported: [ Impact ] The sound volume slider thumb borders are cropped as visible in: https://user-images.githubusercontent.com/36476595/265630526-f4e73c79-8bd3-44e4-924c-cbfe3afb80d4.png [ Test case ] - Open gnome-shell quicklist, the volume slider thumb should not be cropped - The color should match the accent [ Regression potential ] Slider is not visible or has wrong color ** Affects: yaru-theme (Ubuntu) Importance: Low Assignee: Marco Trevisan (Treviño) (3v1n0) Status: In Progress -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to yaru-theme in Ubuntu. https://bugs.launchpad.net/bugs/2038784 Title: Gnome Shell Sound volume slider thumb border is cropped, using wrong color shade Status in yaru-theme package in Ubuntu: In Progress Bug description: [ Impact ] The sound volume slider thumb borders are cropped as visible in: https://user-images.githubusercontent.com/36476595/265630526-f4e73c79-8bd3-44e4-924c-cbfe3afb80d4.png [ Test case ] - Open gnome-shell quicklist, the volume slider thumb should not be cropped - The color should match the accent [ Regression potential ] Slider is not visible or has wrong color To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/yaru-theme/+bug/2038784/+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 2033688] Re: [mantic] gnome-shell fails to follow accent colours
** Changed in: gnome-shell (Ubuntu Mantic) Status: Triaged => Won't Fix ** Also affects: yaru-theme (Ubuntu) Importance: Undecided Status: New ** Changed in: yaru-theme (Ubuntu) Status: New => Triaged ** Changed in: yaru-theme (Ubuntu) Status: Triaged => In Progress ** Changed in: yaru-theme (Ubuntu) Assignee: (unassigned) => Marco Trevisan (Treviño) (3v1n0) -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to yaru-theme in Ubuntu. https://bugs.launchpad.net/bugs/2033688 Title: [mantic] gnome-shell fails to follow accent colours Status in Yaru Theme: New Status in gnome-shell package in Ubuntu: Triaged Status in yaru-theme package in Ubuntu: In Progress Status in gnome-shell source package in Mantic: Won't Fix Bug description: When accent colors are selected in gnome-control-center, gnome-shell fails to follow with the exception of blue and orange. Screenshots attached. Test Case - 1. Open the Settings app 2. Switch to the Appearance page 3. Choose the Purple color 4. Click the quick settings area in the far right side of GNOME Shell's top bar 5. The highlights should be purple What Happens Instead The highlights are still orange 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: pass CurrentDesktop: ubuntu:GNOME Date: Thu Aug 31 13:50:24 2023 DisplayManager: gdm3 InstallationDate: Installed on 2023-03-04 (180 days ago) InstallationMedia: Edubuntu 23.04 "Lunar Lobster" - Alpha amd64 Binary-1 (20230304) 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/yaru/+bug/2033688/+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 2034664] Re: Meta.Rectangle is deprecated, use Mtk.Rectangle instead
** Description changed: + [ Impact ] + The gnome-shell 45.rc log fills with: Meta.Rectangle is deprecated, use Mtk.Rectangle instead + + [ Test case ] + + Run ubuntu with ubuntu extensions enabled (only). + journalctl /usr/bin/gnome-shell should not contain any reference to Meta.Rectangle deprecation + + [ Regression potential ] + + Introspected types are not defined and so extensions my try to use + undefined code. -- 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/2034664 Title: Meta.Rectangle is deprecated, use Mtk.Rectangle instead Status in gnome-shell-extension-tiling-assistant package in Ubuntu: Fix Released Status in gnome-shell-extension-ubuntu-dock package in Ubuntu: Fix Committed Bug description: [ Impact ] The gnome-shell 45.rc log fills with: Meta.Rectangle is deprecated, use Mtk.Rectangle instead [ Test case ] Run ubuntu with ubuntu extensions enabled (only). journalctl /usr/bin/gnome-shell should not contain any reference to Meta.Rectangle deprecation [ Regression potential ] Introspected types are not defined and so extensions my try to use undefined code. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell-extension-tiling-assistant/+bug/2034664/+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 2038783] [NEW] Exit code of locations mount script is not respecting error
Public bug reported: [ Impact ] When mounting an external location a script is used to get the current default app for a type, its return error is parsed by the dock to provide users a feedback, but the returned code is not valid in case of error. [ Test case ] Run: gjs -m /usr/share/gnome-shell/extensions/ubuntu-d...@ubuntu.com/locationsWorker.js /foo/bar/baz echo $? An error should be shown and the return code should be 15 Doing instead gjs -m /usr/share/gnome-shell/extensions/ubuntu-d...@ubuntu.com/locationsWorker.js $HOME echo $? The file manager desktop-id should be printed and the script should return 0. [ Regression Potential ] Some locations may not have a default handler and so not being launched ** Affects: gnome-shell-extension-ubuntu-dock (Ubuntu) Importance: Medium Assignee: Marco Trevisan (Treviño) (3v1n0) Status: In Progress -- 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/2038783 Title: Exit code of locations mount script is not respecting error Status in gnome-shell-extension-ubuntu-dock package in Ubuntu: In Progress Bug description: [ Impact ] When mounting an external location a script is used to get the current default app for a type, its return error is parsed by the dock to provide users a feedback, but the returned code is not valid in case of error. [ Test case ] Run: gjs -m /usr/share/gnome-shell/extensions/ubuntu-d...@ubuntu.com/locationsWorker.js /foo/bar/baz echo $? An error should be shown and the return code should be 15 Doing instead gjs -m /usr/share/gnome-shell/extensions/ubuntu-d...@ubuntu.com/locationsWorker.js $HOME echo $? The file manager desktop-id should be printed and the script should return 0. [ Regression Potential ] Some locations may not have a default handler and so not being launched To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell-extension-ubuntu-dock/+bug/2038783/+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 2030959] Re: Cursor sometimes stutters after heavy shell animations in 42.9
** Changed in: mutter (Ubuntu Jammy) Status: In Progress => Fix Committed -- 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/2030959 Title: Cursor sometimes stutters after heavy shell animations in 42.9 Status in mutter package in Ubuntu: Invalid Status in mutter source package in Jammy: Fix Committed Bug description: [ Impact ] Cursor sometimes stutters after heavy shell animations in 42.9 if there is no GUI animation in response to its movement. And it doesn't stop stuttering until GUI redraws occur (giving the frame clock an opportunity to measure lower GPU usage). This is different to the recent bug fix that probably caused it: Bug 2023766: * only occurs when moving over animated GUIs. * never recovers or corrects itself. * was spatial jittering at full frame rate. * reduced the frame rate of the GUI below it. This bug: * only occurs when moving over non-animated GUIs. * does recover and correct itself. * is stuttering at seemingly half frame rate, but perfect spatially. * does not reduce the frame rate of the the GUI below. I think the reason we only see this in 42 (jammy) is because that predates the change in the triple buffering algorithm to scale based on "dynamic max render time" alone. [ Workaround ] Add this to /etc/environment: MUTTER_DEBUG_ENABLE_ATOMIC_KMS=0 and then reboot. [ Test Plan ] 1. Stress GNOME Shell maximally by repeatedly entering/leaving the overview and/or scrolling the app grid. 2. Stop suddenly and wiggle the mouse over some part of the desktop that DOES NOT respond to mouse movement. Such as the wallpaper or some blank grey space next to the app grid. Expect: The mouse cursor does not get stuck in half frame rate. [ Where problems could occur ] In desktop frame timing since the clutter frame clock is being changed. Although risk is minimal since we're just reverting to the pre-July state of that code. [ Other Info ] The patch being dropped was found to not really be required in GNOME 42: https://bugs.launchpad.net/ubuntu/+source/mutter/+bug/2023766/comments/13 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mutter/+bug/2030959/+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
** Description changed: [ Impact ] 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. [ Test case ] 1. When in GDM, insert a smartcard 2. The GDM interface should require for an user 3. The user should be set (or empty may be provided, depending on sssd configuration) 4. The smartcard PIN should be requested and once introduce the user must login. Note that this requires configuring sssd before, a simple local configuration could require having sssd.conf filled with: ```ini [sssd] enable_files_domain = True services = pam [certmap/implicit_files/$USER] matchrule = .*YOUR CARD IDENTIFIER* [pam] pam_cert_auth = True ``` The UI authentication can also be simulated via pamtester: # Must be ran as user sudo apt install pamtester pamtester -v gdm-smartcard $USER authenticate Expected output is + pamtester -v gdm-smartcard ubuntu authenticate pamtester: invoking pam_start(gdm-smartcard, ubuntu, ...) pamtester: performing operation - authenticate PIN for Test Organization Sub Int Token: pamtester: successfully authenticated --- Alternatively, if no smartcard or hardware is available, this can be tested and simulated using these scripts (they will reset the system setup at each run, but it's suggested to run them in a VM, lxd container or in a test installation): - https://gist.github.com/3v1n0/287d02ca8e03936f1c7bba992173d47a + https://gist.github.com/3v1n0/287d02ca8e03936f1c7bba992173d47a - sudo apt install gdm3 pamtester softhsm2 openssl wget sssd gnutls-bin && \ - sudo apt-mark auto gdm3 pamtester softhsm2 openssl wget sssd gnutls-bin + sudo apt-mark auto gdm3 pamtester softhsm2 openssl wget sssd gnutls-bin - wget https://gist.github.com/3v1n0/287d02ca8e03936f1c7bba992173d47a/raw/sssd-gdm-smartcard-pam-auth-tester.sh - - sudo sssd-gdm-smartcard-pam-auth-tester.sh + - wget https://gist.github.com/3v1n0/287d02ca8e03936f1c7bba992173d47a/raw/sssd-softhism2-certificates-tests.sh + - sudo bash ./sssd-gdm-smartcard-pam-auth-tester.sh The script will generate some fake CA authority, issue some certificates, will install them in some software-based smartcards (using softhsm2) and test that they work properly to login with gdm-smartcard. Using `WAIT` environment variable set (to any value) will make it to restart gdm at each iteration so that an user can try to access, using the username that launched the script and the pin of 123456. [ Regression potential ] Smartcard authentication using custom methods using via a custom configured system nss database may not work anymore. --- ProblemType: BugDistroRelease: 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 -- 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 sssd 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 sssd source package in Focal: In Progress Status in gdm3 package in Debian: Fix Released Bug description: [ Impact ] 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. [ Test case ] 1. When in GDM, insert a smartcard 2. The GDM interface should require for an user 3. The user should be set (or empty may be provided, depending on sssd configuration) 4. The smartcard PIN should be requested and once introduce the user must login. Note that this requires configuring sssd before, a simple local configuration could require having sssd.conf filled with: ```ini [sssd] enable_files_domain = True services = pam
[Desktop-packages] [Bug 1865226] Re: gdm-smartcard pam config needs to be updated for Ubuntu and installed
Andreas: - I've now added SSSD to the bug - I had not uploaded the remaining bits yet as I was waiting for SSSD to hit the queue first - GNOME settings daemon is also uploaded now to the queue - GDM will be uploaded soon by Jeremy The bug has now been updated to have a proper SRU template, with all the tests required to check all the 3 packages. ** Also affects: sssd (Ubuntu) Importance: Undecided Status: New ** Changed in: sssd (Ubuntu) Status: New => In Progress ** Changed in: sssd (Ubuntu) Assignee: (unassigned) => Marco Trevisan (Treviño) (3v1n0) ** No longer affects: gdm3 (Ubuntu Focal) ** No longer affects: gnome-settings-daemon (Ubuntu Focal) ** Also affects: gnome-settings-daemon (Ubuntu Focal) Importance: Undecided Status: New ** Also affects: sssd (Ubuntu Focal) Importance: Undecided Status: New ** Also affects: gdm3 (Ubuntu Focal) Importance: Undecided Status: New ** Changed in: gdm3 (Ubuntu Focal) Importance: Undecided => High ** Changed in: gdm3 (Ubuntu Focal) Assignee: (unassigned) => Marco Trevisan (Treviño) (3v1n0) ** Changed in: gnome-settings-daemon (Ubuntu Focal) Importance: Undecided => Medium ** Changed in: gnome-settings-daemon (Ubuntu Focal) Assignee: (unassigned) => Marco Trevisan (Treviño) (3v1n0) ** Changed in: sssd (Ubuntu Focal) Status: New => In Progress ** Changed in: sssd (Ubuntu Focal) Assignee: (unassigned) => Marco Trevisan (Treviño) (3v1n0) ** Changed in: gdm3 (Ubuntu Focal) Status: New => In Progress ** Changed in: gnome-settings-daemon (Ubuntu Focal) Status: New => In Progress ** Changed in: sssd (Ubuntu) Status: In Progress => Fix Released -- 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 sssd 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 sssd source package in Focal: In Progress Status in gdm3 package in Debian: Fix Released Bug description: [ Impact ] 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. [ Test case ] 1. When in GDM, insert a smartcard 2. The GDM interface should require for an user 3. The user should be set (or empty may be provided, depending on sssd configuration) 4. The smartcard PIN should be requested and once introduce the user must login. Note that this requires configuring sssd before, a simple local configuration could require having sssd.conf filled with: ```ini [sssd] enable_files_domain = True services = pam [certmap/implicit_files/$USER] matchrule = .*YOUR CARD IDENTIFIER* [pam] pam_cert_auth = True ``` The UI authentication can also be simulated via pamtester: # Must be ran as user sudo apt install pamtester pamtester -v gdm-smartcard $USER authenticate Expected output is + pamtester -v gdm-smartcard ubuntu authenticate pamtester: invoking pam_start(gdm-smartcard, ubuntu, ...) pamtester: performing operation - authenticate PIN for Test Organization Sub Int Token: pamtester: successfully authenticated --- Alternatively, if no smartcard or hardware is available, this can be tested and simulated using these scripts (they will reset the system setup at each run, but it's suggested to run them in a VM, lxd container or in a test installation): https://gist.github.com/3v1n0/287d02ca8e03936f1c7bba992173d47a - sudo apt install gdm3 pamtester softhsm2 openssl wget sssd gnutls-bin && \ sudo apt-mark auto gdm3 pamtester softhsm2 openssl wget sssd gnutls-bin - wget https://gist.github.com/3v1n0/287d02ca8e03936f1c7bba992173d47a/raw/sssd-gdm-smartcard-pam-auth-tester.sh - wget https://gist.github.com/3v1n0/287d02ca8e03936f1c7bba992173d47a/raw/sssd-softhism2-certificates-tests.sh - sudo bash ./sssd-gdm-smartcard-pam-auth-tester.sh The script will generate some fake CA authority, issue some certificates, will install them in some software-based smartcards (using softhsm2) and test that they work properly to login with gdm- smartcard. Using `WAIT` environment variable set (to any value) will make it to restart gdm at each iteration so that an user can try to access, using the username that launched the script and the pin of 123456. [ Regression potential ] Smartcard authentication using custo
[Desktop-packages] [Bug 1865226] Re: gdm-smartcard pam config needs to be updated for Ubuntu and installed
** Description changed: + [ Impact ] + 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 + [ Test case ] + + 1. When in GDM, insert a smartcard + 2. The GDM interface should require for an user + 3. The user should be set (or empty may be provided, +depending on sssd configuration) + 4. The smartcard PIN should be requested and once introduce the +user must login. + + Note that this requires configuring sssd before, a simple local + configuration could require having sssd.conf filled with: + + ```ini + [sssd] + enable_files_domain = True + services = pam + + [certmap/implicit_files/$USER] + matchrule = .*YOUR CARD IDENTIFIER* + + [pam] + pam_cert_auth = True + ``` + + The UI authentication can also be simulated via pamtester: + + # Must be ran as user + sudo apt install pamtester + pamtester -v gdm-smartcard $USER authenticate + + Expected output is + + pamtester -v gdm-smartcard ubuntu authenticate + pamtester: invoking pam_start(gdm-smartcard, ubuntu, ...) + pamtester: performing operation - authenticate + PIN for Test Organization Sub Int Token: + pamtester: successfully authenticated + + [ Regression potential ] + + Smartcard authentication using custom methods using via a custom + configured system nss database may not work anymore. + + --- + + ProblemType: BugDistroRelease: 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 + 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 ** Description changed: [ Impact ] 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. [ Test case ] 1. When in GDM, insert a smartcard 2. The GDM interface should require for an user 3. The user should be set (or empty may be provided, -depending on sssd configuration) + depending on sssd configuration) 4. The smartcard PIN should be requested and once introduce the -user must login. + user must login. Note that this requires configuring sssd before, a simple local configuration could require having sssd.conf filled with: ```ini [sssd] enable_files_domain = True services = pam [certmap/implicit_files/$USER] matchrule = .*YOUR CARD IDENTIFIER* [pam] pam_cert_auth = True ``` The UI authentication can also be simulated via pamtester: # Must be ran as user sudo apt install pamtester pamtester -v gdm-smartcard $USER authenticate Expected output is + pamtester -v gdm-smartcard ubuntu authenticate pamtester: invoking pam_start(gdm-smartcard, ubuntu, ...) pamtester: performing operation - authenticate PIN for Test Organization Sub Int Token: pamtester: successfully authenticated + --- + + Alternatively, if no smartcard or hardware is available, this can be tested and simulated using these scripts (they will reset the system setup at each run, but it's suggested to run them in a VM, lxd container or in a test installation): + https://gist.github.com/3v1n0/287d02ca8e03936f1c7bba992173d47a + + - sudo apt install gdm3 pamtester softhsm2 openssl wget sssd gnutls-bin && \ + sudo apt-mark auto gdm3 pamtester softhsm2 openssl wget sssd gnutls-bin + - wget https://gist.github.com/3v1n0/287d02ca8e03936f1c7bba992173d47a/raw/sssd-gdm-smartcard-pam-auth-tester.sh + - sudo sssd-gdm-smartcard-pam-auth-tester.sh + + The script will generate some fake CA authority, issue some + certificates, will install them in some software-based smartcards (using + softhsm2) and test that they work properly to login with gdm-smartcard. + + Using `WAIT` environment variable set (to any value) will make it to + restart gdm at each iteration so that an user can try to access, using + the username that launched the script and the pin of 123456. + [ Regression potential ] Smartcard authentication using custom methods using via a custom configured system nss database may not work anymore. --- ProblemType: BugDistroRelease: Ubuntu 18.04 Package: gdm3 3.28.3-0ubuntu18.04.4
[Desktop-packages] [Bug 2034121] Re: Support goodix fingerprint [27c6:633C]
** Changed in: libfprint (Ubuntu) Status: New => Fix Released ** Also affects: libfprint (Ubuntu Jammy) Importance: Undecided Status: New ** Changed in: libfprint (Ubuntu Jammy) Status: New => Fix Committed -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to libfprint in Ubuntu. https://bugs.launchpad.net/bugs/2034121 Title: Support goodix fingerprint [27c6:633C] Status in OEM Priority Project: New Status in libfprint package in Ubuntu: Fix Released Status in libfprint source package in Jammy: Fix Committed Bug description: [27c6:633C] include in https://salsa.debian.org/ubuntu-dev- team/libfprint/-/commit/96645eaa7ae99a12e08b65e24a8610a3c57a92b3 [Impact] * Support goodix [27c6:633C] fingerprint component. [Test Plan] * Find a machine with this fingerprint device * Launch `settings` and enable `Fingerprint Login` * Enroll finger and then logout * Login system with enrolled finger [Where problems could occur] * The patch add new ids to id_table. Should not affect previous supported device. To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/2034121/+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 2018672] Re: Gnome 44: GDM background configurable with gsettings
** Changed in: gnome-shell (Ubuntu) Status: Confirmed => Fix Committed ** Also affects: gnome-shell (Ubuntu Lunar) Importance: Undecided Status: New -- 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 Committed 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 2024237] Re: gnome-remote-desktop-daemon segfaults on push_queue -> pw_stream_queue_buffer -> on_frame_ready -> grd_thread_dispatch_in_impl -> egl_task_source_dispatch
** Changed in: gnome-remote-desktop (Ubuntu Jammy) Status: New => In Progress ** Changed in: gnome-remote-desktop (Ubuntu Jammy) Assignee: (unassigned) => Marco Trevisan (Treviño) (3v1n0) -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-remote-desktop in Ubuntu. https://bugs.launchpad.net/bugs/2024237 Title: gnome-remote-desktop-daemon segfaults on push_queue -> pw_stream_queue_buffer -> on_frame_ready -> grd_thread_dispatch_in_impl -> egl_task_source_dispatch Status in gnome-remote-desktop package in Ubuntu: Fix Released Status in gnome-remote-desktop source package in Jammy: In Progress Bug description: [ Impact ] GNOME Remote desktop crashes on destruction after a VNC or RDP session [ Test case ] Perform the Basic Test cases at https://wiki.ubuntu.com/DesktopTeam/TestPlans/RemoteDesktop g-r-d should not crash afterwards. https://errors.ubuntu.com/problem/b9db6ccdb84569be427829049e6f135d9777e574 should also not happen anymore. [ Regression Potential ] We may try to use an invalid pointer --- The Ubuntu Error Tracker has been receiving reports about a problem regarding gnome-remote-desktop. This problem was most recently seen with package version 42.7-0ubuntu1, the problem page at https://errors.ubuntu.com/problem/b9db6ccdb84569be427829049e6f135d9777e574 contains more details, including versions of packages affected, stacktrace or traceback, and individual crash reports. If you do not have access to the Ubuntu Error Tracker and are a software developer, you can request it at http://forms.canonical.com/reports/. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-remote-desktop/+bug/2024237/+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
> #7 Help upstream to resolve the s390x endianess issues, so we can re-enable > all tests https://gitlab.freedesktop.org/libinput/libei/-/issues/41 I've done some analisys there of the remaining issue, we should be green soon! -- 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: New Status in mutter package in Ubuntu: New 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
[Desktop-packages] [Bug 2024237] Re: gnome-remote-desktop-daemon segfaults on push_queue -> pw_stream_queue_buffer -> on_frame_ready -> grd_thread_dispatch_in_impl -> egl_task_source_dispatch
** Summary changed: - /usr/libexec/gnome-remote-desktop-daemon:11:push_queue:pw_stream_queue_buffer:on_frame_ready:grd_thread_dispatch_in_impl:egl_task_source_dispatch + gnome-remote-desktop-daemon segfaults on push_queue -> pw_stream_queue_buffer -> on_frame_ready -> grd_thread_dispatch_in_impl -> egl_task_source_dispatch ** Description changed: + [ Impact ] + + GNOME Remote desktop crashes on destruction after a VNC or RDP session + + [ Test case ] + + Perform the Basic Test cases at + https://wiki.ubuntu.com/DesktopTeam/TestPlans/RemoteDesktop + + g-r-d should not crash afterwards. + + https://errors.ubuntu.com/problem/b9db6ccdb84569be427829049e6f135d9777e574 + should also not happen anymore. + + [ Regression Potential ] + + We may try to use an invalid pointer + + --- + The Ubuntu Error Tracker has been receiving reports about a problem regarding gnome-remote-desktop. This problem was most recently seen with package version 42.7-0ubuntu1, the problem page at https://errors.ubuntu.com/problem/b9db6ccdb84569be427829049e6f135d9777e574 contains more details, including versions of packages affected, stacktrace or traceback, and individual crash reports. If you do not have access to the Ubuntu Error Tracker and are a software developer, you can request it at http://forms.canonical.com/reports/. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-remote-desktop in Ubuntu. https://bugs.launchpad.net/bugs/2024237 Title: gnome-remote-desktop-daemon segfaults on push_queue -> pw_stream_queue_buffer -> on_frame_ready -> grd_thread_dispatch_in_impl -> egl_task_source_dispatch Status in gnome-remote-desktop package in Ubuntu: Fix Released Status in gnome-remote-desktop source package in Jammy: New Bug description: [ Impact ] GNOME Remote desktop crashes on destruction after a VNC or RDP session [ Test case ] Perform the Basic Test cases at https://wiki.ubuntu.com/DesktopTeam/TestPlans/RemoteDesktop g-r-d should not crash afterwards. https://errors.ubuntu.com/problem/b9db6ccdb84569be427829049e6f135d9777e574 should also not happen anymore. [ Regression Potential ] We may try to use an invalid pointer --- The Ubuntu Error Tracker has been receiving reports about a problem regarding gnome-remote-desktop. This problem was most recently seen with package version 42.7-0ubuntu1, the problem page at https://errors.ubuntu.com/problem/b9db6ccdb84569be427829049e6f135d9777e574 contains more details, including versions of packages affected, stacktrace or traceback, and individual crash reports. If you do not have access to the Ubuntu Error Tracker and are a software developer, you can request it at http://forms.canonical.com/reports/. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-remote-desktop/+bug/2024237/+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 1966167] Re: Ubuntu Dock icons not clickable at the edge of the screen
** Changed in: gnome-shell-extension-ubuntu-dock (Ubuntu Jammy) Status: Fix Committed => Fix Released -- 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/1966167 Title: Ubuntu Dock icons not clickable at the edge of the screen Status in Dash to dock: New Status in Yaru Theme: New Status in gnome-shell-extension-ubuntu-dock package in Ubuntu: Fix Released Status in yaru-theme package in Ubuntu: Fix Released Status in gnome-shell-extension-ubuntu-dock source package in Jammy: Fix Released Status in yaru-theme source package in Jammy: Fix Released Bug description: [ Impact ] If you go to the bottom left corner of the dock and click, the All Apps button doesn't get triggered or highlighted. Check attached video for details. [ Test case ] For verifying yaru-theme, in the Ubuntu session: 1. Move the pointer to the edge of the screen where the AppIcons button is visible (bottom-left corner by default) 2. The button should be highlighted and clicking it should open the applications grid [ Regression potential ] - The dock margins are wrong or icons are not clickable in their edges - There's no not-reactive space between the activity button and the first icon --- Ubuntu 21.10. Live mode. 1920x1080 screen. To manage notifications about this bug go to: https://bugs.launchpad.net/dash-to-dock/+bug/1966167/+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 1942204] Re: gjs-console assert failure: double free or corruption (out)
*** This bug is a duplicate of bug 2027986 *** https://bugs.launchpad.net/bugs/2027986 ** Changed in: gjs (Ubuntu) Status: Confirmed => Won't Fix ** Also affects: gtk4 (Ubuntu) Importance: Undecided Status: New ** Changed in: gtk4 (Ubuntu) Status: New => Fix Released ** This bug has been marked a duplicate of bug 2027986 gjs-console running Extensions Manager crashes with free(): invalid pointer -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gtk4 in Ubuntu. https://bugs.launchpad.net/bugs/1942204 Title: gjs-console assert failure: double free or corruption (out) Status in gjs package in Ubuntu: Won't Fix Status in gtk4 package in Ubuntu: Fix Released Bug description: https://errors.ubuntu.com/problem/bf1640a188e643438fd2499010e7e2f69faabbd9 --- Changing panel location using Dash to Panel extension. ProblemType: Crash DistroRelease: Ubuntu 21.10 Package: gjs 1.68.1-1 ProcVersionSignature: Ubuntu 5.13.0-14.14-generic 5.13.1 Uname: Linux 5.13.0-14-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.20.11-0ubuntu68 Architecture: amd64 AssertionMessage: double free or corruption (out) CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Tue Aug 31 07:59:18 2021 ExecutablePath: /usr/bin/gjs-console InstallationDate: Installed on 2021-08-30 (1 days ago) InstallationMedia: Ubuntu 21.10 "Impish Indri" - Alpha amd64 (20210829) ProcCmdline: /usr/bin/gjs /usr/share/gnome-shell/org.gnome.Shell.Extensions ProcEnviron: SHELL=/bin/bash XDG_RUNTIME_DIR= PATH=(custom, no user) LANG=en_US.UTF-8 Signal: 6 SourcePackage: gjs StacktraceTop: __libc_message (action=action@entry=do_abort, fmt=fmt@entry=0x7f2dc2538b9c "%s\n") at ../sysdeps/posix/libc_fatal.c:155 malloc_printerr (str=str@entry=0x7f2dc253b0e0 "double free or corruption (out)") at malloc.c:5628 _int_free (av=0x7f2dc256aba0 , p=0x5592189dab70, have_lock=) at malloc.c:4547 __GI___libc_free (mem=) at malloc.c:3309 () at /lib/x86_64-linux-gnu/libgtk-4.so.1 Title: gjs-console assert failure: double free or corruption (out) UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo separator: To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gjs/+bug/1942204/+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 1981678] Re: /usr/bin/gjs-console:double free or corruption (out)
*** This bug is a duplicate of bug 2027986 *** https://bugs.launchpad.net/bugs/2027986 ** This bug is no longer a duplicate of bug 1942204 gjs-console assert failure: double free or corruption (out) ** This bug has been marked a duplicate of bug 2027986 gjs-console running Extensions Manager crashes with free(): invalid pointer -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gjs in Ubuntu. https://bugs.launchpad.net/bugs/1981678 Title: /usr/bin/gjs-console:double free or corruption (out) Status in gjs package in Ubuntu: New Bug description: The Ubuntu Error Tracker has been receiving reports about a problem regarding gjs. This problem was most recently seen with package version 1.72.0-3~ubuntu22.04.2, the problem page at https://errors.ubuntu.com/problem/bf1640a188e643438fd2499010e7e2f69faabbd9 contains more details, including versions of packages affected, stacktrace or traceback, and individual crash reports. If you do not have access to the Ubuntu Error Tracker and are a software developer, you can request it at http://forms.canonical.com/reports/. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gjs/+bug/1981678/+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 2028005] Re: Update gtk4 to 4.6.9
Things works as expected, tested gnome-extensions, portal-test and gnome text editor ❯ apt-cache policy libgtk-4-1 libgtk-4-1: Installed: 4.6.9+ds-0ubuntu0.22.04.1 Candidate: 4.6.9+ds-0ubuntu0.22.04.1 Version table: *** 4.6.9+ds-0ubuntu0.22.04.1 400 400 http://archive.ubuntu.com/ubuntu jammy-proposed/main amd64 Packages 100 /var/lib/dpkg/status 4.6.6+ds-0ubuntu1 500 500 http://archive.ubuntu.com/ubuntu jammy-updates/main amd64 Packages 4.6.2+ds-1ubuntu2 500 500 http://archive.ubuntu.com/ubuntu jammy/main amd64 Packages ** 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 gtk4 in Ubuntu. https://bugs.launchpad.net/bugs/2028005 Title: Update gtk4 to 4.6.9 Status in gtk4 package in Ubuntu: Fix Released Status in gtk4 source package in Jammy: Fix Committed Bug description: Impact -- There is a new point release in the stable GTK 4.6 series. https://gitlab.gnome.org/GNOME/gtk/-/blob/4.6.9/NEWS Test Case 1 --- Make sure that opening and saving files from the Firefox and Chromium snaps still work Test Case 2 --- snap install portal-test snap run portal-test Verify that the app seems to still work ok Test Case 3 --- sudo apt install gnome-shell-extensions-prefs gnome-shell-extensions-prefs GNOME Shell extensions can be configured and managed, the program can run without crashing both during runtime and shutdown. What Could Go Wrong --- Ubuntu includes xdg-desktop-portal-gnome by default which is used for many snap actions like providing a file chooser. This is critical functionality for our snaps. The Ubuntu flavors use a different portal backend, most commonly xdg- desktop-portal-gtk which uses GTK3 so it's not affected by this SRU. The other gtk4 apps installed by default in Ubuntu are gnome-chess and gnome-shell-extension-prefs. gtk4 is part of core GNOME and is in my latest proposed update to the microrelease exception https://wiki.ubuntu.com/StableReleaseUpdates/GNOME https://discourse.ubuntu.com/t/scope-of-gnome-mru/18041/42 gtk4 has extensive build tests and autopkgtests. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gtk4/+bug/2028005/+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 2027986] Re: gjs-console running Extensions Manager crashes with free(): invalid pointer
Tested new version, it works without errors
❯ apt-cache policy libgtk-4-1
libgtk-4-1:
Installed: 4.6.9+ds-0ubuntu0.22.04.1
Candidate: 4.6.9+ds-0ubuntu0.22.04.1
Version table:
*** 4.6.9+ds-0ubuntu0.22.04.1 400
400 http://archive.ubuntu.com/ubuntu jammy-proposed/main amd64 Packages
100 /var/lib/dpkg/status
4.6.6+ds-0ubuntu1 500
500 http://archive.ubuntu.com/ubuntu jammy-updates/main amd64 Packages
4.6.2+ds-1ubuntu2 500
500 http://archive.ubuntu.com/ubuntu jammy/main amd64 Packages
Before upgrading:
❯ gjs -m /tmp/error.js
(gjs:8879): Gjs-CRITICAL **: 10:47:25.041: Attempting to run a JS
callback during garbage collection. This is most likely caused by
destroying a Clutter actor or GTK widget with ::destroy signal
connected, or using the destroy(), dispose(), or remove() vfuncs.
Because it would crash the application, it has been blocked.
(gjs:8879): Gjs-CRITICAL **: 10:47:25.041: The offending callback was
ScaleFormatValueFunc().
== Stack trace for context 0x5634d50d9180 ==
(gjs:8879): Pango-WARNING **: 10:47:25.041: Invalid UTF-8 string passed to
pango_layout_set_text()
free(): invalid pointer
[1]8879 IOT instruction (core dumped) gjs -m /tmp/error.js
marco-ThinkPad-X1-Carbon-7th ~ 8sSIGIOT(6) 10:47:27
❯ apt-cache policy libgtk-4-1
libgtk-4-1:
Installed: 4.6.6+ds-0ubuntu1
Candidate: 4.6.6+ds-0ubuntu1
Version table:
4.6.9+ds-0ubuntu0.22.04.1 400
400 http://archive.ubuntu.com/ubuntu jammy-proposed/main amd64 Packages
*** 4.6.6+ds-0ubuntu1 500
500 http://archive.ubuntu.com/ubuntu jammy-updates/main amd64 Packages
100 /var/lib/dpkg/status
4.6.2+ds-1ubuntu2 500
500 http://archive.ubuntu.com/ubuntu jammy/main amd64 Packages
** 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 gtk4 in Ubuntu.
https://bugs.launchpad.net/bugs/2027986
Title:
gjs-console running Extensions Manager crashes with free(): invalid
pointer
Status in gjs package in Ubuntu:
Won't Fix
Status in gtk4 package in Ubuntu:
Fix Released
Status in gtk4 source package in Jammy:
Fix Committed
Bug description:
[ Impact ]
gnome-shell-extensions-prefs may crash during shutdown because of
wrong memory access:
Jul 14 18:52:30 zerocool gjs[114030]: Attempting to run a JS callback during
garbage collection. This is most likely caused by destroying a Clutter actor or
GTK widget with ::destroy signal connected, or using the destroy(), dispose(),
or remove() vfuncs. Because it would crash the application, it has been blocked.
Jul 14 18:52:30 zerocool gjs[114030]: The offending callback was
ScaleFormatValueFunc().
Jul 14 18:52:30 zerocool org.gnome.Shell.Extensions[114030]: == Stack trace
for context 0x55d05b7f6170 ==
Jul 14 18:52:30 zerocool org.gnome.Shell.Extensions[114030]: #0 55d05b87d5b8
i resource:///org/gnome/Shell/Extensions/js/dbusService.js:186 (3d87eaadaab0 @
257)
Jul 14 18:52:30 zerocool org.gnome.Shell.Extensions[114030]: #1 55d05b87d510
i resource:///org/gnome/Shell/Extensions/js/main.js:22 (3d87eaada4c0 @ 97)
Jul 14 18:52:30 zerocool org.gnome.Shell.Extensions[114030]: #2 55d05b87d478
i resource:///org/gnome/gjs/modules/script/package.js:206 (3d87eaac82e0 @ 45)
Jul 14 18:52:30 zerocool org.gnome.Shell.Extensions[114030]: #3 55d05b87d3f0
i resource:///org/gnome/gjs/modules/script/package.js:190 (3d87eaac8290 @ 37)
Jul 14 18:52:30 zerocool org.gnome.Shell.Extensions[114030]: #4 55d05b87d360
i /usr/share/gnome-shell/org.gnome.Shell.Extensions:1 (3d87eaac80b0 @ 52)
Jul 14 18:52:30 zerocool gjs[114030]: Invalid UTF-8 string passed to
pango_layout_set_text()
Jul 14 18:52:30 zerocool org.gnome.Shell.Extensions[114030]: free(): invalid
pointer
[ Test case ]
1. Add this script to a file (i.e. /tmp/test-gtk.js)
import Gtk from 'gi://Gtk?version=4.0';
const app = new Gtk.Application();
app.connect('activate', () => {
const scale = new Gtk.Scale({drawValue: true});
scale.set_format_value_func(() => '');
new Gtk.Window({application: app, child: scale}).present();
});
app.run([]);
2. Run it via:
gjs -m /tmp/test-gtk.js
A new window should snow
3. Close the window, it should exit normally with no errors.
[ Regression potential ]
None known, the fix
(https://gitlab.gnome.org/GNOME/gtk/-/commit/8b76cc841) only ensures
that we're using the adjustment property if really was used.
---
Other triggers:
7月 17 20:47:01 xsc-Lenovo-R720-15IKBN ubuntu-appindicat...@ubuntu.com[6819]:
unable to update icon for software-update-available
7月 17 20:47:01 xsc-Lenovo-R720-15IKBN ubuntu-appindicat...@ubuntu.com[6819]:
unable to update icon for livepatch
7月 17 20:47:03 xsc-Lenovo-R720-15IKBN gjs[7414]: Attempting to
[Desktop-packages] [Bug 2028005] [NEW] Update gtk4 to 4.6.9
Public bug reported: Impact -- There is a new point release in the stable GTK 4.6 series. https://gitlab.gnome.org/GNOME/gtk/-/blob/4.6.9/NEWS Test Case 1 --- Make sure that opening and saving files from the Firefox and Chromium snaps still work Test Case 2 --- snap install portal-test snap run portal-test Verify that the app seems to still work ok Test Case 3 --- sudo apt install gnome-shell-extensions-prefs gnome-shell-extensions-prefs GNOME Shell extensions can be configured and managed, the program can run without crashing both during runtime and shutdown. What Could Go Wrong --- Ubuntu includes xdg-desktop-portal-gnome by default which is used for many snap actions like providing a file chooser. This is critical functionality for our snaps. The Ubuntu flavors use a different portal backend, most commonly xdg- desktop-portal-gtk which uses GTK3 so it's not affected by this SRU. The other gtk4 apps installed by default in Ubuntu are gnome-chess and gnome-shell-extension-prefs. gtk4 is part of core GNOME and is in my latest proposed update to the microrelease exception https://wiki.ubuntu.com/StableReleaseUpdates/GNOME https://discourse.ubuntu.com/t/scope-of-gnome-mru/18041/42 gtk4 has extensive build tests and autopkgtests. ** Affects: gtk4 (Ubuntu) Importance: Medium Assignee: Marco Trevisan (Treviño) (3v1n0) Status: Fix Released ** Affects: gtk4 (Ubuntu Jammy) Importance: Medium Assignee: Marco Trevisan (Treviño) (3v1n0) Status: In Progress ** Also affects: gtk4 (Ubuntu Jammy) Importance: Undecided Status: New ** Changed in: gtk4 (Ubuntu Jammy) Status: New => In Progress ** Changed in: gtk4 (Ubuntu Jammy) Importance: Undecided => Medium ** Changed in: gtk4 (Ubuntu Jammy) Assignee: (unassigned) => Marco Trevisan (Treviño) (3v1n0) -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gtk4 in Ubuntu. https://bugs.launchpad.net/bugs/2028005 Title: Update gtk4 to 4.6.9 Status in gtk4 package in Ubuntu: Fix Released Status in gtk4 source package in Jammy: In Progress Bug description: Impact -- There is a new point release in the stable GTK 4.6 series. https://gitlab.gnome.org/GNOME/gtk/-/blob/4.6.9/NEWS Test Case 1 --- Make sure that opening and saving files from the Firefox and Chromium snaps still work Test Case 2 --- snap install portal-test snap run portal-test Verify that the app seems to still work ok Test Case 3 --- sudo apt install gnome-shell-extensions-prefs gnome-shell-extensions-prefs GNOME Shell extensions can be configured and managed, the program can run without crashing both during runtime and shutdown. What Could Go Wrong --- Ubuntu includes xdg-desktop-portal-gnome by default which is used for many snap actions like providing a file chooser. This is critical functionality for our snaps. The Ubuntu flavors use a different portal backend, most commonly xdg- desktop-portal-gtk which uses GTK3 so it's not affected by this SRU. The other gtk4 apps installed by default in Ubuntu are gnome-chess and gnome-shell-extension-prefs. gtk4 is part of core GNOME and is in my latest proposed update to the microrelease exception https://wiki.ubuntu.com/StableReleaseUpdates/GNOME https://discourse.ubuntu.com/t/scope-of-gnome-mru/18041/42 gtk4 has extensive build tests and autopkgtests. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gtk4/+bug/2028005/+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 2027986] Re: gjs-console running Extensions Manager crashes with free(): invalid pointer
** Description changed:
- Some JS traces I see are:
+ [ Impact ]
+
+ gnome-shell-extensions-prefs may crash during shutdown because of wrong
+ memory access:
Jul 14 18:52:30 zerocool gjs[114030]: Attempting to run a JS callback during
garbage collection. This is most likely caused by destroying a Clutter actor or
GTK widget with ::destroy signal connected, or using the destroy(), dispose(),
or remove() vfuncs. Because it would crash the application, it has been blocked.
Jul 14 18:52:30 zerocool gjs[114030]: The offending callback was
ScaleFormatValueFunc().
Jul 14 18:52:30 zerocool org.gnome.Shell.Extensions[114030]: == Stack trace
for context 0x55d05b7f6170 ==
Jul 14 18:52:30 zerocool org.gnome.Shell.Extensions[114030]: #0 55d05b87d5b8
i resource:///org/gnome/Shell/Extensions/js/dbusService.js:186 (3d87eaadaab0 @
257)
Jul 14 18:52:30 zerocool org.gnome.Shell.Extensions[114030]: #1 55d05b87d510
i resource:///org/gnome/Shell/Extensions/js/main.js:22 (3d87eaada4c0 @ 97)
Jul 14 18:52:30 zerocool org.gnome.Shell.Extensions[114030]: #2 55d05b87d478
i resource:///org/gnome/gjs/modules/script/package.js:206 (3d87eaac82e0 @ 45)
Jul 14 18:52:30 zerocool org.gnome.Shell.Extensions[114030]: #3 55d05b87d3f0
i resource:///org/gnome/gjs/modules/script/package.js:190 (3d87eaac8290 @ 37)
Jul 14 18:52:30 zerocool org.gnome.Shell.Extensions[114030]: #4 55d05b87d360
i /usr/share/gnome-shell/org.gnome.Shell.Extensions:1 (3d87eaac80b0 @ 52)
Jul 14 18:52:30 zerocool gjs[114030]: Invalid UTF-8 string passed to
pango_layout_set_text()
Jul 14 18:52:30 zerocool org.gnome.Shell.Extensions[114030]: free(): invalid
pointer
- ---
+
+ [ Test case ]
+
+ 1. Add this script to a file (i.e. /tmp/test-gtk.js)
+
+ import Gtk from 'gi://Gtk?version=4.0';
+ const app = new Gtk.Application();
+ app.connect('activate', () => {
+ const scale = new Gtk.Scale({drawValue: true});
+ scale.set_format_value_func(() => '');
+ new Gtk.Window({application: app, child: scale}).present();
+ });
+ app.run([]);
+
+
+ 2. Run it via:
+
+ gjs -m /tmp/test-gtk.js
+
+ A new window should snow
+
+ 3. Close the window, it should exit normally with no errors.
+
+
+ [ Regression potential ]
+
+ None known, the fix
+ (https://gitlab.gnome.org/GNOME/gtk/-/commit/8b76cc841) only ensures
+ that we're using the adjustment property if really was used.
+
+
+ ---
+
+ Other triggers:
7月 17 20:47:01 xsc-Lenovo-R720-15IKBN ubuntu-appindicat...@ubuntu.com[6819]:
unable to update icon for software-update-available
7月 17 20:47:01 xsc-Lenovo-R720-15IKBN ubuntu-appindicat...@ubuntu.com[6819]:
unable to update icon for livepatch
7月 17 20:47:03 xsc-Lenovo-R720-15IKBN gjs[7414]: Attempting to run a JS
callback during garbage collection. This is most likely caused by destroying a
Clutter actor or GTK widget with ::destroy signal connected, or using the
destroy(), dispose(), or remove() vfuncs. Because it would crash the
application, it has been blocked.
7月 17 20:47:03 xsc-Lenovo-R720-15IKBN gjs[7414]: The offending callback was
ScaleFormatValueFunc().
7月 17 20:47:03 xsc-Lenovo-R720-15IKBN org.gnome.Shell.Extensions[7414]: ==
Stack trace for context 0x55674f538170 ==
7月 17 20:47:03 xsc-Lenovo-R720-15IKBN org.gnome.Shell.Extensions[7414]: #0
55674f5c27f8 i resource:///org/gnome/Shell/Extensions/js/dbusService.js:186
(330fd64daab0 @ 257)
7月 17 20:47:03 xsc-Lenovo-R720-15IKBN org.gnome.Shell.Extensions[7414]: #1
55674f5c2750 i resource:///org/gnome/Shell/Extensions/js/main.js:22
(330fd64da4c0 @ 97)
7月 17 20:47:03 xsc-Lenovo-R720-15IKBN org.gnome.Shell.Extensions[7414]: #2
55674f5c26b8 i resource:///org/gnome/gjs/modules/script/package.js:206
(330fd64c82e0 @ 45)
7月 17 20:47:03 xsc-Lenovo-R720-15IKBN org.gnome.Shell.Extensions[7414]: #3
55674f5c2630 i resource:///org/gnome/gjs/modules/script/package.js:190
(330fd64c8290 @ 37)
7月 17 20:47:03 xsc-Lenovo-R720-15IKBN org.gnome.Shell.Extensions[7414]: #4
55674f5c25a0 i /usr/share/gnome-shell/org.gnome.Shell.Extensions:1
(330fd64c80b0 @ 52)
7月 17 20:47:03 xsc-Lenovo-R720-15IKBN gjs[7414]: Invalid UTF-8 string passed
to pango_layout_set_text()
- 7月 17 20:47:03 xsc-Lenovo-R720-15IKBN org.gnome.Shell.Extensions[7414]:
free(): invalid pointer
+ 7月 17 20:47:03 xsc-Lenovo-R720-15IKBN org.gnome.Shell.Extensions[7414]:
free(): invalid pointer
---
The Ubuntu Error Tracker has been receiving reports about a problem regarding
gjs. This problem was most recently seen with package version 1.74.0-1, the
problem page at
https://errors.ubuntu.com/problem/2c4ff471793184d6a5b3a47cee9dcbe517920a3a
contains more details, including versions of packages affected, stacktrace or
traceback, and individual crash reports.
If you do not have access to the Ubuntu Error Tracker and are a software
developer, you can request it at http://forms.canonical.com/reports/.
--
You received this bug notification because you are a member of Desktop
[Desktop-packages] [Bug 2027986] Re: gjs-console running Extensions Manager crashes with free(): invalid pointer
As per further analysis it seems that this bug has always been there in
42 series, however the traces are normally caused by some extensions
settings, for example:
- https://github.com/micheleg/dash-to-dock/issues/1743
- https://github.com/home-sweet-gnome/dash-to-panel/issues/1783
While something like this had already been fixed for some cases in GLib
(included in 1.72, part of gnome 42 and so jammy):
https://gitlab.gnome.org/GNOME/gjs/-/issues/445
The has been found in gtk, though. And fixed by
https://gitlab.gnome.org/GNOME/gtk/-/merge_requests/5061
** Bug watch added: github.com/micheleg/dash-to-dock/issues #1743
https://github.com/micheleg/dash-to-dock/issues/1743
** Bug watch added: github.com/home-sweet-gnome/dash-to-panel/issues #1783
https://github.com/home-sweet-gnome/dash-to-panel/issues/1783
** Bug watch added: gitlab.gnome.org/GNOME/gjs/-/issues #445
https://gitlab.gnome.org/GNOME/gjs/-/issues/445
** Changed in: gtk4 (Ubuntu)
Status: Triaged => Fix Released
** Changed in: gtk4 (Ubuntu)
Importance: Undecided => High
** Changed in: gtk4 (Ubuntu)
Assignee: (unassigned) => Marco Trevisan (Treviño) (3v1n0)
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to gtk4 in Ubuntu.
https://bugs.launchpad.net/bugs/2027986
Title:
gjs-console running Extensions Manager crashes with free(): invalid
pointer
Status in gjs package in Ubuntu:
Won't Fix
Status in gtk4 package in Ubuntu:
Fix Released
Status in gtk4 source package in Jammy:
In Progress
Bug description:
[ Impact ]
gnome-shell-extensions-prefs may crash during shutdown because of
wrong memory access:
Jul 14 18:52:30 zerocool gjs[114030]: Attempting to run a JS callback during
garbage collection. This is most likely caused by destroying a Clutter actor or
GTK widget with ::destroy signal connected, or using the destroy(), dispose(),
or remove() vfuncs. Because it would crash the application, it has been blocked.
Jul 14 18:52:30 zerocool gjs[114030]: The offending callback was
ScaleFormatValueFunc().
Jul 14 18:52:30 zerocool org.gnome.Shell.Extensions[114030]: == Stack trace
for context 0x55d05b7f6170 ==
Jul 14 18:52:30 zerocool org.gnome.Shell.Extensions[114030]: #0 55d05b87d5b8
i resource:///org/gnome/Shell/Extensions/js/dbusService.js:186 (3d87eaadaab0 @
257)
Jul 14 18:52:30 zerocool org.gnome.Shell.Extensions[114030]: #1 55d05b87d510
i resource:///org/gnome/Shell/Extensions/js/main.js:22 (3d87eaada4c0 @ 97)
Jul 14 18:52:30 zerocool org.gnome.Shell.Extensions[114030]: #2 55d05b87d478
i resource:///org/gnome/gjs/modules/script/package.js:206 (3d87eaac82e0 @ 45)
Jul 14 18:52:30 zerocool org.gnome.Shell.Extensions[114030]: #3 55d05b87d3f0
i resource:///org/gnome/gjs/modules/script/package.js:190 (3d87eaac8290 @ 37)
Jul 14 18:52:30 zerocool org.gnome.Shell.Extensions[114030]: #4 55d05b87d360
i /usr/share/gnome-shell/org.gnome.Shell.Extensions:1 (3d87eaac80b0 @ 52)
Jul 14 18:52:30 zerocool gjs[114030]: Invalid UTF-8 string passed to
pango_layout_set_text()
Jul 14 18:52:30 zerocool org.gnome.Shell.Extensions[114030]: free(): invalid
pointer
[ Test case ]
1. Add this script to a file (i.e. /tmp/test-gtk.js)
import Gtk from 'gi://Gtk?version=4.0';
const app = new Gtk.Application();
app.connect('activate', () => {
const scale = new Gtk.Scale({drawValue: true});
scale.set_format_value_func(() => '');
new Gtk.Window({application: app, child: scale}).present();
});
app.run([]);
2. Run it via:
gjs -m /tmp/test-gtk.js
A new window should snow
3. Close the window, it should exit normally with no errors.
[ Regression potential ]
None known, the fix
(https://gitlab.gnome.org/GNOME/gtk/-/commit/8b76cc841) only ensures
that we're using the adjustment property if really was used.
---
Other triggers:
7月 17 20:47:01 xsc-Lenovo-R720-15IKBN ubuntu-appindicat...@ubuntu.com[6819]:
unable to update icon for software-update-available
7月 17 20:47:01 xsc-Lenovo-R720-15IKBN ubuntu-appindicat...@ubuntu.com[6819]:
unable to update icon for livepatch
7月 17 20:47:03 xsc-Lenovo-R720-15IKBN gjs[7414]: Attempting to run a JS
callback during garbage collection. This is most likely caused by destroying a
Clutter actor or GTK widget with ::destroy signal connected, or using the
destroy(), dispose(), or remove() vfuncs. Because it would crash the
application, it has been blocked.
7月 17 20:47:03 xsc-Lenovo-R720-15IKBN gjs[7414]: The offending callback was
ScaleFormatValueFunc().
7月 17 20:47:03 xsc-Lenovo-R720-15IKBN org.gnome.Shell.Extensions[7414]: ==
Stack trace for context 0x55674f538170 ==
7月 17 20:47:03 xsc-Lenovo-R720-15IKBN org.gnome.Shell.Extensions[7414]: #0
55674f5c27f8 i resource:///org/gnome/Shell/Extensions/js/dbusService.js:186
(330fd64daab0 @ 257)
7月 17 20:47:03 xsc-Lenovo-R720-15IKBN org.gnome.Shell.Exten
[Desktop-packages] [Bug 2027986] Re: gjs-console running Extensions Manager crashes with free(): invalid pointer
** Changed in: gjs (Ubuntu) Status: Triaged => Won't Fix ** Also affects: gtk4 (Ubuntu) Importance: Undecided Status: New ** Changed in: gtk4 (Ubuntu) Status: New => Triaged ** Also affects: gjs (Ubuntu Jammy) Importance: Undecided Status: New ** Also affects: gtk4 (Ubuntu Jammy) Importance: Undecided Status: New ** No longer affects: gjs (Ubuntu Jammy) ** Changed in: gtk4 (Ubuntu Jammy) Status: New => In Progress -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gtk4 in Ubuntu. https://bugs.launchpad.net/bugs/2027986 Title: gjs-console running Extensions Manager crashes with free(): invalid pointer Status in gjs package in Ubuntu: Won't Fix Status in gtk4 package in Ubuntu: Fix Released Status in gtk4 source package in Jammy: In Progress Bug description: Some JS traces I see are: Jul 14 18:52:30 zerocool gjs[114030]: Attempting to run a JS callback during garbage collection. This is most likely caused by destroying a Clutter actor or GTK widget with ::destroy signal connected, or using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked. Jul 14 18:52:30 zerocool gjs[114030]: The offending callback was ScaleFormatValueFunc(). Jul 14 18:52:30 zerocool org.gnome.Shell.Extensions[114030]: == Stack trace for context 0x55d05b7f6170 == Jul 14 18:52:30 zerocool org.gnome.Shell.Extensions[114030]: #0 55d05b87d5b8 i resource:///org/gnome/Shell/Extensions/js/dbusService.js:186 (3d87eaadaab0 @ 257) Jul 14 18:52:30 zerocool org.gnome.Shell.Extensions[114030]: #1 55d05b87d510 i resource:///org/gnome/Shell/Extensions/js/main.js:22 (3d87eaada4c0 @ 97) Jul 14 18:52:30 zerocool org.gnome.Shell.Extensions[114030]: #2 55d05b87d478 i resource:///org/gnome/gjs/modules/script/package.js:206 (3d87eaac82e0 @ 45) Jul 14 18:52:30 zerocool org.gnome.Shell.Extensions[114030]: #3 55d05b87d3f0 i resource:///org/gnome/gjs/modules/script/package.js:190 (3d87eaac8290 @ 37) Jul 14 18:52:30 zerocool org.gnome.Shell.Extensions[114030]: #4 55d05b87d360 i /usr/share/gnome-shell/org.gnome.Shell.Extensions:1 (3d87eaac80b0 @ 52) Jul 14 18:52:30 zerocool gjs[114030]: Invalid UTF-8 string passed to pango_layout_set_text() Jul 14 18:52:30 zerocool org.gnome.Shell.Extensions[114030]: free(): invalid pointer --- 7月 17 20:47:01 xsc-Lenovo-R720-15IKBN ubuntu-appindicat...@ubuntu.com[6819]: unable to update icon for software-update-available 7月 17 20:47:01 xsc-Lenovo-R720-15IKBN ubuntu-appindicat...@ubuntu.com[6819]: unable to update icon for livepatch 7月 17 20:47:03 xsc-Lenovo-R720-15IKBN gjs[7414]: Attempting to run a JS callback during garbage collection. This is most likely caused by destroying a Clutter actor or GTK widget with ::destroy signal connected, or using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked. 7月 17 20:47:03 xsc-Lenovo-R720-15IKBN gjs[7414]: The offending callback was ScaleFormatValueFunc(). 7月 17 20:47:03 xsc-Lenovo-R720-15IKBN org.gnome.Shell.Extensions[7414]: == Stack trace for context 0x55674f538170 == 7月 17 20:47:03 xsc-Lenovo-R720-15IKBN org.gnome.Shell.Extensions[7414]: #0 55674f5c27f8 i resource:///org/gnome/Shell/Extensions/js/dbusService.js:186 (330fd64daab0 @ 257) 7月 17 20:47:03 xsc-Lenovo-R720-15IKBN org.gnome.Shell.Extensions[7414]: #1 55674f5c2750 i resource:///org/gnome/Shell/Extensions/js/main.js:22 (330fd64da4c0 @ 97) 7月 17 20:47:03 xsc-Lenovo-R720-15IKBN org.gnome.Shell.Extensions[7414]: #2 55674f5c26b8 i resource:///org/gnome/gjs/modules/script/package.js:206 (330fd64c82e0 @ 45) 7月 17 20:47:03 xsc-Lenovo-R720-15IKBN org.gnome.Shell.Extensions[7414]: #3 55674f5c2630 i resource:///org/gnome/gjs/modules/script/package.js:190 (330fd64c8290 @ 37) 7月 17 20:47:03 xsc-Lenovo-R720-15IKBN org.gnome.Shell.Extensions[7414]: #4 55674f5c25a0 i /usr/share/gnome-shell/org.gnome.Shell.Extensions:1 (330fd64c80b0 @ 52) 7月 17 20:47:03 xsc-Lenovo-R720-15IKBN gjs[7414]: Invalid UTF-8 string passed to pango_layout_set_text() 7月 17 20:47:03 xsc-Lenovo-R720-15IKBN org.gnome.Shell.Extensions[7414]: free(): invalid pointer --- The Ubuntu Error Tracker has been receiving reports about a problem regarding gjs. This problem was most recently seen with package version 1.74.0-1, the problem page at https://errors.ubuntu.com/problem/2c4ff471793184d6a5b3a47cee9dcbe517920a3a contains more details, including versions of packages affected, stacktrace or traceback, and individual crash reports. If you do not have access to the Ubuntu Error Tracker and are a software developer, you can request it at http://forms.canonical.com/reports/. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gjs/+bug/2027986/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages
[Desktop-packages] [Bug 2024240] Re: [rdp] gnome-remote-desktop-daemon crashes in push_queue -> pw_stream_queue_buffer -> on_frame_ready -> process_frame_data -> impl_node_process_input
In 10 days in proposed no error has been recorded in https://errors.ubuntu.com/problem/11f28bb1ebb12472ffcc6dfe3e664af697e8a47a for the version: 42.9-0ubuntu0.22.04.1 ** 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 gnome-remote-desktop in Ubuntu. https://bugs.launchpad.net/bugs/2024240 Title: [rdp] gnome-remote-desktop-daemon crashes in push_queue -> pw_stream_queue_buffer -> on_frame_ready -> process_frame_data -> impl_node_process_input Status in gnome-remote-desktop package in Ubuntu: Fix Released Status in gnome-remote-desktop source package in Jammy: Fix Committed Bug description: [ Test case ] Check that remote desktop work fine in both RDP and VNC modes. --- The Ubuntu Error Tracker has been receiving reports about a problem regarding gnome-remote-desktop. This problem was most recently seen with package version 42.7-0ubuntu1, the problem page at https://errors.ubuntu.com/problem/11f28bb1ebb12472ffcc6dfe3e664af697e8a47a contains more details, including versions of packages affected, stacktrace or traceback, and individual crash reports. If you do not have access to the Ubuntu Error Tracker and are a software developer, you can request it at http://forms.canonical.com/reports/. Related to https://bugs.launchpad.net/ubuntu/+source/gnome-remote- desktop/+bug/2024238 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-remote-desktop/+bug/2024240/+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 2024238] Re: [vnc] gnome-remote-desktop-daemon crashes on -> push_queue -> pw_stream_queue_buffer -> on_frame_ready -> download_in_impl -> grd_thread_dispatch_in_impl
In 10 days in proposed no error has been recorded in https://errors.ubuntu.com/problem/e097eda971e1f65f9170b00258037980eee90aca for the version: 42.9-0ubuntu0.22.04.1 ** Tags removed: verification-needed ** Tags added: verification-done ** Tags removed: verification-needed-jammy ** Tags added: verification-done-jammy -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-remote-desktop in Ubuntu. https://bugs.launchpad.net/bugs/2024238 Title: [vnc] gnome-remote-desktop-daemon crashes on -> push_queue -> pw_stream_queue_buffer -> on_frame_ready -> download_in_impl -> grd_thread_dispatch_in_impl Status in gnome-remote-desktop package in Ubuntu: Fix Released Status in gnome-remote-desktop source package in Jammy: Fix Committed Bug description: The Ubuntu Error Tracker has been receiving reports about a problem regarding gnome-remote-desktop. This problem was most recently seen with package version 42.7-0ubuntu1, the problem page at https://errors.ubuntu.com/problem/e097eda971e1f65f9170b00258037980eee90aca contains more details, including versions of packages affected, stacktrace or traceback, and individual crash reports. If you do not have access to the Ubuntu Error Tracker and are a software developer, you can request it at http://forms.canonical.com/reports/. Related to https://bugs.launchpad.net/ubuntu/+source/gnome-remote- desktop/+bug/2024240 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-remote-desktop/+bug/2024238/+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 2027986] Re: gjs-console running Extensions Manager crashes with free(): invalid pointer
** Changed in: gjs (Ubuntu) Status: New => Triaged -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gjs in Ubuntu. https://bugs.launchpad.net/bugs/2027986 Title: gjs-console running Extensions Manager crashes with free(): invalid pointer Status in gjs package in Ubuntu: Triaged Bug description: Some JS traces I see are: Jul 14 18:52:30 zerocool gjs[114030]: Attempting to run a JS callback during garbage collection. This is most likely caused by destroying a Clutter actor or GTK widget with ::destroy signal connected, or using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked. Jul 14 18:52:30 zerocool gjs[114030]: The offending callback was ScaleFormatValueFunc(). Jul 14 18:52:30 zerocool org.gnome.Shell.Extensions[114030]: == Stack trace for context 0x55d05b7f6170 == Jul 14 18:52:30 zerocool org.gnome.Shell.Extensions[114030]: #0 55d05b87d5b8 i resource:///org/gnome/Shell/Extensions/js/dbusService.js:186 (3d87eaadaab0 @ 257) Jul 14 18:52:30 zerocool org.gnome.Shell.Extensions[114030]: #1 55d05b87d510 i resource:///org/gnome/Shell/Extensions/js/main.js:22 (3d87eaada4c0 @ 97) Jul 14 18:52:30 zerocool org.gnome.Shell.Extensions[114030]: #2 55d05b87d478 i resource:///org/gnome/gjs/modules/script/package.js:206 (3d87eaac82e0 @ 45) Jul 14 18:52:30 zerocool org.gnome.Shell.Extensions[114030]: #3 55d05b87d3f0 i resource:///org/gnome/gjs/modules/script/package.js:190 (3d87eaac8290 @ 37) Jul 14 18:52:30 zerocool org.gnome.Shell.Extensions[114030]: #4 55d05b87d360 i /usr/share/gnome-shell/org.gnome.Shell.Extensions:1 (3d87eaac80b0 @ 52) Jul 14 18:52:30 zerocool gjs[114030]: Invalid UTF-8 string passed to pango_layout_set_text() Jul 14 18:52:30 zerocool org.gnome.Shell.Extensions[114030]: free(): invalid pointer --- 7月 17 20:47:01 xsc-Lenovo-R720-15IKBN ubuntu-appindicat...@ubuntu.com[6819]: unable to update icon for software-update-available 7月 17 20:47:01 xsc-Lenovo-R720-15IKBN ubuntu-appindicat...@ubuntu.com[6819]: unable to update icon for livepatch 7月 17 20:47:03 xsc-Lenovo-R720-15IKBN gjs[7414]: Attempting to run a JS callback during garbage collection. This is most likely caused by destroying a Clutter actor or GTK widget with ::destroy signal connected, or using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked. 7月 17 20:47:03 xsc-Lenovo-R720-15IKBN gjs[7414]: The offending callback was ScaleFormatValueFunc(). 7月 17 20:47:03 xsc-Lenovo-R720-15IKBN org.gnome.Shell.Extensions[7414]: == Stack trace for context 0x55674f538170 == 7月 17 20:47:03 xsc-Lenovo-R720-15IKBN org.gnome.Shell.Extensions[7414]: #0 55674f5c27f8 i resource:///org/gnome/Shell/Extensions/js/dbusService.js:186 (330fd64daab0 @ 257) 7月 17 20:47:03 xsc-Lenovo-R720-15IKBN org.gnome.Shell.Extensions[7414]: #1 55674f5c2750 i resource:///org/gnome/Shell/Extensions/js/main.js:22 (330fd64da4c0 @ 97) 7月 17 20:47:03 xsc-Lenovo-R720-15IKBN org.gnome.Shell.Extensions[7414]: #2 55674f5c26b8 i resource:///org/gnome/gjs/modules/script/package.js:206 (330fd64c82e0 @ 45) 7月 17 20:47:03 xsc-Lenovo-R720-15IKBN org.gnome.Shell.Extensions[7414]: #3 55674f5c2630 i resource:///org/gnome/gjs/modules/script/package.js:190 (330fd64c8290 @ 37) 7月 17 20:47:03 xsc-Lenovo-R720-15IKBN org.gnome.Shell.Extensions[7414]: #4 55674f5c25a0 i /usr/share/gnome-shell/org.gnome.Shell.Extensions:1 (330fd64c80b0 @ 52) 7月 17 20:47:03 xsc-Lenovo-R720-15IKBN gjs[7414]: Invalid UTF-8 string passed to pango_layout_set_text() 7月 17 20:47:03 xsc-Lenovo-R720-15IKBN org.gnome.Shell.Extensions[7414]: free(): invalid pointer --- The Ubuntu Error Tracker has been receiving reports about a problem regarding gjs. This problem was most recently seen with package version 1.74.0-1, the problem page at https://errors.ubuntu.com/problem/2c4ff471793184d6a5b3a47cee9dcbe517920a3a contains more details, including versions of packages affected, stacktrace or traceback, and individual crash reports. If you do not have access to the Ubuntu Error Tracker and are a software developer, you can request it at http://forms.canonical.com/reports/. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gjs/+bug/2027986/+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 1991709] Re: gnome-shell memory leak (when Ubuntu AppIndicators is enabled)
** Changed in: gnome-shell (Ubuntu) Status: Confirmed => Won't Fix ** Changed in: gnome-shell (Ubuntu Jammy) Status: Confirmed => Won't Fix ** Changed in: gjs (Ubuntu Jammy) Status: Confirmed => Fix Released -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-shell-extension-appindicator in Ubuntu. https://bugs.launchpad.net/bugs/1991709 Title: gnome-shell memory leak (when Ubuntu AppIndicators is enabled) Status in GNOME Shell: New Status in Ubuntu AppIndicators: New Status in GNOME Software: New Status in Open Weather Map: New Status in gjs package in Ubuntu: Fix Released Status in gnome-shell package in Ubuntu: Won't Fix Status in gnome-shell-extension-appindicator package in Ubuntu: Fix Released Status in gjs source package in Jammy: Fix Released Status in gnome-shell source package in Jammy: Won't Fix Status in gnome-shell-extension-appindicator source package in Jammy: Confirmed Bug description: over day gnome-shell memory usage increase to 1GB and more. I have 2 enabled extensions: gnome-extensions list --enabled ubuntu-appindicat...@ubuntu.com ubuntu-d...@ubuntu.com other info: lsb_release -rd Description: Ubuntu 22.04.1 LTS Release: 22.04 ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: gnome-shell 42.4-0ubuntu0.22.04.1 ProcVersionSignature: Ubuntu 5.15.0-48.54-generic 5.15.53 Uname: Linux 5.15.0-48-generic x86_64 ApportVersion: 2.20.11-0ubuntu82.1 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Tue Oct 4 22:35:24 2022 DisplayManager: gdm3 InstallationDate: Installed on 2022-07-03 (93 days ago) InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Release amd64 (20220419) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash RelatedPackageVersions: mutter-common 42.2-0ubuntu1 SourcePackage: gnome-shell UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-shell/+bug/1991709/+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 2027986] Re: /usr/bin/gjs-console:free(): invalid pointer
This doesn't seems something easy to understand, because `org.gnome.Shell.Extensions` could be loading *ANY* kind of javascript code that is imported from gnome extensions. Some of this code is definitely setting a wrong pango text, and gjs thus doesn't free it properly. It could be also an issue due to wrong JS-string -> C-string mapping in gjs but it's very hard to reproduce for me. ** Description changed: + Some JS traces I see are: + + + Jul 14 18:52:30 zerocool gjs[114030]: Attempting to run a JS callback during garbage collection. This is most likely caused by destroying a Clutter actor or GTK widget with ::destroy signal connected, or using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked. + Jul 14 18:52:30 zerocool gjs[114030]: The offending callback was ScaleFormatValueFunc(). + Jul 14 18:52:30 zerocool org.gnome.Shell.Extensions[114030]: == Stack trace for context 0x55d05b7f6170 == + Jul 14 18:52:30 zerocool org.gnome.Shell.Extensions[114030]: #0 55d05b87d5b8 i resource:///org/gnome/Shell/Extensions/js/dbusService.js:186 (3d87eaadaab0 @ 257) + Jul 14 18:52:30 zerocool org.gnome.Shell.Extensions[114030]: #1 55d05b87d510 i resource:///org/gnome/Shell/Extensions/js/main.js:22 (3d87eaada4c0 @ 97) + Jul 14 18:52:30 zerocool org.gnome.Shell.Extensions[114030]: #2 55d05b87d478 i resource:///org/gnome/gjs/modules/script/package.js:206 (3d87eaac82e0 @ 45) + Jul 14 18:52:30 zerocool org.gnome.Shell.Extensions[114030]: #3 55d05b87d3f0 i resource:///org/gnome/gjs/modules/script/package.js:190 (3d87eaac8290 @ 37) + Jul 14 18:52:30 zerocool org.gnome.Shell.Extensions[114030]: #4 55d05b87d360 i /usr/share/gnome-shell/org.gnome.Shell.Extensions:1 (3d87eaac80b0 @ 52) + Jul 14 18:52:30 zerocool gjs[114030]: Invalid UTF-8 string passed to pango_layout_set_text() + Jul 14 18:52:30 zerocool org.gnome.Shell.Extensions[114030]: free(): invalid pointer + + --- + The Ubuntu Error Tracker has been receiving reports about a problem regarding gjs. This problem was most recently seen with package version 1.74.0-1, the problem page at https://errors.ubuntu.com/problem/2c4ff471793184d6a5b3a47cee9dcbe517920a3a contains more details, including versions of packages affected, stacktrace or traceback, and individual crash reports. If you do not have access to the Ubuntu Error Tracker and are a software developer, you can request it at http://forms.canonical.com/reports/. ** Summary changed: - /usr/bin/gjs-console:free(): invalid pointer + gjs-console crashes with free(): invalid pointer ** Description changed: Some JS traces I see are: - Jul 14 18:52:30 zerocool gjs[114030]: Attempting to run a JS callback during garbage collection. This is most likely caused by destroying a Clutter actor or GTK widget with ::destroy signal connected, or using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked. Jul 14 18:52:30 zerocool gjs[114030]: The offending callback was ScaleFormatValueFunc(). Jul 14 18:52:30 zerocool org.gnome.Shell.Extensions[114030]: == Stack trace for context 0x55d05b7f6170 == Jul 14 18:52:30 zerocool org.gnome.Shell.Extensions[114030]: #0 55d05b87d5b8 i resource:///org/gnome/Shell/Extensions/js/dbusService.js:186 (3d87eaadaab0 @ 257) Jul 14 18:52:30 zerocool org.gnome.Shell.Extensions[114030]: #1 55d05b87d510 i resource:///org/gnome/Shell/Extensions/js/main.js:22 (3d87eaada4c0 @ 97) Jul 14 18:52:30 zerocool org.gnome.Shell.Extensions[114030]: #2 55d05b87d478 i resource:///org/gnome/gjs/modules/script/package.js:206 (3d87eaac82e0 @ 45) Jul 14 18:52:30 zerocool org.gnome.Shell.Extensions[114030]: #3 55d05b87d3f0 i resource:///org/gnome/gjs/modules/script/package.js:190 (3d87eaac8290 @ 37) Jul 14 18:52:30 zerocool org.gnome.Shell.Extensions[114030]: #4 55d05b87d360 i /usr/share/gnome-shell/org.gnome.Shell.Extensions:1 (3d87eaac80b0 @ 52) Jul 14 18:52:30 zerocool gjs[114030]: Invalid UTF-8 string passed to pango_layout_set_text() Jul 14 18:52:30 zerocool org.gnome.Shell.Extensions[114030]: free(): invalid pointer --- + 7月 17 20:47:01 xsc-Lenovo-R720-15IKBN ubuntu-appindicat...@ubuntu.com[6819]: unable to update icon for software-update-available + 7月 17 20:47:01 xsc-Lenovo-R720-15IKBN ubuntu-appindicat...@ubuntu.com[6819]: unable to update icon for livepatch + 7月 17 20:47:03 xsc-Lenovo-R720-15IKBN gjs[7414]: Attempting to run a JS callback during garbage collection. This is most likely caused by destroying a Clutter actor or GTK widget with ::destroy signal connected, or using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked. + 7月 17 20:47:03 xsc-Lenovo-R720-15IKBN gjs[7414]: The offending callback was ScaleFormatValueFunc(). + 7月 17 20:47:03 xsc-Lenovo-R720-15IKBN org.gnome.Shell.Extensions[7414]: == Stack trace for context 0x55674f538170 == + 7月 17
[Desktop-packages] [Bug 2024248] Re: Update gnome-remote-desktop to 42.9
** 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 gnome-remote-desktop in Ubuntu. https://bugs.launchpad.net/bugs/2024248 Title: Update gnome-remote-desktop to 42.9 Status in gnome-remote-desktop package in Ubuntu: Fix Released Status in gnome-remote-desktop source package in Jammy: Fix Committed Bug description: Impact -- This is a new stable release in the GNOME 42 series It backports fixes for some crashes reported to errors.ubuntu.com Changes since the current Ubuntu 22.04 LTS release: https://gitlab.gnome.org/GNOME/gnome-remote-desktop/-/compare/42.7...42.9 Test Cases -- Complete all the test cases from https://wiki.ubuntu.com/DesktopTeam/TestPlans/RemoteDesktop except for the "New Audio Forwarding Feature" test case. What Could Go Wrong --- RDP Sharing is a new feature for Ubuntu 22.04 LTS as part of GNOME 42. (Previously only VNC Sharing was offered.) RDP Sharing can be used for providing remote support so it's important that this feature works well because it may be difficult for the remote admin to fix issues in person. gnome-remote-desktop is part of GNOME Core and falls under the GNOME Stable Release Update microrelease exception https://wiki.ubuntu.com/StableReleaseUpdates/GNOME Other Info -- The previous 22.04 LTS SRU, 42.7-0ubuntu1, got stuck in phased updates. We worked with upstream to do a new 42 release in hopes that this update along with the SRU for mutter 42.9 (LP: #1998286) will significantly improve the error rate. 42.7-0ubuntu1 was included in Ubuntu Desktop 22.04.2 so many users already have that version from the original install or got it before phasing was halted. https://ubuntu-archive-team.ubuntu.com/phased-updates.html To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-remote-desktop/+bug/2024248/+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 1966167] Re: Ubuntu Dock icons not clickable at the edge of the screen
No, yaru changes are enough for Ubuntu. Different story is for the gnome session if one uses the dock provided by the package. -- 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/1966167 Title: Ubuntu Dock icons not clickable at the edge of the screen Status in Dash to dock: New Status in Yaru Theme: New Status in gnome-shell-extension-ubuntu-dock package in Ubuntu: Fix Released Status in yaru-theme package in Ubuntu: Fix Released Status in gnome-shell-extension-ubuntu-dock source package in Jammy: Fix Committed Status in yaru-theme source package in Jammy: Fix Committed Bug description: [ Impact ] If you go to the bottom left corner of the dock and click, the All Apps button doesn't get triggered or highlighted. Check attached video for details. [ Test case ] For verifying yaru-theme, in the Ubuntu session: 1. Move the pointer to the edge of the screen where the AppIcons button is visible (bottom-left corner by default) 2. The button should be highlighted and clicking it should open the applications grid [ Regression potential ] - The dock margins are wrong or icons are not clickable in their edges - There's no not-reactive space between the activity button and the first icon --- Ubuntu 21.10. Live mode. 1920x1080 screen. To manage notifications about this bug go to: https://bugs.launchpad.net/dash-to-dock/+bug/1966167/+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 2024248] Re: Update gnome-remote-desktop to 42.9
** Summary changed: - Update gnome-remote-desktop to 42.8 + Update gnome-remote-desktop to 42.9 ** Description changed: Impact -- This is a new stable release in the GNOME 42 series It backports fixes for some crashes reported to errors.ubuntu.com Changes since the current Ubuntu 22.04 LTS release: - https://gitlab.gnome.org/GNOME/gnome-remote-desktop/-/compare/42.7...42.8 + https://gitlab.gnome.org/GNOME/gnome-remote-desktop/-/compare/42.7...42.9 Test Cases -- Complete all the test cases from https://wiki.ubuntu.com/DesktopTeam/TestPlans/RemoteDesktop except for the "New Audio Forwarding Feature" test case. What Could Go Wrong --- RDP Sharing is a new feature for Ubuntu 22.04 LTS as part of GNOME 42. (Previously only VNC Sharing was offered.) RDP Sharing can be used for providing remote support so it's important that this feature works well because it may be difficult for the remote admin to fix issues in person. gnome-remote-desktop is part of GNOME Core and falls under the GNOME Stable Release Update microrelease exception https://wiki.ubuntu.com/StableReleaseUpdates/GNOME Other Info -- The previous 22.04 LTS SRU, 42.7-0ubuntu1, got stuck in phased updates. We worked with upstream to do a new 42 release in hopes that this update along with the SRU for mutter 42.9 (LP: #1998286) will significantly improve the error rate. 42.7-0ubuntu1 was included in Ubuntu Desktop 22.04.2 so many users already have that version from the original install or got it before phasing was halted. https://ubuntu-archive-team.ubuntu.com/phased-updates.html -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-remote-desktop in Ubuntu. https://bugs.launchpad.net/bugs/2024248 Title: Update gnome-remote-desktop to 42.9 Status in gnome-remote-desktop package in Ubuntu: Fix Released Status in gnome-remote-desktop source package in Jammy: Fix Committed Bug description: Impact -- This is a new stable release in the GNOME 42 series It backports fixes for some crashes reported to errors.ubuntu.com Changes since the current Ubuntu 22.04 LTS release: https://gitlab.gnome.org/GNOME/gnome-remote-desktop/-/compare/42.7...42.9 Test Cases -- Complete all the test cases from https://wiki.ubuntu.com/DesktopTeam/TestPlans/RemoteDesktop except for the "New Audio Forwarding Feature" test case. What Could Go Wrong --- RDP Sharing is a new feature for Ubuntu 22.04 LTS as part of GNOME 42. (Previously only VNC Sharing was offered.) RDP Sharing can be used for providing remote support so it's important that this feature works well because it may be difficult for the remote admin to fix issues in person. gnome-remote-desktop is part of GNOME Core and falls under the GNOME Stable Release Update microrelease exception https://wiki.ubuntu.com/StableReleaseUpdates/GNOME Other Info -- The previous 22.04 LTS SRU, 42.7-0ubuntu1, got stuck in phased updates. We worked with upstream to do a new 42 release in hopes that this update along with the SRU for mutter 42.9 (LP: #1998286) will significantly improve the error rate. 42.7-0ubuntu1 was included in Ubuntu Desktop 22.04.2 so many users already have that version from the original install or got it before phasing was halted. https://ubuntu-archive-team.ubuntu.com/phased-updates.html To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-remote-desktop/+bug/2024248/+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 2019477] Re: Sliders temporary hide when hovered
Sliders are properly rendered also when hovered. ❯ apt-cache policy yaru-theme-gtk yaru-theme-gtk: Installed: 22.04.5 Candidate: 22.04.5 Version table: *** 22.04.5 400 400 http://archive.ubuntu.com/ubuntu jammy-proposed/main amd64 Packages 400 http://archive.ubuntu.com/ubuntu jammy-proposed/main i386 Packages 100 /var/lib/dpkg/status 22.04.4 500 500 http://archive.ubuntu.com/ubuntu jammy/main amd64 Packages 500 http://archive.ubuntu.com/ubuntu jammy/main i386 Packages ** Package changed: gnome-shell-extension-ubuntu-dock (Ubuntu) => yaru- theme (Ubuntu) ** 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 gnome-shell-extension-ubuntu-dock in Ubuntu. https://bugs.launchpad.net/bugs/2019477 Title: Sliders temporary hide when hovered Status in yaru-theme package in Ubuntu: Fix Released Status in yaru-theme source package in Jammy: Fix Committed Bug description: [ Impact ] The slider temporary hide when hovered (see https://github.com/ubuntu/yaru/pull/3634) [ Test case ] 1. Install gtk3-widget-factory from gtk-3-examples package 2. Run the Widgets Factory application, go to "Page 3" 3. Hover the transparency slider in the right-bottom side of the window 4. The item should not be hidden [ Regression potential ] Sliders are not properly themed during hover To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/yaru-theme/+bug/2019477/+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 2024248] Re: Update gnome-remote-desktop to 42.8
Sadly this new version has a new crash:
Core was generated by `/usr/libexec/gnome-remote-desktop-daemon'.
Program terminated with signal SIGABRT, Aborted.
#0 __pthread_kill_implementation (no_tid=0, signo=6, threadid=140478263563840)
at ./nptl/pthread_kill.c:44
44 ./nptl/pthread_kill.c: No such file or directory.
[Current thread is 1 (Thread 0x7fc3a4ff9640 (LWP 412662))]
(gdb) bt
#0 __pthread_kill_implementation (no_tid=0, signo=6, threadid=140478263563840)
at ./nptl/pthread_kill.c:44
#1 __pthread_kill_internal (signo=6, threadid=140478263563840) at
./nptl/pthread_kill.c:78
#2 __GI___pthread_kill (threadid=140478263563840, signo=signo@entry=6) at
./nptl/pthread_kill.c:89
#3 0x7fc3c4ef2476 in __GI_raise (sig=sig@entry=6) at
../sysdeps/posix/raise.c:26
#4 0x7fc3c4ed87f3 in __GI_abort () at ./stdlib/abort.c:79
#5 0x7fc3c5a34b57 in g_assertion_message
(domain=, file=, line=,
func=0x564671390620 <__func__.4.lto_priv.6>
"maybe_release_pipewire_buffer_lock", message=) at
../../../glib/gtestutils.c:3253
#6 0x7fc3c5a8e70f in g_assertion_message_expr
(domain=domain@entry=0x0, file=file@entry=0x56467138fd98
"../src/grd-rdp-pipewire-stream.c", line=line@entry=194,
func=func@entry=0x564671390620 <__func__.4.lto_priv.6>
"maybe_release_pipewire_buffer_lock", expr=expr@entry=0x0) at
../../../glib/gtestutils.c:3279
#7 0x564671374c00 in maybe_release_pipewire_buffer_lock
(stream=, stream=0x56467361d280, buffer=0x0) at
../src/grd-rdp-pipewire-stream.c:194
#8 on_frame_ready (stream=0x56467361d280, frame=0x0, success=,
user_data=0x0)
at ../src/grd-rdp-pipewire-stream.c:1055
#9 0x7fc3c5788195 in impl_node_process_input (object=0x56467364ff90) at
../src/pipewire/stream.c:953
#10 0x7fc3c5760ab9 in process_node (data=0x564672f78b00) at
../src/pipewire/impl-node.c:1089
#11 0x7fc3c576649c in node_on_fd_events (source=) at
../src/pipewire/impl-node.c:1147
#12 0x7fc3b813fe33 in () at
/usr/lib/x86_64-linux-gnu/spa-0.2/support/libspa-support.so
#13 0x7fc3c5743226 in do_loop (user_data=0x564673611750) at
../src/pipewire/data-loop.c:81
#14 0x7fc3c4f44b43 in start_thread (arg=) at
./nptl/pthread_create.c:442
#15 0x7fc3c4fd6a00 in clone3 () at
../sysdeps/unix/sysv/linux/x86_64/clone3.S:81
(gdb) f 7
#7 0x564671374c00 in maybe_release_pipewire_buffer_lock
(stream=0x56467361d280, stream=0x56467361d280,
buffer=0x0) at ../src/grd-rdp-pipewire-stream.c:194
194 ../src/grd-rdp-pipewire-stream.c: No such file or directory.
(gdb) print stream
$1 = 0x56467361d280
(gdb) print *stream
$2 = {parent = {g_type_instance = {g_class = 0x564673615810 [g_type: None]},
ref_count = 1, qdata = 0x0},
session_rdp = 0x564672f68050, rdp_surface = 0x7fc37c011050, pipewire_source =
0x564672eb7b10,
pipewire_context = 0x564673633570, pipewire_core = 0x564672f7b140,
pipewire_core_listener = {link = {
next = 0x56467364ff98, prev = 0x564672f7b1e8}, cb = {funcs =
0x56467139dde0 ,
data = 0x56467361d280}, removed = 0x0, priv = 0x0}, buffer_pool =
0x5646736061e0,
render_source = 0x564672e97980, frame_mutex = {p = 0x0, i = {0, 0}},
pending_frame = 0x0,
pipewire_stream = 0x56467364ff90, pipewire_stream_listener = {link = {next =
0x56467364fff8,
prev = 0x56467364fff8}, cb = {funcs = 0x56467139da60 ,
data = 0x56467361d280},
removed = 0x7fc3c577ffb0 , priv = 0x56467364ff90},
pipewire_buffers = 0x7fc3b4003520 = {
[0x564673650430] = 0x5646736462b0, [0x564673650408] = 0x564673646290,
[0x5646736503e0] = 0x564673646270,
[0x5646736503b8] = 0x564673646250, [0x564673650390] = 0x56467360e070,
[0x564673650368] = 0x564673611680,
[0x564673650458] = 0x5646736462d0, [0x564673650340] = 0x564673609fb0},
src_node_id = 43, spa_format = {
format = SPA_VIDEO_FORMAT_BGRx, modifier = 0, size = {width = 1920, height
= 1080}, framerate = {num = 0,
denom = 1}, max_framerate = {num = 30, denom = 1}, views = 0,
interlace_mode = SPA_VIDEO_INTERLACE_MODE_PROGRESSIVE, pixel_aspect_ratio =
{num = 0, denom = 0},
multiview_mode = SPA_VIDEO_MULTIVIEW_MODE_MONO, multiview_flags =
SPA_VIDEO_MULTIVIEW_FLAGS_NONE,
chroma_site = SPA_VIDEO_CHROMA_SITE_UNKNOWN, color_range =
SPA_VIDEO_COLOR_RANGE_UNKNOWN,
color_matrix = SPA_VIDEO_COLOR_MATRIX_UNKNOWN, transfer_function =
SPA_VIDEO_TRANSFER_UNKNOWN,
color_primaries = SPA_VIDEO_COLOR_PRIMARIES_UNKNOWN}}
(gdb) print stream->pipewire_buffers
$3 = 0x7fc3b4003520 = {[0x564673650430] = 0x5646736462b0, [0x564673650408] =
0x564673646290,
[0x5646736503e0] = 0x564673646270, [0x5646736503b8] = 0x564673646250,
[0x564673650390] = 0x56467360e070,
[0x564673650368] = 0x564673611680, [0x564673650458] = 0x5646736462d0,
[0x564673650340] = 0x564673609fb0}
Threaded trace: https://dpaste.com/DJP6YT6XX
** Tags removed: verification-needed verification-needed-jammy
** Tags added: verification-failed verification-failed-jammy
--
You received this bug notification
[Desktop-packages] [Bug 1966167] Re: Ubuntu Dock icons not clickable at the edge of the screen
marco-ThinkPad-X1-Carbon-7th ~ 5s 18:22:50 ❯ apt-cache policy gnome-shell-extension-ubuntu-dock gnome-shell-extension-ubuntu-dock: Installed: 72~ubuntu5.22.04.2.1 Candidate: 72~ubuntu5.22.04.2.1 Version table: *** 72~ubuntu5.22.04.2.1 500 500 http://archive.ubuntu.com/ubuntu jammy-updates/main amd64 Packages 500 http://archive.ubuntu.com/ubuntu jammy-updates/main i386 Packages 100 /var/lib/dpkg/status 72~ubuntu5 500 500 http://archive.ubuntu.com/ubuntu jammy/main amd64 Packages 500 http://archive.ubuntu.com/ubuntu jammy/main i386 Packages marco-ThinkPad-X1-Carbon-7th ~ 18:23:27 ❯ apt-cache policy yaru-theme-gnome-shell yaru-theme-gnome-shell: Installed: 22.04.5 Candidate: 22.04.5 Version table: *** 22.04.5 400 400 http://archive.ubuntu.com/ubuntu jammy-proposed/main amd64 Packages 400 http://archive.ubuntu.com/ubuntu jammy-proposed/main i386 Packages 100 /var/lib/dpkg/status 22.04.4 500 500 http://archive.ubuntu.com/ubuntu jammy/main amd64 Packages 500 http://archive.ubuntu.com/ubuntu jammy/main i386 Packages The fix is confirmed ** 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 gnome-shell-extension-ubuntu-dock in Ubuntu. https://bugs.launchpad.net/bugs/1966167 Title: Ubuntu Dock icons not clickable at the edge of the screen Status in Dash to dock: New Status in Yaru Theme: New Status in gnome-shell-extension-ubuntu-dock package in Ubuntu: Fix Released Status in yaru-theme package in Ubuntu: Fix Released Status in gnome-shell-extension-ubuntu-dock source package in Jammy: Fix Committed Status in yaru-theme source package in Jammy: Fix Committed Bug description: [ Impact ] If you go to the bottom left corner of the dock and click, the All Apps button doesn't get triggered or highlighted. Check attached video for details. [ Test case ] For verifying yaru-theme, in the Ubuntu session: 1. Move the pointer to the edge of the screen where the AppIcons button is visible (bottom-left corner by default) 2. The button should be highlighted and clicking it should open the applications grid [ Regression potential ] - The dock margins are wrong or icons are not clickable in their edges - There's no not-reactive space between the activity button and the first icon --- Ubuntu 21.10. Live mode. 1920x1080 screen. To manage notifications about this bug go to: https://bugs.launchpad.net/dash-to-dock/+bug/1966167/+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 2012978] Re: Memory leak
❯ apt-cache policy gjs
gjs:
Installed: 1.72.4-0ubuntu0.22.04.1
Candidate: 1.72.4-0ubuntu0.22.04.1
Version table:
*** 1.72.4-0ubuntu0.22.04.1 400
400 http://archive.ubuntu.com/ubuntu jammy-proposed/main amd64 Packages
100 /var/lib/dpkg/status
1.72.2-0ubuntu2 500
500 http://archive.ubuntu.com/ubuntu jammy-updates/main amd64 Packages
1.72.0-1 500
500 http://archive.ubuntu.com/ubuntu jammy/main amd64 Packages
No variant leak (the other detected is a mozjs issue, but likely a wrong
valgrind detection):
❯ env G_SLICE=always-malloc valgrind --leak-check=full \
--suppressions=/usr/share/glib-2.0/valgrind/glib.supp \
gjs -c "const GLib=imports.gi['GLib'];function leak(){const
l=GLib.Variant['new']('i',1)};leak();imports.system.gc();"
==356489== Memcheck, a memory error detector
==356489== Copyright (C) 2002-2017, and GNU GPL'd, by Julian Seward et al.
==356489== Using Valgrind-3.18.1 and LibVEX; rerun with -h for copyright info
==356489== Command: gjs -c const\ GLib=imports.gi['GLib'];function\
leak(){const\ l=GLib.Variant['new']('i',1)};leak();imports.system.gc();
==356489==
==356489== Warning: set address range perms: large range [0x2204b34b7000,
0x2205330b7000) (noaccess)
==356489== Warning: set address range perms: large range [0x2204b34b7000,
0x2205330b7000) (noaccess)
==356489==
==356489== HEAP SUMMARY:
==356489== in use at exit: 193,115 bytes in 2,445 blocks
==356489== total heap usage: 19,931 allocs, 17,486 frees, 9,251,399 bytes
allocated
==356489==
==356489== 352 bytes in 1 blocks are possibly lost in loss record 1,965 of 2,008
==356489==at 0x484DA83: calloc (in
/usr/libexec/valgrind/vgpreload_memcheck-amd64-linux.so)
==356489==by 0x40147D9: calloc (rtld-malloc.h:44)
==356489==by 0x40147D9: allocate_dtv (dl-tls.c:375)
==356489==by 0x40147D9: _dl_allocate_tls (dl-tls.c:634)
==356489==by 0x5008834: allocate_stack (allocatestack.c:430)
==356489==by 0x5008834: pthread_create@@GLIBC_2.34 (pthread_create.c:647)
==356489==by 0x5A36794: mozilla::TimeStamp::ComputeProcessUptime() (in
/usr/lib/x86_64-linux-gnu/libmozjs-91.so.91.10.0)
==356489==by 0x5A36856: mozilla::TimeStamp::ProcessCreation(bool*) (in
/usr/lib/x86_64-linux-gnu/libmozjs-91.so.91.10.0)
==356489==by 0x5444A7F: JS::detail::InitWithFailureDiagnostic(bool) (in
/usr/lib/x86_64-linux-gnu/libmozjs-91.so.91.10.0)
==356489==by 0x48A2363: ??? (in /usr/lib/x86_64-linux-gnu/libgjs.so.0.0.0)
==356489==by 0x400647D: call_init.part.0 (dl-init.c:70)
==356489==by 0x4006567: call_init (dl-init.c:33)
==356489==by 0x4006567: _dl_init (dl-init.c:117)
==356489==by 0x40202E9: ??? (in
/usr/lib/x86_64-linux-gnu/ld-linux-x86-64.so.2)
==356489==by 0x2: ???
==356489==by 0x1FFEFFFBBE: ???
==356489==
==356489== LEAK SUMMARY:
==356489==definitely lost: 0 bytes in 0 blocks
==356489==indirectly lost: 0 bytes in 0 blocks
==356489== possibly lost: 352 bytes in 1 blocks
==356489==still reachable: 77,254 bytes in 965 blocks
==356489== suppressed: 97,829 bytes in 1,292 blocks
==356489== Reachable blocks (those to which a pointer was found) are not shown.
==356489== To see them, rerun with: --leak-check=full --show-leak-kinds=all
==356489==
==356489== For lists of detected and suppressed errors, rerun with: -s
==356489== ERROR SUMMARY: 1 errors from 1 contexts (suppressed: 1 from 1)
-
env GJS_DEBUG_TOPICS= valgrind --leak-check=full \
--suppressions=/usr/share/glib-2.0/valgrind/glib.supp \
/usr/libexec/installed-tests/gjs/minijasmine \
/usr/libexec/installed-tests/gjs/js/testGIMarshalling.js
==357068== Warning: set address range perms: large range [0xbabd0a0c000,
0xbac5060c000) (noaccess)
==357068==
==357068== HEAP SUMMARY:
==357068== in use at exit: 231,169 bytes in 3,087 blocks
==357068== total heap usage: 155,879 allocs, 152,792 frees, 28,688,797 bytes
allocated
==357068==
==357068== 0 bytes in 1 blocks are definitely lost in loss record 1 of 2,526
==357068==at 0x4848899: malloc (in
/usr/libexec/valgrind/vgpreload_memcheck-amd64-linux.so)
==357068==by 0x4005A22: malloc (rtld-malloc.h:56)
==357068==by 0x4005A22: _dl_find_object_update (dl-find_object.c:791)
==357068==by 0x400ECCF: dl_open_worker_begin (dl-open.c:735)
==357068==by 0x4EC0C27: _dl_catch_exception (dl-error-skeleton.c:208)
==357068==by 0x400DF99: dl_open_worker (dl-open.c:782)
==357068==by 0x4EC0C27: _dl_catch_exception (dl-error-skeleton.c:208)
==357068==by 0x400E34D: _dl_open (dl-open.c:883)
==357068==by 0x4DDC6BB: dlopen_doit (dlopen.c:56)
==357068==by 0x4EC0C27: _dl_catch_exception (dl-error-skeleton.c:208)
==357068==by 0x4EC0CF2: _dl_catch_error (dl-error-skeleton.c:227)
==357068==by 0x4DDC1AD: _dlerror_run (dlerror.c:138)
==357068==by 0x4DDC747: dlopen_implementation (dlopen.c:71)
==357068==by 0x4DDC747: dlopen@@GLIBC_2.34
[Desktop-packages] [Bug 1993214] Re: [jammy] Update gjs to 1.74 using mozjs102
Removing `block-proposed-jammy` given that there's no 1.74 in jammy proposed and otherwise we'd block the landing of 1.72.4-0ubuntu0.22.04.1 ** Tags removed: block-proposed-jammy -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gjs in Ubuntu. https://bugs.launchpad.net/bugs/1993214 Title: [jammy] Update gjs to 1.74 using mozjs102 Status in gjs package in Ubuntu: Fix Released Status in gjs source package in Jammy: Incomplete Bug description: Impact -- GNOME Shell uses the SpiderMonkey JavaScript engine from Firefox ESR (mozjs). Firefox 92 ESR has reached end of life; therefore, we should switch to the 102 ESR series for security updates for the next year. This requires updating gjs from 1.72 to 1.74 from GNOME 43, as packaged in Ubuntu 22.10. This will be done as a Security Update. Updating mozjs in stable Ubuntu releases was recommended when Ubuntu first switched back to GNOME, but this is the first time it's been done. Security Impact --- I looked through https://github.com/mozilla/gecko-dev/commits/esr102/js and searched for referenced bug numbers in https://www.mozilla.org/en-US/security/advisories/ for Firefox ESR releases since Ubuntu's 91.10 and found one CVE. Also, there's the vague Mozilla Bug 1771084 (no CVE issued) mentioned at https://www.mozilla.org/en-US/security/advisories/mfsa2022-24/ Uploaded Packages - We will introduce mozjs102, a new source package for Ubuntu 22.04 LTS, being careful to publish it in main, not universe. And we'll update gjs. No other packages need to be updated for this change. mozjs91 will remain in Ubuntu 22.04 LTS (source package removals are generally not possible), but nothing else in Ubuntu uses it. Test Case - https://wiki.ubuntu.com/DesktopTeam/TestPlans/gjs Security Sponsoring --- sudo apt install git-buildpackage gbp clone https://salsa.debian.org/gnome-team/gjs cd gjs git checkout ubuntu/jammy gbp buildpackage --git-builder="debuild -S -nc" Initial Testing Done I built the packages in my PPA. I installed the packages on Ubuntu 22.04 LTS and successfully completed the Test Case. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gjs/+bug/1993214/+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 2023572] Re: SRU gjs 1.72.4 to jammy
** Tags removed: verification-needed ** Tags added: verification-done ** Tags removed: verification-needed-jammy ** Tags added: verification-done-jammy -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gjs in Ubuntu. https://bugs.launchpad.net/bugs/2023572 Title: SRU gjs 1.72.4 to jammy Status in gjs package in Ubuntu: Fix Released Status in gjs source package in Jammy: Fix Committed Bug description: [ Impact ] That's the GNOME 42 stable update, including some fixes: https://gitlab.gnome.org/GNOME/gjs/-/commits/1.72.4 [ Test case ] The update is part of GNOME stable updates https://wiki.ubuntu.com/StableReleaseUpdates/GNOME The test plan that will be used is documented at https://wiki.ubuntu.com/DesktopTeam/TestPlans/gjs [ Regression potential ] Gjs is fundamental part of the ubuntu desktop, so any failure of it may cause the desktop not even to boot (because it's being used by gdm too). To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gjs/+bug/2023572/+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 1294015] Re: gjs-console crashed with signal 5 in g_settings_bind_with_mapping()
** Changed in: gjs (Ubuntu) Status: Confirmed => Incomplete ** No longer affects: gjs (Ubuntu Trusty) ** No longer affects: gjs (Ubuntu Utopic) ** No longer affects: gnome-settings-daemon (Ubuntu Trusty) ** No longer affects: gnome-settings-daemon (Ubuntu Utopic) ** Changed in: gnome-settings-daemon (Ubuntu) Status: Confirmed => Incomplete -- 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/1294015 Title: gjs-console crashed with signal 5 in g_settings_bind_with_mapping() Status in Ubuntu GNOME: Triaged Status in gjs package in Ubuntu: Incomplete Status in gnome-settings-daemon package in Ubuntu: Incomplete Bug description: I used the GNOME shell extension "EasyScreenCast" and simply clicked on the "options" label in its menu, and voila. https://extensions.gnome.org/extension/690/easyscreencast/ ProblemType: Crash DistroRelease: Ubuntu 14.04 Package: gjs 1.39.91-0ubuntu1 ProcVersionSignature: Ubuntu 3.13.0-17.37-generic 3.13.6 Uname: Linux 3.13.0-17-generic x86_64 ApportVersion: 2.13.3-0ubuntu1 Architecture: amd64 CurrentDesktop: GNOME Date: Tue Mar 18 10:34:41 2014 ExecutablePath: /usr/bin/gjs-console InstallationDate: Installed on 2014-03-16 (1 days ago) InstallationMedia: Ubuntu-GNOME 14.04 "Trusty Tahr" - Alpha amd64 (20140226) ProcCmdline: /usr/bin/gjs-console -I /usr/share/gnome-shell/js -c const\ Main\ =\ imports.extensionPrefs.main;\ Main.main(ARGV); easyscreenc...@iacopodeenosee.gmail.com ProcEnviron: LD_LIBRARY_PATH= PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=fr_FR.UTF-8 SHELL=/bin/bash Signal: 5 SourcePackage: gjs StacktraceTop: ?? () from /usr/lib/x86_64-linux-gnu/libgio-2.0.so.0 ?? () from /usr/lib/x86_64-linux-gnu/libgio-2.0.so.0 g_settings_bind_with_mapping () from /usr/lib/x86_64-linux-gnu/libgio-2.0.so.0 g_settings_bind () from /usr/lib/x86_64-linux-gnu/libgio-2.0.so.0 ffi_call_unix64 () from /usr/lib/x86_64-linux-gnu/libffi.so.6 Title: gjs-console crashed with signal 5 in g_settings_bind_with_mapping() UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-gnome/+bug/1294015/+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 2024240] Re: [rdp] gnome-remote-desktop-daemon crashes in push_queue -> pw_stream_queue_buffer -> on_frame_ready -> process_frame_data -> impl_node_process_input
** Description changed: + [ Test case ] + + Check that remote desktop work fine in both RDP and VNC modes. + + --- + The Ubuntu Error Tracker has been receiving reports about a problem regarding gnome-remote-desktop. This problem was most recently seen with package version 42.7-0ubuntu1, the problem page at https://errors.ubuntu.com/problem/11f28bb1ebb12472ffcc6dfe3e664af697e8a47a contains more details, including versions of packages affected, stacktrace or traceback, and individual crash reports. If you do not have access to the Ubuntu Error Tracker and are a software developer, you can request it at http://forms.canonical.com/reports/. Related to https://bugs.launchpad.net/ubuntu/+source/gnome-remote- desktop/+bug/2024238 -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-remote-desktop in Ubuntu. https://bugs.launchpad.net/bugs/2024240 Title: [rdp] gnome-remote-desktop-daemon crashes in push_queue -> pw_stream_queue_buffer -> on_frame_ready -> process_frame_data -> impl_node_process_input Status in gnome-remote-desktop package in Ubuntu: Fix Released Status in gnome-remote-desktop source package in Jammy: Fix Committed Bug description: [ Test case ] Check that remote desktop work fine in both RDP and VNC modes. --- The Ubuntu Error Tracker has been receiving reports about a problem regarding gnome-remote-desktop. This problem was most recently seen with package version 42.7-0ubuntu1, the problem page at https://errors.ubuntu.com/problem/11f28bb1ebb12472ffcc6dfe3e664af697e8a47a contains more details, including versions of packages affected, stacktrace or traceback, and individual crash reports. If you do not have access to the Ubuntu Error Tracker and are a software developer, you can request it at http://forms.canonical.com/reports/. Related to https://bugs.launchpad.net/ubuntu/+source/gnome-remote- desktop/+bug/2024238 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-remote-desktop/+bug/2024240/+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 2024237] Re: /usr/libexec/gnome-remote-desktop-daemon:11:push_queue:pw_stream_queue_buffer:on_frame_ready:grd_thread_dispatch_in_impl:egl_task_source_dispatch
Should be related to https://bugs.launchpad.net/ubuntu/+source/gnome- remote-desktop/+bug/2024238 ** Changed in: gnome-remote-desktop (Ubuntu) Status: New => Fix Released ** Also affects: gnome-remote-desktop (Ubuntu Jammy) Importance: Undecided Status: New -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-remote-desktop in Ubuntu. https://bugs.launchpad.net/bugs/2024237 Title: /usr/libexec/gnome-remote-desktop- daemon:11:push_queue:pw_stream_queue_buffer:on_frame_ready:grd_thread_dispatch_in_impl:egl_task_source_dispatch Status in gnome-remote-desktop package in Ubuntu: Fix Released Status in gnome-remote-desktop source package in Jammy: New Bug description: The Ubuntu Error Tracker has been receiving reports about a problem regarding gnome-remote-desktop. This problem was most recently seen with package version 42.7-0ubuntu1, the problem page at https://errors.ubuntu.com/problem/b9db6ccdb84569be427829049e6f135d9777e574 contains more details, including versions of packages affected, stacktrace or traceback, and individual crash reports. If you do not have access to the Ubuntu Error Tracker and are a software developer, you can request it at http://forms.canonical.com/reports/. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-remote-desktop/+bug/2024237/+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 2024238] Re: /usr/libexec/gnome-remote-desktop-daemon:11:push_queue:pw_stream_queue_buffer:on_frame_ready:download_in_impl:grd_thread_dispatch_in_impl
** Summary changed: - /usr/libexec/gnome-remote-desktop-daemon:11:push_queue:pw_stream_queue_buffer:on_frame_ready:download_in_impl:grd_thread_dispatch_in_impl + gnome-remote-desktop-daemon crashes on -> push_queue -> pw_stream_queue_buffer -> on_frame_ready -> download_in_impl -> grd_thread_dispatch_in_impl ** Changed in: gnome-remote-desktop (Ubuntu) Status: New => Fix Released ** Also affects: gnome-remote-desktop (Ubuntu Jammy) Importance: Undecided Status: New ** Summary changed: - gnome-remote-desktop-daemon crashes on -> push_queue -> pw_stream_queue_buffer -> on_frame_ready -> download_in_impl -> grd_thread_dispatch_in_impl + [vnc] gnome-remote-desktop-daemon crashes on -> push_queue -> pw_stream_queue_buffer -> on_frame_ready -> download_in_impl -> grd_thread_dispatch_in_impl ** Description changed: The Ubuntu Error Tracker has been receiving reports about a problem regarding gnome-remote-desktop. This problem was most recently seen with package version 42.7-0ubuntu1, the problem page at https://errors.ubuntu.com/problem/e097eda971e1f65f9170b00258037980eee90aca contains more details, including versions of packages affected, stacktrace or traceback, and individual crash reports. If you do not have access to the Ubuntu Error Tracker and are a software developer, you can request it at http://forms.canonical.com/reports/. + + Related to https://bugs.launchpad.net/ubuntu/+source/gnome-remote- + desktop/+bug/2024240 -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-remote-desktop in Ubuntu. https://bugs.launchpad.net/bugs/2024238 Title: [vnc] gnome-remote-desktop-daemon crashes on -> push_queue -> pw_stream_queue_buffer -> on_frame_ready -> download_in_impl -> grd_thread_dispatch_in_impl Status in gnome-remote-desktop package in Ubuntu: Fix Released Status in gnome-remote-desktop source package in Jammy: New Bug description: The Ubuntu Error Tracker has been receiving reports about a problem regarding gnome-remote-desktop. This problem was most recently seen with package version 42.7-0ubuntu1, the problem page at https://errors.ubuntu.com/problem/e097eda971e1f65f9170b00258037980eee90aca contains more details, including versions of packages affected, stacktrace or traceback, and individual crash reports. If you do not have access to the Ubuntu Error Tracker and are a software developer, you can request it at http://forms.canonical.com/reports/. Related to https://bugs.launchpad.net/ubuntu/+source/gnome-remote- desktop/+bug/2024240 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-remote-desktop/+bug/2024238/+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 2024240] Re: [rdp] gnome-remote-desktop-daemon crashes in push_queue -> pw_stream_queue_buffer -> on_frame_ready -> process_frame_data -> impl_node_process_input
** Summary changed: - /usr/libexec/gnome-remote-desktop-daemon:11:push_queue:pw_stream_queue_buffer:on_frame_ready:process_frame_data:impl_node_process_input + [rdp] gnome-remote-desktop-daemon crashes in push_queue -> pw_stream_queue_buffer -> on_frame_ready -> process_frame_data -> impl_node_process_input ** Changed in: gnome-remote-desktop (Ubuntu) Status: New => Fix Released ** Also affects: gnome-remote-desktop (Ubuntu Jammy) Importance: Undecided Status: New ** Changed in: gnome-remote-desktop (Ubuntu Jammy) Status: New => In Progress ** Description changed: The Ubuntu Error Tracker has been receiving reports about a problem regarding gnome-remote-desktop. This problem was most recently seen with package version 42.7-0ubuntu1, the problem page at https://errors.ubuntu.com/problem/11f28bb1ebb12472ffcc6dfe3e664af697e8a47a contains more details, including versions of packages affected, stacktrace or traceback, and individual crash reports. If you do not have access to the Ubuntu Error Tracker and are a software developer, you can request it at http://forms.canonical.com/reports/. + + Related to https://bugs.launchpad.net/ubuntu/+source/gnome-remote- + desktop/+bug/2024238 -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-remote-desktop in Ubuntu. https://bugs.launchpad.net/bugs/2024240 Title: [rdp] gnome-remote-desktop-daemon crashes in push_queue -> pw_stream_queue_buffer -> on_frame_ready -> process_frame_data -> impl_node_process_input Status in gnome-remote-desktop package in Ubuntu: Fix Released Status in gnome-remote-desktop source package in Jammy: In Progress Bug description: The Ubuntu Error Tracker has been receiving reports about a problem regarding gnome-remote-desktop. This problem was most recently seen with package version 42.7-0ubuntu1, the problem page at https://errors.ubuntu.com/problem/11f28bb1ebb12472ffcc6dfe3e664af697e8a47a contains more details, including versions of packages affected, stacktrace or traceback, and individual crash reports. If you do not have access to the Ubuntu Error Tracker and are a software developer, you can request it at http://forms.canonical.com/reports/. Related to https://bugs.launchpad.net/ubuntu/+source/gnome-remote- desktop/+bug/2024238 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-remote-desktop/+bug/2024240/+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 2024239] Re: /usr/libexec/gnome-remote-desktop-daemon:11:spa_ringbuffer_get_read_index:pop_queue:pw_stream_dequeue_buffer:on_stream_process:impl_node_process_input
*** This bug is a duplicate of bug 2024238 *** https://bugs.launchpad.net/bugs/2024238 ** This bug has been marked a duplicate of bug 2024238 gnome-remote-desktop-daemon crashes on -> push_queue -> pw_stream_queue_buffer -> on_frame_ready -> download_in_impl -> grd_thread_dispatch_in_impl -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-remote-desktop in Ubuntu. https://bugs.launchpad.net/bugs/2024239 Title: /usr/libexec/gnome-remote-desktop- daemon:11:spa_ringbuffer_get_read_index:pop_queue:pw_stream_dequeue_buffer:on_stream_process:impl_node_process_input Status in gnome-remote-desktop package in Ubuntu: New Bug description: The Ubuntu Error Tracker has been receiving reports about a problem regarding gnome-remote-desktop. This problem was most recently seen with package version 42.7-0ubuntu1, the problem page at https://errors.ubuntu.com/problem/805859a2500b763fd6019892497ba729463cbf0c contains more details, including versions of packages affected, stacktrace or traceback, and individual crash reports. If you do not have access to the Ubuntu Error Tracker and are a software developer, you can request it at http://forms.canonical.com/reports/. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-remote-desktop/+bug/2024239/+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 2023572] Re: SRU gjs 1.72.4 to jammy
** Summary changed: - SRU gjs 1.72.3 to jammy + SRU gjs 1.72.4 to jammy ** Description changed: [ Impact ] That's the GNOME 42 stable update, including some fixes: - https://gitlab.gnome.org/GNOME/gjs/-/commits/1.72.3 + https://gitlab.gnome.org/GNOME/gjs/-/commits/1.72.4 [ Test case ] The update is part of GNOME stable updates https://wiki.ubuntu.com/StableReleaseUpdates/GNOME Gjs applications (such as GNOME Maps, GNOME Characters, GNOME Weather...) and GNOME Shell and its components and extensions should continue working. [ Regression potential ] Gjs is fundamental part of the ubuntu desktop, so any failure of it may cause the desktop not even to boot (because it's being used by gdm too). -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gjs in Ubuntu. https://bugs.launchpad.net/bugs/2023572 Title: SRU gjs 1.72.4 to jammy Status in gjs package in Ubuntu: Fix Released Status in gjs source package in Jammy: Fix Committed Bug description: [ Impact ] That's the GNOME 42 stable update, including some fixes: https://gitlab.gnome.org/GNOME/gjs/-/commits/1.72.4 [ Test case ] The update is part of GNOME stable updates https://wiki.ubuntu.com/StableReleaseUpdates/GNOME Gjs applications (such as GNOME Maps, GNOME Characters, GNOME Weather...) and GNOME Shell and its components and extensions should continue working. [ Regression potential ] Gjs is fundamental part of the ubuntu desktop, so any failure of it may cause the desktop not even to boot (because it's being used by gdm too). To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gjs/+bug/2023572/+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 2023571] Re: Update to gjs 1.76.2 and SRU it
This bug was fixed in the package gjs - 1.76.2-1 gjs (1.76.2-1) experimental; urgency=medium * New upstream release (LP: #2023571) * Drop all patches: applied in new release -- Jeremy Bícha Wed, 14 Jun 2023 18:44:22 -0400 ** Summary changed: - Update to gjs 1.76.1 and SRU it + Update to gjs 1.76.2 and SRU it ** Description changed: [ Impact ] There is a new bugfix release in the stable series associated with GNOME 44 - https://gitlab.gnome.org/GNOME/gjs/-/blob/1.76.1/NEWS + https://gitlab.gnome.org/GNOME/gjs/-/blob/1.76.2/NEWS [ Test case ] Complete the test cases from https://wiki.ubuntu.com/DesktopTeam/TestPlans/gjs The update is part of GNOME stable updates https://wiki.ubuntu.com/StableReleaseUpdates/GNOME Gjs applications (such as GNOME Maps, GNOME Characters, GNOME Weather...) and GNOME Shell and its components and extensions should continue working. [ Regression potential ] GNOME Shell is the heart of the Ubuntu desktop experience. gjs is a key component of GNOME Shell. A severe enough bug could mean that people are unable to use their desktop version of Ubuntu (it is used by even GDM, the login screen). Smaller bugs could interrupt people's workflows. This update changed fundamentally the memory management of some objects and containers (especially GVariant's), but these changes were already part of gjs released in ubuntu lunar (1.76.0-3). -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gjs in Ubuntu. https://bugs.launchpad.net/bugs/2023571 Title: Update to gjs 1.76.2 and SRU it Status in gjs package in Ubuntu: Fix Released Status in gjs source package in Lunar: In Progress Bug description: [ Impact ] There is a new bugfix release in the stable series associated with GNOME 44 https://gitlab.gnome.org/GNOME/gjs/-/blob/1.76.2/NEWS [ Test case ] Complete the test cases from https://wiki.ubuntu.com/DesktopTeam/TestPlans/gjs The update is part of GNOME stable updates https://wiki.ubuntu.com/StableReleaseUpdates/GNOME Gjs applications (such as GNOME Maps, GNOME Characters, GNOME Weather...) and GNOME Shell and its components and extensions should continue working. [ Regression potential ] GNOME Shell is the heart of the Ubuntu desktop experience. gjs is a key component of GNOME Shell. A severe enough bug could mean that people are unable to use their desktop version of Ubuntu (it is used by even GDM, the login screen). Smaller bugs could interrupt people's workflows. This update changed fundamentally the memory management of some objects and containers (especially GVariant's), but these changes were already part of gjs released in ubuntu lunar (1.76.0-3). To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gjs/+bug/2023571/+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 2023572] Re: SRU gjs 1.72.3 to jammy
** Changed in: gjs (Ubuntu Jammy) Status: In Progress => Fix Committed -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gjs in Ubuntu. https://bugs.launchpad.net/bugs/2023572 Title: SRU gjs 1.72.3 to jammy Status in gjs package in Ubuntu: Fix Released Status in gjs source package in Jammy: Fix Committed Bug description: [ Impact ] That's the GNOME 42 stable update, including some fixes: https://gitlab.gnome.org/GNOME/gjs/-/commits/1.72.3 [ Test case ] The update is part of GNOME stable updates https://wiki.ubuntu.com/StableReleaseUpdates/GNOME Gjs applications (such as GNOME Maps, GNOME Characters, GNOME Weather...) and GNOME Shell and its components and extensions should continue working. [ Regression potential ] Gjs is fundamental part of the ubuntu desktop, so any failure of it may cause the desktop not even to boot (because it's being used by gdm too). To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gjs/+bug/2023572/+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 2012978] Re: Memory leak
** Description changed:
[ Impact ]
High Memory Usage 3.1gb in 2h after reboot
[ Test case ]
Run:
- env G_SLICE=always-malloc valgrind --leak-check=full \
- --suppressions=/usr/share/glib-2.0/valgrind/glib.supp \
- gjs -c "const GLib=imports.gi['GLib'];function leak(){const
l=GLib.Variant['new']('i',1)};leak();imports.system.gc();"
+ env G_SLICE=always-malloc valgrind --leak-check=full \
+ --suppressions=/usr/share/glib-2.0/valgrind/glib.supp \
+ gjs -c "const GLib=imports.gi['GLib'];function leak(){const
l=GLib.Variant['new']('i',1)};leak();imports.system.gc();"
No leak should be detected
+
+ Running more installed tests under valgrind should output no leaks
+ (unless those caused by gobject-introspection):
+
+ sudo apt install gjs-tests
+ env GJS_DEBUG_TOPICS= valgrind --leak-check=full \
+ --suppressions=/usr/share/glib-2.0/valgrind/glib.supp \
+ /usr/libexec/installed-tests/gjs/minijasmine \
+ /usr/libexec/installed-tests/gjs/js/testGIMarshalling.js
+
+ There may be only two leaks caused by
+ gi_marshalling_tests_garray_boxed_struct_full_return and a gbytes one
+ after a ObjectInstance::prop_setter_impl call (these are leaks in the
+ test library that are expected with gobject-introspection 42, but fixed
+ in later versions).
+
+ env GJS_DEBUG_TOPICS= valgrind --leak-check=full \
+ --suppressions=/usr/share/glib-2.0/valgrind/glib.supp \
+ /usr/libexec/installed-tests/gjs/minijasmine \
+ /usr/libexec/installed-tests/gjs/js/testRegress.js
+
+ No leak expected
[ Regression potential ]
Gjs applications (including gnome Shell) using GVariant may misbehave
+ ---
ProblemType: BugDistroRelease: Ubuntu 22.04
Package: gnome-shell 42.5-0ubuntu1
Uname: Linux 6.2.8-060208-generic x86_64
ApportVersion: 2.20.11-0ubuntu82.3
Architecture: amd64
CasperMD5CheckResult: unknown
CurrentDesktop: ubuntu:GNOME
Date: Mon Mar 27 22:46:07 2023
DisplayManager: gdm3
InstallationDate: Installed on 2022-03-25 (366 days ago)
InstallationMedia: Ubuntu 20.04.4 LTS "Focal Fossa" - Release amd64 (20220223)
RelatedPackageVersions: mutter-common 42.5-0ubuntu1SourcePackage: gnome-shell
UpgradeStatus: Upgraded to jammy on 2022-09-03 (205 days ago)
** Changed in: gjs (Ubuntu Kinetic)
Status: Triaged => Won't Fix
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to gjs in Ubuntu.
https://bugs.launchpad.net/bugs/2012978
Title:
Memory leak
Status in gjs package in Ubuntu:
Fix Released
Status in gjs source package in Jammy:
Triaged
Status in gjs source package in Kinetic:
Won't Fix
Bug description:
[ Impact ]
High Memory Usage 3.1gb in 2h after reboot
[ Test case ]
Run:
env G_SLICE=always-malloc valgrind --leak-check=full \
--suppressions=/usr/share/glib-2.0/valgrind/glib.supp \
gjs -c "const GLib=imports.gi['GLib'];function leak(){const
l=GLib.Variant['new']('i',1)};leak();imports.system.gc();"
No leak should be detected
Running more installed tests under valgrind should output no leaks
(unless those caused by gobject-introspection):
sudo apt install gjs-tests
env GJS_DEBUG_TOPICS= valgrind --leak-check=full \
--suppressions=/usr/share/glib-2.0/valgrind/glib.supp \
/usr/libexec/installed-tests/gjs/minijasmine \
/usr/libexec/installed-tests/gjs/js/testGIMarshalling.js
There may be only two leaks caused by
gi_marshalling_tests_garray_boxed_struct_full_return and a gbytes one
after a ObjectInstance::prop_setter_impl call (these are leaks in the
test library that are expected with gobject-introspection 42, but
fixed in later versions).
env GJS_DEBUG_TOPICS= valgrind --leak-check=full \
--suppressions=/usr/share/glib-2.0/valgrind/glib.supp \
/usr/libexec/installed-tests/gjs/minijasmine \
/usr/libexec/installed-tests/gjs/js/testRegress.js
No leak expected
[ Regression potential ]
Gjs applications (including gnome Shell) using GVariant may misbehave
---
ProblemType: BugDistroRelease: Ubuntu 22.04
Package: gnome-shell 42.5-0ubuntu1
Uname: Linux 6.2.8-060208-generic x86_64
ApportVersion: 2.20.11-0ubuntu82.3
Architecture: amd64
CasperMD5CheckResult: unknown
CurrentDesktop: ubuntu:GNOME
Date: Mon Mar 27 22:46:07 2023
DisplayManager: gdm3
InstallationDate: Installed on 2022-03-25 (366 days ago)
InstallationMedia: Ubuntu 20.04.4 LTS "Focal Fossa" - Release amd64 (20220223)
RelatedPackageVersions: mutter-common 42.5-0ubuntu1SourcePackage: gnome-shell
UpgradeStatus: Upgraded to jammy on 2022-09-03 (205 days ago)
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gjs/+bug/2012978/+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 1986522] Re: Using a Gio.DesktopAppinfo().launch with context freezes GJS
It seems the problem is quite old, let's move at
https://gitlab.gnome.org/GNOME/gjs/-/issues/553
** Bug watch added: gitlab.gnome.org/GNOME/gjs/-/issues #553
https://gitlab.gnome.org/GNOME/gjs/-/issues/553
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to gjs in Ubuntu.
https://bugs.launchpad.net/bugs/1986522
Title:
Using a Gio.DesktopAppinfo().launch with context freezes GJS
Status in gjs package in Ubuntu:
New
Bug description:
Creating a Gio.DesktopAppInfo for a desktopfile, then launching with
an app_launch context freezes GJS. Launching with context set to null
works. There is no debug information on the console.
Using Gtk4
Here is the relevant code-
let desktopFile = Gio.DesktopAppInfo.new('gnome-background-panel.desktop');
const context = Gdk.Display.get_default().get_app_launch_context();
context.set_timestamp(Gdk.CURRENT_TIME);
// Fix me, context in the following causes a crash;
desktopFile.launch([], context)
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gjs/+bug/1986522/+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 2016906] Re: Inactive zombie ghost icons left behind on desktop when copying files
** Package changed: gjs (Ubuntu) => gnome-shell-extension-desktop-icons- ng (Ubuntu) -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gjs in Ubuntu. https://bugs.launchpad.net/bugs/2016906 Title: Inactive zombie ghost icons left behind on desktop when copying files Status in gnome-shell-extension-desktop-icons-ng package in Ubuntu: New Bug description: When copying files between directory windows, occasionally zombie ghost icons are left on the desktop. These are like holes in the screen with an icon that appears on top of everything in its covered location, is not selectable and is not moveable. Ubuntu 22.10 Release: 22.10 gjs: Installed: 1.74.0-1 Candidate: 1.74.0-1 Version table: *** 1.74.0-1 500 500 http://us.archive.ubuntu.com/ubuntu kinetic/main amd64 Packages 100 /var/lib/dpkg/status ProblemType: Bug DistroRelease: Ubuntu 22.10 Package: gjs 1.74.0-1 ProcVersionSignature: Ubuntu 5.19.0-38.39-generic 5.19.17 Uname: Linux 5.19.0-38-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.23.1-0ubuntu3.2 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Tue Apr 18 11:24:52 2023 ExecutablePath: /usr/bin/gjs-console InstallationDate: Installed on 2023-02-21 (56 days ago) InstallationMedia: Ubuntu 22.10 "Kinetic Kudu" - Release amd64 (20221020) ProcEnviron: LANG=en_US.UTF-8 PATH=(custom, no user) SHELL=/bin/bash XDG_RUNTIME_DIR= SourcePackage: gjs UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell-extension-desktop-icons-ng/+bug/2016906/+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 1987445] Re: After upgrade to 22.04 from 20.x execution of the shell fails to start the application
** Changed in: gjs (Ubuntu) Status: New => Incomplete -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gjs in Ubuntu. https://bugs.launchpad.net/bugs/1987445 Title: After upgrade to 22.04 from 20.x execution of the shell fails to start the application Status in gjs package in Ubuntu: Incomplete Bug description: file: cd maple2020/bin ./xmaple the file has permission to run as a program. Double-click results in nothing. I expected maple to start up. Right click plus "Run as a Program" works. ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: gjs 1.72.0-3~ubuntu22.04.2 ProcVersionSignature: Ubuntu 5.15.0-46.49-generic 5.15.39 Uname: Linux 5.15.0-46-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu82.1 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: ubuntu:GNOME Date: Tue Aug 23 23:10:01 2022 ExecutablePath: /usr/bin/gjs-console InstallationDate: Installed on 2021-01-10 (590 days ago) InstallationMedia: Ubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731) ProcEnviron: LANG=en_US.UTF-8 LANGUAGE=en_US:en PATH=(custom, user) SHELL=/bin/bash XDG_RUNTIME_DIR= SourcePackage: gjs UpgradeStatus: Upgraded to jammy on 2022-08-17 (6 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gjs/+bug/1987445/+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 2007739] Re: gjs-console crashed with SIGABRT
*** This bug is a duplicate of bug 2012287 ***
https://bugs.launchpad.net/bugs/2012287
** This bug has been marked a duplicate of bug 2012287
gjs-console crashed with signal 6 in g_assertion_message("assertion failed:
(!priv->is_realized)") from g_assertion_message_expr() from
gsk_renderer_dispose() from gsk_renderer_dispose() from g_object_unref()
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to gjs in Ubuntu.
https://bugs.launchpad.net/bugs/2007739
Title:
gjs-console crashed with SIGABRT
Status in gjs package in Ubuntu:
Confirmed
Bug description:
This is happening after wake from suspend.
ProblemType: Crash
DistroRelease: Ubuntu 23.04
Package: gjs 1.74.1-1
ProcVersionSignature: Ubuntu 5.19.0-1012.13-lowlatency 5.19.7
Uname: Linux 5.19.0-1012-lowlatency x86_64
NonfreeKernelModules: nvidia_modeset nvidia
ApportVersion: 2.24.0-0ubuntu2
Architecture: amd64
CasperMD5CheckResult: pass
CrashCounter: 1
CurrentDesktop: ubuntu:GNOME
Date: Fri Feb 17 18:41:41 2023
ExecutablePath: /usr/bin/gjs-console
InstallationDate: Installed on 2021-08-19 (547 days ago)
InstallationMedia: Ubuntu 21.10 "Impish Indri" - Alpha amd64 (20210818)
ProcCmdline: /usr/bin/gjs-console /usr/bin/gnome-characters
--gapplication-service
ProcEnviron:
SHELL=/bin/bash
XDG_RUNTIME_DIR=
PATH=(custom, user)
LANG=en_US.UTF-8
Signal: 6
SourcePackage: gjs
StacktraceTop:
() at /lib/x86_64-linux-gnu/libglib-2.0.so.0
g_assertion_message_expr () at /lib/x86_64-linux-gnu/libglib-2.0.so.0
() at /lib/x86_64-linux-gnu/libgtk-4.so.1
g_object_unref () at /lib/x86_64-linux-gnu/libgobject-2.0.so.0
() at /lib/x86_64-linux-gnu/libgjs.so.0
Title: gjs-console crashed with SIGABRT
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups: adm audio cdrom dip lpadmin lxd plugdev sambashare sudo
separator:
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gjs/+bug/2007739/+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 2023572] [NEW] SRU gjs 1.72.3 to jammy
Public bug reported: [ Impact ] That's the GNOME 42 stable update, including some fixes: https://gitlab.gnome.org/GNOME/gjs/-/commits/1.72.3 [ Test case ] The update is part of GNOME stable updates https://wiki.ubuntu.com/StableReleaseUpdates/GNOME Gjs applications (such as GNOME Maps, GNOME Characters, GNOME Weather...) and GNOME Shell and its components and extensions should continue working. [ Regression potential ] Gjs is fundamental part of the ubuntu desktop, so any failure of it may cause the desktop not even to boot (because it's being used by gdm too). ** Affects: gjs (Ubuntu) Importance: Medium Assignee: Marco Trevisan (Treviño) (3v1n0) Status: Fix Released ** Affects: gjs (Ubuntu Jammy) Importance: Medium Assignee: Marco Trevisan (Treviño) (3v1n0) Status: In Progress ** Also affects: gjs (Ubuntu Jammy) Importance: Undecided Status: New ** Changed in: gjs (Ubuntu Jammy) Status: New => In Progress ** Changed in: gjs (Ubuntu Jammy) Importance: Undecided => Medium ** Changed in: gjs (Ubuntu Jammy) Assignee: (unassigned) => Marco Trevisan (Treviño) (3v1n0) -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gjs in Ubuntu. https://bugs.launchpad.net/bugs/2023572 Title: SRU gjs 1.72.3 to jammy Status in gjs package in Ubuntu: Fix Released Status in gjs source package in Jammy: In Progress Bug description: [ Impact ] That's the GNOME 42 stable update, including some fixes: https://gitlab.gnome.org/GNOME/gjs/-/commits/1.72.3 [ Test case ] The update is part of GNOME stable updates https://wiki.ubuntu.com/StableReleaseUpdates/GNOME Gjs applications (such as GNOME Maps, GNOME Characters, GNOME Weather...) and GNOME Shell and its components and extensions should continue working. [ Regression potential ] Gjs is fundamental part of the ubuntu desktop, so any failure of it may cause the desktop not even to boot (because it's being used by gdm too). To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gjs/+bug/2023572/+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 2023571] Re: Update to gjs 1.76.1 and SRU it
** Changed in: gjs (Ubuntu) Status: In Progress => Fix Committed ** Changed in: gjs (Ubuntu Lunar) Status: In Progress => Fix Committed -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gjs in Ubuntu. https://bugs.launchpad.net/bugs/2023571 Title: Update to gjs 1.76.1 and SRU it Status in gjs package in Ubuntu: Fix Committed Status in gjs source package in Lunar: Fix Committed Bug description: [ Impact ] That's the current GNOME stable update, including some fixes and translation updates https://gitlab.gnome.org/GNOME/gjs/-/commits/1.76.1 [ Test case ] The update is part of GNOME stable updates https://wiki.ubuntu.com/StableReleaseUpdates/GNOME Gjs applications (such as GNOME Maps, GNOME Characters, GNOME Weather...) and GNOME Shell and its components and extensions should continue working. [ Regression potential ] Gjs is fundamental part of the ubuntu desktop, so any failure of it may cause the desktop not even to boot (because it's being used by gdm too). This update changed fundamentally the memory management of some objects and containers (especially GVariant's), but these changes were already part of gjs released in ubuntu lunar (1.76.0-3). To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gjs/+bug/2023571/+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 2023571] [NEW] Update to gjs 1.76.1 and SRU it
Public bug reported: [ Impact ] That's the current GNOME stable update, including some fixes and translation updates https://gitlab.gnome.org/GNOME/gjs/-/commits/1.76.1 [ Test case ] The update is part of GNOME stable updates https://wiki.ubuntu.com/StableReleaseUpdates/GNOME Gjs applications (such as GNOME Maps, GNOME Characters, GNOME Weather...) and GNOME Shell and its components and extensions should continue working. [ Regression potential ] Gjs is fundamental part of the ubuntu desktop, so any failure of it may cause the desktop not even to boot (because it's being used by gdm too). This update changed fundamentally the memory management of some objects and containers (especially GVariant's), but these changes were already part of gjs released in ubuntu lunar (1.76.0-3). ** Affects: gjs (Ubuntu) Importance: Medium Assignee: Marco Trevisan (Treviño) (3v1n0) Status: In Progress ** Affects: gjs (Ubuntu Lunar) Importance: Medium Assignee: Marco Trevisan (Treviño) (3v1n0) Status: In Progress ** Also affects: gjs (Ubuntu Lunar) Importance: Undecided Status: New ** Changed in: gjs (Ubuntu Lunar) Status: New => Fix Committed ** Changed in: gjs (Ubuntu Lunar) Importance: Undecided => Medium ** Changed in: gjs (Ubuntu Lunar) Assignee: (unassigned) => Marco Trevisan (Treviño) (3v1n0) ** Changed in: gjs (Ubuntu Lunar) Status: Fix Committed => In Progress -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gjs in Ubuntu. https://bugs.launchpad.net/bugs/2023571 Title: Update to gjs 1.76.1 and SRU it Status in gjs package in Ubuntu: In Progress Status in gjs source package in Lunar: In Progress Bug description: [ Impact ] That's the current GNOME stable update, including some fixes and translation updates https://gitlab.gnome.org/GNOME/gjs/-/commits/1.76.1 [ Test case ] The update is part of GNOME stable updates https://wiki.ubuntu.com/StableReleaseUpdates/GNOME Gjs applications (such as GNOME Maps, GNOME Characters, GNOME Weather...) and GNOME Shell and its components and extensions should continue working. [ Regression potential ] Gjs is fundamental part of the ubuntu desktop, so any failure of it may cause the desktop not even to boot (because it's being used by gdm too). This update changed fundamentally the memory management of some objects and containers (especially GVariant's), but these changes were already part of gjs released in ubuntu lunar (1.76.0-3). To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gjs/+bug/2023571/+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 2013126] Re: file chooser dialog doesn't respect system theme
** Changed in: xdg-desktop-portal-gnome (Ubuntu) Status: Confirmed => Won't Fix ** Also affects: libadwaita-1 (Ubuntu Jammy) Importance: Undecided Status: New ** Also affects: xdg-desktop-portal-gnome (Ubuntu Jammy) Importance: Undecided Status: New ** No longer affects: libadwaita-1 (Ubuntu Jammy) ** No longer affects: xdg-desktop-portal-gnome (Ubuntu Jammy) ** Also affects: libadwaita-1 (Ubuntu Lunar) Importance: Undecided Status: New ** Also affects: xdg-desktop-portal-gnome (Ubuntu Lunar) Importance: Undecided Status: New ** No longer affects: xdg-desktop-portal-gnome (Ubuntu Lunar) ** Changed in: libadwaita-1 (Ubuntu Lunar) Status: New => Fix Committed ** Changed in: libadwaita-1 (Ubuntu Lunar) Importance: Undecided => High ** Changed in: libadwaita-1 (Ubuntu Lunar) Assignee: (unassigned) => Marco Trevisan (Treviño) (3v1n0) -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to xdg-desktop-portal-gnome in Ubuntu. https://bugs.launchpad.net/bugs/2013126 Title: file chooser dialog doesn't respect system theme Status in libadwaita-1 package in Ubuntu: Fix Released Status in xdg-desktop-portal-gnome package in Ubuntu: Won't Fix Status in libadwaita-1 source package in Lunar: Fix Committed Bug description: The file chooser dialog uses the default (light) style, even when the dark style is enabled. ProblemType: Bug DistroRelease: Ubuntu 23.04 Package: xdg-desktop-portal-gnome 44~beta-1ubuntu1 ProcVersionSignature: Ubuntu 6.2.0-18.18-generic 6.2.6 Uname: Linux 6.2.0-18-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.26.0-0ubuntu2 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Tue Mar 28 21:08:55 2023 InstallationDate: Installed on 2022-09-07 (202 days ago) InstallationMedia: Ubuntu 22.04.1 LTS "Jammy Jellyfish" - Release amd64 (20220809.1) SourcePackage: xdg-desktop-portal-gnome UpgradeStatus: Upgraded to lunar on 2023-03-28 (0 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libadwaita-1/+bug/2013126/+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
