I normally run with 512MB memory, but gave 256MB to the wife when she needed to give XP a kick up the rear, consequently when I came to upgrade from 6.04 to 7.10 (clean install from CD) it seemed to to take an age just to get the first screens running I gave up and borrowed some memory from our sons machine, we were done and dusted in no time.

The only other problem I had was installing Seamonkey, it could not find libstdc++.so.5, not sure where that problem stems from, after a while I installed libstdc++5 using the Synaptic Package Manager, problem solved.

Cheer diddy

No initial problems other than finding this whole compiz thing very confusing. It used to be extremely easy to tweak it to your taste but now I haven't got a clue where to start looking.

Another thing that came up recently is that mplayer crashed after an update. I had to reinstall it.

Looks like a recent update to kdelibs from the package manager fixed the MSN crasher in Kopete. . but I still can't find the compiz options. I'd like to turn it off if it isn't already, since my laptop only has 256 MB of RAM. I did the alternate install, and Kubuntu seems to run decently fast, but I think it could stand to use a little less RAM than it is, at present. (It's using most of the memory with not much at all running, and a little bit of swap as well. @_@)

Only major issue for me so far since moving my laptop from 7.04 to 7.10 (clean install) has been some new suspend problems. At least when running on battery, I'll sometimes get a blank screen when resuminig from a suspend. Also, my wireless (ipw3945) would stall sometimes when resuming from either battery or AC. I managed to work around the wireless problem by adding some commands in /etc/acpi/resume.d/ which reload the driver and NetworkManager. Can't figure-out what the deal is with the black screen, though. One time I did manage to get into X11 from the black screen by trying different key combos, only to find that both CPU cores were at 100% usage by the vbetool program. I'll be sticking with 7.10 for another month or so, trying to work around this (and any other problems I haven't seen yet). Also in the hopes that bugfix updates are headed down the pipe.

But if all fails, I'll go back to 7.04 (it worked fine for me). Might even do some distro hopping.

Just my .

did an upgrade the other day to gutsy- only problem so far is nvidia seems to random lock-up the screen (the only to get out of it when it happens is to physically restart the computer..) edited my xorg.conf file to use vesa- & that fixes the problem for now- but i got to get nvidia straightened out- no 3d graphics sucks...lol. also miro is depended on libboost- python 1.33- gutsy has a newer version of it- but miro doesn't seem to like that verson & gutsy doesn't seem to want to install libboost-python 1.33- lol. (-and while i'm at it- lol..) i gotta try & get my new delta 1010lt soundcard to run--lmao..

The number of running processes is almost double that of v7.04. I don't notice a big slowdown in performance, though.

Evolution won't store passwords for POP accounts.

Mail-Notification won't let me choose SSL/TLS as a connection type for checking POP accounts.

Kent

Tried the Soundblaster card again. I know it works with Fiesty but in Gutsy there is no output. All sound applications run normally with no errors, just no sound. Yes, the speakers work.

Kent

Which soundblaster are you talking about. I have a Soundblaster Audigy, it runs just as well as it did with Feisty.

I'm having the same problem as win32sux, Suspend blacks out my screen. It worked great in Feisty, now it doesn't. A number of programs also seem to load slower, and the initial boot is definately slower. I am strongly considering switching to another distro.

Multimedia audio controller: Creative Labs SB Live! EMU10k1

I had problems with the video on mine as well, my account showed up as 1024x768@85hz but another account on the same box came up as 640x480@51hz, logging into my account then back into the other account made the screen size correct but the setting still would not let it go above 55hz.

When I went back into my account instead of 85hz it wouldn't let me go about 55hz either. I tried to run the configuration wizard that I just ran two or three days ago but now it said that the file could not be found.

I've had it with 7.10 and went back to 7.04, PC works fine now.

Well happy with Gutsy, but still have to admit there's a few problems.

Everything seems so...well...slower. Not sure why, but nothing's immediate in Gutsy. Double-click any program, any window and the response time is definitely down on Feisty.

No doubt about it: boot time is definitely worse than Feisty. And I must agree with Danbuter that programs seem to load slower.

Have had big problems with the Impress element of OOo 2.3 (keeps crashing), but I don't put that down as a 7.10 issue. (If you know differently, let me know!) The rest of OOo is a bit creaky as well.

Azureus could be better, too. I don't like programs that open, complain and crash without any info as to what's wrong.

That said, 3D cube is fantastic, but compiz could take advantage of some real documentation for the benefit of those who give up after three mouse-clicks.

I'm a big ubuntu fan and I'll be staying with gutsy but I do have to be honest and say that there are a few issues. Speed being the main one.

This may not help, but for the sound issue, make sure alsamixer does not have your card on mute. The sound on my laptop refused to function at all with no errors until I finally installed gnome-alsamixer and found the master channel somehow muted. Why the hell it did that is beyond me...

Otherwise, it's slower and less responsive that Feisty. I have sluggishness when it boots up and after login, which has been driving me nuts.

Slackware does that too, couldn't figure out why I had no sound when Windows that was on the very same (box before I put Linux on it) the sound worked fine, then I opened the mixer and found the main sound muted.

Last night I finally found a thread dealing with a similar situation and it just required a simple edit of /etc/init.d/alsa-utils to make sure that the SB Live Analog/Digital Output Jack is set to off then doing an alsa-utils reset. The sound has been working ever since.

I agree, Gutsy is slower than Feisty.

Thanks for your input on the sound issue.

Kent