mail archive of the rauc mailing list
 help / color / mirror / Atom feed
From: Enrico Joerns <ejo@pengutronix.de>
To: caglar.kilimci@accenture.com
Cc: rauc@pengutronix.de
Subject: Re: [RAUC] RUAC service
Date: Mon, 10 Apr 2017 11:18:27 +0200	[thread overview]
Message-ID: <e1e7c872-7785-f3a0-215d-6b3cc32033b3@pengutronix.de> (raw)
In-Reply-To: <00773f851c654087912d55d6987ab280@BY2PR42MB136.048d.mgd.msft.net>

Hi,

On 04/10/2017 10:40 AM, caglar.kilimci@accenture.com 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.)

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

  reply	other threads:[~2017-04-10  9:18 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-04-10  8:40 caglar.kilimci
2017-04-10  9:18 ` Enrico Joerns [this message]
2017-04-10  9:29   ` caglar.kilimci
2017-04-10 10:14     ` Enrico Joerns
2017-04-10 10:51       ` caglar.kilimci
2017-04-11  8:06         ` [RAUC] RAUC service Enrico Joerns

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=e1e7c872-7785-f3a0-215d-6b3cc32033b3@pengutronix.de \
    --to=ejo@pengutronix.de \
    --cc=caglar.kilimci@accenture.com \
    --cc=rauc@pengutronix.de \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox