[plasma-pa] [Bug 449772] New: Can't set volume above 100% for individual application stream through the audio volume applet
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 OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: applet Assignee: plasma-b...@kde.org Reporter: shtetl...@gmail.com CC: m...@ratijas.tk, now...@gmail.com Target Milestone: --- This is mostly reiterating bug #422792 but opening a new bug for better visibility since the other one is closed. The problem is inability to raise volume above 100% for individual application stream through the audio volume applet UI. You can see that technically it supports such feature by raising it for example through pavucontrol (see attached screenshots). And it stays at 100% for the audio device while showing 150% for the stream, so it totally can do it for a single application stream. The are valid use cases for such feature. For example, I'm running Cyberpunk 2077 (Wine) and it uses two audio streams, one for sound effects and one for music. When in PulseAudio prefix config, music stream for some reason has low volume. I can raise it with pavucontrol to 150% which makes it sound better. And the applet reflects it nicely. But I can't raise it through the applet itself. Please fix it to allow doing it for the single stream through the applet UI, avoiding using pavucontrol or going through the long steps sequence like this: click on audio volume icon > click on sandwich menu icon (More actions) > Configure audio devices > Playback Streams. -- You are receiving this mail because: You are watching all bug changes.
[plasma-pa] [Bug 449772] Can't set volume above 100% for individual application stream through the audio volume applet
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 because: You are watching all bug changes.
[plasma-pa] [Bug 449772] Can't set volume above 100% for individual application stream through the audio volume applet
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: You are watching all bug changes.
[kwin] [Bug 450679] New: Kwin Wayland session hangs when monitor is turned off / goes to sleep.
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 Status: REPORTED Severity: normal Priority: NOR Component: wayland-generic Assignee: kwin-bugs-n...@kde.org Reporter: shtetl...@gmail.com Target Milestone: --- There is a persistent bug that causes Wayland session to hang when monitor is explicitly turned off or goes to sleep. After turning it back on it's possible to go into tty and check what's going on, so I collected some gdb logs. When testing (turning it off), the only shown window on the desktop was kwalletd5 password prompt. What can be observed at that moment is that kwin_wayland and kwalletd5 both eat a lot of CPU: kwin_wayland backtrace: #0 0x7f100a14fe6d in recvmsg () from /lib/x86_64-linux-gnu/libpthread.so.0 #1 0x7f100aebc575 in ?? () from /lib/x86_64-linux-gnu/libxcb.so.1 #2 0x7f100aebd068 in ?? () from /lib/x86_64-linux-gnu/libxcb.so.1 #3 0x55c306f54300 in KWin::Xwl::Xwayland::dispatchEvents (this=0x55c307b20b60) at ./src/xwl/xwayland.cpp:302 #4 0x7f100a575183 in ?? () from /lib/x86_64-linux-gnu/libQt5Core.so.5 #5 0x7f100a593666 in QEventDispatcherUNIX::processEvents(QFlags) () from /lib/x86_64-linux-gnu/libQt5Core.so.5 #6 0x55c30703851d in QUnixEventDispatcherQPA::processEvents(QFlags) () #7 0x7f100a53d52b in QEventLoop::exec(QFlags) () from /lib/x86_64-linux-gnu/libQt5Core.so.5 #8 0x7f100a545800 in QCoreApplication::exec() () from /lib/x86_64-linux-gnu/libQt5Core.so.5 #9 0x55c306f39f73 in main (argc=, argv=) at ./src/main_wayland.cpp:727 quit Detaching from program: /usr/bin/kwin_wayland, process 1580 [Inferior 1 (process 1580) detached] - kwalletd5 backtrace: #0 0x7f18e6d39d61 in ?? () from /lib/x86_64-linux-gnu/libfontconfig.so.1 #1 0x7f18e6d322e2 in ?? () from /lib/x86_64-linux-gnu/libfontconfig.so.1 #2 0x7f18e6d32615 in ?? () from /lib/x86_64-linux-gnu/libfontconfig.so.1 #3 0x7f18e6d329b0 in ?? () from /lib/x86_64-linux-gnu/libfontconfig.so.1 #4 0x7f18e6d32ac9 in ?? () from /lib/x86_64-linux-gnu/libfontconfig.so.1 #5 0x7f18e6d338c2 in FcFontMatch () from /lib/x86_64-linux-gnu/libfontconfig.so.1 #6 0x7f18e8ecf0b6 in ?? () from /lib/x86_64-linux-gnu/libQt5WaylandClient.so.5 #7 0x7f18e8ecf737 in ?? () from /lib/x86_64-linux-gnu/libQt5WaylandClient.so.5 #8 0x7f18eaefafd4 in ?? () from /lib/x86_64-linux-gnu/libQt5Gui.so.5 #9 0x7f18eaefb9e3 in QFontDatabase::findFont(QFontDef const&, int) () from /lib/x86_64-linux-gnu/libQt5Gui.so.5 #10 0x7f18eaee31ba in QFontEngineMulti::loadEngine(int) () from /lib/x86_64-linux-gnu/libQt5Gui.so.5 #11 0x7f18eaee3f07 in QFontEngineMulti::ensureEngineAt(int) () from /lib/x86_64-linux-gnu/libQt5Gui.so.5 #12 0x7f18eaee465b in QFontEngineMulti::stringToCMap(QChar const*, int, QGlyphLayout*, int*, QFlags) const () from /lib/x86_64-linux-gnu/libQt5Gui.so.5 #13 0x7f18eaf0680a in QTextEngine::shapeText(int) const () from /lib/x86_64-linux-gnu/libQt5Gui.so.5 #14 0x7f18eaf187a9 in QTextLine::layout_helper(int) () from /lib/x86_64-linux-gnu/libQt5Gui.so.5 #15 0x7f18eaf60005 in ?? () from /lib/x86_64-linux-gnu/libQt5Gui.so.5 #16 0x7f18eaf61405 in ?? () from /lib/x86_64-linux-gnu/libQt5Gui.so.5 #17 0x7f18eaf69170 in ?? () from /lib/x86_64-linux-gnu/libQt5Gui.so.5 #18 0x7f18eaf6975a in ?? () from /lib/x86_64-linux-gnu/libQt5Gui.so.5 #19 0x7f18eaf69d80 in QTextDocumentLayout::doLayout(int, int, int) () from /lib/x86_64-linux-gnu/libQt5Gui.so.5 #20 0x7f18eaf6b3b9 in QTextDocumentLayout::documentChanged(int, int, int) () from /lib/x86_64-linux-gnu/libQt5Gui.so.5 #21 0x7f18eb645e8b in QLabel::changeEvent(QEvent*) () from /lib/x86_64-linux-gnu/libQt5Widgets.so.5 #22 0x7f18eb548486 in QWidget::event(QEvent*) () from /lib/x86_64-linux-gnu/libQt5Widgets.so.5 #23 0x7f18eb5f490e in QFrame::event(QEvent*) () from /lib/x86_64-linux-gnu/libQt5Widgets.so.5 #24 0x7f18eb5066bf in QApplicationPrivate::notify_helper(QObject*, QEvent*) () from /lib/x86_64-linux-gnu/libQt5Widgets.so.5 #25 0x7f18ea82ab1a in QCoreApplication::notifyInternal2(QObject*, QEvent*) () from /lib/x86_64-linux-gnu/libQt5Core.so.5 #26 0x7f18eb5397d5 in QWidgetPrivate::updateFont(QFont const&) () from /lib/x86_64-linux-gnu/libQt5Widgets.so.5 #27 0x7f18eb548940 in QWidget::event(QEvent*) () from /lib/x86_64-linux-gnu/libQt5Widgets.so.5 #28 0x7f18eb5f490e in QFrame::event(QEvent*) () from /lib/x86_64-linux-gnu/libQt5Widgets.so.5 #29 0x7f18eb5066bf in QApplicationPrivate::notify_helper(QObject*, QEvent*) () from /lib/x86_64-linux-gnu/libQt5Widgets.so.5 #30 0x7f18ea82ab1a in QCoreApplication::notifyInternal2(Q
[kwin] [Bug 450679] Kwin Wayland session hangs when monitor is turned off / goes to sleep.
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 to virtual terminal works. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 448275] All qt apps are freezed/crashed after screen wake up
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 watching all bug changes.
[Discover] [Bug 463134] The Discover panel applet says "System up to date," even if there are available updates.
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.
[Discover] [Bug 463134] The Discover panel applet says "System up to date," even if there are available updates.
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 are watching all bug changes.
[plasmashell] [Bug 466041] Data must be copied twice before being pasted on Wayland when history size is set to 1 entry
https://bugs.kde.org/show_bug.cgi?id=466041 Shmerl changed: What|Removed |Added CC||shtetl...@gmail.com --- Comment #4 from Shmerl --- Just hit the same bug. As a workaround I set the history to 2 entries for now. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 466041] Data must be copied twice before being pasted on Wayland when history size is set to 1 entry
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.
[kwin] [Bug 456697] [Wayland] Please provide a means to specify a custom modeline
https://bugs.kde.org/show_bug.cgi?id=456697 Shmerl changed: What|Removed |Added CC||shtetl...@gmail.com --- Comment #4 from Shmerl --- Any news on this? It would be very useful to work around bugs like this: https://gitlab.freedesktop.org/drm/amd/-/issues/1403 Right now it's impossible in the Wayland session. -- You are receiving this mail because: You are watching all bug changes.
[Discover] [Bug 463134] The Discover panel applet says "System up to date," even if there are available updates.
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 in 5.27.2. -- You are receiving this mail because: You are watching all bug changes.
[Discover] [Bug 463134] The Discover panel applet says "System up to date," even if there are available updates.
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.
[Discover] [Bug 463134] The Discover panel applet says "System up to date," even if there are available updates.
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.
[plasma-nm] [Bug 459345] New: Add width to the plasma-nm applet interface to accommodate IPv6 addresses
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: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: applet Assignee: plasma-b...@kde.org Reporter: shtetl...@gmail.com CC: jgrul...@redhat.com Target Milestone: --- When clicking on plasma-nm applet in the notification area, it opens a relatively small rectangular window around that area. Selecting a connection and Details tab in it shows various details about IP addresses. It works OK for IPv4, but IPv6 addresses are quite longer and they are truncated there without any way to see them fully from that interface. May be use wider window to begin with or detect that IPv6 information is needed and increase it on demand? There is no way to resize that applet interface manually either, which could be another workaround. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 460403] Task switcher is ignoring the icon set in the .desktop launcher and associated with the application through StartupWMClass
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.
[kwin] [Bug 460403] Task switcher is ignoring the icon set in the .desktop launcher and associated with the application through StartupWMClass
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 are watching all bug changes.
[plasmashell] [Bug 405750] Why is .kde4/share/config/kdeglobals still being created?
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.
[Akonadi] [Bug 452565] Akonadi is creating "Unknown Organization" in $HOME/.config
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.
[kmail2] [Bug 403752] Support XDG base directory specification when using libnss
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 Engine and how it uses libnss and file a bug there. -- You are receiving this mail because: You are watching all bug changes.
[kmail2] [Bug 403752] Support XDG base directory specification when using libnss
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 changes.
[kwin] [Bug 442839] [wayland] mouse cursor changes away from the theme cursor to adwaita
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 all bug changes.
[kwin] [Bug 460403] New: Task switcher is ignoring the icon set in the .desktop launcher and associated with the application through StartupWMClass
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 Product: kwin Version: 5.24.5 Platform: Debian testing OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: tabbox Assignee: kwin-bugs-n...@kde.org Reporter: shtetl...@gmail.com Target Milestone: --- When some custom .desktop file sets StartupWMClass for its application and also sets an icon file for it, Task Switcher isn't picking up that association and on Wayland for example is using a generic Wayland icon. I tested it with Breeze and Cover Switch task switchers, both demonstrated this problem. In comparison, Task Manager does read it correctly and sets the icon properly accordingly, so something isn't done right with task switchers in particular. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 460403] Task switcher is ignoring the icon set in the .desktop launcher and associated with the application through StartupWMClass
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, assuming your user is named foobar and assuming this icon is present on your system: /usr/share/icons/breeze/status/64/dialog-error.svg): [Desktop Entry] Encoding=UTF-8 Value=1.0 Type=Application Name=Test 1 GenericName=Test 1 Comment=Test 1 Icon=/usr/share/icons/breeze/status/64/dialog-error.svg StartupWMClass=org.kde.kdialog Exec="/home/foobar/tmp/test.sh" Then run kbuildsycoca5 to update your launchers and icons cache. Start Test 1 from the launcher (like with krunner or etc.) and observe that Error icon is displayed in Task Manager, but not in Task Switcher. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 460403] Task switcher is ignoring the icon set in the .desktop launcher and associated with the application through StartupWMClass
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.
[kwin] [Bug 460403] Task switcher is ignoring the icon set in the .desktop launcher and associated with the application through StartupWMClass
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: You are watching all bug changes.
[konsole] [Bug 463475] Konsole crashes when monitor goes to sleep
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.
[plasma-systemmonitor] [Bug 456187] Add ability to see loaded shared libraries and other detailed information for a process to system monitor
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 (Mesa version, etc.). 2. You have GUI application and want to check if it's using Qt, GTK 3, GTK 4 or etc. And so on. -- You are receiving this mail because: You are watching all bug changes.
[konsole] [Bug 463475] Konsole crashes when monitor goes to sleep
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 rolling back to konsole 22.08. What is your Qt version? -- You are receiving this mail because: You are watching all bug changes.
[Discover] [Bug 463134] The Discover panel applet says "System up to date," even if there are available updates.
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.
[plasma-systemmonitor] [Bug 456187] Add ability to see loaded shared libraries and other detailed information for a process to system monitor
https://bugs.kde.org/show_bug.cgi?id=456187 Shmerl changed: What|Removed |Added Resolution|WAITINGFORINFO |--- Status|NEEDSINFO |REPORTED --- Comment #6 from Shmerl --- I added the info, changing the status to reported. -- You are receiving this mail because: You are watching all bug changes.
[konsole] [Bug 372116] Feature Request: Support OSC 52 (copy to clipboard)
https://bugs.kde.org/show_bug.cgi?id=372116 Shmerl changed: What|Removed |Added CC||n...@kde.org --- Comment #46 from Shmerl --- Can someone please help with merging this change? It's a big usability improvement for Wayland use case. Not sure if Christian is still active with this. cc @Nate Graham. -- You are receiving this mail because: You are watching all bug changes.
[konsole] [Bug 372116] Feature Request: Support OSC 52 (copy to clipboard)
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 feature later. -- You are receiving this mail because: You are watching all bug changes.
[konsole] [Bug 372116] Feature Request: Support OSC 52 (copy to clipboard)
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 receiving this mail because: You are watching all bug changes.
[konsole] [Bug 372116] Feature Request: Support OSC 52 (copy to clipboard)
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 mail because: You are watching all bug changes.
[plasma-systemmonitor] [Bug 456187] Add ability to see loaded shared libraries and other detailed information for a process to system monitor
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/blog/2024/05/my-work-in-kde-for-april-2024/#kensa Neat, thanks for working on it! Also if anyone needs, since system monitor drop that feature from sksysguard I've been using this trick with htop which works well enough too: * htop * F3 to find a process you need, then press Enter * While on that process, press L which opens a list of all loaded objects (which includes dynamic shared libraries) * F4 to filter and type what you want to focus on like "qt" to see what version of qt is loaded and so on. That's it. -- You are receiving this mail because: You are watching all bug changes.
[konsole] [Bug 372116] Feature Request: Support OSC 52 (copy to clipboard)
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 watching all bug changes.
[konsole] [Bug 372116] Feature Request: Support OSC 52 (copy to clipboard)
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 (e.g. window title) That might cover all cases (like very large selections) but it's still better than 256 characterless. Is there a problem to changing that default to something like a few megabytes altogether? -- You are receiving this mail because: You are watching all bug changes.
[konsole] [Bug 372116] Feature Request: Support OSC 52 (copy to clipboard)
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 // Max length of tokens (e.g. window title) src/Vt102Emulation.h:132:uint tokenBuffer[MAX_TOKEN_LENGTH]; // FIXME: overflow? ``` But I didn't dig extensively through it. Trying to build it now with that change to see if it does anything. -- You are receiving this mail because: You are watching all bug changes.
[konsole] [Bug 372116] Feature Request: Support OSC 52 (copy to clipboard)
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.
[konsole] [Bug 372116] Feature Request: Support OSC 52 (copy to clipboard)
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 because: You are watching all bug changes.
[konsole] [Bug 372116] Feature Request: Support OSC 52 (copy to clipboard)
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: > > > > ``` > > src/Vt102Emulation.cpp:322:tokenBufferPos = qMin(tokenBufferPos, > > MAX_TOKEN_LENGTH - 1); > > src/Vt102Emulation.h:127:#define MAX_TOKEN_LENGTH 256 // Max length of > > tokens (e.g. window title) > > src/Vt102Emulation.h:132:uint tokenBuffer[MAX_TOKEN_LENGTH]; // FIXME: > > overflow? > > ``` > > That looks like an outdated version of the code. Looking at the git history, > it seems like this issue may have been fixed a few weeks ago and the > tokenBuffer now gets resized to fit the content. I've got to take a closer > look, but that might enable me to revisit this issue. Either way > MAX_TOKEN_LENGTH is definitely obsolete now. Right, I should have clarified, I was doing it with Debian testing's konsole which is behind recent versions (due to Debian being in the middle of time_t 64-bit migration monstrosity and KDE maintainers not updating things often). https://tracker.debian.org/pkg/konsole But that's regardless, if the new code isn't using that define, it's still might have the limit somewhere. So you can get the idea what can be increased? -- You are receiving this mail because: You are watching all bug changes.
[konsole] [Bug 372116] Feature Request: Support OSC 52 (copy to clipboard)
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.
[konsole] [Bug 372116] Feature Request: Support OSC 52 (copy to clipboard)
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/-/commits/master/src/Vt102Emulation.h?ref_type=heads * https://invent.kde.org/utilities/konsole/-/commits/master/src/Vt102Emulation.cpp?ref_type=heads -- You are receiving this mail because: You are watching all bug changes.
[konsole] [Bug 372116] Feature Request: Support OSC 52 (copy to clipboard)
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.
[konsole] [Bug 372116] Feature Request: Support OSC 52 (copy to clipboard)
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.
[konsole] [Bug 372116] Feature Request: Support OSC 52 (copy to clipboard)
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-osc52) no > longer needs to set MAX_TOKEN_LENGTH since the buffer is indeed resized > automatically. Previously, I had set MAX_TOKEN_LENGTH to 65536 but now I'm > able to copy much longer text. Thanks for confirming! @ Christian Muehlhaeuser: Can you merge it please, then? -- You are receiving this mail because: You are watching all bug changes.
[plasma-systemmonitor] [Bug 438318] Some AMD gpu (lm-sensors-based?) sensors no longer available
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.
[plasma-systemmonitor] [Bug 438318] Some AMD gpu (lm-sensors-based?) sensors no longer available
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 changes.
[plasma-systemmonitor] [Bug 438318] Some AMD gpu (lm-sensors-based?) sensors no longer available
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 receiving this mail because: You are watching all bug changes.
[kwin] [Bug 450679] Qt applications in Kwin Wayland session hang when monitor is turned off / goes to sleep.
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.
[plasmashell] [Bug 424836] Task Manager does not remember the order of grouped windows after un-grouping
https://bugs.kde.org/show_bug.cgi?id=424836 Shmerl changed: What|Removed |Added CC||shtetl...@gmail.com --- Comment #1 from Shmerl --- I can confirm this. It's rather annoying. Any time windows are grouped becasue task manager is too crowded, it forgets the ordering requiring to arrange things manually all over again. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 424836] Task Manager does not remember the order of grouped windows after un-grouping
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 are watching all bug changes.
[Akonadi] [Bug 452565] New: Akonadi is creating "Unknown Organization" in $HOME/.config
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 Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: kdepim-b...@kde.org Reporter: shtetl...@gmail.com Target Milestone: --- Akonadi is consistently creating this file for me: $HOME/.config/Unknown Organization/akonadi_unifiedmailbox_agent.conf_changes.dat I suppose it should go to $HOME/.config/akonadi instead. OS: Debian testing. Akonadi: 21.12.3. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 450679] Kwin Wayland session hangs when monitor is turned off / goes to sleep.
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 application windows do. Killing them restores session to normal (pasmashell is OK). 2. GTK applications are not affected! They work normally. So may be it's some Qt specific bug? My current config: Frameworks: 5.93.0 Qt: 5.15.2 -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 450679] Kwin Wayland session hangs when monitor is turned off / goes to sleep.
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 are watching all bug changes.
[kwin] [Bug 450679] Qt applications in Kwin Wayland session hang when monitor is turned off / goes to sleep.
https://bugs.kde.org/show_bug.cgi?id=450679 Shmerl changed: What|Removed |Added Summary|Kwin Wayland session hangs |Qt applications in Kwin |when monitor is turned off |Wayland session hang when |/ goes to sleep.|monitor is turned off / ||goes to sleep. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 448275] All qt apps are freezed/crashed after screen wake up
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.
[kwin] [Bug 455900] No session restore since ~April
https://bugs.kde.org/show_bug.cgi?id=455900 Shmerl changed: What|Removed |Added CC||shtetl...@gmail.com --- Comment #1 from Shmerl --- I just switched to the Wayland session (Debian testing) and also encountered that session restore isn't working anymore. The only restored application is Firefox somehow. Not restored: konsole, kmail, ksysguard. Running Plasma 5.25.1 from experimental. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 455900] No session restore since ~April
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.
[kwin] [Bug 442839] [wayland] mouse cursor changes away from the theme cursor to adwaita
https://bugs.kde.org/show_bug.cgi?id=442839 Shmerl changed: What|Removed |Added CC||shtetl...@gmail.com --- Comment #15 from Shmerl --- The bug description should probably mention XWayland. I noticed that any XWayland use case simply ignores the cursor theme and uses default. A very simple test - run xev and notice how cursor changes when hovering over it. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 451822] Third-party cursor theme reverts to default Breeze when I open a menu of Firefox running on Xwayland
https://bugs.kde.org/show_bug.cgi?id=451822 Shmerl changed: What|Removed |Added CC||shtetl...@gmail.com --- Comment #2 from Shmerl --- This is likely the duplicate of bug #442839. -- You are receiving this mail because: You are watching all bug changes.
[kmail2] [Bug 393842] Scrollbar renders wrongs in message view, correct in message list
https://bugs.kde.org/show_bug.cgi?id=393842 Shmerl changed: What|Removed |Added CC||shtetl...@gmail.com --- Comment #5 from Shmerl --- Any news on this? I didn't realize it's such an old standing known bug. It is pretty annoying visually. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 455900] No session restore since ~April
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 receiving this mail because: You are watching all bug changes.
[ksmserver] [Bug 436318] Save session doesn't work under Wayland
https://bugs.kde.org/show_bug.cgi?id=436318 Shmerl changed: What|Removed |Added CC||shtetl...@gmail.com --- Comment #10 from Shmerl --- So something like this will eventually be able to help it? https://www.youtube.com/watch?v=fRdnRwPBFBk -- You are receiving this mail because: You are watching all bug changes.
[plasma-systemmonitor] [Bug 456187] New: Add ability to see loaded shared libraries and other detailed information for a process to system monitor
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 Platform: Debian testing OS: Linux Status: REPORTED Severity: wishlist Priority: NOR Component: general Assignee: ksysguard-b...@kde.org Reporter: shtetl...@gmail.com CC: ahiems...@heimr.nl, plasma-b...@kde.org Target Milestone: --- ksysguard has a useful feature - when you choose "Detailed information" from context menu for a process from the process list, it gives ability to see loaded shared libraries and a bunch of other information about process context. Please add similar feature to plasma-systemmonitor, since it's intended as a replacement for ksysguard. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 450679] Kwin Wayland session hangs when monitor is turned off / goes to sleep.
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 are watching all bug changes.
[kwin] [Bug 450679] Kwin Wayland session hangs when monitor is turned off / goes to sleep.
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 changes.
[kwin] [Bug 443872] Inconsistent adaptive sync behavior in KWin Wayland session
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.
[plasma-systemmonitor] [Bug 438318] Some AMD gpu (lm-sensors-based?) sensors no longer available
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.
[plasma-systemmonitor] [Bug 438318] Some AMD gpu (lm-sensors-based?) sensors no longer available
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 =0 RPM, max = 3300 RPM) edge: +51.0°C (crit = +100.0°C, hyst = -273.1°C) (emerg = +105.0°C) junction: +56.0°C (crit = +110.0°C, hyst = -273.1°C) (emerg = +115.0°C) mem: +56.0°C (crit = +100.0°C, hyst = -273.1°C) (emerg = +105.0°C) power1: 37.00 W (cap = 272.00 W) I don't see power1 sensors in the GPU section in Plasma 5.23.1 monitor. This approach with filtering is really not sustainable and will be broken every time something new is introduced. Seriously, please allow users adding a generic sensor without any limitations if they want to. -- You are receiving this mail because: You are watching all bug changes.
[plasma-systemmonitor] [Bug 438318] Some AMD gpu (lm-sensors-based?) sensors no longer available
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.
[kwin] [Bug 443872] Inconsistent adaptive sync behavior in KWin Wayland session
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.
[kwin] [Bug 443872] Inconsistent adaptive sync behavior in KWin Wayland session
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) kwin_wayland_drm: vrr changed to 1 But when those spikes to max refresh rate on the display built in HUD happen, it's not logging any of those, so as far as that code goes, it assumes VRR is on during the spikes. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 443872] Inconsistent adaptive sync behavior in KWin Wayland session
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.
[kwin] [Bug 443872] Inconsistent adaptive sync behavior in KWin Wayland session
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.
[kwin] [Bug 443872] Inconsistent adaptive sync behavior in KWin Wayland session
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.
[plasma-systemmonitor] [Bug 438318] Some AMD gpu (lm-sensors-based?) sensors no longer available
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 sensors under "Hardware sensors" in addition to the filtered ones in CPU > or something. Yes, good point. I'm using ksysguard because it allows selecting any available sensors exactly this way and you can see the sensor name. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 443872] New: Inconsistent adaptive sync behavior in KWin Wayland session
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 Status: REPORTED Severity: normal Priority: NOR Component: wayland-generic Assignee: kwin-bugs-n...@kde.org Reporter: shtetl...@gmail.com Target Milestone: --- I just tried Plasma 5.23.0 (built for Debian testing) since it has a number of major Wayland related bugs fixed, and noticed a problem with adaptive sync. When running Cyberpunk 2077 game (Wine-staging + vkd3d-proton), framerate hovers around 70-85 fps in the game for me. Monitor's built in refresh rate meter shows that adaptive sync is working (most of the time it indeed matches the framerate fluctuating around 70-85 Hz), but it also periodically jumps to 144 Hz which looks strange, since Mesa HUD which I use with the game to compare never shows framerate jumping that high and it's my monitor's limit. In X11 Kwin session I don't see such behavior in the same place in the game and monitor's built in meter never shows such spikes in refresh rate. Configuration details: * Plasma / KWin: 5.23.0 * Display setting for adaptive sync: automatic. * GPU: Sapphire Pulse RX 6800 XT. * Display: LG 27GL850 (144 Hz, adaptive sync capable, DisplayPort connection). * Wine-staging: 6.16 (the game runs in XWayland) * Wayland: 1.19.0 * XWayland: 1.20.11 * Kernel / amdgpu: 5.14.12 * Mesa: recent main build - 22.0.0-devel (git-d31ca63527) -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 443872] Inconsistent adaptive sync behavior in KWin Wayland session
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 are watching all bug changes.
[kwin] [Bug 443872] Inconsistent adaptive sync behavior in KWin Wayland session
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 might be in response to some mouse input that's causing movement in the game. How do I check if it's using hardware cursor? I don't think I set anything special for that or even looked into this setting. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 443872] Inconsistent adaptive sync behavior in KWin Wayland session
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 doesn't look like it supports using hardware cursor either. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 443872] Inconsistent adaptive sync behavior in KWin Wayland session
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.
[kwin] [Bug 443872] Inconsistent adaptive sync behavior in KWin Wayland session
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 are watching all bug changes.
[kwin] [Bug 443872] Inconsistent adaptive sync behavior in KWin Wayland session
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 that low in the Mesa HUD and it's still suspicious that it runs at exactly max refresh rate during those spikes, looks more like adaptive sync just turns off during those moments. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 443872] Inconsistent adaptive sync behavior in KWin Wayland session
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 debug logging enabled (if this change is in the compositor already)? -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 443872] Inconsistent adaptive sync behavior in KWin Wayland session
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.
[plasmashell] [Bug 424754] Plasma fails to paste text copied from apps running on Xwayland (tested Firefox and Chromium)
https://bugs.kde.org/show_bug.cgi?id=424754 Shmerl changed: What|Removed |Added CC||shtetl...@gmail.com --- Comment #38 from Shmerl --- I have another use case that doesn't involve GTK or XWayland. 1. Open Kate, open Konsole. 2. Copy test from Kate, paste in Konsole - works. 3. Copy another text from Kate and paste in console - nothing is getting pasted. Klipper shows empty text for the current buffer. Both Konsole and Kate are Wayland windows, no XWayland windows are active during this test. Plasma: 5.22.3. Should I open another bug about it or it falls into the same one? -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 424754] Plasma fails to paste text copied from apps running on Xwayland (tested Firefox and Chromium)
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: You are watching all bug changes.
[plasmashell] [Bug 439765] New: Clipboard is intermittently broken in the Wayland session
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 Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: k...@davidedmundson.co.uk Reporter: shtetl...@gmail.com CC: plasma-b...@kde.org Target Milestone: 1.0 Trying the Wayland session in Plasma 5.22.3 / frameworks 5.84.0 / Qt 5.15.2, I experienced a problem with clipboard that's similar to other reports in bug 424754, except it's with pure Wayland / Qt use case, no XWayland or GTK involved. Scenario: 1. Open Kate and type in some text in it, open Konsole. 2. Copy some text from Kate, paste it in Konsole - works OK. 3. Copy some other text from Kate, paste it Konsole - nothing is getting pasted. This happens intermittently, i.e. sometimes it copy / pastes, sometimes it doesn't. When it doesn't, Klipper shows current content as empty. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 424754] Plasma fails to paste text copied from apps running on Xwayland (tested Firefox and Chromium)
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.
[plasmashell] [Bug 439765] Clipboard is intermittently broken in the Wayland session
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
zwp_primary_selection_offer_v1@3633541696)
[599702.263] -> wl_data_device_manager@9.create_data_source(new id
wl_data_source@39)
[599702.277] -> wl_data_source@39.offer("text/plain")
[599702.280] -> wl_data_source@39.offer("text/plain;charset=utf-8")
[599702.284] -> wl_data_device@10.set_selection(wl_data_source@39, 2099)
[599702.383] wl_data_device@10.data_offer(new id wl_data_offer@3632315184)
[599702.389] wl_data_offer@4278190082.offer("text/plain")
[599702.393] wl_data_offer@4278190082.offer("text/plain;charset=utf-8")
[599702.397] wl_data_device@10.selection(wl_data_offer@4278190082)
[599702.401] -> wl_data_offer@4278190080.destroy()
[599702.554] wl_data_sou...@39.send("text/plain;charset=utf-8", fd 16)
[599702.805] wl_data_source@39.cancelled()
[599702.815] -> wl_data_source@39.destroy()
[599702.823] wl_data_device@10.selection(nil)
[599702.825] -> wl_data_offer@4278190082.destroy()
[599702.846] wl_data_device@10.data_offer(new id wl_data_offer@3633539552)
[599702.851] wl_data_offer@4278190080.offer("text/plain")
[599702.854]
wl_data_offer@4278190080.offer("application/x-kde-onlyReplaceEmpty")
[599702.857] wl_data_offer@4278190080.offer("text/plain;charset=utf-8")
[599702.863] wl_data_device@10.selection(wl_data_offer@4278190080)
[605543.702] -> wl_data_offer@4278190080.destroy()
Bad selection:
[733959.295] zwp_primary_selection_device_v1@12.data_offer(new id
zwp_primary_selection_offer_v1@3633571472)
[734759.439] -> wl_data_device_manager@9.create_data_source(new id
wl_data_source@47)
[734759.449] -> wl_data_source@47.offer("text/plain")
[734759.452] -> wl_data_source@47.offer("text/plain;charset=utf-8")
[734759.457] -> wl_data_device@10.set_selection(wl_data_source@47, 2797)
[734759.565] wl_data_device@10.data_offer(new id wl_data_offer@3633449056)
[734759.572] wl_data_offer@4278190082.offer("text/plain")
[734759.577] wl_data_offer@4278190082.offer("text/plain;charset=utf-8")
[734759.579] wl_data_device@10.selection(wl_data_offer@4278190082)
[734759.583] -> wl_data_offer@4278190081.destroy()
[734760.041] wl_data_source@47.cancelled()
[734760.059] -> wl_data_source@47.destroy()
[734760.066] wl_data_device@10.selection(nil)
[734760.069] -> wl_data_offer@4278190082.destroy()
[734760.260] wl_data_device@10.data_offer(new id wl_data_offer@3633496752)
[734760.264] wl_data_offer@4278190082.offer("text/plain")
[734760.268]
wl_data_offer@4278190082.offer("application/x-kde-onlyReplaceEmpty")
[734760.270] wl_data_offer@4278190082.offer("text/plain;charset=utf-8")
[734760.273] wl_data_device@10.selection(wl_data_offer@4278190082)
[736764.890] -> wl_data_offer@4278190082.destroy()
[737620.024] wl_data_device@10.data_offer(new id wl_data_offer@3633571472)
[737620.029] wl_data_offer@4278190080.offer("text/plain")
[737620.033]
wl_data_offer@4278190080.offer("application/x-kde-onlyReplaceEmpty")
[737620.035] wl_data_offer@4278190080.offer("text/plain;charset=utf-8")
[737620.037] wl_data_device@10.selection(wl_data_offer@4278190080)
[737620.041] zwp_primary_selection_device_v1@12.data_offer(new id
zwp_primary_selection_offer_v1@3633458032)
[738569.965] -> wl_data_offer@4278190080.destroy()
--
You are receiving this mail because:
You are watching all bug changes.
[plasmashell] [Bug 439765] Clipboard is intermittently broken in the Wayland session
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 receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 439765] Clipboard is intermittently broken in the Wayland session
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. Timeout for action popups: 8 seconds Clipboard history size: 1 entry. -- You are receiving this mail because: You are watching all bug changes.
[plasma-systemmonitor] [Bug 438318] Some AMD gpu (lm-sensors-based?) sensors no longer available
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 these are already handles by the CPU and GPU plugins. > However those do not expose all of the available sensors. They should not be intentionally excluded, because CPU / GPU options are more limited than actual sensors. I.e. please let the user decide whether they are satisfied with more simplistic GPU / CPU option or have a need for detailed sensors. Taking away choice is a bad thing here. -- You are receiving this mail because: You are watching all bug changes.
[plasma-systemmonitor] [Bug 438318] Some AMD gpu (lm-sensors-based?) sensors no longer available
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 provide implicitly, it will become immediately available in the generic sensors section. So the better approach is to simply not filter any existing sensors from it. -- You are receiving this mail because: You are watching all bug changes.
[plasma-systemmonitor] [Bug 439574] New: Don't filter out amdgpu from selectable of hardware sensors to monitor.
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: Linux Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: ksysguard-b...@kde.org Reporter: shtetl...@gmail.com CC: ahiems...@heimr.nl, plasma-b...@kde.org Target Milestone: --- When trying to add hardware sensors for Plasma System Monitor, amdgpu ones aren't shown. I assume it's becasue the UI has a separate selection for "GPU", but that looks like a bad reason to prevent selecting amdgpu sensors directly, becasue options in GPU path are more limited than what actual sensors can provide. For example my amdgpu sensors shows me three temperatures: for memory, junction and edge. While GPU UI selection just has a generic "GPU temperature" which probably is just one of the above. Please don't filter out any existing sensors groups - let the user select anything directly, if existing presets don't end up being sufficient. -- You are receiving this mail because: You are watching all bug changes.
[plasma-systemmonitor] [Bug 439574] Don't filter out amdgpu from selectable of hardware sensors to monitor.
https://bugs.kde.org/show_bug.cgi?id=439574 Shmerl changed: What|Removed |Added Platform|Other |Debian testing -- You are receiving this mail because: You are watching all bug changes.
[plasma-systemmonitor] [Bug 439574] Don't filter out amdgpu from selectable hardware sensors to monitor.
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 selectable of hardware |from selectable hardware |sensors to monitor. |sensors to monitor. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 387313] Subsurfaces are not clipped
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 very badly, so I don't think this issue is fixed or I'm missing something. Message pane in Kmail doesn't display anything for me and just flickers sometimes. -- You are receiving this mail because: You are watching all bug changes.
