By default, Bugzilla does not search the list of RESOLVED bugs.
You can force it to do so by putting the upper-case word ALL in front of your search query, e.g.: ALL tdelibs
We recommend searching for bugs this way, as you may discover that your bug has already been resolved and fixed in a later release.

Bug 2123

Summary:	Incorrect directory permissions for /tmp/tdesocket-global
Product:	TDE	Reporter:	Darrell <darrella>
Component:	tdebase	Assignee:	Timothy Pearson <kb9vqf>
Status:	PATCHAVAIL ---
Severity:	normal	CC:	be4youcome, bugwatch, darrella
Priority:	P5
Version:	R14.0.x [Trinity]
Hardware:	Other
OS:	Linux
Compiler Version:		TDE Version String:
Application Version:		Application Name:
Attachments:	Patch to fix permissions

Description Darrell 2014-09-22 17:08:30 CDT

I see the following xsession-error message:

[kdesktop_lock] Warning: unable to create control socket '/tmp/tdesocket-global/kdesktoplockcontrol-0'.  Interactive logon modules may not function properly.

Grepping the tdebase sources indicates several source files have #defines that are hard-coded to /tmp/....

On systems where $TMP, $TEMP, $TMPDIR are defined, the hard-coding fails because the user's socket files will be located as defined by those environment variables rather than a hard-coded /tmp.

Comment 1 Darrell 2015-02-05 02:51:58 CST

Created attachment 2445 [details]
Patch to fix permissions

With respect to /tmp/tdesocket-global, the directory is tagged with full ownership of the primary user but perms of 644. As a directory that should be 755? The referenced error message is about not having permissions. As primary user, when listing the contents of /tmp/tdesocket-global, the output is denied.

I recall that the /tmp/tdesocket-global directory being owned by the primary user was discussed in another bug report or the dev mail list.

Proposed patch attached.

Comment 2 Darrell 2015-02-05 11:51:29 CST

The patch works for me in git. Permissions are now 755. Previously I saw the error message every time the screen saver activated. I no longer see the error message when activating the screen saver. I now can browse the directory as normal user without permission errors.

I updated the bug report summary to reflect the actual bug.