https://bugs.kde.org/show_bug.cgi?id=487228
--- Comment #6 from Andrius Štikonas ---
For mounted file systems, KDE Partition Manager uses QStorageInfo:
p.fileSystem().setSectorsUsed( (storage.bytesTotal() - storage.bytesFree()) /
d.logicalSize());
--
You are receiving this mail because:
You
https://bugs.kde.org/show_bug.cgi?id=504459
Andrius Štikonas changed:
What|Removed |Added
Resolution|--- |NOT A BUG
Status|REPORTED
https://bugs.kde.org/show_bug.cgi?id=504459
Bug ID: 504459
Summary: Mouse cursor keeps growing when being moved
Classification: Plasma
Product: kwin
Version First 6.3.4
Reported In:
Platform: Other
OS: Linux
S
https://bugs.kde.org/show_bug.cgi?id=504352
Andrius Štikonas changed:
What|Removed |Added
Resolution|--- |FIXED
CC
https://bugs.kde.org/show_bug.cgi?id=503842
--- Comment #25 from Andrius Štikonas ---
So it tries to run
/usr/bin/sfdisk --force --append /dev/sdb
and writes to its input:
start=2048 size=3904290816
write
And the error is:
Sector 2048 already used.
Seems like there are more similar reports
https://bugs.kde.org/show_bug.cgi?id=503842
--- Comment #24 from Andrius Štikonas ---
[pid 10061] execve("/usr/bin/sfdisk", ["/usr/bin/sfdisk", "--force",
"--append", "/dev/sdb"], 0x55ce8a5373a0 /* 1 var */) = 0
[pid 9754] write(3, "\1\0\0\
https://bugs.kde.org/show_bug.cgi?id=503842
--- Comment #21 from Andrius Štikonas ---
By the way, is /dev/sdb RAID device? I haven't tested those though I don't see
why they shouldn't work.
Anyway, we need to figure out what commands were launched by partitionmanager.
See what
https://bugs.kde.org/show_bug.cgi?id=503842
--- Comment #19 from Andrius Štikonas ---
(In reply to Keelung from comment #18)
> if the Partition Table has been created, then the `New Partition Table`
> should be disabled.
Well, what if you change your mind and decided to create dif
https://bugs.kde.org/show_bug.cgi?id=503842
--- Comment #17 from Andrius Štikonas ---
(In reply to Keelung from comment #14)
> I'm not sure. So I reboot and tried again by starting it in root permission.
> Same errors reported, both in UI and console.
Don't run it as root. Whi
https://bugs.kde.org/show_bug.cgi?id=503842
Andrius Štikonas changed:
What|Removed |Added
Status|RESOLVED|REOPENED
Resolution|FIXED
https://bugs.kde.org/show_bug.cgi?id=503842
Andrius Štikonas changed:
What|Removed |Added
Resolution|DUPLICATE |FIXED
--- Comment #13 from Andrius Štikonas
https://bugs.kde.org/show_bug.cgi?id=503842
Andrius Štikonas changed:
What|Removed |Added
Status|RESOLVED|REOPENED
Resolution|DUPLICATE
https://bugs.kde.org/show_bug.cgi?id=503932
--- Comment #15 from Andrius Štikonas ---
Anyway, probably best to have a separate ticket there, it's another
application...
--
You are receiving this mail because:
You are watching all bug changes.
https://bugs.kde.org/show_bug.cgi?id=503932
--- Comment #14 from Andrius Štikonas ---
(In reply to hottog from comment #13)
> (In reply to Andrius Štikonas from comment #12)
> > Well, you have an example commit of reordering menu items in
> > partitionmanager. Instead of opening
https://bugs.kde.org/show_bug.cgi?id=454637
Andrius Štikonas changed:
What|Removed |Added
Resolution|--- |FIXED
Status|ASSIGNED
https://bugs.kde.org/show_bug.cgi?id=503932
--- Comment #12 from Andrius Štikonas ---
(In reply to hottog from comment #10)
> Should I open a new bug/wishlist report for that as well?
Well, you have an example commit of reordering menu items in partitionmanager.
Instead of opening wishl
https://bugs.kde.org/show_bug.cgi?id=503932
--- Comment #9 from Andrius Štikonas ---
Git commit ef7b4081aee82965f2dba6778373153d3e64c541 by Andrius Štikonas.
Committed on 09/05/2025 at 01:28.
Pushed by stikonas into branch 'master'.
Re-order settings menu.
M +1-2
https://bugs.kde.org/show_bug.cgi?id=503932
--- Comment #7 from Andrius Štikonas ---
(In reply to hottog from comment #6)
> I feel like this could be improved. Right now the the Settings section
> (dialog? context menu?) looks a bit odd with the empty spaces.
I don't think partition
https://bugs.kde.org/show_bug.cgi?id=503932
Andrius Štikonas changed:
What|Removed |Added
Priority|NOR |LO
Severity|normal
https://bugs.kde.org/show_bug.cgi?id=503842
--- Comment #10 from Andrius Štikonas ---
(In reply to Keelung from comment #9)
> (In reply to Andrius Štikonas from comment #7)
> > https://discussion.fedoraproject.org/t/fedora-42-plasma-kde-partitionmanager-
> > keeps-crashing
https://bugs.kde.org/show_bug.cgi?id=502141
Andrius Štikonas changed:
What|Removed |Added
CC||keelung.y...@flex.com
--- Comment #25 from
https://bugs.kde.org/show_bug.cgi?id=503842
Andrius Štikonas changed:
What|Removed |Added
Status|REPORTED|RESOLVED
Resolution
https://bugs.kde.org/show_bug.cgi?id=503842
--- Comment #7 from Andrius Štikonas ---
https://discussion.fedoraproject.org/t/fedora-42-plasma-kde-partitionmanager-keeps-crashing/150307
further suggests that this is the same problem... So I think let's mark it as a
duplicate. Reopen if it&
https://bugs.kde.org/show_bug.cgi?id=503842
--- Comment #6 from Andrius Štikonas ---
(In reply to Keelung from comment #4)
> So, is it related to
> https://invent.kde.org/system/kpmcore/-/merge_requests/63/diffs ?
> Thx!
Oh, maybe it is related to this diff...
--
You are receiving
https://bugs.kde.org/show_bug.cgi?id=503842
--- Comment #5 from Andrius Štikonas ---
(In reply to Keelung from comment #3)
> here is the log with KPMCORE_DEBUG=1:
> root@z840:/home/keelung# KPMCORE_DEBUG=1 partitionmanager
> kf.coreaddons: "Could not find plugin kpmcore/"
https://bugs.kde.org/show_bug.cgi?id=503842
--- Comment #2 from Andrius Štikonas ---
Hmm, indeed hard to tell what happened.
You could still try to debug it. First run it as
KPMCORE_DEBUG=1 partitionmanager
That should print far more info to the terminal.
--
You are receiving this mail
https://bugs.kde.org/show_bug.cgi?id=503453
--- Comment #18 from Andrius Štikonas ---
(In reply to Michael from comment #17)
> Okay, I just booted up a Live ISO of Neon User Edition, installed PM, and
> the menu structure looks as you say it should.
>
> So the issue is on my
https://bugs.kde.org/show_bug.cgi?id=503453
--- Comment #11 from Andrius Štikonas ---
Also see here the latest master has this configuration:
https://invent.kde.org/system/partitionmanager/-/blob/master/src/gui/partitionmanagerui.rc?ref_type=heads#L34
so clearly in the Devices menu.
--
You
https://bugs.kde.org/show_bug.cgi?id=503453
--- Comment #10 from Andrius Štikonas ---
Are you sure you are not running some old version accidentally? Could you
please double check in About dialog.
--
You are receiving this mail because:
You are watching all bug changes.
https://bugs.kde.org/show_bug.cgi?id=503453
Andrius Štikonas changed:
What|Removed |Added
Status|REPORTED|RESOLVED
Resolution
https://bugs.kde.org/show_bug.cgi?id=502141
Andrius Štikonas changed:
What|Removed |Added
CC||kdeb...@munin-soft.de
--- Comment #20 from
https://bugs.kde.org/show_bug.cgi?id=502141
Andrius Štikonas changed:
What|Removed |Added
CC||farch...@gmail.com
--- Comment #19 from
https://bugs.kde.org/show_bug.cgi?id=503280
Andrius Štikonas changed:
What|Removed |Added
Resolution|--- |DUPLICATE
Status|REPORTED
https://bugs.kde.org/show_bug.cgi?id=503148
Andrius Štikonas changed:
What|Removed |Added
Resolution|--- |DUPLICATE
Status|ASSIGNED
https://bugs.kde.org/show_bug.cgi?id=502243
--- Comment #1 from Andrius Štikonas ---
Well, KDE Partition Manager does not run echo ',' | sfdisk --force --append
/dev/sdc" since that's not a Linux command you can execute. Pipes like this are
just bash syntax. Partition Manag
https://bugs.kde.org/show_bug.cgi?id=502141
--- Comment #7 from Andrius Štikonas ---
Perhaps you could also obtain backtrace from the stuck instance? Right now I
have no idea where it is stuck.
--
You are receiving this mail because:
You are watching all bug changes.
https://bugs.kde.org/show_bug.cgi?id=502141
--- Comment #17 from Andrius Štikonas ---
(In reply to Nate Graham from comment #16)
> It appears to be super duper corrupted. It won't mount read/write, only RO.
> My intention was to use Partition Manager to erase it, but I can't sinc
https://bugs.kde.org/show_bug.cgi?id=502141
--- Comment #1 from Andrius Štikonas ---
Could you see if the following patch helps?
diff --git a/src/plugins/sfdisk/sfdiskbackend.cpp
b/src/plugins/sfdisk/sfdiskbackend.cpp
index e47c4e5..2fe99dd 100644
--- a/src/plugins/sfdisk/sfdiskbackend.cpp
https://bugs.kde.org/show_bug.cgi?id=502141
--- Comment #14 from Andrius Štikonas ---
Crash fixed pushed to
https://invent.kde.org/system/kpmcore/-/commit/458ef81f2e424f13cdea44d2d89b8260b463e34e
--
You are receiving this mail because:
You are watching all bug changes.
https://bugs.kde.org/show_bug.cgi?id=502141
--- Comment #6 from Andrius Štikonas ---
(In reply to Nate Graham from comment #4)
> If it's related, I see this in the log output:
>
> unknown file system type "dos" on "/dev/sdb"
That might be just checking whe
https://bugs.kde.org/show_bug.cgi?id=502141
--- Comment #13 from Andrius Štikonas ---
(In reply to Nate Graham from comment #12)
> Created attachment 179834 [details]
> Debug output
>
> It appears to be running `fsck.fat -n -v /dev/sdc1`. I'm attaching the full
> debug out
https://bugs.kde.org/show_bug.cgi?id=502141
--- Comment #11 from Andrius Štikonas ---
(In reply to Nate Graham from comment #9)
> I do notice that what's stuck is a spawned
> /usr/libexec/kpmcore_externalcommand process. If I quit the app, that keeps
> going. I'll try to get
https://bugs.kde.org/show_bug.cgi?id=501419
Andrius Štikonas changed:
What|Removed |Added
Resolution|--- |DUPLICATE
Status|REPORTED
https://bugs.kde.org/show_bug.cgi?id=461591
Andrius Štikonas changed:
What|Removed |Added
CC||jef...@hotmail.com
--- Comment #3 from
https://bugs.kde.org/show_bug.cgi?id=461591
Andrius Štikonas changed:
What|Removed |Added
CC||omarvx...@gmail.com
--- Comment #2 from
https://bugs.kde.org/show_bug.cgi?id=480180
Andrius Štikonas changed:
What|Removed |Added
Resolution|--- |DUPLICATE
Status|REPORTED
https://bugs.kde.org/show_bug.cgi?id=501037
Andrius Štikonas changed:
What|Removed |Added
Resolution|--- |NOT A BUG
Status|REPORTED
https://bugs.kde.org/show_bug.cgi?id=501037
--- Comment #3 from Andrius Štikonas ---
(In reply to Justin Zobel from comment #2)
> The 5.02GB one when mounted would be correct. There was no content in the
> drive.
Well, that's what we are using when that info is available. But then p
https://bugs.kde.org/show_bug.cgi?id=501037
--- Comment #1 from Andrius Štikonas ---
Hmm, it uses different sources of data. I don't know which one would be correct
in your case.
When partition is mounted QStorageInfo from Qt is used
(https://doc.qt.io/qt-6/qstorageinfo.html) which unde
https://bugs.kde.org/show_bug.cgi?id=501063
--- Comment #2 from Andrius Štikonas ---
Hmm, not sure how this happened. Since it absolutely should have resized
underlying file system. And resizing of fs in shrinking case happens to be
before resizing of partition, see the following 3 lines:
https
https://bugs.kde.org/show_bug.cgi?id=500723
--- Comment #2 from Andrius Štikonas ---
Hmm, not sure whether we want this by default, but perhaps we could do it when
device node is passed via command line (that's what dolphin does when it calls
partitionmanager binary).
--
You are receiving
https://bugs.kde.org/show_bug.cgi?id=500175
--- Comment #2 from Andrius Štikonas ---
I've added those two features to ext2.cpp though for now that is not exposed
yet in partition manager UI.
--
You are receiving this mail because:
You are watching all bug changes.
https://bugs.kde.org/show_bug.cgi?id=500175
--- Comment #1 from Andrius Štikonas ---
Hmm, right now kpmcore library supports optional "Features" and we have some of
them
https://invent.kde.org/system/kpmcore/-/blob/master/src/fs/ext2.cpp?ref_type=heads#L53
lazy_itable_init and lazy_jo
https://bugs.kde.org/show_bug.cgi?id=499064
Andrius Štikonas changed:
What|Removed |Added
Latest Commit|https://invent.kde.org/syst |https://invent.kde.org/syst
https://bugs.kde.org/show_bug.cgi?id=499064
Andrius Štikonas changed:
What|Removed |Added
Resolution|--- |FIXED
Status|CONFIRMED
https://bugs.kde.org/show_bug.cgi?id=499151
--- Comment #1 from Andrius Štikonas ---
Try to run that command manually from the terminal and see what is the error.
--
You are receiving this mail because:
You are watching all bug changes.
https://bugs.kde.org/show_bug.cgi?id=499064
--- Comment #5 from Andrius Štikonas ---
(In reply to Rafael Just from comment #4)
> Could be, since It only looks like the cursor / partition manager doesn't
> notice that there is an edge. Could it be perhaps worth to check out the
&
https://bugs.kde.org/show_bug.cgi?id=499064
--- Comment #3 from Andrius Štikonas ---
(In reply to Rafael Just from comment #2)
> Could be, since It only looks like the cursor / partition manager doesn't
> notice that there is an edge. Could it be perhaps worth to check out the
&
https://bugs.kde.org/show_bug.cgi?id=499064
Andrius Štikonas changed:
What|Removed |Added
Ever confirmed|0 |1
Status|REPORTED
https://bugs.kde.org/show_bug.cgi?id=498765
--- Comment #3 from Andrius Štikonas ---
What happens if you run sudo sfdisk --wipe=always /dev/sdb from the command
line?
Also does dmesg indicate anything about drive being read only?
--
You are receiving this mail because:
You are watching all
https://bugs.kde.org/show_bug.cgi?id=496400
Andrius Štikonas changed:
What|Removed |Added
Latest Commit|https://invent.kde.org/syst |https://invent.kde.org/syst
https://bugs.kde.org/show_bug.cgi?id=496400
Andrius Štikonas changed:
What|Removed |Added
Status|REPORTED|RESOLVED
Latest Commit
https://bugs.kde.org/show_bug.cgi?id=495440
Andrius Štikonas changed:
What|Removed |Added
Status|ASSIGNED|RESOLVED
Resolution
https://bugs.kde.org/show_bug.cgi?id=495440
Andrius Štikonas changed:
What|Removed |Added
URL||https://invent.kde.org/syst
https://bugs.kde.org/show_bug.cgi?id=495399
Andrius Štikonas changed:
What|Removed |Added
Status|REPORTED|RESOLVED
Resolution
https://bugs.kde.org/show_bug.cgi?id=432103
Andrius Štikonas changed:
What|Removed |Added
CC||cgreg...@netcomtechs.com
--- Comment #13
https://bugs.kde.org/show_bug.cgi?id=494961
Andrius Štikonas changed:
What|Removed |Added
Status|REPORTED|RESOLVED
Resolution
https://bugs.kde.org/show_bug.cgi?id=494557
--- Comment #6 from Andrius Štikonas ---
Widgetsaddons bug: https://bugs.kde.org/show_bug.cgi?id=494624
Kevin, I think I tried setting QWidget::setTabOrder yesterday if I remember
correctly and it didn't work.
I have not tried to use QO
https://bugs.kde.org/show_bug.cgi?id=494624
Bug ID: 494624
Summary: KNewPasswordWidget does not let setting tab order
Classification: Frameworks and Libraries
Product: frameworks-kwidgetsaddons
Version: 6.6.0
Platform: Other
https://bugs.kde.org/show_bug.cgi?id=494557
--- Comment #5 from Andrius Štikonas ---
(In reply to Kevin Kofler from comment #4)
> Have you tried setting it programmatically from the code using
> QWidget::setTabOrder (https://doc.qt.io/qt-6/qwidget.html#setTabOrder)?
>
> If that d
https://bugs.kde.org/show_bug.cgi?id=494548
--- Comment #9 from Andrius Štikonas ---
(In reply to Andrius Štikonas from comment #8)
> (In reply to LaughingMan from comment #7)
> > Ok:
> > - Stopped md126.
> > - Tried creating a partition table -> Failed
> > - Stoppe
https://bugs.kde.org/show_bug.cgi?id=494548
--- Comment #8 from Andrius Štikonas ---
(In reply to LaughingMan from comment #7)
> Ok:
> - Stopped md126.
> - Tried creating a partition table -> Failed
> - Stopped md127
> - Tried creating a partition table -> Success
>
&
https://bugs.kde.org/show_bug.cgi?id=494548
--- Comment #6 from Andrius Štikonas ---
(In reply to LaughingMan from comment #5)
> So, should I run
> > sudo mdadm --stop /dev/md126
> or
> > sudo mdadm --stop /dev/md127
> ?
>
> I'm a little out of my depth here.
https://bugs.kde.org/show_bug.cgi?id=494548
--- Comment #4 from Andrius Štikonas ---
(In reply to LaughingMan from comment #3)
> /dev/md0 doesn't exist. There's md, md126 and md127.
>
> lsblk lists the device as:
> > sdf
https://bugs.kde.org/show_bug.cgi?id=494557
--- Comment #3 from Andrius Štikonas ---
(In reply to LaughingMan from comment #2)
> "Unfortunately, there doesn't seem to be an easy way to change tab order of
> KNewPasswordWidget."
>
> Does that mean the tab order for th
https://bugs.kde.org/show_bug.cgi?id=494548
--- Comment #2 from Andrius Štikonas ---
Hmm, I guess what happened in your case is that Linux system noticed that this
is raid disk and automatically activated it on /dev/md0.
Can you try to reproduce the same problem, then run
sudo mdadm --stop /dev
https://bugs.kde.org/show_bug.cgi?id=494556
--- Comment #3 from Andrius Štikonas ---
(In reply to LaughingMan from comment #2)
> Are you aware of an existing issue on the Qt side? Because it pretty clearly
> is a bug, even if partition manager maybe isn't the right place to deploy a
https://bugs.kde.org/show_bug.cgi?id=494548
--- Comment #1 from Andrius Štikonas ---
Hmm, I don't think we want to add --force to sfdisk here since it might protect
us against trashing something in other cases. Not sure what's the best way to
fix this but I guess I should try to re
https://bugs.kde.org/show_bug.cgi?id=494557
Andrius Štikonas changed:
What|Removed |Added
Resolution|--- |FIXED
Latest Commit
https://bugs.kde.org/show_bug.cgi?id=494556
Andrius Štikonas changed:
What|Removed |Added
Status|REPORTED|RESOLVED
Resolution
https://bugs.kde.org/show_bug.cgi?id=470675
--- Comment #10 from Andrius Štikonas ---
(In reply to Thomas Bertels from comment #9)
> The bitwise & operator may make it seem like Shrink and Grow always happen
> (note that it would be in the wrong order as gparted grows it then shrinks
https://bugs.kde.org/show_bug.cgi?id=470675
--- Comment #8 from Andrius Štikonas ---
(In reply to Thomas Bertels from comment #7)
> I've noticed that gparted resizes the partition when moving it: it grows it
> to use all the space, then moves the data and finally shrinks the partiti
https://bugs.kde.org/show_bug.cgi?id=494105
--- Comment #1 from Andrius Štikonas ---
Yes, openQA could be useful.
As for testexternalcommand.cpp, it works here, so something is missing on your
test system, the error message suggest that dbus is not running (to execute
external command test
https://bugs.kde.org/show_bug.cgi?id=492016
--- Comment #1 from Andrius Štikonas ---
We do use that frameworks API
https://invent.kde.org/system/kpmcore/-/blob/master/src/util/capacity.cpp?ref_type=heads#L129
though maybe we don't update unit names, so it still shows MiB...
--
Yo
https://bugs.kde.org/show_bug.cgi?id=491871
Andrius Štikonas changed:
What|Removed |Added
Status|REPORTED|RESOLVED
Resolution
https://bugs.kde.org/show_bug.cgi?id=441916
Andrius Štikonas changed:
What|Removed |Added
CC||wrona1...@gmail.com
--- Comment #22 from
https://bugs.kde.org/show_bug.cgi?id=425040
Andrius Štikonas changed:
What|Removed |Added
CC||techxga...@outlook.com
--- Comment #8 from
https://bugs.kde.org/show_bug.cgi?id=490904
Andrius Štikonas changed:
What|Removed |Added
Resolution|--- |DUPLICATE
Status|REPORTED
https://bugs.kde.org/show_bug.cgi?id=470675
--- Comment #4 from Andrius Štikonas ---
(In reply to Ishrak from comment #3)
> Does *partitionmanager* use *parted* under the hood? If so, I recently found
> that parted would fail to format disk.img but gparted will work. I think I
> mess
https://bugs.kde.org/show_bug.cgi?id=460874
Andrius Štikonas changed:
What|Removed |Added
Status|REPORTED|RESOLVED
Resolution
https://bugs.kde.org/show_bug.cgi?id=432103
Andrius Štikonas changed:
What|Removed |Added
CC||rodrigo.pe...@gmail.com
--- Comment #12
https://bugs.kde.org/show_bug.cgi?id=481780
Andrius Štikonas changed:
What|Removed |Added
Status|REPORTED|RESOLVED
Resolution
https://bugs.kde.org/show_bug.cgi?id=432103
Andrius Štikonas changed:
What|Removed |Added
CC||kde.t-shirt...@passmail.net
--- Comment #11
https://bugs.kde.org/show_bug.cgi?id=451572
Andrius Štikonas changed:
What|Removed |Added
Latest Commit||https://invent.kde.org/syst
https://bugs.kde.org/show_bug.cgi?id=441916
Andrius Štikonas changed:
What|Removed |Added
CC||n...@kde.org
Version Fixed In
https://bugs.kde.org/show_bug.cgi?id=451572
Andrius Štikonas changed:
What|Removed |Added
Ever confirmed|0 |1
Status|REPORTED
https://bugs.kde.org/show_bug.cgi?id=441916
Andrius Štikonas changed:
What|Removed |Added
Latest Commit|https://invent.kde.org/syst |https://invent.kde.org/syst
https://bugs.kde.org/show_bug.cgi?id=489768
Andrius Štikonas changed:
What|Removed |Added
Resolution|--- |WORKSFORME
Status|REPORTED
https://bugs.kde.org/show_bug.cgi?id=489768
--- Comment #1 from Andrius Štikonas ---
Hmm, I can't fully reproduce it. When I press OK in step 4 it asks for LUKS
password (perhaps unnecessary but I need to check) once but then it works and
resizes properly.
--
You are receiving this
https://bugs.kde.org/show_bug.cgi?id=489855
Andrius Štikonas changed:
What|Removed |Added
Resolution|--- |UNMAINTAINED
Status|REPORTED
1 - 100 of 1084 matches
Mail list logo
