** Changed in: systemd (Ubuntu)
Status: Confirmed => Fix Released
** Changed in: systemd (Ubuntu Trusty)
Status: Confirmed => Won't Fix
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
Dear ubuntu staffs,
installing new softwares in my ubutu I am persistently face with error as below:
dpkg-divert: error: rename involves overwriting
'/usr/share/dbus-1/system-services/org.freedesktop.systemd1.service' with
different file
Status changed to 'Confirmed' because the bug affects multiple users.
** Changed in: systemd (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/1252121
Title:
Status changed to 'Confirmed' because the bug affects multiple users.
** Changed in: systemd (Ubuntu Trusty)
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/1252121
I've recently upgraded from 12.04 to 14.04. In 12.04 all worked perfectly.
I see the same sort of thing as discussed. I attach a log from dbus-monitor.
PrepareForSleep True is sent, sleep state is never reached,
PrepareForSleep false is never sent
I have no problem suspend/hybernate via
** Also affects: systemd (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/1252121
Title:
missing PrepareForSleep signal after resuming, causing
This works perfectly on Ubuntu 16.04 with systemd:
https://gist.github.com/nitely/3d5f10b4f686f5f96c95
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1252121
Title:
missing PrepareForSleep signal
** Project changed: network-manager => ubuntu-translations
** No longer affects: ubuntu-translations
** Project changed: wicd => ubuntu-translations
** No longer affects: ubuntu-translations
** Changed in: systemd-shim (Ubuntu Saucy)
Importance: Undecided => High
--
You received this bug
Any progress on this issue? I experience all of the symptoms posted by
#8, are more logs required to properly troubleshoot this issue?
The proposed workaround for enabling the network using "nmcli nm sleep
false" works ok for me, but I also use VirtualBox quite heavily and any
running machines
Currently using Xubuntu 14.04.2 updated.
I have tried all the workarounds (restarting services, scripts, unload module
files, etc) and none of them work for me.
The issue I experience is related only to wired connection (DSL or
Ethernet connections) and *not* with wi-fi.
What I found out and
Have anybody tried to remove light-locker? Maybe light-locker causes it?
Or lightdm... As for me the bug isn't reproducable currently. Also I
have upgraded to 3.16 kernel and suspending is much faster now
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is
Spoke too soon, just hibernated and then resumed with Ethernet cable
plugged in and the problem occurred. Killing or restarting Network
Manager just caused nm-applet to crash so I had to restart that - which
is probably why the workaround no longer works.
I haven't noticed this problem in the
@Pablo have you tried disabling ACPI HPET Table in BIOS? Maybe you don't
have such option in BIOS/UEFI.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1252121
Title:
missing PrepareForSleep signal
Hello guys! The bug seems to be fixed on my PC. There were lots of changes
since the last check, but the last I did was disabling ACPI HPET Table in BIOS.
Also I got rid of indicators.
Other BIOS settings:
suspend to ram - auto
check ready bit - auto
away mode support - disabled
restore on AC
After an upgrade to 14.10 the workaround stopped working (restarting
network manager each resume). Due to another problem I had to reinstall
14.10 and the problem is no longer present for me after the reinstall. I
am not sure whether this has been fixed in 14.10 or whether it was the
14.04.2 had been just released with new kernel 3.16 Is the big still
persists? And what is wicd? Package that fixes bug ?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1252121
Title:
missing
This works fine for me, with wicd on Ubuntu Utopic.
Actually, I don't see why someone (justin parker?) marked wicd as being
affected, because I don't see anyone mentioning wicd in this report, and
neither in https://bugs.launchpad.net/ubuntu/+source/systemd-
shim/+bug/1184262 and neither in any
** Changed in: wicd
Status: New = Incomplete
** Changed in: wicd
Importance: Undecided = Medium
** Changed in: wicd
Assignee: (unassigned) = Tom Van Braeckel (tomvanbraeckel)
** Changed in: wicd
Status: Incomplete = Invalid
--
You received this bug notification because
This works fine for me, with wicd on Ubuntu Utopic.
Actually, I don't see why someone (justin parker?) marked wicd as being
affected, because I don't see anyone mentioning wicd in this report, and
neither in https://bugs.launchpad.net/ubuntu/+source/systemd-
shim/+bug/1184262 and neither in any
The issue of the network not reconnecting after a suspend cycle is
present also in utopic (14.10).
Maybe it is another bug, but if this is the case, the fact that other
bugs opened on the issue are made duplicate of this should be corrected.
The issue completely breaks the possibility of using
The issue of the network not reconnecting after a suspend cycle is
present also in 14.10 (utopic).
Maybe it is another bug, but if this is the case, the fact that other
bugs opened on the issue are made duplicate of this should be corrected.
The issue completely breaks the possibility of using
It is still happening in Xubuntu 14.10. After coming back from suspend
(closed the laptop lid), NetworkManager is asleep:
RUNNING STATE WIFI-HARDWARE WIFI WWAN-HARDWARE WWAN
running asleep enabled enabledenabled
disabled
Maybe it depends on fresh install/update from buggy trusty?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1252121
Title:
missing PrepareForSleep signal after resuming, causing networking to
stay
@r0lf this is still happening in 14.10/Utopic should it be reopened
there?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1252121
Title:
missing PrepareForSleep signal after resuming, causing
If so we are waiting backport of fix to Trusty
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1252121
Title:
missing PrepareForSleep signal after resuming, causing networking to
stay disabled
To
The issue seems be resolved for me in Lubuntu 14.10.
On Wed Jan 21 2015 at 2:01:06 PM Andy Somerville andy.somervi...@gmail.com
wrote:
@r0lf this is still happening in 14.10/Utopic should it be reopened
there?
--
You received this bug notification because you are subscribed to the bug
Same feeling, I'm disappointed no one seems to take care of that basic
bug that keeps me from using Ubuntu as my daily distro.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1252121
Title:
missing
Why is this bug still unassigned more than a year later? Isn't the use
of suspend + network-manager sufficiently common? It seems to me that
this is a critical bug and I am quite shocked that no developer has
deigned so much as to look at it in more than a year. I can do sudo
restart
@Yanapas #148
Yes I have same bug in Linux Mint 17 KDE 64bit
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1252121
Title:
missing PrepareForSleep signal after resuming, causing networking to
stay
saucy has seen the end of its life and is no longer receiving any
updates. Marking the saucy task for this ticket as Won't Fix.
** Changed in: systemd-shim (Ubuntu Saucy)
Status: Confirmed = Won't Fix
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is
Confirming: I installed Xubuntu Utopic 2 days ago, and this bug is also
biting me. However, I noticed that it depends on the time interval
between suspend and resume: the bug only happens when I resume 2+ hours
after I suspend (it always happens in the morning when I first open the
laptop lid).
Is this reproducible on Utopic?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1252121
Title:
missing PrepareForSleep signal after resuming, causing networking to
stay disabled
To manage
I'm not sure whether this scipt were posted here.
=
#!/bin/bash
case $1 in
thaw|resume)
nmcli nm sleep false
;;
*)
;;
esac
exit $?
#save it in /etc/pm/sleep.d/wakenet.sh
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to
@David or anyone else having this problem, I too didn't have any luck
with nmcli nm sleep false in my script under /etc/pm/sleep.d/ either
but when I used service network-manager restart instead it worked
flawlessly. I have not had any problems for almost five months and it
doesn't cause any side
!!! I have just booted from live Linux Mint xfce edition - everything is
OK with network there. Also I booted from Xubuntu and this bug appears
there. Is there anyone with Linux Mint with the same bug?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is
Also experiencing this on Ubuntu 14.04. It's much easier to reproduce
the longer you leave the computer in hibernation. I usually can't
reproduce if I hibernate for a few minutes and then resume, but if I
hibernate overnight and resume the next morning, this bug almost always
occurs. Doing a sudo
For what it's worth, I added the command pkill -f wpa_supplicant after
nmcli nm sleep false in my /etc/pm/sleep.d/ thaw or resume script,
based on another similar bug that was reported elsewhere (I've lost the
link; sorry).
Now the wireless interface comes back up pretty consistently after a
@dave-eorbit Thank you anyway!
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1252121
Title:
missing PrepareForSleep signal after resuming, causing networking to
stay disabled
To manage
Same problem for laptop upgraded from 12.04 into 14.04.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1252121
Title:
missing PrepareForSleep signal after resuming, causing networking to
stay
I'm also experiencing this in 14.04 after upgrade from Ubuntu 12; dbus
log shows PrepareForSleep true on suspend, but no corresponding
PrepareForSleep false on awakening.
Putting a script in /etc/pm/sleep.d/ (or in /usr/lib/pm-utils/sleep.d/)
to issue nmcli nm sleep false (a workaround suggested
The same behavior on fresh reinstalled Xubuntu.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1252121
Title:
missing PrepareForSleep signal after resuming, causing networking to
stay disabled
To
Good question!
I'm on Utopic development version (i. e. 14.10) and there is no way to
get network back on automatically after hibernate! (suspend often caused
my machine to hard-lock so I can only use hibernate in my case)
It's a shame everyone ignores us, saying this is of minor importance.
@andi3 Does hibernation work in Utopic? It is disabled for some unknown
reasons in ubuntu for a long time, and I miss it very much. In addition
to all now I'm back to Windows 7 and waiting for the fix
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is
Yes, hibernation itself DOES work in Utopic (Lubuntu flavor). However,
as I notice that I'm even able to hibernate my machine via GUI menu, I
might have done some change that enables this (because I do remember
there was something on launchpad about this being disabled in the
vanilla installation)
I suppose that problem is invisible for developers. Any ideas how to UP
topic?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1252121
Title:
missing PrepareForSleep signal after resuming, causing
14.04, stock installation (no Jupiter or other additional power
management software), desktop PC, networking never resumed after a
suspend, 100% failure rate. Though being a desktop I supended the PC
maybe 10 times since April.
--
You received this bug notification because you are a member of
@yanpas
I do not know! u-power? something else gnome-specific? I should take
some time to investigate what else there is.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1252121
Title:
missing
@Dimitry from #131
Unfortunatly for some reason Gnomebuntu doesn't care about
/etc/pm/sleep/*, pm-utls is involved with /etc/pm* and pm-utils is not
installed under gnomebuntu 14.04 for me. Installing pm-utils makes
suspend/resume work much less reliable, so leaving it off.
--
You received this
@oliver so which utility does provide you power management?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1252121
Title:
missing PrepareForSleep signal after resuming, causing networking to
stay
I've booted from live Xubuntu 14.04 and there were such a bug too! So
reinstall won't help
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1252121
Title:
missing PrepareForSleep signal after
Ubuntu GNOME 14.04
Log like
https://bugs.launchpad.net/ubuntu/+source/systemd-shim/+bug/1252121/comments/82
** Attachment added: nm.log
https://bugs.launchpad.net/ubuntu/+source/systemd-shim/+bug/1252121/+attachment/4110035/+files/nm.log
--
You received this bug notification because you
Ubuntu GNOME 14.04
Log like
https://bugs.launchpad.net/ubuntu/+source/systemd-shim/+bug/1252121/comments/82
** Attachment added: nm.log
https://bugs.launchpad.net/ubuntu/+source/systemd-shim/+bug/1252121/+attachment/4110034/+files/nm.log
--
You received this bug notification because you
Workaround using
/etc/pm/sleep.d/10_restart-networkmanager
works for me with less priority only, e.g. 01_restart... filename.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1252121
Title:
missing
After upgrading to 14.04 I am more affected by this bug than before:
network-manager does not wake up properly after hibernation.
With 13.10 this might only happen when I was using overriding the METHOD to
METHOD=suspend_hybrid for METHOD=suspend.
The workaround: `sudo nmcli nm sleep false`.
Philip, I also tried the Live CD version of 14.04 and discovered the
same as you did that it did not suffer from this problem. However I
remember some years ago trying the Live CD of a newly released version
of Ubuntu and discovered that Suspend and Hibernate worked flawlessly,
only to install the
Maybe it is gnome-power-manager fault?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1252121
Title:
missing PrepareForSleep signal after resuming, causing networking to
stay disabled
To manage
Ive collected 3 workarounds, and they work differently. Maybe this would
help developers. Also I have lan network printer.
1) suspend via sudo pm-suspend - the best option. LAN printer doesnt
make a noise and doesnt reinitialise and network continues to work,
there ar no notifications about
@Seth Arnold, Justin may have the package Linux installed but clearly he
is lacking its dependencies:
sarcasm-1.2.1
pretentiousness-99.9
elitism-1.0.1
smugness-1.0.0
Seth you seem to have an extra package installed:
unhelpfulness-0.1.1
Justin, you won’t need to restart every time, you can just
Yes, by default password is on. I think the problem is that network
manager needs root password to resume. So that is the trouble. I wonder
why it is still unfixed and there are no comments from devs :(
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is
IDK whats going on and thanks to those like SETH, now the bug is so
split who knows if it will ever be fixed Pablo Thanks for your
help... I'm not that much a newb but also not a developer. I know python
and work in Networking, but when it comes to Ubuntu application support
sorry to say I
A reinstallation might help. Even though the bug has not been fixed for the new
LTS version (), a fresh installation might help. I didn't do much testing
because I uninstalled Ubuntu to free up my SSD space for Windows (which runs
rather stable and doesn't give a whole bunch of error
Hey Guys Try this work around, It's the only one that worked on my
Toshiba NB505 With realtek drivers...
Settings security privacy Uncheck waking from Suspend Returning
From blank screen
Delete the entire contents of the following files
/etc/pm/config.d/config /etc/pm/config.d/unload_modules
Pablo180, this bug is about a missing PrepareForSleep signal from
systemd-shim.
Justin's log messages show that his kernel had trouble re-associating
with his access point. I have seen several other people with similar log
messages and it would be far easier for that problem to be diagnosed and
Seth Arnold, which logs do I need to upload? BTW I use latest systemd-
shim 6-2bzr1
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1252121
Title:
missing PrepareForSleep signal after resuming,
Interesting observation - If you check and then uncheck password request
after suspend - that will fix the problem till the next reboot. So the
final step - how to write .sh script that will check and uncheck this
option at every PC boot? (Something related with dconf). Also check if
this solution
dconf write /org/gnome/desktop/screensaver/ubuntu-lock-on-suspend true
dconf write /org/gnome/desktop/screensaver/ubuntu-lock-on-suspend false
This two-line script didn't solved my problem...
The last workaround I've invented is to change Command suspend from Gear Menu
to:
echo yourpassword |
Yanpas, I tried setting the password request upon resume, it didn't make
any difference for me. Networking was still down after resuming and
entering my password. But I am using 13.10 and only hibernate, I don't
suspend, not sure whether that has any bearing.
Seth, if that was the case then I
14.04 same thing WIFI won't come back after suspend... Editing
/etc/pm/config.d/config with the SUSPEND_MODULES=your_driver_here
in my case rtl8192ce used to work now its not working at all. After
every suspend it seems to be unable to disconnect. The last time WIFI
worked at this point was
** Also affects: network-manager
Importance: Undecided
Status: New
** Also affects: wicd
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/1252121
On my system (HP ProBook 4750s) it doesn't work since Ubuntu 13.10
update. Now killall NetworkManager is my daily routine :)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1252121
Title:
missing
Justin, I believe you have a different issue; please file a new bug
report for it, I suggest filing it against the package 'linux'.
Thanks
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1252121
Bug affecting me in Ubuntu 14.04
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1252121
Title:
missing PrepareForSleep signal after resuming, causing networking to
stay disabled
To manage
This Bug still affects me on 12.04
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1252121
Title:
missing PrepareForSleep signal after resuming, causing networking to
stay disabled
To manage
Same here (13.10) . The big problem is that it seems to be in all releases, so
downgrading from 13.10 to the previous LTS release wouldn't even help. Half a
year ago, everything was fine. So why is it that now it suddenly does not work
anymore and can't be fixed (e.g. by reverting some
I have to agree with Philipp, I also, and perhaps somewhat naively,
believed it would just be a case of comparing what has changed in newer
version with the previous version that didn't have any problem and
working out what is causing this problem. Or maybe just reverting to an
earlier version of
The workaround does not work on my machine.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1252121
Title:
missing PrepareForSleep signal after resuming, causing networking to
stay disabled
To
The same workaround worked for me.
Thanks Massimo !
I really hope that this very annoying bug will be at least resolved for Trusty.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1252121
Title:
This bug still affects me on an up to date saucy, with installed systemd-shim
6-0ubuntu0.13.10.
I also tried systemd-shim in alternative ppa as described in
https://bugs.launchpad.net/ubuntu/+source/systemd-shim/+bug/1184262/comments/151
I could only workaround the problem through
It currently doesn't work for me. I have the latest saucy-proposed
packages, should the update you mentioned be in there?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1252121
Title:
missing
Since the recent update for the Gnome libraries I don't see the bug. The
network resumes normally.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1252121
Title:
missing PrepareForSleep signal after
For completeness, this is grep -C 5 around PrepareForSleep dbus traffic over a
suspend/resume:
string Strength
variant byte 80
)
]
signal sender=:1.23 - dest=(null destination) serial=2607
path=/org/freedesktop/UPower; interface=org.freedesktop.UPower;
This was captured with the given systemd-shim debug capture rune; I
didn't have to ^C systemd-shim on resume as it exited by itself with 0
(see bottom of log).
** Attachment added: systemd-shim.log
Getting this too; I only see one PrepareForSleep true dbus call over a
suspend/resume call (no PrepareForSleep false).
Will attach a systemd-shim debug log.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
Thanks LoÏc. For the record, it's expected that systemd-shim times out
after some seconds of inactivity. So the shim log looks fine, and indeed
the PrepareForSleep False is missing, as with other people. At this
point this requires an in-depth debugging of systemd-logind, to see why
it sometimes
This is how debug output looks:
SYSTEMD_LOG_TARGET=console SYSTEMD_LOG_LEVEL=debug annotate-output
/lib/systemd/systemd-logind
[...]
18:25:19 E: Fixing up /dev/kvm for seat seat0...
18:25:19 E: Fixing up /dev/rfkill for seat seat0...
18:25:19 E: Fixing up /dev/snd/seq for seat seat0...
18:25:19
So launching logind in the foreground, it displays:
New seat seat0.
Watching system buttons on /dev/input/event3 (Power Button)
Watching system buttons on /dev/input/event7 (Video Bus)
Watching system buttons on /dev/input/event1 (Power Button)
Watching system buttons on /dev/input/event0 (Lid
So I patched pm-suspend to exit 0, and that would not trigger the bug
anymore.
I added a sleep as you suggested and NM would disconnect and then
reconnect up to sleep value of 25 but not with sleep values of at least
26. I think we're looking at a 30 seconds timeout since my system takes
some
@pitti
Just an update from my side:
Not using hybrid suspend (via overriding METHOD=suspend_hybrid) fixed it 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/1252121
Title:
missing
The signal is really missing. Attached is the dbus log when closing and
opening the lid.
** Attachment added: dbus-lid.log
https://bugs.launchpad.net/ubuntu/+source/systemd-shim/+bug/1252121/+attachment/3954133/+files/dbus-lid.log
--
You received this bug notification because you are a
Thanks Christian. So this is yet another bug than the one that Daniel
and Rafael are experiencing.
First, please ensure (dpkg -l systemd-shim) that you have version 6-...
installed. If you do, please run this
sudo G_DBUS_DEBUG=all annotate-output /usr/lib/*/systemd-shim 21 |
tee
Seems that in some cases (1 in 5 tries) networkmanager resumes. Attached
is the case when it does not resume.
Note that I don't have to press ctrl+c to stop logging; it exits itself.
** Attachment added: systemd-shim3.log
Here network manager resumed properly.
** Attachment added: systemd-shim2.log
https://bugs.launchpad.net/ubuntu/+source/systemd-shim/+bug/1252121/+attachment/3954187/+files/systemd-shim2.log
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed
So in systemd-shim3.log StartUnit('suspend.target') is called once,
while in systemd-shim2.log it's called twice. Are you sure that systemd-
shim2.log was the one where things worked properly? It seems much more
likely to me that calling StartUnit('suspend.target') twice in short
succession might
I can't reproduce the working state now with 10 tries. And all those
logs of broken resuming only have a single suspend.target call.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1252121
Title:
I have 6-0ubuntu0.13.10.
Please see the attached nm.log that I created as Martin described in #82.
I had to wait some time after sudo Networkmanager ... until my wifi was
connected. Then I suspended which took the usual while. After resume, the
network was disconnected as usual. I didn't have
And here's my systemd-shim.log (see Martin's comment #88). Just like
Christian, I do not have to press Ctrl+C, it exits a few moments after
resuming and entering the user password.
** Attachment added: Suspended using Unity menu
Is there any chance this (and https://bugs.launchpad.net/ubuntu/+source
/pm-utils/+bug/1253456) might get fixed in the next months, e.g. for the
next LTS release? I would have to downgrade to Ubuntu 12.04 otherwise
(or maybe stick to Windows?).
--
You received this bug notification because you
I experience this issue on a MacBook Air when closing the lid. In this case,
the network does not come up.
When I use pm-suspend to put it to sleep, I get a working network connection
after wakeup.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is
I can't participate directly in this bug anymore because I've done a
reinstall.
Having said that, the following configuration now *works* for me.
Ubuntu-Gnome 13.10 install (from scratch)
Gnome-next ppa
Gnome-staging ppa
TLP from https://launchpad.net/~linrunner/+archive/tlp
TLP properly
Philipp, I asked on bug 1253456 for more information, that's a new one.
As for this one, I don't have any log files that show any error, nor do
I know anyone who can reproduce this. If you still have this bug even
with the latest systemd-shim packages, then perhaps looking at network-
manager
1 - 100 of 150 matches
Mail list logo
