-
Notifications
You must be signed in to change notification settings - Fork 129
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Unable to get a Brother QL-700 to print anything with cups-filters 1.28 #493
Comments
I changed the log level of the CUPS logger to
At some point it's complaining about not finding mutool but
|
Further down the log I'm also seeing this
|
This means that you have done something wrong with your installation of cups-filters. ALL versions of cups-filters come with |
Ok but it seems
Not sure if having those filters owned by Would you agree this looks like CUPS is unable to access the filters because of some missing permission? I mean, the filters are definitely installed on disk but CUPS still complains about not finding them... |
Here is a second log where I tried to print the same PDF first with If you take a look at |
@tvanesse After going through your log files there is an error saying that it couldn't open the file due to some permission issue . Could you change permission of file to 644 using |
Transfering an issue originally posted in
ghostscript-printer-app
, I am unable to get my Brother QL-700 to print anything withcups-filters-1.28
.After downgrading to
1.27
yesterday, I was able to send jobs and getting the printer to actually print stuff like it used to. The euphoria was short-lived though, because I woke up this morning finding my computer (rebooted) unable to make the QL-700 print anything, again.I tried to repeat the exact same steps I took the day before but no luck.
I now have a computer with CUPS 2.4.1 and a downgraded
cups-filters
1.27 and I still can't get the QL-700 to print (but it used to!).Out of despair, I am looking for guidance on how to get more useful information about this problem and, finally, get this printer to do its job.
The text was updated successfully, but these errors were encountered: