FS#47528 - [gjs] weird behavior with package from repo (fixed by package rebuild)

Attached to Project: Arch Linux
Opened by Norbert Pfeiler (npfeiler) - Friday, 25 December 2015, 19:37 GMT
Last edited by Jelle van der Waa (jelly) - Sunday, 06 January 2019, 15:39 GMT
Task Type Bug Report
Category Packages: Extra
Status Closed
Assigned To Jan de Groot (JGC)
Jan Alexander Steffens (heftig)
Architecture All
Severity Low
Priority Normal
Reported Version
Due in Version Undecided
Due Date Undecided
Percent Complete 100%
Votes 0
Private No


I reported an issue (https://bugzilla.gnome.org/show_bug.cgi?id=757382) which appears with recent releases of the gjs package (1.44.0-1 and 1.44.0-2).
The issue doesn’t occur if I build the package myself with default makepkg.conf. (it’s 79 KiB bigger than the one from the repositories then)
I can only reproduce this on one system, but I think this oddity should be investigated.
This task depends upon

Closed by  Jelle van der Waa (jelly)
Sunday, 06 January 2019, 15:39 GMT
Reason for closing:  Deferred
Additional comments about closing:  can't reproduce, re-open if it's reproducible.
Comment by Doug Newgard (Scimmia) - Saturday, 26 December 2015, 14:22 GMT
Does it still work if you rebuild in a clean chroot?
Comment by Norbert Pfeiler (npfeiler) - Sunday, 27 December 2015, 12:51 GMT
Good call.
The package files from a clean chroot are identical to the repo package.
I assume that this task can be closed then.

Regardless I would like to get some hints on the following:

Trying to find the reason why “my” package is different, I remembered that I can’t use gnome without https://aur.archlinux.org/packages/mutter-catalyst because the oss driver doesn’t work always.
The issue only occurs if I build mutter(not only mutter-catalyst) with -O3 and use gjs 1.44.* from a clean chroot/the repos.
If I build gjs myself – regardless of compile settings – or downgrade to 1.43.*, everything seems to work even with mutter built with -O3.
Why is this?
And also, why are “my” packages with a default makepkg.conf bigger than from a clean chroot?
How can I proceed from here?
Comment by Jan Alexander Steffens (heftig) - Wednesday, 06 January 2016, 16:15 GMT
Is hardening-wrapper installed? It should not be.
Comment by Norbert Pfeiler (npfeiler) - Wednesday, 06 January 2016, 22:33 GMT
It’s not.
I could reproduce the issue with mutter built with -O3 on every system I tried it on (3 so far).