SOLVED - Plasma Hangs After Login for a Couple of Minutes

Everything about X, Gnome, KDE, ... and everything running on it

SOLVED - Plasma Hangs After Login for a Couple of Minutes

Postby Llewen » 2018-12-25 22:56

I'm having an issue that I can't find an answer on. After I log into my computer it will hang for a couple of minutes before continuing. Yes, I've googled extensively, all of the links concerned bugs that either didn't apply, or have been fixed, and I have tried multiple solutions including deleting .Xauthority and logging back in without rebooting.

Observations which may or may not be relevant:

-The problems seemed to start after I tried installing some wayland packages because I have multiple video cards and I wanted to see if I could put them to good use. I've since uninstalled all the wayland related packages I could without completely nuking the system.
- I have noticed that the audio clicks right after the hang ends, indicated that the audio driver has successfully loaded.
-The Mimetype error messages are related to my icon theme. I have tried changing the theme which made no difference.
- I had no luck finding useful information on kscreen event error 147.
- Other than this annoying 2 min hang after login, the system seems to be working perfectly.

This is my basic hardware information from Sandra when I had Windows installed:
Code: Select all
Chassis : Desktop
Mainboard : ASUS CROSSHAIR V FORMULA-Z
BIOS : AMI (OEM) 2201 03/23/2015
Total Memory : 31.78GB Unknown STD EDO SIMM DIMM ESDRAM DDR2 DDR3 Micro-DIMM FB-DIMM

Processors
Processor : AMD FX(tm)-8350 Eight-Core Processor            (4M 8T 4.64GHz, 2.2GHz IMC, 4x 2MB L2, 8MB L3)

Chipset
Memory Controller : AMD F15 (Orochi) CPU HT Hub 2x 1.1GHz (2.2GHz), 2x 16GB Unknown STD EDO SIMM DIMM ESDRAM DDR2 DDR3 Micro-DIMM FB-DIMM  2GHz 128-bit

Memory Module(s)
Memory Module : G.Skill F3-2400C10-8GTX 8GB DIMM DDR3 PC3-19200U DDR3-2400 (9-9-9-25 4-34-10-5)
Memory Module : G.Skill F3-2400C10-8GTX 8GB DIMM DDR3 PC3-19200U DDR3-2400 (9-9-9-25 4-34-10-5)
Memory Module : G.Skill F3-2400C10-8GTX 8GB DIMM DDR3 PC3-19200U DDR3-2400 (9-9-9-25 4-34-10-5)
Memory Module : G.Skill F3-2400C10-8GTX 8GB DIMM DDR3 PC3-19200U DDR3-2400 (9-9-9-25 4-34-10-5)

Video System
Monitor/Panel : ACR XG270HU
      (2560x1440, 27.0")
Monitor/Panel : ACR XG270HU
      (1920x1080, 27.0")
Video Adapter : 2x Radeon RX 580 Series (36CU 2304SP SM5.1 1.34GHz, 16kB L2, 8GB DDR3 8GHz 256-bit, PCIe 3.00 x16)

Storage Devices
4 X 240GB SSD
Seagate ST8000VN0022-2EL112 (8TB, SATA2x1, 3.5", 7200rpm) : 7TB
ASUS    BW-12B1ST   a (SATA2x1, BD-RE, DVD+-RW, CD-RW) : N/A

Peripherals
Audio Device : ASUS Virtuoso 100 (Xonar Essence STX)
Keyboard:  Logitech G510 Gaming Keyboard
Mouse:  Logitech G502 Gaming Mouse
Input Device:  Logitech G13 Gameboard

Network Services
Network Adapter : Intel(R) 82583V Gigabit Network Connection (Ethernet, 1Gbps)


This is my basic system information:
Code: Select all
Operating System: Debian GNU/Linux
KDE Plasma Version: 5.14.3
Qt Version: 5.11.2
KDE Frameworks Version: 5.51.0
Kernel Version: 4.19.0-1-amd64
OS Type: 64-bit
Processors: 8 × AMD FX(tm)-8350 Eight-Core Processor
Memory: 31.2 GiB of RAM


Output of glxinfo | grep "version"
Code: Select all
server glx version string: 1.4
client glx version string: 1.4
GLX version: 1.4
    Max core profile version: 4.5
    Max compat profile version: 4.4
    Max GLES1 profile version: 1.1
    Max GLES[23] profile version: 3.2
OpenGL core profile version string: 4.5 (Core Profile) Mesa 18.2.7
OpenGL core profile shading language version string: 4.50
OpenGL version string: 4.4 (Compatibility Profile) Mesa 18.2.7
OpenGL shading language version string: 4.40
OpenGL ES profile version string: OpenGL ES 3.2 Mesa 18.2.7
OpenGL ES profile shading language version string: OpenGL ES GLSL ES 3.20


This is the contents of my syslog which shows the hang. The syslog is always the same at the time of the hang:
Code: Select all
Dec 25 18:35:41 NAME systemd[1]: Stopped User Manager for UID 115.
Dec 25 18:35:41 NAME systemd[1]: Stopping User Runtime Directory /run/user/115...
Dec 25 18:35:41 NAME systemd[1249]: run-user-115.mount: Succeeded.
Dec 25 18:35:41 NAME systemd[1]: run-user-115.mount: Succeeded.
Dec 25 18:35:41 NAME systemd[1]: user-runtime-dir@115.service: Succeeded.
Dec 25 18:35:41 NAME systemd[1]: Stopped User Runtime Directory /run/user/115.
Dec 25 18:35:41 NAME systemd[1]: Removed slice User Slice of UID 115.
Dec 25 18:38:10 NAME dbus-daemon[1316]: [session uid=1000 pid=1316] Activating service name='org.kde.kglobalaccel' requested by ':1.1
25' (uid=1000 pid=4957 comm="kded5 [kdeinit5]                                  ")
Dec 25 18:38:10 NAME dbus-daemon[1316]: [session uid=1000 pid=1316] Successfully activated service 'org.kde.kglobalaccel'
Dec 25 18:38:10 NAME org.kde.kglobalaccel[1316]: Invalid Context= "Mimetypes" line for icon theme:  "/home/llewen/.local/share/icons/
Newaita-dark/mimetypes/16@2x/"
Dec 25 18:38:10 NAME org.kde.kglobalaccel[1316]: Invalid Context= "Mimetypes" line for icon theme:  "/home/llewen/.local/share/icons/
Newaita-dark/mimetypes/22@2x/"
Dec 25 18:38:10 NAME org.kde.kglobalaccel[1316]: Invalid Context= "Mimetypes" line for icon theme:  "/home/llewen/.local/share/icons/
Newaita-dark/mimetypes/24@2x/"
Dec 25 18:38:10 NAME org.kde.kglobalaccel[1316]: Invalid Context= "Mimetypes" line for icon theme:  "/home/llewen/.local/share/icons/
Newaita-dark/mimetypes/32@2x/"
Dec 25 18:38:10 NAME org.kde.kglobalaccel[1316]: Invalid Context= "Mimetypes" line for icon theme:  "/home/llewen/.local/share/icons/
Newaita-dark/mimetypes/48@2x/"
Dec 25 18:38:10 NAME org.kde.kglobalaccel[1316]: Invalid Context= "Mimetypes" line for icon theme:  "/home/llewen/.local/share/icons/
Newaita-dark/mimetypes/64@2x/"
Dec 25 18:38:10 NAME dbus-daemon[1316]: [session uid=1000 pid=1316] Activating service name='org.kde.KScreen' requested by ':1.125' (
uid=1000 pid=4957 comm="kded5 [kdeinit5]                                  ")
Dec 25 18:38:10 NAME dbus-daemon[1316]: [session uid=1000 pid=1316] Successfully activated service 'org.kde.KScreen'
Dec 25 18:38:10 NAME org.kde.KScreen[1316]: kscreen.xrandr: Connected output 128 to CRTC 122
Dec 25 18:38:10 NAME org.kde.KScreen[1316]: kscreen.xrandr: Connected output 129 to CRTC 123
Dec 25 18:38:10 NAME org.kde.KScreen[1316]: kscreen.xcb.helper: Detected XRandR 1.6
Dec 25 18:38:10 NAME org.kde.KScreen[1316]: kscreen.xcb.helper: Event Base:  89
Dec 25 18:38:10 NAME org.kde.KScreen[1316]: kscreen.xcb.helper: Event Error:  147
Dec 25 18:38:10 NAME org.kde.KScreen[1316]: kscreen.xrandr: XRandR::setConfig
Dec 25 18:38:10 NAME org.kde.KScreen[1316]: kscreen.xrandr: Requested screen size is QSize(4480, 1440)


This dmesg output from the same time frame:
Code: Select all
[Dec25 18:35] usb 4-1: USB disconnect, device number 2
[  +3.116628] usb 4-1: new full-speed USB device number 4 using ohci-pci
[  +0.200766] usb 4-1: New USB device found, idVendor=046d, idProduct=c22d, bcdDevice=11.72
[  +0.000004] usb 4-1: New USB device strings: Mfr=1, Product=2, SerialNumber=0
[  +0.000003] usb 4-1: Product: G510s Gaming Keyboard
[  +0.000003] usb 4-1: Manufacturer: Logitech
[  +0.006616] input: Logitech G510s Gaming Keyboard as /devices/pci0000:00/0000:00:12.0/usb4/4-1/4-1:1.0/0003:046D:C22D.000D/input/input25
[  +0.057059] hid-generic 0003:046D:C22D.000D: input,hidraw1: USB HID v1.11 Keyboard [Logitech G510s Gaming Keyboard] on usb-0000:00:12.0-1/input0
[  +0.003332] input: Logitech G510s Gaming Keyboard Consumer Control as /devices/pci0000:00/0000:00:12.0/usb4/4-1/4-1:1.1/0003:046D:C22D.000E/input/input26
[  +0.056571] hid-generic 0003:046D:C22D.000E: input,hiddev1,hidraw2: USB HID v1.11 Device [Logitech G510s Gaming Keyboard] on usb-0000:00:12.0-1/input1
[Dec25 18:38] input: G15 Extra Keys as /devices/virtual/input/input28


journalctl output from the same time frame:
Code: Select all
Dec 25 18:35:41 NAME systemd[4795]: Stopped target Timers.
Dec 25 18:35:41 NAME systemd[4795]: Stopped target Paths.
Dec 25 18:35:41 NAME systemd[4795]: Stopped target Sockets.
Dec 25 18:35:41 NAME systemd[4795]: gpg-agent-browser.socket: Succeeded.
Dec 25 18:35:41 NAME systemd[4795]: Closed GnuPG cryptographic agent and passphrase cache (access for web browsers).
Dec 25 18:35:41 NAME systemd[4795]: pulseaudio.socket: Succeeded.
Dec 25 18:35:41 NAME systemd[4795]: Closed Sound System.
Dec 25 18:35:41 NAME systemd[4795]: gpg-agent-extra.socket: Succeeded.
Dec 25 18:35:41 NAME systemd[4795]: Closed GnuPG cryptographic agent and passphrase cache (restricted).
Dec 25 18:35:41 NAME systemd[4795]: dirmngr.socket: Succeeded.
Dec 25 18:35:41 NAME systemd[4795]: Closed GnuPG network certificate management daemon.
Dec 25 18:35:41 NAME systemd[4795]: gpg-agent.socket: Succeeded.
Dec 25 18:35:41 NAME systemd[4795]: Closed GnuPG cryptographic agent and passphrase cache.
Dec 25 18:35:41 NAME systemd[4795]: gpg-agent-ssh.socket: Succeeded.
Dec 25 18:35:41 NAME systemd[4795]: Closed GnuPG cryptographic agent (ssh-agent emulation).
Dec 25 18:35:41 NAME systemd[4795]: dbus.socket: Succeeded.
Dec 25 18:35:41 NAME systemd[4795]: Closed D-Bus User Message Bus Socket.
Dec 25 18:35:41 NAME systemd[4795]: Reached target Shutdown.
Dec 25 18:35:41 NAME systemd[4795]: systemd-exit.service: Succeeded.
Dec 25 18:35:41 NAME systemd[4795]: Started Exit the Session.
Dec 25 18:35:41 NAME systemd[4795]: Reached target Exit the Session.
Dec 25 18:35:41 NAME systemd[1]: user@115.service: Succeeded.
Dec 25 18:35:41 NAME systemd[1]: Stopped User Manager for UID 115.
Dec 25 18:35:41 NAME systemd[1]: Stopping User Runtime Directory /run/user/115...
Dec 25 18:35:41 NAME systemd[1249]: run-user-115.mount: Succeeded.
Dec 25 18:35:41 NAME systemd[1]: run-user-115.mount: Succeeded.
Dec 25 18:35:41 NAME systemd[1]: user-runtime-dir@115.service: Succeeded.
Dec 25 18:35:41 NAME systemd[1]: Stopped User Runtime Directory /run/user/115.
Dec 25 18:35:41 NAME systemd[1]: Removed slice User Slice of UID 115.
Dec 25 18:38:10 NAME dbus-daemon[1316]: [session uid=1000 pid=1316] Activating service name='org.kde.kglobalaccel' requested by ':1.1
Dec 25 18:38:10 NAME dbus-daemon[1316]: [session uid=1000 pid=1316] Successfully activated service 'org.kde.kglobalaccel'
Dec 25 18:38:10 NAME org.kde.kglobalaccel[1316]: Invalid Context= "Mimetypes" line for icon theme:  "/home/name/.local/share/icons/
Dec 25 18:38:10 NAME org.kde.kglobalaccel[1316]: Invalid Context= "Mimetypes" line for icon theme:  "/home/name/.local/share/icons/
Dec 25 18:38:10 NAME org.kde.kglobalaccel[1316]: Invalid Context= "Mimetypes" line for icon theme:  "/home/name/.local/share/icons/
Dec 25 18:38:10 NAME org.kde.kglobalaccel[1316]: Invalid Context= "Mimetypes" line for icon theme:  "/home/name/.local/share/icons/
Dec 25 18:38:10 NAME org.kde.kglobalaccel[1316]: Invalid Context= "Mimetypes" line for icon theme:  "/home/name/.local/share/icons/
Dec 25 18:38:10 NAME org.kde.kglobalaccel[1316]: Invalid Context= "Mimetypes" line for icon theme:  "/home/name/.local/share/icons/
Dec 25 18:38:10 NAME dbus-daemon[1316]: [session uid=1000 pid=1316] Activating service name='org.kde.KScreen' requested by ':1.125' (
Dec 25 18:38:10 NAME dbus-daemon[1316]: [session uid=1000 pid=1316] Successfully activated service 'org.kde.KScreen'
Dec 25 18:38:10 NAME org.kde.KScreen[1316]: kscreen.xrandr: Connected output 128 to CRTC 122
Dec 25 18:38:10 NAME org.kde.KScreen[1316]: kscreen.xrandr: Connected output 129 to CRTC 123
Dec 25 18:38:10 NAME org.kde.KScreen[1316]: kscreen.xcb.helper: Detected XRandR 1.6
Dec 25 18:38:10 NAME org.kde.KScreen[1316]: kscreen.xcb.helper: Event Base:  89
Dec 25 18:38:10 NAME org.kde.KScreen[1316]: kscreen.xcb.helper: Event Error:  147
Dec 25 18:38:10 NAME org.kde.KScreen[1316]: kscreen.xrandr: XRandR::setConfig
Last edited by Llewen on 2018-12-26 14:31, edited 2 times in total.
Llewen
 
Posts: 6
Joined: 2018-12-25 22:03

Re: Plasma Hangs After Login for a Couple of Minutes

Postby Llewen » 2018-12-25 23:29

Minor edit to the op.
Llewen
 
Posts: 6
Joined: 2018-12-25 22:03

Re: Plasma Hangs After Login for a Couple of Minutes

Postby Llewen » 2018-12-26 10:20

It looks like it's related to my G510s keyboard.
Llewen
 
Posts: 6
Joined: 2018-12-25 22:03

Re: Plasma Hangs After Login for a Couple of Minutes

Postby Llewen » 2018-12-26 13:00

Tried removing the g510s packages that I had installed. No joy, still hanging.

Tried reinstalling the g510s packages. No joy, still hanging.

I've also looked at the dmesg for the times of the hang and I'm not seeing the messages regarding the usb peripherals, so that looks like a bust.

I'm pretty much at square 1 with this right now, I have no idea what is causing the problem.
Llewen
 
Posts: 6
Joined: 2018-12-25 22:03

Re: Plasma Hangs After Login for a Couple of Minutes

Postby Llewen » 2018-12-26 13:10

I'm wondering if this is an issue with multiple gpu's. I think I will try a different forum due to the overwhelming number of responses I have received here... :)
Llewen
 
Posts: 6
Joined: 2018-12-25 22:03

Re: Plasma Hangs After Login for a Couple of Minutes

Postby Llewen » 2018-12-26 14:30

Found the answer:

Code: Select all
For a (temporary) workaround you can create a file
/etc/security/limits.d/systemd.conf containing:

* hard nofile 524288
Llewen
 
Posts: 6
Joined: 2018-12-25 22:03

Re: SOLVED - Plasma Hangs After Login for a Couple of Minute

Postby piper » 2018-12-28 12:33

It might also help to let others know (when asking for help) that you are running debian sid and not debian stable, makes a big difference.

https://forum.siduction.org/index.php?t ... 1#msg61271
User avatar
piper
 
Posts: 92
Joined: 2005-07-03 08:29


Return to Desktop & Multimedia

Who is online

Users browsing this forum: No registered users and 7 guests

fashionable