[Bug 855115] New: Shutdown not effectuated with multiusersystem and secure file settings (laptop with ultrabase dockingstation)
https://bugzilla.novell.com/show_bug.cgi?id=855115 https://bugzilla.novell.com/show_bug.cgi?id=855115#c0 Summary: Shutdown not effectuated with multiusersystem and secure file settings (laptop with ultrabase dockingstation) Classification: openSUSE Product: openSUSE 13.1 Version: Final Platform: x86-64 OS/Version: openSUSE 13.1 Status: NEW Severity: Normal Priority: P5 - None Component: Other AssignedTo: bnc-team-screening@forge.provo.novell.com ReportedBy: stakanov@freenet.de QAContact: qa-bugs@suse.de Found By: --- Blocker: --- User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:25.0) Gecko/20100101 Firefox/25.0 I haven't tried this yet for repeatability without dockingstation but with the Lenovo X201 and ultrabase dockingstation this is repeatable and stable. Run a sistem with Lenovo X201, ultrabase and two monitors attached (hdmi and vga). Use "secure" file permissions. Open several terminal sessions for different users. Now shutdown the system from a terminal that is not the first one that you did open. The system asks for root password, you give it, it will apparently shutdown. But it isn't. The screen remains with a little dash blinking high right (like the system would have crashed. But it didn't crash). The monitor hdmi after a while will begin to "flush" in regular time frames and give a bob sound over the speakers. This stays a whole night, by this also making the material suffer. In one night the monitor will switch on and of a few hundred times. If you switch the system off with the power button (will ask correctly for root password) it will shutdown normally. If you switch to the first videoterminal you did open, (with the combination ctrl + alt + F7 which is set normally as the first terminal to open) then the system will proceed correctly to normal shutdown without further intervention. Reproducible: Always Steps to Reproduce: 1.open several video terminals of several users in a system with secure file permissions 2.close the system (shutdown) with root password from any but the original VT 3. system hangs on shutdown Actual Results: system does not shutdown, monitor switches on and off in an ultrabase Expected Results: well, it shut shutdown I guess. Bug 853116 - suse does not shutdown This could be a duplicate but as the original poster did not give any details I cannot now. I set this to normal. I will check if in such situation the encrypted LVM will stay open. In this case this would be also severe from a security point of view. But I have the hope that it isn't the case.Currently I am just afraid for the material when it happens, because you just may not notice it. Imagine you go into a weekend and the thingy is flushing on and off you monitor up to planned obsolescence. -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.
https://bugzilla.novell.com/show_bug.cgi?id=855115 https://bugzilla.novell.com/show_bug.cgi?id=855115#c zhang jiajun <jzhang@suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |jzhang@suse.com AssignedTo|bnc-team-screening@forge.pr |systemd-maintainers@suse.de |ovo.novell.com | -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.
https://bugzilla.novell.com/show_bug.cgi?id=855115 https://bugzilla.novell.com/show_bug.cgi?id=855115#c1 --- Comment #1 from Stakanov Schufter <stakanov@freenet.de> 2013-12-13 10:39:39 UTC --- Some more info (I don't know how useful this might be, however, worth a try). It is possible to consult such a frozen system with Alt+Ctrl+F10 and see the systemlog. I did write down the last lines, maybe that gives some hint. Kdm: :0[2150] Abnormal termination of greater for display:0, code 1, signal 0 Kdm: :0[2150] Abnormal greeter termination, code 1, signal 0 bluetoothd [1700] failed to remove UUID: Invalid Parameters (0x0d) bluetoothd [1700]: message repeated 2 times: [Failed to remove UUID:Invalid Parameters (0x0d)] When then shutting down through the trick of the right VT or by pressing the power off button it is fairly possible to read something like: started cryptographic setup, read ahead data this repeats several times then the system seems to go down. Bear with me, it is fast and it is therefore not easy to get hold of the text here. The system is setup with encrypted root LVM and /boot partition. Hope that gives you at least some idea. Greets. -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.
participants (1)
-
bugzilla_noreply@novell.com