I recently installed a 19.10 UbuntuBudgie. I was using 18.04 ago.
Since this new installation I’ve noticed Firefox is kind of slow to « start » :
⋅ I can launch Firefox but it’s unresponsive for a moment ( no blinking cursor anywhere )
⋅ then cursor eventually appears in address bar but blinking slowly and not usable,
⋅ still, clicking anywhere has no effect, or effect delayed much later,
⋅ a moment later, cursor blinks at its usual pace and Firefox becomes responsive as expected.
The whole process takes 30 seconds to 1 minute and Firefox runs rather ok later on with some slow moments though.
Same behavior in safe-mode ( without any FF addons ).
I use Budgie applets : pixel-saver and global menu. Guess it’s related ?
→ maybe not related, even without these budgie applets, FF still shows the exact same error. [ edit 2020-04-04 ] → my big mistake here → one has to logout / login back to session after each modification on applets / panels !!!
I have not seen this at all. FF opens up almost immediately for me. (See the GIF). I had been trying to replicate - but I can’t seem to mimic your behavior.
Problem here is, as long as Firefox has not finished its starting, all interactions with Budgie desktop are also slowed down ( if I click anything in panels, it will react only after FF is completely ready ).
CurrentDesktop: Budgie:GNOME
Date: Fri Apr 3 02:04:06 2020
DefaultProfileExtensions: extensions.sqlite corrupt or missing
DefaultProfileIncompatibleExtensions: Unavailable (corrupt or non-existant compatibility.ini or extensions.sqlite)
DefaultProfileLocales: extensions.sqlite corrupt or missing
DefaultProfilePrefErrors: Unexpected character ',' before close parenthesis @ /usr/lib/firefox/omni.ja:greprefs.js:732
DefaultProfileThemes: extensions.sqlite corrupt or missing
Any thought about these corrupt or missing mentions ?
Please launch Firefox from terminal and see if any error message.
Launch is fast - but with a frozen unresponsive whole interface for a long moment.
It seems there is a problem in my installation but sudo apt install --reinstall firefox did not help.
Since Firefox downloaded from Mozilla’s page works without error, I have some hope to find out what went wrong ( file omni.ja ? )
If of any interest, here are my installed dbus packages :
django@ASGARD:~$ dpkg -l | grep dbus
ii at-spi2-core 2.34.0-2 amd64 Assistive Technology Service Provider Interface (dbus core)
ii dbus 1.12.14-1ubuntu2 amd64 simple interprocess messaging system (daemon and utilities)
ii dbus-user-session 1.12.14-1ubuntu2 amd64 simple interprocess messaging system (systemd --user integration)
ii dbus-x11 1.12.14-1ubuntu2 amd64 simple interprocess messaging system (X11 deps)
ii libdbus-1-3:amd64 1.12.14-1ubuntu2 amd64 simple interprocess messaging system (library)
ii libdbus-glib-1-2:amd64 0.110-4 amd64 deprecated library for D-Bus IPC
ii libdbusmenu-glib4:amd64 16.04.1+18.10.20180917-0ubuntu2 amd64 library for passing menus over DBus
ii libdbusmenu-gtk3-4:amd64 16.04.1+18.10.20180917-0ubuntu2 amd64 library for passing menus over DBus - GTK+ version
ii libdbusmenu-gtk4:amd64 16.04.1+18.10.20180917-0ubuntu2 amd64 library for passing menus over DBus - GTK+ version
ii libnet-dbus-perl 1.1.0-6 amd64 Perl extension for the DBus bindings
ii libqt5dbus5:amd64 5.12.4+dfsg-4ubuntu1.1 amd64 Qt 5 D-Bus module
ii libqtdbus4:amd64 4:4.8.7+dfsg-7ubuntu3 amd64 Qt 4 D-Bus module library
ii python3-dbus 1.2.12-1 amd64 simple interprocess messaging system (Python 3 interface)
ii python3-dbus.mainloop.pyqt5 5.12.3+dfsg-2 amd64 D-Bus Qt main loop support for Python 3
ii xdg-dbus-proxy 0.1.1-1 amd64 filtering D-Bus proxy
django@ASGARD:~$
Is it normal to find libdbusmenu-gtk4:amd64 already installed by default ?
Going on on my experimentations with « pure » FF from Mozilla, I’ve noticed :
⋅ it does not throw any errors regarding libdbusmenu ( even with my older profile⋅s )
⋅ but it does not export app-menu to Budgie global menu applet…
And going further, is it normal there is no .dbus folder in any of users’ personal folder of Ubuntu Budgie 19.10 ???
Edit,later : on 20.04 tested on live usb, there is a .dbus folder…
Not the same problem, I have never had errors regarding profiles.
I even have tested with different profiles, empty profiles, new profiles.
I always have the (firefox:17653): LIBDBUSMENU-GTK-CRITICAL **: 21:52:24.565: dbusmenu_menuitem_property_set_shortcut: assertion 'gtk_accelerator_valid(key, modifier)' failed error message in terminal. This added to the fact I don’t have .dbus folder in my personal folder sounds not good and related…