Hi, When i try to do a screenshot (with my keyboard) on my Mageia Mate, i have this error with windows title "Marco" : Il y a eu une erreur lors de l'exécution de mate-screenshot : L'exécution du processus fils « mate-screenshot » a échoué (Aucun fichier ou dossier de ce type) --- Try translate : There is an error for launch mate-screenshot : Starting process file " mate-screenshot" is fail (no file or folder of this...) ---- But i don't found "mate-screenshot" in my package :( thank you
Source RPM: (none) => mate-screenshot
Install mate-utils. Probably task-mate(-minimal?) should pull also mate-utils.
Assignee: bugsquad => tarakbumbaSource RPM: mate-screenshot => task-mate
task-mate requires it. Minimal doesn't and shouldn't.. It's _minimal_ after all :)
CC: (none) => mageia
okay i try this... I do clasic install with mate only. I put feedback at 6:00pm (Paris)
The classical installer use the task-minimal: http://svnweb.mageia.org/packages/cauldron/meta-task/current/SOURCES/compssUsers.pl?view=markup#l169 So if you want package out of box installed you can add them in rpmsrates: http://svnweb.mageia.org/packages/cauldron/meta-task/current/SOURCES/rpmsrate-raw?view=markup#l67
Component: New RPM package request => RPM PackagesSource RPM: task-mate => meta-task
Hi. As Manuel has written it is a choice with the meta-task package. Especially rpmsrate file should be well configured to avoid such complains. Well, that is another issue that should be discussed by devs.
While mate-utils is not broken and can be installed from repos than this bug report is not critical severity. Decreasing severity if you don' t mind.
Hardware: x86_64 => AllSeverity: critical => normal
That said there are two things with this bug report: 1- Classic installer should install mate-utils which includes mate-screenshot. But Mageia 4 is already released, so it is wontfix for Mageia 4. For Cauldron it is fixed and Mageia 5 will come without this issue. 2- User can always install mate-utils seperatly or install task-mate which pulls mate-utils. From this point of view this bug report is invalid. Either case, this bug report should be closed. Matter is closed as resolved-fixed or resolved-wontfix?
Version: 4 => Cauldron
Closing as fixed
Status: NEW => RESOLVEDResolution: (none) => FIXED