On 10/27/2011 03:30 PM, jackson byers wrote:
> $ uname -r
> 2.6.35.14-97.fc14.i686.PAE
>
>
> chrome suddenly quit; no response to clicks on icon
>
> trying manually:
>
> $ /opt/google/chrome/google-chrome &
> [2] 4311
> $ [4311:4311:95679337296:ERROR:process_singleton_linux.cc(250)] Failed
> //
Possibly for the read only FS, I think -
Read-only file system is mentioned in the error messages. When you
rebooted, a FSCK was done on the system and things got well.
-Soham
On Fri, Oct 28, 2011 at 2:00 AM, jackson byers wrote:
> $ uname -r
> 2.6.35.14-97.fc14.i686.PAE
>
>
> chrome suddenly
$ uname -r
2.6.35.14-97.fc14.i686.PAE
chrome suddenly quit; no response to clicks on icon
trying manually:
$ /opt/google/chrome/google-chrome &
[2] 4311
$ [4311:4311:95679337296:ERROR:process_singleton_linux.cc(250)] Failed
to unlink /home/byers/.config/google-chrome/SingletonLock: Read-only
fi