Created attachment 1333527 [details] package_list.txt Description of problem: see steps below Version-Release number of selected component (if applicable): $ rpm -qa | grep mate mate-power-manager-1.18.0-2.fc26.x86_64 f26-backgrounds-extras-mate-26.2.7-2.fc26.noarch mate-desktop-1.18.0-5.fc26.x86_64 mate-control-center-filesystem-1.18.2-2.fc26.x86_64 mate-session-manager-1.18.1-1.fc26.x86_64 mate-terminal-1.18.1-1.fc26.x86_64 libmatekbd-1.18.2-1.fc26.x86_64 mate-system-log-1.18.2-1.fc26.x86_64 mate-menus-preferences-category-menu-1.18.0-1.fc26.x86_64 mate-settings-daemon-1.18.1-2.fc26.x86_64 f26-backgrounds-animated-26.2.7-2.fc26.noarch mate-system-monitor-1.18.0-1.fc26.x86_64 mate-themes-3.22.13-1.fc26.noarch libmateweather-data-1.18.1-1.fc26.noarch mate-calc-1.18.0-1.fc26.x86_64 mate-media-1.18.1-2.fc26.x86_64 mate-notification-daemon-1.18.0-1.fc26.x86_64 mate-menus-libs-1.18.0-1.fc26.x86_64 mate-applets-1.18.1-1.fc26.x86_64 mate-disk-usage-analyzer-1.18.2-1.fc26.x86_64 mate-control-center-1.18.2-2.fc26.x86_64 mate-icon-theme-faenza-1.18.1-1.fc26.noarch mate-dictionary-1.18.2-1.fc26.x86_64 mate-menus-1.18.0-1.fc26.x86_64 mate-applet-softupd-0.4.6-1.fc26.x86_64 mate-desktop-libs-1.18.0-5.fc26.x86_64 mate-sensors-applet-1.18.2-2.fc26.x86_64 mate-utils-common-1.18.2-1.fc26.noarch mate-panel-1.18.4-1.fc26.x86_64 mate-user-guide-1.18.0-1.fc26.noarch mate-menu-17.10.1-1.fc26.noarch libmateweather-1.18.1-1.fc26.x86_64 mate-search-tool-1.18.2-1.fc26.x86_64 libmatemixer-1.18.0-1.fc26.x86_64 mate-backgrounds-1.18.0-1.fc26.noarch f26-backgrounds-mate-26.2.7-2.fc26.noarch mate-polkit-1.18.1-1.fc26.x86_64 mate-screensaver-1.18.1-2.fc26.x86_64 mate-icon-theme-1.18.2-1.fc26.noarch mate-panel-libs-1.18.4-1.fc26.x86_64 mate-utils-1.18.2-1.fc26.x86_64 mate-screenshot-1.18.2-1.fc26.x86_64 How reproducible: in last days always Steps to Reproduce: 1. undock 2. suspend (I do that a power button) 3. weakup - login screen appears 4. dock Actual results: the desktop is unlocked Expected results: entering the password should be still required Additional info: complete package listing in attachment
Created attachment 1333785 [details] dmesg Each docking crashes the screen saver while USBs are initiated.
After the frist dock the mate-screensaver is obviously not running. After another undock and dock (without suspending) the screensaver is run again by systemd.
Sorry, i do not have any hardware to reproduce it. Maybe Redhat can sponsor me one.....lol
(In reply to Dalibor Pospíšil from comment #2) > After the frist dock the mate-screensaver is obviously not running. After > another undock and dock (without suspending) the screensaver is run again by > systemd. Can you report it upstream please https://github.com/mate-desktop/mate-screensaver/issues Also providing a gdb backtrace would improve the chances of the issue getting fixed.
(In reply to Wolfgang Ulbrich from comment #3) > Maybe Redhat can sponsor me one.....lol Hell will probably freeze first before that happens :-)
I've updated the system yesterday and today it did not crash. I will observe it for a while but it looks like some integration issue with other component so far. From the list of updated packages, kernel and dbus look suspicious.
(In reply to leigh scott from comment #5) > (In reply to Wolfgang Ulbrich from comment #3) > > > Maybe Redhat can sponsor me one.....lol > > Hell will probably freeze first before that happens :-) You might let your self hired by RedHat, then you'll get more. ;-)
This message is a reminder that Fedora 26 is nearing its end of life. Approximately 4 (four) weeks from now Fedora will stop maintaining and issuing updates for Fedora 26. It is Fedora's policy to close all bug reports from releases that are no longer maintained. At that time this bug will be closed as EOL if it remains open with a Fedora 'version' of '26'. Package Maintainer: If you wish for this bug to remain open because you plan to fix it in a currently maintained version, simply change the 'version' to a later Fedora version. Thank you for reporting this issue and we are sorry that we were not able to fix it before Fedora 26 is end of life. If you would still like to see this bug fixed and are able to reproduce it against a later version of Fedora, you are encouraged change the 'version' to a later Fedora version prior this bug is closed as described in the policy above. Although we aim to fix as many bugs as possible during every release's lifetime, sometimes those efforts are overtaken by events. Often a more recent Fedora release includes newer upstream software that fixes bugs or makes them obsolete.
Fedora 26 changed to end-of-life (EOL) status on 2018-05-29. Fedora 26 is no longer maintained, which means that it will not receive any further security or bug fix updates. As a result we are closing this bug. If you can reproduce this bug against a currently maintained version of Fedora please feel free to reopen this bug against that version. If you are unable to reopen this bug, please file a new report against the current release. If you experience problems, please add a comment to this bug. Thank you for reporting this bug and we are sorry it could not be fixed.