*** This bug is a duplicate of bug 1888598 ***
https://bugs.launchpad.net/bugs/1888598
Likeit is hardcoded...really? Why?
https://gitlab.freedesktop.org/pulseaudio/pulseaudio/-/blame/master/src/modules/module-switch-on-connect.c#L36
--
You received this bug notification because you are
It appeared today, after rebooting with the latest kernel, however I
have not updated procps since some time now and it was working before
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to procps in Ubuntu.
There still one problem.
When I plug in the headphones (with 3 pins no-mic or 4 pins with mic) it
switches the Input to "Microphone (plugged-in)" and strangely enough
there is no sound at all on the headphones.
If I change the microphone setting to anything "Internal Microphone
(plugged in)" or
Indeed 20.04 still has the problem
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to vim in Ubuntu.
https://bugs.launchpad.net/bugs/1833174
Title:
Shadowing the vim-window results in vim-gtk3 crash
Status in vim package in
Checking a bit more, I've realized the following:
- After a reboot, the microphone is not detected and nothing is proposed in
pavucontrol
- If I plug any headphone (3-pins without mic) then the "Internal
microphone" device appears. Which doesn't also don't work (neither
output nor input). After
Public bug reported:
After upgrade from 19.10 to 20.04 (xubuntu) I've lost the sound on the
headphones.
The internal loud speakers works ok when the headphones are not plugged in.
More specifically:
If I open the pavucontrol without the headphones plugged in I see that is
correctly mentioning
** Package changed: linux (Ubuntu) => bluez (Ubuntu)
--
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/1853567
Title:
Bluetooth keyboard after upgrade consumes rapidly battery
Public bug reported:
With XFCE when I try to "shadow" the vim-gtk3 window (just to show only the
title bar) it results in a vim crash and the window just disappears without any
core dump neither .swp files on.
The only message I get on the terminal is
BadMatch (invalid parameter attributes)
Same problem here!
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to apport in Ubuntu.
https://bugs.launchpad.net/bugs/160999
Title:
Apport doesn't overwrite existing core files
Status in apport package in Ubuntu:
Public bug reported:
I am running xubuntu 18.04 and when I click the "shade" button of gvim
frame the window disappears with gvim crashing. It happens only to gvim
all other windows I've tested are ok
ProblemType: Bug
DistroRelease: Ubuntu 18.04
Package: vim-gtk3 2:8.0.1453-1ubuntu1
The error message I get:
BadMatch (invalid parameter attributes)
Vim: Got X error
Vim: Finished.
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to vim in Ubuntu.
https://bugs.launchpad.net/bugs/1785813
Title:
gvim crashes
This is what I am running right now (v4.15-rc1) and the keyboard is reporting 0%
Linux pceet070.cern.ch 4.15.0-041500rc1-generic #201711262030 SMP Mon Nov 27
01:32:09 UTC 2017 x86_64 x86_64 x86_64 GNU/Linux
--
You received this bug notification because you are a member of Ubuntu
Touch seeded
I've tried the kernels from
http://kernel.ubuntu.com/~kernel-ppa/mainline/?C=N;O=D
and the last one that I found workding was the 4.14.52,
I presume that the next one is the 4.15.rc1, which shows the problem.
Are there somewhere more builds in between those two that I can search?
--
You
Moved to v4l
** Package changed: bluez (Ubuntu) => libv4l (Ubuntu)
--
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/1770643
Title:
Logitech QuickCam 4000 Pro halts system
Sorry this is for v4l, by mistake I filled it under bluez
--
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/1770643
Title:
Logitech QuickCam 4000 Pro halts system
Status in
Public bug reported:
After switching from Fedora to Ubuntu (17.10 and now 18.04),
whenever I plug my Logitech QuickCam 4000 Pro USB webcam
and I start vlc or any other camera capture program, the memory of
the program increases to maximum, as a consequence the system halt
and the only way out is
I am using the 4.15.0-20-generic. Just to clarify with this kernel after reboot
it doesn't report the battery on the keyboard, however letting my desktop on
for 2 days
it started reporting.
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is
Indeed with the new update my keyboard started reporting back
--
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/1769075
Title:
[regression][bionic] Bluetooth keyboard battery
The latest that I've tried and it works is 4.14.40-041440
Anything later from 4.15.xx fails
--
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/1769075
Title:
** Changed in: linux (Ubuntu)
Status: Incomplete => Confirmed
--
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/1769075
Title:
[regression][bionic] Bluetooth keyboard
apport information
** Attachment added: "WifiSyslog.txt"
https://bugs.launchpad.net/bugs/1769075/+attachment/5135278/+files/WifiSyslog.txt
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to bluez in Ubuntu.
apport information
** Attachment added: "PulseList.txt"
https://bugs.launchpad.net/bugs/1769075/+attachment/5135276/+files/PulseList.txt
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to bluez in Ubuntu.
apport information
** Attachment added: "ProcModules.txt"
https://bugs.launchpad.net/bugs/1769075/+attachment/5135275/+files/ProcModules.txt
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to bluez in Ubuntu.
apport information
** Attachment added: "UdevDb.txt"
https://bugs.launchpad.net/bugs/1769075/+attachment/5135277/+files/UdevDb.txt
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to bluez in Ubuntu.
apport information
** Attachment added: "ProcInterrupts.txt"
https://bugs.launchpad.net/bugs/1769075/+attachment/5135274/+files/ProcInterrupts.txt
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to bluez in Ubuntu.
apport information
** Attachment added: "ProcEnviron.txt"
https://bugs.launchpad.net/bugs/1769075/+attachment/5135273/+files/ProcEnviron.txt
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to bluez in Ubuntu.
apport information
** Attachment added: "ProcCpuinfo.txt"
https://bugs.launchpad.net/bugs/1769075/+attachment/5135271/+files/ProcCpuinfo.txt
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to bluez in Ubuntu.
apport information
** Attachment added: "Lspci.txt"
https://bugs.launchpad.net/bugs/1769075/+attachment/5135269/+files/Lspci.txt
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to bluez in Ubuntu.
apport information
** Attachment added: "ProcCpuinfoMinimal.txt"
https://bugs.launchpad.net/bugs/1769075/+attachment/5135272/+files/ProcCpuinfoMinimal.txt
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to bluez in Ubuntu.
apport information
** Tags added: apport-collected
** Description changed:
I've recently upgraded to 18.04 from 17.10 and after the upgrade "upower -d"
reports always 0% as battery percentage of the bluetooth Logitech K810
keyboard.
Which is a bit annoying since I get a KDE warning on
apport information
** Attachment added: "CurrentDmesg.txt"
https://bugs.launchpad.net/bugs/1769075/+attachment/5135268/+files/CurrentDmesg.txt
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to bluez in Ubuntu.
apport information
** Attachment added: "CRDA.txt"
https://bugs.launchpad.net/bugs/1769075/+attachment/5135267/+files/CRDA.txt
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to bluez in Ubuntu.
apport information
** Attachment added: "Lsusb.txt"
https://bugs.launchpad.net/bugs/1769075/+attachment/5135270/+files/Lsusb.txt
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to bluez in Ubuntu.
$ echo /sys/class/power_supply/*/capacity
/sys/class/power_supply/hid-34:88:5d:5e:0c:2f-battery/capacity
--
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/1769075
Title:
Of course, here it is
~$ grep . /sys/class/power_supply/*/capacity
0
--
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/1769075
Title:
Upgrade to 18.04 broke the battery
** Package changed: ubuntu => bluez (Ubuntu)
--
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/1769075
Title:
Upgrade to 18.04 broke the battery reporting of bluetooth
Public bug reported:
error came up during distro upgrade from 16.04 to 18.04
ProblemType: Package
DistroRelease: Ubuntu 18.04
Package: fontconfig 2.12.6-0ubuntu2
ProcVersionSignature: Ubuntu 4.15.0-20.21-generic 4.15.17
Uname: Linux 4.15.0-20-generic x86_64
ApportVersion: 2.20.9-0ubuntu7
0008047a20e0
trb-start 0008047a3f30 trb-end 0008047a3f30 seg-start 0008047a3000
seg-end 0008047a3ff0
Please let me know what other tests I can perform to further debug the problem
Thanks in advance
Vasilis
** Affects: v4l-utils (Ubuntu)
Importance: Undecided
Status
Update. I replaced my USB bluetooth dongle Bluetooth V4.0 to a very old
one V2.0 and since a week now I have no problems with any keyboard or
with the mouse.
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to bluez in Ubuntu.
I've tried changing the power management from auto to on of the
bluetooth driver but with no success as well.
If you have ideas on what to check, I am willing to test it. I like a
lot the form factor of the small BT keyboard, and I would like to find a
solution
--
You received this bug
I've tried also (something reported to other sites)
sudo sh -c 'echo N > /sys/module/drm_kms_helper/parameters/poll'
with no success
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to bluez in Ubuntu.
I'e trrrid
also "scan off" with no success
(first line from the BT keyboard)
--
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/1454450
Title:
I have the same issue laggy only (no disconnects) with all my bluetooth HID
devices, and it is the same on both Ubuntu 17.04 as well fedora core 25.
- Keyboard logitech K810
- Mac keyboard
- Dell BT mouse
The problem did not exist on very old versions of bluez at least with
the Mac keyboard.
Public bug reported:
I am trying to connect to a TLS network. I have the .p12 private key
however it is impossible to select it from NetworkManager. When I click
on the "Private Key" and it opens the dialog, I navigate to the
directory with the key and it doesn't appear even though it is there.
44 matches
Mail list logo
