You are not logged in.
Pages: 1
I've made a shutdown utility to use on future versions of Miyo. I'm using it now on the latest release instead of the default obsession utility...
My question is, for those who use Suspend, do you prefer the screen to be locked when you Suspend? Yes, no...doesn't matter?
I'm not asking in regards to MiyoLinux users; I'm asking in regard to anyone who uses Suspend on any operating system.
Thank you for any input!
Click to enlarge...
Last edited by MiyoLinux (2018-05-12 14:29:16)
I have been Devuanated, and my practice in the art of Devuanism shall continue until my Devuanization is complete. Until then, I will strive to continue in my understanding of Devuanchology, Devuanprocity, and Devuanivity.
Veni, vidi, vici vdevuaned. I came, I saw, I Devuaned.
Offline
I usually don't use suspend, so I can't say. But I'd like to have a look at the source of your utility if you don't mind. Can you put it up on GitHub? I suppose it's either written in Bash or Python. I'm working on something similar (in Bash, currently).
Last edited by msi (2018-05-13 23:29:03)
Offline
I've made a shutdown utility to use on future versions of Miyo.......
My question is, for those who use Suspend, do you prefer the screen to be locked when you Suspend?
Just found this, and "No" - I don't want screen to be locked. But, isn't that an option in power manager?
Keeping the option, sounds good to keep
asta
miyoisomix.i2p
Offline
I'm asking in regard to anyone who uses Suspend on any operating system
I generally prefer systems to err on the side of being mistrusting. If I'm using suspend, I'm probably on a device with a battery. Devices on batteries can be picked up and moved away from the owner.
Lock screen, verify that the person in front of the computer is the owner before displaying any potentilaly sensitive data.
---
Devuan Ceres | Ryzen 2400G | RX560 | 32GB RAM | Samsung 850 Pro
Offline
yes, always turn on a screen lock in screensaver/suspend.
but in general i agree with @stanz, that should be a choice, not a default
Offline
I'm with imhigh.today and xinomilo, it should have at least the option to lock. I want my screen to be locked when resuming from either suspend or hibernate.
Offline
First...thanks for these latest replies. I truly appreciate it.
Second, to msi...I don't know if you'll see this, but I promise that I wasn't avoiding your inquiry. I don't know how I missed it before. Please forgive me.
I usually don't use suspend, so I can't say. But I'd like to have a look at the source of your utility if you don't mind. Can you put it up on GitHub? I suppose it's either written in Bash or Python. I'm working on something similar (in Bash, currently).
No...it's simply a basic YAD script...that I'm going to have to change since consolekit apparently will no longer be available beginning in beowulf.
Here it is as it currently exists...
#!/bin/sh
yad --form --center --undecorated --width=165 --borders=10 --height=320 --title="Exit" --skip-taskbar \
--image=/usr/share/miyolinux/miyo-exit.png --image-on-top \
--field=" Shutdown!gnome-shutdown!Shut Down":fbtn "dbus-send --system --print-reply --dest="org.freedesktop.ConsoleKit" /org/freedesktop/ConsoleKit/Manager org.freedesktop.ConsoleKit.Manager.Stop" \
--field=" Reboot!system-reboot!Restart":fbtn "dbus-send --system --print-reply --dest="org.freedesktop.ConsoleKit" /org/freedesktop/ConsoleKit/Manager org.freedesktop.ConsoleKit.Manager.Restart" \
--field=" Suspend!gnome-session-suspend!Suspend":fbtn "dbus-send --system --print-reply --dest="org.freedesktop.UPower" /org/freedesktop/UPower org.freedesktop.UPower.Suspend" \
--field=" Hibernate!gnome-session-hibernate!Hibernate":fbtn "dbus-send --system --print-reply --dest="org.freedesktop.UPower" /org/freedesktop/UPower org.freedesktop.UPower.Hibernate" \
--field=" Log Out!gnome-logout!Log Out":fbtn "openbox --exit" \
--button=gtk-cancel --buttons-layout=center \
Last edited by MiyoLinux (2019-02-16 20:47:35)
I have been Devuanated, and my practice in the art of Devuanism shall continue until my Devuanization is complete. Until then, I will strive to continue in my understanding of Devuanchology, Devuanprocity, and Devuanivity.
Veni, vidi, vici vdevuaned. I came, I saw, I Devuaned.
Offline
No...it's simply a basic YAD script...that I'm going to have to change since consolekit apparently will no longer be available beginning in beowulf.
Isn't there consolekit2. There has been recent discussion. and also there are consolekit related packages in beowulf:
libpolkit-backend-1-0-consolekit
libpolkit-gobject-1-0-consolekit
etc.
You should probably be on the ML.
Offline
MiyoLinux wrote:No...it's simply a basic YAD script...that I'm going to have to change since consolekit apparently will no longer be available beginning in beowulf.
Isn't there consolekit2. There has been recent discussion. and also there are consolekit related packages in beowulf:
libpolkit-backend-1-0-consolekit
libpolkit-gobject-1-0-consolekit
etc.You should probably be on the ML.
Oh...
The last time I tried a straight beowulf build, it was a no-go with consolekit. Perhaps I should try again. LOLOLOLOL!
I've been too busy with the latest i3 versions to test things...
Thank you...I'll look into it when I have time.
I have been Devuanated, and my practice in the art of Devuanism shall continue until my Devuanization is complete. Until then, I will strive to continue in my understanding of Devuanchology, Devuanprocity, and Devuanivity.
Veni, vidi, vici vdevuaned. I came, I saw, I Devuaned.
Offline
golinux wrote:MiyoLinux wrote:No...it's simply a basic YAD script...that I'm going to have to change since consolekit apparently will no longer be available beginning in beowulf.
Isn't there consolekit2. There has been recent discussion. and also there are consolekit related packages in beowulf:
libpolkit-backend-1-0-consolekit
libpolkit-gobject-1-0-consolekit
etc.You should probably be on the ML.
Oh...
The last time I tried a straight beowulf build, it was a no-go with consolekit. Perhaps I should try again. LOLOLOLOL!
I've been too busy with the latest i3 versions to test things...
Thank you...I'll look into it when I have time.
I'm the Ultra-Quoter! LOLOLOLOLOLOLOLOLOL!
Well, I tried a quick basic beowulf Openbox build this evening...there's good news and bad news.
The bad news: still no Consolekit.
The good news: the obsession utility (from the repositories) works with elogind! I can shutdown, reboot, etc with it.
Using lxpolkit (for the authentication agent), still works fantastic for opening things like synaptic too.
Now if I can figure out what commands obsession is using...
I have been Devuanated, and my practice in the art of Devuanism shall continue until my Devuanization is complete. Until then, I will strive to continue in my understanding of Devuanchology, Devuanprocity, and Devuanivity.
Veni, vidi, vici vdevuaned. I came, I saw, I Devuaned.
Offline
The bad news: still no Consolekit.
These packages may or may not be relevant but . . . I leave it to you to sort . . .
Offline
Thank you, but I no longer need Consolekit since obsession works with elogind.
I have been Devuanated, and my practice in the art of Devuanism shall continue until my Devuanization is complete. Until then, I will strive to continue in my understanding of Devuanchology, Devuanprocity, and Devuanivity.
Veni, vidi, vici vdevuaned. I came, I saw, I Devuaned.
Offline
Hooray! I F...I...N...A...L...L...Y found the commands that work with elogind for my exit utility!
loginctl poweroff
loginctl reboot
loginctl suspend
loginctl hibernate
So, if this may possibly help anyone else, here's the new code for the exit utility in upcoming MiyoLinux versions based on beowulf...
#!/bin/sh
yad --form --center --undecorated --align=left --width=165 --borders=10 --height=320 --skip-taskbar \
--image=/usr/share/miyolinux/miyo-exit.png --image-on-top \
--field=" Shutdown!gnome-shutdown!Shut Down":fbtn "loginctl poweroff" \
--field=" Reboot!system-reboot!Restart":fbtn "loginctl reboot" \
--field=" Suspend!gnome-session-suspend!Suspend":fbtn "loginctl suspend" \
--field=" Hibernate!gnome-session-hibernate!Hibernate":fbtn "loginctl hibernate" \
--field=" Log Out!gnome-logout!Log Out":fbtn "openbox --exit" \
--button=gtk-cancel --buttons-layout=center \
...it still looks the same...
Last edited by MiyoLinux (2019-02-20 04:53:37)
I have been Devuanated, and my practice in the art of Devuanism shall continue until my Devuanization is complete. Until then, I will strive to continue in my understanding of Devuanchology, Devuanprocity, and Devuanivity.
Veni, vidi, vici vdevuaned. I came, I saw, I Devuaned.
Offline
Are you sure? loginctl is in the systemd package .. or rather, where did you get it from?
Offline
Ralph, I found it in an old manjaro forum from back when they still had an openrc version.
That loginctl part works on my Beowulf build for shutdown, reboot, and suspend. I haven't tried hibernate yet.
Have I stumbled upon a boo-boo?
I have been Devuanated, and my practice in the art of Devuanism shall continue until my Devuanization is complete. Until then, I will strive to continue in my understanding of Devuanchology, Devuanprocity, and Devuanivity.
Veni, vidi, vici vdevuaned. I came, I saw, I Devuaned.
Offline
Well, I think one can say you are threading the boundary at least
MiyoLinux distribution = Devuan beowulf + ( some bits of systemd that happened to work today )
It doesn't bother me as such, but I might be special
Offline
LOL!
Dagnabit! Just when I thought I was onto something...
I'll see how it plays out...
I have been Devuanated, and my practice in the art of Devuanism shall continue until my Devuanization is complete. Until then, I will strive to continue in my understanding of Devuanchology, Devuanprocity, and Devuanivity.
Veni, vidi, vici vdevuaned. I came, I saw, I Devuaned.
Offline
Are you sure? loginctl is in the systemd package .. or rather, where did you get it from?
Ah...this just registered with me (if I understand the question correctly).
I didn't get "it" anywhere. I just saw what someone was using on Manjaro OpenRC in their i3 config file; which was, loginctl ______ .
I didn't install anything extra; I simply tried the commands first from the terminal, and they worked. Now...whether that relates to it working now (in beowulf) as opposed to it continuing to work in the future...I don't know.
Just wanted to clarify that I didn't install anything to give me the ability to use loginctl.
I have been Devuanated, and my practice in the art of Devuanism shall continue until my Devuanization is complete. Until then, I will strive to continue in my understanding of Devuanchology, Devuanprocity, and Devuanivity.
Veni, vidi, vici vdevuaned. I came, I saw, I Devuaned.
Offline
mmm maybe a
dpkg -S loginctl
could shed some light on it. For me, as I don't have that program, I tried
apt-file find loginctl
which reported it as belonging to systemd. And as far as I can tell, there is no installation candidate for that package in any Devuan repository.
Offline
mmm maybe a
dpkg -S loginctl
could shed some light on it. For me, as I don't have that program, I tried
apt-file find loginctl
which reported it as belonging to systemd. And as far as I can tell, there is no installation candidate for that package in any Devuan repository.
Strange.
I'm using straight beowulf repositories. No outside packages installed other than the Refracta tools (which apparently aren't in beowulf yet?)...and my window themes and custom accessories (that use yad straight from the beowulf repos).
Just for kicks, I did another build on another computer that's even more stripped down (than my normal build) with only beowulf repos and no other additions at all...and loginctl works on it too.
Edited to add: I'm on my phone and can't check that command right now. I'll try it later.
Last edited by MiyoLinux (2019-02-20 12:52:13)
I have been Devuanated, and my practice in the art of Devuanism shall continue until my Devuanization is complete. Until then, I will strive to continue in my understanding of Devuanchology, Devuanprocity, and Devuanivity.
Veni, vidi, vici vdevuaned. I came, I saw, I Devuaned.
Offline
beowulf.
$ dpkg -S loginctl
elogind: /bin/loginctl
$ apt policy elogind
elogind:
Installed: 239.3+20190131-1
Candidate: 239.3+20190131-1
Version table:
*** 239.3+20190131-1 500
500 http://gr.deb.devuan.org/merged testing/main amd64 Packages
500 http://gr.deb.devuan.org/merged ceres/main amd64 Packages
100 /var/lib/dpkg/status
Offline
Good. Apparently my use of apt-file leaves some to be desired.
Offline
Good. Apparently my use of apt-file leaves some to be desired.
LOL!
Here's what mine shows...
dan@miyolinux:~$ dpkg -S loginctl
elogind: /usr/share/bash-completion/completions/loginctl
elogind: /usr/share/man/man1/loginctl.1.gz
elogind: /bin/loginctl
elogind: /usr/share/zsh/site-functions/_loginctl
...and available options...
dan@miyolinux:~$ loginctl -h
loginctl [OPTIONS...] {COMMAND} ...
Send control commands to or query the login manager.
-h --help Show this help
--version Show package version
--no-pager Do not pipe output into a pager
--no-wall Do not print any wall message
--dry-run Only print what would be done
-q --quiet Suppress output
--no-legend Do not show the headers and footers
--no-ask-password Don't prompt for password
-H --host=[USER@]HOST Operate on remote host
-M --machine=CONTAINER Operate on local container
-p --property=NAME Show only properties by this name
-a --all Show all properties, including empty ones
--value When showing properties, only print the value
-l --full Do not ellipsize output
--kill-who=WHO Who to send signal to
-s --signal=SIGNAL Which signal to send
-c Cancel a pending shutdown or reboot
-i --ignore-inhibitors When shutting down or sleeping, ignore inhibitors
Session Commands:
list[-sessions] List sessions (default command)
session-status [ID...] Show session status
show-session [ID...] Show properties of sessions or the manager
activate [ID] Activate a session
lock-session [ID...] Screen lock one or more sessions
unlock-session [ID...] Screen unlock one or more sessions
lock-sessions Screen lock all current sessions
unlock-sessions Screen unlock all current sessions
terminate-session ID... Terminate one or more sessions
kill-session ID... Send signal to processes of a session
User Commands:
list-users List users
user-status [USER...] Show user status
show-user [USER...] Show properties of users or the manager
enable-linger [USER...] Enable linger state of one or more users
disable-linger [USER...] Disable linger state of one or more users
terminate-user USER... Terminate all sessions of one or more users
kill-user USER... Send signal to processes of a user
Seat Commands:
list-seats List seats
seat-status [NAME...] Show seat status
show-seat [NAME...] Show properties of seats or the manager
attach NAME DEVICE... Attach one or more devices to a seat
flush-devices Flush all device associations
terminate-seat NAME... Terminate all sessions on one or more seats
System Commands:
poweroff [TIME] [WALL...] Turn off the machine
reboot [TIME] [WALL...] Reboot the machine
suspend Suspend the machine to memory
hibernate Suspend the machine to disk
hybrid-sleep Suspend the machine to memory and disk
suspend-then-hibernate Suspend the system, wake after a period of
time and put it into hibernate
I have been Devuanated, and my practice in the art of Devuanism shall continue until my Devuanization is complete. Until then, I will strive to continue in my understanding of Devuanchology, Devuanprocity, and Devuanivity.
Veni, vidi, vici vdevuaned. I came, I saw, I Devuaned.
Offline
Pages: 1