Can some1 tell me when this fix will hit ubuntu 14.04 ? thx
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to unity in Ubuntu.
https://bugs.launchpad.net/bugs/1072206
Title:
[nvidia] Window content is black or transparent
14.04, affected by the bug, manually starting NetworkManager helps, but
I do get the error message:
http://postimg.org/image/c9z0at29z/
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to network-manager in Ubuntu.
What I see is similar, but not identical to Gábor's description:
Feb 24 14:51:10 tena kernel: [ 761.070735] CPU: 0 PID: 1132 Comm: Xorg
Tainted: GW 4.4.
0-64-generic #85~14.04.1-Ubuntu
Feb 24 14:51:10 tena kernel: [ 761.070736] Hardware name: Dell Inc. Latitude
E5570/0R3VX4,
#1594591 might be related.
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to bluez in Ubuntu.
https://bugs.launchpad.net/bugs/1594939
Title:
Sound over bluetooth is stuttering
Status in bluez package in Ubuntu:
Confirmed
I encounter sound over bluetooth stuttering as well. Ubuntu 14.04,
bluetooth in A2DP mode. I get the vague feeling that the stuttering gets
worse when the system is active, but sometimes it's the CPU, sometimes
the WiFi...sometimes no obvious reason.
I'm 3m away from a receiver in line of sight,
Public bug reported:
I can play via bluetooth from my laptop or my mobile phone. I have a set
of bluetooth headphones and bluetooth speakers.
Any combination of output with the smartphone as the player works, which
is as it should be.
Any combination of output with the laptop as the player is
@Daniel Thank you, will see where I get with
sudo modprobe ath10k_core btcoex_enable=1 bt_ant_diversity=1
as seems to have been suggested under the related bug.
Will try 5GHz and disabling WiFi, but the latter can obviously only be a
temporary diagnostics step.
--
You received this bug
** Attachment added: "lsusb.txt"
https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1873086/+attachment/5356583/+files/lsusb.txt
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to pulseaudio in Ubuntu.
Adding lsusb output.
** Attachment added: "lspci.txt"
https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1873086/+attachment/5356582/+files/lspci.txt
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to pulseaudio in
Public bug reported:
I connect to a bluetooth speaker.
Observed behaviour: connection established, but sound still continues to
come from the built-in speakers and when looking at available sound
outputs in the gnome-control-center, there are no new outputs.
Expected behaviour: connection
Public bug reported:
I have a Logitech bluetooth mouse (M650) and keyboard (K380, details in
the attached log). I almost never power down the laptop: I suspend and
resume it.
Sometimes when I resume from suspend everything works flawlessly. Other
times, there's a 2-3s "freeze" after just several
I see a similar (same?) issue: if I say a bug is display-related, apport
collecting problem information hangs ~20% through the process and
neither "Cancel" nor (x) can stop the process. Cancel in the parent
window helps.
This is on 20.04.
--
You received this bug notification because you are a
Public bug reported:
Had trouble connecting my K380 keyboard with the laptop (previously used
it without issues), unpaired and now I can no longer pair it.
Other bluetooth devices work with this particular laptop (mouse,
earbuds), the keyboard works flawlessly with a different laptop (running
Forgot to mention: I use this utility to invert Fn key behaviour:
https://github.com/jergusg/k380-function-keys-conf
...and it's set up to start on boot using a variant of the procedure
described here:
https://github.com/embuc/k480_conf
My /etc/udev/rules.d/80-k380.rules looks as follows:
That's generally possible, but unlikely, given that everything worked
well for a couple of months and then suddenly stopped working altogether
(rather than occasionally).
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to bluez
Thanks for responding, Daniel. If it was the driver, I don't know how
the keyboard would have worked until a week ago. If it was the hardware,
I imagine other BT devices wouldn't connect either, but they do (mouse,
earbuds). I might be wrong, of course.
--
You received this bug notification
Any other ideas, anything I can do to help diagnostics?
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to bluez in Ubuntu.
https://bugs.launchpad.net/bugs/2000798
Title:
cannot connect to K380 bluetooth keyboard
Status in
17 matches
Mail list logo
