SUMMARY *** NOTE: If you are reporting a crash, please try to attach a backtrace with debug symbols. See https://community.kde.org/Guidelines_and_HOWTOs/Debugging/How_to_create_useful_crash_reports *** STEPS TO REPRODUCE 1. I'm not sure how/when the folder ~/.local/share/kpeoplevcard appeared OBSERVED RESULT Some file name in that folder have overly long and weird-looking names ("*..vcf.*"), such as: 2519e0b5c67c7-f51d-46fc-9482-cad4b4b5df93..vcf.2399r984-32423A403A32.vcf 2519e0b23619b-f30a-4131-9640-bfbc5d696e53..vcf.2399r1049-3A4E422A32403A4E422A32402A4C4C2A502C3A.2399r1257-3A4E422A32402A4C4C2A502C3A.3954r1259-3A4E422A32402A4C4C2A502C3A.vcf 2519e0b0d773a-da41-41c1-ab67-cdd2d2247d89..vcf.2399r966-304C3C3244443A34324C3E2A5234403A4436.vcf 2519e0ae52add-8052-45ab-b219-dfe477a28adc..vcf.vcf I realized that when my backup tool (Back In Time) choked on overly long filenames. EXPECTED RESULT I don't really know, but I guess that "2519e0b23619b-f30a-4131-9640-bfbc5d696e53..vcf.2399r1049-3A4E422A32403A4E422A32402A4C4C2A502C3A.2399r1257-3A4E422A32402A4C4C2A502C3A.3954r1259-3A4E422A32402A4C4C2A502C3A.vcf" should be named "2519e0b23619b-f30a-4131-9640-bfbc5d696e53.vcf" or something SOFTWARE/OS VERSIONS Linux Mint 21 (Cinnamon desktop) ADDITIONAL INFORMATION Package: kdeconnect Version: 21.12.3-0ubuntu1 Priority: optional Section: universe/kde Origin: Ubuntu Maintainer: Ubuntu Developers <ubuntu-devel-discuss@lists.ubuntu.com> Original-Maintainer: Debian Qt/KDE Maintainers <debian-qt-kde@lists.debian.org> Bugs: https://bugs.launchpad.net/ubuntu/+filebug
I'm seeing this too. We are receiving these weird names as ids from the Android side, so the desktop code seems to work as expected. @Simon any idea what's going on here?
That said I'm not sure whether this is actually a bug or just the ids we get from Android
How can I help troubleshoot this? Due to those overly long names, Back In Time fails everytime (and since I use anacron, it restarts every 15 minutes, shredding my backup disk…).
What phone brand and model do you use? As Nico says, the desktop code just uses the random id given by Android. I don't see any repeated strings in your examples so I don't think it's a matter of the name being repeated, I'd guess Android really is handing over super strange strings. In reality, my best suggestion is to just exclude this directory from your backup. IMO it doesn't have much value to back up anyway since you always have the live version on your phone (so already two copies) and there are better ways to backup contacts (some way which includes the ability to restore them, for instance).
I'm using a Samsung Galaxy S9 with /e/OS 1.4 (Android 10) running KDE Connect 1.19.1 (from F-Droid). Thanks for the hint about excluding that directory, it should definitely do the trick. What's strange is that this behaviour is new : I've been using the same setup (PC + phone + KDE Connect + Back In Time) for years, and only recently started to have that issue. 🤔
Dear Bug Submitter, This bug has been in NEEDSINFO status with no change for at least 15 days. Please provide the requested information as soon as possible and set the bug status as REPORTED. Due to regular bug tracker maintenance, if the bug is still in NEEDSINFO status with no change in 30 days the bug will be closed as RESOLVED > WORKSFORME due to lack of needed information. For more information about our bug triaging procedures please read the wiki located here: https://community.kde.org/Guidelines_and_HOWTOs/Bug_triaging If you have already provided the requested information, please mark the bug as REPORTED so that the KDE team knows that the bug is ready to be confirmed. Thank you for helping us make KDE software even better for everyone!
(In reply to breversa from comment #3) > Due to those overly long names, Back In Time fails everytime (and since I > use anacron, it restarts every 15 minutes, shredding my backup disk…). That sounds like a serious problem with your tool. it should not fail just because a file has a somewhat long name
I don't think "kdeconnect creates files with long names" is a bug, so I'll close this. As a workaround, you can disable the "contacts synchronizer" plugin so we don't create those files.