| Summary: | Crash in NSPluginViewer | ||
|---|---|---|---|
| Product: | [Applications] konqueror | Reporter: | Nick Boyce <nick.boyce> |
| Component: | nspluginviewer | Assignee: | Konqueror Developers <konq-bugs> |
| Status: | RESOLVED UNMAINTAINED | ||
| Severity: | crash | ||
| Priority: | NOR | ||
| Version: | unspecified | ||
| Target Milestone: | --- | ||
| Platform: | Debian stable | ||
| OS: | Linux | ||
| Latest Commit: | Version Fixed In: | ||
| Sentry Crash Report: | |||
|
Description
Nick Boyce
2012-09-14 03:21:34 UTC
Nick please do not report bugs for such old KDE versions, you really should upgrade your system. On Friday 14 Sep 2012 17:12:12 Myriam Schweingruber wrote: > --- Comment #1 from Myriam Schweingruber <myriam@kde.org> --- > Nick please do not report bugs for such old KDE versions, you really should > upgrade your system. My apologies if I have taken up your time with something that is no longer being maintained. I did try to attach my report to two existing bugs open for the same symptoms, so as to prevent time being spent on triaging a new freestanding report. I marked my report as a possible duplicate of 288495, which itself is marked as a duplicate of 213196, which has status "UNCONFIRMED". From that status, and the fact that 213196 has had a stream of other reports added, with at least one query added asking why the bug still has status "UNCONFIRMED" when so many users have confirmed it, I inferred my own report might help clarify the fault. The last user comment on the bug (dated 25.Feb.2012) says "Still true with konqueror/KDE 4.8.00 " There are many many bugs reporting the same NSPluginViewer crash, all marked as duplicates of 213196 (created 5.Nov.2009), and 'RESOLVED/DUPLICATE' - but the base bug still has status 'UNCONFIRMED'. Please advise how I might best help pursue a bug which has already been reported and not yet closed or resolved. I assume that when the KDE Project decides bugs are obsolete or no longer worth working upon, it marks the bugs as 'CLOSED/WONTFIX' or something similar - and I would not re-report a bug marked in such a way. If possible, please point me to a URL which might educate me as to policy and practice at bugs.k.o ... I've been looking without success. I've read https://bugs.kde.org/docs/en/html/bug_page.html and indeed the whole of the Bugzilla Guide, but of course that doesn't cover any specific project policy. Thanks. Well, it is quite easy: we accept bug reports for versions that are considered current stable, which currently is KDE 4.8.5 and KDE 4.9.1, everything else is not maintained as we do not backport fixes to previous versions. If you use a distribution that doesn't ship these versions yet then you have two choices: wait for your distribution to update or change the distribution. As a user of Debian stable you should know that you are not using the latest software, though, and it never will, as they use different branches for that, e.g testing and unstable. The definition of "stable" and "unstable" is not necessarily the same in a distribution as for us upstream. Reporting bugs for obsolete versions is not helping as we need to know if these are reproducible with the latest stable versions. On Tuesday 18 Sep 2012 13:18:29 Myriam Schweingruber wrote: > --- Comment #3 from Myriam Schweingruber <myriam@kde.org> --- > Well, it is quite easy: we accept bug reports for versions that are > considered current stable, which currently is KDE 4.8.5 and KDE 4.9.1, > everything else is not maintained as we do not backport fixes to previous > versions. Okay - thanks for the policy clarification. Just to complete my picture: do you also not look at bugs in old code, even if it is clear the code still exists in the latest release ? > As a user of Debian stable you should know that you are not > using the latest software I do understand Debian release policy. I just hadn't properly understood KDE support policy. > Reporting bugs for obsolete versions is not helping as we need to know if > these are reproducible with the latest stable versions. Point taken. Should I attach no particular meaning then to the status of bugs such as 213196 ? Should I perhaps interpret 'UNCONFIRMED' as 'NOT-TO-BE-WORKED-UPON' rather than 'MORE-EVIDENCE-WOULD-BE-HELPFUL' ? This bug certainly does not have the appearance of a bug that has been tidily closed or resolved in any way, and as long as it retains the character of an ongoing issue I expect that unsuspecting users such as me will continue adding crash reports to it if the symptoms match. (https://bugs.kde.org/show_bug.cgi?id=213196) (In reply to comment #4) > On Tuesday 18 Sep 2012 13:18:29 Myriam Schweingruber wrote: > > > --- Comment #3 from Myriam Schweingruber <myriam@kde.org> --- > > Well, it is quite easy: we accept bug reports for versions that are > > considered current stable, which currently is KDE 4.8.5 and KDE 4.9.1, > > everything else is not maintained as we do not backport fixes to previous > > versions. > > Okay - thanks for the policy clarification. Just to complete my picture: do > you also not look at bugs in old code, even if it is clear the code still > exists in the latest release ? Well, we look at the shipped code, regardless of the age, if it is part of the latest release of course this is current. .. > > Should I attach no particular meaning then to the status of bugs such as > 213196 ? Should I perhaps interpret 'UNCONFIRMED' as > 'NOT-TO-BE-WORKED-UPON' > rather than 'MORE-EVIDENCE-WOULD-BE-HELPFUL' ? Nobody apparently had time to look at the bug, that is all. I updated the version field and changed the status accordingly. Thank you for mentioning it. |