<?xml version="1.0" encoding="ISO-8859-1"?>

<rss version="2.0" xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:content="http://purl.org/rss/1.0/modules/content/">
	<channel>
		<title>LinuxQuestions.org - Blogs - Sonneteer</title>
		<link>http://www.linuxquestions.org/questions/blog/sonneteer-268601/</link>
		<description>LinuxQuestions.org offers a free Linux forum where Linux newbies can ask questions and Linux experts can offer advice. Topics include security, installation, networking and much more.</description>
		<language>en</language>
		<lastBuildDate>Sat, 25 May 2013 00:10:20 GMT</lastBuildDate>
		<generator>vBulletin</generator>
		<ttl>60</ttl>
		<image>
			<url>https://lqo-thequestionsnetw.netdna-ssl.com/questions/images/misc/rss.jpg</url>
			<title>LinuxQuestions.org - Blogs - Sonneteer</title>
			<link>http://www.linuxquestions.org/questions/blog/sonneteer-268601/</link>
		</image>
		<item>
			<title>Ubuntu upgrade from 11.10 to 12.04</title>
			<link>http://www.linuxquestions.org/questions/blog/sonneteer-268601/ubuntu-upgrade-from-11-10-to-12-04-34710/</link>
			<pubDate>Sat, 28 Apr 2012 00:44:33 GMT</pubDate>
			<description>Since I have about a billion 3rd party applications installed, the upgrade process can be somewhat interesting at times.  This time around I...</description>
			<content:encoded><![CDATA[<div>Since I have about a billion 3rd party applications installed, the upgrade process can be somewhat interesting at times.  This time around I uninstalled acroread first, since in previous upgrades, that package has caused the upgrade process to abort.<br />
Now that my internet is on Shaw instead of Telus, the download time was pretty short.  But then the upgrade seemed to be stuck for a long time at the same point, it was not until I expanded the terminal that I found there was an ncurses dialog box waiting for my input (if I didn't see that little arrow by &quot;Terminal&quot;, we could have been waiting for each other for a long time).  <br />
So once it was finally going again, the actual upgrading was going to take awhile, but I can't just leave it with Ubuntu, because it's always asking me about whether I want to keep or replace custom config files.  There's probably a way to automatically answer those if running via the command line, but there was no option that presented itself through the GUI.  I much prefer the way it works on Slackware, where you can let it update everything by itself, and slackpkg will prompt you about each of the new config files only once that is <i>all</i> done.<br />
<br />
Once the upgrade was all said and done, of course I had to investigate the new features.<br />
The first thing, that was terribly annoying, was the way my mouse had to fight to move between my two monitors.  This was easy enough to fix through the unity plugin settings of the CompizConfig, by turning &quot;Launcher Edge Stop Overcome Pressure&quot; down to 5 and &quot;Edge Stop Velocity&quot; to 10.  (I can see how a higher pressure might be useful if I had the launcher on both screens, but rather than a second launcher, I'm running gkrellm there.)<br />
The new privacy settings were nowhere to be found--apparently I had uninstalled the &quot;ubuntu-desktop&quot; meta package at some point in the past, so installing that pulled in the new stuff I was looking for.<br />
Had to open up the Advanced Settings to reset the Window decoration theme back to the way I had it.  <br />
I liked the new icon theme in the panel, but the icons on the launcher were not so hot.  In particular, the default Gnome icon theme was missing the workspace-switcher icon, so it was just an ugly folder sitting in my launcher for the switcher.  Installation of the &quot;gnome-icon-theme-extras&quot; package fixed that though.  (If Unity needs one of those icons, shouldn't that be in the &quot;full&quot; package instead of relegated to &quot;extras&quot;?)<br />
<br />
I kept getting crash reports about virtualbox installation (even though I wasn't trying to run it) until I went back to virtualbox.org, from whence I got the previous version, and downloaded the Precise Pangolin version.<br />
<br />
Mupen64plus was updated to the newer version, which does not have a gui.  In order to reconfigure my controller I grabbed the ~/.config/mupen64plus/blight_input.conf file from my backup and used it as a reference to adjust the settings in ~/.config/mupen64plus/mupen64plus.cfg<br />
<br />
So those have been my adventures so far on this upgrade :)</div>

]]></content:encoded>
			<dc:creator>Sonneteer</dc:creator>
			<guid isPermaLink="true">http://www.linuxquestions.org/questions/blog/sonneteer-268601/ubuntu-upgrade-from-11-10-to-12-04-34710/</guid>
		</item>
		<item>
			<title>Upgrade Ubuntu from Jaunty to Karmic</title>
			<link>http://www.linuxquestions.org/questions/blog/sonneteer-268601/upgrade-ubuntu-from-jaunty-to-karmic-2358/</link>
			<pubDate>Sun, 01 Nov 2009 03:55:34 GMT</pubDate>
			<description>My first attempt to upgrade to Karmic was met with an error about ubuntu-minimal missing.  The problem being the mirror I had selected was not synced...</description>
			<content:encoded><![CDATA[<div>My first attempt to upgrade to Karmic was met with an error about ubuntu-minimal missing.  The problem being the mirror I had selected was not synced with the new distro yet.  (The &quot;Select Best Server&quot; option probably thought it was a good mirror precisely because nobody was downloading thousands of packages from it yet) So after switching to a different mirror, the upgrade went pretty smoothly.<br />
<br />
In addition to the improvements one can find on many another review, a few things I was pleased about were as follows:<br />
Updated nvidia driver.  In Jaunty, glxgears gave me an fps around 8000.  I had thought this was pretty good after coming from an old laptop that gave me 14 fps.  On Karmic glxgears now gives me 41000 fps (with my nvidia GeForce 9800 GT).<br />
digiKam had had a broken editor for me in Jaunty where the photos would not show up at all and I had to resort to gwenview for some quick editing work.  The updated version of digiKam in Karmic is working perfectly though.<br />
<br />
<br />
A couple of things that did not go as well:<br />
There were some serious issues with sound.  Songbird was giving gstreamer errors in the terminal and gave no audio output.  A number of other players, as well as games, were also not outputting sound.<br />
In search of an audio player that would work besides mpd, I installed banshee.  Apt installed the following dependencies for it: banshee libboo2.0-cil libclutter-1.0-0 libmono-zeroconf1.0-cil libnotify0.4-cil libtaglib2.0-cil podsleuth<br />
after this install both songbird and blobAndConquer were able to output audio again.<br />
<br />
gnome-power-manager kept showing up in my kde system tray as an empty space, and would respawn if I killed it.  Fixed this by logging into gnome and finding the power manger settings and told it to never show an icon.<br />
<br />
The RSS plasma widget which I have on the screensaver no longer remembers its size and always reverts back to its default setting which is too small.<br />
The Parley plasma widget still does not remember font selection between logins.</div>

]]></content:encoded>
			<dc:creator>Sonneteer</dc:creator>
			<guid isPermaLink="true">http://www.linuxquestions.org/questions/blog/sonneteer-268601/upgrade-ubuntu-from-jaunty-to-karmic-2358/</guid>
		</item>
		<item>
			<title>upgrade to Slackware 12.2</title>
			<link>http://www.linuxquestions.org/questions/blog/sonneteer-268601/upgrade-to-slackware-12-2-1412/</link>
			<pubDate>Sat, 13 Dec 2008 20:00:28 GMT</pubDate>
			<description>The upgrade from slack 12.1 to slack 12.2 went fairly well.  There were only a few issues, mostly with third party packages. 
 
On the first boot,...</description>
			<content:encoded><![CDATA[<div>The upgrade from slack 12.1 to slack 12.2 went fairly well.  There were only a few issues, mostly with third party packages.<br />
<br />
On the first boot, rc.serial made a lot of output complaining of nonexistant devices.  But this was only a one time occurrence.<br />
<br />
fbpager no longer works with the new fluxbox, but there has been some recent development with fbpager so there may be a new release at some point that will solve this.  Tried fluxter with no success.  For now I have switched to ipager.  My issue with ipager is that I can't see anything in the config that could make it arranged in two rows instead of one (horizontally), so I need to make it rather small if I want to keep it in the vertical slit with gkrellm.  (The pager plugin for gkrellm is too plain looking to me (text with LEDs) compared to the typical graphical pager that shows where the windows are.)<br />
<br />
Slackware's Firefox had issues (symbol lookup error: /usr/lib/libgnome-2.so.0: undefined symbol: g_dgettext) with the libgnome package from dropline 2.24.1 beta, and it wouldn't start until I uninstalled the libgnome package.<br />
<br />
I also no longer seem able to access the third level shift keys from within firefox.  This was annoying as I have some passwords (especially the master) that used symbols from the third level.<br />
<br />
While I was in XFCE, the gam_server process suddenly started taking the CPU up to 100% and it refused to be killed. After a hard reboot I removed the gamin package, but konqueror seems to depend on it so I reinstalled it.  But it hasn't acted up again since.</div>

]]></content:encoded>
			<dc:creator>Sonneteer</dc:creator>
			<guid isPermaLink="true">http://www.linuxquestions.org/questions/blog/sonneteer-268601/upgrade-to-slackware-12-2-1412/</guid>
		</item>
		<item>
			<title>Back to mrxvt</title>
			<link>http://www.linuxquestions.org/questions/blog/sonneteer-268601/back-to-mrxvt-776/</link>
			<pubDate>Fri, 26 Oct 2007 04:20:28 GMT</pubDate>
			<description>So after I upgraded to Slackware 12 from 11, this strange problem arose with Eterm.  I could use vim a couple of times, then thereafter it would not...</description>
			<content:encoded><![CDATA[<div>So after I upgraded to Slackware 12 from 11, this strange problem arose with Eterm.  I could use vim a couple of times, then thereafter it would not work.  I'd type in the command, and the cursor would go to the next line and just sit there.  I couldn't type in anything, couldn't even Ctrl-C out of it and would have to close the window.  It would continue to behave this way until I rebooted.  Other things such as the links browser would also not work, but text editing with elvis still functioned fine.<br />
Having no idea how to track down the cause of this, I gave up and went back to using mrxvt, which has tabs anyway.  (I had stopped using mrxvt when I had gone back to using KDE because I'd use its native konsole, but had since moved to fluxbox, installing Eterm for the suggested Esetroot program).<br />
I quickly discovered that mrxvt has a configuration file (~/.mrxvtrc) where options can be kept instead of using a long command line.  So here's what I have in my .mrxvtrc at the moment:<div style="margin:20px; margin-top:5px">
	<div class="smallfont" style="margin-bottom:2px">Code:</div>
	<pre class="bbcodeblock" dir="ltr" style="
		margin: 0px;
		margin-right: -99999px;
		padding: 3px;
		border: 1px inset;
		width: 98%;
		height: 338px;
		text-align: left;
		overflow: auto">Mrxvt.geometry: 134x31+0+122
Mrxvt.foreground: grey
Mrxvt.textShadow: black
Mrxvt.transparent: True
Mrxvt.shading: 75
Mrxvt.showMenu: False
Mrxvt.transparentMenubar: True
Mrxvt.bottomTabbar: True
Mrxvt.transparentTabbar: True
Mrxvt.tabBackground: black
Mrxvt.tabForeground: white
Mrxvt.itabBackground: #000000
Mrxvt.itabForeground: #808080
Mrxvt.transparentScrollbar: True
Mrxvt.scrollbarStyle: plain
Mrxvt.scrollbarThickness: 10
Mrxvt.scrollbarFloating: True
Mrxvt.troughColor: #000000
Mrxvt.saveLines: 500
Mrxvt.appIcon: /usr/share/pixmaps/mrxvt.xpm</pre>
</div>The colouring of the scrollbar (troughColor) only seems to work when the scrollbarStyle is set to plain, which was a bit annoying, but otherwise this gives me a terminal the way I like it to look when under X.</div>

]]></content:encoded>
			<dc:creator>Sonneteer</dc:creator>
			<guid isPermaLink="true">http://www.linuxquestions.org/questions/blog/sonneteer-268601/back-to-mrxvt-776/</guid>
		</item>
		<item>
			<title>kernel patching</title>
			<link>http://www.linuxquestions.org/questions/blog/sonneteer-268601/kernel-patching-760/</link>
			<pubDate>Sat, 13 Oct 2007 20:03:52 GMT</pubDate>
			<description><![CDATA[So the concept of patching the kernel to update to the next release is something I haven't delved into too much before.  I've had previous...]]></description>
			<content:encoded><![CDATA[<div>So the concept of patching the kernel to update to the next release is something I haven't delved into too much before.  I've had previous experiences of trying to use the patch command that didn't go over too well.  The syntax of the patch command is something that is simple when understood.  Yet being slightly different from other commands, it can look a bit scary to a newbie.  For instance, what number am I supposed to put with the p?  But when I actually sat down to try it, it was actually quite easy to figure out.  So here's the new section that I have now added to my kernel script:<br />
<div style="margin:20px; margin-top:5px">
	<div class="smallfont" style="margin-bottom:2px">Code:</div>
	<pre class="bbcodeblock" dir="ltr" style="
		margin: 0px;
		margin-right: -99999px;
		padding: 3px;
		border: 1px inset;
		width: 98%;
		height: 306px;
		text-align: left;
		overflow: auto">patch)
if [ ! -e patch-$NEWVERSION ]; then
wget http://www.rafal.lkams.kernel.org/pub/linux/kernel/v2.6/patch-$NEWVERSION.gz
        gunzip patch-$NEWVERSION.gz
cd linux-$VERSION
        patch -p1 &lt;../patch-$NEWVERSION
                make silentoldconfig
cd $ROOTSRC
        mv linux-$VERSION linux-$NEWVERSION
        sed -i -e s/^VERSION\=.*/VERSION=$NEWVERSION/ josh.kernel
fi

if [ ! -d $DAZUKODIR ]; then
        cd $ROOTSRC
                wget http://www.dazuko.de/files/dazuko-$DAZUKO.tar.gz
                        tar -zxpf dazuko-$DAZUKO.tar.gz &amp;&amp; rm dazuko-$DAZUKO.tar.gz
fi
;;</pre>
</div>So for the p, I guess just stick with 1, unless you know what you're doing otherwise?<br />
the patch command uses a &quot;&lt;&quot; where other commands would use something such as &quot;-i&quot;</div>

]]></content:encoded>
			<dc:creator>Sonneteer</dc:creator>
			<guid isPermaLink="true">http://www.linuxquestions.org/questions/blog/sonneteer-268601/kernel-patching-760/</guid>
		</item>
	</channel>
</rss>
