Forum rules
There are no such things as "stupid" questions. However if you think your question is a bit stupid, then this is the right place for you to post it. Please stick to easy to-the-point questions that you feel people can answer fast. For long and complicated questions prefer the other forums within the support section.
Before you post please read how to get help
I am having the same issue with my install. All was well until recent updates. I can replicate the issue when I view or edit photos. I don't mean to steal this thread but there appear to be a few threads already and I don't have a Nvidia card installed. Here are my specs:
Mod note:
Good! Hang on to that thought, it's a good one.
I have split off your new question into a separate topic; we do not re-use existing topics here. Thanks for your understanding!
If your issue is solved, kindly indicate that by editing the first post in the topic, and adding [SOLVED] to the title. Thanks!
What were the recent updates you installed? Check in Update Manager > View > History of Updates.
What error messages or crash reports are you seeing in the System Reports app?
What app are you using to view/edit photos?
Mod note:
Good! Hang on to that thought, it's a good one.
I have split off your new question into a separate topic; we do not re-use existing topics here. Thanks for your understanding!
No, thank you Moem. The OP's issue was the same one I am having. I know better now.
"None of us is as smart as all of us." Ken Blanchard
What were the recent updates you installed? Check in Update Manager > View > History of Updates.
This issue has been happening for a couple weeks, more so now that I am playing around with wallpapers and family photos. There must be 20+ updates since this began.
This issue has been happening for a couple weeks, more so now that I am playing around with wallpapers and family photos. There must be 20+ updates since this began.
Was a couple of weeks ago when you upgraded from LM20 to LM20.1?
I've seen a couple of people who have noticed they seem to have what appears to be a memory leak with Cinnamon since upgrading. I have not noticed it, but I also run Cinnamon with all the Windows Effects turned off (which might make a difference). Check your memory usage when the issue happens to see if there might be a correlation.
If all your crash reports are the same (other than the time), then just one example is fine. Mint does clean the logs on a weekly basis, so it is possible the list may be shorter when you go back to get the info.
Check your memory usage when the issue happens to see if there might be a correlation.
I just caused the system to crash by opening multiple images (3). When I closed them the system crashed and I am now in fallback mode. I monitored the ram usage and it started at ~24% and climbed to ~ 32%. It is now at ~26%.
"None of us is as smart as all of us." Ken Blanchard
I did not participate in the beta, but it is my understanding those installs did upgrade to become the official version.
It appears you are getting the same error as the other person, but that person was seeing it happen upon start-up, so there may be something different causing it to happen in your case.
~/.xsession-errors is a file which might shed some light on what happens before the crash. It's a text file and there will be time stamps in the file (but not necessarily for every line), so you should be able to see when Cinnamon starts in relation to when you know the crash happened and hopefully see what errors or warnings may have happened before the crash. You can check the file manually or if you just want to see the error lines you can run cat .xsession-errors | grep -i "error".
I have not noticed it, but I also run Cinnamon with all the Windows Effects turned off (which might make a difference).
I turned all the window effects last night and I have not been able to make the system crash tonight. I will give it a hard hit tomorrow with GIMP and see if I can reproduce the issue.
Thanks for all the help so far SMG I really appreciate it.
"None of us is as smart as all of us." Ken Blanchard
cat .xsession-errors | grep -i "error"
Nemo-Share-Message: 23:23:39.420: Called "net usershare info" but it failed: 'net usershare' returned error 255: net usershare: cannot open usershare directory /var/lib/samba/usershares. Error No such file or directory
(cinnamon:1189): Cjs-CRITICAL **: 23:24:41.271: JS ERROR: TypeError: b is null
(cinnamon:1189): Cjs-CRITICAL **: 23:24:50.378: JS ERROR: TypeError: b is null
(cinnamon:1189): Cjs-CRITICAL **: 23:24:58.780: JS ERROR: TypeError: b is null
(cinnamon:1189): Cjs-CRITICAL **: 23:25:04.095: JS ERROR: TypeError: b is null
(cinnamon:1189): Cjs-CRITICAL **: 23:29:37.173: JS ERROR: TypeError: b is null
(cinnamon:1189): Cjs-CRITICAL **: 23:30:44.388: JS ERROR: TypeError: b is null
(cinnamon:1189): Cjs-CRITICAL **: 23:31:17.102: JS ERROR: TypeError: b is null
(cinnamon:1189): Cjs-CRITICAL **: 23:32:24.388: JS ERROR: TypeError: b is null
(cinnamon:1189): Cjs-CRITICAL **: 23:32:25.972: JS ERROR: TypeError: b is null
(cinnamon:1189): Cjs-CRITICAL **: 23:32:34.019: JS ERROR: TypeError: b is null
(cinnamon:1189): Cjs-CRITICAL **: 23:41:28.542: JS ERROR: TypeError: b is null
(cinnamon:1189): Cjs-CRITICAL **: 05:42:39.751: JS ERROR: TypeError: b is null
(cinnamon:1189): Cjs-CRITICAL **: 05:42:40.534: JS ERROR: TypeError: b is null
Nemo-Share-Message: 11:36:30.030: Called "net usershare info" but it failed: 'net usershare' returned error 255: net usershare: cannot open usershare directory /var/lib/samba/usershares. Error No such file or directory
(cinnamon:1189): Cjs-CRITICAL **: 11:42:03.580: JS ERROR: TypeError: b is null
(cinnamon:1189): Cjs-CRITICAL **: 11:42:04.832: JS ERROR: TypeError: b is null
Clutter:ERROR:clutter-actor.c:5944:clutter_actor_dispose: assertion failed: (priv->parent == NULL)
I see errors but I can't make or tails of them. I can do some searching and see what I can dig up.
I see errors but I can't make or tails of them. I can do some searching and see what I can dig up.
Check the time stamps. I only see the last couple which appear to be recent. Did those happen right before the crash? If you restarted Cinnamon, you should see that happen in the file and be able to see what lines in the log happened before it.
As an FYI, I have that same "samba" error in my file too and I am not having crashes.
I did a grep on 'clutter' on my file and I do not have any errors related to it. This is what I get:
Radeon HD 7480D is not supported. It will never work correctly.
I guess switching to MATE is the next course of action.
If the Radeon HD 7480D is not supported, changing to MATE won't help. Linux provides the support and not Cinnamon. Your install has drivers for the Radeon, so I have no idea what that comment from AnonymousFighter was supposed to mean.
