Version-Release number of selected component: mate-screensaver-1.26.0-1.fc34 Additional info: reporter: libreport-2.15.2 backtrace_rating: 4 cgroup: 0::/user.slice/user-500.slice/user/app.slice/dbus-:1.2-org.mate.ScreenSaver cmdline: /usr/bin/mate-screensaver --no-daemon crash_function: matemenu_tree_item_ref executable: /usr/bin/mate-screensaver journald_cursor: s=889922389d974075be0b065b0cd326c0;i=15cb8;b=d17c467f09e440e29b8a0f2d6496cbea;m=18bb80fe;t=5ca684514f3bd;x=bf6e66c38478500d kernel: 5.13.12-200.fc34.x86_64 rootdir: / runlevel: N 5 type: CCpp uid: 500 Truncated backtrace: Thread no. 1 (10 frames) #0 matemenu_tree_item_ref at /usr/src/debug/mate-menus-1.26.0-1.fc34.x86_64/libmenu/matemenu-tree.c:1799 #1 find_info_for_id at /usr/src/debug/mate-screensaver-1.26.0-1.fc34.x86_64/src/gs-theme-manager.c:270 #2 gs_theme_manager_lookup_theme_info at /usr/src/debug/mate-screensaver-1.26.0-1.fc34.x86_64/src/gs-theme-manager.c:308 #3 manager_select_theme_for_job at /usr/src/debug/mate-screensaver-1.26.0-1.fc34.x86_64/src/gs-manager.c:257 #4 manager_show_window at /usr/src/debug/mate-screensaver-1.26.0-1.fc34.x86_64/src/gs-manager.c:1318 #5 window_show_cb at /usr/src/debug/mate-screensaver-1.26.0-1.fc34.x86_64/src/gs-manager.c:1352 #10 gtk_widget_show at /usr/src/debug/gtk3-3.24.30-1.fc34.x86_64/gtk/gtkwidget.c:4848 #11 show_windows at /usr/src/debug/mate-screensaver-1.26.0-1.fc34.x86_64/src/gs-manager.c:1781 #12 gs_manager_activate at /usr/src/debug/mate-screensaver-1.26.0-1.fc34.x86_64/src/gs-manager.c:1857 #13 gs_manager_set_active at /usr/src/debug/mate-screensaver-1.26.0-1.fc34.x86_64/src/gs-manager.c:1903
Created attachment 1817617 [details] File: backtrace
Created attachment 1817618 [details] File: core_backtrace
Created attachment 1817619 [details] File: cpuinfo
Created attachment 1817620 [details] File: dso_list
Created attachment 1817621 [details] File: environ
Created attachment 1817622 [details] File: exploitable
Created attachment 1817623 [details] File: limits
Created attachment 1817624 [details] File: maps
Created attachment 1817625 [details] File: mountinfo
Created attachment 1817626 [details] File: open_fds
Created attachment 1817627 [details] File: proc_pid_status
*** Bug 1998185 has been marked as a duplicate of this bug. ***
Please post command output. rpm -qa libmate* caja* engrampa* atril* pluma* mozo* python3-caja mate*
And why user id 500 ?
UID 500 is me Bob Bob@engineering ~$ rpm -qa libmate* caja* engrampa* atril* pluma* mozo* python3-caja mate* libmateweather-data-1.26.0-1.fc34.noarch libmateweather-1.26.0-1.fc34.x86_64 libmatekbd-1.26.0-1.fc34.x86_64 caja-schemas-1.26.0-1.fc34.x86_64 pluma-data-1.26.0-1.fc34.noarch pluma-1.26.0-1.fc34.x86_64 libmatemixer-1.26.0-1.fc34.x86_64 caja-core-extensions-1.26.0-1.fc34.x86_64 caja-1.26.0-1.fc34.x86_64 caja-extensions-common-1.26.0-1.fc34.noarch caja-actions-doc-1.26.0-1.fc34.noarch atril-libs-1.26.0-1.fc34.x86_64 pluma-devel-1.26.0-1.fc34.x86_64 atril-1.26.0-1.fc34.x86_64 caja-actions-1.26.0-1.fc34.x86_64 caja-open-terminal-1.26.0-1.fc34.x86_64 mozo-1.26.0-1.fc34.noarch Bob@engineering ~$ Note system mate currently downgraded to 1.24 in order to have a working system. Bob@engineering ~$ sudo dnf list installed mate*1.24* Installed Packages mate-applets.x86_64 1.24.1-3.fc34 @fedora mate-backgrounds.noarch 1.24.2-3.fc34 @fedora mate-calc.x86_64 1.24.2-1.fc34 @fedora mate-common.noarch 1.24.2-3.fc34 @updates mate-control-center.x86_64 1.24.2-1.fc34 @fedora mate-control-center-devel.x86_64 1.24.2-1.fc34 @fedora mate-control-center-filesystem.x86_64 1.24.2-1.fc34 @fedora mate-desktop.x86_64 1.24.1-6.fc34 @updates mate-desktop-devel.x86_64 1.24.1-6.fc34 @updates mate-desktop-libs.x86_64 1.24.1-6.fc34 @updates mate-dictionary.x86_64 1.24.0-3.fc34 @fedora mate-disk-image-mounter.x86_64 1.24.0-3.fc34 @fedora mate-disk-usage-analyzer.x86_64 1.24.0-3.fc34 @fedora mate-icon-theme.noarch 1.24.0-3.fc34 @fedora mate-media.x86_64 1.24.1-2.fc34 @fedora mate-menus.x86_64 1.24.1-2.fc34 @fedora mate-menus-devel.x86_64 1.24.1-2.fc34 @fedora mate-menus-libs.x86_64 1.24.1-2.fc34 @fedora mate-menus-preferences-category-menu.x86_64 1.24.1-2.fc34 @fedora mate-notification-daemon.x86_64 1.24.2-1.fc34 @fedora mate-panel.x86_64 1.24.2-2.fc34 @fedora mate-panel-devel.x86_64 1.24.2-2.fc34 @fedora mate-panel-libs.x86_64 1.24.2-2.fc34 @fedora mate-polkit.x86_64 1.24.0-4.fc34 @fedora mate-power-manager.x86_64 1.24.3-1.fc34 @fedora mate-screensaver.x86_64 1.24.2-1.fc34 @fedora mate-screensaver-devel.x86_64 1.24.2-1.fc34 @fedora mate-screenshot.x86_64 1.24.0-3.fc34 @fedora mate-search-tool.x86_64 1.24.0-3.fc34 @fedora mate-sensors-applet.x86_64 1.24.1-2.fc34 @fedora mate-sensors-applet-devel.x86_64 1.24.1-2.fc34 @fedora mate-session-manager.x86_64 1.24.3-1.fc34 @updates mate-settings-daemon.x86_64 1.24.2-2.fc34 @fedora mate-settings-daemon-devel.x86_64 1.24.2-2.fc34 @fedora mate-system-log.x86_64 1.24.0-3.fc34 @fedora mate-system-monitor.x86_64 1.24.2-1.fc34 @fedora mate-terminal.x86_64 1.24.1-2.fc34 @fedora mate-user-guide.noarch 1.24.0-3.fc34 @fedora mate-utils.x86_64 1.24.0-3.fc34 @fedora mate-utils-common.noarch 1.24.0-3.fc34 @fedora mate-utils-devel.x86_64 1.24.0-3.fc34 @fedora Bob@engineering ~$ Also note, on an unrelated system, a laptop, experienced the screensaver failure. Reported as https://bugzilla.redhat.com/show_bug.cgi?id=1998185 Also, archlinux user reports problems after 1.26 update https://bbs.archlinux.org/viewtopic.php?pid=1989238#p1989238
Do not mix 1.24 and 1.26. How should we debug a 1.26 package when needed dependencies aren't installed? Again, why you don't use normal user id ?
Obviously can't debug a mixed system. All the dumps/reports were for the upgraded 1.26 dysfunctional system. The listing in comment 15 was in quick response to comment 13, which was generated on the working mixed system, as there was no time to recreate the complete 1.26 broken system at that time. UID 500 was the normal UID when the system was first created on Fri 30 Oct 2009 as recorded for folder /home/Bob. System has been continually updated and migrated since first creation. The apparent latter year administrative switch to UID's starting at 1000 seems to have no bearing on current proper operation.
Can you please file out reports at upstream. Maybe they can reproduce your problems. Sorry, i can't reproduce non of them. https://github.com/mate-desktop/mate-panel/issues https://github.com/mate-desktop/mate-screensaver/issues
Ok, thank you for your help. I have filed upstream reports. https://github.com/mate-desktop/mate-screensaver/issues/253 https://github.com/mate-desktop/mate-panel/issues/1249
Amazing, do you really think that developers from unbutu/debian will really look in your reports when you only give a link to rhbz? You're very optimistic. Please provide as much information as possible. Why you expect help from developers when you write simply nothing?
Problem essentially resolved. Dconf settings were incompatible with 1.26 for some reason.
Problem not resolved. Although 1.26 panel malfunctions were traced to nvidia, after removing nvidia and running nouveau, the screensaver bug still persists. Sometimes the screensaver will engage a few times properly, but then it will not respond to manual initiation. The failed manual starts are accompanied by aborts.
*** Bug 2003466 has been marked as a duplicate of this bug. ***
Similar problem has been detected: i left the linux mate desktop idle. when i came back the screen was black and would not wake up. was able to open a new text terminal and reboot from there. was not able to see anything or wakeup the X graphical screen before reboot. reporter: libreport-2.15.2 backtrace_rating: 4 cgroup: 0::/user.slice/user-1000.slice/session-4.scope cmdline: mate-screensaver crash_function: matemenu_tree_item_ref executable: /usr/bin/mate-screensaver journald_cursor: s=dd1adf77adfd4533b5ee6e39a1e67058;i=76252;b=7a3c62256edf4e43852b18e10b08e943;m=dfbc31c6;t=5cc01c85fc7b6;x=d503e100721ff666 kernel: 5.13.12-200.fc34.x86_64 package: mate-screensaver-1.26.0-1.fc34 reason: mate-screensaver killed by SIGSEGV rootdir: / runlevel: 3 5 type: CCpp uid: 1000
(In reply to Victor Stratan from comment #24) > Similar problem has been detected: > > i left the linux mate desktop idle. when i came back the screen was black > and would not wake up. was able to open a new text terminal and reboot from > there. was not able to see anything or wakeup the X graphical screen before > reboot. Exactly the scenario I'm encountering on a half-dozen hosts. I've taken to chmod -x /usr/bin/mate-screensaver until we get some resolution.
Update. Experience with 1.26 had been terrible. Screensaver lockups on multiple F34 systems. In view of the other problem with nvidia incompatibility, I've had to downgrade two systems to 1.24 level, which has worked flawlessly (as it did previous to the the 1.26 problem upgrade) for the past two weeks. The "acid test" clean install with nouveau vs. nvidia drivers under 1.26 clearly isolates the problem to 1.26 and the proprietary nvidia driver. 1.24 works fine. Something changed/added to 1.26, possibly Wayland related, must be responsible for the faulty operation. The major concern is that F35, when released, might be stuck with a dysfunctional 1.26 MATE version, making an F35 upgrade a non-option here. Currently, all updates here require "--exclude=caja*,libmate*,marco*,mate*,eom*" option following the complete downgrade to 1.24.
(In reply to Victor Stratan from comment #24) > Similar problem has been detected: > > i left the linux mate desktop idle. when i came back the screen was black > and would not wake up. was able to open a new text terminal and reboot from > there. was not able to see anything or wakeup the X graphical screen before > reboot. > Thank you for giving the first useful information in this report. So steps to reproduce are: 1. Leaving desktop in idle, no lock screen by hand, or closing lid. 2. Mate session will be locked automatically by default screensaver settings 3. Screensaver theme `black screen` is running, the monitor isn't power off 4. You coming back and pressing any key doesn't give you the unlock dialog. 5. You could open another console and reboot from there. Some questions: System wasn't suspended or monitor was power off? Can you please test this setting? ``` [rave@mother ~]$ gsettings get org.mate.screensaver lock-enabled false [rave@mother ~]$ gsettings get org.mate.screensaver idle-activation-enabled true ``` Use `gesettings set org.mate.screensaver lock-enabled false && gesettings set org.mate.screensaver idle-activation-enabled true` I like to know if the unlock-dialog causes the issue or the screensaver itself. If this steps to reproduce i can try to reproduce it on my notebook. Sorry, normally i use a workstation without needed to lock my screen. And in the evening i simply power off my box. I am also wondering about the crash function `matemenu_tree_item_ref`, because this comes from mate-menus and is only use by mate-panel and not by mate-screensaver. ``` [rave@mother github-matedesktop]$ grep -nr matemenu_tree_item_ref * mate-menus/libmenu/matemenu-tree.c:869: return matemenu_tree_item_ref (tree->root); mate-menus/libmenu/matemenu-tree.c:948: return directory ? matemenu_tree_item_ref (directory) : NULL; mate-menus/libmenu/matemenu-tree.c:970: matemenu_tree_item_ref (entry); mate-menus/libmenu/matemenu-tree.c:985: return item->parent ? matemenu_tree_item_ref (item->parent) : NULL; mate-menus/libmenu/matemenu-tree.c:1106: g_slist_foreach (iter->contents, (GFunc) matemenu_tree_item_ref, NULL); mate-menus/libmenu/matemenu-tree.c:1151: return (MateMenuTreeDirectory*)matemenu_tree_item_ref (iter->item); mate-menus/libmenu/matemenu-tree.c:1170: return (MateMenuTreeEntry*)matemenu_tree_item_ref (iter->item); mate-menus/libmenu/matemenu-tree.c:1189: return (MateMenuTreeHeader*)matemenu_tree_item_ref (iter->item); mate-menus/libmenu/matemenu-tree.c:1208: return (MateMenuTreeAlias*)matemenu_tree_item_ref (iter->item); mate-menus/libmenu/matemenu-tree.c:1227: return (MateMenuTreeSeparator*)matemenu_tree_item_ref (iter->item); mate-menus/libmenu/matemenu-tree.c:1453: return matemenu_tree_item_ref (header->directory); mate-menus/libmenu/matemenu-tree.c:1485: return matemenu_tree_item_ref(alias->directory); mate-menus/libmenu/matemenu-tree.c:1532: return (MateMenuTreeDirectory *) matemenu_tree_item_ref (alias->aliased_item); mate-menus/libmenu/matemenu-tree.c:1547: return (MateMenuTreeEntry *) matemenu_tree_item_ref (alias->aliased_item); mate-menus/libmenu/matemenu-tree.c:1668: retval->directory = matemenu_tree_item_ref (directory); mate-menus/libmenu/matemenu-tree.c:1701: retval->directory = matemenu_tree_item_ref (directory); mate-menus/libmenu/matemenu-tree.c:1703: retval->aliased_item = matemenu_tree_item_ref (item); mate-menus/libmenu/matemenu-tree.c:1707: retval->aliased_item = matemenu_tree_item_ref (alias->aliased_item); mate-menus/libmenu/matemenu-tree.c:1786: * matemenu_tree_item_ref: mate-menus/libmenu/matemenu-tree.c:1792:matemenu_tree_item_ref (gpointer itemp) mate-menus/libmenu/matemenu-tree.c:4362: matemenu_tree_item_ref (alias)); mate-menus/libmenu/matemenu-tree.c:4399: matemenu_tree_item_ref (subdir)); mate-menus/libmenu/matemenu-tree.c:4445: matemenu_tree_item_ref (entry)); mate-menus/libmenu/matemenu-tree.c:5011: (GBoxedCopyFunc)matemenu_tree_item_ref, mate-menus/libmenu/matemenu-tree.c:5024: (GBoxedCopyFunc)matemenu_tree_item_ref, mate-menus/libmenu/matemenu-tree.c:5037: (GBoxedCopyFunc)matemenu_tree_item_ref, mate-menus/libmenu/matemenu-tree.c:5050: (GBoxedCopyFunc)matemenu_tree_item_ref, mate-menus/libmenu/matemenu-tree.c:5063: (GBoxedCopyFunc)matemenu_tree_item_ref, mate-menus/libmenu/matemenu-tree.h:106:gpointer matemenu_tree_item_ref (gpointer item); mate-panel/mate-panel/menu.c:931: matemenu_tree_item_ref (directory), mate-panel/mate-panel/menu.c:1040: matemenu_tree_item_ref (header), mate-panel/mate-panel/menu.c:1058: matemenu_tree_item_ref (entry), mate-panel/mate-panel/menu.c:1067: matemenu_tree_item_ref (alias_directory) ``` (In reply to todd_lewis from comment #25) > (In reply to Victor Stratan from comment #24) > > Similar problem has been detected: > > > > i left the linux mate desktop idle. when i came back the screen was black > > and would not wake up. was able to open a new text terminal and reboot from > > there. was not able to see anything or wakeup the X graphical screen before > > reboot. > > Exactly the scenario I'm encountering on a half-dozen hosts. I've taken to > chmod -x /usr/bin/mate-screensaver > until we get some resolution. Why? Simply disable desktop-idle/lock might be a better workaround. ``` [rave@mother ~]$ gsettings get org.mate.screensaver lock-enabled false [rave@mother ~]$ gsettings get org.mate.screensaver idle-activation-enabled false ``` @Bob Cross posting other non related problems again and again with your box isn't helpful. Better post steps to reproduce this issue with mate-screensaver.
Q: System wasn't suspended or monitor was power off? A: system wasn't suspended. It was on a desktop that does not suspend or power off or hibernate. If you have a way to check the settings, I can do that. I did not lock the system manually. Settings: [user@localhost ~]$ gsettings get org.mate.screensaver lock-enabled false [user@localhost ~]$ gsettings get org.mate.screensaver idle-activation-enabled true I remember before this incident the screen save worked without issues. Today I tried to reproduce the issue by leaving the desktop idle and seeing if the issue occurs. I was unable to reproduce the issue. I did not modify any settings. When the issue occurred, i did not see the unlock dialog, when i tried to "wakeup from screensaver". The screensaver was not showing any pictures, I have is configured to show the pictures on planets.
Do you have xscreensaver installed? Please remove. Does this fix your issue?
Scratch build from mate-menus. Does this fix your issue? https://koji.fedoraproject.org/koji/taskinfo?taskID=77341614
*** Bug 2014897 has been marked as a duplicate of this bug. ***
After applying updates from standard Fedora distro updates, i intentionally left the desktop to idle many times over the weekend, the problem did not repeat. If the issue happens again, will update this ticket.
(In reply to Victor Stratan from comment #32) > After applying updates from standard Fedora distro updates, i intentionally > left the desktop to idle many times over the weekend, the problem did not > repeat. > > If the issue happens again, will update this ticket. Any chance of testing? https://koji.fedoraproject.org/koji/taskinfo?taskID=77341614 This package is not in standard repositories.
I am now on mate-menus-1.26.0-1.fc34.x86_64 and the issue does not reproduce. Since I cannot reproduce the issue any more, not sure what value would be testing the package that you linked.
I reverted an upstream commit which is confirmed by ubuntu users that is fixes problems with up coming ubuntu-21.10. https://github.com/mate-desktop/mate-panel/issues/1260#issuecomment-941646715 But i can't reproduce the issue for myself in result some reporters from this report needs to confirm that https://koji.fedoraproject.org/koji/taskinfo?taskID=77341614 helps.
Similar problem has been detected: Left the screensaver running for hours. Nothing else. reporter: libreport-2.15.2 backtrace_rating: 4 cgroup: 0::/user.slice/user-12428.slice/session-2.scope cmdline: mate-screensaver crash_function: matemenu_tree_item_ref executable: /usr/bin/mate-screensaver journald_cursor: s=df6f3d8bf54144cc8859ece144e1447d;i=3bd12;b=eb85e970198049b39640c4453d8a2258;m=f2e0050b2;t=5ced2f9e2d8f2;x=bfdcbe8a2c622551 kernel: 5.14.10-200.fc34.x86_64 package: mate-screensaver-1.26.0-1.fc34 reason: mate-screensaver killed by SIGSEGV rootdir: / runlevel: N 5 type: CCpp uid: 12428
And from another host: Oct 21 08:57:12 riverkym abrt-server[7567]: Deleting problem directory ccpp-2021-10-21-08:57:11.938403-1511 (dup of ccpp-2021-09-11-08:18:44.365051-1512) Oct 21 08:57:12 riverkym abrt-notification[7608]: [🡕] Process 1512 (mate-screensaver) crashed in matemenu_tree_item_ref()
@todd_lewis or every otrher here..... Why not testing https://koji.fedoraproject.org/koji/taskinfo?taskID=77341614 with a fix for you problems?
(In reply to Wolfgang Ulbrich from comment #38) > @todd_lewis > or every otrher here..... > Why not testing https://koji.fedoraproject.org/koji/taskinfo?taskID=77341614 > with a fix for you problems? I'm not deeply involved with maintaining Fedora packages or using koji; I clicked around a while and went down several rabbit holes before giving up. Apologies if it's something obvious that I just missed, but could you please explain how to go from the link you provided to an rpm I can install and test? Thanks.
(In reply to todd_lewis from comment #39) > (In reply to Wolfgang Ulbrich from comment #38) > > @todd_lewis > > or every otrher here..... > > Why not testing https://koji.fedoraproject.org/koji/taskinfo?taskID=77341614 > > with a fix for you problems? > > I'm not deeply involved with maintaining Fedora packages or using koji; I > clicked around a while and went down several rabbit holes before giving up. > Apologies if it's something obvious that I just missed, but could you please > explain how to go from the link you provided to an rpm I can install and > test? Thanks. 1. select the link with the correct arch of your box you want to install the update. (eg. `buildArch (mate-menus-1.26.0-2.fc34.src.rpm, x86_64)` for x86_64, etc.) 2. in next page download (example for x86_64) mate-menus-1.26.0-2.fc34.x86_64.rpm and mate-menus-libs-1.26.0-2.fc34.x86_64.rpm. The -devel package you need only for compiling other packages. I don't think that you ever did this, in result you don't need this package! 3. In download folder of packages do `dnf install mate-menus-1.26.0-2.fc34.x86_64.rpm mate-menus-libs-1.26.0-2.fc34.x86_64.rpm` ... this is a very easy task , hopefully.
PS: This page (koji) is the fedora build server where fedora builds all packages. You can download everything for fedora from there for all branches....
Still getting SEGV in mate-screensaver even with the 1.26.0-2 rpms; see bug #2016789.
Could you please test this mate-screensaver build with an upstream fix? https://koji.fedoraproject.org/koji/taskinfo?taskID=78290275
Test build included this fix. https://github.com/mate-desktop/mate-screensaver/pull/262
(In reply to Wolfgang Ulbrich from comment #43) > Could you please test this mate-screensaver build with an upstream fix? > https://koji.fedoraproject.org/koji/taskinfo?taskID=78290275 I no longer have ready access to any f34 installs. We've moved them all to Fedora 35.
(In reply to todd_lewis from comment #45) > (In reply to Wolfgang Ulbrich from comment #43) > > Could you please test this mate-screensaver build with an upstream fix? > > https://koji.fedoraproject.org/koji/taskinfo?taskID=78290275 > > I no longer have ready access to any f34 installs. We've moved them all to > Fedora 35. Resurrected a couple of f34 hosts and installed the updated rpm. Fingers crossed. Do we know specifically what triggers the bug? Because if it's fixed, we could be waiting a long time.
(In reply to todd_lewis from comment #46) > (In reply to todd_lewis from comment #45) > > (In reply to Wolfgang Ulbrich from comment #43) > > > Could you please test this mate-screensaver build with an upstream fix? > > > https://koji.fedoraproject.org/koji/taskinfo?taskID=78290275 > > > > I no longer have ready access to any f34 installs. We've moved them all to > > Fedora 35. > > Resurrected a couple of f34 hosts and installed the updated rpm. Fingers > crossed. > > Do we know specifically what triggers the bug? Because if it's fixed, we > could be waiting a long time. In link to upstream pull request are steps to reproduce. But you posted here that you had crashes, so are this crashes gone or not with new version? I will do rebuild for f35.
Build for 35: https://koji.fedoraproject.org/koji/taskinfo?taskID=78363856
Tested on three f34 machines. (Found a 3rd host!) All three no longer crash with the updated mate-screensaver-1.26.0-2 rpm. Unfortunately, I had already applied on two of them before I had the triggering procedure. But on the 3rd, the triggering procedure did indeed cause the crash, and that stopped after applying the new rpm. I will test the procedure on a couple of f35 hosts before applying the new f35 rpm, test it again, then report back here. This is looking very good so far.
Confirming — this triggering procedure: > $ cat ./mate-screensaver-test.sh > #!/usr/bin/bash > > set -x > sudo cp /usr/share/applications/mate-panel.desktop /usr/share/applications/TMPTMPTMP.desktop > sleep 3 > sudo rm /usr/share/applications/TMPTMPTMP.desktop > sleep 3 > mate-screensaver-command -a * causes the crash on f35; and * after applying the updated mate-screensaver-1.26.0-2.fc35.x86_64.rpm the crash no longer happens.
FEDORA-2021-20002cc727 has been submitted as an update to Fedora 34. https://bodhi.fedoraproject.org/updates/FEDORA-2021-20002cc727
FEDORA-2021-8834f85ef0 has been submitted as an update to Fedora 35. https://bodhi.fedoraproject.org/updates/FEDORA-2021-8834f85ef0
Tested mate-screensaver-1.26.0-2.fc35.x86_64.rpm on two F35 machines. Working properly as expected.
FEDORA-2021-20002cc727 has been pushed to the Fedora 34 testing repository. Soon you'll be able to install the update with the following command: `sudo dnf upgrade --enablerepo=updates-testing --advisory=FEDORA-2021-20002cc727` You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-2021-20002cc727 See also https://fedoraproject.org/wiki/QA:Updates_Testing for more information on how to test updates.
FEDORA-2021-8834f85ef0 has been pushed to the Fedora 35 testing repository. Soon you'll be able to install the update with the following command: `sudo dnf upgrade --enablerepo=updates-testing --advisory=FEDORA-2021-8834f85ef0` You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-2021-8834f85ef0 See also https://fedoraproject.org/wiki/QA:Updates_Testing for more information on how to test updates.
FEDORA-2021-8834f85ef0 has been pushed to the Fedora 35 stable repository. If problem still persists, please make note of it in this bug report.
FEDORA-2021-20002cc727 has been pushed to the Fedora 34 stable repository. If problem still persists, please make note of it in this bug report.