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
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:
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
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
I too am experiencing this in Ubuntu 19.04.
--
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/1828107
Title:
gvfs can't list shares from smb servers that disabled SMB1
To manage
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
So... any word on this bug? :S Still getting it.
--
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/1828107
Title:
gvfs can't list shares from smb servers that disabled SMB1
To manage
@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
Desktop Bugs, which is subscribed to gvfs in Ubuntu.
https://bugs.launchpad.net/bugs/1778322
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
Desktop Bugs, which is subscribed to gvfs in Ubuntu.
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.
--
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
Desktop Bugs, which is subscribed to gvfs in Ubuntu.
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
Desktop Bugs, which is
Um, what about Disco Dingo? 19.04, still having the bug.
--
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
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
Desktop Bugs, which is subscribed to nautilus in Ubuntu.
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
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
Desktop Bugs, which is subscribed to nautilus in Ubuntu.
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
Desktop Bugs, which is subscribed to nautilus in Ubuntu.
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
Desktop Bugs, which is subscribed to nautilus in Ubuntu.
https://bugs.launchpad.net/bugs/1778322
Title:
@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
Desktop Bugs, which is
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
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
Desktop Bugs, which is subscribed to gnome-shell in Ubuntu.
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 :/
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_
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
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
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
Desktop Bugs, which is subscribed to gnome-shell in Ubuntu.
The back light never goes off, peripherals plugged in or not.
--
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/1852101
Title:
Monitors keep turning on when in power saving mode,
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)
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
Desktop Bugs, which is subscribed to gvfs in Ubuntu.
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
Desktop Bugs, which is subscribed to gvfs in Ubuntu.
https://bugs.launchpad.net/bugs/1828107
Title:
gvfs can't list
When is this expected to hit main repos?
--
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/1828107
Title:
gvfs can't list shares from smb servers that disabled SMB1
To manage
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
Desktop Bugs, which is subscribed to gvfs in
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
Desktop Bugs, which is subscribed to gvfs in Ubuntu.
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
Desktop Bugs, which is subscribed to gvfs in Ubuntu.
https://bugs.launchpad.net/bugs/1828107
Title:
gvfs can't list
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
Desktop Bugs, which is subscribed to gvfs in Ubuntu.
https://bugs.launchpad.net/bugs/1828107
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
Desktop Bugs, which is subscribed to gvfs in Ubuntu.
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
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,
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
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
Still having to kill gvfsd-smb-browse each time I reboot just so I can
browse network shares. Clearly the fix didn't actually fix this. This is
going on 4-ish years now.
Additional thread:
https://bugs.launchpad.net/ubuntu/+source/gvfs/+bug/1828107
--
You received this bug notification because
@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,
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
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
So I just experienced this again on a computer different from my earlier
observed situation. Different as in separate hardware, but on Ubuntu
22.04 with Wayland.
Naturally, focus-follows-mouse (or whatever the consistent term is)
continues to be high value for me, and I am indeed in this case
For those wanting to lend their thoughts:
https://gitlab.gnome.org/GNOME/gnome-shell/-/issues/7107
** Bug watch added: gitlab.gnome.org/GNOME/gnome-shell/-/issues #7107
https://gitlab.gnome.org/GNOME/gnome-shell/-/issues/7107
--
You received this bug notification because you are a member of
@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
Desktop Bugs,
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!
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
I don't know if it's the same situation for me, but it might be.
On my work laptop I recently upgraded from Ubuntu 20.04 to 22.04, and
the mouse focus follow function (or whatever it's called) has changed in
this LTS upgrade. For me this is specifically when I close an
application/window.
I have
Fresh install of Ubuntu 22.04 and still happening
WILL THIS EVER GET
Yes, I requested "Mouse Acceleration" not any other name for it, or
behaviour. And this bug/feature request should implement it as "Mouse
Acceleration" as that is the term used when humans talk about it, namely
in the gaming community/industries.
I have posted in that thread you've linked to,
Okay so that's good, but why use an ambiguous term such as "Pointer
assistance" when it's more widely known as "Mouse acceleration"? You
have to drill down into the tooltip to even see the connection, and I
think this is likely to lead to a lot of people not even knowing what
that setting does.
So there are now Mouse Acceleration settings coming to a Release version
of GNOME/Ubuntu? If so, which version is being targetted @jbicha ?
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to gnome-control-center in Ubuntu.
That doesn't make it a good decision. The primary audience of mouse
acceleration as a feature is gamers, and the overwhelming majority
consistently refer to it as Mouse Acceleration. I've been running and
attending gaming events for over 20 years, and I never hear them refer
to it as anything but
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
Desktop Bugs, which is subscribed to gvfs in Ubuntu.
https://bugs.launchpad.net/bugs/1828107
Title:
gvfs can't
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
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
If this is related to: https://gitlab.gnome.org/GNOME/gnome-
shell/-/issues/4281
Then this is causing significant instability in my system. Whether I'm
using Ubuntu 20.04 or 22.04.
Details are here, and I'd rather not repost them:
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,
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
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
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
64 matches
Mail list logo
