I have upgraded a Lenovo Thinkpad x60s from Feisty to Gusty. Everything went well with the exception of vmware server and display settings. I had to recompile vmware to their latest release. I am having difficulty with the dual screen options in Gusty. If your dual screens are permanent, it works great. If you use a laptop screen with another monitor and you undock and dock, then I run into issues. Other than that, my experience has been good.
<br><br><p><DEFANGED_div><DEFANGED_span class="gmail_quote">On 11/1/07, <b class="gmail_sendername">Michael Mol</b> <<a href="mailto:mikemol@gmail.com">mikemol@gmail.com</a>> wrote:</DEFANGED_span><blockquote class="gmail_quote" DEFANGED_style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">
On 11/1/07, Bob Kline <<a href="mailto:bob.kline@gmail.com">bob.kline@gmail.com</a>> wrote:<br>> It's been a couple of weeks now<br>> since the launch, does anyone here<br>> have anything good to say about
<br>> Ubuntu 7.10?<br>><br>> Many of the reviews have been<br>> quite bullish. I'm running<br>> Kubuntu 7.04 now, and have so<br>> far taking an "if it ain't broke, don't fix it"<br>
> approach. But I'd hate to miss out on<br>> anything either....<br>><br>><br><br>I actually wrote a second review on my blog, earlier this week.<br>Here's the text:<br><br>So I've been using it a couple weeks, now, and I figured it was a good
<br>time to give it a second look.<br><br>I've had to leave Compiz enabled, because without it, It becomes a<br>hassle to have both Firefox open and watch videos using mplayer.<br>(Firefox hogs X11's XV extension, thanks to the flash plugin. Compiz
<br>seems to perform the functional equivalent of providing a separate<br>copy of the extension to anyone who asks for it.) As a result, I've<br>learned a bit about its behavior.<br><br>The alt-tab behavior is nice. I realize some of you more advanced
<br>folks (Including OS X users and Linux folks using experimental window<br>managers as far back as 2002) have had window previews in your<br>window-switching service for a while. Sure, yeah, it's a convenient<br>feature if you've got multiple windows from the same app loaded. (Web
<br>development with Firefox would be a lot easier if I had this at work.)<br>At home, that's not really an issue for me.<br><br>What's really nice is how passing through the alt-tab list draws the<br>window immediately to the foreground, before I let go of alt-tab.
<br>(FWIW, all my apps are full-screen at home, so I don't know if the<br>window order is permanently adjusted as I pass through.) Now, on<br>Windows, this would be a problem. Each time a portion of a window<br>becomes visible, Windows sends the application a paint message to get
<br>it to redraw itself. At work, when my box was churning over one thing<br>or another, or waiting on some silly user-global lock (Damn you Visual<br>Studio, damn yooou!), I could watch the application ponderously fill<br>
in the window with information.<br><br>In Gutsy Gibbon, with Compiz enabled, the screen contents just flip to<br>the window, pre-drawn. (If I had to guess, I'd think the window never<br>knew it was covered.) The screen changes quickly enough that the new
<br>data appears to be there right at the start of the screen's next<br>vertical refresh.<br><br>Also, there's a neat feature for dealing with unstable applications.<br>If the application "stops responding", to steal a phrase from the
<br>Windows world, the window desaturates until it's wholly in grayscale.<br>That way, you know why it's not doing what you thought it was doing.<br>This doesn't seem to work entirely, though. I was scrolling through
<br>Google Reader--albeit painfully slowly--when the window desaturated. I<br>hadn't stopped scrolling, and the window was still updating, but the<br>window manager decided for some reason that the window had stopped<br>
responding. However, it corrected itself, and resaturated the window<br>after I stopped rolling the scroll wheel on my mouse.<br><br>However, Firefox seems to have taken a hit. It's weird. Up until a<br>couple weeks ago, I never had noticeable stability problems with
<br>Firefox, at work or home, despite both machines being low-end (3GHz or<br>2.2GHz P4s, respectively, though the work machine has 2GB of RAM and<br>the home machine only has 512MB/). In contrast, it's run slow or<br>
crashed three times in the last week. This is only at home, though. My<br>box at work is still running strong. The obvious answer is that<br>Firefox's memory leaks are likely coming into play earlier on my home<br>box.
<br><br>And I'm still irritated that I can't play StepMania. That might change<br>this weekend, though.<br><br><br>--<br>:wq<br>_______________________________________________<br>grlug mailing list<br><a href="mailto:grlug@grlug.org">
grlug@grlug.org</a><br><a href="http://shinobu.grlug.org/cgi-bin/mailman/listinfo/grlug">http://shinobu.grlug.org/cgi-bin/mailman/listinfo/grlug</a><br></blockquote></p><DEFANGED_div><br>