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 <[email protected]> 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 > to unlink /home/byers/.config/google-chrome/SingletonLock: Read-only > file system > [4311:4311:95679337571:ERROR:process_singleton_linux.cc(265)] Failed > to create /home/byers/.config/google-chrome/SingletonLock: File exists > [4311:4311:95679337706:ERROR:process_singleton_linux.cc(250)] Failed > to unlink /home/byers/.config/google-chrome/SingletonLock: Read-only > file system > [4311:4311:95679337746:ERROR:browser_main.cc(1650)] 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. > > [2]+ Exit 20 /opt/google/chrome/google-chrome > > > I then rebooted, and chrome came up as usual. > > advice? > > Jack > -- > users mailing list > [email protected] > To unsubscribe or change subscription options: > https://admin.fedoraproject.org/mailman/listinfo/users > Guidelines: http://fedoraproject.org/wiki/Mailing_list_guidelines >
-- users mailing list [email protected] To unsubscribe or change subscription options: https://admin.fedoraproject.org/mailman/listinfo/users Guidelines: http://fedoraproject.org/wiki/Mailing_list_guidelines
