Your message dated Sat, 14 Jan 2023 18:30:15 +0000 (UTC)
with message-id
<alpine.deb.2.21.2301141823470.24...@postfach.intern.alteholz.me>
and subject line Closing this bug (BTS maintenance for debian-printing)
has caused the Debian Bug report #869498,
regarding Brother QL-500 does not print and blinks
to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.
(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact ow...@bugs.debian.org
immediately.)
--
869498: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=869498
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: printer-driver-ptouch
Version: 1.4.2-2+b1
Severity: normal
Hi,
I am unable to print with my QL-500. All the device does is blinking
fast while CUPS reports a successful print. I am willing to debug, just
tell me what to do.
I have already filed this upstream as
https://bitbucket.org/philpem/printer-driver-ptouch/issues/4/brother-ql-500-not-working
Greetings
Marc
-- System Information:
Debian Release: buster/sid
APT prefers unstable
APT policy: (500, 'unstable')
Architecture: amd64 (x86_64)
Kernel: Linux 4.12.2-zgws1 (SMP w/6 CPU cores)
Locale: LANG=de_DE.utf8, LC_CTYPE=de_DE.utf8 (charmap=UTF-8), LANGUAGE=en
(charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)
Versions of packages printer-driver-ptouch depends on:
ii ghostscript 9.21~dfsg-1
ii libc6 2.24-12
ii libcups2 2.2.4-3
ii libcupsimage2 2.2.4-3
ii python3 3.5.3-3
ii xz-utils 5.2.2-1.3
printer-driver-ptouch recommends no packages.
printer-driver-ptouch suggests no packages.
-- no debconf information
--- End Message ---
--- Begin Message ---
Hi Marc,
I am sorry that nobody took care of this bug. It was filed for an old
version of the package and probably fixed in a later upload. Unfortunately
your original upstream bug report is gone as the repository moved from
bitbucket to github now.
If you can reproduce it with the current version in unstable/testing please
reopen the bug, see https://www.debian.org/Bugs/server-control
for details.
Best regards,
Thorsten
--- End Message ---
