[ktorrent] [Bug 450179] UPnP plugin not forwarding ports
https://bugs.kde.org/show_bug.cgi?id=450179 Sebastian Krzyszkowiak changed: What|Removed |Added CC||d...@dosowisko.net --- Comment #1 from Sebastian Krzyszkowiak --- https://invent.kde.org/network/libktorrent/-/merge_requests/63 may fix this. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 482645] System tray icons are colored wrong when using dark Plasma and light application theme
https://bugs.kde.org/show_bug.cgi?id=482645 Sebastian Krzyszkowiak changed: What|Removed |Added CC||d...@dosowisko.net --- Comment #12 from Sebastian Krzyszkowiak --- This isn't fully fixed - icons that require attention are still dark on dark (for example, Konversation with unread messages). -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 482565] Crash on connecting to audio Bluetooth device
https://bugs.kde.org/show_bug.cgi?id=482565 --- Comment #1 from Sebastian Krzyszkowiak --- Created attachment 166494 --> https://bugs.kde.org/attachment.cgi?id=166494=edit New crash information added by DrKonqi DrKonqi auto-attaching complete backtrace. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 482565] New: Crash on connecting to audio Bluetooth device
https://bugs.kde.org/show_bug.cgi?id=482565 Bug ID: 482565 Summary: Crash on connecting to audio Bluetooth device Classification: Plasma Product: plasmashell Version: 6.0.1 Platform: Arch Linux OS: Linux Status: REPORTED Keywords: drkonqi Severity: crash Priority: NOR Component: generic-crash Assignee: plasma-b...@kde.org Reporter: d...@dosowisko.net Target Milestone: 1.0 Application: plasmashell (6.0.1) Qt Version: 6.6.2 Frameworks Version: 6.0.0 Operating System: Linux 6.7.8-arch1-1 x86_64 Windowing System: Wayland Distribution: "Arch Linux" DrKonqi: 6.0.1 [CoredumpBackend] -- Information about the crash: Connecting to a Bluetooth audio device caused plasmashell to crash. The connection was successful (the device was available once Plasma was up again). The crash can be reproduced sometimes. -- Backtrace (Reduced): #5 0x in ??? () #6 0x78ec8c6be1e2 in QQmlMetaType::propertyCache (obj=, version=...) at /usr/src/debug/qt6-declarative/qtdeclarative-everywhere-src-6.6.2/src/qml/qml/qqmlmetatype.cpp:1328 #7 0x78ec8c6fab55 in qQmlPropertyCacheProperty (obj=0x6412c3d43250, name=0x78ec7c3bf5d0, context=..., local=0x7ffd0cfb91e0) at /usr/src/debug/qt6-declarative/qtdeclarative-everywhere-src-6.6.2/src/qml/qml/qqmlpropertycache.cpp:873 #8 0x78ec8c5b1501 in QQmlPropertyCache::property (local=0x7ffd0cfb91e0, context=, name=, obj=0x6412c3d43250) at /usr/src/debug/qt6-declarative/qtdeclarative-everywhere-src-6.6.2/src/qml/qml/qqmlpropertycache.cpp:896 #9 QV4::QObjectWrapper::setQmlProperty (engine=0x6412bb91b870, qmlContext=, object=0x6412c3d43250, name=, flags=..., value=...) at /usr/src/debug/qt6-declarative/qtdeclarative-everywhere-src-6.6.2/src/qml/jsruntime/qv4qobjectwrapper.cpp:455 Reported using DrKonqi -- You are receiving this mail because: You are watching all bug changes.
[frameworks-networkmanager-qt] [Bug 464615] New: Support Enhanced Open (OWE) Wi-Fi security option
https://bugs.kde.org/show_bug.cgi?id=464615 Bug ID: 464615 Summary: Support Enhanced Open (OWE) Wi-Fi security option Classification: Frameworks and Libraries Product: frameworks-networkmanager-qt Version: unspecified Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: plasma-b...@kde.org Reporter: d...@dosowisko.net CC: lamar...@kde.org, lukas.ti...@merlin.cz Target Milestone: --- NetworkManagerQt does not expose "Enhanced Open" (aka Opportunistic Wireless Encryption) security option for Wi-Fi networks supported by NetworkManager since 2019 (1.24.0), which allows to have the communication between station and access point encrypted without having to use a passphrase. This will be needed to support OWE networks in plasma-nm. -- You are receiving this mail because: You are watching all bug changes.
[kmail2] [Bug 441260] New: Confusing "Mark Message" menu UX
https://bugs.kde.org/show_bug.cgi?id=441260 Bug ID: 441260 Summary: Confusing "Mark Message" menu UX Product: kmail2 Version: Git (master) Platform: unspecified OS: All Status: REPORTED Severity: normal Priority: NOR Component: UI Assignee: kdepim-b...@kde.org Reporter: k...@dosowisko.net Target Milestone: --- Created attachment 140883 --> https://bugs.kde.org/attachment.cgi?id=140883=edit "Mark Message" menu screenshot (version: 5.18.0 [there's no such option in the Version field to choose]) For a message that's marked as important, its "Mark Message" menu presents a selected checkbox with "Remove Important Mark" label (see the attached screenshot). That's... confusing. It suggests that removal of important mark is now being active, so effectively tells that the message is not marked as important, which isn't true. Unchecking it makes the label change to "Mark Message as Important", which makes much more sense. The confusion comes from the fact that KMail presents an action-based wording in a context that strongly suggest a state-based one. Possible solutions: - keep the label as "Mark Message as Important" and don't change it for messages already marked as such, as the checkbox already tells the user whether the message is marked or not and what will happen after toggling it - remove the checkbox; keep the current label's behavior. This will make it clear that the label represents an action that happens after selecting it and not the current state. - split the menu item into two items (mark / unmark) with only one enabled at once. As a bonus, this would make it consistent with "Mark Message as Read/Unread" entries right above. The same issue applies to "Mark Message as Action Item" entry as well. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 407196] plasmashell wakes up a lot (eating CPU and battery) on stock configuration
https://bugs.kde.org/show_bug.cgi?id=407196 Sebastian Krzyszkowiak changed: What|Removed |Added Resolution|WAITINGFORINFO |--- Status|NEEDSINFO |REPORTED --- Comment #9 from Sebastian Krzyszkowiak --- Just booted neon-unstable-20210122-1501.iso in a VM (using gnome-boxes) and it's still happening straight out-of-box until I edit the panel and remove Application Launcher. It's easily reproducible and super simple to check by anyone with "sudo strace -f -p `pidof plasmashell`". -- You are receiving this mail because: You are watching all bug changes.
[konsole] [Bug 430311] Intensive color selection broken as of 270d6ea3
https://bugs.kde.org/show_bug.cgi?id=430311 Sebastian Krzyszkowiak changed: What|Removed |Added CC||d...@dosowisko.net --- Comment #4 from Sebastian Krzyszkowiak --- (In reply to Antonio Russo from comment #3) > I'd appreciate anyone willing to test this out and give feedback---please > notice that the tests I have run right now are VERY MINIMAL. Thanks a lot! My terminal is readable again on "Linux Colors" scheme with your patchset :) -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 407196] plasmashell wakes up a lot (eating CPU and battery) on stock configuration
https://bugs.kde.org/show_bug.cgi?id=407196 Sebastian Krzyszkowiak changed: What|Removed |Added Resolution|WAITINGFORINFO |--- Status|NEEDSINFO |REPORTED --- Comment #5 from Sebastian Krzyszkowiak --- Updating the status (info already provided above). -- You are receiving this mail because: You are watching all bug changes.
[yakuake] [Bug 401982] One Wayland login cripples Yakuake in X11 forever
https://bugs.kde.org/show_bug.cgi?id=401982 Sebastian Krzyszkowiak changed: What|Removed |Added CC||d...@dosowisko.net --- Comment #5 from Sebastian Krzyszkowiak --- Happens here as well. As a workaround, I do "xrandr -s 1" and then "xrandr -s 0", as screen resolution change seems to update Yakuake's geometry to a correct one. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 407458] Window minimize animation misplaced with PLASMA_USE_QT_SCALING=1
https://bugs.kde.org/show_bug.cgi?id=407458 --- Comment #2 from Sebastian Krzyszkowiak --- I don't set random envs, I know what I'm getting into. Not using Qt scaling in Plasma leads to an aesthetic disaster with hidpi scaling. The alternative is a minor glitch reported here. Finding the cases where geometry spaces are being mixed up and fixing them seems to be a correct way to go, as I was advised in T8177. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 407458] New: Window minimize animation misplaced with PLASMA_USE_QT_SCALING=1
https://bugs.kde.org/show_bug.cgi?id=407458 Bug ID: 407458 Summary: Window minimize animation misplaced with PLASMA_USE_QT_SCALING=1 Product: plasmashell Version: 5.15.5 Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: k...@davidedmundson.co.uk Reporter: d...@dosowisko.net CC: plasma-b...@kde.org Target Milestone: 1.0 SUMMARY When using PLASMA_USE_QT_SCALING=1 on X11 (as it's the only way to get correct paddings and UI sizing in Plasma under X11 on a hidpi screen) and minimizing window with a KWin effect, Plasma reports unscaled iconGeometry (in logical coordinates instead of real pixels that KWin expects, like 200x850 instead of 400x1700 on 2x screen), resulting in wrong animations. STEPS TO REPRODUCE 1. Use Plasma on a hidpi screen with PLASMA_USE_QT_SCALING=1 enabled 2. Try to minimize a window by clicking on the taskbar icon (with some minimization animation enabled in KWin) OBSERVED RESULT The window gets minimized to some place in the middle of the screen. EXPECTED RESULT The window gets minimized to the clicked taskbar icon. SOFTWARE/OS VERSIONS KDE Plasma Version: 5.15.5 KDE Frameworks Version: 5.57 Qt Version: 5.12.3 ADDITIONAL INFORMATION https://phabricator.kde.org/T8177#176789 -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 407196] plasmashell wakes up a lot (eating CPU and battery) on stock configuration
https://bugs.kde.org/show_bug.cgi?id=407196 --- Comment #3 from Sebastian Krzyszkowiak --- Since 15-16 ms timeouts suggest that it's likely some rendering loop, let me add that I use Intel Mesa drivers on Arch and llvmpipe in the VM, if that makes any difference. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 407196] plasmashell wakes up a lot (eating CPU and battery) on stock configuration
https://bugs.kde.org/show_bug.cgi?id=407196 --- Comment #2 from Sebastian Krzyszkowiak --- Created attachment 119845 --> https://bugs.kde.org/attachment.cgi?id=119845=edit strace A freshly booted Neon ISO in a virtual machine. The same thing I observed locally on my Arch with stable Plasma. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 407196] New: plasmashell wakes up a lot (eating CPU and battery) on stock configuration
https://bugs.kde.org/show_bug.cgi?id=407196
Bug ID: 407196
Summary: plasmashell wakes up a lot (eating CPU and battery) on
stock configuration
Product: plasmashell
Version: master
Platform: Other
OS: Linux
Status: REPORTED
Severity: normal
Priority: NOR
Component: Application Launcher (Kickoff)
Assignee: k...@davidedmundson.co.uk
Reporter: d...@dosowisko.net
CC: plasma-b...@kde.org
Target Milestone: 1.0
SUMMARY
Seems like Application Launcher widget is somewhat responsible for elevated CPU
(and battery) usage on plasmashell.
STEPS TO REPRODUCE
1. Run a vanilla clean Plasma session.
2. Wait a but until everything finishes launching and becomes idle.
3. Attach strace to a running plasmashell process ("sudo strace -f -p `pidof
plasmashell`")
OBSERVED RESULT
Lots of repeated polls with timeout values less than 20ms, easily eating
significant amounts of CPU (around 5% here).
EXPECTED RESULT
Some occasional polls, plasmashell achieving <1% CPU usage when idle.
--
Afterwards (additional info gathered when investigating):
STEPS TO REPRODUCE
1. Remove Application Launcher widget from the default panel.
2. Add it back.
OBSERVED RESULT
plasmashell becomes way more CPU friendly.
--
STEPS TO REPRODUCE
1. Restart plasmashell.
OBSERVED RESULT
plasmashell becomes CPU hungry again.
EXPECTED RESULT
plasmashell should still be CPU friendly.
--
STEPS TO REPRODUCE
1. Remove Application Launcher.
2. (optionally) Add Application Menu.
3. Restart plasmashell.
OBSERVED RESULT
Plasma is still CPU friendly
SOFTWARE/OS VERSIONS
Tested with latest (2019-05-03) Neon Developer Edition ISO.
ADDITIONAL INFORMATION
All the steps above suggest that something is wrong with Application Launcher
widget, but only when it's loaded together with Plasma and/or panel (adding it
with a default panel causes the same result as restarting whole Plasma).
--
You are receiving this mail because:
You are watching all bug changes.
[kwin] [Bug 395179] Global menu getting outside of screen
https://bugs.kde.org/show_bug.cgi?id=395179 --- Comment #5 from Sebastian Krzyszkowiak --- Forgot to mention: I'm using version 5.13.90 right now, but it was already happening for at least a few releases. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 395179] Global menu getting outside of screen
https://bugs.kde.org/show_bug.cgi?id=395179 --- Comment #4 from Sebastian Krzyszkowiak --- I can confirm on X11. Also, the same issue happens with long menus and nested submenus even when the button is on the left side. Hiding the submenu and making it reappear causes it to show up correctly next time. I've attached a video showing the issue. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 395179] Global menu getting outside of screen
https://bugs.kde.org/show_bug.cgi?id=395179 Sebastian Krzyszkowiak changed: What|Removed |Added CC||d...@dosowisko.net --- Comment #3 from Sebastian Krzyszkowiak --- Created attachment 115436 --> https://bugs.kde.org/attachment.cgi?id=115436=edit Global menu going off the screen with long menus. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 366062] Icons for Electron apps are too large in the System Tray
https://bugs.kde.org/show_bug.cgi?id=366062 Sebastian Krzyszkowiak changed: What|Removed |Added CC||d...@dosowisko.net --- Comment #26 from Sebastian Krzyszkowiak --- No, it's an issue with Chromium. I've just sent a patchset there that fixes it: https://chromium-review.googlesource.com/c/chromium/src/+/1173235 -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 348270] Cannot scroll properly in GTK3 apps after focus switching
https://bugs.kde.org/show_bug.cgi?id=348270 Sebastian Krzyszkowiak <k...@dosowisko.net> changed: What|Removed |Added CC||k...@dosowisko.net --- Comment #36 from Sebastian Krzyszkowiak <k...@dosowisko.net> --- I have just noticed this behavior (unreliable touchpad scrolling in unfocused window) with editor in Qt Creator 4.5. I have tried it on Metacity and it doesn't happen there, so not sure if I should report here to KWin or to Qt Creator. -- You are receiving this mail because: You are watching all bug changes.
[Powerdevil] [Bug 353463] RFE: Make use of iio-sensor-proxy
https://bugs.kde.org/show_bug.cgi?id=353463 Sebastian Krzyszkowiak <k...@dosowisko.net> changed: What|Removed |Added CC||k...@dosowisko.net --- Comment #11 from Sebastian Krzyszkowiak <k...@dosowisko.net> --- I have written kded module for screen rotation already, tested with Yoga 2 Pro and Yoga 900. Uses Plasma's OSD to show that the rotation is about to occur, giving the user some time to cancel if he didn't mean to rotate and just tilted the device a bit too much. It should probably use KScreen instead of shell script to rotate the screen; also "mediaPlayerVolumeChanged" may not be the best option for OSD :D The script also hardcodes the touchscreen device name in order to keep it in sync with rotation. So it's not exactly in upstreamable quality yet, but maybe someone will find it useful :) https://github.com/dos1/kded_rotation -- You are receiving this mail because: You are watching all bug changes.
[ksmserver] [Bug 346714] Focus is not on lockscreen after autologin with DESKTOP_LOCKED=yes
https://bugs.kde.org/show_bug.cgi?id=346714 --- Comment #6 from Sebastian Krzyszkowiak <d...@dosowisko.net> --- I can confirm it doesn't happen anymore :) -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 348270] Cannot scroll properly in GTK3 apps after focus switching
https://bugs.kde.org/show_bug.cgi?id=348270 Sebastian Krzyszkowiak <d...@dosowisko.net> changed: What|Removed |Added CC||d...@dosowisko.net --- Comment #34 from Sebastian Krzyszkowiak <d...@dosowisko.net> --- This bug breaks touchpad smooth scrolling (using XInput 2.1 events) on Firefox when its window gets deactivated :( It kinda works, but it's very painful to use (fortunately getting focus back fixes it, so it's just an annoyance). Should it stay "RESOLVED UPSTREAM" when GTK+ patch has been reverted and it's still broken to this day? Maybe it should be workarounded in KWin after all? GDK_CORE_DEVICE_EVENTS is not an acceptable workaround, as it turns off smooth scrolling completely, and as much as I don't care about it in other GTK+ apps, Firefox is definitely one where I do care ;) -- You are receiving this mail because: You are watching all bug changes.
