Chrome latest not starting on a fresh F17 XFCE install

[96th]

Hi. I've invested in using Fedora 17 XFCE as the system of choice for my parents, on my old laptop (that last ran Fedora at around 11/13, with Chrome running on it just fine) since my mum set fire to the other one (okay, that's a bit overdramatic, but there was smoke involved!). I've set it up just how I wanted it, but there's one small problem.

Chrome will not start. The ABRT says it gets killed by signal 6, SIGABRT. When dragging a shortcut from the desktop into a user terminal, I get a "no access" error. When dragging the actual executable to the command line it just says "stopped". Literally, just that one word. However, yesterday it also said "core dumped".

Interestingly, it only happens on 'mirek' and 'dorota' accounts. It works fine on 'tom' and 'root'. I've managed to make it run on the 'dorota' account by starting Chrome as root with user-data-dir=/home/dorota. However, this is obviously not a viable solution.

Any thoughts?

[ozjd]

Is Chrome configured the same for all users? If not you could try removing the google-chrome directory in ~/.config.

[Ihatewindows]

Try downloading the Gnome LiveCD and try installing Chrome on there. If it works there, try installing Gnome on a test VM in VirtualBox or VMware to test it out. Just a thought.

[96th]

Thanks for your replies.

ozjd: It won't start in the first place, so there's nothing there.
Ihatewindows: It worked on my computer which was set up with exactly the same OS, before my mum set it on fire.

// Edit: Actually, I lied. The old computer was 32bit as opposed to the current 64bit.

// Edit 2: The plot thickens! What should be happening, and is happening with the 'tom' account is that when I type 'su' or 'sudo', I'd get asked for a password and when I'd enter it I'd be in a root shell. However, when I type 'sudo' on the 'dorota', and presumably the 'mirek' accounts just sudo themselves in without password! However, 'su' is still passworded on all accounts. The sudoers file definitely says that every user in the group wheel has equal permissions, and they should require a password. Additionally, 'tom' cannot edit visudo. I don't even know what is happening anymore.

// Edit 3: There's nothing in /etc/sudoers.d

[ozjd]

The su / sudo issue is another problem and shouldn't affect Chrome.
Try running chrome from a terminal and look for errors.

[96th]

ozjd: As I said, it just returns one word: 'stopped'. When I drag the shortcut to the terminal it says 'access denied' (or something. it's translated, but you get the gist). Therefore, I'm sure that these are some sorts of permissions issues and therefore are related. There's no other explanation.

[ozjd]

Rather than dragging the shortcut did you try just typing google-chrome? It should be a user login too not as root.

[96th]

Just says 'stopped'. I'll reinstall it, I think.