[Bug 649917] Re: GLIb-WARNING **: getpwid_r(): failed due to unknown user id
Ubuntu QA's Bug Bot
bug-stats at murraytwins.com
Mon Sep 19 21:31:08 UTC 2011
** Tags added: testcase
--
You received this bug notification because you are a member of Ubuntu
Foundations Bugs, which is subscribed to plymouth in Ubuntu.
https://bugs.launchpad.net/bugs/649917
Title:
GLIb-WARNING **: getpwid_r(): failed due to unknown user id
Status in Release Notes for Ubuntu:
Won't Fix
Status in “plymouth” package in Ubuntu:
Fix Released
Status in “plymouth” source package in Lucid:
Fix Released
Status in “plymouth” source package in Maverick:
Fix Released
Bug description:
Binary package hint: plymouth
Maverick pre-RC ISO testing.
I got this error message on screen just before Desktop appears on the screen (after selecting Try Ubuntu in Ubiquity)
I remember I see it very often in Lucid installed system too.
Annoying because boot is not so smooth with this.
SRU justification:
This message is consistently emitted by plymouth whenever plymouth is included in the initramfs (either because it's needed by some other initramfs script such as cryptsetup or casper, or because the user has themself configured it to be included to provide a prettier boot experience. While plymouth normally hides the message, it is sometimes exposed either because something has switched VT7 into text mode (e.g., during suspend/resume) or because of a bug in plymouth itself. The former is aesthetic, but the latter results in many bugs filed about the message which is *not* related to their problems, making it difficult to triage plymouth bug reports.
This can be addressed for the natty release by forward-copying the
maverick-proposed SRU to natty.
TEST CASE:
1) run 'echo FRAMEBUFFER=y > /etc/initramfs-tools/conf.d/plymouth' as root
2) run 'update-initramfs -u' to regenerate the initramfs, with plymouth added
3) reboot with the splash screen enabled
4) press escape as soon as the splash screen appears; confirm that you see the GLib warning
5) install the plymouth package from -proposed
6) reboot repeatedly, and use the same technique as in step 4, to confirm that the warning message no longer appears
ProblemType: Bug
DistroRelease: Ubuntu 10.10
Package: plymouth 0.8.2-2ubuntu5
ProcVersionSignature: Ubuntu 2.6.35-22.33-generic 2.6.35.4
Uname: Linux 2.6.35-22-generic i686
Architecture: i386
Date: Tue Sep 28 15:25:59 2010
DefaultPlymouth: /lib/plymouth/themes/ubuntu-logo/ubuntu-logo.plymouth
LiveMediaBuild: Ubuntu 10.10 "Maverick Meerkat" - Release Candidate i386 (20100928)
MachineType: Acer Extensa 5220
PccardctlIdent:
Socket 0:
no product info available
PccardctlStatus:
Socket 0:
no card
ProcCmdLine: BOOT_IMAGE=/casper/vmlinuz noprompt cdrom-detect/try-usb=true persistent file=/cdrom/preseed/hostname.seed boot=casper initrd=/casper/initrd.lz quiet splash -- maybe-ubiquity
ProcEnviron:
LANG=it_IT.UTF-8
SHELL=/bin/bash
ProcFB: 0 inteldrmfb
SourcePackage: plymouth
TextPlymouth: /lib/plymouth/themes/ubuntu-text/ubuntu-text.plymouth
dmi.bios.date: 04/15/2008
dmi.bios.vendor: Phoenix Technologies LTD
dmi.bios.version: V1.34
dmi.board.name: Columbia
dmi.board.vendor: Acer
dmi.board.version: Rev
dmi.chassis.asset.tag: None
dmi.chassis.type: 10
dmi.chassis.vendor: Acer
dmi.chassis.version: N/A
dmi.modalias: dmi:bvnPhoenixTechnologiesLTD:bvrV1.34:bd04/15/2008:svnAcer:pnExtensa5220:pvr0100:rvnAcer:rnColumbia:rvrRev:cvnAcer:ct10:cvrN/A:
dmi.product.name: Extensa 5220
dmi.product.version: 0100
dmi.sys.vendor: Acer
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu-release-notes/+bug/649917/+subscriptions
More information about the foundations-bugs
mailing list