Bug#985989: nextcloud-desktop: segmentation fault when trying to open settings
Package: nextcloud-desktop Version: 3.1.1-1 Severity: important X-Debbugs-Cc: till2...@protonmail.com Dear Maintainers, When I try to access the settings of the nextcloud desktop client, it crashes. What I did: 1. run nextcloud 2. right-click on nextcloud tray icon, then click 'Settings' OR click tray icon, then click account name (top left), then click 'Settings' Result: - the client crashes instantly. When running from terminal, "Segmentation fault" is returned. This happens every time. Expectation: - don't crash, open settings window -- System Information: Debian Release: bullseye/sid APT prefers testing APT policy: (900, 'testing'), (500, 'testing-security'), (10, 'unstable') Architecture: amd64 (x86_64) Kernel: Linux 5.10.0-5-amd64 (SMP w/4 CPU threads) Locale: LANG=en_GB.UTF-8, LC_CTYPE=en_GB.UTF-8 (charmap=UTF-8), LANGUAGE=en_GB:en Shell: /bin/sh linked to /usr/bin/dash Init: systemd (via /run/systemd/system) LSM: AppArmor: enabled Versions of packages nextcloud-desktop depends on: ii libc6 2.31-10 ii libcloudproviders0 0.3.0-3 ii libgcc-s1 10.2.1-6 ii libglib2.0-0 2.66.7-2 ii libnextcloudsync0 3.1.1-1 ii libqt5core5a 5.15.2+dfsg-5 ii libqt5dbus55.15.2+dfsg-5 ii libqt5gui5 5.15.2+dfsg-5 ii libqt5keychain10.10.0-1 ii libqt5network5 5.15.2+dfsg-5 ii libqt5qml5 5.15.2+dfsg-5 ii libqt5quick5 5.15.2+dfsg-5 ii libqt5quickcontrols2-5 5.15.2+dfsg-2 ii libqt5sql5-sqlite 5.15.2+dfsg-5 ii libqt5svg5 5.15.2-2 ii libqt5webenginecore5 5.15.2+dfsg-3 ii libqt5webenginewidgets55.15.2+dfsg-3 ii libqt5webkit5 5.212.0~alpha4-11 ii libqt5widgets5 5.15.2+dfsg-5 ii libstdc++6 10.2.1-6 ii nextcloud-desktop-common 3.1.1-1 ii nextcloud-desktop-l10n 3.1.1-1 ii qml-module-qtgraphicaleffects 5.15.2-2 ii qml-module-qtqml-models2 5.15.2+dfsg-5 ii qml-module-qtquick-controls2 5.15.2+dfsg-2 ii qml-module-qtquick-layouts 5.15.2+dfsg-5 ii qml-module-qtquick-window2 5.15.2+dfsg-5 ii qml-module-qtquick25.15.2+dfsg-5 Versions of packages nextcloud-desktop recommends: ii nextcloud-desktop-doc 3.1.1-1 nextcloud-desktop suggests no packages. -- no debconf information
Bug#326787: kdebluetooth should be compiled against KDE 3.4.2 (kdelibs4c2 package)
Package: kdebluetooth Version: 1.0_beta1-1 Severity: wishlist kdebluetooth package hiders from upgrading to KDE 3.4.2 unstable, because it depends on kdelibs4 which is replaced with kdelibs4c2. It should be recompiled against the new package. -- System Information: Debian Release: testing/unstable APT prefers testing APT policy: (990, 'testing'), (500, 'unstable'), (500, 'stable'), (1, 'experimental') Architecture: i386 (i686) Shell: /bin/sh linked to /bin/bash Kernel: Linux 2.6.13 Locale: LANG=C, LC_CTYPE=C (charmap=ANSI_X3.4-1968) Versions of packages kdebluetooth depends on: ii kdelibs44:3.4.1-1core libraries for all KDE applica ii libart-2.0-22.3.17-1 Library of functions for 2D graphi ii libaudio2 1.7-2The Network Audio System (NAS). (s ii libbluetooth1 2.19-1 Library to use the BlueZ Linux Blu ii libc6 2.3.5-6 GNU C Library: Shared libraries an ii libfam0c102 2.7.0-7 client library to control the FAM ii libfontconfig1 2.3.2-1 generic font configuration library ii libfreetype62.1.7-2.4FreeType 2 font engine, shared lib ii libgcc1 1:4.0.1-2GCC support library ii libglib1.2 1.2.10-10The GLib library of C routines ii libgtk1.2 1.2.10-17The GIMP Toolkit set of widgets fo ii libice6 4.3.0.dfsg.1-14 Inter-Client Exchange library ii libidn110.5.18-1 GNU libidn library, implementation ii libopenobex-1.0-0 1:1.0.0-rel-3OBEX protocol library ii libpng12-0 1.2.8rel-1 PNG library - runtime ii libqt3c102-mt 3:3.3.4-3Qt GUI Library (Threaded runtime v ii libsm6 4.3.0.dfsg.1-14 X Window System Session Management ii libstdc++5 1:3.3.6-7The GNU Standard C++ Library v3 ii libx11-64.3.0.dfsg.1-14 X Window System protocol client li ii libxcursor1 1.1.3-1 X cursor management library ii libxext64.3.0.dfsg.1-14 X Window System miscellaneous exte ii libxft2 2.1.7-1 FreeType-based font drawing librar ii libxi6 4.3.0.dfsg.1-14 X Window System Input extension li ii libxrandr2 4.3.0.dfsg.1-14 X Window System Resize, Rotate and ii libxrender1 1:0.9.0-2X Rendering Extension client libra ii libxt6 4.3.0.dfsg.1-14 X Toolkit Intrinsics ii xlibs 4.3.0.dfsg.1-14 X Keyboard Extension (XKB) configu ii xmms1.2.10+cvs20050209-2 Versatile X audio player that look ii zlib1g 1:1.2.2-4compression library - runtime kdebluetooth recommends no packages. -- no debconf information -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Bug#326895: konversation: needs to depend on kdelibs4c2
Package: konversation Version: 0.17-1 Severity: grave Justification: renders package unusable the konversation package depends on kdelibs4, although kdelibs has been upgraded to kdelibs4c2 in unstable. As a result konversation is not available in unstable. -- System Information: Debian Release: testing/unstable APT prefers testing APT policy: (990, 'testing'), (500, 'unstable'), (500, 'stable'), (1, 'experimental') Architecture: i386 (i686) Shell: /bin/sh linked to /bin/bash Kernel: Linux 2.6.13 Locale: LANG=C, LC_CTYPE=C (charmap=ANSI_X3.4-1968) Versions of packages konversation depends on: ii kdelibs4 4:3.4.1-1 core libraries for all KDE applica ii libart-2.0-2 2.3.17-1Library of functions for 2D graphi ii libaudio21.7-2 The Network Audio System (NAS). (s ii libc62.3.5-6 GNU C Library: Shared libraries an ii libfam0c102 2.7.0-7 client library to control the FAM ii libfontconfig1 2.3.2-1 generic font configuration library ii libfreetype6 2.1.7-2.4 FreeType 2 font engine, shared lib ii libgcc1 1:4.0.1-2 GCC support library ii libice6 4.3.0.dfsg.1-14 Inter-Client Exchange library ii libidn11 0.5.18-1GNU libidn library, implementation ii libpng12-0 1.2.8rel-1 PNG library - runtime ii libqt3c102-mt3:3.3.4-3 Qt GUI Library (Threaded runtime v ii libsm6 4.3.0.dfsg.1-14 X Window System Session Management ii libstdc++5 1:3.3.6-7 The GNU Standard C++ Library v3 ii libx11-6 4.3.0.dfsg.1-14 X Window System protocol client li ii libxcursor1 1.1.3-1 X cursor management library ii libxext6 4.3.0.dfsg.1-14 X Window System miscellaneous exte ii libxft2 2.1.7-1 FreeType-based font drawing librar ii libxrandr2 4.3.0.dfsg.1-14 X Window System Resize, Rotate and ii libxrender1 1:0.9.0-2 X Rendering Extension client libra ii libxt6 4.3.0.dfsg.1-14 X Toolkit Intrinsics ii xlibs4.3.0.dfsg.1-14 X Keyboard Extension (XKB) configu ii zlib1g 1:1.2.2-4 compression library - runtime konversation recommends no packages. -- no debconf information -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Bug#327048: kdiff3: uninstallable in unstable beacause of dependency on kdelibs4
Package: kdiff3 Version: 0.9.88-4 Severity: grave Justification: renders package unusable the package is not installable in unstable because it still depends on kdelibs4 which has been replaced with kdelibs4c2 in unstable. Please recompile. Thanks a lot! -- System Information: Debian Release: testing/unstable APT prefers testing APT policy: (990, 'testing'), (500, 'unstable'), (500, 'stable'), (1, 'experimental') Architecture: i386 (i686) Shell: /bin/sh linked to /bin/bash Kernel: Linux 2.6.13 Locale: LANG=C, LC_CTYPE=C (charmap=ANSI_X3.4-1968) Versions of packages kdiff3 depends on: ii kdelibs4 4:3.4.1-1 core libraries for all KDE applica ii libart-2.0-2 2.3.17-1Library of functions for 2D graphi ii libc62.3.5-6 GNU C Library: Shared libraries an ii libfam0c102 2.7.0-7 client library to control the FAM ii libgcc1 1:4.0.1-2 GCC support library ii libice6 4.3.0.dfsg.1-14 Inter-Client Exchange library ii libidn11 0.5.18-1GNU libidn library, implementation ii libpng12-0 1.2.8rel-1 PNG library - runtime ii libqt3c102-mt3:3.3.4-3 Qt GUI Library (Threaded runtime v ii libsm6 4.3.0.dfsg.1-14 X Window System Session Management ii libstdc++5 1:3.3.6-7 The GNU Standard C++ Library v3 ii libx11-6 4.3.0.dfsg.1-14 X Window System protocol client li ii libxext6 4.3.0.dfsg.1-14 X Window System miscellaneous exte ii libxrender1 1:0.9.0-2 X Rendering Extension client libra ii xlibs4.3.0.dfsg.1-14 X Keyboard Extension (XKB) configu ii zlib1g 1:1.2.2-4 compression library - runtime kdiff3 recommends no packages. -- no debconf information -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Bug#327052: openoffice.org-kde: uninstallable in unstable
Package: openoffice.org-kde Version: 1.1.3-9 Severity: grave Justification: renders package unusable package is uninstallable in unstable because it still depends on kdelibs4 which has been upgraded to kdelibs4c2 in unstable. please recompile. thanks! -- System Information: Debian Release: testing/unstable APT prefers testing APT policy: (990, 'testing'), (500, 'unstable'), (500, 'stable'), (1, 'experimental') Architecture: i386 (i686) Shell: /bin/sh linked to /bin/bash Kernel: Linux 2.6.13 Locale: LANG=C, LC_CTYPE=C (charmap=ANSI_X3.4-1968) Versions of packages openoffice.org-kde depends on: ii kdelibs4 4:3.4.1-1 core libraries for all KDE applica ii libc62.3.5-6 GNU C Library: Shared libraries an ii libgcc1 1:4.0.1-2 GCC support library ii libqt3c102-mt3:3.3.4-3 Qt GUI Library (Threaded runtime v ii libstdc++5 1:3.3.6-7 The GNU Standard C++ Library v3 ii libstlport4.64.6.2-2 STLport C++ class library ii libx11-6 4.3.0.dfsg.1-14 X Window System protocol client li ii openoffice.org-bin 1.1.3-9 OpenOffice.org office suite binary ii xlibs4.3.0.dfsg.1-14 X Keyboard Extension (XKB) configu openoffice.org-kde recommends no packages. -- no debconf information -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Bug#122415: gs vertically misaligns printed output
On 01/23/2011 02:23 PM, Jonathan Nieder wrote: gs -sDEVICE=stp \ This bug is obsolete. The built-in Ghostscript driver "stp" does not exist any more in current Ghostscript. It is replaced by the CUPS-Raster- and IJS-based flavors of Gutenprint. So this bug can be closed. Till -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#610928: Backward compatibility script needed for HP PPD upgrade
The Debian packages of HPLIP (hplip, hplip-cups, hpijs, and hpijs-ppds) should generally update the PPDs of the existing print queues to the current packages version in the post-install scripts. Can you attach the PPD(s) which did not get updated automatically to this bug report? Thanks. Till On 01/24/2011 02:47 AM, Kevin Shanahan wrote: Package: hpijs-ppds Version: 3.10.6-1.1 On upgrade from Lenny to Squeeze a number of our printer queues stopped working with the following error logged: D [24/Jan/2011:08:54:10 +1030] [Job 449496] prnt/hpcups/HPCupsFilter.cpp 361: DEBUG: Bad PPD - hpPrinterLanguage not found D [24/Jan/2011:08:54:10 +1030] [Job 449496] prnt/backend/hp.c 839: ERROR: null print job total=0 The upgrade also reset the default paper size to weird values on a bunch of other HP printers. I found this info on the redhat bugzilla: https://bugzilla.redhat.com/show_bug.cgi?id=579355 I grabbed a copy of hpijs-3.10.9-1.fc12.x86_64.rpm, extracted the hpcups-update-ppds script and ran it. This fixed all the issues caused by the upgrade. Debian should have something like this for Squeeze. Regards, Kevin -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#594322: [Foo2zjs-maintainer] Bug#594322: foo2zjs: Please upgrade to more recent version for Squeeze.
Also thank you very much for accepting my changes. Now the differences between the Ubuntu (Natty, 11.04) package and the Debian package are minimal: 1. The Ubuntu package has the hook for the automatic bug reporting system Apport. 2. In the Ubuntu package the menu entry for the paper-out resetter for the HP LaserJet 1018/1020 is suppressed, as it is very hardware-specific. Till On 02/19/2011 08:32 PM, Luca Capello wrote: Hi there! Till, a big THANK YOU for the detailed explanations, I really appreciated. -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#594322: [Foo2zjs-maintainer] Bug#594322: foo2zjs: Please upgrade to more recent version for Squeeze.
OK. Then take the Apport hook into the Debian package and we keep foo2zjs identical on Debian and Ubuntu. Till -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#615202: libgs8: SEGV in gs when called from pstoraster (and in other contexts)
Thank you for the nice bug report with fix. I will apply the fix upstreamm. I have no file to reproduce it. Can you send me your file by e-mail? Thanks. Till -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#616077: "AUTH_GSS upcall timed out" in export with kerberos
Package: nfs-kernel-server Version: 1.2.2-4 Short description: kerberized nfs4 exports do work, but nevertheless there are continuous kernel messages: "RPC: AUTH_GSS upcall timed out." Procedure to trigger the bug: 1. On the server machine, /etc/init.d/nfs-common and /etc/init.d/nfs-kernel-server have already been run with argument start. 2. On the client machine, the nfs-exported directories are not yet mounted and /etc/init.d/nfs-common has been called with argument stop. 3. On the client machine, call /etc/init.d/nfs-common with argument start. 4. On the client machine, mount nfs-exported directories. As yet, nothing wrong happens. 5. From the server machine, log into the client machine with ssh as a non-root user, thus forwarding kerberos credentials to the client machine: the nfs-exported directories are normally accessible on the client machine (according to the rights of this user). After this, the kernel on the server machine logs this to /var/log/messages every 30 seconds (too much output for the log file!): Mar 2 09:44:27 olaf kernel: [60989.928631] RPC: AUTH_GSS upcall timed out. Mar 2 09:44:27 olaf kernel: [60989.928632] Please check user daemon is running. But /usr/sbin/rpc.svcgssd is still running on the server, and the user can still access the nfs-exported directories on the client. Note that the kernel messages every 30 seconds continue even after user logout from the client, unmounting all nfs-exported directories on the client, stopping /etc/init.d/nfs-common on the client, and stopping /etc/init.d/nfs-kernel-server and /etc/init.d/nfs-common on the server. Stopping /etc/init.d/nfs-kernel-server and /etc/init.d/nfs-common and starting it again (in opposite order) gives these kernel messages: Mar 2 09:49:15 olaf kernel: [61278.055487] svc: failed to register lockdv1 RPC service (errno 97). Mar 2 09:49:15 olaf kernel: [61278.056254] NFSD: Using /var/lib/nfs/v4recovery as the NFSv4 state recovery directory Mar 2 09:49:15 olaf kernel: [61278.056268] NFSD: starting 90-second grace period (but these messages are there in each nfs-kernel-server start), and then the above AUTH_GSS messages every 30 seconds continue. Only a server reboot helps. (With a newer kernel on the server --- linux-image-2.6.37-1-amd64 of sid, the messages do not seem to continue, but are also present in the first place). After downgrading nfs-common and nfs-kernel-server to the lenny versions (1.1.2-6), this bug does not occur. I would test nfs-utils-1.2.3 if it were available as debian packages in sid, but hesitate to mess around and install it from source. Other configuration: - Debian squeeze amd64 system, linux-image-2.6.32-5-amd64 both on server and client machine. - /etc/exports on server: /export gss/krb5p(rw,sync,fsid=0,no_subtree_check) /export/nfs gss/krb5p(rw,sync,nohide,no_subtree_check) /export/home gss/krb5p(rw,sync,nohide,no_subtree_check) /export/mail gss/krb5p(rw,sync,nohide,no_subtree_check) - /etc/fstab on client: ... server.machine:/nfs/usr/nfsnfs4sec=krb5p 0 0 server.machine:/home /home nfs4sec=krb5p 0 0 server.machine:/mail /var/mail nfs4sec=krb5p 0 0 - /etc/default/nfs-common on server: # If you do not set values for the NEED_ options, they will be attempted # autodetected; this should be sufficient for most people. Valid alternatives # for the NEED_ options are "yes" and "no". # Do you want to start the statd daemon? It is not needed for NFSv4. NEED_STATD= # Options for rpc.statd. # Should rpc.statd listen on a specific port? This is especially useful # when you have a port-based firewall. To use a fixed port, set this # this variable to a statd argument like: "--port 4000 --outgoing-port 4001". # For more information, see rpc.statd(8) or http://wiki.debian.org/?SecuringNFS STATDOPTS= # Do you want to start the idmapd daemon? It is only needed for NFSv4. NEED_IDMAPD= # Do you want to start the gssd daemon? It is required for Kerberos mounts. NEED_GSSD= - /etc/default/nfs-kernel-server on server: # Number of servers to start up RPCNFSDCOUNT=8 # Runtime priority of server (see nice(1)) RPCNFSDPRIORITY=0 # Options for rpc.mountd. # If you have a port-based firewall, you might want to set up # a fixed port here using the --port option. For more information, # see rpc.mountd(8) or http://wiki.debian.org/?SecuringNFS RPCMOUNTDOPTS=--manage-gids # Do you want to start the svcgssd daemon? It is only required for Kerberos # exports. Valid alternatives are "yes" and "no"; the default is "no". NEED_SVCGSSD=yes # Options for rpc.svcgssd. RPCSVCGSSDOPTS= - on server, statd idmapd nfsd svcgssd mountd are started - /etc/default/nfs-common on client: # If you do not set values for the NEED_ options, they will be attempted # autodetected; this should be sufficient for most people. Valid alternatives # for the NEED_ options are "yes" and "no". # Do you want to start the statd daemon? It is
Bug#616089: Switching from text modus back to Xorg impossible
Package: xserver-xorg-core Version: 1.7.7-11 System info: squeeze amd64, linux-image-2.6.32-5-amd64, gdm3 Description: After switching to text modus login screen with Ctrl-Alt-F1 and switching back with Alt-F7, the screen is black (text modus, with a blinking curser in upper left corner). This does only happen after a user was already logged in with gdm3 and has logged out again; but then it seems to happen always, even after "/etc/init.d/gdm3 restart". While it happens, a backtrace of Xorg with gdb (probably not much use, not compiled with debugging symbols?): (gdb) bt #0 0x7f8cf9c838b3 in select () from /lib/libc.so.6 #1 0x0046577a in WaitForSomething () #2 0x004330f2 in ?? () #3 0x00425c35 in _start () (gdb) and also while it happens: olaf:~# ps ax | grep gdm 1504 ?Sl 0:00 /usr/sbin/gdm3 4999 ?Sl 0:00 /usr/lib/gdm3/gdm-simple-slave --display-id /org/gnome/DisplayManager/Display1 5000 tty9 Ss+0:00 /usr/bin/Xorg :0 -br -verbose -audit 0 -novtswitch -auth /var/run/gdm3/auth-for-Debian-gdm-ch5K3k/database -nolisten tcp vt9 5025 ?Ssl0:00 /usr/bin/gnome-session --autostart=/usr/share/gdm/autostart/LoginWindow/ 5032 ?Ss 0:02 /usr/lib/gnome-settings-daemon/gnome-settings-daemon --gconf-prefix=/apps/gdm/simple-greeter/settings-manager-plugins 5042 ?S 0:00 /usr/lib/gdm3/gdm-simple-greeter 5044 ?S 0:00 /usr/lib/gdm3/gdm-session-worker 5094 tty1 S+ 0:00 grep gdm olaf:~# Xorg.0.log during this state is: X.Org X Server 1.7.7 Release Date: 2010-05-04 X Protocol Version 11, Revision 0 Build Operating System: Linux 2.6.32-5-amd64 x86_64 Debian Current Operating System: Linux olaf.iswbio.uni-jena.de 2.6.32-5-amd64 #1 SMP Wed Jan 12 03:40:32 UTC 2011 x86_64 Kernel command line: BOOT_IMAGE=/boot/vmlinuz-2.6.32-5-amd64 root=UUID=f0ea1315-ab33-4c54-96e9-681d88acefcf ro Build Date: 12 January 2011 02:59:50AM xorg-server 2:1.7.7-11 (Cyril Brulebois ) Current version of pixman: 0.16.4 Before reporting problems, check http://wiki.x.org to make sure that you have the latest version. Markers: (--) probed, (**) from config file, (==) default setting, (++) from command line, (!!) notice, (II) informational, (WW) warning, (EE) error, (NI) not implemented, (??) unknown. (==) Log file: "/var/log/Xorg.0.log", Time: Wed Mar 2 12:23:10 2011 (==) Using config file: "/etc/X11/xorg.conf" (==) Using system config directory "/usr/share/X11/xorg.conf.d" (==) No Layout section. Using the first Screen section. (**) |-->Screen "Default Screen" (0) (**) | |-->Monitor "Configured Monitor" (==) No device specified for screen "Default Screen". Using the first device section listed. (**) | |-->Device "Configured Video Device" (==) Automatically adding devices (==) Automatically enabling devices (WW) The directory "/usr/share/fonts/X11/cyrillic" does not exist. Entry deleted from font path. (==) FontPath set to: /usr/share/fonts/X11/misc, /usr/share/fonts/X11/100dpi/:unscaled, /usr/share/fonts/X11/75dpi/:unscaled, /usr/share/fonts/X11/Type1, /usr/share/fonts/X11/100dpi, /usr/share/fonts/X11/75dpi, /var/lib/defoma/x-ttcidfont-conf.d/dirs/TrueType, built-ins (==) ModulePath set to "/usr/lib/xorg/modules" (II) The server relies on udev to provide the list of input devices. If no devices become available, reconfigure udev or disable AutoAddDevices. (II) Loader magic: 0x7c8a00 (II) Module ABI versions: X.Org ANSI C Emulation: 0.4 X.Org Video Driver: 6.0 X.Org XInput driver : 7.0 X.Org Server Extension : 2.0 (++) using VT number 9 (--) PCI:*(0:1:5:0) 1002:9614:1043:834d ATI Technologies Inc Radeon HD 3300 Graphics rev 0, Mem @ 0xd000/268435456, 0xfbde/65536, 0xfbc0/1048576, I/O @ 0xc000/256 (II) Open ACPI successful (/var/run/acpid.socket) (II) LoadModule: "extmod" (II) Loading /usr/lib/xorg/modules/extensions/libextmod.so (II) Module extmod: vendor="X.Org Foundation" compiled for 1.7.7, module version = 1.0.0 Module class: X.Org Server Extension ABI class: X.Org Server Extension, version 2.0 (II) Loading extension SELinux (II) Loading extension MIT-SCREEN-SAVER (II) Loading extension XFree86-VidModeExtension (II) Loading extension XFree86-DGA (II) Loading extension DPMS (II) Loading extension XVideo (II) Loading extension XVideo-MotionCompensation (II) Loading extension X-Resource (II) LoadModule: "dbe" (II) Loading /usr/lib/xorg/modules/extensions/libdbe.so (II) Module dbe: vendor="X.Org Foundation" compiled for 1.7.7, module version = 1.0.0 Module class: X.Org Server Extension ABI class: X.Org Server Extension, version 2.0 (II) Loading extension DOUBLE-BUFFER (II) LoadModule: "glx" (II) Loading /usr/lib/xorg/modules/extensions/libglx.so (II) Module glx: vendor="X.Org Foundation"
Bug#616089: Switching from text modus back to Xorg impossible
On Wed, Mar 02, 2011 at 01:53:28PM +0100, Michel Dänzer wrote: > The X server is running on VT 9, so you're not expected to see it on VT > 7. :) Oh --- sorry. I did not expect it to change the "VT" (does that mean virtual terminal?) from 7 to another in a restart. So this bug is invalid. But shouldnt't the X server always run on VT 7? Olaf -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#587272: warning from defoma: "It is recommended to run defoma-app purge gs"
I have fixed the problem in the Ubuntu package (8.71.dfsg.2-0ubuntu8), simply following the warning, adding defoma-app purge gs to the ghostscript.preinst script after all other defoma clean-up. Now the installation of this ghostscript package eliminates the defoma warning for all future package installations. debdiff attached. Till diff -u ghostscript-8.71.dfsg.2/debian/changelog ghostscript-8.71.dfsg.2/debian/changelog --- ghostscript-8.71.dfsg.2/debian/changelog +++ ghostscript-8.71.dfsg.2/debian/changelog @@ -1,3 +1,11 @@ +ghostscript (8.71.dfsg.2-0ubuntu8) natty; urgency=low + + * debian/ghostscript.preinst: Clean up traces of Ghostscript in defoma +via "defoma-app purge gs", so that when updating packages which still +use defoma no warnings get issued (Closes: #587272). + + -- Till Kamppeter Tue, 7 Dec 2010 23:59:59 +0100 + ghostscript (8.71.dfsg.2-0ubuntu7) maverick; urgency=low * debian/control: Updated versioned dependency of ghostscript on gsfonts, diff -u ghostscript-8.71.dfsg.2/debian/ghostscript.preinst ghostscript-8.71.dfsg.2/debian/ghostscript.preinst --- ghostscript-8.71.dfsg.2/debian/ghostscript.preinst +++ ghostscript-8.71.dfsg.2/debian/ghostscript.preinst @@ -31,6 +31,12 @@ rm -f /etc/defoma/ghostscript.subst-rule~ rm -f /var/lib/defoma/ghostscript.subst-cache fi + + # Purge old defoma stuff to avoid warnings from defoama when updating + # other packages which still use defoma +if dpkg --compare-versions "$2" lt-nl "8.71.dfsg.2-0ubuntu8"; then + defoma-app purge gs 2>/dev/null || true + fi ;; abort-upgrade)
Bug#696144: 20_head_tests.cf: regex for illegal IP address contains valid network 5/8
Package: spamassassin Version: 3.3.1-1: all Severity: important Spamassassin contains a rule to identify 5/8 as a bad network despite it beeing allocated in 2010-11. Somehow this network was missed when the bug reported in http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=609006 was fixed. -- System Information: Debian Release: 6.0.6 APT prefers stable-updates APT policy: (500, 'stable-updates'), (500, 'stable') Architecture: armel (armv5tel) Kernel: Linux 2.6.32-5-kirkwood Locale: LANG=en_GB.UTF-8, LC_CTYPE=en_GB.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#682426: cups: filter gs takes several minutes consuming 100 % of CPU
On 10/22/2012 06:22 PM, Didier 'OdyX' Raboud wrote: Le lundi, 22 octobre 2012 15.51:19, Paul Menzel a écrit : Didier, thank you for following up on the report. Today I hit this problem again – unfortunately when being in a hurry. It looks like on a new installed system, CUPS is not affected as it does not use the gs filter by default anymore(?). Well, CUPS now supposedly uses the "PDF" workflow and avoids converting PDF's to PS'es when unnecessary. Till will correct me if I'm wrong. :) Yes, that is the case. Usually PDF is only converted into PS if the printer is a PS printer or the driver requires PS input (like foo2zjs). Additionally bug #664538 [2] seems to deal with the same problem. Brian kindly followed up, mentioning too that it has to do with the gs filter in cups-filters and that pdftops might work. Well, the pdftops filter calls gs in Wheezy, as far as I can see. At least in the newest upstream version of cups-filters one can switch the filter to use pdftops from Poppler. Till -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#693606: jwm: Ridiculous dependencies
Package: jwm Version: 2.1.0-3 Severity: normal For a small light weight window manager, it sure has some huge dependencies. I mean come on. Why does a small window manager want to install a web browser? AND xulrunner. It's not a requirement in the source. If people want a browser they can install one on their own. Other packages for window managers bigger than this one don't have such requirements. This is silly... -- System Information: Debian Release: wheezy/sid APT prefers testing APT policy: (990, 'testing'), (500, 'unstable'), (500, 'stable'), (1, 'experimental') Architecture: amd64 (x86_64) Kernel: Linux 3.2.0-3-amd64 (SMP w/2 CPU cores) Locale: LANG=en_AU.UTF-8, LC_CTYPE=en_AU.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#635261: Possible solution: Add "-dNOINTERPOLATE" to Ghostscript command line
See my last comment in the Ubuntu bug report: https://bugs.launchpad.net/ubuntu/+source/foomatic-db/+bug/690116/comments/5 Till -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#555892: ptouch-driver -- CUPS/Foomatic driver for Brother P-touch label printers
I have packaged this driver now for Ubuntu, available as "ptouch-driver" in the Universe repository of Lucid. Till -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#593338: CUPS filters produce postscript that hangs Ricoh Aficio 3035
Hi, in the Debian bug report http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=593338 a user complains that his Ricoh Aficio 3035 printer hangs when printing from Debian on it. Probably the PostScript going to the printer is somehow broken. George, Bin, Ulrich, can someone of you please check with an appropriate Debian (or Ubuntu) installation whether the PostScript output is OK? And if not, tell us what needs to be corrected? Thanks in advance. Till -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#593338: CUPS filters produce postscript that hangs Ricoh Aficio 3035
On 09/07/2010 06:26 AM, Timo Juhani Lindfors wrote:
Note that even if you don't have an appropriate a Debian or Ubuntu
installation you can still look at the PostScript output. It is
available in
http://www.cups.org/str.php?L3646+P0+S-2+C0+I0+E0+M1000+Q
as "port9100_1.4.4-2.dump".
I have printed this file on an HP LaserJet P3005 without filtering,
using the command
nc -w1 192.168.2.115 9100 < port9100_1.4.4-2.dump
The printer prompted for inserting A4 paper and as I have A4 paper in
the tray, it seems that in this job manual paper feed is set. After
confirming the prompt pressing the OK button on the printer twice the
job got printed.
I have looked into the file, most probably either the
[{
%%BeginFeature: *RIPaperPolicy PromptUser
<> setpagedevice
<> >> setpagedevice
%%EndFeature
} stopped cleartomark
or the
[{
%%BeginFeature: *InputSlot 1Tray
<> setpagedevice
%%EndFeature
} stopped cleartomark
caused the printer to switch to manual feed.
Till
--
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#596467: libsane-hpaio: only works if hplip is installed
Fixed in Debian SVN repo and on Ubuntu in HPLIP 3.10.6-1ubuntu6. The fix will appear in the next HPLIP upload to Debian. Thanks for reporting the bug. Till -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#596467: Please make libsane-hpaio recommend hplip (not depend on)
On 09/12/2010 02:22 PM, Pascal Dormeau wrote: I had a look to the way this problem is solved for Ubuntu in Launchpad (make libsane-hpaio depend on hplip) and I believe this solution will prevent users from installing libsane-hpaio in stand-alone (without hplip), as publicized in the package description: "This package is useful for a minimal footprint headless scanning solution" I may have seen only a limited part of the problem, but from my own experience, it seems that the only thing missing is a /etc/hp/hplip.conf containing a stanza with the path to the data directory. Like this: [dirs] home=/usr/share/hplip And of course, a little explanation in a README.Debian. Making libsane-hpaio recommend hplip will prevent problems for most users, and will allow minimal installation (I can use my psc1510 with only hpijs and libsane-hpaio), even if creating the /etc/hp/hplip.conf like above solves only a part of the problem encountered by the original poster. Much better this way. I have implemented it as follows now (in the Debian SVN repo, release 3.10.6-1ubuntu7): - libsane-hpaio recommends hplip. - The file /etc/hp/hplip.conf moved from hplip to libsane-hpaio. This makes libsane-hpaio work without hplip. - As hplip needs /etc/hp/hplip.conf hplip depends on libsane-hpaio again, as before (It was even wrong to lift this dependency as /usr/share/hplip/data/models/models.dat was already in libsane-hpaio). Now it is assured that libsane-hpaio always works and minimum installations are possible. Till -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#596467: Please make libsane-hpaio recommend hplip (not depend on)
The setting of the PPD paths via the post-install script of hplip is no problem. libsane-hpaio does not need these paths, so nothing breaks if hplip gets installed after libsane-hpaio. In addition, hplip sets the paths to places where itself provides The PPD files. We do not expect any users to change them to personal preferences. Till On 09/13/2010 08:21 PM, Pascal Dormeau wrote: Glad to see that did not chose the "depend way". However, i have a remark about the hplip.conf file. Before this bug was opened, I tried to dig myself into the hplip related packages and yes the hplip.conf was shipped (up to now) with the hplip package. It seems that it is still updated after installation through the hplip postinst script (to fix PPD file paths). Could it be harmful (for instance a user that first installs libsane-hpaio then later decides to install hplip)? Well, I raise the question just in case (I guess there is no problem because there is no reason to modify the file with only libsane-hpaio installed), and I am quite sure that you have regarded this already. -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#605397: hplip: Won't print anything (gives unsupported format message)
On 11/29/2010 10:55 PM, Sam Morris wrote: This was solved by installing ghostscript-cups. It is only Recommended by cups; should hplip depend on it? The binary package hplip-cups should depend on it, as this package contains a CUPS Raster driver which needs ghostscript-cups. Till -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#605397: hplip: Won't print anything (gives unsupported format message)
On 11/29/2010 10:55 PM, Sam Morris wrote: This was solved by installing ghostscript-cups. It is only Recommended by cups; should hplip depend on it? Since HPLIP 3.9.6b-1 (exactly 3.9.4b-1ubuntu4) the hplip-cups package depends on ghostscript-cups. So for all Debian releases with this HPLIP version or a newer one this bug should be fixed. Till -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#637978: cups: Please add a dpkg trigger to update PPDs on driver upgrades
Roger, my postinst scripts (which OdyX uses for his trigger solution) conserve the default settings by replacing the PPD files using "lpadmin -m". They also support PPDs which do not exist physically but get generated on the fly (listing available PPDs with "lpinfo -m" and requesting them with "lpadmin -m", no direct file system access is done). Till -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#638277: libgs8 segfault : print jobs (recto/verso) stop after 2nd page
So it is an issue of the CUPS Raster output device of Ghostscript, "cups". At Ghostscript upstream we have fixed several segfault bugs in the CUPS Raster output device (see upstream GIT log). Best is to upgrade to current Ghostscript 9.04 (best with cups/gdevcups.c replaced by the one from GIT master). If this is not possible, one should look into backporting some of these fixes. Till -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#639827: gstoraster segfaults on any attempt to print
Several segfaults in the CUPS Raster output device (this is used by gstoraster) and in Ghostscript in general got fixed in Ghostscript 9.04 and shortly after. The fixes are all contained in the Ghostscript package of Ubuntu Oneiric. I recommend to merge this package to Debian. Till -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#634030: hplip: Please Build-Depends on libjpeg-dev, not libjpeg62-dev
I have updated the SVN repository of HPLIP now. So it needs only someone to upload the current state. I have tested and after the change it also builds correctly under Ubuntu, so that the Debian and Ubuntu packages can be kept identical. Till -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#585623: pcmanfm 0.9.7 problems with gksudo
Package: pcmanfm Version: 0.9.7-1 Severity: normal When selecting open as root in the tools menu pcmanfm loads as root with an auth error and a blank screen, after several seconds, perhaps 40, the error disappears and the files are shown. Click the button in the error dialog has no effect. It works fine if I set the prefs to gksu %s, rather than gksudo %s but then I need to issue the root password. I find this unacceptable! -- System Information: Debian Release: squeeze/sid APT prefers testing APT policy: (990, 'testing'), (500, 'unstable') Architecture: amd64 (x86_64) Kernel: Linux 2.6.32-5-amd64 (SMP w/2 CPU cores) Locale: LANG=en_AU.UTF-8, LC_CTYPE=en_AU.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Versions of packages pcmanfm depends on: ii libc6 2.10.2-9 Embedded GNU C Library: Shared lib ii libcairo2 1.8.10-4 The Cairo 2D vector graphics libra ii libfm-gtk00.1.12-1 file management support - GTK+ GUI ii libfm00.1.12-1 file management support - core lib ii libglib2.0-0 2.24.1-1 The GLib library of C routines ii libgtk2.0-0 2.20.1-1 The GTK+ graphical user interface ii libpango1.0-0 1.28.0-1 Layout and rendering of internatio ii libx11-6 2:1.3.3-3 X11 client-side library Versions of packages pcmanfm recommends: ii gnome-icon-theme 2.30.3-1 GNOME Desktop icon theme ii gvfs-backends 1.6.2-1userspace virtual filesystem - bac ii gvfs-fuse 1.6.2-1userspace virtual filesystem - fus pcmanfm suggests no packages. -- no debconf information -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#585626: pcmanfm does not show mounted drives listed in fstab
Package: pcmanfm Version: 0.9.7-1 Severity: normal pcmanfm 0.9.7 shows my windows drive in the left column but not my linux drives even though they are mounted and listed in fstab. Also there is not sign of my linux drive in (shudders when writing these words) "My Computer" bleh. since when did we start using windows naming conventions? sickening really :( Also I can't mount my windows drive, I get a message saying Authorization is Required. I have no idea where to even begin fixing this one on this version. I did have poliyKit rules written for the last version, but some how these were blasted away by something :( Anyway, it would have been nice to still offer the older version 0.5.2, at least it worked as expected, this version is so far from being finished I really have no use for it. I think it was a bit premature to force it on as an upgrade, it's more a downgrade. -- System Information: Debian Release: squeeze/sid APT prefers testing APT policy: (990, 'testing'), (500, 'unstable') Architecture: amd64 (x86_64) Kernel: Linux 2.6.32-5-amd64 (SMP w/2 CPU cores) Locale: LANG=en_AU.UTF-8, LC_CTYPE=en_AU.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Versions of packages pcmanfm depends on: ii libc6 2.10.2-9 Embedded GNU C Library: Shared lib ii libcairo2 1.8.10-4 The Cairo 2D vector graphics libra ii libfm-gtk00.1.12-1 file management support - GTK+ GUI ii libfm00.1.12-1 file management support - core lib ii libglib2.0-0 2.24.1-1 The GLib library of C routines ii libgtk2.0-0 2.20.1-1 The GTK+ graphical user interface ii libpango1.0-0 1.28.0-1 Layout and rendering of internatio ii libx11-6 2:1.3.3-3 X11 client-side library Versions of packages pcmanfm recommends: ii gnome-icon-theme 2.30.3-1 GNOME Desktop icon theme ii gvfs-backends 1.6.2-1userspace virtual filesystem - bac ii gvfs-fuse 1.6.2-1userspace virtual filesystem - fus pcmanfm suggests no packages. -- no debconf information -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#585623: pcmanfm 0.9.7 problems with gksudo
Ok more info, it only happens when I'm in a directory not owned by root -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#564589: python-kid does not escape ]]> as ]]> in serialization.py
Package: python-kid Version: 0.9.6-1 Python-kid does not excape ]]> to ]]> in serialization.py as it is required by the XML standard. ]]> may only be used to end a CDATA section: http://www.w3.org/TR/2006/REC-xml11-20060816/#syntax A patch used in Fedora is available here: https://bugzilla.redhat.com/attachment.cgi?id=382805 -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#532097: RFC: Forming a Printing Task Force (was RFA: cups -- Common UNIX Printing System)
I think this is a good idea. We are currently in sync with the following packages: - cups (pitti + me) - foomatic-db (OdyX + me) - foomatic-db-engine (OdyX + me) - hplip (Mark Purcell + me) Other printing-related packages are - ghostscript - foomatic-filters - gutenprint - foo2zjs - splix - pnm2ppa - min12xxw - m2300w - pxljr - cjet - system-config-printer - python-cups Note that I have taken this list from Ubuntu. It is possible that Debian has even more packages, especially also for non-CUPS workflows (these are not supported by Ubuntu). foomatic-filters will be synced between Ubuntu and Debian soon, too (OdyX + me). Till On 07/01/2010 03:40 PM, Didier 'OdyX' Raboud wrote: Hi all, I'm answering to RFA bug #532097, CC'ing to various printing-related packages and to pkg-cups-de...@l.a.d.o. Please followup to the pkg-cups-devel list (if that's OKay). === Preamble === I just joined Chris Lawrence, along with Till Kamppeter in maintaining some foomatic-* packages. Then I noticed the big² pile of work in ghostscript, cups and many surrounding packages. I don't intend to fingerpoint specific people or teams, but the situation is worrying : some unresolved security issues, many RC bugs, tons of bugs, an increasing diff with Ubuntu, etc. My perception of the problem is that the forces are currently divided between Ubuntu and Debian. It seems that Ubuntu is better than Debian in keeping up with patches, etc. In my humble opinion, it is now time to get those patches back to Debian and merge our forces towards a better printing experience for both Debian and Ubuntu users. === Proposal === I propose to form a "Printing Task Force" that would join the Debian and Ubuntu forces around common repositories: there is almost never interest in keeping a diff between Debian and Ubuntu. This group would handle the following packages: cups ghostscript foomatic-* ? other ones ? Would there be some interest in such a group ? What other packages would suit ? Thanks in advance, cheers, OdyX N.B. I intentionally kept out of the discussion the "implementation details" such as $VCS choice, mailing-list or group name, etc. -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#446888: Maybe a clue...
I think I had a similar issue between debian lenny + racoon and a netscreen firewall. It comes down to: - what is the lifetime of the phase1 connection - which side has initiated the connection. In my case, racoon seems to have a default of 30 minutes if I don't explicitly put a: lifetime time 60 min; in the sainfo section of racoon.conf. The netscreen (and maybe your ciscos) has a default of 60 minutes. So my situation was this: - time X + 00 minutes: nestcreen establishes a connection - time X + 30 minutes: racoon gets bored, says IPsec-SA expired -> at this time racoon does not renegotiate - time X + 60: miraculously the connection is alive again -> the netscreen firewall has renegotiated after 60 minutes. Any chance that this is your situation, and maybe racoon's default has changed from 60 in sarge to 30 in etch or lenny? HTH Till -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#555892: RFP: ptouch-driver -- CUPS/Foomatic driver for Brother P-touch, label printers
Thank you for your work on packaging the ptouch driver. I have tried it and I have done the following changes: 1. I have corrected the upstream version number of the Debian package. It must be 0.13. 2. I have added a margin definition to the driver/ptouch.xml file assuming zero margins. Now the PPD coming out is the same as your hand-edited PPD. I did not do the following yet, but I would do it when making a Ubuntu package: 1. The 2 changes in the original source code should be supplied as patches 2. There should be a post-install script updating the PPD files of already existing print queues as all Ubuntu printer driver packages have. The new ptouch-driver_0.13-1.diff.gz is attached. make sure to rename the upstream tarball to ptouch-driver_0.13.orig.tar.gz when using the new .diff.gz. Till ptouch-driver_0.13-1.diff.gz Description: Unix tar archive
Bug#555892: RFP: ptouch-driver -- CUPS/Foomatic driver for Brother P-touch, label printers
Sorry, I had the wrong tarball. Upstream version 1.3 was correct. Attached is the fixed .diff.gz for upstreamversion 1.3 with the correct margin definition. Till ptouch-driver_1.3-1.diff.gz Description: Unix tar archive
Bug#631025: cups: change default ErrorPolicy for network printers
CUPS has the retry-job error policy as default only for Ubuntu and there reports like yours never showed up, and also no bug reports for asking to return to the original stop-printer by default. pitti, should we activate the patch to switch to the retry-job error policy as default also for Debian? Till -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#678299: iceweasel (and epiphany) freezes on certain web-sites with javascript enabled
Package: iceweasel Version: 3.5.16-16 Iceweasel freezes on certain web-sites if javascript is enabled, giving the error message: ERROR: Couldn't check percent loaded, network problems. The same happens with epiphany, with the error messages: ** (epiphany-browser:8324): DEBUG: NP_Initialize succeeded ** (epiphany-browser:8324): DEBUG: NP_Initialize ** (epiphany-browser:8324): DEBUG: NP_Initialize succeeded ** (epiphany-browser:8324): DEBUG: NP_Initialize ** (epiphany-browser:8324): DEBUG: NP_Initialize succeeded ** (epiphany-browser:8324): DEBUG: NP_Initialize ** (epiphany-browser:8324): DEBUG: NP_Initialize succeeded ** (epiphany-browser:8324): DEBUG: NP_Initialize ** (epiphany-browser:8324): DEBUG: NP_Initialize succeeded ** (epiphany-browser:8324): DEBUG: NP_Initialize ** (epiphany-browser:8324): DEBUG: NP_Initialize succeeded ** (epiphany-browser:8324): DEBUG: NP_Initialize ** (epiphany-browser:8324): DEBUG: NP_Initialize succeeded ** (epiphany-browser:8324): DEBUG: NP_Initialize ** (epiphany-browser:8324): DEBUG: NP_Initialize succeeded ERROR: Couldn't check percent loaded, network problems. Note that there seem to be no general "network problems" on the system while this happens. I attach a tar-archive with a saved page from youtube. Loading the main file triggers the problem for me (today) with iceweasel and epiphany. I am using squeeze 6.0.5, linux-2.6.32-5-amd64, libc6 2.11.3-3. -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#631025: cups: change default ErrorPolicy for network printers
On 06/21/2012 05:41 AM, Martin Pitt wrote: Till Kamppeter [2012-06-20 18:17 +0200]: CUPS has the retry-job error policy as default only for Ubuntu and there reports like yours never showed up, and also no bug reports for asking to return to the original stop-printer by default. pitti, should we activate the patch to switch to the retry-job error policy as default also for Debian? I have no strong opinion about this. I would be a bit hesitant to change it so close to the Wheezy final freeze, but if there are good reasons for it and some other Debian users agree, sure. Why are there two different defaults for Debian and Ubuntu. What are the motivations in each of the distros? I prefer retry-job as it confuses unexperienced users less. In addition, the backends are badly designed or too enterprise-oriented, making queues getting stopped on temporary failures which users can easily fix, like printer not turned on, cable not plugged in, paper/toner empty, bad per-job option settings. If queues are stopped by failures then they only should get stopped by permanent failures, like queue being set up with wrong driver or wrong device URI, filter required by PPD not installed, not executable, or segfaulting. The default configuration of CUPS (and every other subsystem) should be optimized for desktop/small network users, as these are the ones who do know less about configuring and most need our help. Enterprise system administrators have more ease to change the configuration and can make queues getting stopped when the toner runs out if thwy want it. Therefore I suggest that, in both Debian and Ubuntu 1. ErrorPolicy is et to retry-job 2. CUPS listens to remote printer broadcasts by default Also Debian and Ubuntu should use the same defaults. Till -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#679117: printer-driver-ptouch: Incorrect Margins for PT9500PC and PT9800PCN
Thank you very much for the patch. In your patch you write "Attention: Not tested on other printers." and indeed your patch changes code which affects all supported printers, not only the two models with which you were suffering the problem. This can easily break things on the other printers, assuming that most supported printers work correctly with the original code. If you are not sure that the change works for all printers you should do it in a way that it only applies if the printer is one of the models for which you have made the change. Till -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#670055: cups-filters: diff for version 1.0.18-2 uploaded to DELAYED/2 for #670055
On 05/22/2012 01:39 PM, Tobias Hoffmann wrote: Hmm, I don't really know, but the cups-filters package has a bugtracker at https://bugs.linuxfoundation.org/ (under the OpenPrinting product). But just another debian bug would work equally well ... Till? Tobias, if this needs to be fixed in the texttopdf filter a bug on https://bugs.linuxfoundation.org/ can be filed. If it is a problem of Debian's packaging or Debian shipping a broken font or not shipping a required font then open a Debian bug. Till -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#670055: cups-filters: diff for version 1.0.18-2 uploaded to DELAYED/2 for #670055
On 05/22/2012 03:11 PM, Tobias Hoffmann wrote: Well, it's still not clear, who should fix what: 1. cups-pdf should probably announce that it can not only process PS, but also PDF. I'm not sure if the current cups-filter architecture handles this case well. This bug would be one of cups-pdf or cups-filter(?). This is a cups-pdf problem. I have even fixed it once by doing some slight changes on cups-pdf, making the PPD file accepting both PDF and PostScript as input and modifying the backend script to skip Ghostscript if the input is already PDF. Upstream did not accept this patch as one can modify the output by a variety of options in the config file and these options are implemented via Ghostscript. I suggest then to do a slightly different approach, only skipping Ghostscript if the settings in the config file are the default settings and otherwise using Ghostscript also with PDF input, simply feeding PDF into Ghostscript. See debian/patches/70_cups-pdf_support-pdf-workflow.patch in cups-pdf 2.5.0-17 on https://launchpad.net/ubuntu/+source/cups-pdf/2.5.0-17 2. It's unclear to me what the policy regarding pdftops is wrt. to using popper vs. ghostscript as converting agent. gs generates Type 3 (which causes problems), poppler does not. This can be fixed in pdftops, i.e. cups-filter, (use poppler tools in this case), or ghostscript (don't generate Type 3 -- there might be some commandline switches) For pdftops I was always tending to use Ghostscript as Ghostscript has once better color management and is designed more with printing in mind. At the release of Ubuntu Precise (12.04) I have found out that Ghostscript's PS output has problems with several PostScript printers due to bugs in the printer's PS interpreters. I added some workarounds to the pdftops filter for that. Which PostScript consumers do not like Type 3 fonts? Should I make Ghostscript only sending Type 2 fonts? Chris, is there a command line switch to make Ghostscript's "ps2write" device only sending Type 2 fonts? 3. The issue, that the Type 3 bounding boxes generated by ghostscript are deemed bad by poppler/evince. The experts from ghostscript and poppler have to determine who is wrong (it might even be caused by the original font file). Therefore this is either a poppler/evince, ghostscript or font bug. Chris, can it be that there is a bug in Ghostscript? Till -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#681495: printer-driver-ptouch: rastertoptch installed in directory that's not in cups' PATH
We have fixed this in Ubuntu already. See: https://launchpad.net/ubuntu/+source/ptouch-driver/+changelog http://launchpadlibrarian.net/106473938/ptouch-driver_1.3-3_1.3-3ubuntu0.1.diff.gz Please back-sync this package to Debian. Till -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#681851: escputil: requires module usblp which is blacklisted by CUPS
In the newest CUPS package (1.5.3-4) we have lifted the blacklisting again (solving the USB problems with a new USB backend). -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#682078: hplip: Draft quality makes "hpcups failed" for Deskjet D2660
This problem of having one quality level not working looks most like a fault inside the driver. Please report this problem upstream on http://launchpad.net/hplip/ Then the HPLIP developers at HP will get aware of this problem. Please tell there everything which you told here and also post the /var/log/cups/error_log and the hp-check output, as you did here. Till -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#611993: [ghostscript] Could reproduce with newer version
I could also reproduce the problem with Ghostscript 9.05 on Ubuntu Quantal. Therefore I have forwarded the problem upstream: http://bugs.ghostscript.com/show_bug.cgi?id=693205 Till -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#682426: cups: filter gs takes several minutes consuming 100 % of CPU
The real bug here is a Ghostscript bug. Ghostscript is not able to render a given input file in a reasonable time. This will be best fixed by the upstream developers of Ghostscript. They will need to reproduce the bug without CUPS, therefore we need the original input file and how CUPS has processed it. To obtain this information follow the instructions of the sections "CUPS error_log" and "Capturing print job data" on https://wiki.ubuntu.com/DebuggingPrintingProblems. These instructions are originally made for Ubuntu, but the CUPS package is identical in Debian and Ubuntu, so they should also work in Debian. Note that instead of running a command as root by preceding it with "sudo", like "sudo start cups", run the command (without preceded "sudo") in a second terminal window where you have switched to root via "su -". Till -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#664031: Inkscape
Note that the printing of Inkscape currently does not work. See: https://bugs.launchpad.net/ubuntu/+source/hplip/+bug/975972 Inkscape sends pages with zero width and zero height page size setting. Workaround is always to print out of the page preview of Inkscape. Till -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#664966: Add an option to disable T3CCITT encoding
This patch is backported from upstream (see filename of the patch), so no upstream bug needs to get reported. Till -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#664966: Add an option to disable T3CCITT encoding
There is no corresponding Ghostscript upstream bug, bug the following Ubuntu bug report: https://bugs.launchpad.net/ubuntu/+source/cups-filters/+bug/93 It is commit d6f83dfa81a. Till -- commit d6f83dfa81a2073c3d1f67a30aee7e8407e4685a Author: Ken Sharp Date: Mon Mar 19 10:06:10 2012 + ps2write - work-around bugs in Brother printer CCITTFaxDecode filter Raised on irc by Till Kamppeter, see Ubuntu bug : https://bugs.launchpad.net/ubuntu/+source/cups/+bug/93 After much work by Chris Liddell and Bruce Stough it transpires that at least some Brother printers have a bug in their CCITTFaxDecode filter, especially with small amounts of data. Since the ps2write otuput for bitmapped glyhs (which is required when the input is a CIDFont) always uses the CCITTFax filter, this led to corrupted output from the Brother (Note this is a bug in the *printer* not ps2write) This patch adds a new command line parameter 'NoT3CCITT' which disables compression of bitmapped glyphs. It should only be used with printers which have a problem with CCITTFax data, and in that case should also be used with the EncodeMonoImages switch to disable compression of monochrome images. Eg: -dNoT3CCITT -dEncodeMonoImages=false No differences expected as these are not tested by our regression tests -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#662025: foomatic-filters: Fails to print if 4.0.12-1 or 4.0.13-1 is installed
The problem should be fixed by the recent fixes in cups-filters, version 1.0.5 or later. Till -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#662025: foomatic-filters: Fails to print if 4.0.12-1 or 4.0.13-1 is installed
On 03/27/2012 09:28 PM, Helge Kreutzmann wrote: Thanks again for your help. I rebuild cups-filters 1.0.7-1 in testing (and the required dependencies from sid, where necessary) and now printing on the queue you asked me to set up (with the PPD file from you) works again as expected. Great, then this problem seems to be fixed. Ubuntu users with Kyocera PostScript printers also reported that the problem got fixed. My previous two queues, however, still show the Status: /usr/lib/backend/cups/usb failed Do you have any (idea|fine manual) how to reactivate those, as well? This seems to be an independent problem. Please open a new bug, with error_log, and "lpstat -v" output (and tell which queue works and which not), and also following the instructions of the section "USB printer" on https://wiki.ubuntu.com/DebuggingPrintingProblems. And thanks once more for your speedy and very efficient help, it is highly appreciated! You are welcome. Greetings Helge P.S. Are you going to close this bug or should I do so? Please close it, as this bug is fixed. Till -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#673289: cups-filters: PID xxxxx (/usr/lib/cups/filter/texttopdf) crashed on signal 6.
Paul, thank you for reporting the bug. Tobias, can you have a look into this? The crash is most probably caused by a font problem. Till -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#670055: cups-filters: diff for version 1.0.18-2 uploaded to DELAYED/2 for #670055
For me it looks OK, I would apply it upstream. Tobias, WDYT? Is this patch on texttopdf OK? Perhaps it also fixes bug 673289. Till On 05/18/2012 03:51 PM, Didier Raboud wrote: tags 670055 + pending thanks Dear Till and Martin, I've prepared an upload for cups-filters (versioned as 1.0.18-2) with Fabian's patch and uploaded it to DELAYED/2. Please feel free to tell me if I should delay it longer or reschedule it to let it go as is. Best regards, OdyX P.S. I have pushed the change to the packaging repository. -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#660420: Some Postscript printer drivers (Kyocera, Brother, maybe others) do not work anymore
The PostScript which gets sent to the printer is generated by Ghostscript, with its "ps2write" output device and in your case Ghostscript 9.05 is used. Ghostscript is called either by the pdftops CUPS filter (cups-filters package) or by foomatic-rip (foomatic-filters package). So please do the following test: pdf2ps file.pdf lpr -o raw file.ps This converts a PDF file to PostScript and then sends the file without any filtering to the printer. Does the file get printed? -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#662025: foomatic-filters: Fails to print if 4.0.12-1 or 4.0.13-1 is installed
We need some more information about your problem. First, can you tell us which printer (manufacturer/model), connection type (USB, Parallel, USB->Parallel adapter, network, ...), driver you are using? Can you also follow the instructions of the sections "CUPS error_log" and "Capturing print job data" on https://wiki.ubuntu.com/DebuggingPrintingProblems. The site is for Ubuntu, but the steps of the mentioned sections also work under Debian. If "sudo " does not work or if some administrative command of CUPS does not work, run the command in a second terminal window where you get root via "su -", without the "sudo " in the beginning. Note that we need this information to be able to fix the bug. Till -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#662660: [Pkg-cups-devel] Bug#662660: cups-filters: Please drop ttf-freefonts and use fontconfig to find the best-matching similar font
till@till-precise:~/ubuntu/cups/bzr/build-area/cups-1.5.2$ fc-match FreeMono.ttfDejaVuSans.ttf: "DejaVu Sans" "Book" till@till-precise:~/ubuntu/cups/bzr/build-area/cups-1.5.2$ Till -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#662660: [Pkg-cups-devel] Bug#662660: cups-filters: Please drop ttf-freefonts and use fontconfig to find the best-matching similar font
I have tried this now: till@till-precise:~/ubuntu/cups/bzr/build-area/cups-1.5.2$ ls -l /usr/share/cups/fonts/ total 16 lrwxrwxrwx 1 root root 66 Mar 6 17:29 FreeMonoBoldOblique.ttf -> /usr/share/fonts/truetype/liberation/LiberationMono-BoldItalic.ttf lrwxrwxrwx 1 root root 60 Mar 6 17:30 FreeMonoBold.ttf -> /usr/share/fonts/truetype/liberation/LiberationMono-Bold.ttf lrwxrwxrwx 1 root root 62 Mar 6 17:30 FreeMonoOblique.ttf -> /usr/share/fonts/truetype/liberation/LiberationMono-Italic.ttf lrwxrwxrwx 1 root root 63 Mar 6 17:29 FreeMono.ttf -> /usr/share/fonts/truetype/liberation/LiberationMono-Regular.ttf till@till-precise:~/ubuntu/cups/bzr/build-area/cups-1.5.2$ Now a correct printout came out. Till -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#662660: [Pkg-cups-devel] Bug#662660: cups-filters: Please drop ttf-freefonts and use fontconfig to find the best-matching similar font
Thank you very much. This patch works correctly now. I have committed it to the upstream BZR repository of cups-filters. It will go into the next Debian/Ubuntu package, probably later today. Patches to use fontconfig patterns in the pdf.utf-8.* files are welcome. Till -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#663070: [Pkg-cups-devel] Bug#663070: cups-filters: Please complete the implementation of fontconfig-based font selection
Fabian, thenk you very much for your patches. It works all correct for me, also with the FreeMono fonts uninstalled. I have applied your patches to the upstream BZR repository so that cups-filters 1.0.5 will include the change. Till -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#662025: foomatic-filters: Fails to print if 4.0.12-1 or 4.0.13-1 is installed
I have checked your error_log and it shows one job which has successfully completed. I assume that this is the job which did not print for you. First, a reasonable amount of data gets sent to the printer but it does not make the printer printing something. Second, your attached error_log has only the following part which looks strange: -- D [08/Mar/2012:21:04:00 +0100] [Job 233] Options from the PPD file: D [08/Mar/2012:21:04:00 +0100] [Job 233] D [08/Mar/2012:21:04:00 +0100] [Job 233] D [08/Mar/2012:21:04:00 +0100] [Job 233] D [08/Mar/2012:21:04:00 +0100] [Job 233] File: D [08/Mar/2012:21:04:00 +0100] [Job 233] D [08/Mar/2012:21:04:00 +0100] [Job 233] -- This makes the impression that foomatic-rip did not read any options from the PPD file. Please run the command ls -l /etc/cups/ppd/FS-1020D.ppd and attach your /etc/cups/ppd/FS-1020D.ppd file. Thanks. Till On 03/08/2012 09:19 PM, Helge Kreutzmann wrote: Hello, On Mon, Mar 05, 2012 at 12:32:02PM +0100, Till Kamppeter wrote: We need some more information about your problem. First, can you tell us which printer (manufacturer/model), connection type (USB, Kyocera Ecosys FS-1020D, now connected via USB (used to be parallel, I still have the conection wired to the old (shut down) machine). Parallel, USB->Parallel adapter, network, ...), driver you are using? Driver?? None specifilly. Or do you men ppd file? Can you also follow the instructions of the sections "CUPS error_log" and "Capturing print job data" on https://wiki.ubuntu.com/DebuggingPrintingProblems. The site is for Ubuntu, but the steps of the mentioned sections also work under Debian. If "sudo" does not work or if some administrative command of CUPS does not work, run the command in a second terminal window where you get root via "su -", without the "sudo " in the beginning. Ok. Note that we need this information to be able to fix the bug. Fine. a) There is no »ubuntu-bug« within Debian main (testing). b) apport-collect does not exist neither c) Output of printdebuginfo: == System information == Ubuntu Release : testing (wheezy) Desktop Environment: none Architecture : x86_64 Kernel : 3.2.9sneo.01-grsec Locale : LANG=de_DE.UTF-8, LC_CTYPE=de_DE.UTF-8, LC_PAPER=de_DE.UTF-8 /etc/papersize : a4 == Configured printers == FS-1020D: Kyocera FS-1020D Foomatic/Postscript Kyocera-neu: Kyocera Mita FS-1020D Kyocera: Kyocera Mita FS-1020D Kyocera_FS-1020D: Kyocera Mita FS-1020D device for FS-1020D: usb://Kyocera/FS-1020D?serial=XAX5560374 device for Kyocera_FS-1020D: usb://Kyocera/FS-1020D?serial=XAX5560374 == Installed versions of important printing packages == ii cups-ppdc1.5.2-5 Common UNIX Printing System(tm) - PPD manipulation utilities ii foomatic-filters 4.0.12-1 OpenPrinting printer support - filters ii gs-cjk-resource 1.20100103-3 Resource files for gs-cjk, ghostscript CJK-TrueType extension ii hp-ppd 0.9-0.2 HP Postscript Printer Definition (PPD) files ii hpijs3.11.12-2 transitional dummy package for hpijs printer driver ii libcupsppdc1 1.5.2-5 Common UNIX Printing System(tm) - PPD manipulation library ii printer-driver-gutenprint5.2.7-5 printer drivers for CUPS ii system-config-printer1.3.7-3 graphical interface to configure the printing system Created with printingbuginfo script v1.5 (https://wiki.ubuntu.com/PrintingBugInfoScript) Thu, 08 Mar 2012 20:54:48 +0100 d) 1. Connected, powered on (on not working foomatic version) 2. root@sneo:/tmp# lsmod | grep usb usblp 12593 0 usbhid 30418 0 3.-5: tail -f /var/log/syslog Mar 8 20:56:27 sneo kernel: usblp0: removed Mar 8 20:56:46 sneo kernel: usb 4-5.2: new full-speed USB device number 4 using ohci_hcd Mar 8 20:56:46 sneo kernel: usblp0: USB Bidirectional printer dev 4 if 0 alt 0 proto 2 vid 0x0482 pid 0x000E Mar 8 20:56:46 sneo mtp-probe: checking bus 4, device 4: "/sys/devices/pci:00/:00:12.0/usb4/4-5/4-5.2" Mar 8 20:56:46 sneo mtp-probe: bus: 4, device: 4 was not an MTP device Mar 8 20:56:47 sneo udev-configure-printer: add /devices/pci:00/:00:12.0/usb4/4-5/4-5.2/4-5.2:1.0 Mar 8 20:56:47 sneo udev-configure-printer: device devpath is /devices/pci:00/:00:12.0/usb4/4-5/4-5.2 Mar 8 20:56:47 sneo udev-configure-printer: Device already handled Mar 8 20:56:47 sneo udev-configure-printer:
Bug#662025: foomatic-filters: Fails to print if 4.0.12-1 or 4.0.13-1 is installed
I do not see any problem with your PPD. I can print with it on my HP PostScript printers without problem. Can you print with the manufacturer-supplied PPD file? The manufacturer-supplied PPD sends some PJL directives to the printer before sending the PostScript code. Perhaps the Kyocera printers need this. Till On 03/09/2012 04:47 PM, Helge Kreutzmann wrote: Hello Till, On Thu, Mar 08, 2012 at 10:22:33PM +0100, Till Kamppeter wrote: I have checked your error_log and it shows one job which has successfully completed. I assume that this is the job which did not print for you. Yes. First, a reasonable amount of data gets sent to the printer but it does not make the printer printing something. Second, your attached error_log has only the following part which looks strange: -- D [08/Mar/2012:21:04:00 +0100] [Job 233] Options from the PPD file: D [08/Mar/2012:21:04:00 +0100] [Job 233] D [08/Mar/2012:21:04:00 +0100] [Job 233] D [08/Mar/2012:21:04:00 +0100] [Job 233] D [08/Mar/2012:21:04:00 +0100] [Job 233] File: D [08/Mar/2012:21:04:00 +0100] [Job 233] D [08/Mar/2012:21:04:00 +0100] [Job 233] -- This makes the impression that foomatic-rip did not read any options from the PPD file. Please run the command ls -l /etc/cups/ppd/FS-1020D.ppd root@sneo:~# ls -l /etc/cups/ppd/FS-1020D.ppd -rw-r--r-- 1 root root 9777 Aug 28 2011 /etc/cups/ppd/FS-1020D.ppd root@sneo:~# ls -l /etc/cups/ppd/* -rw-r--r-- 1 root root 9777 Aug 28 2011 /etc/cups/ppd/FS-1020D.ppd -rw-r--r-- 1 root root33401 Aug 28 2011 /etc/cups/ppd/Kyocera_FS-1020D.ppd -rw-r--r-- 1 root lpadmin 33421 Okt 15 2008 /etc/cups/ppd/Kyocera-neu.ppd -rw-r--r-- 1 root lpadmin 33421 Aug 4 2005 /etc/cups/ppd/Kyocera.ppd and attach your /etc/cups/ppd/FS-1020D.ppd file. Done. Thanks. Till On 03/08/2012 09:19 PM, Helge Kreutzmann wrote: Hello, On Mon, Mar 05, 2012 at 12:32:02PM +0100, Till Kamppeter wrote: We need some more information about your problem. First, can you tell us which printer (manufacturer/model), connection type (USB, Kyocera Ecosys FS-1020D, now connected via USB (used to be parallel, I still have the conection wired to the old (shut down) machine). Parallel, USB->Parallel adapter, network, ...), driver you are using? Driver?? None specifilly. Or do you men ppd file? Can you also follow the instructions of the sections "CUPS error_log" and "Capturing print job data" on https://wiki.ubuntu.com/DebuggingPrintingProblems. The site is for Ubuntu, but the steps of the mentioned sections also work under Debian. If "sudo" does not work or if some administrative command of CUPS does not work, run the command in a second terminal window where you get root via "su -", without the "sudo " in the beginning. Ok. Note that we need this information to be able to fix the bug. Fine. a) There is no »ubuntu-bug« within Debian main (testing). b) apport-collect does not exist neither c) Output of printdebuginfo: == System information == Ubuntu Release : testing (wheezy) Desktop Environment: none Architecture : x86_64 Kernel : 3.2.9sneo.01-grsec Locale : LANG=de_DE.UTF-8, LC_CTYPE=de_DE.UTF-8, LC_PAPER=de_DE.UTF-8 /etc/papersize : a4 == Configured printers == FS-1020D: Kyocera FS-1020D Foomatic/Postscript Kyocera-neu: Kyocera Mita FS-1020D Kyocera: Kyocera Mita FS-1020D Kyocera_FS-1020D: Kyocera Mita FS-1020D device for FS-1020D: usb://Kyocera/FS-1020D?serial=XAX5560374 device for Kyocera_FS-1020D: usb://Kyocera/FS-1020D?serial=XAX5560374 == Installed versions of important printing packages == ii cups-ppdc1.5.2-5 Common UNIX Printing System(tm) - PPD manipulation utilities ii foomatic-filters 4.0.12-1 OpenPrinting printer support - filters ii gs-cjk-resource 1.20100103-3 Resource files for gs-cjk, ghostscript CJK-TrueType extension ii hp-ppd 0.9-0.2 HP Postscript Printer Definition (PPD) files ii hpijs3.11.12-2 transitional dummy package for hpijs printer driver ii libcupsppdc1 1.5.2-5 Common UNIX Printing System(tm) - PPD manipulation library ii printer-driver-gutenprint5.2.7-5 printer drivers for CUPS ii system-config-printer1.3.7-3 graphical interface to configure the printing system Created with printingbuginfo script v1.5 (https://wiki.ubuntu.com/PrintingBugInfoScript) Thu, 08 Mar 2012 20:54:48 +0100 d) 1. Connected, powered on (on not working foomatic version) 2. root@sneo:/tmp# lsmod | gr
Bug#662025: foomatic-filters: Fails to print if 4.0.12-1 or 4.0.13-1 is installed
Please set up a print queue with this PPD: http://www.openprinting.org/ppd-o-matic.php?driver=Postscript-Kyocera&printer=Kyocera-FS-1020D Can you print then? Till -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#663192: [Pkg-cups-devel] Bug#663192: cups-filters: Please add support for embedding of Opentype fonts
Patches are welcome. Can OpenType be embedded in a PDF? Or would we need to convert such a font? Till -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#663192: [Pkg-cups-devel] Bug#663192: cups-filters: Please add support for embedding of Opentype fonts
There are not really time constraints. For Ubuntu Precise 12.04 cups-filters 1.0.5 with texttopdf being fully fontconfig-based is enough. Precise comes with suitable TTF fonts. Currently, the change is more thought for upstream to be prepared for the first distros which drop TTF fonts. Till -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#662025: foomatic-filters: Fails to print if 4.0.12-1 or 4.0.13-1 is installed
Note that the new PPD I suggested does not use foomatic-rip, it should work (or not work) independent of the foomatic-filters version installed. The piece of error_log you pasted showed only some USB timeouts. Whether they actually prevent your printer from printing is not known. To determine whether valid PostScript data reaches the backend, you need to clone your print queues into queues pointing into a file. Run the command cupsctl FileDevice=yes then do for each print queue: lpadmin -p -file -E -v file:/tmp/printout- -P /etc/cups/ppd/.ppd Replacs by the actual queue name. Print into the clone queues, always the same input file, a file which showed the problem for you. Make the resulting files readable for normal users: chmod 777 /tmp/printout* Examine the files to see whether they contain valid PostScript, have PJL commands in the beginning, ... Note that if they have PJL commands in the beginning, evince cannot display their PostScript part on the screen but gv can. Are the files OK or are they already without printable data? If they contain printable data, print them unfiltered to the original queues: lpr -P -oraw /tmp/printout- For the foomatic-filters case (Foomatic/Postscript queue), do this with both the old and the new foomatic-filters with the same input file and attach the /tmp/printout- files once the one which prints of the old foomatic-filters and second, the one which does not print of the new foomatic-filters. On 03/11/2012 10:32 AM, Helge Kreutzmann wrote: Hello Till, On Fri, Mar 09, 2012 at 08:05:20PM +0100, Till Kamppeter wrote: Please set up a print queue with this PPD: http://www.openprinting.org/ppd-o-matic.php?driver=Postscript-Kyocera&printer=Kyocera-FS-1020D Did so. The PPD seems to be the English version of one I already have installed (a Diff confirms this, only some "terms" are translated). Can you print then? No, not with current foomatic-filters: ii foomatic-filters 4.0.12-1 OpenPrinting printer support - filters Error log excerpt (lpstat of that user is still showing the job, btw., lpq does not show anything): D [11/Mar/2012:10:05:06 +0100] cupsdReadClient: 16 POST / HTTP/1.1 D [11/Mar/2012:10:05:06 +0100] cupsdSetBusyState: newbusy="Active clients, printing jobs, and dirty files", busy="Printing jobs and dirty files" D [11/Mar/2012:10:05:06 +0100] cupsdAuthorize: No authentication data provided. D [11/Mar/2012:10:05:06 +0100] cupsdReadClient: 16 1.1 Get-Jobs 1 D [11/Mar/2012:10:05:06 +0100] Get-Jobs ipp://localhost/ D [11/Mar/2012:10:05:06 +0100] Returning IPP successful-ok for Get-Jobs (ipp://localhost/) from localhost D [11/Mar/2012:10:05:06 +0100] cupsdSetBusyState: newbusy="Printing jobs and dirty files", busy="Active clients, printing jobs, and dirty files" D [11/Mar/2012:10:05:06 +0100] cupsdReadClient: 16 WAITING Closing on EOF D [11/Mar/2012:10:05:06 +0100] cupsdCloseClient: 16 D [11/Mar/2012:10:05:06 +0100] cupsdSetBusyState: newbusy="Printing jobs and dirty files", busy="Printing jobs and dirty files" I [11/Mar/2012:10:05:09 +0100] Saving job.cache... D [11/Mar/2012:10:05:09 +0100] cupsdSetBusyState: newbusy="Printing jobs", busy="Printing jobs and dirty files" D [11/Mar/2012:10:05:15 +0100] [Job 237] Wrote 8192 bytes of print data... D [11/Mar/2012:10:05:15 +0100] [Job 237] Read 8192 bytes of print data... D [11/Mar/2012:10:05:23 +0100] cupsdAcceptClient: 16 from localhost (Domain) D [11/Mar/2012:10:05:23 +0100] cupsdReadClient: 16 POST / HTTP/1.1 D [11/Mar/2012:10:05:23 +0100] cupsdSetBusyState: newbusy="Active clients and printing jobs", busy="Printing jobs" D [11/Mar/2012:10:05:23 +0100] cupsdAuthorize: No authentication data provided. D [11/Mar/2012:10:05:23 +0100] cupsdReadClient: 16 1.1 Get-Jobs 1 D [11/Mar/2012:10:05:23 +0100] Get-Jobs ipp://localhost/ D [11/Mar/2012:10:05:23 +0100] Returning IPP successful-ok for Get-Jobs (ipp://localhost/) from localhost D [11/Mar/2012:10:05:23 +0100] cupsdSetBusyState: newbusy="Printing jobs", busy="Active clients and printing jobs" D [11/Mar/2012:10:05:23 +0100] cupsdReadClient: 16 WAITING Closing on EOF D [11/Mar/2012:10:05:23 +0100] cupsdCloseClient: 16 D [11/Mar/2012:10:05:23 +0100] cupsdSetBusyState: newbusy="Printing jobs", busy="Printing jobs" D [11/Mar/2012:10:05:26 +0100] cupsdAcceptClient: 16 from localhost (Domain) D [11/Mar/2012:10:05:26 +0100] cupsdReadClient: 16 POST / HTTP/1.1 D [11/Mar/2012:10:05:26 +0100] cupsdSetBusyState: newbusy="Active clients and printing jobs", busy="Printing jobs" D [11/Mar/2012:10:05:26 +0100] cupsdAuthorize: No authentication data provided. D [11/Mar/2012:10:05:26 +0100] cupsdReadClient: 16 1.1 Get-Jobs 1 D [11/Mar/2012:10:05:26 +0100] Get-Jobs ipp://localhost/ D [11/Mar/201
Bug#663554: Nags me to install proprietary plug-in although printer works
In the SVN repository for the Debian packaging of HPLIP I have already deactivated HPLIP's automatic pop-up for the firmware installation as it happens with every LaserJet printer (also my PostScript printers which for sure work without plugin). So the next HPLIP package in Debian will have the problem solved. Till -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#663554: Nags me to install proprietary plug-in although printer works
Quick workaround: Remove the file /lib/udev/rules.d/86-hpmud_plugin.rules Till -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#663564: [Pkg-cups-devel] Bug#663564: Acknowledgement (cups-filters: 'make clean' leaves some object files over)
Fabian, thank you for the patch. I have applied your second patch to the upstream BZR repository now. It will be incluced from cups-filters 1.0.6 on. Till On 03/12/2012 10:53 AM, Fabian Greffrath wrote: An alternative approach, maybe less intrusive: Instead of touching Makedefs, define the correct actual dependency in the top-level Makefile. This will cause configure to be run when 'make distclean' is called twice in a row, which is a bit tedious, but at least it's not a hack anymore but a solution. ;) -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#660420: Some Postscript printer drivers (Kyocera, Brother, maybe others) do not work anymore
This bug I have fixed with cups-filters 1.0.5-1. This version inserts code snippets into PostScript output for Kyocers and Brother PostScript printers to work around the incompatibilities/PS interpreter bugs. Till -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#660348: Bug#660420: cups: Prints one blank sheet regardless of document size (Brother HL-5240)
This bug I have fixed with cups-filters 1.0.5-1. This version inserts code snippets into PostScript output for Kyocers and Brother PostScript printers to work around the incompatibilities/PS interpreter bugs. Till -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#663868: Blacklisting usblp helps
Please remove the blacklisting for usblp, run # modprobe usblp set CUPS into debug mode: # cupsctl LogLevel=debug and then turn off and turn on the printer again. Does it load its firmware? If not, attach your /var/log/cups/error_log file. Till -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#669166: Regression: blurry print on HP LaserJet Pro 1102w with foo2zjs since 1.0.16-1.
Please follow the instructions of the sections "CUPS error_log" and "Capturing print job data" on https://wiki.ubuntu.com/DebuggingPrintingProblems. The instructions are for Ubuntu but should also work under Debian. If "sudo " does not work for you to run commands as root, open a second terminal window where you get root (command "su -") and run the sudo-preceded commands there, leaving out the "sudo " in the beginning. Also attach scans or photos which show a currect printout and a blurred printout. Thanks. Till -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#636801: argyll and libicc2 packages are based on same tarball, they should get merged
Package: argyll Version: 1.3.0-3 The packages argyll and libicc2 are both taking their source code from the upstream source tarball of Argyll. Having two (or more) different packages based on the same source code tarball one will easily get into a maintenance nightmare. If a security vulnerability shows up in the upstream code, all packages based on it need their upstream tarball be updated and rebuilt. One can easily forget one package and so the vulnerability stays in the forgotten package. I am introducing Color Management in Ubuntu and therefore I have updated the Argyll package to version 1.3.3 and also created a merged package (but not uploaded to Ubuntu). You can download it here: http://www.openprinting.org/download/tmp/argyll_1.3.3.orig.tar.gz http://www.openprinting.org/download/tmp/argyll_1.3.3-0ubuntu2.dsc http://www.openprinting.org/download/tmp/argyll_1.3.3-0ubuntu2.debian.tar.gz Problem is that the version number used for libicc is the API/ABI version number 2.12 which is much higher than the 1.3.3 of the upstream tarball. Ho should I proceed to make the resulting package being well accepted by Debian? Should I introduce an epoch? Or can a binary package have another version number than its source package? The mentioned package uses an epoch, but please tell me how to do it correctly. the merged package builds Argyll using the upstream Jam architecture, this makes maintenance much easier than with a packager-supplied autoconf/automake environment. Only libicc is built in a separate directory using the very simple autoconf/automake files from the former libicc2 package. This is done because the Jam environment has no functionality to create shared libraries. The package is a merger of Ubuntu packages, therefore it has Ubuntu release numbers, change them if you want to use this package in Debian. Till -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#637184: libjpeg6b linked with "-Bsymbolic-functions", causing problems with HPLIP and pxljr
Package: libjpeg6b
Version: 6b1-2
In the last months Ubuntu users complained that their HP Color LaserJet
3500/3550/3600 does not print any more in the draft and normal printout
quality modes but still print in high quality mode. In the draft and
normal modes the printer uses JPEG compression for the image data, to
make the data transfer faster. The drivers, pxljr and hplip, use
libjpeg6b to implement the data compression, but as the printer's JPEG
format is not absolutely identical with the standard JPEG format, the
driver overrides certain symbols/functions of libjpeg with its own code
to implement the differences between standard JPEG and the printer's
JPEG. This is done in both the pxljr and hplip drivers.
Since some time LDFLAGS is set to "-Wl,-Bsymbolic-functions" by default
for package builds in Debian and this flag makes ashared library linked
with it disallowing the override of its symbols, breaking the pxljr and
hplip drivers, leading to the JPEG-based modes not working.
So as a fix, the upstream author of the pxljr driver, suggests to build
libjpeg without LDFLAGS being set to "-Wl,-Bsymbolic-functions". I tried
it by preceeding the "./configure" in debian/rules by "LDFLAGS= " and
this libjpeg made the two printer drivers working perfectly in draft and
normal quality modes.
I have attached a patch for the Ubuntu package showing how the fix looks
like. Can you please apply the same fix to the Debian package?
Till
diff -Nru libjpeg6b-6b1/debian/changelog libjpeg6b-6b1/debian/changelog
--- libjpeg6b-6b1/debian/changelog 2011-03-24 06:24:32.0 +0100
+++ libjpeg6b-6b1/debian/changelog 2011-08-08 19:57:41.0 +0200
@@ -1,3 +1,11 @@
+libjpeg6b (6b1-1ubuntu2) oneiric; urgency=low
+
+ * debian/rules: Remove "-Bsymbolic-functions" from LDFLAGS, as this flag
+breaks the libjpeg use by HPLIP and pxljr, in both cases for printing
+on the HP Color LaserJet 3500/3550/3600 (LP: #777670).
+
+ -- Till Kamppeter Mon, 8 Aug 2011 19:57:23 +0200
+
libjpeg6b (6b1-1ubuntu1) natty; urgency=low
* Enable multiarch build (LP: #733501)
diff -Nru libjpeg6b-6b1/debian/rules libjpeg6b-6b1/debian/rules
--- libjpeg6b-6b1/debian/rules 2011-03-24 06:24:00.0 +0100
+++ libjpeg6b-6b1/debian/rules 2011-08-08 20:09:36.0 +0200
@@ -20,7 +20,7 @@
build: build-stamp
build-stamp:
dh_testdir
- ./configure --prefix=/usr --mandir=/usr/share/man \
+ LDFLAGS= ./configure --prefix=/usr --mandir=/usr/share/man \
--libdir=\$${prefix}/lib/$(DEB_HOST_MULTIARCH) \
--enable-static --enable-shared --enable-maxmem=1024 \
--build=$(DEB_BUILD_GNU_TYPE) --host=$(DEB_HOST_GNU_TYPE)
Bug#637184: libjpeg6b linked with "-Bsymbolic-functions", causing problems with HPLIP and pxljr
Martin Pitt asked me to report the bug also to Debian. He told the situation there is the same. HPLIP is indeed build-depending on libjpeg-dev and not on libjpeg62-dev. I for got that I did this change, as I only checked binary package dependencies and it seems that in Ubuntu the libjpeg-dev has still pulled libjpeg62-dev. If simply building HPLIP against the new libjpeg would also fix the printing problem would be great. Someone should test that. Till -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#649991: [Pkg-hpijs-devel] Bug#649991: Please rename the hplip packages to the printer-driver- convention
Thanks for the patch. The patch is not complete. The "hplip-data" binary package contains the PPD files for HP's PostScript printers, so the "hplip" package is also a printer driver. The PPD updater is in "hplip" (a packaging bug). So there should be a new binary package named "printer-driver-hp-postscript", containing these PPDs (current file /usr/lib/cups/driver/hplip, should then be /usr/lib/cups/driver/hp-postscript) and the corresponding PPD updater. The "hpijs-ppds" package is not needed by CUPS as CUPS auto-generates the PPDs based on the .drv file in the "hpijs" binary package. "hpijs-ppds" is only needed for non-CUPS spoolers which cannot cope with a .drv file. WDYT, should "hpijs-ppds" also be renamed to "printer-driver-..."? Should it keep its name? Or should it get dropped? Till -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#649991: [Pkg-hpijs-devel] Bug#649991: Please rename the hplip packages to the printer-driver- convention
On 01/05/2012 01:36 PM, Didier Raboud wrote: On Thu, 05 Jan 2012 13:16:15 +0100, Till Kamppeter wrote: I based my patch on the summary I did both there [0] and when filing the bug [1], both which didn't get reactions. [0] http://lists.debian.org/debian-printing/2011/11/msg00017.html [1] http://lists.debian.org/debian-printing/2011/11/msg00050.html My main question is "does hplip serve as printer driver for CUPS?", as the main reasoning behind the printer-driver-* naming scheme is to have them all installed in a standard installation involving cups. A binary package containing PPDs for PostScript printers is a printer driver, the driver for the PostScript mode of these printers. Note that a PostScript printer driver usually consists of only PPD files. A printer driver package has to contain at least PPDs (the files itself, the PPDs pyppd-compressed, or a PPD generator, either an executable in /usr/lib/cups/driver/ or a .drv file in /usr/share/cups/drv/) and the PPD updater for these PPDs (to update PPDs of existing queues, either in postinst script or a file in /usr/share/cups/ppd-updaters/). In addition, it must contain all filters specified in the cupsFilter lines of the PPDs and their dependencies or depend on the packages containing these filters. My suggestion is to create a new binary package named printer-driver-postscript-hp containing the pyppd-compressed PostScript PPD files (move from hplip-data) plus the PPD updater (move from hplip) to get consistency. The driver name for this new package is Postscript-HP (to be consistent with PostScript driver entry names on OpenPrinting) and not hplip any more, so the files should have appropriate names. printer-driver-postscript-hp should recommend the hplip package, as hplip gives extra functionality (like toner level check) to the PostScript printers but the printers work also without the hplip package installed. There are no PostScript PPDs with valid cupsFilter lines requiring filter executables from the hplip package. (As a side note, I think we'll end up having two classes of printer-driver-* packages: the ones installed trough recommends and the ones only suggested by printer-driver-all, but that's yet to be discussed.) So there should be a new binary package named "printer-driver-hp-postscript", containing these PPDs (current file /usr/lib/cups/driver/hplip, should then be /usr/lib/cups/driver/hp-postscript) and the corresponding PPD updater. Sounds sane, Lets name the "new" driver Postscript-HP and the package printer-driver-postscript-hp, to be consistent with OpenPrinting. The "hpijs-ppds" package is not needed by CUPS as CUPS auto-generates the PPDs based on the .drv file in the "hpijs" binary package. "hpijs-ppds" is only needed for non-CUPS spoolers which cannot cope with a .drv file. WDYT, should "hpijs-ppds" also be renamed to "printer-driver-..."? Should it keep its name? Or should it get dropped? Certainly not printer-driver-*, and I don't see a value in dropping it, hence let's keep it as is. OK, the hpijs-ppds package is not part of the standard CUPS printing environment, so we do not rename it. P.S. Do you want me to provide a new patch or will you work on it (I don't mind preparing it, just say.)? OK, please provide a new patch. Thanks you very much. Till -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#649991: [Pkg-hpijs-devel] Bug#649991: Please rename the hplip packages to the printer-driver- convention
OdyX, thank you for the patch. I have reviewed it and applied it now to the SVN repository of HPLIP and uploaded the new package to Ubuntu (Precise). Till -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#650068: cups-pdf: PDF created are all void without error notice
Eric, can you follow the instructions of the sections "CUPS error_log" and "Capturing print job data" of https://wiki.ubuntu.com/DebuggingPrintingProblems and attach the resulting files uncompressed and as separate attachments? Note that these instructions were created for Ubuntu, but the printing stack of Debian is similar enough so that the instructions of said sections should also work for Debian. Till -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#630227: cups 1.4.6-8 does not support usblp anymore, breaking foo2zjs
An update of foo2zjs to do the firmware transfer without usblp is planned, at least for Debian and Ubuntu. I will create an appropriate package soon. -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#630228: foo2zjs: Firmware upload is not compatible with cups
On 06/12/2011 04:03 PM, Didier Raboud wrote: I'm hereby CC'ing the CUPS maintainers; opinions ? I know about that problem and I will update the firmware upload script in the foo2zjs package soon, so that it also works with libusb. Till -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#630228: Info received (Bug#630228: foo2zjs: Firmware upload is not compatible with cups)
The fix is simple. The firmware uploader script needs to determine
whether usblp is loaded or not, and if it is not loaded and the CUPS
filter /usr/lib/cups/filter/usb exists, it should run a command line
like this ("1020" replaced by actual model number):
for uri in `sudo /usr/lib/cups/backend/usb | grep -i
'HP.*LaserJet.*1020' | grep -v FWVER | cut -d ' ' -f 2`; do echo $uri;
sudo DEVICE_URI="$uri" /usr/lib/cups/backend/usb 1 1 1 1 ''
/lib/firmware/hp/sihp1020.dl; done
This goes through all devices of the given model which do not have
firmware loaded yet and load the firmware into them using the "usb" CUPS
backend. As the usblp module is blacklisted by the CUPS package, this is
sufficient to solve the problem.
Till
--
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#630228: foo2zjs: Firmware upload is not compatible with cups
On 06/12/2011 05:29 PM, Roger Leigh wrote: Why is this not being done at a lower level, e.g. via udev or other existing hotplug mechanisms? Firmware-loading for /any/ device is not the remit of cups, and it's really not cups' call to disable any module loading. Do you know a tool which can send the firmware file to a raw libusb device, so that using the CUPS backend for this is not necessary? Note that upstream CUPS is only to be able to access the USB printers with one method, either usblp or libusb, not both. I suggested to use my patch for getting a hybrid usb backend upstream but Mike Sweet do not want to use it, he tells, usblp should be deprecated and only libusb should be used. libusb is also the better method for modern multi-function devices. Especially HP uses libusb in their "hp" CUPS backend. So for a better consistency it is better to use only libusb in CUPS environments. Therefore I want to deprecate usblp and switch software which still use it to use libusb. Till -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#630228: foo2zjs: Firmware upload is not compatible with cups
I have now updated the Ubuntu package (20110210dfsg-1ubuntu4) applying
the attached patch. The patch modifies the firmware upload script
hplj1000. It adds support for douing the firmware upload through the
"usb" backend of CUPS. This makes the upload independent of the presence
of usblp. It works also with the new libusb-based CUPS package.
Till
Index: foo2zjs-20110210dfsg/hplj1000
===
--- foo2zjs-20110210dfsg.orig/hplj1000 2011-06-14 16:30:59.331940282 +0200
+++ foo2zjs-20110210dfsg/hplj1000 2011-06-14 16:31:26.151976656 +0200
@@ -48,6 +48,12 @@
DEV=""
#
+# Path to the USB CUPS backend. We use this backend to upload the firmware
+# into the printer when we are on a CUPS/libusb-based system.
+#
+USB_BACKEND=/usr/lib/cups/backend/usb
+
+#
# Directory to find downloadable HP firmware files sihp.dl
#
FWDIR=/lib/firmware/hp
@@ -195,7 +201,7 @@
esac
#
-# Procedure to load a single device with firmware
+# Procedures to load a single device with firmware
#
load1() {
_dev="$1"
@@ -218,6 +224,33 @@
return 0
}
+load2() {
+fw="$FWDIR/sihp$FWMODEL.dl"
+if [ ! -f "$fw" ]; then
+ log "Missing HP LaserJet $MODEL firmware file $fw"
+ log "...read foo2zjs installation instructions and run ./getweb $MODEL"
+ return 1
+fi
+
+log "loading HP LaserJet $MODEL firmware $fw to CUPS USB device ..."
+# There is a timeout problem with udev and FC4, so spin it off.
+(
+ device_found=0
+ for uri in `$USB_BACKEND 2> /dev/null | grep -i 'HP.*LaserJet.*'"$MODEL" | grep -v FWVER | cut -d ' ' -f 2`; do
+ device_found=1
+ if DEVICE_URI="$uri" /usr/lib/cups/backend/usb 1 1 1 1 '' $fw 2> /dev/null; then
+ log "$uri... download successful."
+ else
+ log "$uri... download failed."
+ fi
+ done
+ if [ $device_found = 0 ]; then
+ log "... no devices which need firmware found."
+ fi
+) &
+return 0
+}
+
#
# OK, now download firmware to any printers that need it
#
@@ -226,6 +259,13 @@
# force downloading to a specific device
#
load1 "$DEV"
+elif [ -x $USB_BACKEND ]; then
+#
+# If we have CUPS installed, use the CUPS "usb" backend, as then we do
+# not need to care whether the system uses the usblp kernel module or
+# libusb
+#
+load2
elif [ -x $PRINTERID ]; then
#
# Sniff around for printers that need a firmware download
@@ -247,5 +287,5 @@
done
else
log "HP LaserJet $MODEL firmware was not downloaded..."
-log "...couldn't find $PRINTERID and DEV is not set"
+log "...couldn't find $PRINTERID, DEV is not set, and CUPS not installed."
fi
Bug#630228: foo2zjs: Firmware upload is not compatible with cups
Small fix done on the patch ...
Till
Index: foo2zjs-20110210dfsg/hplj1000
===
--- foo2zjs-20110210dfsg.orig/hplj1000 2011-06-14 16:30:59.331940282 +0200
+++ foo2zjs-20110210dfsg/hplj1000 2011-06-14 16:31:26.151976656 +0200
@@ -48,6 +48,12 @@
DEV=""
#
+# Path to the USB CUPS backend. We use this backend to upload the firmware
+# into the printer when we are on a CUPS/libusb-based system.
+#
+USB_BACKEND=/usr/lib/cups/backend/usb
+
+#
# Directory to find downloadable HP firmware files sihp.dl
#
FWDIR=/lib/firmware/hp
@@ -195,7 +201,7 @@
esac
#
-# Procedure to load a single device with firmware
+# Procedures to load a single device with firmware
#
load1() {
_dev="$1"
@@ -218,6 +224,33 @@
return 0
}
+load2() {
+fw="$FWDIR/sihp$FWMODEL.dl"
+if [ ! -f "$fw" ]; then
+ log "Missing HP LaserJet $MODEL firmware file $fw"
+ log "...read foo2zjs installation instructions and run ./getweb $MODEL"
+ return 1
+fi
+
+log "loading HP LaserJet $MODEL firmware $fw to CUPS USB device ..."
+# There is a timeout problem with udev and FC4, so spin it off.
+(
+ device_found=0
+ for uri in `$USB_BACKEND 2> /dev/null | grep -i 'HP.*LaserJet.*'"$MODEL" | grep -v FWVER | cut -d ' ' -f 2`; do
+ device_found=1
+ if DEVICE_URI="$uri" $USB_BACKEND 1 1 1 1 '' $fw 2> /dev/null; then
+ log "$uri... download successful."
+ else
+ log "$uri... download failed."
+ fi
+ done
+ if [ $device_found = 0 ]; then
+ log "... no devices which need firmware found."
+ fi
+) &
+return 0
+}
+
#
# OK, now download firmware to any printers that need it
#
@@ -226,6 +259,13 @@
# force downloading to a specific device
#
load1 "$DEV"
+elif [ -x $USB_BACKEND ]; then
+#
+# If we have CUPS installed, use the CUPS "usb" backend, as then we do
+# not need to care whether the system uses the usblp kernel module or
+# libusb
+#
+load2
elif [ -x $PRINTERID ]; then
#
# Sniff around for printers that need a firmware download
@@ -247,5 +287,5 @@
done
else
log "HP LaserJet $MODEL firmware was not downloaded..."
-log "...couldn't find $PRINTERID and DEV is not set"
+log "...couldn't find $PRINTERID, DEV is not set, and CUPS not installed."
fi
Bug#530600: Lexmark printer tray selection problem - Optra T series
Ruediger, can you attach the PPD files for the print queues with the bad behavior? The files are /etc/cups/ppd/.ppd. Please attach the PPDs to your answer as separate uncompressed files. Thanks. Till -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#530600: Lexmark printer tray selection problem - Optra T series
I have updated the upstream BZR repository of foomatic-db and the OpenPrinting web site now replacing all the tray names in the manufacturer-independent "InputSlot" options by names without tray numbers. The tray numbering can differ from manufacturer to manufacturer. Ruediger has sent me the PPDs I asked for in private and they were all for the Foomatic/Postscript driver, which means that they are generic PostScript PPDs generated from the Foomatic XML files and not manufacturer-supplied PPDs. The new tray names will appear in the next foomatic-db package. For the time being use either PPD files supplied by Lexmark (highly recommended, in the openprinting-ppds package or on the OpenPrinting web site) or the PPD files of the "Postscript" driver entry on the OpenPrinting web site. Till -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#628573: hplip bonjour breaks for some hp printers (e.g. Photosmart D110a)
Can you report you problem to the HPLIP developers at HP, at https://launchpad.net/hplip/? Thanks. Till -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#613408: ghostscript: prints extra blank page
You can use the "cupsfilter" utility to run filter chains manually to find out which filter breaks things. Till On 02/15/2011 12:44 AM, Jonathan Nieder wrote: Hi Brian, brian m. carlson wrote: When I print a file with ghostscript 9, I always get a blank page printed first. Then my document prints normally. [...] The printer I am using is an Officejet 4500. I also see this problem with a Deskjet 5740. Both of these printers use the hplip/hpijs functionality, although one uses the full hplip (with the hp backend) and the other uses just the ppds (with the usb backend); these printers are on two different machines. While this is not terrible, it is inconvenient and quite irksome when I'm printing twenty copies of something. Cc-ing the hplip maintainers for ideas. What would be most useful for debugging: do you know any way to detect the blank page in the output (using gs -sOutputFile) without using an actual printer? With that information, it should be possible to bisect using the upstream ghostscript repo[1]. Thanks for reporting, Jonathan [1] git://git.ghostscript.com/ghostscript.git -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#594322: [Foo2zjs-maintainer] Bug#594322: foo2zjs: Please upgrade to more recent version for Squeeze.
On 11/05/2010 04:10 AM, Luca Capello wrote: Hi there! On Wed, 13 Oct 2010 02:21:35 +0200, Luca Capello wrote: On Mon, 27 Sep 2010 23:16:49 +0200, Till Kamppeter wrote: On 09/27/2010 06:53 PM, Luca Capello wrote: 4) I am not sure debian/local/ is the right place for non-upstream files, but I should admit that this is the first time I heard about it and I can not find any documentation about that. Nevermind, I have added the two non-upstream PPDs. BTW, conceptually speaking, Ubuntu debian/rules misses the command to compress these two files, given that this action is hidden in the 'Add "*cupsFilter" line to accept PDF input data to the PPDs' block. Please go ahead and correct also this. I will overtake the version with your corrections to Ubuntu. Given that I still have not understood what the 'Add "*cupsFilter" line...' does, no corrections on this matter have been made yet. Still valid. This makes the PPD files allow PDF as input format. This way the print queues integrate with the PDF-based printing workflow which is implemented in Debian and Ubuntu. PDF-based printing workflow means that applications send PDF (and not PostScript any more) to CUPS when the user prints his document. CUPS uses PDF as standard file format. Everything coming in which is not PDF (like PostScript output of legacy applications) is turned to PDF at first, then a pdftopdf filter does rearrangement of the pages (if the user selected N-up, reverse order, selected pages, ...), and after that PDF is sent to the driver. See https://www.linuxfoundation.org/collaborate/workgroups/openprinting/pdfasstandardprintjobformat I have seen may packages which use debian/local/ to add non-upstream files. 5) - debian/foo2zjs.postinst: Automatically update the PPD files for existing queues to the versions supplied with this package. - debian/control: Add dependency on cups and cups-client to ensure that automatic update of the PPDs of existing print queues works. I do not understand the purpose of this action, but I should admit that I am not a CUPS expert and I do not know how other drivers behave. However, given that in Debian the PPDs are configuration files (see <http://bugs.debian.org/549673>), I would expect dpkg to prompt for any modification, is it so in this case? Still valid. Often the driver has changes which require also changes in the PPD files, for example if options are added or additional settings for an option. If you simply update the package, the driver executables get replaced by the new version and also the PPD files under /usr/share/ppd/, but not the PPD files of already existing print queues in /etc/cups/ppd/. Rick Richardson, the upstream author of foo2zjs simply tells in his ChangeLog to remove and recreate the print queues. Typical distro users neither read the upstream ChangeLog of a package, nor do they not know that their queues need to get manually recreated to make the update complete. They even often do not know that the foo2zjs package is their printer driver. Therefore I let the package do the dirty work as doing a really complete update by letting the postinst script updating the PPDs of the already configured queues in /etc/cups/ppd/. The only configuration in these files are the default settings (lines starting with "*Default..."), The rest of the files are printer-specific and no user configuration. The automatic update is done with CUPS' "lpadmin" command line utility which preserves the default settings. This way the user has always the correct PPD for his driver (works on both up- and downdate of the package) and his default settings do not get lost. Printing will "just work" for him. 10) - debian/rules: Add /etc/papersize support, and modify all /usr/bin/foo2*-wrapper scripts to handle custom page sizes correctly in the PDF-based printing workflow. - debian/rules: Add "*cupsFilter" line to accept PDF input data to the PPDs. - Support for the PDF printing workflow: o "*cupsFilter:" lines for PDF input in the PPDs o Let wrapper scripts read custom page sizes also from the command line and not only from embedded PostScript commands. I do not understand these modifications, would you mind explaining them, please? I do not feel comfortable in applying something I do not understand, sorry... Still valid. There are awkward foo2...-wrapper scripts, all identical except a few lines. Why did Rick not make one file with function definitions, source it into all the foo2...-wrapper scripts and use the functions? This way it is awkward to make patches doing the same change in each of the scripts. Especially more or less once a year (every second Ubuntu release) there is a new driver with a new foo2...
Bug#627770: foomatic-db-engine doesn't work with foomatic-db-compressed-ppds
The concept is the following: The recommended Foomatic setup for end users (and default Foomatic setup on Ubuntu) is foomatic-db-compressed-ppds and foomatic-rip. The pre-built and compressed PPD files in foomatic-db-compressed-ppds take much less space than the Foomatic XML data of foomatic-db and they get also delivered much more quickly on requests by CUPS than the PPD files generated from the XML data by foomatic-db-engine on demand. foomatic-db-engine gets a developer package (like gcc) then. It is only needed to build compressed PPD repositories from Foomatic XML data, so it is only needed to build packages. foomatic-db-engine also makes sense when foomatic-db is not installed, as in the package build scenario one usually has the Foomatic XML data from which one builds the PPD files at another than the usual place, like in the package's source tree or in a temporary directory. This is the case because one builds from the Foomatic data which the package ships or one mixes data from foomatic-db with data from the package, which a package build cannot do in /usr/share/foomatic. To do so, one sets the environment variable FOOMATICDB pointing to the desired XML database and then one calls the tools of foomatic-db-engine. Therefore we only suggest foomatic-db and do not recommend or even require it. The "Provides: foomatic-db" was added to foomatic-db-compressed-ppds for the transition of Ubuntu from foomatic-db/foomatic-db-engine to foomatic-db-compressed-ppds, together with "Conflicts: foomatic-db; Replaces: foomatic-db". In the Google Summer of Code another approach of using the OpenPrinting database (foomatic-db) will get added: The XMLs will be converted to an SQLite database. This is more flexible than the compressed PPDs as one can easily modify the data in the SQL databse, but on the other side it is probably not so compact and fast as the compressed PPDs. Till -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#627542: foo2zjs: Duplex printing option gone
Sam, does your printer have a duplex unit? Or was the duplex option in the PPD files only for activating a manual duplex function? In the latter case the manual duplex function in the driver was replaced by a GUI tool (gnome-manual-duplex) which helps the user to get through the steps and to turn over the printer pages correctly. gnome-manual-duplex is not packaged yet. It needs to be investigated how well it works, whether it supports only local printing or also printing through the network, does not have any security issues, ... and if all is OK it should be packaged. Re-introducing manual duplex by a patch to the PPD file perhaps will not work as the code for manual duplex can be removed from the driver. Till -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#598248: foomatic-db-engine: Takes a long time to spool/print after recent upgrade
I do not see any functional changes between foomatic-db-engine 4.0.4-2 and 4.0.4-3. Can you downgrade to 4.0.4-2 to see whether this fixes your problem? Can you attach your printer's PPD file (in /etc/cups/ppd/) once with 4.0.4-2 installed and once with 4.0.4-3 installed? Which driver are you using? Till -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#594322: [Foo2zjs-maintainer] Bug#594322: foo2zjs: Please upgrade to more recent version for Squeeze.
On 09/27/2010 06:53 PM, Luca Capello wrote: I have some concerns about the Ubuntu package, here the first of them, I will continue on another email as far as the integration progresses. 1) I do not understand why from version 20100210-0ubuntu1 the debian/changelog contains the following: * README.Debian: Updated completely outdated content. We are using the complete original source code again for longer time as there are no binary-only executables and no *.icm files any more in the source tarball. I am sorry but I do not understand why the complete original source code is now DFSG, while nothing changed WRT the files we previously deleted, which from the debian/changelog are: Sorry, the README.Debian did not tell which files exactly were removed and I did not search through the debian/changelog. So I assumed that only these *.icm were offending. - remove binary file c5200mono.prn [...] - remove crd/qpdl/CLP*, because copyright is unclear [...] So let us use a common source tarball again, with the files mentioned by you here removed. Please prepare the package, I will merge that into Ubuntu after the Maverick release. 2) I do not understand why some patches have been merged, like * debian/patches/60-getweb.in.dpatch, debian/patches/80-getweb.in.dpatch: merged 80-getweb.in.dpatch into 60-getweb.in.dpatch. They fixes two different things, and they must be separated. I thought to better have all for getweb in one patch. Feel free to separate out again this one bashism fix. I will overtake your change then when I make my first foo2zjs package after the Maverick release. 3) directory should be created through debian/$PKG.dirs and not by hand in debian/rules (see /usr/lib/cups/filter/). Always about the same issue, the link created by upstream's Makefile is wrong, given it is not a relative one. The correct fix would be to patch upstream's Makefile, but this can be quite tedious especially if upstream changes something. While the best option seems thus to fix it in debian/rules, we should use dh_link and not ln. Please change this appropriately. 4) I am not sure debian/local/ is the right place for non-upstream files, but I should admit that this is the first time I heard about it and I can not find any documentation about that. Nevermind, I have added the two non-upstream PPDs. BTW, conceptually speaking, Ubuntu debian/rules misses the command to compress these two files, given that this action is hidden in the 'Add "*cupsFilter" line to accept PDF input data to the PPDs' block. Please go ahead and correct also this. I will overtake the version with your corrections to Ubuntu. Till -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#598248: foomatic-db-engine: Takes a long time to spool/print after recent upgrade
The 2 PPD files are absolutely identical. Are you sure that you have tested printing the same file in the two cases (please attach the file) and that you have downgraded only foomatic-db-engine (not any other package like foomatic-filters, ghostscript, ...)? Till -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#598639: foomatic-gui/printconf: Not working in modern CUPS environments
Package: foomatic-gui
Version: 0.7.9.3
Severity: serious
The printer setup tools provided by the foomatic-gui source package,
printconf and foomatic-gui are not usable any more in modern CUPS
environments.
There are several problems which make the mentioned printer setup tools
not working with modern CUPS environments.
1. Only PPDs generated by Foomatic are supported. Instead of asking CUPS
for available PPDs/drivers ("lpinfo -l -m" or appropriate IPP request)
it only looks up the local Foomatic XML database in /usr/share/foomatic.
This makes a lot of available drivers not seen:
a. Ready-made PPDs in /usr/share/ppd and subdirectories (PPDs for
PostScript printers supplied by the printer manufacturers, SpliX,
foo2zjs, LSB-based driver packages from OpenPrinting)
b. PPDs supplied via PPD generators in /usr/lib/cups/driver/
(CUPS Raster driver of Gutenprint, compressed PPD file archives of
newer packages, like ijsgutenprint-ppds, foomatic-db-compressed-
ppds)
c. PPD files generated on-the-fly by the CUPS DDK with CUPS DDK .drv
source files in /usr/share/cups/drv/ (HPLIP, CUPS' own PPD files).
So the newest and most sophisticated, especially manufacturer-supplied
drivers are not available through printconf and foomatic-gui. This can
lead to a lot of false bug reports due to "unsupported" printers.
At least for CUPS a printer setup tool should not directly access the
Foomatic XML data. Once, the data is available through the
/usr/lib/cups/driver/foomatic PPD generator, and second, other PPD
sources available to CUPS can be used, without taking care of them
individually.
2. (Only printconf) Use of deprecated device-based USB URIs, like
usb:/dev/usb/lp0. These URIs are not supported by CUPS any more as they
only work if there is only one USB printer connected to the machine. As
soon as there is more than one USB printer print queues (with
model-specific drivers) do not stay assigned to the correct printer
after rebooting. Therefore the new device-ID-based URIs have to be used.
foomatic-gui uses them though.
Possible fixes are:
1. (A lot of work and re-inventing the wheel) Fix the software to poll
the PPD/driver info and the PPDs itself from CUPS when CUPS is in use.
2. Let foomatic-gui and printconf conflict with the "cups" package, so
that they do not get installed on systems where the printing environment
is CUPS.
3. Remove the foomatic-gui package from Debian altogether (recommended
if upstream development has been discontinued).
Recommended replacement for CUPS users is system-config-printer.
Till
--
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#590163: Changes in foomatic-db
To save space, the PPDs in foomatic-db got compressed. They are all compressed in the /usr/lib/cups/driver/openprinting-ppds and /usr/lib/cups/driver/openprinting-ppds-extra files. CUPS extracts needed PPD files automatically.Nothing will change for you if you set up printers with the web interface (http://localhost:631/) or with system-config-printer. For command-line-based printer setup proceed as follows: # lpinfo -m | grep 1320 | grep -i postscript foomatic:HP-LaserJet_1320-Postscript.ppd HP LaserJet 1320 Foomatic/Postscript hplip:HP/hp-laserjet_1320n-ps.ppd HP LaserJet 1320 series Postscript (recommended) # lpadmin -p lj -E -v parallel:/dev/lp0 -m hplip:HP/hp-laserjet_1320n-ps.ppd -o PageSize=A4 -o sides=two-sided-long-edge -D "HP LaserJet 1320" # lpadmin -d lj Note that the "-m" option of lpadmin is used with the PPD URI. The PPD URI is the first word of each output line of "lpinfo -m". Simply copy and paste the PPD URI for your desired printer/driver combo. I suggest these instructions to be added to the documentation for the package (README.debian etc.). -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
