After an evaluation, GNOME has moved from Bugzilla to GitLab. Learn more about GitLab.
No new issues can be reported in GNOME Bugzilla anymore.
To report an issue in a GNOME project, go to GNOME GitLab.
Do not go to GNOME Gitlab for: Bluefish, Doxygen, GnuCash, GStreamer, java-gnome, LDTP, NetworkManager, Tomboy.
Bug 774354 - Segmentation fault on starting latest jhbuild
Segmentation fault on starting latest jhbuild
Status: RESOLVED WONTFIX
Product: gnome-music
Classification: Applications
Component: general
unspecified
Other Linux
: Normal normal
: ---
Assigned To: gnome-music-maint
gnome-music-maint
Depends on:
Blocks:
 
 
Reported: 2016-11-13 10:43 UTC by Rithvik Patibandla
Modified: 2016-11-17 14:48 UTC
See Also:
GNOME target: ---
GNOME version: ---


Attachments
Output of "jhbuild run gnome-music -d" (25.98 KB, text/plain)
2016-11-13 10:43 UTC, Rithvik Patibandla
Details

Description Rithvik Patibandla 2016-11-13 10:43:33 UTC
Created attachment 339743 [details]
Output of "jhbuild run gnome-music -d"

I built gnome-music using jhbuild and when I try to run it, it is showing a segmentation fault. This behavior is observed in Ubuntu-GNOME 16.04.1 and fedora 24(VM). The output of "jhbuild run gnome-music -d" is attached.
Comment 1 Marinus Schraal 2016-11-13 10:57:59 UTC
What is your pygi version? Is it consistently crashing?

It shouldn't just segfault just like that. Please provide a backtrace of the segfault (with debugging info)
Comment 2 Rithvik Patibandla 2016-11-13 11:29:47 UTC
python-gi                                   3.20.0-0ubuntu1
python-gi-cairo                             3.20.0-0ubuntu1
python-gnome2                               2.28.1+dfsg-1.1
python-gobject                              3.20.0-0ubuntu1
python-gobject-2                            2.28.6-12ubuntu1
python-gtk2                                 2.24.0-4ubuntu1
python3-gi                                  3.20.0-0ubuntu1
python3-gi-cairo                            3.20.0-0ubuntu1

I don't know how to backtrace it
Comment 3 Marinus Schraal 2016-11-13 13:34:58 UTC
(In reply to Rithvik Patibandla from comment #2)
> I don't know how to backtrace it

https://wiki.gnome.org/action/show/Community/GettingInTouch/Bugzilla/GettingTraces
Comment 4 Marinus Schraal 2016-11-13 13:42:01 UTC
Are you btw jhbuilding with the 3.22 moduleset? If not: I don't think the moving target that is current gtk+ unstable is something we need to work on right now.
Comment 5 ppalacios992 2016-11-15 16:18:07 UTC
I've got the same problem here. Setting moduleset into ~/.config/jhbuildrc as bellow and rebuilding everything solved the problem for me:

moduleset = 'gnome-apps-3.22'
Comment 6 Marinus Schraal 2016-11-15 18:04:16 UTC
gtk+ is too much in limbo for the move to 4 to be reliable build target.

jhbuild against the stable release set
Comment 7 Rithvik Patibandla 2016-11-17 14:48:34 UTC
3.22 module set worked for me in Ubuntu GNOME 16.04