[kdeconnect] [Bug 494158] File transfer storage fails (KDE Connect Android 1.32.5)
https://bugs.kde.org/show_bug.cgi?id=494158 Albert Vaca Cintora changed: What|Removed |Added Latest Commit||https://invent.kde.org/netw ||ork/kdeconnect-android/-/co ||mmit/551b089d9ae4602df5d251 ||bbe63ccb9de4146748 Resolution|--- |FIXED Status|REPORTED|RESOLVED --- Comment #12 from Albert Vaca Cintora --- Git commit 551b089d9ae4602df5d251bbe63ccb9de4146748 by Albert Vaca Cintora, on behalf of Luca Carlon. Committed on 08/10/2024 at 15:48. Pushed by albertvaka into branch 'master'. Do not use FLAG_MUTABLE when targeting Android >= 34 M +2-2 src/org/kde/kdeconnect/Plugins/SharePlugin/ReceiveNotification.java https://invent.kde.org/network/kdeconnect-android/-/commit/551b089d9ae4602df5d251bbe63ccb9de4146748 -- You are receiving this mail because: You are watching all bug changes.
[kde] [Bug 494088] After September 28th 2024 update to Android KDE-Connect client 1.32.4 - Play Store. It no longer connects to Debian 12 Bookworm host.
https://bugs.kde.org/show_bug.cgi?id=494088 --- Comment #2 from Albert Vaca Cintora --- 1.32.5 sorry -- You are receiving this mail because: You are watching all bug changes.
[kde] [Bug 494088] After September 28th 2024 update to Android KDE-Connect client 1.32.4 - Play Store. It no longer connects to Debian 12 Bookworm host.
https://bugs.kde.org/show_bug.cgi?id=494088 Albert Vaca Cintora changed: What|Removed |Added Status|REPORTED|NEEDSINFO CC||albertv...@gmail.com Resolution|--- |WAITINGFORINFO --- Comment #1 from Albert Vaca Cintora --- Have you tried with Version 1.35.5? It should be fixed. -- You are receiving this mail because: You are watching all bug changes.
[kdeconnect] [Bug 493943] Android app crashes immediately on starting
https://bugs.kde.org/show_bug.cgi?id=493943 Albert Vaca Cintora changed: What|Removed |Added Status|REPORTED|RESOLVED Resolution|--- |FIXED --- Comment #3 from Albert Vaca Cintora --- Indeed the above commit broke the app on Android 14+, this should fix it: https://invent.kde.org/network/kdeconnect-android/-/commit/63d1d15c4fb02dadf0a28ad3358150e14970f94d I'm going to make a new release with the fix. -- You are receiving this mail because: You are watching all bug changes.
[kdeconnect] [Bug 492351] Cannot add trusted networks in v1.32.1 (F-Droid version)
https://bugs.kde.org/show_bug.cgi?id=492351 Albert Vaca Cintora changed: What|Removed |Added Status|REPORTED|RESOLVED Resolution|--- |FIXED -- You are receiving this mail because: You are watching all bug changes.
[kdeconnect] [Bug 492351] Cannot add trusted networks in v1.32.1 (F-Droid version)
https://bugs.kde.org/show_bug.cgi?id=492351 --- Comment #8 from Albert Vaca Cintora --- This was fixed in https://invent.kde.org/network/kdeconnect-android/-/merge_requests/472 I'll release a new version. -- You are receiving this mail because: You are watching all bug changes.
[kdeconnect] [Bug 491722] KDE Connect aplication crashes when entering Presentation remote mode.
https://bugs.kde.org/show_bug.cgi?id=491722 --- Comment #7 from Albert Vaca Cintora --- This has been fixed but Google is rejecting the updates to the Play Store version of the app :( The F-Droid version should have the fix. -- You are receiving this mail because: You are watching all bug changes.
[kdeconnect] [Bug 487438] Add command pop-up broken
https://bugs.kde.org/show_bug.cgi?id=487438 Albert Vaca Cintora changed: What|Removed |Added Status|ASSIGNED|RESOLVED Latest Commit||https://invent.kde.org/netw ||ork/kdeconnect-kde/-/commit ||/19763dbf463cf97f1865166701 ||32e372c70a9f9b Resolution|--- |FIXED --- Comment #3 from Albert Vaca Cintora --- Git commit 19763dbf463cf97f186516670132e372c70a9f9b by Albert Vaca Cintora, on behalf of Christoph Wolk. Committed on 05/08/2024 at 22:06. Pushed by albertvaka into branch 'master'. plugins/runcommand: use Kirigami.Dialog The "Add Command" dialog in the settings for the Run Command plugin looks rather broken at the moment, as the size is not explicitly set and the default value ends up much smaller than the contents. It uses QQC2.Dialog, even though the plugin makes heavy use of Kirigami. Using Kirigami.dialog here would solve the sizing issue, and generally lead to a more consistent interface. This change makes the plugin use Kirigami.Dialog instead of QQC2. M +2-1plugins/runcommand/kdeconnect_runcommand_config.qml https://invent.kde.org/network/kdeconnect-kde/-/commit/19763dbf463cf97f186516670132e372c70a9f9b -- You are receiving this mail because: You are watching all bug changes.
[kdeconnect] [Bug 490306] patch 4f3a8968 not working as intended
https://bugs.kde.org/show_bug.cgi?id=490306 Albert Vaca Cintora changed: What|Removed |Added Status|REPORTED|RESOLVED Resolution|--- |FIXED --- Comment #4 from Albert Vaca Cintora --- This won't work until a new version of the Android app with this patch [1] is released. It might take one or two weeks still (which I assumed was fine given the change on the desktop side isn't officially released yet, if I'm not mistaken). Sorry for the inconvenience. [1] https://invent.kde.org/network/kdeconnect-android/-/merge_requests/451 -- You are receiving this mail because: You are watching all bug changes.
[kdeconnect] [Bug 488585] Shift-Return in KDE Connect SMS inserts newline at the end of field, not at cursor location
https://bugs.kde.org/show_bug.cgi?id=488585 Albert Vaca Cintora changed: What|Removed |Added Latest Commit||https://invent.kde.org/netw ||ork/kdeconnect-kde/-/commit ||/d03e964ed77a980b027e53f5d6 ||534625a9a8218b Resolution|--- |FIXED Status|ASSIGNED|RESOLVED --- Comment #3 from Albert Vaca Cintora --- Git commit d03e964ed77a980b027e53f5d6534625a9a8218b by Albert Vaca Cintora, on behalf of Ryan Frew. Committed on 28/06/2024 at 11:19. Pushed by albertvaka into branch 'master'. Corrected newline inserting when using shift+return while writing SMS messages Shift+return was always inserting newline at the end of the current line of text, ignoring where the cursor was, and not overriding currently selected text M +3-1smsapp/qml/SendingArea.qml https://invent.kde.org/network/kdeconnect-kde/-/commit/d03e964ed77a980b027e53f5d6534625a9a8218b -- You are receiving this mail because: You are watching all bug changes.
[frameworks-kirigami] [Bug 482752] Tab navigation isn't great
https://bugs.kde.org/show_bug.cgi?id=482752 --- Comment #5 from Albert Vaca Cintora --- Created attachment 169079 --> https://bugs.kde.org/attachment.cgi?id=169079&action=edit Screenshot of the kdeconnect Kirigami app The buttons in the attached screenshot are created by Kirigami. In the kdeconnect-app code we just create Kirigami.Actions and Kirigami turns the actions into buttons. Kirigami.Actions can't have KeyNavigation.tab to "fix" (workaround) the ordering problem (because they are abstract, non-graphical elements). If you manage to focus the buttons in the screenshot (you need the mouse for that, but different bug), then they keyboard navigation goes through them right-to-left instead of left-to-right. I haven't found anything we can do on our side to fix that. -- You are receiving this mail because: You are watching all bug changes.
[frameworks-kirigami] [Bug 485073] Kirigami.Action doesn't honor KeyNavigation.tab
https://bugs.kde.org/show_bug.cgi?id=485073
--- Comment #9 from Albert Vaca Cintora ---
It does happen to me. If I open kdeconnect-app, I can only navigate through the
main pane ("Device") on the right. There's no key that moves the focus to the
left pane. Furthermore, if I press 'space' to select one device from the list,
the focus is lost and there's no way to continue navigating with the keyboard
whatsoever.
--
You are receiving this mail because:
You are watching all bug changes.
[frameworks-kirigami] [Bug 485073] Kirigami.Action doesn't honor KeyNavigation.tab
https://bugs.kde.org/show_bug.cgi?id=485073 --- Comment #6 from Albert Vaca Cintora --- High-level issue is that if you try to navigate the app using your keyboard instead of the mouse, it's impossible: tab doesn't circle through all the buttons (it only does within the area you have selected, and in a somewhat unpredictable order) and right/left arrows don't do anything. -- You are receiving this mail because: You are watching all bug changes.
[frameworks-kirigami] [Bug 485073] Kirigami.Action doesn't honor KeyNavigation.tab
https://bugs.kde.org/show_bug.cgi?id=485073 --- Comment #5 from Albert Vaca Cintora --- I linked the code. They are in another Kirigami component, a `Kirigami.ScrollablePage`: https://invent.kde.org/network/kdeconnect-kde/-/blob/master/app/qml/DevicePage.qml?ref_type=heads#L20-49 -- You are receiving this mail because: You are watching all bug changes.
[frameworks-kirigami] [Bug 485073] Kirigami.Action doesn't honor KeyNavigation.tab
https://bugs.kde.org/show_bug.cgi?id=485073 Albert Vaca Cintora changed: What|Removed |Added Status|RESOLVED|REOPENED Resolution|NOT A BUG |--- Ever confirmed|0 |1 --- Comment #3 from Albert Vaca Cintora --- Reopening because in practice Kirigami.Actions do result in buttons and those need a way to be navigated with the keyboard. See my previous comment. -- You are receiving this mail because: You are watching all bug changes.
[kdeconnect] [Bug 472528] KDE Connect crashes when calling the phone and displaying a notification
https://bugs.kde.org/show_bug.cgi?id=472528 Albert Vaca Cintora changed: What|Removed |Added Status|RESOLVED|REOPENED Resolution|FIXED |--- Ever confirmed|0 |1 --- Comment #5 from Albert Vaca Cintora --- Ah, wait, nope. The crash I fixed was on the Android side. This is on the desktop. Reopening. -- You are receiving this mail because: You are watching all bug changes.
[kdeconnect] [Bug 472528] KDE Connect crashes when calling the phone and displaying a notification
https://bugs.kde.org/show_bug.cgi?id=472528 Albert Vaca Cintora changed: What|Removed |Added Status|REPORTED|RESOLVED Resolution|--- |FIXED --- Comment #4 from Albert Vaca Cintora --- This should be fixed in KDE Connect version 1.30.1 for Android, which we just pushed. It might take a couple days for you to get the update, though. Sorry for the inconvenience :( -- You are receiving this mail because: You are watching all bug changes.
[kdeconnect] [Bug 485278] KDE Connect 1.30.0 keeps crashing on my Android phone
https://bugs.kde.org/show_bug.cgi?id=485278 Albert Vaca Cintora changed: What|Removed |Added Status|REPORTED|RESOLVED Resolution|--- |FIXED --- Comment #8 from Albert Vaca Cintora --- This is related to the SMS plugin and should be fixed in KDE Connect version 1.30.1 for Android, please reopen if it still crashes after updating. As a workaround, disabling the plugin should stop the issues. -- You are receiving this mail because: You are watching all bug changes.
[frameworks-kirigami] [Bug 485073] Kirigami.Action doesn't honor KeyNavigation.tab
https://bugs.kde.org/show_bug.cgi?id=485073 --- Comment #2 from Albert Vaca Cintora --- Created attachment 168294 --> https://bugs.kde.org/attachment.cgi?id=168294&action=edit Kirigami.Actions as buttons Fair enough. I still need a way to fix tab navigation, though. In KDE Connect we have 3 Kirigami.Action [1] that end up as buttons on the top bar (see screenshot). Tab navigation circles through them backwards. How do I fix that? [1] https://invent.kde.org/network/kdeconnect-kde/-/blob/master/app/qml/DevicePage.qml?ref_type=heads#L20-49 -- You are receiving this mail because: You are watching all bug changes.
[frameworks-kirigami] [Bug 485073] New: Kirigami.Action doesn't honor KeyNavigation.tab
https://bugs.kde.org/show_bug.cgi?id=485073 Bug ID: 485073 Summary: Kirigami.Action doesn't honor KeyNavigation.tab Classification: Frameworks and Libraries Product: frameworks-kirigami Version: unspecified Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: kdelibs-b...@kde.org Reporter: albertv...@gmail.com CC: m...@ratijas.tk, notm...@gmail.com Target Milestone: Not decided Context: I'm trying to fix the fact that pressing "tab" in the KDE Connect app walks the buttons backwards. I originally reported this in https://bugs.kde.org/show_bug.cgi?id=482752 but was told that this should be fixed per-app and not in Kirigami. I found that Qt supports KeyNavigation.tab [1] to indicate, for each element, which is the next element to be selected when tab is pressed, together with KeyNavigation.right and KeyNavigation.left for the arrow keys. Although I still think that tab navigation should work out of the box, KeyNavigation seemed like a way to (with a bit of hardcoding) fix it for KDE Connect at least. However, when I tried it, I found that KeyNavigation.tab makes no difference when I use it in a Kirigami.Action. Does Kirigami.Action not support KeyNavigation.tab? [1] https://doc.qt.io/qt-6.5/qml-qtquick-keynavigation.html#tab-attached-prop -- You are receiving this mail because: You are watching all bug changes.
[kdeconnect] [Bug 472395] Changing the volume doesn't work outside of the media player screen
https://bugs.kde.org/show_bug.cgi?id=472395 Albert Vaca Cintora changed: What|Removed |Added Ever confirmed|0 |1 Summary|functions that worked |Changing the volume doesn't |before are now not working |work outside of the media |anymore.|player screen Status|REPORTED|CONFIRMED --- Comment #1 from Albert Vaca Cintora --- I can confirm that changing the volume doesn't work outside of the media player screen. Ring my phone seems to work fine for me, at least on Android 13. -- You are receiving this mail because: You are watching all bug changes.
[kdeconnect] [Bug 476551] Clipboard is sent to phone when reconnecting after disabling clipboard autoshare
https://bugs.kde.org/show_bug.cgi?id=476551 Albert Vaca Cintora changed: What|Removed |Added Status|ASSIGNED|RESOLVED Resolution|--- |FIXED Latest Commit||https://invent.kde.org/netw ||ork/kdeconnect-kde/-/commit ||/642c99056837053d943aa04ebd ||6a487c25d2bd56 --- Comment #8 from Albert Vaca Cintora --- Git commit 642c99056837053d943aa04ebd6a487c25d2bd56 by Albert Vaca Cintora, on behalf of Marx Zhu. Committed on 31/03/2024 at 14:48. Pushed by albertvaka into branch 'master'. fix: do not send NetworkPacket if autoshare is disabled when connecting M +8-1plugins/clipboard/clipboardplugin.cpp https://invent.kde.org/network/kdeconnect-kde/-/commit/642c99056837053d943aa04ebd6a487c25d2bd56 -- You are receiving this mail because: You are watching all bug changes.
[frameworks-kirigami] [Bug 482752] Tab navigation isn't great
https://bugs.kde.org/show_bug.cgi?id=482752 Albert Vaca Cintora changed: What|Removed |Added Target Milestone|--- |Not decided Component|messaging-application |general Product|kdeconnect |frameworks-kirigami Assignee|si...@ergotech.com |kdelibs-b...@kde.org --- Comment #2 from Albert Vaca Cintora --- I don't think those can be fixed in KDE Connect, we don't have any way to affect the behavior of tabbing through elements... it need to be fixed in Kirigami or Qt, so I'm bouncing it back to Kirigami and if Qt folks need to get involved I think this should happen from a Kirigami perspective. However, at the very least the issue of selected items not being visually highlighted should be 100% solvable within Kirigami. I also found this issue had been reported in the past already [1] so sorry for the dupe. [1] https://bugs.kde.org/show_bug.cgi?id=475093 -- You are receiving this mail because: You are watching all bug changes.
[frameworks-kirigami] [Bug 482753] PlaceholderMessage isn't accessible (eg: using a screen reader)
https://bugs.kde.org/show_bug.cgi?id=482753 --- Comment #4 from Albert Vaca Cintora --- > And if they don't or can't, they should have Accessible.name set instead. Yeah, the bug is about Accessible.name not being honored. -- You are receiving this mail because: You are watching all bug changes.
[frameworks-kirigami] [Bug 482753] New: Kirigami isn't accessible (eg: using a screen reader)
https://bugs.kde.org/show_bug.cgi?id=482753 Bug ID: 482753 Summary: Kirigami isn't accessible (eg: using a screen reader) Classification: Frameworks and Libraries Product: frameworks-kirigami Version: Master Platform: Other OS: Other Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: kdelibs-b...@kde.org Reporter: albertv...@gmail.com CC: m...@ratijas.tk, notm...@gmail.com Target Milestone: Not decided - `Kirigami.PlaceholderMessage` content isn't read by screen readers - `Kirigami.Action` that don't have a text property don't use the `Accessible.name` property when using a screen reader. STEPS TO REPRODUCE Can be seen in the kdeconnect-app when using a screen reader. Code for the app can be found here: https://github.com/KDE/kdeconnect-kde/blob/master/app/qml/ -- You are receiving this mail because: You are watching all bug changes.
[frameworks-kirigami] [Bug 482752] New: Tab navigation in Kirigami is unintuitive and has no visual feedback
https://bugs.kde.org/show_bug.cgi?id=482752 Bug ID: 482752 Summary: Tab navigation in Kirigami is unintuitive and has no visual feedback Classification: Frameworks and Libraries Product: frameworks-kirigami Version: Master Platform: Other OS: Other Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: kdelibs-b...@kde.org Reporter: albertv...@gmail.com CC: m...@ratijas.tk, notm...@gmail.com Target Milestone: Not decided Somehow pressing "tab" in a kririgami app iterates through buttons right to left. Furthermore, Tab doesn't iterate through all items on the Window, just the current selected view (eg: you can't jump to a sidebar from the main content). Furthermore, in many elements there's no visual indication that they are selected at all. STEPS TO REPRODUCE Can be seen in kdeconnect-app: - The buttons on the top right are selected right to left instead of left to right. - The elements in the sidebar can't be selected if you are on the main content (tabbing never gets to them). - The elements on the sidebar don't have visual indication when they are selected. - I also think "Enter" doesn't work to "click" on something and you need to press Space instead. KDE Connect app code is here: https://github.com/KDE/kdeconnect-kde/blob/master/app/qml/ -- You are receiving this mail because: You are watching all bug changes.
[kdeconnect] [Bug 482199] KCM header appearance is broken
https://bugs.kde.org/show_bug.cgi?id=482199 Albert Vaca Cintora changed: What|Removed |Added Resolution|--- |FIXED Status|ASSIGNED|RESOLVED Latest Commit||https://invent.kde.org/netw ||ork/kdeconnect-kde/-/commit ||/1785160049b29f3be6c729e344 ||774afab2f26928 --- Comment #6 from Albert Vaca Cintora --- Git commit 1785160049b29f3be6c729e344774afab2f26928 by Albert Vaca Cintora, on behalf of Nicolas Fella. Committed on 06/03/2024 at 22:03. Pushed by albertvaka into branch 'master'. [kcm] Use correct KCModule constructor Related: bug 478091 M +2-2kcm/kcm.cpp M +1-1kcm/kcm.h https://invent.kde.org/network/kdeconnect-kde/-/commit/1785160049b29f3be6c729e344774afab2f26928 -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 478091] Does not remove previous KCM header when switching to certain QtWidgets KCMs (KDE Connect KCM, Digital Camera)
https://bugs.kde.org/show_bug.cgi?id=478091 --- Comment #8 from Albert Vaca Cintora --- Git commit 1785160049b29f3be6c729e344774afab2f26928 by Albert Vaca Cintora, on behalf of Nicolas Fella. Committed on 06/03/2024 at 22:03. Pushed by albertvaka into branch 'master'. [kcm] Use correct KCModule constructor Related: bug 482199 M +2-2kcm/kcm.cpp M +1-1kcm/kcm.h https://invent.kde.org/network/kdeconnect-kde/-/commit/1785160049b29f3be6c729e344774afab2f26928 -- You are receiving this mail because: You are watching all bug changes.
[kdeconnect] [Bug 456517] 2 finger gesture scrolls too much
https://bugs.kde.org/show_bug.cgi?id=456517 Albert Vaca Cintora changed: What|Removed |Added Status|REPORTED|RESOLVED Resolution|--- |DUPLICATE --- Comment #2 from Albert Vaca Cintora --- *** This bug has been marked as a duplicate of bug 407293 *** -- You are receiving this mail because: You are watching all bug changes.
[kdeconnect] [Bug 407293] Remote input plugin's scrolling speed is too fast, can't be adjusted
https://bugs.kde.org/show_bug.cgi?id=407293 Albert Vaca Cintora changed: What|Removed |Added CC||alexban...@gmail.com --- Comment #3 from Albert Vaca Cintora --- *** Bug 456517 has been marked as a duplicate of this bug. *** -- You are receiving this mail because: You are watching all bug changes.
