What is the status of VB (=already reported bug/issue)?
-
@naseyuki VB-51316 is still a new bug and has not been confirmed by a tester yet. However, this appears to be a duplicate of a crash that I reported a few months ago, VB-48162.
-
Status of the following please?
- VB-51056
- VB-51169
- VB-51190
- VB-51285
- VB-51298
- VB-51301
- VB-51306
- VB-51309
- VB-51310
- VB-51331
- VB-51387
- VB-51408
Also I sent new footage to show VB-50952 and VB-51209.
-
@AltCode VB-51309 and VB-51387 are both confirmed. VB-51285 was closed as a duplicate of VB-51194. The rest are all unconfirmed... and some of the bug reports that you are asking about are so new that the ink on them has not even dried yet.
-
Status of
- VB-14691 -
- VB-34482 -
- VB-38449 -
- VB-42578 -
- VB-42580 -
- VB-50906 -
- VB-51347 -
- VB-51349 -
- VB-51351 -
- VB-51352 -
- VB-51353 -
- VB-51354 -
- VB-51356 -
- VB-51360 -
Please
-
@LonM Status of the bugs are as follows:
VB-14691 - Closed / Cannot Reproduce
VB-34482 - Duplicate of VB-23668, which was fixed on 2018-09-30
VB-38449 - Duplicate of VB-38489, which was closed (cannot reproduce) on 2018-04-04
VB-42578 - Confirmed / Unassigned
VB-42580 - Duplicate of VB-33522, which is Confirmed / Unassigned
VB-50906 - Closed (Invalid) on 2019-03-26 (Reason: option is removed now)
VB-51347 - Open / Unconfirmed
VB-51349 - Open / Unconfirmed
VB-51351 - Open / Unconfirmed
VB-51352 - Open / Unconfirmed
VB-51353 - Open / Unconfirmed
VB-51354 - Open / Unconfirmed
VB-51356 - Open / Unconfirmed
VB-51360 - Open / Unconfirmed -
Status of VB-46204?
Thanks!
-
@GyozaGuy said in What is the status of VB (=already reported bug/issue)?:
VB-46204
Closed. Can Not Reproduce.
-
@mveljaca said in What is the status of VB (=already reported bug/issue)?:
can you please check the status of VB-51535 ?
Confirmed
-
I take it enough time has passed now for "the ink on them to dry".
Status of
- VB-50952
- VB-51056
- VB-51169
- VB-51190
- VB-51194
- VB-51209
- VB-51285
- VB-51298
- VB-51301
- VB-51306
- VB-51310
- VB-51331
- VB-51408
Please?
-
@naseyuki
It's closed as a duplicate of VB-48162, which is confirmed and assigned. Progress unknown. -
Hello, could I please get a status check on:
- VB-45879 -
- VB-46828 -
- VB-47976 -
- VB-48848 -
- VB-48966 -
- VB-49046 -
- VB-49323 -
- VB-49579 -
- VB-49792 -
- VB-50220 -
- VB-50337 -
- VB-50525 -
- VB-50944 -
- VB-51347 -
- VB-51349 -
- VB-51351 -
- VB-51352 -
- VB-51353 -
- VB-51354 -
- VB-51356 -
- VB-51360 -
- VB-51715 -
- VB-51716 -
- VB-51717 -
- VB-51755 -
Also, VB-51137/VB-51136 was marked as "invalid" - is there a reason given for this?
Thank you in advance.
-
Status VB-52226?
-
@Nlope Thanks for the report. It's too soon for any kind of a status update. The bug is only about 3 hours old, it is still Unconfirmed, and the only people who have access to the tools required to analyze your crash are currently asleep.
-
Status of VB-49398 and VB-44501?
-
@xyzzy Any new?
-
@Nlope Still too early to ask. Bugs do not move on a day-to-day time scale. There are thousands of them, because it usually takes weeks or months for them to be addressed. Only critical regressions or show-stoppers are usually looked at on same-day basis, and then mostly close to release. And even some of these cannot be solved with a quick turnaround.
On top of this, most of Europe, including Vivaldi, is in Holidays right now. We internal testers are not even getting nightly versions.
-
@Ayespy said in What is the status of VB (=already reported bug/issue)?:
@Nlope Still too early to ask. Bugs do not move on a day-to-day time scale. There are thousands of them, because it usually takes weeks or months for them to be addressed. Only critical regressions or show-stoppers are usually looked at on same-day basis, and then mostly close to release. And even some of these cannot be solved with a quick turnaround.
On top of this, most of Europe, including Vivaldi, is in Holidays right now. We internal testers are not even getting nightly versions.
I understand, thank you for the clarification.
-
@Gwen-Dragon Any news for some of these, particularly the unconfirmed ones?
Also here are some newer reports as well:
- VB-51794
- VB-51795
- VB-51821
- VB-52279
- VB-52280
-
Thanks, but I don't think I was clear enough. Is there any news for these as well?
@Gwen-Dragon said in What is the status of VB (=already reported bug/issue)?:
VB-51056 Unconfirmed
VB-51169 Unconfirmed
VB-51190 Unconfirmed
VB-51209 Invalid
VB-51298 Unconfirmed
VB-51301 Unconfirmed
VB-51306 UnconfirmedAlso after having a closer look through the changelog of snapshot 1525.4, VB-52279 was actually fixed as VB-51196
-
@AltCode Here's the updated status on these bugs:
VB-51056 Unconfirmed (FYI, I can't reproduce this)
VB-51169 Confirmed
VB-51190 Closed: Cannot Reproduce (Although there are other open/confirmed bugs about broken extension popup menus)
VB-51209 Closed: Invalid
VB-51298 Unconfirmed (Might require a HiDPI screen to reproduce)
VB-51301 Unconfirmed (I don't notice this problem)
VB-51306 Resolved: Duplicate (FYI, this setting was recently removed in recent 2.5 builds)