You are not logged in.
I made an update just now and when I tried to log in (my session manager is LightDM), XFCE just gets me back into LightDM again. I suspected that maybe was the window manager so I changed it to the original and the DE let's me in just fine.
I did a
sudo journalctl -b | curl -F 'file=@-' 0x0.st
and this is the output of it. I can't find anything specific about an xfce4 session that just throws you back into the login menu, and the output only says something about a segfault that doesn't happen when I start xfce4 with its own WM. Any idea on what it could be? It doesn't seem to specify anything on why the segfault neither as far as I know, but I could be wrong.
Last edited by Lex0s (2024-10-03 17:13:33)
Offline
Oct 02 19:11:37 Lex0ss systemd-coredump[927]: Process 819 (xfce4-session) of user 1000 dumped core.
Stack trace of thread 819:
#0 0x0000741b171dcbeb n/a (libc.so.6 + 0x16ebeb)
#1 0x0000741b172b3782 g_list_find_custom (libglib-2.0.so.0 + 0x54782)
#2 0x000062a4cb715f5c n/a (xfce4-session + 0x23f5c)
but that could just be a side-effect of the session stopping immediately.
Can you start awesome by itself / can you log into a normal awesome session?
Did you follow https://wiki.archlinux.org/title/Xfce#U … ow_manager - especially the blue note?
Post your ~/.config/xfce4/xfconf/xfce-perchannel-xml/xfce4-session.xml after configuring awesome.
Offline
Can you start awesome by itself / can you log into a normal awesome session?
Yeah, an awesome session works fine.
Did you follow https://wiki.archlinux.org/title/Xfce#U … ow_manager - especially the blue note?
Post your ~/.config/xfce4/xfconf/xfce-perchannel-xml/xfce4-session.xml after configuring awesome.
I just did the command that sets the "Client1_Command" at its moment and everything seemed to be right. I set both clients now and this is the xfce4-session.xml file content:
<?xml version="1.0" encoding="UTF-8"?>
<channel name="xfce4-session" version="1.0">
<property name="general" type="empty">
<property name="FailsafeSessionName" type="empty"/>
<property name="LockCommand" type="empty"/>
<property name="SessionName" type="string" value="Default"/>
<property name="SaveOnExit" type="bool" value="false"/>
</property>
<property name="sessions" type="empty">
<property name="Failsafe" type="empty">
<property name="IsFailsafe" type="empty"/>
<property name="Count" type="empty"/>
<property name="Client0_Command" type="array">
<value type="string" value="xfsettingsd"/>
</property>
<property name="Client0_Priority" type="empty"/>
<property name="Client0_PerScreen" type="empty"/>
<property name="Client1_Command" type="array">
<value type="string" value="awesome"/>
</property>
<property name="Client1_Priority" type="empty"/>
<property name="Client1_PerScreen" type="empty"/>
<property name="Client2_Command" type="empty"/>
<property name="Client2_Priority" type="empty"/>
<property name="Client2_PerScreen" type="empty"/>
<property name="Client3_Command" type="empty"/>
<property name="Client3_Priority" type="empty"/>
<property name="Client3_PerScreen" type="empty"/>
<property name="Client4_Command" type="empty"/>
<property name="Client4_Priority" type="empty"/>
<property name="Client4_PerScreen" type="empty"/>
</property>
</property>
<property name="chooser" type="empty">
<property name="AlwaysDisplay" type="bool" value="true"/>
</property>
</channel>
Now it let me log in but it has a lot of problems, backgrounds won't load and there's a lot of screen tearing that it didn't happened before.
Offline
You're no longer running any compositor (try picom)
About the "backgrounds", you're probably looking for https://archlinux.org/packages/extra/x86_64/xfdesktop/ ?
Does the process run?
Offline
With picom the tearing disappeared. I guess, as you said, needed to put more attention to the blue notes.
About the "backgrounds", you're probably looking for https://archlinux.org/packages/extra/x86_64/xfdesktop/ ?
I tried a lot of things with xfdesktop and I don't know but it seems like it just can't work fine with another WM that is not xfwm4 when it comes to background images, at least before it was working fine for me. So I just disabled it and used the feature from awesome to make it work. Thanks for the help
Offline