Bug 12777

Summary:	I booted my computer, and proceeded to change the clock time on the panel. this message popped up.
Product:	Mageia	Reporter:	Andrew Riddell <riddellarchives2013>
Component:	RPM Packages	Assignee:	Mageia Bug Squad <bugsquad>
Status:	RESOLVED DUPLICATE	QA Contact:
Severity:	normal
Priority:	Normal	CC:	filip.komar, rverschelde
Version:	4
Target Milestone:	Mageia 4
Hardware:	i586
OS:	Linux
Whiteboard:
Source RPM:		CVE:
Status comment:

Description Andrew Riddell 2014-02-15 02:30:34 CET

The "drakclock" program has crashed with the following error:

  undefined value for mandatory argument 'str' encountered at /usr/libexec/drakclock line 49.
  Perl's trace:
  standalone::bug_handler() called from /usr/lib/perl5/vendor_perl/5.18.1/Gtk3.pm:295
  Gtk3::__ANON__() called from /usr/lib/libDrakX/mygtk3.pm:1501
  mygtk3::main() called from /usr/lib/libDrakX/ugtk3.pm:748
  ugtk3::main() called from /usr/libexec/drakclock:235

Used theme: oxygen-gtk

To submit a bug report, click on the report button.  
This will open a web browser window on Bugzilla where you'll find a form to fill in.  The information displayed above will be transferred to that server
It would be very useful to attach to your report the output of the following command: 'lspcidrake -v'.

I'm using Mageia 4.

Reproducible: 

Steps to Reproduce:

Filip Komar 2014-02-15 09:20:50 CET

CC: atelier-bugs, sysadmin-bugs => filip.komar

Filip Komar 2014-02-15 09:24:46 CET

Component: Bugzilla => RPM Packages
Version: unspecified => 4
Assignee: sysadmin-bugs => bugsquad
Product: Infrastructure => Mageia
Target Milestone: --- => Mageia 4

Comment 1 Rémi Verschelde 2014-02-15 11:07:48 CET

Hi Andrew, this should have been fixed in the latest update for perl-Glib-Object-Introspection.

If you run "rpm -qa | grep perl-Glib-Object-Introspection" and see perl-Glib-Object-Introspection-0.18.0-2.mga4, then it means that you system is already up-to-date. If you still get the drakclock issue after the update, then please reopen bug 12625.

*** This bug has been marked as a duplicate of bug 12625 ***

Status: NEW => RESOLVED
CC: (none) => remi
Resolution: (none) => DUPLICATE