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=edit
Screenshot of the kdeconnect Kirigami app
The buttons in the attached screenshot are created by Kirigami. In the
kdeconn
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 pr
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
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
https://bugs.kde.org/show_bug.cgi?id=485073
Albert Vaca Cintora changed:
What|Removed |Added
Status|RESOLVED|REOPENED
Resolution|NOT A BUG
https://bugs.kde.org/show_bug.cgi?id=472528
Albert Vaca Cintora changed:
What|Removed |Added
Status|RESOLVED|REOPENED
Resolution|FIXED
https://bugs.kde.org/show_bug.cgi?id=472528
Albert Vaca Cintora changed:
What|Removed |Added
Status|REPORTED|RESOLVED
Resolution
https://bugs.kde.org/show_bug.cgi?id=485278
Albert Vaca Cintora changed:
What|Removed |Added
Status|REPORTED|RESOLVED
Resolution
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=edit
Kirigami.Actions as buttons
Fair enough. I still need a way to fix tab navigation, though. In KDE Connect
we hav
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
https://bugs.kde.org/show_bug.cgi?id=472395
Albert Vaca Cintora changed:
What|Removed |Added
Ever confirmed|0 |1
Summary|functions
https://bugs.kde.org/show_bug.cgi?id=476551
Albert Vaca Cintora changed:
What|Removed |Added
Status|ASSIGNED|RESOLVED
Resolution
https://bugs.kde.org/show_bug.cgi?id=482752
Albert Vaca Cintora changed:
What|Removed |Added
Target Milestone|--- |Not decided
Component|messaging
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
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
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
https://bugs.kde.org/show_bug.cgi?id=482199
Albert Vaca Cintora changed:
What|Removed |Added
Resolution|--- |FIXED
Status|ASSIGNED
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
https://bugs.kde.org/show_bug.cgi?id=456517
Albert Vaca Cintora changed:
What|Removed |Added
Status|REPORTED|RESOLVED
Resolution
https://bugs.kde.org/show_bug.cgi?id=407293
Albert Vaca Cintora changed:
What|Removed |Added
CC||alexban...@gmail.com
--- Comment #3 from
https://bugs.kde.org/show_bug.cgi?id=480165
--- Comment #1 from Albert Vaca ---
Created attachment 165130
--> https://bugs.kde.org/attachment.cgi?id=165130=edit
Rename dialog
--
You are receiving this mail because:
You are watching all bug changes.
https://bugs.kde.org/show_bug.cgi?id=480165
Bug ID: 480165
Summary: When copying a folder to ExFAT with a name that has
unsupported characters, Dolphin suggests to rename it
but then fails to copy the contents
Classification:
https://bugs.kde.org/show_bug.cgi?id=407293
Albert Vaca changed:
What|Removed |Added
Latest Commit||https://invent.kde.org/netw
https://bugs.kde.org/show_bug.cgi?id=443155
--- Comment #43 from Albert Vaca ---
I've modified GSConnect to use ECDSA and it doesn't seem to fix the issue.
Here's my change:
https://github.com/albertvaka/gnome-shell-extension-gsconnect/compare/main...ecdsa-keys
After applying this change I
https://bugs.kde.org/show_bug.cgi?id=475795
--- Comment #2 from Albert Vaca ---
We should give a better error in these cases.
--
You are receiving this mail because:
You are watching all bug changes.
https://bugs.kde.org/show_bug.cgi?id=475960
--- Comment #3 from Albert Vaca ---
*with kdeconnect installed from a packet from your distribution I mean
--
You are receiving this mail because:
You are watching all bug changes.
https://bugs.kde.org/show_bug.cgi?id=475960
--- Comment #2 from Albert Vaca ---
Have you maybe ever built kdeconnect from sources and mixed that with packets
from your distribution? It seems it's failing to load some plugin for some
reason, which could be a version mismatch.
--
You
https://bugs.kde.org/show_bug.cgi?id=443155
--- Comment #41 from Albert Vaca ---
I'm out of ideas, the only alternative is to upgrade the version of mina-sshd
that we use (which doesn't seem easy).
--
You are receiving this mail because:
You are watching all bug changes.
https://bugs.kde.org/show_bug.cgi?id=443155
--- Comment #40 from Albert Vaca ---
I added rsa-sha2-256 but I think it still didn't fix the issue:
https://invent.kde.org/network/kdeconnect-android/-/merge_requests/401
--
You are receiving this mail because:
You are watching all bug changes.
https://bugs.kde.org/show_bug.cgi?id=443155
--- Comment #38 from Albert Vaca ---
Thanks for the insight, Lukáš!
This change might do the trick:
https://invent.kde.org/network/kdeconnect-android/-/commit/4f44aef5f8bee8603d08cab18decae70f618faa4
Can you please give it a test? You should be able
https://bugs.kde.org/show_bug.cgi?id=443155
--- Comment #35 from Albert Vaca ---
If I'm not mistaken this should be fixed in the Android app version 1.29.0.
However, the fix only applies to new installs, so if you have an existing
version of the Android app installed you will have to use "
https://bugs.kde.org/show_bug.cgi?id=461872
Albert Vaca changed:
What|Removed |Added
Latest Commit|https://invent.kde.org/netw |https://invent.kde.org/netw
https://bugs.kde.org/show_bug.cgi?id=461872
Albert Vaca changed:
What|Removed |Added
Status|REPORTED|RESOLVED
Resolution
https://bugs.kde.org/show_bug.cgi?id=472697
--- Comment #12 from Albert Vaca ---
This missed 23.08.1 and will be in 23.08.2
--
You are receiving this mail because:
You are watching all bug changes.
https://bugs.kde.org/show_bug.cgi?id=407289
Albert Vaca changed:
What|Removed |Added
Status|REOPENED|RESOLVED
Resolution
https://bugs.kde.org/show_bug.cgi?id=474601
Albert Vaca changed:
What|Removed |Added
Resolution|--- |NOT A BUG
Status|REPORTED
https://bugs.kde.org/show_bug.cgi?id=461872
--- Comment #15 from Albert Vaca ---
*** Bug 466416 has been marked as a duplicate of this bug. ***
--
You are receiving this mail because:
You are watching all bug changes.
https://bugs.kde.org/show_bug.cgi?id=466416
Albert Vaca changed:
What|Removed |Added
Status|CONFIRMED |RESOLVED
Resolution
https://bugs.kde.org/show_bug.cgi?id=474552
--- Comment #2 from Albert Vaca ---
Thanks Kai <3
--
You are receiving this mail because:
You are watching all bug changes.
https://bugs.kde.org/show_bug.cgi?id=474552
Albert Vaca changed:
What|Removed |Added
Resolution|--- |FIXED
Latest Commit
https://bugs.kde.org/show_bug.cgi?id=474121
Albert Vaca changed:
What|Removed |Added
Resolution|--- |FIXED
Status|CONFIRMED
https://bugs.kde.org/show_bug.cgi?id=461872
--- Comment #13 from Albert Vaca ---
Good catch! I think we can fix this by adding a version of this function that
doesn't skip hidden entries... I'll take a look.
--
You are receiving this mail because:
You are watching all bug changes.
https://bugs.kde.org/show_bug.cgi?id=461872
--- Comment #9 from Albert Vaca ---
Before adding an item to the menu, we check if any items for the same device ID
exists and we remove them, so I don't see how this could happen.
For reference, here's the code in 23.08 and in master (it has changed
https://bugs.kde.org/show_bug.cgi?id=461872
--- Comment #7 from Albert Vaca ---
I still can't reproduce it with your steps. When the phone stops being
available from the computer, the entry disappears for me. Are you on KDE
Connect 23.08? If not, can you try there? Maybe it has been fixed
https://bugs.kde.org/show_bug.cgi?id=472697
Albert Vaca changed:
What|Removed |Added
Latest Commit|https://invent.kde.org/netw |https://invent.kde.org/netw
https://bugs.kde.org/show_bug.cgi?id=472697
Albert Vaca changed:
What|Removed |Added
Status|ASSIGNED|RESOLVED
Resolution
https://bugs.kde.org/show_bug.cgi?id=461872
--- Comment #5 from Albert Vaca ---
Does this happen even without unpairing/repairing the device? We shouldn't
create more than one entry for the same device, and I can't reproduce this.
--
You are receiving this mail because:
You are watching all
https://bugs.kde.org/show_bug.cgi?id=433051
Albert Vaca changed:
What|Removed |Added
Status|ASSIGNED|RESOLVED
Resolution
https://bugs.kde.org/show_bug.cgi?id=474121
--- Comment #3 from Albert Vaca ---
I thought KItinerary was using the plugin programmatically, but I checked the
code and it isn't. So there's really no tie with it: KItinerary users can still
take a photo + share instead.
--
You are receiving
https://bugs.kde.org/show_bug.cgi?id=474121
Albert Vaca changed:
What|Removed |Added
Status|REPORTED|CONFIRMED
Ever confirmed|0
https://bugs.kde.org/show_bug.cgi?id=473511
--- Comment #10 from Albert Vaca ---
No, this change is specific for Windows. In Arch it should work fine (I use
Arch) with the latest version of kdeconnect. Open a separate issue if it
doesn't.
--
You are receiving this mail because:
You
https://bugs.kde.org/show_bug.cgi?id=469405
Albert Vaca changed:
What|Removed |Added
Resolution|--- |UPSTREAM
Status|REPORTED
https://bugs.kde.org/show_bug.cgi?id=472697
--- Comment #6 from Albert Vaca ---
Thanks Ilia, that's the commit while the file was fixed and thus started to
work as intended (which seems to be problematic). I'm going to remove this
feature until we find a way to do this without causing
https://bugs.kde.org/show_bug.cgi?id=473956
Albert Vaca changed:
What|Removed |Added
Latest Commit|https://invent.kde.org/netw |https://invent.kde.org/netw
https://bugs.kde.org/show_bug.cgi?id=473956
Albert Vaca changed:
What|Removed |Added
Latest Commit||https://invent.kde.org/netw
https://bugs.kde.org/show_bug.cgi?id=470085
Albert Vaca changed:
What|Removed |Added
Status|ASSIGNED|RESOLVED
Resolution
https://bugs.kde.org/show_bug.cgi?id=473956
Albert Vaca changed:
What|Removed |Added
Status|ASSIGNED|RESOLVED
Resolution
https://bugs.kde.org/show_bug.cgi?id=473511
--- Comment #7 from Albert Vaca ---
I just pushed a fix for this. The fix is on the desktop side, so it will have
to wait until the next release for Windows to be available to users. Sorry for
having this broken for so long and thanks for all the info
https://bugs.kde.org/show_bug.cgi?id=473511
Albert Vaca changed:
What|Removed |Added
Status|REPORTED|RESOLVED
Latest Commit
https://bugs.kde.org/show_bug.cgi?id=408508
Albert Vaca changed:
What|Removed |Added
Status|NEEDSINFO |RESOLVED
--- Comment #6 from Albert Vaca ---
We
https://bugs.kde.org/show_bug.cgi?id=473659
Albert Vaca changed:
What|Removed |Added
Resolution|--- |NOT A BUG
Status|REPORTED
https://bugs.kde.org/show_bug.cgi?id=471879
Albert Vaca changed:
What|Removed |Added
Resolution|--- |DUPLICATE
Status|REPORTED
https://bugs.kde.org/show_bug.cgi?id=445511
Albert Vaca changed:
What|Removed |Added
CC||daeng...@gmail.com
--- Comment #1 from Albert
https://bugs.kde.org/show_bug.cgi?id=459573
--- Comment #7 from Albert Vaca ---
Does removing the configuration (from ~/.config/kdeconnect) fix this for you?
--
You are receiving this mail because:
You are watching all bug changes.
https://bugs.kde.org/show_bug.cgi?id=470085
--- Comment #6 from Albert Vaca ---
Maybe a cleaner alternative to passing the Network to the sendUdpIdentityPacket
function would be to use bindProcessToNetwork in the networkChange callback,
which should affect all the sockets that are created from
https://bugs.kde.org/show_bug.cgi?id=470085
--- Comment #5 from Albert Vaca ---
The issue described by Pedro where we would create two sockets and that would
cause a race condition where neither connection works should be fixed by this
commit:
https://invent.kde.org/network/kdeconnect-android
https://bugs.kde.org/show_bug.cgi?id=473511
--- Comment #1 from Albert Vaca ---
This is probably the change that affects you:
https://invent.kde.org/network/kdeconnect-android/-/commit/1ba9e59872e811615a152882469e9b9f07cc7001
What we are doing since this change is request permissions to have
https://bugs.kde.org/show_bug.cgi?id=472920
--- Comment #1 from Albert Vaca ---
Are you unpairing the device each time? If you don't unpair, the settings are
not deleted.
--
You are receiving this mail because:
You are watching all bug changes.
https://bugs.kde.org/show_bug.cgi?id=411750
Albert Vaca changed:
What|Removed |Added
Status|REPORTED|RESOLVED
Resolution
https://bugs.kde.org/show_bug.cgi?id=446337
Albert Vaca changed:
What|Removed |Added
Status|ASSIGNED|RESOLVED
Latest Commit
https://bugs.kde.org/show_bug.cgi?id=460458
Albert Vaca changed:
What|Removed |Added
Resolution|--- |FIXED
Status|REPORTED
https://bugs.kde.org/show_bug.cgi?id=466088
Albert Vaca changed:
What|Removed |Added
Status|REPORTED|RESOLVED
Resolution
https://bugs.kde.org/show_bug.cgi?id=460448
Albert Vaca changed:
What|Removed |Added
Resolution|--- |FIXED
Status|REPORTED
https://bugs.kde.org/show_bug.cgi?id=465136
Albert Vaca changed:
What|Removed |Added
Resolution|--- |NOT A BUG
Status|REPORTED
https://bugs.kde.org/show_bug.cgi?id=356914
Albert Vaca changed:
What|Removed |Added
Status|REPORTED|RESOLVED
Resolution
https://bugs.kde.org/show_bug.cgi?id=442169
Albert Vaca changed:
What|Removed |Added
Resolution|--- |FIXED
Status|REPORTED
https://bugs.kde.org/show_bug.cgi?id=472276
Albert Vaca changed:
What|Removed |Added
Resolution|--- |WAITINGFORINFO
Status|REPORTED
https://bugs.kde.org/show_bug.cgi?id=472276
--- Comment #2 from Albert Vaca ---
Let me know if that fixes it.
--
You are receiving this mail because:
You are watching all bug changes.
https://bugs.kde.org/show_bug.cgi?id=472276
--- Comment #1 from Albert Vaca ---
Can you delete the config files from ~/.config/kdeconnect and try again?
--
You are receiving this mail because:
You are watching all bug changes.
https://bugs.kde.org/show_bug.cgi?id=472287
Albert Vaca changed:
What|Removed |Added
Status|REPORTED|RESOLVED
Resolution
https://bugs.kde.org/show_bug.cgi?id=471066
Albert Vaca changed:
What|Removed |Added
Status|REPORTED|RESOLVED
Resolution
https://bugs.kde.org/show_bug.cgi?id=471271
Albert Vaca changed:
What|Removed |Added
Status|REPORTED|RESOLVED
Resolution
https://bugs.kde.org/show_bug.cgi?id=471271
--- Comment #1 from Albert Vaca ---
It looks like an infinite loop, because you get lots of log lines in a short
amount of time. I recently fixed a bug of this kind in
https://invent.kde.org/network/kdeconnect-android/-/commit
https://bugs.kde.org/show_bug.cgi?id=471233
Albert Vaca changed:
What|Removed |Added
Resolution|--- |FIXED
Status|CONFIRMED
https://bugs.kde.org/show_bug.cgi?id=424912
--- Comment #3 from Albert Vaca ---
Does this happen when using the "browse filesystem" option or the "share file"
option? Does it happen only when sharing from phone -> PC? Which version of the
Android app are you using?
https://bugs.kde.org/show_bug.cgi?id=471066
Albert Vaca changed:
What|Removed |Added
Resolution|--- |WAITINGFORINFO
Status|REPORTED
https://bugs.kde.org/show_bug.cgi?id=469877
Albert Vaca changed:
What|Removed |Added
Resolution|--- |FIXED
Status|ASSIGNED
https://bugs.kde.org/show_bug.cgi?id=469895
Albert Vaca changed:
What|Removed |Added
Latest Commit||https://invent.kde.org/plas
https://bugs.kde.org/show_bug.cgi?id=470078
Albert Vaca changed:
What|Removed |Added
Latest Commit||https://invent.kde.org/netw
https://bugs.kde.org/show_bug.cgi?id=470231
--- Comment #1 from Albert Vaca ---
Google didn't let us publish the app anymore with that usage of the
accessibility permission. I tried reaching out to Google to understand why but
failed (I just got generic "this is not allowed" respo
https://bugs.kde.org/show_bug.cgi?id=470214
Albert Vaca changed:
What|Removed |Added
Assignee|albertv...@gmail.com|unassigned-b...@kde.org
Component
https://bugs.kde.org/show_bug.cgi?id=469895
--- Comment #8 from Albert Vaca ---
Related issue about supporting multiple brightness backends:
https://invent.kde.org/plasma/powerdevil/-/issues/19
--
You are receiving this mail because:
You are watching all bug changes.
https://bugs.kde.org/show_bug.cgi?id=449263
Albert Vaca changed:
What|Removed |Added
CC||albertv...@gmail.com
--- Comment #2 from Albert
https://bugs.kde.org/show_bug.cgi?id=469895
--- Comment #7 from Albert Vaca ---
I'm the one who enabled compiling with libddc by default. I think it's a great
feature to be able to control your monitor brightness from Plasma instead of
having to use the wonky built-in buttons, and would be nice
https://bugs.kde.org/show_bug.cgi?id=468894
--- Comment #2 from Albert Vaca ---
Happy to hear it's resolved. There were a ton of fixes and changes by different
people in this last release, so it might very well be the update :)
--
You are receiving this mail because:
You are watching all bug
https://bugs.kde.org/show_bug.cgi?id=468924
Albert Vaca changed:
What|Removed |Added
Resolution|--- |NOT A BUG
Status|REPORTED
https://bugs.kde.org/show_bug.cgi?id=446337
Albert Vaca changed:
What|Removed |Added
Keywords||junior-jobs
--
You are receiving this mail
https://bugs.kde.org/show_bug.cgi?id=446337
--- Comment #2 from Albert Vaca ---
The standalone window is there so we can use the KCM on Windows, MacOS,
Gnome... I'm not against opening System Settings as long as we have a check to
only do it when running Plasma.
--
You are receiving this mail
https://bugs.kde.org/show_bug.cgi?id=468326
Albert Vaca changed:
What|Removed |Added
Status|NEEDSINFO |RESOLVED
Resolution|WAITINGFORINFO
https://bugs.kde.org/show_bug.cgi?id=446349
Albert Vaca changed:
What|Removed |Added
Status|REPORTED|RESOLVED
Latest Commit
1 - 100 of 489 matches
Mail list logo
