Summary: | test please disregard | ||
---|---|---|---|
Product: | [Applications] drkonqi | Reporter: | RJVB <rjvbertin> |
Component: | general | Assignee: | RJVB <rjvbertin> |
Status: | RESOLVED NOT A BUG | ||
Severity: | wishlist | Keywords: | drkonqi |
Priority: | VLO | Flags: | rjvbertin:
corner_case+
|
Version: | unspecified | ||
Target Milestone: | --- | ||
Platform: | unspecified | ||
OS: | Linux | ||
Latest Commit: | Version Fixed In: | ||
Sentry Crash Report: | |||
Attachments: | support for alternate application suffices |
Description
RJVB
2017-05-11 08:40:26 UTC
You could a mapping to plasma-workspace/drkonqi/data/mappings, otherwise it won't know that "kdevelop5" bugs are to be reported to "kdevelop". Unsure why you are renaming the binary in the first place... That's more or less what I'm trying to do: check for alternate endings in the ProductMapping class. If I'd realised that I couldn't discard a ticket I wouldn't have run a full test (and now I know that the mapping is done as soon as you hit the "report" button so there's no point even in waiting for the backtrace.) Why the rename? I'm trying to standardise to an appended "5" where necessary in my packaging which allows co-existence with KDE4 applications. I'm more surprised by the "kdevelop.bin" entry myself. Created attachment 105481 [details]
support for alternate application suffices
Christoph, could I have broken something with this patch that explains I'm getting an error 143 (process for the bugs.kde.org protocol died unexpectedly)?
I have no idea, René. I am familiar with the bugs, but I never looked at drkonqi or bugzilla code :) |