Mailinglist Archive: opensuse (1523 mails)

[C <smaug42@xxxxxxxxx>]

OK, the problems reported here got me thinking, and wondering... did I
do something different or tweak something I forgot... so, I took my
netbook (Asus Eee 1005 with 2GB Ram and intel 945 GME video - this is
NOT a high spec machine, so any resource intensive things are VERY
noticeable) and wiped the drive clean and did a fresh install of
openSUSE 11.2.  I ran it for a while on KDE4.3.1, setting up the
desktop etc. (eg turning off desktop effects) Then I did a full update
to KDE 4.3.5... again running it for a while, changing some desktop
options etc.

The next step was updating to 4.4.1 via the 1-Click link on the oS
WIki.  This popped up a load of conflict resolution errors that were
resolved by changing vendor.  Then I skimmed through the installed
apps, and picked up a few KDE4.3.5 that needed to be manually added to
the list of updates to 4.4.1.  I also removed QT3 (was installed by
default on the initial I guess).  The update ran, and then I rebooted
(I know no need to reboot, but.. I did just to be sure everything was
clear and started up properly).

In this upgrade path, I did NOT remove the config files (as I
suggested might be the solution in a previous reply).  I left the
config in place through each version upgrade.


On Fri, Mar 26, 2010 at 12:38, Vadym Krevs wrote:
> > > 1. Immediately after login, various nepomuk/aconadi/strigi/virtuso-t
> > > services tool over my machine and for 15 minutes there was no was to
> > > do anything at all due to CPU/IO usage caused by these. Lots of users
> > > complained about this in the past, and yet nothing's done to make this
> > > an on-demand activity.
> >
> > You can turn it off in the options.
>
> The whole point is that one should not have to turn it off  -  IMHO,
> there should've been an option to turn it on by default, so people do
> not have to automatically lose control of their machines after login.

After restarting, Nepomuk was NOT running by default.  I did not turn
it off in the 4.3.1  and 4.3.5 configurations.  I enabled it in the
desktop options, and it started indexing for the first time.  The CPU
load bounces around while it's indexing, but it does not overload my
hardware such that I cannot use it, but it does definitely put some
load on the system - but since in my testing it was off by default...
it's not really a problem I would think.  Note, the hardware is not
high spec on this test I just did (Intel Atom 270 CPU and 2GB Ram).

Why is it on by default with some people's installs and on others it's off?


> > > 2. The  new konsole is simply not usable. It fails to render many
> > > fixed width fonts, is very slow to resize, etc. A quick search on

I tested Konsole over and over trying to trigger this problem, or see
some evidence of it happening.  Konsole is currently set to use
Monospace 8 font, and Linux Colors (Black background, and light grey
font).  I can resize the Konsole to any size and it's very very fast.
No problems at all.


> Again, the key issue here is that konsole worked just fine, absolutely
> zero problems, under KDE 4.3.5, same xorg, same video drivers, etc.
> The problem appeared after upgrade to KDE 4.4.x, hence it is a
> regression.

But.. on what?  I cannot dpulicate this in my tests.  Konsole works
100% as expected in 4.3.1, 4.3.5 and 4.4.1.  If it's a regression...
where is the regression.


> > > 3. The first time Konqueror started and I attempted to enter text into
> > > the search box, suddenly the search box (and all text boxes/drop
> > > downs/combox in all running KDE apps, not just konqueror!!!) became
> > > several times taller. I did try to log off, restart KDE, and log back
> > > on, and the issue came back almost instantly.

I tested this too.  I started up Konqueror in each version of KDE4 I
had... I typed into the search box... and in all cases it worked
exactly as it should.  No resizing...


> Of course I didn't. Am I being so unreasonable to assume that it is
> ridiculous to expect users to discard all their preferences and
> customizations when upgrading from one KDE release to another? I could
> buy that argument when upgrading from KDE3 to KDE4, but there is no
> excuse for that now. KDE 4.4.x ought to offer a seamless upgrade
> experience for any KDE 4.3.5 user, otherwise what's the point?

In my tests in the past 2 days, I found that I didn't need to reset my
profile at all during the update cycle.... so I retract my comment
about needing to remove the config.  This was something that was
necessary at one point, but is no longer (at least in the testing I
did today) - I learned something :-)

So, I'm still confident in the stability and usability of KDE4.4.1.
On all systems I run it on.. laptops, netbooks, desktops/servers, it's
working very well.

C.
--
To unsubscribe, e-mail: opensuse+unsubscribe@xxxxxxxxxxxx
For additional commands, e-mail: opensuse+help@xxxxxxxxxxxx