[gwenview] [Bug 481140] Gwenview crashes when cropping image
https://bugs.kde.org/show_bug.cgi?id=481140 Malte S. Stretz changed: What|Removed |Added Status|REPORTED|CONFIRMED Ever confirmed|0 |1 -- You are receiving this mail because: You are watching all bug changes.
[gwenview] [Bug 481140] Gwenview crashes when cropping image
https://bugs.kde.org/show_bug.cgi?id=481140 Malte S. Stretz changed: What|Removed |Added CC||m...@apache.org --- Comment #10 from Malte S. Stretz --- Created attachment 176271 --> https://bugs.kde.org/attachment.cgi?id=176271&action=edit A nice picture to reproduce the issue with I can reproduce this issue (Gwenview 24.08.3) with the attached image and when I try to set width or height to a one-digit value. Operating System: KDE neon 6.2 KDE Plasma Version: 6.2.3 KDE Frameworks Version: 6.8.0 Qt Version: 6.8.0 Kernel Version: 6.8.0-49-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 Status|REOPENED|RESOLVED Resolution|--- |FIXED --- Comment #18 from Malte S. Stretz --- (In reply to Omar Hany Kasban from comment #17) > (In reply to Omar Hany Kasban from comment #16) > > i get `ksmserver-logout-greeter[5072]: kf.windowsystem: static bool > > KX11Extras::compositingActive() may only be used on X11` on 6.2.3 > > please reopen it its not fixed > > masking drkonqi / removing drkonqi, doesn't work this time This looks like a different/new bug. Can you please report a new one? -- You are receiving this mail because: You are watching all bug changes.
[neon] [Bug 488749] Screen Recorder error in PipeWire remote in all screen recorders, include obs studio: black screen!
https://bugs.kde.org/show_bug.cgi?id=488749
Malte S. Stretz changed:
What|Removed |Added
Resolution|--- |FIXED
Status|CONFIRMED |RESOLVED
--- Comment #15 from Malte S. Stretz ---
Closing this since Neon 24.04.1 is available and seems to have fixed this
issue.
I don't know if it was necessary but I removed the pipewire PPA before
upgrading using these commands, followed by a reboot:
sudo true && echo 'DPkg::Options { "--force-overwrite"; };' | sudo tee
/etc/apt/apt.conf.d/99-dpkg-force-overwrite.conf
sudo ppa-purge pipewire-debian/pipewire-upstream
sudo rm /etc/apt/apt.conf.d/99-dpkg-force-overwrite.conf
--
You are receiving this mail because:
You are watching all bug changes.
[Falkon] [Bug 492704] Tabs always hidden
https://bugs.kde.org/show_bug.cgi?id=492704 Malte S. Stretz changed: What|Removed |Added Resolution|--- |NOT A BUG Status|REPORTED|RESOLVED --- Comment #1 from Malte S. Stretz --- I just discovered that I had the "Vertical Tabs" extension enabled but the sidebar was hidden. One could argue that the sidebar should appear once a new tab is opened but I guess this works as designed. -- You are receiving this mail because: You are watching all bug changes.
[Falkon] [Bug 492704] New: Tabs always hidden
https://bugs.kde.org/show_bug.cgi?id=492704 Bug ID: 492704 Summary: Tabs always hidden Classification: Applications Product: Falkon Version: 24.08.0 Platform: Neon OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: unassigned-b...@kde.org Reporter: m...@apache.org Target Milestone: --- SUMMARY Since while (I think since the Qt6 port) Falkon does not show a tab bar at all anymore. It doesn't matter what value the "Hide tabs when there is only one tab" option is set to. STEPS TO REPRODUCE 1. Open Falkon 2. Go to eg. www.kde.org 3. Press Ctrl+T OBSERVED RESULT No tab bar was visible when the app was started and no tab bar appeared when a new tab was opened EXPECTED RESULT Depending on the "hide tabs" option the tabs should have been visible from the start or not but as soon as a new tab is opened a tab bar should definitely be displayed. SOFTWARE/OS VERSIONS Operating System: KDE neon 6.0 KDE Plasma Version: 6.1.4 KDE Frameworks Version: 6.5.0 Qt Version: 6.7.2 Kernel Version: 6.8.0-40-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 ADDITIONAL INFORMATION -- You are receiving this mail because: You are watching all bug changes.
[okular] [Bug 492358] New: Values of some form fields are not shown in non-forms mode
https://bugs.kde.org/show_bug.cgi?id=492358 Bug ID: 492358 Summary: Values of some form fields are not shown in non-forms mode Classification: Applications Product: okular Version: 24.08.0 Platform: Neon OS: Linux Status: REPORTED Severity: major Priority: NOR Component: PDF backend Assignee: okular-de...@kde.org Reporter: m...@apache.org Target Milestone: --- Created attachment 173082 --> https://bugs.kde.org/attachment.cgi?id=173082&action=edit PDF document with form SUMMARY I will attach a PDF document which has an embedded form. There are two "date" fields which can be filled out in "Show Forms" mode. When that mode is exited and/or the PDF is printed no value is displayed for these fields. Saving the filled out document and opening it in Firefox (ie. pdf.js) shows the previously entered values. STEPS TO REPRODUCE 1. Start Okular 2. Download the form from https://www.hamburg.de/resource/blob/35658/bf5a89315bba109b3a8664d1ed4adcb1/arbeitszeitennachweis-kindertagespflege-data.pdf or use the attached version 3. Click the "Show Forms" button to switch to edit mode 4. Type in some value for "Name des Kindes" 5. Type in some date for "Geburtsdatum des Kindes". Like 01.01.1970 6. Leave the edit mode again by clicking "Show Forms" 7. Observe that the name will stay but the date will disappear (there is another date-like field "Beginn der Arbeit" which shows the same behaviour) 6. Save the file and close Okular 7. Open the file in Firefox 8. Observe that the values are filled out 9. I couldn't find an option to leave the edit mode there. But the value will stay visible in the print preview via Ctrl+P OBSERVED RESULT The values for those "date" fields disappear when the form edit mode is not active. Neither are they visible on a printout. EXPECTED RESULT The values should not disappear. SOFTWARE/OS VERSIONS Operating System: KDE neon 6.0 KDE Plasma Version: 6.1.4 KDE Frameworks Version: 6.5.0 Qt Version: 6.7.2 Kernel Version: 6.8.0-40-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 libpoppler-qt6-3 24.02.0-0xneon+22.04+jammy+release+build30 libpoppler134 24.02.0-0xneon+22.04+jammy+release+build30 -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 490563] Task switcher: 0x3: GL_INVALID_OPERATION in glDrawBuffers(unsupported buffer GL_BACK_LEFT)
https://bugs.kde.org/show_bug.cgi?id=490563 Malte S. Stretz changed: What|Removed |Added See Also||https://bugs.kde.org/show_b ||ug.cgi?id=490682 -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 490682] GL_INVALID_OPERATION errors when alt-tab tries to show window previews
https://bugs.kde.org/show_bug.cgi?id=490682 Malte S. Stretz changed: What|Removed |Added URL||https://bugreports.qt.io/br ||owse/QTBUG-122819 See Also||https://bugs.kde.org/show_b ||ug.cgi?id=490563 --- Comment #6 from Malte S. Stretz --- This bug was closed as "UPSTREAM" without a comment but I guess the upstream bug is https://bugreports.qt.io/browse/QTBUG-122819 -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 488869] When snapping a window to a custom tile using shift, kwin prints to journal "kwin_scene_opengl: 0x2: GL_INVALID_OPERATION in glDrawBuffers(unsupported buffer GL_BACK_LEFT)"
https://bugs.kde.org/show_bug.cgi?id=488869 Malte S. Stretz changed: What|Removed |Added CC||m...@apache.org URL||https://bugreports.qt.io/br ||owse/QTBUG-122819 --- Comment #2 from Malte S. Stretz --- This bug was closed as "UPSTREAM" without a comment but I guess the upstream bug is https://bugreports.qt.io/browse/QTBUG-122819 -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 490682] GL_INVALID_OPERATION errors when alt-tab tries to show window previews
https://bugs.kde.org/show_bug.cgi?id=490682 Malte S. Stretz changed: What|Removed |Added CC||m...@apache.org -- You are receiving this mail because: You are watching all bug changes.
[plasma-nm] [Bug 453453] IPv6 Address field not populated on existing WireGuard entries
https://bugs.kde.org/show_bug.cgi?id=453453 Malte S. Stretz changed: What|Removed |Added See Also||https://bugs.kde.org/show_b ||ug.cgi?id=457041 -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 457041] Can't save Wireguard VPN settings if IPv6 is configured
https://bugs.kde.org/show_bug.cgi?id=457041 Malte S. Stretz changed: What|Removed |Added See Also||https://bugs.kde.org/show_b ||ug.cgi?id=453453 --- Comment #12 from Malte S. Stretz --- There seem to be quite some issues with the IPv6 support for the Wireguard settings via the KCM: Added addresses (bug 453453) or routes (something I ran into) are not persisted even though the Apply button is not greyed out those cases. I guess that bug 461319 is related as well even though it doesn't mention IPv6. -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 457041] Can't save Wireguard VPN settings if IPv6 is configured
https://bugs.kde.org/show_bug.cgi?id=457041 Malte S. Stretz changed: What|Removed |Added Summary|Can't save Wireguard VPN|Can't save Wireguard VPN |settings|settings if IPv6 is ||configured -- You are receiving this mail because: You are watching all bug changes.
[plasma-nm] [Bug 453453] IPv6 Address field not populated on existing WireGuard entries
https://bugs.kde.org/show_bug.cgi?id=453453 Malte S. Stretz changed: What|Removed |Added Status|ASSIGNED|CONFIRMED CC||m...@apache.org -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 457041] Can't save Wireguard VPN settings
https://bugs.kde.org/show_bug.cgi?id=457041 Malte S. Stretz changed: What|Removed |Added Version|5.25.3 |6.1.4 CC||m...@apache.org -- You are receiving this mail because: You are watching all bug changes.
[plasma-nm] [Bug 458746] Apply button doesn't become active after editing wireguard connection
https://bugs.kde.org/show_bug.cgi?id=458746 Malte S. Stretz changed: What|Removed |Added CC||m...@apache.org Resolution|--- |DUPLICATE Status|CONFIRMED |RESOLVED --- Comment #5 from Malte S. Stretz --- *** This bug has been marked as a duplicate of bug 457041 *** -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 457041] Can't save Wireguard VPN settings
https://bugs.kde.org/show_bug.cgi?id=457041 Malte S. Stretz changed: What|Removed |Added CC||gudvinr+...@gmail.com --- Comment #11 from Malte S. Stretz --- *** Bug 458746 has been marked as a duplicate of this bug. *** -- You are receiving this mail because: You are watching all bug changes.
[plasma-nm] [Bug 491627] New: Import IPv6-only VPN config: ipv4.method: method "auto" is not supported for WireGuard
https://bugs.kde.org/show_bug.cgi?id=491627 Bug ID: 491627 Summary: Import IPv6-only VPN config: ipv4.method: method "auto" is not supported for WireGuard Classification: Plasma Product: plasma-nm Version: 6.1.3 Platform: Neon OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: editor Assignee: plasma-b...@kde.org Reporter: m...@apache.org Target Milestone: --- Created attachment 172546 --> https://bugs.kde.org/attachment.cgi?id=172546&action=edit Mullvad WireGuard config file SUMMARY The attached config file was generated via https://mullvad.net/en/account/wireguard-config?platform=linux choosing "Only IPv6" for "Tunnel traffic". Plasma NM fails to import this with the error message > ipv4.method: method "auto" is not supported for WireGuard It can be imported successfully via > nmcli connection import type wireguard file dk-cph-wg-001.conf STEPS TO REPRODUCE 1. System Settings -> Wi-Fi & Internet 2. "Plus" 3. "Import VPN connection..." 4. Choose attached file OBSERVED RESULT Error EXPECTED RESULT A successfully imported WireGuard VPN connection SOFTWARE/OS VERSIONS Operating System: KDE neon 6.0 KDE Plasma Version: 6.1.3 KDE Frameworks Version: 6.4.0 Qt Version: 6.7.2 Kernel Version: 6.5.0-45-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 489872] New: DE: Missing translation "Log out Now"
https://bugs.kde.org/show_bug.cgi?id=489872 Bug ID: 489872 Summary: DE: Missing translation "Log out Now" Classification: Plasma Product: plasmashell Version: 6.1.2 Platform: Neon OS: Linux Status: REPORTED Severity: minor Priority: NOR Component: Session Management Assignee: plasma-b...@kde.org Reporter: m...@apache.org CC: natalie_clar...@yahoo.de Target Milestone: 1.0 SUMMARY The German translation is missing a string on the log out screen: Everything is translated except the "Log out Now" caption. STEPS TO REPRODUCE 1. Use German translations 2. Log out from a session OBSERVED RESULT The left button is labelled with "Log out Now" EXPECTED RESULT It should be labelled "Jetzt abmelden" or something like that. SOFTWARE/OS VERSIONS Operating System: KDE neon 6.0 KDE Plasma Version: 6.1.2 KDE Frameworks Version: 6.3.0 Qt Version: 6.7.0 Kernel Version: 6.5.0-41-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 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 Status|REPORTED|RESOLVED Resolution|--- |FIXED --- Comment #1 from Malte S. Stretz --- This seems to be fixed in the current packages. -- You are receiving this mail because: You are watching all bug changes.
[neon] [Bug 488924] xdg-desktop-portal crashes after update to Plasma 6.1 when screen casting
https://bugs.kde.org/show_bug.cgi?id=488924 Malte S. Stretz changed: What|Removed |Added Resolution|--- |UPSTREAM Status|REPORTED|RESOLVED --- Comment #5 from Malte S. Stretz --- The crash is caused by the ancient Pipewire version in Ubuntu 22.04. This will be fixed once Neon is rebased on 24.04. As a workaround one can install the packages from the PPA at https://pipewire-debian.github.io/pipewire-debian/ The install will fail due to a dependency issue unless one removes the pipewire-pulse package first (it is reinstalled automatically). It is probably a good idea to downgrade pipewire before the upgrade to 24.04 is applied (eg. via ppa-purge). -- You are receiving this mail because: You are watching all bug changes.
[neon] [Bug 488924] xdg-desktop-portal crashes after update to Plasma 6.1 when screen casting
https://bugs.kde.org/show_bug.cgi?id=488924 Malte S. Stretz changed: What|Removed |Added See Also||https://bugs.kde.org/show_b ||ug.cgi?id=488749 -- You are receiving this mail because: You are watching all bug changes.
[neon] [Bug 488749] Screen Recorder error in PipeWire remote in all screen recorders, include obs studio: black screen!
https://bugs.kde.org/show_bug.cgi?id=488749 Malte S. Stretz changed: What|Removed |Added Platform|Other |Neon Ever confirmed|0 |1 See Also||https://bugs.kde.org/show_b ||ug.cgi?id=488924 Status|REPORTED|CONFIRMED CC||m...@apache.org --- Comment #7 from Malte S. Stretz --- This should be fixed once Plasma is rebased on Ubuntu 24.04 which is currently work in progress. In the meantime I worked around this issue by installing pipewire from https://pipewire-debian.github.io/pipewire-debian/ There is a dependency issue which means you have to remove the package pipewire-pulse before you update (it will autoamtically be added again). There are no guarantees though that the upgrade to 24.04 will work so you might want to remove that PPA via ppa-purge before you do that upgrade. -- You are receiving this mail because: You are watching all bug changes.
[neon] [Bug 489134] no menus in LibreOffice with Wayland Session
https://bugs.kde.org/show_bug.cgi?id=489134 Malte S. Stretz changed: What|Removed |Added Status|REPORTED|RESOLVED Resolution|--- |DOWNSTREAM See Also||https://github.com/flathub/ ||org.libreoffice.LibreOffice ||/issues/234 --- Comment #1 from Malte S. Stretz --- This seems to be an issue in the LibreOffice Flatpak which is tracked here https://github.com/flathub/org.libreoffice.LibreOffice/issues/234 -- You are receiving this mail because: You are watching all bug changes.
[krunner] [Bug 416145] Krunner doesn't immediately intercept rapidly-typed keystrokes for first invocation after login, leading the user to accidentally type text into whatever app is open
https://bugs.kde.org/show_bug.cgi?id=416145 Malte S. Stretz changed: What|Removed |Added CC||m...@apache.org -- You are receiving this mail because: You are watching all bug changes.
[kde] [Bug 489336] SSH connection with key not working in Wayland session
https://bugs.kde.org/show_bug.cgi?id=489336 Malte S. Stretz changed: What|Removed |Added Resolution|--- |UPSTREAM Status|REPORTED|RESOLVED CC||m...@apache.org --- Comment #1 from Malte S. Stretz --- I am not 100% sure but I guess you expect the ksshaskpass prompt to pop up? Then the issue is in upstream OpenSSH (and will be fixed in some future version, cf. https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1068044) which doesn't recognize Wayland sessions as graphical sessions and thus never starts the askpass process. You can try env SSH_ASKPASS_REQUIRE=force ssh -i /path/to/key.pem root@ -p 22 to see if that solves your issue. If that doesn't solve it it is probably some other local configuration issue and you should ask on https://discuss.kde.org/tag/neon or https://webchat.kde.org/#/room/#kde-neon-users:kde.org for help. -- You are receiving this mail because: You are watching all bug changes.
[ark] [Bug 489450] Add support for WIM files
https://bugs.kde.org/show_bug.cgi?id=489450 Malte S. Stretz changed: What|Removed |Added Severity|normal |wishlist -- You are receiving this mail because: You are watching all bug changes.
[neon] [Bug 488924] xdg-desktop-portal crashes after update to Plasma 6.1 when screen casting
https://bugs.kde.org/show_bug.cgi?id=488924 --- Comment #4 from Malte S. Stretz --- The Ubuntu pipewire changelog is quite interesting: pipewire (0.3.48-1ubuntu3) jammy; urgency=medium * Revert the previous change to resolve a regression with screencasting. Extra fixes are available upstream but figuring out the details will take longer (https://bugs.launchpad.net/ubuntu/+source/pipewire/+bug/1994928) -- Sebastien Bacher Wed, 09 Nov 2022 12:12:45 +0100 pipewire (0.3.48-1ubuntu2) jammy; urgency=medium * d/p/0001-buffers-ensure-buffer-size-does-not-exceed-maxsize.patch d/p/0002-gst-dequeue-a-shared-buffer-instead-of-original-pool.patch - Camera output freeze when using pipewiresrc (https://bugs.launchpad.net/ubuntu/+source/pipewire/+bug/1985057) -- Kai-Chuan Hsieh Mon, 15 Aug 2022 13:52:20 +0800 -- You are receiving this mail because: You are watching all bug changes.
[neon] [Bug 488924] xdg-desktop-portal crashes after update to Plasma 6.1 when screen casting
https://bugs.kde.org/show_bug.cgi?id=488924 --- Comment #3 from Malte S. Stretz --- Accord to Nate Graham on the Neon Development channel does current Plamsa not work with the old 0.3 pipewire, at least not the jammy version (https://matrix.to/#/!tTRWOsgaQxxZMiAvdi:kde.org/$2w6AojIYScf4KaoIdoPNEAZCM7jDk851LuEQKXIvQOw). I did quick backport of the kinetic version 0.3.58 (instead of jammy's 0.3.48) and that makes KPipeWire crash instead (I saw crashes within xdg-desktop-portal-kde and plasmashell within minutes after the switch). -- You are receiving this mail because: You are watching all bug changes.
[neon] [Bug 488924] xdg-desktop-portal crashes after update to Plasma 6.1 when screen casting
https://bugs.kde.org/show_bug.cgi?id=488924 --- Comment #2 from Malte S. Stretz --- I found a simpler way to trigger the crash which does not involve flatpak: Go to https://www.webrtc-experiment.com/Pluginfree-Screen-Sharing/ in Firefox (from the PPA) and try that. -- You are receiving this mail because: You are watching all bug changes.
[neon] [Bug 488924] xdg-desktop-portal crashes after update to Plasma 6.1 when screen casting
https://bugs.kde.org/show_bug.cgi?id=488924 --- Comment #1 from Malte S. Stretz --- The DrKonqi crash viewer does not pull the debug symbols, here is the same stack trace from gdb: Thread 8 (Thread 0x7768c49ff640 (LWP 22508)): #0 0x7768c5318bcf in __GI___poll (fds=0x59cd11c23f80, nfds=2, timeout=-1) at ../sysdeps/unix/sysv/linux/poll.c:29 #1 0x7768c5a9a256 in g_main_context_poll (priority=, n_fds=2, fds=0x59cd11c23f80, timeout=, context=0x59cd11c25590) at ../../../glib/gmain.c:4518 #2 g_main_context_iterate.constprop.0 (context=context@entry=0x59cd11c25590, block=block@entry=1, dispatch=dispatch@entry=1, self=) at ../../../glib/gmain.c:4208 #3 0x7768c5a423e3 in g_main_context_iteration (context=0x59cd11c25590, may_block=may_block@entry=1) at ../../../glib/gmain.c:4278 #4 0x7768c5a42431 in glib_worker_main (data=) at ../../../glib/gmain.c:6180 #5 0x7768c5a73ab1 in g_thread_proxy (data=0x59cd11bf4360) at ../../../glib/gthread.c:827 #6 0x7768c5294ac3 in start_thread (arg=) at ./nptl/pthread_create.c:442 #7 0x7768c5326850 in clone3 () at ../sysdeps/unix/sysv/linux/x86_64/clone3.S:81 Thread 7 (Thread 0x7768bd3fd640 (LWP 22517)): #0 0x7768c52e57f8 in __GI___clock_nanosleep (clock_id=clock_id@entry=0, flags=flags@entry=0, req=req@entry=0x7768bd3fccb0, rem=rem@entry=0x7768bd3fccb0) at ../sysdeps/unix/sysv/linux/clock_nanosleep.c:78 #1 0x7768c52ea677 in __GI___nanosleep (req=req@entry=0x7768bd3fccb0, rem=rem@entry=0x7768bd3fccb0) at ../sysdeps/unix/sysv/linux/nanosleep.c:25 #2 0x7768c52ea5ae in __sleep (seconds=0, seconds@entry=5) at ../sysdeps/posix/sleep.c:55 #3 0x59cd106886f3 in background_monitor (data=) at ../src/background.c:654 #4 0x7768c5a73ab1 in g_thread_proxy (data=0x59cd11ce4980) at ../../../glib/gthread.c:827 #5 0x7768c5294ac3 in start_thread (arg=) at ./nptl/pthread_create.c:442 #6 0x7768c5326850 in clone3 () at ../sysdeps/unix/sysv/linux/x86_64/clone3.S:81 Thread 6 (Thread 0x7768bf7fe640 (LWP 26844)): #0 0x7768c5325e2e in epoll_wait (epfd=26, events=0x7768bf7fd880, maxevents=32, timeout=-1) at ../sysdeps/unix/sysv/linux/epoll_wait.c:30 #1 0x7768c4e18918 in () at /usr/lib/x86_64-linux-gnu/spa-0.2/support/libspa-support.so #2 0x7768c4e0bd7c in () at /usr/lib/x86_64-linux-gnu/spa-0.2/support/libspa-support.so #3 0x7768c56ee226 in () at /lib/x86_64-linux-gnu/libpipewire-0.3.so.0 #4 0x7768c5294ac3 in start_thread (arg=) at ./nptl/pthread_create.c:442 #5 0x7768c5326850 in clone3 () at ../sysdeps/unix/sysv/linux/x86_64/clone3.S:81 Thread 5 (Thread 0x7768b640 (LWP 22509)): #0 0x7768c5318bcf in __GI___poll (fds=0x59cd11c92b70, nfds=4, timeout=-1) at ../sysdeps/unix/sysv/linux/poll.c:29 #1 0x7768c5a9a256 in g_main_context_poll (priority=, n_fds=4, fds=0x59cd11c92b70, timeout=, context=0x59cd11c30150) at ../../../glib/gmain.c:4518 #2 g_main_context_iterate.constprop.0 (context=0x59cd11c30150, block=block@entry=1, dispatch=dispatch@entry=1, self=) at ../../../glib/gmain.c:4208 #3 0x7768c5a442b3 in g_main_loop_run (loop=0x59cd11c30240) at ../../../glib/gmain.c:4413 #4 0x7768c592a81a in gdbus_shared_thread_func (user_data=0x59cd11c22520) at ../../../gio/gdbusprivate.c:282 #5 0x7768c5a73ab1 in g_thread_proxy (data=0x59cd11c185e0) at ../../../glib/gthread.c:827 #6 0x7768c5294ac3 in start_thread (arg=) at ./nptl/pthread_create.c:442 #7 0x7768c5326850 in clone3 () at ../sysdeps/unix/sysv/linux/x86_64/clone3.S:81 Thread 4 (Thread 0x7768c4e61cc0 (LWP 22502)): #0 0x7768c5318bcf in __GI___poll (fds=0x59cd11c4cbf0, nfds=3, timeout=-1) at ../sysdeps/unix/sysv/linux/poll.c:29 #1 0x7768c5a9a256 in g_main_context_poll (priority=, n_fds=3, fds=0x59cd11c4cbf0, timeout=, context=0x59cd11c1dfb0) at ../../../glib/gmain.c:4518 #2 g_main_context_iterate.constprop.0 (context=0x59cd11c1dfb0, block=block@entry=1, dispatch=dispatch@entry=1, self=) at ../../../glib/gmain.c:4208 #3 0x7768c5a442b3 in g_main_loop_run (loop=0x59cd11c10770) at ../../../glib/gmain.c:4413 #4 0x59cd10656a25 in main (argc=, argv=) at ../src/xdg-desktop-portal.c:496 Thread 3 (Thread 0x7768bdbfe640 (LWP 22516)): #0 0x7768c5325e2e in epoll_wait (epfd=15, events=0x7768bdbfd880, maxevents=32, timeout=-1) at ../sysdeps/unix/sysv/linux/epoll_wait.c:30 #1 0x7768c4e18918 in () at /usr/lib/x86_64-linux-gnu/spa-0.2/support/libspa-support.so #2 0x7768c4e0bd7c in () at /usr/lib/x86_64-linux-gnu/spa-0.2/support/libspa-support.so #3 0x7768c56ee226 in () at /lib/x86_64-linux-gnu/libpipewire-0.3.so.0 #4 0x7768c5294ac3 in start_thread (arg=) at ./nptl/pthread_create.c:442 #5 0x7768c5326850 in clone3 () at ../sysdeps/unix/sysv/linux/x86_64/clone3.S:81 Thread 2 (Thread 0x7768be3ff640 (LWP 22514)): #0 0x7768c5318bcf in __GI___poll (fds=0x59cd11c6dd60, nfds=1, timeout=-1) at ../sysdeps/unix/sysv/linux/poll.c:29 #1 0x7768c5a9a256 in g_main_context_poll (priority=, n_fds=1
[neon] [Bug 488924] New: xdg-desktop-portal crashes after update to Plasma 6.1 when screen casting
https://bugs.kde.org/show_bug.cgi?id=488924 Bug ID: 488924 Summary: xdg-desktop-portal crashes after update to Plasma 6.1 when screen casting Classification: KDE Neon Product: neon Version: unspecified Platform: Neon OS: Linux Status: REPORTED Severity: crash 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: --- Created attachment 170785 --> https://bugs.kde.org/attachment.cgi?id=170785&action=edit /var/log/apt/history.log SUMMARY I updated to Plasma 6.1 the day before yesterday and since then xdg-desktop-portal crashes when I try to share my screen. I (have to) use Teams and I use the teams-for-linux Flatpak (cf. https://flathub.org/de/apps/com.github.IsmaelMartinez.teams_for_linux). I use screen sharing almost daily so I am sure it worked earlier this week. The odd thing is that neither flatpak nor xdg-desktop-portal nor libpipewire was updated according to apt's history.log (attached). My guess is that somehow xdg-desktop-portal-kde (which was updated) cases this (I don't fully understand how these components work together). I found some older bug from 2023 which affected Ubuntu 22.04 which sound similar and were caused by version incompatibilities in pipewire (https://gitlab.freedesktop.org/pipewire/pipewire/-/issues/2964) in the one case and something in xdg-desktop-portal in another case (https://github.com/flatpak/xdg-desktop-portal/issues/771). But the stack traces look differently and those should either have been fixed or have affected me a long time ago. STEPS TO REPRODUCE I can 100% reproduce this with these steps but I will try to find another reproducer with another piece of software: 1. Install and start teams-for-linux Flatpak 2. Start a call and start screen sharing 3. The xdg-desktop-portal-kde dialog will pop up, select a screen to share and confirm 4. The screen share button in Teams will be red for a moment (as it is when you do screen sharing) and then go back to the normal state 5. At the same time the red screen sharing KDE notification will appear in the tray bar and stay like that 6. Check your journal or coredumpctl or drkonqi-coredump-gui and you will see the crash OBSERVED RESULT Screen sharing does not work and xdg-desktop-portal crashes EXPECTED RESULT Screen sharing should work and xdg-desktop-portal should not crash SOFTWARE/OS VERSIONS Operating System: KDE neon 6.0 KDE Plasma Version: 6.1.0 KDE Frameworks Version: 6.3.0 Qt Version: 6.7.0 Kernel Version: 6.5.0-41-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 PID: 22502 (xdg-desktop-por) UID: 1000 (stretz) GID: 1000 (stretz) Signal: 11 (SEGV) Timestamp: Fri 2024-06-21 22:40:12 CEST (3min 44s ago) Command Line: /usr/libexec/xdg-desktop-portal Executable: /usr/libexec/xdg-desktop-portal Control Group: /user.slice/user-1000.slice/user@1000.service/session.slice/xdg-desktop-portal.service Unit: user@1000.service User Unit: xdg-desktop-portal.service Slice: user-1000.slice Owner UID: 1000 (stretz) Boot ID: bd16653cc1514a478b7de48af136b470 Machine ID: 8a16726dcc4c48d5a09d89e06cd6eeb6 Hostname: slpn-nb-mss Storage: /var/lib/systemd/coredump/core.xdg-desktop-por.1000.bd16653cc1514a478b7de48af136b470.22502.171900241200.zst (present) Disk Size: 443.0K Message: Process 22502 (xdg-desktop-por) of user 1000 dumped core. Found module linux-vdso.so.1 with build-id: c3530aed66e71bfd10af66039f58cc7c4d2eaba8 Found module libpipewire-module-session-manager.so with build-id: a4fa9861ba90f36edb94076d1dfef11d1c561d5e Found module libpipewire-module-metadata.so with build-id: dafd3ff9e45eda8b8e72a6c4ee9859bbf3efacfb Found module libpipewire-module-adapter.so with build-id: 4229761ed63759830ca135ab7803b3b450df049a Found module libpipewire-module-client-device.so with build-id: b251ac1d891b2fdc5b8bf4cac47f3211dd44286b Found module libpipewire-module-client-node.so with build-id: 378e0e3bfe3777ae7f02c07f42351b73818bf265 Found module libpipewire-module-protocol-native.so with build-id: 95016f55aab5ffa103dec6b3585936003036b597 Found module libdbus-1.so.3 with build-id: 63e8b99215502138cb63afd6d65851a5e837ed49 Found module libspa-dbus.so with build-id: 7a8c8e1a46e27116cbe556707781aa1785593e07 Found module libspa-journal.so with build-id: 8013a6aa985deab57e102a306d301
[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.
[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.
[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.
[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.
[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.
[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.
[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.
[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&action=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.
[neon] [Bug 485133] New: Package xdg-tools (xdg-mime) requires qtpaths
https://bugs.kde.org/show_bug.cgi?id=485133
Bug ID: 485133
Summary: Package xdg-tools (xdg-mime) requires qtpaths
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
I just installed some odd 3rd party application and the installation script
showed these errors at the end:
Use of uninitialized value $deepLink in substitution (s///) at ./install.pl
line 1087, line 5.
/usr/bin/xdg-mime: 856: qtpaths: not found
Use of uninitialized value $deepLink in concatenation (.) or string at
./install.pl line 1001.
I think this is a bug in xdg-mime to require that application but for now it
looks like it is the way it is and qtchooser and qt6-base-dev-tools have to be
installed for xdg-tools 1.2.1 to work properly on KDE 5 and later.
# sed -n -e '850,860p' $(which xdg-mime)
#
# [Removed Associations]
# text/plain=gnome-gedit.desktop;gnu-emacs.desktop;
vendor="$1"
mimetype="$2"
if [ "${KDE_SESSION_VERSION:-0}" -gt 4 ] ; then
default_dir="$(qtpaths --writable-path ConfigLocation)"
default_file="$default_dir/mimeapps.list"
elif [ x"$KDE_SESSION_VERSION" = x"4" ]; then
default_dir="$(kde4-config --path xdgdata-apps 2> /dev/null | cut -d
':' -f 1)"
default_file="$default_dir/mimeapps.list"
STEPS TO REPRODUCE
1. Make sure neither qttools5-dev-tools nor qt6-base-dev-tools are installed
2. Download the installer tarball from
https://foto.budni.de/bestellsoftware.html?keyAccount=1773&product=391
3a. Execute the contained install.pl
3b. Or grep for the call to xdg-mime to see how it is called and execute it
manually
OBSERVED RESULT
Error message as stated above, properly part of the software is not installed
correctly
EXPECTED RESULT
No 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.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
ADDITIONAL INFORMATION
Package: xdg-utils
Version: 1.2.1-0xneon+22.04+jammy+release+build5
Priority: optional
Section: utils
Maintainer: Neon CI
Installed-Size: 350 kB
Recommends: libfile-mimeinfo-perl, libnet-dbus-perl, libx11-protocol-perl,
x11-utils, x11-xserver-utils
Homepage: https://www.freedesktop.org/wiki/Software/xdg-utils/
Download-Size: 69,7 kB
APT-Manual-Installed: no
APT-Sources: http://archive.neon.kde.org/user jammy/main amd64 Packages
Description: desktop integration utilities from freedesktop.org
--
You are receiving this mail because:
You are watching all bug changes.
[neon] [Bug 484974] "Debuginfod has been disabled" on KDE Neon
https://bugs.kde.org/show_bug.cgi?id=484974 --- Comment #1 from Malte S. Stretz --- Looks like somebody forgot to add a `-D` in https://invent.kde.org/neon/kde/drkonqi/-/blob/Neon/release/debian/rules?ref_type=heads#L5 -- You are receiving this mail because: You are watching all bug changes.
[drkonqi] [Bug 454063] debuginfod symbols not retrieved with gdb 12
https://bugs.kde.org/show_bug.cgi?id=454063 Malte S. Stretz changed: What|Removed |Added See Also||https://bugs.kde.org/show_b ||ug.cgi?id=484974 -- You are receiving this mail because: You are watching all bug changes.
[neon] [Bug 484974] "Debuginfod has been disabled" on KDE Neon
https://bugs.kde.org/show_bug.cgi?id=484974 Malte S. Stretz changed: What|Removed |Added See Also||https://bugs.kde.org/show_b ||ug.cgi?id=454063 -- You are receiving this mail because: You are watching all bug changes.
[neon] [Bug 484974] New: "Debuginfod has been disabled" on KDE Neon
https://bugs.kde.org/show_bug.cgi?id=484974 Bug ID: 484974 Summary: "Debuginfod has been disabled" on KDE Neon 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 The "Developer Information" in DrKonqi's Crash handler starts with > This GDB supports auto-downloading debuginfo from the following URLs: > https://debuginfod.neon.kde.org/: > Enable debuginfod for this session? (y or [n]) [answered N; input not from > terminal] > Debuginfod has been disabled. > To make this setting permanent, add 'set debuginfod enabled off' to .gdbinit. This should be fixed via bug 454063 but it looks like distros have to set WITH_GDB12 explicitly when compiling the package. STEPS TO REPRODUCE 1. Make sure you have no debug symbols installed 2. kwrite & 3. killall -SEGV kwrite 4. Look at the Developer Info of the Crash Reporter (m OBSERVED RESULT No debug symbols are downloaded from https://debuginfod.neon.kde.org/ for eg. Qt6: Thread 12 (Thread 0x7583d0ffe640 (LWP 90704)): #0 0x7583d8918bcf in __GI___poll (fds=0x7583d0ffda10, nfds=2, timeout=-1) at ../sysdeps/unix/sysv/linux/poll.c:29 #1 0x7583d3df18d1 in ?? () from /lib/x86_64-linux-gnu/libQt6WaylandClient.so.6 #2 0x7583d8f5ce7d in ?? () from /lib/x86_64-linux-gnu/libQt6Core.so.6 #3 0x7583d8894ac3 in start_thread (arg=) at ./nptl/pthread_create.c:442 #4 0x7583d8926850 in clone3 () at ../sysdeps/unix/sysv/linux/x86_64/clone3.S:81 EXPECTED RESULT A better stack trace 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 -- You are receiving this mail because: You are watching all bug changes.
[drkonqi] [Bug 482203] drkonqi-sentry-postman keeps uploading with full speed
https://bugs.kde.org/show_bug.cgi?id=482203 --- Comment #4 from Malte S. Stretz --- I got carried away and totally forgot what I originally wanted to ask: I wonder how big those files are and how many there are, could you paste the output of the following command please: ls -lh ~/.cache/drkonqi/sentry-envelopes/ ~/.cache/drkonqi/sentry-sent-envelopes/ -- You are receiving this mail because: You are watching all bug changes.
[drkonqi] [Bug 484958] Wrong Sentry DSN in preamble.py?
https://bugs.kde.org/show_bug.cgi?id=484958 Malte S. Stretz changed: What|Removed |Added Status|REPORTED|RESOLVED Resolution|--- |NOT A BUG --- Comment #1 from Malte S. Stretz --- Ok, I read up on https://develop.sentry.dev/sdk/overview/#parsing-the-dsn and this is not an issue at all. -- You are receiving this mail because: You are watching all bug changes.
[drkonqi] [Bug 482203] drkonqi-sentry-postman keeps uploading with full speed
https://bugs.kde.org/show_bug.cgi?id=482203 --- Comment #3 from Malte S. Stretz --- I agree that there should be a GUI to manage the crash report queue. The queued reports can be found at ~/.cache/drkonqi/sentry-envelopes/ and the sent items at ~/.cache/drkonqi/sentry-sent-envelopes/ and too clear the queue you can delete the former directory. Since at least on my machine those files are only around 100 kB I don't know if some throttling is really required. Unless maybe you have many of them or a really slow internet connection. It should be possible though to save bandwidth and send the data compressed according to https://develop.sentry.dev/sdk/overview/#request-compression It also looks like the current error handling behaviour could be improved. If I interpret the code correctly then it will try to send all queued files and if one can't be sent due to whatever reason it will keep it in the queue to be picked up by the next run. The files will stick around for 30 days which seems to be a bit excessive. I'd reduce that to 7 days or so and add some logic to avoid resending if the server rejects the payload. I think there are also some issues with the systemd units: The timer is configured to run OnCalendar=hourly which will wake it every hour at the full hour. That's not really an issue for the user but not optimal for the server since it can cause a thundering herd problem. I would change that to OnUnitActiveSec=1 hour RandomizedDelaySec=5 minutes The timer has ConditionPathExistsGlob set. I might be wrong but I think (judging from the output of systemctl --user status drkonqi-sentry-postman.timer) this is evaluated only on unit start time, not on each interval. Ie. when nothing is queued on Plasma session start (when the timer is started) this timer is never executed. Maybe this condition should just be dropped. Then the postman would be executed once per hour but should exit quickly since it doesn't find any files to process. And I think on logon the service is executed twice if any events are queued: Once because of the PartOf=graphical-session.target in the service file and once because the path unit will be triggered. -- You are receiving this mail because: You are watching all bug changes.
[drkonqi] [Bug 484958] New: Wrong Sentry DSN in preamble.py?
https://bugs.kde.org/show_bug.cgi?id=484958 Bug ID: 484958 Summary: Wrong Sentry DSN in preamble.py? Classification: Applications Product: drkonqi Version: 6.0.3 Platform: Neon OS: Linux Status: REPORTED Severity: minor Priority: NOR Component: general Assignee: plasma-b...@kde.org Reporter: m...@apache.org Target Milestone: --- SUMMARY While trying to understand how the "new" Automatic Crash Reporting works and where it is hosted I had to dig a bit and found the MR https://invent.kde.org/plasma/drkonqi/-/merge_requests/210/diffs While staring at the diff I noticed a difference between the URL with the hard coded key and index in preamble.py and the ones generated in SentryDSNContext::dsnUrl(): While the latter have the path /api/ before the index the former does not. This looks wrong to me I'd assume that the DSN should be https://d6d53bb0121041dd97f59e29051a1...@crash-reports.kde.org/api/13 instead. I may be wrong of course in which case feel free to just close this report :-) Two additional nits: * I'd put those values into constants and use an f-string instead of having that long URL hardcoded * Out of interest I looked at https://autoconfig.kde.org/drkonqi/sentry/0/dsns.json and couldn't find a project with the index 13. I'd add it there for completeness sake. OBSERVED RESULT The hard coded DSN URL is "https://d6d53bb0121041dd97f59e29051a1...@crash-reports.kde.org/13"; EXPECTED RESULT It looks like the DSN URL should be "https://d6d53bb0121041dd97f59e29051a1...@crash-reports.kde.org/api/13"; instead. -- You are receiving this mail because: You are watching all bug changes.
[drkonqi] [Bug 482203] drkonqi-sentry-postman keeps uploading with full speed
https://bugs.kde.org/show_bug.cgi?id=482203 Malte S. Stretz changed: What|Removed |Added CC||m...@apache.org -- 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 --- Comment #2 from Malte S. Stretz --- Created attachment 167621 --> https://bugs.kde.org/attachment.cgi?id=167621&action=edit diff between old and fixed settings I fixed the settings and the cause for this behaviour seems to be that the session "plasmawayland" was renamed to just "plasma". Some backwards compatibility would be nice. -- You are receiving this mail because: You are watching all bug changes.
[neon] [Bug 484260] After upgrade from 5.27 to 6.0.2 SDDM auto login does not work anymore
https://bugs.kde.org/show_bug.cgi?id=484260 --- Comment #1 from Malte S. Stretz --- Created attachment 167619 --> https://bugs.kde.org/attachment.cgi?id=167619&action=edit diff between old and fixed settings Looks like the "plasmawayland" session was renamed to plain "plasma", cf. attached diff. -- You are receiving this mail because: You are watching all bug changes.
[neon] [Bug 484260] After upgrade from 5.27 to 6.0.2 SDDM auto login does not work anymore
https://bugs.kde.org/show_bug.cgi?id=484260 Malte S. Stretz changed: What|Removed |Added See Also||https://bugs.kde.org/show_b ||ug.cgi?id=484259 -- 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 See Also||https://bugs.kde.org/show_b ||ug.cgi?id=484260 -- You are receiving this mail because: You are watching all bug changes.
[neon] [Bug 484260] New: After upgrade from 5.27 to 6.0.2 SDDM auto login does not work anymore
https://bugs.kde.org/show_bug.cgi?id=484260 Bug ID: 484260 Summary: After upgrade from 5.27 to 6.0.2 SDDM auto login does not work anymore Classification: KDE Neon Product: neon Version: unspecified Platform: Other 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 After an upgrade from Neon 5.27.10 (sddm 0.20.0-0xneon+22.04+jammy+release+build31) to 6.0.2 (0.21.0-0xneon+22.04+jammy+release+build35) the SDDM auto-login setting not work anymore. The file /etc/sddm.conf.d/kde_settings.conf still looks good but it is probably missing something. This happened before and I will re-enable it and add a diff to see the differences. STEPS TO REPRODUCE 1. Enable aut-login in kde-config-sddm and verify that it works 2. Upgrade from 5.27 to 6.0.2 3. After reboot, stare at the login screen OBSERVED RESULT I am not logged in automatically EXPECTED RESULT I should have been logged in automatically SOFTWARE/OS VERSIONS Operating System: KDE neon 6.0 KDE Plasma Version: 6.0.2 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 -- You are receiving this mail because: You are watching all bug changes.
[kscreenlocker] [Bug 346741] bring back "auto-lock screen on login" option from KDM/Plasma 4
https://bugs.kde.org/show_bug.cgi?id=346741 Malte S. Stretz changed: What|Removed |Added CC||m...@apache.org -- 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 --- Comment #1 from Malte S. Stretz --- Created attachment 167617 --> https://bugs.kde.org/attachment.cgi?id=167617&action=edit Screenshot -- 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 See Also||https://bugs.kde.org/show_b ||ug.cgi?id=432018 -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 432018] behaviour always has plasma x11 session selected, ignores actual config
https://bugs.kde.org/show_bug.cgi?id=432018 Malte S. Stretz changed: What|Removed |Added See Also||https://bugs.kde.org/show_b ||ug.cgi?id=484259 -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 484259] New: Auto login behaviour has X11 session selected even though Wayland is currently in use
https://bugs.kde.org/show_bug.cgi?id=484259 Bug ID: 484259 Summary: Auto login behaviour has X11 session selected even though Wayland is currently in use Classification: Applications Product: systemsettings Version: 6.0.2 Platform: Neon OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: kcm_sddm Assignee: plasma-b...@kde.org Reporter: m...@apache.org CC: k...@david-redondo.de, k...@davidedmundson.co.uk Target Milestone: --- Created attachment 167616 --> https://bugs.kde.org/attachment.cgi?id=167616&action=edit /etc/sddm.conf.d/kde_settings.conf SUMMARY After an upgrade from 5.27.10 (4:5.27.10-0xneon+22.04+jammy+release+build28) to 6.0.2 (4:6.0.2-0xneon+22.04+jammy+release+build32) auto-login does not work anymore. So I went to the SDDM settings to enable it again. According to the UI the feature is still enabled though SDDM seems to ignore it. I saw this before and can disable and re-enable the feature to fix this. Last time I did this I accidentially switched from Wayland to X11 though because the drop down list has "Plasma (X11)" instead of "Plasma (Wayland)" selected. I guess that the session was renamed on upgrade and it can't find the old session file anymore. If that happens it should fall back either to the session type which is currently running. I will attach a screenshot and the kde_settings.conf from /etc/sddm.conf.d STEPS TO REPRODUCE 1. Upgrade from 5.x to 6.0.2 2. Notice that Auto Logon does not work anymore 3. Go to KCM to fix it OBSERVED RESULT Session "Plasma (X11)" is preselected even though I am running a Wayland session right now and the kde_settings.conf still has the Session=plasmawayland set. EXPECTED RESULT "Plasma (Wayland)" should be selected. SOFTWARE/OS VERSIONS Operating System: KDE neon 6.0 KDE Plasma Version: 6.0.2 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 This sounds like bug 432018 came back. -- You are receiving this mail because: You are watching all bug changes.
