Has anyone other the problem that kmix (KDE 4.6.1 kde-testing)
consumes 100% CPU, i ca repdroduce this on two machines with
Workstation Core2Quad, Nvidia
Notebook Core2Duo ATI
Seems to be introduced by one of the updates last week, was not
so with the first 4.6.1 packages and i can not say what it triggers
my workaround now is a "killall kmix" if it happens
Has anyone actually used this?
I tried running it to download CentOS-5.5 DVD ISO,
but it caused complete confusion.
As far as I could see, after downloading about 400MB,
it started creating literally thousands of links to this file,
and then my server choked,
and when I stopped it by pressing the power button,
and re-started it the machine was in a confused state,
and took a while to clean up.
e-mail: gayleard /at/ eircom.net
tel: +353-86-2336090, +353-1-2842366
s-mail: School of Mathematics, Trinity College, Dublin 2, Ireland
--> Processing Conflict: kde-l10n-4.6.1-1.fc14.1.noarch conflicts kde-l10n-kdepim > 4.5.90
--> Processing Conflict: kde-l10n-4.6.1-1.fc14.1.noarch conflicts kde-l10n-kdepim-runtime > 4.5.90
--> Finished Dependency Resolution
Error: kde-l10n conflicts with kdepim-runtime
Error: kde-l10n conflicts with kdepim
You could try using --skip-broken to work around the problem
You could try running: rpm -Va --nofiles --nodigest
I have been getting this problem updating recently, a --skip-broken gets me round it no problems
I assume its because my kdepim version is greater than 4.5.90, I use 4.5.94
is this a dependency thing (possible error) or will there be another kde-l10n that is compatible with
ps. I use the kde-testing/unstable repos.
could anybody of the fedora-SIG take a look at this because upstream
seems not to be interested - maybe a simple widget for a shellcommand
would be better which is called every x seconds (configuraebale) to get
a "tail -n 5 /path/ 2> /dev/null" there....
I had this problem back on Fedora 13 and I found out how to fix it. BUT, I did a
fresh install of Fedora 14, and I discovered that I never documented the way
that I fixed it.
If this is the wrong list for this, please let me know...
I am running KDE SC 4.6.1 (from the kde-testing repo) and I really do not like
the monochromatic icons that now seem to be the default in the System Tray. My
question is, Where do I get the color versions of the new monochromatic icons,
and where exactly do I copy them to?
Also, is there a location in my home directory that I could copy them to so that
they would not be wiped out every time the offending (my opinion) icons are
updated? I think that would be something like
Your help is greatly appreciated.
Steven P. Ulrick
I have updated my F14 to 4.6.1 from kde-testing and now i got an error
that akonadi had an error at last run if I start kmail the first time
after login. In the error logfiles I got the message
D-Bus session bus went down - quitting
I had this error once with 4.4 KDE. Is this a known problem with 4.6.1
(regression)? How can I go around this error?
Is it possible for KDE to use different config directory other than ~/.kde ?
Let's say I have different computers or test machines that not necessary runs
the same KDE version (e.g different Fedora releases), or just want different KDE
setup on those machines. I want all the machine to mount the same home
directory from NFS server so that I have access to all my files, but I want the
different machines to use different KDE config directory: e.g. ~/.kde_machine1,
~/.kde_machine2, etc. If this is possible, how do I do it ?
Since a couple of updates and weeks ago (F14, don't remember exactly when,
sorry) the KDE wireless applet stopped doing its work.
When I click on it and choose to connect to my wireless router, it asks for a
passphrase (WPA), and then hangs in "waiting for authorization" state forever,
After some troubleshooting, I figured I can use the nm-applet from Gnome, after
I disable a couple of services in the KDE service manager (namely, the
"NetworkManager User Setting Service" and "Network Status"). If I don't
disable them, nm-applet fails to run, saying another instance is already
running (which is wrong, btw). I suspect one of these services are simulating
the presence of nm-applet to prevent it from running concurrently.
Anyway, when the services are disabled, nm-applet is running and connects to
my router without any problems.
The issue is that this is a workaround, and that default KDE configuration used
to work flawlessly until some point.
I also tried to connect to other wireless networks (open, wep, wpa...) to
check if it's something related to my router, but the symptoms are the same
Is this a known issue? Am I the only one seeing it? How can I troubleshoot it?
I was monitoring /var/log/messages while trying to connect, but nothing there
points to the problem, AFAICT.
Btw, when nm-applet is running, the KDE applet in the taskbar correctly
reports the state of the wireless interface, and appears to coexist nicely
From what I understand, the NetworkManager service is running correctly, nm-
applet is also running correctly, but something within KDE went to lunch...