I’ve never had to use Mono, so I’m lost there.
Yeah, installing and setup on Ubuntu server went fine. So, if anyone wants to install on Fedora there appears to be some weird stuff going on with that. Probably restrictive policies causing packages to crash and blacklist.
Most likely the security context of the files was incorrect.
-# restorecon -Rv /var
restorecon changes the labels/context of the files to what SELinux expects them to be based on the directory they’re in.
So i.e. web server stuff should run in the httpd_t type domain, and the files should be labeled as httpd_content_t iirc.
And then there’s a bunch of booleans as well that might be interfering https://dwalsh.fedorapeople.org/SELinux/httpd_selinux.html
Also, sealert is your friend.
(from 10.08 a couple mins forward)
1 Like
Just following up, I couldn’t figure it out. I tried kernel 4.16, and diagnostics didn’t reveal anything. I did extensive testing on Windows and sold it. 
I ended up getting a great deal on an 8700K (just under $300) so I built a new rig for my nix programming. Running Fedora without issue. I may try Ryzen 2 later on, but under Linux it was abhorrent. I built the rig specifically for running Linux.
Thanks again for your advice.
1 Like
I’m still having persistent display issues with my Radeon WX5100 in Solus. The system appears to lose contact with the monitor at random times. Sometimes it takes days, and sometimes it happens just a few minutes after booting. The display will not come back until the computer is completely shut down (via SSH) and booted again. Restart does not fix the problem.
I am able to SSH in after the display disappears. xrandr -q says Can't open display.
After shutting down and booting:
journalctl -b -1 | grep drm
Apr 13 22:00:51 chariot kernel: [drm] amdgpu kernel modesetting enabled.
Apr 13 22:00:51 chariot kernel: [drm] initializing kernel modesetting (POLARIS10 0x1002:0x67C7 0x1002:0x0B0D 0x00).
Apr 13 22:00:51 chariot kernel: [drm] register mmio base: 0xDFE00000
Apr 13 22:00:51 chariot kernel: [drm] register mmio size: 262144
Apr 13 22:00:51 chariot kernel: [drm] probing gen 2 caps for device 8086:1901 = 261ac83/e
Apr 13 22:00:51 chariot kernel: [drm] probing mlw for device 8086:1901 = 261ac83
Apr 13 22:00:51 chariot kernel: [drm] UVD is enabled in VM mode
Apr 13 22:00:51 chariot kernel: [drm] UVD ENC is enabled in VM mode
Apr 13 22:00:51 chariot kernel: [drm] VCE enabled in VM mode
Apr 13 22:00:51 chariot kernel: [drm] GPU post is not needed
Apr 13 22:00:51 chariot kernel: [drm] vm size is 64 GB, block size is 13-bit, fragment size is 9-bit
Apr 13 22:00:51 chariot kernel: [drm] Detected VRAM RAM=8192M, BAR=256M
Apr 13 22:00:51 chariot kernel: [drm] RAM width 256bits GDDR5
Apr 13 22:00:51 chariot kernel: [drm] amdgpu: 8192M of VRAM memory ready
Apr 13 22:00:51 chariot kernel: [drm] amdgpu: 8192M of GTT memory ready.
Apr 13 22:00:51 chariot kernel: [drm] GART: num cpu pages 65536, num gpu pages 65536
Apr 13 22:00:51 chariot kernel: [drm] PCIE GART of 256M enabled (table at 0x000000F400040000).
Apr 13 22:00:51 chariot kernel: [drm] amdgpu: irq initialized.
Apr 13 22:00:51 chariot kernel: [drm] Chained IB support enabled!
Apr 13 22:00:51 chariot kernel: [drm] Found UVD firmware Version: 1.130 Family ID: 16
Apr 13 22:00:51 chariot kernel: [drm] Found VCE firmware Version: 53.26 Binary ID: 3
Apr 13 22:00:51 chariot kernel: [drm] DM_PPLIB: values for Engine clock
Apr 13 22:00:51 chariot kernel: [drm] DM_PPLIB: 30000
Apr 13 22:00:51 chariot kernel: [drm] DM_PPLIB: 42600
Apr 13 22:00:51 chariot kernel: [drm] DM_PPLIB: 58100
Apr 13 22:00:51 chariot kernel: [drm] DM_PPLIB: 72600
Apr 13 22:00:51 chariot kernel: [drm] DM_PPLIB: 87500
Apr 13 22:00:51 chariot kernel: [drm] DM_PPLIB: 92200
Apr 13 22:00:51 chariot kernel: [drm] DM_PPLIB: 100400
Apr 13 22:00:51 chariot kernel: [drm] DM_PPLIB: 108600
Apr 13 22:00:51 chariot kernel: [drm] DM_PPLIB: Warning: using default validation clocks!
Apr 13 22:00:51 chariot kernel: [drm] DM_PPLIB: Validation clocks:
Apr 13 22:00:51 chariot kernel: [drm] DM_PPLIB: engine_max_clock: 72000
Apr 13 22:00:51 chariot kernel: [drm] DM_PPLIB: memory_max_clock: 80000
Apr 13 22:00:51 chariot kernel: [drm] DM_PPLIB: level : 0
Apr 13 22:00:51 chariot kernel: [drm] DM_PPLIB: reducing engine clock level from 8 to 3
Apr 13 22:00:51 chariot kernel: [drm] DM_PPLIB: values for Memory clock
Apr 13 22:00:51 chariot kernel: [drm] DM_PPLIB: 30000
Apr 13 22:00:51 chariot kernel: [drm] DM_PPLIB: 125000
Apr 13 22:00:51 chariot kernel: [drm] DM_PPLIB: Warning: using default validation clocks!
Apr 13 22:00:51 chariot kernel: [drm] DM_PPLIB: Validation clocks:
Apr 13 22:00:51 chariot kernel: [drm] DM_PPLIB: engine_max_clock: 72000
Apr 13 22:00:51 chariot kernel: [drm] DM_PPLIB: memory_max_clock: 80000
Apr 13 22:00:51 chariot kernel: [drm] DM_PPLIB: level : 0
Apr 13 22:00:51 chariot kernel: [drm] DM_PPLIB: reducing memory clock level from 2 to 1
Apr 13 22:00:51 chariot kernel: [drm] DC: create_links: connectors_num: physical:4, virtual:0
Apr 13 22:00:51 chariot kernel: [drm] Display Core initialized!
Apr 13 22:00:51 chariot kernel: [drm] Rx Caps:
Apr 13 22:00:51 chariot kernel: [drm] HBR2x4 pass VS=3, PE=0
Apr 13 22:00:51 chariot kernel: [drm] LG Ultra HD: [Block 0]
Apr 13 22:00:51 chariot kernel: [drm] LG Ultra HD: [Block 1]
Apr 13 22:00:51 chariot kernel: [drm] dc_link_detect: manufacturer_id = 6D1E, product_id = 5B09, serial_number = 3B523, manufacture_week = 11, manufacture_year = 27, display_name = LG Ultra HD, speaker_flag = 1, audio_mode_count = 1
Apr 13 22:00:51 chariot kernel: [drm] dc_link_detect: mode number = 0, format_code = 1, channel_count = 2, sample_rate = 7, sample_size = 7
Apr 13 22:00:51 chariot kernel: [drm] Supports vblank timestamp caching Rev 2 (21.10.2013).
Apr 13 22:00:51 chariot kernel: [drm] Driver supports precise vblank timestamp query.
Apr 13 22:00:51 chariot kernel: [drm] ring test on 0 succeeded in 14 usecs
Apr 13 22:00:51 chariot kernel: [drm] ring test on 9 succeeded in 10 usecs
Apr 13 22:00:51 chariot kernel: [drm] ring test on 1 succeeded in 8 usecs
Apr 13 22:00:51 chariot kernel: [drm] ring test on 2 succeeded in 1 usecs
Apr 13 22:00:51 chariot kernel: [drm] ring test on 3 succeeded in 3 usecs
Apr 13 22:00:51 chariot kernel: [drm] ring test on 4 succeeded in 3 usecs
Apr 13 22:00:51 chariot kernel: [drm] ring test on 5 succeeded in 8 usecs
Apr 13 22:00:51 chariot kernel: [drm] ring test on 6 succeeded in 2 usecs
Apr 13 22:00:51 chariot kernel: [drm] ring test on 7 succeeded in 2 usecs
Apr 13 22:00:51 chariot kernel: [drm] ring test on 8 succeeded in 2 usecs
Apr 13 22:00:51 chariot kernel: [drm] ring test on 10 succeeded in 6 usecs
Apr 13 22:00:51 chariot kernel: [drm] ring test on 11 succeeded in 6 usecs
Apr 13 22:00:51 chariot kernel: [drm] ring test on 12 succeeded in 1 usecs
Apr 13 22:00:51 chariot kernel: [drm] ring test on 13 succeeded in 17 usecs
Apr 13 22:00:51 chariot kernel: [drm] ring test on 14 succeeded in 5 usecs
Apr 13 22:00:51 chariot kernel: [drm] UVD and UVD ENC initialized successfully.
Apr 13 22:00:51 chariot kernel: [drm] ring test on 15 succeeded in 7 usecs
Apr 13 22:00:51 chariot kernel: [drm] ring test on 16 succeeded in 4 usecs
Apr 13 22:00:51 chariot kernel: [drm] ring test on 17 succeeded in 4 usecs
Apr 13 22:00:51 chariot kernel: [drm] VCE initialized successfully.
Apr 13 22:00:51 chariot kernel: [drm] ib test on ring 0 succeeded
Apr 13 22:00:51 chariot kernel: [drm] ib test on ring 1 succeeded
Apr 13 22:00:51 chariot kernel: [drm] ib test on ring 2 succeeded
Apr 13 22:00:51 chariot kernel: [drm] ib test on ring 3 succeeded
Apr 13 22:00:51 chariot kernel: [drm] ib test on ring 4 succeeded
Apr 13 22:00:51 chariot kernel: [drm] ib test on ring 5 succeeded
Apr 13 22:00:51 chariot kernel: [drm] ib test on ring 6 succeeded
Apr 13 22:00:51 chariot kernel: [drm] ib test on ring 7 succeeded
Apr 13 22:00:51 chariot kernel: [drm] ib test on ring 8 succeeded
Apr 13 22:00:52 chariot kernel: [drm] ib test on ring 9 succeeded
Apr 13 22:00:52 chariot kernel: [drm] ib test on ring 10 succeeded
Apr 13 22:00:52 chariot kernel: [drm] ib test on ring 11 succeeded
Apr 13 22:00:52 chariot kernel: [drm] ib test on ring 12 succeeded
Apr 13 22:00:52 chariot kernel: [drm] ib test on ring 13 succeeded
Apr 13 22:00:52 chariot kernel: [drm] ib test on ring 14 succeeded
Apr 13 22:00:52 chariot kernel: [drm] ib test on ring 15 succeeded
Apr 13 22:00:52 chariot kernel: [drm] fb mappable at 0xC056A000
Apr 13 22:00:52 chariot kernel: [drm] vram apper at 0xC0000000
Apr 13 22:00:52 chariot kernel: [drm] size 33177600
Apr 13 22:00:52 chariot kernel: [drm] fb depth is 24
Apr 13 22:00:52 chariot kernel: [drm] pitch is 15360
Apr 13 22:00:52 chariot kernel: fbcon: amdgpudrmfb (fb0) is primary device
Apr 13 22:00:52 chariot kernel: [drm] {3840x2160, 4000x2222@533250Khz}
Apr 13 22:00:52 chariot kernel: [drm] HBR2x4 pass VS=3, PE=0
Apr 13 22:00:52 chariot kernel: amdgpu 0000:01:00.0: fb0: amdgpudrmfb frame buffer device
Apr 13 22:00:52 chariot kernel: [drm] Initialized amdgpu 3.23.0 20150101 for 0000:01:00.0 on minor 0
Apr 14 00:11:28 chariot kernel: [drm] {3840x2160, 4000x2222@533250Khz}
Apr 14 05:36:10 chariot kernel: [drm] HBR2x4 pass VS=3, PE=0
Apr 14 20:28:02 chariot kernel: [drm] {3840x2160, 4000x2222@533250Khz}
Apr 15 08:20:49 chariot kernel: [drm] HBR2x4 pass VS=3, PE=0
Apr 15 08:20:49 chariot kernel: [drm] {3840x2160, 4000x2222@533250Khz}
Apr 16 09:42:42 chariot kernel: [drm] HBR2x4 pass VS=3, PE=0
Apr 16 09:42:42 chariot kernel: [drm] {3840x2160, 4000x2222@533250Khz}
Apr 16 09:45:39 chariot kernel: [drm] HBR2x4 pass VS=3, PE=0
Apr 16 09:45:39 chariot kernel: [drm] {3840x2160, 4000x2222@533250Khz}
Apr 16 10:19:23 chariot kernel: [drm] HBR2x4 pass VS=3, PE=0
Apr 16 10:19:23 chariot kernel: [drm] Status:
Apr 16 11:25:33 chariot kernel: [drm] HBR2x4 pass VS=3, PE=0
Apr 16 16:28:55 chariot kernel: [drm:drm_atomic_helper_wait_for_flip_done [drm_kms_helper]] *ERROR* [CRTC:43:crtc-0] flip_done timed out
Apr 16 18:42:55 chariot kernel: [drm:drm_atomic_helper_wait_for_dependencies [drm_kms_helper]] *ERROR* [CRTC:43:crtc-0] flip_done timed out
I looked up these, but only found issues with Intel iGPUs. Didn’t find it helpful.
Apr 16 16:28:55 chariot kernel: [drm:drm_atomic_helper_wait_for_flip_done [drm_kms_helper]] *ERROR* [CRTC:43:crtc-0] flip_done timed out
Apr 16 18:42:55 chariot kernel: [drm:drm_atomic_helper_wait_for_dependencies [drm_kms_helper]] *ERROR* [CRTC:43:crtc-0] flip_done timed out
cat dmesg_dump_file | grep drm
[ 1002.383258] [drm] amdgpu kernel modesetting enabled.
[ 1002.398909] [drm] initializing kernel modesetting (POLARIS10 0x1002:0x67C7 0x1002:0x0B0D 0x00).
[ 1002.398923] [drm] register mmio base: 0xDFE00000
[ 1002.398923] [drm] register mmio size: 262144
[ 1002.398932] [drm] probing gen 2 caps for device 8086:1901 = 261ac83/e
[ 1002.398933] [drm] probing mlw for device 8086:1901 = 261ac83
[ 1002.398940] [drm] UVD is enabled in VM mode
[ 1002.398940] [drm] UVD ENC is enabled in VM mode
[ 1002.398942] [drm] VCE enabled in VM mode
[ 1002.399151] [drm] GPU post is not needed
[ 1002.399163] [drm] vm size is 64 GB, block size is 13-bit, fragment size is 9-bit
[ 1002.416753] [drm] Detected VRAM RAM=8192M, BAR=256M
[ 1002.416754] [drm] RAM width 256bits GDDR5
[ 1002.416799] [drm] amdgpu: 8192M of VRAM memory ready
[ 1002.416800] [drm] amdgpu: 8192M of GTT memory ready.
[ 1002.416834] [drm] GART: num cpu pages 65536, num gpu pages 65536
[ 1002.416877] [drm] PCIE GART of 256M enabled (table at 0x000000F400040000).
[ 1002.416937] [drm] amdgpu: irq initialized.
[ 1002.437126] [drm] Chained IB support enabled!
[ 1002.481635] [drm] Found UVD firmware Version: 1.130 Family ID: 16
[ 1002.484774] [drm] Found VCE firmware Version: 53.26 Binary ID: 3
[ 1002.539995] [drm] DM_PPLIB: values for Engine clock
[ 1002.539996] [drm] DM_PPLIB: 30000
[ 1002.539996] [drm] DM_PPLIB: 42600
[ 1002.539997] [drm] DM_PPLIB: 58100
[ 1002.539997] [drm] DM_PPLIB: 72600
[ 1002.539997] [drm] DM_PPLIB: 87500
[ 1002.539998] [drm] DM_PPLIB: 92200
[ 1002.539998] [drm] DM_PPLIB: 100400
[ 1002.539998] [drm] DM_PPLIB: 108600
[ 1002.539999] [drm] DM_PPLIB: Warning: using default validation clocks!
[ 1002.539999] [drm] DM_PPLIB: Validation clocks:
[ 1002.539999] [drm] DM_PPLIB: engine_max_clock: 72000
[ 1002.540000] [drm] DM_PPLIB: memory_max_clock: 80000
[ 1002.540000] [drm] DM_PPLIB: level : 0
[ 1002.540000] [drm] DM_PPLIB: reducing engine clock level from 8 to 3
[ 1002.540001] [drm] DM_PPLIB: values for Memory clock
[ 1002.540002] [drm] DM_PPLIB: 30000
[ 1002.540002] [drm] DM_PPLIB: 125000
[ 1002.540002] [drm] DM_PPLIB: Warning: using default validation clocks!
[ 1002.540002] [drm] DM_PPLIB: Validation clocks:
[ 1002.540003] [drm] DM_PPLIB: engine_max_clock: 72000
[ 1002.540003] [drm] DM_PPLIB: memory_max_clock: 80000
[ 1002.540003] [drm] DM_PPLIB: level : 0
[ 1002.540004] [drm] DM_PPLIB: reducing memory clock level from 2 to 1
[ 1002.540005] [drm] DC: create_links: connectors_num: physical:4, virtual:0
[ 1002.540480] [drm] Display Core initialized!
[ 1002.547061] [drm] Rx Caps:
[ 1002.595105] [drm] HBR2x4 pass VS=3, PE=0
[ 1002.596484] [drm] LG Ultra HD: [Block 0]
[ 1002.596486] [drm] LG Ultra HD: [Block 1]
[ 1002.596488] [drm] dc_link_detect: manufacturer_id = 6D1E, product_id = 5B09, serial_number = 3B523, manufacture_week = 11, manufacture_year = 27, display_name = LG Ultra HD, speaker_flag = 1, audio_mode_count = 1
[ 1002.596488] [drm] dc_link_detect: mode number = 0, format_code = 1, channel_count = 2, sample_rate = 7, sample_size = 7
[ 1002.598422] [drm] Supports vblank timestamp caching Rev 2 (21.10.2013).
[ 1002.598423] [drm] Driver supports precise vblank timestamp query.
[ 1002.599776] [drm] ring test on 0 succeeded in 14 usecs
[ 1002.600568] [drm] ring test on 9 succeeded in 10 usecs
[ 1002.600586] [drm] ring test on 1 succeeded in 8 usecs
[ 1002.600594] [drm] ring test on 2 succeeded in 1 usecs
[ 1002.600603] [drm] ring test on 3 succeeded in 3 usecs
[ 1002.600611] [drm] ring test on 4 succeeded in 3 usecs
[ 1002.600628] [drm] ring test on 5 succeeded in 8 usecs
[ 1002.600635] [drm] ring test on 6 succeeded in 2 usecs
[ 1002.600641] [drm] ring test on 7 succeeded in 2 usecs
[ 1002.600648] [drm] ring test on 8 succeeded in 2 usecs
[ 1002.600695] [drm] ring test on 10 succeeded in 6 usecs
[ 1002.600703] [drm] ring test on 11 succeeded in 6 usecs
[ 1002.627412] [drm] ring test on 12 succeeded in 1 usecs
[ 1002.627452] [drm] ring test on 13 succeeded in 17 usecs
[ 1002.627465] [drm] ring test on 14 succeeded in 5 usecs
[ 1002.627465] [drm] UVD and UVD ENC initialized successfully.
[ 1002.738388] [drm] ring test on 15 succeeded in 7 usecs
[ 1002.738401] [drm] ring test on 16 succeeded in 4 usecs
[ 1002.738413] [drm] ring test on 17 succeeded in 4 usecs
[ 1002.738413] [drm] VCE initialized successfully.
[ 1002.738661] [drm] ib test on ring 0 succeeded
[ 1002.738811] [drm] ib test on ring 1 succeeded
[ 1002.738848] [drm] ib test on ring 2 succeeded
[ 1002.738890] [drm] ib test on ring 3 succeeded
[ 1002.738920] [drm] ib test on ring 4 succeeded
[ 1002.738964] [drm] ib test on ring 5 succeeded
[ 1002.739002] [drm] ib test on ring 6 succeeded
[ 1002.739046] [drm] ib test on ring 7 succeeded
[ 1002.739087] [drm] ib test on ring 8 succeeded
[ 1003.240152] [drm] ib test on ring 9 succeeded
[ 1003.240256] [drm] ib test on ring 10 succeeded
[ 1003.240358] [drm] ib test on ring 11 succeeded
[ 1003.242160] [drm] ib test on ring 12 succeeded
[ 1003.244715] [drm] ib test on ring 13 succeeded
[ 1003.247248] [drm] ib test on ring 14 succeeded
[ 1003.247592] [drm] ib test on ring 15 succeeded
[ 1003.253221] [drm] fb mappable at 0xC056A000
[ 1003.253224] [drm] vram apper at 0xC0000000
[ 1003.253226] [drm] size 33177600
[ 1003.253228] [drm] fb depth is 24
[ 1003.253229] [drm] pitch is 15360
[ 1003.253440] fbcon: amdgpudrmfb (fb0) is primary device
[ 1003.286648] [drm] {3840x2160, 4000x2222@533250Khz}
[ 1003.317718] [drm] HBR2x4 pass VS=3, PE=0
[ 1003.379539] amdgpu 0000:01:00.0: fb0: amdgpudrmfb frame buffer device
[ 1003.388447] [drm] Initialized amdgpu 3.23.0 20150101 for 0000:01:00.0 on minor 0
The relevant boot options in Solus are:
radeon.si_support=0 radeon.cik_support=0 amdgpu.si_support=1 amdgpu.cik_support=1
The displayport cable is a DP1.4 cable that is loose and not near any sources of interference.
Any guidance here would be awesome.
EDIT
Hopefully this will just solve my problem…
https://www.phoronix.com/scan.php?page=news_item&px=AMDGPU-DC-Fixes-For-4.16
ISPConfig 3.1 + SELinux…
seriously? This is still a problem? I remember sorting this out for 3.0. Cleaning up some mail servers aaaaaaand its this BS again.
SELinux, you are about to get secure-booted…
(FYI, I usually just sort out the alerts and enable as needed, but debugging errors that result in “nothing to do” when I perform the requested action is more than I have the patience for right now)
Care to share?
-# ausearch -c ispconfig
-# audit2allow -b
Or for a quickie:
-# audit2allow -bw | grep ispconfig
1 Like
Still sorting through some obvious stuff that can be fixed… Once that’s done, I’ll try again and see if I am still getting errors or misbehavior.
#!!! The file ‘/var/www/ispconfig’ is mislabeled on your system.
#!!! Fix with $ restorecon -R -v /var/www/ispconfig
That context restore was successful. So, on to the next…
This is after I have done:
setsebool -P httpd_can_network_connect_db 1
setsebool -P httpd_can_network_memcache 1
setsebool -P httpd_unified 1
semanage fcontext -a -t httpd_log_t "/var/log/ispconfig/httpd(/.)?"
restorecon -R -v /var/log/ispconfig/httpd(/.)?
audit2allow -bw:
type=AVC msg=audit(1523981224.930:203): avc: denied { write } for pid=2052 comm=“php-cgi” name=“temp” dev=“dm-0” ino=1000435 scontext=system_u:system_r:httpd_sys_script_t:s0 tcontext=unconfined_u:object_r:usr_t:s0 tclass=dir
Was caused by:
Missing type enforcement (TE) allow rule.
You can use audit2allow to generate a loadable module to allow this access.
type=AVC msg=audit(1523981224.934:204): avc: denied { remove_name } for pid=1419 comm=766C6F676765722028616363657373 name=“access.log” dev=“dm-0” ino=1002491 scontext=system_u:system_r:httpd_t:s0 tcontext=system_u:object_r:httpd_log_t:s0 tclass=dir
Was caused by:
Missing type enforcement (TE) allow rule.
You can use audit2allow to generate a loadable module to allow this access.
hmmmm, no paths there???
Yeah that’s a bit weird, haven’t encountered that before, or never notice at least. Anywho you could allow those actions using the pid as an identifier to create custom modules.
-# ausearch -p 2052 --raw | audit2allow -M my-ispconfig-php-cgi-thingy
-# ausearch -p 1419 --raw | audit2allow -M my-ispconfig-log-thingy
To give httpd_sys_script_t:s0 write perms on usr_t:s0 objects ( that usr_t could be a hint on the path )
And to allow processes in the httpd_t:s0 domain to modify httpd_log_t:s0 objects ( Shouldn’t that be allowed by default? What kind of action exactly is ‘remove_name’ btw? )
I have switched to LTS kernel for now (currently 4.9 for Solus). Hopefully that will fix the problem until it is addressed in 4.16 or 4.17.
No audio over DP for me
For anyone interested, these are the directions I followed.
sudo clr-boot-manager set-timeout 5 && sudo eopkg it linux-lts && sudo clr-boot-manager update
This does not change the default kernel, but you can select the LTS one in GRUB. Not sure how/if this translates to systemd-boot if you’re booting EFI.
@cekim
Just a thought, but if ISPConfig has its own way of doing things wouldn’t it be easier to run it in a sandbox domain with its own data and tmp dirs?
It’s already running in its own VM dedicated to mail and mail only.
1 Like
I’ve got a bit of a silly problem, really small but annoying to figure out if you don’t know how to undo it. 
I recently installed the currently most recent version of Kubuntu and I accidentally put the ‘start menu’ (Simple Menu Launcher?) on fullscreen. This happened when I was configuring a global keyboard shortcut to maximize windows to fullscreen. Maybe the Simple Menu Launcher went to fullscreen because of that? How do I get it back to a small window like on the picture here?
Edit
In the meantime I got a bit more information by running the command sleep 5; xprop and clicking with the mouse on the window of “Application Launcher”. I can’t make much sense of it but here is the output.
_NET_WM_DESKTOP(CARDINAL) = 0
WM_STATE(WM_STATE):
window state: Normal
icon window: 0x0
_KDE_NET_WM_ACTIVITIES(STRING) = “00000000-0000-0000-0000-000000000000”
_NET_WM_ALLOWED_ACTIONS(ATOM) = _NET_WM_ACTION_MOVE, _NET_WM_ACTION_RESIZE, _NET_WM_ACTION_MINIMIZE, _NET_WM_ACTION_MAXIMIZE_VERT, _NET_WM_ACTION_MAXIMIZE_HORZ, _NET_WM_ACTION_FULLSCREEN, _NET_WM_ACTION_CHANGE_DESKTOP, _NET_WM_ACTION_CLOSE
_NET_WM_USER_TIME(CARDINAL) = 8720695
_KDE_NET_WM_SHADOW(CARDINAL) = 37751838, 37751839, 37751840, 37751841, 37751842, 37751843, 37751844, 37751845, 1, 6, 1, 1
_KDE_NET_WM_BACKGROUND_CONTRAST_REGION(_KDE_NET_WM_BACKGROUND_CONTRAST_REGION) = 0x0, 0x0, 0x77e, 0x40c, 0x776, 0x40c, 0x8, 0x8, 0x3dfe2535, 0xbc430fb5, 0xbc430fb5, 0x0, 0xbd240cba, 0x3dc480cf, 0xbd240cba, 0x0, 0xbb847cd3, 0xbb847cd3, 0x3e071faf, 0x0, 0x3e23d70b, 0x3e23d70b, 0x3e23d70b, 0x3f800000
_KDE_NET_WM_BLUR_BEHIND_REGION(CARDINAL) = 0, 0, 1918, 1036, 1910, 1036, 8, 8
_KDE_SLIDE(_KDE_SLIDE) = 0xffffffff, 0x3
_NET_WM_STATE(ATOM) = _NET_WM_STATE_ABOVE, _NET_WM_STATE_STAYS_ON_TOP, _NET_WM_STATE_SKIP_TASKBAR, _NET_WM_STATE_SKIP_PAGER
_KDE_NET_WM_DESKTOP_FILE(UTF8_STRING) = “org.kde.plasmashell”
XdndAware(ATOM) = BITMAP
WM_NAME(STRING) =
_NET_WM_NAME(UTF8_STRING) = “Plasma”
_MOTIF_WM_HINTS(_MOTIF_WM_HINTS) = 0x2, 0x1, 0x0, 0x0, 0x0
_NET_WM_WINDOW_TYPE(ATOM) = _KDE_NET_WM_WINDOW_TYPE_OVERRIDE, _NET_WM_WINDOW_TYPE_NORMAL
_XEMBED_INFO(_XEMBED_INFO) = 0x0, 0x1
WM_CLIENT_LEADER(WINDOW): window id # 0x2400014
WM_HINTS(WM_HINTS):
Client accepts input or input focus: True
Initial state is Normal State.
_NET_WM_PID(CARDINAL) = 1008
_NET_WM_SYNC_REQUEST_COUNTER(CARDINAL) = 37748807
WM_CLASS(STRING) = “plasmashell”, “plasmashell”
WM_PROTOCOLS(ATOM): protocols WM_DELETE_WINDOW, WM_TAKE_FOCUS, _NET_WM_PING, _NET_WM_SYNC_REQUEST
WM_NORMAL_HINTS(WM_SIZE_HINTS):
user specified location: 0, 0
user specified size: 1918 by 1044
program specified minimum size: 480 by 624
program specified maximum size: 1920 by 1080
window gravity: Static
Another edit.
I found a solution. alt + right mouse button and you can grab the window of the Application Launcher. I can now confirm that it was done by maximizing the window, I did it again, this time to try it out. Is that a bug? Something which the developer overlooked? It seems to me like the size of that window should be locked.
I just wanted to update you with short-term results of my KDE testing. I’ve been using it for 2-3 days now. Probably close to 24 hours of uptime and I’ve had no stutters or crashes.
1 Like
well my lead problem is that it lorks up at sddm too. Sooooo
I’m using the 390 branch. If you can get on that branch, it might solve some of your issues.
9800’s don’t have support for anything past 341, and the 341 drivers got dropped almost instantly for problems and its stayed on the 340 series.
Ah. I don’t really know where to direct you then. I haven’t been having any problems since moving to fedora KDE.
2 Likes
Got a strange one for ya all,…
nevermind, a reboot fixed the issue, odd.