After pkg upgrade: No DE's like xfce seem to work anymore, but sddm, fluxbox or kodi-standalone work

I have experienced this on two different computers, one upgraded from 11.2 to 11.3 (amd64) and then 'pkg upgrade' and another one from 12.0 to 12.1 and then 'pkg upgrade' as well. Both have nvidia-cards, on both everything was fine, sddm with xfce4. And it is in both cases that after the 'pkg upgrade' suddenly xfce only gives a black screen with a mouse pointer, but sddm works fine. I can also start kodi from sddm, so it does not seem a problem with X. I am saying this, because after the upgrade from 12.0 to 12.1 everything worked fine, the problem only appears after the upgrade of the packages.
'xinit fluxbox' also works fine. But 'xinit startxfce4' or just 'startxfce4' from the console does not. First option shows a terminal on a black screen with the following message:

Code:
/usr/local/bib/startxfce4: X server already running on display :0
xfce4-session: No GPG agent found

Someone else in another forum reported that after a 'pkg upgrade' kde does not work anymore either, so it seems to be the same Problem. I am using quarterly packages. I do not have a .xinitrc and I never had.

My guess is that some package that is related to more complex DE's other that fluxbox is bad, unless something here has significantly changed about the usage of DE's which I don't know of.
 
I wonder if that X display in the error message is sddm. Is there a way to kill it? (Of course, you may have done so already when you tried xinit startxfce4 in which case I apologize for wasting your time.)
 
I did not even start sddm. It is commented (right expression, when I want to say there is a # before sddm_enable="YES" in /etc/rc.conf?)
 
You can say commented. I think "commented out" is more widely used, but everyone would know what you mean when you say commented.
Anyway, sorry that that wasn't the issue.
 
https://docs.xfce.org/xfce/xfce4-session/advanced
By default xfce4-session tries to start the gpg- or ssh-agent. To disable this run the following commands:
xfconf-query -c xfce4-session -p /startup/ssh-agent/enabled -n -t bool -s false
xfconf-query -c xfce4-session -p /startup/gpg-agent/enabled -n -t bool -s false
To force the ssh-agent instead of the gpg-agent use the following command:
xfconf-query -c xfce4-session -p /startup/ssh-agent/type -n -t string -s ssh-agent
In case you want to use gnome-keyring enable the Launch GNOME services on startup in the Advanced tab of the settings dialog. If you do this xfce4-session will not attempt to start the gpg- or ssh-agent.

According to this you need gpg - is it installed?
https://dst.lbl.gov/ksblog/2011/05/xfce-without-gpg-agent/comment-page-1/
 
Thanks for the advice, but it did not solve the problem:

I first did a 'pkg install pgpgpg' and switched to another console, and from there 'startxfce4'. Still black screen.
I startet fluxbox with 'xinit fluxbox', opened a terminal and copied the lines

Code:
xfconf-query -c xfce4-session -p /startup/ssh-agent/enabled -n -t bool -s false
xfconf-query -c xfce4-session -p /startup/gpg-agent/enabled -n -t bool -s false

one by one and executed them. Exited fluxbox and tried 'startxfce4' again. Got a black screen again.
When I do a CTRL+ALT+F2 it switches into a console that has a lot of log messages even with colours, which I can terminate with CTRL+C. What is that log and how can I save it to post it here? I know that log would show up in a terminal in the upper left if xfce4 actually worked, as it does when I do a 'xinit fluxbox'.

Another discovery on the matter: I have installed mate and it does work when starting it with 'xinit mate-session'.
 
Have you tried it with a fresh created user? Maybe a present configuration is interfering with xfce4.

When I do a CTRL+ALT+F2 it switches into a console that has a lot of log messages even with colours, which I can terminate with CTRL+C. What is that log ...
Those are loggings of errors from programs and services running inside xorg.

... how can I save it to post it here?
To safe the console output you can use script(1). Run script logxfce4, run startxfce4, return to console where you started the command, end xorg Ctrl+C, end script Ctrl +D, post logxfce4.
 
Thanks! So here it is:

Have you tried it with a fresh created user? Maybe a present configuration is interfering with xfce4.

Yes, I did, but here is the strange thing: The first time it works, but when exiting xfce4 and trying to start it again same problem. Only if you delete the folders .config/xfce4 and .config/Thunar (you have to delete both!) it works again. So it looks that xfce writes itself an initial configuration that does not work?
 

Attachments

  • logxfce4.txt
    4.5 KB · Views: 204
It looks that this problem with xfce only appears in connection with nvidia-drivers. Today I installed xfce on a new 12.1 system with nvidia-driver-304 and again, first login works fine, but second login gives black screen. Apparently this thread has something to do with the issue. Can someone make something out of this?

 
Not that I have a machine with nVidia drivers, but one symptom looks easy enough to check: do you have something like this on your xorg conf file(s)?
Code:
Option         "metamodes" "nvidia-auto-select +0+0 {ForceCompositionPipeline=On}"
If so, does it help to comment out (place a '#' before it) that line?
 
That entry does not exist in my xorg.conf. Neither do I have anything in /usr/local/etc/X11/xorg.conf.d:

Code:
$ more /etc/X11/xorg.conf
# nvidia-xconfig: X configuration file generated by nvidia-xconfig
# nvidia-xconfig:  version 415.25

Section "ServerLayout"
    Identifier     "Layout0"
    Screen      0  "Screen0"
    InputDevice    "Keyboard0" "CoreKeyboard"
    InputDevice    "Mouse0" "CorePointer"
EndSection

Section "Files"
EndSection

Section "InputDevice"
    # generated from default
    Identifier     "Mouse0"
    Driver         "mouse"
    Option         "Protocol" "auto"
    Option         "Device" "/dev/sysmouse"
    Option         "Emulate3Buttons" "no"
    Option         "ZAxisMapping" "4 5"
EndSection

Section "InputDevice"
    # generated from default
    Identifier     "Keyboard0"
    Driver         "keyboard"
EndSection

Section "Monitor"
    Identifier     "Monitor0"
    VendorName     "Unknown"
    ModelName      "Unknown"
    HorizSync       28.0 - 33.0
    VertRefresh     43.0 - 72.0
    Option         "DPMS"
EndSection

Section "Device"
    Identifier     "Device0"
    Driver         "nvidia"
    VendorName     "NVIDIA Corporation"
EndSection

Section "Screen"
    Identifier     "Screen0"
    Device         "Device0"
    Monitor        "Monitor0"
    DefaultDepth    24
    SubSection     "Display"
        Depth       24
    EndSubSection
EndSection

Code:
$ ls -a /usr/local/etc/X11/xorg.conf.d/
.  ..
 
And does /var/log/Xorg.0.log contain anything interesting (in other words: lines with error messages related to your problem)?
 
No problem as far as I can see in Xorg.0.log:

Code:
[    71.331]
X.Org X Server 1.18.4
Release Date: 2016-07-19
[    71.331] X Protocol Version 11, Revision 0
[    71.331] Build Operating System: FreeBSD 12.0-RELEASE-p12 i386
[    71.332] Current Operating System: FreeBSD elvis69.local 12.1-RELEASE FreeBSD 12.1-RELEASE r354233 GENERIC i386
[    71.332] Build Date: 31 December 2019  08:19:40AM
[    71.332] 
[    71.332] Current version of pixman: 0.38.4
[    71.332]     Before reporting problems, check http://wiki.x.org
    to make sure that you have the latest version.
[    71.332] Markers: (--) probed, (**) from config file, (==) default setting,
    (++) from command line, (!!) notice, (II) informational,
    (WW) warning, (EE) error, (NI) not implemented, (??) unknown.
[    71.332] (==) Log file: "/var/log/Xorg.0.log", Time: Thu Mar 12 12:57:44 2020
[    71.336] (==) Using config file: "/etc/X11/xorg.conf"
[    71.340] (==) ServerLayout "Layout0"
[    71.340] (**) |-->Screen "Screen0" (0)
[    71.340] (**) |   |-->Monitor "Monitor0"
[    71.341] (**) |   |-->Device "Device0"
[    71.341] (**) |-->Input Device "Keyboard0"
[    71.341] (**) |-->Input Device "Mouse0"
[    71.341] (==) Automatically adding devices
[    71.341] (==) Automatically enabling devices
[    71.341] (==) Not automatically adding GPU devices
[    71.342] (==) Max clients allowed: 256, resource mask: 0x1fffff
[    71.355] (==) FontPath set to:
    /usr/local/share/fonts/misc/,
    /usr/local/share/fonts/TTF/,
    /usr/local/share/fonts/OTF/,
    /usr/local/share/fonts/Type1/,
    /usr/local/share/fonts/100dpi/,
    /usr/local/share/fonts/75dpi/,
    catalogue:/usr/local/etc/X11/fontpath.d
[    71.356] (==) ModulePath set to "/usr/local/lib/xorg/modules"
[    71.356] (WW) Hotplugging is on, devices using drivers 'kbd', 'mouse' or 'vmmouse' will be disabled.
[    71.356] (WW) Disabling Keyboard0
[    71.356] (WW) Disabling Mouse0
[    71.356] (II) Loader magic: 0x824a150
[    71.356] (II) Module ABI versions:
[    71.356]     X.Org ANSI C Emulation: 0.4
[    71.356]     X.Org Video Driver: 20.0
[    71.356]     X.Org XInput driver : 22.1
[    71.356]     X.Org Server Extension : 9.0
[    71.357] (--) PCI:*(0:1:0:0) 10de:01d7:1025:0090 rev 161, Mem @ 0xd1000000/16777216, 0xc0000000/268435456, 0xd0000000/16777216, BIOS @ 0x????????/65536
[    71.358] (II) LoadModule: "glx"
[    71.360] (II) Loading /usr/local/lib/xorg/modules/extensions/libglx.so
[    71.952] (II) Module glx: vendor="NVIDIA Corporation"
[    71.952]     compiled for 4.0.2, module version = 1.0.0
[    71.952]     Module class: X.Org Server Extension
[    71.953] (II) NVIDIA GLX Module  304.137  Thu Sep 14 13:54:16 PDT 2017
[    71.953] (II) LoadModule: "nvidia"
[    71.954] (II) Loading /usr/local/lib/xorg/modules/drivers/nvidia_drv.so
[    71.967] (II) Module nvidia: vendor="NVIDIA Corporation"
[    71.968]     compiled for 4.0.2, module version = 1.0.0
[    71.968]     Module class: X.Org Video Driver
[    71.970] (II) NVIDIA dlloader X Driver  304.137  Thu Sep 14 13:35:03 PDT 2017
[    71.970] (II) NVIDIA Unified Driver for all Supported NVIDIA GPUs
[    71.971] (--) Using syscons driver with X support (version 2.0)
[    71.971] (--) using VT number 9

[    71.988] (II) Loading sub module "fb"
[    71.988] (II) LoadModule: "fb"
[    71.989] (II) Loading /usr/local/lib/xorg/modules/libfb.so
[    71.991] (II) Module fb: vendor="X.Org Foundation"
[    71.991]     compiled for 1.18.4, module version = 1.0.0
[    71.991]     ABI class: X.Org ANSI C Emulation, version 0.4
[    71.991] (II) Loading sub module "wfb"
[    71.991] (II) LoadModule: "wfb"
[    71.992] (II) Loading /usr/local/lib/xorg/modules/libwfb.so
[    71.994] (II) Module wfb: vendor="X.Org Foundation"
[    71.994]     compiled for 1.18.4, module version = 1.0.0
[    71.994]     ABI class: X.Org ANSI C Emulation, version 0.4
[    71.995] (II) Loading sub module "ramdac"
[    71.995] (II) LoadModule: "ramdac"
[    71.995] (II) Module "ramdac" already built-in
[    71.998] (WW) VGA arbiter: cannot open kernel arbiter, no multi-card support
[    71.998] (**) NVIDIA(0): Depth 24, (--) framebuffer bpp 32
[    71.998] (==) NVIDIA(0): RGB weight 888
[    71.998] (==) NVIDIA(0): Default visual is TrueColor
[    71.999] (==) NVIDIA(0): Using gamma correction (1.0, 1.0, 1.0)
[    72.003] (**) NVIDIA(0): Enabling 2D acceleration
[    73.282] (II) NVIDIA(0): NVIDIA GPU GeForce Go 7300 (G72) at PCI:1:0:0 (GPU-0)
[    73.282] (--) NVIDIA(0): Memory: 262144 kBytes
[    73.282] (--) NVIDIA(0): VideoBIOS: 05.72.22.58.30
[    73.282] (II) NVIDIA(0): Detected PCI Express Link width: 16X
[    73.282] (--) NVIDIA(0): Interlaced video modes are supported on this GPU
[    73.282] (--) NVIDIA(0): Valid display device(s) on GeForce Go 7300 at PCI:1:0:0
[    73.282] (--) NVIDIA(0):     CRT-0
[    73.282] (--) NVIDIA(0):     TV-0
[    73.282] (--) NVIDIA(0):     AU Optronics Corporation (DFP-0) (connected)
[    73.282] (--) NVIDIA(0):     DFP-1
[    73.282] (--) NVIDIA(0): CRT-0: 400.0 MHz maximum pixel clock
[    73.282] (--) NVIDIA(0): TV-0: 400.0 MHz maximum pixel clock
[    73.282] (--) NVIDIA(0): TV encoder: Unknown
[    73.282] (--) NVIDIA(0): AU Optronics Corporation (DFP-0): 330.0 MHz maximum pixel clock
[    73.282] (--) NVIDIA(0): AU Optronics Corporation (DFP-0): Internal Dual Link LVDS
[    73.282] (--) NVIDIA(0): DFP-1: 165.0 MHz maximum pixel clock
[    73.282] (--) NVIDIA(0): DFP-1: Internal Single Link TMDS
[    73.282] (**) NVIDIA(0): Using HorizSync/VertRefresh ranges from the EDID for display
[    73.282] (**) NVIDIA(0):     device AU Optronics Corporation (DFP-0) (Using EDID
[    73.282] (**) NVIDIA(0):     frequencies has been enabled on all display devices.)
[    73.282] (==) NVIDIA(0):
[    73.282] (==) NVIDIA(0): No modes were requested; the default mode "nvidia-auto-select"
[    73.282] (==) NVIDIA(0):     will be used as the requested mode.
[    73.282] (==) NVIDIA(0):
[    73.283] (II) NVIDIA(0): Validated MetaModes:
[    73.283] (II) NVIDIA(0):     "DFP-0:nvidia-auto-select"
[    73.283] (II) NVIDIA(0): Virtual screen size determined to be 1280 x 800
[    73.283] (WW) NVIDIA(0): Unable to support custom viewPortOut 1280 x 720 +0 +40
[    73.284] (WW) NVIDIA(0): Unable to support custom viewPortOut 1066 x 800 +107 +0
[    73.284] (WW) NVIDIA(0): Unable to support custom viewPortOut 1066 x 800 +107 +0
[    73.284] (WW) NVIDIA(0): Unable to support custom viewPortOut 1066 x 800 +107 +0
[    73.285] (--) NVIDIA(0): DPI set to (98, 96); computed from "UseEdidDpi" X config
[    73.285] (--) NVIDIA(0):     option
[    73.285] (--) Depth 24 pixmap format is 32 bpp
[    73.298] (II) NVIDIA(0): Setting mode "DFP-0:nvidia-auto-select"
[    74.552] (==) NVIDIA(0): Disabling shared memory pixmaps
[    74.552] (==) NVIDIA(0): Backing store enabled
[    74.552] (==) NVIDIA(0): Silken mouse enabled
[    74.555] (**) NVIDIA(0): DPMS enabled
[    74.558] (II) Loading sub module "dri2"
[    74.558] (II) LoadModule: "dri2"
[    74.558] (II) Module "dri2" already built-in
[    74.558] (II) NVIDIA(0): [DRI2] Setup complete
[    74.558] (II) NVIDIA(0): [DRI2]   VDPAU driver: nvidia
[    74.560] (--) RandR disabled
[    74.579] (II) Initializing extension GLX
[    74.579] (II) Indirect GLX disabled.(II) config/devd: probing input devices...
[    74.845] (II) config/devd: adding input device (null) (/dev/kbdmux)
[    74.846] (II) LoadModule: "kbd"
[    74.848] (II) Loading /usr/local/lib/xorg/modules/input/kbd_drv.so
[    74.849] (II) Module kbd: vendor="X.Org Foundation"
[    74.849]     compiled for 1.18.4, module version = 1.9.0
[    74.849]     Module class: X.Org XInput Driver
[    74.849]     ABI class: X.Org XInput driver, version 22.1
[    74.849] (II) Using input driver 'kbd' for 'kbdmux'
[    74.849] (**) kbdmux: always reports core events
[    74.849] (**) kbdmux: always reports core events
[    74.849] (**) Option "Protocol" "standard"
[    74.849] (**) Option "XkbRules" "base"
[    74.849] (**) Option "XkbModel" "pc105"
[    74.849] (**) Option "XkbLayout" "us"
[    74.849] (**) Option "config_info" "devd:kbdmux"
[    74.849] (II) XINPUT: Adding extended input device "kbdmux" (type: KEYBOARD, id 6)
[    74.853] (II) config/devd: kbdmux is enabled, ignoring device atkbd0
[    74.853] (II) config/devd: adding input device (null) (/dev/sysmouse)
[    74.853] (II) LoadModule: "mouse"
[    74.853] (II) Loading /usr/local/lib/xorg/modules/input/mouse_drv.so
[    74.855] (II) Module mouse: vendor="X.Org Foundation"
[    74.855]     compiled for 1.18.4, module version = 1.9.3
[    74.855]     Module class: X.Org XInput Driver
[    74.855]     ABI class: X.Org XInput driver, version 22.1
[    74.855] (II) Using input driver 'mouse' for 'sysmouse'
[    74.855] (**) sysmouse: always reports core events
[    74.855] (**) Option "Device" "/dev/sysmouse"
[    74.855] (==) sysmouse: Protocol: "Auto"
[    74.855] (**) sysmouse: always reports core events
[    74.855] (==) sysmouse: Emulate3Buttons, Emulate3Timeout: 50
[    74.856] (**) sysmouse: ZAxisMapping: buttons 4 and 5
[    74.856] (**) sysmouse: Buttons: 5
[    74.856] (**) Option "config_info" "devd:sysmouse"
[    74.856] (II) XINPUT: Adding extended input device "sysmouse" (type: MOUSE, id 7)
[    74.856] (**) sysmouse: (accel) keeping acceleration scheme 1
[    74.856] (**) sysmouse: (accel) acceleration profile 0
[    74.856] (**) sysmouse: (accel) acceleration factor: 2.000
[    74.856] (**) sysmouse: (accel) acceleration threshold: 4
[    74.856] (II) sysmouse: SetupAuto: hw.iftype is 4, hw.model is 0
[    74.856] (II) sysmouse: SetupAuto: protocol is SysMouse
[    74.903] (II) config/devd: adding input device Mouse (/dev/psm0)
[    74.903] (II) Using input driver 'mouse' for 'Mouse'
[    74.903] (**) Mouse: always reports core events
[    74.903] (**) Option "Device" "/dev/psm0"
[    74.903] (==) Mouse: Protocol: "Auto"
[    74.903] (**) Mouse: always reports core events
[    74.950] (==) Mouse: Emulate3Buttons, Emulate3Timeout: 50
[    74.950] (**) Mouse: ZAxisMapping: buttons 4 and 5
[    74.950] (**) Mouse: Buttons: 5
[    74.950] (**) Option "config_info" "devd:psm0"
[    74.950] (II) XINPUT: Adding extended input device "Mouse" (type: MOUSE, id 8)
[    74.950] (**) Mouse: (accel) keeping acceleration scheme 1
[    74.950] (**) Mouse: (accel) acceleration profile 0
[    74.950] (**) Mouse: (accel) acceleration factor: 2.000
[    74.950] (**) Mouse: (accel) acceleration threshold: 4
[    74.964] (II) Mouse: SetupAuto: hw.iftype is 3, hw.model is 0
[    74.964] (II) Mouse: SetupAuto: protocol is PS/2
[    75.404] (II) Mouse: ps2EnableDataReporting: succeeded
[    76.444] (**) NVIDIA(0): Using HorizSync/VertRefresh ranges from the EDID for display
[    76.444] (**) NVIDIA(0):     device AU Optronics Corporation (DFP-0) (Using EDID
[    76.444] (**) NVIDIA(0):     frequencies has been enabled on all display devices.)
[    78.367] (**) NVIDIA(0): Using HorizSync/VertRefresh ranges from the EDID for display
[    78.367] (**) NVIDIA(0):     device AU Optronics Corporation (DFP-0) (Using EDID
[    78.367] (**) NVIDIA(0):     frequencies has been enabled on all display devices.)

The way I see it, it is a xfwm4 problem. Because what I can do .e.g is login to openbox from sddm, which gives a blank screen, but if I start xterm and then execute xfce4-session & I get a fully functional xfce4-environment based on openbox.
 
Have you compared Xorg log files between your failed Xfce4 normal startup / try and the Xfce4 with openbox that you describe above? Do you see anything interesting?
 
I'll post the obligatory "meee too" but also give you guys log files from a just-built, binary-pkg system.

At work I install headless systems with XFCE + TightVNC. I just created my first system in a few months and now, using the same xstartup file that works on all my older systems, I get a blank white screen and an error that XFCE is already running. There are some nVidia Tesla V100s in the system but they are not display adapters and the driver is not installed. Hopefully this helps solve the problem.

Installed packages (plus many, many, auto-loaded dependencies):
Code:
xfce-4.14                      meta-port for the Xfce Desktop Environment
tightvnc-1.3.10_6              Enhanced version of VNC


xstartup is set to 755:
Code:
#!/bin/sh

unset SESSION_MANAGER
unset DBUS_SESSION_BUS_ADDRESS
xsetroot -solid grey
unset DBUS_SESSION_BUS_ADDRESS
exec /usr/local/bin/startxfce4 --with-ck-launch

The VNC log contains the following declaration that XFCE is already running:
Code:
27/03/20 12:59:49 Copyright (C) 2000-2009 TightVNC Group
27/03/20 12:59:49 Copyright (C) 1999 AT&T Laboratories Cambridge
27/03/20 12:59:49 All Rights Reserved.
27/03/20 12:59:49 See http://www.tightvnc.com/ for information on TightVNC
27/03/20 12:59:49 Desktop name 'X' (myhost:25)
27/03/20 12:59:49 Protocol versions supported: 3.3, 3.7, 3.8, 3.7t, 3.8t
27/03/20 12:59:49 Listening for VNC connections on TCP port 5925
27/03/20 12:59:49 Listening for HTTP connections on TCP port 5825
27/03/20 12:59:49   URL http://myhost:5825
/usr/local/bin/startxfce4: X server already running on display :25

27/03/20 12:59:58 Got connection from client x.x.x.x
27/03/20 12:59:58 Using protocol version 3.8
27/03/20 12:59:58 Enabling TightVNC protocol extensions
27/03/20 13:00:00 Full-control authentication passed by x.x.x.x
27/03/20 13:00:00 Using tight encoding for client x.x.x.x
27/03/20 13:00:00 rfbProcessClientNormalMessage: ignoring unknown encoding 16
27/03/20 13:00:00 Using image quality level 6 for client x.x.x.x
27/03/20 13:00:00 rfbProcessClientNormalMessage: ignoring unknown encoding -223
27/03/20 13:00:00 Enabling LastRect protocol extension for client x.x.x.x
27/03/20 13:00:00 Enabling cursor position updates for client x.x.x.x
27/03/20 13:00:00 Enabling full-color cursor updates for client x.x.x.x
27/03/20 13:00:10 Client x.x.x.x gone
27/03/20 13:00:10 Statistics:
27/03/20 13:00:10   key events received 0, pointer events 38
27/03/20 13:00:10   framebuffer updates 1, rectangles 4, bytes 1108
27/03/20 13:00:10     LastRect markers 1, bytes 12
27/03/20 13:00:10     cursor shape updates 1, bytes 1068
27/03/20 13:00:10     cursor position updates 1, bytes 12
27/03/20 13:00:10     tight rectangles 1, bytes 16
27/03/20 13:00:10   raw bytes equivalent 8294412, compression ratio 518400.750000
 
As I said above already, the problem seems to be xfwm4. As this problem seemed to appear in Linux also, it looks that the problem may be originated even before porting it to FreeBSD? So who would this issue have to be addressed to?
 
Back
Top