After a automatic update when I reboot I still get the login screen but now the passwords will not work not even root so I cant login in
I am using Opensuse 12.1
Thanks
What do you mean by “Automatic update”? What do you use for such an update?
And as you say this was Automatic, I better do not ask what was updated I am afraid.
BTW do you use KDE? Then I hope you followed the advice that is givem many times here to deinstall Apper.
Hit Ctrl-F1 in the login screen, try to login with username and password, and report if that is working. Hit Ctrl-D to logout, Ctrl-F7 to return to the login screen.
I’m experiencing problems too after kernel (and other) update(s).
After hitting enter on the login screen this error is shown:
Could not start ksmserver. Check your installation.
/var/log/messages reports:
Jun 23 19:49:18 vaio-z kernel: 48.530441] ksmserver[1750]: segfault at 2c280 ip 000000000002c280 sp 00007fff3e643778 error 14 in kdeinit4[400000+c000]
Jun 23 19:49:19 vaio-z kernel: 48.638673] kded4[1745]: segfault at 2c280 ip 000000000002c280 sp 00007fff3e641d58 error 14 in kdeinit4[400000+c000]
Jun 23 19:49:27 vaio-z login[1518]: pam_apparmor(login:session): Unknown error occurred changing to root hat: Operation not permitted
.xsession_errors also provides some details
/etc/X11/xim: Checking whether an input method should be started.
sourcing /etc/sysconfig/language to get the value of INPUT_METHOD
INPUT_METHOD is not set or empty (no user selected input method).
Trying to start a default input method for the locale en_US.UTF-8 …
There is no default input method for the current locale.
Dummy input method “none” (do not use any fancy input method by default)
startkde: Starting up…
Connecting to deprecated signal QDBusConnectionInterface::serviceOwnerChanged(QString,QString,QString)
QDBusConnection: session D-Bus connection created before QCoreApplication. Application may misbehave.
QDBusConnection: session D-Bus connection created before QCoreApplication. Application may misbehave.
kbuildsycoca4 running…
KCrash: Attempting to start /usr/bin/kded4 from kdeinit
kded(1740): Communication problem with “kded” , it probably crashed.
Error message was: “org.freedesktop.DBus.Error.NoReply” : " “Message did not receive a reply (timeout by message bus)” "
QDBusConnection: session D-Bus connection created before QCoreApplication. Application may misbehave.
QDBusConnection: session D-Bus connection created before QCoreApplication. Application may misbehave.
KCrash: Application ‘kded4’ crashing…
KCrash: Attempting to start /usr/lib64/kde4/libexec/drkonqi from kdeinit
kdeinit4: (ksmserver /usr/bin/ksmserver) Pipe closed unexpectedlykdeinit4: Pipe closed unexpectedly: Resource temporarily unavailable
KInit could not launch ‘ksmserver’.
startkde: Could not start ksmserver. Check your installation.
kbuildsycoca4 running…
kded(1744): Communication problem with “kded” , it probably crashed.
Error message was: “org.freedesktop.DBus.Error.NoReply” : " “Message did not receive a reply (timeout by message bus)” "
I’ve tried reverting to kernel 3.1.9 but the errors remain. LXDE is operational, but I’d like to get back to KDE. Googling the ksmserver error shows a lot of hits, but I’m unsure about relevance.
On 2012-06-23 20:46, jdaandels wrote:
>
> I’m experiencing problems too after kernel (and other) update(s).
>
> After hitting enter on the login screen this error is shown:
>
> Could not start ksmserver. Check your installation.
According to Will Stephenson, a SUSE dev, «“ksmserver wont start” is a
classic symptom of mismatched KDE/Qt libraries and hence messed up repo
priorities.»
–
Cheers / Saludos,
Carlos E. R.
(from 11.4 x86_64 “Celadon” at Telcontar)
Here’s a list of my repo’s. All were at prio 99, but just changed KDE to 98 and ran zypper dup which updated some packages. NetworkManager branding and some other packages were updated.After a system reboot the error remains
| Alias | Name | Enabled | Refresh | Priority | Type | URI | Service
–±------------------------±----------------------±--------±--------±---------±-------±--------------------------------------------------------------------------------±-------
1 | KDE | openSUSE - KDE | Yes | Yes | 98 | rpm-md | Index of /repositories/KDE:/Release:/48/openSUSE_12.1 |
2 | Packman_1 | openSUSE - Packman | Yes | Yes | 99 | rpm-md | Index of /suse/openSUSE_Tumbleweed/Essentials/ |
3 | bumblebee | bumblebee | Yes | Yes | 99 | rpm-md | Index of /repositories/home:/tuoma:/Bumblebee/openSUSE_12.1 |
4 | openSUSE_-_VirtualBox | openSUSE - VirtualBox | Yes | Yes | 99 | rpm-md | Index of /virtualbox/rpm/opensuse/11.4/ |
5 | openSUSE_11.3_Non-Oss_1 | openSUSE - non OSS | Yes | Yes | 99 | yast2 | Index of /distribution/openSUSE-current/repo/non-oss |
6 | openSUSE_11.3_Oss_1 | openSUSE - OSS | Yes | Yes | 99 | yast2 | Index of /distribution/openSUSE-current/repo/oss |
7 | openSUSE_11.3_Updates | openSUSE - Updates | Yes | Yes | 99 | rpm-md | Index of /update/openSUSE-current |
Soad2, could you please confirm you have simular error messages. I would not like having hyjacked your topic…
Please jdaandels, use CODE tags around your copied/pasted computer text: http://forums.opensuse.org/english/information-new-users/advanced-how-faq-read-only/451526-posting-code-tags-guide.html
On 2012-06-23 22:26, hcvv wrote:
>
> Please jdaandels, use CODE tags around your copied/pasted computer text:
> http://tinyurl.com/2wwx7l9
Yes, please, repeat the post. I can not analyze that list of repos as it is.
–
Cheers / Saludos,
Carlos E. R.
(from 11.4 x86_64 “Celadon” at Telcontar)
Not sure if it matters but why is the VB repo from 11.4??? And packman is for Tumbleweed??? That is bound to pull in out of version stuff.
I’ve been experiencing the same problem after I installed the latest set of updates from the Tumbleweed repository. The error message was
Could not start ksmserver. Check your installation.
From the Developer Information in the KDE Crash Handler, I realized that the problem is somehow related to the libQtWebKit4 library. So I decided to downgrade libQtWebKit4 from version 4.8.2+2.2.0-4.4 in the Tumbleweed repository to version 4.7.7+2.2.0-2.1.2 from the openSUSE-Current-Oss repository, leaving everything else unchanged. After this change, I was able to log in. There were, however, some problems (Kopete and Skype would freeze) but the system generally seemed usable. This all led me to believe that there must be some inconsistency with the Qt packages so I decided to add the following repository “Current Qt 4.x packages (openSUSE_12.1)” (Index of /repositories/KDE:/Qt/openSUSE_12.1) and get all of my Qt packages from there. After getting Qt packages from this repository, I was again able to log in just fine.
So somehow Tumbleweed repository brought in an inconsistent set of Qt packages. However, I’m not sure if all systems are affected (my laptop is Dell Inspiron with Intel graphics).
Here’s the formatted list of repos
vaio-z:~ # zypper lr -d
# | Alias | Name | Enabled | Refresh | Priority | Type | URI | Service
--+-------------------------+-----------------------+---------+---------+----------+--------+---------------------------------------------------------------------------------+--------
1 | KDE | openSUSE - KDE | Yes | Yes | 98 | rpm-md | http://download.opensuse.org/repositories/KDE:/Release:/48/openSUSE_12.1/ |
2 | Packman_1 | openSUSE - Packman | Yes | Yes | 99 | rpm-md | http://packman.inode.at/suse/openSUSE_Tumbleweed/Essentials/ |
3 | bumblebee | bumblebee | Yes | Yes | 99 | rpm-md | http://download.opensuse.org/repositories/home:/tuoma:/Bumblebee/openSUSE_12.1/ |
4 | openSUSE_-_VirtualBox | openSUSE - VirtualBox | Yes | Yes | 99 | rpm-md | http://download.virtualbox.org/virtualbox/rpm/opensuse/11.4 |
5 | openSUSE_11.3_Non-Oss_1 | openSUSE - non OSS | Yes | Yes | 99 | yast2 | http://download.opensuse.org/distribution/openSUSE-current/repo/non-oss/ |
6 | openSUSE_11.3_Oss_1 | openSUSE - OSS | Yes | Yes | 99 | yast2 | http://download.opensuse.org/distribution/openSUSE-current/repo/oss/ |
7 | openSUSE_11.3_Updates | openSUSE - Updates | Yes | Yes | 99 | rpm-md | http://download.opensuse.org/update/openSUSE-current/ |
Please note the 11.3 is from openSUSE-current and is actually 12.1…
I’ll have a look at the crash info to see if contains libQtWebKit and will follow up with the suggestions regarding libQt libraries and repos
I have had a look at the developer information, but the error does not seem to originate from libQtWebKit, but libQtOpenGL instead:
Application: KDE Daemon (kdeinit4), signal: Segmentation fault
[KCrash Handler]
#6 0x000000000002c280 in ?? ()
#7 0x00007f862410d936 in ?? () from /usr/lib64/libQtOpenGL.so.4
#8 0x00007f8618588456 in ?? () from /usr/lib64/kde4/kded_powerdevil.so
#9 0x0000000000000004 in ?? ()
#10 0x00007fff872d3698 in ?? ()
#11 0x00007f8624087aa3 in _init () from /usr/lib64/libQtOpenGL.so.4
#12 0x0000000000677ed0 in ?? ()
#13 0x00007f8632832dc4 in call_init () from /lib64/ld-linux-x86-64.so.2
#14 0x00007f8632832ef6 in _dl_init_internal () from /lib64/ld-linux-x86-64.so.2
#15 0x00007f8632836f43 in dl_open_worker () from /lib64/ld-linux-x86-64.so.2
#16 0x00007f8632832c36 in _dl_catch_error () from /lib64/ld-linux-x86-64.so.2
#17 0x00007f86328367ca in _dl_open () from /lib64/ld-linux-x86-64.so.2
#18 0x00007f862dcd7f26 in dlopen_doit () from /lib64/libdl.so.2
#19 0x00007f8632832c36 in _dl_catch_error () from /lib64/ld-linux-x86-64.so.2
#20 0x00007f862dcd84cf in _dlerror_run () from /lib64/libdl.so.2
#21 0x00007f862dcd7fc1 in dlopen@@GLIBC_2.2.5 () from /lib64/libdl.so.2
#22 0x00007f863161cc3b in ?? () from /usr/lib64/libQtCore.so.4
#23 0x00007f863161962a in ?? () from /usr/lib64/libQtCore.so.4
#24 0x00007f8631619913 in ?? () from /usr/lib64/libQtCore.so.4
#25 0x00007f8631bac618 in KPluginLoader::load() () from /usr/lib64/libkdecore.so.5
#26 0x00007f8631bac8e9 in KPluginLoader::factory() () from /usr/lib64/libkdecore.so.5
#27 0x00007f861d9d3ad0 in ?? () from /usr/lib64/libkdeinit4_kded4.so
#28 0x00007f861d9d4d87 in ?? () from /usr/lib64/libkdeinit4_kded4.so
#29 0x00007f861d9d6aa1 in ?? () from /usr/lib64/libkdeinit4_kded4.so
#30 0x00007f86323f6f02 in ?? () from /usr/lib64/libkdeui.so.5
#31 0x00007f86323f6f84 in ?? () from /usr/lib64/libkdeui.so.5
#32 0x00007f86323f70cb in ?? () from /usr/lib64/libkdeui.so.5
#33 0x00007f862e373f6b in ?? () from /usr/lib64/libQtDBus.so.4
#34 0x00007f862e37507d in ?? () from /usr/lib64/libQtDBus.so.4
#35 0x00007f862e375a9b in ?? () from /usr/lib64/libQtDBus.so.4
#36 0x00007f862e375b8b in ?? () from /usr/lib64/libQtDBus.so.4
#37 0x00007f8631643e06 in QObject::event(QEvent*) () from /usr/lib64/libQtCore.so.4
#38 0x00007f8630794e34 in QApplication::event(QEvent*) () from /usr/lib64/libQtGui.so.4
#39 0x00007f8630790fe4 in QApplicationPrivate::notify_helper(QObject*, QEvent*) () from /usr/lib64/libQtGui.so.4
#40 0x00007f8630795db3 in QApplication::notify(QObject*, QEvent*) () from /usr/lib64/libQtGui.so.4
#41 0x00007f86323f1746 in KApplication::notify(QObject*, QEvent*) () from /usr/lib64/libkdeui.so.5
#42 0x00007f863162ad0c in QCoreApplication::notifyInternal(QObject*, QEvent*) () from /usr/lib64/libQtCore.so.4
#43 0x00007f863162e5ba in QCoreApplicationPrivate::sendPostedEvents(QObject*, int, QThreadData*) () from /usr/lib64/libQtCore.so.4
#44 0x00007f86316599a3 in ?? () from /usr/lib64/libQtCore.so.4
#45 0x00007f862cbad58d in g_main_context_dispatch () from /usr/lib64/libglib-2.0.so.0
#46 0x00007f862cbadd88 in ?? () from /usr/lib64/libglib-2.0.so.0
#47 0x00007f862cbadf59 in g_main_context_iteration () from /usr/lib64/libglib-2.0.so.0
#48 0x00007f8631659dcf in QEventDispatcherGlib::processEvents(QFlags<QEventLoop::ProcessEventsFlag>) () from /usr/lib64/libQtCore.so.4
#49 0x00007f863083469e in ?? () from /usr/lib64/libQtGui.so.4
#50 0x00007f8631629842 in QEventLoop::processEvents(QFlags<QEventLoop::ProcessEventsFlag>) () from /usr/lib64/libQtCore.so.4
#51 0x00007f8631629a97 in QEventLoop::exec(QFlags<QEventLoop::ProcessEventsFlag>) () from /usr/lib64/libQtCore.so.4
#52 0x00007f863162e8b5 in QCoreApplication::exec() () from /usr/lib64/libQtCore.so.4
#53 0x00007f861d9d3495 in kdemain () from /usr/lib64/libkdeinit4_kded4.so
#54 0x00000000004088e4 in _start ()
since libQtOpenGL is from Qt as well (libqt4-x11) I’ve updated my repositories anyway to include the suggested Qt repo and ran a zypper dup. This did not update any rpm, so I manually pulled in the files from the KDE Qt repo. After a reboot I’ve attempted to login back to KDE again, but the same error is still there…
this is my new repo config:
# | Alias | Name | Enabled | Refresh | Priority | Type | URI
--+-------------------------+-----------------------+---------+---------+----------+--------+--------------------------------------------------------------------------------
4 | openSUSE_-_Qt | openSUSE - Qt | Yes | Yes | 70 | rpm-md | http://download.opensuse.org/repositories/KDE:/Qt/openSUSE_12.1/
1 | KDE | openSUSE - KDE | Yes | Yes | 80 | rpm-md | http://download.opensuse.org/repositories/KDE:/Release:/48/openSUSE_12.1/
2 | Packman_1 | openSUSE - Packman | Yes | Yes | 99 | rpm-md | http://packman.inode.at/suse/openSUSE_Tumbleweed/Essentials/
5 | openSUSE_-_VirtualBox | openSUSE - VirtualBox | Yes | Yes | 99 | rpm-md | http://download.virtualbox.org/virtualbox/rpm/opensuse/11.4
6 | openSUSE_11.3_Non-Oss_1 | openSUSE - Non-OSS | Yes | Yes | 99 | yast2 | http://download.opensuse.org/distribution/openSUSE-current/repo/non-oss/
7 | openSUSE_11.3_Oss_1 | openSUSE - OSS | Yes | Yes | 99 | yast2 | http://download.opensuse.org/distribution/openSUSE-current/repo/oss/
8 | openSUSE_11.3_Updates | openSUSE - Updates | Yes | Yes | 99 | rpm-md | http://download.opensuse.org/update/openSUSE-current/
3 | bumblebee | bumblebee | Yes | Yes | 100 | rpm-md | http://download.opensuse.org/repositories/home:/tuoma:/Bumblebee/openSUSE_12.1/
By the way, I’m not using Tumbleweed repo (i.m.h.o. it updates kernel too often, which requires a “very hard” reinstall of nvidia drivers). Laptop is a Sony Vaio with nvidia and intel graphics. I use intel by default and bumblebee 3.0 bbswitch turn the nvidia off by default and on when running programs with optirun…
Gentleman,
As a mod I would like to bring the following to your attention.
The OP in this thread is Soad2. It now looks like jdaandels has hyjacked this thread.
I admit that Soad2 did not answer to any suggestions made earlier, but IMHO it is still his thread and thus answers, solutions, suggestions here are to be made to him in the first place.
Even if jdaandels has also a problem in the same area (GUI login) it is by no means certain that it is the same problem (my idea is that it is pretty sure it isn’t). Thus the present thread became a bit of a mess.
Any suggestions how to disentangle this. And Soad2, are you still there?
On 2012-06-24 11:46, jdaandels wrote:
>
> Here’s the formatted list of repos
And as I said, you have an incompatible mixture there. You are attempting
to use Tumbleweed, but have repos for 12.1 and for 11.4. Change all to
tumbleweed except those for current.
Any further posts about this must be in the tumbleweed repo, not here.
If you do not intend to use tumbleweed, then remove all tumbleweed repos
and replace with 12.1 ones (not current), then do a dup to restore
conditions (it may fail).
–
Cheers / Saludos,
Carlos E. R.
(from 11.4 x86_64 “Celadon” at Telcontar)
hvcc,
I agree the chances are very slim Soad2 is having the same problem, though his initial symptoms matched mine. Could you split off my posts in a separate topic so the original topic is clean again? I apologize for the inconveince.
robin_listas,
I’ve adjusted the current repos back to 12.1. I was under the impression current repos only pointed to the most recent release (12.1) and I need a add a special repo to pull in Tumbleweed packages. When I decided to stop using Tumbleweed I apparently forgot to change the Packman back to openSUSE_12.1. The 11.4 repo is from virtualbox and since Oracle does not provide a separate repo for 12.1 and their websites states the same rpm should be used for 11.4 and 12.1 I double this repo causes any problems. I’ve also removed the Qt repo and changed all priorities back to 99
I’ve ran a zypper dup and accepted all changes, which were mostly downgrades from the packman Tumbleweed repo but also reinstallation of some other packages, including kdebase4-openSUSE and ksplashx packages. After these changes I’ve rebooted my system and was able to login back into the KDE workspace. I’m currently not sure which packages or repos exactly caused this problem since I’ve made to many changes at once, but probably the reinstall of some packages resolved my issue. If you’d like to dive into that I can provide my /var/log/zypp/history…