Bug 5434

Summary: drakconnect crashed (Can't kill a non-numeric process ID at /usr/lib/libDrakX/network/network.pm line 802.)
Product: Mageia Reporter: Markus Mertens <Mertens.MPT>
Component: RPM PackagesAssignee: Olivier Blin <mageia>
Status: RESOLVED DUPLICATE QA Contact:
Severity: normal    
Priority: Normal CC: thierry.vignaud
Version: 1   
Target Milestone: ---   
Hardware: x86_64   
OS: Linux   
Whiteboard:
Source RPM: drakx-net CVE:
Status comment:
Attachments: lspcidrake -v

Description Markus Mertens 2012-04-17 08:38:52 CEST
Created attachment 2008 [details]
lspcidrake -v

The "drakconnect" program crashed. Drakbug-13.58 caught it.


I tried to remove the unused network "wwan0" from within mcc.


Backtrace was:
Can't kill a non-numeric process ID at /usr/lib/libDrakX/network/network.pm line 802.
standalone::bug_handler() called from /usr/lib/libDrakX/wizards.pm:202
wizards::safe_process() called from /usr/lib/libDrakX/network/drakconnect/delete.pm:65
network::drakconnect::delete::del_intf() called from /usr/sbin/drakconnect:47

Kernel version = 2.6.38.8-server-10.mga
Distribution=Mageia release 1 (Official) for x86_64
CPU=Intel(R) Xeon(R) CPU           W5590  @ 3.33GHz
Manuel Hiebel 2012-04-17 16:41:55 CEST

Assignee: bugsquad => mageia
Source RPM: drakx-net-text-0.97.2-1.mga1 => drakx-net

Comment 1 Marja Van Waes 2012-07-06 15:05:55 CEST
Please look at the bottom of this mail to see whether you're the assignee of this  bug, if you don't already know whether you are.


If you're the assignee:

We'd like to know for sure whether this bug was assigned correctly. Please change status to ASSIGNED if it is, or put OK on the whiteboard instead.

If you don't have a clue and don't see a way to find out, then please put NEEDHELP on the whiteboard.

Please assign back to Bug Squad or to the correct person to solve this bug if we were wrong to assign it to you, and explain why.

Thanks :)

**************************** 

@ the reporter and persons in the cc of this bug:

If you have any new information that wasn't given before (like this bug being valid for another version of Mageia, too, or it being solved) please tell us.

@ the reporter of this bug

If you didn't reply yet to a request for more information, please do so within two weeks from now.

Thanks all :-D
Comment 2 Manuel Hiebel 2012-09-04 16:23:33 CEST
fixed in cauldron (according to tv)

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

Comment 3 Thierry Vignaud 2012-09-06 10:53:59 CEST
Dup

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

CC: (none) => thierry.vignaud
Resolution: FIXED => DUPLICATE