Closing due to age.
If a similar bug appears in 21.10 please open a new report.
** Changed in: dbus (Ubuntu)
Status: Triaged => Invalid
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/295405
I found some of the related bugs when I experienced several of the
mentioned symptoms (restart button doesn't work, Ubuntu Software Center
doesn't work, can't open users-admin, etc). I'd just like to report
that #26 fixed all the problems.
I was experiencing said problems on a fresh install of
Michał, Kaulbach: edit /etc/passwd and replace 108 with 107 in the
messagebus line, that should fix it.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/295405
Title:
Fails to run
Indeed, the log shows D-Bus was upgraded during the process, so maybe it's the
install script that messes with GIDs...
upgrade libdbus-1-3 1.2.16-2ubuntu4.1 1.2.16-2ubuntu4.2
upgrade dbus 1.2.16-2ubuntu4.1 1.2.16-2ubuntu4.2
upgrade dbus-x11 1.2.16-2ubuntu4.1 1.2.16-2ubuntu4.2
--
You received
Natty with all updates applied as of 15 minutes ago today started generating
this same error for me, may be some regression
mike@acer64:~$ grep messagebus /etc/passwd
messagebus:x:102:108::/var/run/dbus:/bin/false
mike@acer64:~$ grep messagebus /etc/group
messagebus:x:107:
mike@acer64:~$
--
I have the same problem as David on 2008-11-28. Instead of an update, I
had major, hardware-induced series of crashes. After hardware repair I
saw identical problems, i.e. all D-BUS dependent applications refusing
to run, all the earlier-reported symptoms, including this:
# cat etc/passwd |grep
I reinstalled 'dbus' and this cleared the error but I'm seeing strange
behavior.
Logged in as a regular user.
Time and Date: all greyed out and you are not authorized..., no prompt
to enter root password.
Users and Groups: can only change Password for current user, the other
Change buttons do
Gerry: your bug doesn't present duplicate GIDs, but the problem here is
not about them. Be GIDs duplicate or not, the real issue is that the
launcher program is not owned by the 'messagebus' group. The fact that
it's using a GID used by another group is a coincidence that doesn't
change anything
It did not seem to matter that the launcher was group as 'messagebus'.
It still generated the error even after I changed the group.
In my case it was a fresh install of Ubuntu Lucid server and followed by
an install of ubuntu-desktop. Those were the main packages.
--
Fails to run
Seriously, a user cannot be expected to get into a terminal and go
searching their entire system trying to fix up GIDs that were
incorrectly set by some package. That isn't even a possible general
workaround.
This bug is a SHOWSTOPPER for Ubuntu Lucid. The majority of users are
not going to
Dennis, the bug you pointed to does not say that the user and group id
need to be the same. It says that there are two groups using the same
id which causes the error. It is perfectly allowable to have a user id
and group id be different from each other.
--
fails to run
Gerry, does the procedure explained here fixes your probem? Of course,
this feels wrong, but one explanation can be that some files on the
system still have the GID corresponding to the messagebus UID, and going
back to that value fixes the problem. You could also find those files
and fix their
Sorry for the noise, seem that the root of evil is found after reading
https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/553115.
The gid for user messagebus from /etc/passwd was different from the gid
of group messagebus in /etc/group. Edited manually and everything seems
to work like
First, let me thank everyone across the web that has been posting information
about this bug. It gave me a serious headache for a couple days until I finally
figured out a fix that worked. Here is what I did to permanently alleviate the
problem:
Delete (or comment) the messagebus line from
Reopening. Duplicate 475503 has several reporters confirming that this
still happens when upgrading to Karmic. We should find out whether this
comes from the d-bus package of from another part of the system that
recreates the group with a wrong GID. Seems really strange.
** Changed in: dbus
Also for me. I upgraded from a working 8.10 system to 9.04 ubuntu,
and the greeter didn't show any user names. Logs (syslog and gdm/*.log)
showed errors executing dbus-daemon-launch-helper and the
UID and GID of messagebus didn't match.
I fixed the GID of the messagebus user in /etc/passwd
Same here with 9.04 kubuntu... kdm drops out, I see problems launching the dbus
helper.
This worked before upgrading to 9.04, with 8.10 I had no problems.
$ grep messagebus /etc/passwd
messagebus:x:105:115::/var/run/dbus:/bin/false
$ grep 115 /etc/group
Debian-exim:x:115:
no idea how that can
On Wed, 2009-07-15 at 21:05 +, Fish wrote:
I have had the same issue as the OP
While you may have the same issue, it is unlikely you have the same bug.
Please do not hijack somebody else's report, and instead file a new bug
for your problems.
Scott
--
Scott James Remnant
Fair enough, but I'd say the chances of the two issues being related are
fairly likely (messagebus user points to wrong messagebus group in both
cases). I'll file another bug report, but I'm pretty sure it'll be
marked as a duplicate of this one.
--
fails to run
(Expired)
This really looks like something removed the messagebus group and caused
it to be recreated with a new gid
** Changed in: dbus (Ubuntu)
Status: Incomplete = Invalid
--
fails to run lib/dbus-1.0/dbus-daemon-launch-helper
https://bugs.launchpad.net/bugs/295405
You received this
I think it's something wrong in the dbus setup package.
I have had the same issue as the OP - the dbus executable file has permissions
set up improperly. I also have most of the system groups 1000 exported out
from a common NIS server. ( need common administrators across various
computers,
Either that, or we add a new module to nsswitch to merge NIS+local
groups in a way that is better than the one right now [check NIS, then
check local], so we don't have 2 database, and thus, problems like
this
--
fails to run lib/dbus-1.0/dbus-daemon-launch-helper
It's a somewhat-bug in the setup package...
** Changed in: dbus (Ubuntu)
Status: Invalid = Confirmed
--
fails to run lib/dbus-1.0/dbus-daemon-launch-helper
https://bugs.launchpad.net/bugs/295405
You received this bug notification because you are a member of Ubuntu
Bugs, which is
So you are saying that on your system, both the ssl-cert and the
messagebox group shared the same group ID? Eww... Any idea how this
could have happened?
Your command certainly works, although find / -uid 112 is the
canonical, and probably more efficient, incantation.
As for your attached
I have never used the program users-admin. However, an odd thing just
happened. When I tried to start users-admin to see if it looked
familiar, I got the massage that I didn't have permission to run it. So
I checked the messagebus user in /etc/passwd, and it was okay. I then
retested all of
OK, thanks. Unfortunately that didn't give me any insight yet. Let's try
something else:
sudo strace -s 4096 -f -o /tmp/trace -p `ps h -o %p -U messagebus`
This will block. Open a second terminal, and do
ck-list-sessions
Then go back to the first one, press Control-C, and attach /tmp/trace
I really appreciate the interest you are taking in solving this.
** Attachment added: trace
http://launchpadlibrarian.net/20003330/trace
--
fails to run lib/dbus-1.0/dbus-daemon-launch-helper
https://bugs.launchpad.net/bugs/295405
You received this bug notification because you are a member
Ah, that revealed something more interesting:
9568 execve(/lib/dbus-1.0/dbus-daemon-launch-helper,
[/lib/dbus-1.0/dbus-daemon-launch-helper,
[...]
9568 ... execve resumed )= -1 EACCES (Permission denied)
So apparently /lib/dbus-1.0/dbus-daemon-launch-helper isn't executable
for
You comment that apparently /lib/dbus-1.0/dbus-daemon-launch-helper
isn't executable for the user messagebus caused me to look at
/etc/passwd and /etc/group on the computer with these problems, and I
found a major problem.
The entry in /etc/passwd was:
Ah, that would indeed be it. Now, the interesting question is indeed how
that happened. I believe you that you didn't hand-edited that, it would
be a very unusual thing to do. Did you ever use sytem - admin - users
and groups? (the program users-admin). In earlier releases it had a
grave bug which
[EMAIL PROTECTED]:~$ strace -o /tmp/trace -f ck-list-sessions
** (ck-list-sessions:14000): WARNING **: Failed to get list of seats:
Failed to execute program /lib/dbus-1.0/dbus-daemon-launch-helper:
Success
However, it did generate the attached trace.
** Attachment added: trace
1. sudo killall jockey-backend
returns
jockey-backend: no process killed
2. sudo /usr/share/jockey/jockey-backend 21 | tee /tmp/jockey.log
3. Ran the Hardware Drivers application, and nothing happened.
4. Entered ^C in terminal window
5. cat /tmp/jockey.log showed that the file was empty,
OK, seems you have a much more general problem with D-BUS then. To be
honest I don't really know what to look for now, but let's first make
sure the other packages are correct. What's the output of
dpkg -l dbus policykit consolekit
ck-list-sessions
?
** Changed in: dbus (Ubuntu)
[EMAIL PROTECTED]:/etc/default$ dpkg -l dbus policykit consolekit
Desired=Unknown/Install/Remove/Purge/Hold
| Status=Not/Inst/Cfg-files/Unpacked/Failed-cfg/Half-inst/trig-aWait/Trig-pend
|/ Err?=(none)/Hold/Reinst-required/X=both-problems (Status,Err: uppercase=bad)
||/ Name
Right, that again. Can you please try
strace -o /tmp/trace -f ck-list-sessions
and attach /tmp/trace here?
--
fails to run lib/dbus-1.0/dbus-daemon-launch-helper
https://bugs.launchpad.net/bugs/295405
You received this bug notification because you are a member of Ubuntu
Bugs, which is
Ah, no; jockey-common depends on policykit, which depends on dbus. So
unless you manually forcefully removed it, you should have dbus
installed. Can you please give me the output of
ls -l /lib/dbus-1.0/dbus-daemon-launch-helper
?
--
fails to run lib/dbus-1.0/dbus-daemon-launch-helper
ls -l /lib/dbus-1.0/dbus-daemon-launch-helper
-rwsr-xr-- 1 root messagebus 47704 2008-10-07 07:26
/lib/dbus-1.0/dbus-daemon-launch-helper
--
fails to run lib/dbus-1.0/dbus-daemon-launch-helper
https://bugs.launchpad.net/bugs/295405
You received this bug notification because you are a member of
That looks correct. Can you reproduce this, or was it an one-time
glitch? If it happens every time, please try this:
sudo killall jockey-backend
sudo /usr/share/jockey/jockey-backend 21 | tee /tmp/jockey.log
then try to start jockey from the menu. Does that work now? After you
close the
38 matches
Mail list logo
