LinuxQuestions.org
Visit Jeremy's Blog.
Home Forums Tutorials Articles Register
Go Back   LinuxQuestions.org > Forums > Linux Forums > Linux - Software
Reload this Page KDE Plasma, recording video of the boot stage
User Name
Password
Linux - Software This forum is for Software issues.
Having a problem installing a new program? Want to know which application is best for the job? Post your question in this forum.

Notices


Reply
Page 1 of 2 1 2
  Search this Thread
Old 10-26-2023, 01:52 AM   #1
alex4buba
Member
 
Registered: Jul 2020
Posts: 624

Rep: Reputation: Disabled
KDE Plasma, recording video of the boot stage

I get errors during boot time and am unable to see what they are so as to try and attend to it. Checking the various log files is not much help.

Is there a way to record the process from power ON until end of the boot process that I can later watch the clip in slow motion?

Thank you
 
Old 10-26-2023, 08:52 PM   #2
frankbell
LQ Guru
Contributing Member
 
Registered: Jan 2006
Location: Virginia, USA
Distribution: Slackware, Ubuntu MATE, Mageia, and whatever VMs I happen to be playing with
Posts: 19,386
Blog Entries: 28

Rep: Reputation: 6164Reputation: 6164Reputation: 6164Reputation: 6164Reputation: 6164Reputation: 6164Reputation: 6164Reputation: 6164Reputation: 6164Reputation: 6164Reputation: 6164
I assume you are talking about the boot messages that appear on the monitor. I doubt there's anyway you can have the computer record screen activity before it's booted and operational.

Have you tried using a video recorder of some sort (maybe a phone or tablet cam), or, alternatively, a series of quickly snapped photos?

I'm almost inclined to think that the latter would be a better alternative.
 
Old 10-29-2023, 05:25 AM   #3
mrmazda
LQ Guru
 
Registered: Aug 2016
Location: SE USA
Distribution: openSUSE 24/7; Debian, Knoppix, Mageia, Fedora, others
Posts: 5,878
Blog Entries: 1

Rep: Reputation: 2078Reputation: 2078Reputation: 2078Reputation: 2078Reputation: 2078Reputation: 2078Reputation: 2078Reputation: 2078Reputation: 2078Reputation: 2078Reputation: 2078
Language used in OP suggests only direct searches within log files found with a file viewer. In a normal systemd managed installation, various formerly normal .log files no longer exist. Instead, logging goes to the systemd journal, which is accessed using the journalctl command. If persistent journal is enabled, signified by existence of /var/log/journal/, the journal from the 2nd previous boot can be accessed via 'journalctl -b -2'.
 
Old 10-29-2023, 07:20 AM   #4
smallpond
Senior Member
 
Registered: Feb 2011
Location: Massachusetts, USA
Distribution: Fedora
Posts: 4,160

Rep: Reputation: 1266Reputation: 1266Reputation: 1266Reputation: 1266Reputation: 1266Reputation: 1266Reputation: 1266Reputation: 1266Reputation: 1266
Add a serial console on the kernel command line and log what is sent with Putty on another system.
 
Old 10-29-2023, 04:19 PM   #5
alex4buba
Member
 
Registered: Jul 2020
Posts: 624

Original Poster
Rep: Reputation: Disabled
Quote:
Originally Posted by frankbell View Post
I assume you are talking about the boot messages that appear on the monitor. I doubt there's anyway you can have the computer record screen activity before it's booted and operational.

Have you tried using a video recorder of some sort (maybe a phone or tablet cam), or, alternatively, a series of quickly snapped photos?

I'm almost inclined to think that the latter would be a better alternative.
OK, not record, but is there any way to see those messages in a file? When I try looking log files, I can't understand which line represents any of those boot errors. I wonder, am I the only Linux user that is asking this question?

Most feedback I get from people in the group are using terms and acronyms far from my knowledge.

Thank you
 
Old 10-29-2023, 04:23 PM   #6
alex4buba
Member
 
Registered: Jul 2020
Posts: 624

Original Poster
Rep: Reputation: Disabled
Quote:
Originally Posted by mrmazda View Post
Language used in OP suggests only direct searches within log files found with a file viewer. In a normal systemd managed installation, various formerly normal .log files no longer exist. Instead, logging goes to the systemd journal, which is accessed using the journalctl command. If persistent journal is enabled, signified by existence of /var/log/journal/, the journal from the 2nd previous boot can be accessed via 'journalctl -b -2'.
Dear Mr mrmazda,

I am such a beginner that I hardly understand any suggestions, for example - what is OP? What is "normal log"? How do I make persistant journal?

I wonder, am I the only Linux user who wants to see what are the boot message?

Thanks again
 
Old 10-29-2023, 05:11 PM   #7
mrmazda
LQ Guru
 
Registered: Aug 2016
Location: SE USA
Distribution: openSUSE 24/7; Debian, Knoppix, Mageia, Fedora, others
Posts: 5,878
Blog Entries: 1

Rep: Reputation: 2078Reputation: 2078Reputation: 2078Reputation: 2078Reputation: 2078Reputation: 2078Reputation: 2078Reputation: 2078Reputation: 2078Reputation: 2078Reputation: 2078
Quote:
Originally Posted by alex4buba View Post
what is OP?
You, the thread starter, or Original Poster.

Quote:
What is "normal log"?
There were exceptions, but logs generally used to be plain text files that any file viewer or editor could open for reading. Exceptions could be any of various binary formats. In distros with systemd controlling init, a comprehensive binary journalling system is included, accessed and managed via journalctl and /etc/systemd/journald.conf.

Quote:
How do I make persistant journal?
If /var/log/journal/ exists, you already have it. If not, either create that directory manually, or make alteration(s) in /etc/systemd/journald.conf.

Quote:
I wonder, am I the only Linux user who wants to see what are the boot message?
You're definitely not. To that end, I either prevent from being installed, or purge if installed, or neuter if deinstallation is impossible, all packages including the string "plymouth". It apparently exists primarily to make Linux boot more complicated and resemble Windows boot by hiding boot messages. In most cases, those messages scroll by too fast to read, but at least their appearance indicates something is actually happening, or not.
 
Old 10-30-2023, 09:41 PM   #8
alex4buba
Member
 
Registered: Jul 2020
Posts: 624

Original Poster
Rep: Reputation: Disabled
Quote:
Originally Posted by mrmazda View Post
You, the thread starter, or Original Poster.

There were exceptions, but logs generally used to be plain text files that any file viewer or editor could open for reading. Exceptions could be any of various binary formats. In distros with systemd controlling init, a comprehensive binary journalling system is included, accessed and managed via journalctl and /etc/systemd/journald.conf.

If /var/log/journal/ exists, you already have it. If not, either create that directory manually, or make alteration(s) in /etc/systemd/journald.conf.

You're definitely not. To that end, I either prevent from being installed, or purge if installed, or neuter if deinstallation is impossible, all packages including the string "plymouth". It apparently exists primarily to make Linux boot more complicated and resemble Windows boot by hiding boot messages. In most cases, those messages scroll by too fast to read, but at least their appearance indicates something is actually happening, or not.
I don't understand what you wrote in the final paragraph ... You are definetely not...
That folder you mention Journal is present, I am attaching a screen shot of it, but all the files inside it are in binary format, so what can I do with that? Please give me an example, then if I manage to view the contant, what should I look for?
I don't like to be living with the unknown that one day will crash my machine, which happened some 2 weeks ago.

Thanks again for your time
Attached Thumbnails
Click image for larger version Name: Journal.jpg Views: 3 Size: 53.4 KB ID: 41962  
 
Old 10-30-2023, 10:16 PM   #9
mrmazda
LQ Guru
 
Registered: Aug 2016
Location: SE USA
Distribution: openSUSE 24/7; Debian, Knoppix, Mageia, Fedora, others
Posts: 5,878
Blog Entries: 1

Rep: Reputation: 2078Reputation: 2078Reputation: 2078Reputation: 2078Reputation: 2078Reputation: 2078Reputation: 2078Reputation: 2078Reputation: 2078Reputation: 2078Reputation: 2078
Quote:
Originally Posted by alex4buba View Post
I don't understand what you wrote in the final paragraph ... You are definetely not...
...(the only one)...
Quote:
who wants to see what are the boot message
Quote:
all the files inside it are in binary format, so what can I do with that?
Quote:
accessed and managed via journalctl and /etc/systemd/journald.conf
Quote:
Please give me an example
Try typing the command I gave you already. man journalctl. Google has examples too. Try it with the -b option.
Quote:
, then if I manage to view the contant, what should I look for?
Words like "fail", "error", "fault", "not" and so forth.
 
Old 10-31-2023, 02:54 AM   #10
alex4buba
Member
 
Registered: Jul 2020
Posts: 624

Original Poster
Rep: Reputation: Disabled
Quote:
Originally Posted by mrmazda View Post
...(the only one)...
Try typing the command I gave you already. man journalctl. Google has examples too. Try it with the -b option.Words like "fail", "error", "fault", "not" and so forth.
Much appreciated, managed to read the output by redirecting the output to a txt file on the desktop.
Just one thing, can't figure out how to run a "filter" on say fail? Will appreciate an example

say I run just journalctl filter?

Cheers
 
Old 10-31-2023, 03:08 AM   #11
pan64
LQ Addict
 
Registered: Mar 2012
Location: Hungary
Distribution: debian/ubuntu/suse ...
Posts: 22,041

Rep: Reputation: 7348Reputation: 7348Reputation: 7348Reputation: 7348Reputation: 7348Reputation: 7348Reputation: 7348Reputation: 7348Reputation: 7348Reputation: 7348Reputation: 7348
grep is used to look for specific text in such files (log files). For example:
Code:
grep fail output.txt
https://www.cyberciti.biz/faq/howto-...in-linux-unix/
 
1 members found this post helpful.
Old 10-31-2023, 04:25 AM   #12
mrmazda
LQ Guru
 
Registered: Aug 2016
Location: SE USA
Distribution: openSUSE 24/7; Debian, Knoppix, Mageia, Fedora, others
Posts: 5,878
Blog Entries: 1

Rep: Reputation: 2078Reputation: 2078Reputation: 2078Reputation: 2078Reputation: 2078Reputation: 2078Reputation: 2078Reputation: 2078Reputation: 2078Reputation: 2078Reputation: 2078
As in most things Linux, multiple ways to skin a cat. Redirecting to file is certainly a way, but not the only. Try the "less" command on any large plain text file. Once you appreciate less, then journalctl is a breeze, because the same functionality is built into journalctl. IOW, journalctl -b to open the journal for the current boot, then scan via pgdn/pgup and other cursor pad keys, or search for various strings via the search trigger "/", thus:
Code:
sudo journalctl -b
/fail<ENTER>
/<ENTER>
/<ENTER>
interactively locates the first three instances of string "fail" in journal of current boot, while sudo journalctl -b | egrep 'fail|fault' will simply return all instances in current journal of strings "fail" and "fault". There's no need to know the name of the file or the parent directories of the binary systemd journal to use it.
 
Old 10-31-2023, 03:31 PM   #13
alex4buba
Member
 
Registered: Jul 2020
Posts: 624

Original Poster
Rep: Reputation: Disabled
Quote:
Originally Posted by mrmazda View Post
As in most things Linux, multiple ways to skin a cat. Redirecting to file is certainly a way, but not the only. Try the "less" command on any large plain text file. Once you appreciate less, then journalctl is a breeze, because the same functionality is built into journalctl. IOW, journalctl -b to open the journal for the current boot, then scan via pgdn/pgup and other cursor pad keys, or search for various strings via the search trigger "/", thus:
Code:
sudo journalctl -b
/fail<ENTER>
/<ENTER>
/<ENTER>
interactively locates the first three instances of string "fail" in journal of current boot, while sudo journalctl -b | egrep 'fail|fault' will simply return all instances in current journal of strings "fail" and "fault". There's no need to know the name of the file or the parent directories of the binary systemd journal to use it.
I like skinning cats... not really.

After executing the command : sudo journalctl -b | egrep 'fail|fault'

I got the following, that was after a new boot, BUT - what out of all this is really important and I need to try and resolve?

Code:
Nov 01 07:24:33 alexe kernel: pid_max: default: 32768 minimum: 301
Nov 01 07:24:33 alexe kernel: Low-power S0 idle used by default for system suspend
Nov 01 07:24:33 alexe kernel: iommu: Default domain type: Translated
Nov 01 07:24:33 alexe kernel: NetLabel:  unlabeled traffic allowed by default
Nov 01 07:24:33 alexe kernel: PCI: CLS 0 bytes, default 64
Nov 01 07:24:33 alexe kernel: nvme nvme0: 8/0/0 default/read/poll queues
Nov 01 07:24:33 alexe systemd[1]: systemd 249.11-0ubuntu3.10 running in system mode (+PAM +AUDIT +SELINUX +APPARMOR +IMA +SMACK +SECCOMP +GCRYPT +GNUTLS +OPENSSL +ACL +BLKID +CURL +ELFUTILS +FIDO2 +IDN2 -IDN +IPTC +KMOD +LIBCRYPTSETUP +LIBFDISK +PCRE2 -PWQUALITY -P11KIT -QRENCODE +BZIP2 +LZ4 +XZ +ZLIB +ZSTD -XKBCOMMON +UTMP +SYSVINIT default-hierarchy=unified)
Nov 01 07:24:33 alexe systemd[1]: Queued start job for default target Graphical Interface.
Nov 01 07:24:33 alexe systemd-udevd[446]: nvme0n1: Process '/usr/bin/unshare -m /usr/bin/snap auto-import --mount=/dev/nvme0n1' failed with exit code 1.
Nov 01 07:24:33 alexe systemd-udevd[417]: Using default interface naming scheme 'v249'.
Nov 01 07:24:33 alexe systemd-udevd[421]: nvme0n1p2: Process '/usr/bin/unshare -m /usr/bin/snap auto-import --mount=/dev/nvme0n1p2' failed with exit code 1.
Nov 01 07:24:33 alexe systemd-udevd[454]: nvme0n1p1: Process '/usr/bin/unshare -m /usr/bin/snap auto-import --mount=/dev/nvme0n1p1' failed with exit code 1.
Nov 01 07:24:33 alexe systemd-udevd[419]: nvme0n1p3: Process '/usr/bin/unshare -m /usr/bin/snap auto-import --mount=/dev/nvme0n1p3' failed with exit code 1.
Nov 01 07:24:33 alexe systemd-udevd[413]: sda: Process '/usr/bin/unshare -m /usr/bin/snap auto-import --mount=/dev/sda' failed with exit code 1.
Nov 01 07:24:33 alexe systemd-udevd[413]: sda2: Process '/usr/bin/unshare -m /usr/bin/snap auto-import --mount=/dev/sda2' failed with exit code 1.
Nov 01 07:24:34 alexe kernel: thermal thermal_zone16: failed to read out thermal zone (-61)
Nov 01 07:24:34 alexe systemd-udevd[420]: Using default interface naming scheme 'v249'.
Nov 01 07:24:35 alexe NetworkManager[648]: <info>  [1698783875.0722] Read config: /etc/NetworkManager/NetworkManager.conf (lib: 10-dns-resolved.conf, 30-connectivity-kde.conf, no-mac-addr-change.conf) (run: 10-globally-managed-devices.conf) (etc: default-wifi-powersave-on.conf)
Nov 01 07:24:35 alexe systemd[1]: Starting GRUB failed boot detection...
Nov 01 07:24:35 alexe udisksd[686]: failed to load module mdraid: libbd_mdraid.so.2: cannot open shared object file: No such file or directory
Nov 01 07:24:35 alexe systemd[1]: Finished GRUB failed boot detection.
Nov 01 07:24:35 alexe NetworkManager[648]: <info>  [1698783875.1699] settings: (enp3s0): created default wired connection 'Wired connection 1'
Nov 01 07:24:35 alexe dbus-daemon[647]: [system] Activation via systemd failed for unit 'dbus-org.freedesktop.network1.service': Unit dbus-org.freedesktop.network1.service not found.
Nov 01 07:24:35 alexe NetworkManager[648]: <info>  [1698783875.6634] failed to open /run/network/ifstate
Nov 01 07:24:36 alexe sddm[779]: Setting default cursor
Nov 01 07:24:36 alexe systemd[930]: Queued start job for default target Main User Target.
Nov 01 07:24:37 alexe org_kde_powerdevil[1183]: org.kde.powerdevil: org.kde.powerdevil.chargethresholdhelper.getthreshold failed "Charge thresholds are not supported by the kernel for this hardware"
Nov 01 07:24:37 alexe org_kde_powerdevil[1183]: org.kde.powerdevil: org.kde.powerdevil.chargethresholdhelper.getthreshold failed "Charge thresholds are not supported by the kernel for this hardware"
Nov 01 07:24:37 alexe kwin_x11[1084]: kf.config.core: "\"fsrestore1\" - conversion of \"0,0,0,0\" to QRect failed"
Nov 01 07:24:37 alexe kwin_x11[1084]: kf.config.core: "\"fsrestore2\" - conversion of \"0,0,0,0\" to QRect failed"
Nov 01 07:24:37 alexe kwin_x11[1084]: kf.config.core: "\"fsrestore3\" - conversion of \"0,0,0,0\" to QRect failed"
Nov 01 07:24:37 alexe DiscoverNotifie[1336]: Warning: Treating remote fetch error as non-fatal since runtime/org.freedesktop.Platform.GL.default/x86_64/23.08-extra is already installed: No such ref 'runtime/org.freedesktop.Platform.GL.default/x86_64/23.08-extra' in remote flathub
Nov 01 07:24:37 alexe DiscoverNotifie[1336]: Warning: Treating remote fetch error as non-fatal since runtime/org.freedesktop.Platform.GL.default/x86_64/23.08 is already installed: No such ref 'runtime/org.freedesktop.Platform.GL.default/x86_64/23.08' in remote flathub
Nov 01 07:24:37 alexe DiscoverNotifie[1336]: Warning: Treating remote fetch error as non-fatal since runtime/org.freedesktop.Platform.GL.default/x86_64/22.08-extra is already installed: No such ref 'runtime/org.freedesktop.Platform.GL.default/x86_64/22.08-extra' in remote flathub
Nov 01 07:24:37 alexe DiscoverNotifie[1336]: Warning: Treating remote fetch error as non-fatal since runtime/org.freedesktop.Platform.GL.default/x86_64/22.08 is already installed: No such ref 'runtime/org.freedesktop.Platform.GL.default/x86_64/22.08' in remote flathub
Nov 01 07:24:37 alexe DiscoverNotifie[1336]: Warning: Treating remote fetch error as non-fatal since runtime/org.freedesktop.Platform.GL.default/x86_64/21.08 is already installed: No such ref 'runtime/org.freedesktop.Platform.GL.default/x86_64/21.08' in remote flathub
Nov 01 07:24:38 alexe kded5[1083]: Imported file "/usr/share/khotkeys/defaults.khotkeys"
Nov 01 07:24:38 alexe org.gnome.Weath[1459]: g_object_unref: assertion 'G_IS_OBJECT (object)' failed
Nov 01 07:24:39 alexe packagekitd[1432]: pk_package_set_update_severity: assertion 'update_severity == PK_INFO_ENUM_UNKNOWN || update_severity == PK_INFO_ENUM_LOW || update_severity == PK_INFO_ENUM_NORMAL || update_severity == PK_INFO_ENUM_IMPORTANT || update_severity == PK_INFO_ENUM_CRITICAL' failed
Nov 01 07:24:39 alexe packagekitd[1432]: pk_package_set_update_severity: assertion 'update_severity == PK_INFO_ENUM_UNKNOWN || update_severity == PK_INFO_ENUM_LOW || update_severity == PK_INFO_ENUM_NORMAL || update_severity == PK_INFO_ENUM_IMPORTANT || update_severity == PK_INFO_ENUM_CRITICAL' failed
Nov 01 07:24:39 alexe packagekitd[1432]: pk_package_set_update_severity: assertion 'update_severity == PK_INFO_ENUM_UNKNOWN || update_severity == PK_INFO_ENUM_LOW || update_severity == PK_INFO_ENUM_NORMAL || update_severity == PK_INFO_ENUM_IMPORTANT || update_severity == PK_INFO_ENUM_CRITICAL' failed
Nov 01 07:24:39 alexe packagekitd[1432]: pk_package_set_update_severity: assertion 'update_severity == PK_INFO_ENUM_UNKNOWN || update_severity == PK_INFO_ENUM_LOW || update_severity == PK_INFO_ENUM_NORMAL || update_severity == PK_INFO_ENUM_IMPORTANT || update_severity == PK_INFO_ENUM_CRITICAL' failed
Nov 01 07:24:39 alexe packagekitd[1432]: pk_package_set_update_severity: assertion 'update_severity == PK_INFO_ENUM_UNKNOWN || update_severity == PK_INFO_ENUM_LOW || update_severity == PK_INFO_ENUM_NORMAL || update_severity == PK_INFO_ENUM_IMPORTANT || update_severity == PK_INFO_ENUM_CRITICAL' failed
Nov 01 07:24:39 alexe packagekitd[1432]: pk_package_set_update_severity: assertion 'update_severity == PK_INFO_ENUM_UNKNOWN || update_severity == PK_INFO_ENUM_LOW || update_severity == PK_INFO_ENUM_NORMAL || update_severity == PK_INFO_ENUM_IMPORTANT || update_severity == PK_INFO_ENUM_CRITICAL' failed
Nov 01 07:24:39 alexe packagekitd[1432]: pk_package_set_update_severity: assertion 'update_severity == PK_INFO_ENUM_UNKNOWN || update_severity == PK_INFO_ENUM_LOW || update_severity == PK_INFO_ENUM_NORMAL || update_severity == PK_INFO_ENUM_IMPORTANT || update_severity == PK_INFO_ENUM_CRITICAL' failed
Nov 01 07:24:39 alexe packagekitd[1432]: pk_package_set_update_severity: assertion 'update_severity == PK_INFO_ENUM_UNKNOWN || update_severity == PK_INFO_ENUM_LOW || update_severity == PK_INFO_ENUM_NORMAL || update_severity == PK_INFO_ENUM_IMPORTANT || update_severity == PK_INFO_ENUM_CRITICAL' failed
Nov 01 07:24:39 alexe packagekitd[1432]: pk_package_set_update_severity: assertion 'update_severity == PK_INFO_ENUM_UNKNOWN || update_severity == PK_INFO_ENUM_LOW || update_severity == PK_INFO_ENUM_NORMAL || update_severity == PK_INFO_ENUM_IMPORTANT || update_severity == PK_INFO_ENUM_CRITICAL' failed
Nov 01 07:24:39 alexe packagekitd[1432]: pk_package_set_update_severity: assertion 'update_severity == PK_INFO_ENUM_UNKNOWN || update_severity == PK_INFO_ENUM_LOW || update_severity == PK_INFO_ENUM_NORMAL || update_severity == PK_INFO_ENUM_IMPORTANT || update_severity == PK_INFO_ENUM_CRITICAL' failed
Nov 01 07:24:39 alexe packagekitd[1432]: pk_package_set_update_severity: assertion 'update_severity == PK_INFO_ENUM_UNKNOWN || update_severity == PK_INFO_ENUM_LOW || update_severity == PK_INFO_ENUM_NORMAL || update_severity == PK_INFO_ENUM_IMPORTANT || update_severity == PK_INFO_ENUM_CRITICAL' failed
Nov 01 07:24:39 alexe packagekitd[1432]: pk_package_set_update_severity: assertion 'update_severity == PK_INFO_ENUM_UNKNOWN || update_severity == PK_INFO_ENUM_LOW || update_severity == PK_INFO_ENUM_NORMAL || update_severity == PK_INFO_ENUM_IMPORTANT || update_severity == PK_INFO_ENUM_CRITICAL' failed
Nov 01 07:24:39 alexe packagekitd[1432]: pk_package_set_update_severity: assertion 'update_severity == PK_INFO_ENUM_UNKNOWN || update_severity == PK_INFO_ENUM_LOW || update_severity == PK_INFO_ENUM_NORMAL || update_severity == PK_INFO_ENUM_IMPORTANT || update_severity == PK_INFO_ENUM_CRITICAL' failed
Nov 01 07:24:39 alexe packagekitd[1432]: pk_package_set_update_severity: assertion 'update_severity == PK_INFO_ENUM_UNKNOWN || update_severity == PK_INFO_ENUM_LOW || update_severity == PK_INFO_ENUM_NORMAL || update_severity == PK_INFO_ENUM_IMPORTANT || update_severity == PK_INFO_ENUM_CRITICAL' failed
Nov 01 07:24:39 alexe packagekitd[1432]: pk_package_set_update_severity: assertion 'update_severity == PK_INFO_ENUM_UNKNOWN || update_severity == PK_INFO_ENUM_LOW || update_severity == PK_INFO_ENUM_NORMAL || update_severity == PK_INFO_ENUM_IMPORTANT || update_severity == PK_INFO_ENUM_CRITICAL' failed
Nov 01 07:24:39 alexe packagekitd[1432]: pk_package_set_update_severity: assertion 'update_severity == PK_INFO_ENUM_UNKNOWN || update_severity == PK_INFO_ENUM_LOW || update_severity == PK_INFO_ENUM_NORMAL || update_severity == PK_INFO_ENUM_IMPORTANT || update_severity == PK_INFO_ENUM_CRITICAL' failed
Nov 01 07:24:39 alexe packagekitd[1432]: pk_package_set_update_severity: assertion 'update_severity == PK_INFO_ENUM_UNKNOWN || update_severity == PK_INFO_ENUM_LOW || update_severity == PK_INFO_ENUM_NORMAL || update_severity == PK_INFO_ENUM_IMPORTANT || update_severity == PK_INFO_ENUM_CRITICAL' failed
Nov 01 07:24:39 alexe packagekitd[1432]: pk_package_set_update_severity: assertion 'update_severity == PK_INFO_ENUM_UNKNOWN || update_severity == PK_INFO_ENUM_LOW || update_severity == PK_INFO_ENUM_NORMAL || update_severity == PK_INFO_ENUM_IMPORTANT || update_severity == PK_INFO_ENUM_CRITICAL' failed
Nov 01 07:24:39 alexe packagekitd[1432]: pk_package_set_update_severity: assertion 'update_severity == PK_INFO_ENUM_UNKNOWN || update_severity == PK_INFO_ENUM_LOW || update_severity == PK_INFO_ENUM_NORMAL || update_severity == PK_INFO_ENUM_IMPORTANT || update_severity == PK_INFO_ENUM_CRITICAL' failed
Nov 01 07:24:39 alexe packagekitd[1432]: pk_package_set_update_severity: assertion 'update_severity == PK_INFO_ENUM_UNKNOWN || update_severity == PK_INFO_ENUM_LOW || update_severity == PK_INFO_ENUM_NORMAL || update_severity == PK_INFO_ENUM_IMPORTANT || update_severity == PK_INFO_ENUM_CRITICAL' failed
Nov 01 07:24:39 alexe packagekitd[1432]: pk_package_set_update_severity: assertion 'update_severity == PK_INFO_ENUM_UNKNOWN || update_severity == PK_INFO_ENUM_LOW || update_severity == PK_INFO_ENUM_NORMAL || update_severity == PK_INFO_ENUM_IMPORTANT || update_severity == PK_INFO_ENUM_CRITICAL' failed
Nov 01 07:24:39 alexe packagekitd[1432]: pk_package_set_update_severity: assertion 'update_severity == PK_INFO_ENUM_UNKNOWN || update_severity == PK_INFO_ENUM_LOW || update_severity == PK_INFO_ENUM_NORMAL || update_severity == PK_INFO_ENUM_IMPORTANT || update_severity == PK_INFO_ENUM_CRITICAL' failed
Nov 01 07:24:39 alexe packagekitd[1432]: pk_package_set_update_severity: assertion 'update_severity == PK_INFO_ENUM_UNKNOWN || update_severity == PK_INFO_ENUM_LOW || update_severity == PK_INFO_ENUM_NORMAL || update_severity == PK_INFO_ENUM_IMPORTANT || update_severity == PK_INFO_ENUM_CRITICAL' failed
Nov 01 07:24:39 alexe packagekitd[1432]: pk_package_set_update_severity: assertion 'update_severity == PK_INFO_ENUM_UNKNOWN || update_severity == PK_INFO_ENUM_LOW || update_severity == PK_INFO_ENUM_NORMAL || update_severity == PK_INFO_ENUM_IMPORTANT || update_severity == PK_INFO_ENUM_CRITICAL' failed
Nov 01 07:24:39 alexe packagekitd[1432]: pk_package_set_update_severity: assertion 'update_severity == PK_INFO_ENUM_UNKNOWN || update_severity == PK_INFO_ENUM_LOW || update_severity == PK_INFO_ENUM_NORMAL || update_severity == PK_INFO_ENUM_IMPORTANT || update_severity == PK_INFO_ENUM_CRITICAL' failed
Nov 01 07:24:39 alexe packagekitd[1432]: pk_package_set_update_severity: assertion 'update_severity == PK_INFO_ENUM_UNKNOWN || update_severity == PK_INFO_ENUM_LOW || update_severity == PK_INFO_ENUM_NORMAL || update_severity == PK_INFO_ENUM_IMPORTANT || update_severity == PK_INFO_ENUM_CRITICAL' failed
Nov 01 07:24:39 alexe packagekitd[1432]: pk_package_set_update_severity: assertion 'update_severity == PK_INFO_ENUM_UNKNOWN || update_severity == PK_INFO_ENUM_LOW || update_severity == PK_INFO_ENUM_NORMAL || update_severity == PK_INFO_ENUM_IMPORTANT || update_severity == PK_INFO_ENUM_CRITICAL' failed
Nov 01 07:24:39 alexe packagekitd[1432]: pk_package_set_update_severity: assertion 'update_severity == PK_INFO_ENUM_UNKNOWN || update_severity == PK_INFO_ENUM_LOW || update_severity == PK_INFO_ENUM_NORMAL || update_severity == PK_INFO_ENUM_IMPORTANT || update_severity == PK_INFO_ENUM_CRITICAL' failed
Nov 01 07:24:39 alexe packagekitd[1432]: pk_package_set_update_severity: assertion 'update_severity == PK_INFO_ENUM_UNKNOWN || update_severity == PK_INFO_ENUM_LOW || update_severity == PK_INFO_ENUM_NORMAL || update_severity == PK_INFO_ENUM_IMPORTANT || update_severity == PK_INFO_ENUM_CRITICAL' failed
Nov 01 07:24:39 alexe NetworkManager[648]: <info>  [1698783879.8613] policy: set 'M3200-1185' (wlp0s20f3) as default for IPv4 routing and DNS
Nov 01 07:24:39 alexe systemd-resolved[608]: wlp0s20f3: Bus client set default route setting: yes
Nov 01 07:24:40 alexe packagekitd[1432]: pk_package_set_update_severity: assertion 'update_severity == PK_INFO_ENUM_UNKNOWN || update_severity == PK_INFO_ENUM_LOW || update_severity == PK_INFO_ENUM_NORMAL || update_severity == PK_INFO_ENUM_IMPORTANT || update_severity == PK_INFO_ENUM_CRITICAL' failed
Nov 01 07:24:40 alexe packagekitd[1432]: pk_package_set_update_severity: assertion 'update_severity == PK_INFO_ENUM_UNKNOWN || update_severity == PK_INFO_ENUM_LOW || update_severity == PK_INFO_ENUM_NORMAL || update_severity == PK_INFO_ENUM_IMPORTANT || update_severity == PK_INFO_ENUM_CRITICAL' failed
Nov 01 07:24:40 alexe packagekitd[1432]: pk_package_set_update_severity: assertion 'update_severity == PK_INFO_ENUM_UNKNOWN || update_severity == PK_INFO_ENUM_LOW || update_severity == PK_INFO_ENUM_NORMAL || update_severity == PK_INFO_ENUM_IMPORTANT || update_severity == PK_INFO_ENUM_CRITICAL' failed
Nov 01 07:24:40 alexe packagekitd[1432]: pk_package_set_update_severity: assertion 'update_severity == PK_INFO_ENUM_UNKNOWN || update_severity == PK_INFO_ENUM_LOW || update_severity == PK_INFO_ENUM_NORMAL || update_severity == PK_INFO_ENUM_IMPORTANT || update_severity == PK_INFO_ENUM_CRITICAL' failed
Nov 01 07:24:40 alexe packagekitd[1432]: pk_package_set_update_severity: assertion 'update_severity == PK_INFO_ENUM_UNKNOWN || update_severity == PK_INFO_ENUM_LOW || update_severity == PK_INFO_ENUM_NORMAL || update_severity == PK_INFO_ENUM_IMPORTANT || update_severity == PK_INFO_ENUM_CRITICAL' failed
Nov 01 07:24:40 alexe packagekitd[1432]: pk_package_set_update_severity: assertion 'update_severity == PK_INFO_ENUM_UNKNOWN || update_severity == PK_INFO_ENUM_LOW || update_severity == PK_INFO_ENUM_NORMAL || update_severity == PK_INFO_ENUM_IMPORTANT || update_severity == PK_INFO_ENUM_CRITICAL' failed
Nov 01 07:24:40 alexe packagekitd[1432]: pk_package_set_update_severity: assertion 'update_severity == PK_INFO_ENUM_UNKNOWN || update_severity == PK_INFO_ENUM_LOW || update_severity == PK_INFO_ENUM_NORMAL || update_severity == PK_INFO_ENUM_IMPORTANT || update_severity == PK_INFO_ENUM_CRITICAL' failed
Nov 01 07:24:40 alexe packagekitd[1432]: pk_package_set_update_severity: assertion 'update_severity == PK_INFO_ENUM_UNKNOWN || update_severity == PK_INFO_ENUM_LOW || update_severity == PK_INFO_ENUM_NORMAL || update_severity == PK_INFO_ENUM_IMPORTANT || update_severity == PK_INFO_ENUM_CRITICAL' failed
Nov 01 07:24:40 alexe packagekitd[1432]: pk_package_set_update_severity: assertion 'update_severity == PK_INFO_ENUM_UNKNOWN || update_severity == PK_INFO_ENUM_LOW || update_severity == PK_INFO_ENUM_NORMAL || update_severity == PK_INFO_ENUM_IMPORTANT || update_severity == PK_INFO_ENUM_CRITICAL' failed
Nov 01 07:24:40 alexe packagekitd[1432]: pk_package_set_update_severity: assertion 'update_severity == PK_INFO_ENUM_UNKNOWN || update_severity == PK_INFO_ENUM_LOW || update_severity == PK_INFO_ENUM_NORMAL || update_severity == PK_INFO_ENUM_IMPORTANT || update_severity == PK_INFO_ENUM_CRITICAL' failed
Nov 01 07:24:40 alexe packagekitd[1432]: pk_package_set_update_severity: assertion 'update_severity == PK_INFO_ENUM_UNKNOWN || update_severity == PK_INFO_ENUM_LOW || update_severity == PK_INFO_ENUM_NORMAL || update_severity == PK_INFO_ENUM_IMPORTANT || update_severity == PK_INFO_ENUM_CRITICAL' failed
Nov 01 07:24:40 alexe packagekitd[1432]: pk_package_set_update_severity: assertion 'update_severity == PK_INFO_ENUM_UNKNOWN || update_severity == PK_INFO_ENUM_LOW || update_severity == PK_INFO_ENUM_NORMAL || update_severity == PK_INFO_ENUM_IMPORTANT || update_severity == PK_INFO_ENUM_CRITICAL' failed
Nov 01 07:24:40 alexe packagekitd[1432]: pk_package_set_update_severity: assertion 'update_severity == PK_INFO_ENUM_UNKNOWN || update_severity == PK_INFO_ENUM_LOW || update_severity == PK_INFO_ENUM_NORMAL || update_severity == PK_INFO_ENUM_IMPORTANT || update_severity == PK_INFO_ENUM_CRITICAL' failed
Nov 01 07:24:40 alexe packagekitd[1432]: pk_package_set_update_severity: assertion 'update_severity == PK_INFO_ENUM_UNKNOWN || update_severity == PK_INFO_ENUM_LOW || update_severity == PK_INFO_ENUM_NORMAL || update_severity == PK_INFO_ENUM_IMPORTANT || update_severity == PK_INFO_ENUM_CRITICAL' failed
Nov 01 07:24:40 alexe packagekitd[1432]: pk_package_set_update_severity: assertion 'update_severity == PK_INFO_ENUM_UNKNOWN || update_severity == PK_INFO_ENUM_LOW || update_severity == PK_INFO_ENUM_NORMAL || update_severity == PK_INFO_ENUM_IMPORTANT || update_severity == PK_INFO_ENUM_CRITICAL' failed
Nov 01 07:24:40 alexe packagekitd[1432]: pk_package_set_update_severity: assertion 'update_severity == PK_INFO_ENUM_UNKNOWN || update_severity == PK_INFO_ENUM_LOW || update_severity == PK_INFO_ENUM_NORMAL || update_severity == PK_INFO_ENUM_IMPORTANT || update_severity == PK_INFO_ENUM_CRITICAL' failed
Nov 01 07:24:40 alexe packagekitd[1432]: pk_package_set_update_severity: assertion 'update_severity == PK_INFO_ENUM_UNKNOWN || update_severity == PK_INFO_ENUM_LOW || update_severity == PK_INFO_ENUM_NORMAL || update_severity == PK_INFO_ENUM_IMPORTANT || update_severity == PK_INFO_ENUM_CRITICAL' failed
Nov 01 07:24:40 alexe packagekitd[1432]: pk_package_set_update_severity: assertion 'update_severity == PK_INFO_ENUM_UNKNOWN || update_severity == PK_INFO_ENUM_LOW || update_severity == PK_INFO_ENUM_NORMAL || update_severity == PK_INFO_ENUM_IMPORTANT || update_severity == PK_INFO_ENUM_CRITICAL' failed
Nov 01 07:24:40 alexe packagekitd[1432]: pk_package_set_update_severity: assertion 'update_severity == PK_INFO_ENUM_UNKNOWN || update_severity == PK_INFO_ENUM_LOW || update_severity == PK_INFO_ENUM_NORMAL || update_severity == PK_INFO_ENUM_IMPORTANT || update_severity == PK_INFO_ENUM_CRITICAL' failed
Nov 01 07:24:40 alexe packagekitd[1432]: pk_package_set_update_severity: assertion 'update_severity == PK_INFO_ENUM_UNKNOWN || update_severity == PK_INFO_ENUM_LOW || update_severity == PK_INFO_ENUM_NORMAL || update_severity == PK_INFO_ENUM_IMPORTANT || update_severity == PK_INFO_ENUM_CRITICAL' failed
Nov 01 07:24:40 alexe packagekitd[1432]: pk_package_set_update_severity: assertion 'update_severity == PK_INFO_ENUM_UNKNOWN || update_severity == PK_INFO_ENUM_LOW || update_severity == PK_INFO_ENUM_NORMAL || update_severity == PK_INFO_ENUM_IMPORTANT || update_severity == PK_INFO_ENUM_CRITICAL' failed
Nov 01 07:24:40 alexe packagekitd[1432]: pk_package_set_update_severity: assertion 'update_severity == PK_INFO_ENUM_UNKNOWN || update_severity == PK_INFO_ENUM_LOW || update_severity == PK_INFO_ENUM_NORMAL || update_severity == PK_INFO_ENUM_IMPORTANT || update_severity == PK_INFO_ENUM_CRITICAL' failed
Nov 01 07:24:40 alexe packagekitd[1432]: pk_package_set_update_severity: assertion 'update_severity == PK_INFO_ENUM_UNKNOWN || update_severity == PK_INFO_ENUM_LOW || update_severity == PK_INFO_ENUM_NORMAL || update_severity == PK_INFO_ENUM_IMPORTANT || update_severity == PK_INFO_ENUM_CRITICAL' failed
Nov 01 07:24:40 alexe packagekitd[1432]: pk_package_set_update_severity: assertion 'update_severity == PK_INFO_ENUM_UNKNOWN || update_severity == PK_INFO_ENUM_LOW || update_severity == PK_INFO_ENUM_NORMAL || update_severity == PK_INFO_ENUM_IMPORTANT || update_severity == PK_INFO_ENUM_CRITICAL' failed
Nov 01 07:24:40 alexe packagekitd[1432]: pk_package_set_update_severity: assertion 'update_severity == PK_INFO_ENUM_UNKNOWN || update_severity == PK_INFO_ENUM_LOW || update_severity == PK_INFO_ENUM_NORMAL || update_severity == PK_INFO_ENUM_IMPORTANT || update_severity == PK_INFO_ENUM_CRITICAL' failed
Nov 01 07:24:40 alexe packagekitd[1432]: pk_package_set_update_severity: assertion 'update_severity == PK_INFO_ENUM_UNKNOWN || update_severity == PK_INFO_ENUM_LOW || update_severity == PK_INFO_ENUM_NORMAL || update_severity == PK_INFO_ENUM_IMPORTANT || update_severity == PK_INFO_ENUM_CRITICAL' failed
Nov 01 07:24:40 alexe packagekitd[1432]: pk_package_set_update_severity: assertion 'update_severity == PK_INFO_ENUM_UNKNOWN || update_severity == PK_INFO_ENUM_LOW || update_severity == PK_INFO_ENUM_NORMAL || update_severity == PK_INFO_ENUM_IMPORTANT || update_severity == PK_INFO_ENUM_CRITICAL' failed
Nov 01 07:24:40 alexe packagekitd[1432]: pk_package_set_update_severity: assertion 'update_severity == PK_INFO_ENUM_UNKNOWN || update_severity == PK_INFO_ENUM_LOW || update_severity == PK_INFO_ENUM_NORMAL || update_severity == PK_INFO_ENUM_IMPORTANT || update_severity == PK_INFO_ENUM_CRITICAL' failed
Nov 01 07:24:40 alexe packagekitd[1432]: pk_package_set_update_severity: assertion 'update_severity == PK_INFO_ENUM_UNKNOWN || update_severity == PK_INFO_ENUM_LOW || update_severity == PK_INFO_ENUM_NORMAL || update_severity == PK_INFO_ENUM_IMPORTANT || update_severity == PK_INFO_ENUM_CRITICAL' failed
Nov 01 07:24:41 alexe NetworkManager[648]: <info>  [1698783881.5231] policy: set 'M3200-1185' (wlp0s20f3) as default for IPv6 routing and DNS
Nov 01 07:24:42 alexe baloo_file_extractor[1721]: kf.baloo: "/home/alexe/afolders/cktwsbhx.default-release-20230302-1745/ImapMail/imap.gmail.com/New-Home.sbd/Rc_Clubs" id seems to have changed. Perhaps baloo was not running, and this file was deleted + re-created
Nov 01 07:24:43 alexe ntfs-3g[1731]: Mount options: nodev,nosuid,uhelper=udisks2,allow_other,nonempty,relatime,rw,default_permissions,fsname=/dev/sda2,blkdev,blksize=4096
Nov 01 07:24:45 alexe baloo_file_extractor[1721]: kf.baloo: "/home/alexe/afolders/cktwsbhx.default-release-20230302-1745/ImapMail/imap.gmail.com/New-Home.sbd/Travel" id seems to have changed. Perhaps baloo was not running, and this file was deleted + re-created
Nov 01 07:24:45 alexe baloo_file_extractor[1721]: kf.baloo: "/home/alexe/afolders/cktwsbhx.default-release-20230302-1745/ImapMail/imap.gmail.com/New-Home.sbd/web_things" id seems to have changed. Perhaps baloo was not running, and this file was deleted + re-created
Nov 01 07:24:55 alexe kate[1756]: kf.sonnet.clients.hspell: HSpellDict::HSpellDict: Init failed
Thanks again
 
Old 10-31-2023, 03:36 PM   #14
Xeratul
Senior Member
 
Registered: Jun 2006
Location: UNIX
Distribution: FreeBSD
Posts: 2,659

Rep: Reputation: 255Reputation: 255Reputation: 255
Quote:
Originally Posted by alex4buba View Post
I get errors during boot time and am unable to see what they are so as to try and attend to it. Checking the various log files is not much help.

Is there a way to record the process from power ON until end of the boot process that I can later watch the clip in slow motion?

Thank you
Code:
qemu-system-x86_64 -hda /dev/sda 

ffmpeg  -f ........ .avi
 
Old 10-31-2023, 03:42 PM   #15
alex4buba
Member
 
Registered: Jul 2020
Posts: 624

Original Poster
Rep: Reputation: Disabled
Quote:
Originally Posted by Xeratul View Post
Code:
qemu-system-x86_64 -hda /dev/sda 

ffmpeg  -f ........ .avi
Sorry, what is
..... what command should I execute?

Thanks
 
  


Reply
Page 1 of 2 1 2

Tags
boot err msg., kde plasma 5, recording, video



Posting Rules
You may not post new threads
You may not post replies
You may not post attachments
You may not edit your posts
BB code is On
Smilies are On
[IMG] code is Off
HTML code is Off


Similar Threads
Thread Thread Starter Forum Replies Last Post
LXer: Solus Readies KDE Plasma Edition Testing ISO with Latest KDE Plasma 5.14 Desktop LXer Syndicated Linux News 0 10-25-2018 03:03 PM
LXer: KDE Plasma 5.13 Desktop Reaches End of Life, KDE Plasma 5.14 Arrives October 9 LXer Syndicated Linux News 0 09-15-2018 10:30 PM
LXer: KDE Plasma Media Center 1.1 Up To RC Stage LXer Syndicated Linux News 0 08-11-2013 08:41 PM
Half of my applications are broken. I am using Gentoo stage 1 on 3 nptl (stage 1.5) dragonslay Linux - Games 3 04-01-2005 05:23 PM
Gentoo: Stage 1, Stage 2, or Stage 3 skorpi0wn Linux - Distributions 3 03-01-2005 07:47 PM

LinuxQuestions.org > Forums > Linux Forums > Linux - Software

All times are GMT -5. The time now is 10:00 PM.

Contact Us - Advertising Info - Rules - Privacy - LQ Merchandise - Donations - Contributing Member - LQ Sitemap -
Main Menu
Advertisement
My LQ
Write for LQ
LinuxQuestions.org is looking for people interested in writing Editorials, Articles, Reviews, and more. If you'd like to contribute content, let us know.
Main Menu
Syndicate
RSS1  Latest Threads
RSS1  LQ News
Twitter: @linuxquestions
Open Source Consulting | Domain Registration