[kwin] [Bug 480032] Window is out of screen after unplugging external display
https://bugs.kde.org/show_bug.cgi?id=480032 Luca Carlon changed: What|Removed |Added CC||carlon.l...@gmail.com --- Comment #5 from Luca Carlon --- This happens to me very frequently, without any user switch. Simply unplug a screen when multiple windows are open: some windows are moved from the unplugged screen to the visible one, others remain invisible. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 486535] kwin_wayland starts consuming a high amount of CPU
https://bugs.kde.org/show_bug.cgi?id=486535 --- Comment #1 from Luca Carlon --- I can reproduce with other apps using XWayland. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 486550] Wrong layout of the desktop folder settings window
https://bugs.kde.org/show_bug.cgi?id=486550 --- Comment #1 from Luca Carlon --- Created attachment 169178 --> https://bugs.kde.org/attachment.cgi?id=169178=edit Layout of the window after resizing it. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 486550] New: Wrong layout of the desktop folder settings window
https://bugs.kde.org/show_bug.cgi?id=486550 Bug ID: 486550 Summary: Wrong layout of the desktop folder settings window Classification: Plasma Product: plasmashell Version: 6.0.4 Platform: Manjaro OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: Image Wallpaper Assignee: plasma-b...@kde.org Reporter: carlon.l...@gmail.com CC: notm...@gmail.com, qydwhotm...@gmail.com Target Milestone: 1.0 SUMMARY Resizing the "Desktop Folder Settings" may lead to a wrong layout. STEPS TO REPRODUCE 1. Open the desktop folder settings window from the menu in the desktop. 2. Resize it. OBSERVED RESULT The window is clearly too small, it only shows two images (this should also be fixed). It is therefore necessary to always resize it. After resizing it, the layout typically breaks, and the bar containing the "add" and "get new" buttons is misplaced or even lost. EXPECTED RESULT The title bar containing the "add" and "get new" buttons should remain at the top. SOFTWARE/OS VERSIONS Linux/KDE Plasma: 6.8.8-2-MANJARO (64-bit) KDE Plasma Version: 6.0.4 KDE Frameworks Version: 6.1.0 Qt Version: 6.7.0 -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 486535] New: kwin_wayland starts consuming a high amount of CPU
https://bugs.kde.org/show_bug.cgi?id=486535 Bug ID: 486535 Summary: kwin_wayland starts consuming a high amount of CPU Classification: Plasma Product: kwin Version: unspecified Platform: Manjaro OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: kwin-bugs-n...@kde.org Reporter: carlon.l...@gmail.com Target Milestone: --- SUMMARY After a variable amount of time, kwin_wayland starts consuming a high amount of CPU. Typical CPU usage of kwin_wayland while system is idle is 0-2% on this machine. When the problem appears, consumption rises to 8-12% or even more. Framerate is lower and CPU fan accelerates. This only started to happen when I upgraded to Plasma 6. It never happened with Plasma 5. STEPS TO REPRODUCE After trying many things, I found a weird way to reproduce. It does not happen 100% of the times, but doesn't take much to reproduce here: 1. Close every application/window. 2. Open VLC and play a video (in Manjaro VLC 3 is using XWayland by default); 3. Seek a few times into the video or/and try to resize the window a bit. This makes kwin_wayland consume a bit more CPU, going above 20%, which may be normal; 4. wait a few seconds and close VNC. 5. In some cases, kwin_wayland goes back to 1% or less, which is OK. Go back to step 2 in this case and try again. In other cases, it remains at around 10% CPU or even more. OBSERVED RESULT System framerate lowers. It even affects video playback in VLC, making the system pretty bad to use. Fan accelerates, leading to higher battery consumption. The situation does not fix by itself, I need to reboot or logout/login. EXPECTED RESULT With the provided steps, I'd expect kwin_wayland to go back to the usual 0-2% CPU usage after VLC is closed. SOFTWARE/OS VERSIONS Linux/KDE Plasma: 6.8.8-2-MANJARO (64-bit) KDE Plasma Version: 6.0.4 KDE Frameworks Version: 6.1.0 Qt Version: 6.7.0 ADDITIONAL INFO: I tried to disable vaapi acceleration. Nothing changes. I tried to blacklist nvidia (I only use the Intel GPU anyway), nothing changed. -- You are receiving this mail because: You are watching all bug changes.
[kde] [Bug 483625] The microphone icon is missing. Notifications flew to the corner of the screen
https://bugs.kde.org/show_bug.cgi?id=483625 Luca Carlon changed: What|Removed |Added CC||carlon.l...@gmail.com --- Comment #10 from Luca Carlon --- I'm also experiencing this issue. I've never experienced this with Plasma 5. It only started with Plasma 6. I found a way to reproduce quickly: 1. setup the system to have two screens (I have the laptop screen and an external screen), and set the external screen to be the primary; 2. unplug the external screen; 3. wait for the system to adapt to the new setup; 4. plug the screen again; 5. try to set the volume; 6. you should see the volume window in the upper left corner of one screen. It won't even move to the other screen properly. It is also possible to simply turn off the screen by using the proper Plasma shortcut. To fix: logout and then login again. I can reproduce in a few seconds. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 481000] Kicker not highlighting selection, neither via keyboard nor hover
https://bugs.kde.org/show_bug.cgi?id=481000 --- Comment #21 from Luca Carlon --- The problem did not appear again for me after what I explained above. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 481000] Kicker not highlighting selection, neither via keyboard nor hover
https://bugs.kde.org/show_bug.cgi?id=481000 Luca Carlon changed: What|Removed |Added CC||carlon.l...@gmail.com --- Comment #19 from Luca Carlon --- I was also affected by this problem (on Manjaro). The problem started with the updates published the 22/2/2024. I tried to downgrade the packages starting with "k" one by one, but nothing changed. I then downgraded everything else and the problem was fixed. I then tried to upgrade again one by one, but I am now unfortunately unable to reproduce the problem. I can provide the pacman log of that day if needed, but there are more than 300 packages. -- You are receiving this mail because: You are watching all bug changes.
[Breeze] [Bug 462005] Window shadow outlines have artifacts on HiDPI, especially with fractional scale factors
https://bugs.kde.org/show_bug.cgi?id=462005 --- Comment #26 from Luca Carlon --- Hiding it would be useful for the systems where it is broken. Would it be possible to hide the broken feature for Plasma5, which is still what users will use for several months? For instance, would it be possible to simply not draw it when scaling != 1? I do not think users will complain for a missing broken feature. -- You are receiving this mail because: You are watching all bug changes.
[Breeze] [Bug 462005] Window shadow outlines have artifacts on HiDPI, especially with fractional scale factors
https://bugs.kde.org/show_bug.cgi?id=462005 --- Comment #24 from Luca Carlon --- Any way to, at least, hide it? It is of no practical use, so hiding it is perfectly acceptable. At least users will not remain with a broken feature for many other months. -- You are receiving this mail because: You are watching all bug changes.
[Breeze] [Bug 462005] Window shadow outlines have artifacts on HiDPI, especially with fractional scale factors
https://bugs.kde.org/show_bug.cgi?id=462005 --- Comment #22 from Luca Carlon --- Can the fix be backported? -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 457130] Bluetooth Remember Previous Status setting works on reboot, but not shutdown
https://bugs.kde.org/show_bug.cgi?id=457130 Luca Carlon changed: What|Removed |Added CC||carlon.l...@gmail.com -- You are receiving this mail because: You are watching all bug changes.
[kdeconnect] [Bug 477910] New: Cannot unpause VLC after pausing
https://bugs.kde.org/show_bug.cgi?id=477910 Bug ID: 477910 Summary: Cannot unpause VLC after pausing Classification: Applications Product: kdeconnect Version: 23.08.3 Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: android-application Assignee: albertv...@gmail.com Reporter: carlon.l...@gmail.com CC: andrew.g.r.hol...@gmail.com Target Milestone: --- SUMMARY It seems that I cannot unpause VLC after pausing it with kdeconnect. The play/resume button becomes disabled. I found this https://code.videolan.org/videolan/vlc/-/issues/21419, but it seems a bit different. In my case it only happens with kdeconnect, and not with the Plasma controls. It only happens with VLC though. Other media players, like with the Brave browser, do not show the same problem, kdeconnect can resume properly. STEPS TO REPRODUCE 1. Start a video with VLC (version 3.0.20). 2. Select it with kdeconnect. 3. Pause it. OBSERVED RESULT The play/resume button is visible, but it is disabled. EXPECTED RESULT After pausing the video, the play/resume button should be visible and enabled. Pressing it should resume playback. SOFTWARE/OS VERSIONS Linux: 6.6.3 KDE Plasma Version: 5.27.9 KDE Frameworks Version: 5.112.0 Qt Version: 5.15.11 -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 476501] Plasmashell crashes immediately at start
https://bugs.kde.org/show_bug.cgi?id=476501 --- Comment #2 from Luca Carlon --- The problems with pipewire are probably simply related to the fact that I did not configure it in any way. I simply installed it so I could build Plasma 6. I do not need it to work for the moment. Are you saying I built something incorrectly? Or are you saying the problem is in some pipewire library? Cause I do not see anything specifically related to pipewire in the stack trace. I only see the registration of a QQuickItem. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 476501] New: Plasmashell crashes immediately at start
https://bugs.kde.org/show_bug.cgi?id=476501 Bug ID: 476501 Summary: Plasmashell crashes immediately at start Classification: Plasma Product: plasmashell Version: master Platform: Manjaro OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: Task Manager and Icons-Only Task Manager Assignee: plasma-b...@kde.org Reporter: carlon.l...@gmail.com CC: qydwhotm...@gmail.com Target Milestone: 1.0 SUMMARY Built Plasma 6 with kdesrc-build. Plasmashell immediately crashes. This is what I could get with gdb: #0 __strcmp_avx2 () at ../sysdeps/x86_64/multiarch/strcmp-avx2.S:287 #1 0x74b4430e in QMetaObject::indexOfClassInfo(char const*) const () at /usr/lib/libQt6Core.so.6 #2 0x76acc438 in QQmlMetaType::registerType(QQmlPrivate::RegisterType const&) () at /usr/lib/libQt6Qml.so.6 #3 0x76a5bc20 in QQmlPrivate::qmlregister(QQmlPrivate::RegistrationType, void*) () at /usr/lib/libQt6Qml.so.6 #4 0x7fff9405d95b in qmlRegisterType(char const*, int, int, char const*) (qmlName=0x7fff940616fc "PipeWireSourceItem", versionMinor=1, versionMajor=0, uri=0x7fff9c5f6e10 "org.kde.taskmanager") at /usr/include/qt6/QtQml/qqml.h:328 #5 TaskManager::TaskManagerPlugin::registerTypes(char const*) (this=, uri=0x7fff9c5f6e10 "org.kde.taskmanager") at /home/lucadev/kde/src/plasma-workspace/libtaskmanager/declarative/taskmanagerplugin.cpp:37 #6 0x76acdabd in QQmlMetaType::registerPluginTypes(QObject*, QString const&, QString const&, QString const&, QTypeRevision, QList*) () at /usr/lib/libQt6Qml.so.6 #7 0x76af7e03 in () at /usr/lib/libQt6Qml.so.6 #8 0x76aaf168 in QQmlImports::importExtension(QString const&, QTypeRevision, QQmlImportDatabase*, QQmlTypeLoaderQmldirContent const*, QList*) () at /usr/lib/libQt6Qml.so.6 #9 0x76ab9dbd in QQmlImports::addLibraryImport(QQmlImportDatabase*, QString const&, QString const&, QTypeRevision, QString const&, QString const&, QFlags, unsigned short, QList*) () at /usr/lib/libQt6Qml.so.6 #10 0x76b4c814 in () at /usr/lib/libQt6Qml.so.6 #11 0x76b49d66 in QQmlTypeLoader::Blob::addLibraryImport(std::shared_ptr const&, QList*) () at /usr/lib/libQt6Qml.so.6 #12 0x76b4b379 in QQmlTypeLoader::Blob::addImport(QV4::CompiledData::Import const*, QFlags, QList*) () at /usr/lib/libQt6Qml.so.6 #13 0x76b42071 in () at /usr/lib/libQt6Qml.so.6 #14 0x76b4554a in QQmlTypeLoader::setData(QQmlRefPointer const&, QQmlDataBlob::SourceCodeData const&) () at /usr/lib/libQt6Qml.so.6 #15 0x76b45aa1 in QQmlTypeLoader::setData(QQmlRefPointer const&, QString const&) () at /usr/lib/libQt6Qml.so.6 #16 0x76b486ea in QQmlTypeLoader::loadThread(QQmlRefPointer const&) () at /usr/lib/libQt6Qml.so.6 #17 0x76b4d559 in () at /usr/lib/libQt6Qml.so.6 #18 0x76a54dcb in () at /usr/lib/libQt6Qml.so.6 #19 0x75f7134b in QApplicationPrivate::notify_helper(QObject*, QEvent*) () at /usr/lib/libQt6Widgets.so.6 #20 0x74b3ba98 in QCoreApplication::notifyInternal2(QObject*, QEvent*) () at /usr/lib/libQt6Core.so.6 #21 0x74b3be1b in QCoreApplicationPrivate::sendPostedEvents(QObject*, int, QThreadData*) () at /usr/lib/libQt6Core.so.6 #22 0x74d3dd34 in () at /usr/lib/libQt6Core.so.6 #23 0x73c40f19 in () at /usr/lib/libglib-2.0.so.0 #24 0x73c9f2b7 in () at /usr/lib/libglib-2.0.so.0 #25 0x73c3f112 in g_main_context_iteration () at /usr/lib/libglib-2.0.so.0 #26 0x74d3bd24 in QEventDispatcherGlib::processEvents(QFlags) () at /usr/lib/libQt6Core.so.6 #27 0x74b45953 in QEventLoop::exec(QFlags) () at /usr/lib/libQt6Core.so.6 #28 0x74c2f43f in QThread::run() () at /usr/lib/libQt6Core.so.6 #29 0x74c74932 in () at /usr/lib/libQt6Core.so.6 #30 0x744aa9eb in start_thread (arg=) at pthread_create.c:444 #31 0x7452e7cc in clone3 () at ../sysdeps/unix/sysv/linux/x86_64/clone3.S:78 These are the logs printer by plasmashell: kf.svg: The theme "breath-dark" uses the legacy metadata.desktop. Consider contacting the author and asking them update it to use the newer JSON format. kf.svg: The theme "breath-dark" uses the legacy metadata.desktop. Consider contacting the author and asking them update it to use the newer JSON format. kf.plasma.core: The theme "breath-dark" uses the legacy metadata.desktop. Consider contacting the author and asking them update it to use the newer JSON format. kf.plasma.core: The theme "breath-dark" uses the legacy metadata.desktop. Consider contacting the author and asking them update it to use the newer JSON format. KPackageStructure of KPluginMetaData(pluginId:"org.kde.kdeconnect", fileName: "/usr/share/plasma/plasmoids/org.kde.kdeconnect/metadata.json") does not match requested format "Plasma/Applet" KPackageStructure of
[konsole] [Bug 373232] Horizontal lines with fractional HiDPI scaling
https://bugs.kde.org/show_bug.cgi?id=373232 --- Comment #261 from Luca Carlon --- I sent a few patches: https://invent.kde.org/utilities/konsole/-/commit/87c895cf9759e64829e7a4b7d117b810a0da4da8 https://invent.kde.org/utilities/konsole/-/commit/d747635ce1f542bd0e3e278f1f1b95b8b462500d https://invent.kde.org/utilities/konsole/-/commit/1f0cefa40815b00c2ba05453f8774ced180ca113 https://invent.kde.org/utilities/konsole/-/commit/fe46ddc09a59141b1c80c4d588df050151dc47a4 with these patches applied, I cannot reproduce the problem anymore in the Konsole terminal view (I can still see horizontal lines elsewhere in Plasma though). Hope this helps. -- You are receiving this mail because: You are watching all bug changes.
[konsole] [Bug 373232] Horizontal lines with fractional HiDPI scaling
https://bugs.kde.org/show_bug.cgi?id=373232 --- Comment #260 from Luca Carlon --- Git commit 1f0cefa40815b00c2ba05453f8774ced180ca113 by Luca Carlon. Committed on 09/05/2023 at 21:57. Pushed by hindenburg into branch 'master'. Invalidate a slightly larger area when scheduling a repaint In highdpi with fractional scaling factor some lines appear in the terminal area. This may be the result of areas that should be refreshed with new content that are not included in the invalidated area. This commit increases the invalidated area a bit to ensure the missing area is included. M +21 -13 src/terminalDisplay/TerminalDisplay.cpp M +19 -0src/terminalDisplay/TerminalDisplay.h M +1-0src/terminalDisplay/TerminalPainter.cpp https://invent.kde.org/utilities/konsole/commit/1f0cefa40815b00c2ba05453f8774ced180ca113 -- You are receiving this mail because: You are watching all bug changes.
[konsole] [Bug 373232] Horizontal lines with fractional HiDPI scaling
https://bugs.kde.org/show_bug.cgi?id=373232 --- Comment #258 from Luca Carlon --- This is another related patch for the underline: https://invent.kde.org/utilities/konsole/-/merge_requests/843. -- You are receiving this mail because: You are watching all bug changes.
[konsole] [Bug 373232] Horizontal lines with fractional HiDPI scaling
https://bugs.kde.org/show_bug.cgi?id=373232 Luca Carlon changed: What|Removed |Added CC||carlon.l...@gmail.com --- Comment #257 from Luca Carlon --- I can still see the horizontal lines. Is my configuration not sufficiently up to date? Konsole 22.12.3 Plasma: 5.27.4 Qt: 5.15.8 Wayland I also tried Konsole master with the same result. This issue is pretty frequent with fractional scaling, so I took 5 minutes to apply a quick patch: https://invent.kde.org/lcarlon/konsole/-/commit/eb11d4fd92996f92d9b37e997f74ec7ac08c25fa. I'm unable to reproduce the issue with it so far. That is clearly not fixing the bug, it is fixing the result though. Please note that, even with my patch, I could reproduce a slight issue with underlined font. I had a look and, from what I understand, that may have a different cause. -- You are receiving this mail because: You are watching all bug changes.
[Breeze] [Bug 468020] Window outline inconsistent between windows and sides of the same window and mispositioned
https://bugs.kde.org/show_bug.cgi?id=468020 --- Comment #4 from Luca Carlon --- (In reply to Nate Graham from comment #3) > Are you using a fractional scale factor, by any chance? I'm sorry, I forgot the obvious detail: fractional scaling set to 1.5 in Wayland. -- You are receiving this mail because: You are watching all bug changes.
[Breeze] [Bug 468020] Window outline inconsistent between windows and sides of the same window and mispositioned
https://bugs.kde.org/show_bug.cgi?id=468020 Luca Carlon changed: What|Removed |Added Attachment #157756|VLC looks reasonable. |vlc.png description|| -- You are receiving this mail because: You are watching all bug changes.
[Breeze] [Bug 468020] Window outline inconsistent between windows and sides of the same window and mispositioned
https://bugs.kde.org/show_bug.cgi?id=468020 Luca Carlon changed: What|Removed |Added Attachment #157755|Different look of the |konversation.png description|outline on two sides of a | |window. | -- You are receiving this mail because: You are watching all bug changes.
[Breeze] [Bug 468020] Window outline inconsistent between windows and sides of the same window and mispositioned
https://bugs.kde.org/show_bug.cgi?id=468020 --- Comment #2 from Luca Carlon --- Created attachment 157757 --> https://bugs.kde.org/attachment.cgi?id=157757=edit settings.png -- You are receiving this mail because: You are watching all bug changes.
[Breeze] [Bug 468020] Window outline inconsistent between windows and sides of the same window and mispositioned
https://bugs.kde.org/show_bug.cgi?id=468020 --- Comment #1 from Luca Carlon --- Created attachment 157756 --> https://bugs.kde.org/attachment.cgi?id=157756=edit VLC looks reasonable. -- You are receiving this mail because: You are watching all bug changes.
[Breeze] [Bug 468020] New: Window outline inconsistent between windows and sides of the same window and mispositioned
https://bugs.kde.org/show_bug.cgi?id=468020 Bug ID: 468020 Summary: Window outline inconsistent between windows and sides of the same window and mispositioned Classification: Plasma Product: Breeze Version: 5.27.3 Platform: Manjaro OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: window decoration Assignee: plasma-b...@kde.org Reporter: carlon.l...@gmail.com CC: kwin-bugs-n...@kde.org, uhh...@gmail.com Target Milestone: --- Created attachment 157755 --> https://bugs.kde.org/attachment.cgi?id=157755=edit Different look of the outline on two sides of a window. SUMMARY The new outline feature in 5.27 may be appreciated or not, but I would like to point out a couple of things that made me think that it was a bug at first. I attached a few images to show what I see. If you zoom in a lot you'll clearly see the problems. 1. konversation.png: this image shows the bottom left corner of konversation. As you can see the left border has an outline, the bottom border does not seem to have the outline. The result is bad and seems buggy. 2. vlc.png: in this image, the outline looks identical on all sides. This does not seem buggy. 3. settings.png: the outline on the left and at the top is not contiguous to the window. There is a transparent line between the window and the outline. I do not clearly understand if this is expected, I do not think so, but in any case it does not seem to be consistent with what I see in other windows (like in vlc.png), and it is not even consistent with the outline at the bottom. This can also be seen in konversation.png. STEPS TO REPRODUCE 1. 2. 3. OBSERVED RESULT Outline is missing or mispositioned, inconsistent between different windows and even between sides of the same window. EXPECTED RESULT I am not sure what the expected result was. According to some images I saw online, like these https://invent.kde.org/plasma/breeze/uploads/2eeb591d95a296adfa2daee4a985351e/Screenshot_20230302_181452.png, I guess there shouldn't be a transparent line and the outline should be identical on all sides. I'd also expect it to be identical for all windows. SOFTWARE/OS VERSIONS KDE Plasma Version: 5.27.3 KDE Frameworks Version: 5.104.0 Qt Version: 5.15.8 Linux: 6.1.21-1-MANJARO (64-bit) Wayland -- You are receiving this mail because: You are watching all bug changes.
[konsole] [Bug 453519] Horizontal lines with fractional HiDPI scaling
https://bugs.kde.org/show_bug.cgi?id=453519 --- Comment #6 from Luca Carlon --- Created attachment 154927 --> https://bugs.kde.org/attachment.cgi?id=154927=edit Horizontal lines in Plasma menus. Something very similar happens in Plasma in other places, not sure if this is related. Can this be related? -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 462290] New: A window should not be moved to the top on a mouse down event when the event results in a selection
https://bugs.kde.org/show_bug.cgi?id=462290 Bug ID: 462290 Summary: A window should not be moved to the top on a mouse down event when the event results in a selection Classification: Plasma Product: kwin Version: 5.26.3 Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: glx Assignee: kwin-bugs-n...@kde.org Reporter: carlon.l...@gmail.com Target Milestone: --- SUMMARY This is a pretty bothering behavior of Plasma. When something is selected in a window that is not on top, that window is brought to the top immediately on the mouse down event. This creates a problem: when something is being selected to be dragged to the window on top, the mouse down event hides the window immediately, making it impossible to drop the selected object. Both Mac OS and Windows do not behave like this, and I think this should be the proper behavior. STEPS TO REPRODUCE 1. Place a dolphin window somewhere and make it pretty large. 2. Open a new dolphin window and make it smaller, overlapping the previous one. 3. Now try to move a file from the first window (which is not on top) into the smaller widow (which is on top). OBSERVED RESULT The result is that the smaller window is hidden as soon as the file is selected. This makes it impossible to drop on it. EXPECTED RESULT In my opinion, the window in the back should not be moved to the top on mouse down event on selection. The mouse down event should select the file in the back window, but the top window should remain on top. This makes it possible to drop on it. SOFTWARE/OS VERSIONS Linux/KDE Plasma: Wayland KDE Plasma Version: 5.26.3 KDE Frameworks Version: 5.99.0 Qt Version: 5.15.7 -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 460440] Black background and missing context menu on the desktop in multiscreen configuration
https://bugs.kde.org/show_bug.cgi?id=460440 --- Comment #4 from Luca Carlon --- I read the bugreport you linked. Are you sure this is really a duplicate of that? In that report I read: "Wallpaper/tablet settings are restored to default". One thing is losing some custom configuration, one other thing is a malfunctioning system, missing background and missing context menu that can only be fixed by rebooting or restarting plasmashell. Please note that I did not read the entire thread, I'm just asking for a confirmation. I also sometimes see that the background is restored to default, that is a different, less relevant issue. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 460440] New: Black background and missing context menu on the desktop in multiscreen configuration
https://bugs.kde.org/show_bug.cgi?id=460440 Bug ID: 460440 Summary: Black background and missing context menu on the desktop in multiscreen configuration Classification: Plasma Product: plasmashell Version: 5.25.5 Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: plasma-b...@kde.org Reporter: carlon.l...@gmail.com CC: k...@davidedmundson.co.uk Target Milestone: 1.0 SUMMARY In some occasions, in a multiscreen configuration, one of the two screens may turn up to have a black background and to show no context menu on the desktop. Sometimes switching setup in the settings fixes the problem and the desktop is back to normal. Sometimes this does not work and unplugging and plugging the screen fixes the situation. Sometimes restarting plasmashell with "plasmashell --replace" fixes the situation. STEPS TO REPRODUCE Unfortunately this does not happen deterministically, but it is not infrequent. May happen immediately after the boot. OBSERVED RESULT One of the screens is working as usual, the other one has a black background and no context menu can be opened. If this happens on the primary screen, the panel is visible and seems to work as usual. Windows can be moved on the black background. EXPECTED RESULT Background should be present and context menu should open with the usual mouse button. SOFTWARE/OS VERSIONS Linux/KDE Plasma: 5.19.13 KDE Plasma Version: 5.25.5 Wayland KDE Frameworks Version: 5.98.0 Qt Version: 5.15.6 ADDITIONAL INFORMATION On the same machine I used to connect a HDMI 1080p screen and I do not remember this problem. This situation began after I bought a 4K USB-C screen. If the screen itself (or the 4K resolution) is really the cause of the issue is unknown. The failing setup is with two 4K screens, one with scaling factor 2 and the other with scaling factor 1.5. -- You are receiving this mail because: You are watching all bug changes.
[konsole] [Bug 453519] Horizontal lines with fractional HiDPI scaling (regression) under Wayland
https://bugs.kde.org/show_bug.cgi?id=453519 Luca Carlon changed: What|Removed |Added CC||carlon.l...@gmail.com --- Comment #1 from Luca Carlon --- This is happening to me as well in a 4K screen scaled to 150%. Linux/KDE Plasma: Manjaro/Plasma 5.24.6 (available in About System) KDE Plasma Version: 5.24.6 KDE Frameworks Version: 5.96.0 Qt Version: 5.15.5 -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 454635] Hovering over panel applet closes edit mode
https://bugs.kde.org/show_bug.cgi?id=454635 --- Comment #17 from Luca Carlon --- And if you created a new user, with a default setup, does it happen there? If it doesn't, then maybe there is a specific setup needed to reproduce it. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 454635] Hovering over panel applet closes edit mode
https://bugs.kde.org/show_bug.cgi?id=454635 --- Comment #15 from Luca Carlon --- Tried it. Also tried to enable "auto hide". Tried also on the secondary screen. Is this deterministically reproducible for you? -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 454635] Hovering over panel applet closes edit mode
https://bugs.kde.org/show_bug.cgi?id=454635 --- Comment #13 from Luca Carlon --- I tried on both X11 and Wayland but I'm not able to reproduce the issue in my build. But I'm sure I saw this some weeks ago. If the problem appears when hovering, these two places come to my mind: https://invent.kde.org/frameworks/plasma-framework/-/blob/affcdeed45755321d7d41c83375729abf9018d5f/src/plasmaquick/dialog.cpp#L1483 and https://invent.kde.org/frameworks/plasma-framework/-/blob/affcdeed45755321d7d41c83375729abf9018d5f/src/plasmaquick/dialog.cpp#L1620. Both require that edges are resizable though. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 454635] Hovering over panel applet closes edit mode
https://bugs.kde.org/show_bug.cgi?id=454635 --- Comment #10 from Luca Carlon --- Is this confirmed to be related to https://invent.kde.org/frameworks/plasma-framework/-/merge_requests/500? -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 454635] Can't remove applet from panel on Wayland
https://bugs.kde.org/show_bug.cgi?id=454635 --- Comment #5 from Luca Carlon --- I rebuilt the entire Plasma from master and I still cannot reproduce. Could you provide a video of the issue? Maybe there is something different in our setup. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 454635] Can't remove applet from panel on Wayland
https://bugs.kde.org/show_bug.cgi?id=454635 Luca Carlon changed: What|Removed |Added CC||carlon.l...@gmail.com --- Comment #3 from Luca Carlon --- I have to say I'm not currently able to reproduce with my build. I'll try to rebuild the entire Plasma. -- You are receiving this mail because: You are watching all bug changes.
[frameworks-plasma] [Bug 332512] Plasma Popups aren't resizable, and if you force-resize them, they forget their size after the computer or plasmashell is restarted
https://bugs.kde.org/show_bug.cgi?id=332512 --- Comment #117 from Luca Carlon --- If someone wanted to test, this is the set of patches I proposed: * https://invent.kde.org/frameworks/kwindowsystem/-/merge_requests/55 * https://invent.kde.org/libraries/plasma-wayland-protocols/-/merge_requests/38 * https://invent.kde.org/frameworks/kwayland/-/merge_requests/60 * https://invent.kde.org/plasma/kwin/-/merge_requests/2305 * https://invent.kde.org/frameworks/plasma-framework/-/merge_requests/500 * https://invent.kde.org/plasma/plasma-workspace/-/merge_requests/1688 * https://invent.kde.org/plasma/plasma-desktop/-/merge_requests/924 -- You are receiving this mail because: You are watching all bug changes.
[frameworks-plasma] [Bug 332512] Plasma Popups aren't resizable, and if you force-resize them, they forget their size after the computer or plasmashell is restarted
https://bugs.kde.org/show_bug.cgi?id=332512 --- Comment #116 from Luca Carlon --- I opened another MR regarding this feature: https://invent.kde.org/plasma/kwin/-/merge_requests/2253. I won't be able to go on with this feature without feedback from some expert Plasma/kwin dev about these MRs. -- You are receiving this mail because: You are watching all bug changes.
[frameworks-plasma] [Bug 332512] Plasma Popups aren't resizable, and if you force-resize them, they forget their size after the computer or plasmashell is restarted
https://bugs.kde.org/show_bug.cgi?id=332512 --- Comment #115 from Luca Carlon --- I opened the first merge request: https://invent.kde.org/frameworks/plasma-framework/-/merge_requests/500. This one is just for the resize capability in the dialog implementation. If this is actually accepted, I'll other merge requests depending on this. -- You are receiving this mail because: You are watching all bug changes.
[frameworks-plasma] [Bug 332512] Plasma Popups aren't resizable, and if you force-resize them, they forget their size after the computer or plasmashell is restarted
https://bugs.kde.org/show_bug.cgi?id=332512 --- Comment #113 from Luca Carlon --- This is what I came up with: https://youtu.be/iSZcLh2yL1E works pretty much the same on both Wayland and X11. If someone wanted to provide some feedback, these are the two patches: https://invent.kde.org/lcarlon/plasma-framework/-/commits/resize_dialog/ https://invent.kde.org/lcarlon/plasma-workspace/-/tree/resize_systray_popups -- You are receiving this mail because: You are watching all bug changes.
[frameworks-plasma] [Bug 332512] Plasma Popups aren't resizable, and if you force-resize them, they forget their size after the computer or plasmashell is restarted
https://bugs.kde.org/show_bug.cgi?id=332512 --- Comment #112 from Luca Carlon --- Thank you Nate for your feedback. I'm currently stuck with the Wayland implementation. It seems that this technique works in Wayland when only Qt is involved, but does not seem to work when applied to the PlasmaQuick::Dialog. I suspect the reason is related to the fact that the popup in Wayland is somehow wrapped in a KWayland::Client::PlasmaShellSurface, so resize events should be redirected there instead. I'm digging into KWayland to find out how this works, but if someone had a hint, it would be helpful. -- You are receiving this mail because: You are watching all bug changes.
[frameworks-plasma] [Bug 332512] Plasma Popups aren't resizable, and if you force-resize them, they forget their size after the computer or plasmashell is restarted
https://bugs.kde.org/show_bug.cgi?id=332512 --- Comment #110 from Luca Carlon --- What about this second proposal Nate? It makes dialogs resizable as requested. https://invent.kde.org/lcarlon/plasma-framework/-/commit/492c2d8fb76d6b7f7e4cd4f4153ae05ee1c16c5c https://invent.kde.org/lcarlon/plasma-workspace/-/commit/5868a147599951bfeabc0abe3894aeaa6a17f561 It is just a draft. This patch does what Qt internally does. I tested it on X11, I'll need to work more for Wayland. X11 with applied scaling may be affected by a known Qt bug instead, still untested though. The implementation still needs applets to properly set the resizable flag (I wanted the change to be transparent for the rest of Plasma). The patch respects the max and min sizes if set by the applets, so those sizes must be changed in the applets. I only tested on the systray applet. -- You are receiving this mail because: You are watching all bug changes.
[frameworks-plasma] [Bug 332512] Plasma Popups aren't resizable, and if you force-resize them, they forget their size after the computer or plasmashell is restarted
https://bugs.kde.org/show_bug.cgi?id=332512 --- Comment #109 from Luca Carlon --- Is there someone actively working on this? -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 409040] Framerate decreases rapidly in Wayland on nVidia with proprietary drivers
https://bugs.kde.org/show_bug.cgi?id=409040 --- Comment #5 from Luca Carlon --- I recently saw a new update from nVidia (driver version 510.54) and I tried to remove the nVidia driver from the blacklist. I see no more performance related problems anymore on the same machine of the first report (and I can render offload some applications too). Also I'd say that the performance of animations in Plasma has increased to the point that it is hard to tell the difference from what I see on X11. I tried to enable the fps measurement in X11 but the framerate suddenly dropped (bug?), so I cannot provide precise measurements. On Wayland instead, moving wobbly windows around (in a multiscreen environment) makes the fps counter grow from 60 to 100. It was < 30 according to the report. I have to say I do not trust that fps counter much. I suspect it only counts the number of page swaps, but animations are slower than that. In any case, performance on Wayland seems to be pretty much similar to X11 now. In some cases it is even better maybe. I would probably close this report. Please note that my current software setup is clearly no more the one of the report. -- You are receiving this mail because: You are watching all bug changes.
[frameworks-plasma] [Bug 332512] Plasma Popups aren't resizable, and if you force-resize them, they forget their size after the computer or plasmashell is restarted
https://bugs.kde.org/show_bug.cgi?id=332512 Luca Carlon changed: What|Removed |Added CC||carlon.l...@gmail.com --- Comment #107 from Luca Carlon --- Sorry to disturb. I was looking into this. I still have to find a way to properly implement the resize as requested, but for the moment I though I could be happy with something like this: https://invent.kde.org/lcarlon/plasma-workspace/-/commit/4be549976a28957fb225d6a98df8b9f258e2292b. Works well for me. Not what was discussed, but can it be useful anyway? -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 409040] Framerate decreases rapidly in Wayland on nVidia with proprietary drivers
https://bugs.kde.org/show_bug.cgi?id=409040 --- Comment #1 from Luca Carlon --- I recently started to use Wayland on the same machine more seriously. It seems the problem mostly solved by blacklisting nvidia and nouveau drivers and switching the latency setup to "force smoothest animations". If this is somehow expected, maybe it should be somehow notified to the user? -- You are receiving this mail because: You are watching all bug changes.
[dolphin] [Bug 444652] New: Dolphin allows the user to move to the trash files that cannot actually be removed by him
https://bugs.kde.org/show_bug.cgi?id=444652 Bug ID: 444652 Summary: Dolphin allows the user to move to the trash files that cannot actually be removed by him Product: dolphin Version: 21.08.2 Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: dolphin-bugs-n...@kde.org Reporter: carlon.l...@gmail.com CC: kfm-de...@kde.org Target Milestone: --- SUMMARY In some cases dolphin allows to move to the trash bin directories that cannot be actually removed by the current user. STEPS TO REPRODUCE 1. Create a directory owned by the current user: mkdir somedir 2. Create a directory owned by root inside somedir: sudo mkdir rootdir 3. Create a file owned by root inside rootdir: sudo touch file 4. Move to the trash bin the entire directory "somedir". OBSERVED RESULT Dolphin allows the user to remove the directory, and places it in the trash bin. Once the user tries to empty the trash bin, an error is returned. This may be pretty bothering cause a user won't be able to empty the trash until he finds what must be moved out of the bin. EXPECTED RESULT IMO the user should not be allowed to send "somedir" to the trash bin, although "moving" is technically possible. Sending to the trash bin should be possible only when "removing" is actually allowed. The result is that a user won't be able to empty the trash bin anymore without fixing the problem manually, by restoring what is blocking the procedure. This does not seem very user-friendly. SOFTWARE/OS VERSIONS Linux/KDE Plasma: 5.14.10-1 (available in About System) KDE Plasma Version: 5.22.5 KDE Frameworks Version: 5.87.0 Qt Version: 5.15.2 -- You are receiving this mail because: You are watching all bug changes.
[kdenlive] [Bug 431376] Image sequence does not seem to properly handle images of different sizes
https://bugs.kde.org/show_bug.cgi?id=431376 --- Comment #5 from Luca Carlon --- Hello, yes, with that patch I can't reproduce the issue in melt or kdenlive. Hope it's fixed. Thanks for your help. -- You are receiving this mail because: You are watching all bug changes.
[kdenlive] [Bug 431376] Image sequence does not seem to properly handle images of different sizes
https://bugs.kde.org/show_bug.cgi?id=431376 --- Comment #2 from Luca Carlon --- Reported here: https://github.com/mltframework/mlt/issues/663. Thanks! -- You are receiving this mail because: You are watching all bug changes.
[kdenlive] [Bug 431376] New: Image sequence does not seem to properly handle images of different sizes
https://bugs.kde.org/show_bug.cgi?id=431376 Bug ID: 431376 Summary: Image sequence does not seem to properly handle images of different sizes Product: kdenlive Version: 20.12.0 Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: Video Display & Export Assignee: j...@kdenlive.org Reporter: carlon.l...@gmail.com Target Milestone: --- SUMMARY The slideshow produced by adding an image sequence seems to show images with the wrong size when transitioning from an image to the next one. Both in the preview and in the rendered video, when a new image appears, it seems to appear scaled to the size of the previous image. After some milliseconds, the new image is shown with its proper size. I'm attaching a couple of videos to show the result. STEPS TO REPRODUCE 1. Create a new project (HD 1080p 60fps, but I tried other setups). 2. Add an image sequence. 3. Select a sequence of images and ensure the sequence contains alternating images of different sizes. This is the set I used: https://app.box.com/s/df55s9ldew4sj4nyk6t9h7k7u96fjtuw. 4. I can see the issue both in the preview and in the rendered video, but not for all transitions. The issue did not seem to be entirely deterministic. OBSERVED RESULT Resulting video shows the selected sequence of images. In some cases, when transitioning from one image to the next, the following image is shown with a size similar to the previous one, resulting in distortion. After some milliseconds, the geometry is fixed. EXPECTED RESULT When transitioning from one image to the next, the next image should always be shown with its own geometry, without distortion. SOFTWARE/OS VERSIONS Linux/KDE Plasma: Linux Manjaro KDE Plasma Version: 5.20.4 KDE Frameworks Version: 5.77.0 Qt Version: 5.15.2 ADDITIONAL INFORMATION I followed the steps above and this is the result: * Video without dissolve transition: https://app.box.com/s/rcgtxwojmjxnleava475f7eehkogjagy * Video without any animation: https://app.box.com/s/uaqlftg0sb6xwhc7meiqdu8boi0l123z -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 425571] New: Panel is animated twice when shown
https://bugs.kde.org/show_bug.cgi?id=425571 Bug ID: 425571 Summary: Panel is animated twice when shown Product: plasmashell Version: 5.19.4 Platform: Manjaro OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: Panel Assignee: plasma-b...@kde.org Reporter: carlon.l...@gmail.com Target Milestone: 1.0 Created attachment 131029 --> https://bugs.kde.org/attachment.cgi?id=131029=edit Show the problem and how to reproduce. SUMMARY When system tray (panel) is set to auto hide, the animation showing it is played twice in some cases. I attach a video to show the issue. STEPS TO REPRODUCE 1. Move the cursor to the border of the screen to show the panel. 2. Leave the cursor on the border, do not move it during the animation. OBSERVED RESULT Show animation is played twice. EXPECTED RESULT Show animation should only be played once. SOFTWARE/OS VERSIONS Linux/KDE Plasma: Manjaro Linux (available in About System) KDE Plasma Version: 5.19.4 KDE Frameworks Version: 5.73.0 Qt Version: 5.15.0 ADDITIONAL INFORMATION I've seen this issue also in Kubuntu. Please note that I'm working on a highdpi display. Not sure if this also happens in a regular display. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 356446] plasmashell does not respect QT_DEVICE_PIXEL_RATIO on X
https://bugs.kde.org/show_bug.cgi?id=356446 --- Comment #49 from Luca Carlon --- Stupid question. "Depends on" is probably what I was looking for, sorry. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 356446] plasmashell does not respect QT_DEVICE_PIXEL_RATIO on X
https://bugs.kde.org/show_bug.cgi?id=356446 --- Comment #48 from Luca Carlon --- I wouldn't even use Plasma without PLASMA_USE_QT_SCALING=1. Is there an updated list with all the tasks blocking this? -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 406180] KWin 5.15.4+ hang regression on Nvidia Optimus
https://bugs.kde.org/show_bug.cgi?id=406180 --- Comment #130 from Luca Carlon --- No, the package is 5.12.4 patched. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 406180] KWin 5.15.4+ hang regression on Nvidia Optimus
https://bugs.kde.org/show_bug.cgi?id=406180 --- Comment #128 from Luca Carlon --- What system? -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 406180] KWin 5.15.4+ hang regression on Nvidia Optimus
https://bugs.kde.org/show_bug.cgi?id=406180 --- Comment #125 from Luca Carlon --- This is the deb package I use on Kubuntu 19.10: https://bugfreeblog.page.link/libqt5gui5_5124. This package should be enough. If anything goes wrong, just do: sudo apt-get install --reinstall libqt5gui5 to get the previous one back. If you prefer however not to rely on prebuilt packages, rebuilding is a matter of a few commands. You do not have to do anything to Plasma/kwin, there is no ABI change. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 406180] KWin 5.15.4+ hang regression on Nvidia Optimus
https://bugs.kde.org/show_bug.cgi?id=406180 --- Comment #123 from Luca Carlon --- @Paul I suggest you simply download the source package from Ubuntu repo, apply the patch to Qt and rebuild. Then install the new deb packages. Works perfectly fine for me. If you want, I have the packages I built. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 406180] KWin 5.15.4+ hang regression on Nvidia Optimus
https://bugs.kde.org/show_bug.cgi?id=406180 --- Comment #118 from Luca Carlon --- I updated to Kubuntu 19.10 and this bug broke my system again. Kubuntu 19.10 is based on: Plasma: 5.16.5 Qt: 5.12.4 This bug is reported as fixed in 5.16.2 and Qt 5.12.4. I checked git history and I don't see Erik's commit in Qt 5.12.4 branch: https://github.com/qt/qtbase/blob/5.12.4/src/plugins/platforms/xcb/gl_integrations/xcb_glx/qglxintegration.cpp. Qt 5.12.5 instead seems to include it: https://github.com/qt/qtbase/blob/5.12.5/src/plugins/platforms/xcb/gl_integrations/xcb_glx/qglxintegration.cpp. I applied Erik's patch to Qt again and problem seems fixed so far. Probably we just need to fix the field "Version Fixed In"? -- You are receiving this mail because: You are watching all bug changes.
[konversation] [Bug 400362] Add a note stating that identifying with nickserv may result in failures when auto-joining
https://bugs.kde.org/show_bug.cgi?id=400362 --- Comment #5 from Luca Carlon --- I suspected that. Thanks for explaining. What about my first proposal: adding a simple note explaining the situation to the user, maybe suggesting SASL? It took me hours to understand why that was happening to me and that a solution was one click away :-) -- You are receiving this mail because: You are watching all bug changes.
[ksysguard] [Bug 410902] Add per process power-related information in the process table
https://bugs.kde.org/show_bug.cgi?id=410902 --- Comment #7 from Luca Carlon --- It is not necessarily an issue, but that means I need to know how it works. The second instance of KSysGuard calls into the existing KAuth helper? Is it creating a new thread? This is something I need to know cause it means things must be thread-safe. I excepted two helper processes. If running an executable with suid bit is allowed, it would probably be a good option. I didn't do that cause some systems do not allow it, like Android, and also I think it is ignored with SELinux. But it would be better to design first and implement after, instead of implementing, redesigning and reimplementing. Are there other parts of Plasma using suid bit? Maybe KAuth itself? I don't think any of this is a showstopper to plugin integration, but the implementation may differ, and I can't therefore go on. I'll study what you provided. Thanks! -- You are receiving this mail because: You are watching all bug changes.
[ksysguard] [Bug 410902] Add per process power-related information in the process table
https://bugs.kde.org/show_bug.cgi?id=410902 --- Comment #5 from Luca Carlon --- It probably is. I'll read more carefully. Do you also happen to have an example? At the moment I'm more worried about the other portion of the implementation. Multiple instances of KSysGuard are allowed, but I see only one KAuth helper process. -- You are receiving this mail because: You are watching all bug changes.
[ksysguard] [Bug 410902] Add per process power-related information in the process table
https://bugs.kde.org/show_bug.cgi?id=410902 --- Comment #3 from Luca Carlon --- Hello, this is just a draft of the architecture of what I imagined, but I guess it is simpler to get comments/critics by providing what I did. I added a few notes about the build procedure in my main repo: https://github.com/carlonluca/libksysguard. Powertop includes a training phase of a few minutes (on battery) where values are simply hidden (I guess): I'm currently missing this phase and I just provide values even if those are not probably accurate during it. I've never built the code outside my env yet, so please let me know if you see something is not working in the build phase. -- You are receiving this mail because: You are watching all bug changes.
[ksysguard] [Bug 410902] Add per process power-related information in the process table
https://bugs.kde.org/show_bug.cgi?id=410902 --- Comment #2 from Luca Carlon --- At the moment I just have a draft. I can improve it a bit and share. I would like to have some feedback from the community about the key points before working more on this. Do you think relying on some fork of powertop would be a good approach? Are there licensing issues? Would you prefer to have a fork of powertop in the form of a shared library or do you prefer to integrate the code. Do you think linking to libksysguard is ok or do we want a daemon with a dbus interface instead? -- You are receiving this mail because: You are watching all bug changes.
[ksysguard] [Bug 410902] New: Add per process power-related information in the process table
https://bugs.kde.org/show_bug.cgi?id=410902 Bug ID: 410902 Summary: Add per process power-related information in the process table Product: ksysguard Version: unspecified Platform: Other OS: Linux Status: REPORTED Severity: wishlist Priority: NOR Component: general Assignee: ksysguard-b...@kde.org Reporter: carlon.l...@gmail.com Target Milestone: --- Created attachment 122116 --> https://bugs.kde.org/attachment.cgi?id=122116=edit KSysGuard including per-process power consumption. SUMMARY When working on battery-powered devices, it would be very useful to have info about power consumption related to each process (and maybe even application). Other OS like Mac OS and Android provide such a feature in some form. I think this is a feature that Plasma should include. Other energy-related info can be provided in the future, but for the moment I'd start with this one. IDEA For the first step, a new column in the process table that reports some kind of power requirement information for the process may be sufficient. An example is provided in the shot I attached. The concept may then be extended with more info/tools, charts, etc... if there is interest. TECHNICAL PROPOSAL My researches led me to a tool named Powertop (https://github.com/fenrus75/powertop), which seems to be able to provide an estimation in Watts of the power required by a process. The tool is a command line binary based on ncurses that provides a process table with energy-related information. Powertop is written by Intel and published under GPLv2 license. It is reported to work on Linux and Android. A possible approach would be to leverage the implementation contained in Powertop and display in KSysGuard. PROOF OF CONCEPT To test the feasibility of my idea I implemented a proof of concept (the attached shot results from it). I turned the Powertop executable into a shared library (libpowertop) used as a data provider. Powertop requires root privileges, so ksysguard uses libksysguard to get the process list, which in turn uses KAuth to transparently run a helper linking to libpowertop. The helper runs for the entire lifespan of the process list and provides data. The shot I uploaded comes from my draft. CONCLUSION I'd appreciate feedback about both the feature itself and about my technical proposal. There are clearly a few technical key points that would need in depth discussion. Thanks! -- You are receiving this mail because: You are watching all bug changes.
[konversation] [Bug 400362] Add a note stating that identifying with nickserv may result in failures when auto-joining
https://bugs.kde.org/show_bug.cgi?id=400362 --- Comment #2 from Luca Carlon --- I agree that the default method should not be one that is known to be unreliable. And does it make sense to keep an unreliable method? If it does, should we anyway put a note stating it is unreliable? -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 408748] Applications are not always opened when clicked
https://bugs.kde.org/show_bug.cgi?id=408748 --- Comment #17 from Luca Carlon --- It seems that the issue appeared in 0ecb135. This is my attempt to fix the issue: https://phabricator.kde.org/D22306. It seems to work so far in my environment: applications are properly opened when clicked, moving an icon to the favorite list does not close the dashboard and also clicking outside results in closing the dashboard. Unfortunately, the rationale behind that commit is not completely clear to me. In particular, this line https://phabricator.kde.org/source/plasma-desktop/browse/master/applets/kicker/package/contents/ui/ItemGridView.qml$433 is not completely clear to me. It seems my env has something peculiar, as no one else could reproduce. Maybe there is someone who can review my patch and let me know if it works? Thanks. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 408748] Applications are not always opened when clicked
https://bugs.kde.org/show_bug.cgi?id=408748 --- Comment #16 from Luca Carlon --- Someone who can suggest a way to debug this? I was able to build everything and log into a dev version of Plasma. I suppose it is difficult to use gdb in there. Can I read logs somehow from that QML file or from the component? -- You are receiving this mail because: You are watching all bug changes.
[neon] [Bug 409298] No desktop when trying to run the docker Neon image
https://bugs.kde.org/show_bug.cgi?id=409298 --- Comment #1 from Luca Carlon --- Created attachment 121219 --> https://bugs.kde.org/attachment.cgi?id=121219=edit Logs from the docker image. -- You are receiving this mail because: You are watching all bug changes.
[neon] [Bug 409298] New: No desktop when trying to run the docker Neon image
https://bugs.kde.org/show_bug.cgi?id=409298 Bug ID: 409298 Summary: No desktop when trying to run the docker Neon image Product: neon Version: unspecified Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: Docker Assignee: j...@jriddell.org Reporter: carlon.l...@gmail.com Target Milestone: --- I was used to develop in the past (probably last year) running a docker Neon image into a Xephyr window. Now I can't do this anymore as nothing is displayed in Xephyr except the mouse pointer. STEPS TO REPRODUCE Simply run the two commands reported here: https://github.com/KDE/docker-neon. 1. Xephyr -screen 1024x768 :1 & 2. docker run -v /tmp/.X11-unix:/tmp/.X11-unix kdeneon/plasma:unstable OBSERVED RESULT Xephyr only shows black with the mouse pointer inside (which is different from the one of the host). EXPECTED RESULT I should see the Plasma desktop. SOFTWARE/OS VERSIONS Linux/KDE Plasma: Kubuntu 19.04 KDE Plasma Version: 5.16.1 KDE Frameworks Version: 5.59.0 Qt Version: 5.12.2 ADDITIONAL INFORMATION I attached logs docker is printing to stdour/stderr. I see many errors, so it is difficult to understand for me which are relevant. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 408748] Applications are not always opened when clicked
https://bugs.kde.org/show_bug.cgi?id=408748 --- Comment #15 from Luca Carlon --- @Vlad yes, starting apps from command line works properly. The only thing not working properly is the "click event" in that view. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 409040] New: Framerate decreases rapidly in Wayland on nVidia with proprietary drivers
https://bugs.kde.org/show_bug.cgi?id=409040 Bug ID: 409040 Summary: Framerate decreases rapidly in Wayland on nVidia with proprietary drivers Product: kwin Version: 5.16.1 Platform: Kubuntu Packages OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: wayland-generic Assignee: kwin-bugs-n...@kde.org Reporter: carlon.l...@gmail.com Target Milestone: --- Performance of kwin on Wayland on nVidia GM107GLM [Quadro M1200 Mobile] (proprietary drivers) is much worse than performance on X11. Animations seem to have a lower framerate and seem to degrade more severely with the number of open applications. STEPS TO REPRODUCE It is very simple to notice. Just move around a window and you should see the difference. However this is a test I made to quantificate. 1. Enable some effects like wobbling windows and animations on minimize/maximize. 2. Enable the overlay with the framerate chart. 3. Open a window with many widgets, like System Settings -> Desktop Behavior -> Desktop Effects. 4. Move the window around, the window should deform and become semi-transparent. OBSERVED RESULT In X11, framerate is typically 60fps. While moving the window as reported above, the framerate remains properly at 60fps. Result is excellent. In Wayland, framerate quickly decreases and is around 30fps or lower while moving the window. Actually, I don't even need to move the window: just move the pointer over the window and framerate decreases. EXPECTED RESULT I'd expect Wayland to be no worse than X11, and of course not to halve the framerate. SOFTWARE/OS VERSIONS Linux/KDE Plasma: Kubuntu 19.04 KDE Plasma Version: 5.6.1 KDE Frameworks Version: 5.59.0 Qt Version: 5.12.2 ADDITIONAL INFORMATION I guess this is not related, but I had to patch both kwin and Qt because of this bug: https://bugs.kde.org/show_bug.cgi?id=406180. So my current setup includes those two patches. Also I had to set: export __GL_MaxFramesAllowed=1 export PLASMA_USE_QT_SCALING=1 because of other kwin bugs. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 408748] Applications are not always opened when clicked
https://bugs.kde.org/show_bug.cgi?id=408748 --- Comment #12 from Luca Carlon --- Tried Plasma on Wayland with nVidia: I could reproduce immediately. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 408748] Applications are not always opened when clicked
https://bugs.kde.org/show_bug.cgi?id=408748 --- Comment #10 from Luca Carlon --- Yes, proprietary drivers. I only use X11 as kwin with wayland on nVidia is not supported (probably added in 5.16 right?). -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 408748] Applications are not always opened when clicked
https://bugs.kde.org/show_bug.cgi?id=408748 --- Comment #8 from Luca Carlon --- I tried to simply disable nVidia and run on Intel HD only. No issue on Intel HD. The problem occurs only on nVidia. Unfortunately I tried to create a VM to rebuild plasma and run a session there but... believe it or not, virtualbox freezes the system when on nVidia... So, I don't exactly now how to help more on this. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 406180] KWin 5.15.4+ hang regression on Nvidia Optimus
https://bugs.kde.org/show_bug.cgi?id=406180 --- Comment #88 from Luca Carlon --- I applied the patches in the version posted here to kwin 5.16 and Qt 5.12: no issue even after many hours of uptime. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 408748] Applications are not always opened when clicked
https://bugs.kde.org/show_bug.cgi?id=408748 Luca Carlon changed: What|Removed |Added Platform|Other |Kubuntu Packages --- Comment #6 from Luca Carlon --- I'll try to bisect. Did you try on a HiDPI screen by any chance? -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 408748] Applications are not always opened when clicked
https://bugs.kde.org/show_bug.cgi?id=408748 --- Comment #4 from Luca Carlon --- It seems I cannot reproduce on the buttons "Apps & Docs" and "Widgets". -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 408748] Applications are not always opened when clicked
https://bugs.kde.org/show_bug.cgi?id=408748 --- Comment #3 from Luca Carlon --- I uploaded a shot of the application I'm talking about. Just to be sure I set the proper component in the report. I see the problem everywhere there is a square with something to click on. Even a widget. So I could reproduce in the "Favorites" section, in the "Recent applications" section, "Recent documents" and all the others I tested (I can't find the "history" tab you referred to). Unfortunately I cannot find a real deterministic pattern: may need 1 click, 2 clicks or more. Sometimes I simply gave up. But the "enter" key always works immediately. I'm a dev, can I help somehow? Any log I can enable? Can I start that from the command line somehow? If you want me to add a log somewhere and test I can probably do it if you give me some hints. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 408748] Applications are not always opened when clicked
https://bugs.kde.org/show_bug.cgi?id=408748 --- Comment #2 from Luca Carlon --- Created attachment 120953 --> https://bugs.kde.org/attachment.cgi?id=120953=edit Application screenshot -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 408748] Applications are not always opened when clicked
https://bugs.kde.org/show_bug.cgi?id=408748 Luca Carlon changed: What|Removed |Added Summary|Hard to open apps clicking |Applications are not always |on the icons|opened when clicked -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 408748] New: Hard to open apps clicking on the icons
https://bugs.kde.org/show_bug.cgi?id=408748 Bug ID: 408748 Summary: Hard to open apps clicking on the icons Product: plasmashell Version: 5.16.0 Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: Application Launcher (Kickoff) Assignee: k...@davidedmundson.co.uk Reporter: carlon.l...@gmail.com CC: plasma-b...@kde.org Target Milestone: 1.0 Since Plasma version 5.16 it is very difficult to open apps. It seems that clicking on the icons does not always result in the app being opened. I have to click multiple times, and even in that case, sometimes the application is not opened. The only reliable way to open is to hover on the application with the pointer and to press enter. STEPS TO REPRODUCE 1. Click on an icon, once or multiple times. OBSERVED RESULT Application not always opened. EXPECTED RESULT Application used to open after the first click. Now it opens only sometimes. Other times, multiple clicks are needed. Other times, no way to open it. I need to press enter. SOFTWARE/OS VERSIONS Linux/KDE Plasma: Kubuntu 19.04 KDE Plasma Version: 5.16.0 KDE Frameworks Version: 5.58.0 Qt Version: 5.12.2 ADDITIONAL INFORMATION Used to work in previous versions. I think I had 5.15.4 before. -- You are receiving this mail because: You are watching all bug changes.
[Discover] [Bug 390630] Add filtering feature (only KDE apps, only GNOME apps, only phone apps, not phone apps, etc)
https://bugs.kde.org/show_bug.cgi?id=390630 Luca Carlon changed: What|Removed |Added CC||carlon.l...@gmail.com -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 406180] KWin 5.15.4+ hang regression on Nvidia Optimus
https://bugs.kde.org/show_bug.cgi?id=406180 --- Comment #80 from Luca Carlon --- I see the Qt patch was merged to the 5.12 branch. Hope to see it in 5.12.4. But what about kwin? When is the patch release planned? -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 406180] KWin 5.15.4+ hang regression on Nvidia Optimus
https://bugs.kde.org/show_bug.cgi?id=406180 --- Comment #75 from Luca Carlon --- Is there anyone in charge of publishing the changes? Was the Qt patch submitted? I sent patches to Qt in the past if you need it. I'd consider this a high priority bug as it makes the system unusable in some configurations. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 406180] KWin 5.15.4+ hang regression on Nvidia Optimus
https://bugs.kde.org/show_bug.cgi?id=406180 --- Comment #65 from Luca Carlon --- What distro? -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 406180] KWin 5.15.4+ hang regression on Nvidia Optimus
https://bugs.kde.org/show_bug.cgi?id=406180 --- Comment #61 from Luca Carlon --- No, this was only happening on nVidia for me too. But the patches seemed not to apply only to that case. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 406180] KWin 5.15.4+ hang regression on Nvidia Optimus
https://bugs.kde.org/show_bug.cgi?id=406180 --- Comment #59 from Luca Carlon --- I tested the patches on Intel HD and everything seems to work as usual. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 406180] KWin 5.15.4+ hang regression on Nvidia Optimus
https://bugs.kde.org/show_bug.cgi?id=406180 --- Comment #57 from Luca Carlon --- You just have to apply the two patches provided in the report. One to qtcore and the other to kwin. This fixed the issue for me. I hope someone could work on the release or describe what is blocking. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 406180] KWin 5.15.4+ hang regression on Nvidia Optimus
https://bugs.kde.org/show_bug.cgi?id=406180 --- Comment #53 from Luca Carlon --- Were the patches committed? Do these patches affect also other platforms/drivers? Do you need other tests? These patches seem to be pretty relevant if someone wants to work on nVidia on many machines. Many thanks to the author(s) of the patches btw, no issue for me so far. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 406180] KWin 5.15.4+ hang regression on Nvidia Optimus
https://bugs.kde.org/show_bug.cgi?id=406180 --- Comment #39 from Luca Carlon --- Tried hard to reproduce but I couldn't. These two patches seem to fix properly for me on nVidia. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 406180] KWin 5.15.4+ hang regression on Nvidia Optimus
https://bugs.kde.org/show_bug.cgi?id=406180 --- Comment #36 from Luca Carlon --- Erik, I'm not sure what you mean by "the first time the switcher is displayed". Do you mean "the first time the switcher is displayed after kwin process started"? If this is what you mean then it seems yes, the first time I open the switcher, it is typically displayed. The following times, it is typically NOT displayed, unless I force a refresh somehow by moving the mouse pointer. If I move the pointer, the proper screen is displayed on the screen immediately, including the switcher. Do you have a working patch to Qt to fix this issue properly? I can try to test if you want. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 406180] KWin 5.15.4 hang regression on Nvidia Optimus
https://bugs.kde.org/show_bug.cgi?id=406180 --- Comment #30 from Luca Carlon --- Unfortunately not working properly for me on 5.15.4 and 5.15.5. When I switch the window, sometimes it works as expected, sometimes (more than 50% of the times) nothing happens and nothing changes on the screen (until the timeout occurs). However I can see an improvement with this patch: if I move the mouse pointer while the screen is stuck, the entire screen is refreshed immediately, displaying the scene in the proper state. If I keep moving the pointer with one hand and switching with the other, it seems to work properly. It seems like moving the pointer is forcing the refresh of the screen, which wasn't happening before. As a consequence, I couldn't reproduce the issue moving the window around. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 406180] KWin 5.15.4 hang regression on Nvidia Optimus
https://bugs.kde.org/show_bug.cgi?id=406180 --- Comment #27 from Luca Carlon --- I tried to revert 22a441e071515e9c630f3bdac743c678052f88be for 5.15.4. The system is working almost perfectly. However, if you try hard enough, the issue still appears. Before reverting, moving a window for a couple of seconds, resulted in kwin hanging. Opening the switcher once, resulted in a hang. After reverting, it is unlikely to reproduce the issue while working regularly. But if you insist moving a window or opening the switcher for a minute, you can still reproduce. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 406180] KWin 5.15.4 hang regression on Nvidia Optimus
https://bugs.kde.org/show_bug.cgi?id=406180 --- Comment #23 from Luca Carlon --- I checked the backtrace using gdb and I got the same result reported by Pieter-Jan Briers. I, however, do not see one busy core as reported, CPU is reported 99% idle. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 406180] KWin 5.15.4 hang regression on Nvidia Optimus
https://bugs.kde.org/show_bug.cgi?id=406180 Luca Carlon changed: What|Removed |Added CC||carlon.l...@gmail.com --- Comment #22 from Luca Carlon --- Hello, I'm also affected by this issue. It is so severe that the system was hardly usable. I just noticed one thing: I suspect the issue appears for me only when drm is enabled with nvidia-drm.modeset=1. By default this was not set in Kubuntu 18.10 and 19.04 (may explain why Peter Eszlari could not reproduce?). Unfortunately drm is the only way I found to prevent horizontal tearing. No idea if this info is already known or of any help to you. -- You are receiving this mail because: You are watching all bug changes.
[dolphin] [Bug 175051] mount .iso option in context menu
https://bugs.kde.org/show_bug.cgi?id=175051 --- Comment #24 from Luca Carlon --- I'm not an experienced KDE dev and I cannot guarantee I can provide patches shortly. I just started to look into the projects I need to patch, haven't written anything yet. If you want to take over there is no problem for me. -- You are receiving this mail because: You are watching all bug changes.
[dolphin] [Bug 175051] mount .iso option in context menu
https://bugs.kde.org/show_bug.cgi?id=175051 --- Comment #21 from Luca Carlon --- What about using fuseiso as suggested, and make dolphin also list fuse mounts? I may try to propose a patch if there is nothing against it. -- You are receiving this mail because: You are watching all bug changes.
[dolphin] [Bug 175051] mount .iso option in context menu
https://bugs.kde.org/show_bug.cgi?id=175051 --- Comment #20 from Luca Carlon --- I had a look at smb4k: what about using KAuth? -- You are receiving this mail because: You are watching all bug changes.
[krdc] [Bug 406080] New: Custom connection parameters in connection dialog
https://bugs.kde.org/show_bug.cgi?id=406080 Bug ID: 406080 Summary: Custom connection parameters in connection dialog Product: krdc Version: unspecified Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: VNC Assignee: uwol...@kde.org Reporter: carlon.l...@gmail.com Target Milestone: --- SUMMARY It seems that VNC connections in KRDC can be established by choosing one out of three types of connections: high, medium and low. This results in a connection defined by a predefined combination of color depth, encoding, compression level and quality. In some cases, however, I need to tweak the params more precisely. For instance, when connecting to embedded boards, I would like to use 8-bit depth with hextile, as CPU cannot handle stronger algorithms and screen changes entirely. Connection type "low", instead, seems to ask copyrect with higher priority. Is this correct? Why not providing a fourth mode which is "custom", and let the user select the params manually? Something like this: http://www.uvnc.com/img/vieweroptions.png. Params I consider useful are: encoding, color depth, compression and quality. Would a patch like this be useful? EXPECTED RESULT User can select a predefined configuration or set custom params. libvncserver may then change the setup according to what the server supports. -- You are receiving this mail because: You are watching all bug changes.
[konsole] [Bug 180770] Provide a quadkonsole like interface
https://bugs.kde.org/show_bug.cgi?id=180770 --- Comment #26 from Luca Carlon --- I'll stop working on this then. Thanks for letting me know. -- You are receiving this mail because: You are watching all bug changes.
