Beta Release | Endless OS 6.0.0~beta1

#1

The first beta release of Endless OS 6 is out! Please follow these instructions if you want to join the beta testing program. Bear in mind that the chance of encountering bugs in a beta release is higher than in a regular release – please ensure your data is backed up before updating.

Endless OS 6 will bring a lot of changes and improvements, which are detailed in draft form in the Draft Release Notes. Most of the changes listed there are already present in the 6.0.0~beta1 release.

As a beta tester, you can help us by providing feedback on stability and hardware support, and reporting software regressions (things that used to work in previous releases that stopped working on this new release).

1 Like
#2

Note that you won’t be able to automatically update to 6.0.0~beta1 until the forthcoming 5.1.3~beta1 release is published. We’ll post here when that is the case.

#3

Now the automatic update should be possible.

If you’re running Endless OS 5, please help to test this change by ensuring you are on the beta channel then checking for & installing the OS update to 5.1.3~beta1 in the App Center. After rebooting you should be notified of a major update to Endless OS 6 in the App Center.

Thanks @wjt for clarifying.

1 Like
#4

Hi, i do the upgrade as you talked on post, but now I can’t run many applications, like browsers or libre office, and can’t run eos diagnostic because the terminal is not running too, what could I do?

#5

Good morning, after a lot, I got the terminal to work so I could run the eos diasnostic; After updating to the Endless 6 beta, several applications are not working (not running), and I would like some help to solve this problem.

eos-diagnostic-240413_092827_UTC-0300.txt (1,8 MB)

OOM killer is overly aggressive (Endless OS 5.1.2 - Kernel 6.5)
#6

@James_Martinez thank you so much for testing and contributing the diagnostic! The team at Endless is investigating the issue. One initial guess is that your system is running out of memory while applications are being updating, so any application that launches is being stopped right away (by the OOM killer). If this is the case, your system should be back to normal after the update is done in the background. But it shouldn’t happen in any case.

#7

@James_Martinez could you help with a little debugging? The bottom of the file /etc/gdm3/daemon.conf reads:


[debug]
# Uncomment the line below to turn on debugging
# More verbose logs
# Additionally lets the X server dump core if it crashes
#Enable=true

Can you change that so Enable=true is uncommented like this:

[debug]
# Uncomment the line below to turn on debugging
# More verbose logs
# Additionally lets the X server dump core if it crashes
Enable=true

You can run sudoedit /etc/gdm3/daemon.conf to do that. After that, please reboot, run eos-diagnostics and upload the diagnostics file again. Thanks!

#8

Dan, Hello, I don’t know if I have done things as you have indicated, but here is the new diagnosis; If I can help, I will be attentive.

eos-diagnostic-240415_195117_UTC-0300.txt (1023,4 KB)

#9

Just to give you some background as to what may be happening: it seems that the system believes it is running out of memory, and hence it is preventing some further apps from starting (or terminating ones that were already running).

Your system has 4GB RAM and you are simultaneously running some apps that can be quite large, like Chrome, Floorp, Firefox, Zotero and Libreoffice, so it is not unthinkable that you could be exceeding available resources.

In any case we are doing some analysis to understand if the system is truly out of resources or not, as we do have some other reports of unexpected results in this area. It would be really useful if you have any comments on whether this behaviour seems new to you in EOS6, i.e. does the same set of applications work simultaneously under the previous version EOS5.1?

Thanks

#10

It really is a behavior that I had not had in previous versions of Endelss, in addition, I have run several applications at the same time (libreoffice, librewolf, ImageJ, among others), without any failure in the resources, in this case, in endless 6 not even I can start applications, such as browsers, in any case I am available to continue sending information.

#11

Thanks for the info. Could you please run this command, and see if it makes any noticable difference to the situation:

echo 'n' | sudo tee /sys/kernel/mm/lru_gen/enabled

(This adjustment will only apply to the current boot. On reboot, the original behaviour will be restored.)

#12

Alright, I have run echo ‘n’ | sudo tee /sys/kernel/mm/lru_gen/enabled, and I have tried different applications but the same problem still exists, none of them start or it takes a long time to start. I performed the test without rebooting the system.

#13

Please retest for this app-killing issue with the beta2 release (should be available as an automatic update)

#14

Ok, I have already upgraded to Beta 2, I also ran the same command echo ‘n’ | sudo tee /sys/kernel/mm/lru_gen/enabled, but nothing happened, the applications continue to have problems starting or do not run. I add the diagnosis after the update.
eos-diagnostic-240427_151152_UTC-0300.txt (1,2 MB)

#15

I think there are 2 problems that have been occurring for you.

  1. Apps were getting killed when there was too much memory pressure. I don’t see that in the latest diagnostics file.
  2. Wayland isn’t working properly all the time. In the latest diagnostics file, a Wayland session is attempted and there are problems, so it falls back to using a regular X11 session. I’m not sure why that’s happening. When you run LibreWolf are you not seeing any window at all? Might be useful to try running flatpak run --env=MOZ_ENABLE_WAYLAND=0 io.gitlab.librewolf-community.
#16

Well, when I try to open a browser like LibreWolf, nothing happens, the application does not start (it does not run and no window opens), only after several attempts to open it, it runs in safe mode and finally a window opens; This happens with all the browsers I use. Something similar happens with other applications like Libreoffice that, only after several attempts, run in safe mode. Now, I have executed the command flatpak run --env=MOZ_ENABLE_WAYLAND=0 io.gitlab.librewolf-community, and librewolf has started without any problem (a normal window has opened quickly); Is it possible that the same could happen with the rest of the applications? The following image shows the response of the command executed in the terminal

Captura desde 2024-04-29 20-52-12
Captura desde 2024-04-29 20-52-121280×720 1.03 MB

#17

Yeah, I think that’s the issue you’re facing now. Your session is setup as if Wayland is available but it really isn’t. When programs start, they think they should use Wayland and nothing happens.

Can you run the command env | sort from a terminal and paste the text here? Please review the text to make sure there’s nothing sensitive in there like a password.

#18

OK, there is the information:

james@janad:~$ env | sort
COLORTERM=truecolor
DBUS_SESSION_BUS_ADDRESS=unix:path=/run/user/1001/bus
DESKTOP_SESSION=endless-wayland
DISPLAY=:0
ENDLESS_KEY_USE_SYSTEM_INSTANCE=yes
GDM_LANG=es_CO.UTF-8
GDMSESSION=endless-wayland
GNOME_DESKTOP_SESSION_ID=this-is-deprecated
GNOME_SETUP_DISPLAY=:1
GNOME_SHELL_SESSION_MODE=endless
GNOME_TERMINAL_SCREEN=/org/gnome/Terminal/screen/c746c765_de69_4fa7_9303_00a037d6eaed
GNOME_TERMINAL_SERVICE=:1.128
GTK_MODULES=gail:atk-bridge
HOME=/sysroot/home/james
KOLIBRI_USE_SYSTEM_INSTANCE=yes
LANG=es_CO.UTF-8
LOGNAME=james
MEMORY_PRESSURE_WATCH=/sys/fs/cgroup/user.slice/user-1001.slice/user@1001.service/session.slice/org.gnome.Shell@wayland.service/memory.pressure
MEMORY_PRESSURE_WRITE=c29tZSAyMDAwMDAgMjAwMDAwMAA=
PATH=/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin:/usr/games:/usr/local/games:/sysroot/home/james/.local/share/flatpak/exports/bin:/var/lib/flatpak/exports/bin
PWD=/sysroot/home/james
QT_ACCESSIBILITY=1
QT_IM_MODULE=ibus
SESSION_MANAGER=local/janad:@/tmp/.ICE-unix/1580,unix/janad:/tmp/.ICE-unix/1580
SHELL=/bin/bash
SHLVL=1
SSH_AGENT_LAUNCHER=openssh
SSH_AUTH_SOCK=/run/user/1001/keyring/ssh
SYSTEMD_EXEC_PID=1623
TERM=xterm-256color
USER=james
USERNAME=james
_=/usr/bin/env
VTE_VERSION=7006
WAYLAND_DISPLAY=wayland-0
XAUTHORITY=/run/user/1001/.mutter-Xwaylandauth.ZNNIN2
XDG_CURRENT_DESKTOP=Endless:GNOME
XDG_DATA_DIRS=/usr/share/gnome:/var/lib/kolibri/data/content/xdg/share:/sysroot/home/james/.local/share/flatpak/exports/share:/var/lib/flatpak/exports/share:/usr/local/share/:/usr/share/
XDG_MENU_PREFIX=gnome-
XDG_RUNTIME_DIR=/run/user/1001
XDG_SESSION_CLASS=user
XDG_SESSION_DESKTOP=endless-wayland
XDG_SESSION_TYPE=wayland
XMODIFIERS=@im=ibus