Gentoo Websites Logo
Go to: Gentoo Home Documentation Forums Lists Bugs Planet Store Wiki Get Gentoo!
Bug 106144 - app-crypt/seahorse-0.7.9 build fails with gnome 2.12 (gedit problem)
Summary: app-crypt/seahorse-0.7.9 build fails with gnome 2.12 (gedit problem)
Status: RESOLVED FIXED
Alias: None
Product: Gentoo Linux
Classification: Unclassified
Component: [OLD] GNOME (show other bugs)
Hardware: All Linux
: High normal (vote)
Assignee: Gentoo Linux Gnome Desktop Team
URL:
Whiteboard:
Keywords:
: 108195 (view as bug list)
Depends on:
Blocks:
 
Reported: 2005-09-15 20:51 UTC by Surakshan Mendis
Modified: 2005-10-06 02:26 UTC (History)
1 user (show)

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


Attachments
seahorse 0.7.9 config log (config.log,45.32 KB, text/plain)
2005-09-15 20:53 UTC, Surakshan Mendis
Details

Note You need to log in before you can comment on or make changes to this bug.
Description Surakshan Mendis 2005-09-15 20:51:21 UTC
Since gnome 2.12 in in portage I'm unmasked it using package.keywords and
package.unmask.

app-crypt/seahorse-0.7.9 which I believe is needed for Evolution* to do inline
PGP fails with the following error (below)



Reproducible: Always
Steps to Reproduce:
1. Install Gnome 2.12 (i guess gedit 2.12.0 is the cause)
2. emerge seahorse-0.7.9 (which is ~arch)
3.

Actual Results:  
enabling key server support
enabling gedit plugin...
checking for supported versions of gedit...
checking for gedit-2.10 >= 2.9.0... checking for gedit-2.8 >= 2.8.0... checking
for gedit-2.6 >= 2.6.0... Package gedit-2.6 was not found in the pkg-config sear
ch path. Perhaps you should add the directory containing `gedit-2.6.pc' to the P
KG_CONFIG_PATH environment variable No package 'gedit-2.6' found
configure: error: Library requirements (gedit-2.6 >= 2.6.0) not met; consider ad
justing the PKG_CONFIG_PATH environment variable if your libraries are in a nons
tandard prefix so pkg-config can find them.

!!! Please attach the config.log to your bug report:
!!! /var/tmp/portage/seahorse-0.7.9/work/seahorse-0.7.9/config.log

!!! ERROR: app-crypt/seahorse-0.7.9 failed.
!!! Function econf, Line 485, Exitcode 0
!!! econf failed
!!! If you need support, post the topmost build error, NOT this status message.


Expected Results:  
seahorse to compile correctly,
hence allowing evolution to do inline PGP stuff (evolution complains that it
couldn't try to the seahorse socket (because seahorse DNE).


synapse sura # emerge info
Portage 2.0.51.22-r2 (default-linux/x86/2005.0, gcc-3.4.4, glibc-2.3.5-r1,
2.6.13 i686)
=================================================================
System uname: 2.6.13 i686 Intel(R) Pentium(R) 4 CPU 2.66GHz
Gentoo Base System version 1.6.13
distcc 2.18.3 i686-pc-linux-gnu (protocols 1 and 2) (default port 3632) [enabled]
ccache version 2.3 [enabled]
dev-lang/python:     2.3.5-r2, 2.4.1-r1
sys-apps/sandbox:    1.2.12
sys-devel/autoconf:  2.13, 2.59-r6
sys-devel/automake:  1.4_p6, 1.5, 1.6.3, 1.7.9-r1, 1.8.5-r3, 1.9.6
sys-devel/binutils:  2.15.92.0.2-r10
sys-devel/libtool:   1.5.18-r1
virtual/os-headers:  2.6.8.1-r1, 2.6.11-r2
ACCEPT_KEYWORDS="x86"
AUTOCLEAN="yes"
CBUILD="i686-pc-linux-gnu"
CFLAGS="-O2 -march=pentium4 -funroll-loops -fprefetch-loop-arrays -pipe"
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.4/env
/usr/kde/3.4/share/config /usr/kde/3.4/shutdown /usr/kde/3/share/config
/usr/lib/X11/xkb /usr/lib/mozilla/defaults/pref /usr/share/config
/var/qmail/control"
CONFIG_PROTECT_MASK="/etc/gconf /etc/splash /etc/terminfo /etc/env.d"
CXXFLAGS="-O2 -march=pentium4 -funroll-loops -fprefetch-loop-arrays -pipe"
DISTDIR="/usr/portage/distfiles"
FEATURES="autoconfig ccache distcc distlocks sandbox sfperms strict"
GENTOO_MIRRORS="http://mirror.pacific.net.au/gentoo/"
MAKEOPTS="-j6"
PKGDIR="/usr/portage/packages"
PORTAGE_TMPDIR="/var/tmp"
PORTDIR="/usr/portage"
PORTDIR_OVERLAY="/usr/local/portage"
SYNC="rsync://rsync.gentoo.org/gentoo-portage"
USE="x86 X acl alsa apm avi berkdb bitmap-fonts bonobo cdr crypt cups curl eds
emboss encode esd flac foomaticdb fortran gd gdbm gif gnome gpm gstreamer gtk
gtk2 guile hal imagemagick imlib ipv6 java jpeg junit libg++ libwww lirc mad
mikmod motif mozilla mp3 mpeg mppe-mppc mysql ncurses nls nptl ogg oggvorbis
opengl oss pam pdflib perl pic png ppds python quicktime quotas readline samba
sdl slang spell sqlite ssl svga tcltk tcpd theora tiff truetype truetype-fonts
type1-fonts vorbis xml xml2 xv zlib userland_GNU kernel_linux elibc_glibc"
Unset:  ASFLAGS, CTARGET, LANG, LC_ALL, LDFLAGS, LINGUAS
Comment 1 Surakshan Mendis 2005-09-15 20:53:26 UTC
Created attachment 68554 [details]
seahorse 0.7.9 config log

seahorse 0.7.9 config log
Comment 2 Natanael Copa 2005-09-15 23:41:24 UTC
Even more info.

In capplets/background/gnome-wp-item.c at line 221 there is an:

if (pixbuf != NULL) { 
   ...
}

Right after that block there is a:

pw = gdk_pixbuf_get_width (pixbuf);
ph = gdk_pixbuf_get_height (pixbuf);

Those generates the warnings, since pixbuf obviously is NULL. Looks like they
handle that. But the "g_object_unref (pixbuf)" does not it makes the capplet
segfault.

Now, I wonder: why is pixbuf NULL at all? Should there be a

if (pixbuf == NULL) return;

statement somewhere before?

I have no experience of gtk/gnome programming, but it looks like there is a
missing check if the pixbuf is created sucessully or not somwhere.

I also suspect that this only happens to a certain types of files and not all. 
Comment 3 Natanael Copa 2005-09-15 23:45:46 UTC
(In reply to comment #2)
> Even more info.

Oups... This was in the wrong bug... My comment is not related to this at all.
I'm sorry.
Comment 4 Daniel Gryniewicz (RETIRED) gentoo-dev 2005-09-16 12:12:35 UTC
Seahorse seems to require gedit 2.10, while gnome 2.12 has gedit 2.12.  Upstream
will need to update it to make it work with 2.12.
Comment 5 Mike Gardiner (RETIRED) gentoo-dev 2005-09-17 21:17:27 UTC
I've patched it and added to CVS.
Comment 6 Mike Gardiner (RETIRED) gentoo-dev 2005-10-06 02:26:52 UTC
*** Bug 108195 has been marked as a duplicate of this bug. ***