GNOME Bugzilla – Bug 743825
gparted displaying incorrect dialog title: libparted bug found!
Last modified: 2015-03-23 17:47:37 UTC
Created attachment 295911 [details] screenshot of error message using ubuntu 14.04.1 fully updated. ran the dd command on a new kingston 8gig flashdrive. to mount the .ISO mint linux 17.1, which it did. placed flashdrive in other computer and it displayed "1234f:" on an otherwise blank screen. ejected and placed back into the ubuntu machine. ran gparted from bash it yeilded an error message about bug found in libparted. would not repair the flashdrive. flashdrive is useless, who cares $5.00 my gparted is for the first time, acting weird with flashdrives. fixmycar69@yahoo.com
i have screenshots of all messages and commands was 3 error messages all together. can send the suspect kingston flashdrive to you for examination. i was rather shocked after 3 years of linux, ubuntu. and using gparted daily; to have it not work. sorry if i broke it, please fix. Dave
Hi Dave, 1) GParted has given the wrong title to the dialog and is reporting that libparted encountered an error. The dialog should be: Libparted Error (-) Input/output error write to /dev/sdf 2) The Linux kernel encountered an error, probably hardware, writing to /dev/sdf. I can only point you to at the kernel log to look for the errors at the time this occurred. (Not that familiar with Ubuntu and the logging is configured differently, but the errors should be in /var/log/kern.log). Thanks, Mike
So what is the actual issue here? Can someone set a proper bug summary please?
Hi André, As per my previous update, there are 2 issues: * Hardware error generated when writting to flashdrive * GParted titles this as a libparted bug instead of an error message
Created attachment 296018 [details] [review] Correctly report libparted exceptions (v1) Hi Curtis, As we now have a user report of this bug I want to push my fix via this report rather than as an unlabelled patch in bug 743181. For the record I was getting this: Libparted Bug Found! (-) Invalid argument during seek for read on /dev/md1 [ Retry ] [ Cancel ] [ Ignore ] After investigation found that GParted was asking libparted to read from sector -1. Libparted was actually reporting an error but GParted was incorrectly displaying this as a bug. Found when trying to copy whole disk device file system while coding in bug 743181. This lead to the discovery of bug 742920 "GParted internal copy is overstepping partition boundaries". Thanks, Mike
Thank you Mike for identifying the two issues in comment #4, and for providing a patch to correct the title for the libparted message. The code for the patch in comment #5 looks good to me. I tested the patch with a disk image with a GPT partitition table and then grew the image so that the backup partition table was no longer at the end of the image. The correct "Libparted Warning" was shown for before and after this patch. The patch in comment #5 has been committed to the git repository for inclusion in the next release of GParted. The relevant git commit can be viewed at the following link: Correct dialog title displaying libparted exceptions (#743825) https://git.gnome.org/browse/gparted/commit/?id=9294a10fbdc68f0eb669cb7357033f022c4ef135 Dave, Thank you for reporting this problem. While I believe the problem with GParted displaying the incorrect libparted message has been fixed, I'm afraid your flash drive appears to be suffering from hardware issues. If you are comfortable applying patches and compiling, then please test the patch in comment #5 to see if GParted now displays the proper message (for example, not "Libparted Bug"). If not, then no worries. I do think at least the problem with the libparted message is now fixed. Curtis
Change title from: gparted displaying dialog: libparted bug found! to: gparted displaying incorrect dialog title: libparted bug found!
This enhancement was included in the GParted 0.22.0 release on March 23, 2015.