I just found a workaround for this issue, and it works in kubuntu 16.04.
The workaround steps are:
1. Edit /etc/xdg/menus/kf5-applications.menu
2. After add the following line:
applications-merged
3. Save the file, and you might need to reboot to see the updated menus.
This problem was re
Would you be able to provide the output from the following three
commands?
sudo fdisk -l -u
where one of the options is a lower case "L" and not the number one.
sudo parted /path-to-your-device unit s print
where /path-to-your-device is something like /dev/sda.
sudo blkid
--
You receiv
I don't have a 4K monitor, but the following steps fixed video tearing
with Kubuntu 16.04 on my Intel i7-2600k CPU with integrated Intel HD
3000 Graphics.
Edit /etc/environment and add the following lines:
__GL_YIELD="USLEEP"
KWIN_TRIPLE_BUFFER=0
KWIN_USE_BUFFER_AGE=0
Save the file and reboot.
@Nishihama ,
This issue is caused when there is less than two unallocated sectors
between logical partitions. The Extended Boot Record is stored in the
unallocated sector area. In your situation the problem arises with sda5
and sda6 sda5.
332625887 end of sda5
332625888 start of sda6
The sour
GParted 0.8.1 is quite old. Would you be able to try with the latest
version (currently 0.12.0)?
The easiest way to do this would be to download a copy of GParted Live
0.12.0-5, and burn this to a CD or write it to a USB. Then you can boot
from this media and test to see if the problem still occ
With regards to the problem with the NTFS file system, this should be
able to be fixed by booting into Windows, running "chkdsk /f" on the
drive, and rebooting twice.
Regarding the problem with GParted hanging, it would be helpful if you
could test GParted 0.12.0 first to see if the problem still
** Bug watch added: GNOME Bug Tracker #112622
https://bugzilla.gnome.org/show_bug.cgi?id=112622
** Also affects: sound-juicer via
https://bugzilla.gnome.org/show_bug.cgi?id=112622
Importance: Unknown
Status: Unknown
--
You received this bug notification because you are a member o
It is certainly possible that there could be a problem with large
amounts of error output. This previously occurred with copying huge
NTFS partitions; however, this problem was fixed in GParted version
0.5.2.
Unfortunately I have been unable to recreate the problem you
experienced. Hence we do n
@Manish-Raj, after re-reading this bug report I noticed that you did
include the log of output from ntfsresize. If someone has time they
might be able to feed this into GParted to try to recreate the error.
Would you be able to provide some of the specifications of the computer
on which you enter
> Maybe the create menu option just needs to be enabled regardless
> of what you have selected.
This might be a good solution to this request.
The create "New" partition menu would always be available.
There would be three scenarios to handle:
A) If the user had pre-selected unallocated space.
The current selection is important because there can be more than one
section of the disk with free unallocated space.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to the bug report.
https://bugs.launchpad.net/bugs/32484
Title:
selection sh
The only thing that I can think of that does not violate the GNOME HIG
is to perhaps default to selecting free space on the default selected
drive.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to the bug report.
https://bugs.launchpad.net/bugs
That would work -- selecting the largest free space if no free space is
already selected.
Two situations could still arise that would need handling:
A) The user had pre-selected a file system with a partition.
In this case the "New" menu and toolbar button could be disabled.
OR
I think we are in agreement. The part that is required is to default
select the free space.
#1 and #4 are already in the code. :-)
Bodsda, are you working to fix the patch in comment #2, or otherwise to
implement a default selection of free unallocated space?
--
You received this bug notifica
This problem was resolved in GParted 0.9.1.
The relevant upstream bug report is:
Bug 655215 - NTFS partition resize fails
https://bugzilla.gnome.org/show_bug.cgi?id=655215
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.
** Bug watch added: GNOME Bug Tracker #601239
https://bugzilla.gnome.org/show_bug.cgi?id=601239
** Also affects: gparted via
https://bugzilla.gnome.org/show_bug.cgi?id=601239
Importance: Unknown
Status: Unknown
--
You received this bug notification because you are a member of Ubu
Public bug reported:
In some situations when shrinking, moving, and copying linux-swap, the
linux-swap partition is no longer recognized as linux-swap.
For example, try moving (no size change) a linux-swap logical partition
to the right and applying the change. The result, after GParted rescans
Thanks Seth for doing the hard work of finding the root cause of the
problem and for developing a patch to resolve the problem.
Also thank you Luca Bruno for subscribing me to this bug report.
I think that this problem is the same as the bug #609477:
gpartedbin crashed with signal 5 in Glib:
> Are you going to replace all those ustring objects for next release
cycle?
To clarify, are you referring to all of the ustring objects in the
GParted_Core::get_filesystems() method?
For example the following line of code to detect LUKS encryption:
if ( Glib::ustring( magic1 ) =
Would you be able to try the latest version of GParted (currently
0.19.1). One way to do this is by booting from media containing GParted
Live. See http://gparted.org/livecd.php
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https:/
Alexander, I believe the problem is with the underlying libparted
library. The problem exists in Ubuntu 14.04 with libparted
2.3-19ubuntu1, and also with our latest GParted Live 0.19.1-1 with
libparted0debian1:i386 2.3-20.
As such, there is no need to perform the test I requested.
Instead I have
This problem has been resolved upstream. See:
Prevent GSource double-destroy warning messages
https://bugzilla.gnome.org/show_bug.cgi?id=729800
** Bug watch added: GNOME Bug Tracker #729800
https://bugzilla.gnome.org/show_bug.cgi?id=729800
--
You received this bug notification because you
Alexander, would you be able to try the latest GParted Live 0.19.1-4?
This newest Live image include gparted 0.19.1 linked with libparted
3.2-5. In my testing of fat32 resizes, all completed successfully with
this newer libparted version.
--
You received this bug notification because you are a
Thanks Alexander for reporting back that GParted with libparted 3.2
successfully works with fat32.
With the GParted option "Partion -> Check", GParted first runs a file
system check and then it will perform a file system resize to maximum to
ensure the file sytem uses the entire partition.
It app
This looks like the following upstream bug report:
GParted 0.19.0-2 segfaults with error in Glib::wrap_register()
https://bugzilla.gnome.org/show_bug.cgi?id=743399
A patch to glibmm has been submitted and committed to glibmm upstream.
See bug report:
core dump in wrap_register() when calling dep
The details are also available immediately under the details section of
the Applying pending operations window.
For example, see "The progress dialog" on the GParted web site screenshots page.
http://gparted.org/screenshots.php
Following is an example of the details in the Applying pending operat
A patch for this issue was included in the upstream GParted 0.22.0
release on March 23, 2015.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1078445
Title:
Xubuntu install fail due partition auto mou
@Phillip, this report sounds very similar to the following upstream
report.
GParted crashes resizing fat16 file system
https://bugzilla.gnome.org/show_bug.cgi?id=735669
Mike Fleetwood posted a libparted patch to address the issue.
https://bugzilla.gnome.org/show_bug.cgi?id=735669#c15
Perhaps th
@Skyman,
If you want to test to see if Mike's patch fixes the problem, the easiest way
is to try booting from the latest GParted Live 0.22.0-1.
http://gparted.org/livecd.php
The GParted Live image contains a custom parted/libparted that includes Mike's
patch.
--
You received this bug notifi
No worries Phillip. We all get busy from time to time. :-)
Steps to reproduce the crash are included in the upstream bug report. 'Still
it is always good to have the original reporter confirm if the problem is
resolved.
https://bugzilla.gnome.org/show_bug.cgi?id=735669#c4
If it helps to get
I believe that this is the same as the following upstream report:
https://bugzilla.gnome.org/show_bug.cgi?id=649509
** Bug watch added: GNOME Bug Tracker #649509
https://bugzilla.gnome.org/show_bug.cgi?id=649509
--
You received this bug notification because you are a member of Ubuntu
Bugs, w
*** This bug is a duplicate of bug 545911 ***
https://bugs.launchpad.net/bugs/545911
This is an problem reported earlier and fixed with the package parted -
2.3-5ubuntu4.
See bug #545911 - GParted crashes with Assertion (head_size <= 63)
** This bug has been marked a duplicate of bug 545911
Hi Phillip,
I tested growing an ext4 file system from 20 GiB to 40 GiB on Intel
Software RAID (Fake RAID) using the ubuntu-14.04.3-desktop-i386.iso
image and all worked as it should. :-)
Hence in my opinion this bug can be closed.
Curtis
--
You received this bug notification because you are
Since you mentioned "recovery" I assume that you are using the "Device
-> Attempt Data Rescue" menu option. If this is the case then the
required package is "gpart" (guess partitions). The command to install
*gpart* on ubuntu is:
sudo apt-get update && apt-get install gpart
If my assumptio
Hi Phillip,
Good news! This problem does not exist with Ubuntu 15.10.
I booted my computer using the ubuntu-15.10-desktop-i386.iso image,
and then successfully grew a 20 GiB ext4 partition to 40 GiB on my
Intel Software RAID (Fake RAID).
Following are the details of the successful test.
*** Bo
I don't have 14.04 installed on this computer. I tested using the
ubuntu-14.04-desktop-i386.iso live image.
Did you change anything in libparted for ubuntu 14.04 since it was
first released?
If you like I can test using the ubuntu-14.04.3-desktop-i386.iso live
image.
--
You received this bug
Thank you Rolf for your interest in improving GParted.
This problem was fixed upstream in GParted 0.20.0. See the following
upstream bug report:
GParted resizes the wrong filesystem (does not pass the devid to btrfs
filesystem resize)
https://bugzilla.gnome.org/show_bug.cgi?id=723842
The lates
The message "Can not have partition outside/without disk" indicates a
problem with the partition table.
To fix the problem you might look at the following article:
How-to Fix Invalid MSDOS Partition Tables
http://gparted.org/h2-fix-msdos-pt.php
--
You received this bug notification because you a
GParted displays partition sizes using units that try to keep the digits
before the decimal place to three or less.
When the Move/Resize or the Copy dialog box is first shown, the current
size is shown in mebibytes in the "New size (MiB)" field.
--
You received this bug notification because you
When GParted creates partitions, it uses the size in MiB as a guideline.
The size on disk can vary depending upon the setting of the "Align to"
drop down box.
See Specifying Partition Alignment
http://gparted.org/display-doc.php?name=help-manual#gparted-specify-partition-alignment
--
You receive
On thing you might try is to create a single partition starting 8 MiB
from the start of the drive.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/996188
Title:
Gparted Hosed my USB Thumb Drive
To ma
> Can't sectors per MiB be different on different harddisks?
> But the LBA size "sectors?" may be the right option for below MiB alligning.
Sector size can vary from the traditional 512 bytes per sector. Hence
sectors per MiB can be different on different hard disks. I believe the
same can be sa
Cefn, it would help if you save and attach the gparted_details.htm log
file if/when you are able to reproduce the problem you experienced.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/996188
Title:
*** This bug is a duplicate of bug 545911 ***
https://bugs.launchpad.net/bugs/545911
** This bug has been marked a duplicate of bug 545911
GParted crashes with Assertion (head_size <= 63)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to
Does the crash occur if you run "sudo gparted" from a terminal?
If so can you post the text output?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/945433
Title:
gparted crashes on scanning GPT forma
Many bugs have been fixed since the 0.4.5 release. The most recent
version is 0.11.0. Would you be able to try this latest version to see
if the problem still occurs?
GParted 0.11.0 can be found on the GParted Live CD
(http://gparted.org/livecd.php), and also on the Precise Pangolin Ubuntu
12.04
If I recall correctly this is an old problem that was fixed in newer
versions of the libparted library used by GParted.
I assume that you are running on an older version of Ubuntu. If you
only wish to use the latest version of GParted, you might try booting
from media containing GParted Live.
ht
It's possible that a hardware error with the card/device is being
encountered. After you run one of the aformentioned tools and encounter
the problem, open a terminal window and enter the command: dmesg
Take a look at the output of dmesg to see if any errors are being
reported.
--
You received
Hi Phillip,
The most recent version of GParted I saw in the psusi PPA was
0.19.0-1-ubuntu1, not 0.19.1.
https://launchpad.net/~psusi/+archive/ubuntu/ppa
Recently on October 20th, GParted 0.20.0 was released.
Am I looking at the correct URL for the PPA for the most recent version
of GParted?
Cu
Thank you Phillip for the clarification about only the fix being back-
ported.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1376051
Title:
gpartedbin crashed with SIGABRT in g_assertion_message()
Thank you Phillip for following up on these problems and back-porting
the appropriate patches. :-)
If I understand your post correctly, the "second" bug was introduced in
0.19. Was this "second" bug fixed in 0.19.1 by "Prevent cross thread
write after free in _OnReadable() (#731752)" ?
I guess
The upstream bug report for GParted can be found at the following link:
Bug number 729800 - Prevent GSource double-destroy warning messages
https://bugzilla.gnome.org/show_bug.cgi?id=729800
** Bug watch added: GNOME Bug Tracker #729800
https://bugzilla.gnome.org/show_bug.cgi?id=729800
--
Yo
** Bug watch added: GNOME Bug Tracker #729800
https://bugzilla.gnome.org/show_bug.cgi?id=729800
** Also affects: gparted via
https://bugzilla.gnome.org/show_bug.cgi?id=729800
Importance: Unknown
Status: Unknown
--
You received this bug notification because you are a member of Ubu
This problem also occurs on a fresh install of Ubuntu 13.10 i386 from
the ubuntu-13.10-desktop-i386.iso file.
A sample session demonstrating this problem follows:
root@saucy:~# gparted /dev/sdb# Create 512 MiB nilfs2 sdb1
==
libparted : 2.3
==
root@
Messages of the form "GLib-CRITICAL **: Source ID 6 was not found when
attempting to remove it" also occur when running GParted.
For example on Ubuntu GNOME 14.04 beta1:
$ sudo apt-get install gparted
$ sudo gparted
==
libparted : 2.3
==
(gpartedbin:2677):
Hmm... using "sudo" is how I would have run "gsmartcontrol". It works
on my computer with kubuntu 12.04. Perhaps this is a new problem with
the latest xubuntu release?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.laun
Thanks Chris for your interest in improving GParted.
As far as I know, udisks2 *does not* contain a command to inhibit
automounting of devices.
In the past I was told that a "udisks2-inhibit" command existed, but I
have not been able to locate it.
If anyone knows how to inhibit or prevent automo
In the past I tried "which udisks2-inhibit" to find the location of the
command, but this always returned no results. I didn't dig any deeper
because I regularly use Kubuntu and Ubuntu and the problem with
automounting does not occur.
Today I started my Ubuntu 14.04 Virtual Machine and ran the fo
These appear to be hardware errors. You might check to ensure that all
cables are securely plugged in and then try again.
The output from the following command would also be useful:
sudo parted -l
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subsc
If there are fragmented NTFS or FAT16/32 file systems on a device, then
this can cause GParted to take a very long time to scan. This is
because the ntfsresize command and the dosfsck command can take a long
time to determine used and unused sectors.
One way to check for this issue is with the fo
Error messages such as:
Error fsyncing/closing /dev/sdb: Remote I/O error
Remote I/O error during write on /dev/sdb
often imply a hardware problem. This can be as simple as a loose cable,
all the way up to a failing hard drive.
If the drive supports smart monitoring, you can use the graph
This problem was fixed with the upstream release of GParted 0.19.0 on
June 10, 2014.
The link to the relevant upstream report is as follows:
Partition Information Dialog Warning not readable
https://bugzilla.gnome.org/show_bug.cgi?id=690542
** Bug watch added: GNOME Bug Tracker #690542
https
Public bug reported:
I booted my computer using the ubuntu-14.04-desktop-i386.iso image, and
then tried to grow a 20 GiB ext4 partition to 40 GiB. Unfortunately
this failed because at some point the underlying /dev/mapper partition
entry disappeared.
Following are some details from before and af
gparted_details.htm log file that failed when attempting to grow an ext4
20 GiB dmraid partition to 40 GiB.
** Attachment added: "gparted_details-ubuntu1404-dm-grow.htm"
https://bugs.launchpad.net/ubuntu/+source/gparted/+bug/1332139/+attachment/4134974/+files/gparted_details-ubuntu1404-dm-grow
This problem was fixed with the upstream release of GParted 0.17.0 on
December 9, 2013.
The link to the relevant upstream report is as follows:
Partition Information Dialog - let user copy warnings
https://bugzilla.gnome.org/show_bug.cgi?id=705596
** Bug watch added: GNOME Bug Tracker #705596
This report should be closed as WONTFIX because there is no way that
GParted can provide all file system drivers for all operating systems.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/237575
Title:
Only one GParted process is *supposed* to be permitted to run at any one
time. From testing the gparted 0.11.0 package in ubuntu 12.04, I can
confirm that multiple running copies of GParted are permitted.
An enhancement was made to GParted 0.16.2 that permits only one instance
of GParted to execu
GParted uses blkid to acquire information about partitions so it is not
surprising that GParted is also impacted by this blkid behaviour.
This problem can happen in GParted if the BIOS indicates that a floppy
drive is present, but no physical floppy device is installed.
A work-around to this prob
GParted 0.18.0 contains some bugs known to cause crashes.
See:
Bug 729139 - Refactor OperationDetail to address random crash behavior
https://bugzilla.gnome.org/show_bug.cgi?id=729139
Bug 731752 - Write after free cross thread race in PipeCapture::_OnReadable()
causes crash
https://bugzilla.gnom
GParted 0.19.0 contains a bug known to cause crashes.
See:
Bug 731752 - Write after free cross thread race in PipeCapture::_OnReadable()
causes crash
https://bugzilla.gnome.org/show_bug.cgi?id=731752
Can you retry using GParted 0.20.0?
The easiest way might be to boot from media containing GPar
GParted 0.14.1 was released upstream on December 12, 2012 and includes a
fix for this problem.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1074606
Title:
gparted identifying incorrect raid arrays
Thank you for taking the time to improve Ubuntu and GParted by reporting
this problem.
>From a look at the upstream code, there is no "Settings;" category in the
>gparted.desktop file.
http://git.gnome.org/browse/gparted/tree/gparted.desktop.in.in
As such, when Ubuntu upgrades to the most recent
Eureka! I have discovered an even better work around for Mythbuntu
MythTV. This new workaround not only addresses the video tearing
problem, but also addresses the small amount of juddering that was
present in the workaround identified in comment #23.
For Mythbuntu 11.04 MythTV see the followin
Would you be able to provide the output from the following three
commands (run with root authority)?
fdisk -l -u
where one of the options is a lower case "L" and not the number one.
parted /path-to-your-device unit s print
where /path-to-your-device is something like /dev/sda.
blkid
Thank you peterzay for the terminal output. From a quick glance this
looks like a more complicated problem. The base partitioning tools,
such as fdisk and parted, only see the file system. The ecryptfs
appears to be device mapped on top of the underlying file system.
--
You received this bug n
Would you be able to provide the output from the following two commands?
sudo fdisk -l -u
where one of the options is a lower case "L" and not the number one.
sudo parted /path-to-your-device unit s print
where /path-to-your-device is something like /dev/sda.
--
You received this bug
Warren,
It does appear that the blkid command without any parameter is hung, and
that blkid was invoked from gparted.
When you run GParted, has Ubuntu been running for a while, or did you
immediately start up GParted as soon as Ubuntu booted?
The reason I ask is I have a hypothesis that internal
Phillip, I agree that there should be no difference if blkid is run by
hand in a terminal, or by gparted.
When GParted spawns the the blkid command, it uses the C locale (e.g.,
LC_ALL=C). I don't think that this should make any difference.
Assuming my hypothesis is correct, then if Ubuntu is boo
Warren, your observations are certainly relevant. If I understand
correctly, the situation is as follows:
Ubuntu - gparted hangs
Lubuntu - gparted hangs
Xubuntu - gparted works!
To me this means that there is something different between these
versions.
Does blkid follow the same pattern in Ubun
Yes. "parted" without the "g" is the command I would like you to run.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1068574
Title:
The package gparted did not load information about the Hard drives
This problem seems to be related to the following upstream bug report:
Bug 324220 - Gnome automount should be disabled when changing partitions
https://bugzilla.gnome.org/show_bug.cgi?id=324220
This problem was resolved in GParted 0.4.3 and higher.
** Bug watch added: GNOME Bug Tracker #324220
Warren, was the BIOS misconfigured when you ran the blkid command tests?
Either way I think the problem is outside of changes that can be made in
GParted.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs
This bug report appears to be similar to Ubuntu Launchpad Bug #375095 -
Crashed twice, once when hitting 'Cancel' another when I hit undo.
The problem with a crash when pressing ESC in a dialog window with number spin
buttons was confirmed in the following upstream bug report.
Bug 682658 - GParte
This bug might be related to the following upstream bug report:
Bug 682658 - GParted crash by pressing Esc in dialogs with number entry
https://bugzilla.gnome.org/show_bug.cgi?id=682658
** Bug watch added: GNOME Bug Tracker #682658
https://bugzilla.gnome.org/show_bug.cgi?id=682658
--
You re
Warren, as per Phillip's request, would you be able to test the blkid
command with and without the -p switch to see if these commands hang?
E.g.
sudo blkid
and
sudo blkid -p
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
As shown in the upstream bug report, the crash problem when hitting the
ESC key in the Resize/Move dialog window has been confirmed. So far I
have been unable to confirm the crash when using the menu option "Edit
--> Undo last operation" or the "Undo" toolbar button.
** Bug watch added: GNOME Bu
Did the "sudo blkid" command hang for a long period of time, or did it
complete quickly?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1029149
Title:
gparted automatically starts scanning all device
Phillip, I should have some more free time starting late November. If
there is something I can help with then just let me know.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/375095
Title:
Crashed t
Phillip, with regards to the refactoring to remove pthread, is there an
upstream bug report that we should link to? If not then perhaps we
should create one to help track the progress of the refactoring.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subs
Phillip, I read through the list of upstream GParted patches and did not
find one that exactly matched the refactoring issue. As such I have
created the following upstream bug report:
Bug 685740 - Refactor to use asynchronous command execution
https://bugzilla.gnome.org/show_bug.cgi?id=685740
*
Warren, it appears that you have also reported the following bug
reports:
Bug #1029149 - gparted automatically starts scanning all devices slowly and
never completing the task
Bug #1056540 - gparted does not finish scanning when in live session USB drive
Is this bug report a duplicate of the fir
*** This bug is a duplicate of bug 693430 ***
https://bugs.launchpad.net/bugs/693430
** This bug has been marked a duplicate of bug 693430
gparted information dialog bigger than screen
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ub
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.
https://bugs
While GParted is scanning the devices, would you be able to provide the
output from the following command?
ps -ef | egrep -i "dos|ntfs"
This will tell us if the problem is already known for fat16/32, or ntfs
file systems.
--
You received this bug notification because you are a member of Ubuntu
Warren,
Perhaps the BIOS on the computer is misconfigured to indicate that a
floppy disk device is present when the computer does not have a physical
floppy disk drive.
See Ubuntu Launchpad Bug #910379 - Gparted does not start and continues
to scan devices
See also GParted FAQ
http://gparted.org
Based on your screen shots from lubuntu12.10, it appears that the root
of the problem is that the scan does not complete when the BIOS is set
to indicate a floppy is present when no physical floppy device is
attached.
To confirm that I have understood the output correctly, does GParted
finish scan
The root of the problem is the misconfigured BIOS. Having said this, it
appears that earlier versions of Lubuntu did not suffer from this
problem. This suggests a change in some of the underlying utilities and
libraries.
Would you be able to reproduce the problem in Lubunut 12.10, and then
while
Thank you Warren for the process status output. From a quick look it
would appear that the 'blkid' command is not returning in a reasonable
amount of time.
To confirm this is the problem, would you be able to test the following
command with a misconfigured BIOS?
sudo blkid
Normally this co
Warren, it looks like blkid is hanging, or at least taking a long time
to process partition statistics, when working on a PC with the BIOS
misconfigured to indicate a floppy is present when no physical floppy
drive is installed.
Can you create a bug report for blkid?
--
You received this bug not
101 - 200 of 412 matches
Mail list logo
