[SOLVED] Bus Error (7) when trying to launch ksysguard

-LXR- · 2020-06-01 17:39:23

I already posted this issue on Reddit but no one responded so I'm copy/pasting it here now. Reddit post

Let me start off by saying I'm new to Arch, I switched over when my ubuntu version (Disco Dingo) stopped getting support. I installed the KDE plasma desktop environment and it works beautifully except for a couple of non required applications such as konquerer, kmixer, ksysguard, etc. But the one I want to focus on is ksysguard as I find it very useful when trying to figure out why my computer is acting up. If anyone could help me figure this out, it would be greatly appreciated.

Last edited by -LXR- (2020-06-07 05:37:11)

V1del · 2020-06-01 17:42:28

What happens? does it just not start? What's the terminal output you get? https://bbs.archlinux.org/viewtopic.php?id=57855

-LXR- · 2020-06-01 18:20:33

The program doesn't start, running in console gives me this.

[######@Cornerstone ~]$ ksysguard
Bus error (core dumped)

Looking at the core dump returns this

[######@Cornerstone ~]$ coredumpctl list
Mon 2020-06-01 10:58:10 PDT    3534  1000   985   7 present   /usr/bin/ksysguard
[######@Cornerstone ~]$ coredumpctl info 3534
           PID: 3534 (ksysguard)
           UID: 1000 (######)
           GID: 985 (users)
        Signal: 7 (BUS)
     Timestamp: Mon 2020-06-01 10:58:08 PDT (18min ago)
  Command Line: ksysguard
    Executable: /usr/bin/ksysguard
 Control Group: /user.slice/user-1000.slice/session-2.scope
          Unit: session-2.scope
         Slice: user-1000.slice
       Session: 2
     Owner UID: 1000 (######)
       Boot ID: 42eab9134b394231abba878983a6b770
    Machine ID: 3a62f3fca47c4676a30a2c75c00c49c9
      Hostname: Cornerstone
       Storage: /var/lib/systemd/coredump/core.ksysguard.1000.42eab9134b394231abba878983a6b770.3534.1591034288000000000000.lz4
       Message: Process 3534 (ksysguard) of user 1000 dumped core.
                
                Stack trace of thread 3534:
                #0  0x00007f7216fe4b73 memset (ld-linux-x86-64.so.2 + 0x21b73)
                #1  0x00007f7216fcb72c _dl_map_object_from_fd (ld-linux-x86-64.so.2 + 0x872c)
                #2  0x00007f7216fcd3dd _dl_map_object (ld-linux-x86-64.so.2 + 0xa3dd)
                #3  0x00007f7216fd1eb5 openaux (ld-linux-x86-64.so.2 + 0xeeb5)
                #4  0x00007f7216fdf3ae _dl_catch_exception (ld-linux-x86-64.so.2 + 0x1c3ae)
                #5  0x00007f7216fd2233 _dl_map_object_deps (ld-linux-x86-64.so.2 + 0xf233)
                #6  0x00007f7216fc7eb1 dl_main (ld-linux-x86-64.so.2 + 0x4eb1)
                #7  0x00007f7216fde33b _dl_sysdep_start (ld-linux-x86-64.so.2 + 0x1b33b)
                #8  0x00007f7216fc5f4c _dl_start (ld-linux-x86-64.so.2 + 0x2f4c)
                #9  0x00007f7216fc5108 _start (ld-linux-x86-64.so.2 + 0x2108)

V1del · 2020-06-01 19:53:59

That doesn't look good just from that excerpt... That's pretty basic low level stuff that's failing here (but maybe post a full bt full on a gdb run on that stacktrace). What's your hardware? Make sure your microcode updates are installed and configured. Maybe run a memtest as well, but first gut feeling is that you are on an old microcode that runs into parallelism issues.

-LXR- · 2020-06-01 22:23:38

I'm not entirely sure how to use gdb, I ran [$ gdb bt -full] and it returned [no stack.] I'm confident that I loaded the microcode correctly (albeit I did do a late load of it) but if there is way to check, that would be much appreciated. Ill do a memtest later and post my results when its done.

                   -`                    ######@Cornerstone 
                  .o+`                   ------------------ 
                 `ooo/                   OS: Arch Linux x86_64 
                `+oooo:                  Host: Lars 1.0 
               `+oooooo:                 Kernel: 5.6.14-arch1-1 
               -+oooooo+:                Uptime: 25 mins 
             `/:-:++oooo+:               Packages: 1096 (pacman), 6 (flatpak) 
            `/++++/+++++++:              Shell: bash 5.0.17 
           `/++++++++++++++:             Resolution: 1920x1080 
          `/+++ooooooooooooo/`           DE: Plasma 
         ./ooosssso++osssssso+`          WM: KWin 
        .oossssso-````/ossssss+`         WM Theme: Breeze 
       -osssssso.      :ssssssso.        Theme: Breeze Dark [Plasma], Breeze [GTK2/3] 
      :osssssss/        osssso+++.       Icons: breeze-dark [Plasma], breeze-dark [GTK2/3] 
     /ossssssss/        +ssssooo/-       Terminal: konsole 
   `/ossssso+/:-        -:/+osssso+-     CPU: Intel i5-6200U (4) @ 2.800GHz 
  `+sso+:-`                 `.-/+oso:    GPU: Intel Skylake GT2 [HD Graphics 520] 
 `++:.                           `-/+/   Memory: 1318MiB / 7860MiB 
 .`                                 `/

V1del · 2020-06-01 23:10:58

You should set it up for early load to be sure that it's applied. For gdb you can run

coredumpctl gdb 3534
bt full

on the dump you received, and then bt full for the stack trace

-LXR- · 2020-06-02 00:31:54

here is the bt full

[######@Cornerstone ~]$ coredumpctl gdb 3534
           PID: 3534 (ksysguard)
           UID: 1000 (######)
           GID: 985 (users)
        Signal: 7 (BUS)
     Timestamp: Mon 2020-06-01 10:58:08 PDT (6h ago)
  Command Line: ksysguard
    Executable: /usr/bin/ksysguard
 Control Group: /user.slice/user-1000.slice/session-2.scope
          Unit: session-2.scope
         Slice: user-1000.slice
       Session: 2
     Owner UID: 1000 (######)
       Boot ID: 42eab9134b394231abba878983a6b770
    Machine ID: 3a62f3fca47c4676a30a2c75c00c49c9
      Hostname: Cornerstone
       Storage: /var/lib/systemd/coredump/core.ksysguard.1000.42eab9134b394231abba878983a6b770.3534.1591034288000000000000.lz4
       Message: Process 3534 (ksysguard) of user 1000 dumped core.
                
                Stack trace of thread 3534:
                #0  0x00007f7216fe4b73 memset (ld-linux-x86-64.so.2 + 0x21b73)
                #1  0x00007f7216fcb72c _dl_map_object_from_fd (ld-linux-x86-64.so.2 + 0x872c)
                #2  0x00007f7216fcd3dd _dl_map_object (ld-linux-x86-64.so.2 + 0xa3dd)
                #3  0x00007f7216fd1eb5 openaux (ld-linux-x86-64.so.2 + 0xeeb5)
                #4  0x00007f7216fdf3ae _dl_catch_exception (ld-linux-x86-64.so.2 + 0x1c3ae)
                #5  0x00007f7216fd2233 _dl_map_object_deps (ld-linux-x86-64.so.2 + 0xf233)
                #6  0x00007f7216fc7eb1 dl_main (ld-linux-x86-64.so.2 + 0x4eb1)
                #7  0x00007f7216fde33b _dl_sysdep_start (ld-linux-x86-64.so.2 + 0x1b33b)
                #8  0x00007f7216fc5f4c _dl_start (ld-linux-x86-64.so.2 + 0x2f4c)
                #9  0x00007f7216fc5108 _start (ld-linux-x86-64.so.2 + 0x2108)

GNU gdb (GDB) 9.2
Copyright (C) 2020 Free Software Foundation, Inc.
License GPLv3+: GNU GPL version 3 or later <http://gnu.org/licenses/gpl.html>
This is free software: you are free to change and redistribute it.
There is NO WARRANTY, to the extent permitted by law.
Type "show copying" and "show warranty" for details.
This GDB was configured as "x86_64-pc-linux-gnu".
Type "show configuration" for configuration details.
For bug reporting instructions, please see:
<http://www.gnu.org/software/gdb/bugs/>.
Find the GDB manual and other documentation resources online at:
    <http://www.gnu.org/software/gdb/documentation/>.

For help, type "help".
Type "apropos word" to search for commands related to "word"...
Reading symbols from /usr/bin/ksysguard...
(No debugging symbols found in /usr/bin/ksysguard)
[New LWP 3534]
Core was generated by `ksysguard'.
Program terminated with signal SIGBUS, Bus error.
#0  0x00007f7216fe4b73 in memset () from /lib64/ld-linux-x86-64.so.2
(gdb) bt full
#0  0x00007f7216fe4b73 in memset () from /lib64/ld-linux-x86-64.so.2
No symbol table info available.
#1  0x00007f7216fcb72c in _dl_map_object_from_fd () from /lib64/ld-linux-x86-64.so.2
No symbol table info available.
#2  0x00007f7216fcd3dd in _dl_map_object () from /lib64/ld-linux-x86-64.so.2
No symbol table info available.
#3  0x00007f7216fd1eb5 in openaux () from /lib64/ld-linux-x86-64.so.2
No symbol table info available.
#4  0x00007f7216fdf3ae in _dl_catch_exception () from /lib64/ld-linux-x86-64.so.2
No symbol table info available.
#5  0x00007f7216fd2233 in _dl_map_object_deps () from /lib64/ld-linux-x86-64.so.2
No symbol table info available.
#6  0x00007f7216fc7eb1 in dl_main () from /lib64/ld-linux-x86-64.so.2
No symbol table info available.
#7  0x00007f7216fde33b in _dl_sysdep_start () from /lib64/ld-linux-x86-64.so.2
No symbol table info available.
#8  0x00007f7216fc5f4c in _dl_start () from /lib64/ld-linux-x86-64.so.2
No symbol table info available.
#9  0x00007f7216fc5108 in _start () from /lib64/ld-linux-x86-64.so.2
No symbol table info available.
#10 0x0000000000000001 in ?? ()
No symbol table info available.
#11 0x00007ffc6ee72a72 in ?? ()
No symbol table info available.
#12 0x0000000000000000 in ?? ()
No symbol table info available.

The memory test turned out fine, although, I have a suspicion that it may be my storage device that is being faulty.

Edit: Is there a way I can early load without having to re-setup my computer?

Last edited by -LXR- (2020-06-02 00:36:44)

V1del · 2020-06-02 00:44:21

Yes how you do early loading depends on your boot loader and is usually just a configuration file away, read the linked article for your chosen booting method. Storage device might be a possible culprit, what's your output for

pacman -Qkk glibc

and maybe run a long SMART test and post the output of smartctl -a $device once the needed time for the test has elapsed.

-LXR- · 2020-06-07 05:34:10

Welp guys, the problem no longer exists, it disappeared. I don't know what the cause or the solution was, but it is gone. It most likely was a microcode update.

Last edited by -LXR- (2020-06-07 05:37:25)

Arch Linux

#1 2020-06-01 17:39:23

[SOLVED] Bus Error (7) when trying to launch ksysguard

#2 2020-06-01 17:42:28

Re: [SOLVED] Bus Error (7) when trying to launch ksysguard

#3 2020-06-01 18:20:33

Re: [SOLVED] Bus Error (7) when trying to launch ksysguard

#4 2020-06-01 19:53:59

Re: [SOLVED] Bus Error (7) when trying to launch ksysguard

#5 2020-06-01 22:23:38

Re: [SOLVED] Bus Error (7) when trying to launch ksysguard

#6 2020-06-01 23:10:58

Re: [SOLVED] Bus Error (7) when trying to launch ksysguard

#7 2020-06-02 00:31:54

Re: [SOLVED] Bus Error (7) when trying to launch ksysguard

#8 2020-06-02 00:44:21

Re: [SOLVED] Bus Error (7) when trying to launch ksysguard

#9 2020-06-07 05:34:10

Re: [SOLVED] Bus Error (7) when trying to launch ksysguard

Board footer