https://bugs.kde.org/show_bug.cgi?id=484323
Kai Krakow changed:
What|Removed |Added
CC|k...@kaishome.de |
--- Comment #110 from Kai Krakow ---
Removing
https://bugs.kde.org/show_bug.cgi?id=499039
--- Comment #13 from Kai Krakow ---
BTW, adding to my previous post: I thought wayland windows aren't supposed to
position themselves somewhere specific.
So I wonder how Chrome sometimes positions "itself" to some arbitrary scree
https://bugs.kde.org/show_bug.cgi?id=499039
--- Comment #12 from Kai Krakow ---
(In reply to Kai Krakow from comment #11)
> I'm going to try the wayland platform hint but from my previous tests, this
> introduces other Chrome bugs and even stops some render acceleration fallin
https://bugs.kde.org/show_bug.cgi?id=499039
--- Comment #11 from Kai Krakow ---
I have the feeling that this gets worse with either each Plasma update or each
Chrome update.
Since I use different systems, here are some observations that I can share:
1. This happens only with the wayland
https://bugs.kde.org/show_bug.cgi?id=450696
Kai Krakow changed:
What|Removed |Added
CC||k...@kaishome.de
--- Comment #1 from Kai Krakow
https://bugs.kde.org/show_bug.cgi?id=441077
--- Comment #15 from Kai Krakow ---
Maybe there's a similar issue in dolphin:
If there are many network shares (automounted or kio), dolphin takes a few
seconds before opening its window on first start. Successive starts are much
faster, until I
https://bugs.kde.org/show_bug.cgi?id=501314
Bug ID: 501314
Summary: Maximizing Chrome PWA windows may render without
window frame and offset contents
Classification: Plasma
Product: kwin
Version: 6.3.2
Platform: Other
https://bugs.kde.org/show_bug.cgi?id=500819
Kai Krakow changed:
What|Removed |Added
CC||k...@kaishome.de
--
You are receiving this mail
https://bugs.kde.org/show_bug.cgi?id=499560
Kai Krakow changed:
What|Removed |Added
Ever confirmed|0 |1
Resolution|WORKSFORME
https://bugs.kde.org/show_bug.cgi?id=499560
Kai Krakow changed:
What|Removed |Added
Summary|plasmashell leaks 1-4 GB of |plasmashell allocates
|VRAM
https://bugs.kde.org/show_bug.cgi?id=499560
Kai Krakow changed:
What|Removed |Added
Summary|plasmashell allocates |plasmashell allocates
|500-1500
https://bugs.kde.org/show_bug.cgi?id=499560
--- Comment #6 from Kai Krakow ---
So I've watched plasmashell with `nvidia-smi pmon -s m`, and each time I turn a
monitor off and back on, it adds about 500-1500 MB of VRAM allocations to
plasmashell. The actual value is not consistent and fluct
https://bugs.kde.org/show_bug.cgi?id=499560
--- Comment #5 from Kai Krakow ---
I just logged in remotely. The monitors are off, and the VRAM usage is even
below the "normal" usage:
|0 N/A N/A 848779 G /usr/bin/plasmashell
335MiB |
I'm
https://bugs.kde.org/show_bug.cgi?id=499560
--- Comment #4 from Kai Krakow ---
Thanks. I may give 550 a try.
After using the system with high VRAM usage for a while, I noticed that
plasmashell VRAM allocations goes down again to the original value.
So it's not a leak per-se but high temp
https://bugs.kde.org/show_bug.cgi?id=499560
--- Comment #2 from Kai Krakow ---
Instead of just closing this as "works for me", how about writing which driver
version you are using, so I could try that.
Closing it just because it works for you without even giving any hint what
shoul
https://bugs.kde.org/show_bug.cgi?id=499560
Kai Krakow changed:
What|Removed |Added
Version|git-stable-Plasma/6.2 |6.2.5
--
You are receiving this mail because
https://bugs.kde.org/show_bug.cgi?id=499560
Bug ID: 499560
Summary: plasmashell leaks 1-4 GB of VRAM over a period of less
than 20 hours
Classification: Plasma
Product: plasmashell
Version: git-stable-Plasma/6.2
Platfor
https://bugs.kde.org/show_bug.cgi?id=494156
Bug ID: 494156
Summary: Windows flicker and contents deform when
connecting/turning on monitors
Classification: Plasma
Product: kwin
Version: 6.1.5
Platform: Gentoo Packages
https://bugs.kde.org/show_bug.cgi?id=466771
--- Comment #35 from Kai Krakow ---
(In reply to Ben Hay from comment #33)
> Even swapped my NVidia card for AMD. Bug still occured, although it takes a
> little longer to manifest.
>
> Finally I uninstalled the latte-dock package.
> P
https://bugs.kde.org/show_bug.cgi?id=466771
Kai Krakow changed:
What|Removed |Added
CC||k...@kaishome.de
--- Comment #32 from Kai Krakow
https://bugs.kde.org/show_bug.cgi?id=484323
--- Comment #38 from Kai Krakow ---
(In reply to Kai Krakow from comment #36)
> Is this caused by the blur effects of plasma and konsole?
It may have been resolved, at least partially, by
https://github.com/NVIDIA/open-gpu-kernel-modules/com
https://bugs.kde.org/show_bug.cgi?id=404057
--- Comment #51 from Kai Krakow ---
(In reply to tagwerk19 from comment #50)
> (In reply to Kai Krakow from comment #49)
>
> Thank you for the insights. That's a lot more to think about...
You're welcome.
> What we ha
https://bugs.kde.org/show_bug.cgi?id=404057
--- Comment #49 from Kai Krakow ---
(In reply to tagwerk19 from comment #47)
> That said, I've not noticed the percentages behaving differently than a
> defined amount of memory (so, I think a "MemoryHigh=25%" on a 2GB system
https://bugs.kde.org/show_bug.cgi?id=404057
--- Comment #46 from Kai Krakow ---
(In reply to tagwerk19 from comment #45)
> Yes, there's been a handful of bug reports where I've "blamed" the 512M
> limit.
>
> I tentatively recommend "MemoryHigh=25%". I
https://bugs.kde.org/show_bug.cgi?id=404057
--- Comment #44 from Kai Krakow ---
(In reply to tagwerk19 from comment #43)
> I think the dust has probably settled here after:
> https://invent.kde.org/frameworks/baloo/-/merge_requests/131
> and cherrypicked for KF5
> https://in
https://bugs.kde.org/show_bug.cgi?id=484323
Kai Krakow changed:
What|Removed |Added
CC||k...@kaishome.de
--- Comment #36 from Kai Krakow
https://bugs.kde.org/show_bug.cgi?id=187172
--- Comment #47 from Kai Krakow ---
(In reply to Martin Steigerwald from comment #46)
> Nowadays where Ext3 should not be in wide use anymore, if at all, and
> nowadays where many people use flash based storage, I am strongly for just
> makin
https://bugs.kde.org/show_bug.cgi?id=479859
Bug ID: 479859
Summary: select-and-drag text crashes some or all non-KDE apps
in wayland
Classification: Plasma
Product: kwin
Version: 5.27.10
Platform: Gentoo Packages
https://bugs.kde.org/show_bug.cgi?id=477569
Bug ID: 477569
Summary: Filelight crashes when deleting a directory via
context menu
Classification: Applications
Product: filelight
Version: 23.08.3
Platform: Gentoo Packages
https://bugs.kde.org/show_bug.cgi?id=472182
Bug ID: 472182
Summary: kwin_wayland crashed probably while calling into
pipewire
Classification: Plasma
Product: kwin
Version: 5.27.4
Platform: Gentoo Packages
https://bugs.kde.org/show_bug.cgi?id=377911
Kai Krakow changed:
What|Removed |Added
CC||k...@kaishome.de
--
You are receiving this mail
https://bugs.kde.org/show_bug.cgi?id=469279
--- Comment #3 from Kai Krakow ---
Thanks for investigating. I think this example shows that KDE/Plasma should
treat VRAM as a valuable resource, and it affects a lot of other KDE background
processes, too. So maybe creating some infrastructure to have
https://bugs.kde.org/show_bug.cgi?id=431050
Kai Krakow changed:
What|Removed |Added
CC||k...@kaishome.de
--- Comment #24 from Kai Krakow
https://bugs.kde.org/show_bug.cgi?id=469283
Kai Krakow changed:
What|Removed |Added
Status|REPORTED|RESOLVED
Resolution
https://bugs.kde.org/show_bug.cgi?id=469283
--- Comment #7 from Kai Krakow ---
(In reply to Harald Sitter from comment #5)
> > Do you mean to say that this may have been fixed in 23.04?
>
> Yes
> https://invent.kde.org/network/kio-extras/-/commit/
> 46d3f2fd41dece1d49e7295ae9
https://bugs.kde.org/show_bug.cgi?id=469283
--- Comment #6 from Kai Krakow ---
OTOH, this may also be fixed in Dolphin rather than kio (if there's no way
around that behavior): If Dolphin detects 0 bytes free and 0 bytes size at the
same time, it should infer that there's no informa
https://bugs.kde.org/show_bug.cgi?id=469283
Kai Krakow changed:
What|Removed |Added
Summary|cannot copy files to smb|cannot copy files to smb if
https://bugs.kde.org/show_bug.cgi?id=469283
Kai Krakow changed:
What|Removed |Added
Status|NEEDSINFO |REPORTED
Resolution|WAITINGFORINFO
https://bugs.kde.org/show_bug.cgi?id=469283
--- Comment #2 from Kai Krakow ---
(In reply to Harald Sitter from comment #1)
> Please provide reproducible steps for 1. Setup a DFS share with two member
> servers and DFSR sync
On two Windows Server hosts, install DFS replication services.
I
https://bugs.kde.org/show_bug.cgi?id=469283
Bug ID: 469283
Summary: cannot copy files to smb when accessing a DFS share
Classification: Frameworks and Libraries
Product: kio-extras
Version: 23.04.0
Platform: Gentoo Packages
https://bugs.kde.org/show_bug.cgi?id=441077
--- Comment #12 from Kai Krakow ---
I partially found automounts triggering the problem. With automounts enabled,
right clicking on dolphin window icons or starting konsole (probably every app
that is somehow involved in checking mount point stats) can
https://bugs.kde.org/show_bug.cgi?id=145911
Kai Krakow changed:
What|Removed |Added
Status|CONFIRMED |RESOLVED
Resolution
https://bugs.kde.org/show_bug.cgi?id=469281
Bug ID: 469281
Summary: windows with background blur (e.g., konsole) flicker
and leave mouse trails
Classification: Plasma
Product: kwin
Version: 5.27.4
Platform: Gentoo Packa
https://bugs.kde.org/show_bug.cgi?id=469279
--- Comment #1 from Kai Krakow ---
BTW: Running "kcmshell5 qtquicksettings" and forcing software rendering for
plasma completely eliminates the issue (with Xorg staying really low on VRAM)
but then plasma loudly complains about non-optimal
https://bugs.kde.org/show_bug.cgi?id=469279
Bug ID: 469279
Summary: Running akonadi servers easily doubles or triples VRAM
usage
Classification: Frameworks and Libraries
Product: Akonadi
Version: 5.23.0
Platform: Gentoo
https://bugs.kde.org/show_bug.cgi?id=450301
Kai Krakow changed:
What|Removed |Added
CC||k...@kaishome.de
--- Comment #12 from Kai Krakow
https://bugs.kde.org/show_bug.cgi?id=450068
--- Comment #77 from Kai Krakow ---
For me it seems to be fixed or at least works as expected after I disabled the
kscreen service in the system settings. With each plasma updates, the behavior
seems to change in random and unpredictable ways
https://bugs.kde.org/show_bug.cgi?id=141267
Kai Krakow changed:
What|Removed |Added
CC||k...@kaishome.de
--- Comment #22 from Kai Krakow
https://bugs.kde.org/show_bug.cgi?id=450068
--- Comment #37 from Kai Krakow ---
(In reply to Nate Graham from comment #35)
> Unfortunately this is exactly right. [...]
> The current system needs to be thrown away and replaced with
> something better-engineered from the start, wh
https://bugs.kde.org/show_bug.cgi?id=450068
--- Comment #33 from Kai Krakow ---
(In reply to Iyán Méndez Veiga from comment #32)
> Plasma 5.25.90 has a new issue and it's really unstable and difficult to
> replicate. Every morning when I connect the laptop to the docking station I
>
https://bugs.kde.org/show_bug.cgi?id=412005
Kai Krakow changed:
What|Removed |Added
Status|NEEDSINFO |RESOLVED
Resolution|WAITINGFORINFO
https://bugs.kde.org/show_bug.cgi?id=356225
--- Comment #409 from Kai Krakow ---
(In reply to Nate Graham from comment #408)
> This bug report is only about Plasma panels moving, not windows. That's a
> different issue.
Except it may be not... I'm seeing a similar behavior:
https://bugs.kde.org/show_bug.cgi?id=450068
--- Comment #27 from Kai Krakow ---
We probably need a system which stores a containment layout per number of
monitors connecting. If an additional monitor gets connected, clone the next
"lower count" layout. Then, sort the primary moni
https://bugs.kde.org/show_bug.cgi?id=356727
--- Comment #76 from Kai Krakow ---
(In reply to Nate Graham from comment #75)
> As a result it would
> probably be best if people who are still affected could file new bug
> reports, and I will try my best to triage them accordingly. Thanks!
https://bugs.kde.org/show_bug.cgi?id=453554
Kai Krakow changed:
What|Removed |Added
Version Fixed In|5.25|
--
You are receiving this mail because:
You are
https://bugs.kde.org/show_bug.cgi?id=453554
--- Comment #9 from Kai Krakow ---
Created attachment 150180
--> https://bugs.kde.org/attachment.cgi?id=150180&action=edit
configuration completely doesn't match the output
Here's an example of messed up content:
As you can see, t
https://bugs.kde.org/show_bug.cgi?id=453554
Kai Krakow changed:
What|Removed |Added
Status|RESOLVED|REOPENED
Resolution|FIXED
https://bugs.kde.org/show_bug.cgi?id=453554
--- Comment #6 from Kai Krakow ---
Okay, so I'm now on Plasma 5.25 and this original issue seems fixed.
But now, when I turn the monitor back on, the background image of that monitor
is gone and completely black. I also cannot right click o
https://bugs.kde.org/show_bug.cgi?id=453554
--- Comment #5 from Kai Krakow ---
It worked for a few days in a row. But yesterday evening and today morning,
this happened again and the behavior is quite random:
This time, only the top panel moved to the wrong screen while the bottom panel
stood
https://bugs.kde.org/show_bug.cgi?id=453554
--- Comment #4 from Kai Krakow ---
Also, Plasma version is probably not the only thing that changed. The nvidia
driver was also updated at least once, and Xorg components were also updated at
least once. But I cannot really pin-point that to one of
https://bugs.kde.org/show_bug.cgi?id=453554
--- Comment #3 from Kai Krakow ---
(In reply to Marco Martin from comment #1)
> are all outputs connected to the internal videocard or there are external DP
> dongles involved?
No dongles but there is one DP-to-HDMI cable. Not sure if that count
https://bugs.kde.org/show_bug.cgi?id=453554
Bug ID: 453554
Summary: turning one monitor off kills the panel configuration
of the second monitor
Product: plasmashell
Version: 5.24.5
Platform: Gentoo Packages
https://bugs.kde.org/show_bug.cgi?id=441077
--- Comment #10 from Kai Krakow ---
OTOH, I could try migrating to a borg client/server model instead of opening
the repository via filesystem directly. This also decouples some security
concerns as the borg service limits access patterns to those
https://bugs.kde.org/show_bug.cgi?id=441077
--- Comment #9 from Kai Krakow ---
I'm not sure how that could even work.
(a) it runs from a different session context, it's running from systemd system
service while kio-fuse is a user session dbus service
(b) this would imply that I cou
https://bugs.kde.org/show_bug.cgi?id=441077
--- Comment #7 from Kai Krakow ---
(In reply to Nate Graham from comment #5)
> That's what kio-fuse was meant to solve. Do you have it installed?
Ah ok, didn't know how it worked - and it was eventually kicked from the system
previ
https://bugs.kde.org/show_bug.cgi?id=441077
--- Comment #4 from Kai Krakow ---
(In reply to Nate Graham from comment #2)
> In general, this is why KIO exists: to provide asynchronous, non-blocking
> access to flaky network resources. When you bypass KIO and mount them
> directly, you&#
https://bugs.kde.org/show_bug.cgi?id=441077
--- Comment #1 from Kai Krakow ---
Created attachment 140791
--> https://bugs.kde.org/attachment.cgi?id=140791&action=edit
thread apply all bt full
--
You are receiving this mail because:
You are watching all bug changes.
https://bugs.kde.org/show_bug.cgi?id=441077
Bug ID: 441077
Summary: Plasmashell panels may freeze, usually unrelated but
unresponsive NFS/SMB mounts are involved
Product: plasmashell
Version: 5.21.5
Platform: Other
https://bugs.kde.org/show_bug.cgi?id=402154
--- Comment #22 from Kai Krakow ---
(In reply to tagwerk19 from comment #20)
> (In reply to Kai Krakow from comment #18)
> > ... I suggest to
> > read that entirely to understand the problem ...
> I've done my best :-) Thank yo
https://bugs.kde.org/show_bug.cgi?id=402154
--- Comment #19 from Kai Krakow ---
BTW: Such a UUID-to-deviceId mapping table would allow baloo to properly
support most yet unsupported filesystems, probably also zfs. With such an idea
implemented, the only requirement left to a supported filesystem
https://bugs.kde.org/show_bug.cgi?id=402154
Kai Krakow changed:
What|Removed |Added
CC||k...@kaishome.de
--- Comment #18 from Kai Krakow
https://bugs.kde.org/show_bug.cgi?id=435444
--- Comment #3 from Kai Krakow ---
Are there instruction on how to properly create a dbus monitor log?
--
You are receiving this mail because:
You are watching all bug changes.
https://bugs.kde.org/show_bug.cgi?id=435444
Kai Krakow changed:
What|Removed |Added
Version|5.21.3 |5.21.4
--
You are receiving this mail because
https://bugs.kde.org/show_bug.cgi?id=435444
--- Comment #1 from Kai Krakow ---
Killing kdeconnectd seems to stop this behavior.
--
You are receiving this mail because:
You are watching all bug changes.
https://bugs.kde.org/show_bug.cgi?id=435444
Bug ID: 435444
Summary: bluetooth is constantly scanning for services /
devices
Product: Bluedevil
Version: 5.21.3
Platform: Gentoo Packages
OS: Linux
https://bugs.kde.org/show_bug.cgi?id=421131
--- Comment #14 from Kai Krakow ---
I'd say that "loss of input events" should be actionable... (reported in
comment #11) I don't care if mouse lags behind a little bit or jumps during CPU
spikes, this also happens using X11. But
https://bugs.kde.org/show_bug.cgi?id=421131
--- Comment #11 from Kai Krakow ---
BTW: It's not only the mouse cursor lagging, key presses are also simply not
detected. And this even happens with a low average CPU load if you just have
some processes stuck in IO for a few ms: I was thinkin
https://bugs.kde.org/show_bug.cgi?id=364947
Kai Krakow changed:
What|Removed |Added
Resolution|WAITINGFORINFO |UNMAINTAINED
Status|NEEDSINFO
https://bugs.kde.org/show_bug.cgi?id=422282
--- Comment #19 from Kai Krakow ---
Following up on my original report https://bugs.kde.org/show_bug.cgi?id=428770:
When the problem occurs, I usually see every folder entry duplicated. I only
observed that in folder tree mode when expanding the tree
https://bugs.kde.org/show_bug.cgi?id=377588
--- Comment #6 from Kai Krakow ---
I can still reproduce it on a real 2-monitor system at work: After an update to
Plasma 5.20, one panel was gone, the other moved over to the second monitor.
When I switch between Wayland session and X11 session, I
https://bugs.kde.org/show_bug.cgi?id=428770
Bug ID: 428770
Summary: Dolphin crashed when browsing cifs mounts
Product: dolphin
Version: 20.08.2
Platform: Gentoo Packages
OS: Linux
Status: REPORTED
Keywords
https://bugs.kde.org/show_bug.cgi?id=421131
Kai Krakow changed:
What|Removed |Added
CC||k...@kaishome.de
--- Comment #9 from Kai Krakow
https://bugs.kde.org/show_bug.cgi?id=375951
--- Comment #38 from Kai Krakow ---
(In reply to Adam from comment #34)
> I would love to see LIM. Having the two bars is a waste of space imo.
>
> I tried with the menu button before, but then you don't see which menus are
> availa
https://bugs.kde.org/show_bug.cgi?id=420030
Bug ID: 420030
Summary: Konsole crashed after creating a new profile
Product: konsole
Version: 19.12.3
Platform: Gentoo Packages
OS: Linux
Status: REPORTED
Keywo
https://bugs.kde.org/show_bug.cgi?id=415286
Kai Krakow changed:
What|Removed |Added
CC||k...@kaishome.de
--- Comment #10 from Kai Krakow
https://bugs.kde.org/show_bug.cgi?id=404057
--- Comment #40 from Kai Krakow ---
Further research confirms: btrfs has unstable device ids because it exposes
subvolumes as virtual block devices without their own device node in /dev.
Thus, device id numbers are allocated dynamically at runtime from
https://bugs.kde.org/show_bug.cgi?id=404057
--- Comment #38 from Kai Krakow ---
(In reply to Martin Steigerwald from comment #35)
> I like the idea to use one DB per filesystem. This way you can save the
> complete filesystem UUID and/or other identifying information *once* and use
> th
https://bugs.kde.org/show_bug.cgi?id=404057
--- Comment #36 from Kai Krakow ---
Oh, nice... Sometimes it helps to talk about a few things.
I could think of the following solution:
Add another UUID->CounterID mapping table to the database, that is easy to
achieve. Everytime we encounter a
https://bugs.kde.org/show_bug.cgi?id=404057
--- Comment #33 from Kai Krakow ---
Also, LMDB is totally the wrong tool when using 32-bit systems because your
index cannot grow beyond a certain size before crashing baloo.
I'm not sure if 32-bit systems are still a thing - but if they are
https://bugs.kde.org/show_bug.cgi?id=404057
--- Comment #32 from Kai Krakow ---
(In reply to Martin Steigerwald from comment #30)
> I believe this bug is at
> least about two or three independent issues, but as you told, let's have it
> about the re-indexing files thing. I bet
https://bugs.kde.org/show_bug.cgi?id=404057
--- Comment #31 from Kai Krakow ---
As far as I understand from researching the discussions in phabricator, this
problem won't be easy to fix as it is baked into the design decision that
defined the database scheme.
Based on the fact that the
https://bugs.kde.org/show_bug.cgi?id=404057
--- Comment #29 from Kai Krakow ---
During the re-index job after reboot, baloo shows very strange behavior when
evaluating the indexSize:
$ balooctl indexSize
File Size: 6,83 GiB
Used: 25,48 MiB
PostingDB: 1.018,96 MiB 3998.360
https://bugs.kde.org/show_bug.cgi?id=404057
--- Comment #28 from Kai Krakow ---
(In reply to Kai Krakow from comment #19)
> After testing this a few days, with my patches it works flawlessly: No
> performance impact, krunner finds result immediately without thrashing the
> HDD, etc
https://bugs.kde.org/show_bug.cgi?id=404057
Kai Krakow changed:
What|Removed |Added
Attachment #122925|0 |1
is obsolete
https://bugs.kde.org/show_bug.cgi?id=404057
Kai Krakow changed:
What|Removed |Added
Attachment #122918|0 |1
is obsolete
https://bugs.kde.org/show_bug.cgi?id=404057
--- Comment #25 from Kai Krakow ---
Yes, that's my plan. But I'd like to refine them a bit first. Especially
turning fsync() off seems to involve a big controversy discussion about whether
this should be done or not. So I will research the si
https://bugs.kde.org/show_bug.cgi?id=404057
--- Comment #23 from Kai Krakow ---
I'll have a look at that soon. First I'd like to get the "Reduce stack
pressure" patch upstreamed (also as a learning curve because this is my first
KDE contribution). I've uploaded it t
https://bugs.kde.org/show_bug.cgi?id=404057
Kai Krakow changed:
What|Removed |Added
See Also||https://bugs.kde.org/show_b
https://bugs.kde.org/show_bug.cgi?id=400704
Kai Krakow changed:
What|Removed |Added
See Also||https://bugs.kde.org/show_b
https://bugs.kde.org/show_bug.cgi?id=356357
Kai Krakow changed:
What|Removed |Added
See Also||https://bugs.kde.org/show_b
1 - 100 of 156 matches
Mail list logo
