All of lore.kernel.org
 help / color / mirror / Atom feed
From: Ulf Samuelsson <openembedded@emagii.com>
To: openembedded-devel@lists.openembedded.org
Subject: Could not update ICEauthority file /var/lib/gdm/.ICEauthority
Date: Tue, 04 Feb 2014 12:32:02 +0100	[thread overview]
Message-ID: <52F0CFB2.2040708@emagii.com> (raw)

I built a derivative of cloud9-gnome-image/Angstrom-1.4  for the 
Beaglebone Black on an Ubuntu 12.04 host.

When I boot, I get a popup window with the text:

"Could not update ICEauthority file /var/lib/gdm/.ICEauthority"

This appears because /var/lib/gdm is not owned by gdm.
Instead it is owned by 115:125

I manually changed the owner and rebooted, and this time I did not get 
the error message.

I tracked down why:

The recipe for gdm in 
meta-openembedded/meta-gnome/recipes-gnome/gdm_2.32.2.bb contains:


------------------------------------------------------------------------------
do_install_append() {
     ...
     chown -R gdm:gdm ${D}${localstatedir}/lib/gdm
     chmod 0750 ${D}${localstatedir}/lib/gdm
     ...
}
------------------------------------------------------------------------------

Problem with this approach is that the chown command is using the 
user:group of the host .

If I do
<host> # cat /etc/passwd | grep gdm
I get:

gdm:x:115:125:Gnome Display Manager:/var/lib/gdm:/bin/false

If I do the same on the target I get:

root@beaglebone:~# cat /etc/passwd | grep gdm
I get:
gdm:x:997:993::/var/lib/gdm:/bin/sh

so I think that setting the user:group must be done in a postinstall task.


-- 
Best Regards
Ulf Samuelsson



             reply	other threads:[~2014-02-04 11:32 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-02-04 11:32 Ulf Samuelsson [this message]
2014-02-04 12:49 ` Could not update ICEauthority file /var/lib/gdm/.ICEauthority Koen Kooi

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=52F0CFB2.2040708@emagii.com \
    --to=openembedded@emagii.com \
    --cc=openembedded-devel@lists.openembedded.org \
    /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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.