[Lunar Linux 0000379]: gdk-pixbuf will not build

[noreply at bugs.lunar-linux.org]

A BUGNOTE has been added to this bug.
=======================================================================
http://bugs.lunar-linux.org/view_bug_page.php?f_id=0000379
=======================================================================
Reporter:                   nhudson
Handler:                    niki
=======================================================================
Project:                    Lunar Linux
Bug ID:                     0000379
Category:                   moonbase
Reproducibility:            always
Severity:                   major
Priority:                   none
Status:                     assigned
=======================================================================
Date Submitted:             2003-09-27 14:06 GMT
Last Modified:              2003-11-04 20:53 GMT
=======================================================================
Summary:                    gdk-pixbuf will not build
Description: 
Now I know I could prolly fix this but given I dont have tim atm I will
remort it as a bug for now to see if anyone has any ideas on why this
happens.  gdk-pixbuf will not build due to it cannot open up the display.

mv -f .libs/gdk-pixbuf-scan.lo gdk-pixbuf-scan.lo
ccache gcc -o .libs/gdk-pixbuf-scan gdk-pixbuf-scan.o -rdynamic 
../gdk-pixbuf/.libs/libgdk_pixbuf.so -L/usr/lib -ldl -ldl -L/usr/X11R6/lib
-ldl -ldl -ldl -ldl -lXi -lXext -lX11 -lm
../gdk-pixbuf/.libs/libgnomecanvaspixbuf.so -lm -lm -lm -lm -lm -ldl
-lXext -ldl -lXi -lXext -lX11 -lm -ldl -lXi -lXext -lX11 -lm -ldl -ldl
-lXi -lXext -lX11 -lm -ldl -lXi -lXext -lX11 -lm -ldl -lXi -lXext -lX11
-lm -ldl -ldl -lXi -lXext -lX11 -lm -lm -lm -ldl -lXext -ldl -lXi -lXext
-lX11 -lm -ldl -lXi -lXext -lX11 -lm -ldl -ldl -lXi -lXext -lX11 -lm -lm
-lm -lm -lm -lm /usr/lib/libgnomeui.so -lm -lm -lm -lm -lm -ldl -lXext
-ldl -lXi -lXext -lX11 -lm -ldl -lXi -lXext -lX11 -lm -ldl -ldl -lXi
-lXext -lX11 -lm -ldl -lXi -lXext -lX11 -lm -ldl -lXi -lXext -lX11 -lm
-ldl -ldl -lXi -lXext -lX11 -lm -lm /usr/lib/libart_lgpl.so -lm
/usr/lib/libgdk_imlib.so -ldl -lXext -lSM -lICE /usr/lib/libgtk.so -ldl
-lXi -lXext -lX11 -lm /usr/lib/libgdk.so -ldl -lXi -lXext -lX11 -lm
/usr/lib/libgmodule.so -ldl -ldl -lXi -lXext -lX11 /usr/lib/libgnome.so
-lm -lm /usr/lib/libgnomesupport.so -lz -lm /usr/lib/libesd.so -lm
/usr/lib/libaudiofile.so -lm -lm -ldb-3 /usr/lib/libglib.so -lm
creating gdk-pixbuf-scan
 
Gtk-WARNING **: cannot open display:
Scan failed
make[2]: *** [scan-build.stamp] Error 25
make[2]: Leaving directory `/usr/src/gdk-pixbuf-0.22.0/doc'
make[1]: *** [all-recursive] Error 1
make[1]: Leaving directory `/usr/src/gdk-pixbuf-0.22.0'
make: *** [all-recursive-am] Error 2
Creating /var/log/lunar/compile/gdk-pixbuf-0.22.0.bz2
! Problem detected during BUILD


This is solved one way by running lin gdk-pixbuf as root with regular "su"
and not "su -".  I guess if su to root with "su -" like the shell says it
will not open the display.  If you su to root with "su" or "su root" it
will work fine but lin coughs up a "WARNING" message that says 

WARNING: You are not running a fully initialized root shell, consider
running a proper root shell with 'su -'

SO if you run it as "su -" gdk-pixbuf will not compile.  Anyone have any
sugesstions on how this can be solved.
=======================================================================

-----------------------------------------------------------------------
 niki - 2003-09-27 14:16 GMT 
-----------------------------------------------------------------------
Do as the users that ownes the X session "xhost +localhost" then you can do
a "DISPLAY=:0.0 lin -c gdk-pixbuf" that is how i normaly do it. With that
you can use "su -".

-----------------------------------------------------------------------
 nhudson - 2003-11-04 20:53 GMT 
-----------------------------------------------------------------------
I think we can call this resolved?  What do you think niki?  If I do what
you suggested then all is fine but is there a way we can enable this in
the module so that any normal user wont freak when this happens?