Linux - NewbieThis Linux forum is for members that are new to Linux.
Just starting out and have a question?
If it is not in the man pages or the how-to's this is the place!
Notices
Welcome to LinuxQuestions.org, a friendly and active Linux Community.
You are currently viewing LQ as a guest. By joining our community you will have the ability to post topics, receive our newsletter, use the advanced search, subscribe to threads and access many other special features. Registration is quick, simple and absolutely free. Join our community today!
Note that registered members see fewer ads, and ContentLink is completely disabled once you log in.
If you have any problems with the registration process or your account login, please contact us. If you need to reset your password, click here.
Having a problem logging in? Please visit this page to clear all LQ-related cookies.
Get a virtual cloud desktop with the Linux distro that you want in less than five minutes with Shells! With over 10 pre-installed distros to choose from, the worry-free installation life is here! Whether you are a digital nomad or just looking for flexibility, Shells can put your Linux machine on the device that you want to use.
Exclusive for LQ members, get up to 45% off per month. Click here for more info.
Hi all,
My name is Harry and I am a Linux/Xubuntu User from The Netherlands.
Usually I Post my questions on the Dutch Ubuntu Forum but since they experienced a D-dos attack months ago, the experts are probably very busy getting the Forum completed to operate. Therefore I Post my Problem here.
I have a Cups problem with my Canon Pixma MG3255 and the Printer is connected by USB-wire to my desktop PC. Does scan (Simple Scan) with Xubuntu and works fine with Windows 7 on my laptop.
Also tried using GIMP to print an PDF file, I am not able to see the printer at all.
The first thing I've noticed is the Pop-up with: "CUPS-server Problem" and with "Failed to connect to server".
Is "/run/cups/cups.sock" to connect to the server the right Text?
A Dutch Forum Member suggested try "systemctl enable cups.service" but that doesn't work in the Terminal because it won't accept my Password (although it is correct and functional in Synaptic).
Hope you understand my (crappy) English and are able to help me with this.
The systemctl command you quote will start cups at boot time for the future. However the fact that you have a cups socket in /run suggests that cups is already running. You can check this by running the command ps aux|grep cups in a terminal. You should get two hits, one for grep and one for the cups daemon.
If cups is running, you can enter the interface in your browser (address localhost:631) and try to set up your printer from there.
The fact that you can't use your password in a terminal is also something that you need to fix pronto. Are you sure you have the Dutch character map set for both text terminals and the graphical interface?
There is no need to apologise for your English. We use English as a lingua franca here but a lot of us are not native speakers.
Used the terminal and this is what I got to see: harry@harry-desktop:~$ ps aux|grep cups
harry 2079 0.0 0.0 22012 1028 pts/0 S+ 19:51 0:00 grep --color=auto cups
localhost:631 : not able to connect
Using my password in the terminal does function unfortunate only not i.r.t. this Cups Problem
BTW I run Xubuntu 18.04LTS (usually this info is in my signature).
OK, cups is not running. That is shown by the fact that only the "grep cups" appears in your ps output and the cups browser interface is not accessible.
So you need to start cups and also to activate it permanently (those are two different things btw). That may possibly be all that's needed. The problem is how to do it, because you definitely need your password. So you must fix your terminal problem first.
You haven't said whether you are using a plain text console or a graphical one like gnome-terminal. That will make a difference if it is a mapping problem. Have you tried both? Do you have problems with (for example) punctuation marks in any graphical applications? I suggest you try with an editor like leafpad: type the letters, numbers and punctuation marks and see if any come out wrong. Then go to a linux virtual console and try there.
@sevendogsbsd: at the moment he can't use sudo because his terminal isn't accepting his password.
OK, cups is not running. That is shown by the fact that only the "grep cups" appears in your ps output and the cups browser interface is not accessible.
So you need to start cups and also to activate it permanently (those are two different things btw). That may possibly be all that's needed. The problem is how to do it, because you definitely need your password. So you must fix your terminal problem first.
You haven't said whether you are using a plain text console or a graphical one like gnome-terminal. That will make a difference if it is a mapping problem. Have you tried both? Do you have problems with (for example) punctuation marks in any graphical applications? I suggest you try with an editor like leafpad: type the letters, numbers and punctuation marks and see if any come out wrong. Then go to a linux virtual console and try there.
@sevendogsbsd: at the moment he can't use sudo because his terminal isn't accepting his password.
Leafpad: aAbbcC&*,;\`>~| no problems (imo)
linux virtual console: do not understand what it is or where to find it (sorry).
You can get a linux virtual console by pressing simultaneously ctrl+alt+F1. You will see a black screen with a login prompt. If you can log in there with your normal password, you can use sudo too. To get back to your desktop, use alt+F7.
Here's a trick to to test out your graphical console. Open it and enter your password directly in response to the command prompt. Since the system won't be expecting a password, it won't do anything to hide your input. That way you can tell immediately if the password you typed is received correctly.
You also have a real problem with cups: The logged output (well done for finding it!) shows that cups does start but then it crashes. That will have to be fixed separately. But you can't fix it until you can use sudo properly.
OK. To log in at a virtual console, you need to put your username in first. Then your password when prompted for it. If that works try using sudo systemctl cups start. We already know that cups will start and then crash. But if sudo gives you no errors, you have a way to fix anything. You need to try the same test on your graphical terminal too.
If sudo fails (and you know now that it's reading your password correctly), then you may have a sudoers file error. Did you edit that file lately?
Probably stupid but I do not know if I use a username to get in the system My machine starts without username etc.
When I MUST have it (always), is it to find anywhere?
Your screen capture shows that your username is harry (and not harry-desktop!). It looks like harry-desktop is the name of your machine. So you can log in and your password is accepted. Now can you use sudo on that console?
In the meantime I have done a bit of research. Synaptic doesn't use sudo to start up these days; it uses a different authentication program called pkexec. And you say that works for you. So if sudo really is screwed on your system, you should be able to use pkexec to fix things.
The cups error messages show that systemd is trying to repeatedly restart cups and probably doing it too quickly. So once you have got terminal sudo access back, the next thing to try will be to launch cups by hand and see if that works better.
Didn't work well therefore I tried it in Terminal.
This is the answer: harry@harry-desktop:~$ sudo systemctl start cups.service
Job for cups.service failed.
See "systemctl status cups.service" and "journalctl -xe" for details.
Code:
harry@harry-desktop:~$ systemctl status cups.service
● cups.service - CUPS Scheduler
Loaded: loaded (/lib/systemd/system/cups.service; enabled; vendor preset: ena
Active: failed (Result: start-limit-hit) since Wed 2018-11-07 22:03:52 CET; 2
Docs: man:cupsd(8)
Process: 18094 ExecStart=/usr/sbin/cupsd -l (code=killed, signal=TERM)
Main PID: 18094 (code=killed, signal=TERM)
nov 07 22:03:52 harry-desktop systemd[1]: cups.service: Service hold-off time ov
nov 07 22:03:52 harry-desktop systemd[1]: cups.service: Scheduled restart job, r
nov 07 22:03:52 harry-desktop systemd[1]: Stopped CUPS Scheduler.
nov 07 22:03:52 harry-desktop systemd[1]: cups.service: Start request repeated t
nov 07 22:03:52 harry-desktop systemd[1]: cups.service: Failed with result 'star
nov 07 22:03:52 harry-desktop systemd[1]: Failed to start CUPS Scheduler.
nov 07 22:03:59 harry-desktop systemd[1]: cups.service: Start request repeated t
nov 07 22:03:59 harry-desktop systemd[1]: cups.service: Failed with result 'star
nov 07 22:03:59 harry-desktop systemd[1]: Failed to start CUPS Scheduler.
lines 1-16/16 (END)
Code:
harry@harry-desktop:~$ journalctl -xe
nov 07 22:07:41 harry-desktop NetworkManager[613]: <info> [1541624861.4499] dhc
nov 07 22:07:41 harry-desktop NetworkManager[613]: <info> [1541624861.4499] dhc
nov 07 22:07:41 harry-desktop NetworkManager[613]: <info> [1541624861.4500] dhc
nov 07 22:07:41 harry-desktop NetworkManager[613]: <info> [1541624861.4500] dhc
nov 07 22:07:41 harry-desktop dbus-daemon[609]: [system] Activating via systemd:
nov 07 22:07:41 harry-desktop dhclient[1111]: bound to 192.168.178.108 -- renewa
nov 07 22:07:41 harry-desktop systemd[1]: Starting Network Manager Script Dispat
-- Subject: Unit NetworkManager-dispatcher.service has begun start-up
-- Defined-By: systemd
-- Support: http://www.ubuntu.com/support
--
-- Unit NetworkManager-dispatcher.service has begun starting up.
nov 07 22:07:41 harry-desktop dbus-daemon[609]: [system] Successfully activated
nov 07 22:07:41 harry-desktop systemd[1]: Started Network Manager Script Dispatc
-- Subject: Unit NetworkManager-dispatcher.service has finished start-up
-- Defined-By: systemd
-- Support: http://www.ubuntu.com/support
--
-- Unit NetworkManager-dispatcher.service has finished starting up.
--
-- The start-up result is RESULT.
nov 07 22:07:41 harry-desktop nm-dispatcher[18673]: req:1 'dhcp4-change' [enp2s0
nov 07 22:07:41 harry-desktop nm-dispatcher[18673]: req:1 'dhcp4-change' [enp2s0
lines 2814-2836/2836 (END)
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.
