[kwin] [Bug 448435] Overview effect's shortcut breaks a lot
https://bugs.kde.org/show_bug.cgi?id=448435 carlo changed: What|Removed |Added CC||wodd...@gmail.com --- Comment #8 from carlo --- Same problem here on Tumbleweed, Plasma 5.24. I noticed this happens after changing some settings, e.g. theme, icons, fonts etc. -- You are receiving this mail because: You are watching all bug changes.
[kdeconnect] [Bug 447774] File system expose cannot expose certain folders on Android 11
https://bugs.kde.org/show_bug.cgi?id=447774 Carlo changed: What|Removed |Added CC||cirlo...@msn.com -- You are receiving this mail because: You are watching all bug changes.
[kdeconnect] [Bug 447636] Android 11: scoped storage does not allow to share the root of the filesystem
https://bugs.kde.org/show_bug.cgi?id=447636 Carlo changed: What|Removed |Added CC||cirlo...@msn.com -- You are receiving this mail because: You are watching all bug changes.
[kdeconnect] [Bug 439342] File system expose does not allow primary exposure
https://bugs.kde.org/show_bug.cgi?id=439342 Carlo changed: What|Removed |Added CC||cirlo...@msn.com -- You are receiving this mail because: You are watching all bug changes.
[Breeze] [Bug 451889] Native chrome wayland with no title bar, inconsistent GTK theme (close button circled).
https://bugs.kde.org/show_bug.cgi?id=451889 --- Comment #3 from carlo --- (In reply to Nate Graham from comment #2) > Can confirm. Not sure this is a breeze-gtk bug though. Needs some > investigation. It's easily reproduced, I have it on all PCs, I'm not even sure if the problem is the gtk theme, however if it helps I think chrome still uses gtk2, but I'm not sure. -- You are receiving this mail because: You are watching all bug changes.
[frameworks-kglobalaccel] [Bug 465867] Allow certain shortcuts that can be triggered regardless of modifiers
https://bugs.kde.org/show_bug.cgi?id=465867 Carlo changed: What|Removed |Added CC||cirlo...@msn.com --- Comment #4 from Carlo --- Moreover, I think being able to set a shortcut only on one modifier key would be preferred. While I understand the reasoning behind why it does not allow to bind a shortcut to modifiers keys only (e.g. , , ,...), I feel like a framework for global shortcuts should allow it. User experience in push-to-talk applications requires to use only one button. It doesn't matter if, for instance, when I +C something I blip my mic on Mumble for a microsecond. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 464798] Second monitor is always black on startup. Have to lock the screen to SDDM to have a chance at fixing it
https://bugs.kde.org/show_bug.cgi?id=464798 --- Comment #5 from Carlo --- The issue appears to not occur with a different display server (from from SDDM). Might be worth waiting for SDDM 0.20 release and see if the port to Wayland fixes the issue -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 464798] Second monitor is always black on startup. Have to lock the screen to SDDM to have a chance at fixing it
https://bugs.kde.org/show_bug.cgi?id=464798 --- Comment #7 from Carlo --- I installed and set lightDM as my display manager instead of SDDM. Not even the git version of SDDM (0.20.alpha?) fixed the issue. Only disabling SDDM solved it for me. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 450068] Use of volatile connector IDs to map containments to screens cannot be made to work reliably and should be replaced with something else
https://bugs.kde.org/show_bug.cgi?id=450068 Carlo changed: What|Removed |Added CC||cirlo...@msn.com -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 458957] New: All-but-last grid's columns are buggy on second monitor
https://bugs.kde.org/show_bug.cgi?id=458957 Bug ID: 458957 Summary: All-but-last grid's columns are buggy on second monitor Product: kwin Version: 5.25.5 Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: effects-desktop-grid Assignee: kwin-bugs-n...@kde.org Reporter: cirlo...@msn.com Target Milestone: --- SUMMARY If I have n columns of virtual desktops, in the Desktop Grid I will always have the first n-1 columns being buggy. By "buggy" I mean that: - windows in the secondary display appear in the primary display (or in both, if the window is in the last column) - all the windows in the secondary display are invisible unless i invisibly click on the corresponding window frame - sometimes windows from the first display are not movable in the second display (as if i was dragging them in an empty space) - the wallpaper of the secondary display is replaced with the one from the primary display - etc... (probably there are more bugs i can't remember now) You can properly see this weird behaviour in the attached video. Mind you that I recorded both screens and the centre of the video should correspond to the border between displays STEPS TO REPRODUCE 1. have multiple displays 2. enable desktop grid effect 3. open the desktop grid with the shortcut OBSERVED RESULT see wallpapers are mismatched between displays (+ other bugs) SOFTWARE/OS VERSIONS Linux/KDE Plasma: Arch Linux KDE Plasma Version: 5.25.5 KDE Frameworks Version: 5.97.0 Qt Version: 5.15.6 -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 458957] All-but-last grid's columns are buggy on second monitor
https://bugs.kde.org/show_bug.cgi?id=458957 --- Comment #1 from Carlo --- I could not attach the video to the bug report because of the size. Here is an external link to it: https://drive.google.com/file/d/1dVfOcKoDC8ZGU4pM7SnDO_cIBYSBn5mT/view?usp=sharing -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 458957] All-but-last grid's columns are buggy on second monitor
https://bugs.kde.org/show_bug.cgi?id=458957 --- Comment #2 from Carlo --- it seems like this bug is ~similar to https://bugs.kde.org/show_bug.cgi?id=455897 -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 464798] Second monitor is always black on startup. Have to lock the screen to SDDM to have a chance at fixing it
https://bugs.kde.org/show_bug.cgi?id=464798 --- Comment #9 from Carlo --- done: https://github.com/sddm/sddm/issues/1696 -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 464798] Second monitor is always black on startup. Have to lock the screen to SDDM to have a chance at fixing it
https://bugs.kde.org/show_bug.cgi?id=464798 --- Comment #10 from Carlo --- update: enabling Wayland on SDDM in the alpha version seems to be another valid fix. In /etc/sddm.conf.d/kde_settings.conf I set: [General] DisplayServer=wayland GreeterEnvironment=QT_WAYLAND_SHELL_INTEGRATION=layer-shell [Wayland] CompositorCommand=kwin_wayland --no-lockscreen --inputmethod qtvirtualkeyboard -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 465747] desktop icons moved to secondary monitor upon login
https://bugs.kde.org/show_bug.cgi?id=465747 Carlo changed: What|Removed |Added CC||cirlo...@msn.com -- You are receiving this mail because: You are watching all bug changes.
[plasma-browser-integration] [Bug 395461] multiple video support
https://bugs.kde.org/show_bug.cgi?id=395461 Carlo changed: What|Removed |Added CC||cirlo...@msn.com -- You are receiving this mail because: You are watching all bug changes.
[dolphin] [Bug 272539] WISH: Instant preview like OSX Snow Leopard
https://bugs.kde.org/show_bug.cgi?id=272539 Carlo changed: What|Removed |Added CC||cirlo...@msn.com -- You are receiving this mail because: You are watching all bug changes.
[Breeze] [Bug 451889] Native chrome wayland with no title bar, inconsistent GTK theme (close button circled).
https://bugs.kde.org/show_bug.cgi?id=451889 --- Comment #4 from carlo --- It seems this bug is fixed, I didn't understand if it was fixed by Chrome or by KDE. -- You are receiving this mail because: You are watching all bug changes.
[Breeze] [Bug 451889] Native chrome wayland with no title bar, inconsistent GTK theme (close button circled).
https://bugs.kde.org/show_bug.cgi?id=451889 --- Comment #6 from carlo --- (In reply to Nate Graham from comment #5) > Ah questo. Credo che sia stato risolto con modifiche breeze-gtk. Did some tests, still present on KDE Neon, fixed on Tumbleweed. -- You are receiving this mail because: You are watching all bug changes.
[Breeze] [Bug 451889] Native chrome wayland with no title bar, inconsistent GTK theme (close button circled).
https://bugs.kde.org/show_bug.cgi?id=451889 --- Comment #7 from carlo --- At this point I don't see what the difference could be, could it be a wayland bug? That would explain why it's still there in Neon and no longer in Tumbleweed. -- You are receiving this mail because: You are watching all bug changes.
[Breeze] [Bug 451889] Native chrome wayland with no title bar, inconsistent GTK theme (close button circled).
https://bugs.kde.org/show_bug.cgi?id=451889 --- Comment #1 from carlo --- Unfortunately this bug still seems to be valid on Plasma 5.25 and also on Plasma 5.25.90 (5.26 beta). I remember that the problem is present in Chrome only when it is launched in native wayland mode, I add image below... https://i.imgur.com/ilOsjwx.png -- You are receiving this mail because: You are watching all bug changes.
[dolphin] [Bug 396449] Dolphin crash on close
https://bugs.kde.org/show_bug.cgi?id=396449 carlo changed: What|Removed |Added Status|NEEDSINFO |RESOLVED --- Comment #5 from carlo --- Thanks, this bug no longer happens to me. Carlo. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 464798] New: Second monitor is always black on startup. Have to lock the screen to SDDM to have a chance at fixing it
https://bugs.kde.org/show_bug.cgi?id=464798 Bug ID: 464798 Summary: Second monitor is always black on startup. Have to lock the screen to SDDM to have a chance at fixing it Classification: Plasma Product: plasmashell Version: 5.26.90 Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: Multi-screen support Assignee: plasma-b...@kde.org Reporter: cirlo...@msn.com CC: aleix...@kde.org, notm...@gmail.com Target Milestone: 1.0 SUMMARY When booting in wayland session (X11 not tested), the secondary monitor is always black. The mouse cursor goes through the primary display, but it is not viewed in the second as if the display was not connected. In monitor settings the display is detected and enabled. I always have to lock the session. SDDM, then, turns on the secondary display and I can finally use it in KDE Plasma as well. I hoped bug 450068 fixed it, but it apparently didn't. I'm on kde-testing on Arch Linux. Some of the noticed settings upon booting: in .config/plasmashellr: [ScreenConnectors] 0=HDMI-A-4 2=Virtual-Virtual1 in .config/plasma-org.kde.plasma.desktop-appletsrc a new plugin=org.kde.plasma.folder with lastScreen=2 is created. lastScreen=1 components are still present. in .config/kcminputrc there is nothing pertinent to monitors SOFTWARE/OS VERSIONS Linux/KDE Plasma: Arch Linux (Wayland session) KDE Plasma Version: 5.26.90 KDE Frameworks Version: 5.102.0 Qt Version: 5.15.8 ADDITIONAL INFORMATION GPU: AMD R9 380 Monitors: 1. Samsung LC24RG50 2. Samsung S24B150 -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 464798] Second monitor is always black on startup. Have to lock the screen to SDDM to have a chance at fixing it
https://bugs.kde.org/show_bug.cgi?id=464798 --- Comment #1 from Carlo --- Oh: sometimes neither of the two displays turn on after the usual kernel infos are displayed. It's as if they are turned off right when Plasma is started. It's a roulette every time I turn my desktop pc on. In this cases I have to forcibly power-off my pc and restart it, since i can't go to tty (ALT+CTRL+F does nothing) -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 464798] Second monitor is always black on startup. Have to lock the screen to SDDM to have a chance at fixing it
https://bugs.kde.org/show_bug.cgi?id=464798 Carlo changed: What|Removed |Added Target Milestone|--- |1.0 Product|kwin|plasmashell Component|multi-screen|Multi-screen support --- Comment #3 from Carlo --- KScreen 2 service is enabled in Plasma settings(In reply to Nate Graham from comment #2) > Do you by any chance have KScreen disabled? KScreen 2 service is enabled in Plasma settings -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 465075] New: Window thumbnails don't work on my AMD notebook - wayland session
https://bugs.kde.org/show_bug.cgi?id=465075 Bug ID: 465075 Summary: Window thumbnails don't work on my AMD notebook - wayland session Classification: Plasma Product: plasmashell Version: 5.26.90 Platform: openSUSE OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: Task Manager and Icons-Only Task Manager Assignee: plasma-b...@kde.org Reporter: wodd...@gmail.com Target Milestone: 1.0 SUMMARY Window thumbnails don't work on my AMD notebook - wayland session *** Thumbnail windows don't work on my AMD notebook, it didn't even work on Plasma 5.26, I think it's a regression because they worked before. I specified AMD hardware, because on the other Intel notebook there are no problems. In the log I often find this error " Failed connect to PipeWire: Couldn't connect PipeWire", I don't know if it is related. STEPS TO REPRODUCE 1. open any application 2. hover the pointer over the task manager icon OBSERVED RESULT you see the empty thumbnail EXPECTED RESULT you should see the thumbnail of the (application) window SOFTWARE/OS VERSIONS Linux/KDE Plasma: openSUSE Tumbleweed (repo factory) KDE Plasma 5.26.90 KDE Frameworks Version: 5.102.0 Qt Version: 5.15.8 ADDITIONAL INFORMATION In Xorg session no problem. I attach image https://i.imgur.com/quV7Uzg.png -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 465075] Window thumbnails don't work on my AMD notebook - wayland session
https://bugs.kde.org/show_bug.cgi?id=465075 --- Comment #2 from carlo --- (In reply to Fushan Wen from comment #1) > Should be fixed in 5.27.0, or you can try to build KPipewire with > https://invent.kde.org/plasma/kpipewire/-/commit/ > 67f8d36cf3e0364adc9cbd380ffb1ad4dca5b155 Great news. Thank you. -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 465229] New: No flatpak applications appear in the system settings for managing permissions. My flatpak apps are installed as a user, I don't know if that's the problem.
https://bugs.kde.org/show_bug.cgi?id=465229 Bug ID: 465229 Summary: No flatpak applications appear in the system settings for managing permissions. My flatpak apps are installed as a user, I don't know if that's the problem. Classification: Applications Product: systemsettings Version: 5.26.90 Platform: openSUSE OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: kcm_flatpak Assignee: plasma-b...@kde.org Reporter: wodd...@gmail.com CC: joshiesuha...@gmail.com Target Milestone: --- SUMMARY No flatpak applications appear in the system settings for managing permissions. My flatpak apps are installed as a user, I don't know if that's the problem. STEPS TO REPRODUCE 1. Open system settings in applications - flatpak permission settings OBSERVED RESULT No visible applications EXPECTED RESULT view all installed flatpak applications SOFTWARE/OS VERSIONS Linux/KDE Plasma: openSUSE Tumbleweed (factory repository) KDE Plasma Version: 5.26.90 KDE Frameworks Version: 5.102.0 Qt Version: 5.15.8 ADDITIONAL INFORMATION session wayland -- You are receiving this mail because: You are watching all bug changes.
[kde] [Bug 486511] New: System settings UI bug
https://bugs.kde.org/show_bug.cgi?id=486511 Bug ID: 486511 Summary: System settings UI bug Classification: I don't know Product: kde Version: unspecified Platform: openSUSE OS: Linux Status: REPORTED Severity: minor Priority: NOR Component: general Assignee: unassigned-b...@kde.org Reporter: carlo.7...@gmail.com Target Milestone: --- Created attachment 169148 --> https://bugs.kde.org/attachment.cgi?id=169148&action=edit three screen shots in one image *** If you're not sure this is actually a bug, instead post about it at https://discuss.kde.org If you're reporting a crash, attach a backtrace with debug symbols; see https://community.kde.org/Guidelines_and_HOWTOs/Debugging/How_to_create_useful_crash_reports *** SUMMARY STEPS TO REPRODUCE 1. Have system settings window open on desktop, with, for example keyboard settings, showing the submenu, see image 001 - top screenshot, attached. 2. Click on the configure power settings on the plasma dropdown menu, see image 001 - middle screenshot 3. submenu for keyboard still visible, see image 001 - bottom screenshot OBSERVED RESULT Prevoiuse sub-menu still visible EXPECTED RESULT New sub-menu should be visible if relevant SOFTWARE/OS VERSIONS Linux/KDE Plasma: OpenSuse Tumblweed 20240426 (available in About System) KDE Plasma Version: 6.0.4 KDE Frameworks Version: 6.1.0 Qt Version: 6.7.0 ADDITIONAL INFORMATION -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 486613] New: [Grid View] moving window in different virtual desktop is inconsistent
https://bugs.kde.org/show_bug.cgi?id=486613 Bug ID: 486613 Summary: [Grid View] moving window in different virtual desktop is inconsistent Classification: Plasma Product: kwin Version: 6.0.4 Platform: Arch Linux OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: effects-window-management Assignee: kwin-bugs-n...@kde.org Reporter: cirlo...@msn.com Target Milestone: --- SUMMARY Often, when you are fast dragging and releasing a window to a different virtual desktop, it does not get moved. You have to be really precise, slow and accurate with movements. This behaviour is a bit different from what i experience with the old grid view pre Plasma 6 SOFTWARE/OS VERSIONS Operating System: Arch Linux KDE Plasma Version: 6.0.4 KDE Frameworks Version: 6.1.0 Qt Version: 6.7.0 Kernel Version: 6.8.9-zen1-1-zen (64-bit) Graphics Platform: Wayland -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 486613] [Grid View] moving window in different virtual desktop is inconsistent
https://bugs.kde.org/show_bug.cgi?id=486613 --- Comment #1 from Carlo --- Created attachment 169207 --> https://bugs.kde.org/attachment.cgi?id=169207&action=edit brief video demonstrating this weird behaviour -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 442733] The task manager and cursor animation for starting applications in wayland only works if no other windows are already open.
https://bugs.kde.org/show_bug.cgi?id=442733 carlo changed: What|Removed |Added Version|5.22.90 |5.23.3 --- Comment #7 from carlo --- Since the bug is still present on 5.23.3 I changed the version as 5.22.90 was a beta version. I hope it goes well. -- You are receiving this mail because: You are watching all bug changes.
[Plasma Vault] [Bug 386200] Import Vault
https://bugs.kde.org/show_bug.cgi?id=386200 Carlo changed: What|Removed |Added CC||cirlo...@msn.com --- Comment #28 from Carlo --- (In reply to Ivan Čukić from comment #8) > The reason this is not in the UI is that I don't find the use-case of > syncing with other computers via a public cloud service a particularly > secure practice. I am very new to the subject, but I'd be interested if you could explain a little further. What is that you don't like about using public Cloud service + CryFS (or w/e), exactly? Is it about the fact that you don't trust Cloud services in general? Is it because, perhaps, this use case could corrupt the files/folder in case of an internet connection loss? Is there something else I don't see -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 385135] Monitor connection names differ across X11 and Wayland, causing multi-monitor containment mappings to break when switching session types
https://bugs.kde.org/show_bug.cgi?id=385135 Carlo changed: What|Removed |Added CC||cirlo...@msn.com -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 96431] Improve Wayland mouse button support for shortcuts in KHotkeys
https://bugs.kde.org/show_bug.cgi?id=96431 Carlo changed: What|Removed |Added CC||cirlo...@msn.com -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 34362] Support for configuring additional mouse buttons
https://bugs.kde.org/show_bug.cgi?id=34362 Carlo changed: What|Removed |Added CC||cirlo...@msn.com -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 226370] GUI for configuring additional mouse buttons
https://bugs.kde.org/show_bug.cgi?id=226370 Carlo changed: What|Removed |Added CC||cirlo...@msn.com -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 96431] Improve Wayland mouse button support for shortcuts in KHotkeys
https://bugs.kde.org/show_bug.cgi?id=96431 --- Comment #63 from Carlo --- I have no idea if this is still taken into consideration, but I'm also interested in this being implemented. Even more so now that Wayland is here. Wayland no longer allows applications to grab inputs by applications. The peak example is VoiP programs that support push-to-talk. Some apps (see Mumble) are starting to adapt by exposing an rpc interface (e.g., `mumble rpc starttalking` and `mumble rpc stoptalking`). That's a great start, but not being able to bind those commands to a mouse button makes them quite useless. Additionally: i don't know if it's possible but it would be interesting to have an option to execute a different command on press & release of the same button. -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 456951] Global shortcut for arbitrary terminal command should be possible without creating a script file on disk
https://bugs.kde.org/show_bug.cgi?id=456951 Carlo changed: What|Removed |Added CC||cirlo...@msn.com -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 391531] No containment shown on given screen in overlapping setup
https://bugs.kde.org/show_bug.cgi?id=391531 Carlo changed: What|Removed |Added CC||cirlo...@msn.com -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 442699] Laptop display remains black with only a cursor after resuming from sleep
https://bugs.kde.org/show_bug.cgi?id=442699 Carlo changed: What|Removed |Added CC||cirlo...@msn.com -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 451906] Blackscreen with mouse pointer only on wayland when multiple displays are connected
https://bugs.kde.org/show_bug.cgi?id=451906 Carlo changed: What|Removed |Added CC||cirlo...@msn.com -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 451386] Black Screen with Movable Cursor after Screens Resume from Sleep
https://bugs.kde.org/show_bug.cgi?id=451386 Carlo changed: What|Removed |Added CC||cirlo...@msn.com -- You are receiving this mail because: You are watching all bug changes.
[plasma-mediacenter] [Bug 418288] Keyboard multimedia keys are unstable
https://bugs.kde.org/show_bug.cgi?id=418288 Carlo changed: What|Removed |Added CC||cirlo...@msn.com -- You are receiving this mail because: You are watching all bug changes.
[plasma-mediacenter] [Bug 418288] Keyboard multimedia keys are unstable
https://bugs.kde.org/show_bug.cgi?id=418288 --- Comment #2 from Carlo --- This still happens to me. Both in X11 and Wayland. It's freaking annoying and i see it as a 15-minutes-bug, tbh -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 451270] Media hotkeys don't do anything
https://bugs.kde.org/show_bug.cgi?id=451270 Carlo changed: What|Removed |Added CC||cirlo...@msn.com -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 442733] New: The task manager and cursor animation for starting applications in wayland only works if no other windows are already open.
https://bugs.kde.org/show_bug.cgi?id=442733 Bug ID: 442733 Summary: The task manager and cursor animation for starting applications in wayland only works if no other windows are already open. Product: plasmashell Version: 5.22.90 Platform: openSUSE RPMs OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: Task Manager and Icons-Only Task Manager Assignee: h...@kde.org Reporter: wodd...@gmail.com CC: plasma-b...@kde.org Target Milestone: 1.0 SUMMARY The animation in the task manager and cursor when starting applications in wayland only works if there are no other applications open. STEPS TO REPRODUCE 1. open Firefox 2. open Dolphin 3. OBSERVED RESULT while opening FF the animation works, when I open Dolphin it doesn't work, this regardless of the specific applications. EXPECTED RESULT Animation should always work. SOFTWARE/OS VERSIONS Linux/KDE Plasma: openSUSE Leap 15.3 (repository KDE-QT) KDE Plasma Version: 5.22.90 KDE Frameworks Version: 5.86.0 Qt Version: 5.15.2 ADDITIONAL INFORMATION -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 442733] The task manager and cursor animation for starting applications in wayland only works if no other windows are already open.
https://bugs.kde.org/show_bug.cgi?id=442733 --- Comment #2 from carlo --- (In reply to Nate Graham from comment #1) > That's weird, cannot reproduce. This is on Wayland, right? Yes wayland, I also tried to install Plasma 5.22.90 on Tumbleweed, to understand if it was a Leap problem, but also in Tumbleweed same behavior. Basically the animation only works if there is nothing open in that virtual desktop. A greeting. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 442733] The task manager and cursor animation for starting applications in wayland only works if no other windows are already open.
https://bugs.kde.org/show_bug.cgi?id=442733 --- Comment #4 from carlo --- (In reply to Nate Graham from comment #3) > Aha, virtual desktops. Does it work as expected if you have only one virtual > desktop? No, it doesn't seem related, even with just one desktop the problem remains. However I tried to reset all the settings and I noticed that now it works every now and then, but random. -- You are receiving this mail because: You are watching all bug changes.
[xdg-desktop-portal-kde] [Bug 436453] No reply to Quit() after Inhibit() call
https://bugs.kde.org/show_bug.cgi?id=436453 --- Comment #13 from Carlo --- Confirming the fix works for me as well! Many thanks ^^ -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 447637] Activity bar widget. Activity name gets cut in half when opening settings
https://bugs.kde.org/show_bug.cgi?id=447637 Carlo changed: What|Removed |Added CC||cirlo...@msn.com -- You are receiving this mail because: You are watching all bug changes.
[Active Window Control] [Bug 451889] New: Native chrome wayland with no title bar, inconsistent GTK theme (close button circled).
https://bugs.kde.org/show_bug.cgi?id=451889 Bug ID: 451889 Summary: Native chrome wayland with no title bar, inconsistent GTK theme (close button circled). Product: Active Window Control Version: unspecified Platform: openSUSE RPMs OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: General Assignee: zrenf...@gmail.com Reporter: wodd...@gmail.com CC: plasma-b...@kde.org Target Milestone: --- SUMMARY The inactivity state of the "close" X button when using native Chrome wayland with the GTK theme is not consistent with the Plasma theme. NOTE: If you are reporting a crash, please try to attach a backtrace with debug symbols. See https://community.kde.org/Guidelines_and_HOWTOs/Debugging/How_to_create_useful_crash_reports *** STEPS TO REPRODUCE 1. Open native wayland chrome 2. Set the GTK theme 3. Do not use the title decoration panel in chrome. OBSERVED RESULT The close button appears circled in black, inconsistent with the Plasma theme. EXPECTED RESULT The theme should be consistent. SOFTWARE/OS VERSIONS Windows: macOS: Linux/KDE Plasma: (available in About System) KDE Plasma Version: 5.24.3 KDE Frameworks Version: 5.92.0 Qt Version: 5.15.2 ADDITIONAL INFORMATION Image... https://i.postimg.cc/pdDRFR6G/Screenshot-20220325-140425.png -- You are receiving this mail because: You are watching all bug changes.
[plasma-pk-updates] [Bug 445010] Network is offline after standby
https://bugs.kde.org/show_bug.cgi?id=445010 carlo changed: What|Removed |Added CC||wodd...@gmail.com -- You are receiving this mail because: You are watching all bug changes.
[Breeze] [Bug 451889] Native chrome wayland with no title bar, inconsistent GTK theme (close button circled).
https://bugs.kde.org/show_bug.cgi?id=451889 carlo changed: What|Removed |Added CC||wodd...@gmail.com -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 442733] The task manager and cursor animation for starting applications in wayland only works if no other windows are already open.
https://bugs.kde.org/show_bug.cgi?id=442733 --- Comment #5 from carlo --- However, the problem persists, I have seen that some on Reddit have already reported it. Some claim they have this problem on Xorg, but I can't confirm it. https://www.reddit.com/r/openSUSE/comments/qap3tc/523_hits_tumbleweed/ -- You are receiving this mail because: You are watching all bug changes.
[Powerdevil] [Bug 432730] New: powerdevil uses outdated ddcutil protocol
https://bugs.kde.org/show_bug.cgi?id=432730 Bug ID: 432730 Summary: powerdevil uses outdated ddcutil protocol Product: Powerdevil Version: 5.20.5 Platform: Manjaro OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: plasma-b...@kde.org Reporter: cirlo...@msn.com Target Milestone: --- ddcutil just reached production status in version 1.0.0. That, although, also means that they changed something in the interface that requires powerdevil to adapt powerdevil to them. I know other projects like Clight had to. I hope to have some news soon. Not everybody is on a laptop and most external monitors communicate through DDC/CI :/ TEMPORARY FIX: if anybody is interested, for the time being I have bound two keyboard keys to the following command (and its equivalent): ddcutil setvcp 10 + 5 --display 1 && ddcutil setvcp 10 + 5 --display 2 && notify-send "Brightness: $(ddcutil getvcp 10 --display 1 -t | grep -oP '(?<=VCP 10 C ).*?(?= 100)')%" -- You are receiving this mail because: You are watching all bug changes.
[Powerdevil] [Bug 432730] powerdevil uses outdated ddcutil protocol
https://bugs.kde.org/show_bug.cgi?id=432730 --- Comment #2 from Carlo --- As far as I am concerned I am interested, but I have zero experience with C++ & KDE framework and my setup is not up to date with Plasma 5.21 That in combination with the fact that now I have to study for my last uni exam makes it difficult for me to start anytime soon :/ That said this evening I tried to locate the region of the bug, at least. I didn't do much, but I understood that powerdevil can actually read and write the actual screen brightness from libddcutil. PowerDevilUPowerBackend does what it should, afaik. It even changes display's brightness through ddcutil according to powersaving settings (e.g. after 5 mins of inactivity it actually dims the screen). Nontheless no slider appears in powerdevil's applet. How is that even possibile that it can read & write the right only needed value, I don't know, it is probably something I cannot understand with the connect() calls. I tried to see the API changes of ddcutil 1.0.0 (http://www.ddcutil.com/c_api_100/), but none of those seem to affect KDE's code... Finally there is one log I don't understand: org.kde.powerdevil: Handle button events action could not check for screen configuration (HandleButtonEvents::checkOutputs@240) -- You are receiving this mail because: You are watching all bug changes.
[Powerdevil] [Bug 432730] powerdevil uses outdated ddcutil protocol
https://bugs.kde.org/show_bug.cgi?id=432730 --- Comment #4 from Carlo --- Thanks! Looking forward to hear from him soon ^^ -- You are receiving this mail because: You are watching all bug changes.
[Breeze] [Bug 433196] New: Make the icons of minimized applications, more pronounced
https://bugs.kde.org/show_bug.cgi?id=433196 Bug ID: 433196 Summary: Make the icons of minimized applications, more pronounced Product: Breeze Version: 5.21.0 Platform: Compiled Sources OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: plasma-b...@kde.org Reporter: wodd...@gmail.com Target Milestone: --- SUMMARY Set more contrast in the panel icons when the application is minimized. You could also choose a different color, now it is almost invisible with both breeze and dark breeze. This wasn't a problem with the old task manager, but with the new task manager (icons only) it is. STEPS TO REPRODUCE 1. Open an application 2. minimize it 3. OBSERVED RESULT you will notice that the contrast on the default themes is minimal, almost non-existent. EXPECTED RESULT the icon should show more prominently the application status. SOFTWARE/OS VERSIONS Windows: macOS: Linux/KDE Plasma: (available in About System) KDE Plasma Version: KDE Frameworks Version: Qt Version: ADDITIONAL INFORMATION -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 427278] Panel & desktop config of secondary monitor lost after ScreenConnectors renumbering
https://bugs.kde.org/show_bug.cgi?id=427278 Carlo changed: What|Removed |Added CC||cirlo...@msn.com -- You are receiving this mail because: You are watching all bug changes.
[plasma-systemmonitor] [Bug 438621] New: New systemmonitor application does not show any graphics, this also happens with objects for cpu control
https://bugs.kde.org/show_bug.cgi?id=438621 Bug ID: 438621 Summary: New systemmonitor application does not show any graphics, this also happens with objects for cpu control Product: plasma-systemmonitor Version: 5.22.0 Platform: openSUSE RPMs OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: ksysguard-b...@kde.org Reporter: wodd...@gmail.com CC: ahiems...@heimr.nl, plasma-b...@kde.org Target Milestone: --- SUMMARY New systemmonitor application does not show any graphics, this also happens with objects for cpu control, memory etc. STEPS TO REPRODUCE 1. open system monitor or add control objects cpu, memory etc. 2. 3. OBSERVED RESULT open system monitor, view cpu graphics, memory. EXPECTED RESULT SOFTWARE/OS VERSIONS Windows: macOS: Linux/KDE Plasma: Tumbleweed - PLASMA 5.22 (available in About System) KDE Plasma Version: KDE Frameworks Version: Qt Version: ADDITIONAL INFORMATION Application: plasma-systemmonitor (5.22.0) Qt Version: 5.15.2 Frameworks Version: 5.82.0 Operating System: Linux 5.12.9-1-default x86_64 Windowing System: Wayland Drkonqi Version: 5.22.0 Distribution: "openSUSE Tumbleweed" -- Information about the crash: The crash can be reproduced every time. -- Backtrace: Application: Monitor di sistema (plasma-systemmonitor), signal: Segmentation fault Content of s_kcrashErrorMessage: [Current thread is 1 (Thread 0x7fc4452b8880 (LWP 1934))] [KCrash Handler] #6 0x56548ee23f51 in ?? () #7 0x7fc42c3b6146 in ToolBarLayoutDelegate::ensureItemVisibility (this=0x56548f22fa30) at /usr/src/debug/kirigami2-5.82.0-1.2.x86_64/src/toolbarlayoutdelegate.h:87 #8 0x7fc4480f70f3 in QtPrivate::QSlotObjectBase::call (a=0x7ffca2ddba10, r=0x56548f22fa30, this=0x56548ef4e3e0) at ../../include/QtCore/../../src/corelib/kernel/qobjectdefs_impl.h:398 #9 doActivate (sender=0x56548ebe2a30, signal_index=18, argv=0x7ffca2ddba10) at kernel/qobject.cpp:3886 #10 0x7fc4480f05bf in QMetaObject::activate (sender=sender@entry=0x56548ebe2a30, m=m@entry=0x7fc4479bce20 , local_signal_index=local_signal_index@entry=15, argv=argv@entry=0x0) at kernel/qobject.cpp:3946 #11 0x7fc4476b9713 in QQuickItem::visibleChanged (this=this@entry=0x56548ebe2a30) at .moc/moc_qquickitem.cpp:1170 #12 0x7fc4476c9d47 in QQuickItemPrivate::setEffectiveVisibleRecur (this=this@entry=0x56548ec9ce70, newEffectiveVisible=) at /usr/src/debug/libqt5-qtdeclarative-5.15.2-4.2.x86_64/src/quick/items/qquickitem.cpp:6057 #13 0x7fc4476d2439 in QQuickItem::setParentItem (this=this@entry=0x56548ebe2a30, parentItem=parentItem@entry=0x0) at /usr/src/debug/libqt5-qtdeclarative-5.15.2-4.2.x86_64/src/quick/items/qquickitem.cpp:2710 #14 0x7fc4476d2956 in QQuickItem::~QQuickItem (this=0x56548ebe2a30, __in_chrg=) at /usr/src/debug/libqt5-qtdeclarative-5.15.2-4.2.x86_64/src/quick/items/qquickitem.cpp:2311 #15 0x7fc40a1323ae in QQuickButton::~QQuickButton (this=, this=) at ../../../include/QtQuickTemplates2/5.15.2/QtQuickTemplates2/private/../../../../../src/quicktemplates2/qquickbutton_p.h:57 #16 QQuickToolButton::~QQuickToolButton (this=, this=) at ../../../include/QtQuickTemplates2/5.15.2/QtQuickTemplates2/private/../../../../../src/quicktemplates2/qquicktoolbutton_p.h:55 #17 QQmlPrivate::QQmlElement::~QQmlElement (this=, this=) at /usr/include/qt5/QtQml/qqmlprivate.h:144 #18 QQmlPrivate::QQmlElement::~QQmlElement (this=, this=) at /usr/include/qt5/QtQml/qqmlprivate.h:144 #19 0x7fc42c3b6ab6 in ToolBarLayoutDelegate::~ToolBarLayoutDelegate (this=, this=) at /usr/src/debug/kirigami2-5.82.0-1.2.x86_64/src/toolbarlayoutdelegate.cpp:84 #20 0x7fc42c3b6b4a in ToolBarLayoutDelegate::~ToolBarLayoutDelegate (this=, this=) at /usr/src/debug/kirigami2-5.82.0-1.2.x86_64/src/toolbarlayoutdelegate.cpp:70 #21 std::default_delete::operator() (__ptr=0x56548f22fa30, this=) at /usr/include/c++/11/bits/unique_ptr.h:85 #22 std::unique_ptr >::~unique_ptr (this=, this=) at /usr/include/c++/11/bits/unique_ptr.h:361 #23 std::pair > >::~pair (this=, this=) at /usr/include/c++/11/bits/stl_pair.h:211 #24 __gnu_cxx::new_allocator > >, false> >::destroy > > > (__p=0x56548ef86308, this=0x56548e728668) at /usr/include/c++/11/ext/new_allocator.h:162 #25 std::allocator_traits > >, false> > >::destroy > > > (__p=0x56548ef86308, __a=...) at /usr/include/c++/11/bits/alloc_traits.h:531 #26 std::__detail::_Hashtable_alloc > >, false> > >::_M_deallocate_node (__n=0x56548ef86300, this=0x56548e728668) at /usr/include/c++/11/bits/hashtable_policy.h:1891 #27 std::_Hashtable > >, std::allocator > > >, std::__detail::_Select1st, std::equal_to, std::hash, std::__detail::_Mod_range_hashing, std::__detail::_Default_ranged_hash, std::__detail::_Prime_rehash_policy, std::__detail::_Hashtable_traits >::_M_erase (this=0x56548e728668, __bkt=
[plasma-systemmonitor] [Bug 439181] New: New systemmonitor application does not show any graphics, this also happens with objects for cpu control
https://bugs.kde.org/show_bug.cgi?id=439181 Bug ID: 439181 Summary: New systemmonitor application does not show any graphics, this also happens with objects for cpu control Product: plasma-systemmonitor Version: 5.22.1 Platform: openSUSE RPMs OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: ksysguard-b...@kde.org Reporter: wodd...@gmail.com CC: ahiems...@heimr.nl, plasma-b...@kde.org Target Milestone: --- SUMMARY The new system monitor and reference plasmoids do not display any graphs. STEPS TO REPRODUCE 1. open system monitor 2. not display any graphs. 3. OBSERVED RESULT EXPECTED RESULT view the graphics of the cpu and of the various sensors SOFTWARE/OS VERSIONS Windows: macOS: Linux/openSUSE Tumbleweed (available in About System) KDE Plasma Version: 5.22.1 KDE Frameworks Version: info 5.83.0 Qt Version: 5.15.2 ADDITIONAL INFORMATION I don't know if this is a Plasma or Tumbleweed bug, but I know that other users have encountered it in other distributions, such as Arch. Attach image ... https://imgur.com/LsB6dYF -- You are receiving this mail because: You are watching all bug changes.
[plasma-systemmonitor] [Bug 439181] New systemmonitor application does not show any graphics, this also happens with objects for cpu control
https://bugs.kde.org/show_bug.cgi?id=439181 --- Comment #2 from carlo --- (In reply to David Edmundson from comment #1) > Can you please invoke ksystemstats manually from the command line and report > on any output. > > If it crashes, please include a backtrace. No crashes. The result of @localhost:~> ksystemstats Errore di segmentazione (core dump creato) A greeting. -- You are receiving this mail because: You are watching all bug changes.
[plasma-systemmonitor] [Bug 439181] New systemmonitor application does not show any graphics, this also happens with objects for cpu control
https://bugs.kde.org/show_bug.cgi?id=439181 --- Comment #3 from carlo --- The strange thing is that on another PC, always with Tumbleweed and with the same applications installed, the new system monitor works fine. -- You are receiving this mail because: You are watching all bug changes.
[Powerdevil] [Bug 432730] powerdevil uses outdated ddcutil protocol
https://bugs.kde.org/show_bug.cgi?id=432730 --- Comment #6 from Carlo --- I am sorry for the very late reply. That said I am not really sure since when, but I appear to have been fixed ^^ Powerdevil now have its slider and (i presume) it uses the right ddcutil interface. @Rind > If so, can you test the DKMS module ddcci-driver-linux? At the moment i am using ddcutil and it works, so i haven't tried it yet. Do you still need me to test with ddcci driver? -- You are receiving this mail because: You are watching all bug changes.
[Powerdevil] [Bug 432730] powerdevil uses outdated ddcutil protocol
https://bugs.kde.org/show_bug.cgi?id=432730 Carlo changed: What|Removed |Added Resolution|--- |FIXED Status|CONFIRMED |RESOLVED -- You are receiving this mail because: You are watching all bug changes.
[xdg-desktop-portal-kde] [Bug 436453] New: No reply to Quit() after Inhibit() call
https://bugs.kde.org/show_bug.cgi?id=436453 Bug ID: 436453 Summary: No reply to Quit() after Inhibit() call Product: xdg-desktop-portal-kde Version: unspecified Platform: Manjaro OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: jgrul...@redhat.com Reporter: cirlo...@msn.com Target Milestone: --- SUMMARY Portal documentation (https://flatpak.github.io/xdg-desktop-portal/portal-docs.html#gdbus-org.freedesktop.portal.Inhibit) prescribe that in order to remove the inhibition, the client must call Close() on the returned handle. After a quick look at src/inhibit.cpp (and comparing it to xdg-desktop-portal-gtk) I am pretty sure no reply is prepared. This means that the client hangs on and finally crashes. STEPS TO REPRODUCE 1. run /lib/xdg-desktop-portal-kde --verbose 2. run my quick demo: https://gist.github.com/carlocastoldi/b52a3434c36b8bf185afe4a545ff90d8 3. click on the GUI bottom twice. One for inhibiting and one for stopping the inhibition 4. make sure the Close() call is received by xdg-desktop-portal-kde 5. Wait for a certain amount of seconds Make sure to run my demo on X11, as on Wayland I take advantage of xdg-foreign to export the toplevel handle and Kwin does not yet support it (I don't even know if there is any plans to) OBSERVED RESULT dbus.exceptions.DBusException: org.freedesktop.DBus.Error.NoReply: Did not receive a reply. Possible causes include: the remote application did not send a reply, the message bus security policy blocked the reply, the reply timeout expired, or the network connection was broken EXPECTED RESULT The inhibition is cancelled and a reply is sent back to the application ADDITIONAL INFORMATION This bug report and demo is done with the goal to ease the usage of portals by host applications (and not!) as i think they can play a really important role in the interoperability between gnu/linux environments. I'd be happy to share ideas & code with someone who sees the same potential! For further info: https://github.com/flatpak/xdg-desktop-portal/issues/579 -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 436463] New: Inkscape icons are not visible in the global menu
https://bugs.kde.org/show_bug.cgi?id=436463 Bug ID: 436463 Summary: Inkscape icons are not visible in the global menu Product: plasmashell Version: 5.21.4 Platform: Manjaro OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: Global Menu Assignee: k...@privat.broulik.de Reporter: cirlo...@msn.com CC: mvourla...@gmail.com, plasma-b...@kde.org Target Milestone: 1.0 SUMMARY In Inkscape icons are really important to quickly identify different functions between the many options. Not being able to see them heavily impacts the workflow. In order to work around this issue I am forced to blacklist inkscape in org.appmenu.gtk-module in dconf. Following I show the differences: * Inkscape with KDE's global menu: https://i.imgur.com/zmhkCXG.png * Inkscape with Gtk/default menu: https://i.imgur.com/YipgySe.png SOFTWARE/OS VERSIONS KDE Plasma Version: 5.21.4 KDE Frameworks Version: 5.81.0 Qt Version: 5.15.2 Inkscape: 1.0.2 / 1.1.beta -- You are receiving this mail because: You are watching all bug changes.
[xdg-desktop-portal-kde] [Bug 436453] No reply to Quit() after Inhibit() call
https://bugs.kde.org/show_bug.cgi?id=436453 --- Comment #2 from Carlo --- I tried your portal-test as host application and it works for me as well. At this point I don't know what to change in my demo.. I am fairly new to dbus and I cannot explain to myself why it works on GNOME, but it does not on KDE. Would you please be so kind to try helping me debugging it? I am using python dbus API + Gtk because I'd like to then write a merge request for a Gtk app written in python P.S. I also tried to make an asynchronous call to Close(), but it didn't help. It just changed the error it displayed to GDBus.Error:org.freedesktop.DBus.Error.UnknownObject: No such object path '/org/freedesktop/portal/desktop/request/1_204/t' where 1_204/t is the handle returned by Inhibit -- You are receiving this mail because: You are watching all bug changes.
[xdg-desktop-portal-kde] [Bug 436453] No reply to Quit() after Inhibit() call
https://bugs.kde.org/show_bug.cgi?id=436453 --- Comment #3 from Carlo --- actually: i think the UnknownObject error is due to the fact that i tried to click the toggle multiple times trying to close the request. The first time still gets org.freedesktop.DBus.Error.NoReply, so there is really no change with asynch calls -- You are receiving this mail because: You are watching all bug changes.
[xdg-desktop-portal-kde] [Bug 436453] No reply to Quit() after Inhibit() call
https://bugs.kde.org/show_bug.cgi?id=436453 --- Comment #5 from Carlo --- On KDE? That's strange, powerdevil seems to detect it on my system: https://i.imgur.com/eEJUAVh.png I assume the systems has installed: Gtk4, dbus-python and python-gobject -- You are receiving this mail because: You are watching all bug changes.
[xdg-desktop-portal-kde] [Bug 436453] No reply to Quit() after Inhibit() call
https://bugs.kde.org/show_bug.cgi?id=436453 --- Comment #8 from Carlo --- Could the X11 error due to the fact that the DISPLAY variable is not set? On Wayland you may want to try this version of the demo, where I don't try to get toplevel's handle to pass to the Portal: https://pastebin.com/raw/tziTenUa -- You are receiving this mail because: You are watching all bug changes.
[xdg-desktop-portal-kde] [Bug 436453] No reply to Quit() after Inhibit() call
https://bugs.kde.org/show_bug.cgi?id=436453 --- Comment #10 from Carlo --- Yes, I noticed that! But I think it's the Portal that un-inhibits the session when it detects the peer has exited. But I don't make the Close() call on exit -- You are receiving this mail because: You are watching all bug changes.
[xdg-desktop-portal-kde] [Bug 436453] No reply to Quit() after Inhibit() call
https://bugs.kde.org/show_bug.cgi?id=436453 --- Comment #11 from Carlo --- Oh I just realised that in my demo it is not clear that if you click a second time on "Toggle Inhibtion", it uninhibits the session. That is what caused me problems. -- You are receiving this mail because: You are watching all bug changes.
[plasma-systemmonitor] [Bug 436580] New: XDG autostarted application units are wrongly parsed
https://bugs.kde.org/show_bug.cgi?id=436580 Bug ID: 436580 Summary: XDG autostarted application units are wrongly parsed Product: plasma-systemmonitor Version: 5.21.4 Platform: Manjaro OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: ksysguard-b...@kde.org Reporter: cirlo...@msn.com CC: ahiems...@heimr.nl, plasma-b...@kde.org Target Milestone: --- SUMMARY KDE (& GNOME) in the last few months/years started rolling out an innovative resource management that makes usage of cgroups (thanks David Edmundson). I assume that this is what "Applications" tab is using to determine to which program a certain process belongs to. According to the specifications the app units are of the following format: * app[-]-[@].service * app[-]--.scope The interesting bit should be the . Note that, assuming to split unit by the dashes, the app_id is in the last and second to last split. However, using systemd-cgls, you can notice that there is a third possibility: * app--autostart.service Even if it is a ".service", the app_id is in the second to last split, not in the last one. I assume this is what Plasma System Monitor forgets when displaying OBSERVED RESULT https://i.imgur.com/n6Ysb4T.png SOFTWARE/OS VERSIONS KDE Plasma Version: 5.21.4 KDE Frameworks Version: 5.81.0 Qt Version: 5.15.2 -- You are receiving this mail because: You are watching all bug changes.
[plasma-systemmonitor] [Bug 436580] XDG autostarted application units are wrongly parsed
https://bugs.kde.org/show_bug.cgi?id=436580 --- Comment #2 from Carlo --- It is indeed fixed in systemd v248. Thanks! -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 435078] Direction of Wayland 4 finger gestures can't be modified from settings.
https://bugs.kde.org/show_bug.cgi?id=435078 Carlo changed: What|Removed |Added CC||cirlo...@msn.com -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 435261] Plasma crashed after changing desktop wallpaper source and right clicking in desktop
https://bugs.kde.org/show_bug.cgi?id=435261 carlo changed: What|Removed |Added CC||wodd...@gmail.com -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 435261] Plasma crashed after changing desktop wallpaper source and right clicking in desktop
https://bugs.kde.org/show_bug.cgi?id=435261 --- Comment #1 from carlo --- I also confirm the bug on my machines, sometimes it happens even without changing the background, but simply by right clicking on the desktop. It happens on both the Xorg and Wayland session. -- You are receiving this mail because: You are watching all bug changes.
[kdeconnect] [Bug 443155] kdeconnect breaks when openssh is upgraded to version 8.8p1-1
https://bugs.kde.org/show_bug.cgi?id=443155 Carlo changed: What|Removed |Added CC||cirlo...@msn.com -- You are receiving this mail because: You are watching all bug changes.
[kdeconnect] [Bug 429173] [Wayland] Keyboard input is not available from Android to Plasma
https://bugs.kde.org/show_bug.cgi?id=429173 Carlo changed: What|Removed |Added CC||cirlo...@msn.com -- You are receiving this mail because: You are watching all bug changes.
[kdeconnect] [Bug 461545] New: Use KDEConnect as NMEA source and to contribute to MLS
https://bugs.kde.org/show_bug.cgi?id=461545 Bug ID: 461545 Summary: Use KDEConnect as NMEA source and to contribute to MLS Classification: Applications Product: kdeconnect Version: unspecified Platform: Other OS: Linux Status: REPORTED Severity: wishlist Priority: NOR Component: common Assignee: albertv...@gmail.com Reporter: cirlo...@msn.com Target Milestone: --- Mozilla Location Service is an open geolocation service based on publicly observable cell sites and Wi-Fi access points. Its proprietary counterpart is GLS (Google Location Service). It is quite widely used and (up until recently) worked well thanks to people contributing to the service thanks to Mozilla's applications: Mozilla Stumbler[1] and Firefox Mobile (Fennec version). However, since Mozilla Stumbler was retired [2] and Firefox Mobile was updated to Fenix [3] there is no easy way for everyday users to contribute to MLS. Indeed, ~1.5 years later we are starting to see bad reports from MLS [4]. I thus think that integrating into KDEConnect the option to use the phone as a source of NMEA sentences may allow to: 1. get a better location of the connected PCs, to be used for application requiring a ~good precision 2. have a trusted and open platform, better than alternatives that are proprietary, abandoned and badly integrated with Linux systems [5] 3. contribute, if the user wants, to Mozilla Location Service. The contribution could be done/enabled either from the phone or from the connected PC Sources: [1]: https://github.com/mozilla/MozStumbler [2]: https://discourse.mozilla.org/t/retiring-mozilla-stumbler/75206 [3]: https://github.com/mozilla-mobile/fenix/issues/1253 [4]: https://gitlab.freedesktop.org/geoclue/geoclue/-/issues/166 [5]: https://jillybunch.com/sharegps/ https://play.google.com/store/apps/details?id=com.jillybunch.shareGPS -- You are receiving this mail because: You are watching all bug changes.
[kdeconnect] [Bug 424159] Using smartphone gps via kdeconnect
https://bugs.kde.org/show_bug.cgi?id=424159 Carlo changed: What|Removed |Added See Also||https://bugs.kde.org/show_b ||ug.cgi?id=461545 -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 442733] The task manager and cursor animation for starting applications in wayland only works if no other windows are already open.
https://bugs.kde.org/show_bug.cgi?id=442733 --- Comment #9 from carlo --- (In reply to Nate Graham from comment #8) > Still cannot reproduce in current git master (which will soon be Plasma > 5.24). I am testing Plasma 5.24 (5.23.90) beta in Tumbleweed and I no longer have this problem. -- You are receiving this mail because: You are watching all bug changes.
[Discover] [Bug 443302] Discover crashed in ResourcesUpdatesModel::useUnattendedUpdatesChanged() while I was interacting with a GHNS window
https://bugs.kde.org/show_bug.cgi?id=443302
carlo changed:
What|Removed |Added
CC||wodd...@gmail.com
--- Comment #4 from carlo ---
Same problem in Tumbleweed using factory repositories, so Plasma 5.23.90 -
Frameworks 5.90.0 - qt 5.15.2 - Applications 21.12.2.
Starting Discover from the terminal I get :
plasma-discover %F
QObject::startTimer: Timers cannot have negative intervals
org.kde.plasma.discover: Trying to open unexisting file
QUrl("file:///home/carlo/%25F")
adding empty sources model QStandardItemModel(0x561c5bd61b90)
org.kde.plasma.libdiscover: Couldn't find a category for "fwupd-backend"
file:///usr/lib64/qt5/qml/org/kde/kirigami.2/private/PrivateActionToolButton.qml:74:5:
QML Binding: Binding loop detected for property "value"
file:///usr/lib64/qt5/qml/org/kde/kirigami.2/AbstractApplicationWindow.qml:283:5:
QML Binding: Not restoring previous value because restoreMode has not been set.
This behavior is deprecated.
You have to import QtQml 2.15 after any QtQuick imports and set
the restoreMode of the binding to fix this warning.
In Qt < 6.0 the default is Binding.RestoreBinding.
In Qt >= 6.0 the default is Binding.RestoreBindingOrValue.
file:///usr/lib64/qt5/qml/org/kde/kirigami.2/BasicListItem.qml:261:18: QML
QQuickItem*: Binding loop detected for property "implicitWidth"
file:///usr/lib64/qt5/qml/org/kde/kirigami.2/AbstractApplicationWindow.qml:283:5:
QML Binding: Not restoring previous value because restoreMode has not been set.
This behavior is deprecated.
You have to import QtQml 2.15 after any QtQuick imports and set
the restoreMode of the binding to fix this warning.
In Qt < 6.0 the default is Binding.RestoreBinding.
In Qt >= 6.0 the default is Binding.RestoreBindingOrValue.
Errore di segmentazione (core dump creato)
I think it's the same bug, but I'm not sure, in any case Discover doesn't
start.
--
You are receiving this mail because:
You are watching all bug changes.
[plasma-browser-integration] [Bug 430075] New: Plasma Shell Crash SSL Certificate
https://bugs.kde.org/show_bug.cgi?id=430075 Bug ID: 430075 Summary: Plasma Shell Crash SSL Certificate Product: plasma-browser-integration Version: unspecified Platform: openSUSE RPMs OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: k...@privat.broulik.de Reporter: wodd...@gmail.com Target Milestone: --- Plasma Integration extension on some streaming sites, display a Plasma pop up with the following message "The server certificate failed the authenticity test (aketemp01 ...). The issuer certificate of a certificate cannot be found locally. No certificate can be verified. " Clicking on "cancel" continues without problems, clicking on the other two options Plasma crashes and you need to restart the session. Without extension no problem, verified on both Chrome and Firefox. I enclose the discussion on Reddit. https://postimg.cc/v4bZZZqj https://www.reddit.com/r/openSUSE/comments/k6vjv1/plasma_shell_crash_ssl_certificate/ I apologize if my English is not perfect. A greeting STEPS TO REPRODUCE 1. 2. 3. OBSERVED RESULT EXPECTED RESULT SOFTWARE/OS VERSIONS Windows: macOS: Linux/KDE Plasma: (available in About System) KDE Plasma Version: KDE Frameworks Version: Qt Version: ADDITIONAL INFORMATION -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 401479] Feature request: add animations that follow the fingers when performing touchpad gestures
https://bugs.kde.org/show_bug.cgi?id=401479 Carlo changed: What|Removed |Added CC||cirlo...@msn.com -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 375951] locally integrated menus
https://bugs.kde.org/show_bug.cgi?id=375951 Carlo changed: What|Removed |Added CC||cirlo...@msn.com -- You are receiving this mail because: You are watching all bug changes.
[krunner] [Bug 416145] Krunner doesn't immediately intercept keystrokes, leading the user to accidentally type text into whatever app is open
https://bugs.kde.org/show_bug.cgi?id=416145 Carlo changed: What|Removed |Added CC||cirlo...@msn.com -- You are receiving this mail because: You are watching all bug changes.
[ksmserver] [Bug 429426] Immediate login after logout will stuck till timeout because of kglobalaccel5
https://bugs.kde.org/show_bug.cgi?id=429426 Carlo changed: What|Removed |Added CC||cirlo...@msn.com -- You are receiving this mail because: You are watching all bug changes.
[apper] [Bug 384165] Plasma5 Crash after Updating System with Update Plugin
https://bugs.kde.org/show_bug.cgi?id=384165 --- Comment #7 from carlo --- (In reply to Justin Zobel from comment #6) > Thank you for the crash report. > > As it has been a while since this was reported, can you please test and > confirm if this issue is still occurring or if this bug report can be marked > as resolved. > > I have set the bug status to "needsinfo" pending your response, please > change back to "reported" or "resolved/worksforme" when you respond, thank > you. The bug is fixed, so it can be closed. A greeting, thanks. -- You are receiving this mail because: You are watching all bug changes.
[kdeconnect] [Bug 461545] Use KDEConnect as NMEA source and to contribute to MLS
https://bugs.kde.org/show_bug.cgi?id=461545 --- Comment #1 from Carlo --- over at Mozilla they also seemed enthusiast to built such an infrastructure! source: https://github.com/mozilla/ichnaea/issues/1926 -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 424485] GDbus-DBusMenu-Proxy does not work for GTK Wayland apps
https://bugs.kde.org/show_bug.cgi?id=424485 Carlo changed: What|Removed |Added CC||cirlo...@msn.com -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 433308] KDE, Wayland, Qt Mouse Focus Malfunction, then System Settings Crash
https://bugs.kde.org/show_bug.cgi?id=433308 carlo changed: What|Removed |Added CC||wodd...@gmail.com -- You are receiving this mail because: You are watching all bug changes.
[gwenview] [Bug 411196] Gwenview very slow to launch while the top item in the system clipboard was sent by KDE Connect using the shared clipboard feature
https://bugs.kde.org/show_bug.cgi?id=411196 carlo changed: What|Removed |Added CC||wodd...@gmail.com -- You are receiving this mail because: You are watching all bug changes.
[kio-gdrive] [Bug 415089] Dolphin Kio-gdrive authentication with Google account fails
https://bugs.kde.org/show_bug.cgi?id=415089 carlo changed: What|Removed |Added CC||wodd...@gmail.com --- Comment #18 from carlo --- I can confirm, that this bug also affects other distributions, both Leap 15.1 and Tumbleweed have this bug with authentication for kio-gdrive. A greeting. -- You are receiving this mail because: You are watching all bug changes.
[kmail2] [Bug 397825] [Wayland] Message viewer displays only a black rectangle
https://bugs.kde.org/show_bug.cgi?id=397825 carlo changed: What|Removed |Added CC||wodd...@gmail.com --- Comment #9 from carlo --- Same problem on my PC Plasma 5.18.3 openSUSE Tumbleweed, AMD graphics card. The text of the message is invisible as in the image above. Kmail seems to be having some problems in Wayland ... -- You are receiving this mail because: You are watching all bug changes.
[dolphin] [Bug 396449] New: Dolphin crash on close
https://bugs.kde.org/show_bug.cgi?id=396449 Bug ID: 396449 Summary: Dolphin crash on close Product: dolphin Version: 18.04.2 Platform: openSUSE RPMs OS: Linux Status: UNCONFIRMED Keywords: drkonqi Severity: crash Priority: NOR Component: general Assignee: dolphin-bugs-n...@kde.org Reporter: carlo.7...@gmail.com CC: elvis.angelac...@kde.org Target Milestone: --- Application: dolphin (18.04.2) Qt Version: 5.11.1 Frameworks Version: 5.47.0 Operating System: Linux 4.17.4-1-default x86_64 Distribution: "openSUSE Tumbleweed" -- Information about the crash: - What I was doing when the application crashed: Open Dolphin, right click on a file or folder to show the menu, then without any further clicks move the mouse to the close button of the dolphin window and click the button to close Dolphin, the application crashes.(OpenSuse Tumbleweed Plasma 5.13.2 Frameworks 5.47.0) The crash can be reproduced every time. -- Backtrace: Application: Dolphin (dolphin), signal: Segmentation fault Using host libthread_db library "/lib64/libthread_db.so.1". [Current thread is 1 (Thread 0x7f389b671c80 (LWP 25889))] Thread 4 (Thread 0x7f387a2af700 (LWP 25892)): #0 0x7f38903364dc in pthread_cond_wait@@GLIBC_2.3.2 () from /lib64/libpthread.so.0 #1 0x7f387af3779b in ?? () from /usr/lib64/dri/i965_dri.so #2 0x7f387af374c7 in ?? () from /usr/lib64/dri/i965_dri.so #3 0x7f3890330554 in start_thread () from /lib64/libpthread.so.0 #4 0x7f389af09ccf in clone () from /lib64/libc.so.6 Thread 3 (Thread 0x7f3881d58700 (LWP 25891)): #0 0x7f389aefad34 in read () from /lib64/libc.so.6 #1 0x7f388dc947a0 in ?? () from /usr/lib64/libglib-2.0.so.0 #2 0x7f388dc4fd9f in g_main_context_check () from /usr/lib64/libglib-2.0.so.0 #3 0x7f388dc50270 in ?? () from /usr/lib64/libglib-2.0.so.0 #4 0x7f388dc503ec in g_main_context_iteration () from /usr/lib64/libglib-2.0.so.0 #5 0x7f38950bfb3b in QEventDispatcherGlib::processEvents (this=0x7f3874000b20, flags=...) at kernel/qeventdispatcher_glib.cpp:425 #6 0x7f389506fb3b in QEventLoop::exec(QFlags) () at ../../include/QtCore/../../src/corelib/global/qflags.h:140 #7 0x7f3894ece326 in QThread::exec() () at ../../include/QtCore/../../src/corelib/global/qflags.h:120 #8 0x7f3895510f45 in ?? () from /usr/lib64/libQt5DBus.so.5 #9 0x7f3894ed78ec in QThreadPrivate::start(void*) () at thread/qthread_unix.cpp:367 #10 0x7f3890330554 in start_thread () from /lib64/libpthread.so.0 #11 0x7f389af09ccf in clone () from /lib64/libc.so.6 Thread 2 (Thread 0x7f38842ef700 (LWP 25890)): #0 0x7f389aeff2c9 in poll () from /lib64/libc.so.6 #1 0x7f388d588377 in ?? () from /usr/lib64/libxcb.so.1 #2 0x7f388d589f8a in xcb_wait_for_event () from /usr/lib64/libxcb.so.1 #3 0x7f38872ca089 in QXcbEventReader::run (this=0x558443d321c0) at qxcbconnection.h:409 #4 0x7f3894ed78ec in QThreadPrivate::start(void*) () at thread/qthread_unix.cpp:367 #5 0x7f3890330554 in start_thread () from /lib64/libpthread.so.0 #6 0x7f389af09ccf in clone () from /lib64/libc.so.6 Thread 1 (Thread 0x7f389b671c80 (LWP 25889)): [KCrash Handler] #6 0x7f389635c9a0 in QGraphicsScenePrivate::storeMouseButtonsForMouseGrabber (this=this@entry=0x558444296800, event=event@entry=0x7ffdb3cc1450) at ../../include/QtCore/../../src/corelib/tools/qlist.h:540 #7 0x7f389636363b in QGraphicsScenePrivate::mousePressEventHandler (this=this@entry=0x558444296800, mouseEvent=mouseEvent@entry=0x7ffdb3cc1450) at graphicsview/qgraphicsscene.cpp:1463 #8 0x7f3896363769 in QGraphicsScene::mousePressEvent (this=, mouseEvent=0x7ffdb3cc1450) at graphicsview/qgraphicsscene.cpp:4046 #9 0x7f389636ad10 in QGraphicsScene::event (this=0x5584442c0f40, event=0x7ffdb3cc1450) at graphicsview/qgraphicsscene.cpp:3410 #10 0x7f389607dc11 in QApplicationPrivate::notify_helper (this=this@entry=0x558443d52980, receiver=receiver@entry=0x5584442c0f40, e=e@entry=0x7ffdb3cc1450) at kernel/qapplication.cpp:3728 #11 0x7f3896084df0 in QApplication::notify(QObject*, QEvent*) () at kernel/qapplication.cpp:3487 #12 0x7f3895070d29 in QCoreApplication::notifyInternal2(QObject*, QEvent*) () at ../../include/QtCore/../../src/corelib/kernel/qobject.h:142 #13 0x7f389638450b in QGraphicsView::mousePressEvent (this=0x558444247f90, event=0x7ffdb3cc1950) at /usr/include/c++/8/bits/atomic_base.h:390 #14 0x7f38960b9e69 in QWidget::event (this=this@entry=0x558444247f90, event=event@entry=0x7ffdb3cc1950) at kernel/qwidget.cpp:8897 #15 0x7f3896159c4e in QFrame::event (this=0x558444247f90, e=0x7ffdb3cc1950) at widgets/qframe.cpp:550 #16 0x7f389638567b in QGraphicsView::viewportEvent(QEvent*) () at graphicsview/qgraphicsview.cpp:2969 #17 0x7f3895070a53 in QCoreApplicationPrivate::sendThroughObject
[krita] [Bug 387783] New: System bugs almost everywhere
https://bugs.kde.org/show_bug.cgi?id=387783 Bug ID: 387783 Summary: System bugs almost everywhere Product: krita Version: 3.3.2 Platform: MS Windows OS: MS Windows Status: UNCONFIRMED Severity: grave Priority: NOR Component: Tools Assignee: krita-bugs-n...@kde.org Reporter: funelca...@gmail.com Target Milestone: --- Created attachment 109301 --> https://bugs.kde.org/attachment.cgi?id=109301&action=edit This popped up and I can't make it go away I'm currently using a HUION610 PRO,and here is a big list of things that don't work,even though I'm loving this program. - Shortcuts are messed up (ex: The "Zoom In" Shortcut on the tablet ROTATES the image,and some of the tablet's buttons switch function time by time. The erase button once was for erasing,then became "Save As" and now "Filter settings" - (watch attached file) This popped up from nothing,and now I can't do anything on the file. It just remains there - Time by time,the program could have influence on the PC's system. This only happens when I'm drawing. A little example,but when I'm on a youtube playlist,when i skip to a video,Chrome opens it on a completly different window. I hope that I can solve this soon,regards. -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 387783] System bugs almost everywhere
https://bugs.kde.org/show_bug.cgi?id=387783 --- Comment #2 from Carlo --- Ok,thanks for your time boys. -- You are receiving this mail because: You are watching all bug changes.
