[kdeconnect] [Bug 392594] KDE Connect crashes after establishing connection

[Mykola Krachkovsky]

https://bugs.kde.org/show_bug.cgi?id=392594

Mykola Krachkovsky  changed:

   What|Removed |Added

 Status|REOPENED|RESOLVED
 Resolution|--- |WORKSFORME

--- Comment #12 from Mykola Krachkovsky  ---
So, my old phone is broken and I don't use it anymore. Closing as not actual,
as KDE Connect works fine on newer Androids.

-- 
You are receiving this mail because:
You are watching all bug changes.

[kdeconnect] [Bug 392594] KDE Connect crashes after establishing connection

[Mykola Krachkovsky]

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 watching all bug changes.

[kdeconnect] [Bug 392594] KDE Connect crashes after establishing connection

[Mykola Krachkovsky]

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_DISPOSITION_DEFAULT (I suppose) was just
optimized out, as that's a final static field.

-- 
You are receiving this mail because:
You are watching all bug changes.

[kdeconnect] [Bug 392594] KDE Connect crashes after establishing connection

[Mykola Krachkovsky]

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
class is made from gui thread (and fails when from non-gui). Adding nothing
doing log to MainActivity:

Log.d("MainActivity", "Current RemoteKeyboardPlugin instance: " +
RemoteKeyboardService.instance);

Fixes future call and everything seems works fine after that.
Sounds crazy. It looks like some bug of Android 4.4 to me. I'm not sure how to
fix it properly, calling log looks too hacky.

I've tried to access InputMethodService.BACK_DISPOSITION_DEFAULT but that
hadn't effect.

I'm not sure about static initializers, but couldn't find anything else.

-- 
You are receiving this mail because:
You are watching all bug changes.

[kdeconnect] [Bug 392594] KDE Connect crashes after establishing connection

[Matthijs Tijink]

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 should be clear enough).

-- 
You are receiving this mail because:
You are watching all bug changes.

[kdeconnect] [Bug 392594] KDE Connect crashes after establishing connection

[Mykola Krachkovsky]

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.ExceptionInInitializerError
E/AndroidRuntime(12161):at
org.kde.kdeconnect.Plugins.RemoteKeyboardPlugin.RemoteKeyboardPlugin.onCreate(RemoteKeyboardPlugin.java:123)
E/AndroidRuntime(12161):at
org.kde.kdeconnect.Device.addPlugin(Device.java:741)
E/AndroidRuntime(12161):at
org.kde.kdeconnect.Device.reloadPluginsFromSettings(Device.java:830)
E/AndroidRuntime(12161):at
org.kde.kdeconnect.Device.addLink(Device.java:516)
E/AndroidRuntime(12161):at
org.kde.kdeconnect.BackgroundService$5.onConnectionReceived(BackgroundService.java:192)
E/AndroidRuntime(12161):at
org.kde.kdeconnect.Backends.BaseLinkProvider.connectionAccepted(BaseLinkProvider.java:48)
E/AndroidRuntime(12161):at
org.kde.kdeconnect.Backends.LanBackend.LanLinkProvider.addLink(LanLinkProvider.java:315)
E/AndroidRuntime(12161):at
org.kde.kdeconnect.Backends.LanBackend.LanLinkProvider.access$100(LanLinkProvider.java:70)
E/AndroidRuntime(12161):at
org.kde.kdeconnect.Backends.LanBackend.LanLinkProvider$3.handshakeCompleted(LanLinkProvider.java:247)
E/AndroidRuntime(12161):at
com.android.org.conscrypt.OpenSSLSocketImpl.notifyHandshakeCompletedListeners(OpenSSLSocketImpl.java:582)
E/AndroidRuntime(12161):at
com.android.org.conscrypt.OpenSSLSocketImpl.startHandshake(OpenSSLSocketImpl.java:444)
E/AndroidRuntime(12161):at
org.kde.kdeconnect.Backends.LanBackend.LanLinkProvider$4.run(LanLinkProvider.java:267)
E/AndroidRuntime(12161):at java.lang.Thread.run(Thread.java:841)
E/AndroidRuntime(12161): Caused by: java.lang.RuntimeException: Can't create
handler inside thread that has not called Looper.prepare()
E/AndroidRuntime(12161):at android.os.Handler.(Handler.java:200)
E/AndroidRuntime(12161):at android.os.Handler.(Handler.java:114)
E/AndroidRuntime(12161):at
android.inputmethodservice.InputMethodService.(InputMethodService.java:315)
E/AndroidRuntime(12161):... 13 more


As you can't reproduce, I'll try to debug it on my side. Are sources [1] and
Android Studio are enough for build/debug?

[1] https://cgit.kde.org/kdeconnect-android.git/

-- 
You are receiving this mail because:
You are watching all bug changes.

[kdeconnect] [Bug 392594] KDE Connect crashes after establishing connection

[Mykola Krachkovsky]

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.

[kdeconnect] [Bug 392594] KDE Connect crashes after establishing connection

[Matthijs Tijink]

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? You may be prompted to first remove the old app.

-- 
You are receiving this mail because:
You are watching all bug changes.

[kdeconnect] [Bug 392594] KDE Connect crashes after establishing connection

[Mykola Krachkovsky]

https://bugs.kde.org/show_bug.cgi?id=392594

Mykola Krachkovsky  changed:

   What|Removed |Added

 Resolution|BACKTRACE   |---
 Ever confirmed|0   |1
 Status|NEEDSINFO   |REOPENED

--- Comment #4 from Mykola Krachkovsky  ---
I should've changed status to reopened, right?

-- 
You are receiving this mail because:
You are watching all bug changes.

[kdeconnect] [Bug 392594] KDE Connect crashes after establishing connection

[Mykola Krachkovsky]

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=edit
adb logcat

Sure, here it is.

-- 
You are receiving this mail because:
You are watching all bug changes.

[kdeconnect] [Bug 392594] KDE Connect crashes after establishing connection

[Aleix Pol]

https://bugs.kde.org/show_bug.cgi?id=392594

Aleix Pol  changed:

   What|Removed |Added

 CC||aleix...@kde.org
 Resolution|--- |BACKTRACE
 Status|UNCONFIRMED |NEEDSINFO

--- Comment #2 from Aleix Pol  ---
Please provide the information Matthijs requested.

-- 
You are receiving this mail because:
You are watching all bug changes.

[kdeconnect] [Bug 392594] KDE Connect crashes after establishing connection

[Matthijs Tijink]

https://bugs.kde.org/show_bug.cgi?id=392594

Matthijs Tijink  changed:

   What|Removed |Added

 CC||matthijstij...@gmail.com

--- Comment #1 from Matthijs Tijink  ---
Can you post a log of the crash? You can do this by running "adb logcat >
log.txt" from the command line, while your device is plugged in your desktop.

-- 
You are receiving this mail because:
You are watching all bug changes.