[opensuse-factory] openSUSE Tumbleweed 20190214 - Plasma screenlock does not unlock
Linux 4.20.7-1-default [openSUSE Tumbleweed 20190214] HP ZBook 15G3 openSUSE-release-20190214-44.1.x86_64 plasma5-desktop-5.15.0-1.1.x86_64 plasma5-workspace-5.15.0-1.1.x86_64 libkscreen2-plugin-5.15.0-1.1.x86_64 When my desktop goes into screenlock, nothing will unlock it. There is no unlock dialog showing when I move the mouse or hit a key # loginctl unlock-session xxx still works. (doing so from a Alt-Ctrl-F3 login) # zypper ve is clean (except for spotify and opera-12, but I know that) -- H.Merijn Brand http://tux.nl Perl Monger http://amsterdam.pm.org/ using perl5.00307 .. 5.29 porting perl5 on HP-UX, AIX, and openSUSE http://mirrors.develooper.com/hpux/ http://www.test-smoke.org/ http://qa.perl.org http://www.goldmark.org/jeff/stupid-disclaimers/
On samedi, 16 février 2019 17.07:35 h CET H.Merijn Brand wrote:
Linux 4.20.7-1-default [openSUSE Tumbleweed 20190214] HP ZBook 15G3
openSUSE-release-20190214-44.1.x86_64 plasma5-desktop-5.15.0-1.1.x86_64 plasma5-workspace-5.15.0-1.1.x86_64 libkscreen2-plugin-5.15.0-1.1.x86_64
When my desktop goes into screenlock, nothing will unlock it. There is no unlock dialog showing when I move the mouse or hit a key
# loginctl unlock-session xxx
still works. (doing so from a Alt-Ctrl-F3 login)
# zypper ve
is clean (except for spotify and opera-12, but I know that)
Work without any glitches here : same release, same package. Check dmesg for any gpu / kernel hicup ? here blob nvidia, and it works even with 3 screens ;-) -- Bruno Friedmann Ioda-Net Sàrl www.ioda-net.ch Bareos Partner, openSUSE Member, fsfe supporter GPG KEY : D5C9B751C4653227 irc: tigerfoot -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org
Did you reboot already since doing the update? Strange things can happen in the running session if the whole system (or certain parts at least) are replaced underneath by new major versions... Kind Regards, Wolfgang -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org
Am Samstag, 16. Februar 2019, 18:26:35 CET schrieb Wolfgang Bauer:
Strange things can happen in the running session if the whole system (or certain parts at least) are replaced underneath by new major versions...
I have some trouble with suspend, I guess since the 4.20 kernel series: Normally it goes to suspend when I close the lid, but sometimes not - and I could not fint the reason for it in the logs. Cheers Axel -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org
Am Samstag, 16. Februar 2019, 18:54:56 schrieb Axel Braun:
Am Samstag, 16. Februar 2019, 18:26:35 CET schrieb Wolfgang Bauer:
Strange things can happen in the running session if the whole system (or certain parts at least) are replaced underneath by new major versions...
I have some trouble with suspend, I guess since the 4.20 kernel series: Normally it goes to suspend when I close the lid, but sometimes not - and I could not fint the reason for it in the logs.
That's hardly related to the problem mentioned here though, or to KDE's screenlocker for that matter. If suspend/resume doesn't work reliably for you, it's probably a kernel problem IMHO. Especially as you mention it seems to happen "since the 4.20 kernel series"... ;-) Kind Regards, Wolfgang -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org
On Sat, 16 Feb 2019 18:26:35 +0100, Wolfgang Bauer <wbauer@tmo.at> wrote:
Did you reboot already since doing the update?
Yes, of course. I got a new kernel, so I rebooted
Strange things can happen in the running session if the whole system (or certain parts at least) are replaced underneath by new major versions...
FWIW I have no (additional) problems with hibernate/resume. That works fine, but after resume, the same black screen stays without the popup of the unlock dialog. Alt-Ctrl-F2 and loginctl unlock-session to the rescue But I found the cause. It is completely my own "fault" I have (good) reasons to set my locale to en_US.utf-8, but I really hate the US date system. 123 is onehundredandtwentythree, not twohundredandthirteen, so 1/2/2019 is NOT the 2nd of January, but the first of February. With that in mind, I alter Clock.qml after system updates replace it, to something that doesn't annoy me all the time. As the format of this file changed, my automatic "repair" caused it to contain illegal content and hence failed to show the dialog(s) Mea culpa. Sorry for the noise! # zypper in -f plasma5-theme-openSUSE fixed it to working again. Applying my changes by hand made me happy again: --8<--- diff /usr/share/plasma/look-and-feel/org.openSUSE.desktop/contents/components-real/Clock.qml /usr/share/plasma/look-and-feel/org.openSUSE.desktop/contents/components-real/Clock.qml.new 38c38 < text: Qt.formatTime(timeSource.data["Local"]["DateTime"]) ---
text: Qt.formatTime(timeSource.data["Local"]["DateTime"], "hh:mm")
45c45 < text: Qt.formatDate(timeSource.data["Local"]["DateTime"], Qt.DefaultLocaleLongDate) ---
text: Qt.formatDate(timeSource.data["Local"]["DateTime"], "ddd dd MMM yyyy")
48c48 < font.pointSize: 24 ---
font.pointSize: 14
59c59 < layer.enabled: !softwareRendering ---
layer.enabled: undefined
-->8--- Now I need to find where the logname is shown when I have to enter my password, as layer.enabled makes that ugly and unreadable. None of your concerns though :)
Wolfgang
-- H.Merijn Brand http://tux.nl Perl Monger http://amsterdam.pm.org/ using perl5.00307 .. 5.29 porting perl5 on HP-UX, AIX, and openSUSE http://mirrors.develooper.com/hpux/ http://www.test-smoke.org/ http://qa.perl.org http://www.goldmark.org/jeff/stupid-disclaimers/
Am 17.02.19 um 09:31 schrieb H.Merijn Brand:
On Sat, 16 Feb 2019 18:26:35 +0100, Wolfgang Bauer <wbauer@tmo.at> wrote:
Did you reboot already since doing the update?
Yes, of course. I got a new kernel, so I rebooted
Strange things can happen in the running session if the whole system (or certain parts at least) are replaced underneath by new major versions...
FWIW I have no (additional) problems with hibernate/resume. That works fine, but after resume, the same black screen stays without the popup of the unlock dialog. Alt-Ctrl-F2 and loginctl unlock-session to the rescue
But I found the cause. It is completely my own "fault"
I have (good) reasons to set my locale to en_US.utf-8, but I really hate the US date system. 123 is onehundredandtwentythree, not twohundredandthirteen, so 1/2/2019 is NOT the 2nd of January, but the first of February. With that in mind, I alter Clock.qml after system updates replace it, to something that doesn't annoy me all the time.
Maybe looking up on LC_TIME in locale(7) would be helpful ;-) -- Stefan Seyfried "For a successful technology, reality must take precedence over public relations, for nature cannot be fooled." -- Richard Feynman -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org
On Sun, 17 Feb 2019 09:39:46 +0100, Stefan Seyfried <stefan.seyfried@googlemail.com> wrote:
Am 17.02.19 um 09:31 schrieb H.Merijn Brand:
On Sat, 16 Feb 2019 18:26:35 +0100, Wolfgang Bauer <wbauer@tmo.at> wrote:
Did you reboot already since doing the update?
Yes, of course. I got a new kernel, so I rebooted
Strange things can happen in the running session if the whole system (or certain parts at least) are replaced underneath by new major versions...
FWIW I have no (additional) problems with hibernate/resume. That works fine, but after resume, the same black screen stays without the popup of the unlock dialog. Alt-Ctrl-F2 and loginctl unlock-session to the rescue
But I found the cause. It is completely my own "fault"
I have (good) reasons to set my locale to en_US.utf-8, but I really hate the US date system. 123 is onehundredandtwentythree, not twohundredandthirteen, so 1/2/2019 is NOT the 2nd of January, but the first of February. With that in mind, I alter Clock.qml after system updates replace it, to something that doesn't annoy me all the time.
Maybe looking up on LC_TIME in locale(7) would be helpful ;-)
Which is not taken into account in that screen, for whatever reason. If that is a bug, I don't have the energy to make a ticket, as there as other places that completely ignore LC_TIME (like LibreOffice). I'll just "fix" them as they come. $ locale -ck LC_TIME LC_TIME abday="Sun;Mon;Tue;Wed;Thu;Fri;Sat" day="Sunday;Monday;Tuesday;Wednesday;Thursday;Friday;Saturday" abmon="Jan;Feb;Mar;Apr;May;Jun;Jul;Aug;Sep;Oct;Nov;Dec" mon="January;February;March;April;May;June;July;August;September;October;November;December" am_pm="AM;PM" d_t_fmt="%a %d %b %Y %R %Z" d_fmt="%d-%m-%Y" t_fmt="%R" t_fmt_ampm="%H:%M:%S" era= era_year="" era_d_fmt="" alt_digits= era_d_t_fmt="" era_t_fmt="" time-era-num-entries=0 time-era-entries="S" week-ndays=7 week-1stday=19971130 week-1stweek=1 first_weekday=1 first_workday=2 cal_direction=1 timezone="" date_fmt="%a %d %b %Y %R %Z" time-codeset="UTF-8" alt_mon="January;February;March;April;May;June;July;August;September;October;November;December" ab_alt_mon="Jan;Feb;Mar;Apr;May;Jun;Jul;Aug;Sep;Oct;Nov;Dec" -- H.Merijn Brand http://tux.nl Perl Monger http://amsterdam.pm.org/ using perl5.00307 .. 5.29 porting perl5 on HP-UX, AIX, and openSUSE http://mirrors.develooper.com/hpux/ http://www.test-smoke.org/ http://qa.perl.org http://www.goldmark.org/jeff/stupid-disclaimers/
On 2019年2月17日 at 9:31:49, H.Merijn Brand (h.m.brand@xs4all.nl(mailto:h.m.brand@xs4all.nl)) wrote:
But I found the cause. It is completely my own "fault"
I have (good) reasons to set my locale to en_US.utf-8, but I really hate the US date system. 123 is onehundredandtwentythree, not twohundredandthirteen, so 1/2/2019 is NOT the 2nd of January, but the first of February. With that in mind, I alter Clock.qml after system updates replace it, to something that doesn't annoy me all the time.
As the format of this file changed, my automatic "repair" caused it to contain illegal content and hence failed to show the dialog(s)
Instead of hacking the Clock plasmoid, you can use the ‘detailed’ locale settings in the Formats System Settings module. Change Region to ‘No Change’ (That list changes LANG for me), tick the box and set Time to whatever you want! Regards Radosław Wyrzykowski
On Sun, 17 Feb 2019 10:33:53 +0000, Radosław Wyrzykowski <kapibada@hotmail.com> wrote:
On 2019年2月17日 at 9:31:49, H.Merijn Brand (h.m.brand@xs4all.nl(mailto:h.m.brand@xs4all.nl)) wrote:
But I found the cause. It is completely my own "fault"
I have (good) reasons to set my locale to en_US.utf-8, but I really hate the US date system. 123 is onehundredandtwentythree, not twohundredandthirteen, so 1/2/2019 is NOT the 2nd of January, but the first of February. With that in mind, I alter Clock.qml after system updates replace it, to something that doesn't annoy me all the time. As the format of this file changed, my automatic "repair" caused it to contain illegal content and hence failed to show the dialog(s)
Instead of hacking the Clock plasmoid, you can use the ‘detailed’ locale settings in the Formats System Settings module. Change Region to ‘No Change’ (That list changes LANG for me), tick the box and set Time to whatever you want!
I don't think that works, as I (also) change my locale settings for the same reasons mentioned above: $ echo $LANG en_US.UTF-8 $ locale -ck LC_TIME | grep fmt= d_t_fmt="%a %d %b %Y %R %Z" d_fmt="%d-%m-%Y" t_fmt="%R" era_d_fmt="" era_d_t_fmt="" era_t_fmt="" date_fmt="%a %d %b %Y %R %Z" I hate Windows, but this is an area where Windows clearly wins. You can choose your locale and in the dialog change *every* aspect of the default settings and these will be respected. (I once chose a half-width space for triad-sep in numeric format, just to see how Windows would cope, and it worked like a charm. This is not possible in Formats System Settings, where the summary shows my preferences as crafted into the modified en_US.UTF-8 is represented exactly to my wishes Numbers: 1000.01 Time: Sunday, 17 february 2019 12:14:48 CET (long format) 17 Feb 2019 12:14:48 (short format) Currency: 24.00 Meas units: Metric FWIW LibreOffice has all locales builtin. Whatever custom locale you build or choose, it will never be perfect (at least not in *my* perception. Looks like the screen saver/lock screen does *NOT* respect the current local settings. Maybe *that* is a bug Summary of my changes: # Date 05/04/2007 => 04-05-2007 # Date Thu Apr 5 11:04:08 CEST 2007 => Thu 5 Apr 2007 11:04:08 # Time 5:00 PM => 17:00 For ADDRESS, MEASUREMENT, MONETARY, and PAPER I have copied nl_NL.utf8 settings (Metric, EUR € and A4)
Regards Radosław Wyrzykowski
-- H.Merijn Brand http://tux.nl Perl Monger http://amsterdam.pm.org/ using perl5.00307 .. 5.29 porting perl5 on HP-UX, AIX, and openSUSE http://mirrors.develooper.com/hpux/ http://www.test-smoke.org/ http://qa.perl.org http://www.goldmark.org/jeff/stupid-disclaimers/
participants (6)
-
Axel Braun -
Bruno Friedmann -
H.Merijn Brand -
Radosław Wyrzykowski -
Stefan Seyfried -
Wolfgang Bauer