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
but gnome-shell-extens
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 recei
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
--
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:
https://bug
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 manage
$ 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.
https://bugs.launchpad.net/bugs/20206
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 thi
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 "corruption"
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 us
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
https://wi
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
https://wiki.ubunt
> 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 B
To illustrate this bug, in this video capture I:
- selected file3
- hit the delete key
- hit the F5 (refresh) key
** Attachment added: "deleted-file-3-and-refreshed.webm"
https://bugs.launchpad.net/ubuntu/+source/nautilus/+bug/2022851/+attachment/5677929/+files/deleted-file-3-and-refreshed.we
After some googling, maybe this is the fix?
https://gitlab.gnome.org/GNOME/gtk/-/merge_requests/5873
--
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/2022851
Title:
Inappropriate f
Thanks for the lunar tests in comment #22, and also for confirming that
the problem you saw happened without this update. I think a separate
bug for that is appropriate, if you could please file one.
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is
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 reg
evince and apparmor for lunar should be released together to fix this
bug, but there is still a DEP8 failure that needs clearing under
apparmor: libreoffice/armhf
https://ubuntu-archive-team.ubuntu.com/proposed-
migration/lunar/update_excuses.html#apparmor
It was retried a few times already, but
** Description changed:
Impact
--
There is a new bugfix release in the stable 42 series.
https://gitlab.gnome.org/GNOME/mutter/-/blob/42.9/NEWS
The overall GNOME project considers GNOME 42 to be end of life now and
there are no more scheduled releases for mutter 42 after 42.9
It's my understanding that this should be released together with gnome-
shell 42.9-0ubuntu2 which is currently in jammy-proposed.
gnome-shell 42.9 is https://bugs.launchpad.net/ubuntu/+source/gnome-
shell/+bug/2023913 and has been in jammy-proposed for 5 days, and is
still pending verification.
-
It's my understanding that this should be released together with gnome-
shell 42.9-0ubuntu2 which is currently in jammy-proposed.
gnome-shell 42.9 is https://bugs.launchpad.net/ubuntu/+source/gnome-
shell/+bug/2023913 and has been in jammy-proposed for 5 days, and is
still pending verification.
-
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 r
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 r
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 a
> 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 ->
snap_browse
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" p
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 notification
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
https://wiki.u
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
https://wiki.
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
https://wiki.u
The verification of the Stable Release Update for gnome-control-center
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 yo
> (Except for the workrave extension but that was already broken when Ubuntu
> 23.04 was released and
> mentioned in every SRU since. I believed it's fixed in 23.10 so it needs to
> be SRU'd.)
https://bugs.launchpad.net/ubuntu/+source/workrave/+bug/2017302 I suppose, and
https://bugs.launchpa
The verification of the Stable Release Update for gnome-shell 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
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 r
Apparmor in jammy-proposed has the necessary changes, we just need a new
evince upload to jammy without the recommends then.
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to evince in Ubuntu.
https://bugs.launchpad.net/bugs/1794064
Tit
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 unappro
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.
https://bugs.launchpad.net/bugs/18652
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.
htt
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: Med
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: gnome
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 r
Noble also has 1:45.0-1ubuntu3, with the same fix. This all started
before noble was released, hence the version collision, but I'm pretty
sure that throughout the devel cycle, noble will get a gnome-control-
center version bump, so no harm in releasing mantic with this version
now.
--
You receiv
The verification of the Stable Release Update for gnome-control-center
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 yo
Marking as incomplete pending the completion of what was requested in
comment #2 above. I also added tasks for the missing ubuntu releases.
** Also affects: libfprint (Ubuntu Jammy)
Importance: Undecided
Status: New
** Also affects: libfprint (Ubuntu Noble)
Importance: High
St
The verification of the Stable Release Update for gnome-shell 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
noble-proposed still only has 45.1-2ubuntu1, btw. It should get 45.2
before this update is released to mantic. I updated the main bug status
to reflect that noble isn't fixed nor committed yet.
** Changed in: mutter (Ubuntu)
Status: Fix Committed => Triaged
--
You received this bug notifi
Hello Gonzalo, or anyone else affected,
Accepted mutter into mantic-proposed. The package will build now and be
available at https://launchpad.net/ubuntu/+source/mutter/45.2-0ubuntu1
in a few hours, and then in the -proposed repository.
Please help us by testing this new package. See
https://wik
Hello Jeremy, or anyone else affected,
Accepted mutter into mantic-proposed. The package will build now and be
available at https://launchpad.net/ubuntu/+source/mutter/45.2-0ubuntu1
in a few hours, and then in the -proposed repository.
Please help us by testing this new package. See
https://wiki
Hello Jeremie, or anyone else affected,
Accepted mutter into mantic-proposed. The package will build now and be
available at https://launchpad.net/ubuntu/+source/mutter/45.2-0ubuntu1
in a few hours, and then in the -proposed repository.
Please help us by testing this new package. See
https://wik
Also, before release, please someone clarify this statement about a mesa
regression in noble with 45.1 presumably:
"It will get updated to 45.2 (and eventually to 46) after a mesa
regression is handled."
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which
> I wanted to test the updated version of mutter so a couple of days ago I
> enabled the `proposed`
> repository, but I didn't receive any updates.
Jeremie, you also have to pass "-t mantic-proposed" in the apt command
line.
--
You received this bug notification because you are a member of Ubu
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 r
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 r
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 r
Hello Kai-Chuan, or anyone else affected,
Accepted gnome-shell into focal-proposed. The package will build now and
be available at https://launchpad.net/ubuntu/+source/gnome-
shell/3.36.9-0ubuntu0.20.04.3 in a few hours, and then in the -proposed
repository.
Please help us by testing this new pac
Hello shine, or anyone else affected,
Accepted gnome-shell into focal-proposed. The package will build now and
be available at https://launchpad.net/ubuntu/+source/gnome-
shell/3.36.9-0ubuntu0.20.04.3 in a few hours, and then in the -proposed
repository.
Please help us by testing this new package
I see this was filed on the 13th. Had this been mentioned in the 45.2
mantic SRU bug[1], I wouldn't have released the package to updates on
the 14th :/
1. https://bugs.launchpad.net/ubuntu/+source/mutter/+bug/2043000
--
You received this bug notification because you are a member of Ubuntu
Deskt
The DEP8 tests are green now.
I'm going to verify this revert for mantic, which is currently in
mantic-proposed. But note I have NOT been able to reproduce the stuttering in
firefox with the mutter package from mantic-updates (45.2-0ubuntu1). I tried:
- wayland
- xorg
- native resolution (2880x1
mantic verification
I used mutter from mantic-proposed:
andreas@nsnx2:~$ apt-cache policy mutter
mutter:
Installed: 45.2-0ubuntu2~really45.0
Candidate: 45.2-0ubuntu2~really45.0
Version table:
*** 45.2-0ubuntu2~really45.0 100
100 http://br.archive.ubuntu.com/ubuntu mantic-proposed/un
There is an armhf DEP8 failure that I just retriggered, let's see if it
passes in the next run.
--
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/2051074
Title:
Mirror mode doesn't wor
There is an armhf DEP8 failure that I just retriggered, let's see if it
passes in the next run.
--
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/2054510
Title:
Incomplete screen redra
The test failure on armhf persists:
939s # Running test: mutter-13/fullscreen-maximize.test
940s # Executing: mutter-13/fullscreen-maximize.test
941s # FAIL: mutter-13/fullscreen-maximize.test (Child process exited with code
1)
941s not ok - mutter-13/fullscreen-maximize.test
--
You received th
The test failure on armhf persists:
939s # Running test: mutter-13/fullscreen-maximize.test
940s # Executing: mutter-13/fullscreen-maximize.test
941s # FAIL: mutter-13/fullscreen-maximize.test (Child process exited with code
1)
941s not ok - mutter-13/fullscreen-maximize.test
--
You received th
> this is an extremely easy fix in code to make
As this is a long bug, with many comments and different scenarios at
play, I'm a bit lost by now.
What is the easy code fix you are referring to, do you have a link to a
patch?
Also, please restate what is the scenario we are talking about here.
Ub
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 a
The verification of the Stable Release Update for file-roller 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
Regarding the LC_* variables in openssh's config, I understand it's not
a direct replacement for ~/.pam_environment, because that is on the
*server*, and we would be sending the *client* vars.
** Also affects: gdm3 (Ubuntu)
Importance: Undecided
Status: New
--
You received this bug not
Adding a task for gdm3, since it seems affected by dropping
user_readenv=1 from its pam configuration.
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to gdm3 in Ubuntu.
https://bugs.launchpad.net/bugs/2059859
Title:
pam_env(sshd:sessi
The verification of the Stable Release Update for gnome-shell 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
The verification of the Stable Release Update for gnome-shell 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
The verification of the Stable Release Update for gnome-shell 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
The verification of the Stable Release Update for gnome-shell 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
The verification of the Stable Release Update for gnome-shell 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
The verification of the Stable Release Update for gnome-shell 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
The verification of the Stable Release Update for evolution 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
The verification of the Stable Release Update for evolution 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
Please clarify the testing that was done, and *with which version
exactly* (as requested in comment #12). This package had to go through a
revert in the previous attempt to update to 1.72.4 (see version
1.72.4-0ubuntu0.22.04.3~really.is.1.72.2.0ubuntu2), and we need more
confidence.
** Tags remove
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.
https://bu
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 de
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 pa
The original samba patch had a typo/error, this is the fix for that:
https://github.com/samba-
team/samba/commit/885435e8a4dc561749b880f8be7a32041fa954ec
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to gvfs in Ubuntu.
https://bugs.lau
It worked with the updated patch. Packages rebuilt in the PPA. I'll
prepare a merge proposal and SRU this into bionic. We will have to
rebuild gvfs there, though, after samba lands in proposed.
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscri
** Description changed:
- * Impact
- On Bionic Beaver 18.04.1 gvfs-smb-browse can't browse smbtree because of that
Nautilus displays "Empty Folder" when clicking "Windows Network"
+ [Impact]
+ The so called "browsing a windows network" made use of an SMB1 protocol
version feature. Recent version
** Description changed:
[Impact]
The so called "browsing a windows network" made use of an SMB1 protocol
version feature. Recent versions of samba, including the one released with
bionic, default to a higher versions of the protocol which lacks this feature.
As a result, the "other location
For anyone wanting to test this bug, please note you will also have to
wait for a gvfs rebuild with this new samba package.
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to gvfs in Ubuntu.
https://bugs.launchpad.net/bugs/1778322
Title:
Bionic verification
Bug reproduced with the following packages:
ubuntu@ubuntu:~$ apt-cache policy samba gvfs-backends
samba:
...
*** 2:4.7.6+dfsg~ubuntu-0ubuntu2.7 500
500 http://br.archive.ubuntu.com/ubuntu bionic-updates/main amd64
Packages
100 /var/lib/dpkg/status
...
gvfs-bac
Bionic verification (continued)
Now installing the new samba packages. Since I need a gvfs rebuild with
the new samba packages, I'm doing that locally.
So in the end I now have:
samba from proposed:
*** 2:4.7.6+dfsg~ubuntu-0ubuntu2.8 500
500 http://br.archive.ubuntu.com/ubuntu bionic-pro
Bionic:
full smbstatus output, showing the connection to the pub share as well:
root@ubuntu:~# smbstatus
Samba version 4.7.6-Ubuntu
PID Username GroupMachine
Protocol Version Encryption Signing
---
Cosmic verification
Confirming the bug:
ubuntu@ubuntu:~$ apt-cache policy samba gvfs-backends
samba:
Installed: 2:4.8.4+dfsg-2ubuntu2.1
Candidate: 2:4.8.4+dfsg-2ubuntu2.1
Version table:
*** 2:4.8.4+dfsg-2ubuntu2.1 500
500 http://br.archive.ubuntu.com/ubuntu cosmic-updates/main amd64
Cosmic verification (continued)
Now installing the updated samba packages, and rebuilding gvfs locally:
samba:
Installed: 2:4.8.4+dfsg-2ubuntu2.2
Candidate: 2:4.8.4+dfsg-2ubuntu2.2
Version table:
*** 2:4.8.4+dfsg-2ubuntu2.2 500
500 http://br.archive.ubuntu.com/ubuntu cosmic-propose
I think I mixed the verification-done tags, but both are done now.
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to gvfs in Ubuntu.
https://bugs.launchpad.net/bugs/1778322
Title:
gvfs-smb-browse can't browse samba/smb tree
To manage
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 sh
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
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 of
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.
https:
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 samba/smb
1 - 100 of 263 matches
Mail list logo
