Bug 2512001 - gnome-system-monitor fails to start: undefined symbol gtk_restore_reason_get_type in libgtkmm-4.0.so.0
Summary: gnome-system-monitor fails to start: undefined symbol gtk_restore_reason_get_...
Keywords:
Status: CLOSED CURRENTRELEASE
Alias: None
Product: Fedora
Classification: Fedora
Component: gtkmm4.0
Version: 45
Hardware: Unspecified
OS: Unspecified
unspecified
high
Target Milestone: ---
Assignee: Matthias Clasen
QA Contact: Petr Sklenar
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2026-08-06 12:22 UTC by Petr Sklenar
Modified: 2026-09-14 08:49 UTC (History)
5 users (show)

Fixed In Version:
Clone Of:
Environment:
Last Closed: 2026-09-14 08:49:41 UTC
Type: ---
Embargoed:


Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
GNOME Gitlab GNOME/gnome-system-monitor/-/work_items/379 0 None None None 2026-08-07 14:23:26 UTC

Description Petr Sklenar 2026-08-06 12:22:04 UTC
Description of problem:
gnome-system-monitor fails to start with: "symbol lookup error: /lib64/libgtkmm-4.0.so.0: undefined symbol: gtk_restore_reason_get_type"

The symbol gtk_restore_reason_get_type is referenced by libgtkmm-4.0.so.0 (marked as U/undefined in nm -D output) but is not provided by libgtk-4.so.1. This is an ABI incompatibility between gtkmm4.0 and gtk4.

Version-Release number of selected component:
gtkmm4.0-4.23.0-4.fc45.aarch64
gtk4-4.23.3-1.fc45.aarch64
gnome-system-monitor-51~beta-1.fc45.aarch64

How reproducible:
Always (100%)

Steps to Reproduce:
1. Install Fedora 45 (Rawhide) on aarch64
2. Run: gnome-system-monitor

Actual Results:
gnome-system-monitor: symbol lookup error: /lib64/libgtkmm-4.0.so.0: undefined symbol: gtk_restore_reason_get_type
Process exits immediately.

Expected Results:
gnome-system-monitor should start normally.

Additional info:
- Symbol analysis: nm -D /lib64/libgtkmm-4.0.so.0 shows: U gtk_restore_reason_get_type
nm -D /lib64/libgtk-4.so.1 does NOT contain this symbol.
- Build dates: gtkmm4.0 was built on 2026-07-30, gtk4 was built on 2026-08-03. It appears gtk4 was updated after gtkmm4.0 and either removed or renamed the symbol. gtkmm4.0 needs a rebuild against current gtk4.
- OS: Fedora Linux 45 (Workstation Edition Prerelease)
- Kernel: 7.2.0-0.rc6.48.fc45.aarch64
- Architecture: aarch64 (Raspberry Pi 4, Cortex-A72)

Comment 1 Petr Sklenar 2026-08-06 12:38:03 UTC
related gtkmm commit 1ed5e281? : 
  https://gitlab.gnome.org/GNOME/gtkmm/-/commit/1ed5e281dcd9d59d4f98cdfc0e0aa303e3205fd5

Comment 2 Petr Sklenar 2026-08-06 13:03:15 UTC
Upstream fix is in gtkmm commit 1ed5e281 (2026-08-05):
https://gitlab.gnome.org/GNOME/gtkmm/-/commit/1ed5e281dcd9d59d4f98cdfc0e0aa303e3205fd5
"Gtk: Remove API as in gtk 4.23.3" - removes enum RestoreReason.

gtkmm4.0 needs a rebuild against current gtk4-4.23.3.

Comment 3 Kamil Páral 2026-08-07 14:23:27 UTC
Upstream bug report: https://gitlab.gnome.org/GNOME/gnome-system-monitor/-/work_items/379

Comment 4 Milan Crha 2026-09-03 16:35:09 UTC
That upstream commit is part of the 4.23.2 gtkmm release, which is part of the Fedora. It was build [1] against gtk4 4.23.3-1. Then there is 51.rc release of the gnome-system-monitor [2] , thus the things should be sorted out, I guess.

[1] https://koji.fedoraproject.org/koji/buildinfo?buildID=3077045
[2] https://bodhi.fedoraproject.org/updates/FEDORA-2026-494d8c11bd

Comment 5 Kamil Páral 2026-09-11 07:17:03 UTC
Petr, can you please test whether the update fixes the issue? Thanks.

Comment 6 Petr Sklenar 2026-09-11 10:50:14 UTC
verified with f45 beta 1.3, after package rebuilt:

rpm -q gnome-system-monitor  gtkmm4.0 gtk4
gnome-system-monitor-51~rc-1.fc45.x86_64
gtkmm4.0-4.23.2-1.fc45.x86_64
gtk4-4.23.4-1.fc45.x86_64

gnome-system-monitor was started fine

Comment 7 Kamil Páral 2026-09-14 08:49:41 UTC
https://bodhi.fedoraproject.org/updates/FEDORA-2026-494d8c11bd pushed closing. Dropping Common Issues.


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