Re: kde Digest, Vol 91, Issue 1
by William W. Austin
On 2016-06-05 16:10:19, kde-request(a)lists.fedoraproject.org wrote:
======quoted message from Florian Sievert <caleb(a)phobeus.de>, subject "Re: Plasma won't wake up after sleep. Black screen with cursor."======
> Hi,
> > At least twice this week when I woke up my system from sleep instead
> > of lock screen I am presented with black screen and cursor. There is
> > no way for me to get back to working system except go to tty and
> > restart sddm or reboot system. Htop doesn't seem to show any obvious
> > culprit. This is highly undesirable as I keep losing my unsaved
> work.
> I encouter this as well a few times recently, seems to be related to
> some of the latest updates. For some reason "plasmashell" seems to
> crash
> sometimes. This can be pretty painful if krunner is crashed as well
> (and
> feels like always...). So try press "ALT+F2" and run "kquitapp
> plasmashell & plasmashall" or try to get into a console and launch the
> command there. After a few seconds the desktop shall be there as
> normal,
> even tho these crashs are extremly nasty...
[SNIP]
Florian's description of "black scrren and cursor" sounds like text
mode, not an x-windows dispaly.
That being said, I don't get that problem, and I never put my system
to the sleep/hibernate state - but I get what sounds like something
simlar in principle at least once per day and often as many as 4-6
times in a day when I unlock the screen.
To me the worst part is when the screen is unlocked and this happens,
there is (of course) no panel, and all I can see is the black screen
with whatever windows were open when I locked the screen. Any windows
which were iconized when I locked it are impossible to get to.
ASIDE: +I don't know whether it's related or not, but frequently
(possibly always, although I don't always keep top running somewhere
to determine whether this is the case) before this happens I'll
notice a krunner process which is using extremely large of amounts
cpu (>100% for more than a few seconds). That causes me to wonder
whether something in krunner gets caught in a loop.
Sometimes I use the same sequence as Florian ("kquitapp plasmashell &
plasmashall") but it doesn't always work.
FWIW I also get FREQUENT error message boxes telling me that this
or that kde component has crashed. Sometimes I believe they have;
however, more often a search of /var/log and/or /var/account/pacct
does not record the crash and I suspect some other glitch in kde5 is
causing a false error message.
I've been using the KDE desktop on virtually every machine where I
have a login for longer than I can remember, and the many glitches in
kde5 make me long for the stability, usefulness, and configurability
of kde4.
- wwa
--
william w. austin airedad(a)att.net
"life is just another phase i'm going through. this time, anyway ..."
7 years, 10 months
PIM 16.04 F24
by Colin J Thomson
Hi,
I have been struggling to rebuild/install the required DEV packages F25
> F24
so I can rebuild the PIM F25 src.rpms for this F24 box. There are a lot
of split
packages and after a few weeks struggling I think its time to ask..
Is the PIM suite 16.04.x planned for F24 or is there a COPR for PIM
somewhere.
I ask as I really miss using Kmail with my other IMAP accounts and since
applications
15.12 there has been a huge number of fixes in PIM and for IMAP.
FWIW on this F24 Desktop box, Single monitor/Nouveau KF5/Plasma is
working
very very well, stable and no real issues here at all.
Colin
--
Roundcube open source webmail software
7 years, 10 months
Issue with Chrome and Unity Launcher Support (requires libunity)
by Gerald B. Cox
I noticed an issue running chrome-unstable where download status wasn't
being displayed:
https://bugs.chromium.org/p/chromium/issues/detail?id=604171
This also applied to chrome-beta.
It worked for chrome-stable and chromium.
I initially thought it had to do with the version of chrome - i.e. there
was some type of regression.
Now it appears that when the version of chrome-unstable moved into stable
the issue was resolved. The version in stable had the exact same number as
that which didn't work in unstable, which leads to to believe that instead
of there being an issue on the chrome side, instead this is an issue on the
kde side where something is coded in such a way that it is looking for a
"stable" designation for chrome in order to function.
That just seems a bit wacky to me, like why would anyone do that... but
that is how it appears.
I was wondering if anyone else has noticed this issue and is seeing the
same results? If so, I would consider this a kde bug rather than chrome.
Thanks!
7 years, 10 months
F24 karma requests (blocker/FE fixes)
by Adam Williamson
Hey folks!
Unfortunately we're still waiting on a fix for
https://bugzilla.redhat.com/show_bug.cgi?id=1320273 before we can build
a release candidate. While we're waiting, though, as well as doing the
missing validation tests on the current nominated nightly, it'd be
useful for folks to test and karma some FE / blocker updates:
https://admin.fedoraproject.org/updates/FEDORA-2016-b0494cdc04 (anaconda)
fixes several FEs. If you aren't set up to build your own installer
image, you can boot a live image and update the anaconda package before
running the live installer - that's a decent way to test most aspects.
https://admin.fedoraproject.org/updates/FEDORA-2016-714119426f (cloud-
utils) fixes a blocker bug in the cloud images. I think you need to be
able to build a Cloud image to be able to fully test the fix, which is
why I'm CCing cloud@ :)
https://admin.fedoraproject.org/updates/FEDORA-2016-a7c55ce2fa (firefox)
fixes an FE but also introduces quite a lot more change, so it'd be
good to have it carefully tested; if everyone who uses firefox could
update to it and check all their usual stuff works, that'd be great.
https://admin.fedoraproject.org/updates/FEDORA-2016-7e822d9239 (qt5)
fixes a KDE crasher; it'd be great if KDE folks could update to it,
make sure their stuff all still works normally, and +1 it if so.
There's also a flock of FTBFS / dependency rebuild fixes:
https://admin.fedoraproject.org/updates/FEDORA-2016-a88e158b2c
https://admin.fedoraproject.org/updates/FEDORA-2016-6166f85051
https://admin.fedoraproject.org/updates/FEDORA-2016-a7af5e90d1
https://admin.fedoraproject.org/updates/FEDORA-2016-54554f20d4
for those all that's really needed is to verify that they have no
dependency issues, and ideally that they start up and do...something
(or if they're libraries, that something based on them starts up and
works).
Thanks a lot folks!
--
Adam Williamson
Fedora QA Community Monkey
IRC: adamw | Twitter: AdamW_Fedora | XMPP: adamw AT happyassassin . net
http://www.happyassassin.net
7 years, 10 months
Plasma won't wake up after sleep. Black screen with cursor.
by Sudhir Khanger
Hi,
At least twice this week when I woke up my system from sleep instead of lock screen I am presented with black screen and cursor. There is no way for me to get back to working system except go to tty and restart sddm or reboot system. Htop doesn't seem to show any obvious culprit. This is highly undesirable as I keep losing my unsaved work.
Regards,
Sudhir Khanger,
sudhirkhanger.com.
7 years, 10 months