Bug 228268 - Can't log with rootpassword yast login, rootshell login, dolphin login
Summary: Can't log with rootpassword yast login, rootshell login, dolphin login
Status: RESOLVED FIXED
Alias: None
Product: kde
Classification: I don't know
Component: general (show other bugs)
Version: unspecified
Platform: openSUSE Other
: NOR normal
Target Milestone: ---
Assignee: Unassigned bugs mailing-list
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2010-02-24 06:07 UTC by wasserschneemaennchen
Modified: 2019-07-30 20:47 UTC (History)
3 users (show)

See Also:
Latest Commit:
Version Fixed In:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description wasserschneemaennchen 2010-02-24 06:07:18 UTC
Version:            (using KDE 4.3.1)
OS:                Other
Installed from:    openSUSE RPMs

Hi I have an Aspire 5810T(imeline) Laptop running Opensuse 11.2 with Intel Core Solo CPU U3500 at 1.40 Ghz, 800Mhz FSB, notebook laptop  x 86_64
with 4Go DDR3 RAM
Graphicchip: Intel GMA 4500 MHD
Free Swap at 4 Go
320 Go 2,5 inch harddisk
Wireless ACER Nplify TM 802.11 a/b/g/Draft-N,  !!! Under YAST2  in Network Peripherial clicking on network parameters I have the wireless device not configured, I wanted to have this so...

Software:
In Use KDE 4.3.1 release 6
Gnome Xfce desktop environnements have been installed
During Installation of opensuse 11.2 all package groups have been installed, excepted remote desktop, all the servers, webdeveloppment, Virtual Machine, have not been installed.
In addition have been installed: kinternet, smpppd, zenmap, nmap, wireshark, sniffing tools under descriptive: ? snif ? .

Most packages under following descriptives have been removed on Yast2 (=Those who did not generate more than 5 dependency problems by removing):
game, remote, telefone, ekiga, choqok, konversation, kopete, pidgin, xchat, irc, bluetooth, ftp, kmail, evolution, liferea,akregator,ktorrent, torrent, epiphany, knode, krfb, krdc, mysql, postgre, multisync, sync, hsqldb, server.
I'm more than sure the problem isn't hidden here because I systematically do this to all my computers, all dependencies are OK, and always all works well.

Update:
All updates have been done up to the 24 february 2010 at ~ 22h00 Bern Geneva Zurich Swiss Time
Language: German 
Keyboard: French Switzerland



The 24 february 2010 at 22h15 I click on the root shell which is offered into the plasmoids (mini programs) there are two choices rootshell and shell, I choose rootshell, the window with this shell appears, but when I insert my password and make ? enter ?, nothing happens, there is no #, simply nothing appears the window remains. 
I close the root shell window and retry to open it after several 2 min intervals each time it does not open when I click rootshell in the shells little window upon my taskbar.
I close the root shell window and retry to open it after a 5  minutes intervall it does not open when I click on rootshell.
The same after a 14 min intervall the rootshell window doesn't appear nothing happens.
The same after a 20 min intervall the rootshell window doesn't appear nothing happens.
Finally I gave up this and tried starting yast.

When I try to open the graphical interface (on runlevel 5) Yast2 after typing the password when I click. After the password has been typed in the yast login window as my password circular spots appear, after this I klick on OK, the login window freezes, the black spot line remains containing the password and the ok button even doesn't let push himself by the click of the mouse.

I decide to click several times on the cross button of this window to close it:
Warning Kwin appears which in it is written traduced in english from german:
? The window execute as root doesn't react. It belongs to programm kdesu (PID: 8301, computer: localhost).
Do you want to close this programm inclusively all of Kindprocesses. In this case all unsaved data in it will be lost ?
This little warning window permits to end kdesu or to abbort. I choose ending kdesu. The window disappears.

I repeat this logging prcedure, same little login-window freezes, this time I notice that when I drive in this frozen yast login window with the mouse cursor, the mouse cursor disappears as it gets in the area (surface) of this window, despite it is wll possible to click on the little cross button on the top at the right to closethis window.
I must click about a 40 times  until
 the same Kwin warning window reappears, this time kdesu with PID number 8358.

However I manage well to close all windows on my laptop.


I decide to reboot: Click on start button, then on ? leave ? or quit then click on reboot, it's even possible to introduce the reboot-root-password: I introduce password an make OK.

A black screen appears with written in it on the top on the left:

INIT: Switching to runlevel: 6
INIT: Sending processes the TERM signal
INIT: Sending processes the KILL signal
INIT: Pid 4150 [id 2] seems to hang
INIT: Pid 4152 [id 3] seems to hang
INIT: Pid 4154 [id 4] seems to hang
INIT: Pid 4156 [id 5] seems to hang
INIT: Pid 4158 [id 6] seems to hang
_

The note book does not reboot
The screen remains frozen.
I switch off by pushing power button of notebook on off.


I restart the notebook, on the bootlogging screen I get the fast impression thant all is in green OK
My user password is asked for loging into the graphical computer interface. I manage to log very well.

As first the Konsole window from the unfructuous rootkonsole logging appears, despite, the window has just the menues but there is not written ? password :? .
I close this console window by clicking on little cross button on top on the right of this window:

Instantaneously appears the debugger with the cute red little beetle.
Details: Executable Folder: konsole PID 5316 Signal: 11 (Segmentation fault)

I go to tab developper informations, please see what's written in the bug's log, please contact me at
wasserschneemaennchen@yahoo.fr and and indicate me your e-mail adress so that I can send you the log photography.

Apparently 3 or 4 hours later when docking an USBmemostickharddrive dolphin asks me rootpassword, I manage very well to log with rootpassword and navigate the folders of my memo stick.
So I get the idea to retry to log su onto my rootshell, to see what happens: It still doesn't work at 4 o clock in the morning.

Date to which I'm sending to you this bug
After 4h44
Retryed to dock usb dongle this time dolphin login with rootpassword also doesn't work.

My contact e-mail is:

wasserschneemaennchen@yahoo.fr



see:log:
Application: Konsole (kdeinit4), signal: Segmentation fault
[KCrash Handler]
#5 0x00007f6d87eaf710 in ?? () from /usr/lib64/libkonsoleprivate.so
#6 0x00007f6d87eb4e89 in Konsole::ViewManager::viewProperties() const () from /usr/lib64/libkonsoleprivate.so
#7 0x00007f6d880ffcb1 in QKeySequence::~QKeySequence() () from /usr/lib64/libkdeinit4_konsole.so
#8 0x00007f6d91717281 in KMainWindow::closeEvent(QCloseEvent*) () from /usr/lib64/libkdeui.so.5
#9 0x00007f6d90a9a678 in QWidget::event(QEvent*) () from /usr/lib64/libQtGui.so.4
#10 0x00007f6d90df40bb in QMainWindow::event(QEvent*) () from /usr/lib64/libQtGui.so.4
#11 0x00007f6d91751d83 in KXmlGuiWindow::event(QEvent*) () from /usr/lib64/libkdeui.so.5
#12 0x00007f6d90a4c2ac in QApplicationPrivate::notify_helper(QObject*, QEvent*) () from /usr/lib64/libQtGui.so.4
#13 0x00007f6d90a5357e in QApplication::notify(QObject*, QEvent*) () from /usr/lib64/libQtGui.so.4
#14 0x00007f6d916468d6 in KApplication::notify(QObject*, QEvent*) () from /usr/lib64/libkdeui.so.5
#15 0x00007f6d92c5bddc in QCoreApplication::notifyInternal(QObject*, QEvent*) () from /usr/lib64/libQtCore.so.4
#16 0x00007f6d90a9fa51 in QWidgetPrivate::close_helper(QWidgetPrivate::CloseMode) () from /usr/lib64/libQtGui.so.4
#17 0x00007f6d90aa6ee6 in QApplication::x11ClientMessage(QWidget*, _XEvent*, bool) () from /usr/lib64/libQtGui.so.4
#18 0x00007f6d90ab7864 in QApplication::x11ProcessEvent(_XEvent*) () from /usr/lib64/libQtGui.so.4
#19 0x00007f6d90adfb6c in ?? () from /usr/lib64/libQtGui.so.4
#20 0x00007f6d8f995dee in g_main_context_dispatch () from /usr/lib64/libglib-2.0.so.0
#21 0x00007f6d8f9997b8 in ?? () from /usr/lib64/libglib-2.0.so.0
#22 0x00007f6d8f9998e0 in g_main_context_iteration () from /usr/lib64/libglib-2.0.so.0
#23 0x00007f6d92c843a3 in QEventDispatcherGlib::processEvents(QFlags<QEventLoop::ProcessEventsFlag>) () from /usr/lib64/libQtCore.so.4
#24 0x00007f6d90adf31e in ?? () from /usr/lib64/libQtGui.so.4
#25 0x00007f6d92c5a712 in QEventLoop::processEvents(QFlags<QEventLoop::ProcessEventsFlag>) () from /usr/lib64/libQtCore.so.4
#26 0x00007f6d92c5aae4 in QEventLoop::exec(QFlags<QEventLoop::ProcessEventsFlag>) () from /usr/lib64/libQtCore.so.4
#27 0x00007f6d92c5cc99 in QCoreApplication::exec() () from /usr/lib64/libQtCore.so.4
#28 0x00007f6d88102263 in kdemain () from /usr/lib64/libkdeinit4_konsole.so
#29 0x0000000000406f88 in _start ()
Comment 1 Christoph Feck 2010-02-26 00:37:51 UTC
Thanks for the detailed bug report.

For future reports, please keep the amount of information about your system minimal; it is confusing to read. If information is missing, the developers will request those from you.

Also, please do not report multiple problems in a single bug report. Often bugs are not related, and managing them is easier if there is one report per bug.

From what I understand, you get hanging dialog windows when trying to enter passwords. Could you check in System Settings > Personal > About Me > Password & User Account if your Password Prompt is set to "three bullets" ("Drei Sterne" in German translation)? If yes, please change that to "Show one bullet for each letter". This bug is fixed for KDE SC 4.4.0.

In case root login does not work because you have forgotten your root password, there are steps available on the Internet to reset the root password. Ask in openSUSE forums if that is the case.

The backtrace that you attached was reported already as bug 211668.
Comment 2 Samuel Brack 2011-01-05 15:05:11 UTC
wasserschneemann, is it possible for you to check the validity of your bug with the method described in comment 1 again? This seems to be fixed and if nobody can reproduce the behaviour, this bug can be closed, I think.
Comment 3 wasserschneemaennchen 2011-01-10 04:03:12 UTC
Yes, concerning my side this bug can be closed since it is from last year and has allready been fixed in KDE 4.4.4.

Thank's a lot for your kindful help :-)
!
Comment 4 Samuel Brack 2011-01-10 14:31:00 UTC
Finally closed.