| Summary: | printer Epson EPL-6100L is configured and installed, but does not print. | ||
|---|---|---|---|
| Product: | Mageia | Reporter: | Norbert Zeranski <n.zeranski> |
| Component: | Installer | Assignee: | All Packagers <pkg-bugs> |
| Status: | NEW --- | QA Contact: | |
| Severity: | major | ||
| Priority: | Normal | CC: | ouaurelien |
| Version: | 8 | ||
| Target Milestone: | --- | ||
| Hardware: | All | ||
| OS: | Linux | ||
| Whiteboard: | |||
| Source RPM: | CVE: | ||
| Status comment: | |||
| Attachments: | test on 13-03-2021 | ||
|
Description
Norbert Zeranski
2021-03-11 13:35:24 CET
Sorry for your trouble.
Can you please say how you installed Mageia (which ISO). And post the O/P of:
$ inxi -Sxx
and say how the printer is connected.
This looks as if CUPS is not running. First check with Mageia Control Centre-System-Manage System Services-Manage System Services, and confirm that cups is running and ticked to start (at startup).
Also do:
$ systemctl status cups
Mine shows (for comparison):
● cups.service - CUPS Scheduler
Loaded: loaded (/usr/lib/systemd/system/cups.service; enabled; vendor pres>
Drop-In: /usr/lib/systemd/system/cups.service.d
└─server.conf
Active: active (running) since Thu 2021-03-11 15:39:15 CET; 4h 49min ago
TriggeredBy: ● cups.socket
● cups.path
Docs: man:cupsd(8)
Main PID: 1308 (cupsd)
Status: "Scheduler is running..."
Tasks: 2 (limit: 4355)
Memory: 3.7M
CPU: 123ms
CGroup: /system.slice/cups.service
└─1308 /usr/sbin/cupsd -l
Maw 11 15:39:14 localhost.localdomain systemd[1]: Starting CUPS Scheduler...
Maw 11 15:39:14 localhost.localdomain cupsd[1308]: Missing value on line 59 of >
Maw 11 15:39:15 localhost.localdomain systemd[1]: Started CUPS Scheduler.
If it is not running, try:
$ systemctl start cups [it will ask for a password]
and initiate another print request.
If the blockage persistes, try turning OFF and ON the printer.
Was the printer switched on before you booted? Or did you turn it on afterwards? I ask because there was an old bug when the system did not always recognise a printer already turned on at boot; but that was eventually fixed.
Did you install the printer immediately after re-booting after installation? Or after some normal system usage and re-boots? Does this blockage happen for anything you try to print? You can delete blocked items from the print queue before initiating another print request.CC:
(none) =>
lewyssmith, ouaurelien Hi, the printer EPSON EPL-6100L is connected via USB. The Mageia 8.0 is downloaded from CHIP in March 2021. So far I can see, CUPS is running the printer was turned on, when Mageia was active the printer was installed immediately after re-booting after installation situation, printer is not printing (In reply to Norbert Zeranski from comment #2) > the printer EPSON EPL-6100L is connected via USB. The Mageia 8.0 is > downloaded from CHIP in March 2021. > So far I can see, CUPS is running > the printer was turned on, when Mageia was active > the printer was installed immediately after re-booting after installation > situation, printer is not printing Thank you for this information. To indicate your system details, please post the ouptut of: $ inxi -Sxx Just to try poking the affair harder, with a blocked queued print request, can you see whether: $ systemctl stop cups $ systemctl start cups does anything? And as a last more extreme test: in Print Settings (or MCC-Hardware-Configure printing & scanning), *remove* then *re-install* the printer. This does not take long. Created attachment 12458 [details]
test on 13-03-2021
Hi,
following my system details:
sysman@localhost Dokumente]$ inxi -Sxx
System:
Host: localhost Kernel: 5.10.16-desktop-1.mga8 x86_64 bits: 64
compiler: gcc v: 10.2.1 Desktop: GNOME 3.38.3 tk: GTK 3.24.24
wm: gnome-shell dm: GDM Distro: Mageia 8 mga8
[sysman@localhost Dokumente
I do not know, how I can bring the information in a better version.
The commands for "stop cups" and "start cups" give no changes to system and printer.
"removing" and "re-install" of the printer does not change the situation, the printer is not printing.
By installing the printer a lot of drivers are given, I took the driver which was proposed by Mageia.
Sorry !
Thank for trying all the things asked of you. Assigning this bug gobally to solicit greater wisdom. Assignee:
bugsquad =>
pkg-bugs |