gdk-pixbuf merge will start Xvfb to connect but will fail due to authentication problems if merged under X session from a su in a terminal. To correct the problem -ac flag needs to be passed to the Xvfb to disable authentication
*** Bug 1520 has been marked as a duplicate of this bug. ***
Here's the error message that I'm getting. gcc -march=i686 -O3 -pipe -I.. -I.. -I/usr/include/gnome-1.0 -DNEED_GNOMESUPPORT_H -I/usr/lib/gnome-libs/include -I/usr/include/gtk-1.2 -I/usr/include/glib-1.2 -I/usr/lib/glib/include -I/usr/X11R6/include -c gdk-pixbuf-scan.c -fPIC -DPIC -o .libs/gdk-pixbuf-scan.lo gcc -march=i686 -O3 -pipe -I.. -I.. -I/usr/include/gnome-1.0 -DNEED_GNOMESUPPORT_H -I/usr/lib/gnome-libs/include -I/usr/include/gtk-1.2 -I/usr/include/glib-1.2 -I/usr/lib/glib/include -I/usr/X11R6/include -c gdk-pixbuf-scan.c -o gdk-pixbuf-scan.o >/dev/null 2>&1 mv -f .libs/gdk-pixbuf-scan.lo gdk-pixbuf-scan.lo gcc -o .libs/gdk-pixbuf-scan gdk-pixbuf-scan.o -rdynamic ../gdk-pixbuf/.libs/libgdk_pixbuf.so ../gdk-pixbuf/.libs/libgnomecanvaspixbuf.so -L/usr/lib -L/usr/X11R6/lib /usr/lib/libgnomeui.so /usr/lib/libart_lgpl.so /usr/lib/libgdk_imlib.so -lSM -lICE /usr/lib/libgtk.so /usr/lib/libgdk.so /usr/lib/libgmodule.so -ldl -lXi -lXext -lX11 /usr/lib/libgnome.so /usr/lib/libgnomesupport.so /usr/lib/libesd.so /usr/lib/libasound.so /usr/lib/libaudiofile.so -ldb1 /usr/lib/libglib.so -lm creating gdk-pixbuf-scan Xlib: connection to ":8.0" refused by server Xlib: No protocol specified Gtk-WARNING **: cannot open display: :8 Scan failed make[2]: *** [scan-build.stamp] Error 1 make[2]: Leaving directory `/var/tmp/portage/gdk-pixbuf-0.16.0-r7/work/gdk-pixbuf-0.16.0/doc' make[1]: *** [all-recursive] Error 1 make[1]: Leaving directory `/var/tmp/portage/gdk-pixbuf-0.16.0-r7/work/gdk-pixbuf-0.16.0' make: *** [all-recursive-am] Error 2 !!! ERROR: The ebuild did not complete successfully. !!! Function src_compile, Line 21, Exitcode 2 !!! (no error message) ...done! >>> emerge media-libs/gdk-pixbuf-0.16.0-r7 to / !!! emerge aborting on /usr/portage/media-libs/gdk-pixbuf/gdk-pixbuf-0.16.0-r7.ebuild .
OK kids, we need some info here. First off, please make sure that any packages which have files in /etc/pam.d are up to date: emerge gentoolkit, then do this: qpkg -f /etc/pam.d that will give you a list of things which use this. Go ahead and remerge things, unless any of those have been remerged in the last few days. Don't forget to run etc-update so that your config files are updated as well. There have been some major PAM changes and this has been the cause.
*** Bug 1465 has been marked as a duplicate of this bug. ***
OK: boresch@lipari /usr/sbin/qpkg -f /etc/pam.d kde-base/kdebase-2.2.2-r2 * kde-base/kdebase-3.0-r1 * net-mail/postfix-1.1.6-r1 * net-misc/openssh-3.1_p1-r2 * net-print/cups-1.1.14-r2 * sys-apps/shadow-4.0.2-r4 * sys-libs/pam-0.75-r6 * sys-libs/pwdb-0.61-r3 * x11-base/xfree-4.2.0-r9 * BTW, gdk-pixbuf..-r8 built, but I ran emerge --update world from the text console without X. My feeling is that the solution was floating around on the gentoo-user/dev mailing lists. One should check whether DISPLAY is set, if yes use it. If not (i.e., build is running from the console, use Xvfb). My 2 cents...
Um, the Xvfb solution has been in use since the -r7 ebuild :P
This problem seems to be disappearing, so I am closing this bug.
Yeah, I know: This is what breaks things for me. When you compile from within X, i.e., when you already have a valid $DISPLAY, then you can start Xvfb, but you can't connect to it. That was in my orginal bug report. BTW, this affects evolution and some others as well. r8 installed, but I happened to install (emerge) from a pure text console in this case. As I said, there was a patch/suggestion floating around on gentoo-users/gentoo-dev which basically did the following: If "valid $DISPLAY" emake else "do Mandrake magic" I didn't try it, but is sounded reasonably since I never had this problem with any of the pri -r7 ebuilds -- I usually build from an xterminal.
Well, actually in console you should have experienced those errors as well. Nevertheless, make sure your PAM configs are up to date. Since you have just emerged the new xfree, make sure to overwrite the /etc/pam.d/xdm file with the new one and do the same for kdm. The issue was one of xauth in the PAM modules being handled badly by the previous configuration.
