Comments not saved when navigating between tests

Bug #63293 reported by Adam Porter
20
This bug affects 1 person
Affects Status Importance Assigned to Milestone
Checkbox
Fix Released
Medium
David Murphy
checkbox (Ubuntu)
Fix Released
Medium
Unassigned
hwtest (Ubuntu)
Won't Fix
Undecided
Unassigned

Bug Description

If the network test fails, and you try again, and it fails again, the comments field is emptied. Quite annoying.

Revision history for this message
Paul Dufresne (paulduf) wrote :

Thank you for taking the time to report this bug and helping to make Ubuntu better. You reported this bug a while ago and there hasn't been any activity in it recently. We were wondering is this still an issue for you? Can you try with latest Ubuntu release? Thanks in advance.

Changed in hwdb-client:
assignee: nobody → dufresnep
status: New → Incomplete
Revision history for this message
Shirish Agarwal (shirishag75) wrote :

Right now on hardy & there is no candidate version of hwdb-client to try with. Will definitely update when I'm able to use the hwdb-client with Hardy.

Revision history for this message
Shirish Agarwal (shirishag75) wrote :

aptitude show hwdb-client
No current or candidate version found for hwdb-client
Package: hwdb-client
State: not a real package

Revision history for this message
Paul Dufresne (paulduf) wrote :

hwdb-client is the source package.
Need to search for one of the binary package:
hwdb-client-gnome or hwdb-client-kde (which I suppose indirectly install hwdb-client-common)

Revision history for this message
nglnx (nglnx) wrote :

We are closing this bug report because it lacks the information we need to investigate the problem, as described in the previous comments. Please reopen it if you can give us the missing information, and don't hesitate to submit bug reports in the future. To reopen the bug report you can click on the current status, under the Status column, and change the Status back to "New". Thanks again!

Changed in hwdb-client:
status: Incomplete → Invalid
Revision history for this message
Adam Porter (alphapapa) wrote :

With respect, in my opinion, a better way to handle a bug report like this would be to make sure the developer of the app sees it, because he should know if he's fixed the bug. It's enough trouble to report a bug in the first place; asking me to retest the app a year later, when the developer hasn't even acknowledged it, is discouraging. If my first report didn't get any results, why would a second one?

Changed in hwdb-client:
status: Invalid → New
Revision history for this message
RJ Clay (rjclay) wrote :

Which hwdb-client program did you see the problem with: hwdb-client-gnome or hwdb-client-kde?

Changed in hwdb-client:
status: New → Incomplete
Revision history for this message
RJ Clay (rjclay) wrote :

We are closing this bug report because it lacks the information we need to investigate the problem, as described in the previous comments. Please reopen it if you can give us the missing information, and don't hesitate to submit bug reports in the future. To reopen the bug report you can click on the current status, under the Status column, and change the Status back to "New". Thanks again!

Changed in hwdb-client:
status: Incomplete → Invalid
Revision history for this message
Adam Porter (alphapapa) wrote :

I believe it was the KDE client from Kubuntu.

Changed in hwdb-client:
status: Invalid → New
Revision history for this message
Andrea Corbellini (andrea.corbellini) wrote :

Thank you for taking the time to report this bug and helping to make Ubuntu better. You reported this bug a while ago and there hasn't been any activity in it recently. We were wondering if this is still an issue for you. Can you try with the latest Ubuntu release? Thanks in advance.

Changed in hwdb-client:
assignee: nobody → andrea-bs
status: New → Incomplete
Revision history for this message
Adam Porter (alphapapa) wrote :

(I'm basically repeating myself here...) Respectfully, please do not ask me to retest a bug like this (again!). If the developer or maintainer of the app has made no effort to fix this bug (which is a result of code that wasn't written), it still exists. Code must be written to handle this situation. Until that happens, it's still a bug. You're asking me to download the ISO and boot it up and start an install process just to test this, when it's apparent that no one's even tried to fix it.

Writing a form-letter "please test this again" response to this bug after what I've already posted on it is almost insulting. Debian doesn't handle bug reports like this.

Changed in hwdb-client:
status: Incomplete → New
Changed in hwdb-client:
assignee: andrea-bs → nobody
Revision history for this message
Malte Cornils (malte) wrote :

The package name has changed, since the functionality is now provided by the hwtest source package. There, this bug is reproducible. However, the comment field is emptied even after the first attempt.

affects: hwdb-client (Ubuntu) → hwtest (Ubuntu)
Changed in hwtest (Ubuntu):
status: New → Confirmed
Revision history for this message
David Murphy (schwuk) wrote :

hwdb-client was superceded by hwtest in 8.04, and subsequently renamed to checkbox for Jaunty. I can confirm that comments are *not* persisted when navigating between tests, not just for the network test. I will therefore alter the bug title accordingly.

Changed in checkbox:
importance: Undecided → Medium
status: New → Confirmed
Changed in hwtest (Ubuntu):
status: Confirmed → Won't Fix
Changed in checkbox (Ubuntu):
importance: Undecided → Medium
status: New → Confirmed
summary: - Comments not saved if network test fails
+ Comments not saved when navigating between tests
Revision history for this message
Malte Cornils (malte) wrote :

I have also had a cursory look at the old hwtest source (I guess checkbox is not so different) - there, I have located the position where the textbox is cleared. Attached is a patch that disables this clearing or overwriting of the textview. However, there are obviously side effects and it's just meant as showing which area of the code should be fixed - a checkbox developer should have a look at how to fix this problem in a clean way while preserving the textview clearing on passing to the next test and preserving the copying of test result data into the textview (maybe as an append operation).

David Murphy (schwuk)
Changed in checkbox:
assignee: nobody → David Murphy (schwuk)
milestone: none → 0.9-featurefreeze
David Futcher (bobbo)
tags: added: patch-forwarded-upstream
tags: added: patch-needswork
removed: patch-forwarded-upstream
Revision history for this message
Brendan Donegan (brendan-donegan) wrote :

This doesn't happen anymore, so Fix Released

Changed in checkbox (Ubuntu):
status: Confirmed → Fix Released
Changed in checkbox:
status: Confirmed → Fix Released
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Duplicates of this bug

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.