xfce4-session issueshttps://gitlab.xfce.org/xfce/xfce4-session/-/issues2023-11-01T10:19:33Zhttps://gitlab.xfce.org/xfce/xfce4-session/-/issues/135Shutdown/reboot/poweroff doesn't warn to save file2023-11-01T10:19:33ZBugzilla MigrationShutdown/reboot/poweroff doesn't warn to save file## Submitted by turcovadio@sapo.pt
Assigned to **Nick Schermer**
**[Link to original bug (#14431)](https://bugzilla.xfce.org/show_bug.cgi?id=14431)**
## Description
Xfce 4.8.0.3, installed in Debian 7 Wheezy, at shutdown/poweroff/...## Submitted by turcovadio@sapo.pt
Assigned to **Nick Schermer**
**[Link to original bug (#14431)](https://bugzilla.xfce.org/show_bug.cgi?id=14431)**
## Description
Xfce 4.8.0.3, installed in Debian 7 Wheezy, at shutdown/poweroff/reboot asks the user if he wants to save unsaved files created using Gedit, Libreoffice Writer, etc.
In Xfce4 (4.10.1) installed in Debian 8 Jessie, and in Xfce (4.12.3) installed in Debian 9 Stretch, when doing shutdown/poweroff/reboot does not ask the user if he wants to save unsaved files. The unsaved files are lost.
Version: Unspecifiedhttps://gitlab.xfce.org/xfce/xfce4-session/-/issues/133Memory usage keeps growing2023-05-06T16:53:39ZMaximilian KnespelMemory usage keeps growingI'm currently logged in for 108 days and over that time I observed a very slow creep of xfce4-session memory usage over each day. At the current time, it takes up 4GB of memory! So akin to 40 MB per day.
It looks like a memory leak to m...I'm currently logged in for 108 days and over that time I observed a very slow creep of xfce4-session memory usage over each day. At the current time, it takes up 4GB of memory! So akin to 40 MB per day.
It looks like a memory leak to me, which forces me to reboot the system sometime in the future. Unfortunately, I don't have any more information on this and I'm not running a debug version, so I doubt I could glean anything useful from it with a memory dump.
I'm completely guessing at this point but it could be something trivial like some internal memory-held log growing over time. I had a similar problem with the `.xsession-errors` files in the past because pidgin keeps spamming `Json-CRITICAL` "warnings". Currently, `.xsession-errors` is 45MB large, which is still ok. Xfce4-session is "only" mentioned about 4000 times with (the Pidgin log line appears 380k times):
(xfce4-session:14089): xfce4-session-WARNING **: 01:10:58.993: ICE connection 0x56327fb692f0 rejected
and 5 times
(xfce4-session:14089): GLib-WARNING **: 19:10:20.560: GChildWatchSource: Exit status of a child process was requested but ECHILD was received by waitpid(). See the documentation of g_child_watch_source_new() for possible causes.https://gitlab.xfce.org/xfce/xfce4-session/-/issues/131A .desktop file without Type key will be launched at startup but won't appear...2022-04-07T11:09:51ZXu ZhenA .desktop file without Type key will be launched at startup but won't appear in Session and StartupIn the `xfae_item_new` function at https://gitlab.xfce.org/xfce/xfce4-session/-/blob/master/settings/xfae-model.c#L660
```
/* verify that we have an application here */
value = xfce_rc_read_entry (rc, "Type", NULL);
if ...In the `xfae_item_new` function at https://gitlab.xfce.org/xfce/xfce4-session/-/blob/master/settings/xfae-model.c#L660
```
/* verify that we have an application here */
value = xfce_rc_read_entry (rc, "Type", NULL);
if (G_LIKELY (value != NULL
&& g_ascii_strcasecmp (value, "Application") == 0))
{
...
}
else
{
return NULL;
}
```
A .desktop file must set Type=Application to be appeared in the Application Autostart tab of the Session and Startup.
But in the `xfsm_launch_desktop_files_on_run_hook` function at https://gitlab.xfce.org/xfce/xfce4-session/-/blob/master/xfce4-session/xfsm-global.c#L373
```
/* check the "Type" key */
type = xfce_rc_read_entry (rc, "Type", NULL);
if (G_UNLIKELY (!skip && type != NULL && g_ascii_strcasecmp (type, "Application") != 0))
{
skip = TRUE;
xfsm_verbose ("Type == Application, skipping\n");
}
```
If a .desktop file doesn't have a Type key, it can still pass the check and get launched.https://gitlab.xfce.org/xfce/xfce4-session/-/issues/128Starting session might fail without package "procps"2023-04-24T11:58:30ZJakkojahau@rocketmail.comStarting session might fail without package "procps"Specific example:
On distribution postmarketOS I installed package `calls` (a phone application). Two reboots later, the Xfce4 session fails to start and returns to the display manager.
What happens:
postmarketOS is based on distribut...Specific example:
On distribution postmarketOS I installed package `calls` (a phone application). Two reboots later, the Xfce4 session fails to start and returns to the display manager.
What happens:
postmarketOS is based on distribution Alpine Linux [1], which is build around musl libc and busybox. On installation of `calls`, it is added to autostart. After the first reboot, `calls` starts a daemon. By default, at the Xfce4 shutdown/reboot dialog the option "Save session for future logins" is set. Saving the restart command for running programs is done by `ps -p %u -o args=` [2]. Busybox doesn't have the option "-p" in its `ps` command [3]. Therefore the line RestartCommand (and line Program) remains empty in file ~/.config/sessions/xfce4-session-HOSTNAME:0. When rebooting a second time, this empty line leads to xfce4-session failing to start.
Snippet from file ~/.config/sessions/xfce4-session-hostname:0:
```
Client6_ClientId=org.gnome.Calls
Client6_Hostname=hostname
Client6_RestartCommand=
Client6_DesktopFile=/usr/share/applications/org.gnome.Calls.desktop
Client6_Program=
```
Workaround:
I will set up a merge request at Alpine Linux to set package "procps" as a dependency of xfce4-session. This package contains the full-featured `ps` command [4].
Points I want to raise:
- Maybe there are other distros running on busybox or other reasons why xfce4-session should run reliably without package "procps".
- Even if package "procps" isn't installed and a RestartCommand line remains empty, this shouldn't lead to xfce4-session failing to start. I would expect just the program not starting. This would confuse the user as well but would be less severe.
OS/software:
- Distribution: postmarketOS (based on Alpine Linux)
- xfce4-session version: 4.16.0
References:
- [1] https://www.alpinelinux.org
- [2] https://gitlab.xfce.org/xfce/xfce4-session/-/blob/xfce4-session-4.16.0/xfce4-session/xfsm-client.c#L450
- [3] https://www.busybox.net/downloads/BusyBox.html#ps
- [4] https://gitlab.com/procps-ng/procps/-/blob/v3.3.17/ps/help.c#L114https://gitlab.xfce.org/xfce/xfce4-session/-/issues/126Session and Startup Application Autostart tab does not allow editing personal...2022-04-07T11:10:18ZChristopher HeadSession and Startup Application Autostart tab does not allow editing personal overrides of system autostart filesIf `/etc/xdg/autostart/foo.desktop` exists, the Session and Startup Autostart tab shows that item in the list but does not allow editing or removing it. Ideally it would (with any edit creating a copy of the file in `~/.config/autostart`...If `/etc/xdg/autostart/foo.desktop` exists, the Session and Startup Autostart tab shows that item in the list but does not allow editing or removing it. Ideally it would (with any edit creating a copy of the file in `~/.config/autostart` and putting the edits there), but that is more of a feature request than a bug.
If `/etc/xdg/autostart/foo.desktop` and `~/.config/autostart/foo.desktop` both already exist, then `xfce4-session` correctly *uses* `~/.config/autostart/foo.desktop` and ignores `/etc/xdg/autostart/foo.desktop` at startup; however, the control panel still refuses to edit `~/.config/autostart/foo.desktop`, which it should allow (though if the override mechanism is not properly implemented, it should probably still disable the remove button); it seems like a bug to me for this to not work since the actual editing mechanism is the same as for personal-only (as opposed to personal-override) autostart items.https://gitlab.xfce.org/xfce/xfce4-session/-/issues/125Session and Startup do not show suggestions for applications2022-04-07T11:10:45ZTioSession and Startup do not show suggestions for applicationsIf I didn't post it to the proper package can you please move it to where it belongs? Thanks.
Basically in Session and Startup - Application Autostart, if I click the + sign to add a new application it does not show any suggestions whil...If I didn't post it to the proper package can you please move it to where it belongs? Thanks.
Basically in Session and Startup - Application Autostart, if I click the + sign to add a new application it does not show any suggestions while typing in the Name box:
![image](/uploads/5ab2ee04717b3a5da34187c8c753e926/image.png)
However when creating a new launcher and such, same dialogue window, will showcase suggestions based on the installed apps on my system. And it is very very useful.https://gitlab.xfce.org/xfce/xfce4-session/-/issues/124add elogind support2023-04-24T12:00:13ZRizal Martinadd elogind supportxfce4-session supports ConsoleKit2 and systemd. However some distros replaced ConsoleKit2 in favor of elogind (non-systemd version of logind)
See [elogind on Gentoo Wiki](https://wiki.gentoo.org/wiki/Elogind)xfce4-session supports ConsoleKit2 and systemd. However some distros replaced ConsoleKit2 in favor of elogind (non-systemd version of logind)
See [elogind on Gentoo Wiki](https://wiki.gentoo.org/wiki/Elogind)https://gitlab.xfce.org/xfce/xfce4-session/-/issues/123xfce4-session attempts to manage multiple X screens even though core apps can...2023-04-24T12:04:18Ztroyrolloxfce4-session attempts to manage multiple X screens even though core apps can no longer handle itSince GTK 3.10, GTK (at least according to the change logs) has not supported multiple X screens (eg. :0.0 + :0.1) from the same process. xfce4-panel no longer supports it, and you cannot start a separate instance because they both will ...Since GTK 3.10, GTK (at least according to the change logs) has not supported multiple X screens (eg. :0.0 + :0.1) from the same process. xfce4-panel no longer supports it, and you cannot start a separate instance because they both will want to grab the same names on DBUS.
Multiple screens are still sometimes unavoidable - for example if you need both XRANDR and the proprietary NVIDIA drivers and have two GPUs that are different.
the GTK people recommend treating the separate screens as different servers, effectively requiring a separate XFCE session for each of the screens (with a separate DBUS). As a result, the code in xfce4-session that iterates over multiple screens leads to the sessions interfering with each other.
It seems that xfce4-session should now only look at the "default" screen, and the loops should be removed.
It would be good if xfce4-session could instead be configured to launch additional sessions (with a new instance of itself and a new DBUS) on the second and subsequent screens. Even better if it could be configured to launch sessions of other desktop environments on the second and subsequent screens.https://gitlab.xfce.org/xfce/xfce4-session/-/issues/121Fix program name display for a current session representation2021-08-24T08:10:47ZMarkus ElfringFix program name display for a current session representationI am trying also the program “xfce4-session-settings” out from the package “xfce4-session-4.16.0-3.fc34”.
I observed a software behaviour which I find improvable.
1. A listing is provided on [the tab “Current Session”](https://docs.xfc...I am trying also the program “xfce4-session-settings” out from the package “xfce4-session-4.16.0-3.fc34”.
I observed a software behaviour which I find improvable.
1. A listing is provided on [the tab “Current Session”](https://docs.xfce.org/xfce/xfce4-session/4.16/preferences#session "Active session settings").
2. I can start the program “dolphin” (version 21.08.0-2) fine for example.
3. An additional entry is displayed with the text “(Unbekannter Fehler)” (unknown error) here in the mentioned widget.
How can a more helpful information appear?https://gitlab.xfce.org/xfce/xfce4-session/-/issues/118SSH_AUTH_SOCK is not set when using gpg-agent ssh support2023-10-11T16:56:21ZThomas BrunoSSH_AUTH_SOCK is not set when using gpg-agent ssh support```
xfce4-session version 4.16
Ubuntu 20.04: http://ppa.launchpad.net/xubuntu-dev/staging/ubuntu
I have also manually compiled for the same result.
```
I've been debugging a bit trying to get gpg-agent with ssh working. When starting u...```
xfce4-session version 4.16
Ubuntu 20.04: http://ppa.launchpad.net/xubuntu-dev/staging/ubuntu
I have also manually compiled for the same result.
```
I've been debugging a bit trying to get gpg-agent with ssh working. When starting up $SSH_AUTH_SOCK is unset when using gpg-agent's ssh support. SSH expects $SSH_AUTH_SOCK to be the gpg-agent's ssh socket but it is unset at line 292 of xfsm-startup.c. On my system .xsessionrc already is setting SSH_AUTH_SOCK to be the gpg-agent's socket but 292 ends unsetting this value.
I see a check for gpgagent_ssh_enabled in the ssh-agent handling section at 279 but cannot find any place where SSH_AUTH_SOCK is then reset to be the gpg-agent's ssh socket.
I have ssh-agent set to Enabled, and gpg-agent set to enabled and I have forced ssh-agent to be gpg-agent. /compat/LaunchGNOME is false.
```
xfconf-query -c xfce4-session -p /startup/ssh-agent/enabled -n -t bool -s true
xfconf-query -c xfce4-session -p /startup/gpg-agent/enabled -n -t bool -s true
xfconf-query -c xfce4-session -p /startup/ssh-agent/type -n -t string -s gpg-agent
.xsessionrc:
unset SSH_AGENT_PID
if [ "${gnupg_SSH_AUTH_SOCK_by:-0}" -ne $$ ]; then
export SSH_AUTH_SOCK="$(gpgconf --list-dirs agent-ssh-socket)"
fi
```https://gitlab.xfce.org/xfce/xfce4-session/-/issues/117Reboot into UEFI setup2023-05-13T23:51:55ZArtem S. TashkinovReboot into UEFI setupPlease add an option to reboot into UEFI setup.
That's `systemctl reboot --firmware-setup`Please add an option to reboot into UEFI setup.
That's `systemctl reboot --firmware-setup`https://gitlab.xfce.org/xfce/xfce4-session/-/issues/116GNOME Keyring Daemon should be locked upon suspension and hibernation2021-07-04T17:56:35ZAlexander ShukaevGNOME Keyring Daemon should be locked upon suspension and hibernationAs per [Security FAQ](https://wiki.gnome.org/Projects/GnomeKeyring/SecurityFAQ), GNOME Keyring Daemon (GKD) should be locked upon suspension and hibernation. I don't think this is happening currently. From my side, I would add that wra...As per [Security FAQ](https://wiki.gnome.org/Projects/GnomeKeyring/SecurityFAQ), GNOME Keyring Daemon (GKD) should be locked upon suspension and hibernation. I don't think this is happening currently. From my side, I would add that wrapping a GKD process with `systemd-inhibit --what=shutdown:sleep:idle:handle-power-key:handle-suspend-key:handle-hibernate-key ... gnome-keyring-daemon ...` if `systemd-inhibit` is available on a system is a good way to both prevent and document this.https://gitlab.xfce.org/xfce/xfce4-session/-/issues/107xfce4-session-logout fails to get focus sometimes, allowing input to the wron...2021-03-23T06:37:04ZFurretUberxfce4-session-logout fails to get focus sometimes, allowing input to the wrong windowIt is possible that when the xfce4-session-logout window appear, it will fail to grab the focus. The focus grab failure allows the user to add keyboard input to windows behind it. For example, I can write this bug report while the window...It is possible that when the xfce4-session-logout window appear, it will fail to grab the focus. The focus grab failure allows the user to add keyboard input to windows behind it. For example, I can write this bug report while the window of xfce4-session-logout is appearing in the front of the Firefox window.
Steps to reproduce:
1) Run `xfce4-session-logout`, either using the menu or using the terminal;
2) Press Alt-Tab;
3) Wait the shutdown options window appear;
4) Press Tab again to choose the window behind you want to focus;
5) Focus the wrong window.
This bug can be problematic in the scenario the user don't want to shutdown, but to suspend or hibernate and end sending input to the wrong window.
The attached video has the recording of the bug happening. This bug is easier to reproduce in the first run of xfce4-session-logout, related to #52
![xfce4-session-logout-bug](/uploads/cb01c2631332670f93b5101fbeac1c6d/xfce4-session-logout-bug.mp4)
The system has Xubuntu 20.04 using the xubuntu-dev staging PPA.
```
$ xfce4-session-logout --version
xfce4-session 4.16.0 (Xfce 4.16)
Copyright (c) 2004-2020
A equipe de desenvolvimento do Xfce. Todos os direitos reservados.
Escrito por Benedikt Meurer <benny@xfce.org>
e Brian Tarricone <kelnos@xfce.org>.
Por favor relate os erros para <https://bugzilla.xfce.org/>.
```https://gitlab.xfce.org/xfce/xfce4-session/-/issues/105Sessions always saved, whatever is checked in xfce4-session2024-03-28T13:45:17ZeipaosxsSessions always saved, whatever is checked in xfce4-sessionHow to reproduce:
1. open "Session and startup"
2. uncheck "Automatically save session on logout"
3. shutdown or restart your machine
Expected result:
1. a blank session is started
Actual result:
1. your last session is restored
2. /.s...How to reproduce:
1. open "Session and startup"
2. uncheck "Automatically save session on logout"
3. shutdown or restart your machine
Expected result:
1. a blank session is started
Actual result:
1. your last session is restored
2. /.session contains your past session
Note that the setting xfce4-session "SaveOnExit" is correctly set to "Boolean" and empty.
Check on Manjaro, Xfce 4.16.https://gitlab.xfce.org/xfce/xfce4-session/-/issues/103After creating a new session /general/SessionName is not set with newly creat...2021-03-09T02:39:40ZAvinash SonawaneAfter creating a new session /general/SessionName is not set with newly created session's nameHello!
Steps to reproduce:
1. Turn on Session and startup > General >"Display chooser on login"
2. Logout
3. Login
4. Create new session `foo` in session chooser
5. /general/SessionName in xfce4-session channel has name of the previosly...Hello!
Steps to reproduce:
1. Turn on Session and startup > General >"Display chooser on login"
2. Logout
3. Login
4. Create new session `foo` in session chooser
5. /general/SessionName in xfce4-session channel has name of the previosly loaded session (one before logout)
6. Side effect of this is that on Session and Startup > Current Session > "Current active session" shows previously loaded session name and not currently active session name `foo`
Thanks!https://gitlab.xfce.org/xfce/xfce4-session/-/issues/102[Feature Request] Allow loading session from saved sessions2021-08-24T09:30:25ZAvinash Sonawane[Feature Request] Allow loading session from saved sessionsHello!
Use case:
1. User logins with session `foo`
2. Then after doing some work wants to change the context i.e. want to load the session `dev`
It would be really cool if user could simply load the session from Session and Startup > S...Hello!
Use case:
1. User logins with session `foo`
2. Then after doing some work wants to change the context i.e. want to load the session `dev`
It would be really cool if user could simply load the session from Session and Startup > Saved Sessions list instead of logging out, selecting the `dev` session in session chooser and then logging in again.
Thanks!https://gitlab.xfce.org/xfce/xfce4-session/-/issues/101[Feature Request] Allow saving session with custom name2021-08-24T09:38:37ZAvinash Sonawane[Feature Request] Allow saving session with custom nameHello!
It would be really handy if user could create a custom session while operating the xfce desktop. This could be achieved by allowing user to save session with custom name.
A use case would be:
1. User logins with session foo
2. W...Hello!
It would be really handy if user could create a custom session while operating the xfce desktop. This could be achieved by allowing user to save session with custom name.
A use case would be:
1. User logins with session foo
2. While working and switching contexts user opens dev-related apps (e.g. IDE, editor, debugger etc.)
3. And now user wants to save this current desktop checkpoint as new session named `dev`
Currently, only way to do that is by logging out and then logging in with new session named `dev`. And then again open those exact apps she wants `dev` session to have.
May be we can give user a choice to enter custom session name when user clicks Session and Startup > Current Session > "Save Session" button instead of only allowing to save the checkpoint to current session?
Thanks!https://gitlab.xfce.org/xfce/xfce4-session/-/issues/100Session chooser allows to create new session with the same name as that of an...2021-03-09T02:38:17ZAvinash SonawaneSession chooser allows to create new session with the same name as that of an existing session overwriting the exisiting sessionHello!
While creating a new session from Session chooser dialog, session chooser doesn't check if the session name already exists. This overwrites the existing session when the new session having the same name is saved (Either manually ...Hello!
While creating a new session from Session chooser dialog, session chooser doesn't check if the session name already exists. This overwrites the existing session when the new session having the same name is saved (Either manually clicking "Save session" or automatically on logout)
Steps to reproduce:
1. Create couple of sessions foo, bar, baz etc.
2. Create new session having same name as that of an existing session `foo`
If user has handful of sessions in session list, she might use existing session name while creating a new session. Session chooser should show error message "Session already exists" instead of overwriting the existing session.
This is much like `adduser`:
```
$ sudo adduser root
adduser: The user `root' already exists.
$
```
I believe the fix is needed right after https://gitlab.xfce.org/xfce/xfce4-session/-/blob/master/xfce4-session/xfsm-manager.c#L725
Thanks!https://gitlab.xfce.org/xfce/xfce4-session/-/issues/99When session list is empty, session chooser is not displayed even if /chooser...2021-03-09T02:38:00ZAvinash SonawaneWhen session list is empty, session chooser is not displayed even if /chooser/AlwaysDisplay is setHello!
If there are no sessions saved then session chooser is not displayed even if /chooser/AlwaysDisplay is set.
Steps to reproduce:
1. Turn on Session and startup > General >"Display chooser on login" (this sets /chooser/AlwaysDispl...Hello!
If there are no sessions saved then session chooser is not displayed even if /chooser/AlwaysDisplay is set.
Steps to reproduce:
1. Turn on Session and startup > General >"Display chooser on login" (this sets /chooser/AlwaysDisplay)
2. Delete all saved sessions
3. Logout without saving the session
4. Now, login
I expected to see session chooser on login since I have set /chooser/AlwaysDisplay. The chooser could have presented empty list where user could create new custom session (by clicking "+" button in session chooser dialog).
Current behavior forces the session name "Default". Instead user could have created custom session if the session chooser was shown as user had set /chooser/AlwaysDisplay.
I believe https://gitlab.xfce.org/xfce/xfce4-session/-/blob/master/xfce4-session/xfsm-manager.c#L439 is the root of the issue.
Thanks!https://gitlab.xfce.org/xfce/xfce4-session/-/issues/96[Feature] Autostart delay for system startup apps / Support for X-GNOME-Autos...2022-03-07T10:20:12ZMartin Dünkelmann[Feature] Autostart delay for system startup apps / Support for X-GNOME-Autostart-DelayIt would be nice, if the startup app has a gui element to set the startup delay in seconds, minutes, etc.
A support for X-GNOME-Autostart-Delay would be nice.It would be nice, if the startup app has a gui element to set the startup delay in seconds, minutes, etc.
A support for X-GNOME-Autostart-Delay would be nice.