Re: Bug#81397: [authorization] fails silently for normal users, cannot start server
This is my answer to a private mail (it seems...) I don't want to talk
about these in private. Please note the reason why I carried this bug
report to the list.
On Sat, Jan 06, 2001 at 02:59:31PM -0200, Henrique de Moraes Holschuh wrote:
> You've already gotten into Branden's permanent shitlist. Please be more
> reserved on ANYTHING you do that might even remotely involve his packages,
> ok? We don't need him going psycothic again.
What is this supposed to mean? There are many users here suffering from this
problem since this is a multi-user system and none of them have the time
to learn the peculiarities of x. They, and I, just want to use this stuff
and I moved the system to unstable because it seemed we needed some of
the bug fixes...
BTW, the users here are not at all interested in the psychological state
of a particular developer. On the contrary, every developer should be required
to deal with every bug report in an objective manner. [*] Which I think is the
way Branden did it, due to the big number of bug reports he must have skimmed
quickly and reassigned it to gdm. I'm sure that he will check the upgrade
path after the additional information I gave. [+]
> Now, back to your problem. Please verify if /etc/X11/Xwrapper.config lists
> allowed_users=something. You want to make that 'something' "console" or
> "any" I think.
Okay, i'll check that. Hadn't found that myself. Thanks. I'm downgrading X
now, but I might need this information.
> This was discussed in d-user, d-devel and numerous bug reports to the point
> that Branden would go "Overfiend" on *anyone* asking it again.
I've never seen this mentioned, nor is it written down anywhere and I don't
think that mailing search stuff really works... And I wouldn't think I'd be
able to find it with this much info (i can't start x as a user). Point
me to an FAQ, and I will understand it then. I thought this might be some
common case and fiddled with some "security" options but wasn't able to resolve
the problem which led me to ask it here, because I didn't find an FAQ. "Deal with it,
or quit." isn't the kind of answer I expect about a display system that we use
[*] Inappropriate dismissal or incorrect evaluation of bug reports could
be dealt with if bug reports were subject to peer review. That's why I
posted here. I'm not blaming Branden, nor do I say that this is a very
important bug. However, it is generating a lot of dissatisfaction with
the system here, and I have to solve it. I thought that review by
wider audience would be instrumental in that.
[+] Not because I'm especially fond of the developer in question. It is
not a matter of personal liking.
Eray (exa) Ozkural
Comp. Sci. Dept., Bilkent University, Ankara