[Solved] LM 19.3 xfce: Startup application xiccd does not terminate on logoff

[karlchen]

Hi, folks.

Newly detected issue on 3 different LM 19.3 xfce systems:

xiccd Process does not exit on logout

Preface:

LM 19.3 introduces a new user startup application: xiccd.
Displayed as "xiccd (Applies color management profiles to your session)"

A completely new settings dialog to manage color profiles has been created. For most users this means out of the box support for color-managed printing (through cupsd) and scanning (through saned). For monitor profiles you will have to install an additional service like xiccd.

Problem:

Whereas during shutdown terminating xiccd does not seem to cause any slowdown or any other issue, the started xiccd process refuses to terminate, when you only log off the current user.
Consequences:
+ After you log in again, there will be 2 xiccd processes.
+ The old xiccd process from the previous user session occupies a complete CPU core.

Solution:

None known so far.

Workariund:

Kill the left over xiccd process from the previous session.

Regards,
Karl

[MrEen]

Hi Karl.

In Menu > Settings > Session and Startup > Applications Autostart you could call a script that kills xiccd using the trigger logout as a workaround.

[rene]

Symptom confirmed also here, with however the remark that xiccd was not in fact installed on this from 19.2 Xfce upgraded 19.3 Xfce system.

[MrEen]

Bug report here: https://bugs.launchpad.net/ubuntu/+sour ... ug/1845800

Looks like it's fixed in the newest version of xiccd, but Ubuntu is still stuck on a more than 2 years old version for Bionic through Eoan users.

There's an experimental PPA from the Xubuntu developers here that has the newer xiccd.

[karlchen]

Hi, MrEen.

Excellent search. Excellent result.
Now we will only have to wait for 2 more years, till xiccd 0.3.0-1 will be outdated enough in order to be offered in the official software repositories.
But, hey, this is not your fault.

Cheers,
Karl

[xenopeek]

Was xiccd installed for you by default on 19.3? I can't recall what I did on my 19.3 Xfce VM but I had to install xiccd myself.

Adding killall xiccd on logout in "Session and Startup" > "Application Autostart" as MrEen alluded to works for me. If you have multiple accounts also add it on switch user.

The xubuntu-dev/experimental PPA isn't useful as the package built for Eoan needs a newer version of libcolord2 than is on Bionic. Does somebody have a Xubuntu 19.10 VM lying around and can confirm it has the same issue with stock xiccd and upgrading to the PPA version fixes this issue?

I also tried finding xiccd alternatives as https://docs.xfce.org/xfce/xfce4-settings/4.14/color repeatedly implies there are, but I can't find any.

[karlchen]

Hi, xenopeek.

Yes, xiccd has been installed as part of the upgrade from LM 19.1 xfce to LM 19.3 xfce.
Below is the history which Synaptic wrote while doing the installation steps on behalf of Update Manager, which had invoked mint-release-upgrade, which in turn called Synaptic to do the work.
Anyway, here are the update steps:

Code: Select all

Commit Log for Sat Dec 28 17:13:37 2019


Die folgenden Pakete wurden entfernt:
xfce4-quicklauncher-plugin

Die folgenden Pakete wurden aktualisiert:
base-files (19.1.2) to 19.3.0
blueberry (1.2.5) to 1.3.3
catfish (1.4.4-1) to 1.4.10-1~18.04
cinnamon-desktop-data (4.0.1+tessa) to 4.4.1+tricia
desktop-file-utils (0.23+linuxmint5) to 0.23+linuxmint8
exo-utils (0.12.2-0ubuntu0.18.04.1) to 0.12.8-1~18.04
gdebi (0.9.5.7xmint8) to 0.9.5.7xmint9
gdebi-core (0.9.5.7xmint8) to 0.9.5.7xmint9
gir1.2-appindicator3-0.1 (12.10.1+18.04.20180322.1-0ubuntu1) to 12.10.1+18.04.20180322.1-1mint1+tricia
gir1.2-xapp-1.0 (1.4.6+tessa) to 1.6.8+tricia
gir1.2-xplayer-1.0 (2.0.2+tessa) to 2.2.3+tricia
libappindicator0.1-cil (12.10.1+18.04.20180322.1-0ubuntu1) to 12.10.1+18.04.20180322.1-1mint1+tricia
libappindicator1 (12.10.1+18.04.20180322.1-0ubuntu1) to 12.10.1+18.04.20180322.1-1mint1+tricia
libappindicator3-1 (12.10.1+18.04.20180322.1-0ubuntu1) to 12.10.1+18.04.20180322.1-1mint1+tricia
libcinnamon-desktop4 (4.0.1+tessa) to 4.4.1+tricia
libexo-1-0 (0.12.2-0ubuntu0.18.04.1) to 0.12.8-1~18.04
libexo-2-0 (0.12.2-0ubuntu0.18.04.1) to 0.12.8-1~18.04
libexo-common (0.12.2-0ubuntu0.18.04.1) to 0.12.8-1~18.04
libexo-helpers (0.12.2-0ubuntu0.18.04.1) to 0.12.8-1~18.04
libgarcon-1-0 (0.6.1-2linuxmint1) to 0.6.4-1~18.04mint1
libgarcon-common (0.6.1-2linuxmint1) to 0.6.4-1~18.04mint1
libtumbler-1-0 (0.2.1-0ubuntu1) to 0.2.7-2~18.04
libxapp1 (1.4.6+tessa) to 1.6.8+tricia
libxfce4panel-2.0-4 (4.12.2-1ubuntu1mint2) to 4.14.1-0ubuntu1~18.04mint1
libxfce4ui-1-0 (4.13.4-1ubuntu1) to 4.14.1-1ubuntu1~18.04
libxfce4ui-2-0 (4.13.4-1ubuntu1) to 4.14.1-1ubuntu1~18.04
libxfce4ui-common (4.13.4-1ubuntu1) to 4.14.1-1ubuntu1~18.04
libxfce4util-bin (4.12.1-3) to 4.14.0-1~18.04
libxfce4util-common (4.12.1-3) to 4.14.0-1~18.04
libxfce4util7 (4.12.1-3) to 4.14.0-1~18.04
libxplayer0 (2.0.2+tessa) to 2.2.3+tricia
libxreaderdocument3 (2.0.2+tessa) to 2.4.3+tricia
libxreaderview3 (2.0.2+tessa) to 2.4.3+tricia
lightdm-settings (1.2.5) to 1.3.2
menulibre (2.2.0-1) to 2.2.1-1~18.04
mint-artwork (1.1.9.1) to 1.3.4
mint-common (1.3.4) to 2.0.9
mint-info-xfce (2018.09.10) to 2019.11.25
mint-meta-codecs (2018.11.28) to 2019.12.28
mint-meta-core (2018.11.28) to 2019.12.28
mint-meta-xfce (2018.11.28) to 2019.12.28
mint-themes (1.7.8) to 1.8.3
mint-translations (2018.12.11) to 2019.12.11
mint-x-icons (1.5.1) to 1.5.3
mint-y-icons (1.3.3) to 1.3.7
mintbackup (2.3.5) to 2.3.8
mintdesktop (3.6.3) to 3.6.8
mintdrivers (1.4.1) to 1.4.4
mintinstall (7.9.7.1) to 8.0.3
mintlocale (1.5.1) to 1.5.3
mintreport (1.0.6) to 1.1.4
mintsources (1.8.4) to 1.9.1
mintstick (1.3.9) to 1.4.1
mintsystem (8.4.2) to 8.4.6
mintupdate (5.4.7) to 5.5.8
mintwelcome (2.3.7) to 2.4.1
mugshot (0.4.0-1) to 0.4.2-1~18.04
nvidia-prime-applet (1.0.7) to 1.0.8
onboard (1.4.1-2ubuntu1mint2) to 1.4.1-2ubuntu1mint3
onboard-common (1.4.1-2ubuntu1mint2) to 1.4.1-2ubuntu1mint3
pix (2.0.3+tessa) to 2.4.3+tricia
pix-data (2.0.3+tessa) to 2.4.3+tricia
pix-dbg (2.0.3+tessa) to 2.4.3+tricia
python3-xapp (1.4.0) to 1.8.1
slick-greeter (1.2.4+tessa) to 1.3.1+tricia
synaptic (0.84.3linuxmint1+tara) to 0.84.3linuxmint3+tricia
thunar (1.6.15-0ubuntu1) to 1.8.9-1~18.04.0
thunar-archive-plugin (0.3.1-4) to 0.4.0-2~18.04.1
thunar-data (1.6.15-0ubuntu1) to 1.8.9-1~18.04.0
thunar-media-tags-plugin (0.2.1-1) to 0.3.0-2~18.04
thunar-volman (0.8.1-2) to 0.9.5-1~18.04
timeshift (18.9.1.2+tessa) to 19.08.1.2+tricia
tumbler (0.2.1-0ubuntu1) to 0.2.7-2~18.04
tumbler-common (0.2.1-0ubuntu1) to 0.2.7-2~18.04
ubuntu-system-adjustments (2019.06.29) to 2019.12.09
xapps-common (1.4.6+tessa) to 1.6.8+tricia
xed (2.0.2+tessa) to 2.4.2+tricia
xed-common (2.0.2+tessa) to 2.4.2+tricia
xed-dbg (2.0.2+tessa) to 2.4.2+tricia
xfce4-appfinder (4.12.0-2ubuntu2) to 4.14.0-1~18.04
xfce4-cpufreq-plugin (1.1.3-1) to 1.2.1-1~18.04
xfce4-datetime-plugin (0.7.0-1ubuntu1) to 0.8.0-1~18.04
xfce4-dict (0.8.0-1) to 0.8.2-1~18.04
xfce4-mailwatch-plugin (1.2.0-2ubuntu2) to 1.2.0-3~18.04
xfce4-notifyd (0.4.2-0ubuntu2) to 0.4.4-0ubuntu1~18.04
xfce4-panel (4.12.2-1ubuntu1mint2) to 4.14.1-0ubuntu1~18.04mint1
xfce4-places-plugin (1.7.0-3) to 1.8.1-1~18.04
xfce4-power-manager (1.6.1-0ubuntu1mint1) to 1.6.5-2~18.04mint1
xfce4-power-manager-data (1.6.1-0ubuntu1mint1) to 1.6.5-2~18.04mint1
xfce4-power-manager-plugins (1.6.1-0ubuntu1mint1) to 1.6.5-2~18.04mint1
xfce4-pulseaudio-plugin (0.4.1-0ubuntu1mint1) to 0.4.2-1~18.04mint1
xfce4-screenshooter (1.8.2-2) to 1.9.6-1~18.04
xfce4-session (4.12.1-3ubuntu3) to 4.14.0-0ubuntu1~18.04
xfce4-settings (4.12.4-0ubuntu0.18.04.1) to 4.14.1-1ubuntu1~18.04
xfce4-systemload-plugin (1:1.2.1-0ubuntu1) to 1:1.2.3-1ubuntu1~18.04
xfce4-taskmanager (1.2.0-0ubuntu1) to 1.2.2-1~18.04
xfce4-time-out-plugin (1.0.2-0ubuntu1) to 1.0.2-0ubuntu2~18.04
xfce4-timer-plugin (1.6.0-1build1) to 1.7.0-1~18.04
xfce4-verve-plugin (1.1.0-1) to 2.0.0-1~18.04
xfce4-weather-plugin (0.8.11-0ubuntu0.18.04.1) to 0.10.0-1~18.04
xfce4-whiskermenu-plugin (2.3.0-0ppa1~bionic) to 2.3.3-1~18.04
xfconf (4.12.1-1) to 4.14.1-1~18.04
xfdesktop4 (4.12.3-4ubuntu2) to 4.14.1-1~18.04
xfdesktop4-data (4.12.3-4ubuntu2) to 4.14.1-1~18.04
xfwm4 (4.13.0-2~downgrade-4.12.5-1ubuntu0.18.04.1+tara) to 4.14.0-1~18.04
xplayer (2.0.2+tessa) to 2.2.3+tricia
xplayer-common (2.0.2+tessa) to 2.2.3+tricia
xplayer-dbg (2.0.2+tessa) to 2.2.3+tricia
xplayer-plugins (2.0.2+tessa) to 2.2.3+tricia
xreader (2.0.2+tessa) to 2.4.3+tricia
xreader-common (2.0.2+tessa) to 2.4.3+tricia
xreader-dbg (2.0.2+tessa) to 2.4.3+tricia
xviewer (2.0.2+tessa) to 2.4.2+tricia
xviewer-dbg (2.0.2+tessa) to 2.4.2+tricia

Die folgenden Pakete wurden installiert:
grub2-theme-mint (1.2.2)
libgarcon-gtk3-1-0 (0.6.4-1~18.04mint1)
libthunarx-3-0 (1.8.9-1~18.04.0)
libxfconf-0-3 (4.14.1-1~18.04)
libxpresent1 (1.0.0-2)
mint-backgrounds-tricia (1.1)
python3-parted (3.11.1-1ubuntu2)
xfce4-xapp-status-plugin (0.1.3+tricia)
xiccd (0.2.4-1)

xiccd was the last package to be added.

Cheers,
Karl
--
P.S.:
Same on the other 2 LM 19.1/2 xfce systems, upgraded to LM 19.3 xfce.

[smurphos]

Another way that should work is to edit /etc/systemd/logind.conf to add the line KillUserProcesses=yes. That should ensure that all user processes are ended on logout.

[karlchen]

Hi, smurphos.

Another way that should work is to edit /etc/systemd/logind.conf to add the line KillUserProcesses=yes. That should ensure that all user processes are ended on logout.

Excellent.
Enabling KillUserProcesses=yes indeed makes sure that the process xiccd gets terminated when the current user logs off. As a consequence, there will be no more left behind instances of xiccd hogging one CPU core per instance.

Cheers,
Karl
--
I'll mark this thread as [solved], because there is a way of preventing orphaned xiccd instances from hogging the CPU cores.
This will be good enough for most users. Waiting for Ubuntu to make available the bug-fixed xiccd 0.3.0-1 in their repos for Ubuntu 18.04 may take some more time or never happen.

[clem]

Karlchen,

Can you try an "apt remove xiccd"? Don't let it go through, I just want to see the output to understand what depends on it (i.e. why it's being added in the upgrade).

I can confirm this package isn't in Mint by default, in any releases.

Looking at the reports upstream it's not clear to me what the fix is... the devs just mentioned it was fixed in 0.3.

[karlchen]

Hello, Clem.

Sure I will check what would happen if xiccd got uninstalled.
Yet, I will be able to do so only tonight, i.e. some time after 18:00 CET, because for the next few hours I will be logged in on my Windows office machine.
By the way, xiccd was brought along by xfce 4.14.1, if I remember right, in order to communicate with colord.
At least, it was not present while the system was still on LM 19.2 xfce 4.12.3.
Might also be it was my love for the xfce4-goodies, which pulled it in as a side effect.

Cheers,
Karl

[xenopeek]

I can only find xiccd as an optional (recommends) dependency for xfce4-settings. This dependency is new as compared to xfce4-settings version of Linux Mint 19.2.

I guess it would be installed in an upgrade from 19.2 if "consider recommended packages as dependencies" is set in Synaptic? Can you check that config on your system also karlchen? It's in Settings > Preferences > General tab and then under the "Marking Changes" heading.

[gm10]

If you have multiple accounts also add it on switch user.

Considering switch user doesn't log the user out, why would you want to do that?

I guess it would be installed in an upgrade from 19.2 if "consider recommended packages as dependencies" is set in Synaptic?

Yep, that would happen (except for users of my PPA).

[karlchen]

"consider recommended packages as dependencies" is set in Synaptic?

Yes, this setting has been enabled on each and every Mint system here.

[clem]

Here's 0.3.0 compiled against our base. Let me know if it helps.

[rene]

Confirmed to solve the issue itself on 19.3 Xfce here (while again noting that the upgrade from 19.2 Xfce didn't pull xiccd in for me here, and also, that purging the repository-version of xiccd purges xiccd itself and nothing else).

[karlchen]

Good evening, Clem.

Can you try an "apt remove xiccd"?

Code: Select all

karl@unimatrix3:~$ LC_ALL=C sudo apt-get --dry-run remove xiccd
Reading package lists... Done
Building dependency tree       
Reading state information... Done
The following packages were automatically installed and are no longer required:
  libllvm7 libllvm7:i386 linux-headers-4.15.0-66 linux-headers-4.15.0-66-generic linux-headers-4.15.0-70
  linux-headers-4.15.0-70-generic linux-image-4.15.0-66-generic linux-image-4.15.0-70-generic linux-modules-4.15.0-66-generic
  linux-modules-4.15.0-70-generic linux-modules-extra-4.15.0-66-generic linux-modules-extra-4.15.0-70-generic
Use 'sudo apt autoremove' to remove them.
The following packages will be REMOVED:
  xiccd
0 upgraded, 0 newly installed, 1 to remove and 0 not upgraded.
Remv xiccd [0.3.0-0]

The only package to be removed would be xiccd itself.

Checking in Synaptic I can confirm xenopeek's statement that xfce4-settings pulls in xiccd as a recommended package.
It was really pulled in and installed here, because the setting APT::Install-Recommends "true"; was and is present on the system.

Here's 0.3.0 compiled against our base. Let me know if it helps.

Thank you for compiling the bug-fixed xiccd package.

• Disabled the systemd workaround KillUserProcesses=yes and rebooted. (Cf. above)
• Killed process xiccd 0.2.4-1.
• Installed xiccd 0.3.0 (xiccd_0.3.0-0_amd64.deb) and launched xiccd manually this time via <Alt><F2>.
• Logged out, logged back in. - Checked that only 1 instance of xiccd was running, started after login. (yes, precisely so)
• Repeated the previous steps several times. - No more left behind xiccd instance after logging back in again, only the newly started xiccd instance.
• Seems as if xiccd 0.3.0 really fixes the reported problem.

Cheers,
Karl

[clem]

Thanks, xiccd 0.3.0-0 is now in the repositories.

[Akadole1932]

Another way that should work is to edit /etc/systemd/logind.conf to add the line KillUserProcesses=yes. That should ensure that all user processes are ended on logout.

Should I remove the hash symbol before KillUserProcesses?

[Moem]

A hash symbol before a line generally means 'ignore this line'. So: yes.