Hi,
On 04/10/2017 11:29 AM, [email protected] wrote:
On 04/10/2017 10:40 AM, [email protected] wrote:
Hello all,
I get GLib-GObject-CRITICAL warning or error while staring RAUC service:
# rauc -d service
Domains: 'rauc'
(rauc:537): rauc-DEBUG: service start
(rauc:537): rauc-DEBUG: No mount prefix provided, using /mnt/rauc/ as
default
(rauc:537): GLib-GObject-CRITICAL **: g_object_set: assertion
'G_IS_OBJECT (object)' failed
(rauc:537): rauc-DEBUG: name 'de.pengutronix.rauc' acquired
What does it mean?
to ease understanding what could have went wrong: Which exact version of RAUC
are you using? (Because there were some changes surrounding the Code that might
have caused this issue.)
I am using Yocto and last commit information is:
commit 3867722b8d64c43765e2d04f346dd612c02ad137
Author: Jan Lübbe <[email protected]>
Date: Mon Feb 13 10:34:53 2017 +0100
README.md: update github URL
And console output is:
# rauc --version
rauc 0.572-3867-dirty
Ok, if you say Yocto, I assume you are using meta-rauc, right?
And yes... definitely have to update meta-rauc to use the latest version
of RAUC.
I assume you see an error that was fixed by
https://github.com/rauc/rauc/commit/98f8484fb3357fc8b2bba7ddc7f31f6e9a04f518
(as always, the first commit after the revision that is in ;) )
For now you can update RAUC manually by adding (if not yet existing) a
rauc_git.bbappend file to your projects meta layer and set
SRCREV = "33fe5ab4bc8c364b666b7332c2f3ec6fc095b7a2"
to use the latest version of RAUC.
Does this temporary hack solve your runtime problems for now?
Best regards
Enrico
--
Pengutronix e.K. | Enrico Jörns |
Industrial Linux Solutions | http://www.pengutronix.de/ |
Peiner Str. 6-8, 31137 Hildesheim, Germany | Phone: +49-5121-206917-5080 |
Amtsgericht Hildesheim, HRA 2686 | Fax: +49-5121-206917-5555 |
_______________________________________________
RAUC mailing list
