https://bugs.kde.org/show_bug.cgi?id=516623

            Bug ID: 516623
           Summary: Data loss when navigating back and forth through the
                    crash reporting flow
    Classification: Applications
           Product: drkonqi
      Version First 6.6.0
       Reported In:
          Platform: Other
                OS: Linux
            Status: REPORTED
          Severity: normal
          Priority: NOR
         Component: general
          Assignee: [email protected]
          Reporter: [email protected]
  Target Milestone: ---

Created attachment 190034
  --> https://bugs.kde.org/attachment.cgi?id=190034&action=edit
Screenshot of the crash information form

SUMMARY
I was about to send the bug report after having written a very long description
of the problem, but then I had to press the back button to make a change a few
pages back. When I returned to the "Enter details about the crash", the entire
form was empty! I just lost everything I had written. Man, I'm pissed.

When I attempted to reproduce this data loss again, I couldn't. Something went
wrong the first time, but later it fixed itself.

I did notice that the "Distribution method" selector was unavailable the first
time (loading endlessly with a spinning animation), and I just happily wrote
all that bug description, unaware of the impending disaster.

STEPS TO REPRODUCE
1. Go through the crash report flow all the way to "Enter details about the
crash". Write something there. The distribution method should be unavailable
(loading endlessly).
2. Press the Back button to go back to "Your Knowledge" and change something
there.
3. Press the Forward button to return to "Enter details about the crash".

OBSERVED RESULT
The fields are empty.

EXPECTED RESULT
They should preserve whatever you had written there.

SOFTWARE/OS VERSIONS
Linux/KDE Plasma: openSUSE Tumbleweed
KDE Plasma Version: 6.6.0
KDE Frameworks Version: 6.23.0
Qt Version: 6.10.2

ADDITIONAL INFORMATION

-- 
You are receiving this mail because:
You are watching all bug changes.

Reply via email to