xfce commandline start problems

eric · 2020-04-27 18:37:09

After startx from the commandline, messages (o.a. GLib-GIO-CRITICAL) appear in the error output (see output below), which I'd like to resolve. I cannot see anything suspicious in /var/log/Xorg.0.log.

(Also, when xfce is started, as root user *only*, the mouse pointer freezes in the screencenter; I can see no difference in xfce startup output between root and non-root user. When starting X & twm (root or non-root user): no mouse problems. If you think/know this is related to the GLib-GIO-CRITICAL etc. feel free to respond here; if not I'll open a seperate post later.)

Just coming as a new *NIX user from Win10 to Freebsd & xfce-4.14, I installed everything from FreeBSD packages and according to the FreeBSD handbook 5.7.3 Xfce on a Samsung Q210 laptop (using nvidia-driver-340-340.108).

xauth:  file /home/eric/.serverauth.1398 does not exist


X.Org X Server 1.20.8
X Protocol Version 11, Revision 0
Build Operating System: FreeBSD 12.1-RELEASE-p3 amd64 
Current Operating System: FreeBSD q210 12.1-RELEASE-p3 FreeBSD 12.1-RELEASE-p3 GENERIC amd64
Build Date: 04 April 2020  12:43:14PM
 
Current version of pixman: 0.38.4
	Before reporting problems, check http://wiki.x.org
	to make sure that you have the latest version.
Markers: (--) probed, (**) from config file, (==) default setting,
	(++) from command line, (!!) notice, (II) informational,
	(WW) warning, (EE) error, (NI) not implemented, (??) unknown.
(==) Log file: "/var/log/Xorg.0.log", Time: Mon Apr 27 15:12:52 2020
(==) Using config directory: "/usr/local/etc/X11/xorg.conf.d"
(==) Using system config directory "/usr/local/share/X11/xorg.conf.d"
gpg-agent[1440]: WARNING: "--write-env-file" is an obsolete option - it has no effect
gpg-agent: a gpg-agent is already running - not starting a new one

(xfce4-session:1415): xfce4-session-WARNING **: 15:12:55.540: gpg-agent returned no PID in the variables

(xfsettingsd:1443): GVFS-RemoteVolumeMonitor-WARNING **: 15:12:56.653: remote volume monitor with dbus name org.gtk.vfs.HalVolumeMonitor is not supported

(xfce4-panel:1447): GVFS-RemoteVolumeMonitor-WARNING **: 15:12:57.462: remote volume monitor with dbus name org.gtk.vfs.HalVolumeMonitor is not supported

(wrapper-2.0:1454): GLib-GIO-CRITICAL **: 15:12:57.838: g_file_new_for_path: assertion 'path != NULL' failed

(wrapper-2.0:1454): GLib-GIO-CRITICAL **: 15:12:57.839: g_file_monitor_file: assertion 'G_IS_FILE (file)' failed

(wrapper-2.0:1454): GLib-GObject-WARNING **: 15:12:57.839: invalid (NULL) pointer instance

(wrapper-2.0:1454): GLib-GObject-CRITICAL **: 15:12:57.839: g_signal_connect_data: assertion 'G_TYPE_CHECK_INSTANCE (instance)' failed

(wrapper-2.0:1454): Gtk-WARNING **: 15:12:57.839: Attempting to add a widget with type GtkToggleButton to a container of type XfcePanelPlugin, but the widget is already inside a container of type XfcePanelPlugin, please remove the widget from its existing container first.

(wrapper-2.0:1454): Gtk-WARNING **: 15:12:57.969: Negative content width -3 (allocation 1, extents 2x2) while allocating gadget (node button, owner GtkToggleButton)

(wrapper-2.0:1456): Gtk-WARNING **: 15:12:57.973: gtk_widget_size_allocate(): attempt to allocate widget with width -1 and height 24

(wrapper-2.0:1455): Gtk-WARNING **: 15:12:57.978: Negative content width -1 (allocation 1, extents 1x1) while allocating gadget (node button, owner XfceArrowButton)

(xfdesktop:1453): GVFS-RemoteVolumeMonitor-WARNING **: 15:12:58.029: remote volume monitor with dbus name org.gtk.vfs.HalVolumeMonitor is not supported

(xfdesktop:1453): GVFS-RemoteVolumeMonitor-WARNING **: 15:12:58.033: remote volume monitor with dbus name org.gtk.vfs.GPhoto2VolumeMonitor is not supported

(Thunar:1451): Gtk-CRITICAL **: 15:14:50.856: gtk_main_quit: assertion 'main_loops != NULL' failed
GLib (gthread-posix.c): Unexpected error from C library during 'pthread_mutex_lock': Invalid argument.  Aborting.
xinit: connection to X server lost

waiting for X server to shut down .(II) Server terminated successfully (0). Closing log file.

--Update 30 April
Regarding the mouse-freeze when starting xfce as root, I've tried (_constantly_) moving the mouse while starting xfce via startx, I noticed:
m1) during non-graphical "stay" at ttyv I have a rather big mouse pointer which is completely functional.
m2) after the command startx is given the screen goes black and the big mouse disappears.
m3) the NVIDIA splashscreen appears and is followed by a black screen
m4) sometime into this black screen a new--much smaller--mouse pointer appears and is movable!
m5) the first elements of the xfce DE appear and that mouse pointer freezes (now obviously) out off screencenter
m6) without the mouse it is difficult to use the DE but opening an xfce terminal via CTL+ALT+T works.
It all seems to be functional. As is closing the xfce DE via ALT+F4.

Regarding the generated errors (o.a. GLib-GIO-CRITICAL) mentioned before.
After reading about the xfce-UP-arrow problem I tried xev(1). Inside an xfce-terminal it seemed to work ok: I can't see anything strange in the output and no error output is generated. However, in the ttyv from which xfce was started more errors were generated which seem to relate to gtk (see at "MARKER"):

N.B.: these error messages are absent when using xev(1) inside an X-terminal in the original twm(1).

xauth:  file /home/eric/.serverauth.2210 does not exist


X.Org X Server 1.20.8
X Protocol Version 11, Revision 0
Build Operating System: FreeBSD 12.1-RELEASE-p3 amd64 
Current Operating System: FreeBSD q210 12.1-RELEASE-p3 FreeBSD 12.1-RELEASE-p3 GENERIC amd64
Build Date: 04 April 2020  12:43:14PM
 
Current version of pixman: 0.38.4
	Before reporting problems, check http://wiki.x.org
	to make sure that you have the latest version.
Markers: (--) probed, (**) from config file, (==) default setting,
	(++) from command line, (!!) notice, (II) informational,
	(WW) warning, (EE) error, (NI) not implemented, (??) unknown.
(==) Log file: "/var/log/Xorg.0.log", Time: Thu Apr 30 01:03:33 2020
(==) Using config directory: "/usr/local/etc/X11/xorg.conf.d"
(==) Using system config directory "/usr/local/share/X11/xorg.conf.d"
gpg-agent[2252]: WARNING: "--write-env-file" is an obsolete option - it has no effect
gpg-agent: a gpg-agent is already running - not starting a new one

(xfce4-session:2227): xfce4-session-WARNING **: 01:03:36.145: gpg-agent returned no PID in the variables

(xfsettingsd:2255): GVFS-RemoteVolumeMonitor-WARNING **: 01:03:37.375: remote volume monitor with dbus name org.gtk.vfs.HalVolumeMonitor is not supported

(xfce4-panel:2261): GVFS-RemoteVolumeMonitor-WARNING **: 01:03:38.134: remote volume monitor with dbus name org.gtk.vfs.HalVolumeMonitor is not supported

(wrapper-2.0:2268): GLib-GIO-CRITICAL **: 01:03:38.373: g_file_new_for_path: assertion 'path != NULL' failed

(wrapper-2.0:2268): GLib-GIO-CRITICAL **: 01:03:38.373: g_file_monitor_file: assertion 'G_IS_FILE (file)' failed

(wrapper-2.0:2268): GLib-GObject-WARNING **: 01:03:38.373: invalid (NULL) pointer instance

(wrapper-2.0:2268): GLib-GObject-CRITICAL **: 01:03:38.373: g_signal_connect_data: assertion 'G_TYPE_CHECK_INSTANCE (instance)' failed

(wrapper-2.0:2268): Gtk-WARNING **: 01:03:38.373: Attempting to add a widget with type GtkToggleButton to a container of type XfcePanelPlugin, but the widget is already inside a container of type XfcePanelPlugin, please remove the widget from its existing container first.

(wrapper-2.0:2268): Gtk-WARNING **: 01:03:38.576: Negative content width -3 (allocation 1, extents 2x2) while allocating gadget (node button, owner GtkToggleButton)

(wrapper-2.0:2270): Gtk-WARNING **: 01:03:38.691: gtk_widget_size_allocate(): attempt to allocate widget with width -1 and height 24

(wrapper-2.0:2269): Gtk-WARNING **: 01:03:38.727: Negative content width -1 (allocation 1, extents 1x1) while allocating gadget (node button, owner XfceArrowButton)

(xfdesktop:2267): GVFS-RemoteVolumeMonitor-WARNING **: 01:03:38.824: remote volume monitor with dbus name org.gtk.vfs.HalVolumeMonitor is not supported

(xfdesktop:2267): GVFS-RemoteVolumeMonitor-WARNING **: 01:03:38.828: remote volume monitor with dbus name org.gtk.vfs.GPhoto2VolumeMonitor is not supported

(xfce4-terminal:2284): GVFS-RemoteVolumeMonitor-WARNING **: 01:03:44.722: remote volume monitor with dbus name org.gtk.vfs.HalVolumeMonitor is not supported

>>>>>>>>>>>>>MARKER: next xfce4-panel Gtk-CRITICAL messages seem to be generated by xev(1).
(xfce4-panel:2261): Gtk-CRITICAL **: 01:04:42.172: gtk_icon_theme_load_icon: assertion 'icon_name != NULL' failed

(xfce4-panel:2261): Gtk-CRITICAL **: 01:04:42.178: gtk_icon_theme_load_icon: assertion 'icon_name != NULL' failed

(xfce4-panel:2261): Gtk-CRITICAL **: 01:04:42.260: gtk_icon_theme_load_icon: assertion 'icon_name != NULL' failed

(xfce4-panel:2261): Gtk-CRITICAL **: 01:04:42.267: gtk_icon_theme_load_icon: assertion 'icon_name != NULL' failed

(xfce4-panel:2261): Gtk-CRITICAL **: 01:04:42.325: gtk_icon_theme_load_icon: assertion 'icon_name != NULL' failed

(Thunar:2263): Gtk-CRITICAL **: 01:04:49.036: gtk_main_quit: assertion 'main_loops != NULL' failed
xinit: connection to X server lost

waiting for X server to shut down .(II) Server terminated successfully (0). Closing log file.

What I have installed as packages grepped on gtk:

% pkg info | grep -i gtk
at-spi2-atk-2.26.2             Assisted Technology Provider module for GTK+
gdk-pixbuf2-2.40.0             Graphic library for GTK+
greybird-theme-3.22.12         Gtk and xfwm4 themes for the Xfce Desktop
gtk-murrine-engine-0.98.2_5    Murrine GTK+ 2.x cairo based engine
gtk-update-icon-cache-2.24.32  Gtk-update-icon-cache utility from the Gtk+ toolkit
gtk2-2.24.32                   Gimp Toolkit for X11 GUI (previous stable version)
gtk3-3.24.10_1                 Gimp Toolkit for X11 GUI (current stable version)
gtksourceview3-3.24.8_3        Text widget that adds syntax highlighting to the GtkTextView widget
webkit2-gtk3-2.28.1            Opensource browser engine using the GTK+ 3 toolkit

Last edited by eric (2020-04-30 08:10:19)

eriefisher · 2020-04-27 19:58:22

Normally you startxfce4 not startx. Although I'm not sure if BSD has any other requirements as I've never used it. You could use startx if you add startxfce4 to your .xinitrc file then startx will startxfce4. That's confusing!

eric · 2020-04-27 20:19:38

Thanks, however, as per FreeBSD handbook: 5.7.3. Xfce I've created .xinitrc:

% echo ". /usr/local/etc/xdg/xfce4/xinitrc" > ~/.xinitrc

(When comparing to X & twm I've (temp.) renamed .xinitrc.)

Tried starting by startxfce4: same critical errors and even some new errors, like:

###!!! [Child][MessageChannel] Error: (msgtype=0x37012D,name=PContent::Msg_AsyncMessage) Channel closing: too late to send/recv, messages will be lost

P.S. I suspect the xfce-UP-arrow problem is not related; I haven't saved the earlier err output (before installing x11/libxfce4menu version: 4.14.1_1) but from memory: the same troubles arose when starting xfce before the update.

Last edited by eric (2020-04-27 21:30:21)

eriefisher · 2020-04-27 22:00:30

Do you have a .xsession-errors file in your home directory? It may shed some light? You may also want to try and install a login manager. I use Lightdm(don't know if it's available with BSD) or GDM to handle the startup stuff.

Edit: On the Prev page from the link you posted from the handbook it shows XDM. It would also be a good choice for a login manager,

Last edited by eriefisher (2020-04-27 22:11:27)

eric · 2020-04-27 22:48:17

No .xsession-errors file is currently being generated (for both root & non-root user); I've captured the OP-output by:

 % (startx > startx.out) >& startxerr.out

For the moment I forego installing a display manager/graphical login manager.

Last edited by eric (2020-04-27 22:50:32)

eric · 2020-04-30 07:26:14

I've extended my OP with an update.

Last edited by eric (2020-04-30 07:29:13)

Clio · 2020-04-30 12:22:08

The command startxfce4 does not create an error.log in the home directory.
The command startx creates a logfile, because this command is also used by all display managers.

Xfce Forum

Sub domains

#1 2020-04-27 18:37:09

xfce commandline start problems

#2 2020-04-27 19:58:22

Re: xfce commandline start problems

#3 2020-04-27 20:19:38

Re: xfce commandline start problems

#4 2020-04-27 22:00:30

Re: xfce commandline start problems

#5 2020-04-27 22:48:17

Re: xfce commandline start problems

#6 2020-04-30 07:26:14

Re: xfce commandline start problems

#7 2020-04-30 12:22:08

Re: xfce commandline start problems

Board footer