Gentoo Websites Logo
Go to: Gentoo Home Documentation Forums Lists Bugs Planet Store Wiki Get Gentoo!
Bug 493832 - net-libs/webkit-gtk-2.0.4 - /usr/bin/g-ir-scanner loops infinitely in WebKit-3.0.gir make target
Summary: net-libs/webkit-gtk-2.0.4 - /usr/bin/g-ir-scanner loops infinitely in WebKit-...
Status: RESOLVED FIXED
Alias: None
Product: Gentoo Linux
Classification: Unclassified
Component: [OLD] GNOME (show other bugs)
Hardware: AMD64 Linux
: Normal normal (vote)
Assignee: Gentoo Linux Gnome Desktop Team
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2013-12-10 11:57 UTC by Bernd Waibel
Modified: 2014-01-09 09:58 UTC (History)
0 users

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


Attachments
emerge --info (emerge-info.txt,6.25 KB, text/plain)
2013-12-10 11:58 UTC, Bernd Waibel
Details
tail of build.log (webkit-gtk-build-tail.log,22.40 KB, text/plain)
2013-12-10 12:21 UTC, Bernd Waibel
Details
webkit-gtk-2.0.4:20131209-081823.log.xz (webkit-gtk-2.0.4:20131209-081823.log.xz,299.90 KB, application/x-xz)
2013-12-10 17:22 UTC, Bernd Waibel
Details

Note You need to log in before you can comment on or make changes to this bug.
Description Bernd Waibel 2013-12-10 11:57:46 UTC
When compiling webkit-gtk-2.0.4 the compile process at one time catches the assertion

(process:32407): GLib-GObject-CRITICAL **: g_object_class_install_property: assertion `class->set_property != NULL' failed

but instead of breaking the build, it seems to run into an infinite loop and runs forever. I tried several times using emerge and ebuild, with the same results and CTRL-C'ed the process after 12+ hours running.

I was first thinking, it's the same bug as in Bug #483610 and posted there, but someone there told me, that it's a different bug and I should post a new report. The bug also looks similar to Bug #493014 and Bug #493136 but they are marked as duplicates of #483610 so now I'm writing this new report. I'll attach the emerge --info and a compressed build log (beeing 64MB in size uncompressed)

Reproducible: Always

Steps to Reproduce:
1. eselect profile set default/linux/amd64/13.0/desktop/gnome/systemd
2. emerge -DaquvN @world
3.
Actual Results:  
build of webkit-gtk-2.0.4 hangs

Expected Results:  
build of webkit-gtk-2.0.4 succeeds and update can continue
Comment 1 Bernd Waibel 2013-12-10 11:58:47 UTC
Created attachment 365040 [details]
emerge --info
Comment 2 Jeroen Roovers (RETIRED) gentoo-dev 2013-12-10 12:15:12 UTC
Please attach the entire build log to this bug report.
Comment 3 Bernd Waibel 2013-12-10 12:21:07 UTC
Created attachment 365042 [details]
tail of build.log

Only the last 185+ lines being the relevant one, as the compressed build.log won't currently upload. I'll come back and try again later, once I'm back home.
Comment 4 Bernd Waibel 2013-12-10 17:22:00 UTC
Created attachment 365060 [details]
webkit-gtk-2.0.4:20131209-081823.log.xz
Comment 5 Pacho Ramos gentoo-dev 2013-12-11 21:19:20 UTC
Do you have nvidia drivers? Does setting "eselect opengl" to x11 during building help?
Comment 6 Bernd Waibel 2013-12-11 22:34:13 UTC
Yes, I do use nvidia-drivers. I'm currently trying to build, coming back with more information later.
Comment 7 Bernd Waibel 2013-12-12 07:08:07 UTC
The package successfully built, when using xorg-x11 opengl drivers!

Does anyone know what's the cause of the problem here with the nvidia-drivers?
Comment 8 Pacho Ramos gentoo-dev 2013-12-12 18:25:27 UTC
This is a dupe of bug 463960, what nvidia-drivers version are you using?
Comment 9 Bernd Waibel 2013-12-12 21:26:59 UTC
I am using nvidia-drivers-331.20
Comment 10 Pacho Ramos gentoo-dev 2013-12-12 21:30:39 UTC

*** This bug has been marked as a duplicate of bug 463960 ***
Comment 11 Pacho Ramos gentoo-dev 2013-12-12 21:35:14 UTC
Probably:
https://bugs.gentoo.org/show_bug.cgi?id=463960#c67

will help you
Comment 12 Bernd Waibel 2013-12-12 22:08:08 UTC
I will try this out, once the update is finished. Currently there's an additional fail with libreoffice (which I can ignore for some time, if the rest of the packages are updating).
Comment 13 Juanlu Pérez 2014-01-09 09:58:03 UTC
I'm still getting this bug with nvidia-drivers-304.117