Hi I hope this is the correct place to post this question fairly new to Linux
I keep getting this request from the system to enter the system password
"system policies prevent you from getting the brightness level "
I have read a number of posts about this problem for 11.2
one said it might be a bug
I did try to implement some of the repairs most of witch ended in “No such file”
This system has just been update from 12.2 using the online update to 12.3, 64 bit amd
I did see this system request a couple of times before the update and hoped the update would fix it,
I believe I used that page to update from the 12.2 to 12.3 I know it was through the supper user konsole
Might it be broken that is a possibility from what you say (respecting your superior knowledge in this matter)
It appears to be working the only other issues known about is Thunderbird is slowing down to a crawl and the Brother dcp j925dw scanner is not being recognised the printing works,
DESCRIPTION
pkcheck is used to check whether a process, specified by either --process or --system-bus-name, is
authorized for action. The --detail option can be used zero or more times to pass details about
action. If --allow-user-interaction is passed, pkcheck blocks while waiting for authentication.
The invocation pkcheck --list-temp will list all temporary authorizations for the current session
and pkcheck --revoke-temp will revoke all temporary authorizations for the current session.
This command is a simple wrapper around the polkit D-Bus interface; see the D-Bus interface
documentation for details.
RETURN VALUE
If the specified process is authorized, pkcheck exits with a return value of 0. If the
authorization result contains any details, these are printed on standard output as key/value pairs
using environment style reporting, e.g. first the key followed by a an equal sign, then the value
followed by a newline.
KEY1=VALUE1
KEY2=VALUE2
KEY3=VALUE3
...
Octects that are not in [a-zA-Z0-9_] are escaped using octal codes prefixed with \. For example,
the UTF-8 string føl,你好 will be printed as f\303\270l\54\344\275\240\345\245\275.
If the specificied process is not authorized, pkcheck exits with a return value of 1 and a
diagnostic message is printed on standard error. Details are printed on standard output.
If the specificied process is not authorized because no suitable authentication agent is available
or if the --allow-user-interaction wasn't passed, pkcheck exits with a return value of 2 and a
diagnostic message is printed on standard error. Details are printed on standard output.
If the specificied process is not authorized because the authentication dialog / request was
dismissed by the user, pkcheck exits with a return value of 3 and a diagnostic message is printed
on standard error. Details are printed on standard output.
If an error occured while checking for authorization, pkcheck exits with a return value of 127
with a diagnostic message printed on standard error.
If one or more of the options passed are malformed, pkcheck exits with a return value of 126. If
stdin is a tty, then this manual page is also shown.
NOTES
Since process identifiers can be recycled, the caller should always use pid,pid-start-time to
specify the process to check for authorization when using the --process option. The value of
pid-start-time can be determined by consulting e.g. the proc(5) file system depending on the
operating system. If only pid is passed to the --process option, then pkcheck will look up the
start time itself but note that this may be racy.
AUTHENTICATION AGENT
pkcheck, like any other polkit application, will use the authentication agent registered for the
process in question. However, if no authentication agent is available, then pkcheck can register
its own textual authentication agent if the option --enable-internal-agent is passed.
Manual page pkcheck(1) line 1 (press h for help or q to quit)
I believe this is a kde set up excepted the default set up from the original disk
I hope this is what yopu wanted
Also sorted the Thunderbird issue out that was a root kit scanner playing badly,
On 2013-05-20 12:26, dkar0011 wrote:
>
> robin_listas;2555080 Wrote:
> I believe I used that page to update from the 12.2 to 12.3
Which page? I gave three.
An “online update” is either the command “zypper patch”, or “YaST online
update” modules, and neither of those can do a version upgrade from 12.2
to 12.3.
> I know it
> was through the supper user konsole
Via “konsole” it can be done with a “zypper dup” if you follow the
procedure, specially regarding having the exact set of repos you need
(ie: oss, non-oss, update: no more, no less). If you don’t, the results
are unpredictable.
If this is the case, the procedure for repair (and it doesn’t always
work) is a “zypper dup” per the instructions at the “SDB:System_upgrade”
wiki page.
And notice that this is not recommended to be done from a graphical
session: instead you have to boot to text mode and do it there. The
graphical session can crash in the middle, leaving you nowhere with a
half-cooked system.
An alternative repair, brute force, is an offline upgrade using the DVD
of the same version you have installed. And later you have to redo all
your repo configurations-additions-updates.
–
Cheers / Saludos,
Carlos E. R.
(from 12.1 x86_64 “Asparagus” at Telcontar)
Can we relax for a minute and take in the fact that he said he was new to linux. I doubt he knows anything about upgrades, yast or anything else you are insisting on.
> Can we relax for a minute and take in the fact that he said he was new
> to linux. I doubt he knows anything about upgrades, yast or anything
> else you are insisting on.
Sorry, but no.
He said:
OP> This system has just been update from 12.2 using the online update to
OP> 12.3,
This can cause severe problems, if what he says there is exactly what he
did. We need clarification of what he did before attempting to solve any
other problem.
–
Cheers / Saludos,
Carlos E. R.
(from 12.1 x86_64 “Asparagus” at Telcontar)
Well now that is way better understood than your previous ramble. We need to know if he performed an online upgrade? I myself did an online upgrade from 12.2 to 12.3 with one pc here and I did not have any severe problems, can you clarify what you mean exactly.
Sorry I know you are helping but I do not want anyone worrying without reason.
Am 21.05.2013 04:36, schrieb anika200:
>
> Well now that is way better understood than your previous ramble. We
> need to know if he performed an online upgrade? I myself did an
> online upgrade from 12.2 to 12.3 with one pc here and I did not have
> any severe problems, can you clarify what you mean exactly.
>
It is normal to not have serious problems after an upgrade (more often
some small glitches easily solved) if the upgrade is done correct.
But if for example someone upgrades from 12.2 to 12.3 by running “zypper
up” instead of “zypper dup” you get a zombie system which as a mixture
of both (I intentionally tested that with 12.1 -> 12.2 a while ago to
see what happens).
I give this example to as a real world reason why we need to know
exactly how it was done by the OP.
–
PC: oS 12.3 x86_64 | i7-2600@3.40GHz | 16GB | KDE 4.10.2 | GTX 650 Ti
ThinkPad E320: oS 12.3 x86_64 | i3@2.30GHz | 8GB | KDE 4.10.3 | HD 3000
HannsBook: oS 12.3 x86_64 | SU4100@1.3GHz | 2GB | KDE 4.10.2 | GMA4500
On 2013-05-21 10:46, Martin Helm wrote:
> Am 21.05.2013 04:36, schrieb anika200:
>>
>> Well now that is way better understood than your previous ramble. We
>> need to know if he performed an online upgrade? I myself did an
>> online upgrade from 12.2 to 12.3 with one pc here and I did not have
>> any severe problems, can you clarify what you mean exactly.
Are you sure you did an “online update”? Are you using the name
properly, or do you refer to something else?
> It is normal to not have serious problems after an upgrade (more often
> some small glitches easily solved) if the upgrade is done correct.
> But if for example someone upgrades from 12.2 to 12.3 by running “zypper
> up” instead of “zypper dup” you get a zombie system which as a mixture
> of both (I intentionally tested that with 12.1 -> 12.2 a while ago to
> see what happens).
> I give this example to as a real world reason why we need to know
> exactly how it was done by the OP.
Exactly.
Or worse, he used “yast online update”, which is equivalent of “zypper
patch”.
–
Cheers / Saludos,
Carlos E. R.
(from 12.1 x86_64 “Asparagus” at Telcontar)
On 2013-05-21 16:56, consused wrote:
>
> robin_listas;2558880 Wrote:
>> On 2013-05-21 10:46, Martin Helm wrote:
>>> Am 21.05.2013 04:36, schrieb anika200:
>>>>
>>>> Well now that is way better understood than your previous ramble. We
>>>> need to know if he performed an online upgrade? I myself did an
>>>> online upgrade from 12.2 to 12.3 with one pc here and I did not have
>>>> any severe problems, can you clarify what you mean exactly.
>>
>> Are you sure you did an “online update”? Are you using the name
>> properly, or do you refer to something else?
> Is that a misquote? @anika200 clearly used “online upgrade” twice.
I know, but maybe what I understand by “online update” is not what
people understand by those words. My first language is not English,
after all.
For me it means one of these two only:
YaST online update module, aka “you”.
run “zypper patch”.
But Martin speaks of “zypper up”, which for me is not an “online update”
procedure in SUSE parlance. Yes, it is an update, yes, it is done
online. Yet… it is not what is named “online update”.
What anika200 understands as “online update” is not clear to me.
And what “dkar0011” did, is an absolute unknown to me. He declares being
new to Linux, yet he said he used online update to go from 12.2 to 12.3.
A system version upgrade is a complex procedure which many seasoned
users here shun of as failure prone (I use it a lot). But he did that
via “online update”, and at this I’m totally baffled.
–
Cheers / Saludos,
Carlos E. R.
(from 12.1 x86_64 “Asparagus” at Telcontar)
On 2013-05-21 17:01, Martin Helm wrote:
> Am 20.05.2013 12:26, schrieb dkar0011:
>> I believe I used that page to update from the 12.2 to 12.3 I know it
>> was through the supper user konsole
>
> In order to find out which commands you used, you can try in the su
> console to run
>
> history | grep zypper
>
He probably has to try both the history via “su” and also via “su -”,
they could be different. Huh, I’m not sure of this at all… I’d have to
run an experiment, but I have to go right now.
–
Cheers / Saludos,
Carlos E. R.
(from 12.1 x86_64 “Asparagus” at Telcontar)