https://bugs.kde.org/show_bug.cgi?id=449772
Bug ID: 449772
Summary: Can't set volume above 100% for individual application
stream through the audio volume applet
Product: plasma-pa
Version: 5.23.5
Platform: Debian testing
https://bugs.kde.org/show_bug.cgi?id=449772
--- Comment #1 from Shmerl ---
Created attachment 146422
--> https://bugs.kde.org/attachment.cgi?id=146422&action=edit
Volume raised to 150% for the single Cyberpunk 2077 stream as shown by the
applet.
--
You are receiving this mail becau
https://bugs.kde.org/show_bug.cgi?id=449772
--- Comment #2 from Shmerl ---
Created attachment 146423
--> https://bugs.kde.org/attachment.cgi?id=146423&action=edit
Volume raised to 150% for the single Cyberpunk 2077 stream with pavucontrol
--
You are receiving this mail because:
https://bugs.kde.org/show_bug.cgi?id=450679
Bug ID: 450679
Summary: Kwin Wayland session hangs when monitor is turned off
/ goes to sleep.
Product: kwin
Version: 5.24.1
Platform: Debian testing
OS: Linux
https://bugs.kde.org/show_bug.cgi?id=450679
--- Comment #1 from Shmerl ---
Some additional details:
Mouse cursor is movable in that hang up session. So it's not some hard hang
like GPU one. Even the password prompt window can be moved. But keyboard input
in it doesn't work. Switching
https://bugs.kde.org/show_bug.cgi?id=448275
--- Comment #11 from Shmerl ---
Looks like Debian unstable / testing is *finally* getting newer Qt, so this
nasty bug will hopefully be fixed:
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1007170
--
You are receiving this mail because:
You are
https://bugs.kde.org/show_bug.cgi?id=463134
--- Comment #3 from Shmerl ---
Still happens in 5.26.90.
--
You are receiving this mail because:
You are watching all bug changes.
https://bugs.kde.org/show_bug.cgi?id=463134
Shmerl changed:
What|Removed |Added
Version|5.26.5 |5.26.90
--
You are receiving this mail because:
You
https://bugs.kde.org/show_bug.cgi?id=466041
Shmerl changed:
What|Removed |Added
CC||shtetl...@gmail.com
--- Comment #4 from Shmerl
https://bugs.kde.org/show_bug.cgi?id=466041
--- Comment #5 from Shmerl ---
Btw, the problem didn't exist for me, until upgrade to newer frameworks
happened (5.102 → 5.103). So it might be a regression in the new one.
--
You are receiving this mail because:
You are watching all bug changes.
https://bugs.kde.org/show_bug.cgi?id=456697
Shmerl changed:
What|Removed |Added
CC||shtetl...@gmail.com
--- Comment #4 from Shmerl
https://bugs.kde.org/show_bug.cgi?id=463134
Shmerl changed:
What|Removed |Added
Version|5.26.90 |5.27.2
--- Comment #4 from Shmerl ---
Still happens
https://bugs.kde.org/show_bug.cgi?id=463134
--- Comment #5 from Shmerl ---
Related: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1027831
--
You are receiving this mail because:
You are watching all bug changes.
https://bugs.kde.org/show_bug.cgi?id=463134
--- Comment #6 from Shmerl ---
Just tested, libpackagekitqt5-1 1.1.1 fixes it for me on Debian.
--
You are receiving this mail because:
You are watching all bug changes.
https://bugs.kde.org/show_bug.cgi?id=459345
Bug ID: 459345
Summary: Add width to the plasma-nm applet interface to
accommodate IPv6 addresses
Classification: Unclassified
Product: plasma-nm
Version: 5.25.5
Platform: Oth
https://bugs.kde.org/show_bug.cgi?id=460403
--- Comment #9 from Shmerl ---
Just FYI, this still happens with 5.27.3. Didn't test 5.27.4 since it's not in
Debian yet.
--
You are receiving this mail because:
You are watching all bug changes.
https://bugs.kde.org/show_bug.cgi?id=460403
Shmerl changed:
What|Removed |Added
Version|5.24.5 |5.27.3
--
You are receiving this mail because:
You
https://bugs.kde.org/show_bug.cgi?id=405750
--- Comment #15 from Shmerl ---
For what it's worth, looks like $HOME/.kde isn't being created anymore (even
with current plasma before Qt 6 usage). Hooray!
--
You are receiving this mail because:
You are watching all bug changes.
https://bugs.kde.org/show_bug.cgi?id=452565
--- Comment #1 from Shmerl ---
Any news on this?
--
You are receiving this mail because:
You are watching all bug changes.
https://bugs.kde.org/show_bug.cgi?id=403752
--- Comment #5 from Shmerl ---
I think I found the culprit:
apt depends kmail | rg libqt5webengine
Depends: libqt5webenginecore5 (>= 5.15.2~)
apt depends libqt5webenginecore5 | rg libnss
Depends: libnss3 (>= 2:3.22)
I can look into Qt Web
https://bugs.kde.org/show_bug.cgi?id=403752
--- Comment #6 from Shmerl ---
Hmm, since Qt Web Engine seems to be using Chromium, this might be the upstream
bug:
https://bugs.chromium.org/p/chromium/issues/detail?id=1038587
--
You are receiving this mail because:
You are watching all bug
https://bugs.kde.org/show_bug.cgi?id=442839
--- Comment #22 from Shmerl ---
And why would root's settings affect user session even in XWayland case? There
is clearly some kind of misconfig / disconnect of expectations here.
--
You are receiving this mail because:
You are watching al
https://bugs.kde.org/show_bug.cgi?id=460403
Bug ID: 460403
Summary: Task switcher is ignoring the icon set in the
.desktop launcher and associated with the application
through StartupWMClass
Classification: Plasma
Produ
https://bugs.kde.org/show_bug.cgi?id=460403
--- Comment #1 from Shmerl ---
Here is how you can test it.
Create test.sh file like this: (let's say you place it in your
$HOME/tmp/test.sh).
#!/bin/bash
kdialog --msgbox "Test!"
Then create a test.desktop (in $HOME file like this
https://bugs.kde.org/show_bug.cgi?id=460403
--- Comment #2 from Shmerl ---
I meant you should create test.desktop in $HOME/.local/share/applications
--
You are receiving this mail because:
You are watching all bug changes.
https://bugs.kde.org/show_bug.cgi?id=460403
--- Comment #6 from Shmerl ---
Making it dependent on the application only removes the ability to set custom
icons which otherwise are possible with StartupWMClass. So I think flexibility
of that is valuable.
--
You are receiving this mail because
https://bugs.kde.org/show_bug.cgi?id=463475
--- Comment #9 from Shmerl ---
Looks like after Qt 5.15.8 this bug is gone. I'll keep watching if it happens
and after a while not, I can close this.
--
You are receiving this mail because:
You are watching all bug changes.
https://bugs.kde.org/show_bug.cgi?id=456187
--- Comment #4 from Shmerl ---
The use case was already described. To see shared libraries of a running
process. Not sure what exactly needs clarification, but here are some examples:
1. You have a running game want to check what libraries it uses
https://bugs.kde.org/show_bug.cgi?id=463475
--- Comment #11 from Shmerl ---
(In reply to Lukas Bergdoll from comment #10)
> I have the same issue, it keeps crashing it always crashes in
> TerminalDisplay.cpp:3165 `log2line[i] = pos;`. Disabling bidi did not help,
> nor did rollin
https://bugs.kde.org/show_bug.cgi?id=463134
--- Comment #2 from Shmerl ---
Any news on this? I think it can be seen as confirmed.
--
You are receiving this mail because:
You are watching all bug changes.
https://bugs.kde.org/show_bug.cgi?id=456187
Shmerl changed:
What|Removed |Added
Resolution|WAITINGFORINFO |---
Status|NEEDSINFO
https://bugs.kde.org/show_bug.cgi?id=372116
Shmerl changed:
What|Removed |Added
CC||n...@kde.org
--- Comment #46 from Shmerl ---
Can
https://bugs.kde.org/show_bug.cgi?id=372116
--- Comment #49 from Shmerl ---
I agree about being able to paste already. I actually don't want to have a
paste functionality with osc52. I only care about copy. So it's a good starting
point even if you do want to have it as an extra fea
https://bugs.kde.org/show_bug.cgi?id=372116
--- Comment #50 from Shmerl ---
I'd say implementing copy over osc52 will cover 99.9% of all needed use cases.
You can make it configurable if you want to, but it's not a deal breaker if
it's available by default I think.
--
You are
https://bugs.kde.org/show_bug.cgi?id=372116
--- Comment #52 from Shmerl ---
There is no reason why this can't be added in stages, first copy and then paste
with security controls for it. So it's not a a blocker not to merge current
accumulated progress.
--
You are receiving this ma
https://bugs.kde.org/show_bug.cgi?id=456187
--- Comment #10 from Shmerl ---
(In reply to Arjen Hiemstra from comment #9)
> This is now in progress as a separate application, which allows for a better
> UI to be developed for detailed process inspection, see
> https://redstrate.com/blo
https://bugs.kde.org/show_bug.cgi?id=372116
--- Comment #32 from Shmerl ---
I would appreciate some update on this too. Is there some way to help with
this? What has to be implemented / improved for this to work? Something about
kosnole buffer?
--
You are receiving this mail because:
You are
https://bugs.kde.org/show_bug.cgi?id=372116
--- Comment #33 from Shmerl ---
Apparently some downstream distros are working around this by changing the
buffer size:
-#define MAX_TOKEN_LENGTH 256 // Max length of tokens (e.g. window title)
+#define MAX_TOKEN_LENGTH 65536 // Max length of tokens
https://bugs.kde.org/show_bug.cgi?id=372116
--- Comment #35 from Shmerl ---
Well, I see it being used at least in a few places in the code:
```
src/Vt102Emulation.cpp:322:tokenBufferPos = qMin(tokenBufferPos,
MAX_TOKEN_LENGTH - 1);
src/Vt102Emulation.h:127:#define MAX_TOKEN_LENGTH 256
https://bugs.kde.org/show_bug.cgi?id=372116
--- Comment #36 from Shmerl ---
It's definitely helping! I was able to copy 27,637 bytes now when testing
copying some random text, unlike without the patch.
--
You are receiving this mail because:
You are watching all bug changes.
https://bugs.kde.org/show_bug.cgi?id=372116
--- Comment #37 from Shmerl ---
So I'd say it's worth looking into that, or even making this buffer dynamic
when you need to handle osc52 altogether and set some limits which are defined
separately.
--
You are receiving this mail becaus
https://bugs.kde.org/show_bug.cgi?id=372116
--- Comment #39 from Shmerl ---
(In reply to Christian Muehlhaeuser from comment #38)
> (In reply to Shmerl from comment #35)
> > Well, I see it being used at least in a few places in the code:
> >
> > ```
> >
https://bugs.kde.org/show_bug.cgi?id=372116
--- Comment #40 from Shmerl ---
> tokenBuffer now gets resized to fit the content
If that's the case - then great! May be your patch will just work then.
--
You are receiving this mail because:
You are watching all bug changes.
https://bugs.kde.org/show_bug.cgi?id=372116
--- Comment #41 from Shmerl ---
I'll check if I can backport those recent commits and your osc52 patch to the
older konsole in Debian testing, to be able to use that before it's updated
there:
*
https://invent.kde.org/utilities/konsole
https://bugs.kde.org/show_bug.cgi?id=372116
--- Comment #42 from Shmerl ---
That didn't work unfortunately due it using some unavailable Qt functionality
for that version.
--
You are receiving this mail because:
You are watching all bug changes.
https://bugs.kde.org/show_bug.cgi?id=372116
--- Comment #43 from Shmerl ---
Any luck with testing your patch against latest codebase? It would be good to
merge it if it works as intended with resizable buffers.
--
You are receiving this mail because:
You are watching all bug changes.
https://bugs.kde.org/show_bug.cgi?id=372116
--- Comment #45 from Shmerl ---
(In reply to Anthony Wang from comment #44)
> I'm the maintainer of the konsole-osc52 AUR package and I can confirm that
> the patch
> (https://aur.archlinux.org/cgit/aur.git/tree/osc52.patch?h=konsole-osc5
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 #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 #34 from Shmerl ---
(In reply to Maciej Stanczew from comment #33)
> For anyone who just wants to get rid of filtering and use the hardware
> sensors directly, there is a simple blacklist in ksystemstats code
Thanks!
--
You are rec
https://bugs.kde.org/show_bug.cgi?id=450679
--- Comment #6 from Shmerl ---
It's probably a duplicate of bug #448275.
--
You are receiving this mail because:
You are watching all bug changes.
https://bugs.kde.org/show_bug.cgi?id=424836
Shmerl changed:
What|Removed |Added
CC||shtetl...@gmail.com
--- Comment #1 from Shmerl ---
I
https://bugs.kde.org/show_bug.cgi?id=424836
Shmerl changed:
What|Removed |Added
Version|5.19.3 |5.24.3
--
You are receiving this mail because:
You
https://bugs.kde.org/show_bug.cgi?id=452565
Bug ID: 452565
Summary: Akonadi is creating "Unknown Organization" in
$HOME/.config
Product: Akonadi
Version: unspecified
Platform: Debian testing
OS: Linux
https://bugs.kde.org/show_bug.cgi?id=450679
--- Comment #5 from Shmerl ---
Some additional details on this. I ran a few tests with Plasma 5.24.4 in the
Wayland session, and observed the following:
1. When monitor is turned off and turned back on, session doesn't die, but all
Qt applic
https://bugs.kde.org/show_bug.cgi?id=450679
Shmerl changed:
What|Removed |Added
Version|5.24.3 |5.24.4
--
You are receiving this mail because:
You
https://bugs.kde.org/show_bug.cgi?id=450679
Shmerl changed:
What|Removed |Added
Summary|Kwin Wayland session hangs |Qt applications in Kwin
|when
https://bugs.kde.org/show_bug.cgi?id=448275
--- Comment #12 from Shmerl ---
Debian testing finally after a huge wait got a newer Qt (5.15.4) and this bug
is gone!
--
You are receiving this mail because:
You are watching all bug changes.
https://bugs.kde.org/show_bug.cgi?id=455900
Shmerl changed:
What|Removed |Added
CC||shtetl...@gmail.com
--- Comment #1 from Shmerl ---
I
https://bugs.kde.org/show_bug.cgi?id=455900
--- Comment #2 from Shmerl ---
I enabled systemd boot for KDE in the past if that makes a difference.
--
You are receiving this mail because:
You are watching all bug changes.
https://bugs.kde.org/show_bug.cgi?id=442839
Shmerl changed:
What|Removed |Added
CC||shtetl...@gmail.com
--- Comment #15 from Shmerl
https://bugs.kde.org/show_bug.cgi?id=451822
Shmerl changed:
What|Removed |Added
CC||shtetl...@gmail.com
--- Comment #2 from Shmerl
https://bugs.kde.org/show_bug.cgi?id=393842
Shmerl changed:
What|Removed |Added
CC||shtetl...@gmail.com
--- Comment #5 from Shmerl
https://bugs.kde.org/show_bug.cgi?id=455900
--- Comment #4 from Shmerl ---
(In reply to John E from comment #3)
>
> What do you mean by that so I can confirm if I've done that as well.
See: https://blog.davidedmundson.co.uk/blog/plasma-and-the-systemd-startup/
--
You are receivin
https://bugs.kde.org/show_bug.cgi?id=436318
Shmerl changed:
What|Removed |Added
CC||shtetl...@gmail.com
--- Comment #10 from Shmerl
https://bugs.kde.org/show_bug.cgi?id=456187
Bug ID: 456187
Summary: Add ability to see loaded shared libraries and other
detailed information for a process to system monitor
Product: plasma-systemmonitor
Version: 5.25.1
Pla
https://bugs.kde.org/show_bug.cgi?id=450679
Shmerl changed:
What|Removed |Added
Version|5.24.1 |5.24.2
--
You are receiving this mail because:
You
https://bugs.kde.org/show_bug.cgi?id=450679
--- Comment #3 from Shmerl ---
Still happens in 5.24.3.
After the hang the desktop is sometimes responsive (like plasmashell is
operational). But part of the open windows are frozen.
--
You are receiving this mail because:
You are watching all bug
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=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=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
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=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=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 on
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 #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 #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=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
>
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=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
--- 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
It mi
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,
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 #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
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 notic
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 #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=424754
Shmerl changed:
What|Removed |Added
CC||shtetl...@gmail.com
--- Comment #38 from Shmerl
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 beca
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 #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
--- 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=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 #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=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
> sensors because
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 se
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: L
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
Shmerl changed:
What|Removed |Added
Summary|Don't filter out amdgpu |Don't filter out amdgpu
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
1 - 100 of 329 matches
Mail list logo
