Bug 405773 - Latte is not registered with Crash Reporting Assistant
Summary: Latte is not registered with Crash Reporting Assistant
Status: RESOLVED FIXED
Alias: None
Product: lattedock
Classification: Plasma
Component: application (show other bugs)
Version: git (master)
Platform: Other Linux
: NOR normal
Target Milestone: ---
Assignee: Michail Vourlakos
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2019-03-23 07:03 UTC by trmdi
Modified: 2019-03-23 10:22 UTC (History)
0 users

See Also:
Latest Commit:
Version Fixed In:
Sentry Crash Report:

Attachments
Add an attachment

Note You need to log in before you can comment on or make changes to this bug.
Description trmdi 2019-03-23 07:03:03 UTC 
When I try to report a Latte crash using Crash Reporting Assistant, I see this message: https://i.imgur.com/vpK0Ewp.png
Comment 1 Michail Vourlakos 2019-03-23 08:01:32 UTC 
no idea how this is achieved...
Comment 2 trmdi 2019-03-23 09:32:56 UTC 
(In reply to Michail Vourlakos from comment #1)
> no idea how this is achieved...

The answer from @krop in https://riot.im/app/#/room/%23kde-devel:kde.org:

- that implies changing the KAboutData parameters in app/main.cpp. removing about.setBugAddress(BUG_ADDRESS); on line 296 should be enough
- changing lattedock to latte-dock on line 285 is also needed I think (to match the bugzilla product name)
Comment 3 Michail Vourlakos 2019-03-23 09:58:41 UTC 
(In reply to trmdi from comment #2)
>
> - that implies changing the KAboutData parameters in app/main.cpp. removing
> about.setBugAddress(BUG_ADDRESS); on line 296 should be enough

ok, this is done

> - changing lattedock to latte-dock on line 285 is also needed I think (to
> match the bugzilla product name)

unfortunately this must be avoided because it breaks so many things if it is done, I asked instead from kde sysadmins to rename the product name in bug tracker but I dont know if this is possible now...

https://phabricator.kde.org/T10711
Comment 4 Michail Vourlakos 2019-03-23 10:14:08 UTC 
ok... bugs.kde.org was updated
Comment 5 Michail Vourlakos 2019-03-23 10:22:05 UTC 
it should be fixed with latest commit