PDA

View Full Version : ...I'm scared


NCLI
September 22nd, 2010, 05:50 PM
What does this mean? :shock:

laila@laila-desktop:~$ gksudo update-manager -d
No ask_pass set, using default!
xauth: /tmp/libgksu-VLRX84/.Xauthority
STARTUP_ID: gksudo/update-manager/7420-0-laila-desktop_TIME2519756
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]: update-manager
buffer: -GNOME_SUDO_PASS-
brute force GNOME_SUDO_PASS ended...
Yeah, we're in...

EDIT: Ok, it seems like the "-d" activated gksudo's debug mode, instead of asking Update Manager to look for development releases. This works:

gksudo "update-manager -d"
Weird.
Tibuda
September 22nd, 2010, 05:54 PM
:shock:

they're in!
NCLI
September 22nd, 2010, 05:55 PM
:shock:

they're in!

Who, Frodo and Sam??
NCLI
September 22nd, 2010, 05:58 PM
Ok, it seems like the "-d" activated gksudo's debug mode, instead of asking Update Manager to look for development releases. This works:

gksudo "update-manager -d"
Weird.
Tibuda
September 22nd, 2010, 06:01 PM
So that's debug info? I'm scared off "brute force" and "we're in" too..
NCLI
September 22nd, 2010, 06:05 PM
So that's debug info? I'm scared off "brute force" and "we're in" too..

And that's why I posted before thinking. Freaky!
whiskeylover
September 22nd, 2010, 06:06 PM
You can just do a "update-manager -d" without the gksudo. It'll ask for your password when you hit the install/upgrade button.
tgm4883
September 22nd, 2010, 06:18 PM
what is the output of


which update-manager
NCLI
September 22nd, 2010, 06:20 PM
You can just do a "update-manager -d" without the gksudo. It'll ask for your password when you hit the install/upgrade button.

It's just a habit. Still, this could have happened with any other application.

what is the output of


which update-manager

laila@laila-desktop:~$ which update-manager
/usr/bin/update-manager
CharlesA
September 22nd, 2010, 06:28 PM
Just tried it on a brand new install and it did the same thing. Debug mode can be.. interesting.. sometimes..

I tried it with gedit and it did the same thing. O_o
Calash
September 22nd, 2010, 06:43 PM
For kicks I just tried the following



gksu -d


and found something I did not know about. It can let you run any command as any user. Very neat feature IMHO.
FuturePilot
September 22nd, 2010, 06:45 PM
You don't need to launch update-manager -d with gksudo. It will elevate privileges at the appropriate time.
Tibuda
September 22nd, 2010, 08:25 PM
You don't need to launch update-manager -d with gksudo. It will elevate privileges at the appropriate time.

but the thread is not really about update-manager, but about gksudo debugging messages.
NCLI
September 22nd, 2010, 08:49 PM
You don't need to launch update-manager -d with gksudo. It will elevate privileges at the appropriate time.

It's just a habit. Still, this could have happened with any other application.


but the thread is not really about update-manager, but about gksudo debugging messages.
Exactly.
kmsalex
September 23rd, 2010, 05:00 AM
slightly diffrent last line here.


alex@alex-laptop:~$ gksudo gedit
alex@alex-laptop:~$ gksudo gedit -d
No ask_pass set, using default!
xauth: /tmp/libgksu-GCEwAy/.Xauthority
STARTUP_ID: gksudo/gedit/12700-0-alex-laptop_TIME15429662
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]: gedit
buffer: -/root/.gtkrc-2.0:8: Unable to find include file: ".themes/nautilus/nautilus.rc"-
brute force GNOME_SUDO_PASS ended...
No password prompt found; we'll assume we don't need a password.
/root/.gtkrc-2.0:8: Unable to find include file: ".themes/nautilus/nautilus.rc"
Khakilang
September 23rd, 2010, 05:49 AM
If you're Luke Skywalker, you don't have to use brute force. The force is always be with you.