Bug 890143 - Kde partitionmanager doesn't work in F18 and higher
Summary: Kde partitionmanager doesn't work in F18 and higher
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Fedora
Classification: Fedora
Component: kde-partitionmanager
Version: 18
Hardware: Unspecified
OS: Unspecified
unspecified
urgent
Target Milestone: ---
Assignee: Mattia Verga
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2012-12-25 09:41 UTC by Mattia Verga
Modified: 2013-07-03 01:39 UTC (History)
4 users (show)

Fixed In Version: kde-partitionmanager-1.0.3-11.20130624svn.fc19
Clone Of:
Environment:
Last Closed: 2013-07-03 01:32:41 UTC
Type: Bug
Embargoed:


Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
KDE Software Compilation 311408 0 None None None Never

Description Mattia Verga 2012-12-25 09:41:30 UTC
Kde-partitionmanager doesn't currently work in F18 and higher due to a problem of kdelibs (solid) and udisks2 backend.
See https://bugs.kde.org/show_bug.cgi?id=311408

Comment 1 Gregg Lebovitz 2013-02-10 01:31:45 UTC
Hi, I am confirming this behavior after installing fedora 18 on a new disk. The partition manager is showing mountable partition devices rather than the entire disk device in the devices list.

Rather than seeing

/dev/sda
/dev/sdb
/dev/sdc

in the device list, I am seeing

/dev/sda5
/dev/sdb3
/dev/sdc1

where sda5 is a mountable NTFS Partition, sdb3 is a mountable NTFS partiton and sdc2 is an ext4 boot partition.

Hardware is an ACER S3-951-6432 and drives are

sda - SATA SSD
sdb - USB to SATA bridge with Samsung drive
sdb - USB to SATA bridge with Hitachi drive (Hitachi Easy Drive)

Comment 2 Mattia Verga 2013-02-10 10:23:50 UTC
I'm still waiting for upstream kdelibs developers to solve the problem.
For the moment using gparted is the only choice.

Comment 3 Peter Trenholme 2013-06-21 17:35:54 UTC
I just looked at the partitionmanager script in /usr/bin/, and noticed that the test for the hal_lock availability:

HAL_LOCK=`which hal-lock`
PARTITIONMANAGER_BIN=/usr/bin/partitionmanager-bin
RUN_WITHOUT_LOCK=1

if [ "x$HAL_LOCK" != "x" ]; then
        $HAL_LOCK --interface org.freedesktop.Hal.Device.Storage --exclusive --run "$PARTITIONMANAGER_BIN $*" && RUN_WITHOUT_LOCK=0
fi

ASSUMES that "which" returns null when ut is not available. I believe that

HAL_LOCK=`which hal-lock 2>/dev/null`

would be a better choice.

Note: Making that change did not fix the problem reported in this bug report, but I thought it might be related thereto.

Comment 4 Fedora Update System 2013-06-23 11:48:07 UTC
kde-partitionmanager-1.0.3-11.20130624svn.fc19 has been submitted as an update for Fedora 19.
https://admin.fedoraproject.org/updates/kde-partitionmanager-1.0.3-11.20130624svn.fc19

Comment 5 Fedora Update System 2013-06-23 11:48:17 UTC
kde-partitionmanager-1.0.3-11.20130624svn.fc18 has been submitted as an update for Fedora 18.
https://admin.fedoraproject.org/updates/kde-partitionmanager-1.0.3-11.20130624svn.fc18

Comment 6 Fedora Update System 2013-06-23 19:03:05 UTC
Package kde-partitionmanager-1.0.3-11.20130624svn.fc19:
* should fix your issue,
* was pushed to the Fedora 19 testing repository,
* should be available at your local mirror within two days.
Update it with:
# su -c 'yum update --enablerepo=updates-testing kde-partitionmanager-1.0.3-11.20130624svn.fc19'
as soon as you are able to.
Please go to the following url:
https://admin.fedoraproject.org/updates/FEDORA-2013-11511/kde-partitionmanager-1.0.3-11.20130624svn.fc19
then log in and leave karma (feedback).

Comment 7 Fedora Update System 2013-07-03 01:32:41 UTC
kde-partitionmanager-1.0.3-11.20130624svn.fc18 has been pushed to the Fedora 18 stable repository.  If problems still persist, please make note of it in this bug report.

Comment 8 Fedora Update System 2013-07-03 01:39:54 UTC
kde-partitionmanager-1.0.3-11.20130624svn.fc19 has been pushed to the Fedora 19 stable repository.  If problems still persist, please make note of it in this bug report.


Note You need to log in before you can comment on or make changes to this bug.