The officially official Devuan Forum!

You are not logged in.

#1 Re: DIY » Input requested regarding Suspend » Today 12:49:51

ralph.ronnquist wrote:

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. smile

#2 Re: DIY » Input requested regarding Suspend » Today 11:00:30

ralph.ronnquist wrote:

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.

#3 Re: DIY » Input requested regarding Suspend » Today 07:18:44

LOL! big_smile

Dagnabit! Just when I thought I was onto something...

I'll see how it plays out...

#4 Re: DIY » Input requested regarding Suspend » Today 07:01:02

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? tongue

#5 Re: DIY » Input requested regarding Suspend » Today 04:52:59

Hooray! I F...I...N...A...L...L...Y found the commands that work with elogind for my exit utility! tongue

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...

miyo-exit_1_orig.png

#6 Re: Installation » Beowulf: Link sbin » 2019-02-18 22:06:22

fsmithred wrote:

The problem you're running into is the change in root's path when you run su in a terminal. That path no longer contains the sbins. If you use su - instead, you'll get the root path that you're used to. But then you won't be able to start graphical apps as root from that terminal. For that, you're supposed to use pkexec. When you figure all that out, I'll read your posts. Until then, or until someone gives me good reasons not to do this, I'm working around the problem.

# grep PATH /root/.bashrc
export PATH="/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin"

Oh yeah, the other workaround is to use the full path for commands.

/sbin/blkid
/usr/sbin/update-grub

Thanks fsr. The "full path" answer is what I thought of after doing it the way that I did. I wasn't aware of su -. Thanks.

As for opening items with pkexec, I have a couple of apps in the "MiyoLinux Accessories" that run as root. PCManFM and Lxappearance. The way that I solved that was to add a file for both of them in /usr/share/policykit-1/actions/

I just used one of the existing ones as a template and changed each instance of the original application's name in the existing file to the appropriate name of the application that I wanted to use it for in the file I was creating; such as, if I were using the synaptic file as an example, I replaced every instance of synaptic with lxapppearance...hope that makes sense. Also, I changed the icon used and named both files similarly to how the existing files are named.

Anyway, I can now open both PCManFM (as root) and Customize Look and Feel (as root) from the menu using pkexec. smile

#7 Installation » Beowulf: Link sbin » 2019-02-18 09:31:25

MiyoLinux
Replies: 11

After my latest stab at building a basic Openbox system on the Beowulf .iso, everything is working wonderfully. smile

I have one question, and I know that this is rather vague...

During the installation, there was an option to link sbin to bin (?). I can't remember exactly what it said...sorry. I'm bad about not reading things. LOL! tongue

Anyway...I chose the default answer of No. Later on, after setting everything up and adding a desktop-grub.png image, I tried to run update-grub and received an error in the terminal that the update-grub command wasn't found. Grrrrrr...

So...I opened the file manager as root, went to the sbin folder, and sure enough...update-grub was there. So I opened the terminal in that folder and ran update-grub successfully.

So my question is...despite the default answer of no, should sbin be linked to bin (or whatever that option was) in Beowulf? I just don't have it in me to go through another installation right now in order to read that message during the installation. sad  tongue

#8 Re: DIY » Input requested regarding Suspend » 2019-02-18 02:58:57

Thank you, but I no longer need Consolekit since obsession works with elogind.

#9 Re: DIY » Input requested regarding Suspend » 2019-02-18 01:28:11

MiyoLinux wrote:
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. neutral  tongue

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...

tongue

The last time I tried a straight beowulf build, it was a no-go with consolekit. Perhaps I should try again. LOLOLOLOL! tongue

I've been too busy with the latest i3 versions to test things...

Thank you...I'll look into it when I have time. smile

I'm the Ultra-Quoter! LOLOLOLOLOLOLOLOLOL!  tongue

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. smile

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...

#10 Re: Devuan Derivatives » [MiyoLinux] Miyo-i3 Releases » 2019-02-16 21:36:36

The new versions of Miyo-i3 are now available. smile  I've made a few improvements over the last release of Miyo-i3...I think. LOLOLOLOLOL!!! tongue

Here is a video overview of it...

https://www.youtube.com/watch?v=FjkXMRCxM0E&t=116s

Downloads include 32 bit, 64 bit, and a 64 bit EFI version. They are available for download here...

https://sourceforge.net/projects/miyoli … elease/i3/

#11 Re: DIY » Input requested regarding Suspend » 2019-02-16 21:33:09

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. neutral  tongue

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...

tongue

The last time I tried a straight beowulf build, it was a no-go with consolekit. Perhaps I should try again. LOLOLOLOL! tongue

I've been too busy with the latest i3 versions to test things...

Thank you...I'll look into it when I have time. smile

#12 Re: DIY » Input requested regarding Suspend » 2019-02-16 20:45:14

First...thanks for these latest replies. smile  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.

msi wrote:

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. neutral  tongue

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 \

#13 Re: Devuan » As an extensive user, GIMP 2.10.x is unusable. 2.8.x is great though! » 2019-02-16 20:37:14

I definitely agree with the OP. In trying the later versions of GIMP, I found that some of the options that I used were no longer there, or some of the options that I used were completely changed. I basically would have to learn how to use GIMP all over again. So...

#14 Re: Desktop and Multimedia » Software update notifications in XFCE » 2019-02-16 17:29:23

franko wrote:

No, the mail is delivered every time a root cron job is done...

Sorry for raising confusion. XD But I learned something. :-)

I also learned something. I have no mail. So, what you pointed out is good for me to know.

I didn't see it as confusion. smile

#15 Re: Desktop and Multimedia » Software update notifications in XFCE » 2019-02-16 03:48:23

franko wrote:

I've been reading this guide, that brought me to my undestanding: https://code.tutsplus.com/tutorials/sch … --net-8800

Where do you get that log? I've been just observing when do I get the aforementioned mail from the cron job...

My cron job for the update is set like this: 0 */3 * * * root /usr/bin/apt-get update

According to what you say and what seems from that log, it would mean it would be done at 3 am, 6 am etc... But I received that mail some time after midnight and before 3 am -- of that I'm sure. So I believe it counts 3 hours since the computer boot up, and than again, and again... I will give more precise attention to it tomorrow.

It IS confusing...

I don't know...perhaps the mail only goes out once a day?

Regarding the location of the log...I'm on my phone, so I'm doing this from memory...

I don't remember the actual name of the cron log file...but it's located in /var/log/ and it has "cron" in the name.

EDITED: Of all things, it's called cron.log   LOLOLOL! tongue

If it's not already there, check to see if cron is commented out in the rsyslog.conf file...found in /etc/rsyslog.conf.

I think you may have to reboot after uncommenting cron in the rsyslog.conf file for it to show up in /var/log.

#16 Re: Desktop and Multimedia » Software update notifications in XFCE » 2019-02-16 00:07:44

MiyoLinux wrote:
franko wrote:

Are you sure? If I understand that syntax right, that means every 3:45 h since a computer is started. I believe 3 would mean at 3 am, and */3 means every 3 hours since you start a computer... Am I wrong about it? At least, that's what it seems to work like here on my machine...

I'm gonna have a brain-jerkdown thinking about this. LOL! tongue

According to my cron log, mine is working as I described. For instance, if I turn my computer on at 8:30 am (and using the 45 */3 * * * example), the cron job will do its first run at 9:45 am...despite the computer has only been on an hour and 15 minutes. However, the update-notifier.py script won't run until the computer has been on for 4 hours.

That's how mine is working...never know though...I might've jinxed it. LOLOLOL! tongue

Edited to add...

It's almost time for the cron job to run...I'll reboot and double-check. I'll report back.

Okay...it's working as I described. I'm doing the final testing of the i3 release today, so this cron log is from it.

RED = When the computer is turned on (notice I turned it on after the 6:45 am mark, but it still ran the first cron at 9:45. The second time in RED is when I rebooted to make sure that I knew what I was talking about. LOL! big_smile  Computer on at 6:20 pm, and the cron ran at 6:45 pm.

YELLOW = the cron job for the updater.

Feb 15 06:50:25 localhost cron[1386]: (CRON) INFO (pidfile fd = 3)
Feb 15 06:50:25 localhost cron[1387]: (CRON) STARTUP (fork ok)
Feb 15 06:50:25 localhost cron[1387]: (CRON) INFO (Running @reboot jobs)

Feb 15 06:55:01 localhost CRON[2835]: (root) CMD (command -v debian-sa1 > /dev/null && debian-sa1 1 1)
Feb 15 07:05:01 localhost CRON[3939]: (root) CMD (command -v debian-sa1 > /dev/null && debian-sa1 1 1)
Feb 15 07:15:01 localhost CRON[5020]: (root) CMD (command -v debian-sa1 > /dev/null && debian-sa1 1 1)
Feb 15 07:17:01 localhost CRON[5231]: (root) CMD (   cd / && run-parts --report /etc/cron.hourly)
Feb 15 07:25:01 localhost CRON[6083]: (root) CMD (command -v debian-sa1 > /dev/null && debian-sa1 1 1)
Feb 15 07:30:01 localhost CRON[6638]: (root) CMD ([ -x /etc/init.d/anacron ] && if [ ! -d /run/systemd/system ]; then /usr/sbin/invoke-rc.d anacron start >/dev/null; fi)
Feb 15 07:35:01 localhost CRON[7189]: (root) CMD (command -v debian-sa1 > /dev/null && debian-sa1 1 1)
Feb 15 07:45:01 localhost CRON[8233]: (root) CMD (command -v debian-sa1 > /dev/null && debian-sa1 1 1)
Feb 15 07:55:01 localhost CRON[9322]: (root) CMD (command -v debian-sa1 > /dev/null && debian-sa1 1 1)
Feb 15 08:05:01 localhost CRON[10344]: (root) CMD (command -v debian-sa1 > /dev/null && debian-sa1 1 1)
Feb 15 08:15:01 localhost CRON[11372]: (root) CMD (command -v debian-sa1 > /dev/null && debian-sa1 1 1)
Feb 15 08:17:01 localhost CRON[11583]: (root) CMD (   cd / && run-parts --report /etc/cron.hourly)
Feb 15 08:25:01 localhost CRON[12388]: (root) CMD (command -v debian-sa1 > /dev/null && debian-sa1 1 1)
Feb 15 08:35:01 localhost CRON[13416]: (root) CMD (command -v debian-sa1 > /dev/null && debian-sa1 1 1)
Feb 15 08:45:01 localhost CRON[14420]: (root) CMD (command -v debian-sa1 > /dev/null && debian-sa1 1 1)
Feb 15 08:55:01 localhost CRON[15417]: (root) CMD (command -v debian-sa1 > /dev/null && debian-sa1 1 1)
Feb 15 09:05:01 localhost CRON[16414]: (root) CMD (command -v debian-sa1 > /dev/null && debian-sa1 1 1)
Feb 15 09:15:01 localhost CRON[17415]: (root) CMD (command -v debian-sa1 > /dev/null && debian-sa1 1 1)
Feb 15 09:17:01 localhost CRON[17610]: (root) CMD (   cd / && run-parts --report /etc/cron.hourly)
Feb 15 09:25:01 localhost CRON[18398]: (root) CMD (command -v debian-sa1 > /dev/null && debian-sa1 1 1)
Feb 15 09:35:01 localhost CRON[19394]: (root) CMD (command -v debian-sa1 > /dev/null && debian-sa1 1 1)
Feb 15 09:45:01 localhost CRON[20393]: (root) CMD (/usr/bin/apt-get update)
Feb 15 09:45:01 localhost CRON[20394]: (root) CMD (command -v debian-sa1 > /dev/null && debian-sa1 1 1)
Feb 15 09:45:17 localhost CRON[20390]: (CRON) info (No MTA installed, discarding output)
Feb 15 09:55:01 localhost CRON[21645]: (root) CMD (command -v debian-sa1 > /dev/null && debian-sa1 1 1)
Feb 15 10:05:01 localhost CRON[22635]: (root) CMD (command -v debian-sa1 > /dev/null && debian-sa1 1 1)
Feb 15 10:15:01 localhost CRON[23611]: (root) CMD (command -v debian-sa1 > /dev/null && debian-sa1 1 1)
Feb 15 10:17:01 localhost CRON[23814]: (root) CMD (   cd / && run-parts --report /etc/cron.hourly)
Feb 15 10:25:01 localhost CRON[24602]: (root) CMD (command -v debian-sa1 > /dev/null && debian-sa1 1 1)
Feb 15 10:35:01 localhost CRON[25594]: (root) CMD (command -v debian-sa1 > /dev/null && debian-sa1 1 1)
Feb 15 10:45:01 localhost CRON[26594]: (root) CMD (command -v debian-sa1 > /dev/null && debian-sa1 1 1)
Feb 15 10:55:01 localhost CRON[27587]: (root) CMD (command -v debian-sa1 > /dev/null && debian-sa1 1 1)
Feb 15 11:05:01 localhost CRON[28572]: (root) CMD (command -v debian-sa1 > /dev/null && debian-sa1 1 1)
Feb 15 11:15:01 localhost CRON[29552]: (root) CMD (command -v debian-sa1 > /dev/null && debian-sa1 1 1)
Feb 15 11:17:01 localhost CRON[29748]: (root) CMD (   cd / && run-parts --report /etc/cron.hourly)
Feb 15 11:25:01 localhost CRON[30540]: (root) CMD (command -v debian-sa1 > /dev/null && debian-sa1 1 1)
Feb 15 11:35:01 localhost CRON[31520]: (root) CMD (command -v debian-sa1 > /dev/null && debian-sa1 1 1)
Feb 15 11:45:01 localhost CRON[32516]: (root) CMD (command -v debian-sa1 > /dev/null && debian-sa1 1 1)
Feb 15 11:55:01 localhost CRON[1038]: (root) CMD (command -v debian-sa1 > /dev/null && debian-sa1 1 1)
Feb 15 12:05:01 localhost CRON[2166]: (root) CMD (command -v debian-sa1 > /dev/null && debian-sa1 1 1)
Feb 15 12:15:01 localhost CRON[3162]: (root) CMD (command -v debian-sa1 > /dev/null && debian-sa1 1 1)
Feb 15 12:17:01 localhost CRON[3357]: (root) CMD (   cd / && run-parts --report /etc/cron.hourly)
Feb 15 12:25:01 localhost CRON[4137]: (root) CMD (command -v debian-sa1 > /dev/null && debian-sa1 1 1)
Feb 15 12:35:01 localhost CRON[5126]: (root) CMD (command -v debian-sa1 > /dev/null && debian-sa1 1 1)
Feb 15 12:45:01 localhost CRON[6107]: (root) CMD (/usr/bin/apt-get update)
Feb 15 12:45:01 localhost CRON[6108]: (root) CMD (command -v debian-sa1 > /dev/null && debian-sa1 1 1)
Feb 15 12:45:07 localhost CRON[6106]: (CRON) info (No MTA installed, discarding output)
Feb 15 12:55:01 localhost CRON[7362]: (root) CMD (command -v debian-sa1 > /dev/null && debian-sa1 1 1)
Feb 15 13:05:01 localhost CRON[8347]: (root) CMD (command -v debian-sa1 > /dev/null && debian-sa1 1 1)
Feb 15 13:15:01 localhost CRON[9339]: (root) CMD (command -v debian-sa1 > /dev/null && debian-sa1 1 1)
Feb 15 13:17:01 localhost CRON[9539]: (root) CMD (   cd / && run-parts --report /etc/cron.hourly)
Feb 15 13:25:01 localhost CRON[10412]: (root) CMD (command -v debian-sa1 > /dev/null && debian-sa1 1 1)
Feb 15 13:35:01 localhost CRON[11401]: (root) CMD (command -v debian-sa1 > /dev/null && debian-sa1 1 1)
Feb 15 13:45:01 localhost CRON[12389]: (root) CMD (command -v debian-sa1 > /dev/null && debian-sa1 1 1)
Feb 15 13:55:01 localhost CRON[13369]: (root) CMD (command -v debian-sa1 > /dev/null && debian-sa1 1 1)
Feb 15 14:05:01 localhost CRON[14358]: (root) CMD (command -v debian-sa1 > /dev/null && debian-sa1 1 1)
Feb 15 14:15:01 localhost CRON[15338]: (root) CMD (command -v debian-sa1 > /dev/null && debian-sa1 1 1)
Feb 15 14:17:01 localhost CRON[15542]: (root) CMD (   cd / && run-parts --report /etc/cron.hourly)
Feb 15 14:25:01 localhost CRON[16330]: (root) CMD (command -v debian-sa1 > /dev/null && debian-sa1 1 1)
Feb 15 14:35:01 localhost CRON[17314]: (root) CMD (command -v debian-sa1 > /dev/null && debian-sa1 1 1)
Feb 15 14:45:01 localhost CRON[18298]: (root) CMD (command -v debian-sa1 > /dev/null && debian-sa1 1 1)
Feb 15 14:55:01 localhost CRON[19289]: (root) CMD (command -v debian-sa1 > /dev/null && debian-sa1 1 1)
Feb 15 15:05:01 localhost CRON[20269]: (root) CMD (command -v debian-sa1 > /dev/null && debian-sa1 1 1)
Feb 15 15:15:01 localhost CRON[21270]: (root) CMD (command -v debian-sa1 > /dev/null && debian-sa1 1 1)
Feb 15 15:17:01 localhost CRON[21469]: (root) CMD (   cd / && run-parts --report /etc/cron.hourly)
Feb 15 15:25:01 localhost CRON[22250]: (root) CMD (command -v debian-sa1 > /dev/null && debian-sa1 1 1)
Feb 15 15:35:01 localhost CRON[23242]: (root) CMD (command -v debian-sa1 > /dev/null && debian-sa1 1 1)
Feb 15 15:45:01 localhost CRON[24233]: (root) CMD (/usr/bin/apt-get update)
Feb 15 15:45:01 localhost CRON[24234]: (root) CMD (command -v debian-sa1 > /dev/null && debian-sa1 1 1)
Feb 15 15:45:06 localhost CRON[24232]: (CRON) info (No MTA installed, discarding output)
Feb 15 15:55:01 localhost CRON[25471]: (root) CMD (command -v debian-sa1 > /dev/null && debian-sa1 1 1)
Feb 15 16:05:01 localhost CRON[26471]: (root) CMD (command -v debian-sa1 > /dev/null && debian-sa1 1 1)
Feb 15 16:15:01 localhost CRON[27455]: (root) CMD (command -v debian-sa1 > /dev/null && debian-sa1 1 1)
Feb 15 16:17:01 localhost CRON[27654]: (root) CMD (   cd / && run-parts --report /etc/cron.hourly)
Feb 15 16:25:01 localhost CRON[28443]: (root) CMD (command -v debian-sa1 > /dev/null && debian-sa1 1 1)
Feb 15 16:35:01 localhost CRON[29423]: (root) CMD (command -v debian-sa1 > /dev/null && debian-sa1 1 1)
Feb 15 16:45:01 localhost CRON[30413]: (root) CMD (command -v debian-sa1 > /dev/null && debian-sa1 1 1)
Feb 15 16:55:01 localhost CRON[31389]: (root) CMD (command -v debian-sa1 > /dev/null && debian-sa1 1 1)
Feb 15 17:05:01 localhost CRON[32365]: (root) CMD (command -v debian-sa1 > /dev/null && debian-sa1 1 1)
Feb 15 17:15:01 localhost CRON[888]: (root) CMD (command -v debian-sa1 > /dev/null && debian-sa1 1 1)
Feb 15 17:17:01 localhost CRON[1091]: (root) CMD (   cd / && run-parts --report /etc/cron.hourly)
Feb 15 17:25:01 localhost CRON[2017]: (root) CMD (command -v debian-sa1 > /dev/null && debian-sa1 1 1)
Feb 15 17:35:01 localhost CRON[3006]: (root) CMD (command -v debian-sa1 > /dev/null && debian-sa1 1 1)
Feb 15 17:45:01 localhost CRON[3984]: (root) CMD (command -v debian-sa1 > /dev/null && debian-sa1 1 1)
Feb 15 17:55:01 localhost CRON[4974]: (root) CMD (command -v debian-sa1 > /dev/null && debian-sa1 1 1)
Feb 15 18:05:01 localhost CRON[5958]: (root) CMD (command -v debian-sa1 > /dev/null && debian-sa1 1 1)
Feb 15 18:15:01 localhost CRON[6946]: (root) CMD (command -v debian-sa1 > /dev/null && debian-sa1 1 1)
Feb 15 18:17:01 localhost CRON[7146]: (root) CMD (   cd / && run-parts --report /etc/cron.hourly)
Feb 15 18:20:45 localhost cron[1397]: (CRON) INFO (pidfile fd = 3)
Feb 15 18:20:45 localhost cron[1398]: (CRON) STARTUP (fork ok)
Feb 15 18:20:45 localhost cron[1398]: (CRON) INFO (Running @reboot jobs)

Feb 15 18:25:01 localhost CRON[2646]: (root) CMD (command -v debian-sa1 > /dev/null && debian-sa1 1 1)
Feb 15 18:35:01 localhost CRON[3703]: (root) CMD (command -v debian-sa1 > /dev/null && debian-sa1 1 1)
Feb 15 18:45:01 localhost CRON[4732]: (root) CMD (/usr/bin/apt-get update)
Feb 15 18:45:01 localhost CRON[4733]: (root) CMD (command -v debian-sa1 > /dev/null && debian-sa1 1 1)
Feb 15 18:45:06 localhost CRON[4731]: (CRON) info (No MTA installed, discarding output)

#17 Re: Desktop and Multimedia » Software update notifications in XFCE » 2019-02-15 23:13:22

franko wrote:

Are you sure? If I understand that syntax right, that means every 3:45 h since a computer is started. I believe 3 would mean at 3 am, and */3 means every 3 hours since you start a computer... Am I wrong about it? At least, that's what it seems to work like here on my machine...

I'm gonna have a brain-jerkdown thinking about this. LOL! tongue

According to my cron log, mine is working as I described. For instance, if I turn my computer on at 8:30 am (and using the 45 */3 * * * example), the cron job will do its first run at 9:45 am...despite the computer has only been on an hour and 15 minutes. However, the update-notifier.py script won't run until the computer has been on for 4 hours.

That's how mine is working...never know though...I might've jinxed it. LOLOLOL! tongue

Edited to add...

It's almost time for the cron job to run...I'll reboot and double-check. I'll report back.

#18 Re: Desktop and Multimedia » Software update notifications in XFCE » 2019-02-15 20:27:19

Yes....well, mine runs at 45 minutes past every 7th hour starting at 7:00 am...

7:45 am, 2:45 pm, and 9:45 pm. Then it starts over at 7:45 am the next day.

The one in the .zip file download is...

3:45 am, 6:45 am, 9:45 am, 12:45 pm, 3:45 pm, 6:45 pm, and 9:45 pm. Then starts over at 3:45 am the next day.

I chose that route for the one included in the upcoming release, because it seemed like a reasonable compromise since I have no clue as to when a user may turn their computer on or how long they may leave their computer on. smile  tongue

#19 Re: Desktop and Multimedia » Software update notifications in XFCE » 2019-02-15 05:21:48

Sorry...I've been busy with the latest i3 releases. Hope to have them uploaded to Sourceforge tomorrow (Feb. 16). smile

I ended up using this for the cron job on my personal update notifier...

45 */7 * * * root /usr/bin/apt-get update

...and I have the update-notifier.py checking for updates every 8 hours.

I've been so busy that I forgot to upload a new .zip file for anyone else who may want to try it. The one that I uploaded is the one that I've included on the upcoming i3 versions. Its cron job is set up for this...

45 */3 * * * root /usr/bin/apt-get update

...and the update-notifier.py checks for updates every 4 hours.       

Here's the link to download the .zip file if you're interested...

https://my.pcloud.com/publink/show?code … iQqy9qb2sk

Here are the instructions that are included...

Notifications for updates are presented with a desktop notification and an icon in the system tray.

The notifier will only notify you that updates are available. Clicking on the desktop notification or icon in the system tray WILL NOT perform any updates. You will have to do that manually through the terminal or synaptic.

When you click the icon in the system tray, a notification will appear on the desktop and display the updates that are available. This will allow you to see what's available and decide if you want to install the updates immediately or wait until later.

By default, the notifier will check for updates every 4 hours; however, you can change the time interval for that.

To change the time interval, open the update-notifier.py with your text editor as root. I'll use leafpad as the example, but substitute leafpad with your preferred text editor...

sudo leafpad /usr/share/update-notifier/update-notifier.py

When it opens, enable line numbers, and go to line 38. It looks like this...

interval = 14400, # 4 hours

The 14400 is 14400 seconds (which equals 4 hours).

60 x 60 x 4 = 14400

60 seconds x 60 minutes x 4 hours = 14400 seconds

If you want to change that to a different time interval, you'll have to convert your interval into seconds. For example, if you wanted it to check for updates every 5 hours, you would use the following...

60 x 60 x 5 = 18000

60 seconds x 60 minutes x 5 hours = 18000 seconds

So you would edit line 38 to read as...

interval = 18000, # 5 hours

VERY IMPORTANT: DO NOT PLACE A COMMA INSIDE THE NUMBERS! Such as, 18,000 (with a comma). The number MUST BE 18000 (without a comma). However DO PLACE A COMMA AFTER THE NUMBER as given in the examples above.
___________________________________________________

To install, open your file manager as root, and...

1. Place the update_notifier text file in /etc/cron.d/

2. Place the Update Notifier application in /etc/xdg/autostart/

3. Place the show-updates script in /usr/local/bin/

4. Place the update-notifier folder in /usr/share/

5. Reboot

Be aware...some window managers don't use /etc/xdg/autostart, so if you are using a window manager (such as i3), you will have to add the update-notifier.py to your autostart file. For example, I added the following line to my autostart section in i3...

exec --no-startup-id /usr/share/update-notifier/update-notifier.py
___________________________________________________

If the notifier isn't working, make sure that you have the following installed...

python-gtk2
libnotify-bin
python-notify

#20 Re: Desktop and Multimedia » Software update notifications in XFCE » 2019-02-12 10:04:02

ralph.ronnquist wrote:

With * as "minute" it'll run every minute at the hours that divide evenly. So, you do need a specific minute number.

Thanks Ralph. I had already changed it to include 1 for the minute, because I saw that it wasn't working correctly. More waiting... tongue

Thank you.

#21 Re: Desktop and Multimedia » Software update notifications in XFCE » 2019-02-12 08:10:36

Well...I don't mind the cron job running. LOL! tongue

Finally figured it out...I think.

First, I wasn't getting any cron logs at all. I discovered that cron was commented out in the rsyslog.conf file.

Fixed that. Then noticed that in the cron log, it was saying that it had the wrong permissions...it was showing me as the owner of the file instead of root. So, I renamed the original file to update_notifier2, and created a new one as root named as the correct name of update_notifier, and copied the contents from the original file into it.

Here's the default cron job from the original...

*/30 * * * * root /usr/bin/apt-get update

Each asterisk represents a specific time-frame. There are 5 asterisks, and here are what they represent in order...

     *              *                    *                        *                            *
Minutes     Hours     Days of the month     Months            Days of the week
  0-59         0-23               1-31                   1-12        0-7 (Sunday is either 0 or 7)

That */ is very important. By using that, it's telling the cron job to run every 30 minutes of the day.

Here's what I'm currently testing...simply because I don't have much time right now...

* */2 * * * root /usr/bin/apt-get update

...which means that it should run the cron job everyday at 2 hour intervals...starting at 2:00 am. So, it should run at 2:00 am, 4:00 am, 6:00 am etc...

If this works, I'll change it to...

* */7 * * * root /usr/bin/apt-get update

...which will hopefully make it run 3 times a day at 7 hour intervals...7:00 am, 2:00 pm, and 9:00 pm. I'm not sure if a "minute" number is required or not. If it is, I'll use 5 for an example...

5 */7 * * * root /usr/bin/apt-get update

...would mean that it would run the cron job every 7 hours and 5 minutes. ???

We'll see...

fsmithred wrote:

@miyo:
In beowulf, /lib/live/mount has changed to /run/live/medium

Okay...thank you.

#22 Devuan Derivatives » [Miyo-Basic] Calendar position fix » 2019-02-11 05:23:56

MiyoLinux
Replies: 0

A YouTuber found an issue with Miyo-Basic...

When moving the panel to another position other than the bottom of the screen, the calendar still appears at the bottom of the screen when clicking on the clock. tongue

I apologize; this was an oversight on my part.

To fix this...

1. Open the Tint2 Settings application.
2. Click on the Clock tab.

Next to "Left click command", you will see the command used to open the calendar.

It looks like this...

yad --calendar --width=400 --borders=5 --button=gtk-close --posx=-1 --posy=-40 --skip-taskbar --undecorated --on-top

3. Replace --posx=-1 --posy=-40 with --mouse

It will then look like this...

yad --calendar --width=400 --borders=5 --button=gtk-close --mouse --skip-taskbar --undecorated --on-top

4. Click Apply.

The calendar will then appear at the correct position.

More references...

https://www.youtube.com/watch?v=HZ4_0UQIuxI&t=74s

https://sourceforge.net/p/miyolinux/wik … dar%20Fix/

#23 Re: Devuan Derivatives » [MiyoLinux] Miyo-i3 Releases » 2019-02-09 22:42:53

golinux wrote:

Wonderful!  You always make me smile.  big_smile

Well...not to toot my own horn, but I am a smiley kind'a guy...

LOLOLOLOLOLOLOL!!! tongue

#25 Re: Desktop and Multimedia » Software update notifications in XFCE » 2019-02-08 18:33:35

fsmithred wrote:

Played with it some more.
# Run my script
    gui = "/usr/local/bin/show-updates",


/usr/local/bin/show-updates (don't forget to make it executable)

#!/usr/bin/env bash

list=$(apt-get -s dist-upgrade | awk '/^Inst/ { print $2 }')
notify-send "$list"

exit 0

Outstanding! I REALLY like that. I was trying to figure out a way to use yad, but I like the notification better. Do you mind if I use your script in the upcoming Miyo-i3 release?

I did modify it a little...

#!/usr/bin/env bash

list=$(apt-get -s dist-upgrade | awk '/^Inst/ { print $2 }')
notify-send "The following updates are available: 

$list"

exit 0
fsmithred wrote:

Edit: Oops! This makes it run every minute. I put it back the way it was (0/30 * * * *)

I'm not wise in the ways of cron-ism... tongue big_smile

What if 30 was changed to 480? Would that work? 480 minutes is 8 hours which is 3 times a day.

Board footer

Forum Software