Bug 32474

Summary: the desktop-file seems to be incorrect
Product: Mageia Reporter: r rbr <mageia9jul14rbr>
Component: RPM PackagesAssignee: Mageia Bug Squad <bugsquad>
Status: RESOLVED FIXED QA Contact:
Severity: normal    
Priority: Normal CC: marja11
Version: 8   
Target Milestone: ---   
Hardware: All   
OS: Linux   
Whiteboard:
Source RPM: malcontent-0.10.0-1.mga8.x86_64.rpm CVE:
Status comment:

Description r rbr 2023-11-01 10:26:44 CET
Description of problem:

the desktop file org.freedesktop.MalcontentControl.desktop seems to mix-up UK and RU translations

Version-Release number of selected component (if applicable):

I have noticed this in MGA 7 and MGA 8

How reproducible:

Install
 malcontent-0.10.0-1.mga8.x86_64.rpm
and have a look at
 /usr/share/applications/org.freedesktop.MalcontentControl.desktop 
specific the translations

Keywords[uk]=parental controls;screen time;app restrictions;web browser restrictions;oars;usage;usage limit;kid;child;батьківський контроль;час за комп'ютером;обмеження програм;обмеження інтернету;користування;використання;обмеження користування;дитина;дитячий;
Comment 1 Dick Gevers 2023-11-01 10:38:06 CET
English should be en or en-GB
[uk]stands for Ukrainian which the Cyrillic parts appears to be. According to google translate that is not Russian.
---
Slava Ukraini !
Comment 2 r rbr 2023-11-01 10:54:34 CET
Indeed I did incorrectly read the desktop file.
This desktop file is able to crash kmenuedit and konqueror from the trinity-desktop r14.9 and r14.10, and I assumed the error was with this desktop-file, but now I am not sure about that...
Comment 3 Marja Van Waes 2023-11-01 14:09:42 CET
(In reply to r rbr from comment #2)
> Indeed I did incorrectly read the desktop file.
> This desktop file is able to crash kmenuedit and konqueror from the
> trinity-desktop r14.9 and r14.10, and I assumed the error was with this
> desktop-file, but now I am not sure about that...

Do we have trinity-desktop packaged??  If so, which Mageia package supplies it?

CC: (none) => marja11

Comment 4 r rbr 2023-11-01 14:43:49 CET
Mageia does not
...not yet...?
...unfortunately...
does not have a trinity desktop package.

trinity desktop can be obtained here:

https://www.trinitydesktop.org/

and installation instrucations for MAGEIA are here:

https://wiki.trinitydesktop.org/Category:Documentation#Installing_from_a_Package_Manager

It works good with Mageia, already since MGA2,
except for this 1 desktop-file,
and I started this bug-case with the assumption that the problem was with this desktop-file.
Comment 5 Marja Van Waes 2023-11-01 15:34:21 CET
(In reply to r rbr from comment #4)
> Mageia does not
> ...not yet...?
> ...unfortunately...
> does not have a trinity desktop package.
> 
> trinity desktop can be obtained here:
> 
> https://www.trinitydesktop.org/
> 
> and installation instrucations for MAGEIA are here:
> 
> https://wiki.trinitydesktop.org/Category:
> Documentation#Installing_from_a_Package_Manager
> 
> It works good with Mageia, already since MGA2,
> except for this 1 desktop-file,
> and I started this bug-case with the assumption that the problem was with
> this desktop-file.

Can you please try to reproduce this issue in Mageia 9, in Plasma KDE without 3rd party software installed?

If it crashes there, too, then please give the exact steps for us to reproduce the issue.

Ever confirmed: 1 => 0
Status: NEW => UNCONFIRMED

Marja Van Waes 2023-11-01 15:34:34 CET

Status: UNCONFIRMED => NEEDINFO
Ever confirmed: 0 => 1

Comment 6 sturmvogel 2023-11-01 18:10:26 CET
1. The desktop file comes from upstream malcontentcontrol
2. It is no "issue" that the keyword part in the desktop file have a mixed translation. Also ca, de, cz_TW and others have a mixed keyword
3. The desktop file does not crash konqueror from Mageia 9 (neither whilst opening nor executing the desktop file).
4. A desktop file is not related to kmenuedit and can not be used with it.



So this looks like a problem with Trinity Desktop and should be reported there. As Trinity is not supported by Mageia, there is nothing what can be done.

If you are concerned by the mixed translations in the malcontentcontrolfile, you should also report it upstream.
Comment 7 r rbr 2023-11-01 18:49:39 CET
Agreed. It is not a MAGEIA issue.

Resolution: (none) => FIXED
Status: NEEDINFO => RESOLVED