[SOLVED] Chromium won't start

Jabrick · 2012-01-18 04:04:50

I'm not sure why but chromium does no longer want to start for me.
When I type it in the terminal I get this error message

[1856:1856:142255483:ERROR:process_singleton_linux.cc(940)] Failed to create socket directory.
[1856:1856:142255592:ERROR:chrome_browser_main.cc(1507)] Failed to create a ProcessSingleton for your profile directory. This means that running multiple instances would start multiple browser processes rather than opening a new window in the existing process. Aborting now to avoid profile corruption.

According to sources online the problem is caused becaused the /tmp directory is fulll.
When I run df -h my results are

Filesystem                                              Size  Used Avail Use% Mounted on
udev                                                     10M     0   10M   0% /dev
run                                                      10M  260K  9.8M   3% /run
/dev/disk/by-uuid/cdee53e2-d656-4ea7-8a89-aa151cb5180b  7.3G  7.0G     0 100% /
shm                                                     3.9G     0  3.9G   0% /dev/shm
/dev/sdb1                                               123G  188M  116G   1% /media
/dev/sda1                                                99M   17M   78M  18% /boot
/dev/sda4                                               451G  134G  295G  32% /home

Now I dont know if it has to do with the
/dev/disk/by-uuid/cdee53e2-d656-4ea7-8a89-aa151cb5180b
And when I go to my root directory and type in ls the /tmp directory is highlighted in green.
In my tmp there is nothing there except an empty cron folder.

Before hand I was trying to get CUPS working.
And had disabled usblp.
But I took I no longer blacklisted it, and removed CUPS from my DAEMON.
When I rebooted I noticed usblp did not load on startup.
So i modprobe usblp, but I still get same problem.
Could that be my problem?
How to I get it to load usblp from start up?

Last edited by Jabrick (2012-01-18 04:22:07)

fsckd · 2012-01-18 04:08:01

You have bigger problems than chromium not starting. Your / is full. Clear up space or you'll see other things fail too.

Jabrick · 2012-01-18 04:11:05

Sorry but what should I be cleaning up to fix the issue.
Isn't the root directory very important?
I do not save any files (pictures videos etc.) in my root directory...

karol · 2012-01-18 04:12:33

Find out what is taking up the space. No, you can't just delete everything :-)
Maybe you have just too many packages installed and you should be using a bigger / partition.

Last edited by karol (2012-01-18 04:13:37)

fsckd · 2012-01-18 04:13:35

Yes it is important which is why having it filled to 100% is not very good. I'd start by cleaning the pacman cache (pacman has an option to do this for you) and checking for oversized log files (in /var/log).

Jabrick · 2012-01-18 04:21:43

Ok yes thanks for the help.
Never experienced a full root folder before.
My pacman cache was up to 2.7G.
Thanks

karol · 2012-01-18 04:25:14

You still might want to resize your / . You have a big /home and e.g. 20 GB / might better suit your needs.

Arch Linux

#1 2012-01-18 04:04:50

[SOLVED] Chromium won't start

#2 2012-01-18 04:08:01

Re: [SOLVED] Chromium won't start

#3 2012-01-18 04:11:05

Re: [SOLVED] Chromium won't start

#4 2012-01-18 04:12:33

Re: [SOLVED] Chromium won't start

#5 2012-01-18 04:13:35

Re: [SOLVED] Chromium won't start

#6 2012-01-18 04:21:43

Re: [SOLVED] Chromium won't start

#7 2012-01-18 04:25:14

Re: [SOLVED] Chromium won't start

Board footer