Given the number of bug reports, and that this causes delayed breakage
in server environments, perhaps this bug priority should be raised from
"Low" to "Medium"?
I encountered this delayed failure in an LXC container, following
upgrading the server and LXC container from Ubuntu 17.10 to Ubuntu
Public bug reported:
The Problem
---
Using a SuperMicro MBD-X11SAE-M motherboard, (which uses the Intel C236
chipset,) running firmware version 1.0b 03/24/2016 - latest at time of
filing this bug, when booted in BIOS/CSM mode, the machine locks-up - no
disk activity, no caps lock
Public bug reported:
The Problem
---
When booted in EFI mode, using a SuperMicro MBD-X11SAE-M motherboard,
(which uses the Intel C236 chipset,) running firmware version 1.0b
03/24/2016 - latest at time of filing this bug, the machine reboots upon
invocation of the 'boot' command in grub,
Public bug reported:
The Problem
---
Using a SuperMicro MBD-X11SAE-M motherboard, (which uses the Intel C236
chipset,) running firmware version 1.0b 03/24/2016 - latest at time of
filing this bug, the machine locks-up - no disk activity, no caps lock
response, black screen -- upon
/etc/update-manager/release-upgrades:
---
# Default behavior for the release upgrader.
[DEFAULT]
# Default prompting behavior, valid options:
#
# never - Never check for a new release.
# normal - Check to see if a new release is available. If more than one new
# release is found,
This bug is still present in Ubuntu 16.04.1 LTS with the latest updates.
user@computer:~$ lsb_release -a;date;sudo tsocks do-release-upgrade;date
No LSB modules are available.
Distributor ID: Ubuntu
Description:Ubuntu 16.04.1 LTS
Release:16.04
Codename: xenial
Wed Dec 14
The bug is still present in the latest version of Ubuntu and Ubuntu gnucash
package.
DistroRelease: Ubuntu 15.10
Package: gnucash 1:2.6.6-2ubuntu2
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
Occured for me after a new install of Ubuntu Server 14.10 64-bit to an
ext4 FS on a RAID-1 on SSDs.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1359439
Title:
[7.287663] systemd-logind[1057]:
On an 800 Mhz machine I can quite consistently reproduce startup
failures and conflicting IPs with ext3 instead of btrfs with only two
containers.
Additional Information:
A brand new install of Ubuntu 13.04 Server AMD64 with all updates applied.
$ sudo lxc-ls --fancy
NAME STATEIPV4
Public bug reported:
Occurred on Ubuntu upgrade
ProblemType: Package
DistroRelease: Ubuntu 11.04
Package: monodoc-base 2.6.7-5ubuntu3
ProcVersionSignature: Ubuntu 2.6.35-30.54-generic 2.6.35.13
Uname: Linux 2.6.35-30-generic x86_64
NonfreeKernelModules: fglrx
Architecture: amd64
Date: Sat Jul 9
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/808215
Title:
package monodoc-base 2.6.7-5ubuntu3 failed to install/upgrade:
ErrorMessage: subprocess installed post-installation script returned
Also applies to Dell XPS M1210 laptop which uses a Synaptics touchpad.
Can anyone confirm if this bug only effects Dell laptops?
Laptop sales now exceed 50% of PCs sold, and just about all laptops have
touchpads. With 7%-10% of computer users being left-handed, this bug
effects between 1 out of
I'm experiencing the same bug.
I tested it with it the mainline kernel packages 2.6.31 amd64 and sound
works after resume. Unfortunately the current ATI binary drivers
provide no 3D with that kernel.
** Attachment added: uname-a.log
http://launchpadlibrarian.net/31739157/uname-a.log
--
no
** Attachment added: lspci-vvnn.log
http://launchpadlibrarian.net/31739161/lspci-vvnn.log
--
no sound after suspend with ca0106 Soundblaster Live! 7.1 24bit
https://bugs.launchpad.net/bugs/255737
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed
** Attachment added: alsa-info.txt
http://launchpadlibrarian.net/31739166/alsa-info.txt
--
no sound after suspend with ca0106 Soundblaster Live! 7.1 24bit
https://bugs.launchpad.net/bugs/255737
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to
** Tags added: linux-2.6.28
** Tags removed: needs-upstream-testing
--
no sound after suspend with ca0106 Soundblaster Live! 7.1 24bit
https://bugs.launchpad.net/bugs/255737
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
I am experiencing the same bug since I upgraded my IBM Thinkpad X24
Type 2662 from Edgy to Feisty today. The Atheros 5212 based NIC is a
NetGear WPN511.
** Attachment added: uname -a
http://librarian.launchpad.net/7384082/uname-a.log
--
Atheros 5212 NIC Fails to Connect in Feisty
** Attachment added: lspci -vvn
http://librarian.launchpad.net/7384083/lspci-vvn.log
--
Atheros 5212 NIC Fails to Connect in Feisty
https://bugs.launchpad.net/bugs/96754
You received this bug notification because you are a member of Ubuntu
Bugs, which is the bug contact for Ubuntu.
--
** Attachment added: lspci -vv
http://librarian.launchpad.net/7384085/lspci-vv.log
--
Atheros 5212 NIC Fails to Connect in Feisty
https://bugs.launchpad.net/bugs/96754
You received this bug notification because you are a member of Ubuntu
Bugs, which is the bug contact for Ubuntu.
--
** Attachment added: dmesg
http://librarian.launchpad.net/7384087/dmesg.log
--
Atheros 5212 NIC Fails to Connect in Feisty
https://bugs.launchpad.net/bugs/96754
You received this bug notification because you are a member of Ubuntu
Bugs, which is the bug contact for Ubuntu.
--
ubuntu-bugs
** Attachment added: cat /proc/version
http://librarian.launchpad.net/7384088/proc_version.log
--
Atheros 5212 NIC Fails to Connect in Feisty
https://bugs.launchpad.net/bugs/96754
You received this bug notification because you are a member of Ubuntu
Bugs, which is the bug contact for Ubuntu.
I did some additional testing:
Although the network is seen without the SSID being broadcast, since
upgrading to Feisty it can not connect to the network without the SSID
being broadcast. With the SSID being broadcast, I have been
successfully able to connect using no encryption and using WPA2
22 matches
Mail list logo
