https://bugs.kde.org/show_bug.cgi?id=428844
Harald Sitter changed:
What|Removed |Added
Latest Commit|https://invent.kde.org/plas |https://invent.kde.org/plas
|
https://bugs.kde.org/show_bug.cgi?id=428844
Harald Sitter changed:
What|Removed |Added
Latest Commit||https://invent.kde.org/plas
|
https://bugs.kde.org/show_bug.cgi?id=428844
--- Comment #16 from Kwon-Young Choi ---
(In reply to Harald Sitter from comment #15)
> (In reply to Kwon-Young Choi from comment #13)
> > (In reply to Harald Sitter from comment #12)
> > > Kind of. The data we care about is available so we could still
https://bugs.kde.org/show_bug.cgi?id=428844
--- Comment #15 from Harald Sitter ---
(In reply to Kwon-Young Choi from comment #13)
> (In reply to Harald Sitter from comment #12)
> > Kind of. The data we care about is available so we could still show the
> > device, the output you posted suggests o
https://bugs.kde.org/show_bug.cgi?id=428844
Bug Janitor Service changed:
What|Removed |Added
Status|REPORTED|ASSIGNED
Ever confirmed|0
https://bugs.kde.org/show_bug.cgi?id=428844
--- Comment #13 from Kwon-Young Choi ---
(In reply to Harald Sitter from comment #12)
> Kind of. The data we care about is available so we could still show the
> device, the output you posted suggests our timeout is just too short (well,
> it's 30 secon
https://bugs.kde.org/show_bug.cgi?id=428844
Harald Sitter changed:
What|Removed |Added
Resolution|WAITINGFORINFO |---
Status|NEEDSINFO
https://bugs.kde.org/show_bug.cgi?id=428844
--- Comment #11 from Kwon-Young Choi ---
(In reply to Harald Sitter from comment #10)
> Thanks. There's something weird though...
>
> > "exit_status": 4
>
> shouldn't be filtered right now, so there must be something else going on
> additionally.
>
>
https://bugs.kde.org/show_bug.cgi?id=428844
--- Comment #10 from Harald Sitter ---
Thanks. There's something weird though...
> "exit_status": 4
shouldn't be filtered right now, so there must be something else going on
additionally.
It'd be great if you could get me the output of
`QT_LOGGING_R
https://bugs.kde.org/show_bug.cgi?id=428844
--- Comment #9 from Kwon-Young Choi ---
(In reply to Harald Sitter from comment #8)
> You'll want to take this upstream https://www.smartmontools.org/#BugReports
> this is either a bug in smartmontools or, I guess more likely, the drive
> firmware itsel
https://bugs.kde.org/show_bug.cgi?id=428844
Harald Sitter changed:
What|Removed |Added
Resolution|FIXED |WAITINGFORINFO
--- Comment #8 from Harald Sitte
https://bugs.kde.org/show_bug.cgi?id=428844
--- Comment #7 from Kwon-Young Choi ---
I have just run the dell diagnostics on my laptop and the smart, dst short and
long test all passed without any problems.
--
You are receiving this mail because:
You are watching all bug changes.
https://bugs.kde.org/show_bug.cgi?id=428844
Kwon-Young Choi changed:
What|Removed |Added
Resolution|WAITINGFORINFO |FIXED
--- Comment #6 from Kwon-Young Choi --
https://bugs.kde.org/show_bug.cgi?id=428844
Justin Zobel changed:
What|Removed |Added
Resolution|FIXED |WAITINGFORINFO
--- Comment #5 from Justin Zobel
https://bugs.kde.org/show_bug.cgi?id=428844
Kwon-Young Choi changed:
What|Removed |Added
Resolution|WAITINGFORINFO |FIXED
--- Comment #4 from Kwon-Young Choi --
https://bugs.kde.org/show_bug.cgi?id=428844
Justin Zobel changed:
What|Removed |Added
Resolution|--- |WAITINGFORINFO
Status|REPORTED
https://bugs.kde.org/show_bug.cgi?id=428844
--- Comment #2 from Kwon-Young Choi ---
ok, I don't really know what to do to understand what is not working on my
system.
Does plasma-disks has log somewhere I could get ?
Maybe it will tell us what is going wrong ?
--
You are receiving this mail be
https://bugs.kde.org/show_bug.cgi?id=428844
Justin Zobel changed:
What|Removed |Added
CC||justin.zo...@gmail.com
--- Comment #1 from Justi
18 matches
Mail list logo
