Bug 224718

Summary: x11/qterminal exits with signal 11 when renaming the session (tab)
Product: Ports & Packages Reporter: Marco Beishuizen <mbeis>
Component: Individual Port(s)Assignee: freebsd-ports-bugs (Nobody) <ports-bugs>
Status: Closed FIXED    
Severity: Affects Only Me CC: jsm
Priority: --- Flags: bugzilla: maintainer-feedback? (jsm)
Version: Latest   
Hardware: Any   
OS: Any   
Attachments:
Description Flags
Patch to fix getting tabindex by contextmenu and tabAt none

Description Marco Beishuizen 2017-12-30 02:35:03 UTC
Using qterminal for a while now and decided to try to change the session name (changing the tab name). But immediately when pressing OK, qterminal exits with a signal 11. No coredump, no further error messages.
Comment 1 Jesper Schmitz Mouridsen freebsd_committer freebsd_triage 2017-12-30 11:18:09 UTC
(In reply to Marco Beishuizen from comment #0)
I cannot reproduce, can you be more detailed about your setup? E.g version of qterminal and qtermwidget window manager etc..
Comment 2 Marco Beishuizen 2017-12-30 12:52:39 UTC
Hi Jesper,

My uname -a is:
FreeBSD yokozuna 11.1-STABLE FreeBSD 11.1-STABLE #0 r322753: Mon Aug 21 22:56:30 CEST 2017     root@yokozuna:/usr/obj/usr/src/sys/YOKOZUNA  amd64

Windowmanager is windowmaker 0.95.8. Qterminal is latest version (0.8.0) and is build with on FreeBSD latest Qt5 5.7.1. Ports are up to date.
Comment 3 Jesper Schmitz Mouridsen freebsd_committer freebsd_triage 2017-12-30 13:59:32 UTC
(In reply to Marco Beishuizen from comment #2)
Can you confirm that this only happens when chaning tab layout?
When having tabs at the bottom I can reproduce the bug, i'm looking into it.
Comment 4 Marco Beishuizen 2017-12-30 14:08:31 UTC
Hey you're right. Having the tabs on the bottom now. Changing to the top and problem dissappears.
Comment 5 Jesper Schmitz Mouridsen freebsd_committer freebsd_triage 2017-12-30 14:40:51 UTC
Created attachment 189221 [details]
Patch to fix getting tabindex by contextmenu and tabAt

see for emplanation https://bugreports.qt.io/browse/QTBUG-16536
Comment 6 Marco Beishuizen 2017-12-31 14:07:28 UTC
Yes patch works!

Thanks,
Marco