Thanks for the update, I missed that comment (again). I guess it can be
moved back to "triaged" then.
** Changed in: apache2 (Ubuntu)
Status: Incomplete => Triaged
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to glib2.0 in
Does this also happen with Ubuntu Disco? I checked upstream and there
were no other changes following this one in that file:
commit 6c8bc39f570ea82cf14e83ce7d1dbdbe569d09d1
Author: Ondrej Holy
Date: Wed Sep 12 15:28:51 2018 +0200
smbbrowse: Force NT1 protocol version for workgroup support
I indeed think interacting with a server that has disabled SMB1 entirely
is a related, but different problem. Can you get smbclient -L to work
with such a server, using the netbios hostname, or does it fail when
listing the shares?
--
You received this bug notification because you are a member
I think it's exactly getting the share list using NT1 that is failing. I
will look at this tomorrow, see what smbclient -L is doing wrt NT1
temporary downgrade.
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to nautilus in Ubuntu.
Yes, please open a separate bug report, and attach your smb.conf there
please.
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to nautilus in Ubuntu.
https://bugs.launchpad.net/bugs/1778322
Title:
gvfs-smb-browse can't browse
It is, that's all that's needed now. I heard another, unrelated, gvfs
SRU was in the works and was hitting problems, though.
I have a no-change rebuild in this PPA for bionic:
https://launchpad.net/~ahasenack/+archive/ubuntu/gvfs-rebuild-1778322/
--
You received this bug notification because
Disco shouldn't have this bug. It (gvfs) will have issues connecting to
smb servers that have disabled SMB1, just like bionic and everything in
between.
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to nautilus in Ubuntu.
Public bug reported:
After bug #1778322 is fixed (just needs a gvfs rebuild with newer
samba), samba machines will start to show up again in the "windows
network" tab in nautilus. But if a server has disabled the SMB1
protocol, nautilus will show an error when that server is clicked on,
instead
I filed https://bugs.launchpad.net/gvfs/+bug/1828107 for the remaining
issue of connecting to machines in the windows network tab that have
disabled SMB1. Note that a connection made specifically to the
machine/ip still works (smb:///)
--
You received this bug notification because you are a
I found an upstream issue about not being able to get a share list from
a machine that has SMB1 disabled:
https://gitlab.gnome.org/GNOME/gvfs/issues/307
** Bug watch added: gitlab.gnome.org/GNOME/gvfs/issues #307
https://gitlab.gnome.org/GNOME/gvfs/issues/307
--
You received this bug
Switching zsh back to incomplete, according to previous comment. Thanks
for noticing that.
** Changed in: zsh (Ubuntu)
Status: Triaged => Incomplete
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to glib2.0 in Ubuntu.
@morbius1, how did you disable smb1 on your test samba server? "server
min protocol = SMB2"?
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to nautilus in Ubuntu.
https://bugs.launchpad.net/bugs/1778322
Title:
gvfs-smb-browse can't
Ah, you said so, sorry
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to nautilus in Ubuntu.
https://bugs.launchpad.net/bugs/1778322
Title:
gvfs-smb-browse can't browse samba/smb tree
To manage notifications about this bug go to:
> The original issue was you couldn't get a listing of samba hosts in Nautilus
> so
> yes that issue is fixed.
The original problem also affected linux samba boxes, which do allow
smb1 by default still. You couldn't even see them in nautilus. Now you
can, and you can browse their shares and
Nice, that's good to know, thanks for pointing it out.
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to nautilus in Ubuntu.
https://bugs.launchpad.net/bugs/1778322
Title:
gvfs-smb-browse can't browse samba/smb tree
To manage
@seb128, the test case uses a localhost samba server, with a non-guest
pub share pointing at /tmp. Not even that was visible in gnome before
this fix.
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to nautilus in Ubuntu.
The "windows network" tab depends on an election to happen between the
smb servers, and a master browser being elected. It's the master browser
that is contacted for the list of machines in the network. If that
machine has smb1 disabled, for example, then this won't work, because it
will hit
Try the test case in a disco vm
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to nautilus in Ubuntu.
https://bugs.launchpad.net/bugs/1778322
Title:
gvfs-smb-browse can't browse samba/smb tree
To manage notifications about this bug
Check your smb.conf, maybe you have some overriding setting in there.
The default disco install I tested had no config file.
With gvfsd running in debug mode, there is also a specific message you
can look for which will tell you if your gvfsd was rebuilt with the
right samba version: "Forcing NT1
I checked disco when I prepared these updates for bionic and cosmic, and
it was allright. Let me re-check with a default install using the CD
this time, now that it is released.
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to nautilus
It worked just fine on a disco desktop default install.
I brought up a bionic vm, which has samba running and set to a workgroup
called "workgroup" and has a /pub share. On disco, I click on "other
locations", then "windows network", and I see "WORKGROUP". I can click
on "WORKGROUP", which then
Hi Petrida,
could you please elaborate on why you changed the bug status from
incomplete to confirmed without providing the requested information from
comment #95?
** Changed in: openssh (Ubuntu)
Status: Confirmed => Incomplete
--
You received this bug notification because you are a
sssd master has pcre2 support via
https://github.com/SSSD/sssd/pull/677#issuecomment-508238642
eoan is getting 2.2.0, which doesn't have that yet, but getting closer!
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to glib2.0 in Ubuntu.
Public bug reported:
When coming back from a suspend on eoan, the tabs and gnome-terminal
window are all broken. Some are maximized, some are not, some have huge
fonts, some don't. I have to double click on the title bar (if I can
find it), and then double-click again to maximize and restore the
apport information
** Attachment added: "ProcCpuinfoMinimal.txt"
https://bugs.launchpad.net/bugs/1850960/+attachment/5302065/+files/ProcCpuinfoMinimal.txt
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to gnome-terminal in Ubuntu.
apport information
** Attachment added: "ProcEnviron.txt"
https://bugs.launchpad.net/bugs/1850960/+attachment/5302066/+files/ProcEnviron.txt
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to gnome-terminal in Ubuntu.
apport information
** Attachment added: "Dependencies.txt"
https://bugs.launchpad.net/bugs/1850960/+attachment/5302064/+files/Dependencies.txt
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to gnome-terminal in Ubuntu.
** Description changed:
When coming back from a suspend on eoan, the tabs and gnome-terminal
window are all broken. Some are maximized, some are not, some have huge
fonts, some don't. I have to double click on the title bar (if I can
find it), and then double-click again to maximize and
** Attachment added: "app-is-ready.png"
https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1864682/+attachment/5330903/+files/app-is-ready.png
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to gnome-shell in Ubuntu.
Public bug reported:
I'm getting double notifications in Focal. First, the actual content of
the notification, like an irc ping. Then, a few seconds later, another
one saying that "App is ready" (hexchat in this case).
Attached two screenshots showing this.
ProblemType: Bug
DistroRelease:
*** This bug is a duplicate of bug 1813441 ***
https://bugs.launchpad.net/bugs/1813441
** Summary changed:
- Dran and drop to desktop area doesn't work
+ Drag and drop to desktop area doesn't work
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which
Public bug reported:
When I select an icon in my desktop, be it a folder or file, the
"delete" key doesn't do anything with it anymore. I was expecting it to
be moved to the trash folder.
ProblemType: Bug
DistroRelease: Ubuntu 20.04
Package: gnome-shell 3.35.91-1ubuntu2
ProcVersionSignature:
Public bug reported:
If I have a folder window open, and drag a file from it into the desktop
area, that is somehow forbidden and the icon just moves back to the
folder where it came from, in a "moving" animation. It's almost as if I
didn't have filesystem permissions to move it to the desktop.
Public bug reported:
When logging in, one of the two isn't centered on screen: either the
password input box, or the avatar. See attached photograph.
ProblemType: Bug
DistroRelease: Ubuntu 20.04
Package: gdm3 3.34.1-1ubuntu1
ProcVersionSignature: Ubuntu 5.4.0-17.21-generic 5.4.22
Uname: Linux
Done: https://gitlab.gnome.org/GNOME/gnome-shell/-/issues/2598
** Bug watch added: gitlab.gnome.org/GNOME/gnome-shell/-/issues #2598
https://gitlab.gnome.org/GNOME/gnome-shell/-/issues/2598
** Also affects: gnome-shell via
https://gitlab.gnome.org/GNOME/gnome-shell/-/issues/2598
Public bug reported:
See attached screenshot.
I clicked the "Update" button next to a firmware update notification,
but my laptop was not connected to AC power. It told me that, but at the
same time it told me the update was applied correctly, and that I should
reboot. That's wrong.
** Tags added: champagne
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to gnome-terminal in Ubuntu.
https://bugs.launchpad.net/bugs/1850960
Title:
Coming back from suspend, tabs and window are broken
To manage notifications about
Public bug reported:
I can't exactly pinpoint which gnome package is responsible for this. It
might be gnome-keyring. Let's go with gnome-shell first.
TL;DR openssh 8.2p1 in focal has support for U2F authentication. This is
a new feature we will highlight in the release notes and a blog post.
** Description changed:
I can't exactly pinpoint which gnome package is responsible for this. It
might be gnome-keyring. Let's go with gnome-shell first.
- TL;DR openssh 8.2p1 in focal has support for U2F authentication. This is
- a new feature we will highlight in the release notes and a
apport information
** Tags added: focal third-party-packages
** Description changed:
When coming back from a suspend on eoan and now focal, the tabs and
gnome-terminal window are all broken. Some are maximized, some are not,
some have huge fonts, some don't. I have to double click on the
apport information
** Attachment added: "ProcCpuinfoMinimal.txt"
https://bugs.launchpad.net/bugs/1850960/+attachment/5338383/+files/ProcCpuinfoMinimal.txt
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to gnome-shell in Ubuntu.
apport information
** Attachment added: "GsettingsChanges.txt"
https://bugs.launchpad.net/bugs/1850960/+attachment/5338382/+files/GsettingsChanges.txt
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to gnome-shell in Ubuntu.
apport information
** Attachment added: "ProcEnviron.txt"
https://bugs.launchpad.net/bugs/1850960/+attachment/5338384/+files/ProcEnviron.txt
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to gnome-shell in Ubuntu.
apport information
** Attachment added: "monitors.xml.txt"
https://bugs.launchpad.net/bugs/1850960/+attachment/5338386/+files/monitors.xml.txt
** Changed in: gnome-shell (Ubuntu)
Status: Incomplete => New
--
You received this bug notification because you are a member of Ubuntu
apport information
** Attachment added: "ShellJournal.txt"
https://bugs.launchpad.net/bugs/1850960/+attachment/5338385/+files/ShellJournal.txt
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to gnome-shell in Ubuntu.
Happens with every suspend/resume cycle. I'll attach the logs after I
come back from lunch, which will be a great opportunity since I'll
suspend the laptop.
It does not happen with a simple lock/unlock sequence. It has to be
coming back from suspend.
--
You received this bug notification
It's happening with focal as well. This system was upgraded to focal
from eoan.
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to gnome-terminal in Ubuntu.
https://bugs.launchpad.net/bugs/1850960
Title:
Coming back from suspend, tabs
I stand corrected in that it doesn't happen every time. I had to try
about 4 times to get it to happen again, and it's just with the gnome-
terminal window.
Here is the requested log.
** Attachment added: "journalctl-b-0.txt"
scale is 100%, screen resolution is at 1920x1080, but it supports more
(2ksomethingXsomething, can't remember now).
--
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/1850960
Title:
hardware is a x1 5th gen laptop
--
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/1850960
Title:
Coming back from suspend, tabs and window are broken
To manage notifications
When you manually connect, by typing in the full smb url, it doesn't
mean SMB1 is being used. You can verify that by running "sudo smbstatus"
on the server.
** Changed in: nautilus (Ubuntu)
Status: New => Incomplete
--
You received this bug notification because you are a member of Ubuntu
Ah, I think I see what you mean. Nautilus (gvfs actually) is temporarily
downgrading the protocol for the discovery, but it's not reverting that
when trying to actually connect to a discovered host. Is that it?
This does ring a bell, it was supposed to be fixed with an SRU on
bionic, and in the
This will only get better once another discovery service is used, since
SMB1 won't come back.
https://github.com/christgau/wsdd is something we could look into
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to gvfs in Ubuntu.
There is an sssd package in focal-unapproved that points at this bug,
with this d/changelog snippet:
* debian/patches: Backport patches atches to support properly GDM smartcard
login (LP: #1865226)
(sic)
But there is no sssd task in this bug.
I also don't see a gdm3 upload to focal
Also, this but is missing the SRU template, in case the sssd upload I
mentioned in my previous comment is really addressing this bug.
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to gdm3 in Ubuntu.
This bug is ready for verification. Due to the release status mantic was
in when the package was accepted, the tooling failed to add the template
comment to this bug, and add the tags, and I did all of that manually
now.
** Also affects: gnome-control-center (Ubuntu Mantic)
Importance: High
This bug is ready for verification. Due to the status mantic was in when
the package was accepted, the tooling failed to add the template comment
to this bug, and add the tags, and I did all of that manually now.
** Also affects: gnome-shell-extension-ubuntu-dock (Ubuntu Mantic)
Importance:
This bug is ready for verification. Due to the status mantic was in when
the package was accepted, the tooling failed to add the template comment
to this bug, and add the tags, and I did all of that manually now.
** Tags added: verification-needed verification-needed-mantic
** Also affects:
Hi Georgia, is this still pending an evince fix? Your PPA has an updated
evince package, but I don't think it was uploaded to unapproved yet,
without the recommends.
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to evince in Ubuntu.
I think this is a bit more nefarious.
On an installed system, all you have to do to have port 3389/tcp
suddenly open is to *visit* the "share" tab in the settings. No need to
change a thing, just visit it, then close the window. Boom, you have rdp
desktop sharing running. At least it's a random
The verification of the Stable Release Update for mutter 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 encounter a
I see. That is a proprietary library needed for this particular
smartcard. I understand Ubuntu is not responsible for it. The only thing
I can add it that it didn't crash before, and I've been using it since
2017 or so.
It still works, mind you, I can login to sites that require it, sign
Hi all,
I'm reviewing this SRU, and was trying to reproduce the issue following
the given test case, but no matter what I try, it just works.
I installed cinnamon 22.10 from the ISO image into a VM, and added a
remote network printer (not wifi, though: wired ethernet). I monitored
dmesg, and
Hi Gunnar and others,
with Lunar just released, I'm going over the lunar unapproved queue to
pick out packages that should now become SRUs for lunar.
Could someone please add the SRU template to this bug's description, and
fill it out?
Since the package is in unapproved, and not proposed, I'm
Hello Robert,
the [test plan] has very specific steps involving the calculator,
gsettings, and an expected result. Did you perform those specifically?
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to glib2.0 in Ubuntu.
I verified that the test was executed according to the [test plan].
I understand kinetic is not part of this SRU. The reason wasn't
explained anywhere, but I'm assuming it's because it's a) ending support
soon; and/or b) this glib update is more useful for core22 snap and core
desktop
The verification of the Stable Release Update for glib2.0 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 encounter a
The verification of the Stable Release Update for nautilus 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 encounter
Neil didn't clarify which ubuntu release he tested in his comment above,
but given that he is the one who filed this bug originally on kinetic
(22.10), and also confirmed in comment #12 that the issue was fixed,
I'll take this as verification done for kinetic, assuming it was the
test case number
The test plan is a bit superficial, but it is what it is.
The build-time tests ran and passed (17 in total). There were warnings
about failing to create files/directories in the build env, but these
were there before for previous releases as well.
The package built correctly in all architectures
I verified the test results and am satisfied that they show the executed
planned test case, and that the results are correct. Since the test case
was a script, I also ran it successfully on a kinetic LXD.
The package built correctly in all architectures and Ubuntu releases it
was meant for.
The verification of the Stable Release Update for gdm3 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 encounter a
Given comment #12, I'm adding a block-proposed tag to this bug. Is this
something we could use to improve the test plan of this package by any
chance? Since it seems to have introduced crashes on kinetic.
** Tags added: block-proposed-jammy
** Tags added: block-proposed-kinetic
--
You received
Hello Neil, or anyone else affected,
Accepted gdm3 into kinetic-proposed. The package will build now and be
available at
https://launchpad.net/ubuntu/+source/gdm3/43.0-1ubuntu1.22.10.1 in a few
hours, and then in the -proposed repository.
Please help us by testing this new package. See
Hello Neil, or anyone else affected,
Accepted gdm3 into jammy-proposed. The package will build now and be
available at
https://launchpad.net/ubuntu/+source/gdm3/42.0-1ubuntu7.22.04.1 in a few
hours, and then in the -proposed repository.
Please help us by testing this new package. See
We discussed this a bit in the SRU team, and the external dependency is
"fine" because it's disabled by default. I would still prefer it's not
there, or at least that the default for OFFLINE_MODE was already 1 and
you wouldn't have to specify it when running the test, but this is not a
blocker for
Hello Jeremy, or anyone else affected,
Accepted pango1.0 into jammy-proposed. The package will build now and be
available at
https://launchpad.net/ubuntu/+source/pango1.0/1.50.6+ds-2ubuntu1 in a
few hours, and then in the -proposed repository.
Please help us by testing this new package. See
Marco, why have you kept the code that may download a test script from a
github gist? I can more or less understand having that there while
testing/troubleshooting, but now? I know it's gated on a) OFFLINE_MODE
(although lunar has some changes in that area that are not in kinetic);
and b) the test
Jaap, what's needed is a verification for kinetic. Please see the test
plan in the bug description at the very top, and try out the package
from proposed as outlined in comment #24.
And we also need a kinetic verification on
https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1949200 which
The verification of the Stable Release Update for mutter 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 encounter a
The verification of the Stable Release Update for mutter 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 encounter a
The verification of the Stable Release Update for apparmor 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 encounter
Looks like we get this if evince is update, apparmor is not, and a link
in a pdf is clicked:
Jul 06 18:36:59 j-evince kernel: audit: type=1400
audit(1688668619.304:78): apparmor="DENIED" operation="exec"
info="profile transition not found" error=-13 profile="/usr/bin/evince"
name="/usr/bin/snap"
> Do we need evince to be reuploaded for jammy there since the previous
upload was rejected by Steve?
I'm trying to see what type of error we get if we load a profile with
such a rule and the target profile does not exist:
/{,snap/core/[0-9]*/,snap/snapd/[0-9]*/}usr/bin/snap mrCx ->
Hello Daniel, or anyone else affected,
Accepted mutter into jammy-proposed. The package will build now and be
available at https://launchpad.net/ubuntu/+source/mutter/42.9-0ubuntu3
in a few hours, and then in the -proposed repository.
Please help us by testing this new package. See
Hello Fabio, or anyone else affected,
Accepted mutter into jammy-proposed. The package will build now and be
available at https://launchpad.net/ubuntu/+source/mutter/42.9-0ubuntu3
in a few hours, and then in the -proposed repository.
Please help us by testing this new package. See
In the test plan, can you also please confirm it keeps working with the
current and upcoming HWE kernels for jammy?
** Changed in: mutter (Ubuntu Jammy)
Status: In Progress => Fix Committed
** Tags added: verification-needed verification-needed-jammy
--
You received this bug
Hello Ionut, or anyone else affected,
Accepted mutter into jammy-proposed. The package will build now and be
available at https://launchpad.net/ubuntu/+source/mutter/42.9-0ubuntu3
in a few hours, and then in the -proposed repository.
Please help us by testing this new package. See
Hello Ghadi, or anyone else affected,
Accepted gdm3 into jammy-proposed. The package will build now and be
available at
https://launchpad.net/ubuntu/+source/gdm3/42.0-1ubuntu7.22.04.3 in a few
hours, and then in the -proposed repository.
Please help us by testing this new package. See
Hello Ghadi, or anyone else affected,
Accepted gdm3 into lunar-proposed. The package will build now and be
available at https://launchpad.net/ubuntu/+source/gdm3/44.0-1ubuntu2 in
a few hours, and then in the -proposed repository.
Please help us by testing this new package. See
Please include a "normal" test for gdm3 in the test case. Something like
testing that logins keep working after applying this update, a switch
between "init 3" and "init 5", and that user switching works (while
logged in as user A, with open apps, login as user B, launch an app, and
come back to
> Marking verification-done-jammy. I'll verify lunar tomorrow.
Please note my request in comment #9 about a few extra test cases.
** Tags removed: verification-done-jammy
** Tags added: verification-needed-jammy
--
You received this bug notification because you are a member of Ubuntu
Desktop
It's particularly annoying if I have a maximized terminal window in one
monitor. Chrome on the monitor in its left "perturbs" the terminal
window, see the screenshot. It's like it's drawing beyond the window
limits, over the adjacent window.
The moment the terminal window that has the
I disabled all extensions using gnome-extensions-app, logged out and
logged back in:
$ gsettings get org.gnome.shell enabled-extensions
@as []
andreas@nsnx2:~$
I don't know what `@as` is.
But I still see the same artifacts at the borders, and between monitors, as
before.
--
You received
Public bug reported:
I installed mutter 44.1 and gnome-shell 44.1 from proposed, and a few of
other related dependencies. I don't have everything at 44.1, I don't
know if we should expect more gnome-related updates in lunar-proposed.
For example, I have
gnome-shell-extension-prefs 44.1-0ubuntu1
I filed https://bugs.launchpad.net/ubuntu/+source/mutter/+bug/2020674
about the above.
--
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/2020225
Title:
Update mutter to 44.1
To
$ gsettings get org.gnome.shell enabled-extensions
['d...@rastersoft.com', 'ubuntu-d...@ubuntu.com', 'tiling-assist...@ubuntu.com']
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to mutter in Ubuntu.
Also happens with chromium (the snap).
--
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/2020225
Title:
Update mutter to 44.1
To manage notifications about this bug go to:
The artifact at the border also happens across monitors. The tall chrome
window on the right of the left monitor interferes with the windows
aligned to the left of the right monitor.
This happened immediately after updating mutter and gnome shell to 44.1,
it wasn't happening before.
--
You
Turns out I'm only seeing it with google-chrome. Tried firefox, and a
terminal, using the same reproducer, and it didn´t happen.
** Attachment added: "chrome-mutter-44.1.webm"
https://bugs.launchpad.net/ubuntu/+source/mutter/+bug/2020225/+attachment/5675428/+files/chrome-mutter-44.1.webm
--
101 - 200 of 246 matches
Mail list logo
