Bug 11830 - drakhardware break it at the begining
Summary: drakhardware break it at the begining
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: NEEDINFO, Triaged
: 11836 (view as bug list)
Depends on:
Blocks:
 
Reported: 2013-11-30 13:55 CET by Bernard SIAUD
Modified: 2013-12-01 09:47 CET (History)
1 user (show)

See Also:
Source RPM: drakxtools-16.2-1.mga4.src.rpm
CVE:
Status comment:


Attachments

Description Bernard SIAUD 2013-11-30 13:55:41 CET
Description of problem: drakhardware stop ip


Version-Release number of selected component (if applicable):
drakxtools-16.2-1.mga4.src.rpm

How reproducible:
Every time I attempt to run drakhardware


Steps to Reproduce:
[root@localhost ~]# drakhardware 
Subroutine Gtk3::main redefined at /usr/lib/perl5/vendor_perl/5.18.1/Gtk3.pm line 304.

(drakhardware:19153): Gtk-WARNING **: GtkImage 0x3409e60 adjusted size vertical min 51 natural 51 must not decrease below min 52 natural 52

(drakhardware:19153): Gtk-WARNING **: GtkImage 0x3409e60 attempted to adjust its size allocation from -12,1 805x58 to 0,0 793x59. adjust_size_allocation must keep allocation inside original bounds
Subroutine Gtk3::main redefined at /usr/lib/perl5/vendor_perl/5.18.1/Gtk3.pm line 304.
Minuterie d'alerte
[root@localhost ~]#

Reproducible: 

Steps to Reproduce:
Manuel Hiebel 2013-11-30 17:01:22 CET

Keywords: (none) => Triaged
Assignee: bugsquad => thierry.vignaud

Comment 1 Thierry Vignaud 2013-11-30 23:01:48 CET
Please try with drakxtools-16.3

Keywords: (none) => NEEDINFO

Comment 2 Thierry Vignaud 2013-12-01 08:23:16 CET
*** Bug 11836 has been marked as a duplicate of this bug. ***

CC: (none) => contact

Comment 3 Thierry Vignaud 2013-12-01 08:24:09 CET
Closing

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

Comment 4 Bernard SIAUD 2013-12-01 09:47:51 CET
Yes, it's good now.

Thank's.

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