'Chökie Gyaltsen' via qubes-users: > Hello all, > > > I've just installed Qubes latest preview 3. Installed it offline, so all the > logs you will see are from a disconnected system. There are some services > disabled related to security that worry me ( listed below ). Also some > entries that i have some doubts on sys logs ( written below also ). I had a > critical warning just after the install, related to gtk before the login > screen. Attached are all the logs found, complete. If you need some other > info please just let me know.
> > output of systemctl -al showing inactive services only ( full list of > services attached ) > > ----------------------------------------------------------------------------------------- > UNIT > LOAD ACTIVE SUB > DESCRIPTION > boot.automount > loaded inactive dead boot.automount > The question here is if it is normal that these services are disabled on > first login just after a disconnected install? Yes; most of those only fire once on boot and are no longer needed afterwards. > > > > output of journalctl -ax --merge ( full journalctl output attached ) below > the messages i have some comments on my doubts > ------------------------------------------------------------------------------------------------------------------------- > Dec 15 20:52:30 dom0 kernel: Linux version 4.19.86-1.pvops.qubes.x86_64 > (user@build-fedora4) (gcc version 6.4.1 20170727 (Red Hat 6.4.1-1) (GCC)) #1 > SMP Sun Dec 1 07:16:00 UTC 2019 > Dec 15 20:52:30 dom0 kernel: Command line: placeholder > root=/dev/mapper/qubes_dom0-root ro rd.lvm.lv=qubes_dom0/root > rd.lvm.lv=qubes_dom0/swap i915.alpha_support=1 plymouth.ignore-serial-con > ( is it possible to disable alpha support? i Have a skylake 9th gen ) - later > there is an entry stating that it taints the kernel Possibly. Keep in mind dom0 runs Fedora 25, so does not have newer drivers. In most cases, it does not matter. You could try to remove it and see what happens. On this and your other hardware related questions, you could also try booting a newer version of Qubes (i.e. 4.0.2rc3) or another distribution like Debian 10 on the same hardware and cross-referencing logs.> > Dec 15 20:52:30 dom0 systemd-modules-load[195]: Failed to find module > 'uinput' > > ( found info on kernel.org stating this module is for user input, is it > normal that the module is not present? ) No, it is present on mine. > Dec 15 20:52:31 dom0 kernel: nvme nvme0: missing or invalid SUBNQN field. > Dec 15 20:52:31 dom0 kernel: nvme nvme0: Shutdown timeout set to 8 seconds > Dec 15 20:52:31 dom0 kernel: nvme0n1: p1 p2 > ( after some searching i found that this message is related to the boot disk > Samsung V-NAND SSD 970 PRO NVMe M.2, just installed. The hardware is pretty > new but Samsung has made available the source code for 'magician' ( if i > remember correctly, ( i am still offline ), software under request. The linux > version is old and does not recognize any of the disks present on the > machine. Do you know of any opensource project ongoing to port the tool to > linux? ) No, but I am not aware of any functionality the software provides that can't be accomplished some other way. Not really Qubes related, though. > Dec 15 20:52:34 dom0 kernel: platform regulatory.0: Direct firmware load for > regulatory.db failed with error -2 > ( is it normal this error? ) Yes, Xen/Qubes blocks some direct hardware access. > Dec 15 20:52:35 dom0 systemd[1]: tmp.mount: Directory /tmp to mount over is > not empty, mounting anyway. > ( this always happened in previous installations, strange no? ) Typical on a remount. > Dec 15 20:52:36 dom0 systemd-tmpfiles[1180]: Cannot set file attribute for > '/var/log/journal', value=0x00800000, mask=0x00800000: Operation not supported > Dec 15 20:52:36 dom0 systemd-tmpfiles[1180]: Cannot set file attribute for > '/var/log/journal/2f474aa11eba4b1394708823e685bcd8', value=0x00800000, > mask=0x00800000: Operation not supported > ( is this normal? ) My logs show it too. > Dec 15 20:52:36 dom0 xenstored[1267]: TDB: tdb_open_ex: could not open file > /var/lib/xenstored/tdb: No such file or directory > Dec 15 20:52:36 dom0 xenstored[1267]: Checking store ... > ( this message happens at every boot ) Same. > Dec 15 20:52:37 dom0 xenstored[1267]: Checking store complete. > > Dec 15 20:52:38 dom0 udisksd[1497]: Acquired the name org.freedesktop.UDisks2 > on the system message bus > Dec 15 20:52:38 dom0 udisksd[1497]: Error loading modules: Error opening > directory '/usr/lib64/udisks2/modules': No such file or directory Did you install something in dom0? Generally, you should not. Uninstall it or reinstall Qubes and the error should go away. > Dec 15 22:29:02 dom0 anacron[12882]: Can't find sendmail at > /usr/sbin/sendmail, not mailing output > > ( below i have the configuration of anacron, is this email sent to root? If > root is disabled can it be redirected? ) Email isn't sent anywhere, because sendmail isn't installed. > Dec 16 08:57:02 dom0 xfce4-notifyd[15405]: xfce_notify_window_expire_timeout: > assertion 'XFCE_IS_NOTIFY_WINDOW(data)' failed > Dec 16 08:57:30 dom0 xfce4-notifyd[15405]: xfce_notify_window_expire_timeout: > assertion 'XFCE_IS_NOTIFY_WINDOW(data)' failed > Dec 16 08:57:55 dom0 xfce4-notifyd[15405]: xfce_notify_window_expire_timeout: > assertion 'XFCE_IS_NOTIFY_WINDOW(data)' failed > Dec 16 08:58:25 dom0 xfce4-notifyd[15405]: xfce_notify_window_expire_timeout: > assertion 'XFCE_IS_NOTIFY_WINDOW(data)' failed > Dec 16 08:58:52 dom0 xfce4-notifyd[15405]: xfce_notify_window_expire_timeout: > assertion 'XFCE_IS_NOTIFY_WINDOW(data)' failed > ( i suppose this was the first critical message i got after install and > before the login screen, below the second. I include Xorg logs, do not know > if it helps or not troubleshooting. Please let me know what to do to solve > this ) Were you having trouble with XFCE windows in Qubes? If not, there's nothing to solve! Ignore the messages unless you're experiencing problems. -- - don't top post Mailing list etiquette: - trim quoted reply to only relevant portions - when possible, copy and paste text instead of screenshots -- You received this message because you are subscribed to the Google Groups "qubes-users" group. To unsubscribe from this group and stop receiving emails from it, send an email to qubes-users+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/qubes-users/8668c77b-2f6e-261a-9943-30d2955fed78%40danwin1210.me.
