Recent Pop_OS updates have been changing my GNOME settings

[TriggerDingus]

Distribution (run cat /etc/os-release): NAME="Pop!_OS" VERSION="22.04 LTS" ID=pop ID_LIKE="ubuntu debian" PRETTY_NAME="Pop!_OS 22.04 LTS" VERSION_ID="22.04"

Related Application and/or Package Version (run apt policy $PACKAGE NAME): N/A

Issue/Bug Description: When receiving relatively recent Pop_OS updates from the Pop Shop (within the past month or three), I've noticed they are altering some of my Gnome settings. These are the settings I know are being changed, because with each update I am required to manually change things back. This issue exists on both of my laptops (a Darter Pro and a Gazelle):

• I don't have the Launcher, Apps or Workspaces icons on my dock, but with the recent Pop! updates have been forcing them back onto my dock requiring me to manually remove them again.
• Within my power settings, I turn OFF Automatic Suspend if my machines are on wall power, however, recent Pop! updates have been forcing Automatic Suspend for both battery and wall power, wiping out my personal settings.

Steps to reproduce (if you know): Described above

Expected behavior: My personal settings should never be changed during normal maintenance fixes, which has been the practice in the past. Something changed recently where that hasn't been the case?

Other Notes:

[mmstick]

System updates only change system files. The package manager cannot touch files in your home folder. My guess is that these settings aren't getting saved.

[TriggerDingus]

Not sure I understand what you mean by not getting saved. Once the these settings get changed by (or during) an OS update, they get changed back to default and then I have to go into settings and change them back the way I've had my settings for more than two years. There's no 'saving' involved from my end while making these updates, though perhaps there's a recent change in the desktop that can explain this behavior. As I mentioned, this is happening on two machines and both are experiencing the same issue but only during updates.

[TriggerDingus]

I will capture screen videos during my next few OS updates and I'll post it when I capture the described behavior. I applied a smaller update today but the issue didn't occur during that one.

[boenshao]

I can confirm the same observation, the suspend setting changes after update.

[jacobgkau]

The default suspend settings changed recently: https://github.com/pop-os/default-settings/pull/156

gsettings overrides (defaults) should not affect any settings that you've manually changed. If you had not changed the four affected settings from their defaults in any particular user account, then they would "change" as the defaults changed.

The default used to be not suspending on wall power or battery power, and now the default is to suspend after 30 minutes on either wall power or battery power. This sounds like it would explain your power settings changing, as that would not have been "wiping out your personal settings" but changing a setting that was still set to its default.

This change to the defaults was made to comply with California Title 20 regulations.

[TriggerDingus]

The default suspend settings changed recently: pop-os/default-settings#156

gsettings overrides (defaults) should not affect any settings that you've manually changed. If you had not changed the four affected settings from their defaults in any particular user account, then they would "change" as the defaults changed.

The default used to be not suspending on wall power or battery power, and now the default is to suspend after 30 minutes on either wall power or battery power. This sounds like it would explain your power settings changing, as that would not have been "wiping out your personal settings" but changing a setting that was still set to its default.

This change to the defaults was made to comply with California Title 20 regulations.

I hear what you're saying. The issue is I've had to manually change it back to NOT suspend, however, my settings have been changed back after updates. So, this setting wasn't at it's default at least for the last several OS updates. I'll try and capture the behavior in a video and post here.

[mmstick]

Is your setting surviving reboots?

[TriggerDingus]

Yes, no problems during reboots.

[TriggerDingus]

Leaving this video for future reference only. I took this capture since I saw a POP OS update to apply, however, this one did NOT change my settings. There's a couple frames that shows the updates to be applied, which could be a helpful comparison when I do make a video that captures an update changing my settings.

https://odysee.com/DID-NOT-change-settings-2022-09-11:6

[TriggerDingus]

Leaving these videos for reference only. Two more updates applied today but these didn't change my settings either. Seems like since I made the issue report, the bugs are keeping a low profile..

https://odysee.com/Screencast-2022-09-13-10-41-38:0 https://odysee.com/Screencast-2022-09-13-10-36-52:9

[mmstick]

It's probably a specific package.

[TriggerDingus]

This is a weird one. I've been capturing screen video on my primary machine but I happened to use my 2nd machine (a Darter Pro) at the coffee shop today and when I powered it up, the issue was there. I have updates to apply on it, but I'm holding off in the hopes maybe you can let me know if there's a way to see the last updates applied? I recall the last time I used it, which was days ago, I applied some updates but apparently hadn't rebooted to see if the issue happened.

Attached is a screen capture, which denotes the extra icons pushed back onto my dock as well as the Auto-Suspend settings changed back to default.

[mmstick]

/var/log/apt/history.log contains history of package operations and the dates they were applied

[TriggerDingus]

I suspect there's a clue buried in my last update on that machine, which appears to have been 9/7/22. Here's the log. history.log

[mmstick]

It could be the pop-default-settings update on 9/5.

[mmstick]

I'm not seeing anything in pop-default-settings that would cause this though.

[TriggerDingus]

That might be. I searched for that update in my primary machine history.log and the last update was 9/1/22 which might explain why I haven't been able to reproduce it recently in my videos.

[mmstick]

It must be pop-desktop's gsettings override. I'm not sure how it would be overriding a user-level config though.

[TriggerDingus]

I see I posted this issue on/about 9/8 so I must have experienced the issue on this machine around that time. For reference, here is the log info from my primary machine around that time:

Start-Date: 2022-09-03 12:42:30 Commandline: packagekit role='update-packages' Requested-By: bob (1000) Upgrade: brave-browser:amd64 (1.43.88, 1.43.89) End-Date: 2022-09-03 12:42:36

Start-Date: 2022-09-05 13:24:51 Commandline: packagekit role='update-packages' Requested-By: bob (1000) Upgrade: gjs:amd64 (1.72.0-3~ubuntu22.04.2, 1.72.2-0ubuntu1), libgjs0g:amd64 (1.72.0-3~ubuntu22.04.2, 1.72.2-0ubuntu1), gnome-remote-desktop:amd64 (42.3-0ubuntu1, 42.4-0ubuntu1) End-Date: 2022-09-05 13:24:52

Start-Date: 2022-09-06 17:52:53 Commandline: packagekit role='update-packages' Requested-By: bob (1000) Upgrade: firefox-locale-ar:amd64 (103.0~1658935678~22.04~6ca92d7, 104.0.1~1661960476~22.04~f77767e), firefox-locale-de:amd64 (103.0~1658935678~22.04~6ca92d7, 104.0.1~1661960476~22.04~f77767e), firefox-locale-en:amd64 (103.0~1658935678~22.04~6ca92d7, 104.0.1~1661960476~22.04~f77767e), firefox-locale-es:amd64 (103.0~1658935678~22.04~6ca92d7, 104.0.1~1661960476~22.04~f77767e), firefox-locale-fr:amd64 (103.0~1658935678~22.04~6ca92d7, 104.0.1~1661960476~22.04~f77767e), firefox-locale-it:amd64 (103.0~1658935678~22.04~6ca92d7, 104.0.1~1661960476~22.04~f77767e), firefox-locale-ja:amd64 (103.0~1658935678~22.04~6ca92d7, 104.0.1~1661960476~22.04~f77767e), firefox-locale-pt:amd64 (103.0~1658935678~22.04~6ca92d7, 104.0.1~1661960476~22.04~f77767e), firefox-locale-ru:amd64 (103.0~1658935678~22.04~6ca92d7, 104.0.1~1661960476~22.04~f77767e), hidpi-daemon:amd64 (18.04.6~1616430980~22.04~8f165bb, 18.04.6~1661971145~22.04~0ea00f5), firefox:amd64 (103.0~1658935678~22.04~6ca92d7, 104.0.1~1661960476~22.04~f77767e), pop-shell:amd64 (1.1.0~1661535383~22.04~4c03091, 1.1.0~1662054060~22.04~4520e78), firefox-locale-zh-hans:amd64 (103.0~1658935678~22.04~6ca92d7, 104.0.1~1661960476~22.04~f77767e), firefox-locale-zh-hant:amd64 (103.0~1658935678~22.04~6ca92d7, 104.0.1~1661960476~22.04~f77767e) End-Date: 2022-09-06 17:52:55

Start-Date: 2022-09-07 13:09:43 Commandline: packagekit role='update-packages' Requested-By: bob (1000) Upgrade: dmidecode:amd64 (3.3-3, 3.3-3ubuntu0.1) End-Date: 2022-09-07 13:09:43

[TriggerDingus]

It just happened on my primary machine as well. I applied an update the morning, rebooted, and the issue appeared. Here's a screen image as well as the last couple days of my update history.

Start-Date: 2022-09-13 10:34:05 Commandline: packagekit role='update-packages' Requested-By: bob (1000) Upgrade: firefox-locale-ar:amd64 (104.0.1~1661960476~22.04~f77767e, 104.0.2~1662490162~22.04~faed4ab), firefox-locale-de:amd64 (104.0.1~1661960476~22.04~f77767e, 104.0.2~1662490162~22.04~faed4ab), firefox-locale-en:amd64 (104.0.1~1661960476~22.04~f77767e, 104.0.2~1662490162~22.04~faed4ab), firefox-locale-es:amd64 (104.0.1~1661960476~22.04~f77767e, 104.0.2~1662490162~22.04~faed4ab), firefox-locale-fr:amd64 (104.0.1~1661960476~22.04~f77767e, 104.0.2~1662490162~22.04~faed4ab), firefox-locale-it:amd64 (104.0.1~1661960476~22.04~f77767e, 104.0.2~1662490162~22.04~faed4ab), firefox-locale-ja:amd64 (104.0.1~1661960476~22.04~f77767e, 104.0.2~1662490162~22.04~faed4ab), firefox-locale-pt:amd64 (104.0.1~1661960476~22.04~f77767e, 104.0.2~1662490162~22.04~faed4ab), firefox-locale-ru:amd64 (104.0.1~1661960476~22.04~f77767e, 104.0.2~1662490162~22.04~faed4ab), libnvidia-common-515:amd64 (515.48.07-1pop0~1657640780~22.04~e863eed, 515.65.01-1pop0~1663007364~22.04~9bd887b), libnvidia-fbc1-515:amd64 (515.48.07-1pop0~1657640780~22.04~e863eed, 515.65.01-1pop0~1663007364~22.04~9bd887b), libnvidia-fbc1-515:i386 (515.48.07-1pop0~1657640780~22.04~e863eed, 515.65.01-1pop0~1663007364~22.04~9bd887b), system76-firmware-daemon:amd64 (1.0.43~1661806894~22.04~b9c7553, 1.0.44~1662572473~22.04~a444e4f), libnvidia-gl-515:amd64 (515.48.07-1pop0~1657640780~22.04~e863eed, 515.65.01-1pop0~1663007364~22.04~9bd887b), libnvidia-gl-515:i386 (515.48.07-1pop0~1657640780~22.04~e863eed, 515.65.01-1pop0~1663007364~22.04~9bd887b), pop-launcher:amd64 (1.2.1~1661884387~22.04~4ddcdec, 1.2.1~1662488179~22.04~6e2fa02), libnvidia-extra-515:amd64 (515.48.07-1pop0~1657640780~22.04~e863eed, 515.65.01-1pop0~1663007364~22.04~9bd887b), nvidia-compute-utils-515:amd64 (515.48.07-1pop0~1657640780~22.04~e863eed, 515.65.01-1pop0~1663007364~22.04~9bd887b), nvidia-dkms-515:amd64 (515.48.07-1pop0~1657640780~22.04~e863eed, 515.65.01-1pop0~1663007364~22.04~9bd887b), nvidia-driver-515:amd64 (515.48.07-1pop0~1657640780~22.04~e863eed, 515.65.01-1pop0~1663007364~22.04~9bd887b), pop-desktop:amd64 (1.6.0~1661536842~22.04~79a6983, 1.6.0~1662996938~22.04~b7f18a0), xserver-xorg-video-amdgpu:amd64 (22.0.0-1build1, 22.0.0-1ubuntu0.1), libqt5core5a:amd64 (5.15.3+dfsg-2ubuntu0.1, 5.15.3+dfsg-2ubuntu0.2), qt5-gtk-platformtheme:amd64 (5.15.3+dfsg-2ubuntu0.1, 5.15.3+dfsg-2ubuntu0.2), libnvidia-encode-515:amd64 (515.48.07-1pop0~1657640780~22.04~e863eed, 515.65.01-1pop0~1663007364~22.04~9bd887b), libnvidia-encode-515:i386 (515.48.07-1pop0~1657640780~22.04~e863eed, 515.65.01-1pop0~1663007364~22.04~9bd887b), nvidia-utils-515:amd64 (515.48.07-1pop0~1657640780~22.04~e863eed, 515.65.01-1pop0~1663007364~22.04~9bd887b), xserver-xorg-video-nvidia-515:amd64 (515.48.07-1pop0~1657640780~22.04~e863eed, 515.65.01-1pop0~1663007364~22.04~9bd887b), alsa-ucm-conf:amd64 (1.2.7.2-1pop1~1659622258~22.04~5db19ea, 1.2.7.2-1pop1~1663000370~22.04~c9d3378), libqt5network5:amd64 (5.15.3+dfsg-2ubuntu0.1, 5.15.3+dfsg-2ubuntu0.2), pop-session:amd64 (5.0.0~1654602899~22.04~4bbfadd, 5.0.0~1662569841~22.04~1c78668), libqt5dbus5:amd64 (5.15.3+dfsg-2ubuntu0.1, 5.15.3+dfsg-2ubuntu0.2), zlib1g-dev:amd64 (1:1.2.11.dfsg-2ubuntu9, 1:1.2.11.dfsg-2ubuntu9.1), libpoppler-cpp0v5:amd64 (22.02.0-2, 22.02.0-2ubuntu0.1), libqt5test5:amd64 (5.15.3+dfsg-2ubuntu0.1, 5.15.3+dfsg-2ubuntu0.2), libnvidia-decode-515:amd64 (515.48.07-1pop0~1657640780~22.04~e863eed, 515.65.01-1pop0~1663007364~22.04~9bd887b), libnvidia-decode-515:i386 (515.48.07-1pop0~1657640780~22.04~e863eed, 515.65.01-1pop0~1663007364~22.04~9bd887b), libqt5widgets5:amd64 (5.15.3+dfsg-2ubuntu0.1, 5.15.3+dfsg-2ubuntu0.2), poppler-utils:amd64 (22.02.0-2, 22.02.0-2ubuntu0.1), firefox:amd64 (104.0.1~1661960476~22.04~f77767e, 104.0.2~1662490162~22.04~faed4ab), libqt5gui5:amd64 (5.15.3+dfsg-2ubuntu0.1, 5.15.3+dfsg-2ubuntu0.2), nvidia-kernel-common-515:amd64 (515.48.07-1pop0~1657640780~22.04~e863eed, 515.65.01-1pop0~1663007364~22.04~9bd887b), gnome-shell-extension-cosmic-dock:amd64 (72~ubuntu2pop0~1657899512~22.04~0544fb1, 72~ubuntu2pop0~1663007108~22.04~ca15539), libqt5printsupport5:amd64 (5.15.3+dfsg-2ubuntu0.1, 5.15.3+dfsg-2ubuntu0.2), libpoppler-glib8:amd64 (22.02.0-2, 22.02.0-2ubuntu0.1), libqt5xml5:amd64 (5.15.3+dfsg-2ubuntu0.1, 5.15.3+dfsg-2ubuntu0.2), libqt5opengl5:amd64 (5.15.3+dfsg-2ubuntu0.1, 5.15.3+dfsg-2ubuntu0.2), libpoppler118:amd64 (22.02.0-2, 22.02.0-2ubuntu0.1), libqt5sql5:amd64 (5.15.3+dfsg-2ubuntu0.1, 5.15.3+dfsg-2ubuntu0.2), pop-shell:amd64 (1.1.0~1662054060~22.04~4520e78, 1.1.0~1662496692~22.04~91a8599), system76-driver:amd64 (20.04.63~1661882542~22.04~a76f488, 20.04.64~1662586768~22.04~f8a17ba), libnvidia-cfg1-515:amd64 (515.48.07-1pop0~1657640780~22.04~e863eed, 515.65.01-1pop0~1663007364~22.04~9bd887b), libqt5sql5-sqlite:amd64 (5.15.3+dfsg-2ubuntu0.1, 5.15.3+dfsg-2ubuntu0.2), nvidia-kernel-source-515:amd64 (515.48.07-1pop0~1657640780~22.04~e863eed, 515.65.01-1pop0~1663007364~22.04~9bd887b), libnvidia-compute-515:amd64 (515.48.07-1pop0~1657640780~22.04~e863eed, 515.65.01-1pop0~1663007364~22.04~9bd887b), libnvidia-compute-515:i386 (515.48.07-1pop0~1657640780~22.04~e863eed, 515.65.01-1pop0~1663007364~22.04~9bd887b), zlib1g:amd64 (1:1.2.11.dfsg-2ubuntu9, 1:1.2.11.dfsg-2ubuntu9.1), zlib1g:i386 (1:1.2.11.dfsg-2ubuntu9, 1:1.2.11.dfsg-2ubuntu9.1), system76-driver-nvidia:amd64 (20.04.63~1661882542~22.04~a76f488, 20.04.64~1662586768~22.04~f8a17ba), intel-microcode:amd64 (3.20220510.0ubuntu0.22.04.1, 3.20220809.0ubuntu0.22.04.1), firefox-locale-zh-hans:amd64 (104.0.1~1661960476~22.04~f77767e, 104.0.2~1662490162~22.04~faed4ab), firefox-locale-zh-hant:amd64 (104.0.1~1661960476~22.04~f77767e, 104.0.2~1662490162~22.04~faed4ab) End-Date: 2022-09-13 10:35:06

Start-Date: 2022-09-13 10:36:03 Commandline: packagekit role='update-packages' Requested-By: bob (1000) Upgrade: torbrowser-launcher:amd64 (0.3.3-6ubuntu1, 0.3.3-6ubuntu1.22.04.1) End-Date: 2022-09-13 10:36:04

Start-Date: 2022-09-13 21:17:14 Commandline: packagekit role='update-packages' Requested-By: bob (1000) Upgrade: libgdk-pixbuf2.0-bin:amd64 (2.42.8+dfsg-1, 2.42.8+dfsg-1ubuntu0.1), gir1.2-gdkpixbuf-2.0:amd64 (2.42.8+dfsg-1, 2.42.8+dfsg-1ubuntu0.1), libgdk-pixbuf-2.0-0:amd64 (2.42.8+dfsg-1, 2.42.8+dfsg-1ubuntu0.1), libgdk-pixbuf2.0-common:amd64 (2.42.8+dfsg-1, 2.42.8+dfsg-1ubuntu0.1) End-Date: 2022-09-13 21:17:16

Start-Date: 2022-09-13 21:31:01 Commandline: /usr/sbin/synaptic Requested-By: bob (1000) Purge: librewolf:amd64 (99.0.1-2) End-Date: 2022-09-13 21:31:01

Start-Date: 2022-09-14 09:24:22 Commandline: packagekit role='remove-packages' Requested-By: bob (1000) Remove: firefox-locale-ar:amd64 (104.0.2~1662490162~22.04~faed4ab), firefox-locale-de:amd64 (104.0.2~1662490162~22.04~faed4ab), firefox-locale-en:amd64 (104.0.2~1662490162~22.04~faed4ab), firefox-locale-es:amd64 (104.0.2~1662490162~22.04~faed4ab), firefox-locale-fr:amd64 (104.0.2~1662490162~22.04~faed4ab), firefox-locale-it:amd64 (104.0.2~1662490162~22.04~faed4ab), firefox-locale-ja:amd64 (104.0.2~1662490162~22.04~faed4ab), firefox-locale-pt:amd64 (104.0.2~1662490162~22.04~faed4ab), firefox-locale-ru:amd64 (104.0.2~1662490162~22.04~faed4ab), firefox:amd64 (104.0.2~1662490162~22.04~faed4ab), firefox-locale-zh-hans:amd64 (104.0.2~1662490162~22.04~faed4ab), firefox-locale-zh-hant:amd64 (104.0.2~1662490162~22.04~faed4ab) End-Date: 2022-09-14 09:24:23

Start-Date: 2022-09-14 09:26:15 Commandline: packagekit role='update-packages' Requested-By: bob (1000) Upgrade: fd-find:amd64 (8.3.1-1, 8.3.1-1ubuntu0.1) End-Date: 2022-09-14 09:26:15

[TriggerDingus]

As an FYI, you see in the history that I removed Firefox. This is another indication of the problems because it also forced Firefox as my default browser and Firefox is never my default browser. After the update, I removed Firefox and set my default browser back to Librewolf.

[TriggerDingus]

Just an update... Since my last post 19 days ago, I hesitantly suggest I haven't experienced this issue since so I'm feeling like something was fixed in recent updates? I've applied numerous system updates since then, so I'm feeling pretty good about the fact the issue was found and patched?

[TriggerDingus]

I spoke too soon! The issue just happened again on my Darter Pro.

Here are the last few updates:

Start-Date: 2022-10-05 14:48:50 Commandline: packagekit role='update-packages' Requested-By: bob (1000) Upgrade: evolution-plugins:amd64 (3.44.1-0ubuntu1, 3.44.4-0ubuntu1), libevolution:amd64 (3.44.1-0ubuntu1, 3.44.4-0ubuntu1), evolution-plugin-pstimport:amd64 (3.44.1-0ubuntu1, 3.44.4-0ubuntu1), evolution-plugin-bogofilter:amd64 (3.44.1-0ubuntu1, 3.44.4-0ubuntu1), evolution:amd64 (3.44.1-0ubuntu1, 3.44.4-0ubuntu1), evolution-common:amd64 (3.44.1-0ubuntu1, 3.44.4-0ubuntu1) End-Date: 2022-10-05 14:48:53

Start-Date: 2022-10-05 14:49:34 Commandline: packagekit role='update-packages' Requested-By: bob (1000) Upgrade: isc-dhcp-common:amd64 (4.4.1-2.3ubuntu2.2, 4.4.1-2.3ubuntu2.3), isc-dhcp-client:amd64 (4.4.1-2.3ubuntu2.2, 4.4.1-2.3ubuntu2.3), librewolf:amd64 (105.0.1-1, 105.0.2-1), ubuntu-advantage-tools:amd64 (27.10.1~22.04.1, 27.11.2~22.04.1) End-Date: 2022-10-05 14:49:39

Start-Date: 2022-10-08 16:01:52 Commandline: packagekit role='update-packages' Requested-By: bob (1000) Upgrade: librewolf:amd64 (105.0.2-1, 105.0.3-1), brave-browser:amd64 (1.44.105, 1.44.108) End-Date: 2022-10-08 16:02:02

[jacobgkau]

None of those updates would be related to COSMIC or GNOME. Are you sure the settings resets are actually correlated to installing updates, and not being caused by something else?

[TriggerDingus]

At least one, if not two other people seem to concur with my observations. (see above) I'm just trying to document the issue. If I'm doing something to change these settings, I would have no earthly idea what it would be, especially that would touch system settings that I never play with. I don't install or deinstall software - my current software set has been pretty static over the past year or so and so I don't think it has to do with me playing with unknown software. My two systems are very static - the only changes that occur with my systems (that I'm aware of ) happens when I apply updates. I do very basic computing - just business-related stuff.

As a former developer myself I understand your perspective and believe in the theory of PEBMAC - I just have no other explanation on my end. I'm a very boring user - I don't do much and I never change anything. I have stuff like I want it, so I don't monkey with it other than regular updates.

[jacobgkau]

At least one, if not two other people seem to concur with my observations. (see above)

The issue originally coincided with an intentional default setting change, and you seem to be the only one still talking about changes happening now. That's why I wanted to check if there might be something else going on than just the updates.

I'm not suggesting that you're intentionally changing the settings, but I'm wondering if some other piece of software on your system might be doing it. Again, the list of packages you provided for the most recent occurrence consists of Evolution, a DHCP client, Ubuntu Advantage (which does nothing on Pop!_OS), LibreWolf, and Brave. None of those things would have any interest in GNOME Shell extension gsettings keys.

[jacobgkau]

I see that you're on System76 hardware. Creating a set of log files from the Settings -> Support page could provide some clue as to what else might be running on the system that would affect this. If you're not comfortable posting full logs to a public GitHub issue, you can send them into a support ticket if you'd like.

Since the issue happens on more than one system, even just a list of non-default software you have installed on both systems (and any other settings that you typically modify when you install a new system) could provide a relevant clue.

[TriggerDingus]

OK. Go ahead and close this issue. Thanks <--my misunderstanding, I didn't read your last posting completely but just got back in to this issue today to follow-up since it's been happening again on both machines

[TriggerDingus]

Sorry - this issue didn't creep up for quite some time, however, it's been back with a few recent updates. I just submitted a ticket but the ticket didn't have a place for attaching the logs. I'm assuming a support rep will reach out to give me an upload location.

[jacobgkau]

@thomas-zimmerman passed your logs to me. The only things I see recently updated are Brave and OnlyOffice (neither of which are available in default Pop!_OS apt repos, and neither of which should be touching our extensions' gsettings) as well as Ubuntu Advantage tools (which do nothing on Pop!_OS) and some Ruby packages.

I want to confirm, the issue happened on December 1st, and the settings were changed after you rebooted (not immediately after installing the updates), correct? This time, was it the three dock icons, the power settings, or both that were changed? I see a Mullvad VPN client is running, which would at least be making changes to the network settings; is it installed on both of the machines that have been affected by this?

[TriggerDingus]

The last time it happened was a few days before the 1st of December but I wasn't ferociously logging the changes as I had been doing but now that we're both re-engaged, I'll be sure to do so the next time it happens and capture a fresh log at that time.

That being said, I can answer your questions: As is always the case, the same settings are always changed after rebooting following an update. The settings changed are always the same: the three dock icons and the power settings. Mullvad is installed on both machines.

[mmstick]

Have you use dconf-editor to check if these settings have use-default-value set?

[TriggerDingus]

I don't poke around in there at all, but here's a snapshot of what it looks like:

I'm assuming that should match my current settings here? Keep in-mind, I have these settings set to what I want them to be and not what they look like after they get 'reset'.

[TriggerDingus]

It just happened again. I received an update notification from the PopShop and so I immediately applied the updates and then immediately rebooted to see if my settings would be changed, and they were. All the exact same settings as mentioned in the thread were changed again. I generated the log file and sent it to the support Email, so you should have that any minute now.

[mmstick]

The description about the schema being missing is suspicious. The contents look nothing like the screenshot I gave.

[TriggerDingus]

I noticed my screen capture was very different from yours but since I don't play around with my settings on either of my machines, I don't know what that means. I pretty much had my settings like I wanted them a year or two ago and I really don't change them...but something is doing it for me...

[thomas-zimmerman]

The packages updated for the most recent change are:

Start-Date: 2022-12-06  21:12:20
Commandline: packagekit role='update-packages'
Upgrade: system76-firmware-daemon:amd64 (1.0.46~1668113396~22.04~220411c, 1.0.47~1670361247~22.04~c961d56), 
libctf-nobfd0:amd64 (2.38-4ubuntu2, 2.38-4ubuntu2.1), 
pop-launcher:amd64 (1.2.2~1668460831~22.04~fb8d5f5, 1.2.2~1670015921~22.04~8641dc5), 
libxml2-dev:amd64 (2.9.13+dfsg-1ubuntu0.1, 2.9.13+dfsg-1ubuntu0.2), 
libxml2-utils:amd64 (2.9.13+dfsg-1ubuntu0.1, 2.9.13+dfsg-1ubuntu0.2), 
xserver-xorg-core:amd64 (2:21.1.3-2ubuntu2.3, 2:21.1.3-2ubuntu2.4), 
libpipewire-0.3-common:amd64 (0.3.60-1~1668441179~22.04~e9e7c31, 0.3.61~1669829278~22.04~8eb17d0), 
pipewire-pulse:amd64 (0.3.60-1~1668441179~22.04~e9e7c31, 0.3.61~1669829278~22.04~8eb17d0), 
libbinutils:amd64 (2.38-4ubuntu2, 2.38-4ubuntu2.1), 
system76-power:amd64 (1.1.24~1669765342~22.04~32c55a4, 1.1.24~1670342346~22.04~e898259), 
binutils-x86-64-linux-gnu:amd64 (2.38-4ubuntu2, 2.38-4ubuntu2.1), 
pipewire:amd64 (0.3.60-1~1668441179~22.04~e9e7c31, 0.3.61~1669829278~22.04~8eb17d0), 
libbpf0:amd64 (1:0.5.0-1, 1:0.5.0-1ubuntu22.04.1), 
libxml2:amd64 (2.9.13+dfsg-1ubuntu0.1, 2.9.13+dfsg-1ubuntu0.2), 
libxml2:i386 (2.9.13+dfsg-1ubuntu0.1, 2.9.13+dfsg-1ubuntu0.2), 
xserver-xorg-legacy:amd64 (2:21.1.3-2ubuntu2.3, 2:21.1.3-2ubuntu2.4), 
libspa-0.2-jack:amd64 (0.3.60-1~1668441179~22.04~e9e7c31, 0.3.61~1669829278~22.04~8eb17d0), 
libspa-0.2-bluetooth:amd64 (0.3.60-1~1668441179~22.04~e9e7c31, 0.3.61~1669829278~22.04~8eb17d0), 
xserver-common:amd64 (2:21.1.3-2ubuntu2.3, 2:21.1.3-2ubuntu2.4), 
pipewire-jack:amd64 (0.3.60-1~1668441179~22.04~e9e7c31, 0.3.61~1669829278~22.04~8eb17d0), 
gstreamer1.0-pipewire:amd64 (0.3.60-1~1668441179~22.04~e9e7c31, 0.3.61~1669829278~22.04~8eb17d0), 
libctf0:amd64 (2.38-4ubuntu2, 2.38-4ubuntu2.1), 
pipewire-avb:amd64 (0.3.60-1~1668441179~22.04~e9e7c31, 0.3.61~1669829278~22.04~8eb17d0), 
pipewire-bin:amd64 (0.3.60-1~1668441179~22.04~e9e7c31, 0.3.61~1669829278~22.04~8eb17d0), 
binutils-common:amd64 (2.38-4ubuntu2, 2.38-4ubuntu2.1), 
ca-certificates:amd64 (20211016, 20211016ubuntu0.22.04.1), 
system76-driver:amd64 (20.04.67~1668113670~22.04~cfb1f88, 20.04.68~1670343116~22.04~6f763d8), 
libspa-0.2-modules:amd64 (0.3.60-1~1668441179~22.04~e9e7c31, 0.3.61~1669829278~22.04~8eb17d0), 
xserver-xephyr:amd64 (2:21.1.3-2ubuntu2.3, 2:21.1.3-2ubuntu2.4), 
libpipewire-0.3-modules:amd64 (0.3.60-1~1668441179~22.04~e9e7c31, 0.3.61~1669829278~22.04~8eb17d0), 
system76-driver-nvidia:amd64 (20.04.67~1668113670~22.04~cfb1f88, 20.04.68~1670343116~22.04~6f763d8), 
binutils:amd64 (2.38-4ubuntu2, 2.38-4ubuntu2.1), 
pipewire-alsa:amd64 (0.3.60-1~1668441179~22.04~e9e7c31, 0.3.61~1669829278~22.04~8eb17d0), 
libpipewire-0.3-0:amd64 (0.3.60-1~1668441179~22.04~e9e7c31, 0.3.61~1669829278~22.04~8eb17d0), 
libspa-0.2-avb:amd64 (0.3.60-1~1668441179~22.04~e9e7c31, 0.3.61~1669829278~22.04~8eb17d0)
End-Date: 2022-12-06  21:12:47

[jacobgkau]

I think we should focus on eliminating the No schema available. message. What happens if you click Erase key? Also, what is the output of apt policy gnome-settings-daemon?

[TriggerDingus]

I clicked Erase Key and then rebooted. Here's the dconf panel now:

---

Here's the output from apt policy gnome-settings-daemon:

gnome-settings-daemon:
  Installed: 42.1-1ubuntu3pop0~1661536383~22.04~3fb6384
  Candidate: 42.1-1ubuntu3pop0~1661536383~22.04~3fb6384
  Version table:
 *** 42.1-1ubuntu3pop0~1661536383~22.04~3fb6384 1001
       1001 http://apt.pop-os.org/release jammy/main amd64 Packages
        100 /var/lib/dpkg/status
     42.1-1ubuntu2.1 500
        500 http://apt.pop-os.org/ubuntu jammy-updates/main amd64 Packages
     42.1-1ubuntu2 500
        500 http://apt.pop-os.org/ubuntu jammy/main amd64 Packages

[jacobgkau]

I've edited your comment to put the output in code blocks. Please use three backticks (```) on their own line before and after a block of output.

[jacobgkau]

Can you please provide the output of these commands:

ls -alh /usr/share/glib-2.0/schemas/org.gnome.settings-daemon.plugins.power.gschema.xml
apt policy gnome-settings-daemon-common

It looks like that is the file that defines these schemas, and that is the specific package that provides this file.

[TriggerDingus]

ins.power.gschema.xml
apt policy gnome-settings-daemon-common
-rw-r--r-- 1 root root 4.3K Aug 26 13:53 /usr/share/glib-2.0/schemas/org.gnome.settings-daemon.plugins.power.gschema.xml
gnome-settings-daemon-common:
  Installed: 42.1-1ubuntu3pop0~1661536383~22.04~3fb6384
  Candidate: 42.1-1ubuntu3pop0~1661536383~22.04~3fb6384
  Version table:
 *** 42.1-1ubuntu3pop0~1661536383~22.04~3fb6384 1001
       1001 http://apt.pop-os.org/release jammy/main amd64 Packages
       1001 http://apt.pop-os.org/release jammy/main i386 Packages
        100 /var/lib/dpkg/status
     42.1-1ubuntu2.1 500
        500 http://apt.pop-os.org/ubuntu jammy-updates/main amd64 Packages
        500 http://apt.pop-os.org/ubuntu jammy-updates/main i386 Packages
     42.1-1ubuntu2 500
        500 http://apt.pop-os.org/ubuntu jammy/main amd64 Packages
        500 http://apt.pop-os.org/ubuntu jammy/main i386 Packages

[TriggerDingus]

Not sure why some text pasted as strike-through because it isn't outputted as strikethrough in my terminal. This is apparently a browser 'pasting' issue.

[TriggerDingus]

I see what may have caused the strikethrough. The browser doesn't like the tildes. Heres a screen cap, instead:

[jacobgkau]

I see what may have caused the strikethrough. The browser doesn't like the tildes. Heres a screen cap, instead:

This has nothing to do with the "browser," that is happening because you are not putting the text within code blocks (between lines of three backticks ```) like I asked you to do. I have once again edited your comment to fix this.

[TriggerDingus]

Sorry you may be upset. I didn't understand your 'tick' comment, or that you were speaking to me.

[jacobgkau]

I'm able to recreate the "No schema available." message if I launch dconf-editor as a Flatpak.

However, your screenshot shows that it's using the Pop! theme, which should mean it's not using the Flatpak (the Flatpak version appears to be using libadwaita or otherwise forcing the Adwaita theme.) Can you confirm that you installed dconf-editor as a .deb and not a Flatpak, just to be safe?

The output of both of these commands would be good, to confirm it's installed via .deb and it's coming from the correct apt repository:

flatpak uninstall ca.desrt.dconf-editor
apt policy dconf-editor

Assuming the outputs for those are as I expect them to be, then I still believe we need to figure out what's causing dconf-editor to report that those schemas don't exist on your system (possibly something user account-specific overriding the system schemas?)

[TriggerDingus]

bob@pop-os:~$ flatpak uninstall ca.desrt.dconf-editor

        ID                                   Branch         Op
        ID                                   Branch         Op
 1. [-] ca.desrt.dconf-editor                stable         r
 2. [-] ca.desrt.dconf_editor.Locale         stable         r

Uninstall complete.
bob@pop-os:~$ apt policy dconf-editor
dconf-editor:
  Installed: (none)
  Candidate: 3.38.3-3
  Version table:
     3.38.3-3 500
        500 http://apt.pop-os.org/ubuntu jammy/universe amd64 Packages
bob@pop-os:~$ 

[jacobgkau]

Ok, so you had the Flatpak version installed. Please run sudo apt install dconf-editor to install the .deb version, and look for the same settings. Is the No schema available. message gone now? (Please post a screenshot so we can see the use-default-value option that @mmstick originally asked about, too.)

[TriggerDingus]