Just to clarify things a little bit. I don't believe this is actually
very "unusual hardware". I try to develop software for Raspberry Pi (a
common hardware platform) on my laptop and have installed QEmu to do so.
If I use libvirt to start QEmu, I run into this exact same problem.
Starting QEmu
*** This bug is a duplicate of bug 1676810 ***
https://bugs.launchpad.net/bugs/1676810
** This bug has been marked a duplicate of bug 1676810
Network Manager needs restarting from sleep
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to
*** This bug is a duplicate of bug 1676810 ***
https://bugs.launchpad.net/bugs/1676810
** This bug has been marked a duplicate of bug 1676810
Network Manager needs restarting from sleep
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to
Please note that bug 1666318 has relevant information. It appears that
editing
/etc/NetworkManager/NetworkManager.conf
and removing "dns=dnsmasq" makes the problem go away.
So, this could be a bug in either network manager or in dnsmasq
--
You received this bug notification because you are a
*** This bug is a duplicate of bug 1676810 ***
https://bugs.launchpad.net/bugs/1676810
** This bug has been marked a duplicate of bug 1676810
Network Manager needs restarting from sleep
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to
*** This bug is a duplicate of bug 1676810 ***
https://bugs.launchpad.net/bugs/1676810
** This bug has been marked a duplicate of bug 1676810
Network Manager needs restarting from sleep
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to
I can't access the bug, yet. But hopefully, I will be able to do so at
some point -- or maybe, you can add me to it? Not sure if Launchpad
supports doing that.
In the meantime, I noticed that you updated the link in the FAQ. Thank
you! That's awesome.
--
You received this bug notification
As is, Asterisk is completely broken in Xenial. A fresh install crashes
within seconds of service start up. While I can't guarantee that
tracking upstream would fix this particular problem, it stands a much
higher chance of getting the attention of the Asterisk developers.
Shipping an outdated and
Public bug reported:
This bug applies to Ubuntu 14.04 (Trusty Tahr)
I configured my (GNOME) desktop to make Caps_Lock an additional Control
key.
This results in a perfectly reasonable xkb keymap:
xkb_keymap {
xkb_keycodes { include evdev+aliases(qwerty) };
xkb_types {
Public bug reported:
Patch 51 in the gnome-settings-daemon source code now disables auto-
locking of the screen, when the machine goes into suspend. This policy
makes some sense for users who use auto-login and don't have any other
security measures in place.
But it is counter-productive for
Hmm, I expected launchpad to ask me about the version number of the
software and the release that is affected. Apparently, it doesn't do
that.
So, here we go:
gnome-settings-daemon-3.3.90
DISTRIB_ID=Ubuntu
DISTRIB_RELEASE=12.04
DISTRIB_CODENAME=precise
DISTRIB_DESCRIPTION=Ubuntu precise
Try the attached patch for cryptsetup. It will probably take care of the
issue.
** Patch added: cryptsetup.diff
http://launchpadlibrarian.net/44205307/cryptsetup.diff
--
Problems when booting an encrypted lvm containing btrfs
https://bugs.launchpad.net/bugs/551055
You received this bug
** Attachment added: Bugfix
http://launchpadlibrarian.net/35930814/pam_issue.c.diff
--
pam_issue cannot read /etc/issue unless noesc option has been set
https://bugs.launchpad.net/bugs/486455
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to
Public bug reported:
pam_issue.c has a bug that prevents it from successfully reading the
contents of /etc/issue unless the noesc option was set in the pam.d/
configuration file.
I attached a patch that fixes this bug.
** Affects: pam (Ubuntu)
Importance: Undecided
Status: New
--
Public bug reported:
As reported on the Grub developer's mailing list (http://osdir.com/ml
/grub-devel-gnu/2009-07/msg00387.html ), Grub 2 has a bug that prevents
it from reporting sufficient information about the partition table when
chainloading other boot loaders.
Among others, this affects
** Attachment added: Fix chainloader's reporting of partition information
http://launchpadlibrarian.net/34903884/grub2-chainloader.diff
--
Grub2's chainloader cannot load extlinux (syslinux)
https://bugs.launchpad.net/bugs/469568
You received this bug notification because you are a member of
Public bug reported:
Binary package hint: initramfs-tools
I noticed this bug with Ubuntu intrepid (8.10) and initramfs-tools
0.92ubuntu2, but I believe it actually exists in all older releases,
too. Possibly even upstream, but I did not check.
I have a server with several harddrives spread
17 matches
Mail list logo
