Bug 1912424 Comment 5 Edit History

Note: The actual edited comment in the bug view page will always show the original commenter’s name and original timestamp.

Hello,

We did not manage to reproduce using Stable Debian GNU/Linux 12(Bookworm)[Gnome Version 43.9) using the STR from the Description.
When opening Developer tools , I receive an "Incoming Connection" prompt in which if I press OK, developer tools open without any issues.
I am able to reproduce it however, if in the above mentioned prompt I select "Disable". Then I will no longer receive the "incoming connection" prompt and developer tools will no longer be displayed.

It is worth mentioning that I have tried to switch to unstable using the instructions from [Wiki](https://wiki.debian.org/DebianUnstable) and was unable to .

If you are still able to reproduce this issue with the same steps and would like to provide assistance in us addressing this issue, it would be very helpful if you could help us determine a regression range.

I will provide some steps to make it easier for you:

You have to determine a build that reproduces the issue. In your (case)[https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1078201) it seems it reproduce either on 128.x or on 115.x, right? You can retest it anytime.

Then you should find one that does NOT reproduce it. Detailed steps:
a. Open Mozregression app;
b. Click "File" -> "Run a single build";
c. On the "Single Run Wizard" pop-up, "Basic configuration", select "Thunderbird" and click "Next".
d. On the "Profile selection" page, just click the "Next" button.
e. On the "Build selection" select a date (dates before 2024-08-09 you find one that does not reproduce the issue) on the from the drop-down on the left and click "Finish".
f. Now the mozregression app will open a thunderbird build of the selected date and you can use it, close it and open another. (make a note of the version that does not reproduce the issue)

You will use mozregression app to "bisect" builds that reproduce the issue by builds that do not reproduce it in search of the one build/changeset that introduced the issue, in the first place:
a. Open mozregression-gui.exe
b. Click "File" -> "Run a new bisection"
c. On "Basic configuration" screen, select "Thunderbird" and click "Next" button.
d. Skip "Profile selection" screen by the "Next" button.
e. On the Bisection wizard screen, you will need to select a build that reproduces the issue and one that does not:
e1. In the "Last known good build:" section, select "date" on the right drop-down and the date of the build you found NOT to reproduce the issue.
e2. In the "First known bad build:" section, select "date" on the right drop-down and the date of the build you found to reproduce the issue.
f. Click "Finish" to start the bisection process.
g. Builds will open one-by-one, you will need to test each one of them and see whether the issue reproduces. If it reproduces, then you need to select the "bad" button in the mozregression window and if not, you need to select the "good" button.
h. When bisection is done, you will have the information in the "Log View" section of the mozregression window; bisection may also fail due to not enough builds, but the logs can always be useful.
Copy the logs in a text file and attach it to this bug.

If there is still information you need regarding the regression process, please request information from me.
Thank you for your contribution!
Hello,

We did not manage to reproduce using Stable Debian GNU/Linux 12(Bookworm)[Gnome Version 43.9) using the STR from the Description.
When opening Developer tools , I receive an "Incoming Connection" prompt in which if I press OK, developer tools open without any issues.
I am able to reproduce it however, if in the above mentioned prompt I select "Disable". Then I will no longer receive the "incoming connection" prompt and developer tools will no longer be displayed.

It is worth mentioning that I have tried to switch to unstable using the instructions from [Wiki](https://wiki.debian.org/DebianUnstable) and was unable to .

If you are still able to reproduce this issue with the same steps and would like to provide assistance in us addressing this issue, it would be very helpful if you could help us determine a regression range.

I will provide some steps to make it easier for you:

You have to determine a build that reproduces the issue. In your [case](https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1078201) it seems it reproduce either on 128.x or on 115.x, right? You can retest it anytime.

Then you should find one that does NOT reproduce it. Detailed steps:
a. Open Mozregression app;
b. Click "File" -> "Run a single build";
c. On the "Single Run Wizard" pop-up, "Basic configuration", select "Thunderbird" and click "Next".
d. On the "Profile selection" page, just click the "Next" button.
e. On the "Build selection" select a date (dates before 2024-08-09 you find one that does not reproduce the issue) on the from the drop-down on the left and click "Finish".
f. Now the mozregression app will open a thunderbird build of the selected date and you can use it, close it and open another. (make a note of the version that does not reproduce the issue)

You will use mozregression app to "bisect" builds that reproduce the issue by builds that do not reproduce it in search of the one build/changeset that introduced the issue, in the first place:
a. Open mozregression-gui.exe
b. Click "File" -> "Run a new bisection"
c. On "Basic configuration" screen, select "Thunderbird" and click "Next" button.
d. Skip "Profile selection" screen by the "Next" button.
e. On the Bisection wizard screen, you will need to select a build that reproduces the issue and one that does not:
e1. In the "Last known good build:" section, select "date" on the right drop-down and the date of the build you found NOT to reproduce the issue.
e2. In the "First known bad build:" section, select "date" on the right drop-down and the date of the build you found to reproduce the issue.
f. Click "Finish" to start the bisection process.
g. Builds will open one-by-one, you will need to test each one of them and see whether the issue reproduces. If it reproduces, then you need to select the "bad" button in the mozregression window and if not, you need to select the "good" button.
h. When bisection is done, you will have the information in the "Log View" section of the mozregression window; bisection may also fail due to not enough builds, but the logs can always be useful.
Copy the logs in a text file and attach it to this bug.

If there is still information you need regarding the regression process, please request information from me.
Thank you for your contribution!

Back to Bug 1912424 Comment 5