Yes, I did try that. I just tried creating a printer profile with a different
driver (I was using hplip, which seems to make sense and it's what I've
always used), but that didn't change anything.
I am facing the same issue with that I am also getting Epson Printer Error
Code 0x9d and I also tried to contact
https://errorcode0x.com/fix-epson-printer-error-code-0x9d/ but did not get
the valid solution from there. Can I get any suggestion?
Dunno myself, but you probably know more about hardware than me so yeah.
As I wrote, my bet is on a defective RAM stick. The log sometimes contains
sequences of unprintable characters right before the crashes occur. Besides
that (and hyperion's 'killall' every second), everything looks OK in the log.
That is curious. Have you tried "removing" the printer and "adding" it
again? You can try different drivers if several are proposed.
As much as I dislike systemd and its questionable ways, I somehow doubt it
would work incorrectly like the way you mentioned. All you have to do to know
that I dislike systemd is do a search in my history on here.
That aside, I use trisquel 8 on my kororapenguin and it works fine even with
systemd stuff aside, what do you think his problem is via the log he
attached? just curious.
Which printer model are you using?
After each crash, I would peruse the syslog only to find
indicator-application-service acting up for several lines just before each
crash, saying something about how there was already an instance running.
"indicator" does not occur in the syslog you attached.
Come to think of it, the RAM
Hi,
I already asked about this at the GnuPG users mailing list [0], but as I did
not get a solution, I am trying here.
I have two Trisquel 8 computers syncing their ~/.gnupg directories.
"alice" is my username in one computer, "bob" is my username in the other
one.
I have a CA
10 matches
Mail list logo