|
Bugzilla – Full Text Bug Listing |
| Summary: | segfault in libglib/libgio/libgobject 2.0.so.0.7800.0 since MicroOS-20230921 | ||
|---|---|---|---|
| Product: | [openSUSE] openSUSE Tumbleweed | Reporter: | Dirk Datzert <dirk.datzert> |
| Component: | MicroOS | Assignee: | Forgotten User u0-bnvADNc <forgotten_u0-bnvADNc> |
| Status: | RESOLVED FIXED | QA Contact: | E-mail List <qa-bugs> |
| Severity: | Normal | ||
| Priority: | P5 - None | CC: | rbrown |
| Version: | Current | ||
| Target Milestone: | --- | ||
| Hardware: | VMWare | ||
| OS: | openSUSE Tumbleweed | ||
| Whiteboard: | |||
| Found By: | --- | Services Priority: | |
| Business Priority: | Blocker: | --- | |
| Marketing QA Status: | --- | IT Deployment: | --- |
| Attachments: | Hardcopy of the segfault messages | ||
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. 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 Since 4 days no segfaults with glib2 2.78.0-2.1 visible. Reported fixed |
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.