The "drakfont" program crashed. Drakbug-17.88 caught it. Ouverture de l'item de MCC "gérer, ajouter ... polices windows SEGV Glibc's trace: 4: /lib64/libperl.so.5.22(Perl_sighandler+0x213) [0x7f60cda140f3] 5: /lib64/libpthread.so.0(+0x10bb0) [0x7f60cd74abb0] 6: /lib64/libgtk-3.so.0(+0x1949e3) [0x7f60c26409e3] 7: /lib64/libgtk-3.so.0(+0xd10ae) [0x7f60c257d0ae] 8: /lib64/libgtk-3.so.0(+0x18eeed) [0x7f60c263aeed] 9: /lib64/libgtk-3.so.0(+0x18b217) [0x7f60c2637217] 10: /lib64/libgtk-3.so.0(gtk_style_properties_set_valist+0x1a8) [0x7f60c257d408] 11: /lib64/libgtk-3.so.0(gtk_style_properties_set+0xe6) [0x7f60c257d726] 12: /lib64/libgtk-3.so.0(+0x249bba) [0x7f60c26f5bba] 13: /lib64/libgtk-3.so.0(+0xb43c9) [0x7f60c25603c9] 14: /lib64/libgtk-3.so.0(+0xb48f1) [0x7f60c25608f1] 15: /lib/../lib64/libgobject-2.0.so.0(+0x10134) [0x7f60c4572134] 16: /lib/../lib64/libgobject-2.0.so.0(g_signal_emit_valist+0xbf8) [0x7f60c458c148] 17: /lib/../lib64/libgobject-2.0.so.0(g_signal_emit+0x82) [0x7f60c458c822] 18: /lib64/libgtk-3.so.0(+0x3509b4) [0x7f60c27fc9b4] 19: /lib64/libgtk-3.so.0(gtk_tree_view_set_cursor_on_cell+0x138) [0x7f60c28002b8] Perl's trace: drakbug::bug_handler() called from /usr/lib/libDrakX/drakbug.pm:41 drakbug::__ANON__() called from /usr/lib/perl5/vendor_perl/5.22.3/Gtk3.pm:566 (eval)() called from /usr/lib/perl5/vendor_perl/5.22.3/Gtk3.pm:566 Gtk3::main() called from /usr/lib/perl5/vendor_perl/5.22.3/Gtk3.pm:523 Gtk3::__ANON__() called from /usr/lib/libDrakX/mygtk3.pm:1550 mygtk3::main() called from /usr/lib/libDrakX/ugtk3.pm:857 ugtk3::main() called from /usr/libexec/drakfont:512 main::interactive_mode() called from /usr/libexec/drakfont:516 Theme name: Adwaita Kernel version = 4.9.50-desktop-1.mga6 Distribution=Mageia release 6 (Official) for x86_64 CPU=Intel(R) Core(TM) i3 CPU 540 @ 3.07GHz
Looks like bug 17176, which was closed as duplicate of bug 16354 The latter has as summary "drakfont segfaulted at /usr/libexec/drakfont:590 ($file_dialog->destroy)" But bug 17176 and this report don't have the long Perl trace with a line resembling the /usr/libexec/drakfont:590 line that bug 16354 has.
Ever confirmed: 0 => 1CC: (none) => marja11Assignee: bugsquad => mageiatoolsSource RPM: drakxtools-17.88-1.mga6 => drakxtools-17.88-1.mga6. gtk+3.0Status: UNCONFIRMED => NEW
*** Bug 21865 has been marked as a duplicate of this bug. ***
sees you are under gnome, can you confirm ? i ask because under plasma i don't reproduce.
CC: (none) => mageia
*** Bug 22827 has been marked as a duplicate of this bug. ***
CC: (none) => fenrislisek
(In reply to Nicolas Lécureuil from comment #3) > sees you are under gnome, can you confirm ? > > i ask because under plasma i don't reproduce. @ all who have seen this crash: Please answer Nicolas' question
(In reply to Marja van Waes from comment #5) > (In reply to Nicolas Lécureuil from comment #3) > > sees you are under gnome, can you confirm ? > > > > i ask because under plasma i don't reproduce. > > @ all who have seen this crash: > > Please answer Nicolas' question Hiya, I was working in Plasma when my bug happend.
*** Bug 23181 has been marked as a duplicate of this bug. ***
CC: (none) => raoul.behrend
Hardware: x86_64 => All
*** Bug 22034 has been marked as a duplicate of this bug. ***
CC: (none) => listas.apl
*** Bug 23234 has been marked as a duplicate of this bug. ***
CC: (none) => krakkeroe
Mageia 6 changed to end-of-life (EOL) status on 2019-09-30. It is no longer maintained, which means that it will not receive any further security or bug fix updates. Package Maintainer: If you wish for this bug to remain open because you plan to fix it in a currently maintained version, simply change the 'version' to a later Mageia version. Bug Reporter: Thank you for reporting this issue and we are sorry that we weren't able to fix it before Mageia 6's end of life. If you are able to reproduce it against a later version of Mageia, you are encouraged to click on "Version" and change it against that version of Mageia. Although we aim to fix as many bugs as possible during every release's lifetime, sometimes those efforts are overtaken by events. Often a more recent Mageia release includes newer upstream software that fixes bugs or makes them obsolete. If you would like to help fixing bugs in the future, don't hesitate to join the packager team via our mentoring program [1] or join the teams that fit you most [2]. [1] https://wiki.mageia.org/en/Becoming_a_Mageia_Packager [2] http://www.mageia.org/contribute/ Best regards, Aurélien Bugsquad Team
Resolution: (none) => OLDCC: (none) => ouaurelienStatus: NEW => RESOLVED