Dear Maintainer,

*** Reporter, please consider answering these questions, where appropriate ***

What led up to the situation?

I installed the official packages gcin and hime on Debian 12.
What exactly did you do (or not do) that was effective (or ineffective)?

I successfully installed these two packages. However, after the installation, when I tried to launch or log into my KDE desktop environment, I couldn't access it.
What was the outcome of this action?

I was unable to access or use my KDE desktop environment.
What outcome did you expect instead?

I expected to be able to access and use my KDE desktop environment normally after installing gcin and hime.

*** End of the template - remove these template lines ***

Thanks for your report.

I used my Kubuntu 23.04 installation to test, but neither with gcin nor
hime I could reproduce the problem with not being able to enter the
Plasma session.

I did encounter a problem with gcin refusing to start in Plasma
(Wayland), but that's a separate thing which is said to be fixed in
Debian 12.

So since the issue you reported is not easily reproducible, we need more
info to be able to address this bug report. Are you able to provide a
log file showing a failed login attempt?

Another thing is that you can run:

im-config -n none

and with that prevent im-config from automatically starting and
configuring gcin or hime at login. Doing so should reasonably allow you
to log in and study what happens when you try to start gcin/hime manually.

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 <owner@bugs.debian.org> 寫道：