I like to use set -x in scripts to show what's going on, especially if the script is going to run in a CI/CD pipeline and I might need to debug some failure post-hoc. One annoyance with doing this is that if I want to echo some text to the user (e.g., a status message or "I'm starting to do $X") then that message gets output twice - once for the echo command itself being echoed, and then once as the output of that echo command. What's a good way to make this nicer? One solution is this:

set -x

... bunch of normal commands that get echoed

(
  # Temporarily don't echo, so we don't double-echo
  set +x
  echo "Here is my status message"
)

... rest of commands get echoed again

But the two problems with that are 1. That's a lot of machinery to write every time I want to tell the user something, and it's "non-obvious" enough that it probably requires the comment every time 2. It echoes the set +x too, which is undesirable. Is there another option that works well? Something like Make's feature of prepending an @ to suppress echoing would be great, but I've not been able to find such a feature in Bash.

So I am working on a debugger for linux s390x system and have the whole disassembler etc set up for reading the ELF file. For debugger I just run it on the process with base address from the process maps. Now when running for debugger, the process map doesn't have a read only map which would only have ELF headers and this map also does not have the ELF magic bytes in the starting unlike other systems like linux x86_64 and linux arm64. Now this affects my debugger as the addresses are set according to this. Also to set up the breakpoint ptrace provides the #define S390_BREAKPOINT_U16 ((__u16)0x0001) Now when set the this at the opcode, it hits the breakpoint correctly, but when I replace the original opcode, the opcode 4 bytes ahead gets placed at this position for some reason. I think most probably the ELF header magic bytes missing messes up stuff, even if i set the breakpoint to start of a function like main SIGILL is hit some

I'm using KDE on last debian and i get a lot of problem with the menu. I was using the kdemenu to organise the start menu, but i get a lot of trouble : Some .desktop shows in the start menu but not in kdemenu Some .desktop shows in kdemenu but not in the startmenu under the good menu Some .desktop can only be called with the search option and show nowhere else (menu or kmenuedit) I first try to look at applications-kmenuedit.menu but it's a mess, there is some old change which are keep for no reason i understand. This a test directory i made, which i deleted, but is kept :

test
   
    
    a
   
   test.directory
   
    a
    a.directory

So, i wanted to create my own .menu file, inside ~/.config/menus/applications-merged/ keeping /etc/xdg and basic kde menu file :

menu
   
    _hidden
   
   
    _new
    
      AIMP.desktop
      arduino.desktop
    
   
   
    a
    
      arduino.desktop
    
   
   
    b
     
      c
     
     
      d
      
        LTspice2.desktop
      
     
    
      test.desktop
    
   
  
    chrome-aghbiahbpaijignceidepookljebhfak-Default.desktop
  
 
Education
Web Development
Translation
Science & Math

I get that problem : - Sometimes, the start menu refresh, sometimes it seems not. xdg-desktop-menu forceupdate --mode user change nothing - "Education" menu disappear but not "Science & Math" - Some .desktop are at the good place : arduino.desktop for example, but chrome[...].desktop don't show. I don't know why, maybe some interract with others .menu file. So i'm looking for a tool or verbose to know how xdg will construct the start menu and will be able to debug my .menu file by my own. Thanks in advance, Regards,

My PC takes a long time booting. I have reason to believe it is caused by delays after grub, but before kernel logging starts (booting takes 30 seconds, but dmesg messages have time stamps between 0.00000 - 9.34223, details in [this post](https://unix.stackexchange.com/questions/499832/long-time-spent-between-grub2-menu-before-kernel-boot)) . Are there any ways to debug what's going on? In particular: * Is there a way to make grub itself more verbose, or keep logs? * Are there any other processes between grub and the kernel logging that could be taking time? How do I debug those? I believe the question is not specific to my setup. But just in case, I'm running Ubuntu 16.10 and grub(2) **EDIT**: Following a suggestion by @TooTea, I set the debug=all environment variables which produced a lot of messages a la script/script.c:50 malloc 0x7a9a2ca0 that should not be a problem. Then there is one block of messages that coincide with a 8 seconds delay delay: kern/dl.c:56 Detecting ext2... lib/relocator.c:1397 chunks = 0x7a7e0ae0 lib/relocator.c:434 trying to allocate in ...-... aligned ... size ... lib/relocator.c:1198 allocated: ...+... lib/relocator.c:1409 allocated .../... lib/relocator.c:1410 chunks = 0x7a7e0ae0

this is a post that has workaround but not an explanation ---- Sometime in last 4 weeks my LibreOffice on my debian started crashing. Not producing window with eg. LOWriter, just a "crashed docs recovery" and a Soffice start window "choose from recent docs, create new" I think it's not relevant, but reported version is "LibreOffice 25.2.3.2 520(Build:2)" on debian trixie indication was only this error output in console

> soffice --writer                                                                                                                                     (base) 
terminate called after throwing an instance of 'std::bad_alloc'
  what():  std::bad_alloc

# or at most

> lowriter                                                                                                                                             (base) 
terminate called after throwing an instance of 'std::bad_alloc'
  what():  std::bad_alloc
terminate called after throwing an instance of 'std::bad_alloc'
  what():  std::bad_alloc
terminate called recursively

no other indication, running with --backtrace yielded no success either (i can share the log, or strace log as well) **However once I cleared env and removed "miniconda3 init code" from .bashrc it started working** Can anybody please think of 1. explanation 2. proper way to detect/debug this kind of issue (since neither strace, gdb or anything helped me) Thank you

I am trying to understand the SATA Host-Device Communication and for that I have put a lot of debug messages in the kernel driver code. Now messages are in such a huge amount that I am not able to see the initial messages of the device enumeration in the dmesg log. For the same I have modified CONFIG_LOG_BUF_SHIFT(=21) config variable to increase the ring buffer size from where dmesg takes the message but still I am facing the same issue. So, Is there any method available by which I can log all the dmesg from the kernel boot in to a specific file? Thanks for the Help in advance.

Is there a log file I can peruse, or settings somewhere that might give me a clue? I'm running GNOME nautilus 3.14.3 ("Files") in Ubuntu 16.04.

During a routine

pacman -Syu --needed

involving about 50 packages, the upgrade exited early due to a "Less than 1 b/s transferred the last 10 seconds" error. Follwing that, I can no longer update my system.

$ sudo pacman -Syu --debug
debug: pacman v7.0.0 - libalpm v15.0.0
debug: config: new section 'options'
debug: config: HoldPkg: pacman
debug: config: HoldPkg: glibc
debug: config: Architecture: auto
debug: config: arch: x86_64
debug: config: verbosepkglists
debug: config: sandboxuser: alpm
debug: config: SigLevel: Required
debug: config: SigLevel: DatabaseOptional
debug: config: LocalFileSigLevel: Optional
debug: config: new section 'core-testing'
debug: config file /etc/pacman.conf, line 75: including /etc/pacman.d/mirrorlist
debug: config: new section 'core'
debug: config file /etc/pacman.conf, line 78: including /etc/pacman.d/mirrorlist
debug: config: new section 'extra-testing'
debug: config file /etc/pacman.conf, line 81: including /etc/pacman.d/mirrorlist
debug: config: new section 'extra'
debug: config file /etc/pacman.conf, line 84: including /etc/pacman.d/mirrorlist
debug: config: new section 'multilib-testing'
debug: config file /etc/pacman.conf, line 90: including /etc/pacman.d/mirrorlist
debug: config: new section 'multilib'
debug: config file /etc/pacman.conf, line 93: including /etc/pacman.d/mirrorlist
debug: config: finished parsing /etc/pacman.conf
debug: setup_libalpm called
debug: option 'logfile' = /var/log/pacman.log
debug: option 'gpgdir' = /etc/pacman.d/gnupg/
debug: option 'hookdir' = /etc/pacman.d/hooks/
debug: option 'cachedir' = /var/cache/pacman/pkg/
debug: registering sync database 'core-testing'
debug: database path for tree core-testing set to /var/lib/pacman/sync/core-testing.db
debug: "/var/lib/pacman/sync/core-testing.db.sig" is not readable: No such file or directory
debug: sig path /var/lib/pacman/sync/core-testing.db.sig could not be opened
debug: got error 43 at _alpm_gpgme_checksig (../lib/libalpm/signing.c: 599) : missing PGP signature
debug: missing optional signature
debug: setting usage of 15 for core-testing repository
debug: adding new server URL to database 'core-testing': ...
debug: registering sync database 'core'
debug: database path for tree core set to /var/lib/pacman/sync/core.db
debug: "/var/lib/pacman/sync/core.db.sig" is not readable: No such file or directory
debug: sig path /var/lib/pacman/sync/core.db.sig could not be opened
debug: got error 43 at _alpm_gpgme_checksig (../lib/libalpm/signing.c: 599) : missing PGP signature
debug: missing optional signature
debug: setting usage of 15 for core repository
debug: adding new server URL to database 'core': ...
debug: registering sync database 'extra-testing'
debug: database path for tree extra-testing set to /var/lib/pacman/sync/extra-testing.db
debug: "/var/lib/pacman/sync/extra-testing.db.sig" is not readable: No such file or directory
debug: sig path /var/lib/pacman/sync/extra-testing.db.sig could not be opened
debug: got error 43 at _alpm_gpgme_checksig (../lib/libalpm/signing.c: 599) : missing PGP signature
debug: missing optional signature
debug: setting usage of 15 for extra-testing repository
debug: adding new server URL to database 'extra-testing': ...
debug: registering sync database 'extra'
debug: database path for tree extra set to /var/lib/pacman/sync/extra.db
debug: "/var/lib/pacman/sync/extra.db.sig" is not readable: No such file or directory
debug: sig path /var/lib/pacman/sync/extra.db.sig could not be opened
debug: got error 43 at _alpm_gpgme_checksig (../lib/libalpm/signing.c: 599) : missing PGP signature
debug: missing optional signature
debug: setting usage of 15 for extra repository
debug: adding new server URL to database 'extra': ...
debug: registering sync database 'multilib-testing'
debug: database path for tree multilib-testing set to /var/lib/pacman/sync/multilib-testing.db
debug: "/var/lib/pacman/sync/multilib-testing.db.sig" is not readable: No such file or directory
debug: sig path /var/lib/pacman/sync/multilib-testing.db.sig could not be opened
debug: got error 43 at _alpm_gpgme_checksig (../lib/libalpm/signing.c: 599) : missing PGP signature
debug: missing optional signature
debug: setting usage of 15 for multilib-testing repository
debug: adding new server URL to database 'multilib-testing': ...
debug: registering sync database 'multilib'
debug: database path for tree multilib set to /var/lib/pacman/sync/multilib.db
debug: "/var/lib/pacman/sync/multilib.db.sig" is not readable: No such file or directory
debug: sig path /var/lib/pacman/sync/multilib.db.sig could not be opened
debug: got error 43 at _alpm_gpgme_checksig (../lib/libalpm/signing.c: 599) : missing PGP signature
debug: missing optional signature
debug: setting usage of 15 for multilib repository
debug: adding new server URL to database 'multilib': ...
debug: option 'sandboxuser' = alpm
:: Synchronizing package databases...
 core-testing downloading...
 core downloading...
 extra-testing downloading...
 extra downloading...
 multilib-testing downloading...
 multilib downloading...
debug: filesystem access has been restricted to /var/lib/pacman/sync/download-T96Kmv/, landlock ABI is 6
debug: core-testing.db: url is ...
debug: core-testing.db: maxsize 134217728
debug: core-testing.db: using time condition 1747924883
debug: core-testing.db: opened tempfile for download: /var/lib/pacman/sync/download-T96Kmv/core-testing.db.part (wb)
debug: core.db: url is ...
debug: core.db: maxsize 134217728
debug: core.db: using time condition 1747897677
debug: core.db: opened tempfile for download: /var/lib/pacman/sync/download-T96Kmv/core.db.part (wb)
debug: extra-testing.db: url is ...
debug: extra-testing.db: maxsize 134217728
debug: extra-testing.db: using time condition 1747924860
debug: extra-testing.db: opened tempfile for download: /var/lib/pacman/sync/download-T96Kmv/extra-testing.db.part (wb)
debug: extra.db: url is ...
debug: extra.db: maxsize 134217728
debug: extra.db: using time condition 1747924853
debug: extra.db: opened tempfile for download: /var/lib/pacman/sync/download-T96Kmv/extra.db.part (wb)
debug: multilib-testing.db: url is ...
debug: multilib-testing.db: maxsize 134217728
debug: multilib-testing.db: using time condition 1747924908
debug: multilib-testing.db: opened tempfile for download: /var/lib/pacman/sync/download-T96Kmv/multilib-testing.db.part (wb)
debug: multilib.db: url is ...
debug: multilib.db: maxsize 134217728
debug: multilib.db: using time condition 1747924908
debug: multilib.db: opened tempfile for download: /var/lib/pacman/sync/download-T96Kmv/multilib.db.part (wb)
debug: multilib-testing.db: curl returned result 0 from transfer
debug: multilib-testing.db: response code 304
debug: multilib-testing.db.sig: url is ...
debug: multilib-testing.db.sig: maxsize 16384
debug: multilib-testing.db.sig: opened tempfile for download: /var/lib/pacman/sync/download-T96Kmv/multilib-testing.db.sig.part (wb)
debug: multilib-testing.db: file met time condition
debug: core-testing.db: curl returned result 0 from transfer
debug: core-testing.db: response code 304
debug: core-testing.db.sig: url is ...
debug: core-testing.db.sig: maxsize 16384
debug: core-testing.db.sig: opened tempfile for download: /var/lib/pacman/sync/download-T96Kmv/core-testing.db.sig.part (wb)
debug: core-testing.db: file met time condition
debug: extra-testing.db: curl returned result 0 from transfer
debug: extra-testing.db: response code 304
debug: extra-testing.db.sig: url is ...
debug: extra-testing.db.sig: maxsize 16384
debug: extra-testing.db.sig: opened tempfile for download: /var/lib/pacman/sync/download-T96Kmv/extra-testing.db.sig.part (wb)
debug: extra-testing.db: file met time condition
debug: multilib.db: curl returned result 0 from transfer
debug: multilib.db: response code 304
debug: multilib.db.sig: url is ...
debug: multilib.db.sig: maxsize 16384
debug: multilib.db.sig: opened tempfile for download: /var/lib/pacman/sync/download-T96Kmv/multilib.db.sig.part (wb)
debug: multilib.db: file met time condition
debug: extra.db: curl returned result 0 from transfer
debug: extra.db: response code 304
debug: extra.db.sig: url is ...
debug: extra.db.sig: maxsize 16384
debug: extra.db.sig: opened tempfile for download: /var/lib/pacman/sync/download-T96Kmv/extra.db.sig.part (wb)
debug: extra.db: file met time condition
debug: core.db: curl returned result 0 from transfer
debug: core.db: response code 200
debug: core.db.sig: url is ...
debug: core.db.sig: maxsize 16384
debug: core.db.sig: opened tempfile for download: /var/lib/pacman/sync/download-T96Kmv/core.db.sig.part (wb)
debug: multilib-testing.db.sig: curl returned result 0 from transfer
debug: multilib-testing.db.sig: response code 404
debug: multilib-testing.db.sig: no more servers to retry
debug: core-testing.db.sig: curl returned result 0 from transfer
debug: core-testing.db.sig: response code 404
debug: core-testing.db.sig: no more servers to retry
debug: extra-testing.db.sig: curl returned result 0 from transfer
debug: extra-testing.db.sig: response code 404
debug: extra-testing.db.sig: no more servers to retry
debug: multilib.db.sig: curl returned result 0 from transfer
debug: multilib.db.sig: response code 404
debug: multilib.db.sig: no more servers to retry
debug: extra.db.sig: curl returned result 0 from transfer
debug: extra.db.sig: response code 404
debug: extra.db.sig: no more servers to retry
debug: core.db.sig: curl returned result 0 from transfer
debug: core.db.sig: response code 404
debug: core.db.sig: no more servers to retry
debug: curl_download_internal return code is 0
debug: "/var/lib/pacman/sync/core-testing.db.sig" is not readable: No such file or directory
debug: sig path /var/lib/pacman/sync/core-testing.db.sig could not be opened
debug: got error 43 at _alpm_gpgme_checksig (../lib/libalpm/signing.c: 599) : missing PGP signature
debug: missing optional signature
debug: "/var/lib/pacman/sync/core.db.sig" is not readable: No such file or directory
debug: sig path /var/lib/pacman/sync/core.db.sig could not be opened
debug: got error 43 at _alpm_gpgme_checksig (../lib/libalpm/signing.c: 599) : missing PGP signature
debug: missing optional signature
debug: "/var/lib/pacman/sync/extra-testing.db.sig" is not readable: No such file or directory
debug: sig path /var/lib/pacman/sync/extra-testing.db.sig could not be opened
debug: got error 43 at _alpm_gpgme_checksig (../lib/libalpm/signing.c: 599) : missing PGP signature
debug: missing optional signature
debug: "/var/lib/pacman/sync/extra.db.sig" is not readable: No such file or directory
debug: sig path /var/lib/pacman/sync/extra.db.sig could not be opened
debug: got error 43 at _alpm_gpgme_checksig (../lib/libalpm/signing.c: 599) : missing PGP signature
debug: missing optional signature
debug: "/var/lib/pacman/sync/multilib-testing.db.sig" is not readable: No such file or directory
debug: sig path /var/lib/pacman/sync/multilib-testing.db.sig could not be opened
debug: got error 43 at _alpm_gpgme_checksig (../lib/libalpm/signing.c: 599) : missing PGP signature
debug: missing optional signature
debug: "/var/lib/pacman/sync/multilib.db.sig" is not readable: No such file or directory
debug: sig path /var/lib/pacman/sync/multilib.db.sig could not be opened
debug: got error 43 at _alpm_gpgme_checksig (../lib/libalpm/signing.c: 599) : missing PGP signature
debug: missing optional signature
:: Starting full system upgrade...
debug: checking for package upgrades
debug: loading package cache for repository 'local'
debug: added 4080 packages to package cache for db 'local'
debug: searching for replacements for 7zip in core-testing
debug: loading package cache for repository 'core-testing'
debug: opening archive /var/lib/pacman/sync/core-testing.db
debug: added 8 packages to package cache for db 'core-testing'
debug: searching for replacements for 7zip in core
...
debug: searching for replacements for zziplib in extra
resolving dependencies...
debug: resolving target's dependencies
debug: started resolving dependencies
debug: checkdeps: package alsa-card-profiles-1:1.4.3-1
debug: finished resolving dependencies
debug: started resolving dependencies
...
debug: found cached pkg: /var/cache/pacman/pkg/wxwidgets-gtk3-3.2.8-5-x86_64.pkg.tar.zst
debug: setting download size 0 for pkg wxwidgets-gtk3
debug: sorting by dependencies
debug: started sorting dependencies
debug: sorting dependencies finished

Package (52)                            Old Version            New Version         Net Change

extra-testing/alsa-card-profiles        1:1.4.2-1              1:1.4.3-1             0.00 MiB
...
extra/wxwidgets-gtk3                    3.2.8-4                3.2.8-5               0.00 MiB

Total Installed Size:  6806.07 MiB
Net Upgrade Size:        22.29 MiB

:: Proceed with installation? [Y/n] y
debug: using cachedir: /var/cache/pacman/pkg/
...
debug: found cached pkg: /var/cache/pacman/pkg/wxwidgets-gtk3-3.2.8-5-x86_64.pkg.tar.zst.sig
debug: checking available disk space for download
debug: discovered mountpoint: /tmp
debug: discovered mountpoint: /sys/kernel/tracing
debug: discovered mountpoint: /sys/kernel/security
debug: discovered mountpoint: /sys/kernel/debug
debug: discovered mountpoint: /sys/kernel/config
debug: discovered mountpoint: /sys/fs/pstore
debug: discovered mountpoint: /sys/fs/fuse/connections
debug: discovered mountpoint: /sys/fs/cgroup
debug: discovered mountpoint: /sys/fs/bpf
debug: discovered mountpoint: /sys/firmware/efi/efivars
debug: discovered mountpoint: /sys
debug: discovered mountpoint: /run/user/1000/gvfs
debug: discovered mountpoint: /run/user/1000/doc
debug: discovered mountpoint: /run/user/1000
debug: discovered mountpoint: /run/credentials/systemd-journald.service
debug: discovered mountpoint: /run
debug: discovered mountpoint: /proc/sys/fs/binfmt_misc
debug: discovered mountpoint: /proc
debug: discovered mountpoint: /efi
debug: discovered mountpoint: /dev/shm
debug: discovered mountpoint: /dev/pts
debug: discovered mountpoint: /dev/mqueue
debug: discovered mountpoint: /dev/hugepages
debug: discovered mountpoint: /dev
debug: discovered mountpoint: /
debug: loading fsinfo for /
debug: partition /, needed 1, cushion 5121, free ...
:: Retrieving packages...
debug: filesystem access has been restricted to /var/cache/pacman/pkg/download-JFrr96/, landlock ABI is 6
debug: pacman-mirrorlist-20250522-1-any.pkg.tar.zst: url is ...
debug: pacman-mirrorlist-20250522-1-any.pkg.tar.zst: maxsize 8292
debug: pacman-mirrorlist-20250522-1-any.pkg.tar.zst: tempfile found, attempting continuation from 8292 bytes
debug: curl_download_internal return code is 1
checking keyring...
debug: found signature key: B8AC08600F108CDF
debug: GPGME version: 1.24.3
debug: GPGME engine info: file=/usr/bin/gpg, home=/etc/pacman.d/gnupg/
debug: looking up key B8AC08600F108CDF locally
debug: key lookup success, key exists
debug: found signature key: 7A4E76095D8A52E4
...
checking package integrity...
debug: found cached pkg: /var/cache/pacman/pkg/alsa-card-profiles-1:1.4.3-1-x86_64.pkg.tar.zst
debug: sig data: iHUEABYKAB0WIQSDvIiJNRtd67toQW64rAhgDxCM3wUCaC8FsAAKCRC4rAhgDxCM33urAPsE9Ltb4WNKoutXEfcyjzQ47EVtE/zcHvVSvaiB2qXPlAEA0/OpOs08AK2vp0HPwNBFq9ETVrM1EpMg7PaDzeVY9wA=
debug: checking signature for /var/cache/pacman/pkg/alsa-card-profiles-1:1.4.3-1-x86_64.pkg.tar.zst
debug: 1 signatures returned
debug: fingerprint: 83BC8889351B5DEBBB68416EB8AC08600F108CDF
debug: summary: valid
debug: summary: green
debug: status: Success
debug: timestamp: 1747912112
debug: exp_timestamp: 0
debug: validity: full; reason: Success
debug: key: 83BC8889351B5DEBBB68416EB8AC08600F108CDF, Jan Alexander Steffens (heftig) , owner_trust unknown, disabled 0
debug: signature is valid
debug: signature is fully trusted
...
error: pacman-mirrorlist: could not find package in cache
debug: returning error 33 from check_validity (../lib/libalpm/sync.c: 1021) : could not find or read package
error: failed to commit transaction (could not find or read package)
Errors occurred, no packages were upgraded.
debug: unregistering database 'local'
...
debug: freeing package cache for repository 'multilib'

I am working on a process that forks several times. To debug it, I am using a debug file for which I open a fd and which stays the same for all child forks. Then I have a function print_debug, that will print to that fd. Now when the main process and the childs are printing at the same time, the output is intertwined in the debug file. I tried to solve that via a flock(fd, LOCK_EX), but that seems to have no effect. Here is an excerpt from the print_debug function:

void	print_debug(int fd, char *msg)
{
	
	flock(fd, LOCK_EX);
	print_debug2("... LOCK ACQUIRED ...");
    
    ... printing msg ...
    flock(fd, LOCK_UN);
}

Now when several forks print at the same time, the output looks like this:

--12692-- ... LOCK ACQUIRED ...
--12692-- fork no wait with fd_in 4, fd_out 1 and fd_close
----121269694-2-- - ..... . LOLOCKCK A ACQCQUIUIRERED D .....
.
----121269694-2-- - exriecghutt e sitrdeee o
f pipe started
--12694---- 12.69..2- - LO..CK.  ALOCQCUIK RACED Q..UI.
RE--D 12..69.4-
- --fd12 69ou2-t-  ifs orck urwreaintt
ly: 1
----121269692-4-- - ...... L LOCOCK K ACACQUQUIRIREDED . .....

----121269692-4-- - fofdrk o nuto  owan itcm wdit ch atfd i_is n cu0,rr fend_tlouy:t  15 
and fd_close
--126--9412--69 .6-..-  L..OC. K LOACCKQU AICQREUD IR..ED. .
.--.
12--69124-69- 6-er- rnexo ec2
ute tree
--1269--412--69 6-..- . ..LO.CK  ALOCCKQU IRACEQUDIR ED.. ..
.--.
12--6129694-6- --c fmdd_e oxutec iuts edcu rrfrenomtl y:ex ec5

Clearly, the printing of "lock acquired" overlap. I also controlled the return value of flock, which is always 0 (success). Does flock work in a situation like this? Why do I still have the issues of garbled messages in the log file?

Distribution: Arch Linux OBS Version: 31.0.3 Kernel Version: 6.14.2-arch1-1 v4l2loopback-utils Version: 0.14.0-1 vulkan-radeon Version: 25.0.3-1

> v4l2-ctl --list-devices
OBS Virtual Camera (platform:v4l2loopback-000):
    /dev/video2

Laptop Camera: Laptop Camera (usb-0000:c4:00.4-1):
    /dev/video0
    /dev/video1
    /dev/media0

When I click "Start Virtual Camera" on OBS Studio I get the "Failed to start virtual camera" error. Checking the logs, I see "Failed to start streaming on '/dev/video2' (Invalid argument)." I tried downgrading to 0.13.2-1.

> sudo downgrade v4l2loopback-dkms
> sudo downgrade v4l2loopback-utils
> sudo rmmod -f v4l2loopback
> sudo modprobe v4l2loopback

I could start the Virtual Camera, but Google Meet and other conferencing software could not detect my virtual camera anymore. also some other programs need v4l2 so I can no longer keep it in the downgraded state. Are there any fixes other than waiting for OBS to correct their code?

I had purchased two Fluke Etherscopes, these are stuck with the message 'Loading Kernel' on the screen. I was able to get a serial console, and access the bootloader using the serial port on the side of the device. I can access the bootloader (Intrinsyc Bootloader) and have tried to use the update files to install a new kernel. It installs successfully to the flash memory, and then tries to boot. I have tried to pass kernel boot parameters through the boot command, and get no output what so ever. I have successfully identified the JTAG pins, except for the nTRST pin, pretty sure I know which pin, but showing a diode between the pad and the suspected pin. I have flashed the Black Magic Probe firmware and bootloader to my STM32F104 development board, it has a logic level of 3.3v, and so does the CPU. I know which pins to attach the BMP to, but I am not sure where to go from here. I have tried looking for information on debugging the Linux kernel through JTAG, and GDB, but nothing that I see as very clear. I found multiple firmware update files for this device, and also found some source code, both on a public fluke ftp site. I have tried to contact Fluke for service information, and they told me to reach out to NetScout, who say that Fluke never gave them that information. I am attaching the serial printout from when I press the power button to where it stops outputting and just shows the loading kernel screen. I would like to at least get an idea of what I can research in order to get either debug output to the serial console, or debug output through the JTAG port and the BMP firmware. The CPU is the Intel XScale PXA255. I know that when a CF card is inserted with a file with the name 'ZIMAGE', it tries to load it as a 'Debug Kernel' into RAM, and then points to it for execution. If there is anymore information I can give anyone, please let me know. I bought these devices broken so that I can learn while trying to fix them, and would really like to get them up and running. Again, any information I can pass along, please let me know and I will post it. Thank you all for your time. **Serial Output from Boot:**

**************************************************
** Intrinsyc Bootloader (IBoot)                 **
** Copyright 2001,2002 Intrinsyc Software Inc.  **
** Version: 2.0                                 **
** Support: http://www.intrinsyc.com             **
**************************************************
Enabling LCD controller
Setting Registers in the EPSON Controller!!
Finished Setting Registers in the EPSON Controller!!
MCMEM0 : 0x0002449D
MCATT0 : 0x0002449D
MCIO0  : 0x00014290
MECR   : 0x00000000
MCCR : 0x00000001
GPLR0 : CFF79FFD
PCMCIA Detected 0 Slots.
setup def img : Image Offset : 70
Image Size X : 294 Y : 70
img done
Loading TXRX Xilinx.
TXRX Xilinx Complete.
reseting PHY
We Should Auto Negociate
Phy Control Register = 0x0000FFFF
Phy ID Register one = 0x0000FFFF
Phy ID Register two = 0x0000FFFF
Phy STAT Register = 0x0000FFFF
Xilinx TXRX Reg : 0x003C3B3C
Leaving init_ethernet
IBoot> help
boot, bootmem, copy, crc, createfis, decode, download,
eraseflash, exec, flash, flashloader, flashverify, getbyte, getword,
getdword, help, info, jump, memtest, ping, reboot,
save, setbyte, setword, setdword, set, set gw, set hwrev,
set option, set initpwr, set ip, set mac, set mask, set mfgdate, set mfgtest,
set model, set serial, set server, set speed, set trial, show, reflash
IBoot> boot
Board Control Regs : 0x00000042
Loading PCMCIA Xilinx.
Waiting for Xilinx INIT pin low.
Waiting for Xilinx INIT pin high.
Writing data to Xilinx.
Waiting for Done High.
Relocating zImage from 000C0000 to A0008000 (len=00100000)
Proper ARM zImage ID found. Booting...
Uncompressing Linux............................................................... done, booting the kernel.

I came across the following kernel log entry showing a task named Scanner-0 in an unexpected state, along with a call trace involving kvm_async_pf_task_wait_schedule and a page fault.

[320099.377111] task:Scanner-0       state:D stack:0     pid:2798  ppid:1      flags:0x00000084
[320099.377247] Call Trace:
[320099.377368]  __schedule+0x2d1/0x870
[320099.377491]  schedule+0x55/0xf0
[320099.377610]  kvm_async_pf_task_wait_schedule+0x15c/0x1a0
[320099.377740]  __kvm_handle_async_pf+0x4c/0x90
[320099.377880]  do_page_fault+0x7b/0x12d
... (additional registers and RIP details)

Is this a known process (e.g. kernel module)? I couldn’t find definitive references. Any tips on tracing this further? The state:D suggests it’s in an uninterruptible sleep state which could indicate a deadlock or I/O wait.

I am trying to analyze a VMware memory dump from an AlmaLinux guest. I converted the snapshot to a core dump using vmss2core:

vmss2core-sb-8456865.exe -N vSRV1_Snapshot815.vmsn vSRV1_Snapshot815.vmem

Then, I installed the necessary tools for crash dump analysis:

sudo dnf install yum-utils -y
sudo dnf install kexec-tools crash gdb -y
sudo dnf debuginfo-install kernel-debuginfo-$(uname -r) -y

However, when I try to analyze the dump with crash, I get an error:

crash /usr/lib/debug/lib/modules/4.18.0-553.34.1.el8_10.x86_64/vmlinux /home2/memdump/vmss.core
crash: cannot resolve "p2m_top"

Any advice on how to properly analyze this dump or work around the p2m_top error? Thanks.

My ext-4 root and home filesystem became suddently read-only. How can I find out what was the reason for this? The system is ubuntu 16.04 with systemd (installed on an ssd), where root and home partition are encrypted with dm-crypt and formatted with an ext-4 fs. **Edit** Just after I wrote this post the system crashed again (two times) with a slightly blinking black/colored screen. Now it seems to work again. The /etc/fstab contains for the root partition the mount option errors=remount-ro The smartctl -a /dev/sda gives smartctl -a /dev/sda smartctl 6.5 2016-01-24 r4214 [x86_64-linux-4.4.0-21-generic] (local build) Copyright (C) 2002-16, Bruce Allen, Christian Franke, www.smartmontools.org === START OF INFORMATION SECTION === Device Model: SAMSUNG MZ7PC256HAFU-000L7 Serial Number: S0Y5NSAC602442 Firmware Version: CXM72L1Q User Capacity: 256,060,514,304 bytes [256 GB] Sector Size: 512 bytes logical/physical Rotation Rate: Solid State Device Device is: Not in smartctl database [for details use: -P showall] ATA Version is: ATA8-ACS T13/1699-D revision 4c SATA Version is: SATA 3.0, 6.0 Gb/s (current: 6.0 Gb/s) Local Time is: Mon May 23 17:07:40 2016 UTC SMART support is: Available - device has SMART capability. SMART support is: Enabled === START OF READ SMART DATA SECTION === SMART overall-health self-assessment test result: PASSED General SMART Values: Offline data collection status: (0x02) Offline data collection activity was completed without error. Auto Offline Data Collection: Disabled. Self-test execution status: ( 0) The previous self-test routine completed without error or no self-test has ever been run. Total time to complete Offline data collection: ( 1020) seconds. Offline data collection capabilities: (0x5b) SMART execute Offline immediate. Auto Offline data collection on/off support. Suspend Offline collection upon new command. Offline surface scan supported. Self-test supported. No Conveyance Self-test supported. Selective Self-test supported. SMART capabilities: (0x0003) Saves SMART data before entering power-saving mode. Supports SMART auto save timer. Error logging capability: (0x01) Error logging supported. General Purpose Logging supported. Short self-test routine recommended polling time: ( 2) minutes. Extended self-test routine recommended polling time: ( 17) minutes. SMART Attributes Data Structure revision number: 1 Vendor Specific SMART Attributes with Thresholds: ID# ATTRIBUTE_NAME FLAG VALUE WORST THRESH TYPE UPDATED WHEN_FAILED RAW_VALUE 9 Power_On_Hours 0x0032 098 098 000 Old_age Always - 6093 12 Power_Cycle_Count 0x0032 097 097 000 Old_age Always - 2810 175 Program_Fail_Count_Chip 0x0032 100 100 010 Old_age Always - 0 176 Erase_Fail_Count_Chip 0x0032 100 100 010 Old_age Always - 0 177 Wear_Leveling_Count 0x0013 095 095 017 Pre-fail Always - 169 178 Used_Rsvd_Blk_Cnt_Chip 0x0013 094 094 010 Pre-fail Always - 230 179 Used_Rsvd_Blk_Cnt_Tot 0x0013 094 094 010 Pre-fail Always - 450 180 Unused_Rsvd_Blk_Cnt_Tot 0x0013 094 094 010 Pre-fail Always - 7614 181 Program_Fail_Cnt_Total 0x0032 100 100 010 Old_age Always - 0 182 Erase_Fail_Count_Total 0x0032 100 100 010 Old_age Always - 0 183 Runtime_Bad_Block 0x0013 100 100 010 Pre-fail Always - 0 184 End-to-End_Error 0x0033 100 100 097 Pre-fail Always - 0 187 Reported_Uncorrect 0x0032 100 100 000 Old_age Always - 0 190 Airflow_Temperature_Cel 0x0032 066 042 000 Old_age Always - 34 195 Hardware_ECC_Recovered 0x001a 200 200 000 Old_age Always - 0 198 Offline_Uncorrectable 0x0030 100 100 000 Old_age Offline - 0 199 UDMA_CRC_Error_Count 0x003e 253 253 000 Old_age Always - 1 233 Media_Wearout_Indicator 0x003a 200 200 000 Old_age Always - 0 234 Unknown_Attribute 0x0012 100 100 000 Old_age Always - 0 235 Unknown_Attribute 0x0012 099 099 000 Old_age Always - 48 236 Unknown_Attribute 0x0012 099 099 000 Old_age Always - 48 237 Unknown_Attribute 0x0012 099 099 000 Old_age Always - 169 238 Unknown_Attribute 0x0012 099 099 000 Old_age Always - 450 SMART Error Log Version: 1 No Errors Logged SMART Self-test log structure revision number 1 Num Test_Description Status Remaining LifeTime(hours) LBA_of_first_error # 1 Extended offline Completed without error 00% 6092 - SMART Selective self-test log data structure revision number 1 SPAN MIN_LBA MAX_LBA CURRENT_TEST_STATUS 1 0 0 Not_testing 2 0 0 Not_testing 3 0 0 Not_testing 4 0 0 Not_testing 5 0 0 Not_testing Selective self-test flags (0x0): After scanning selected spans, do NOT read-scan remainder of disk. If Selective self-test is pending on power-up, resume after 0 minute delay.

**Problem** [steam-1.0.0.82-1.fc41.i686 from RPMFusion](https://fedora.pkgs.org/41/rpmfusion-nonfree-updates-x86_64/steam-devices-1.0.0.82-1.fc41.i686.rpm.html) is crashing for me upon startup (when invoked from $HOME/.local/share/applications/steam.desktop). An example of this is visible at [youtu.be/jZQqvgGneSc](https://www.youtube.com/watch?v=jZQqvgGneSc#:~:text=0:06%20/%200:15-,+2024%2D12%2D04T00:24:48+00:00%5BEurope/London%5D%5Bca%2Diso8601%5D,-Unlisted) . As the undermentioned .KCrash file demonstrates drkonqi-coredump-gui doesn't produce a useful trace for it: ~~~YAML PID: 160667 (steamwebhelper) UID: 1000 (RokeJulianLockhart) GID: 1000 (RokeJulianLockhart) Signal: 11 (SEGV) Timestamp: Tue 2024-12-03 17:56:53 GMT (3h 37min ago) Command Line: ./steamwebhelper -lang=en_US -cachedir=/home/RokeJulianLockhart/.local/share/Steam/config/htmlcache -steampid=159838 -buildid=1731433018 -steamid=76561198832168690 -logdir=/home/RokeJulianLockhart/.local/share/Steam/logs -uimode=7 -startcount=1 -steamuniverse=Public -realm=Global -clientui=/home/RokeJulianLockhart/.local/share/Steam/clientui -steampath=/home/RokeJulianLockhart/.local/share/Steam/ubuntu12_32/steam -launcher=0 -no-restart-on-ui-mode-change --valve-enable-site-isolation --enable-smooth-scrolling --password-store=basic --log-file=/home/RokeJulianLockhart/.local/share/Steam/logs/cef_log.txt --disable-quick-menu --enable-features=PlatformHEVCDecoderSupport --disable-features=SpareRendererForSitePerProcess,DcheckIsFatal,ValveFFmpegAllowLowDelayHEVC Executable: /home/RokeJulianLockhart/.local/share/Steam/ubuntu12_64/steamwebhelper Control Group: /user.slice/user-1000.slice/user@1000.service/app.slice/app-steam@16d13b83ca27431bab21f6fb66833e8e.service Unit: user@1000.service User Unit: app-steam@16d13b83ca27431bab21f6fb66833e8e.service Slice: user-1000.slice Owner UID: 1000 (RokeJulianLockhart) Boot ID: c12448e213c144b18ffc5a0816158a6a Machine ID: 8962ec69d8de46f6b8ebc778a4ca76cb Hostname: SNRW3Q Storage: /var/lib/systemd/coredump/core.steamwebhelper.1000.c12448e213c144b18ffc5a0816158a6a.160667.1733248613000000.zst (present) Size on Disk: 6.6M Message: Process 160667 (steamwebhelper) of user 1000 dumped core. Module /run/host/usr/lib64/libxcb-glx.so.0.0.0 from rpm libxcb-1.17.0-3.fc41.x86_64 Module /run/host/usr/lib64/libGLX_mesa.so.0.0.0 from rpm mesa-24.2.8-1.fc41.x86_64 Module /run/host/usr/lib64/libXxf86vm.so.1.0.0 from rpm libXxf86vm-1.1.5-7.fc41.x86_64 Module /run/host/usr/lib64/libudev.so.1.7.9 from rpm systemd-256.9-2.fc41.x86_64 Module /run/host/usr/lib64/libcap.so.2.70 from rpm libcap-2.70-4.fc41.x86_64 Module /run/host/usr/lib64/libwayland-client.so.0.23.0 from rpm wayland-1.23.0-2.fc41.x86_64 Module /run/host/usr/lib64/libxml2.so.2.12.8 from rpm libxml2-2.12.8-2.fc41.x86_64 Module /run/host/usr/lib64/libunistring.so.5.0.0 from rpm libunistring-1.1-8.fc41.x86_64 Module /run/host/usr/lib64/libedit.so.0.0.74 from rpm libedit-3.1-53.20240808cvs.fc41.x86_64 Module /run/host/usr/lib64/libpciaccess.so.0.11.1 from rpm libpciaccess-0.16-13.fc41.x86_64 Module /run/host/usr/lib64/libffi.so.8.1.4 from rpm libffi-3.4.6-3.fc41.x86_64 Module /run/host/usr/lib64/libxcb-dri2.so.0.0.0 from rpm libxcb-1.17.0-3.fc41.x86_64 Module /run/host/usr/lib64/libdrm_intel.so.1.123.0 from rpm libdrm-2.4.123-1.fc41.x86_64 Module /run/host/usr/lib64/libdrm_amdgpu.so.1.123.0 from rpm libdrm-2.4.123-1.fc41.x86_64 Module /run/host/usr/lib64/libelf-0.192.so from rpm elfutils-0.192-6.fc41.x86_64 Module /run/host/usr/lib64/libdrm_radeon.so.1.123.0 from rpm libdrm-2.4.123-1.fc41.x86_64 Module /run/host/usr/lib64/libsensors.so.4.5.0 from rpm lm_sensors-3.6.0-20.fc41.x86_64 Module /run/host/usr/lib64/libxshmfence.so.1.0.0 from rpm libxshmfence-1.3.2-5.fc41.x86_64 Module /run/host/usr/lib64/libxcb-sync.so.1.0.0 from rpm libxcb-1.17.0-3.fc41.x86_64 Module /run/host/usr/lib64/libxcb-xfixes.so.0.0.0 from rpm libxcb-1.17.0-3.fc41.x86_64 Module /run/host/usr/lib64/libxcb-present.so.0.0.0 from rpm libxcb-1.17.0-3.fc41.x86_64 Module /run/host/usr/lib64/libxcb-dri3.so.0.1.0 from rpm libxcb-1.17.0-3.fc41.x86_64 Module /run/host/usr/lib64/libX11-xcb.so.1.0.0 from rpm libX11-1.8.10-2.fc41.x86_64 Module /run/host/usr/lib64/libglapi.so.0.0.0 from rpm mesa-24.2.8-1.fc41.x86_64 Module /run/host/usr/lib64/libidn2.so.0.4.0 from rpm libidn2-2.3.7-2.fc41.x86_64 Module /run/host/usr/lib64/libzstd.so.1.5.6 from rpm zstd-1.5.6-2.fc41.x86_64 Module /run/host/usr/lib64/liblzma.so.5.6.2 from rpm xz-5.6.2-2.fc41.x86_64 Module /run/host/usr/lib64/libgallium-24.2.8.so from rpm mesa-24.2.8-1.fc41.x86_64 Module /run/host/usr/lib64/libxcb-shm.so.0.0.0 from rpm libxcb-1.17.0-3.fc41.x86_64 Module /run/host/usr/lib64/libxcb-randr.so.0.1.0 from rpm libxcb-1.17.0-3.fc41.x86_64 Module /run/host/usr/lib64/libwayland-server.so.0.23.0 from rpm wayland-1.23.0-2.fc41.x86_64 Module /run/host/usr/lib64/libXau.so.6.0.0 from rpm libXau-1.0.11-7.fc41.x86_64 Module /run/host/usr/lib64/libGLdispatch.so.0.0.0 from rpm libglvnd-1.7.0-5.fc41.x86_64 Module /run/host/usr/lib64/libGLX.so.0.0.0 from rpm libglvnd-1.7.0-5.fc41.x86_64 Module /run/host/usr/lib64/libz.so.1.3.1.zlib-ng from rpm zlib-ng-2.1.7-3.fc41.x86_64 Module /run/host/usr/lib64/libgbm.so.1.0.0 from rpm mesa-24.2.8-1.fc41.x86_64 Module /run/host/usr/lib64/libxcb.so.1.1.0 from rpm libxcb-1.17.0-3.fc41.x86_64 Module /run/host/usr/lib64/libexpat.so.1.10.0 from rpm expat-2.6.4-1.fc41.x86_64 Module /run/host/usr/lib64/libXfixes.so.3.1.0 from rpm libXfixes-6.0.1-4.fc41.x86_64 Module /run/host/usr/lib64/libdrm.so.2.123.0 from rpm libdrm-2.4.123-1.fc41.x86_64 Module /run/host/usr/lib64/libGL.so.1.7.0 from rpm libglvnd-1.7.0-5.fc41.x86_64 Module /run/host/usr/lib64/libX11.so.6.4.0 from rpm libX11-1.8.10-2.fc41.x86_64 Module /run/host/usr/lib64/libXext.so.6.4.0 from rpm libXext-1.3.6-2.fc41.x86_64 Stack trace of thread 160771: #0 0x0000000000000000 n/a (n/a + 0x0) ELF object binary architecture: AMD x86-64 ~~~ I presume that this is due to the undermentioned:

RokeJulianLockhart@SNRW3Q:~$ file /usr/bin/steam
/usr/bin/steam: symbolic link to /usr/lib/steam/bin_steam.sh
RokeJulianLockhart@SNRW3Q:~$ file /usr/lib/steam/bin_steam.sh
/usr/lib/steam/bin_steam.sh: Bourne-Again shell script, ASCII text executable

Consequently, I want to capture a stack trace (using gdb), so that I can report this crash to [bugzilla.rpmfusion.org/enter_bug.cgi?product=Fedora](https://bugzilla.rpmfusion.org/enter_bug.cgi?product=Fedora) . (It's not a duplicate of [/show_bug.cgi?id=6900#c6](https://bugzilla.rpmfusion.org/show_bug.cgi?id=6900#c6).) Preventing me doing is so, is that, incredibly, it does not crash when invoked via bash (in konsole): ~~~bash #!/usr/bin/env -S bash steam ~~~ That inability to make it crash in the shell is why I'm unable to debug the source of it crashing, because the undermentioned is of no use: ~~~bash #!/usr/bin/env -S bash DEBUGGER=gdb steam ~~~ **Attempted Solutions** Consequently, I have attempted to add the diagnostic information to its .desktop file. To demonstrate what I have modified, by default, its content is the undermentioned: ~~~desktop [Desktop Action BigPicture] Exec=steam steam://open/bigpicture Name=Big Picture [Desktop Action Community] Exec=steam steam://url/SteamIDControlPage Name=Community Name[bg]=Общност Name[cs]=Komunita Name[da]=Fællesskab Name[de]=Community Name[el]=Κοινότητα Name[es]=Comunidad Name[fi]=Yhteisö Name[fr]=Communauté Name[hu]=Közösség Name[it]=Comunità Name[ja]=コミュニティ Name[ko]=커뮤니티 Name[nl]=Community Name[no]=Samfunn Name[pl]=Społeczność Name[pt_BR]=Comunidade Name[pt_PT]=Comunidade Name[ro]=Comunitate Name[ru]=Сообщество Name[sv]=Gemenskap Name[th]=ชุมชน Name[tr]=Topluluk Name[uk]=Спільнота Name[vi]=Cộng đồng Name[zh_CN]=社区 Name[zh_TW]=社群 [Desktop Action Friends] Exec=steam steam://open/friends Name=Friends Name[bg]=Приятели Name[cs]=Přátelé Name[da]=Venner Name[de]=Freunde Name[el]=Φίλοι Name[es]=Amigos Name[fi]=Kaverit Name[fr]=Amis Name[hu]=Barátok Name[it]=Amici Name[ja]=フレンド Name[ko]=친구 Name[nl]=Vrienden Name[no]=Venner Name[pl]=Znajomi Name[pt_BR]=Amigos Name[pt_PT]=Amigos Name[ro]=Prieteni Name[ru]=Друзья Name[sv]=Vänner Name[th]=เพื่อน Name[tr]=Arkadaşlar Name[uk]=Друзі Name[vi]=Bạn bè Name[zh_CN]=好友 Name[zh_TW]=好友 [Desktop Action Library] Exec=steam steam://open/games Name=Library Name[bg]=Библиотека Name[cs]=Knihovna Name[da]=Bibliotek Name[de]=Bibliothek Name[el]=Συλλογή Name[es]=Biblioteca Name[fi]=Kokoelma Name[fr]=Bibliothèque Name[hu]=Könyvtár Name[it]=Libreria Name[ja]=ライブラリ Name[ko]=라이브러리 Name[nl]=Bibliotheek Name[no]=Bibliotek Name[pl]=Biblioteka Name[pt_BR]=Biblioteca Name[pt_PT]=Biblioteca Name[ro]=Colecţie Name[ru]=Библиотека Name[sv]=Bibliotek Name[th]=คลัง Name[tr]=Kütüphane Name[uk]=Бібліотека Name[vi]=Thư viện Name[zh_CN]=库 Name[zh_TW]=收藏庫 [Desktop Action News] Exec=steam steam://open/news Name=News Name[bg]=Новини Name[cs]=Zprávy Name[da]=Nyheder Name[de]=Neuigkeiten Name[el]=Νέα Name[es]=Noticias Name[fi]=Uutiset Name[fr]=Actualités Name[hu]=Hírek Name[it]=Notizie Name[ja]=ニュース Name[ko]=뉴스 Name[nl]=Nieuws Name[no]=Nyheter Name[pl]=Aktualności Name[pt_BR]=Notícias Name[pt_PT]=Novidades Name[ro]=Știri Name[ru]=Новости Name[sv]=Nyheter Name[th]=ข่าวสาร Name[tr]=Haberler Name[uk]=Новини Name[vi]=Tin tức Name[zh_CN]=新闻 Name[zh_TW]=新聞 [Desktop Action Screenshots] Exec=steam steam://open/screenshots Name=Screenshots Name[bg]=Снимки Name[cs]=Snímky obrazovky Name[da]=Skærmbilleder Name[de]=Screenshots Name[el]=Φωτογραφίες Name[es]=Capturas Name[fi]=Kuvankaappaukset Name[fr]=Captures d'écran Name[hu]=Képernyőmentések Name[it]=Screenshot Name[ja]=スクリーンショット Name[ko]=스크린샷 Name[nl]=Screenshots Name[no]=Skjermbilder Name[pl]=Zrzuty ekranu Name[pt_BR]=Capturas de tela Name[pt_PT]=Capturas de ecrã Name[ro]=Capturi de ecran Name[ru]=Скриншоты Name[sv]=Skärmdumpar Name[th]=ภาพหน้าจอ Name[tr]=Ekran Görüntüleri Name[uk]=Скріншоти Name[vi]=Ảnh chụp Name[zh_CN]=截图 Name[zh_TW]=螢幕擷圖 [Desktop Action Servers] Exec=steam steam://open/servers Name=Servers Name[bg]=Сървъри Name[cs]=Servery Name[da]=Servere Name[de]=Server Name[el]=Διακομιστές Name[es]=Servidores Name[fi]=Palvelimet Name[fr]=Serveurs Name[hu]=Szerverek Name[it]=Server Name[ja]=サーバー Name[ko]=서버 Name[nl]=Servers Name[no]=Tjenere Name[pl]=Serwery Name[pt_BR]=Servidores Name[pt_PT]=Servidores Name[ro]=Servere Name[ru]=Серверы Name[sv]=Servrar Name[th]=เซิร์ฟเวอร์ Name[tr]=Sunucular Name[uk]=Сервери Name[vi]=Máy chủ Name[zh_CN]=服务器 Name[zh_TW]=伺服器 [Desktop Action Settings] Exec=steam steam://open/settings Name=Settings Name[bg]=Настройки Name[cs]=Nastavení Name[da]=Indstillinger Name[de]=Einstellungen Name[el]=Ρυθμίσεις Name[es]=Parámetros Name[fi]=Asetukset Name[fr]=Paramètres Name[hu]=Beállítások Name[it]=Impostazioni Name[ja]=設定 Name[ko]=설정 Name[nl]=Instellingen Name[no]=Innstillinger Name[pl]=Ustawienia Name[pt_BR]=Configurações Name[pt_PT]=Definições Name[ro]=Setări Name[ru]=Настройки Name[sv]=Inställningar Name[th]=การตั้งค่า Name[tr]=Ayarlar Name[uk]=Налаштування Name[vi]=Thiết lập Name[zh_CN]=设置 Name[zh_TW]=設定 [Desktop Action Store] Exec=steam steam://store Name=Store Name[bg]=Магазин Name[cs]=Obchod Name[da]=Butik Name[de]=Shop Name[el]=ΚΑΤΑΣΤΗΜΑ Name[es]=Tienda Name[fi]=Kauppa Name[fr]=Magasin Name[hu]=Áruház Name[it]=Negozio Name[ja]=ストア Name[ko]=상점 Name[nl]=Winkel Name[no]=Butikk Name[pl]=Sklep Name[pt_BR]=Loja Name[pt_PT]=Loja Name[ro]=Magazin Name[ru]=Магазин Name[sv]=Butik Name[th]=ร้านค้า Name[tr]=Mağaza Name[uk]=Крамниця Name[vi]=Cửa hàng Name[zh_CN]=商店 Name[zh_TW]=商店 [Desktop Entry] Actions=Store;Community;Library;Servers;Screenshots;News;Settings;BigPicture;Friends; Categories=Network;FileTransfer;Game; Comment[en_GB]=Application for managing and playing games on Steam Comment=Application for managing and playing games on Steam Comment[bg]=Приложение за ръководене и пускане на игри в Steam Comment[cs]=Aplikace pro spravování a hraní her ve službě Steam Comment[da]=Applikation til at håndtere og spille spil på Steam Comment[de]=Anwendung zum Verwalten und Spielen von Spielen auf Steam Comment[el]=Εφαρμογή διαχείρισης παιχνιδιών στο Steam Comment[es]=Aplicación para administrar y ejecutar juegos en Steam Comment[fi]=Steamin pelien hallintaan ja pelaamiseen tarkoitettu sovellus Comment[fr]=Application de gestion et d'utilisation des jeux sur Steam Comment[hu]=Alkalmazás a Steames játékok futtatásához és kezeléséhez Comment[it]=Applicazione per la gestione e l'esecuzione di giochi su Steam Comment[ja]=Steam 上でゲームを管理＆プレイするためのアプリケーション Comment[ko]=Steam에 있는 게임을 관리하고 플레이할 수 있는 응용 프로그램 Comment[nl]=Applicatie voor het beheer en het spelen van games op Steam Comment[no]=Program for å administrere og spille spill på Steam Comment[pl]=Aplikacja do zarządzania i uruchamiania gier na platformie Steam Comment[pt_BR]=Aplicativo para jogar e gerenciar jogos no Steam Comment[pt_PT]=Aplicação para organizar e executar jogos no Steam Comment[ro]=Aplicație pentru administrarea și jucatul jocurilor pe Steam Comment[ru]=Приложение для игр и управления играми в Steam Comment[sv]=Ett program för att hantera samt spela spel på Steam Comment[th]=โปรแกรมสำหรับจัดการและเล่นเกมบน Steam Comment[tr]=Steam üzerinden oyun oynama ve düzenleme uygulaması Comment[uk]=Програма для керування іграми та запуску ігор у Steam Comment[vi]=Ứng dụng để quản lý và chơi trò chơi trên Steam Comment[zh_CN]=管理和进行 Steam 游戏的应用程序 Comment[zh_TW]=管理並執行 Steam 遊戲的應用程式 Exec=env /usr/bin/steam %U GenericName[en_GB]= GenericName= Icon=steam MimeType= Name[en_GB]=Steam Name=Steam Path= PrefersNonDefaultGPU=true StartupNotify=true Terminal=false TerminalOptions=\s--noclose Type=Application X-KDE-RunOnDiscreteGpu=true X-KDE-SubstituteUID=false X-KDE-Username= ~~~ I then modify it as the undermentioned demonstrate: 1. ~~~diff - Exec=env /usr/bin/steam %U + Exec=env 'DEBUGGER=gdb --args /usr/bin/steam' %U ~~~ 2. ~~~diff - Terminal=false + Terminal=true ~~~ This becomes the undermentioned: ~~~desktop [Desktop Action BigPicture] Exec=steam steam://open/bigpicture Name=Big Picture [Desktop Action Community] Exec=steam steam://url/SteamIDControlPage Name=Community Name[bg]=Общност Name[cs]=Komunita Name[da]=Fællesskab Name[de]=Community Name[el]=Κοινότητα Name[es]=Comunidad Name[fi]=Yhteisö Name[fr]=Communauté Name[hu]=Közösség Name[it]=Comunità Name[ja]=コミュニティ Name[ko]=커뮤니티 Name[nl]=Community Name[no]=Samfunn Name[pl]=Społeczność Name[pt_BR]=Comunidade Name[pt_PT]=Comunidade Name[ro]=Comunitate Name[ru]=Сообщество Name[sv]=Gemenskap Name[th]=ชุมชน Name[tr]=Topluluk Name[uk]=Спільнота Name[vi]=Cộng đồng Name[zh_CN]=社区 Name[zh_TW]=社群 [Desktop Action Friends] Exec=steam steam://open/friends Name=Friends Name[bg]=Приятели Name[cs]=Přátelé Name[da]=Venner Name[de]=Freunde Name[el]=Φίλοι Name[es]=Amigos Name[fi]=Kaverit Name[fr]=Amis Name[hu]=Barátok Name[it]=Amici Name[ja]=フレンド Name[ko]=친구 Name[nl]=Vrienden Name[no]=Venner Name[pl]=Znajomi Name[pt_BR]=Amigos Name[pt_PT]=Amigos Name[ro]=Prieteni Name[ru]=Друзья Name[sv]=Vänner Name[th]=เพื่อน Name[tr]=Arkadaşlar Name[uk]=Друзі Name[vi]=Bạn bè Name[zh_CN]=好友 Name[zh_TW]=好友 [Desktop Action Library] Exec=steam steam://open/games Name=Library Name[bg]=Библиотека Name[cs]=Knihovna Name[da]=Bibliotek Name[de]=Bibliothek Name[el]=Συλλογή Name[es]=Biblioteca Name[fi]=Kokoelma Name[fr]=Bibliothèque Name[hu]=Könyvtár Name[it]=Libreria Name[ja]=ライブラリ Name[ko]=라이브러리 Name[nl]=Bibliotheek Name[no]=Bibliotek Name[pl]=Biblioteka Name[pt_BR]=Biblioteca Name[pt_PT]=Biblioteca Name[ro]=Colecţie Name[ru]=Библиотека Name[sv]=Bibliotek Name[th]=คลัง Name[tr]=Kütüphane Name[uk]=Бібліотека Name[vi]=Thư viện Name[zh_CN]=库 Name[zh_TW]=收藏庫 [Desktop Action News] Exec=steam steam://open/news Name=News Name[bg]=Новини Name[cs]=Zprávy Name[da]=Nyheder Name[de]=Neuigkeiten Name[el]=Νέα Name[es]=Noticias Name[fi]=Uutiset Name[fr]=Actualités Name[hu]=Hírek Name[it]=Notizie Name[ja]=ニュース Name[ko]=뉴스 Name[nl]=Nieuws Name[no]=Nyheter Name[pl]=Aktualności Name[pt_BR]=Notícias Name[pt_PT]=Novidades Name[ro]=Știri Name[ru]=Новости Name[sv]=Nyheter Name[th]=ข่าวสาร Name[tr]=Haberler Name[uk]=Новини Name[vi]=Tin tức Name[zh_CN]=新闻 Name[zh_TW]=新聞 [Desktop Action Screenshots] Exec=steam steam://open/screenshots Name=Screenshots Name[bg]=Снимки Name[cs]=Snímky obrazovky Name[da]=Skærmbilleder Name[de]=Screenshots Name[el]=Φωτογραφίες Name[es]=Capturas Name[fi]=Kuvankaappaukset Name[fr]=Captures d'écran Name[hu]=Képernyőmentések Name[it]=Screenshot Name[ja]=スクリーンショット Name[ko]=스크린샷 Name[nl]=Screenshots Name[no]=Skjermbilder Name[pl]=Zrzuty ekranu Name[pt_BR]=Capturas de tela Name[pt_PT]=Capturas de ecrã Name[ro]=Capturi de ecran Name[ru]=Скриншоты Name[sv]=Skärmdumpar Name[th]=ภาพหน้าจอ Name[tr]=Ekran Görüntüleri Name[uk]=Скріншоти Name[vi]=Ảnh chụp Name[zh_CN]=截图 Name[zh_TW]=螢幕擷圖 [Desktop Action Servers] Exec=steam steam://open/servers Name=Servers Name[bg]=Сървъри Name[cs]=Servery Name[da]=Servere Name[de]=Server Name[el]=Διακομιστές Name[es]=Servidores Name[fi]=Palvelimet Name[fr]=Serveurs Name[hu]=Szerverek Name[it]=Server Name[ja]=サーバー Name[ko]=서버 Name[nl]=Servers Name[no]=Tjenere Name[pl]=Serwery Name[pt_BR]=Servidores Name[pt_PT]=Servidores Name[ro]=Servere Name[ru]=Серверы Name[sv]=Servrar Name[th]=เซิร์ฟเวอร์ Name[tr]=Sunucular Name[uk]=Сервери Name[vi]=Máy chủ Name[zh_CN]=服务器 Name[zh_TW]=伺服器 [Desktop Action Settings] Exec=steam steam://open/settings Name=Settings Name[bg]=Настройки Name[cs]=Nastavení Name[da]=Indstillinger Name[de]=Einstellungen Name[el]=Ρυθμίσεις Name[es]=Parámetros Name[fi]=Asetukset Name[fr]=Paramètres Name[hu]=Beállítások Name[it]=Impostazioni Name[ja]=設定 Name[ko]=설정 Name[nl]=Instellingen Name[no]=Innstillinger Name[pl]=Ustawienia Name[pt_BR]=Configurações Name[pt_PT]=Definições Name[ro]=Setări Name[ru]=Настройки Name[sv]=Inställningar Name[th]=การตั้งค่า Name[tr]=Ayarlar Name[uk]=Налаштування Name[vi]=Thiết lập Name[zh_CN]=设置 Name[zh_TW]=設定 [Desktop Action Store] Exec=steam steam://store Name=Store Name[bg]=Магазин Name[cs]=Obchod Name[da]=Butik Name[de]=Shop Name[el]=ΚΑΤΑΣΤΗΜΑ Name[es]=Tienda Name[fi]=Kauppa Name[fr]=Magasin Name[hu]=Áruház Name[it]=Negozio Name[ja]=ストア Name[ko]=상점 Name[nl]=Winkel Name[no]=Butikk Name[pl]=Sklep Name[pt_BR]=Loja Name[pt_PT]=Loja Name[ro]=Magazin Name[ru]=Магазин Name[sv]=Butik Name[th]=ร้านค้า Name[tr]=Mağaza Name[uk]=Крамниця Name[vi]=Cửa hàng Name[zh_CN]=商店 Name[zh_TW]=商店 [Desktop Entry] Actions=Store;Community;Library;Servers;Screenshots;News;Settings;BigPicture;Friends; Categories=Network;FileTransfer;Game; Comment[en_GB]=Application for managing and playing games on Steam Comment=Application for managing and playing games on Steam Comment[bg]=Приложение за ръководене и пускане на игри в Steam Comment[cs]=Aplikace pro spravování a hraní her ve službě Steam Comment[da]=Applikation til at håndtere og spille spil på Steam Comment[de]=Anwendung zum Verwalten und Spielen von Spielen auf Steam Comment[el]=Εφαρμογή διαχείρισης παιχνιδιών στο Steam Comment[es]=Aplicación para administrar y ejecutar juegos en Steam Comment[fi]=Steamin pelien hallintaan ja pelaamiseen tarkoitettu sovellus Comment[fr]=Application de gestion et d'utilisation des jeux sur Steam Comment[hu]=Alkalmazás a Steames játékok futtatásához és kezeléséhez Comment[it]=Applicazione per la gestione e l'esecuzione di giochi su Steam Comment[ja]=Steam 上でゲームを管理＆プレイするためのアプリケーション Comment[ko]=Steam에 있는 게임을 관리하고 플레이할 수 있는 응용 프로그램 Comment[nl]=Applicatie voor het beheer en het spelen van games op Steam Comment[no]=Program for å administrere og spille spill på Steam Comment[pl]=Aplikacja do zarządzania i uruchamiania gier na platformie Steam Comment[pt_BR]=Aplicativo para jogar e gerenciar jogos no Steam Comment[pt_PT]=Aplicação para organizar e executar jogos no Steam Comment[ro]=Aplicație pentru administrarea și jucatul jocurilor pe Steam Comment[ru]=Приложение для игр и управления играми в Steam Comment[sv]=Ett program för att hantera samt spela spel på Steam Comment[th]=โปรแกรมสำหรับจัดการและเล่นเกมบน Steam Comment[tr]=Steam üzerinden oyun oynama ve düzenleme uygulaması Comment[uk]=Програма для керування іграми та запуску ігор у Steam Comment[vi]=Ứng dụng để quản lý và chơi trò chơi trên Steam Comment[zh_CN]=管理和进行 Steam 游戏的应用程序 Comment[zh_TW]=管理並執行 Steam 遊戲的應用程式 Exec=env 'DEBUGGER=gdb --args /usr/bin/steam' %U GenericName[en_GB]= GenericName= Icon=steam MimeType= Name[en_GB]=Steam Name=Steam Path= PrefersNonDefaultGPU=true StartupNotify=true Terminal=true TerminalOptions=\s--noclose Type=Application X-KDE-RunOnDiscreteGpu=true X-KDE-SubstituteUID=false X-KDE-Username= ~~~ The aforementioned doesn't work, for although Terminal=true makes me see that the variable has been passed, I do not see the gdb CLI: **Potential Solutions** I may be able to spawn an interactive shell by using the instructions in [/revisions/682872/4](https://superuser.com/revisions/682872/4) . However, I don't much understand them; much less so, how to implement them in a .desktop file. **Corroborations** This situation appears to be similar to [bbs.archlinux.org/viewtopic.php?id=295425](https://bbs.archlinux.org/viewtopic.php?id=295425) . However, their solution is irrelevant to mine, because I've no NVIDIA hardware.

I was re-doing what described here about multiprocessing debugging in GDB. The weird thing is that GDB doesn't hit the exec catchpoint on the child process running cat command (the latter is forked off from bash). ubuntu@ubuntu:~$ echo $$ 670639 ubuntu@ubuntu:~$ cat /etc/issue root@ubuntu:~# gdb -q -p 670639 Attaching to process 670639 Reading symbols from /usr/bin/bash... (No debugging symbols found in /usr/bin/bash) Reading symbols from /lib/x86_64-linux-gnu/libtinfo.so.6... (No debugging symbols found in /lib/x86_64-linux-gnu/libtinfo.so.6) Reading symbols from /lib/x86_64-linux-gnu/libc.so.6... Reading symbols from /usr/lib/debug/.build-id/49/0fef8403240c91833978d494d39e537409b92e.debug... Reading symbols from /lib64/ld-linux-x86-64.so.2... Reading symbols from /usr/lib/debug/.build-id/41/86944c50f8a32b47d74931e3f512b811813b64.debug... [Thread debugging using libthread_db enabled] Using host libthread_db library "/lib/x86_64-linux-gnu/libthread_db.so.1". pselect64_syscall (sigmask=0x564025a0c820 , timeout=, exceptfds=0x0, writefds=0x0, readfds=0x7ffe468736e0, nfds=1) at ../sysdeps/unix/sysv/linux/pselect.c:34 34 ../sysdeps/unix/sysv/linux/pselect.c: No such file or directory. (gdb) catch fork Catchpoint 1 (fork) (gdb) catch exec Catchpoint 2 (exec) (gdb) c Continuing. Catchpoint 1 (forked process 719946), arch_fork (ctid=0x7fbccdc6fa10) at ../sysdeps/unix/sysv/linux/arch-fork.h:52 52 ../sysdeps/unix/sysv/linux/arch-fork.h: No such file or directory. (gdb) info inferiors Num Description Connection Executable * 1 process 670639 1 (native) /usr/bin/bash (gdb) set detach-on-fork off (gdb) nexti [New inferior 2 (process 719946)] [Thread debugging using libthread_db enabled] Using host libthread_db library "/lib/x86_64-linux-gnu/libthread_db.so.1". 52 in ../sysdeps/unix/sysv/linux/arch-fork.h (gdb) c Continuing. What is the reason behind it? Thanks.

When using bash -x or set -x in a script the output shows the result of the line being processed but not the source line which produced the result. There are times when knowing this as well could save time by not having to cross-reference the script with its output. For example, if variable "x" currently has a value of 1 then source line x=$((x+1)) shows x=2 without revealing how the result was obtained - it could have been a simple x=2 assignment. Limited testing also indicates that there is no difference between the output of a while loop and the equivalent series of if tests. Is there any facility in bash which will return the "pre-interpreted" source line for display?

I'm having some problems with some scripts in bash, about errors and unexpected behaviors. I would like to investigate the causes of the problems so I can apply fixes. Is there a way I can turn some kind of "debug-mode" for bash, to get more information?

Does Bash have an option to diagnose (and optionally abort execution) "expanded to empty value" variables? Example (hypothetical):

$ bash -c 'echo $x' --xxx
bash: line 1: variable 'x' expanded to empty value

Reason for the question: such an option may be useful when debugging scripts. For example, in some script all variables are expected to expand to a non-empty values. Hence, using an option to detect (and optionally abort execution) "expanded to empty value" variables may be useful for such case. I've already searched for this option in [set builtin](https://www.gnu.org/software/bash/manual/html_node/The-Set-Builtin.html) , but have found nothing.

Do you know where I might find an interpretation of all the debug level messages (debug1, debug2, and debug3), that are output when the ssh -v, ssh -vv, or ssh -vvv command is executed?