Newbie stuck : installed graphics leads to freeze's

Data007 · 2023-01-21 12:47:37

Lone_Wolf wrote:

Neither of those look like crashes, someone OR something instructed the system to reboot .

Now that I don't like to be precise "Someone" it certainly was not me, so it had to come from the interweb.

Lone_Wolf wrote:

The first log has this just before the reboot is forced :

Jan 20 17:20:33 archlinux streamdeck[12558]: ---------------------------------------------------------------------------
Jan 20 17:20:33 archlinux streamdeck[12558]: If you have errors, report it on the discord channel of ArcoLinux
Jan 20 17:20:33 archlinux streamdeck[12558]: Then launch the Arch Linux Tweak Tool again
Jan 20 17:20:33 archlinux streamdeck[12558]: ---------------------------------------------------------------------------
Jan 20 17:20:33 archlinux streamdeck[12558]: Created for :
Jan 20 17:20:33 archlinux streamdeck[12558]:  - ArcoLinux     - https://arcolinux.info/
Jan 20 17:20:33 archlinux streamdeck[12558]:  - Arch Linux    - https://archlinux.org/
Jan 20 17:20:33 archlinux streamdeck[12558]:  - Alci          - https://alci.online/
Jan 20 17:20:33 archlinux streamdeck[12558]:  - Carli         - https://arcolinuxiso.com/
Jan 20 17:20:33 archlinux streamdeck[12558]:  - Ariser        - https://ariser.eu/
Jan 20 17:20:33 archlinux streamdeck[12558]:  - EndeavourOS   - https://endeavouros.com/
Jan 20 17:20:33 archlinux streamdeck[12558]:  - Garuda        - https://garudalinux.org/
Jan 20 17:20:33 archlinux streamdeck[12558]:  - Manjaro       - https://manjaro.org/
Jan 20 17:20:33 archlinux streamdeck[12558]:  - Xerolinux     - https://xerolinux.xyz/
Jan 20 17:20:33 archlinux streamdeck[12558]:  - Axyl          - https://axyl-os.github.io/
Jan 20 17:20:33 archlinux streamdeck[12558]:  - RebornOS      - https://rebornos.org/
Jan 20 17:20:33 archlinux streamdeck[12558]:  - Archcraft     - https://archcraft.io/
Jan 20 17:20:33 archlinux streamdeck[12558]:  - CachyOS       - https://cachyos.org/
Jan 20 17:20:33 archlinux streamdeck[12558]:  - Archman       - https://archman.org/
Jan 20 17:20:33 archlinux streamdeck[12558]: ---------------------------------------------------------------------------
Jan 20 17:20:33 archlinux streamdeck[12558]: Other Arch Linux based distros will be visited later
Jan 20 17:20:33 archlinux streamdeck[12558]: Adding repositories should be done with great care - they can conflict
Jan 20 17:20:33 archlinux streamdeck[12558]: Wayland desktops are not supported e.g. Sway/Hyprland/...
Jan 20 17:20:33 archlinux streamdeck[12558]: ---------------------------------------------------------------------------
Jan 20 17:20:33 archlinux streamdeck[12558]: We make backups of files related to the ATT.
Jan 20 17:20:33 archlinux streamdeck[12558]: You can recognize them by the extension .bak
Jan 20 17:20:33 archlinux streamdeck[12558]: If we have a reset button, the .bak file will be used
Jan 20 17:20:33 archlinux streamdeck[12558]: If you have errors, because of the login managers
Jan 20 17:20:33 archlinux streamdeck[12558]: You can try running one of these scripts:
Jan 20 17:20:33 archlinux streamdeck[12558]: Run fix-sddm-conf
Jan 20 17:20:33 archlinux streamdeck[12558]: Run fix-lightdm-conf
Jan 20 17:20:33 archlinux streamdeck[12558]: Run fix-lxdm-conf
Jan 20 17:20:33 archlinux streamdeck[12558]: You can receive ATT support on https://discord.gg/R2amEEz
Jan 20 17:20:33 archlinux streamdeck[12558]: ---------------------------------------------------------------------------
Jan 20 17:20:33 archlinux streamdeck[12558]: Item has been added to autostart

That tool is NOT designed or maintained by archlinux devs or archlinux users.
It's designed by arcolinux devs and appears to be some kind of gui tool to manage a system.

The screenshot in the arcolinux github repo does show pacman .
pacman devs have NEVER released or designed a gui for pacman.

Please remove it immediately.

It has been removed, also passwords have been reset.

Thanks again for your help, I am still thinking about arch installation and the rest of your post.

Data007 · 2023-01-26 04:27:36

Hi
I have had again some oddness the system has logged me out three times unexpectantly in total.
I have uploaded (the last) to my website logs as I have done before,

https://stevedoeslinux.com/wp-content/uploads/2023/01/newlogout.txt

I don't know how much work is involved in analyzing said logs but can someone have a look at them, please?

Depending on the outcome I may have to concede to demand and reinstall.

--
Data007

Lone_Wolf · 2023-01-26 10:17:31

this time it's clearly related to the videocard.

an 26 03:59:51 archlinux kernel: [drm:amdgpu_job_timedout [amdgpu]] *ERROR* ring gfx_0.0.0 timeout, signaled seq=1958883, emitted seq=1958885
Jan 26 03:59:51 archlinux kernel: [drm:amdgpu_job_timedout [amdgpu]] *ERROR* Process information: process kwin_x11 pid 793 thread kwin_x11:cs0 pid 821
Jan 26 03:59:51 archlinux kernel: amdgpu 0000:08:00.0: amdgpu: GPU reset begin!
Jan 26 03:59:51 archlinux kernel: amdgpu 0000:08:00.0: [drm:amdgpu_ring_test_helper [amdgpu]] *ERROR* ring kiq_2.1.0 test failed (-110)
Jan 26 03:59:51 archlinux kernel: [drm:gfx_v10_0_hw_fini [amdgpu]] *ERROR* KGQ disable failed
Jan 26 03:59:51 archlinux kernel: [drm:gfx_v10_0_hw_fini [amdgpu]] *ERROR* failed to halt cp gfx
Jan 26 03:59:51 archlinux kernel: [drm] free PSP TMR buffer
Jan 26 03:59:51 archlinux kernel: amdgpu 0000:08:00.0: AMD-Vi: Event logged [IO_PAGE_FAULT domain=0x0013 address=0xf7d058fd580 flags=0x0010]
Jan 26 03:59:51 archlinux kernel: amdgpu 0000:08:00.0: AMD-Vi: Event logged [IO_PAGE_FAULT domain=0x0013 address=0xf7d04d0d600 flags=0x0030]
Jan 26 03:59:51 archlinux kernel: amdgpu 0000:08:00.0: AMD-Vi: Event logged [IO_PAGE_FAULT domain=0x0013 address=0xf7d04d19400 flags=0x0030]
Jan 26 03:59:51 archlinux kernel: amdgpu 0000:08:00.0: AMD-Vi: Event logged [IO_PAGE_FAULT domain=0x0013 address=0xf7d04d1a520 flags=0x0030]
Jan 26 03:59:51 archlinux kernel: amdgpu 0000:08:00.0: AMD-Vi: Event logged [IO_PAGE_FAULT domain=0x0013 address=0xf7d04d1b520 flags=0x0030]
Jan 26 03:59:51 archlinux kernel: amdgpu 0000:08:00.0: AMD-Vi: Event logged [IO_PAGE_FAULT domain=0x0013 address=0xf7d04d13700 flags=0x0030]
Jan 26 03:59:51 archlinux kernel: amdgpu 0000:08:00.0: AMD-Vi: Event logged [IO_PAGE_FAULT domain=0x0013 address=0xf7d04d16600 flags=0x0030]
Jan 26 03:59:51 archlinux kernel: amdgpu 0000:08:00.0: AMD-Vi: Event logged [IO_PAGE_FAULT domain=0x0013 address=0xf7d04d14468 flags=0x0030]
Jan 26 03:59:51 archlinux kernel: amdgpu 0000:08:00.0: AMD-Vi: Event logged [IO_PAGE_FAULT domain=0x0013 address=0xf7d04d1b560 flags=0x0030]
Jan 26 03:59:51 archlinux kernel: amdgpu 0000:08:00.0: AMD-Vi: Event logged [IO_PAGE_FAULT domain=0x0013 address=0xf7d04d16640 flags=0x0030]
Jan 26 03:59:51 archlinux kernel: amdgpu 0000:08:00.0: amdgpu: MODE1 reset
Jan 26 03:59:51 archlinux kernel: amdgpu 0000:08:00.0: amdgpu: GPU mode1 reset
Jan 26 03:59:51 archlinux kernel: amdgpu 0000:08:00.0: amdgpu: GPU smu mode1 reset
Jan 26 03:59:52 archlinux kernel: amdgpu 0000:08:00.0: amdgpu: GPU reset succeeded, trying to resume
Jan 26 03:59:52 archlinux kernel: [drm] PCIE GART of 512M enabled (table at 0x0000008000300000).
Jan 26 03:59:52 archlinux kernel: [drm] VRAM is lost due to GPU reset!
Jan 26 03:59:52 archlinux kernel: [drm] PSP is resuming...

It could still be a software issue, but these errors are often related to power or heat problems.

I suggest you open the case , take the videocard out, clean the case if needed.
Then reseat the card and its power connectors (verify ALL power connectors on the card are connected)

Data007 · 2023-01-26 12:19:20

Lone_Wolf wrote:

this time it's clearly related to the videocard.
It could still be a software issue, but these errors are often related to power or heat problems.
I suggest you open the case , take the videocard out, clean the case if needed.
Then reseat the card and its power connectors (verify ALL power connectors on the card are connected)

"It could still be a software issue" How true.

Hok I did as you said and took it apart, it was as clean as a whistle, so I put it back together and ran it up on the bench.
I stuck my finger near the Graphics fans, no air movement, so I stuck my finger in the fan.....(dangers I know) the fans are NOT turning.
The whole thing could be heat........ So I stuck it all back together and browsed the interweb....

Came across a post via google on Redit,

https://www.reddit.com/r/linux4noobs/comments/pafppv/radeon_6700xt_fans_not_spinning_i_found_this_fix/

which lead's to youtube and on to a github repo.......

 https://www.youtube.com/watch?v=YWnwRNtrD0k

https://github.com/marazmista/radeon-profile

Now I tried and follow the readme in github URL above.
I get the following error.

Info: creating stash file /home/steve/source/radeon-profile/radeon-profile/.qmake.stash
Project MESSAGE: Building for release
Project ERROR: Unknown module(s) in QT: charts

Maybe there is a file on aur/pacman that can do the same good.
I am sure you will know @Lone_Wolf Away to have a search.

Last edited by Data007 (2023-01-29 04:12:27)

Data007 · 2023-01-26 12:23:53

HI

pacman -S radeon-profile-git

HIH

Edit:: youtube video goes on to talk about a demon, so it runs at startup and not tiing up cli.
Ive had a quick look and can't locate 'deamon'
End edit::

Last edited by Data007 (2023-01-26 12:42:23)

Data007 · 2023-01-26 17:40:45

Hi Loan_Wolf
Following the instructions found in the video, and with a bit of knowledge I have manged to compile and
install the radeon.profile.service My only gripe is it runs and pops up a window on startup/login must
be a switch to add to the autostart.
Hopefully this is it this time, and in a few days, I will be able to mark this solved.

 https://www.youtube.com/watch?v=YWnwRNtrD0k

The steps I followed can be seen in the video link above timestamp 6.44
copied out the service,
systemctl the service + start,
also created as per the instructions an autostart shortcut.

Added the info in case it helps someone.

--
Data007

Data007 · 2023-01-27 02:56:35

Hi Loan_Wolf

I post the latest logs on my website,

https://stevedoeslinux.com/newlogout-27-1-23

I don't know the cause, nor can I confirm that the fans are turning or not turning, all I can say is the following.
That the new software Radeon-Profile has the system as running at 33c.

A little history I had the logout and then when I went to generate logs, I entered the password wrong at prompt, meaning
another reboot and login Before the log was taken.
For some reason my system has always done this even back in the old distro days, enter the password wrong,
and a logout or reboot is required to clear it.

Anyway thanks again I hope it can be narrowed done this time.

Edit Possibly due to my efforts instability is in the system, Another
logout Logs from the website again for download. I note 35oC temp

[url]https://stevedoeslinux.com/new-logout-27-1-23-450am[/url]

Edit2 12:30 Just tried an experiment (playing NFS Game), I don't think its heat related now.
While playing it the Radeon-Profile software had the temps at 50C and no logouts/crashes.
--
Data007

Last edited by Data007 (2023-01-27 12:29:20)

Data007 · 2023-01-28 17:18:39

Hi Lone_wolf
At present, I have more logs off a logout in when I was using my machine browsing the web....
As usual, I have uploaded them to my website.

https://stevedoeslinux.com/newlogout-28-1-23

Hoping you can help.
--
Data007

Lone_Wolf · 2023-01-31 13:05:39

No clear clues what goes wrong in these 3 logs.

The logs have a low Signal-to-Noise Ratio due to the noise from sources like sddm , audit, gnome-keyring and kscreen messages .

the audit messages are not hard to get rid of .
append audit=0 to the bootcommand line and they'll be gone .

no idea how to reduce the gnome-keyring spam.

kscreen spam could be avoided by using another (simpler) environment.
Do you have any experience with openbox or other window managers ?

By far the simplest way to get rid of the sddm messages is to not use it (or any other display manager) .
Are you familiar enough with cli to boot to a tty and login by typing username & password there ?

Data007 · 2023-02-09 12:52:49

Hi

I so nearly posted solved this morning, been going great then a logout a while ago minutes!!

Logs available from the website as before,

https://stevedoeslinux.com/newlogout-9-2-23

thanks.
--
Data007

Lone_Wolf · 2023-02-11 12:58:37

While the SNR hasn't improved, I am slowly starting to see a pattern.

nordpass generates a coredump that looks like a consequence instead of a cause, Streamdeck also reports errors, but doesn't crash on them.

This appears to be the trigger for the logout

Feb 09 08:22:39 archlinux radeon-profile[1099]: Unable to open  "/sys/class/drm/card0/device/hwmon/hwmon1/pwm1_enable"  to write  "2"
Feb 09 08:22:39 archlinux radeon-profile[1099]: Unable to open  "/sys/class/drm/card0/device/pp_sclk_od"  to write  "0"
Feb 09 08:22:39 archlinux radeon-profile[1099]: Unable to open  "/sys/class/drm/card0/device/pp_mclk_od"  to write  "0"
Feb 09 08:22:39 archlinux kded5[858]: Service  ":1.52" unregistered
Feb 09 08:22:39 archlinux systemd[741]: app-radeon\x2dprofile-e49db929b57a4c3fbbdcf0d0512cf85f.scope: Consumed 1min 45.130s CPU time.
Feb 09 08:22:48 archlinux kded5[858]: Service  ":1.67" unregistered
Feb 09 08:22:48 archlinux kwin_x11[859]: kwin_core: XCB error: 152 (BadDamage), sequence: 24840, resource id: 17254590, major code: 143 (DAMAGE), minor code: 3 (Subtract)
Feb 09 08:22:50 archlinux radeon-profile-daemon[566]: Client disconnected
Feb 09 08:22:50 archlinux radeon-profile-daemon[566]: Awaiting connections...
Feb 09 08:22:50 archlinux kded5[858]: Service  ":1.51" unregistered
Feb 09 08:22:50 archlinux systemd[741]: app-Radeon\x2dprofile@autostart.service: Consumed 1min 47.262s CPU time.
Feb 09 08:22:54 archlinux kded5[858]: Service  ":1.73" unregistered
Feb 09 08:22:56 archlinux kded5[858]: Service  ":1.64" unregistered
Feb 09 08:23:00 archlinux plasmashell[915]: qt.svg: <input>:662:9: Could not resolve property: #radialGradient3118
Feb 09 08:23:00 archlinux plasmashell[915]: qt.svg: <input>:662:9: Could not resolve property: #radialGradient3112
Feb 09 08:23:00 archlinux plasmashell[915]: qt.svg: <input>:662:9: Could not resolve property: #radialGradient3118
Feb 09 08:23:00 archlinux plasmashell[915]: qt.svg: <input>:662:9: Could not resolve property: #radialGradient3112
Feb 09 08:23:00 archlinux plasmashell[915]: qt.svg: <input>:662:9: Could not resolve property: #radialGradient3321
Feb 09 08:23:00 archlinux plasmashell[915]: qt.svg: <input>:662:9: Could not resolve property: #radialGradient3321
Feb 09 08:23:00 archlinux plasmashell[915]: qt.svg: <input>:662:9: Could not resolve property: #radialGradient3327
Feb 09 08:23:00 archlinux plasmashell[915]: qt.svg: <input>:662:9: Could not resolve property: #radialGradient3327
Feb 09 08:23:00 archlinux plasmashell[915]: qt.svg: <input>:662:9: Could not resolve property: #radialGradient3085
Feb 09 08:23:00 archlinux plasmashell[915]: qt.svg: <input>:662:9: Could not resolve property: #radialGradient3101
Feb 09 08:23:00 archlinux plasmashell[915]: qt.svg: <input>:662:9: Could not resolve property: #radialGradient3139
Feb 09 08:23:00 archlinux plasmashell[915]: qt.svg: <input>:662:9: Could not resolve property: #radialGradient3133
Feb 09 08:23:00 archlinux plasmashell[915]: qt.svg: <input>:662:9: Could not resolve property: #radialGradient3499
Feb 09 08:23:00 archlinux plasmashell[915]: qt.svg: <input>:662:9: Could not resolve property: #radialGradient3505
Feb 09 08:23:00 archlinux plasmashell[915]: qt.svg: <input>:662:9: Could not resolve property: #radialGradient3047
Feb 09 08:23:00 archlinux plasmashell[915]: qt.svg: <input>:662:9: Could not resolve property: #radialGradient3041
Feb 09 08:23:00 archlinux plasmashell[915]: qt.svg: <input>:662:9: Could not resolve property: #radialGradient3079
Feb 09 08:23:00 archlinux plasmashell[915]: qt.svg: <input>:662:9: Could not resolve property: #radialGradient3073
Feb 09 08:23:00 archlinux plasmashell[915]: qt.svg: <input>:662:9: Could not resolve property: #radialGradient3499
Feb 09 08:23:00 archlinux plasmashell[915]: qt.svg: <input>:662:9: Could not resolve property: #radialGradient3505
Feb 09 08:23:01 archlinux dbus-daemon[760]: [session uid=1000 pid=760] Activating service name='org.kde.LogoutPrompt' requested by ':1.18' (uid=1000 pid=915 comm="/usr/bin/plasmashell --no-respawn")
Feb 09 08:23:01 archlinux dbus-daemon[760]: [session uid=1000 pid=760] Successfully activated service 'org.kde.LogoutPrompt'

"xcb error 152" occurs multiple times in the log before the forced logout, so it's probably a red herring.
Hardware or low level software errors seems to be the most likely cause .

Gigabyte/AORUS have released a never firmware on januari 13, version F16 . https://www.gigabyte.com/Motherboard/B5 … rt-dl-bios
Please upgrade to that version.

There has been talk about 6.1 becoming the next LTS kernel and that appears to be confirmed, see https://kernel.org/category/releases.html .
I think it's time to test with the stock kernel (6.1.11 atm) again, please upgrade to it.

Data007 · 2023-02-11 14:15:10

Lone_Wolf wrote:

"xcb error 152" occurs multiple times in the log before the forced logout, so it's probably a red herring.
Hardware or low level software errors seems to be the most likely cause .
Gigabyte/AORUS have released a never firmware on januari 13, version F16 . https://www.gigabyte.com/Motherboard/B5 … rt-dl-bios
Please upgrade to that version.
There has been talk about 6.1 becoming the next LTS kernel and that appears to be confirmed, see https://kernel.org/category/releases.html .
I think it's time to test with the stock kernel (6.1.11 atm) again, please upgrade to it.

Hi
I have updated to the 6.1.11 this was a simple process, I updated headers to the same number.
I am unable at present to get a fat32 USB drive to register on the computer, even one that works(formatted in winblows), no not dualing.
so uping the firmware will have to await, at least til I figure out WHY they are not registering.

Ho Hum
--
Data007

Data007 · 2023-02-14 02:41:52

Data007 wrote:

Lone_Wolf wrote:
"xcb error 152" occurs multiple times in the log before the forced logout, so it's probably a red herring.
Hardware or low level software errors seems to be the most likely cause .
Gigabyte/AORUS have released a never firmware on januari 13, version F16 . https://www.gigabyte.com/Motherboard/B5 … rt-dl-bios
Please upgrade to that version.
There has been talk about 6.1 becoming the next LTS kernel and that appears to be confirmed, see https://kernel.org/category/releases.html .
I think it's time to test with the stock kernel (6.1.11 atm) again, please upgrade to it.
Hi
I have updated to the 6.1.11 this was a simple process, I updated headers to the same number.
I am unable at present to get a fat32 USB drive to register on the computer, even one that works(formatted in winblows), no not dualing.
so uping the firmware will have to await, at least til I figure out WHY they are not registering.
Ho Hum
--
Data007

Hi
Well, I got the firmware done only yesterday and today another logout.
I was converting mp4 to mp3 with a newly installed program and midway through it quit to login.

New Log's available on the website,

https://stevedoeslinux.com/wp-content/uploads/2023/02/logout.txt

Thanks for looking.

EDIT*********
New logot 04-15ish
maybe the new audio converter

https://stevedoeslinux.com/newlogout-04-15ish

--
Data007

Last edited by Data007 (2023-02-14 04:25:12)

Lone_Wolf · 2023-02-14 11:06:41

https://stevedoeslinux.com/wp-content/u … logout.txt and https://stevedoeslinux.com/newlogout-04-15ish appear to be the same log .

Feb 13 16:51:30 archlinux streamdeck[1634]: [2023-02-13T16:51:30Z ERROR viaduct::backend::ffi] Missing HTTP status
Feb 13 16:51:30 archlinux streamdeck[1634]: [2023-02-13T16:51:30Z ERROR viaduct::backend::ffi] Missing HTTP status
Feb 13 16:51:34 archlinux plasmashell[923]: qt.svg: <input>:662:9: Could not resolve property: #radialGradient3118
Feb 13 16:51:34 archlinux plasmashell[923]: qt.svg: <input>:662:9: Could not resolve property: #radialGradient3112
Feb 13 16:51:34 archlinux plasmashell[923]: qt.svg: <input>:662:9: Could not resolve property: #radialGradient3118
Feb 13 16:51:34 archlinux plasmashell[923]: qt.svg: <input>:662:9: Could not resolve property: #radialGradient3112
Feb 13 16:51:34 archlinux plasmashell[923]: qt.svg: <input>:662:9: Could not resolve property: #radialGradient3321
Feb 13 16:51:34 archlinux plasmashell[923]: qt.svg: <input>:662:9: Could not resolve property: #radialGradient3321
Feb 13 16:51:34 archlinux plasmashell[923]: qt.svg: <input>:662:9: Could not resolve property: #radialGradient3327
Feb 13 16:51:34 archlinux plasmashell[923]: qt.svg: <input>:662:9: Could not resolve property: #radialGradient3327
Feb 13 16:51:34 archlinux plasmashell[923]: qt.svg: <input>:662:9: Could not resolve property: #radialGradient3085
Feb 13 16:51:34 archlinux plasmashell[923]: qt.svg: <input>:662:9: Could not resolve property: #radialGradient3101
Feb 13 16:51:34 archlinux plasmashell[923]: qt.svg: <input>:662:9: Could not resolve property: #radialGradient3139
Feb 13 16:51:34 archlinux plasmashell[923]: qt.svg: <input>:662:9: Could not resolve property: #radialGradient3133
Feb 13 16:51:34 archlinux plasmashell[923]: qt.svg: <input>:662:9: Could not resolve property: #radialGradient3499
Feb 13 16:51:34 archlinux plasmashell[923]: qt.svg: <input>:662:9: Could not resolve property: #radialGradient3505
Feb 13 16:51:34 archlinux plasmashell[923]: qt.svg: <input>:662:9: Could not resolve property: #radialGradient3047
Feb 13 16:51:34 archlinux plasmashell[923]: qt.svg: <input>:662:9: Could not resolve property: #radialGradient3041
Feb 13 16:51:34 archlinux plasmashell[923]: qt.svg: <input>:662:9: Could not resolve property: #radialGradient3079
Feb 13 16:51:34 archlinux plasmashell[923]: qt.svg: <input>:662:9: Could not resolve property: #radialGradient3073
Feb 13 16:51:34 archlinux plasmashell[923]: qt.svg: <input>:662:9: Could not resolve property: #radialGradient3499
Feb 13 16:51:34 archlinux plasmashell[923]: qt.svg: <input>:662:9: Could not resolve property: #radialGradient3505
Feb 13 16:51:37 archlinux plasmashell[923]: "Could not convert argument 2 at"
Feb 13 16:51:37 archlinux plasmashell[923]:          "onPositionChanged@file:///usr/share/plasma/plasmoids/org.kde.plasma.kicker/contents/ui/SideBarItem.qml:114"
Feb 13 16:51:37 archlinux plasmashell[923]: "Passing incompatible arguments to C++ functions from JavaScript is dangerous and deprecated."
Feb 13 16:51:37 archlinux plasmashell[923]: "This will throw a JavaScript TypeError in future releases of Qt!"
Feb 13 16:51:37 archlinux plasmashell[923]: Arrived mimeData () () at 1203 ,  906
Feb 13 16:51:42 archlinux kded5[863]: Service  ":1.75" unregistered
Feb 13 16:51:47 archlinux dbus-daemon[765]: [session uid=1000 pid=765] Activating service name='org.kde.LogoutPrompt' requested by ':1.18' (uid=1000 pid=923 comm="/usr/bin/plasmashell --no-respawn")
Feb 13 16:51:47 archlinux dbus-daemon[765]: [session uid=1000 pid=765] Successfully activated service 'org.kde.LogoutPrompt'

It doesn't look like the videocard is related to this crash.

Maybe streamdeck upstream can help fo figure out whether Feb 13 16:51:30 archlinux streamdeck[1634]: [2023-02-13T16:51:30Z ERROR viaduct::backend::ffi] Missing HTTP could lead to a crash ?

Data007 · 2023-02-14 12:55:25

Lone_Wolf wrote:

https://stevedoeslinux.com/wp-content/u … logout.txt and https://stevedoeslinux.com/newlogout-04-15ish appear to be the same log .
It doesn't look like the videocard is related to this crash.
Maybe streamdeck upstream can help fo figure out whether Feb 13 16:51:30 archlinux streamdeck[1634]: [2023-02-13T16:51:30Z ERROR viaduct::backend::ffi] Missing HTTP could lead to a crash ?

Hi
Sorry about the logs appearing as if they are the same one, they are definitely different file here on HD, again Sorry.

The new to me program converting video to audio was pushing the graphics card I could hear it spooling up(fans) and then the logout.
Both the logouts happened in relation to converchion runs. For the third lot I set a limit on the number of files that could be done in one
go. The streamdeck GitHub is not very active, at least the last time I looked.

Thanks again.
--
Data007

Lone_Wolf · 2023-02-15 11:22:09

The files are not identical, but both start at the same timestamp : Feb 13 13:15:38 .

Please switch to multi-user.target booting and use startx / .xinitrc to get into the graphical environment.
This will help to determine whether a crash or a logout happened and reduce the noise in the logs by a lot .

https://wiki.archlinux.org/title/System … _boot_into
https://wiki.archlinux.org/title/Xinit#xinitrc

Data007 · 2023-02-15 16:23:48

Lone_Wolf wrote:

The files are not identical, but both start at the same timestamp : Feb 13 13:15:38 .
Please switch to multi-user.target booting and use startx / .xinitrc to get into the graphical environment.
This will help to determine whether a crash or a logout happened and reduce the noise in the logs by a lot .
https://wiki.archlinux.org/title/System … _boot_into
https://wiki.archlinux.org/title/Xinit#xinitrc

Hi
The time-stamp of the file should be more like 03:15:38 as in very early in the morning/I rise very early some days.

This multi-user.target booting : I am the only one using the machine, if you see otherwise it should not be.

Startx now that's a command I have not heard of for a while, old school. Iam as at home on the command line -/- cli
as I am in a graphical environment.

I emphasise al lot and don't like the idea of :query: Noise in the logs. As previously stated I live alone, although on
a very small lan 5 comp's some windblows only one machine usually is on at a time. With me being in control of it all.

I am slightly confused, probably as you can see, I recognize startx much like a when we used to boot msdos and run
win in the cli to spoolup windblows.

I will be away over the weekend on a small jaunt to the mainland.
--
Data007

Data007 · 2023-02-17 05:46:22

Hi Sorry not managed to do what you ask yet.

This Crashlog is different >I was still able to attempt a logout, ctrl-alt-del I was mid-way through it and lost the option
to do so in the on-screen jumble

Logs can be found on the website as usual.

https://stevedoeslinux.com/graphicscrash-17-2-23

I hope for not too much noise.

--
Data007

Lone_Wolf · 2023-02-17 14:03:12

Feb 17 05:20:43 archlinux kernel: amdgpu 0000:08:00.0: amdgpu: [gfxhub] page fault (src_id:0 ring:24 vmid:7 pasid:32774, for process kwin_x11 pid 874 thread kwin_x11:cs0 pid 901)
Feb 17 05:20:43 archlinux kernel: amdgpu 0000:08:00.0: amdgpu:   in page starting at address 0x00008009431a4000 from client 0x1b (UTCL2)
Feb 17 05:20:43 archlinux kernel: amdgpu 0000:08:00.0: amdgpu: GCVM_L2_PROTECTION_FAULT_STATUS:0x00701031
Feb 17 05:20:43 archlinux kernel: amdgpu 0000:08:00.0: amdgpu:          Faulty UTCL2 client ID: TCP (0x8)
Feb 17 05:20:43 archlinux kernel: amdgpu 0000:08:00.0: amdgpu:          MORE_FAULTS: 0x1
Feb 17 05:20:43 archlinux kernel: amdgpu 0000:08:00.0: amdgpu:          WALKER_ERROR: 0x0
Feb 17 05:20:43 archlinux kernel: amdgpu 0000:08:00.0: amdgpu:          PERMISSION_FAULTS: 0x3
Feb 17 05:20:43 archlinux kernel: amdgpu 0000:08:00.0: amdgpu:          MAPPING_ERROR: 0x0
Feb 17 05:20:43 archlinux kernel: amdgpu 0000:08:00.0: amdgpu:          RW: 0x0
Feb 17 05:20:43 archlinux kernel: amdgpu 0000:08:00.0: amdgpu: [gfxhub] page fault (src_id:0 ring:24 vmid:7 pasid:32774, for process kwin_x11 pid 874 thread kwin_x11:cs0 pid 901)
Feb 17 05:20:43 archlinux kernel: amdgpu 0000:08:00.0: amdgpu:   in page starting at address 0x00008009431a5000 from client 0x1b (UTCL2)
Feb 17 05:20:43 archlinux kernel: amdgpu 0000:08:00.0: amdgpu: GCVM_L2_PROTECTION_FAULT_STATUS:0x00000000
Feb 17 05:20:43 archlinux kernel: amdgpu 0000:08:00.0: amdgpu:          Faulty UTCL2 client ID: CB/DB (0x0)
Feb 17 05:20:43 archlinux kernel: amdgpu 0000:08:00.0: amdgpu:          MORE_FAULTS: 0x0
Feb 17 05:20:43 archlinux kernel: amdgpu 0000:08:00.0: amdgpu:          WALKER_ERROR: 0x0
Feb 17 05:20:43 archlinux kernel: amdgpu 0000:08:00.0: amdgpu:          PERMISSION_FAULTS: 0x0
Feb 17 05:20:43 archlinux kernel: amdgpu 0000:08:00.0: amdgpu:          MAPPING_ERROR: 0x0
Feb 17 05:20:43 archlinux kernel: amdgpu 0000:08:00.0: amdgpu:          RW: 0x0
Feb 17 05:20:43 archlinux kernel: amdgpu 0000:08:00.0: amdgpu: [gfxhub] page fault (src_id:0 ring:24 vmid:7 pasid:32774, for process kwin_x11 pid 874 thread kwin_x11:cs0 pid 901)
Feb 17 05:20:43 archlinux kernel: amdgpu 0000:08:00.0: amdgpu:   in page starting at address 0x00008009431a6000 from client 0x1b (UTCL2)
Feb 17 05:20:43 archlinux kernel: amdgpu 0000:08:00.0: amdgpu: GCVM_L2_PROTECTION_FAULT_STATUS:0x00000000
Feb 17 05:20:43 archlinux kernel: amdgpu 0000:08:00.0: amdgpu:          Faulty UTCL2 client ID: CB/DB (0x0)
Feb 17 05:20:43 archlinux kernel: amdgpu 0000:08:00.0: amdgpu:          MORE_FAULTS: 0x0
Feb 17 05:20:43 archlinux kernel: amdgpu 0000:08:00.0: amdgpu:          WALKER_ERROR: 0x0
Feb 17 05:20:43 archlinux kernel: amdgpu 0000:08:00.0: amdgpu:          PERMISSION_FAULTS: 0x0
Feb 17 05:20:43 archlinux kernel: amdgpu 0000:08:00.0: amdgpu:          MAPPING_ERROR: 0x0
Feb 17 05:20:43 archlinux kernel: amdgpu 0000:08:00.0: amdgpu:          RW: 0x0
Feb 17 05:20:43 archlinux kernel: amdgpu 0000:08:00.0: amdgpu: [gfxhub] page fault (src_id:0 ring:24 vmid:7 pasid:32774, for process kwin_x11 pid 874 thread kwin_x11:cs0 pid 901)
Feb 17 05:20:43 archlinux kernel: amdgpu 0000:08:00.0: amdgpu:   in page starting at address 0x00008009431a7000 from client 0x1b (UTCL2)
Feb 17 05:20:43 archlinux kernel: amdgpu 0000:08:00.0: amdgpu: GCVM_L2_PROTECTION_FAULT_STATUS:0x00000000
Feb 17 05:20:43 archlinux kernel: amdgpu 0000:08:00.0: amdgpu:          Faulty UTCL2 client ID: CB/DB (0x0)
Feb 17 05:20:43 archlinux kernel: amdgpu 0000:08:00.0: amdgpu:          MORE_FAULTS: 0x0
Feb 17 05:20:43 archlinux kernel: amdgpu 0000:08:00.0: amdgpu:          WALKER_ERROR: 0x0
Feb 17 05:20:43 archlinux kernel: amdgpu 0000:08:00.0: amdgpu:          PERMISSION_FAULTS: 0x0
Feb 17 05:20:43 archlinux kernel: amdgpu 0000:08:00.0: amdgpu:          MAPPING_ERROR: 0x0
Feb 17 05:20:43 archlinux kernel: amdgpu 0000:08:00.0: amdgpu:          RW: 0x0
Feb 17 05:20:43 archlinux kernel: amdgpu 0000:08:00.0: amdgpu: [gfxhub] page fault (src_id:0 ring:24 vmid:7 pasid:32774, for process kwin_x11 pid 874 thread kwin_x11:cs0 pid 901)
Feb 17 05:20:43 archlinux kernel: amdgpu 0000:08:00.0: amdgpu:   in page starting at address 0x00008009431a1000 from client 0x1b (UTCL2)
Feb 17 05:20:43 archlinux kernel: amdgpu 0000:08:00.0: amdgpu: GCVM_L2_PROTECTION_FAULT_STATUS:0x00000000
Feb 17 05:20:43 archlinux kernel: amdgpu 0000:08:00.0: amdgpu:          Faulty UTCL2 client ID: CB/DB (0x0)
Feb 17 05:20:43 archlinux kernel: amdgpu 0000:08:00.0: amdgpu:          MORE_FAULTS: 0x0
Feb 17 05:20:43 archlinux kernel: amdgpu 0000:08:00.0: amdgpu:          WALKER_ERROR: 0x0
Feb 17 05:20:43 archlinux kernel: amdgpu 0000:08:00.0: amdgpu:          PERMISSION_FAULTS: 0x0
Feb 17 05:20:43 archlinux kernel: amdgpu 0000:08:00.0: amdgpu:          MAPPING_ERROR: 0x0
Feb 17 05:20:43 archlinux kernel: amdgpu 0000:08:00.0: amdgpu:          RW: 0x0
Feb 17 05:20:43 archlinux kernel: amdgpu 0000:08:00.0: amdgpu: [gfxhub] page fault (src_id:0 ring:24 vmid:7 pasid:32774, for process kwin_x11 pid 874 thread kwin_x11:cs0 pid 901)
Feb 17 05:20:43 archlinux kernel: amdgpu 0000:08:00.0: amdgpu:   in page starting at address 0x00008009431a3000 from client 0x1b (UTCL2)
Feb 17 05:20:43 archlinux kernel: amdgpu 0000:08:00.0: amdgpu: GCVM_L2_PROTECTION_FAULT_STATUS:0x00000000
Feb 17 05:20:43 archlinux kernel: amdgpu 0000:08:00.0: amdgpu:          Faulty UTCL2 client ID: CB/DB (0x0)
Feb 17 05:20:43 archlinux kernel: amdgpu 0000:08:00.0: amdgpu:          MORE_FAULTS: 0x0
Feb 17 05:20:43 archlinux kernel: amdgpu 0000:08:00.0: amdgpu:          WALKER_ERROR: 0x0
Feb 17 05:20:43 archlinux kernel: amdgpu 0000:08:00.0: amdgpu:          PERMISSION_FAULTS: 0x0
Feb 17 05:20:43 archlinux kernel: amdgpu 0000:08:00.0: amdgpu:          MAPPING_ERROR: 0x0
Feb 17 05:20:43 archlinux kernel: amdgpu 0000:08:00.0: amdgpu:          RW: 0x0
Feb 17 05:20:43 archlinux kernel: amdgpu 0000:08:00.0: amdgpu: [gfxhub] page fault (src_id:0 ring:24 vmid:7 pasid:32774, for process kwin_x11 pid 874 thread kwin_x11:cs0 pid 901)
Feb 17 05:20:43 archlinux kernel: amdgpu 0000:08:00.0: amdgpu:   in page starting at address 0x00008009431a6000 from client 0x1b (UTCL2)
Feb 17 05:20:43 archlinux kernel: amdgpu 0000:08:00.0: amdgpu: GCVM_L2_PROTECTION_FAULT_STATUS:0x00000000
Feb 17 05:20:43 archlinux kernel: amdgpu 0000:08:00.0: amdgpu:          Faulty UTCL2 client ID: CB/DB (0x0)
Feb 17 05:20:43 archlinux kernel: amdgpu 0000:08:00.0: amdgpu:          MORE_FAULTS: 0x0
Feb 17 05:20:43 archlinux kernel: amdgpu 0000:08:00.0: amdgpu:          WALKER_ERROR: 0x0
Feb 17 05:20:43 archlinux kernel: amdgpu 0000:08:00.0: amdgpu:          PERMISSION_FAULTS: 0x0
Feb 17 05:20:43 archlinux kernel: amdgpu 0000:08:00.0: amdgpu:          MAPPING_ERROR: 0x0
Feb 17 05:20:43 archlinux kernel: amdgpu 0000:08:00.0: amdgpu:          RW: 0x0
Feb 17 05:20:43 archlinux kernel: amdgpu 0000:08:00.0: amdgpu: [gfxhub] page fault (src_id:0 ring:24 vmid:7 pasid:32774, for process kwin_x11 pid 874 thread kwin_x11:cs0 pid 901)
Feb 17 05:20:43 archlinux kernel: amdgpu 0000:08:00.0: amdgpu:   in page starting at address 0x00008009431a5000 from client 0x1b (UTCL2)
Feb 17 05:20:43 archlinux kernel: amdgpu 0000:08:00.0: amdgpu: GCVM_L2_PROTECTION_FAULT_STATUS:0x00000000
Feb 17 05:20:43 archlinux kernel: amdgpu 0000:08:00.0: amdgpu:          Faulty UTCL2 client ID: CB/DB (0x0)
Feb 17 05:20:43 archlinux kernel: amdgpu 0000:08:00.0: amdgpu:          MORE_FAULTS: 0x0
Feb 17 05:20:43 archlinux kernel: amdgpu 0000:08:00.0: amdgpu:          WALKER_ERROR: 0x0
Feb 17 05:20:43 archlinux kernel: amdgpu 0000:08:00.0: amdgpu:          PERMISSION_FAULTS: 0x0
Feb 17 05:20:43 archlinux kernel: amdgpu 0000:08:00.0: amdgpu:          MAPPING_ERROR: 0x0
Feb 17 05:20:43 archlinux kernel: amdgpu 0000:08:00.0: amdgpu:          RW: 0x0
Feb 17 05:20:43 archlinux kernel: amdgpu 0000:08:00.0: amdgpu: [gfxhub] page fault (src_id:0 ring:24 vmid:7 pasid:32774, for process kwin_x11 pid 874 thread kwin_x11:cs0 pid 901)
Feb 17 05:20:43 archlinux kernel: amdgpu 0000:08:00.0: amdgpu:   in page starting at address 0x00008009431a4000 from client 0x1b (UTCL2)
Feb 17 05:20:43 archlinux kernel: amdgpu 0000:08:00.0: amdgpu: GCVM_L2_PROTECTION_FAULT_STATUS:0x00000000
Feb 17 05:20:43 archlinux kernel: amdgpu 0000:08:00.0: amdgpu:          Faulty UTCL2 client ID: CB/DB (0x0)
Feb 17 05:20:43 archlinux kernel: amdgpu 0000:08:00.0: amdgpu:          MORE_FAULTS: 0x0
Feb 17 05:20:43 archlinux kernel: amdgpu 0000:08:00.0: amdgpu:          WALKER_ERROR: 0x0
Feb 17 05:20:43 archlinux kernel: amdgpu 0000:08:00.0: amdgpu:          PERMISSION_FAULTS: 0x0
Feb 17 05:20:43 archlinux kernel: amdgpu 0000:08:00.0: amdgpu:          MAPPING_ERROR: 0x0
Feb 17 05:20:43 archlinux kernel: amdgpu 0000:08:00.0: amdgpu:          RW: 0x0
Feb 17 05:20:43 archlinux kernel: amdgpu 0000:08:00.0: amdgpu: [gfxhub] page fault (src_id:0 ring:24 vmid:7 pasid:32774, for process kwin_x11 pid 874 thread kwin_x11:cs0 pid 901)
Feb 17 05:20:43 archlinux kernel: amdgpu 0000:08:00.0: amdgpu:   in page starting at address 0x00008009431a7000 from client 0x1b (UTCL2)
Feb 17 05:20:43 archlinux kernel: amdgpu 0000:08:00.0: amdgpu: GCVM_L2_PROTECTION_FAULT_STATUS:0x00000000
Feb 17 05:20:43 archlinux kernel: amdgpu 0000:08:00.0: amdgpu:          Faulty UTCL2 client ID: CB/DB (0x0)
Feb 17 05:20:43 archlinux kernel: amdgpu 0000:08:00.0: amdgpu:          MORE_FAULTS: 0x0
Feb 17 05:20:43 archlinux kernel: amdgpu 0000:08:00.0: amdgpu:          WALKER_ERROR: 0x0
Feb 17 05:20:43 archlinux kernel: amdgpu 0000:08:00.0: amdgpu:          PERMISSION_FAULTS: 0x0
Feb 17 05:20:43 archlinux kernel: amdgpu 0000:08:00.0: amdgpu:          MAPPING_ERROR: 0x0
Feb 17 05:20:43 archlinux kernel: amdgpu 0000:08:00.0: amdgpu:          RW: 0x0
Feb 17 05:20:53 archlinux kernel: [drm:amdgpu_job_timedout [amdgpu]] *ERROR* ring gfx_0.0.0 timeout, but soft recovered
Feb 17 05:20:53 archlinux kwin_x11[874]: kwin_scene_opengl: A graphics reset not attributable to the current GL context occurred.
Feb 17 05:20:53 archlinux plasmashell[926]: Could not find the Plasmoid for Plasma::FrameSvgItem(0x55cc3851a210) QQmlContext(0x55cc37b61fc0) QUrl("file:///usr/share/plasma/plasmoids/org.kde.plasma.notifications/contents/ui/global/Globals.qml")
Feb 17 05:20:53 archlinux plasmashell[926]: Could not find the Plasmoid for Plasma::FrameSvgItem(0x55cc3851a210) QQmlContext(0x55cc37b61fc0) QUrl("file:///usr/share/plasma/plasmoids/org.kde.plasma.notifications/contents/ui/global/Globals.qml")
Feb 17 05:20:54 archlinux nordpass[1432]: [1432:0217/052054.156488:ERROR:shared_context_state.cc(846)] SharedContextState context lost via ARB/EXT_robustness. Reset status = GL_INNOCENT_CONTEXT_RESET_KHR
Feb 17 05:20:54 archlinux nordpass[1432]: [1432:0217/052054.156592:ERROR:gpu_service_impl.cc(990)] Exiting GPU process because some drivers can't recover from errors. GPU process will restart shortly.
Feb 17 05:20:54 archlinux nordpass[1095]: [1095:0217/052054.160924:ERROR:gpu_process_host.cc(974)] GPU process exited unexpectedly: exit_code=8704

I do not know what an UTCL2 client is or does , but it could have to do with timestamps and databases .

Overall this looks like something goes wrong with the gpu, nordpass notices it and chokes on it.
Several earlier crashlogs gave me the same impression, but they were not clear enough to be sure.
Can you configure nordpass to NOT use the gpu ?

Last edited by Lone_Wolf (2023-02-17 14:04:50)

Data007 · 2023-02-17 14:43:46

Lone_Wolf wrote:

I do not know what an UTCL2 client is or does , but it could have to do with timestamps and databases .
Overall this looks like something goes wrong with the gpu, nordpass notices it and chokes on it.
Several earlier crashlogs gave me the same impression, but they were not clear enough to be sure.
Can you configure nordpass to NOT use the gpu ?

Hi
Just about to go out the door on my jaunt Long weekend away from home.

UTCL2 I stuck that in google and it s top two are posts about amdgpu.....
Nordpass not sure about setting it to not use the GPU..

Will be back Monday morning UK time 08.00 will investigate then.

Thanks for looking, will check forum from winblows laptop while I am away.

--
Data007

seth · 2023-02-17 15:34:21

Sanity check: AMD recommends a 650+W PSU for the GPU, does your setup provide that?
Can you boot w/ "amdgpu.dpm=0"?
The amdgpu pagefaults are all for kwin_x11, do you hit this when disabling the compositor (SHIFT+alt+F12)?
Do you hit this when disabling the compositor and launch some GPU-intens-ish other process (you may try w/ picom, the default backend is xrender, though.
Alternatively try eg. https://archlinux.org/packages/communit … 4/xonotic/

Data007 · 2023-02-17 16:22:43

seth wrote:

Sanity check: AMD recommends a 650+W PSU for the GPU, does your setup provide that?
Can you boot w/ "amdgpu.dpm=0"?
The amdgpu pagefaults are all for kwin_x11, do you hit this when disabling the compositor (SHIFT+alt+F12)?
Do you hit this when disabling the compositor and launch some GPU-intens-ish other process (you may try w/ picom, the default backend is xrender, though.
Alternatively try eg. https://archlinux.org/packages/communit … 4/xonotic/

Hi Seth
Err am away from home now till Monday morning.
I Belive if memory servers on 750 but can not honestly say with out striping the pc when I rerturn, I may just order/buy a bigger psu whill
I am away. I Money holds. I guess `the minumum is 650W but no harm in deliverying more W.

The rest off your reply will have to wait till I return home.

Thanks Seth.
--
Data007

Data007 · 2023-02-20 15:26:55

Hi Loan Wolf, Seth
I returned home this morning on an overnight ferry, I have not had time yet today to do anything.
I will tare down the machine possibly later today or tomorrow.

Situation:
The machine sitting idle it locked because of power saving(No input from me ...), on entering the password to log in it froze and logged me out.
Crash log at my website,

https://stevedoeslinux.com/wp-content/uploads/2023/02/Logout-while-idele-login.txt

Will it ever end, Iam going to have something to eat maybe after that I look at what wattage PSU is Seth.

--
Data-007

seth · 2023-02-20 16:08:09

Feb 20 13:33:23 archlinux kscreen_backend_launcher[1067]: kscreen.xcb.helper: RRNotify_OutputProperty (ignored)
…
Feb 20 13:33:24 archlinux plasmashell[935]: 25 -- exe=/usr/bin/plasmashell
Feb 20 13:33:24 archlinux plasmashell[935]: 13 -- platform=xcb
Feb 20 13:33:24 archlinux plasmashell[935]: 11 -- display=:0
Feb 20 13:33:24 archlinux plasmashell[935]: 20 -- appname=plasmashell
Feb 20 13:33:24 archlinux plasmashell[935]: 17 -- apppath=/usr/bin
Feb 20 13:33:24 archlinux plasmashell[935]: 10 -- signal=11
Feb 20 13:33:24 archlinux plasmashell[935]: 8 -- pid=935
Feb 20 13:33:24 archlinux plasmashell[935]: 18 -- appversion=5.27.0
Feb 20 13:33:24 archlinux plasmashell[935]: 19 -- programname=Plasma
Feb 20 13:33:24 archlinux plasmashell[935]: 31 -- bugaddress=submit@bugs.kde.org
…
Feb 20 13:33:28 archlinux systemd-coredump[7063]: Process 935 (plasmashell) of user 1000 dumped core.
…
Feb 20 13:38:59 archlinux kscreen_backend_launcher[1067]: kscreen.xcb.helper: RRNotify_OutputProperty (ignored)
…
Feb 20 13:39:02 archlinux systemd-coredump[7238]: Process 7078 (plasmashell) of user 1000 dumped core.

"kcmshell5 kded", disable kscreen

The idleness will trigger DPMS, that likely makes one output unregister and when you wake up, kscreen becomes hyperactive and the next thing is that plasmashell crashes.

Data007 · 2023-02-20 16:41:40

seth wrote:

"kcmshell5 kded", disable kscreen
The idleness will trigger DPMS, that likely makes one output unregister and when you wake up, kscreen becomes hyperactive and the next thing is that plasmashell crashes.

Hi Seth thanks for the swift reply, I will away and research how to disable kscreen.

In the meantime I have been tearing down the machine/computer, I am happy to report it has

Corsair RM750W PSU

--
Data-007

Arch Linux

#51 2023-01-21 12:47:37

Re: Newbie stuck : installed graphics leads to freeze's

#52 2023-01-26 04:27:36

Re: Newbie stuck : installed graphics leads to freeze's

#53 2023-01-26 10:17:31

Re: Newbie stuck : installed graphics leads to freeze's

#54 2023-01-26 12:19:20

Re: Newbie stuck : installed graphics leads to freeze's

#55 2023-01-26 12:23:53

Re: Newbie stuck : installed graphics leads to freeze's

#56 2023-01-26 17:40:45

Re: Newbie stuck : installed graphics leads to freeze's

#57 2023-01-27 02:56:35

Re: Newbie stuck : installed graphics leads to freeze's

#58 2023-01-28 17:18:39

Re: Newbie stuck : installed graphics leads to freeze's

#59 2023-01-31 13:05:39

Re: Newbie stuck : installed graphics leads to freeze's

#60 2023-02-09 12:52:49

Re: Newbie stuck : installed graphics leads to freeze's

#61 2023-02-11 12:58:37

Re: Newbie stuck : installed graphics leads to freeze's

#62 2023-02-11 14:15:10

Re: Newbie stuck : installed graphics leads to freeze's

#63 2023-02-14 02:41:52

Re: Newbie stuck : installed graphics leads to freeze's

#64 2023-02-14 11:06:41

Re: Newbie stuck : installed graphics leads to freeze's

#65 2023-02-14 12:55:25

Re: Newbie stuck : installed graphics leads to freeze's

#66 2023-02-15 11:22:09

Re: Newbie stuck : installed graphics leads to freeze's

#67 2023-02-15 16:23:48

Re: Newbie stuck : installed graphics leads to freeze's

#68 2023-02-17 05:46:22

Re: Newbie stuck : installed graphics leads to freeze's

#69 2023-02-17 14:03:12

Re: Newbie stuck : installed graphics leads to freeze's

#70 2023-02-17 14:43:46

Re: Newbie stuck : installed graphics leads to freeze's

#71 2023-02-17 15:34:21

Re: Newbie stuck : installed graphics leads to freeze's

#72 2023-02-17 16:22:43

Re: Newbie stuck : installed graphics leads to freeze's

#73 2023-02-20 15:26:55

Re: Newbie stuck : installed graphics leads to freeze's

#74 2023-02-20 16:08:09

Re: Newbie stuck : installed graphics leads to freeze's

#75 2023-02-20 16:41:40

Re: Newbie stuck : installed graphics leads to freeze's

Board footer