| Summary: | Update to glibc causes 2560 x 1440 display resolution in KDE Plasma to become not available in System Settings. | ||
|---|---|---|---|
| Product: | Mageia | Reporter: | Lee Miller <lmiller> |
| Component: | RPM Packages | Assignee: | KDE maintainers <kde> |
| Status: | NEW --- | QA Contact: | |
| Severity: | normal | ||
| Priority: | Normal | CC: | tmb |
| Version: | 8 | ||
| Target Milestone: | --- | ||
| Hardware: | x86_64 | ||
| OS: | Linux | ||
| Whiteboard: | |||
| Source RPM: | systemsettings-5.20.4-2.mga8.src.rpm, glibc-2.32-25.mga8.src.rpm | CVE: | |
| Status comment: | |||
|
Description
Lee Miller
2022-02-09 00:20:55 CET
Thank you for the report, and sorry for the problem. To tell us about your system, especially the graphics, please post the output of $ inxi -MSGxx Are you obliged to use "System Settings >Display and Monitor >Display Configuration >Resolution" at all? If the resolution is correct in MCC-Hardware-Install graphic driver, are you saying that Plasma ignores that? Also, how do you manage to get back to a satisfactory resolution? (Sorry to ask; I hardly use Plasma, and certainly not to fiddle with screen resolution). Are you able to say which of these updates affected you? I ask to clarify 'glibm'. - lib64glibmm2.4_1 - lib64glibmm2.66_1 If you do: $ rpm -qa --last | less and look (/) for these in the output, which is date ordered most recent first, they should see the date of the most recent update. I ask in case the fault lies there. CC:
(none) =>
lewyssmith According our MADB there were never an update to any of those two packages since Mga8 release. Both are in core release. https://madb.mageia.org/package/list/t_search/Glibmm/application/0/arch/x86_64 The screen resolutions in systemsettings5 are provided by KDE Plasma. The screen resolutions in MCC are provided by Mageia core system and is independent from any desktop environment like Plasma or Gnome or whatever. (In reply to Lewis Smith from comment #1) > Thank you for the report, and sorry for the problem. > To tell us about your system, especially the graphics, please post the > output of > $ inxi -MSGxx > > Are you obliged to use "System Settings >Display and Monitor >Display > Configuration >Resolution" at all? If the resolution is correct in > MCC-Hardware-Install graphic driver, are you saying that Plasma ignores that? > Also, how do you manage to get back to a satisfactory resolution? > > (Sorry to ask; I hardly use Plasma, and certainly not to fiddle with screen > resolution). > > Are you able to say which of these updates affected you? I ask to clarify > 'glibm'. > - lib64glibmm2.4_1 > - lib64glibmm2.66_1 > If you do: > $ rpm -qa --last | less > and look (/) for these in the output, which is date ordered most recent > first, they should see the date of the most recent update. I ask in case the > fault lies there. Thank you Lewis for the prompt and informative reply, and it helped me provide a more correct version of the cause of the problem. But first, the answers to your questions: 1. $ inxi -MSGxx System: Host: myhost.localdomain Kernel: 5.15.18-desktop-2.mga8 x86_64 bits: 64 compiler: gcc v: 10.3.0 Desktop: KDE Plasma 5.20.4 tk: Qt 5.15.2 wm: kwin_x11 dm: SDDM Distro: Mageia 8 mga8 Machine: Type: Desktop Mobo: ASRock model: X570 Steel Legend WiFi ax serial: <superuser required> UEFI: American Megatrends v: P3.70 date: 04/14/2021 Graphics: Device-1: AMD Navi 10 [Radeon RX 5600 OEM/5600 XT / 5700/5700 XT] vendor: ASRock driver: amdgpu v: kernel bus ID: 0f:00.0 chip ID: 1002:731f Display: x11 server: Mageia X.org 1.20.14 compositor: kwin_x11 driver: amdgpu,v4l resolution: 2560x1440~60Hz s-dpi: 96 OpenGL: renderer: AMD Radeon RX 5600 XT (NAVI10 DRM 3.42.0 5.15.18-desktop-2.mga8 LLVM 11.0.1) v: 4.6 Mesa 21.3.4 direct render: Yes $ 2. No, I'm not obligated to use "System Settings...Resolution". It's only there to allow for multiple users with different resolution requirements than that set by the "MCC-Hardwarea-Install graphic driver. So, MCC resolution is the default for all users, but can be overridden in Plasma System Settings as needed. My error that compounded the problem initially was to go to the System Settings to reset the resolution from the changed 3840x2160. The character size had become so small that I thought I was selecting 2560x1440 but didn't see that I was selecting some other resolution not valid for my monitor/display. If instead I had gone to the MCC>Hardware>...Resolution, after a reboot, all would have been good again. That's what I did the second time the problem occurred, and all has returned to normal. To recover from the first occurrence, I was able to do a Alt-Ctrl-Backspace and revise the user to Root. Then in the KDE Plasma graphical environment, I added a new user with the same passwords as the one that was now with the unusable resolution in the System Settings, not an ideal solution, but the only one I knew how to make work. So Plasma doesn't ignore it as it's initially set for each user to default to the settings in the MCC >Hardware section; however, it can then be revised to override the MCC settings by root or users (a feature not a bug). 3. As I mentioned in my explanation in #2 above, after the software updates (to glibc and glibc-devel) and I rebooted as directed for it to take effect, I discovered the resolution had been revised from the default of 2560x1440 as indicated in the MCC >Hardware. The first time, I mistakenly went to the System Settings, and made a second error in setting it to an invalid resolution (for my monitor). "I was having a really bad moment!". However, the second time it happened, I reacted more sanely and went to the MCC >Hardware, and that worked. 4. I was also in error when I said it was glibm (I was trusting my memory), but thanks to your suggestion to use the rpm -qa command, I can state with certainty that it was "glibc" and "glibc-devel" when it happened yesterday (the second time). I haven't been able to find the same command around the time it happened the first time (approximately 1 - 2 weeks ago. I'll continue to try to pin it down and provide and update, but these are the 2 lines from the rpm command you provided: $ rpm -qa --last | less glibc-devel-2.32-25.mga8.x86_64 Tue 08 Feb 2022 04:12:52 PM EST glibc-2.32-25.mga8.x86_64 Tue 08 Feb 2022 04:12:52 PM EST $ I apologize for the length of this. It was difficult to be concise and provide all the info that might make your job easier. I will continue to try to discover the software updates that triggered the same problem the first time. (My bad was not writing down the date-time it occurred; although I'm pretty sure it was between 1 and 2 weeks ago). Also, the problem isn't in KScreen, but I had to pick something. Both times the reboot after specific software updates resulted in the "System Settings" desktop screen resolution being revised to 3840x2160 from the MCC >Hardare-Install graphic driver setting of 2560x1440. I am positive on the second time, it was glibc-2.32-25 and the same version for glibc-devel. They were the only revisions on that update and reboot, and it occurred immediately after the reboot. Still trying to pin down the program/programs that caused it the first time. And, it's not on every software update, just those 2 times. Please let me know if there's anything else I can provide. Thank you! Thank you for your voluminous explanations, and precisions about the occurence of the fault: > I am positive on the second time, it was glibc-2.32-25 . > They were the only revisions on that update and reboot, > and it occurred immediately after the reboot. The difference from 'glibm' to 'glibc' is primordial. > I haven't been able to find the same command around the time it happened > the first time (approximately 1 - 2 weeks ago. > I'll continue to try to pin it down and provide and update Please do not bother! The package list only shows the latest update, not any previous ones. $ rpm -qa --last | less glibc-devel-2.32-25.mga8.x86_64 Tue 08 Feb 2022 04:12:52 PM EST glibc-2.32-25.mga8.x86_64 Tue 08 Feb 2022 04:12:52 PM ES > (In reply to sturmvogel from comment #3) > The screen resolutions in systemsettings5 are provided by KDE Plasma. > The screen resolutions in MCC are provided by Mageia core system and is > independent from any desktop environment like Plasma or Gnome or whatever. Thanks for this illumination! @ Lee > Plasma doesn't ignore it as it's initially set for each user to default > to the settings in the MCC >Hardware section; however, > it can then be revised to override the MCC settings by root or users Thanks for this same enlightenement. I discover that Mate (at least) has a similar facility. Assigning this to KDE/Plasma people assuming 'systemsettings[5]' is the cause; or whatever is the source of screen resolutions to that. CC'ing tmb because of 'glibc' involvement. Source RPM:
kscreen-5.20.4-1.mga8.src.rpm =>
systemsettings-5.20.4-2.mga8.src.rpm, glibc-2.32-25.mga8.src.rpm It happened again (on 29 Apr 2022 @ 09:26:59 PM EDT). On the next boot after the following Mageia updates, the display resolution was reset from 2560 x 1440 to 3840 x 2160, the standard resolution on my Dell 32 inch Ultrasharp. In addition to updates to LibreOffice to bring it to version 7.3.2.2.1, the following 2 files were also updated (update version shown): lib64orcus0.17_0-0.17.2-1.mga8.x86_64 Fri 29 Apr 2022 09:26:59 PM EDT lib64ixion0.17_0-0.17.0-3.mga8.x86_64 Fri 29 Apr 2022 09:26:59 PM EDT I'd have to "assume" it was one of those two files that caused the display resolution to be reset without my participation or wishes! It continues to "auto" revise the display resolution from my setting of 2560 x 1440 to it's default of 3840 x 2160 every time specific library files are updated. Please let me know if you need any additional information. Many thanks! Sorry for the incomplete comment (#6) above. Here's some more info to add to my previous Comment #6. When I checked the display resolution in the Hardware section of the MCC (MCC>Hardware>"Setup the Graphical Server"), it indicates the resolution is still 2560 x 1440 24 bpp. However, when I checked the System Settings>Display and Monitor>"Display Configuration", it has been revised to 3840 x 2160, overriding the MCC>Hardware setting. So once again, a revision to a specific library file causes the Display Resolution in System Settings>Display and Monitor>"Display Configuration" to be reset to it's default setting (without any user intervention), overriding any revised resolution in the MCC>Hardware>"Setup the Graphical Server". In spite of the fact that there were no changes to the Display Resolution in either the MCC or System Settings by the user, if the display resolution has been revised in the MCC from it's default at some point prior, certain library file revisions will negate the display resolution revision and reset it back to its default by resetting the resolution in the System Settings, which override the MCC settings that are still showing the original revision. Example: Original MCC resolution: 3840 x 2160 Current MCC resolution: 2560 x 1440 lib file revision causes System Setting resolution to be reset to 3840 x 2160 Dell Display resolution is revised from 2560 x 1440 to 3840 x 2160 after library file revision even though MCC resolution is still indicating 2560 x 1440. I hope this helps to further clarify the issue. My sincere apologies if I've managed to muddy the water instead. |