🤦🤦🤦🙄🙄🙄
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1828107
Title:
gvfs can't list shares from smb servers that disabled SMB1
To manage notifications about this bug go to:
https://bugs.launchpad.n
So when are we going to see SNMPD v5.9.3 pushed out to currently-active
LTS editions of Ubuntu? I have kubernetes nodes on 22.04 that have SNMPD
crashing but not seeing v5.9.3 available, only v5.9.1 on the main repos.
Seems like the fix is already available with a newer version... is there
somethin
Can we PLEASE get this fixed already? I have to deal with this problem
EVERY DAY, and it's now over 5 years old!
I AM SICK AND TIRED OF HAVE TO BEG FOR THIS 30 MINUTE FIX TO BE
IMPLEMENTED
It is CLEAR that restarting the service provides a work-around, and a
VERY RUDIMENTARY CODE CHANGE COULD
CAN WE PLEASE GET THIS FIXED ALREADY? I have to deal with this EVERY DAY
and this is an extremely easy fix in code to make. But I do not have any
approval for code commitment or anything like that.
THIS PROBLEM IS NOW 6 YEARS OLD and could probably be fixed in HALF AN
HOUR.
I am fed up having to
WS Discovery is irrelevant for storage systems that don't even have WS
capabilities at all. Please take note that the relevant component gvfsd-
smb-browse already clearly has the capability to work here but
_requires_ a kill/restart of the component after a fresh reboot to fix.
This could easily be
I am still having this issue every time I reboot, on Ubuntu Desktop
v23.10.
The "gvfs" package installed is version "1.52.0-1".
This issue is 100% reproducible, and my work-around still demonstrates
that the package itself (gvfs) has the capabilities of solving this
itself. Instead of failing, pr
I'm having the same problem seemingly only on my k8s nodes (running on
docker, not containerd), Ubuntu 22.04, and erratic for frequency
snmpd/jammy-updates,now 5.9.1+dfsg-1ubuntu2.6 amd64 [installed]
Can't find a solution anywhere on the internet, so I guess this is me
subscribing to this thread
@seb128 just booted into a live ISO for Ubuntu 23.10, just to test
without installing etc, and still getting the "Failed to retrieve share
list from server: Invalid argument" that I get on other systems :(
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is sub
Yeah I've confirmed with the release notes (
https://gitlab.gnome.org/GNOME/gvfs/-/commit/ca9c22c4c41afe8ce4cc4a0bae376e9d2850f0a5
) that the fix (hopefully the one that actually solves this properly) is
in gvfs v1.50.5! "smbbrowse: Fix empty device listing after unrelated
mount failure (Ondrej Hol
Ondrej actually means if we see issues with gvfs v1.50.5 that we should
open a new issue, to clarify. That suggests (implicitly, not explicitly)
that v1.50.5 of gvfs has (might?) an appropriate fix.
I have no idea when this will hit a version of Ubuntu I can test this
on. But it sounds promising!
@deisi , That certainly is something for valid consideration. In my use-
case there is no network bridging going on, just to clear that up. The
NAS and the client are on the same network (two non-routing switches
exist between them), on the same CIDR IP range, same DHCP server
involved, same DNS, s
It's looking like maybe the most relevant GNOME issue thread is :
https://gitlab.gnome.org/GNOME/gvfs/-/issues/307
(Holy cow! 6 years originally posted! Yikes!)
Also, there looks to be two open MRs in #307 (linked above) which might
help. One is for use of WSD (which as demonstrated isn't relevan
STILL having this problem! Also, the gnome issue of #506 is NOT
RELEVANT! As this issue PREDATED WSD IN TOTALITY.
Like, how more clear do I REEAALLL need to make this? I kill the
gvfsd-smb-browse process, and IMMEDIATELY I can browse SMB shares when
SMB1 is disabled. CLEARLY the application is
SMB1 is disabled on the server/NAS end. And I'm using the out of the box
experience for Ubuntu 23.04. The UX of this whole situation is
effectively broken. And while I know that I can just "killall gvfsd-smb-
browse" to trigger it to restart, that's not the whole point of why this
needs to be fixed
Upgraded to Ubuntu 23.04 and the issue persists... Will this ever get
fixed? This is now over 4 years old.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to a duplicate bug report (1881780).
https://bugs.launchpad.net/bugs/1828107
Title:
gvfs
This is about a bug in this piece of software, and not about finding
another piece of software to take its place. wsdd, as you proposed, is
not included by default in Ubuntu.
The point of seeking a fix for this issue is so that the UX, out of the
box, is better than it is now.
Users should not ha
Fresh install of Ubuntu 22.04 and still happening
WILL THIS EVER GET
FIXED
Why have a package manager if I can just compile from source every time?
This bug report is about the package in the repo not working on newer
nVidia driver packages, and compiling from source is NOT an option.
We need the repo managers to address this.
--
You received this bug notification bec
I'm on Ubuntu 20.04 and I just upgraded my nVidia driver to 470 which
immediately broke my nvtop. Something I use regularly to help balance my
resourcing in my workflow. How is it that it's TWO YEARS and this STILL
HAS NOT BEEN FIXED?
Get it together Canonical. This punishes users for upgrading th
Public bug reported:
Very frequently aptitude will know about new updates from the repos I
use, but when I use Software Updater, it reports there are no more
updates to apply. I have to revert to using apt at the CLI to update my
packages. This really breaks the GUI UX of the environment, and whil
I don't use Windows for serving SMB, I was simply linking the reason for
deprecation. FreeNAS, and other non-windows systems serve SMB v2 and
higher for network shares, and WSD is not present, relevant, or desired
in those configurations. WSD is not the solution, nor replacement, and
SMB v2 and v3
Um, no. Microsoft did not deprecate SMB v1 for WSD, they did it because
it has a blatant security flaw in it :
https://techcommunity.microsoft.com/t5/storage-at-microsoft/stop-using-
smb1/ba-p/425858
Furthermore, SMB v2 and v3.x has been out for years, as modern
implementations of the protocol, _n
There's no way the solution to this is implementing a new protocol to
replace SMB, that would be absurd. The discoverability and connectivity
works when the process is terminated and restarted. Clearly this is
achievable.
--
You received this bug notification because you are a member of Ubuntu
Bu
Getting frustrated because a bug that has existed so long and is key to
network security (connection with SMB1), and has gone ignored for over
1.5 years, is not bad conduct. SMB1 was disabled because of it's
egregious security issues, and having no solution for things like this
as a result is unacc
I AM STILL GETTING THIS ISSUE TO THIS DAY. WILL THIS EVER BE FIXED? This
issue was reported over 1.5 YEARS ago and a fix was already made, but
HAS NOT BEEN RELEASED TO UBUNTU 20.04 WHICH IS THE LONG TERM SUPPORT
VERSION. WHEN WILL THIS BE FIXED?
--
You received this bug notification because you a
The issue went away for me in 19.10 not long after I saw reports that a
fix was released. And same system, the issue came back when I upgraded
to 20.04.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/18
Oh I dunno, maybe the "Fix Released" part? You do realise there is code
out there that fixes this that hasn't hit 20.04, right? It was solved in
later 19.10, now broken in 20.04.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://
When is this expected to hit main repos?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1828107
Title:
gvfs can't list shares from smb servers that disabled SMB1
To manage notifications about this b
Why has this STILL not been rolled out to 20.04??? It was fixed for
19.10, but still not for 20.04...
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1828107
Title:
gvfs can't list shares from smb ser
STILL getting this error in Ubuntu 20.04. Just upgraded to 19.10 and I
get this error immediately. How exactly is this not already upstreamed
and fixed already??? >:|
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchp
Really hope this gets solved soon, have to kill the process after
browsing shares every time I reboot.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1828107
Title:
gvfs can't list shares from smb se
But once I nicely kill the process, I not only can connect to the share,
I can still discover network shares. So, I don't really know how to
explain that.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/
Can we please get this addressed already? This issue persists in 19.10
(haven't tested in 20.04 yet due to unrelated reasons)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1828107
Title:
gvfs can't
Public bug reported:
When doing a distro-upgrade from Ubuntu 16.04 to 18.04 shared-mime-info
broke the whole process throwing errors about libicu60, which was
installed as new in the upgrade process. While the system was broken, I
forced a reinstall of libicu60 (apt install --reinstall libicu60) w
That's fine! :) Misunderstandings happen, I hope I clarified
effectively.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1858961
Title:
Update-Manager does not apply updates seen by the package manag
I don't see how that's relevant. My package manager sees there are
packages available, but the Update-Manager doesn't always apply them.
When I go to the CLI and manually tell apt to apply the updates it sees,
then they get updated.
I'm basing the "available packages" on what my package manager te
So far it's fixed for me! Yay!!!
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1847570
Title:
PulseAudio automatically switches to HDMI sound output on login
To manage notifications about this bug
Woot! Thanks for rolling this out all involved! \o/ Stuff like this is
why I love FOSS.
Now to try it out!
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1847570
Title:
PulseAudio automatically swit
Public bug reported:
Very frequently Update-Manager will only update part of the packages
that are reported as available for updating. I don't know how to tell
which ones it does and which it doesn't update. For example, it won't
update any libreoffice packages at all recently.
I have to go to th
Waiting on release for Eoan :D
Thanks for getting this fixed! \o/
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1847570
Title:
PulseAudio automatically switches to HDMI sound output on login
To ma
Any word how long before this might hit main repos for 19.10?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1847570
Title:
PulseAudio automatically switches to HDMI sound output on login
To manage
The back light never goes off, peripherals plugged in or not.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1852101
Title:
Monitors keep turning on when in power saving mode, every time.
To manage
I just said yes that it stays dark, and plugging them in did not seem to
"wake" it back up. The system does not appear to be properly entering
ACPI sleep, just that the screen is "black" (but I can still see the
back light through the LCD matrices).
--
You received this bug notification because y
I don't see evidence that the peripherals are to cause here. Plugging
them in/not does not appear to have a change in results.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1852101
Title:
Monitors k
I rebooted (so no apps are running really), locked computer, and
unplugged all USB devices.
The screen eventually goes dark, but the monitors never get told to be
"off"/standby (lights stay green on them), and I see the mouse pointer.
I can also see the back panel lighting through the screen (as
The issue persisted on my last computer, which would have a completely
different user, and I was not using GNOME Extensions at that point.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1852101
Title:
Public bug reported:
Whenever I lock my computer, or it goes into power saving mode
automatically, the monitors turn back on and show the lock screen a few
seconds later. This has persisted now for about a year, has persisted
across multiple upgrades (18.10, 19.04, 19.10) as well as complete
hardw
And as a reminder, my "solution" is to:
1. trigger the error by trying to browse to an SMB share with SMB1 disabled on
the server-side
2. "pidof gvfsd-smb-browse"
3. "kill $PID" from above (regular kill, not -9)
It then works, I can actually get to shares.
I have to do this after _every_ reboot
So I just upgraded to 19.10 and I am _STILL_ having this issue. I have
had this issue now through two whole major releases! SMB1 being turned
off _SHOULD NOT BREAK THIS_. SMB1 is a _MAJOR_ security threat, and this
really needs to get fixed!
I've been reporting this failure since April of 2019 :/
So this is actually happening now every time I lock my computer, no
power change whatsoever (no standby, no suspend to RAM, no power
off/reboot). So this is now becoming very frustrating to work with as I
have to change my default audio device every time I use my computer now
so that my volume cont
Public bug reported:
I'm using Adwaita-Dark with the gnome-themes-extra package that comes
available to Ubuntu 19.10.
When I go to a login form, github search, or other text field that has
auto-complete options, the presented auto-complete options are black
text on black background, and are compl
I just upgraded from 19.04 to 19.10 and this happens every reboot, my
default audio switches from my sound card to my HDMI audio output.
This kind of a regression is really going to turn new users off to
Ubuntu/Linux.
--
You received this bug notification because you are a member of Ubuntu
Bugs,
@andreas oops I think I got muddled up, sorry about that! I'm going to
unsub from this bug (which I should have done earlier).
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1778322
Title:
gvfs-smb-b
So... any word on this bug? :S Still getting it.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1828107
Title:
gvfs can't list shares from smb servers that disabled SMB1
To manage notifications abou
In fact I literally just tried it again, and get the same issue, where
it does not prompt for login, and the related gvfs process needs to be
killed.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/17783
The bug still exists for me on Disco, so I don't see how you arrive at
the position that it "works" out of the box. It does not "work" for me,
the bug exists on Disco for me. And I've regularly kept my system up to
date. I've reported this multiple times in this thread and seem to be
ignored.
--
Can we also get this bug marked as Disco to? Not just Bionic and Cosmic?
I'm _still_ getting the issue with a fully updated Disco (19.04).
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1778322
Title:
I too am experiencing this in Ubuntu 19.04.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1828107
Title:
gvfs can't list shares from smb servers that disabled SMB1
To manage notifications about thi
Well I know for a fact it has SMB1 disabled, as I disabled it myself.
Ran the test you asked, didn't output any info that seemed to
conclusively say which protocols were visible. I'm intentionally
disabling SMB1 for the very public security concerns. In this case, the
"server" has a minimum protoco
I'm using Disco as my daily driver and I still have this issue every
time I reboot. I also update nearly daily from the main repos, so any
fixes that may have rolled out, thus-far, aren't fixing it.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed
Okay but it isn't fixed in Dingo. I still get it. What more do you want
me to do, not say it's happening for me in Disco Dingo? Because it is...
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1778322
T
I have the issue in Disco... and have since I upgraded to it, as I
mentioned
https://bugs.launchpad.net/ubuntu/+source/gvfs/+bug/1778322/comments/35.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/17783
Um, what about Disco Dingo? 19.04, still having the bug.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1778322
Title:
gvfs-smb-browse can't browse samba/smb tree
To manage notifications about this
Checked smb.conf so far only seeing "client min protocol = SMB2" which
should not be causing this problem...
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1778322
Title:
gvfs-smb-browse can't browse
@Andreas , I already have those installed. Still seeing the same effect
each reboot.
Not sure why my result is different. I do have two workgroups in play
though, so I wonder if that's it...
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubu
Also, since samba package isn't installed by default (at least in my
18.10 to 19.04 upgrade), how do we fix this without the samba package
installed?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/17783
I'm seeing this issue with Disco Dingo 19.04
Using samba/disco,now 2:4.10.0+dfsg-0ubuntu2 amd64 [installed]
Upgrade didn't install samba by default, and nautilus is still having
issues with network share being SMB2 minimum
Solved by:
1. Killing PID of gvfsd-smb-browse
2. Running "GVFS_SMB_DEBUG=
Um, this issue still persists...
Can we PLEASE not have bugs expire because of no activity from devs?
That's uncool.
** Changed in: xscreensaver (Ubuntu)
Status: Expired => Confirmed
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubu
Why yes, it is generally the same, except I submitted 12 months ago, heh
;P
Either way, I'd like to get this implemented. Had I know the gitlab for
Gnome was the more appropriate place to post this, I would have.
Which area do Gnome developers _actually_ look at? :S
--
You received this bug not
Original install was Ubuntu (3-4 years ago?), along the way I installed
the XFCE meta package (forget if it was the xubuntu meta or what), and
switched the DE to XFCE, but the core is base Ubuntu. That's why I use
that nomenclature.
This is a desktop, so no laptopy stuff here. Last I checked xscre
I tried to re-enable the bluetooth service to start as default, and so
far the issue is not happening again. Not sure what's up here...
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1802774
Title:
B
So, you want me to "break" my setup again, try to reproduce, and paste
the log?
Hmmm, the bug reporting tool doesn't submit that file? Can't recall,
does it ever have any sensitive info it?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubun
Public bug reported:
I recently upgraded from 18.04 to 18.10, and after the upgrade I
immediately started seeing very long delays after login. Not only that,
the xfce4-notifyd aspect would just time out and never complete loading.
The solution was
systemctl disable bluetooth
So, to disable the
Public bug reported:
Something keeps triggering the login, as if the mouse is moved or
keyboard pressed. This results in screens never going into standby, and
the login prompt always being up, so screensaver animations mostly don't
continue.
This has persisted across multiple Ubuntu versions and
Public bug reported:
Bluetooth keeps starting by default on boot, I turn it off, and it's not
set to start in startup applications. Need a way for it to be always off
by default, but still be able to turn it on when I need it.
I've been seeing this for many major Ubuntu versions for years. Finall
Public bug reported:
The default software tool "gnome-software" that ships with Ubuntu,
doesn't even use the repositories that APT is setup.
What's the point in using such a ham-string software installation GUI
tool if it won't even use the environment it's setup with?
So much software just can'
Public bug reported:
Can we please get the ability to adjust Mouse Acceleration back?
This is important for touchpads and gaming on Linux (yes, that's a
thing).
It's not exactly a complicated feature to re-add, and I'm not even sure
why it was removed in the first place. Users need a GUI way to
Public bug reported:
Here is an example image : https://imgur.com/J4xZht3
I've had this issue for years, and I really want to see it fixed, as it
is a regression that came a long time ago. It didn't do this when I
started using compiz (year ago), but it does it every time now.
ProblemType: B
Public bug reported:
Can we please get a GUI control for adjusting and turning off Mouse
Acceleration? This is really important for gaming.
ProblemType: Bug
DistroRelease: Ubuntu 17.10
Package: gnome-control-center 1:3.26.2-0ubuntu0.1
ProcVersionSignature: Ubuntu 4.13.0-21.24-generic 4.13.13
Unam
Public bug reported:
Can we please get a GUI control for adjusting and turning off Mouse
Acceleration? This is really important for gaming.
ProblemType: Bug
DistroRelease: Ubuntu 17.10
Package: unity-control-center 15.04.0+17.10.20170930-0ubuntu1
ProcVersionSignature: Ubuntu 4.13.0-21.24-generic
I haven't seen anyone do anything on this bug. I'm now on 17.04 and I'm
still having the issue... I love that open source projects can get
updates, but I really don't understand how people are supposed to get
attention to Ubuntu bugs, if things like this just get ignored...
--
You received this b
Public bug reported:
I use network-manager to connect to openVPN servers.
First, when adding a new VPN config, entering a login is required, and
we are unable to save if we do not enter a username. This is a security
flaw as we need the ability to enter login and password each and every
time as a
I was able to import my config after making the adjustment outlined here
: https://askubuntu.com/a/816140
However now I am having issues with systemd and my tap device, I'm not
sure it's correctly creating it as I'm doing bridging not tunneling on
the server end :( (probably unrelated here though)
I'm on ubuntu 16.10,
I have pfsense running my openVPN service, and I exported the client
config to an ovpn file (inline).
When I get network-manager to import, I STILL get "the plugin does not
support import capability".
This bug has been open for OVER 6 YEARS now. How about we get this
conclus
I'm on Ubuntu 16.10 now, with compiz 0.9.13.0, and I still have this
weirdness.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1589165
Title:
cube rotate draws improperly on multi-monitor setup
To m
Public bug reported:
Example : http://imgur.com/J4xZht3
I have 3 monitors, 1920x1080, all landscape.
When I rotate my cube, you'll see it draws the adjacent monitors in ways
it shouldn't. I think this issue started in 15.10, but I'm not sure. I
know that in past builds this wasn't an issue thoug
86 matches
Mail list logo
