Activity log for bug #1622313

Date Who What changed Old value New value Message
2016-09-11 10:24:34 sudodus bug added bug
2016-09-11 10:24:34 sudodus attachment added screenshot-lubuntu-desktop-xenial-i386-with-gparted.png https://bugs.launchpad.net/bugs/1622313/+attachment/4738595/+files/screenshot-lubuntu-desktop-xenial-i386-with-gparted.png
2016-09-11 10:47:35 Launchpad Janitor gparted (Ubuntu): status New Confirmed
2016-09-11 10:52:14 JackT bug added subscriber JackT
2016-09-11 11:02:10 Ubuntu QA Website tags apport-bug i386 xenial apport-bug i386 iso-testing xenial
2016-09-11 11:28:31 sudodus attachment added screenshot-ubuntu-14.04.1-desktop-amd64-with-gparted.png https://bugs.launchpad.net/ubuntu/+source/gparted/+bug/1622313/+attachment/4738647/+files/screenshot-ubuntu-14.04.1-desktop-amd64-with-gparted.png
2016-09-11 11:48:03 sudodus attachment added screenshot-ubuntu-16.04.1-desktop-amd64-with-gparted-1.png https://bugs.launchpad.net/ubuntu/+source/gparted/+bug/1622313/+attachment/4738664/+files/screenshot-ubuntu-16.04.1-desktop-amd64-with-gparted-1.png
2016-09-11 11:49:16 sudodus attachment added screenshot-ubuntu-16.04.1-desktop-amd64-with-gparted-2.png https://bugs.launchpad.net/ubuntu/+source/gparted/+bug/1622313/+attachment/4738665/+files/screenshot-ubuntu-16.04.1-desktop-amd64-with-gparted-2.png
2016-09-11 11:54:38 sudodus description I am testing in a live system and looking at the very drive, from which it is booted, the current daily iso file of Lubuntu Xenial i386 (post 16.04.1 LTS). The problem is that the file system cannot be identified, and several end users may (and will) think that the USB boot drive is damaged. But it works, it is cloned, which is the straightforward method to create a boot drive from a hybrid iso file. this issue was worse in previous versions, where gparted would complain about an error; now it is at least seeing the partition. The next step is that it can see the file system too. lsblk can see it, as illustrated by the following command line (in a wide terminal window), sudo lsblk -fm The attached screenshot illustrates the problem, and shows that it affects the text mode program parted too. ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: gparted 0.25.0-1 ProcVersionSignature: Ubuntu 4.4.0-38.57-generic 4.4.19 Uname: Linux 4.4.0-38-generic i686 ApportVersion: 2.20.1-0ubuntu2.1 Architecture: i386 CasperVersion: 1.376 CurrentDesktop: LXDE Date: Sun Sep 11 10:10:21 2016 LiveMediaBuild: Lubuntu 16.04.1 LTS "Xenial Xerus" - Beta i386 (20160909) ProcEnviron: TERM=xterm PATH=(custom, no user) XDG_RUNTIME_DIR=<set> LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: gparted UpgradeStatus: No upgrade log present (probably fresh install) I am testing in a live system and looking at the very drive, from which it is booted, the current daily iso file of Lubuntu Xenial i386 (post 16.04.1 LTS). The problem is that the file system cannot be identified, and several end users may (and will) think that the USB boot drive is damaged. But it works, it is cloned, which is the straightforward method to create a boot drive from a hybrid iso file. this issue was worse in previous versions, where gparted would complain about an error; now it is at least seeing the partition. The next step is that it can see the file system too. lsblk can see it, as illustrated by the following command line (in a wide terminal window), sudo lsblk -fm The attached screenshot illustrates the problem, and shows that it affects the text mode program parted too. ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: gparted 0.25.0-1 ProcVersionSignature: Ubuntu 4.4.0-38.57-generic 4.4.19 Uname: Linux 4.4.0-38-generic i686 ApportVersion: 2.20.1-0ubuntu2.1 Architecture: i386 CasperVersion: 1.376 CurrentDesktop: LXDE Date: Sun Sep 11 10:10:21 2016 LiveMediaBuild: Lubuntu 16.04.1 LTS "Xenial Xerus" - Beta i386 (20160909) ProcEnviron:  TERM=xterm  PATH=(custom, no user)  XDG_RUNTIME_DIR=<set>  LANG=en_US.UTF-8  SHELL=/bin/bash SourcePackage: gparted UpgradeStatus: No upgrade log present (probably fresh install) Edit: After some testing I found that the current i386 versions behave in a similar way as Xenial. But the current amd64 (64-bit) versions are more severely affected by this bug. It is much worse in Trusty, but also bad in Xenial as illustrated by screenshots in comments #6 and #7. This behaviour will really confuse new users of Ubuntu and the Ubuntu flavours.
2016-09-11 12:27:14 Alberto Salvia Novella bug watch added https://bugzilla.gnome.org/show_bug.cgi?id=771244
2016-09-11 12:27:14 Alberto Salvia Novella bug task added gparted
2016-09-11 12:28:50 Alberto Salvia Novella gparted (Ubuntu): importance Undecided High
2016-09-11 12:29:21 Alberto Salvia Novella nominated for series Ubuntu Xenial
2016-09-11 12:34:20 Alberto Salvia Novella gparted (Ubuntu): status Confirmed Triaged
2016-09-11 16:07:15 Bug Watch Updater gparted: status Unknown Confirmed
2016-09-11 16:07:15 Bug Watch Updater gparted: importance Unknown High
2017-02-14 22:08:37 Bug Watch Updater gparted: status Confirmed Fix Released
2017-08-02 14:56:04 Mantas Kriaučiūnas bug added subscriber Mantas Kriaučiūnas
2017-08-02 20:02:39 Launchpad Janitor gparted (Ubuntu): status Triaged Fix Released
2017-08-03 05:59:05 sudodus attachment added gparted-recognizes-iso9660.png https://bugs.launchpad.net/ubuntu/+source/gparted/+bug/1622313/+attachment/4926374/+files/gparted-recognizes-iso9660.png