Bug 16905 - drakguard crashed (undefined value for mandatory argument 'text' encountered at /usr/sbin/drakguard line 230)
Summary: drakguard crashed (undefined value for mandatory argument 'text' encountered ...
Status: NEW
Alias: None
Product: Mageia
Classification: Unclassified
Component: RPM Packages (show other bugs)
Version: Cauldron
Hardware: x86_64 Linux
Priority: Normal major
Target Milestone: ---
Assignee: Thierry Vignaud
QA Contact:
URL:
Whiteboard:
Keywords:
Depends on:
Blocks: 11778
  Show dependency treegraph
 
Reported: 2015-10-05 04:10 CEST by haile eyob
Modified: 2020-08-18 18:20 CEST (History)
6 users (show)

See Also:
Source RPM: drakguard-1.7-4.mga8.src.rpm
CVE:
Status comment:


Attachments
Patch (1.55 KB, patch)
2017-09-15 15:59 CEST, Masanori Kakura
Details | Diff

Description haile eyob 2015-10-05 04:10:10 CEST
The "drakguard" program crashed. Drakbug-16.104 caught it.

Learning about the Mageia Control Center

undefined value for mandatory argument 'text' encountered at /usr/sbin/drakguard line 230.
Perl's trace:
drakbug::bug_handler() called from /usr/lib/perl5/vendor_perl/5.20.1/Gtk3.pm:295
Gtk3::__ANON__() called from /usr/sbin/drakguard:323

Theme name: oxygen-gtk
Kernel version = 4.1.8-desktop586-1.mga5
Distribution=Mageia release 5 (Official) for i586
CPU=AMD Athlon(tm) II X2 220 Processor
Comment 1 Rémi Verschelde 2015-10-05 07:18:20 CEST
Thanks, drakguard has no official maintainer in our database but I put some devs who use to work on it in CC.

Could you give more information as to what you were doing exactly with drakguard (the parental control utility in the MCC) when it crashed?

CC: (none) => derekjenn, thierry.vignaud
Summary: drakguard crashed => drakguard crashed (undefined value for mandatory argument 'text' encountered at /usr/sbin/drakguard line 230)

Thierry Vignaud 2015-10-05 11:48:32 CEST

Assignee: bugsquad => thierry.vignaud
Blocks: (none) => 11778

Comment 2 Thierry Vignaud 2015-10-06 13:03:46 CEST
What language do you use?

Keywords: (none) => NEEDINFO

Comment 3 Masanori Kakura 2017-09-15 15:59:23 CEST
Created attachment 9675 [details]
Patch

I found a similar bug in drakguard on Mageia 6. It crashes when cancelling/closing file chooser dialog in "Block programs" tab.

Steps to reproduce:

1. Check "Enable parental control" in "Configuration" tab if unchecked
2. Check "Block defined applications" in "Block programs" tab if unchecked
3. Click "..." button (A file chooser dialog appears)
4. Press "Cancel" or close (click WM close button) the file chooser dialog

----- The output of Mageia Bug Report Tool -----
The "drakguard" program has crashed with the following error:

  undefined value for mandatory argument 'text' encountered at /usr/sbin/drakguard line 230.
  Perl's trace:
  drakbug::bug_handler() called from /usr/lib/perl5/vendor_perl/5.22.3/Gtk3.pm:524
  Gtk3::__ANON__() called from /usr/sbin/drakguard:323

CC: (none) => kakurasan

Comment 4 Marja Van Waes 2018-09-30 18:16:45 CEST
@ Haile and Masanori

Please reply to comment #2:
> What language do you use?

CC: (none) => marja11
Version: 5 => 6

Comment 5 Masanori Kakura 2018-10-01 15:19:47 CEST
(In reply to Marja Van Waes from comment #4)
> @ Haile and Masanori
> 
> Please reply to comment #2:
> > What language do you use?

My locale is "ja_JP.UTF-8", but also confirmed with "LANG=C". I believe this issue is locale-independent and GTK+ related.
Comment 6 Aurelien Oudelet 2020-08-16 18:56:52 CEST
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

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

Comment 7 Masanori Kakura 2020-08-17 15:32:32 CEST
> 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.
I still can reproduce this on Mageia 8 Beta 1
but I don't have the permission to edit "Version".

Ever confirmed: 1 => 0
Status: RESOLVED => UNCONFIRMED
Resolution: OLD => (none)

Comment 8 Aurelien Oudelet 2020-08-17 15:45:08 CEST
Assigning against Cauldron and add latest drakguard SRPM.

Version: 6 => Cauldron
Severity: normal => major
Ever confirmed: 0 => 1
Keywords: NEEDINFO => (none)
Source RPM: drakguard-1.3-1.mga5 => drakguard-1.7-4.mga8.src.rpm
Status: UNCONFIRMED => NEW

Comment 9 Dave Hodgins 2020-08-17 16:03:09 CEST
(In reply to Masanori Kakura from comment #7)
> but I don't have the permission to edit "Version".

You have permission to edit the bug fields now.

CC: (none) => davidwhodgins

Comment 10 Masanori Kakura 2020-08-18 16:48:59 CEST
Thanks Aurelien and Dave. Now I can do it but thankfully I don't need to do it :)
Comment 11 Dave Hodgins 2020-08-18 18:20:53 CEST
In the future you can. :-) The reason we restrict it is to block spammers who
have created mageia identities and used bots to add spam links to various 
bugzilla entries.

Note You need to log in before you can comment on or make changes to this bug.