After testing gtk3 version for ~2 weeks I haven't had it crash once so
it is definitely something related to gtk2, so if in future terminator
will only be gtk3-only it probably doesn't make sense to chase that bug
--
You received this bug notification because you are a member of Ubuntu
Bugs, whic
Public bug reported:
After upgrading to 0.97/8 (I've tested both Debian and Ubuntu packages)
in Debian Testing I get random hangs (window freezes, does not respond
to alt+f4. I've managed to get a backtrace in gdb:
http://pastebin.com/HkjPa4br , what else I can do to help debug that ?
** Affects
Thanks, I'll try to debug it tommorrow.
It is REALLY weird case as I basically have 2 machines with almost same
config (as in "I have Puppet manifest that runs on both that deploys
same config for almost everything on both") and it only happens on one
of those (tho it is one I use much more, so I
I've commented that line ( self.set_from_icon_name(icon,
gtk.ICON_SIZE_MENU) ) but it still crashes, looks like something deep in
gtk... I've attached a trace
** Attachment added: "terminator.gdb.txt"
https://bugs.launchpad.net/ubuntu/+source/terminator/+bug/1535364/+attachment/4573726/+files
I have tried that, but it just displayed:
Titlebar::get_desired_visibility: configured visibility: True
Titlebar::get_desired_visibility: configured visibility: True
Titlebar::update_visibility: showing titlebar
stacktrace looked similiar to previous one. I've got the coredumpt altho
> Hi, you have unfortunately over trimmed. Any chance you could post the
last 50 or so lines of the debug output? This way I could more
definitively be sure where we are in the path.
do you mean output from "terminator -d --debug-class
TerminalPopupMenu,Titlebar" ?
It was same 3 lines repeated fe
Same error happens when connecting to libvirt's VM VNC console
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/117229
Title:
vncviewer fais vith "Rect too big"
To manage notifications about this bug
