Using Garuda Kwin broken, link has most of the inormation given, the YouTube video has more information

I can log into the guest account, as I cant change the scailer, as it needs a restart, and such settings dont scail, the userface is to small to do mutch in the guest account, but it works apperntly with out issuse.

Before this, the login screen use to load flawlessly but now I see a bright screen for about a second, then it loads, after log in, I am lucky to see the background if it were not for the welcome screen the log I took would not have been possible, without your aid and the command line.

For reasons beyond me, I cant Cntrl alt f2 into the command line, it loads, but will not let me log in, no clue why. Though I can summon it on the desktop and get root that way, as I tried Sudo update.... that was perhaps more invasive than I needed, to no regard did it aid me.

Snapshot was of no help, the last thing I did was watch some shows in the browser, I put it to sleep, and stowed my keyboard under my coffee table.

The last week I have had to hard shut down my pc with the power button due to it not waking up, the newest change is that I have had to use a tv instead of my monitor as the cable broke moving an old crt down the stairs, cents this change, wake up has been shotty. using an LG smart tv.

Disabled, writing disability. Hope this has been of help. and I hope you can help me.

Perhaps the reason no one has responded is that you have failed to provide an inxi -Faz terminal output. If you can't get to a TTY to enter the command, then the output can be gotten from a live boot disk with the same version of Garuda as you have installed.

Also, that's a real dogs breakfast of issues you've got going on there. It would have been far better to have dealt with issues separately when they occurred, such as your hard shutdown because of a freezing issue. This can cause real problems so you should scan your file system for errors and run smartmon on your drives. You should probably also run a memory testing utility as your problems sound so drastic that hardware might be at fault.

Try doing what I suggested and report back with some thorough explanations of your investigations and their results. Tests can be run from live disks to diagnose if your systems hardware is an issue. Be sure to run the thorough memory test not the quick one. Post as many relevant outputs as possible

Please do not post terminal outputs as pictures or video. Only post outputs in a text format. Terminal outputs may be posted from run level three using termbin.
Search the forum for "run level three termbin" if you need assistance/instructions for posting outputs from a TTY.

Forum assistants are going to need logs and your system info at the minumum to be able to provide any diagnosis of what your issue may be.

Good luck to you.

[email protected] in ~  
╰─λ inxi -Faz
System:    Kernel: 5.14.16-zen1-1-zen x86_64 bits: 64 compiler: gcc v: 11.1.0
parameters: BOOT_IMAGE=/@/boot/vmlinuz-linux-zen root=UUID=eb336417-47ad-47a4-a2db-7087f96c6806
rw [email protected] quiet splash rd.udev.log_priority=3 vt.global_cursor_default=0
systemd.unified_cgroup_hierarchy=1 loglevel=3
Desktop: KDE Plasma 5.23.3 tk: Qt 5.15.2 wm: kwin_x11 vt: 1 dm: SDDM Distro: Garuda Linux
base: Arch Linux
Machine:   Type: Desktop System: Alienware product: Aurora-R4 v: 00 serial: <filter> Chassis: type: 3
v: 00 serial: <filter>
Mobo: Alienware model: 0FPV4P v: A00 serial: <filter> BIOS: Alienware v: A11 date: 11/26/2013
Battery:   Device-1: sony_controller_battery_00:22:68:de:df:b9 model: N/A serial: N/A charge: N/A
status: Charging
CPU:       Info: Quad Core model: Intel Core i7-3820 bits: 64 type: MT MCP arch: Sandy Bridge family: 6
model-id: 2D (45) stepping: 7 microcode: 71A cache: L2: 10 MiB
flags: avx lm nx pae sse sse2 sse3 sse4_1 sse4_2 ssse3 vmx bogomips: 57467
Speed: 3789 MHz min/max: 1200/4200 MHz Core speeds (MHz): 1: 3789 2: 3881 3: 3891 4: 2008
5: 3891 6: 3327 7: 3891 8: 3705
Vulnerabilities: Type: itlb_multihit status: KVM: VMX disabled
Type: l1tf mitigation: PTE Inversion; VMX: conditional cache flushes, SMT vulnerable
Type: mds mitigation: Clear CPU buffers; SMT vulnerable
Type: meltdown mitigation: PTI
Type: spec_store_bypass mitigation: Speculative Store Bypass disabled via prctl
Type: spectre_v1 mitigation: usercopy/swapgs barriers and __user pointer sanitization
Type: spectre_v2
mitigation: Full generic retpoline, IBPB: conditional, IBRS_FW, STIBP: conditional, RSB filling
Type: srbds status: Not affected
Type: tsx_async_abort status: Not affected
Graphics:  Device-1: AMD Navi 10 [Radeon RX 5600 OEM/5600 XT / 5700/5700 XT] vendor: Gigabyte
driver: amdgpu v: kernel bus-ID: 04:00.0 chip-ID: 1002:731f class-ID: 0300
Device-2: Microdia MSI Starcam Racer type: USB driver: snd-usb-audio,uvcvideo bus-ID: 2-1.1.1:6
chip-ID: 0c45:62e0 class-ID: 0102
Display: x11 server: X.Org compositor: kwin_x11 driver: loaded: amdgpu,ati
unloaded: modesetting,radeon alternate: fbdev,vesa display-ID: :0 screens: 1
Screen-1: 0 s-res: 3840x2160 s-dpi: 61 s-size: 1600x900mm (63.0x35.4") s-diag: 1836mm (72.3")
Monitor-1: HDMI-A-0 res: 3840x2160 hz: 60 dpi: 61 size: 1600x900mm (63.0x35.4")
diag: 1836mm (72.3")
OpenGL: renderer: AMD Radeon RX 5600 XT (NAVI10 DRM 3.42.0 5.14.16-zen1-1-zen LLVM 12.0.1)
v: 4.6 Mesa 21.2.4 direct render: Yes
Audio:     Device-1: Intel C600/X79 series High Definition Audio vendor: Dell driver: snd_hda_intel
v: kernel bus-ID: 00:1b.0 chip-ID: 8086:1d20 class-ID: 0403
Device-2: AMD Navi 10 HDMI Audio driver: snd_hda_intel v: kernel bus-ID: 04:00.1
chip-ID: 1002:ab38 class-ID: 0403
Device-3: Microdia MSI Starcam Racer type: USB driver: snd-usb-audio,uvcvideo bus-ID: 2-1.1.1:6
chip-ID: 0c45:62e0 class-ID: 0102
Device-4: Sony DualShock 4 [CUH-ZCT2x] type: USB driver: snd-usb-audio,sony,usbhid
bus-ID: 2-1.2:4 chip-ID: 054c:09cc class-ID: 0300
Sound Server-1: ALSA v: k5.14.16-zen1-1-zen running: yes
Sound Server-2: sndio v: N/A running: no
Sound Server-3: JACK v: 1.9.19 running: no
Sound Server-4: PulseAudio v: 15.0 running: yes
Sound Server-5: PipeWire v: 0.3.39 running: yes
Network:   Device-1: Realtek RTL8111/8168/8411 PCI Express Gigabit Ethernet vendor: Dell driver: r8169
v: kernel port: d000 bus-ID: 07:00.0 chip-ID: 10ec:8168 class-ID: 0200
IF: enp7s0 state: up speed: 100 Mbps duplex: full mac: <filter>
Device-2: Micro Star MS-3871 802.11bgn Wireless Module [Ralink RT8070] type: USB
driver: rt2800usb bus-ID: 2-1.6.2:13 chip-ID: 0db0:3871 class-ID: 0000 serial: <filter>
IF: wlp0s29u1u6u2 state: down mac: <filter>
IF-ID-1: anbox0 state: down mac: <filter>
Bluetooth: Device-1: Micro Star type: USB driver: btusb v: 0.8 bus-ID: 2-1.6.1:12 chip-ID: 0db0:a871
class-ID: e001
Report: bt-adapter ID: hci0 rfk-id: 0 state: up address: <filter>
Drives:    Local Storage: total: 2.73 TiB used: 373.13 GiB (13.4%)
SMART Message: Unable to run smartctl. Root privileges required.
ID-1: /dev/sda maj-min: 8:0 vendor: Western Digital model: WD10EZEX-60ZF5A0 size: 931.51 GiB
block-size: physical: 4096 B logical: 512 B speed: 6.0 Gb/s type: HDD rpm: 7200
serial: <filter> rev: 0A80 scheme: MBR
ID-2: /dev/sdb maj-min: 8:16 vendor: Western Digital model: WD10EZEX-08WN4A0 size: 931.51 GiB
block-size: physical: 4096 B logical: 512 B speed: 3.0 Gb/s type: HDD rpm: 7200
serial: <filter> rev: 1A02 scheme: MBR
ID-3: /dev/sdc maj-min: 8:32 vendor: Western Digital model: WD10EZEX-60ZF5A0 size: 931.51 GiB
block-size: physical: 4096 B logical: 512 B speed: 3.0 Gb/s type: HDD rpm: 7200
serial: <filter> rev: 0A80 scheme: MBR
Partition: ID-1: / raw-size: 931.51 GiB size: 931.51 GiB (100.00%) used: 373.13 GiB (40.1%) fs: btrfs
dev: /dev/sda1 maj-min: 8:1
ID-2: /home raw-size: 931.51 GiB size: 931.51 GiB (100.00%) used: 373.13 GiB (40.1%) fs: btrfs
dev: /dev/sda1 maj-min: 8:1
ID-3: /var/log raw-size: 931.51 GiB size: 931.51 GiB (100.00%) used: 373.13 GiB (40.1%)
fs: btrfs dev: /dev/sda1 maj-min: 8:1
ID-4: /var/tmp raw-size: 931.51 GiB size: 931.51 GiB (100.00%) used: 373.13 GiB (40.1%)
fs: btrfs dev: /dev/sda1 maj-min: 8:1
Swap:      Kernel: swappiness: 133 (default 60) cache-pressure: 100 (default)
ID-1: swap-1 type: zram size: 11.61 GiB used: 2.5 MiB (0.0%) priority: 100 dev: /dev/zram0
Sensors:   System Temperatures: cpu: 52.0 C mobo: N/A gpu: amdgpu temp: 55.0 C mem: 56.0 C
Fan Speeds (RPM): N/A gpu: amdgpu fan: 0
Info:      Processes: 361 Uptime: 29m wakeups: 1 Memory: 11.61 GiB used: 4.94 GiB (42.6%) Init: systemd
v: 249 tool: systemctl Compilers: gcc: 11.1.0 clang: 12.0.1 Packages: pacman: 1798 lib: 545
Shell: fish v: 3.3.1 default: Bash v: 5.1.8 running-in: konsole inxi: 3.3.08

The battle to get that into this check box was worse than the time I tried to pull a rotten tooth from my mouth, though thankfully this did not end in my failure of nerve to finish the job, or perhaps god was feeling pitting and stopped me from ripping my hair from my head.

Also just getting my browser open was a merical by itself, even the notepad... Had to use the terminal to open my file manager, not even with a commend, was a right-click, then I had to make a new text doc, then I could open it and fill it with text.

I just want my computer back, I miss her dearly.

Oh and mem test was the 1st thing I ran, no errors detected. Windows runs fin, even if it's a bit trashed from the loss of a hard drive a year or so ago. >_> Mostly just a very sluggish boot up as it looks for missing logs or something I assume, but it runs fine after ten or so minutes for a start-up.

Steam ran after i typed it into terminal, tried to load idtech game, umb dont think it will run

Going to shut down for now

Use last working snapshot.

Read, please

and edit you post # 3.


You have such a mess going on that a reinstall might be the quickest way to restore your computer to a proper working state. I almost never tell users that, because the user learns nothing about repairing their own system that way. You have so many issues that this may be one of the rare instances where it might be a good alternative.

Having said that, there are some things you might want to try before giving up on repairing things.

Have you booted from a live boot disk yet? Do you have issues still when in a Garuda live environment?

Have you tried creating a new user account? If this is possible, does a new account improve things.

Have you tested the effect when only one display monitor is used?

Have you tried restoring a snapshot from the terminal or chroot? I am going to assume this is an older install and you are still using timeshift (as you did not identify if you were using timeshift or snapper).

This ^^^ tells us absolutely nothing about why this failed.

Did timeshift fail to start?
Were there error messages (please provide) from the restore attempt?
Did timeshift start, but could not successfully restore a snapshot?
Did timeshift perform a restore, but your system was still borked?
If you actually could restore from a snapshot, did you test all earlier snapshots?

If you were using snapper to restore a snapshot please describe fully what happened when you attempted a restore.

Have you checked the config file for sddm? If it doesn't look correct, restore it to an earlier state. I always create a duplicate of important system config files with a .bak extension so that I can restore manually in cases where a restore is not functional. Perhaps you might want to consider making full backups of root and home in the future to avoid the worst case senario you now find yourself in. Snapshots are not proper backups and they cannot fully restore your system as your config files in your home directory are not included. Snapshots are not a comprehensive backup system. You really should implement a full backup regime if you are unable to correct issues yourself.

The scant information you have provided really doesn't give assistants much to go on to identify a cause here.

You have still provided no logs of error messages to narrow down the possibilities. Please post some logs of the errors from your journal if you desire further assistance.

Unfortunately, it sounds like so many different issues here, that identifying a cause may be a very long and painful process. You may want to consider a reinstall in this case, because forum assistants will have a very hard time sorting this mess with the information you were able to provide so far.

Regarding your wake from sleep problem when you switched your monitor to a TV. Not all older TV's work properly waking from sleep when triggered by a Linux computer. There are ways of working around this, but you'll need to do your own research.

In the future please try to deal with problems individually as they arise with their own individual help requests. Creating a help request with a litany of problems generally is not very productive and makes things very difficult for forum assistants. It also makes things very difficult for users trying to find solutions to similar issues in a very long thread dealing with a bunch of different issues.

Good luck sorting your problems.

1 Like

How do i get error logs?

Timeshift was just broked, tried all of them, no luck.

I would assume making a new user would work, as the guest account works without issue. The x enviroment boots, and everything runs well.

No clue what snapper is, but as iaid time shift was no help, i could shift with out issue, but its still the same issue.

Was hoping reinstalling the x environment could help, but that will be hard as the F2 terminal wont let me log in.

I cun cntrl t a terminal into existence though.

Create a new user account.

Enter in terminal:

man journalctl

Also see:

Also search for:

boot to run level 3


journalctl - Query the systemd journal

journalctl [OPTIONS...] [MATCHES...]

journalctl may be used to query the contents of the systemd(1) journal as written by systemd-

If called without parameters, it will show the full contents of the journal, starting with the
oldest entry collected.

If one or more match arguments are passed, the output is filtered accordingly. A match is in the
format "FIELD=VALUE", e.g.  "_SYSTEMD_UNIT=httpd.service", referring to the components of a
structured journal entry. See systemd.journal-fields(7) for a list of well-known fields. If multiple
matches are specified matching different fields, the log entries are filtered by both, i.e. the
resulting output will show only entries matching all the specified matches of this kind. If two
matches apply to the same field, then they are automatically matched as alternatives, i.e. the
resulting output will show entries matching any of the specified matches for the same field.
Finally, the character "+" may appear as a separate word between other terms on the command line.
This causes all matches before and after to be combined in a disjunction (i.e. logical OR).

It is also possible to filter the entries by specifying an absolute file path as an argument. The
file path may be a file or a symbolic link and the file must exist at the time of the query. If a
Manual page journalctl(1) line 1/650 5% (press h for help or q to quit)

It is also possible to filter the entries by specifying an absolute file path as an argument. The
file path may be a file or a symbolic link and the file must exist at the time of the query. If a
file path refers to an executable binary, an "_EXE=" match for the canonicalized binary path is
added to the query. If a file path refers to an executable script, a "_COMM=" match for the script
name is added to the query. If a file path refers to a device node, "_KERNEL_DEVICE=" matches for
the kernel name of the device and for each of its ancestor devices is added to the query. Symbolic
links are dereferenced, kernel names are synthesized, and parent devices are identified from the
environment at the time of the query. In general, a device node is the best proxy for an actual
device, as log entries do not usually contain fields that identify an actual device. For the
resulting log entries to be correct for the actual device, the relevant parts of the environment at
the time the entry was logged, in particular the actual device corresponding to the device node,
must have been the same as those at the time of the query. Because device nodes generally change
their corresponding devices across reboots, specifying a device node path causes the resulting
entries to be restricted to those from the current boot.

Additional constraints may be added using options --boot, --unit=, etc., to further limit what
entries will be shown (logical AND).

Output is interleaved from all accessible journal files, whether they are rotated or currently being
written, and regardless of whether they belong to the system itself or are accessible user journals.

The set of journal files which will be used can be modified using the --user, --system, --directory,
and --file options, see below.
Manual page journalctl(1) line 22/650 8% 

All users are granted access to their private per-user journals. However, by default, only root and
users who are members of a few special groups are granted access to the system journal and the
journals of other users. Members of the groups "systemd-journal", "adm", and "wheel" can read all
journal files. Note that the two latter groups traditionally have additional privileges specified by
the distribution. Members of the "wheel" group can often perform administrative tasks.

The output is paged through less by default, and long lines are "truncated" to screen width. The
hidden part can be viewed by using the left-arrow and right-arrow keys. Paging can be disabled; see
the --no-pager option and the "Environment" section below.

When outputting to a tty, lines are colored according to priority: lines of level ERROR and higher
are colored red; lines of level NOTICE and higher are highlighted; lines of level DEBUG are colored
lighter grey; other lines are displayed normally.

The following options are understood:

--no-full, --full, -l
Ellipsize fields when they do not fit in available columns. The default is to show full fields,
allowing them to wrap or be truncated by the pager, if one is used.

The old options -l/--full are not useful anymore, except to undo --no-full.

Manual page journalctl(1) line 46/650 12% 

-a, --all
Show all fields in full, even if they include unprintable characters or are very long. By
default, fields with unprintable characters are abbreviated as "blob data". (Note that the pager
may escape unprintable characters again.)

-f, --follow
Show only the most recent journal entries, and continuously print new entries as they are
appended to the journal.

-e, --pager-end
Immediately jump to the end of the journal inside the implied pager tool. This implies -n1000 to
guarantee that the pager will not buffer logs of unbounded size. This may be overridden with an
explicit -n with some other numeric value, while -nall will disable this cap. Note that this
option is only supported for the less(1) pager.

-n, --lines=
Show the most recent journal events and limit the number of events shown. If --follow is used,
this option is implied. The argument is a positive integer or "all" to disable line limiting.
The default value is 10 if no argument is given.

Show all stored output lines, even in follow mode. Undoes the effect of --lines=.

-r, --reverse
Reverse output so that the newest entries are displayed first.
Manual page journalctl(1) line 71/650 16%

-r, --reverse
Reverse output so that the newest entries are displayed first.

-o, --output=
Controls the formatting of the journal entries that are shown. Takes one of the following

is the default and generates an output that is mostly identical to the formatting of classic
syslog files, showing one line per journal entry.

is very similar, but shows timestamps in the format the --since= and --until= options
accept. Unlike the timestamp information shown in short output mode this mode includes
weekday, year and timezone information in the output, and is locale-independent.

is very similar, but shows ISO 8601 wallclock timestamps.

as for short-iso but includes full microsecond precision.

is very similar, but shows classic syslog timestamps with full microsecond precision.


is very similar, but shows seconds passed since January 1st 1970 UTC instead of wallclock
timestamps ("UNIX time"). The time is shown with microsecond accuracy.

shows the full-structured entry items with all fields.

serializes the journal into a binary (but mostly text-based) stream suitable for backups and
network transfer (see Journal Export Format[1] for more information). To import the binary
stream back into native journald format use systemd-journal-remote(8).

formats entries as JSON objects, separated by newline characters (see Journal JSON Format[2]
for more information). Field values are generally encoded as JSON strings, with three

1. Fields larger than 4096 bytes are encoded as null values. (This may be turned off by
passing --all, but be aware that this may allocate overly long JSON objects.)

2. Journal entries permit non-unique fields within the same log entry. JSON does not allow
non-unique fields within objects. Due to this, if a non-unique field is encountered a
JSON array is used as field value, listing all field values as elements.

3. Fields containing non-printable or non-UTF8 bytes are encoded as arrays containing the
Manual page journalctl(1) line 122/650 2

3. Fields containing non-printable or non-UTF8 bytes are encoded as arrays containing the
raw bytes individually formatted as unsigned numbers.

Note that this encoding is reversible (with the exception of the size limit).

formats entries as JSON data structures, but formats them in multiple lines in order to make
them more readable by humans.

formats entries as JSON data structures, but wraps them in a format suitable for Server-Sent

formats entries as JSON data structures, but prefixes them with an ASCII Record Separator
character (0x1E) and suffixes them with an ASCII Line Feed character (0x0A), in accordance
with JavaScript Object Notation (JSON) Text Sequences[4] ("application/json-seq").

generates a very terse output, only showing the actual message of each journal entry with no
metadata, not even a timestamp. If combined with the --output-fields= option will output the
listed fields for each log record, instead of the message.

similar to short-full, but prefixes the unit and user unit names instead of the traditionall

syslog identifier. Useful when using templated instances, as it will include the arguments
in the unit names.

A comma separated list of the fields which should be included in the output. This has an effect
only for the output modes which would normally show all fields (verbose, export, json,
json-pretty, json-sse and json-seq), as well as on cat. For the former, the "__CURSOR",
"__REALTIME_TIMESTAMP", "__MONOTONIC_TIMESTAMP", and "_BOOT_ID" fields are always printed.

Express time in Coordinated Universal Time (UTC).

Don't show the hostname field of log messages originating from the local host. This switch has
an effect only on the short family of output modes (see above).

Note: this option does not remove occurrences of the hostname from log entries themselves, so it
does not prevent the hostname from being visible in the logs.

-x, --catalog
Augment log lines with explanation texts from the message catalog. This will add explanatory
help texts to log messages in the output where this is available. These short help texts will
explain the context of an error or log event, possible solutions, as well as pointers to support
forums, developer documentation, and any other relevant manuals. Note that help texts are not
available for all messages, but only for selected ones. For more information on the message
catalog, please refer to the Message Catalog Developer Documentation[5].

Note: when attaching journalctl output to bug reports, please do not use -x.

-q, --quiet
Suppresses all informational messages (i.e. "-- Journal begins at ...", "-- Reboot --"), any
warning messages regarding inaccessible system journals when run as a normal user.

-m, --merge
Show entries interleaved from all available journals, including remote ones.

-b [[ID][±offset]|all], --boot[=[ID][±offset]|all]
Show messages from a specific boot. This will add a match for "_BOOT_ID=".

The argument may be empty, in which case logs for the current boot will be shown.

If the boot ID is omitted, a positive offset will look up the boots starting from the beginning
of the journal, and an equal-or-less-than zero offset will look up boots starting from the end
of the journal. Thus, 1 means the first boot found in the journal in chronological order, 2 the
second and so on; while -0 is the last boot, -1 the boot before last, and so on. An empty offset
is equivalent to specifying -0, except when the current boot is not the last boot (e.g. because
--directory was specified to look at logs from a different machine).

If the 32-character ID is specified, it may optionally be followed by offset which identifies
the boot relative to the one given by boot ID. Negative values mean earlier boots and positive
values mean later boots. If offset is not specified, a value of zero is assumed, and the logs
for the boot given by ID are shown.

The special argument all can be used to negate the effect of an earlier use of -b.

Show a tabular list of boot numbers (relative to the current boot), their IDs, and the
timestamps of the first and last message pertaining to the boot.

-k, --dmesg
Show only kernel messages. This implies -b and adds the match "_TRANSPORT=kernel".

-t, --identifier=SYSLOG_IDENTIFIER
Show messages for the specified syslog identifier SYSLOG_IDENTIFIER.

This parameter can be specified multiple times.

-u, --unit=UNIT|PATTERN
Show messages for the specified systemd unit UNIT (such as a service unit), or for any of the
units matched by PATTERN. If a pattern is specified, a list of unit names found in the journal
is compared with the specified pattern and all that match are used. For each unit name, a match
is added for messages from the unit ("_SYSTEMD_UNIT=UNIT"), along with additional matches for
messages from systemd and messages about coredumps for the specified unit. A match is also added
for "_SYSTEMD_SLICE=UNIT", such that if the provided UNIT is a systemd.slice(5) unit, all logs
of children of the slice will be shown.

This parameter can be specified multiple times.

Show messages for the specified user session unit. This will add a match for messages from the
unit ("_SYSTEMD_USER_UNIT=" and "_UID=") and additional matches for messages from session
systemd and messages about coredumps for the specified unit. A match is also added for
"_SYSTEMD_USER_SLICE=UNIT", such that if the provided UNIT is a systemd.slice(5) unit, all logs
of children of the unit will be shown.

This parameter can be specified multiple times.

-p, --priority=
Filter output by message priorities or priority ranges. Takes either a single numeric or textual
log level (i.e. between 0/"emerg" and 7/"debug"), or a range of numeric/text log levels in the
form FROM..TO. The log levels are the usual syslog log levels as documented in syslog(3), i.e.
"emerg" (0), "alert" (1), "crit" (2), "err" (3), "warning" (4), "notice" (5), "info" (6),
"debug" (7). If a single log level is specified, all messages with this log level or a lower
(hence more important) log level are shown. If a range is specified, all messages within the
range are shown, including both the start and the end value of the range. This will add
"PRIORITY=" matches for the specified priorities.

Filter output by syslog facility. Takes a comma-separated list of numbers or facility names. The
names are the usual syslog facilities as documented in syslog(3).  --facility=help may be used
to display a list of known facility names and exit.

-g, --grep=
Filter output to entries where the MESSAGE= field matches the specified regular expression.
PERL-compatible regular expressions are used, see pcre2pattern(3) for a detailed description of
the syntax.

If the pattern is all lowercase, matching is case insensitive. Otherwise, matching is case
sensitive. This can be overridden with the --case-sensitive option, see below.

Make pattern matching case sensitive or case insensitive.

-c, --cursor=
Start showing entries from the location in the journal specified by the passed cursor.

If FILE exists and contains a cursor, start showing entries after this location. Otherwise the
show entries according the other given options. At the end, write the cursor of the last entry
to FILE. Use this option to continually read the journal by sequentially calling journalctl.

Start showing entries from the location in the journal after the location specified by the
passed cursor. The cursor is shown when the --show-cursor option is used.

The cursor is shown after the last entry after two dashes:

-- cursor: s=0639...

The format of the cursor is private and subject to change.

-S, --since=, -U, --until=
Start showing entries on or newer than the specified date, or on or older than the specified
date, respectively. Date specifications should be of the format "2012-10-30 18:17:16". If the
time part is omitted, "00:00:00" is assumed. If only the seconds component is omitted, ":00" is
assumed. If the date component is omitted, the current day is assumed. Alternatively the strings
"yesterday", "today", "tomorrow" are understood, which refer to 00:00:00 of the day before the
current day, the current day, or the day after the current day, respectively.  "now" refers to
the current time. Finally, relative times may be specified, prefixed with "-" or "+", referring
to times before or after the current time, respectively. For complete time and date
specification, see systemd.time(7). Note that --output=short-full prints timestamps that follow
precisely this format.

-F, --field=
Print all possible data values the specified field can take in all entries of the journal.

-N, --fields
Print all field names currently used in all entries of the journal.

--system, --user
Show messages from system services and the kernel (with --system). Show messages from service of
current user (with --user). If neither is specified, show all messages that the user can see.

-M, --machine=
Show messages from a running, local container. Specify a container name to connect to.

-D DIR, --directory=DIR
Takes a directory path as argument. If specified, journalctl will operate on the specified
journal directory DIR instead of the default runtime and system journal paths.

Takes a file glob as an argument. If specified, journalctl will operate on the specified journal
files matching GLOB instead of the default runtime and system journal paths. May be specified
multiple times, in which case files will be suitably interleaved.

Takes a directory path as an argument. If specified, journalctl will operate on journal
directories and catalog file hierarchy underneath the specified directory instead of the root
directory (e.g.  --update-catalog will create ROOT/var/lib/systemd/catalog/database, and journal
files under ROOT/run/journal/ or ROOT/var/log/journal/ will be displayed).

Takes a path to a disk image file or block device node. If specified, journalctl will operate on
the file system in the indicated disk image. This is similar to --root= but operates on file
systems stored in disk images or block devices, thus providing an easy way to extract log data
from disk images. The disk image should either contain just a file system or a set of file
systems within a GPT partition table, following the Discoverable Partitions Specification[6].
For further information on supported disk images, see systemd-nspawn(1)'s switch of the same

Takes a journal namespace identifier string as argument. If not specified the data collected by
the default namespace is shown. If specified shows the log data of the specified namespace
instead. If the namespace is specified as "*" data from all namespaces is shown, interleaved. If
the namespace identifier is prefixed with "+" data from the specified namespace and the default
namespace is shown, interleaved, but no other. For details about journal namespaces see systemd-

Instead of showing journal contents, show internal header information of the journal fields

Shows the current disk usage of all journal files. This shows the sum of the disk usage of all
archived and active journal files.

--vacuum-size=, --vacuum-time=, --vacuum-files=
Removes the oldest archived journal files until the disk space they use falls below the
specified size (specified with the usual "K", "M", "G" and "T" suffixes), or all archived
journal files contain no data older than the specified timespan (specified with the usual "s",
"m", "h", "days", "months", "weeks" and "years" suffixes), or no more than the specified number
of separate journal files remain. Note that running --vacuum-size= has only an indirect effect
on the output shown by --disk-usage, as the latter includes active journal files, while the
vacuuming operation only operates on archived journal files. Similarly, --vacuum-files= might
not actually reduce the number of journal files to below the specified number, as it will not
remove active journal files.

--vacuum-size=, --vacuum-time= and --vacuum-files= may be combined in a single invocation to
enforce any combination of a size, a time and a number of files limit on the archived journal
files. Specifying any of these three parameters as zero is equivalent to not enforcing the
specific limit, and is thus redundant.

These three switches may also be combined with --rotate into one command. If so, all active
files are rotated first, and the requested vacuuming operation is executed right after. The
rotation has the effect that all currently active files are archived (and potentially new, empty
journal files opened as replacement), and hence the vacuuming operation has the greatest effect
as it can take all log data written so far into account.

--list-catalog [128-bit-ID...]
List the contents of the message catalog as a table of message IDs, plus their short description

If any 128-bit-IDs are specified, only those entries are shown.

--dump-catalog [128-bit-ID...]
Show the contents of the message catalog, with entries separated by a line consisting of two
dashes and the ID (the format is the same as .catalog files).

If any 128-bit-IDs are specified, only those entries are shown.

Update the message catalog index. This command needs to be executed each time new catalog files
are installed, removed, or updated to rebuild the binary catalog index.

Instead of showing journal contents, generate a new key pair for Forward Secure Sealing (FSS).
This will generate a sealing key and a verification key. The sealing key is stored in the
journal data directory and shall remain on the host. The verification key should be stored
externally. Refer to the Seal= option in journald.conf(5) for information on Forward Secure
Sealing and for a link to a refereed scholarly paper detailing the cryptographic theory it is
based on.

When --setup-keys is passed and Forward Secure Sealing (FSS) has already been configured,
recreate FSS keys.

Specifies the change interval for the sealing key when generating an FSS key pair with
--setup-keys. Shorter intervals increase CPU consumption but shorten the time range of
undetectable journal alterations. Defaults to 15min.

Check the journal file for internal consistency. If the file has been generated with FSS enabled
and the FSS verification key has been specified with --verify-key=, authenticity of the journal
file is verified.

Specifies the FSS verification key to use for the --verify operation.

Asks the journal daemon to write all yet unwritten journal data to the backing file system and
synchronize all journals. This call does not return until the synchronization operation is
complete. This command guarantees that any log messages written before its invocation are safely
stored on disk at the time it returns.

Asks the journal daemon to flush any log data stored in /run/log/journal/ into
/var/log/journal/, if persistent storage is enabled. This call does not return until the
operation is complete. Note that this call is idempotent: the data is only flushed from
/run/log/journal/ into /var/log/journal/ once during system runtime (but see --relinquish-var
below), and this command exits cleanly without executing any operation if this has already
happened. This command effectively guarantees that all data is flushed to /var/log/journal/ at
the time it returns.

Asks the journal daemon for the reverse operation to --flush: if requested the daemon will write
further log data to /run/log/journal/ and stops writing to /var/log/journal/. A subsequent call
to --flush causes the log output to switch back to /var/log/journal/, see above.

Similar to --relinquish-var but executes no operation if the root file system and
/var/lib/journal/ reside on the same mount point. This operation is used during system shutdown
in order to make the journal daemon stop writing data to /var/log/journal/ in case that
directory is located on a mount point that needs to be unmounted.

Asks the journal daemon to rotate journal files. This call does not return until the rotation
operation is complete. Journal file rotation has the effect that all currently active journal
files are marked as archived and renamed, so that they are never written to in future. New
(empty) journal files are then created in their place. This operation may be combined with
--vacuum-size=, --vacuum-time= and --vacuum-file= into a single command, see above.

-h, --help
Print a short help text and exit.

Print a short version string and exit.

Do not pipe output into a pager.


On success, 0 is returned; otherwise, a non-zero failure code is returned.

The maximum log level of emitted messages (messages with a higher log level, i.e. less important
ones, will be suppressed). Either one of (in order of decreasing importance) emerg, alert, crit,
err, warning, notice, info, debug, or an integer in the range 0...7. See syslog(3) for more

A boolean. If true, messages written to the tty will be colored according to priority.

This setting is only useful when messages are written directly to the terminal, because
journalctl(1) and other tools that display logs will color messages based on the log level on
their own.

A boolean. If true, console log messages will be prefixed with a timestamp.

This setting is only useful when messages are written directly to the terminal or a file,
because journalctl(1) and other tools that display logs will attach timestamps based on the
entry metadata on their own.

A boolean. If true, messages will be prefixed with a filename and line number in the source code
where the message originates.

Note that the log location is often attached as metadata to journal entries anyway. Including it
directly in the message text can nevertheless be convenient when debugging programs.

A boolean. If true, messages will be prefixed with the current numerical thread ID (TID).

Note that the this information is attached as metadata to journal entries anyway. Including it
directly in the message text can nevertheless be convenient when debugging programs.

The destination for log messages. One of console (log to the attached tty), console-prefixed
(log to the attached tty but with prefixes encoding the log level and "facility", see syslog(3),
kmsg (log to the kernel circular log buffer), journal (log to the journal), journal-or-kmsg (log
to the journal if available, and to kmsg otherwise), auto (determine the appropriate log target
automatically, the default), null (disable log output).

Pager to use when --no-pager is not given; overrides $PAGER. If neither $SYSTEMD_PAGER nor
$PAGER are set, a set of well-known pager implementations are tried in turn, including less(1)
and more(1), until one is found. If no pager implementation is discovered no pager is invoked.
Setting this environment variable to an empty string or the value "cat" is equivalent to passing

Override the options passed to less (by default "FRSXMK").

Users might want to change two options in particular:

This option instructs the pager to exit immediately when Ctrl+C is pressed. To allow less to
handle Ctrl+C itself to switch back to the pager command prompt, unset this option.

If the value of $SYSTEMD_LESS does not include "K", and the pager that is invoked is less,
Ctrl+C will be ignored by the executable, and needs to be handled by the pager.

This option instructs the pager to not send termcap initialization and deinitialization
strings to the terminal. It is set by default to allow command output to remain visible in
the terminal even after the pager exits. Nevertheless, this prevents some pager
functionality from working, in particular paged output cannot be scrolled with the mouse.

See less(1) for more discussion.

Override the charset passed to less (by default "utf-8", if the invoking terminal is determined
to be UTF-8 compatible).

Takes a boolean argument. When true, the "secure" mode of the pager is enabled; if false,
disabled. If $SYSTEMD_PAGERSECURE is not set at all, secure mode is enabled if the effective UID
is not the same as the owner of the login session, see geteuid(2) and sd_pid_get_owner_uid(3).
In secure mode, LESSSECURE=1 will be set when invoking the pager, and the pager shall disable
commands that open or create new files or start new subprocesses. When $SYSTEMD_PAGERSECURE is
not set at all, pagers which are not known to implement secure mode will not be used. (Currently
only less(1) implements secure mode.)

Note: when commands are invoked with elevated privileges, for example under sudo(8) or
pkexec(1), care must be taken to ensure that unintended interactive features are not enabled.
"Secure" mode for the pager may be enabled automatically as describe above. Setting
SYSTEMD_PAGERSECURE=0 or not removing it from the inherited environment allows the user to
invoke arbitrary commands. Note that if the $SYSTEMD_PAGER or $PAGER variables are to be
honoured, $SYSTEMD_PAGERSECURE must be set too. It might be reasonable to completely disable the
pager using --no-pager instead.

Takes a boolean argument. When true, systemd and related utilities will use colors in their
output, otherwise the output will be monochrome. Additionally, the variable can take one of the
following special values: "16", "256" to restrict the use of colors to the base 16 or 256 ANSI
colors, respectively. This can be specified to override the automatic decision based on $TERM
and what the console is connected to.

The value must be a boolean. Controls whether clickable links should be generated in the output
for terminal emulators supporting this. This can be specified to override the decision that
systemd makes based on $TERM and other conditions.

Without arguments, all collected logs are shown unfiltered:


With one match specified, all entries with a field matching the expression are shown:

journalctl _SYSTEMD_UNIT=avahi-daemon.service
journalctl _SYSTEMD_CGROUP=/user.slice/user-42.slice/session-c1.scope

If two different fields are matched, only entries matching both expressions at the same time are

journalctl _SYSTEMD_UNIT=avahi-daemon.service _PID=28097

If two matches refer to the same field, all entries matching either expression are shown:

journalctl _SYSTEMD_UNIT=avahi-daemon.service _SYSTEMD_UNIT=dbus.service

If the separator "+" is used, two expressions may be combined in a logical OR. The following will
show all messages from the Avahi service process with the PID 28097 plus all messages from the D-Bus
service (from any of its processes):

journalctl _SYSTEMD_UNIT=avahi-daemon.service _PID=28097 + _SYSTEMD_UNIT=dbus.service

To show all fields emitted by a unit and about the unit, option -u/--unit= should be used.
journalctl -u name expands to a complex filter similar to

+ UNIT=name.service _PID=1
+ OBJECT_SYSTEMD_UNIT=name.service _UID=0
+ COREDUMP_UNIT=name.service _UID=0 MESSAGE_ID=fc2e22bc6ee647b6b90729ab34a250b1

(see systemd.journal-fields(7) for an explanation of those patterns).

Show all logs generated by the D-Bus executable:

journalctl /usr/bin/dbus-daemon

Show all kernel logs from previous boot:

journalctl -k -b -1

Show a live log display from a system service apache.service:

journalctl -f -u apache


systemd(1), systemd-journald.service(8), systemctl(1), coredumpctl(1), systemd.journal-fields(7),
journald.conf(5), systemd.time(7), systemd-journal-remote.service(8), systemd-journal-

1. Journal Export Format

2. Journal JSON Format

3. Server-Sent Events

4. JavaScript Object Notation (JSON) Text Sequences

5. Message Catalog Developer Documentation

6. Discoverable Partitions Specification

systemd 249                                                                                   JOURNALCTL(1)

The hell to copy and past that is only amplified by the fact that I cant highlight the bloody log, well I can, one page at a time, oh and kwin and busted, so I can only see the right side of the log behind both the file explorer and my text document.

I am burnt out...,

Show all kernel logs from previous boot:

           journalctl -k -b -1

I wrote a very lengthy response to you with many questions and suggestions. You ignored most of the suggestions/questions or gave completely inadequate information on your following response.

You did not even reply to my suggestion to create a new user account. This was one of my most important suggestions!!! This would tell us a great deal if a new user was working correctly, as well as giving you a properly functioning system to work on if successful.

I know there is probably a communication issue here because of language differences, but I can't work with any user that I need to pry information out of with a crowbar.

Good luck with your issue.


Just working one thing at a time, you asked for logs, so i prioritized those 1st, as the new user would require me to de some research on how to do that in terminal.

You never told me that was important, and as the guest account works fine, i saw no hurry on this

So sorry that all i have done is fetched one log, two logs, if you count the log thing i nabbed far the start of my post.

If you give suggestions you should list there importance also, as not everyone will jump onto them, if for say, there more concerned with getting logs filed.

Also with eye site issues the wiki is cumbersome and of no help.

Better banging rocks together, when all you want is same terminal commends not a bloody technical document.

I second @tbg and reinstall may be the easiest thing for you.
Although..... I wouldn't want my computer in that state, but would love to mess around in your computer :slight_smile: So many issues !!

I think kwin is the least of your worries!
First thing you should do is BACKUPS ASAP! of your important data.

I suggest you keep a usb pen with Ventoy ( there is a topic about it here and livecd . Ventoy ). Its pretty cool to keep handy.
Extra tip: If you have a big usb pen you can keep some spare GB's in an extra partition to make backups directly to the pen with ventoy.

Then try to check the btrfs for errors. ( for example, when booting on the live usb, btrfs check "/dev/sda1" disk. Please think 100 times before doing btrfs check --repair ). also check if with the liveusb booted, you have any lib ata errors.

By the way, did you change kernels or anything in the computer uefi/bios ? Those kernel erros look scary AF and interesting !


The kernal is the same as i start, never bothered swapping stuff, the most stock iv had my system.

Really don't want to dumb my system, save game data bing a concern.

I still need to fetch a second log for someone and make guest account apparently

And a guest account, but glad this 1st log is intriguing to you.

Also what is borked on my computer besides kwin and that otherthing you mentioned?

Also, if you want to, you can have a look under the hood, if you can recommend a remora software.

I don't keep personals on line, and as long as i con nuke the connection with a touch of a button.

This is a stock install, so its on the os if it topples, so might find a bug.

Though i am more then willing to pull it from the digital void by myself.

I have saved my os after a swap of the log in greeter, did not take, or the many times I reinstalled the X environment, for smoothing else.

I had to reinstall this three times, issues with compez or wayland? Dovak would not take. Sad, love Compez but its dead.

I can brows the web in Terminal... its saved a os a few times. Is there a way to increases font size in there? Not that gui impersonator eather, talking about tde backbone naked to the eye. Hate that void, dont know how you older fellers do it, or the archafiles.

Never bothered with toying with the desktop enviroment, yet, due to how finicky it is

Its a shame, i realy like gruda, vs mint with gaming. When it works, it works like better, but its choppy, or perhaps my hardwere is just to old to be considered.

Cpu is like 2014 or so. Eh who knows, pacman is buggy as heck with gui, don't really know why it went side ways.

Mine is the same age no problems

That is not pacman-GUI its not even a arch program its Manjaro pamac poorly written software that tries to re-invent the wheel should leave well alone.

What you should ask yourself why is this only happening to me, instead you are blaming everything else for your problems. ever thought it could be down to your total lack of understanding and or knowledge. you have a good CPU a good GPU


Not blaming anything, dang thing is stock, ant don nothing with it.

Its buggy, and i dont know why.

So with millions of i7 with AMD graghics yours is the only one that's buggy wake up you need to crawl before you can walk, many users run your setup Garuda is arch based 1000s use the same hardware so something is wrong at your end. or you made a mistake with the iso or install. but you blame the OS have you tried to reinstall tried a different flavour. it is possible you are shooting above your level of knowledge Endeavour is not intended for new users and works fine for experienced users think about it. Use Linux mint you can always come back latter.

even using the wrong program to install on the USB can give bad results, not having your bias upto date can also cause problems.

1 Like

well ... I can recommend ssh ( secure shell ) for the remove login. you can stop the sshd whenever you want.

Maybe @tbg or anyone more experienced than me can have a look.

I am surprised that with all those "disk errors" you can do anything with it.

But my take would be to get to know why those kernel/btrfs disk bugs are happening.

If you can, could you swap the kernel to an LTS version and then boot it and paste here the dmesg ?