https://bugs.kde.org/show_bug.cgi?id=370384
--- Comment #22 from Vishal Rao ---
Just FYI, got this version: 2.2.1+p16.04+git20161026.1000-0 in Neon dev
unstable update just now and it seems to be working okay.
--
You are receiving this mail because:
You are watching all
https://bugs.kde.org/show_bug.cgi?id=370384
--- Comment #21 from Andrius Štikonas ---
Just a small update:
Looks like partitionmanager packaging repository disappeared, that's there were
no newer snapshots of partitionmanager for a month...
The reason for disappearance
https://bugs.kde.org/show_bug.cgi?id=370384
Andrius Štikonas changed:
What|Removed |Added
Status|UNCONFIRMED |RESOLVED
https://bugs.kde.org/show_bug.cgi?id=370384
--- Comment #19 from Andrius Štikonas ---
(In reply to Emre Unlu from comment #18)
> I can reproduce this easily on KDE neon dev. ed. -stable and can get logs if
> needed.
dev stable edition has the same package as dev unstable
https://bugs.kde.org/show_bug.cgi?id=370384
Emre Unlu changed:
What|Removed |Added
CC||e...@eunlu.com
--- Comment #18
https://bugs.kde.org/show_bug.cgi?id=370384
--- Comment #17 from Vishal Rao ---
Just an update that while the issue occurs on my updated Neon dev unstable
edition, it does not occur on a freshly installed neon user edition 5.8.2 at
this time.
--
You are receiving this mail
https://bugs.kde.org/show_bug.cgi?id=370384
--- Comment #16 from Vishal Rao ---
I have built dummy backend also as part of kpmcore and noted both the default
partitionmanager binary and my built one both try to load the backends from
/usr/lib/x86.../qt5/plugins folder, so I
https://bugs.kde.org/show_bug.cgi?id=370384
--- Comment #15 from Andrius Štikonas ---
(In reply to Vishal Rao from comment #13)
> I should mention if I run my local build of partitionmanager/kpmcore it does
> not crash, not sure if it's because I made a debug build. But when
https://bugs.kde.org/show_bug.cgi?id=370384
--- Comment #14 from Andrius Štikonas ---
(In reply to Vishal Rao from comment #13)
> I should mention if I run my local build of partitionmanager/kpmcore it does
> not crash, not sure if it's because I made a debug build. But when
https://bugs.kde.org/show_bug.cgi?id=370384
--- Comment #13 from Vishal Rao ---
I should mention if I run my local build of partitionmanager/kpmcore it does
not crash, not sure if it's because I made a debug build. But when I run the
one that came installed in /usr/bin I get
https://bugs.kde.org/show_bug.cgi?id=370384
--- Comment #12 from Vishal Rao ---
While trying to install source and building/debugging (not much success here,
newbie) I noticed my stacktrace now has Device::setIconName() call as follows.
doing a quick grep, it looks like only
https://bugs.kde.org/show_bug.cgi?id=370384
--- Comment #11 from Vishal Rao ---
In the original reporter's (and mine) stacktrace it seems to indicate operator=
for QString when it's trying to read/set Device::deviceNode() so something
about scanning an m.2 device (mine is
https://bugs.kde.org/show_bug.cgi?id=370384
--- Comment #10 from Andrius Štikonas ---
Hi Ben,
Isn't m.2 drive nvme? I thought that's what nvme is...
Backtrace points to line
QListWidgetItem(QIcon::fromTheme(d.iconName()).pixmap(IconSize(KIconLoader::Desktop)),
https://bugs.kde.org/show_bug.cgi?id=370384
--- Comment #9 from Ben Klopfenstein ---
Additionally, running at the command line suggests this may be due to missing
SMART support:
benklop@Thinkpad:~$ sudo partitionmanager
QStandardPaths: XDG_RUNTIME_DIR not set, defaulting to
https://bugs.kde.org/show_bug.cgi?id=370384
--- Comment #8 from Ben Klopfenstein ---
Created attachment 101709
--> https://bugs.kde.org/attachment.cgi?id=101709=edit
Additional backtrace output
My backtrace is slightly different, if only because I have more debugging
https://bugs.kde.org/show_bug.cgi?id=370384
Ben Klopfenstein changed:
What|Removed |Added
CC||benk...@gmail.com
---
https://bugs.kde.org/show_bug.cgi?id=370384
--- Comment #4 from Vishal Rao ---
Correction to my previous comment "was trying to format the pen drive when came
across this issue" - I didn't write correct - I meant to say I also faced this
issue during startup of partition
https://bugs.kde.org/show_bug.cgi?id=370384
--- Comment #6 from Andrius Štikonas ---
(In reply to Vishal Rao from comment #4)
> Correction to my previous comment "was trying to format the pen drive when
> came across this issue" - I didn't write correct - I meant to say I
https://bugs.kde.org/show_bug.cgi?id=370384
--- Comment #5 from Vishal Rao ---
Output of running "sudo fdisk -l" minus the snipped sections of /dev/ramX
items: https://paste.kde.org/p1fbzr2po
--
You are receiving this mail because:
You are watching all bug changes.
https://bugs.kde.org/show_bug.cgi?id=370384
--- Comment #3 from Vishal Rao ---
I faced the same issue. I have Neon 5.8 dev unstable edition, same backtrace as
original reporter's. I have a SATA SSD, an NVMe m.2 SSD, an HDD, an external
USB HDD, and a USB pen drive plugged
https://bugs.kde.org/show_bug.cgi?id=370384
Vishal Rao changed:
What|Removed |Added
CC||vishal...@gmail.com
---
https://bugs.kde.org/show_bug.cgi?id=370384
--- Comment #1 from Andrius Štikonas ---
I can't reproduce this on Neon User Edition running on VirtualBox. Can you
provide any more info? What devices or partitions are there?
--
You are receiving this mail because:
You are
22 matches
Mail list logo