Version-Release number of selected component: repsnapper-2.2.0-0.1.a2.fc18 Additional info: reporter: libreport-2.1.4 backtrace_rating: 3 cmdline: repsnapper _OR_U crash_function: gobj executable: /usr/bin/repsnapper kernel: 3.9.4-200.fc18.i686 runlevel: N 5 uid: 1000 Truncated backtrace: Thread no. 1 (4 frames) #0 gobj at ../pangomm/font.h:108 #1 Pango::Font::get_metrics at font.cc:40 #2 Render::on_realize at src/render.cpp:166 #3 ??
Created attachment 755439 [details] File: backtrace
Created attachment 755440 [details] File: cgroup
Created attachment 755441 [details] File: core_backtrace
Created attachment 755442 [details] File: dso_list
Created attachment 755443 [details] File: environ
Created attachment 755444 [details] File: limits
Created attachment 755445 [details] File: maps
Created attachment 755446 [details] File: open_fds
Created attachment 755447 [details] File: proc_pid_status
Created attachment 755448 [details] File: var_log_messages
Created attachment 755449 [details] File: xsession_errors
Hi, do you know what happened before the crash? Can you reproduce it? Thanks.
(In reply to Miro Hrončok from comment #12) > Hi, do you know what happened before the crash? Can you reproduce it? Thanks. Hi, no dont sorry all i did was open the app and then crashed
And if you open it again, does the crash reoccur?
(In reply to Miro Hrončok from comment #14) > And if you open it again, does the crash reoccur? yes i tried to open it few times but it crashed everutime
If you run repsnapper command from the terminal, is attachment 755449 [details] the only output?
yep thats all i see
I just tried to reproduce this bug and it seems it is not present in Xfce desktop, but is present in GNOME one. What I got in output (together with attachment 755449 [details]) is the message Can't load font sans 8. You got that one too, right?
yep i get the same error Parsing config from '/home/xxxx/.config/repsnapper/repsnapper.conf (repsnapper:14308): GdkGLExt-WARNING **: cannot find PangoXSubfont *** Can't load font sans 8 (repsnapper:14308): Gtk-CRITICAL **: IA__gtk_main_quit: assertion `main_loops != NULL' failed Segmentation fault (core dumped)
repsnapper-2.2.0-0.2.a4.fc19 has been submitted as an update for Fedora 19. https://admin.fedoraproject.org/updates/repsnapper-2.2.0-0.2.a4.fc19
repsnapper-2.2.0-0.2.a4.fc18 has been submitted as an update for Fedora 18. https://admin.fedoraproject.org/updates/repsnapper-2.2.0-0.2.a4.fc18
repsnapper-2.2.0-0.2.a4.fc17 has been submitted as an update for Fedora 17. https://admin.fedoraproject.org/updates/repsnapper-2.2.0-0.2.a4.fc17
This update fixes the issue for me. If you are not in hurry, wait for the package to reach testing repository. If you want to try immediately, download the package from Koji: http://kojipkgs.fedoraproject.org//packages/repsnapper/2.2.0/0.2.a4.fc18/i686/repsnapper-2.2.0-0.2.a4.fc18.i686.rpm
Package repsnapper-2.2.0-0.2.a4.fc19: * should fix your issue, * was pushed to the Fedora 19 testing repository, * should be available at your local mirror within two days. Update it with: # su -c 'yum update --enablerepo=updates-testing repsnapper-2.2.0-0.2.a4.fc19' as soon as you are able to. Please go to the following url: https://admin.fedoraproject.org/updates/FEDORA-2013-9896/repsnapper-2.2.0-0.2.a4.fc19 then log in and leave karma (feedback).
repsnapper-2.2.0-0.2.a4.fc19 has been pushed to the Fedora 19 stable repository. If problems still persist, please make note of it in this bug report.
repsnapper-2.2.0-0.2.a4.fc17 has been pushed to the Fedora 17 stable repository. If problems still persist, please make note of it in this bug report.
repsnapper-2.2.0-0.2.a4.fc18 has been pushed to the Fedora 18 stable repository. If problems still persist, please make note of it in this bug report.