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)
Steps to Reproduce:
1. eselect profile set default/linux/amd64/13.0/desktop/gnome/systemd
2. emerge -DaquvN @world
build of webkit-gtk-2.0.4 hangs
build of webkit-gtk-2.0.4 succeeds and update can continue
Created attachment 365040 [details]
Please attach the entire build log to this bug report.
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.
Created attachment 365060 [details]
Do you have nvidia drivers? Does setting "eselect opengl" to x11 during building help?
Yes, I do use nvidia-drivers. I'm currently trying to build, coming back with more information later.
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?
This is a dupe of bug 463960, what nvidia-drivers version are you using?
I am using nvidia-drivers-331.20
*** This bug has been marked as a duplicate of bug 463960 ***
will help you
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).
I'm still getting this bug with nvidia-drivers-304.117