Am 16.09.2015 um 18:12 schrieb Wes Hardaker:
> Reindl Harald <h.reindl(a)thelounge.net> writes:
>> * start a VM
>> * move the mouse pointer into the window
>> "Do you really want to activate 'slow keys' and 'mouse keys'..... if
>> you do not need them, you can select 'Deativate all AccessX features
>> and gestures' - independent what you chose, move the mouse and the
>> same dialog appears again and again - seriously?
> Yikes. Please to post if you find a fix for that
a workaround is just disable 3D graphics for the VM's and start them
headless with the VNC option and avoid the normal GUI but after so many
years using VMware under KDE (as well as ESXi for production servers) it
leaves a bad taste in my mouth to say it polite
and the fact that copy files over sftp freezes half of the GUI and i
recently smoked two cigarettes until something starts to working again
on a i7 SandyBrdige machine with 16 GB ram while switch with CTRL+ALT+F2
to a console and verify that all the files are already there while
plasma is running in circles with high CPU load confirms that until now
KDE5 is just unusable
I've been seeing this problem several times a day. I can't reproduce it in any reliable way and I have no idea how I can go about collecting the needed info... Anyway, here is what happens.
My most recent experience with "freeze" is not a solid one. The screen is frozen but I can still move the mouse around. Also, if there is a video playing it will freeze but the audio will continue on. I can get out of it by logging in from a terminal and doing a "killall -u myusername" which gets me back to the login screen.
I think "kwin" is the most likely suspect and have upgraded to kwin-5.4.0-4 from updates testing as the changelog included this nugget which gave me hope....
* Tue Aug 25 2015 Daniel Vrátil <dvratil(a)redhat.com> - 5.4.0-2
- add upstream patch to fix crash
- make sure kwayland-integration is installed for kwin-wayland
But no... Still have issues. Any suggestion on what to look for to see if the culprit can be identified?
It seems most people that say they are "done talking about it" never really are until given the last word.
One cause is known, see https://bugzilla.redhat.com/show_bug.cgi?id=1264486
From: kde-bounces(a)lists.fedoraproject.org <kde-bounces(a)lists.fedoraproject.org> on behalf of Glenn Holmer <shadowm(a)lyonlabs.org>
Sent: Sunday, September 20, 2015 6:36 PM
To: KDE on Fedora discussion
Subject: Re: A near freeze of plasma
On 09/18/2015 06:49 PM, Ed Greshko wrote:
> On 09/19/15 07:19, Ed Greshko wrote: The best way to get a "near
> freeze" is to tell everyone that you've not had one in at least a
> week. Seriously, less than one hour after writing this I got a "near
> freeze" and was able to confirm that "killall -9 drkonqi" got me
> going again.
I've reached my limit with the Plasma 5 freezes. Speaking to users
who've tried alpha builds: do you think there's any hope of this
situation improving in Fedora 23? I see we're scheduled for a beta this
week. If the cause of the freezes hasn't been found yet, I'll start
making other plans for this machine.
Glenn Holmer (Linux registered user #16682)
"After the vintage season came the aftermath -- and Cenbe."
kde mailing list
New to KDE4? - get help from http://userbase.kde.org
Do you happen to use transmission or owncloud? If so, it would appear their systray icons are one source of leaks.
From: kde-bounces(a)lists.fedoraproject.org <kde-bounces(a)lists.fedoraproject.org> on behalf of Colin J Thomson <colin.thomson(a)g6avk.co.uk>
Sent: Sunday, September 20, 2015 6:58 PM
To: KDE on Fedora discussion
Subject: Re: Re: A near freeze of plasma
My only real gripe with P5 now is the amount of RAM it eats over the course of
a day.. up to almost 5 gig now and hitting swap! (8 gig on this box) uptime ~
17 hours. So kquitapp plasmashell resets it nicely.
So I have to use LXQt Desktop env because the freezing returned with the
latest update of Fedora 22:
See the txt file for the packages which were updated. Looks like the bug
This time manually setting the xorg.conf doesn't fix the problem. I even
turned off all compositing as just xrender and it still locks up my xorg
session. I have no choice than ctrl-alt-backspace ... at least that
The information contained in this transmission contains privileged and confidential information. It is intended only for the use of the person named above. If you are not the intended recipient, you are hereby notified that any review, dissemination, distribution or duplication of this communication is strictly prohibited. If you are not the intended recipient, please contact the sender by reply email and destroy all copies of the original message.
CAUTION: Intended recipients should NOT use email communication for emergent or urgent health care matters.
I just installed a fresh Fedora 22 with KDE. For some reason, the
Clock widget and Calendar does not display events from Korganizer. In
my Korganizer I have both events from Google Calendar and default
calendar. The "Digital Clock Settings" or "Calendar Settings" don't
even have any checkbox for displaying events, like in earlier version.
I am sorry if this was asked before; I've search everywhere but
couldn't come up with anything. Is there something I missed ?
I wonder if anyone else experiences this?
Sometimes when I move the cursor with the pointer on my ThinkPad T510
I am apparently logged out, and have to re-enter my password.
This doesn't really worry me, as the re-entry after giving my password
takes only a second, so it is not a proper logging out.
I should say I'm running Fedora 22 with KDE-4.14.11.
gayleard /at/ eircom.net
School of Mathematics, Trinity College, Dublin
I fedup'ed my F21 (with plasma 5 from copr) to F22 which mostly went
well. For a few packages, F21 was actually ahead of F22 (sigh) but dnf
downgrade took care of that. There is one remaining piece in "dnf list
Erasing that takes quite a bit with it (see below).
Which package should obsolete it, and/or how do I get into a proper "F22
only plasma 5 state"?
(There are many other .fc21 packages, which is confusing but normal in
fedora land; that plasma5 package should go away, though.)