-
Notifications
You must be signed in to change notification settings - Fork 6
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
Fails to start #53
Comments
Thank you for reporting. Would you be able to start the app with
|
flatpak run net.mkiol.Jupii --verbose |
Hi. Sorry for the late reply. I have not been able to identify where the problem is, but... Would you be able to try if the same issue occurs also on new version 2.15.0? |
chris@fedora:~$ flatpak run net.mkiol.Jupii --verbose > ~/jupii.log |
So, nothing changed :/ I want to make sure, so when you start the app it just crashes without any UI, right? |
Yes. It might have shown the UI the first time, but I can't remember. That's because I have been trying several similar apps to try to communicate with my Blu-ray HDD player. |
If you're not already very tired of me asking for more logs, could please try to start the app with debugger? To do this, you need to install the Debug version of Jupii and Flatpak SDK. This can be done with the following command:
than, start the Flatpak sandbox:
than, start the debugger (inside Flatpak sandbox)
after the crash:
|
Since you are working on the problem for me, I can hardly complain about being asked for a log :)
That didn't work, so I did:
Loads of lines of output, the GUI started, and I exited with this on the terminal:
|
Now if I run it in the terminal, the GUI starts and I get:
It also works if I click the icon on the taskbar. Maybe the new SDK has fixed it? |
I'm super glad that it started working :) I have no idea what was wrong, but yes, most likely an update during installing the SDK solved the problem. |
Thanks for your prompt attention to the problem. |
The Fedora 41 error tracking report is:
--- Running report_uReport ---
Error: Unable to open './coredump': No such file or directory
--- Skipping collect_GConf ---
No matching actions found for this event.
--- Skipping collect_vimrc_system ---
No matching actions found for this event.
--- Skipping collect_vimrc_user ---
No matching actions found for this event.
--- Skipping collect_xsession_errors ---
No matching actions found for this event.
--- Running analyze_CCpp ---
Generating backtrace
Backtrace is generated and saved, 123811 bytes
Can't open file 'component' for reading: No such file or directory
--- Running analyze_BodhiUpdates ---
Looking for similar problems in bugzilla
The text was updated successfully, but these errors were encountered: