epileptic network [on hold]
I am a new Kubuntu user coming from close to 15 years of Opensuse. I'm currently using disco dingo from an upgrade of cosmic. Everything is fine with the exception of my network.
I mentioned the upgrade so that you won't think the upgrade caused my problem because the problem was there from when I first installed 18.10
My problem is that my network settings have a mind of their own. Sometimes, I boot and everything is ok for a while then the network,both lan and wireless, just stops working with no error and no change of configuration. Everything looks fine but I just can't reach any machine on my network nor can I reach the Internet.
Other times I'll have to boot many times before all is well. But still after some minutes, network stops working.
At first I thought it was netplan, which is extremely temperamental. So I switched to networking which had the same result. So I finally went to old faithful from my opensuse days. NetworkManager. But still the same result.
As it stands now, I want to stay with NetworkManager. I have uninstalled netplan and my interface file is empty and networking is disabled. Only NetworkManager is enabled under systemd. I have a good NetworkManager configuration with settings for my lan and wireless. This is virtually the same network setup I had on this same laptop with opensuse. But still the network just stops working whenever it feels like it.
Can anyone give me a clue as to what it might be? BTW, I have another machine that also has the same setup (18.10 though) and there is no problem there. The only difference is that it is not a laptop.
Any help would be appreciated as I'm close to pulling out my hair if that was possible seeing that I'm bald.
Thanks in advance
iomari
networking
asked yesterday
Ibrahim Salim OmariIbrahim Salim Omari
1
New contributor
Ibrahim Salim Omari is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
Check out our Code of Conduct.
put on hold as off-topic by guiverc, DK Bose, karel, N0rbert, Eric Carvalho yesterday
This question appears to be off-topic. The users who voted to close gave this specific reason:
- "Bug reports and problems specific to development version of Ubuntu should be reported on Launchpad so that developers can see, track and fix these issues." – guiverc, DK Bose, karel, N0rbert, Eric Carvalho
If this question can be reworded to fit the rules in the help center, please edit the question.
add a comment |
I am a new Kubuntu user coming from close to 15 years of Opensuse. I'm currently using disco dingo from an upgrade of cosmic. Everything is fine with the exception of my network.
I mentioned the upgrade so that you won't think the upgrade caused my problem because the problem was there from when I first installed 18.10
My problem is that my network settings have a mind of their own. Sometimes, I boot and everything is ok for a while then the network,both lan and wireless, just stops working with no error and no change of configuration. Everything looks fine but I just can't reach any machine on my network nor can I reach the Internet.
Other times I'll have to boot many times before all is well. But still after some minutes, network stops working.
At first I thought it was netplan, which is extremely temperamental. So I switched to networking which had the same result. So I finally went to old faithful from my opensuse days. NetworkManager. But still the same result.
As it stands now, I want to stay with NetworkManager. I have uninstalled netplan and my interface file is empty and networking is disabled. Only NetworkManager is enabled under systemd. I have a good NetworkManager configuration with settings for my lan and wireless. This is virtually the same network setup I had on this same laptop with opensuse. But still the network just stops working whenever it feels like it.
Can anyone give me a clue as to what it might be? BTW, I have another machine that also has the same setup (18.10 though) and there is no problem there. The only difference is that it is not a laptop.
Any help would be appreciated as I'm close to pulling out my hair if that was possible seeing that I'm bald.
Thanks in advance
iomari
networking
asked yesterday
Ibrahim Salim OmariIbrahim Salim Omari
1
New contributor
Ibrahim Salim Omari is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
Check out our Code of Conduct.
put on hold as off-topic by guiverc, DK Bose, karel, N0rbert, Eric Carvalho yesterday
This question appears to be off-topic. The users who voted to close gave this specific reason:
- "Bug reports and problems specific to development version of Ubuntu should be reported on Launchpad so that developers can see, track and fix these issues." – guiverc, DK Bose, karel, N0rbert, Eric Carvalho
If this question can be reworded to fit the rules in the help center, please edit the question.
1
Possible off-topic question. Ubuntu 19.04 (disco) is off-topic on this site until it's release in 2019.April. Please refer to askubuntu.com/help/on-topic and ask on a site or method that supports Ubuntu+1 (such as #ubuntu+1 on freenode). To get help here, you should have asked back when you were using 18.10 or a supported release of Ubuntu.
– guiverc
yesterday
This has nothing to do with disco. I already explained this problem was there before the upgrade.
– Ibrahim Salim Omari
yesterday
2
And if you were still using 18.10, you'd be on a supported release (instead of a development release) and on-topic for this site. I'm using 19.04 myself, but know it's off-topic on this site and I can't ask questions about my chosen-Ubuntu using this site.
– guiverc
yesterday
fyi: assuming you don't have another OS installed, I'd boot an unrelated distro in 'live' mode & have it tested awhile. Your description reminds me of a failing component (ie. do a cap-check) and not software. I'd also look at what [kernel] modules (drivers) you are using for your hardware if the test was reliable, and check your (k)ubuntu is using the same (or add/change them).
– guiverc
yesterday
add a comment |
I am a new Kubuntu user coming from close to 15 years of Opensuse. I'm currently using disco dingo from an upgrade of cosmic. Everything is fine with the exception of my network.
I mentioned the upgrade so that you won't think the upgrade caused my problem because the problem was there from when I first installed 18.10
My problem is that my network settings have a mind of their own. Sometimes, I boot and everything is ok for a while then the network,both lan and wireless, just stops working with no error and no change of configuration. Everything looks fine but I just can't reach any machine on my network nor can I reach the Internet.
Other times I'll have to boot many times before all is well. But still after some minutes, network stops working.
At first I thought it was netplan, which is extremely temperamental. So I switched to networking which had the same result. So I finally went to old faithful from my opensuse days. NetworkManager. But still the same result.
As it stands now, I want to stay with NetworkManager. I have uninstalled netplan and my interface file is empty and networking is disabled. Only NetworkManager is enabled under systemd. I have a good NetworkManager configuration with settings for my lan and wireless. This is virtually the same network setup I had on this same laptop with opensuse. But still the network just stops working whenever it feels like it.
Can anyone give me a clue as to what it might be? BTW, I have another machine that also has the same setup (18.10 though) and there is no problem there. The only difference is that it is not a laptop.
Any help would be appreciated as I'm close to pulling out my hair if that was possible seeing that I'm bald.
Thanks in advance
iomari
networking
asked yesterday
Ibrahim Salim OmariIbrahim Salim Omari
1
New contributor
Ibrahim Salim Omari is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
Check out our Code of Conduct.
I am a new Kubuntu user coming from close to 15 years of Opensuse. I'm currently using disco dingo from an upgrade of cosmic. Everything is fine with the exception of my network.
I mentioned the upgrade so that you won't think the upgrade caused my problem because the problem was there from when I first installed 18.10
My problem is that my network settings have a mind of their own. Sometimes, I boot and everything is ok for a while then the network,both lan and wireless, just stops working with no error and no change of configuration. Everything looks fine but I just can't reach any machine on my network nor can I reach the Internet.
Other times I'll have to boot many times before all is well. But still after some minutes, network stops working.
At first I thought it was netplan, which is extremely temperamental. So I switched to networking which had the same result. So I finally went to old faithful from my opensuse days. NetworkManager. But still the same result.
As it stands now, I want to stay with NetworkManager. I have uninstalled netplan and my interface file is empty and networking is disabled. Only NetworkManager is enabled under systemd. I have a good NetworkManager configuration with settings for my lan and wireless. This is virtually the same network setup I had on this same laptop with opensuse. But still the network just stops working whenever it feels like it.
Can anyone give me a clue as to what it might be? BTW, I have another machine that also has the same setup (18.10 though) and there is no problem there. The only difference is that it is not a laptop.
Any help would be appreciated as I'm close to pulling out my hair if that was possible seeing that I'm bald.
Thanks in advance
iomari
networking
networking
asked yesterday
Ibrahim Salim OmariIbrahim Salim Omari
1
New contributor
Ibrahim Salim Omari is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
Check out our Code of Conduct.
asked yesterday
Ibrahim Salim OmariIbrahim Salim Omari
1
New contributor
Ibrahim Salim Omari is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
Check out our Code of Conduct.
asked yesterday
Ibrahim Salim OmariIbrahim Salim Omari
1
New contributor
Ibrahim Salim Omari is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
Check out our Code of Conduct.
asked yesterday
Ibrahim Salim OmariIbrahim Salim Omari
1
asked yesterday
Ibrahim Salim OmariIbrahim Salim Omari
1
1
New contributor
Ibrahim Salim Omari is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
Check out our Code of Conduct.
New contributor
Ibrahim Salim Omari is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
Check out our Code of Conduct.
Ibrahim Salim Omari is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
Check out our Code of Conduct.
put on hold as off-topic by guiverc, DK Bose, karel, N0rbert, Eric Carvalho yesterday
This question appears to be off-topic. The users who voted to close gave this specific reason:
- "Bug reports and problems specific to development version of Ubuntu should be reported on Launchpad so that developers can see, track and fix these issues." – guiverc, DK Bose, karel, N0rbert, Eric Carvalho
If this question can be reworded to fit the rules in the help center, please edit the question.
put on hold as off-topic by guiverc, DK Bose, karel, N0rbert, Eric Carvalho yesterday
This question appears to be off-topic. The users who voted to close gave this specific reason:
- "Bug reports and problems specific to development version of Ubuntu should be reported on Launchpad so that developers can see, track and fix these issues." – guiverc, DK Bose, karel, N0rbert, Eric Carvalho
If this question can be reworded to fit the rules in the help center, please edit the question.
1
Possible off-topic question. Ubuntu 19.04 (disco) is off-topic on this site until it's release in 2019.April. Please refer to askubuntu.com/help/on-topic and ask on a site or method that supports Ubuntu+1 (such as #ubuntu+1 on freenode). To get help here, you should have asked back when you were using 18.10 or a supported release of Ubuntu.
– guiverc
yesterday
This has nothing to do with disco. I already explained this problem was there before the upgrade.
– Ibrahim Salim Omari
yesterday
2
And if you were still using 18.10, you'd be on a supported release (instead of a development release) and on-topic for this site. I'm using 19.04 myself, but know it's off-topic on this site and I can't ask questions about my chosen-Ubuntu using this site.
– guiverc
yesterday
fyi: assuming you don't have another OS installed, I'd boot an unrelated distro in 'live' mode & have it tested awhile. Your description reminds me of a failing component (ie. do a cap-check) and not software. I'd also look at what [kernel] modules (drivers) you are using for your hardware if the test was reliable, and check your (k)ubuntu is using the same (or add/change them).
– guiverc
yesterday
add a comment |
1
Possible off-topic question. Ubuntu 19.04 (disco) is off-topic on this site until it's release in 2019.April. Please refer to askubuntu.com/help/on-topic and ask on a site or method that supports Ubuntu+1 (such as #ubuntu+1 on freenode). To get help here, you should have asked back when you were using 18.10 or a supported release of Ubuntu.
– guiverc
yesterday
This has nothing to do with disco. I already explained this problem was there before the upgrade.
– Ibrahim Salim Omari
yesterday
2
And if you were still using 18.10, you'd be on a supported release (instead of a development release) and on-topic for this site. I'm using 19.04 myself, but know it's off-topic on this site and I can't ask questions about my chosen-Ubuntu using this site.
– guiverc
yesterday
fyi: assuming you don't have another OS installed, I'd boot an unrelated distro in 'live' mode & have it tested awhile. Your description reminds me of a failing component (ie. do a cap-check) and not software. I'd also look at what [kernel] modules (drivers) you are using for your hardware if the test was reliable, and check your (k)ubuntu is using the same (or add/change them).
– guiverc
yesterday
1
1
Possible off-topic question. Ubuntu 19.04 (disco) is off-topic on this site until it's release in 2019.April. Please refer to askubuntu.com/help/on-topic and ask on a site or method that supports Ubuntu+1 (such as #ubuntu+1 on freenode). To get help here, you should have asked back when you were using 18.10 or a supported release of Ubuntu.
– guiverc
yesterday
Possible off-topic question. Ubuntu 19.04 (disco) is off-topic on this site until it's release in 2019.April. Please refer to askubuntu.com/help/on-topic and ask on a site or method that supports Ubuntu+1 (such as #ubuntu+1 on freenode). To get help here, you should have asked back when you were using 18.10 or a supported release of Ubuntu.
– guiverc
yesterday
This has nothing to do with disco. I already explained this problem was there before the upgrade.
– Ibrahim Salim Omari
yesterday
This has nothing to do with disco. I already explained this problem was there before the upgrade.
– Ibrahim Salim Omari
yesterday
2
2
And if you were still using 18.10, you'd be on a supported release (instead of a development release) and on-topic for this site. I'm using 19.04 myself, but know it's off-topic on this site and I can't ask questions about my chosen-Ubuntu using this site.
– guiverc
yesterday
And if you were still using 18.10, you'd be on a supported release (instead of a development release) and on-topic for this site. I'm using 19.04 myself, but know it's off-topic on this site and I can't ask questions about my chosen-Ubuntu using this site.
– guiverc
yesterday
fyi: assuming you don't have another OS installed, I'd boot an unrelated distro in 'live' mode & have it tested awhile. Your description reminds me of a failing component (ie. do a cap-check) and not software. I'd also look at what [kernel] modules (drivers) you are using for your hardware if the test was reliable, and check your (k)ubuntu is using the same (or add/change them).
– guiverc
yesterday
fyi: assuming you don't have another OS installed, I'd boot an unrelated distro in 'live' mode & have it tested awhile. Your description reminds me of a failing component (ie. do a cap-check) and not software. I'd also look at what [kernel] modules (drivers) you are using for your hardware if the test was reliable, and check your (k)ubuntu is using the same (or add/change them).
– guiverc
yesterday
add a comment |
0
active
oldest
votes
0
active
oldest
votes
0
active
oldest
votes
active
oldest
votes
active
oldest
votes
1
Possible off-topic question. Ubuntu 19.04 (disco) is off-topic on this site until it's release in 2019.April. Please refer to askubuntu.com/help/on-topic and ask on a site or method that supports Ubuntu+1 (such as #ubuntu+1 on freenode). To get help here, you should have asked back when you were using 18.10 or a supported release of Ubuntu.
– guiverc
yesterday
This has nothing to do with disco. I already explained this problem was there before the upgrade.
– Ibrahim Salim Omari
yesterday
2
And if you were still using 18.10, you'd be on a supported release (instead of a development release) and on-topic for this site. I'm using 19.04 myself, but know it's off-topic on this site and I can't ask questions about my chosen-Ubuntu using this site.
– guiverc
yesterday
fyi: assuming you don't have another OS installed, I'd boot an unrelated distro in 'live' mode & have it tested awhile. Your description reminds me of a failing component (ie. do a cap-check) and not software. I'd also look at what [kernel] modules (drivers) you are using for your hardware if the test was reliable, and check your (k)ubuntu is using the same (or add/change them).
– guiverc
yesterday