0

So, on this Ubuntu 18.04 box* running Files 3.26.4 under Other Locations I have this entry for a long gone Brother printing station thing: Screenshot of GNOME Files 3.26.4 showing "Other Locations" with an entry under "Network" named "brcm93390smwvg2-2"

Since it is clearly gone, there is no sensible way of interaction, so I wondered where this might be cached and how to remove it. Unfortunately, I could not find any documentation on this anywhere and searching for the raw string in gconf-editor, dconf-editor and recursively grepping .config also did not bring up any hits.

So, the question is: Where are the entries under "Network" in GNOME Files 3.26.4 saved/cached?

(*The author is aware of the outdatedness of this OS.)

Edit: The printer was never installed on this machine, so this cannot be a remnant of some driver installation.

7
  • 1
    Try lpadmin -x brcm93390smwvg2-2.
    – harrymc
    Commented Dec 28, 2023 at 17:11
  • Ubuntu 18.04 is EoL since April. Please upgrade to a supported release ASAP and unless you have an ESM contract you shouldn't even keep it online and/or use network dependent features. Commented Dec 29, 2023 at 19:32
  • @harrymc: lpadmin: The printer or class does not exist.
    – Kreuvf
    Commented Dec 31, 2023 at 7:28
  • 1
    Do you see it using lpinfo -v ?
    – harrymc
    Commented Dec 31, 2023 at 10:12
  • 1
    Some keywords that could help/are related: Bonjour, mDNS.
    – Daniel B
    Commented Dec 31, 2023 at 22:01

1 Answer 1

2

They are not cached by GNOME; the corresponding GVfs providers all take their data "live" from external sources. There are several sources that network:/// gets its data from – look at the internal GVfs path names to get hints:

gio list network:///

This will show the 'raw' item name, such as dnssd-something, and will reveal it as originating either from DNS-SD (aka Bonjour, aka mDNS, discovered via avahi-daemon) or from SMB (more accurately NetBIOS, discovered via Samba)... or perhaps from Google Cloud Print, which GNOME used to integrate with.

If the result is DNS-SD, the data was received from avahi-daemon, which has no persistent cache; any ghost entries should disappear after restarting the service. Try avahi-browse, or the graphical avahi-discover, and/or Wireshark or tcpdump to figure out what's producing the service advertisements. (Use the capture filter port 5353.)

1
  • There it is: dnssd-domain-brcm93390smwvg2-2._sftp-ssh._tcp. Thank you :) Will try and see where this comes from and try turning it off.
    – Kreuvf
    Commented Dec 31, 2023 at 22:47

You must log in to answer this question.

Not the answer you're looking for? Browse other questions tagged .