1

I am new to Linux and have been poking around a lot in Terminal. I launched Firefox from the command line and noticed that I began getting the below. It still opens and seems to run as it should. I don't remember seeing this before deleting Chrome or before using proxychains. Any thoughts?

(firefox:8321): GLib-GObject-CRITICAL **: g_object_ref: assertion 'object->ref_count > 0' failed

(firefox:8321): GLib-GObject-CRITICAL **: g_object_unref: assertion 'object->ref_count > 0' failed

(firefox:8321): GLib-GObject-CRITICAL **: g_object_ref: assertion 'object->ref_count > 0' failed

(firefox:8321): GLib-GObject-CRITICAL **: g_object_unref: assertion 'object->ref_count > 0' failed
wjandrea
  • 14,236
  • 4
  • 48
  • 98
user635942
  • 11
  • 1
    See Why am I getting this error while using gedit? However, if you're looking for the cause, we might not want to close this question as a duplicate; the answer there doesn't address that. ...What command are you running? Just firefox, or something else? Is there any other output in the terminal when you run it? What version of Ubuntu? Do the messages appear if you don't use proxychains? (I understand you might not be able to test that, for security reasons. So if not, please don't sweat it.) I recommend editing your question to provide this additional info. – Eliah Kagan Dec 28 '16 at 23:35
  • 1
    Just run firefox &>/dev/null &. Those are useless messages spewed by a graphics library. (Despite the scary CRITICAL tag, they are actually utterly unimportant.) There is nothing else you can do about them. – AlexP Dec 29 '16 at 01:34
  • @AlexP, I have noticed that too when I launch app from terminal. Why is that the case, if the app works fine why the error messages ? – George Udosen Dec 29 '16 at 01:37
  • 1
    @George: Those are debugging messages produced by a graphics library. Why they are displayed unconditionally in production builds is a mystery for the ages. – AlexP Dec 29 '16 at 01:50
  • 1
    Also see my answer here: http://askubuntu.com/a/422400/248158 – DK Bose Dec 29 '16 at 04:53

0 Answers0