https://bugs.kde.org/show_bug.cgi?id=438318
--- Comment #28 from Shmerl ---
Looks like the whole thing is built on top of libksysguard, so I need to figure
out how to filters sensors from there to skip ones for CPU and GPU.
--
You are receiving this mail because:
You are watching all bug
https://bugs.kde.org/show_bug.cgi?id=438318
--- Comment #27 from Shmerl ---
I'll take a look into making a patch that simply removes this filtering.
--
You are receiving this mail because:
You are watching all bug changes.
https://bugs.kde.org/show_bug.cgi?id=438318
--- Comment #25 from Shmerl ---
(In reply to Ilia Kats from comment #24)
> I'm all for making KDE beginner-friendly, but it shouldn't be at the cost of
> advanced users. Perhaps there can be an option, off by default, to show all
> the sens
https://bugs.kde.org/show_bug.cgi?id=443872
--- Comment #24 from Shmerl ---
Tested the patch, it fixed the spikes for me too with CP2077!
--
You are receiving this mail because:
You are watching all bug changes.
https://bugs.kde.org/show_bug.cgi?id=443872
--- Comment #23 from Shmerl ---
Let me try to apply that to KWin 5.23.2.
--
You are receiving this mail because:
You are watching all bug changes.
https://bugs.kde.org/show_bug.cgi?id=443872
--- Comment #18 from Shmerl ---
I definitely don't see such spikes in X11 session though, so something must be
different.
--
You are receiving this mail because:
You are watching all bug changes.
https://bugs.kde.org/show_bug.cgi?id=443872
--- Comment #17 from Shmerl ---
Run the test with CP2077.
I only see that value flipping in the long when I minimize the game window
(then vrr turns off)
kwin_wayland_drm: vrr changed to 0
and restore it back (then vrr turns
https://bugs.kde.org/show_bug.cgi?id=443872
--- Comment #16 from Shmerl ---
OK, trying to build the custom KWin now. I suppose in Debain that would be
producing modified kwin-wayland-backend-drm package.
--
You are receiving this mail because:
You are watching all bug changes.
https://bugs.kde.org/show_bug.cgi?id=438318
--- Comment #21 from Shmerl ---
For now I'm sticking to ksysguard which is not enforcing any pointless
artificial limitations like that.
--
You are receiving this mail because:
You are watching all bug changes.
https://bugs.kde.org/show_bug.cgi?id=438318
--- Comment #20 from Shmerl ---
I can confirm that power consumption isn't being picked up from lm sensors for
amdgpu.
Here is what I see when running sensors:
amdgpu-pci-0f00
Adapter: PCI adapter
vddgfx:6.00 mV
fan1: 0 RPM (min
https://bugs.kde.org/show_bug.cgi?id=438318
--- Comment #18 from Shmerl ---
I hold there still should be a way to add any kind of sensors, not filtering
GPU ones out on purpose.
--
You are receiving this mail because:
You are watching all bug changes.
https://bugs.kde.org/show_bug.cgi?id=443872
--- Comment #14 from Shmerl ---
Where will that log appear btw? Is it
$HOME/.local/share/sddm/wayland-session.log
--
You are receiving this mail because:
You are watching all bug changes.
https://bugs.kde.org/show_bug.cgi?id=443872
--- Comment #13 from Shmerl ---
OK, I can try building custom kwin with this patch.
--
You are receiving this mail because:
You are watching all bug changes.
https://bugs.kde.org/show_bug.cgi?id=443872
--- Comment #11 from Shmerl ---
(In reply to Zamundaaa from comment #10)
> Created attachment 142746 [details]
> debug logging for vrr enable/disable
Will this land in the upcoming Plasma bugfix releases? And how do I run
something with such
https://bugs.kde.org/show_bug.cgi?id=443872
--- Comment #8 from Shmerl ---
If it's stutter may be it's something with LFC kicking in? I.e. low framerate
compensation where monitor runs at refresh rate that's multiple of the
framerate below certain point?
But I didn't notice framerate dropping
https://bugs.kde.org/show_bug.cgi?id=443872
--- Comment #6 from Shmerl ---
OK, I run some tests with that env variable set.
It's still happening. And I also tried not to use mouse and keyboard during the
test. Those spikes still periodically occur.
--
You are receiving this mail because:
You
https://bugs.kde.org/show_bug.cgi?id=443872
--- Comment #5 from Shmerl ---
I can try to set that env variable in the profile and see if it makes a
difference.
--
You are receiving this mail because:
You are watching all bug changes.
https://bugs.kde.org/show_bug.cgi?id=443872
--- Comment #4 from Shmerl ---
(In reply to Zamundaaa from comment #3)
> It has to be visible and usually has the system theme (but that's not a
> given).
I this case I only see in-game UI and cursor, no system UI. Reading about
CP2077, it d
https://bugs.kde.org/show_bug.cgi?id=443872
--- Comment #2 from Shmerl ---
(In reply to Zamundaaa from comment #1)
> Does the refresh rate jump in response to moving a visible hardware cursor
> or really periodically, without input? The former would be expected behavior
> atm
https://bugs.kde.org/show_bug.cgi?id=443872
Shmerl changed:
What|Removed |Added
Version|unspecified |5.23.0
--
You are receiving this mail because:
You
https://bugs.kde.org/show_bug.cgi?id=443872
Bug ID: 443872
Summary: Inconsistent adaptive sync behavior in KWin Wayland
session
Product: kwin
Version: unspecified
Platform: Debian testing
OS: Linux
https://bugs.kde.org/show_bug.cgi?id=438318
--- Comment #14 from Shmerl ---
To give another example. Imagine, tomorrow k10temp and amdgpu will add another
metric. Since CPU / GPU UI doesn't anticipate it, it will be missing there
until you implement it. While if you simply read all that sensors
https://bugs.kde.org/show_bug.cgi?id=438318
--- Comment #13 from Shmerl ---
(In reply to David Redondo from comment #6)
> The cause of the problem is, that in the new sensors plugin coretemp,
> k10temp and amdgpu are intentionally excluded to not expose duplicated
> sensor
https://bugs.kde.org/show_bug.cgi?id=439765
--- Comment #5 from Shmerl ---
If it matters, my other settings from Klipper:
"Ignore selection": checked.
"Text selection only": unchecked
"Synchronize contents of the clipboard and the selection": unchecked.
Timeou
https://bugs.kde.org/show_bug.cgi?id=439765
--- Comment #3 from Shmerl ---
I also tried experimenting with some options in Klipper settings, and noticed
that this bug doesn't happen when "Prevent empty clipboard" is unchecked. It
happens the above option is enabled.
--
You are
https://bugs.kde.org/show_bug.cgi?id=439765
--- Comment #2 from Shmerl ---
Both windows are Wayland windows. Also confirmed with KWin console that no
XWayland windows are present.
Successful selection:
[597918.013] zwp_primary_selection_device_v1@12.data_offer(new id
https://bugs.kde.org/show_bug.cgi?id=424754
--- Comment #41 from Shmerl ---
Opened bug 439765.
--
You are receiving this mail because:
You are watching all bug changes.
https://bugs.kde.org/show_bug.cgi?id=439765
Bug ID: 439765
Summary: Clipboard is intermittently broken in the Wayland
session
Product: plasmashell
Version: 5.22.3
Platform: Debian testing
OS: Linux
https://bugs.kde.org/show_bug.cgi?id=424754
--- Comment #40 from Shmerl ---
(In reply to Nate Graham from comment #39)
> If XWayland is not involved, that sounds like a different bug. :)
OK, I'll open another one. But the symptom looks very similar.
--
You are receiving this mail because:
https://bugs.kde.org/show_bug.cgi?id=424754
Shmerl changed:
What|Removed |Added
CC||shtetl...@gmail.com
--- Comment #38 from Shmerl
https://bugs.kde.org/show_bug.cgi?id=439574
Shmerl changed:
What|Removed |Added
Summary|Don't filter out amdgpu |Don't filter out amdgpu
|from
https://bugs.kde.org/show_bug.cgi?id=439574
Shmerl changed:
What|Removed |Added
Platform|Other |Debian testing
--
You are receiving this mail
https://bugs.kde.org/show_bug.cgi?id=439574
Bug ID: 439574
Summary: Don't filter out amdgpu from selectable of hardware
sensors to monitor.
Product: plasma-systemmonitor
Version: 5.22.2
Platform: Other
OS:
https://bugs.kde.org/show_bug.cgi?id=428871
--- Comment #1 from Shmerl ---
I just noticed something strange. When opening one clip of the playlist for the
first time, controls actually work. But after jumping to the next (or previous
one), they stop working. Refreshing the page and starting
https://bugs.kde.org/show_bug.cgi?id=428871
Bug ID: 428871
Summary: Next / previous media controls stopped working with
Youtube playlists
Product: plasma-browser-integration
Version: unspecified
Platform: Debian testing
https://bugs.kde.org/show_bug.cgi?id=428663
--- Comment #3 from Shmerl ---
The(In reply to Christoph Feck from comment #2)
> Locale data comes from the CLDR database inside Qt, and is currently not
> customizable.
Then I suppose this should be seen as a deficiency that can to be s
https://bugs.kde.org/show_bug.cgi?id=428663
--- Comment #1 from Shmerl ---
I meant there is *no option currently.
--
You are receiving this mail because:
You are watching all bug changes.
https://bugs.kde.org/show_bug.cgi?id=428663
Bug ID: 428663
Summary: Add a way to explicitly configure the order of days of
the week
Product: systemsettings
Version: 5.19.5
Platform: Debian testing
OS: Linux
https://bugs.kde.org/show_bug.cgi?id=387313
--- Comment #74 from Shmerl ---
(In reply to Vlad Zahorodnii from comment #73)
> It might be some other subsurface-related issue.
Should I open another bug and do you need any data to narrow this down? You can
try reproducing it, it happens pre
https://bugs.kde.org/show_bug.cgi?id=387313
--- Comment #72 from Shmerl ---
(In reply to Shmerl from comment #71)
> So now I have 5.19.3, so I tried Plasma session again. Kmail still behaves
I meant Wayland session. I'm back to X11 for now, since Kmail was practically
unusable.
--
https://bugs.kde.org/show_bug.cgi?id=387313
--- Comment #71 from Shmerl ---
I finally managed to run newer Plasma on Debian testing using this:
https://www.preining.info/blog/2020/07/kde-plasma-status-update-2020-07-04/
So now I have 5.19.3, so I tried Plasma session again. Kmail still behaves
https://bugs.kde.org/show_bug.cgi?id=246196
Shmerl changed:
What|Removed |Added
CC||shtetl...@gmail.com
--- Comment #18 from Shmerl
https://bugs.kde.org/show_bug.cgi?id=419242
--- Comment #22 from Shmerl ---
Or kwin doesn't work correctly. What can be the problem then if it's not kwin?
--
You are receiving this mail because:
You are watching all bug changes.
https://bugs.kde.org/show_bug.cgi?id=419242
--- Comment #20 from Shmerl ---
So, can anything be done about it? Can you please collaborate with AMD
developers on this somehow?
This IS a bug, because in practice, the session doesn't recover. If the reason
lies in the radeonsi bugs, then they have
https://bugs.kde.org/show_bug.cgi?id=419242
--- Comment #19 from Shmerl ---
The bottom line is, for the end user this is not working as it should.
--
You are receiving this mail because:
You are watching all bug changes.
https://bugs.kde.org/show_bug.cgi?id=419242
--- Comment #18 from Shmerl ---
> There is no indication of this being a kwin bug at this time.
According to AMD developers, KWin is likely not using OpenGL robustness
extensions correctly, since GPU reset should be supported properly in the
ker
https://bugs.kde.org/show_bug.cgi?id=419353
--- Comment #3 from Shmerl ---
Waiting for Debian to upload Plasma 5.18.x. It can take a long while.
--
You are receiving this mail because:
You are watching all bug changes.
https://bugs.kde.org/show_bug.cgi?id=419353
Bug ID: 419353
Summary: System load viewer can't handle 24 cores
Product: kdeplasma-addons
Version: 5.17.5
Platform: Debian testing
OS: Linux
Status: REPORTED
https://bugs.kde.org/show_bug.cgi?id=419242
--- Comment #15 from Shmerl ---
I can try triggering GPU reset explicitly for a test to see how kwin reacts.
--
You are receiving this mail because:
You are watching all bug changes.
https://bugs.kde.org/show_bug.cgi?id=419242
--- Comment #14 from Shmerl ---
According to AMD developers:
> The kernel driver and mesa support the necessary OpenGL robustness extensions
> to enable this functionality. I'm not familiar with kwin's implementation
> however.
So ther
https://bugs.kde.org/show_bug.cgi?id=419242
--- Comment #13 from Shmerl ---
Or more exactly: https://gitlab.freedesktop.org/drm/amd/issues/892
--
You are receiving this mail because:
You are watching all bug changes.
https://bugs.kde.org/show_bug.cgi?id=419242
Shmerl changed:
What|Removed |Added
Resolution|NOT A BUG |WAITINGFORINFO
--- Comment #12 from Shmerl
https://bugs.kde.org/show_bug.cgi?id=419242
--- Comment #10 from Shmerl ---
OK, just got another hang and reset. Desktop became garbled, with some
reactions to input.
I switched to tty, and run:
DISPLAY=:0 kwin_x11 --replace
That started, and showed various OpenGL info about the system
https://bugs.kde.org/show_bug.cgi?id=419242
--- Comment #9 from Shmerl ---
Oh, I missed one preceding dmesg part:
[16340.923960] [drm:amdgpu_dm_atomic_commit_tail [amdgpu]] *ERROR* Waiting
for fences timed out!
[16345.787744] [drm:amdgpu_job_timedout [amdgpu]] *ERROR* ring gfx_0.0.0
https://bugs.kde.org/show_bug.cgi?id=419242
--- Comment #8 from Shmerl ---
OK, it happened again, and I can tell it was a reset, since I see it in dmesg
(see below).
The session got corrupted again, but was reacting on some garbled fashion to
input like before.
I switched to tty, and run
https://bugs.kde.org/show_bug.cgi?id=419242
--- Comment #7 from Shmerl ---
It reacted in as something was happening on the screen due to Alt+F2, but it
was garbled.
> kwin_x11 --replace
Thanks, I'll give it a try.
--
You are receiving this mail because:
You are watching all bug changes.
https://bugs.kde.org/show_bug.cgi?id=419242
--- Comment #5 from Shmerl ---
Also, when reset happens, there is a brief period when everything is completely
frozen, and then it starts reacting on input again, and this what happened
here.
It even reacted on me opening krunner with Alt+F2, but all
https://bugs.kde.org/show_bug.cgi?id=419242
--- Comment #4 from Shmerl ---
(In reply to David Edmundson from comment #3)
> >The driver reset it,
>
> How do you know?
>
> Did a restart of kwin_x11 fix it?
Because it didn't cause a hard hang, like it used to before amdgpu
https://bugs.kde.org/show_bug.cgi?id=419242
Shmerl changed:
What|Removed |Added
Summary|Support robust recovery |KWin doesn't recover after
|from
https://bugs.kde.org/show_bug.cgi?id=419242
--- Comment #2 from Shmerl ---
(In reply to David Edmundson from comment #1)
> We read glGetGraphicsResetStatus and reset appropriately.
>
> If you have any more specific information please provide it and reopen the
> report.
https://bugs.kde.org/show_bug.cgi?id=419242
Shmerl changed:
What|Removed |Added
Status|RESOLVED|REOPENED
Ever confirmed|0
https://bugs.kde.org/show_bug.cgi?id=419242
Bug ID: 419242
Summary: Support robust recovery from GPU reset in KWin
Product: kwin
Version: unspecified
Platform: unspecified
OS: Linux
Status: REPORTED
https://bugs.kde.org/show_bug.cgi?id=389962
--- Comment #17 from Shmerl ---
Updated my workaround script that downloads astronomy picture of the day:
https://gist.github.com/shmerl/7465989937cddeb9539db3803ba3feb8
Pair it with local user systemd timer or crontab entry that calls that script
https://bugs.kde.org/show_bug.cgi?id=411542
--- Comment #6 from Shmerl ---
Just confirming that it works. I just built 5.5-rc1 and can observe nvme
temperature in ksysguard!
--
You are receiving this mail because:
You are watching all bug changes.
https://bugs.kde.org/show_bug.cgi?id=195074
--- Comment #9 from Shmerl ---
And if you really think the majority is using such old KDE4 applications, and
only minority is not, you can make the opposite - by default it will be
enabled, and those who don't want to clutter $HOME can opt out
https://bugs.kde.org/show_bug.cgi?id=195074
--- Comment #8 from Shmerl ---
(In reply to Nate Graham from comment #7)
> Bug 405750 cannot be fixed because then it would break the remaining KDE4
> apps that some people are still using (believe it or not). Once nobody is
> using any KDE4
https://bugs.kde.org/show_bug.cgi?id=195074
--- Comment #6 from Shmerl ---
(In reply to Nate Graham from comment #5)
> Bug 405750 is the cause, and the issue here has been fixed in Frameworks 5.
I meant I was wondering, why there is some resistance to fix #405750 for good.
Or you mean that
https://bugs.kde.org/show_bug.cgi?id=411542
--- Comment #4 from Shmerl ---
(In reply to Nate Graham from comment #3)
> So there are no changes needed in KSysGuard to gain this feature once it's
> in the kernel?
I think so. I'll build 5.5-rc1 once and will come out, and will give it
https://bugs.kde.org/show_bug.cgi?id=414811
--- Comment #5 from Shmerl ---
(In reply to Kai Uwe Broulik from comment #4)
> It is a standard :)
>
> https://developer.mozilla.org/en-US/docs/Web/API/Media_Session_API
> https://w3c.github.io/mediasession/
Great! I'll ping Ba
https://bugs.kde.org/show_bug.cgi?id=414811
--- Comment #3 from Shmerl ---
(In reply to Kai Uwe Broulik from comment #2)
> This extension doesn't do any site-specific code. The website would need to
> register a callback like so:
>
> if (navigator.
https://bugs.kde.org/show_bug.cgi?id=414811
--- Comment #1 from Shmerl ---
Example to test:
https://ryanike.bandcamp.com/album/west-of-loathing-original-game-soundtrack
--
You are receiving this mail because:
You are watching all bug changes.
https://bugs.kde.org/show_bug.cgi?id=411542
--- Comment #2 from Shmerl ---
Looks like NVMe senors are being added to standard hwmon in Linux 5.5, so that
would be supported by ksysguard seamlessly.
--
You are receiving this mail because:
You are watching all bug changes.
https://bugs.kde.org/show_bug.cgi?id=414811
Bug ID: 414811
Summary: Plasma browser integration playlist controls aren't
working on Bandcamp
Product: plasma-browser-integration
Version: unspecified
Platform: Debian testing
https://bugs.kde.org/show_bug.cgi?id=413719
Bug ID: 413719
Summary: Please implement Vulkan rendering in KWin
Product: kwin
Version: unspecified
Platform: Other
OS: Linux
Status: REPORTED
Severity: normal
https://bugs.kde.org/show_bug.cgi?id=195074
--- Comment #4 from Shmerl ---
(In reply to Erik Quaeghebeur from comment #3)
> (In reply to Shmerl from comment #2)
> > But something still creates $HOME/.kde/config/kdeglobals for me (it's the
> > only file remaining there now).
&
https://bugs.kde.org/show_bug.cgi?id=405750
--- Comment #14 from Shmerl ---
For XDG support you can see the specification itself:
https://specifications.freedesktop.org/basedir-spec/basedir-spec-latest.html
In fact, KDE project is behind it too, so it's a bit surprising that still
needs
https://bugs.kde.org/show_bug.cgi?id=405750
Shmerl changed:
What|Removed |Added
CC||shtetl...@gmail.com
--- Comment #13 from Shmerl
https://bugs.kde.org/show_bug.cgi?id=195074
Shmerl changed:
What|Removed |Added
CC||shtetl...@gmail.com
--- Comment #2 from Shmerl
https://bugs.kde.org/show_bug.cgi?id=411542
--- Comment #1 from Shmerl ---
Some idea how to do it here:
https://github.com/linux-nvme/nvme-cli/blob/master/nvme.c#L168
https://github.com/linux-nvme/nvme-cli/blob/master/nvme-ioctl.c
--
You are receiving this mail because:
You are watching all
https://bugs.kde.org/show_bug.cgi?id=411542
Bug ID: 411542
Summary: Add ability to display nvme drives temperature
Product: ksysguard
Version: 5.14.5
Platform: unspecified
OS: Linux
Status: REPORTED
https://bugs.kde.org/show_bug.cgi?id=43
--- Comment #2 from Shmerl ---
(In reply to Nate Graham from comment #1)
> There already are keyboard shortcuts: ctrl+shift+arrow keys.
>
> This feature is a bit hidden in the shortcuts dialog. But the feature is
> implemented and does wo
https://bugs.kde.org/show_bug.cgi?id=43
Bug ID: 43
Summary: Please add keyboard shortcuts for navigating between
konsole splits
Product: konsole
Version: 19.08.0
Platform: unspecified
OS: Linux
https://bugs.kde.org/show_bug.cgi?id=405912
--- Comment #11 from Shmerl ---
(In reply to oiaohm from comment #9)
>
> Again that path does not have required sync functionality in wayland.
>
Consensus is that it should be a Wayland protocol extension (see linked Wayland
bug). That
https://bugs.kde.org/show_bug.cgi?id=178320
--- Comment #49 from Shmerl ---
Is this included in 19.04.3?
--
You are receiving this mail because:
You are watching all bug changes.
https://bugs.kde.org/show_bug.cgi?id=402206
--- Comment #5 from Shmerl ---
Comment by Jan Horak:
https://bugzilla.mozilla.org/show_bug.cgi?id=1516290#c9
> Setting GTK_USER_PORTAL=1 to get KDE native dialog is generally not a good
> idea. The GTK_USER_PORTAL variable is used to
https://bugs.kde.org/show_bug.cgi?id=387313
--- Comment #63 from Shmerl ---
Is there any progress beyond the proposed approach?
--
You are receiving this mail because:
You are watching all bug changes.
https://bugs.kde.org/show_bug.cgi?id=405912
--- Comment #10 from Shmerl ---
There should be a use case of not using EGL. Not sure why it has to be required
if you say that Wayland doesn't need to care about platform specifics. If you
think EGL is required because Vulkan / WSI didn't exist
https://bugs.kde.org/show_bug.cgi?id=405912
--- Comment #8 from Shmerl ---
Wayland applications aren't supposed to be restricted to EGL. They can use WSI
too (VK_USE_PLATFORM_WAYLAND_KHR and etc.).
--
You are receiving this mail because:
You are watching all bug changes.
https://bugs.kde.org/show_bug.cgi?id=407113
Bug ID: 407113
Summary: Allow assigning aliases to sensor names
Product: ksysguard
Version: 5.14.5
Platform: Debian testing
OS: Linux
Status: REPORTED
Severity:
https://bugs.kde.org/show_bug.cgi?id=405912
--- Comment #6 from Shmerl ---
Related Wayland issue:
https://gitlab.freedesktop.org/wayland/wayland/issues/84#note_136147
In short, it requires new Wayland protocol extension first.
--
You are receiving this mail because:
You are watching all bug
https://bugs.kde.org/show_bug.cgi?id=405912
--- Comment #3 from Shmerl ---
Just in case, this can be helpful:
https://www.amd.com/en/products/freesync-monitors
--
You are receiving this mail because:
You are watching all bug changes.
https://bugs.kde.org/show_bug.cgi?id=405912
--- Comment #2 from Shmerl ---
(In reply to Martin Flöser from comment #1)
>
> Obvious problem: this requires (expensive) hardware.
>
Do you mean monitors or GPUs? VRR is supported by low end GPUs as well. As for
monitors, you can find 192
https://bugs.kde.org/show_bug.cgi?id=405912
Bug ID: 405912
Summary: Add support for adaptive sync (FreeSync) in KWin for
Wayland and X sessions
Product: kwin
Version: unspecified
Platform: Other
OS: Linux
https://bugs.kde.org/show_bug.cgi?id=387313
--- Comment #58 from Shmerl ---
Well, if it requires changing some taken approaches, that's redesign already.
--
You are receiving this mail because:
You are watching all bug changes.
https://bugs.kde.org/show_bug.cgi?id=387313
--- Comment #56 from Shmerl ---
(In reply to Martin Flöser from comment #55)
> See comment #42
Does it require KWin redesign in some way, or the fix is just not trivial?
--
You are receiving this mail because:
You are watching all bug changes.
https://bugs.kde.org/show_bug.cgi?id=387313
--- Comment #54 from Shmerl ---
(In reply to Vlad Zagorodniy from comment #47)
>
> I picked wrong verb. There is no currently any fix.
Is it clear what needs fixing though or how to fix it, or so far it's not even
known?
--
You are rec
https://bugs.kde.org/show_bug.cgi?id=403752
--- Comment #3 from Shmerl ---
lsof also shows, that kmail holds these files in $HOME/.pki/nssdb open while
running: cert9.db key4.db
--
You are receiving this mail because:
You are watching all bug changes.
https://bugs.kde.org/show_bug.cgi?id=403752
--- Comment #2 from Shmerl ---
I'll try to narrow it down to some dependency, but it's certainly being created
when Kmail starts.
--
You are receiving this mail because:
You are watching all bug changes.
https://bugs.kde.org/show_bug.cgi?id=403752
Bug ID: 403752
Summary: Support XDG base directory specification when using
libnss
Product: kmail2
Version: 5.9.1
Platform: Debian testing
OS: Linux
https://bugs.kde.org/show_bug.cgi?id=387313
--- Comment #49 from Shmerl ---
(In reply to Rainer Finke from comment #48)
> Thanks for your answer! Ok, this explains than why I got a flickering when
> kmail is open as a non maximized window and I open kate as well as a non
> maximiz
101 - 200 of 291 matches
Mail list logo
