I am seeing the following problem appearing on random occasions during regular
usage of my regular updated KDE/F14/64bit system.
The desktop becomes extremely slow and unresponsive, out of the blue. It lasts
for about a minute or two, and then reverts to normal. If i happen to have a
terminal open when it happens, I can see in top that usage of both CPUs goes
to 100%. However, it's not because some process is using them, but because
both CPUs are wasting cycles in "wait" state for I/O.
Then if I manage to start iotop to see what is sucking all disk I/O, I see
that 99.99% of I/O is being used by something like
virtuoso-t +foreground +configfile /tmp/virtuoso_Lh1825.ini +wait
Would someone explain what is this, why is it running on random, what triggers
it, and --- most importantly --- why is it configured by default to suck all
life out of my system during its (presumably normal) operation?
yum info virtuoso-opensource says:
Summary : A high-performance object-relational SQL database
Description : Virtuoso is a scalable cross-platform server that combines
SQL/RDF/XML Data Management with Web Application Server and Web Services
This suggests that it is some kind of database used by KDE (or something
else?), so I can understand that it can be resource-hungry. However, I don't
understand what is its purpose on my system?
If I try to yum remove it, it wants to remove most of the OS istallation,
including kdebase, so I guess it is something very required by KDE.
I would be very thankful if someone explains what this is and how to make it
do its work only when the system is idle enough (say, when the screensaver has
been active for half an hour, or something like that), and not in the middle
of my regular work.
Fedora 14 (x86_64) on a Lenovo ThinkPad T510 an "nVidia Corporation
GT218 [NVS 3100M]" GPU.
I normally don't use my laptop's built-in display when it's at
home, so I'm not exactly sure when it started, but I suspect that
the recent update to KDE 4.6 was probably the trigger.
I can boot my system and log in to GNOME just fine. Logging in to
KDE, however, causes the brightness of my laptop display to become
unusably dim. This happens whether or not the laptop is running on
AC power. The screen does return to its normal brightness momentarily
when I connect AC power, but it then returns to its dim state.
The KDE brightness controls are still set to full brightness; I can use
them to change the display from unusable dim to completely black and
The only way I have found to restore the display to its normal
brightness (until I log in to KDE) is to reboot.
Anyone have any idea what might be going on? I really am completely
unable to use KDE this way. :-(
When opening a new page, the latest Google Chrome (10.0.648.82 beta,
F14) frequently pops up a KDE Wallet dialogue asking for a keyring
password. This seems unrelated to whether the page itself wants a
No previous version of Chrome did this, in fact I'm surprised Chrome has
any interaction with KDE at all.
Has anyone seen this? I'm asking here before reporting to BZ.
When I enable desktop effects (nouveau/openGL) by default the panel gets
transparent. Really nice, but this in combination with the Lovelock wallpaper
makes the date e.g. very hard to read. Especially the bottom of the paper is
Anyone else have thoughts on this?
Per our team meeting this week and after consulting upstream, the kde-sig
decided kdepim-4.6 isn't ready yet and and to roll back to kdepim-4.4.x for
fedora 15 (and ideally squeeze this in for the upcoming alpha release).
We'll continue to provide kdepim-4.6 in rawhide (targetting f16 now) and
unofficial test builds in kde-unstable repo for further testing and
I used to be able to remove the Sleep and Hibernate options from the kde
Leave menu, systemwide, by having pm-is-supported do an "exit 1".
However, after the kde 4.6.1 update this no longer stops the Sleep and
Hibernate items appearing. How would I remove these items systemwide now?
Did something change recently with KTorrent? Did the search portion get
removed or is it still there and just hidden? I used to be able to search
for and download torrents using KTorrent, but now it only appears to
download them. Just wondering.
Since the kde 4.6.1 update my kdm greeter colours are different.
In the [X-*-Greeter] section of /etc/kde/kdm/kdmrc I have:
which used to give the desired colour scheme.
I've tried changing ColorScheme to other values like Steel by hand
and nothing seems to change.
I tried using the Login Screen panel from System Settings (General Tab,
appearance section), which
curiously has Colour Scheme set to "<default>" despite having set
ObsidianCoast in kdmrc, but setting "Obsidian Coast", there didn't help.
Does changing the colour scheme work for anyone else in 4.6.1?
Hi - the recent KDE update in F14 caused Amarok to lose all the music files
in its database - nice!
You can get them back by going into Configure Amarok and doing a "Full
After upgrading to 4.6.1 this morning I have problems with Kontact/Kmail.
I have commented on https://bugzilla.redhat.com/show_bug.cgi?id=693177
My first problem was with the "Akondai progress bar" was stuck
bouncing left to right and back. Kontact didn't start.
I moved ~/.config/akonadi and ~/.local/share/akonadi, and that first
the Akonadi startup problem but then I couldn't send email. The send
button highlighted but then the program completely hung. It needed a
kill -9 to remove it.
I tried a clean kmail installation (moved all the kmail/kontact
directories and files from .kde/share/apps and .kde/share/config but I
still had the same problem.
I had been been using akonadi-googledata-1.0.1-1.fc13.i686 from
tomasj's repository so I removed that. That didn't resolve the
Next I looked at Akonadi (google data was removed) and I looked at the
server configuration. I ran a test and there were lots of errors
including MySQL server not found etc. I stopped the Akonadi server and
restarted, re-ran the test and they were now all passed except
"Previous Akonadi server error log not found".
Suddenly a "hanging kmail send" which was in the background suddenly
jumped into life and the mail was sent.
I'm not reimporting my folders to the new structure and we'll see if
there are any further problems.
It seems to me that Akonadi is the part at fault here and that moving
away ~/.config/akonadi and
~/.local/share/akonadi doesn't solve the problem completely.
paulsscott at gmail.com