Is totally normal and doesn't reflect on your current running invoking user. Therefore, the error you see i.e.: Trying to run as user instance, but $XDG_RUNTIME_DIR is not set. Is invoked as the user root( not your current user invoking sudo) without actual root login and therefore, invoked as such, doesn't have an existing user-runtime environment including a runtime-directory. Whether my prior habit of launching Firefox multiple times with profiles that were already running did so in a new window in the same running instance or a new window and new instance makes no difference to me: it worked before now it does not. To close the other instance would defeat the object of my attempt to launch Firefox with a profile that is already open.(Thanks to for the suggestion). Indeed, I usually have multiple windows open with the same profile on multiple workspaces. I cannot simply close the other running window/instance of Firefox, since that would destroy my workflow. What can I do to get Firefox working properly from its default Snap install on Ubuntu 22.04 LTS, and launch new windows/instances with profiles that are already running? When I run SNAPD_DEBUG=1 snap run firefox -profile-manager, Snap also reports that it is using a uid of 1000 but does appear to be have an error: ATTENTION: default value of option mesa_glthread overridden by environment. Reports on this problem suggest systemd might be responsible.īut syslog seems to report no problems when Firefox is called. Trying to run as user instance, but $XDG_RUNTIME_DIR is not set. echo $DBUS_SESSION_BUS_ADDRESSīut systemd thinks it is not._. My $DBUS_SESSION_BUS_ADDRESS does appear to be set._. Numerous other reports on the matter suggest that the problem can sometimes be that the environment variable $DBUS_SESSION_BUS_ADDRESS is not set, and that the fix can involve simply setting this envar to unix:path=/run/user/$DBUS_SESSION_BUS_ADDRESS/bus. firefox -P default ""ĪTTENTION: default value of option mesa_glthread overridden by environment. Now when I run Firefox from the terminal I get the following error. Using Firefox on 20.04, my everyday workflow as a knowledge worker involved starting new instances of Firefox with profiles that were already running on other workspaces. This problem did not exist with Ubuntu 20.04 (where the default install was managed via apt). You must first close the existing Firefox process, restart your "Firefox is already running, but is not responding. When I try to launch Firefox with a profile that is already running, I get an error: Firefox is broken on a fresh install of Ubuntu 22.04 LTS (Xubuntu) with Firefox 113.0.2, installed by the now default method, from Snap.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |