This is the error report on my host machine.

Hint: You are currently not seeing messages from other users and the system.
      Users in groups 'adm', 'systemd-journal' can see all messages.
      Pass -q to turn off this notice.
           PID: 2006 (gcin)
           UID: 1000 (zendas)
           GID: 1000 (zendas)
        Signal: 11 (SEGV)
     Timestamp: Wed 2023-08-23 09:31:46 CST (1 day 14h ago)
  Command Line: /usr/bin/gcin
    Executable: /usr/bin/gcin
 Control Group: 
/user.slice/user-1000.slice/user@1000.service/app.slice/app-im\x2dlaunch@autostart.service
          Unit: user@1000.service
     User Unit: app-im\x2dlaunch@autostart.service
         Slice: user-1000.slice
     Owner UID: 1000 (zendas)
       Boot ID: 2396e901668b41efb39aa31eaedfb918
    Machine ID: 9738094c31254caba3c91410247f4592
      Hostname: TMP249
       Storage: 
/var/lib/systemd/coredump/core.gcin.1000.2396e901668b41efb39aa31eaedfb918.2006.1692754306000000.zst
 (present)
  Size on Disk: 895.0K
       Message: Process 2006 (gcin) of user 1000 dumped core.
                
                Module libsystemd.so.0 from deb systemd-252.12-1~deb12u1.amd64
                Stack trace of thread 2006:
                #0  0x0000560399412055 n/a (gcin + 0xd055)
                #1  0x00007fe6cab3c1ca n/a (libc.so.6 + 0x271ca)
                #2  0x00007fe6cab3c285 __libc_start_main (libc.so.6 + 0x27285)
                #3  0x0000560399411731 n/a (gcin + 0xc731)
                
                Stack trace of thread 2009:
                #0  0x00007fe6cac1103f __poll (libc.so.6 + 0xfc03f)
                #1  0x00007fe6caf6b9ae n/a (libglib-2.0.so.0 + 0x549ae)
                #2  0x00007fe6caf6bacc g_main_context_iteration 
(libglib-2.0.so.0 + 0x54acc)
                #3  0x00007fe6caf6bb11 n/a (libglib-2.0.so.0 + 0x54b11)
                #4  0x00007fe6caf95cfd n/a (libglib-2.0.so.0 + 0x7ecfd)
                #5  0x00007fe6cab9e044 n/a (libc.so.6 + 0x89044)
                #6  0x00007fe6cac1e5fc n/a (libc.so.6 + 0x1095fc)
                
                Stack trace of thread 2010:
                #0  0x00007fe6cac16539 syscall (libc.so.6 + 0x101539)
                #1  0x00007fe6cafc050c g_cond_wait_until (libglib-2.0.so.0 + 
0xa950c)
                #2  0x00007fe6caf39881 n/a (libglib-2.0.so.0 + 0x22881)
                #3  0x00007fe6caf96722 n/a (libglib-2.0.so.0 + 0x7f722)
                #4  0x00007fe6caf95cfd n/a (libglib-2.0.so.0 + 0x7ecfd)
                #5  0x00007fe6cab9e044 n/a (libc.so.6 + 0x89044)
                #6  0x00007fe6cac1e5fc n/a (libc.so.6 + 0x1095fc)
                
                Stack trace of thread 2011:
                #0  0x00007fe6cac1103f __poll (libc.so.6 + 0xfc03f)
                #1  0x00007fe6caf6b9ae n/a (libglib-2.0.so.0 + 0x549ae)
                #2  0x00007fe6caf6bcef g_main_loop_run (libglib-2.0.so.0 + 
0x54cef)
                #3  0x00007fe6caa3a8f6 n/a (libgio-2.0.so.0 + 0x1188f6)
                #4  0x00007fe6caf95cfd n/a (libglib-2.0.so.0 + 0x7ecfd)
                #5  0x00007fe6cab9e044 n/a (libc.so.6 + 0x89044)
                #6  0x00007fe6cac1e5fc n/a (libc.so.6 + 0x1095fc)
                
                Stack trace of thread 2012:
                #0  0x00007fe6cac1103f __poll (libc.so.6 + 0xfc03f)
                #1  0x00007fe6caf6b9ae n/a (libglib-2.0.so.0 + 0x549ae)
                #2  0x00007fe6caf6bacc g_main_context_iteration 
(libglib-2.0.so.0 + 0x54acc)
                #3  0x00007fe6c99bc4bd n/a (libdconfsettings.so + 0xb4bd)
                #4  0x00007fe6caf95cfd n/a (libglib-2.0.so.0 + 0x7ecfd)
                #5  0x00007fe6cab9e044 n/a (libc.so.6 + 0x89044)
                #6  0x00007fe6cac1e5fc n/a (libc.so.6 + 0x1095fc)
                ELF object binary architecture: AMD x86-64





------- Original Message -------
在 2023年8月24日 星期四 下午 4:45,Debian Bug Tracking System <ow...@bugs.debian.org> 寫道:


> 
> 
> Thank you for filing a new Bug report with Debian.
> 
> You can follow progress on this Bug here: 1050410: 
> https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1050410.
> 
> This is an automatically generated reply to let you know your message
> has been received.
> 
> Your message is being forwarded to the package maintainers and other
> interested parties for their attention; they will reply in due course.
> 
> As you requested using X-Debbugs-CC, your message was also forwarded to
> zen...@pm.me
> (after having been given a Bug report number, if it did not have one).
> 
> Your message has been sent to the package maintainer(s):
> Debian Input Method Team debian-input-met...@lists.debian.org
> 
> 
> If you wish to submit further information on this problem, please
> send it to 1050...@bugs.debian.org.
> 
> Please do not send mail to ow...@bugs.debian.org unless you wish
> to report a problem with the Bug-tracking system.
> 
> --
> 1050410: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1050410
> Debian Bug Tracking System
> Contact ow...@bugs.debian.org with problems

Reply via email to