[SOLVED] My Chromium (not google chrome) browser closes after launching but not when 'root'
SlackwareThis Forum is for the discussion of Slackware Linux.
Notices
Welcome to LinuxQuestions.org, a friendly and active Linux Community.
You are currently viewing LQ as a guest. By joining our community you will have the ability to post topics, receive our newsletter, use the advanced search, subscribe to threads and access many other special features. Registration is quick, simple and absolutely free. Join our community today!
Note that registered members see fewer ads, and ContentLink is completely disabled once you log in.
If you have any problems with the registration process or your account login, please contact us. If you need to reset your password, click here.
Having a problem logging in? Please visit this page to clear all LQ-related cookies.
Get a virtual cloud desktop with the Linux distro that you want in less than five minutes with Shells! With over 10 pre-installed distros to choose from, the worry-free installation life is here! Whether you are a digital nomad or just looking for flexibility, Shells can put your Linux machine on the device that you want to use.
Exclusive for LQ members, get up to 45% off per month. Click here for more info.
My Chromium (not google chrome) browser closes after launching but not when 'root'
Hello:
Out of the blue, my Chromium browser closes immediately after it starts!
I used pkgtool to remove it, cd to /tmp and then did:
Code:
bash-4.1# ./chromium-8.0.558.0-i486-1_SBo.tgz
This did not fix the problem.
Important, I think: If I restart my computer and login as user 'root', Chromium works perfectly.
Firefox still works properly.
This may be related, I don't know: For some reason, all the 'groups' for user 'rob' were 'unchecked' - I did not, knowingly, do this! I have never used the 'Kuser' application until yesterday when my sound stopped working and a poster here asked if user 'rob' was included in the 'audio' group - 'rob' wasn't. That's when I noticed that user 'rob' was not included in any group. I added: audio cdrom floppy plugdev video power netdev groups to user 'rob'.
Do you think that I should login as 'root' and then remove user 'rob' using 'userdel rob' (not 'userdel -r rob') and then recreate 'rob' using adduser? Would this help?
Any suggestions would be appreciated.
Last edited by Robert.Thompson; 02-23-2011 at 09:41 AM.
Robert, do a little experiment please. Open the terminal and, as root, type
Code:
adduser
Then you do this: the questions it is going to ask you are:
Login name: Pick any name.
User ID. Just press enter.
Initial group [ users ]. Just press enter.
Additional UNIX groups. At this moment, there will be a note telling you about some security implications.
DO NOT PRESS ENTER YET!!!
Press the UP arrow on your keyboard. That will add a list of groups:
Quote:
audio cdrom floppy plugdev video power netdev
Now you press enter.
After that, it's safe to just go pressing enter. Give a password to that user.
In the end, end your current session and login as the new user. I bet more than half your problems will have magically disappeared.
Distribution: slackware64 13.37 and -current, Dragonfly BSD
Posts: 1,810
Rep:
Quote:
I did the 'usermod' part and then logged in as 'rob' but the chromium browser opens and then, immediately closes.
Hmm - well it seems to be something in rob's home directory messing up Chrome. Possbily something in /home/rob/.cache/google-chrome/ so you could try "rm -R /home/rob/.cache/google-chrome/*" and if still no joy perhaps
"rm -R /home/rob/.config/google-chrome/*" - be careful of the last one - it may delete saved bookmarks and other stuff - I'm not sure exactly what Chrome stores there.
Hmm - well it seems to be something in rob's home directory messing up Chrome. Possbily something in /home/rob/.cache/google-chrome/ so you could try "rm -R /home/rob/.cache/google-chrome/*" and if still no joy perhaps
"rm -R /home/rob/.config/google-chrome/*" - be careful of the last one - it may delete saved bookmarks and other stuff - I'm not sure exactly what Chrome stores there.
Hi bgeddy.
The path for chromium (not google chrome) is a little different so I did:
Code:
# rm -R /home/rob/.cache/chromium/Cache/*
but the problem remains.
The directory /home/rob/.config/chromium contains 3 sub directories as well as 7 files.
Before I do:
Code:
rm -R /home/rob/.config/chromium/*
I was wondering why my initial use of pkgtool to remove chromium didn't entirely remove chromium?
Is there a more thorough method of removing a SlackBuild from my system?
I am assuming that doing 'rm -R /home/rob/.config/chromium/*' will make chromium not work at all but I could easily be wrong. If it does, what would I do next?
I was wondering why my initial use of pkgtool to remove chromium didn't entirely remove chromium?
Is there a more thorough method of removing a SlackBuild from my system?
I am assuming that doing 'rm -R /home/rob/.config/chromium/*' will make chromium not work at all but I could easily be wrong. If it does, what would I do next?
Thanks for you patience,
Removing Chromium with pkgtool removes every file that was installed from the package. When running Chromium it creates user-based configurations and cache data in your home directory (thus only affecting one user). Most programs work this way; the application itself has been removed, but user-specific data remains since it was created post-install by the program itself. Issuing that command will remove all Chromium user configuration from your home directory. It is still installed on the system, and it should work fine -- but browser history, bookmarks, and any browser configuration you did will be removed (so you'll be starting fresh, and new data will be created with default settings).
Distribution: slackware64 13.37 and -current, Dragonfly BSD
Posts: 1,810
Rep:
As T3slider has already said - removing a package will remove the files in the package but not anything the application creates. That's a bit like expecting removepkg vim to remove all the documents you have ever created with vim. The ~/ files the application creates are settings for the user created at run time. As a new user works and your rob user doesn't I suspect on of these user files may be at fault.
Quote:
I am assuming that doing 'rm -R /home/rob/.config/chromium/*' will make chromium not work at all but I could easily be wrong. If it does, what would I do next?
No - when you created the new user robert he did not automatically have a /home/robert/.config/chrome directory - Chrome created that when it first ran. I'm just trying to work through what could be making the Chrome application fail for ron but not robert (or any other user). That leads me to think it must be something in the application's settings it stores in the user's /home directory. Don't be scared to toy with these things - it's easy to remove and install packages - it's the settings a user has stored that are important - (like bookmarks in a browser).
On that note I can recommend a browser add-on called Xmarks that lets you store bookmarks, passwords and stuff on line so you can transfer them between machines and users. I use it a lot and trust it, (although obviously not with anything really secure - like my bank account login)!
Last edited by bgeddy; 02-23-2011 at 03:49 PM.
Reason: Better sense
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.