https://bugs.kde.org/show_bug.cgi?id=382941
Bug Janitor Service changed:
What|Removed |Added
Status|NEEDSINFO |RESOLVED
Resolution|WAITINGFORINF
https://bugs.kde.org/show_bug.cgi?id=382941
--- Comment #23 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=382941
Justin Zobel changed:
What|Removed |Added
Status|REOPENED|NEEDSINFO
Resolution|---
https://bugs.kde.org/show_bug.cgi?id=382941
Simon Andric changed:
What|Removed |Added
CC||simonandr...@gmail.com
--
You are receiving thi
https://bugs.kde.org/show_bug.cgi?id=382941
--- Comment #21 from Leslie Zhai ---
Git commit 8cf67cf6ec6312fb82cdca729fc03e2acea22989 by Leslie Zhai.
Committed on 15/08/2017 at 01:41.
Pushed by lesliezhai into branch 'master'.
[libk3bdevice] Update comment for modeSense
M +8-5libk3bdevi
https://bugs.kde.org/show_bug.cgi?id=382941
--- Comment #20 from Thomas Schmitt ---
Hi,
some final remarks about the comments:
---
This rumor can be deleted. It is not relevant in any way:
// Some CDs writer retur
https://bugs.kde.org/show_bug.cgi?id=382941
--- Comment #19 from Thomas Schmitt ---
Hi,
i was not really in patch mood yet, but still in the stage of making up
theories.
Nevertheless, the new commit should really fix the problem.
Mark reports in
https://bugs.kde.org/show_bug.cgi?id=382941#c8
https://bugs.kde.org/show_bug.cgi?id=382941
--- Comment #18 from Leslie Zhai ---
Git commit d50a0c30b582aa2fc5cfccea4b87a70adc2d5d81 by Leslie Zhai.
Committed on 14/08/2017 at 08:21.
Pushed by lesliezhai into branch 'master'.
Fix wrong comparison if there are no descriptors.
A patch by Thomas S
https://bugs.kde.org/show_bug.cgi?id=382941
--- Comment #17 from Thomas Schmitt ---
Hi,
the proposed cdrskin run has a wrong redirection sequence.
It must be
cdrskin -V dev=/dev/sr0 >/tmp/cdrskin_scsi_log 2>&1
(I tested mine with "| less". When changing this to "> /tmp/..."
i stepped into
https://bugs.kde.org/show_bug.cgi?id=382941
--- Comment #16 from Thomas Schmitt ---
Hi,
Mark's workaround justifies itself by mere arithmetics. The new "if"
prevents computation from being performed if it would yield 0 or less.
The remaining question is why this computation is made and whether
https://bugs.kde.org/show_bug.cgi?id=382941
--- Comment #15 from Leslie Zhai ---
Git commit 96540735dbcc3189812e6d46cf7d147f006e5654 by Leslie Zhai.
Committed on 14/08/2017 at 07:06.
Pushed by lesliezhai into branch 'master'.
[tests] Remove some testcase might lead UB issue.
Testcase by Matthia
https://bugs.kde.org/show_bug.cgi?id=382941
--- Comment #14 from Matthias Schwarzott ---
(In reply to Leslie Zhai from comment #12)
> Git commit 16576d6fd33fd4fd81f66904d29a4478a91a561f by Leslie Zhai.
> Committed on 14/08/2017 at 03:35.
> Pushed by lesliezhai into branch 'master'.
>
> Revert fr
https://bugs.kde.org/show_bug.cgi?id=382941
--- Comment #13 from Leslie Zhai ---
> Firstly, k3bdeviceglobals.cpp line 215- can revert to:
>
> quint16 K3b::Device::from2Byte(const unsigned char* d)
> {
> if (d == NULL) {
> qWarning() << "Invalid Byte!";
https://github.com/KDE/k3b/com
https://bugs.kde.org/show_bug.cgi?id=382941
Leslie Zhai changed:
What|Removed |Added
CC||scdbac...@gmx.net
--
You are receiving this mail
https://bugs.kde.org/show_bug.cgi?id=382941
--- Comment #12 from Leslie Zhai ---
Git commit 16576d6fd33fd4fd81f66904d29a4478a91a561f by Leslie Zhai.
Committed on 14/08/2017 at 03:35.
Pushed by lesliezhai into branch 'master'.
Revert from{2,4}Byte.
Hi Thomas:
Please help me! I have no idea why n
https://bugs.kde.org/show_bug.cgi?id=382941
andreas.sturmlech...@gmail.com changed:
What|Removed |Added
Resolution|WAITINGFORINFO |---
Status|NEEDSINF
https://bugs.kde.org/show_bug.cgi?id=382941
Mark changed:
What|Removed |Added
Status|REOPENED|NEEDSINFO
Resolution|---
https://bugs.kde.org/show_bug.cgi?id=382941
andreas.sturmlech...@gmail.com changed:
What|Removed |Added
Ever confirmed|0 |1
Resolution|WORKSFORME
https://bugs.kde.org/show_bug.cgi?id=382941
Mark changed:
What|Removed |Added
Status|RESOLVED|VERIFIED
Resolution|WAITINGFORINFO
https://bugs.kde.org/show_bug.cgi?id=382941
andreas.sturmlech...@gmail.com changed:
What|Removed |Added
CC||andreas.sturmlechner@gmail.
https://bugs.kde.org/show_bug.cgi?id=382941
Matthias Schwarzott changed:
What|Removed |Added
CC||z...@gentoo.org
--- Comment #7 from Matth
https://bugs.kde.org/show_bug.cgi?id=382941
Dr. Chapatin changed:
What|Removed |Added
CC||yy...@gmx.com
--
You are receiving this mail be
https://bugs.kde.org/show_bug.cgi?id=382941
--- Comment #6 from Mark ---
(In reply to Leslie Zhai from comment #5)
Spent a couple hours on this but made no progress. Followed the code back to
modeSense trying to see actual results from the drive but didn't help. Your fix
makes perfect sense to me
https://bugs.kde.org/show_bug.cgi?id=382941
--- Comment #5 from Leslie Zhai ---
(In reply to Mark from comment #4)
> Unfortunately the fix causes a new problem. All is fine until opening the
> burn dialog which then says "Please insert an empty disc..." Medium Info
> shows no supported writing s
https://bugs.kde.org/show_bug.cgi?id=382941
Mark changed:
What|Removed |Added
Resolution|FIXED |WAITINGFORINFO
--- Comment #4 from Mark ---
Unfortunate
https://bugs.kde.org/show_bug.cgi?id=382941
Leslie Zhai changed:
What|Removed |Added
Resolution|--- |FIXED
Status|UNCONFIRMED
https://bugs.kde.org/show_bug.cgi?id=382941
--- Comment #2 from Mark ---
Hi Leslie,
Hope it helps:
Thread 1 "k3b" received signal SIGSEGV, Segmentation fault.
0x767148e8 in K3b::Device::from2Byte (d=0x7002 )
at /home/mark/Sources/k3b/libk3bdevice/k3bdeviceglobals.cpp:221
221
https://bugs.kde.org/show_bug.cgi?id=382941
Leslie Zhai changed:
What|Removed |Added
CC||lesliez...@llvm.org.cn
--- Comment #1 from Leslie
28 matches
Mail list logo