Dropbox asks Authentication is needed to run `/usr/sh' as the super user












3















This question has been asked several times, but the standard answer does not apply.



Current system: Ubuntu 18.04, kernel version 4.15.0-29-generic. But it started on - I think - 16.xx.



The system comes with this question at user login. A simple Cancel is fine for Dropbox to do the thing it is supposed to do. Occasionally it asks 3 times, somewhere in a login session.



The standard advice on the forum is to change the according line in /usr/bin/dropbox into PARENT_DIR = os.path.expanduser("~"), but that is already how it comes for the last few years. I install each release from scratch on alternating root partitions, so no left-overs. /home is on a separate partition, so that's a place for a possible left-over. The message has recently been absent for about 3 weeks, but after the latest kernel update it's back. Note that the system now asks for permission to execute /bin/sh, no longer for /usr/bin/dropbox.



Your help would be appreciated.



Tia, Theo










share|improve this question

























  • Maybe you have a desktop file in your startup applications with sudo sh in its Exec line?

    – steeldriver
    Aug 5 '18 at 13:29











  • find . -name "*.desktop" -exec grep sudo {} ; yields nothing.

    – tpg
    Aug 5 '18 at 20:25











  • Thanks for at least steering me in the right direction; I'm also getting that error on login sometimes and I couldn't figure out where it was coming from. I have dropbox installed also. Note that the actual current version of the binary is installed in ~/.dropbox-dist and gets auto-updated, so it could be something in there. The "absent for about 3 weeks" was likely due to the binary not being updated in that time. I'm betting it only happens when a new version is pulled in.

    – Toby J
    Sep 21 '18 at 20:32











  • The same problem appeared for me today ok (K)Ubuntu 18.04. I log in and something asks me fot authentication. Googling yielded that it's caused by Dropbox. This is not because of what I have in startup applications - trying to exec "dropbox start -i" maually triggers the permission dialog as well. I have tried this solution: maketecheasier.com/fixing-authentication-issue-dropbox-ubuntu, but the PARENT_DIR is already set to "~". I have tried reinstalling Dropbox as well, but did not help as well.

    – Mitu
    Oct 18 '18 at 14:45
















3















This question has been asked several times, but the standard answer does not apply.



Current system: Ubuntu 18.04, kernel version 4.15.0-29-generic. But it started on - I think - 16.xx.



The system comes with this question at user login. A simple Cancel is fine for Dropbox to do the thing it is supposed to do. Occasionally it asks 3 times, somewhere in a login session.



The standard advice on the forum is to change the according line in /usr/bin/dropbox into PARENT_DIR = os.path.expanduser("~"), but that is already how it comes for the last few years. I install each release from scratch on alternating root partitions, so no left-overs. /home is on a separate partition, so that's a place for a possible left-over. The message has recently been absent for about 3 weeks, but after the latest kernel update it's back. Note that the system now asks for permission to execute /bin/sh, no longer for /usr/bin/dropbox.



Your help would be appreciated.



Tia, Theo










share|improve this question

























  • Maybe you have a desktop file in your startup applications with sudo sh in its Exec line?

    – steeldriver
    Aug 5 '18 at 13:29











  • find . -name "*.desktop" -exec grep sudo {} ; yields nothing.

    – tpg
    Aug 5 '18 at 20:25











  • Thanks for at least steering me in the right direction; I'm also getting that error on login sometimes and I couldn't figure out where it was coming from. I have dropbox installed also. Note that the actual current version of the binary is installed in ~/.dropbox-dist and gets auto-updated, so it could be something in there. The "absent for about 3 weeks" was likely due to the binary not being updated in that time. I'm betting it only happens when a new version is pulled in.

    – Toby J
    Sep 21 '18 at 20:32











  • The same problem appeared for me today ok (K)Ubuntu 18.04. I log in and something asks me fot authentication. Googling yielded that it's caused by Dropbox. This is not because of what I have in startup applications - trying to exec "dropbox start -i" maually triggers the permission dialog as well. I have tried this solution: maketecheasier.com/fixing-authentication-issue-dropbox-ubuntu, but the PARENT_DIR is already set to "~". I have tried reinstalling Dropbox as well, but did not help as well.

    – Mitu
    Oct 18 '18 at 14:45














3












3








3








This question has been asked several times, but the standard answer does not apply.



Current system: Ubuntu 18.04, kernel version 4.15.0-29-generic. But it started on - I think - 16.xx.



The system comes with this question at user login. A simple Cancel is fine for Dropbox to do the thing it is supposed to do. Occasionally it asks 3 times, somewhere in a login session.



The standard advice on the forum is to change the according line in /usr/bin/dropbox into PARENT_DIR = os.path.expanduser("~"), but that is already how it comes for the last few years. I install each release from scratch on alternating root partitions, so no left-overs. /home is on a separate partition, so that's a place for a possible left-over. The message has recently been absent for about 3 weeks, but after the latest kernel update it's back. Note that the system now asks for permission to execute /bin/sh, no longer for /usr/bin/dropbox.



Your help would be appreciated.



Tia, Theo










share|improve this question
















This question has been asked several times, but the standard answer does not apply.



Current system: Ubuntu 18.04, kernel version 4.15.0-29-generic. But it started on - I think - 16.xx.



The system comes with this question at user login. A simple Cancel is fine for Dropbox to do the thing it is supposed to do. Occasionally it asks 3 times, somewhere in a login session.



The standard advice on the forum is to change the according line in /usr/bin/dropbox into PARENT_DIR = os.path.expanduser("~"), but that is already how it comes for the last few years. I install each release from scratch on alternating root partitions, so no left-overs. /home is on a separate partition, so that's a place for a possible left-over. The message has recently been absent for about 3 weeks, but after the latest kernel update it's back. Note that the system now asks for permission to execute /bin/sh, no longer for /usr/bin/dropbox.



Your help would be appreciated.



Tia, Theo







permissions 18.04 dropbox






share|improve this question















share|improve this question













share|improve this question




share|improve this question








edited Aug 5 '18 at 14:56









Graham

2,24261529




2,24261529










asked Aug 5 '18 at 12:26









tpgtpg

162




162













  • Maybe you have a desktop file in your startup applications with sudo sh in its Exec line?

    – steeldriver
    Aug 5 '18 at 13:29











  • find . -name "*.desktop" -exec grep sudo {} ; yields nothing.

    – tpg
    Aug 5 '18 at 20:25











  • Thanks for at least steering me in the right direction; I'm also getting that error on login sometimes and I couldn't figure out where it was coming from. I have dropbox installed also. Note that the actual current version of the binary is installed in ~/.dropbox-dist and gets auto-updated, so it could be something in there. The "absent for about 3 weeks" was likely due to the binary not being updated in that time. I'm betting it only happens when a new version is pulled in.

    – Toby J
    Sep 21 '18 at 20:32











  • The same problem appeared for me today ok (K)Ubuntu 18.04. I log in and something asks me fot authentication. Googling yielded that it's caused by Dropbox. This is not because of what I have in startup applications - trying to exec "dropbox start -i" maually triggers the permission dialog as well. I have tried this solution: maketecheasier.com/fixing-authentication-issue-dropbox-ubuntu, but the PARENT_DIR is already set to "~". I have tried reinstalling Dropbox as well, but did not help as well.

    – Mitu
    Oct 18 '18 at 14:45



















  • Maybe you have a desktop file in your startup applications with sudo sh in its Exec line?

    – steeldriver
    Aug 5 '18 at 13:29











  • find . -name "*.desktop" -exec grep sudo {} ; yields nothing.

    – tpg
    Aug 5 '18 at 20:25











  • Thanks for at least steering me in the right direction; I'm also getting that error on login sometimes and I couldn't figure out where it was coming from. I have dropbox installed also. Note that the actual current version of the binary is installed in ~/.dropbox-dist and gets auto-updated, so it could be something in there. The "absent for about 3 weeks" was likely due to the binary not being updated in that time. I'm betting it only happens when a new version is pulled in.

    – Toby J
    Sep 21 '18 at 20:32











  • The same problem appeared for me today ok (K)Ubuntu 18.04. I log in and something asks me fot authentication. Googling yielded that it's caused by Dropbox. This is not because of what I have in startup applications - trying to exec "dropbox start -i" maually triggers the permission dialog as well. I have tried this solution: maketecheasier.com/fixing-authentication-issue-dropbox-ubuntu, but the PARENT_DIR is already set to "~". I have tried reinstalling Dropbox as well, but did not help as well.

    – Mitu
    Oct 18 '18 at 14:45

















Maybe you have a desktop file in your startup applications with sudo sh in its Exec line?

– steeldriver
Aug 5 '18 at 13:29





Maybe you have a desktop file in your startup applications with sudo sh in its Exec line?

– steeldriver
Aug 5 '18 at 13:29













find . -name "*.desktop" -exec grep sudo {} ; yields nothing.

– tpg
Aug 5 '18 at 20:25





find . -name "*.desktop" -exec grep sudo {} ; yields nothing.

– tpg
Aug 5 '18 at 20:25













Thanks for at least steering me in the right direction; I'm also getting that error on login sometimes and I couldn't figure out where it was coming from. I have dropbox installed also. Note that the actual current version of the binary is installed in ~/.dropbox-dist and gets auto-updated, so it could be something in there. The "absent for about 3 weeks" was likely due to the binary not being updated in that time. I'm betting it only happens when a new version is pulled in.

– Toby J
Sep 21 '18 at 20:32





Thanks for at least steering me in the right direction; I'm also getting that error on login sometimes and I couldn't figure out where it was coming from. I have dropbox installed also. Note that the actual current version of the binary is installed in ~/.dropbox-dist and gets auto-updated, so it could be something in there. The "absent for about 3 weeks" was likely due to the binary not being updated in that time. I'm betting it only happens when a new version is pulled in.

– Toby J
Sep 21 '18 at 20:32













The same problem appeared for me today ok (K)Ubuntu 18.04. I log in and something asks me fot authentication. Googling yielded that it's caused by Dropbox. This is not because of what I have in startup applications - trying to exec "dropbox start -i" maually triggers the permission dialog as well. I have tried this solution: maketecheasier.com/fixing-authentication-issue-dropbox-ubuntu, but the PARENT_DIR is already set to "~". I have tried reinstalling Dropbox as well, but did not help as well.

– Mitu
Oct 18 '18 at 14:45





The same problem appeared for me today ok (K)Ubuntu 18.04. I log in and something asks me fot authentication. Googling yielded that it's caused by Dropbox. This is not because of what I have in startup applications - trying to exec "dropbox start -i" maually triggers the permission dialog as well. I have tried this solution: maketecheasier.com/fixing-authentication-issue-dropbox-ubuntu, but the PARENT_DIR is already set to "~". I have tried reinstalling Dropbox as well, but did not help as well.

– Mitu
Oct 18 '18 at 14:45










2 Answers
2






active

oldest

votes


















1














For some reason



chmod 755 ~/Dropbox


fixed the problem for me. I recall that I've recently moved my Dropbox folder from NTFS partition symlinked in my home folder to physically be in my home folder - and probably didn't set the permissions after it.






share|improve this answer
























  • 755 did not work for me. The problem persists in Ubuntu 18.10.

    – tpg
    Oct 23 '18 at 14:10











  • For me neither. Also Ubuntu 18.10

    – CPBL
    Jan 29 at 18:23



















0














Watching the terminal when running "start dropbox", I see also the following advice:



Please run "echo fs.inotify.max_user_watches=100000 | sudo tee -a /etc/sysctl.conf; sudo sysctl -p" and restart Dropbox to fix the problem.


This solved the problem for me, without having to give Dropbox sudo powers to do whatever it wants.






share|improve this answer
























  • I did as you advised, copy-pasted your text into a konsole. But alas.

    – tpg
    Feb 4 at 12:28











Your Answer








StackExchange.ready(function() {
var channelOptions = {
tags: "".split(" "),
id: "89"
};
initTagRenderer("".split(" "), "".split(" "), channelOptions);

StackExchange.using("externalEditor", function() {
// Have to fire editor after snippets, if snippets enabled
if (StackExchange.settings.snippets.snippetsEnabled) {
StackExchange.using("snippets", function() {
createEditor();
});
}
else {
createEditor();
}
});

function createEditor() {
StackExchange.prepareEditor({
heartbeatType: 'answer',
autoActivateHeartbeat: false,
convertImagesToLinks: true,
noModals: true,
showLowRepImageUploadWarning: true,
reputationToPostImages: 10,
bindNavPrevention: true,
postfix: "",
imageUploader: {
brandingHtml: "Powered by u003ca class="icon-imgur-white" href="https://imgur.com/"u003eu003c/au003e",
contentPolicyHtml: "User contributions licensed under u003ca href="https://creativecommons.org/licenses/by-sa/3.0/"u003ecc by-sa 3.0 with attribution requiredu003c/au003e u003ca href="https://stackoverflow.com/legal/content-policy"u003e(content policy)u003c/au003e",
allowUrls: true
},
onDemand: true,
discardSelector: ".discard-answer"
,immediatelyShowMarkdownHelp:true
});


}
});














draft saved

draft discarded


















StackExchange.ready(
function () {
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2faskubuntu.com%2fquestions%2f1062568%2fdropbox-asks-authentication-is-needed-to-run-usr-sh-as-the-super-user%23new-answer', 'question_page');
}
);

Post as a guest















Required, but never shown

























2 Answers
2






active

oldest

votes








2 Answers
2






active

oldest

votes









active

oldest

votes






active

oldest

votes









1














For some reason



chmod 755 ~/Dropbox


fixed the problem for me. I recall that I've recently moved my Dropbox folder from NTFS partition symlinked in my home folder to physically be in my home folder - and probably didn't set the permissions after it.






share|improve this answer
























  • 755 did not work for me. The problem persists in Ubuntu 18.10.

    – tpg
    Oct 23 '18 at 14:10











  • For me neither. Also Ubuntu 18.10

    – CPBL
    Jan 29 at 18:23
















1














For some reason



chmod 755 ~/Dropbox


fixed the problem for me. I recall that I've recently moved my Dropbox folder from NTFS partition symlinked in my home folder to physically be in my home folder - and probably didn't set the permissions after it.






share|improve this answer
























  • 755 did not work for me. The problem persists in Ubuntu 18.10.

    – tpg
    Oct 23 '18 at 14:10











  • For me neither. Also Ubuntu 18.10

    – CPBL
    Jan 29 at 18:23














1












1








1







For some reason



chmod 755 ~/Dropbox


fixed the problem for me. I recall that I've recently moved my Dropbox folder from NTFS partition symlinked in my home folder to physically be in my home folder - and probably didn't set the permissions after it.






share|improve this answer













For some reason



chmod 755 ~/Dropbox


fixed the problem for me. I recall that I've recently moved my Dropbox folder from NTFS partition symlinked in my home folder to physically be in my home folder - and probably didn't set the permissions after it.







share|improve this answer












share|improve this answer



share|improve this answer










answered Oct 18 '18 at 14:56









MituMitu

12310




12310













  • 755 did not work for me. The problem persists in Ubuntu 18.10.

    – tpg
    Oct 23 '18 at 14:10











  • For me neither. Also Ubuntu 18.10

    – CPBL
    Jan 29 at 18:23



















  • 755 did not work for me. The problem persists in Ubuntu 18.10.

    – tpg
    Oct 23 '18 at 14:10











  • For me neither. Also Ubuntu 18.10

    – CPBL
    Jan 29 at 18:23

















755 did not work for me. The problem persists in Ubuntu 18.10.

– tpg
Oct 23 '18 at 14:10





755 did not work for me. The problem persists in Ubuntu 18.10.

– tpg
Oct 23 '18 at 14:10













For me neither. Also Ubuntu 18.10

– CPBL
Jan 29 at 18:23





For me neither. Also Ubuntu 18.10

– CPBL
Jan 29 at 18:23













0














Watching the terminal when running "start dropbox", I see also the following advice:



Please run "echo fs.inotify.max_user_watches=100000 | sudo tee -a /etc/sysctl.conf; sudo sysctl -p" and restart Dropbox to fix the problem.


This solved the problem for me, without having to give Dropbox sudo powers to do whatever it wants.






share|improve this answer
























  • I did as you advised, copy-pasted your text into a konsole. But alas.

    – tpg
    Feb 4 at 12:28
















0














Watching the terminal when running "start dropbox", I see also the following advice:



Please run "echo fs.inotify.max_user_watches=100000 | sudo tee -a /etc/sysctl.conf; sudo sysctl -p" and restart Dropbox to fix the problem.


This solved the problem for me, without having to give Dropbox sudo powers to do whatever it wants.






share|improve this answer
























  • I did as you advised, copy-pasted your text into a konsole. But alas.

    – tpg
    Feb 4 at 12:28














0












0








0







Watching the terminal when running "start dropbox", I see also the following advice:



Please run "echo fs.inotify.max_user_watches=100000 | sudo tee -a /etc/sysctl.conf; sudo sysctl -p" and restart Dropbox to fix the problem.


This solved the problem for me, without having to give Dropbox sudo powers to do whatever it wants.






share|improve this answer













Watching the terminal when running "start dropbox", I see also the following advice:



Please run "echo fs.inotify.max_user_watches=100000 | sudo tee -a /etc/sysctl.conf; sudo sysctl -p" and restart Dropbox to fix the problem.


This solved the problem for me, without having to give Dropbox sudo powers to do whatever it wants.







share|improve this answer












share|improve this answer



share|improve this answer










answered Jan 29 at 20:27









CPBLCPBL

298510




298510













  • I did as you advised, copy-pasted your text into a konsole. But alas.

    – tpg
    Feb 4 at 12:28



















  • I did as you advised, copy-pasted your text into a konsole. But alas.

    – tpg
    Feb 4 at 12:28

















I did as you advised, copy-pasted your text into a konsole. But alas.

– tpg
Feb 4 at 12:28





I did as you advised, copy-pasted your text into a konsole. But alas.

– tpg
Feb 4 at 12:28


















draft saved

draft discarded




















































Thanks for contributing an answer to Ask Ubuntu!


  • Please be sure to answer the question. Provide details and share your research!

But avoid



  • Asking for help, clarification, or responding to other answers.

  • Making statements based on opinion; back them up with references or personal experience.


To learn more, see our tips on writing great answers.




draft saved


draft discarded














StackExchange.ready(
function () {
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2faskubuntu.com%2fquestions%2f1062568%2fdropbox-asks-authentication-is-needed-to-run-usr-sh-as-the-super-user%23new-answer', 'question_page');
}
);

Post as a guest















Required, but never shown





















































Required, but never shown














Required, but never shown












Required, but never shown







Required, but never shown

































Required, but never shown














Required, but never shown












Required, but never shown







Required, but never shown







Popular posts from this blog

How to make a Squid Proxy server?

Is this a new Fibonacci Identity?

19世紀