My main concern here is not to fix "my" problem locally but to do what I can to ensure a global fix is applied on a problem that I (and others) have identified. So in essence my effort is to seek resolution on a problem that is inherent to the operating system rather than find a work-around that will keep the problem from surfacing on my personal computer.
So my question is, what follow-up, if any, should I be doing to ensure that this happens appropriately?
This is the first time I have participated in a beta test for Kubuntu (or any other Linux distro for that matter). Years ago I participated in a beta test for a commercial application. My responsibilities were much more clear to me then although I admit that I did not run into anything that qualified as a bug report -- all of my feedback was positive.
The issue that has prompted me to seek this advice has already been mentioned on this forum and while I am not seeking resolution in this thread, I do want to learn how to be a better beta-tester so that my time is truly spent helping the Ubuntu community resolve an issue prior to release. But I like specifics and assume that others will too so as reference I am providing a couple links.
Forum Discussion: firefox crashes X
http://kubuntuforums.net/forums/inde...opic=3110792.0
Bug Report: [Lucid]NoScript crashes Firefox, crashes X-session
https://bugs.launchpad.net/ubuntu/+s...er/+bug/551754
I have also entered a bug report in KDE space but have since determined (as did the KDE contact) that this is particular issue is upstream of KDE and most likely xorg-server as the Launchpad team has so far determined. The Launchpad entry shows an update of some troubleshooting that I have done as well. For more information please see https://bugs.launchpad.net/ubuntu/+s...754/comments/8.
Am I correct in assuming this is a problem that is more global than my system (hardware and software and user) and that the nature of the problem would qualify as a serious issue? I say 'serious' because were a user to have this happen in the release version, he/she could quite likely suffer data loss for any unsaved application files that were open at the time of the crash.
Again, although I would really like to see this specific issue get resolved, my question is more general in nature. Have I done everything I can to see that a problem is sent to the right place so that it can be properly addressed? Am I correct in assuming a sense of ownership of the problem to the point of seeking follow-up or should I just file it and forget it until someone gets back to me?
Quite frankly, were this an issue that I needed to not happen I would certainly seek an alternative solution until it was fixed (and I don't use the beta for 'production' usage -- I use a stable distro for those activities). But I ask this in the spirit of beta-testing specifically and in general for bug-reporting of released software.
Many thanks!!
update: The KDE Bugzilla report.
https://bugs.kde.org/show_bug.cgi?id=233988
So my question is, what follow-up, if any, should I be doing to ensure that this happens appropriately?
This is the first time I have participated in a beta test for Kubuntu (or any other Linux distro for that matter). Years ago I participated in a beta test for a commercial application. My responsibilities were much more clear to me then although I admit that I did not run into anything that qualified as a bug report -- all of my feedback was positive.
The issue that has prompted me to seek this advice has already been mentioned on this forum and while I am not seeking resolution in this thread, I do want to learn how to be a better beta-tester so that my time is truly spent helping the Ubuntu community resolve an issue prior to release. But I like specifics and assume that others will too so as reference I am providing a couple links.
Forum Discussion: firefox crashes X
http://kubuntuforums.net/forums/inde...opic=3110792.0
Bug Report: [Lucid]NoScript crashes Firefox, crashes X-session
https://bugs.launchpad.net/ubuntu/+s...er/+bug/551754
I have also entered a bug report in KDE space but have since determined (as did the KDE contact) that this is particular issue is upstream of KDE and most likely xorg-server as the Launchpad team has so far determined. The Launchpad entry shows an update of some troubleshooting that I have done as well. For more information please see https://bugs.launchpad.net/ubuntu/+s...754/comments/8.
Am I correct in assuming this is a problem that is more global than my system (hardware and software and user) and that the nature of the problem would qualify as a serious issue? I say 'serious' because were a user to have this happen in the release version, he/she could quite likely suffer data loss for any unsaved application files that were open at the time of the crash.
Again, although I would really like to see this specific issue get resolved, my question is more general in nature. Have I done everything I can to see that a problem is sent to the right place so that it can be properly addressed? Am I correct in assuming a sense of ownership of the problem to the point of seeking follow-up or should I just file it and forget it until someone gets back to me?
Quite frankly, were this an issue that I needed to not happen I would certainly seek an alternative solution until it was fixed (and I don't use the beta for 'production' usage -- I use a stable distro for those activities). But I ask this in the spirit of beta-testing specifically and in general for bug-reporting of released software.
Many thanks!!
update: The KDE Bugzilla report.
https://bugs.kde.org/show_bug.cgi?id=233988