GTK crash running bleachbit as sudo on Fedora linux

[ghost]

Running:
sudo bleachbit
on Fedora 32, BleachBit version 4.0.0 crashes:

(non sudo bleachbit from command line works fine)...

No protocol specified
Unable to init server: Could not connect: Connection refused
No protocol specified
Unable to init server: Could not connect: Connection refused

(bleachbit:3891): Gdk-CRITICAL **: 09:12:12.381: gdk_screen_get_root_window: assertion 'GDK_IS_SCREEN (screen)' failed
No protocol specified
Unable to init server: Could not connect: Connection refused

(bleachbit:3891): Gtk-WARNING **: 09:12:12.392: cannot open display: :0

[az0]

I tried sudo bleachbit on Fedora 31 with BleachBit 3.9.0 (that's the system I had handy), and it worked fine. Have you tried searching the web for your error message? This issue is not specific to BleachBit.

Have you also tried other applications such as sudo gedit?

Let me know how it goes. If you need more help, please let me know whether your windowing system is X or Wayland.

[ghost]

Thanks :)

sudo works fine with other applications on my system. I use: Fedora 32 - KDE spin. KDE plasma 5.18.5. 64bit. X windows.

I used to use 3.9.0 on linux mint (ubuntu) - that worked fine as sudo. I changed to F32.

Now using bleachbit 4.0.0.: non-sudo bleachbit works in the command line. sudo errors.

Googling - a few people experienced this error also, using bleachbit in the command line. I couldn't see a resolution.

[ediowar]

Seems to be a dup of #919 , #922

[abitrolly]

Can not reproduce on Fedora 33 with GNOME and X11 or Wayland. @sjclondonukgreat can you test if the issue still repeats on your system, and paste the output of bleachbit --sysinfo?

[ghost]

I have F33 now and KDE with X11. It seems to work now, so the issue must have resolved itself. I use 4.0.0.

BleachBit version 4.0.0
Git revision f2093f8
GTK version 3.24.23
GTK theme = Breeze
GTK icon theme = Tela
GTK prefer dark theme = False
SQLite version 3.33.0
local_cleaners_dir = None
locale_dir = /usr/share/locale/
options_dir = /home/alex/.config/bleachbit
personal_cleaners_dir = /home/alex/.config/bleachbit/cleaners
system_cleaners_dir = /usr/share/bleachbit/cleaners
locale.getdefaultlocale = ('en_GB', 'UTF-8')
os.getenv('DESKTOP_SESSION') = /usr/share/xsessions/plasma
os.getenv('LOGNAME') = alex
os.getenv('USER') = alex
os.getenv('SUDO_UID') = None
os.path.expanduser('~') = /home/alex
platform.linux_distribution() = ('Fedora', '33', 'Thirty Three')
platform.platform = Linux-5.8.17-300.fc33.x86_64-x86_64-with-glibc2.32
platform.version = #1 SMP Thu Oct 29 15:55:40 UTC 2020
sys.argv = ['/usr/bin/bleachbit', '--sysinfo']
sys.executable = /usr/bin/python3
sys.version = 3.9.0 (default, Oct 6 2020, 00:00:00)
[GCC 10.2.1 20200826 (Red Hat 10.2.1-3)]
file = /usr/share/bleachbit/Diagnostic.py

[abitrolly]

@sjclondonukgreat thanks for the update. That could have been an issue with GTK not specific to BleachBit that got fixed. Just a guess - I am not monitoring GTK development closely to find some prooflinks.