While debugging an unrelated issue with printing to my HP LaserJet 1012,
I switched from the "hpcups" driver to the "hpijs" driver, and I am
**BLOWN AWAY** by the quality of its dithering. After seeing the
difference, I am absolutely appalled at how poorly the "hpcups" driver
dithers grayscales. I
This bug (if it's a bug) also affects sys-libs/glibc-2.23-r3 on Gentoo.
The Qt Blog has a post about this issue from 2011:
http://blog.qt.io/blog/2011/10/28/rpath-and-runpath/
This may not be a bug: it is possible that DT_RUNPATH was never intended
to be transitive. However, if this is so, then
Oh, and for what it's worth, the same test runs fine on Amazon Linux,
which is running kernel 3.4.57-48.42.amzn1.x86_64. There are no skb
rides the rocket messages when the test is run on Amazon Linux, only
when it's run on Ubuntu.
--
You received this bug notification because you are a member
I'm seeing this on 3.8.0-19-generic at Amazon EC2 as well. It's very
reproducible (happens every time), and it causes a bizarre
(theoretically impossible) state for my sockets. I have a client and a
server on separate machines, both running Ubuntu 13.04 on EC2, and
shortly into a stress test, all
Seth Forshee pointed out that input_mt_report_pointer_emulation exists
for this purpose, so I've switched to it. Tested working.
** Patch added: new version of patch using input_mt_report_pointer_emulation
Public bug reported:
This patch resolves a shortcoming of the ektf3k driver. Previously, the
driver was reporting only multi-touch events. xf86-input-evdev 2.7.3
crashes upon receiving input events from the driver, and 2.8.1 simply
ignores the input device altogether as a workaround for the
This is happening to me on Gentoo with KDE 4.2.2 and Amarok 2.0.90, so
it's not limited to Ubuntu. Very aggravating, since not only does it
skip every other song, but it tells Last.fm that I actually listened to
the song it skipped, and it bumps up the score and play count of the
skipped song as
I have been in communications with Trolltech about this, and here is
their preliminary response:
We're still not convinced that this is a bug in Qt at all.
Can you run an application that calls somewhere in the beginning:
qApp-setDesktopSettingsAware(false);
See
