Bug 410325 - Discover crashes at launch (in Norwegian Nynorsk locale)
Summary: Discover crashes at launch (in Norwegian Nynorsk locale)
Status: RESOLVED DUPLICATE of bug 409195
Alias: None
Product: Discover
Classification: Applications
Component: discover (show other bugs)
Version: unspecified
Platform: Other Linux
: NOR crash
Target Milestone: ---
Assignee: Dan Leinir Turthra Jensen
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2019-07-28 19:29 UTC by Karl Ove Hufthammer
Modified: 2019-07-29 06:46 UTC (History)
1 user (show)

See Also:
Latest Commit:
Version Fixed In:

Attachments
Add an attachment

Note You need to log in before you can comment on or make changes to this bug.
Description Karl Ove Hufthammer 2019-07-28 19:29:23 UTC 
SUMMARY
When I launch Discover, a (transparent) window briefly appears, and then Discover crashes. But this only seems to happen under a Norwegian Nynorsk (language code: nn) locale, or at least when setting Norwegian Nynorsk to the preferred language.


STEPS TO REPRODUCE
1. Run ‘LANGUAGE=nn plasma-discover’ from the command-line.
2. Wait.


OBSERVED RESULT
A window briefly appears, and then Discover crashes.
The text ‘Segmentation fault (core dumped)’ is shown on the terminal.

EXPECTED RESULT
Discover launch normally, without crashing.


SOFTWARE/OS VERSIONS
Operating System: openSUSE Tumbleweed 20190726
KDE Plasma Version: 5.16.3
KDE Frameworks Version: 5.60.0
Qt Version: 5.13.0
Kernel Version: 5.2.2-1-default
OS Type: 64-bit
Processors: 4 × Intel® Core™ i5-2500 CPU @ 3.30GHz
Memory: 15.6 GiB


ADDITIONAL INFORMATION
Running Discover under a different language (e.g. ‘LANGUAGE=da plasma-discover’) works fine.

But removing the translation file (/usr/share/locale/nn/LC_MESSAGES/plasma-discover.mo) doesn’t help.

This (also) happens on the latest git version of Discover.
Comment 1 Karl Ove Hufthammer 2019-07-29 06:46:43 UTC 
Running
sudo rm -rf /var/cache/app-info/
sudo appstreamcli refresh-cache --force
seems to have helped.

I now believe this bug is just a duplicate of bug #409195.

*** This bug has been marked as a duplicate of bug 409195 ***