Summary: | x11-terms/wterm-6.2.9-r2 crashes on extreme resizing | ||
---|---|---|---|
Product: | Gentoo Linux | Reporter: | Santiago M. Mola (RETIRED) <coldwind> |
Component: | New packages | Assignee: | No maintainer - Look at https://wiki.gentoo.org/wiki/Project:Proxy_Maintainers if you want to take care of it <maintainer-needed> |
Status: | RESOLVED WONTFIX | ||
Severity: | normal | CC: | treecleaner |
Priority: | High | Keywords: | PMASKED |
Version: | unspecified | ||
Hardware: | All | ||
OS: | Linux | ||
Whiteboard: | Pending Removal: 2012-03-12 | ||
Package list: | Runtime testing required: | --- |
Description
Santiago M. Mola (RETIRED)
2008-03-24 15:58:23 UTC
I can confirm this, did some debugging but failed. does not reproduce in "gdb wterm ; run" Looks like upstream is dead, I would vote for simply treecleaning this dropped Hey, I use this terminal on a regular basis!!!!! I run the script: #/bin/bash source /etc/profile wterm -sl 70000 -si -sk -st -sr -bg black -fg white -geometry 146x36 -ut -C -title '' -fn and it work 100%, the greatest terminal I've got. Please put this terminal back into portage so that I, and everyone else, can emerge it. re: >> Resize (I did with modkey + mouse) and try to bring the right side past the left side (like if you wanted to resize to width 0). Why would I want to do that? I'm not able to reproduce this error but there if it is just "integer parameter out of range for operation" the fix should be relatively simple. (In reply to comment #4) > Hey, I use this terminal on a regular basis!!!!! > > I run the script: > > #/bin/bash > source /etc/profile > wterm -sl 70000 -si -sk -st -sr -bg black -fg white -geometry 146x36 -ut > -C -title '' -fn > > > and it work 100%, the greatest terminal I've got. > > Please put this terminal back into portage so that I, and everyone else, can > emerge it. > > > > re: > >> Resize (I did with modkey + mouse) and try to bring the right side past > the left side (like if you wanted to resize to width 0). > > Why would I want to do that? I'm not able to reproduce this error but there > if it is just "integer parameter out of range for operation" the fix should > be relatively simple. show us an active fork otherwise... last release is from 2005. If I had to change something in the build system I would need to rewrite it from scratch (cause almost all autotools macros would be broken). So to start someone would have to: a) fork it b) fix this bug c) rewrite the entire build system This bug is closed. The package is gone. Please don't write anymore on this bug cos nobody will do anything to please you. (In reply to comment #6) > This bug is closed. The package is gone. Please don't write anymore on this > bug cos nobody will do anything to please you. I will re-include wterm if there is a proper fork, so I don't see a reason not to write here. (In reply to comment #7) > (In reply to comment #6) > > This bug is closed. The package is gone. Please don't write anymore on this > > bug cos nobody will do anything to please you. > > I will re-include wterm if there is a proper fork, so I don't see a reason > not to write here. The process will be similar to any other ebuild. Open a bug assigned to maintainer-wanted@ and let someone handle this. The new package (must of course) solves all the problems that lead to the previous one dropped from the tree. This is what we did/dofor resurrected packages. |