Bug#891063:

On 2018-08-28 11:39:08 -0700, Chris Waters wrote: > Programs are allowed to use the environment to communicate with each > other. Programs *do*. If you assume they won't, you're likely to > experience more "breakage". The problem is not with these programs; > the problem is with your assumptions.

Bug#891063:

On Sun, Aug 26, 2018 at 2:57 PM Vincent Lefevre wrote: > > On 2018-08-24 18:04:29 -0700, Chris Waters wrote: > > Ok, sorry that I can't remember *all* the ways that "su" without a > > login option is broken. Even with that, it's still plenty broken, as > > you have observed, > > No, it had worked

Bug#891063:

On 2018-08-24 18:04:29 -0700, Chris Waters wrote: > Blaming emacs for a problem with su which is documented by the su man > page, though, is simply not reasonable. If you're going to insist on > using su instead of sudo, then it's your job to vet all your > environment variables to make sure you do

Bug#891063:

On 2018-08-24 18:04:29 -0700, Chris Waters wrote: > Ok, sorry that I can't remember *all* the ways that "su" without a > login option is broken. Even with that, it's still plenty broken, as > you have observed, No, it had worked very well for *years*, until it got broken by dconf. That's dconf tha

Bug#891063:

On Fri, Aug 24, 2018 at 6:24 AM Vincent Lefevre wrote: > > On 2018-08-14 10:51:41 -0700, Chris Waters wrote: > > Vincent Lefevre writes: > > > But in any case, the bug needs to be fixed. > > > > Yeah, I don't believe this can reasonably be called a bug. Emacs, like > > a lot of big complex apps,

Bug#891063:

On 2018-08-14 10:51:41 -0700, Chris Waters wrote: > If it *really* bothers you to type the pathname, you can make an alias > like: "eroot='emacs /sudo::$(pwd)/$1'". Or even "su -l emacs $(pwd)/$1". > > However, turning off dbus access for emacs, which is something some of > us actually *use*, just

Bug#891063:

On 2018-08-14 10:51:41 -0700, Chris Waters wrote: > Vincent Lefevre writes: > > But in any case, the bug needs to be fixed. > > Yeah, I don't believe this can reasonably be called a bug. Emacs, like > a lot of big complex apps, can and does write to various parts of the > filesystem when used. Th

Bug#891063: not RC

Control: severity -1 important I believe since there is not concensus as to whether this issue is a bug, it is not RC. In particular, it does not render the package unusable, at least not for many many users who do not use emacs as root. d signature.asc Description: PGP signature

Bug#891063:

Vincent Lefevre writes: > But in any case, the bug needs to be fixed. Yeah, I don't believe this can reasonably be called a bug. Emacs, like a lot of big complex apps, can and does write to various parts of the filesystem when used. There's a good chance that if you check your home directory, yo

Bug#891063:

Vincent Lefevre writes: > The current workaround is to unset XDG_RUNTIME_DIR completely (this is > sufficient for Emacs and doesn't affect dbus), but this might yield > other issues and bug reports... > > But in any case, the bug needs to be fixed. Perhaps, but I don't have the impression that t

Bug#891063:

On 2018-08-12 17:33:22 -0500, Rob Browning wrote: > Vincent Lefevre writes: > > The answer is to build Emacs with "--without-gsettings". > > That's not how I read the thread, or rather it sounded like they were > saying that it's not a general solution, but it might be fine for a > custom build f

Bug#891063:

Vincent Lefevre writes: > The answer is to build Emacs with "--without-gsettings". That's not how I read the thread, or rather it sounded like they were saying that it's not a general solution, but it might be fine for a custom build for you. i.e. I read the thread more as emacs is "working as

Bug#891063:

On 2018-08-12 21:19:37 +0200, Vincent Lefevre wrote: > On 2018-08-10 11:35:26 +0200, Vincent Lefevre wrote: > > I've just reported a bug upstream: > > > > https://debbugs.gnu.org/cgi/bugreport.cgi?bug=32413 > > The answer is to build Emacs with "--without-gsettings". This may also fix other bu

Bug#891063:

On 2018-08-10 11:35:26 +0200, Vincent Lefevre wrote: > I've just reported a bug upstream: > > https://debbugs.gnu.org/cgi/bugreport.cgi?bug=32413 The answer is to build Emacs with "--without-gsettings". -- Vincent Lefèvre - Web: 100% accessible validated (X)HTML - B

Bug#891063:

Control: forwarded -1 https://debbugs.gnu.org/cgi/bugreport.cgi?bug=32413 On 2018-08-10 01:09:13 -0500, Rob Browning wrote: > Vincent Lefevre writes: > > "su -l" is not a solution as it reset the current working directory. > > And one should still be able to run X applications after su. > > Hmm,

Bug#891063:

Vincent Lefevre writes: > "su -l" is not a solution as it reset the current working directory. > And one should still be able to run X applications after su. Hmm, is that true? I don't actually know, but the suggestion I'd often heard is to generally avoid running X applications much as root, b

Bug#891063:

On 2018-08-08 03:13:59 +, J. Smith wrote: > This is not an Emacs bug (or a bug at all) IMO. See eg bug#766464 > and its many duplicates, or the summary from bug#827639: > >    The problem is that you are using su to start a X/GNOME application as >    root. su does not clear the environment, s

Bug#891063:

This is not an Emacs bug (or a bug at all) IMO. See eg bug#766464 and its many duplicates, or the summary from bug#827639:    The problem is that you are using su to start a X/GNOME application as    root. su does not clear the environment, so XDG_RUNTIME_DIR points to    your users path, and the

Bug#891063: emacs25: dconf-CRITICAL errors

Control: tags -1 security On 2018-02-21 22:41:53 -0800, Rob Browning wrote: > I'm not sure I understand yet how this makes Emacs unusable -- does it > warn or crash? I've looked at it more closely, and the problem seems to come from that when Emacs is run as root after "su" (without using -m or -

Bug#891063: emacs25: dconf-CRITICAL errors

On 2018-02-21 22:41:53 -0800, Rob Browning wrote: > Vincent Lefevre writes: > > > Package: emacs25 > > Version: 25.2+1-6+b1 > > Severity: grave > > Justification: renders package unusable > > I'm not sure I understand yet how this makes Emacs unusable -- does it > warn or crash? Well, there are

Bug#891063: emacs25: dconf-CRITICAL errors

Vincent Lefevre writes: > Package: emacs25 > Version: 25.2+1-6+b1 > Severity: grave > Justification: renders package unusable I'm not sure I understand yet how this makes Emacs unusable -- does it warn or crash? Thanks -- Rob Browning rlb @defaultvalue.org and @debian.org GPG as of 2011-07-10

Bug#891063: emacs25: dconf-CRITICAL errors

Package: emacs25 Version: 25.2+1-6+b1 Severity: grave Justification: renders package unusable After the latest kernel upgrade, I now get the errors when starting emacs: (emacs:8958): dconf-CRITICAL **: unable to create file '/run/user/1000/dconf/user': Permission denied. dconf will not work pro