Android Studio 启动时崩溃

Question

好吧，简单说一下，我最近将我的新 Lenovo y50 设置为双启动 Arch 和 Windows 8.1。我使用 Arch Linux 作为我的开发环境。我可以启动 Android Studio 5.6，然后更新到 6.1。更新后(这发生在 6.0 和 6.1 上)，它几乎开始加载我的项目，并且它杀死了我的笔记本电脑。没有错误屏幕或报告，只是立即关闭。我查看了日志，恐怕我对内核操作不够熟悉，无法理解这些错误。以下输出来自命令 journalctl --since=today:

    Jun 19 21:51:04 Archer /etc/gdm/Xsession[6315]: Window manager warning: Log level 16: STACK_OP_RAISE_ABOVE: sibling window 0x2000d07 not in stack
    Jun 19 21:55:43 Archer /etc/gdm/Xsession[6315]: [1352606]   WARN - api.vfs.impl.local.FileWatcher - Watcher terminated with exit code 0
    Jun 19 21:55:43 Archer /etc/gdm/Xsession[6315]: Java HotSpot(TM) 64-Bit Server VM warning: ignoring option MaxPermSize=350m; support was removed in 8.0
    Jun 19 21:55:55 Archer /etc/gdm/Xsession[6315]: Java HotSpot(TM) 64-Bit Server VM warning: ignoring option MaxPermSize=350m; support was removed in 8.0
    Jun 19 21:55:57 Archer /etc/gdm/Xsession[6315]: Window manager warning: Invalid WM_TRANSIENT_FOR window 0x2000024 specified for 0x200002b ( ).
    Jun 19 21:56:07 Archer /etc/gdm/Xsession[6315]: SLF4J: Failed to load class "org.slf4j.impl.StaticLoggerBinder".
    Jun 19 21:56:07 Archer /etc/gdm/Xsession[6315]: SLF4J: Defaulting to no-operation (NOP) logger implementation
    Jun 19 21:56:07 Archer /etc/gdm/Xsession[6315]: SLF4J: See http://www.slf4j.org/codes.html#StaticLoggerBinder for further details.
    Jun 19 21:56:07 Archer /etc/gdm/Xsession[6315]: 21:56:07.157 [Connection worker] DEBUG o.g.t.i.provider.DefaultConnection - Tooling API provider 1.12 created.
    Jun 19 21:56:07 Archer /etc/gdm/Xsession[6315]: 21:56:07.386 [Connection worker] DEBUG o.g.t.i.provider.ProviderConnection - Configuring logging to level: INFO
    Jun 19 21:56:07 Archer /etc/gdm/Xsession[6315]: Tooling API is using target Gradle version: 1.12.
    Jun 19 21:56:07 Archer /etc/gdm/Xsession[6315]: Tooling API is using target Gradle version: 1.12.
    Jun 19 21:56:09 Archer /etc/gdm/Xsession[6315]: Could not determine classpath for class org.gradle.util.GradleVersion
    Jun 19 21:56:09 Archer /etc/gdm/Xsession[6315]: Could not determine classpath for class org.slf4j.LoggerFactory
    Jun 19 21:56:09 Archer /etc/gdm/Xsession[6315]: Starting Gradle daemon
    Jun 19 21:56:09 Archer /etc/gdm/Xsession[6315]: Starting daemon process: workingDir = /home/kaleb/.gradle/daemon/1.12, daemonArgs: [/opt/java/bin/java, -XX:MaxPermSize=256m, -XX:+HeapDump
    Jun 19 21:56:09 Archer /etc/gdm/Xsession[6315]: Starting process 'Gradle build daemon'. Working directory: /home/kaleb/.gradle/daemon/1.12 Command: /opt/java/bin/java -XX:MaxPermSize=256m
    Jun 19 21:56:09 Archer /etc/gdm/Xsession[6315]: Successfully started process 'Gradle build daemon'
    Jun 19 21:37:15 Archer /etc/gdm/Xsession[6315]: at com.intellij.openapi.externalSystem.util.ExternalSystemUtil$3.execute(ExternalSystemUtil.java:467)
    Jun 19 21:37:15 Archer /etc/gdm/Xsession[6315]: at com.intellij.openapi.externalSystem.util.ExternalSystemUtil$4$2.run(ExternalSystemUtil.java:546)
    Jun 19 21:37:15 Archer /etc/gdm/Xsession[6315]: at com.intellij.openapi.progress.impl.ProgressManagerImpl$TaskRunnable.run(ProgressManagerImpl.java:464)
    Jun 19 21:37:15 Archer /etc/gdm/Xsession[6315]: at com.intellij.openapi.progress.impl.ProgressManagerImpl$2.run(ProgressManagerImpl.java:178)
    Jun 19 21:37:15 Archer /etc/gdm/Xsession[6315]: at com.intellij.openapi.progress.ProgressManager.executeProcessUnderProgress(ProgressManager.java:209)
    Jun 19 21:37:15 Archer /etc/gdm/Xsession[6315]: at com.intellij.openapi.progress.impl.ProgressManagerImpl.executeProcessUnderProgress(ProgressManagerImpl.java:212)
    Jun 19 21:37:15 Archer /etc/gdm/Xsession[6315]: at com.intellij.openapi.progress.impl.ProgressManagerImpl.runProcess(ProgressManagerImpl.java:171)
    Jun 19 21:37:15 Archer /etc/gdm/Xsession[6315]: at com.intellij.openapi.progress.impl.ProgressManagerImpl$8.run(ProgressManagerImpl.java:373)
    Jun 19 21:37:15 Archer /etc/gdm/Xsession[6315]: at com.intellij.openapi.application.impl.ApplicationImpl$8.run(ApplicationImpl.java:419)
    Jun 19 21:37:15 Archer /etc/gdm/Xsession[6315]: at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:511)
    Jun 19 21:37:15 Archer /etc/gdm/Xsession[6315]: at java.util.concurrent.FutureTask.run(FutureTask.java:266)
    Jun 19 21:37:15 Archer /etc/gdm/Xsession[6315]: at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142)
    Jun 19 21:37:15 Archer /etc/gdm/Xsession[6315]: at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617)
    Jun 19 21:37:15 Archer /etc/gdm/Xsession[6315]: at java.lang.Thread.run(Thread.java:745)
    Jun 19 21:37:15 Archer /etc/gdm/Xsession[6315]: at com.intellij.openapi.application.impl.ApplicationImpl$1$1.run(ApplicationImpl.java:149)
    Jun 19 21:37:15 Archer /etc/gdm/Xsession[6315]: [ 244688]   WARN - .project.GradleProjectImporter -
    Jun 19 21:40:10 Archer /etc/gdm/Xsession[6315]: (nemo:6397): librsvg-WARNING **: CSS parsing error
    Jun 19 21:40:10 Archer /etc/gdm/Xsession[6315]: (nemo:6397): librsvg-WARNING **: CSS parsing error
    Jun 19 21:40:38 Archer /etc/gdm/Xsession[6315]: (nemo:6397): librsvg-WARNING **: CSS parsing error
    Jun 19 21:40:38 Archer /etc/gdm/Xsession[6315]: (nemo:6397): librsvg-WARNING **: CSS parsing error
    Jun 19 21:50:36 Archer gdm-Xorg-:0[495]: (II) intel(0): switch to mode 1920x1080@60.1 on eDP1 using pipe 0, position (0, 0), rotation normal, reflection none
    Jun 19 21:50:40 Archer cinnamon-screensaver-dialog[7179]: pam_tally(cinnamon-screensaver:auth): Error opening /var/log/faillog for update
    Jun 19 21:50:40 Archer cinnamon-screensaver-dialog[7179]: pam_tally(cinnamon-screensaver:auth): Error opening /var/log/faillog for read
    Jun 19 21:50:44 Archer cinnamon-screensaver-dialog[7179]: pam_tally(cinnamon-screensaver:setcred): Error opening /var/log/faillog for update
    Jun 19 21:50:44 Archer cinnamon-screensaver-dialog[7179]: pam_tally(cinnamon-screensaver:setcred): Error opening /var/log/faillog for update

非常感谢任何帮助!

编辑:我不知道发生了什么，但我重新启动了大约 6 次，创建了另一个 android 项目以查看它是否会崩溃，并多次打开和关闭 Android Studio 以尝试再次破坏它。无论出于何种原因，现在一切似乎都运行良好。

Answer 1

使用您的设备更新版本检查您的 list 目标并尝试。

<uses-sdk android:minSdkVersion="?" />
<uses-sdk android:maxSdkVersion="?" />