logging in as root in KDE4

[blackjack72]

When I log in with KDE4 instead of 3.5, I cannot log in as root (password not accepted) and, in 3.5, Adept will not install more KDE4 packages. Any Ideas?

This is the crash report when I try to install some package

I will try them one at a time to see if I can isolate the problem.

#6 0xffffe410 in __kernel_vsyscall ()
#7 0xb6587875 in raise () from /lib/tls/i686/cmov/libc.so.6
#8 0xb6589201 in abort () from /lib/tls/i686/cmov/libc.so.6
#9 0xb67936e0 in __gnu_cxx::__verbose_terminate_handler ()
from /usr/lib/libstdc++.so.6
#10 0xb6790f65 in ?? () from /usr/lib/libstdc++.so.6
#11 0xb6790fa2 in std::terminate () from /usr/lib/libstdc++.so.6
#12 0xb67910ca in __cxa_throw () from /usr/lib/libstdc++.so.6
#13 0x0807a106 in ?? ()
#14 0x0807afca in ?? ()
#15 0x0807c8b8 in ?? ()
#16 0x0807c975 in ?? ()
#17 0x0812a19d in ?? ()
#18 0x08071845 in ?? ()
#19 0xb6e0eadf in QWidget::event () from /usr/lib/libqt-mt.so.3
#20 0xb6ee4c5a in QMainWindow::event () from /usr/lib/libqt-mt.so.3
#21 0xb6d6eaf0 in QApplication::internalNotify () from /usr/lib/libqt-mt.so.3
#22 0xb6d714ba in QApplication::notify () from /usr/lib/libqt-mt.so.3
#23 0xb7534cd2 in KApplication::notify () from /usr/lib/libkdecore.so.4
#24 0xb6d01209 in QApplication::sendEvent () from /usr/lib/libqt-mt.so.3
#25 0xb6e11575 in QWidget::close () from /usr/lib/libqt-mt.so.3
#26 0xb6ced852 in QETWidget::translateCloseEvent ()
from /usr/lib/libqt-mt.so.3
#27 0xb6cf3313 in QApplication:11ClientMessage ()
from /usr/lib/libqt-mt.so.3
#28 0xb6cfe8f6 in QApplication:11ProcessEvent () from /usr/lib/libqt-mt.so.3
#29 0xb6d151a4 in QEventLoop:rocessEvents () from /usr/lib/libqt-mt.so.3
#30 0xb6d89140 in QEventLoop:rocessEvents () from /usr/lib/libqt-mt.so.3
#31 0xb6d70704 in QApplication:rocessEvents () from /usr/lib/libqt-mt.so.3
#32 0xb6d7072f in QApplication:rocessEvents () from /usr/lib/libqt-mt.so.3
#33 0x0807f64b in ?? ()
#34 0xb7dcbcfe in OpProgress::Progress ()
from /usr/lib/libapt-pkg-libc6.6-6.so.4.5
#35 0xb7de2a0b in pkgDepCache::Update ()
from /usr/lib/libapt-pkg-libc6.6-6.so.4.5
#36 0xb7de2df6 in pkgDepCache::Init ()
from /usr/lib/libapt-pkg-libc6.6-6.so.4.5
#37 0x0812b16f in ?? ()
#38 0x0812b426 in ?? ()
#39 0x0812b504 in ?? ()
#40 0x08072cb8 in ?? ()
#41 0x0807411e in ?? ()
#42 0xb6dd7893 in QObject::activate_signal () from /usr/lib/libqt-mt.so.3
#43 0xb6dd8338 in QObject::activate_signal () from /usr/lib/libqt-mt.so.3
#44 0xb77273d9 in KAction::activated () from /usr/lib/libkdeui.so.4
#45 0xb7769ca2 in KAction::slotActivated () from /usr/lib/libkdeui.so.4
#46 0xb7769c3c in KAction::slotButtonClicked () from /usr/lib/libkdeui.so.4
#47 0xb7867b66 in KAction::qt_invoke () from /usr/lib/libkdeui.so.4
#48 0xb6dd7893 in QObject::activate_signal () from /usr/lib/libqt-mt.so.3
#49 0xb775d3d0 in KToolBarButton::buttonClicked () from /usr/lib/libkdeui.so.4
#50 0xb775d6d6 in KToolBarButton::mouseReleaseEvent ()
from /usr/lib/libkdeui.so.4
#51 0xb6e0e681 in QWidget::event () from /usr/lib/libqt-mt.so.3
#52 0xb77d81c1 in KToolBarButton::event () from /usr/lib/libkdeui.so.4
#53 0xb6d6eaf0 in QApplication::internalNotify () from /usr/lib/libqt-mt.so.3
#54 0xb6d70cae in QApplication::notify () from /usr/lib/libqt-mt.so.3
#55 0xb7534cd2 in KApplication::notify () from /usr/lib/libkdecore.so.4
#56 0xb6d0127d in QApplication::sendSpontaneousEvent ()
from /usr/lib/libqt-mt.so.3
#57 0xb6cffee2 in QETWidget::translateMouseEvent ()
from /usr/lib/libqt-mt.so.3
#58 0xb6cfdfcc in QApplication:11ProcessEvent () from /usr/lib/libqt-mt.so.3
#59 0xb6d151a4 in QEventLoop:rocessEvents () from /usr/lib/libqt-mt.so.3
#60 0xb6d891ce in QEventLoop::enterLoop () from /usr/lib/libqt-mt.so.3
#61 0xb6d88fde in QEventLoop::exec () from /usr/lib/libqt-mt.so.3
#62 0xb6d70699 in QApplication::exec () from /usr/lib/libqt-mt.so.3
#63 0x0806f75e in ?? ()
#64 0xb6573050 in __libc_start_main () from /lib/tls/i686/cmov/libc.so.6
#65 0x0806f401 in ?? ()

[srikar]

Re: logging in as root in KDE4

are u unable to login as root with this command

sudo -i

[blackjack72]

Re: logging in as root in KDE4

yes, but when I sign in to adept I get the incorrect password message. Synaptic and Kpackage seem to work.

Also, what is the difference between "su" and "sudo". Somewhere else (and I can't remember where, sorry) I was able to change from one to the other. Adept wants to log me on as su and that is when I get the "incorrect password" message.

[sky]

Re: logging in as root in KDE4

Hi,

By default you can't use su in kubuntu (or any *ubuntu) because to use su, you need the password to be set. sudo is like su but usually only for one command (not with sudo -i), but you need to be in admin group to be able to use it.
More details here about sudo :
https://help.ubuntu.com/community/RootSudo

Hope it helps

[Fintan]

Re: logging in as root in KDE4

Ditto with sky.

Do you have kdesudo-kde4 installed?

[blackjack72]

Re: logging in as root in KDE4

Thanks,
That explains thing a bit, but my issue stemmed from the fact that whenever I wanted to use adept (and some other functions in KDE4) I got the message to log in as su. Maybe a better question is; where (how) do I set the su password. I've actually given up on KDE4 for the time being and switched over to Ubuntu for the time being as I just feel that KDE makes Kubuntu too unstable for a relative Newbie like me to play with.

Thanks again for the help!

[Fintan]

Re: logging in as root in KDE4

whenever I wanted to use adept (and some other functions in KDE4) I got the message to log in as su.

I have not seen that pop up with anything in kde3/4.
It asks for administrator privalages on my machine.

If you don't have kdesudo-kde / -kde4 installed you may get that message. But they schould be installed by default.

Maybe a better question is; where (how) do I set the su password.

With sudo your user password you gave at install is the "root" password.

Qoute from sky's link:

The benefits of leaving root logins disabled by default include the following:

*

The installer has to ask fewer questions.
*

Users don't have to remember an extra password (i.e. the root password), which they are likely to forget.
*

It avoids the "I can do anything" interactive login by default (e.g. the tendency by users to login as an "Administrator" user in Microsoft Windows systems), you will be prompted for a password before major changes can happen, which should make you think about the consequences of what you are doing.
*

Sudo adds a log entry of the command(s) run (In /var/log/auth.log). If you mess up, you can always go back and see what commands were run. It is also nice for auditing.
*

Every cracker trying to brute-force their way into your box will know it has an account named root and will try that first. What they don't know is what the usernames of your other users are. Since the root account password is locked, this attack becomes essentially meaningless, since there is no password to crack or guess in the first place.
*

Allows easy transfer for admin rights, in a short term or long term period, by adding and removing users from groups, while not compromising the root account.
*

sudo can be setup with a much more fine-grained security policy.
*

The authentication automatically expires after a short time (which can be set to as little as desired or 0); so if you walk away from the terminal after running commands as root using sudo, you will not be leaving a root terminal open indefinitely.

I've actually given up on KDE4 for the time being and switched over to Ubuntu for the time being as I just feel that KDE makes Kubuntu too unstable for a relative Newbie like me to play with.

KDE4 is in the first phase of release (about a month old) and is supposed to be played with
KDE3 is very solid and is supposed to be worked with

In ubuntu you are going to have the same sudo stuff.

Have a good look at sky's link and good luck/fun