Plague meant I started the update, and have only now been able to get
back to text if it worked.
It did.
Thank you.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1927660
Title:
Update from 18.04
Public bug reported:
Have successfully performed this update with similar extra software
installed, and can't narrow it down to what software is blocking things.
Other bug reports talk about various other packages, many of which I've
tried removing with no improvement.
"apt-get purge
** Also affects: kernel-package (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/1528735
Title:
Suspend fails every second time on some laptops in
So given that this bug has been confirmed, found to be a bug in the
kernel code, and a patch created for it... is it possible to get this
bug moved to the Kernel, and generally find out if there's a timeline
for the patch being ported to the usual set of kernels?
It would be nice to have full
Leading up to the suspend, I don't think the OS can tell that there's
anything different... Or else if it can it's not looking for it.
Afterwards it's not getting as far as the kernel before UEFI kills it,
at which point the kernel can only tell that it was rebooted while in a
suspended state. All
There are no logs. Unless UEFI is keeping any,I don't think there can be
any logs, because the OS is suspended at the time it happens.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1528735
Title:
Just updated to 4.2.0-27-generic #32~14.04.1-Ubuntu SMP, and this is
still an issue.
This may not actually be directly related to pm-suspend, but I put it
here for lack of a better proximate cause. This may need to be
transferred to be a kernel bug.
I suspect it may be related to a reaction to
Just updated to 4.2.0-27-generic #32~14.04.1-Ubuntu SMP, and this is
still an issue.
This may not actually be directly related to pm-suspend, but I put it
here for lack of a better proximate cause. This may need to be
transferred to be a kernel bug.
I suspect it may be related to a reaction to
Public bug reported:
Fresh install of Xubuntu 14.04.3, replacing existing OEM Windows 10.
Install detected UEFI, and installed in UEFI mode. (I have attempted to
change to legacy boot, and got it to a state where it was booting
without /sys/firmware/efi/ being present, but behaviour persisted.)
Public bug reported:
Fresh install of Xubuntu 14.04.3, replacing existing OEM Windows 10.
Install detected UEFI, and installed in UEFI mode. (I have attempted to
change to legacy boot, and got it to a state where it was booting
without /sys/firmware/efi/ being present, but behaviour persisted.)
Compaq Presario CQ62-227TU
I since upgraded to 12.04.2, but the kernels in that line are still
showing this behaviour. (Last one checked: 3.2.0-51.77)
I still have the 3.9.0-030900rc2 generic kernel installed from earlier
testing, and the wireless connectivity does work under this kernel.
(There
$ uname -a
Linux faustus 3.9.0-030900rc2-generic #201303102035 SMP Mon Mar 11 00:44:44 UTC
2013 i686 i686 i386 GNU/Linux
Install of 3.9.0 kernel made dkms complain about virtualbox, but I only
very rarely use that, so it's not an issue.
New behaviour: On boot into this kernel, the buggy
Booted back into 3.0.0.31-pae, wireless had same behaviour as in 3.9:
did not start correctly on boot, works after rmmod/modprobe of rtl8192se
module.
dmesg of this session attached.
** Attachment added: dmesg of boot into 3.0.0.31 kernel after 3.9 test.
Public bug reported:
Behaviour noticed immediately after kernel upgrade from 3.0.0-31 to 32.
When laptop is connected to power, all is as it should be.
When laptop is disconnected from mains, and running on battery, the
wireless will continue working for a while (less than a minute), then
drop
14 matches
Mail list logo
