After an evaluation, GNOME has moved from Bugzilla to GitLab. Learn more about GitLab.
No new issues can be reported in GNOME Bugzilla anymore.
To report an issue in a GNOME project, go to GNOME GitLab.
Do not go to GNOME Gitlab for: Bluefish, Doxygen, GnuCash, GStreamer, java-gnome, LDTP, NetworkManager, Tomboy.
Bug 657480 - bad link in error dialog
bad link in error dialog
Status: RESOLVED NOTABUG
Product: gparted
Classification: Other
Component: application
0.7.0
Other Linux
: Normal normal
: ---
Assigned To: gparted maintainers alias
gparted maintainers alias
Depends on:
Blocks:
 
 
Reported: 2011-08-26 22:43 UTC by Ulf Zibis
Modified: 2011-09-03 15:44 UTC
See Also:
GNOME target: ---
GNOME version: ---


Attachments
Screen shot (358.65 KB, image/png)
2011-08-28 16:53 UTC, Ulf Zibis
Details

Description Ulf Zibis 2011-08-26 22:43:49 UTC
In error message there is stated to post the details log to http://gparted.org/savedetails.
This page doesn't exist.

After confirming the dialogue, additionally, after click on the triangle of an item in the details list of the "pending operations" dialogue, the dialogue is completely in-responsive on Ubuntu 11.04, i.e. "Save Details" doesn't work any more. I had to kill the process and start GParted again.
Comment 1 Curtis Gedak 2011-08-27 20:19:29 UTC
Unless I am mistaken, the GParted program prompts that instructions to save the detail log can be found at the following URL:

     http://gparted.org/save-details.htm

There is no "http://gparted.org/savedetails".

If you find that the program provides a different URL path, then please do take a screen shot and re-open this bug report and provide additional information.
Comment 2 Ulf Zibis 2011-08-27 20:36:00 UTC
Seems, that I remembered the URL incorrectly, thanks.
As the screen was frozen, I hadn't any chance to review the correct spelling, so I came to "bad link", as I couldn't find any link on your web page gparted.org. Would be nice to have!

Anyway, the "dialogue is completely in-responsive"-part is a bug to me, so why closing this issue?
Comment 3 Curtis Gedak 2011-08-28 15:31:53 UTC
Sorry, I thought the problem was the bad link in the error dialog as stated in the title.

Do you have a reproducible set of steps to recreate the "dialogue is completely in-responsive" problem?

If so please do re-open this bug report and post these steps here.
Comment 4 Ulf Zibis 2011-08-28 16:51:09 UTC
- run resize as descripted in bug 657118
- continue as in this description above until "open details" + "open item" in details list.
I could reproduce it 2 times
A 3rd time, I opened the details while operating (see attachment), but after the error was detected, "OK" didn't work, even as "Schließsen" of the underlying dialogue, but "Details speichern" worked fine. I again had to kill the GParted process.
A 4th time, unexpectedly the operation succeeded, regardless the inconsistency with the backup sector.
Comment 5 Ulf Zibis 2011-08-28 16:53:33 UTC
Created attachment 194975 [details]
Screen shot
Comment 6 Curtis Gedak 2011-08-31 16:50:00 UTC
Thanks Ulf for performing more testing.  Unfortunately I am unable to reproduce the problem using the steps you describe in comment #4.

My suspicion is that there is a problem with the computer hardware you are using.

Are you able to test the device to see if it is failing or somehow not
maintaining a good connection?
Comment 7 Ulf Zibis 2011-09-02 23:12:50 UTC
(In reply to comment #6)
> My suspicion is that there is a problem with the computer hardware you are
> using.
> 
> Are you able to test the device to see if it is failing or somehow not
> maintaining a good connection?

See my comments on bug 657118.

But anyway, I still think GParted or Ubuntu should not freeze in some way and the dialogues should stay responsive on any provided action, if an error occurs.
Comment 8 Curtis Gedak 2011-09-03 15:44:51 UTC
Unfortunately when hardware errors occur just about anything can happen.  When I say hardware errors, these can be memory errors, disk input/output errors, bad cable connections, etc.

Since I am unable to reproduce these errors and have not heard from anyone else with this problem I highly suspect that the problem encountered is hardware related and not software related.

Since we are currently discussing hardware diagnosis in bug #657118, I am going to close this bug for now.  If / when we discover the root cause of bug #657118 then we can re-consider whether this bug should be re-opened.