** 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
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
Additional Notes:
The bug may related to the bug report:
https://bugs.documentfoundation.org/show_bug.cgi?id=120796
Everything goes fine after it was changed from .txt to .csv.
** Bug watch added: Document Foundation Bugzilla #120796
https://bugs.documentfoundation.org/show_bug.cgi?id=120796
Public bug reported:
The situation found when I try to covert a txt file into Calc file by
libreoffice. The preview looks all fine, all the tabs and texts were
well arranged in the preview. However, when the button "ok" was pressed,
libreoffice use all the memory and CPU, even the txt file only
** 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 firefox (Ubuntu) because there has been no activity for 60
days.]
** Changed in: firefox (Ubuntu)
Status: Incomplete => Expired
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to firefox in Ubuntu.
[Expired for chromium-browser (Ubuntu) because there has been no
activity for 60 days.]
** Changed in: chromium-browser (Ubuntu)
Status: Incomplete => Expired
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to chromium-browser in
I was able to fix this on Ubuntu 18.04 (bionic), which comes with
libmtp-common=1.1.13 by installing a newer version of libmtp 1.1.16.
Now Ubuntu transfers huge numbers of songs between my phone and laptop
by simply drag-and-drop in Nautilus.
sudo apt install build-essential pkg-config wget
** 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
Please report the issue to the upstream developers here:
https://gitlab.freedesktop.org/groups/xorg/-/issues
and then tell us the new issue ID.
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to xorg-server in Ubuntu.
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:
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
Thank you for reporting this bug to Ubuntu.
Ubuntu 13.04 (raring) reached end-of-life on January 27, 2014.
See this document for currently supported Ubuntu releases:
https://wiki.ubuntu.com/Releases
We appreciate that this bug may be old and you might not be interested
in discussing it any
If the GUI is frozen but the mouse moves then this means it is the
gnome-shell process that has frozen or crashed. The mouse can still move
because that is done by Xorg.
...
Thank you for taking the time to report this bug and helping to make
Ubuntu better. It sounds like some part of the system
The the GUI is frozen but the mouse moves then this means it is the
gnome-shell process that has frozen or crashed. The mouse can still move
because that is done by Xorg.
...
Thank you for taking the time to report this bug and helping to make
Ubuntu better. It sounds like some part of the
** Description changed:
https://errors.ubuntu.com/problem/4de849dfec89af168af9cda3318221a2a654e530
+ https://errors.ubuntu.com/problem/4c203db78dea0a68c29cbd981d4abbd4aef31851
---
No idea what happened.
ProblemType: Crash
DistroRelease: Ubuntu 16.04
Package: xserver-xorg-core
** Bug watch added: github.com/micheleg/dash-to-dock/issues #689
https://github.com/micheleg/dash-to-dock/issues/689
** Also affects: dash-to-dock via
https://github.com/micheleg/dash-to-dock/issues/689
Importance: Unknown
Status: Unknown
** Project changed: dash-to-dock =>
*** This bug is a duplicate of bug 1543192 ***
https://bugs.launchpad.net/bugs/1543192
** Summary changed:
- /usr/lib/xorg/Xorg:6:raise:abort:OsAbort:AbortServer:FatalError
+ Xorg crashed with SIGABRT in raise() from abort() from OsAbort() from
AbortServer() from FatalError()
** Summary
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"
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
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
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 Desktop
Packages,
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
** 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 Desktop
Packages, which is subscribed to xorg in Ubuntu.
If the problem really was mutter#655 then this would be a duplicate of
bug 1844222. But you seem to have the fix for that already (mutter
3.34.2) so it sounds like this is not mutter#655.
Can you please provide a screenshot or photo of the issue?
** Bug watch added: Mozilla Bugzilla #1604948
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
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:
-
Thank you for reporting this bug to Ubuntu.
Ubuntu 10.10 (maverick) reached end-of-life on April 10, 2012.
See this document for currently supported Ubuntu releases:
https://wiki.ubuntu.com/Releases
We appreciate that this bug may be old and you might not be interested
in discussing it any
This does not occur when using podman 1.4.4, must be a nuance of Docker
1.13.1.
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to mono in Ubuntu.
https://bugs.launchpad.net/bugs/1852870
Title:
core dumps when installing mono-devel in
Thanks. It appears this is a simple Xorg crash:
Jan 02 08:09:39 ektorp /usr/lib/gdm3/gdm-x-session[4553]: (EE)
Jan 02 08:09:39 ektorp /usr/lib/gdm3/gdm-x-session[4553]: (EE) Backtrace:
Jan 02 08:09:39 ektorp /usr/lib/gdm3/gdm-x-session[4553]: (EE) 0:
/usr/lib/xorg/Xorg (OsLookupColor+0x139)
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
** No longer affects: netspeed (Ubuntu)
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to gnome-shell in Ubuntu.
https://bugs.launchpad.net/bugs/1857660
Title:
The offending signal was destroy on Gjs_ExtensionRow
Status in gnome-shell
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 Desktop
Packages, which is subscribed to pulseaudio in Ubuntu.
https://bugs.launchpad.net/bugs/1847570
Title:
PulseAudio
Sounds like it's maybe connected to a hardware multiplexer ("mux"). I
don't have experience with such systems, but you might find it useful to
look at these:
https://wiki.archlinux.org/index.php/Hybrid_graphics
\https://01.org/linuxgraphics/gfx-docs/drm/gpu/vga-switcheroo.html
--
You received
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 Desktop
Packages, which is subscribed to pulseaudio in Ubuntu.
https://bugs.launchpad.net/bugs/1816271
Title:
** Bug watch added: gitlab.freedesktop.org/libinput/libinput/issues #158
https://gitlab.freedesktop.org/libinput/libinput/issues/158
** Also affects: libinput via
https://gitlab.freedesktop.org/libinput/libinput/issues/158
Importance: Unknown
Status: Unknown
--
You received this
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
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
Public bug reported:
Single-day events on 1st of month show on all days of preceding month.
For example, someone's birthday on April 1 will show up (in the month
view) as being a month-long event during all of March.
I am using a NextCloud calendar. The events look OK on the NextCloud
Public bug reported:
The Ubuntu Error Tracker has been receiving reports about a problem regarding
gnome-settings-daemon. This problem was most recently seen with package
version 3.34.1-1ubuntu2, the problem page at
https://errors.ubuntu.com/problem/3d7933d46e17d4d2ab4cdba47c09ba3f0cb34cf5
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
Public bug reported:
The Ubuntu Error Tracker has been receiving reports about a problem regarding
chromium-browser. This problem was most recently seen with package version
79.0.3945.79-0ubuntu0.19.04.3, the problem page at
Public bug reported:
The Ubuntu Error Tracker has been receiving reports about a problem regarding
nautilus. This problem was most recently seen with package version
1:3.34.1-1ubuntu1, the problem page at
https://errors.ubuntu.com/problem/d27a750c5eaf7972c99c001fbb86cb2e6500594f
contains
Public bug reported:
The Ubuntu Error Tracker has been receiving reports about a problem regarding
gjs. This problem was most recently seen with package version 1.58.1-1, the
problem page at
https://errors.ubuntu.com/problem/897036aa239708c7e78ec460a8bc7c9571d61b3a
contains more details,
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,
Public bug reported:
The Ubuntu Error Tracker has been receiving reports about a problem regarding
xorg-server. This problem was most recently seen with package version
2:1.20.5+git20191008-0ubuntu1, the problem page at
Public bug reported:
The Ubuntu Error Tracker has been receiving reports about a problem regarding
nautilus. This problem was most recently seen with package version
1:3.26.4-0ubuntu9, the problem page at
https://errors.ubuntu.com/problem/8625807832947f023e918eb923eaac89cd468993
contains
Public bug reported:
There is a patch available via this link.
https://w3logistics.com/blog/archives/438-EAP-MSCHAPv2-for-pppd-2-4-7.html
Adding support for EAP-MSCHAPv2 to this would be very helpful for sstp-
client project to connect to an Azure instance.
** Affects: ppp (Ubuntu)
** Bug watch added: gitlab.gnome.org/GNOME/mutter/issues #997
https://gitlab.gnome.org/GNOME/mutter/issues/997
** Also affects: mutter via
https://gitlab.gnome.org/GNOME/mutter/issues/997
Importance: Unknown
Status: Unknown
--
You received this bug notification because you are a
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
I get this quite regularly, thanks to the participants of this for the
work around, very useful. But this is definitely still a problem.
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to gnome-shell-extension-ubuntu-dock in
Ubuntu.
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
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:
Public bug reported:
Following info from about:sync-log
```
1578230581042 Sync.LogManager DEBUG Flushing file log
1578230581043 FirefoxAccounts DEBUG FxAccountsProfileClient: Requested
profile
1578230581043 FirefoxAccounts DEBUG getOAuthToken enter
1578230581047 FirefoxAccounts
Public bug reported:
Entire system froze
only mouse moved
left click no response
right click no response
keyboard not responding
could not access terminal via ctrl + alt +f2 or ctrl + alt + sys rq etc.
here's the video
https://www.youtube.com/watch?v=byaYLD9zyMU
ProblemType: Bug
DistroRelease:
Using Kubuntu 19.10 with KDE 5.17 (via backports) with Firefox 71. This
seems to be the case to me as well. Won't open Dolphin from download.
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to firefox in Ubuntu.
Crashed few times today and yesterday, /var/crash is empty :(
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to gnome-shell in Ubuntu.
https://bugs.launchpad.net/bugs/1853199
Title:
Ctrl + c (copy) anywhere some times crashes gnome
With version 0.8.09-0ubuntu0ppa1535-ubuntu19.10.1 (eoan) deja-dup now
seems to start to work as a normal user, but I need to backup some root
stuff, and when run under sudo or pkexec I get the following
immediately:
Traceback (innermost last):
File "/usr/bin/duplicity", line 101, in
I also get this on a fresh install of Ubuntu 19.10 on one of the two machines I
use (laptop with wifi is fine, desktop with wired connection is buggy, I used
the same USB for install). My internet connection is fine, but some of the
websites I want to get on are blocked (e.g. mobile banking,
** Branch unlinked: lp:~vcs-imports-ii/freefont/trunk
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to fonts-freefont in Ubuntu.
https://bugs.launchpad.net/bugs/1558899
Title:
Recent recipe version of FreeFont were failed to build
60 matches
Mail list logo
