FS#46621 - [workrave] Segfault after updating gtkmm3 to 3.18.0-1

Attached to Project: Community Packages
Opened by Pieter Frenssen (pfrenssen) - Friday, 09 October 2015, 09:24 GMT
Last edited by Doug Newgard (Scimmia) - Wednesday, 28 October 2015, 13:48 GMT
Task Type Bug Report
Category Packages
Status Closed
Assigned To Sergej Pupykin (sergej)
Architecture All
Severity Low
Priority Normal
Reported Version
Due in Version Undecided
Due Date Undecided
Percent Complete 100%
Votes 6
Private No

Details

Description:

Workrave segfaults when started. This is caused by the latest 3.18.0-1 update of gtkmm3. I had to roll back to gtkmm3-3.16.0-1.

I can replicate this on two machines.
This task depends upon

Closed by  Doug Newgard (Scimmia)
Wednesday, 28 October 2015, 13:48 GMT
Reason for closing:  Fixed
Additional comments about closing:  workrave 1.10.8-1
Comment by Doug Newgard (Scimmia) - Friday, 09 October 2015, 13:19 GMT
Does using the default Adwaita theme change anything?

Possible duplicate of  FS#46614 
Comment by Pieter Frenssen (pfrenssen) - Friday, 09 October 2015, 22:33 GMT
I think I am using that, I'm using the vanilla installation of GTK, have never customized it in any way. I tried to force select the Adwaita theme but the segfault still occurs:

$ GTK_THEME=Adwaita workrave
Segmentation fault (core dumped)
Comment by Andrew Chen (andrewchen) - Friday, 16 October 2015, 06:19 GMT
This issue is because workrave is not rebuilt with gtk 3.18.

However, workrave doesn't build with gtk 3.18 because c++11 is not enabled.
I've filed this bug upstream as http://issues.workrave.org/show_bug.cgi?id=1219.
Nevertheless, we could just enable c++11 ourselves in the meantime:

diff --git a/trunk/PKGBUILD b/trunk/PKGBUILD
index fc37282..f908757 100644
--- a/trunk/PKGBUILD
+++ b/trunk/PKGBUILD
@@ -4,7 +4,7 @@

pkgname=workrave
pkgver=1.10.6
-pkgrel=2
+pkgrel=3
pkgdesc="a tool to help RSI"
arch=('i686' 'x86_64')
license=('GPL2')
@@ -20,7 +20,7 @@ build() {
cd $srcdir/workrave-${pkgver//./_}
export PYTHON=python2
./autogen.sh
- ./configure --prefix=/usr --enable-dbus --sysconfdir=/etc --libexecdir=/usr/lib/workrave \
+ CXXFLAGS+=' --std=c++11' ./configure --prefix=/usr --enable-dbus --sysconfdir=/etc --libexecdir=/usr/lib/workrave \
--disable-pulse
make
}
Comment by Pieter Frenssen (pfrenssen) - Monday, 19 October 2015, 09:22 GMT
Thanks! I tried the patch but I'm getting a compile error, seem like I'm missing a package. I have all the make dependencies installed, and libxtst 1.2.2-1.

checking for shmat in -lipc... no
checking for IceConnectionNumber in -lICE... no
checking for XRecordEnableContext in -lXtst... no
configure: error: X RECORD extension headers files required on Unix platform
==> ERROR: A failure occurred in build().
Aborting...
Comment by Javier Tiá (jetm) - Monday, 19 October 2015, 22:20 GMT
I submitted a pull request to workrave upstream GitHub repo:

https://github.com/rcaelers/workrave/pull/50
Comment by Andrew Chen (andrewchen) - Tuesday, 20 October 2015, 09:40 GMT
Pieter Frenssen: I cannot reproduce the compile error, even when building in a clean chroot (using extra-x86_64-build from devtools). Can you try to build in a clean chroot if you are still having the problem.
Comment by Pieter Frenssen (pfrenssen) - Tuesday, 20 October 2015, 12:13 GMT
I tried building in a chrooted environment with extra-x86_64-build, but getting the same error:

checking for XRecordEnableContext in -lXtst... no
configure: error: X RECORD extension headers files required on Unix platform
==> ERROR: A failure occurred in build().
Aborting...
==> ERROR: Build failed, check /var/lib/archbuild/extra-x86_64/pieter/build

Nevermind, I can work around it for the moment by downgrading gtkmm3. Thanks for the assistance.
Comment by Javier Tiá (jetm) - Tuesday, 20 October 2015, 15:22 GMT
My pull request
https://github.com/rcaelers/workrave/pull/50 was merged to workrave upstream repo.

I created a local workrave package with that change and workrave doesn't crash anymore.

Loading...