Dear Maintainer,



    * What led up to the situation?
    I simply started X11 desktop.

    * What exactly did you do (or not do) that was effective (or
      ineffective)?
    Nothing in particular. I simply logged in as a normal user.

    * What was the outcome of this action?
    I found that xiccd segfaulted. I noticed it in the output of demsg.
    This is immediately after I opened a few terminal windows and ran
    dmesg.

[    6.506567] audit: type=1400 audit(1766020708.797:128):
apparmor="ALLOWED"
operation="open" class="file" profile="Xorg" name="/dev/udmabuf" pid=3288
comm="Xorg" requested_mask="wr" denied_mask="wr" fsuid=0 ouid=0
[    6.514919] audit: type=1400 audit(1766020708.805:129):
apparmor="ALLOWED"
operation="capable" class="cap" profile="Xorg" pid=3288 comm="Xorg"
capability=12  capname="net_admin"
[    7.160945] systemd-journald[536]: Time jumped backwards, rotating.
[   26.601503] xiccd[5926]: segfault at 0 ip 00007f9955f86987 sp
00007ffdab899db8 error 4 in libc.so.6[166987,7f9955e48000+165000] likely
on CPU
4 (core 0, socket 8)
[   26.601519] Code: 48 01 d0 c5 f8 77 c3 66 2e 0f 1f 84 00 00 00 00 00
66 90
c4 41 01 ef ff 89 f8 09 f0 c1 e0 14 3d 00 00 00 f8 0f 87 29 03 00 00
<c5> fe 6f
07 c5 fd 74 0e c5 85 74 d0 c5 ed df c9 c5 fd d7 c9 ff c1
root@ip030:/home/ishikawa#

    * What outcome did you expect instead?
    xiccd should not segfault


    I am running Debian GNU/Linux within vmware workstation pro 25H2.
    This *may* have something tod

Dear Chiaki,

I am going to "adopt" this package as maintainer.

Then, for this report,
can you try to get the backtrace?

You may install xiccd-dbgsym instead of xiccd
and proceed like below:

(outline)

edit sources.list of apt and add like:
deb http://debug.mirrors.debian.org/debian-debug/ trixie-debug main

sudo apt update
sudo apt install xiccd-dbgsym libc6-dbgsym

start xiccd then segfaults will happens

coredumpctl gdb xiccd
# after gdb started
(gdb) bt full