Recreating Unity in Xubuntu

ToZ · 2022-01-06 18:09:33

A couple of your images are missing. Are you referring to the Alt-Tab window or still just the logout dialog? Or both?

ToZ · 2022-01-06 18:55:41

KBar wrote:

Also, I'd like to get rid of the checkbutton. `dialog.xfsm-logout-dialog .text-button { opacity: 0; }` does it in a way, but maybe there is an xfconf property (like ShowSuspend boolean, etc.)?

kiosk mode will do this for you. Create an /etc/xdg/xfce4/kiosk/kioskrc file with the following content:

[xfce4-session]
SaveSession=NONE

...and log out and back in again.

ToZ · 2022-01-06 18:57:43

KBar wrote:

How do I hide the label at the very bottom?

/* hide window title label from tabwin */
#xfwm-tabwin>box>label { font-size: 0; }

KBar · 2022-01-07 04:51:51

ToZ wrote:

A couple of your images are missing. Are you referring to the Alt-Tab window or still just the logout dialog? Or both?

Sorry, I was asking about xfwm-tabwin, but soon after managed to resolve it. I should have stroke through that part of the post.

kiosk mode will do this for you

I wasn't aware of such a mode. That's wonderful. I edited the kioskrc, let me reboot. Thanks a lot!

KBar · 2022-01-07 16:40:35

Enabling CSD system-wide fixes the logout dialog issue.

It's strange that `GTK_CSD=1 xfce4-session-logout` did nothing. Can I somehow disable CSD for the whole system but let the xfsm-logout-dialog use them?

ToZ · 2022-01-07 17:53:21

KBar wrote:

It's strange that `GTK_CSD=1 xfce4-session-logout` did nothing. Can I somehow disable CSD for the whole system but let the xfsm-logout-dialog use them?

I'd guess its because xfce4-session is already running and it's reusing its environment variables.

Try starting xfce4-session with GTK_CSD=1 set. On Arch, it looks like its run from /etc/xdg/xfce4/xinitrc, but reviewing the startxfce4 executable, if you copy that file to ~/.config/xfce4/ and edit it:

exec GTK_CSD=1 xfce4-session

...it should be run instead.

KBar · 2022-01-07 18:37:29

Hmm. startxfce4(1) says to copy /etc/xdg/xfce4/xinitrc to ~/.config/xfce4/xinitrc and modify that file, too. I did just that. After reboot, PAM wouldn't let me log in. Removed that file and edited the system-wide configuration file. PAM still complains:

Jan 07 23:25:47 hp lightdm[1033]: PAM unable to dlopen(pam_kwallet.so): /lib/security/pam_kwallet.so: cannot open shared object file: No such file or directory
Jan 07 23:25:47 hp lightdm[1033]: PAM adding faulty module: pam_kwallet.so
Jan 07 23:25:47 hp lightdm[1033]: PAM unable to dlopen(pam_kwallet5.so): /lib/security/pam_kwallet5.so: cannot open shared object file: No such file or directory
Jan 07 23:25:47 hp lightdm[1033]: PAM adding faulty module: pam_kwallet5.so
Jan 07 23:25:47 hp lightdm[1033]: pam_unix(lightdm-greeter:session): session opened for user lightdm by (uid=0)
Jan 07 23:25:47 hp systemd[1]: Created slice User Slice of UID 114.
Jan 07 23:25:47 hp systemd[1]: Starting User Runtime Directory /run/user/114...
Jan 07 23:25:47 hp systemd-logind[712]: New session c2 of user lightdm.
Jan 07 23:25:47 hp systemd[1]: Finished User Runtime Directory /run/user/114.
Jan 07 23:25:47 hp systemd[1]: Starting User Manager for UID 114...
Jan 07 23:25:47 hp systemd[1053]: pam_unix(systemd-user:session): session opened for user lightdm by (uid=0)
Jan 07 23:25:48 hp systemd[1053]: Reached target Paths.
Jan 07 23:25:48 hp systemd[1053]: Reached target Timers.
Jan 07 23:25:48 hp systemd[1053]: Starting D-Bus User Message Bus Socket.
Jan 07 23:25:48 hp systemd[1053]: Listening on GnuPG network certificate management daemon.
Jan 07 23:25:48 hp systemd[1053]: Listening on GnuPG cryptographic agent and passphrase cache (access for web browsers).
Jan 07 23:25:48 hp systemd[1053]: Listening on GnuPG cryptographic agent and passphrase cache (restricted).
Jan 07 23:25:48 hp systemd[1053]: Listening on GnuPG cryptographic agent (ssh-agent emulation).
Jan 07 23:25:48 hp systemd[1053]: Listening on GnuPG cryptographic agent and passphrase cache.
Jan 07 23:25:48 hp systemd[1053]: Listening on debconf communication socket.
Jan 07 23:25:48 hp systemd[1053]: Listening on Sound System.
Jan 07 23:25:48 hp systemd[1053]: Listening on REST API socket for snapd user session agent.
Jan 07 23:25:48 hp systemd[1053]: Listening on D-Bus User Message Bus Socket.
Jan 07 23:25:48 hp systemd[1053]: Reached target Sockets.
Jan 07 23:25:48 hp systemd[1053]: Reached target Basic System.
Jan 07 23:25:48 hp systemd[1]: Started User Manager for UID 114.
Jan 07 23:25:48 hp systemd[1053]: Starting Sound Service...
Jan 07 23:25:48 hp systemd[1]: Started Session c2 of user lightdm.
Jan 07 23:25:48 hp lightdm[1033]: gkr-pam: gnome-keyring-daemon started properly
Jan 07 23:25:48 hp rtkit-daemon[903]: Successfully made thread 1059 of process 1059 owned by '114' high priority at nice level -11.
Jan 07 23:25:48 hp rtkit-daemon[903]: Supervising 4 threads of 2 processes of 2 users.
Jan 07 23:25:48 hp systemd[1053]: Started D-Bus User Message Bus.
Jan 07 23:25:48 hp dbus-daemon[1067]: [session uid=114 pid=1067] AppArmor D-Bus mediation is enabled
Jan 07 23:25:48 hp set-cpufreq[698]: Setting ondemand scheduler for all CPUs
Jan 07 23:25:48 hp dbus-daemon[1067]: [session uid=114 pid=1067] Activating via systemd: service name='org.a11y.Bus' unit='at-spi-dbus-bus.service' requested by ':1.2' (uid=114 pid=1066 comm="/usr/sbin/lightdm-gtk-greeter " label="unconfined")
Jan 07 23:25:48 hp systemd[1053]: Starting Accessibility services bus...
Jan 07 23:25:48 hp systemd[1]: ondemand.service: Succeeded.
Jan 07 23:25:48 hp dbus-daemon[1067]: [session uid=114 pid=1067] Successfully activated service 'org.a11y.Bus'
Jan 07 23:25:48 hp systemd[1053]: Started Accessibility services bus.
Jan 07 23:25:48 hp dbus-daemon[1067]: [session uid=114 pid=1067] Activating via systemd: service name='org.gtk.vfs.Daemon' unit='gvfs-daemon.service' requested by ':1.4' (uid=114 pid=1066 comm="/usr/sbin/lightdm-gtk-greeter " label="unconfined")
Jan 07 23:25:48 hp systemd[1053]: Starting Virtual filesystem service...
Jan 07 23:25:48 hp dbus-daemon[1067]: [session uid=114 pid=1067] Successfully activated service 'org.gtk.vfs.Daemon'
Jan 07 23:25:48 hp systemd[1053]: Started Virtual filesystem service.
Jan 07 23:25:48 hp rtkit-daemon[903]: Supervising 4 threads of 2 processes of 2 users.
Jan 07 23:25:48 hp rtkit-daemon[903]: Successfully made thread 1112 of process 1059 owned by '114' RT at priority 5.
Jan 07 23:25:48 hp rtkit-daemon[903]: Supervising 5 threads of 2 processes of 2 users.
Jan 07 23:25:48 hp rtkit-daemon[903]: Supervising 5 threads of 2 processes of 2 users.
Jan 07 23:25:48 hp rtkit-daemon[903]: Successfully made thread 1113 of process 1059 owned by '114' RT at priority 5.
Jan 07 23:25:48 hp rtkit-daemon[903]: Supervising 6 threads of 2 processes of 2 users.
Jan 07 23:25:48 hp dbus-daemon[680]: [system] Activating via systemd: service name='org.bluez' unit='dbus-org.bluez.service' requested by ':1.43' (uid=114 pid=1059 comm="/usr/bin/pulseaudio --daemonize=no --log-target=jo" label="unconfined")
Jan 07 23:25:48 hp dbus-daemon[680]: [system] Activation via systemd failed for unit 'dbus-org.bluez.service': Unit dbus-org.bluez.service not found.
Jan 07 23:25:48 hp systemd[1053]: Started Sound Service.
Jan 07 23:25:48 hp systemd[1053]: Reached target Main User Target.
Jan 07 23:25:48 hp systemd[1053]: Startup finished in 570ms.
Jan 07 23:25:48 hp pulseaudio[1059]: GetManagedObjects() failed: org.freedesktop.systemd1.NoSuchUnit: Unit dbus-org.bluez.service not found.
Jan 07 23:25:48 hp systemd[1]: dmesg.service: Succeeded.
Jan 07 23:25:49 hp at-spi-bus-launcher[1098]: dbus-daemon[1098]: Activating service name='org.a11y.atspi.Registry' requested by ':1.0' (uid=114 pid=1066 comm="/usr/sbin/lightdm-gtk-greeter " label="unconfined")
Jan 07 23:25:49 hp lightdm[1129]: PAM unable to dlopen(pam_kwallet.so): /lib/security/pam_kwallet.so: cannot open shared object file: No such file or directory
Jan 07 23:25:49 hp lightdm[1129]: PAM adding faulty module: pam_kwallet.so
Jan 07 23:25:49 hp lightdm[1129]: PAM unable to dlopen(pam_kwallet5.so): /lib/security/pam_kwallet5.so: cannot open shared object file: No such file or directory
Jan 07 23:25:49 hp lightdm[1129]: PAM adding faulty module: pam_kwallet5.so
Jan 07 23:25:49 hp lightdm[1129]: pam_succeed_if(lightdm:auth): requirement "user ingroup nopasswdlogin" was met by user "kbar"
Jan 07 23:25:49 hp at-spi-bus-launcher[1098]: dbus-daemon[1098]: Successfully activated service 'org.a11y.atspi.Registry'
Jan 07 23:25:49 hp at-spi-bus-launcher[1132]: SpiRegistry daemon is running with well-known name - org.a11y.atspi.Registry
Jan 07 23:25:50 hp NetworkManager[681]: <info>  [1641579950.1956] manager: startup complete
Jan 07 23:25:50 hp systemd[1]: Finished Network Manager Wait Online.
Jan 07 23:25:50 hp systemd[1]: Reached target Network is Online.
Jan 07 23:25:50 hp systemd[1]: Starting LSB: disk temperature monitoring daemon...
Jan 07 23:25:50 hp systemd[1]: Starting Tool to automatically collect and submit kernel crash signatures...
Jan 07 23:25:50 hp systemd[1]: Starting LSB: VirtualBox Linux kernel module...
Jan 07 23:25:50 hp systemd[1]: Started crash report submission daemon.
Jan 07 23:25:50 hp systemd[1]: Started LSB: disk temperature monitoring daemon.
Jan 07 23:25:50 hp systemd[1]: kerneloops.service: Found left-over process 1146 (kerneloops) in control group while starting unit. Ignoring.
Jan 07 23:25:50 hp systemd[1]: This usually indicates unclean termination of a previous run, or service implementation deficiencies.
Jan 07 23:25:50 hp whoopsie[1142]: [23:25:50] Using lock path: /var/lock/whoopsie/lock
Jan 07 23:25:50 hp virtualbox[1140]:  * Loading VirtualBox kernel modules...
Jan 07 23:25:50 hp systemd[1]: Started Tool to automatically collect and submit kernel crash signatures.
Jan 07 23:25:50 hp kernel: vboxdrv: loading out-of-tree module taints kernel.
Jan 07 23:25:50 hp kernel: vboxdrv: module verification failed: signature and/or required key missing - tainting kernel
Jan 07 23:25:50 hp kernel: vboxdrv: Found 4 processor cores
Jan 07 23:25:50 hp kernel: vboxdrv: TSC mode is Invariant, tentative frequency 1696068415 Hz
Jan 07 23:25:50 hp kernel: vboxdrv: Successfully loaded version 6.1.26_Ubuntu r145957 (interface 0x00300000)
Jan 07 23:25:50 hp kernel: VBoxNetFlt: Successfully started.
Jan 07 23:25:50 hp virtualbox[1140]:    ...done.
Jan 07 23:25:50 hp systemd[1]: Started LSB: VirtualBox Linux kernel module.
Jan 07 23:25:50 hp systemd[1]: Reached target Multi-User System.
Jan 07 23:25:50 hp systemd[1]: Reached target Graphical Interface.
Jan 07 23:25:50 hp kernel: VBoxNetAdp: Successfully started.
Jan 07 23:25:50 hp systemd[1]: Starting Update UTMP about System Runlevel Changes...
Jan 07 23:25:50 hp systemd[1]: systemd-update-utmp-runlevel.service: Succeeded.
Jan 07 23:25:50 hp systemd[1]: Finished Update UTMP about System Runlevel Changes.
Jan 07 23:25:50 hp systemd[1]: Startup finished in 1.949s (firmware) + 3.577s (loader) + 2.704s (kernel) + 19.222s (userspace) = 27.454s.
Jan 07 23:25:50 hp whoopsie[1142]: [23:25:50] The default IPv4 route is: /org/freedesktop/NetworkManager/ActiveConnection/1
Jan 07 23:25:50 hp whoopsie[1142]: [23:25:50] Not a paid data plan: /org/freedesktop/NetworkManager/ActiveConnection/1
Jan 07 23:25:50 hp whoopsie[1142]: [23:25:50] Found usable connection: /org/freedesktop/NetworkManager/ActiveConnection/1
Jan 07 23:25:51 hp systemd[1]: Stopping Session c2 of user lightdm.
Jan 07 23:25:51 hp systemd[1]: session-c2.scope: Succeeded.
Jan 07 23:25:51 hp systemd[1]: Stopped Session c2 of user lightdm.
Jan 07 23:25:51 hp systemd[1053]: pulseaudio.service: Succeeded.
Jan 07 23:25:51 hp systemd-logind[712]: Removed session c2.
Jan 07 23:25:51 hp lightdm[1129]: pam_unix(lightdm:session): session opened for user kbar by (uid=0)
Jan 07 23:25:51 hp systemd-logind[712]: New session c3 of user kbar.
Jan 07 23:25:51 hp systemd[1]: Started Session c3 of user kbar.
Jan 07 23:25:51 hp lightdm[1129]: gkr-pam: gnome-keyring-daemon started properly
Jan 07 23:25:51 hp lightdm[1129]: pam_unix(lightdm:session): session closed for user kbar
Jan 07 23:25:51 hp systemd-logind[712]: Session c3 logged out. Waiting for processes to exit.
Jan 07 23:25:51 hp systemd[860]: pulseaudio.service: Succeeded.
Jan 07 23:25:52 hp lightdm[1282]: PAM unable to dlopen(pam_kwallet.so): /lib/security/pam_kwallet.so: cannot open shared object file: No such file or directory
Jan 07 23:25:52 hp lightdm[1282]: PAM adding faulty module: pam_kwallet.so
Jan 07 23:25:52 hp lightdm[1282]: PAM unable to dlopen(pam_kwallet5.so): /lib/security/pam_kwallet5.so: cannot open shared object file: No such file or directory
Jan 07 23:25:52 hp lightdm[1282]: PAM adding faulty module: pam_kwallet5.so
Jan 07 23:25:52 hp lightdm[1282]: pam_unix(lightdm-greeter:session): session opened for user lightdm by (uid=0)
Jan 07 23:25:52 hp systemd-logind[712]: New session c4 of user lightdm.
Jan 07 23:25:52 hp systemd[1]: Started Session c4 of user lightdm.
Jan 07 23:25:52 hp lightdm[1282]: gkr-pam: gnome-keyring-daemon started properly
Jan 07 23:25:53 hp lightdm[1327]: PAM unable to dlopen(pam_kwallet.so): /lib/security/pam_kwallet.so: cannot open shared object file: No such file or directory
Jan 07 23:25:53 hp lightdm[1327]: PAM adding faulty module: pam_kwallet.so
Jan 07 23:25:53 hp lightdm[1327]: PAM unable to dlopen(pam_kwallet5.so): /lib/security/pam_kwallet5.so: cannot open shared object file: No such file or directory
Jan 07 23:25:53 hp lightdm[1327]: PAM adding faulty module: pam_kwallet5.so
Jan 07 23:25:53 hp lightdm[1327]: pam_succeed_if(lightdm:auth): requirement "user ingroup nopasswdlogin" was met by user "kbar"
Jan 07 23:25:56 hp systemd-resolved[640]: Using degraded feature set (UDP) for DNS server 192.168.1.1.
Jan 07 23:25:56 hp systemd[1]: NetworkManager-dispatcher.service: Succeeded.
Jan 07 23:25:56 hp systemd[1]: session-c1.scope: Succeeded.
Jan 07 23:25:56 hp systemd-logind[712]: Removed session c1.
Jan 07 23:26:01 hp systemd[1]: session-c3.scope: Succeeded.
Jan 07 23:26:01 hp systemd-logind[712]: Removed session c3.
Jan 07 23:26:02 hp systemd[1]: Stopping Session c4 of user lightdm.
Jan 07 23:26:02 hp systemd[1]: session-c4.scope: Succeeded.
Jan 07 23:26:02 hp systemd[1]: Stopped Session c4 of user lightdm.
Jan 07 23:26:02 hp lightdm[1327]: pam_unix(lightdm:session): session opened for user kbar by (uid=0)
Jan 07 23:26:02 hp systemd-logind[712]: Removed session c4.
Jan 07 23:26:02 hp systemd-logind[712]: New session c5 of user kbar.
Jan 07 23:26:02 hp systemd[1]: Started Session c5 of user kbar.
Jan 07 23:26:02 hp lightdm[1327]: gkr-pam: gnome-keyring-daemon started properly
Jan 07 23:26:03 hp lightdm[1327]: pam_unix(lightdm:session): session closed for user kbar
Jan 07 23:26:03 hp systemd-logind[712]: Session c5 logged out. Waiting for processes to exit.
Jan 07 23:26:04 hp lightdm[1448]: PAM unable to dlopen(pam_kwallet.so): /lib/security/pam_kwallet.so: cannot open shared object file: No such file or directory
Jan 07 23:26:04 hp lightdm[1448]: PAM adding faulty module: pam_kwallet.so
Jan 07 23:26:04 hp lightdm[1448]: PAM unable to dlopen(pam_kwallet5.so): /lib/security/pam_kwallet5.so: cannot open shared object file: No such file or directory
Jan 07 23:26:04 hp lightdm[1448]: PAM adding faulty module: pam_kwallet5.so
Jan 07 23:26:04 hp lightdm[1448]: pam_unix(lightdm-greeter:session): session opened for user lightdm by (uid=0)
Jan 07 23:26:04 hp systemd-logind[712]: New session c6 of user lightdm.
Jan 07 23:26:04 hp systemd[1]: Started Session c6 of user lightdm.
Jan 07 23:26:04 hp lightdm[1448]: gkr-pam: gnome-keyring-daemon started properly
Jan 07 23:26:05 hp lightdm[1493]: PAM unable to dlopen(pam_kwallet.so): /lib/security/pam_kwallet.so: cannot open shared object file: No such file or directory
Jan 07 23:26:05 hp lightdm[1493]: PAM adding faulty module: pam_kwallet.so
Jan 07 23:26:05 hp lightdm[1493]: PAM unable to dlopen(pam_kwallet5.so): /lib/security/pam_kwallet5.so: cannot open shared object file: No such file or directory
Jan 07 23:26:05 hp lightdm[1493]: PAM adding faulty module: pam_kwallet5.so
Jan 07 23:26:05 hp lightdm[1493]: pam_succeed_if(lightdm:auth): requirement "user ingroup nopasswdlogin" was met by user "kbar"
Jan 07 23:26:12 hp login[794]: pam_unix(login:session): session opened for user kbar by LOGIN(uid=0)
Jan 07 23:26:12 hp systemd-logind[712]: New session 3 of user kbar.
Jan 07 23:26:12 hp systemd[1]: Started Session 3 of user kbar.
Jan 07 23:26:12 hp systemd[1]: systemd-fsckd.service: Succeeded.
Jan 07 23:26:13 hp systemd[1]: session-c5.scope: Succeeded.
Jan 07 23:26:13 hp systemd-logind[712]: Removed session c5.
Jan 07 23:26:13 hp systemd-timesyncd[641]: Initial synchronization to time server 91.189.89.199:123 (ntp.ubuntu.com).
Jan 07 23:26:13 hp systemd[1]: systemd-hostnamed.service: Succeeded.
Jan 07 23:26:18 hp systemd[1]: systemd-timedated.service: Succeeded.
Jan 07 23:26:33 hp systemd[1]: Stopping Session c6 of user lightdm.

ToZ · 2022-01-07 21:15:35

It "looks" like its working. It's complaining about a missing pam_kwallet5 library (probably something left over from a kde app/install) but it appears to start sessions for kbar.

KBar · 2022-01-08 02:29:26

Never installed any KDE app (only got Electrum as an AppImage). It tries to open a session but immediately closes it. Apparently, it is a known bug: https://forums.linuxmint.com/viewtopic.php?t=286950

Last edited by KBar (2022-01-08 02:33:09)

KBar · 2022-01-08 02:43:25

ToZ wrote:

Try starting xfce4-session with GTK_CSD=1 set. On Arch, it looks like its run from /etc/xdg/xfce4/xinitrc, but reviewing the startxfce4 executable, if you copy that file to ~/.config/xfce4/ and edit it:
exec GTK_CSD=1 xfce4-session
...it should be run instead.

It turns out environment variables need to come first like so:

GTK_CSD=1 exec xfce4-session

Desktop starts up normally, but it looks like this affects CSD globally. Now all windows have them. I guess, you can't have your cake and eat it too.

ToZ · 2022-01-08 02:48:18

Hmph. Funny that its packaged with lightdm in ubuntu regardless of whether or not you have kwallet installed. Upstream debian doesn't do this.

KBar · 2022-01-08 09:19:46

In an attempt to fix an unrelated problem, I had to disable LD_PRELOAD in /etc/X11/Xsession.d/01gtk3-nocsd:

export GTK3_NOCSD_IGNORE=1

It turns out, the logout dialog problem is gone, too. How convenient! Two birds with one stone. And it also doesn't mess with nocsd globally. So actually three birds with one stone!

ToZ wrote:

Hmph. Funny that its packaged with lightdm in ubuntu regardless of whether or not you have kwallet installed. Upstream debian doesn't do this.

I guess because Xubuntu users might wish to install KDE with LightDM and it requires kwallet module for proper login?

Another question: I don't really need the Log Out button. Can I replace it with Suspend or at least disable it?

Last edited by KBar (2022-01-08 11:39:35)

ToZ · 2022-01-08 12:12:57

KBar wrote:

Another question: I don't really need the Log Out button. Can I replace it with Suspend or at least disable it?

Some of the buttons can be hidden (https://forum.xfce.org/viewtopic.php?pid=56285#p56285) but it doesn't look like logout can.

With css, I can target the logout button with:

.xfsm-logout-buttons box:first-child button:first-child { background-color: red; }

...but I can't see a way to hide it.

KBar · 2022-01-08 12:36:32

Well, that's a bummer.

Thanks for that example ruleset. Was just gonna theme the individual buttons.

KBar · 2022-01-09 08:11:01

And, I'm done theming xfsm-logout-dialog:

And this is Unity's session dialog:

Spot 10 differences tongue

ToZ · 2022-01-09 11:50:08

Nice. What config did you end up using to achieve that?

KBar · 2022-01-09 12:20:56

Now also label is shown under highlighted button: https://imgur.com/a/kx5dYE8

ToZ wrote:

Nice. What config did you end up using to achieve that?

For the logout dialog alone around 45 lines:

.xfsm-logout-dialog {
	background: alpha(@average_bg, 0.9) padding-box;
	border: 20px solid;
	border-image: url("assets/switcher_border.png") 25%/25px stretch;
	border-radius: 25px;
	padding: 0px;
}

.xfsm-logout-label { padding: 16px 30px 12px; font: lighter 16px "Ubuntu Thin"; color: white; text-shadow: none; }

.xfsm-logout-dialog separator { opacity: 0; padding: 0; margin: 0; }

.xfsm-logout-dialog .text-button { background: transparent url("assets/dialog_close.png") no-repeat border-box; border: 1px solid alpha(white, 0); font-size: 0px; }

.xfsm-logout-dialog .text-button:hover { background-image: url("assets/dialog_close_highlight.png"); }

.xfsm-logout-dialog .text-button:active { background-image: url("assets/dialog_close_press.png"); }

.xfsm-logout-buttons .horizontal { padding-left: 35px; padding-right: 35px; padding-bottom: 44px; margin-top: -20px; }

.xfsm-logout-buttons button { background: none; border: 1px solid alpha(white, 0); border-radius: 16px; min-width: 168px; min-height: 168px; }

.xfsm-logout-buttons button label { font-size: 0; margin-bottom: -284px; }

.xfsm-logout-buttons button:hover label { color: white; font: lighter 16px "Ubuntu Light"; text-shadow: none; }

.xfsm-logout-buttons button image { opacity: 0; }

.xfsm-logout-buttons button:nth-child(1) { background: url("assets/logout.png") no-repeat; margin: 0; padding: 0; margin-right: 8px; }

.xfsm-logout-buttons button:nth-child(1):hover { background: url("assets/logout_highlight.png") no-repeat; }

.xfsm-logout-buttons button:nth-child(2) { background: url("assets/restart.png") no-repeat; margin: 0 4px; padding: 0 }

.xfsm-logout-buttons button:nth-child(2):hover { background: url("assets/restart_highlight.png") no-repeat; }

.xfsm-logout-buttons button:nth-child(3) { background: url("assets/shutdown.png") no-repeat; margin: 0; padding: 0; margin-left: 8px; }

.xfsm-logout-buttons button:nth-child(3):hover { background: url("assets/shutdown_highlight.png") no-repeat; }

dialog.background.keycap.xfsm-logout-dialog box.vertical.dialog-vbox box.horizontal.dialog-action-box { margin-right: 545px; margin-top: -538px; }

dialog.background.keycap.xfsm-logout-dialog box.vertical.dialog-vbox box.horizontal.dialog-action-box buttonbox.horizontal.dialog-action-area button.text-button { margin-right: 62px; margin-bottom: 8px; margin-top: -5px; margin-left: -4px }

dialog.background.keycap.xfsm-logout-dialog box.vertical.dialog-vbox box.horizontal.dialog-action-box buttonbox.horizontal.dialog-action-area button.text-button label { font-size: 0px; }

KBar · 2022-01-10 15:14:07

ToZ wrote:

Some of the buttons can be hidden (https://forum.xfce.org/viewtopic.php?pid=56285#p56285) but it doesn't look like logout can.
With css, I can target the logout button with:
.xfsm-logout-buttons box:first-child button:first-child { background-color: red; }
...but I can't see a way to hide it.

Loaded with a bit of knowledge, I think forcing the logout button to not be drawn (I'm thinking of reducing its size or pushing it outside the main window) and replacing it with the suspend button should be doable. I'll try that tomorrow and share the results.

On a side note, is CSS, or rather GTK's implementation of it, efficient? Can additional rules hindrance the performance? I mean, Greybird's gtk.css file has over 2000 lines, so maybe it isn't that big of a resource-consumer.

As always, thank you for your invaluable contributions.

ToZ · 2022-01-10 16:41:39

KBar wrote:

Can additional rules hindrance the performance? I mean, Greybird's gtk.css file has over 2000 lines, so maybe it isn't that big of a resource-consumer.

I haven't seen any issues but I have read online where people are noticing performance impacts from some themes. Maybe related to animations and stuff?

KBar · 2022-01-10 16:45:32

Yeah, you're probably onto something. I think I should be alright, too. If I ever add fancy animations all over, might as well just switch to GNOME. tongue

KBar · 2022-01-10 18:26:13

UPDATE: Idea scrapped. I decided not to include the suspend button since closing the lid already does it. Having the logout button there is logical and might prove useful later.

Added suspend, sent logout to heavens (preliminary view):

The button is still there (just 1px). As long as I don't click around top border (which I won't), it should be alright. Only need to include its own background image and make sure it's pixel-perfect.

Last edited by KBar (2022-01-11 05:46:09)

KBar · 2022-02-07 16:18:02

I forgot to post another update. This is my tabwin:

KBar · 2022-02-11 08:10:39

Since the xfce4-windowck-plugin didn't quite work quite well on my system, I decided to bring the panel with three launchers with custom window buttons back. Having learnt a bit more about Bash and shell scripts in general, I improved the script and made it more robust.

During the process, I wondered: where does the title bar and its contents go when the titleless maximize setting is enabled? This curiosity made me venture into the source code, where I came across this and eventually this, which still doesn't explain to me where the title bar goes.

The ultimate question is, however: are there any plugins or perhaps Python scripts that catch the title bar and place it on the panel? Is this what xfce4-windowck-plugin does at a fundamental level or am I way off in my assumption (and discoveries)?

ToZ · 2022-02-11 12:33:32

KBar wrote:

During the process, I wondered: where does the title bar and its contents go when the titleless maximize setting is enabled? This curiosity made me venture into the source code, where I came across this and eventually this, which still doesn't explain to me where the title bar goes.

Apparently a well-guarded secret. I can't find anything specific about GDK Atoms outside of what you found.

The ultimate question is, however: are there any plugins or perhaps Python scripts that catch the title bar and place it on the panel? Is this what xfce4-windowck-plugin does at a fundamental level or am I way off in my assumption (and discoveries)?

Which elements of a window's titlebar are you trying to move up there? If you already have the control buttons via your launchers, and the appmenu would show the app name, is there anything else you want up there? Maybe the application title, or the menu?

KBar · 2022-02-11 12:45:15

ToZ wrote:

Which elements of a window's titlebar are you trying to move up there? If you already have the control buttons via your launchers, and the appmenu would show the app name, is there anything else you want up there? Maybe the application title, or the menu?

Sorry, it's just my inner thirst for knowing more that cannot be quenched. tongue

Everything needed is already there, as you said: I got my buttons and a pseudo window title. It's not ideal or perfect but I can live with it. Just a question that popped into my head and I felt like I had to dig deep to come close to its answer (which I failed but that's okay).

Last edited by KBar (2022-02-11 12:46:00)

Xfce Forum

Sub domains

#51 2022-01-06 18:09:33

Re: Recreating Unity in Xubuntu

#52 2022-01-06 18:55:41

Re: Recreating Unity in Xubuntu

#53 2022-01-06 18:57:43

Re: Recreating Unity in Xubuntu

#54 2022-01-07 04:51:51

Re: Recreating Unity in Xubuntu

#55 2022-01-07 16:40:35

Re: Recreating Unity in Xubuntu

#56 2022-01-07 17:53:21

Re: Recreating Unity in Xubuntu

#57 2022-01-07 18:37:29

Re: Recreating Unity in Xubuntu

#58 2022-01-07 21:15:35

Re: Recreating Unity in Xubuntu

#59 2022-01-08 02:29:26

Re: Recreating Unity in Xubuntu

#60 2022-01-08 02:43:25

Re: Recreating Unity in Xubuntu

#61 2022-01-08 02:48:18

Re: Recreating Unity in Xubuntu

#62 2022-01-08 09:19:46

Re: Recreating Unity in Xubuntu

#63 2022-01-08 12:12:57

Re: Recreating Unity in Xubuntu

#64 2022-01-08 12:36:32

Re: Recreating Unity in Xubuntu

#65 2022-01-09 08:11:01

Re: Recreating Unity in Xubuntu

#66 2022-01-09 11:50:08

Re: Recreating Unity in Xubuntu

#67 2022-01-09 12:20:56

Re: Recreating Unity in Xubuntu

#68 2022-01-10 15:14:07

Re: Recreating Unity in Xubuntu

#69 2022-01-10 16:41:39

Re: Recreating Unity in Xubuntu

#70 2022-01-10 16:45:32

Re: Recreating Unity in Xubuntu

#71 2022-01-10 18:26:13

Re: Recreating Unity in Xubuntu

#72 2022-02-07 16:18:02

Re: Recreating Unity in Xubuntu

#73 2022-02-11 08:10:39

Re: Recreating Unity in Xubuntu

#74 2022-02-11 12:33:32

Re: Recreating Unity in Xubuntu

#75 2022-02-11 12:45:15

Re: Recreating Unity in Xubuntu

Board footer