[ubuntu-mono] [Bug 151047] Re: vte# segfaults when the Vte.Teminal.Commit signal is used

rusivi1 151047 at bugs.launchpad.net
Fri Sep 17 03:23:13 UTC 2010


Thank you for taking the time to report this bug and helping to make
Ubuntu better. The version of Ubuntu your using is in End of Life
status. More information may be found at:
https://wiki.ubuntu.com/Releases As well, the issue that you reported
should be reproducible with the live environment of the Desktop CD
development release - Maverick Meerkat. It would help us greatly if you
could test with it so we can work on getting it fixed in the next
release of Ubuntu. You can find out more about the development release
at http://www.ubuntu.com/testing/. Please repost a detailed error report
and update the bug status. Thanks again and we appreciate your help.

** Changed in: gtk-sharp2 (Ubuntu)
       Status: New => Incomplete

-- 
vte# segfaults when the Vte.Teminal.Commit signal is used
https://bugs.launchpad.net/bugs/151047
You received this bug notification because you are a member of Ubuntu
CLI/Mono Uploaders, which is subscribed to gtk-sharp2 in ubuntu.

Status in “gtk-sharp2” package in Ubuntu: Incomplete

Bug description:
Binary package hint: libvte-cil

This bug was discovered when developing with vte#, and a fix was sent to Mike Kestner (the gtk#/gnome# maintainer) who commited it. The fix in question can be found here:

http://anonsvn.mono-project.com/viewcvs/trunk/gnome-sharp/vte/Vte.metadata?rev=84241&r1=63555&r2=84241

I will attach a small test case that demonstrates the crasher, and which works with the above patch applied to vte#. Nothing except the Commit signal (and the OnCommit protected method) is changed by the patch.






More information about the Ubuntu-mono mailing list