Bug 22624

Summary:	mate preferred applications function does not allow entering personalized applications
Product:	Mageia	Reporter:	andré blais <andr999>
Component:	RPM Packages	Assignee:	All Packagers <pkg-bugs>
Status:	REOPENED ---	QA Contact:
Severity:	normal
Priority:	Normal	CC:	marja11, ouaurelien
Version:	8
Target Milestone:	---
Hardware:	All
OS:	Linux
Whiteboard:
Source RPM:	mate-control-center-1.18.0-1.mga6.src.rpm	CVE:
Status comment:

Description andré blais 2018-02-17 22:45:30 CET

The mate preferences application, mate-default-applications-properties,
part of mate-control-center,
does not allow entering personalized applications in each category,
despite documentation which says this is possible.

Often a application in a particular category does not appear as an option, and a workaround, if possible, is often awkward.
The documentation indicates that the missing function is much like adding an entry to the menu, thus relatively easy for the average user.

Marja Van Waes 2018-02-18 07:34:27 CET

CC: (none) => marja11
Assignee: bugsquad => tarakbumba

Comment 1 Samuel Verschelde 2018-09-21 09:40:19 CEST

Reassigning to all packagers collectively as the original maintainer is not available anymore (thanks for all your work Atilla!).

Assignee: tarakbumba => pkg-bugs

Comment 2 Aurelien Oudelet 2020-08-16 18:49:55 CEST

Mageia 6 changed to end-of-life (EOL) status on 2019-09-30. It is no longer 
maintained, which means that it will not receive any further security or bug 
fix updates.

Package Maintainer: If you wish for this bug to remain open because you plan 
to fix it in a currently maintained version, simply change the 'version' to 
a later Mageia version.

Bug Reporter: Thank you for reporting this issue and we are sorry that we 
weren't able to fix it before Mageia 6's end of life. If you are able to 
reproduce it against a later version of Mageia, you are encouraged to click 
on "Version" and change it against that version of Mageia.

Although we aim to fix as many bugs as possible during every release's 
lifetime, sometimes those efforts are overtaken by events. Often a more recent
Mageia release includes newer upstream software that fixes bugs or makes them
obsolete.

If you would like to help fixing bugs in the future, don't hesitate to join the
packager team via our mentoring program [1] or join the teams that fit you 
most [2].

[1] https://wiki.mageia.org/en/Becoming_a_Mageia_Packager
[2] http://www.mageia.org/contribute/

Best regards,
Aurélien
Bugsquad Team

Status: NEW => RESOLVED
Resolution: (none) => OLD
CC: (none) => ouaurelien

Comment 3 andré blais 2020-08-16 20:23:49 CEST

It is still a problem with Mageia 7, completely up to date.

Resolution: OLD => (none)
Version: 6 => 7
Status: RESOLVED => REOPENED

Comment 4 Aurelien Oudelet 2021-07-06 13:14:21 CEST

Mageia 7 is EOL since July 1st 2021.
There will not have any further bugfix for this release.

You are encouraged to upgrade to Mageia 8 as soon as possible.

@reporter, if this bug still apply with Mageia 8, please let us know it.

@packager, if you work on the Mageia 7 version of your package, please check the Mageia 8 package if issue is also present. In this case, please fix the Mageia 8 version instead.

This bug report will be closed OLD if there is no further notice within 1st September 2021.

Comment 5 andré blais 2021-07-07 01:48:14 CEST

It is still problem with Mageia 8, completely up to date.

Marja Van Waes 2021-07-07 18:24:02 CEST

Version: 7 => 8