Skip site navigation (1)Skip section navigation (2) 
Date:      Sun, 11 Apr 2021 02:52:26 +0000
From:      bugzilla-noreply@freebsd.org
To:        enlightenment@FreeBSD.org
Subject:   E on FreeBSD: [Bug 254970] x11/terminology desktop environment becomes nearly unresponsive; problems involving devel/efl efreetd
Message-ID:  <bug-254970-33756@https.bugs.freebsd.org/bugzilla/>
next in thread | raw e-mail | index | archive | help 
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=3D254970

            Bug ID: 254970
           Summary: x11/terminology desktop environment becomes nearly
                    unresponsive; problems involving devel/efl efreetd
           Product: Ports & Packages
           Version: Latest
          Hardware: Any
                OS: Any
            Status: New
          Severity: Affects Only Me
          Priority: ---
         Component: Individual Port(s)
          Assignee: enlightenment@FreeBSD.org
          Reporter: grahamperrin@gmail.com
          Assignee: enlightenment@FreeBSD.org
             Flags: maintainer-feedback?(enlightenment@FreeBSD.org)

I can't recall when I first installed Terminology (maybe years ago). I vagu=
ely
recall it being OK at the time.=20

Today I tried maybe three times to use Terminology 1.9.0 with KDE Plasma on
FreeBSD 14.0-CURRENT. On each occasion, shortly after performing a few acti=
ons
the system became largely unresponsive for long periods. Almost no response=
 to
input on a peripheral USB keyboard; almost no response to trackball or trac=
kpad
input; and so on. htop in Konsole showed the kernel using around 300% CPU (4
CPUs).=20

Actions such as:=20

* using the scaler at start time

* clicking the grid button at top right

* resizing or moving the window

=E2=80=93 nothing extraordinary.=20

If I recall correctly: on the first occasion, Control-Alt-F2 eventually (af=
ter
a long wait) got me to ttyv1 where I used htop to kill the process.=20

In all cases: after killing or quitting Terminology, problems ceased.=20

Below, the tail of /var/log/messages

----


Apr 11 02:39:39 mowa219-gjp4-8570p kernel: sonewconn: pcb 0xfffff80367363100
(local:/var/run/user/1002/.ecore/efreetd/0): Listen queue overflow: 1 alrea=
dy
in queue awaiting acceptance (1 occurrences)
Apr 11 02:41:05 mowa219-gjp4-8570p efreetd[75523]: stack overflow detected;
terminated
Apr 11 02:41:06 mowa219-gjp4-8570p kernel: pid 75523 (efreetd), jid 0, uid
1002: exited on signal 6 (core dumped)
Apr 11 02:41:07 mowa219-gjp4-8570p kernel: sonewconn: pcb 0xfffff80234076d00
(local:/var/run/user/1002/.ecore/efreetd/0): Listen queue overflow: 1 alrea=
dy
in queue awaiting acceptance (1 occurrences)
Apr 11 02:43:51 mowa219-gjp4-8570p login[1784]: ROOT LOGIN (root) ON ttyv1
Apr 11 02:44:07 mowa219-gjp4-8570p efreetd[75539]: stack overflow detected;
terminated
Apr 11 02:44:07 mowa219-gjp4-8570p kernel: pid 75539 (efreetd), jid 0, uid
1002: exited on signal 6 (core dumped)
Apr 11 02:44:35 mowa219-gjp4-8570p kernel: pid 75534 (urxvt), jid 0, uid 10=
02:
exited on signal 10
Apr 11 02:50:53 mowa219-gjp4-8570p kernel: sonewconn: pcb 0xfffff803a151fc00
(local:/var/run/user/1002/.ecore/efreetd/0): Listen queue overflow: 1 alrea=
dy
in queue awaiting acceptance (1 occurrences)
Apr 11 02:51:35 mowa219-gjp4-8570p efreetd[75644]: stack overflow detected;
terminated
Apr 11 02:51:36 mowa219-gjp4-8570p kernel: pid 75644 (efreetd), jid 0, uid
1002: exited on signal 6 (core dumped)
Apr 11 02:52:22 mowa219-gjp4-8570p efreetd[75647]: stack overflow detected;
terminated
Apr 11 02:53:43 mowa219-gjp4-8570p kernel: pid 75647 (efreetd), jid 0, uid
1002: exited on signal 6 (core dumped)
Apr 11 02:54:42 mowa219-gjp4-8570p kernel: pid 75636 (urxvt), jid 0, uid 10=
02:
exited on signal 10
Apr 11 03:01:23 mowa219-gjp4-8570p kernel: pid 75672 (urxvt), jid 0, uid 10=
02:
exited on signal 10
Apr 11 03:01:30 mowa219-gjp4-8570p kernel: sonewconn: pcb 0xfffff80359509100
(local:/var/run/user/1002/.ecore/efreetd/0): Listen queue overflow: 1 alrea=
dy
in queue awaiting acceptance (1 occurrences)
Apr 11 03:02:16 mowa219-gjp4-8570p efreetd[75681]: stack overflow detected;
terminated
Apr 11 03:02:17 mowa219-gjp4-8570p kernel: pid 75681 (efreetd), jid 0, uid
1002: exited on signal 6 (core dumped)
Apr 11 03:03:53 mowa219-gjp4-8570p efreetd[75687]: stack overflow detected;
terminated
Apr 11 03:04:24 mowa219-gjp4-8570p kernel: pid 75687 (efreetd), jid 0, uid
1002: exited on signal 6 (core dumped)
Apr 11 03:05:46 mowa219-gjp4-8570p kernel: sonewconn: pcb 0xfffff802538eda00
(local:/var/run/user/1002/.ecore/efreetd/0): Listen queue overflow: 1 alrea=
dy
in queue awaiting acceptance (1 occurrences)
Apr 11 03:08:02 mowa219-gjp4-8570p efreetd[75691]: stack overflow detected;
terminated
Apr 11 03:08:03 mowa219-gjp4-8570p kernel: pid 75691 (efreetd), jid 0, uid
1002: exited on signal 6 (core dumped)

--=20
You are receiving this mail because:
You are the assignee for the bug.=

Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?bug-254970-33756>