| 2024-03-26 12:38:26 |
Matthew Hagemann |
bug |
|
|
added bug |
| 2024-03-26 12:39:46 |
Matthew Hagemann |
description |
These 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 as a newly created user, and thus not own the file in /run/gnome-initial-setup and always exit here.
My workaround in provd is to update the ownership of the file in /run/gnome-initial-setup to the newly created user before booting into their session, allowing this check to pass.
ProblemType: Bug
DistroRelease: Ubuntu 23.10
Package: gnome-initial-setup 45.0-1ubuntu3 [modified: usr/share/applications/gnome-initial-setup.desktop]
ProcVersionSignature: Ubuntu 6.5.0-26.26-generic 6.5.13
Uname: Linux 6.5.0-26-generic x86_64
ApportVersion: 2.28.0-0ubuntu1
Architecture: amd64
CasperMD5CheckResult: unknown
CurrentDesktop: ubuntu:GNOME
Date: Tue Mar 26 14:31:52 2024
InstallationDate: Installed on 2024-03-02 (24 days ago)
InstallationMedia: Ubuntu 23.10.1 "Mantic Minotaur" - Release amd64 (20231016.1)
ProcEnviron:
LANG=en_US.UTF-8
PATH=(custom, no user)
SHELL=/usr/bin/zsh
TERM=xterm-256color
XDG_RUNTIME_DIR=<set>
SourcePackage: gnome-initial-setup
UpgradeStatus: No upgrade log present (probably fresh install) |
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 as a newly created user, and thus not own the file in /run/gnome-initial-setup and always exit here.
My workaround in provd is to update the ownership of the file in /run/gnome-initial-setup to the newly created user before booting into their session, allowing this check to pass.
ProblemType: Bug
DistroRelease: Ubuntu 23.10
Package: gnome-initial-setup 45.0-1ubuntu3 [modified: usr/share/applications/gnome-initial-setup.desktop]
ProcVersionSignature: Ubuntu 6.5.0-26.26-generic 6.5.13
Uname: Linux 6.5.0-26-generic x86_64
ApportVersion: 2.28.0-0ubuntu1
Architecture: amd64
CasperMD5CheckResult: unknown
CurrentDesktop: ubuntu:GNOME
Date: Tue Mar 26 14:31:52 2024
InstallationDate: Installed on 2024-03-02 (24 days ago)
InstallationMedia: Ubuntu 23.10.1 "Mantic Minotaur" - Release amd64 (20231016.1)
ProcEnviron:
LANG=en_US.UTF-8
PATH=(custom, no user)
SHELL=/usr/bin/zsh
TERM=xterm-256color
XDG_RUNTIME_DIR=<set>
SourcePackage: gnome-initial-setup
UpgradeStatus: No upgrade log present (probably fresh install) |
|
| 2024-03-26 12:41:24 |
Matthew Hagemann |
description |
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 as a newly created user, and thus not own the file in /run/gnome-initial-setup and always exit here.
My workaround in provd is to update the ownership of the file in /run/gnome-initial-setup to the newly created user before booting into their session, allowing this check to pass.
ProblemType: Bug
DistroRelease: Ubuntu 23.10
Package: gnome-initial-setup 45.0-1ubuntu3 [modified: usr/share/applications/gnome-initial-setup.desktop]
ProcVersionSignature: Ubuntu 6.5.0-26.26-generic 6.5.13
Uname: Linux 6.5.0-26-generic x86_64
ApportVersion: 2.28.0-0ubuntu1
Architecture: amd64
CasperMD5CheckResult: unknown
CurrentDesktop: ubuntu:GNOME
Date: Tue Mar 26 14:31:52 2024
InstallationDate: Installed on 2024-03-02 (24 days ago)
InstallationMedia: Ubuntu 23.10.1 "Mantic Minotaur" - Release amd64 (20231016.1)
ProcEnviron:
LANG=en_US.UTF-8
PATH=(custom, no user)
SHELL=/usr/bin/zsh
TERM=xterm-256color
XDG_RUNTIME_DIR=<set>
SourcePackage: gnome-initial-setup
UpgradeStatus: No upgrade log present (probably fresh install) |
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 as a newly created user, and thus not own the file in /run/gnome-initial-setup and always exit here.
My workaround in provd is to update the ownership of the file in /run/gnome-initial-setup to the newly created user before booting into their session, allowing this check to pass.
Without this workaround, several settings applied in the gnome-initial-setup new user flow (mainly a11y) are not persisted to the new user after the gis process concludes.
ProblemType: Bug
DistroRelease: Ubuntu 23.10
Package: gnome-initial-setup 45.0-1ubuntu3 [modified: usr/share/applications/gnome-initial-setup.desktop]
ProcVersionSignature: Ubuntu 6.5.0-26.26-generic 6.5.13
Uname: Linux 6.5.0-26-generic x86_64
ApportVersion: 2.28.0-0ubuntu1
Architecture: amd64
CasperMD5CheckResult: unknown
CurrentDesktop: ubuntu:GNOME
Date: Tue Mar 26 14:31:52 2024
InstallationDate: Installed on 2024-03-02 (24 days ago)
InstallationMedia: Ubuntu 23.10.1 "Mantic Minotaur" - Release amd64 (20231016.1)
ProcEnviron:
LANG=en_US.UTF-8
PATH=(custom, no user)
SHELL=/usr/bin/zsh
TERM=xterm-256color
XDG_RUNTIME_DIR=<set>
SourcePackage: gnome-initial-setup
UpgradeStatus: No upgrade log present (probably fresh install) |
|
| 2024-07-10 14:55:44 |
Mantas Kriaučiūnas |
bug |
|
|
added subscriber Baltix GNU/Linux system developers |
| 2024-07-10 14:55:48 |
Launchpad Janitor |
gnome-initial-setup (Ubuntu): status |
New |
Confirmed |
|
| 2024-07-10 14:55:52 |
Mantas Kriaučiūnas |
bug |
|
|
added subscriber Mantas Kriaučiūnas |
