seduction
 Language:
Welcome, Guest. Please login or register.
Did you miss your activation email?
2019/06/26, 06:55:18


Help

Author [EN] [PL] [ES] [PT] [IT] [DE] [FR] [NL] [TR] [SR] [AR] [RU] Topic: SOLVED - Plasma Hangs After Login for a Couple of Minutes  (Read 387 times)

0 Members and 1 Guest are viewing this topic.

Offline Llewen

  • User
  • Posts: 13
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.- I'm leaning towards this being an issue with multiple gpu's.

This is my basic hardware information from Sandra when I had Windows installed:
Code: [Select]
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]
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]
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]
Dec 26 09:39:42 NAME systemd[1]: user@115.service: Succeeded.
Dec 26 09:39:42 NAME systemd[1]: Stopped User Manager for UID 115.
Dec 26 09:39:42 NAME systemd[1]: Stopping User Runtime Directory /run/user/115...
Dec 26 09:39:42 NAME systemd[1326]: run-user-115.mount: Succeeded.
Dec 26 09:39:42 NAME systemd[1]: run-user-115.mount: Succeeded.
Dec 26 09:39:42 NAME systemd[1]: user-runtime-dir@115.service: Succeeded.
Dec 26 09:39:42 NAME systemd[1]: Stopped User Runtime Directory /run/user/115.
Dec 26 09:39:42 NAME systemd[1]: Removed slice User Slice of UID 115.
Dec 26 09:39:47 NAME systemd[1]: NetworkManager-dispatcher.service: Succeeded.
Dec 26 09:39:49 NAME systemd[1]: systemd-fsckd.service: Succeeded.
Dec 26 09:39:50 NAME systemd-timesyncd[703]: Synchronized to time server 62.112.194.89:123 (2.debian.pool.ntp.org).
Dec 26 09:39:50 NAME systemd[1]: systemd-hostnamed.service: Succeeded.
Dec 26 09:42:08 NAME dbus-daemon[1362]: [session uid=1000 pid=1362] Activating service name='org.kde.kglobalaccel' requested by ':1.1
0' (uid=1000 pid=1513 comm="/usr/bin/kaccess ")
Dec 26 09:42:08 NAME dbus-daemon[1362]: [session uid=1000 pid=1362] Activating service name='ca.desrt.dconf' requested by ':1.11' (ui
d=1000 pid=1523 comm="/usr/bin/gsettings set org.gnome.desktop.a11y.appl")
Dec 26 09:42:08 NAME dbus-daemon[1362]: [session uid=1000 pid=1362] Successfully activated service 'ca.desrt.dconf'
Dec 26 09:42:08 NAME dbus-daemon[1362]: [session uid=1000 pid=1362] Successfully activated service 'org.kde.kglobalaccel'
Dec 26 09:42:08 NAME org.kde.kglobalaccel[1362]: Invalid Context= "Mimetypes" line for icon theme:  "/home/llewen/.local/share/icons/
Newaita-dark/mimetypes/16@2x/"
Dec 26 09:42:08 NAME org.kde.kglobalaccel[1362]: Invalid Context= "Mimetypes" line for icon theme:  "/home/llewen/.local/share/icons/
Newaita-dark/mimetypes/22@2x/"
Dec 26 09:42:08 NAME org.kde.kglobalaccel[1362]: Invalid Context= "Mimetypes" line for icon theme:  "/home/llewen/.local/share/icons/
Newaita-dark/mimetypes/24@2x/"
Dec 26 09:42:08 NAME org.kde.kglobalaccel[1362]: Invalid Context= "Mimetypes" line for icon theme:  "/home/llewen/.local/share/icons/
Newaita-dark/mimetypes/32@2x/"
Dec 26 09:42:08 NAME org.kde.kglobalaccel[1362]: Invalid Context= "Mimetypes" line for icon theme:  "/home/llewen/.local/share/icons/
Newaita-dark/mimetypes/48@2x/"
Dec 26 09:42:08 NAME org.kde.kglobalaccel[1362]: Invalid Context= "Mimetypes" line for icon theme:  "/home/llewen/.local/share/icons/
Newaita-dark/mimetypes/64@2x/"
Dec 26 09:42:08 NAME dbus-daemon[1362]: [session uid=1000 pid=1362] Activating service name='org.kde.KScreen' requested by ':1.9' (ui
d=1000 pid=1507 comm="kded5 [kdeinit5]                                  ")
Dec 26 09:42:08 NAME dbus-daemon[1362]: [session uid=1000 pid=1362] Successfully activated service 'org.kde.KScreen'
Dec 26 09:42:08 NAME org.kde.KScreen[1362]: kscreen.xrandr: Connected output 128 to CRTC 122
Dec 26 09:42:08 NAME org.kde.KScreen[1362]: kscreen.xrandr: Connected output 129 to CRTC 123
Dec 26 09:42:08 NAME org.kde.KScreen[1362]: kscreen.xcb.helper: Detected XRandR 1.6
Dec 26 09:42:08 NAME org.kde.KScreen[1362]: kscreen.xcb.helper: Event Base:  89
Dec 26 09:42:08 NAME org.kde.KScreen[1362]: kscreen.xcb.helper: Event Error:  147
Dec 26 09:42:08 NAME org.kde.KScreen[1362]: kscreen.xrandr: XRandR::setConfig
Dec 26 09:42:08 NAME org.kde.KScreen[1362]: kscreen.xrandr: Requested screen size is QSize(4480, 1440)
Dec 26 09:42:08 NAME org.kde.KScreen[1362]: kscreen.xrandr: Needed CRTCs:  2
Dec 26 09:42:08 NAME org.kde.KScreen[1362]: kscreen.xrandr: Actions to perform:
Dec 26 09:42:08 NAME org.kde.KScreen[1362]: kscreen.xrandr: #011Primary Output: false
Dec 26 09:42:08 NAME org.kde.KScreen[1362]: kscreen.xrandr: #011Change Screen Size: true
Dec 26 09:42:08 NAME org.kde.KScreen[1362]: kscreen.xrandr: #011#011Old: QSize(5120, 1440)
Dec 26 09:42:08 NAME org.kde.KScreen[1362]: kscreen.xrandr: #011#011Intermediate: QSize(5120, 1440)
Dec 26 09:42:08 NAME org.kde.KScreen[1362]: kscreen.xrandr: #011#011New: QSize(4480, 1440)
Dec 26 09:42:08 NAME org.kde.KScreen[1362]: kscreen.xrandr: #011Disable outputs: false
Dec 26 09:42:08 NAME org.kde.KScreen[1362]: kscreen.xrandr: #011Change outputs: true
Dec 26 09:42:08 NAME org.kde.KScreen[1362]: kscreen.xrandr: #011#011 (128, 129)
Dec 26 09:42:08 NAME org.kde.KScreen[1362]: kscreen.xrandr: #011Enable outputs: false
Dec 26 09:42:08 NAME org.kde.KScreen[1362]: kscreen.xrandr: RRSetCrtcConfig (change output)
Dec 26 09:42:08 NAME org.kde.KScreen[1362]: kscreen.xrandr: #011Output: 128 ( "DisplayPort-0" )
Dec 26 09:42:08 NAME org.kde.KScreen[1362]: kscreen.xrandr: #011CRTC: 122
Dec 26 09:42:08 NAME org.kde.KScreen[1362]: kscreen.xrandr: #011Pos: QPoint(0,0)
Dec 26 09:42:08 NAME org.kde.KScreen[1362]: kscreen.xrandr: #011Mode: 135 KScreen::Mode(Id: "135" , Size: QSize(2560, 1440) @ 143.856
 )

journalctl output from the same time frame:
Code: [Select]
Dec 26 09:39:18 NAME kernel: RAMDISK: [mem 0x37253000-0x37920fff]
Dec 26 09:39:18 NAME kernel: ACPI: Early table checksum verification disabled
Dec 26 09:39:18 NAME kernel: ACPI: RSDP 0x000000009A76D000 000024 (v02 ALASKA)
Dec 26 09:39:18 NAME kernel: ACPI: XSDT 0x000000009A76D078 000064 (v01 ALASKA A M I    01072009 AMI  00010013)
Dec 26 09:39:18 NAME kernel: ACPI: FACP 0x000000009A774290 00010C (v05 ALASKA A M I    01072009 AMI  00010013)
Dec 26 09:39:18 NAME kernel: ACPI BIOS Warning (bug): Optional FADT field Pm2ControlBlock has valid Length but zero Address: 0x000000
Dec 26 09:39:18 NAME kernel: ACPI: DSDT 0x000000009A76D170 007119 (v02 ALASKA A M I    00000000 INTL 20051117)
Dec 26 09:39:18 NAME kernel: ACPI: FACS 0x000000009B591F80 000040
Dec 26 09:39:18 NAME kernel: ACPI: APIC 0x000000009A7743A0 00009E (v03 ALASKA A M I    01072009 AMI  00010013)
Dec 26 09:39:18 NAME kernel: ACPI: FPDT 0x000000009A774440 000044 (v01 ALASKA A M I    01072009 AMI  00010013)
Dec 26 09:39:18 NAME kernel: ACPI: MCFG 0x000000009A774488 00003C (v01 ALASKA A M I    01072009 MSFT 00010013)
Dec 26 09:39:18 NAME kernel: ACPI: HPET 0x000000009A7744C8 000038 (v01 ALASKA A M I    01072009 AMI  00000005)
Dec 26 09:39:18 NAME kernel: ACPI: SSDT 0x000000009A791630 000D3C (v01 AMD    POWERNOW 00000001 AMD  00000001)
Dec 26 09:39:18 NAME kernel: ACPI: VFCT 0x000000009A774558 01D0A0 (v01 ALASKA A M I    00000001 AMD  31504F47)
...skipping...
Dec 26 09:42:08 NAME rtkit-daemon[1582]: Successfully called chroot.
Dec 26 09:42:08 NAME rtkit-daemon[1582]: Successfully dropped privileges.
Dec 26 09:42:08 NAME rtkit-daemon[1582]: Successfully limited resources.
Dec 26 09:42:08 NAME rtkit-daemon[1582]: Running.
Dec 26 09:42:08 NAME rtkit-daemon[1582]: Watchdog thread running.
Dec 26 09:42:08 NAME rtkit-daemon[1582]: Canary thread running.
Dec 26 09:42:08 NAME rtkit-daemon[1582]: Successfully made thread 1577 of process 1577 (n/a) owned by '1000' high priority at nice le
Dec 26 09:42:08 NAME rtkit-daemon[1582]: Supervising 1 threads of 1 processes of 1 users.
Dec 26 09:42:08 NAME kernel: fuse init (API version 7.27)
Dec 26 09:42:08 NAME systemd[1]: Mounting FUSE Control File System...
Dec 26 09:42:08 NAME systemd[1]: Mounted FUSE Control File System.
« Last Edit: 2018/12/26, 16:18:07 by Llewen »

Offline hendrikL

  • User
  • Posts: 316
Re: Plasma Hangs After Login for a Couple of Minutes
« Reply #1 on: 2018/12/26, 15:29:24 »
did you read that thread?
https://forum.siduction.org/index.php?topic=7508.0

maybe there are two answers that could solve that problem.

Offline Llewen

  • User
  • Posts: 13
Re: Plasma Hangs After Login for a Couple of Minutes
« Reply #2 on: 2018/12/26, 15:54:11 »
So perhaps the answer is that this is a known bug and just wait for an update?  If I know that this is a known bug, and not because of something I screwed up, I won't have a problem waiting for a fix.  It's annoying, but it isn't a show stopper.

Offline devil

  • Administrator
  • User
  • *****
  • Posts: 4.337
Re: Plasma Hangs After Login for a Couple of Minutes
« Reply #3 on: 2018/12/26, 15:59:15 »
Does no one read upgrade warnings? There is even 2 ways to fix this.

Offline jure

  • User
  • Posts: 477
Re: Plasma Hangs After Login for a Couple of Minutes
« Reply #4 on: 2018/12/26, 16:04:02 »
as written in the bugreport you can do this

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

* hard nofile 524288
Gruss Juergen

Offline Llewen

  • User
  • Posts: 13
Re: Plasma Hangs After Login for a Couple of Minutes
« Reply #5 on: 2018/12/26, 16:15:21 »
Thanks so much, that fixed it.  When you are a noob, there aren't enough hours in the day to read everything everyone expects you to read, and you have no idea what's important and what isn't.  I have a few ideas, but finding this kind of information on google is a nightmare.

Offline Llewen

  • User
  • Posts: 13
Re: SOLVED - Plasma Hangs After Login for a Couple of Minutes
« Reply #6 on: 2018/12/26, 16:38:26 »
I should also say, I'm not using Siduction.  I just had it from a reliable source that the people here know their stuff.  I am running vanilla Debian Sid.  So I didn't get the warnings your update scripts would have provided.  I may eventually go that route.  But I do, very much appreciate you taking the time to respond to my post and help me out, and I swear, I didn't post here until I spent days, literally, banging my head against the wall trying to find an answer.
Noobs often don't know what questions to ask, or where to ask the questions, so if I shouldn't have posted here, I apologize.

Offline piper

  • Global Moderator
  • User
  • *****
  • Posts: 1.632
  • we are the priests ... of the temples of syrinx
Re: SOLVED - Plasma Hangs After Login for a Couple of Minutes
« Reply #7 on: 2018/12/26, 19:07:40 »
All is good

Get used to reading a lot, it's a no-brainer in a sid environment, whether the forums or what apt is telling you
"We're all grown up and don't freak out when a piece of text contains the word 'fuck'. I still don't understand why people think that the word 'fuck' is what would keep certain groups from contributing to the Linux kernel. In all seriousness, it doesn't."

John Paul Adrian Glaubitz