Description of problem: system-config-language use #!/bin/sh exec /usr/bin/pkexec /usr/share/system-config-language/system-config-language.py in executable script. Unfortunately using 'exec' cause a double forking issue if starting from mate-control-center, see https://bugzilla.redhat.com/show_bug.cgi?id=972534 . Using '/usr/bin/pkexec /usr/share/system-config-language/system-config-language.py' would fix the issue. Is it possible to change that or is there a technical reason to use 'exec' in the script? Thanks in advance Version-Release number of selected component (if applicable): all fedora branches How reproducible: always Steps to Reproduce: 1. starting mate session 2. open mate-control-center from menu 3. try to start system-config-language
any news?
Is this MATE specific issue or we can reproduce on GNOME desktop environment also?
I don't think because system-config-language don't start from g-c-c in gnome session. From mate's menu system-config-language starts well, it only ocours when starting from m-c-c window. I guess starting from gnome-menu inside classic session works well too (never tested). But did gnome really use system-config-language nowadays?
I do know few people who used to report bugs or provide feedback to me. Some of them are Gnome and others KDE. I don't think there is any other application available that can do the work that system-config-language used to do.
system-config-language starts well from menu in gnome-classic and activity window in gnome-shell in a VM. So yes, it's only a prob in mate session if starting it from m-c-c window. In gnome there is a control-center app called 'region & language' where you can set the language of the session. Maybe the different is that system-config-language change the language system wide.
Created attachment 988938 [details] region & language gnome
Any news in your analysis of the problem? Honestly, i see no reason why you use 'exec' in a one line script.
ping again!
May be unrelated but I can't open s-c-l from gnome-shell overview in F22.
ping?
system-config-language-2.4.1-2.fc22 has been submitted as an update for Fedora 22. https://admin.fedoraproject.org/updates/system-config-language-2.4.1-2.fc22
system-config-language-2.3.0-3.fc21 has been submitted as an update for Fedora 21. https://admin.fedoraproject.org/updates/system-config-language-2.3.0-3.fc21
system-config-language-2.3.0-3.fc20 has been submitted as an update for Fedora 20. https://admin.fedoraproject.org/updates/system-config-language-2.3.0-3.fc20
Package system-config-language-2.3.0-3.fc21: * should fix your issue, * was pushed to the Fedora 21 testing repository, * should be available at your local mirror within two days. Update it with: # su -c 'yum update --enablerepo=updates-testing system-config-language-2.3.0-3.fc21' as soon as you are able to. Please go to the following url: https://admin.fedoraproject.org/updates/FEDORA-2015-4745/system-config-language-2.3.0-3.fc21 then log in and leave karma (feedback).
system-config-language-2.4.1-2.fc22 has been pushed to the Fedora 22 stable repository. If problems still persist, please make note of it in this bug report.
system-config-language-2.3.0-3.fc21 has been pushed to the Fedora 21 stable repository. If problems still persist, please make note of it in this bug report.
system-config-language-2.3.0-3.fc20 has been pushed to the Fedora 20 stable repository. If problems still persist, please make note of it in this bug report.
hm probably I need to revert the change done in system-config-language then...