Bug 1215709 - segfault in libglib/libgio/libgobject 2.0.so.0.7800.0 since MicroOS-20230921
Summary: segfault in libglib/libgio/libgobject 2.0.so.0.7800.0 since MicroOS-20230921
Status: RESOLVED FIXED
Alias: None
Product: openSUSE Tumbleweed
Classification: openSUSE
Component: MicroOS (show other bugs)
Version: Current
Hardware: VMWare openSUSE Tumbleweed
: P5 - None : Normal (vote)
Target Milestone: ---
Assignee: Forgotten User u0-bnvADNc
QA Contact: E-mail List
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2023-09-26 07:56 UTC by Dirk Datzert
Modified: 2024-06-26 21:00 UTC (History)
1 user (show)

See Also:
Found By: ---
Services Priority:
Business Priority:
Blocker: ---
Marketing QA Status: ---
IT Deployment: ---

Attachments
Hardcopy of the segfault messages (340.72 KB, image/png)
2023-09-26 07:56 UTC, Dirk Datzert 		Details
View All Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this bug.
Description Dirk Datzert 2023-09-26 07:56:33 UTC 
Created attachment 869748 [details]
Hardcopy of the segfault messages

After Upgrading to MicroOS-20230921 I see such segfaults pasted in the hardcopy on serveral VM Machines.

I can revert to a snapshot from 20230918 and disable transactional-update.timer. Has this segfault seen somewhere else ?

I'm running different k3s-version-branches on top of MicroOS and reverted also this to an older release.
Comment 1 Dirk Datzert 2023-09-27 06:32:29 UTC 
Maybe this is the same bug as in https://gitlab.gnome.org/GNOME/glib/-/issues/3105

I saw that NetworkManager 1.44 and glib 2.78 are on my vms.

glib was updated to 2.78 with MicroOS-20230921 on my vms.
Comment 2 Dirk Datzert 2023-09-27 06:59:25 UTC 
My work-around is going back to snapshot 20230918 with MicroOS-20230915.
Prevent upgrading to glib2 2.78.0 by:

zypper al glib2-tools gio-branding-openSUSE libglib-2_0-0 libgio-2_0-0 libgobject-2_0-0 libgmodule-2_0-0

transactional-update dup reboot
Comment 3 Dirk Datzert 2023-10-10 08:27:23 UTC 
Since 4 days no segfaults with glib2 2.78.0-2.1 visible.
Comment 4 Richard Brown 2023-10-10 14:29:28 UTC 
Reported fixed