Announcement

Collapse
No announcement yet.

Plasma Crashes

Collapse
X
 
  • Filter
  • Time
  • Show
Clear All
new posts

    #16
    Thank you for your response, claydoh. I finally got the time to dive back into this.

    Yesterday I changed from Desktop to Folder view. Yesterday I removed all widgets/icons from ~/Desktop and repopulated the applications (widgets/icons) onto the Desktop within the Folder view, so all widgets/icons are "new". I exercised all applications on the Desktop with no issues.

    Today the plasma desktop experienced a crash while I was using Chromium in Incognito mode while viewing a video on a news site. The video did not crash. Chromium did not crash. Only the plasma desktop crashed.

    I think I will stop using Chromium for a while and instead use Chrome. If the issue still occurs, I will move away from Chrome and try Firefox or Opera. Then if the issue still occurs, I might consider yet another fresh install.

    Comment


      #17
      Same thing here. System runs for a bit, then plasmadesktop freezes. I have to ctl-alt-del to get a reboot screen. I have currently changed to oxygen from sweet global theme AND I made sure I was logging into plasma-Wayland over x11. Good news is that my clock widget also freezes at the same time. Bad news is that the system keeps freezing during journalctl in yakuake.

      I thought it was an Nvidia thing because it cleared up after I threw ubuntu-drivers at it. I also don't think it's a browser issue because I use Firefox and the same thing happens.

      --break--

      ok, my system ran alright until I changed my icons to something other than Breeze. I've changed back to Breeze-Dark as my global theme. Everything is set back to Breeze(-Dark). I will monitor.

      My system is currently in the process of freezing. Firefox hasn't frozen yet. I guess we can discount a theme issue. this is journalctl -r. My clock is frozen at 10:24:50

      Code:
      Sep 14 10:24:52 Pats-Main wpa_supplicant[1028]: wlp5s0: CTRL-EVENT-SIGNAL-CHANGE above=1 signal=-28 noise=9999 txrate=0
      Sep 14 10:24:50 Pats-Main plasmashell[1701]: kf.plasma.quick: location should be set before showing popup window
      Sep 14 10:24:50 Pats-Main plasmashell[1701]: kf.plasma.quick: location should be set before showing popup window
      Sep 14 10:24:49 Pats-Main plasmashell[1701]: kf.plasma.quick: location should be set before showing popup window
      Sep 14 10:24:49 Pats-Main plasmashell[1701]: kpipewire_logging: PipeWire remote error: -2 unknown resource 5 op:7
      Sep 14 10:24:49 Pats-Main plasmashell[1701]: kpipewire_logging: PipeWire remote error: -2 unknown resource 4 op:7
      Sep 14 10:24:49 Pats-Main plasmashell[1701]: kpipewire_logging: PipeWire remote error: -2 target not found
      Sep 14 10:24:49 Pats-Main plasmashell[1701]: kpipewire_logging: PipeWire remote error: -2 target not found
      Sep 14 10:24:49 Pats-Main firefox[3666]: [GFX1-]: RenderCompositorSWGL failed mapping default framebuffer, no dt
      Sep 14 10:24:45 Pats-Main plasmashell[1701]: MESA: warning: zink: PERF WARNING! > 100 copy boxes detected for 0x76619442a0c0
      Sep 14 10:24:41 Pats-Main plasmashell[1701]: MESA: warning: zink: PERF WARNING! > 100 copy boxes detected for 0x7660ec75d600
      Sep 14 10:24:30 Pats-Main wpa_supplicant[1028]: wlp5s0: CTRL-EVENT-SIGNAL-CHANGE above=1 signal=-28 noise=9999 txrate=0
      ​My name is Pat, btw...

      -break-

      OK my system is freezing due to Wayland. Or Nvidia and Wayland. So now I've been logging in plasma-x11 and haven't lost my menu bars or firefox.
      Last edited by Buddlespit; Today, 10:27 AM. Reason: I think I got it.
      I'm tired of maintaining my system. I'll let Neon do it for me.

      Comment

      Users Viewing This Topic

      Collapse

      There are 0 users viewing this topic.

      Working...
      X