Bug 1211589

Summary: Software updates are not installed automatically through GNOME Software
Product: [openSUSE] openSUSE Tumbleweed Reporter: Tobias Görgens <tobi.goergens>
Component: GNOMEAssignee: E-mail List <gnome-bugs>
Status: RESOLVED NORESPONSE QA Contact: E-mail List <qa-bugs>
Severity: Normal    
Priority: P5 - None CC: songchuan.kang, tobi.goergens
Version: Current   
Target Milestone: ---   
Hardware: Other   
OS: Other   
Whiteboard:
Found By: --- Services Priority:
Business Priority: Blocker: ---
Marketing QA Status: --- IT Deployment: ---

Description Tobias Görgens 2023-05-22 11:03:56 UTC
Hey there,

I recently installed OpenSUSE Tumbleweed and replaced the zypper packagekit plugin with the DNF one (described here: https://en.opensuse.org/SDB:DNF) While it's stable, updates that are shown in GNOME Software are not automatically installed, even though the option is enabled (I can install them manually though).
I waited for over 3 weeks now, the install-timestamp (gsettings get org.gnome.software install-timestamp) shows May 1st, so it should've pulled updates already.
This is similar to the issue described here:
https://bugzilla.redhat.com/show_bug.cgi?id=2026108
except that software updates aren't installed automatically after 2 weeks
Manually installing updates works fine.

Is this reproducable?
Are any logs required?
Comment 1 Jonathan Kang 2023-06-07 08:01:08 UTC
(In reply to Tobias Görgens from comment #0)
> Hey there,
> 
> I recently installed OpenSUSE Tumbleweed and replaced the zypper packagekit
> plugin with the DNF one (described here: https://en.opensuse.org/SDB:DNF)
> While it's stable, updates that are shown in GNOME Software are not
> automatically installed, even though the option is enabled (I can install
> them manually though).
> I waited for over 3 weeks now, the install-timestamp (gsettings get
> org.gnome.software install-timestamp) shows May 1st, so it should've pulled
> updates already.
> This is similar to the issue described here:
> https://bugzilla.redhat.com/show_bug.cgi?id=2026108
> except that software updates aren't installed automatically after 2 weeks
> Manually installing updates works fine.
> 
> Is this reproducable?
> Are any logs required?

The output of `gnome-software --verbose` will be helpful. You need run `gnome-software --quit` before that. And wait some time for GNOME Software to trigger the update check.
Comment 2 Tobias Görgens 2023-06-08 11:34:22 UTC
(In reply to Jonathan Kang from comment #1)
> (In reply to Tobias Görgens from comment #0)
> > Hey there,
> > 
> > I recently installed OpenSUSE Tumbleweed and replaced the zypper packagekit
> > plugin with the DNF one (described here: https://en.opensuse.org/SDB:DNF)
> > While it's stable, updates that are shown in GNOME Software are not
> > automatically installed, even though the option is enabled (I can install
> > them manually though).
> > I waited for over 3 weeks now, the install-timestamp (gsettings get
> > org.gnome.software install-timestamp) shows May 1st, so it should've pulled
> > updates already.
> > This is similar to the issue described here:
> > https://bugzilla.redhat.com/show_bug.cgi?id=2026108
> > except that software updates aren't installed automatically after 2 weeks
> > Manually installing updates works fine.
> > 
> > Is this reproducable?
> > Are any logs required?
> 
> The output of `gnome-software --verbose` will be helpful. You need run
> `gnome-software --quit` before that. And wait some time for GNOME Software
> to trigger the update check.

Hey there,
thank you for your reply :)

This is some of the output:
https://pastebin.com/puiuw2nj

With the following error being repeated later on as well:
11:31:16:237 dconf unable to create file '/run/user/1000/dconf/user': Keine Berechtigung.  dconf will not work properly.

Do you know why this might happen?
Comment 3 Jonathan Kang 2023-06-12 02:05:10 UTC
(In reply to Tobias Görgens from comment #2)
> Hey there,
> thank you for your reply :)
> 
> This is some of the output:
> https://pastebin.com/puiuw2nj
> 
> With the following error being repeated later on as well:
> 11:31:16:237 dconf unable to create file '/run/user/1000/dconf/user': Keine
> Berechtigung.  dconf will not work properly.
> 
> Do you know why this might happen?

No idea why that happens. A quick google search shows a few possibilities. You can try them and see if any of them work.

This error message should be the reason why GNOME Software is not able to automatically download updates, as it cannot read needed data from dconf.
Comment 4 Tobias Görgens 2023-06-13 09:50:49 UTC
(In reply to Jonathan Kang from comment #3)
> (In reply to Tobias Görgens from comment #2)
> > Hey there,
> > thank you for your reply :)
> > 
> > This is some of the output:
> > https://pastebin.com/puiuw2nj
> > 
> > With the following error being repeated later on as well:
> > 11:31:16:237 dconf unable to create file '/run/user/1000/dconf/user': Keine
> > Berechtigung.  dconf will not work properly.
> > 
> > Do you know why this might happen?
> 
> No idea why that happens. A quick google search shows a few possibilities.
> You can try them and see if any of them work.
> 
> This error message should be the reason why GNOME Software is not able to
> automatically download updates, as it cannot read needed data from dconf.

OK, I just manually changed the permission, after a reboot the permission stays in place, the error is gone.
This might have been caused by me using gsettings with root when I setup the system.
Flatpak updates are now installed automatically, however, system updates stil do not work
This is the message I see about that:
09:44:28:768 Gs  First hourly updates check
09:44:28:768 Gs  Chaining cancellation from 0x563459df5dc0 to 0x56345d56fa50
09:44:28:768 Gs  Getting upgrades
09:44:28:768 Gs  no plugin could handle listing distro upgrades
09:44:28:768 Gs  No distro upgrades to refine
09:44:28:768 Gs  running unknown with dedupe-flags=7
09:44:28:768 Gs  no upgrades; withdrawing upgrades-available notification
09:44:28:769 Gs  no plugin could handle get-langpacks
09:44:28:769 Gs  no refine flags set for transaction
09:44:28:769 Gs  running get-langpacks with dedupe-flags=7 with refine-flags=require-icon with search=de_DE.UTF-8
09:44:28:769 Gs  no language pack found
Comment 5 Tobias Görgens 2023-06-13 09:54:31 UTC
(In reply to Tobias Görgens from comment #4)
> (In reply to Jonathan Kang from comment #3)
> > (In reply to Tobias Görgens from comment #2)
> > > Hey there,
> > > thank you for your reply :)
> > > 
> > > This is some of the output:
> > > https://pastebin.com/puiuw2nj
> > > 
> > > With the following error being repeated later on as well:
> > > 11:31:16:237 dconf unable to create file '/run/user/1000/dconf/user': Keine
> > > Berechtigung.  dconf will not work properly.
> > > 
> > > Do you know why this might happen?
> > 
> > No idea why that happens. A quick google search shows a few possibilities.
> > You can try them and see if any of them work.
> > 
> > This error message should be the reason why GNOME Software is not able to
> > automatically download updates, as it cannot read needed data from dconf.
> 
> OK, I just manually changed the permission, after a reboot the permission
> stays in place, the error is gone.
> This might have been caused by me using gsettings with root when I setup the
> system.
> Flatpak updates are now installed automatically, however, system updates
> stil do not work
> This is the message I see about that:
> 09:44:28:768 Gs  First hourly updates check
> 09:44:28:768 Gs  Chaining cancellation from 0x563459df5dc0 to 0x56345d56fa50
> 09:44:28:768 Gs  Getting upgrades
> 09:44:28:768 Gs  no plugin could handle listing distro upgrades
> 09:44:28:768 Gs  No distro upgrades to refine
> 09:44:28:768 Gs  running unknown with dedupe-flags=7
> 09:44:28:768 Gs  no upgrades; withdrawing upgrades-available notification
> 09:44:28:769 Gs  no plugin could handle get-langpacks
> 09:44:28:769 Gs  no refine flags set for transaction
> 09:44:28:769 Gs  running get-langpacks with dedupe-flags=7 with
> refine-flags=require-icon with search=de_DE.UTF-8
> 09:44:28:769 Gs  no language pack found

Sorry, forgot the full log (it's not the full log, I didn't find a way to forward the output to a text file, I hope this catches the update fetching:
https://pastebin.com/QUinUrpm
Comment 6 Jonathan Kang 2023-06-14 01:41:20 UTC
(In reply to Tobias Görgens from comment #5)
> 
> Sorry, forgot the full log (it's not the full log, I didn't find a way to
> forward the output to a text file, I hope this catches the update fetching:
> https://pastebin.com/QUinUrpm

You can run `gnome-software --verbose > gs-log` to put logs inside gs-log file. It'll be better if you leave this command running for more than 1 day to collect enough information.

BTW, are you in power save mode?
Comment 7 Tobias Görgens 2023-06-19 12:46:12 UTC
(In reply to Jonathan Kang from comment #6)
> (In reply to Tobias Görgens from comment #5)
> > 
> > Sorry, forgot the full log (it's not the full log, I didn't find a way to
> > forward the output to a text file, I hope this catches the update fetching:
> > https://pastebin.com/QUinUrpm
> 
> You can run `gnome-software --verbose > gs-log` to put logs inside gs-log
> file. It'll be better if you leave this command running for more than 1 day
> to collect enough information.
> 
> BTW, are you in power save mode?

Ah thanks that works, I probably had a typo when I tried to log it earlier lol.
I'll let it run until tomorrow morning, no, I'm not in power saving mode (I saw once in the logs that that prevented auto updates so I turned it off)
Comment 8 Tobias Görgens 2023-06-19 13:19:27 UTC
(In reply to Jonathan Kang from comment #6)
> (In reply to Tobias Görgens from comment #5)
> > 
> > Sorry, forgot the full log (it's not the full log, I didn't find a way to
> > forward the output to a text file, I hope this catches the update fetching:
> > https://pastebin.com/QUinUrpm
> 
> You can run `gnome-software --verbose > gs-log` to put logs inside gs-log
> file. It'll be better if you leave this command running for more than 1 day
> to collect enough information.
> 
> BTW, are you in power save mode?

I let it run for about an hour when I saw that GNome software promted me to reboot to install the updates
I did that, it installed the updates, so it seems to work now.
I don't know why it didn't work last time I tried, maybe one package update was broken.
Anyway, thank you very much for your patience and time, I'll close the issue for now, should the issue appear again, I'll re-open it.
Have a nice day! :)
Comment 9 Tobias Görgens 2023-06-20 12:13:05 UTC
(In reply to Tobias Görgens from comment #8)
> (In reply to Jonathan Kang from comment #6)
> > (In reply to Tobias Görgens from comment #5)
> > > 
> > > Sorry, forgot the full log (it's not the full log, I didn't find a way to
> > > forward the output to a text file, I hope this catches the update fetching:
> > > https://pastebin.com/QUinUrpm
> > 
> > You can run `gnome-software --verbose > gs-log` to put logs inside gs-log
> > file. It'll be better if you leave this command running for more than 1 day
> > to collect enough information.
> > 
> > BTW, are you in power save mode?
> 
> I let it run for about an hour when I saw that GNome software promted me to
> reboot to install the updates
> I did that, it installed the updates, so it seems to work now.
> I don't know why it didn't work last time I tried, maybe one package update
> was broken.
> Anyway, thank you very much for your patience and time, I'll close the issue
> for now, should the issue appear again, I'll re-open it.
> Have a nice day! :)

The issue came back, after letting gnome-software install the automatic updates, dconf had again no access to the file.
For some reason, as it seems, gnome software locks the file itself?
Comment 10 Jonathan Kang 2023-06-21 01:32:14 UTC
(In reply to Tobias Görgens from comment #9)
> The issue came back, after letting gnome-software install the automatic
> updates, dconf had again no access to the file.
> For some reason, as it seems, gnome software locks the file itself?

What's the output of `ls -l /run/user/1000/dconf/` in your system?
Comment 11 Tobias Görgens 2023-07-31 10:31:40 UTC
(In reply to Jonathan Kang from comment #10)
> (In reply to Tobias Görgens from comment #9)
> > The issue came back, after letting gnome-software install the automatic
> > updates, dconf had again no access to the file.
> > For some reason, as it seems, gnome software locks the file itself?
> 
> What's the output of `ls -l /run/user/1000/dconf/` in your system?

Hey, sorry for the late reply, must have missed the email :(

Here's the output:
ls -l /run/user/1000/dconf/              [12:28:51]
overall 4
-rw------- 1 root root 2 28. Jul 10:51 user
Comment 12 Jonathan Kang 2023-08-01 12:09:15 UTC
(In reply to Tobias Görgens from comment #11)
> (In reply to Jonathan Kang from comment #10)
> > (In reply to Tobias Görgens from comment #9)
> > > The issue came back, after letting gnome-software install the automatic
> > > updates, dconf had again no access to the file.
> > > For some reason, as it seems, gnome software locks the file itself?
> > 
> > What's the output of `ls -l /run/user/1000/dconf/` in your system?
> 
> Hey, sorry for the late reply, must have missed the email :(
> 
> Here's the output:
> ls -l /run/user/1000/dconf/              [12:28:51]
> overall 4
> -rw------- 1 root root 2 28. Jul 10:51 user

This shouldn't be owned by root. Did you use any application that uses dconf as root(maybe via sudo)?

Logging out and back in should be able to recreate this file with owner of $YourUserId.

> -rw-------. 1 MyUsername Myusername 2 Aug  1 10:16 user

This is the output of that command at my system.
Comment 13 Jonathan Kang 2023-12-15 06:28:38 UTC
Closing this. Feel free to reopen with requested information.