Bug 2188005 - Gnome-software fail to start after upgrading to Fedora 38
Summary: Gnome-software fail to start after upgrading to Fedora 38
Keywords:
Status: CLOSED INSUFFICIENT_DATA
Alias: None
Product: Fedora
Classification: Fedora
Component: gnome-software
Version: 38
Hardware: x86_64
OS: Linux
unspecified
medium
Target Milestone: ---
Assignee: Milan Crha
QA Contact: Fedora Extras Quality Assurance
URL: https://discussion.fedoraproject.org/...
Whiteboard:
Depends On: 2187837
Blocks:
TreeView+ depends on / blocked
 
Reported: 2023-04-19 12:56 UTC by Matias Repetti
Modified: 2023-04-21 08:48 UTC (History)
4 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2023-04-20 22:10:15 UTC
Type: ---
Embargoed:


Attachments (Terms of Use)

Description Matias Repetti 2023-04-19 12:56:44 UTC
User-Agent:       Mozilla/5.0 (X11; Linux x86_64; rv:109.0) Gecko/20100101 Firefox/112.0
Build Identifier: 

After upgrading to Fedora 38 from 37, the Gnome-software app fail to start. The app start refreshing the catalog and crash. 



Reproducible: Always




Running the app from command line shows the following error:

GLib-GIO Settings schema 'org.gnome.software' does not contain a key named 'show-only-free-apps'

The key seems to be missing for Glib or in /usr/share/glib-2.0/schemas/org.gnome.software.gschema.xml

I did fixed the issue doing a downgrade for gnome-software to 43.5 from 44.0. 

One problem I'm having, a BIG ONE, if I now try to upgrade again to 44.0, this update requires a restart, but when the system try to update on boot it get stuck.I found that removing the broken link (/system-update) allow me to boot and abort the upgrade.

Comment 1 Milan Crha 2023-04-19 13:17:22 UTC
Thanks for a bug report. The crash is reported as bug #2187837. If you can still reproduce this, could you follow bug #2187837 comment #13 and write the result, here, please?

Comment 2 Matias Repetti 2023-04-19 19:49:24 UTC
Ok, I had to upgrade gnome-software so I have it on 44.0 version, and then compiling the schemas seams to work. Gnome-software doesn´t crash now.

I didn´t restart the system yet, I hope it doesn´t get stuck at boot.

Thanks!

Here is the output.

$ sudo glib-compile-schemas /usr/share/glib-2.0/schemas/

Warning: Schema “org.freedesktop.ibus” has path “/desktop/ibus/”.  Paths starting with “/apps/”, “/desktop/” or “/system/” are deprecated.
Warning: Schema “org.freedesktop.ibus.general” has path “/desktop/ibus/general/”.  Paths starting with “/apps/”, “/desktop/” or “/system/” are deprecated.
Warning: Schema “org.freedesktop.ibus.general.hotkey” has path “/desktop/ibus/general/hotkey/”.  Paths starting with “/apps/”, “/desktop/” or “/system/” are deprecated.
Warning: Schema “org.freedesktop.ibus.panel” has path “/desktop/ibus/panel/”.  Paths starting with “/apps/”, “/desktop/” or “/system/” are deprecated.
Warning: Schema “org.freedesktop.ibus.panel.emoji” has path “/desktop/ibus/panel/emoji/”.  Paths starting with “/apps/”, “/desktop/” or “/system/” are deprecated.
Warning: Schema “org.gnome.crypto.cache” has path “/desktop/gnome/crypto/cache/”.  Paths starting with “/apps/”, “/desktop/” or “/system/” are deprecated.
Warning: Schema “org.gnome.crypto.pgp” has path “/desktop/gnome/crypto/pgp/”.  Paths starting with “/apps/”, “/desktop/” or “/system/” are deprecated.
Warning: Schema “org.gnome.system.locale” has path “/system/locale/”.  Paths starting with “/apps/”, “/desktop/” or “/system/” are deprecated.
Warning: Schema “org.gnome.system.proxy” has path “/system/proxy/”.  Paths starting with “/apps/”, “/desktop/” or “/system/” are deprecated.
Warning: Schema “org.gnome.system.proxy.http” has path “/system/proxy/http/”.  Paths starting with “/apps/”, “/desktop/” or “/system/” are deprecated.
Warning: Schema “org.gnome.system.proxy.https” has path “/system/proxy/https/”.  Paths starting with “/apps/”, “/desktop/” or “/system/” are deprecated.
Warning: Schema “org.gnome.system.proxy.ftp” has path “/system/proxy/ftp/”.  Paths starting with “/apps/”, “/desktop/” or “/system/” are deprecated.
Warning: Schema “org.gnome.system.proxy.socks” has path “/system/proxy/socks/”.  Paths starting with “/apps/”, “/desktop/” or “/system/” are deprecated.
No such key “picture-uri-dark” in schema “org.gnome.desktop.screensaver” as specified in override file “/usr/share/glib-2.0/schemas/10_org.gnome.desktop.screensaver.fedora.gschema.override”; ignoring override for this key.

$ cat /usr/share/glib-2.0/schemas/org.gnome.software.gschema.xml | grep show-only-free-apps
    <key name="show-only-free-apps" type="b">

Comment 3 Matias Repetti 2023-04-19 23:00:22 UTC
Well, after restart the system wont boot. So I installed Fedora 38 from scratch.

Comment 4 Milan Crha 2023-04-20 05:22:55 UTC
(In reply to Matias Repetti from comment #3)
> Well, after restart the system wont boot. So I installed Fedora 38 from
> scratch.

I'm sorry about that, but I believe it's unrelated to the original problem recorded here.

Comment 5 Milan Crha 2023-04-20 05:28:07 UTC
Adam (added into CC), this seems to be a serious problem after upgrade. See the bug #2187837, where are piling duplicates. It seems the recompilation of the glib schemas failed during the upgrade for some reason. I do not know where to move this to, I'm sorry.

Comment 6 Matias Repetti 2023-04-20 11:08:00 UTC
I can´t say much, once I fixed the issue with the gnome-software schema everything seems fine. The only thing, for me, that triggers the problem on boot was if I ran the 'restart & update' suggested by gnome-software. 

Another thing to mention, not sure it helps on this, when starting the upgrade on the first time, I got a warning that some packages wont be available, this where: steam, pipewire-alsa and some other pipewire package that I don´t remember. I should have takne an screenshot but because I didn´t care much about those packages, I continued.

Comment 7 Matias Repetti 2023-04-20 13:16:57 UTC
Hello, this issue was with my laptop, which I work with. But I completely forgot I actually have a PC (which I don´t use so often but try to keep updated) running Fedora 37, I'll try to upgrade to 38 maybe later today.

I could debug this the upgrade somehow if you tell me where should I look or which log files to check.

==== From the other bug report I read ====
It would really help to see logs from the actual upgrade process, either using `journalctl -b-N` (which shows the logs from N boots ago, so if you've just booted for the first time after upgrading, `journalctl -b-1` should show the logs from the upgrade process; for each reboot since upgrading, bump the number...), or if they're in `/var/log/dnf.log`, from there (I'm not sure if they'll be there if you upgraded with Software).  
====== 

I could check that too.

Comment 8 Matias Repetti 2023-04-20 22:10:15 UTC
I upgraded my PC to Fedora 38 and everything went smooth. The difference between the laptop and the PC was, the PC have a pretty clean install of Fedora 37. For example, I didn´t have Steam or pipewire libs installed, so there was no warnings regarding this packages which I did have when upgrading my laptop.

Thanks for your support.

Comment 9 Adam Williamson 2023-04-20 22:36:12 UTC
Well, lots of people seem to be hitting this, so there's definitely a real problem. But without logs from an upgrade that hit the problem, it's hard to move forward - we need something to give us some idea what is needed to trigger the problem. It probably relates to having some specific package installed or some particular local configuration set before upgrading, but it's hard to guess *what*.

https://bugzilla.redhat.com/show_bug.cgi?id=2187837 is where most of the dupes are landing.

Comment 10 Adam Williamson 2023-04-20 23:30:03 UTC
Matias: you should still be able to find the logs from the laptop; they shouldn't be lost. How exactly did you do the upgrade? Did you use GNOME Software, or `dnf system-upgrade`, or what?

Comment 11 Adam Williamson 2023-04-21 00:59:29 UTC
I tried an upgrade using dnf system-upgrade from a clean F37 Workstation with Steam installed, worked OK.

Comment 12 Matias Repetti 2023-04-21 08:48:25 UTC
(In reply to Adam Williamson from comment #10)
> Matias: you should still be able to find the logs from the laptop; they
> shouldn't be lost. How exactly did you do the upgrade? Did you use GNOME
> Software, or `dnf system-upgrade`, or what?


Apologies, but I had to install F38 from scratch so I don't have access to those logs anymore.


I started the upgrade from Gnome-Software. It warned me about some packages like Steam, which was installed from rpmfusion-nonfree-steam (this 'free' keyworkd triggers alarms) but I continued. It finished the upgrade and restarted. Everything fine so far. Gnome-software opens and start reloading the catalog and there it crashes. I search the web and at first, someone recommended to downgrade gnome-software, I did, and it seems to work. Gnome-software was working but showing me a pending update of gnome-software of course from 43.5 to 44.0. I tried to update and this time, at restart, it stuck at boot. I found there was a broken link at /root/system-update, I removed this link (guessing) from a live USB session (rescue image didn´t boot neither), and it allow me to boot and continue with my stuff but everytime I did 'restart & update' process it stuck at boot. 


Understand there's a lot of duplicates, don't want to add more noise, but here is where I started the conversation: https://discussion.fedoraproject.org/t/gnome-software-crashes-doesnt-open-after-update-to-fedora-38/81078/14


Note You need to log in before you can comment on or make changes to this bug.