-
Notifications
You must be signed in to change notification settings - Fork 208
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
phantom yad clicks #2575
Comments
Hello there 👋 Please respond as soon as possible if a Pi-Apps maintainer requests more information from you. Stale issues will be closed after a lengthy period of time with no response. |
Pi-Apps tries to run quickly, so when you are viewing the main top level of blue categories, the subcategories are being generated in the background. This involves reading a lot of files, so with a really slow SD card, you may encounter a brief freeze. What kind of drive are you using to boot the Pi from? Have you benchmarked it with the |
im booting from a sd card and the diag gives it a pass |
OK try this command and see if it causes the 100% cpu issue:
Please give it a few seconds. On my Pi4 it would usually only use some cpu in the first couple seconds. |
alright would you like a video of the issue that is happening? |
I ran the command and it says |
ok, so then if you open pi-apps again, does it still have the 100% cpu issue? |
yes |
Yeah that is strange. I would like to connect to your system using TeamViewer to have a look for myself. Please install Teamviewer with this command:
And then launch TeamViewer from Menu -> Internet, accept the terms and conditions, and then send me the ID and password in a private discord message to @Botspot. |
Fixed dev connected tryed reproducing didnt work while dev was connected worked after a reboot and dev was disconnected after changing theme to another and changing it back the issue now doesnt seem to happen |
so basically, I could never reproduce it while connected to @thepotatolover with RustDesk, and after disconnecting, @thepotatolover could still not reproduce it until rebooting. @thepotatolover then switched to the xlunch theme, which worked fine, then switched back to yad-default where this issue no longer occurs. @thepotatolover will re-open this issue if the issue returns. My theory is it's something graphics-related somehow causing |
Yeah that is very strange. As indicated by the terminal logs yad is registering repeated clicks (calling That could be some strange filsystem corruption but I think it would need to be very specific. Maybe they are leaving out critical information like the presence of a rogue virtual mouse or touchscreen causing these phantom clicks. Regardless its not a pi-apps issue itself. |
Tryed on 2 installs 1 on a usb ssd and an sd card and they both gave the same issue only had 1 keyboard and mouse that also works fine nothing else was plugged into usb except the mouse and keyboard and the usb ssd when i was booting from the ssd otherwise it would of just been the keyboard and mouse |
also they was both clean installs from the raspberry pi imager |
Can not reproduce on a fresh image
As I said before, this is not a pi-apps issue. This appears to be a hardware issue. Your video can only be simulated by spamming the mouse left click on the GUI at very high frequency (looks like 20 times per second in your video). Try using different peripherals (keyboard and mouse). |
i did same issue |
I don't really have any answer for you than swap out hardware one by one. it is simply impossible to trigger multiple |
@thepotatolover were there ever any more updates to this? This is a very strange issue and you have been the only one to ever report it. |
Closing as unactionable. |
Confirmations
What happened?
Clicking any app to install it maxes out cpu and causes the os to lock up
Description
Newest version of pi apps on rpi 4 8gb newest rpi os 64bit
When i click any app to install it, it then causes the cpu to go to 100% and eventually the os locks up fully for no reason
What are your system specs (run the following command in your terminal)?
(Recommended) Error log? Terminal output? Debug messages?
The text was updated successfully, but these errors were encountered: