Bug 12009 - mgaapplet crashed
Summary: mgaapplet crashed
Status: RESOLVED FIXED
Alias: None
Product: Mageia
Classification: Unclassified
Component: RPM Packages (show other bugs)
Version: Cauldron
Hardware: x86_64 Linux
Priority: Normal normal
Target Milestone: ---
Assignee: Thierry Vignaud
QA Contact:
URL:
Whiteboard:
Keywords:
Depends on:
Blocks: 11778
  Show dependency tree / graph
 
Reported: 2013-12-16 09:29 CET by René Lagoni Neukirch
Modified: 2013-12-16 10:36 CET (History)
1 user (show)

See Also:
Source RPM: mgaonline-3.1-1.mga4
CVE:
Status comment:

Attachments
Add an attachment (proposed patch, testcase, etc.)

Description René Lagoni Neukirch 2013-12-16 09:29:47 CET 
The "mgaapplet" program crashed. Drakbug-16.15 caught it.


Just looked for the "About" of the applet.
(Right click on the icon in the panel).

Probably same-same as the recent, similar bug (11972) on draksambashare.
Maybe a little code inspection around the "Abouts" would catch some more similar bugs ???



need an array ref to convert to GArray at /usr/lib/libDrakX/mygtk3.pm line 1052.
Perl's trace:
standalone::bug_handler() called from /usr/lib/perl5/vendor_perl/5.18.1/Gtk3.pm:303
Gtk3::__ANON__() called from /usr/bin/mgaapplet:263

Theme name: oxygen-gtk
Kernel version = 3.12.3-server-1.mga4
Distribution=Mageia release 4 (Cauldron) for x86_64
CPU=Intel(R) Core(TM) i5-3350P CPU @ 3.10GHz
Comment 1 Thierry Vignaud 2013-12-16 10:26:25 CET 
Fixed in git

Status: NEW => RESOLVED
CC: (none) => thierry.vignaud
Resolution: (none) => FIXED
Assignee: bugsquad => thierry.vignaud

Comment 2 Mageia Robot 2013-12-16 10:30:41 CET 
commit 11da5efc0519fa287935aa5f0867bd8464e8b59b
Author: Thierry Vignaud <thierry.vignaud@...>
Date:   Mon Dec 16 10:28:40 2013 +0100

    fix crashing when displaying about dialog (mga#12009)
    
    set_authors() needs an array ref with Gtk3
---
 Commit Link:
   http://gitweb.mageia.org/software/mgaonline/commit/?id=11da5efc0519fa287935aa5f0867bd8464e8b59b
Thierry Vignaud 2013-12-16 10:36:30 CET

Blocks: (none) => 11778
Note You need to log in before you can comment on or make changes to this bug.