Tuesday, April 30, 2024
Homepage · 13.10
 Popular · Latest · Hot · Upcoming
2
rated 0 times [  2] [ 0]  / answers: 1 / hits: 999  / 2 Years ago, wed, april 27, 2022, 3:23:33

Apparently, there's a bug in Upstart that's shipped with Ubuntu 13.10, which overrides the umask set either through $HOME/.profile or /etc/login.defs.



Upstart has been updated to fix this in Trusty, but how do I go about it in Ubuntu 13.10?



The bug report mentions creating an Upstart override job in $HOME/.config/upstart for whatever session you happen to be running. How would one do this?



The report also mentioning disabling Upstart for the user session, which would be the way things worked pre-13.10 if I've understand things correctly. But are there any side effects to this?



How can I find out if the updated Upstart will find its way to 13.10?


More From » 13.10
 Answers
3

I seem to have solved this. Here's what I did:




  1. I copied gnome-session.conf from /usr/share/upstart/sessions to
    gnome-session.override in $HOME/.config/upstart

  2. I edited gnome-session.override and added umask 0002 on the line before
    exec gnome-session --session=$DESKTOP_SESSION

  3. I edited $HOME/.bashrc and added umask 002 to the end of the file



Step 2 made newly created files within the desktop session writable, but the umask for the terminal seemed to remain 0022, which prompted step 3. I repeated these steps for the other users as well.



Comments are very welcome, as I'm not a sure this is the best solution.


[#28170] Thursday, April 28, 2022, 2 Years  [reply] [flag answer]
Only authorized users can answer the question. Please sign in first, or register a free account.
darpose
Add To Favorites
Follow
Total Points: 424
Total Questions: 99
Total Answers: 121
Location: Jersey
Member since Fri, Oct 1, 2021
3 Years ago
darpose questions
Sun, Jan 23, 22, 04:32, 2 Years ago
Fri, Jan 7, 22, 10:51, 2 Years ago
Tue, Apr 25, 23, 23:44, 1 Year ago
Wed, Dec 15, 21, 14:42, 2 Years ago
Wed, Jun 2, 21, 23:41, 3 Years ago
View All
;