https://bugs.kde.org/show_bug.cgi?id=425638
Philip C <cliabh...@gmail.com> changed:
What |Removed |Added
----------------------------------------------------------------------------
CC| |cliabh...@gmail.com
Resolution|--- |WAITINGFORINFO
Status|CONFIRMED |NEEDSINFO
--- Comment #22 from Philip C <cliabh...@gmail.com> ---
(In reply to Nathan from comment #16)
> > (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?
>
> I've installed adb and can confirm that my computer sees my device.
>
> :$ adb devices
> List of devices attached
> R5CT10HN9MP device
>
> I've tried both, running "adb logcat org.kde.kdeconnect:I *:S >
> kdeconnect-logcat.txt" before and after trying to send an SMS message from
> my PC, but in both cases, it just sits there waiting and the file is empty.
> I sent a reply from the notification while the logcat was running, but
> nothing populate the file then either.
That is odd. If you're still up for it, could I trouble you try running
"adb logcat" or "adb shell logcat" alone, and see if that shows anything
at all? You should get a very large output. Don't attach the output here,
mind, as it'll likely have sensitive information from other apps on the
phone.
--
You are receiving this mail because:
You are watching all bug changes.
