Having just made the move onto 64-bit Plasma Mageia-7, I have encountered
an unexpected reluctance for its Okular 1.7.0 to provide an option to
'Print' a .pdf file (Only option shown is 'Print to file'.)
try running system-config-printer to start the service etc.
On Sun, 11 Aug 2019 14:51:17 -0400, David W. Hodgins wrote:
try running system-config-printer to start the service etc.
That didn't work; complained of missing functions.
But then tried the 'HP Device Manager' (as root) and it printed a test
copy and afterwards Okular was able to find the printer.
Regards,
What brand is your printer? Sounds like an HP. My wife's tablet is an
HP, and runs more slowly than a 100 year old PC.
I wonder if the hardware detection in 7 is not as good as in 6.
printer.
Having just made the move onto 64-bit Plasma Mageia-7, I have encountered
an unexpected reluctance for its Okular 1.7.0 to provide an option to
'Print' a .pdf file (Only option shown is 'Print to file'.)
However, if I present the same PDF file to Mga6.1's Okular, it happily
prints it.
What have I omitted to do?!
On 8/11/19 1:47 PM, Maurice wrote:
Having just made the move onto 64-bit Plasma Mageia-7, I have encounteredYou haven't omitted anything. See https://bugs.mageia.org/show_bug.cgi?id=24189
an unexpected reluctance for its Okular 1.7.0 to provide an option to
'Print' a .pdf file (Only option shown is 'Print to file'.)
However, if I present the same PDF file to Mga6.1's Okular, it happily
prints it.
What have I omitted to do?!
It's a bug in Mageia 7, in that cups services fail to start on some hardware, due to what appears to be a race condition. As it doesn't
affect all hardware, it must be rather illusive.
At the moment, the only workaround seems to be to start the cups
services manually. For those who, like me, prefer GUIs over the command line, this can be done with MCC/System/Manage system services by
enabling or disabling them.
There is one other solution, not favored by most as it is rather drastic
and probably unreliable. The problem went away for me after a major
system hardware change/upgrade.
TJ
On 2019-08-14, TJ <TJ@noneofyour.business> wrote:
On 8/11/19 1:47 PM, Maurice wrote:
Having just made the move onto 64-bit Plasma Mageia-7, I have encountered >>> an unexpected reluctance for its Okular 1.7.0 to provide an option toYou haven't omitted anything. See
'Print' a .pdf file (Only option shown is 'Print to file'.)
However, if I present the same PDF file to Mga6.1's Okular, it happily
prints it.
What have I omitted to do?!
https://bugs.mageia.org/show_bug.cgi?id=24189
It's a bug in Mageia 7, in that cups services fail to start on some
hardware, due to what appears to be a race condition. As it doesn't
affect all hardware, it must be rather illusive.
At the moment, the only workaround seems to be to start the cups
services manually. For those who, like me, prefer GUIs over the command
line, this can be done with MCC/System/Manage system services by
enabling or disabling them.
There is one other solution, not favored by most as it is rather drastic
and probably unreliable. The problem went away for me after a major
system hardware change/upgrade.
The other solution is to restart the various cups programs after boot
and then just leave the computer running for months or years.
Of course that might be hard on a laptop.
You could also try putting a cups restart into /etc/rc.d/rc.local. That starts up more of less last on the startup programs which might be late enough that the bug is no longer operative. (Note that cupsd runs, but cups-browsed, and cups.socket and cups.path which give failures -bliss
TJ
then tried the 'HP Device Manager' (as root) and it printed a test copy
and afterwards Okular was able to find the printer.
On Mon, 12 Aug 2019 07:50:52 +0000, I wrote:
then tried the 'HP Device Manager' (as root) and it printed a test copy
and afterwards Okular was able to find the printer.
And all was fine last weekend, but today returning to base I find that
Mga7
cannot print at all! system-config-printer et al can FIND the printer
(HP Photosmart 5520) but 'cannot find PPD file', so absolutely stymied...
HP Device Manager says "No installed HP devices found'.
If I go to its "Setup Device" it shows the precise printer name, but
the
'PPD file' line says (with yellow hiliting) "(Not found..>" and if I
broswe
its list of PPD files and select the correct one, if I hit Next it just reverts to the previous window "PPD not found"! (The file is there in /usr/share/ppd/hp...)
Similar impasse if 'CUPS interface' selected, and also get nowhere with system-config-printer.
Just done s/w update on Mga7 but no change. *Can no longer print*!!!
Can only print if revert to Mga6.1. This is seriously WEIRD.
Suggestions very welcome :-(
*Can no longer print*!!!
Seems to have been a hiccup with CUPS
See
https://bugs.mageia.org/show_bug.cgi?id=24189
It's a bug in Mageia 7, in that cups services fail to start on some hardware,
On Thu, 15 Aug 2019 16:51:36 +0000, I wrote:
*Can no longer print*!!!
Seems to have been a hiccup with CUPS. Have just done:
# service cups start
cups.service - CUPS Scheduler
Loaded: loaded (/usr/lib/systemd/system/cups.service; enabled; vendor preset: disabled)
Active: active (running) since Thu 2019-08-15 18:23:22 BST; 22s ago
Docs: man:cupsd(8)
Main PID: 12000 (cupsd)
Status: "Scheduler is running..."
Memory: 1.8M CGroup: /system.slice/cups.service
└─12000 /usr/sbin/cupsd -l
Aug 15 18:23:22 pc18.mab.test systemd[1]: Starting CUPS Scheduler...
Aug 15 18:23:22 pc18.mab.test cupsd[12000]: CreateProfile failed:
org.freedesktop.DBus.Error.ServiceUnknown:The name
org.freedesktop.ColorManager was not>
Aug 15 18:23:22 pc18.mab.test cupsd[12000]: CreateProfile failed:
org.freedesktop.DBus.Error.ServiceUnknown:The name
org.freedesktop.ColorManager was not>
Aug 15 18:23:22 pc18.mab.test cupsd[12000]: CreateDevice failed:
org.freedesktop.DBus.Error.ServiceUnknown:The name
org.freedesktop.ColorManager was not >
Aug 15 18:23:22 pc18.mab.test systemd[1]: Started CUPS Scheduler.
lines 1
and all of a sudden printing works again...
Wonder what's gpoing on about CUPS...
On Thu, 15 Aug 2019 17:33:20 +0000, I wrote:
Seems to have been a hiccup with CUPS
As TJ reported earlier in here:
See
https://bugs.mageia.org/show_bug.cgi?id=24189
It's a bug in Mageia 7, in that cups services fail to start on some
hardware,
But I didn't see it when checking out the pre-reldease Mga7 on same hardware, so I suspect some subsequent change for the worse...
Is there a simple way of restarting CUPS automatically at power-up?
There are a couple of bugs for CUPS. https://bugs.mageia.org/show_bug.cgi?id=24189 deals mainly with Cauldron
but seems to affect Mageia 7 in some instances as well. A manual restart appears to get things working in some cases.
Try putting systemctl restart cups into /etc/rc.d/rc.local....
| Sysop: | Keyop |
|---|---|
| Location: | Huddersfield, West Yorkshire, UK |
| Users: | 296 |
| Nodes: | 16 (2 / 14) |
| Uptime: | 42:15:43 |
| Calls: | 6,648 |
| Files: | 12,193 |
| Messages: | 5,329,573 |