gtg team mailing list archive

[Thibault Fevry <619445@xxxxxxxxxxxxxxxxxx>]

Public bug reported:

First, why I launched this in root ? Because I needed it. I had done
some experiments with file permissions (To see how gtg would react), and
finally launched this in root.

 It just changed my /tmp permissions.

 This is a big issue because in GNOME this make it impossible to login
in graphical mode. (/usr/lib/libgconf2-4/gconf-sanity-check-2 exited
with error status 256).

 I know they arn't any reasons a normal dev would launch this in sth
else than normal user, but there's also no problem to don't accept root
execution.

 I'll try to add a patch, but I'm not very good in bash.

** Affects: gtg
     Importance: Undecided
         Status: Confirmed

-- 
Launching ./scripts/debug.sh with root permissions breaks /tmp
https://bugs.launchpad.net/bugs/619445
You received this bug notification because you are a member of Gtg
contributors, which is subscribed to Getting Things GNOME!.

Status in Getting Things GNOME!: Confirmed

Bug description:
First, why I launched this in root ? Because I needed it. I had done some experiments with file permissions (To see how gtg would react), and finally launched this in root.

 It just changed my /tmp permissions. 

 This is a big issue because in GNOME this make it impossible to login in graphical mode. (/usr/lib/libgconf2-4/gconf-sanity-check-2 exited with error status 256).

 I know they arn't any reasons a normal dev would launch this in sth else than normal user, but there's also no problem to don't accept root execution.

 I'll try to add a patch, but I'm not very good in bash.