Description of problem: When resizing a window to over 4020 pixel on a dual 4k setup, emerald segfaults with *** stack smashing detected *** Version-Release number of selected component (if applicable): emerald-0.8.14-1.mga6 How reproducible: Always Steps to Reproduce: 1. resize a window of your choice to 4100 pixel width. *** stack smashing detected ***: emerald terminated ======= Backtrace: ========= /lib64/libc.so.6(+0x72435)[0x7f6ec9b10435] /lib64/libc.so.6(__fortify_fail+0x37)[0x7f6ec9ba52e7] /lib64/libc.so.6(__fortify_fail+0x0)[0x7f6ec9ba52b0] /lib64/libcairo.so.2(+0x6904a)[0x7f6eca5db04a] /lib64/libcairo.so.2(+0x6995a)[0x7f6eca5db95a] /lib64/libcairo.so.2(+0x6a7a3)[0x7f6eca5dc7a3] /lib64/libcairo.so.2(+0x27508)[0x7f6eca599508] /lib64/libcairo.so.2(+0x380c7)[0x7f6eca5aa0c7] /lib64/libcairo.so.2(+0x6d817)[0x7f6eca5df817] /lib64/libcairo.so.2(+0x2f42c)[0x7f6eca5a142c] /lib64/libcairo.so.2(+0x28b99)[0x7f6eca59ab99] /lib64/libcairo.so.2(cairo_fill+0x15)[0x7f6eca594255] /usr/lib64/emerald/engines/libvrunner.so(draw_filled_closed_curve+0xf3)[0x7f6ebdbb4053] /usr/lib64/emerald/engines/libvrunner.so(engine_draw_frame+0x33a)[0x7f6ebdbb470a] emerald[0x40e3ab] emerald[0x40f88f] emerald[0x407fec] /lib64/libglib-2.0.so.0(g_main_context_dispatch+0x13a)[0x7f6eca8de97a] /lib64/libglib-2.0.so.0(+0x49cf8)[0x7f6eca8decf8] /lib64/libglib-2.0.so.0(g_main_loop_run+0xc2)[0x7f6eca8df012] /lib64/libgtk-3.so.0(gtk_main+0x85)[0x7f6ecc0dfe15] emerald[0x40773e] /lib64/libc.so.6(__libc_start_main+0xf0)[0x7f6ec9abe600] emerald[0x407829]
Assigning to the registered emerald maintainer.
Assignee: bugsquad => tarakbumbaCC: (none) => marja11
Reassigning to all packagers collectively as the original maintainer is not available anymore (thanks for all your work Atilla!).
Assignee: tarakbumba => pkg-bugs
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
Status: NEW => RESOLVEDCC: (none) => ouaurelienResolution: (none) => OLD