The problem does not occur in Linux version 4.8.0-34-generic
(buildd@lcy01-21) from yakkety-proposed. I don't understand the
"checkbox-gtk" instruction in the page you reference.
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubu
I've been using the 4.9.0 I mentioned in comment #14 with no trouble at
all. There is a new 4.9.0 of about the same date in the drm-intel-next
branch that knz tried in comment #11. See if that has the problem fixed.
Someone can also try building Linus's 4.9.0 to see if it's a general or
Ubuntu reso
Ubuntu added a 4.9.0 kernel yesterday
(4.9.0-040900-generic_4.9.0-040900.201612111631_amd64.deb) in the
mainline kernel ppa. This kernel does not have the problem on my Surface
Pro 3.
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux i
I've had the same problem with every 4.8 I tried including the one that
is in the brand new Ubuntu 16.10 (4.8.0-22) [via live cd, not
installed!]. My computer is a Surface Pro 3 which uses a Marvell chipset
in the docking station. I'm pretty sure I have updated to the latest
mwifiex in my installed
Bluez 5.40 works for me for both Designer keyboard and mouse. At this
time Ubuntu has not packaged it up into a DEB but I was able to build
and install it myself (search for bluez 5.40 to find how to download the
entire large source). I am using Ubuntu 16.04 but a newer kernel made by
Ubuntu (4.6.0
The 4.4 Linux Kernel series reconnects even after the 10 minutes or
(usually) a reboot. My roll-your-own is 4.4-rc2 which has a building
problem but that is known and probably will already be fixed in rc3
--
You received this bug notification because you are a member of Kernel
Packages, which is
A follow-up. My Android Lollipop phone can connect and knows that the
Designer Mouse is a mouse (not an unknown). Unfortunately it too loses
connection in 10 minutes so the problem is deeper than I had expected.
--
You received this bug notification because you are a member of Kernel
Packages, wh
I have been working with a Microsoft Designer Mouse (also a BLA device).
I went to AskUbuntu to try to find out why I could not use it with
Ubuntu 15.10. [I have a Microsoft Surface Pro3 and am using a home-built
kernel but the kernel does not seem to affect this problem.] I have
followed the instr
Christopher, this assignment doesn't seem possible. When I use Linux
4.0.0-04rc7-genericx86_64, it suspends well and seems to stay
suspended indefinitely. But I can't get it to resume at all and have to
kill it by holding the power switch for a long time.
When it comes back it reports two or t
Christopher, when I downloaded the 4.0-rc6 kernel earlier in the week it
didn't really install right but ran (somehow broken with respect to the
headers) so I deleted it after making the report. Tonight I can't repeat
the installation, good or bad, so I'll wait until the next one is made,
probably
Here is my bios information:
3.11.0760
03/16/2015
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1436620
Title:
Bluetooth & USB interrupt suspended state on Surface Pro 3
Status in lin
I am using that update; it came March 31 and disconnected me from grub.
I figured out how to use boot-repair and got back to Linux.
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1436620
T
I should really say that suspend-to-idle never holds forever. With the
SP3 disconnected from every plug including docking station, power, type
cover, and micro-SD and with both BT and WIFI turned off, it lasts for
random periods and then comes back alive.
I'm using 4.0-RC6 with the set of patches
I tested with Linux version 4.0.0-04rc6-generic using the
pm_functions as modified by Launchpad bug 1380076. This is not a
perfectly clean bug in that it sometimes bounces back from freeze even
without BT being on and it can go a long time with BT on. But definitely
BT makes the freeze less rel
I have created bug 1436620. It's a bit of a messy situation but I hope I
described it well enough.
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1380076
Title:
Can't suspend on Surface
I have created bug 1436620. It's a bit of a messy situation but I hope I
described it well enough.
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1380076
Title:
Can't suspend on Surface
Public bug reported:
[Please note: this information was collected using 3.16.0-33 but
actually is talking about behavior under 4.0.0-RC4 with four specific
patches described at the end of the note.]
1. When suspending (i.e. freezing in this situation), it is never
certain that it will stay suspen
With the freeze patch installed and the power button patch in the kernel it can
still fail to stay suspended. However I think there are two causes in my system
and without them it will stay frozen at least until there is a power glitch:
- Bluetooth on, even with nothing paired, is certain to caus
Kernel bug 84651 addresses the power button issue. As of today it is
still being tested. On my computer (now running 4.0-RC4 with patches but
NOT the freeze patch from comment 26) suspending still bounces back, but
with their patch it goes to the lock screen mode.
I will now try putting that in an
I got that wrong yesterday, I think. IWhen the freeze patch is
installed, it seems to do something akin to suspending, but I haven't
figured out how to get it back (not power button or mouse movement).
Instead you have to hold the power button long enough to kill it and
then start over. Note that t
I made Akdor's pm-functions patch using 3.19RC3. Suspend did not change
at all; it still bounced right back. Note that this kernel is unaware of
the battery (I've read that 3.16 kernels don't have that problem) so
maybe there is some interaction there.
--
You received this bug notification becaus
Good question, Chris,
Again my hardware is HP mini 110, not Dell. The xorg people fixed my
problem seemingly quite completely around 8 months ago (before 13.04). I
don't use dual monitors on a regular basis, so I don't know any more than
that.
Keith
On Thu, Nov 21, 2013 at 3:21 AM, cmavr8 <1079
I don't know why you are sending this. So far as I know the problem has
been fixed--but I'm not doing dual monitor stuff now and not inclined to
make a new test.
Keith
On Nov 20, 2013 7:41 PM, "Christopher M. Penalver" <
christopher.m.penal...@gmail.com> wrote:
>
> cmavr8, if you have a bug in Ub
I don't think I have a new bug.
Keith
On Nov 19, 2013 7:15 PM, "Christopher M. Penalver" <
christopher.m.penal...@gmail.com> wrote:
>
> Keith McClelland, if you have a bug in Ubuntu, the Ubuntu Kernel team,
Ubuntu Bug Control team, and Ubuntu Bug Squad would like you
Christopher,
My problem is (was?) with an HP Mini 110 not a Dell computer. I haven't
tried it recently so I can't say if it was fixed or not.
Thanks,
Keith
On Tue, Nov 19, 2013 at 7:09 AM, Christopher M. Penalver <
christopher.m.penal...@gmail.com> wrote:
> mikesmithv, as per
>
> http://www.de
25 matches
Mail list logo
