Hm. Can you still confirm that sudo aa-complain cupsd makes your
printer work?
--
After update from Feisty to Gutsy RC, print jobs fail:
/usr/lib/cups/backend/mfp failed
https://bugs.launchpad.net/bugs/152537
You received this bug notification because you are a member of Ubuntu
Bugs, which is
It actually never did.
--
After update from Feisty to Gutsy RC, print jobs fail:
/usr/lib/cups/backend/mfp failed
https://bugs.launchpad.net/bugs/152537
You received this bug notification because you are a member of Ubuntu
Bugs, which is the bug contact for Ubuntu.
--
ubuntu-bugs mailing list
Marco: Ah, then you seem to have a completely different problem. Maybe
you need to update that 'mfp' driver? (wherever it came from); it's not
shipped by Ubuntu, so we cannot do anything about it if it is broken.
Pietro, you reported the bug originally. Does it work for you now?
--
After update
Well yeah, but it was working perfectly untill I updated to gutsy, and
nobody else complains beside people here... Don't really know where to
go :-/
--
After update from Feisty to Gutsy RC, print jobs fail:
/usr/lib/cups/backend/mfp failed
https://bugs.launchpad.net/bugs/152537
You received
I was opening usbview when it gave this error:
cannot open the file /proc/bus/usb/devices
Verify that you have USB compiled into your kernel, have the USB core modules
loaded, and have the usbdevs filesystem mounted.
From lsmod: usbcore 138632 6
I mark this as invalid, since it affects software which is not shipped
in Ubuntu and is unrelated to cups. The original report was about
problems in the AppArmor profile, which have been fixed in Gutsy and
Hardy.
** Changed in: cupsys (Ubuntu Gutsy)
Status: New = Invalid
** Changed in:
MarcoPau: usbview is broken at the moment, see bug 156085. It is
plausible that the mfp driver has the same problem and hasn't been
updated for /dev/bus/usb/. Maybe a newer version is available which will
work with current Linux distros?
--
After update from Feisty to Gutsy RC, print jobs fail:
I'm posting error_log again after activating the debug option in cups.
Hope there's some useful info in it:
D [04/Feb/2008:00:42:15 +] cupsdReadClient: 18 POST /admin HTTP/1.1
D [04/Feb/2008:00:42:15 +] cupsdAuthorize: No authentication data provided.
D [04/Feb/2008:00:42:15 +] [CGI]
If setting the apparmor profile to complain mode still makes it work,
then there must be still some kernel messages about denied actions. Your
recent debug log (thanks for that) has
[Job 93] Unable to open MFP port device file!: Input/output error
But does not say which or where. It's a bit
Feb 4 08:21:00 pau kernel: [ 679.372000] parport0: PC-style at 0x378, irq 7
[PCSPP,TRISTATE]
Feb 4 08:21:01 pau kernel: [ 679.584000] lp0: using parport0
(interrupt-driven).
Feb 4 08:21:01 pau kernel: [ 679.74] parport0: PC-style at 0x378, irq 7
[PCSPP,TRISTATE]
Feb 4 08:21:01 pau
Any news for me? :-(
If it helps, I get these messages in /var/log/cups/error_log when adding
a new printer thru the samsung driver configurator.
E [02/Feb/2008:20:48:16 +] [cups-driverd] Unable to open PPD directory
/opt/share/ppd: No such file or directory
E [02/Feb/2008:20:48:16 +]
Noticed that cups/error_log is always one hour behind...
--
After update from Feisty to Gutsy RC, print jobs fail:
/usr/lib/cups/backend/mfp failed
https://bugs.launchpad.net/bugs/152537
You received this bug notification because you are a member of Ubuntu
Bugs, which is the bug contact for
This is cups error_log:
E [29/Jan/2008:09:49:08 +] PID 5924 (/usr/lib/cups/backend/mfp)
stopped with status 2!
Syslog is exactly what I posted before, as it was already copied after
printing:
Jan 29 10:49:08 pau kernel: [ 630.856000] parport0: PC-style at 0x378, irq 7
[PCSPP,TRISTATE]
Jan
Reopening for gutsy, but no fix known yet for the subsequent problem.
** Changed in: cupsys (Ubuntu Gutsy)
Status: Fix Released = New
Target: gutsy-updates = None
--
After update from Feisty to Gutsy RC, print jobs fail:
/usr/lib/cups/backend/mfp failed
Can you please try to print something, and immediately afterwards attach
/var/log/cups/error_log and /var/log/syslog?
** Changed in: cupsys (Ubuntu)
Status: Fix Released = Incomplete
Target: ubuntu-8.04-beta = None
--
After update from Feisty to Gutsy RC, print jobs fail:
Tried removing ehci_hcd, but no differences.
--
After update from Feisty to Gutsy RC, print jobs fail:
/usr/lib/cups/backend/mfp failed
https://bugs.launchpad.net/bugs/152537
You received this bug notification because you are a member of Ubuntu
Bugs, which is the bug contact for Ubuntu.
--
MarcoPau, 7.3 does not have the fix. Can you please upgrade again
(should pull in version 7.5, unless you disabled gutsy-updates)?
--
After update from Feisty to Gutsy RC, print jobs fail:
/usr/lib/cups/backend/mfp failed
https://bugs.launchpad.net/bugs/152537
You received this bug notification
Martin, I actually had 7.5 but tried to downgrade to 7.3 as it seemed to
be the right version for the fix. In both cases, anyway, I get the error
in localhost:631. The syslog is different (reupgraded to 7.5 meanwhile):
Jan 28 16:29:27 pau rmmod: ERROR: Module ppdev does not exist in /proc/modules
Nothing changes, unfortunately...
--
After update from Feisty to Gutsy RC, print jobs fail:
/usr/lib/cups/backend/mfp failed
https://bugs.launchpad.net/bugs/152537
You received this bug notification because you are a member of Ubuntu
Bugs, which is the bug contact for Ubuntu.
--
ubuntu-bugs
Ah, if that was the complete syslog, then the patch indeed seems to
have helped a bit. Now that seems to be the fault of the actual mfp
backend you installed.
It might help to do 'sudo modprobe ppdev' perhaps, but I can only
guess.
--
After update from Feisty to Gutsy RC, print jobs fail:
Just installed version 7.3, but still getting the error message in cups. My
printer is a samsung SCX-4200.
Syslog says
Jan 25 23:42:02 pau rmmod: FATAL: can't open /proc/modules: Permission denied
Jan 25 23:42:02 pau last message repeated 3 times
Jan 25 23:42:02 pau kernel: [50150.932000]
Copied to gutsy-updates to get the fixes in for the other four bugs in
this SRU. We know that the new version is not any worse wrt. this bug,
and we strongly believe that this bug is fixed now. Please reopen if you
still have problems with the new version.
** Changed in: cupsys (Ubuntu Gutsy)
I reapplied the fixes from comment 18 to Kees' security update and
uploaded it to gutsy-proposed. Please test and give feedback here. Thank
you!
--
After update from Feisty to Gutsy RC, print jobs fail:
/usr/lib/cups/backend/mfp failed
https://bugs.launchpad.net/bugs/152537
You received this
Hilary, this sounds like a different bug. We are going to fix that, too,
but before we need to verify the fix of this bug so that the current
-proposed package can go into -updates. Do you have a printer which was
previously affected by this bug? (/usr/lib/cups/backend/mfp failed)
--
After
Martin,
Thank you for your reply.
No I do not have the error /usr/lib/cups/backend/mfp failed, Sorry
about that.
If my problem is s different one, could you point me to the relevant
bug, so that I can watch that thread? Thank you.
Hilary
--
After update from Feisty to Gutsy RC, print jobs
This has been superseded by a security update. Please remerge. Gutsy
debdiff from 1.3.2-1ubuntu7.1 attached...
** Attachment added: security update debdiff
http://launchpadlibrarian.net/11217870/cupsys_1.3.2-1ubuntu7.3.debdiff
--
After update from Feisty to Gutsy RC, print jobs fail:
Good Morning Martin,
Well, well...
I thought you should know that when I started up the office machines
this morning printing on the client machines worked a breeze. I am at a
loss to know why, since the only change I have made was to install the
updates for this bug (/usr/lib/cups/backend/mfp
Hilary, I think bug 173470 was the one you described. However, if it
works now, so much the better. That bug might just be a race condition,
though, so the next time you start the print server it might again not
work any more.
--
After update from Feisty to Gutsy RC, print jobs fail:
Hilary, BTW, the avahi side of bug 173470 is already in gutsy-proposed,
so if you installed -proposed as well and it works now, then please give
a comment there to track verification. Thank you!
--
After update from Feisty to Gutsy RC, print jobs fail:
/usr/lib/cups/backend/mfp failed
Dear Martin,
In reply to your request for feedback...
I have a local network with Gutsy installed on all machines and the
latest Avahi patches installed on all machines. I use vanilla cupsd.conf
files on all machines, on the server I have allowed sharing of published
printers and the printer is
A lot of people got this problem apparently. Can anyone please give this
some testing and give some feedback here? Without this, it cannot be
moved to -updates.
--
After update from Feisty to Gutsy RC, print jobs fail:
/usr/lib/cups/backend/mfp failed
https://bugs.launchpad.net/bugs/152537
You
Proposed debdiff for Gutsy on
https://bugs.launchpad.net/ubuntu/+source/cupsys/+bug/147800/comments/17.
--
After update from Feisty to Gutsy RC, print jobs fail:
/usr/lib/cups/backend/mfp failed
https://bugs.launchpad.net/bugs/152537
You received this bug notification because you are a member
Accepted into gutsy-proposed. Please test this version and give some
feedback here. Thank you!
cupsys (1.3.2-1ubuntu7.2) gutsy-proposed; urgency=low
.
* debian/local/apparmor-profile:
- Allow rw access to /dev/parport* and ro access to
/proc/sys/dev/parport/**, so that parallel
The 32 and 64 bit DO have different versions of HPLIP. 32 has 2.7.10,
and 64 has 2.7.7. I downloaded and installed the latest version for the
64 bit, and the problem has vanished. Blue tooth was not the problem.
--
After update from Feisty to Gutsy RC, print jobs fail:
/usr/lib/cups/backend/mfp
To get HPLIP 2.7.10 onto your 64-bit box, did you do an update of the
official Ubuntu packages (automatic update by clicking the notification
icon/using command sudo apt-get dist-upgrade or manual update of only
HPLIP with Synaptic or apt-get) or did you some kind of unofficial
update (upstream
Hi,
Till Kamppeter [2007-11-29 17:45 -]:
It would be a severe failure of the release management if the official
releases on two different platforms are of two different versions, as
our build server usually builds packages for all platforms once a new
source package is uploaded. And the
phenest, the Bluetooth issue is bug 147800.
--
After update from Feisty to Gutsy RC, print jobs fail:
/usr/lib/cups/backend/mfp failed
https://bugs.launchpad.net/bugs/152537
You received this bug notification because you are a member of Ubuntu
Bugs, which is the bug contact for Ubuntu.
--
Fixed in bzr head.
** Changed in: cupsys (Ubuntu)
Status: Incomplete = Fix Committed
Target: gutsy-updates = ubuntu-8.04-beta
** Changed in: cupsys (Ubuntu Gutsy)
Importance: Undecided = Medium
Assignee: (unassigned) = Martin Pitt (pitti)
Status: New = In Progress
cupsys (1.3.4-1ubuntu3) hardy; urgency=low
* debian/local/apparmor-profile:
- Allow rw access to /dev/parport* and ro access to
/proc/sys/dev/parport/**, so that parallel port printer detection works.
- Allow unconfined execution of the bluetooth backend. AppArmor currently
I have a Compaq TC1100 tablet running Gutsy and a Dell Precision M90
running Gutsy. My printer is a HP Deskjet 460 connected via bluetooth,
but I can only print from the tablet. The Dell will only print if I use
the 'sudo aa-complain cupsd' method. The Dell is running 64 bit whereas
the tablet is
The HPLIP is exactly the same on 32-bit and 64-bit. The problem is
perhaps a 64-bit only bug in AppArmor which prevents AppArmor from doing
its protection job on 64-bit.
--
After update from Feisty to Gutsy RC, print jobs fail:
/usr/lib/cups/backend/mfp failed
I have the AppArmor problem with my HP LJ 1012 printer. The aa-complain
cupsys freed up the printer. I had no trouble with samba visibility
during the time that the printer was shown as stopped (and shown stopped
by samba as well as the gnome printer manager. )
FWIW, upon gutsy installation, I
I confirm the problem with AppArmor. I am using a Canon Pixma MP460 with
the drivers of the MP160. It worked on Feisty but it didn't anymore on
Gutsy and I had no error message. I ran sudo aa-complain cupsd and now
it works fine, even after rebooting.
--
After update from Feisty to Gutsy RC,
More info on the problem: after a reboot of the system the problem persist.
To make it print, it is necessary to issue the aa-compain cupsys after
each restart of the PC.
Many thanks for your efforts, looking forward to test the fixed bug!
2007/10/15, Till Kamppeter [EMAIL PROTECTED]:
**
2007/10/16, Pietro Piutti [EMAIL PROTECTED]:
More info on the problem: after a reboot of the system the problem persist.
To make it print, it is necessary to issue the aa-compain cupsys after
each restart of the PC.
Many thanks for your efforts, looking forward to test the fixed bug!
Sorry
2007/10/14, Till Kamppeter [EMAIL PROTECTED]:
Looks like a problem caused by the AppArmor protection of CUPS. Can you
attach your /var/log/syslog and also the output of the dmesg command?
To deactivate the protection you can run sudo aa-complain cupsd. Are
you able to print then? To reactivate
** Changed in: cupsys (Ubuntu)
Target: None = gutsy-updates
--
After update from Feisty to Gutsy RC, print jobs fail:
/usr/lib/cups/backend/mfp failed
https://bugs.launchpad.net/bugs/152537
You received this bug notification because you are a member of Ubuntu
Bugs, which is the bug
I cannot say without getting the syslog.
** Changed in: cupsys (Ubuntu)
Target: ubuntu-7.10 = None
--
After update from Feisty to Gutsy RC, print jobs fail:
/usr/lib/cups/backend/mfp failed
https://bugs.launchpad.net/bugs/152537
You received this bug notification because you are a
I'll send it later tonight when I am back home from work.
2007/10/15, Martin Pitt [EMAIL PROTECTED]:
I cannot say without getting the syslog.
** Changed in: cupsys (Ubuntu)
Target: ubuntu-7.10 = None
--
After update from Feisty to Gutsy RC, print jobs fail:
Looks like a problem caused by the AppArmor protection of CUPS. Can you
attach your /var/log/syslog and also the output of the dmesg command?
To deactivate the protection you can run sudo aa-complain cupsd. Are
you able to print then? To reactivate the protection, run sudo aa-
enforce cupsd.
50 matches
Mail list logo
