Feedback topic for bug forum.

[Guest]

[mouse1]

I'll move this to feedback if that's OK and respond there

Best wishes

Mouse

[mouse1]

why not just set up a web fprm for the bug or glitch issues. this way it is a form with the specifics you want and it can maybe get looked at or emailed to a coordinater instead of sitting in limbo on a web forum.
something to consider to stream efforts to get things right.

This is an interesting suggestion. But such things take time I am afraid - we are quite a long way from being able to do this at present!

[Peroulades]

Child Boards within Bug Reports can only be seen by Logged On Users. This seriously restricts the number of forum users that are able to see the real bug issues.
For example I rarely log-on unless I wish to add to the forum issues and I suspect there are a lot of casual users that do the same.
Hence there is less chance of finding a suitable workaround from a user who may have the same problem.
Also there is no guarantee that the Bug reported has been accepted as an issue by the Developers.
Less visibility = Less chance of a solution.

Regards

[mouse1]

Child Boards within Bug Reports can only be seen by Logged On Users. This seriously restricts the number of forum users that are able to see the real bug issues.
For example I rarely log-on unless I wish to add to the forum issues and I suspect there are a lot of casual users that do the same.
Hence there is less chance of finding a suitable workaround from a user who may have the same problem.
Also there is no guarantee that the Bug reported has been accepted as an issue by the Developers.
Less visibility = Less chance of a solution.

Regards

Thanks. I guess I understand this may be an inconvenience, but is it a major one in a world of automated log-ons? Happy to be persuaded

Your other point about the visibility of developer investigation is well made. THey have agreed to mark posts as under investigation. I will remind.

[Peroulades]

Thanks. I guess I understand this may be an inconvenience, but is it a major one in a world of automated log-ons? Happy to be persuaded

It is not a convenience issue. It is the fact that many users may visit the forum without being a member and hence will only see Bug Reports that are available to them. If they see an issue that is pertinent to them they may well take up membership and reply. This is my point about visibility. Those issues that are raised without the correct format have more visibility than those with the correct format. Convinced?

Also, on the issue of automated log-ons, there are a lot of PC users who do not store userids, passwords or cookies on their PCs for safety/privacy reasons.

Regards

[HeffeD]

Also, on the issue of automated log-ons, there are a lot of PC users who do not store userids, passwords or cookies on their PCs for safety/privacy reasons.

Not a problem. I use RoboForm Password Manager. No passwords stored in the browser, passwords stored on computer are encrypted, you can have your logon of Roboform last for a session, or have it time out after a period of time. I've used it for years and have been very happy. You can even use a portable version so you can carry your passwords around with you to use on any computer.

[mouse1]

It is not a convenience issue. It is the fact that many users may visit the forum without being a member and hence will only see Bug Reports that are available to them. If they see an issue that is pertinent to them they may well take up membership and reply. This is my point about visibility. Those issues that are raised without the correct format have more visibility than those with the correct format. Convinced?

Also, on the issue of automated log-ons, there are a lot of PC users who do not store userids, passwords or cookies on their PCs for safety/privacy reasons.

Regards

Thanks for your further thoughts. Will raise the issue with the mods. It wll probably depdend on whether the forum software offers this facility.

Many thanks

Mouse

[SS26]

+1 Peroulades

As for standard format:

1. i think that quoted below part of Bug writing guidelines is easier to follow and less complicated than #1 ("What you did:"), #2 ("What actually happened or you actually saw:"), #3 ("What you expected to happen or see:"), #7 (? -- why it is number 7 and not 4 in the first place? next question: what is it for in the first place -- just to copy paste what was already described in #1 ? ).

Steps to Reproduce: Minimized, easy-to-follow steps that will trigger the bug. Include any special setup steps.

Code:

1) View any web page. (I used the default sample page,
resource:/res/samples/test0.html)

2) Drag-select the page. (Specifically, while holding down
the mouse button, drag the mouse pointer downwards from any
point in the browser's content region to the bottom of the
browser's content region.)

Actual Results: What the application did after performing the above steps.

Code:

The application crashed.

Expected Results: What the application should have done, were the bug not present.

Code:

The window should scroll downwards. Scrolled content should be selected.
(Or, at least, the application should not crash.)

2. What for #4 ("How you tried to fix it & what happened:") -- developer was provided step-by-step instructions, it's up to developer "to try to fix and see what happens", no need to irritate user with excessive questions.

3. What for #5 ("If its an application compatibility problem have you tried the application fixes here?:") -- developer was provided step-by-step instructions, it's up to developer to classify bug as incompatibility with definite software or smth else; who knows what means phrase "application fixes" in the first place.  No need to irritate user with excessive questions.

4. What for #6 ("Details (exact version) of any application involved with download link:"), if there is a paragraph "Your set-up" -- just to copy paste CIS version?

...more will follow probably... This "feedback" because i spit a lot when filling out a bug in "standard format".  By the way, who made "standard format"?  Were CIS developres among those who made "standard format"?

[mouse1]

+1 Peroulades

This has been requested. No action yet unfortunately.

Points on the format.
Thanks for your feedback, which is much appreciated.

1. i think that quoted below part of Bug writing guidelines is easier to follow and less complicated than #1 ("What you did:"), #2 ("What actually happened or you actually saw:"), #3 ("What you expected to happen or see:"), #7 (? -- why it is number 7 and not 4 in the first place? next question: what is it for in the first place -- just to copy paste what was already described in #1 ? ).

I'll check the numbering problem - thanks.

Re the other issues. If all bugs were immediately replicable and all users were capable and willing to set down precise steps to replicate, then having only the 'steps to replicate' question would work, if and only if the expected as well as actual behaviour were included in such steps. Unfortunately often we are presented reports which instinct tell us are genuine, but are very difficult to replicate, and/or users who find it very difficult to be precise enough to describe steps to replicate properly and/or users who think that expected behaviour is a bug and, without a specific question will not indicate what they (fallaciously but often understandably) expect to happen. Please note that steps to replicate are often only arrived at after a lot of work with users, particularly if users are less expert. Incidentally the devs tell us that 'what actually happened' and what is expected to happen is their starting point for analysis.

2. What for #4 ("How you tried to fix it & what happened:") -- developer was provided step-by-step instructions, it's up to developer "to try to fix and see what happens", no need to irritate user with excessive questions.

It's OK to reply nothing and not applicable to #4 questions. This is just to collect the information if the users have it. It's really there to save us and the devs from asking have you tried x or y? Remember not all apparent bugs actually are bugs, they may describe expected behaviour if the user fails to use CIS correctly.

3. What for #5 ("If its an application compatibility problem have you tried the application fixes here?:") -- developer was provided step-by-step instructions, it's up to developer to classify bug as incompatibility with definite software or smth else; who knows what means phrase "application fixes" in the first place.  No need to irritate user with excessive questions.

There will always be software that conflicts with security packages unless specific package settings are used. The aim of this setting is to determine whether these settings have been tried, and thus distinguish genuine from invalid issues. Again this save mods and developers time.

4. What for #6 ("Details (exact version) of any application involved with download link:"), if there is a paragraph "Your set-up" -- just to copy paste CIS version?

I agree this could be more clearly phrased and will amend it. This means 'third party software' not CIS.

...more will follow probably... This "feedback" because i spit a lot when filling out a bug in "standard format".  By the way, who made "standard format"?  Were CIS developres among those who made "standard format"?

I'm sorry you find it frustrating. Maybe if you reflect on the fact that CIS gives so much for free, it will make it easier to understand why these reports have a strong emphasis on saving developer and moderator time. If no automation is provided a consequence of this is that more user time is involved. Also maybe it will help to reflect on the needs and limitations of users less expert than yourself, and the fact that working with such users to create bug reports is a process of eliciting information, not a one off report submission. If I remember correctly you have submitted some very useful bug reports in the past, with seeming ease, but not everyone finds this easy! (Devs were involved in designing the process, but I would welcome further and more detailed input - eg line by line comments on the format - if any dev reads this. I am an ex software - albeit 4GL - developer myself).

Hope this helps you to understand, and please be assured that I will make the corrections promised above and reflect on the rest of your very helpful input further.

Best wishes

Mouse

[SS26]

You R too kind man, Mouse.

[Valentin N]

Hey there everyone

I have checked how the the bug report is written and I must say that some of the sentences are hard to understand and some are wrong made.

For instance the question "What you did"...

I will give my version of the bug report and please feel free to help. I am not aiming to say anything bad but I think it can be improved.

Valentin's version of the bug report

We would appreciate if you write your answer thick (by pressing on B under Message icon).

Bug reports:

The bug/issue
1. What did you do:
2. What did actually happen or what did you actually see:
3. What did you expect to happen or see:
4. How did you try to fix it & what happened:
5. If its an application compatibility problem please tell us how have you tried to fix it:
6. Details & exact version of any application (execpt CIS) and please provide us the download link:
7. If you know how you can make the problem happen again, please tell us how it's done:
8. Could you provide us with any other information that might find useful and important to know and that's related to your bug/issue (eg your guess regarding the cause, with reasons):

Attached files (Additional Options ---> Attach). (Please zip unless screenshots).
1. Screenshots illustrating the bug:
2. Screenshots of related CIS event logs and the Defense+ Active Processes List:
3. A CIS config report or file (You will find CIS's crash report by writting: %AllUsersProfile%\Comodo\CISDumps in run.
4. Crash or freeze dump file:

Your set-up
1. CIS version, AV database version & configuration used:
2. a) Have you updated (without uninstall) from CIS 3 or 4:
    b) if so, have you tried a clean reinstall (without losing settings - if not please do)?:

3. a) Have you imported a config from a previous version of CIS:
    b) if so, have you tried a standard config (without losing settings - if not please do)?:

4. Have you made any other major changes to the default config? (eg ticked 'block all unknown requests', other egs here.):

5. Defense+,  Sandbox,  Firewall & AV security levels:
D+= ,
Sandbox= ,
Firewall =
AV = 

6. Please provide us with following information:
OS version:
service pack:
number of bits,
UAC setting,
Account type:

7. Do you have other security and utility software installed:

8. Did you use Virtual machine (Please do NOT use Virtual box):

Regards,
            Valentin N

[mouse1]

Hey there everyone

I have checked how the the bug report is written and I must say that some of the sentences are hard to understand and some are wrong made.

For instance the question "What you did"...

I will give my version of the bug report and please feel free to help. I am not aiming to say anything bad but I think it can be improved.

Valentin's version of the bug report

We would appreciate if you write your answer thick (by pressing on B under Message icon).

Bug reports:

The bug/issue
1. What did you do:
2. What did actually happen or what did you actually see:
3. What did you expect to happen or see:
4. How did you try to fix it & what happened:
5. If its an application compatibility problem please tell us how have you tried to fix it:
6. Details & exact version of any application (execpt CIS) and please provide us the download link:
7. If you know how you can make the problem happen again, please tell us how it's done:
8. Could you provide us with any other information that might find useful and important to know and that's related to your bug/issue (eg your guess regarding the cause, with reasons):

Attached files (Additional Options ---> Attach). (Please zip unless screenshots).
1. Screenshots illustrating the bug:
2. Screenshots of related CIS event logs and the Defense+ Active Processes List:
3. A CIS config report or file (You will find CIS's crash report by writting: %AllUsersProfile%\Comodo\CISDumps in run.
4. Crash or freeze dump file:

Your set-up
1. CIS version, AV database version & configuration used:
2. a) Have you updated (without uninstall) from CIS 3 or 4:
    b) if so, have you tried a clean reinstall (without losing settings - if not please do)?:

3. a) Have you imported a config from a previous version of CIS:
    b) if so, have you tried a standard config (without losing settings - if not please do)?:

4. Have you made any other major changes to the default config? (eg ticked 'block all unknown requests', other egs here.):

5. Defense+,  Sandbox,  Firewall & AV security levels:
D+= ,
Sandbox= ,
Firewall =
AV = 

6. Please provide us with following information:
OS version:
service pack:
number of bits,
UAC setting,
Account type:

7. Do you have other security and utility software installed:

8. Did you use Virtual machine (Please do NOT use Virtual box):

Regards,
            Valentin N

Hi Valentin

Sorry for the delayed reply, I have been away from the forums - still am mostly, due to illness in my family.

Many thanks for your many comments - we will consider them when we next do a major revision of the format.

Best wishes

Mouse

[Valentin N]

Hi Valentin

Sorry for the delayed reply, I have been away from the forums - still am mostly, due to illness in my family.

Many thanks for your many comments - we will consider them when we next do a major revision of the format.

Best wishes

Mouse

Hey Mouse

I am sorry to hear that and I thank you for answering back and also taking my bug version in consideration; it has been few times that people (in general) have take my tips/advices in consideration.

Thanks for answer and I wish your family all the best.

Regards,
            Valentin N

[stuhart]

Please post here

a) any feedback relating to the bugs/issues forum. For example on guide, format, process etc
v) any requests for help on using the format, guidelines or bug reporting process

Best wishes

Mouse

hi very new to all this and dont understand it all when i turned my pc on other day commodo told me it had a bug but couldnt send info at time and thought it said it saved info in zip file so i looked for it and couldnt find anything obvious i probably got it wrong and forgot where it was saved could you tell me the right type of file and whare it might be

[mouse1]

hi very new to all this and dont understand it all when i turned my pc on other day commodo told me it had a bug but couldnt send info at time and thought it said it saved info in zip file so i looked for it and couldnt find anything obvious i probably got it wrong and forgot where it was saved could you tell me the right type of file and whare it might be

Please see this FAQ here.

Best wishes

Mouse

[Tags:]