Gentoo Websites Logo
Go to: Gentoo Home Documentation Forums Lists Bugs Planet Store Wiki Get Gentoo!
Bug 91878 - eterm-0.9.3-r3: dead keys not working anymore
Summary: eterm-0.9.3-r3: dead keys not working anymore
Status: RESOLVED FIXED
Alias: None
Product: Gentoo Linux
Classification: Unclassified
Component: Current packages (show other bugs)
Hardware: x86 Linux
: High normal (vote)
Assignee: SpanKY
URL: http://sourceforge.net/mailarchive/me...
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2005-05-08 04:27 UTC by Tobias Vogel
Modified: 2005-05-10 17:31 UTC (History)
0 users

See Also:
Package list:
Runtime testing required: ---


Attachments
eterm-0.9.3-deadkeys.patch (eterm-0.9.3-deadkeys.patch,4.56 KB, patch)
2005-05-10 15:14 UTC, SpanKY
Details | Diff

Note You need to log in before you can comment on or make changes to this bug.
Description Tobias Vogel 2005-05-08 04:27:01 UTC
I upgraded from eterm-0.9.2-r6 to eterm-0.9.3-r3, as a dependency libast got upgraded from "0.5-r2" to "0.6.1".

With this new version dead keys (like "~" or backquotes) are not working anymore, which is quite annoying in a shell. When trying to type one of these chars once or multiple times (with or without space after them), simply nothing happens. The settings are correct as it worked before and still does for any X-appclication, terminal and in the text mode console (all without "nodeadkeys" variant).

It is not a setting in "user.cfg", as temporarly removing it to get the default settings doesn't change the behaviour.

Temporary workaround:
I downgraded to eterm-0.9.2-r6, as a dependency libast was downgraded from "0.6.1" to "0.5-r2". Now all dead keys are working again, so the problem seems to be located in one of these two packages.

Reproducible: Always
Steps to Reproduce:
1. emerge -av =x11-terms/eterm-0.9.3-r3
2. open eterm
3. try to type a tilde or a backquote

Actual Results:  
nothing ;-)

Expected Results:  
It should print out the chars mapped to the dead keys.
Comment 1 SpanKY gentoo-dev 2005-05-09 00:05:48 UTC
eterm-0.9.3 can work with libast-0.5 ... i just force the DEPEND to keep things sane ...

try doing:
emerge =libast-0.5*
emerge =eterm-0.9.3* --nodeps

and then see if deadkeys still fail to work properly ...

also, you neglected to post `emerge info` like the bug report page told you to, so make sure you include it this time :P
Comment 2 Tobias Vogel 2005-05-09 02:19:40 UTC
Allright, I tried this one, but eterm-0.9.3 in combination with libast-0.5 shows the same behaviour.


Sorry about the emerge info, there it goes:

Portage 2.0.51.19 (default-linux/x86/2005.0, gcc-3.3.5-20050130, glibc-2.3.4.20041102-r1, 2.6.11-gentoo-r6 i686)
=================================================================
System uname: 2.6.11-gentoo-r6 i686 AMD Athlon(TM) XP 2500+
Gentoo Base System version 1.4.16
Python:              dev-lang/python-2.3.5 [2.3.5 (#1, Apr 30 2005, 11:23:32)]
dev-lang/python:     2.3.5
sys-apps/sandbox:    [Not Present]
sys-devel/autoconf:  2.59-r6, 2.13
sys-devel/automake:  1.7.9-r1, 1.8.5-r3, 1.5, 1.4_p6, 1.6.3, 1.9.5
sys-devel/binutils:  2.15.92.0.2-r7
sys-devel/libtool:   1.5.16
virtual/os-headers:  2.6.8.1-r2
ACCEPT_KEYWORDS="x86"
AUTOCLEAN="yes"
CFLAGS="-march=athlon-xp -O2 -pipe -mmmx -msse -m3dnow"
CHOST="i686-pc-linux-gnu"
CONFIG_PROTECT="/etc /usr/kde/2/share/config /usr/kde/3.3/env /usr/kde/3.3/share/config /usr/kde/3.3/shutdown /usr/kde/3/share/config /usr/lib/X11/xkb /usr/share/config /usr/share/texmf/dvipdfm/config/ /usr/share/texmf/dvips/config/ /usr/share/texmf/tex/generic/config/ /usr/share/texmf/tex/platex/config/ /usr/share/texmf/xdvi/ /var/qmail/control"
CONFIG_PROTECT_MASK="/etc/gconf /etc/terminfo /etc/env.d"
CXXFLAGS="-march=athlon-xp -O2 -pipe -mmmx -msse -m3dnow"
DISTDIR="/usr/portage/distfiles"
FEATURES="autoaddcvs autoconfig ccache distlocks sandbox sfperms strict"
GENTOO_MIRRORS="http://mirror.switch.ch/mirror/gentoo/ ftp://ftp.uni-erlangen.de/pub/mirrors/gentoo ftp://ftp-stud.fht-esslingen.de/pub/Mirrors/gentoo/"
MAKEOPTS="-j2"
PKGDIR="/usr/portage/packages"
PORTAGE_TMPDIR="/var/tmp"
PORTDIR="/usr/portage"
PORTDIR_OVERLAY="/usr/local/portage"
SYNC="rsync://rsync.europe.gentoo.org/gentoo-portage"
USE="3dnow X aac acpi aim alsa apm arts avi berkdb bitmap-fonts bzlib calendar cddb cdparanoia cdr crypt cups curl dedicated directfb divx4linux doc dvd dvdr dvdread emboss encode esd exif fam fbcon ffmpeg flac flash foomaticdb fortran ftp gdbm gif gpm gstreamer gtk gtk2 icq imagemagick imap imlib ipv6 jabber java javascript jpeg junit kde libg++ libwww lirc mad mikmod mime ming mmx motif mp3 mpeg msn mysql ncurses nls nvidia ogg oggvorbis opengl oss pam pdflib perl pic png posix postgres ppds python qt quicktime readline real samba scanner sdl snmp spell sse ssl svg svga tcltk tcpd tetex tidy tiff truetype truetype-fonts type1-fonts unicode usb userlocales v4l vcd vhosts videos vorbis wmf wxwindows x86 xine xml xml2 xmms xv xvid zlib userland_GNU kernel_linux elibc_glibc"
Unset:  ASFLAGS, CBUILD, CTARGET, LANG, LC_ALL, LDFLAGS, LINGUAS
Comment 3 SpanKY gentoo-dev 2005-05-10 15:14:19 UTC
Created attachment 58623 [details, diff]
eterm-0.9.3-deadkeys.patch

please try this patch
Comment 4 Tobias Vogel 2005-05-10 17:06:51 UTC
Thanks, the patch is working and so are deadkeys now. :-)

I added the patch to the ebuild in /usr/portage/x11-terms/eterm, and edited the manifest to work with it. Is this the correct way, or will this cause problems with portage, if I don't manually remove all changes?
Comment 5 SpanKY gentoo-dev 2005-05-10 17:31:47 UTC
next time you `emerge sync` all changes in your portage tree will be lost

not to worry, once i got confirmation this patch worked i was going to add it to portage (which i just did) ... 0.9.3-r4 now in portage

thanks for testing !