Two browser plugins tried to register

Please post any bugs you have found
Post Reply
Message
Author
User avatar
Argolance
Posts: 3767
Joined: Sun 06 Jan 2008, 22:57
Location: PORT-BRILLET (Mayenne - France)
Contact:

Two browser plugins tried to register

#1 Post by Argolance »

Hello,
I don't know exactly where to ask my question but as far as I know this doesn't only concern Puppy Precise 5.7.1 I am currently running but other more and less recent Puppies I tested too.
When I run both Pale Moon or Midori web browsers, I get these warning messages (and other similar) in console:

Code: Select all

(midori4:20051): GLib-GObject-WARNING **: Two different plugins tried to register 'GConfSettingsBackend'.

(midori4:20051): GLib-GIO-WARNING **: Tried to register an extension of the type (null) to extension point gsettings-backend. Expected type is GObject.
GLib-GIO-Message: Using the 'memory' GSettings backend.  Your settings will not be saved or shared with other applications.

Code: Select all

# palemoon

(palemoon:20794): GLib-GObject-WARNING **: Two different plugins tried to register 'GConfSettingsBackend'.

(palemoon:20794): GLib-GIO-WARNING **: Tried to register an extension of the type (null) to extension point gsettings-backend. Expected type is GObject.
GLib-GIO-Message: Using the 'memory' GSettings backend.  Your settings will not be saved or shared with other applications.
Not sure but I think it has to do with wrong modules configuration inside /usr/lib/gio/modules...
What's wrong?
I there a way to get rid of/solve this?

Cordialement.

Pelo

I don't know Argolance,

#2 Post by Pelo »

I don't know Argolance, I would have been happy to help you.
What i can do, is to make your question at the top again.

watchdog
Posts: 2021
Joined: Fri 28 Sep 2012, 18:04
Location: Italy

#3 Post by watchdog »

Using palemoon I think you should open as text pluginreg.dat in your browser's profile to see what plugins fail to register.

musher0
Posts: 14629
Joined: Mon 05 Jan 2009, 00:54
Location: Gatineau (Qc), Canada

#4 Post by musher0 »

Allô, Argolance.

Do you mean that those messages appear in /tmp/xerrs.log?

I had similar messages in Slim-6 (a trimmed-down Slacko 6).

Certainly your first error is linked to gconf. This error you can probably
remedy by checking if you have all the components of gconf. That's what
I had to do in Slim-6: re-install some gconf components. "ninaholic",
author of Slim-6, had trimmed too much of the original Slacko 6.

However both your errors seem to be linked to the "glibc". It may be that
there is a slight difference in the sub-version between the glibc versions
in your ToOpPy and in the browsers. If they run anyway, I wouldn't worry
too much about it. From experience, I can tell you that trying to pair up
exactly two slightly different glibc's is an unnecessary nightmare.

J'espère que ça t'aide un peu. Au revoir.
musher0
~~~~~~~~~~
"You want it darker? We kill the flame." (L. Cohen)

Post Reply