Description of problem: I'm not sure if this would count as a regression, but as I don't use eth0-interface in my Desktop since I prefer having no wires in my home that I might trip on I use wlan0 instead. wlan0 works just fine now, but when I reboot my Desktop-PC I autologin to GNOME & notice that drakconnect is trying to use eth0 even thou it's deleted using drakconf. Rightclicking on drakconnect & going to Active connections I see both eth0 & wlan0. That seems wrong if I've previously used drakconf to delete the interface. Here's the output from using drakconf to delete the eth0-interface: [root@localhost ~]# "/usr/bin/drakmenustyle" is not executable [Menus] at /usr/sbin/drakconf.real line 822. "/usr/sbin/drakbackup" is not executable [Backups] at /usr/sbin/drakconf.real line 822. "/usr/sbin/drakvirt" is not executable [Virtualization] at /usr/sbin/drakconf.real line 822. "/usr/sbin/tomoyo-gui" is not executable [Tomoyo Policy] at /usr/sbin/drakconf.real line 822. SIOCETHTOOL: Operation is not supported SIOCETHTOOL: Operation is not supported Gtk-CRITICAL **: gtk_cell_view_set_cell_data: assertion `cell_view->priv->displayed_row != NULL' failed at /usr/lib/libDrakX/interactive/gtk.pm line 522. Version-Release number of selected component (if applicable): 0.97.2 How reproducible: Everytime. Steps to Reproduce: 1. Make sure you have a RTL8101E/RTL8102E PCI Express Fast Ethernet controller. 2. Boot your computer into GNOME. 3. Watch the drakx-net-applet before wlan0 comes up & you'll see that it tries to up eth0 even thou you just recently removed it. 4. When wlan0 is up, open drakconf & go to Network and Internet. 5. Click Remove a connection. 6. Check the list of available connections & you see that eth0 is back.
Here's output to show that the module for my card isn't loaded: [root@localhost ~]# lsmod | grep rt ipt_addrtype 12599 2 xt_multiport 12597 5 x_tables 27482 48 ipt_IFWLOG,xt_time,xt_connlimit,xt_realm,xt_set,iptable_raw,xt_comment,xt_recent,xt_policy,ipt_ULOG,ipt_REJECT,ipt_REDIRECT,ipt_NETMAP,ipt_MASQUERADE,ipt_ECN,ipt_ecn,ipt_CLUSTERIP,ipt_ah,ipt_addrtype,xt_TPROXY,ip6_tables,xt_tcpmss,xt_pkttype,xt_physdev,xt_owner,xt_NFQUEUE,xt_NFLOG,xt_multiport,xt_mark,xt_mac,xt_limit,xt_length,xt_iprange,xt_helper,xt_hashlimit,xt_DSCP,xt_dscp,xt_dccp,xt_conntrack,xt_connmark,xt_CLASSIFY,ipt_LOG,xt_tcpudp,xt_state,iptable_nat,iptable_mangle,iptable_filter,ip_tables exportfs 12851 1 nfsd iTCO_vendor_support 13419 1 iTCO_wdt rt73usb 26969 0 crc_itu_t 12579 1 rt73usb rt2x00usb 19438 1 rt73usb rt2x00lib 42569 2 rt73usb,rt2x00usb mac80211 194438 2 rt2x00usb,rt2x00lib cfg80211 163553 2 rt2x00lib,mac80211 usbcore 151763 6 rt73usb,rt2x00usb,usbhid,uhci_hcd,ehci_hcd parport_pc 37225 0 parport 36308 2 ppdev,parport_pc rtc_cmos 18207 0
Hmmmmmmmmmmmmmm. r8169 was the module that the card is using. Here's new info to show that the module isn't used: [root@localhost ~]# lsmod | grep r8169 r8169 47613 0 mii 13486 1 r8169
This message is a reminder that Mageia 1 is nearing its end of life. In approximately 25 days from now, Mageia will stop maintaining and issuing updates for Mageia 1. At that time this bug will be closed as WONTFIX (EOL) if it remains open with a Mageia 'version' of '1'. 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 prior to Mageia 1's end of life. Bug Reporter: Thank you for reporting this issue and we are sorry that we may not be able to fix it before Mageia 1 is end of life. If you would still like to see this bug fixed and 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. -- Mageia Bugsquad
Mageia 1 changed to end-of-life (EOL) status on ''1st December''. Mageia 1 is no longer maintained, which means that it will not receive any further security or bug fix updates. As a result we are closing this bug. If you can reproduce this bug against a currently maintained version of Mageia please feel free to click on "Version" change it against that version of Mageia and reopen this bug. Thank you for reporting this bug and we are sorry it could not be fixed. -- Mageia Bugsquad
Status: NEW => RESOLVEDResolution: (none) => WONTFIX