Back to bug 29742

Who When What Removed Added
philippedidier 2021-12-08 13:01:24 CET Hardware All i586
philippedidier 2021-12-08 13:01:55 CET Summary guayadeque crashes on i586 but not on x86.64 guayadeque crashes on i586 but not on x86_64
lewyssmith 2021-12-08 20:24:55 CET CC lewyssmith, tarazed25, westel
andrewsfarm 2021-12-08 23:46:00 CET CC andrewsfarm
lewyssmith 2021-12-09 20:30:05 CET URL https://github.com/anonbeat/guayadeque/issues/137
Keywords UPSTREAM
CC tarazed25, westel jani.valimaa
lewyssmith 2021-12-12 20:35:47 CET Source RPM guayadeque 0.4.6-7.git20201222.2.mga8 guayadeque 0.4.6-7.git20201222.2.mga8, wxgtk-3.1.5-0.git20201230.1.mga8.src.rpm
Summary guayadeque crashes on i586 but not on x86_64 guayadeque crashes on i586 but not on x86_64; wxgtk-3.1 is suspected
Assignee bugsquad geiger.david68210
CC lewyssmith
andrewsfarm 2021-12-12 22:38:27 CET Keywords UPSTREAM
Hardware i586 All
andrewsfarm 2021-12-12 22:41:19 CET Summary guayadeque crashes on i586 but not on x86_64; wxgtk-3.1 is suspected guayadeque crashes on i586 but not on x86_64; wxgtk-3.1 is suspected; gnuplot is affected on both arches
philippedidier 2021-12-13 17:33:34 CET Summary guayadeque crashes on i586 but not on x86_64; wxgtk-3.1 is suspected; gnuplot is affected on both arches guayadeque crashes on i586 but not on x86_64; packaging problem
philippedidier 2021-12-17 01:37:41 CET Summary guayadeque crashes on i586 but not on x86_64; packaging problem guayadeque crashes on i586 but not on x86_64; packaging problem with Mageia's build flag macro
davidwhodgins 2021-12-18 07:04:08 CET CC davidwhodgins
fri 2022-01-13 16:59:02 CET CC fri
Depends on 29848
philippedidier 2022-01-13 17:39:37 CET Depends on 29848
fri 2022-01-27 11:54:21 CET See Also https://bugs.mageia.org/show_bug.cgi?id=29848
fri 2022-01-27 15:23:22 CET Depends on 29848
See Also https://bugs.mageia.org/show_bug.cgi?id=29848
philippedidier 2023-11-24 17:46:43 CET See Also https://bugs.mageia.org/show_bug.cgi?id=32550
philippedidier 2023-11-25 18:36:58 CET Status NEW RESOLVED
Resolution --- FIXED

Back to bug 29742