1. pick a screensaver in kde 2. run a movie or do whatever that updates the screen without typing / moving mouse 3. wait for screensaver delay to time up 4. see screen stopped from being refreshed, instead of screensaver to appear note that the same thing happens whether kwin effects are enabled or not.
Hi, thanks for reporting this bug. Assigned to the package maintainer. (Please set the status to 'assigned' if you are working on it)
Keywords: (none) => TriagedAssignee: bugsquad => balcaen.johnSource RPM: (none) => kdemultimedia4 ?
Could you test with rc2 when it will be available ? What is the movie player used for this ? Do you have any useful logs from ~/.xsession-errors (with kdebugdialog set correctly) ? Also in a general way it seems to be more an upstream bug against kde-workspace.
CC: (none) => balcaen.john
i'll test with rc2. note that it's not new, it is happening since quite some time - i just got fed up with it enough to report a bug. :-) movie player was vlc. but it's not really relevant, even if i'm not using a movie player, screen stops from being refreshed (eg, the clock at the bottom right corner).
ok. did you try to change the default screensaver ?
yes, screen saver was changed to "flying things" what should i enable in kdebugdialog before pasting .xsession-errors?
i can reproduce with rc2.
Trying to ping 41 bug reports in one move, because nothing has happened with them for more than 3 months, they still have the status NEW or REOPENED, there is no "OK" on the Whiteboard and severity and priority are "normal" or higher. Is this one still valid for Mageia 2 rc? If it is and you're the assignee, please set status to ASSIGNED if you think this bug was assigned correctly. If for work flow reasons you can't do that, then please put OK on the whiteboard instead. If it wasn't assigned correctly, please assign back to Bug Squad and explain.
still valid.
Are you able to reproduce with a fresh user ? Do you have anythings useful in logs ?
Hi, This bug was filed against cauldron, but we do not have cauldron at the moment. Please report whether this bug is still valid for Mageia 2. Thanks :) Cheers, marja
Keywords: (none) => NEEDINFO
Please look at the bottom of this mail to see whether you're the assignee of this bug, if you don't already know whether you are. If you're the assignee: We'd like to know for sure whether this bug was assigned correctly. Please change status to ASSIGNED if it is, or put OK on the whiteboard instead. If you don't have a clue and don't see a way to find out, then please put NEEDHELP on the whiteboard. Please assign back to Bug Squad or to the correct person to solve this bug if we were wrong to assign it to you, and explain why. Thanks :) **************************** @ the reporter and persons in the cc of this bug: If you have any new information that wasn't given before (like this bug being valid for another version of Mageia, too, or it being solved) please tell us. @ the reporter of this bug If you didn't reply yet to a request for more information, please do so within two weeks from now. Thanks all :-D
@Jerome : Can you provide the info requested on comment 9. Roelof
CC: (none) => r.wobben
No response in 2 years. Not reproducible in Mageia 5 kde4-config --version Qt: 4.8.6 KDE Development Platform: 4.14.3 kde4-config: 1.0
Status: NEW => RESOLVEDCC: (none) => nicResolution: (none) => WORKSFORME