Bug #1442050 “(colord:832): Cd-WARNING **: failed to get session...” : Bugs : colord package : Ubuntu

Revision history for this message

dino99 (9d9) wrote on 2015-04-09:

#1

CurrentDmesg.txt Edit (112.0 KiB, text/plain; charset="utf-8")
Dependencies.txt Edit (3.0 KiB, text/plain; charset="utf-8")
JournalErrors.txt Edit (136.7 KiB, text/plain; charset="utf-8")
Lspci.txt Edit (13.6 KiB, text/plain; charset="utf-8")
ProcCpuinfo.txt Edit (3.2 KiB, text/plain; charset="utf-8")
ProcEnviron.txt Edit (328 bytes, text/plain; charset="utf-8")
ProcInterrupts.txt Edit (2.3 KiB, text/plain; charset="utf-8")
ProcModules.txt Edit (4.0 KiB, text/plain; charset="utf-8")
SystemdDelta.txt Edit (894 bytes, text/plain; charset="utf-8")
UdevDb.txt Edit (126.2 KiB, text/plain; charset="utf-8")
UdevLog.txt Edit (255.0 KiB, text/plain; charset="utf-8")

summary:	- colord[832]: (colord:832): Cd-WARNING : failed to get session [pid - 690]: Unknown error -2 + (colord:832): Cd-WARNING : failed to get session [pid 690]: Unknown + error -2
description:	updated

Martin Pitt (pitti) on 2015-04-09

affects:

systemd (Ubuntu) → colord (Ubuntu)

Revision history for this message

Launchpad Janitor (janitor) wrote on 2015-05-06:

#2

Status changed to 'Confirmed' because the bug affects multiple users.

Changed in colord (Ubuntu):
status:	New → Confirmed

Alberto Salvia Novella (es20490446e) on 2015-05-12

Changed in colord (Ubuntu):
importance:	Undecided → High

Revision history for this message

SoftCoder (mark-vejvoda) wrote on 2016-02-05:

#3

I keep seeing this error in 16.04 via ossec, and continuously:

OSSEC HIDS Notification.
2016 Feb 04 20:30:02

Received From: softcoder-linux->/var/log/syslog
Rule: 1002 fired (level 2) -> "Unknown problem somewhere in the system."
Portion of the log(s):

Feb 4 20:30:02 softcoder-linux colord[1096]: (colord:1096): Cd-WARNING **: failed to get session [pid 26812]: No such device or address

--END OF NOTIFICATION

Revision history for this message

SoftCoder (mark-vejvoda) wrote on 2016-02-12:

#4

Latest updates in 16.04 today and no more errors, so this patch must have been pushed out.

Revision history for this message

dino99 (9d9) wrote on 2016-02-12:

#5

Still get that error on xenial 64 bits logged with gnome-shell

colord[834]: (colord:834): Cd-WARNING **: failed to get session [pid 2855]: No such device or address

tags:

added: xenial

Revision history for this message

SoftCoder (mark-vejvoda) wrote on 2016-02-12:

#6

And now they came back again after todays udpates

Revision history for this message

SoftCoder (mark-vejvoda) wrote on 2016-02-13:

#7

And as of today no more errors after today's updates

Revision history for this message

dino99 (9d9) wrote on 2016-03-03:

#8

This problem persist; maybe xenial should upgrade to the newest version:

Version Date
1.3.1 2015-11-27

https://www.freedesktop.org/software/colord/download.html

but Debian still have not packaged it yet.

Revision history for this message

dino99 (9d9) wrote on 2016-03-03:

#9

The 1.3.1 changelog:

Version 1.3.1
~~~~~~~~~~~~~
Released: 2015-11-27

New Features:
- Add a sensor error for missing dark calibration (Richard Hughes)
- Add g_autoptr() defines for cd_color* (Richard Hughes)
- Add get-spectral-reading command to colormgr (Richard Hughes)
- Add the GetSpectrum() sensor D-Bus method (Richard Hughes)
- Allow returning spectral readings from the Spark sensor (Richard Hughes)
- libcolord: Add an error enum for missing irradiance calibration (Richard Hughes)
- libcolord: Add a spectral sensor capability (Richard Hughes)
- libcolord: Add cd_sensor_get_spectrum() (Richard Hughes)
- libcolord: Add cd_spectrum_get_value_max() (Richard Hughes)
- libcolord: Add cd_spectrum_limit_min() (Richard Hughes)
- libcolord: Add cd_spectrum_planckian_new_full() (Richard Hughes)
- libcolord: Add cd_spectrum_resample() (Richard Hughes)
- libcolord: Add cd_spectrum_set_wavelength_cal() (Richard Hughes)
- libcolord: Add cd_spectrum_subtract() (Richard Hughes)
- libcolord: Add cd_spectrum_to_string() (Richard Hughes)

Bugfixes:
- Add a systemd user service corresponding to the D-Bus session service (Simon McVittie)
- Add a tmpfiles.d snippet to fix stateless systems (Tobias Hunger)
- data: Build Rec709 correctly (Richard Hughes)
- Ignore the ColorHug+ in DFU mode (Richard Hughes)
- Install the tmpfiles.d snippet in the right place (Richard Hughes)
- Reset the sensor back to idle after each action (Richard Hughes)
- libcolord: Fix a tiny memory leak in cd_icc_get_tag_data() (Richard Hughes)
- libcolord: Fix saving non-normalized spectra (Richard Hughes)
- libcolord: Make cd_spectrum_free() NULL-safe (Richard Hughes)
- libcolord: Return an error when we fail to estimate the gamma value (Richard Hughes)

https://github.com/hughsie/colord/blob/master/NEWS

Revision history for this message

dino99 (9d9) wrote on 2016-03-03:

#10

How to compile it:

Compiling for Linux
Ensure the following packages are installed:

dbus-devel
docbook-utils
gettext
glib2-devel
gobject-introspection-devel
gtk-doc
intltool
lcms2-devel
libgudev1-devel
libgusb-devel
polkit-devel
sqlite-devel
systemd-devel
vala-tools

Then just do ./autogen.sh && make

Revision history for this message

Michael Heuberger (michael.heuberger) wrote on 2016-03-03:

#11

Can I apt-get upgrade this anytime soon instead?

Revision history for this message

jowfdoijdfdwfwdf (dsfkljo322332) wrote on 2016-05-15:

#12

Still getting this erro in Ubuntu 16.04 LTS 4.4.0-22-generic

May 15 15:47:27 hostname systemd[1]: Started CUPS Scheduler.
May 15 15:47:27 hostname colord[1053]: (colord:1053): Cd-WARNING *
*: failed to get session [pid 21870]: No such device or address

Revision history for this message

SoftCoder (mark-vejvoda) wrote on 2016-05-21:

#13

Same here I still get this (and continue getting it for months now, both before and after release), thought it would be fixed by now I have all latest updates.

Revision history for this message

Stéphane Charette (stephanecharette) wrote on 2016-07-02:

#14

Also on 64-bit 16.04. I'm up-to-date with all the fixes, running 4.4.0-28-generic #47-Ubuntu. Like clockwork, every 5 minutes I get 2 of these:

> grep colord /var/log/syslog
...
Jul 2 12:50:14 loup colord[1341]: (colord:1341): Cd-WARNING **: failed to get session [pid 30207]: No such device or address
Jul 2 12:50:14 loup colord[1341]: (colord:1341): Cd-WARNING **: failed to get session [pid 30207]: No such device or address
Jul 2 12:55:13 loup colord[1341]: (colord:1341): Cd-WARNING **: failed to get session [pid 30976]: No such device or address
Jul 2 12:55:13 loup colord[1341]: (colord:1341): Cd-WARNING **: failed to get session [pid 30976]: No such device or address

Reading through this bug report, I still don't understand why this is happening, or what I can do to fix it.

Revision history for this message

dynaguy (dynaguy) wrote on 2016-08-08:

#15

I got this on my newly built 64-bit Ubuntu 16.04 as well:
Aug 8 06:25:32 tau systemd[1]: Started CUPS Scheduler.
Aug 8 06:25:32 tau colord[2924]: (colord:2924): Cd-WARNING **: failed to get session [pid 12313]: No such device or address
Aug 8 06:25:32 tau colord[2924]: (colord:2924): Cd-WARNING **: failed to get session [pid 12313]: No such device or address
Aug 8 06:38:33 tau systemd[1]: Started CUPS Scheduler.
Aug 8 06:38:33 tau colord[2924]: (colord:2924): Cd-WARNING **: failed to get session [pid 12325]: No such device or address
Aug 8 06:38:33 tau colord[2924]: (colord:2924): Cd-WARNING **: failed to get session [pid 12325]: No such device or address
Aug 8 06:51:33 tau systemd[1]: Started CUPS Scheduler.
Aug 8 06:51:34 tau colord[2924]: (colord:2924): Cd-WARNING **: failed to get session [pid 12337]: No such device or address
Aug 8 06:51:34 tau colord[2924]: (colord:2924): Cd-WARNING **: failed to get session [pid 12337]: No such device or address
Aug 8 07:04:34 tau systemd[1]: Started CUPS Scheduler.
Aug 8 07:04:34 tau colord[2924]: (colord:2924): Cd-WARNING **: failed to get session [pid 12349]: No such device or address
Aug 8 07:04:34 tau colord[2924]: (colord:2924): Cd-WARNING **: failed to get session [pid 12349]: No such device or address
Aug 8 07:17:01 tau CRON[12361]: (root) CMD ( cd / && run-parts --report /etc/cron.hourly)
Aug 8 07:17:35 tau systemd[1]: Started CUPS Scheduler.
Aug 8 07:17:35 tau colord[2924]: (colord:2924): Cd-WARNING **: failed to get session [pid 12364]: No such device or address
Aug 8 07:17:35 tau colord[2924]: (colord:2924): Cd-WARNING **: failed to get session [pid 12364]: No such device or address

Revision history for this message

chris pollock (cpollock) wrote on 2016-08-13:

#16

Download full text (4.7 KiB)

I'm also seeing these same errors on my 16.04.1LTS 64bit install with kernel 4.4.0-34-generic #53-Ubuntu SMP

Aug 13 07:35:12 localhost colord[2417]: (colord:2417): Cd-WARNING **: failed to get session [pid 25642]: No such device or address
Aug 13 07:41:15 localhost colord[2417]: (colord:2417): Cd-WARNING **: failed to get session [pid 25880]: No such device or address
Aug 13 07:41:15 localhost colord[2417]: (colord:2417): Cd-WARNING **: failed to get session [pid 25880]: No such device or address
Aug 13 08:04:40 localhost colord[2417]: (colord:2417): Cd-WARNING **: failed to get session [pid 27636]: No such device or address
Aug 13 08:04:40 localhost colord[2417]: (colord:2417): Cd-WARNING **: failed to get session [pid 27636]: No such device or address
Aug 13 08:10:42 localhost colord[2417]: (colord:2417): Cd-WARNING **: failed to get session [pid 27919]: No such device or address
Aug 13 08:10:42 localhost colord[2417]: (colord:2417): Cd-WARNING **: failed to get session [pid 27919]: No such device or address
Aug 13 08:13:26 localhost colord-sane: io/hpmud/musb.c 2095: Invalid usb_open: Permission denied
Aug 13 08:13:26 localhost colord-sane: io/hpmud/pp.c 627: unable to read device-id ret=-1
Aug 13 08:16:43 localhost colord[2417]: (colord:2417): Cd-WARNING **: failed to get session [pid 28182]: No such device or address
Aug 13 08:16:43 localhost colord[2417]: (colord:2417): Cd-WARNING **: failed to get session [pid 28182]: No such device or address
Aug 13 09:03:00 localhost colord[2417]: (colord:2417): Cd-WARNING **: failed to get session [pid 30397]: No such device or address
Aug 13 09:03:01 localhost colord[2417]: (colord:2417): Cd-WARNING **: failed to get session [pid 30397]: No such device or address
Aug 13 10:01:20 localhost colord[2417]: (colord:2417): Cd-WARNING **: failed to get session [pid 1284]: No such device or address
Aug 13 10:01:21 localhost colord[2417]: (colord:2417): Cd-WARNING **: failed to get session [pid 1284]: No such device or address
Aug 13 10:07:22 localhost colord[2417]: (colord:2417): Cd-WARNING **: failed to get session [pid 1514]: No such device or address
Aug 13 10:07:22 localhost colord[2417]: (colord:2417): Cd-WARNING **: failed to get session [pid 1514]: No such device or address
Aug 13 10:13:23 localhost colord[2417]: (colord:2417): Cd-WARNING **: failed to get session [pid 1760]: No such device or address
Aug 13 10:13:23 localhost colord[2417]: (colord:2417): Cd-WARNING **: failed to get session [pid 1760]: No such device or address
Aug 13 10:19:25 localhost colord[2417]: (colord:2417): Cd-WARNING **: failed to get session [pid 2003]: No such device or address
Aug 13 10:19:25 localhost colord[2417]: (colord:2417): Cd-WARNING **: failed to get session [pid 2003]: No such device or address
Aug 13 10:25:26 localhost colord[2417]: (colord:2417): Cd-WARNING **: failed to get session [pid 2264]: No such device or address
Aug 13 10:25:26 localhost colord[2417]: (colord:2417): Cd-WARNING **: failed to get session [pid 2264]: No such device or address
Aug 13 10:59:38 localhost colord[2417]: (colord:2417): Cd-WARNING **: failed to get session [pid 3780]: No such device or address
Aug 13 10:59:38 localhost colord...

I'm also seeing these same errors on my 16.04.1LTS 64bit install with kernel 4.4.0-34-generic #53-Ubuntu SMP

Aug 13 07:35:12 localhost colord[2417]: (colord:2417): Cd-WARNING **: failed to get session [pid 25642]: No such device or address
Aug 13 07:41:15 localhost colord[2417]: (colord:2417): Cd-WARNING **: failed to get session [pid 25880]: No such device or address
Aug 13 07:41:15 localhost colord[2417]: (colord:2417): Cd-WARNING **: failed to get session [pid 25880]: No such device or address
Aug 13 08:04:40 localhost colord[2417]: (colord:2417): Cd-WARNING **: failed to get session [pid 27636]: No such device or address
Aug 13 08:04:40 localhost colord[2417]: (colord:2417): Cd-WARNING **: failed to get session [pid 27636]: No such device or address
Aug 13 08:10:42 localhost colord[2417]: (colord:2417): Cd-WARNING **: failed to get session [pid 27919]: No such device or address
Aug 13 08:10:42 localhost colord[2417]: (colord:2417): Cd-WARNING **: failed to get session [pid 27919]: No such device or address
Aug 13 08:13:26 localhost colord-sane: io/hpmud/musb.c 2095: Invalid usb_open: Permission denied
Aug 13 08:13:26 localhost colord-sane: io/hpmud/pp.c 627: unable to read device-id ret=-1
Aug 13 08:16:43 localhost colord[2417]: (colord:2417): Cd-WARNING **: failed to get session [pid 28182]: No such device or address
Aug 13 08:16:43 localhost colord[2417]: (colord:2417): Cd-WARNING **: failed to get session [pid 28182]: No such device or address
Aug 13 09:03:00 localhost colord[2417]: (colord:2417): Cd-WARNING **: failed to get session [pid 30397]: No such device or address
Aug 13 09:03:01 localhost colord[2417]: (colord:2417): Cd-WARNING **: failed to get session [pid 30397]: No such device or address
Aug 13 10:01:20 localhost colord[2417]: (colord:2417): Cd-WARNING **: failed to get session [pid 1284]: No such device or address
Aug 13 10:01:21 localhost colord[2417]: (colord:2417): Cd-WARNING **: failed to get session [pid 1284]: No such device or address
Aug 13 10:07:22 localhost colord[2417]: (colord:2417): Cd-WARNING **: failed to get session [pid 1514]: No such device or address
Aug 13 10:07:22 localhost colord[2417]: (colord:2417): Cd-WARNING **: failed to get session [pid 1514]: No such device or address
Aug 13 10:13:23 localhost colord[2417]: (colord:2417): Cd-WARNING **: failed to get session [pid 1760]: No such device or address
Aug 13 10:13:23 localhost colord[2417]: (colord:2417): Cd-WARNING **: failed to get session [pid 1760]: No such device or address
Aug 13 10:19:25 localhost colord[2417]: (colord:2417): Cd-WARNING **: failed to get session [pid 2003]: No such device or address
Aug 13 10:19:25 localhost colord[2417]: (colord:2417): Cd-WARNING **: failed to get session [pid 2003]: No such device or address
Aug 13 10:25:26 localhost colord[2417]: (colord:2417): Cd-WARNING **: failed to get session [pid 2264]: No such device or address
Aug 13 10:25:26 localhost colord[2417]: (colord:2417): Cd-WARNING **: failed to get session [pid 2264]: No such device or address
Aug 13 10:59:38 localhost colord[2417]: (colord:2417): Cd-WARNING **: failed to get session [pid 3780]: No such device or address
Aug 13 10:59:38 localhost colord[2417]: (colord:2417): Cd-WARNING **: failed to get session [pid 3780]: No such device or address
Aug 13 11:05:39 localhost colord[2417]: (colord:2417): Cd-WARNING **: failed to get session [pid 4042]: No such device or address
Aug 13 11:05:39 localhost colord[2417]: (colord:2417): Cd-WARNING **: failed to get session [pid 4042]: No such device or address
Aug 13 11:11:42 localhost colord[2417]: (colord:2417): Cd-WARNING **: failed to get session [pid 4353]: No such device or address
Aug 13 11:11:42 localhost colord[2417]: (colord:2417): Cd-WARNING **: failed to get session [pid 4353]: No such device or address
Aug 13 11:17:45 localhost colord[2417]: (colord:2417): Cd-WARNING **: failed to get session [pid 10259]: No such device or address
Aug 13 11:17:45 localhost colord[2417]: (colord:2417): Cd-WARNING **: failed to get session [pid 10259]: No such device or address
Aug 13 11:23:49 localhost colord[2417]: (colord:2417): Cd-WARNING **: failed to get session [pid 10586]: No such device or address
Aug 13 11:23:49 localhost colord[2417]: (colord:2417): Cd-WARNING **: failed to get session [pid 10586]: No such device or address

Does this also fit into this bug or is it another bug?

Aug 13 11:17:44 localhost gnome-session[18660]: (gnome-settings-daemon:18691): color-plugin-WARNING **: failed to connect to device: Failed to connect to missing device /org/freedesktop/ColorManager/devices/cups_HP_LaserJet_1020
Aug 13 11:17:44 localhost gnome-session[18660]: (gnome-settings-daemon:18691): color-plugin-WARNING **: failed to connect to device: Failed to connect to missing device /org/freedesktop/ColorManager/devices/cups_PDF

Revision history for this message

prof2004 (jdokupil) wrote on 2016-08-29:

#17

I am running ubuntu 16.04.1 LTS, all updates applied until today,
and have this issue as well.

Revision history for this message

D Tangman (dgtangman) wrote on 2016-10-14:

#18

Same problem - 16.04.1 LTS fully updated. Two copies of this message logged about every 13 minutes.

Revision history for this message

Not Martin Wimpress (not-martinwimpress) wrote on 2016-10-19:

#19

Regarding: "Aug 8 06:38:33 tau systemd[1]: Started CUPS Scheduler.
Aug 8 06:38:33 tau colord[2924]: (colord:2924): Cd-WARNING **: failed to get session [pid 12325]: No such device or address"

This bug is successfully resolved by removing "samba" and "samba-common" in synaptic. Apparently colord has severe issues with printer sharing when the device is not longer available (possibly by default gufw rules.)

information type:	Public → Public Security
information type:	Public Security → Public

Revision history for this message

chris pollock (cpollock) wrote on 2016-10-19:

#20

Sorry, but I tried your fix last night and the issue is still there. FWIW samba wasn't installed but samba-common was so using synaptic I removed it. Syslog output from this morning

Oct 19 08:57:02 localhost colord[1215]: (colord:1215): Cd-WARNING **: failed to get session [pid 10168]: No such device or address
Oct 19 08:57:02 localhost colord[1215]: (colord:1215): Cd-WARNING **: failed to get session [pid 10168]: No such device or address

Revision history for this message

Not Martin Wimpress (not-martinwimpress) wrote on 2016-10-19:

#21

I was referring to the cups scheduler. You might have issues with applications (or system applications as in the case with samba) trying to perpetually connect to your devices' embedded colour profiles and fails spectacularly when said profile no longer is accessible.

Revision history for this message

Not Martin Wimpress (not-martinwimpress) wrote on 2016-10-19:

#22

Btw @cpollock, I noticed you have a 1020 printer. HP uses a convoluted method to ensure you accept their license agreement to install their proprietary driver for this particular printer. If you haven't already done so by first installing the hplip gui and then manually running the hp setup, then go ahead and do a "sudo apt-get install hplip-gui", turn on the printer, then "delete" the printer listed in your list of installed printers, then do a "hp-setup", accept the license agreement, follow the instructions to complete installation, reboot, and now you're free to uninstall "hplip-gui" if you want. (Just don't also uninstall "hplip".)

Revision history for this message

chris pollock (cpollock) wrote on 2016-10-19:

#23

I don't use HPLIP -

Oct 19 14:31:12 localhost foo2zjs-wrapper: foo2zjs-wrapper -z1 -P -L0 -r1200x600 -p1 -T3 -m1 -s7 -n1
Oct 19 14:31:12 localhost foo2zjs-wrapper: gs -sPAPERSIZE=letter -g10200x6600 -r1200x600 -sDEVICE=pbmraw -dCOLORSCREEN -dMaxBitmap=500000000
Oct 19 14:31:12 localhost foo2zjs-wrapper: foo2zjs -r1200x600 -g10200x6600 -p1 -m1 -n1 -d1 -s7 -z1 -u 192x96 -l 192x96 -L 0 -T3 -P

Revision history for this message

Edward Donovan (edward.donovan) wrote on 2016-11-07:

#24

This is happening on a machine I just upgraded to 16.10. AFAICT, from looking back at the logs, it only started happening, regularly, after this upgrade. <shrug> :)

Only comes about every three hours here. Just wanted to confirm it seems to exist in the latest release. Thanks.

Revision history for this message

Not Martin Wimpress (not-martinwimpress) wrote on 2016-11-07:

#25

Btw, for those of you with the cups scheduler messages as well and still want to share with samba shares, you can disable just printer sharing and that will also effectively get rid of these messages as well. The guide to do that is here: https://forums.linuxmint.com/viewtopic.php?p=1231018#p1231018

Be sure to reboot.

Revision history for this message

chris pollock (cpollock) wrote on 2016-11-07:

#26

And if one doesn't have Samba installed?

Revision history for this message

Not Martin Wimpress (not-martinwimpress) wrote on 2016-11-07:

#27

@cpollock, I don't know your situation specifically so I would be speculating at best. But, if I were in your position I might do the following (but only do these steps at your own risk and have backups of your data elsewhere):

<risk>
1. delete any and all listed printers in your printer manager.
2. purge the foo2zjs drivers (I'm not familiar with the "correct" way of doing this so ask someone else.)
3. ensure hplip is fully-purged from your system by doing something like a "sudo apt purge hplip hplip-data"
4. now, install hplip and use hp's own drivers as explained in #22. Something curious from your log: hpmud is a component of hplip so perhaps it was installed at one time and wasn't properly purged before you installed the foo2zjs drivers and now colord is complaining that it can't see your 1020's color profile because foo2zjs isn't allowing it (pure speculation again.)
5. If those steps don't solve it, then perhaps purging and re-installing cups and then re-doing the steps over again might.
</risk>

Good luck.

Revision history for this message

Thomas Mayer (thomas303) wrote on 2017-01-31:

#28

I get this message in a row with cups messages:

Jan 31 07:35:09 lat61 systemd[1]: Stopping Make remote CUPS printers available locally...
Jan 31 07:35:09 lat61 systemd[1]: Stopped Make remote CUPS printers available locally.
Jan 31 07:35:09 lat61 systemd[1]: Stopping CUPS Scheduler...
Jan 31 07:35:09 lat61 systemd[1]: Stopped CUPS Scheduler.
Jan 31 07:35:09 lat61 systemd[1]: Started CUPS Scheduler.
Jan 31 07:35:09 lat61 systemd[1]: Started Make remote CUPS printers available locally.
Jan 31 07:35:09 lat61 colord[1368]: (colord:1368): Cd-WARNING **: failed to get session [pid 24360]: Kein passendes Gerät bzw. keine passende Adresse gefunden

Note that I have a Kyocera FS-1020D printer. Which is _not_ from HP.

Revision history for this message

Thomas Mayer (thomas303) wrote on 2017-01-31:

#29

Im on xenial 16.04, Kernel 4.4.0-59-generic. Still get this message.

Revision history for this message

Peter Draksler (draksler) wrote on 2017-02-03:

#30

Seeing the same on a fresh (as of last week) Xubuntu 16.04 install (4.4.0-62-generic) with all the latest updates;

Feb 3 14:07:17 vader systemd[1]: Started CUPS Scheduler.
Feb 3 14:07:17 vader colord[1453]: (colord:1453): Cd-WARNING **: failed to get session [pid 6191]: No such device or address
Feb 3 14:07:17 vader colord[1453]: (colord:1453): Cd-WARNING **: failed to get session [pid 6191]: No such device or address

Revision history for this message

jhansonxi (jhansonxi) wrote on 2017-02-22:

#31

Possibly related Debian bugs:
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=750533
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=813334

Revision history for this message

Josep Pujadas-Jubany (jpujades) wrote on 2017-07-30:

#32

Lubuntu 16.04 LTS 64 bit (up-to-date)

The service seems to run, but I've got errors...

sudo service colord status
● colord.service - Manage, Install and Generate Color Profiles
   Loaded: loaded (/lib/systemd/system/colord.service; static; vendor preset: enabled)
   Active: active (running) since dg 2017-07-30 08:34:17 CEST; 2h 13min ago
Main PID: 857 (colord)
   CGroup: /system.slice/colord.service
           └─857 /usr/lib/colord/colord

jul 30 08:34:16 pj01-lubuntu systemd[1]: Starting Manage, Install and Generate Color Profiles...
jul 30 08:34:17 pj01-lubuntu systemd[1]: Started Manage, Install and Generate Color Profiles.
jul 30 08:34:17 pj01-lubuntu colord[857]: (colord:857): Cd-WARNING **: failed to get session [pid 749]: No such device or address
jul 30 08:34:17 pj01-lubuntu colord[857]: (colord:857): Cd-WARNING **: failed to get session [pid 749]: No such device or address
jul 30 08:34:18 pj01-lubuntu colord[857]: (colord:857): Cd-WARNING **: failed to get session [pid 877]: No such device or address
jul 30 08:39:16 pj01-lubuntu colord[857]: (colord:857): Cd-WARNING **: failed to get session [pid 3152]: No such device or address
jul 30 08:39:16 pj01-lubuntu colord[857]: (colord:857): Cd-WARNING **: failed to get session [pid 3152]: No such device or address

Revision history for this message

paz (mozit) wrote on 2017-07-31:

#33

still a problem here:
Ubuntu 17.04.1 32 bit

sudo service colord status
[sudo] password for paz:
● colord.service - Manage, Install and Generate Color Profiles
   Loaded: loaded (/lib/systemd/system/colord.service; static; vendor preset: enabled)
   Active: active (running) since Mon 2017-07-31 07:48:17 IDT; 3h 0min ago
Main PID: 939 (colord)
    Tasks: 3 (limit: 4915)
   CGroup: /system.slice/colord.service
           └─939 /usr/lib/colord/colord

Jul 31 07:48:16 paz-it systemd[1]: Starting Manage, Install and Generate Color Profiles...
Jul 31 07:48:17 paz-it systemd[1]: Started Manage, Install and Generate Color Profiles.
Jul 31 07:48:17 paz-it colord[939]: failed to get session [pid 825]: No such device or address
Jul 31 07:49:06 paz-it colord[939]: failed to get session [pid 1721]: No such device or address

Revision history for this message

ALinuxUser (buntulongername-new) wrote on 2017-08-03:

#35

I experience the same state of affairs on Linux Mint x64 18.2 Cinnamon.

Revision history for this message

Vladimir Botka (vbotka-9) wrote on 2018-01-09:

#36

FWIW. I experience the same state of affairs on Ubuntu 17.10

Jan 9 00:07:13 planb colord[999]: failed to get session [pid 10836]: No data available

> ps ax | grep 10836
10836 ? Ss 0:00 /usr/sbin/cupsd -l

Revision history for this message

Stefan Wagner (wagner-stefan) wrote on 2018-02-23:

#37

I can confirm this bug too:
<blockquote>
(colord:1154): Cd-WARNING **: failed to get session [pid 2091]: Kein passendes Gerät bzw. keine passende Adresse gefunden]
</blockquote>
linux version:
<blockquote>uname -a
Linux tux201t 4.4.0-112-generic #135-Ubuntu SMP Fri Jan 19 11:48:36 UTC 2018 x86_64 x86_64 x86_64 GNU/Linux
</blockquote>
Ubuntu version (Xubuntu)
<blockquote>cat /etc/lsb-release
DISTRIB_ID=Ubuntu
DISTRIB_RELEASE=16.04
DISTRIB_CODENAME=xenial
DISTRIB_DESCRIPTION="Ubuntu 16.04.3 LTS"
</blockquote>

Revision history for this message

ivanto (ivantu) wrote on 2018-05-11:

#38

still present

:~$ journalctl -b 0 | grep -i fail
mag 11 09:11:13 userpc colord[1140]: (colord:1140): Cd-WARNING **: failed to get session [pid 847]: Device o indirizzo non esistente
mag 11 09:11:13 userpc colord[1140]: (colord:1140): Cd-WARNING **: failed to get session [pid 847]: Device o indirizzo non esistente
mag 11 09:11:13 userpc colord[1140]: (colord:1140): Cd-WARNING **: failed to get session [pid 847]: Device o indirizzo non esistente

:~$ echo $DESKTOP_SESSION
Lubuntu

:~$ uname -a
Linux userpc 4.4.0-124-generic #148-Ubuntu SMP Wed May 2 13:00:18 UTC 2018 x86_64 x86_64 x86_64 GNU/Linux

:~$ cat /etc/lsb-release
DISTRIB_ID=Ubuntu
DISTRIB_RELEASE=16.04
DISTRIB_CODENAME=xenial
DISTRIB_DESCRIPTION="Ubuntu 16.04.4 LTS"

Revision history for this message

tomdean (tomdean) wrote on 2019-08-08:

#39

Still in 18.04 LTS

> uname -a
Linux Meerkat 5.0.0-23-generic #24~18.04.1-Ubuntu SMP Mon Jul 29 16:12:28 UTC 2019 x86_64 x86_64 x86_64 GNU/Linux

> lsb_release -a
No LSB modules are available.
Distributor ID: Ubuntu
Description: Ubuntu 18.04.3 LTS
Release: 18.04
Codename: bionic

> echo $DESKTOP_SESSION
ubuntu

> journalctl -b 0 | grep -i fail | grep -i colord
Aug 07 16:25:47 Meerkat colord[981]: failed to get session [pid 847]: No data available
Aug 07 16:25:47 Meerkat colord[981]: failed to get session [pid 847]: No data available
Aug 08 00:08:17 Meerkat colord[981]: failed to get session [pid 9890]: No data available
Aug 08 00:08:17 Meerkat colord[981]: failed to get session [pid 9890]: No data available

Revision history for this message

chris pollock (cpollock) wrote on 2019-08-08:

#40

I can verify that here as well

uname -a
Linux localhost 5.0.0-23-generic #24~18.04.1-Ubuntu SMP Mon Jul 29 16:12:28 UTC 2019 x86_64 x86_64 x86_64 GNU/Linux

chris@localhost:~$ lsb_release -a
No LSB modules are available.
Distributor ID: Ubuntu
Description: Ubuntu 18.04.3 LTS
Release: 18.04
Codename: bionic

echo $DESKTOP_SESSION
gnome

journalctl -b 0 | grep -i fail | grep -i colord
Aug 07 17:47:57 localhost colord[1249]: failed to get session [pid 1062]: No data available
Aug 07 17:47:58 localhost colord[1249]: failed to get session [pid 1062]: No data available
Aug 08 00:06:43 localhost colord[1249]: failed to get session [pid 11911]: No data available
Aug 08 00:06:43 localhost colord[1249]: failed to get session [pid 11911]: No data available

Revision history for this message

WinEunuchs2Unix (ricklee518) wrote on 2019-10-25:

#41

Bug still exists on Ubuntu 16.04.6 LTS, Kernel 4.14.140. Found when looking for what was causing xrandr to reset screens to full brightness and gamma. Even if `colord` isn't culprit, life is easier with less spam in journalctl.

Ignore extra `s` in `fails` below (line wrap off) for bug report:

$ journalctl | grep "failed to get session \[pid"
Aug 24 08:43:54 alien colord[1366]: (colord:1366): Cd-WARNING **: fails
Aug 24 08:43:54 alien colord[1366]: (colord:1366): Cd-WARNING **: fails
Aug 25 07:41:51 alien colord[1366]: (colord:1366): Cd-WARNING **: fails
Aug 25 07:41:51 alien colord[1366]: (colord:1366): Cd-WARNING **: fails

.. (SNIP) ..

Oct 22 04:33:50 alien colord[1215]: (colord:1215): Cd-WARNING **: fails
Oct 22 04:33:50 alien colord[1215]: (colord:1215): Cd-WARNING **: fails
Oct 23 04:34:53 alien colord[1215]: (colord:1215): Cd-WARNING **: fails
Oct 23 04:34:53 alien colord[1215]: (colord:1215): Cd-WARNING **: fails
Oct 24 04:36:20 alien colord[1215]: (colord:1215): Cd-WARNING **: fails
Oct 24 04:36:20 alien colord[1215]: (colord:1215): Cd-WARNING **: fails
Oct 25 04:36:56 alien colord[1215]: (colord:1215): Cd-WARNING **: fails
Oct 25 04:36:56 alien colord[1215]: (colord:1215): Cd-WARNING **: fails

Ubuntu
colord package

(colord:832): Cd-WARNING **: failed to get session [pid 690]: Unknown error -2

Bug Description

Duplicates of this bug

Other bug subscribers

Bug attachments

Remote bug watches

Ubuntucolord package

(colord:832): Cd-WARNING **: failed to get session [pid 690]: Unknown error -2

Bug Description

Duplicates of this bug

Other bug subscribers

Bug attachments

Remote bug watches

Ubuntu
colord package