I have been hit by a bug that I don't know how to go about it. First my login manager slim is not showing any "username / password" text upon log in; now Openoffice-bin has no menu text on top. How to go about this bug? I have four systems two x86 and two amd64 one x86 and one amd64 are effected by this bug, two other system working normally :-/ Reproducible: Always Portage 2.2.1 (default/linux/amd64/13.0/desktop, gcc-4.5.4, glibc-2.15-r3, 3.1.6-gentoo x86_64) ================================================================= System uname: Linux-3.1.6-gentoo-x86_64-AMD_FX-tm-8150_Eight-Core_Processor-with-gentoo-2.2 KiB Mem: 8094600 total, 4231356 free KiB Swap: 8757244 total, 8757244 free Timestamp of tree: Mon, 14 Oct 2013 16:00:01 +0000 ld GNU ld (GNU Binutils) 2.23.1 app-shells/bash: 4.2_p45 dev-java/java-config: 2.1.12-r1 dev-lang/python: 2.7.5-r2, 3.1.5-r1, 3.2.5-r2 dev-util/cmake: 2.8.10.2-r2 dev-util/pkgconfig: 0.28 sys-apps/baselayout: 2.2 sys-apps/openrc: 0.11.8 sys-apps/sandbox: 2.6-r1 sys-devel/autoconf: 2.13, 2.69 sys-devel/automake: 1.11.6, 1.13.4 sys-devel/binutils: 2.23.1 sys-devel/gcc: 4.5.4, 4.7.3-r1 sys-devel/gcc-config: 1.7.3 sys-devel/libtool: 2.4.2 sys-devel/make: 3.82-r4 sys-kernel/linux-headers: 3.9 (virtual/os-headers) sys-libs/glibc: 2.15-r3 Repositories:
"First"? Does that mean that both slim and openoffice-bin are affected by missing text on the same computer? Is there a bug report for slim? If so, you may be missing one font. Compare the output of "fc-list" on systems where you see this problem with the output where there is no problem.
(In reply to Chí-Thanh Christopher Nguyễn from comment #1) > "First"? Does that mean that both slim and openoffice-bin are affected by > missing text on the same computer? Is there a bug report for slim? > > If so, you may be missing one font. Compare the output of "fc-list" on > systems where you see this problem with the output where there is no problem. Thanks for answering. Yes, my two systems are effected in the same way both slim and openoffice-bin are missing text menu. I'll try "fc-list" to compare if anything is missing and report back, good suggestion.
(In reply to Chí-Thanh Christopher Nguyễn from comment #1) > "First"? Does that mean that both slim and openoffice-bin are affected by > missing text on the same computer? Is there a bug report for slim? > > If so, you may be missing one font. Compare the output of "fc-list" on > systems where you see this problem with the output where there is no problem. I've compared "fc-list" of two x86 systems system called "atom" - not effected system called "syscon2" - effected by not showing text the menu. All fonts that are in "atom" are present in "syscon2" so I don't think this is problem with the fonts.
Does openoffice print any errors when you run it from a terminal?
(In reply to Chí-Thanh Christopher Nguyễn from comment #4) > Does openoffice print any errors when you run it from a terminal? No, no errors. From terminal I run "oowriter" it starts, without any "text menu" but no errors are reported when I exit. I'm running right now emerge -vae openoffice-bin :-( (logged over ssh) It is a pain about 300 packages to be emerged; every about 10-packages I run: /etc/inid.d/xdm restart to see if slim login menu will show text "username / passowrd"; this ways I might be able to narrow it to a package that is responsible for this behaviour. I think "slim" and "openoffice-bin" are effected by the same bug.
If it is not a missing font, then the issue could be related to the graphics driver.
(In reply to Chí-Thanh Christopher Nguyễn from comment #6) > If it is not a missing font, then the issue could be related to the graphics > driver. Good suggestion. Running emerge -1av $(qlist -IC x11-drivers) These are the packages that would be merged, in order: Calculating dependencies... done! [ebuild R ] x11-drivers/nvidia-drivers-310.51 USE="X acpi (multilib) tools -pax_kernel" 0 kB [ebuild R ] x11-drivers/xf86-input-evdev-2.8.1 0 kB [ebuild R ] x11-drivers/xf86-video-nouveau-1.0.9 0 kB How to find out which driver was installed previously? Digging via emerge.log?
"qlop -lu" will show you the merge history. Using the nouveau driver instead of nvidia would be something you could try too.
(In reply to Chí-Thanh Christopher Nguyễn from comment #8) > "qlop -lu" will show you the merge history. > Using the nouveau driver instead of nvidia would be something you could try > too. I've downgraded to: x11-drivers/xf86-video-nouveau-1.0.4 x11-drivers/xf86-input-evdev-2.7.3 LogOut/IN but still the same problem. I think I'm using nouveau: cat /etc/X11/xorg.conf # uncomment when the card gets IN Section "Device" Identifier "nouveau" Driver "nouveau" EndSection
(In reply to Chí-Thanh Christopher Nguyễn from comment #8) > "qlop -lu" will show you the merge history. > Using the nouveau driver instead of nvidia would be something you could try > too. I'm trying to downgrade all x11-drivers that were updated on my x86 system but I'm getting errors: emerge -uDNav world These are the packages that would be merged, in order: Calculating dependencies... done! [ebuild UD ] x11-drivers/xf86-video-fbdev-0.4.3 [0.4.4] 0 kB [ebuild UD ] x11-drivers/xf86-video-vesa-2.3.2 [2.3.3] 0 kB [ebuild UD ] x11-drivers/xf86-video-nv-2.1.20 [2.1.20-r1] 0 kB [ebuild UD ] x11-drivers/xf86-input-keyboard-1.6.2 [1.7.0] 0 kB [ebuild UD ] x11-drivers/xf86-input-mouse-1.8.1 [1.9.0] 0 kB Emerging (1 of 5) x11-drivers/xf86-video-fbdev-0.4.3 (it is listed as stable) ... >>> Source configured. >>> Compiling source in /var/tmp/portage/x11-drivers/xf86-video-fbdev-0.4.3/work/xf86-video-fbdev-0.4.3 ... >>> Working in BUILD_DIR: "/var/tmp/portage/x11-drivers/xf86-video-fbdev-0.4.3/work/xf86-video-fbdev-0.4.3_build" make -j1 make all-recursive make[1]: Entering directory `/var/tmp/portage/x11-drivers/xf86-video-fbdev-0.4.3/work/xf86-video-fbdev-0.4.3_build' Making all in src make[2]: Entering directory `/var/tmp/portage/x11-drivers/xf86-video-fbdev-0.4.3/work/xf86-video-fbdev-0.4.3_build/src' CC fbdev.lo /var/tmp/portage/x11-drivers/xf86-video-fbdev-0.4.3/work/xf86-video-fbdev-0.4.3/src/fbdev.c:17:22: fatal error: mibstore.h: No such file or directory compilation terminated. make[2]: *** [fbdev.lo] Error 1
It makes only sense to downgrade the drivers which are actually in use according to Xorg.0.log If nouveau gives you rendering errors, you can try xf86-video-modesetting. xf86-video-fbdev-0.4.3 driver is incompatible with xorg-server-1.14
(In reply to Chí-Thanh Christopher Nguyễn from comment #11) > It makes only sense to downgrade the drivers which are actually in use > according to Xorg.0.log > If nouveau gives you rendering errors, you can try xf86-video-modesetting. > xf86-video-fbdev-0.4.3 driver is incompatible with xorg-server-1.14 You gave me an idea. I'm downgrading to xorg-server-1.13.4 and see what will happen
(In reply to Chí-Thanh Christopher Nguyễn from comment #11) > It makes only sense to downgrade the drivers which are actually in use > according to Xorg.0.log > If nouveau gives you rendering errors, you can try xf86-video-modesetting. > xf86-video-fbdev-0.4.3 driver is incompatible with xorg-server-1.14 That was it! SOLVED It seems to me xorg-server-1.14 is not compatible with some of the video cards. Few days ago xorg-server-1.14-r2 was even stable on amd64 but actually neither xorg-server-1.14-r2 nor 1.14 working correctly with video drivers. I've downgraded both x86 and amd64 to xorg-server-1.13.4-r1 and they both work correctly now.
*** Bug 488612 has been marked as a duplicate of this bug. ***
*** Bug 488816 has been marked as a duplicate of this bug. ***
*** Bug 495280 has been marked as a duplicate of this bug. ***
