APT error messages encountered for Stretch SolydK x86_64

[UncleSam]

A routine APT update on my AMD AMD A8-5600K 4-core CPU returned some error messages:

Code: Select all

root@solydk1:/home/user# apt-get update && apt-get upgrade
Get:1 http://security.debian.org stretch/updates InRelease [94.3 kB]
Ign:2 http://deb.debian.org/debian stretch InRelease                                                          
Hit:3 http://deb.debian.org/debian stretch-updates InRelease                                                  
Hit:4 http://deb.debian.org/debian stretch Release                                                            
Hit:5 http://ftp.debian.org/debian stretch-backports InRelease                                                
Hit:7 https://repository.solydxk.com solydxk-9 InRelease
Fetched 94.3 kB in 0s (105 kB/s)
Reading package lists... Done
Reading package lists... Done
Building dependency tree       
Reading state information... Done
Calculating upgrade... Done
The following packages will be upgraded:
  solydk-system-adjustments-9 solydxk-system
2 upgraded, 0 newly installed, 0 to remove and 0 not upgraded.
Need to get 3,044 kB of archives.
After this operation, 0 B of additional disk space will be used.
Do you want to continue? [Y/n] y
Get:1 https://repository.solydxk.com solydxk-9/main amd64 solydk-system-adjustments-9 all 2.9.9 [2,213 kB]
Get:2 https://repository.solydxk.com solydxk-9/main amd64 solydxk-system all 3.2.2 [831 kB]
Fetched 3,044 kB in 3s (795 kB/s)       
(Reading database ... 287857 files and directories currently installed.)
Preparing to unpack .../solydk-system-adjustments-9_2.9.9_all.deb ...
Unpacking solydk-system-adjustments-9 (2.9.9) over (2.9.8) ...
Preparing to unpack .../solydxk-system_3.2.2_all.deb ...
Unpacking solydxk-system (3.2.2) over (3.2.1) ...
Setting up solydxk-system (3.2.2) ...
Processing triggers for mime-support (3.60) ...
Processing triggers for desktop-file-utils (0.23-1) ...
Processing triggers for menu (2.1.47+b1) ...
Setting up solydk-system-adjustments-9 (2.9.9) ...
QStandardPaths: wrong ownership on runtime directory /run/user/1000, 1000 instead of 0
QStandardPaths: wrong ownership on runtime directory /run/user/1000, 1000 instead of 0
QStandardPaths: wrong ownership on runtime directory /run/user/1000, 1000 instead of 0
QStandardPaths: wrong ownership on runtime directory /run/user/1000, 1000 instead of 0
update-initramfs: deferring update (trigger activated)
Generating grub configuration file ...
Found background image: /usr/share/images/desktop-base/desktop-grub.png
Found linux image: /boot/vmlinuz-4.9.0-8-amd64
Found initrd image: /boot/initrd.img-4.9.0-8-amd64
mount: mount /dev/sdb1 on /mnt/b1 failed: Structure needs cleaning
done
Processing triggers for hicolor-icon-theme (0.15-1) ...
Processing triggers for fontconfig (2.11.0-6.7+b1) ...
Processing triggers for initramfs-tools (0.130) ...
update-initramfs: Generating /boot/initrd.img-4.9.0-8-amd64

I am reporting this because I don't understand what the "wrong ownership" messages mean.
I encountered no problem, but this just happened so it is too early to tell, I guess.

Apparently one file on /boot was changed:

Code: Select all

user@solydk1:~$ ls -Fdltr /boot/vmlinuz-4.9.0-8-amd64
-rw-r--r-- 1 root root 4241184 Feb 19 04:05 /boot/vmlinuz-4.9.0-8-amd64
user@solydk1:~$ ls -Fdltr /boot/initrd.img-4.9.0-8-amd64
-rw-r--r-- 1 root root 26545390 Mar 13 09:40 /boot/initrd.img-4.9.0-8-amd64

If I should do anything , please tell me.

[Arjen Balfoort]

I think you get this message:

Code: Select all

QStandardPaths: wrong ownership on runtime directory /run/user/1000, 1000 instead of 0

because you ran the upgrade as su instead of as a user with sudo.

I don't know what triggers this message but I suspect python in this case.

However, I see the upgrade finished despite the errors. So, these were no fatal errors for dpkg and you can ignore these errors.

initrd.img-4.9.0-8-amd64 was correctly updated by initramfs-tools.

[EDIT]
The message is not an error message. Just a message and messages can safely be ignored.

[Arjen Balfoort]

I reinstalled solydk-system-adjustments-9 with sudo and as su.
You can see that QStandardPaths shows two different messages:

Code: Select all

solydxk@solydxk:~$ apt reinstall solydk-system-adjustments-9    
Reading package lists... Done
Building dependency tree       
Reading state information... Done
0 upgraded, 0 newly installed, 1 reinstalled, 0 to remove and 0 not upgraded.
Need to get 0 B/2,213 kB of archives.
After this operation, 0 B of additional disk space will be used.
(Reading database ... 230116 files and directories currently installed.)
Preparing to unpack .../solydk-system-adjustments-9_2.9.9_all.deb ...
Unpacking solydk-system-adjustments-9 (2.9.9) over (2.9.9) ...
Processing triggers for solydxk-system (3.2.2) ...
Processing triggers for mime-support (3.60) ...
Processing triggers for desktop-file-utils (0.23-1) ...
Setting up solydk-system-adjustments-9 (2.9.9) ...
QStandardPaths: XDG_RUNTIME_DIR not set, defaulting to '/tmp/runtime-root'
QStandardPaths: XDG_RUNTIME_DIR not set, defaulting to '/tmp/runtime-root'
QStandardPaths: XDG_RUNTIME_DIR not set, defaulting to '/tmp/runtime-root'
QStandardPaths: XDG_RUNTIME_DIR not set, defaulting to '/tmp/runtime-root'
update-initramfs: deferring update (trigger activated)
Generating grub configuration file ...
Found background image: /usr/share/images/desktop-base/desktop-grub.png
Found linux image: /boot/vmlinuz-4.9.0-8-amd64
Found initrd image: /boot/initrd.img-4.9.0-8-amd64
Found SolydX 9 64-bit (9) on /dev/sdb1
Adding boot menu entry for EFI firmware configuration
done
Processing triggers for fontconfig (2.11.0-6.7+b1) ...
Processing triggers for initramfs-tools (0.130) ...
update-initramfs: Generating /boot/initrd.img-4.9.0-8-amd64
solydxk@solydxk:~$ su
Password: 
root@solydxk:/home/solydxk# apt reinstall solydk-system-adjustments-9
Reading package lists... Done
Building dependency tree       
Reading state information... Done
0 upgraded, 0 newly installed, 1 reinstalled, 0 to remove and 0 not upgraded.
Need to get 0 B/2,213 kB of archives.
After this operation, 0 B of additional disk space will be used.
(Reading database ... 230116 files and directories currently installed.)
Preparing to unpack .../solydk-system-adjustments-9_2.9.9_all.deb ...
Unpacking solydk-system-adjustments-9 (2.9.9) over (2.9.9) ...
Processing triggers for solydxk-system (3.2.2) ...
Processing triggers for mime-support (3.60) ...
Processing triggers for desktop-file-utils (0.23-1) ...
Setting up solydk-system-adjustments-9 (2.9.9) ...
QStandardPaths: wrong ownership on runtime directory /run/user/1000, 1000 instead of 0
QStandardPaths: wrong ownership on runtime directory /run/user/1000, 1000 instead of 0
QStandardPaths: wrong ownership on runtime directory /run/user/1000, 1000 instead of 0
QStandardPaths: wrong ownership on runtime directory /run/user/1000, 1000 instead of 0
update-initramfs: deferring update (trigger activated)
Generating grub configuration file ...
Found background image: /usr/share/images/desktop-base/desktop-grub.png
Found linux image: /boot/vmlinuz-4.9.0-8-amd64
Found initrd image: /boot/initrd.img-4.9.0-8-amd64
Found SolydX 9 64-bit (9) on /dev/sdb1
Adding boot menu entry for EFI firmware configuration
done
Processing triggers for fontconfig (2.11.0-6.7+b1) ...
Processing triggers for initramfs-tools (0.130) ...
update-initramfs: Generating /boot/initrd.img-4.9.0-8-amd64

I now see, these are not errors, just messages. They can safely be ignored.

[UncleSam]

Okay, thank you, Arjen, for the detailed explanation.

One thing doesn't seem right to me--I repeated the apt reinstall command in your second post as user.
I was prompted for my user password and entered it before the command was executed. It seems to be that this command ought to be a superuser command, and not a user command.

[Arjen Balfoort]

That is by design.
Run

Code: Select all

apt -h

for the full parameter list.