Terminal crashed while I was typing a command. It sometimes crashes without a reason. But quite rarely. Here's the record from /var/log/messages: Nov 23 17:13:09 supervisor kernel: Terminal[5661]: segfault at bff9c000 ip b7da4e8d sp bff9a440 error 6 in libvte.so.9.6.0[b7d80000+ac000] Seems like that bug is mostly connected to x11-libs/vte-0.20.5 Please consider moving stable back to vte-0.17.4-r3 I didn't notice same behaviour there. Thank you. Reproducible: Sometimes Steps to Reproduce:
I found similar report here: http://groups.google.com/group/linux.debian.bugs.rc/browse_thread/thread/dc86c7253af2cfa1 Looks like Debian Bug report #548350 is similar to what we have.
http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=548350 "I've uploaded 2.22.1 fixing this." Should be fixed in new x11-libs/vte, moving to gnome@ maintainers so we can get something recent stable.
patches in the debian bug seem to fix it, need to include it in next 2.26 stable roll.
Sorry for mentioning again, but aren't you going to mark release 0.20.5 of vte to be unstable? My Terminal still crashes from time to time... I can't believe that I'm the only person who have this problem.
I think to solve this we should just stabilize 0.22.5 -- backporting the fix is not possible since a lot of the code was rewritten. I have verified that gnome-terminal-2.26.3.1-r2 and terminal-0.4.2 work just fine with vte-0.22.5
(In reply to comment #5) > I think to solve this we should just stabilize 0.22.5 -- backporting the fix is > not possible since a lot of the code was rewritten. > > I have verified that gnome-terminal-2.26.3.1-r2 and terminal-0.4.2 work just > fine with vte-0.22.5 > Is stabilization going to happen?
I am using x11-libs/vte-0.22.5 since more than one month with gnome-terminal-2.26.3.1-r2 with no problems at all, then, I think that it could be stabled without waiting for the rest of gnome 2.28
(In reply to comment #7) > I am using x11-libs/vte-0.22.5 since more than one month with > gnome-terminal-2.26.3.1-r2 with no problems at all, then, I think that it could > be stabled without waiting for the rest of gnome 2.28 > Sorry to push it again, but this isn't moving. Can I read your statement as it's OK to add archteams here for x11-libs/vte-0.22.5 stabilization?
vte-0.22 has drawing bugs that 0.20 does not have, that's why I request a 0.20-rsomething, now if you don't care about those bugs, go ahead.
(In reply to comment #9) > vte-0.22 has drawing bugs that 0.20 does not have, that's why I request a > 0.20-rsomething, now if you don't care about those bugs, go ahead. > Care about what bugs? There's always bugs. You need to be more specific. Been working great here and I can see it's fixing couple of those mentioned drawing bugs per ChangeLog e.g. "Bug 597242 - libvte color and cursor glitches"
There are still bad drawing bugs, like loosing all of your history besides the last ~25 lines all of a sudden, the rest being the background color, which I didn't experience with vte-0.20 series.
(In reply to comment #11) > There are still bad drawing bugs, like loosing all of your history besides the > last ~25 lines all of a sudden, the rest being the background color, which I > didn't experience with vte-0.20 series. > I expected some links to upstream bugs that would block the stabilization. The history bug when resizing is fixed in 0.22.3 per ChangeLog. Also 0.22.5 is the one shipped with Fedora Core 12 and has no patches applied on top of it. So I'm going with Comment #5, Comment #7 and personal experience that it's working great. And most importantly, it doesn't crash like current stable does. Adding arches.
amd64 stable, despite of bug 286375 because it's not a regression
x86 stable
alpha/arm/ia64/sh/sparc stable
ppc64 done
ppc done
Just a heads up this package version is likely to stop compiling when gtk+ is stabilised. The use of GTK_DISABLE_DEPRECATED in the config setup will mean some rather old GTK macros will not be there. =vte-0.24.2 does compile but I have yet to do some stabilisation testing on it.
Stable for HPPA and closing.
