still present in Xenial
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1184262
Title:
times out too early, stuck in PrepareForSleep, causing network and
other services to not resume
To manage
** Changed in: systemd-shim (Ubuntu Trusty)
Milestone: ubuntu-13.11 => None
** No longer affects: systemd (Ubuntu Trusty)
** No longer affects: systemd (Ubuntu Saucy)
** No longer affects: systemd (Ubuntu)
--
You received this bug notification because you are a member of Ubuntu
Bugs,
There's no need to file another bug report, it will only be marked as a
duplicate. This bug has not been fixed for everyone and continues on here:-
https://bugs.launchpad.net/ubuntu/+source/systemd-shim/+bug/1252121
--
You received this bug notification because you are a member of Ubuntu
Bugs,
I am on Ubuntu 14.04 and am still experiencing this issue.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1184262
Title:
times out too early, stuck in PrepareForSleep, causing network and
other
Chris Morris, if you are experiencing an issue still, then this bug
report had nothing to do with your problem. Please file a new report.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1184262
Title:
I got the problem with sleeping network again. This time I'm
absolutely sure I wasn't doing anything that could provoke the sleep.
The computer was with the lid closed, HDMI connected to the external
monitor. I left for lunch. When I returned. the network was sleeping,
the crescent shaped LED on
** Information type changed from Public to Public Security
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1184262
Title:
times out too early, stuck in PrepareForSleep, causing network and
other
** Information type changed from Public Security to Public
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1184262
Title:
times out too early, stuck in PrepareForSleep, causing network and
other
@ madmin314:
If you are sure this is a security bug, please:
1. Explain why do you think so.
2. Mark it as Public Security again.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1184262
Title:
I'm on fully up-to-date Ubuntu 14.04 with the latest kernel
3.13.0-36-generic, and I got this error. I have a Lenovo ThinkPad W530.
I use it either with the internal monitor or with an external monitor
connected to displayport. I don't remember what I did today. I think I
connected the display
Have somebody tried to install the latests kernel versions? Will it fix
the trouble?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1184262
Title:
times out too early, stuck in PrepareForSleep,
This bug exists in 14.04. I can manually reconnect to wireless by typing
sudo service network-manager restart
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1184262
Title:
times out too early,
Joao Natali / Carlos A., please do not add bug tasks nor apport collect to this
report, as it is closed. If you are having a bug in Ubuntu, so your hardware
and problem may be tracked, could you please file a new report with Ubuntu by
executing the following in a terminal while booted into a
Christopher M. Penalver, Carlos A., there is already a continuation of
this bug #1252121.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1184262
Title:
times out too early, stuck in PrepareForSleep,
** Also affects: linux (Ubuntu)
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1184262
Title:
times out too early, stuck in PrepareForSleep, causing
ApportVersion: 2.14.1-0ubuntu3
Architecture: amd64
AudioDevicesInUse:
USERPID ACCESS COMMAND
/dev/snd/controlC0: cif2063 F pulseaudio
CurrentDesktop: Unity
DistroRelease: Ubuntu 14.04
HibernationDevice: RESUME=UUID=78205ef1-1270-4794-b8c5-647151a38a07
InstallationDate:
In latest version of Ubuntu 14.04 this bug not fixed!
I can't enable wireless networking after my laptop resumed from suspend.
p.s. suspend turning with some errors too:
1) It take more time (in Ubuntu 12.04 laptop suspend faster)
2) before display turns off and laptop become full suspended -
Bug report here:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1295285
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1184262
Title:
times out too early, stuck in PrepareForSleep, causing
Daniel Lombraña González, Please see
https://bugs.launchpad.net/ubuntu/+source/systemd-
shim/+bug/1184262/comments/151 .
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1184262
Title:
times out too
This bugs keeps affecting me even with the latest version. Can I do
something to get this fixed?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1184262
Title:
times out too early, stuck in
** Changed in: systemd-shim (Ubuntu Trusty)
Assignee: Gruia Catalin (catalynn-nr1) = (unassigned)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1184262
Title:
times out too early, stuck in
I still have this issue. The system is up-to-date.
My network controller:
44:00.0 Network controller: Broadcom Corporation BCM4312 802.11b/g LP-PHY (rev
01)
Linux kernel:
Linux stant-laptop 3.11.0-14-generic #21-Ubuntu SMP Tue Nov 12 17:07:40 UTC
2013 i686 i686 i686 GNU/Linux
Package
Anton Statutov, if you still have this issue, than this report doesn't cover
your problem as it is marked Fix Released. Please file a new report via a
terminal:
ubuntu-bug systemd-shim
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
Andon: Please see https://bugs.launchpad.net/ubuntu/+source/systemd-
shim/+bug/1184262/comments/151
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1184262
Title:
times out too early, stuck in
This bug was fixed in the package systemd-shim - 4-0ubuntu0.13.10
---
systemd-shim (4-0ubuntu0.13.10) saucy-proposed; urgency=low
* New upstream release:
- Flush bus before exiting on idle to avoid a race where a message is
queued up but not yet sent. (LP: #1184262, part
** Changed in: systemd-shim (Ubuntu Saucy)
Assignee: Martin Pitt (pitti) = (unassigned)
** Changed in: systemd-shim (Ubuntu Trusty)
Assignee: Martin Pitt (pitti) = Gruia Catalin (catalynn-nr1)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is
For the record: anyone who is still affected by this particular symptom
(network not coming up after suspend), please subscribe to and have a
look at bug 1252121. I put a fix into my
https://launchpad.net/~pitti/+archive/sru-test PPA (systemd-shim version
5-0ubuntu0.0pitti1). This is the only
This doesn't make it worse for me, it makes it better, but it still
doesn't completely solve the network failing to resume problem. As with
the first patch I get a failure rate of around 1 in 30. I've tried
suspending 30 times in 3 different ways: using the lid, using sudo pm-
suspend and the menu
As for me, that completely fixes the problem. Thanks!
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1184262
Title:
times out too early, stuck in PrepareForSleep, causing network and
other
Hello Catalin,
thanks for your feedback!
Catalin Hritcu [2013-11-19 8:17 -]:
lid: | X
pm-suspend: | |
menu/power button: | |
Interesting, thanks for pointing that out. If it can be confirmed that
this now only happens if you close the lid, then this indeed
I'll try this experiment and report in the next 24 hours then. It takes
quite a bit, and I'll try to get a larger number of repeats.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1184262
Title:
I don't have the time to repeat the experiments, however in my case it
seems to be pretty deterministic: None of the suggested ways works
(menu, pm-suspend, the other command or lid-close, which i usually do).
--
You received this bug notification because you are a member of Ubuntu
Bugs, which
Philipp Keck [2013-11-19 10:11 -]:
I don't have the time to repeat the experiments, however in my case it
seems to be pretty deterministic: None of the suggested ways works
(menu, pm-suspend, the other command or lid-close, which i usually do).
If even sudo pm-suspend does not work, then
The fix in -proposed repo makes the situation much better for me. Both
my desktop and netbook, which were hitting the bug every suspend, now
show it only occasionally -- as in, it may happen once every few days.
I presume that's from a different cause so I'll try to get logs for bug
#1252121 next
Thanks everyone for testing and your patience! We got sufficiently many
verification results now. Let's move this to -updates after the 7 days
are over, and close this bug report which already got way out of hand.
Remaining network failures after resume should be discussed on bug
1252121, I left
Can we please get some more people to test this, so that this can be
released into -updates soon? Both it fixed my problem and I still
have the problem, but the update does not make it worse are
appreciated. And of course, if this update makes it worse, this would be
a showstopper and we
As per comment #140, I have submitted a new bug #1252121 with Dbus
logging.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1184262
Title:
times out too early, stuck in PrepareForSleep, causing
Rafael Levi [2013-11-15 19:44 -]:
I understand that it's difficult to deal with several bugs that look the
same. Before I file a new bug. Is there anything I can do to distinguish
the bug I have from the solve one?
For one, if the -proposed package didn't help then that's a strong
Doesn't work for me either. I installed systemd-shim/saucy-proposed,
rebooted, suspended, waited 15 minutes and turned it on again - wifi
didn't work. sudo killall NetworkManager still solves the problem, so
no regression.
--
You received this bug notification because you are a member of Ubuntu
Hi,
I understand that it's difficult to deal with several bugs that look the
same. Before I file a new bug. Is there anything I can do to distinguish
the bug I have from the solve one? They have the same symptoms.
Rafael.
On Nov 14, 2013 10:31 PM, Martin Pitt martin.p...@ubuntu.com wrote:
systemd-shim 4-0ubuntu0.13.10 from saucy-proposed solved the problem for
me. Thanks for your bug-hunting efforts!
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1184262
Title:
times out too early,
Hello Steve, or anyone else affected,
Accepted systemd-shim into saucy-proposed. The package will build now
and be available at http://launchpad.net/ubuntu/+source/systemd-
shim/4-0ubuntu0.13.10 in a few hours, and then in the -proposed
repository.
Please help us by testing this new package.
** Branch linked: lp:ubuntu/saucy-proposed/systemd-shim
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1184262
Title:
times out too early, stuck in PrepareForSleep, causing network and
other
systemd-shim_4-0_ubuntu0.13.10 didn't fix 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/1184262
Title:
times out too early, stuck in PrepareForSleep, causing network and
** Tags removed: verification-needed
** Tags added: verification-failed
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1184262
Title:
times out too early, stuck in PrepareForSleep, causing network
Rafael, thanks for testing. We know that this update does not fix the
problem for everyone, but it seems to fix it for half/most of the
reporters here. So may I ask for only declaring this verification-failed
if you see a regression, i. e. if this version makes it worse than
before? After you get
Unfortunately my problem wasn't fix either using saucy proposed. Looking
forward to a new bug report.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1184262
Title:
times out too early, stuck in
This bug isn't fixed, I still lose network on suspend/resume when
installing the latest systemd-shim from the linked PPA.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1184262
Title:
times out too
Have to agree with Gabriel #129. I installed the latest version from PPA
yesterday and restarted, but today I also lost network on resume again.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1184262
Thanks Martin for all your efforts on this bug. You're PPA has totally
fixed the bug for me on 13.10.
Sorry to hear its not working for everyone.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1184262
Big thanks from me, too, Martin Pitt!
I installed your PPA on my Ubuntu 13.10/Acer AO722 netbook about eight
hours ago, and have exercised it quite a bit. As with Martin Farrell,
your PPA seems to have totally fixed my Suspend failures. (They began
with the beta of Ubuntu 13.10; see my comments
** Branch linked: lp:ubuntu/trusty-proposed/systemd-shim
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1184262
Title:
times out too early, stuck in PrepareForSleep, causing network and
other
This bug was fixed in the package systemd-shim - 4-0ubuntu1
---
systemd-shim (4-0ubuntu1) trusty; urgency=low
* New upstream release:
- Flush bus before exiting on idle to avoid a race where a message is
queued up but not yet sent. (LP: #1184262, part 1)
- Adjust the
For our friends on 13.10, I updated my PPA
(https://launchpad.net/~pitti/+archive/sru-test) to have systemd-shim
version 4, so you can test it now. I also pinged the SRU team, but
accepting into -proposed might still take a day or two.
--
You received this bug notification because you are a
** Changed in: systemd-shim (Ubuntu Trusty)
Milestone: None = ubuntu-13.11
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1184262
Title:
times out too early, stuck in PrepareForSleep, causing
55 matches
Mail list logo
