Authorization Failure and some settings not remembered after restart

When i restart my laptop some of the settings are not remembered like the touchpad side scrolling setting is not remembered nor is the clock setting and it always starts with the wrong time. And when i try to set the time it says it could not authenticate and does not allow me to change the settings. Also i am trying to install an rpm and that authentication fils as well. But on that the authentication box doesn’t even come up. Here’s a screen cap of th error that comes up when trying to install the rpm file…

https://docs.google.com/open?id=0B03UWSVeKK3yenJyYXprNXZWdW8

Anyone have any clue what’s gone wrong and how to fix it?

No? No one? :slight_smile:

On 10/07/2012 09:16 AM, Angelbeast wrote:
> Anyone have any clue what’s gone wrong and how to fix it?

with reference to the image: there are only about a thousand things that
might be wrong…but, without other hints i have to guess that you have
logged in KDE, or GNOME, or LXDE, or XFCE (always tell your operating
system and verion and DE and version!!!) as root and in doing so have
damaged your system’s file permissions…

with reference to the “settings are not remembered” that could also be a
symptom caused by incorrect file permissions…

as to: “it always starts with the wrong time.” that is probably because
you are dual booting with Window and have your hardware clock set wrong
for that situation…(and, there are a thousand previous threads on how
to fix it–and, the fix varies between 12.2 and all previous versions
(another reason you must tell systems/versions to get help)


dd

I know it could be a million things that’s why i’m needing help :slight_smile: And i’m not dual booting…I’m running the current version of Tumbleweed and KDE…I wasn’t doing anything to mess anything up that i know of…Just configuring a printer and not logged in as root…It just started doing it…

On 10/09/2012 12:56 AM, Angelbeast wrote:
> and not logged in as root…It just started doing it…

ok, if you were not logged in as root when you got the imaged
“Authorization Failed” while trying to configure a printer–had you ever
logged into KDE as root before you got that authorization failure?

and what did you do while you were logged into KDE as root? did you add
any software? or change any system settings? or tweak the way the touch
padworks? or adjust the clock? or change any security settings (in say
PolKit or App Armor, or YaST, or or or) or did you change the
permissions of any files by using chown or chmod?

and, this problem “just started” at sometime after you did something
while logged into KDE as root, right?

if no, then i have absolutely no idea what might be wrong.
if yes, then i have absolutely no idea how to fix it.

hopefully, others can be more helpful than i am . . .


dd

Well the clock has always started with the wrong time on reboot since installing 12.2 but i’ve been able to set it until now. I had been logged in as root in a terminal some time before this problem started but i did nothing to change any permissions. The problem is also when i left click on an rpm file and attempt tp install it it gives me that error. But…I am able to do it just fine if i go through add remove programs.

On 10/10/2012 08:16 AM, Angelbeast wrote:

> Well the clock has always started with the wrong time on reboot since
> installing 12.2 but i’ve been able to set it until now.

i have not looked, but wonder if you asked in the forums for help on
fixing that problem (rather than continue to reset the time,
often–which should not be required)

> I had been
> logged in as root in a terminal some time before this problem started
> but i did nothing to change any permissions.

ok, so if you have not been logging into the GUI as root (and have just
been becomming root in a terminal with “su -” then my guess was way off
base…but, that is the most likely scenario i am aware of to pin down
the cause of your symptoms)

so, i’m pretty much out of ideas…except: did you md5sum check the
downloaded 12.2 and then provoke the install medium to self test itself
like shown here: http://tinyurl.com/3qde66h (that is to say, if you
installed from a corrupt disk then there is not much to do but wonder
what was installed that was corrupted in what way–and, is it involved
in the bizarre symptoms you describe (that thousands and thousands of
other have never seen)

> The problem is also when i
> left click on an rpm file and attempt tp install it it gives me that
> error. But…I am able to do it just fine if i go through add remove
> programs.

have a read here:
http://doc.opensuse.org/documentation/html/openSUSE/opensuse-startup/part.reference.software.html

i’m not sure (have not read it lately) but i don’t think you will find
instructions that would lead one to routinely download and then “left
click on an rpm file”

so, anytime you get an rpm file from any non-openSUSE repo you have to
wonder if it is correctly packaged for openSUSE, and is it
trustworthy…so, i’m saying use YaST Software Management and/or zypper
and/or 1Clicks discovered via http://software.opensuse.org/search to
flush out your needs…

hint: i did not mention using package kit or apper

someone else will have to solve your authorization failure symptom…


dd http://tinyurl.com/DD-Caveat

I also don’t seem to be able to reboot via the start menu either.

On 10/13/2012 06:26 AM, Angelbeast wrote:
>
> I also don’t seem to be able to reboot via the start menu either.

it sounds like your system is very bonked.

what happens if you:

-press Ctrl+Alt+F2 (you will then be switched to a full screen terminal)
-type


root                  <and press enter
[root's password]     <you will not see what you type, press enter
shutdown -h now       <and press enter

it may be best to save all your data to an off machine medium, and
reinstall from a KNOWN good (and tested) install medium…then don’t so
hasty to jump in and change everything you can find to change…just use
it a while, as it is born…move slowly and deliberately in your
customizations and ‘improvements’…do NOT do a whole bunch of stuff at
one time (in one day) and then not learn until tomorrow when you boot
that it is all messed up–because you will have NO idea what you did to
kill it.

for example, i updated several packages yesterday…AFTER making a list
of the version i had yesterday which was working fine, AND what i ran in
to update…

so, today (so far) everything seems to be going ok…so, still i will
NOT fiddle with the setup today…maybe monday i will have decided that
what i did friday was ok…and, i can consider doing some more little
things…after a backup…and, after i’ve laid plans.

but, i do that because i’m still pretty new to this Linux thing…and i
always need to build a bridge back to What Works! before i go forward.


dd
http://tinyurl.com/DD-Caveat