apport information
** Attachment added: "ProcEnviron.txt"
https://bugs.launchpad.net/bugs/1785060/+attachment/5413762/+files/ProcEnviron.txt
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to evince in Ubuntu.
https://bugs.launchpad.net
apport information
** Attachment added: "ProcCpuinfoMinimal.txt"
https://bugs.launchpad.net/bugs/1785060/+attachment/5413761/+files/ProcCpuinfoMinimal.txt
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to evince in Ubuntu.
https://bugs
apport information
** Attachment added: "Dependencies.txt"
https://bugs.launchpad.net/bugs/1785060/+attachment/5413759/+files/Dependencies.txt
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to evince in Ubuntu.
https://bugs.launchpad.n
ProblemType: Bug
ApportVersion: 2.20.11-0ubuntu27.9
Architecture: amd64
CasperMD5CheckResult: skip
CurrentDesktop: ubuntu:GNOME
DistroRelease: Ubuntu 20.04
InstallationDate: Installed on 2020-09-23 (0 days ago)
InstallationMedia: Ubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731)
Package:
apport information
** Attachment added: "KernLog.txt"
https://bugs.launchpad.net/bugs/1785060/+attachment/5413760/+files/KernLog.txt
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to evince in Ubuntu.
https://bugs.launchpad.net/bugs/17
apport information
** Attachment added: "RelatedPackageVersions.txt"
https://bugs.launchpad.net/bugs/1785060/+attachment/5413763/+files/RelatedPackageVersions.txt
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to evince in Ubuntu.
http
I have the same MSFT0001:00 04F3:3186 touchpad, however, the touchpad
will show as Elantech Touch Pad under windows and it is listed under the
firmware section:
Elantech Touch Pad Firmware 1.0.0.2
Device type:Firmware
Manufacturer: Elantech Ltd.
Locatioon: on Microsft UEFI-Compliant Sy
Public bug reported:
dkms.conf can be changed to just use
PATCH[0]="kernel-5.7.patch"
PATCH[1]="buildfix_kernel_5.8.patch"
with patches from archlinux:
https://aur.archlinux.org/cgit/aur.git/tree/buildfix_kernel_5.8.patch?h=nvidia-340xx
and
https://gitlab.manjaro.org/packages/extra/linux57-extr
This bug was fixed in the package libfprint - 1:1.90.3+tod1-0ubuntu1
---
libfprint (1:1.90.3+tod1-0ubuntu1) groovy; urgency=medium
* New upstream release (LP: #1896861):
- New goodixmoc driver supporting Goodix USB devices:
27C6:5840, 27C6:6496, 27C6:60A2
- Newly added
This bug was fixed in the package libfprint - 1:1.90.3+tod1-0ubuntu1
---
libfprint (1:1.90.3+tod1-0ubuntu1) groovy; urgency=medium
* New upstream release (LP: #1896861):
- New goodixmoc driver supporting Goodix USB devices:
27C6:5840, 27C6:6496, 27C6:60A2
- Newly added
Tested again from focal-proposed (mutter 3.36.6-1ubuntu0.20.04.2). Can
confirm it still fixes the problem! (Intel HD Graphics).
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to mutter in Ubuntu.
https://bugs.launchpad.net/bugs/1892440
Tit
** Also affects: libfprint (Ubuntu Focal)
Importance: Undecided
Status: New
** Changed in: libfprint (Ubuntu Focal)
Importance: Undecided => Medium
** Changed in: libfprint (Ubuntu Focal)
Status: New => In Progress
** Changed in: libfprint (Ubuntu Focal)
Assignee: (unass
Public bug reported:
Fixes various bugs in AuthenTec chip, synapitcs and add goodix reader
support
** Affects: libfprint (Ubuntu)
Importance: Medium
Assignee: Marco Trevisan (Treviño) (3v1n0)
Status: In Progress
--
You received this bug notification because you are a member o
As per comment
https://bugs.launchpad.net/mutter/+bug/1857947/comments/11
We can mark this as verified.
** Tags removed: verification-needed verification-needed-focal
** Tags added: verification-done verification-done-focal
--
You received this bug notification because you are a member of Deskt
As per comment
https://bugs.launchpad.net/ubuntu/+source/mutter/+bug/1870867/comments/27
We can mark this as verified.
** Tags removed: verification-needed verification-needed-focal
** Tags added: verification-done verification-done-focal
--
You received this bug notification because you are a
As per comment
https://bugs.launchpad.net/ubuntu/+source/mutter/+bug/1887998/comments/13
We can mark this as verified.
** Tags removed: verification-needed verification-needed-focal
** Tags added: verification-done verification-done-focal
--
You received this bug notification because you are a
** Tags removed: verification-needed verification-needed-focal
** Tags added: verification-done verification-done-focal
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to mutter in Ubuntu.
https://bugs.launchpad.net/bugs/1892440
Title:
Sh
I forgot to mention this i changelogs, so this will be closed once bug
https://bugs.launchpad.net/ubuntu/+source/mutter/+bug/1896332 will be
** Changed in: mutter (Ubuntu Focal)
Status: Triaged => Fix Committed
--
You received this bug notification because you are a member of Desktop
Pack
** Tags removed: verification-needed verification-needed-focal
** Tags added: verification-done verification-done-focal
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to mutter in Ubuntu.
https://bugs.launchpad.net/bugs/1896332
Title:
SR
** Tags removed: verification-needed verification-needed-focal
** Tags added: verification-done verification-done-focal
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to mutter in Ubuntu.
https://bugs.launchpad.net/bugs/1896818
Title:
Gn
yep, there we go, works fine now. I wonder what component malfunctioned
when setting that, could have been wine or vlc or any number of things
that prevent sleep while playing media, I suppose. It's too bad that
there's no indicator or overrider to let a user know what's going on in
this scenario.
No issues here either on AMD and Intel. Thankfully this also finally
fixes https://bugs.launchpad.net/bugs/1879968
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to mutter in Ubuntu.
https://bugs.launchpad.net/bugs/1896332
Title:
SRU 3.3
** Summary changed:
- Poor quality audio with modern Bluetooth headsets in HSP/HFP. Missing wide
band speech support.
+ Poor quality audio with modern Bluetooth headsets in HSP/HFP. Missing wide
band speech support (Bluetooth A2DP codecs ).
--
You received this bug notification because you a
Hi, Brian and Marco,
I've tested the mutter 3.36.6-1ubuntu0.20.04.2 (from "focal-proposed"
repository).
Now, all works fine! Without problems.
Thanks for your attention and work! :)
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to mutter
Hi, Brian and Marco,
I've tested the mutter 3.36.6-1ubuntu0.20.04.2 (from "focal-proposed"
repository).
Now, all works fine! Without problems.
Thanks for your attention and work! :)
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to mutter
Hi, Brian and Marco,
I've tested the mutter 3.36.6-1ubuntu0.20.04.2 (from "focal-proposed"
repository).
Now, all works fine! Without problems.
Thanks for your attention and work! :)
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to mutter
Dear sender!
Thank you for your message! Unfortunately, I am out of office until 27.9.2020
and hence will not be able to reply immediately.
Your email will not be forwarded, but I will answer your email as soon as
possible on my return. In very urgent cases, however,
please contact our service c
Yeah, it seems to get worse with every 5.4 LTS update. Worked almost
flawless about some months ago (despite taking something from 30-60s to
successfully connect). But I don't see a correlation to any commits. But
now, it's almost impossible to connect successfully, it usually
disconnects after a 1
Public bug reported:
Most of the executable ELF files in /usr/bin/ will not run from any GUI
interface and most do not show up anywhere including in the files list. When I
try to execute one from GUI I get the popup box that I have attached to this
report. However, when I run the same file from
On Wed, Sep 23, 2020 at 10:14:57PM -, Tessa wrote:
> Sep 23 15:07:58 boxxy gnome-shell[209336]: Screen lock is locked down,
> not locking
>
> so it appears as if it thinks the screen is already locked, even though
> I'm interacting with my session. and the dbus call doesn't have any way
This
Hello, facing the same issue (obviously).
I appear to have the MSFT0001:00 04F3:3186, ordered in France, so this
model does not seems to be limited to china (R7000 variant).
Blacklisting done nothing. I have seen the chinese blog but I'm a little
lost with this, is it supposed to work with my mod
Hello Anthony, or anyone else affected,
Accepted mutter into focal-proposed. The package will build now and be
available at
https://launchpad.net/ubuntu/+source/mutter/3.36.6-1ubuntu0.20.04.2 in a
few hours, and then in the -proposed repository.
Please help us by testing this new package. See
ht
why am I not surprised that sending a cryptic dbus command is the
"correct" way to lock the screen from the cli these days.
in any case, I can run that command as often as you like, and it always
returns success to the shell, but it never locks the screen:
tessa@boxxy:~/Downloads$ dbus-send --typ
Hello errors.ubuntu.com, or anyone else affected,
Accepted mutter into focal-proposed. The package will build now and be
available at
https://launchpad.net/ubuntu/+source/mutter/3.36.6-1ubuntu0.20.04.2 in a
few hours, and then in the -proposed repository.
Please help us by testing this new packag
Hello Cristiano, or anyone else affected,
Accepted mutter into focal-proposed. The package will build now and be
available at
https://launchpad.net/ubuntu/+source/mutter/3.36.6-1ubuntu0.20.04.2 in a
few hours, and then in the -proposed repository.
Please help us by testing this new package. See
Hello Ivan, or anyone else affected,
Accepted mutter into focal-proposed. The package will build now and be
available at
https://launchpad.net/ubuntu/+source/mutter/3.36.6-1ubuntu0.20.04.2 in a
few hours, and then in the -proposed repository.
Please help us by testing this new package. See
https
Hello Marco, or anyone else affected,
Accepted mutter into focal-proposed. The package will build now and be
available at
https://launchpad.net/ubuntu/+source/mutter/3.36.6-1ubuntu0.20.04.2 in a
few hours, and then in the -proposed repository.
Please help us by testing this new package. See
http
Hello Marco, or anyone else affected,
Accepted mutter into focal-proposed. The package will build now and be
available at
https://launchpad.net/ubuntu/+source/mutter/3.36.6-1ubuntu0.20.04.2 in a
few hours, and then in the -proposed repository.
Please help us by testing this new package. See
http
Hello Cristiano, or anyone else affected,
Accepted mutter into focal-proposed. The package will build now and be
available at
https://launchpad.net/ubuntu/+source/mutter/3.36.6-1ubuntu0.20.04.2 in a
few hours, and then in the -proposed repository.
Please help us by testing this new package. See
For ABNT2 keyboards, I've removed the "Scroll Lock" key, see:
https://gitlab.freedesktop.org/xkeyboard-config/xkeyboard-
config/-/merge_requests/112
It is not the right solution (I even regretted it), but it works...
--
You received this bug notification because you are a member of Desktop
Pack
I've tested the mutter 3.36.6-1ubuntu0.20.04.2~wip1 (in the PPA).
Now, all works fine!
Thanks for your attention and work.
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to mutter in Ubuntu.
https://bugs.launchpad.net/bugs/1896818
Title:
Public bug reported:
ishabalov@black:~$ simple-scan --debug
[+0.00s] DEBUG: simple-scan.vala:1720: Starting simple-scan 3.36.3, PID=38292
[+0.00s] DEBUG: unsetenv() is not thread-safe and should not be used after
threads are created
[+0.01s] DEBUG: _g_io_module_get_default: Found default implemen
Hello Andreas, or anyone else affected,
Accepted livecd-rootfs into xenial-proposed. The package will build now
and be available at https://launchpad.net/ubuntu/+source/livecd-
rootfs/2.408.60 in a few hours, and then in the -proposed repository.
Please help us by testing this new package. See
h
I have amended test case k) to stipulate that we ensure the base ubuntu-
cpc image continues to have grub-legacy-ec2 installed. The intended
outcome of this change is that all images that currently have grub-
legacy-ec2 installed have it, all images that do not have grub-legacy-
ec2 installed cont
Thanks, Trevinho! ;)
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to mutter in Ubuntu.
https://bugs.launchpad.net/bugs/1896818
Title:
Gnome-shell crash after turn display off in mutter
3.36.6-ubuntu0.20.04.1 (NVIDIA)
Status in mutte
Thanks for making the bug SRU compliant, I've uploaded a new version.
In the mean time you can probably test it using the ppa at
https://launchpad.net/~ci-train-ppa-service/+archive/ubuntu/4267
** Description changed:
In Ubuntu 20.04.1 [focal-proposed]:
[ Impact ]
GNOME Shell crash aft
** Package changed: ubuntu => xorg (Ubuntu)
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to xorg in Ubuntu.
https://bugs.launchpad.net/bugs/1896815
Title:
Xorg freeze? Old Arabic Fonts are not working
Status in xorg package in Ubuntu:
You have been subscribed to a public bug:
Hello,
Old Arabic Fonts (not MS fonts) were running on MS Word.
they can not working on ubuntu.
they listed in LO Writer , but they are not running in all kubuntu 20.10
applications.
I used fc-cache for install them. but they are not configured for
run
I mean, this looks like bug #1889090 is back..
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to mutter in Ubuntu.
https://bugs.launchpad.net/bugs/1896818
Title:
Gnome-shell crash after turn display off in mutter
3.36.6-ubuntu0.20.04.1
Oh, crazy... This was supposed to be fixed already, looks like something
broke when adapting the patch?!
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to mutter in Ubuntu.
https://bugs.launchpad.net/bugs/1896818
Title:
Gnome-shell crash
** Attachment added: "lsusb-v.log"
https://bugs.launchpad.net/ubuntu/+source/mutter/+bug/1896818/+attachment/5413598/+files/lsusb-v.log
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to mutter in Ubuntu.
https://bugs.launchpad.net/bugs/
See also:
https://bugs.launchpad.net/ubuntu/+source/mutter/+bug/1892440
** Description changed:
+ In Ubuntu 20.04.1 (focal):
+
[ Impact ]
GNOME Shell crash after updating mutter to version 3.36.6-ubuntu0.20.04.1.
With the old version (3.36.4-0ubuntu0.20.04.1) and (3.36.4-0ubuntu0.20.04.2)
** Attachment added: "syslog"
https://bugs.launchpad.net/ubuntu/+source/mutter/+bug/1896818/+attachment/5413597/+files/syslog
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to mutter in Ubuntu.
https://bugs.launchpad.net/bugs/1896818
T
** Attachment added: "version.log"
https://bugs.launchpad.net/ubuntu/+source/mutter/+bug/1896818/+attachment/5413599/+files/version.log
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to mutter in Ubuntu.
https://bugs.launchpad.net/bugs/
In my syslog:
gnome-shell[3407]: mutter:ERROR:../src/backends/x11/meta-monitor-
manager-xrandr.c:211:meta_monitor_manager_xrandr_update_screen_size:
assertion failed: (width > 0 && height > 0 && scale > 0)
gnome-shell[3407]: Bail out! mutter:ERROR:../src/backends/x11/meta-
monitor-manager-
xrandr
** Attachment added: "dmesg.log"
https://bugs.launchpad.net/ubuntu/+source/mutter/+bug/1896818/+attachment/5413602/+files/dmesg.log
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to mutter in Ubuntu.
https://bugs.launchpad.net/bugs/1896
** Attachment added: "lspci-vnvn.log"
https://bugs.launchpad.net/ubuntu/+source/mutter/+bug/1896818/+attachment/5413601/+files/lspci-vnvn.log
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to mutter in Ubuntu.
https://bugs.launchpad.net
And a new upload now in the queue:
https://bugs.launchpad.net/ubuntu/+source/gnome-
shell/+bug/1838152/comments/11
--
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/1890875
Title:
K
I've tested in a fresh install also.
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to mutter in Ubuntu.
https://bugs.launchpad.net/bugs/1896818
Title:
Gnome-shell crash after turn display off in mutter
3.36.6-ubuntu0.20.04.1 (NVIDIA)
Public bug reported:
[ Impact ]
Mesa 20 update broke mutter builds, as visible in
https://launchpad.net/ubuntu/+source/mutter/3.28.4+git20200505-0ubuntu18.04.1
[ Test case ]
Mutter should build cleanly in a bionic chroot
[ Regression potential ]
Wayland components aren't included in the final
** Attachment added: "uname-a.log"
https://bugs.launchpad.net/ubuntu/+source/mutter/+bug/1896818/+attachment/5413600/+files/uname-a.log
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to mutter in Ubuntu.
https://bugs.launchpad.net/bugs/
There is a problem:
https://bugs.launchpad.net/ubuntu/+source/mutter/+bug/1896818
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to mutter in Ubuntu.
https://bugs.launchpad.net/bugs/1896332
Title:
SRU 3.36.6
Status in mutter package in
I've fill another bug:
https://bugs.launchpad.net/ubuntu/+source/mutter/+bug/1896818
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to mutter in Ubuntu.
https://bugs.launchpad.net/bugs/1892440
Title:
Shell text with wrong size in mutter
Daniel, I'm not sure if this bug is related but, the system also hangs
for a few seconds whenever the Wi-Fi gets disconnected.
--
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/1892747
Public bug reported:
[ Impact ]
GNOME Shell crash after updating mutter to version 3.36.6-ubuntu0.20.04.1.
With the old version (3.36.4-0ubuntu0.20.04.1) and (3.36.4-0ubuntu0.20.04.2),
all works fine.
[ Test case ]
Steps to reproduce the error:
1) Lock screen;
2) Turn off the display;
3) Turn on
** Package changed: systemd (Ubuntu) => tracker (Ubuntu)
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to tracker in Ubuntu.
https://bugs.launchpad.net/bugs/1896756
Title:
tracker* startup is defined multiple times
Status in tracker pa
You have been subscribed to a public bug:
This is about
- tracker-miner-fs
- tracker-extract
- tracker-store
Actual Behavior
=
Their startup is defined in
- ${XDG_CONFIG_HOME}/autostart ( more info:
https://wiki.archlinux.org/index.php/XDG_Autostart )
- /usr/lib/systemd/user/
I do not see any window flickering with QEMU hosting 20.10 guest. So
specific to intel i915? Sorry - I cannot test radeon or Nvidia.
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to mutter in Ubuntu.
https://bugs.launchpad.net/bugs/189665
Should note - testing mutter package 3.38.0-1ubuntu1
** Summary changed:
- Windows flicker when resizing with mouse
+ Windows flicker when resizing with mouse (GNOME-Shell - Xorg & Budgie
** Summary changed:
- Windows flicker when resizing with mouse (GNOME-Shell - Xorg & Budgie
+ Windows flic
@ Marco Trevisan,
After I power down my display and power up again (in the lock screen),
the problem is:
gnome-shell[3407]: mutter:ERROR:../src/backends/x11/meta-monitor-
manager-xrandr.c:211:meta_monitor_manager_xrandr_update_screen_size:
assertion failed: (width > 0 && height > 0 && scale > 0)
Status changed to 'Confirmed' because the bug affects multiple users.
** Changed in: mutter (Ubuntu)
Status: New => Confirmed
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to mutter in Ubuntu.
https://bugs.launchpad.net/bugs/189665
Note - this affects GNOME-Shell on Xorg as well.
Confirmed with intel i915 driver.
GNOME-Shell on Wayland there are no window flicker
So most probably a regression in mutter (since budgie and GNOME-Shell
share the same window manager) in the X11 handling.
--
You received this bug notification
I also have Lenovo Legion 5 15ARH05H, 82B1000AUS and would like to help
out with adding support for this device. Any advice on how to get
started?
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to xserver-xorg-input-libinput in Ubuntu.
http
** Changed in: snapd (Ubuntu)
Status: New => Confirmed
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to ubuntu-meta in Ubuntu.
https://bugs.launchpad.net/bugs/1895144
Title:
ubuntu-server CET gap analysis
Status in golang-defaul
Public bug reported:
Unable to change drivers
ProblemType: Package
DistroRelease: Ubuntu 20.04
Package: nvidia-340 (not installed)
ProcVersionSignature: Ubuntu 5.4.0-48.52-generic 5.4.60
Uname: Linux 5.4.0-48-generic x86_64
ApportVersion: 2.20.11-0ubuntu27.9
Architecture: amd64
CasperMD5CheckResu
** Tags removed: need-duplicate-check
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to nvidia-graphics-drivers-340 in Ubuntu.
https://bugs.launchpad.net/bugs/1896814
Title:
package nvidia-340 (not installed) failed to install/upgrade: t
I've prepared a new package with the whole set of fixes:
https://launchpad.net/ubuntu/bionic/+queue?queue_state=1&queue_text
=gnome-shell
--
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/bu
@ Marco Trevisan,
I'll do that.
Anyway, thanks for the fix. ;)
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to mutter in Ubuntu.
https://bugs.launchpad.net/bugs/1892440
Title:
Shell text with wrong size in mutter 3.36.4-0ubuntu0.20.0
Public bug reported:
Ubuntu 20.04.1
Package mutter-3.36.6-1ubuntu0.20.04.1
Sep 23 12:30:03 razorback systemd[2389]: Starting GNOME Shell on X11...
Sep 23 12:30:03 razorback gnome-shell[26684]: **
Sep 23 12:30:03 razorback gnome-shell[26684]:
mutter:ERROR:../src/backends/x11/meta-monitor-manager
@ Cristiano,
please fill another bug for that :)
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to mutter in Ubuntu.
https://bugs.launchpad.net/bugs/1892440
Title:
Shell text with wrong size in mutter 3.36.4-0ubuntu0.20.04.2 (mostly
o
The bug is fixed when I updated mutter to 3.36.1-1ubuntu0.20.04.1.
BUT
After an "Automatic Screen Lock", the display turned off, the Gnome
Shell crash and show us a blank screen with the message "Oh no!
Something has gone wrong."
This bug did not appears before the update.
I have a NVIDIA c
This bug was fixed in the package libreoffice - 1:6.4.6-0ubuntu0.20.04.1
---
libreoffice (1:6.4.6-0ubuntu0.20.04.1) focal; urgency=medium
* New upstream release (LP: #1892783)
-- Heather Ellsworth Mon, 24 Aug
2020 16:58:01 -0600
** Changed in: libreoffice (Ubuntu Focal)
The verification of the Stable Release Update for libreoffice has
completed successfully and the package is now being released to
-updates. Subsequently, the Ubuntu Stable Release Updates Team is being
unsubscribed and will not receive messages about this bug report. In
the event that you encount
This bug was fixed in the package apparmor - 3.0.0~beta1-0ubuntu6
---
apparmor (3.0.0~beta1-0ubuntu6) groovy; urgency=medium
* Drop d/p/lp1824812.patch: this patch was only needed with 2.13 and not
3.0. With AppArmor 3, the patch ends up setting SFS_MOUNTPOINT to the
wrong d
Ah about this:
> If this isn't used for generating the final packages at all, why do
you propose to make users download an update?
Those files aren't included at all into the package, the README.sources
there was included to explain why we have such files, even though they
are not built.
It's ju
> I don't understand why yaru-theme needs to be updated, either. I see
> that this has been done for yaru-theme once before, but I've found no
> explanation as to why.
I will make it clearer in the top post, but it should be quite easy to
spot looking at the shell's (data subdir) and yaru diffs:
@ David
I think pop-os disabled fractional scaling patch, so get in contact with them
please:
https://github.com/pop-os/mutter/commit/bc7c2658e4c873a28afeaf621fb24a1341c6d74c
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to gnome-contr
** Also affects: libreoffice (Ubuntu)
Importance: Undecided
Status: New
--
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/1884850
Title:
Xorg server uses unacceptably large
** Package changed: ubuntu => alsa-driver (Ubuntu)
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to alsa-driver in Ubuntu.
https://bugs.launchpad.net/bugs/1896774
Title:
Headphone output stopped working after perfoming dist-upgrade
Sta
An upload of gnome-shell to bionic-proposed has been rejected from the
upload queue for the following reason: "Fix appears incomplete, and no
progress in a month. Please see
https://bugs.launchpad.net/ubuntu/+source/gnome-
shell/+bug/1838152/comments/5 and subsequent discussion.".
--
You received
An upload of gnome-shell to bionic-proposed has been rejected from the
upload queue for the following reason: "Fix appears incomplete, and no
progress in a month. Please see
https://bugs.launchpad.net/ubuntu/+source/gnome-
shell/+bug/1838152/comments/5 and subsequent discussion.".
--
You received
You have been subscribed to a public bug:
# What happened:
- Upgraded packages using: sudo apt-get update && sudo apt-get dist-
upgrade
- Following packages were installed:
pulseaudio-utils:amd64 1:8.0-0ubuntu3.12 1:8.0-0ubuntu3.14
pulseaudio-module-x11:amd64 1:8.0-0ubuntu3.12 1:8.0-0ubuntu3.14
** Also affects: gnome-shell-extension-appindicator (Ubuntu Focal)
Importance: Undecided
Status: New
** Changed in: gnome-shell-extension-appindicator (Ubuntu Focal)
Importance: Undecided => High
** Changed in: gnome-shell-extension-appindicator (Ubuntu Focal)
Assignee: (unassig
** Changed in: tracker (Ubuntu Focal)
Importance: Undecided => Low
** Changed in: tracker (Ubuntu Focal)
Status: New => In Progress
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to tracker in Ubuntu.
https://bugs.launchpad.net/b
Hello, I have exactly the same issue as the creator of this bug. I have
a Lenovo Legion 5 15ARH05H, model number 82B1000AUS
(https://psref.lenovo.com/Detail/Legion/Lenovo_Legion_5_15ARH05H?M=82B1000AUS),
and my touchpad is listed as MSFT0001:00 04F3:3186, not 04F3:3140.
How can I help add support
** Description changed:
[ Impact ]
Indicators using (big) pixmap icons cause the shell to use a lot of CPU
computation, which interfere with user experience
-
[ Test case ]
- Install mega client from https://mega.nz/sync
- Run it in ubuntu and ensure it doesn't block the UI w
Could you please stop that reassigning game? You are right, it's either
on shared-mime-info or the qt integration, now the result of the
testcase provided is correct on GNOME (see comment 5), it's also correct
on a cloud instance (e.g no desktop integration) so it's only buggy on
KDE, you should ra
testing with xdgmime [1] (reference implementation of the spec [2] and
also used tests on shared-mine-type):
> ../xdgmime/src/print-mime-data .
test.py:
name: text/x-python
data: application/xhtml+xml
file: application/xhtml+xml
> ../xdgmime/src/test-mime test.py
File "tes
Hey Chris, thanks for the review.
The GNOME maintainers sometime has a somewhat flexible definition of
what is a bugfix indeed.
The command has been added to help migrations from tracker2 to the new
tracker3, it's not strictly something we need in focal but at the same time
it's a new option so
You have been subscribed to a public bug:
Expected behavior:
$ kmimetypefinder5 example.py
text/x-python3
or
$ kmimetypefinder5 example.py
text/x-python
or
$ kmimetypefinder5 example.py
text/plain
Actual behavior:
$ kmimetypefinder5 example.py
application
1 - 100 of 144 matches
Mail list logo
