You are not logged in.
The new versions of Miyo-i3 are now available. I've made a few improvements over the last release of Miyo-i3...I think. LOLOLOLOLOL!!!
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...
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.
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 \
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...
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.
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!
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.
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!
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!
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! 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)
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!
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!
Edited to add...
It's almost time for the cron job to run...I'll reboot and double-check. I'll report back.
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.
Sorry...I've been busy with the latest i3 releases. Hope to have them uploaded to Sourceforge tomorrow (Feb. 16).
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
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...
Thank you.
Well...I don't mind the cron job running. LOL!
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...
@miyo:
In beowulf, /lib/live/mount has changed to /run/live/medium
Okay...thank you.
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.
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...
Wonderful! You always make me smile.
Well...not to toot my own horn, but I am a smiley kind'a guy...
LOLOLOLOLOLOLOL!!!
Quick preview of the upcoming Miyo-i3...
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
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...
What if 30 was changed to 480? Would that work? 480 minutes is 8 hours which is 3 times a day.
I don't mean to distract the topic...but-
Hello Miyo & fsmithred!Kinda long-time, no type.. lol
back on topic (for now..hee hee hee)...
I'm getting nowhere with the dec mini and miyo asked:MiyoLinux wrote:a pure Beowulf build to test it on...
that's - "not" an ascii upgraded?
I'll try the mini iso on other laptop, soon. Other tower isn't unpacked yet
asta folks~~!
stanz! Man, it's good to hear from you! Hope you've been well!
You're correct...I was referring to a pure beowulf system rather than an upgrade from ASCII to beowulf.
Take care friend!
MiyoLinux Thanks again - edited the script. Works just fine.
Thanks geki!
Sorry I wasn't clear. It's doing just what you said it would do, before and after the edits.
Now I want to learn python so I can modify it. What's the python equivalent of notify-send "$check" and how do you make that run when you click on the icon? That would show the list of packages to be upgraded for a few seconds - long enough to know whether you want to bother opening synaptic (or a root terminal) or rather leave it until later.
Sounds like a great idea, and I wish I knew the answer fsr. Sorry.
I have noticed I am receiving "mail" with logs from this script in /var/mail/<myusername>. I am not sure if it is caused by the script or otherwise, but I would like it to stop. XD Any ideas?
Hmmm...I'm not getting any mail from the script. The only difference that I can think of is that I'm using i3 on ascii, I've only received one set of small updates since implementing the script, and I'm using the updated script in which I removed SEVERAL of the things that are probably still on yours. Here's what my current update-notifier.py looks like...
#!/usr/bin/env python
"""
pyupdatesd: A simple yum update checker.
This script will watch for available yum updates and show a Gtk2 tray icon and
notification pop-up when updates become available.
This is intended for desktop environments like XFCE that don't have a native
PackageKit update watcher.
Set this script to run on session startup, and it will check for updates every
4 hours (by default; this is configurable in the source code).
This software is open domain and may be freely modified and distributed.
Requires: pygtk2
--Kirsle
http://sh.kirsle.net
"""
################################################################################
# Configuration Section Begins Here #
################################################################################
c = dict(
# The title to be shown on the pop-up and the icon tooltip.
title = "Updates Available",
# The message to be shown in the pop-up.
message = "There are updates available to install.",
# Icon to use in the system tray and pop-up.
icon = "/usr/share/update-notifier/updates.svg",
# Frequency to check for available updates.
interval = 14400, # 4 hours
# Command to run to check for available updates, and the expected status
# code that indicates updates are available.
check = "/usr/bin/apt-get -s dist-upgrade | /bin/grep -c '^Inst '",
# Path to notify-send (set to None if you don't want notifications)
notify = "/usr/bin/notify-send",
)
################################################################################
# Configuration Section Ends Here #
################################################################################
import gtk
import gobject
import commands
import subprocess
from time import time
def onClick(widget):
"""Event handler for the tray icon being clicked."""
widget.set_visible(False)
gobject.timeout_add(1, self.destroy)
def show_notify():
subprocess.call([c['notify'],
'-a', __name__,
'-i', c['icon'],
c['title'],
c['message'],
])
tray = gtk.StatusIcon()
tray.set_from_file(c['icon'])
tray.set_title(c['title'])
tray.set_tooltip(c['title'])
tray.set_visible(False)
tray.connect('activate', onClick)
next_check = int(time()) + c['interval']
def main_loop():
# Time to check?
global next_check
if int(time()) >= next_check:
status = commands.getoutput(c['check'])
# Updates?
if status != "0":
tray.set_visible(True)
show_notify()
elif tray.get_visible() == True and status == "0":
# Updates have disappeared behind our back!
tray.set_visible(False)
next_check = int(time()) + c['interval']
gobject.timeout_add(1000, main_loop)
gobject.timeout_add(1000, main_loop)
gtk.main()
# vim:expandtab
One thing I noticed is that if I use the script straight away with my interval of 14400, it doesn't seem to work. I had to change it back to the interval of 900 (well, I actually used 100 to test it). Logged out and back in, and it worked. So then I changed it to the 14400, logged out and back in, and it notified me 4 hours later like it should.
I installed from your first zip. I saw the icon and clicked on it, but it just disappeared. Made the changes you suggested and I'm waiting to see that icon again. Anyway, I have a question and a comment.
How/where is 'apt-get update' happening?
This code won't work with a devuan-live (or with most debian-live derivatives):
# Do not run in a LiveCD session import os.path import sys if os.path.exists('/etc/pointlinux-installer/install.conf'): print "Can't run in a LiveCD session!" sys.exit()
This would probably work better:
# Do not run in a LiveCD session import os.path import sys if os.path.exists('/lib/live/mount/medium'): print "Can't run in a LiveCD session!" sys.exit()
Note: It will still work in a live session with persistence, because in that case, the path would be '/lib/live/mount/persistence'. If you used '/lib/live/mount' in the code, that would keep it from working in both cases (with or without persistence.)
fsr,
The icon disappearing is all that was supposed to happen. I wanted it to simply notify that updates are available, and leave it up to me to install them manually. On the original Point Linux Update Notifier, clicking on the icon in the system tray would open Synaptic and install updates (if you clicked to mark them).
Did you make the changes after you clicked on the icon? Did you logout/login or reboot after you made the changes?
If you clicked on the icon before making the changes, it killed the whole process, so it wouldn't run again until a logout or reboot.
That section of code that you pointed out is actually part of what I removed in the second version. However, I've temporarily taken the download link down while I investigate a couple of things.
Okay, I've made a new zip file. I've also cut out some of the code in the update-notifier.py to avoid possible confusion by those who may look at it. I rewrote the instructions and also set the notifier to check for updates every 2 hours instead of the default 15 minutes.
I went back and edited the post where I presented it with the new instructions and provided the new download link there too.
If you've already installed it, you don't have to use the newer one.
OK, thanks! Indeed, I would make it a bit less frequently... :-)
Okay...open the update-notifier.py as root with your text editor...
If line numbers are enabled, it's line 38, and looks like this...
interval = 900, # 15 minutes
The interval is in seconds.
60 seconds x 15 minutes = 900 seconds
So we have to figure out how many seconds are in the time interval that we want to use. I change mine to check every 4 hours. So to turn that into seconds, I do...
60 seconds x 60 minutes x 4 hours = 14400 seconds
So I would edit that line with my desired amount of seconds...
interval = 14400, # 4 hours
Adjust to your desired time frame.
VERY IMPORTANT!!! DO NOT PUT A COMMA INSIDE THE NUMBER THAT YOU COME UP WITH. In other words (using my example), don't write the number as 14,400 (with a comma). It needs to be 14400 (without a comma). BUT DO LEAVE THE COMMA AFTER THE NUMBER THAT YOU USE.
All right, it seems to work as expected. :-) It notified me of upgrades a minute ago, and I am upgrading just now.
Hooray! Thanks for testing it franko...and the feedback!
Make sure to make that change in the update-notifier.py so the notifier will continue monitoring after closing the system tray icon. I'm planning to make a new zip file later with that change and edit the instructions with how to change how often it checks for updates. As it is, it checks every 15 minutes.
Dual monitors is something I've never dealt with, so I may not have an answer. These are just guesses. If someone else has an answer, feel free to supply it.
Does xrandr show the other monitor?
Does running that command in the terminal work?
If so, have you tried putting the desktop application that you created in /etc/xdg/autostart ?
What about creating a script; such as...
!#/bin/sh
sc -c `xrandr --output VGA1 --mode 1600x900 --rate 60.00 --same-as LVDS1 --output LVDS1 --off`
...Mark it as executable, and place it in /usr/bin/ (as an example).
Then try adding the script to ~/.config/openbox/autostart
As an example, I'll use "external-monitor" as the name of the script, and it was placed in /usr/bin/.
/usr/bin/external-monitor &
Sure thing geki.
Also, I've improved it already.
I figured out how to close the system tray notification icon without killing the notifier. In other words, clicking the system tray icon will still close it, but the notifier continues to check for updates. That's much better for those on beowulf. ...'cause updates are a'comin'!
If you want to make that change, open the update-notifier.py with your text editor as root. I'll use leafpad as the example, but substitute leafpad with your preferred editor.
sudo leafpad /usr/share/update-notifier/update-notifier.py
If you enable line numbers, scroll down to line 76. It presently looks like this...
gobject.timeout_add(1, exit)
Change it to this...
gobject.timeout_add(1, self.destroy)
Save the file, and close it. Then reboot for it to take effect.
Well...as I said, I know it would be a pain, but for the situation that you described, that's the only solution that I could think of off of the top of my head. I know (from past conversations) that you're aware that Miyo doesn't come with a browser pre-installed. That's the whole ideology behind Miyo..."make it your own"...let the user decide what goes on their system...which means the browser too.
I realize that periodically, there will be situations like you've described, so I apologize if things didn't work out like you hoped, but thank you anyway.