I mean something that has debug symbols? So the backtrace is “complete” and “helpful” or whatever the kde developers want to successfully fix the bug?
This has been discussed on multiple occasions.
Manjaro does not provide such packages.
The closest you can get is using unstable branch - if it is the same version as upstream Arch then you can use their debug symbols.
5 Likes
not helpful. 
What do mean?
Manjaro does not provide debug packages - so how is it not helpful?
I believe it is very important to understand that in order to provide complete and helpful backtrace - you need to use the lastest applications - meaning your application must match what KDE developers work with - anything else is noise.
1 Like
Look at the Arch wiki.
Manjaro, especially Manjaro stable, uses “outdated” versions - from the point of view of Arch.
The method they provide will simply not work in most cases for Manjaro.
That is just how it is - the reality of the situation.
(use Arch and you’ll have no such problem)
… sounds a little passive aggressive in light of this
2 Likes
KDE Neon updates first… there is a flood of activity on KDE Discuss, they’re on 6.4.3 now.
What use would our debug packages do other than to flood them with noise about our archaic operating system?
There are technical hurdles in rolling releases and limited developer resources. Contributers needing detailed backtraces might need to recompile KWin manually, or simply use dedicated debug repos in other distributions because for KDE Developers, this gap vastly complicates bug reporting from Manjaro users.
So actually, more helpful than not.
Manjaro isn’t Arch, Manjaro isn’t KDE Neon.
3 Likes
So what you are saying basically is, that there’s no point to report any kde bugs from stable branch Manjaro? Oookey then.
Lets be real. Switching to unstable branch would be absurd pre-requisite for most people to try to help devs with bug reporting and debugging their bugs. Sadly.
Not:
no piont
but:
no easy way to do it
If you find bugs in kde on stable branch - chances are very high it has already been fixed upstream.
I agree - it is inconvenient - but that is how stable branch work - stable does not mean bug free - it rather means longer time between changes.
2 Likes
@scotty65 please stop tagging non-solution as solution. you did it already twice. just stop.
Write a personal message - there is no solution mark here that I can see.
1 Like
I did unmark it. twice.
Has your question not been answered satisfactorily?
1 Like
Why? Because you didn’t like the answer?
Your question has adequately been answered by several people. In short…
-
You can only do it by installing Arch’s debug packages, which Manjaro does not carry; and
-
There’s no point, because our versions of the Plasma packages are already outdated by KDE’s standards, and therefore they have no interest in receiving any debugging information from us.
3 Likes
The question has been answered - that’s how you use debug symbols and it’s not going to change anytime soon.
I’ve marked the solution, because it is the solution and that mark is there for the benefit of other users.
Your issue may have been fixed in newer versions, so you’d need to switch to unstable to test using the latest version first anyway, and then you’d need to make a bug report based on the latest version.
Reporting bugs for older versions isn’t helpful unless the devs still support that version. For instance, python has multiple supported versions, so reporting a bug for an older but still supported version makes sense.
EDIT:
You can’t reply, the thread has been closed, so you might as well stop typing. It’s no more useful than reporting a KDE bug from stable.
3 Likes