public inbox for gentoo-user@lists.gentoo.org
 help / color / mirror / Atom feed
From: Alexander Kirillov <nevis2us@infoline.su>
To: gentoo-user@lists.gentoo.org
Subject: Re: [gentoo-user] [OT] Can't unlock session in KDE 3.4
Date: Mon, 18 Jul 2005 00:06:18 +0400	[thread overview]
Message-ID: <42DABA3A.4090003@infoline.su> (raw)
In-Reply-To: <42DAA0CF.9050302@gmail.com>

>> Kb layout switch in session unlock screen
>> doesn't work for me after upgrade to kde 3.4
>> When kde session locks on timeout
>> and the keyboard happens to be left in non-english layout
>> I can't switch it back to en and have to kill X
>> to get things back to normal.
>> This only happens when unlocking a session
>> and works well inside kde.
>> Any ideas?
> 
> Sounds like it could be a security constraint.  A locked screen
> shouldn't allow much more than password input.  You can't input the
> password with the non-en layout? Too bad :-(.

Hi Zac,
That doesn't sound optimistic. Does it?
The problem is it used to be working.
And the widget to switch kb layouts is still there.
But it doesn't work as expected.
And yep. The damn password is all ascii. Too bad.
I've just found this is not the only problem I'm having
with i18n in kde. For some reason I can't switch encodings in
kde editors either.
I should mention this happened after massive system cleanup.
Removed gnome and a bunch of multimedia soft I didn't need any more.
Followed by usual depcleans and revdep-rebuilds.
Didn't find any inconsistences in installed ebuilds though.
So the challenge still stands and all suggestions welcome.
Sasha

-- 
gentoo-user@gentoo.org mailing list



  reply	other threads:[~2005-07-17 20:10 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-07-17  9:21 [gentoo-user] [OT] Can't unlock session in KDE 3.4 Alexander Kirillov
2005-07-17 18:17 ` Zac Medico
2005-07-17 20:06   ` Alexander Kirillov [this message]
2005-07-17 20:20     ` Zac Medico
2005-07-17 20:40       ` Alexander Kirillov
2005-07-17 21:22         ` Zac Medico
2005-07-17 22:23           ` Alexander Kirillov

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=42DABA3A.4090003@infoline.su \
    --to=nevis2us@infoline.su \
    --cc=gentoo-user@lists.gentoo.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox