Unknown username "polkit" in message bus.....

[NAC]

I have enabled dbus and hald in rc.conf.
but when starting the system, it error pops up,
says:

starting dbus
Unknown username "polkit" in message bus configuration file
Unknown username "avahi" in message bus configuration file
starting hald..

somehow, i cannot starx no more..

could someone help with it?
thanks a lot in adv..

[crsd]

What did you do after last time you successfully started X?

[NAC]

I compiled a customized kernel...
and then, i got errors..

thank you

[NAC]

i am new to Freebsd, normally use Gentoo,
is there a way to re-compile all existing packages? or could fix it simply!
thanks

[crsd]

Customized kernel doesn't seem to be related. Deleted/installed any packages?

[fronclynne]

It sounds like you overwrote your /etc/passwd when you upgraded.
You can manually add the users polkit and avahi (you probably will need messagebus & haldaemon as well) with adduser. I don't think the UID or GID are strict, & using /sbin/nologin as the shell is probably an excellent idea.
(extracted from my /etc/passwd messagebus:*:556:556:D-BUS Daemon User:/nonexistent:/sbin/nologin
polkit:*:562:562:PolicyKit Daemon User:/nonexistent:/sbin/nologin
haldaemon:*:560:560:HAL Daemon User:/nonexistent:/sbin/nologin
avahi:*:558:558:Avahi Daemon User:/nonexistent:/sbin/nologin
& /etc/group)
messagebus:*:556:
polkit:*:562:
haldaemon:*:560:
avahi:*:558:

[NAC]

i am going to give a try thanks a lot :)

[NAC]

I have manually added those lines, after rebooting i found the error still there! it is wired!

[crsd]

You can't add them manually by editing /etc/passwd. Delete them from /etc/passwd and use `vipw` and add them (`env EDITOR=ee vipw` if you are not familar with vi).

[NAC]

You can't add them manually by editing /etc/passwd. Delete them from /etc/passwd and use `vipw` and add them (`env EDITOR=ee vipw` if you are not familar with vi).

thank you, yes i do use vi.
i am going to have a try..:)

[NAC]

thanks a lot guys, i have fixed it used this way:

cd /usr/ports/sysutils/policykit/
make reinstall reinstall clean

cd /usr/ports/net/avahi-app
make reinstall reinstall clean

also i have tried the way as crsd pointed, it helped me as well. thanks a lot.:)

[fronclynne]

You can't add them manually by editing /etc/passwd. Delete them from /etc/passwd and use `vipw` and add them (`env EDITOR=ee vipw` if you are not familar with vi).
IIRC, you can just run /usr/sbin/pwd_mkdb /etc/passwd on the munged^H^H^H^H^H^Hedited file, no?

[finndo]

I have had this same issue as well, I know the cause of my FUBAR, but the quoted text below is basically what I did to fix it, and the only thing I had to do to fix it.

the only difference is I had to do a "make deinstall" as teh second step in each one and a "make install clean" as a third and final step and then both of these problems were gone.

FreeBSD 8.0-RELEASE

I am still having mouse issues in KDE though, but it now works fine on the command line...
I also had to edit /etc/rc.conf to change my mouse bus type to "usm0" as it was set as something else, I forgot what now. additionally moused_enable was set to off. this was probably the most important thing to change!!

Anyway I need to get some sleep, hope this helps someone in the future, and if it does. please remember to login, and quote this message stating it worked (or at least put in a post referencing my post and stating that it worked, as if you do you will then be helping someone else out in the future. My biggest complaint about using the internet for troubleshooting is when you find a post from years ago that is exactly what you are having a problem with and it does not have the solution, or has several and no one said which one worked.

Good luck, and I referrenced linked this forum post from my website to help get people here if they need this help. http://www.joelperryporductions.com

thanks a lot guys, i have fixed it used this way:

cd /usr/ports/sysutils/policykit/
make reinstall reinstall clean

cd /usr/ports/net/avahi-app
make reinstall reinstall clean

also i have tried the way as crsd pointed, it helped me as well. thanks a lot.:)

[finndo]

since I am not yet allowed to edit my posts... you can also hit the thanks button on the post that helped you. Enjoy and most important have fun, if you are not, then go find something else to do.

----------------------------------------------------------
1984
At the Winter USENIX/UniForum meeting, AT&T describes its support policy for Unix:
"No advertising, no support, no bug fixes, payment in advance."

----------------------------------------------------------

[SirDice]

I am still having mouse issues in KDE though, but it now works fine on the command line...
I also had to edit /etc/rc.conf to change my mouse bus type to "usm0" as it was set as something else, I forgot what now. additionally moused_enable was set to off. this was probably the most important thing to change!!
Don't. Remove the moused_enable line completely. You have an USB mouse. It's automatically loaded. Make sure both hald and dbus are running.

[rusma]

This is interesting stuff!!

I'm trying to set up x11-wm/awesome, x11/rxvt-unicode and www/firefox under x11/Xorg on 7.3-STABLE. I'm able to xinit, but not able to move the mouse or anything.

It complains about the user "messagebus" not present...

Is it really safe to manually adding messagebus user using vi? I do not think the /usr/sbin/pwd_mkdb /etc/passwd works quite as expected (complains about the standard line 3).

OFFTOPIC: Is it possible in some way to speed up tty switching from xorg to normal (alt+ctrl+F1) in the kernel in some way?

[wblock@]

OFFTOPIC: Is it possible in some way to speed up tty switching from xorg to normal (alt+ctrl+F1) in the kernel in some way?

When moused is running in normal mode (as opposed to autostarted for USB mice), it eliminates the long pause switching back to X from console.

[rusma]

When moused is running in normal mode (as opposed to autostarted for USB mice), it eliminates the long pause switching back to X from console.

Does this have to do with the kernel?

[wblock@]

Does this have to do with the kernel?

Not to my knowledge, more like an interaction between X and moused. Try it: switch to and from X from a console, then set moused_enable="YES", restart, and try it again. I think it's the switch from console back to X that is really long if moused isn't explicitly enabled but autostarted by USB.

[rusma]

Not to my knowledge, more like an interaction between X and moused. Try it: switch to and from X from a console, then set moused_enable="YES", restart, and try it again. I think it's the switch from console back to X that is really long if moused isn't explicitly enabled but autostarted by USB.

Thanks. I'll sure try that out.

What about the rest ONTOPIC question of mine?