[kdeconnect] [Bug 471412] New: Not work on Ubuntu GNOME Wayland
https://bugs.kde.org/show_bug.cgi?id=471412 Bug ID: 471412 Summary: Not work on Ubuntu GNOME Wayland Classification: Applications Product: kdeconnect Version: 23.04.0 Platform: Ubuntu OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: common Assignee: albertv...@gmail.com Reporter: ekon...@atlas.sk CC: andrew.g.r.hol...@gmail.com Target Milestone: --- Created attachment 159882 --> https://bugs.kde.org/attachment.cgi?id=159882&action=edit wayland Hello, On Ubuntu default setting, on GNOME Wayland not work correct Kde Connect. Main features not work correct. My version of KDE connect is 22.12.3. Installed form Ubuntu Software KDE Connect work correct only on Ubuntu Xorg. Can you add support for Ubuntu Wayland? Thanks -- You are receiving this mail because: You are watching all bug changes.
[kdeconnect] [Bug 471412] Not work on Ubuntu GNOME Wayland
https://bugs.kde.org/show_bug.cgi?id=471412 --- Comment #1 from Matej --- Created attachment 159883 --> https://bugs.kde.org/attachment.cgi?id=159883&action=edit login -- You are receiving this mail because: You are watching all bug changes.
[kdeconnect] [Bug 471412] Not work on Ubuntu GNOME Wayland
https://bugs.kde.org/show_bug.cgi?id=471412 --- Comment #3 from Matej --- Hi Nicolas, on Wayland not work correct clipboard a remote access. And issue with graphics – cursor is too big. -- You are receiving this mail because: You are watching all bug changes.
[kdeconnect] [Bug 471412] Not work on Ubuntu GNOME Wayland
https://bugs.kde.org/show_bug.cgi?id=471412 Matej changed: What|Removed |Added CC||ekon...@atlas.sk -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 413794] New: Transform deletes object
https://bugs.kde.org/show_bug.cgi?id=413794 Bug ID: 413794 Summary: Transform deletes object Product: krita Version: 4.2.7.1 Platform: MS Windows OS: MS Windows Status: REPORTED Severity: normal Priority: NOR Component: Tools/Transform Assignee: krita-bugs-n...@kde.org Reporter: matejko...@hotmail.sk Target Milestone: --- Using any transform option (scale, perspective, warp, etc.) deletes all contents of selection. STEPS TO REPRODUCE 1. Pick an object/selection 2. Use transform tool (scale, perspective, warp, etc.) 3. Apply changes OBSERVED RESULT The selection/object gets deleted. I checked all layers everything if it doesn't just get moved and stuff but no EXPECTED RESULT It should leave the image in place but transform it SOFTWARE/OS VERSIONS Windows: 10 -- You are receiving this mail because: You are watching all bug changes.
[kdeconnect] [Bug 493958] New: Crash on android. After update it fully crash
https://bugs.kde.org/show_bug.cgi?id=493958 Bug ID: 493958 Summary: Crash on android. After update it fully crash Classification: Applications Product: kdeconnect Version: unspecified Platform: Android OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: android-application Assignee: albertv...@gmail.com Reporter: ekon...@atlas.sk CC: andrew.g.r.hol...@gmail.com Target Milestone: --- Hello, I use Android A52. Bug report!! Please repair it!! After update it fully crash. After open it instantly crash. Please create instantly update with repair -- You are receiving this mail because: You are watching all bug changes.
[kdeconnect] [Bug 493958] Crash on android. After update it fully crash
https://bugs.kde.org/show_bug.cgi?id=493958 --- Comment #11 from Matej --- I am sorry. Yes. I use Samsung Galaxy A52. Android version is Android 14. Issues starts after Android restart. I am sorry for non-gracious form of communication. My update of KDE Connect was from Google Play too. The same bug as from others described. -- You are receiving this mail because: You are watching all bug changes.
[kdeconnect] [Bug 493958] Crash on android. After update it fully crash
https://bugs.kde.org/show_bug.cgi?id=493958 --- Comment #17 from Matej --- While you will wait on next update on Google Play Store with repair, you can use temporary solution. Uninstall KDE conect and install older version. For example version 1.32.2. Older version you can download for example here https://apkpure.com/kde-connect/org.kde.kdeconnect_tp -- You are receiving this mail because: You are watching all bug changes.
[kdeconnect] [Bug 501241] Issue with connection between two Android phones on version 1.33.1
https://bugs.kde.org/show_bug.cgi?id=501241 --- Comment #12 from Matej --- Created attachment 179369 --> https://bugs.kde.org/attachment.cgi?id=179369&action=edit Logs created during try connect KDE connect Android phones Thank you very much Albert for your work. I am now tested it. Version 1.33.2 works correct between my Android 13 and Android 14. Your version from mega.nz work correct between my Android 13 and Android 14 correct too. But it these two KDE connect versions not work correct between Android 7 and newer versions Android phones -- You are receiving this mail because: You are watching all bug changes.
[dolphin] [Bug 501550] New: Open as root not work correct on Kubuntu
https://bugs.kde.org/show_bug.cgi?id=501550 Bug ID: 501550 Summary: Open as root not work correct on Kubuntu Classification: Applications Product: dolphin Version: 24.08.3 Platform: Kubuntu OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: dolphin-bugs-n...@kde.org Reporter: ekon...@atlas.sk CC: kfm-de...@kde.org Target Milestone: --- Created attachment 179438 --> https://bugs.kde.org/attachment.cgi?id=179438&action=edit version If I use other file browser it is very simple use as root / sudo. For example I write in terminal: sudo nautilus (is is possible in Ubuntu desktop) sudo nemo (Is ti possible in linux mint) But open as root is extremely difficult in dolphin in Kubuntu. Kubuntu blocking using as root. But exist solution. Can you please add feature in terminal? Actually it not working sudo doplhin Can you please repair it? Thank you very much My dolphin version dolphin 24.08.1 -- You are receiving this mail because: You are watching all bug changes.
[kio-admin] [Bug 501550] Dolphin kio-admin faliure: Unable to create KIO worker. Unknown protocol 'admin' despite kio-admin being installed
https://bugs.kde.org/show_bug.cgi?id=501550 --- Comment #7 from Matej --- Here is more information about this bug https://bugs.launchpad.net/ubuntu/+source/kio-admin/+bug/2084720?comments=all -- You are receiving this mail because: You are watching all bug changes.
[kdeconnect] [Bug 501241] Issue with connection between two Android phones on version 1.33.1
https://bugs.kde.org/show_bug.cgi?id=501241 --- Comment #14 from Matej --- Created attachment 179387 --> https://bugs.kde.org/attachment.cgi?id=179387&action=edit I add log from Android 10 in attachment. I add log from Android 10 in attachment. Thank you very much for repair. Based my phones, based my testings, latest version works correct on Android versions 13 and 14. Thank you very much for repair! But on Android 7 and Android 10 not work correct. -- You are receiving this mail because: You are watching all bug changes.
[kdeconnect] [Bug 501241] Issue with connection between two Android phones on version 1.33.1
https://bugs.kde.org/show_bug.cgi?id=501241 --- Comment #15 from Matej --- Created attachment 179389 --> https://bugs.kde.org/attachment.cgi?id=179389&action=edit Android 10 second log, only one device was visible and connected. Other Android devices was not visible in Android 10. Android 10 second log, only one device was visible and connected. Other Android devices was not visible in Android 10. More info in attachment -- You are receiving this mail because: You are watching all bug changes.
[kdeconnect] [Bug 501241] Issue with connection between two Android phones on version 1.33.1
https://bugs.kde.org/show_bug.cgi?id=501241 --- Comment #16 from Matej --- After some complications I connected successfully Android 10 With Android 13 and 14. It is all OK. Only Android 7 not works correct. Other versions are OK -- You are receiving this mail because: You are watching all bug changes.
[dolphin] [Bug 501550] Open as root not work correct on Kubuntu
https://bugs.kde.org/show_bug.cgi?id=501550 --- Comment #2 from Matej --- Avraham Thank you very much for answer. But it not work. On Kubuntu is blocked root in Dolphin. More info in video https://youtu.be/lMBLs66jWDE Actually work in terminal only this command pkexec env DISPLAY=$DISPLAY XAUTHORITY=$XAUTHORITY KDE_SESSION_VERSION=5 KDE_FULL_SESSION=true dolphin This guide not work in my PC. I use most innovative encryption FSCRYPT of home folder. I am not sure whether it is reason of issue https://www.linux.org/threads/kubuntu-22-04-tip.41959/ https://wiki.archlinux.org/title/Fscrypt -- You are receiving this mail because: You are watching all bug changes.
[dolphin] [Bug 501550] Open as root not work correct on Kubuntu
https://bugs.kde.org/show_bug.cgi?id=501550 --- Comment #3 from Matej --- This command work for Kubuntu. But it is not so simple as with nautilus or nemo sudo SUDO_USER= dolphin -- You are receiving this mail because: You are watching all bug changes.
[Discover] [Bug 503002] New: Kubuntu version 25.04 issue with flatpak
https://bugs.kde.org/show_bug.cgi?id=503002 Bug ID: 503002 Summary: Kubuntu version 25.04 issue with flatpak Classification: Applications Product: Discover Version: 6.3.4 Platform: Kubuntu OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: Flatpak Backend Assignee: plasma-b...@kde.org Reporter: ekon...@atlas.sk CC: aleix...@kde.org, jgrul...@redhat.com, trav...@redhat.com Target Milestone: --- Created attachment 180398 --> https://bugs.kde.org/attachment.cgi?id=180398&action=edit Screen video On Kubuntu version 25.04 is bug. If I chose snap, switch back to flatpak is no possible. More information in video. Dear developers, can you please repair it? More info in attachments Video and picture -- You are receiving this mail because: You are watching all bug changes.
[Discover] [Bug 503002] Kubuntu version 25.04 issue with flatpak. Issue with flatpak / snap switch in Discover
https://bugs.kde.org/show_bug.cgi?id=503002 Matej changed: What|Removed |Added Summary|Kubuntu version 25.04 issue |Kubuntu version 25.04 issue |with flatpak|with flatpak. Issue with ||flatpak / snap switch in ||Discover -- You are receiving this mail because: You are watching all bug changes.
[Discover] [Bug 503002] Kubuntu version 25.04 issue with flatpak
https://bugs.kde.org/show_bug.cgi?id=503002 --- Comment #1 from Matej --- Created attachment 180399 --> https://bugs.kde.org/attachment.cgi?id=180399&action=edit Screenshot picture, version -- You are receiving this mail because: You are watching all bug changes.
[kdeconnect] [Bug 501078] Critical error on latest Android version of KDE connect version 1.33.0. Create connection is no possible
https://bugs.kde.org/show_bug.cgi?id=501078 --- Comment #3 from Matej --- Thank you very much for repair Albert between phone and GSConnect. But between Android phones is this bug not repaired -- You are receiving this mail because: You are watching all bug changes.
[kdeconnect] [Bug 501241] New: Issue with connection between two Android phones on version 1.33.1
https://bugs.kde.org/show_bug.cgi?id=501241 Bug ID: 501241 Summary: Issue with connection between two Android phones on version 1.33.1 Classification: Applications Product: kdeconnect Version: unspecified Platform: Android OS: Android 14.x Status: REPORTED Severity: critical Priority: NOR Component: android-application Assignee: albertv...@gmail.com Reporter: ekon...@atlas.sk CC: andrew.g.r.hol...@gmail.com Target Milestone: --- Dear developers. Can you please repair? Critical error. Connection is no possible on version 1.33.1 On version 1.32.11 all work correct. Testing connection on my phones: Samsung Galaxy Android 14 Honor with Android 7 Thank you very much -- You are receiving this mail because: You are watching all bug changes.
[kdeconnect] [Bug 501241] Issue with connection between two Android phones on version 1.33.1
https://bugs.kde.org/show_bug.cgi?id=501241 --- Comment #3 from Matej --- Created attachment 179247 --> https://bugs.kde.org/attachment.cgi?id=179247&action=edit Logs created during try connect KDE connect Android phones Thank you very much for your answer, Albert. I am sorry, I am not programmer, and I created log first time in my life. I am not sure whether it is OK. I used this guide. https://stackoverflow.com/questions/70318755/software-to-show-android-logcat I am not removed limitations from me terminal (max number of characters). If you need, I can create without limitation. I add txt files in the attachment. Logs created during try connect KDE connect Android phones -- You are receiving this mail because: You are watching all bug changes.
[kdeconnect] [Bug 501078] New: Critical error on latest Android version of KDE connect version 1.33.0. Create connection is no possible
https://bugs.kde.org/show_bug.cgi?id=501078 Bug ID: 501078 Summary: Critical error on latest Android version of KDE connect version 1.33.0. Create connection is no possible Classification: Applications Product: kdeconnect Version: unspecified Platform: Android OS: Linux Status: REPORTED Severity: critical Priority: NOR Component: android-application Assignee: albertv...@gmail.com Reporter: ekon...@atlas.sk CC: andrew.g.r.hol...@gmail.com Target Milestone: --- Dear developers! On last Android version on KDE connect is bug. Create connection between Android-Android and Android-GSConnect is no possible. On older Android version all work correct. Can you please repair? (I use GSConnect on Ubuntu) Thank you very much -- You are receiving this mail because: You are watching all bug changes.
[kdeconnect] [Bug 501241] Issue with connection between two Android phones on version 1.33.1
https://bugs.kde.org/show_bug.cgi?id=501241 --- Comment #5 from Matej --- Thank you Albert, I created file based on Linux Ubuntu and Android USB cable connection. TXT file is 41 MB. You can find log here on mega.nz cloud https://mega.nz/file/Nnwm1Q4J#u6UjofwGdtyT8RljU-EjWERHbMYcCa9cFmdRnaC8sSE It is without terminal characters limitation. I fully closed KDE connect (closed on background too) and then open again. Turn off Wifi connection on short time. (Main time is Wifi turn on, of course) I used this command: adb shell logcat Is it OK? Of you have any better command for me terminal (for example with any filter), send me. -- You are receiving this mail because: You are watching all bug changes.
[kdeconnect] [Bug 501241] Issue with connection between two Android phones on version 1.33.1
https://bugs.kde.org/show_bug.cgi?id=501241 --- Comment #8 from Matej --- I created this log from Samsung Android 13 phone and I tried connect with Android 7 phone. On both phones I was installed version of KDE connect from mega.nz link Unfortunately, the same issue with connection. Phones was not connected https://mega.nz/file/9vYBlT6S#j5-ZQQHmQ74XD3CFIWaclcW3pfnukxUDkHZ_hNoGdXY -- You are receiving this mail because: You are watching all bug changes.
[kdeconnect] [Bug 501241] Issue with connection between two Android phones on version 1.33.1
https://bugs.kde.org/show_bug.cgi?id=501241 --- Comment #13 from Matej --- Logs from Android 7 is in attachment in previous comment. -- You are receiving this mail because: You are watching all bug changes.
[kdeconnect] [Bug 501078] Critical error on latest Android version of KDE connect version 1.33.0. Create connection is no possible
https://bugs.kde.org/show_bug.cgi?id=501078 --- Comment #2 from Matej --- Thank you very much Albert for willingness -- You are receiving this mail because: You are watching all bug changes.
[kdeconnect] [Bug 501241] Issue with connection between two Android phones on version 1.33.1
https://bugs.kde.org/show_bug.cgi?id=501241 --- Comment #11 from Matej --- Thank you very much, Albert, for your development too :) -- You are receiving this mail because: You are watching all bug changes.
[kio-admin] [Bug 501550] Dolphin kio-admin faliure: Unable to create KIO worker. Unknown protocol 'admin' despite kio-admin being installed
https://bugs.kde.org/show_bug.cgi?id=501550 --- Comment #6 from Matej --- Thank you very much John for answer. I contacted Kubuntu developers based your advice. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 449163] Plasma panel visually freezes after some time under Wayland
https://bugs.kde.org/show_bug.cgi?id=449163 --- Comment #31 from Matej Mrenica --- I've also been running the MR and so far so good. -- You are receiving this mail because: You are watching all bug changes.
[Powerdevil] [Bug 438716] Lid close leads to suspend even when external monitor is attached
https://bugs.kde.org/show_bug.cgi?id=438716 --- Comment #23 from Matej Mrenica --- (In reply to ita84 from comment #22) > Just updated to Plasma 5.24 and the issue has been fixed for me: now closing > the laptop lid in a Wayland session doesn't trigger suspend anymore, and > selecting Shutdown shuts the laptop down correctly instead of suspending it. > Thanks! Same here. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 449836] Compose key does not work
https://bugs.kde.org/show_bug.cgi?id=449836 Matej Mrenica changed: What|Removed |Added CC||matejm98m...@gmail.com --- Comment #1 from Matej Mrenica --- But only with Context menu key, right? Because here it works correctly with right Alt. -- You are receiving this mail because: You are watching all bug changes.
[plasma-browser-integration] [Bug 450070] New: Media player not detected on BBC Sounds
https://bugs.kde.org/show_bug.cgi?id=450070 Bug ID: 450070 Summary: Media player not detected on BBC Sounds Product: plasma-browser-integration Version: unspecified Platform: Archlinux Packages OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: Firefox Assignee: k...@privat.broulik.de Reporter: matejm98m...@gmail.com Target Milestone: --- SUMMARY Visit this link: https://www.bbc.co.uk/sounds/play/w3ct1jzw and start playback. OBSERVED RESULT No media controls appear in system tray. EXPECTED RESULT They do appear. SOFTWARE/OS VERSIONS KDE Plasma Version: 5.24.0 KDE Frameworks Version: 5.90 Qt Version: 5.15.2 ADDITIONAL INFORMATION The same link opened in Chromium works correctly. -- You are receiving this mail because: You are watching all bug changes.
[plasma-browser-integration] [Bug 450070] Media player not detected on BBC Sounds
https://bugs.kde.org/show_bug.cgi?id=450070 Matej Mrenica changed: What|Removed |Added Status|REPORTED|RESOLVED CC||matejm98m...@gmail.com Resolution|--- |FIXED --- Comment #1 from Matej Mrenica --- Never mind, after a browser restart it works correctly now, sorry. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 450445] kwin wayland crash spa_list_insert (elem=0x55c3442d8320, list=0x0) at ../pipewire/spa/include/spa/utils/list.h:58
https://bugs.kde.org/show_bug.cgi?id=450445 Matej Mrenica changed: What|Removed |Added Status|REPORTED|CONFIRMED CC||matejm98m...@gmail.com Ever confirmed|0 |1 --- Comment #1 from Matej Mrenica --- Same crash here, might be a Pipewire issue tho. On the other hand, even if it is, kwin_wayland (and thus the entire session) shouldn't crash. Log: https://pastebin.com/sLE83XF3 -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 450445] kwin wayland crash spa_list_insert (elem=0x55c3442d8320, list=0x0) at ../pipewire/spa/include/spa/utils/list.h:58
https://bugs.kde.org/show_bug.cgi?id=450445 --- Comment #3 from Matej Mrenica --- After you updated to new pipewire, did you reboot, or not? I am guessing that if we rebooted the system right there it wouldn't crash after a while. There is another reported crash that happens when pipewire is updated but not rebooted yet (449568). These two issues might be related or even the same. -- You are receiving this mail because: You are watching all bug changes.
[Powerdevil] [Bug 450551] New: Battery charge limit is not preserved after reboot
https://bugs.kde.org/show_bug.cgi?id=450551 Bug ID: 450551 Summary: Battery charge limit is not preserved after reboot Product: Powerdevil Version: 5.24.1 Platform: Archlinux Packages OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: plasma-b...@kde.org Reporter: matejm98m...@gmail.com Target Milestone: --- SUMMARY ASUS laptop, battery charge limit can be set and battery stops charging when the limit is reached (or when battery is 1-2% under the limit). The issue is that on every reboot the configured charge limit is reset to 100%. TLP also allows to configure a battery charge limit and this one is working as expected. (I am not running tlp at this moment, nor anything else that chages this setting) More info about setting battery charge limit on ASUS devices: https://wiki.archlinux.org/title/Laptop/ASUS#Battery_charge_threshold SOFTWARE/OS VERSIONS KDE Frameworks Version: 5.91 Qt Version: 5.15.2 -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 450564] New: Kwin_wayland crash in KWin::KscreenEffect::switchState()
https://bugs.kde.org/show_bug.cgi?id=450564 Bug ID: 450564 Summary: Kwin_wayland crash in KWin::KscreenEffect::switchState() Product: kwin Version: 5.24.1 Platform: Archlinux Packages OS: Linux Status: REPORTED Severity: crash Priority: NOR Component: wayland-generic Assignee: kwin-bugs-n...@kde.org Reporter: matejm98m...@gmail.com Target Milestone: --- SUMMARY Kwin_wayland crashed while being idle and screen was locked. BT: #0 0x7f7951664144 in xcb_send_request_with_fds64 () at /usr/lib/libxcb.so.1 #1 0x7f79516646ba in xcb_send_request () at /usr/lib/libxcb.so.1 #2 0x7f795166b303 in xcb_change_property () at /usr/lib/libxcb.so.1 #3 0x560ba78e97d7 in KWin::KscreenEffect::switchState(KWin::KscreenEffect::ScreenState&) (state=..., this=0x560ba95a1fe0) at /usr/src/debug/kwin-5.24.1/src/effects/kscreen/kscreen.cpp:214 #4 KWin::KscreenEffect::prePaintScreen(KWin::ScreenPrePaintData&, std::chrono::duration >) (this=0x560ba95a1fe0, data=..., presentTime=...) at /usr/src/debug/kwin-5.24.1/src/effects/kscreen/kscreen.cpp:108 #5 0x7f7952e15aa2 in KWin::EffectsHandlerImpl::prePaintScreen(KWin::ScreenPrePaintData&, std::chrono::duration >) (this=0x560ba8b41040, data=, presentTime=...) at /usr/src/debug/kwin-5.24.1/src/effects.cpp:380 #6 0x7f7952e848bc in KWin::Scene::paintScreen(QRegion const&, QRegion const&, QRegion*, QRegion*, KWin::RenderLoop*, QMatrix4x4 const&) (this=0x560ba873a360, damage=, repaint=..., updateRegion=0x7ffe7060d4f0, validRegion=0x7ffe7060d4e8, renderLoop=, projection=...) at /usr/src/debug/kwin-5.24.1/src/scene.cpp:259 #7 0x7f7952f4af27 in KWin::SceneOpenGL::paint(KWin::AbstractOutput*, QRegion const&, QList const&, KWin::RenderLoop*) (this=0x560ba873a360, output=0x560ba874ccc0, damage=..., toplevels=, renderLoop=0x560ba8a6cf50) at /usr/src/debug/kwin-5.24.1/src/scenes/opengl/scene_opengl.cpp:259 #8 0x7f7952de7814 in KWin::Compositor::composite(KWin::RenderLoop*) (this=0x560ba88ed600, renderLoop=0x560ba8a6cf50) at /usr/src/debug/kwin-5.24.1/src/composite.cpp:633 #9 0x7f7950d8a9d3 in QtPrivate::QSlotObjectBase::call(QObject*, void**) (a=0x7ffe7060d750, r=, this=0x560ba86549e0, this=, r=, a=) at ../../include/QtCore/../../src/corelib/kernel/qobjectdefs_impl.h:398 #10 doActivate(QObject*, int, void**) (sender=0x560ba8a6cf50, signal_index=5, argv=0x7ffe7060d750) at kernel/qobject.cpp:3886 #11 0x7f7952da57b7 in KWin::RenderLoop::frameRequested(KWin::RenderLoop*) (this=, _t1=) at /usr/src/debug/build/src/kwin_autogen/EWIEGA46WW/moc_renderloop.cpp:206 #12 0x7f7952e76eb8 in KWin::RenderLoopPrivate::dispatch() (this=0x560ba8a70c80) at /usr/src/debug/kwin-5.24.1/src/renderloop.cpp:150 #13 0x7f7950d8a9d3 in QtPrivate::QSlotObjectBase::call(QObject*, void**) (a=0x7ffe7060d870, r=, this=0x560ba8a6c810, this=, r=, a=) at ../../include/QtCore/../../src/corelib/kernel/qobjectdefs_impl.h:398 #14 doActivate(QObject*, int, void**) (sender=0x560ba8a70c98, signal_index=3, argv=0x7ffe7060d870) at kernel/qobject.cpp:3886 #15 0x7f7950d8cc0f in QTimer::timeout(QTimer::QPrivateSignal) (this=, _t1=...) at .moc/moc_qtimer.cpp:205 --Type for more, q to quit, c to continue without paging-- #16 0x7f7950d7dd56 in QObject::event(QEvent*) (this=0x560ba8a70c98, e=0x7ffe7060da10) at kernel/qobject.cpp:1291 #17 0x7f79518161a6 in QApplicationPrivate::notify_helper(QObject*, QEvent*) (this=, receiver=0x560ba8a70c98, e=0x7ffe7060da10) at kernel/qapplication.cpp:3632 #18 0x7f7950d59b9a in QCoreApplication::notifyInternal2(QObject*, QEvent*) (receiver=0x560ba8a70c98, event=0x7ffe7060da10) at kernel/qcoreapplication.cpp:1064 #19 0x7f7950da5335 in QTimerInfoList::activateTimers() (this=0x560ba85e69c8) at kernel/qtimerinfo_unix.cpp:643 #20 0x7f7950da57d2 in QEventDispatcherUNIX::processEvents(QFlags) (this=, flags=...) at kernel/qeventdispatcher_unix.cpp:516 #21 0x560ba79979e2 in QUnixEventDispatcherQPA::processEvents(QFlags) () #22 0x7f7950d51e6b in QEventLoop::exec(QFlags) (this=0x7ffe7060dbb0, flags=...) at ../../include/QtCore/../../src/corelib/global/qflags.h:69 #23 0x7f7950d5d5c7 in QCoreApplication::exec() () at ../../include/QtCore/../../src/corelib/global/qflags.h:121 #24 0x7f7951128332 in QGuiApplication::exec() () at kernel/qguiapplication.cpp:1867 #25 0x7f795181452a in QApplication::exec() () at kernel/qapplication.cpp:2824 #26 0x560ba78a62da in main(int, char**) (argc=, argv=) at /usr/src/debug/kwin-5.24.1/src/main_wayland.cpp:727 -- You are receiving this mail because: You are watching all bug changes.
[Powerdevil] [Bug 450551] Battery charge limit is not preserved after reboot
https://bugs.kde.org/show_bug.cgi?id=450551 Matej Mrenica changed: What|Removed |Added CC||matejm98m...@gmail.com --- Comment #2 from Matej Mrenica --- (In reply to galder from comment #1) > Hello, > Do you know if Plasma has specifics battery settings for this feature? > If not, I think we need set the ticket as feature request. > > Regards I am not sure I understand your question, powerdevil has the ability to set battery charge limit. The issue I am reporting is that the value is not saved properly / is reset after reboot. -- You are receiving this mail because: You are watching all bug changes.
[Powerdevil] [Bug 450551] Battery charge limit is not preserved after reboot
https://bugs.kde.org/show_bug.cgi?id=450551 Matej Mrenica changed: What|Removed |Added Resolution|WAITINGFORINFO |--- Status|NEEDSINFO |REPORTED --- Comment #8 from Matej Mrenica --- (In reply to Nate Graham from comment #5) > 1. What kernel version are you using? 5.16.10 > 2. What is the output of `cat > /sys/class/power_supply/BAT*/charge_control_end_threshold` right after you > set the charge limit? It's the value I set, like 60. > 3. And what is the output of that command after you reboot? 100 (In reply to Kai Uwe Broulik from comment #7) > There's no persistency in PowerDevil. I assumed that setting would be > persistet by the device's SMC. I dd not want to bluntly write it on every > boot in fear of wearing down some firmware flash storage or something. So, user has to reset the setting on every boot? Is that the intended behavior? -- You are receiving this mail because: You are watching all bug changes.
[Powerdevil] [Bug 450551] Battery charge limit is not preserved after reboot
https://bugs.kde.org/show_bug.cgi?id=450551 --- Comment #10 from Matej Mrenica --- (In reply to Nate Graham from comment #9) > No, we're expecting the system to remember the charge threshold value once > set. > > So there are two possibilities here: > 1. The device's SMC erases it. If this is what's happening, we will need to > write it on every login if it's been changed. > 2. Something else on your computer is resetting it. > > It might be sane to write the value on login if it's gotten changed from > what powerdevil set it to. That would cover case #1 without unduly wearing > out the flash memory, since for most people it gets remembered and wouldn't > need to be written again. For those whose settings get erased automatically, > there's no alternative anyway. >From the Arch Wiki (https://wiki.archlinux.org/title/Laptop/ASUS#Battery_charge_threshold): ... By default this value is set to 100 and reset on every power cycle. ... IIRC when I used TLP my battery charge limit was remembered after a reboot, so TLP has to re-set this value every time. And so does Windows. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 454349] Searching for something automatically selects the second item instead of the first
https://bugs.kde.org/show_bug.cgi?id=454349 Matej Mrenica changed: What|Removed |Added CC||matejm98m...@gmail.com, ||mikel5...@gmail.com, ||noaha...@gmail.com Component|Application Menu (Kicker) |Application Launcher ||(Kickoff) --- Comment #4 from Matej Mrenica --- I did mean Kickoff , sorry. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 454394] moving applets/widgets freezes plasma for some time
https://bugs.kde.org/show_bug.cgi?id=454394 --- Comment #3 from Matej Starc --- (In reply to Nate Graham from comment #2) > Can you upgrade to the Plasma 5.25 beta and see if the issue is fixed in > that release? We did a lot of code cleanup for the panel. The bug is still present, although it's not as bad as before. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 454501] New: floating panels parent item has effects
https://bugs.kde.org/show_bug.cgi?id=454501 Bug ID: 454501 Summary: floating panels parent item has effects Product: plasmashell Version: 5.24.90 Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: Panel Assignee: plasma-b...@kde.org Reporter: matej.sta...@gmail.com CC: niccolo.venera...@gmail.com Target Milestone: 1.0 SUMMARY Floating panel spacer parent item has background effects and a border. STEPS TO REPRODUCE 1. Set panel to floating mode 2. Observe the background around the panel OBSERVED RESULT The parent item for the floating panel has a border and background effects (shade, etc.) EXPECTED RESULT It shouldn't have those effects. SOFTWARE/OS VERSIONS Operating System: Arch Linux KDE Plasma Version: 5.24.90 KDE Frameworks Version: 5.94.0 Qt Version: 5.15.4 Kernel Version: 5.17.9-arch1-1 (64-bit) Graphics Platform: Wayland Processors: 12 × Intel® Core™ i7-8700 CPU @ 3.20GHz Memory: 15.5 GiB of RAM Graphics Processor: AMD Radeon RX 480 Graphics -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 454502] New: floating panel fills up parent item used for spacing
https://bugs.kde.org/show_bug.cgi?id=454502 Bug ID: 454502 Summary: floating panel fills up parent item used for spacing Product: plasmashell Version: 5.24.90 Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: Panel Assignee: plasma-b...@kde.org Reporter: matej.sta...@gmail.com CC: niccolo.venera...@gmail.com Target Milestone: 1.0 Created attachment 149271 --> https://bugs.kde.org/attachment.cgi?id=149271&action=edit bug image SUMMARY Floating panel fills up parent widget used for spacing on auto-hide, when having a maximized window. STEPS TO REPRODUCE 1. Set panel to floating and autohide 2. Open an application 3. Maximize the application EXPECTED RESULT I assume it should only have spacing under, left, right of the panel SOFTWARE/OS VERSIONS Operating System: Arch Linux KDE Plasma Version: 5.24.90 KDE Frameworks Version: 5.94.0 Qt Version: 5.15.4 Kernel Version: 5.17.9-arch1-1 (64-bit) Graphics Platform: Wayland Processors: 12 × Intel® Core™ i7-8700 CPU @ 3.20GHz Memory: 15.5 GiB of RAM Graphics Processor: AMD Radeon RX 480 Graphics -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 454502] floating panel fills up parent item used for spacing
https://bugs.kde.org/show_bug.cgi?id=454502 Matej Starc changed: What|Removed |Added Attachment #149271|0 |1 is obsolete|| --- Comment #1 from Matej Starc --- Created attachment 149272 --> https://bugs.kde.org/attachment.cgi?id=149272&action=edit bug image -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 454503] New: plasma floating panel does not show in fullscreen app
https://bugs.kde.org/show_bug.cgi?id=454503 Bug ID: 454503 Summary: plasma floating panel does not show in fullscreen app Product: plasmashell Version: 5.24.90 Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: Panel Assignee: plasma-b...@kde.org Reporter: matej.sta...@gmail.com CC: niccolo.venera...@gmail.com Target Milestone: 1.0 SUMMARY Panel set to autohide does not show when a fullscreen app is open. STEPS TO REPRODUCE 1. Set panel to autohide 2. Open app and set it to fullscreen (CTRL+F11) 3. Try using the panel OBSERVED RESULT It shows that quick corners animation indication that something is going to happen if you hover to that position, but nothing happens after doing so. EXPECTED RESULT Not showing the panel is an UX choice, but still showing the blue animation indication that hovering there will show the panel should be fixed (it shouldn't display anything). SOFTWARE/OS VERSIONS Operating System: Arch Linux KDE Plasma Version: 5.24.90 KDE Frameworks Version: 5.94.0 Qt Version: 5.15.4 Kernel Version: 5.17.9-arch1-1 (64-bit) Graphics Platform: Wayland Processors: 12 × Intel® Core™ i7-8700 CPU @ 3.20GHz Memory: 15.5 GiB of RAM Graphics Processor: AMD Radeon RX 480 Graphics -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 454527] New: bottom and right size glitch on window resize
https://bugs.kde.org/show_bug.cgi?id=454527 Bug ID: 454527 Summary: bottom and right size glitch on window resize Product: kwin Version: 5.24.90 Platform: Archlinux Packages OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: wayland-generic Assignee: kwin-bugs-n...@kde.org Reporter: matej.sta...@gmail.com Target Milestone: --- SUMMARY Right and bottom sides glitch out when resizing. STEPS TO REPRODUCE 1. Open any app (I tested it with dolphin, neochat, and some others) 2. Try resizing from top left corner. OBSERVED RESULT Right and bottom side expand in size and return to the intended size. Bug video: https://cloud.aljaxus.eu/index.php/s/gXbtWrLRRjNz9z7 EXPECTED RESULT Right and bottom size should not resize because we are resizing from top left corner. Konsole does not experience this bug when I tested it. SOFTWARE/OS VERSIONS Operating System: Arch Linux KDE Plasma Version: 5.24.90 KDE Frameworks Version: 5.94.0 Qt Version: 5.15.4 Kernel Version: 5.17.9-arch1-1 (64-bit) Graphics Platform: Wayland Processors: 12 × Intel® Core™ i7-8700 CPU @ 3.20GHz Memory: 15.5 GiB of RAM Graphics Processor: AMD Radeon RX 480 Graphics -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 454548] New: panel widgets reversed on panel creation
https://bugs.kde.org/show_bug.cgi?id=454548 Bug ID: 454548 Summary: panel widgets reversed on panel creation Product: plasmashell Version: 5.24.90 Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: Panel Assignee: plasma-b...@kde.org Reporter: matej.sta...@gmail.com CC: niccolo.venera...@gmail.com Target Milestone: 1.0 SUMMARY When creating a default panel, every widget is reversed. STEPS TO REPRODUCE 1. Right click 2. Add panel 3. Default panel OBSERVED RESULT Widgets are reversed (app launcher is on the right and show desktop widget is on the left) SOFTWARE/OS VERSIONS Operating System: Arch Linux KDE Plasma Version: 5.24.90 KDE Frameworks Version: 5.94.0 Qt Version: 5.15.4 Kernel Version: 5.17.9-arch1-1 (64-bit) Graphics Platform: X11 Processors: 12 × Intel® Core™ i7-8700 CPU @ 3.20GHz Memory: 15.5 GiB of RAM Graphics Processor: AMD Radeon RX 480 Graphics -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 454548] panel widgets reversed on panel creation
https://bugs.kde.org/show_bug.cgi?id=454548 Matej Starc changed: What|Removed |Added Platform|Other |Archlinux Packages -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 454548] panel widgets reversed on panel creation
https://bugs.kde.org/show_bug.cgi?id=454548 Matej Starc changed: What|Removed |Added Keywords||release_blocker, usability -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 454549] New: app launcher still responds to activation key after being deleted
https://bugs.kde.org/show_bug.cgi?id=454549 Bug ID: 454549 Summary: app launcher still responds to activation key after being deleted Product: plasmashell Version: 5.24.90 Platform: Archlinux Packages OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: Panel Assignee: plasma-b...@kde.org Reporter: matej.sta...@gmail.com CC: niccolo.venera...@gmail.com Target Milestone: 1.0 SUMMARY Because of some problems (another bug report incoming) I had to delete both panels, and when I pressed my super key and noticed that the application launcher menu opened, even though I just delete the widget. STEPS TO REPRODUCE 1. Create a default panel 2. Set your keyboard shortcut 3. Delete the panel 4. Press the shortcut you assigned OBSERVED RESULT Application launcher menu can be shown even after widget is removed. SOFTWARE/OS VERSIONS Operating System: Arch Linux KDE Plasma Version: 5.24.90 KDE Frameworks Version: 5.94.0 Qt Version: 5.15.4 Kernel Version: 5.17.9-arch1-1 (64-bit) Graphics Platform: X11 Processors: 12 × Intel® Core™ i7-8700 CPU @ 3.20GHz Memory: 15.5 GiB of RAM Graphics Processor: AMD Radeon RX 480 Graphics -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 454549] app launcher still responds to activation key after being deleted
https://bugs.kde.org/show_bug.cgi?id=454549 --- Comment #1 from Matej Starc --- Created attachment 149302 --> https://bugs.kde.org/attachment.cgi?id=149302&action=edit bug screenshot -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 454501] floating panels parent item has effects
https://bugs.kde.org/show_bug.cgi?id=454501 --- Comment #1 from Matej Starc --- This is no longer present in my case. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 454548] panel widgets reversed on panel creation
https://bugs.kde.org/show_bug.cgi?id=454548 --- Comment #1 from Matej Starc --- Screenshot file too big. https://cloud.aljaxus.eu/index.php/s/Sib4tqgG79GmfzB -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 454550] New: widgets stacked on the left side
https://bugs.kde.org/show_bug.cgi?id=454550 Bug ID: 454550 Summary: widgets stacked on the left side Product: plasmashell Version: 5.24.90 Platform: Archlinux Packages OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: Panel Assignee: plasma-b...@kde.org Reporter: matej.sta...@gmail.com CC: niccolo.venera...@gmail.com Target Milestone: 1.0 SUMMARY When I first booted into plasma 5.25 beta, I noticed all my widgets were positioned to the left. This would cause problems if not fixed when released. STEPS TO REPRODUCE It happened to me after reboot. OBSERVED RESULT All widgets are stacked on the left side (glitched together). SOFTWARE/OS VERSIONS Operating System: Arch Linux KDE Plasma Version: 5.24.90 KDE Frameworks Version: 5.94.0 Qt Version: 5.15.4 Kernel Version: 5.17.9-arch1-1 (64-bit) Graphics Platform: X11 Processors: 12 × Intel® Core™ i7-8700 CPU @ 3.20GHz Memory: 15.5 GiB of RAM Graphics Processor: AMD Radeon RX 480 Graphics -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 454550] Widgets glitched on the left side (stack on top of each other)
https://bugs.kde.org/show_bug.cgi?id=454550 Matej Starc changed: What|Removed |Added Summary|widgets stacked on the left |Widgets glitched on the |side|left side (stack on top of ||each other) -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 454551] New: panels cause a crash
https://bugs.kde.org/show_bug.cgi?id=454551 Bug ID: 454551 Summary: panels cause a crash Product: plasmashell Version: 5.24.90 Platform: Archlinux Packages OS: Linux Status: REPORTED Severity: crash Priority: NOR Component: generic-crash Assignee: plasma-b...@kde.org Reporter: matej.sta...@gmail.com Target Milestone: 1.0 SUMMARY Plasma shell crashes because of panels. When I logged in into plasma wayland session, I noticed that my widgets were all stacked to the left side (see additional information), and then the screen went black for a second and the shell restarted. This went on even after reboot, until I removed both panels. STEPS TO REPRODUCE This happened to be after reboot, so my best bet would be to use this release version, use the default panel and reboot. OBSERVED RESULT Plasmashell restarts until panels are removed. SOFTWARE/OS VERSIONS Operating System: Arch Linux KDE Plasma Version: 5.24.90 KDE Frameworks Version: 5.94.0 Qt Version: 5.15.4 Kernel Version: 5.17.9-arch1-1 (64-bit) Graphics Platform: X11 Processors: 12 × Intel® Core™ i7-8700 CPU @ 3.20GHz Memory: 15.5 GiB of RAM Graphics Processor: AMD Radeon RX 480 Graphics ADDITIONAL INFORMATION The cause might be https://bugs.kde.org/show_bug.cgi?id=454550 -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 454551] panels cause a crash
https://bugs.kde.org/show_bug.cgi?id=454551 Matej Starc changed: What|Removed |Added Keywords||release_blocker, usability -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 454550] Widgets glitched on the left side (stack on top of each other)
https://bugs.kde.org/show_bug.cgi?id=454550 --- Comment #1 from Matej Starc --- Created attachment 149306 --> https://bugs.kde.org/attachment.cgi?id=149306&action=edit bug screenshot -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 454550] Widgets glitched on the left side (stack on top of each other)
https://bugs.kde.org/show_bug.cgi?id=454550 --- Comment #2 from Matej Starc --- Created attachment 149308 --> https://bugs.kde.org/attachment.cgi?id=149308&action=edit how to make it glitched -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 454550] Widgets glitched on the left side (stack on top of each other)
https://bugs.kde.org/show_bug.cgi?id=454550 --- Comment #3 from Matej Starc --- Created attachment 149309 --> https://bugs.kde.org/attachment.cgi?id=149309&action=edit after it is glitched -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 454551] panels cause a crash
https://bugs.kde.org/show_bug.cgi?id=454551 --- Comment #3 from Matej Starc --- (In reply to Bacteria from comment #1) > Does the problem goes away if you remove all the application icons from the > panel? This problem only occurred to me twice (the first time, after that I rebooted, and it happened again. I fixed it by removing the panels). I haven't been able to reproduce the issue since. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 454550] Widgets glitched on the left side (stack on top of each other)
https://bugs.kde.org/show_bug.cgi?id=454550 --- Comment #4 from Matej Starc --- Probably a duplicate of https://bugs.kde.org/show_bug.cgi?id=454105/ -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 454551] panels cause a crash
https://bugs.kde.org/show_bug.cgi?id=454551 --- Comment #4 from Matej Starc --- (In reply to Bacteria from comment #2) > Might be due to bug 454105 but it wasn't crashing plasmashell for anyone. Plasmashell crashing was only my guess because of how it behaved. It's also, as you said, that bug is responsible for my issue here. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 454501] floating panels parent item has effects
https://bugs.kde.org/show_bug.cgi?id=454501 --- Comment #2 from Matej Starc --- (In reply to Matej Starc from comment #1) > This is no longer present in my case. It seems it is still present. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 454501] floating panels parent item has effects
https://bugs.kde.org/show_bug.cgi?id=454501 --- Comment #3 from Matej Starc --- Created attachment 149317 --> https://bugs.kde.org/attachment.cgi?id=149317&action=edit screenshot 1 -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 454501] floating panels parent item has effects
https://bugs.kde.org/show_bug.cgi?id=454501 --- Comment #4 from Matej Starc --- (In reply to Matej Starc from comment #3) > Created attachment 149317 [details] > screenshot 1 Both images. https://cloud.aljaxus.eu/index.php/s/yqsRGkeA2FFGARx https://cloud.aljaxus.eu/index.php/s/DXLsq4FkXnGq46P -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 454548] panel widgets reversed on panel creation
https://bugs.kde.org/show_bug.cgi?id=454548 --- Comment #3 from Matej Starc --- (In reply to galder from comment #2) > Hello, > I tried this but I can create a default panel as usual. > > Operating System: Kubuntu 21.10 > KDE Plasma Version: 5.25.80 > KDE Frameworks Version: 5.95.0 > Qt Version: 5.15.2 > Kernel Version: 5.13.0-44-generic (64-bit) > Graphics Platform: X11 > Processors: 8 × Intel® Core™ i7-7700HQ CPU @ 2.80GHz > Memory: 15.5 GiB of RAM > Graphics Processor: NVIDIA GeForce GTX 1060/PCIe/SSE2 This is something I noticed when I was testing plasma. I think it happened on the first successful boot. -- You are receiving this mail because: You are watching all bug changes.
[kscreenlocker] [Bug 454129] [Wayland] Pixelated artifacts when resuming from suspend, which partially reveals content
https://bugs.kde.org/show_bug.cgi?id=454129 Matej Mrenica changed: What|Removed |Added CC||matejm98m...@gmail.com --- Comment #5 from Matej Mrenica --- I have the same issue on almost the same CPU/GPU but It's not a regression, it's been here some time. -- You are receiving this mail because: You are watching all bug changes.
[kscreenlocker] [Bug 454129] [Wayland] Pixelated artifacts when resuming from suspend, which partially reveals content
https://bugs.kde.org/show_bug.cgi?id=454129 Matej Mrenica changed: What|Removed |Added Status|NEEDSINFO |REPORTED Resolution|WAITINGFORINFO |--- --- Comment #7 from Matej Mrenica --- (In reply to Nate Graham from comment #6) > Could it be Bug 316734? I can reproduce Bug 316734, but I don't see any > pixelated artifacts, just the desktop itself for a moment before the screen > locker screen appears. That bug, if I read it correctly, is about lock screen not showing soon enough and desktop being temporarily fully visible. But in this case instead of the desktop being fully visible there is a random mess of pixels that slightly resembles a combination of the lockscreen and whatever was on the desktop previously. That said, these two issues likely have the same root cause. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 454527] bottom and right size glitch on window resize
https://bugs.kde.org/show_bug.cgi?id=454527 --- Comment #2 from Matej Starc --- (In reply to Nate Graham from comment #1) > Cannot reproduce with an Intel HD 620 iGPU. Weird. I have all drivers installed, so drivers shouldn't be an issue. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 454549] app launcher still responds to activation key after being deleted
https://bugs.kde.org/show_bug.cgi?id=454549 --- Comment #3 from Matej Starc --- (In reply to Nate Graham from comment #2) > Did you close the notification that says "a panel was deleted" or is it > still visible somewhere? Ah. So it seems that until that notification ceases to be valid or is closed, the app launcher can still be used. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 454548] panel widgets reversed on panel creation
https://bugs.kde.org/show_bug.cgi?id=454548 --- Comment #5 from Matej Starc --- (In reply to Nate Graham from comment #4) > So you can confirm that it's correct when you create a new panel? It only > happened on the first boot after installing the 5.25 beta? Indeed, if I recall correctly. It hasn't happened since. -- You are receiving this mail because: You are watching all bug changes.
[krunner] [Bug 454352] While typing in Krunner opened above Firefox playing a video, Firefox drops almost all frames
https://bugs.kde.org/show_bug.cgi?id=454352 --- Comment #6 from Matej Mrenica --- This issue seems to be resolved with FF Beta 102 if GPU video decoding (VAAPI) is enabled. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 454549] Deleted panels still respond to keyboard shortcuts until their "undo deleting this panel" notification is closed
https://bugs.kde.org/show_bug.cgi?id=454549 --- Comment #5 from Matej Starc --- (In reply to Nate Graham from comment #4) > Yes, until you close the notification, the panel is just hidden, not > actually deleted. That's so you can undo deleting it using the notification. > > We could probably block keyboard shortcuts that affect it when it's in this > state. Blocking shortcuts would be a good idea. Thanks. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 454549] Deleted panels still respond to keyboard shortcuts until their "undo deleting this panel" notification is closed
https://bugs.kde.org/show_bug.cgi?id=454549 Matej Starc changed: What|Removed |Added Ever confirmed|1 |0 Status|CONFIRMED |REPORTED -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 455262] New: Shadow on a floating panel is misplaced and floating panel has "korners"
https://bugs.kde.org/show_bug.cgi?id=455262 Bug ID: 455262 Summary: Shadow on a floating panel is misplaced and floating panel has "korners" Product: plasmashell Version: 5.25.0 Platform: Archlinux Packages OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: Panel Assignee: plasma-b...@kde.org Reporter: matejm98m...@gmail.com CC: niccolo.venera...@gmail.com Target Milestone: 1.0 Created attachment 149694 --> https://bugs.kde.org/attachment.cgi?id=149694&action=edit Screenshot SUMMARY See the attached screenshot. Basically, shadow of a floating panel is placed based on the bigger size. Second issue (maybe should've been a separate report) is that floating panel has "korners" (white dots) in all 4 of it's corners. SOFTWARE/OS VERSIONS Arch Linux, everything up-to-date ADDITIONAL INFORMATION Tested on wayland -- You are receiving this mail because: You are watching all bug changes.
[frameworks-plasma] [Bug 438644] Broken corners on dialogs, floating panel, applet hints
https://bugs.kde.org/show_bug.cgi?id=438644 --- Comment #39 from Matej Mrenica --- I've tried building and installing https://invent.kde.org/frameworks/plasma-framework/-/merge_requests/522, but it didn't make a difference. Is that supposed to fix the issue? -- You are receiving this mail because: You are watching all bug changes.
[frameworks-plasma] [Bug 438644] Broken corners on dialogs, floating panel, applet hints
https://bugs.kde.org/show_bug.cgi?id=438644 --- Comment #41 from Matej Mrenica --- (In reply to Niccolò Venerandi from comment #40) > That MR is currently not fixing the bug as intended; there's a suggestion > from Nate in the MR that actually works for that specific bug, however I > have not updated the MR as d_ed already said that it would not be the > correct way to approach the issue. > > That said, this bug here is not caused just by the scaling issue that's > being fixed in that MR; as an example, if you have this bug in the top left > corner of your dialog/window/anything, it means it's unrelated to that MR. OK, thanks for the answer. -- You are receiving this mail because: You are watching all bug changes.
[Elisa] [Bug 455402] New: audio progress bar does not update
https://bugs.kde.org/show_bug.cgi?id=455402 Bug ID: 455402 Summary: audio progress bar does not update Product: Elisa Version: 22.04.2 Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: matthieu_gall...@yahoo.fr Reporter: matej.sta...@gmail.com Target Milestone: --- Created attachment 149788 --> https://bugs.kde.org/attachment.cgi?id=149788&action=edit bug screenshot SUMMARY Audio progress bar stuck at the beginning when I try to play an audio file 58 min long. STEPS TO REPRODUCE 1. Open elisa 2. Try playing an audio file that is long enough. OBSERVED RESULT Audio progress bar updates on audio files that are around 4 minutes long, but doesn't do the same when it is 50 minutes long (in my case). SOFTWARE/OS VERSIONS Operating System: Arch Linux KDE Plasma Version: 5.24.5 KDE Frameworks Version: 5.95.0 Qt Version: 5.15.4 Kernel Version: 5.18.3-arch1-1 (64-bit) Graphics Platform: Wayland Processors: 12 × Intel® Core™ i7-8700 CPU @ 3.20GHz Memory: 15.5 GiB of RAM Graphics Processor: AMD Radeon RX 480 Graphics -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 455588] New: Bing POTD doesn't update correctly if it's set to both desktop and lock screen
https://bugs.kde.org/show_bug.cgi?id=455588 Bug ID: 455588 Summary: Bing POTD doesn't update correctly if it's set to both desktop and lock screen Product: plasmashell Version: 5.25.0 Platform: Android OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: Image Wallpaper Assignee: plasma-b...@kde.org Reporter: matejm98m...@gmail.com CC: notm...@gmail.com, qydwhotm...@gmail.com Target Milestone: 1.0 STEPS TO REPRODUCE 1. Set desktop wallpaper to Bing POTD 2. Set lock screen wallpaper to Bing POTD 3. wait 24 hours (or less) OBSERVED RESULT Lock screen wallpaper is updated, desktop wallpaper is not. EXPECTED RESULT Both are updated. SOFTWARE/OS VERSIONS Arch Linux, everything up-to-date. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 455588] Bing POTD doesn't update correctly if it's set to both desktop and lock screen
https://bugs.kde.org/show_bug.cgi?id=455588 Matej Mrenica changed: What|Removed |Added CC||matejm98m...@gmail.com --- Comment #1 from Matej Mrenica --- Currently I set Bing POTD only to my desktop and will see if It updates tomorrow. -- You are receiving this mail because: You are watching all bug changes.
[Elisa] [Bug 465591] New: Elisa does not set how much left/right arrow key should affect the time
https://bugs.kde.org/show_bug.cgi?id=465591 Bug ID: 465591 Summary: Elisa does not set how much left/right arrow key should affect the time Classification: Applications Product: Elisa Version: 22.12.2 Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: matthieu_gall...@yahoo.fr Reporter: matej.st...@protonmail.com Target Milestone: --- SUMMARY When pressing left/right arrow elisa moves the time for only a miniscule amount. Please adjust the slider values so when I have focus on the slider, I can directly go back and forth in the song. STEPS TO REPRODUCE 1. Open elisa 2. Play a song 3. Click on the slider so it gets focus 4. Press left/right arrow key on keyboard OBSERVED RESULT It only moves time for a basically nonexistent amount. EXPECTED RESULT It should move the playing time for 5 sec, or even better, let the user set it in settings. SOFTWARE/OS VERSIONS Operating System: Arch Linux KDE Plasma Version: 5.26.5 KDE Frameworks Version: 5.102.0 Qt Version: 5.15.8 Kernel Version: 6.1.10-arch1-1 (64-bit) Graphics Platform: Wayland Processors: 12 × Intel® Core™ i7-8700 CPU @ 3.20GHz Memory: 15,5 GiB of RAM Graphics Processor: AMD Radeon RX 480 Graphics -- You are receiving this mail because: You are watching all bug changes.
[Elisa] [Bug 465591] Elisa does not set how much left/right arrow key should affect the time
https://bugs.kde.org/show_bug.cgi?id=465591 --- Comment #2 from Matej Starc --- I did not know of this. Cool. But I still suggest adding an option for this to control how much you want to go back/forward. -- You are receiving this mail because: You are watching all bug changes.
[frameworks-kirigami] [Bug 435289] Tab Focus chain should ignore invisible pages
https://bugs.kde.org/show_bug.cgi?id=435289 Matej Starc changed: What|Removed |Added CC||matej.st...@protonmail.com --- Comment #1 from Matej Starc --- Can reproduce. Also, we should mention that if you add a button to the page component, the button will not be showed to that glitched green page. -- You are receiving this mail because: You are watching all bug changes.
[frameworks-kirigami] [Bug 465908] KF6: ActionToolBar.qml: Object or context destroyed during incubation
https://bugs.kde.org/show_bug.cgi?id=465908 Matej Starc changed: What|Removed |Added CC||matej.st...@protonmail.com --- Comment #3 from Matej Starc --- This is a duplicate of https://bugs.kde.org/show_bug.cgi?id=460101. -- You are receiving this mail because: You are watching all bug changes.
[frameworks-kirigami] [Bug 456772] GlobalDrawer glitches when changing isMenu while being open
https://bugs.kde.org/show_bug.cgi?id=456772 Matej Starc changed: What|Removed |Added Latest Commit||https://invent.kde.org/fram ||eworks/kirigami/commit/da80 ||46bce8291d4ed1c43ef31a23ebf ||462363f93 Status|CONFIRMED |RESOLVED Resolution|--- |FIXED --- Comment #3 from Matej Starc --- Git commit da8046bce8291d4ed1c43ef31a23ebf462363f93 by Matej Starc. Committed on 08/02/2023 at 22:17. Pushed by sporknife into branch 'master'. GlobalDrawer: close drawer when isMenu is changed Signed-off-by: Matej Starc M +2-0src/controls/GlobalDrawer.qml M +9-0src/controls/private/globaltoolbar/PageRowGlobalToolBarUI.qml https://invent.kde.org/frameworks/kirigami/commit/da8046bce8291d4ed1c43ef31a23ebf462363f93 -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 466823] New: Icons on desktop disappear regularly after some time, possibly a multi-monitor issue
https://bugs.kde.org/show_bug.cgi?id=466823 Bug ID: 466823 Summary: Icons on desktop disappear regularly after some time, possibly a multi-monitor issue Classification: Plasma Product: plasmashell Version: 5.27.2 Platform: Archlinux OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: Folder Assignee: plasma-b...@kde.org Reporter: matejm98m...@gmail.com CC: h...@kde.org Target Milestone: 1.0 SUMMARY Restarting plasmashell fixes this issue, switching from "Folder view" to "Desktop" and back also fixes the issue. Changing any icon sorting settings doesn't do anything. STEPS TO REPRODUCE 1. Have some icons on your desktop 2. Wait some time or put your laptop to sleep? OBSERVED RESULT Icons will disappear. EXPECTED RESULT They stay there. SOFTWARE/OS VERSIONS KDE Plasma Version: 5.27.2 and before maybe since 5.27 Beta? KDE Frameworks Version: 5.103.0 Qt Version: 5.15.8 ADDITIONAL INFORMATION Both X.org and Wayland. Multi-monitor setup: laptop + external screen, laptop screen is off. IIRC I don't have this issue with only the laptop screen. Also this may not be a Folder view issue. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 449167] Icons on desktop move randomly
https://bugs.kde.org/show_bug.cgi?id=449167 --- Comment #11 from Matej Mrenica --- (In reply to Nate Graham from comment #10) > Matej, is This issue still happening to you in Plasma 5.27.3 or later? I haven't had the chance to test this yet, I will let you know. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 449167] Icons on desktop move randomly
https://bugs.kde.org/show_bug.cgi?id=449167 Matej Mrenica changed: What|Removed |Added Resolution|WAITINGFORINFO |--- Status|NEEDSINFO |REPORTED --- Comment #12 from Matej Mrenica --- I re-tested this today, first time I logged in my icons were already missing. Later, I left my laptop idle for a while and when i returned to it my icons were gone again, so there is no change to this issue with Plasma 5.27.3. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 466823] Icons on desktop disappear regularly after some time, possibly a multi-monitor issue
https://bugs.kde.org/show_bug.cgi?id=466823 Matej Mrenica changed: What|Removed |Added CC||matejm98m...@gmail.com --- Comment #4 from Matej Mrenica --- In case this is caused by corrupted config files, what files could be the culprit? -- You are receiving this mail because: You are watching all bug changes.
[frameworks-kirigami] [Bug 458894] New: combobox dropdowns wider than the combobox
https://bugs.kde.org/show_bug.cgi?id=458894 Bug ID: 458894 Summary: combobox dropdowns wider than the combobox Product: frameworks-kirigami Version: 5.97.0 Platform: Archlinux Packages OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: kdelibs-b...@kde.org Reporter: matej.sta...@gmail.com CC: notm...@gmail.com Target Milestone: Not decided Created attachment 151935 --> https://bugs.kde.org/attachment.cgi?id=151935&action=edit kalendar_bug SUMMARY While using the Kalendar I noticed that the combobox dropdown for adding tags to an event in the todo section is wider than the combobox. It seems this happens in other apps. OBSERVED RESULT Combobox dropdown wider than the combobox. SOFTWARE/OS VERSIONS Operating System: Arch Linux KDE Plasma Version: 5.25.5 KDE Frameworks Version: 5.97.0 Qt Version: 5.15.5 Kernel Version: 5.19.7-arch1-1 (64-bit) Graphics Platform: Wayland Processors: 16 × AMD Ryzen 7 5800H with Radeon Graphics Memory: 15.0 GiB of RAM Graphics Processor: AMD RENOIR Manufacturer: ASUSTeK COMPUTER INC. Product Name: Zenbook UN5401QAB_UN5401QA System Version: 1.0 -- You are receiving this mail because: You are watching all bug changes.
[frameworks-kirigami] [Bug 458894] combobox dropdowns wider than the combobox
https://bugs.kde.org/show_bug.cgi?id=458894 --- Comment #1 from Matej Starc --- Created attachment 151936 --> https://bugs.kde.org/attachment.cgi?id=151936&action=edit systemsettings_bug system settings -> global theme -> application style -> edit theme -> click on a combobox to display a dropdown -- You are receiving this mail because: You are watching all bug changes.
[frameworks-kirigami] [Bug 442799] Cards are not clickable with a Wacom pen
https://bugs.kde.org/show_bug.cgi?id=442799 Matej Starc changed: What|Removed |Added CC||matej.sta...@gmail.com --- Comment #4 from Matej Starc --- This might be taken as a rant, but ok. This is what I've found while testing with my Asus stylus. 1. When pressing on "right click button" on my stylus, the right click event is triggered where the actual cursor is and not where the stylus pen cursor is (video1: https://cloud.aljaxus.eu/index.php/s/FWe7dNb9QDHoqGN) 2. It seems that labels block the pressed/clicked signal. (video2: https://cloud.aljaxus.eu/index.php/s/HwwogK4bWZts6rE, video3: https://cloud.aljaxus.eu/index.php/s/t6ELQQqtnjAkagb) 3. Some action list items are only clickable in icon's area. I assume because the label blocks all the events (video: https://cloud.aljaxus.eu/index.php/s/amRmW2HywfqkGt7) IMHO Labels are the cause of most of these problems. -- You are receiving this mail because: You are watching all bug changes.
[frameworks-kirigami] [Bug 442799] Cards are not clickable with a Wacom pen
https://bugs.kde.org/show_bug.cgi?id=442799 --- Comment #5 from Matej Starc --- (In reply to Matej Starc from comment #4) > This might be taken as a rant, but ok. This is what I've found while testing > with my Asus stylus. > > 1. When pressing on "right click button" on my stylus, the right click event > is triggered where the actual cursor is and not where the stylus pen cursor > is (video1: https://cloud.aljaxus.eu/index.php/s/FWe7dNb9QDHoqGN) > > 2. It seems that labels block the pressed/clicked signal. (video2: > https://cloud.aljaxus.eu/index.php/s/HwwogK4bWZts6rE, video3: > https://cloud.aljaxus.eu/index.php/s/t6ELQQqtnjAkagb) > > 3. Some action list items are only clickable in icon's area. I assume > because the label blocks all the events (video: > https://cloud.aljaxus.eu/index.php/s/amRmW2HywfqkGt7) > > IMHO Labels are the cause of most of these problems. What I wanted to say is, that this is not the only issue and there is no problem with cards but with either Qt or kwin. -- You are receiving this mail because: You are watching all bug changes.
[frameworks-kirigami] [Bug 458393] Kirigami.CategorizedSettings does not produce good results with long words in names
https://bugs.kde.org/show_bug.cgi?id=458393 Matej Starc changed: What|Removed |Added CC||matej.sta...@gmail.com --- Comment #3 from Matej Starc --- I think Kirigami could offer an option in this case that would get the widest word and get the width from that word (in this case, it would make those buttons to access a specific setting page just wide enough for the widest word to fit perfectly without word wrapping). Thank you for bringing this up! I think this could be fixed by getting the longest/widest word and getting its width. If this word's width exceeds maximumWidth (newly created property) it would word wrap it, otherwise it can just set the width of categorized settings sidebar, so the longest word fits perfectly. -- You are receiving this mail because: You are watching all bug changes.
[frameworks-kirigami] [Bug 383737] Adaptive width of text fields
https://bugs.kde.org/show_bug.cgi?id=383737 Matej Starc changed: What|Removed |Added CC||matej.sta...@gmail.com --- Comment #1 from Matej Starc --- I think this can be considered resolved. We now have TextArea which works. -- You are receiving this mail because: You are watching all bug changes.
[frameworks-kirigami] [Bug 383737] Adaptive width of text fields
https://bugs.kde.org/show_bug.cgi?id=383737 Matej Starc changed: What|Removed |Added Status|REPORTED|RESOLVED Resolution|--- |FIXED --- Comment #2 from Matej Starc --- (In reply to Matej Starc from comment #1) > I think this can be considered resolved. We now have TextArea which works. Also, that text input element was meant for one line only.(In reply to Matej Starc from comment #1) > I think this can be considered resolved. We now have TextArea which works. TextField Qt doc (short description): - Qt5: "Displays a single line of editable plain text" - Qt6: "Single-line text input field" -- You are receiving this mail because: You are watching all bug changes.
[frameworks-kirigami] [Bug 383730] Kirigami Gallery hangs upon changing of it's window width in 'Color' section
https://bugs.kde.org/show_bug.cgi?id=383730 Matej Starc changed: What|Removed |Added CC||matej.sta...@gmail.com --- Comment #4 from Matej Starc --- Cannot reproduce. Operating System: Arch Linux KDE Plasma Version: 5.25.5 KDE Frameworks Version: 5.97.0 Qt Version: 5.15.6 Kernel Version: 5.19.7-zen2-1-zen (64-bit) Graphics Platform: Wayland Processors: 12 × Intel® Core™ i7-8700 CPU @ 3.20GHz Memory: 15.5 GiB of RAM Graphics Processor: AMD Radeon RX 480 Graphics -- You are receiving this mail because: You are watching all bug changes.
