Bug 949070
Summary: | mate-power-manager doesn't turn off laptop panel or suspend on lid close | ||||||
---|---|---|---|---|---|---|---|
Product: | [Fedora] Fedora | Reporter: | James Ralston <ralston> | ||||
Component: | mate-power-manager | Assignee: | Dan Mashal <dan.mashal> | ||||
Status: | CLOSED ERRATA | QA Contact: | Fedora Extras Quality Assurance <extras-qa> | ||||
Severity: | unspecified | Docs Contact: | |||||
Priority: | unspecified | ||||||
Version: | 18 | CC: | cqi, dan.mashal, rdieter, stefano | ||||
Target Milestone: | --- | ||||||
Target Release: | --- | ||||||
Hardware: | Unspecified | ||||||
OS: | Unspecified | ||||||
Whiteboard: | |||||||
Fixed In Version: | Doc Type: | Bug Fix | |||||
Doc Text: | Story Points: | --- | |||||
Clone Of: | Environment: | ||||||
Last Closed: | 2013-04-27 03:18:24 UTC | Type: | Bug | ||||
Regression: | --- | Mount Type: | --- | ||||
Documentation: | --- | CRM: | |||||
Verified Versions: | Category: | --- | |||||
oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |||||
Cloudforms Team: | --- | Target Upstream Version: | |||||
Embargoed: | |||||||
Attachments: |
|
Description
James Ralston
2013-04-05 19:29:04 UTC
Paste the output of the following commands: 1) 'rpm -qa |grep mate' 2) fpaste --sysinfo 3) output of .xsession_errors 4) Do you have any other DEs installed? 5) I see there are a few kernel updates and systemd updates sitting in updates-testing, mate-power-manager should support systemd inhibit. Thanks, Dan (In reply to comment #1) I'm running Fedora 17 now. > Paste the output of the following commands: > > 1) 'rpm -qa |grep mate' > mate-media-1.5.2-1.fc17.x86_64 libmatekbd-1.5.0-1.fc17.x86_64 mate-utils-1.5.0-1.fc17.x86_64 mate-image-viewer-1.5.0-2.fc17.x86_64 mate-panel-libs-1.5.6-1.fc17.x86_64 libmatewnck-1.5.1-1.fc17.x86_64 mate-file-manager-extensions-1.5.5-1.fc17.x86_64 libmatecomponentui-1.4.0-2.fc17.x86_64 mate-session-manager-1.5.1-1.fc17.x86_64 mate-file-manager-open-terminal-1.5.0-1.fc17.x86_64 mate-dialogs-1.5.0-1.fc17.x86_64 mate-settings-daemon-1.5.7-1.fc17.x86_64 mate-backgrounds-1.5.0-2.fc17.noarch mate-file-archiver-1.5.1-6.fc17.x86_64 libmatecomponent-1.4.0-14.fc17.x86_64 mate-file-manager-1.5.5-1.fc17.x86_64 mate-panel-1.5.6-1.fc17.x86_64 mate-themes-1.5.1-1.fc17.noarch libmateui-1.4.0-2.fc17.x86_64 mate-corba-1.4.1-1.fc17.x86_64 mate-vfs-1.4.0-14.fc17.x86_64 mate-netspeed-1.5.2-1.fc17.x86_64 mate-menus-libs-1.5.0-1.fc17.x86_64 mate-text-editor-1.5.0-1.fc17.x86_64 mate-system-log-1.5.0-1.fc17.x86_64 mate-conf-1.4.0-21.fc17.x86_64 libmate-1.4.0-17.fc17.x86_64 mate-icon-theme-1.5.1-1.fc17.noarch mate-window-manager-1.5.5-1.fc17.x86_64 mate-screensaver-1.5.2-1.fc17.x86_64 mate-power-manager-1.5.1-3.fc17.1.x86_64 mate-notification-daemon-1.5.1-1.fc17.x86_64 mate-polkit-1.5.0-1.fc17.x86_64 libmateweather-1.5.1-1.fc17.x86_64 mate-desktop-libs-1.5.8-1.fc17.x86_64 mate-keyring-1.5.1-1.fc17.x86_64 mate-terminal-1.5.1-1.fc17.x86_64 mate-mime-data-1.4.0-10.fc17.noarch mate-control-center-1.5.5-3.fc17.x86_64 mate-system-monitor-1.5.1-1.fc17.x86_64 libmatekeyring-1.5.1-1.fc17.x86_64 libmatecanvas-1.4.0-7.fc17.x86_64 mate-conf-editor-1.4.0-2.fc17.x86_64 mate-desktop-1.5.8-1.fc17.x86_64 mate-keyring-pam-1.5.1-1.fc17.x86_64 mate-calc-1.5.2-1.fc17.x86_64 mate-menus-1.5.0-1.fc17.x86_64 libmatenotify-1.5.0-1.fc17.x86_64 > 2) fpaste --sysinfo > http://paste.fedoraproject.org/7299/75843413/ > 3) output of .xsession_errors > No errors after closing lid and opening it again. > 4) Do you have any other DEs installed? > GNOME 3 is installed only. > 5) I see there are a few kernel updates and systemd updates sitting in > updates-testing, mate-power-manager should support systemd inhibit. > > Thanks, > Dan I'd recommend seeing if this is still reproducible if you do not use 'startx', but instead use gdm/kdm/lightdm or whatever. (In reply to comment #3) > I'd recommend seeing if this is still reproducible if you do not use > 'startx', but instead use gdm/kdm/lightdm or whatever. Works for me using lightdm but I still hit double suspend. I am opening an issue with upstream on this. Actually found a fix for this, tested and confirmed. https://github.com/mate-desktop/mate-power-manager/pull/55 Building/pushing out shortly. mate-power-manager-1.5.2-1.fc17 has been submitted as an update for Fedora 17. https://admin.fedoraproject.org/updates/mate-power-manager-1.5.2-1.fc17 mate-power-manager-1.5.2-1.fc18 has been submitted as an update for Fedora 18. https://admin.fedoraproject.org/updates/mate-power-manager-1.5.2-1.fc18 mate-power-manager-1.6.0-2.fc19 has been submitted as an update for Fedora 19. https://admin.fedoraproject.org/updates/mate-power-manager-1.6.0-2.fc19 Package mate-power-manager-1.5.2-1.fc17: * should fix your issue, * was pushed to the Fedora 17 testing repository, * should be available at your local mirror within two days. Update it with: # su -c 'yum update --enablerepo=updates-testing mate-power-manager-1.5.2-1.fc17' as soon as you are able to, then reboot. Please go to the following url: https://admin.fedoraproject.org/updates/FEDORA-2013-6212/mate-power-manager-1.5.2-1.fc17 then log in and leave karma (feedback). Created attachment 738578 [details]
errors from X session
mate-power-manager-1.6.0-2.fc18 doesn't change anything for me using startx(1) under F18: closing the lid doesn't trigger a suspend, and then screen is never turned off.
I am using startx because my laptop has wonky nVidia graphics, and gdm usually triggers a GPU lockup before I can even login. Maybe lightdm would be better, but I shouldn't have to use a dedicated display manager just to get proper functionality out of mate-power-manager; startx should be properly supported.
As of this morning, I'm up to date with respect to updates-testing:
0:imsettings-mate-1.5.1-2.fc18.x86_64
0:libmate-1.4.0-17.fc18.x86_64
0:libmatecanvas-1.4.0-7.fc18.x86_64
0:libmatecomponent-1.4.0-14.fc18.x86_64
0:libmatecomponentui-1.4.0-2.fc18.x86_64
0:libmatekbd-1.5.0-2.fc18.x86_64
0:libmatekeyring-1.5.1-1.fc18.x86_64
0:libmatenotify-1.5.0-1.fc18.x86_64
0:libmateui-1.4.0-2.fc18.x86_64
0:libmateweather-1.5.1-1.fc18.x86_64
0:libmatewnck-1.5.1-1.fc18.x86_64
0:mate-applets-1.5.1-5.fc18.x86_64
0:mate-backgrounds-1.5.0-2.fc18.noarch
0:mate-calc-1.5.2-1.fc18.x86_64
0:mate-conf-1.4.0-21.fc18.x86_64
0:mate-conf-editor-1.4.0-2.fc18.x86_64
0:mate-control-center-1.5.5-3.fc18.x86_64
0:mate-corba-1.4.1-1.fc18.x86_64
0:mate-desktop-1.5.8-1.fc18.x86_64
0:mate-desktop-libs-1.5.8-1.fc18.x86_64
0:mate-dialogs-1.5.0-2.fc18.x86_64
0:mate-file-archiver-1.5.1-6.fc18.x86_64
0:mate-file-manager-1.5.5-1.fc18.x86_64
0:mate-file-manager-extensions-1.5.5-1.fc18.x86_64
0:mate-file-manager-open-terminal-1.5.0-1.fc18.x86_64
0:mate-icon-theme-1.5.1-1.fc18.noarch
0:mate-image-viewer-1.5.0-2.fc18.x86_64
0:mate-keyring-1.5.1-2.fc18.x86_64
0:mate-keyring-pam-1.5.1-2.fc18.x86_64
0:mate-media-1.5.2-1.fc18.x86_64
0:mate-menus-1.5.0-1.fc18.x86_64
0:mate-menus-libs-1.5.0-1.fc18.x86_64
0:mate-mime-data-1.4.0-10.fc18.noarch
0:mate-netspeed-1.5.2-1.fc18.x86_64
0:mate-notification-daemon-1.5.1-1.fc18.x86_64
0:mate-panel-1.5.6-1.fc18.x86_64
0:mate-panel-libs-1.5.6-1.fc18.x86_64
0:mate-polkit-1.5.0-1.fc18.x86_64
0:mate-power-manager-1.5.2-1.fc18.x86_64
0:mate-screensaver-1.5.2-1.fc18.x86_64
0:mate-session-manager-1.5.1-1.fc18.x86_64
0:mate-settings-daemon-1.5.7-1.fc18.x86_64
0:mate-system-log-1.5.0-1.fc18.x86_64
0:mate-system-monitor-1.5.1-1.fc18.x86_64
0:mate-terminal-1.5.1-1.fc18.x86_64
0:mate-text-editor-1.5.0-1.fc18.x86_64
0:mate-themes-1.5.1-1.fc18.noarch
0:mate-utils-1.5.0-1.fc18.x86_64
0:mate-vfs-1.4.0-14.fc18.x86_64
0:mate-window-manager-1.5.5-1.fc18.x86_64
I also have GNOME and Sawfish installed. (I normally use sawfish as my WM under mate, but the results are the same if I use marco.)
fpaste seems to upload a *lot* of information. Is there something specific you're looking for?
What does this say: systemd-loginctl list-sessions for your startx session? See also bug #806491 for pitfalls related to startx + systemd-logind mate-power-manager-1.6 was not pushed to f18. Are you using official Fedora repos? After looking at your list of install RPMs more deeply you look pretty up to date. I haven't tested this on GDM. Please try with lightdm. I'm not sure if lightdm supports a gnome session though. Sorry; I copy-and-pasted the wrong value. The list of packages I generated in comment 11 is correect. $ systemd-loginctl list-sessions SESSION UID USER SEAT 7 1000 username seat0 1 sessions listed. I had been using ck-launch-session in /etc/sysconfig/desktop, but based on the discussion in bug #806491, I removed it. However, that didn't change mate-power-manager's behavior. I'll give lightdm a whirl to see if that works. Suspend-on-close, screen dimming, and panel power saving all work properly when I use lightdm instead of startx. So this seems to be an interaction with mate-power-manager and startx. mate-power-manager-1.6.0-2.fc19 has been pushed to the Fedora 19 stable repository. If problems still persist, please make note of it in this bug report. (In reply to comment #17) > Suspend-on-close, screen dimming, and panel power saving all work properly > when I use lightdm instead of startx. So this seems to be an interaction > with mate-power-manager and startx. lightdm has been patched to work with systemd. ConsoleKit is deprecated and will probably be retired in Fedora 19. As far as Fedora goes you are using an unsupported configuration. mate-power-manager-1.5.2-1.fc18 has been pushed to the Fedora 18 stable repository. If problems still persist, please make note of it in this bug report. (In reply to comment #19) > As far as Fedora goes you are using an unsupported configuration. One of the reasons why I continued to use startx instead of using a display manager is because I knew that not many people (and thus not many developers) would be testing those cases. But if we have reached the point where startx no longer works and is no longer supported, then it should be removed from Fedora. As it is now, it appears to work, but breaks in ways not necessarily attributable to using startx instead of a DM. In summary, either fix startx, or remove it. There is no benefit to anyone in leaving a known trap for people to accidentally fall into. |