Hello members,
I have made a new installation of Sparky Game over. As I wanted to use the Aptus-tool, I noted, that it cannot be opened.
1. I start the Aptus-link from the Menu
2. It appears the window for the login as the Administrator.
3. I fill up the password and push the ok-button
4. nothing happens...!
What is wrong?
Did you make a system upgrade?
If yes, make sure you have 'lxpolkit' package installed.
Run it via a terminal emulator and check the output:
remsu sparky-aptus
or
sudo aprky-aptus
Hello pavroo,
thank you for the fast reply.
I thought, I would have done a system upgrade with running the programm "Sparky first run". But it seems so, that it has not functioned.
The 'lxpolkit'-package? Unfortunately I don't know, how I can check this... (I'm a poor MS-Windows-rat) :-\
in the Menu of the Sparky-Desktop I could not discover it...
So I have ignored this point.
I opened the LXTerminal:
The command "remsu sparky-aptus"
had no reaction.
The command "sudo sparky-aptus"
had started the APTus-Programm. :)
Here I could create an update-list and then run a system-update. The programm downloaded 574MB! and it seemed that the update-process was running.
After this was finished, I started the computer anew.
But unfortunately the problem is the same: I can't start the APTus from the Menu: It seems that it was opening a window in the background for a second, but in the end it doesn't appear a programm-window.
So I repeat the process with opening the LXTerminal and the command "sudo sparky-aptus". Now the programm doesn't create a new update-list; I think because it's done by the first time and I conclude, that the system is now up to date.
At this moment where I write these sentences, I want start the APTus-Programm via opening the LXTerminal and the command "sudo sparky-aptus" again for a better explanation, but the system answers:
"yad: cannot create shared memory for key 123450: Die Datei existiert bereits" ("Die Datei existiert bereits" = "the file already exists")
I think I must start the computer anew.
apt-cache policy lxpolkit
Will give you the answer.
Thank you, blaze,
the system answers:
lxpolkit:
Installiert: (keine)
Installationskandidat: 0.5.3-1
Versionstabelle:
0.5.3-1 500
500 http://ftp.debian.org/debian testing/main amd64 Packages
It seems, that lxpolkit is not installed... :-\
How can I install lxpolkit? Can I use the APTus-Programm (which is only running with the Terminal-command)?
Run in the LXterminal:
sudo apt update
sudo apt install lxpolkit
Then reboot to let the LXDE uses lxpolkit on startup.
Hehe, I'm a superman ;D
with the command
sudo apt-get install lxpolkit
the lxpolkit is now installed.
If it helps to the problem, that APTus cannot be opened from the menu of the sparky-desktop, I will see later. probably I must restart the computer...
Thank you, pavroo,
you wrote to the same time to me, as I wrote my post.
:)
Hello pavroo,
after installing lxpolkit and rboot the computer unfortunately the problem is the same: I can't start the APTus from the Menu.
It seems strange, that I am the first or the only one which has this problem? You would think that my computer is perhaps a kind of Millennium Falcon of Han Solo, but nothing!
With your help the problem is not essential now, because I can start APTus with the command, but it's not nice.
Show me:
pidof lxpolkit
apt-cache policy lxpolkit
ls -l $HOME/.config/autostart
cat $HOME/.config/autostart/lxpolkit.desktop
What is your sparky installation? 32 or 64 bit?
Hello pavroo,
these are the answers from the system to "your" commands:
goofy@pc01goofy:~$ pidof lxpolkit
1448
goofy@pc01goofy:~$ apt-cache policy lxpolkit
lxpolkit:
Installiert: 0.5.3-1
Installationskandidat: 0.5.3-1
Versionstabelle:
*** 0.5.3-1 500
500 http://ftp.debian.org/debian testing/main amd64 Packages
100 /var/lib/dpkg/status
goofy@pc01goofy:~$ ls -l $HOME/.config/autostart
insgesamt 0
goofy@pc01goofy:~$ cat $HOME/.config/autostart/lxpolkit.desktop
cat: /home/goofy/.config/autostart/lxpolkit.desktop: Datei oder Verzeichnis nicht gefunden (file or directory not found)
I have installed the Sparky-64bit-version
Mayby some additional Informations with importance:
The Sparky-First-Run programm is also running only with the terminal-command. I tried the command:
sudo sparky-firstrun
Now, it has downloaded some files. In the end it showed the message:
WARNING: apt does not have a stable CLI interface. Use with caution in scripts.
1. How did you install sparky - using live installer or advanced installer?
2. Did you change root password or you use only one for user 'goofy' and root?
3. show me:
groups
ls -l $HOME/.su-to-root
4. What happens running:
gksu sparky-aptus
gksudo sparky-aptus
Hello pavroo,
first I want say that I'm very grateful to you for your help! :)
1. Surely I have used the live installer. All the installation running automatically.
2. No, I haven't changed the root password.
No, I think the user goofy and root are seperatly (I remember there was a question about this during the installation). But in the login-window it is only possibel to use the user goofy; It's no option to login as root.
3. (...Unfortunately I can't find an option to set the LXTerminal-window to english...)
Here are the results:
goofy@pc01goofy:~$ groups
goofy adm dialout fax cdrom floppy tape sudo audio dip video plugdev users fuse scanner lpadmin bluetooth netdev
goofy@pc01goofy:~$ ls -l $HOME/.su-to-root
ls: Zugriff auf '/home/goofy/.su-to-root' nicht möglich: Datei oder Verzeichnis nicht gefunden
(access to '/home/goofy/.su-to-root' not possible: file or directory not found)
4.
goofy@pc01goofy:~$ gksu sparky-aptus
goofy@pc01goofy:~$ gksudo sparky-aptus
goofy@pc01goofy:~$
To the last both commands in point 4, the system doesn't give any answer.
Sorry, should be '.su-to-rootrc'
If it doesn't exist, run:
leafpad .su-to-rootrc
type into the file:
SU_TO_ROOT_SU=sudo
save the file, then re-login to your account.
Edit:
one more question, if the file exist, and still no luck, run and show the output:
gksu -d sparky-aptus
gksudo -d sparky-aptus
The file '.su-to-rootrc' does already exists. It contains one line exactly with 'your' code: SU_TO_ROOT_SU=sudo
The output from the command 'gksu -d sparky-aptus' is:
goofy@pc01goofy:~$ gksu -d sparky-aptus
xauth: -e0f5e98b1c4d8a0b6fb7b7f2a4492388
-
display: -:0.0-
final xauth: -e0f5e98b1c4d8a0b6fb7b7f2a4492388
-
final display: -:0.0-
STARTUP_ID: gksu/sparky-aptus/1838-0-pc01goofy_TIME139252
gksu_context_run: buf: -Passwort: -
no password on keyring
DEBUG (run:after-pass) buf: -Passwort: -
-EBUG (run:post-after-pass) buf: -
-EBUG (run:post-after-pass) buf: -su: Fehler bei Authentifizierung
-EBUG (auth_failed) buf: -su: Fehler bei Authentifizierung
goofy@pc01goofy:~$
It's strange that the output says, that there is no Password on keyring in spite of the fact, that I have done exactly this: The command 'gksu -d sparky-aptus' asks for this password, which I must given.
The output from the command 'gksudo -d sparky-aptus' is:
goofy@pc01goofy:~$ gksudo -d sparky-aptus
No ask_pass set, using default!
xauth: /tmp/libgksu-1Ya105/.Xauthority
STARTUP_ID: gksudo/sparky-aptus/2105-0-pc01goofy_TIME1166664
cmd[0]: /usr/bin/sudo
cmd[1]: -H
cmd[2]: -S
cmd[3]: -p
cmd[4]: GNOME_SUDO_PASS
cmd[5]: -u
cmd[6]: root
cmd[7]: --
cmd[8]: sparky-aptus
buffer: -GNOME_SUDO_PASS-
brute force GNOME_SUDO_PASS ended...
Yeah, we're in...
xauth: /tmp/libgksu-1Ya105/.Xauthority
xauth_env: /home/goofy/.Xauthority
dir: /tmp/libgksu-1Ya105
goofy@pc01goofy:~$
My attempts show that it is a general problem: Almost all system-tools from the desktop-menu are concerned. I cannot open these from the Menu.
Show me:
ls -l $HOME/.Xauthority
Anyway I suggest to try to clean up the file:
mv $HOME/.Xauthority $HOME/.Xauthority.bak
touch $HOME/.Xauthority
then reboot.
The answer from the command 'ls -l $HOME/.Xauthority' is:
goofy@pc01goofy:~$ ls -l $HOME/.Xauthority
-rw-r--r-- 1 goofy goofy 54 Jan 4 06:54 /home/goofy/.Xauthority
goofy@pc01goofy:~$
I have tried
mv $HOME/.Xauthority $HOME/.Xauthority.bak
touch $HOME/.Xauthority
and reboot, but it changes nothing.
Hello pavroo,
now I observed a new problem: I wanted to start APTus via the LXTerminal with (like at the beginning of our discussion)
goofy@pc01goofy:~$ sudo sparky-aptus
[sudo] Passwort für goofy:
but I cannot type the password anymore, because there is no reaction to my keyboard inputs. I have reboot but it stills the same.
Can it be, that something of the last inputs has changed something important?
I have no more ideas by now, I only suggest to make fresh installation.
I second that. Have read the whole thread, and nothing comes to mind.
Goofy, have you done any other changes or configurations to your system that is not mentioned in this thread?
Hello pavroo, thank you very much for your time!
Hello blaze, thank you for your concerning...
No, I have made no changes, exept ot install Libre-Office or the Ryzom-Client. But this problem existed from the beginning. Only I have not recognized it. When I ran "Sparky-First-run" the first one, I thought this was normal, that I have seen nothing; Nothing means exept the small stopwatch and something like in the background is opened a window, which I could't see, because all is clear.
As I started then these processes like APTus und the Sparky-First-Run from the LXTerminal, I have seen what would have had to happen.
Yes, I think also that a new installation, would be the best. But which one should I take? I think perhaps it is problematically, because I used the 64-bit version? -A test before offered that my i5-CPU could do it... ...but mayby not? Or another component in my Computer doesn't like 64bit and then the Sparky is crashing?
Likely I would have to try both to be sure... :'(
ok, now I have made a new installation of Sparky-64-bit version and...
...all is ok! ;D
Now I know what was wrong:
Pavroo supposed the mistake at the correct place: It was a Problem with the passwords.
At my first installation the Sparky-installer asked me for a password for the admin; (It must have been so, because I noted it on a paper...) When I have started now APTus or another system -tool, the system asked for the admin-password; And I typed it in and nothing is happened...
By the three installations which I have done afterwards, were no demands for a admin-password. -And so I gave the system my user-password (in those dialogs, where the system needs the admin-password) and all is going fine.
The question is now, should I change this and create a seperatly password for the admin?
Well Goofy... sometimes... ;D
About the password, do as what fits your personal situation. :)
Type "man passwd" Read. Act accordingly. Peace out.