Bug 890143
| Summary: | Kde partitionmanager doesn't work in F18 and higher | ||
|---|---|---|---|
| Product: | [Fedora] Fedora | Reporter: | Mattia Verga <mattia.verga> |
| Component: | kde-partitionmanager | Assignee: | Mattia Verga <mattia.verga> |
| Status: | CLOSED ERRATA | QA Contact: | Fedora Extras Quality Assurance <extras-qa> |
| Severity: | urgent | Docs Contact: | |
| Priority: | unspecified | ||
| Version: | 18 | CC: | gregg, jjr16, mattia.verga, PTrenholme |
| Target Milestone: | --- | ||
| Target Release: | --- | ||
| Hardware: | Unspecified | ||
| OS: | Unspecified | ||
| Whiteboard: | |||
| Fixed In Version: | kde-partitionmanager-1.0.3-11.20130624svn.fc19 | Doc Type: | Bug Fix |
| Doc Text: | Story Points: | --- | |
| Clone Of: | Environment: | ||
| Last Closed: | 2013-07-03 01:32:41 UTC | Type: | Bug |
| Regression: | --- | Mount Type: | --- |
| Documentation: | --- | CRM: | |
| Verified Versions: | Category: | --- | |
| oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |
| Cloudforms Team: | --- | Target Upstream Version: | |
| Embargoed: | |||
|
Description
Mattia Verga
2012-12-25 09:41:30 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) I'm still waiting for upstream kdelibs developers to solve the problem. For the moment using gparted is the only choice. 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.
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 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 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). 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. 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. |