search

TheAssassin / AppImageLauncher

Helper application for Linux distributions serving as a kind of "entry point" for running and integrating AppImages
https://assassinate-you.net/tags/appimagelauncher/
MIT License
5.54k stars 264 forks source link

appimagelauncher crashes desktop and wont allow login to desktop after reboot #612

Open Allan-Shand opened 10 months ago

Allan-Shand commented 10 months ago

Pre-submit checks

Describe the bug

After updating the "where to put my appimages" option desktop freezes and after hard reset login to desktop fails

Expected behavior

nothing initially but appimages being sent to this directory after being integrated

Steps to reproduce the issue

add a directory to the "where to put my appimages" option and confirm the updated configuration

Screenshots

No response

Distribution and desktop environment

Operating System: Manjaro Linux KDE Plasma Version: 5.27.10 KDE Frameworks Version: 5.112.0 Qt Version: 5.15.11 Kernel Version: 6.5.13-4-MANJARO (64-bit) Graphics Platform: Wayland

Tested on xorg session as well with same result

Installed AppImageLauncher version

Package listed in Manjaro repo 2.2.0-9

List of AppImages you tried

No response

Additional context

No response

Misoder commented 10 months ago

I ran into the exact same problem on OpenSUSE Tumbleweed with KDE 5. Downloaded the latest rpm from the releases page. Unable to login with my user. Was able to login as root and tried to clear my .cache and .config folders in my users home dir but that didn't help.

Allan-Shand commented 10 months ago

phew thought I was the only one this had happened to (nothing came up in a google search) hence the starting of this issue report. I have another laptop that had exactly the same issue I'm going to see if i can replicate it over christmas and do some tty investigation.

OWL4C commented 7 months ago

Hi, i am running Kubuntu 23.10 and had the same error, as well as hangs whenever launching an Appimage, as well as random hangs after installation, possibly related to #618, but with higher intensity, sometimes freezing the entire desktop multiple minutes. @Misoder i had luck clearing both .cache and .config, but sometimes it didn't work then either. Clearing (both+).local fixed all of these cases. Since this is quite old i am guessing this is to late to help, and you can't test this fix?

618 did some sleuthing, maybe between all of us we can figure out what the problem is exactly

TheAssassin commented 5 months ago

Can you confirm that this is an issue with appimagelauncherd? I can't reproduce the issue at the moment.

krom commented 5 months ago

I upgraded from latest version of Kubuntu 23.10 to just released Kubuntu 24.04 and faced with same issue. I use sddm and X11

I use ~/Appications folder for apps

AppImageLauncher version

$ AppImageLauncher --appimagelauncher-version 
AppImageLauncher version 2.2.0 (git commit 0f91801), built on 2020-09-29 21:36:15 UTC

System

OS: Kubuntu 24.04 LTS x86_64 
Host: MS-7C94 1.0 
Kernel: 6.8.0-31-generic 
Uptime: 26 mins 
Packages: 4233 (dpkg), 85 (flatpak), 41 (snap) 
Shell: zsh 5.9 
Resolution: 1920x1080, 3840x2160 
DE: Plasma 5.27.11 
WM: KWin 
Theme: Breeze Dark [Plasma], Breeze [GTK2/3] 
Icons: [Plasma], breeze-dark [GTK2/3] 
Terminal: yakuake 
CPU: AMD Ryzen 7 5700G with Radeon Graphics (16) @ 4.851GHz 
GPU: NVIDIA GeForce RTX 2060 SUPER 
Memory: 7671MiB / 64183MiB

I have 10 apps in ~/Application folder but I didn't change apps before upgrade from Kubuntu 23.10 to 24.04

After loging in SDDM

plasmashell_x11 uses 100% of cpu and hangs

how to reproduce

Rename Applications_old to Applications

how to temporary fix

  1. Rename Allications to Applications_old
  2. Remove ~/.local/share

I plan to compare .local/share folder before and after renamting folder to Applications for changes

dptsolutions commented 4 months ago

I have encountered similar to what @krom experienced on a clean installation of Kubuntu 24.04, albeit with the home directory of my user copied over from the install of my previous computer, which was running Kubuntu 22.04.

Immediately after dragging and dropping a new appimage into the folder that I have monitored for auto-installation (~/appimage), the system starts to hang. I dropped into another TTY and ran htop and found that one of the CPU cores was fully pegged at 100% for the process /usr/bin/kded5, and mem usage creeping up. Then after a reboot I encountered what @krom experienced - startplasma_x11 pegs a core at 100%, and mem usage creeps up.

The solution I found was similar, but a bit more targeted. I took the following steps, some of which I took as suggestion from this forum post which referenced this post.

  1. Remove all appimages from ~/appimage
  2. Delete all files from ~/.local/share/mime/packages
  3. Delete ~/.local/share/mime/mime.cache
  4. Reboot

After that all is well, and I rebuilt my mime cache using the update-mime-database ~/.local/share/mime command referenced in the second post.

I attempted to install both the current stable release, and the latest continuous build from the releases page, same behavior with both when attempting to drag and drop an appimage into ~/appimage.

I also noticed these things during my replication of the issue:

  1. During both attempts, there were two files that started with appimagekit_ (sorry I don't have the full filenames) in the ~/.local/share/mime/packages folder And during the second attempt, they were the only files in the packages folder.
  2. During the first attempt using the stable release, iif I attempted to cat ~/.local/share/mime/mime.cache, somewhere during it's output to my screen the character set rendered to the terminal would go all wonky, and wouldn't be fixed until reboot. Not sure if that's related but including it as interesting.

System Info

Operating System: Kubuntu 24.04
KDE Plasma Version: 5.27.11
KDE Frameworks Version: 5.115.0
Qt Version: 5.15.13
Kernel Version: 6.8.0-31-generic (64-bit)
Graphics Platform: X11
Processors: 16 × AMD Ryzen 7 7840U w/ Radeon 780M Graphics
Memory: 60.6 GiB of RAM
Graphics Processor: AMD Radeon Graphics
Manufacturer: Framework
Product Name: Laptop 13 (AMD Ryzen 7040Series)
System Version: A7
krom commented 4 months ago

I compared the catalogs and came to a similar conclusion with @dptsolutions Looks like is needed to check how to applauncher creates files in ~/.local/share/applications

I also added files to ~/appimage one at a time and checked, at first everything was fine, then it broke on a certain file

konotorii commented 2 days ago

Wanted to confirm that this still happens.

System Info

OS: Kubuntu 24.04.1 LTS x86_64 
Host: B650M Pro RS WiFi 
Kernel: 6.8.0-47-generic 
Uptime: 2 mins 
Packages: 2952 (dpkg), 25 (snap) 
Shell: bash 5.2.21 
Resolution: 2560x1440, 2560x1440 
DE: Plasma 5.27.11 
WM: KWin 
Theme: [Plasma], Breeze [GTK2/3] 
Icons: [Plasma], candy-icons [GTK2/3] 
Terminal: konsole 
CPU: AMD Ryzen 5 7600X (12) @ 5.453GHz 
GPU: NVIDIA GeForce RTX 3060 Ti Lite Hash Rate 
GPU: AMD ATI 0e:00.0 Raphael 
Memory: 5432MiB / 31203MiB

Ended up deleting the following:

Timeline of events

  1. I installed appimagelauncher_2.2.0-travis995.0f91801.bionic_amd64
  2. I then installed WhatPulse, Arduino IDE, balena Etcher, and Cura UtilMaker.
  3. Cura and WhatPulse opened just fine, after a few minutes KDE Plasma crashed and gave me a black screen so I restarted in hopes that would fix the issue.
  4. Was met with the black screen after login and an unknown error popup after a few minutes.
  5. Had to use a manjaro live boot USB to go into file directory and delete all the files.

I did also observe that when the error popup came and I pressed Developer information, It showed me a list of required packages that weren't installed. All the required packages had something with Qt5. I could experiment and go back to get the full list instead of going off memory...

Edit: I misremembered what happened when I restarted my computer for the first time.

OWL4C commented 1 day ago

This is not a fix, but i am now running Gearlever on my Desktop to manage my appimages, and it works great, i think i prefer it's gui over appimagelaunchers in some situations. On my Laptop i am still running appimagelauncher without problems. (Even though at some points i had the same appimages installed on both)