Thema: (Gelöst) Yast tut's nach Suse--Online-Update nicht mehr

Success! Hat aber geschlagene 4 Stunden gedauert. Hab es so gemacht, wie von dir vorgeschlagen, außer - ich habe die Server in den smart.channel-Dateien in /etc/smart in kedit von Hand geändert, GUI war mir zu lästig. Yast2 funktioniert wieder. Es gab aber während des Updates zwei Vorkommnisse:

Im Smart-Verlauf habe ich folgende Fehlermeldungen gefunden:

Code:

WARNING: /lib/modules/2.6.16.21-0.25-default/weak-updates/at76c505a-rfmd2958.ko needs unknown symbol at76c503_delete_device
WARNING: /lib/modules/2.6.16.21-0.25-default/weak-updates/at76c505a-rfmd2958.ko needs unknown symbol at76c503_do_probe
WARNING: /lib/modules/2.6.16.21-0.25-default/weak-updates/at76c505-rfmd.ko needs unknown symbol at76c503_delete_device
WARNING: /lib/modules/2.6.16.21-0.25-default/weak-updates/at76c505-rfmd.ko needs unknown symbol at76c503_do_probe
WARNING: /lib/modules/2.6.16.21-0.25-default/weak-updates/at76c503-rfmd.ko needs unknown symbol at76c503_delete_device
WARNING: /lib/modules/2.6.16.21-0.25-default/weak-updates/at76c503-rfmd.ko needs unknown symbol at76c503_do_probe
WARNING: /lib/modules/2.6.16.21-0.25-default/weak-updates/at76c505-rfmd2958.ko needs unknown symbol at76c503_delete_device
WARNING: /lib/modules/2.6.16.21-0.25-default/weak-updates/at76c505-rfmd2958.ko needs unknown symbol at76c503_do_probe
WARNING: /lib/modules/2.6.16.21-0.25-default/weak-updates/at76c503-i3863.ko needs unknown symbol at76c503_delete_device
WARNING: /lib/modules/2.6.16.21-0.25-default/weak-updates/at76c503-i3863.ko needs unknown symbol at76c503_do_probe
WARNING: /lib/modules/2.6.16.21-0.25-default/weak-updates/at76c503-i3861.ko needs unknown symbol at76c503_delete_device
WARNING: /lib/modules/2.6.16.21-0.25-default/weak-updates/at76c503-i3861.ko needs unknown symbol at76c503_do_probe
WARNING: /lib/modules/2.6.16.21-0.25-default/weak-updates/at76c503-rfmd-acc.ko needs unknown symbol at76c503_delete_device
WARNING: /lib/modules/2.6.16.21-0.25-default/weak-updates/at76c503-rfmd-acc.ko needs unknown symbol at76c503_do_probe

Außerdem leuchtete ein Popup mit dem KDE-Crashmanager auf, der meldete kdbuildsycoca sei abgestürzt. Als weitere Infos konnte man in der Rückverfolgung dann Folgendes lesen:

Code:

Überprüfung der Systemkonfiguration beim Start deaktiviert.

(no debugging symbols found)
Using host libthread_db library "/lib/libthread_db.so.1".
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
[Thread debugging using libthread_db enabled]
[New Thread -1230797136 (LWP 25730)]
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
[KCrash handler]
#6  0xffffe410 in __kernel_vsyscall ()
#7  0xb6fd27d0 in raise () from /lib/libc.so.6
#8  0xb6fd3ea3 in abort () from /lib/libc.so.6
#9  0xb7007f8b in __libc_message () from /lib/libc.so.6
#10 0xb700d911 in malloc_printerr () from /lib/libc.so.6
#11 0xb700ef84 in free () from /lib/libc.so.6
#12 0xb717be51 in operator delete () from /usr/lib/libstdc++.so.6
#13 0xb717bead in operator delete[] () from /usr/lib/libstdc++.so.6
#14 0xb77f653d in QChar::joining () from /usr/lib/qt3/lib/libqt-mt.so.3
#15 0xb7db0ad1 in KService::~KService () from /opt/kde3/lib/libkio.so.4
#16 0x08290df0 in ?? ()
#17 0x08291b50 in ?? ()
#18 0xb7db080b in KService::~KService () from /opt/kde3/lib/libkio.so.4
#19 0xb68199a8 in ?? () from /opt/kde3/lib/libkdeinit_kbuildsycoca.so
#20 0x08291b50 in ?? ()
#21 0x08292cb0 in ?? ()
#22 0xbfe8e528 in ?? ()
#23 0xb6815cb0 in QValueListPrivate<KSharedPtr<KSycocaEntry> >::clear ()
   from /opt/kde3/lib/libkdeinit_kbuildsycoca.so
#24 0xb6815cb0 in QValueListPrivate<KSharedPtr<KSycocaEntry> >::clear ()
   from /opt/kde3/lib/libkdeinit_kbuildsycoca.so
#25 0xb6815d18 in QValueList<KSharedPtr<KSycocaEntry> >::clear ()
   from /opt/kde3/lib/libkdeinit_kbuildsycoca.so
#26 0xb6802cfe in KBuildServiceGroupFactory::addEntry ()
   from /opt/kde3/lib/libkdeinit_kbuildsycoca.so
#27 0xb680e6d9 in KBuildServiceGroupFactory::addNew ()
   from /opt/kde3/lib/libkdeinit_kbuildsycoca.so
#28 0xb680efa4 in KBuildSycoca::createMenu ()
   from /opt/kde3/lib/libkdeinit_kbuildsycoca.so
#29 0xb680f0a6 in KBuildSycoca::createMenu ()
   from /opt/kde3/lib/libkdeinit_kbuildsycoca.so
#30 0xb6810093 in KBuildSycoca::build ()
   from /opt/kde3/lib/libkdeinit_kbuildsycoca.so
#31 0xb68121f2 in KBuildSycoca::recreate ()
   from /opt/kde3/lib/libkdeinit_kbuildsycoca.so
#32 0xb6812b56 in kdemain () from /opt/kde3/lib/libkdeinit_kbuildsycoca.so
#33 0xb7f6e534 in kdeinitmain () from /opt/kde3/lib/kde3/kbuildsycoca.so
#34 0x0804e8bf in ?? ()
#35 0x00000002 in ?? ()
#36 0x08072430 in ?? ()
#37 0x00000001 in ?? ()
#38 0x00000000 in ?? ()

Soll ich das erst einmal ignorieren oder droht mir neues Unheil?

Ansonsten: Vielen vielen Dank an Rain_Maker!

Gruß

Benno

PS am 17.11.: Bislang läuft das System stabil und alles läuft wieder.

Die Meldungen sehen übler aus, als sie sind und es hat AFAIK mit dem "Minor-Update" von 2.6.6.21-0.13 auf 2.6.16.21-0.25 zu tun.

Es sind ja auch nur "Warnings" und keine Fehlermeldungen.

Ich hatte diese Meldungen damals auch und es gab keine Probleme.

Das mit dem Crashmanager war wahrscheinlich eine KDE-Applikation, die beim Update selbst erneuert wurde und dann bei einem Datenbankzugriff auf die erneuerte Datenbank einmalig abgeschmiert ist. Sollte nicht vorkommen, passiert aber ab und zu mal und ist in der Regel nur lästig aber nicht schlimm.

Greetz,

RM

==> Closed.