[kwin] [Bug 483698] choppy framerate in X11 after upgrade to Plasma 6
https://bugs.kde.org/show_bug.cgi?id=483698 --- Comment #4 from S. Christian Collins --- (In reply to Zamundaaa from comment #3) > Please attach the output of > > glxinfo | grep timer_query GL_ARB_texture_view, GL_ARB_timer_query, GL_ARB_transform_feedback2, GL_EXT_texture_swizzle, GL_EXT_timer_query, GL_EXT_transform_feedback, GL_ARB_texture_swizzle, GL_ARB_texture_view, GL_ARB_timer_query, GL_EXT_texture_snorm, GL_EXT_texture_swizzle, GL_EXT_timer_query, GL_EXT_discard_framebuffer, GL_EXT_disjoint_timer_query, -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 487912] plasma X11 session is not restored after logout/login
https://bugs.kde.org/show_bug.cgi?id=487912 --- Comment #25 from S. Umar --- Fedora 40 included these patches in a new version. However, it seems to break the logout from KDE plasma. When I select logout (on multiple computers) I get a black screen with the mouse cursor showing only. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 488022] Multiple instances of gkrellm upon reboot or logout/login
https://bugs.kde.org/show_bug.cgi?id=488022 --- Comment #4 from S. Umar --- The logout works with Plasma Wayland. The problem seems to be with Plasma(X1). However, I can't use Wayland because some apps are very jittery, like chrome and linreoffice. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 60894] Periodic auto-saving of session state so state isn't lost if there's a crash or power loss
https://bugs.kde.org/show_bug.cgi?id=60894 Eric S changed: What|Removed |Added CC||subscri...@blackbrook.org --- Comment #18 from Eric S --- Woah thus bug is old! Is it really so hard to have a timer task run that does the equivalent of the manual save session button? Is there a command line way to trigger that function that I could add to a cron job? If not, could a command line way to activate it be added as a bit of a stopgap for this issue? -- You are receiving this mail because: You are watching all bug changes.
[kate] [Bug 488077] New: quotes implicitly in "automatically close brackets" feature
https://bugs.kde.org/show_bug.cgi?id=488077
Bug ID: 488077
Summary: quotes implicitly in "automatically close brackets"
feature
Classification: Applications
Product: kate
Version: 24.02.2
Platform: openSUSE
OS: Linux
Status: REPORTED
Severity: normal
Priority: NOR
Component: kwrite
Assignee: kwrite-bugs-n...@kde.org
Reporter: subscri...@blackbrook.org
Target Milestone: ---
SUMMARY
My "Enclosing characters" field in my Settings->Editing Options->General is set
to
<>(){}[]
But checking the box above it for "Automatically close brackets when opening
bracket is typed" causes the editor to automatically close double (") and
single (') quotes. There are 3 problems with this:
1) these characters are not listing in the "Enclosing characters" field
2) the wording for the checkbox. These characters are not "brackets"
3) Autoclosing quotes should not be a default, nevermind a hidden default. It
is counterproductive and annoying whenever you need to add quotes to existing
text, write an appostrophe etc, which for me is OFTEN.
STEPS TO REPRODUCE
1. Do not have " or ' in the "Enclosing characters" field
2. Check the box for "Automatically close brackets when opening bracket is
typed"
3. Type a " and observe how it is automatically closed.
4. Uncheck the box for "Automatically close brackets when opening bracket is
typed"
3. Type a " and observe how it is no longer automatically closed.
OBSERVED RESULT
" and ' are automatically closed or not according to the "Automatically close
brackets when opening bracket is typed" checkbox even if not in the "Enclosing
characters" field
EXPECTED RESULT
" and ' are automatically closed only when the "Automatically close brackets
when opening bracket is typed" checkbox even and included in "Enclosing
characters" field
SOFTWARE/OS VERSIONS
Linux/KDE Plasma: openSUSE Tumbleweed
(available in About System)
KDE Plasma Version: 6.0.4
KDE Frameworks Version: 6.2.0
Qt Version: 6.7.0
--
You are receiving this mail because:
You are watching all bug changes.
[plasmashell] [Bug 488022] Multiple instances of gkrellm upon reboot or logout/login
https://bugs.kde.org/show_bug.cgi?id=488022 --- Comment #3 from S. Umar --- Also in, .local/share/plasmasessionrestore/plasmasessionrestorestaterc [0] appId=gnome-gkrellm.desktop [1] appId=gnome-gkrellm.desktop -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 488022] Multiple instances of gkrellm upon reboot or logout/login
https://bugs.kde.org/show_bug.cgi?id=488022 --- Comment #2 from S. Umar --- No, it is not. There is nothing in .config/autostart. Is there another place for autostart? I see it in .config/ksmserverrc as: [LegacySession: saved at previous logout] clientMachine1=localhost clientMachine2=localhost command1=gkrellm command2=gkrellm count=2 -- I also see multiple instances I (after logging in and out) in kwin_saved\ at\ previous\ logout_ resourceClass1=Gkrellm resourceClass2=Gkrellm resourceClass3=plasmashell resourceClass4=Gkrellm resourceClass5=gkrellm resourceClass6=plasmashell resourceName1=gkrellm resourceName2=gkrellm resourceName3=plasmashell resourceName4=gkrellm resourceName5=gkrellm resourceName6=plasmashell .. wmCommand1=gkrellm\s wmCommand2=gkrellm\s wmCommand3= wmCommand4=gkrellm\s wmCommand5=gkrellm\s wmCommand6= -- You are receiving this mail because: You are watching all bug changes.
[kolourpaint] [Bug 488036] New: can't re-dock the Colors toolbar
https://bugs.kde.org/show_bug.cgi?id=488036 Bug ID: 488036 Summary: can't re-dock the Colors toolbar Classification: Applications Product: kolourpaint Version: 22.12.3 Platform: Debian stable OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: kolourpaint-supp...@lists.sourceforge.net Reporter: ene...@gmail.com Target Milestone: --- Created attachment 170147 --> https://bugs.kde.org/attachment.cgi?id=170147=edit an image of Kolourpaint, open to a blank canvas, with the Color box undocked. SUMMARY I'm able to un-dock the Color box to have it as a separate window from the main one, but I cannot re-dock it anywhere in the Kolourpaint window. I also cannot return it to the main window by closing the window, or by resetting any thing in the settings. Getting rid of all user data does put it back in the default location but I cannot seem to put it back in any other way. I have tried this on both the Debian repo version and on the Flatpak version. This is functionality that works in other KDE programs, like Krita. STEPS TO REPRODUCE 1. Install and run Kolourpaint. 2. Undock the Color box from the main window by dragging it out of place. 3. Try to move the Color box around or close it and see if you can put it back? OBSERVED RESULT Nothing puts it back in the main window. EXPECTED RESULT It should be able to be returned to the main window. SOFTWARE/OS VERSIONS Linux: Debian 12 (bookworm) KDE Plasma Version: 5.27.5 KDE Frameworks Version: 5.103.0 Qt Version: 5.15.8 -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 488022] New: Multiple instances of gkrellm upon reboot or logout/login
https://bugs.kde.org/show_bug.cgi?id=488022 Bug ID: 488022 Summary: Multiple instances of gkrellm upon reboot or logout/login Classification: Plasma Product: plasmashell Version: 6.0.5 Platform: Fedora RPMs OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: Session Management Assignee: plasma-b...@kde.org Reporter: u...@compsci.cas.vanderbilt.edu CC: natalie_clar...@yahoo.de Target Milestone: 1.0 *** 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 I have gtk app gkrellm on my desktop. I just noticed that everytime I login/logout OR even after every reboot there is an extra session of gkrellm running. It just keeps growing. I have done a killall -HUP gkrelmm and tested again multiple times with the same result. Eventually they start consuming significant amount of CPU. PS: I am running plasma-X11. I have not tested with Wayland. STEPS TO REPRODUCE 1. start gkrellm on desktop 2. login/logout or reboot 3. ps -e |grep gkrellm OBSERVED RESULT multiple instances of gkrellm upon reboot or login/logout EXPECTED RESULT Single instance of gkrellm SOFTWARE/OS VERSIONS Windows: macOS: Linux/KDE Plasma: (available in About System) KDE Plasma Version: 6.0.5 KDE Frameworks Version: 6.2.0 (some 6.2.1 and 6.2.2) Qt Version: 6.7.1 ADDITIONAL INFORMATION -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 487912] plasma X11 session is not restored after logout/login
https://bugs.kde.org/show_bug.cgi?id=487912 --- Comment #23 from S. Umar --- No it did not. I will open a new case -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 487912] plasma X11 session is not restored after logout/login
https://bugs.kde.org/show_bug.cgi?id=487912 S. Umar changed: What|Removed |Added CC||u...@compsci.cas.vanderbilt ||.edu --- Comment #22 from S. Umar --- I have also noticed that gtk apps that are on the desktop (I use gkrellm) multiply after logout/login or reboot. I have gkrellm on the desktop and I noticed many copies of it running. I killed them all started one and tested again and they keep multiplying. I will test to see if this patch fixes that too. -- You are receiving this mail because: You are watching all bug changes.
[krdc] [Bug 482950] KRDC RDP Blue screen shows nothing
https://bugs.kde.org/show_bug.cgi?id=482950 --- Comment #23 from Joe S --- (In reply to Mykola Krachkovsky from comment #21) > If you use openSUSE Tubleweed, you can either > 1. Install older KRDC (krdc5 — 23.08.4) from this repo: > https://download.opensuse.org/repositories/home:/wolfi323:/branches:/KDE:/ > Frameworks5/openSUSE_Tumbleweed/ > Which could be installed simultaneously with KRDC based on KF6. > OR > 2. Install develompent version from > https://download.opensuse.org/repositories/KDE:/Unstable:/Applications/ > KDE_Unstable_Frameworks_openSUSE_Factory/ > But in my experience this version has problems with mouse input with scaling > or multiple screens (not sure) on wayland session at least. Thanks for providing those options. I missed getting krdc 23.* version from the TW history repos before it was gone and was not aware of those. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 484875] On X11, after locking screen and turning off monitor, panels are occasionally placed in the wrong position
https://bugs.kde.org/show_bug.cgi?id=484875 S Rider changed: What|Removed |Added CC||romma...@gmail.com --- Comment #12 from S Rider --- I am reporting that I also am having the same issue on Manjaro, KDE 6.0.5. I can consistently reproduce the issue by simply turning off my monitor for a moment (no need to lock), turning the monitor back on, and then the very next minimize to desktop activity will pop the panel to the top of the screen. I had been logging off and back on to resolve the issue, but also found that going into edit mode, changing the position to top (which has no effect) and then back to bottom, will get the panel back to the bottom of the screen. It seems to be related to the transition between the "floating" panel and the "anchored" panel (not sure of the actual terms). When the monitor is turned off it seems to change the next panel "floating to anchored" transition to pop to the top of the screen. -- You are receiving this mail because: You are watching all bug changes.
[krdc] [Bug 482950] KRDC RDP Blue screen shows nothing
https://bugs.kde.org/show_bug.cgi?id=482950 --- Comment #20 from Joe S --- (In reply to Tilman Vogel from comment #17) > Broken on openSUSE Tumbleweed 20240524. > Thanks to https://bugs.kde.org/show_bug.cgi?id=482950#c10 for the workaround! Some additional details using other linux distros. In all cases I am attempting to connect to the TW 20240524 test machine from the other test machine. Using a Debian 12 ( BookWorm ) test machine which is using plasma 5.27.5 and krdc 22.12.3 to the TW test machine running TW 20240524 WORKS and the desktop is displayed. Using a Debian SID ( Trixie ) test machine which is using plasma 5.27.10 and krdc 23.08.3 to the TW test machine running TW 20240524 WORKS and the desktop is displayed. After updating Debian SID test machine to latest version which is using plasma 5.27.11 and krdc 23.08.3 I retested to the TW test machine running TW 20240524 WORKS and the desktop is displayed. Using a EndeavourOS test machine which is using plasma 6.0.5 and krdc 24.05.0 to the TW test machine running TW 20240524 FAILS and just displays the BLUE screen but displayed the following messages KRDC: Starting RDP session [12:45:38:623] [1674:1674] [INFO][com.freerdp.gdi] - Local framebuffer format PIXEL_FORMAT_RGBA32 [12:45:38:623] [1674:1674] [INFO][com.freerdp.gdi] - Remote framebuffer format PIXEL_FORMAT_BGRA32 [12:45:38:625] [1674:1674] [INFO][com.freerdp.channels.rdpsnd.client] - [static] Loaded pulse backend for rdpsnd [12:45:38:625] [1674:1674] [INFO][com.freerdp.channels.drdynvc.client] - Loading Dynamic Virtual Channel rdpsnd [12:45:38:625] [1674:1674] [INFO][com.freerdp.channels.drdynvc.client] - Loading Dynamic Virtual Channel audin [12:45:38:626] [1674:1674] [INFO][com.freerdp.channels.audin.client] - Loaded pulse backend for audin [12:45:38:626] [1674:1674] [INFO][com.freerdp.channels.drdynvc.client] - Loading Dynamic Virtual Channel rdpgfx Using a Manjaro test machine which is using plasma 6.0.5 and krdc 24.0.5.0 to the TW test machine running TW 20240524 FAILS and coredumps Using a openSUSE MicroOS KDE test machine which is using plasma 6.0.4 and krdc 24.02.2 to the TW test machine running TW 20240524 FAILS and coredumps. Using a Ubuntu 23.10 test machine which is using plasma 5.27.8 and krdc 23.08.1 to the TW test machine running TW 20240524 WORKS and the desktop is displayed. Using a Windows 11 test machine and the Microsoft Remote Desktop client to the TW test machine running TW 20240524 WORKS and the desktop is displayed. So in summary, these tests show that The problem is occurs with other Linux distros that are using plasma 6 and krdc 24.* The problem does NOT occur with other Linux distros that are still using plasma 5 and krdc 23.* Even the Windows 11 RDP client WORKS I'm not sure what other information the developers could possibly need to get this problem addressed. -- You are receiving this mail because: You are watching all bug changes.
[krdc] [Bug 482950] KRDC RDP Blue screen shows nothing
https://bugs.kde.org/show_bug.cgi?id=482950 Joe S changed: What|Removed |Added Status|REPORTED|CONFIRMED Ever confirmed|0 |1 --- Comment #19 from Joe S --- (In reply to Tilman Vogel from comment #17) > Broken on openSUSE Tumbleweed 20240524. > Thanks to https://bugs.kde.org/show_bug.cgi?id=482950#c10 for the workaround! Some additional details using other linux distros. In all cases I am attempting to connect to the TW 20240524 test machine from the other test machine. Using a Debian 12 ( BookWorm ) test machine which is using plasma 5.27.5 and krdc 22.12.3 to the TW test machine running TW 20240524 WORKS and the desktop is displayed. Using a Debian SID ( Trixie ) test machine which is using plasma 5.27.10 and krdc 23.08.3 to the TW test machine running TW 20240524 WORKS and the desktop is displayed. After updating Debian SID test machine to latest version which is using plasma 5.27.11 and krdc 23.08.3 I retested to the TW test machine running TW 20240524 WORKS and the desktop is displayed. Using a EndeavourOS test machine which is using plasma 6.0.5 and krdc 24.05.0 to the TW test machine running TW 20240524 FAILS and just displays the BLUE screen but displayed the following messages KRDC: Starting RDP session [12:45:38:623] [1674:1674] [INFO][com.freerdp.gdi] - Local framebuffer format PIXEL_FORMAT_RGBA32 [12:45:38:623] [1674:1674] [INFO][com.freerdp.gdi] - Remote framebuffer format PIXEL_FORMAT_BGRA32 [12:45:38:625] [1674:1674] [INFO][com.freerdp.channels.rdpsnd.client] - [static] Loaded pulse backend for rdpsnd [12:45:38:625] [1674:1674] [INFO][com.freerdp.channels.drdynvc.client] - Loading Dynamic Virtual Channel rdpsnd [12:45:38:625] [1674:1674] [INFO][com.freerdp.channels.drdynvc.client] - Loading Dynamic Virtual Channel audin [12:45:38:626] [1674:1674] [INFO][com.freerdp.channels.audin.client] - Loaded pulse backend for audin [12:45:38:626] [1674:1674] [INFO][com.freerdp.channels.drdynvc.client] - Loading Dynamic Virtual Channel rdpgfx Using a Manjaro test machine which is using plasma 6.0.5 and krdc 24.0.5.0 to the TW test machine running TW 20240524 FAILS and coredumps Using a openSUSE MicroOS KDE test machine which is using plasma 6.0.4 and krdc 24.02.2 to the TW test machine running TW 20240524 FAILS and coredumps. Using a Ubuntu 23.10 test machine which is using plasma 5.27.8 and krdc 23.08.1 to the TW test machine running TW 20240524 WORKS and the desktop is displayed. Using a Windows 11 test machine and the Microsoft Remote Desktop client to the TW test machine running TW 20240524 WORKS and the desktop is displayed. So in summary, these tests show that The problem is occurs with other Linux distros that are using plasma 6 and krdc 24.* The problem does NOT occur with other Linux distros that are still using plasma 5 and krdc 23.* Even the Windows 11 RDP client WORKS I'm not sure what other information the developers could possibly need to get this problem addressed. -- You are receiving this mail because: You are watching all bug changes.
[krdc] [Bug 482950] KRDC RDP Blue screen shows nothing
https://bugs.kde.org/show_bug.cgi?id=482950 --- Comment #18 from Joe S --- (In reply to Tilman Vogel from comment #17) > Broken on openSUSE Tumbleweed 20240524. > Thanks to https://bugs.kde.org/show_bug.cgi?id=482950#c10 for the workaround! Doesn't work for me on TW 20240430 using Accelleration "Disable All Accelleration". Here's the messages for krdc kf.coreaddons: The plugin "/usr/lib64/qt6/plugins/krdc/libkrdc_rdpplugin.so" explicitly states an Id in the embedded metadata, which is different from the one derived from the filename The Id field from the KPlugin object in the metadata should be removed kf.coreaddons: The plugin "/usr/lib64/qt6/plugins/krdc/libkrdc_testplugin.so" explicitly states an Id in the embedded metadata, which is different from the one derived from the filename The Id field from the KPlugin object in the metadata should be removed kf.coreaddons: The plugin "/usr/lib64/qt6/plugins/krdc/libkrdc_vncplugin.so" explicitly states an Id in the embedded metadata, which is different from the one derived from the filename The Id field from the KPlugin object in the metadata should be removed qt.core.qobject.connect: QObject::connect: No such signal KBookmarkManager::changed(QString,QString) KRDC: Starting RDP session [10:35:56:292] [18533:18533] [INFO][com.freerdp.gdi] - Local framebuffer format PIXEL_FORMAT_RGBA32 [10:35:56:292] [18533:18533] [INFO][com.freerdp.gdi] - Remote framebuffer format PIXEL_FORMAT_BGR24 [10:35:56:308] [18533:18533] [INFO][com.freerdp.channels.rdpsnd.client] - [static] Loaded pulse backend for rdpsnd [10:35:56:309] [18533:18533] [INFO][com.freerdp.channels.drdynvc.client] - Loading Dynamic Virtual Channel rdpsnd [10:35:56:309] [18533:18533] [INFO][com.freerdp.channels.drdynvc.client] - Loading Dynamic Virtual Channel audin [10:35:56:318] [18533:18533] [INFO][com.freerdp.channels.audin.client] - Loaded pulse backend for audin [10:35:58:532] [18533:18613] [ERROR][com.freerdp.core.update] - UPDATE_TYPE Bitmap [1] failed [10:35:58:532] [18533:18613] [ERROR][com.freerdp.core.rdp] - DATA_PDU_TYPE_UPDATE - update_recv() failed [10:35:58:532] [18533:18613] [ERROR][com.freerdp.core.transport] - transport_check_fds: transport->ReceiveCallback() - -1 [10:35:58:532] [18533:18613] [ERROR][com.freerdp.core] - freerdp_check_fds() failed - 0 [10:36:00:951] [18533:18533] [ERROR][com.freerdp.core] - freerdp_abort_connect:freerdp_set_last_error_ex ERRCONNECT_CONNECT_CANCELLED [0x0002000B] And then I'm disconnected. Doesn't work for me on TW 20240430 using Accelleration Force RemoteFX. Here's the messages for krdc kf.coreaddons: The plugin "/usr/lib64/qt6/plugins/krdc/libkrdc_rdpplugin.so" explicitly states an Id in the embedded metadata, which is different from the one derived from the filename The Id field from the KPlugin object in the metadata should be removed kf.coreaddons: The plugin "/usr/lib64/qt6/plugins/krdc/libkrdc_testplugin.so" explicitly states an Id in the embedded metadata, which is different from the one derived from the filename The Id field from the KPlugin object in the metadata should be removed kf.coreaddons: The plugin "/usr/lib64/qt6/plugins/krdc/libkrdc_vncplugin.so" explicitly states an Id in the embedded metadata, which is different from the one derived from the filename The Id field from the KPlugin object in the metadata should be removed qt.core.qobject.connect: QObject::connect: No such signal KBookmarkManager::changed(QString,QString) KRDC: Starting RDP session [10:38:17:156] [18740:18740] [INFO][com.freerdp.gdi] - Local framebuffer format PIXEL_FORMAT_RGBA32 [10:38:17:156] [18740:18740] [INFO][com.freerdp.gdi] - Remote framebuffer format PIXEL_FORMAT_BGRA32 [10:38:17:175] [18740:18740] [INFO][com.freerdp.channels.rdpsnd.client] - [static] Loaded pulse backend for rdpsnd [10:38:17:176] [18740:18740] [INFO][com.freerdp.channels.drdynvc.client] - Loading Dynamic Virtual Channel rdpsnd [10:38:17:176] [18740:18740] [INFO][com.freerdp.channels.drdynvc.client] - Loading Dynamic Virtual Channel audin [10:38:17:180] [18740:18740] [INFO][com.freerdp.channels.audin.client] - Loaded pulse backend for audin [10:38:19:330] [18740:18817] [WARN][com.freerdp.channels.rdpdr.client] - Checking ExtendedPDU::RDPDR_USER_LOGGEDON_PDU, client supported, server not found and then it hangs on the Blue Screen. Whereas "xfreerdp -u -v --dynamic-resolution" works fine and displays the desktop. NOTE: I have been trying to resolve these issues for almost 3 MONTHS now. They started for me when TW switched to KDE Plasma 6. The messages above are from my main machine ( where I originally found the problem ) which is running TW 20240430 now, HOWEVER, months ago I setup 2 test machines with brand new TW installations and replicated the problem there on brand new installations completely eliminating any issue with my main machine. Over the last 3 months, I have updated those
[neon] [Bug 487452] Missing Icons in Breeze Light and Twilight.
https://bugs.kde.org/show_bug.cgi?id=487452 S. Christian Collins changed: What|Removed |Added CC||s_chriscoll...@hotmail.com -- You are receiving this mail because: You are watching all bug changes.
[neon] [Bug 470281] KRDC does not work under wayland because it misses wlfreerdp
https://bugs.kde.org/show_bug.cgi?id=470281 Malte S. Stretz changed: What|Removed |Added Status|REPORTED|CONFIRMED Ever confirmed|0 |1 --- Comment #3 from Malte S. Stretz --- @François thanks for the info but could you please file a separate bug for that issue? This one is about the Neon packaging which works once the (now obsolete) missing package is installed. -- You are receiving this mail because: You are watching all bug changes.
[policykit-kde-agent-1] [Bug 485407] polkit-kde-agent crashes with nullptr in PolicyKitListener::finishObtainPrivilege() when run in Hyprland
https://bugs.kde.org/show_bug.cgi?id=485407 --- Comment #21 from S. Christian Collins --- (In reply to Sin Jeong-hun from comment #20) > I think "Hyperland" is not related. I am using Plasma X11 (version 6.0.4), > and it happens, too. Took me hours to find out this is a bug, because I > thought it was a problem of polkit rules and tried modifying rules. Yeah, I experience this bug as described by the OP under KDE neon User Edition on my two native installs (my two VirtualBox installs are unaffected). I can only assume it's the same cause, but I guess I'll find out once 6.0.5 is released. -- You are receiving this mail because: You are watching all bug changes.
[kdesrc-build] [Bug 485564] Workspace build fails on Neon developer version when trying to build gpgme
https://bugs.kde.org/show_bug.cgi?id=485564 --- Comment #7 from Malte S. Stretz --- Hmmm... the posted commit added the dependency to kwallet. But I think it is required earlier in the build chain so if Nicolas' tool was run maybe it is still broken because it isn't pulled in early enough. Or due to the dependency ordering third-party/libgpg-error is built after third-party/gpgme since the former is no dep on the latter but on kwallet. IMO the cleanest solution would be to define the dep like I did in my workaround but that would probably require some change in Nicolas' tool. -- You are receiving this mail because: You are watching all bug changes.
[kdesrc-build] [Bug 485564] Workspace build fails on Neon developer version when trying to build gpgme
https://bugs.kde.org/show_bug.cgi?id=485564 --- Comment #6 from Malte S. Stretz --- This is my workaround: echo 'third-party/gpgme: third-party/libgpg-error' >> ~/.local/state/sysadmin-repo-metadata/dependencies/dependency-data-kf6-qt6 I think this shouldn't be required anymore but that tool from Nicolas Fella has to be run to update the dependencies from the CI data. Maybe that was done already; if it still doesn't work (I didn't check, my workaround works for me) I guess there is a bug in that tool. Since it is written in rust I didn't want to dive into that topic. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 485771] Desktop icons disappear after icon update (including the trash icon)
https://bugs.kde.org/show_bug.cgi?id=485771 David S changed: What|Removed |Added CC||d...@digitalmonkey.org --- Comment #10 from David S --- Thought I was going nuts when my trash icon disappeared after emptying... Confirmed here on two machines. One fresh install of Plasma 6 and another upgraded from 5 -- You are receiving this mail because: You are watching all bug changes.
[krdc] [Bug 482950] KRDC RDP Blue screen shows nothing
https://bugs.kde.org/show_bug.cgi?id=482950 --- Comment #15 from Joe S --- (In reply to Jesús Martínez Novo (Ciencia Al Poder) from comment #13) > I had to downgrade to krdc-23.08.4 to continue using it because of this same > problem. And some weeks ago I had to downgrade to freerdp-2.11.2 too, > because OpenSuSE Tumbleweed pushed a new version of freerdp which changes > several command line parameters, causing it to be incompatible with krdc 23 Where did you get krdc 23.08 or did you compile yourself ? -- You are receiving this mail because: You are watching all bug changes.
[krdc] [Bug 482950] KRDC RDP Blue screen shows nothing
https://bugs.kde.org/show_bug.cgi?id=482950 --- Comment #14 from Joe S --- (In reply to Jesús Martínez Novo (Ciencia Al Poder) from comment #13) > I had to downgrade to krdc-23.08.4 to continue using it because of this same > problem. And some weeks ago I had to downgrade to freerdp-2.11.2 too, > because OpenSuSE Tumbleweed pushed a new version of freerdp which changes > several command line parameters, causing it to be incompatible with krdc 23 Where did you get the older version of krdc or did you compile yourself ? -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 478556] Sometimes the stacking order is out of sync with Xorg
https://bugs.kde.org/show_bug.cgi?id=478556 S. Christian Collins changed: What|Removed |Added CC||s_chriscoll...@hotmail.com -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 485690] X11 and Wayland use different Window Class Names
https://bugs.kde.org/show_bug.cgi?id=485690 S. Christian Collins changed: What|Removed |Added CC||s_chriscoll...@hotmail.com -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 483503] Window rules: Force app to specific screen don't work with Wayland
https://bugs.kde.org/show_bug.cgi?id=483503 S. Christian Collins changed: What|Removed |Added CC||s_chriscoll...@hotmail.com -- You are receiving this mail because: You are watching all bug changes.
[krdc] [Bug 482950] KRDC RDP Blue screen shows nothing
https://bugs.kde.org/show_bug.cgi?id=482950 --- Comment #11 from Joe S --- This problem just seems to get worse with each update. I have replicated it on a Tumbleweed vm running the latest build 20240507. My KDE Neon test environment updated to the last version just displays the blue screen that everyone else is complaining about. Those are NEW fresh installations that were updated to the latest builds so nothing in the current environment where the problem was originally found comes into play. Trying to connect using krdc 24.02.2 now just core dumps systemd-coredump[758]: [] Process 744 (krdc) of user 1000 dumped core. Stack trace of thread 744: #0 0x7fee3c013bf1 n/a (libkrdc_rdpplugin.so + 0xebf1) #1 0x7fee3c01948d n/a (libkrdc_rdpplugin.so + 0x1448d) #2 0x7fee43ddc245 _ZN15HostPreferences10showDialogEP7QWidget (libkrdccore.so.5 + 0xb245) #3 0x5619e047d93b n/a (krdc + 0x3293b) #4 0x5619e0467017 n/a (krdc + 0x1c017) #5 0x7fee4162a1f0 __libc_start_call_main (libc.so.6 + 0x2a1f0) #6 0x7fee4162a2b9 __libc_start_main@@GLIBC_2.34 (libc.so.6 + 0x2a2b9) #7 0x5619e04672d5 n/a (krdc + 0x1c2d5) Stack trace of thread 745: #0 0x7fee4170578f __poll (libc.so.6 + 0x10578f) #1 0x7fee405ce2ff n/a (libglib-2.0.so.0 + 0x5f2ff) #2 0x7fee405cea0c g_main_context_iteration (libglib-2.0.so.0 + 0x5fa0c) #3 0x7fee421c0a8c _ZN20QEventDispatcherGlib13processEventsE6QFlagsIN10QEventLoop17ProcessEve> #4 0x7fee41f9979b _ZN10QEventLoop4execE6QFlagsINS_17ProcessEventsFlagEE (libQt6Core.so.6 + 0> #5 0x7fee42074cb4 _ZN7QThread4execEv (libQt6Core.so.6 + 0x274cb4) #6 0x7fee41d7b6fa n/a (libQt6DBus.so.6 + 0x386fa) #7 0x7fee420ecea9 n/a (libQt6Core.so.6 + 0x2ecea9) #8 0x7fee41692bb2 start_thread (libc.so.6 + 0x92bb2) #9 0x7fee4171400c __clone3 (libc.so.6 + 0x11400c) Stack trace of thread 747: #0 0x7fee4168effe __futex_abstimed_wait_common (libc.so.6 + 0x8effe) #1 0x7fee41691d40 pthread_cond_wait@@GLIBC_2.3.2 (libc.so.6 + 0x91d40) #2 0x7fee35d10e5b n/a (iris_dri.so + 0x110e5b) #3 0x7fee35d06e67 n/a (iris_dri.so + 0x106e67) #4 0x7fee41692bb2 start_thread (libc.so.6 + 0x92bb2) #5 0x7fee4171400c __clone3 (libc.so.6 + 0x11400c) Stack trace of thread 746: #0 0x7fee4170578f __poll (libc.so.6 + 0x10578f) #1 0x7fee3f6ed8aa n/a (libxcb.so.1 + 0xe8aa) #2 0x7fee3f6ef41c xcb_wait_for_event (libxcb.so.1 + 0x1041c) #3 0x7fee3dd34e30 n/a (libQt6XcbQpa.so.6 + 0x5de30) #4 0x7fee420ecea9 n/a (libQt6Core.so.6 + 0x2ecea9) #5 0x7fee41692bb2 start_thread (libc.so.6 + 0x92bb2) #6 0x7fee4171400c __clone3 (libc.so.6 + 0x11400c) Stack trace of thread 748: #0 0x7fee4168effe __futex_abstimed_wait_common (libc.so.6 + 0x8effe) #1 0x7fee41691d40 pthread_cond_wait@@GLIBC_2.3.2 (libc.so.6 + 0x91d40) #2 0x7fee35d10e5b n/a (iris_dri.so + 0x110e5b) #3 0x7fee35d06e67 n/a (iris_dri.so + 0x106e67) #4 0x7fee41692bb2 start_thread (libc.so.6 + 0x92bb2) #5 0x7fee4171400c __clone3 (libc.so.6 + 0x
[frameworks-baloo] [Bug 478854] Baloo_file ASSERT failures when creating/renaming folders
https://bugs.kde.org/show_bug.cgi?id=478854 Malte S. Stretz changed: What|Removed |Added CC||m...@apache.org --- Comment #11 from Malte S. Stretz --- *** Bug 486671 has been marked as a duplicate of this bug. *** -- You are receiving this mail because: You are watching all bug changes.
[frameworks-baloo] [Bug 486671] baloo_file crashes with assertion: appFilePath points to nullptr
https://bugs.kde.org/show_bug.cgi?id=486671 Malte S. Stretz changed: What|Removed |Added Status|REPORTED|RESOLVED Resolution|--- |DUPLICATE --- Comment #1 from Malte S. Stretz --- *** This bug has been marked as a duplicate of bug 478854 *** -- You are receiving this mail because: You are watching all bug changes.
[frameworks-baloo] [Bug 486671] New: baloo_file crashes with assertion: appFilePath points to nullptr
https://bugs.kde.org/show_bug.cgi?id=486671
Bug ID: 486671
Summary: baloo_file crashes with assertion: appFilePath points
to nullptr
Classification: Frameworks and Libraries
Product: frameworks-baloo
Version: 6.0.0
Platform: Neon
OS: Linux
Status: REPORTED
Severity: normal
Priority: NOR
Component: Baloo File Daemon
Assignee: baloo-bugs-n...@kde.org
Reporter: m...@apache.org
Target Milestone: ---
SUMMARY
I discovered this crash in my journal when looking for something else.
Mai 06 13:05:56 localhost baloo_file_extractor[24749]: kf.idletime: Could not
find any system poller plugin
Mai 06 13:05:56 localhost baloo_file_extractor[24749]: qt.core.qobject.connect:
QObject::connect(KAbstractIdleTimePoller, KIdleTime): invalid nullptr parameter
Mai 06 13:05:56 localhost baloo_file_extractor[24749]: qt.core.qobject.connect:
QObject::connect(KAbstractIdleTimePoller, KIdleTime): invalid nullptr parameter
Mai 06 13:06:06 localhost baloo_file_extractor[24791]: kf.idletime: Could not
find any system poller plugin
Mai 06 13:06:06 localhost baloo_file_extractor[24791]: qt.core.qobject.connect:
QObject::connect(KAbstractIdleTimePoller, KIdleTime): invalid nullptr parameter
Mai 06 13:06:06 localhost baloo_file_extractor[24791]: qt.core.qobject.connect:
QObject::connect(KAbstractIdleTimePoller, KIdleTime): invalid nullptr parameter
Mai 06 13:06:27 localhost baloo_file_extractor[24800]: kf.idletime: Could not
find any system poller plugin
Mai 06 13:06:27 localhost baloo_file_extractor[24800]: qt.core.qobject.connect:
QObject::connect(KAbstractIdleTimePoller, KIdleTime): invalid nullptr parameter
Mai 06 13:06:27 localhost baloo_file_extractor[24800]: qt.core.qobject.connect:
QObject::connect(KAbstractIdleTimePoller, KIdleTime): invalid nullptr parameter
Mai 06 13:06:36 localhost baloo_file_extractor[24810]: kf.idletime: Could not
find any system poller plugin
Mai 06 13:06:36 localhost baloo_file_extractor[24810]: qt.core.qobject.connect:
QObject::connect(KAbstractIdleTimePoller, KIdleTime): invalid nullptr parameter
Mai 06 13:06:36 localhost baloo_file_extractor[24810]: qt.core.qobject.connect:
QObject::connect(KAbstractIdleTimePoller, KIdleTime): invalid nullptr parameter
Mai 06 13:06:54 localhost baloo_file_extractor[24846]: kf.idletime: Could not
find any system poller plugin
Mai 06 13:06:54 localhost baloo_file_extractor[24846]: qt.core.qobject.connect:
QObject::connect(KAbstractIdleTimePoller, KIdleTime): invalid nullptr parameter
Mai 06 13:06:54 localhost baloo_file_extractor[24846]: qt.core.qobject.connect:
QObject::connect(KAbstractIdleTimePoller, KIdleTime): invalid nullptr parameter
Mai 06 13:07:06 localhost baloo_file_extractor[24909]: kf.idletime: Could not
find any system poller plugin
Mai 06 13:07:06 localhost baloo_file_extractor[24909]: qt.core.qobject.connect:
QObject::connect(KAbstractIdleTimePoller, KIdleTime): invalid nullptr parameter
Mai 06 13:07:06 localhost baloo_file_extractor[24909]: qt.core.qobject.connect:
QObject::connect(KAbstractIdleTimePoller, KIdleTime): invalid nullptr parameter
Mai 06 13:07:17 localhost baloo_file[1266]: ASSERT: "to[to.size()-1] !=
QLatin1Char('/')" in file ./src/file/metadatamover.cpp, line 80
Mai 06 13:07:17 localhost baloo_file[1266]: KCrash: appFilePath points to
nullptr!
Mai 06 13:07:17 localhost baloo_file[1266]: KCrash: Application ''
crashing... crashRecursionCounter = 2
STEPS TO REPRODUCE
1. Unknown
OBSERVED RESULT
baloo_file crashed die to an assertion
EXPECTED RESULT
The unexpected situation should have handled without crashing the application.
SOFTWARE/OS VERSIONS
Linux/KDE Plasma: Neon
(available in About System)
Operating System: KDE neon 6.0
KDE Plasma Version: 6.0.4
KDE Frameworks Version: 6.1.0
Qt Version: 6.7.0
Kernel Version: 6.5.0-28-generic (64-bit)
Graphics Platform: Wayland
Processors: 4 × Intel® Core™ i5-6300U CPU @ 2.40GHz
Memory: 19,4 GiB of RAM
Graphics Processor: Mesa Intel® HD Graphics 520
Manufacturer: LENOVO
Product Name: 20F9CTO1WW
System Version: ThinkPad T460s
ADDITIONAL INFORMATION
DrKonqi didn't pop up and didn't pull the debug symbols automatically, I had to
ask gdb to do so:
GNU gdb (Ubuntu 12.1-0ubuntu1~22.04) 12.1
Copyright (C) 2022 Free Software Foundation, Inc.
License GPLv3+: GNU GPL version 3 or later
This is free software: you are free to change and redistribute it.
There is NO WARRANTY, to the extent permitted by law.
Type "show copying" and "show warranty" for details.
This GDB was configured as "x86_64-linux-gnu".
Type "show configuration" for configuration details.
For bug reporting instructions, please see:
[kdelibs] [Bug 325155] Docs and code for X-KDE-autostart-phase disagree.
https://bugs.kde.org/show_bug.cgi?id=325155 --- Comment #3 from Malte S. Stretz --- Just for the record: The default value and the reasoning is now properly documented in https://invent.kde.org/plasma/plasma-workspace/-/blob/master/ksmserver/README (which should probably be updated to the current state without kdeinit). -- You are receiving this mail because: You are watching all bug changes.
[neon] [Bug 434038] Please provide an updated version of Maliit that is usable
https://bugs.kde.org/show_bug.cgi?id=434038 S. Christian Collins changed: What|Removed |Added CC||s_chriscoll...@hotmail.com --- Comment #12 from S. Christian Collins --- On some systems, maalit-keyboard prevents Plasma X11 session from logging in (Wayland is unaffected). SDDM just freezes after entering the password. I have experienced this on two systems running KDE neon User Edition, but am unable to replicate in VirtualBox. Related bug report: https://bugs.launchpad.net/ubuntu/+source/maliit-keyboard/+bug/2039721 -- You are receiving this mail because: You are watching all bug changes.
[Discover] [Bug 486362] New: Discover crashes when opening
https://bugs.kde.org/show_bug.cgi?id=486362 Bug ID: 486362 Summary: Discover crashes when opening Classification: Applications Product: Discover Version: 5.27.5 Platform: Debian stable OS: Linux Status: REPORTED Keywords: drkonqi Severity: crash Priority: NOR Component: discover Assignee: plasma-b...@kde.org Reporter: v24909...@gmail.com CC: aleix...@kde.org Target Milestone: --- Application: plasma-discover (5.27.5) Qt Version: 5.15.8 Frameworks Version: 5.103.0 Operating System: Linux 6.1.0-20-amd64 x86_64 Windowing System: Wayland Distribution: Debian GNU/Linux 12 (bookworm) DrKonqi: 5.27.5 [KCrashBackend] -- Information about the crash: Hello! When I try to open "Discover" I get an application crash, the program quits unexpectedly, immediately after the initial loading has completed. This happens every time when I try to open it. The reporter is unsure if this crash is reproducible. -- Backtrace: Application: Центр программ Discover (plasma-discover), signal: Segmentation fault [KCrash Handler] #4 0x7f5b568e8a3d in ?? () from /lib/x86_64-linux-gnu/libQt5Core.so.5 #5 0x7f5b58b143b2 in ResultsStream::resourcesFound(QVector const&) () from /usr/lib/x86_64-linux-gnu/plasma-discover/libDiscoverCommon.so #6 0x7f5b467434d0 in ?? () from /usr/lib/x86_64-linux-gnu/qt5/plugins/discover/packagekit-backend.so #7 0x7f5b4673d588 in ?? () from /usr/lib/x86_64-linux-gnu/qt5/plugins/discover/packagekit-backend.so #8 0x7f5b568dd6f0 in QObject::event(QEvent*) () from /lib/x86_64-linux-gnu/libQt5Core.so.5 #9 0x7f5b58362fae in QApplicationPrivate::notify_helper(QObject*, QEvent*) () from /lib/x86_64-linux-gnu/libQt5Widgets.so.5 #10 0x7f5b568b16f8 in QCoreApplication::notifyInternal2(QObject*, QEvent*) () from /lib/x86_64-linux-gnu/libQt5Core.so.5 #11 0x7f5b568b4681 in QCoreApplicationPrivate::sendPostedEvents(QObject*, int, QThreadData*) () from /lib/x86_64-linux-gnu/libQt5Core.so.5 #12 0x7f5b5690a153 in ?? () from /lib/x86_64-linux-gnu/libQt5Core.so.5 #13 0x7f5b5511e7a9 in g_main_context_dispatch () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #14 0x7f5b5511ea38 in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #15 0x7f5b5511eacc in g_main_context_iteration () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #16 0x7f5b56909836 in QEventDispatcherGlib::processEvents(QFlags) () from /lib/x86_64-linux-gnu/libQt5Core.so.5 #17 0x7f5b568b017b in QEventLoop::exec(QFlags) () from /lib/x86_64-linux-gnu/libQt5Core.so.5 #18 0x7f5b568b82d6 in QCoreApplication::exec() () from /lib/x86_64-linux-gnu/libQt5Core.so.5 #19 0x5652932f52a7 in ?? () #20 0x7f5b5644624a in __libc_start_call_main (main=main@entry=0x5652932f49b0, argc=argc@entry=1, argv=argv@entry=0x7ffc5f880a58) at ../sysdeps/nptl/libc_start_call_main.h:58 #21 0x7f5b56446305 in __libc_start_main_impl (main=0x5652932f49b0, argc=1, argv=0x7ffc5f880a58, init=, fini=, rtld_fini=, stack_end=0x7ffc5f880a48) at ../csu/libc-start.c:360 #22 0x5652932f5811 in ?? () [Inferior 1 (process 16052) detached] Reported using DrKonqi -- You are receiving this mail because: You are watching all bug changes.
[trojita] [Bug 321369] Autoconfiguration via DNS: RFC6186 support
https://bugs.kde.org/show_bug.cgi?id=321369 Malte S. Stretz changed: What|Removed |Added See Also||https://bugs.kde.org/show_b ||ug.cgi?id=441193 CC||m...@apache.org -- You are receiving this mail because: You are watching all bug changes.
[kmail2] [Bug 441193] support auto configuration by SRV records only
https://bugs.kde.org/show_bug.cgi?id=441193 Malte S. Stretz changed: What|Removed |Added See Also||https://bugs.kde.org/show_b ||ug.cgi?id=321369 -- You are receiving this mail because: You are watching all bug changes.
[kmail2] [Bug 441193] support auto configuration by SRV records only
https://bugs.kde.org/show_bug.cgi?id=441193 Malte S. Stretz changed: What|Removed |Added URL||https://datatracker.ietf.or ||g/doc/html/rfc6186 Version|unspecified |6.0.2 Severity|normal |wishlist Keywords||usability -- You are receiving this mail because: You are watching all bug changes.
[kmail2] [Bug 441193] support auto configuration by SRV records only
https://bugs.kde.org/show_bug.cgi?id=441193 Malte S. Stretz changed: What|Removed |Added CC||m...@apache.org -- You are receiving this mail because: You are watching all bug changes.
[kmail2] [Bug 481763] Support for RFC 6186 for Mail Auto-Configuration
https://bugs.kde.org/show_bug.cgi?id=481763 Malte S. Stretz changed: What|Removed |Added Status|REPORTED|RESOLVED CC||m...@apache.org Resolution|--- |DUPLICATE --- Comment #1 from Malte S. Stretz --- *** This bug has been marked as a duplicate of bug 441193 *** -- You are receiving this mail because: You are watching all bug changes.
[kmail2] [Bug 441193] support auto configuration by SRV records only
https://bugs.kde.org/show_bug.cgi?id=441193 Malte S. Stretz changed: What|Removed |Added CC||zocker.netw...@gmail.com --- Comment #4 from Malte S. Stretz --- *** Bug 481763 has been marked as a duplicate of this bug. *** -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 485609] cpu usage at 100% when moving the mouse on wayland but not on X11
https://bugs.kde.org/show_bug.cgi?id=485609 S. Umar changed: What|Removed |Added CC||u...@compsci.cas.vanderbilt ||.edu --- Comment #1 from S. Umar --- I can confirm this on the new Fedora 40. kwin_wayland both on laptop Intel HD graphics and Workstaion with NVIDIA drivers use 2-3% of CPU when nothing is done. When one moves the mouse it goes up to 15-17%. Fedora 40 no longer provides the X11 option for Plasma 6 so we need a solution for this. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 483691] plasma panel unresponsive after connecting secondary monitor aligned to the left of primary (Wayland)
https://bugs.kde.org/show_bug.cgi?id=483691 --- Comment #12 from S. Christian Collins --- (In reply to Nate Graham from comment #11) > Glad to hear it. S. Christian Collins, is that your experience too? Yes, this does appear to be fixed now! Hooray! -- You are receiving this mail because: You are watching all bug changes.
[Merkuro] [Bug 486025] New: Imported google groupware doesn't immediately show after import
https://bugs.kde.org/show_bug.cgi?id=486025 Bug ID: 486025 Summary: Imported google groupware doesn't immediately show after import Classification: Applications Product: Merkuro Version: 24.02.1 Platform: Fedora RPMs OS: Linux Status: REPORTED Severity: minor Priority: NOR Component: general Assignee: claudio.cam...@kde.org Reporter: mspuban...@fastmail.us CC: c...@carlschwan.eu Target Milestone: --- SUMMARY Importing a new calendar (google groupware) did not show the imported calendar until after restart STEPS TO REPRODUCE 1. Have a Merkuro instance that lacks a google groupware calendar (ie after fresh Fedora install on system) 2. Start Merkuro and import the Google calendar 3. Current calendar in view doesn't update, must exit merkuro and restart it OBSERVED RESULT Google Groupware calendar doesn't automatically show after newly imported, must exit and restart Merkuro EXPECTED RESULT Update event after import in the app should make the calendar redraw with the newly imported calendar's events. This would be preferred from a usability standpoint, since the calendar was newly linked and imported it would verify the success of the operation. However, restarting Merkuro does make the Google events show. SOFTWARE/OS VERSIONS Windows: macOS: Linux/KDE Plasma: (available in About System) KDE Plasma Version: 6.0.3 KDE Frameworks Version: 6.0.0 Qt Version: 6.6.2 ADDITIONAL INFORMATION Fedora 40 Kernel Linux 6.8.7-300.fc40.x86_64 #1 SMP PREEMPT_DYNAMIC Micro-Star International Co., Ltd Bravo 15 A4DDR Linux msi 6.8.7-300.fc40.x86_64 #1 SMP PREEMPT_DYNAMIC Wed Apr 17 19:21:08 UTC 2024 x86_64 GNU/Linux Firmware Version: E16WKAMS.110 -- You are receiving this mail because: You are watching all bug changes.
[Merkuro] [Bug 482482] Merkuro Calandar starting wrong week in week-view
https://bugs.kde.org/show_bug.cgi?id=482482 Mark S changed: What|Removed |Added CC||mspuban...@fastmail.us --- Comment #4 from Mark S --- I happened to make a duplicate bug on redhat bugzilla for this, see: https://bugzilla.redhat.com/show_bug.cgi?id=2276317 -- You are receiving this mail because: You are watching all bug changes.
[policykit-kde-agent-1] [Bug 485407] polkit-kde-agent crashes with nullptr
https://bugs.kde.org/show_bug.cgi?id=485407 S. Christian Collins changed: What|Removed |Added CC||s_chriscoll...@hotmail.com -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 407459] new notifications: Abnormal space appears below "Open" and hamburger buttons when a download is completed
https://bugs.kde.org/show_bug.cgi?id=407459 --- Comment #20 from S. Christian Collins --- Reading again through the comments, I realize I've had the "morphing popups" desktop effect disabled for a while now, which might be why I no longer see the bug (or any of the other bugs that effect creates). So, the bug might still be out there, folks. Be sure to lock your doors at night and count your kids. -- You are receiving this mail because: You are watching all bug changes.
[dolphin] [Bug 464086] keyboard selection gets stuck when trying to delete a file permanently
https://bugs.kde.org/show_bug.cgi?id=464086 S. Christian Collins changed: What|Removed |Added Resolution|--- |WORKSFORME Status|REPORTED|RESOLVED --- Comment #1 from S. Christian Collins --- This bug was fixed at some point. Closing. -- You are receiving this mail because: You are watching all bug changes.
[dolphin] [Bug 425007] dolphin loses "all desktops" setting when a folder is opened via another application
https://bugs.kde.org/show_bug.cgi?id=425007 S. Christian Collins changed: What|Removed |Added Resolution|--- |WORKSFORME Status|REPORTED|RESOLVED --- Comment #6 from S. Christian Collins --- I haven't been able to reproduce this bug for a long time, so I consider it fixed. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 468371] Kate window rules: "All Desktops" + "No titlebar and frame" = pager & taskbar only see Kate on Desktop #1
https://bugs.kde.org/show_bug.cgi?id=468371 S. Christian Collins changed: What|Removed |Added Resolution|--- |WORKSFORME Status|REPORTED|RESOLVED --- Comment #5 from S. Christian Collins --- I have not encountered this bug in a while, so I am closing it. -- You are receiving this mail because: You are watching all bug changes.
[ark] [Bug 453452] creating 7zip archive of ~/.mozilla or ~/.thunderbird folder fails
https://bugs.kde.org/show_bug.cgi?id=453452 --- Comment #1 from S. Christian Collins --- This bug is still present in Ark 24.02.2 (Plasma 6.0.4). -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 407459] new notifications: Abnormal space appears below "Open" and hamburger buttons when a download is completed
https://bugs.kde.org/show_bug.cgi?id=407459 --- Comment #18 from S. Christian Collins --- I haven't experienced this bug in a long, long time. I'd say we can probably close it. -- 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 S. Christian Collins changed: What|Removed |Added Status|REPORTED|RESOLVED Resolution|--- |WORKSFORME --- Comment #20 from S. Christian Collins --- I can no longer reproduce this in Plasma 6. Closing. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 483689] Invisible text in some widget settings with mixed light/dark theme e.g. Breeze Twilight
https://bugs.kde.org/show_bug.cgi?id=483689 --- Comment #7 from S. Christian Collins --- Created attachment 168619 --> https://bugs.kde.org/attachment.cgi?id=168619=edit new look of the bug (sensors details) -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 483689] Invisible text in some widget settings with mixed light/dark theme e.g. Breeze Twilight
https://bugs.kde.org/show_bug.cgi?id=483689 --- Comment #6 from S. Christian Collins --- Created attachment 168618 --> https://bugs.kde.org/attachment.cgi?id=168618=edit new look of the bug (pie chart details) With the upgrade to Plasma 6.0.4 and Frameworks 6.1.0, this bug has changed its colors, literally. Previously, the text color for certain widgets was being pulled from the dark plasma theme, conflicting with the light application theme making the white text impossible to read against the white background (when using Twilight). Now, the widget background is also being pulled from the plasma theme, leading to cases of hard to read black text on a dark background and white check marks instead of black. -- You are receiving this mail because: You are watching all bug changes.
[kdesrc-build] [Bug 485564] Workspace build fails on Neon developer version when trying to build gpgme
https://bugs.kde.org/show_bug.cgi?id=485564 Malte S. Stretz changed: What|Removed |Added CC||nicolas.fe...@gmx.de --- Comment #2 from Malte S. Stretz --- Ok, I found the issue: There is no dependency at all defined between gpgme and libgpg-error. So the latter is never build (except for Qt I guess) and as long as the system headers match the gpgme package nobody notices. I worked around it via this command: echo 'third-party/gpgme: third-party/libgpg-error' >> ~/.local/state/sysadmin-repo-metadata/dependencies/dependency-data-kf6-qt6 Not sure how this should be fixed properly, maybe in https://invent.kde.org/nicolasfella/dependency-generator? The quickest fix would probably if third-party/libgpg-error was added as a dependency to https://invent.kde.org/frameworks/kwallet/-/blob/master/.kde-ci.yml since kwallet is the only app which depends on gpgme according to the dependencies file. -- You are receiving this mail because: You are watching all bug changes.
[kdesrc-build] [Bug 485564] Workspace build fails on Neon developer version when trying to build gpgme
https://bugs.kde.org/show_bug.cgi?id=485564 --- Comment #1 from Malte S. Stretz --- This still happens on Neon user edition. For me it fails in > Building gpgme from custom-qt6-libs (19/43) > Fetching remote changes to gpgme > Merging gpgme changes from branch master > No changes to gpgme source code, but proceeding to build anyway. > Compiling... failed (after 20 seconds) I checked https://invent.kde.org/sysadmin/repo-metadata/-/blob/master/module-definitions/custom-qt6-libs.ksb?ref_type=heads and it does define an "option" libgpg-error. But when I look into the src directory I only see the gpgme directory, not the libgpg-error so it is never checked out? Maybe because the libgpgme11-dev package which probably pulls in libgpg-error-dev as well is installed via https://invent.kde.org/sysadmin/repo-metadata/-/blob/master/distro-dependencies/debian.ini?ref_type=heads? -- You are receiving this mail because: You are watching all bug changes.
[kdesrc-build] [Bug 485564] Workspace build fails on Neon developer version when trying to build gpgme
https://bugs.kde.org/show_bug.cgi?id=485564 Malte S. Stretz changed: What|Removed |Added Status|REPORTED|CONFIRMED Ever confirmed|0 |1 CC||m...@apache.org -- You are receiving this mail because: You are watching all bug changes.
[dolphin] [Bug 482899] Dolphin can't write to folder with group write access
https://bugs.kde.org/show_bug.cgi?id=482899 --- Comment #10 from S. Christian Collins --- I can confirm this bug is indeed fixed in Frameworks 6.1. Thank you! -- You are receiving this mail because: You are watching all bug changes.
[krdc] [Bug 483638] TAB key not functional inside rdp windows client
https://bugs.kde.org/show_bug.cgi?id=483638 Joe S changed: What|Removed |Added CC||jmscdba+...@gmail.com --- Comment #5 from Joe S --- I have been trying to resolve the same problem with the tab key not working in a RDP sessions but I am connecting to xrdp on a linux server. As an example, if I run konsole in the rdp session and type ls -al and press the tab key it does not show the matches immediately ( .inputrc has set-show-all-if-ambiguous on ). If I connect using xfreerdp instead of krdc, then the tab key works perfectly in konsole. The konsole client is NOT the problem because I can replicate the tab key broken using libreoffice calc too. Start libreoffice calc ( cursor is in cell A1 ), press tab, nothing happens if you are using krdc client. Switch to using xfreerdp instead of krdc and the tab key works correctly in the rdp session moving the cursor to B1. IMHO, it seems like the tab key is being "consumed" by something instead of the current process. I say this because when using krdc and pressing tab ( whether in konsole or libreoffice calc ) those applications no longer respond to keystrokes, however, if you click on anything else ( the desktop background, another app, the taskbar ) to switch focus and then click back on the application ( either konsole or libreoffice calc ) then keystrokes are accepted again and until you press tab key again. My platform is openSUSE Tumbleweed 20240329 but I have replicated on 20240412 too. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 484473] Symbolic icons have wrong color when using Twilight theme
https://bugs.kde.org/show_bug.cgi?id=484473 --- Comment #5 from S. Christian Collins --- Perhaps the assigned component of this bug should be changed from "widget explorer" to "icon" or whatever is most appropriate, as this issue clearly affects more than just the widget explorer. Being assigned to the wrong component might hamper this bug's visibility to the pertinent developers. -- You are receiving this mail because: You are watching all bug changes.
[neon] [Bug 485578] /etc/xdg/autostart/klipper.desktop is obsolete or refers to wrong command
https://bugs.kde.org/show_bug.cgi?id=485578 Malte S. Stretz changed: What|Removed |Added Severity|normal |minor -- You are receiving this mail because: You are watching all bug changes.
[neon] [Bug 485578] New: /etc/xdg/autostart/klipper.desktop is obsolete or refers to wrong command
https://bugs.kde.org/show_bug.cgi?id=485578 Bug ID: 485578 Summary: /etc/xdg/autostart/klipper.desktop is obsolete or refers to wrong command Classification: KDE Neon Product: neon Version: unspecified Platform: Neon OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: Packages User Edition Assignee: neon-b...@kde.org Reporter: m...@apache.org CC: j...@jriddell.org, neon-b...@kde.org Target Milestone: --- SUMMARY I am not sure if this is a packaging bug so I file it against Neon. Feel free to move it to the proper product. When I looked at some other issue I found these lines in my journal: > Apr 15 09:12:48 slpn-nb-mss systemd-xdg-autostart-generator[1178]: Exec > binary 'klipper' does not exist: No such file or directory > Apr 15 09:12:48 slpn-nb-mss systemd-xdg-autostart-generator[1178]: Not > generating service for XDG autostart app-klipper@autostart.service, error > parsing Exec= line: No such file or directory The file /etc/xdg/autostart/klipper.desktop is provided by the plasma-workspace package which sounds wrong. Maybe a leftover from Plasma 5? I do have a working clipboard management icon in the tray area or whatever it is called nowadays. But sounds like that one is not called Klipper anymore? At least there is no klipper binary to be found and no package called klipper available. STEPS TO REPRODUCE 1. journalctl --user | grep klipper OBSERVED RESULT Error about an invalid klipper autostart entry. EXPECTED RESULT No such error. SOFTWARE/OS VERSIONS Operating System: KDE neon 6.0 KDE Plasma Version: 6.0.3 KDE Frameworks Version: 6.0.0 Qt Version: 6.7.0 Kernel Version: 6.5.0-27-generic (64-bit) Graphics Platform: Wayland Processors: 4 × Intel® Core™ i5-6300U CPU @ 2.40GHz Memory: 19,4 GiB of RAM Graphics Processor: Mesa Intel® HD Graphics 520 Manufacturer: LENOVO Product Name: 20F9CTO1WW System Version: ThinkPad T460s ADDITIONAL INFORMATION -- You are receiving this mail because: You are watching all bug changes.
[neon] [Bug 485546] New: /etc/issue not updated, still reports KDE neon 5.27
https://bugs.kde.org/show_bug.cgi?id=485546 Bug ID: 485546 Summary: /etc/issue not updated, still reports KDE neon 5.27 Classification: KDE Neon Product: neon Version: unspecified Platform: Neon OS: Linux Status: REPORTED Severity: minor Priority: NOR Component: Packages User Edition Assignee: neon-b...@kde.org Reporter: m...@apache.org CC: j...@jriddell.org, neon-b...@kde.org Target Milestone: --- SUMMARY # cat /etc/issue KDE neon 5.27 \n \l # lsb_release -a No LSB modules are available. Distributor ID: Neon Description:KDE neon 6.0 Release:22.04 Codename: jammy STEPS TO REPRODUCE 1. See above 2. Or Press Ctrl+Alt+F3 because the screen locker crashed 3. Profit? OBSERVED RESULT KDE Neon is still reported as 5.27 by agetty EXPECTED RESULT It should be 6.0 or since this isn't the first time (cf. bug 433022) maybe only 6 without a minor version? SOFTWARE/OS VERSIONS Operating System: KDE neon 6.0 KDE Plasma Version: 6.0.3 KDE Frameworks Version: 6.0.0 Qt Version: 6.7.0 Kernel Version: 6.5.0-27-generic (64-bit) Graphics Platform: Wayland Processors: 4 × Intel® Core™ i5-6300U CPU @ 2.40GHz Memory: 7,6 GiB of RAM Graphics Processor: Mesa Intel® HD Graphics 520 Manufacturer: LENOVO Product Name: 20F5S1H800 System Version: ThinkPad X260 ADDITIONAL INFORMATION Package: base-files Version: 12ubuntu4.6+p22.04+vrelease+git20240224.2032 Priority: required Essential: yes Section: admin Maintainer: Neon CI Original-Maintainer: Santiago Vila Installed-Size: 406 kB Provides: base Pre-Depends: awk Depends: libcrypt1 (>= 1:4.4.10-10ubuntu3), libc6 (>= 2.34) Breaks: debian-security-support (<< 2019.04.25), initscripts (<< 2.88dsf-13.3), sendfile (<< 2.1b.20080616-5.2~), ubuntu-server (<< 1.453) Replaces: base, dpkg (<= 1.15.0), miscutils Download-Size: 90,4 kB APT-Manual-Installed: yes APT-Sources: http://archive.neon.kde.org/user jammy/main amd64 Packages Description: Debian base system miscellaneous files -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 483691] plasma panel unresponsive after connecting secondary monitor aligned to the left of primary (Wayland)
https://bugs.kde.org/show_bug.cgi?id=483691 --- Comment #9 from S. Christian Collins --- I took a video reproducing steps 4 and 5 above on my laptop (after the reboot): https://youtu.be/Ew2JgrpOG7I -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 483691] plasma panel unresponsive after connecting secondary monitor aligned to the left of primary (Wayland)
https://bugs.kde.org/show_bug.cgi?id=483691 --- Comment #8 from S. Christian Collins --- (In reply to Nate Graham from comment #7) > Either way, we need to know if it reproduces at all in a new clean user > account. Thanks all! When I try these steps in a new user account with no changes to the UI from default, the following happens: 1. Plug in the monitor and configure to the left of primary screen: the panel works fine. 2. Unplug the monitor: the right side of the panel becomes unresponsive. 3. Reboot & log in again. Panel will again be responsive. 4. Plug in the monitor (which will remember its configuration to the left of primary): panel is unresponsive. 5. Unplug the monitor: all but the leftmost bit of the panel remains unresponsive. I haven't tried this yet with VirtualBox, but here is the system info from the laptop on which I reproduced the above: OS: KDE Neon 6.0 User Edition (Plasma Desktop 6.0.3, KDE Frameworks 6.0.0, Qt 6.7.0) Linux Kernel: 6.5.0-27-lowlatency (64-bit) PC: HP Pavilion m6-1035dx laptop CPU/GPU: AMD A10-4600M 2.3 GHz quad-core APU with Trinity [Radeon HD 7660G] Graphics (using radeon driver) RAM: 8GB DDR3 (2x 4GB PC3-12800 1600 MHz), 7.2GB usable Screen #1 (LVDS-1, screen 0): - Resolution: 1366 x 768 @ 60 Hz Screen #2 (HDMI-A-1, screen 1): - Monitor: Dell P170Sb 17" LCD Monitor - Resolution: 1280 x 1024 @ 75 Hz -- You are receiving this mail because: You are watching all bug changes.
[www.kde.org] [Bug 418239] Apply for a Developer Account
https://bugs.kde.org/show_bug.cgi?id=418239 Malte S. Stretz changed: What|Removed |Added Resolution|--- |NOT A BUG Status|REPORTED|RESOLVED -- You are receiving this mail because: You are watching all bug changes.
[ksshaskpass] [Bug 444862] ksshaskpass can not parse "The authenticity of host can't be established." message from OpenSSH
https://bugs.kde.org/show_bug.cgi?id=444862 Malte S. Stretz changed: What|Removed |Added See Also||https://bugs.kde.org/show_b ||ug.cgi?id=485418 -- You are receiving this mail because: You are watching all bug changes.
[ksshaskpass] [Bug 485418] ksshaskpass can not parse "Enter passphrase" messages from ssh-keygen
https://bugs.kde.org/show_bug.cgi?id=485418 Malte S. Stretz changed: What|Removed |Added See Also||https://bugs.kde.org/show_b ||ug.cgi?id=444862 Keywords||junior-jobs Platform|Other |Neon -- You are receiving this mail because: You are watching all bug changes.
[ksshaskpass] [Bug 485418] New: ksshaskpass can not parse "Enter passphrase" messages from ssh-keygen
https://bugs.kde.org/show_bug.cgi?id=485418 Bug ID: 485418 Summary: ksshaskpass can not parse "Enter passphrase" messages from ssh-keygen Classification: Applications Product: ksshaskpass Version: 6.0.3 Platform: Other OS: Linux Status: REPORTED Severity: minor Priority: NOR Component: general Assignee: jpwhit...@kde.org Reporter: m...@apache.org Target Milestone: --- SUMMARY This is like bug 444862 but for two different pattern. When a new key is generated via ssh-keygen ksshaspass complains about not being able to parse these prompts: ksshaskpass: Unable to parse phrase "Enter passphrase (empty for no passphrase): " ksshaskpass: Unable to parse phrase "Enter same passphrase again: " STEPS TO REPRODUCE 1. export SSH_ASKPASS_REQUIRE=prefer 2. export SSH_ASKPASS=/usr/bin/ksshaskpass 3. ssh-keygen -f /tmp/id_dummy OBSERVED RESULT No error message EXPECTED RESULT It actually works so this is more cosmetics. The error message should not appear though. SOFTWARE/OS VERSIONS Operating System: KDE neon 6.0 KDE Plasma Version: 6.0.3 KDE Frameworks Version: 6.0.0 Qt Version: 6.6.2 Kernel Version: 6.5.0-26-generic (64-bit) Graphics Platform: Wayland Processors: 4 × Intel® Core™ i5-6300U CPU @ 2.40GHz Memory: 19,4 GiB of RAM Graphics Processor: Mesa Intel® HD Graphics 520 Manufacturer: LENOVO Product Name: 20F9CTO1WW System Version: ThinkPad T460s ADDITIONAL INFORMATION Code can be found at https://github.com/KDE/ksshaskpass/blob/v6.0.3/src/main.cpp#L36 -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 484259] Auto login behaviour has X11 session selected even though Wayland is currently in use
https://bugs.kde.org/show_bug.cgi?id=484259 Malte S. Stretz changed: What|Removed |Added Ever confirmed|0 |1 Resolution|DUPLICATE |--- Status|RESOLVED|REOPENED --- Comment #4 from Malte S. Stretz --- This is not a duplicate of bug 483006. That one is describing the root cause which leads to the suboptimal behaviour of the KCM as described in the summary. There are a few things which can be improved in the KCM when such a thing (the session definition pointed at in the config disappears) happens: 1. The "Automatically log in" check mark should be disabled. Instead maybe a message should appear with a text like "The previously configured auto-login session is invalid. Please select a new one". 2. The value in "with session" should not default to "Plasma (X11)". That is actually the opposite of what is wanted according to bug 483006. It should at worst default to "Plasma (Wayland)". I think some heuristics can be added to make it default to the Plasma session for the currently running composer. Or even the currently running session but it looks like that information is not readily available anymore. I already digged a bit through the source code and might have a shot at this when I have some spare time. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 483691] plasma panel unresponsive after connecting secondary monitor aligned to the left of primary (Wayland)
https://bugs.kde.org/show_bug.cgi?id=483691 --- Comment #5 from S. Christian Collins --- Just now after testing your last steps, I unplugged the secondary monitor, and only some parts of the panel became responsive again to clicks. The panel itself isn't dead, though... I can still hit the Meta key to bring up the menu. It's just dead to mouse clicks throughout some areas of the panel. Again, this bug only happens when the secondary monitor is configured *to the left* of primary. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 483691] plasma panel unresponsive after connecting secondary monitor aligned to the left of primary (Wayland)
https://bugs.kde.org/show_bug.cgi?id=483691 --- Comment #4 from S. Christian Collins --- (In reply to Nate Graham from comment #3) > Sounds a bit like Bug 483188. Does it start working if you restart > plasmashell or maximize and de-maximize a window? Neither of these steps work. The command to restart plasmashell (systemctl --user restart plasma-plasmashell) does nothing. The panel just sits there, frozen until I unplug the secondary monitor. Also, while I mentioned that my affected laptop has an AMD GPU, I can reproduce this bug in VirtualBox on a different system with an NVIDIA graphics card (though obviously the NVIDIA driver is not running inside the virtual machine). See the video linked in my original report. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 483689] invisible text in widget settings
https://bugs.kde.org/show_bug.cgi?id=483689 --- Comment #4 from S. Christian Collins --- (In reply to Nate Graham from comment #3) > I can't reproduce the issue. I suspect it may be related to the color sin > your active color scheme or Plasma theme. Can you reproduce it in a new > clean user account? Aah! The issue only appears when using "Breeze Twilight" (light application theme with dark plasma theme). Perhaps the affected text boxes are getting their text color from the plasma theme rather than the application theme? I tested this in a KDE neon VirtualBox install (X11), rebooting between each theme change as the plasma theme didn't fully change over until I did. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 483691] plasma panel unresponsive after connecting secondary monitor aligned to the left of primary (Wayland)
https://bugs.kde.org/show_bug.cgi?id=483691 --- Comment #2 from S. Christian Collins --- (In reply to Nate Graham from comment #1) > What GPU hardware are you using? It is an old AMD APU: AMD A10-4600M 2.3 GHz quad-core APU with Trinity [Radeon HD 7660G] Graphics (using radeon driver) -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 483684] memory monitor circle sometimes stuck at 100%
https://bugs.kde.org/show_bug.cgi?id=483684 S. Christian Collins changed: What|Removed |Added Ever confirmed|0 |1 Status|RESOLVED|REOPENED Resolution|DUPLICATE |--- --- Comment #4 from S. Christian Collins --- (In reply to Nate Graham from comment #3) > > *** This bug has been marked as a duplicate of bug 477983 *** Nate, I don't think these are the same bugs. In bug #477983, it is the sensor data that is incorrect. In my bug, the reported value is correct, but the graphical representation (circle) is occasionally stuck at 100%. Also, in my original report, I had said this only happens on my laptop. I finally had it happen for the first time on my desktop just the other day. I wonder if system speed is a factor? My laptop is quite old and slow compared to my much faster desktop and has the bug happen much more frequently. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 402857] Touchpad gestures should be configurable
https://bugs.kde.org/show_bug.cgi?id=402857 --- Comment #12 from Ima S --- I looked at the source, and the gesture seems to be registered by these lines: https://invent.kde.org/plasma/kwin/-/blob/master/src/virtualdesktops.cpp#L772 If someone could wrap them with an if-statement that checks a toggle, that might be enough? I don't know how to contribute this myself or I would. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 402857] Touchpad gestures should be configurable
https://bugs.kde.org/show_bug.cgi?id=402857 Ima S changed: What|Removed |Added CC||imasuf...@gmail.com --- Comment #11 from Ima S --- I'd like to echo @breakingspell's comment for the plasma 6 upgrade. This is a serious issue for my laptop usage, I use my own custom gestures for almost all navigation (via libinput-gestures), and the current system breaks my entire config. Please add an off button in settings. I don't care about extensibility in the short term, power users can manage their own gestures with other tools for now, but only once we can turn off the current system. Even if other work is pending, at least add an on/off toggle in 'Settings -> Mouse & Touchpad -> Touchpad' for the next release. -- You are receiving this mail because: You are watching all bug changes.
[drkonqi] [Bug 484864] drkonqi-coredump-pickup.service breaks logging out during pre-start
https://bugs.kde.org/show_bug.cgi?id=484864 Malte S. Stretz changed: What|Removed |Added See Also||https://bugs.kde.org/show_b ||ug.cgi?id=485011 -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 485011] Can't log out of Plasma 6
https://bugs.kde.org/show_bug.cgi?id=485011 Malte S. Stretz changed: What|Removed |Added See Also||https://bugs.kde.org/show_b ||ug.cgi?id=484864 -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 485011] Can't log out of Plasma 6
https://bugs.kde.org/show_bug.cgi?id=485011 --- Comment #13 from Malte S. Stretz --- I digged a bit and it looks like the job is already run in "fail" mode but unless I miss something then the result of the returned job object is never checked: https://invent.kde.org/plasma/plasma-workspace/-/blob/v6.0.3/startkde/plasma-shutdown/shutdown.cpp?ref_type=tags#L126 There should probably some error message here, yes. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 485011] Can't log out of Plasma 6
https://bugs.kde.org/show_bug.cgi?id=485011 --- Comment #11 from Malte S. Stretz --- systemctl has a --job-mode switch for this and the shutdown/halt commands set the equivalent to "replace-irreversibly" according to the man page. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 485011] Can't log out of Plasma 6
https://bugs.kde.org/show_bug.cgi?id=485011 --- Comment #10 from Malte S. Stretz --- I found this: > systemd has a minimal transaction system: if a unit is requested to start up > or shut down it will add it and all its dependencies to a temporary > transaction. Then, it will verify if the transaction is consistent (i.e. > whether the ordering of all units is cycle-free). If it is not, systemd will > try to fix it up, and removes non-essential jobs from the transaction that > might remove the loop. Also, systemd tries to suppress non-essential jobs in > the transaction that would stop a running service. Finally it is checked > whether the jobs of the transaction contradict jobs that have already been > queued, and optionally the transaction is aborted then. If all worked out and > the transaction is consistent and minimized in its impact it is merged with > all already outstanding jobs and added to the run queue. Effectively this > means that before executing a requested operation, systemd will verify that > it makes sense, fixing it if possible, and only failing if it really cannot > work. Source: https://www.freedesktop.org/software/systemd/man/latest/systemd.html The root cause here seems to be that all units are transitioned to stopped except graphical-session which makes the whole session more or less a zombie. Maybe if the stopping of graphical-session could be marked as an essential job somehow the whole transaction would fail which should be a better outcome than this. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 485011] Can't log out of Plasma 6
https://bugs.kde.org/show_bug.cgi?id=485011 --- Comment #9 from Malte S. Stretz --- Looks very much like that one, yes. Shall we mark this as a duplicate or is there a deeper issue in the session handling itself which should be looked into? Couldn't other units break this as well? -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 485011] Can't log out of Plasma 6
https://bugs.kde.org/show_bug.cgi?id=485011 Malte S. Stretz changed: What|Removed |Added CC||sit...@kde.org --- Comment #7 from Malte S. Stretz --- I added Harald Sitter to the CC list but am not really sure if DrKonqi is really the root cause or just triggering another systemd dependency issue. Why are the other jobs stopped (eg. "Stopped target KDE Plasma Workspace.") even though something is wrong and do not really end the session and thus throw the whole session management into disorder? Some oddities I see here: 1. This affects only one of my two Notebooks running Neon 6.0.3 2. On the affected one only one user is affected. I cans till switch the session to another user and restart the system normally. 3. It is also not reliably affecting that user, maybe 80% of the cases. 4. The first time this happens I see the logout confirmation screen (I guess that is org.kde.LogoutPrompt) but when I confirm there nothing happens (I guess that should be handled by org.kde.Shutdown). 5. Once this happened once I don't ever see that confirmation screen for this user again and the logout button just doesn't do anything. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 485011] Can't log out of Plasma 6
https://bugs.kde.org/show_bug.cgi?id=485011 --- Comment #5 from Malte S. Stretz --- Instead of uninstalling drkonqi these command should be enough to work around the issue: systemctl --user stop drkonqi-coredump-pickup.service systemctl --user mask drkonqi-coredump-pickup.service Don't forget to execute this once the issue is fixed: systemctl --user unmask drkonqi-coredump-pickup.service -- You are receiving this mail because: You are watching all bug changes.
[frameworks-baloo] [Bug 484226] baloo_file crashes with assert "!filePath.endsWith(QLatin1Char('/'))" in xattrindexer
https://bugs.kde.org/show_bug.cgi?id=484226 Malte S. Stretz changed: What|Removed |Added CC||m...@apache.org -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 485011] Can't log out of Plasma 6
https://bugs.kde.org/show_bug.cgi?id=485011 Malte S. Stretz changed: What|Removed |Added Ever confirmed|0 |1 Status|REPORTED|CONFIRMED -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 485011] Can't log out of Plasma 6
https://bugs.kde.org/show_bug.cgi?id=485011 --- Comment #2 from Malte S. Stretz --- I see the same issue. Looks like a deadlock in systemd caused by drkonqi-coredump-processor. This started after an update of KDE Neon from 6.0.2 to 6.03. Apr 07 19:22:07 xxx plasmashell[1886]: file:///usr/share/plasma/plasmoids/org.kde.plasma.kickoff/contents/ui/ApplicationsPage.qml:202: TypeError: Cannot call method 'forceActiveFocus' of null Apr 07 19:22:10 xxx dbus-daemon[1269]: [session uid=1001 pid=1269] Activating service name='org.kde.LogoutPrompt' requested by ':1.27' (uid=1001 pid=1886 comm="/usr/bin/plasmashell --no-respawn " label="unconfined") Apr 07 19:22:10 xxx dbus-daemon[1269]: [session uid=1001 pid=1269] Successfully activated service 'org.kde.LogoutPrompt' Apr 07 19:22:11 xxx ksmserver-logout-greeter[2238]: qt.gui.imageio: libpng warning: iCCP: known incorrect sRGB profile Apr 07 19:22:11 xxx ksmserver-logout-greeter[2238]: kf.windowsystem: static bool KX11Extras::compositingActive() may only be used on X11 Apr 07 19:22:13 xxx dbus-daemon[1269]: [session uid=1001 pid=1269] Activating service name='org.kde.Shutdown' requested by ':1.48' (uid=1001 pid=2238 comm="/usr/lib/x86_64-linux-gnu/libexec/ksmserver-logout" label="unconfined") Apr 07 19:22:13 xxx dbus-daemon[1269]: [session uid=1001 pid=1269] Successfully activated service 'org.kde.Shutdown' Apr 07 19:22:13 xxx kded6[1863]: Service ":1.43" unregistered Apr 07 19:22:13 xxx systemd[1222]: Stopped target plasma-workspace-wayland.target. Apr 07 19:22:13 xxx systemd[1222]: Stopped target KDE Plasma Workspace. Apr 07 19:22:13 xxx systemd[1222]: Requested transaction contradicts existing jobs: Transaction for graphical-session.target/stop is destructive (drkonqi-coredump-pickup.service has 'start' job queued, but 'stop' is included in transaction). Apr 07 19:22:13 xxx systemd[1222]: graphical-session.target: Failed to enqueue stop job, ignoring: Transaction for graphical-session.target/stop is destructive (drkonqi-coredump-pickup.service has 'start' job queued, but 'stop' is included in transaction). Apr 07 19:22:13 xxx systemd[1222]: Stopped target KDE Plasma Workspace Core. Apr 07 19:22:13 xxx systemd[1222]: Stopped target Startup of XDG autostart applications. Apr 07 19:22:13 xxx systemd[1222]: Stopped target Session services which should run early before the graphical session is brought up. Operating System: KDE neon 6.0 KDE Plasma Version: 6.0.3 KDE Frameworks Version: 6.0.0 Qt Version: 6.6.3 Kernel Version: 6.5.0-26-generic (64-bit) Graphics Platform: Wayland Processors: 4 × Intel® Core™ i5-6300U CPU @ 2.40GHz Memory: 7,6 GiB of RAM Graphics Processor: Mesa Intel® HD Graphics 520 Manufacturer: LENOVO Product Name: 20F5S1H800 System Version: ThinkPad X260 -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 485011] Can't log out of Plasma 6
https://bugs.kde.org/show_bug.cgi?id=485011 Malte S. Stretz changed: What|Removed |Added CC||w...@culturanuova.net --- Comment #1 from Malte S. Stretz --- *** Bug 485129 has been marked as a duplicate of this bug. *** -- You are receiving this mail because: You are watching all bug changes.
[neon] [Bug 485129] power commands again not working
https://bugs.kde.org/show_bug.cgi?id=485129 Malte S. Stretz changed: What|Removed |Added Status|REPORTED|RESOLVED CC||m...@apache.org Resolution|--- |DUPLICATE --- Comment #1 from Malte S. Stretz --- *** This bug has been marked as a duplicate of bug 485011 *** -- You are receiving this mail because: You are watching all bug changes.
[neon] [Bug 485133] Package xdg-tools 1.2.x requires qtpaths for xdg-mime
https://bugs.kde.org/show_bug.cgi?id=485133 --- Comment #4 from Malte S. Stretz --- Created attachment 168254 --> https://bugs.kde.org/attachment.cgi?id=168254=edit Patch against xdg-mime I didn't bother yet to create a fdo Gitlab user but looks like the fix was quite overkill and no call to qtpaths is required at all: That call just returns the typical value for XDG_CONFIG_HOME (cf. https://github.com/qt/qtbase/blob/dev/src/corelib/io/qstandardpaths_unix.cpp#L237) ie. according to that change did Plasma 5 and later move to the default generic location of the mimapps.list file. I might post the attached patch to the project but maybe somebody with an existing account can posu it upstream. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 485011] Can't log out of Plasma 6
https://bugs.kde.org/show_bug.cgi?id=485011 Malte S. Stretz changed: What|Removed |Added CC||m...@apache.org -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 474639] Cannot launch ksmserver-logout-greeter when no global theme is set
https://bugs.kde.org/show_bug.cgi?id=474639 Malte S. Stretz changed: What|Removed |Added CC||m...@apache.org -- You are receiving this mail because: You are watching all bug changes.
[neon] [Bug 485133] Package xdg-tools 1.2.x requires qtpaths for xdg-mime
https://bugs.kde.org/show_bug.cgi?id=485133 Malte S. Stretz changed: What|Removed |Added See Also||https://bugs.kde.org/show_b ||ug.cgi?id=485135 -- You are receiving this mail because: You are watching all bug changes.
[neon] [Bug 485135] Should qtchooser default to qt6?
https://bugs.kde.org/show_bug.cgi?id=485135 Malte S. Stretz changed: What|Removed |Added See Also||https://bugs.kde.org/show_b ||ug.cgi?id=485133 -- You are receiving this mail because: You are watching all bug changes.
[neon] [Bug 485135] New: Should qtchooser default to qt6?
https://bugs.kde.org/show_bug.cgi?id=485135 Bug ID: 485135 Summary: Should qtchooser default to qt6? Classification: KDE Neon Product: neon Version: unspecified Platform: Neon OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: Packages User Edition Assignee: neon-b...@kde.org Reporter: m...@apache.org CC: j...@jriddell.org, neon-b...@kde.org, sit...@kde.org Target Milestone: --- SUMMARY While looking into bug 485133 I found out that qtchooser still defaults to qt6 on current KDE Neon. I had to execute this to make it default to qt6: sudo mkdir -p /etc/xdg/qtchooser sudo ln -s /usr/share/qtchooser/qt6-x86_64-linux-gnu.conf /etc/xdg/qtchooser/default.conf Shouldn't that be the default for Neon 6? STEPS TO REPRODUCE 1. Execute qmake --version OBSERVED RESULT qmake: could not exec '/usr/lib/qt5/bin/qmake': No such file or directory EXPECTED RESULT QMake version 3.1 Using Qt version 6.6.3 in /usr/lib/x86_64-linux-gnu SOFTWARE/OS VERSIONS Operating System: KDE neon 6.0 KDE Plasma Version: 6.0.3 KDE Frameworks Version: 6.0.0 Qt Version: 6.6.3 Kernel Version: 6.5.0-26-generic (64-bit) Graphics Platform: Wayland Processors: 4 × Intel® Core™ i5-6300U CPU @ 2.40GHz Memory: 7,6 GiB of RAM Graphics Processor: Mesa Intel® HD Graphics 520 Manufacturer: LENOVO Product Name: 20F5S1H800 System Version: ThinkPad X260 -- You are receiving this mail because: You are watching all bug changes.
[neon] [Bug 485133] Package xdg-tools 1.2.x requires qtpaths for xdg-mime
https://bugs.kde.org/show_bug.cgi?id=485133 Malte S. Stretz changed: What|Removed |Added Summary|Package xdg-tools |Package xdg-tools 1.2.x |(xdg-mime) requires qtpaths |requires qtpaths for ||xdg-mime -- You are receiving this mail because: You are watching all bug changes.
[neon] [Bug 485133] Package xdg-tools (xdg-mime) requires qtpaths
https://bugs.kde.org/show_bug.cgi?id=485133 --- Comment #3 from Malte S. Stretz --- Should maybe qtpaths moved to qt6-base? Looks like a useful utility and qt6-base already contains qmake which I'd also expect in qt6-base-dev-tools. qt6-base should probably depend on qtchooser then. -- You are receiving this mail because: You are watching all bug changes.
[neon] [Bug 485133] Package xdg-tools (xdg-mime) requires qtpaths
https://bugs.kde.org/show_bug.cgi?id=485133 Malte S. Stretz changed: What|Removed |Added Status|REPORTED|CONFIRMED Ever confirmed|0 |1 --- Comment #2 from Malte S. Stretz --- Looks like this was introduced with v1.2.0: # git tag --contains 6f36849cc90f953a80bc4200073ab0c95937208e v1.2.0 v1.2.1 -- You are receiving this mail because: You are watching all bug changes.
[neon] [Bug 485133] Package xdg-tools (xdg-mime) requires qtpaths
https://bugs.kde.org/show_bug.cgi?id=485133 --- Comment #1 from Malte S. Stretz --- Looks like the qtpaths dependency was introduced only recently (October last year): https://gitlab.freedesktop.org/xdg/xdg-utils/-/merge_requests/47#note_2108717 -- You are receiving this mail because: You are watching all bug changes.
