You are not logged in.

Pages: 1

#1 2020-04-27 21:31:05

makosmos
Member
Registered: 2019-12-25
Posts: 28

[SOLVED] SDDM After login display issue

Hello,

I've just installed sddm as my display manager, after login it starts the window manager spectrwm
The issue is that the screen doesn't seems to clear itself anymore (but it can still draw on top of previous draws)
Thus, after login, I can see some remenant of sddm between the bar and the apllication's windows:
https://postimg.cc/2bvdg82M (I've exagerated border gap to show that sddm doesn't clear)
This display issue is for everything, for example if I switch to an empty workspace, the display of the previous workspace will not be cleared
I also noticed that there is now some tearing

As you can see, the display was fine before using sddm :
https://postimg.cc/YL1JjwMV

Here the .local/share/sddm/xorg-session.log

Apr 27 23:32 : exception: Decoder plugin 'wildmidi' is unavailable: configuration file does not exist: /etc/timidity/timidity.cfg
Apr 27 23:32 : exception: Input plugin 'tidal' is unavailable: No Tidal application token configured
Apr 27 23:32 : exception: Input plugin 'qobuz' is unavailable: No Qobuz app_id configured
spectrwm: Welcome to spectrwm V3.3.0 Build: 3.3.0

(The exception are from mpd)

Xorg is the display server used
I've tried to enable the high dpi option in sddm config but it didn't fixed it

Thanks in advance for your help

Last edited by makosmos (2020-04-29 12:45:15)

Offline

#2 2020-04-27 21:48:40

V1del
Forum Moderator
Registered: 2012-10-16
Posts: 25,363

Re: [SOLVED] SDDM After login display issue

Sounds like an issue in spectrewm rather than sddm. Once you're in spectrewm sddm should not matter anymore. Can you reproduce this on other window managers?

There are a few "anymores" in this post, what did you use beforehand? Which xorg driver do you use? if xf86-video-intel, try removing it.

Last edited by V1del (2020-04-27 21:50:14)

Offline

#3 2020-04-27 21:56:26

makosmos
Member
Registered: 2019-12-25
Posts: 28

Re: [SOLVED] SDDM After login display issue

You're right, it's because of spectrwm since awesome works fine
The driver used was indeed, xf86-video-intel, I replaced in xorg.conf the driver "intel" by "modesetting" but it doesn't change anything
The issue is now to fix spectrwm...

Last edited by makosmos (2020-04-27 22:02:15)

Offline

#4 2020-04-29 10:03:04

makosmos
Member
Registered: 2019-12-25
Posts: 28

Re: [SOLVED] SDDM After login display issue

Some updates:
It don't think the display issue is related to spectrwm. Indeed, there is an artifact (tearing) on awesome too that I've fixed in the past by modifying the xorg's config file.
Maybe sddm doesn't correctly start the Xserver (don't load the xorg.conf file) ?

Last edited by makosmos (2020-04-29 10:03:22)

Offline

#5 2020-04-29 10:21:38

V1del
Forum Moderator
Registered: 2012-10-16
Posts: 25,363

Re: [SOLVED] SDDM After login display issue

What's your xorg config? Post your xorg log. And no, SDDM doesn't do anything here, xorg starts and xorg reads the config. Tearing is generally to be expected unless you use a compositor (or xf86-video-intel's TearFree option, but xf86-video-intel has quite a few different issues...). Have you tried using startx and does it "just" work if you use startx?

Offline

#6 2020-04-29 10:33:29

makosmos
Member
Registered: 2019-12-25
Posts: 28

Re: [SOLVED] SDDM After login display issue

Here's my xorg.conf

Section "ServerLayout"
	Identifier     "X.org Configured"
	Screen      1  "Screen1"
	InputDevice    "Mouse0" "CorePointer"
	InputDevice    "Keyboard0" "CoreKeyboard"
EndSection

Section "Files"
	ModulePath   "/usr/lib/xorg/modules"
	FontPath     "/usr/share/fonts/misc"
	FontPath     "/usr/share/fonts/TTF"
	FontPath     "/usr/share/fonts/OTF"
	FontPath     "/usr/share/fonts/Type1"
	FontPath     "/usr/share/fonts/100dpi"
	FontPath     "/usr/share/fonts/75dpi"
EndSection

Section "Module"
	Load  "glx"
EndSection

Section "InputDevice"
	Identifier  "Keyboard0"
	Driver      "kbd"
EndSection

Section "InputDevice"
	Identifier  "Mouse0"
	Driver      "mouse"
	Option	    "Protocol" "auto"
	Option	    "Device" "/dev/input/mice"
	Option	    "ZAxisMapping" "4 5 6 7"
EndSection

Section "Monitor"
	Identifier   "Monitor0"
	VendorName   "Monitor Vendor"
	ModelName    "Monitor Model"
EndSection

Section "Monitor"
	Identifier   "Monitor1"
	VendorName   "Monitor Vendor"
	ModelName    "Monitor Model"
EndSection

Section "Device"
        ### Available Driver options are:-
        ### Values: <i>: integer, <f>: float, <bool>: "True"/"False",
        ### <string>: "String", <freq>: "<f> Hz/kHz/MHz",
        ### <percent>: "<f>%"
        ### [arg]: arg optional
        #Option     "Accel"              	"True"	
        #Option     "SWcursor"           	# [<bool>]
        #Option     "EnablePageFlip"     	# [<bool>]
        #Option     "ColorTiling"        	"True"	
        #Option     "ColorTiling2D"      	"True"
        #Option     "RenderAccel"        	# [<bool>]
        #Option     "SubPixelOrder"      	# [<str>]
        #Option     "AccelMethod"        	# <str>
        #Option     "ShadowPrimary"      	# [<bool>]
        #Option     "EXAVSync"           	# [<bool>]
        #Option     "EXAPixmaps"         	# [<bool>]
        #Option     "ZaphodHeads"        	# <str>
        #Option     "SwapbuffersWait"    	# [<bool>]
        #Option     "DeleteUnusedDP12Displays" 	# [<bool>]
        #Option     "DRI3"               	# [<bool>]
        #Option     "DRI"                	# <i>
        #Option     "TearFree"           	"True"
	Identifier  "radeon"
	Driver      "radeon"
	BusID       "PCI:1:0:0"
EndSection

#Section "OutputClass"
#	Identifier "radeon"
#	MatchDriver "radeon"
#	Option "PrimaryGPU" "yes"
#EndSection

Section "Device"
        ### Available Driver options are:-
        ### Values: <i>: integer, <f>: float, <bool>: "True"/"False",
        ### <string>: "String", <freq>: "<f> Hz/kHz/MHz",
        ### <percent>: "<f>%"
        ### [arg]: arg optional
        #Option     "SWcursor"           	# [<bool>]
        #Option     "kmsdev"             	# <str>
        #Option     "ShadowFB"           	# [<bool>]
        #Option     "AccelMethod"        	# <str>
        #Option     "PageFlip"           	# [<bool>]
        #Option     "ZaphodHeads"        	# <str>
        #Option     "DoubleShadow"       	# [<bool>]
        #Option     "Atomic"             	# [<bool>]
	Option      "TearFree"			"true"
	Identifier  "Card1"
	Driver      "intel"
	BusID       "PCI:0:2:0"
EndSection

Section "Screen"
	Identifier "Screen1"
	Device     "Card1"
	Monitor    "Monitor1"
	SubSection "Display"
		Viewport   0 0
		Depth     1
	EndSubSection
	SubSection "Display"
		Viewport   0 0
		Depth     4
	EndSubSection
	SubSection "Display"
		Viewport   0 0
		Depth     8
	EndSubSection
	SubSection "Display"
		Viewport   0 0
		Depth     15
	EndSubSection
	SubSection "Display"
		Viewport   0 0
		Depth     16
	EndSubSection
	SubSection "Display"
		Viewport   0 0
		Depth     24
	EndSubSection
EndSection

Here the xorg-session.log under ~/.local/share/sddm

Apr 29 12:31 : exception: Decoder plugin 'wildmidi' is unavailable: configuration file does not exist: /etc/timidity/timidity.cfg
Apr 29 12:31 : exception: Input plugin 'tidal' is unavailable: No Tidal application token configured
Apr 29 12:31 : exception: Input plugin 'qobuz' is unavailable: No Qobuz app_id configured
spectrwm: Welcome to spectrwm V3.3.0 Build: 3.3.0
[1077:1077:0429/123119.636814:ERROR:vaapi_wrapper.cc(481)] vaInitialize failed: unknown libva error
[1077:1077:0429/123119.698078:ERROR:sandbox_linux.cc(374)] InitializeSandbox() called with multiple threads in process gpu-process.
[1050:1059:0429/123121.796597:ERROR:rewards_service_impl.cc(194)] Failed to read file: /home/makosmos/.config/BraveSoftware/Brave-Browser/Default/ledger_state
[1129:1129:0429/123121.796762:ERROR:ledger_impl.cc(113)] Failed to initialize wallet
[1394:1:0429/123125.764874:ERROR:child_process_sandbox_support_impl_linux.cc(79)] FontService unique font name matching request did not receive a response.
[1394:1:0429/123125.776294:ERROR:child_process_sandbox_support_impl_linux.cc(79)] FontService unique font name matching request did not receive a response.
[1394:1:0429/123125.787114:ERROR:child_process_sandbox_support_impl_linux.cc(79)] FontService unique font name matching request did not receive a response.
[1394:1:0429/123125.794358:ERROR:child_process_sandbox_support_impl_linux.cc(79)] FontService unique font name matching request did not receive a response.
[1395:1:0429/123126.388307:ERROR:child_process_sandbox_support_impl_linux.cc(79)] FontService unique font name matching request did not receive a response.
[1395:1:0429/123126.390367:ERROR:child_process_sandbox_support_impl_linux.cc(79)] FontService unique font name matching request did not receive a response.
[1394:1:0429/123126.604394:ERROR:child_process_sandbox_support_impl_linux.cc(79)] FontService unique font name matching request did not receive a response.
[1395:1:0429/123126.698354:ERROR:child_process_sandbox_support_impl_linux.cc(79)] FontService unique font name matching request did not receive a response.
[1395:1:0429/123126.699244:ERROR:child_process_sandbox_support_impl_linux.cc(79)] FontService unique font name matching request did not receive a response.
[1395:1:0429/123126.700717:ERROR:child_process_sandbox_support_impl_linux.cc(79)] FontService unique font name matching request did not receive a response.
[1395:1:0429/123126.701127:ERROR:child_process_sandbox_support_impl_linux.cc(79)] FontService unique font name matching request did not receive a response.

I don't have any clues about theses errors
Yes everything is working fine with startx command

Last edited by makosmos (2020-04-29 10:35:07)

Offline

#7 2020-04-29 12:44:42

makosmos
Member
Registered: 2019-12-25
Posts: 28

Re: [SOLVED] SDDM After login display issue

Okay so after installing and running the window compositor picom, all the problems disappeared !
By the way, the errors in xorg-session.log was because I remove in the sddm.conf the line 

ServerArguments=-nolisten tcp

Offline

Pages: 1

Board footer

Powered by FluxBB