Control: tags -1 unreproducible Control: tags -1 moreinfo Hello Shirish!
On 05/19/2015 08:36 PM, shirish शिरीष wrote: > Now even if I type the credentials the asteriks that should appear > (*******************) don't appear and authentication fails. I just tried to reproduce your problem and I was unable to, mate-screensaver 1.8.1-2 works as expected on my system. I can lock the screen and then type my password to unlock my screen again without any issues. Furthermore I would like to give you an advise: The bug you are reporting here would basically be a regression of a fundamental functionality of the screensaver, i.e. locking the screen and being able to unlock it with the correct password. If you ever encounter such a fundamental issue, your first thought shouldn't be: "Oh, looks like I found a bug, I'll just go ahead and report it." Rather you should actually absolutely make sure you didn't mess up anything with your installation. If you really want to file useful bug reports, you should actually test such issues on a clean installation. This is the only way to make sure that the problem you are seeing is not a local configuration problem or whatsoever. You can also do some googling to figure out whether there are others who already ran into the same problem. Given the fact that the problem you found is such a fundamental issue, chances are very high that many others already ran into the same problem and potentially have reported your bug upstream or to other distribution bug trackers or just posted the issues on community support forums for you to find it. But your current bug report is rather more like a support ticket that you would send to your IT department: "Hey, my screensaver doesn't work properly, please have a look and fix it." But that's not how a useful bug report should look like. A useful bug report should rather be like: "See, I upgraded application xyz to 1.9.2 and started the application to use function abc, then application crashes reproducibly. However, when I downgrade to 1.9.1, it works as expected." This would help us much more instead of just the report of something not working. Don't get me wrong, I absolutely do not want to discourage you from writing bug reports, bug reports are necessary and always welcome. However, I would like to ask you to do some more testing yourself before sending such a report in order to help us trying to locate and fix the issue. Otherwise chances are, the developers waste too much time trying to find a bug which doesn't really exist because it was just a configuration error on machine of the bug submitter. TL;DR: Needs more info. Adrian -- .''`. John Paul Adrian Glaubitz : :' : Debian Developer - [email protected] `. `' Freie Universitaet Berlin - [email protected] `- GPG: 62FF 8A75 84E0 2956 9546 0006 7426 3B37 F5B5 F913 -- To UNSUBSCRIBE, email to [email protected] with a subject of "unsubscribe". Trouble? Contact [email protected]
