Recently had trouble printing a large document – received error message “Unable to write print data: Broken pipe”.
Quick fix: printing the document in sections worked.
For other options: this ubuntu forum post has various links/discussion.
I was recently trying to sort out OpenID delegation for a blog. I wanted to leave comments on someone else’s Live Journal blog using an OpenID that pointed to my blog’s URL.
Sam Ruby’s article, OpenID for non-SuperUsers has everything one needs to know about OpenID.
For my purposes, all I needed to do was get an OpenID (which can be obtained here) and add the following to the header.php file for the WordPress blog that I wanted to use as my OpenID URL:
<link rel=”openid.server” href=”http://www.myopenid.com/server” />
<link rel=”openid.delegate” href=”http://my-openid-account-name.myopenid.com/” />
(The my-openid-account-name string needs to be replaced with an actual OpenID account name.)
After the most recent Jaunty update, I received this “Couldn’t open audio” error message when I next tried to play audiobooks on xmms:
Please check that:
Your soundcard is configued properly
You have the correct output plugin selected
No other program is blocking the soundcard
This thread had lots of info on diagnosing the problem.
(All I had to do was go to Options -> Preferences -> Audio I/O Plugins and choose “ALSA 1.2.11 output plugin [libALSA.so]” from the “” menu. It had been set to “OSS Driver 1.2.11 [libOSS.so]” before.)
I’m an xmms girl. I’ve never needed the extra features in xmms2, so I was distraught when xmms was no longer available from my friendly neighbourhood Synaptic Package Manager once I moved to Hardy.
Thank the stars, this wonderful person provided all the information I needed to rectify the situation.
This also worked for me in Jaunty (Netbook Remix).
Long live xmms!
The fade-in effect on the Google search engine home page causes me disproportionate rage. I have given it a go for over a month now, but I still cringe every time I load the page, and I’ve decided I just don’t need this kind of aggravation on a daily basis.
I tried out a few other search engines but nothing appealed, so now I’m back to Google. However, the daily bad feeling generated by the fade-in is too much for me. Life is short, so I’ll live it fade-in free.
Here are several of the things I’ve tried, all of which work in one way or another in Firefox….
1. I had Google as my ‘home’ page in Firefox. Changing the link from www.google.com or www.google.co.uk to this:
http://www.google.co.uk/firefox?client=firefox-a&rls=org.mozilla:en-US:official
leaves me with all links but none of the fade-in. My only hesitation in making this change is that I enjoy the occasional changes to the Google logo.
2. I then tried adding the Noscript plug-in and disabling scripts from running on Google, available here:
https://addons.mozilla.org/en-US/firefox/addon/722
This worked, but every time I opened a search page, a little Noscript message would pop up, informing me that scripts were disabled. This was better than the fade, but not quite as good as things were before all this fade-in business began.
3. Finally, I tried the Stylish plug-in available here:
https://addons.mozilla.org/en-US/firefox/addon/2108
Once it was installed, I pointed my browser at Google, clicked the Stylish icon and chose ‘Write new style’ from the menu. I then entered:
@namespace url(http://www.w3.org/1999/xhtml);
@-moz-document domain(“www.google.co.uk”) {
#ghead
{
opacity:1!important;
}
.fade
{
opacity:1!important;
}
.gbh
{
opacity:1!important;
}
#fctr
{
opacity:1!important;
}
#sbl
{
opacity:1!important;
}}
in the text box and saved. (Many thanks to BdgR47!) Everything works beautifully now – there is no fade, no extra plug-in messages messing up the page and I’ll not miss any festive logos. The world is, indeed, a better place in which to live.
Make a 135×135 pixel .png image.
Copy it to:
/var/lib/mediawiki/skins/common/images/wiki.png
and refresh the browser.
