33740 killing desktop

zoydberg · September 23, 2020, 8:04pm

My VM and laptop received 33740 today and now i am getting this at power on:

Switched to console, logged in, did startx , got basic gnome working. Seems like its too much for me at this point…

inmanturbo · September 23, 2020, 8:30pm

Same issue here.

journalctl -f

only shows

nuc cbc_lifecycle[480]: waiting for /dev/cbc-lifecycle

twice per second

inmanturbo · September 23, 2020, 8:46pm

philip_g · September 24, 2020, 1:52am

Same issue. I feel better. I thought I had broke it. Relieved it wasn’t me!

hsehdar · September 24, 2020, 5:02am

Gnome update from 3.36 to 3.38 in 33730 could be the broken build. I guess only.

Go to another tty
Log in
Executed swupd repair -V 33720 --force --picky command and restored to 33720 which was working normally.

technician · September 24, 2020, 5:37am

Thank you, hsendar, for your post,

the same sitaution after update,
reapair to previous 33720 version work.
You save my day!

mpala · September 24, 2020, 7:33am

Same issue.
journalctl -f sent back :

NetworkManager[378]: ((shared/nm-glib-aux/nm-time-utils.c:263)): assertion ‘’ failed

mpala · September 24, 2020, 7:50am

Thank you Hsehdar
You same my day too !!

technician · September 24, 2020, 9:27am

FYI:

hsehdar · September 24, 2020, 9:47am

Excitedly upgraded to see Gnome 3.38 and sadly reverted.

@ahkok As day progresses would there be fixed builds?

bz1234 · September 24, 2020, 4:41pm

Same issue after upgrade to 33740

inmanturbo · September 24, 2020, 5:07pm

It’s not likely there will be a release right away, and no changes will go out until the next release.

It looks like they will be testing builds with another version of glibc over the next day or two to prepare a fix for the next release.

philip_g · September 24, 2020, 5:14pm

So, since I am running CL as a dual-boot with Win10Pro, Win10Pro first, at the end of the day, does this mean I will have to do a clean reinstall, or is there some other way to fix my installation? From what I’m seeing, a reinstall will be necessary. Is there another way?

The_Peaceful · September 24, 2020, 6:24pm

Same this happened to when I tried nvidia drivers but got fucked thanks for the fix btw

philip_g · September 24, 2020, 11:06pm

I followed these instruction. Use control+alt+f5 (or another f-key) to access command prompt (tty). Thanks!

zoydberg · September 25, 2020, 5:38pm

Be careful , swupd repair is damaged my vmware workstation installation and it wasnt so easy to repair. Seems like some python libs installed with sudo was wiped too.

doct0rHu · September 25, 2020, 8:51pm

Yep, this happens.
So I suggest everyone to install pyenv

inmanturbo · September 25, 2020, 10:19pm

as @doct0rHu suggested or

sudo swupd repair [options] --picky --picky-whitelist=/usr/lib/python

https://docs.01.org/clearlinux/latest/guides/clear/swupd.html#example-3-verify-and-correct-system-file-mismatch

inmanturbo · September 25, 2020, 10:27pm

github.com/clearlinux/swupd-client

add a check for an /etc/swupd/picky_repair.d/*.whitelist (or similar) for whitelisting

opened 06:20PM - 14 Jun 20 UTC

inmanturbo

enhancement

Cheers everyone. I have a little idea here.I might have more to add here later. …I just wanted to bounce this off you first. So I'm simply opening this issue so that we have a place to discuss it. System hackers and rogue devs will constantly be pushing at the bounds of swupd and the stateless design. Of course you want to use it, but you also want to be able to harness it. Currenty, whitelisting a file or directory for swupd can done by creating a config under /etc/swupd/ and adding it to the picky_whitelist here: ``` [repair] # Any path completely matching the POSIX extended regular expression is ignored # by --picky, matched directories get skipped (string value) # Example: /var|/etc/machine-id # Default: /usr/lib/modules|/usr/lib/kernel|/usr/local|/usr/src #picky_whitelist=[RE] ``` And/or in the same file under [diagnose]. As is touched on [here](https://github.com/clearlinux/swupd-client/blob/master/docs/swupd.1.rst#files). # The Problem - Having the whitelist represented by a single posix string can be cumbersome and difficult to manage - Automatically updating the whitelist requires all sorts of sed magic ## The Proposal - Include /etc/swupd/picky_diagnose.d/*.whitelist - Include /etc/swupd/picky_repair.d/*.whitelist - ensure swupd will follow symlinks Users and admins can then easily automatically update their diagnose and repair whitelists with commands, scripts or policies by adding a symlink or file to their respective directories. i.e: ```bash sudo mkdir -p /etc/swupd/{whitelists-available/,picky_repair.d/} ``` ```bash echo "/usr/lib/python" | sudo tee -a /etc/swupd/whitelists-available/python.whitelist ``` ```bash sudo ln -s /etc/swupd/whitelists-available/python.whitelist /etc/swupd/picky_repair.d/ ``` Possibly more on this later. Thanks for taking a look at it and may all your coding be stress and bug free!