Bug 14433

Summary: drakconf crashed (object 90e2c48 is not really a GObject at drakconf line 1079)
Product: Mageia Reporter: Mormede Bernard <bmormede>
Component: RPM PackagesAssignee: Mageia Bug Squad <bugsquad>
Status: RESOLVED OLD QA Contact:
Severity: normal    
Priority: Normal CC: dune06, thierry.vignaud
Version: 4   
Target Milestone: ---   
Hardware: i586   
OS: Linux   
Whiteboard:
Source RPM: drakconf-12.51-1.mga4 CVE:
Status comment:

Description Mormede Bernard 2014-11-02 17:45:43 CET
The "drakconf" program crashed. Drakbug-16.26.11 caught it.

je lancais Gérer vos partitions sur le GUI de drakconf

object 90e2c48 is not really a GObject at /usr/libexec/drakconf line 1079.
Perl's trace:
standalone::bug_handler() called from /usr/libexec/drakconf:1103

Theme name: oxygen-gtk
Kernel version = 3.14.18-desktop586-3.mga4
Distribution=Mageia release 4 (Official) for i586
CPU=Pentium(R) Dual-Core CPU       T4200  @ 2.00GHz
Comment 1 Manuel Hiebel 2014-11-07 20:19:00 CET
you can reproduce ?
Comment 2 Mormede Bernard 2014-11-08 08:28:05 CET
no, not until now
Thierry Vignaud 2015-05-22 09:00:32 CEST

CC: (none) => thierry.vignaud
Summary: drakconf crashed => drakconf crashed (object 90e2c48 is not really a GObject at drakconf line 1079)

Comment 3 Thierry Vignaud 2015-07-01 13:06:00 CEST
*** Bug 16259 has been marked as a duplicate of this bug. ***

CC: (none) => dune06

Comment 4 Samuel Verschelde 2015-09-21 13:21:50 CEST
Mageia 4 changed to end-of-life (EOL) status on 2015-09-19. It is 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 4'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. If it's valid in several versions, 
select the highest and add MGAxTOO in whiteboard for each other valid release.
Example: it's valid in cauldron and Mageia 5, set to cauldron and add MGA5TOO.

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/
Comment 5 Marja Van Waes 2015-10-27 06:58:46 CET
As announced over a month ago, Mageia 4 changed to end-of-life (EOL) status on 2015-09-19. It is is no longer maintained, which means that it will not receive any further security or bug fix updates.

This issue may have been fixed in a later Mageia release, so, if you still see it and didn't already do so: please upgrade to Mageia 5 (or, if you read this much later than this is written: make sure you run a currently maintained Mageia version)

If you are able to reproduce it against a maintained version of Mageia, you are encouraged to 
1. reopen this bug report, by changing the "Status" from "RESOLVED - OLD" to "REOPENED"
2. click on "Version" and change it against that version of Mageia. If you know it's valid in several versions, select the highest and add MGAxTOO in whiteboard for each other valid release.
Example: it's valid in cauldron and Mageia 5, set to cauldron and add MGA5TOO.
3. give as much relevant information as possible. If you're not an experienced bug reporter and have some time: please read this page:
https://wiki.mageia.org/en/How_to_report_a_bug_properly

If you see a similar issue, but are _not_sure_ it is the same, with the same cause, then please file a new bug report and mention this one in it (please include the bug number, too). 


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/

Status: NEW => RESOLVED
Resolution: (none) => OLD