Please read this before reporting a bug:
https://wiki.archlinux.org/title/Bug_reporting_guidelines
Do NOT report bugs when a package is just outdated, or it is in the AUR. Use the 'flag out of date' link on the package page, or the Mailing List.
REPEAT: Do NOT report bugs for outdated packages!
https://wiki.archlinux.org/title/Bug_reporting_guidelines
Do NOT report bugs when a package is just outdated, or it is in the AUR. Use the 'flag out of date' link on the package page, or the Mailing List.
REPEAT: Do NOT report bugs for outdated packages!
FS#55895 - [chromium] Bug 55837 is not fixed but was closed
Attached to Project:
Arch Linux
Opened by Craig Barnes (cbb) - Saturday, 07 October 2017, 00:02 GMT
Last edited by Doug Newgard (Scimmia) - Saturday, 07 October 2017, 04:12 GMT
Opened by Craig Barnes (cbb) - Saturday, 07 October 2017, 00:02 GMT
Last edited by Doug Newgard (Scimmia) - Saturday, 07 October 2017, 04:12 GMT
|
DetailsWhy was Bug #55837 closed as "likely config issue"? The issue has reoccurred for me twice since my last comment on that bug, but I can't add new comments now that it's closed.
It may well be config-related, but the only configs I have are (valid) policy files. The original bug reporter also still has the same issue. Just closing unresolved bugs as "likely config issue" sounds a lot like a thinly veiled way to say "likely stupid user" to me. That's real classy... |
This task depends upon