| Summary: | screensaver for kdm | ||
|---|---|---|---|
| Product: | [Unmaintained] kdm | Reporter: | Greg Coit <gregcoit> |
| Component: | general | Assignee: | kdm bugs tracker <kdm-bugs-null> |
| Status: | RESOLVED UNMAINTAINED | ||
| Severity: | wishlist | CC: | ana, angel_blue_co2004, darknessrs, h, khanreaper, serhiy.int, szo |
| Priority: | LO | ||
| Version: | unspecified | ||
| Target Milestone: | --- | ||
| Platform: | unspecified | ||
| OS: | Other | ||
| Latest Commit: | Version Fixed In: | ||
| Sentry Crash Report: | |||
|
Description
Greg Coit
2002-04-30 07:53:17 UTC
Subject: Re: screensaver for kdm --- Oswald Buddenhagen <ossi@kde.org> wrote: > ------- You are receiving this mail because: ------- > You reported the bug, or are watching the reporter. > > http://bugs.kde.org/show_bug.cgi?id=41941 > ossi@kde.org changed: > > What |Removed > |Added > ---------------------------------------------------------------------------- > Status|UNCONFIRMED |NEW > everconfirmed|0 |1 > Priority|NOR |LO Hello, I've found out that this is certainly doable (And available now). The trick it to follow the instructions in the xdm man page - these settings are then incorporated by kdm. I know have xscreensaver running while kdm is active (and I forgot to close the bug (wishlist) report). Please let me know if there is any information I can provide. Thanks! Greg Coit gregcoit@yahoo.com __________________________________________________ Do you Yahoo!? Yahoo! Mail Plus - Powerful. Affordable. Sign up now. http://mailplus.yahoo.com yes, it would be nice if you described what you did. btw, always quote only what is absolutely necessary to understand the context of your reply - in the above case nothing. Well, I just tried it, and it seems the general idea would be to edit ${KDEDIR}/share/config/kdm/Xsetup to run xscreensaver &, additionally writing out its pid to a file if you wanted to kill it (using the Xstartup script) before starting the session.
The way I tried it was by running gkrellm2, but somehow that locked up the keyboard almost completely, preventing me from logging in. Thank God for console login. :-)
yeah, both the screensaver and kdm try to grab the keyboard. there is probably a way to prevent xscreensaver from doing this, though. Implementing this feature, one must be very careful that no security leak à la "replace logon.scr with musrmgr.exe" will be included. http://www.google.com/search?q=replace+logon.scr+with+musrmgr.exe Has information about that principle Here's excatly what I did: I added the following to the /etc/X11/xdm/Xsessions file (near the top right above the "# handle KDM line": xscreensaver-command -exit xscreensaver & Then I added the following to the Xsetup_0 file (right below the part that sets the KDEDIR variable): xhost +localhost xscreensaver-command -exit xscreensaver & Hope this helps! I'm going to mark this as resolved.... uhm, no, i want built-in support one day. the current solution is beyond the non-techie user. Yes I don't like xscreensaver, and I want to have diaporama or other stuff that kde provide for screensaver While the above is a nice hack, I agree with the above posters in that it would be nice to have the native implementation work. You will also have to change My environment: Fedora Core 3 with kernel 2.6.10-1.760_FC3 NVidia 5700LE running the NVIDIA-Linux-x86-1.0-6629 drivers xorg-x11-6.8.1-12.FC3.21 xscreensaver-4.18-4 kdebase-3.3.1-4.3.FC3 Screensavers work fine in preview mode. Also, if you just run the following from the command line (moebius used), a window will pop up with the screen saver. /usr/X11R6/lib/xscreensaver/moebius However, if you add the -root command line switch, an error will occur. Here is the text of that error. /usr/X11R6/lib/xscreensaver/moebius -root X error in moebius: X Error of failed request: BadWindow (invalid Window parameter) Major opcode of failed request: 3 (X_GetWindowAttributes) Resource id in failed request: 0x7 Serial number of failed request: 248 Current serial number in output stream: 249 This is the exact same error that you get when you run: /usr/bin/kdesktop_lock From this it would appear that there's an incompatibility with the way kdm is providing Window information and the way that a native (xdm) program expects it. A native solution to this would be nice. *** Bug 99887 has been marked as a duplicate of this bug. *** Are there any news? This issue still happens with kde 3.4.2 (and FC3). Hope this is added to Login Manager in some future version of KDE4 I guess this can be closed now. KDM is unmaintained and not used in KDE Plasma 5. SDDM is the login manager used in KDE Plasma 5. If you still have this same issue with SDDM, please file an issue on the SDDM bugtracker (after doing a search for existing issues first!): https://github.com/sddm/sddm/issues/ |