Bug 1608739
| Summary: | gnome-user-share is enabled even though gconftool-2 said enabled = false | ||||||
|---|---|---|---|---|---|---|---|
| Product: | Red Hat Enterprise Linux 6 | Reporter: | masanari iida <masanari.iida> | ||||
| Component: | gnome-user-share | Assignee: | Bastien Nocera <bnocera> | ||||
| Status: | CLOSED NOTABUG | QA Contact: | Desktop QE <desktop-qa-list> | ||||
| Severity: | low | Docs Contact: | |||||
| Priority: | unspecified | ||||||
| Version: | 6.10 | CC: | masanari.iida | ||||
| Target Milestone: | rc | ||||||
| Target Release: | --- | ||||||
| Hardware: | All | ||||||
| OS: | Linux | ||||||
| Whiteboard: | |||||||
| Fixed In Version: | Doc Type: | If docs needed, set a value | |||||
| Doc Text: | Story Points: | --- | |||||
| Clone Of: | Environment: | ||||||
| Last Closed: | 2018-07-26 15:14:42 UTC | Type: | Bug | ||||
| Regression: | --- | Mount Type: | --- | ||||
| Documentation: | --- | CRM: | |||||
| Verified Versions: | Category: | --- | |||||
| oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |||||
| Cloudforms Team: | --- | Target Upstream Version: | |||||
| Embargoed: | |||||||
| Attachments: |
|
||||||
|
Description
masanari iida
2018-07-26 08:58:09 UTC
Schema file in gnome-user-share and gconftool output shows
"enabled = false".
In that case the gnome-user-share should be disabled by default
$ gconftool-2 -a /desktop/gnome/file_sharing
bluetooth_obexpush_enabled = false
bluetooth_allow_write = false
bluetooth_accept_files = bonded
bluetooth_notify = false
require_password = never
bluetooth_enabled = false
enabled = false <==
bluetooth_require_pairing = true
/etc/gconf/schemas/desktop_gnome_file_sharing.schemas
<?xml version="1.0"?>
<gconfschemafile>
<schemalist>
<schema>
<key>/schemas/desktop/gnome/file_sharing/enabled</key>
<applyto>/desktop/gnome/file_sharing/enabled</applyto>
<owner>gnome-user-share</owner>
<type>bool</type>
<default>false</default> <==
<gettext_domain>gnome-user-share</gettext_domain>
<locale name="C">
I can manipulate the value using gconftool-2. $ gconftool-2 --type bool --set /desktop/gnome/file_sharing/enabled true $ gconftool-2 --type bool --set /desktop/gnome/file_sharing/enabled false But after I modify it to "enabled=false" again, logout and login, still the file manager shows the gnome-usr-share. I have no idea how to disable it from CLI. (In reply to masanari iida from comment #0) > Description of problem: > I try to disable gnome-user-share function without removing gnome-user-share > RPM. What "gnome-user-share function" are you trying to disable? > I try to modify /desktop/gnome/file_sharing/enabled flag. > It is already "enabled = false", but the gnome-user-sharing is enabled. What do you mean by "gnome-user-sharing is enabled"? > Version-Release number of selected component (if applicable): > gnome-user-share-3.28.2-3.el6 I'm guessing you mean "gnome-user-share-2.28.2-3.el6", correct? > How reproducible: > Always > > Steps to Reproduce: > (1) Install OS. > (2) Install gnome-user-share RPM. > (3) Open "Downloads" folder in filemanager. > > Result: User file sharing is enabled. > > (4) gconftool-2 -a /desktop/gnome/file_sharing |grep enabled > > Actual Result: > enabled=false > > Expexted Result: > enabled= true It's disabled by default, but the value won't be reset if you uninstall and reinstall the package for example. > My understanding is that when I install gnome-user-share RPM, > it is enabled by default. That's not the case, we obviously don't want to share files without the user's consent. > In that case the gconftool-2 also show "enabled = true". > > My actual problem is, how do I disable gnome-user-share function > without removing the RPM. (In reply to masanari iida from comment #3) > I can manipulate the value using gconftool-2. > > $ gconftool-2 --type bool --set /desktop/gnome/file_sharing/enabled true > > $ gconftool-2 --type bool --set /desktop/gnome/file_sharing/enabled false > > But after I modify it to "enabled=false" again, logout and login, > still the file manager shows the gnome-usr-share. What does that mean? > I have no idea how to disable it from CLI. Let me explain one more time. I want to disable file sharing function in "File Browser". From "Application" -> SystemTools -> File Browser Then Click "Download" on left menu. I can see "Personal File Sharing. You can receive files over Bluetooth into this folder". I found that if I remove "gnome-user-share" RPM form the system, then the message "Personal File Sharing. You can receive files over Bluetooth into this folder" doesn't exist any more. So I suspect gnome-user-share RPM is related to my symptom. Then I found a schema file in the RPM file, so I tried to disable the "personal file sharing" using gconftool-2. Created attachment 1470701 [details]
File Browser with Personal file share message
(In reply to masanari iida from comment #5) > Let me explain one more time. > I want to disable file sharing function in "File Browser". > From "Application" -> SystemTools -> File Browser > Then Click "Download" on left menu. > I can see "Personal File Sharing. You can receive files over Bluetooth into > this folder". That's normal, and will appear even if the feature is disabled, the goal being to provide a quick link to the preferences to enable it as needed. It doesn't mean that there's file sharing enabled _at this moment_. > I found that if I remove "gnome-user-share" RPM form the system, > then the message "Personal File Sharing. You can receive files > over Bluetooth into this folder" doesn't exist any more. The only way to disable the message is to remove the RPM, that's correct. > So I suspect gnome-user-share RPM is related to my symptom. > Then I found a schema file in the RPM file, so I tried to disable > the "personal file sharing" using gconftool-2. That's not going to make a difference. > The only way to disable the message is to remove the RPM, that's correct.
This is what I wanted to know.
Thanks
(In reply to masanari iida from comment #8) > > The only way to disable the message is to remove the RPM, that's correct. > This is what I wanted to know. > > Thanks Great, thanks for the reply, I'll close this bug now. |