[Bug 1828107] Re: gvfs can't list shares from smb servers that disabled SMB1
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 AT LEAST IMPLEMENT A MOSTLY ACCEPTABLE DAY TO DAY WORK-AROUND. WHY DO I HAVE TO BEG FOR THIS TO GET IMPLEMENTED//////////////////////////v -- 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 notifications about this bug go to: https://bugs.launchpad.net/gvfs/+bug/1828107/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1778322] Re: gvfs-smb-browse can't browse samba/smb tree
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 BEG for this to get fixed -- 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 notifications about this bug go to: https://bugs.launchpad.net/gvfs/+bug/1778322/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1828107] Re: gvfs can't list shares from smb servers that disabled SMB1
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 solved with adjusting the internal code to instead of fail as it does, just re-init itself in similar logical vein (but better than killing it). So yet again to say explicitly WS DISCOVERY AND RELATED WS ASPECTS ARE NOT THE SOLUTION HERE. How many times do I need to say that here and elsewhere before it gets noticed and read? I am glad that you chimed in Sebastien Bacher, as this is now approaching 5 years outstanding as an issue, despite there being a clearly simple solution (within the code). And I do hear you on the always limited resources. But I genuinely believe someone could bang out a solution to this (as I describe-ish) very quickly. -- 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 notifications about this bug go to: https://bugs.launchpad.net/gvfs/+bug/1828107/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1828107] Re: gvfs can't list shares from smb servers that disabled SMB1
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, producing a not-helpful error, it should simply re-init the relevant components that re-init when I do the "killall gvfsd-smb-browse" after trying to browser the SMB Server. While I have not looked at the code, I know programming well-enough that a basic re-init in this scenario should be a trivial amount of code to write, as a basic work-around until a proper solution is identified. Either way, is this even going anywhere? Are any Devs reading this at all? (Canonical or otherwise) This issue is coming up to 5 years old, and frankly the UX here is unacceptable, potentially even threatening the usability in professional settings. Can we please get a proper solution here? Or at minimum, a built-in stop-gap solution as I have roughly described? -- 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 notifications about this bug go to: https://bugs.launchpad.net/gvfs/+bug/1828107/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1828107] Re: gvfs can't list shares from smb servers that disabled SMB1
@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, 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 notifications about this bug go to: https://bugs.launchpad.net/gvfs/+bug/1828107/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1969602] Re: gnome-shell with focus-mode=mouse behaves wrongly when alt-tabbing
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 Ubuntu Desktop Bugs, which is subscribed to mutter in Ubuntu. https://bugs.launchpad.net/bugs/1969602 Title: gnome-shell with focus-mode=mouse behaves wrongly when alt-tabbing To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-shell/+bug/1969602/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1969602] Re: gnome-shell with focus-mode=mouse behaves wrongly when alt-tabbing
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 coincidentally using Wayland, and I'll probably switch to xorg/X11 once I finish typing here. The way I was able to notice it: 1. Have multiple windows open. Steam maximised behind, two gedit windows open but not one on top of the other. 2. gedit window #1 is what I had focus of, then I open gedit window #2, steam was already opened before gedit window #1, and is behind both windows of gedit at this point. 3. close gedit window #2 by clicking the X on the window dressing 4. instead of focus going back to gedit window #1, focus goes back to steam, because it is now the application "under" my mouse, as gedit window #1 is NOT under my mouse I took a look at selected "fix released" ticket, and the alt ticket, for gnome, and both are not approrpiate tickets for a "fix" as not only have they actually _not_ released a fix, their nature does not involve focus- follows-mouse at all. ** Changed in: gnome-shell Importance: Unknown => Undecided ** Changed in: gnome-shell Status: Fix Released => New ** Changed in: gnome-shell Remote watch: gitlab.gnome.org/GNOME/gnome-shell/-/issues #5439 => None -- 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/1969602 Title: gnome-shell with focus-mode=mouse behaves wrongly when alt-tabbing To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-shell/+bug/1969602/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1828107] Re: gvfs can't list shares from smb servers that disabled SMB1
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 Holy)". Ondrej goes on to report that "GVfs 1.50.x is meant for GNOME 42+." so v1.50.5+ should eventually land in Ubuntu repos probably! As for how that whole workflow works I know nothing about that. So yay! Can't wait to apply that code all over my compies! \o/ -- 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 notifications about this bug go to: https://bugs.launchpad.net/gvfs/+bug/1828107/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1828107] Re: gvfs can't list shares from smb servers that disabled SMB1
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! -- 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 notifications about this bug go to: https://bugs.launchpad.net/gvfs/+bug/1828107/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1828107] Re: gvfs can't list shares from smb servers that disabled SMB1
@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, same internet access. So nothing is really sticking- out for me in that regards that could be relevant for my scenario. But I'm open to even more ideas I had not considered :^) as I really just would love this solved lol. -- 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 notifications about this bug go to: https://bugs.launchpad.net/gvfs/+bug/1828107/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1828107] Re: gvfs can't list shares from smb servers that disabled SMB1
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 relevant, in my case anyways), and the other, something about SMB server cache (which I'm a touch dubious of, but I'm asking for details). Ondrej really carrying the torch there though! :) -- 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 notifications about this bug go to: https://bugs.launchpad.net/gvfs/+bug/1828107/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1828107] Re: gvfs can't list shares from smb servers that disabled SMB1
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 capable, however is unwilling to cooperate until it gets restarted (gvfsd-smb-browse). This has NOTHING to do with WSD in impact, or even as a solution! WSD _IS NOT PRESENT ON MY NETWORK_. Hell, we even have another thread _claiming_ that this was fixed in much earlier versions of Ubuntu (which clearly it wasn't): https://bugs.launchpad.net/ubuntu/+source/gvfs/+bug/1778322 Again, also, _THIS HAPPENS OUT OF THE BOX FOR ALL UBUNTU DESKTOP INSTALLATIONS CURRENT AND FOR THE PAST 4+ YEARS_. ** Changed in: gvfs Remote watch: gitlab.gnome.org/GNOME/gvfs/-/issues #506 => None ** Changed in: gvfs Status: New => Unknown ** Changed in: gvfs Remote watch: None => gitlab.gnome.org/GNOME/gvfs/-/issues #307 -- 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 notifications about this bug go to: https://bugs.launchpad.net/gvfs/+bug/1828107/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1778322] Re: gvfs-smb-browse can't browse samba/smb tree
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 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 notifications about this bug go to: https://bugs.launchpad.net/gvfs/+bug/1778322/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 2007742] Re: Can't update stage views actor (regarding MetaWindowGroup, MetaWindowActorX11, MetaSurfaceActorX11)
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: https://gitlab.gnome.org/GNOME/gnome-shell/-/issues/4281#note_1738026 -- 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/2007742 Title: Can't update stage views actor (regarding MetaWindowGroup, MetaWindowActorX11, MetaSurfaceActorX11) To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-shell/+bug/2007742/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1828107] Re: gvfs can't list shares from smb servers that disabled SMB1
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. This needs to be fixed, yes, because of the security aspect. But primarily because a user shouldn't have to worry about having to kill gvfsd-smb-browse just to reach an SMB network share using an actually secure protocol version. So again, what's the hold-up here? SMB1 is off, and has been for years. -- 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 notifications about this bug go to: https://bugs.launchpad.net/gvfs/+bug/1828107/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1828107] Re: gvfs can't list shares from smb servers that disabled SMB1
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 list shares from smb servers that disabled SMB1 To manage notifications about this bug go to: https://bugs.launchpad.net/gvfs/+bug/1828107/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1828107] Re: gvfs can't list shares from smb servers that disabled SMB1
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 have to install another tool to get this basic functionality working. I would like to remind those reading that this issue was posted ALMOST FOUR YEARS ago. And the "temporary workaround" is to kill the process so it reinitalises. Can we PLEASE get this fixed already?!?!?!? -- 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 notifications about this bug go to: https://bugs.launchpad.net/gvfs/+bug/1828107/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1828107] Re: gvfs can't list shares from smb servers that disabled SMB1
Fresh install of Ubuntu 22.04 and still happening WILL THIS EVER GET FIXED It's been FIVE YEARS since this first came up (other bugs), and SMB1 has been off for security reasons for many years now. This User eXperience is completely garbage, frankly. And no user should realistically be expected to have to open a cli and kill gvfsd-smb-browse just because we don't have a proper implementation for this. It truly begs the question, WHY DOES THIS WORK WHEN THAT PROCESS IS RESTARTED? If restarting it "fixers" it, then why on earth does it break in the first place? And why isn't this already fixed? For humans in the future, use this command for convenience: killall gvfsd-smb-browse And then ctrl+r for future quick recall (in the CLI of your desire). -- 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 notifications about this bug go to: https://bugs.launchpad.net/gvfs/+bug/1828107/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1739635] Re: Can we please get Mouse Acceleration as a GUI control?
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, thanks for pointing me to this. It would be a mistake to call this feature anything but "Mouse Acceleration" as that is what a human is expecting to see when looking for that setting, and using any other term or verbiage would tangibly make it harder to actually know which setting disables "Mouse Acceleration". The fact there are guides showing how to disable "Mouse Acceleration" in other operating systems reliably demonstrates that the terms used by Windows/macOS, etc, are not sensible or self-indicative terms. If the term used were "Mouse Acceleration", a guide realistically would likely not be needed at all. Adding a function should always take usability into consideration, and there is a very tangible usability difference between "Mouse Acceleration" as a term for the function, or _any other term used_. The devs will do as they may, but again, it would be a tangible mistake to not use "Mouse Acceleration" as the name. -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gnome-control-center in Ubuntu. https://bugs.launchpad.net/bugs/1739635 Title: Can we please get Mouse Acceleration as a GUI control? To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-control-center/+bug/1739635/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1739635] Re: Can we please get Mouse Acceleration as a GUI control?
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 Mouse Acceleration. Example google query shows 4,500,000 results : https://www.google.com/search?q=mouse+acceleration+gaming This guide for competitive gaming settings literally has the first recommendation of disabling Mouse Acceleration: https://alexskra.com/blog/competitive-gaming-optimal-settings/ Here's another article that explains that the Windows term used refers to Mouse Acceleration, and the impact of it: https://eliteownage.com/mouseguide.html And another: https://www.billelafros.com/how-to-turn-off-mouse- acceleration-and-why-does-it-matter-for-esports/ Seriously there is an effectively inexhaustible source of information reliably demonstrating that "Mouse Acceleration" is not only the functional term that is appropriate, but it is the one that is used with effectively total dominance in the common vernacular. The justification (made by you, or other people) that Windows/macOS call it something completely pointless can be countered easily with "if they jumped off a bridge, would you?" style of rebuttal. I genuinely see zero actual reason to call it anything but "Mouse Acceleration", as it literally changes how the mouse pointer _accelerates_. Putting aside the aforementioned points made about actual verbiage used in the affected user base (gamers). -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gnome-control-center in Ubuntu. https://bugs.launchpad.net/bugs/1739635 Title: Can we please get Mouse Acceleration as a GUI control? To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-control-center/+bug/1739635/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1739635] Re: Can we please get Mouse Acceleration as a GUI control?
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. Like, I really think there's less value in using the term "Pointer assistance" over the term "Mouse acceleration", as anyone who actually wants to turn the setting off will be looking for "Mouse acceleration" and not "Pointer assistance". -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gnome-control-center in Ubuntu. https://bugs.launchpad.net/bugs/1739635 Title: Can we please get Mouse Acceleration as a GUI control? To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-control-center/+bug/1739635/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1739635] Re: Can we please get Mouse Acceleration as a GUI control?
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. https://bugs.launchpad.net/bugs/1739635 Title: Can we please get Mouse Acceleration as a GUI control? To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-control-center/+bug/1739635/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1969602] Re: gnome-shell with "Focus on hover" behaves wrongly when alt-tabbing
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 it set so focus automatically switches to where the mouse is over top, but to NOT bring any window forward (over top of others) when the focus changes, which is the desired state. Let's say I have on one monitor Vivaldi (browser) maximised, and I have two text editor windows overlapping each other but are only windows that take up a portion of the screen. Text Editor 1 is "on top" of Text Editor 2, and both of these Text Editor windows are "on top" of Vivaldi, in terms of the stack of view (or whatever it is called). On Ubuntu 20.04: If I were to close Text Editor 1, then Text Editor 2 would be on top, and if my mouse is over top of it Text Editor 2 would have focus, and still be on top of Vivaldi. If my mouse is not over top of Text Editor 2 after closing Text Editor 1, then Text Editor 2 may not be focused, however it is _still_ over top of Vivaldi and Text Editor 2 is still visible. This is the desired outcome. On Ubuntu 22.04 If I were to close Text Editor 1, then Text Editor 2 would immediately be moved behind Vivaldi, unless my mouse was over top of Text Editor 2 when closing Text Editor 1, which is often not the case. This is _not_ the desired outcome. To put it another way, it looks like when closing a window the check related to mouse focus immediately is performed, however in 22.04 it brings whatever window it is hovering over to the very front, which is not desired nor how it is configured to behave. Again, in 20.04 this change of window stacking did not happen with the exact same settings, and it happens in 22.04. I rely on focus shifting tied to my mouse (without windows being pulled forward) as a key part of my high-performance workflow. So this change in outcome actually makes my workflow less efficient as I need to bring one or multiple windows back in-front when this forces windows behind others in ways that it shouldn't. I'm unsure if this is related to the original bug, but for me this really does need to be fixed. -- 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/1969602 Title: gnome-shell with "Focus on hover" behaves wrongly when alt-tabbing To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-shell/+bug/1969602/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1828107] Re: gvfs can't list shares from smb servers that disabled SMB1
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 have existed for longer than WSD. Yes, netbios was used previously, but clearly after killing the process I can reach them without SMB v1, just not after the first boot. And just because that's the workaround, does not make it warrant another thread... -- 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 notifications about this bug go to: https://bugs.launchpad.net/gvfs/+bug/1828107/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1828107] Re: gvfs can't list shares from smb servers that disabled SMB1
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, _not_ WSD. And again, I can browse to my SMB shares just by killing and restarting the gvfsd-smbd process, so clearly this has nothing to do with WSD at all, since that's not in play in my environment at all (I know this because my FreeNAS system doesn't serve WSD). -- 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 notifications about this bug go to: https://bugs.launchpad.net/gvfs/+bug/1828107/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1828107] Re: gvfs can't list shares from smb servers that disabled SMB1
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 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 notifications about this bug go to: https://bugs.launchpad.net/gvfs/+bug/1828107/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1828107] Re: gvfs can't list shares from smb servers that disabled SMB1
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 unacceptable. Yes, I know this is volunteer work, but this ticket should not be marked Triaged as no work has actually been done on it, and quite frankly, this should be marked with a higher priority. This kind of functional behaviour is only going to promote the re-enabling of SMB1 on systems, which is the complete opposite of what anyone wants. -- 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 notifications about this bug go to: https://bugs.launchpad.net/gvfs/+bug/1828107/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1828107] Re: gvfs can't list shares from smb servers that disabled SMB1
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 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 notifications about this bug go to: https://bugs.launchpad.net/gvfs/+bug/1828107/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1828107] Re: gvfs can't list shares from smb servers that disabled SMB1
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. 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.net/gvfs/+bug/1828107/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1828107] Re: gvfs can't list shares from smb servers that disabled SMB1
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 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.net/gvfs/+bug/1828107/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1828107] Re: gvfs can't list shares from smb servers that disabled SMB1
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 notifications about this bug go to: https://bugs.launchpad.net/gvfs/+bug/1828107/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1828107] Re: gvfs can't list shares from smb servers that disabled SMB1
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 shares from smb servers that disabled SMB1 To manage notifications about this bug go to: https://bugs.launchpad.net/gvfs/+bug/1828107/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1828107] Re: gvfs can't list shares from smb servers that disabled SMB1
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. 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.net/gvfs/+bug/1828107/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1828107] Re: gvfs can't list shares from smb servers that disabled SMB1
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 shares from smb servers that disabled SMB1 To manage notifications about this bug go to: https://bugs.launchpad.net/gvfs/+bug/1828107/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1828107] Re: gvfs can't list shares from smb servers that disabled SMB1
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. 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.net/gvfs/+bug/1828107/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1828107] Re: gvfs can't list shares from smb servers that disabled SMB1
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 Title: gvfs can't list shares from smb servers that disabled SMB1 To manage notifications about this bug go to: https://bugs.launchpad.net/gvfs/+bug/1828107/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1872235] [NEW] package shared-mime-info 1.9-2 failed to install/upgrade: installed shared-mime-info package post-installation script subprocess returned error exit status 127
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) which then allowed shared-mime-info to be installable. As this interrupted the distro upgrade process, I have rolled back to a backup before the upgrade took place, so this system is not in the same state as when the issue happened. I am not able to provide further debug assistance here. I've performed many upgrades from 16.04 to 18.04 and have only seen this issue happen once so far. ProblemType: Package DistroRelease: Ubuntu 18.04 Package: shared-mime-info 1.9-2 ProcVersionSignature: Ubuntu 4.4.0-177.207-generic 4.4.214 Uname: Linux 4.4.0-177-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.14 Architecture: amd64 Date: Sat Apr 11 13:33:07 2020 ErrorMessage: installed shared-mime-info package post-installation script subprocess returned error exit status 127 InstallationDate: Installed on 2016-03-14 (1489 days ago) InstallationMedia: Ubuntu-Server 14.04.1 LTS "Trusty Tahr" - Release amd64 (20140722.3) Python3Details: /usr/bin/python3.6, Python 3.6.9, python3-minimal, 3.6.7-1~18.04 PythonDetails: /usr/bin/python2.7, Python 2.7.17, python-minimal, 2.7.15~rc1-1 RelatedPackageVersions: dpkg 1.19.0.5ubuntu2.3 apt 1.6.12 SourcePackage: shared-mime-info Title: package shared-mime-info 1.9-2 failed to install/upgrade: installed shared-mime-info package post-installation script subprocess returned error exit status 127 UpgradeStatus: Upgraded to bionic on 2020-04-11 (0 days ago) ** Affects: shared-mime-info (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-package bionic -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to shared-mime-info in Ubuntu. https://bugs.launchpad.net/bugs/1872235 Title: package shared-mime-info 1.9-2 failed to install/upgrade: installed shared-mime-info package post-installation script subprocess returned error exit status 127 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/shared-mime-info/+bug/1872235/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1852101] Re: Monitors keep turning on when in power saving mode, every time.
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, every time. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1852101/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1852101] Re: Monitors keep turning on when in power saving mode, every time.
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 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, every time. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1852101/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1852101] Re: Monitors keep turning on when in power saving mode, every time.
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. https://bugs.launchpad.net/bugs/1852101 Title: Monitors keep turning on when in power saving mode, every time. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1852101/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1852101] Re: Monitors keep turning on when in power saving mode, every time.
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 is normal for LCD), further showing that the monitors are not being told to turn off properly. -- 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, every time. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1852101/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1852101] Re: Monitors keep turning on when in power saving mode, every time.
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. https://bugs.launchpad.net/bugs/1852101 Title: Monitors keep turning on when in power saving mode, every time. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1852101/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1852101] [NEW] Monitors keep turning on when in power saving mode, every time.
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 hardware replacement (CPU intel -> AMD, GPU nVidia -> AMD). So I'm convinced this is a software bug. The first line in logging that I can find that seems to trigger this is: "gnome-shell[1967]: ../../../gobject/gsignal.c:2647: instance '0x55daa50a2920' has no handler with id '145952'" I update my system regularly, so this looks to either be a regression, or uncaught bug. I don't know if other things are causing this, but that's the first line (based on time) that is reported when it turns the monitors back on. ProblemType: Bug DistroRelease: Ubuntu 19.10 Package: gnome-shell 3.34.1-1ubuntu1 ProcVersionSignature: Ubuntu 5.3.0-19.20-generic 5.3.1 Uname: Linux 5.3.0-19-generic x86_64 ApportVersion: 2.20.11-0ubuntu8.2 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Mon Nov 11 09:40:42 2019 DisplayManager: gdm3 InstallationDate: Installed on 2019-03-08 (247 days ago) InstallationMedia: Ubuntu 18.10 "Cosmic Cuttlefish" - Release amd64 (20181017.3) RelatedPackageVersions: mutter-common 3.34.1-1ubuntu1 SourcePackage: gnome-shell UpgradeStatus: Upgraded to eoan on 2019-11-05 (5 days ago) ** Affects: gnome-shell (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug eoan -- 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, every time. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1852101/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1828107] Re: gvfs can't list shares from smb servers that disabled SMB1
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. -- 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 notifications about this bug go to: https://bugs.launchpad.net/gvfs/+bug/1828107/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1828107] Re: gvfs can't list shares from smb servers that disabled SMB1
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 :/ (started in another bug report) -- 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 notifications about this bug go to: https://bugs.launchpad.net/gvfs/+bug/1828107/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1778322] Re: gvfs-smb-browse can't browse samba/smb tree
@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 Title: gvfs-smb-browse can't browse samba/smb tree To manage notifications about this bug go to: https://bugs.launchpad.net/gvfs/+bug/1778322/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1828107] Re: gvfs can't list shares from smb servers that disabled SMB1
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 notifications about this bug go to: https://bugs.launchpad.net/gvfs/+bug/1828107/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1778322] Re: gvfs-smb-browse can't browse samba/smb tree
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. -- 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 notifications about this bug go to: https://bugs.launchpad.net/gvfs/+bug/1778322/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1778322] Re: gvfs-smb-browse can't browse samba/smb tree
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. https://bugs.launchpad.net/bugs/1778322 Title: gvfs-smb-browse can't browse samba/smb tree To manage notifications about this bug go to: https://bugs.launchpad.net/gvfs/+bug/1778322/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1778322] Re: gvfs-smb-browse can't browse samba/smb tree
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. https://bugs.launchpad.net/bugs/1778322 Title: gvfs-smb-browse can't browse samba/smb tree To manage notifications about this bug go to: https://bugs.launchpad.net/gvfs/+bug/1778322/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1828107] Re: gvfs can't list shares from smb servers that disabled SMB1
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 notifications about this bug go to: https://bugs.launchpad.net/gvfs/+bug/1828107/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1778322] Re: gvfs-smb-browse can't browse samba/smb tree
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 protocol set to SMB2. -- 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 notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gvfs/+bug/1778322/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1778322] Re: gvfs-smb-browse can't browse samba/smb tree
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 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: https://bugs.launchpad.net/ubuntu/+source/gvfs/+bug/1778322/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1778322] Re: gvfs-smb-browse can't browse samba/smb tree
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. https://bugs.launchpad.net/bugs/1778322 Title: gvfs-smb-browse can't browse samba/smb tree To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gvfs/+bug/1778322/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1778322] Re: gvfs-smb-browse can't browse samba/smb tree
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. https://bugs.launchpad.net/bugs/1778322 Title: gvfs-smb-browse can't browse samba/smb tree To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gvfs/+bug/1778322/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1778322] Re: gvfs-smb-browse can't browse samba/smb tree
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 notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gvfs/+bug/1778322/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1778322] Re: gvfs-smb-browse can't browse samba/smb tree
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: gvfs-smb-browse can't browse samba/smb tree To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gvfs/+bug/1778322/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1778322] Re: gvfs-smb-browse can't browse samba/smb tree
@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 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: https://bugs.launchpad.net/ubuntu/+source/gvfs/+bug/1778322/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1778322] Re: gvfs-smb-browse can't browse samba/smb tree
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. https://bugs.launchpad.net/bugs/1778322 Title: gvfs-smb-browse can't browse samba/smb tree To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gvfs/+bug/1778322/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1778322] Re: gvfs-smb-browse can't browse samba/smb tree
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=1 /usr/lib/gvfs/gvfsd-smb-browse" Issue returns after reboot. So, looks like was solved in 4.8, but since Disco Dingo 19.04 uses 4.10, looks like it didn't get the fix, not sure. -- 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: https://bugs.launchpad.net/ubuntu/+source/gvfs/+bug/1778322/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1739635] Re: Can we please get Mouse Acceleration as a GUI control?
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 notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gnome-control-center in Ubuntu. https://bugs.launchpad.net/bugs/1739635 Title: Can we please get Mouse Acceleration as a GUI control? To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-control-center/+bug/1739635/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1785689] [NEW] Does not use configured package repositories for sources
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't be installed by this GUI tool, effectively rendering it useless to users who aren't okay with using the CLI. Can we please get gnome-software to actually used the setup APT repositories for the environment? PLEASE? And I mean, the default Canonical repos, universe, plus 3rd party PPAs and others. Until then, this tool is a completely terrible choice for a default Software Installer tool. ** Affects: gnome-software (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gnome-software in Ubuntu. https://bugs.launchpad.net/bugs/1785689 Title: Does not use configured package repositories for sources To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-software/+bug/1785689/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1785692] [NEW] [Feature Request] Mouse Acceleration controls
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 set this that is consistent. The community methods are hacky and inconsistent. Please? :) ** Affects: gnome-control-center (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gnome-control-center in Ubuntu. https://bugs.launchpad.net/bugs/1785692 Title: [Feature Request] Mouse Acceleration controls To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-control-center/+bug/1785692/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1739635] [NEW] Can we please get Mouse Acceleration as a GUI control?
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 Uname: Linux 4.13.0-21-generic x86_64 NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia ApportVersion: 2.20.7-0ubuntu3.6 Architecture: amd64 CurrentDesktop: XFCE Date: Thu Dec 21 08:54:59 2017 InstallationDate: Installed on 2015-07-20 (884 days ago) InstallationMedia: Ubuntu 15.04 "Vivid Vervet" - Release amd64 (20150422) SourcePackage: gnome-control-center UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: gnome-control-center (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug artful -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gnome-control-center in Ubuntu. https://bugs.launchpad.net/bugs/1739635 Title: Can we please get Mouse Acceleration as a GUI control? To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-control-center/+bug/1739635/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
