- SRWare Iron was doing a peculiar thing: When I used it to view my junkbox.com main page, the title image was broken. This was not the case using IE, FF, or Opera. Nor was it true of the several other images on that same page, but only that big main one. An intuition led me to look up the name of the image file: junkboxmainbanner.png. I renamed the file “junkboxmain.png” (that is, removing the substring “banner” from the filename) and the image began rendering normally. I guess there’s a downside to adblockers as twitchy as this one.
- From Bruce Baker comes a nice chronological screenshot survey of computer GUIs since the primordial Xerox Alto in 1973, up through Windows Vista and KDE 4. No judgements are passed on the products, and not much history is offered, but it’s unusual to see them all lined up in one place, and one definitely gets a sense for the way it all evolved, and especially for the immeasurable debt that Apple owes Xerox.
- On a tip from Pete Albrecht, I’ve learned that the Progressive Insurance girl Flo and one of the Geico cavemen shared a scene in the short-lived 2007 TV sitcom Cavemen . Here’s a YouTube clip of the scene. This was sheer coincidence; the Progressive ad campaign did not happen for at least a year after that and Stephanie Courtney just happened to get the part. I tried to like the series and failed, but I’ll admit that it had some surreal moments, a few of which we evidently didn’t appreciate at the time. Now, cavemen ate geckos. (Cavemen ate anything they could catch.) Dare we hope…
- Here’s an old article from Popular Mechanics on building your own Geiger counter. Michael Covington reminds me that there was a circuit in Alfred Morgan’s book The Boys’ Second Book of Radio and Electronics, though it had a peculiar power supply and didn’t work when I tried to build it in 1966. (I may still have the G-M tube somewhere, but I can’t find it and in truth haven’t seen it in decades.)
- Yet another one, this time from Popular Science, March 1950.
- Todd Johnson suggests using scrounged or surplus fluorescent lamp supplies from computer scanners for homebrew Geiger counters. I’ve got two defunct scanners on the woodpile downstairs, but if you don’t, Todd also sent along a pointer to a surplus source, for only $5.
- Today is Ubuntu 9.04 day. It’s like the Day after Thanksgiving at Marshall Fields up there, so don’t expect much in the line of download performance. I’m going to wait for the dust to settle a little (and maybe for my assembly book to be done) but it will happen here sooner or later. If you want it, look for torrents. And come with a backpack of patience.
- Do you have Linux running on an Intel DQ35 motherboard. If so, be careful.
- Finally, this clever food hack reminds me vaguely of something. I don’t know what. That’s probably just as well.
software
Odd Lots
Iron Filings
I’m a little disappointed in the new Chromium-based browser SRWare Iron (see my entry for April 18, 2009) or perhaps I should say a little disappointed in SRWare itself. The browser has worked extremely well the last couple of days here on my quad-core XP machine. After only a little sleuthing I made the ad blocker work: All you have to do is download a text list of ad sites into the Iron directory, and the browser runs with it. (The browser is shipped with an empty adblock.ini file.) However, Pete Albrecht alerted me to the fact that Iron won’t run at all on his Windows 2000 machine–even though SRWare hints that it might.
Google is quite firm about it: Chrome won’t even install under Win2K. XP and Vista are all you get. However, down in the German-language portion of the SRWare Web site, Pete (who is fluent in German and in fact translates engineering texts for a living) found this:
There is something new for users of Windows 2000 as well; for cost reasons, there are still many users of this system, for example, in business. While Chrome can’t even be installed on Windows 2000 systems, Iron has also removed the warning message that appears whenever it is started on a Windows 2000 system. However, installations under Windows 2000 remain unsupported, as there may be isolated problems.
(Pete’s translation; the item is not present in English.) Well, if the problems are isolated, they’re isolated in a peculiarly concentrated fashion. I loaded Iron Portable on a Cruzer Mini and woke up every operational Win2K machine I still have in the house. (This took some waking; my poor 2001 ThinkPad doesn’t work very well anymore.) Iron failed on all four machines, with variations on the following error message:
The procedure entry point <whatever> could not be located in the dynamic link library KERNEL32.DLL.
KERNEL32.DLL is one of several places where the fundamental Windows API lives. The API call that failed was not always the same, but in every single case, Iron failed to start.
0 for 5 on Win2K, sigh. Iron won’t run on Linux or Mac either. (Nor will Chrome.) What bothers Pete and me is that SRWare suggests that the software should run under Win2K, with only “isolated problems.” Why not just be honest? If people get their hopes up that your software will run on their systems and then find out the hard way that it won’t, it only makes your software (and you) look bad. This is not the way to make a very promising software product catch on.
The Iron Sandbox
I’ve been pretty focused the last three or four months, so I mostly missed the whole discussion about Google Chrome and its pros and cons. Parts of Chrome are very impressive, particularly the “sandbox” security model–and parts are about what you’d expect from a monster company that makes its money on Web ads. I caught snatches of the debate here and there, but it wasn’t until I found myself at 3 PM today with 5,100 words’ worth of progress made since 7:30 AM that I decided, enough of this. (I’m now 133,000 words in and pretty much on schedule again, having lost some ground in March.) So I kicked back and started reading up on Chrome. In doing so, I found something I hadn’t expected, or heard about at all: SRWare Iron.
What Iron looks like to me is Chrome with Google’s business model stripped out. Chrome itself was based on a number of different technologies, most of them open-source, including Google Code’s Chromium browser framework and the WebKit rendering engine. Google built a number of tracking mechanisms into Chrome, including a unique user ID and a few other mechanisms for sending search statistics back to Google. These seemed relatively benign to me (perhaps I’ve seen too much of the really bad stuff, heh) but a lot of people got very upset over the Chrome privacy model.
Enter SRWare, a German software security firm. They took the open-source codebase for Chrome and stripped out whatever they considered dicey from a privacy standpoint. They updated the WebKit rendering engine, did a few other miscellaneous security tweaks, and re-released the product as Iron. This sounds presumptuous to some people, but that’s how open source works. (There’s nothing preventing Google from re-absorbing SRWare’s changes, but as the changes are mostly features removed, that wouldn’t be especially useful.) Basically, we have a Chrome variant that doesn’t track your searches and phone home.
That’s good, and as browsers both Chrome and Iron have reviewed well. Chrome (and therefore Iron) do well on Web standards, passing Acid1 completely and Acid2 with only minor glitches. But what I find best about Chrome/Iron is the security model. Each tab is a separate process, and each tab process has its system rights severely restricted. Even if the browser itself is running in an admin account, the tabs run as restricted users, with a few further restrictions. Malware may well run in a tab, but there is very little that the malware can do except run in the tab. It can’t install software, sniff other processes, write files, or survive the closing of the tab. It’s not a per-tab virtual machine (which is where I think malware will eventually force Web browsers to go) but it’s a giant step in the right direction. (InfoWorld has a nice discussion of the Chrome security model.) I’m still having a little trouble getting a technical grip on the merits and flaws of Chrome’s V8 javascript virtual machine, but I’ll keep sniffing around and will eventually figure it out.
The security model prevents many plug-ins from working correctly, and this may bother some people more than others. Not me: Plug-ins are the 900-square-foot hole in browser security generally, and for basic Web research, I can do without, well, all of them.
I’ve only had a couple of hours to fool with Iron, and I’ll tell you right now that I like it a lot. I installed the portable version, which confines all of its files to a single directory and does not touch the Windows Registry. The rendering is very snappy, snappier than Firefox 3. (I haven’t touched IE in so long I didn’t even bother making a comparison.) It imported all my bookmarks without a burp, though it did not automatically place my Firefox toolbar bookmarks in its own toolbar. (I did that from Iron’s bookmark manager with one drag and drop.) I read somewhere that Iron had a built-in ad blocker, but I don’t see any controls for it, and I’m still seeing lots of ads.
Still, what attracted me to Iron is its approach to Web security…and over and above everything in the code, what may make Iron safest of all browsers is that it’s rare. Security exploits are often (if not always) app-specific or at least library-specific. Malware depends heavily on the density of the installed base to succeed, which is why so many exploits target IE, and more recently Firefox. As long as the software works well for me, I don’t care how few copies are out there–in truth, the fewer the better. SRWare has kept up with patches on both the Chrome code base and the WebKit code base (which Chrome itself hasn’t kept up with) and assuming they continue to do so, we may have us a breakthrough in the malware wars. It’s still early, but I’m already very impressed. (I’ll come back with “highly recommended” if I still think so in a few weeks. Stay tuned.)
Odd Lots
- The dairy that delivered milk to our house when I was a kid was indeed Hawthorn Mellody Farms (as verified by the Sister of Eidetic Recall) which was unusual in several ways: They had an amusement park in Libertyville, Illinois, complete with a miniature train ride, a petting zoo, Western town, and pony rides, that was a famous destination in the 50s for suburban moms with station wagons full of Boomer kids. They were the first dairy to put pictures of missing children on milk cartons. And before they went bankrupt in 1992, they were one of the largest Black-owned businesses in the country.
- Also relevant to my entry of Febraury 24, 2009: Dunteman’s Dairy evidently existed before 1939. A page out of the 1937 Arlington Heights phone book from Digital Past shows an entry for Dunteman’s Dairy at 830 N. Dunton Avenue in Arlington Heights. The 1936 phone book shows a listing at the same address for “L. Dunteman,” so Lenard may have begun operating the dairy from his back yard (not an uncommon thing to do back then!) in that year. Prior to 1936 his listing shows yet a different address. I’ll have to see what’s at that address today the next time I’m in the area.
- Digital Past is a very good source if you’re doing genealogy research on Chicago’s northwest suburbs; awhile back I found the location and a photo of the headstone of Laura Brommelkamp Dunteman there, after looking in vain for some years. (She was the second wife of Henry Dunteman, founder of R. W. Dunteman Construction, which is still in operation in Chicago’s western burbs.)
- Well, grub is still plug-ugly, but it’s no longer difficult to configure. I’ve been using KGrubEditor for over a month now, and it makes the job a breeze. Highly recommended.
- Where’s my flying car? Well, it may be here: Yet another Skycar concept, but this time it’s more Mad Max than Flash Gordon. Put a big fan on the back of a go-kart, get up some speed, and then release the parawing. Off you go!
- Philip Jose Farmer has left us. Along with Heinlein, Clarke, and Keith Laumer, Farmer was one of the SF writers who inspired me to keep going and make something of myself in fiction. I still consider the Riverworld concept one of the most compelling ideas ever to surface in SF, even though the series wandered toward the end and would have been much better had it been three books (on the outside, four) instead of five.
- I was going to do a whole entry on this, but Cory Doctorow said everything I intended to say about whackjob Roy Blount Jr and the knucklehead Authors’ Guild, who want money from anyone who does text-to-speech. There’s nothing I can add, and as a longtime author who still makes money writing, I think I have a right to strong opinions about this. Let me quote Cory here, and cheer:
-
Time and again, the Author’s Guild has shown itself to be the epitome of a venal special interest group, the kind of grasping, foolish posturers that make the public cynically assume that the profession it represents is a racket, not a trade. This is, after all, the same gang of weirdos who opposed the used book trade going online.
A Chart, If You Can Read It
The last couple of evenings I’ve been working at fulfilling a promise I reneged on ten years ago. Somewhere in the text of the second edition of Assembly Language Step By Step (which I was writing in the summer of 1999) I promised readers an ASCII chart as one of the appendices. I then plum forgot, and the book appeared in 2000 without that appendix. I still get emails from people asking me where they could find the chart, and have to reply in my best sheepish email voice that no chart exists anywhere in the book.
So this time I thought to put things right. I sat down in front of InDesign and figured out an ASCII chart format for the full 256-character extended set, and drew me an ASCII chart. For the encoding I used Code Page 437, which is what they now call the IBM PC ROM character set. Whether they could name it or not, CP437 was much beloved of DOS text-mode programmers, with all four card suits and more box-draw characters than anybody ever knew what to do with. The chart will fit comfortably (if snugly) on a single page in what we in publishing call “computer trim,” and I consider it a complete success, at least if you have good eyesight or a set of readers within easy reach.
Except…
As best I can tell, there is no encoding option available for Konsole (or any other Linux terminal emulator that I have) for Code Page 437. As close as I’ve come is IBM-850, which has fewer box-draw characters and more non-English alphabet glyphs. Of course, once you have a chart, it’s no big deal to find a new set of glyphs and sub them in, which is what I’ll be doing in coming days. In the meantime, if you have any use at all for a CP437 ASCII chart, here it is. I’ll post the one for IBM-850 when I finish it. Ten years late, I guess, but better late than never.
Debuggery
In parallel with editing and (increasingly) writing chapters, I’ve been interviewing tools to feature in later parts of the third edition of Assembly Language Step By Step. Kate has the gig for editor, but the debugger slot has been annoyingly open for a long time. Since the beginning of the year I’ve been interviewing debuggers and GUI debugger front-ends for gdb, which is more an engine than a debugger and may well be the single most painful piece of software I’ve ever had to use. (Don’t get me started on that. Whoops. Too late.)
It’s been frustration cubed. Here are some notes on the fray thus far:
- Nemiver does not work correctly with assembly language executables.
- Insight would be a good choice, but it is one of the ugliest things I’ve ever seen running on Linux, and I mean ugly in the sense of, well, ugly: Badly rendered Motif/Lesstif screens that seem scruffier than they should be, with hard-to-read tiny fonts. I know why they used that widget set (it’s very lightweight) but I also think that’s no longer anything like an issue in the Linux world.
- DDD is uglier than Insight, and doesn’t work as well.
- KDbg was my favorite for a long time, because it’s not ugly and fairly straightforward to use, but its help system is broke and I never figured out how to dump memory or display named data items from assembly. Like Nemiver, it was really created with C and C++ in mind. Like people tell me endlessly (and shut up, already!) “Nobody uses assembly anymore.” Heh.
As I race past 65,000 words and close in on the end of Chapter 6, I was forced yesterday to make an executive decision and call Insight the winner. Insight is interesting in a number of ways: It’s not a GUI front-end for gdb; it is gdb, and has knowledge of gdb’s deep internals in a way that a separate app simply can’t match. The GUI was written in Tcl/Tk, a language I learned and enjoyed almost fifteen years ago when I got Ousterhout’s book in for review at PC Techniques. One would think it would be no big deal to rewrite Insight for Gtk or Qt, but I don’t see the dust from any stampede.
So I got me an ugly debugger. That is (given my deadlines and the significant amount of money riding on the project) better than no debugger at all.
KDE Follies
I’ve been busy. And I’ve had headaches. This is mostly why you haven’t heard from me in a few days. I wondered for awhile if I was getting headaches because I was busy, but I’m coming around to a different point of view: I’m having headaches because I’ve been fooling with KDE.
I used to like KDE, until KDE 4 happened. Kubuntu 8.04 would not install correctly on two of the three machines I tried it on, and on the third it malfunctioned weirdly after a couple of days of very light use. I had almost no trouble with Kubuntu 7.10, apart from its failing to set up a network printer. That was KDE 3.5, which I liked. The press on KDE 4 was not good, and I figured I would let Kubuntu rest for a couple of cycles to see if the KDE 4 codebase would shake out a little.
I might have waited for 9.04 except that I couldn’t get the KDbg documentation to run under GNOME. I like KDbg a lot; it’s a beginner-friendly front end to the highly human-hostile gdb debugger engine. I’d like to cite it in my book, but there are a couple of things about it that I just can’t figure. Press F1, right? Well, when I do that, I get a mysterious error dialog:
Could not launch the KDE Help Center:
Could not find service ‘khelpcenter’.
I assumed at first that this is what happens when you have a KDE app running under GNOME, but the kate editor is also a KDE app, and its help document comes up without any trouble. The khelpcenter4 package is installed on the system. The obvious thing to try is to run KDbg under KDE, and see if things work any better.
Of course, to do that you have to have a running install of KDE.
I downloaded the latest Kubuntu ISO (in 13 minutes on BT!!), burned it to CD, and booted the live install on my SX270, the same machine on which Ubuntu 8.10 installed without a glitch. Kubuntu detected the monitor resolution, but…the display blacks out every six seconds for about three-fourths of a second. Otherwise (heh) it runs perfectly. The blackout is not a fade; the screen just turns black instantly. It made me a little nuts, but I suffered through this game of desktop peek-a-boo long enough to install KDbg. I pressed F1. Same dialog. KDE can’t seem to make its own help system work.
So KDE is on that certain list of mine right now. Even though it displays the assembly source for single-stepping, KDbg won’t display named initialized data in NASM executables, and the Memory window refuses to display anything, initialized or otherwise. Being able to inspect data in memory is mighty damned useful, and I’m starting to think that KDbg isn’t really set up to debug assembly language. Like almost everything else in the Linux world, it’s a C thing. Maybe there’s a magic command-line option that allows it to interpret stabs format debug data for assembly language, but there’s nothing much about it online. Clues welcome.
And Kate? The only thing it lacks is a shortcut for running make or launching a debugger, but that’s easy enough to do in the terminal window. It’s graspable enough for beginners, and that’s what I’m striving for here. Newcomers should not have to learn EMACS or gdb to make “Hello world” happen in assembly.
I don’t want to have to use gdb Insight (if there’s an uglier widget set than Lesstif’s I’ve yet to see it) but if I can’t get KDbg to browse data in memory, I may have to. And the decision has to be made soon. (I feel another headache coming on…)
Odd Lots
- German model train manufacturer Marklin has filed for bankruptcy, though there is still some hope that the 150-year-old firm will remain in business. Thanks to Pete Albrecht for the link.
- Scientific American has an interesting retrospective on the infamous nuclear-powered B-36 that actually flew back in the late 1950s, with a live, air-cooled fission reactor in its rear bomb bay. I’m less twitchy about nuclear than almost anyone I know, and that item still gives me pause. (I do think that the stock B-36 was the coolest military aircraft of the transition period between props and jets, and one of the coolest of all time, period.)
- From Rich Rostrom comes an aerial photo of the Fovant Badges, which are a group of military insignia cut into the Wiltshire chalk downs in southern England. They date back to WWI, and have been laboriously maintained since then–a job and a half, considering that some are over 200 feet wide.
- When I first heard Cher’s uber-irritating hit “Believe” years ago I wanted to know what sort of processing was going on with her audio. I didn’t want to know enough to search too deeply, but it recently turned up on Slashdot. The gadget is called Auto-Tune. And Cher can actually sing when she wants to; one wonders what it could do for no-voicers like Bob Dylan.
- I’ve never paid much attention to KDE’s Kate editor, but discovered today to my delight that it has syntax highlighting for NASM. I’d basically given up trying to find a lightweight Linux assembly language IDE to describe in my book, but half an hour of lightweight fooling around with it makes me think that Kate might be the one. Now all I have to do is become an expert in the next couple of weeks. Are there any books on it, print or e? I looked around and have found nothing so far.
- From the Words I Didn’t Know Until Yesterday Department: interpunct, which is a small dot used originally in Latin to unambiguously mark the spaces between words. It’s still used today to show you where the invisible characters are on your screen, and I recognized the concept immediately, but never knew what it was called.
- From ditto: A placket is a flap of cloth that hides a button on fancy clothes. I have a pair of pants with one, and again, never knew what it was called until very recently.
- Pete Albrecht pointed out a source of very nice cast aluminum house numbers in the Craftsman style–though at prices like these, I’m glad I have only a 3-digit address.
- From the Painting the Devil on the Wall Department: One of the nation’s leading promotors of monster truck shows was run over and killed by a monster truck at one of his own shows. (Again, thanks to Pete for the link.)
- From Ed Keefe comes a pointer to a stunt kite fitted out with a microcontroller, an accelerometer, and LEDs so that it could be flown at night and turn different colors depending on how fast it’s going and which way it’s pointing. I flew a kite at night in 1965 and only knew what it was doing by the crackle noise it made and how hard it pulled on the string. Technology advances…
The Yard’s All Out of 3 X 4s…
I’ve gotten far enough into the revision of Assembly language Step By Step that I need to have a Linux machine running up here in my office all the time. I often spend hours in Ubuntu on this dual-boot machine, but there are still some things I need to do in Windows, and booting in and out to bounce from one to the other is time wasted, and pointless when I have old PCs stacked like cordwood in the basement.
I have one of the very cool SX270 stainless-steel all-in-one brackets that combines a 10cm VESA monitor mount with a couple of tangs to hold an SX270 mini-PC behind the monitor. It makes for a very compact system, and in fact it was the integration of the SX270 and the monitor on the bracket that first brought the SX270 to my attention some years back, when I saw a couple of them at our optometrist’s office. So I took my spare SX270, parked it on the bracket, dug a Dell keyboard and a mouse out of the odd lots box, and realized that I did not have a VESA monitor to hang on it. So off we went to Best Buy, where I learned from the earnest young woman in the computer department that they had not sold 4:3 monitors for almost a year now. Every single one in the long line on display was 16:9.
I know why this is the case (home theater) and whereas it wouldn’t be my first choice, I’m willing to use that form factor, and really needed a monitor. I was apprehensive for a simple reason: The SX270 was made in 2003, and I don’t recall the machine supporting the 1600 X 900 resolution of the smaller 16:9 LCDs. I took a chance, figuring (or at least hoping) that I could rummage around online and come up with a newer driver for the Intel 82865G graphics chipset.
What I bought was a Samsung SyncMaster 2033SW. It’s VESA-compliant, and I bolted it to the stainless steel bracket without difficulty. It was on sale for $179. The machine itself cost me less than that; I think $150 on eBay some time last summer. 2.8 GHz, 1 GB RAM, with XP Pro–used and used hard, and ugly up close, but completely functional. I went up to Dell’s site to see if newer video drivers were available, but what they had was what I had. The closest that Windows could come to 1600 X 900 was 1280 X 768. The monitor centered the smaller raster in the middle of its screen, with the surrounding pixels dark. There was a “stretch” option that spread the raster out to the full extent of the screen, but it looked hideous.
Fortunately, Windows wasn’t the goal here. I booted the Ubuntu Intrepid installer CD in LiveCD mode to see what the OS would detect and how it would respond, considering that the machine dates back to 2003. Without a grunt of complaint, it detected the graphics hardware and loaded a 1600 X 900 driver. I tried a few things, pronounced it good, and told the OS to go install itself in earnest. Twenty minutes later, I was downloading NASM, Kdbg, the Bless Hex Editor, Nemiver, ddd, and a few other things through the Synaptic Package Manager. Not once did I have to face a command line. Everything Just Worked. The age of the machine (apparent from its collection of dents and inventory-tag stickum) didn’t seem to matter at all.
The display is gorgeous; it’s easily the brightest LCD I’ve ever seen. The whole gadget takes up about as little space as anything with a 20″ monitor possibly could. And after spending an afternoon with it, I realize that a long horizontal aspect can be handy: Editor on the right, Kdbg on the left, and just enough of a terminal peeking out under the editor to run make as needed.
I’ve been fooling with Linux intermittently for well over ten years, and the craziness of today’s events still boggles me: It installed much faster and way more easily than Windows generally does, and on old hardware to boot. This was not the case in 1999, let me tell you. If MS isn’t in trouble by now, it’s nobody’s fault but our own.
Odd Lots
- From the Words I Didn’t Know Until Yesterday Department: The Ranters were a wild-eyed seventeenth-century religious fringe group, who were perhaps most notable for incorporating nudity into their worship. (Whatever else they might have been, they sure weren’t Catholic.)
- From ditto: In modern urban slang, a “butterface” is a homely girl with a great body, as in, “Every part of her was perfect but her face.”
- And elsewhere on the words front, even William Safire, from whom the scariest words recoil in terror, was unable to determine the origin of that very up-to-date and with-it 90s expression, “it is what it is.” Wikipedia suggests that it was coined by John Locke, circa 1680. So much for being up-to-date.
- From the Microprocessors I Never Heard of Until Yesterday Department: There was an 80376. It was an embedded variant of the 80386 that did not support real mode, but only protected mode, and was produced from 1989 until 1994.
- Much angst is flowing about the blogosphere concerning the Conficker worm, but this is the first page about it that I respect at all. I’ve long since disabled Autorun, and in fact, “autorunning” things is one of the worst ideas in computing since DLLs. Make sure you’ve got that November patch they speak of
- And while we’re talking worms, here’s some news on a piece of malware that comes in on pirated Mac software, evidently with the intent of creating an all-Mac botnet. The dangerous thing here is that a lot of nontechnical people seem to believe that the Mac is immune to malware somehow. OS/X is certainly tougher to infect than Windows, but it can be done, especially when people are sure that it can’t.
- Carol and I launch our Internet-facing apps under a clever mini-utility called DropMyRights, which basically runs such apps with limited user account privileges instead of admin privileges, even if you’re running as admin. Doesn’t work on Win2K, so I have not used it myself until fairly recently, but I installed it on Carol’s XP box probably two years ago, and she has used it daily without any issues since then.
- I have tried and failed to make a Linux utility called KGrubeditor work under my instance of Ubuntu Intrepid. When I attempt to launch it, an item appears in the taskbar for about fifteen seconds before vanishing, and nothing else happens. At least one another person I know has made it work correctly, but I just don’t see what I’m doing wrong. I installed it through Ubuntu’s apt-get shell and saw no errors during the process. If any of you are users and are aware of any trickiness in the utility, I’d love to hear more.
