Error prompt: TX2 system program problem detected

Right after power up and UI icons displayed on the left, a small window would pop up in the center:

<b>System program problem detected</b>
Do you want to report the problem now?

Clicking on [Report problem] would produce a report window of “Sorry, Ubuntu 16.04 has experienced an internal error”.

Clicking on the “show details” would show that

ExecutablePath
  /usr/lib/colord/colord-sane
Package
  colord 1.2.12-1ubuntu1
ProblemType
  Crash

By the way, the problem happens after installed JetPack 3.1 (with Ubuntu 14.04 host on a 64bit PC)

Any suggestion on how to fix it?

colord isn’t specifically related to a Jetson and might be related to printers or scanners (or the software even if you don’t have a printer or scanner). First, is the system updated? Here’s what I’d suggest…

First check that there is no error in “sha1sum -c /etc/nv_tegra_release”. If there is, and if it is a libglx.so error, run this command to fix:

<b>sudo ln -sf /usr/lib/aarch64-linux-gnu/tegra/libglx.so /usr/lib/xorg/modules/extensions/libglx.so</b>

Then run “sudo apt update” followed by “sudo apt-get upgrade”. After this, before you do anything else, check again if “sha1sum -c /etc/nv_tegra_release” shows an error with libglx.so. If it does, just fix it with that above command (mesa package is required and there is more than one mesa-related package…on of those packages when updated overwrites the NVIDIA version which will break the GUI if you log out or reboot). Once packages are updated you can do some debugging.

The way to see if colord is running:

systemctl status colord.service

colord saves and restores color profile information with devices which might need some form of color calibration, e.g., scanners and printers. It would probably crash if there were permission issues when writing, or if disk space ran out. See how much space you have:

df -H /

When colord talks to different parts of the system it uses dbus. What makes this particularly difficult is that you get your error while logging in with the GUI, but you can’t use the dbus-monitor tool unless there is a running GUI (it’s a session tool for apps to talk to each other…it can’t send a message without a session). If the above systemctl command shows colord.service is not running, then the error is from prior to your login, and might not be as hard to locate. If colord.service is running, then there is an error revolving around your login session.

Is colord.service running? After login to the GUI do you see anything from “dmesg | egrep -i colord”?

sha1sum -c /etc/nv_tegra_release

/usr/lib/aarch64-linux-gnu/libv4l/plugins/libv4l2_nvvideocodec.so: OK
/usr/lib/aarch64-linux-gnu/libv4l/plugins/libv4l2_nvvidconv.so: OK
/usr/lib/aarch64-linux-gnu/tegra/libnvomx.so: OK
/usr/lib/aarch64-linux-gnu/tegra/libnveglstreamproducer.so: OK
/usr/lib/aarch64-linux-gnu/tegra/libnvtx_helper.so: OK
/usr/lib/aarch64-linux-gnu/tegra/libnvddk_vic.so: OK
/usr/lib/aarch64-linux-gnu/tegra/libglx.so: OK
/usr/lib/aarch64-linux-gnu/tegra/libargus_socketserver.so: OK
/usr/lib/aarch64-linux-gnu/tegra/libnvmmlite.so: OK
/usr/lib/aarch64-linux-gnu/tegra/libnvddk_2d_v2.so: OK
/usr/lib/aarch64-linux-gnu/tegra/libnvwinsys.so: OK
/usr/lib/aarch64-linux-gnu/tegra/libargus.so: OK
/usr/lib/aarch64-linux-gnu/tegra/libnvmm.so: OK
/usr/lib/aarch64-linux-gnu/tegra/libnvjpeg.so: OK
/usr/lib/aarch64-linux-gnu/tegra/libnvexif.so: OK
/usr/lib/aarch64-linux-gnu/tegra/libnvdc.so: OK
/usr/lib/aarch64-linux-gnu/tegra/libnvavp.so: OK
/usr/lib/aarch64-linux-gnu/tegra/libnvtestresults.so: OK
/usr/lib/aarch64-linux-gnu/tegra/libargus_socketclient.so: OK
/usr/lib/aarch64-linux-gnu/tegra/libnvmm_utils.so: OK
/usr/lib/aarch64-linux-gnu/tegra/libnvfnet.so: OK
/usr/lib/aarch64-linux-gnu/tegra/libnvll.so: OK
/usr/lib/aarch64-linux-gnu/tegra/libnvcameratools.so: OK
/usr/lib/aarch64-linux-gnu/tegra/libnvapputil.so: OK
/usr/lib/aarch64-linux-gnu/tegra/libnveglstream_camconsumer.so: OK
/usr/lib/aarch64-linux-gnu/tegra/libnvrm.so: OK
/usr/lib/aarch64-linux-gnu/tegra/libnvcam_imageencoder.so: OK
/usr/lib/aarch64-linux-gnu/tegra/libtegrav4l2.so: OK
/usr/lib/aarch64-linux-gnu/tegra/libnvparser.so: OK
/usr/lib/aarch64-linux-gnu/tegra/libnvtvmr.so: OK
/usr/lib/aarch64-linux-gnu/tegra/libnvrm_gpu.so: OK
/usr/lib/aarch64-linux-gnu/tegra/libnvtnr.so: OK
/usr/lib/aarch64-linux-gnu/tegra/libnvcamerautils.so: OK
/usr/lib/aarch64-linux-gnu/tegra/libnvidia-egl-wayland.so: OK
/usr/lib/aarch64-linux-gnu/tegra/libnvfnetstoredefog.so: OK
/usr/lib/aarch64-linux-gnu/tegra/libnvodm_imager.so: OK
/usr/lib/aarch64-linux-gnu/tegra/libnvmmlite_utils.so: OK
/usr/lib/aarch64-linux-gnu/tegra/libnvcolorutil.so: OK
/usr/lib/aarch64-linux-gnu/tegra/libnvmmlite_video.so: OK
/usr/lib/aarch64-linux-gnu/tegra/libnvmmlite_image.so: OK
/usr/lib/aarch64-linux-gnu/tegra/libnvmm_contentpipe.so: OK
/usr/lib/aarch64-linux-gnu/tegra/libnvimp.so: OK
/usr/lib/aarch64-linux-gnu/tegra/libnvos.so: OK
/usr/lib/aarch64-linux-gnu/tegra/libnvrm_graphics.so: OK
/usr/lib/aarch64-linux-gnu/tegra/libnvmedia.so: OK
/usr/lib/aarch64-linux-gnu/tegra/libnvfnetstorehdfx.so: OK
/usr/lib/aarch64-linux-gnu/tegra/libnvomxilclient.so: OK
/usr/lib/aarch64-linux-gnu/tegra/libnvcamlog.so: OK
/usr/lib/aarch64-linux-gnu/tegra/libnvmm_parser.so: OK
/usr/lib/aarch64-linux-gnu/tegra/libscf.so: OK
/usr/lib/aarch64-linux-gnu/tegra/libnvosd.so: OK
/usr/lib/xorg/modules/drivers/nvidia_drv.so: OK
/usr/lib/xorg/modules/extensions/libglx.so: OK

df -H /

Filesystem      Size  Used Avail Use% Mounted on
/dev/root        30G   12G   17G  41% /

systemctl status colord.service

colord.service - Manage, Install and Generate Color Profiles
 Loaded: loaded (/lib/systemd/system/colord.service; static; vendor preset: enabled)
   Active: active (running) since Sun 2017-10-01 03:34:45 UTC; 1 day 16h ago
 Main PID: 1286 (colord)
   CGroup: /system.slice/colord.service
           └─1286 /usr/lib/colord/colord

Oct 01 03:34:45 tegra-ubuntu systemd[1]: Starting Manage, Install and Generate Color Profiles...
Oct 01 03:34:45 tegra-ubuntu systemd[1]: Started Manage, Install and Generate Color Profiles.
Oct 01 03:34:47 tegra-ubuntu colord[1286]: colord-sane: simple-watch.c:454: avahi_simple_poll_prepare: Assertion `s->state == STATE_INIT

dmesg| egrep -i colord shows no result.

However, dmesg shows some errors, not sure if they would cause colord to malfunction.

[   17.137219] dhd_preinit_ioctls pspretend_threshold for HostAPD failed  -23
[   17.142572] Firmware version = wl0: May  4 2017 13:48:00 version 7.35.221.21 (r697384) FWID 01-58d9d0b3
[   17.145326] dhd_interworking_enable: failed to set WNM info, ret=-23
[   17.145564] tegra_sysfs_on
[   17.238534] IPv6: ADDRCONF(NETDEV_UP): eth0: link is not ready
[   17.240350] gpio tegra-gpio wake18 for gpio=101(M:5)
[   17.242287] IPv6: ADDRCONF(NETDEV_UP): eth0: link is not ready
[   17.416289] CFGP2P-ERROR) wl_cfgp2p_add_p2p_disc_if : P2P interface registered
[   17.442631] WLC_E_IF: NO_IF set, event Ignored
[   18.179104] PD DISP2 index4 DOWN
[   18.179266] PD DISP1 index3 DOWN
[   18.179342] PD DISP0 index2 DOWN
[   18.189915] PD DISP0 index2 UP
[   18.191057] PD DISP1 index3 UP
[   18.191140] PD DISP2 index4 UP
[   18.192637] Parent Clock set for DC plld2
[   18.194044] tegradc 15210000.nvdisplay: hdmi: pclk:148500K, set prod-setting:prod_c_150M
[   20.393735] fuse init (API version 7.23)
[   21.121743] eqos 2490000.ether_qos eth0: Link is Up - 1Gbps/Full - flow control off
[   21.130875] IPv6: ADDRCONF(NETDEV_CHANGE): eth0: link becomes ready
[   22.422530] PD DISP2 index4 DOWN
[   22.422683] PD DISP1 index3 DOWN
[   22.422758] PD DISP0 index2 DOWN
[   22.433265] PD DISP0 index2 UP
[   22.434567] PD DISP1 index3 UP
[   22.435189] PD DISP2 index4 UP
[   22.437077] Parent Clock set for DC plld2
[   22.438668] tegradc 15210000.nvdisplay: hdmi: pclk:148500K, set prod-setting:prod_c_150M
[   23.540537] FAT-fs (mmcblk1p1): Volume was not properly unmounted. Some data may be corrupt. Please run fsck.

Hi linuxdev, thanks for your comments. I just ran the checking as you suggested. And the results are posted above.

The system has be been flashed with JetPack 3.1. I haven’t done much programming yet as my machine is in sort of a backup mode while my partner was cranking his Jetson box.

Although I don’t see anything specific, I do see something of interest:

[   23.540537] FAT-fs (mmcblk1p1): Volume was not properly unmounted. Some data may be corrupt. Please run fsck.

Apparently you are using an SD card and it is formatted with VFAT file system type. This is not journaling, and there are errors on the SD card which need to be fixed (this card should not be removed without first using umount or other safe eject tool).

To start with, is the SD card involved with anything which might be generating the error? Typically one would fix the error via:

sudo umount /dev/mmcblk1p1
fsck.fat /dev/mmcblk1p1

…then reboot. Note that although fsck can fix any corruption on the SD card it is still possible the data which was “fixed” will now be missing.

The colord service appears to be running normally.

Good catch! I think my SD card could be a source of problem. The 32G card was taken from my camera, and hasn’t been used after inserted to TX2. I just didn’t get a chance to format it.

A little problem though. After I clicked the SD card icon on the GUI, and request to format the whole thing to EXT4, the icon disappeared from the GUI. I rebooted the system, still didn’t see the SD Card.

mkfs.ext4 /dev/mcblk1p1

mke2fs 1.42.13 (17-May-2015)
The file /dev/mcblk1p1 does not exist and no size was specified.

lsblk

mmcblk0rpmb  179:24   0     4M  0 disk 
mmcblk0boot0 179:8    0     4M  1 disk 
mmcblk0boot1 179:16   0     4M  1 disk 
mmcblk0      179:0    0  29.1G  0 disk 
├─mmcblk0p1  179:1    0    28G  0 part /
├─mmcblk0p2  179:2    0     4M  0 part 
├─mmcblk0p3  179:3    0   256K  0 part 
├─mmcblk0p4  179:4    0   512K  0 part 
├─mmcblk0p5  179:5    0     3M  0 part 
├─mmcblk0p6  179:6    0     2K  0 part 
├─mmcblk0p7  179:7    0   604K  0 part 
├─mmcblk0p8  259:0    0   500K  0 part 
├─mmcblk0p9  259:1    0     2M  0 part 
├─mmcblk0p10 259:2    0     6M  0 part 
├─mmcblk0p11 259:3    0     2M  0 part 
├─mmcblk0p12 259:4    0   128M  0 part 
├─mmcblk0p13 259:5    0    32M  0 part 
├─mmcblk0p14 259:6    0    64M  0 part 
├─mmcblk0p15 259:7    0   512K  0 part 
├─mmcblk0p16 259:8    0   256M  0 part 
└─mmcblk0p17 259:9    0 646.7M  0 part 
mmcblk1      179:32   0  29.5G  0 disk 
└─mmcblk1p1  179:33   0  29.5G  0 part

Any idea what to do next?

Looks like it is caused by a typographic error. “/dev/mcblk1p1” is incorrect…it is “mmcblk1p1” (two leading “m” characters instead of one).

Oops, silly me.

I think I did it right this time.

sudo mkfs.ext4 /dev/mmcblk1p1
sudo mount -t ext4 /dev/mmcblk1p1 /mnt

Now do I need to do anything else in order to use the SD card?

BTW, thanks so much, linuxdev. If I took out the SD card, the “system program problem” error would be gone. To that issue, you solved it.

The SD card should play nicely now. It’ll even have a journal to help avoid future corruption (though you lose data whenever the journal stops corruption). It sounds like the error went away (unless I’m reading this wrong), so perhaps the system program problem was an attempt to mount a corrupted file system (as opposed to the program itself being the problem).

Side note: I don’t like VFAT, though it can be used across multiple operating systems. If you ever need this to work from Windows you might format as NTFS…unfortunately, cameras and many devices don’t support NTFS or ext4 (some appliances use Linux, so they do support ext4). ext4 is a very good choice if the SD card is to run only on Linux.

Hi linuxdev, I think to this point I can say for sure the error is gone and the root cause was due to the format of SD card as you suspected. With the SD card in the reader, no error is shown after a few rounds of reboot.

The SD card is working, but I have another question about SD’s mount directory. I mounted it to /mnt but the physical directory seems goes to

/media/nvidia/a83fb6f4-d15e-4c17-9a19-e700f2d87ca6

If I create a file or folder under /mnt, then open the SD icon from GUI, the change would not be reflected in the GUI window.

Let me start another thread as the issue seems unrelated to the topic here. Again, thanks a lot for your insight.