You are not logged in.
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.ogg
But 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?
Only a Mate file is in there. Any other ideas?
MiyoLinux wrote:
Yes, change those lines so that they look like this...default_user ron # Set to "yes" to enable this feature focus_password yes
Great. This worked! But still have the very long login time. Is there anything I can check or do about it to help?
Thanks MiyoLinux. Your fix for sudo worked. Also your login screen workaround also worked. But I would really like to just be prompted for my password. I noticed in slim.conf these 3 lines:
#default_user miyo
# Set to "yes" to enable this feature
#focus_password no
If I change miyo to ron and change no to yes, would that get me what I want?
Also, I made a mistake saying boot time. I meant login time. From the time I enter my password and hit enter, it takes 27 seconds to log in. However, I notice that if I giggle the mouse while I'm waiting that that speeds up the login.
Also I should mention that I installed the Mate desktop and uninstalled openbox, all things Xfce, and the other thing I can't remember, I think it ends in "fm." I did the same thing in Jessie and had no problems.
Just installed the new release (along side of Jessie and Mint). I'm having a couple of problems. The first thing is that boot time is way slow compared to Jessie's boot time. The other problem (to me it is a problem) is the login screen. Unlike Jessie where my user name is already selected, and I only have to type in my password, Ascii requires me to type in my user name, and then my password. I know this may seem trivial, but before I tried Miyo I tried two other distros that behaved the same; not having to type in my user name for login was a very big reason I went with Miyo. (It seems superfluous to have to type it in when there's only one user account.)
Another problem I don't think has to do with Ascii is that I'm trying to run Pale Moon's browser installer script and when it asks me for my password I get an error message. It says make sure this user has sudo rights, or something like that. My password works for Synaptic so I don't know why it doesn't work for this.
MiyoLinux wrote:
Then I'd recommend putting the # back on the backports repo.
I can't remember if I put them back. Should it look like this:
# jessie-backports
#deb http://auto.mirror.devuan.org/merged jessie-backports main
#deb-src http://auto.mirror.devuan.org/merged jessie-backports main
or just this:
# jessie-backports
deb http://auto.mirror.devuan.org/merged jessie-backports main
deb-src http://auto.mirror.devuan.org/merged jessie-backports main
Another question, if I disable the backports then won't I not be offered an update on the new kernel when one is released?
Thanks guys. I marked as solved.
2. I really want to know why your anacrontab doesn't read:
1 8 automatic.trim /sbin/fstrim --all || true
Also, what's the rationale behind keeping the " || true" statement?
You mean I really don't even need the trim script file?
As for the || true, I have no idea. I kept the file exactly the same as it was in Mint. Also, thanks for the tip in #1, and your link in your previous post.
And before I forget, many thanks to both siva and GNUser. I'm getting closer to ditching Mint and going with Miyo full-time.
Okay, I think it's finally working in a way I can understand. First, I delete the trim file out of the /etc/cron.daily folder (and kept the one in my Documents folder). Then I went back to the anacron file in /etc and added this:
1 8 automatic.trim /bin/bash /home/ron/Documents/trim
I changed 10 minutes to 8 and using your suggestion named it automatic.trim. Rebooted and ran sudo cat /var/log/syslog | grep anacron and got this on one line:
May 1 19:06:28 localhost anacron[1661]: Will run job `automatic.trim' in 8 min.
Finally, checked that the log file automatic.trim exists, opened it up and found this: 20180501.
So, can I finally consider this as SOLVED?
Okay, one thing I just realized in looking at the anacrontab file in /etc. There is the following line:
1 5 cron.daily run-parts --report /etc/cron.daily
I had previously put the script trim in /etc/cron.daily (and it's still there) so does that mean that trim ran?
I just finished all the steps you gave me. It appears to have worked but I have one question. When I ran sudo cat /var/log/syslog | grep anacron I got this:
May 1 18:09:38 localhost anacron[1659]: Anacron 2.3 started on 2018-05-01
May 1 18:09:38 localhost anacron[1659]: Will run job `cron.daily' in 5 min.
May 1 18:09:38 localhost anacron[1659]: Will run job `cron.weekly' in 10 min.
May 1 18:09:38 localhost anacron[1659]: Will run job `cron.monthly' in 15 min.
May 1 18:09:38 localhost anacron[1659]: Jobs will be executed sequentially
Any idea why it says the daily cron will run in 5 minutes when it's set for 10?
EDIT: I think I know what happened. After installing anacron, I should have went back to re-add the line
1 10 example.daily /bin/bash /home/ron/Documents/trim. I'm going back to add it again and retry everything. It should work this time!
GNUser wrote:
Would you kindly share the contents of that file?
#!/bin/sh
# trim all mounted file systems which support it
/sbin/fstrim --all || true
siva wrote:
A) which program
B) find / -iname *program*
which anacron returned nothing while almost every line from find / -iname anacron ended with Permission denied.
siva wrote:
To reiterate, I'm not sure why you're pointing cron to a script that runs a simple command. I would use a script if there were a series of lines.
If I had to do it manually, I'd probably forget about it. One thing I'm wondering about, can I turn this script into an .sh file that will run when I click on it?
Okay, I think I got a handle on this. I added the following line to /etc/anacrontab:
@daily 10 example.daily /bin/bash /home/ron/Documents/trim
and made sure I copied the trim script into my Documents folder. Is that all there is to it? Once again, thanks for helping.
FTR, I'm just an average desktop user that regularly powers off (no hibernation/suspend).
EDIT: I just checked out the link in GNUser's post, and I don't have an anacron file in /usr/sbin, just a link. Does that mean anacron isn't working?