When D-Bus starts it warns of an unknown gdm user in the dbus configuration. Reproducible: Always Steps to Reproduce: 1. Find a system with dbus and consolekit installed and no user called "gdm" 2. sudo /etc/init.d/dbus restart 3. Actual Results: # /etc/init.d/dbus restart * Stopping ConsoleKit daemon ... [ ok ] * Stopping Hardware Abstraction Layer daemon ... [ ok ] * Stopping D-BUS system messagebus ... [ ok ] * Starting D-BUS system messagebus ... Unknown username "gdm" in message bus configuration file [ ok ] * Starting ConsoleKit daemon ... [ ok ] * Starting Hardware Abstraction Layer daemon ... [ ok ] Expected Results: # /etc/init.d/dbus restart * Stopping ConsoleKit daemon ... [ ok ] * Stopping Hardware Abstraction Layer daemon ... [ ok ] * Stopping D-BUS system messagebus ... [ ok ] * Starting D-BUS system messagebus ... [ ok ] * Starting ConsoleKit daemon ... [ ok ] * Starting Hardware Abstraction Layer daemon ... [ ok ] emerge --info: Portage 2.1.3.9 (default-linux/x86/2007.0/desktop, gcc-4.2.0, glibc-2.6.1-r0, 2.6.22-gentoo-r6 i686) ================================================================= System uname: 2.6.22-gentoo-r6 i686 Genuine Intel(R) CPU T2400 @ 1.83GHz Timestamp of tree: Mon, 10 Sep 2007 22:20:01 +0000 ccache version 2.4 [enabled] app-shells/bash: 3.2_p17-r1 dev-lang/python: 2.5.1-r2 dev-python/pycrypto: 2.0.1-r6 dev-util/ccache: 2.4-r7 sys-apps/baselayout: 1.12.10-r4 sys-apps/sandbox: 1.2.18.1 sys-devel/autoconf: 2.13, 2.61-r1 sys-devel/automake: 1.5, 1.6.3, 1.7.9-r1, 1.8.5-r3, 1.9.6-r2, 1.10 sys-devel/binutils: 2.18.50.0.1 sys-devel/gcc-config: 1.4.0-r2 sys-devel/libtool: 1.5.24 virtual/os-headers: 2.6.22-r2 ACCEPT_KEYWORDS="x86 ~x86" CBUILD="i686-pc-linux-gnu" CFLAGS=" -march=prescott -O2 -pipe -fomit-frame-pointer " CHOST="i686-pc-linux-gnu" CONFIG_PROTECT="/etc /usr/share/X11/xkb" CONFIG_PROTECT_MASK="/etc/env.d /etc/gconf /etc/revdep-rebuild /etc/terminfo /etc/texmf/web2c /etc/udev/rules.d" CXXFLAGS=" -march=prescott -O2 -pipe -fomit-frame-pointer " DISTDIR="/usr/portage/distfiles" FEATURES="buildpkg ccache distlocks fixpackages metadata-transfer parallel-fetch sandbox sfperms strict unmerge-orphans userfetch userpriv usersandbox" GENTOO_MIRRORS="http://gentoo.virginmedia.com/" MAKEOPTS="-j4" PKGDIR="/usr/portage/packages" PORTAGE_RSYNC_OPTS="--recursive --links --safe-links --perms --times --compress --force --whole-file --delete --delete-after --stats --timeout=180 --exclude=/distfiles --exclude=/local --exclude=/packages --filter=H_**/files/digest-*" PORTAGE_TMPDIR="/var/tmp" PORTDIR="/usr/portage" PORTDIR_OVERLAY="/usr/local/portage /home/endgame/Code/overlay /usr/local/layman/sunrise /usr/local/layman/lila-theme" SYNC="rsync://rsync.europe.gentoo.org/gentoo-portage" USE="X a52 aac acpi alsa bash-completion berkdb bitmap-fonts cairo ccache cdr cli cracklib dbus divx dri dvd dvdr dvdread eds emacs emboss encode evo fam firefox fortran gdbm gif gpm gstreamer hal iconv ipv6 isdnlog jpeg kqemu mad midi mikmod mmx mp3 mpeg mudflap ncurses nls nptl nptlonly nsplugin ogg opengl openmp pam pcre pdf perl png pppd python qt3support quicktime readline reflection sdl session spl sse sse2 ssl svg tcpd theora tiff timidity truetype truetype-fonts type1-fonts unicode vorbis win32codecs x86 xml xorg xv xvid zlib" ALSA_CARDS="hda-intel" ALSA_PCM_PLUGINS="adpcm alaw asym copy dmix dshare dsnoop empty extplug file hooks iec958 ioplug ladspa lfloat linear meter mulaw multi null plug rate route share shm softvol" ELIBC="glibc" INPUT_DEVICES="evdev keyboard mouse synaptics" KERNEL="linux" LCD_DEVICES="bayrad cfontz cfontz633 glk hd44780 lb216 lcdm001 mtxorb ncurses text" USERLAND="GNU" VIDEO_CARDS="nvidia" Unset: CTARGET, EMERGE_DEFAULT_OPTS, INSTALL_MASK, LANG, LC_ALL, LDFLAGS, LINGUAS, PORTAGE_COMPRESS, PORTAGE_COMPRESS_FLAGS, PORTAGE_RSYNC_EXTRA_OPTS
So basically, rather than remove the un-used user (which will require a re-emerge of consolekit if you install GDM so it has the correct user in the configuration) yourself, you would like us to on everyones system? I am not sure I understand really, could you clarify what exactly you want to happen here?
I'm not sure what the best action to take is. I see a few options: 1. What you just said: Don't include that part of the config file if there's no gdm user. 2. Add a use flag (gnome, perhaps?) to control the inclusion of the gdm part of the config. 3. enewuser gdm like the gdm ebuilds do. 4. einfo a message that the config file might need changing (check if gdm is installed before doing so?) 5. Mark this as RESOLVED INVALID and assume that the user can tinker their config files as appropriate.
well currently ConsoleKit in Gentoo is only used by GDM... I'm curious as to what you're trying to accomplish with ConsoleKit. However, I'll keep this ticket opened since there will be some changes in ConsoleKit in the future.
It will also be pulled in by x11-apps/xinit if USE=hal. I'm not sure why. That probably should've been clearer.
I can confirm this. No gnome here on my KDE only system (hence no user gdm) but consolekit gets pulled in via kdm and xinit with USE hal. On every startup I get the error message described above. I like Jack's suggestion 2. in Comment #2. Seems consistent with the general gentoo approach. If a user installs gnome later and sets USE gnome, emerge --newuse will catch that consolekit needs to be reinstalled. If a user has USE gnome set but gnome is not installed or user gdm does not exist, they will see the error message alerting them that something is wrong. Easy and clean solution. (My 2c.)
Created attachment 131057 [details, diff] Possible patch
Same over here, everybody who is not using gnome/gdm will get a dbus error. If consolekit only works with gnome/gdm then it should only be pulled in the deptree by xinit if xinit has an activated (currently non-existing) gnome useflag.
It's not an error it's a warning. ConsoleKit ships with a hardcoded file that has settings for gdm. Stop the big fuss, it's a minor warning that basically says the user doesn't exist so dbus will ignore the section that contains it. Which is perfectly find since it's only for gdm.
Not sure who is making a "fuss" here, it's certainly not me ... ;-) I thought that gentoo was about choice, e.g. the choice not to install gnome related stuff if I don't want it (for whatever reason), and that USE flags existed precisely for that reason. So, what is wrong with the solution suggested in Comment #6? Or, is consolekit being wrongly pulled by xinit -gnome as Comment #7 suggests? It would be good if those in the know would tell us so we who care can produce a patch. Cheers, Jochen
The "patch" for those of you who need one, is to remove that section from the ConsoleKit.conf file in /etc/dbus-1/system.d - This is removed upstream, however, currently it is in place, and we tend to follow upstream with ConsoleKit due to its nature. If you don't like that, I do apologize, but that is our policy. Remove the user to get rid of the warning, but if you emerge gdm, and things stop working *shrug* There is a new version of ConsoleKit released earlier that removes the user, I am currently working on committing it to Gentopia, however, I have no idea how it affects things in tree yet - it removes the user from the config, but it expects things like PolicyKit to be in place. Until these other bits are in place, the user stays.
Jochen: You are creating a fuss by saying "OMG GENTOO IS ABOUT CHOICE AND YOU'RE VIOLATING MY CHOICE!". No one is forcing you to install anything or any GNOME bits. You're getting a warning that you're going to have to deal with since YOU CHOOSE to run ~arch of Gentoo which is considered Gentoo's unstable branch. Guess what you sometimes have bumps that you have to deal with. Also, don't say Gentoo is about choice because it's not. Gentoo is about developers writing code or working on what scratches their itch. If it happens to work for you, then great, if not... if we get around to it or are in the mood we'll fix it. But otherwise, it's up to you to fix it. You also have the choice and the ability to have a local overlay which would overlay this ebuild and provide the functionality you want. If that's not good enough for you, become a developer yourself and scratch that itch. Bugzilla is not your personal support forum for demanding any and all features you want cause guess what? I'm not paid for this. And until I am, it's all about scratching my itch and my itch alone.
Doug: if you are reading my previous comment #9 carefully, you will A) find a smiley and B) realize that all I asked for is some hint if the right thing to do (TM) is to erase the part of the config file (meanwhile confirmed in comment #10, thanks Steev), or to not have xinit depend on consolekit. The rest I can do myself, otherwise I would indeed not run ~x86. If you even care to go back to my comment #5, you will find that I tried to engage in a debate about the right design of this tiny little piece of gentoo. I am sorry to see that such contributions are apparently not welcome.
Jochen: Anytime someone grabs their soapbox and hops on it, you won't see a favorable response from me. But that aside..... ConsoleKit 0.2.3 has been released invalidating this bug and it's been committed to the tree.
