mate-power-manager suddenly crashes (mate-power-manager:9756): PowerManager-ERROR **: 10:04:35.627: Error in dbus - GDBus.Error:System.Error.ESTALE: Stale file handle Trace/Breakpoint ausgelöst (Speicherabzug geschrieben) kernel: traps: mate-power-mana[9685] trap int3 ip:7f3739713227 sp:7ffc43c48460 error:0 in libglib-2.0.so.0.7600.3[7f37396d1000+93000]
The crash occured on my device. Please let me know if I should provide further information.
CC: (none) => nils.reibold
Yes, both of you please provide some information about your systems. From: $ inxi -MS and say whether this is something that repeats, or is essentially one-off.
CC: (none) => lewyssmithSource RPM: mate-power-manager => mate-power-manager-1.26.1-1.mga9.src.rpm
it is reproduceable on any hardware I have. Since I don't restart regularly, I didn't notice it at once. It worked in mga 9; but died after some of the latest updates. Just run a mate session, it should be active even on new installations. If not, just run by hand mate-power-manager. $ inxi -MS System: Host: localhost Kernel: 6.6.43-desktop-1.mga9 arch: x86_64 bits: 64 Desktop: MATE v: 1.26.1 Distro: Mageia 9 Machine: Type: Laptop System: LENOVO product: 43843DG v: ThinkPad T510 serial: <superuser required> Mobo: LENOVO model: 43843DG serial: <superuser required> BIOS: LENOVO v: 6MET61WW (1.24 ) date: 06/07/2010
$ inxi -MS System: Host: localhost Kernel: 6.6.28-desktop-1.mga9 arch: x86_64 bits: 64 Desktop: MATE v: 1.26.1 Distro: Mageia 9 Machine: Type: Laptop System: LENOVO product: 20N5S56P00 v: ThinkPad T590 serial: <superuser required> Mobo: LENOVO model: 20N5S56P00 v: SDK0J40697 WIN serial: <superuser required> UEFI: LENOVO v: N2IETA3W (1.81 ) date: 10/26/2023
inxi -MS System: Host: localhost Kernel: 6.6.43-desktop-1.mga9 arch: x86_64 bits: 64 Desktop: MATE v: 1.26.1 Distro: Mageia 9 Machine: Type: Laptop System: LENOVO product: 20FH0023GE v: ThinkPad T560 serial: <superuser required> Mobo: LENOVO model: 20FH0023GE v: SDK0J40705 WIN serial: <superuser required> UEFI: LENOVO v: N1KET21W (1.08 ) date: 04/20/2016
Thank you both for the info: laptops; both Lenovo. I have one - can try it (it needs a lot of updates first...)!
I don't think it depends on the hardware. I have the same issue on a shuttle pc. It is visible, that the small icon for power is missing, or when pressing the power button the pc instantly goes to power down, instead of asking, if suspend, reboot or power off should be reached.
Trying the Lenovo not updated for a long time, running Mate, and mate-power-manager is running (visible in ps ax; and the systray icon is there): the machine is on charge because the battery is nearly dead. mate-power-manager-1.26.1-1.mga9 dated 27 Sep 2023. I shall now update it... (see start of comment 3: "died after some of the latest updates"). 176 pkgs, 107MB. Done. Re the previous comment, pressing the power button correctly showed the multiple-choice dialogue - the pre-update mate. Chose reboot to see what happens after the updates; login back to Mate. 1) NO power manager icon in systray: confirmed. 2) mate-power-manager NOT visible with 'ps ax'. 3) Launch it from a terminal: $ mate-power-manager Then the crash as in comment 0 (core dumped). Confirmed also. 4) Pressing the power button does NOT show the exit dialogue, but closes the system down. Confirmed again. [Re comment 7, I could have tried this on my desktop machine; except power management is not relevant...] So all complaints confirmed. But the package itself seems unchanged: mate-power-manager-1.26.1-1.mga9 dated 27 Sep 2023. Looking now on my desktop box at all mate packages, most were updated Sep 2023, so I think we can discount those. These are the ones updated 2024: mate-panel-1.26.3-1.1.mga9.x86_64 11 mis Gorffennaf 2024 11 JULY lib64mate-panel-applet-gir4.0-1.26.3-1.1.mga9.x86_64 11 mis Gorffennaf 11 JULY lib64mate-panel-applet4_1-1.26.3-1.1.mga9.x86_64 11 mis Gorffennaf 2024 11 JULY mate-applets-1.26.1-1.1.mga9.x86_64 11 mis Chwefror 2024 11 FEBRUARY We can probably also discount mate-applets, updated in Feb. Which leaves the most recent July 2024 updates: mate-panel, lib64mate-panel-applet-gir4.0, lib64mate-panel-applet4_1 Can both of you try *downgrading* these 3 packages, with something like: #urpmi --downgrade [pkg-ids up to, I think, the version number] then reboot and test.
I guess it is more a dependend lib, like glibc or sth. I update my system regulary; it must be sth. changed in the last 3 weeks (maybe 4).
For downgrading, I forgot the previous veriosn numbers. All current versions are 1.26.3-1.1; the previous versions were 1.26.3-1 Marc, you can see what updates were done recently with: $ rpm -qa --last | less Once you have seen this output, you can refine the command with grep something + cut + sort to see what packages were updated for a chosen month. Looking at August, there is no glibc; just kernel and systemd. And if you want to try an earlier kernel, the boot menu should allow to choose one. We need to pin it down. Perhaps I can try one of these things; need to change desktop to Mate & explore.
Before this update (and reboot) it worked: botan2 2.19.5 1.mga9 x86_64 expat 2.6.3 1.mga9 x86_64 ffmpeg 5.1.6 1.mga9 x86_64 lib64apr1_0 1.7.5 1.mga9 x86_64 lib64assimp5 5.2.2 4.1.mga9 x86_64 lib64avcodec59 5.1.6 1.mga9 x86_64 lib64avfilter8 5.1.6 1.mga9 x86_64 lib64avformat59 5.1.6 1.mga9 x86_64 lib64avutil57 5.1.6 1.mga9 x86_64 lib64botan2_19 2.19.5 1.mga9 x86_64 lib64expat1 2.6.3 1.mga9 x86_64 lib64mariadb3 10.11.9 1.mga9 x86_64 lib64ntfs-3g89 2022.10.3 1.1.mga9 x86_64 lib64openssl3 3.0.15 1.mga9 x86_64 lib64orc0.4_0 0.4.33 1.1.mga9 x86_64 lib64pcap1 1.10.5 1.mga9 x86_64 lib64postproc56 5.1.6 1.mga9 x86_64 lib64swresample4 5.1.6 1.mga9 x86_64 lib64swscaler6 5.1.6 1.mga9 x86_64 lib64systemd0 253.24 1.mga9 x86_64 lib64tiff6 4.5.1 1.5.mga9 x86_64 lib64udev-devel 253.24 1.mga9 x86_64 lib64udev1 253.24 1.mga9 x86_64 lib64unbound8 1.21.0 1.mga9 x86_64 lib64zziplib13 0.13.72 2.2.mga9 x86_64 nodejs 22.6.0 1.mga9 x86_64 nodejs-libs 22.6.0 1.mga9 x86_64 npm 10.8.2 1.22.6.0.1.m> x86_64 nss-myhostname 253.24 1.mga9 x86_64 ntfs-3g 2022.10.3 1.1.mga9 x86_64 openssl 3.0.15 1.mga9 x86_64 php-bz2 8.2.23 1.mga9 x86_64 php-cli 8.2.23 1.mga9 x86_64 php-filter 8.2.23 1.mga9 x86_64 php-gd 8.2.23 1.mga9 x86_64 php-iconv 8.2.23 1.mga9 x86_64 php-ini 8.2.23 1.mga9 x86_64 php-intl 8.2.23 1.mga9 x86_64 php-mbstring 8.2.23 1.mga9 x86_64 php-mysqli 8.2.23 1.mga9 x86_64 php-mysqlnd 8.2.23 1.mga9 x86_64 php-openssl 8.2.23 1.mga9 x86_64 php-pcntl 8.2.23 1.mga9 x86_64 php-phar 8.2.23 1.mga9 x86_64 php-sysvsem 8.2.23 1.mga9 x86_64 php-sysvshm 8.2.23 1.mga9 x86_64 php-tokenizer 8.2.23 1.mga9 x86_64 php-zlib 8.2.23 1.mga9 x86_64 python3-unbound 1.21.0 1.mga9 x86_64 systemd 253.24 1.mga9 x86_64 vim-common 9.1.719 1.mga9 x86_64 vim-enhanced 9.1.719 1.mga9 x86_64 vim-minimal 9.1.719 1.mga9 x86_64 (Medium »Core Backports«) php8.3-bz2 8.3.9 2.mga9 x86_64 php8.3-cli 8.3.9 2.mga9 x86_64 php8.3-filter 8.3.9 2.mga9 x86_64 php8.3-gd 8.3.9 2.mga9 x86_64 php8.3-iconv 8.3.9 2.mga9 x86_64 php8.3-ini 8.3.9 2.mga9 x86_64 php8.3-intl 8.3.9 2.mga9 x86_64 php8.3-mbstring 8.3.9 2.mga9 x86_64 php8.3-mysqli 8.3.9 2.mga9 x86_64 php8.3-mysqlnd 8.3.9 2.mga9 x86_64 php8.3-openssl 8.3.9 2.mga9 x86_64 php8.3-pcntl 8.3.9 2.mga9 x86_64 php8.3-phar 8.3.9 2.mga9 x86_64 php8.3-sysvsem 8.3.9 2.mga9 x86_64 php8.3-sysvshm 8.3.9 2.mga9 x86_64 php8.3-tokenizer 8.3.9 2.mga9 x86_64 php8.3-zlib 8.3.9 2.mga9 x86_64 after the update it worked until reboot. Comparing ldd /usr/bin/mate-power-manager to those files, most likely candidates are: lib64pcap1 1.10.5 1.mga9 x86_64 lib64systemd0 253.24 1.mga9 x86_64 lib64udev1 253.24 1.mga9 x86_64 lib64zziplib13 0.13.72 2.2.mga9 x86_64 Since I am on holiday from now on - I will not be able to test some more. Bit hopefully this information helps to track the bug down; maybe a rebuild of mate-power-manager may already help....
Bad news. Running Mate on a desktop box, mate power manager not running, with the latest version of the three likely packages: mate-panel-1.26.3-1.1.mga9 lib64mate-panel-applet-gir4.0-1.26.3-1.1.mga9 lib64mate-panel-applet4_1-1.26.3-1.1.mga9 $ mate-power-manager crashed as expected: (mate-power-manager:3439): PowerManager-ERROR **: 20:50:29.138: Error in dbus - GDBus.Error:System.Error.ESTALE: Stale file handle Trace/breakpoint trap (core dumped) Downgrading these three packages to their previous versions (the string shown is what urpmi --downgrade wants): mate-panel-1.26.3-1.mga9 lib64mate-panel-applet-gir4.0-1.26.3-1.mga9 lib64mate-panel-applet4_1-1.26.3-1.mga9 then re-booting to ensure they apply - *still* the command line crash occurs. So it is something else, alas. Thanks Marc for your list, znd suggestions. ("after the update it worked until reboot": because the system was already running with the older versions, and the newest did not take effect until a reboot - I guess). I will try downgrading the packages you suggest. Latest versions (dates here): lib64pcap1-1.10.5-1.mga9 12 Sep lib64systemd0-253.24-1.mga9 24 Aug lib64udev1-253.24-1.mga9 24 Aug lib64zziplib13-0.13.72-2.2.mga9 10 Sep Previous versions: libpcap-1.10.4-1.mga9 lib64systemd0-253.16-1.mga lib64udev1-253.16-1.mga9 lib64zziplib13-0.13.72-2.1.mga9 but I will start with the systemd/udev pkgs (which also downgraded systemd itself).
Re-booted with reverted pkgs: systemd-253.16-1.mga9 lib64systemd0-253.16-1.mga9 lib64udev1-253.16-1.mga9 mate-power-manager *is* running: 2648 ? Sl 0:00 mate-power-manager and trying its command crashes it because that is so! Not the issue... There is no systray icon because ? it is not relevant on a desktop box. $ mate-power-manager (mate-power-manager:3516): PowerManager-WARNING **: 21:26:11.271: Failed to get session for pid 3516: The name org.freedesktop.ConsoleKit was not provided by any .service files (mate-power-manager:3516): PowerManager-WARNING **: 21:26:11.277: could not map keysym 1008ffa8 to keycode (mate-power-manager:3516): PowerManager-ERROR **: 21:26:11.311: Rheolwr Pŵer is already running in this session. Trace/breakpoint trap (core dumped) I will need to try this on the laptop - tomorrow.
Have just done so. See comment 8 for the starting point with all the faults, Mate desktop on a laptop. I downgraded *just* systemd etc to: systemd-253.16-1.mga9 lib64systemd0-253.16-1.mga9 re-booted, and Lo! The battery application appeared in Systray, and mate-power-manager was running. Pointless to try launching it from terminal. Well guessed Marc.
Summary: mate-power-manager crashes => mate-power-manager crashes since latest systemd update to 253.24-1; worked with previous 253.16-1Assignee: bugsquad => pkg-bugs
CC: (none) => smelror
@Stig: you did the last update; maybe you can have a look into it; or try to rebuild the package as a first try?
I did not consider one thing: dbus "(mate-power-manager:9756): PowerManager-ERROR **: 10:04:35.627: Error in dbus - GDBus.Error:System.Error.ESTALE: Stale file handle" But that was last updated Feb 2023, so cannot be the reason.
do U know, how to use debuginfo-install ? Found the page: https://wiki.mageia.org/en/Debugging_software_crashes But gdb wants additional debug packages: Missing separate debuginfos, use: debuginfo-install gvfs-1.50.4-1.mga9.x86_64 lib64atk-bridge2.0_0-2.48.3-2.mga9.x86_64 .... Running this command does not work, as debug source has to be enabled somehow. I guess this page should be updated, to better know how to debug.
Added a an upstream bug report. Rebuild of the package did not help.
See Also: (none) => https://github.com/mate-desktop/mate-power-manager/issues/400
Tested again. Systemd update kills mate-power-manager (gdbus)
systemd-253.25 (latest release) does not work either :( hoped, it was already discovered and fixed...
I seem to have this same problem with kde plasma and its power manager. Suspend on laptops isn't as reliable as it has been. But on all my desktops (asus amd, dell small form factor with intel gen 5 i5 cpu, and dell workstation with 2020 era xeon processor all shutdown immediately when pressed, even when kde is configured to suspend on power button press. Also sometimes when in suspend, it wakes when the power button is pressed, but then immediately powers off. I, too, suspect this is due to the systemd update.
CC: (none) => dvdgrttr
yeah. That looks quite the same, even if the app does not crash. Maybe we should check the changelogs on systemd in more detail. Or test which version introduced this behaviour.
I've done some extensive tests and compiled a all systemd patch releases since 16: 16-23 works 24,25 don't - after install of 24 reboot hangs and mate-power-manager does not work anymore
See Also: (none) => https://github.com/systemd/systemd-stable/issues/447
pushed a fix for systemd (reverting a patch which introduced the problem); tested on my laptops. ============== This update fixes some issues on laptops (or desktops) with suspend/resume or using the powerbutton. Before this patch pressing the power button immediately powered the system off. After this patch, the desktop manager asks again, if it should suspend, power off or reboot. Also events for closing the lid, setting brightness and/or showing the battery status now work again. References: https://github.com/systemd/systemd-stable/issues/447 ======================== Updated packages in core/updates_testing: ======================== systemd-253.24-3.mga9.src.rpm systemd-homed-debuginfo-253.24-3.mga9.x86_64.rpm lib64systemd0-debuginfo-253.24-3.mga9.x86_64.rpm nss-myhostname-253.24-3.mga9.x86_64.rpm lib64udev1-debuginfo-253.24-3.mga9.x86_64.rpm nss-myhostname-debuginfo-253.24-3.mga9.x86_64.rpm lib64systemd0-253.24-3.mga9.x86_64.rpm lib64udev1-253.24-3.mga9.x86_64.rpm systemd-homed-253.24-3.mga9.x86_64.rpm systemd-devel-253.24-3.mga9.x86_64.rpm lib64udev-devel-253.24-3.mga9.x86_64.rpm systemd-tests-253.24-3.mga9.x86_64.rpm systemd-tests-debuginfo-253.24-3.mga9.x86_64.rpm systemd-253.24-3.mga9.x86_64.rpm systemd-debugsource-253.24-3.mga9.x86_64.rpm x86_64/systemd-debuginfo-253.24-3.mga9.x86_64.rpm SRPM: systemd-253.24-3.mga9.src.rpm
Severity: normal => majorAssignee: pkg-bugs => qa-bugs
Source RPM: mate-power-manager-1.26.1-1.mga9.src.rpm => systemd
Keywords: (none) => advisory
RH x86_64 Update without issues Reboot System start without issues rpm -qa|grep 253.24-3 lib64systemd0-253.24-3.mga9 nss-myhostname-253.24-3.mga9 systemd-253.24-3.mga9 lib64udev1-253.24-3.mga9 Tomorrow will test in my i586 laptop
MGA9-64 server MATE on HP-Pavillion No installation issues omitting the debug and src packages. After installation reboot Find mate-power-manager already running. $ ps -aux | grep power root 852 0.0 0.1 309572 6144 ? Ssl 10:58 0:00 /usr/libexec/upowerd tester9 56965 0.0 0.8 568368 30984 ? Sl 11:05 0:00 mate-power-manager tester9 58763 0.0 0.0 9492 2304 pts/0 S+ 11:19 0:00 grep --color power To be sure I could restart it [tester9@mach4 ~]$ kill 56965 [tester9@mach4 ~]$ ps -aux | grep power root 852 0.0 0.1 309572 6144 ? Ssl 10:58 0:00 /usr/libexec/upowerd tester9 58818 0.0 0.0 9492 2304 pts/0 S+ 11:20 0:00 grep --color power [tester9@mach4 ~]$ mate-power-manager (mate-power-manager:58825): PowerManager-WARNING **: 11:20:21.155: Failed to get session for pid 58825: The name org.freedesktop.ConsoleKit was not provided by any .service files (mate-power-manager:58825): PowerManager-WARNING **: 11:20:21.166: could not map keysym 1008ffa8 to keycode (mate-power-manager:58825): Gdk-CRITICAL **: 11:20:21.301: gdk_window_thaw_toplevel_updates: assertion 'window->update_and_descendants_freeze_count > 0' failed And the konsole hangs, indicating mate-power-manager runs. Ctrl-C stops it. Start it again and from other konsole tab: ps -aux | grep power root 852 0.0 0.1 309572 6144 ? Ssl 10:58 0:00 /usr/libexec/upowerd tester9 59111 0.8 0.8 568372 31140 pts/0 Sl+ 11:25 0:00 mate-power-manager root 59156 0.0 0.0 9488 2304 pts/1 S+ 11:26 0:00 grep --color power AFAICS, this seems OK, but waiting for other tests on other HW.
CC: (none) => herman.viaene
RH i586 LC_ALL=C urpmi --auto --auto-update medium "QA Testing (32-bit)" is up-to-date medium "Core Release (distrib1)" is up-to-date medium "Core Updates (distrib3)" is up-to-date medium "Nonfree Release (distrib11)" is up-to-date medium "Nonfree Updates (distrib13)" is up-to-date medium "Tainted Release (distrib21)" is up-to-date medium "Tainted Updates (distrib23)" is up-to-date installing libsystemd0-253.24-3.mga9.i586.rpm libudev-devel-253.24-3.mga9.i586.rpm systemd-253.24-3.mga9.i586.rpm libudev1-253.24-3.mga9.i586.rpm nss-myhostname-253.24-3.mga9.i586.rpm from //home/katnatek/qa-testing/i586 Preparing... ####################################################################################### 1/5: nss-myhostname ####################################################################################### 2/5: libudev1 ####################################################################################### 3/5: libsystemd0 ####################################################################################### 4/5: libudev-devel ####################################################################################### 5/5: systemd ####################################################################################### 1/5: removing systemd-253.24-1.mga9.i586 ####################################################################################### 2/5: removing libudev-devel-253.24-1.mga9.i586 ####################################################################################### 3/5: removing libudev1-253.24-1.mga9.i586 ####################################################################################### 4/5: removing libsystemd0-253.24-1.mga9.i586 ####################################################################################### 5/5: removing nss-myhostname-253.24-1.mga9.i586 ####################################################################################### You should restart your computer for systemd Reboot Start session OK Open some aplication and hibernate, after back from hibernation applications are as expected Suspend and resume OK Looks good to me
System: Kernel: 6.6.52-desktop-1.mga9 arch: x86_64 bits: 64 compiler: gcc v: 12.3.0 Desktop: MATE v: 1.26.1 info: mate-panel wm: marco v: 1.26.2 vt: 2 dm: 1: LightDM v: 1.32.0 note: stopped 2: LXDM note: stopped 3: SDDM Distro: Mageia 9 Machine: Type: Laptop System: TOSHIBA product: Satellite C50D-B v: PSCN4A-01600H serial: <superuser required> Mobo: TOSHIBA model: ZBWAE v: 1.00 serial: <superuser required> UEFI: TOSHIBA v: 1.30 date: 06/06/2014 $ rpm -qa --last | grep systemd | cut -d ' ' -f 1 libsystemd0-253.24-1.mga9.i586 systemd-253.24-1.mga9.x86_64 lib64systemd0-253.24-1.mga9.x86_64 rpm-plugin-systemd-inhibit-4.18.2-1.mga9.x86_64 $ mate-power-manager (mate-power-manager:4497): PowerManager-ERROR **: 11:32:36.570: Error in dbus - GDBus.Error:System.Error.ESTALE: Stale file handle Trace/breakpoint trap (core dumped) note: instant power off is not apparent on this hardware , I always get the dialogue boxes. # urpmi systemd To satisfy dependencies, the following packages are going to be installed: Package Version Release Arch (medium "Core Updates Testing (distrib5)") lib64systemd0 253.24 3.mga9 x86_64 systemd 253.24 3.mga9 x86_64 1.6KB of additional disk space will be used. 7.5MB of packages will be retrieved. Proceed with the installation of the 2 packages? (Y/n) y reboot $ ps -aux | grep power root 879 0.0 0.0 309600 6400 ? Ssl 11:44 0:00 /usr/libexec/upowerd work 2155 0.1 0.4 504044 32504 ? Sl 11:57 0:00 mate-power-manager work 3452 0.1 0.4 421000 30960 ? Sl 11:59 0:00 xfce4-power-manager-settings root 3508 0.0 0.0 0 0 ? I 11:59 0:00 [kworker/1:2-events_power_efficient] work 4033 0.0 0.0 9492 2432 pts/0 S+ 12:04 0:00 grep --color power $ mate-power-manager (mate-power-manager:3671): PowerManager-WARNING **: 12:00:31.312: Failed to get session for pid 3671: The name org.freedesktop.ConsoleKit was not provided by any .service files (mate-power-manager:3671): PowerManager-WARNING **: 12:00:31.327: could not map keysym 1008ffa8 to keycode (mate-power-manager:3671): PowerManager-ERROR **: 12:00:31.465: Power Manager is already running in this session. Trace/breakpoint trap (core dumped) power off dialogue boxes work correctly
CC: (none) => westel
mga9-64 OK here on three systems using Plasma and SDDM Tested normal operation and suspend-resume and hibernate-resume --- My workstation svarten Host: svarten.tribun Kernel: 6.6.52-desktop-1.mga9 arch: x86_64 bits: 64 compiler: gcc v: 12.3.0 Desktop: KDE Plasma v: 5.27.10 Distro: Mageia 9 Machine: Type: Desktop Mobo: ASRock model: P55 Pro serial: <superuser required> BIOS: American Megatrends v: P2.60 date: 08/20/2010 --- Laptop Acer Aspire 7 Host: aspire7-kajsa Kernel: 6.6.52-desktop-1.mga9 arch: x86_64 bits: 64 compiler: gcc v: 12.3.0 Desktop: KDE Plasma v: 5.27.10 Distro: Mageia 9 Machine: Type: Laptop System: Acer product: Aspire A717-71G v: V1.13 serial: <superuser required> Mobo: KBL model: Charizard_KLS v: V1.13 serial: <superuser required> UEFI: Insyde v: 1.13 date: 12/26/2017 --- My Laptop Asus G75V Host: republic.tribun Kernel: 6.6.52-desktop-1.mga9 arch: x86_64 bits: 64 compiler: gcc v: 12.3.0 Desktop: KDE Plasma v: 5.27.10 Distro: Mageia 9 Machine: Type: Laptop System: ASUSTeK product: G75VW v: 1.0 serial: <superuser required> Mobo: ASUSTeK model: G75VW v: 1.0 serial: <superuser required> UEFI: American Megatrends v: G75VW.223 date: 01/07/2013
CC: (none) => fri
See Also: (none) => https://bugs.mageia.org/show_bug.cgi?id=33649
*** Bug 33649 has been marked as a duplicate of this bug. ***
CC: (none) => flink
We have at less other issue fixed by this update https://bugs.mageia.org/show_bug.cgi?id=33649#c6
CC: (none) => andrewsfarm
MGA9-64 Plasma, i5-7500. Confirmed the power button issue before the update, updated the packages with no issues, rebooted, power button issue fixed. Tried a few informational commands, all OK. This looks OK to me. Also giving it a 32-bit OK based on comment 27. Validating.
Keywords: (none) => validated_updateWhiteboard: (none) => MGA9-32-OK MGA9-64-OKCC: (none) => sysadmin-bugs
An update for this issue has been pushed to the Mageia Updates repository. https://advisories.mageia.org/MGAA-2024-0211.html
Status: NEW => RESOLVEDResolution: (none) => FIXED