I've already posted that bug, see http://bugs.gentoo.org/show_bug.cgi?id=143373. But today, I found out more on it. I compiled both an older version of openmotif and also lesstif, used motif-config and then recompiled xpdf and as I tried out lesstif, the original bug disappeared. So I conclude that xpdf and openmotif do not work together well. Either there is a bug in xpdf or a bug in openmotif. My emerge --info Gentoo Base System version 1.12.6 Portage 2.1.1-r2 (default-linux/x86/2006.0, gcc-4.1.1, glibc-2.3.6-r4, 2.6.18-suspend2 i686) ================================================================= System uname: 2.6.18-suspend2 i686 Intel(R) Pentium(R) M processor 1.86GHz Last Sync: Sat, 23 Dec 2006 12:00:01 +0000 ccache version 2.3 [enabled] app-admin/eselect-compiler: [Not Present] dev-java/java-config: 1.3.7, 2.0.31 dev-lang/python: 2.4.3-r4 dev-python/pycrypto: 2.0.1-r5 dev-util/ccache: 2.3 dev-util/confcache: [Not Present] sys-apps/sandbox: 1.2.17 sys-devel/autoconf: 2.13, 2.60 sys-devel/automake: 1.4_p6, 1.5, 1.6.3, 1.7.9-r1, 1.8.5-r3, 1.9.6-r2 sys-devel/binutils: 2.16.1-r3 sys-devel/gcc-config: 1.3.14 sys-devel/libtool: 1.5.22 virtual/os-headers: 2.6.17-r2 ACCEPT_KEYWORDS="x86" AUTOCLEAN="yes" CBUILD="i686-pc-linux-gnu" CFLAGS="-O2 -pipe" CHOST="i686-pc-linux-gnu" CONFIG_PROTECT="/etc /usr/kde/3.5/env /usr/kde/3.5/share/config /usr/kde/3.5/shutdown /usr/share/X11/xkb /usr/share/config" CONFIG_PROTECT_MASK="/etc/env.d /etc/env.d/java/ /etc/gconf /etc/java-config/vms/ /etc/revdep-rebuild /etc/splash /etc/terminfo /etc/texmf/web2c" CXXFLAGS="-O2 -pipe" DISTDIR="/usr/portage/distfiles" FEATURES="autoconfig ccache distlocks metadata-transfer parallel-fetch sandbox sfperms strict" GENTOO_MIRRORS="http://distfiles.gentoo.org http://distro.ibiblio.org/pub/linux/distributions/gentoo" LANG="german" LC_ALL="de_DE.UTF-8" LINGUAS="de en" PKGDIR="/usr/portage/packages/" PORTAGE_RSYNC_OPTS="--recursive --links --safe-links --perms --times --compress --force --whole-file --delete --delete-after --stats --timeout=180 --exclude='/distfiles' --exclude='/local' --exclude='/packages'" PORTAGE_TMPDIR="/var/tmp" PORTDIR="/usr/portage" PORTDIR_OVERLAY="/usr/local/overlays/xor /usr/portage/local/layman/toe.ch" SYNC="rsync://rsync.gentoo.org/gentoo-portage" USE="x86 7zip X a52 aac aalib acpi alsa alsa_cards_cmipci alsa_cards_intel8x0 alsa_cards_usb-audio alsa_pcm_plugins_adpcm alsa_pcm_plugins_alaw alsa_pcm_plugins_asym alsa_pcm_plugins_copy alsa_pcm_plugins_dmix alsa_pcm_plugins_dshare alsa_pcm_plugins_dsnoop alsa_pcm_plugins_empty alsa_pcm_plugins_extplug alsa_pcm_plugins_file alsa_pcm_plugins_hooks alsa_pcm_plugins_iec958 alsa_pcm_plugins_ioplug alsa_pcm_plugins_ladspa alsa_pcm_plugins_lfloat alsa_pcm_plugins_linear alsa_pcm_plugins_meter alsa_pcm_plugins_mulaw alsa_pcm_plugins_multi alsa_pcm_plugins_null alsa_pcm_plugins_plug alsa_pcm_plugins_rate alsa_pcm_plugins_route alsa_pcm_plugins_share alsa_pcm_plugins_shm alsa_pcm_plugins_softvol apache2 apm arts audiofile bash-completion bcmath berkdb bindist bitmap-fonts bl blender-game bzip2 cairo cdparanoia cdr cli cracklib crypt cscope cups curl dlloader dmi dri dv dvd dvdr dvdread elibc_glibc encode esd exif extrafilters fam fat fbsplash ffmpeg fftw firefox flac flash foomaticdb fortran ftp gdbm gif gimp gimpprint glut gmp gnome gphoto2 gpm gs gstreamer gtk gtk2 gtkhtml gzip hal howl iconv idn ieee1394 imagemagick imlib inkjar input_devices_evdev input_devices_keyboard input_devices_mouse input_devices_synaptics input_devices_vmmouse ipv6 isdnlog jack java jpeg jpeg2k junit kde kernel_linux lcms libg++ libsamplerate libwww linguas_de linguas_en lirc logitech-mouse lzo mad madwifi mcal mhash mikmod ming mjpeg mmx mng motif mozbranding mozdevelop mozsvg mp3 mp4live mpeg mpeg2 ncurses nls nptl nptlonly nsplugin offensive ogg openal opengl oss pam pcre pdf perl php plotutils png portaudio ppds pppd python qt3 qt4 quicktime rar readline recode reflection rtc samba scanner sdl session sftp slang speex spell spl ssl svg svgz swat symlink sysfs szip tcpd tetex threads tidy tiff truetype truetype-fonts type1-fonts udev unicode usb userland_GNU v4l v4l2 vcd vhosts video_cards_fbdev video_cards_fglrx video_cards_glint video_cards_radeon video_cards_v4l vim vim-pager vim-with-x vorbis wifi wma wmf wxwindows xine xinerama xml xorg xprint xscreensaver xv xvid zip zlib" Unset: CTARGET, EMERGE_DEFAULT_OPTS, INSTALL_MASK, LDFLAGS, MAKEOPTS, PORTAGE_RSYNC_EXTRA_OPTS
Created attachment 104757 [details] a screenshot of the original bug
In my experience, and that of many other users, xpdf works even better with openmotif than lesstif, in fact I'm using that combination right now. The real cause for a lot of motif related problems is that motif-config is fundamentally broken. (The previous maintainer is well aware of these problems, but refused to acknowledge them before he left. Just do a bugzilla search from early 2005 till now on this subject.) Currently, the only reliable way is to unmerge all providers of the virtual/motif virtual, unmerge all packages depending on it and start over with exacactly 1 (one) motif library installed. (that would defeat the whole purpose of motif-config, but there you go.) The minute a second provider of virtual/motif is installed, everything is possible, including, but not limited to, cross-linkage between different motif libraries, compiling against headers of current motif-config selection but linking to random other (incompatible) motif library due to libtool being confused, pulling in one motif library directly and another one indirectly, etc., etc., etc. There is a nice analysis somewhere here, again please try and search bugzilla for more information.
(In reply to comment #2) Confirmed, I have seen the exact same ComboBox behaviour some time ago, in Xpdf, and in other programs as well. The important thing is, you have to emerge Openmotif and Lesstif in a specific order and repeat from scratch if said order is disturbed during an update. DISCLAIMER: The following is not supposed to be an advertisement, just saying that neither Lesstif, Openmotif, nor Xpdf are at fault. If you're in France, Germany or Switzerland, there's a shop that offers commercial Motif support on Gentoo. Maybe a little pricey for home use, but they're offering a portage overlay with Openmotif, Lesstif, and all Motif apps that used to be, are, and will be in the future, in Gentoo, incl. security backports and guaranteed availability for 1, 2, 5, or more years. From what I've seen they're using a USE flag based Motif selection similar to what used to be in regular portage some years ago plus some advanced portage technology for better interoperability with non-gentoo binary-only stuff. Seeing that the above method works so well here, perhaps Gentoo should do the same?
I have unmerged openmotif, lesstif and even motif-config. Then, I emerged openmotif and xpdf again (I didn't unmerge xpdf before, that's right, but I don't think it matters). The bug is there again! Can't be the solution.
Created attachment 105118 [details] xpdf.png For comparison, here's a shot of what it's supposed to look like with unbroken openmotif. Looks identical both with stock xpdf-3.01 and Gentoo's 3.01-r8 (which for some reason reports itself as 3.0 and seems to contain lots of ubuntuisms).
Is your DPI for X server sane? $ xdpyinfo |grep resolution I cannot confirm this bug with openmotif-2.2.3-r9 and xpdf-3.01-r8. All menus work as expected. What versions are you using?
xdpyinfo |grep resolution delivers resolution: 81x86 dots per inch xpdf version: 3.01-r9 openmotif version: 2.2.3-r9:2.2 motif-config version: 0.9 (not the latest one, but stable) you should have my emerge --info As I said, I performed an emerge --unmerge openmotif lesstif motif-config xpdf emerge xpdf And the bug came again, since I used xpdf with lesstif
Nothing to do with DPI. The problem is, due to mismatches between header version, compile time library version and runtime library version caused by this whole motif-config mess, when xpdf tries to set some unrelated resource, it really sets the visible item count on the combobox widget to some random value. (which, btw, gentoo's motif maintainer is fully aware of, but his reasoning for closing any bug reports is "there haven't been any complaints". Next time it's reported, "nobody else complained about it" ==> "everything is A-OK" ==> "FIXED", and so on..ad nauseam) And that is only one of many things that can (and will) go wrong. Trust me on this. We've been through this problem so many times on various client sites, I'm very surprised that this is the first time somebody reported this particular symptom. If you really need motif and lesstif at the same time (a lot of people do), currently the best way is to grab ebuilds from the mid-2004 era and add any later patches (minus the bogus ones) yourself, but be sure to select one that is not affected by bug #91951. That's what we do here.
I didn't want to use anything in parallel, I just wanted to use xpdf with openmotif, so that it works correctly; nothing more. But I already switched to kpdf. It's not as obsolute as that xpdf motif-frontend, has a much better memory management and things look good and work correctly, so I am perfectly happy. Working with old and obsolete software is like taking care for old, senile people and I'm really fed up with it.
(In reply to comment #2) > The real cause for a lot of motif related problems is that motif-config > is fundamentally broken. Right on spot... *** This bug has been marked as a duplicate of bug 147067 ***