<?xml version="1.0" encoding="utf-8" ?><rss version="2.0" xmlns:admin="http://webns.net/mvcb/" xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:creativeCommons="http://backend.userland.com/creativeCommonsRssModule" xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:html="http://www.w3.org/1999/html" xmlns:rdf="http://www.w3.org/1999/02/22-rdf-syntax-ns#" xmlns:slash="http://purl.org/rss/1.0/modules/slash/"><channel><title>Random notes from mg</title><link>http://mg.pov.lt/blog</link><description>a blog by Marius Gedminas</description><language>en</language><ttl>60</ttl><dc:creator>Marius Gedminas</dc:creator><admin:generatorAgent rdf:resource="http://pyblosxom.sourceforge.net/"/><admin:errorReportsTo rdf:resource="mailto:marius@gedmin.as"/><item><title>Fixing the netspeed applet</title><guid isPermaLink="false">netspeed-applet</guid><link>http://mg.pov.lt/blog/netspeed-applet</link><description>Netspeed is a GNOME panel applet that shows your current upload/download speed in bytes (or bits) per second. I love ...</description><content:encoded><![CDATA[
<p><a href="http://www.gnome.org/projects/netspeed/">Netspeed</a> is a GNOME
panel applet that shows your current upload/download speed in bytes (or bits)
per second.  I love it.  Except... you have to manually say which network
device to monitor.  If you're switching between wireless and wired, this gets
old really quickly.  There's an option, <em>Always monitor a connected
device</em>, but it is <a
href="http://bugzilla.gnome.org/show_bug.cgi?id=503518">buggy</a> and usually
gets stuck monitoring some stupid network interface like wmaster0 or
vmnet8.</p>

<p>Today I spent a couple of hours fiddling with netspeed's source code and
<a href="http://bugzilla.gnome.org/show_bug.cgi?id=503518#c17">fixed</a> <a
href="http://bugzilla.gnome.org/show_bug.cgi?id=503518#c18">the bug</a>!
Patches attached to the bug report and tested with netspeed-0.14 on Ubuntu
Hardy.</p>

<p>While doing this I created a local Bazaar branch for playing with the source
code.  Sadly, Bazaar decided to hurt me again: bzr viz, instead of letting me
look at my commits in a nice GUI window, barfs <em>AttributeError:
'KnitPackRepository' object has no attribute 'get_revision_graph'</em> and
stops.  Apparently the latest version of bzr-gtk (trunk from launchpad) is not
compatible with the latest version of bzr (1.6rc2 from the Hardy PPA).</p>

<p>It's becoming a pattern: every couple of months I give Bazaar a try, and I
hit a new bug that prevents me from doing whatever I wanted to do.  Why do I
even keep trying?</p>
]]></content:encoded><category domain="http://mg.pov.lt">/home/mg/blog/data</category><dc:date>2008-08-24T00:53:58Z</dc:date></item><item><title>PowerTop as GNOME applet?</title><guid isPermaLink="false">powertop-as-gnome-applet</guid><link>http://mg.pov.lt/blog/powertop-as-gnome-applet</link><description>Dear lazyweb, Where's the GNOME applet that can show me my laptop's power usage in Watt? I cannot believe that ...</description><content:encoded><![CDATA[
<p>Dear lazyweb,</p>

<p>Where's the GNOME applet that can show me my laptop's power usage in
Watt?  I cannot believe that nobody has written one yet.</p>
]]></content:encoded><category domain="http://mg.pov.lt">/home/mg/blog/data</category><dc:date>2008-06-05T21:21:25Z</dc:date></item><item><title>GNOME startup time</title><guid isPermaLink="false">gnome-startup</guid><link>http://mg.pov.lt/blog/gnome-startup</link><description>On my laptop (Pentium M, 1.6 GHz, 1 GB RAM) it takes exactly 68 seconds from the time I press ...</description><content:encoded><![CDATA[
<p>On my laptop (Pentium M, 1.6 GHz, 1 GB RAM) it takes exactly 68 seconds
from the time I press Enter in the GDM login screen, until the GNOME desktop
is completely loaded (the last applets appear and the disk activity stops).
This is GNOME 2.16.1 from Ubuntu Edgy.</p>

<p>This is after a fresh reboot (so, nothing in disk cache, except for
what Ubuntu's readahead loads).  The startup process is not interfering (I
waited until the disk activity stopped before I logged in).</p>

<p>What does GNOME load?  A large wallpaper (2304x1280 -- I use dual-head),
xcompmgr, Tomboy, Network Manager applet, a bunch of GNOME applets on three
panels (netspeed, gweather, battery, sound volume, two clocks, window
switcher, workspace switcher, two window lists, two system managers, CPU
frequency, trashcan, 7 launchers).  And the usual GNOME processes (nautilus,
gnome-settings-daemon, etc.).</p>

<p>Still, 68 seconds is too much.  I ought to figure out how to hook bootchart
to this thing and start filing bugs.</p>
]]></content:encoded><category domain="http://mg.pov.lt">/home/mg/blog/data</category><dc:date>2006-12-27T13:23:49Z</dc:date></item><item><title>GNOME Terminal text shadow</title><guid isPermaLink="false">gnome-terminal-text-effects</guid><link>http://mg.pov.lt/blog/gnome-terminal-text-effects</link><description>Before: After: Patch: libvte4-drop-shadows.patch . Inspiration: Eterm , Keith Packard's xterm hack .</description><content:encoded><![CDATA[
<p>Before:</p>

<p><img alt="GNOME Terminal screenshot with no text shadows"
        src="http://mg.pov.lt/gnome-term-no-drop-shadow.png"
        width="685" height="432" /></p>

<p>After:</p>

<p><img alt="GNOME Terminal screenshot with text shadows"
        src="http://mg.pov.lt/gnome-term-drop-shadow.png"
        width="685" height="432" /></p>

<p>Patch: <a
href="http://mg.pov.lt/libvte4-drop-shadows.patch">libvte4-drop-shadows.patch</a>.</p>

<p>Inspiration: <a href="http://www.eterm.org/">Eterm</a>, <a
href="http://freedesktop.org/~keithp/screenshots/translucentapps.png">Keith
Packard's xterm hack</a>.</p>
]]></content:encoded><category domain="http://mg.pov.lt">/home/mg/blog/data</category><dc:date>2005-09-11T16:34:57Z</dc:date></item></channel></rss>
