You are not logged in.

#1 2021-08-21 01:31:13

ArcticStag
Member
Registered: 2020-09-14
Posts: 46

I want to understand xmodmap better

Hi there,

I have been noticing a lot of errors when I launch my window manager (I cant seem to find these errors in journalctl -xe, Xorg.0.log or Xorg.1.log, Will link anyway)

This is the contents of my /etc/X11/xinit directory

# la /etc/X11/xinit
xinitrc.d
xinitrc
xserverrc

Journalctl

Xorg.0.log

Xorg.1.log

Finally here is a copy of the default and only xinitrc on my system

#!/bin/sh

userresources=$HOME/.Xresources
usermodmap=$HOME/.Xmodmap
sysresources=/etc/X11/xinit/.Xresources
sysmodmap=/etc/X11/xinit/.Xmodmap

# merge in defaults and keymaps

if [ -f $sysresources ]; then
    xrdb -merge $sysresources
fi

if [ -f $sysmodmap ]; then
    xmodmap $sysmodmap
fi

if [ -f "$userresources" ]; then
    xrdb -merge "$userresources"
fi

if [ -f "$usermodmap" ]; then
    xmodmap "$usermodmap"
fi

# start some nice programs

if [ -d /etc/X11/xinit/xinitrc.d ] ; then
 for f in /etc/X11/xinit/xinitrc.d/?*.sh ; do
  [ -x "$f" ] && . "$f"
 done
 unset f
fi

twm &
xclock -geometry 50x50-1+1 &
xterm -geometry 80x50+494+51 &
xterm -geometry 80x20+494-0 &
exec xterm -geometry 80x66+0+0 -name login

I notice that in the xinitrc it is attempting to reference sysmodmap=/etc/X11/xinit/.Xmodmap however there is no .Xmodmap in the /etc/xinit/ directory.

I also notice that in the xinitrc it is attempting to reference sysresources=/etc/X11/xinit/.Xresources however there is no .Xresources in the /etc/xinit/ directory.

  1. Is this a bad thing?

  2. Should this be there by default?

  3. Should I add this file in here?

    • If yes

      • Can it be auto generated somehow?

      • Do I need to manually create it?

TIA!

Last edited by ArcticStag (2021-08-23 05:49:34)

Offline

#2 2021-08-21 02:21:54

thiagowfx
Member
Registered: 2013-07-09
Posts: 586

Re: I want to understand xmodmap better

1) No ([ -f ] in bash checks if the file exists, so it's harmless)
2) No (Run pacman -Ql xorg-xmodmap xorg-xrdb and you'll see)
3) No (Only if you want to...)

Also, see https://wiki.archlinux.org/title/Xmodmap

Last edited by thiagowfx (2021-08-21 02:22:42)

Offline

#3 2021-08-21 04:30:11

Trilby
Inspector Parrot
Registered: 2011-11-29
Posts: 30,500
Website

Re: I want to understand xmodmap better

Are you actually running twm?  When you start X you get three xterms and an xclock?

If not, then all of this is irrelevant as that xinitrc is not in use.


"UNIX is simple and coherent" - Dennis Ritchie; "GNU's Not Unix" - Richard Stallman

Offline

#4 2021-08-21 06:21:47

seth
Member
From: Won't reply 2 private help req
Registered: 2012-09-03
Posts: 77,342

Re: I want to understand xmodmap better

a lot of errors when I launch my window manager (I cant seem to find these errors in journalctl -xe, Xorg.0.log or Xorg.1.log

It would also be super-helpful if you'd indicate *what* those errors actually are…

Unrelated:

Aug 21 10:55:38 asgard kernel: ata1.00: exception Emask 0x0 SAct 0x4078f0 SErr 0x0 action 0x0
Aug 21 10:55:38 asgard kernel: ata1.00: irq_stat 0x40000008
Aug 21 10:55:38 asgard kernel: ata1.00: failed command: READ FPDMA QUEUED
Aug 21 10:55:38 asgard kernel: ata1.00: cmd 60/08:b0:60:1d:41/00:00:61:00:00/40 tag 22 ncq dma 4096 in
                                        res 41/40:08:60:1d:41/00:00:61:00:00/00 Emask 0x409 (media error) <F>
Aug 21 10:55:38 asgard kernel: ata1.00: status: { DRDY ERR }
Aug 21 10:55:38 asgard kernel: ata1.00: error: { UNC }
Aug 21 10:55:38 asgard kernel: ata1.00: configured for UDMA/133
Aug 21 10:55:38 asgard kernel: sd 0:0:0:0: [sda] tag#22 FAILED Result: hostbyte=DID_OK driverbyte=DRIVER_SENSE cmd_age=3s
Aug 21 10:55:38 asgard kernel: sd 0:0:0:0: [sda] tag#22 Sense Key : Medium Error [current] 
Aug 21 10:55:38 asgard kernel: sd 0:0:0:0: [sda] tag#22 Add. Sense: Unrecovered read error - auto reallocate failed
Aug 21 10:55:38 asgard kernel: sd 0:0:0:0: [sda] tag#22 CDB: Read(10) 28 00 61 41 1d 60 00 00 08 00
Aug 21 10:55:38 asgard kernel: blk_update_request: I/O error, dev sda, sector 1631657312 op 0x0:(READ) flags 0x3000 phys_seg 1 prio class 0
Aug 21 10:55:38 asgard kernel: EXT4-fs warning (device sda1): htree_dirblock_to_tree:1027: inode #50987182: lblock 0: comm find: error -5 reading directory block
Aug 21 10:55:38 asgard kernel: ata1: EH complete
Aug 21 10:55:41 asgard kernel: ata1.00: exception Emask 0x0 SAct 0x800000 SErr 0x0 action 0x0
Aug 21 10:55:41 asgard kernel: ata1.00: irq_stat 0x40000008
Aug 21 10:55:41 asgard kernel: ata1.00: failed command: READ FPDMA QUEUED
Aug 21 10:55:41 asgard kernel: ata1.00: cmd 60/08:b8:58:1d:41/00:00:61:00:00/40 tag 23 ncq dma 4096 in
                                        res 41/40:08:58:1d:41/00:00:61:00:00/00 Emask 0x409 (media error) <F>
Aug 21 10:55:41 asgard kernel: ata1.00: status: { DRDY ERR }
Aug 21 10:55:41 asgard kernel: ata1.00: error: { UNC }
Aug 21 10:55:41 asgard kernel: ata1.00: configured for UDMA/133
Aug 21 10:55:41 asgard kernel: sd 0:0:0:0: [sda] tag#23 FAILED Result: hostbyte=DID_OK driverbyte=DRIVER_SENSE cmd_age=3s
Aug 21 10:55:41 asgard kernel: sd 0:0:0:0: [sda] tag#23 Sense Key : Medium Error [current] 
Aug 21 10:55:41 asgard kernel: sd 0:0:0:0: [sda] tag#23 Add. Sense: Unrecovered read error - auto reallocate failed
Aug 21 10:55:41 asgard kernel: sd 0:0:0:0: [sda] tag#23 CDB: Read(10) 28 00 61 41 1d 58 00 00 08 00
Aug 21 10:55:41 asgard kernel: blk_update_request: I/O error, dev sda, sector 1631657304 op 0x0:(READ) flags 0x3000 phys_seg 1 prio class 0
Aug 21 10:55:41 asgard kernel: ata1: EH complete
Aug 21 10:55:41 asgard kernel: EXT4-fs warning (device sda1): htree_dirblock_to_tree:1027: inode #50987179: lblock 0: comm find: error -5 reading directory block
Aug 21 10:55:44 asgard kernel: ata1.00: exception Emask 0x0 SAct 0x4000 SErr 0x0 action 0x0
Aug 21 10:55:44 asgard kernel: ata1.00: irq_stat 0x40000008
Aug 21 10:55:44 asgard kernel: ata1.00: failed command: READ FPDMA QUEUED
Aug 21 10:55:44 asgard kernel: ata1.00: cmd 60/08:70:c0:1d:41/00:00:61:00:00/40 tag 14 ncq dma 4096 in
                                        res 41/40:08:c0:1d:41/00:00:61:00:00/00 Emask 0x409 (media error) <F>
Aug 21 10:55:44 asgard kernel: ata1.00: status: { DRDY ERR }
Aug 21 10:55:44 asgard kernel: ata1.00: error: { UNC }
Aug 21 10:55:44 asgard kernel: ata1.00: configured for UDMA/133
Aug 21 10:55:44 asgard kernel: sd 0:0:0:0: [sda] tag#14 FAILED Result: hostbyte=DID_OK driverbyte=DRIVER_SENSE cmd_age=2s
Aug 21 10:55:44 asgard kernel: sd 0:0:0:0: [sda] tag#14 Sense Key : Medium Error [current] 
Aug 21 10:55:44 asgard kernel: sd 0:0:0:0: [sda] tag#14 Add. Sense: Unrecovered read error - auto reallocate failed
Aug 21 10:55:44 asgard kernel: sd 0:0:0:0: [sda] tag#14 CDB: Read(10) 28 00 61 41 1d c0 00 00 08 00
Aug 21 10:55:44 asgard kernel: blk_update_request: I/O error, dev sda, sector 1631657408 op 0x0:(READ) flags 0x3000 phys_seg 1 prio class 0
Aug 21 10:55:44 asgard kernel: ata1: EH complete
Aug 21 10:55:44 asgard kernel: EXT4-fs warning (device sda1): htree_dirblock_to_tree:1027: inode #50987076: lblock 0: comm find: error -5 reading directory block
Aug 21 10:57:18 asgard kernel: ata1.00: exception Emask 0x0 SAct 0x40 SErr 0x0 action 0x0
Aug 21 10:57:18 asgard kernel: ata1.00: irq_stat 0x40000008
Aug 21 10:57:18 asgard kernel: ata1.00: failed command: READ FPDMA QUEUED
Aug 21 10:57:18 asgard kernel: ata1.00: cmd 60/08:30:60:1d:41/00:00:61:00:00/40 tag 6 ncq dma 4096 in
                                        res 41/40:08:60:1d:41/00:00:61:00:00/00 Emask 0x409 (media error) <F>
Aug 21 10:57:18 asgard kernel: ata1.00: status: { DRDY ERR }
Aug 21 10:57:18 asgard kernel: ata1.00: error: { UNC }
Aug 21 10:57:18 asgard kernel: ata1.00: configured for UDMA/133
Aug 21 10:57:18 asgard kernel: sd 0:0:0:0: [sda] tag#6 FAILED Result: hostbyte=DID_OK driverbyte=DRIVER_SENSE cmd_age=3s
Aug 21 10:57:18 asgard kernel: sd 0:0:0:0: [sda] tag#6 Sense Key : Medium Error [current] 
Aug 21 10:57:18 asgard kernel: sd 0:0:0:0: [sda] tag#6 Add. Sense: Unrecovered read error - auto reallocate failed
Aug 21 10:57:18 asgard kernel: sd 0:0:0:0: [sda] tag#6 CDB: Read(10) 28 00 61 41 1d 60 00 00 08 00
Aug 21 10:57:18 asgard kernel: blk_update_request: I/O error, dev sda, sector 1631657312 op 0x0:(READ) flags 0x3000 phys_seg 1 prio class 0
Aug 21 10:57:18 asgard kernel: ata1: EH complete
Aug 21 10:57:18 asgard kernel: EXT4-fs warning (device sda1): htree_dirblock_to_tree:1027: inode #50987182: lblock 0: comm find: error -5 reading directory block
Aug 21 10:57:21 asgard kernel: ata1.00: exception Emask 0x0 SAct 0x80000008 SErr 0x0 action 0x0
Aug 21 10:57:21 asgard kernel: ata1.00: irq_stat 0x40000008
Aug 21 10:57:21 asgard kernel: ata1.00: failed command: READ FPDMA QUEUED
Aug 21 10:57:21 asgard kernel: ata1.00: cmd 60/08:18:58:1d:41/00:00:61:00:00/40 tag 3 ncq dma 4096 in
                                        res 41/40:08:58:1d:41/00:00:61:00:00/00 Emask 0x409 (media error) <F>
Aug 21 10:57:21 asgard kernel: ata1.00: status: { DRDY ERR }
Aug 21 10:57:21 asgard kernel: ata1.00: error: { UNC }
Aug 21 10:57:21 asgard kernel: ata1.00: configured for UDMA/133
Aug 21 10:57:21 asgard kernel: sd 0:0:0:0: [sda] tag#3 FAILED Result: hostbyte=DID_OK driverbyte=DRIVER_SENSE cmd_age=3s
Aug 21 10:57:21 asgard kernel: sd 0:0:0:0: [sda] tag#3 Sense Key : Medium Error [current] 
Aug 21 10:57:21 asgard kernel: sd 0:0:0:0: [sda] tag#3 Add. Sense: Unrecovered read error - auto reallocate failed
Aug 21 10:57:21 asgard kernel: sd 0:0:0:0: [sda] tag#3 CDB: Read(10) 28 00 61 41 1d 58 00 00 08 00
Aug 21 10:57:21 asgard kernel: blk_update_request: I/O error, dev sda, sector 1631657304 op 0x0:(READ) flags 0x3000 phys_seg 1 prio class 0
Aug 21 10:57:21 asgard kernel: EXT4-fs warning (device sda1): htree_dirblock_to_tree:1027: inode #50987179: lblock 0: comm find: error -5 reading directory block
Aug 21 10:57:21 asgard kernel: ata1: EH complete
Aug 21 10:57:24 asgard kernel: ata1.00: exception Emask 0x0 SAct 0x30 SErr 0x0 action 0x0
Aug 21 10:57:24 asgard kernel: ata1.00: irq_stat 0x40000008
Aug 21 10:57:24 asgard kernel: ata1.00: failed command: READ FPDMA QUEUED
Aug 21 10:57:24 asgard kernel: ata1.00: cmd 60/08:20:c0:1d:41/00:00:61:00:00/40 tag 4 ncq dma 4096 in
                                        res 41/40:08:c0:1d:41/00:00:61:00:00/00 Emask 0x409 (media error) <F>
Aug 21 10:57:24 asgard kernel: ata1.00: status: { DRDY ERR }
Aug 21 10:57:24 asgard kernel: ata1.00: error: { UNC }
Aug 21 10:57:24 asgard kernel: ata1.00: configured for UDMA/133
Aug 21 10:57:24 asgard kernel: sd 0:0:0:0: [sda] tag#4 FAILED Result: hostbyte=DID_OK driverbyte=DRIVER_SENSE cmd_age=2s
Aug 21 10:57:24 asgard kernel: sd 0:0:0:0: [sda] tag#4 Sense Key : Medium Error [current] 
Aug 21 10:57:24 asgard kernel: sd 0:0:0:0: [sda] tag#4 Add. Sense: Unrecovered read error - auto reallocate failed
Aug 21 10:57:24 asgard kernel: sd 0:0:0:0: [sda] tag#4 CDB: Read(10) 28 00 61 41 1d c0 00 00 08 00
Aug 21 10:57:24 asgard kernel: blk_update_request: I/O error, dev sda, sector 1631657408 op 0x0:(READ) flags 0x3000 phys_seg 1 prio class 0
Aug 21 10:57:24 asgard kernel: EXT4-fs warning (device sda1): htree_dirblock_to_tree:1027: inode #50987076: lblock 0: comm find: error -5 reading directory block
Aug 21 10:57:24 asgard kernel: ata1: EH complete

=> https://wiki.archlinux.org/title/SMART

Offline

#5 2021-08-22 03:36:50

ArcticStag
Member
Registered: 2020-09-14
Posts: 46

Re: I want to understand xmodmap better

Trilby wrote:

Are you actually running twm?  When you start X you get three xterms and an xclock?

If not, then all of this is irrelevant as that xinitrc is not in use.

No, I am not. Should I remove that from the default file there?

seth wrote:

It would also be super-helpful if you'd indicate *what* those errors actually are…

My apologies, I forgot to mention the errors. The errors zip past quite quickly, however they are all related to [im]xf86-{somthing-here}[/im]

seth wrote:

Unrelated:

Aug 21 10:55:38 asgard kernel: ata1.00: exception Emask 0x0 SAct 0x4078f0 SErr 0x0 action 0x0
Aug 21 10:55:38 asgard kernel: ata1.00: irq_stat 0x40000008
Aug 21 10:55:38 asgard kernel: ata1.00: failed command: READ FPDMA QUEUED
Aug 21 10:55:38 asgard kernel: ata1.00: cmd 60/08:b0:60:1d:41/00:00:61:00:00/40 tag 22 ncq dma 4096 in
                                        res 41/40:08:60:1d:41/00:00:61:00:00/00 Emask 0x409 (media error) <F>
Aug 21 10:55:38 asgard kernel: ata1.00: status: { DRDY ERR }
Aug 21 10:55:38 asgard kernel: ata1.00: error: { UNC }
Aug 21 10:55:38 asgard kernel: ata1.00: configured for UDMA/133
Aug 21 10:55:38 asgard kernel: sd 0:0:0:0: [sda] tag#22 FAILED Result: hostbyte=DID_OK driverbyte=DRIVER_SENSE cmd_age=3s
Aug 21 10:55:38 asgard kernel: sd 0:0:0:0: [sda] tag#22 Sense Key : Medium Error [current] 
Aug 21 10:55:38 asgard kernel: sd 0:0:0:0: [sda] tag#22 Add. Sense: Unrecovered read error - auto reallocate failed
Aug 21 10:55:38 asgard kernel: sd 0:0:0:0: [sda] tag#22 CDB: Read(10) 28 00 61 41 1d 60 00 00 08 00
Aug 21 10:55:38 asgard kernel: blk_update_request: I/O error, dev sda, sector 1631657312 op 0x0:(READ) flags 0x3000 phys_seg 1 prio class 0
Aug 21 10:55:38 asgard kernel: EXT4-fs warning (device sda1): htree_dirblock_to_tree:1027: inode #50987182: lblock 0: comm find: error -5 reading directory block
Aug 21 10:55:38 asgard kernel: ata1: EH complete
Aug 21 10:55:41 asgard kernel: ata1.00: exception Emask 0x0 SAct 0x800000 SErr 0x0 action 0x0
Aug 21 10:55:41 asgard kernel: ata1.00: irq_stat 0x40000008
Aug 21 10:55:41 asgard kernel: ata1.00: failed command: READ FPDMA QUEUED
Aug 21 10:55:41 asgard kernel: ata1.00: cmd 60/08:b8:58:1d:41/00:00:61:00:00/40 tag 23 ncq dma 4096 in
                                        res 41/40:08:58:1d:41/00:00:61:00:00/00 Emask 0x409 (media error) <F>
Aug 21 10:55:41 asgard kernel: ata1.00: status: { DRDY ERR }
Aug 21 10:55:41 asgard kernel: ata1.00: error: { UNC }
Aug 21 10:55:41 asgard kernel: ata1.00: configured for UDMA/133
Aug 21 10:55:41 asgard kernel: sd 0:0:0:0: [sda] tag#23 FAILED Result: hostbyte=DID_OK driverbyte=DRIVER_SENSE cmd_age=3s
Aug 21 10:55:41 asgard kernel: sd 0:0:0:0: [sda] tag#23 Sense Key : Medium Error [current] 
Aug 21 10:55:41 asgard kernel: sd 0:0:0:0: [sda] tag#23 Add. Sense: Unrecovered read error - auto reallocate failed
Aug 21 10:55:41 asgard kernel: sd 0:0:0:0: [sda] tag#23 CDB: Read(10) 28 00 61 41 1d 58 00 00 08 00
Aug 21 10:55:41 asgard kernel: blk_update_request: I/O error, dev sda, sector 1631657304 op 0x0:(READ) flags 0x3000 phys_seg 1 prio class 0
Aug 21 10:55:41 asgard kernel: ata1: EH complete
Aug 21 10:55:41 asgard kernel: EXT4-fs warning (device sda1): htree_dirblock_to_tree:1027: inode #50987179: lblock 0: comm find: error -5 reading directory block
Aug 21 10:55:44 asgard kernel: ata1.00: exception Emask 0x0 SAct 0x4000 SErr 0x0 action 0x0
Aug 21 10:55:44 asgard kernel: ata1.00: irq_stat 0x40000008
Aug 21 10:55:44 asgard kernel: ata1.00: failed command: READ FPDMA QUEUED
Aug 21 10:55:44 asgard kernel: ata1.00: cmd 60/08:70:c0:1d:41/00:00:61:00:00/40 tag 14 ncq dma 4096 in
                                        res 41/40:08:c0:1d:41/00:00:61:00:00/00 Emask 0x409 (media error) <F>
Aug 21 10:55:44 asgard kernel: ata1.00: status: { DRDY ERR }
Aug 21 10:55:44 asgard kernel: ata1.00: error: { UNC }
Aug 21 10:55:44 asgard kernel: ata1.00: configured for UDMA/133
Aug 21 10:55:44 asgard kernel: sd 0:0:0:0: [sda] tag#14 FAILED Result: hostbyte=DID_OK driverbyte=DRIVER_SENSE cmd_age=2s
Aug 21 10:55:44 asgard kernel: sd 0:0:0:0: [sda] tag#14 Sense Key : Medium Error [current] 
Aug 21 10:55:44 asgard kernel: sd 0:0:0:0: [sda] tag#14 Add. Sense: Unrecovered read error - auto reallocate failed
Aug 21 10:55:44 asgard kernel: sd 0:0:0:0: [sda] tag#14 CDB: Read(10) 28 00 61 41 1d c0 00 00 08 00
Aug 21 10:55:44 asgard kernel: blk_update_request: I/O error, dev sda, sector 1631657408 op 0x0:(READ) flags 0x3000 phys_seg 1 prio class 0
Aug 21 10:55:44 asgard kernel: ata1: EH complete
Aug 21 10:55:44 asgard kernel: EXT4-fs warning (device sda1): htree_dirblock_to_tree:1027: inode #50987076: lblock 0: comm find: error -5 reading directory block
Aug 21 10:57:18 asgard kernel: ata1.00: exception Emask 0x0 SAct 0x40 SErr 0x0 action 0x0
Aug 21 10:57:18 asgard kernel: ata1.00: irq_stat 0x40000008
Aug 21 10:57:18 asgard kernel: ata1.00: failed command: READ FPDMA QUEUED
Aug 21 10:57:18 asgard kernel: ata1.00: cmd 60/08:30:60:1d:41/00:00:61:00:00/40 tag 6 ncq dma 4096 in
                                        res 41/40:08:60:1d:41/00:00:61:00:00/00 Emask 0x409 (media error) <F>
Aug 21 10:57:18 asgard kernel: ata1.00: status: { DRDY ERR }
Aug 21 10:57:18 asgard kernel: ata1.00: error: { UNC }
Aug 21 10:57:18 asgard kernel: ata1.00: configured for UDMA/133
Aug 21 10:57:18 asgard kernel: sd 0:0:0:0: [sda] tag#6 FAILED Result: hostbyte=DID_OK driverbyte=DRIVER_SENSE cmd_age=3s
Aug 21 10:57:18 asgard kernel: sd 0:0:0:0: [sda] tag#6 Sense Key : Medium Error [current] 
Aug 21 10:57:18 asgard kernel: sd 0:0:0:0: [sda] tag#6 Add. Sense: Unrecovered read error - auto reallocate failed
Aug 21 10:57:18 asgard kernel: sd 0:0:0:0: [sda] tag#6 CDB: Read(10) 28 00 61 41 1d 60 00 00 08 00
Aug 21 10:57:18 asgard kernel: blk_update_request: I/O error, dev sda, sector 1631657312 op 0x0:(READ) flags 0x3000 phys_seg 1 prio class 0
Aug 21 10:57:18 asgard kernel: ata1: EH complete
Aug 21 10:57:18 asgard kernel: EXT4-fs warning (device sda1): htree_dirblock_to_tree:1027: inode #50987182: lblock 0: comm find: error -5 reading directory block
Aug 21 10:57:21 asgard kernel: ata1.00: exception Emask 0x0 SAct 0x80000008 SErr 0x0 action 0x0
Aug 21 10:57:21 asgard kernel: ata1.00: irq_stat 0x40000008
Aug 21 10:57:21 asgard kernel: ata1.00: failed command: READ FPDMA QUEUED
Aug 21 10:57:21 asgard kernel: ata1.00: cmd 60/08:18:58:1d:41/00:00:61:00:00/40 tag 3 ncq dma 4096 in
                                        res 41/40:08:58:1d:41/00:00:61:00:00/00 Emask 0x409 (media error) <F>
Aug 21 10:57:21 asgard kernel: ata1.00: status: { DRDY ERR }
Aug 21 10:57:21 asgard kernel: ata1.00: error: { UNC }
Aug 21 10:57:21 asgard kernel: ata1.00: configured for UDMA/133
Aug 21 10:57:21 asgard kernel: sd 0:0:0:0: [sda] tag#3 FAILED Result: hostbyte=DID_OK driverbyte=DRIVER_SENSE cmd_age=3s
Aug 21 10:57:21 asgard kernel: sd 0:0:0:0: [sda] tag#3 Sense Key : Medium Error [current] 
Aug 21 10:57:21 asgard kernel: sd 0:0:0:0: [sda] tag#3 Add. Sense: Unrecovered read error - auto reallocate failed
Aug 21 10:57:21 asgard kernel: sd 0:0:0:0: [sda] tag#3 CDB: Read(10) 28 00 61 41 1d 58 00 00 08 00
Aug 21 10:57:21 asgard kernel: blk_update_request: I/O error, dev sda, sector 1631657304 op 0x0:(READ) flags 0x3000 phys_seg 1 prio class 0
Aug 21 10:57:21 asgard kernel: EXT4-fs warning (device sda1): htree_dirblock_to_tree:1027: inode #50987179: lblock 0: comm find: error -5 reading directory block
Aug 21 10:57:21 asgard kernel: ata1: EH complete
Aug 21 10:57:24 asgard kernel: ata1.00: exception Emask 0x0 SAct 0x30 SErr 0x0 action 0x0
Aug 21 10:57:24 asgard kernel: ata1.00: irq_stat 0x40000008
Aug 21 10:57:24 asgard kernel: ata1.00: failed command: READ FPDMA QUEUED
Aug 21 10:57:24 asgard kernel: ata1.00: cmd 60/08:20:c0:1d:41/00:00:61:00:00/40 tag 4 ncq dma 4096 in
                                        res 41/40:08:c0:1d:41/00:00:61:00:00/00 Emask 0x409 (media error) <F>
Aug 21 10:57:24 asgard kernel: ata1.00: status: { DRDY ERR }
Aug 21 10:57:24 asgard kernel: ata1.00: error: { UNC }
Aug 21 10:57:24 asgard kernel: ata1.00: configured for UDMA/133
Aug 21 10:57:24 asgard kernel: sd 0:0:0:0: [sda] tag#4 FAILED Result: hostbyte=DID_OK driverbyte=DRIVER_SENSE cmd_age=2s
Aug 21 10:57:24 asgard kernel: sd 0:0:0:0: [sda] tag#4 Sense Key : Medium Error [current] 
Aug 21 10:57:24 asgard kernel: sd 0:0:0:0: [sda] tag#4 Add. Sense: Unrecovered read error - auto reallocate failed
Aug 21 10:57:24 asgard kernel: sd 0:0:0:0: [sda] tag#4 CDB: Read(10) 28 00 61 41 1d c0 00 00 08 00
Aug 21 10:57:24 asgard kernel: blk_update_request: I/O error, dev sda, sector 1631657408 op 0x0:(READ) flags 0x3000 phys_seg 1 prio class 0
Aug 21 10:57:24 asgard kernel: EXT4-fs warning (device sda1): htree_dirblock_to_tree:1027: inode #50987076: lblock 0: comm find: error -5 reading directory block
Aug 21 10:57:24 asgard kernel: ata1: EH complete

=> https://wiki.archlinux.org/title/SMART

I will take a look at the URL provided for SMART, Can you advise a basic overview of what it is you are seeing?
Also is there a way I can run Journalctl to just show the errors you have highlighted?

TIA!

Offline

#6 2021-08-22 03:45:38

Trilby
Inspector Parrot
Registered: 2011-11-29
Posts: 30,500
Website

Re: I want to understand xmodmap better

What you should do is really beside the point.  We need to know what you are doing, and you are clearly not using xinit/startx with that as your xinitrc.  As I said:

Trilby wrote:

If not, then all of this is irrelevant as that xinitrc is not in use.

The premise of this thread was a question founded on "this xinitrc is trying to ..."

But that xinitrc isn't doing, or trying to do, anything at all.  It's just sitting completely unused in your /etc/ directory.

Last edited by Trilby (2021-08-22 03:47:18)


"UNIX is simple and coherent" - Dennis Ritchie; "GNU's Not Unix" - Richard Stallman

Offline

#7 2021-08-22 04:57:47

ArcticStag
Member
Registered: 2020-09-14
Posts: 46

Re: I want to understand xmodmap better

Trilby wrote:

What you should do is really beside the point.  We need to know what you are doing, and you are clearly not using xinit/startx with that as your xinitrc.  As I said:

Trilby wrote:

If not, then all of this is irrelevant as that xinitrc is not in use.

The premise of this thread was a question founded on "this xinitrc is trying to ..."

But that xinitrc isn't doing, or trying to do, anything at all.  It's just sitting completely unused in your /etc/ directory.

So I am seeing the errors when I am booting into the system. I am using the ly login manager and when I login to awesome WM it then shows the errors.

Offline

#8 2021-08-22 09:21:40

V1del
Forum Moderator
Registered: 2012-10-16
Posts: 25,310

Re: I want to understand xmodmap better

Don't use ly, it's broken and doesn't properly work with systemd sessions.

But that disclaimer out of the way, you might be able to find the errors in your ~/.xsession-errors file if it's present.

Last edited by V1del (2021-08-22 09:24:53)

Offline

#9 2021-08-22 09:25:50

seth
Member
From: Won't reply 2 private help req
Registered: 2012-09-03
Posts: 77,342

Re: I want to understand xmodmap better

The errors zip past quite quickly, however they are all related to [im]xf86-{somthing-here}[/im]

Are they in your xorg log?
https://wiki.archlinux.org/title/Xorg#General

Can you advise a basic overview of what it is you are seeing?

There's a good chance that your disk is falling apart...
https://wiki.archlinux.org/title/System … ing_output

It's from the ringbuffer, "journalctl -g" greps

Offline

#10 2021-08-22 12:00:03

ArcticStag
Member
Registered: 2020-09-14
Posts: 46

Re: I want to understand xmodmap better

V1del wrote:

Don't use ly, it's broken and doesn't properly work with systemd sessions.

But that disclaimer out of the way, you might be able to find the errors in your ~/.xsession-errors file if it's present.

Okay, So I have stopped using ly, I didn't realise there was any issue with is.

seth wrote:

There's a good chance that your disk is falling apart...

Looks like I am in the market for a new HDD then sad
Glad you it came to light before the disk really died on me

I think I will close this thread. Thank's to everyone for the advice.

Offline

#11 2021-08-22 12:14:32

2ManyDogs
Forum Fellow
Registered: 2012-01-15
Posts: 4,648

Re: I want to understand xmodmap better

Please do not mark a thread [CLOSED] -- that is used by staff when a thread is not open for further replies. If you consider your issue solved, mark the thread [SOLVED]. If you would like a thread closed or deleted, please use the Report button.

Offline

#12 2021-08-23 09:24:54

WorMzy
Administrator
From: Scotland
Registered: 2010-06-16
Posts: 13,620
Website

Re: I want to understand xmodmap better

Closing, on request.


Sakura:-
Mobo: MSI MAG X570S TORPEDO MAX // Processor: AMD Ryzen 9 5950X @4.9GHz // GFX: AMD Radeon RX 5700 XT // RAM: 32GB (4x 8GB) Corsair DDR4 (@ 3000MHz) // Storage: 1x 3TB HDD, 6x 1TB SSD, 2x 120GB SSD, 1x 275GB M2 SSD

Making lemonade from lemons since 2015.

Offline

Board footer

Powered by FluxBB