https://bugs.kde.org/show_bug.cgi?id=417506
--- Comment #10 from Andrius Štikonas ---
I think you are looking at the wrong place.
This is the screenshot on Neon:
https://kde.modular.im/_matrix/media/r0/download/kde.org/BZRpvNRMcJVCOMrFFKcdzwGe
--
You are receiving this mail because:
You
https://bugs.kde.org/show_bug.cgi?id=417506
--- Comment #8 from Andrius Štikonas ---
(In reply to Ricardo Alejandro García Gómez from comment #7)
> (In reply to Andrius Štikonas from comment #6)
> > (In reply to Ricardo Alejandro García Gómez from comment #5)
> > > (In reply t
https://bugs.kde.org/show_bug.cgi?id=417506
--- Comment #6 from Andrius Štikonas ---
(In reply to Ricardo Alejandro García Gómez from comment #5)
> (In reply to Andrius Štikonas from comment #4)
> > You possibly did not install exfat-utils. You can check that in Tools->File
> &
https://bugs.kde.org/show_bug.cgi?id=417506
--- Comment #4 from Andrius Štikonas ---
You possibly did not install exfat-utils. You can check that in Tools->File
System Support.
--
You are receiving this mail because:
You are watching all bug changes.
https://bugs.kde.org/show_bug.cgi?id=417506
Andrius Štikonas changed:
What|Removed |Added
Resolution|--- |NOT A BUG
Status|REPORTED
https://bugs.kde.org/show_bug.cgi?id=417205
Andrius Štikonas changed:
What|Removed |Added
Status|REPORTED|RESOLVED
Resolution
https://bugs.kde.org/show_bug.cgi?id=411841
Andrius Štikonas changed:
What|Removed |Added
CC||esbo...@gmail.com
--- Comment #2 from
https://bugs.kde.org/show_bug.cgi?id=417139
Andrius Štikonas changed:
What|Removed |Added
Status|REPORTED|RESOLVED
Resolution
https://bugs.kde.org/show_bug.cgi?id=413883
Andrius Štikonas changed:
What|Removed |Added
CC||tim.ban...@gmail.com
--- Comment #8 from
https://bugs.kde.org/show_bug.cgi?id=416967
--- Comment #5 from Andrius Štikonas ---
(In reply to Josh Freeno from comment #4)
> (In reply to Andrius Štikonas from comment #3)
> > Unfortunately, without more info, I won't be able to do anything.
> > I just tried with my USB
https://bugs.kde.org/show_bug.cgi?id=416968
Andrius Štikonas changed:
What|Removed |Added
Resolution|--- |DUPLICATE
Status|REPORTED
https://bugs.kde.org/show_bug.cgi?id=413973
Andrius Štikonas changed:
What|Removed |Added
CC||freefreen...@gmail.com
--- Comment #34 from
https://bugs.kde.org/show_bug.cgi?id=416967
--- Comment #3 from Andrius Štikonas ---
Unfortunately, without more info, I won't be able to do anything.
I just tried with my USB, it works fine.
My theory (although I have no strong proof) is that for some reason your Linux
kernel marked USB
https://bugs.kde.org/show_bug.cgi?id=416967
Andrius Štikonas changed:
What|Removed |Added
Status|REPORTED|NEEDSINFO
Resolution
https://bugs.kde.org/show_bug.cgi?id=404398
--- Comment #5 from Andrius Štikonas ---
Hmm, the commit was done before release. So it should have been released. I'll
have to investigate this again...
--
You are receiving this mail because:
You are watching all bug changes.
https://bugs.kde.org/show_bug.cgi?id=386114
--- Comment #27 from Andrius Štikonas ---
(In reply to Carson Black from comment #24)
> Yakuake positions itself correctly on Wayland for me, but KRunner is still
> overlapped by the panel.
Yakuake does not position itself correctly on your
https://bugs.kde.org/show_bug.cgi?id=416230
--- Comment #3 from Andrius Štikonas ---
(In reply to HM from comment #2)
> So the USB drive I had this crash happen with was kind of problematic. It
> was a promo USB that you receive at expos. (Might have been read only. I was
> able
https://bugs.kde.org/show_bug.cgi?id=397769
Andrius Štikonas changed:
What|Removed |Added
Status|REPORTED|RESOLVED
Resolution
https://bugs.kde.org/show_bug.cgi?id=413418
Andrius Štikonas changed:
What|Removed |Added
CC||mcmailf...@protonmail.com
--- Comment #7
https://bugs.kde.org/show_bug.cgi?id=413418
Andrius Štikonas changed:
What|Removed |Added
CC||prote...@hotmail.it
--- Comment #6 from
https://bugs.kde.org/show_bug.cgi?id=416230
Andrius Štikonas changed:
What|Removed |Added
Status|REPORTED|RESOLVED
Resolution
https://bugs.kde.org/show_bug.cgi?id=414497
Andrius Štikonas changed:
What|Removed |Added
Resolution|--- |DUPLICATE
Status|REPORTED
https://bugs.kde.org/show_bug.cgi?id=342178
--- Comment #4 from Andrius Štikonas ---
Git commit d24191ebd8ee4a1792003e5bd280cb7679f5e834 by Andrius Štikonas, on
behalf of Arnaud Ferraris.
Committed on 12/01/2020 at 11:58.
Pushed by stikonas into branch 'master'.
Add support for filesystem
https://bugs.kde.org/show_bug.cgi?id=393236
Andrius Štikonas changed:
What|Removed |Added
CC||rych...@gmx.ch
--- Comment #4 from Andrius
https://bugs.kde.org/show_bug.cgi?id=415929
Andrius Štikonas changed:
What|Removed |Added
Status|REPORTED|RESOLVED
Resolution
https://bugs.kde.org/show_bug.cgi?id=415964
Andrius Štikonas changed:
What|Removed |Added
Status|REPORTED|RESOLVED
Resolution
https://bugs.kde.org/show_bug.cgi?id=407192
Andrius Štikonas changed:
What|Removed |Added
CC||brucewwayne1...@gmail.com
--- Comment #18
https://bugs.kde.org/show_bug.cgi?id=392693
--- Comment #25 from Andrius Štikonas ---
(In reply to Andrius Štikonas from comment #23)
> (In reply to Andrius Štikonas from comment #22)
> > After I booted with just laptop screen and blur was working, I plugged in my
> >
https://bugs.kde.org/show_bug.cgi?id=404636
Andrius Štikonas changed:
What|Removed |Added
Status|REOPENED|CONFIRMED
--
You are receiving this mail
https://bugs.kde.org/show_bug.cgi?id=404636
--- Comment #5 from Andrius Štikonas ---
(In reply to tguen from comment #4)
> I haven't tried a clean environment, but this was about the minimum size,
> not the default (although they appear to be the same). I have tried resizing
> t
https://bugs.kde.org/show_bug.cgi?id=404636
--- Comment #3 from Andrius Štikonas ---
(In reply to tguen from comment #2)
> This bug still exists in 4.0.0.
Have you tried with clean environment? Only the default size was changed. If
too small size was already written to settings, it might s
https://bugs.kde.org/show_bug.cgi?id=407191
Andrius Štikonas changed:
What|Removed |Added
Resolution|NOT A BUG |FIXED
--- Comment #11 from Andrius Štikonas
https://bugs.kde.org/show_bug.cgi?id=413973
Andrius Štikonas changed:
What|Removed |Added
Status|REPORTED|RESOLVED
Resolution
https://bugs.kde.org/show_bug.cgi?id=414624
--- Comment #1 from Andrius Štikonas ---
Unfortunately, I don't really know what causes craash in sectorsUsed.
I have seen them myself from time to time and I had some bug reports but I was
never able to reproduce them, they were just random crashes
https://bugs.kde.org/show_bug.cgi?id=413973
--- Comment #25 from Andrius Štikonas ---
partitionmanager will be patched not to include non-block devices. There
is no reason to include them.
Maybe also worth opening KD bug against touchpad kcm?
On 2019-11-25 15:43, bugzilla_nore...@kde.org
https://bugs.kde.org/show_bug.cgi?id=413973
--- Comment #21 from Andrius Štikonas ---
(In reply to joey.joey586 from comment #20)
> Do i file the udev bug to the systemd github or is there another place for
> that? (this is my first time filing bugs so i'm somewhat clueless)
I wou
https://bugs.kde.org/show_bug.cgi?id=413973
--- Comment #18 from Andrius Štikonas ---
(In reply to joey.joey586 from comment #17)
> Yup, running the "udevadm trigger --subsystem-match= fixes the
> issue.
>
> So should I file a bug to udev or should this be considered a bug on
&
https://bugs.kde.org/show_bug.cgi?id=413973
--- Comment #16 from Andrius Štikonas ---
(In reply to joey.joey586 from comment #15)
> I was unable to reproduce this issue in Manjaro KDE. Probably a regression?
>
> Manjaro:
>
> kde plasma version: 5.13.4
> kde frameworks ve
https://bugs.kde.org/show_bug.cgi?id=407191
--- Comment #10 from Andrius Štikonas ---
(In reply to Andrius Štikonas from comment #8)
> Yes, I'll take a look at it too.
>
> I'll close this bug in the meantime as it's not something I can fix in
> partition manager. But you can still
https://bugs.kde.org/show_bug.cgi?id=413973
Andrius Štikonas changed:
What|Removed |Added
See Also||https://bugs.kde.org/show_b
https://bugs.kde.org/show_bug.cgi?id=407191
Andrius Štikonas changed:
What|Removed |Added
See Also||https://bugs.kde.org/show_b
https://bugs.kde.org/show_bug.cgi?id=413973
--- Comment #13 from Andrius Štikonas ---
--subsystem-match=SUBSYSTEM
Trigger events for devices which belong to a matching subsystem(In
reply to joey.joey586 from comment #12)
> So I don't think this is an Archlinux-specific issue
https://bugs.kde.org/show_bug.cgi?id=413973
--- Comment #9 from Andrius Štikonas ---
(In reply to joey.joey586 from comment #8)
> Sorry. I tested it again; it only needs "udevadm trigger" to cause the
> touchpad issue.
I had some other bug from Arch user (different s
https://bugs.kde.org/show_bug.cgi?id=413973
--- Comment #7 from Andrius Štikonas ---
(In reply to joey.joey586 from comment #6)
> I think I found it; I ran these commands (as root):
>
> udevadm settle --timeout=10
> udevadm trigger
>
> and the touchpad refuses to tap-to-click
https://bugs.kde.org/show_bug.cgi?id=413973
--- Comment #4 from Andrius Štikonas ---
(In reply to joey.joey586 from comment #3)
> Oh I forgot to add:
> I'm running Xorg 1.20.5
Same here, 1.20.5...
Maybe you can try to figure out which command resets partition manager
configuration?
https://bugs.kde.org/show_bug.cgi?id=413973
--- Comment #1 from Andrius Štikonas ---
Hmm, I am unable to reproduce this.
kpmcore master
KDE Frameworks: 5.64
Qt: 5.13.2
Windowing system: Wayland
Maybe it works on wayland?
--
You are receiving this mail because:
You are watching all bug
https://bugs.kde.org/show_bug.cgi?id=413927
Andrius Štikonas changed:
What|Removed |Added
Resolution|--- |FIXED
Status|CONFIRMED
https://bugs.kde.org/show_bug.cgi?id=413927
--- Comment #2 from Andrius Štikonas ---
(In reply to Andrius Štikonas from comment #1)
> I can reproduce this (but maybe had to click more times).
I think this happens because at the moment FileSystemFactory::init is not
reentrant, so new c
https://bugs.kde.org/show_bug.cgi?id=413927
Andrius Štikonas changed:
What|Removed |Added
Status|REPORTED|CONFIRMED
Ever confirmed|0
https://bugs.kde.org/show_bug.cgi?id=413883
--- Comment #7 from Andrius Štikonas ---
Any chance you can test these changes?
At the moment they are in master, but maybe it's worth adding them to 4.0
branch too.
--
You are receiving this mail because:
You are watching all bug changes.
https://bugs.kde.org/show_bug.cgi?id=413883
Andrius Štikonas changed:
What|Removed |Added
Resolution|--- |FIXED
Status|REPORTED
https://bugs.kde.org/show_bug.cgi?id=413883
--- Comment #4 from Andrius Štikonas ---
Hmm, there seems to be two problems. The one mentioned above can be fixed by
replacing blockdev with partx (both part of util-linux).
However, there seems to be some bug in luks resizing code too (incorrect
https://bugs.kde.org/show_bug.cgi?id=413883
--- Comment #5 from Andrius Štikonas ---
Git commit 13beb9931951cf5972e341a871263146d2bdafbe by Andrius Štikonas.
Committed on 18/11/2019 at 18:42.
Pushed by stikonas into branch 'master'.
Use partx instead of blockdev to update partition table
https://bugs.kde.org/show_bug.cgi?id=413883
--- Comment #3 from Andrius Štikonas ---
blockdev --rereadpt /dev/sd# seem to be failing when there is an open luks
partition.
So I guess this is a regression in KPMcore 4.0 (when switching to sfdisk
backend.)
--
You are receiving this mail because
https://bugs.kde.org/show_bug.cgi?id=413883
--- Comment #2 from Andrius Štikonas ---
Hmm, for some reason when resizing LVM PV partition, the information about new
partition table is not passed to kernel (can be seen in /sys/block/*/size), so
when cryptsetup resize runs, it sees the old size
https://bugs.kde.org/show_bug.cgi?id=413853
Andrius Štikonas changed:
What|Removed |Added
Status|REPORTED|RESOLVED
Resolution
https://bugs.kde.org/show_bug.cgi?id=413851
Andrius Štikonas changed:
What|Removed |Added
Status|REPORTED|RESOLVED
Resolution
https://bugs.kde.org/show_bug.cgi?id=413853
--- Comment #1 from Andrius Štikonas ---
Test smart is known to be broken.
It tries to call df command which helper is not allowed to run.
Possibly it makes sense to remove this test...
--
You are receiving this mail because:
You are watching all
https://bugs.kde.org/show_bug.cgi?id=413122
--- Comment #3 from Andrius Štikonas ---
(In reply to falling_failing_falling from comment #2)
> Sorry, no backtrace, since I don't know how to share them.
> I always had issues with Lexar USB drives.
> One time I got a refund for one of them.
https://bugs.kde.org/show_bug.cgi?id=413418
--- Comment #3 from Andrius Štikonas ---
(In reply to Shubham from comment #2)
> The patch does not apply cleanly on kpmcore master.
it still applies...
$ patch -p1 < 1.patch
patching file src/gui/partwidget.cpp
Hunk #2 succeeded at 95 with
https://bugs.kde.org/show_bug.cgi?id=413418
--- Comment #1 from Andrius Štikonas ---
I've seen this backtrace before but I was never able to reliably reproduce it
myself.
Would you be able to try the following patch (to the kpmcore repository)? It
should print partition()->capac
https://bugs.kde.org/show_bug.cgi?id=413122
Andrius Štikonas changed:
What|Removed |Added
Status|REPORTED|NEEDSINFO
Resolution
https://bugs.kde.org/show_bug.cgi?id=412959
Andrius Štikonas changed:
What|Removed |Added
Status|REPORTED|RESOLVED
Latest Commit
https://bugs.kde.org/show_bug.cgi?id=412959
--- Comment #2 from Andrius Štikonas ---
(In reply to Andrius Štikonas from comment #1)
> Hmm, I checked MBR partition codes, I think it should be 0x0c (MBR with LBA
> addressing)
Here they also use "c":
https://elinux.org/Buildin
https://bugs.kde.org/show_bug.cgi?id=412959
--- Comment #1 from Andrius Štikonas ---
Hmm, I checked MBR partition codes, I think it should be 0x0c (MBR with LBA
addressing)
--
You are receiving this mail because:
You are watching all bug changes.
https://bugs.kde.org/show_bug.cgi?id=412887
Andrius Štikonas changed:
What|Removed |Added
Status|REPORTED|CONFIRMED
Ever confirmed|0
https://bugs.kde.org/show_bug.cgi?id=383127
Andrius Štikonas changed:
What|Removed |Added
CC||andr...@stikonas.eu
--- Comment #45 from
https://bugs.kde.org/show_bug.cgi?id=412376
--- Comment #9 from Andrius Štikonas ---
That's up to Kate's maintainers to approve. For some projects there might make
sense to have separate toolbars.
I'm not too sure about Kate, but it might be that one toolbar comes from
katepart which is reused
https://bugs.kde.org/show_bug.cgi?id=412575
Andrius Štikonas changed:
What|Removed |Added
Version Fixed In||4.0.1
--
You are receiving this mail
https://bugs.kde.org/show_bug.cgi?id=412204
--- Comment #12 from Andrius Štikonas ---
Git commit 6f17476b75185886f57e340bbfb1912b2b62c42e by Andrius Štikonas.
Committed on 05/10/2019 at 11:03.
Pushed by stikonas into branch '4.0'.
Run udevadm settle once more after udevadm trigger.
M +1-0
https://bugs.kde.org/show_bug.cgi?id=411226
Andrius Štikonas changed:
What|Removed |Added
Latest Commit|https://invent.kde.org/kde/ |https://invent.kde.org/kde
https://bugs.kde.org/show_bug.cgi?id=412575
Andrius Štikonas changed:
What|Removed |Added
Latest Commit|https://invent.kde.org/kde/ |https://invent.kde.org/kde
https://bugs.kde.org/show_bug.cgi?id=412575
--- Comment #4 from Andrius Štikonas ---
I'll try to release a new bug fix version of kpmcore too.
--
You are receiving this mail because:
You are watching all bug changes.
https://bugs.kde.org/show_bug.cgi?id=412575
Andrius Štikonas changed:
What|Removed |Added
Resolution|--- |FIXED
Latest Commit
https://bugs.kde.org/show_bug.cgi?id=412575
--- Comment #2 from Andrius Štikonas ---
Ok, I tested this on my system. I'll disable automatic realignment. I slightly
misunderstood your initial comment, so ignore my first comment that it's not
possible. (What's not possible is not mounting btrfs
https://bugs.kde.org/show_bug.cgi?id=412575
Andrius Štikonas changed:
What|Removed |Added
Version|3.3 |4.0.0
--
You are receiving this mail
https://bugs.kde.org/show_bug.cgi?id=412575
Andrius Štikonas changed:
What|Removed |Added
Ever confirmed|0 |1
Status|REPORTED
https://bugs.kde.org/show_bug.cgi?id=412376
Andrius Štikonas changed:
What|Removed |Added
Resolution|WORKSFORME |FIXED
Latest Commit
https://bugs.kde.org/show_bug.cgi?id=412575
--- Comment #1 from Andrius Štikonas ---
Regarding disabling if it's mounted, that's not possible. Btrfs does not
support offline resizing at all, to resize btrfs partition we mount it anyway.
Instead of disabling it, it's better to investigate whether
https://bugs.kde.org/show_bug.cgi?id=412376
--- Comment #5 from Andrius Štikonas ---
Hi, your attached file seems to work for me.
I just copied it over to
/usr/share/kxmlgui5/partitionmanager/partitionmanagerui.rc where my packager
manager installed original version.
I can either commit
https://bugs.kde.org/show_bug.cgi?id=396650
--- Comment #6 from Andrius Štikonas ---
This can be closed. It was fixed some time ago. Sorry, I forgot to close
it.
It's not about full screen support though. The bug was that plasma popup
windows, e.g. kickoff menu or calendar widget were always
https://bugs.kde.org/show_bug.cgi?id=412376
--- Comment #3 from Andrius Štikonas ---
That should be easy to fix.
It's just specified in a text file in XML format:
https://invent.kde.org/kde/partitionmanager/blob/master/src/gui/partitionmanagerui.rc
Do you want to try to fix it? Alternatively
https://bugs.kde.org/show_bug.cgi?id=412376
Andrius Štikonas changed:
What|Removed |Added
Status|REPORTED|RESOLVED
Resolution
https://bugs.kde.org/show_bug.cgi?id=412204
--- Comment #11 from Andrius Štikonas ---
Git commit 467ea50aeb73b975d87a2c9107a04ac21033b048 by Andrius Štikonas.
Committed on 25/09/2019 at 21:33.
Pushed by stikonas into branch 'master'.
Run udevadm settle once more after udevadm trigger.
M +1
https://bugs.kde.org/show_bug.cgi?id=412204
--- Comment #10 from Andrius Štikonas ---
(In reply to Patrick Silva from comment #9)
> Created attachment 122848 [details]
> partition manager can not delete "unknown" partition
>
> I changed my partitioning scheme since I opene
https://bugs.kde.org/show_bug.cgi?id=412204
--- Comment #8 from Andrius Štikonas ---
(In reply to Patrick Silva from comment #6)
> (In reply to Andrius Štikonas from comment #5)
> > (In reply to Patrick Silva from comment #3)
> > > This problem is always reproducible here.
&
https://bugs.kde.org/show_bug.cgi?id=412204
--- Comment #5 from Andrius Štikonas ---
(In reply to Patrick Silva from comment #3)
> This problem is always reproducible here.
>
> If you give me detailed instructions, I can try your fix.
By the way, how detailed instruction do
https://bugs.kde.org/show_bug.cgi?id=412204
--- Comment #4 from Andrius Štikonas ---
Created attachment 122805
--> https://bugs.kde.org/attachment.cgi?id=122805=edit
speculative patch
Can you try to recompile kpmcore with this patch?
--
You are receiving this mail because:
You are watch
https://bugs.kde.org/show_bug.cgi?id=412204
--- Comment #2 from Andrius Štikonas ---
It works for me here.
How reproducible is this on your machine?
I think there might be a race in SfdiskPartitionTable::commit. mkfs tries to
run before block device is available.
Possibly adding another
https://bugs.kde.org/show_bug.cgi?id=411841
Andrius Štikonas changed:
What|Removed |Added
Ever confirmed|0 |1
Status|REPORTED
https://bugs.kde.org/show_bug.cgi?id=411226
Andrius Štikonas changed:
What|Removed |Added
Latest Commit|https://invent.kde.org/kde/ |https://invent.kde.org/kde
https://bugs.kde.org/show_bug.cgi?id=377528
Andrius Štikonas changed:
What|Removed |Added
CC||andr...@stikonas.eu
--- Comment #6 from
https://bugs.kde.org/show_bug.cgi?id=411226
--- Comment #3 from Andrius Štikonas ---
(In reply to Mathew from comment #2)
> Tested this and it's working fine.
> Slight correction: this is significant figures not decimal places
> (https://doc.qt.io/qt-5/qstring.html#argument-formats)
https://bugs.kde.org/show_bug.cgi?id=411559
--- Comment #4 from Andrius Štikonas ---
(In reply to Jonathan Wakely from comment #3)
> Created attachment 122469 [details]
> Output of successful format by gparted
Partition manager also wipes file system signatures, it runs wipefs.
Looks lik
https://bugs.kde.org/show_bug.cgi?id=400540
--- Comment #13 from Andrius Štikonas ---
(In reply to Dal Monico from comment #12)
> Thank you
Do you want to debug this further now that KPM 4.0 is released? Or should I
close this as won't fix?
--
You are receiving this mail because:
https://bugs.kde.org/show_bug.cgi?id=410738
Andrius Štikonas changed:
What|Removed |Added
CC||model...@outlook.com.au
--- Comment #2 from
https://bugs.kde.org/show_bug.cgi?id=411227
Andrius Štikonas changed:
What|Removed |Added
Status|REPORTED|RESOLVED
Resolution
https://bugs.kde.org/show_bug.cgi?id=410738
Andrius Štikonas changed:
What|Removed |Added
Status|REPORTED|RESOLVED
Resolution
https://bugs.kde.org/show_bug.cgi?id=407617
Andrius Štikonas changed:
What|Removed |Added
Status|REPORTED|RESOLVED
Resolution
https://bugs.kde.org/show_bug.cgi?id=410223
--- Comment #1 from Andrius Štikonas ---
I can't reproduce this anymore in KDE Partition Manager 4.0
--
You are receiving this mail because:
You are watching all bug changes.
701 - 800 of 1613 matches
Mail list logo
