You are not logged in.
Still working so marked as SOLVED.
I get bash: mate-power-manager: command not found
If I put sudo in front I get: sudo: mate-power-manager: command not found
It doesn't help if I put in mate-power-manager-common either.
EDIT:
I also tried to reinstall it in hopes the same error message would pop up again, but it did not.
I had forgotten about this little problem I have but was reminded of it through a different problem (which is now solved, I hope). I am posting it here as it is a separate problem (I think so, at least).
As the subject line states, I have no access to the power manager. It usually should be in the Mate Control center, but it's not. I have upower installed. I thought maybe if I installed mate-power-manager-common then the power manager link would show up in the control center, but it did not. Another thing is after installing this, an error message popped up which unfortunately I did not write down. But it is installed according to Synaptic, along with upower.
Is there a way to check which one is running? Or if any? Thanks.
Thanks Rolfie for the suggestion to search askUbuntu. I found something there that seems to be working:
[Disable suspend (upower)]
Identity=unix-user:*
Action=org.freedesktop.upower.suspend
ResultActive=no
ResultInactive=no
ResultAny=no
[Disable suspend (logind)]
Identity=unix-user:*
Action=org.freedesktop.login1.suspend
ResultActive=no
ResultInactive=no
ResultAny=no
[Disable suspend when others are logged in (logind)]
Identity=unix-user:*
Action=org.freedesktop.login1.suspend-multiple-sessions
ResultActive=no
ResultInactive=no
ResultAny=noI put this where you suggested (/etc/polkit-1/localauthority/50-local.d) with your file name (enable-shutdown-reboot.pkla), and it seems to be working, even without a reboot. I will continue to monitor this throughout the day (with multiple reboots) and report back.
EDIT:
Didn't notice at first that this only dropped suspend from the shut down menu. So I went back and made this file look like this and that also removed hibernate:
[Disable suspend (upower)]
Identity=unix-user:*
Action=org.freedesktop.upower.suspend
ResultActive=no
ResultInactive=no
ResultAny=no
[Disable suspend (logind)]
Identity=unix-user:*
Action=org.freedesktop.login1.suspend
ResultActive=no
ResultInactive=no
ResultAny=no
[Disable suspend when others are logged in (logind)]
Identity=unix-user:*
Action=org.freedesktop.login1.suspend-multiple-sessions
ResultActive=no
ResultInactive=no
ResultAny=no
[Disable hibernate (upower)]
Identity=unix-user:*
Action=org.freedesktop.upower.hibernate
ResultActive=no
ResultInactive=no
ResultAny=no
[Disable hibernate (logind)]
Identity=unix-user:*
Action=org.freedesktop.login1.hibernate
ResultActive=no
ResultInactive=no
ResultAny=no
[Disable hibernate when others are logged in (logind)]
Identity=unix-user:*
Action=org.freedesktop.login1.hibernate-multiple-sessions
ResultActive=no
ResultInactive=no
ResultAny=noI don't have a policykit-1 folder in /etc . . . but I do have a PolicyKit and a polkit-1 folder.
Also I'm not understanding something. In that other thread you stated you did not enable suspend or hibernate. That's what I want, so why would I use the opposite settings?
have a look at: https://dev1galaxy.org/viewtopic.php?id=2023, I think it will give you some interesting insight.
Read that thread and followed GNUser's advice in installing lightdm and libpolkit-backend-1-0-elogind and libpolkit-gobject-1-0-elogind. I'm still getting suspend and hibernate in the shut down menu. Did I forget to do something else?
BTW, last night I removed hibernate & uswsusp as MiyoLinux wrote. Then I looked up upower in Synaptic to see what would happen if I deleted that also. It would have removed the Mate desktop as well! That doesn't seem right. And I still had suspend and hibernate in the shut down menu.
Also, this reminded me of another thing. In the Mate control center, I don't have any link to Power Management. I downloaded the mate-power-manager-common app, but still no dice. I do remember after installing it some kind of error message popped up which unfortunately I didn't write down.
I have a feeling that all of this is somehow related. Anyone have any advice?
So I went ahead and edited this file. I still get suspend in the shut down menu, and sometimes hibernate. So this "fix" isn't really a fix at all. Is there any other way?
P.S. I always got suspend, and sometimes hibernate even before I edited this file. Why would I sometimes get hibernate, and sometimes not? Also, when I was running Jessie, neither one appeared on the shut down menu.
I searched online how to get rid of the Suspend and Hibernate options from the shut down menu, and found the following instructions:
There are two sections in this file:
/usr/share/polkit-1/actions/org.freedesktop.upower.policy
the first for suspend and the second for hibernate.
Near the end of each section will be a line with:
<allow_active>yes</allow_active>
It should be changed from “yes” to “no” to disable hibernate/suspend.Can someone here verify if this is a correct way to do this? Or, if there is a more correct way to do it?
Note that GRUB will look for /boot/grub/grub.cfg on the partition from which you run the grub-install command (i.e., if you run grub-install from your ASCII partition, GRUB will look for /boot/grub/grub.cfg in /dev/sda6)
Thanks for all the info GNUser. My system uses the MBR partition table (thanks for showing me how to check). Here's what happened, I believe. The last OS I installed was ASCII. Now when I deleted Jessie, that caused my ASCII partition, which had been sda6 up to that point, to switch to being sda5 (I wasn't expecting that). So based on what you wrote above (I believe) GRUB was looking for /boot/grub/grub.cfg in /dev/sda6, which then no longer existed. Does that sound plausible to you?
Also, what makes putting GRUB on its own partition a bad idea? I'm just wondering because that is an option when installing the OS.
Once again, thanks for the help.
A little background: I was tripled-booting Mint, Jessie & ASCII (Miyo). Jessie was on sda5 and ASCII on sda6. Since ASCII runs so well, I decided to delete my Jessie partition and integrate it into my ASCII partition. So I did that (while booted in Mint), but it messed up the grub loader, which I fixed by reinstalling ASCII (I know, that was drastic).
Question: If I had installed grub on its own partition, would that have prevented grub from getting messed up? Also, how big should the separate grub partition be? Thanks!
I just wanted to post this as a follow up: ASCII runs so great, that I've deleted Jessie and am running ASCII full-time.
Thanks MiyoLinux. I already had the "ugly" installed but I needed the "bad." So it's now working. If you can remember how you found out it needed both these plugins, I'd appreciate knowing. I searched last night and came up empty. I did look at the dependencies listed in Synaptic, and I had them all. But gstreamer1.0-plugins-bad wasn't listed in Synaptic. Why would that be? It lists gstreamer1.0-plugins-base & gstreamer1.0-plugins-good. (Is there a gstreamer package that includes all this stuff so a user wouldn't have to download a bunch of different ones?
Thanks again.
My first contribution to this thread. 80s rock had both hard-charging guitars and great melodies.
Yes, that's it. It doesn't work on my system, on either Jessie or ASCII.
Palemoon is still winning, barely. But it can't do mhtml or view pdfs like Chromium can.
You could add the extension Moon PDF Viewer for PDF viewing.
There's a small app I used to use on Mint, called Alarm Clock. I've tried it on Devaun (Miyo) but it doesn't work right (on both Jessie and ASCII). I use it for its timer function. You set it for say, 5 or 10 minutes, and then when it reaches "0" it plays a sound file of your choosing. It's pretty handy if you have something on the stove-top you don't want to forget. Can anyone suggest to me something else like this that works on Devuan? Or even better, how to get Alarm Clock working on Devuan?
I've been playing around with Ascii all day, installing all the apps I use and testing things. I have to say that Ascii runs just as good on my computer as Jessie does. And it looks better too. Good work. How close is Ascii to being considered a stable version? To me it seems like it already is. ![]()
Never mind about the login sound. I found out how to fix it. I just changed paplay to aplay.
Lucky guess!
Hey...if you decide you'd like to switch back to LightDM for any reason, let me know, and I'll tell you how to make your name show so that all you need to do is fill in your password in LightDM.
LightDM looks better to me, so I would appreciated the instructions.
Also, there is another very minor issue I come across. I like to have a startup sound, and this is what I did to get one in Jessie (I got this from my Mint days):
Enable login sound on Mate:
Go to Startup Applications and click "Add." Fill in the following:
Name: GNOME Login Sound
Command: paplay /usr/share/sounds/stereo/xxxx.ogg
Comment: Plays a sound whenever you log in
To test sound in terminal, run:
paplay /usr/share/sounds/stereo/xxxx.oggBut this doesn't work in Ascii. I did some research and it seems the reason is because PulseAudio isn't installed in Ascii. So is there a way to get a login sound without installing PulseAudio? Thanks.
I saw another post about opening a file as administrator in Mate's file manager, but it's gone now? If you already solved it, great going!
I removed the post because I figured it out. I compared the caja packages I had installed between Jessis and Ascii, and installed the ones I had in Jessie but was missing in Ascii. That gave me the "open as administrator" option back. Thank you for your help.
So, now Ascii appears to be running just fine on my system. If I have anymore problems I will post here again. By the way, I switched back to slim. Both slim and lightdm worked fine as long as I have haveged installed. (Thanks once again to GNUser.)
Adding haveged as GNUser suggested seems to have fixed the problem (thanks GNUser!). Is this installed by default on Jessie?
What i would do is press E on grub remove the " quiet " and see when it boot where it hangs or what error spits out .
The problem is not during the boot. It's during the login to the OS.
Just reinstalled Ascii. I'm still getting the long login time even before I have done anything with it (logged in twice so far). I don't remember this happening when I first installed Ascii (I mean before the changes I had made). I'm stumped on this. I guess I'll just have to wait for an updated Ascii in the future. Unless anyone has any ideas.
If I wipe the partition Ascii is on, and consolidate it back onto the Jessie partition, will that mess up the grub boot loader? If so, how would I fix it?
I'll try an OS reinstall without deleting anything. But I won't be able to get to it until late tonight. Will post results back later tonight.
Thanks for the help so far.
MiyoLinux wrote:
Okay, I'm nearing the end of my knowledge. I'm seriously wondering how much the deletion of Openbox and the change to Mate under the "still being developed Ascii" is influencing this; however, let's try one more thing...
That didn't work. What was that supposed do? Before I made this edit I was able to press F1 and get "Session: Mate." (After the edit I still had to press F1 to get it.)
Another thing I should mention. I notice that about maybe 1 out of 6 times it will login very quickly.
golinux wrote:
Keeping in mind that slim and lightdm require different backends iirc.
So if I wanted to switch to lightdm, does that mean that I would need to install something else along with it?