https://bugs.kde.org/show_bug.cgi?id=392594
Mykola Krachkovsky changed:
What|Removed |Added
Status|REOPENED|RESOLVED
Resolution|---
https://bugs.kde.org/show_bug.cgi?id=392594
--- Comment #11 from Mykola Krachkovsky ---
And still, that's not a full solution. When KDE Connect GUI isn't started and
connection made from background thread it still crashes until GUI is opened.
--
You are receiving this mail because:
You are watc
https://bugs.kde.org/show_bug.cgi?id=392594
--- Comment #10 from Mykola Krachkovsky ---
Opps, missed this from my logs, static initializer, clinit:
E/AndroidRuntime(12161):at
android.inputmethodservice.InputMethodService.(InputMethodService.java:315)
And call to InputMethodService.BACK_D
https://bugs.kde.org/show_bug.cgi?id=392594
--- Comment #9 from Mykola Krachkovsky ---
Ok, so what I've found, problem seems is in calling of some of static
initializers of RemoteKeyboardService or its super classes
(InputMethodService?). This static initializer works fine if first access to
clas
https://bugs.kde.org/show_bug.cgi?id=392594
--- Comment #8 from Matthijs Tijink ---
Yeah, looks identical. It'd be great if you could debug this, or at least
provide the full backtrace!
Android Studio and the code should indeed be enough (it'll prompt you to
install SDK components, but those sho
https://bugs.kde.org/show_bug.cgi?id=392594
--- Comment #7 from Mykola Krachkovsky ---
Exception looks similar:
E/AndroidRuntime(12161): FATAL EXCEPTION: Thread-22405
E/AndroidRuntime(12161): Process: org.kde.kdeconnect_tp, PID: 12161
E/AndroidRuntime(12161): java.lang.ExceptionInInitializerErro
https://bugs.kde.org/show_bug.cgi?id=392594
--- Comment #6 from Mykola Krachkovsky ---
Hmm. Crashes anyway, I'll try to see logcat later.
--
You are receiving this mail because:
You are watching all bug changes.
https://bugs.kde.org/show_bug.cgi?id=392594
--- Comment #5 from Matthijs Tijink ---
Unfortunately, I can't reproduce the issue myself.
If you open https://phabricator.kde.org/D12073 however, I tried to create a
fix. Could you download and install the APK and report back if that fixes the
issue?
https://bugs.kde.org/show_bug.cgi?id=392594
Mykola Krachkovsky changed:
What|Removed |Added
Resolution|BACKTRACE |---
Ever confirmed|0
https://bugs.kde.org/show_bug.cgi?id=392594
--- Comment #3 from Mykola Krachkovsky ---
Created attachment 111904
--> https://bugs.kde.org/attachment.cgi?id=111904&action=edit
adb logcat
Sure, here it is.
--
You are receiving this mail because:
You are watching all bug changes.
https://bugs.kde.org/show_bug.cgi?id=392594
Aleix Pol changed:
What|Removed |Added
CC||aleix...@kde.org
Resolution|---
https://bugs.kde.org/show_bug.cgi?id=392594
Matthijs Tijink changed:
What|Removed |Added
CC||matthijstij...@gmail.com
--- Comment #1 from
12 matches
Mail list logo