https://bugs.kde.org/show_bug.cgi?id=476025
--- Comment #12 from Eyal ---
But this one is not merged: https://bugsfiles.kde.org/attachment.cgi?id=162566
Should it be merged?
--
You are receiving this mail because:
You are watching all bug changes.
https://bugs.kde.org/show_bug.cgi?id=474160
--- Comment #2 from Eyal ---
Let me know if there's anything that you'd like me to do here! The patch and
testing is pretty straight-forward. I think that the new behavior will be more
inline with valgrind user expectation.
--
You are receiving
https://bugs.kde.org/show_bug.cgi?id=462443
Eyal changed:
What|Removed |Added
Status|NEEDSINFO |RESOLVED
Resolution|WAITINGFORINFO
https://bugs.kde.org/show_bug.cgi?id=462443
--- Comment #2 from Eyal ---
(In reply to Akseli Lahtinen from comment #1)
> Have you encountered this bug again on newer version of dolphin?
>
> Also if you have, can you send a backtrace with debug symbols:
> https://commu
https://bugs.kde.org/show_bug.cgi?id=417993
Eyal changed:
What|Removed |Added
Attachment #162607|0 |1
is obsolete
https://bugs.kde.org/show_bug.cgi?id=417993
--- Comment #13 from Eyal ---
> I think my only question is whether we should "clear" all of data or just
> the value fields of the result and opnds[] of the test_data_t?
> I guess it doesn't matter whether the rest of the test_d
https://bugs.kde.org/show_bug.cgi?id=417993
--- Comment #11 from Eyal ---
Comment on attachment 162608
--> https://bugs.kde.org/attachment.cgi?id=162608
This might fix it, too, but I prefer the other one.
This one is bigger and the other one works just as well so don't use this one.
--
https://bugs.kde.org/show_bug.cgi?id=417993
--- Comment #10 from Eyal ---
Comment on attachment 162608
--> https://bugs.kde.org/attachment.cgi?id=162608
This might fix it, too, but I prefer the other one.
This one is much more convoluted and unnecessary. Just use the other one.
--
https://bugs.kde.org/show_bug.cgi?id=417993
--- Comment #9 from Eyal ---
Created attachment 162619
--> https://bugs.kde.org/attachment.cgi?id=162619=edit
A test case to force this error even on amd64.
This is just for testing purposes. Don't put this into the repo.
--
You are receiv
https://bugs.kde.org/show_bug.cgi?id=417993
--- Comment #8 from Eyal ---
Drawing up the truth table of those two versions of calculating a_min, I find
that only the case when aa is unknown and vaa is 1 make any difference. The
output in the version aa & ~vaa return 0 is aa==x and va
https://bugs.kde.org/show_bug.cgi?id=417993
--- Comment #7 from Eyal ---
Created attachment 162608
--> https://bugs.kde.org/attachment.cgi?id=162608=edit
This might fix it, too, but I prefer the other one.
We refactor the code so that the computation is done before the vbits are
https://bugs.kde.org/show_bug.cgi?id=417993
--- Comment #6 from Eyal ---
Created attachment 162607
--> https://bugs.kde.org/attachment.cgi?id=162607=edit
This might fix the problem and it's the solution that I prefer.
This might fix the problem and it's the solution that I prefer.
After
https://bugs.kde.org/show_bug.cgi?id=417993
--- Comment #5 from Eyal ---
Like I said before: As part of the tests, some vbits get set. However, we need
to clear them again before we compute the expectation or else the expectation
*itself* will have vbits set in it. The expectation should have
https://bugs.kde.org/show_bug.cgi?id=417993
Eyal changed:
What|Removed |Added
CC||eyals...@gmail.com
--- Comment #4 from Eyal
https://bugs.kde.org/show_bug.cgi?id=476025
Eyal changed:
What|Removed |Added
Attachment #162550|0 |1
is obsolete
https://bugs.kde.org/show_bug.cgi?id=476025
--- Comment #8 from Eyal ---
I completed the new tests. Please try adding ppc platforms and test them. I
already added amd64 testing for a few of them.
On Wed, Oct 25, 2023, 09:37 Carl Love wrote:
> https://bugs.kde.org/show_bug.cgi?id=476
https://bugs.kde.org/show_bug.cgi?id=476025
--- Comment #6 from Eyal ---
Created attachment 162550
--> https://bugs.kde.org/attachment.cgi?id=162550=edit
Fix vbits for cmpgtExB where E*B==128
This adds more precise testing to the vbits program. Only amd64 is enabled.
Add .ppc32=1 or .pp
https://bugs.kde.org/show_bug.cgi?id=476025
Eyal changed:
What|Removed |Added
CC||eyals...@gmail.com
--- Comment #5 from Eyal ---
I'll
https://bugs.kde.org/show_bug.cgi?id=432801
--- Comment #68 from Eyal ---
Thanks for doing this! Now this one:
https://bugs.kde.org/show_bug.cgi?id=474160 ?
Eyal
On Tue, Sep 19, 2023 at 11:33 AM Paul Floyd
wrote:
> https://bugs.kde.org/show_bug.cgi?id=432801
>
> Paul Floyd
https://bugs.kde.org/show_bug.cgi?id=432801
--- Comment #65 from Eyal ---
Yeah, I saw that you have been busy with that!
Do you prefer that I go through the process of pushing a branch for CI? I
need to get added with some permissions?
Eyal
On Sun, Sep 10, 2023, 10:02 Paul Floyd wrote
https://bugs.kde.org/show_bug.cgi?id=432801
--- Comment #63 from Eyal ---
I think that you could have used 'git apply' also. Anyway, I hope that the
tests are all passing now and perhaps we can make progress on the patch?
Eyal
On Wed, Sep 6, 2023, 23:39 Paul Floyd wrote:
> ht
https://bugs.kde.org/show_bug.cgi?id=432801
--- Comment #61 from Eyal ---
(In reply to Paul Floyd from comment #59)
> You forgot to update the expecteds (I saw that just the line numbers have
> changed), and I had to convert the text .cpp files into symlinks (does Linux
> / GCC accep
https://bugs.kde.org/show_bug.cgi?id=432801
Eyal changed:
What|Removed |Added
Attachment #136381|0 |1
is obsolete
https://bugs.kde.org/show_bug.cgi?id=474160
--- Comment #1 from Eyal ---
Created attachment 161405
--> https://bugs.kde.org/attachment.cgi?id=161405=edit
patch with working code and unit test
This fixes the issue and adds a unit test. Also here:
https://github.com/eyal0/valgrind/pull/5/fi
https://bugs.kde.org/show_bug.cgi?id=474160
Bug ID: 474160
Summary: If errors-for-leak-kinds is specified,
exit-on-first-error should only exit on one of the
listed errors.
Classification: Developer tools
Product:
https://bugs.kde.org/show_bug.cgi?id=432801
Eyal changed:
What|Removed |Added
Attachment #139036|0 |1
is obsolete
https://bugs.kde.org/show_bug.cgi?id=432801
--- Comment #57 from Eyal ---
I've identified the problem and I hope to have a solution, soon. It is based
on a similar solution for AMD64. Both platforms to not have an xmm shift with
lane size of 8. I'll update the patch and also add test cases
https://bugs.kde.org/show_bug.cgi?id=432801
--- Comment #56 from Eyal ---
I was able to get the tests to build and pass on master by running `sudo
apt-get install libc6-dbg:i386` and `sudo apt-get remove libc6-dbg`. I guess
that this is an x86 and not amd64 problem only?
I'm able
https://bugs.kde.org/show_bug.cgi?id=432801
--- Comment #55 from Eyal ---
(In reply to Eyal from comment #54)
> (In reply to Mark Wielaard from comment #53)
> > (In reply to Eyal from comment #52)
> > > Y'all need CI, I can't even build the master branch. :-(
> >
&
https://bugs.kde.org/show_bug.cgi?id=432801
--- Comment #54 from Eyal ---
(In reply to Mark Wielaard from comment #53)
> (In reply to Eyal from comment #52)
> > Y'all need CI, I can't even build the master branch. :-(
>
> We do have CI against various distros and
https://bugs.kde.org/show_bug.cgi?id=432801
--- Comment #52 from Eyal ---
Y'all need CI, I can't even build the master branch. :-(
--
You are receiving this mail because:
You are watching all bug changes.
https://bugs.kde.org/show_bug.cgi?id=432801
--- Comment #51 from Eyal ---
I'll take a look.
I gotta say, this patch is super annoying. I've been working on it for 2.5
years now? Instead of github, emails. And no CI. :-( I've resorted to my
own personal branch of valgrind with all my fixes
https://bugs.kde.org/show_bug.cgi?id=472879
--- Comment #2 from Eyal ---
Two additional advantages:
1. As Maik has pointed out (in another bug), main-menu items are available as
toolbar actions (ie. can be added as toolbar buttons).
2. Similarly, main-menu items can be assigned keyboard
https://bugs.kde.org/show_bug.cgi?id=472881
Eyal changed:
What|Removed |Added
Summary|Grouping/Versioning: add|Grouping/Versioning: add
|grouping
https://bugs.kde.org/show_bug.cgi?id=472881
--- Comment #12 from Eyal ---
I think it should be standalone.
Regarding priority it's of course your decision. I can only ask you to consider
this:
Digikam has versioning.
Digikam has grouping.
But the two features don't work together.
If I batch
https://bugs.kde.org/show_bug.cgi?id=472881
--- Comment #10 from Eyal ---
Bug 338882 - is mostly ignored from 2014, and it is about *automatic* grouping
(ie. no user intervention).
Bug 318357 - I still don't understand if it covers the Digikam's own
versioning.
--
You are receiving this mail
https://bugs.kde.org/show_bug.cgi?id=472881
--- Comment #8 from Eyal ---
But I asked if the fix for bug 318357 will handle filename_v1, filename_v2,
etc. - you answered it will not.
I'm a bit confused.
--
You are receiving this mail because:
You are watching all bug changes.
https://bugs.kde.org/show_bug.cgi?id=472881
--- Comment #6 from Eyal ---
So why is this a duplicate of the other bug?
I still wish to file a bug to have grouping that supports Digikam's versioning
scheme.
As it is, I can't file this bug because you mark it as a duplicate of another
bug, which
https://bugs.kde.org/show_bug.cgi?id=472884
--- Comment #2 from Eyal ---
Only need to implement grouping function once, and call it from relevant tools.
--
You are receiving this mail because:
You are watching all bug changes.
https://bugs.kde.org/show_bug.cgi?id=472883
--- Comment #2 from Eyal ---
Only need to implement grouping function once, and call it from relevant tools.
--
You are receiving this mail because:
You are watching all bug changes.
https://bugs.kde.org/show_bug.cgi?id=472881
--- Comment #4 from Eyal ---
So the fix for bug 318357 will also group these?
filename.raw
filename_v1.jpg
filename_v2.jpg
--
You are receiving this mail because:
You are watching all bug changes.
https://bugs.kde.org/show_bug.cgi?id=423993
Eyal changed:
What|Removed |Added
CC||e...@zvi.org
--- Comment #7 from Eyal ---
I strongly
https://bugs.kde.org/show_bug.cgi?id=472881
--- Comment #2 from Eyal ---
I understand that technically my suggestion is a private case of a more generic
/ RegEx grouping.
However, from a user perspective, grouping by Digikam's standard versioning
scheme is less error prone than RegEx, priovides
https://bugs.kde.org/show_bug.cgi?id=472884
Bug ID: 472884
Summary: Grouping/Versioning: add Batch Queue Manager option to
automatically group new version with original
Classification: Applications
Product: digikam
Version:
https://bugs.kde.org/show_bug.cgi?id=472883
Eyal changed:
What|Removed |Added
Platform|Other |Archlinux
--
You are receiving this mail because:
You
https://bugs.kde.org/show_bug.cgi?id=472881
Eyal changed:
What|Removed |Added
Platform|Other |Archlinux
--
You are receiving this mail because:
You
https://bugs.kde.org/show_bug.cgi?id=472883
Bug ID: 472883
Summary: Grouping/Versioning: add Image Editor option to
automatically group new version with original
Classification: Applications
Product: digikam
Version: unspecified
https://bugs.kde.org/show_bug.cgi?id=472881
Eyal changed:
What|Removed |Added
Summary|Grouping: add grouping by |Grouping/Versioning: add
|filename
https://bugs.kde.org/show_bug.cgi?id=472881
Bug ID: 472881
Summary: Grouping: add grouping by filename with versioning
Classification: Applications
Product: digikam
Version: unspecified
Platform: Other
OS: Linux
https://bugs.kde.org/show_bug.cgi?id=472879
Bug ID: 472879
Summary: Grouping: add Group to main Items menu
Classification: Applications
Product: digikam
Version: unspecified
Platform: Archlinux
OS: All
Status:
https://bugs.kde.org/show_bug.cgi?id=472878
Bug ID: 472878
Summary: Grouping: add toolbar buttons / actions
Classification: Applications
Product: digikam
Version: unspecified
Platform: Archlinux
OS: All
Status:
https://bugs.kde.org/show_bug.cgi?id=399037
Eyal Rozenberg changed:
What|Removed |Added
Status|NEEDSINFO |REPORTED
Resolution|WAITINGFORINFO
https://bugs.kde.org/show_bug.cgi?id=462443
Bug ID: 462443
Summary: Crash when renaming a file
Classification: Applications
Product: dolphin
Version: 22.08.3
Platform: Archlinux
OS: Linux
Status: REPORTED
https://bugs.kde.org/show_bug.cgi?id=392247
Eyal Rozenberg changed:
What|Removed |Added
Resolution|WAITINGFORINFO |---
Status|NEEDSINFO
https://bugs.kde.org/show_bug.cgi?id=432801
--- Comment #47 from Eyal ---
Any progress here? I see the valgrind is getting new commits all the time.
--
You are receiving this mail because:
You are watching all bug changes.
https://bugs.kde.org/show_bug.cgi?id=432801
--- Comment #45 from Eyal ---
Sure, let me know if I can be of assistance.
This was an actual issue for me with false positives in boost in newer clang.
Boost is quite popular so I imagine that as more people upgrade to newer clang,
maybe more
https://bugs.kde.org/show_bug.cgi?id=432801
--- Comment #41 from Eyal ---
Got it done! Thank you for testing out the code. Try again?
--
You are receiving this mail because:
You are watching all bug changes.
https://bugs.kde.org/show_bug.cgi?id=432801
Eyal changed:
What|Removed |Added
Attachment #138226|0 |1
is obsolete
https://bugs.kde.org/show_bug.cgi?id=432801
--- Comment #37 from Eyal ---
Any further comments? This is fixing a real false positive that users of clang
will experience with reasonable optimization levels.
--
You are receiving this mail because:
You are watching all bug changes.
https://bugs.kde.org/show_bug.cgi?id=370397
--- Comment #4 from Eyal Rozenberg ---
In those screenshot, I see a colored line under the tab. That's not sufficient,
it should be possible to color the whole tab. The line is not noticeable
enough.
--
You are receiving this mail because:
You
https://bugs.kde.org/show_bug.cgi?id=370397
--- Comment #2 from Eyal Rozenberg ---
(In reply to Podagric from comment #1)
> it is now possible to do so.
> could you close this bug?
I'm not using the latest KDE right now, so I can't verify this being the case.
But I won't object if s
https://bugs.kde.org/show_bug.cgi?id=432801
--- Comment #36 from Eyal ---
Oh, I see it now. I must have forgotten to recompile. I've sent the new
patch.
--
You are receiving this mail because:
You are watching all bug changes.
https://bugs.kde.org/show_bug.cgi?id=432801
Eyal changed:
What|Removed |Added
Attachment #137990|0 |1
is obsolete
https://bugs.kde.org/show_bug.cgi?id=432801
--- Comment #34 from Eyal ---
Huh. I don't have any errors on my computer with it. Can you send an example
error from the test? Maybe the location of the conditional jump depends on the
platform...?
--
You are receiving this mail because:
You
https://bugs.kde.org/show_bug.cgi?id=432801
--- Comment #32 from Eyal ---
How does the latest code look? Are all the warnings gone now? Passes tests on
FreeBSD?
--
You are receiving this mail because:
You are watching all bug changes.
https://bugs.kde.org/show_bug.cgi?id=432801
Eyal changed:
What|Removed |Added
Attachment #136599|0 |1
is obsolete
https://bugs.kde.org/show_bug.cgi?id=432801
--- Comment #29 from Eyal ---
Okay. I don't think that I'm using any special features of c nor c++... How
would I know? Is there some test that I can run?
I didn't find any errors when I compiled with -Wall -Werror so I didn't see
that string being
https://bugs.kde.org/show_bug.cgi?id=432801
--- Comment #27 from Eyal ---
Maybe that's with the c code. I wrote a version in c++ which is uses templates
to make the test code much shorter.
Let's focus on just one of them so that I don't have to duplicate too much
work. Do we want c
https://bugs.kde.org/show_bug.cgi?id=432801
--- Comment #25 from Eyal ---
Created attachment 136599
--> https://bugs.kde.org/attachment.cgi?id=136599=edit
patch that supports pcmpgtX for 64/32/16/8 bit testing all lanes and using
templates
This one uses c++ in the test only. It is a m
https://bugs.kde.org/show_bug.cgi?id=432801
--- Comment #24 from Eyal ---
Created attachment 136575
--> https://bugs.kde.org/attachment.cgi?id=136575=edit
patch that supports pcmpgtX for 64/32/16/8 bit
This one is more complex but it supports all the different pcmpgt* instructions
in
https://bugs.kde.org/show_bug.cgi?id=432801
--- Comment #23 from Eyal ---
Generalizing the patch to handle different bit widths would be easy. In fact,
that's why I wrote it using a switch statement with just one case. To
generalize it you just need to add cases into the switch statement. Pretty
https://bugs.kde.org/show_bug.cgi?id=432801
--- Comment #21 from Eyal ---
Will anyone consider the patch? There might be a lot of false positives out
there now that clang is doing this optimization and it would be nice to catch
them before many users waste a lot of time on this.
--
You
https://bugs.kde.org/show_bug.cgi?id=432801
--- Comment #20 from Eyal ---
Created attachment 136381
--> https://bugs.kde.org/attachment.cgi?id=136381=edit
patch with tests
--
You are receiving this mail because:
You are watching all bug changes.
https://bugs.kde.org/show_bug.cgi?id=432801
--- Comment #19 from Eyal ---
Comment on attachment 136346
--> https://bugs.kde.org/attachment.cgi?id=136346
patch for expensive greater than comparisons
Obsolete now.
--
You are receiving this mail because:
You are watching all bug changes.
https://bugs.kde.org/show_bug.cgi?id=432801
Eyal changed:
What|Removed |Added
Attachment #136346|0 |1
is obsolete
https://bugs.kde.org/show_bug.cgi?id=432801
--- Comment #18 from Eyal ---
>Interesting analysis, and a plausible patch; thank you for that. This seems
>like a new trick from LLVM.
Thanks. Yes
>* where's the addition instruction that merges the lanes together? I don't
> see that
https://bugs.kde.org/show_bug.cgi?id=432801
Eyal changed:
What|Removed |Added
Attachment #136346|path for expensive greater |patch for expensive greater
description|than
https://bugs.kde.org/show_bug.cgi?id=432801
--- Comment #16 from Eyal ---
Created attachment 136346
--> https://bugs.kde.org/attachment.cgi?id=136346=edit
path for expensive greater than comparisons
--
You are receiving this mail because:
You are watching all bug changes.
https://bugs.kde.org/show_bug.cgi?id=432801
--- Comment #14 from Eyal ---
A possible solution in Valgrind:
https://github.com/eyal0/valgrind/commit/899ea491e358013579f87e443beff0a30c69e348
This improves Valgrind's check for definedness when doing 32x4 SIMD signed
greater than. It solves
https://bugs.kde.org/show_bug.cgi?id=432801
--- Comment #13 from Eyal ---
https://bugs.llvm.org/show_bug.cgi?id=49372
I hope that LLVM can help us out here! I think that it would be nice.
--
You are receiving this mail because:
You are watching all bug changes.
https://bugs.kde.org/show_bug.cgi?id=432801
--- Comment #12 from Eyal ---
Okay, now I'm back to thinking that it's a valgrind issue. But it's nothing
that valgrind can fix. Here's the problematic asm code:
movd %edx,%xmm2 (1)
punpcklbw %xmm2,%xmm2 (2
https://bugs.kde.org/show_bug.cgi?id=432801
--- Comment #11 from Eyal ---
I'm back to not being sure if this is an llvm issue.
There are a few things at play here. One is sigaction(), which can foul up the
the contents of xmm registers, especially xmm3, which is the only register that
isn't
https://bugs.kde.org/show_bug.cgi?id=432801
--- Comment #9 from Eyal ---
Oops, I spoke to soon. It's a bug in clang. Here's code that you can try:
#include
#include
#include
#include
void foo() {
// Put the garbage number 123 into eax.
// It's caller-saved so no problem
https://bugs.kde.org/show_bug.cgi?id=432801
--- Comment #8 from Eyal ---
Even vgdb isn't helping me. Here's the code that I'm using:
#include
#include
#include
#include
int main()
{
struct sigaction act;
if (sigaction(SIGTERM, 0, ) == 1) {
return 12;
}
if (sigaction(SIGTERM, 0
https://bugs.kde.org/show_bug.cgi?id=432801
--- Comment #7 from Eyal ---
It seems that the issue is the loop. When the length of pattern is more than
8, the code runs a routine that is able to sum 8 chars at a time. It uses xmm
for this. It only enters that code if the number of bytes to sum
https://bugs.kde.org/show_bug.cgi?id=432801
--- Comment #6 from Eyal ---
Here's one that also fails but with a different error:
==12859== Syscall param exit_group(status) contains uninitialised byte(s)
==12859==at 0x492F9D6: _Exit (_exit.c:31)
==12859==by 0x48A2E89: __run_exit_handlers
https://bugs.kde.org/show_bug.cgi?id=432801
Eyal changed:
What|Removed |Added
CC||eyals...@gmail.com
--- Comment #5 from Eyal ---
I have
https://bugs.kde.org/show_bug.cgi?id=409837
Eyal Rozenberg changed:
What|Removed |Added
Resolution|WAITINGFORINFO |WORKSFORME
Status|NEEDSINFO
https://bugs.kde.org/show_bug.cgi?id=409837
--- Comment #4 from Eyal Rozenberg ---
(In reply to Heiko Becker from comment #3)
> As I wrote 2.9.71 (aka 2.10 Alpha1, you can get it from
> https://download.kde.org/unstable/amarok/2.9.71/). git master works too and
> isn't that diffe
https://bugs.kde.org/show_bug.cgi?id=409837
--- Comment #2 from Eyal Rozenberg ---
(In reply to Heiko Becker from comment #1)
Which exact version should I try and build?
--
You are receiving this mail because:
You are watching all bug changes.
https://bugs.kde.org/show_bug.cgi?id=409966
--- Comment #14 from Eyal Rozenberg ---
Ah, I see what you mean. Ok then. That is, I'm not pleased but at least I
understand the rationale of your decisions.
--
You are receiving this mail because:
You are watching all bug changes.
https://bugs.kde.org/show_bug.cgi?id=409966
--- Comment #12 from Eyal Rozenberg ---
Excuse me, but - are you serious? This is the _Amarok_ bug tracking system. You
can't close bugs about the current release and tell people not to use it. If
that's how you feel - terminate your account or stop
https://bugs.kde.org/show_bug.cgi?id=409966
--- Comment #10 from Eyal Rozenberg ---
(In reply to Christophe Giboudeaux from comment #9)
> Doesn't change anything. There's no officially supported Qt5 based amarok
The single current official release of Amarok is 2.9.0. That's the
https://bugs.kde.org/show_bug.cgi?id=409966
Eyal Rozenberg changed:
What|Removed |Added
Resolution|NOT A BUG |---
Status|RESOLVED
https://bugs.kde.org/show_bug.cgi?id=409966
--- Comment #6 from Eyal Rozenberg ---
(In reply to Christophe Giboudeaux from comment #4)
> why ecm ? isn't amarok 2.9 the KDE4 version?
Can you explain the latest exchange of comments? I'm not quite following.
Amarok 2.9 is the current rele
https://bugs.kde.org/show_bug.cgi?id=409966
Eyal Rozenberg changed:
What|Removed |Added
Status|RESOLVED|REOPENED
Ever confirmed|0
Severity: major
Priority: NOR
Component: general
Assignee: amarok-bugs-d...@kde.org
Reporter: eyal...@technion.ac.il
Target Milestone: kf5
I've downloaded and built Amarok 2.9.0 on Devuan Beowulf (= Debian Buster
without systemd) - after installing a whole
https://bugs.kde.org/show_bug.cgi?id=409836
--- Comment #4 from Eyal Rozenberg ---
(In reply to Myriam Schweingruber from comment #3)
> I guessed as much.
It's still a build failure, albeit of the testing code. Aren't you supposed to
change the component or mark it somehow instead of test
https://bugs.kde.org/show_bug.cgi?id=409836
Eyal Rozenberg changed:
What|Removed |Added
Status|NEEDSINFO |REPORTED
Resolution|WAITINGFORINFO
: REPORTED
Severity: normal
Priority: NOR
Component: general
Assignee: amarok-bugs-d...@kde.org
Reporter: eyal...@technion.ac.il
Target Milestone: kf5
SUMMARY
I'm building v2.9.0 on Debian buster (well, actually, Devuan Beowulf, which is
the same
1 - 100 of 119 matches
Mail list logo
