[frameworks-kio] [Bug 487995] Downloading pdf from Signal Desktop crashes thumbnailer
https://bugs.kde.org/show_bug.cgi?id=487995 --- Comment #5 from Yannik --- The same exact issue happened to me right now - this time on my KDE Plasma 6.1 Desktop PC. This time, I had Signal installed as Snap, so the issue occured once with Flatpak and once with Snap, implying that it is 100% a KDE issue. In my opinion, this is a critical bug. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 487995] New: Downloading pdf from Signal Desktop crashes whole machine. Fatal bug.
https://bugs.kde.org/show_bug.cgi?id=487995 Bug ID: 487995 Summary: Downloading pdf from Signal Desktop crashes whole machine. Fatal bug. Classification: Plasma Product: plasmashell Version: master Platform: Other OS: Other Status: REPORTED Severity: normal Priority: NOR Component: generic-crash Assignee: plasma-b...@kde.org Reporter: yannik.riek...@pm.me Target Milestone: 1.0 Created attachment 170120 --> https://bugs.kde.org/attachment.cgi?id=170120&action=edit Generated Kioworker Crash Log SUMMARY STEPS TO REPRODUCE 1. Open Signal Desktop (tested on Flatpak and Deb installed via PPA; bug is reproducable and happens everytime) 2. Download File 3. Crash OBSERVED RESULT Hundreds of error messages EXPECTED RESULT Just download the file OS: TUXEDO OS 3 x86_64 6.5.0-10040-tuxedo Plasma 6.0.4 ADDITIONAL INFORMATION I got a PDF from a friend. The file is not corrupted and downloads on my Android phone in 1 second and can also be viewed. When I try to download it on Signal Desktop, Plasma sends me hundreds of "Kioworker closed unexpectedly" messages. Even before the file is downloaded, it sends the messages. When I choose the home directory for the download location in Dolphin, it doesn't download. When I chose a different folder like Downloads or Desktop, it downloads. The file has no problem and can be viewed. I downloaded the log and attached it. My system gets very loud and even shut down when this happened the first time. Absolute crazy bug I've never encountered before. -- You are receiving this mail because: You are watching all bug changes.
[frameworks-kio] [Bug 487995] Downloading pdf from Signal Desktop crashes thumbnailer
https://bugs.kde.org/show_bug.cgi?id=487995 --- Comment #2 from Yannik --- Created attachment 170130 --> https://bugs.kde.org/attachment.cgi?id=170130&action=edit coredumpctl gdb -- You are receiving this mail because: You are watching all bug changes.
[frameworks-kio] [Bug 487995] Downloading pdf from Signal Desktop crashes thumbnailer
https://bugs.kde.org/show_bug.cgi?id=487995 --- Comment #3 from Yannik --- (In reply to David Redondo from comment #1) > Thank you for the bug report! Unfortunately I can't reproduce the crash > myself on current git master, and the backtrace is incomplete and missing > debug symbols for the following lines that we need to figure out exactly > what's going wrong: > Could you please install debug symbols and attach a new symbolicated > backtrace generated by using coredumpctl gdb in a terminal window? See > https://community.kde.org/Guidelines_and_HOWTOs/Debugging/ > How_to_create_useful_crash_reports#Retrieving_a_backtrace_using_coredumpctl > for details about how to do this. > Thanks again! I'm not sure if I reported everything you wanted, may you look into the .txt and tell me if I need to do something else? Thanks -- You are receiving this mail because: You are watching all bug changes.
[kdeplasma-addons] [Bug 484389] New: OSD Notification for Caps and Num Lock Change
https://bugs.kde.org/show_bug.cgi?id=484389 Bug ID: 484389 Summary: OSD Notification for Caps and Num Lock Change Classification: Plasma Product: kdeplasma-addons Version: unspecified Platform: Other OS: Other Status: REPORTED Severity: wishlist Priority: NOR Component: General Assignee: plasma-b...@kde.org Reporter: yannik.riek...@pm.me Target Milestone: --- KDE is missing a feature which is available for Windows and GNOME Extension: Displaying an OSD Notification when changing key lock state. Also the (I think included by default) extension "Lock Keys Status 1.0" only shows either NUM or CAPS and can't display both, which is also "unintuitive" if you ask me. So I would implement A) the ability to show both states at the same time (maybe also SCROLL LOCK) on the Tray (Task Manager) as well as having the ability to optionally enable an OSD Notification. Lock Keys GNOME Shell Extension: https://extensions.gnome.org/extension/36/lock-keys/ Windows FOSS App: https://github.com/limbo666/KeyzPal Ihr seid ja meines Erachtens deutsch. Also an dieser Stelle props an KDE und alles Gute. In ein paar Jahren spende ich euch mal 100 Euro :) -- You are receiving this mail because: You are watching all bug changes.
[kdeplasma-addons] [Bug 484390] New: OSD Notification for File Operations
https://bugs.kde.org/show_bug.cgi?id=484390 Bug ID: 484390 Summary: OSD Notification for File Operations Classification: Plasma Product: kdeplasma-addons Version: unspecified Platform: Other OS: Other Status: REPORTED Severity: normal Priority: NOR Component: General Assignee: plasma-b...@kde.org Reporter: yannik.riek...@pm.me Target Milestone: --- KDE is missing a feature which is available via various GNOME Shell Extension Clipboard Managers, like for example the powerful clipboard manager "Pano" but lacking in KDE's native Clipboard Manager: The ability to show a notification when performing a file operation. When you copy a file in GNOME, it can show a notification which simply says "Copied 1 file" or "Cut 1 file", which is pretty handy if you ask me. Check out the extension; you will find quality of life improvements which are lacking in KDE's native Clipboard Manager. https://extensions.gnome.org/extension/5278/pano/ Schönen Tag euch -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 489824] New: Feature Request: "Lock Keys Status" Plasmoid: Add view for both CAPS AND NUM
https://bugs.kde.org/show_bug.cgi?id=489824 Bug ID: 489824 Summary: Feature Request: "Lock Keys Status" Plasmoid: Add view for both CAPS AND NUM Classification: Plasma Product: plasmashell Version: master Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: System Tray Assignee: plasma-b...@kde.org Reporter: yannik.riek...@pm.me CC: mate...@gmail.com Target Milestone: 1.0 In the past, I made a request asking for the implementation of an OSD notification when changing CAPS / NUM states. This, in my opinion, would absolutely still be nice to have, but is not as important because now, the auditive equivalent seems to work by enabling accessibility features (previously broken on Wayland, but now it seems to work on my system). The native Lock Keys Status Plasmoid is pretty bad in my opinion because it doesn't really show both states. When a user enables both CAPS and NUM, there are not even two icons - for me, it even looks like a bug; the icon "merges" into the other when you desire to enable both CAPS and NUM and the same time. By implementing just one tiny change, you could achieve a similar result like GNOME's popular "Lock Keys" extension: Showing the "yes or no" status of the lock state. This is not possible in the current plasmoid. https://github.com/kazysmaster/gnome-shell-extension-lockkeys Thank you very much! *** If you're not sure this is actually a bug, instead post about it at https://discuss.kde.org If you're reporting a crash, attach a backtrace with debug symbols; see https://community.kde.org/Guidelines_and_HOWTOs/Debugging/How_to_create_useful_crash_reports *** SUMMARY STEPS TO REPRODUCE 1. 2. 3. OBSERVED RESULT EXPECTED RESULT SOFTWARE/OS VERSIONS Windows: macOS: Linux/KDE Plasma: (available in About System) KDE Plasma Version: KDE Frameworks Version: Qt Version: ADDITIONAL INFORMATION -- You are receiving this mail because: You are watching all bug changes.
[kdeconnect] [Bug 478769] New: Permission denied for sshfs-mounted filesystem with android 13 / latest kdeconnect app
https://bugs.kde.org/show_bug.cgi?id=478769 Bug ID: 478769 Summary: Permission denied for sshfs-mounted filesystem with android 13 / latest kdeconnect app Classification: Applications Product: kdeconnect Version: unspecified Platform: Android OS: Android 13.x Status: REPORTED Severity: normal Priority: NOR Component: android-application Assignee: albertv...@gmail.com Reporter: yan...@sembritzki.me CC: andrew.g.r.hol...@gmail.com Target Milestone: --- SUMMARY Access of files on a kdeconnect mounted filesystem is broken, resulting in permission denied error. STEPS TO REPRODUCE 1. Do a fresh install of kdeconnect 1.29.0 on android 13 2. Ensure that MANAGE_EXTERNAL_STORAGE permission is granted to kdeconnect app 3. Pair laptop with android device using kdeconnect or gsconnect 4. Mount android filesystem using `sshfs -p 1739 kdeconnect@192.168.1.40:/ -o ssh_command='ssh -i ~/.config/gsconnect/private.pem -o IdentitiesOnly=yes -o PubkeyAcceptedKeyTypes=+ssh-rsa -v' -d -f mountdir` 5. try to list files with `ls mountdir` OBSERVED RESULT `ls mountdir` results in `permission denied` (even when using sudo) We can see from the sshfs command output that the connection is fine: SSHFS version 3.7.3 executing <-i> <~/.config/gsconnect/private.pem> <-o> <-o> <-v> <-x> <-a> <-oClearAllForwardings=yes> <-oPort=1739> <-2> <-s> OpenSSH_9.0p1, OpenSSL 3.0.9 30 May 2023 debug1: Reading configuration data /home/yannik/.ssh/config debug1: /home/yannik/.ssh/config line 1: Applying options for * debug1: Reading configuration data /etc/ssh/ssh_config debug1: Reading configuration data /etc/ssh/ssh_config.d/50-redhat.conf debug1: Reading configuration data /etc/crypto-policies/back-ends/openssh.config debug1: configuration requests final Match pass debug1: re-parsing configuration debug1: Reading configuration data /home/yannik/.ssh/config debug1: /home/yannik/.ssh/config line 1: Applying options for * debug1: Reading configuration data /etc/ssh/ssh_config debug1: Reading configuration data /etc/ssh/ssh_config.d/50-redhat.conf debug1: Reading configuration data /etc/crypto-policies/back-ends/openssh.config debug1: Connecting to 192.168.1.40 [192.168.1.40] port 1739. debug1: Connection established. debug1: identity file /home/yannik/.config/gsconnect/private.pem type -1 debug1: identity file /home/yannik/.config/gsconnect/private.pem-cert type -1 debug1: Local version string SSH-2.0-OpenSSH_9.0 debug1: Remote protocol version 2.0, remote software version SSHD-CORE-0.14.0 debug1: compat_banner: no match: SSHD-CORE-0.14.0 debug1: Authenticating to 192.168.1.40:1739 as 'kdeconnect' debug1: load_hostkeys: fopen /home/yannik/.ssh/known_hosts2: No such file or directory debug1: load_hostkeys: fopen /etc/ssh/ssh_known_hosts: No such file or directory debug1: load_hostkeys: fopen /etc/ssh/ssh_known_hosts2: No such file or directory debug1: SSH2_MSG_KEXINIT sent debug1: SSH2_MSG_KEXINIT received debug1: kex: algorithm: ecdh-sha2-nistp384 debug1: kex: host key algorithm: ecdsa-sha2-nistp256 debug1: kex: server->client cipher: aes256-ctr MAC: hmac-sha2-256 compression: none debug1: kex: client->server cipher: aes256-ctr MAC: hmac-sha2-256 compression: none debug1: kex: ecdh-sha2-nistp384 need=32 dh_need=32 debug1: kex: ecdh-sha2-nistp384 need=32 dh_need=32 debug1: expecting SSH2_MSG_KEX_ECDH_REPLY debug1: SSH2_MSG_KEX_ECDH_REPLY received debug1: Server host key: ecdsa-sha2-nistp256 SHA256:jeQHsA4OYuqtgdzmrUFYWR1wnhyhNyPtH4Ak9p7z8So debug1: load_hostkeys: fopen /home/yannik/.ssh/known_hosts2: No such file or directory debug1: load_hostkeys: fopen /etc/ssh/ssh_known_hosts: No such file or directory debug1: load_hostkeys: fopen /etc/ssh/ssh_known_hosts2: No such file or directory debug1: Host '[192.168.1.40]:1739' is known and matches the ECDSA host key. debug1: Found key in /home/yannik/.ssh/known_hosts:1993 debug1: rekey out after 4294967296 blocks debug1: SSH2_MSG_NEWKEYS sent debug1: expecting SSH2_MSG_NEWKEYS debug1: SSH2_MSG_NEWKEYS received debug1: rekey in after 4294967296 blocks debug1: get_agent_identities: bound agent to hostkey debug1: get_agent_identities: agent returned 5 keys debug1: Will attempt key: /home/yannik/.config/gsconnect/private.pem explicit debug1: SSH2_MSG_SERVICE_ACCEPT received debug1: Authentications that can continue: password,keyboard-interactive,publickey debug1: Next authentication method: publickey debug1: Trying private key: /home/yannik/.config/gsconnect/private.pem Authenticated to 192.168.1.40 ([192.168.1.40]:1739) using "publickey". debug1: pkcs11_del_provider: called, provider_id = (null) debug1: channel 0: new [client-session] debug1: Entering interactive session. debug1: pledge: filesystem debug1: Sending su
[kdeconnect] [Bug 478769] Permission denied for sshfs-mounted filesystem with android 13 / latest kdeconnect app
https://bugs.kde.org/show_bug.cgi?id=478769
--- Comment #1 from Yannik Sembritzki ---
On the android side, I can see the following messages using `adb logcat` when
trying to access files on the mounted filesystem:
12-20 13:33:58.273 15311 15311 W sshd-SftpSubsys: type=1400 audit(0.0:2980):
avc: denied { read } for name="/" dev="dm-2" ino=2
scontext=u:r:untrusted_app:s0:c51,c257,c512,c768 tcontext=u:object_r:rootfs:s0
tclass=dir permissive=0 app=org.kde.kdeconnect_tp
--
You are receiving this mail because:
You are watching all bug changes.
[kdeconnect] [Bug 460927] New: Split up persistent notification into two notification channels for no devices/connected devices
https://bugs.kde.org/show_bug.cgi?id=460927 Bug ID: 460927 Summary: Split up persistent notification into two notification channels for no devices/connected devices Classification: Applications Product: kdeconnect Version: unspecified Platform: Android OS: Android 12.x Status: REPORTED Severity: normal Priority: NOR Component: android-application Assignee: albertv...@gmail.com Reporter: yan...@sembritzki.me Target Milestone: --- Currently, the persistent notification uses one notification channel, called `PERSISTENT`, no matter whether devices are connected or not: https://invent.kde.org/network/kdeconnect-android/-/blob/master/src/org/kde/kdeconnect/BackgroundService.java#L337 This prevents users from choosing to display the notification when devices are connected, and hiding it when no devices are connected. To solve this, it would be nice to split this up into two notification channels. -- You are receiving this mail because: You are watching all bug changes.
[kdeconnect] [Bug 460927] Split up persistent notification into two notification channels for no devices/connected devices
https://bugs.kde.org/show_bug.cgi?id=460927 --- Comment #1 from Yannik Sembritzki --- PR for this: https://invent.kde.org/network/kdeconnect-android/-/merge_requests/299 -- You are receiving this mail because: You are watching all bug changes.
