Description of problem: (lazarus-ide:2141): GLib-GObject-CRITICAL **: g_object_unref: assertion `G_IS_OBJECT (object)' failed [FORMS.PP] ExceptionOccurred Sender=EInvalidOp Exception=Invalid floating point operation Stack trace: $00007FA72A2D6D2A TApplication.HandleException Invalid floating point operation Stack trace: $00007FA72A2D6D2A [FORMS.PP] ExceptionOccurred Version-Release number of selected component (if applicable): How reproducible: Steps to Reproduce: 1. 2. 3.
Assignee: bugsquad => dmorganec
Assignee: dmorganec => olav
Le problème a été résolu en désinstallant : désinstallation du paquetage liboxygen-gtk-1.1.3-1.mga2.i586 désinstallation du paquetage oxygen-gtk3-1.0.50-8.mga2.x86_64 désinstallation du paquetage oxygen-gtk-debug-1.1.3-1.mga2.x86_64 ....? J'ai tenté d'utiliser gdb, ce qui m'a fait apparaitre la chaine de caractère "oxygen".
Please speak in English here, and thanks for the info ;) "the issue was solved with removing: ... I have try with gdb, and it show me the string "oxygen" " (something like that :) )
Severity: critical => major
Works for me. I need steps to reproduce and a proper backtrace. Do something like: gdb lazarus-ide r then bt when it crashes. Make sure to add all the debug packages gdb requests, and if it does, do above steps again. If removing oxygen fixes it, then likely it is an oxygen problem.
Keywords: (none) => NEEDINFO
@ Michel Do you still have this bug? If so, can you please give the information Olav requested in comment 3 Please read https://wiki.mageia.org/en/Debugging_software_crashes if you do not understand what he means.
CC: (none) => marja11
Since there are insufficient details provided in this report for us to investigate the issue further, and we have not received feedback to the information we have requested above, we will assume the problem was not reproducible, or has been fixed in one of the updates we have released for the reporter's distribution. Users who have experienced this problem are encouraged to upgrade to the latest update of their distribution, and if this issue turns out to still be reproducible in the latest update, please reopen this bug with additional information. Closing as OLD.
Status: NEW => RESOLVEDResolution: (none) => OLD