Your message dated Sun, 21 Jan 2024 19:15:15 +0100
with message-id <[email protected]>
and subject line Re: [Pkg-utopia-maintainers] Bug#726028: policykit-1:
Authorisation error in KDE when GREP_OPTIONS include output options
has caused the Debian Bug report #726028,
regarding policykit-1: Authorisation error in KDE when GREP_OPTIONS include
output options
to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.
(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact [email protected]
immediately.)
--
726028: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=726028
Debian Bug Tracking System
Contact [email protected] with problems
--- Begin Message ---
Package: policykit-1
Version: 0.105-3
Severity: important
Dear Maintainer,
Setting GREP_OPTIONS in either $HOME/.profile or $HOME/.bash_profile affecting
grep's output causes authorisation failures in KDE. E.g., try the following:
export GREP_OPTIONS="--color=auto --initial-tab --line-number"
When KDE starts, you get an authorisation error from the apt update daemon.
Also, anything requiring administrative privileges to change, such as Login
screen, will refuse to grant access. The refusal is not logged in any of the
usual places that I can see.
The same applies if an alias is defined like this:
alias grep='grep --color=auto --initial-tab --line-number'
In either case, removing --line-number and --initial-tab restores the
authorisation. Setting --color is OK, so long as it's set to auto.
The problem does not appear when using GNOME or XFCE, but their respective
login managers don't source $HOME/.profile or $HOME/.bash_profile. I believe
the problem would also affect users of XDM and SLIM.
I thought it may be due to an unguarded call to grep in a system shell script
somewhere, but I haven't been able to track it down so far.
If memory serves, Ubuntu and Linux Mint used to have exactly the same problem.
I believe they fixed it, but don't quote me on that.
I have logged this as important because, although the workaround is easy to
apply, it is very confusing. I thought I had a major SNAFU in my configuration,
until I remembered I experienced the problem before.
Thanks.
-- System Information:
Debian Release: jessie/sid
APT prefers testing
APT policy: (500, 'testing')
Architecture: amd64 (x86_64)
Kernel: Linux 3.10-3-amd64 (SMP w/6 CPU cores)
Locale: LANG=en_GB.UTF-8, LC_CTYPE=en_GB.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Versions of packages policykit-1 depends on:
ii consolekit 0.4.6-3+b1
ii dbus 1.6.14-1
ii libc6 2.17-93
ii libexpat1 2.1.0-4
ii libglib2.0-0 2.36.4-1
ii libpam0g 1.1.3-9
ii libpolkit-agent-1-0 0.105-3
ii libpolkit-backend-1-0 0.105-3
ii libpolkit-gobject-1-0 0.105-3
policykit-1 recommends no packages.
policykit-1 suggests no packages.
-- no debconf information
--- End Message ---
--- Begin Message ---
There was no follow-up on this request and the given information is not
sufficient to fix this issue.
I'm thus closing the bug report.
Regards,
Michael
On Fri, 11 Oct 2013 13:24:57 +0200 Michael Biebl <[email protected]> wrote:
tags 726028 + moreinfo unreproducible
thanks
Am 11.10.2013 12:58, schrieb James Bannon:
> Package: policykit-1
> Version: 0.105-3
> Severity: important
>
> Dear Maintainer,
>
> Setting GREP_OPTIONS in either $HOME/.profile or $HOME/.bash_profile affecting
> grep's output causes authorisation failures in KDE. E.g., try the following:
>
> export GREP_OPTIONS="--color=auto --initial-tab --line-number"
>
> When KDE starts, you get an authorisation error from the apt update daemon.
> Also, anything requiring administrative privileges to change, such as Login
> screen, will refuse to grant access. The refusal is not logged in any of the
> usual places that I can see.
>
> The same applies if an alias is defined like this:
>
> alias grep='grep --color=auto --initial-tab --line-number'
>
> In either case, removing --line-number and --initial-tab restores the
> authorisation. Setting --color is OK, so long as it's set to auto.
>
> The problem does not appear when using GNOME or XFCE, but their respective
> login managers don't source $HOME/.profile or $HOME/.bash_profile. I believe
> the problem would also affect users of XDM and SLIM.
>
> I thought it may be due to an unguarded call to grep in a system shell script
> somewhere, but I haven't been able to track it down so far.
>
> If memory serves, Ubuntu and Linux Mint used to have exactly the same problem.
> I believe they fixed it, but don't quote me on that.
>
> I have logged this as important because, although the workaround is easy to
> apply, it is very confusing. I thought I had a major SNAFU in my
configuration,
> until I remembered I experienced the problem before.
>
Seeing that polkit doesn't call grep in any way, I don't see how setting
this config option would affect it in any way.
Indeed, adding
export GREP_OPTIONS="--color=auto --initial-tab --line-number"
to ~/.profile and using kdm to log into KDE, I can not reproduce the
issue. Trying to run an application via polkit (e.g. pkexec aptitude)
works just fine.
I've also checked the Ubuntu polkit package. It doesn't ship any patches
on top of the Debian package which seem relevant in this regard.
Since I'm not able to reproduce, you'll need to dig deeper yourself.
I'd probably start stracing the relevant processes.
Michael
--
OpenPGP_signature.asc
Description: OpenPGP digital signature
--- End Message ---
_______________________________________________
Pkg-utopia-maintainers mailing list
[email protected]
https://alioth-lists.debian.net/cgi-bin/mailman/listinfo/pkg-utopia-maintainers
