Description of problem: After the recent kernel upgrade to 3.0 the net_applet doesn't work anymore. It shows inacive status, although the wlan connection is working. This semmes to be a different behaviour as described in #2152 It is somehow connected to the kernel, when booting 2.6.38.8, it's working again, when booting 3.0.0 it's not working. Version-Release number of selected component (if applicable): kernel-server-3.0.0-0.rc7.2.1.mga2-1-1.mga2 drakx-net-0.97-1.mga1 drakx-net-applet-0.97-1.mga1 Here is the output of net_applet: -------------------------------< snap >---------------------------------- [oli@beteigeuze ~]$ LC_ALL=C net_applet Cannot open /dev/input/eventX: Permission denied Cannot open /dev/input/eventX: Permission denied Cannot open /dev/input/eventX: Permission denied Cannot open /dev/input/eventX: Permission denied Cannot open /dev/input/eventX: Permission denied Cannot open /dev/input/eventX: Permission denied Cannot open /dev/input/eventX: Permission denied Cannot open /dev/input/eventX: Permission denied Cannot open /dev/input/eventX: Permission denied Cannot open /dev/input/eventX: Permission denied Cannot open /dev/input/eventX: Permission denied Cannot open /dev/input/eventX: Permission denied Cannot open /dev/input/eventX: Permission denied Cannot open /dev/input/eventX: Permission denied Cannot open /dev/input/eventX: Permission denied Cannot open /dev/input/eventX: Permission denied Cannot open /dev/input/eventX: Permission denied Cannot open /dev/input/eventX: Permission denied SIOCETHTOOL: Operation not supported SIOCETHTOOL: Operation not supported Cannot open /dev/input/eventX: Permission denied Cannot open /dev/input/eventX: Permission denied Cannot open /dev/input/eventX: Permission denied Cannot open /dev/input/eventX: Permission denied Cannot open /dev/input/eventX: Permission denied Cannot open /dev/input/eventX: Permission denied Cannot open /dev/input/eventX: Permission denied Cannot open /dev/input/eventX: Permission denied Cannot open /dev/input/eventX: Permission denied Cannot open /dev/input/eventX: Permission denied Cannot open /dev/input/eventX: Permission denied Cannot open /dev/input/eventX: Permission denied Cannot open /dev/input/eventX: Permission denied Cannot open /dev/input/eventX: Permission denied Cannot open /dev/input/eventX: Permission denied Cannot open /dev/input/eventX: Permission denied Cannot open /dev/input/eventX: Permission denied Cannot open /dev/input/eventX: Permission denied -------------------------------< snap >----------------------------------
No connection via eth0, if disconnected eth0 wlan will be activ (not shown by the net_applet)
CC: (none) => magnus.mud
a little bit from dmesg: r8169 0000:02:00.0: eth0: link down r8169 0000:02:00.0: eth0: link down ADDRCONF(NETDEV_UP): eth0: link is not ready r8169 0000:02:00.0: eth0: link up ADDRCONF(NETDEV_CHANGE): eth0: link becomes ready eth0: no IPv6 routers present
I confirm with eth0, no wifi involved. Connection comes up and is operational, but net_applet displays it as down. Here's why: [ftg@ftgme2 ~]$ net_applet Cannot open /dev/input/eventX: Permission denied Cannot open /dev/input/eventX: Permission denied Cannot open /dev/input/eventX: Permission denied Cannot open /dev/input/eventX: Permission denied ^Z [1]+ Stopped net_applet [ftg@ftgme2 ~]$ bg [1]+ net_applet & [ftg@ftgme2 ~]$ cd /dev/input [ftg@ftgme2 input]$ ls by-path/ event0 event1 event2 event3 event4 mice mouse0 There is no eventX. Also: [ftg@ftgme2 input]$ ls -l total 0 drwxr-xr-x 2 root root 100 Jul 18 15:19 by-path/ crw-r----- 1 root root 13, 64 Jul 18 15:19 event0 crw-r----- 1 root root 13, 65 Jul 18 15:19 event1 crw-r----- 1 root root 13, 66 Jul 18 15:19 event2 crw-r----- 1 root root 13, 67 Jul 18 15:19 event3 crw-r----- 1 root root 13, 68 Jul 18 15:19 event4 crw-r----- 1 root root 13, 63 Jul 18 15:19 mice crw-r----- 1 root root 13, 32 Jul 18 15:19 mouse0 These devices are readable only by root.
CC: (none) => ftg
A duplicate. The "Cannot open /dev/input/eventX: Permission denied" is a separate issue, not related to this bug. *** This bug has been marked as a duplicate of bug 1266 ***
Status: NEW => RESOLVEDResolution: (none) => DUPLICATE