Announcement

Collapse
No announcement yet.

KDE Saw Many Bug Fixes This Week From KWin Crashes To Plasma Wayland Improvements

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

  • #51
    Originally posted by polarathene View Post

    That doesn't sound right.. Talking about a fresh boot of the system to the desktop. If I include dolphin/kate/terminals and the like from session restore, it's more like 600-700MB atm. Open other software like a web browser and restore all it's tabs and that will add many GB on the desktop, on the laptop I have to keep the amount of tabs/windows for a browser managed due to low ram.
    It is what it is - it's simply the result of how I'm working here. I rebuilt my xps15 from ubuntu to arch clean a few years ago to match my desktop, and it has the exact same ram utilization as my desktop did, and (k)ubuntu was the same prior. I'd love to know what I'm doing wrong, other than using a lot of tabs and libreoffice windows that I simply need 32-128gb of ram to base function.

    Originally posted by polarathene View Post

    You should probably report to KDE's bugzilla. If you're not sure where perhaps you can ask the community for some guidance, but generally they expect you to direct bug reports to bugzilla and not rant on their community channels about it much where it'll get lost over time. r/kde subreddit is pretty good, just chime in about your issue(be more terse as most aren't likely to read paragraphs of text), and someone will probably let you know where on bugzilla it belongs. Alternatively just take a guess, and a dev will relocate it to the appropriate place if it's in the wrong one.

    https://bugs.kde.org/
    https://community.kde.org/Get_Involved/Issue_Reporting
    The window placement issue is obviously a KDE problem, but the cause is more the display handling at either a kernel, video driver, or software layer (xorg, xrandr, kde). The problem I run into if I go to KDE, they tell me to talk to NVidia. If I talk to NVidia, they tell me to talk to KDE, or upstream to the kernel. Round and round we go. Why I had to simply abandon my desktop, as I went through this dance with the GLES driver issue randomly appearing on my desktop - no one (kde, nvidia, or kernel) had any good suggestion, and just kept referring me elsewhere or to try reinstalling everything. I thought I ended that with windoze...

    Like right now, I got a new thunderbolt3 dock for my laptop, as my TB16 Dell unit was failing (bad cable, not replaceable), insert random chinese replacement. Every time my monitors get shut down by os for power save (normal monitor dpms mode to shut down), my 3rd monitor every time comes back in 1920x1200 mode, and refuses to go back to 4k until I disconnect the dock, and restart it. Is it the dock, is it nvidia drivers, is it kde, xrandr, or is it the kernel?

    When it does this, often I can go into KDE and set it to 4k again, sometime I can't like the display is only reporting 1080p as max. If only 1080p max, disconnecting and reconnecting the TB port often works. Sometimes I just end up having to reboot to get my 4k back fully. Trying to chase down who's problem it really is under linux is a bad game of whack-a-mole.

    The good news is they *did* fix the window placement issue, as once I get the displays reporting right after a reconnect, it moves things mostly back to the right place. Mostly... It doesn't on the 3rd display that changes resolution, but far improved from simply slamming all the windows into some default corner that is always simply wrong.

    Comment


    • #52
      Originally posted by ssokolow View Post

      On X11, even with LCDs, I've found the KScreen 2 daemon to have a penchant for confusing Plasma about screen assignments and which panel should go where, so I disable it on my desktop (KRunner → Background Services)... assuming I don't just use nVidia's MetaModes option to lock the desktop resolution to keep games' first-run resolution changes from confusing KWin into squashing everything into a single monitor.
      Try newer KDE if you can - easily done on Arch or other rolling distro's, not so much on ubuntu without going Neon. At least the window positional handling is much improved as of an upgrade last week, as well as restoration of windows to the right places, so long as they don't get too disturbed (which mine do with above TB3 dock gyrations), it it working far better than it has since 4.x. Ahem, about time.

      Comment


      • #53
        Originally posted by mikus View Post

        Try newer KDE if you can - easily done on Arch or other rolling distro's, not so much on ubuntu without going Neon. At least the window positional handling is much improved as of an upgrade last week, as well as restoration of windows to the right places, so long as they don't get too disturbed (which mine do with above TB3 dock gyrations), it it working far better than it has since 4.x. Ahem, about time.
        To be honest, I'm not sure I've ever seen a window manager without that issue. I had the problem under Openbox, Kwin 3.x, Kwin 4.x, and now Kwin 5.x, and it's been a long time, but I vaguely remember having it under other WMs too.

        It's one of the reasons I'm looking forward to a day when there exists a Wayland compositor with crash recovery, server-side window decoration support, and APIs that allow things like automatic time trackers to be ported (and either nVidia support or being far enough in the future that I've replaced my GTX750 with something AMD). Wayland doesn't give arbitrary applications access to the permanent resolution-changing APIs and then defer reacting in an attempt to guess whether it's really a fake-out from a fullscreened application.

        That said, I will admit that I'm currently on Kubuntu 16.04 LTS because my upgrade from 14.04 LTS got side-tracked with bug-squashing long enough that I'm now sufficiently used to its flaws to be more interested in continuing to replace ugly hacks with proper solutions before I press forward.

        Comment


        • #54
          My last adventure with wayland was running ubuntu on my xps originally, as I had for some 13+ years, and finally was sick of it being just as broken, particularly every upgrade. Ubuntu defaulted to wayland, and I could never figure out how to get it back to xorg, as it prevented me from using any desktop other than gnome-shell, and I HATE gnome-shell. I moved to arch, but after a few years of it, can't say I've found it much better for other reasons.

          I've been struggling making any DE work well for me here, I'm starting to think the graphic driver is buggy, or the new kernel, which arch has me up to 5.5.9. So far Cinnamon/Mate will crash in less than 2 days of running hard, and kde is just all over the place, sometimes it'll crash in 20 minutes, sometimes a week. Even bigger issue is my monitors.

          Every time my displays get powered down via the os, it's a total crap shoot which of the external displays will restart. Sometimes 1, sometimes both, sometimes neither. Each DE was a bit different about this too oddly... I might say this might be my TB3 dock, as it is fairly new, but I would get this on my desktop with a 1070gtx with my 3x 48" tv's as well losing random monitors.

          KDE will sometimes not see one of the displays (nor xrandr), sometimes it sees them, but shuts them off, forcing me to reconfigure display settings. It keeps forgetting about it, losing it, whatever, but almost every time I walk away from my desktop, I either need to reconfigure the displays, or unplug/plug back my TB3 dock. It's also getting worse about my window placement and restoration oddly, almost like some state tracking is going insane over time. Also interesting, my kde menu panel freezes after a random interval as well, as well as my systray and other useful things.

          Cinnamon tends to work best, but the hard locking issue is almost a bigger problem than kde being just random and weird. Compositing there works pretty well at least, I just can't pin down the crash as nothing indicates an issue, until it's just dead. It occasionally loses displays too, but a restart of my tb always brings it back up, and all my windows go back where they were meant to, unlike KDE.

          Tried using MATE again, and while not bad, is maddening for other reasons. Mostly lack of HiDPI settings that make everything super huge, or super small, all inconsistently, while still getting the same crash every few days. It is somewhat related to Cinnamon, so something common to the two seems awry... It was not very good about putting my windows back when I'd lose displays there too.

          Truly maddening how consistently unstable/bad kde has become. I have an older Dell Latitude e7240 laptop running kde (5.7.5) neon/ubuntu that is rock solid. I've had it on for the past few months, and use that to try and ssh back to mine to diag when it does crash, and kde on that is absolutely stable with full compositing. I really miss having a DE that works for more than a few hours/days at a time, KDE and others really need to address these issues before anything new.

          Comment

          Working...
          X