[partitionmanager] [Bug 486206] does not give focus to Authentication required
https://bugs.kde.org/show_bug.cgi?id=486206 --- Comment #4 from Carlo Gioia --- Good Day Andrius and others Yesterday I received notice of KDE Partition Manager version 24.02.2. I updated to this version, ran a quick test and am able to confirm the bug is gone. On Sat, Apr 27, 2024 at 11:46 AM Andrius Štikonas wrote: > https://bugs.kde.org/show_bug.cgi?id=486206 > > Andrius Štikonas changed: > >What|Removed |Added > > > Status|REPORTED|RESOLVED > Resolution|--- |WORKSFORME > > --- Comment #1 from Andrius Štikonas --- > Seems to work fine on Plasma 6 with Wayland. (though I remember this was > not > working before...) > > -- > You are receiving this mail because: > You reported the bug. -- 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=edit brief video demonstrating this weird behaviour -- 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.
[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=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.
[partitionmanager] [Bug 486206] does not give focus to Authentication required
https://bugs.kde.org/show_bug.cgi?id=486206 --- Comment #3 from Carlo Gioia --- Sorry for this ... a bug is a bug is a bug ... 40+ years of it taught me to let my customers report it and we would fix it. I do have a workaround. I do not need another method (wayland) to get around the issue. I know it's not a big deal AND since you stated it was an issue before ... Perhaps this should be part of the testing script. On Sat, Apr 27, 2024 at 11:47 AM Andrius Štikonas wrote: > https://bugs.kde.org/show_bug.cgi?id=486206 > > --- Comment #2 from Andrius Štikonas --- > Let me know if you can still reproduce it there... > > -- > You are receiving this mail because: > You reported the bug. -- You are receiving this mail because: You are watching all bug changes.
[partitionmanager] [Bug 486206] New: does not give focus to Authentication required
https://bugs.kde.org/show_bug.cgi?id=486206 Bug ID: 486206 Summary: does not give focus to Authentication required Classification: Applications Product: partitionmanager Version: 23.08.5 Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: andr...@stikonas.eu Reporter: gioia.ca...@gmail.com Target Milestone: --- when invoking KDE partition Manager ... screen posps up ok but does not give focus to Authentication Required PolicyKit1 KDE agent ... it hides it ... you need to move scrre to see its right behind . other than that all is ok. This started happening in the last couple of months ... I was hoping it would be fixed by not. I know its not its not the Authentication required since it does get focus when called by Dolphin. Hopefully this is a simple setting that will soon be fixed . -- You are receiving this mail because: You are watching all bug changes.
[NeoChat] [Bug 485883] New: "View Notification" icon hides the "Expand Low Priority" icon
https://bugs.kde.org/show_bug.cgi?id=485883 Bug ID: 485883 Summary: "View Notification" icon hides the "Expand Low Priority" icon Classification: Applications Product: NeoChat Version: 24.02.2 Platform: Arch Linux OS: Linux Status: REPORTED Severity: minor Priority: NOR Component: General Assignee: fe...@posteo.de Reporter: matteo@gmail.com CC: c...@carlschwan.eu Target Milestone: --- Created attachment 168735 --> https://bugs.kde.org/attachment.cgi?id=168735=edit screenshot of the issue ## Description The "View Notification" button icon is over the "Expand Low Priority" icon making the second one non clickable. ## Steps to reproduce 1. Open app 2. Have enough rooms to fill in the vertical space (alternatively, resize the window) 3. Have at least one room set to low-priority 4. Enable the following configuration: General; Rooms and private chats: Separated ## What is the current bug behavior? The "View Notification" button icon is over the "Expand Low Priority" icon making the second one non clickable. The list cannot scroll further so the "Expand Low Priority" is difficult to interact with. ## What is the expected correct behavior? The buttons should both be easy to interact with. ## Relevant logs and/or screenshots ## Possible fixes Not sure how to solve this one, but the buttons should both be easy to interact with. Either move one of the two buttons or add some padding at the bottom of the list so "Expand" button becomes clickable. ## System/Matrix Information - **Distribution / Platform:** Arch linux / Plasma 6 / wayland ... - **Qt Version:** 6.7.0 - **NeoChat version:** 24.02.2 - **Quotient version:** 0.8.2 - **Matrix server:** neo.matteodroids.science -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 457487] After fixing the shaded/shuttered window feature, restarting kwin_x11 --replace forgets the shaded window sizes
https://bugs.kde.org/show_bug.cgi?id=457487 carlo cancellieri changed: What|Removed |Added CC||ccancelli...@hotmail.com --- Comment #6 from carlo cancellieri --- Dear KDE, this is also affecting my Vanilla system since a while. Personally I love to use this functionality in combination with keep on top so I can shade and unshade windows just hovering it's bar. I think this functionality is valuable and I'd love to give my assistance in debugging experimenting for a solution if someone is so kind to look into it. Best, Carlo Info: Operating System: Kubuntu 22.04 KDE Plasma Version: 5.24.7 KDE Frameworks Version: 5.92.0 Qt Version: 5.15.3 Kernel Version: 5.15.0-88-generic (64-bit) Graphics Platform: X11 Processors: 8 × Intel® Core™ i7-10510U CPU @ 1.80GHz Memory: 15,3 GiB of RAM Graphics Processor: NVIDIA GeForce MX250/PCIe/SSE2 -- 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.
[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 #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 #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.
[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.
[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.
[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.
[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.
[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 #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.
[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.
[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.
[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.
[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.
[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.
[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 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 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] 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.
[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] 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.
[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.
[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.
[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.
[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.
[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 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] 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.
[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.
[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.
[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.
[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.
[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.
[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 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.
[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.
[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.
[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 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 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 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.
[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.
[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.
[systemsettings] [Bug 456050] New: Adding second langue turns language into dutch no matter where I put it.
https://bugs.kde.org/show_bug.cgi?id=456050 Bug ID: 456050 Summary: Adding second langue turns language into dutch no matter where I put it. Product: systemsettings Version: 5.25.1 Platform: Archlinux Packages OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: kcm_language Assignee: h...@kde.org Reporter: ca...@alinoe.com CC: plasma-b...@kde.org Target Milestone: --- SUMMARY *** STEPS TO REPRODUCE 1. Go to System Settings --> Personalization --> Regional Settings --> Language 2. Add on top of "American English (default)" the language "Nederlands". Put "Nederlands" at the bottom. 3. Save, reboot, run plasma/kde 4. On konsole prompt type an error (for example: sudo foobar). It will report an error in Dutch. The direct reason for seeing Dutch is (apparently) due to the environment variable LANGUAGE which is set to "en_US:nl". Changing that into "nl:en_US" doesn't make a difference: still dutch error messages. Only when changing LANGUAGE into "en_US" you get English error messages. OBSERVED RESULT EXPECTED RESULT Everything is still 100% English (en_US), but now spelling checking also works when I type in Dutch. ADDITIONAL INFORMATION There is another bug; if you choose in the list of Formats (not Language) en_NL - then everything breaks because that locale doesn't exist and is not supported. I think it SHOULD be supported: everyone in the Netherlands speaks English - this basically a two-language country, one of them being English. Aka en_NL makes a LOT of sense, exactly like all the other en_XY locales. Nevertheless, if I select it, then I expect it to work - and it doesn't: you can't generate that locale because certain idiots think it is not needed and refuse to add it (see for example https://sourceware.org/bugzilla/show_bug.cgi?id=14085) -- 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.
[kwin] [Bug 453147] New: amdgpu: GPU reset crash loop
https://bugs.kde.org/show_bug.cgi?id=453147 Bug ID: 453147 Summary: amdgpu: GPU reset crash loop Product: kwin Version: 5.24.4 Platform: Archlinux Packages OS: Linux Status: REPORTED Severity: crash Priority: NOR Component: core Assignee: kwin-bugs-n...@kde.org Reporter: matteo@gmail.com Target Milestone: --- SUMMARY I have a Vulkan application (a non famous game engine) that sometimes triggers a gpu reset. A gpu fence timeout seems to be my latest issue, but I think other misuses might have happened other times. When this happens, the GPU attempts to reset, but kwin seems to be unble to recover and trips a gpu reset in an almost infinite loop. After the first reset the mouse input is unresponsive, probably because video buffers do not update. STEPS TO REPRODUCE 1. Run kde in wayland mode on AMD open graphic stack 2. Reset the gpu (accidentally, can I manually reset it to test?) 3. enjoy the corruption loop OBSERVED RESULT The screens display are displaying corrupted images with random pixels in a grid pattern going full green or red. The corruption increases at every gpu reset. After a bunch of resets the screen goes into tty mode (kwin crashed completely I guess). dmesg output: ``` [25894.802524] [drm:amdgpu_dm_atomic_commit_tail [amdgpu]] *ERROR* Waiting for fences timed out! [25895.015855] [drm:amdgpu_dm_atomic_commit_tail [amdgpu]] *ERROR* Waiting for fences timed out! [25899.719088] [drm:amdgpu_job_timedout [amdgpu]] *ERROR* ring gfx_0.0.0 timeout, signaled seq=2308869, emitted seq=2308871 [25899.719267] [drm:amdgpu_job_timedout [amdgpu]] *ERROR* Process information: process Tests pid 33837 thread Tests:cs0 pid 33839 [25899.719426] amdgpu :44:00.0: amdgpu: GPU reset begin! [25900.195085] amdgpu :44:00.0: [drm:amdgpu_ring_test_helper [amdgpu]] *ERROR* ring kiq_2.1.0 test failed (-110) [25900.195246] [drm:gfx_v10_0_hw_fini [amdgpu]] *ERROR* KGQ disable failed [25900.419828] amdgpu :44:00.0: [drm:amdgpu_ring_test_helper [amdgpu]] *ERROR* ring kiq_2.1.0 test failed (-110) [25900.419986] [drm:gfx_v10_0_hw_fini [amdgpu]] *ERROR* KCQ disable failed [25900.644591] [drm:gfx_v10_0_hw_fini [amdgpu]] *ERROR* failed to halt cp gfx [25900.651532] [drm] free PSP TMR buffer [25900.683662] amdgpu :44:00.0: amdgpu: BACO reset [25902.770356] amdgpu :44:00.0: amdgpu: GPU reset succeeded, trying to resume [25902.770506] [drm] PCIE GART of 512M enabled (table at 0x00800030). [25902.770522] [drm] VRAM is lost due to GPU reset! [25902.770523] [drm] PSP is resuming... [25902.816962] [drm] reserve 0x90 from 0x81fe40 for PSP TMR [25902.858907] amdgpu :44:00.0: amdgpu: RAS: optional ras ta ucode is not available [25902.864919] amdgpu :44:00.0: amdgpu: RAP: optional rap ta ucode is not available [25902.864921] amdgpu :44:00.0: amdgpu: SECUREDISPLAY: securedisplay ta ucode is not available [25902.864924] amdgpu :44:00.0: amdgpu: SMU is resuming... [25902.867331] amdgpu :44:00.0: amdgpu: SMU is resumed successfully! [25903.171192] [drm] kiq ring mec 2 pipe 1 q 0 [25903.172711] [drm] VCN decode and encode initialized successfully(under DPG Mode). [25903.172796] [drm] JPEG decode initialized successfully. [25903.172812] amdgpu :44:00.0: amdgpu: ring gfx_0.0.0 uses VM inv eng 0 on hub 0 [25903.172815] amdgpu :44:00.0: amdgpu: ring comp_1.0.0 uses VM inv eng 1 on hub 0 [25903.172816] amdgpu :44:00.0: amdgpu: ring comp_1.1.0 uses VM inv eng 4 on hub 0 [25903.172817] amdgpu :44:00.0: amdgpu: ring comp_1.2.0 uses VM inv eng 5 on hub 0 [25903.172818] amdgpu :44:00.0: amdgpu: ring comp_1.3.0 uses VM inv eng 6 on hub 0 [25903.172819] amdgpu :44:00.0: amdgpu: ring comp_1.0.1 uses VM inv eng 7 on hub 0 [25903.172820] amdgpu :44:00.0: amdgpu: ring comp_1.1.1 uses VM inv eng 8 on hub 0 [25903.172821] amdgpu :44:00.0: amdgpu: ring comp_1.2.1 uses VM inv eng 9 on hub 0 [25903.172822] amdgpu :44:00.0: amdgpu: ring comp_1.3.1 uses VM inv eng 10 on hub 0 [25903.172823] amdgpu :44:00.0: amdgpu: ring kiq_2.1.0 uses VM inv eng 11 on hub 0 [25903.172824] amdgpu :44:00.0: amdgpu: ring sdma0 uses VM inv eng 12 on hub 0 [25903.172825] amdgpu :44:00.0: amdgpu: ring sdma1 uses VM inv eng 13 on hub 0 [25903.172826] amdgpu :44:00.0: amdgpu: ring vcn_dec uses VM inv eng 0 on hub 1 [25903.172826] amdgpu :44:00.0: amdgpu: ring vcn_enc0 uses VM inv eng 1 on hub 1 [25903.172827] amdgpu :44:00.0: amdgpu: ring vcn_enc1 uses VM inv eng 4 on hub 1 [25903.172828] amdgpu :44:00.0: amdgpu: ring jpeg_dec uses VM inv eng 5 on hub 1 [25903.175542] amdgpu :44:00.0: amdgpu: recover vram bo from shadow start [25903.175638] amdgpu :44:00.0: amdgpu: recover vram bo from shadow done [25903.175640] [drm] Skip scheduling IBs! ... [26254.330249] [drm] Skip scheduling IBs! [26254.330170] [drm:amdgpu_cs_ioctl
[muon] [Bug 450881] "Commiting changes" screen of muon lacks padding
https://bugs.kde.org/show_bug.cgi?id=450881 Carlo Vanini changed: What|Removed |Added Status|ASSIGNED|RESOLVED Latest Commit||https://invent.kde.org/syst ||em/muon/commit/74487f4ad24c ||2057e355e42ac044e80fc4b69ca ||f Resolution|--- |FIXED --- Comment #3 from Carlo Vanini --- Git commit 74487f4ad24c2057e355e42ac044e80fc4b69caf by Carlo Vanini, on behalf of Fire Fragment. Committed on 08/04/2022 at 16:38. Pushed by vanini into branch 'master'. Add margins to TransactionWidget When installing packages, there's a screen showing information about the installation. It had no padding and didn't look good. This commit adds padding. GUI: M +7-0src/MainWindow.cpp https://invent.kde.org/system/muon/commit/74487f4ad24c2057e355e42ac044e80fc4b69caf -- 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.
[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.
[muon] [Bug 425643] Muon Package Manager is crashed when I want install package digikam
https://bugs.kde.org/show_bug.cgi?id=425643 --- Comment #2 from Carlo Vanini --- (In reply to Adrián López Galera from comment #1) > I have many PPAs. > GPG error: https://download.mono-project.com/repo/ubuntu stable-focal > InRelease: NO_PUBKEY A6A19B38D3D831EF Thank you for your report. >From this error it looks like you didn't add the repository key for one of the PPAs (or the key has changed). Is that correct? Nevertheless, the crash is probably unrelated to that. It is caused by an existing race between the search and update of the list of available packages. -- 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.
[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 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.
[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.
[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.
[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.
[plasmashell] [Bug 414785] Notifications cause lag/freeze in plasmashell and apps when using an NVIDIA GPU
https://bugs.kde.org/show_bug.cgi?id=414785 --- Comment #33 from Carlo Meijer --- (In reply to Michael Hamilton from comment #32) > (In reply to Carlo Meijer from comment #29) > > I managed to work around the problem by means of the solution proposed here, > > number 2 (Disabling KWIN Vsync and force full composition pipeline): > > https://www.reddit.com/r/EndeavourOS/comments/p8b2kf/ > > for_those_that_have_stutterlags_problems_with_kde/ > > I already reported it in the relevant nvidia forums topic, but I'm also > > posting it here since disabling vsync in KWin and forcing it to be offloaded > > to the nvidia driver seems to fix the issue. Perhaps there's something > > unforeseen going on in KWin and something can be done in KWin to > > fix/workaround the issue (perhaps some nvidia-specific hacks). > > > > I found that latte-dock still stutters, disabling tooltips solved that one > > for me. I was hoping this magically solved it as well, but apparently not. > > I tried the described work around. it doesn't appear to fix the stutter > described in bug 443696 (a duplicate of this one), the test being: > > for i in 1 2 3 4 5 6 7 8 9 10; do notify-send --expire-time 2 test > $i; done > > Perhaps bug 443696 is not actually the same as this one. It seems that, indeed, there are two distinct issues: 1) is the one described by TS; as long as the notification is open, everything stutters. I had this issue as well, and solved it by offloading vsync to the nvidia driver, as referenced in my previous post. 2) is described in 443696 and 436902; stutters and cpu spikes appear only during the appearance and disappearance of a notification. Now that I pay attention to it, it seems that my system is also affected by (2). However, in my humble opinion, it's is much less severe than (1). I can live with it until wayland is ready for daily use. Hopefully that will magically make the issue go away. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 414785] Notifications cause lag/freeze in plasmashell and apps when using an NVIDIA GPU
https://bugs.kde.org/show_bug.cgi?id=414785 --- Comment #31 from Carlo Meijer --- (In reply to Lapineige from comment #30) > > I already reported it in the relevant nvidia forums topic > > Can you post the link here please ? Sure, https://forums.developer.nvidia.com/t/desktop-notifications-cause-stutter-on-kde-plasma-5-21-5/177717/8 I thought the topic was created by TS, but I'll post the link anyways. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 414785] Notifications cause lag/freeze in plasmashell and apps when using an NVIDIA GPU
https://bugs.kde.org/show_bug.cgi?id=414785 Carlo Meijer changed: What|Removed |Added CC||ca...@youcontent.nl --- Comment #29 from Carlo Meijer --- I managed to work around the problem by means of the solution proposed here, number 2 (Disabling KWIN Vsync and force full composition pipeline): https://www.reddit.com/r/EndeavourOS/comments/p8b2kf/for_those_that_have_stutterlags_problems_with_kde/ I already reported it in the relevant nvidia forums topic, but I'm also posting it here since disabling vsync in KWin and forcing it to be offloaded to the nvidia driver seems to fix the issue. Perhaps there's something unforeseen going on in KWin and something can be done in KWin to fix/workaround the issue (perhaps some nvidia-specific hacks). I found that latte-dock still stutters, disabling tooltips solved that one for me. I was hoping this magically solved it as well, but apparently not. -- You are receiving this mail because: You are watching all bug changes.
[muon] [Bug 445603] usb-creator-kde missing python3-sip
https://bugs.kde.org/show_bug.cgi?id=445603 Carlo Vanini changed: What|Removed |Added Resolution|--- |NOT A BUG Status|REPORTED|RESOLVED --- Comment #1 from Carlo Vanini --- Hello, thank you for reporting. What you describe, a missing dependency, is a problem in packaging. You should report the bug to you distribution (Ubuntu) against the usb-creator-kde package. This is not something that can be fixed in Muon. -- 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-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.
[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.
[systemsettings] [Bug 411795] Crash in QQmlData::wasDeleted() after adding a language in the Translations KCM
https://bugs.kde.org/show_bug.cgi?id=411795 --- Comment #13 from Carlo Borger --- For me it seems the issue is not there anymore. I run qt 5.15.2 by the way. -- 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 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.
[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] 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 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 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.
[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: 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 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,
[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.
[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.
[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.
[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 #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 #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 #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 #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.
[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] 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.
[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.
[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.
[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.
[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.
[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.
[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.
[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.
[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.
[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.
