Updated kernel to 3.8.4 (latest stable; dated 2013-03-20) and receive
the same errors as on previous versions (every 5 seconds):
[ 11.482307] xhci_queue_intr_tx: 71 callbacks suppressed
[ 16.594634] xhci_queue_intr_tx: 76 callbacks suppressed
[ 21.707011] xhci_queue_intr_tx: 72 callbacks sup
I also found a few of these, which is identical to the error the
original poster was receiving:
xhci_hcd :00:14.0: WARN Event TRB for slot 1 ep 6 with no TDs
queued?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.lau
I'm running 3.7.6 on a Samsung Chronos 7 (780Z) laptop and get flooded
with these:
[28568.301952] xhci_queue_intr_tx: 74 callbacks suppressed
[28573.414409] xhci_queue_intr_tx: 74 callbacks suppressed
[28578.526801] xhci_queue_intr_tx: 74 callbacks suppressed
[28583.639180] xhci_queue_intr_tx: 74
I first noticed this problem when I started running Conky. However, it
had nothing to do with Conky itself, but rather with the rule I put in
ccsm (CompizConfig Settings Manager) to disable shadows on the Conky
window [i.e. Window Decorations -> Shadow Windows = (any) &
!(class=Conky)]. This caus
> Ok, it was just that "wasting time on things like Unity"
> seamed a bit rude an unnecessary.
I hear you. My point wasn't that Ubuntu should not be pursuing new
features but, rather, that they need to get basic functionality working
and stable first. It just seems that, all too often, we just
> Dean negative comments rarely gets positive results
I wouldn't characterize my comment as negative. It was an appeal to
whoever should be fixing this to give it a higher priority than a simple
'cosmetic' issue. And disabling Compiz is not an option since it's
providing many other essential acc
ATTENTION DEVELOPERS: You may be treating this as a low-priority item
simply because you believe it to be cosmetic in nature. However, you
need to be treating this as an accessibility issue and giving it a
little more attention than it has gotten over the past several years
that this defect has sta
*** This bug is a duplicate of bug 86184 ***
https://bugs.launchpad.net/bugs/86184
ATTENTION DEVELOPERS: You may be treating this as a low-priority item
simply because you believe it to be cosmetic in nature. However, you
need to be treating this as an accessibility issue and giving it a
litt
Exact same problem here ("An internal error occurred" when trying to
copy CD) on a desktop machine that was upgraded from 9.10 to 10.04.
--
Brasero can't copy CDs or create images from them (Ubuntu 10.04)
https://bugs.launchpad.net/bugs/585941
You received this bug notification because you are a
Yes, I'm not sure why it got assigned as a Firefox issue (that's
actually the one place where behavior is as expected). Does it
automatically scan the description for hints?
--
Specified mouse pointer size broken in Lucid
https://bugs.launchpad.net/bugs/579704
You received this bug notification b
** Attachment added: "Dependencies.txt"
http://launchpadlibrarian.net/48357428/Dependencies.txt
** Attachment added: "ExtensionSummary.txt"
http://launchpadlibrarian.net/48357429/ExtensionSummary.txt
** Attachment added: "profile_default_pluginreg.dat.txt"
http://launchpadlibrarian.net/
Public bug reported:
Binary package hint: firefox
In the Appearance Preferences -> Customize Theme -> Pointer dialog,
mouse pointers like DMZ (White) or DMZ (Black) allow the pointer size to
be specified. Lucid is ignoring the setting and always defaults to the
smallest size. I've confirmed that
Of course, I meant Ubuntu 9.04, not 9.10.
--
Very weak signal using ath9k compared to Windows driver on same machine
https://bugs.launchpad.net/bugs/379861
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing list
ubun
Public bug reported:
This is on a Fujitsu u820 with the AR928X wireless chipset. If I boot
Windows Vista I get a strong signal (typically 85% - 92%). When I boot
into Ubuntu 9.10 using the ath9k driver I can connect fine, but I only
get between 10% and 16% strength. Also, annoying disconnects are
Travis, I don't understand why you keep saying that "you can't interact
with things when Zoom Area Lock is enabled." The fact is, you *can* --
as long as the "Scale the mouse pointer" option is enabled. Please try
it and you'll see. (Strictly speaking you can also interact using the
unscaled poin
Travis, sorry, but that makes absolutely no sense whatsoever. There are
countless reasons why you would want and need to interact with the
screen while locked. Training presentations are just one example. When
connected to a projector, it is often helpful to zoom into part of an
application window
There definitely is a bug here (actually more than one), but I don't
believe it's as described above.
Everything works fine as long as 'Zoom Area Lock' is not selected in
that mouse clicks register in the correct position. If the 'Zoom Area
Lock' option is enabled, however, the mouse clicks do not
17 matches
Mail list logo
