[Bug 802525] New: dbus hung on upgrade from Beta
https://bugzilla.novell.com/show_bug.cgi?id=802525 https://bugzilla.novell.com/show_bug.cgi?id=802525#c0 Summary: dbus hung on upgrade from Beta Classification: openSUSE Product: openSUSE 12.3 Version: RC 1 Platform: x86-64 OS/Version: SUSE Other Status: NEW Severity: Major Priority: P5 - None Component: Basesystem AssignedTo: bnc-team-screening@forge.provo.novell.com ReportedBy: bwiedemann@suse.com QAContact: qa-bugs@suse.de Found By: --- Blocker: --- User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:18.0) Gecko/20100101 Firefox/18.0 dbus hung on rtkit upgrade from Beta Reproducible: Always Steps to Reproduce: 1. have 12.3-Beta 2. run zypper up Actual Results: installtion of rtkit blocked forever in %post script with ps axf showing a dbus-send --system --type=method_call --dest=org.freedesktop.DBus / org.freedesktop.DBus.ReloadConfig and firefox would not start either then. rcdbus restart made it unblock Expected Results: upgrade should be possible without user-interaction -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.
https://bugzilla.novell.com/show_bug.cgi?id=802525
https://bugzilla.novell.com/show_bug.cgi?id=802525#c1
Rich Coe
https://bugzilla.novell.com/show_bug.cgi?id=802525
https://bugzilla.novell.com/show_bug.cgi?id=802525#c2
Bernhard Wiedemann
https://bugzilla.novell.com/show_bug.cgi?id=802525
https://bugzilla.novell.com/show_bug.cgi?id=802525#c3
--- Comment #3 from Robert Milasan
https://bugzilla.novell.com/show_bug.cgi?id=802525
https://bugzilla.novell.com/show_bug.cgi?id=802525#c4
Greg Freemyer
https://bugzilla.novell.com/show_bug.cgi?id=802525
https://bugzilla.novell.com/show_bug.cgi?id=802525#c
Greg Freemyer
https://bugzilla.novell.com/show_bug.cgi?id=802525
https://bugzilla.novell.com/show_bug.cgi?id=802525#c5
Stanislav Brabec
https://bugzilla.novell.com/show_bug.cgi?id=802525
https://bugzilla.novell.com/show_bug.cgi?id=802525#c6
--- Comment #6 from Robert Milasan
https://bugzilla.novell.com/show_bug.cgi?id=802525
https://bugzilla.novell.com/show_bug.cgi?id=802525#c7
Hans Petter Jansson
https://bugzilla.novell.com/show_bug.cgi?id=802525
https://bugzilla.novell.com/show_bug.cgi?id=802525#c8
--- Comment #8 from Hans Petter Jansson
https://bugzilla.novell.com/show_bug.cgi?id=802525
https://bugzilla.novell.com/show_bug.cgi?id=802525#c9
--- Comment #9 from Hans Petter Jansson
https://bugzilla.novell.com/show_bug.cgi?id=802525
https://bugzilla.novell.com/show_bug.cgi?id=802525#c10
--- Comment #10 from Hans Petter Jansson
https://bugzilla.novell.com/show_bug.cgi?id=802525
https://bugzilla.novell.com/show_bug.cgi?id=802525#c11
--- Comment #11 from Hans Petter Jansson
https://bugzilla.novell.com/show_bug.cgi?id=802525
https://bugzilla.novell.com/show_bug.cgi?id=802525#c12
Scott Reeves
https://bugzilla.novell.com/show_bug.cgi?id=802525
https://bugzilla.novell.com/show_bug.cgi?id=802525#c13
Robert Milasan
https://bugzilla.novell.com/show_bug.cgi?id=802525
https://bugzilla.novell.com/show_bug.cgi?id=802525#c14
Kamil Dziedzic
https://bugzilla.novell.com/show_bug.cgi?id=802525
https://bugzilla.novell.com/show_bug.cgi?id=802525#c15
--- Comment #15 from Kamil Dziedzic
https://bugzilla.novell.com/show_bug.cgi?id=802525
https://bugzilla.novell.com/show_bug.cgi?id=802525#c16
--- Comment #16 from Greg Freemyer
My update to 12.3 just stopped on rtkit too. Advice from bug report 'rcdbus restart made it unblock' doesn't work for me.
#rcdbus restart redirecting to systemctl restart dbus Failed to issue method call: Unit name dbus is not valid.
:/ Any idea how can I go further?:)
I just rebooted and reran "zypper dup". In my case I was also hit with the network not starting bug, so I had to run "NetworkManager" from the kde konsole to get my network online, the run "zypper dup". -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.
https://bugzilla.novell.com/show_bug.cgi?id=802525
https://bugzilla.novell.com/show_bug.cgi?id=802525#c17
Stephan Kulow
https://bugzilla.novell.com/show_bug.cgi?id=802525
https://bugzilla.novell.com/show_bug.cgi?id=802525#c18
Frederic Crozat
https://bugzilla.novell.com/show_bug.cgi?id=802525
https://bugzilla.novell.com/show_bug.cgi?id=802525#c19
Robert Milasan
https://bugzilla.novell.com/show_bug.cgi?id=802525
https://bugzilla.novell.com/show_bug.cgi?id=802525#c20
--- Comment #20 from Frederic Crozat
https://bugzilla.novell.com/show_bug.cgi?id=802525
https://bugzilla.novell.com/show_bug.cgi?id=802525#c21
Robert Milasan
https://bugzilla.novell.com/show_bug.cgi?id=802525
https://bugzilla.novell.com/show_bug.cgi?id=802525#c22
Frederic Crozat
https://bugzilla.novell.com/show_bug.cgi?id=802525
https://bugzilla.novell.com/show_bug.cgi?id=802525#c23
Robert Milasan
https://bugzilla.novell.com/show_bug.cgi?id=802525
https://bugzilla.novell.com/show_bug.cgi?id=802525#c24
--- Comment #24 from Hans Petter Jansson
Second, I'm afraid we have a inconsistency until dbus is restarted, because dbus library will try to connect to system bus using the new address for the unix socket used by system bus and system bus will still be only listening to the old socket path (I might be wrong..).
netstat confirms this. The old dbus-daemon is still listening on /var/run/dbus/system_bus_socket (both before and after the new dbus package is installed), while packages compiled with the new dbus try to talk to it at /run/dbus/system_bus_socket. I could probably come up with a patch that makes clients try to connect to both /run/dbus/system_bus_socket and /var/run/dbus/system_bus_socket as a stopgap. It'd have to be in for as long as we want to support a dist-upgrade across this change. Would that be acceptable? -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.
https://bugzilla.novell.com/show_bug.cgi?id=802525
https://bugzilla.novell.com/show_bug.cgi?id=802525#c25
Frederic Crozat
BTW, can't we add to dbus.service and/or dbus.socket some After=var-run.mount var-lock.mount ?
this is not needed: dbus.socket has "After=sysinit.target" ; sysinit.target has "After=local-fs.target" and var-run.mount has "Before=local-fs.target", so we are garanteed the socket is created by systemd after /var/run has been bind mounted. -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.
https://bugzilla.novell.com/show_bug.cgi?id=802525
https://bugzilla.novell.com/show_bug.cgi?id=802525#c26
Robert Milasan
https://bugzilla.novell.com/show_bug.cgi?id=802525
https://bugzilla.novell.com/show_bug.cgi?id=802525#c27
Frederic Crozat
Yes, but thats for dbus.service, what about dbus.socket:
[Unit] Description=D-Bus System Message Bus Socket
[Socket] ListenStream=/var/run/dbus/system_bus_socket
Isn't this created by systemd?
It is, but when you check systemctl show dbus.socket | grep After=, you'll notice sysinit.target which does pull var-run.mount (through local-fs.target). So we are safe here. -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.
https://bugzilla.novell.com/show_bug.cgi?id=802525
https://bugzilla.novell.com/show_bug.cgi?id=802525#c28
Robert Milasan
https://bugzilla.novell.com/show_bug.cgi?id=802525
https://bugzilla.novell.com/show_bug.cgi?id=802525#c29
--- Comment #29 from Robert Milasan
https://bugzilla.novell.com/show_bug.cgi?id=802525
https://bugzilla.novell.com/show_bug.cgi?id=802525#c30
--- Comment #30 from Frederic Crozat
BTW, Frederic (sorry for writing you name the wrong way) how can we find out what was created in /var/run before it was binded to /run. Because I've checked dbus and you where right, checked cups and again the same, but the error still happens.
We need to move the bind mount to another directory to access the one underneath and check what is left there (maybe with mount --move but I'm not an expert here). Of course, a good test would be to wipe /var/run (on disk) before booting.. -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.
https://bugzilla.novell.com/show_bug.cgi?id=802525
https://bugzilla.novell.com/show_bug.cgi?id=802525#c31
--- Comment #31 from Bernhard Wiedemann
https://bugzilla.novell.com/show_bug.cgi?id=802525
https://bugzilla.novell.com/show_bug.cgi?id=802525#c32
--- Comment #32 from Robert Milasan
https://bugzilla.novell.com/show_bug.cgi?id=802525
https://bugzilla.novell.com/show_bug.cgi?id=802525#c33
--- Comment #33 from Hans Petter Jansson
https://bugzilla.novell.com/show_bug.cgi?id=802525
https://bugzilla.novell.com/show_bug.cgi?id=802525#c34
Stephan Kulow
https://bugzilla.novell.com/show_bug.cgi?id=802525
https://bugzilla.novell.com/show_bug.cgi?id=802525#c35
Hans Petter Jansson
am I correct that we can remove the ship stopper flag now? the bug is fixed as reported, right?
Confirmed -- with the dbus-1 packages in openSUSE:Factory that have the patch reverted, the problem no longer occurs for me. -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.
https://bugzilla.novell.com/show_bug.cgi?id=802525
https://bugzilla.novell.com/show_bug.cgi?id=802525#c36
--- Comment #36 from Hans Petter Jansson
https://bugzilla.novell.com/show_bug.cgi?id=802525
https://bugzilla.novell.com/show_bug.cgi?id=802525#c37
--- Comment #37 from Frederic Crozat
I can't say what an ideal fix for this would be, but if we could get the .socket file to refer to /var/run/ until D-Bus is restarted/the system is rebooted, and then changed that to /run/, that'd probably work. A symlink that gets replaced on startup would probably work too.
I'm not sure symlinks will play nice with sockets. You should shadow the system .socket by putting a fil in /run/systemd/system but I think this directory will be wiped out when you run systemctl daemon-reload (which is required for systemd to reload config files). -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.
https://bugzilla.novell.com/show_bug.cgi?id=802525
https://bugzilla.novell.com/show_bug.cgi?id=802525#c
Stephan Kulow
https://bugzilla.novell.com/show_bug.cgi?id=802525
https://bugzilla.novell.com/show_bug.cgi?id=802525#c38
--- Comment #38 from Hans Petter Jansson
I'm not sure symlinks will play nice with sockets. You should shadow the system .socket by putting a fil in /run/systemd/system but I think this directory will be wiped out when you run systemctl daemon-reload (which is required for systemd to reload config files).
Thanks! That got me on the right track. Experimentally, /run/systemd/system/dbus.socket will persist across systemctl daemon-reload. Combined with my libdbus patch to fall back to /var/run/dbus/system_bus_socket, this makes "zypper install rtkit" and dbus-send not hang. The dbus-1.spec file will need something like this in the %post section: %post # Temporarily override the socket path systemd sees, so the running D-Bus process won't be clobbered. /bin/mkdir -p /run/systemd/system /usr/bin/sed 's#ListenStream=/run/dbus/system_bus_socket#ListenStream=/var/run/dbus/system_bus_socket#' < /usr/lib/systemd/system/dbus.socket > /run/systemd/system/dbus.socket -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.
https://bugzilla.novell.com/show_bug.cgi?id=802525
https://bugzilla.novell.com/show_bug.cgi?id=802525#c39
--- Comment #39 from Hans Petter Jansson
https://bugzilla.novell.com/show_bug.cgi?id=802525
https://bugzilla.novell.com/show_bug.cgi?id=802525#c40
--- Comment #40 from Hans Petter Jansson
https://bugzilla.novell.com/show_bug.cgi?id=802525
https://bugzilla.novell.com/show_bug.cgi?id=802525#c41
--- Comment #41 from Frederic Crozat
Frederic, Robert: Is it worth making another try, or is it too late in the process? Should I submit it?
I'd say go for it, but Coolo might disagree. -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.
https://bugzilla.novell.com/show_bug.cgi?id=802525
https://bugzilla.novell.com/show_bug.cgi?id=802525#c42
Robert Milasan
https://bugzilla.novell.com/show_bug.cgi?id=802525
https://bugzilla.novell.com/show_bug.cgi?id=802525#c43
Hans Petter Jansson
https://bugzilla.novell.com/show_bug.cgi?id=802525
https://bugzilla.novell.com/show_bug.cgi?id=802525#c44
--- Comment #44 from Hans Petter Jansson
https://bugzilla.novell.com/show_bug.cgi?id=802525
https://bugzilla.novell.com/show_bug.cgi?id=802525#c
Hans Petter Jansson
https://bugzilla.novell.com/show_bug.cgi?id=802525
https://bugzilla.novell.com/show_bug.cgi?id=802525#c45
Hans Petter Jansson
https://bugzilla.novell.com/show_bug.cgi?id=802525
https://bugzilla.novell.com/show_bug.cgi?id=802525#c46
Stephan Kulow
https://bugzilla.novell.com/show_bug.cgi?id=802525
https://bugzilla.novell.com/show_bug.cgi?id=802525#c47
Robert Milasan
https://bugzilla.novell.com/show_bug.cgi?id=802525
https://bugzilla.novell.com/show_bug.cgi?id=802525#c48
--- Comment #48 from Hans Petter Jansson
https://bugzilla.novell.com/show_bug.cgi?id=802525
https://bugzilla.novell.com/show_bug.cgi?id=802525#c49
Frederic Crozat
https://bugzilla.novell.com/show_bug.cgi?id=802525
https://bugzilla.novell.com/show_bug.cgi?id=802525#c50
--- Comment #50 from Bernhard Wiedemann
https://bugzilla.novell.com/show_bug.cgi?id=802525
https://bugzilla.novell.com/show_bug.cgi?id=802525#c51
Robert Milasan
https://bugzilla.novell.com/show_bug.cgi?id=802525
https://bugzilla.novell.com/show_bug.cgi?id=802525#c52
--- Comment #52 from Dominique Leuenberger
https://bugzilla.novell.com/show_bug.cgi?id=802525
https://bugzilla.novell.com/show_bug.cgi?id=802525#c53
Hrvoje Senjan
The dbus-1.spec file will need something like this in the %post section:
%post # Temporarily override the socket path systemd sees, so the running D-Bus process won't be clobbered. /bin/mkdir -p /run/systemd/system /usr/bin/sed 's#ListenStream=/run/dbus/system_bus_socket#ListenStream=/var/run/dbus/system_bus_socket#' < /usr/lib/systemd/system/dbus.socket > /run/systemd/system/dbus.socket
This now creates similar situation, at least with current Factory. Try to install/upgrade systemd and dbus in the same run, and one then gets e.g. logind service, polkit, etc hang. Do we need this really in the %post now? Upgrades work correctly with the original ListenStream. -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.
https://bugzilla.novell.com/show_bug.cgi?id=802525
https://bugzilla.novell.com/show_bug.cgi?id=802525#c54
--- Comment #54 from Bernhard Wiedemann
https://bugzilla.novell.com/show_bug.cgi?id=802525
https://bugzilla.novell.com/show_bug.cgi?id=802525#c55
--- Comment #55 from Frederic Crozat
https://bugzilla.novell.com/show_bug.cgi?id=802525
https://bugzilla.novell.com/show_bug.cgi?id=802525#c56
--- Comment #56 from Hrvoje Senjan
I'm wondering if we should put hpj fallback patch, otherwise, we will never be able to migrate properly..
That may be true, however, that will also create hangs for everyone on > 12.3 -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.
https://bugzilla.novell.com/show_bug.cgi?id=802525
https://bugzilla.novell.com/show_bug.cgi?id=802525#c57
--- Comment #57 from Frederic Crozat
(In reply to comment #55)
I'm wondering if we should put hpj fallback patch, otherwise, we will never be able to migrate properly..
That may be true, however, that will also create hangs for everyone on > 12.3
hmm, no, the point was to use /run/dbus/.. and if it doesn't respond, fallback to /var/run/dbus/... -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.
https://bugzilla.novell.com/show_bug.cgi?id=802525
https://bugzilla.novell.com/show_bug.cgi?id=802525#c58
--- Comment #58 from Hrvoje Senjan
hmm, no, the point was to use /run/dbus/.. and if it doesn't respond, fallback to /var/run/dbus/...
Well the patch is already/still applied in Factory. Cheating in spec file with replacing ListenStream was removed recently, due to issue i mentioned -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.
https://bugzilla.novell.com/show_bug.cgi?id=802525
https://bugzilla.novell.com/show_bug.cgi?id=802525#c59
Frederic Crozat
https://bugzilla.novell.com/show_bug.cgi?id=802525
https://bugzilla.novell.com/show_bug.cgi?id=802525#c60
Hans Petter Jansson
https://bugzilla.novell.com/show_bug.cgi?id=802525
https://bugzilla.novell.com/show_bug.cgi?id=802525#c61
Hans Petter Jansson
https://bugzilla.novell.com/show_bug.cgi?id=802525
https://bugzilla.novell.com/show_bug.cgi?id=802525#c62
Hrvoje Senjan
Dup'ing from 12.3 to Factory, it looks like the rtkit upgrade is hanging again. dbus-daemon is back to listening on the socket in /var/run for some reason, but dbus-send is correctly trying to connect to the socket in /run.
Hrvoje: Are you seeing the same? Any idea what's causing it?
What i was seeing, for some time in O:F (but not since the ListenStream sed was removed from spec), was that when at least when both dbus and systemd packages where upgraded/installed, the whole system hanged (polkit, upower, etc - dead), no salvation with rcdbus, just restarting with SysRQ. Haven't checked, but also could be that it happened with dbus upgrades alone, not just in combination with systemd. Can't say what happens on 12.3 -> O:F at this point, but i trust all of you the hang has returned. But by just adding back the sed hack, we would have upgraders to O:F/13.1 not hang, and constant hangs for O:F/13.1 users each time when they would upgrade dbus (+ systemd).
Since systemd is not listening on the socket in /run on behalf of dbus-daemon either, the connect() call is hanging in dbus-send. I can probably make it time out the connect() call in addition to the post-connect bus registration...
Not sure is this a (pretty) solution, but maybe we can have a conditional %post, which would check existance of xyz (which would we need to ship as 12.3 update), and then execute the sed command? -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.
https://bugzilla.novell.com/show_bug.cgi?id=802525
https://bugzilla.novell.com/show_bug.cgi?id=802525#c63
Hans Petter Jansson
https://bugzilla.novell.com/show_bug.cgi?id=802525
https://bugzilla.novell.com/show_bug.cgi?id=802525#c64
Hans Petter Jansson
https://bugzilla.novell.com/show_bug.cgi?id=802525
https://bugzilla.novell.com/show_bug.cgi?id=802525#c65
Hrvoje Senjan
https://bugzilla.novell.com/show_bug.cgi?id=802525
https://bugzilla.novell.com/show_bug.cgi?id=802525#c66
Hans Petter Jansson
https://bugzilla.novell.com/show_bug.cgi?id=802525
https://bugzilla.novell.com/show_bug.cgi?id=802525#c67
--- Comment #67 from Hrvoje Senjan
Hrvoje: Any luck? :)
Sorry for delay, i'll test it asap - hopefully today. Though i can only test situation on factory, it would still need validation for 12.3 -> factory upgrade -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.
https://bugzilla.novell.com/show_bug.cgi?id=802525
https://bugzilla.novell.com/show_bug.cgi?id=802525#c68
Hrvoje Senjan
https://bugzilla.novell.com/show_bug.cgi?id=802525
https://bugzilla.novell.com/show_bug.cgi?id=802525#c69
--- Comment #69 from Hans Petter Jansson
https://bugzilla.novell.com/show_bug.cgi?id=802525
https://bugzilla.novell.com/show_bug.cgi?id=802525#c70
--- Comment #70 from Dirk Weber
https://bugzilla.novell.com/show_bug.cgi?id=802525
https://bugzilla.novell.com/show_bug.cgi?id=802525#c71
--- Comment #71 from Rich Coe
https://bugzilla.novell.com/show_bug.cgi?id=802525
https://bugzilla.novell.com/show_bug.cgi?id=802525#c72
--- Comment #72 from Rich Coe
https://bugzilla.novell.com/show_bug.cgi?id=802525
https://bugzilla.novell.com/show_bug.cgi?id=802525#c
Alberto Planas Dominguez
https://bugzilla.novell.com/show_bug.cgi?id=802525
https://bugzilla.novell.com/show_bug.cgi?id=802525#c73
--- Comment #73 from Bernhard Wiedemann
https://bugzilla.novell.com/show_bug.cgi?id=802525
https://bugzilla.novell.com/show_bug.cgi?id=802525#c74
--- Comment #74 from Hrvoje Senjan
https://bugzilla.novell.com/show_bug.cgi?id=802525
https://bugzilla.novell.com/show_bug.cgi?id=802525#c75
--- Comment #75 from Hans Petter Jansson
https://bugzilla.novell.com/show_bug.cgi?id=802525
https://bugzilla.novell.com/show_bug.cgi?id=802525#c76
Scott Reeves
https://bugzilla.novell.com/show_bug.cgi?id=802525
https://bugzilla.novell.com/show_bug.cgi?id=802525#c77
Hans Petter Jansson
With the latest dbus (and factory) i now get:
Sep 25 21:01:58 shumarija systemd[1]: Failed to open private bus connection: Failed to connect to socket /run/dbus/system_bus_socket: Transport endpoint is already connected
and basically unusuable system -> please revert (or fix ;-) ASAP!
How it worked 2 months ago, and now it doesn't, i have no idea...
Were you testing with the D-Bus from home:hpjansson:bnc802525/dbus-1 ? I haven't synced that branch with Factory for a while, so maybe it's just outdated? What did you do to trigger the issue? -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.
https://bugzilla.novell.com/show_bug.cgi?id=802525
https://bugzilla.novell.com/show_bug.cgi?id=802525#c78
Hrvoje Senjan
https://bugzilla.novell.com/show_bug.cgi?id=802525
https://bugzilla.novell.com/show_bug.cgi?id=802525#c79
--- Comment #79 from Hans Petter Jansson
https://bugzilla.novell.com/show_bug.cgi?id=802525
https://bugzilla.novell.com/show_bug.cgi?id=802525#c80
--- Comment #80 from Bernhard Wiedemann
https://bugzilla.novell.com/show_bug.cgi?id=802525
https://bugzilla.novell.com/show_bug.cgi?id=802525#c81
Marcus Meissner
https://bugzilla.novell.com/show_bug.cgi?id=802525
https://bugzilla.novell.com/show_bug.cgi?id=802525#c82
--- Comment #82 from Hrvoje Senjan
https://bugzilla.novell.com/show_bug.cgi?id=802525
https://bugzilla.novell.com/show_bug.cgi?id=802525#c83
Ancor Gonzalez Sosa
https://bugzilla.novell.com/show_bug.cgi?id=802525
https://bugzilla.novell.com/show_bug.cgi?id=802525#c84
--- Comment #84 from Bernhard Wiedemann
https://bugzilla.novell.com/show_bug.cgi?id=802525
https://bugzilla.novell.com/show_bug.cgi?id=802525#c85
Ancor Gonzalez Sosa
https://bugzilla.novell.com/show_bug.cgi?id=802525
https://bugzilla.novell.com/show_bug.cgi?id=802525#c86
--- Comment #86 from Hrvoje Senjan
That bug will hit everybody running 'zypper dup' to upgrade from 12.X to 13.1RC1.
It will happen until DBus update is published for 12.3. Or people can manually create /var/lib/old_run_path file -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.
https://bugzilla.novell.com/show_bug.cgi?id=802525
https://bugzilla.novell.com/show_bug.cgi?id=802525#c87
Ancor Gonzalez Sosa
https://bugzilla.novell.com/show_bug.cgi?id=802525
https://bugzilla.novell.com/show_bug.cgi?id=802525#c88
--- Comment #88 from Swamp Workflow Management
https://bugzilla.novell.com/show_bug.cgi?id=802525
https://bugzilla.novell.com/show_bug.cgi?id=802525#c89
--- Comment #89 from Klaus Kämpf
https://bugzilla.novell.com/show_bug.cgi?id=802525
https://bugzilla.novell.com/show_bug.cgi?id=802525#c90
--- Comment #90 from Axel Braun
https://bugzilla.novell.com/show_bug.cgi?id=802525
https://bugzilla.novell.com/show_bug.cgi?id=802525#c91
Ancor Gonzalez Sosa
https://bugzilla.novell.com/show_bug.cgi?id=802525
https://bugzilla.novell.com/show_bug.cgi?id=802525#c92
Hrvoje Senjan
https://bugzilla.novell.com/show_bug.cgi?id=802525
https://bugzilla.novell.com/show_bug.cgi?id=802525#c93
--- Comment #93 from Frederic Crozat
so with https://build.opensuse.org/request/show/234182 we will have this back. @Fridrich is this really wanted? also quite a few packages rely on DBus' socket in /run...
Yes, it is wanted: systemd has changed back dbus socket from /run to /var/run to follow the D-Bus specification per the book where /var/run is hardcoded. In the future, when we switch to kdbus, /var/run/ will still be used. Therefore, dbus should be an exception to the move to /run. -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.
https://bugzilla.novell.com/show_bug.cgi?id=802525
https://bugzilla.novell.com/show_bug.cgi?id=802525#c94
--- Comment #94 from Marcus Meissner
https://bugzilla.novell.com/show_bug.cgi?id=802525
https://bugzilla.novell.com/show_bug.cgi?id=802525#c95
--- Comment #95 from Robert Milasan
funny that this is coming from the very same crowd that mandated the /run move in the beginning
Yes, this is utterly stupid. Why have /run, when anyways we will use /var/run. Dumb! -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.
https://bugzilla.novell.com/show_bug.cgi?id=802525
https://bugzilla.novell.com/show_bug.cgi?id=802525#c96
--- Comment #96 from Stephan Kulow
https://bugzilla.novell.com/show_bug.cgi?id=802525
https://bugzilla.novell.com/show_bug.cgi?id=802525#c97
--- Comment #97 from Hrvoje Senjan
Yes, it is wanted: systemd has changed back dbus socket from /run to /var/run to follow the D-Bus specification per the book where /var/run is hardcoded.
but it is not hardcoded. systemd should allow @system_bus_default_address@ configure switch, and not guess where the location is! -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.
https://bugzilla.novell.com/show_bug.cgi?id=802525
https://bugzilla.novell.com/show_bug.cgi?id=802525#c98
--- Comment #98 from Stephan Kulow
https://bugzilla.novell.com/show_bug.cgi?id=802525
https://bugzilla.novell.com/show_bug.cgi?id=802525#c99
--- Comment #99 from Frederic Crozat
https://bugzilla.novell.com/show_bug.cgi?id=802525
https://bugzilla.novell.com/show_bug.cgi?id=802525#c100
--- Comment #100 from Stephan Kulow
https://bugzilla.novell.com/show_bug.cgi?id=802525
https://bugzilla.novell.com/show_bug.cgi?id=802525#c101
--- Comment #101 from Robert Milasan
participants (1)
-
bugzilla_noreply@novell.com