Bug 448183
| Summary: | KDE 4.0.4 Screensaver does not start automatically | ||||||
|---|---|---|---|---|---|---|---|
| Product: | [Fedora] Fedora | Reporter: | Andrea <mariofutire> | ||||
| Component: | kdebase-workspace | Assignee: | Lukáš Tinkl <ltinkl> | ||||
| Status: | CLOSED CURRENTRELEASE | QA Contact: | Fedora Extras Quality Assurance <extras-qa> | ||||
| Severity: | low | Docs Contact: | |||||
| Priority: | low | ||||||
| Version: | 9 | CC: | fedora, jgrulich, kevin, ltinkl, rdieter, than | ||||
| Target Milestone: | --- | ||||||
| Target Release: | --- | ||||||
| Hardware: | i686 | ||||||
| OS: | Linux | ||||||
| Whiteboard: | |||||||
| Fixed In Version: | 4.0.5-3 | Doc Type: | Bug Fix | ||||
| Doc Text: | Story Points: | --- | |||||
| Clone Of: | Environment: | ||||||
| Last Closed: | 2008-06-23 21:24:51 UTC | Type: | --- | ||||
| Regression: | --- | Mount Type: | --- | ||||
| Documentation: | --- | CRM: | |||||
| Verified Versions: | Category: | --- | |||||
| oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |||||
| Cloudforms Team: | --- | Target Upstream Version: | |||||
| Embargoed: | |||||||
| Attachments: |
|
||||||
|
Description
Andrea
2008-05-24 06:27:07 UTC
Works for me. 'Science' screensaver; starts after 5 mins, no password required. (From kdeartwork-extras-4.0.4-1.fc9.x86_64) John. (In reply to comment #1) > Works for me. > > 'Science' screensaver; starts after 5 mins, no password required. > (From kdeartwork-extras-4.0.4-1.fc9.x86_64) In my case, none of the screensavers works. With or without kdeartwork and ldeawrtwork-extras installed. Andrea Can't reproduce here either. What video hw/driver are you using? (In reply to comment #4) > What video hw/driver are you using? 01:00.0 VGA compatible controller: ATI Technologies Inc Radeon RV250 [Mobility FireGL 9000] (rev 02) (prog-if 00 [VGA controller]) I'm using the radeon dirver. How can I check if this service is running properly. Obviously what SystemSettings reports is not exact? Created attachment 307289 [details]
Output of startx
This is the output of the current X session, in which I have manually stopped
and started the screensaver.
startx? you're not using a desktopmanager like gdm or kdm? (In reply to comment #7) > startx? you're not using a desktopmanager like gdm or kdm? No. I start in text-mode runlevel 3 and when I need X, I start it manually with startx. Is it not supported any more? Not really (you miss out on at least ConsoleKit support). Please use gdm or kdm, and see if you can still reproduce. (In reply to comment #9) > Not really (you miss out on at least ConsoleKit support). > Please use gdm or kdm, and see if you can still reproduce. No difference. I've set the default runlevel to 5, rebooted and did not notice any difference. Is there a way to query the screensaver daemon to see what it is doing? Cheers This is probably something to get upstream involved with, and report to them at bugs.kde.org. I have no idea why/how this affects some folks, and not others. Neither I, nor any other fedora kde-sig'er (afaik) can reproduce this. (In reply to comment #11) > This is probably something to get upstream involved with, and report to them at > bugs.kde.org. > > I have no idea why/how this affects some folks, and not others. Neither I, nor > any other fedora kde-sig'er (afaik) can reproduce this. Ok, I've posted the bugreport to kde. http://bugs.kde.org/show_bug.cgi?id=163006 Could you please tell me which application/daemon/configuration is involved. So that I try to resolve it by myself. Is there a way to enable/disable the screensaver using a script? Thanks kscreensaver is integrated, afaik, there is no separate application/daemon, and configuration is set solely via systemsettings. Re: scripting, I would normally recommend xdg-screensaver , but alas, that seems to not yet work with kde4 (for me anyway). If you're seeking additiona debugging hints/advice, I'd recommend using one of the kde mailing lists (unless someone else listening here has better advice... feel free to chime in). (In reply to comment #13) > kscreensaver is integrated, afaik, there is no separate application/daemon, and > configuration is set solely via systemsettings. > > Re: scripting, I would normally recommend xdg-screensaver , but alas, that seems > to not yet work with kde4 (for me anyway). > > If you're seeking additiona debugging hints/advice, I'd recommend using one of > the kde mailing lists (unless someone else listening here has better advice... > feel free to chime in). I can confirm that xdg-screensaver is problematic: [andrea@thinkpad ~]$ xdg-screensaver status call failed ERROR: kdesktop KScreensaverIface isEnabled returned '' It's obviously trying to use DCOP, which won't work with KDE 4. (In reply to comment #15) > It's obviously trying to use DCOP, which won't work with KDE 4. What is the correct way? Do you know why xdg-screensaver is shipped as part of Fedora even if it does not work? > What is the correct way? D-Bus. > Do you know why xdg-screensaver is shipped as part of Fedora even if it does > not work? Because it's part of the upstream xdg-utils. This issue has to be filed at http://bugs.freedesktop.org if it isn't already filed there. It isn't relevant to this bug report in any case. kdebase-workspace-4.0.5-3.fc9 has been submitted as an update for Fedora 9 kdebase-workspace-4.0.5-3.fc9 has been pushed to the Fedora 9 stable repository. If problems still persist, please make note of it in this bug report. Good news. It has been working for 3 days. Hope it is fixed forever. Good to hear, please reopen if it happens again :) |