** Description changed:
- Whenever I turn on my headphones theyll connect to my computer but im
+ [Impact]
+
+ Whenever I turn on my headphones they'll connect to my computer but I'm
able to hear the input audio from my microphone and low quality output
audio. I have to disconnect the headpho
Patch for Ubuntu 19.10
** Patch added: "bluez_5.50-0ubuntu5.debdiff"
https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1845046/+attachment/5317845/+files/bluez_5.50-0ubuntu5.debdiff
** Changed in: bluez (Ubuntu Eoan)
Status: Triaged => Fix Committed
--
You received this bug n
** No longer affects: gnome-control-center (Ubuntu)
** Also affects: pulseaudio (Ubuntu Eoan)
Importance: Undecided
Status: New
** Also affects: bluez (Ubuntu Eoan)
Importance: Undecided
Status: New
** Changed in: bluez (Ubuntu Eoan)
Assignee: (unassigned) => Daniel van
[Expired for systemd (Ubuntu) because there has been no activity for 60
days.]
** Changed in: systemd (Ubuntu)
Status: Incomplete => Expired
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to systemd in Ubuntu.
https://bu
** Also affects: pulseaudio (Ubuntu Bionic)
Importance: Undecided
Status: New
** Also affects: gnome-control-center (Ubuntu Bionic)
Importance: Undecided
Status: New
** Also affects: bluez (Ubuntu Bionic)
Importance: Undecided
Status: New
** Changed in: bluez (Ubunt
When you say the trackpad still works, can you also click on things and
get them to respond?
If you get a response to the trackpad then this is probably a keyboard
bug to be assigned to the kernel. If you get no response from the
trackpad and can only move the cursor then this is probably a gnome-
It looks like the recurring problem here is indeed just Xorg:
[ 604.230] (EE) Backtrace:
[ 604.230] (EE) 0: /usr/lib/xorg/Xorg (OsLookupColor+0x13c) [0x5576c3d8facc]
[ 604.231] (EE) 1: /lib/x86_64-linux-gnu/libpthread.so.0 (funlockfile+0x60)
[0x7f6767b6359f]
[ 604.231] (EE) 2: /lib/x86_64
Thank you for taking the time to report this bug and helping to make
Ubuntu better. Unfortunately, we cannot work on this bug because your
description didn't include enough information. You may find it helpful
to read "How to report bugs effectively"
http://www.chiark.greenend.org.uk/~sgtatham/bugs
The other thing that changed in this area between 19.04 and 19.10 was
the kernel, so we need to rule that out first before pursuing
PulseAudio. Please try installing kernel 5.0.0 which is more like what
was in Ubuntu 19.04:
https://kernel.ubuntu.com/~kernel-ppa/mainline/v5.0/
Then run 'uname -a
** Summary changed:
- Xorg freeze with bluetooth mouse plugin, 19.10
+ System freeze with bluetooth mouse plugin, 19.10
** Package changed: xorg (Ubuntu) => linux (Ubuntu)
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to xorg
It seems this is a side effect of a mistake made in the release and
subsequent withdrawal of update 1:11.1-1ubuntu7.5. So it's not a bug in
the code but is a problem people will encounter with Ubuntu updates...
This should automatically correct itself with the re-release of
1:11.1-1ubuntu7.5. In t
There is no problem in the source code which says:
Package: libpulse-dev
Section: libdevel
Architecture: any
Multi-Arch: same
Depends: ${misc:Depends},
libpulse0 (= ${binary:Version}),
** Tags added: bionic
--
You received this bug notification because you are a member of Ubuntu
Touch seeded
Thank you for taking the time to report this bug and helping to make
Ubuntu better. It sounds like some part of the system has crashed. To
help us find the cause of the crash please follow these steps:
1. Look in /var/crash for crash files and if found run:
ubuntu-bug YOURFILE.crash
Then tell
Please be careful to only report one issue per bug report. It's OK to
open multiple bug reports.
Which issue would you like this bug to be about?
** Package changed: xorg (Ubuntu) => ubuntu
** Changed in: ubuntu
Status: New => Incomplete
--
You received this bug notification because you
We would like to see the system log from a frozen boot. To get that we
need to look at a negative boot ID. Please reproduce the freeze again
and then on the very next boot which doesn't freeze run:
journalctl -b-1 > prevboot.txt
Then send us the file 'prevboot.txt'.
** Summary changed:
- Xor
The fix for 19.10 is queued and on the way:
https://launchpad.net/ubuntu/eoan/+queue?queue_state=1
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to pulseaudio in Ubuntu.
https://bugs.launchpad.net/bugs/1847570
Title:
PulseAu
Well, thanks anyway for looking into it. It's disappointing, but I can
totally understand why this won't be backported if the patch is that
complex and touches that many other packages. I'll just use the
workaround until I get the updated Qt stack in 20.04.
--
You received this bug notification
This bug is closed so if you still experience problems then please open
a new bug by running:
ubuntu-bug pulseaudio
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to pulseaudio in Ubuntu.
https://bugs.launchpad.net/bugs/18162
Can this package get updated to 1.9.13, or at least patched in time for
20.04? The security exploitability of this bug may be low, but the impact
on affected users is high. It causes hard to debug, random crashes of other
programs (e g. Kodi) that are scanning ALSA devices when the jack daemon
isn'
Sven, here are the workaround steps (as root) :
1) Create the folder '/etc/systemd/user/gnome-terminal-server.service.d' (with
usual mode 755).
2) In this newly created folder, create the 'umask.conf' file with following
content :
[Service]
UMask=
--
You received this bug notification bec
Question Answers:
1. Windows 10 laptop core i7 Microsoft Windows [Version 10.0.17763.914]
2. TERM=xterm
3.
write(1,
"\33[?1049h\33[22;0;0t\33[1;47r\33(B\33[m\33[4l\33[?7h\33[39;49m\33[?1h\33=",
54) = 54
write(1, "\33[?1h\33=", 7) = 7
write(1, "\33[?1h\33=", 7) = 7
wr
Public bug reported:
The Ubuntu Error Tracker has been receiving reports about a problem regarding
tracker. This problem was most recently seen with package version 2.3.1-1, the
problem page at
https://errors.ubuntu.com/problem/ae2e8393101fd16b6c88d15f22ec43828be91c66
contains more details, i
Public bug reported:
The Ubuntu Error Tracker has been receiving reports about a problem regarding
evolution-data-server. This problem was most recently seen with package
version 3.34.1-1build1, the problem page at
https://errors.ubuntu.com/problem/1fe5b6b206c2db7112df2b401761c7188a1ddab2
con
Any chance that this patch can get released into Eoan? It is an
upstream patch.
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to nano in Ubuntu.
https://bugs.launchpad.net/bugs/1853825
Title:
^W ^G ^X fails to redisplay the
As the patch for bug #1641592 has been released to Xenial, it means that
this bug has been fixed too.
** Changed in: nano (Ubuntu)
Status: Confirmed => Fix Released
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to nano
is there now a solution that works under Ubuntu 19.10?
/etc/systemd/user/gnome-terminal-server.service.d/umask.conf
The path from "gnome-terminal-server.service.d" does not exist here at
all.
The problem should be solved after such a long time :-( Is there a
plan how the problem can be solv
Public bug reported:
Since two to three weeks, my keyboard sometimes becomes unresponsive after wake
up from resume. Often it is associated with an @ sign on black background, when
the machine is resumed.
After that I am back in the desktop. Trackpad and everything works, but the
keyboard does
Public bug reported:
After doing a normal installation with erasing the disk in GNOME Boxes,
I cannot log into the Ubuntu Xorg session. Wayland works fine, but this
still isn't a workaround if the user wants to use Xorg for any given
reason.
ProblemType: Bug
DistroRelease: Ubuntu 20.04
Package: x
Thanks for reporting. Please answer the following questions.
1) From what kind of machine are you putty'ing into your Ubuntu 18.04
machines?
2) When putty'ed in, what is the output of 'env | grep TERM'?
3) When putty'ed in, please run 'strace -ewrite -s2000 /bin/nano
--ignore 2>TRAIL', paste yo
** Branch unlinked: lp:~vcs-imports-ii/freefont/trunk
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to fonts-freefont in Ubuntu.
https://bugs.launchpad.net/bugs/1558899
Title:
Recent recipe version of FreeFont were failed to
30 matches
Mail list logo
