-
Notifications
You must be signed in to change notification settings - Fork 204
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
Crash at statup, on a pinephone pro linux phone (maybe keyring) #1849
Comments
Hello Henry, Based on your comment and output it seems you have not even started the GUI but just the CLI. Do you have a desktop environment on your Pinephone? Just look for "Back In Time" and click on it. On terminal there is Does this help? |
Thanks for the quick reply, Christian. Nice catch. I did run diagnostics using the command line program. I just reran it using the gui command but other than one additional sys.path line the outputs are the same. Anyway, the new output is below. As far as the debug text output is concerned, I ran that using the qt program, but I labeled it incorrectly. So that output is still valid. When I look at the debug output it seems that the segmentation occurs when trying to detect the theme. Looking at the diagnostics the fallback theme has an empty value. The pinephone is running gnome 46 with a custom shell (phosh). As you can see , PyQt generates a warning regarding the locale setting. I realize that these conditions may or may not point to any relevant problem. I am going to try to reset the locale based on the PyQt warning to see if that will help. If I can provide any further information, please let me know.
|
The warning about the language is not a problem. But I wonder why your local is set to "C" instead of "en_US" or something else. This might indicate that you are running BIT in an unusual environment. What is the output of |
locale update: Setting the locale to en_US.UTF-8 removed the Py-QT warning, but the segmentation fault still happens exactly as before.
|
I've done some more investigation. My laptop uses the same OS ver as this phone. backintime-qt [ver1.5.2] starts and works fine on this laptop. Here is a comparison of the --dbug from the phone and then the laptop. pinephonepro first --> laptop second:
I'm wondering if this could be a gnome-keyring problem? I've also tested backintime-qt [ver 1.2] on an older phone [debian 11] 2021 . It works fine, no problems at all. Any ideas? |
Hello Henry, |
I have medium level python skills. If you can give me a place to start I'd be willing to give it a try. I've since discovered that if I provide a basic config file (copied from my laptop) and generate a ssh key pair the --debug goes quite a bit further. Eventually it segfaults after:
|
I would recommend to wait for Jürgen's (aryoda) feedback. He is more involved in keyring issues and I think your issues is related to it. |
I'm using debian trixie on a pinephone pro
arm64
The UI will not start.
Running backintime --diagnostics
Running backintime --debug
The text was updated successfully, but these errors were encountered: