You are not logged in.
Chromium: chromium/stable-security
APT-Sources: http://deb.devuan.org/merged chimaera-security/main amd64
Version 110.0.5481.177 (Official Build) built on Debian 11.6, running on Debian 11.1 (64-bit)
A desire to be able to explore the contents of Chromium's cache led me to try to fix my Wine installation. Assistance to fix either would be appreciated.
First a brief on how this started, then details on each problem.
15 Jan: I ordered a Braun 3040s shaver from Amazon for £55.99
18 Feb: whilst investigating the cost of Guide Combs for the 3040s I discovered that the then-current cost of a 3040s at Amazon was £1100
Today: re-checking the cost, the 3040s is £35
The above caused me to doubt #2 above. It seemed bizarre at the time, and now I doubted it totally. I knew that it would be stored within Chromium's history, but also knew that any attempt to access that history would replace the cache with the current page. How could I view the stored historic pages?
Exactly what I wanted was at EaseUS Chrome Cache Viewer as a free download, but with a big caveat: it was only available for Windows or Mac.
Wine was already installed on my Chimaera system, so I downloaded the EaseUS zip file & attempted to use wine to run it. Oh dear.
$ mkdir ChromeCache
$ cd ChromeCache
$ mv ~/Downloads/chromecacheview.zip ./
$ wine ChromeCacheView.exe -folder ~/.cache/chromium/Default/Cache
it looks like wine32 is missing, you should install it.
as root, please execute "apt-get install wine32"
it looks like wine32 is missing, you should install it.
as root, please execute "apt-get install wine32"
002b:err:module:__wine_process_init L"Z:\\home\\alexk\\Personal\\ChromeCache\\ChromeCacheView.exe" not supported on this system
It originally also told me to do # dpkg --add-architecture i386, and I cannot now reverse that instruction. My searching suggested that wine32 is now redundant since my amd64 system already contains provision for 32-bit wine. Are the suggestions above on installing wine32 now out-of-date?
My attempts to remedy the below may have it got me in deeper water, but here is the (seems to be misleading) original results:
$ sudo apt-get install wine32
[sudo] password for alexk:
Reading package lists... Done
Building dependency tree... Done
Reading state information... Done
Some packages could not be installed. This may mean that you have
requested an impossible situation or if you are using the unstable
distribution that some required packages have not yet been created
or been moved out of Incoming.
The following information may help to resolve the situation:
The following packages have unmet dependencies:
libcurl4:i386 : Depends: libldap-2.4-2:i386 (>= 2.4.7) but it is not going to be installed
libvkd3d1:i386 : Depends: libvulkan1:i386 (>= 1.1.70) but it is not going to be installed
libwine:i386 : Depends: libldap-2.4-2:i386 (>= 2.4.7) but it is not going to be installed
Recommends: libgl1:i386 but it is not installable
Recommends: libglu1-mesa:i386 but it is not installable or
libglu1:i386
Recommends: libsane1:i386 (>= 1.0.27) but it is not installable
Recommends: libvulkan1:i386 (>= 1.2.131.2) but it is not going to be installed
Recommends: libgl1-mesa-dri:i386 but it is not installable
E: Unable to correct problems, you have held broken packages.
I checked, and there are zero held packages.
Is anyone using WINE & knows how to escape these problems? Or, even better, does anyone know how to view or extract historic cache pages from Chromium?
2023-02-24: added Chromium version, etc.
Hi Andre, thanks for responding.
I'm not going to try your suggestions.
The printer was initially setup from brand-new, so is already at factory-defaults, never having been changed from those defaults.
CUPS requires printer-specific setup. CUPS itself is printer-agnostic & requires instructing on the specifics required for a specific printer; that is the purpose of the PPD text-files. The only way that your DCP-L2550DW could have been auto-setup without an external driver is if it used the CUPS-supplied ppd file. I've already confirmed that the CUPS-supplied driver for my model is identical to the Brother-supplied driver that does not perform. I'm not going through that all over again. But again, thanks for trying.
Extra: I see that your printer has an option for IPP Network Printer. That also uses the CUPS database, so may well have the same problem as the USB connection that I'm using. Ah, spit.
Hmm. Turns out that these are smartphones with Mediatek MT62xx / MT65xx / MT67xx Family chips (MTK chips) only. So, disregard my previous post.
I think that Android 5 was the last that let you do what you want to do, which essentially is to mount the Android 'disc' on a foreign machine. The only means of USB connection with Android 6 & higher is via MTP ('Media Transfer Protocol') which, essentially, is connection via modem. It thus prevents any mounting of the Android electronics on anything other than Android localhost.
Because of the above lsusb becomes ineffective.
The fix recommended at #6247 is:-
diff --git a/yt_dlp/extractor/youtube.py b/yt_dlp/extractor/youtube.py
index 95ca52b3a..4dde4bbaa 100644
--- a/yt_dlp/extractor/youtube.py
+++ b/yt_dlp/extractor/youtube.py
@@ -4120,7 +4120,7 @@ def is_bad_format(fmt):
'thumbnail': traverse_obj(original_thumbnails, (-1, 'url')),
'description': video_description,
'uploader': get_first(video_details, 'author'),
- 'uploader_id': self._search_regex(r'/(?:channel|user)/([^/?&#]+)', owner_profile_url, 'uploader id') if owner_profile_url else None,
+ 'uploader_id': self._search_regex(r'/(?:channel/|user/|(?=@))([^/?&#]+)', owner_profile_url, 'uploader id', default=None),
'uploader_url': owner_profile_url,
'channel_id': channel_id,
'channel_url': format_field(channel_id, None, 'https://www.youtube.com/channel/%s'),
I could not find the relevant code at line 4124, but did find it lower down higher up:
$ cd /usr/lib/python3/dist-packages/yt_dlp/extractor/
$ fgrep -n "'uploader_id': self._search_regex" youtube.py
4049: 'uploader_id': self._search_regex(r'/(?:channel|user)/([^/?&#]+)', owner_profile_url, 'uploader id') if owner_profile_url else None,
Since I have zero experience with either creating or using diff files, I decided on a short & dirty fix: edit it directly:
$ sudo cp youtube.py youtube.py.2023.01.06
$ sudo nano youtube.py
$ fgrep "'uploader_id': self._search_regex" youtube.py -B 1
# def is_bad_format(fmt):
# 'uploader_id': self._search_regex(r'/(?:channel|user)/([^/?&#]+)', owner_profile_url, 'uploader id') if owner_profile_url else None,
'uploader_id': self._search_regex(r'/(?:channel/|user/|(?=@))([^/?&#]+)', owner_profile_url, 'uploader id', default=None),
The above now works fine for me.
Starting (for me) yesterday the YouTube downloader yt-dlp gives the error:
ERROR: [youtube] 72FQIV-jpEk: Unable to extract uploader id;
please report this issue on https://github.com/yt-dlp/yt-dlp/issues?q= ,
filling out the appropriate issue template.
Looking at the GitHub site it has been fixed 5 days ago, and that fix is for this specific error:-
yt-dlp 2023.02.17
Latest
4 days ago
The version for Chimaera from Backports is considerably older:
$ apt search yt-dlp
Sorting... Done
Full Text Search... Done
yt-dlp/stable-backports,now 2023.01.06-1~bpo11+1 all [installed]
downloader of videos from YouTube and other sites
$ yt-dlp --version
2023.01.06
I was surprised to find at the GitHub site that CUPS has a dependency upon systemD. I'm not sure how Devuan handles that. I run SLiM myself.
$ 7z l Brother-DCP-L3510CDW-ppd.zip
7-Zip [64] 16.02 : Copyright (c) 1999-2016 Igor Pavlov : 2016-05-21
p7zip Version 16.02 (locale=en_GB.UTF-8,Utf16=on,HugeFiles=on,64 bits,4 CPUs AMD A8-7410 APU with AMD Radeon R5 Graphics (730F01),ASM,AES-NI)
Scanning the drive for archives:
1 file, 244572 bytes (239 KiB)
Listing archive: Brother-DCP-L3510CDW-ppd.zip
Date Time Attr Size Compressed Name
------------------- ----- ------------ ------------ ------------------------
2017-08-23 14:45:14 ..... 30733 6653 BRPPL3510CDW.ar.ppd
2017-08-23 14:45:08 ..... 31172 6734 BRPPL3510CDW.bg.ppd
2017-08-23 14:45:08 ..... 30823 6673 BRPPL3510CDW.cs.ppd
2017-08-23 14:45:10 ..... 30748 6661 BRPPL3510CDW.da.ppd
2017-08-23 14:45:10 ..... 30768 6681 BRPPL3510CDW.de.ppd
2017-08-23 14:45:08 ..... 30989 6649 BRPPL3510CDW.en-1.ppd
2017-08-23 14:45:10 ..... 30609 6617 BRPPL3510CDW.en-2.ppd
2017-08-23 14:45:14 ..... 30617 6617 BRPPL3510CDW.en-3.ppd
2017-08-23 14:45:12 ..... 31115 6711 BRPPL3510CDW.es.ppd
2017-08-23 14:45:10 ..... 30897 6685 BRPPL3510CDW.fi.ppd
2017-08-23 14:45:10 ..... 30958 6704 BRPPL3510CDW.fr-1.ppd
2017-08-23 14:45:10 ..... 30970 6707 BRPPL3510CDW.fr-2.ppd
2017-08-23 14:45:10 ..... 30878 6683 BRPPL3510CDW.hr.ppd
2017-08-23 14:45:10 ..... 31071 6740 BRPPL3510CDW.hu.ppd
2017-08-23 14:45:10 ..... 30804 6666 BRPPL3510CDW.id.ppd
2017-08-23 14:45:10 ..... 31011 6693 BRPPL3510CDW.it.ppd
2017-08-23 14:45:10 ..... 30431 6617 BRPPL3510CDW.ko.ppd
2017-08-23 14:45:12 ..... 31125 6723 BRPPL3510CDW.ls.ppd
2017-08-23 14:45:10 ..... 30761 6673 BRPPL3510CDW.nl.ppd
2017-08-23 14:45:12 ..... 30693 6651 BRPPL3510CDW.no.ppd
2017-08-23 14:45:12 ..... 31092 6767 BRPPL3510CDW.pl.ppd
2017-08-23 14:45:12 ..... 31118 6735 BRPPL3510CDW.pt-1.ppd
2017-08-23 14:45:12 ..... 31024 6709 BRPPL3510CDW.pt-2.ppd
2017-08-23 14:45:12 ..... 30962 6726 BRPPL3510CDW.ro.ppd
2017-08-23 14:45:12 ..... 31190 6760 BRPPL3510CDW.ru.ppd
2017-08-23 14:45:12 ..... 31043 6744 BRPPL3510CDW.sk.ppd
2017-08-23 14:45:16 ..... 31125 6723 BRPPL3510CDW.sl.ppd
2017-08-23 14:45:12 ..... 30971 6698 BRPPL3510CDW.sr.ppd
2017-08-23 14:45:12 ..... 30833 6684 BRPPL3510CDW.sv.ppd
2017-08-23 14:45:12 ..... 30679 6701 BRPPL3510CDW.th.ppd
2017-08-23 14:45:12 ..... 30849 6726 BRPPL3510CDW.tr.ppd
2017-08-23 14:45:14 ..... 31246 6791 BRPPL3510CDW.uk.ppd
2017-08-23 14:45:14 ..... 30828 6646 BRPPL3510CDW.vi.ppd
2017-08-23 14:45:08 ..... 30213 6521 BRPPL3510CDW.zh-cn.ppd
2017-08-23 14:45:08 ..... 30492 6558 BRPPL3510CDW.zh-tw.ppd
2019-07-03 13:53:57 ..... 26326 4497 DCPL3510CDW.original.ppd
------------------- ----- ------------ ------------ ------------------------
2019-07-03 13:53:57 1107164 238524 36 files
Puzzling this problem with the GitHub page it seemed to me that the problem was probably with ScriptSafe, which is a script-blocker that I use in Chromium to try to get ahead of problems with egregious scripts. So I returned to the GitHub page & watched ScriptSafe…
ScriptSafe == green on entry to the page
(I was also logged in)
ScriptSafe == one exception
(this was following a failed attempt to upload the zip-file)
(the failure was a new githubusercontent url)
ScriptSafe == green
(added clearance for that URL & the upload now worked & we have a download link for the zip)
I'll add the link into a fresh post to try to help make the link easier to find.
try the upload with a different browser
It's fully-updated Chromium. If that doesn't work then sod it.
I've now reported the issue to CUPS; see https://github.com/OpenPrinting/cups/issues/611
Unfortunately the upload-utility failed, so the zip of all the ppd variants remains on my disk lonely as a cloud.
It doesn't look like any ICC profile will do any good here. I may have run out of options to fix this model so that it will print colours OK. Bugger.
This link to cityinkexpress.co.uk will help explain what ICC Profiles are normally used by print shops to achieve.
In a nutshell, the biggest problem for a printshop is when a customer's home-produced printout on *their* printer looks lovely in their business/home, and all wrong from the Print Shop. So, City Ink Express provide a Colour Chart for the customer to printout using their printer. The customer then posts (or delivers) the printout back to the shop. City Ink Express have a piece of software ("advanced color calibration software") that scans the printout & produces an ICC Profile (software file) which is emailed back to the customer. The intention of the profile is to shift colour differences between the customer's printer & the commercial printer, so that (as much as possible) the commercial printout looks as close to the home printout as possible. The main issue for me is that no details of how that profile is used are revealed.
You can probably see why the above excited me re: my problem, and specifically because I had seen references to "Profile" whilst printing. Nope, wrong kind of Profile.
Brother has a Printing Profile, but you can tell from the link that it is nothing to do with shifting colour balances.
"ICC Profiles" feature exactly nowhere in brother.com. What *does* feature is "Windows ICM Profiles". That link states that these are provided on the driver CD at "x:\driver\ps\icm". Not on the CD for the DPL3510CDW they arn't. Yet another blind alley.
The final blind alley was me trawling through all the MSI files on the CD yet again, this time looking for "Profiles". Or even "ICC" or "ICM". Just in case. Nope. None. Nada.
I've also tried to find an address at which to report the Dead Fish that is the CUPS driver for the DPL3510CDW. I found a Reporting Issues information page. The one missing item was either an email address, a website page, a telephone number or even the location of a stone in a park to place the secret paper underneath. It seems like they don't want to know.
And with that final big NO I must leave this report.
Where's the NOT SOLVED button?
current Brother DCP-L3510CDW PPD is the default option for your printer.
It is the only option from CUPS for that model.
(re: ICC_Profile_Creator)
Well, that looks awesome (hurrah)
Ah, it is integrated into rawtherapee (boo)
But rawtherapee is open-source (hurrah)
The AppImage is 108 MB (boo)
Bugger. And I strongly suspect that the profile created is directly related to the screen (meaning, do colours from *any* program show accurately on the screen). I've already got & use a profile for that (and it isn't even a high-performance screen).
Still, no matter. That was a superb find. I now need to find whether the Profile-Maker can be installed independently of the entire program†, and whether that can be used for a printer. I'm also shortly going to trawl through the Brother win-drivers again looking for a profile. I also need to find the way to communicate to CURL (which I think is also openprinting.com) that their current Brother DCP-L3510CDW PPD is pants, and to offer the derived-from-windows collection (69 separate files‡).
† Feb 6 update: I did check & the GitHub site shows a single file to create the utility. However, it is thoroughly integrated into the whole program, with dozens of calls to other sections
‡ Feb 6 update: 35 PPD files after removing dupes
Thanks for the link, Altoid.
I'm well used to Pantones (although did not get my hands dirty with them other than with a University where the logo was specified in Pantone colours; a very good way to send print costs sky-rocketing). I used to deal with a print-house, talking often with the guys that got ink on their fingers. Also working at a furniture company that used a commercial printer to print Sales & Product sheets for mail-order (I was using a Mac with early DTP software that were then sent to the Printer; he was dubious because this was the late 1980s, but we got good results).
So all-in-all I'm up to speed with the issues. And the main issue seems to be the need to have an ICC profile to cover RGB-to-CYMK issues, and iirc I recall that being buggy with (I think) Ghostscript, and I still have not heard of any fixes for that, nor of a Profile supplied with Brother printers. However, HP manage to print correctly, so it can be done.
This talk of "punching up the colours" is missing the point. I'm not going to be using any more than 4 inks, and 600 dpi is twice what I'm used to and better than a cheap HP DeskJet. The point here is that the Brother is printing the wrong colours. I produced some sheets with a large, standard range of HTML colours (specified in 6 hex digits so that they could be checked back) & they were all printed wrong.
any problem CUPS may have with a specific printer lies in the structure of the PPD and/or colour profile files
I certainly agree with the (non-existent) Profile file as being a likely source for the problem. That was my early suss when first trying to fix this beast. The fact that there is less problems with the CMYK driver than the RGB driver points in the same direction (as far as I understand these things). However, how do I get such a file? I managed to get one for my monitor from an old Windows driver, but that was a Monocoque, so there was only one place to look.
@delgado:
The Brother is 600dpi and generally colours are good (recall that it is CMYK, same as printing inks). They are simply wrong!
This is the post to explain the actual installation of a Brother DCP-L3510CDW printer under Devuan Chimaera-4 using a PPD extracted from the printer-supplied CD (see OP) & placed into /etc/cups/ppd. The OP was easy, since the Terminal creates a history file at ~/.bash_history. The GUI does not, so I have to repeat everything to be certain of getting it right.
(This printer is now £200 cheaper than when I bought it. Harrumph.)
My Desktop Manager is XFCE v4.16, and the printer config utility system-config-printer (accessed via menu: Settings) is as follows:
1.5.14
A CUPS configuration tool.README.md:
system-config-printer
It uses IPP to configure a CUPS server. Additionally it provides dBUS interface for several operations which aren't directly available in cupsd, and automatic USB printer installation daemon for non-IPP-over-USB printers.The alternatives for the graphical configuration tool are CUPS Web interface, desktop control-center or lpadmin command line tool if you need to install printer manually which may not be needed in recent cases.
My user is neither root nor the print-admin user lp, so my version shows an "Unlock" button which needs to be pressed (then pw authentication) before making any additions or changes. So, here is the step-by-step:
Open system-config-printer via menu: Settings
Press "Unlock" button & authenticate
(needs to be done often; I will not repeat it here)
Highlight an existing printer & duplicate (Ctrl+D)
(if none present then lpadmin is a terminal app to create one, but you are on your own there)
Click on the dupe & select Properties (right-click or menu:Printer)
Under Settings | Make & Model click on Change... button
(Click Cancel on the Search box, or wait for the timeout)
(The default is to offer a set of CUPS-supplied drivers (PPD files) for a vast range of printers)
To install a CUPS-supplied driver:
Click on Brother then click the Forward button
Scroll down the list & select the DCP-L3510CDW CUPS model at left, then the sole driver at right, and click the Forward button
Select the top option on the next screen ("Use the new PPD as is") & click Apply
Then click OK
(we are back at the main screen; I renamed the new printer "DCP-L3510CDW-CUPS")
(more to come; I will just check out how that printer performs)
Ah well, there is zero point in my checking that CUPS-supplied PPD since it is identical to the driver that Brother supplied me from their website over 2 years ago:
$ la /etc/cups/ppd
total 148
-rw-r----- 1 root lp 30989 Feb 4 02:33 BRPPL3510CDW-CMYK.ppd
-rw-r----- 2 alexk alexk 30989 Aug 23 2017 BRPPL3510CDW.PPD
-rw-r----- 2 alexk alexk 26326 Jul 3 2019 DCP3510W.PPD
-rw-r----- 1 root lp 26310 Feb 4 02:39 DCP3510W-RGB.ppd
-rw-r----- 1 root lp 26310 Feb 4 16:28 DCP-L3510CDW-CUPS.ppd
$ sudo diff /etc/cups/ppd/DCP3510W-RGB.ppd /etc/cups/ppd/DCP-L3510CDW-CUPS.ppd
$ # (no result)
To install Your Own PPD driver:
Click on "Provide PPD file" then click the Folder/Directory icon that appears below it
Navigate to the directory where the PPD file is stored
Select the PPD file that is the driver & click Open
(you may need to change the file option to "All files (*)")
(note that this file *must* be accessible under your user, and there is zero option available for sudo or whatever if it is not)
Then click Forward
Select the top option on the next screen ("Use the new PPD as is") & click Apply
Then click OK
(we are back at the main screen; rename the new printer if you wish)
(note that the original PPD file is left unchanged; a new PPD will be created in /etc/cups/ppd)
Even though this CMYK driver is older than the RGB driver it performs much better. But not perfect.
My standard LibreOffice Writer pages each have a snazzy vertical Drawing Object, adventurously labelled "Shape1", at the LHS of the first page. These are text-boxes that have a colour gradient background ('Area') which goes from a deep-blue at the top to a mid-blue at the bottom (#204A87 to #729FCF). On top is a text-field that contains the Page Title in a mid-grey (#CCCCCC). It is deeply attractive; I'm both proud & delighted with it. HP printed it perfectly & the damned Brother will not!
The newer RGB driver gets all colours wrong, including this Drawing Object on text-pages. The older CMYK seems to get the colour right but will not graduate the text-box Area. Sigh. An improvement, but no cigar.
The OP detailed my problem; in a nutshell:
Having paid out shed-loads of money to Amazon for a LED-powered printer/copier/scanner/wlan CMYK-toner network printer and,
having downloaded an up-to-date Linux driver from the Brother website,
discovered that it completely screwed up the colour balance in both text & photographs and,
Brother just responded with handy-wavy gestures & did nuthin'
To rub salt into the wound, I saved a file that was giving print difficulties as a PDF, took it to a friend with a business, and used his HP DeskJet to print it out (flawless). Bah!
Very recently I discovered that the key to ALL printing (regardless of your OS) is a PPD file. These were originated by Apple (as I understand it), and Adobe is in there somewhere. They are plain-text configuration files for PostScript and, mostly, are to specify ways in which printer-specific services are to be configured, and how things differ from the defaults. Here is the CUPS Help file (link only works if you have CUPS installed):
Printers use a description file with one or more driver ("filter") programs that communicate with the printer through a "backend" program. CUPS currently uses PPD (PostScript Printer Description) files to describe the printer and driver programs needed, some of which come with CUPS while others come with your operating system or Linux distribution.
The Printer Queue shows icons for each installed printer. CUPS uses a PPD file at install-time, in the process creating that icon(s):
Printers
Showing 2 of 2 printers.
Queue Name | Description | Make and Model | Status BRPPL3510CDW-CMYK DCPL3510CDW Brother DCP-L3510CDW BR-Script3 Idle DCP3510W-RGB DCP3510W-RGB Brother DCP-L3510CDW CUPS Idle
Here is the head of each file so that you can get a handle on what they are like:
$ sudo head /etc/cups/ppd/BRPPL3510CDW-CMYK.ppd -n 40
*PPD-Adobe: "4.3"
*%================================================
*% Copyright(C) 2017 Brother Industries, Ltd.
*% "Brother DCP-L3510CDW BR-Script3"
*%================================================
*%==== General Information Keywords ========================
*FormatVersion: "4.3"
*FileVersion: "1.0"
*LanguageEncoding: ISOLatin1
*LanguageVersion: English
*Manufacturer: "Brother"
*PCFileName: "BRPPL3510CDW.PPD"
*Product: "(Brother DCP-L3510CDW)"
*PSVersion: "(3010.106) 3"
*ShortNickName: "Brother DCP-L3510CDW BR-Script3"
*ModelName: "Brother DCP-L3510CDW BR-Script3"
*NickName: "Brother DCP-L3510CDW BR-Script3"
*%==== Basic Device Capabilities =============
*LanguageLevel: "3"
*TTRasterizer: Type42
*ColorDevice: True
*DefaultColorSpace: CMYK
*FileSystem: True
*?FileSystem:"
save
/devname (%disk0%) def
/ret false def
0 1 7{
devname exch 48 add 5 exch put
devname devstatus {
0 ne {/ret true def}if
pop pop pop pop pop pop pop
}if
}for
ret {(True)}{(False)} ifelse = flush
restore
"
*End
$ sudo head /etc/cups/ppd/DCP3510W-RGB.ppd -n 40
*PPD-Adobe: "4.3"
*%================================================
*% Copyright(C) 2018 Brother Industries, Ltd.
*% "Brother DCP-L3510CDW for CUPS"
*%================================================
*%==== General Information Keywords ========================
*FormatVersion: "4.3"
*FileVersion: "4.0.9"
*LanguageVersion: English
*LanguageEncoding: ISOLatin1
*PCFileName: "DCP3510W.PPD"
*Manufacturer: "Brother"
*Product: "(DCP-L3510CDW)"
*1284DeviceID: "MFG:Brother;MDL:DCP-L3510CDW"
*cupsVersion: 1.4
*cupsManualCopies: false
*cupsFilter: "application/vnd.cups-postscript 0 brother_lpdwrapper_dcpl3510cdw"
*%cupsFilter: "application/vnd.cups-pdf 0 brother_lpdwrapper_dcpl3510cdw"
*cupsModelNumber: 5
*ModelName: "Brother DCP-L3510CDW"
*ShortNickName: "DCP-L3510CDW"
*NickName: "Brother DCP-L3510CDW CUPS"
*PSVersion: "(3010.106) 3"
*%==== Basic Device Capabilities =============
*LanguageLevel: "3"
*ColorDevice: True
*DefaultColorSpace: RGB
*FileSystem: False
*Throughput: "17"
*VariablePaperSize: False
*TTRasterizer: Type42
*FreeVM: "2700000"
*DefaultResolution: 600dpi
*%DefaultOutputOrder: Reverse
*%=== UI Constraints ==================================
*UIConstraints: "*BRInputSlot AutoSelect *BRMediaType Label"
So, first I had to find a PPD file that would actually work. That was simple, if fiddly, once I found it, and is detailed in the OP. I then hoped that simply replacing the file located in /etc/cups/ppd with the new file renamed-to-the-old would be sufficient but, naturally, that was a foolish hope. There is an actual install process to go through, and that will be detailed in the next post.
A HP DeskJet printer got replaced with a Brother DCP-L3510CDW led printer.
The HP was used so infrequently that the ink clogged up all the time. That did not happen with the Brother. However, whilst the DeskJet printed fine, the Brother did not:
The Brother was 5 x the cost of the HP
The screen (print preview) + paper results did not correspond
(b/w was OK but colour values were wrong)
A bug report to Brother got nowhere.
After 2 years (still using the same print drums all this time, and never clogs up) I've more-or-less fixed the broken colour values today. Here is how:
Brother provided a code-free CUPS driver from their website that moved in mysterious ways & provided an icon in the XFCE system-config-printer utility accessed from menu:Settings.
I know now that all that is required is a PPD file installed within /etc/cups/ppd/
('PPD' files are Postscript config files, detailing the specific features of the printer)
I recently looked at Brother under Open Printing
(CUPs *does* provide a ppd file for my model, but I only found that after fixing it!)
My original PPD file was marked as RGB whilst a Brother-DCP-9045CDN-Postscript-Brother.ppd file was marked as CMYK. That gave me hope that changing my driver to CMYK may fix the broken driver (the led printer uses 4 drums to print).
$ la /etc/cups/ppd
total 120
-rw-r----- 1 root lp 30989 Feb 4 02:33 BRPPL3510CDW-CMYK.ppd
-rw-r----- 2 alexk alexk 30989 Aug 23 2017 BRPPL3510CDW.PPD
-rw-r----- 2 alexk alexk 26326 Jul 3 2019 DCP3510W.PPD
-rw-r----- 1 root lp 26310 Feb 4 02:39 DCP3510W-RGB.ppd
$ # the original postscript driver:
$ fgrep DefaultColorSpace /etc/cups/ppd/DCP3510W.PPD
*DefaultColorSpace: RGB
$ # now the new one:
$ fgrep DefaultColorSpace /etc/cups/ppd/BRPPL3510CDW.PPD
*DefaultColorSpace: CMYK
The Brother came with a driver CD, but it was only good for Windows or Apple Mac. I found the PPD files within a Windows .msi file (brpsc17a.msi), and 7-Zip is the best way to extract it):
$ 7z x /media/alexk/BROTHER/install/msi/brpsc17a.msi
That creates a mass of (compressed) PPD files that each look something like this:
BRPPL3510CDW.PP__10.8743C30B_11BB_422B_A1A0_160735E2777E
Once again, 7-Zip will expand these files to the (plain-text) PPD files
(a lot of commands moving all relevant files into a sub-dir are missing here):
for i in ./*; do 7z x $i; done;
All these files are virtually identical. The major difference is a language declaration
(the language within all files was identical; just the declaration was different):
fgrep LanguageVersion *
$ # example follows
$ fgrep LanguageVersion BRPPL3510CDW.PP__03
*LanguageVersion: English
I placed the 2-digit ISO 639-1 code into the filename like this:
eg BRPPL3510CDW.en.PP__03 (in the end I had 6 'en' files & used the first one)
(the important feature here is that that PPD file was also CMYK)
I now had 2 PPD files:
1) DCP3510W.PPD :: this is the original faulty RGB driver provided via the Brother website
2) BRPPL3510CDW.PPD :: this was sourced via the Brother-supplied driver CD
I copied these as hard-links into the CUPs directory (/etc/cups/ppd). It is important to note that they must retain my file owner and group:
$ cp BRPPL3510CDW.en.PP__03 -l /etc/cups/ppd/BRPPL3510CDW.PPD
$ cp DCPL3510CDW.original.ppd -l /etc/cups/ppd/DCP3510W.PPD
That is the first part. Next, we shall use the Xfce-supplied Print Settings utility to add printers for each of these setups. However, that shall be tomorrow after I've had some sleep (almost 5am here in the UK).
Don't do this with Chimaera:
W: Skipping acquire of configured file 'non-free-firmware/binary-amd64/Packages'
as repository 'http://deb.devuan.org/merged chimaera InRelease'
doesn't have the component 'non-free-firmware'
(component misspelt in sources.list?)
Edit: reset since code is too stupid to wrap lines to the page
I'm on Chimaera & an upgrade included git just now (minutes earlier). However, no idea if that will have fixed *your* problem.
Sounds like port-80 is blocked for external traffic. But of course, that would mean that nf_tables (or something) is running.
Sorry, but cannot help. I was competent with the old firewall, but know nothing about the new one(s).
Blu-Ray Menus
Mostly, you need to give up on them. They will not run.
Blu-Ray uses JAVA to show a menu on screen. That *used* to work with Linux, but no more. If you have spent any time with Linux you will understand that last sentence completely. However, it also affects a (physical) Samsung Blue-Ray reader that I use to show (upto now, only) DVDs on a large TV-Screen (Samsung Smart TV). It will play the 2001 movie, but no menus. A little better with VLC after the updates: It will play the movie but no menus. VLC will, however show a 'Top Title' via Playback | Title | Top Menu, and that shows me all the titles in the disk, with text to describe them.
My ancient DVD VHS of "2001 A Space Odyssey" is badly damaged so, since it is one of my favourite movies & I wanted to rip it to disk so that I could watch it in multiple formats, I got a Blu-Ray DVD from Amazon (£6.79).
I was very much hoping that my old, cheap external DVD-reader/burner (~£12) would be able to read a blu-ray. Of course not, so that meant buying a new Blu-Ray reader (£84.98).
The new DVD connects via USB just like the old DVD, and this one revealed files & dirs, but neither VLC nor Handbrake would play. Even after following Interwebs advice I got the following:
$ /usr/bin/vlc bluray:///dev/sr1
VLC media player 3.0.18 Vetinari (revision 3.0.13-8-g41878ff4f2)
[000056024a64f580] main libvlc: Running vlc with the default interface. Use 'cvlc' to use vlc without interface.
keydbcfg.c:680: No valid AACS configuration files found
aacs.c:121: No usable AACS libraries found!
dec.c:197: aacs_open() failed: -2!
[00007f860c001160] libbluray demux: First play: 1, Top menu: 1
HDMV Titles: 19, BD-J Titles: 0, Other: 0
(this was due to my the supplier case-error in naming the cfg file - see 'Fix' below)
Sources:
The Fix:
When DVDs first appeared Linux could not play them. They were encrypted & not (as I understand it) documented. That got fixed & DVDs can now easily be played under Linux. Blu-Ray is more difficult, in that an ID (VUK - part of 'aacs') needs to exist for your specific disk in your specific language.
What follows now are the steps to take (identical to Debian, as it happens):
Install the necessary libraries:
$ sudo apt install vlc libaacs0 libbluray-bdj libbluray2
Download & install the latest file of Blu-Ray decryption keys in a specific place with a specific name:
(note that the supplied ZIP contains the correct file with the correct name but in the wrong case)
$ la /usr/share/doc/libaacs0/KEYDB.cfg.gz
-rw-r--r-- 1 root root 2615 May 4 2017 /usr/share/doc/libaacs0/KEYDB.cfg.gz
$ mkdir $HOME/.config/aacs
$ cd $HOME/.config/aacs
$ wget http://fvonline-db.bplaced.net/fv_download.php?lang=eng
$ mv 'fv_download.php?lang=eng' keydb_eng.zip
$ unzip keydb_eng.zip
Archive: keydb_eng.zip
inflating: keydb.cfg
(give it the correct name (case-sensitive))
$ mv keydb.cfg KEYDB.cfg
All The VLC Blu-Ray players will now work, as does Handbrake:
$ /usr/bin/vlc bluray:///dev/sr1
VLC media player 3.0.18 Vetinari (revision 3.0.13-8-g41878ff4f2)
[000056145484c580] main libvlc: Running vlc with the default interface. Use 'cvlc' to use vlc without interface.
aacs.c:170: ignoring empty drl
[00007f0578001120] libbluray demux: First play: 1, Top menu: 1
HDMV Titles: 19, BD-J Titles: 0, Other: 0
[00007f0578001120] libbluray demux: Adding ES 4113 select 1
[00007f0578001120] libbluray demux: Adding ES 4352 select 1
…
[00007f0558003890] gl gl: Initialized libplacebo v2.72.0 (API v72)
libva info: VA-API version 1.10.0
libva info: Trying to open /usr/lib/x86_64-linux-gnu/dri/radeonsi_drv_video.so
libva info: Found init function __vaDriverInit_1_10
libva info: va_openDriver() returns 0
[00007f056c006170] avcodec decoder: Using Mesa Gallium driver 20.3.5 for AMD KABINI (DRM 2.50.0, 6.0.0-0.deb11.6-amd64, LLVM 11.0.1) for hardware decoding
qt.qpa.xcb: QXcbConnection: XCB error: 3 (BadWindow), sequence: 7365, resource id: 17060910, major code: 40 (TranslateCoords), minor code: 0
A script to use under cron to keep the CFG file updated would be useful.
Updated 2023-01-22:
Corrected small errors. See also my next post for Blu-Ray menu errors (not fixed)
HTH
FWIW:
I've got Chimaera & gparted is installed:
$ apt policy gparted
gparted:
Installed: 1.2.0-1
Candidate: 1.2.0-1
Version table:
*** 1.2.0-1 500
500 http://deb.devuan.org/merged chimaera/main amd64 Packages
100 /var/lib/dpkg/status