Developer application fails to start on Ubuntu system
Developer application fails to start on Ubuntu system
Everything functioning smoothly until recently, around a week ago. The Opera Developer 47 stopped working on my Ubuntu system. When attempting to run it as an administrator, I received the warning: "Can't open user profile directory, because you lack sufficient privileges. You might want to contact the administrator of this machine." I mistakenly started two Opera instances simultaneously. After closing Opera, I tried launching another app nearby, but it relaunched Opera too quickly while it was still closing in the background. This issue remains unchanged since then. The same problem was described here: https://ubuntuforums.org/showthread.php?t=2371416. Someone resolved it by logging out and back in. Despite multiple restarts, the situation hasn't improved. Any advice would be appreciated!
You could try executing it in a terminal to avoid permission issues.
I'm not certain what "opera" refers to—perhaps it's a misunderstanding. If you're looking for ways to run an application, you might try locating the correct executable via a shortcut and launching it with sudo from the terminal.
Open the opera launcher icon and tap on its properties. It will display the command it uses to start the app. The launcher is typically located at home.local/applications or usr/local/applications. You can also try the locate command, which functions like a powerful search tool on Linux. If the service isn't working, reinstall it. Use apt purge and auto remove to clear all system-related settings for opera. Then navigate to your home directory and remove any remaining opera files—whether in the opera folder or in .local, .cache, or .Config directories.
Thanks for sharing your experience. I'm glad the instructions helped resolve your issue. You mentioned needing to remove all Chrome data from Ubuntu, which prevented installation and use. The developer folder you accessed contained important files like "Current Session", "Current Session.bak", "Last Session", and "Last Session.bak". It sounds like a careful cleanup was necessary. I'm here if you need further guidance on Chrome setup or any other help!