Bug 170626

Summary:	Can't change user photo in System Settings
Product:	[Applications] systemsettings	Reporter:	Rubens de Souza Matos Júnior <rubens.matos>
Component:	kcm_useraccount	Assignee:	Frans Englich <frans.englich>
Status:	RESOLVED WORKSFORME
Severity:	normal	CC:	andresbajotierra, finex, serge.iovleff
Priority:	NOR	Keywords:	needs_verification
Version:	4.1
Target Milestone:	---
Platform:	Debian testing
OS:	Linux
Latest Commit:		Version Fixed In:

Description Rubens de Souza Matos Júnior 2008-09-07 17:36:50 UTC

Version:            (using KDE 4.1.1)
OS:                Linux
Installed from:    Debian testing/unstable Packages

When I try to change my user image, the following message appears: "Your administrator doesn't have permission to change your image"
It happens when i start systemsettings from menu and from konsole, with "sudo".
When I run with "sudo" the following error messages appear:

Error: "/tmp/kde-rubens" is owned by uid 1000 instead of uid 0.
Error: "/tmp/ksocket-rubens" is owned by uid 1000 instead of uid 0.
kdeinit4: Shutting down running client.
kdeinit4: preparing to launch /usr/lib/kde4/libexec/klauncher
Error: "/tmp/ksocket-rubens" is owned by uid 1000 instead of uid 0.
Error: "/tmp/kde-rubens" is owned by uid 1000 instead of uid 0.
kdeinit4: preparing to launch /usr/bin/kded4
Error: "/var/tmp/kdecache-rubens" is owned by uid 1000 instead of uid 0.
kdeinit4: preparing to launch /usr/bin/kbuildsycoca4
kbuildsycoca4 running...
Error: "/var/tmp/kdecache-rubens" is owned by uid 1000 instead of uid 0.
Error: "/var/tmp/kdecache-rubens" is owned by uid 1000 instead of uid 0.
kdeinit4: preparing to launch /usr/lib/kde4/libexec/kconf_update
kdeinit4: preparing to launch /usr/bin/knotify4
Error: "/var/tmp/kdecache-rubens" is owned by uid 1000 instead of uid 0.

Comment 1 Dario Andres 2008-11-28 18:48:17 UTC

Here: (KDE 4.1.3 on ArchLinux x86_64): I can't reproduce this. I can setup my user account image, and it is correctly saved and then loaded (on SystemSettings reload).

Can you still reproduce it with a recent KDE version? (4.1.3 / 4.2beta1 / 4.2svn?)

Comment 2 FiNeX 2008-11-29 02:14:48 UTC

I cannot reproduce even using current trunk. It seems more a packaging problem.

Comment 3 Dario Andres 2009-01-13 12:59:55 UTC

No news from the bug reporter, closing. Please reopen this bug report if you experience the same bug again with a recent KDE (4.1.4 / 4.2beta2 / 4.2rc1 / 4.2svn / 4.3svn) . Thanks :)

Comment 4 iovleff 2009-11-04 23:30:54 UTC

I recently upgrade to karmic koala and I experiment exactly the same bug
(KDE 4.3.2)
Serge