** Description changed:
+ [ Impact ]
+
While using Gnome-Initial-Setup launched from GDM (when no user > 1000
is present on the machine), no background is set on GNOME-Greeter,
leading to a solid blue background wallpaper.
- Could we set the background here to the Ubuntu default? By upda
** Description changed:
[ Impact ]
While using Gnome-Initial-Setup launched from GDM (when no user > 1000
is present on the machine), no background is set on GNOME-Greeter,
leading to a solid blue background wallpaper.
Gnome-Initial-Setup is currently used on OEM shipped devices to
Tested version 24.04.5 from https://launchpad.net/ubuntu/+source/ubuntu-
settings/24.04.5
Following the first few steps in the testplan
https://wiki.ubuntu.com/DesktopTeam/TestPlans/GnomeInitialSetup I:
- Created a 24.04.1 VM and preformed normal installation
- Installed ubuntu-settings 24.04.5
-
Public bug reported:
There is a check in the copy worker that looks to see if the user
running the copy worker owns the files it is trying to copy
```
if (!g_file_query_exists (src, NULL) ||
!file_is_ours (src))
exit (EXIT_SUCCESS);
```
From all my testing, the copy worker will always run
Hi Nathan :)
Sorry, I meant folder, not file.
The code is checking the ownership of the home directory of gnome-
initial-setup which is /run/gnome-initial-setup, which is where the
files we are trying to copy live:
```
src = g_file_new_for_path (initial_setup_homedir);
if (!g_file_query_exists
Public bug reported:
While using Gnome-Initial-Setup launched from GDM (when no user > 1000
is present on the machine), no background is set on GNOME-Greeter,
leading to a solid blue background wallpaper.
Could we set the background here to the Ubuntu default? By updating
/usr/share/glib-2.0/sche
** Changed in: ubuntu-settings (Ubuntu)
Milestone: None => ubuntu-24.10
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2077741
Title:
No default background set for GNOME-Greeter
To manage notif
Public bug reported:
I kept seeing dbus-daemon denials in the journal while testing setting
the system locale via Gnome Initial Setup:
```
dbus-daemon[971]: [system] Rejected send message, 3 matched rules;
type="method_call", sender=":1.112" (uid=118 pid=2985
comm="/usr/libexec/gnome-initial-se
,
preventing you from being able to ever download these additional
language packs.
** Affects: gnome-initial-setup (Ubuntu)
Importance: Undecided
Assignee: Matthew Hagemann (matt-hagemann)
Status: New
** Changed in: gnome-initial-setup (Ubuntu)
Assignee: (unassigned
/tree/debian/rules?h=ubuntu/oracular
This is causing pkexec to sit attempting to close 1073741816 file descriptors
which takes several minutes every time it was called to install a lang pack.
** Affects: gnome-initial-setup (Ubuntu)
Importance: Undecided
Assignee: Matthew Hagemann (matt
Public bug reported:
I've been testing in plucky, and see the start-here-symbolic.svg is not
rendering on the language page correctly. yaru-theme-icon is present,
and I can open /usr/share/icons/Yaru/scalable/places/start-here-
symbolic.svg in an image viewer without any issue.
All other svg's ar
Public bug reported:
Plucky bug:
The summary page current runs the following code after language packs
are installed:
```
if (act_user_is_loaded (user))
act_user_set_language (user, locale);
else
g_signal_connect (user,
Hey, yes, with that systemd patch SetLocale works again. Keyboard is
still blocked, but my understanding is for good reason.
** Summary changed:
- SetLocale and SetX11Keyboard auto-denied on Ubuntu
+ SetX11Keyboard auto-denied on Ubuntu
** Description changed:
I kept seeing dbus-daemon denial
13 matches
Mail list logo
