After updating my Ubuntu desktop to a more recent release (12.04 / Precise Pangolin), my rarely used Canon Pixma MP190 stopped working. Not completely, but in a rather annoying way: Printing a single page works fine, but printing multiple pages / copies causes the printer to hang. Hard. As in, you have to pull the power plug to reset it, as no button will do anything anymore.
Apparently there was a bug introduced with CUPS a while ago, or rather a change in behavior of CUPS which triggers a bug in the printer Firmware. Took me a couple hours to find and had me on the brink of throwing out the whole printer.
And it looks like it affects quite a few other USB printers as well: Epson NX130, Canon i550, i560, ip4200, ip4300, ip5200, MP180, MP160, MP210, MP450, MP500, MP520, …
To save you from reading through all the comments: Till Kamppeter came up with a workaround that worked perfectly for me and others.
In a terminal window, run the command
lpadmin -p -o usb-unidir-default=true
with being the name of your printer as displayed
by the "lpstat -p" command.
Now turn off and turn on your printer, then try to print several jobs.
After that I was able to print a couple hundred envelopes without a hitch.
If you can’t wait to play the newest iteration of Fallout, yet don’t want to boot Windows to do it – with a little effort you can get it running under Wine as well.
It doesn’t seem to work out of the box, even with a very recent release (Failed to initialize renderer. Unknown error creating the GamebryoRenderer.)
But if you don’t mind adding a little patch and compiling Wine yourself, you should be able to get Fallout New Vegas up and running in no time.
WineHQ Bug 24831 describes the problem and someone else came up with a fix just a few hours later. But if you’re running Ubuntu 10.10, sadly the patch doesn’t apply right away. To manually fix it, just get the Wine source package and edit the file ‘dlls/d3d9/directx.c’, go to line 477, remove or comment out this part
*device = NULL;
and substitute it with this:
return IDirect3D9Ex_CreateDevice(iface, adapter, device_type, focus_window, flags, parameters, (void *)device);
Save the file and run ‘dpkg-buildpackage’ and when finished, install the resulting .deb.
(Or just download my modified directx,c and save it to wine1.2-1.2.1/dlls/d3d9/directx.c before compiling)
That’s it. Enjoy your stay in New Vegas. :)
If you recently upgraded to WordPress 3 and you’re using their new default Theme together with the famous All in One SEO Pack Plugin, you probably already noticed an annoying little bug: Your blog title is now appearing twice. Kinda defeats the whole SEO thing…
While the bug itself hasn’t been fixed yet, there’s a simple workaround.
Open up functions.php of your TwentyTen theme and go to line 262.
You’ll see a line that looks like
add_filter( 'wp_title', 'twentyten_filter_wp_title', 10, 2 );
Just add two forward slashes in front of it so that it looks like
//add_filter( 'wp_title', 'twentyten_filter_wp_title', 10, 2 );
Everything looks like it’s supposed to and AIOSEOP is back to doing its magic.
After upgrading Firefox on my main workstation to a more up-to-date release (3.6), it turns out I can’t access the Webinterface of any of my VMware Servers. While some kind of glitch every now and then is to be expected from this “somewhat” buggy piece of sh… uhm, code – this time, logging with Firefox actually manages to crash the management application on the server itself. Yeah, that’s right – at that point you can’t even access it with another browser or the VIC until you kill the hostd and do a /etc/init.d/vmware-mgmt restart. It isn’t even some kind of ancient beta release, but 2.0.2 – the most recent release as of now. WTF?
According to the logs there appears to be some kind of SSL issue:
SSL Handshake on client connection failed.
Turns out Web Access can’t handle SSL3 and Firefox 3.6 has SSL2 disabled per default. Why this manages to crash an application on the server boggles my mind, but at least there’s an easy workaround until VMware manages to fix this:
Go to your about:config page and set security.enable.ssl2 from false to true.
That’s it, done. At least it worked for me – no more issues whatsoever.