When I started building out GNOME I followed the BLFS GNOME chapter and used their package list, which is a little trimmed down still and doesnt include the video player (totem). BLFS helped limit the package count for what I needed to submit and maintain on SBo, and it provides a decent GNOME desktop. I have also been using alienBOB's restricted vlc package for years so I didnt have a need to build another video player.

I was hoping that posting about this "GNOME on SBo" project here in the forums that it would drum up interest and maybe attract some other people to add gnome builds they like to use to SBo...

This version of GNOME comes with a udev rule to disable wayland for certain versions of the nvidia driver, but otherwise it indeed uses wayland by default. On my laptop it runs on Wayland, on my desktop it detects my nvidia and only Xorg is available. YMMV

I haven't seen gnome-terminal do that, but I've only tested gnome on three machines so far. Is there something you can do to reproduce it? I could try troubleshooting if I could get it to do the same. Also might be worth comparing gnome-terminal in X11 versus Wayland. There can be some differences with Wayland operation due to profile scripts not being sourced. If it works in X11 but not Wayland then thats where I would start looking.

I primarily used BLFS as a guide, along with referencing Artix for the patches. I didnt see anything in building gnome-session about restoring previous sessions. I wonder if this is something that ubuntu patches in? I tried to build everything as vanilla as upstream provides it, minus a couple patches to get GNOME to work with elogind. Thanks for posting the instructions. If that works then it gives users the option to set up restoring previous sessions.

Thanks for the report. I'd be curious to know the full build time on a machine like that.

@LuckyCyborg
I'm testing out a patched version of gnome-session that adds sourcing of all the profile scripts for a gnome wayland session. I basically copied what sddm does and applied to gnome-session. With this version of gnome-session, the /etc/profile, /etc/profile.d and $HOME/.{bash_profile,profile} scripts are properly sourced.

The default from before was for gnome on wayland to depend on a systemd daemon to provide it this environment info, which causes issues with gnome-terminal and a number of other things that depend on environment variables. Now that issue is removed.

If you want to test out this patched gnome-session, you can get a copy and build it from my repo here: https://github.com/0xBOBF/gnome-slac.../gnome-session Just build and use upgradepkg to switch to this version.

Theres some other people testing this out at the moment but so far it fixes several issues in GNOME/wayland without systemd. I also plan on pushing the changes to SBo but for now here it is.

OK, I will do.

BTW, how can be build (and upgraded) only the updated packages with a sbopkg queue? It's even possible?

I confess that I did not used too much SBo and sbopkg.

I'm not sure about updating packages with sbopkg. I use a few subsets of sbopkg's functionality but I'm not an expert at it.

If you want steps to build and test the gnome-session package I am talking about, this should work for you:

1. In a temporary working directory clone the testing branch of my repo:
2. Navigate to the gnome-session directory and run the slackbuild as root. The following should do:
Then logout and login again. You can remove the cloned repo after.

Thanks, but I figured out already how to use manually your SlackBuild. My question was about sbopkg.

Well the changes here are just in this repo and not submitted yet, so they cant really be queued up using sbopkg yet (without hacking sbopkg's repos). Once the changed build is submitted to slackbuilds.org then you can just run 'sbopkg' in its dialog mode and check for package upgrades. gnome-session can be upgraded without affecting anything else from the previous build queue. All thats changed with this patch is the wrapper script that comes with gnome-session so that it sources profile scripts.

Thanks!

When I'll arrive home I will do this rebuild. Now I'm in the way to home.

1 members found this post helpful.

It should take care of those gnome-terminal issues. Some other things that it fixes are firefox and gnome-terminal properly following the system light/dark theme that you can select with gnome-tweaks, as well as some other things like flatpaks appearing properly in the application menus.

Maybe this fixes the nutty terminal, too.

I will test with a brand new user account.

Okay, I tested this, building and installing the patched gnome-session.

Honestly, I did not seen any difference and the gnome-terminal continues to have its issue and this both in Wayland and X11.

This happens when it's enabled "use colors from system theme" and it manifests as an illegible console with strange artifacts. Quite strange, I cannot make a screenshot - in screenshot everything is OK.

BTW, I've used since beginning that blocaled - I should do something regarding it?

PS. Also the session's restoring of open applications does not work, as previous. Both in Wayland and X11.

Let me explain what I mean: did you remember that in KDE4 or Plasma5, IF you leave an application (i.e. a Firefox window) open and you logout or shutdown/restart the computer, when you start the KDE desktop back, the application leaved open is reopened automatically?

Same is capable Gnome, with the note that Plasma5 still has issues under Wayland, BUT Gnome4 should work like a charm even under Wayland. This work under Ubuntu or OpenSUSE, if you activate that particular option (which I presented you) via DConf.

https://wiki.gnome.org/Projects/Sess...t/GnomeSession

Blocaled was my first attempt at solving this problem. It's something that the BLFS guys made to get gnome working in wayland and it expects systemd style config files like /etc/locale.conf. The problem is that these are not present in slackware so I also made a script to generate the expected configs. It's never been the proper solution in my opinion so I never submitted it to SBo.

The gnome-session solution I am working on is meant to replace blocaled and use the existing profile files from slackware instead. You should removepkg blocaled and remove the /etc/locale.conf file that the blocaled package created at install. After removing, reboot the system to make sure the blocaled system dbus service is no longer running.

OK, this way I will do.

I'm still looking for a solution to that restore session problem. This gnome-session patch is just to fix profile scripts. I'm not sure if this restore session is something that other distros configure as a custom tweak on their end but if I dig something up I'll let you know.

In fact, it restores the session! With a delay of one minute or more.

After I removed blocaled & Co. while restarting the computer, I have started another box to deLILOficate it (I move everything to GRUB2 after last bootloader adventures) and this was a work around several minutes.

For my surprise, looking back, I found the Gnome4 test box with the session restored. After at least one minute. Should have done it immediately like Gnome4 do in Ubuntu.

BTW, the session restoring should be a stock/standard option, from my knowledge. The link given by me (and which describes how the Gnome4 sessions works) is right on to official Gnome documentation.