[plasmashell] [Bug 478478] A lot of random crashing

[postix]

https://bugs.kde.org/show_bug.cgi?id=478478

postix  changed:

   What|Removed |Added

 CC||pos...@posteo.eu
 Status|REPORTED|RESOLVED
 Resolution|--- |DUPLICATE

--- Comment #6 from postix  ---


*** This bug has been marked as a duplicate of bug 487385 ***

-- 
You are receiving this mail because:
You are watching all bug changes.

[plasmashell] [Bug 478478] A lot of random crashing

[Nate Graham]

https://bugs.kde.org/show_bug.cgi?id=478478

Nate Graham  changed:

   What|Removed |Added

 Resolution|WAITINGFORINFO  |---
 Status|NEEDSINFO   |REPORTED

-- 
You are receiving this mail because:
You are watching all bug changes.

[plasmashell] [Bug 478478] A lot of random crashing

[Bug Janitor Service]

https://bugs.kde.org/show_bug.cgi?id=478478

--- Comment #5 from Bug Janitor Service  ---
Dear Bug Submitter,

This bug has been in NEEDSINFO status with no change for at least
15 days. Please provide the requested information as soon as
possible and set the bug status as REPORTED. Due to regular bug
tracker maintenance, if the bug is still in NEEDSINFO status with
no change in 30 days the bug will be closed as RESOLVED > WORKSFORME
due to lack of needed information.

For more information about our bug triaging procedures please read the
wiki located here:
https://community.kde.org/Guidelines_and_HOWTOs/Bug_triaging

If you have already provided the requested information, please
mark the bug as REPORTED so that the KDE team knows that the bug is
ready to be confirmed.

Thank you for helping us make KDE software even better for everyone!

-- 
You are receiving this mail because:
You are watching all bug changes.

[plasmashell] [Bug 478478] A lot of random crashing

[Peter_H]

https://bugs.kde.org/show_bug.cgi?id=478478

--- Comment #4 from Peter_H  ---
Another crash, this time it's startplasma-x11 crashing on login so I'm kicked
out and back to login screen. Have to reboot to be able to login

coredumpctl gdb 1028
   PID: 1028 (startplasma-x11)
   UID: 1000 (raddinox)
   GID: 1000 (raddinox)
Signal: 11 (SEGV)
 Timestamp: Fri 2023-12-22 14:08:39 CET (5min ago)
  Command Line: /usr/bin/startplasma-x11
Executable: /usr/bin/startplasma-x11
 Control Group: /user.slice/user-1000.slice/session-4.scope
  Unit: session-4.scope
 Slice: user-1000.slice
   Session: 4
 Owner UID: 1000 (raddinox)
   Boot ID: f0578c4823774962ab8c482a07eb2fab
Machine ID: 2b85e2c6b2dd4c66aba122262341bd4a
  Hostname: Universe30
   Storage:
/var/lib/systemd/coredump/core.startplasma-x11.1000.f0578c4823774962ab8c482a07eb2fab.1028.170325051900.zst
(present)
  Size on Disk: 757.8K
   Message: Process 1028 (startplasma-x11) of user 1000 dumped core.

Stack trace of thread 1028:
#0  0x7fb05dc7892c n/a (ld-linux-x86-64.so.2 + 0xe92c)
#1  0x7fb05dc88489 n/a (ld-linux-x86-64.so.2 + 0x1e489)
#2  0x7fb05dc84cd3 n/a (ld-linux-x86-64.so.2 + 0x1acd3)
#3  0x7fb05dc8643e n/a (ld-linux-x86-64.so.2 + 0x1c43e)
#4  0x7fb05dc852a8 n/a (ld-linux-x86-64.so.2 + 0x1b2a8)
ELF object binary architecture: AMD x86-64

GNU gdb (GDB) 13.2
Copyright (C) 2023 Free Software Foundation, Inc.
License GPLv3+: GNU GPL version 3 or later 
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:
.
Find the GDB manual and other documentation resources online at:
.

For help, type "help".
Type "apropos word" to search for commands related to "word"...
Reading symbols from /usr/bin/startplasma-x11...

This GDB supports auto-downloading debuginfo from the following URLs:
  
Enable debuginfod for this session? (y or [n]) y
Debuginfod has been enabled.
To make this setting permanent, add 'set debuginfod enabled on' to .gdbinit.
Reading symbols from
/home/raddinox/.cache/debuginfod_client/3c27863a9d263ec1037f91d65597c62ffd7ebc50/debuginfo...
[New LWP 1028]
   
  --Type  for more, q to quit, c to continue
without paging--c
[Thread debugging using libthread_db enabled]   
Using host libthread_db library "/usr/lib/libthread_db.so.1".
Core was generated by `/usr/bin/startplasma-x11'.
Program terminated with signal SIGSEGV, Segmentation fault.
#0  0x7fb05dc7892c in elf_machine_rela_relative
(reloc_addr_arg=0x8fb05c09cae8, reloc=0x7fb05bad7b30, 
l_addr=) at ../sysdeps/x86_64/dl-machine.h:483
483 *(Elf64_Addr *) reloc_addr = (Elf64_Addr) l_addr + reloc->r_addend; 
(gdb) bt
#0  0x7fb05dc7892c in elf_machine_rela_relative
(reloc_addr_arg=0x8fb05c09cae8, reloc=0x7fb05bad7b30, l_addr=)
at ../sysdeps/x86_64/dl-machine.h:483
#1  elf_dynamic_do_Rela
(skip_ifunc=, lazy=0, nrelative=5830, relsize=659208,
reladdr=140395428990024, scope=, map=0x7fb05d49ff50) at
/usr/src/debug/glibc/glibc/elf/do-rel.h:124
#2  _dl_relocate_object
(l=l@entry=0x7fb05d49ff50, scope=, reloc_mode=, consider_profiling=, consider_profiling@entry=0) at
dl-reloc.c:301
#3  0x7fb05dc88489 in dl_main
(phdr=, phnum=, user_entry=,
auxv=)
at rtld.c:2305
#4  0x7fb05dc84cd3 in _dl_sysdep_start
(start_argptr=start_argptr@entry=0x7ffeb4d25f80,
dl_main=dl_main@entry=0x7fb05dc86740 )
at ../sysdeps/unix/sysv/linux/dl-sysdep.c:140
#5  0x7fb05dc8643e in _dl_start_final (arg=0x7ffeb4d25f80) at rtld.c:494
#6  _dl_start (arg=0x7ffeb4d25f80) at rtld.c:581
#7  0x7fb05dc852a8 in _dl_start_user () at /lib64/ld-linux-x86-64.so.2
#8  0x0001 in  ()
#9  0x7ffeb4d267f2 in  ()
#10 0x in  ()

-- 
You are receiving this mail because:
You are watching all bug changes.

[plasmashell] [Bug 478478] A lot of random crashing

[Peter_H]

https://bugs.kde.org/show_bug.cgi?id=478478

--- Comment #3 from Peter_H  ---
So I have cleared out my Home folder on Arch Linux to try with a fresh KDE
config for a longer period of time. This has been working better than before,
at least from a KDE perspective.

I have hade issues with Konsole and Gwenview not starting. There is no coredump
generated, and trying to start the software in question through Xterm has
printed some failure in loading a shared library (.so) file. Reboot has fixed
this, and sometimes if I knew what package I could reinstall the package and it
would be solved.

I have had some wierd crashes in other software not related to KDE as well,
like wine and conky.

So I'm back into thinking this is some hardware issue, creating crashes with
some random bit-flips/read error. But Memtest86+ still does not report any
errors. What is the most likely hardware to cause an error like this? Read
error from NVME? or broken CPU bit-flipping, or broken RAM?

Another crash report from plasmashell
coredumpctl gdb 1122
   PID: 1122 (plasmashell)
   UID: 1000 (raddinox)
   GID: 1000 (raddinox)
Signal: 11 (SEGV)
 Timestamp: Thu 2023-12-21 13:20:44 CET (25s ago)
  Command Line: /usr/bin/plasmashell --no-respawn
Executable: /usr/bin/plasmashell
 Control Group:
/user.slice/user-1000.slice/user@1000.service/session.slice/plasma-plasmashell.service
  Unit: user@1000.service
 User Unit: plasma-plasmashell.service
 Slice: user-1000.slice
 Owner UID: 1000 (raddinox)
   Boot ID: d70240671eb740a5867043e6e2c4331f
Machine ID: 2b85e2c6b2dd4c66aba122262341bd4a
  Hostname: Universe30
   Storage:
/var/lib/systemd/coredump/core.plasmashell.1000.d70240671eb740a5867043e6e2c4331f.1122.170316124400.zst
(present)
  Size on Disk: 16.7M
   Message: Process 1122 (plasmashell) of user 1000 dumped core.

Stack trace of thread 1122:
#0  0x7f9c16eac83c n/a (libc.so.6 + 0x8e83c)
#1  0x7f9c16e5c668 raise (libc.so.6 + 0x3e668)
#2  0x7f9c1983088f _ZN6KCrash19defaultCrashHandlerEi
(libKF5Crash.so.5 + 0x788f)
#3  0x7f9c16e5c710 n/a (libc.so.6 + 0x3e710)
#4  0x7f9c180ecb3d
_ZN14KProcessRunner4initERK28QExplicitlySharedDataPointerI8KServiceERK7QStringS7_S7_RK10QByteArray
(libKF5KIOGui.so.5 + 0x1cb3d)
#5  0x7ffcf93ebc70 n/a (n/a + 0x0)
#6  0x7ffcf93ebd20 n/a (n/a + 0x0)
ELF object binary architecture: AMD x86-64

GNU gdb (GDB) 13.2
Copyright (C) 2023 Free Software Foundation, Inc.
License GPLv3+: GNU GPL version 3 or later 
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:
.
Find the GDB manual and other documentation resources online at:
.

For help, type "help".
Type "apropos word" to search for commands related to "word"...
Reading symbols from /usr/bin/plasmashell...

This GDB supports auto-downloading debuginfo from the following URLs:
  
Enable debuginfod for this session? (y or [n]) y
Debuginfod has been enabled.
To make this setting permanent, add 'set debuginfod enabled on' to .gdbinit.
Reading symbols from
/home/raddinox/.cache/debuginfod_client/1aced287a50f338d96a0aef654971cd0d96fbd3c/debuginfo...

warning: Can't open file /memfd:JSGCHeap:QtQml (deleted) during file-backed
mapping note processing

warning: Can't open file /memfd:JITCode:QtQml (deleted) during file-backed
mapping note processing

warning: Can't open file /memfd:unknown-usage:QtQml (deleted) during
file-backed mapping note processing

warning: Can't open file /memfd:pulseaudio (deleted) during file-backed mapping
note processing

warning: Can't open file
/mnt/home/raddinox.arch/.cache/plasmashell/qmlcache/33c917e773abe4bc3a0103a6068c9216dcb36d95.qmlc
(deleted) during file-backed mapping note processing

warning: Can't open file
/mnt/home/raddinox.arch/.cache/plasmashell/qmlcache/1b5209199f08f45647dca2dcf400e9be889314d2.qmlc
(deleted) during file-backed mapping note processing

warning: Can't open file
/mnt/home/raddinox.arch/.cache/plasmashell/qmlcache/c1600cc797c41f278479c5812c87627ad5efdfe4.qmlc
(deleted) during file-backed mapping note processing

warning: Can't open file
/mnt/home/raddinox.arch/.cache/plasmashell/qmlcache/5c5649af53bb78a2255cc07dba00b5d037690788.qmlc
(deleted) during file-backed mapping note processing

warning: Can't open file
/mnt/home/raddinox.arch/.cache/plasmashell/qmlcache/deee88605d9768c1308bf3a2402a425b5f9cf35b.qmlc
(deleted) during file-backed mapping note p

[plasmashell] [Bug 478478] A lot of random crashing

[Peter_H]

https://bugs.kde.org/show_bug.cgi?id=478478

--- Comment #2 from Peter_H  ---
(In reply to Harald Sitter from comment #1)
> Unsurprising that only our software is affected since the crash happens
> inside Qt SVG handling
> 
> #11 0x7fb9b8bd194d in QSvgHandler::endElement(QStringRef const&)
> (this=0x2,
> this@entry=0x7fffb57ccc70, localName=...) at
> /usr/src/debug/qt5-svg/qtsvg/src/svg/qsvghandler.cpp:3879
> #12 0x7fb9b8bd852c in QSvgHandler::parse() (this=0x7fffb57ccc70)
> at /usr/src/debug/qt5-svg/qtsvg/src/svg/qsvghandler.cpp:3700
> 
> This looks rather mysterious. First we have a `this` and then it disappears
> into a nullptr. Rather strange that. I am wondering... does this also happen
> with a new user? My suspicion would be that there is an SVG in your home
> that breaks the handler somehow.

Thank you for looking into this. I did have some crashing when I switched from
Debian to Arch Linux. I did not restore my settings at once just for this
purpose of testing. But I don't have any crash logs for the crashing before I
restored my KDE configs.

I will clear out my $HOME for my Arch Linux user and run with fresh settings
for a while and save some coredump backtraces if it crashes.

-- 
You are receiving this mail because:
You are watching all bug changes.

[plasmashell] [Bug 478478] A lot of random crashing

[Nate Graham]

https://bugs.kde.org/show_bug.cgi?id=478478

Nate Graham  changed:

   What|Removed |Added

 CC||n...@kde.org

-- 
You are receiving this mail because:
You are watching all bug changes.

[plasmashell] [Bug 478478] A lot of random crashing

[Harald Sitter]

https://bugs.kde.org/show_bug.cgi?id=478478

Harald Sitter  changed:

   What|Removed |Added

 CC||sit...@kde.org
 Status|REPORTED|NEEDSINFO
 Resolution|--- |WAITINGFORINFO

--- Comment #1 from Harald Sitter  ---
Unsurprising that only our software is affected since the crash happens inside
Qt SVG handling

#11 0x7fb9b8bd194d in QSvgHandler::endElement(QStringRef const&) (this=0x2,
this@entry=0x7fffb57ccc70, localName=...) at
/usr/src/debug/qt5-svg/qtsvg/src/svg/qsvghandler.cpp:3879
#12 0x7fb9b8bd852c in QSvgHandler::parse() (this=0x7fffb57ccc70)
at /usr/src/debug/qt5-svg/qtsvg/src/svg/qsvghandler.cpp:3700

This looks rather mysterious. First we have a `this` and then it disappears
into a nullptr. Rather strange that. I am wondering... does this also happen
with a new user? My suspicion would be that there is an SVG in your home that
breaks the handler somehow.

-- 
You are receiving this mail because:
You are watching all bug changes.