Project

General

Profile

Issue #1872

dandelion* 1.0.8 breaks Replicant 6.0

Added by ariel enter over 2 years ago. Updated over 2 years ago.

Status:
Resolved
Priority:
Normal
Assignee:
-
Category:
-
Target version:
Start date:
02/06/2018
Due date:
% Done:

0%

Estimated time:
Resolution:
fixed
Device:

Description

General information

dandelion* 1.0.8
Andrid 6.0.1, Replicant 6.0, Galaxy S2 I9100

Description

When dandelion* 1.0.8 (Diaspora-for-Android) is installed on replicant 6.0, many apps start crashing, including trebuchet, f-droid and com.android.settings.Settings. It is impossible to access the app list and the only way I found to recover is to uninstall it with the following adb command:

adb uninstall com.github.dfa.diaspora_android

Some times the phone restarts all together.

I'm sending some info I got from CatLog app. I already opened an issue on dandelion*'s website, but I'm not sure where the problem is.

https://github.com/Diaspora-for-Android/dandelion/issues/187

Thank you.


Files

2018-02-05-16-00-32.txt (32.9 KB) 2018-02-05-16-00-32.txt ariel enter, 02/06/2018 06:31 PM
tombstones.zip (122 KB) tombstones.zip ariel enter, 02/06/2018 06:31 PM

History

#1

Updated by ariel enter over 2 years ago

I should had said that this doesn't happen with the previous version 1.0.6

Thank you.

#2

Updated by ariel enter over 2 years ago

@gsantner, the dandelion*'s developer, suggest that, this replicant behavior might indicate a vulnerability on the system that might be exploit. https://github.com/Diaspora-for-Android/dandelion/issues/187#issuecomment-363543399

I hope is noting to worry about.

#3

Updated by ariel enter over 2 years ago

I just installing the newest version of Conversations 1.23.4 and it gave the same results which makes me believe that the issue affects the installation of all new apps. At least the newest builds.

Am I the only one having this problems?

I just opened a ticket at f-droid:

https://gitlab.com/fdroid/fdroidclient/issues/1321

Thank you.

#4

Updated by ariel enter over 2 years ago

Seems this issue is already been taken care of: https://gitlab.com/fdroid/fdroiddata/issues/979

Sorry I couldn't find it earlier before posting. We can close this issue now.

#5

Updated by Fil Bergamo over 2 years ago

  • Status changed from New to Resolved
  • Resolution set to fixed

Closing as requested by OP, as it's fixed in F-Droid.

Also available in: Atom PDF