| Summary: | Can't log back in once When I lock the screen from KDE, I can't log back in! KDE relogin doesn't seem to recog"Lock Screen" problem in KDE | ||
|---|---|---|---|
| Product: | Ports & Packages | Reporter: | sucho2 <sucho2> |
| Component: | Individual Port(s) | Assignee: | freebsd-bugs (Nobody) <bugs> |
| Status: | Closed FIXED | ||
| Severity: | Affects Only Me | ||
| Priority: | Normal | ||
| Version: | Latest | ||
| Hardware: | Any | ||
| OS: | Any | ||
|
Description
sucho2
2000-12-04 04:50:01 UTC
> >Severity: critical noncritical > >Class: sw-bug ports in real world... > When I lock the screen from KDE, I can't log back in! It seems, KDE doesn't recognize my password. > The only way to log back in to KDE is to shut down the computer and turn in back on! > But then all my unsaved works are lost! KDE 1.X Problem exist. Incorrect auth/pam use? Try to use Ctrl-Shift-Backspace to shutdown X as a temporary solution or Ctrl-Shift-F? onto different virtual console and kill KDE lock process. Bye! Serg N. Voronkov Please, close this PR.
Serg N. Voronkov
Hint: Forget to read message from portinstaller
@${ECHO_MSG} "Due to the potential security hole represented by
the KDE"
@${ECHO_MSG} "screensavers, you will have to set them setuid
yourself."
@${ECHO_MSG} "In order to do this, run:"
@${ECHO_MSG} " # chmod 4755 ${PREFIX}/bin/*.kss"
State Changed From-To: open->feedback Does making the screen-savers setuid as per the documentation (pointed out by Sergey Voronkov) solve the originator's problem? State Changed From-To: feedback->closed Originator reports satisfaction with making the screen savers setuid, and also satisfaction with FreeBSD in general :) |