I am currently running Ubuntu 12.04.1 LTS Precise, kernel
3.2.0-29-generic, Gparted version: 0.11.0-2, if I have legacy floppy
enabled in my bios I still have the problem of Gparted scanning devices
forever. I will disable legacy diskette in my bios to get it work.
--
You received this bug
** Changed in: gparted (Ubuntu)
Status: Triaged = Fix Released
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/910379
Title:
Gparted does not start and continues to scan devices
To manage
The patch to GParted mentioned in comment #26 is included in the
upstream release of GParted 0.12.1.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/910379
Title:
Gparted does not start and continues
After checking again, the patch is actually first included in upstream
GParted 0.12.0. Hence this patch is not yet part of Precise Pangolin,
which is using GParted 0.11.0-2.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
I have the problem on precise with parted 2.3-8ubuntu5
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/910379
Title:
Gparted does not start and continues to scan devices
To manage notifications
Workaround disabling floppy in bios worked on precise with parted
2.3-8ubuntu5
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/910379
Title:
Gparted does not start and continues to scan devices
To
@dino99, how long did it take for the blkid command to run?
When you performed the test, was your BIOS configured to indicate a floppy
drive was present when there actually was no physical floppy drive?
The patch mentioned above was included in GParted 0.12.0 released
upstream on February 21,
@Curtis
bios config : floppy off
no floppy reader into that system
blkid request send instantly (1/2 second)
do you need floppy activated into the bios ? then and other blkid test ?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
I remember that i've already made the blkid request a few days back with
the floppy setting activated into the bios. The blkid request took about
4 minutes to succeed.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
Curtis, 0.11.0 still runs blkid -p, not -c, doesn't it? That was
changed in 0.12.0.
Dino, does the status bar indicate what device it is trying to scan?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
@Phillip
test made with 0.11.0-1 on Precise i386:
- while scanning : the gparted screen is all greyed except this orange scan bar
- when the scan is done: it first select /dev/sda , then i can switch to sdb or
sdc
so its ok if i do it with floppy setting deactivated into the bios. But
my main
does the status bar indicate what device it is trying to scan?
no nothing till the scan end
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/910379
Title:
Gparted does not start and continues
Ok, then this is fixed in parted 0.12.0.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/910379
Title:
Gparted does not start and continues to scan devices
To manage notifications about this bug go
@dino99. Thanks for running the extra tests. The concern was that
blkid -c /dev/null would take a long time on a BIOS that was
incorrectly configured to indicate it had a floppy device when no
physical device was present. Phillip is correct, this is fixed in
GParted 0.12.0.
@Phillip, GParted
@Curtis
oem@oem-desktop:~$ sudo blkid -c /dev/null
sudo: command not found
root@oem-desktop:~# blkid -c /dev/null
/dev/sda1: LABEL=LTS32 UUID=0eea5390-114c-4ee2-815f-a3cfca716c04
TYPE=ext4
/dev/sda2: UUID=0a9ca7f0-6eeb-4b21-b70f-670fa600de16 TYPE=swap
/dev/sda3: LABEL=lhom
** Changed in: gparted
Status: Confirmed = Fix Released
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/910379
Title:
Gparted does not start and continues to scan devices
To manage
The upstream patch for the change on blkid invocation can be found at
the following link:
Fix long scan problem when BIOS floppy setting incorrect
http://git.gnome.org/browse/gparted/commit/?id=18f863151c82934fe0a980853cc3deb1e439bec2
This patch is planned for inclusion in the upstream GParted
@Curtis
is the cached blkid results always up-to-dated ? or does the users
need to be warned to refresh it then restart gparted again ?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/910379
Title:
@dino99. GParted performs a udevadm settle before re-reading the
blkid cache. Hence the cache should already have been updated before
GParted proceeds with the device refresh.
In my testing I did find this to be the case and to work properly.
--
You received this bug notification because you
@Curtis
ok thanks, it was only a doubt of my own, in case it should be usefull
before getting your patch. Waiting the new package, no hurry anyway.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
@dino99. To confirm that the problem is with blkid, would you be able
to try running the following command with your computer setup?
sudo blkid -c /dev/null
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
Got the same issue on Precise i386 with 0.11 version:
Its the first time i try to use gparted since we got 0.11 version on Precise
i386. Loading it from the menu (gnome-classic) fails with this error:
- the first time, a greyed parted dialogbox start to scan to find hdds (have 2
pata + 1 sata)
on Precise, packages used are:
- parted 2.3-8ubuntu3
- gparted 0.11.0-1
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/910379
Title:
Gparted does not start and continues to scan devices
To manage
Ahh yes, gparted also needs the change to how it invokes blkid.
** Changed in: gparted (Ubuntu)
Status: Fix Released = Triaged
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/910379
Title:
** Changed in: gparted (Ubuntu)
Status: In Progress = Fix Released
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/910379
Title:
Gparted does not start and continues to scan devices
To manage
This bug was fixed in the package parted - 2.3-8ubuntu2
---
parted (2.3-8ubuntu2) precise; urgency=low
* Add 16-dos-partitions.patch: Fix parted to correctly handle
more than 16 partitions on dos partition tables.
* Add dm-part-sync.patch: Backport fix to allow modifying
When you tested, did you still have your BIOS incorrectly set to say a
floppy drive is present when there really isn't a floppy drive
physically installed?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
Yes, I checked it immediatly when I saw Gparted work.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/910379
Title:
Gparted does not start and continues to scan devices
To manage notifications about
Based on that then I think this bug can be closed.
I do plan to keep the change to GParted since it does not appear to
cause any harm, and it will offer a slight performance improvement when
GParted rescans disk devices.
--
You received this bug notification because you are a member of Ubuntu
ok thank you.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/910379
Title:
Gparted does not start and continues to scan devices
To manage notifications about this bug go to:
** Bug watch added: GNOME Bug Tracker #667511
https://bugzilla.gnome.org/show_bug.cgi?id=667511
** Also affects: gparted via
https://bugzilla.gnome.org/show_bug.cgi?id=667511
Importance: Unknown
Status: Unknown
--
You received this bug notification because you are a member of
** Also affects: parted (Ubuntu)
Importance: Undecided
Status: New
** Changed in: parted (Ubuntu)
Status: New = In Progress
** Changed in: parted (Ubuntu)
Assignee: (unassigned) = Phillip Susi (psusi)
--
You received this bug notification because you are a member of
** Changed in: gparted
Status: Unknown = Confirmed
** Changed in: gparted
Importance: Unknown = Medium
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/910379
Title:
Gparted does not start
Hello Curtis,
First thanks for your help.
I think I made a bit of a mess.
I wasn't able to start my PC, for some reason I still have to find out, it
freezed on checking battery state..., but this is not your problem.
The fact is that I installed today's Precise Pangolin iso on the sda5 partition
** Branch linked: lp:~psusi/ubuntu/precise/parted/fixloop
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/910379
Title:
Gparted does not start and continues to scan devices
To manage notifications
On 1/5/2012 4:05 PM, Curtis Gedak wrote:
Phillip, are you able to bring this problem with blkid searching non-
existent floppy drive to the attention of the right people?
I don't think it is considered a bug by anyone. If the bios claims you
have a floppy, then the kernel thinks you have a
On 1/6/2012 11:41 AM, Curtis Gedak wrote:
Regarding waiting for udev to update it's cache, do you think a udevadm
settle would be sufficient before a call to blkid to ensure that has
up-to-date information?
Yes, that should do it.
--
You received this bug notification because you are a
Since GParted already includes a call to udevadm settle I removed the
-c /dev/null and tested with ubuntu 11.04 and 10.04. Both of these
worked correctly. :-)
As such I have committed the following patch to the upstream GParted
code repository:
Fix long scan problem when BIOS floppy setting
Hello Curtis,
I tried to retrieve and compile GParted from the git source code repository,
but it needs glib-gettext = 2.2.0 on Ubuntu Precise I have 0.18.1.
I tried to install 2.2.0 but I'm having other problems, I'll try to work it out
so I can test the new patch for you.
--
You received
Sorry couldn't finish installation, during make got this output and do
not know how to fix it:
In file included from ../include/../include/../include/../include/i18n.h:9:0,
from ../include/../include/../include/Utils.h:28,
from
Perhaps you are simply missing a dependency.
Would you please try the following command to ensure the dependencies
are installed. This command last tested with Ubuntu 11.10 if I recall
correctly.
sudo apt-get install build-essential e2fsprogs uuid uuid-dev \
Here are the last lines of sudo strace -e trace=file
/usr/sbin/gpartedbin (I put file instead of files, files gave me an
error):
open(/usr/local/share//mime/aliases, O_RDONLY) = -1 ENOENT (No such file or
directory)
open(/usr/local/share//mime/subclasses, O_RDONLY) = -1 ENOENT (No such file
If of any help I ran sudo strace /usr/sbin/gpartedbin these are the
last lines of output:
read(4, 0x7fff494d46a0, 16) = -1 EAGAIN (Resource temporarily
unavailable)
poll([{fd=3, events=POLLIN|POLLOUT}], 1, -1) = 1 ([{fd=3, revents=POLLOUT}])
writev(3, [{5\30\4\0\35\206 \4\4\0
Well I was hoping to see an open() in there on /dev/fd to confirm that
it is hanging up on that floppy. I'm not sure why it would change
between releases of Ubuntu, but if the floppy is the problem, then this
is at its core a hardware configuration issue. It doesn't really make
sense to bother
Carla, do you have the dmraid package installed?
If so, would you please try the following command and let us know the
results:
sudo dmraid -sa -c
This is to test if scanning of the floppy drive is related to the dmraid
command.
--
You received this bug notification because you are a
Yes I have dmraid installed
This is the result:
charlie@charlie02:~$ sudo dmraid -sa -c
[sudo] password for charlie:
no raid disks
charlie@charlie02:~$
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
Okay, that confirms that dmraid is not part of the problem. I didn't
think it was, but it is always good to check.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/910379
Title:
Gparted does not
On 1/5/2012 12:18 PM, Curtis Gedak wrote:
Okay, that confirms that dmraid is not part of the problem. I didn't
think it was, but it is always good to check.
What about kpartx?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
I do not have kpartx installed.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/910379
Title:
Gparted does not start and continues to scan devices
To manage notifications about this bug go to:
Thanks for checking kpartx. GParted removed use of kpartx in version
0.8.1, which was adopted in Oneiric Ubuntu (11.10).
Carla, would you be able to provide the results of the following
command?
sudo blkid -c /dev/null
--
You received this bug notification because you are a member of
This is the output of sudo blkid -c /dev/null:
charlie@charlie02:~$ sudo blkid -c /dev/null
/dev/zram0: UUID=22899080-92c1-4a74-9265-b7e580a6239e TYPE=swap
/dev/sda1: UUID=1ab3c2d9-9b38-4502-9e2a-434ec6833169 TYPE=ext4
/dev/sda2: UUID=7559004b-3edf-46f5-8faa-723082912704 TYPE=ext4
/dev/sda3:
Aha! So the delay is due to calling blkid.
Phillip, are you able to bring this problem with blkid searching non-
existent floppy drive to the attention of the right people?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
On 1/5/2012 3:20 PM, Carla Sella wrote:
This is the output of sudo blkid -c /dev/null:
Say Curtis, why do you use -c /dev/null? Why not let blkid use its
cache to speed things up?
The only thing is that I had to wait like 15 minutes for this output,
I wanted to press ctrl+c to get out, but
Phillip,
In the past if I changed the label of a partition with GParted and then
called blkid, I received the cached result which was the old label.
That is why I used the -c /dev/null to force blkid to re-read the
information.
I have not tested to see if blkid still has this same behaviour.
--
On 1/5/2012 4:05 PM, Curtis Gedak wrote:
Phillip, are you able to bring this problem with blkid searching non-
existent floppy drive to the attention of the right people?
I don't think it is considered a bug by anyone. If the bios claims you
have a floppy, then the kernel thinks you have a
Hi Philipp,
I cannot se what devices it's trying to scan.
I launched gparted from terminal, but there's no output, see attached immage.
I have this output on /var/log/syslog, but these messages occur also
when gparted is closed so I'm not sure they are caused by gparted:
Jan 4 11:30:07
Hello Curtis,
This is the output while Gparted is running:
root@charlie02:/var/log# ps -ef | egrep -i dosfsck|ntfsresize
root 7889 7535 0 11:33 pts/000:00:00 egrep -i dosfsck|ntfsresize
root@charlie02:/var/log#
On this PC I do not have NTFS or FAT filesystems:
It looks like it is trying to scan your floppy drive, and I assume you
do not actually have one. You need to configure your bios to not think
you have a floppy drive if you don't actually have one.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is
Great!
I disabled Legacy diskette in my PC's BIOS and now gparted works.
I have one argument though:
Before precise pangolin gparted used to work also with legacy diskette enabled
in my BIOS.
Can't this be fixed ?
Thank you.
--
You received this bug notification because you are a member of
The problem with GParted taking a long time scanning a non-existent floppy
drive is identified in the FAQ.
http://gparted.org/faq.php#faq-11
The relevant bug report is:
Bug 351753 - missing floppy causes loop on scan devices
https://bugzilla.gnome.org/show_bug.cgi?id=351753
The fix back then
Can you turn the floppy back on and run sudo strace -e trace=files
/usr/sbin/gpartedbin and post the last 15 or so lines?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/910379
Title:
Gparted does
At the bottom of the window, it should specify what device it is
scanning. Can you tell me what that is?
** Changed in: gparted (Ubuntu)
Status: New = Incomplete
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
Would you please also provide the output from the following command
while GParted is scanning:
ps -ef | egrep -i dosfsck|ntfsresize
If the problem occurs with NTFS or FAT file systems, then sometimes
running a disk check or defragmenting the file system can fix the
problem.
--
You received
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/910379
Title:
Gparted does not start and continues to scan devices
To manage notifications about this bug go to:
64 matches
Mail list logo
