** Bug watch added: gitlab.freedesktop.org/xdg/shared-mime-info/-/issues #11
https://gitlab.freedesktop.org/xdg/shared-mime-info/-/issues/11
** Also affects: shared-mime-info via
https://gitlab.freedesktop.org/xdg/shared-mime-info/-/issues/11
Importance: Unknown
Status: Unknown
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
This has been fixed in 34-1
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to gnome-shell-extension-appindicator
in Ubuntu.
https://bugs.launchpad.net/bugs/1896785
Title:
Exported DBus interface is missing info or using wrong names
probably fixed on shared-mime-info 2.0:
https://gitlab.freedesktop.org/xdg/shared-mime-info/-/commit/18bb7cfc6c43d710ecf60339b5dd9bd19c297cdf
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to shared-mime-info in Ubuntu.
I tried the PPA suggested in post 122
(https://bugs.launchpad.net/ubuntu/+source/gnome-control-
center/+bug/1870736/comments/122) last night. No luck
I'm running Pop OS 20.04 and the displays control panel does not even
have fractional scaling buttons to try. I just have choices for "100%
200%
Upstream issue https://github.com/ubuntu/gnome-shell-extension-
appindicator/issues/246
** Description changed:
[ Impact ]
Padding on indicators is too wide, as per double-multiplication of the
same, leading to very spread icons:
https://user-
This was fixed by gnome-shell-extension-appindicator 34-1
** Changed in: gnome-shell-extension-appindicator (Ubuntu)
Status: New => Fix Released
** Also affects: gnome-shell-extension-appindicator (Ubuntu Focal)
Importance: Undecided
Status: New
--
You received this bug
I can confirm this bug is fixed when I updated mutter to
3.36.1-1ubuntu0.20.04.1. Using NVIDIA Graphics card.
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to mutter in Ubuntu.
https://bugs.launchpad.net/bugs/1892440
Title:
Shell
** Description changed:
[ Impact ]
GNOME shell when using this indicator should export the
org.kde.StatusNotifierWatcher dbus interface, although some methods and
properties are missing or invalid
-
[ Test case ]
-
Run:
- gdbus call --session --dest org.gnome.Shell
** Changed in: gnome-shell-extension-appindicator (Ubuntu)
Status: New => Fix Released
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to gnome-shell-extension-appindicator
in Ubuntu.
https://bugs.launchpad.net/bugs/1720334
Public bug reported:
[ Impact ]
GNOME shell when using this indicator should export the
org.kde.StatusNotifierWatcher dbus interface, although some methods and
properties are missing or invalid
[ Test case ]
Run:
gdbus call --session --dest org.gnome.Shell --object-path
** 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:
On gnome-shell, we now understand there are complications with API
breakage in microreleases, so we need a plan for reverse dependency
shell extensions to mitigate potential regressions. Discussion at
https://discourse.ubuntu.com/t/scope-of-gnome-mru/18041. I don't think
we can proceed with the
> > dpkg -S /usr/bin/mimetype
> libfile-mimeinfo-perl: /usr/bin/mimetype
how is that supposed to prove it's a shared-mime-info bug?
** Changed in: shared-mime-info (Ubuntu)
Status: New => Fix Committed
--
You received this bug notification because you are a member of Ubuntu
Desktop
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
Public bug reported:
[ Impact ]
Padding on indicators is too wide, as per double-multiplication of the
same, leading to very spread icons:
https://user-
images.githubusercontent.com/16012374/77627511-505f3780-6f47-11ea-
9d65-ec9053290b2f.png
[ Test case ]
- Open various indicator, padding
Daniel,
after further extensive testing and trialling. I can confirm that the high CPU
problem does not occur when I disable all GNOME extensions.
When no gnome-extensions were enabled the problem did not occur.
However, I was able to make the high CPU problem appear by running the
dock
** Also affects: tracker (Ubuntu Focal)
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to tracker in Ubuntu.
https://bugs.launchpad.net/bugs/1896073
Title:
SRU the current 2.3.6 stable
@Kai, so you use a 'command is provided by a perl utility' as a reason
to reasing to shared-mime-info, what's the logic? also xdg-mime works
fine under GNOME or when using gio that uses shared-mime-info...
** Package changed: shared-mime-info (Ubuntu) => kde-cli-tools (Ubuntu)
--
You received
** Also affects: gnome-shell-extension-appindicator (Ubuntu Focal)
Importance: Undecided
Status: New
** Changed in: gnome-shell-extension-appindicator (Ubuntu Focal)
Importance: Undecided => Low
** Changed in: gnome-shell-extension-appindicator (Ubuntu Focal)
Assignee:
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
** 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
This was fixed by version 34-1
** Changed in: gnome-shell-extension-appindicator (Ubuntu)
Status: New => Fix Released
** Changed in: gnome-shell-extension-appindicator (Ubuntu)
Assignee: (unassigned) => Marco Trevisan (Treviño) (3v1n0)
** Also affects:
Upstream issue:
https://github.com/ubuntu/gnome-shell-extension-appindicator/issues/235
Upstream fix:
https://github.com/ubuntu/gnome-shell-extension-appindicator/pull/231
** Description changed:
+ [ Impact ]
+
+ An app-indicator icon does not show when I login using the default gnome
+
Update to mutter 3.36.1-1ubuntu0.20.04.1 in focal/proposed also fixed
the bug for AMD.
Good work, thanks and cheers! :-)
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to mutter in Ubuntu.
https://bugs.launchpad.net/bugs/1892440
** Changed in: gnome-shell-extension-appindicator (Ubuntu Focal)
Status: New => In Progress
** Changed in: gnome-shell-extension-appindicator (Ubuntu)
Assignee: (unassigned) => Marco Trevisan (Treviño) (3v1n0)
** Changed in: gnome-shell-extension-appindicator (Ubuntu Focal)
** 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 Ubuntu
Desktop Bugs, which is subscribed to mutter in Ubuntu.
https://bugs.launchpad.net/bugs/1892440
Title:
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
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
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 Ubuntu
Desktop Bugs, which is subscribed to gnome-shell in Ubuntu.
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 Ubuntu
Desktop Bugs, which is subscribed to mutter in Ubuntu.
https://bugs.launchpad.net/bugs/1896818
Title:
Gnome-shell
> 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:
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
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
@ Cristiano,
please fill another bug for that :)
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, 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
@ Marco Trevisan,
I'll do that.
Anyway, thanks for the fix. ;)
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to mutter in Ubuntu.
https://bugs.launchpad.net/bugs/1892440
Title:
Shell text with wrong size in mutter
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]:
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
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 Ubuntu
Desktop Bugs, which is subscribed to mutter in Ubuntu.
I mean, this looks like bug #1889090 is back..
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to mutter in Ubuntu.
https://bugs.launchpad.net/bugs/1896818
Title:
Gnome-shell crash after turn display off in mutter
Public bug reported:
Disks utility program and command line only seeing the drive as read
only. unable to write data to the disk. all works OK in Windows 10.
ProblemType: Bug
DistroRelease: Ubuntu 20.04
Package: brasero 3.12.2-6ubuntu1
ProcVersionSignature: Ubuntu 5.4.0-31.35-generic 5.4.34
@ 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 Ubuntu
Desktop Bugs, which is subscribed to mutter
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
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
** Package changed: systemd (Ubuntu) => tracker (Ubuntu)
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to tracker in Ubuntu.
https://bugs.launchpad.net/bugs/1896756
Title:
tracker* startup is defined multiple times
To manage
There is a problem:
https://bugs.launchpad.net/ubuntu/+source/mutter/+bug/1896818
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to mutter in Ubuntu.
https://bugs.launchpad.net/bugs/1896332
Title:
SRU 3.36.6
To manage notifications
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 Ubuntu
Desktop Bugs, which is subscribed to mutter in Ubuntu.
@ 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)
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've fill another bug:
https://bugs.launchpad.net/ubuntu/+source/mutter/+bug/1896818
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to mutter in Ubuntu.
https://bugs.launchpad.net/bugs/1892440
Title:
Shell text with wrong size in
** 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 Ubuntu
Desktop Bugs, which is subscribed to mutter in Ubuntu.
** 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 Ubuntu
Desktop Bugs, which is subscribed to mutter in Ubuntu.
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
** 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 Ubuntu
Desktop Bugs, which is subscribed to mutter in Ubuntu.
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 Ubuntu
Desktop Bugs, which is subscribed to gnome-shell in Ubuntu.
https://bugs.launchpad.net/bugs/1890875
Title:
I've tested in a fresh install also.
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, 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
** 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 Ubuntu
Desktop Bugs, which is subscribed to mutter in Ubuntu.
** 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 Ubuntu
Desktop Bugs, which is subscribed to mutter in Ubuntu.
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
** 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 Ubuntu
Desktop Bugs, which is subscribed to mutter in Ubuntu.
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-
I've prepared a new package with the whole set of fixes:
https://launchpad.net/ubuntu/bionic/+queue?queue_state=1_text
=gnome-shell
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to gnome-shell in Ubuntu.
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 )
-
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
Thanks, Trevinho! ;)
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, 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)
To manage
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.
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
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 Ubuntu
Desktop Bugs, which is subscribed to
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 Ubuntu
Desktop Bugs, which is subscribed to
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 Ubuntu
Desktop Bugs, which is subscribed to mutter in Ubuntu.
https://bugs.launchpad.net/bugs/1896818
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
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
** 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 Ubuntu
Desktop Bugs, which is subscribed to mutter in Ubuntu.
https://bugs.launchpad.net/bugs/1892440
Title:
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 Ubuntu
Desktop Bugs, which is subscribed to mutter in Ubuntu.
https://bugs.launchpad.net/bugs/1896818
Title:
** 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 Ubuntu
Desktop Bugs, which is subscribed to mutter in Ubuntu.
https://bugs.launchpad.net/bugs/1896332
Title:
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
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 Ubuntu
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 Ubuntu
Desktop Bugs, which is subscribed to
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 Ubuntu
Desktop Bugs, which is subscribed to mutter in Ubuntu.
https://bugs.launchpad.net/bugs/1896332
Title:
SRU
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
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
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 Ubuntu
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
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
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 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
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
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 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
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
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
** 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:
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 Ubuntu
Desktop Bugs, which is subscribed to mutter in Ubuntu.
https://bugs.launchpad.net/bugs/1892440
adding 'journalctl -b 0' from a session having the issue.
** Attachment added: "Adding 'journalctl -b 0' as file journalctl.txt"
https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1896637/+attachment/5413471/+files/journalctl.txt
--
You received this bug notification because you are
Still with snap-store 3.36.0-82-g80486d0 481
has the maintenance of snap-store been abandoned?
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to the bug report.
https://bugs.launchpad.net/bugs/1873040
Title:
Source for deb apps in
I installed mutter 3.36.6-1ubuntu0.20.04.1 from the focal/proposed
repository and can confirm that the bug is fixed for me.
The font is no longer too small. Thank you.
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to mutter in Ubuntu.
I have the same problem in Ubuntu 20.04, and also 19.10 before
upgrading. The problem occurs sporadically. I can confirm that the
problem disappears after reboot, or if I just log out and log in again.
When the problem occurs, it also triggers weird mouse behavior in a few
other applications such
Daniel, I have only faced that bug once, so far it hasn't happened
again, so I have no idea how to reproduce it. Should I open a new bug
anyway? Under mutter and the NVIDIA drivers?
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to
it's not a shared-mime-info issue, on a GNOME session the result is
right
$ xdg-mime query filetype index.py
text/x-python
** Package changed: shared-mime-info (Ubuntu) => kde-cli-tools (Ubuntu)
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is
1 - 100 of 109 matches
Mail list logo
