You are not logged in.
thanks... I don't know why I had the multilib repository disabled since March 2013.
Offline
arojas wrote:If you don't understand it, then you should answer yes. That's why it is the default.
I think that could be a bit dangerous. You don't think it's better to do some research before agreeing to make system changes which you don't understand? If you select (N), you can always come right back and do it again after checking to see what it's wanting you to agree to.
No. If you select "no", you are leaving your system in a partially updated (and therefore unsupported and potentially broken) state. In this case this didn't happen because a conflict prevents the update from proceeding. Answering "yes" is always the safe option here.
Offline
FWIW: NetworkManager failed after the last update (It gives 'a connection has failed'; initially it shows the networks, but fails connecting. After that it won't show any networks). I didn't investigate it yet but I think NetworkManager also does stuff through dbus so it might be related.
Netctl works though so I switched to that for now.
(edit: never mind, too quick: missed that network manager package was also upgraded. The issue seems to be with that one, not with the d-bus unsplit)
Last edited by blaatenator (2016-08-29 11:17:49)
Offline
Not sure why this thread gets all this attention. As pointed out several times, it's a trivial matter of moving files from one package to another. The different issue in #16 already has a thread of its own.
Mods are just community members who have the occasionally necessary option to move threads around and edit posts. -- Trilby
Offline
I updated shortly after the first few replies and nothing bad happened. Thanks, I will trust the devs' suggested default going forward and come back complaining if something brakes
Marked as solved.
Last edited by Bednar (2016-08-29 20:47:10)
Offline
Well I had upgaded previously and this the resulting error message in .xsession-errors
Thunar: Failed to initialize Xfconf: Using X11 for dbus-daemon autolaunch was disabled at compile time, set your DBUS_SESSION_BUS_ADDRESS instead
and thunar comes up as 640x480 size.
I had gotten some this error when opening a root xfce terminal.
Failed to init libxfconf: Using X11 for dbus-daemon autolaunch was disabled at compile time, set your DBUS_SESSION_BUS_ADDRESS instead.
So I downgraded back to previious version of dbus and everything was fine.
So I truly believe there is something going on with the new dbus.
Offline
So I truly believe there is something going on with the new dbus.
The different issue in #16 already has a thread of its own.
https://bbs.archlinux.org/viewtopic.php?id=216001
Last edited by Alad (2016-08-29 21:34:26)
Mods are just community members who have the occasionally necessary option to move threads around and edit posts. -- Trilby
Offline
I solved my problem by removing dbus files located at /etc/systemd/user (dbus.service, dbus.socket, default.target.wants/dbus.socket).
SDDM is now visible and launches Kde as usual.
Last edited by Sebarres (2016-08-30 15:28:25)
Offline