https://bugs.kde.org/show_bug.cgi?id=482892
--- Comment #7 from Kevin Krammer ---
(In reply to Ivan Čukić from comment #6)
> There was the usual plugin-page in settings similar to the rest of
> applications. Someone decided (forgot who, was a long time ago) that it just
> confuses the
https://bugs.kde.org/show_bug.cgi?id=482891
--- Comment #1 from Kevin Krammer ---
Kolab Resource still missing from kpim6-kdepim-runtime package after upgrade to
6.1
--
You are receiving this mail because:
You are watching all bug changes.
https://bugs.kde.org/show_bug.cgi?id=484327
Kevin Krammer changed:
What|Removed |Added
Version|6.0.1 |6.1.0
--- Comment #3 from Kevin Krammer
https://bugs.kde.org/show_bug.cgi?id=484323
--- Comment #34 from Kevin Krammer ---
After upgrade to Plasma 6.1 the behavior is still present but not as bad as
before.
Xorg still goes up to ~50% of one CPU, but kwin_x11 only to 30% and ksmserver
only to 15%
--
You are receiving this mail
https://bugs.kde.org/show_bug.cgi?id=484323
Kevin Krammer changed:
What|Removed |Added
Version|6.0.3 |6.1.0
--
You are receiving this mail because
https://bugs.kde.org/show_bug.cgi?id=482892
Kevin Krammer changed:
What|Removed |Added
Version|6.0.2 |6.1.0
--
You are receiving this mail because
https://bugs.kde.org/show_bug.cgi?id=484323
--- Comment #28 from Kevin Krammer ---
(In reply to Zamundaaa from comment #27)
> KScreen being stopped preventing this isn't too surprising, as it can
> trigger output changes and that seems to be what's using so much CPU, but
> > or call
https://bugs.kde.org/show_bug.cgi?id=484323
--- Comment #26 from Kevin Krammer ---
(In reply to Petr Tesařík from comment #25)
> (In reply to Kevin Krammer from comment #24)
> > Disabling KScreen2 also works to avoid the issue.
>
> Did you disable the service, log out and lo
https://bugs.kde.org/show_bug.cgi?id=484323
--- Comment #24 from Kevin Krammer ---
(In reply to Kevin Krammer from comment #22)
> (In reply to Zamundaaa from comment #21)
> > Does this still happen if you
> > 1. kill kwin_x11 before locking the screen?
>
> When I
https://bugs.kde.org/show_bug.cgi?id=484323
--- Comment #22 from Kevin Krammer ---
(In reply to Zamundaaa from comment #21)
> Does this still happen if you
> 1. kill kwin_x11 before locking the screen?
When I kill kwin_x11 or call it manually with --replace then the CPU load does
no
https://bugs.kde.org/show_bug.cgi?id=484323
--- Comment #19 from Kevin Krammer ---
Interesting observation on that other ticket which I can confirm on my system:
if I restart kwin_x11 (by running kwin_x11 --replace) it does no longer show
the observed CPU load behavior when locking the screen
https://bugs.kde.org/show_bug.cgi?id=484606
Kevin Krammer changed:
What|Removed |Added
CC||kram...@kde.org
--- Comment #8 from Kevin
https://bugs.kde.org/show_bug.cgi?id=484323
--- Comment #18 from Kevin Krammer ---
(In reply to fbm224 from comment #17)
> Is this the same or related to:
> https://bugs.kde.org/show_bug.cgi?id=484606#1 ? I made comment #6 there.
Great find, this does indeed sound like the same problem.
https://bugs.kde.org/show_bug.cgi?id=484323
--- Comment #12 from Kevin Krammer ---
(In reply to leoh from comment #9)
> Same. Plasma 6.0.3-1 with X11. Laptop with x1 external monitor and laptop
> lid closed.
Can you check if the problem also happens when the external monitor is not
p
https://bugs.kde.org/show_bug.cgi?id=484323
--- Comment #7 from Kevin Krammer ---
(In reply to Francisco from comment #4)
> Notice that ksmserver is also using quite a bit of CPU, maybe they are
> sending each other events in an infinite loop?
I can confirm that I also see an increased C
https://bugs.kde.org/show_bug.cgi?id=484327
--- Comment #1 from Kevin Krammer ---
New observation: main window and composer seem to access the same size
information.
I just realized that the observed 760x830 mentioned in the report are the size
of my non-maximized composer window.
To verify I
https://bugs.kde.org/show_bug.cgi?id=484328
Bug ID: 484328
Summary: Kmail config dialog takes about 40 seconds to show up
Classification: Applications
Product: kmail2
Version: 6.0.1
Platform: Neon
OS: Linux
https://bugs.kde.org/show_bug.cgi?id=484327
Bug ID: 484327
Summary: Bad initial window sizes
Classification: Applications
Product: kmail2
Version: 6.0.1
Platform: Neon
OS: Linux
Status: REPORTED
https://bugs.kde.org/show_bug.cgi?id=484323
Bug ID: 484323
Summary: High CPU load of kwin_x11 when locking the screen
Classification: Plasma
Product: kwin
Version: 6.0.2
Platform: Neon
OS: Linux
Status:
https://bugs.kde.org/show_bug.cgi?id=482892
Kevin Krammer changed:
What|Removed |Added
Version|6.0.0 |6.0.2
--
You are receiving this mail because
https://bugs.kde.org/show_bug.cgi?id=482892
--- Comment #4 from Kevin Krammer ---
Great find!
Removing the plugin does indeed restore predictable switching behavior.
I've changed the product to point to kactivitymanagerd
--
You are receiving this mail because:
You are watching all bug
https://bugs.kde.org/show_bug.cgi?id=482892
Kevin Krammer changed:
What|Removed |Added
CC||plasma-b...@kde.org
Component
https://bugs.kde.org/show_bug.cgi?id=482889
--- Comment #4 from Kevin Krammer ---
(In reply to Kai Uwe Broulik from comment #2)
> Sounds like a trivial fix but I’d like to understand how the scheme can be
> empty in the first place. Any chance you could look at what the url is it
&
https://bugs.kde.org/show_bug.cgi?id=482892
Bug ID: 482892
Summary: Switching activities also switches active virtual
desktop
Classification: Plasma
Product: plasmashell
Version: git-stable-Plasma/5.26
Platform: Neon
https://bugs.kde.org/show_bug.cgi?id=482891
Bug ID: 482891
Summary: Kolab resource gone after upgrade to 6.0.0 mega
release and not migrated to IMAP either
Classification: Frameworks and Libraries
Product: Akonadi
Version: 6.0.0
https://bugs.kde.org/show_bug.cgi?id=224916
Kevin Krammer changed:
What|Removed |Added
Resolution|--- |UNMAINTAINED
Status|CONFIRMED
https://bugs.kde.org/show_bug.cgi?id=482889
--- Comment #1 from Kevin Krammer ---
Created attachment 166723
--> https://bugs.kde.org/attachment.cgi?id=166723=edit
Backtrace with debug symbol packages installed
--
You are receiving this mail because:
You are watching all bug changes.
https://bugs.kde.org/show_bug.cgi?id=482889
Bug ID: 482889
Summary: plasmashell hits ASSERT on startup after upgrade to
6.0.0
Classification: Plasma
Product: plasmashell
Version: 6.0.0
Platform: Neon
https://bugs.kde.org/show_bug.cgi?id=435574
--- Comment #34 from Kevin Krammer ---
(In reply to Neal Gompa from comment #33)
> Nor does it tell you
> whether the update being pushed has been marked as one that requires a
> reboot or relogin.
Yes, sorry, I did not intend
https://bugs.kde.org/show_bug.cgi?id=435574
--- Comment #32 from Kevin Krammer ---
Interesting observation: I've use the config option to return to immediate
update and just had bunch of new KDE packages come through.
They were separated into "Application Updates", "Addons"
https://bugs.kde.org/show_bug.cgi?id=435574
--- Comment #31 from Kevin Krammer ---
(In reply to Aleix Pol from comment #19)
> kcm: Add a configuration setting for offline updates
Awesome, thanks a lot!
This was really annoying for applications with frequent updates, e.g. browsers,
messeng
https://bugs.kde.org/show_bug.cgi?id=438393
--- Comment #3 from Kevin Krammer ---
Thanks for finding the duplicate Nate!
--
You are receiving this mail because:
You are watching all bug changes.
https://bugs.kde.org/show_bug.cgi?id=438393
--- Comment #1 from Kevin Krammer ---
Created attachment 139186
--> https://bugs.kde.org/attachment.cgi?id=139186=edit
Asking for a reboot after installing just an application
--
You are receiving this mail because:
You are watching all bug changes.
https://bugs.kde.org/show_bug.cgi?id=438393
Bug ID: 438393
Summary: Mistakenly considers Chrome update a system upgrade
Product: Discover
Version: 5.22.0
Platform: Neon Packages
OS: Linux
Status: REPORTED
34 matches
Mail list logo
