Bugzilla – Bug 1142530
libICE6 >=1.0.10 blocks KDE3 and TDE sessions from starting
Last modified: 2019-11-19 04:17:04 UTC
libICE6 >1.0.9-4.7 blocks KDE3 and TDE sessions from starting
Mailing list threads:
Try to start KDE3 session after upgrade to libICE6-1.0.10-1.1:
There was an error setting up inter-process communications for KDE. The message
returned by the system was:
Could not read network connection list:
Please check that the "dcopserver" program is running.
Reverting to libICE6-1.0.9-4.7 on host gx27c via rpmrebuild on host gx280 restored access to a working KDE3 session.
It would be good if somebody could bisect this. Just 31 commits between 1.0.9 and 1.0.10.
(about 5 steps only)
I filed this upstream since it also affects TDE on Archlinux.
(In reply to Felix Miata from comment #4)
> I filed this upstream since it also affects TDE on Archlinux.
Thanks. Looks like the culprit is
Author: Allison Lortie <email@example.com>
Date: Tue Jun 14 16:09:46 2016 -0400
authutil: support $XDG_RUNTIME_DIR/ICEauthority
If we find that $XDG_RUNTIME_DIR is set (and $ICEAUTHORITY is not), then
the ICEauthority file is stored in the XDG_RUNTIME_DIR instead of the
home directory, and without a leading dot.
Signed-off-by: Alan Coopersmith <firstname.lastname@example.org>
(In reply to Stefan Dirsch from comment #5)
> commit b484311c929a1b64966d89da92fafce7263006e1
https://cgit.freedesktop.org/xorg/lib/libICE/commit/?id=b484311c92 referenced by TDE bug.
I just updated TW20190614 to TW20190723 with libICE6-1.0.9-4.7 to libICE6-1.0.10-1.1 on host fi965r without remembering to first lock 1.0.09-4.7, and this bug did not present either via KDM3 or startx. :-O
Earlier in the day it did present on another 64bit host (gx320?) upgraded from TW20190514(?) to TW20190721 with libICE6-1.0.9-4.5 locked. :-S
On TW20190607 host t2240 with libICE6-1.0.9-4.6 I locked it before upgrading to TW20190726. Rebooting resulted in blocked KDE3 session, for same reason. so I unlocked libICE6, upgraded it to 1.0.10, restarted KDM, and was immediately able to log into a KDE3 session normally, as well as on subsequent boot.
So what's the remaining issue here? Our users usually don't block updates, right? Apart from KDE3/TDE not being shipped, let alone being supported by TW anyway ...
Ok. So seems nothing remains here. Otherwise please feel free to reopen (with a good reason!). ;-)
I just zypper dup'd 64bit host gx620 from TW20190716 to TW20191112, which upgraded libICE6-1.0.9-4.8 to libICE6-1.0.10-1.1, which in turn resurrected this bug in TDE. I kept 1.0.9-4.7, which I reinstalled to work around this.
So is there $XDG_RUNTIME_DIR or $ICEAUTHORITY set during desktop start? Does $XDG_RUNTIME_DIR/ICEauthority or $HOME/.ICEauthority exist?
My reading of the corresponding TDE bug http://bugs.pearsoncomputing.net/show_bug.cgi?id=3027 suggests it may be that a TDE patch is required.
Successfully booted into a TDE session because older libICE is installed:
# echo $HOSTNAME
# rpm -qa | grep libICE
# echo $XDG_RUNTIME_DIR
# echo $ICEAUTHORITY
# echo $XDG_RUNTIME_DIR/IDEauthority
# echo $HOME/.ICEauthority
Could well be. I suggest to use the workaround referenced in http://bugs.pearsoncomputing.net/show_bug.cgi?id=3027#c2
I believe the issue is in DCOP not using libice, but hardcode ICEAUTHORITY file instead.
explains how to fix this using libice. I wasn't able to find dcop, let alone the sources for it. Probably this died together with KDE3.