Please, keep the bug CC (full quote for the bug log), and please also
answer the last question (are more versions also affected or not?).

> i thought a picture is worth a thousand words but if that is not true for
> you i will try to explain it even so i am not very skilled in doing this
> using the english language...

An error message in German, hidden in a picture, without an explanation,
was definitely not understandable, thanks for coming back to us.

>     * What led up to the situation?
> just installed requestpolicy using apt-get on my debian stable system and
> restarted my iceweasel
>     * What exactly did you do (or not do) that was effective (or
>       ineffective)?
> i dont think that the exact way i chose really matters.
> $ tail /var/log/apt/history.log
>> Start-Date: 2015-03-01 19:18:36 Commandline: apt-get install
>> xul-ext-requestpolicy Install: xul-ext-requestpolicy:amd64 (0.5.25-1)
>> End-Date: 2015-03-01 19:18:42
> startet iceweasel, tryed to open pages, got problems, pressed ctrl+t to
> open new tab, entered another url directly by keyboard, pressed return
>      * What was the outcome of this action?
> the request policy plugin tryed to gard me from my own request. (as you
> can see at the picture) It thought that the request had been made by
> about:newtab but insted i typed in the url by my self.
>     * What outcome did you expect instead?
> that my own request will be exepted, otherwise i had to whitelist every
> url that i am typing in what sure isnt the right way.
> i guess the reason for that error is an incompatibility between the
> iceweasel version and the request policy version. Even so both packages
> are part in the debian stable version. I have installed the latest version
> using mozillas addon page and the problem isnt present anymore. So please
> follow my steps, try that out and fix that!!
> thanks a lot and keep up the good work
> Am 01.03.2015 um 19:55 schrieb "David Prévot":
>> Hi treaki,
>> Thanks for your interest in packaged extensions.
>>> Package: xul-ext-requestpolicy
>>> Version: 0.5.25-1
>>> Severity: important
>>> have a look at this screenshot,
>> That’s not really a useful bug report.
>>> something is wrong..
>> Please, do explain what is going on, consider using the default
>> reportbug
>> template and answer the following questions:
>>     * What led up to the situation?
>>     * What exactly did you do (or not do) that was effective (or
>>       ineffective)?
>>     * What was the outcome of this action?
>>     * What outcome did you expect instead?
>>> please fix that

>> Please also document if the issue is fixed in 0.5.28-1 (as available in
>> Jessie and Sid) or 1.0.0~beta8.2+dfsg-1 (as available in experimental).
>> Regards
>> David

Pkg-mozext-maintainers mailing list

Reply via email to