https://bugs.kde.org/show_bug.cgi?id=340982
--- Comment #272 from Robin Laing ---
I like the reference to "Windows" in comment #271. I don't normally have
access to a Windows machine but in my experience, changing the date/time format
in Windows is easy. That is all we are askin
https://bugs.kde.org/show_bug.cgi?id=316348
--- Comment #59 from Robin Laing ---
This is from journal logs with one process kscreenlocker_greet at 99%
Apr 06 22:37:36 darkstar.tardis.localdomain kscreenlocker_greet[63511]: Qt:
Session management error: networkIdsList argument is NULL
Apr 06 22
https://bugs.kde.org/show_bug.cgi?id=316348
--- Comment #58 from Robin Laing ---
I am running into the situation where kscreenlocker goes to 99% on a regular
basis. I did updates on the weekend and have not seen it since. It seemed to
happen more often the longer I was running between reboots
https://bugs.kde.org/show_bug.cgi?id=366421
Robin Laing changed:
What|Removed |Added
CC||me...@telusplanet.net
--- Comment #5 from Robin
https://bugs.kde.org/show_bug.cgi?id=316348
--- Comment #47 from Robin Laing ---
(In reply to Shmerl from comment #45)
> And just for the reference, it only happens when screen locker is using
> image slideshow. With static image CPU usage is minimal.
I wasn't using a slide show
https://bugs.kde.org/show_bug.cgi?id=316348
--- Comment #46 from Robin Laing ---
(In reply to Shmerl from comment #44)
> (In reply to Robin Laing from comment #43)
> > Okay, I will create a new bug and keep trying to get any more information.
> >
> > Just wanted to confirm
https://bugs.kde.org/show_bug.cgi?id=316348
--- Comment #43 from Robin Laing ---
Okay, I will create a new bug and keep trying to get any more information.
Just wanted to confirm before opening a new bug report.
--
You are receiving this mail because:
You are watching all bug changes.
https://bugs.kde.org/show_bug.cgi?id=316348
Robin Laing changed:
What|Removed |Added
CC||me...@telusplanet.net
--- Comment #40 from Robin
https://bugs.kde.org/show_bug.cgi?id=340982
--- Comment #114 from Robin Laing ---
It would be nice if the system recognized the locale to start with. One
configuration. BUT, I do agree, on a multiuser system, there has to be
recognition of personal choice.
First fix should be to get all the
https://bugs.kde.org/show_bug.cgi?id=340982
--- Comment #74 from Robin Laing ---
Maybe it would save allot of headaches if there was an easy way to change
locale system wide. There are ways to play around but it would be nice if
there was an ISO 8601 based locale instead of searching and using
https://bugs.kde.org/show_bug.cgi?id=340982
--- Comment #63 from Robin Laing ---
Since this has been pointed out to be a KDE issue, I decided to look at the QT
bug reports. I only found one that I think may be related.
There is an open bug report for QT to extend the date formats to support
https://bugs.kde.org/show_bug.cgi?id=353428
--- Comment #36 from Robin Laing ---
Just an update.
After major problems with KDE after the latest KDE updates, I decided to wipe
out all my old configuration files and start my account from scratch. Since
doing this, I have not had a single crash
https://bugs.kde.org/show_bug.cgi?id=353428
--- Comment #35 from Robin Laing ---
Noticed this before but didn't report it.
If I type in
ps aux |grep kwin
response is
robin14161 0.4 0.5 3471124 170420 ? Sl Dec14 16:41
/usr/bin/kwin_x11 --crashes 1
This is after a f
https://bugs.kde.org/show_bug.cgi?id=353428
--- Comment #34 from Robin Laing ---
No, it was the "Strg-Alt-Fx" you wrote that I hope was a typo.
Your freezing is similar to a situation that I run into every once in a while
that is different. My desktop will totally freeze but
https://bugs.kde.org/show_bug.cgi?id=353428
--- Comment #27 from Robin Laing ---
Bzi, comment 25
I use a USB keyboard and can Ctrl+Alt+Fx to the terminal. I usually use F5 out
of years of habit. I hope your comment is a typo. Try to Ctrl+Alt+Fx before
the lockup and see if that works.
I
https://bugs.kde.org/show_bug.cgi?id=353428
--- Comment #26 from Robin Laing ---
For part of the discussion.
I wonder if others that are having this issue have upgraded and those that
don't have a problem are using a clean install.
I have a couple of test accounts on the same machine but
16 matches
Mail list logo
