GF,
As far as I can tell the problem is now gone. There is definitely no
problem using the HP driver which names the printer as
somethng-Officejet-Pro_8500-A910. The other one (which names it as
Officejet_Pro_8500_A910_174835_ and I think is the new generic printer)
doesn't print as close to the
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 Ubuntu
Bugs, which is subscribed to Ubuntu.
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
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 Ubuntu
Bugs, which is subscribed to Ubuntu.
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
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
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 Ubuntu
Bugs, 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 Ubuntu
Bugs, which
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
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
Here is my bios information:
3.11.0760
03/16/2015
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1436620
Title:
Bluetooth USB interrupt suspended state on Surface Pro 3
To manage notifications
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
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 Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1436620
Title:
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
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 Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1380076
Title:
Can't suspend on Surface Pro 3
To
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 Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1380076
Title:
Can't suspend on Surface Pro 3
To
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
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
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
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
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
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 Ubuntu,
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
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 to please file
a new report
This must be a very difficult situation for developers. There's no
question in my mind that the problem that I could detect when I created
this bug was resolved in February (as well as the related freedesktop-
bugs #58594 which is where it was ultimately resolved). The difference
may be that I
Chris,
I don't know how to report this as a bug so I'll just tell you and see if
you know.
A friend of mine has been having a horrible time with 12.10 and really
various other releases as well: the system freezes up in a manner very
reminiscent of the dual monitor problem I have--though he's not
Fun has returned. I don't know why the Feb 18 drm-intel-next insists on
crashing and I have no idea why the first attempt at the Feb 23 drm-
intel-nightly was a failure, but I returned to using it
(3.8.0-994-generic) with complete success later on. A 5-hour run, an
8-hour run, and it is currently
Chris,
That's the latest kernel in drm-intel-next. There is a newer one (23rd of
Feb) in drm-intel-nightly that has the same Ville S. fixes at the top but
COMMIT is another different number. I'll try that; I don't see any point in
pursuing a different bug at this moment.
Keith
On Mon, Feb 25,
Since Chris pointed out that the drm-intel-next build (Feb 18) is too
old for this fix (never mind that it also seems to exhibit a critical
bug on my computer), I tried the latest build from drm-intel-nightly
(Feb 23). No critical bug there.
However, it wastes very little time -- a few seconds --
I couldn't find a commit with the number Chris gave. But I loaded up
the 3.8.0-997_3.8.0-997.201302180432 kernel from drm-intel-next.
However, despite the fact that it seems to have built and installed
okay, it dies with an almost-all-black screen a few seconds after it
starts initializing the
Diane's understanding sounds good. If you poke and poke at the missing
scroll bar you can sometimes see a transient and non-functional hiding
scroll control.
Does anyone know how we can edit that blacklist on our computers?
--
You received this bug notification because you are a member of
I've added as many log files and additional information as I could to
freedesktop-bugs #58594.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1079440
Title:
i945: Random complete freeze using dual
I have a refinement for my workaround. I supposed that the important
thing was to keep Xorg and compiz on the same CPU. But that is not the
case. The most important thing seems to be to run Xorg on CPU 1. Note
that my computer is an Intel Atom N280 whose two cores are is not
advertised to be
Sorry, I wasn't subscribed to notifications so I thought there was
nothing going on.
I loaded 3.8-rc5 but the system still freezes after a few minutes.
I don't know how to add the tag 'kernel-bug-exists-upstream' but need
to.
** Tags added: kernel-bug-exists-upstream
--
You received this bug
I've made a breakthrough in understanding this problem. It seems to give
me a 100% workaround but of course I can't be sure.
The solution is to use taskset to force the Xorg and compiz
processes to always be run on the same CPU. The simple terminal commands
are:
taskset -pa 1 $(pgrep -x
I have also entered a bug in the bugzilla at freedesktop.org. This bug
is number 58594. I was advised in response to that bug that many changes
have been made in related software recently and I should try a drm-
intel daily build of kernel 3.7.0 plus the entire suite of xorg-
edgers updates.
I
More information:
Although this is marked above as applying to compiz, I feel that it is
really the i915 driver that powers both screens. Ubuntu 12.04 uses
xserver-xorg-video-intel 2:2.17.0-1ubuntu4. 12.10 uses
2:2.20.9-0ubuntu2. It's more of a feeling than a certainty. The driver
would probably
I've looked into this further.
First, the bug is heavily related to screen, keyboard, and/or mouse
activity. If I set up two monitors and don't have anything going on more
interesting than the clock changing once a minute, all is fine for
hours. If I set up activities on both screens and start
I get the same problem with the same description except that it only
takes a few minutes.
My Hardware is HP Mini 110. It appears that it only works properly using
800x600 for the external monitor, but I can use native 1024x600 for the
internal screen.
After a few minutes it freezes up in such a
Public bug reported:
The top few pixels of anything printed from Evolution, Firefox,
LibreOffice applications, Shotwell, and probably others are missing on
the printout with HP 8500A on wifi. The problem does not occur with
lpr. Note that this is the logical top but could be any of the four
sides
I have this problem too on my HP Mini 110. Here are some more facts
about it.
1. The problem only occurs when Compiz is used; everything is fine without
enabling Compiz.
2. There is no problem until you enter the calendar mode. From then until you
exit the application, it exhibits the crazy
Exact reason found and corrected: see bug #539467. The SATA Link Power
was being turned off, apparently when there was still disk activity
waiting. Applying lucid-proposed version of pm-utils-powersave-policy
(currently at 0.3.1) resolves the issues about stopping completely.
Note that the issues
Final news: I think I was mistaken about it being a kernel bug at all.
Replacing GRUB2 with GRUB seems to have solved it. I'll let someone else
fight that battle. Thank you for your hard work.
--
Lucid incompatible with HP Mini 110 BIOS (F.15)
https://bugs.launchpad.net/bugs/578868
You received
apport information
** Tags added: apport-collected
** Description changed:
Lucid Lynx 10.04 LTS does not start up well with the F.15 BIOS of HP
Mini 110. [This wasn't a problem before and is once again not a problem
now that I have reinstalled Karmic.]
The symptom is that if Lucid
apport information
** Attachment added: BootDmesg.txt
http://launchpadlibrarian.net/48361100/BootDmesg.txt
--
Lucid incompatible with HP Mini 110 BIOS (F.15)
https://bugs.launchpad.net/bugs/578868
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed
apport information
** Attachment added: Card0.Amixer.values.txt
http://launchpadlibrarian.net/48361101/Card0.Amixer.values.txt
--
Lucid incompatible with HP Mini 110 BIOS (F.15)
https://bugs.launchpad.net/bugs/578868
You received this bug notification because you are a member of Ubuntu
Bugs,
apport information
** Attachment added: Card0.Codecs.codec.0.txt
http://launchpadlibrarian.net/48361102/Card0.Codecs.codec.0.txt
--
Lucid incompatible with HP Mini 110 BIOS (F.15)
https://bugs.launchpad.net/bugs/578868
You received this bug notification because you are a member of Ubuntu
apport information
** Attachment added: CurrentDmesg.txt
http://launchpadlibrarian.net/48361103/CurrentDmesg.txt
--
Lucid incompatible with HP Mini 110 BIOS (F.15)
https://bugs.launchpad.net/bugs/578868
You received this bug notification because you are a member of Ubuntu
Bugs, which is
apport information
** Attachment added: IwConfig.txt
http://launchpadlibrarian.net/48361120/IwConfig.txt
--
Lucid incompatible with HP Mini 110 BIOS (F.15)
https://bugs.launchpad.net/bugs/578868
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed
apport information
** Attachment added: Lspci.txt
http://launchpadlibrarian.net/48361125/Lspci.txt
--
Lucid incompatible with HP Mini 110 BIOS (F.15)
https://bugs.launchpad.net/bugs/578868
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to
apport information
** Attachment added: Lsusb.txt
http://launchpadlibrarian.net/48361126/Lsusb.txt
--
Lucid incompatible with HP Mini 110 BIOS (F.15)
https://bugs.launchpad.net/bugs/578868
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to
apport information
** Attachment added: PciMultimedia.txt
http://launchpadlibrarian.net/48361127/PciMultimedia.txt
--
Lucid incompatible with HP Mini 110 BIOS (F.15)
https://bugs.launchpad.net/bugs/578868
You received this bug notification because you are a member of Ubuntu
Bugs, which is
apport information
** Attachment added: ProcCpuinfo.txt
http://launchpadlibrarian.net/48361128/ProcCpuinfo.txt
--
Lucid incompatible with HP Mini 110 BIOS (F.15)
https://bugs.launchpad.net/bugs/578868
You received this bug notification because you are a member of Ubuntu
Bugs, which is
apport information
** Attachment added: ProcInterrupts.txt
http://launchpadlibrarian.net/48361129/ProcInterrupts.txt
--
Lucid incompatible with HP Mini 110 BIOS (F.15)
https://bugs.launchpad.net/bugs/578868
You received this bug notification because you are a member of Ubuntu
Bugs, which is
apport information
** Attachment added: ProcModules.txt
http://launchpadlibrarian.net/48361130/ProcModules.txt
--
Lucid incompatible with HP Mini 110 BIOS (F.15)
https://bugs.launchpad.net/bugs/578868
You received this bug notification because you are a member of Ubuntu
Bugs, which is
apport information
** Attachment added: UdevDb.txt
http://launchpadlibrarian.net/48361133/UdevDb.txt
--
Lucid incompatible with HP Mini 110 BIOS (F.15)
https://bugs.launchpad.net/bugs/578868
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to
apport information
** Attachment added: RfKill.txt
http://launchpadlibrarian.net/48361131/RfKill.txt
--
Lucid incompatible with HP Mini 110 BIOS (F.15)
https://bugs.launchpad.net/bugs/578868
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to
apport information
** Attachment added: UdevLog.txt
http://launchpadlibrarian.net/48361135/UdevLog.txt
--
Lucid incompatible with HP Mini 110 BIOS (F.15)
https://bugs.launchpad.net/bugs/578868
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to
apport information
** Attachment added: WifiSyslog.txt
http://launchpadlibrarian.net/48361138/WifiSyslog.txt
--
Lucid incompatible with HP Mini 110 BIOS (F.15)
https://bugs.launchpad.net/bugs/578868
You received this bug notification because you are a member of Ubuntu
Bugs, which is
Okay -developers. All that stuff above isn't the bug, it's what it
looked like right after I loaded up Lucid netbook edition. Now I'm going
to hibernate without power and restore. Then I'll do it again. Good
luck!
--
Lucid incompatible with HP Mini 110 BIOS (F.15)
Well, I couldn't get that to come back at all. Hung early in the boot
process (just a cursor at upper left) regardless what regular thing I
did. Finally I convinced it to boot the Karmic UNR stick. When I
rebooted from that and chose the disk as the boot device, it resumed
from where it left off
apport information
** Attachment added: AlsaDevices.txt
http://launchpadlibrarian.net/48363939/AlsaDevices.txt
--
Lucid incompatible with HP Mini 110 BIOS (F.15)
https://bugs.launchpad.net/bugs/578868
You received this bug notification because you are a member of Ubuntu
Bugs, which is
apport information
** Attachment added: BootDmesg.txt
http://launchpadlibrarian.net/48363940/BootDmesg.txt
--
Lucid incompatible with HP Mini 110 BIOS (F.15)
https://bugs.launchpad.net/bugs/578868
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed
apport information
** Attachment added: Card0.Amixer.values.txt
http://launchpadlibrarian.net/48363943/Card0.Amixer.values.txt
--
Lucid incompatible with HP Mini 110 BIOS (F.15)
https://bugs.launchpad.net/bugs/578868
You received this bug notification because you are a member of Ubuntu
Bugs,
apport information
** Attachment added: Card0.Codecs.codec.0.txt
http://launchpadlibrarian.net/48363944/Card0.Codecs.codec.0.txt
--
Lucid incompatible with HP Mini 110 BIOS (F.15)
https://bugs.launchpad.net/bugs/578868
You received this bug notification because you are a member of Ubuntu
apport information
** Attachment added: IwConfig.txt
http://launchpadlibrarian.net/48363950/IwConfig.txt
--
Lucid incompatible with HP Mini 110 BIOS (F.15)
https://bugs.launchpad.net/bugs/578868
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed
apport information
** Attachment added: CurrentDmesg.txt
http://launchpadlibrarian.net/48363949/CurrentDmesg.txt
--
Lucid incompatible with HP Mini 110 BIOS (F.15)
https://bugs.launchpad.net/bugs/578868
You received this bug notification because you are a member of Ubuntu
Bugs, which is
apport information
** Attachment added: Lsusb.txt
http://launchpadlibrarian.net/48363952/Lsusb.txt
--
Lucid incompatible with HP Mini 110 BIOS (F.15)
https://bugs.launchpad.net/bugs/578868
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to
apport information
** Attachment added: PciMultimedia.txt
http://launchpadlibrarian.net/48363953/PciMultimedia.txt
--
Lucid incompatible with HP Mini 110 BIOS (F.15)
https://bugs.launchpad.net/bugs/578868
You received this bug notification because you are a member of Ubuntu
Bugs, which is
apport information
** Attachment added: Lspci.txt
http://launchpadlibrarian.net/48363951/Lspci.txt
--
Lucid incompatible with HP Mini 110 BIOS (F.15)
https://bugs.launchpad.net/bugs/578868
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to
apport information
** Attachment added: ProcInterrupts.txt
http://launchpadlibrarian.net/48363964/ProcInterrupts.txt
--
Lucid incompatible with HP Mini 110 BIOS (F.15)
https://bugs.launchpad.net/bugs/578868
You received this bug notification because you are a member of Ubuntu
Bugs, which is
apport information
** Attachment added: ProcCpuinfo.txt
http://launchpadlibrarian.net/48363960/ProcCpuinfo.txt
--
Lucid incompatible with HP Mini 110 BIOS (F.15)
https://bugs.launchpad.net/bugs/578868
You received this bug notification because you are a member of Ubuntu
Bugs, which is
apport information
** Attachment added: ProcModules.txt
http://launchpadlibrarian.net/48363965/ProcModules.txt
--
Lucid incompatible with HP Mini 110 BIOS (F.15)
https://bugs.launchpad.net/bugs/578868
You received this bug notification because you are a member of Ubuntu
Bugs, which is
apport information
** Attachment added: RfKill.txt
http://launchpadlibrarian.net/48363966/RfKill.txt
--
Lucid incompatible with HP Mini 110 BIOS (F.15)
https://bugs.launchpad.net/bugs/578868
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to
apport information
** Attachment added: UdevDb.txt
http://launchpadlibrarian.net/48363968/UdevDb.txt
--
Lucid incompatible with HP Mini 110 BIOS (F.15)
https://bugs.launchpad.net/bugs/578868
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to
apport information
** Attachment added: UdevLog.txt
http://launchpadlibrarian.net/48363970/UdevLog.txt
--
Lucid incompatible with HP Mini 110 BIOS (F.15)
https://bugs.launchpad.net/bugs/578868
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to
apport information
** Attachment added: WifiSyslog.txt
http://launchpadlibrarian.net/48363974/WifiSyslog.txt
--
Lucid incompatible with HP Mini 110 BIOS (F.15)
https://bugs.launchpad.net/bugs/578868
You received this bug notification because you are a member of Ubuntu
Bugs, which is
Excellent news! Kernel 2.6.34-999.201005121008 works and doesn't have
the problem!
--
Lucid incompatible with HP Mini 110 BIOS (F.15)
https://bugs.launchpad.net/bugs/578868
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs
Not so excellent news; restart failed after doing an update (I skipped
the kernel parts of the update).
--
Lucid incompatible with HP Mini 110 BIOS (F.15)
https://bugs.launchpad.net/bugs/578868
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to
Public bug reported:
Lucid Lynx 10.04 LTS does not start up well with the F.15 BIOS of HP
Mini 110. [This wasn't a problem before and is once again not a problem
now that I have reinstalled Karmic.]
The symptom is that if Lucid has been running on either the disk or a
UNE stick, attempting to
After an agonizing week of trying to understand what was wrong, I now
have a working Karmic system but without full restoration. I can't start
all this over again to load Lucid on the computer. Unfortunately, I can
find no way of saving output from those commands when running the UNE
that I can
82 matches
Mail list logo
