-
Notifications
You must be signed in to change notification settings - Fork 732
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
unable to launch Cinnamon system settings in LM20.3 #10591
Comments
|
Attached /var/log/syslog |
|
Running pip3 (pip) with elevated privileges overwrites the system installed packages. |
|
Not so fast... we might want to do something about it. I wanted an issue about this personally so we could look into it during the week. |
|
Can you run: and report the output? Thanks |
|
Q6. Can you run following command & report output: A6. as the output is large, please see attached file |
|
This happened to me too. |
|
I finally managed to fix this; cinnamon-settings should work now In my case I did this for |
|
Many thanks for the fix. Ran both commands and now Your help is much appreciated. Cheers |
|
I propose @clefebvre to put explanation about this issue and it's formulated solution somewhere in 20.3 Upgrade Guide and future Upgrade Guides. |
|
So, even though we have a workaround. We still need to assess how/why the upgrade to 20.3 triggered this situation. And on the cinnamon side of things, we're currently filtering/forbidding the use of .local in cinnamon-settings. We did that to address pip versions of PIL which made it segfault. But most apps don't do that, so we're deviating from normal behavior. I think we need to talk about this again. Obviously there's an issue either way.. whether .local is in or not. Typically here, even though we don't use .local, it still hides away system modules, so that's not OK. |
|
very sound approach Clem, my sentimentals also. |
|
@clefebvre |
|
Hi, I've been trying to work out a script that can resolve this issue when it crops up. Unfortunately it's a bit of a challenge for me to truly reproduce the problem in the first place, so hopefully I can catch someone here to test it (maybe one of you who's skirted around our 'path adjustments'). What I have so far, is it tries to detect modules installed by both the system package manager (like apt or dnf), and those installed by other means, such as pip. It then reinstalls the system versions of these packages. It's non-destructive - it only attempts to reinstall system packages (it won't install or remove anything unless a package has newly-added dependencies or conflicts, which is unlikely). To try it: You'll need pip3 installed - it'll prompt you to do so if necessary. Thanks a lot! |
|
Hi mtwester results of all 3 runs as follows: -------------1st Run------------------------------------ ---------2nd Run below---------------------- ----------3rd Run below-------- hope this helps. happy to assist again if you need me. |
|
@juglanshub The script will always find potential conflicts - it's just comparing names of system and pip packages, and making sure the system ones are where they belong, so when you run cinnamon-settings, and ~/.local and /usr/local packages are forbidden, it will run as it should. You probably had a pip version of pip installed, which is why it didn't prompt you to install python3-pip the first time. The pip version used isn't that important. The issue should have hopefully been fixed after the first run. Thanks! I'll wait for maybe a bit more feedback before making this 'official'. |
|
@mtwebster First I want to really appreciate your work about automating the solution The reason behind these are:
You have to uninstall them first with root privileges using pip, then reinstalling using apt. |
Rilevo lo stesso problema e ho trovato online questa soluzione:Nel file /usr/share/cinnamon/cinnamon-settings/bin/util.py ho commentato le righe 9 e 10: |
|
I'm having the same issue with |
|
@poldon I believe in your case it would be |
Yes, this solution worked for me also. I'm not sure how my installation was different other than maybe being caused by me installing some other application. Also, not sure if it matters, but I'm on a system that has been upgraded with each new release starting with LM 18. Thanks for the solution! |
|
It is never too late to tell @mtwebster that his script works like a charm. I had a problem starting cinnamon-settings because of pytz module, and his script fixed everything. I just had to run it once, and the script offered me to reinstall some Pythong packages. After the reinstallation of the packages, everything started to work again. This is on Mint Cinnamon 20.3. |
|
Hi, I've also encountered the problem of cinnamon-settings failing to run from the menu, I then tried from the cli and get this. However if I run I'm not sure what changed when settings stopped working, but after a little investigation I could 'fix' 90% of the problem. I commented out Looking a bit further back into "/usr/share/cinnamon/cinnamon-settings/cinnamon-settings.py", I see this line, Clearly, I don't know what I'm doing, but it works for the present. I'd appreciate someone informing me what the impact of |
Usually Generally speaking you never want to install anything ever from |
|
@spamegg1 Yes that fixed it, thanks. |
|
Check out PyEnv, I made a tutorial https://forums.linuxmint.com/viewtopic.php?f=42&p=2103213 |
|
Thanks, will do. |
Issue
Background:
Following my comments on 'Linux Mint 20.3 Una Cinnamon release" blog, and at the request of Clem, I am submitting this Cinnamon issue.
Problem:
on 8-Jan-22, I updated from LM20.2 to LM20.3 on my Lenovo x230 laptop, running Cinnamon & Linux kernel 5.4.0-92.
No errors encountered during the update process or after a reboot.
The issue I am experiencing is that since upgrading to LM20.3, I am unable to launch the 'System Settings' or 'System Info' or 'Startup applications' tasks in the toolbar from the bottom left corner LM menu. When I click on any of these 3 icons, nothing happens. No error messages either. Bug happens “always”
Other system functions in the toolbar such at 'System reports' & 'System monitor' & 'System Profiler' are working fine.
'System reports' states 'no problems found' & there are no crash reports. Also. the 'system info' tab displays the details I expect.
All user applications launch OK.
I am partially able to launch 'system settings' from the command line with
$ cinnamon-control-center
This displays a partial systems settings gui with just 4 hardware icons, which will launch the setting, but am unable to see or scroll to any other system settings icons.
Q&A
Q1. What errors do you get when running it from terminal with “cinnamon-settings”?
A1. Command “cinnamon-settings” produces error message “no module named certifi"
Q2. Does installing python3-certifi fix it ?
A2. software manager confirms python3-certifi is already installed. Version is 2019.11.28-1
Q3. you might have a conflict between system python modules and user installed ones (via pip). my guess is that your version of python3-requests is pip’s. Can you try to apt install python3-requests ?
A3. tried installing via 'apt install python3-requests' but message stated python3-requests already newest version and would not install.
Steps to reproduce
Bug happens “always”
Expected behaviour
Expect System settings GUI to launch when icon clicked
Other information
Configuration info, if applicable
Q4. what is the output of “dpkg -l | grep python”
A4. the output is :
Q5. What is the output of “pip freeze”
A5. the output is :
The text was updated successfully, but these errors were encountered: