The "internal server error" has nothing to do with the Brother driver and everything to do with the CUPS setup in Quirky. Are you doing this from a clean install? Have you added any other packages like web browsers? Are you using a 32bit Quirky?

You should post your problem in the Quirky thread.

Attempt to add printer was done on a fresh install of Quirky Tahr 6.0.5, which is a 32-bit version of Quirky.

The only package added was debbi-1.2.pet. Specifically no browsers were added.

@rcrsn51, I have made an interesting observation on the problem that I described in my post of 26 July above regarding installation of an MFC-L2700DW Brother printer on Quirky Tahr (which is 32-bit).

I made another fresh install of quirky Tahr. To it I copied debbi-1.2.pet; then I updated the oackage manager and installed HPLIP from the Ubuntu repositories. I also downloaded mfcl2700dwlpr-3.2.0-1.i386.deb and mfcl2700dwcupswrapper-3.2.0-1.i386.deb from the Brother site.

Opening CUPS, I installed an HP 6500 E710n-z using HPLIP's driver for the printer. Test print was fine. I printed out test files from Abiword and Geany, which were fine. So the CUPS setup in Quirky, at least in regards to HPLIP, seems to be functional at this point.

Then I used debbi with Brother's lpr and cupswrapper files, trying to create the MFC-L2700DW Brother driver, and the errors reported were the same as described above, including the "Internal Server Error"!

And as one might expect, I could no longer print to the HP machine from Abiword or Geany.

Might Brother's mfcl2700dwlpr-3.2.0-1.i386.deb and mfcl2700dwcupswrapper-3.2.0-1.i386.deb somehow be interacting with CUPS to disable it?

Might Brother's mfcl2700dwlpr-3.2.0-1.i386.deb and mfcl2700dwcupswrapper-3.2.0-1.i386.deb somehow be interacting with CUPS to disable it?

That's a reasonable conclusion, but I have no idea why and I don't have a Quirky setup to investigate.

But here is a potential fix. In regular Tahrpup (where it works) use debbi-pet-maker to convert the Debian packages into a PET. Then install the PET in Quirky. You will need a temporary clean install of Tahrpup for debbi-pet-maker to work properly. Otherwise, it will get confused by an existing install of the driver.

[Edit] I tested this method on an ISObooter flash drive install of 32bit Quirky April and it didn't break CUPS.

@rcrsn51, so far this technique on Quirky does not seem to be working for me. This terminal will not let me scroll back and copy the error messages. I am on my 3rd practice install of Tahrpup...I'll go more slowly and write down the errors as they occur.

OK, after wandering in computer wilderness for a couple of days, mostly due to self-inflicted injuries, I am finally ready to report on my attempt at using debbi-pet-maker in Tahrpup 6.0.3 (also 32-bit) to create a MFC-L2700DW.pet to (hopefully) install the driver in Quirky Tahr.

Both debbi-1.1 and debbi-1.2 can create functioning MFC-L2700DW drivers for the Tahrpup in conjunction with “printernamelpr.deb” and “printernamecupswrapper.deb” downloadable from the brother web site. On cd-ing to the directory with the two .deb files and using debbi, here is the terminal output:

The errror “chown: unknown user lp” doesn’t seem to be fatal, and PPD files are created in /etc/cups/ppd/, /opt/brother/Printers/ and /usr/share/ppd/brother; the printer is installed in cups (at least for a USB connection), and the driver seems to be fully functional.

The file “debbi-1.2.pet” when installed, contains an additional program “debbi-pet-maker”, electively run from the terminal. First cd to the directory containing the brother lpr- and cuppswrapper-driver-creating programs, type "debbi-pet-maker" and this program creates ppd driver files for the parent distro but also creates a .pet file that can run the printer driver installation in a different 32-bit puppy copy.

I made a fresh copy of Tahrpup (a “practice copy” which I could later sacrifice), installed debbi-1.2.pet, made a MFC-L2700DW-1.0.0 directory in my Downloads directory, in which I placed mfcl2700dwlpr-3.2.0-1.i386.deb and mfcl2700dwcuppswrapper-3.2.0-1.i386.deb. I opened a terminal, cd to MFC-L2700DW-1.0.0 and ran debbi-pet-maker.

The program is interactive and requires some easy user-input; the “chown: unknown user lp” error was there as before.

The .pet is made, and PPD files are installed in the “practice” copy of Tahrpup. My printer was installed in CUPS with a USB connection; I deleted this connection and installed it to a (known working) network connection. Test print did not work.

I made a fresh copy of Quirky Tahr, booted it and copied to it the MFC-L2700DW-1.0.0.pet and the Brother lpr/cuppswrapper driver creator files (not sure if they were needed). When clicked on, the .pet reported successful installation.

I opened CUPS, and the printer had not been installed. PPD files were present in /opt/Brother/printers and /usr/share/model but not /etc/cups/ppd. I installed the printer using a PPD file and a (known working) network connection. Test print did not work, but CUPS reported “Job Completed”.

No. Since the PET didn't work in Tahrpup, it certainly wasn't going to work in Quirky.

However, you have already reported that installing the printer in Tahrpup with debbi works. Debbi-pet-maker runs debbi on the two DEBs and collects all the installed files into a PET. So I don't know why the resulting install would now fail.

Now for my current everyday system....
Fatdog 621 (64bit) Network install ethernet
Although this system is already superseeded it works better for me on a lot of programs and devices so I just had to make it work here.

1. Mount 32 bit libs using an sfs file (see fatdog repos i tend to use the 32bit slacko sfs

5. in that folder where I put them all did in a terminal in that folder

Code:

debbi ####.deb

for each of the deb files starting with the ##lpr## file
and ran the cupswrapper script as done in step 2 for the lucid version above

6. I unpacked and compiled the source file to at least get another 64bit binary--- copied it to the same location as the 32bit components from the deb
(may not be necessary as you are going to be using 32bit stuff anyway (no choice))

7. Thanks to a post elsewhere:
in etc/init.d/71cups-32
change line 168 to be

Code:

start32 /usr/sbin/cupsd

8. THIS STEP WAS THE BIG KEY!
In Fatdog control panel/System /Manage Servers and Services
Turn off cups (normal 64bit) also for startup
Start cups32 and if you need it all the time also check it on for startup

9. For a network install ..
add in etc/hosts a line

Code:

192.168.2.52 BRN30055C174C16

(Where the above ip address is the one your printer is on and the BRN number matches the one you see in cups (see 10))

To use it you may need to run the cupswrapper script again (Step 2 )
You may need to change the line in etc/hosts to reflect your ip address and the correct BRN number (you should see it in cups)
And Step 8 to turn on cups32.
and you need to click on find printer in cups admin
and for the scanner do step 1 reflecting your IP and the name you want to use.

Hope it helps someone else to get their similar device up and running.
Thanks to rcrsn51 for your hard work here.

I write now out the original Lubuntu Trusty Tahr 64, the puppy like form of original Ubuntu.

Why?

Only

because it was not possible for me to start my brother HL-2035 with some original Puppy... I did test more than 15..20 different 32 and 64 Puppy's and spend days for that search and I am not a new comer! But I print really rarely, and did use about all the "Puppy time" a Canon ink printer making never problem excepted at the time of the 4.nn Puppy's: so, I have no experience in matter of printer in Linux as I use today about 10 years principally Puppy... My "new" (it is now very old) canon scanner works immediately in xsane in each Puppy, excepted that it is not always possible to find some adequate ocr for Puppy for all frequent languages. My old scanner from HP did not work at all in Linux; really unfortunate as it was one of those special letter format scanner being able to scann page after page some really bigger documents as advertising posters and to rebuild them after that using sofware...

my post in this thread today is to incite you to think about the declaration of the guy's from woof-CE:

Great things are happening in the "testing" branch of woof-CE:
- Support for building tahrpup64
- Support for packages of more distros and more distro versions
- Speed improvements, new looks and new features in PPM
- Support for new kernels
- UI improvements
- Bug fixes
- New translations
- ... and more

Many Puppy developers produce their puplets by remastering an existing Puppy built using woof-CE, so they don't receive all those new features. For example, if someone builds a puplet from tahrpup 6.0.2, it won't benefit from the features added to woof-CE after tahrpup 6.0.2 was released. Also, this means the additions to woof-CE are less battle-tested.

It's sad that puplets remain oudated, while all these features are already available and waiting for someone to take advantage of them. And they don't cost money, so why not?

I want YOU to use woof-CE. It's always good to have more working hands and thinking minds in a community project like this.

Therefore, I encourage you:
- If your puplet includes non-trivial changes (i.e it's more than just a different wallpaper), build it using woof-CE and not by remastering. This way, you gain new features and have much more control: you can change everything in your puplet. To use woof-CE:

See? It's simple. If you're new to woof-CE, try to build tahrpup (x86, x86, ubuntu, trusty) first. Then, edit files under woof-distro/x86/ubuntu/trusty until you get the knack of it.
- Contribute all bug fixes in your puplets back to woof-CE, so other puplet developers don't have to fix them again
- To contribute all changes you do to woof-CE, using a git pull request (see GitHub's documentation). This way, the entire Puppy ecosystem benefits from them.
- Maintain your puplet's configuration files under woof-distro directly in woof-CE. This way, you have all the features of modern version control (full history, the ability to track changes, branches, the ability to revert changes and see when they happened ...) while making it easier for others to join the development.
- If you're serious about Puppy development, join the woof-CE organization in GitHub.

etc.......

Cheers,
Dima

already forgotten?

it is nonsens to continue a thread over 200 answers along to solve a problem for only one brand of hardware making

absolutely no problem in the original ubuntu

(I did re install Ubuntu trusty twice time last friday: one time with Unity, that I don't like at all, and after that, one time with Lubuntu trusty, trusty because Lubuntu is not available for all processors in all versions...) my printer makes no problem! Immediately recognized, you can pass the different pages from cups, and only change in the last one the printing size "letter" in "A4" for European people: it is all...

The software from Puppy is wrong! Puppy did destroy the good settings from Ubuntu using old Puppy cram being not really operable. In WoofCE or manually is egal - it is irresponsible in my eyes!

200 answers and nobody wakes up ...

Is that the work of a community?

Note: The job of Julien Lavergne, the actual French developer of Lubuntu, is about exactly the same as the job of main developers of Puppy new versions like TahrPup or TahrPup64: Reduce Ubuntu and it's installation in such kind don't to introduce lose of really existent abilities... It is different from the comparable operation through own binaries produced from scratch out sources from authors of the software and app's!

You cannot post new topics in this forumYou cannot reply to topics in this forumYou cannot edit your posts in this forumYou cannot delete your posts in this forumYou cannot vote in polls in this forumYou cannot attach files in this forumYou can download files in this forum