[Expired for linux (Ubuntu) because there has been no activity for 60
days.]
** Changed in: linux (Ubuntu)
Status: Incomplete => Expired
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1027202
T
Syafix Said, it will help immensely if you filed a new report with the Ubuntu
repository kernel (not mainline/upstream) via a terminal:
ubuntu-bug linux
Please feel free to subscribe me to it.
For more on why this is helpful, please see
https://wiki.ubuntu.com/ReportingBugs.
** This bug is no l
*** This bug is a duplicate of bug 1184262 ***
https://bugs.launchpad.net/bugs/1184262
i'm using ubuntu 16.10, after suspend / sleep the notebook, then can't connect
to wireless.
the only things is i can do is kill the nm-applet using System Monitor then run
nm-applet again.
the wireless lis
*** This bug is a duplicate of bug 1184262 ***
https://bugs.launchpad.net/bugs/1184262
Christopher, I (a) didn't know quite how to comment on your comment #25
above, (b) had unclear results for a few days, and (c) was off on other
matters.
However, today I downloaded the new patch by Martin P
*** This bug is a duplicate of bug 1184262 ***
https://bugs.launchpad.net/bugs/1184262
Kai Mast, if you have a problem in Trusty, please file a new report via a
terminal:
ubuntu-bug linux
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to U
*** This bug is a duplicate of bug 1184262 ***
https://bugs.launchpad.net/bugs/1184262
Imo this is not a duplicate. The other bug is marked as fixed in trusty
but I still have this problem -- also in trusty.
Sometimes I also need to restart nm-applet to reconnect.
--
You received this bug n
*** This bug is a duplicate of bug 1184262 ***
https://bugs.launchpad.net/bugs/1184262
Marius Hofert, could you please confirm this issue exists with the
latest development release of Ubuntu? ISO images are available from
http://cdimage.ubuntu.com/daily-live/current/ . If the issue remains,
co
*** This bug is a duplicate of bug 1184262 ***
https://bugs.launchpad.net/bugs/1184262
** This bug has been marked a duplicate of bug 1184262
[logind] times out too early, stuck in PrepareForSleep, causing network and
other services to not resume
--
You received this bug notification bec
A .Richard Miller, it would be most helpful if you file a new report in a
terminal so that your hardware may be reviewed:
ubuntu-bug linux
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1027202
Title:
Sorry; this replaces my messages #22 and #23.
Hi, Chris and All:
Great that this bug is active again!
My computer and my FOSS User Group use of Ubuntu are still limping with
this failing Suspend (since a late beta of Saucy; see messages #10, 11,
and 14 above), so I await a fix and invite you to
Corrected version of "these further observations", above:
1. In a new session, Suspend will fail with any of the following: with the
closing of the lid, or by clicking on the Power button (in upper right of top
bar) > Suspend, or by a Suspend time-out.
2. "sudo restart network-manager" will repai
Hi, Chris and All:
Great that this bug is active again!
My computer and my FOSS User Group use of Ubuntu are still limping with
this failing Suspend (since a late beta of Saucy; see messages #10, 11,
and 14 above), so I await a fix and invite you to ask when I can be of
further help.
And, these
Horst Schirmeier, if you have a bug in Ubuntu, the Ubuntu Kernel team, Ubuntu
Bug Control team, and Ubuntu Bug Squad would like you to please file a new
report by executing the following in a terminal while booted into a Ubuntu
repository kernel (not a mainline one) via:
ubuntu-bug linux
For mo
This issue disables both wired and wireless connections, and it only
happens about every second suspend/resume cycle on my machine. For the
remaining cycles, networking comes back up fine after resume.
If the original bug reporter does not reply, I'm willing to follow the
testing instructions Chri
Peng, if you have a bug in Ubuntu, the Ubuntu Kernel team, Ubuntu Bug Control
team, and Ubuntu Bug Squad would like you to please file a new report by
executing the following in a terminal while booted into a Ubuntu repository
kernel (not a mainline one) via:
ubuntu-bug linux
For more on this,
Just for some input I have tested the mainline 3.8 kernel under saucy
and the problem still occurs. Since I didn't have this problem in raring
so maybe it's not kernel bug.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.l
Marius Hofert, could you please confirm this issue exists with the
latest development release of Ubuntu? ISO images are available from
http://cdimage.ubuntu.com/daily-live/current/ . If the issue remains,
could you please run the following command in the development release
from a Terminal (Applica
This happens to me on saucy on two computers fairly often and a third
seldomly.
The first system with the problem has a:
03:00.0 Ethernet controller: Marvell Technology Group Ltd. 88E8056 PCI-E
Gigabit Ethernet Controller (rev 14)
The other system has:
02:00.0 Ethernet controller: Realtek Semic
I'm seeing this on saucy, too. "service network-manager restart" fixes
the problem. I'm using a Dell Latitude E6400 with iwlwifi.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1027202
Title:
Does no
Thanks, panther_d. Much appreciated!
I'd considered doing something like that. But, like you, I want Saucy
Salamander to "just work" for casual users of Ubuntu. Rather than
featuring this bug, I'm delaying introducing Saucy Salamander to our
clients and my FOSS User Group (NatickFOSS.org).
I hope
I have a workaround that isn't particularly elegant but does the trick
for me: have the NetworkManager automatically restart at resume.
1. add file to /etc/pm/sleep.d/ , e.g. call it 99_restart-network-manager, and
make it executable
2. in the file, put
#!/bin/bash
case "${1}" in
resume|th
Got the same issue after updating to Saucy yesterday.
Restarting NetworkManager helps, but that's not a real option especially
for non-computer-literate users...
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.n
Drat! My "permanent fix" was working while I resumed operation within a
few seconds after the Suspend LED began blinking. But several minutes of
Suspend is enough to derail it, requiring another application of "sudo
restart network-manager".
So, add me (and Saucy on an Acer AO722) to the list of t
Thank you! This solved my problem permanently - at least, for today. :-)
Using Saucy (64-bit Ubuntu Desktop 13.10 beta2) with daily updates, my
Acer AO722 notebook computer had been networking well after suspending
by closing its lid - until something changed less than a week ago.
Beginning then,
I still have this problem in saucy.
It says "triaged" but the bug is assigned to know one. Is anybody
working on this? Do you need any more information?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1
I forgot to add all I have to do on saucy to fix the problem is service
network-manager restart like Kai Mast as well. It appears to happen
every time I suspend.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.ne
The following just happened to me.
Suspend/resume -> network manager broke (as expected)
Suspend/resume a second time -> network manager works again
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/10272
Alberto, no I am using a self build pc and a lenovo thinkpad edge.
This seems to be independent of the hardware
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1027202
Title:
Does not connect (to wir
I'm also seeing this on saucy on a gigabyte ga-965p-dq6 motherboard with
a marvell 88e8056 gige controller.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1027202
Title:
Does not connect (to wired ne
Kai Mast, are you using a MacBookAir too?
** Changed in: network-manager (Ubuntu)
Importance: Undecided => High
** Changed in: network-manager (Ubuntu)
Status: Confirmed => Triaged
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ub
I have a similar issue in saucy on both of my machines.
"sudo restart network-manager" fixes the problem for me.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1027202
Title:
Does not connect (to wi
Status changed to 'Confirmed' because the bug affects multiple users.
** Changed in: network-manager (Ubuntu)
Status: New => Confirmed
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1027202
Tit
** Tags added: saucy
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1027202
Title:
Does not connect (to wired network) after suspend
To manage notifications about this bug go to:
https://bugs.launch
33 matches
Mail list logo
