Ok, 42.6 uploaded to hirsute and SRUed now
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to deja-dup in Ubuntu.
https://bugs.launchpad.net/bugs/1902044
Title:
SRU the current 42.5 stable update
Status in deja-dup package in Ubuntu:
It's not under the GNOME MRE no, just a micro release update worth
SRUing for the fixes it includes. The .6 update is newer than the upload
in the queue but we should get the current version so feel free to
reject .5 and I will upload the new one today
** Changed in: deja-dup (Ubuntu Groovy)
Yes, that's the part of the changelog
' * debian/patches/revert_vino_deprecated.patch:
- revert the upstream change to remove the vino control option, it's
still working in Ubuntu because we reverted the g-s-d commit
which deprecated the backend handling'
** Changed in:
Oh sorry, it looks like you reverted this in your upload.
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to gnome-control-center in Ubuntu.
https://bugs.launchpad.net/bugs/1905740
Title:
SRU the current 3.36.5 stable update
Status in
Most of this looks fine but I'm concerned about this upstream changelog
item:
sharing: Replace vino with gnome-remote-desktop for X11 sessions
It looks like that was done because of a problem with Wayland only.
Changing behaviour for X11 that isn't for the purpose of fixing a bug is
something
Also 42.6 includes:
- Exclude snap and flatpak cache files (fixed regression that stopped
doing this)
Would this be a regression introduced by this upload?
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to deja-dup in Ubuntu.
I'm not clear on whether you want to update deja-dup on the basis of the
GNOME MRE or not.
If you intend to base this on the GNOME MRE, then I don't see this in
the current working list of included packages at
https://discourse.ubuntu.com/t/scope-of-gnome-mru/18041/8?u=rbasak so if
you want to
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
FTR, I would strongly advise against that, see
https://github.com/martinpitt/umockdev/issues/110#issuecomment-736224503
. You want the tests to work independently on the hardware it's running
on, so that you can run it on e.g. standard autopkgtest infra.
You could create
** Tags added: focal
** Also affects: libevdev (Ubuntu)
Importance: Undecided
Status: New
** Also affects: linux (Ubuntu)
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to libevdev in
This bug was fixed in the package software-properties - 0.99.4
---
software-properties (0.99.4) hirsute; urgency=medium
* cloudarchive: Enable support for the Wallaby Ubuntu Cloud Archive on
20.04 (LP: #1902710).
-- Corey Bryant Tue, 03 Nov 2020 08:58:47
-0500
** Changed
Public bug reported:
[Impact]
* The touchpad's right button become no function after update to 5.4
kernel
* The INPUT_PROP_BUTTONPAD property is set by 5.4 kernel, so that
libinput regard it as clickpad.
* Add a model quirk to unset the bit can make touchpad's right button
works normally.
I also uninstalled the vanilla version of deja-dup that came with 18.04 and
installed the snap with the latest. Will see in a few days whether anything
is different.
On Mon, Nov 30, 2020 at 5:00 PM Michael Terry <1906...@bugs.launchpad.net>
wrote:
> Oh that’s interesting yes. I’ll have to see
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
See also bug 1888598 and bug 1745866
** Tags added: hdmi
** Tags removed: hdmi-audio
--
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/1718927
Title:
No HDMI sound after
** Tags added: hdmi nvidia
** Also affects: nvidia-graphics-drivers (Ubuntu)
Importance: Undecided
Status: New
** Changed in: nvidia-graphics-drivers (Ubuntu)
Status: New => Confirmed
--
You received this bug notification because you are a member of Desktop
Packages, which is
*** This bug is a duplicate of bug 1888598 ***
https://bugs.launchpad.net/bugs/1888598
** This bug is no longer a duplicate of bug 1895665
PulseAudio automatically switches away from HDMI after display sleep
** This bug has been marked a duplicate of bug 1888598
Pulseaudio breaks HDMI
See also bug 1745866 and bug 1718927
** Summary changed:
- pulseaudio breaks hdmi audio on sleep/wake in ubuntu 20.10
+ Pulseaudio breaks HDMI audio on sleep/wake
** Tags added: hdmi
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to
*** This bug is a duplicate of bug 1888598 ***
https://bugs.launchpad.net/bugs/1888598
** This bug has been marked a duplicate of bug 1888598
Pulseaudio breaks HDMI audio on sleep/wake
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed
*** This bug is a duplicate of bug 1888598 ***
https://bugs.launchpad.net/bugs/1888598
Thank you for taking the time to report this bug and helping to make
Ubuntu better. This particular bug has already been reported and is a
duplicate of bug 1888598, so it is being marked as such. Please
The other bug isn't about application crashes, it's about gnome-shell
crashes which for Xorg sessions you might not notice happening.
Especially if you're in an application trying to go full screen.
To be sure which issue this is, please:
1. Reproduce the bug.
2. Reboot.
3. Run:
xrandr
I've been monitoring upower and I think the problem is it is incorrectly
detecting the number of batteries in my laptop. I only have one yet
upower detects 5 power sources. One of them is a DisplayDevice which
normally shows the same amount of battery as my system battery.
Sometimes that drops to
Please follow all of the steps in comment #3. I think we are up to step
2 now.
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to xorg-server in Ubuntu.
https://bugs.launchpad.net/bugs/190
Title:
Xserver crash at start , black screen
*** This bug is a duplicate of bug 1898005 ***
https://bugs.launchpad.net/bugs/1898005
Actually this is probably bug 1898005 or bug 1898910
** This bug is no longer a duplicate of bug 1867763
gnome-shell crashed with SIGABRT: assertion failure in st_bin_destroy:
assertion failed:
*** This bug is a duplicate of bug 1898005 ***
https://bugs.launchpad.net/bugs/1898005
Actually this is probably bug 1898005 or bug 1898910
** This bug is no longer a duplicate of bug 1867763
gnome-shell crashed with SIGABRT: assertion failure in st_bin_destroy:
assertion failed:
*** This bug is a duplicate of bug 1898005 ***
https://bugs.launchpad.net/bugs/1898005
Actually this is probably bug 1898005 or bug 1898910
** This bug is no longer a duplicate of bug 1867763
gnome-shell crashed with SIGABRT: assertion failure in st_bin_destroy:
assertion failed:
*** This bug is a duplicate of bug 1898005 ***
https://bugs.launchpad.net/bugs/1898005
Actually this is probably bug 1898005 or bug 1898910
** This bug is no longer a duplicate of bug 1867763
gnome-shell crashed with SIGABRT: assertion failure in st_bin_destroy:
assertion failed:
** Tags removed: hirsute
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to gnome-shell-extension-ubuntu-dock in
Ubuntu.
https://bugs.launchpad.net/bugs/1867763
Title:
gnome-shell crashed with SIGABRT: assertion failure in
*** This bug is a duplicate of bug 1898005 ***
https://bugs.launchpad.net/bugs/1898005
Actually this is probably bug 1898005 or bug 1898910
** This bug is no longer a duplicate of bug 1867763
gnome-shell crashed with SIGABRT: assertion failure in st_bin_destroy:
assertion failed:
This bug has been closed for over a year. Please open a new bug for any
issues in 20.10.
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to xorg-server in Ubuntu.
https://bugs.launchpad.net/bugs/1822515
Title:
Touchscreen input doesn't
Launchpad has imported 14 comments from the remote bug at
https://bugs.documentfoundation.org/show_bug.cgi?id=106008.
If you reply to an imported comment from within Launchpad, your comment
will be sent to the remote bug automatically. Read more about
Launchpad's inter-bugtracker facilities at
Turn off "launch on system startup" in general settings, then add
Nextcloud desktop sync client to startup applications of the system.
This works for me in Ubuntu 20.04.
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to
I went to look at "Window theme" but couldn't tell which was selected,
so I clicked on them. Now I can't reproduce the issue anymore. Maybe
something was wrong with my window theme before.
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to
#13, nah. Gobs of RAM are/were available.
I am forced to wonder how long the bug has existed. Under normal
circumstances, nobody would ever trigger it. I'm also puzzled about the
lack of any error messages.
As leok said, it seems to only happen with Vivid. I purely tested it
because I'd tested
** Tags removed: need-duplicate-check
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to glib2.0 in Ubuntu.
https://bugs.launchpad.net/bugs/1905758
Title:
package libglib2.0-0:i386 2.66.1-2 failed to install/upgrade:
dependency
** Information type changed from Private Security to Public
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to glib2.0 in Ubuntu.
https://bugs.launchpad.net/bugs/1905758
Title:
package libglib2.0-0:i386 2.66.1-2 failed to
** Package changed: xorg (Ubuntu) => xorg-server (Ubuntu)
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to xorg-server in Ubuntu.
https://bugs.launchpad.net/bugs/1906316
Title:
Xorg crash
Status in xorg-server package in Ubuntu:
New
Could the fix be included in 20.04 too?
--
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/1899206
Title:
Input device settings not applied on hotplug/reconnect/resume in Xorg
Public bug reported:
after opening nautilus it closes instantly
ProblemType: Bug
DistroRelease: Ubuntu 20.10
Package: nautilus 1:3.38.1-1ubuntu1
ProcVersionSignature: Ubuntu 5.8.0-31.33-generic 5.8.17
Uname: Linux 5.8.0-31-generic x86_64
ApportVersion: 2.20.11-0ubuntu50.2
Architecture: amd64
Public bug reported:
none
ProblemType: Package
DistroRelease: Ubuntu 20.04
Package: xcursor-themes 1.0.6-0ubuntu1
ProcVersionSignature: Ubuntu 5.4.0-56.62-generic 5.4.73
Uname: Linux 5.4.0-56-generic x86_64
NonfreeKernelModules: nvidia_modeset nvidia
.proc.driver.nvidia.capabilities.gpu0: Error:
This bug was fixed in the package libfprint - 1:1.90.3+tod1-0ubuntu3
---
libfprint (1:1.90.3+tod1-0ubuntu3) hirsute; urgency=medium
* debian/patches:
- Reorder to give upstream more priority
- Don't use power-save mode for USB controller (LP: #1906296)
-- Marco Trevisan
Thanks Heather, I will survive. :) (Thanks, Sebastien!)
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to libreoffice in Ubuntu.
https://bugs.launchpad.net/bugs/1888505
Title:
Two-finger touchpad zoom extremely sensitive
Status in
Public bug reported:
/usr/share/ubuntu-drivers-common/fake-devices-wrapper should bindmount
efivars under testbed.get_root_dir().
Ie. such that /sys/firmware/efi/efivars is correctly available under the
umockdev test-bed.
That way when testing subiquity, it should correctly observe if it was
I am running the default 20.04 gnome desktop, except for the display
manager.
I'm not sure how to trigger the issue since the problem is that the
screensaver doesn't start when it's supposed to.
Ran
journalctl -b 0
Checked the journal nothing there related to gnome. There are a lot of
*** This bug is a duplicate of bug 1899206 ***
https://bugs.launchpad.net/bugs/1899206
Thanks Gunner
Indeed the "Hide duplicates" check prevent me for finding the bugs I
report! :)
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to
*** This bug is a duplicate of bug 1899206 ***
https://bugs.launchpad.net/bugs/1899206
Thanks!
Yes I uncheck the "Hide duplicate" now I can see the bugs
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to gnome-control-center in
I do not understand why this is so complicated. You dont see Microsoft
or apple or google asking you to log in to a web page and diddle with
some kind of ticket system... just ask for permission and collect the
info. If you need to probe more and dig deeper, fine... go a head... Ask
if you may
Public bug reported:
Just crached all of a sudden. I was in a terminal using dialog...
ProblemType: Bug
DistroRelease: Ubuntu 20.04
Package: xorg 1:7.7+19ubuntu14
ProcVersionSignature: Ubuntu 5.4.0-42.46-generic 5.4.44
Uname: Linux 5.4.0-42-generic x86_64
NonfreeKernelModules: nvidia_modeset
The snap with Firefox 84 has the same problem.
I tried Ubuntu Studio 20.04, that also uses XFCE and that worked fine
and so do the Ubuntu 20.04, Ubuntu Mate 20.04 and Xubuntu 21.04 Dev.Ed.
However e.g Ubuntu 18.04 and Xubuntu 18.04 do have the same problem.
To be a little more precise. If you
Oh that’s interesting yes. I’ll have to see how to get the quota info
from gvfs and apply it to our calculations. Thank you for the report!
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to deja-dup in Ubuntu.
*** This bug is a duplicate of bug 1899206 ***
https://bugs.launchpad.net/bugs/1899206
No problem. Launchpad may be a bit confusing for newcomers. :) I
explained on the other bug how you can include duplicate bugs when
searching.
I closed this one too by making it a duplicate.
** Changed
Unfortunately, the commit I linked to in comment #1 doesn't explain why
coinmp support was disabled. The most likely reason is what Séb wrote,
that a package in main cannot depend on a package in universe, and
promoting a dependency from universe to main can be a tedious and time-
consuming
*** This bug is a duplicate of bug 1899206 ***
https://bugs.launchpad.net/bugs/1899206
Ah, the reason is that duplicate bugs are hidden by default. Those can
be searched for via the "Advanced search" option if you uncheck the
"Hide duplicate bugs" option.
--
You received this bug
I am not very familiar with how all this works. Could you please tell
me what would my next plan of action be? I have problems with all our
laptops and have lost so many documents as a result of trying to install
Ubuntu 20.04. Please help
--
You received this bug notification because you are
*** This bug is a duplicate of bug 1899206 ***
https://bugs.launchpad.net/bugs/1899206
Thanks Gunnar
I wasn't able to find this bug report, don't know why did show on my
reported bug page neither searching for it!
Thanks again
--
You received this bug notification because you are a member
Hi Gunnar
Sorry I was try to find the report that I did yesterday but I couldn't
find it, I search for it and didnt find the report. I thought he hadn't
reported
Sorry my bad this can be deleted or closed
The strange thing is that the previous report doesn't show on my
launchpad page so I
** Bug watch added: Debian Bug tracker #976091
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=976091
** Also affects: wpa (Debian) via
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=976091
Importance: Unknown
Status: Unknown
** Tags added: patch-accepted-upstream
**
Public bug reported:
I don't know if this is a bug, just have been having lots of problems
with all my laptops after trying to get new version of ubuntu. Don't
know if my version is corrupt.
Ubuntu 20.04.1 Lts Focal
When i Typed 'apt-cache policy pkgname', N : Unable to locate package
pkgname
Installed updates in proposed. New libfprint fixed the problem.
Thanks a lot
corrado@corrado-p6-hh-1125:~$ apt policy libfprint-2-2
libfprint-2-2:
Installed: 1:1.90.3+tod1-0ubuntu3
Candidate: 1:1.90.3+tod1-0ubuntu3
Version table:
*** 1:1.90.3+tod1-0ubuntu3 500
500
** Tags added: bionic
** Bug watch added: gitlab.gnome.org/GNOME/glibmm/-/issues #33
https://gitlab.gnome.org/GNOME/glibmm/-/issues/33
** Also affects: glibmm via
https://gitlab.gnome.org/GNOME/glibmm/-/issues/33
Importance: Unknown
Status: Unknown
** Also affects: glibmm2.4
I installed all the updates in proposed (main repository) and now have
libfprint-2-2 1:1.90.3tod1-0ubuntu3 installed
This fixed the problem on my computer
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to gnome-shell in Ubuntu.
Same on partition with proposed enabled. problem still here.
corrado@corrado-p6-hh-1125:~$ apt policy libfprint-2-2
libfprint-2-2:
Installed: 1:1.90.3+tod1-0ubuntu2
Candidate: 1:1.90.3+tod1-0ubuntu2
Version table:
*** 1:1.90.3+tod1-0ubuntu2 500
500 http://archive.ubuntu.com/ubuntu
This is my libfprint before and also after update and problem does not
disappear.
Will try on the partition where i have proposed enabled.
corrado@corrado-x2-hh-1104:~$ apt policy libfprint-2-2
libfprint-2-2:
Installed: 1:1.90.3+tod1-0ubuntu2
Candidate: 1:1.90.3+tod1-0ubuntu2
Version
No its different issue. My happens during import from ICS file. Syncing
with Google is after that. Regarding your question it doesnt happen whem I
manually create event so its somehow related to how this event is
imtermally stored in way common to gnome-calemdar and Evolution
pon., 30 lis 2020,
** Summary changed:
- gedit needs classic confinement
+ gedit snap fails to open fails in user dot directories
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to gedit in Ubuntu.
https://bugs.launchpad.net/bugs/1897562
Title:
gedit snap
> That would seem to rule out FTBFS for example too.
We have been rls-not-fixing build failures in the past as well yes,
especially in non lts series
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to libreoffice in Ubuntu.
Why did you submit yet another copy of this bug report? You filed bug
#1906186 and I marked it as a duplicate. If you think that was wrong,
please say that on the other bug and explain why you thought it was
wrong.
** Changed in: gnome-control-center (Ubuntu)
Status: New => Incomplete
--
** Package changed: pulseaudio (Ubuntu) => linux (Ubuntu)
--
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/1906267
Title:
IntelHD audio not detected after upgrading to Ubuntu 20.10
Could you try if the snap (which is an upstream build) has the same
issue?
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to firefox in Ubuntu.
https://bugs.launchpad.net/bugs/1898656
Title:
Firefox not playing YouTube videos in
The way launchpad bug tracking is working is that the status reflect the
current serie, and as you said it's fixed in 20.10. If the fix is needed
in older serie it's possible to target an older serie which would add a
line to the bug table. We do need to determine if the bug is important
enough
Public bug reported:
Backups are being stored using and external usb drive with the zfs
filesystem. There is a quota set on the backup partition. When deja-dup
fills the partition to it's quota it simply stops backing up instead of
deleting the oldest backups to make room for new backups. Setting
the issue on the hirsute serie could be bug #1906296 , could you try of
the libfprint update fixes the problem for you?
--
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/1905946
The usual reason is 'the package is in universe so we can't use it yet,
the MIR process takes time and we don't want to be blocked so let's
disable so we can get things rolling' but I don't have more background
information on whether there was a specific reason, I will let Olivier
comment
--
You
Thank you so much for your bug report and making Ubuntu better!
There are some issues with Qt integration library already. However, due
to resources vs priority, this is pretty low especially since there's a
workaround.
** Changed in: libreoffice (Ubuntu)
Status: New => Triaged
**
Public bug reported:
Hi!
Sometimes when close and open the laptop lid, the mouse natural
scrolling get reset to disable (default). Im using a thinkpad T460 with
the trackpoint with the mouse natural scrolling turn on so when I use
the scroll in the trackpoint (middle bottom) I get the same
> And when I open it with Calc, the format is much altered.
Ok now this is a real issue if the document does not look the same
between the two formats. Please open a new bug with information on this
including screenshots if possible. Thanks.!
--
You received this bug notification because you
Without a reason of why CoinMP was disabled in 2015, I don't have a
basis to go off on to re-evaluate enabling it. We could revert the patch
Olivier mentioned in comment 1 to close this bug but could be
reintroducing an old issue. Olivier/Seb, your suggestions?
--
You received this bug
Glad you have a working libreoffice now!
** Changed in: libreoffice (Ubuntu)
Status: Incomplete => Won't Fix
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to libreoffice in Ubuntu.
https://bugs.launchpad.net/bugs/1904377
Title:
Public bug reported:
laney@raleigh> apt policy libfprint-2-2
libfprint-2-2:
Installed: 1:1.90.3+tod1-0ubuntu2
Candidate: 1:1.90.3+tod1-0ubuntu2
Version table:
*** 1:1.90.3+tod1-0ubuntu2 500
500 file:/srv/mirrors/ubuntu hirsute/main amd64 Packages
100 /var/lib/dpkg/status
This appears to be a known issue upstream so I've attached the bug.
Tomislav, we will consume a fix from upstream and in the meantime sorry
for the inconvenience and thanks for reporting the issue :)
** Bug watch added: Document Foundation Bugzilla #106008
Upgraded libreoffice from 7.0.2-0ubuntu1 to 7.0.3-0ubuntu0.20.10.1 from
groovy-proposed in a clean and up-to-date groovy amd64 VM, and
successfully ran test plan at
https://wiki.ubuntu.com/Process/Merges/TestPlans/libreoffice.
** Tags removed: verification-needed-groovy
** Tags added:
@vanvugt, I use a Logitech Wireless Touchpad and a K800 keyboard.
--
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/1905946
Title:
Mouse stop moving after few seconds. restart at
Public bug reported:
Hello,
after a long time of inactivites, my session automatically locked (GDM).
When I unlock it, I can no more hear audio, device is set to spdif instead of
hdmi/displayport2.
I have to kill pulseaudio to retablish the good device hdmi/displayport2.
It's a very annoying
Public bug reported:
CPU usage after close of Chromium is 98,7% by systemd-jounal after these
updates
Start-Date: 2020-11-30 18:39:16
Commandline: packagekit role='update-packages'
Upgrade: gir1.2-mutter-7:amd64 (3.38.1-1ubuntu1, 3.38.1-2ubuntu1), snapd:amd64
(2.47.1+20.10.1, 2.48+20.10),
Hi @Sebastien,
I don't really understand the last comment. What do you mean by
"However, I am closing it because the bug has been fixed in the latest
development version of Ubuntu."?
The issue is present in the last version of the package for Ubuntu 18.04
LTS. The problem is that we can NOT
*** This bug is a duplicate of bug 1847570 ***
https://bugs.launchpad.net/bugs/1847570
Ok, I left the 2 lines disabled and found a fix for the dummy audio here:
https://www.linuxuprising.com/2018/06/fix-no-sound-dummy-output-issue-in.html
Seems to be working for me so far.
Thanks for
Uploaded librsvg 2.48.9-1ubuntu0.20.04.1, now sitting in the focal
unapproved queue, waiting for the SRU team to review and accept it.
** Changed in: librsvg (Ubuntu Focal)
Status: Triaged => In Progress
--
You received this bug notification because you are a member of Desktop
Packages,
** Changed in: libreoffice (Ubuntu)
Status: In Progress => Fix Released
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to libreoffice in Ubuntu.
https://bugs.launchpad.net/bugs/1904478
Title:
[SRU] libreoffice 7.0.3 for groovy
Public bug reported:
Recently in groovy, using the mouse scroll wheel while hovering over a
message in geary stopped scrolling the message. hovering over the
header or the scrollbar still works. possibly related to webkit2gtk
update?
ProblemType: Bug
DistroRelease: Ubuntu 20.10
Package: geary
*** This bug is a duplicate of bug 1847570 ***
https://bugs.launchpad.net/bugs/1847570
I guess I should add some info to my post yesterday.
I'm running on a Gigabyte Aorus Elite X570 MB with a Zotec GTX 1070 and
I have nothing hooked up to an HDMI port on either.
Disabling load-module
The issue with the patches for my Leveno updates has been resolved but
now I have a the same error with other patches. I have attached a screen
shoot of the error message.
Thank you,
** Attachment added: "Screenshot from 2020-11-30 11-35-36.png"
Well,
that doesn't happen on mine, except for the Chromium browser. I have
Telegram desktop installed as a snap but ç works fine. The same happens
on the other apps also.
Usually you need to have you keyboard layout configured as "English US-
Int with dead keys" in order for that to work.
--
** Tags added: hirsute
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to gnome-shell-extension-ubuntu-dock in
Ubuntu.
https://bugs.launchpad.net/bugs/1867763
Title:
gnome-shell crashed with SIGABRT: assertion failure in st_bin_destroy:
This bug remains, and exhibits with every startup in the T570's
UltraDock. Likewise, this bug has exhibited on every system here (all
ThinkPads) when in their respective UltraDocks. This includes a T480,
which is a current machine based on the i7-8xxx chipset.
--
You received this bug
*** This bug is a duplicate of bug 1867763 ***
https://bugs.launchpad.net/bugs/1867763
Thank you for taking the time to report this crash and helping to make
this software better. This particular crash has already been reported
and is a duplicate of bug #1867763, so is being marked as such.
** Description changed:
As we introduced the "-server" NVIDIA drivers, and the concept of "LTSB"
(Long Term Support Branch) and "NFB" (New Feature Branch) releases, the
detection logic behind ubuntu-drivers needs an update to make the
correct choices for the user.
The introduction of
librsvg 2.50.2+dfsg-1 is now in hirsute. We can proceed with the SRU.
** Changed in: librsvg (Ubuntu)
Status: Triaged => Won't Fix
** Changed in: librsvg (Ubuntu)
Status: Won't Fix => Fix Released
--
You received this bug notification because you are a member of Desktop
Packages,
Public bug reported:
After upgrading to Kubuntu 20.10, from 20.04 occasionally when I turn my
computer on the sound card doesn't work. If I load Pulse Audio Volume
Control and disable and then re-enable the audio controller (Family 17h
(Models 00h-0fh) HD Audio Controller it will work again.
** Changed in: yelp (Ubuntu)
Importance: Undecided => Low
** Changed in: yelp (Ubuntu)
Status: Confirmed => Triaged
** Bug watch added: gitlab.gnome.org/GNOME/yelp/-/issues #169
https://gitlab.gnome.org/GNOME/yelp/-/issues/169
** Also affects: yelp via
I added +1 to this, since this notification is really irritating and not
really useful.
For example, I have to use Skype and Teams for work, and every time
someone writes a message, I get " is ready" on the screen
top and it just hangs there, without any useful information, even
without the
1 - 100 of 167 matches
Mail list logo
