Skip to main content

SLED 10 and Google Earth commingle, cause desktop to crash

I was running Google Earth 4 on SLED 10 this morning when I decided to go and 'visit' Denver, Colorado. You can see the screenshot of it below, taken right before the desktop crashed and kicked me back out to the login screen.

Before I get into the gory details of the crash, let me describe what happened up to that point. I'd navigated to Denver and oriented the view as you see above. I had 3D buildings enabled. I noticed that it took 15 minutes for the view to completey render, which was far, far longer than another other city I've been to via Google Earth. While it was rendering is was chewing processor time up like nobodies business (according to the Gnome system monitor). Moving from screen to screen was sluggish, so much so that when flipping to Google Earth's screen it froze for a number of seconds in mid-turn, before showing full on. This, on a machine running SLED for X86_64 using an Athlon FX-55 with 4GB of memory. It has never taken this long to render any view, and it still doesn't, as long as I stay away from Denver. What's interesting about Denver is that the 3D buildings being rendered are very high quality and very high detail, far more so than any other city I've viewed to date. I'm sure that played into the very long render time and the subsequent crash.

After Google Earth was finished (Streaming posted 100%), I took the screen shot you see above. Then I attempted to zoom in and re-orient the view to take a closer look at the Qwest building. That's the tall round, brown building near the lower right edge of the screen shot.

Here's Denver again, but this time I've moved in and around for a better look at the Qwest building. This is using Google Earth 4 on Windows XP (the Gateway M685 notebook). The detail is gorgeous, and by the way it looks every bit as good on Linux. The problem is that looking at Denver with Google Earth on Linux causes performance and stability problems.

Here's the setup on the Linux system:
  • Boxx system using Athlon 64 FX-55, with 4GB of ram, nVidia Quadro FX 540.
  • the nVidia drivers are installed, the monitor ia a Samsung SyncMaster 740B at 1280 x 1024.
  • SLED 10, X8674.
  • Compiz desktop manager enabled and running.
When I attempted to zoom in on the Qwest building, the desktop crashed. I was kicked off the desktop and back out to the login screen. When I logged back in, the compositing desktop features were disabled. I couldn't figure out why at first, but a clue was that the desktop would not fit completely in the monitor's screen. When I checked the screen resolution I discovered the screen's resolution has been kicked to 1400 x 1050. That broke Compiz (it looks like Compiz won't handle the odd screen resolution). So I put the resolution back and rebooted first the desktop, then eventually the entire box. I'm back to working on the desktop.

I guess I should be thankful that unlike Windows I didn't get a BSOD. But crashing the X desktop is no less acceptable, especially when the resolution is seemingly screwed up. And considering that this is an Enterprise release (that's what the 'E' in SLED stands for) I have very little tolerance for loosing my work this way. I had all four screens filled with something running (NetBeans 6 on one screen, Protege 3.3 on a second, and Google Earth 4 on a third, not to mention Firefox and terminals...). I can live with applications crashing, but not an application crashing and taking a major part of my OS with it along with all my work. No, the machine did not lock up. Yes, I lost all my work up to that point. A crash of this magnitude is as bad as a Windows BSOD. I had the same loss of time and productivity. I am not amused.

I'd be curious to hear what Suse folks have to say about this.


Popular posts from this blog

cat-in-a-box channels greta garbo

So I'm sitting at my computer, when I start to notice a racket in back. I ignore it for a while until I hear a load "thump!", as if something had been dropped on the floor, followed by a lot of loud rattling. I turn around and see Lucy in the box just having a grand old time, rolling around and rattling that box a good one. I grab the GX1 and snap a few shots before she notices me and the camera, then leaps out and back into her chair (which used to be my chair before she decided it was her chair).

Just like caring for Katie my black Lab taught me about dogs, caring for Lucy is teaching me about cats. She finds me fascinating, as I do her. And she expresses great affection and love toward me without coaxing. I try to return the affection and love, but she is a cat, and she takes a bat at me on occasion, although I think that's just her being playful. She always has her claws in when she does that.

She sits next to me during the evening in her chair while I sit in mi…

first night for the gingersnaps

The first night has passed and the two have managed to survive, in spite of what their tiny hearts might have thought when first arriving. Greebo, the larger of the two, has been in hiding the entire time so far. Ponder has spent the time zipping in and out of hiding spots, checking things out, and learning just how comfortable pillows are for resting your head.

During the night I felt the tiny body of Ponder hitting the bed as he leaped up on the side, and then climbed to the top to run around on top of me. At least once he play-attacked my fingers. He might be small but his claws are still quite sharp.

When I got up in the morning the bowl of cat kitten food was fairly well depleted. It's been refilled and fresh water put in the big dish on the floor. I'm assuming that both Greebo and Ponder are feeding and drinking. I have seen Greebo under the furniture peeking out at me when I went looking for him. I'm leaving him alone while he continues to adjust.

So far the guys h…

vm networking problem fixed

Over the weekend I upgraded to Windows 8.1, then discovered that networking for the virtual machines wouldn't work. Then I tried something incredibly simple and fixed the problem.

Checking the system I noticed that three VMware Windows services weren't running; VMnetDHCP, VMUSBArbService, and VMwareNatService. VMware Player allows you to install, remove, or fix an existing installation. I chose to try fixing the installation, and that fixed the problem. The services were re-installed/restarted, and the virtual machines had networking again.

Once network connectivity was established there was exactly one updated file for Ubuntu 13.10, a data file. This underscores how solid and finished the release was this time. Every other version of every other Linux installation I've ever dealt with has always been succeeded by boatloads of updates after the initial installation. But not this time.

Everything is working properly on my notebook. All's right with the world.