Bug 287757 - kded4 crashes at every login to KDE after upgrade to openSUSE 12.1
Summary: kded4 crashes at every login to KDE after upgrade to openSUSE 12.1
Status: RESOLVED FIXED
Alias: None
Product: Network Management
Classification: Miscellaneous
Component: KDED Module (show other bugs)
Version: 0.7
Platform: openSUSE Linux
: NOR crash
Target Milestone: ---
Assignee: Unassigned bugs mailing-list
URL:
Keywords:
: 292668 (view as bug list)
Depends on:
Blocks:
 
Reported: 2011-11-28 14:44 UTC by Vadym Krevs
Modified: 2012-02-04 12:34 UTC (History)
2 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 Vadym Krevs 2011-11-28 14:44:56 UTC
Version:           4.7 (using KDE 4.7.3) 
OS:                Linux

I've just upgraded to 12.1 from 11.4 and kded4 crashes on each login with the
following stack trace:

Application: KDE Dæmon (kdeinit4), signal: Segmentation fault
82    T_PSEUDO (SYSCALL_SYMBOL, SYSCALL_NAME, SYSCALL_NARGS)
[KCrash Handler]
#6  0x00007f66da98c1d8 in
Solid::Control::NetworkManagerNm09Private::networkInterfaces (this=0x9b9720) at
/usr/src/debug/networkmanagement/solidcontrolfuture/libs/solid/control/networkmanager.cpp:113
#7  0x00007f66da98c631 in Solid::Control::NetworkManagerNm09::networkInterfaces
() at
/usr/src/debug/networkmanagement/solidcontrolfuture/libs/solid/control/networkmanager.cpp:120
#8  0x00007f66dae30c84 in ConnectionUsageMonitor::ConnectionUsageMonitor
(this=0x950990, connectionList=<optimized out>, activatableList=0x9b8760,
parent=<optimized out>) at
/usr/src/debug/networkmanagement/libs/service/connectionusagemonitor.cpp:55
#9  0x00007f66db28c57f in NetworkManagementService::NetworkManagementService
(this=0x9606c0, parent=<optimized out>) at
/usr/src/debug/networkmanagement/kded/service.cpp:93
#10 0x00007f66db28c8d7 in
KPluginFactory::createInstance<NetworkManagementService, QObject>
(parentWidget=<optimized out>, parent=<optimized out>, args=...) at
/usr/include/kpluginfactory.h:477
#11 0x00007f66f579a5f1 in KPluginFactory::create (this=0x9a5540,
iface=0x7f66f57ee980 "KDEDModule", parentWidget=0x0, parent=0x6f5520, args=...,
keyword=<optimized out>) at
/usr/src/debug/kdelibs-4.7.3/kdecore/util/kpluginfactory.cpp:203
#12 0x00007f66e2070a6d in create<KDEDModule> (args=..., parent=0x6f5520,
this=<optimized out>) at
/usr/src/debug/kdelibs-4.7.3/kdecore/util/kpluginfactory.h:507
#13 Kded::loadModule (this=0x6f5520, s=..., onDemand=<optimized out>) at
/usr/src/debug/kdelibs-4.7.3/kded/kded.cpp:409
#14 0x00007f66e2071cb7 in Kded::initModules (this=0x6f5520) at
/usr/src/debug/kdelibs-4.7.3/kded/kded.cpp:268
#15 0x00007f66e2073a21 in newInstance (this=<optimized out>) at
/usr/src/debug/kdelibs-4.7.3/kded/kded.cpp:846
#16 KDEDApplication::newInstance (this=<optimized out>) at
/usr/src/debug/kdelibs-4.7.3/kded/kded.cpp:803
#17 0x00007f66f5fda772 in KUniqueApplicationAdaptor::newInstance
(this=0x84c700, asn_id=<optimized out>, args=...) at
/usr/src/debug/kdelibs-4.7.3/kdeui/kernel/kuniqueapplication.cpp:442
#18 0x00007f66f5fda812 in KUniqueApplicationAdaptor::qt_metacall
(this=0x84c700, _c=QMetaObject::InvokeMetaMethod, _id=0, _a=0x7fff9e3db980) at
/usr/src/debug/kdelibs-4.7.3/build/kdeui/kuniqueapplication_p.moc:81
#19 0x00007f66f1ffe9fb in QDBusConnectionPrivate::deliverCall (this=0x6e3dc0,
object=0x84c700, msg=..., metaTypes=..., slotIdx=4) at qdbusintegrator.cpp:942
#20 0x00007f66f1fffb0d in QDBusConnectionPrivate::activateCall (this=0x6e3dc0,
object=0x84c700, flags=337, msg=...) at qdbusintegrator.cpp:845
#21 0x00007f66f20004a2 in QDBusConnectionPrivate::activateObject
(this=0x6e3dc0, node=..., msg=..., pathStartPos=<optimized out>) at
qdbusintegrator.cpp:1410
#22 0x00007f66f2000578 in QDBusActivateObjectEvent::placeMetaCall
(this=0x82c220) at qdbusintegrator.cpp:1524
#23 0x00007f66f525914a in QObject::event (this=0x7fff9e3dc6d0, e=<optimized
out>) at kernel/qobject.cpp:1226
#24 0x00007f66f43f8ab4 in QApplication::event (this=0x7fff9e3dc6d0, e=0x82c220)
at kernel/qapplication.cpp:2522
#25 0x00007f66f43f4be4 in notify_helper (e=0x82c220, receiver=0x7fff9e3dc6d0,
this=0x6f6b80) at kernel/qapplication.cpp:4481
#26 QApplicationPrivate::notify_helper (this=0x6f6b80, receiver=0x7fff9e3dc6d0,
e=0x82c220) at kernel/qapplication.cpp:4453
#27 0x00007f66f43f9a71 in QApplication::notify (this=0x7fff9e3dc6d0,
receiver=0x7fff9e3dc6d0, e=0x82c220) at kernel/qapplication.cpp:4360
#28 0x00007f66f5fd4e36 in KApplication::notify (this=0x7fff9e3dc6d0,
receiver=0x7fff9e3dc6d0, event=0x82c220) at
/usr/src/debug/kdelibs-4.7.3/kdeui/kernel/kapplication.cpp:311
#29 0x00007f66f524281c in QCoreApplication::notifyInternal
(this=0x7fff9e3dc6d0, receiver=0x7fff9e3dc6d0, event=0x82c220) at
kernel/qcoreapplication.cpp:787
#30 0x00007f66f5245bf8 in sendEvent (event=0x82c220, receiver=0x7fff9e3dc6d0)
at kernel/qcoreapplication.h:215
#31 QCoreApplicationPrivate::sendPostedEvents (receiver=0x0, event_type=0,
data=0x615f10) at kernel/qcoreapplication.cpp:1428
#32 0x00007f66f526d0b3 in sendPostedEvents () at kernel/qcoreapplication.h:220
#33 postEventSourceDispatch (s=<optimized out>) at
kernel/qeventdispatcher_glib.cpp:277
#34 0x00007f66f0a5158d in g_main_dispatch (context=0x6f8e10) at gmain.c:2425
#35 g_main_context_dispatch (context=0x6f8e10) at gmain.c:2995
#36 0x00007f66f0a51d88 in g_main_context_iterate (context=0x6f8e10,
block=<optimized out>, dispatch=1, self=<optimized out>) at gmain.c:3073
#37 0x00007f66f0a51f59 in g_main_context_iteration (context=0x6f8e10,
may_block=1) at gmain.c:3136
#38 0x00007f66f526d50f in QEventDispatcherGlib::processEvents (this=0x617440,
flags=<optimized out>) at kernel/qeventdispatcher_glib.cpp:422
#39 0x00007f66f4497f2e in QGuiEventDispatcherGlib::processEvents
(this=<optimized out>, flags=<optimized out>) at
kernel/qguieventdispatcher_glib.cpp:204
#40 0x00007f66f5241a22 in QEventLoop::processEvents (this=<optimized out>,
flags=...) at kernel/qeventloop.cpp:149
#41 0x00007f66f5241c1f in QEventLoop::exec (this=0x7fff9e3dc660, flags=...) at
kernel/qeventloop.cpp:201
#42 0x00007f66f5245de7 in QCoreApplication::exec () at
kernel/qcoreapplication.cpp:1064
#43 0x00007f66e20703c5 in kdemain (argc=1, argv=0x6d1380) at
/usr/src/debug/kdelibs-4.7.3/kded/kded.cpp:924
#44 0x0000000000408897 in launch (argc=1, _name=0x40b3b4 "kded4",
args=<optimized out>, cwd=0x0, envc=<optimized out>, envs=<optimized out>,
reset_env=false, tty=0x0, avoid_loops=false, startup_id_str=0x40b22e "0") at
/usr/src/debug/kdelibs-4.7.3/kinit/kinit.cpp:734
#45 0x0000000000405ec9 in main (argc=4, argv=0x7fff00000001,
envp=0x7fff9e3dd790) at /usr/src/debug/kdelibs-4.7.3/kinit/kinit.cpp:1849

rpm -q kdelibs4
kdelibs4-4.7.3-10.4.x86_64

Reproducible: Always

Steps to Reproduce:
Login to KDE


Expected Results:  
No crash.
Comment 1 Lamarque V. Souza 2011-11-28 23:43:54 UTC
What is the backend order in systemsettings -> Information Source -> NetworkManager. If NetworkManager 0.9 is not the first move it to the first position and try again.
Comment 2 Lamarque V. Souza 2011-11-28 23:44:21 UTC
Git commit 7ecd47e754790eda5a8f0a8fab15f1518dea193f by Lamarque V. Souza.
Committed on 29/11/2011 at 00:41.
Pushed by lvsouza into branch 'nm09'.

Do not use null backend pointer in warning message.

CCBUG: 287757

M  +1    -1    plasma_nm_version.h
M  +1    -1    solidcontrolfuture/libs/solid/control/networkmanager.cpp

http://commits.kde.org/networkmanagement/7ecd47e754790eda5a8f0a8fab15f1518dea193f
Comment 3 Vadym Krevs 2011-11-29 09:49:17 UTC
(In reply to comment #1)
> What is the backend order in systemsettings -> Information Source ->
> NetworkManager. If NetworkManager 0.9 is not the first move it to the first
> position and try again.

Thanks for responding to this so quickly (and fixing it too!).

I don't know what the order was after the upgrade. As many things are broken without a working kded4, I had to find a workaround quickly, and uninstalling all network manager related rpms did the trick. 

This morning, however, I read your comments, and reinstalled network manager. After logging back into KDE, there was no crash, and NetworkManager 0.9 was the first information source.

Thanks again.
Comment 4 Lamarque V. Souza 2011-11-29 10:15:47 UTC
Well, my commit above just prevents the crash but Plasma NM would still not work without a backend loaded. The only things that could prevent a backend from loading is a misconfiguration or missing file.

The backend comes with Plasma NM, but some distributions split Plasma NM files into several packages. If the package with the backend was not installed together with the plasmoid and kded module things can malfunction. Probably that was what happened and reinstalling fixed the problem.

I will this as fixed then. Reopen if it happens again.
Comment 5 Lamarque V. Souza 2012-02-04 12:34:01 UTC
*** Bug 292668 has been marked as a duplicate of this bug. ***