FS#60877 - Cinnamon 4.0.2-1 package breaks completely

Attached to Project: Community Packages
Opened by Swâmi Petaramesh (petaramesh) - Wednesday, 21 November 2018, 13:54 GMT
Last edited by Eli Schwartz (eschwartz) - Wednesday, 21 November 2018, 15:58 GMT
Task Type Bug Report
Category Packages
Status Closed
Assigned To Eli Schwartz (eschwartz)
Architecture All
Severity High
Priority Normal
Reported Version
Due in Version Undecided
Due Date Undecided
Percent Complete 100%
Votes 0
Private No

Details

Description:

Upgrading Cinnamon from 4.0.1-1 to 4.0.2-1 on my system breaks it completely.

Nothing usable comes up when opening the session, the system is unusable (in the GUI).

Downgrading to Cinnamon 4.0.1-1 fixes the issue.

The issue is unrelated to other Cinnamon packages : it's the Cinnamon package itself that breaks it all.
The settings-daemon, nemo, and muffin packages can be upgraded to 4.0.2-1 without problem.

On my system, the issue is perfectly isolated to Cinnamon 4.0.2-1, and reproductible.

Kind regards.
This task depends upon

Closed by  Eli Schwartz (eschwartz)
Wednesday, 21 November 2018, 15:58 GMT
Reason for closing:  Not a bug
Additional comments about closing:  The problem lies in thirdparty applet code.
Comment by Eli Schwartz (eschwartz) - Wednesday, 21 November 2018, 14:44 GMT
  • Field changed: Status (Unconfirmed → Assigned)
  • Field changed: Architecture (x86_64 → All)
  • Field changed: Severity (Critical → High)
  • Task assigned to Eli Schwartz (eschwartz)
Clearly not critical ("System crash, severe boot failure that is likely to affect more than just you, or an exploitable security issue in either a core or outward-facing service package"), as you can successfully use the tty to downgrade.

As for your issue itself, it works for me and a lot of other people. A perfectly reproducible issue that I cannot reproduce, would be endlessly easier to reproduce if you provided reproduction info:

- Coredumps? Logfiles (~/.xsession-errors, and ~/.cinnamon/glass.log)?

- Does it work if you use a new user without any pre-existing configuration? If so, what happens when you disable selected applets and re-upgrade to cinnamo 4.0.2?

- What happens when you update the multicore-sys-monitor applet, which is known to be broken on cinnamon 4.0.2 due to being incompatible with the new NetworkManager code, and has an update to fix that?

...

Hint: I'm 99% sure multicore-sys-monitor or some other applet which is incompatible with the newer NetworkManager code, is to blame. And applets are not my problem -- you need to check if the applet is updated, and if not, speak to the applet developer.
Comment by Swâmi Petaramesh (petaramesh) - Wednesday, 21 November 2018, 15:09 GMT
Hi,

I had put it as « critical » because I know several friends of mine who will be at a complete loss if their machine boots to a completely unusable GUI...

Anyway you were right about multicore-sys-monitor, that was it.

I didn't expect it because it's the first time that a Cinnamon upgrade breaks it completely on my system, and I wounldn't have expected a "newly incompatible" applet to completely prevent the GUI from starting up without any kind of error message or failsafe feature...

Well anyway that's fixed here. Thanks for your help and suggestion. I believe this bug can be closed (but I believe others will fall from this cliff as I did...)

Kind regards.
Comment by Eli Schwartz (eschwartz) - Wednesday, 21 November 2018, 15:57 GMT
The applet calls networkmanager functions which are no longer linked, and that is what is crashing. There *are* error messages, but error messages for your graphical user interface completely crashing, will be logfiles, not graphical user interface popups.

Anyway, future versions of cinnamon should include a blacklist for these applets: https://github.com/linuxmint/Cinnamon/pull/8050

Loading...