Mageia forum

Just installed Mageia 6 on my dekstop. Generally good, but I can't get a couple of things to work. This may require a separate topic and I'm okay with that. Just let me know.

I've been through the release notes and didn't find anything about these issues. So...

I can't get Akonadi to run and after a reboot suddenly Chrome-browser stopped opening. So, the first issue is Akonadi. I get a generic "Akonadi is not operational" message. I've installed almost everything related to 64-bit Akonadi and rebooted, but I can't get the service to start. Clicking on the "Details..." button on the applications does nothing. Any help on that appreciated.

The second issue is Chromium-browser taking a hike on me.

I tried uninstalling and deleted the ~/.kde4/google-chrome directory but that didn't work. I'm getting these errors:

Code: Select all

$ chromium-browser
[9404:9404:0828/005609.204093:ERROR:browser_main_loop.cc(257)] GTK theme error: Unable to locate theme engine in module_path: "adwaita",
[9404:9432:0828/005609.282873:ERROR:nss_util.cc(808)] After loading Root Certs, loaded==false: NSS error code: -8018
[9404:9404:0828/005609.282926:ERROR:process_singleton_posix.cc(975)] Failed to create socket directory.
[9404:9404:0828/005609.282999:ERROR:chrome_browser_main.cc(1539)] 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.

Google hasn't been very helpful in all this. Yes, I appreciate the irony.

Again, any help appreciated.

Command-output placed between [CODE][/CODE]-markings for better readability.

Of course, you are correct. It's late and I've been grinding on this for about 10 hours what with one thing an another.

Thank you for the eidt. I do appreciate it.

Looks to me like a permissions issue. Did your UID perhaps get changed from something in the 500s to something above 1000? Or, perhaps, your UID is not changed, but the UID for the owner of your home directory is changed?

If your UID and your home directory UID don't match, then perhaps Chromium cannot write in your home directory...which IS what it is complaining about.

Also check group memberships and see if something there is inconsistent.

I am a member of my own group, madams, and only that group. I made a point to set my uid and gid to "10001" on initial config. It seems to be okay.

Code: Select all

$ ll /home|grep madams
drwxr-xr-x 206 madams madams 20480 Aug 28 02:58 madams

It's correct throughout:

Code: Select all

$ ll |grep google-chrome
drwx------ 16 madams madams  4096 Aug 28 03:04 google-chrome/


I should mention that I installed the chromium-browser from google's repos and it loads, but extensions crash out of the gate. Would much rather have the chromium-browser that I had prior to the upgrade.

Still stumped.

As a general hint and golden rule: Please only one problem per thread
So either open another one for the akonadi issue or the chrome one.

Although for both you're missing a few details. For akonad, how do you exactly try to start the service? And what does "akonadictl status" return.
For chrome, either you use chromium from the Mageia repos, or chrome from the google repos. There's no chromium-browser from google repos.

For chrome, either you use chromium from the Mageia repos, or chrome from the google repos. There's no chromium-browser from google repos.

Right, but Google was kind enough to provide google-chrome-stable_current_x86_64.rpm at http://dl.google.com/linux/chrome/rpm/stable/x86_64 and when that's in your media repos, it's supposed to upgrade like any other package. Supposed to. Reality? I don't know. I've never had to resort to this before.

So, when I started this message yesterday, chromium-browser was not opening. clicking the launcher did nothing. I uninstalled it and deleted the configuration directory, rebooted, probably another thing or two as I recall. It did no good.

This evening I tried installing chromium-browser alongside gooogle-chrome-stable. I don't know why or how, but now chromium-browser is working just fine. I have no idea why. Marking this one resolved.

mark9117 wrote:Right, but Google was kind enough to provide google-chrome-stable_current_x86_64.rpm at http://dl.google.com/linux/chrome/rpm/stable/x86_64 and when that's in your media repos, it's supposed to upgrade like any other package. Supposed to. Reality?

As I said, it's chrome, not chromium.

And if you want to receive updates make sure that is enabled as update repository, otherwise you have to resort to urpmi --auto-update.

I'm sticking with chromium browser. It picks up my configuration and runs extensions without crashing. I like that in a browser.