blivet-gui icon indicating copy to clipboard operation
blivet-gui copied to clipboard

Not launching/opening

Open mrme02 opened this issue 2 years ago • 5 comments

Running Debian Bullseye. X11 with Cinnamon desktop.

Upon launching, I get asked for my root password, nothing happens after that. Noob user, so unaware of what, if any logs are required to diagnose.

If any further detail is required, please let me know, so I can get this issue resolved.

mrme02 avatar Nov 04 '22 12:11 mrme02

Hi, try running blivet-gui from the terminal with the blivet-gui command, it should produce some error message. Logs are stored in /var/log/blivet-gui but if something happened immediately after the start, it's probably not logged.

vojtechtrefny avatar Nov 04 '22 14:11 vojtechtrefny

From console (su -)

I get the following (I tried this before, but gave up as they looked like the same error messages I get when running applications as root from the console)

Unable to init server: Could not connect: Connection refused

And, (blivet-gui:144649): Gtk-CRITICAL **: 14:39:32.030: _gtk_style_provider_private_get_settings: assertion 'GTK_IS_STYLE_PROVIDER_PRIVATE (provider)' failed Segmentation fault

mrme02 avatar Nov 05 '22 14:11 mrme02

I just tried running this as my normal user after reinstalling blivet-gui, to see if I had missed anything. It asked for my password, then this is what was printed to the console,

Traceback (most recent call last): File "/usr/bin/blivet-gui", line 117, in main() File "/usr/bin/blivet-gui", line 110, in main client = BlivetGUIClient(server_socket=sockfile) File "/usr/lib/python3/dist-packages/blivetgui/communication/client.py", line 110, in init self.sock.connect(server_socket) PermissionError: [Errno 13] Permission denied

mrme02 avatar Nov 21 '22 01:11 mrme02

Sorry for late answer. I did a new release of blivet, there was a different issue reported on Debian (https://github.com/storaged-project/blivet/issues/1087) so it is possible that it fixes your problem too. But it might be also something, I'll try to do a fresh installation of Debian 11 to see whether I can reproduce your issue (I didn't see a similar problem with testing).

vojtechtrefny avatar Dec 04 '22 14:12 vojtechtrefny

I've updated to the latest version, but the issue still remains, same errors, and nothing logged. Just tried in a Bullseye VM, and confirms it runs without issue inside a VM, so the issue is with my Debian install.

I'll reinstall Python, as that's where the issues seem to stem from.

Thank you for helping me out up to this point, I do appreciate your help :-)

mrme02 avatar Dec 04 '22 15:12 mrme02