mate-desktop / mate-power-manager Goto Github PK

i would like an option in power manager to lock the screen when the display is inactive. i dont use the screensaver as it gets activated when i use full screen applications (e.g. smplayer, vlc) and the available work arounds dont work for me (caffeine), so having an option in the power manager would be helpful.

We should support machines that have ambient light sensors, and use this as a means to automatically scale the system lighting in various light conditions.

Want to back this issue? Post a bounty on it! We accept bounties via Bountysource.

configure log:

configure:15954: result: yes
configure:15974: $PKG_CONFIG --exists --print-errors "gucharmap-2 >= $GUCHARMAP2_REQUIRED"
Package gucharmap-2 was not found in the pkg-config search path.
Perhaps you should add the directory containing `gucharmap-2.pc'
to the PKG_CONFIG_PATH environment variable
No package 'gucharmap-2' found
configure:15977: $? = 1
configure:16078: checking for GUCHARMAP
configure:16085: $PKG_CONFIG --exists --print-errors "gucharmap >= $GUCHARMAP_REQUIRED"
Package gucharmap was not found in the pkg-config search path.
Perhaps you should add the directory containing `gucharmap.pc'
to the PKG_CONFIG_PATH environment variable
No package 'gucharmap' found
configure:16088: $? = 1
configure:16102: $PKG_CONFIG --exists --print-errors "gucharmap >= $GUCHARMAP_REQUIRED"
Package gucharmap was not found in the pkg-config search path.
Perhaps you should add the directory containing `gucharmap.pc'
to the PKG_CONFIG_PATH environment variable
No package 'gucharmap' found
configure:16105: $? = 1
configure:16119: result: no
No package 'gucharmap' found
configure:16159: WARNING: *** 'charpick' applet will not be built with gucharmap support ***

in gucharmap-devel-3.10.1
/usr/lib/libgucharmap_2_90.so
/usr/lib/pkgconfig/gucharmap-2.90.pc
/usr/share/gir-1.0/Gucharmap-2.90.gir

I've set the power manager to ask me what to do when the power button is pressed. But no matter what I set to, when I press the power button, the system shuts down without popping the option dialog.

I had already posted this in the forums.

I run Linux Mint 15 MATE amd64 edition on Asus X55C laptop. Let me know if I can give you any system logs or more information.

Every time after starting MATE brightness is set to maximum value and I have to fix it manually. I guess there is a workaround to hard-code the desired value as default, but this issue should be fixed in my opinion.

Kernel: 3.10-2-686-pae i686 (32 bit) Desktop: MATE 1.6.0 Distro: Debian GNU/Linux jessie/sid
System: SAMSUNG product: 300E4A/300E5A/300E7A/3430EA/3530EA version: 0.1
Mobo: SAMSUNG model: 300E4A/300E5A/300E7A/3430EA/3530EA version: FAB1 Bios: Phoenix version: 09QA date: 11/02/2012
mate-power-manager package version: 1.6.1-1

Want to back this issue? Post a bounty on it! We accept bounties via Bountysource.

See also: https://bugzilla.redhat.com/show_bug.cgi?id=875415

A laptop system with fedora will "double suspend" when the lid is closed. This is because both MPM and systemed are responing to the lid close event, and sending a sleep event to the queue.

This can be solved using http://www.freedesktop.org/wiki/Software/systemd/inhibit (Thanks to rdieter for pointing this out). It would not be hard to add this dbus call into the startup of MPM, and to unlock the inhibitor on close.

This would appear to be the cleanest solution, as MPM would retain control of suspend if it is running, but users who opt out of MPM usage, will still have working suspend on systemd based systems.

I am happy to contribute the fixes to this if no one else is working on it - but I do have a few questions about the best way to go about it / the best place to insert the code etc.

I'm using a Thinkpad L530 with Linux Mint 14. After resuming from standby, my battery appears twice when clicking on the power-manager status symbol.

I have a Thinkpad T400 and X200.
Both are running Mate Desktop for quite a while now.

When i use the hotkeys (FN+F4) to go to standby,
-> the system goes to standby
-> the system wakes up by pushing a button
-> the system goes to standby right again

This issue can be solved, when selecting in mate-power-preferences

• When the suspend button is pressed "Do nothing".
  But unfortunately this option is not available.

Actually i choose "hibernate in that option.
Then my system goes to standby first and then it goes to hibernate.

My assumption is:

• there is another service running that monitors thinkpad hotkeys and makes my laptop go to standby. Then the laptop wakes up and mate-power-manager makes it go to standby again.

Suggestion:
Add an option "DO NOTHING" to WHEN SUSPEND BUTTON IS PRESSED in mate-power-preferences.

Sometimes when a right-click on the mate-power-manager applet I see two different batteries:


After booting the system I see only one battery (correct), but after a while (I'm not sure if it could be related to resuming the system, after putting it to sleep) it shows two.

It does this under the following OSes, Debian 7, Linux Mint 15, LMDE, they all do this. With MATE, when using XDM, or LightDM they do it. Pressing power button then restarting does not restart. it just crashes I have no idea why this is happening but it is continually happening and doesn't seem to have gotten fixed at all and just is getting worse as time goes on.

Also when pressing "shut down" then pressing "cancel" doesn't cancel it. It just shuts down anyway. It also when doing this shut down, it first off seems to go back to the default MATE theme, and then it kills itself. I don't know why that is happening but it keeps on happening.

I have seen the other fix that was filed for debian whenever that was done but that file is no longer there as acpi has been updated/upgraded since then.

there's some spelling error in 'patches' subdirectory

https://github.com/mate-desktop/mate-power-manager/tree/790fa5e0ea340ce4c826237e1c4626096c5d42bc/parches

also, imho dont-eat-the-logs.patch should be just applied to code itself, or at least made portable, as &>/dev/null is bash extension, not posix standard. so debian and friends will fail on that (afaik debian has dash as /bin/sh)

dbus_g apis should be rewritten to g_dbus apis, as these are "newer". There is a preliminary example of this in gpm-kbd-backlight.c

Want to back this issue? Post a bounty on it! We accept bounties via Bountysource.

consolekit checks in code prevent systemd-login1 to suspend on lid close.

Orginal fedora bug report:
https://bugzilla.redhat.com/show_bug.cgi?id=972881

BUG is in gpm-manager.c in several places like this:

static void
gpm_manager_button_pressed_cb (GpmButton *button, const gchar *type, GpmManager *manager)
{
gchar *message;
egg_debug ("Button press event type=%s", type);

    /* ConsoleKit says we are not on active console */
    if (!egg_console_kit_is_active (manager->priv->console)) {
            egg_debug ("ignoring as not on active console");
            return;
    }

In short, if systemd-login1 support is enabled, it needs to skip this ConsoleKit-specific check, and instead query
org.freedesktop.login1.Manager.CanSuspend
and friends for the capability.

I am trying to build the source but I get this error

make all-am
make[3]: Entering directory
`/home/david/bin/mate-desktop-mate-power-manager-252ecc3/src'
CC egg-color.o
CC egg-debug.o
CC egg-unique.o
egg-unique.c:26:27: fatal error: unique/unique.h: No such file or directory
compilation terminated.

The config returned this result

   MATE Power Manager 1.1.0
                   =============================

         prefix:                    /usr/local
         datadir:                   ${datarootdir}
         compiler:                  gcc
         cflags:                    -g -O2
         Building extra applets:    yes
         Self test support:         no
         MateConf default support:  yes
         Use libunique:             no
         Docbook support:           no
         documentation dir: ${datarootdir}/doc/mate-power-manager-1.1.0
         dbus-1 services dir:       ${datarootdir}/dbus-1/services
         mateconf-schema dir:       $(sysconfdir)/mateconf/schemas

so I assume the build conditions are met.

any ideas?

thanks

david

Right now it seems mate backlight helper can only handle backlight devices under /sys/class/backlight/ but that doesn't always work, for example my laptop (dell precision m4700) has an acpi0_video there but changing it's brightness value does nothing, while xbacklight works fine. Would be nice if mate supported also the methods used by xbacklight in addition to the other techniques (and allowed to prioritize them in some way), which as far as I see it's xrandr based so doesn't even require pkexec priviledge escalation to work.

I'm running Arch. Infirit on irc suggested that it has something to do with incomplete systemd version.

To reproduce:

1. Install mate on arch from the custom repo
2. Set display to never go black when inactive
3. Watch as your computer disregards your command

Some upower functions that mate-power-manager is using are now deprecated and will be removed in upower 1.0.

We need to manage them keeping support with old upower versions and on systems without systemd equivalents.

http://lists.freedesktop.org/archives/devkit-devel/2013-January/001339.html
http://cgit.freedesktop.org/upower/commit/libupower-glib/up-client.h?id=9843589

Hi, I'm using Mate on Arch Linux. I can't get mate-power-manager to turn off my screen or modify DPMS settings, apparently because it's still trying to use consoleKit. Here's my log of "mate-power-manager --verbose":
http://www.pastebin.ca/2465180
Especially notice lines like:

TI:08:23:40 TH:0x12c2630    FI:egg-console-kit.c    FN:egg_console_kit_init,301
 - Failed to get session for pid 1399: The name org.freedesktop.ConsoleKit was not provided by any .service files

and

 - Changing sleep-display-ac to 300
TI:08:23:43 TH:0x1354e30    FI:gpm-backlight.c  FN:gpm_settings_key_changed_cb,401
 - unknown key sleep-display-ac

After trying to change the settings, "xset -q" looks like this:

    03: Compose:     off    04: Kana:        off    05: Sleep:       off
    06: Suspend:     off    07: Mute:        off    08: Misc:        off
    09: Mail:        off    10: Charging:    off    11: Shift Lock:  off
    12: Group 2:     off    13: Mouse Keys:  off
  auto repeat delay:  500    repeat rate:  30
  auto repeating keys:  00ffffffdffffbbf
                        fadfffefffedffff
                        9fffffffffffffff
                        fff7ffffffffffff
  bell percent:  50    bell pitch:  400    bell duration:  100
Pointer Control:
  acceleration:  2/1    threshold:  4
Screen Saver:
  prefer blanking:  yes    allow exposures:  yes
  timeout:  0    cycle:  0
Colors:
  default colormap:  0x22    BlackPixel:  0x0    WhitePixel:  0xffffff
Font Path:
  /usr/share/fonts/misc/,/usr/share/fonts/TTF/,/usr/share/fonts/OTF/,/usr/share/fonts/Type1/,built-ins
DPMS (Energy Star):
  Standby: 0    Suspend: 0    Off: 0
  DPMS is Enabled
  Monitor is On

The old consoleKit dependancy was supposed to be fixed in this latest version (1.6.2-3) according to..
https://bugzilla.redhat.com/show_bug.cgi?id=994232 and
#72
...so I'm not too sure what's going on here.

The mate-screensaver does work correctly. Also "xset dpms 600 600 600" does turn off the screen after 10 minutes the way I want it to.

Thanks for the help!

At this time, the OSD for brightness, also is acting as the OSD for volume and eject actions. The latter two, are not part of the power manager, and this raises the point that the OSD is not just for power management actions.

As such, I would like to suggest that the OSD be seperated either into it's own section, or become part of notifcifications, as logically it makes more sense to place there. Comments and thoughts are welcome, and I am willing to carry out this work myself.

In FreeBSD, I am getting this noise about missing /sys/class/backlight and org.freedesktop.UPower.KbdBacklight. Not all users have keyboard backlight. It has been fixed in gnome-settings-daemon 3.1.92.

** (mate-power-backlight-helper:1093): WARNING **: failed to find any devices: E
rror opening directory '/sys/class/backlight': No such file or directory

** (mate-power-manager:1086): 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

GNOME Bugzilla: https://bugzilla.gnome.org/show_bug.cgi?id=658613
Patch: https://mail.gnome.org/archives/commits-list/2011-September/msg03549.html

The plugins/power/gsd-power-manager.c from gnome-settings-daemon looks like has been moved to https://github.com/mate-desktop/mate-power-manager/blob/master/src/gpm-kbd-backlight.c#L759 .

no-manual-page-for-binary mate-power-bugreport.sh
no-manual-page-for-binary mate-power-backlight-helper
Each executable in standard binary directories should have a man page.

Distro: Ubuntu 13.04/13.10 64-bit
Display driver: Radeon
UPower version: 0.9.22
mate-power-manager: 1.6.1-1

I have the power manager set to blank the screen for both AC and Battery when the lid is closed but even if I close it briefly, MATE still decides to suspend.

I have the power manager set to blank the screen for AC when the lid is closed but even if I close it briefly, MATE still decides to suspend (not related to the bugs #83 and #75). Mate installed on Ubuntu 13.10. Here is my upower and dconf dumps:

$ upower --dump
Device: /org/freedesktop/UPower/devices/line_power_AC
  native-path:          AC
  power supply:         yes
  updated:              Wed 05 Feb 2014 09:51:32 PM CET (4159 seconds ago)
  has history:          no
  has statistics:       no
  line-power
    online:             yes

Device: /org/freedesktop/UPower/devices/battery_BAT0
  native-path:          BAT0
  vendor:               Hewlett-Packard
  model:                Primary
  serial:               10059 2013/10/23
  power supply:         yes
  updated:              Wed 05 Feb 2014 11:00:37 PM CET (14 seconds ago)
  has history:          yes
  has statistics:       yes
  battery
    present:             yes
    rechargeable:        yes
    state:               fully-charged
    energy:              60.3396 Wh
    energy-empty:        0 Wh
    energy-full:         61.1721 Wh
    energy-full-design:  61.1721 Wh
    energy-rate:         0 W
    voltage:             12.771 V
    percentage:          98%
    capacity:            100%
    technology:          lithium-ion

Daemon:
  daemon-version:  0.9.22
  can-suspend:     yes
  can-hibernate:   no
  on-battery:      no
  on-low-battery:  no
  lid-is-closed:   no
  lid-is-present:  yes
  is-docked:       no

$ dconf dump /org/gnome/settings-daemon/plugins/power/
[/]
lid-close-battery-action='suspend'
lid-close-ac-action='nothing'
sleep-inactive-ac-timeout=0
sleep-inactive-battery-timeout=0

dmesg after lid closed:

[ 5153.441533] PM: Syncing filesystems ... done.
[ 5153.564527] PM: Preparing system for mem sleep
[ 5153.564890] Freezing user space processes ... (elapsed 0.001 seconds) done.
[ 5153.566526] Freezing remaining freezable tasks ... (elapsed 0.001 seconds) done.
[ 5153.567698] PM: Entering mem sleep
[ 5153.567709] Suspending console(s) (use no_console_suspend to debug)
[ 5153.567903] sd 0:0:0:0: [sda] Synchronizing SCSI cache
[ 5153.568114] sd 0:0:0:0: [sda] Stopping disk
[ 5153.726555] mei_me 0000:00:16.0: suspend
[ 5153.970063] snd_hda_intel 0000:00:1b.0: power state changed by ACPI to D3cold
[ 5154.205771] PM: suspend of devices complete after 638.136 msecs
[ 5154.205867] PM: late suspend of devices complete after 0.095 msecs
[ 5154.221842] ehci-pci 0000:00:1d.0: System wakeup enabled by ACPI
[ 5154.237866] ehci-pci 0000:00:1a.0: System wakeup enabled by ACPI
[ 5154.253712] e1000e 0000:00:19.0: System wakeup enabled by ACPI
[ 5154.285695] xhci_hcd 0000:00:14.0: System wakeup enabled by ACPI
[ 5154.301687] PM: noirq suspend of devices complete after 95.840 msecs
[ 5154.302285] ACPI: Preparing to enter system sleep state S3
[ 5154.325748] PM: Saving platform NVS memory
[ 5154.325769] Disabling non-boot CPUs ...
[ 5154.429644] smpboot: CPU 1 is now offline
[ 5154.533623] smpboot: CPU 2 is now offline
[ 5154.637616] smpboot: CPU 3 is now offline

When I am logged in into the default Ubuntu desktop, it works as expected (just blank screen), does not work when I am logged in the MATE

Orginal report at fedora bugzilla
https://bugzilla.redhat.com/show_bug.cgi?id=994232

Description of problem:
MATE Power Manager doesn't turn off the display despite elapsed timeout. The screensaver kicks in, but the display is never turned off.

Version-Release number of selected component (if applicable):
mate-power-manager-1.6.1-3.fc19.x86_64

How reproducible:
Always

Steps to Reproduce:

1. Set "Put display to sleep when inactive for" to 1 minute in Power Management Preferences, "On AC Power" tab.
2. Wait 1 minute without touching the keyboard or mouse.

Actual results:
Nothing happens.

Expected results:
Display should be turned off.

Additional info:
Similar symptom as in bug 949070, but I get this on both a desktop PC and a laptop.

$ grep -i dpms /var/log/Xorg.0.log
[ 3.607] Initializing built-in extension DPMS
3.754 RADEON(0): DPMS capabilities: StandBy Suspend Off
3.831 RADEON(0): DPMS enabled

xset dpms force off does turn the display off.

$ rpm -qa mate |sort
imsettings-mate-1.6.3-1.fc19.x86_64
libmatekbd-1.6.1-1.fc19.x86_64
libmatekeyring-1.6.0-1.fc19.x86_64
libmateweather-1.6.1-1.fc19.x86_64
libmatewnck-1.6.1-1.fc19.x86_64
mate-applets-1.6.1-4.fc19.x86_64
mate-backgrounds-1.6.0-1.fc19.noarch
mate-calc-1.6.0-1.fc19.x86_64
mate-character-map-1.6.0-4.fc19.x86_64
mate-control-center-1.6.0-2.fc19.x86_64
mate-desktop-1.6.1-8.fc19.x86_64
mate-desktop-libs-1.6.1-8.fc19.x86_64
mate-dialogs-1.6.0-1.fc19.x86_64
mate-document-viewer-1.6.0-6.fc19.x86_64
mate-document-viewer-data-1.6.0-6.fc19.noarch
mate-document-viewer-libs-1.6.0-6.fc19.x86_64
mate-file-archiver-1.6.0-2.fc19.x86_64
mate-file-manager-1.6.1-9.fc19.x86_64
mate-file-manager-extensions-1.6.1-9.fc19.x86_64
mate-file-manager-open-terminal-1.6.0-1.fc19.x86_64
mate-icon-theme-1.6.1-1.fc19.noarch
mate-image-viewer-1.6.0-1.fc19.x86_64
mate-keyring-1.6.0-2.fc19.x86_64
mate-keyring-pam-1.6.0-2.fc19.x86_64
mate-media-1.6.0-2.fc19.x86_64
mate-menus-1.6.0-4.fc19.x86_64
mate-menus-libs-1.6.0-4.fc19.x86_64
mate-netspeed-1.6.0-1.fc19.x86_64
mate-notification-daemon-1.6.0-2.fc19.x86_64
mate-panel-1.6.0-3.fc19.x86_64
mate-panel-libs-1.6.0-3.fc19.x86_64
mate-polkit-1.6.0-1.fc19.x86_64
mate-power-manager-1.6.1-3.fc19.x86_64
mate-screensaver-1.6.0-1.fc19.x86_64
mate-sensors-applet-1.6.0-3.fc19.x86_64
mate-session-manager-1.6.0-3.fc19.x86_64
mate-settings-daemon-1.6.1-2.fc19.x86_64
mate-system-log-1.6.0-5.fc19.x86_64
mate-system-monitor-1.6.0-1.fc19.x86_64
mate-terminal-1.6.1-9.fc19.x86_64
mate-text-editor-1.6.0-2.fc19.x86_64
mate-themes-1.6.1-2.fc19.noarch
mate-utils-1.6.0-5.fc19.x86_64
mate-window-manager-1.6.2-3.fc19.x86_64

$ cat .xsession-errors
** (mate-power-manager:1062): WARNING **: levels is 0!

I can confirm this issue on a installation without consolekit (f19)

Distro: Arch Linux 64-bit
Display driver: AMD Catalyst Legacy
UPower version: 0.9.22-1
mate-power-manager: 1.6.2-3

The Suspend and Hibernate options do not appear in the shutdown menu.
Closing the laptop lid produces this error message:
"Failed to suspend
Computer failed to suspend.
Failure was reported as: Cannot suspend"

Running "sudo pm-suspend" from the terminal correctly suspends the laptop and I was able to resume correctly.

https://bugzilla.gnome.org/show_bug.cgi?id=709114
https://bug709114.bugzilla-attachments.gnome.org/attachment.cgi?id=256549

incorrect-fsf-address in COPYING and others

I have a laptop running Mint 13 and verified this with 14-rc too.

I have it hooked up to an external display and have no use for the laptop being open, so i just close the lid. When I do that, the monitor goes blank. The power manager does not have an option for doing nothing when the lid is closed. The options are "Blank Screen", "Suspend", and "Shutdown".

I tried messing around with mateconf-editor > apps > mate-power-manager > buttons and setting the
lid keys to "nothing" but still no results...

Is there a way to make the monitor not go to a blank screen when the lid is closed? The only way I found is to turn the laptop screen Off (in "Monitor Preferences") every time I plug the monitor and then On again when unplugged...

Hi there!
It seems there is a bug on gsd-backlight-helper (formerly gnome-power-backlight-helper) which MATE has inherited.
The bug is described here, and causes the program to select an arbitrary file under /sys/class/backlight, giving the user no way to select which one to use.
On some laptops with hybrid graphics proccessor, this results on non-working backlight controls on the DE, or incorrect stepping controlling backlight.

Could be possible to force mate-power-backlight-helper to use a file defined somewhere (maybe dconf)?

I'm personally affected by this bug, and it's quite annoying being forced to set an alternate shortcut with a custom script to change the backlight on the correct card.

Best regards.

original report at fedora bugzilla.
https://bugzilla.redhat.com/show_bug.cgi?id=965633

Description of problem:
When trying to change brightness from mate-panel, clicking on any level or '+'/'-' buttons will just collapse the menu without setting the brightness level.

Version-Release number of selected component (if applicable):
mate-applets-1.6.1-1.fc19.x86_64

How reproducible:
Always

Steps to Reproduce:

1. Right click on panel -> Add to Panel
2. Brightness Applet -> Add
3. Click on Brightness -> try to change brightness level

Actual results:
Brightness does not change

Expected results:
Brightness is changed

Additional info:
Scrolling up&down on the brightness icon -> adjusting brightness takes a lot of time (not immediate reaction)

Note: That here inhibitors mean mate-power-manager inhibiors, not systemd ones.

System power state (Ie Hibernate, Suspend, Power off etc) Is managed by each module. This means that certain things are handled inconsistently. For example, gpm-idle.c uses it's own "gpm_idle_set_mode", after doing idle checks, and inhibitor checks in gpm_idle_evaluate. This can cause a race condition, where the screen becomes idle, inhibitors are evaluated then the callback setup. Say now someone logs (ssh) into the machine, and starts a background job that should be inhibited, this will not be as the call back will fire without an inhibit check.

gpm-control.c also has it's own suspend function, that appears to make no inhibitor check, but it does make policy kit checks.

Finally gpm-session.c has it's own suspend routine, that makes the inhibitor checks etc.

What I propose is that this code be refactored, into some gpm (or mpm) mpm-system-state.c, which manages the suspend, hibernate, power off routines etc. Then each needed action, such as idle, session, control etc, makes calls into this. They provides a consistent user experience of power actions, and provides protections to users doing actions that provide inhibitors. It simplifies the addition or manipulation of modules such as Idle, etc, as a good deal of their code will be factor out to a single location.

Finally, this will make integration with external tools like systemd-login api's, or other api's trivially simple, as now suspend hooks need to be managed in a single location in code, rather than "spaghettied" throughout our codebase.

The user should be able to configure the keyboard backlight controls from the settings ui. This includes dimming when idle, and reducing power on battery etc.

Want to back this issue? Post a bounty on it! We accept bounties via Bountysource.

I have recently installed Linux Mint 13 MATE on my Acer Aspire One d250 . Whenever i close the lid of the netbook and re-open it the netbook freezes(or atleast the screen) : the screen stays black but i guess the netbook is still active. When i start mouseclicking or pressing enter, the display flashes to the point i left it before the lid close.The problem occurs whenatever power management action for closing lid i chose ( blank screen/suspend), but suspend is working fine if i launch it manually. If i press power button i can see in the flash, that the choose option window of the power button is there, but the screen flashes black after one second. I checked the state of the lid , while using it and it said state : closed, when the lid was open. I also wrote the same command while the screen was frozen, and in the mere flash i was able to read that the status was also closed. I am new Linux user so if any solution is found, please send me feedback in a newbish, understandable manner .
Best regards.

EDIT : forgot to mention , that once i closed the lid and reopened it, all i could do is hard reboot the netbook, and every once in a while when i reboot it i get this message in a black conzole just before the reboot : cannot write bytes : Broken pipe . Like 15 rows of it.

When the option to reduce the backlight brightness is set, the brightness is properly reduced when the keyboard/mouse goes idle. However, when the system exits the idle state, the backlight brightness is not restored to what it was before the system went idle.

Steps to reproduce:

1. Enable backlight dimming when the system is idle.
2. Increase brightness to 100%.
3. Let system go idle.
4. Move the mouse/type something. The brightness is not restored.

We are currently adding temporary support to inhibit systemd from managing power actions.

In the future, power actions on a system that posses systemd should use the login api, instead of managing these ourselves.

This feature is not suggesting exclusion of non systemd based distros - Merely that if systemd is avaliable, we should use its functions. If it's not there, we use the current power management actions and code.

Again, I'm happy to do this work myself, but comments and such are welcome.

I would like to request a feature (mainly useful for laptops) to enable/disable power management. This is mainly useful for people with laptops attached to a docking stating where sometimes we don't want the default behavior and just want it disabled.

This option should be user controlled (maybe applet?) and not automatic.

bug forwarded from https://bugzilla.redhat.com/show_bug.cgi?id=868538

Accessed screensaver from System - Preferences
Pressed power management button.
Changed time for powering down monitor from 1 to 30 minutes. Computer sleep time is set to never.
Pressed default button. This is where program crashed. Was not prompted for root password.
Reopened power management and found that settings are saved for me.

backtrace_rating: 4
Package: mate-power-manager-1.4.0-0100.fc17
Architecture: i686
OS Release: Fedora release 17 (Beefy Miracle)

Hi,

I would like to propose renaming mate-power-bugreport.sh to mate-power-manager-bugreport.

Reasons:

(1) Debian's lintian complains about file extensions (.sh). So for Debian, we have to rename the file anyway.

(2) When using bash auto completion (I use mate-power-manager in i3 desktop environment and evoke it via a terminal), mate-power-bugreport.sh always gets suggested first (before mate-power-manager).

(3) For the Debian package mate-power-manager, I will maintain the renaming until something happens with its name upstream (or forever if nothing happens to its name).

Greets,
Mike

I set the power button to enter my laptop into suspend mode. However, after wake the system is immediately shut down.

Kernel: 3.10-2-686-pae i686 (32 bit) Desktop: MATE 1.6.0 Distro: Debian GNU/Linux jessie/sid
System: SAMSUNG product: 300E4A/300E5A/300E7A/3430EA/3530EA version: 0.1
Mobo: SAMSUNG model: 300E4A/300E5A/300E7A/3430EA/3530EA version: FAB1 Bios: Phoenix version: 09QA date: 11/02/2012
mate-power-manager package version: 1.6.1-1

When I wake up my Computer from suspend to ram it immediately locks the screen and goes back to suspend to ram. When I wake it up again, everything works fine.
This issue only appears when I advise the screensaver to lock the screen. When I disable this option everything works fine.

Edit:
This issue also appears if I set the following values in mateconf-editor:
/apps/mate-power-manager/lock/use_screensaver_settings false
/apps/mate-power-manager/lock/suspend true

When I set value /apps/mate-power-manager/lock/suspend to false (and use_screensaver_settings to false) everything goes fine but the screen is not locked after wakeup.

The shutdown dialog box is actually displayed, but with zero timeout instead of the default 60s, so the laptop is shut down immediately.

OS: Linux Mint 13
Computer: HP EliteBook 8740W

When laptop is powered up after Suspend, the screen is not locked and no password is needed.

OS: Linux MInt 13
Computer: HP EliteBook 8740W

I have a problem building mate-power-manager. it is not finding G_CONST_RETURN, which is deprecated define from GLIB.
https://mail.gnome.org/archives/commits-list/2011-June/msg03847.html

I think the problem is that fedora16 has a old version of libunique, missing this patch
http://git.gnome.org/browse/unique/commit/?id=03526f8d95910c207170391c1b6594905a71e4e9
so maybe this is not really Mate's fault

The makefile in src/ has-DG_DISABLE_DEPRECATED from somewhere. so maybe getting rid of that is the answer

                 from /usr/include/unique-1.0/unique/unique.h:24,
                 from egg-unique.c:26:
/usr/include/unique-1.0/unique/uniquemessage.h:51:1: error: unknown type name ‘G_CONST_RETURN’
/usr/include/unique-1.0/unique/uniquemessage.h:51:23: error: expected ‘=’, ‘,’, ‘;’, ‘asm’ or ‘__attribute__’ before ‘*’ token
/usr/include/unique-1.0/unique/uniquemessage.h:66:1: error: unknown type name ‘G_CONST_RETURN’
/usr/include/unique-1.0/unique/uniquemessage.h:66:22: error: expected ‘=’, ‘,’, ‘;’, ‘asm’ or ‘__attribute__’ before ‘*’ token
In file included from /usr/include/unique-1.0/unique/unique.h:25:0,
                 from egg-unique.c:26:
/usr/include/unique-1.0/unique/uniquebackend.h:97:1: error: unknown type name ‘G_CONST_RETURN’
/usr/include/unique-1.0/unique/uniquebackend.h:97:22: error: expected ‘=’, ‘,’, ‘;’, ‘asm’ or ‘__attribute__’ before ‘*’ token
/usr/include/unique-1.0/unique/uniquebackend.h:100:1: error: unknown type name ‘G_CONST_RETURN’
/usr/include/unique-1.0/unique/uniquebackend.h:100:22: error: expected ‘=’, ‘,’, ‘;’, ‘asm’ or ‘__attribute__’ before ‘*’ token
make[3]: *** [egg-unique.o] Error 1
make[3]: *** Waiting for unfinished jobs....
make[3]: Leaving directory`/var/tmp/mate/mate-power-manager/src'
make[2]: **\* [all] Error 2
make[2]: Leaving directory `/var/tmp/mate/mate-power-manager/src'
make[1]: *** [all-recursive] Error 1
make[1]: Leaving directory`/var/tmp/mate/mate-power-manager'
make: **\* [all] Error 2

```
```

Occasionally, the battery indicator applet in the mate panel reports a wrong battery level and issues a subsequent warning as it's under the wrong impression that the battery has reached y critical level below "low" whereas in fact the battery is still 77%.

I tracked this down to a g_object_get invocation in the function gpm_engine_get_warning_percentage (file gpm-engine.c) that yields the wrong value compared to a direct acpi invocation from the command line, but this issue (GObject invocation delivering the wrong results) may come up elsewhere in the code. Unfortunately, this issue is not reproducible based on certain conditions but happens randomly about 15% of the time.

What I've also noticed: with the same probability (and non-determinism :-( ), the battery panel applet reports TWO batteries where there should only be one.

Both issues first observed on a MacBook Pro 13" (issued early 2012). System is a Precise stock environment with mate installed from the the Mate repos (64 bit). Let me know if you need more details.

distribution : debian jessie (3.12-1.486 #1 (2014-02-01)
mate-desktop version : 1.8.0
system = sony vgn-p11z ultrabook

The brightness +/- keys doesn't work anymore, and the slider in mate-power-preferences doesn't change the brightness, no matter what value it is set.

Want to back this issue? Post a bounty on it! We accept bounties via Bountysource.

I: mate-power-manager: desktop-entry-lacks-keywords-entry usr/share/applications/mate-power-preferences.desktop
N:
N: This .desktop file does either not contain a "Keywords" entry or it does
N: not contain any keywords not already present in the "Name" or
N: "GenericName" entries.
N:
N: .desktop files are organized in key/value pairs (similar to .ini files).
N: "Keywords" is the name of the entry/key in the .desktop file containing
N: keywords relevant for this .desktop file.
N:
N: The desktop-file-validate tool in the desktop-file-utils package is
N: useful for checking the syntax of desktop entries.
N:
N: Refer to
N: http://standards.freedesktop.org/desktop-entry-spec/latest/ar01s05.html,
N: http://bugs.debian.org/693918, and
N: https://wiki.gnome.org/Initiatives/GnomeGoals/DesktopFileKeywords for
N: details.
N:
N: Severity: wishlist, Certainty: certain
N:
N: Check: menu-format, Type: binary
N:

I: mate-power-manager: hyphen-used-as-minus-sign usr/share/man/man1/mate-power-manager.1.gz:28
N:
N: This manual page seems to contain a hyphen where a minus sign was
N: intended. By default, "-" chars are interpreted as hyphens (U+2010) by
N: groff, not as minus signs (U+002D). Since options to programs use minus
N: signs (U+002D), this means for example in UTF-8 locales that you cannot
N: cut and paste options, nor search for them easily. The Debian groff
N: package currently forces "-" to be interpreted as a minus sign due to
N: the number of manual pages with this problem, but this is a
N: Debian-specific modification and hopefully eventually can be removed.
N:
N: "-" must be escaped ("-") to be interpreted as minus. If you really
N: intend a hyphen (normally you don't), write it as "(hy" to emphasise
N: that fact. See groff(7) and especially groff_char(7) for details, and
N: also the thread starting with
N: http://lists.debian.org/debian-devel/2003/debian-devel-200303/msg01481.html
N:
N: If you use some tool that converts your documentation to groff format,
N: this tag may indicate a bug in the tool. Some tools convert dashes of
N: any kind to hyphens. The safe way of converting dashes is to convert
N: them to "-".
N:
N: Because this error can occur very often, Lintian shows only the first 10
N: occurrences for each man page and give the number of suppressed
N: occurrences. If you want to see all warnings, run Lintian with the
N: -d/--debug option.
N:
N: Refer to /usr/share/doc/groff-base/README.Debian and the groff_char(7)
N: manual page for details.
N:
N: Severity: wishlist, Certainty: possible
N:
N: Check: manpages, Type: binary
N:
I: mate-power-manager: hyphen-used-as-minus-sign usr/share/man/man1/mate-power-manager.1.gz:31
I: mate-power-manager: hyphen-used-as-minus-sign usr/share/man/man1/mate-power-manager.1.gz:34
I: mate-power-manager: hyphen-used-as-minus-sign usr/share/man/man1/mate-power-manager.1.gz:37
I: mate-power-manager: hyphen-used-as-minus-sign usr/share/man/man1/mate-power-preferences.1.gz:26
I: mate-power-manager: hyphen-used-as-minus-sign usr/share/man/man1/mate-power-preferences.1.gz:29
I: mate-power-manager: hyphen-used-as-minus-sign usr/share/man/man1/mate-power-statistics.1.gz:28
I: mate-power-manager: hyphen-used-as-minus-sign usr/share/man/man1/mate-power-statistics.1.gz:31

Hello, I have a problem to install the applet, the error occurs when I run the ./autogen on the root folder.

configure.ac:156: error: possibly undefined macro: AM_MATECONF_SOURCE_2
If this token and others are legitimate, please use m4_pattern_allow.
See the Autoconf documentation.

I am using Linux Mint 12 with mate obviously.

A similar error occurs when I try to install the mate-applets package.

Even on AC power MATE Power Manager 1.6.2 uses settings in battery section for lid closing.