Solved XFCE4 doesn't start properly

freezr

freezr

The solution is here: https://forums.freebsd.org/threads/xfce4-doesnt-start-properly.93179/post-659406
Click to expand...

Hi guys,

latest quarterly updates brought a lot of issues with Xfce4, the main issue is after the Lightdm login I got only the desktop image and nothing else.
I need to restart several time Lightdm before to get a functional desktop.

Code: 
usr/local/bin/iceauth:  creating new authority file /var/run/user/1001/ICEauthority
(xfsettingsd:26287): xfconf-WARNING **: 12:06:49.744: Failed to set property "displays::/ActiveProfile": Operation was cancelled
** (wrapper-2.0:35933): WARNING **: 12:06:50.087: could not get output property
** (xfce4-power-manager:40966): WARNING **: 12:06:50.330: could not get output property
(xfsettingsd:26287): libxfce4ui-WARNING **: 12:07:01.940: ICE I/O Error
(xfce4-power-manager:40966): libxfce4ui-WARNING **: 12:07:01.940: ICE I/O Error
(xfsettingsd:26287): libxfce4ui-WARNING **: 12:07:01.940: Disconnected from session manager.
(xfce4-power-manager:40966): libxfce4ui-WARNING **: 12:07:01.940: Disconnected from session manager.
(xfce4-terminal:36708): libxfce4ui-WARNING **: 12:07:01.940: ICE I/O Error
(xfce4-terminal:36708): libxfce4ui-WARNING **: 12:07:01.940: Disconnected from session manager.
(xfce4-panel:27292): libxfce4ui-WARNING **: 12:07:01.940: ICE I/O Error
(xfce4-panel:27292): libxfce4ui-WARNING **: 12:07:01.940: Disconnected from session manager.
(xfdesktop:27868): libxfce4ui-WARNING **: 12:07:01.940: ICE I/O Error
(xfdesktop:27868): libxfce4ui-WARNING **: 12:07:01.940: Disconnected from session manager.
xfsettingsd: Another instance took over. Leaving...
(Thunar:27767): thunar-WARNING **: 12:07:01.946: Name 'org.xfce.FileManager' lost on the message dbus.
(Thunar:27767): thunar-WARNING **: 12:07:01.946: Name 'org.freedesktop.FileManager1' lost on the message dbus.
(xfce4-notes:37495): GVFS-RemoteVolumeMonitor-WARNING **: 12:07:01.950: Owner of volume monitor org.gtk.vfs.UDisks2VolumeMonitor disconnected from the bus; removing drives/volumes/mounts
(xfce4-notes:37495): GVFS-RemoteVolumeMonitor-WARNING **: 12:07:01.954: Owner of volume monitor org.gtk.vfs.MTPVolumeMonitor disconnected from the bus; removing drives/volumes/mounts
(xfce4-notes:37495): GVFS-RemoteVolumeMonitor-WARNING **: 12:07:01.955: Owner of volume monitor org.gtk.vfs.GPhoto2VolumeMonitor disconnected from the bus; removing drives/volumes/mounts
** (xfce4-power-manager:40966): WARNING **: 12:07:01.973: Error: The connection is closed
** (xfce4-power-manager:40966): WARNING **: 12:07:01.973: Error: The connection is closed
(xfsettingsd:44947): xfconf-WARNING **: 12:08:38.221: Failed to set property "displays::/ActiveProfile": Operation was cancelled
** (wrapper-2.0:53588): WARNING **: 12:08:38.567: could not get output property
** (xfce4-power-manager:58360): WARNING **: 12:08:38.818: could not get output property
JavaScript error: resource://gre/modules/XPCOMUtils.sys.mjs, line 140: TypeError:

I have also many XFCE4 dumps on my home:
Code: 
lagrange.core
thunar.core
thunderbird.core
wrapper-2.0.core
xfce4-display-setti.core
xfce4-terminal.core

This is a serious bug, how should I report it?

Thanks! ?
 

Attachments

  • XFCE4 A.jpg
    XFCE4 A.jpg
    739.9 KB · Views: 801
  • XFCE4 B.jpg
    XFCE4 B.jpg
    1.2 MB · Views: 665
Last edited:
Nothing that will really help you, but I just upgraded a XFCE4 VM on the quaterly repo and got no trouble. I don't use LightDM.

That said, I struggled to make XFCE4 works at the base. It was simpler before...
 
Stefan2 said:
Which FreeBSD version do you use?

I upgraded two of my pc's with FreeBSD 14.0 RELEASE-p6 and XFCE with lightdm without any problems.
Click to expand...

I have your exact version, can you share your RC.CONF, perhaps your settings are better!
Do you have Nvdia as GPU?

Thanks!
 
Last edited:
Any ideas
1. Run outside of ligthdm:
# service lightdm stop
$ startx > xfce_log 2>&1
2. Delete or rename your ~/.config
3. Check the status of your disks: df -h
4. Missing deps?
 
Last edited:
I agree with what YYY__ has suggested. Running startx or probably startxfc4 from a commandline will give you more info. There is probably a "$HOME/.config/xfce4" directory that maybe move just that out of the way. There may also be a $HOME/.config/autostart directory to move out also.
I would not delete $HOME/.config thats where you have all the config for "all the things"
 
I made a test moving on the latest repo but it didn't resolve anything, actually none a XFCE4 main component was updated at all...

Definitely this is the cause:

Code: 
(xfsettingsd:89607): xfconf-WARNING **: 23:54:07.704: Failed to set property "displays::/ActiveProfile": Operation was cancelled

I have also a dump on my home... ?
 
Hi guys I am trying to solve this with the XFCE folks, meanwhile I noticed a parallelism...

When XFCE doesn't load on the TTY I have these warnings:
Code: 
Jun 16 00:26:07 dbsd pulseaudio[15217]: [] module-devd-detect.c: Failed to connect to devd.
Jun 16 00:26:07 dbsd pulseaudio[15217]: [] module.c: Failed to load module "module-devd-detect" (argument: ""): initialization failed.
Jun 16 00:26:26 dbsd pulseaudio[49853]: [] core-util.c: Failed to create secure directory (/var/run/user/1001/pulse): No such file or directory

When it loads only these two:
Code: 
Jun 16 00:26:07 dbsd pulseaudio[15217]: [] module-devd-detect.c: Failed to connect to devd.
Jun 16 00:26:07 dbsd pulseaudio[15217]: [] module.c: Failed to load module "module-devd-detect" (argument: ""): initialization failed.

Could there be a relationship between the two parties? ?‍♂️
 
Uninstalling Pulseaudio didn't solve this issue, actually for unknown reasons made my system more unstable... ?‍♂️
 
Reading the Handbook I found a way to display some information from the .core file:

Code: 
lldb -c xfce4-display-setti.core -- xfce4-display-settings
(lldb) target create "xfce4-display-settings" --core "xfce4-display-setti.core"
Core file '/home/freezr/xfce4-display-setti.core' (x86_64) was loaded.
(lldb) thread backtrace all
* thread #1, name = 'xfce4-display-setti', stop reason = signal SIGBUS
  * frame #0: 0x00000008259cb5af
    frame #1: 0x000033d56251e7d0
    frame #2: 0x000000000024fa30 xfce4-display-settings`___lldb_unnamed_symbol847 + 320
    frame #3: 0x000000000024a52f xfce4-display-settings`___lldb_unnamed_symbol791 + 479
  thread #2, name = 'pool-spawner', stop reason = signal SIGBUS
    frame #0: 0x000000082a828d2c
    frame #1: 0x000000082a838d72
  thread #3, name = 'gmain', stop reason = signal SIGBUS
    frame #0: 0x000000082c09fc2a
    frame #1: 0x000000082a837691
  thread #4, name = 'gdbus', stop reason = signal SIGBUS
    frame #0: 0x000000082c0dec80
    frame #1: 0x000000084fa47dd0
  thread #5, name = 'pool-xfce4-disp', stop reason = signal SIGBUS
    frame #0: 0x000000082a828d2c
    frame #1: 0x000000082a838d72
(lldb)

Unfortunately it doesn't say anything to me... ?
 
Guys, perhaps an orthogonal and rather trivial question, but is there any real added value in running Xfce or Gnome via lightdm/gdm/whatever display manager and not via proper startx/startxfce4/xinit? When one uses just and only a single fixed DE.
 
jb82 said:
Guys, perhaps an orthogonal and rather trivial question, but is there any real added value in running Xfce or Gnome via lightdm/gdm/whatever display manager and not via proper startx/startxfce4/xinit? When one uses just and only a single fixed DE.
Click to expand...

Comfortable and elegant.

But also more practical if you only use the system as a pure desktop system anyway.
 
jb82 said:
Guys, perhaps an orthogonal and rather trivial question, but is there any real added value in running Xfce or Gnome via lightdm/gdm/whatever display manager and not via proper startx/startxfce4/xinit? When one uses just and only a single fixed DE.
Click to expand...
I started off using XFCE but found it had much that I did not need/use and switched to LXDE many years ago. I'm pretty much a light user but it serves for what I want to do, which mainly consists of Chromium and Xterm.
 
Apparently the issue might be caused by this bug:

Code: 
libxfce4ui-WARNING **: 12:07:01.940: ICE I/O Error

Which is supposed to be already closed so not sure why ended up into Xfce for FreeBSD... ?‍♂️
 
I found what is triggering the issue: is the compositor; when the compositor is deactivated I don't have this annoying issue.

Is there anything that I can do to refine better this trouble shooting within the FreeBSD side?
The dude that is helping me is not familiar with FreeBSD...

Thanks! ?

In case you're a dev/maintainer and you want learn more: https://forum.xfce.org/viewtopic.php?pid=76029
 
Alexander88207 said:
But also more practical if you only use the system as a pure desktop system anyway.
Click to expand...
Disagree. My system is only used as a desktop, I boot to command line and run startx and have done that for a long time.

Why?
If you've ever had issues with graphics drivers booting directly to gd/xdm/whatever-dm makes it difficult to almost impossible to figure it out. What typically happens is the DM tries to start fails for whatever reason related to can't start X, respawns, fails, respawns and the user sits there trying to remember magic key combos to switch to a different VT and kill things or reboot to single user.
I find it's also easier to test out different window managers/DEs; have the following commented out in my .xinitrc:

#exec /usr/local/bin/xterm

Then I simply comment out my current windowmanager line, uncomment the xterm and run startx. You are at a window with no decorations, you just run "whatever your start command is for the DE/windowmanager".
 
  • Like
Reactions: mro
This is a bit cumbersome.

For example, if lightdm doesn't start, i open a second tty and start it there manually to get information.

But it's very rare for me that it stops working in general, so i don't really have a routine in it or even think about how.
 
So far the workaround is to activate the compositor after the desktop is loaded and deactivate on logout/shutdown however this doesn't solve or explain the main issue, might it be an Nvidia issue eventually? ?
 
Sorry freezr, for unrelated to your problem side comment.

mer said:
I find it's also easier to test out different window managers/DEs; have the following commented out in my .xinitrc:

#exec /usr/local/bin/xterm

Then I simply comment out my current windowmanager line, uncomment the xterm and run startx.
Click to expand...
I have a similar method, but I use shell aliases, without the need of editing files.

For extensive testing purposes of different WMs I've created an easy way to start them without a display manager. I'm a console (xterminal) person anyway, except internet browsing.

Some of those <wm>.xinitrc files contain instructions which programs to start (besides the WM), which background to set, environment variables, etc., others only the WM. Those without other instructions are configure by the specific WMs configuration files.
Code: 
alias    xfluxbox="env XINITRC=$HOME/.xinitrc.d/fluxbox.xinitrc startx"
alias    xherbst="env XINITRC=$HOME/.xinitrc.d/herbstluftwm.xinitrc startx"
alias    xi3="env XINITRC=$HOME/.xinitrc.d/i3.xinitrc startx"
alias    xicewm="env XINITRC=$HOME/.xinitrc.d/icewm.xinitrc startx"
alias    xjwm="env XINITRC=$HOME/.xinitrc.d/jwm.xinitrc startx"
alias    xopenbox="env XINITRC=$HOME/.xinitrc.d/openbox.xinitrc startx"
alias    xsawfish="env XINITRC=$HOME/.xinitrc.d/sawfish.xinitrc startx"

I don't have to type the whole alias, shell autocompletion does the work.
 
freezr said:
So far the workaround is to activate the compositor after the desktop is loaded and deactivate on logout/shutdown however this doesn't solve or explain the main issue, might it be an Nvidia issue eventually? ?
Click to expand...
That is interesting. Is the compositor in the autostart list? If the list can be reordered, perhaps moving it to the end may make a difference. I'm not sure if the autostart list is parsed/started from top to bottom, but if so it may help.
Going by hazy memory, I think ICE is related to components talking to each other. They register somehow and then can go talk to each other. If compositor is trying to talk through ICE to "A" but "A" hasn't registered yet, maybe compositor fails. That would match the workaround I think.
 
You must log in or register to reply here.
Back
Top