LinuxQuestions.org
Visit Jeremy's Blog.
Go Back   LinuxQuestions.org > Forums > Linux Forums > Linux - Distributions > Slackware
User Name
Password
Slackware This Forum is for the discussion of Slackware Linux.

Notices



Reply
 
Search this Thread
Old 08-30-2011, 06:07 PM   #1
ReaperX7
Senior Member
 
Registered: Jul 2011
Location: California
Distribution: LFS-7.6, Slackware 14.1, FreeBSD 10.1
Posts: 3,838
Blog Entries: 15

Rep: Reputation: 1188Reputation: 1188Reputation: 1188Reputation: 1188Reputation: 1188Reputation: 1188Reputation: 1188Reputation: 1188Reputation: 1188
KDE and Network connectivity issues (yet again)


I tried today to get KDE working again with my network and still there is a serious issue, even on the Slackware64-current provided packages.

As soon as KDE starts it kill the network connection completely and even switching to XFce using xwmconfig does not restore connectivity until a reboot is completed.

ifconfig says there is connectivity but there is none.

This isn't an old issue but it did happen to me with 13.37 also. I attempted the fix of deleting the KDE folder in the hidden files to reset the configuration and nothing. Switched window managers as stated above and dead still.

Other people have duplicated the bug also. There is something seriously wrong with KDE that needs to be addressed.

I like using KDE but I can use XFce, but this issue needs addressing, and hopefully someone can clear up what exactly is wrong.
 
Old 08-30-2011, 07:23 PM   #2
SeRi@lDiE
Member
 
Registered: Jun 2006
Location: /dev/null
Distribution: Slackware 13.1, Slackware 13.37, aptosid, rhel
Posts: 538
Blog Entries: 7

Rep: Reputation: 54
Quote:
Originally Posted by ReaperX7 View Post
I tried today to get KDE working again with my network and still there is a serious issue, even on the Slackware64-current provided packages.

As soon as KDE starts it kill the network connection completely and even switching to XFce using xwmconfig does not restore connectivity until a reboot is completed.

ifconfig says there is connectivity but there is none.

This isn't an old issue but it did happen to me with 13.37 also. I attempted the fix of deleting the KDE folder in the hidden files to reset the configuration and nothing. Switched window managers as stated above and dead still.

Other people have duplicated the bug also. There is something seriously wrong with KDE that needs to be addressed.

I like using KDE but I can use XFce, but this issue needs addressing, and hopefully someone can clear up what exactly is wrong.
Hu?

How can you determine this is an actual bug with kde? If it was a bug this would be the issue wit all kde users. I am in KDE and have no issues with my network. Maybe this is related to a specific NIC? Also how is it that kde is handling your nic? Are you using some type of application like network manager?
KDE does nothing with my nic. Its all handle at the back end.
 
Old 08-30-2011, 09:34 PM   #3
ReaperX7
Senior Member
 
Registered: Jul 2011
Location: California
Distribution: LFS-7.6, Slackware 14.1, FreeBSD 10.1
Posts: 3,838
Blog Entries: 15

Original Poster
Rep: Reputation: 1188Reputation: 1188Reputation: 1188Reputation: 1188Reputation: 1188Reputation: 1188Reputation: 1188Reputation: 1188Reputation: 1188
Linksys USB300 (ASIX AX88772A).

I have WICD running as well and it does nothing also. I have even tried NetworkManager, and it's the same thing. Zero connectivity. However... if I do NOT use X11 and KDE and use a commandline browser like LYNX, I get connectivity just fine as if I'm using XFce, BlackBox, etc.

It's something in KDE. It doesn't happen with any other window manager and desktop environment. Only KDE.
 
Old 08-30-2011, 09:48 PM   #4
SeRi@lDiE
Member
 
Registered: Jun 2006
Location: /dev/null
Distribution: Slackware 13.1, Slackware 13.37, aptosid, rhel
Posts: 538
Blog Entries: 7

Rep: Reputation: 54
Quote:
Originally Posted by ReaperX7 View Post
Linksys USB300 (ASIX AX88772A).

I have WICD running as well and it does nothing also. I have even tried NetworkManager, and it's the same thing. Zero connectivity. However... if I do NOT use X11 and KDE and use a commandline browser like LYNX, I get connectivity just fine as if I'm using XFce, BlackBox, etc.

It's something in KDE. It doesn't happen with any other window manager and desktop environment. Only KDE.
This is an issue specific to your configuration of kde and your hardware not a bug.
And if you have evidence and feel strong that this is a bug than take it upstream.
Have you even looked at the kde bug report system to see if somebody have reported your described issue?
I bet you have not.

Have you try to look at the kde system wide settings?
Maybe there is something hard coded in to the kde network settings.... Static or Proxy wise... Who knows... the more I look at this thread the more I think the issue is you (Well something in your config)

Last edited by SeRi@lDiE; 08-30-2011 at 09:54 PM.
 
Old 08-30-2011, 10:19 PM   #5
bosth
Member
 
Registered: Apr 2011
Posts: 235

Rep: Reputation: 68
Try running dmesg after you start KDE. Am I right in understanding this is a USB device? Perhaps KDE is interfering with your USB ports. Have you tried looking at your KDE SystemSettings to see if there is anything relevant there?
 
Old 08-30-2011, 10:43 PM   #6
ReaperX7
Senior Member
 
Registered: Jul 2011
Location: California
Distribution: LFS-7.6, Slackware 14.1, FreeBSD 10.1
Posts: 3,838
Blog Entries: 15

Original Poster
Rep: Reputation: 1188Reputation: 1188Reputation: 1188Reputation: 1188Reputation: 1188Reputation: 1188Reputation: 1188Reputation: 1188Reputation: 1188
The KDE Network Settings dialog box always pops up that it can not Parse the XML file the configuration is stored in. That's the only thing I have found that has any anomalies with the system, even as Root.
 
Old 08-30-2011, 10:56 PM   #7
SeRi@lDiE
Member
 
Registered: Jun 2006
Location: /dev/null
Distribution: Slackware 13.1, Slackware 13.37, aptosid, rhel
Posts: 538
Blog Entries: 7

Rep: Reputation: 54
Quote:
Originally Posted by ReaperX7 View Post
The KDE Network Settings dialog box always pops up that it can not Parse the XML file the configuration is stored in. That's the only thing I have found that has any anomalies with the system, even as Root.
Seriously?
Right now this thread going down hill....
You have posted this issue before now that i remember... claiming that 13.37 is to "beta"
I mean no harm or offense but it sounds to me like you are trying to start something.

Giving you the benefit of the doubt seen that you are fairly new here I will go along with it....

So quoting you again....

Quote:
Originally Posted by ReaperX7 View Post
The KDE Network Settings dialog box always pops up that it can not Parse the XML file the configuration is stored in. That's the only thing I have found that has any anomalies with the system, even as Root.
^^ Buddy that's your issue ^^
Maybe the xml file lost its permissions.


here are some searches for you...

http://www.google.com/search?sourcei...w=1920&bih=964
 
Old 08-30-2011, 10:58 PM   #8
SeRi@lDiE
Member
 
Registered: Jun 2006
Location: /dev/null
Distribution: Slackware 13.1, Slackware 13.37, aptosid, rhel
Posts: 538
Blog Entries: 7

Rep: Reputation: 54
And some more.

http://www.linuxquestions.org/questi...archid=4851875
 
Old 08-30-2011, 11:39 PM   #9
ReaperX7
Senior Member
 
Registered: Jul 2011
Location: California
Distribution: LFS-7.6, Slackware 14.1, FreeBSD 10.1
Posts: 3,838
Blog Entries: 15

Original Poster
Rep: Reputation: 1188Reputation: 1188Reputation: 1188Reputation: 1188Reputation: 1188Reputation: 1188Reputation: 1188Reputation: 1188Reputation: 1188
Trust when I say I'm not trying to cause trouble.

Okay for starters, after some digging, the XML file is part of KNetworkManager which isn't used in Slackware distros (so that's a dead end, big whoop). However, the other tips listed like restarting the DHCP Daemon, resetting Netconfig settings, using static IP addressing, etc... I've done them ALL.

KDE also isn't doing anything to my USB devices. Every device (as well as my game controller and USB Camera) is listed, but after loading KDE, the NIC can not maintain an IP address for the Network Adapter regardless of what tool is used to manage it. It only happens when I use KDE, it never happens for any other desktop environment or window manager, and it can not be cleared up without rebooting the system even after shutting down KDE and X11.
 
Old 08-30-2011, 11:47 PM   #10
bosth
Member
 
Registered: Apr 2011
Posts: 235

Rep: Reputation: 68
Did you try looking at dmesg?

You aren't running as root are you?
 
Old 08-31-2011, 12:18 AM   #11
ReaperX7
Senior Member
 
Registered: Jul 2011
Location: California
Distribution: LFS-7.6, Slackware 14.1, FreeBSD 10.1
Posts: 3,838
Blog Entries: 15

Original Poster
Rep: Reputation: 1188Reputation: 1188Reputation: 1188Reputation: 1188Reputation: 1188Reputation: 1188Reputation: 1188Reputation: 1188Reputation: 1188
Both. Both my user and Root accounts have the same problems. My user is a member of netdev group also. I've fairly much given my user account as much control as possible so it's not a permissions issue.

I tried dmesg while in Xfce and KDE and there is nothing out of the ordinary coming up. Everything is loaded, running, and working except for the network.

The oddest thing was as I mentioned in my original post was the problem only showed up in 13.37 but not in 13.1 versions. Same hardware was being used for 13.1 also and it worked without incident.
 
Old 08-31-2011, 02:51 AM   #12
mRgOBLIN
Slackware Contributor
 
Registered: Jun 2002
Location: New Zealand
Distribution: Slackware
Posts: 999

Rep: Reputation: 227Reputation: 227Reputation: 227
Don't use the KDE network manager and make sure it doesn't start when you log in.

Make sure you have set wicd up as per the instructions, have the wicd-daemon running and are a member of the netdev group.

The KDE network manager has not been Slackware compatible for as long as I can remember (correct me someone if it's been fixed in the past year or so).
 
Old 08-31-2011, 11:31 AM   #13
SeRi@lDiE
Member
 
Registered: Jun 2006
Location: /dev/null
Distribution: Slackware 13.1, Slackware 13.37, aptosid, rhel
Posts: 538
Blog Entries: 7

Rep: Reputation: 54
Quote:
Originally Posted by mRgOBLIN View Post
Don't use the KDE network manager and make sure it doesn't start when you log in.

Make sure you have set wicd up as per the instructions, have the wicd-daemon running and are a member of the netdev group.

The KDE network manager has not been Slackware compatible for as long as I can remember (correct me someone if it's been fixed in the past year or so).
mRgOBLIN has it right on the nail. I have never used any type of network manager in my life.... I hate those things just like I hate firewall builders.... I am sure thats your problem. check your start up settings and disable what you dont need.
 
Old 08-31-2011, 12:24 PM   #14
Woodsman
Senior Member
 
Registered: Oct 2005
Distribution: Slackware 14.1
Posts: 3,482

Rep: Reputation: 534Reputation: 534Reputation: 534Reputation: 534Reputation: 534Reputation: 534
Quote:
It's something in KDE. It doesn't happen with any other window manager and desktop environment. Only KDE.
Quote:
The oddest thing was as I mentioned in my original post was the problem only showed up in 13.37 but not in 13.1 versions. Same hardware was being used for 13.1 also and it worked without incident.
I believe you. I don't believe you are trying to start any flame wars about KDE, but are reporting what is happening to you.

You verified that running Xfce or a window manager environment does not kill the network connection. In the short term that would be one work-around solution. You also mentioned that everything worked in 13.1 --- specifically KDE 4.4.3. Reverting to 13.1 would not provide you the latest KDE, but that would be another short term work-around.

Of course, the preferred solution is to discover why KDE 4.5.5 kills your wifi network adapter. You are using KDE because you want to.

As mRgOBLIN mentioned, the KDE network manager never has been Slackware compatible. In past Slackware releases, sometimes that app worked and sometimes not. Possibly you were fortunate the KDE network manager worked for you in KDE 4.4.3, but at least for you, that no longer is the case with KDE 4.5.5.

Browse the forum and notice a common remedy to configure a wireless network adapter in Slackware is to use wicd. If you are a KDE user then that possibly is somewhat irritating to use a GTK app in KDE. Yet that is a common remedy in Slackware.

I appreciate the resistance to changing ways. I'm an "old school" computer user and don't like the way some things are evolving in the computer industry. I suspect many Slackers are that way in one respect or another, which is one reason many of remain with Slackware. Yet sometimes we have no choice but to adapt to different software to achieve our purposes.

Consider temporarily running Xfce or a window manager and running wicd from there. At least then you can focus on correctly configuring wicd without the KDE network manager interfering. Then disable the KDE network manager from running and launching. That might require you to run KDE more than once, which will kill the network adapter interface and rebooting, but eventually you should be able to run KDE without your adapter dying. And you'll already have wicd configured and ready to go.
 
Old 08-31-2011, 12:48 PM   #15
bosth
Member
 
Registered: Apr 2011
Posts: 235

Rep: Reputation: 68
There is a wicd interface which integrates into KDE available as a Slackbuild. When I use KDE, I only use that and no other network manager, and I have never had a problem connecting.
 
  


Reply


Thread Tools Search this Thread
Search this Thread:

Advanced Search

Posting Rules
You may not post new threads
You may not post replies
You may not post attachments
You may not edit your posts

BB code is On
Smilies are On
[IMG] code is Off
HTML code is Off


Similar Threads
Thread Thread Starter Forum Replies Last Post
XBMC Network Connectivity Issues elusive_night Linux - Software 8 09-04-2010 03:53 AM
Network Connectivity Issues LinuxCrayon Linux - Networking 5 10-09-2008 02:02 PM
Slackware network connectivity issues? Archer36 Slackware 6 03-12-2008 02:01 PM
LXer: 9 Tips to diagnose remote GNU/Linux server network connectivity issues LXer Syndicated Linux News 0 02-21-2007 06:46 PM
Network Connectivity Issues undeadpenguin Linux - Networking 4 09-19-2003 11:57 AM


All times are GMT -5. The time now is 08:08 PM.

Main Menu
Advertisement
My LQ
Write for LQ
LinuxQuestions.org is looking for people interested in writing Editorials, Articles, Reviews, and more. If you'd like to contribute content, let us know.
Main Menu
Syndicate
RSS1  Latest Threads
RSS1  LQ News
Twitter: @linuxquestions
identi.ca: @linuxquestions
Facebook: linuxquestions Google+: linuxquestions
Open Source Consulting | Domain Registration