[kdeconnect] [Bug 486761] Stop spam SMS messages shown in main list
https://bugs.kde.org/show_bug.cgi?id=486761 Simon Redman changed: What|Removed |Added Ever confirmed|0 |1 Status|REPORTED|CONFIRMED --- Comment #1 from Simon Redman --- To be very picky, this is not true (to my knowledge) (In reply to Justin Zobel from comment #0) > Android has a way to filter out spam messages ... Google Messages (and presumably other apps) have a way of filtering out spam messages. As far as I can tell, this is 100% handled at the application layer, so there is no way we can get the information by calling system APIs. If someone knows otherwise, please share the doc links, etc. Marking this bug as confirmed, since it is true that KDE Connect does not filter spam messages and ideally should. -- You are receiving this mail because: You are watching all bug changes.
[kdeconnect] [Bug 468105] Desktop displays deleted messages
https://bugs.kde.org/show_bug.cgi?id=468105 --- Comment #6 from Simon Redman --- (In reply to MikMak from comment #5) > @simon sorry for the mood of my comment it was not appropriate and I was > indeed surprised that the incident had not received a response. > I do try to reply to every bug report. It's not nice when someone goes to the effort to file a report and doesn't get a reply. > I do understand it's not easy, it's an open source project and we have to > accept that not everything is perfect. I apologize for that. > Thanks. Apology accepted. > In fact I looked how I could contribute to your project, and I will be happy > to do this. But I am not sure I could help. I am on nixos, don't use KDE, > etc... But I would really like to help for this project. > Feel free to join us on Matrix and talk about how you could help. To take this example, a distro-agnostic project could be to add support for hiding archived messages in the KDE Connect Android app. https://matrix.to/#/!KPnlFCXuKzRXyhSxnY:kde.org?via=matrix.org=kde.org=mozilla.org > Anyway, I deleted the archived messages on my phone and after a while, not > immediately, kdeconnect no longer displayed the messages. Good to hear! -- You are receiving this mail because: You are watching all bug changes.
[kdeconnect] [Bug 468105] Desktop displays deleted messages
https://bugs.kde.org/show_bug.cgi?id=468105 Simon Redman changed: What|Removed |Added Status|REPORTED|NEEDSINFO Resolution|--- |WAITINGFORINFO --- Comment #4 from Simon Redman --- @biscotty666, sorry for no reply @MikMak it would be nice if there were enough engineer-hours to make the application perfect. If you or someone you know wants to get involved, I would be happy to help them onboard. The KDE Connect SMS plugin reads directly from the phone's database of messages and doesn't do any persistent caching/etc. if you see messages on you computer, then your phone does not think they are deleted. For instance, maybe you have "archived" the message or conversation, or maybe your messages app is not propagating the delete for whatever reason. The one case where you would see deleted messages that your phone has deleted, would be if you delete them and then immediately look at the computer. Message deletion is not propagated. The deleted messages will be gone the next time your devices lose connection, which will cause the desktop to fetch all messages from the remote device. If anyone has a repro where you can delete a message on the phone and still see it on the desktop after rebooting the desktop, please share that. Please double-check with another messaging app on the phone that the message really doesn't appear, and it's not just hidden by your normal messaging app. -- You are receiving this mail because: You are watching all bug changes.
[kdeconnect] [Bug 466469] kdeconnect-sms crashes (SIGSEGV)
https://bugs.kde.org/show_bug.cgi?id=466469 Simon Redman changed: What|Removed |Added Resolution|--- |WORKSFORME Status|REPORTED|RESOLVED -- You are receiving this mail because: You are watching all bug changes.
[kdeconnect] [Bug 483798] kdeconnect-sms doesn't detect URLs in messages
https://bugs.kde.org/show_bug.cgi?id=483798 Simon Redman changed: What|Removed |Added Status|REPORTED|RESOLVED Resolution|--- |DUPLICATE --- Comment #1 from Simon Redman --- Thanks for taking the time to submit this. I've linked this to an earlier item which suggests the same. Please add more to that item if you think it's missing anything. *** This bug has been marked as a duplicate of bug 419100 *** -- You are receiving this mail because: You are watching all bug changes.
[kdeconnect] [Bug 419100] Make links in SMS clickable
https://bugs.kde.org/show_bug.cgi?id=419100 Simon Redman changed: What|Removed |Added CC||john@pelago.org.uk --- Comment #3 from Simon Redman --- *** Bug 483798 has been marked as a duplicate of this bug. *** -- You are receiving this mail because: You are watching all bug changes.
[kdeconnect] [Bug 464654] KDE Connect should be able to send RCS messages
https://bugs.kde.org/show_bug.cgi?id=464654 Simon Redman changed: What|Removed |Added Status|REPORTED|CONFIRMED Ever confirmed|0 |1 --- Comment #1 from Simon Redman --- Google publishes a sample app which could be useful to make the KDE Connect implementation https://android.googlesource.com/platform/packages/services/Telephony/+/refs/heads/main/testapps/TestRcsApp -- You are receiving this mail because: You are watching all bug changes.
[kdeconnect] [Bug 476747] When connection is lost, messages sent just disappear
https://bugs.kde.org/show_bug.cgi?id=476747 --- Comment #3 from Simon Redman --- (In reply to unsubtleness_wastery from comment #2) > (I just rechecked by Enable Airplane mode->send messages on PC-> disable > Airplane mode, that no warning whatsoever is displayed on my PC. I don't > know if a keepalive is used but maybe it should be lower.) There is a keepalive in KDE Connect as a whole. IIRC, it's just the timeout of the TCP connection, which nominally you could configure, but it would then apply to everything on your system. > - Disabling the message input and/or displaying a very visible warning. Once the connection is detected as lost, this is what happens. -- You are receiving this mail because: You are watching all bug changes.
[kdeconnect] [Bug 481389] Possible "fix" for reliability issues
https://bugs.kde.org/show_bug.cgi?id=481389 Simon Redman changed: What|Removed |Added Resolution|--- |INTENTIONAL Status|REPORTED|RESOLVED --- Comment #1 from Simon Redman --- (In reply to Robert Walker from comment #0) > PROPOSAL: > When I began looking at this I thought the original fix to this issue might > be caching messages to a local DB and revising that implementation, but I > have had another idea I want to share with the developer. I think may take > significantly less time and testing. I believe this is observed behavior > that is behind many bug reports on this site, and off-site threads I have > observed exploring KDEConnect (stack, reddit, etc.). > > I have deleted over 130k of my messages to reduce the SMS load to a more > reasonable "1 year of history" and have roughly 35k messages. With this > done, the app is snappy and works great, as expected. > > I believe allowing a configuration setting for the plugin (or perhaps it > best lives in the KDEConnect app to reduce SMS parsing?) to only load the > last "X" messages or since "Y" date would fix many performance issues and > give 99% of users the experience they are looking for - the ability to > respond to relatively recent messages with snappy performance and reliable > transit, without adding additional logic to caching messages or establishing > new databases/data integrity. > > I believe most users want to respond to current messages, or messages from > recent memory, when using this program effectively. Adding these settings > would be a "low cost" way to address performance issues for large SIM > databases without asking users to delete messages from their record source. > Thanks for your consideration. Thanks for sharing this suggestion and the finding. I had not considered deleting messages, it's very interesting this is a significant speedup. At least in the current master build of KDE Connect, the behavior you have described is how it is implemented. The desktop requests the list of conversations, and the phone sends back the first message in each conversation, sending the newest first. Presumably, users most-used contacts will float to the top of this ordering. When a user selects a conversation, the first messages (I think always 10, but maybe I was clever and made it dynamic) are fetched. As you scroll back in history, more messages are fetched, doubling each time first 10, then first 20, then first 40 ... Yes, wasted effort, but extremely easy to implement correctly, and performs adequately. This will get more fluid in the next Android release, because a few days ago a change went in to put all the SMS fetching into a separate thread, so the conversation list can be fetched, at the same time as fetching the history, at the same time as sending a message. I suspect the speedup you're experiencing is because all Android devices (that I know of) use SQLite as the backend for storing messages, and that presumably gets slower as the tables (indices, etc.) get larger. That's just my guess, I'm far from a SQLite expert. (In reply to Robert Walker from comment #0) > Have observed messages "lost" on send This in particular, I assume is due to either the message being sent while the device was actually disconnected (and the UI didn't know), or when other stuff was blocking the main worker thread in KDE Connect Android, causing the packet to be dropped (see note above about putting it all into threads) -- You are receiving this mail because: You are watching all bug changes.
[kdeconnect] [Bug 425638] SMS disappears instead of being send
https://bugs.kde.org/show_bug.cgi?id=425638 --- Comment #21 from Simon Redman --- (In reply to James Pirie from comment #20) > Fairphone 4 KDE connect version 1.21.1 > > Kubuntu 22.10 KDE connect Version 22.08.3-0ubuntu1~ubuntu22.10~ppa1 > > I started experiencing this issue only after a fairly recent update to the > Kubuntu KDE connect app. Previously I was able to send SMS flawlessly. 1.21.1 was the last version which had the SDK version bug. 1.22+ contain the fix. Are you sill seeing issues with SMS? (In reply to James Pirie from comment #20) > I also lost the ability to "reply" to any notifications at all which also > used to work for those applications where it was offered i.e. Email, Signal, > Telegram etc. > This may, of course, have to be the subject of another report. Replying to notifications is a totally different "pipeline" than SMS. Did you file a bug for this? -- You are receiving this mail because: You are watching all bug changes.
[kdeconnect] [Bug 425638] SMS disappears instead of being send
https://bugs.kde.org/show_bug.cgi?id=425638 Simon Redman changed: What|Removed |Added CC||si...@ergotech.com -- You are receiving this mail because: You are watching all bug changes.
[kdeconnect] [Bug 468158] Missing letters in GUI
https://bugs.kde.org/show_bug.cgi?id=468158 Simon Redman changed: What|Removed |Added CC||janitus1...@gmail.com --- Comment #9 from Simon Redman --- *** Bug 468150 has been marked as a duplicate of this bug. *** -- You are receiving this mail because: You are watching all bug changes.
[kdeconnect] [Bug 468150] Characters are not rendering correctly
https://bugs.kde.org/show_bug.cgi?id=468150 Simon Redman changed: What|Removed |Added CC||si...@ergotech.com Resolution|--- |DUPLICATE Status|REPORTED|RESOLVED --- Comment #6 from Simon Redman --- This was fixed with release 23.08.01 (published to the Windows Store a few days after this bug was opened) *** This bug has been marked as a duplicate of bug 468158 *** -- You are receiving this mail because: You are watching all bug changes.
[kdeconnect] [Bug 424127] Accelerator gone missing on "Send" button
https://bugs.kde.org/show_bug.cgi?id=424127 Simon Redman changed: What|Removed |Added Status|REPORTED|RESOLVED Resolution|--- |FIXED --- Comment #1 from Simon Redman --- The pop up window described (sendreplydialog) has been replaced in favour of reply-able notifications, which are provided by KNotification and should support all the relevant accelerators, etc. -- You are receiving this mail because: You are watching all bug changes.
[kdeconnect] [Bug 449333] Support Silence SMS application
https://bugs.kde.org/show_bug.cgi?id=449333 Simon Redman changed: What|Removed |Added Resolution|--- |UPSTREAM Status|REPORTED|RESOLVED --- Comment #1 from Simon Redman --- Marking this bug as "upstream", since Silence intentionally prevents this. -- You are receiving this mail because: You are watching all bug changes.
[kdeconnect] [Bug 415563] SMS notifications persist despite countdown
https://bugs.kde.org/show_bug.cgi?id=415563 Simon Redman changed: What|Removed |Added Status|REPORTED|RESOLVED Resolution|--- |FIXED --- Comment #1 from Simon Redman --- The pop up window described has been replaced in favour of reply-able notifications, which should integrate nicely with the rest of the desktop environment. -- You are receiving this mail because: You are watching all bug changes.
[kdeconnect] [Bug 479396] kdeconnect-sms: conversations list and message lists completely messed up
https://bugs.kde.org/show_bug.cgi?id=479396 Simon Redman changed: What|Removed |Added Resolution|WAITINGFORINFO |WORKSFORME Status|NEEDSINFO |RESOLVED --- Comment #5 from Simon Redman --- (In reply to Tony Green from comment #4) > Its feeling like the problem is something screwed up on my 'phone rather > than in KDEConnect. This is certainly possible. Not a very satisfying outcome, but really the best I can suggest without dissecting your phone on my desk, which I don't have time for and you probably don't want . (In reply to Tony Green from comment #4) > So I'm inclined to suggest closing this off and assuming > it's a one-off problem at the user-end. Since I can *send* messages from the > command line with kdeconnect-cli, I've got most of the functionality I > really need anyway. Thanks for your work on this. Sounds good. I'm glad you're enjoying it! -- You are receiving this mail because: You are watching all bug changes.
[kdeconnect] [Bug 479134] Kdialog with Kdeconnect
https://bugs.kde.org/show_bug.cgi?id=479134 Simon Redman changed: What|Removed |Added Resolution|WAITINGFORINFO |NOT A BUG Status|NEEDSINFO |RESOLVED --- Comment #4 from Simon Redman --- (In reply to lpcornel from comment #2) > The idea is a rudimentary way have desktop-to-desktop messages without using > phones. The design concept is to pop up the kdeconnect tray icon and type in > a message to another kdeconnect desktop user. The message then pops up from > the recipient's tray in the way that kdialog displays the text. It is not > meant to be a conversation thread. Thanks for the reply and suggestion. Since KDE Connect is mostly about connecting _your own_ devices, I don't think this feature makes sense as part of KDE Connect, since normally you would not need a tool to send messages to yourself. -- You are receiving this mail because: You are watching all bug changes.
[kdeconnect] [Bug 479396] kdeconnect-sms: conversations list and message lists completely messed up
https://bugs.kde.org/show_bug.cgi?id=479396 Simon Redman changed: What|Removed |Added Status|REPORTED|NEEDSINFO Resolution|--- |WAITINGFORINFO --- Comment #3 from Simon Redman --- Thanks for taking the time to report this. Unfortunately I can't reproduce what you're experiencing so there isn't much I can directly do. Did this break recently for you? What messaging app are you using on your phone? (In reply to Tony Green from comment #0) > 1. In general, only single person conversations are listed (so none of those > where I've sent SMS messages to multiple contacts). Though ONE multi-person > conversation IS listed. Can you confirm that the messages you've sent to multiple contacts are actually *MMS*? As far as I understand, SMS can only have a single target. (In reply to Tony Green from comment #0) > Not all conversations shown in my SMS app are shown in the conversations list. Can you try to narrow down what is special about all the conversations which are not shown? Are they special messages from your network? Messages from a SIM/phone number which used to be in this phone? Are they from an email address? Etc. (In reply to Tony Green from comment #0) > 3. A number of long-deleted conversations (no longer shown on the app) are > shown. This sounds like you might have only hidden (archived, etc.) the conversation using your messaging app on Android. Anything like that would be an app-specific setting, so KDE Connect reading messages from the messages databases wouldn't have the information that they should not be displayed. (In reply to Tony Green from comment #1) > Created attachment 164672 [details] > Screenshot showing incorrect messages for contact > > The messages shown for this contact were from a completely different one, > which doesn't even appear on the conversations list. This smells like the conversation ID is somehow being corrupted. -- You are receiving this mail because: You are watching all bug changes.
[kdeconnect] [Bug 479134] Kdialog with Kdeconnect
https://bugs.kde.org/show_bug.cgi?id=479134 Simon Redman changed: What|Removed |Added Status|REPORTED|NEEDSINFO Resolution|--- |WAITINGFORINFO --- Comment #1 from Simon Redman --- There is not enough information here for me to make any actions. I don't see a connection between kdialog and messaging, except that kdialog is a rudimentary way to display text, and messages are text. Please detail the design you are suggesting. -- You are receiving this mail because: You are watching all bug changes.
[kdeconnect] [Bug 477361] SMS: Scrolling over- or undershoots when sending messages that don't fit on screen
https://bugs.kde.org/show_bug.cgi?id=477361 Simon Redman changed: What|Removed |Added CC||danielremsb...@gmail.com --- Comment #2 from Simon Redman --- *** Bug 478463 has been marked as a duplicate of this bug. *** -- You are receiving this mail because: You are watching all bug changes.
[kdeconnect] [Bug 478463] When sending a text, the screen scrolls all the way to the top so only the last message sent or received is visible.
https://bugs.kde.org/show_bug.cgi?id=478463 Simon Redman changed: What|Removed |Added Resolution|--- |DUPLICATE Status|REPORTED|RESOLVED --- Comment #1 from Simon Redman --- > as a side note, I can code but I can't (won't?) spin up the while entire > build system for this, is there a way I can contribute otherwise? As mentioned in the bug to which I am linking this one, a key missing piece of information is what exact situation causes this behavior to happen. From the way you've worded this bug, it appears it happens to you all the time, but that is not my experience nor the experience of the other reporter. That said, developer time is always the limiting resource. Even if we knew exactly what needed to be fixed, fixing it would require allocating time that doesn't currently exist. *** This bug has been marked as a duplicate of bug 477361 *** -- You are receiving this mail because: You are watching all bug changes.
[kdeconnect] [Bug 477361] SMS: Scrolling over- or undershoots when sending messages that don't fit on screen
https://bugs.kde.org/show_bug.cgi?id=477361 Simon Redman changed: What|Removed |Added Status|REPORTED|CONFIRMED Ever confirmed|0 |1 --- Comment #1 from Simon Redman --- This is definitely a thing that happens. Thanks for taking the time to write the bug report. In the title you said "when sending messages that don't fit on screen". By this, do you mean sending messages in the case when it should scroll down to show the new messages? (As opposed to the case where there might have already been whitespace?) For me, this happens only sometimes, other times the scrolling works. Is it 100% for you? If not, have you been able to pin down the situation in which this happens reliably? -- You are receiving this mail because: You are watching all bug changes.
[kdeconnect] [Bug 476747] When connection is lost, messages sent just disappear
https://bugs.kde.org/show_bug.cgi?id=476747 Simon Redman changed: What|Removed |Added Ever confirmed|0 |1 Priority|NOR |HI Severity|critical|major Status|REPORTED|CONFIRMED --- Comment #1 from Simon Redman --- Thanks for reporting this. Marking as confirmed because this is something which definitely can happen. I thought I had already written a bug report for this, but apparently not. I have adjusted the priority to "HI" and the severity to "major" -- I agree this is very annoying, and dataloss makes this a more-serious case, but I would like to reserve "critical" for things which are really a disaster, like data being compromised by 3rd parties, etc. This is a tough case to handle, given the way the app was designed. If the connection is lost, then the connection is lost. Since the model is that Android is the source of truth, and since that has been lost, recovering from this situation is outside of the original design. The desktop app could perhaps cache messages in some way (even if it were as simple as allowing the user to copy-paste them out of the GUI). -- You are receiving this mail because: You are watching all bug changes.
[kdeconnect] [Bug 425731] Can no longer send sms
https://bugs.kde.org/show_bug.cgi?id=425731 Simon Redman changed: What|Removed |Added Resolution|--- |WORKSFORME Status|ASSIGNED|RESOLVED --- Comment #21 from Simon Redman --- If this is still happening to you, please reopen the bug with the latest information (OS version, KDE Connect version, Android version, etc.). `sendSms` is the correct name (as of today) of the dbus method. -- You are receiving this mail because: You are watching all bug changes.
[kdeconnect] [Bug 417172] If reply string too long send fails
https://bugs.kde.org/show_bug.cgi?id=417172 Simon Redman changed: What|Removed |Added Status|REPORTED|RESOLVED Resolution|--- |WORKSFORME --- Comment #1 from Simon Redman --- If this is still happening to you, please reopen the bug with the latest information (OS version, KDE Connect version, Android version, etc.). MMS should be fully supported on the latest builds, and you can change at what length the message will change from SMS to MMS in the KDE Connect SMS plugin settings on the Android side. -- You are receiving this mail because: You are watching all bug changes.
[kdeconnect] [Bug 420886] Unable to reply to SMS Message from Desktop
https://bugs.kde.org/show_bug.cgi?id=420886 Simon Redman changed: What|Removed |Added Status|REPORTED|RESOLVED Resolution|--- |WORKSFORME --- Comment #3 from Simon Redman --- If this is still happening to you, please reopen the bug with the latest information (OS version, KDE Connect version, Android version, etc.) -- You are receiving this mail because: You are watching all bug changes.
[kdeconnect] [Bug 437939] KDE Connect SMS 21.04.1 Application quits cleanly after encountering an mms message/image.
https://bugs.kde.org/show_bug.cgi?id=437939 Simon Redman changed: What|Removed |Added Resolution|--- |WORKSFORME Status|REPORTED|RESOLVED --- Comment #1 from Simon Redman --- If this is still happening, please reopen the bug with the latest information. MMS should be fully supported in modern builds. -- You are receiving this mail because: You are watching all bug changes.
[kdeconnect] [Bug 474991] KDE Connect SMS crashes
https://bugs.kde.org/show_bug.cgi?id=474991 Simon Redman changed: What|Removed |Added Resolution|--- |WORKSFORME Status|REPORTED|RESOLVED --- Comment #1 from Simon Redman --- There is not enough information in this bug report to pursue. Please open a new bug report, and be sure to fill out all the template sections and ideally include a backtrace (using the community wiki link in the template). -- You are receiving this mail because: You are watching all bug changes.
[kdeconnect] [Bug 463247] Unable to create new KDE CONNECT SMS messages with "+New" - button greyed out
https://bugs.kde.org/show_bug.cgi?id=463247 Simon Redman changed: What|Removed |Added CC||si...@ergotech.com --- Comment #11 from Simon Redman --- @himcesjf If you have a code change, feel free to make a merge request and we can discuss on the MR itself. If I understand the suggestion in your comment (#10) then it seems like it's just forcing enabled to be true always, which defeats the point of having validation. In general I'm not happy with how this button works. I think the only quick fix here is to update the tooltip to tell users to enter a phone number in the search box. A bigger fix would be to create a new .qml view, similar to the view you get when you click the "New Conversation" in Google messages, which allows users to search their contacts as well as enter a number, and change the behavior of this button to open that view. -- You are receiving this mail because: You are watching all bug changes.
[kdeconnect] [Bug 458304] Contacts not displaying in SMS application
https://bugs.kde.org/show_bug.cgi?id=458304 Simon Redman changed: What|Removed |Added CC||kde.kf...@simplelogin.com --- Comment #4 from Simon Redman --- *** Bug 471283 has been marked as a duplicate of this bug. *** -- You are receiving this mail because: You are watching all bug changes.
[kdeconnect] [Bug 471283] Messaging app does not show contact names, only phone numbers
https://bugs.kde.org/show_bug.cgi?id=471283 Simon Redman changed: What|Removed |Added Status|REPORTED|RESOLVED Resolution|--- |DUPLICATE --- Comment #2 from Simon Redman --- Thanks for taking the time to report this and sorry for the delay. You almost certainly need to install kpeoplevcard. Since you mention you're using Fedora, please upvote this bug to have the kpeoplevcard package added as a dependency of kdeconnect: https://bugzilla.redhat.com/show_bug.cgi?id=2125943 *** This bug has been marked as a duplicate of bug 458304 *** -- You are receiving this mail because: You are watching all bug changes.
[kdeconnect] [Bug 401677] Some phone models, ROMs or Apps don't report SMS History
https://bugs.kde.org/show_bug.cgi?id=401677 --- Comment #115 from Simon Redman --- (In reply to jackdinn from comment #114) > ... > > Please advise. All the fixes discussed in this thread have been integrated into the release version of the app for at least a year. Given that, any discussion involving problems you are having are probably different. Please make a new bug, share your desktop information (version, OS, etc.) as well as your Android device information (make and model, KDE Connect version, etc.) and Android logcat (https://userbase.kde.org/KDEConnect#KDE_Connect_Android_app_crashes) (To anyone who finds this bug in the future: Same request to you. Please search for open bugs involving your exact symptoms, or make a new bug.) -- You are receiving this mail because: You are watching all bug changes.
[kdeconnect] [Bug 468158] Missing letters in GUI
https://bugs.kde.org/show_bug.cgi?id=468158 --- Comment #4 from Simon Redman --- BOF, a new version was just pushed to the Windows store a few hours ago. Can you update to that and let us know if the same thing is happening? Did this used to work for you or did it recently start happening? -- You are receiving this mail because: You are watching all bug changes.
[kdeconnect] [Bug 468937] SMS not working
https://bugs.kde.org/show_bug.cgi?id=468937 Simon Redman changed: What|Removed |Added Resolution|WAITINGFORINFO |NOT A BUG Status|NEEDSINFO |RESOLVED --- Comment #4 from Simon Redman --- (In reply to Justin from comment #3) > I just tested again - and it worked. huh. > Is there a word limit? > Thanks. Thanks for confirming. There is not an intentional word limit but a massive network call is more likely to get lost or messed up, and possibly a massive message might fail to send. If you can reproduce that, please send a bug report with the details of how long is too long and your phone manufacturer. -- You are receiving this mail because: You are watching all bug changes.
[kdeconnect] [Bug 468937] SMS not working
https://bugs.kde.org/show_bug.cgi?id=468937 Simon Redman changed: What|Removed |Added Status|REPORTED|NEEDSINFO Resolution|--- |WAITINGFORINFO --- Comment #1 from Simon Redman --- Hi Justin, Please share your Android app version. There was an issue with 1.24.0 which broke SMS, which was fixed with 1.24.1 a few days later. Thanks, Simon -- You are receiving this mail because: You are watching all bug changes.
[kdeconnect] [Bug 446895] Desktop SMS Unresponsive
https://bugs.kde.org/show_bug.cgi?id=446895 Simon Redman changed: What|Removed |Added Status|REPORTED|NEEDSINFO Resolution|--- |WORKSFORME --- Comment #3 from Simon Redman --- Odin, it does not sound like you are having the same problem as this report. This report specifically describes opening the SMS app, which works, then closing and re-opening the app, after which it does not work. You seem to be saying that the app never works for you. Please check for other related bugs (https://bugs.kde.org/show_bug.cgi?id=468602, maybe?) Garry, are you still able to produce this issue? I do not see this behavior. On the second open of the app, it loads instantly, and I am able to browse conversations, read old messages, and send messages. -- You are receiving this mail because: You are watching all bug changes.
[kdeconnect] [Bug 455149] Unable to continue conversation. After first message sent, "Send Arrow" remains inactive.
https://bugs.kde.org/show_bug.cgi?id=455149 Simon Redman changed: What|Removed |Added Status|CONFIRMED |RESOLVED Resolution|--- |FIXED Latest Commit||https://invent.kde.org/netw ||ork/kdeconnect-kde/commit/0 ||d02a6f99e46e002a89c259ae30b ||02f23661e06c --- Comment #6 from Simon Redman --- Git commit 0d02a6f99e46e002a89c259ae30b02f23661e06c by Simon Redman, on behalf of Dmytrii Zavalnyi. Committed on 21/04/2023 at 16:28. Pushed by sredman into branch 'master'. Fix inactive "Send Arrow" in smsapp after first message sent The "enabled" property of the button was set to false and has overwritten the default value based on the message length. The message field had "anchors.fill" positioning and raised "Binding loop detected for property "implicitHeight"" error. attachmentList property of ChatMessage didn't have the default value and was undefined. M +1-1smsapp/qml/ChatMessage.qml M +13 -10 smsapp/qml/SendingArea.qml https://invent.kde.org/network/kdeconnect-kde/commit/0d02a6f99e46e002a89c259ae30b02f23661e06c -- You are receiving this mail because: You are watching all bug changes.
[kdeconnect] [Bug 468602] Latest update of the Android app prevents desktop app from ever synchronizing SMS
https://bugs.kde.org/show_bug.cgi?id=468602 --- Comment #2 from Simon Redman --- Version 1.24.1 is available on the F-Droid store -- You are receiving this mail because: You are watching all bug changes.
[kdeconnect] [Bug 468602] Latest update of the Android app prevents desktop app from ever synchronizing SMS
https://bugs.kde.org/show_bug.cgi?id=468602 Simon Redman changed: What|Removed |Added OS|Linux |Unspecified Platform|Fedora RPMs |Android Resolution|--- |FIXED Status|REPORTED|RESOLVED Version Fixed In||1.24.1 --- Comment #1 from Simon Redman --- This is presumably due to the change from if/else to switch here, which forgot breaks between the cases: https://invent.kde.org/network/kdeconnect-android/-/commit/038f6e8598441103f0bf3c95b55a759d56534df8#3f11df9dbfb12205751132bb9f36348782af1924 It is fixed here: https://invent.kde.org/network/kdeconnect-android/-/merge_requests/337/diffs Which is part of the 1.24.1 release from this weekend. I've asked for that to be pushed to F-Droid. -- You are receiving this mail because: You are watching all bug changes.
[kdeconnect] [Bug 466469] kdeconnect-sms crashes (SIGSEGV)
https://bugs.kde.org/show_bug.cgi?id=466469 Simon Redman changed: What|Removed |Added Status|REPORTED|NEEDSINFO Resolution|--- |WAITINGFORINFO --- Comment #1 from Simon Redman --- Does the KDE Crash Handler pop up when you see this? The wiki has a few other suggestions for how to get the backtrace: https://community.kde.org/Guidelines_and_HOWTOs/Debugging/How_to_create_useful_crash_reports#Retrieving_a_backtrace_using_coredumpctl Unfortunately there's not enough here to do anything with. The chatty warnings are always there (except the i18n errors because I fixed them recently) -- You are receiving this mail because: You are watching all bug changes.
[kdeconnect] [Bug 464392] Since SDK 31 bump, it is not possible to send SMS using KDE Connect
https://bugs.kde.org/show_bug.cgi?id=464392 Simon Redman changed: What|Removed |Added Latest Commit||https://invent.kde.org/netw ||ork/kdeconnect-android/comm ||it/bcf080f6eb93b12194208e41 ||14b52767f5b0acb0 Resolution|--- |FIXED Status|CONFIRMED |RESOLVED --- Comment #2 from Simon Redman --- Git commit bcf080f6eb93b12194208e4114b52767f5b0acb0 by Simon Redman. Committed on 23/01/2023 at 22:02. Pushed by sredman into branch 'master'. [SMS Plugin] Change android-smsmms to in-house build until upstream supports SDK31 ## Summary Android apps which target SDK 31+ require specifying the mutability of any PENDING_INTENT. This is not supported in the upstream android-smsmms library: https://github.com/klinker41/android-smsmms/pull/193 Until the above PR is merged, we need a solution. I have pulled the code into https://invent.kde.org/sredman/android-smsmms and published the package in the Maven repository in gitlab. ## Test Plan ### Before: Attempting to send an SMS or MMS message using kdeconnect-sms results in no message being sent, and an error being logged: > V/Sending message: Sending new SMS > E/Sending message: Exception > java.lang.IllegalArgumentException: org.kde.kdeconnect_tp: Targeting S+ > (version 31 and above) requires that one of FLAG_IMMUTABLE or FLAG_MUTABLE be > specified when creating a PendingIntent. > Strongly consider using FLAG_IMMUTABLE, only use FLAG_MUTABLE if some > functionality depends on the PendingIntent being mutable, e.g. if it needs to > be used with inline replies or bubbles. > at android.app.PendingIntent.checkFlags(PendingIntent.java:382) > at > android.app.PendingIntent.getBroadcastAsUser(PendingIntent.java:673) > at android.app.PendingIntent.getBroadcast(PendingIntent.java:660) > at > com.klinker.android.send_message.Transaction.sendSmsMessage(Transaction.java:267) > at > com.klinker.android.send_message.Transaction.sendNewMessage(Transaction.java:158) > at > com.klinker.android.send_message.Transaction.sendNewMessage(Transaction.java:172) > at > org.kde.kdeconnect.Plugins.SMSPlugin.SmsMmsUtils.sendMessage(SmsMmsUtils.java:188) > at > org.kde.kdeconnect.Plugins.SMSPlugin.SMSPlugin.onPacketReceived(SMSPlugin.java:414) > at org.kde.kdeconnect.Device.onPacketReceived(Device.java:570) > ### After: SMS and MMS sends normally. M +8-2build.gradle M +6-0settings.gradle https://invent.kde.org/network/kdeconnect-android/commit/bcf080f6eb93b12194208e4114b52767f5b0acb0 -- You are receiving this mail because: You are watching all bug changes.
[kdeconnect] [Bug 452946] Can only get the last 10 messages of any conversation
https://bugs.kde.org/show_bug.cgi?id=452946 Simon Redman changed: What|Removed |Added Latest Commit|https://invent.kde.org/netw |https://invent.kde.org/netw |ork/kdeconnect-kde/commit/5 |ork/kdeconnect-kde/commit/6 |b716dde02a3cc533ab73b10e96f |6a355076c39170047735a5a5bdb |ccd37905b639|45bd25bf70ce --- Comment #4 from Simon Redman --- Git commit 66a355076c39170047735a5a5bdb45bd25bf70ce by Simon Redman. Committed on 22/01/2023 at 22:11. Pushed by sredman into branch 'release/22.12'. [SMS App] Fix loading more messages ## Summary For awhile (since at least early last year), it has not been possible to scroll past the first screen of message history. I believe this was due to a version bump in some library, but I was not able to biset it at the time. This changes how messages are loaded to work again. I like this solution better anyway, because it means one can smoothly scroll back in time without needing to stop every time you reach the top of the history. ## Test Plan ### Before: Scrolling to the top of the kdeconnect-sms history would do nothing. You could only view the first handful of messages in the conversation (whichever messages the app decided to load for you when you first open the conversation). ### After: Scrolling to the top of the list of messages will cause the app to load more, allowing you to view more history of messages. (cherry picked from commit 5b716dde02a3cc533ab73b10e96fccd37905b639) M +16 -5smsapp/qml/ConversationDisplay.qml https://invent.kde.org/network/kdeconnect-kde/commit/66a355076c39170047735a5a5bdb45bd25bf70ce -- You are receiving this mail because: You are watching all bug changes.
[kdeconnect] [Bug 452946] Can only get the last 10 messages of any conversation
https://bugs.kde.org/show_bug.cgi?id=452946 Simon Redman changed: What|Removed |Added Latest Commit||https://invent.kde.org/netw ||ork/kdeconnect-kde/commit/5 ||b716dde02a3cc533ab73b10e96f ||ccd37905b639 Resolution|--- |FIXED Status|CONFIRMED |RESOLVED --- Comment #3 from Simon Redman --- Git commit 5b716dde02a3cc533ab73b10e96fccd37905b639 by Simon Redman. Committed on 22/01/2023 at 22:10. Pushed by sredman into branch 'master'. [SMS App] Fix loading more messages ## Summary For awhile (since at least early last year), it has not been possible to scroll past the first screen of message history. I believe this was due to a version bump in some library, but I was not able to biset it at the time. This changes how messages are loaded to work again. I like this solution better anyway, because it means one can smoothly scroll back in time without needing to stop every time you reach the top of the history. ## Test Plan ### Before: Scrolling to the top of the kdeconnect-sms history would do nothing. You could only view the first handful of messages in the conversation (whichever messages the app decided to load for you when you first open the conversation). ### After: Scrolling to the top of the list of messages will cause the app to load more, allowing you to view more history of messages. M +16 -5smsapp/qml/ConversationDisplay.qml https://invent.kde.org/network/kdeconnect-kde/commit/5b716dde02a3cc533ab73b10e96fccd37905b639 -- You are receiving this mail because: You are watching all bug changes.
[kdeconnect] [Bug 443155] kdeconnect breaks when openssh is upgraded to version 8.8p1-1
https://bugs.kde.org/show_bug.cgi?id=443155 Simon Redman changed: What|Removed |Added Latest Commit|https://invent.kde.org/netw |https://invent.kde.org/netw |ork/kdeconnect-kde/commit/c |ork/kdeconnect-kde/commit/a |eea2af7da84169de32584329df0 |7c17468f0bf16e4ed87c093dac0 |e4a89af21887|b77749c61d50 --- Comment #24 from Simon Redman --- Git commit a7c17468f0bf16e4ed87c093dac0b77749c61d50 by Simon Redman, on behalf of Albert Vaca Cintora. Committed on 22/01/2023 at 20:35. Pushed by sredman into branch 'release/22.12'. Fix ssh authentication using pubkey on recent openssh versions (cherry picked from commit 204207f2e66e87e7696ff1c98d70ce41b3e2d396) M +1-0plugins/sftp/mounter.cpp https://invent.kde.org/network/kdeconnect-kde/commit/a7c17468f0bf16e4ed87c093dac0b77749c61d50 -- You are receiving this mail because: You are watching all bug changes.
[kdeconnect] [Bug 443155] kdeconnect breaks when openssh is upgraded to version 8.8p1-1
https://bugs.kde.org/show_bug.cgi?id=443155 Simon Redman changed: What|Removed |Added Latest Commit|https://invent.kde.org/netw |https://invent.kde.org/netw |ork/kdeconnect-kde/commit/2 |ork/kdeconnect-kde/commit/c |04207f2e66e87e7696ff1c98d70 |eea2af7da84169de32584329df0 |ce41b3e2d396|e4a89af21887 --- Comment #23 from Simon Redman --- Git commit ceea2af7da84169de32584329df0e4a89af21887 by Simon Redman, on behalf of Albert Vaca Cintora. Committed on 22/01/2023 at 20:34. Pushed by sredman into branch 'cherry-pick-204207f2'. Fix ssh authentication using pubkey on recent openssh versions (cherry picked from commit 204207f2e66e87e7696ff1c98d70ce41b3e2d396) M +1-0plugins/sftp/mounter.cpp https://invent.kde.org/network/kdeconnect-kde/commit/ceea2af7da84169de32584329df0e4a89af21887 -- You are receiving this mail because: You are watching all bug changes.
[kdeconnect] [Bug 464555] KDE Connect SMS group chat issues: last message shows only one person in a 3 person group chat , KDE Connect does not distinguish messages from different people
https://bugs.kde.org/show_bug.cgi?id=464555 Simon Redman changed: What|Removed |Added Latest Commit||https://invent.kde.org/netw ||ork/kdeconnect-android/comm ||it/9db4c885a5001cadab9b5f2d ||269165e3d20dc3de Resolution|--- |FIXED Status|CONFIRMED |RESOLVED --- Comment #3 from Simon Redman --- Git commit 9db4c885a5001cadab9b5f2d269165e3d20dc3de by Simon Redman. Committed on 22/01/2023 at 20:16. Pushed by sredman into branch 'master'. [SMS Plugin] Fix handling for addresses list of multi-target group messages ## Summary Fix a logic error in the SMS plugin which caused it to skip the addresses of other targets when reporting group messages. Notionally, this bug originated with the logic change in !197, where everything switched to using the android-smsmms library. ## Test Plan ### Before: Group messages would be returned as single-target messages between you and the sender, meaning the desktop app would have a bad time showing them. ### After: Group messages are returned with the appropriate list of addresses, the desktop app groups them appropriately. M +1-1src/org/kde/kdeconnect/Plugins/SMSPlugin/SmsMmsUtils.java https://invent.kde.org/network/kdeconnect-android/commit/9db4c885a5001cadab9b5f2d269165e3d20dc3de -- You are receiving this mail because: You are watching all bug changes.
[kdeconnect] [Bug 464654] New: KDE Connect should be able to send RCS messages
https://bugs.kde.org/show_bug.cgi?id=464654 Bug ID: 464654 Summary: KDE Connect should be able to send RCS messages Classification: Applications Product: kdeconnect Version: unspecified Platform: Android OS: Android 13.x Status: REPORTED Severity: wishlist Priority: NOR Component: messaging-application Assignee: si...@ergotech.com Reporter: si...@ergotech.com Target Milestone: --- SUMMARY When trying to send a message to an RCS-enabled thread, KDE Connect instead sends a regular SMS or MMS. STEPS TO REPRODUCE (Steps not exactly known, since Android does not provide the APIs) 1. Enable RCS 2. Have someone else enable RCS 3. Send a message to that person using KDE Connect OBSERVED RESULT KDE Connect cannot send messages as RCS EXPECTED RESULT KDE Connect should send messages as RCS SOFTWARE/OS VERSIONS N/A -- Affects all Android versions to-date ADDITIONAL INFORMATION This is not possible until Android enables RCS support for 3rd party apps. Some APIs are there but, as of today, they are hidden. It might be possible to use them via reflection, but I am not willing to invest in non-stable APIs. I would gamble they do work, though, as I believe the APIs exist for Samsung or other OEMs to enable RCS support for their customers. For example, the RcsMessage class in the latest Android SDK is hidden. https://android.googlesource.com/platform/prebuilts/fullsdk/sources/android-29/+/refs/heads/androidx-core-core-role-release/android/telephony/ims/RcsMessage.java If someone else wants to take on this work with an implementation which fails gracefully if the APIs are not available, please feel free to do so. -- You are receiving this mail because: You are watching all bug changes.
[kdeconnect] [Bug 415531] KDE Connect mistakenly thinks a conversation is a group if the latest message was a received RCS message
https://bugs.kde.org/show_bug.cgi?id=415531 Simon Redman changed: What|Removed |Added Status|REPORTED|RESOLVED Resolution|--- |FIXED --- Comment #2 from Simon Redman --- This has been resolved; probably by exactly the thought I had earlier of enabling Android to strip out the user's own phone number. -- You are receiving this mail because: You are watching all bug changes.
[kdeconnect] [Bug 464555] KDE Connect SMS group chat issues: last message shows only one person in a 3 person group chat , KDE Connect does not distinguish messages from different people
https://bugs.kde.org/show_bug.cgi?id=464555 --- Comment #2 from Simon Redman --- Correction: The interesting release of the Android app was December 27, 2022. Prior to that, the previous release was v1.19.1 from January 24, 2022. -- You are receiving this mail because: You are watching all bug changes.
[kdeconnect] [Bug 464555] KDE Connect SMS group chat issues: last message shows only one person in a 3 person group chat , KDE Connect does not distinguish messages from different people
https://bugs.kde.org/show_bug.cgi?id=464555 Simon Redman changed: What|Removed |Added Ever confirmed|0 |1 Status|REPORTED|CONFIRMED --- Comment #1 from Simon Redman --- Thanks for reporting this. In spite of my long believe to the contrary, it looks like this is actually due to the Android app misbehaving! Did you start experiencing this around the time the most-recent version of the Android app was pushed? That was January 6, 2023. -- You are receiving this mail because: You are watching all bug changes.
[kdeconnect] [Bug 464392] Since SDK 31 bump, it is not possible to send SMS using KDE Connect
https://bugs.kde.org/show_bug.cgi?id=464392 Simon Redman changed: What|Removed |Added Priority|NOR |HI Severity|normal |major -- You are receiving this mail because: You are watching all bug changes.
[kdeconnect] [Bug 464392] Since SDK 31 bump, it is not possible to send SMS using KDE Connect
https://bugs.kde.org/show_bug.cgi?id=464392 Simon Redman changed: What|Removed |Added Status|REPORTED|CONFIRMED Ever confirmed|0 |1 --- Comment #1 from Simon Redman --- I have created this PR against the com.klinker.android library, which contains the offending code: https://github.com/klinker41/android-smsmms/pull/193 I have tested this change locally: Next step, figure out how to package and ship KDE Connect with that fix. -- You are receiving this mail because: You are watching all bug changes.
[kdeconnect] [Bug 455149] Unable to continue conversation. After first message sent, "Send Arrow" remains inactive.
https://bugs.kde.org/show_bug.cgi?id=455149 --- Comment #4 from Simon Redman --- (In reply to Dmytrii from comment #3) > > Hello, I found some QML positioning errors. It is not just enabled/disabled > issue. This property depends on messageField textarea which became > undefined. I can fix it. Could you assign this bug to me, or should I do it > on my own? Feel free to take ownership yourself. Thanks for stepping up! Please reach out to the team if you get stuck or want to ask questions: https://community.kde.org/KDEConnect#Development -- You are receiving this mail because: You are watching all bug changes.
[kdeconnect] [Bug 464391] Multi sim Manage
https://bugs.kde.org/show_bug.cgi?id=464391 Simon Redman changed: What|Removed |Added Resolution|--- |FIXED Status|REPORTED|RESOLVED --- Comment #2 from Simon Redman --- https://invent.kde.org/network/kdeconnect-kde/-/commit/d3062cafd41460113911c13c40fa6d4b67dcbcf0 added multi-SIM reply in mid-2020 1.4.x was branched December 2019, so that build does not contain this feature. I would strongly encourage you to upgrade. If your distro does not package a recent version, you could try building from source: https://community.kde.org/KDEConnect#Linux_Desktop I caution that it will be an uphill battle. By picking an LTS distro (as you have apparently done, from the system information provided), you have made a trade: "I will be very stable but I will not have the latest features". I don't know how the packages in Linux Mint work, but you could try the kubuntu Backports PPA. Rik Mills does a very nice job maintaining it with recent version of KDE software for various Ubuntu releases which may be compatible with your Mint version. https://launchpad.net/~kubuntu-ppa/+archive/ubuntu/backports. Note this will significantly pollute your LTS stability, as you will end up with lots of much newer packages (KDE Frameworks, likely Qt, etc.) -- You are receiving this mail because: You are watching all bug changes.
[kdeconnect] [Bug 425638] SMS disappears instead of being send
https://bugs.kde.org/show_bug.cgi?id=425638 --- Comment #19 from Simon Redman --- Created a bug for the specific issue reported by bb817...@spymail.one which is due to the SDK bump https://bugs.kde.org/show_bug.cgi?id=464392. If you're experiencing that (as I said before, I imagine everyone is experiencing it) please watch there. -- You are receiving this mail because: You are watching all bug changes.
[kdeconnect] [Bug 464392] Since SDK 31 bump, it is not possible to send SMS using KDE Connect
https://bugs.kde.org/show_bug.cgi?id=464392 Simon Redman changed: What|Removed |Added Assignee|albertv...@gmail.com|si...@ergotech.com -- You are receiving this mail because: You are watching all bug changes.
[kdeconnect] [Bug 464392] New: Since SDK 31 bump, it is not possible to send SMS using KDE Connect
https://bugs.kde.org/show_bug.cgi?id=464392 Bug ID: 464392 Summary: Since SDK 31 bump, it is not possible to send SMS using KDE Connect Classification: Applications Product: kdeconnect Version: unspecified Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: android-application Assignee: albertv...@gmail.com Reporter: si...@ergotech.com CC: andrew.g.r.hol...@gmail.com Target Milestone: --- SUMMARY Since SDK 31 (https://invent.kde.org/network/kdeconnect-android/-/commit/6fbd923c60538c2cc6da22246f5b523ef3160256), it is not possible to send SMS. STEPS TO REPRODUCE 1. Use latest KDE Connect release (early January, 2023) 2. Send SMS using KDE Connect OBSERVED RESULT > V/Sending message: Sending new SMS > E/Sending message: Exception > java.lang.IllegalArgumentException: org.kde.kdeconnect_tp: Targeting S+ > (version 31 and above) requires that one of FLAG_IMMUTABLE or FLAG_MUTABLE be > specified when creating a PendingIntent. > Strongly consider using FLAG_IMMUTABLE, only use FLAG_MUTABLE if some > functionality depends on the PendingIntent being mutable, e.g. if it needs to > be used with inline replies or bubbles. > at android.app.PendingIntent.checkFlags(PendingIntent.java:382) > at > android.app.PendingIntent.getBroadcastAsUser(PendingIntent.java:673) > at android.app.PendingIntent.getBroadcast(PendingIntent.java:660) > at > com.klinker.android.send_message.Transaction.sendSmsMessage(Transaction.java:267) > at > com.klinker.android.send_message.Transaction.sendNewMessage(Transaction.java:158) > at > com.klinker.android.send_message.Transaction.sendNewMessage(Transaction.java:172) > at > org.kde.kdeconnect.Plugins.SMSPlugin.SmsMmsUtils.sendMessage(SmsMmsUtils.java:188) > at > org.kde.kdeconnect.Plugins.SMSPlugin.SMSPlugin.onPacketReceived(SMSPlugin.java:414) > at org.kde.kdeconnect.Device.onPacketReceived(Device.java:570) > EXPECTED RESULT SMS sends SOFTWARE/OS VERSIONS Linux/KDE Plasma: KDE Plasma Version: 5.26.4 KDE Frameworks Version: 5.101.0 Qt Version: 5.15.7 ADDITIONAL INFORMATION Initially reported by another user in https://bugs.kde.org/show_bug.cgi?id=425638 -- You are receiving this mail because: You are watching all bug changes.
[kdeconnect] [Bug 433871] FRE: SMS plugin - multi SIM support
https://bugs.kde.org/show_bug.cgi?id=433871 Simon Redman changed: What|Removed |Added Status|REPORTED|RESOLVED Resolution|--- |WORKSFORME --- Comment #1 from Simon Redman --- KDE Connect SMS will reply to messages using the same SIM card as the most-recent message in the conversation. So the app does have multi-SIM support. I don't remember when multi-SIM support was added. At the time this bug was created, maybe it was not supported, in which case we should just resolve this bug, as it has indeed been resolved. If you are having issues with the current implementation, please create a new bug with the symptoms and we can have the discussion there. We made the simplifying decision when adding that support, to not add support for selecting subscriptions when sending. It is massively more difficult to ask Android "what SIM cards are currently available?" than it is to use the last-active subscription, and I do not believe there is a usecase to "hop" between outgoing phone numbers within one conversation. If someone has a case where you need to be able to reply to a conversation with a subscription other than the last one, please open a new bug and describe that use case. (One valid use-case, would be to at least display the subscription which KDE Connect will use to reply.) -- You are receiving this mail because: You are watching all bug changes.
[kdeconnect] [Bug 442773] Pamac notification forwarding cannot be disabled
https://bugs.kde.org/show_bug.cgi?id=442773 Simon Redman changed: What|Removed |Added Resolution|--- |WAITINGFORINFO Component|messaging-application |common Assignee|si...@ergotech.com |albertv...@gmail.com Status|REPORTED|NEEDSINFO CC||andrew.g.r.hol...@gmail.com ||, si...@ergotech.com --- Comment #1 from Simon Redman --- Hi, Sorry for the long delay in responding. Are you still having this issue? If so, please add to the STEPS TO REPRODUCE steps including how you have filtered notifications. (You will have to copy-paste the old list into a new comment, bugzilla does not allow editing old comments). -- You are receiving this mail because: You are watching all bug changes.
[kdeconnect] [Bug 438201] app can open but all founctions does not work.
https://bugs.kde.org/show_bug.cgi?id=438201 Simon Redman changed: What|Removed |Added Component|messaging-application |common Resolution|--- |FIXED CC||andrew.g.r.hol...@gmail.com ||, si...@ergotech.com Status|REOPENED|RESOLVED Assignee|si...@ergotech.com |veyx.s...@gmail.com --- Comment #14 from Simon Redman --- >From the conversation it looks like this has been fixed. If you are still having issues, please open a new bug with the latest information. -- You are receiving this mail because: You are watching all bug changes.
[kdeconnect] [Bug 410112] SMS app offers devices which don't have SMS support
https://bugs.kde.org/show_bug.cgi?id=410112 Simon Redman changed: What|Removed |Added Status|REPORTED|CONFIRMED Keywords||junior-jobs Ever confirmed|0 |1 --- Comment #2 from Simon Redman --- Marking this item as a junior-job because it should be relatively easy to add this filtering. Feel free to reach out to me if you are interested in taking it on. -- You are receiving this mail because: You are watching all bug changes.
[kdeconnect] [Bug 410112] SMS app offers devices which don't have SMS support
https://bugs.kde.org/show_bug.cgi?id=410112 Simon Redman changed: What|Removed |Added CC||sichersic...@t-online.de --- Comment #1 from Simon Redman --- *** Bug 458930 has been marked as a duplicate of this bug. *** -- You are receiving this mail because: You are watching all bug changes.
[kdeconnect] [Bug 458930] Wrong device is selected when opening SMS messaging
https://bugs.kde.org/show_bug.cgi?id=458930 Simon Redman changed: What|Removed |Added Status|REPORTED|RESOLVED Resolution|--- |DUPLICATE --- Comment #1 from Simon Redman --- (In reply to Halmut Holz from comment #0) > SUMMARY > > I have 2 devices with KDE-connect (tablet and phone). When I select my phone > from the KDE-connect tray-icon and select "SMS-Nachrichten" (sorry, I don't > know what the menu entries are called in English), the messaging-window > opens, but my tablet is selected - even though SMS-messaging is disabled in > the tablets settings. I assume it is selected because it is alphabetically > before the phone. > > > STEPS TO REPRODUCE > 1. Connect two different devices with KDE-Connect on a Kubuntu 22.04 desktop > 2. Click on the KDE-Connect tray icon > 3. On the second device in the list click on the three-bar-menu > (hamburger-button) and click "SMS-Messages" > > OBSERVED RESULT > The SMS-Messages-Windows opens but with the other device selected. > > EXPECTED RESULT > The the second device should be selected in the SMS-Messages-Window > > SOFTWARE/OS VERSIONS > KDE-Connect Version: 21.12.3-0ubuntu1 > Betriebssystem: Kubuntu 22.04 > KDE-Plasma-Version: 5.24.6 > KDE-Frameworks-Version: 5.92.0 > Qt-Version: 5.15.3 > Kernel-Version: 5.15.0-47-generic (64-bit) > Grafik-Plattform: X11 Hi Halmut, Thanks for taking the time to report this, and sorry for the long delay in my response. I've marked this bug as a duplicate of the wishlist/workitem https://bugs.kde.org/show_bug.cgi?id=410112. This is a long-standing feature gap. Please monitor there for any updates. *** This bug has been marked as a duplicate of bug 410112 *** -- You are receiving this mail because: You are watching all bug changes.
[kdeconnect] [Bug 421606] After the update for Ubuntu 20.04, the interface in the pc desktop (right upper corner) disappear!
https://bugs.kde.org/show_bug.cgi?id=421606 Simon Redman changed: What|Removed |Added Resolution|--- |DOWNSTREAM Status|REPORTED|RESOLVED --- Comment #2 from Simon Redman --- Marking this bug as resolved since it seems to belong to GS Connect. Luiz, if you are still having issues, please reach out to the GS Connect users on the GS Connect github. -- You are receiving this mail because: You are watching all bug changes.
[kdeconnect] [Bug 425113] Can't copy partial message from SMS
https://bugs.kde.org/show_bug.cgi?id=425113 Simon Redman changed: What|Removed |Added Resolution|--- |FIXED Status|REPORTED|RESOLVED --- Comment #2 from Simon Redman --- I didn't write the commit so it is not easy to look up, but support for partial-message and whole-message copy-paste was added awhile back. It's a little clunky, so I invite anyone interested to iterate and improve, but for the purpose of this bug I'm going to call it resolved. -- You are receiving this mail because: You are watching all bug changes.
[kdeconnect] [Bug 442918] speed up transfer of messages when kdeconnect first connects, by an appropriate mechanism
https://bugs.kde.org/show_bug.cgi?id=442918 --- Comment #5 from Simon Redman --- (In reply to robin from comment #3) > Also, it sounds like you might be about to volunteer to write a > standards-compliant SMS app, to get around the problem. ;-) > > Or at least recommend something which follows the appropriate spec. Annoyingly, the issue is with non-standard _Android_ implementations. If everyone ran ASOP, there would be no problem. The SMS app which sits on top just uses the interfaces Android provides. There are SMS apps which do everything by themselves (Signal, for example), but that's a special case. -- You are receiving this mail because: You are watching all bug changes.
[kdeconnect] [Bug 442918] speed up transfer of messages when kdeconnect first connects, by an appropriate mechanism
https://bugs.kde.org/show_bug.cgi?id=442918 Simon Redman changed: What|Removed |Added Status|REPORTED|RESOLVED Resolution|--- |FIXED --- Comment #4 from Simon Redman --- I forgot about this bug. However, several months ago I implemented this: https://invent.kde.org/network/kdeconnect-android/-/merge_requests/296. It should be in the latest (early January 2023) KDE Connect Android release and does not require any change on the desktop side. Conversations are now returned one-by-one, with more-recent conversations returned first. This means the GUI starts being populated nearly instantly, and presumably the more-useful conversations get loaded first since those are likely the most-recent. There is still plenty of room to improve in this space, but I am going to consider this bug resolved. -- You are receiving this mail because: You are watching all bug changes.
[kdeconnect] [Bug 464071] New: Add packet statistics tracking
https://bugs.kde.org/show_bug.cgi?id=464071 Bug ID: 464071 Summary: Add packet statistics tracking Classification: Applications Product: kdeconnect Version: unspecified Platform: unspecified OS: All Status: REPORTED Severity: wishlist Priority: NOR Component: common Assignee: albertv...@gmail.com Reporter: si...@ergotech.com CC: andrew.g.r.hol...@gmail.com Target Milestone: --- SUMMARY KDE Connect should keep track of the number of packets of each type it receives. This would be useful for debugging issues like performance or battery drain, and also useful as a starting place to debug why a particular plugin might not be working. -- You are receiving this mail because: You are watching all bug changes.
[kdeconnect] [Bug 441830] 12 TCP keepalive packets per minute is excessive, battery drain hazard.
https://bugs.kde.org/show_bug.cgi?id=441830 --- Comment #9 from Simon Redman --- In particular, this claim is unsubstantiated from the evidence in this bug: (In reply to Maxim Egorushkin from comment #7) > Battery power is a limited resource but 5-second keepalive frequency expends > it at high rate without consideration. The only test mentioned is the app installed vs. uninstalled. There could be any number of other explanations for this. Maybe you use an app on the desktop with a very chatty MPRIS implementation, for instance. https://bugs.kde.org/show_bug.cgi?id=442782 You apparently have a workaround which changes the keepalive frequency. I assume you're happy with the battery life after applying the questions. Can you quantify that? -- You are receiving this mail because: You are watching all bug changes.
[kdeconnect] [Bug 441830] 12 TCP keepalive packets per minute is excessive, battery drain hazard.
https://bugs.kde.org/show_bug.cgi?id=441830 Simon Redman changed: What|Removed |Added Status|REPORTED|NEEDSINFO CC||si...@ergotech.com Resolution|--- |WAITINGFORINFO --- Comment #8 from Simon Redman --- (In reply to Maxim Egorushkin from comment #5) > The developers must provide justification for these rather frequent TCP > keepalive messages when communicating with battery-powered devices. As in the PR vladikss linked: If the keepalive is set higher, it will falsely tell users that the phone is connected when it is in fact not. Please do the test as requested by vladikss. Without some evidence that a change actually makes a difference, it's just a random number. -- You are receiving this mail because: You are watching all bug changes.
[kdeconnect] [Bug 425638] SMS disappears instead of being send
https://bugs.kde.org/show_bug.cgi?id=425638 --- Comment #18 from Simon Redman --- (In reply to bb81710y from comment #17) > I can read SMS but I stopped being able to send them when I updated From > LineageOS 19 to 20 (Android 12L to 13) on my bramble. Here's what logcat > continuously states when I try to send. > > 12-31 22:12:07.148 15551 15972 E TelephonyHelper: at > org.kde.kdeconnect.Backends.LanBackend.LanLink$$ExternalSyntheticLambda0. > run(Unknown Source:4) > 12-31 22:12:07.188 15551 15972 E Sending message: > java.lang.IllegalArgumentException: org.kde.kdeconnect_tp: Targeting S+ > (version 31 and above) requires that one of FLAG_IMMUTABLE or FLAG_MUTABLE > be specified when creating a PendingIntent. > 12-31 22:12:07.188 15551 15972 E Sending message: at > org.kde.kdeconnect.Plugins.SMSPlugin.SmsMmsUtils.sendMessage(SmsMmsUtils. > java:188) > 12-31 22:12:07.188 15551 15972 E Sending message: at > org.kde.kdeconnect.Plugins.SMSPlugin.SMSPlugin.onPacketReceived(SMSPlugin. > java:414) > 12-31 22:12:07.188 15551 15972 E Sending message: at > org.kde.kdeconnect.Device.onPacketReceived(Device.java:570) > 12-31 22:12:07.188 15551 15972 E Sending message: at > org.kde.kdeconnect.Backends.BaseLink.packageReceived(BaseLink.java:70) > 12-31 22:12:07.188 15551 15972 E Sending message: at > org.kde.kdeconnect.Backends.LanBackend.LanLink.receivedNetworkPacket(LanLink. > java:250) 12-31 22:12:07.188 15551 15972 E Sending message: at > org.kde.kdeconnect.Backends.LanBackend.LanLink.lambda$reset$0(LanLink.java: > 98) > 12-31 22:12:07.188 15551 15972 E Sending message: at > org.kde.kdeconnect.Backends.LanBackend.LanLink. > $r8$lambda$X(Unknown Source:0) > 12-31 22:12:07.188 15551 15972 E Sending message: at > org.kde.kdeconnect.Backends.LanBackend.LanLink$$ExternalSyntheticLambda0. > run(Unknown Source:4) This crash looks like a new issue (specifically because it says "version 31 and above") Albert had to bump the SDK version for the Google Play release. By any chance did you notice if you got the new KDE Connect app over the weekend, and was that correlated to the new errors you get? (Or did you update your phone over this weekend as well, so it's hard to say?) Could you open a new bug for this issue, please? I'll try to make time for it this week since from my quick research it should be straightforward and probably broken for everyone. (Relevant commit: https://invent.kde.org/network/kdeconnect-android/-/commit/6fbd923c60538c2cc6da22246f5b523ef3160256) -- You are receiving this mail because: You are watching all bug changes.
[kdeconnect] [Bug 425638] SMS disappears instead of being send
https://bugs.kde.org/show_bug.cgi?id=425638 --- Comment #15 from Simon Redman --- Somehow I am still missing email notifications on this bug... Here's a mega reply. Firstly, to everyone, does this happen the first time you launch kdeconnect-sms, or only after awhile? (Specifically, after the phone has lost connection) (In reply to pyr0m4n14c12 from comment #12) > I installed adb in hopes of helping. I try to send an SMS (disappears like > usual) and then run > > adb logcat org.kde.kdeconnect:I *:S >> ~/kdeconnect-logcat.txt > > I get > > - waiting for device - This looks like you haven't paired your adb devices. Make sure you've accepted the debugging fingerprint on the phone, and that `adb devices` shows you have one device paired. (In reply to pyr0m4n14c12 from comment #13) > I want to add that I just realized my 'send' airplane is greyed out. I've > been hitting 'enter' to send so I never noticed. I can browse files on my > phone from my PC and I can send pings. Kde Connect shows them as > successfully paired. This is probably unrelated. It's more likely you're seeing https://bugs.kde.org/show_bug.cgi?id=455149 (In reply to Nathan from comment #14) > I know this is an older bug, but I can confirm that it's still present on > 21.12.3. If I click reply from the notification popup, my text goes through. > If I try to send a text from the KDE Connect SMS app, it disappears and > nothing is sent. > > I'm running Linux Mint 21 and using a Samsung Galaxy S22. I will also note > that I have a physical AND eSIM on my phone. I'm not sure if that fact may > be contributing to this bug. KDE Connect SMS worked with dual-sim setups. I no longer have a dual SIM setup to test. Also there's always the chance that Samsung has broken something on their end. Can you get a logcat, as described above? -- You are receiving this mail because: You are watching all bug changes.
[kdeconnect] [Bug 455149] Unable to continue conversation. After first message sent, "Send Arrow" remains inactive.
https://bugs.kde.org/show_bug.cgi?id=455149 Simon Redman changed: What|Removed |Added Keywords||junior-jobs Ever confirmed|0 |1 Status|REPORTED|CONFIRMED -- You are receiving this mail because: You are watching all bug changes.
[kdeconnect] [Bug 455149] Unable to continue conversation. After first message sent, "Send Arrow" remains inactive.
https://bugs.kde.org/show_bug.cgi?id=455149 --- Comment #2 from Simon Redman --- Marking as confirmed since another user reported a duplicate bug and I can reproduce the same behavior. Note that pressing the enter button to send causes the button to be disabled, but you can send multiple messages in the same conversation by using enter to send. If I were guessing, something is wrong with the `disabled` state of the send button, probably in the part of the code where it tries to prevent sending duplicate messages by briefly disabling the button. Marking this as a junior job. It's probably a simple fix, someone just needs to poke into the QML and find where the disabled state of the button is set, and find where it should be re-enabled. -- You are receiving this mail because: You are watching all bug changes.
[kdeconnect] [Bug 463247] Unable to create new KDE CONNECT SMS messages with "+New" - button greyed out
https://bugs.kde.org/show_bug.cgi?id=463247 Simon Redman changed: What|Removed |Added Keywords||junior-jobs --- Comment #2 from Simon Redman --- Marking this as a junior job. It should be a simple fix, poke into the QML and find why the logic for the `enabled` state of the new button doesn't work. If I were guessing, it's probably due to a mis-named or re-named variable. -- You are receiving this mail because: You are watching all bug changes.
[kdeconnect] [Bug 455149] Unable to continue conversation. After first message sent, "Send Arrow" remains inactive.
https://bugs.kde.org/show_bug.cgi?id=455149 Simon Redman changed: What|Removed |Added CC||rleyva...@gmail.com --- Comment #1 from Simon Redman --- *** Bug 463248 has been marked as a duplicate of this bug. *** -- You are receiving this mail because: You are watching all bug changes.
[kdeconnect] [Bug 463248] Paper Airplane Button to send message greyed out and unavailable after sending one SMS message
https://bugs.kde.org/show_bug.cgi?id=463248 Simon Redman changed: What|Removed |Added Resolution|--- |DUPLICATE Status|REPORTED|RESOLVED --- Comment #1 from Simon Redman --- *** This bug has been marked as a duplicate of bug 455149 *** -- You are receiving this mail because: You are watching all bug changes.
[kdeconnect] [Bug 401208] Synced contact numbers are always in North American format
https://bugs.kde.org/show_bug.cgi?id=401208 Simon Redman changed: What|Removed |Added Resolution|WAITINGFORINFO |UPSTREAM Status|NEEDSINFO |RESOLVED -- You are receiving this mail because: You are watching all bug changes.
[kdeconnect] [Bug 463247] Unable to create new KDE CONNECT SMS messages with "+New" - button greyed out
https://bugs.kde.org/show_bug.cgi?id=463247 Simon Redman changed: What|Removed |Added Status|REPORTED|CONFIRMED Ever confirmed|0 |1 --- Comment #1 from Simon Redman --- Thanks for reporting this. I see the same behavior. I remember there was a refactor of the UI awhile ago, I expect the `enabled` property of the New button got disconnected somehow as part of that. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 459929] USB-C connected display goes black when mouse is moved from laptop display
https://bugs.kde.org/show_bug.cgi?id=459929 --- Comment #7 from Simon Redman --- Issue opened here: https://github.com/DisplayLink/evdi/issues/388 I have replaced my displaylink dock because it was causing too many headaches but I still have it on my desk so I can test. Someone who is more impacted (Alexander Reinholdt, if you're following this bug, for instance) may want to take point on responding to the EVDI bug if the developers on that side respond. -- You are receiving this mail because: You are watching all bug changes.
[kdeconnect] [Bug 461325] Overly long file and/or erroneous names in ~/.local/share/kpeoplevcard
https://bugs.kde.org/show_bug.cgi?id=461325 Simon Redman changed: What|Removed |Added Status|CONFIRMED |NEEDSINFO Resolution|--- |WORKSFORME --- Comment #4 from Simon Redman --- 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). -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 459929] USB-C connected display goes black when mouse is moved from laptop display
https://bugs.kde.org/show_bug.cgi?id=459929 --- Comment #4 from Simon Redman --- (In reply to Zamundaaa from comment #3) > So without more information I am relatively certain this is a driver bug. I > think the correct place to report that is > https://github.com/DisplayLink/evdi/issues > > Until that's fixed, you can try forcing a software cursor as a workaround: > https://invent.kde.org/plasma/kwin/-/wikis/Environment- > Variables#kwin_force_sw_cursor Sorry for the long delay in responding. The KWIN_FORCE_SW_CURSOR is working for me. I no longer have to live in fear of system updates! Do you have a suggestion for what I should tell the EVDI people? -- You are receiving this mail because: You are watching all bug changes.
[kdeconnect] [Bug 460711] KDE Connect SMS message entry restrict copy-paste
https://bugs.kde.org/show_bug.cgi?id=460711 --- Comment #4 from Simon Redman --- Thanks for the video. I now understand what you're experiencing but I can't reproduce it. If I enter a character, I can still click anywhere in the box to paste. If I delete that character, it still behaves normally. What versions do you have for: kdeconnect-sms (probably packaged with some other kdeconnect package, but you can check the about screen in the app) kirigami and kirigami2 (packaged as kf5-kirigami and kf5-kirigami2 on Fedora, but I don't know how it is packaged on other platforms) -- You are receiving this mail because: You are watching all bug changes.
[kdeconnect] [Bug 460711] KDE Connect SMS message entry restrict copy-paste
https://bugs.kde.org/show_bug.cgi?id=460711 Simon Redman changed: What|Removed |Added Resolution|WORKSFORME |--- Status|NEEDSINFO |REPORTED -- You are receiving this mail because: You are watching all bug changes.
[kdeconnect] [Bug 460711] KDE Connect SMS message entry restrict copy-paste
https://bugs.kde.org/show_bug.cgi?id=460711 Simon Redman changed: What|Removed |Added Resolution|--- |WORKSFORME Status|REPORTED|NEEDSINFO --- Comment #1 from Simon Redman --- Could you please attach a video/gif/screenshots showing the issue you're having? I can paste into the compose message field normally, without any care for where I click in order to get the cursor to the end of the line. -- You are receiving this mail because: You are watching all bug changes.
[kdeconnect] [Bug 459171] Network discovery is performed only using main interface (no devices when VPN or multiple interfaces are connected)
https://bugs.kde.org/show_bug.cgi?id=459171 Simon Redman changed: What|Removed |Added Latest Commit||https://invent.kde.org/netw ||ork/kdeconnect-kde/commit/3 ||90a44a901de2a887fa37c7f7c6c ||db20fd50a371 Status|ASSIGNED|RESOLVED Resolution|--- |FIXED --- Comment #3 from Simon Redman --- Git commit 390a44a901de2a887fa37c7f7c6cdb20fd50a371 by Simon Redman, on behalf of ValdikSS ValdikSS. Committed on 17/10/2022 at 22:21. Pushed by sredman into branch 'master'. Really set source IP for broadcast discovery packets on Windows/FreeBSD This whole code was no-op: it enumerates network interfaces, enumerates its IP addresses, but does not change the address of broadcast UDP packet, sending it only via default route/interface. Bind the socket to IP addresses of the interfaces to fix the issue. M +1-0core/backends/lan/lanlinkprovider.cpp https://invent.kde.org/network/kdeconnect-kde/commit/390a44a901de2a887fa37c7f7c6cdb20fd50a371 -- You are receiving this mail because: You are watching all bug changes.
[kdeconnect] [Bug 458063] KDE Connect clipboard sharing syncs passwords copied from password managers
https://bugs.kde.org/show_bug.cgi?id=458063 Simon Redman changed: What|Removed |Added Status|ASSIGNED|RESOLVED Resolution|--- |FIXED Latest Commit||https://invent.kde.org/netw ||ork/kdeconnect-kde/commit/b ||9a089344efeb68ae4e6b5d780a3 ||9de398208fe3 --- Comment #6 from Simon Redman --- Git commit b9a089344efeb68ae4e6b5d780a39de398208fe3 by Simon Redman, on behalf of Yuchen Shi. Committed on 17/10/2022 at 21:04. Pushed by sredman into branch 'master'. Add config for clipboard plugin on content types to share. ## Summary This MR adds a config dialog for the Clipboard plugin, where the user can toggle whether to share password and/or anything else with other devices. Implements !39 According to previous discussion at !39 (and the bug linked), some users want to skip sending passwords to other devices while others rely on the existing behavior. This MR addresses that by allowing users to control those two types separately and will replace !39 if merged.  Borrowing the idea from !39, the `x-kde-passwordManagerHint` MIME data hint is used to determine whether the content is considered secret. I've tested this method with KeepassXC which [sets this correctly](https://github.com/keepassxreboot/keepassxc/blob/a6d3f973fa8449f0f7dac864b3bd3928c29c649f/src/gui/Clipboard.cpp#L62). See test plan below. In theory, MIME also can be used to test for images and another checkbox can be easily added should we decided to support images later. For now though, the enum and the config supports only passwords or "anything else". Both defaults to true, thus keeping full backwards compatibility. I've been keeping both unchecked since I only share in one direction (Android to Linux), which wasn't possible until this MR. Others may want to make their own choices. ## Test Plan Please reference the screenshot above for the steps. >From the indicator, right-click and select `Configure`. Select a device from the left side (or pair one if needed). In "available plugins", make sure "Clipboard" is checked, and verify that a "Configure" icon button is now shown on the right. Clicking that icon should bring up the new config dialog, where the two check boxes can be toggled as desired. Click on "OK" to save and apply the settings. Clicking on "Defaults" should bring both back to checked (the default behavior). Copy normal plain text from your favorite text editor and it should be sent to another device if the "anything else" checkbox is checked. I've tested this on an Android phone but I see no reason it won't work elsewhere given the code for sending has not been changed. (Feel free to test on other devices.) Open KeepassXC and select an entry, right click and select "Copy password". This sets the MIME hint so it should be treated as a password, controlled by the "passwords" checkbox. I've toggled the settings multiple times on and off. Once "OK" is clicked, the next clipboard change should pick up the latest settings. I've only tested on Linux desktops (Arch Linux) since I do not own a Mac. I don't believe any OS X application sets `x-kde-passwordManagerHint` at all, so they may be controlled by "anything else". M +11 -0plugins/clipboard/CMakeLists.txt A +56 -0plugins/clipboard/clipboard_config.cpp [License: GPL(3+eV) GPL(v3.0) GPL(v2.0)] A +34 -0plugins/clipboard/clipboard_config.h [License: GPL(3+eV) GPL(v3.0) GPL(v2.0)] A +69 -0plugins/clipboard/clipboard_config.ui M +16 -5plugins/clipboard/clipboardlistener.cpp M +7-2plugins/clipboard/clipboardlistener.h M +13 -1plugins/clipboard/clipboardplugin.cpp M +3-1plugins/clipboard/clipboardplugin.h M +1-0plugins/clipboard/kdeconnect_clipboard.json A +39 -0plugins/clipboard/kdeconnect_clipboard_config.qml [License: GPL(3+eV) GPL(v3.0) GPL(v2.0)] https://invent.kde.org/network/kdeconnect-kde/commit/b9a089344efeb68ae4e6b5d780a39de398208fe3 -- You are receiving this mail because: You are watching all bug changes.
[kdeconnect] [Bug 460218] kdeconnect SMS Feature Request: Limit number of conversations and messages to hasten loading
https://bugs.kde.org/show_bug.cgi?id=460218 Simon Redman changed: What|Removed |Added Latest Commit||5487d72c29176ddc7c87313c78a ||aead0c393732c Resolution|--- |FIXED Status|REPORTED|RESOLVED --- Comment #1 from Simon Redman --- Hi Nate, Assuming you have a recent (2 years) version of the Android and desktop apps, it will request only a few messages in a conversation and only once you click it the first time. https://invent.kde.org/network/kdeconnect-android/-/merge_requests/122 This MR was checked in today which returns conversations one at a time (in sorted order, hopefully), which dramatically reduces the amount of time to wait until the app is usable. https://invent.kde.org/network/kdeconnect-android/-/merge_requests/296 -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 459929] USB-C connected display goes black when mouse is moved from laptop display
https://bugs.kde.org/show_bug.cgi?id=459929 --- Comment #2 from Simon Redman --- Created attachment 152568 --> https://bugs.kde.org/attachment.cgi?id=152568=edit startplasma_wayland with QT_LOGGING_RULES="kwin_*.debug=true" I don't get anything interesting-looking in the log file. I switched to a TTY, ran `export QT_LOGGING_RULES="kwin_*.debug=true"` then `startplasma-wayland > ~/startplasma-wayland.log 2>&1`, reproduced my issue, and logged out. File attached. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 459929] New: USB-C connected display goes black when mouse is moved from laptop display
https://bugs.kde.org/show_bug.cgi?id=459929 Bug ID: 459929 Summary: USB-C connected display goes black when mouse is moved from laptop display Classification: Plasma Product: kwin Version: 5.25.5 Platform: Compiled Sources OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: wayland-generic Assignee: kwin-bugs-n...@kde.org Reporter: si...@ergotech.com Target Milestone: --- Created attachment 152551 --> https://bugs.kde.org/attachment.cgi?id=152551=edit dmesg with drm debugging SUMMARY After commit f07d6bd40034372b7176f57de080003c8a612d57, when I move my mouse from my laptop display to my externally-connected HDMI display, the second display goes black. If I have the Display Configuration open, it says that a devices has been removed and it needs to refresh. This video shows what I am experiencing: https://youtu.be/ncIfA-Q5Mxw Oddly, I am not able to reproduce this with just kwin_wayland running in a TTY. STEPS TO REPRODUCE 1. Log in to plasma Wayland with any build containing f07d6bd40034372b7176f57de080003c8a612d57 2. Move mouse from primary display onto USB-C connected HDMI display 3. OBSERVED RESULT Display "disconnects". EXPECTED RESULT Mouse moves smoothly from one display to the next. SOFTWARE/OS VERSIONS Linux/KDE Plasma: 5.19.8-200.fc36.x86_64 (available in About System) KDE Plasma Version: 5.25.5 KDE Frameworks Version: 5.98.0 Qt Version: 5.15.6 ADDITIONAL INFORMATION This is a dual GPU setup, with the laptop's internal display connected to an AMD 680M and the HDMI display connected over USB-C (evdi driver). Attached file contains the DRM logs, collected as described here: https://invent.kde.org/plasma/kwin/-/wikis/Debugging-DRM-issues -- You are receiving this mail because: You are watching all bug changes.
[kdeconnect] [Bug 458487] Share Plugin: URLs with titles should be shared as plain URLs
https://bugs.kde.org/show_bug.cgi?id=458487 Simon Redman changed: What|Removed |Added Severity|normal |wishlist -- You are receiving this mail because: You are watching all bug changes.
[kdeconnect] [Bug 458487] Share Plugin: URLs with titles should be shared as plain URLs
https://bugs.kde.org/show_bug.cgi?id=458487 Simon Redman changed: What|Removed |Added Keywords||junior-jobs --- Comment #1 from Simon Redman --- Tagging as junior job since this should hopefully be fairly simple. See https://invent.kde.org/network/kdeconnect-kde/-/merge_requests/484 where it was proposed to do this on the receiving side, and translate the behavior to the sending side. -- You are receiving this mail because: You are watching all bug changes.
[kdeconnect] [Bug 458487] New: Share Plugin: URLs with titles should be shared as plain URLs
https://bugs.kde.org/show_bug.cgi?id=458487 Bug ID: 458487 Summary: Share Plugin: URLs with titles should be shared as plain URLs Product: kdeconnect Version: unspecified Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: android-application Assignee: albertv...@gmail.com Reporter: si...@ergotech.com Target Milestone: --- SUMMARY Some apps (Google News, some RSS readers, probably others), when you share a link from them, send it in the form of "title \n url". KDE Connect should share just the URL (perhaps under a toggle switch, in case users like the "pretty" url) STEPS TO REPRODUCE 1. Share URL from certain applications using KDE Connect OBSERVED RESULT URL is opened in a text editor window with "title \n url" EXPECTED RESULT URL is opened in the default handler for the URL type. ADDITIONAL INFORMATION This ought to be caught and handled on the sending (Android) side, not on the receiving side. -- You are receiving this mail because: You are watching all bug changes.
[kdeconnect] [Bug 458304] Contacts not displaying in SMS application
https://bugs.kde.org/show_bug.cgi?id=458304 Simon Redman changed: What|Removed |Added Resolution|--- |NOT A BUG Status|CONFIRMED |RESOLVED --- Comment #3 from Simon Redman --- (In reply to Nicolas Fella from comment #2) > Sounds like kpeoplevcard is missing Good catch. That was exactly what I needed. Considering this issue closed. -- You are receiving this mail because: You are watching all bug changes.
[kdeconnect] [Bug 458304] Contacts not displaying in SMS application
https://bugs.kde.org/show_bug.cgi?id=458304 Simon Redman changed: What|Removed |Added Status|REPORTED|CONFIRMED Ever confirmed|0 |1 --- Comment #1 from Simon Redman --- Mailing list user reported the same issue. Marking this bug as "CONFIRMED". -- You are receiving this mail because: You are watching all bug changes.
[kdeconnect] [Bug 458304] New: Contacts not displaying in SMS application
https://bugs.kde.org/show_bug.cgi?id=458304
Bug ID: 458304
Summary: Contacts not displaying in SMS application
Product: kdeconnect
Version: unspecified
Platform: Other
OS: Linux
Status: REPORTED
Severity: normal
Priority: NOR
Component: messaging-application
Assignee: si...@ergotech.com
Reporter: si...@ergotech.com
Target Milestone: ---
SUMMARY
Suddenly the SMS application is not resolving phone numbers to contact names.
Given that this happened without any code changes on our side, I suspect it is
caused by some dependency.
STEPS TO REPRODUCE
1. Verify the Contacts plugin has put contact cards in
~/.local/share/kpeoplevcard/{deviceId}-kdeconnect
2. Launch SMS application
OBSERVED RESULT
SMS application displays the list of conversations but with phone numbers
instead of contact names
EXPECTED RESULT
SMS application displays the list of conversations with contact names
SOFTWARE/OS VERSIONS
Linux/KDE Plasma: 5.25.4
KDE Plasma Version: 5.25.4
KDE Frameworks Version: 5.97.0
Qt Version: 5.15.5
ADDITIONAL INFORMATION
Issue has been present for at least a month. I don't remember when I took
system updates well enough to correlate.
--
You are receiving this mail because:
You are watching all bug changes.
[kdeconnect] [Bug 401677] Some phone models, ROMs or Apps don't report SMS History
https://bugs.kde.org/show_bug.cgi?id=401677 Simon Redman changed: What|Removed |Added Status|CONFIRMED |RESOLVED Resolution|--- |FIXED --- Comment #113 from Simon Redman --- Making as resolved since nobody appears to be having problems post my workaround. -- You are receiving this mail because: You are watching all bug changes.
[kdeconnect] [Bug 336726] It is possible to spam a KDE Connect user with pairing requests
https://bugs.kde.org/show_bug.cgi?id=336726 Simon Redman changed: What|Removed |Added CC||si...@ergotech.com Status|ASSIGNED|CONFIRMED --- Comment #3 from Simon Redman --- We discussed this in a developer meeting at one point and decided it would be best to have a "smart" system where if a device sends too many pairing requests in a short period (spam) the local device automatically starts ignoring that device. -- You are receiving this mail because: You are watching all bug changes.
[kdeconnect] [Bug 456140] KDE Connect contacts sync only partially working
https://bugs.kde.org/show_bug.cgi?id=456140 Simon Redman changed: What|Removed |Added CC||si...@ergotech.com Status|REPORTED|RESOLVED Resolution|--- |INTENTIONAL --- Comment #3 from Simon Redman --- (In reply to raguse from comment #2) > Thanks @Nicholas for the answer. > I know about the complexity of a real 2-way sync. However, it would be quite > a core functionality of such an application like KDE Connect. > > Are there plans to to enhance this in the near term to allow optimal > integration with KDE PIM? > Technically most of the needed is there already, just not the sync. There is nobody working on adding two-way sync to the contacts plugin. I don't know about KDE PIM, but if other apps wanted to use KDE Connect's vcards, they could use the KPeople library to access them (the same way the SMS app does) -- You are receiving this mail because: You are watching all bug changes.
