Network killed by Gnome

Hi,
Tried to install Gnome today. Curiosity killed more than one cat, sure. There are no connections for me, in good old KDE - and in Gnome, too. Right now I'm sitting in front of Archbang livecd system, the main arch install properly chrooted. Unfortunately, I've no idea about the next step.
My network configuration is the simplest possible: router, DHCP, wired. All of my livecds have no trouble at all. KDE, as well as Gnome, uses networkmanager.
While in trouble, LAN1 LED on the router is yellow instead of green.
Last edited by Llama (2013-05-02 15:57:57)

I know your pain - this is one of the things I've disliked about Arch compared to other distros. Whenever this happened to me, it was usually a conflict between netcfg and whatever the graphical network program is, typically networkmanager. If you are using networkmanager in either KDE or GNOME, I found a temporary workaround is to disable networking and re-enable it (from the nm GUI). Try shutting down netcfg and see if that helps.
Last edited by schmidtbag (2013-05-02 15:06:34)

Similar Messages

Pacman: no network connection in gnome-terminal since update.

Since the upgrade to Gnome 2.30 I can not use any programs that require a network connection in gnome-terminal. The network works fine in Xterm and tty.
To get an internet connection I use networkmanager-pptp to connect to a VPN, and I have a proxy server set in gnome-network-properties.
Last edited by Rodan (2010-04-05 14:56:31)

Rodan wrote:
Since the upgrade to Gnome 2.30 I can not use any programs that require a network connection in gnome-terminal. The network works fine in Xterm and tty.
To get an internet connection I use networkmanager-pptp to connect to a VPN, and I have a proxy server set in gnome-network-properties.
weird, i am gonna look into this and inform you when i get some info. It seems like you have to edit gconf using gconf-editor.
Last edited by raj7095 (2010-04-05 02:11:25)

[SOLVED] No network manager in Gnome 3.8

I've been looking for this for a few days but the search terms that I'm working with a probably too generic.
I come from 3.4 on Debian and was always able to connect to wireless networks from a menu in the top right. I could also set proxy settings there and other things.
Now I'm connecting to my wifi with wifi-menu and changing the proxy when needed by using the export command, which is working nicely, but I'm looking for more comfort now.
Where it should be: http://snag.gy/1W9vD.jpg
What I'm looking for: http://doc.opensuse.org/documentation/h … etwork.png
I was looking in the direction of nm-applet and NetworkManager, but after installing these I still don't see it coming up in Gnome. Anybody who can point me in the right direction?
edit: I do get these
** (nm-applet:3032): WARNING **: Could not initialize NMClient /org/freedesktop/NetworkManager: Unit dbus-org.freedesktop.NetworkManager.service failed to load: No such file or directory. See system logs and 'systemctl status dbus-org.freedesktop.NetworkManager.service' for details.
** (nm-applet:3032): WARNING **: Error connecting to ModemManager: Error calling StartServiceByName for org.freedesktop.ModemManager1: GDBus.Error:org.freedesktop.systemd1.LoadFailed: Unit dbus-org.freedesktop.ModemManager1.service failed to load: No such file or directory. See system logs and 'systemctl status dbus-org.freedesktop.ModemManager1.service' for details.
** Message: applet now removed from the notification area
** Message: applet now embedded in the notification area
** (nm-applet:3032): WARNING **: fetch_connections_done: error fetching connections: (32) Unit dbus-org.freedesktop.NetworkManager.service failed to load: No such file or directory. See system logs and 'systemctl status dbus-org.freedesktop.NetworkManager.service' for details..
** (nm-applet:3032): WARNING **: Failed to register as an agent: (32) Unit dbus-org.freedesktop.NetworkManager.service failed to load: No such file or directory. See system logs and 'systemctl status dbus-org.freedesktop.NetworkManager.service' for details.
Last edited by InFerYes (2013-09-25 23:18:19)

Ok, pretty typical, after looking for a while and asking for help you usually find the solution yourself, as did I.
Make sure NetworkManager is started:
systemctl status NetworkManager
If not, start it
systemctl start NetworkManager
But also bring down the currently link that you've made "manually":
ip link set wlp11s0 down
The applet is visible and I'm connecting to networks.
Thanks for reading, issue resolved.

By connecting MBP to wireless network, kills network.

So here is a crazy one.
I just got a work issued brand new MBP, and as soon as i try to connect it to my network, the network goes down. All the lights are lit on my modem and router and I even called the cable company and they didn't see any issues on their end. As soon as I reset the router and modem it starts working fine, but as soon as I try to connect the new MBP, it kills it again. Craziest thing I have seen. What could possibly be killing my network on this MBP?
I have another mbp, an imac, two iphones, an ipad, and appletv on the network without anything issues.

You have not provided any detail about your setup, connection, equipment, or configuration so any response will be a guess.
I guess you have not configured your computer and to use DHCP.
Second guess, you have not correctly set up your wifi security on your router and computer.
Third guess, you configured your computer incorrectly to share its network connection.
My suggestion, use an Ethernet cable to connect your computer to the router and check its settings and security. Once you get that connection working try setting up your wifi connection.
Provide more detail.

Clicking on router in Win7 My Computer Network killed internet until router hard reset!

I blogged about a really odd bug I found in either Win7 and or the verizon fios router, check it out...
http://gregfricke.wordpress.com/2009/12/03/how-windows-7-killed-my-verizon-fios-router/
In a nutshell, double clicking on the router in the network area in my computer, killed the broadband pipe on the router until I hard reset the router.
The verizon rep said this was news to him and he escalated it internally but I wanted to throw it out there for anyone that runs into this

gman6 wrote:
I blogged about a really odd bug I found in either Win7 and or the verizon fios router, check it out...
http://gregfricke.wordpress.com/2009/12/03/how-windows-7-killed-my-verizon-fios-router/
In a nutshell, double clicking on the router in the network area in my computer, killed the broadband pipe on the router until I hard reset the router.
The verizon rep said this was news to him and he escalated it internally but I wanted to throw it out there for anyone that runs into this
I have an Actiontec router, I tried what you did and got somewhat different results:
1) When I look at my network in Windows 7 I see "Wireless Broadband Router" not "Actiontec ...." Strange. But a right-click on the icon and selecting Properties does show the device as an Actionte.
2) The first time I double-clicked on the router icon, nothing happened, I still had internet connectivity.
3) When I double-clicked on the router icon a second time, I did lose internet connectivity as you did.
4) When I logged into the router it clearly said the WAN was disconnected, same as you.
5) I did a reboot of the router from within the router dialog. When it finished rebooting the WAN showed "connecting". After waiting a few minutes it showed "connected" and all worked normally. No hard reset required
That is strange that it does disable the WAN. But again I was able to get it back with just a reboot. I am one of the original FiOS internet users, I still have a PPPoE connection and my WAN is Ethernet not coax so that might explain the difference, I don't know.
But yeah, Verizon needs to fix that.
Justin
Verizon FiOS TV, Internet, and phone
QIP6416-P1, IMG 1.7C, Build 09.83
Keller, TX 76248

Warning: Upcoming dbus upgrade will kill outdated gnome sessions

We're planning to upgrade dbus to 1.0.x in a short while. The new configuration files used by dbus 1.0.x is incompatible with the version in our repositories, which causes dbus to crash as soon as it tries to reload the configuration.
Due to a bug in gnome-session and the XFCE Terminal program, these programs will crash together with dbus. This bug has been fixed on Januari 23 in both gnome-session and Terminal.
When upgrading your system to dbus 1.0.x from either XFCE Terminal or Gnome with the affected packages dated before Januari 23rd, be warned that you will lose all unsaved work affected by these crashes (gnome-session drops to the console and hard-quits all your active programs, Terminal only kills all active Terminal sessions). A solution is to upgrade from outside of these programs, or, to upgrade to the latest versions of these packages, restarting these programs and then upgrade dbus.

Hi there,
I just did the upgrade to dbus-1.0.2-2 from a gnome terminal and although my system was up to date as of 12 hours ago I still found that the desktop and everything on it died.
regards ross

Network browsing with Gnome

rant mode = on
Ok, Novell says that it wants to default with Gnome...
I like to follow Novells lead,but this is getting a bit troubling,
I was totally happy with KDE and got to know it quite easily. But....
The Gnome is such a pretty simple thing and nice to use and will make a
great Business class desktop unless:
1) you are a sophisticated power user with unusuall needs
2) you are a Netware administrator and want to assign file rights to
network folders or files with novell file attributes
3) You want to configure your menu's to make life easier
for you to do your job
4) You want to browse unmapped NSS based file systems
this is why I'm posting, I can't figure out what exactly the
Nautilus plugin for NCL actually does. It seems that there is no way to
browse, I tried "network servers" in the internet section. I tried using
nnetscannds:/ or nnetscannwsrv:/ all to no avail.
Am I crazy or is the Gnome a little daft?
Did I install something wroong?
I have double checked and reintstalled the client with both red-carpet and
the bash script.
at this rate it will be NLD version 12 before I actually use this at work!
and it's supposed to be a business class system.
somebody tell Nat Friedman to stop taking trips overseas and blogging and
get his ass to work! http://nat.org/ and drag that aother guy Miguel de
Icaza http://primates.ximian.com/~miguel/gallery/ with him.
Seriously, traveling when they could be integrating NLD into a Netware
network at a speed that actually makes a difference. **** NCPFS does as
much for GNOME as NCL

James Tremblay wrote:
> {
> rant mode = on
> }
> Ok, Novell says that it wants to default with Gnome...
> I like to follow Novells lead,but this is getting a bit troubling,
> I was totally happy with KDE and got to know it quite easily. But....
> The Gnome is such a pretty simple thing and nice to use and will make a
> great Business class desktop unless:
> 1) you are a sophisticated power user with unusuall needs
> 2) you are a Netware administrator and want to assign file rights to
> network folders or files with novell file attributes
> 3) You want to configure your menu's to make life easier
> for you to do your job
> 4) You want to browse unmapped NSS based file systems
>
> this is why I'm posting, I can't figure out what exactly the
> Nautilus plugin for NCL actually does. It seems that there is no way to
> browse, I tried "network servers" in the internet section. I tried using
> nnetscannds:/ or nnetscannwsrv:/ all to no avail.
> Am I crazy or is the Gnome a little daft?
> Did I install something wroong?
> I have double checked and reintstalled the client with both red-carpet and
> the bash script.
> at this rate it will be NLD version 12 before I actually use this at work!
> and it's supposed to be a business class system.
> somebody tell Nat Friedman to stop taking trips overseas and blogging and
> get his ass to work! http://nat.org/ and drag that aother guy Miguel de
> Icaza http://primates.ximian.com/~miguel/gallery/ with him.
> Seriously, traveling when they could be integrating NLD into a Netware
> network at a speed that actually makes a difference. **** NCPFS does as
> much for GNOME as NCL
When I was using Gnome I just created a link to Konq and used that for my
netware file browsing and it worked fine. I even used a custom icon for it
that was a little screen with a red N in the middle of it...I eventually
moved over to KDE though after having numerous issues with gnome weirdness
with gnome-panels and the gnome-keyring. I got so frustrated one day after
making just a couple minor modifications to my desktop that I logged into
KDE and I haven't been back to gnome since...that was like 3 months ago.
Prior to that I had been using Gnome exclusively for years (since redhat 7
days) It cracks me up that Novell makes this big press announcement about
standardizing on Gnome but their client is sooo much better intergrated
with KDE. I don't get it either.

Chat SSDP Discovery flooding network killing all networking

I am having a huge issue with the latest version of iChat. When I start it up it sends out 10,000 to 20,000 SSDP requests to 239.255.255.250. If I shut down iChat it continues for about a minute then stops and everything is back to normal. Tried changing the ports.
We are using NAT on a Windows 2003 server.
This kills the network and no other network traffic happens.
When I run iChat at home it all works fine, without a problem. It is only when I am in the office.
My office setup is DHCP from a Windows 2003 R2 x64 server and all network traffic is routed through this server via NAT.
It has been working fine in the office for about a year and all three macs worked fine. Now all three have the same issue.
A network sniff with WireShark shows that my mac sends a MDNS query to 224.0.0.251 then to 10.x.x.x which is the server. but the one to the server is designated a malformated packet.
My mac then sends a SSDP request to 10.x.x.x
The server replies with an ICMP packet saying the port it not reachable
My mac then sends out another request to the server
Then it sends out a SSDP request to 239.255.255.250 and continues doing so killing the network.
This is part of the packet trace
Host:239.255.255.250:1900
ST:urn:schemas-upnp-org:service:WANIPConnection:1
Man:"ssdp:discover"

Hi Ralph
Thanks but no joy.
Some more background information:
When I run iChat at home it all works fine, without a problem. It is only when I am in the office.
My office setup is DHCP from a Windows 2003 R2 x64 server and all network traffic is routed through this server via NAT.
It has been working fine in the office for about a year and all three macs worked fine. Now all three have the same issue.
A network sniff with WireShark shows that my mac sends a MDNS query to 224.0.0.251 then to 10.x.x.x which is the server. but the one to the server is designated a malformated packet.
My mac then sends a SSDP request to 10.x.x.x
The server replies with an ICMP packet saying the port it not reachable
My mac then sends out another request to the server
Then it sends out a SSDP request to 239.255.255.250 and continues doing so killing the network.
This is part of the packet trace
Host:239.255.255.250:1900
ST:urn:schemas-upnp-org:service:WANIPConnection:1
Man:"ssdp:discover"

IChat SSDP Discovery flooding network killing all networking.

I am having a huge issue with the latest version of iChat. When I start it up it sends out 10,000 to 20,000 SSDP requests to 239.255.255.250. If I shut down iChat it continues for about a minute then stops and everything is back to normal. Tried changing the ports.
We are using NAT on a Windows 2003 server.
This kills the network and no other network traffic happens.
This has only just started in the last week.

Hi Ralph
Thanks but no joy.
Some more background information:
When I run iChat at home it all works fine, without a problem. It is only when I am in the office.
My office setup is DHCP from a Windows 2003 R2 x64 server and all network traffic is routed through this server via NAT.
It has been working fine in the office for about a year and all three macs worked fine. Now all three have the same issue.
A network sniff with WireShark shows that my mac sends a MDNS query to 224.0.0.251 then to 10.x.x.x which is the server. but the one to the server is designated a malformated packet.
My mac then sends a SSDP request to 10.x.x.x
The server replies with an ICMP packet saying the port it not reachable
My mac then sends out another request to the server
Then it sends out a SSDP request to 239.255.255.250 and continues doing so killing the network.
This is part of the packet trace
Host:239.255.255.250:1900
ST:urn:schemas-upnp-org:service:WANIPConnection:1
Man:"ssdp:discover"

[SOLVED] Kill the Gnome screen curtain once and for all

Author edit: you can see the fix that finally worked in post https://bbs.archlinux.org/viewtopic.php … 4#p1351594
I was inadvertently locked out of my own computer for about 10 minutes until I happened to stumble on the "Ctl + L" trick to bring up the login in screen. How can I remove or disable the gnome shell screen lock for good.
I already tried:
setting the "screen lock" to OFF under gnome setting > Privacy (gnome 3.10 appears to ignore this, or "screen lock" refers to something else)
the Disable Screen Shield extension - this has not been updated to gnome 3.10
Last edited by marko2010 (2013-11-19 18:04:06)

I think I finally found a way to disable the inactivity curtain in gnome 3.10. Launch dconf-editor then drill down org > gnome > desktop> session. Find the key for idle-delay and change it's value to 0 .
Or you can do it in once step by running the command:
gsettings set org.gnome.desktop.session idle-delay 0
Note you would think that going into the gnome control center and moving Privacy > Screen Lock to "OFF" would completely disable the screen curtain, but this never worked for me. The curtain would still come up after periods of inactivity, but would no longer ask for a password. Adding the fix above, completely gets rid of this pesky thing.

Windoze Ad-hoc networks killing Airport Extreme Base Station

After having a horrible experience with an Orinoco base station sometime ago at his coffee shop, a client of mine asked me to install a new Wi-Fi access point to replace it. Since I'd never had a problem with my graphite Airport Base Station, I selected recommended that he try the Airport Extreme. Everything was been fine for over a year and half, with only the occasional interference problem, and even that easily fixed by a restart on the base station. Lately that has changed. We're in Baton Rouge, and since Hurricane Katrina, our population in our city has doubled (that's not an exaggeration), and the number of customers using the network in his coffee shop has increased as well - although it's still well below the maximum. The problem is that there are is large number of students from Loyola, UNO and Tulane who are now attending LSU, right across the street. And a significant fraction of those have ad-hoc networks set up on their Windoze notebooks, apparently unintentionally. When they come into the coffee shop their ad-hoc networks seems to cause the Airport Extreme to die, and not recover, until it is reset. This happens many times per day, sometimes more than once in an hour.
It had been configured to automatically select a channel, but I re-configured to use a specific channel (and have been experimenting with the particular channel). It seems to reduce the problem for a time, but then we'll have the problem back in force within a few days.
I have verified (using iStumbler) that there are no other "managed" networks near-by, and I have noticed that the problem ALWAYS happens when there is are ad-hoc networks, and after politely asking customers if I can check their settings, (it's scary how many people will let you poke around on their computer, if you seem like you know what you're doing) I've also seen compelling evidence that it is Windoze users, not Mac users, who tend to cause the problem. Incidentally at this particular coffee shop the Windoze:Mac ration is something like 60:40. What can I say, it attracts discerning customers. Since some of them have "lsuwireless" set up as an ad-hoc network (and as I said, LSU is across the street), my guess is that somehow these get set up, not on purpose, but accidentally, while trying to connect to the university's wireless network. Apparently the process is not so straight forward for Windoze users as for Mac users.
I have upgraded the Airport Base Station software to the latest available as of last week. Though I don't have that version number available at the moment.
So I have several questions:
1) Is this really the same radio interference problem that I've read about elsewhere on this discussion board?
2) Would an external antenna on the base station help? How about a powered one?
3) Aside from "Use Interference Robustness" and trying different channels, is there some configuration setting that I might be missing that could enhance the base station's reliability?
4) Does anyone have a suggestion for a permanent fix - preferably without switching to a different access point, although at this point, that's a viable alternative. After a year and a half of stable operation though, we're loathe to switch again unless it can't be avoided, because the Orinoco access point we used before had behaved exactly like this, but even worse, and without necessarily having ad-hoc networks being present to cause the problem.
5) Failing any other good solution, can anyone suggest a way to determine which computers are causing the problem without having to interrupt each customer to poke around on his computer?

I have an Intel based iMac and a MacBook Pro. Both
are (well until tonight) connected to the internet
wirelessly through the Airport Extreme Base station.
I've had no trouble up until now. Tonight for some
odd reason the MacBook Pro Airport card fails to
detect the Airport Extreme Base Station. It detects
OTHER wireless networks around the building, just
not the one it's supposed to connect to. Opening up
Airport Utility doesn't even show the Airport
Extreme Base Station being present. I know the Base
Station is not at fault - it works fine with the
iMac. Tried setting the Sharing mode on but that
didn't help either (not that I changed any of the
settings to begin with).
Can anyone help? I'm really at a loss here.
Any one? Any suggestions?

Extending the Network kills speed performance, would bridging do the same?

I have a Time Capsule in my basement and upstairs I have a very hard time getting a good wireless signal.
I decided to buy an Airport Express to try and solve the problem. I tried to extend the network with the AX and now my computer upstairs can get a good wireless signal, however the performance has dropped significantly. When I run a speed test on both my upstairs computer and my laptop downstairs I now get about 1.5 Mbit down/1 MBit up which is much worse than what i used to get (10-14 MBit down/2 MBit up).
If I were to hook the AX up to an ethernet port in my house (should be activated in the next few days which is why I can't try it now) and have the AX set up to work in bridge mode, would this improve the performance? I thought I read somewhere that extending the network could hurt performance (which I'm certainly seeing), but I don't know if that would apply to bridge mode.
Thanks for the help.

The way I understand it -
You're effectively doubling the network traffic - everything has to make 2 hops. The "extension" receives the data and has to re-transmit it to the main base station. Receiving, processing and re-transmitting takes time.
In reality, traffic can be much more than doubled. If the message from the computer is received by both the extension and the base station, and then again by the base station when the extension re-transmits it, the base station has to work out that it has received the data twice. This extra processing (ignoring duplicates) takes time.
With more data on the network, there's more chance of "collisions", so more re-transmits.
I think it's pretty amazing that it works at all!

Gnome-network-manager shouldn't require Gnome?

According to its page on Gnomefiles, network-manager-applet (gnome-network-manager on Arch) doesn't need Gnome deps.
Maybe it would be a good idea to include a version that isn't compiled for Gnome in Extra, so that people using E17 or XFCE or whatever can easily use networkmanager? If people think this is practical I'll file a feature request...

Gullible Jones wrote:According to its page on Gnomefiles, network-manager-applet (gnome-network-manager on Arch) doesn't need Gnome deps.
It does need gnome deps. Requires libgnomegui and gnome-keyring... in turn it also uses gconf and other things. These can't be disabled.
James

Is Killer Network actually Killing My Network?

Hello All,
I have been running into issues this past week after a recent computer build. One of my computers either is having Video Card Issues, or Network Issues.
I have a "Lan Center" that I have built over the years in my basement. Ever since the early Beta Counterstrike days I have always ran more than 1 computer in my household. Most of my friends are broke hippies, but I work in IT and enjoy playing once in a while.
The Game : GTA V for PC
The Problem : When going high speeds in vehicles, or when in big online lobby's. The framerate either drops (I don't know how to monitor FPS on this game as of yet) or my network is dying. On the other two PC's when in a private lobby, I can watch this PC lag in game. It will start off fine, but jump in a Bugatti, and it all goes to hell.
The Hardware :
Computer 1 -
CPU -i7-5820K (No OC)
Video - EVGA GTX 970 (No OC)
Mobo - ASRock X99X
HDD - Samsung 850 Pro 512gb
Ram - Crucial 16GB DDR4
PSU - Corsair AX760
CPU Cooler - Corsair H75
Sound - Creative SB ZxR
Case - NZXT H440
OS - Win 7 64bit Pro
Computer 2 -
MSI GT60 20D-026US Laptop
CPU - i7 4700MQ (No OC)
Video - GTX 780m (No OC)
HDD - Samsung 840 EVO 500gb
Ram - 16GB DDR3
OS - Win 8.1 64bit
Computer 3 -
CPU - i7-4790K (No OC)
Video - Radeon HD7870 (No OC)
Mobo - MSI Z97-GD65
HDD - WD Black 1TB
Ram - Kingston 8GB DDR3
PSU - EVGA 750G2
CPU Cooler - Stock
Case - NZXT H440
OS - Win 7 64bit Pro
Network Equipment -
Connection - Comcast 50/10
Modem - Motorola SB6121
Router - Netgear N750
Troubleshooting : I have already updated all of the drivers for the current hardware. I have already ran ALL windows updates. I have already ran Speccy on the culprit pc (Computer 3). All idle temps are fine, I left it running while running the game and all temps appear to be fine then as well. What I don't understand is the network graph, while in game it shows HUGE spikes and inconsistency. Thinking it could be a network cable, I replaced it with a new one. I just don't understand why this computer would spike and the other two don't. Another possibility is, when building this computer, it was basically a swap from my main computer. I never uninstalled the drivers for my GTX 970, so I guess there is a possibility that that is causing the video issue. All have Killer NIC cards. So stands my question. Is Killer Network, killing my network? Any help would be greatly appreciated. Also, any tips on buffing up my network would be great as well. Thanks in advance!

I am with JLio01 on this. Try the Killer Network driver without the application and see if that fixes the issue.
There is not really any reason that it should lag like that.

Network Manager (GNOME 3.8.x) disconnecting

Hi,
I have a problem with the Network Manager for Gnome 3.8.2 on my laptop - I've tried to have it connect to my network broadband but the problem is it keeps disconnecting - even the ethernet cable on the laptop. Is the Network Manager for gnome at it's latest version if not could it be updated! Is anyone else having the same problem?

I'm also traped in this trouble. Did you resolve this problem?
I've noticed that this annoying error started after I've installed the network manager and network manager applet in gnome.
And I cannot remove network manage and the applet cause gnome now depends on it. What a stupid error.
Thanks in advance.
Last edited by victordfb (2013-10-29 12:20:21)

Network killed by Gnome

Similar Messages

Maybe you are looking for