Install gutenprint ubuntu9/3/2023 ![]() Happy me.īut there’s a real question here, behind : after first initial 20.04→22.04 upgrade attempt I was already surprised I had to « reconfigure » my network. I backup’ed hidden elements of my $HOME visible data are safe elsewhere.īut work context where doing 3~4 things in the same time made me later forget « how » I did that backup and I deleted it while doing something else totally unrelated. Remember, I do all these on a production machine at work, such a good idea of mine, lol. 13⋅× if remembered correctly ) and… exactly same complain about libc version. Ok let’s try to boot an older kernel ( a 5. 15.0-46 kernel ! I must have done something wrong with Timeshift. Now looking closer at the installed kernels : my ( now ) downgraded 20.04 ( from 22.04 using Timeshift ) is actually running a 5. Then I noticed I had no network at all, no way to enable it anywhere, nmcli complaining about being unable to do something with netplan.ĭigging a bit in dmesg and other places I found netplan expected some version of libc ( ≥ 2.34 ).Īnd indeed, on a 20.04 glibc is 2.31 not 2.34. I’m here on a 22.04 « upgraded » some days ago from 20.04.Īll seemed to go well, rebooted fine at first sight. The long story : actually I was not so incautious and I had some Timeshift snapshots, therefore I decided to « roll back in time » to a 3 weeks old snapshots. I still have a working 22.04 installation beside where I’ll try to figure out how to « fix » the B&W issue. Ok, I ended up screwing everything, leading to a plain re-installation of UBudgie 20.04 where printer works as expected. $ lpoptions -p colorprintertest -l | grep ColorModel ![]() The printer thinks it is BW by default, too: How does it get there, and why monochrome, if the PPD is CMYK by default? I see option `Option print-color-mode monochrome` is at the bottom for no apparent reason. # DO NOT EDIT THIS FILE WHEN CUPSD IS RUNNING # Printer configuration file for CUPS v2.4.2 Look into /etc/cups/nf for the current printer options: $ grep DefaultColorModel /etc/cups/ppd/colorprintertest.ppdĢ. Make sure its DefaultColorModel was CMYK from the start: Sudo lpadmin -p colorprintertest -E -m openprinting-ppds:0/ppd/openprinting/Ricoh/PS/Ricoh-MP_C3004_PS.ppd -v socket://printerĢ. ![]() Create a new printer using a PPD that has `DefaultColorModel: CMYK`: So one of my problems sits in the upgraded system only ( and not on the plainly installed one ).Īnyway I need that printer and its colors - it’s a terrible bug.ĭebian testing/bookworm, CUPS 2.4.2-1, cups-filters 1.28.15-1+build1. ![]() I wonder : what are my best chances to reinstall 22.04 while keeping $HOMEs ?īecause when I try the same thing from the other installed system, it works as you describe ( but unable to print in colors, only B&W whatever set in printer driver. Plus some errors regarding nouveau driver, nothing new. In red : août 23 15:08:26 PROLIANT python3: io/hpmud/jd.c 772: invalid hostĪoût 23 15:08:26 PROLIANT python3: io/hpmud/jd.c 731: invalid ipĪoût 23 15:08:26 PROLIANT hp-makeuri: hp-makeuri: error: Device not foundĪoût 23 15:08:39 PROLIANT python3: io/hpmud/jd.c 94: unable to read device-idĪoût 23 15:08:39 PROLIANT python3: io/hpmud/jd.c 746: invalid ip 192.168.92.185Īoût 23 15:08:39 PROLIANT hp-makeuri: hp-makeuri: error: Device not foundĪoût 23 21:15:23 PROLIANT systemd: rvice: Failed with result 'exit-code'.Īoût 23 21:15:23 PROLIANT systemd: Failed to start Refresh fwupd metadata and update motd.
0 Comments
Leave a Reply.AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |