> the screensaver stuff looks at to know about whether to start or not. And this boolean in systemsettings should be what > screensaver is about to start, it checks whether or not the user actually wants > I'll try to explain how my 'naive' way of thinking see things: When the > Or tell us "dummies, wait for us to care" No discussion has yet been started on this side > there would be some trace of that somwhere so that someone can start looking. > so, i'd really urge (beg? yes, I beg) you to tell us more about it, at least This needs to be discussed into KDE, as screen lock handling has to be reworked > where ? If not, why is it so ? are you the only one aware of this problem ? if > What is it that "needs discussion" ? Has it been discussed already ? I'm saying: if you want to add comments like "Oh shit has to be fixed or everyone will die", then yes, you'd better shut up. > some more about what the bug really is, and where in "kde internals" we should > we could go forward in a lot more friendly and effective manner if you told us > You keep saying "patch it or shut up" and "it's deep in kde internals". > actually a lot more difficult to understand. > this, and even more, you tell me that what seemed to be a trivial issue is > I'd love to be able to provide a patch, trust me, but i have no clue about The problem is that screen locking is handled by the screensaver itself, and until this does not change, if you have a screensaver set it will start up. Here as well, and the screensaver does not start. It's disabled here, but the screensaver keeps on starting. > "Start automatically" in the 'screensaver' part of 'systemsettings' to be and you tell me i should "just" disable it. i'm DREAMING of disabling the screensaver, that's what this bug report I dont know what powerdevil is or how if fits there. And this boolean in systemsettings should be what the screensaver stuff looks at to know about whether to start or not. I'll try to explain how my 'naive' way of thinking see things: When the screensaver is about to start, it checks whether or not the user actually wants it. Or tell us "dummies, wait for us to care" What is it that "needs discussion" ? Has it been discussed already ? where ? If not, why is it so ? are you the only one aware of this problem ? if so, i'd really urge (beg? yes, I beg) you to tell us more about it, at least there would be some trace of that somwhere so that someone can start looking. I think we could go forward in a lot more friendly and effective manner if you told us some more about what the bug really is, and where in "kde internals" we should look at. You keep saying "patch it or shut up" and "it's deep in kde internals". I'd love to be able to provide a patch, trust me, but i have no clue about this, and even more, you tell me that what seemed to be a trivial issue is actually a lot more difficult to understand. All i'm wanting is the button saying "Start automatically" in the 'screensaver' part of 'systemsettings' to be followed. i'm DREAMING of disabling the screensaver, that's what this bug report is all about.
0 kommentar(er)
