Comment 71 for bug 1875062

Revision history for this message
Benjamin Drung (bdrung) wrote (last edit ):

I have a working patch for ubiquity that sets the GNOME keyboard there as well. Next steps (next week):
* finish test cases
* test Kubuntu (KDE)
* then create merge request

I created bug #1968354 for open-vm-tools to make the udev trigger more precise.

Site notes
==========

If you do following steps in the live system:
```
sudo gedit # close without any change
ps auxff | grep dconf-servic[e]
ubiquity --debug gtk_ui
```

`sudo gedit` will start a dconf-service process owned by root. Then ubiquity will launch another dconf-service process owned by ubuntu:

```
ubuntu@ubuntu:~$ ps aux | grep dconf-servic[e]
ubuntu 1596 0.0 0.1 156984 6020 ? Ssl 17:28 0:00 /usr/libexec/dconf-service
root 5615 0.0 0.1 156856 5708 ? Sl 17:29 0:00 /usr/libexec/dconf-service
ubuntu 5998 0.0 0.1 156956 6060 ? Sl 17:29 0:00 /usr/libexec/dconf-service
```

In that case, gsettings changes by ubiquity will be send to the "wrong" dconf-service and the gnome-shell will not get these changes.

Solution: Run ubiquity the same way the ubiquity.desktop runs it:
```
sudo --preserve-env=DBUS_SESSION_BUS_ADDRESS,XDG_DATA_DIRS,XDG_RUNTIME_DIR sh -c 'ubiquity --debug gtk_ui'
```

Note 2: I also run into bug #1755452 during testing.