Bug 189012
Summary: | hp-toolbox umask causes owner-only readable qt settings file when run as root | ||
---|---|---|---|
Product: | [Fedora] Fedora | Reporter: | Bernard Johnson <bjohnson> |
Component: | qt | Assignee: | Than Ngo <than> |
Status: | CLOSED RAWHIDE | QA Contact: | Ben Levenson <benl> |
Severity: | medium | Docs Contact: | |
Priority: | medium | ||
Version: | 6 | CC: | mefoster, rdieter, twaugh |
Target Milestone: | --- | Keywords: | Reopened |
Target Release: | --- | ||
Hardware: | i386 | ||
OS: | Linux | ||
Whiteboard: | |||
Fixed In Version: | Doc Type: | Bug Fix | |
Doc Text: | Story Points: | --- | |
Clone Of: | Environment: | ||
Last Closed: | 2006-11-09 20:22:42 UTC | Type: | --- |
Regression: | --- | Mount Type: | --- |
Documentation: | --- | CRM: | |
Verified Versions: | Category: | --- | |
oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |
Cloudforms Team: | --- | Target Upstream Version: | |
Embargoed: |
Description
Bernard Johnson
2006-04-14 17:29:23 UTC
qt uses the default umask setting to set the file permission when it's created. It seems your umask setting is not correct here. set umask 0022 will fix the problem Oh, I see now. It's actually line 272 in hp-toolbox setting the umask (0.9.10-1.3). It still seems to me the root of the problem is that qt should set the umask to a sane value before it writes a file that _everyone_ is expected to be able to use. I agree with Bernard. Can't qt use chmod on that file if it's meant to be globally readable? I have taken a look at the hp-toolbox and qt source. Qt tries to read the global setting first and then the local settings in $HOME/.qt. So this warning is needless here and should be ignored. I will disable this annoying warning in next Qt rebuild. I still get this "annoying warning" with qt-3.3.6-0.4.fc5 (the latest from updates-testing); maybe the fix for the warning slipped through the cracks? It would be good to get rid of it, as it just causes noise every time I run any QT app from the command line. Just saw a report of this with FC6 on fedora-list as well. Re-opening. it's now really fixed in qt-3.3.7-1.fc7. The fix will be included in next qt build for FC6 update. |