https://bugs.kde.org/show_bug.cgi?id=416967
kolAflash changed:
What|Removed |Added
CC||kolafl...@kolahilft.de
Status|REPORTED
https://bugs.kde.org/show_bug.cgi?id=416967
soredake changed:
What|Removed |Added
CC||ndrzj1...@relay.firefox.com
--
You are receiving
https://bugs.kde.org/show_bug.cgi?id=416967
--- Comment #22 from nilsocket ---
Forgot to add System Info:
Operating System: Arch Linux
KDE Plasma Version: 5.19.1
KDE Frameworks Version: 5.71.0
Qt Version: 5.15.0
Kernel Version: 5.7.2-arch1-1
OS Type: 64-bit
Processors: 8 × Intel® Core™ i7-8550U
https://bugs.kde.org/show_bug.cgi?id=416967
nilsocket changed:
What|Removed |Added
CC||nilsoc...@gmail.com
--- Comment #21 from nilsocket
https://bugs.kde.org/show_bug.cgi?id=416967
--- Comment #20 from Andrius Štikonas ---
(In reply to Hannus from comment #19)
> I had the same problem. Can you try to leave 1 mb empty before the new
> partition? That seems to be the trick for partitionmanager to not give an
> error when creating a
https://bugs.kde.org/show_bug.cgi?id=416967
Hannus changed:
What|Removed |Added
CC||baggeraa...@gmail.com
--- Comment #19 from Hannus
https://bugs.kde.org/show_bug.cgi?id=416967
Patrick Silva changed:
What|Removed |Added
Status|NEEDSINFO |REPORTED
Resolution|WAITINGFORINFO
https://bugs.kde.org/show_bug.cgi?id=416967
--- Comment #17 from Bug Janitor Service ---
Dear Bug Submitter,
This bug has been in NEEDSINFO status with no change for at least
15 days. Please provide the requested information as soon as
possible and set the bug status as REPORTED. Due to regular
https://bugs.kde.org/show_bug.cgi?id=416967
--- Comment #16 from Patrick Silva ---
here is the output of your commands:
$ sudo sfdisk --force --append /dev/sdd
[sudo] password for myusername:
Welcome to sfdisk (util-linux 2.35.1).
Changes will remain in memory only, until you decide to write
https://bugs.kde.org/show_bug.cgi?id=416967
--- Comment #15 from Andrius Štikonas ---
(In reply to Patrick Silva from comment #14)
> Ok, I have just built master branch of both kpmcore (with your patch) and
> KPM.
> KPM can not create a ntfs partition yet.
Can you try to use sfdisk manually.
https://bugs.kde.org/show_bug.cgi?id=416967
--- Comment #14 from Patrick Silva ---
Ok, I have just built master branch of both kpmcore (with your patch) and KPM.
KPM can not create a ntfs partition yet.
--
You are receiving this mail because:
You are watching all bug changes.
https://bugs.kde.org/show_bug.cgi?id=416967
--- Comment #13 from Patrick Silva ---
(In reply to Andrius Štikonas from comment #12)
> Did you install kpcore 4.1.0 to /usr? It looks like you are trying to
> compile KDE Partition Manager 4.1 with KPMcore 4.0.
Yes.
I built remotes/origin/4.0 branch
https://bugs.kde.org/show_bug.cgi?id=416967
--- Comment #12 from Andrius Štikonas ---
(In reply to Patrick Silva from comment #11)
> Created attachment 126488 [details]
> no device detected
>
> I have applied your patch, but apparently I did something wrong.
> Now KPM does not detect any
https://bugs.kde.org/show_bug.cgi?id=416967
--- Comment #11 from Patrick Silva ---
Created attachment 126488
--> https://bugs.kde.org/attachment.cgi?id=126488=edit
no device detected
I have applied your patch, but apparently I did something wrong.
Now KPM does not detect any device.
I tried
https://bugs.kde.org/show_bug.cgi?id=416967
--- Comment #10 from Andrius Štikonas ---
(In reply to Patrick Silva from comment #9)
> Operating System: Arch Linux
> KDE Plasma Version: 5.18.2
> KDE Frameworks Version: 5.67.0
> Qt Version: 5.14.1
> Kernel Version: 5.4.22-1-lts
Would you be able
https://bugs.kde.org/show_bug.cgi?id=416967
--- Comment #9 from Patrick Silva ---
Operating System: Arch Linux
KDE Plasma Version: 5.18.2
KDE Frameworks Version: 5.67.0
Qt Version: 5.14.1
Kernel Version: 5.4.22-1-lts
--
You are receiving this mail because:
You are watching all bug changes.
https://bugs.kde.org/show_bug.cgi?id=416967
Patrick Silva changed:
What|Removed |Added
CC||bugsefor...@gmx.com
--- Comment #8 from
https://bugs.kde.org/show_bug.cgi?id=416967
--- Comment #7 from Bug Janitor Service ---
Dear Bug Submitter,
This bug has been in NEEDSINFO status with no change for at least
15 days. Please provide the requested information as soon as
possible and set the bug status as REPORTED. Due to regular
https://bugs.kde.org/show_bug.cgi?id=416967
--- Comment #6 from Josh Freeno ---
(In reply to Andrius Štikonas from comment #5)
> (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.
>
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, it works fine.
> >
https://bugs.kde.org/show_bug.cgi?id=416967
--- Comment #4 from Josh Freeno ---
(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, it works fine.
>
> My theory (although I have no strong proof) is that
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 as
https://bugs.kde.org/show_bug.cgi?id=416967
--- Comment #2 from Josh Freeno ---
(In reply to Andrius Štikonas from comment #1)
> What are the errors?
>
> Does "mkfs.ntfs --quick --verbose deviceNode" work?
Screenshot is of what is does every time and I tried this three or four times
but I
https://bugs.kde.org/show_bug.cgi?id=416967
Andrius Štikonas changed:
What|Removed |Added
Status|REPORTED|NEEDSINFO
Resolution|---
24 matches
Mail list logo
