https://bugs.kde.org/show_bug.cgi?id=489840
--- Comment #36 from Robin Bankhead ---
I just reviewed this report's sort-of precursor [1] - which I had been
reluctant to add here as it's quite a mess and petered out - and out of those
commenters there who I think likely to actually hav
https://bugs.kde.org/show_bug.cgi?id=489840
--- Comment #34 from Robin Bankhead ---
(In reply to Pierre Ossman from comment #32)
> TigerVNC developer here, trying to have a look at this.
>
> (In reply to Robin Bankhead from comment #26)
> > If that's the case then we may
https://bugs.kde.org/show_bug.cgi?id=489840
Robin Bankhead changed:
What|Removed |Added
See Also||https://github.com/TigerVNC
https://bugs.kde.org/show_bug.cgi?id=489840
--- Comment #31 from Robin Bankhead ---
(In reply to Davide Favaro from comment #30)
> coss posting to #489840 and #306352 because I don't know which one is the
> correct one.
> I have the same problem: remote TigerVNC session eatin
https://bugs.kde.org/show_bug.cgi?id=489840
--- Comment #29 from Robin Bankhead ---
Now on plasma-6.2.2 and have noticed some change in behaviour.
1. Triggering has returned to on first manual keypress within the VNC client
session, rather than immediately on client connect.
2. On killing and
https://bugs.kde.org/show_bug.cgi?id=306352
--- Comment #32 from Robin Bankhead ---
Can anyone followup on whether this commit has fixed their occurrence of this
bug?
For my part, it has not, but I demur on reopening this report myself because I
created #489840 to address my specific set of
https://bugs.kde.org/show_bug.cgi?id=492285
--- Comment #4 from Robin Bankhead ---
Thank you for clarifying things for me. So it sounds like the virtual backend
*can* provide what a 3rd-party VNC server would need on the output side. I will
look elsewhere for what would need doing on the input
https://bugs.kde.org/show_bug.cgi?id=492285
--- Comment #2 from Robin Bankhead ---
(In reply to Vlad Zahorodnii from comment #1)
> It sounds like you rather need a way to tell the plasma start script to
> start kwin_wayland with the virtual backend and also provide a way to pass
> a
https://bugs.kde.org/show_bug.cgi?id=466836
Robin Bankhead changed:
What|Removed |Added
CC||kde.b...@headbank.co.uk
--
You are receiving
https://bugs.kde.org/show_bug.cgi?id=492285
Bug ID: 492285
Summary: Support headless VNC server like WayVNC
Classification: Plasma
Product: kwin
Version: unspecified
Platform: unspecified
OS: Linux
Status: REPOR
https://bugs.kde.org/show_bug.cgi?id=481912
Robin Bankhead changed:
What|Removed |Added
CC||kde.b...@headbank.co.uk
--
You are receiving
https://bugs.kde.org/show_bug.cgi?id=15329
Robin Bankhead changed:
What|Removed |Added
CC||kde.b...@headbank.co.uk
--
You are receiving
https://bugs.kde.org/show_bug.cgi?id=489840
--- Comment #28 from Robin Bankhead ---
Created attachment 172758
--> https://bugs.kde.org/attachment.cgi?id=172758&action=edit
Screenshot of Gammaray attached to kglobalacceld in Xvnc session
Found it. Another KDAB app, do you work f
https://bugs.kde.org/show_bug.cgi?id=489840
--- Comment #26 from Robin Bankhead ---
If that's the case then we may have run out of road here, because tigervnc only
support systemd nowadays.
What I could do is solicit for Gentoo systemd+KDE users in the forums to see if
the issue exists for
https://bugs.kde.org/show_bug.cgi?id=489840
--- Comment #24 from Robin Bankhead ---
Could it have anything to do with dbus?
I can't resist the suspicion that openrc vs systemd lies at the root of the
issue, and the logging shows a number of dbus-related complaints including this
one t
https://bugs.kde.org/show_bug.cgi?id=489840
--- Comment #21 from Robin Bankhead ---
Created attachment 172739
--> https://bugs.kde.org/attachment.cgi?id=172739&action=edit
perf.data.perfparser exported from hotspot, xz-compressed
--
You are receiving this mail because:
You are watch
https://bugs.kde.org/show_bug.cgi?id=489840
Robin Bankhead changed:
What|Removed |Added
Attachment #172729|0 |1
is obsolete
https://bugs.kde.org/show_bug.cgi?id=489840
--- Comment #17 from Robin Bankhead ---
Created attachment 172729
--> https://bugs.kde.org/attachment.cgi?id=172729&action=edit
perf.data capture, xz-compressed (raw size 414MB)
perf data as requested, ~10s worth captured just after trigger
https://bugs.kde.org/show_bug.cgi?id=489840
Robin Bankhead changed:
What|Removed |Added
Attachment #172536|0 |1
is obsolete
https://bugs.kde.org/show_bug.cgi?id=489840
--- Comment #15 from Robin Bankhead ---
(In reply to fanzhuyifan from comment #12)
> Any chance you could get timestamps in front of the log lines, so that we
> know how long everything is taking? E.g., take a look at
> https://server
https://bugs.kde.org/show_bug.cgi?id=489840
--- Comment #14 from Robin Bankhead ---
(In reply to fanzhuyifan from comment #6)
> When kglobalacceld uses 100% of CPU, could you attach a gdb instance to it,
> press Ctrl-C, and upload the results of `thread apply all backtrace full`?
> T
https://bugs.kde.org/show_bug.cgi?id=489840
Robin Bankhead changed:
What|Removed |Added
Attachment #171431|0 |1
is obsolete
https://bugs.kde.org/show_bug.cgi?id=489840
--- Comment #9 from Robin Bankhead ---
Have rebuilt kglobalacceld with the full MR patch -- no change, as you expected
-- and without stripping. If I have to do the same for other packages as well,
it will be a while before I can do this as it will
https://bugs.kde.org/show_bug.cgi?id=489840
--- Comment #7 from Robin Bankhead ---
Will do - once I re-teach myself how. Been over a decade.
Ctrl+C might not work under the bugged condition within the VNC session - is
there any problem with doing that in a VT, or in a parallel SSH session
https://bugs.kde.org/show_bug.cgi?id=489840
Robin Bankhead changed:
What|Removed |Added
Resolution|WAITINGFORINFO |---
Status|NEEDSINFO
https://bugs.kde.org/show_bug.cgi?id=489840
--- Comment #3 from Robin Bankhead ---
Thanks. We will see in October. I spotted this commit and did wonder if it
might be pertinent.
However I note that your description of the issue describes the CPU surge as
being "1 minute plus"; my
https://bugs.kde.org/show_bug.cgi?id=306352
--- Comment #30 from Robin Bankhead ---
For those who have triggered the behaviour by using xmodmap, this recent commit
may be of interest:
https://github.com/KDE/kglobalacceld/commit/105a0eaf80effcc4c014ed8b0b14bc2d656bae33
It speaks of the
https://bugs.kde.org/show_bug.cgi?id=489840
--- Comment #1 from Robin Bankhead ---
I obtained a change in behaviour by removing all KDE/Plasma related content
from ~/.cache folder.
Having done this and launched a new tigervnc Xvnc session, the CPU surge starts
as soon as the VNC client connects
https://bugs.kde.org/show_bug.cgi?id=489840
Bug ID: 489840
Summary: kglobalacceld 100% CPU in Xvnc session
Classification: Frameworks and Libraries
Product: frameworks-kglobalaccel
Version: 6.1.0
Platform: Gentoo Packages
O
https://bugs.kde.org/show_bug.cgi?id=306352
--- Comment #29 from Robin Bankhead ---
Plasma 6(.1) update: situation worse :(
[Reminder, my context = in tigervnc-server session]
The initial CPU spike still happens (I'm not sure if it actually still required
any keyboard input to trigger it,
https://bugs.kde.org/show_bug.cgi?id=484384
Robin Bankhead changed:
What|Removed |Added
Summary|No system info displayed on |No system info displayed on
https://bugs.kde.org/show_bug.cgi?id=484384
Bug ID: 484384
Summary: No system info displayed on wayland/raspberry pi OS
Classification: Applications
Product: plasma-systemmonitor
Version: 5.27.5
Platform: Other
OS: Linux
https://bugs.kde.org/show_bug.cgi?id=422529
Robin Bankhead changed:
What|Removed |Added
CC||kde.b...@headbank.co.uk
--
You are receiving
https://bugs.kde.org/show_bug.cgi?id=434922
Robin Bankhead changed:
What|Removed |Added
CC||kde.b...@headbank.co.uk
--
You are receiving
https://bugs.kde.org/show_bug.cgi?id=443168
--- Comment #26 from Robin Bankhead ---
@JoostR it's not at all inappropriate to discuss how to resolve a bug in that
bug's comment thread. That's exactly what it is for. What behaviour is desired
must be hashed out before it can be impl
https://bugs.kde.org/show_bug.cgi?id=443168
--- Comment #22 from Robin Bankhead ---
> @Robin Bankhead
> > It doesn't make any sense for Gwenview to revert to obeying Dolphin's
> > ordering instead of persisting the ordering chosen in its own UI, across
> > mul
https://bugs.kde.org/show_bug.cgi?id=443168
--- Comment #16 from Robin Bankhead ---
(In reply to Andrew Shark from comment #13)
> > I fail to see why it should be in sync with Dolphin at all
>
> That is incorrect. My use case is that I do not use Gwenview as an image
> browse
https://bugs.kde.org/show_bug.cgi?id=443168
--- Comment #12 from Robin Bankhead ---
(In reply to Christoph Cullmann from comment #11)
> The first thing I need to do is always to set the order twice. It shows sort
> by name, but doesn't do that, I need to set an other one and set it b
https://bugs.kde.org/show_bug.cgi?id=306352
--- Comment #24 from Robin Bankhead ---
I've found a way to trigger the cpu thrash on-demand (when in VNC session). I
noticed one of my custom shortcuts was triggering it every time, but on
investigation it is not the shortcut but this command i
https://bugs.kde.org/show_bug.cgi?id=306352
--- Comment #23 from Robin Bankhead ---
Sorry, amendment to the above on further investigation.
The CPU spike is triggered by ANY keyboard input (e.g. typing a letter key,
which opens the quick-launcher, or CTRL on its own which has no UI effect
https://bugs.kde.org/show_bug.cgi?id=306352
--- Comment #22 from Robin Bankhead ---
Further data point: I just added a systemmonitor plasmoid to my panel to show
CPU usage, and interestingly after first opening my vnc session it actually did
not show any heavy activity.
It started maxing one
https://bugs.kde.org/show_bug.cgi?id=425638
Robin Bankhead changed:
What|Removed |Added
CC||kde.b...@headbank.co.uk
--
You are receiving
https://bugs.kde.org/show_bug.cgi?id=464392
Robin Bankhead changed:
What|Removed |Added
CC||kde.b...@headbank.co.uk
--
You are receiving
https://bugs.kde.org/show_bug.cgi?id=306352
--- Comment #18 from Robin Bankhead ---
As mentioned above I'm on Gentoo, so no systemd involved here. And being in VNC
I don't see it being graphics stack related either, but that's probably a bit
above my pay-grade to say ;)
I
https://bugs.kde.org/show_bug.cgi?id=306352
--- Comment #16 from Robin Bankhead ---
Just to update on my earlier, I haven't found a way of re-triggering the high
CPU usage after killing and relaunching kglobalaccel5 at the start of my VNC
session, and it has not recurred again during s
https://bugs.kde.org/show_bug.cgi?id=306352
--- Comment #15 from Robin Bankhead ---
FWIW, the issue as I outlined my experience of it is still occurring under
kde-frameworks/kglobalaccel-5.97.0, but for the first time I have also
encountered it recurring later in my VNC session. (It is possible
https://bugs.kde.org/show_bug.cgi?id=306352
Robin Bankhead changed:
What|Removed |Added
CC||kde.b...@headbank.co.uk
--- Comment #10 from
https://bugs.kde.org/show_bug.cgi?id=443168
Robin Bankhead changed:
What|Removed |Added
CC||kde.b...@headbank.co.uk
--- Comment #5 from
https://bugs.kde.org/show_bug.cgi?id=450230
Robin Bankhead changed:
What|Removed |Added
CC||kde.b...@headbank.co.uk
--- Comment #1 from
https://bugs.kde.org/show_bug.cgi?id=443757
--- Comment #16 from Robin Bankhead ---
Have just updated to 5.24 and have to be honest, this is not a very good
replacement.
- Windows are smaller
- Thick blue border around centred window
- No reflections
- Opaque grey background instead of
https://bugs.kde.org/show_bug.cgi?id=443757
--- Comment #11 from Robin Bankhead ---
Maybe I'll understand when I see the new version, but I don't see how removing
reflections is an improvement. Couldn't they be made an option? Good to see
this has been done though.
--
You are
https://bugs.kde.org/show_bug.cgi?id=443757
Robin Bankhead changed:
What|Removed |Added
CC||kde.b...@headbank.co.uk
--
You are receiving
https://bugs.kde.org/show_bug.cgi?id=438883
Robin Bankhead changed:
What|Removed |Added
CC||kde.b...@headbank.co.uk
--
You are receiving
https://bugs.kde.org/show_bug.cgi?id=443410
Robin Bankhead changed:
What|Removed |Added
CC||kde.b...@headbank.co.uk
--
You are receiving
https://bugs.kde.org/show_bug.cgi?id=433260
Robin Bankhead changed:
What|Removed |Added
CC||kde.b...@headbank.co.uk
--- Comment #4 from
55 matches
Mail list logo