Closed Bug 963979 Opened 11 years ago Closed 10 years ago

GLib-CRITICAL while doing "Getting Started With cfx" tutorial on "cfx run" command

Categories

(Add-on SDK Graveyard :: General, defect, P2)

x86_64
Linux
defect

Tracking

(Not tracked)

RESOLVED WONTFIX

People

(Reporter: zawiczek, Unassigned)

References

Details

Attachments

(1 file)

User Agent: Mozilla/5.0 (X11; Ubuntu; Linux x86_64; rv:26.0) Gecko/20100101 Firefox/26.0 (Beta/Release) Build ID: 20131206145143 Steps to reproduce: On Linux mint 16 (Cinnamon x86_64) using Firefox 26.0 and addon-sdk-1.15. I've been fallowing: https://developer.mozilla.org/en-US/Add-ons/SDK/Tutorials/Getting_Started_With_cfx while running command "cfx run" I've got lots of errors and warnings in command prop. Actual results: No expected icon in right bottom corner, and command prop full of: Using binary at '/usr/bin/firefox'. (process:7991): GLib-CRITICAL **: g_slice_set_config: assertion 'sys_page_size == 0' failed Using profile at '/tmp/tmp8kkuhO.mozrunner'. (process:7995): GLib-CRITICAL **: g_slice_set_config: assertion 'sys_page_size == 0' failed WARNING: Attempt to add property GnomeProgram::sm-connect after class was initialised: 'glib warning', file /build/buildd/firefox-26.0+build2/toolkit/xre/nsSigHandlers.cpp, line 127 (firefox:7995): GLib-GObject-WARNING **: Attempt to add property GnomeProgram::sm-connect after class was initialised WARNING: Attempt to add property GnomeProgram::show-crash-dialog after class was initialised: 'glib warning', file /build/buildd/firefox-26.0+build2/toolkit/xre/nsSigHandlers.cpp, line 127 (firefox:7995): GLib-GObject-WARNING **: Attempt to add property GnomeProgram::show-crash-dialog after class was initialised WARNING: Attempt to add property GnomeProgram::display after class was initialised: 'glib warning', file /build/buildd/firefox-26.0+build2/toolkit/xre/nsSigHandlers.cpp, line 127 (firefox:7995): GLib-GObject-WARNING **: Attempt to add property GnomeProgram::display after class was initialised WARNING: Attempt to add property GnomeProgram::default-icon after class was initialised: 'glib warning', file /build/buildd/firefox-26.0+build2/toolkit/xre/nsSigHandlers.cpp, line 127 (firefox:7995): GLib-GObject-WARNING **: Attempt to add property GnomeProgram::default-icon after class was initialised reference to undefined property options.bytesreference to undefined property exn.stackJavaScript strict warning: chrome://browser/content/urlbarBindings.xml, line 672: reference to undefined property this._value JavaScript error: chrome://browser/content/urlbarBindings.xml, line 654: aUrl is undefined Expected results: Expected behaviour is described in "Getting Started With cfx". "M" icon does not show up.
OS: All → Linux
Hardware: All → x86_64
This looks like it could be from a GLib issue in bug 833117. What GLib version are you running?
Flags: needinfo?(zawiczek)
(In reply to Jordan Santell [:jsantell] [@jsantell] from comment #1) > This looks like it could be from a GLib issue in bug 833117. What GLib > version are you running? dpkg -s libglib2.0-0 | grep Version -> Version: 2.38.1-0ubuntu1
Flags: needinfo?(zawiczek)
Check out the comments in bug 833117 -- some work arounds are possible, I think. Are you able to run Firefox normally, outside of using CFX and addon development?
There is no problem with Firefox, but it's a pity that because of this bug CFX flow of building addons is disrupted.
See Also: → 967701
This bug affects me. I filed a separate report here: https://bugzilla.mozilla.org/show_bug.cgi?id=1057336 How do I change the bug status to 'confirmed'?
Dear Loic You marked my other account of this bug as "resolved" on account of the workarounds given in bug 833117. (see: https://bugzilla.mozilla.org/show_bug.cgi#add_comment). Bug 963979 does indeed *seem* related - but it does not provide a solution: it merely suggests a workaround for bug 833117. I tried that suggested workaround ($export G_SLICE=always-malloc) for this tutorial bug. It did not solve my problem. Either way, a workaround is not a fix.
Two questions: * How do I change the status to 'confirmed'? * Where is the best place to report a bug in a tutorial? i.e. This is a bug in the tutorial since the tutorial example doesn't work. But by dismissing it as another bug that *seems* may be the *cause* of the tutorial bug, misses the point. The fact remains that the tutorial example doesn't work. That is the bug.
Sorry we won't be releasing any new versions of cfx, jpm is the replacement https://www.npmjs.com/package/jpm
Status: UNCONFIRMED → RESOLVED
Closed: 10 years ago
Resolution: --- → WONTFIX
You need to log in before you can comment on or make changes to this bug.

Attachment

General

Creator:
Created:
Updated:
Size: