GNOME maintenance

Ok, looks like I've got the same behavior here. GDM freezes after entering the password. Version: gnome-keyring-48.0.
Error on the console is:
Code:
gdm-password: gkr-pam: unable to locate daemon control file.
I already checked /usr/local/etc/pam.d/gdm-password - and both pam_gnome_keyring.so entries are present and active.
How is gnome-keyring launched?

With x11/gnome-shell or x11/gnome-shell-extensions you need to install x11/xdg-desktop-portal-gnome. It is already a dependency in meta port x11/gnome (or gnome-lite).

gnome-keyring checks SSH_AUTH_SOCK variable. In /usr/local/share/example/gnome-shell/xprofile, this variable is defined.

Personally SSH_AUTH_SOCK is subdir of XDG_RUNTIME_DIR (with gnome/gdm, you don't need to defined this variable, they follow the XDG PAM module, but with lightdm it uses value of ConsoleKit2).

If your login manager is lightdm, you can defined a new value (e.g. in .xprofile) and don't forget to enable the gnome-keyring PAM module too.

Code:
_version=$(sysctl kern.osreldate | awk -F " " '{printf("%s", $2);}')

# Set $XDG_RUNTIME_DIR
if [ ${_version} -gt 1401000 ]; then
    _user_id=$(id -un)
    if [ -d "/var/run/xdg/${_user_id}" ]; then
        XDG_RUNTIME_DIR="/var/run/xdg/${_user_id}"
    fi
else
    _user_id=$(id -u)
    if [ -d "/var/run/user/${_user_id}" ]; then
        XDG_RUNTIME_DIR="/var/run/user/${_user_id}"
    fi
fi
export XDG_RUNTIME_DIR

# Unlock gnome-keyring-daemon
if test -n "$DESKTOP_SESSION" ; then
    SSH_AUTH_SOCK="${XDG_RUNTIME_DIR}/keyring"

    export SSH_AUTH_SOCK
fi

gnome-keyring is working fine, I have sockets in XDG_RUNTIME_DIR/keyring.

Code:
ps x
[...]
1497  -  S    0:00,03 /usr/local/bin/gnome-keyring-daemon --start --components=secrets
1498  -  I    0:00,01 /usr/local/bin/gnome-keyring-daemon --start --components=pkcs11
1499  -  I    0:00,03 /usr/local/bin/gnome-keyring-daemon --start --components=ssh
[...]
 
Last edited:
To be honest I'm a little confused now. Gnome works fine, and the keyring-daemon seems to work in the desktop environment. It's just that x11/gdm freezes after login. All ports listed above are installed :) (I'm not sure if this thread is the correct to discuss the login issue, but I found the bug-link mentioned above)
 
I see, me running 42 but switched to xfce4 2 days ago.. unfortunately
Anyways, xfce is faster but I am missing gnome
I had been holding back on patches until I had finished a project. I had experienced problems updating GNOME a few months ago and rolled back to a working snapshot. I later found when I was ready to update again that GNOME3 in 14.3p5 doesn't work with GDM. So I tried KDE instead. Weirdly, GNOME did start from SDDM but I had already decided that I would not be using GNOME again. KDE worked until my laptop suspended for inactivity, then I realised that a reboot was necessary everytime KDE suspended. After about five reboots, I deleted KDE and installed XFCE4. It's fast, a bit ugly, but it mostly works. Suspend doesn't work properly but XFCE4 shows a dialog box instead of freezing the session which I can live with.

It would be nice if there was a simple package to install the Zorin theme and icons. I might try that, but at the moment GhostBSD Gershwin looks interesting. I spent 14 years using GNOME3 and I do miss it, but not enough to have to use SystemD.
 
stead. Weirdly, GNOME did start from SDDM but I had already decided that I would not be using GNOME again. KDE worked until my laptop suspended for inactivity, then I realised that a reboot was necessary everytime KDE suspended. After about five reboots, I deleted KDE and installed XFCE4. It's fast, a bit ugly, but it mostly works. Suspend doesn't work properly but XFCE4 shows a dialog box instead of freezing the session which I can live with.
I actually have the whole 'suspend' feature turned off. I do allow the screen to be turned off under Xorg. Then KDE works fine - under Xorg. Under Wayland, there's still power management issues that are dogging me, but I think the issue is with Display Management, rather than anything else.
 
I actually have the whole 'suspend' feature turned off. I do allow the screen to be turned off under Xorg. Then KDE works fine - under Xorg. Under Wayland, there's still power management issues that are dogging me, but I think the issue is with Display Management, rather than anything else.
Same. I've yet to try 6.5 to check for improvements, will do probably later today.
 
Same. I've yet to try 6.5 to check for improvements, will do probably later today.
It's in the official Ports Collection now, but the thread mentions some patches that probably are NOT in the Ports Collection or even in the Area 51 repo... those patches help with session management, but not Display Management / greeter issues.
 
Even non systemd Linux are having problems with GNOME 49. In particular, the main culprit is the removal of the non-systemd fallback code in gnome-session
 
Even non systemd Linux are having problems with GNOME 49. In particular, the main culprit is the removal of the non-systemd fallback code in gnome-session
Yup. Artix Linux team just straight up removed Gnome from their repos. Its a garbage DE anyway, so no harm done.
 
Yup. Artix Linux team just straight up removed Gnome from their repos.
At least that frees up the name (i.e to avoid naming collisions) with reinstating Gnome 2. It had its own issues but it was the last proper DE that FOSS ever had. It would be quite a powerful statement against Red Hat if people reused the original. Basically shunning Gtk3, systemd, Wayland entirely.
 
Yup. Artix Linux team just straight up removed Gnome from their repos. Its a garbage DE anyway, so no harm done.
Dear All,

I've been a dedicated MATE user on FreeBSD for many years, but recently decided to start testing Gnome 3 again. I'm running the latest version built from ports (47.10).
I have also deskutils/cairo-dock on Gnome, and this feels and works just fine.

Have to say, I'm impressed, finding the user interface polished, and also like the way Gnome windows and desktop management works. It also feels fast and responsive. So far, all things I need seem to work just as expected, however, one main issue is with session restoration.

What I would like is for Gnome to restore my last session when I log out and log back in, re-opening all the applications and windows I had open when logging out. This doesn't seem to work correctly. Some applications seem to be restored, but the desktop is mostly empty every time.

Am I missing something (a setting somewhere that enables session restoration)?

Any advice would be appreciated!
 
Dear All,

I've been a dedicated MATE user on FreeBSD for many years, but recently decided to start testing Gnome 3 again. I'm running the latest version built from ports (47.10).
I have also deskutils/cairo-dock on Gnome, and this feels and works just fine.

Have to say, I'm impressed, finding the user interface polished, and also like the way Gnome windows and desktop management works. It also feels fast and responsive. So far, all things I need seem to work just as expected, however, one main issue is with session restoration.

What I would like is for Gnome to restore my last session when I log out and log back in, re-opening all the applications and windows I had open when logging out. This doesn't seem to work correctly. Some applications seem to be restored, but the desktop is mostly empty every time.

Am I missing something (a setting somewhere that enables session restoration)?

Any advice would be appreciated!
Have you tried saving the session manually, just to see what happens? I tried that in KDE Wayland, after seeing that same issue there. It worked for me in KDE, so I think it's not out of question that a similar approach may work under GNOME...
 
Have you tried saving the session manually, just to see what happens? I tried that in KDE Wayland, after seeing that same issue there. It worked for me in KDE, so I think it's not out of question that a similar approach may work under GNOME...
How can I save the session manually in Gnome?
 
The shell used since GNOME3 just looks like Windows 8. I don't know why anyone who hates it still uses it. There are so many better (in my opinion) shells available.
Gnome 3 isn't really a shell. It is a massive collection of libraries, programs and general clutter.

But I think the DE wars fizzled out about a decade ago. Perhaps people realised that all DEs have stagnated in terms of innovation and what someone may like one year, doesn't necessarily even exist the next.
 
In my humble opinion, Gnome advanced through its beginning to 2.x, and go into broken and incorrect way on 3.0. Why prohibited multiple windows, especially terminal emulators, of the same apps? It was too much of pain, and I've stuck with 2.x, then, Mate (the fork from 2.x) as ports moved on it.
 
You can start by Googling that very question, and then seeing if you can make use of the answers you get.
Actually I did Google before I wrote my last question. Did not find much. (May be my fault). I have done gsettings set org.gnome.SessionManager auto-save-session true.

Running gsettings get org.gnome.SessionManager auto-save-session gives me true. Seems that Gnome saves something, but not the full session.
Thought that maybe someone has experience with that.
 
Yup. Artix Linux team just straight up removed Gnome from their repos. Its a garbage DE anyway, so no harm done.
I tried installing GNOME either when I first started 14.1, or after Xfce with 14.2; it wasn't presented as-ideally as I was used to from openSUSE/Fedora mainstream Linux (I forget the specifics :p) so I kept using Xfce.

Xfce Greybird default has side-window grabs awkward because of some theme-based tiny bar thing (others recommend either patching it or using another theme; Chicago95's is fine). I wasn't into theming years ago and preferred GNOME basically working out-the-box fine!

I haven't tried GNOME on FreeBSD in a while, but with Wayland sessions I'd like to see at least version 48 (lower vers to 42 were odd with realtime cursor handling and 1000Hz mice; anything lower than 42 with Wayland was a worse-joke with that handling like 90s-style software cursors :p ). GNOME deprecated their X11 support 49+ if I heard right, so I'd be fine with lower vers on Xorg.

Am I missing something (a setting somewhere that enables session restoration)?
I haven't seen it be an option enabled with openSUSE, Fedora, or Ubuntu and didn't know GNOME could do that (I'm wondering if GNOME themselves support session restore or if it's experimental?)

I figure reboots imply needing a clean-slate on reboot, and don't like the idea of stuff re-opening (I disable restore on Xfce)
 
Actually I did Google before I wrote my last question. Did not find much. (May be my fault). I have done gsettings set org.gnome.SessionManager auto-save-session true.

Running gsettings get org.gnome.SessionManager auto-save-session gives me true. Seems that Gnome saves something, but not the full session.
Thought that maybe someone has experience with that.
Ah... yeah. In KDE, there is an option to turn on manual session save... but you'd have to dig around in systemsettings app to find it. Based on that, I thought that GNOME might have something similar.

When I re-run the same search, the Google AI section gives me a suggestion to run gnome-session-save. Dunno if that command is available in FreeBSD when GNOME is installed.

Looking a bit further, like in the first 10 Google hits, I'm seeing rather recent information that difficulty saving a GNOME session is a very persistent problem that GNOME devs are probably actually aware of: https://discourse.gnome.org/t/unable-to-save-gnome-session-with-dconf/24989. So this doesn't look like a FreeBSD-specific problem with GNOME, Linux camp is having the same GNOME session saving issues as you do.

There is a GNOME shell extension (also within top 10 Google hits that I got): https://extensions.gnome.org/extension/4709/another-window-session-manager/ . This looks like something worth trying.

HTH
 
Actually I did Google before I wrote my last question. Did not find much. (May be my fault). I have done gsettings set org.gnome.SessionManager auto-save-session true.

Running gsettings get org.gnome.SessionManager auto-save-session gives me true. Seems that Gnome saves something, but not the full session.
Thought that maybe someone has experience with that.

That stub is a red herring. They want to couple application state with window state and if I recall correctly, the APIs aren't quite flushed out:
https://gitlab.gnome.org/GNOME/gnome-session/-/issues/147

The GNOME extension, "Another Window Session Manager" supports GNOME 47. I don't know if it builds under FreeBSD:
https://github.com/nlpsuge/gnome-shell-extension-another-window-session-manager
 
Do you mean that with 6.5.x windows get restored in their original positions, in the respective monitors in a multi monitor setup? That would be news indeed.
 
Do you mean that with 6.5.x windows get restored in their original positions, in the respective monitors in a multi monitor setup? That would be news indeed.
I only have one monitor, so I can't test a multi-monitor setup.

But prior to the timestamp of post #702, KDE 6.5.x did indeed have issues with session management.

The Ctrl-C bug crashed the Plasma Wayland session. And the session could not be properly restored afterwards. How do I know that? The Firefox window would disappear without a trace, no crash core dumps or anything. After I enabled the manual session saving, session management issues disappeared for me. Konsole would be in the correct place, and so would Firefox.
 
Well, you're mixing things.

First of all, the Ctrl+C bug has nothing to do with KDE it's a pure sddm bug that is now partially address with the latest release in the ports (which now crashes for me when trying to move from the Wayland GUI to a VT with for example Ctrl+Alt+F1).

Second, saving the session like you describe always worked with Xorg, even way before 6.5.0 was released. The apps were correctly restored but when using Wayland all of them appeared on the default monitor whilst under Xorg all worked as expected and every app was restored in the monitor it was running previously.

I just checked right now with 6.5.2 and there's some difference with respect to the previous versions, now the sesson gets saved even under Wayland but on session restore you get absolutely the same behavior. BTW, I have a dual monitor setup.
 
Back
Top