Hmmmm.... trying to make sense of it...
There's hardly any code from gnome-terminal itself in the stack trace,
most of them is from GTK.
#10 is from update_color_scheme():
if (gdk_rgba_hash (&priv->bg_color) != gdk_rgba_hash (&bg))
{
priv->bg_color = bg;
g_object_notify (G_OBJECT (screen), "bg-color"); <---- this line
}
#0 gtk_widget_queue_draw() is called by #1 g_closure_invoke(), so the
former is called as a callback registered earlier. The only place where
this method can be registered as a callback is in
terminal_screen_container_constructed():
g_signal_connect_swapped (priv->screen, "notify::bg-color",
G_CALLBACK (gtk_widget_queue_draw),
priv->vscrollbar);
and it's indeed about the same "bg-color" signal, so I'm quite sure this
is where we are.
Now, this is not part of upstream gnome-terminal. It's added by Ubuntu's
"scrollbar-background-theming.patch", as per lp:1493964, which tries to
theme the scrollbar to match the terminal screen's main background
color.
I suspect that toggling the scrollbar's visibility might eliminate this
bug for you. Also, if you're familiar with recompiling Ubuntu packages
with tiny modifications, I'm fairly confident that dropping this patch
should fix the problem. Installed packages, modules, settings, whatnot
related to GTK scrollbars (e.g. choosing whether to use an overlay or
traditional one, etc.) might easily be relevant to whether this bug
occurs.
I'm not an Ubuntu developer, and I'm not affiliated with Ubuntu or
Launchpad. I'm a GNOME Terminal developer. At this point, I suspect with
99%+ certainity that upstream GNOME Terminal is not affected by the bug,
it's introduced by Ubuntu (or maybe Debian). Therefore I'm sorry but I'm
afraid I won't be able to help any further, the investigation and fixing
should be continued by Ubuntu devs.
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to gnome-terminal in Ubuntu.
https://bugs.launchpad.net/bugs/2049923
Title:
gnome-terminal freezing, then crashing
Status in gnome-terminal package in Ubuntu:
New
Bug description:
First: It's very hard to reproduce, but it happens to me about once per week.
If often open new windows or split windows out from tabs. And then it
happens. First it becomes unresponsive, and then after about 2-3 seconds it
simply closes all instances.
[328830.780749] gnome-terminal-[117706]: segfault at 4600000742 ip
00007fdb2fb45611 sp 00007ffdb8c5fda0 error 4 in
libgtk-3.so.0.2406.32[7fdb2f883000+38f000] likely on CPU 4 (core 4, socket 0)
[328830.780761] Code: fb 48 83 ec 20 64 48 8b 04 25 28 00 00 00 48 89
44 24 18 31 c0 e8 bf 6d ff ff 48 85 db 74 7a 48 89 c6 48 8b 03 48 85
c0 74 05 <48> 39 30 74 0c 48 89 df e8 a2 c2 d4 ff 85 c0 74 5e 48 89 e6
48 89
[329377.925310] gnome-terminal-[120116]: segfault at 2f00000774 ip
00007f86af745611 sp 00007ffc9943c5c0 error 4 in
libgtk-3.so.0.2406.32[7f86af483000+38f000] likely on CPU 2 (core 2,
socket 0)
[329377.925324] Code: fb 48 83 ec 20 64 48 8b 04 25 28 00 00 00 48 89
44 24 18 31 c0 e8 bf 6d ff ff 48 85 db 74 7a 48 89 c6 48 8b 03 48 85
c0 74 05 <48> 39 30 74 0c 48 89 df e8 a2 c2 d4 ff 85 c0 74 5e 48 89 e6
48 89
unfortunately, apport isn't automatically creating a crash report.
ProblemType: Bug
DistroRelease: Ubuntu 23.10
Package: gnome-terminal 3.49.92-2ubuntu1
ProcVersionSignature: Ubuntu 6.5.0-14.14-generic 6.5.3
Uname: Linux 6.5.0-14-generic x86_64
ApportVersion: 2.27.0-0ubuntu5
Architecture: amd64
CasperMD5CheckResult: unknown
CurrentDesktop: ubuntu:GNOME
Date: Fri Jan 19 16:48:43 2024
SourcePackage: gnome-terminal
UpgradeStatus: Upgraded to mantic on 2023-10-17 (94 days ago)
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-terminal/+bug/2049923/+subscriptions
--
Mailing list: https://launchpad.net/~desktop-packages
Post to : [email protected]
Unsubscribe : https://launchpad.net/~desktop-packages
More help : https://help.launchpad.net/ListHelp
