Bug 949070 - mate-power-manager doesn't turn off laptop panel or suspend on lid close
Summary: mate-power-manager doesn't turn off laptop panel or suspend on lid close
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Fedora
Classification: Fedora
Component: mate-power-manager
Version: 18
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: ---
Assignee: Dan Mashal
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2013-04-05 19:29 UTC by James Ralston
Modified: 2013-07-19 21:10 UTC (History)
4 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2013-04-27 03:18:24 UTC
Type: Bug
Embargoed:


Attachments (Terms of Use)
errors from X session (2.34 KB, text/plain)
2013-04-22 16:43 UTC, James Ralston
no flags Details

Description James Ralston 2013-04-05 19:29:04 UTC
mate-power-manager is mostly non-functional on my Fedora 18 laptop. I have it set to put the display to sleep after 10 minutes, to suspend when the lid is closed, and to reduce the backlight brightness when on battery power.

It correctly reduces the backlight when on battery power, but it never actually turns off the display, no matter how long I wait. Also, it does not suspend when I close the lid; to suspend, I specifically have to pick Shutdown -> Suspend from the main menu.

For various reasons, I run my laptop with systemd set to the multi-user target, not the graphical target, and I start the X by running "startx". I start mate-session via "exec ck-launch-session mate-session" in /etc/X11/xinit/Xclients.

Some of the comments on bug 888184 make me wonder if the reason why mate-power-manager seems to be mostly broken for me is that I start my session via startx instead of gdm/lightdm from the "graphical" systemd target.

I can live with suspending by picking Shutdown -> Suspend from the main menu. But the fact that mate-power-manager won't actually turn off the display is a big deal.

I see lots of errors from mate-power-manager, but I don't know which ones are relevant. So far in my current session, I see one of these:

** (mate-power-manager:25055): WARNING **: Failed to get brightness: GDBus.Error:org.freedesktop.DBus.Error.UnknownMethod: Method "GetBrightness" with signature "" on interface "org.freedesktop.UPower.KbdBacklight" doesn't exist

Two of these:

(mate-power-manager:25055): Gtk-WARNING **: Theme directory  of theme menta has no size field

Four of these:

(mate-power-manager:25055): Gdk-CRITICAL **: IA__gdk_window_get_root_coords: assertion `GDK_IS_WINDOW (window)' failed

And tons (29 and counting) of these:

** (mate-power-manager:25055): WARNING **: levels is 0!

Any ideas? Anything I can do to gather more information?

Version-Release number of selected component (if applicable):

0:kernel-3.8.5-201.fc18.x86_64
0:mate-power-manager-1.5.1-4.fc18.x86_64
0:mate-screensaver-1.5.2-1.fc18.x86_64
1:xorg-x11-drv-nouveau-1.0.6-4.fc18.x86_64

Comment 1 Dan Mashal 2013-04-12 06:06:00 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

Comment 2 cqi 2013-04-12 09:24:40 UTC
(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

Comment 3 Rex Dieter 2013-04-12 13:05:21 UTC
I'd recommend seeing if this is still reproducible if you do not use 'startx', but instead use gdm/kdm/lightdm or whatever.

Comment 4 Dan Mashal 2013-04-13 20:01:08 UTC
(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.

Comment 5 Dan Mashal 2013-04-21 16:28:16 UTC
I am opening an issue with upstream on this.

Comment 6 Dan Mashal 2013-04-21 16:48:07 UTC
Actually found a fix for this, tested and confirmed.

https://github.com/mate-desktop/mate-power-manager/pull/55

Building/pushing out shortly.

Comment 7 Fedora Update System 2013-04-21 16:59:24 UTC
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

Comment 8 Fedora Update System 2013-04-21 16:59:37 UTC
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

Comment 9 Fedora Update System 2013-04-21 18:44:34 UTC
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

Comment 10 Fedora Update System 2013-04-21 23:53:15 UTC
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).

Comment 11 James Ralston 2013-04-22 16:43:37 UTC
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?

Comment 12 Rex Dieter 2013-04-22 16:46:15 UTC
What does this say:

systemd-loginctl  list-sessions


for your startx session?

Comment 13 Rex Dieter 2013-04-22 16:51:11 UTC
See also bug #806491 for pitfalls related to startx + systemd-logind

Comment 14 Dan Mashal 2013-04-22 17:10:01 UTC
mate-power-manager-1.6 was not pushed to f18. Are you using official Fedora repos?

Comment 15 Dan Mashal 2013-04-22 18:31:36 UTC
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.

Comment 16 James Ralston 2013-04-23 15:16:11 UTC
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.

Comment 17 James Ralston 2013-04-23 23:52:09 UTC
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.

Comment 18 Fedora Update System 2013-04-27 03:18:26 UTC
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.

Comment 19 Dan Mashal 2013-04-27 03:21:05 UTC
(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.

Comment 20 Fedora Update System 2013-05-03 01:55:02 UTC
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.

Comment 21 James Ralston 2013-07-19 21:10:23 UTC
(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.


Note You need to log in before you can comment on or make changes to this bug.