Bug 367474 - Partition Manager seems to show swap partition is using more than its size
Summary: Partition Manager seems to show swap partition is using more than its size
Status: RESOLVED DUPLICATE of bug 367473
Alias: None
Product: partitionmanager
Classification: Applications
Component: general (show other bugs)
Version: 2.2
Platform: Arch Linux Linux
: NOR normal
Target Milestone: ---
Assignee: Andrius Štikonas
URL: http://imgur.com/a/8ay0g
Keywords:
Depends on:
Blocks:
 
Reported: 2016-08-18 00:34 UTC by Marco Parillo
Modified: 2016-08-18 00:45 UTC (History)
0 users

See Also:
Latest Commit:
Version Fixed In:

Attachments
Screenshot showing Partition Manager (73.15 KB, image/png)
2016-08-18 00:35 UTC, Marco Parillo 		Details
View All Add an attachment

Note You need to log in before you can comment on or make changes to this bug.
Description Marco Parillo 2016-08-18 00:34:05 UTC 
free -h
              total        used        free      shared  buff/cache   available
Mem:           3.8G        1.4G        1.5G         50M        1.0G        2.2G
Swap:          8.4G          0B        8.4G

So it seems as if I am using none of my swap, Yet, it seems to show the same amount used as my root partition.

Reproducible: Always

Steps to Reproduce:
1. Start Partition Manager
2. View > Refresh Devices and File > Quit and re-starting it return the same results

Actual Results:  
See URL and Attachment.

Expected Results:  
Something like the results from free -h
              total        used        free      shared  buff/cache   available
Mem:           3.8G        1.4G        1.5G         50M        1.0G        2.2G
Swap:          8.4G          0B        8.4G

Actually Manjaro, but Arch was the closest in the pull-down.

Version 2.2.1
Using:
KDE Frameworks 5.24.0
Qt 5.7.0 (built against 5.7.0)
The xcb windowing system
Comment 1 Marco Parillo 2016-08-18 00:35:15 UTC 
Created attachment 100650 [details]
Screenshot showing Partition Manager

Screenshot.
Comment 2 Marco Parillo 2016-08-18 00:45:46 UTC 

*** This bug has been marked as a duplicate of bug 367473 ***