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
#33740 crash at boot #2133
Comments
Can confirm. The wayland session will crash to gdm, which will then try to fall back to the x session. This then crashes with an "oh no. something went wrong" message on the white screen. The Metacity Fallback session works. But if I try to start GDM by itself, GDM will also give me the "oh no" message. Tried downgrading to 33720 with |
Update 33740 failed to boot. |
Downgrading to 33720 did work for me luckily. |
33720 did not work for me, but 33710 did. Go figure. In either case, this is a pretty serious issue. |
Same issue here. Haven't tried dowgrading yet. |
looks like the core issue here is the gnome upgrade. switching to console and |
sudo swupd autoupdate --disable shoulld work no? sudo swupd autoupdate --enable also startx from commandline works. |
gnome-tweaks # or any shell extension
|
|
Would recommend first running
To see what changes will be made
|
Picky downgrade to 33720 worked for me.
gjs dumped core with 33740 journalctl output (pretty long)gnome-shell:
gjs:
|
Comment/Close this issue when they push a working update. Thanks in advance. |
@ahkok has anyone looked at this yet? |
I got the crash screen from GDM, looks like the same issue? I can see in the logs a segfault for Gnome Shell
|
GNOME 3.38 was integrated in release 33740, and this crash is certainly related to that update. After initial investigation, I suspect that gjs 1.66.0 is not compatible with glib 2.66.0; some of its unit tests fail when built with glib 2.66.0 (but not with glib 2.64.5), and some of the test error messages are identical to the ones we are seeing at bootup beginning with release 33740. If I rebuild gjs with glib 2.64.5 as a build dependency, those errors disappear, and all unit tests pass. Similar unit test result improvements appear for gnome-shell when it is built with the rebuilt gjs in the environment. I will do some testing on a live Clear Linux system tomorrow, and if my suspicion is correct, we will downgrade glib to 2.64.5 (and do any rebuilds, likely for gjs followed by gnome-shell at a minimum). |
Testing should be done before any release on at least 20+ different hardware systems. We had several of these no-boot issues now with CL over the past months, you need to implement a proper release test plan to prevent such avoidable situations in the future .. |
I tried the repair command but it also breaks other stuffs like: module for RTL8822BE USB wireless adapter can't be loaded, fonts rendering broke, USB DAC doesn't work. The good thing is this isn't a work machine. |
try swupd repair --picky |
I tried the same commands in #2133 (comment) |
Yep. Same on two machines with wildly different setups (one Intel-only hw, one with Intel+NVIDIA) both borked, both work machines. This is a pretty critical issue. Aren't the failing tests supposed to be a red flag for pushing this kind of stuff? |
@namm2 please check that you are still running the correct kernel |
@amonforstmann I'm using lts2019 kernel version 5.4.65 |
I checked the logs and it
On the fonts issue, I checked the command's output and it looks like it removed a lot of files in |
I am facing the exactly same issue and I can see that it has generated core dumps for 3 binaries. |
also hit this. downgrade fixed it |
33760 is working |
33760 still not booting on USB drive with Luks. I noticed when pressing e during boot, that the kernel version still is listed as 5.8.9-* and not 5.8.11-?? for 33760, so something is still broken .. |
sudo swupd check-update |
33760 does indeed boot and load a desktop. |
gnome-photos still dumps core
|
Indeed, switching to a different gtk style/theme resolved this. |
Can confirm that the update to 33760 mostly fixes the shell. But I am also having some glitches with my non-standard theme: in my case, Arc. |
@jumpinggoofballs Also check update for your theme. |
Working now as of latest update. |
The theme files are copied over from a flatpak installation of the theme (not available in the repo), and I think it hasn't been updated in any case since 3.22 But I don't see why a theme should give visual artefacting. I understand styling classes going awry and such, but the kind of artefacting that you get from buggy graphics drivers? Why would that have anything to do with a particular css theme? |
@jumpinggoofballs |
im closing it as its resolved in 33760 |
Is it safe to enable auto update after 33760? |
only CL team knows :) |
I am a little disappointed CL team not checking out updates more carefully
this last 33740 update for me required a reinstall of Clear Linux with a
disable of auto update I guess gnome desktop is not top priority for CL
team. I think for me on my PC a usb bluetooth dongle I use was not handled
properly by 33730 and then 33740 broke everything.
…On Sat, Sep 26, 2020 at 11:07 AM ilmarn ***@***.***> wrote:
im closing it as its resolved in 33760
terminal issue can be resolved by swithing to adwaita theme or manually
updating your current theme
Is it safe to enable auto update after 33760?
only CL team knows :)
personally i prefer to update manually after a day or two after release
and checking issues on github
—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub
<#2133 (comment)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/AJFGJRVX2TFEGZXKP4HRQILSHX7UJANCNFSM4RXKI4NA>
.
|
33760 did not fix my broken installation, followed all instructions given here. Result: another dead server which has to be reinstalled .. impressive ! |
33760 worked perfectly on my PC?? |
update to 33760, problem persists, gnome-shell still crashes for me. Going back to 33710...
|
journalctl attached
journalctl.log
The text was updated successfully, but these errors were encountered: