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 785304 - open settings crashes the app
open settings crashes the app
Status: RESOLVED FIXED
Product: rhythmbox
Classification: Other
Component: User Interface
3.4.x
Other Linux
: High critical
: ---
Assigned To: RhythmBox Maintainers
RhythmBox Maintainers
Depends on:
Blocks:
 
 
Reported: 2017-07-23 08:43 UTC by luca
Modified: 2017-08-05 12:08 UTC
See Also:
GNOME target: ---
GNOME version: 3.23/3.24


Attachments
trace (69.70 KB, text/plain)
2017-07-24 15:11 UTC, luca
Details

Description luca 2017-07-23 08:43:36 UTC
hi there...

just upgraded to fedora workstation 26 and noticed that rhythmbox (3.4.1) crashes everytime i open settings...tried opening on terminal and it told me there is a segmentation fault error...what to do now considering that in fedora 25 was working well?
Comment 1 Jonathan Matthew 2017-07-23 12:18:33 UTC
Thanks for taking the time to report this.
Without a stack trace from the crash it's very hard to determine what caused it.
Can you get us a stack trace? Please see https://wiki.gnome.org/Community/GettingInTouch/Bugzilla/GettingTraces for more information on how to do so. When pasting a stack trace in this bug report, please reset the status of this bug report from NEEDINFO to its previous status. Thanks in advance!
Comment 2 luca 2017-07-23 14:46:28 UTC
hi there...well since i'm on fedora and the automatic bug reporting tool prompted me to fill a bug i even done that and it automatically generated everything...you could take a look on here...

https://bugzilla.redhat.com/show_bug.cgi?id=1474035

sorry if it may cause confusion
Comment 3 Jonathan Matthew 2017-07-24 09:42:50 UTC
Please attach (at least) the stack trace here.  Having some details in other bug trackers makes it difficult to search, and risks losing information due to changes on one side or the other.
Comment 4 luca 2017-07-24 15:11:48 UTC
Created attachment 356312 [details]
trace

that should be the trace... :)
Comment 5 luca 2017-07-29 07:52:34 UTC
no news on that?
Comment 6 Jonathan Matthew 2017-08-05 10:21:06 UTC
commit bc06095 should fix this
Comment 7 luca 2017-08-05 12:08:12 UTC
ok...thanks...will try it and report it... :)