dbus-core removal [Solved]

Antunes · 2012-12-05 17:17:24

My dbus-core was just removed, it seems it is no longer in the repos. This happened when dbus upgraded to 1.6.8-5.

Ever since, I cannot automount internal drives and several other modules seem to be broken. Is it intentional to remove dbus-core from the repos and what do I have to do to compensate for that?

Last edited by Antunes (2012-12-06 11:18:25)

bgc1954 · 2012-12-05 17:41:58

I'd guess that you didn't have any packages installed that required dbus-core so it was removed. I see the new dbus doesn't have dbus-core as a dep. I still have dbus-core installed since I have a couple of packages that still require it so pacman must have left it alone. Have you switched over to systemd yet?

Last edited by bgc1954 (2012-12-05 17:42:25)

65kid · 2012-12-05 17:42:53

dbus-core has been merged into dbus, that's why it is being removed.

sano · 2012-12-05 17:45:39

Out of curiousity, and to check if your problems are reproducible: What other modules are broken?
(Auto)mounting internal partitions seems to break all the time, and I am using fstab for automounting and udevil for "manual" mounting...

Jristz · 2012-12-05 17:46:59

and as same time a filesystem update was merged
not sure how manage it because only add dbus as a new user id and the flag fro dbus-core into dbus make my thinking that is going to be bad if I merge it incoprreclty

any idea about it?

Antunes · 2012-12-05 17:49:01

@sano: Another problem was that I could not open X windows as root: see here

 sudo thunar                                                                 
No protocol specified
Thunar: Cannot open display:

Is this unrelated?

Last edited by Antunes (2012-12-05 17:49:38)

Stebalien · 2012-12-05 17:56:21

Antunes wrote:

@sano: Another problem was that I could not open X windows as root: see here
 sudo thunar                                                                 
No protocol specified
Thunar: Cannot open display: 
Is this unrelated?

Yes. You'll notice that it says, "Cannot open display: ". That means that the DISPLAY variable is not set. Use something like gksudo/kdesudo etc.

bgc1954 · 2012-12-05 17:59:44

Try reading https://wiki.archlinux.org/index.php/Ru … ps_as_root

We try to encourage people to do some of their own research before asking on the forum.

edit: I gotta learn how to type or think faster.

Last edited by bgc1954 (2012-12-05 18:00:38)

Antunes · 2012-12-05 18:02:00

OK, so this seems to be unrelated. Is nobody else having these automount problems?

@bgc1954: this was just a side issue, the main problem is the automounting.

Last edited by Antunes (2012-12-05 18:02:46)

omeringen · 2012-12-05 18:06:27

(1/1) removing dbus-core                                                                         [---------------------------------------------------------] 100%
userdel: user dbus is currently used by process 318
groupdel: cannot remove the primary group of user 'dbus'
error: command failed to execute correctly
(1/3) upgrading filesystem                                                                       [---------------------------------------------------------] 100%
warning: /etc/group installed as /etc/group.pacnew
warning: /etc/passwd installed as /etc/passwd.pacnew
warning: /etc/gshadow installed as /etc/gshadow.pacnew
warning: /etc/shadow installed as /etc/shadow.pacnew
(2/3) upgrading dbus                                                                             [---------------------------------------------------------] 100%
New optional dependencies for dbus
    libx11: dbus-launch support
(3/3) upgrading hwids                                                                            [---------------------------------------------------------] 100%

Anything about the error on (1/1) ?

Antunes · 2012-12-05 18:07:40

Thx, omeringen. Had that error myself, sorry for not posting earlier, but I had lost the logs upon reboot.

Stebalien · 2012-12-05 18:12:20

For everyone in this thread: just install the new dbus package and the new filesystem package and make sure to merge your .pacnew files. If any of your old packages depend on dbus-core, they should still work as dbus now provides dbus-core.

There have been two changes:
1. The dbus package used to only include dbus-launch while dbus-core included dbus itself. Now, the dbus package includes everything.
2. The 'dbus' user is no longer added by the install script in the dbus-core/dbus package; it is defined in the default /etc/{passwd,group,shadow,gshadow} files in the filesystem package.

googol-1 · 2012-12-05 18:12:59

Jristz wrote:

and as same time a filesystem update was merged
not sure how manage it because only add dbus as a new user id and the flag fro dbus-core into dbus make my thinking that is going to be bad if I merge it incoprreclty
any idea about it?

No need to merge the .pacnew files in this case.
You should have a dbus user and groupe already. It was added by dbus-core and now it is provided by filesystem.
If you don't have them than merge the .pacnew

And about the error:
https://mailman.archlinux.org/pipermail … 24118.html

Last edited by googol-1 (2012-12-05 18:23:42)

Stebalien · 2012-12-05 18:13:14

omeringen wrote:

(1/1) removing dbus-core                                                                         [---------------------------------------------------------] 100%
userdel: user dbus is currently used by process 318
groupdel: cannot remove the primary group of user 'dbus'
error: command failed to execute correctly
(1/3) upgrading filesystem                                                                       [---------------------------------------------------------] 100%
warning: /etc/group installed as /etc/group.pacnew
warning: /etc/passwd installed as /etc/passwd.pacnew
warning: /etc/gshadow installed as /etc/gshadow.pacnew
warning: /etc/shadow installed as /etc/shadow.pacnew
(2/3) upgrading dbus                                                                             [---------------------------------------------------------] 100%
New optional dependencies for dbus
    libx11: dbus-launch support
(3/3) upgrading hwids                                                                            [---------------------------------------------------------] 100%

Anything about the error on (1/1) ?

That error is expected and unavoidable, ignore it (or read the arch-dev-public mailing list for an explanation).

googol-1 wrote:

No need to merge the .pacnew files in this case.
You should have a dbus user and groupe already. It was added by dbus-core and now it is provided by filesystem.

Theoretically, if the userdel/groupdel commands actually worked, you would have to merge the pacnew files. However, they don't so you are correct and this shouldn't be a problem. However, it's still a good idea to merge them for consistency.

Last edited by Stebalien (2012-12-05 18:15:36)

bgc1954 · 2012-12-05 18:16:15

@omeringen - A simple search on the forums revealed this: https://bbs.archlinux.org/viewtopic.php?pid=1187801 which is eerily similair.

edit: Again, beaten to the punch and a tad off the mark but perhaps relevant.

Last edited by bgc1954 (2012-12-05 18:20:37)

Antunes · 2012-12-05 18:22:18

Hmm, just checked and the groupnew file does not contain anything which is not alread in the old one.

So is it possible that the automount problems are completely unrelated?

teateawhy · 2012-12-05 19:29:51

There was a change in the /etc/passwd file. The dbus entry has been modified a bit.
Old entry:
dbus:x:81:81:System message bus:/:/bin/false
New entry:
dbus:x:81:81:dbus:/:/sbin/nologin
Is it safe to change to the new entry? I assume it is because the group number is the same and only description and shell have been changed.

jasonwryan · 2012-12-05 19:32:25

Antunes wrote:

So is it possible that the automount problems are completely unrelated?

I can confirm that, using udiskie, automounting has gone south with the new dbus. I haven't had time to look at it more closely...

teatetawhy wrote:

dbus:x:81:81:dbus:/:/sbin/nologin
Is it safe to change to the new entry? I assume it is because the group number is the same and only description and shell have been changed.

It worked for me

root · 2012-12-05 19:48:28

So if I understand correctly *all* old entries are simply to be replaced by the new info regarding dbus, f.e. dbus:!:: in gshadow etc.?

teateawhy · 2012-12-05 20:28:54

root wrote:

So if I understand correctly *all* old entries are simply to be replaced by the new info regarding dbus, f.e. dbus:!:: in gshadow etc.?

Do not replace your original shadow file. It contains hashed passwords, if you overwrite the file your passwords will be empty and everyone can login...

hydn · 2012-12-05 20:30:24

Hey me to. I'm skeptical about removing until I can confirm others report doing so without issue.

Sorry I don't know the answer to your question but I have one of my own. Anyone can confirm allowing this removal without any issues after reboot etc?

thx

root · 2012-12-05 20:37:58

teateawhy wrote:

Do not replace your original shadow file. It contains hashed passwords, if you overwrite the file your passwords will be empty and everyone can login...

No, no I do no refer to replace the file but to set the dbus entries to the ones featured in the .pacnew files.

F.e. in groups, if I remember correctly, I had already the pacnew entry but changed it in order to have a more 'standard' listing. The passwd update is working fine so far, just like mentioned by jasonwryan in #18 (and I presume in your case too).

But in gshadow I have besides the update info also a dbus:!:: entry. Therefore I am not sure if that has to be removed and only the dbus:x:: has to be kept or the keeping should apply to both.

Last edited by root (2012-12-05 20:39:43)

T.J.S. · 2012-12-05 20:56:27

Also in /etc/shadow the dbus line is changed, but if I understand correctly this should stay the way it was.

Anyone can elaborate more on the shell change in dbus line in /etc/passwd? I want to change it, but the lack of knowledge is refraining me.

Last edited by T.J.S. (2012-12-05 20:58:03)

root · 2012-12-05 21:06:37

T.J.S. wrote:

Also in /etc/shadow the dbus line is changed, but if I understand correctly this should stay the way it was.
Anyone can elaborate more on the shell change in dbus line in /etc/passwd? I want to change it, but the lack of knowledge is refraining me.

Mind sharing the source for the dbus line to stay the same?

As for your shell doubt check out #17/#18 in this same thread.

Last edited by root (2012-12-05 21:09:15)

gordoleon · 2012-12-05 21:09:42

The only problem i've been having is that automounting is gone wich is a real pain.

Anyone with more info about all the .pacnew's im quite confused here.=|

Arch Linux

#1 2012-12-05 17:17:24

dbus-core removal [Solved]

#2 2012-12-05 17:41:58

Re: dbus-core removal [Solved]

#3 2012-12-05 17:42:53

Re: dbus-core removal [Solved]

#4 2012-12-05 17:45:39

Re: dbus-core removal [Solved]

#5 2012-12-05 17:46:59

Re: dbus-core removal [Solved]

#6 2012-12-05 17:49:01

Re: dbus-core removal [Solved]

#7 2012-12-05 17:56:21

Re: dbus-core removal [Solved]

#8 2012-12-05 17:59:44

Re: dbus-core removal [Solved]

#9 2012-12-05 18:02:00

Re: dbus-core removal [Solved]

#10 2012-12-05 18:06:27

Re: dbus-core removal [Solved]

#11 2012-12-05 18:07:40

Re: dbus-core removal [Solved]

#12 2012-12-05 18:12:20

Re: dbus-core removal [Solved]

#13 2012-12-05 18:12:59

Re: dbus-core removal [Solved]

#14 2012-12-05 18:13:14

Re: dbus-core removal [Solved]

#15 2012-12-05 18:16:15

Re: dbus-core removal [Solved]

#16 2012-12-05 18:22:18

Re: dbus-core removal [Solved]

#17 2012-12-05 19:29:51

Re: dbus-core removal [Solved]

#18 2012-12-05 19:32:25

Re: dbus-core removal [Solved]

#19 2012-12-05 19:48:28

Re: dbus-core removal [Solved]

#20 2012-12-05 20:28:54

Re: dbus-core removal [Solved]

#21 2012-12-05 20:30:24

Re: dbus-core removal [Solved]

#22 2012-12-05 20:37:58

Re: dbus-core removal [Solved]

#23 2012-12-05 20:56:27

Re: dbus-core removal [Solved]

#24 2012-12-05 21:06:37

Re: dbus-core removal [Solved]

#25 2012-12-05 21:09:42

Re: dbus-core removal [Solved]

Board footer