yesterday I had to shut down my laptop in a hurry. This morning, I powered up and saw to my consternation that several Firefox Tabs did not load (server unavailable). I gave it several tries, but
it did not work. Hiding Firefox, I saw that KWallet was waiting for a password. After that, I entered the password for SU, and Firefox worked. Then it struck me:
I did not login - repeat: I DID NOT LOGIN - , no username, no password. And the password for KWallet is not the same as my user PW.
If I am correct, openSuSE 11.4 (64 bits) may have security problem. Could somebody please check if they can duplicate the problem? Do:
Start Firefox 4.0 Beta 12
Start some application that needs a password stored in KWallet, do not enter the PW
Place the Firefox window over the KWallet wind for the PW
Do a shutdown via the Icon
Wait 30 seconds after power down
Turn the power on
If you now enter the session without specifying any user name or PW, then this message has some merit; if not, I will try to duplicate the issue tomorrow.
this is interesting! However, I am pretty sure that I had the red Icon in the middle of the screen when I did the shutdown (I was in a hurry, not in a panic). I will try duplicating the exercise.
I see you calmed a bit down after your first surprise
The only thing I try is to ananlyze your problem. As I asume you do not have automatic logon (else you most probably wouldn’t have started this thread) and as what you describe does not happen in all the other systems (and as I do not believe in magic, at least not in computers), we must find out where your description must be wrong. One place where descriptions go wrong is that the OP makes an assumption that is simply not true.
Now I myself have no laptop and I do never hibernate my desktop, but as what you describe can not be true for a shutdown, I guessed for hibernation. Again I have no experience, but IIRC you can hibernate laptops by simlpy closing the lid. So it “might be” that in your hurry, you did not click really on the red cross and closed the lid without seeing that you missed it, let alone veryfying that the shutdown completed including the switch off.
I have just found something that might be interesting, if for you an unlocked session after waking up from hibernation is not such a good thing. There is a utility called KShutdown that offers “Lock screen before Hibernate” and if I am not mistaken, the session would be locked after you woke your machine up from hibernation (I haven’t tested though).
KShutdown is in the KDE:Extra repos, you would just have to pick the one matching your install: KDE repositories - openSUSE
And just one more thing. You can actually see from the logs, whether you hibernated or not. There is a handy application for the KDE desktop called KSytemlog for example, which you can use to look at System or Kernel logs to find out what precisely happened when you supposedly shut-down and booted the machine again.
since s/he has been experimenting trying to duplicate the problem for
four hours now, i suspect the next time we hear from her/him, s/he
will not be a happy camper…having shot her-/him-self in the foot…
a couple of times…
–
DenverD
CAVEAT: http://is.gd/bpoMD
[NNTP posted w/openSUSE 11.3, KDE4.5.5, Thunderbird3.1.8, nVidia
173.14.28 3D, Athlon 64 3000+]
“It is far easier to read, understand and follow the instructions than
to undo the problems caused by not.” DD 23 Jan 11
if your e-mail above is mirroring your attitude, I must say that you are pretty ignorant. In any case you need to improve your style.
You assume that I have been working on the problem for four hours. This is wrong. I have not been working on the problem since my last post.
Could you please stop your nonsense.
I logged in 5 minutes ago, and:
THE PROBLEM IS REPRODUCEABLE !!!
I suppose that you are too ignorant to learn more.
May I just ask if you not perchance have automatic log-in enabled? If so, automatic log-in is not a bug, it is a feature, and it is the default when you install openSUSE. It can be easily turned off though. If you combine automatic log-in with KDE’s “Restore previous session” (IIRC also default) you can get quite close to what you have observed.
since s/he has been experimenting trying to duplicate the problem for
four hours now, i suspect the next time we hear from her/him, s/he
will not be a happy camper…having shot her-/him-self in the foot…
a couple of times…
She/he is quite right about a couple of times:
I have now done a regular shutdown 3 times, and each time I have to enter my Kdewallet password to log in. Is there anybody out there who would want to learn more about what I am experiencing, or is a potential security problem of no interest to all of the moderators?
On 03/18/2011 07:36 PM, jc anker wrote:
> I suppose that you are too ignorant to learn more.
far too ignorant to help you in anyway…
–
DenverD
CAVEAT: http://is.gd/bpoMD
[NNTP posted w/openSUSE 11.3, KDE4.5.5, Thunderbird3.1.8, nVidia
173.14.28 3D, Athlon 64 3000+]
“It is far easier to read, understand and follow the instructions than
to undo the problems caused by not.” DD 23 Jan 11
On 03/18/2011 02:36 PM, jc anker wrote:
>
> DenverD wrote:
>
>> since s/he has been experimenting trying to duplicate the problem for
>> four hours now, i suspect the next time we hear from her/him, s/he
>> will not be a happy camper…having shot her-/him-self in the
>> foot…
>>
>> a couple of times…
>
> She/he is quite right about a couple of times:
> I have now done a regular shutdown 3 times, and each time I have to
> enter my Kdewallet password to log in. Is there anybody out there who
> would want to learn more about what I am experiencing, or is a potential
> security problem of no interest to all of the moderators?
Are you using encrypted wireless? If so, the norm is to store the secret in the
wallet andf for the wallet to request the password on startup.
@DenverD: That is unreasonable harsh. Everybody here lives at some part of the globe and has his/her own time of going for work or sleep. We all try to accomodate for that. E.g. I was away for many more hourse attending the Dutch openSUSE 11.4 Release Party first, traveling there and back home and going for a nice sleep, I hope you don’t mind.
@jc_anker: Please do not get irritated too soon. When a post is not to your liking, you can ignore it. As long as you are interested in having your problem solved and as long as you think there is still some usefull discussion with some people here, you can just go on with providing more information that may give us some clues.
You saying it is reproducable, you must be able to give us a thourough description of all the steps you take and what the results are. No need any more to live on your memory. And allways keep in mind that it is a hassle to describe all what you see to people that may have different set-ups and can not look over your shoulder to confirm to themselves that they see what you describe.
Thanks for the confirmation, it was of cours only a suggestion we should clarify.
When automatic logon is switched on, why are you surprised by being atomaticaly loged in? I doubt that you can switch automatic login on and off with Kwallet (in fact I am pretty sure there is no connection, automatic logon is by definition working before you have a session and thus before KWallet can do anything for that particular user in that particular session).
As long as we are not very clear on what the problem is, we can not make an exact bug description, let alone file it at Bugzilla.
Then we rule out any suspension/hibernation.
Yes, using KDE, all you passwords/keys are stored there by default. Thus when you use Networkmanager (which I guess you do), connecting to a network is a task of the end-user, including providing of the key for the wireless, by which you can be helped by using Kwallet. And as connecting to your network is about the first thing that happens after login, it triggers Kwallet (in my system, not using Networkmanager, Kmail is the first to start for me and thus triggers Kwallet for the passwords of my mail provider).
Do I come rightly to the conclusion that everything is now found as a “normal” way of working (though maybe not the way of working you like most)?
