Bug 310187 - after a recent update of project neon (specifically project-neon-kmix and project-neon-kmix-dbg packages), kmix crashes right after reboot and kded (kdeinit4) does not start (KDE Daemon/Kmix/KmixCtrl)
Summary: after a recent update of project neon (specifically project-neon-kmix and pro...
Status: RESOLVED DUPLICATE of bug 310186
Alias: None
Product: kmix
Classification: Applications
Component: general (other bugs)
Version First Reported In: 4.3
Platform: Ubuntu Linux
: NOR crash
Target Milestone: ---
Assignee: Christian Esken
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2012-11-16 02:48 UTC by Simon Andric
Modified: 2012-12-04 23:34 UTC (History)
0 users

See Also:
Latest Commit:
Version Fixed In:
Sentry Crash Report:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Simon Andric 2012-11-16 02:48:00 UTC
Application: kmixctrl (4.3)
KDE Platform Version: 4.9.80
Qt Version: 4.8.4
Operating System: Linux 3.7.0-0-generic i686
Distribution: Ubuntu Raring Ringtail (development branch)

-- Information about the crash:
- What I was doing when the application crashed:

after a recent update of project neon (specifically project-neon-kmix and project-neon-kmix-dbg packages), kmix crashes right after reboot and kded (kdeinit4) does not start
 (KDE Daemon/Kmix/KmixCtrl)

also three dr. konqi windows appear - one for kde daemon, one for kmix and one for kmixctrl.

when i try to send the dr. konqi report after inputing my username/pw i get error 
failed to communicate with kded

i have to initiate the comman kdeinit4 in konsole so i can send the report

i use kubuntu raring all newest stuff in project neon.

nice day
and thank you for all help...you are all the best!

Simon :)

The crash can be reproduced every time.

-- Backtrace:
Application: KMixCtrl (kdeinit4), signal: Aborted
Using host libthread_db library "/lib/i386-linux-gnu/libthread_db.so.1".
[KCrash Handler]
#7  0xb77c6424 in __kernel_vsyscall ()
#8  0xb5ba692f in __GI_raise (sig=sig@entry=6) at ../nptl/sysdeps/unix/sysv/linux/raise.c:63
#9  0xb5ba9ec3 in __GI_abort () at abort.c:90
#10 0xb6b9f1a5 in qt_message_output (msgType=QtFatalMsg, buf=0xa037c38 "ASSERT failure in QDBusConnection::registerObject: \"Invalid object path given\", file qdbusconnection.cpp, line 799") at global/qglobal.cpp:2294
#11 0xb6b9f34d in qt_message (msgType=QtFatalMsg, msg=0xb6d4d4f8 "ASSERT failure in %s: \"%s\", file %s, line %d", ap=0xbffed474 "$\365z\265\b\365z\265\364\364z\265\037\003") at global/qglobal.cpp:2360
#12 0xb6b9f7e3 in qErrnoWarning (code=-1227565832, msg=0xb57af524 "QDBusConnection::registerObject") at global/qglobal.cpp:2521
#13 0xb6b9ed94 in qt_assert (assertion=0xb57af524 "QDBusConnection::registerObject", file=0xb57af508 "Invalid object path given", line=-1250233100) at global/qglobal.cpp:2019
#14 0xb6d4d4f8 in ?? () from /opt/project-neon/lib/libQtCore.so.4
#15 0xb575b443 in QDBusConnection::registerObject (this=0xbffed558, path=..., object=0xa04a220, options=...) at qdbusconnection.cpp:798
#16 0xb10d8c68 in __gnu_cxx::__exchange_and_add_dispatch (__mem=0xa04a220, __val=-1073818192) at /usr/include/c++/4.7/ext/atomicity.h:81
#17 0xb10fb1a2 in MixDevice::init (this=0xbffed634, mixer=0xa03be80, id=..., name=..., iconName=..., moveDestinationMixSet=0x0) at /build/buildd/project-neon-kmix-2+git20121115+r1732/core/mixdevice.cpp:136
#18 0xb10ecb45 in context_state_callback (c=0xa036668) at /build/buildd/project-neon-kmix-2+git20121115+r1732/backends/mixer_pulse.cpp:657
#19 0xb10ed8a4 in Mixer_PULSE::addDevice (this=0xa036668, dev=..., isAppStream=false) at /build/buildd/project-neon-kmix-2+git20121115+r1732/backends/mixer_pulse.cpp:835
#20 0xb10dbc62 in MixerAdaptor::qt_metacall (this=0xa036668, _c=QMetaObject::ReadProperty, _id=-1073817800, _a=0xb6ba3634 <qMalloc(unsigned int)+4>) at /build/buildd/project-neon-kmix-2+git20121115+r1732/obj-i686-linux-gnu/mixeradaptor.moc:114
#21 0xb10f83ab in Mixer::volumeLoad (this=0xa036918, config=0xbffed7a0) at /build/buildd/project-neon-kmix-2+git20121115+r1732/core/mixer.cpp:208
#22 0xb10feb12 in MixerToolBox::initMixerInternal (this=0xa03ef70, multiDriverMode=(unknown: 167995672), backendList=<error reading variable: Cannot access memory at address 0x0>, ref_hwInfoString=...) at /build/buildd/project-neon-kmix-2+git20121115+r1732/core/mixertoolbox.cpp:259
#23 0xb10fe41b in MixerToolBox::initMixerInternal (this=0xa03ef70, multiDriverMode=MixerToolBox::SINGLE_PLUS_MPRIS2, backendList=..., ref_hwInfoString=...) at /build/buildd/project-neon-kmix-2+git20121115+r1732/core/mixertoolbox.cpp:111
#24 0xb10fde9c in QMap<Volume::ChannelID, VolumeChannel>::value (this=0x1, akey=@0xbffed898: 134574960) at /opt/project-neon/include/QtCore/qmap.h:502
#25 0xb10fde4b in QMap<Volume::ChannelID, VolumeChannel>::iterator::operator++ (this=0xa03ef70) at /opt/project-neon/include/QtCore/qmap.h:261
#26 0xb10f2750 in QMap<QString, restoreRule>::mutableFindNode (this=0x2, aupdate=0x9fc9130, akey=...) at /opt/project-neon/include/QtCore/qmap.h:786
#27 0x0804d5b5 in launch (argc=2, _name=0x9ffa3a4 "/opt/project-neon/bin/kmixctrl", args=0x9ffa3cd "", cwd=0x0, envc=0, envs=0x9ffa3d1 "", reset_env=false, tty=0x0, avoid_loops=false, startup_id_str=0x8052fc5 "0") at /build/buildd/project-neon-kdelibs-2+git20121115+r92187/kinit/kinit.cpp:732
#28 0x0804e65e in handle_launcher_request (sock=8, who=0x8053260 "launcher") at /build/buildd/project-neon-kdelibs-2+git20121115+r92187/kinit/kinit.cpp:1221
#29 0x0804eed8 in handle_requests (waitForPid=0) at /build/buildd/project-neon-kdelibs-2+git20121115+r92187/kinit/kinit.cpp:1413
#30 0x080508d4 in main (argc=<error reading variable: Cannot access memory at address 0xe33>, argv=<error reading variable: Cannot access memory at address 0xe33>, envp=<error reading variable: Cannot access memory at address 0xe33>) at /build/buildd/project-neon-kdelibs-2+git20121115+r92187/kinit/kinit.cpp:1902

This bug may be a duplicate of or related to bug 310186, bug 310185.

Possible duplicates by query: bug 310186, bug 310185.

Reported using DrKonqi
Comment 1 Christian Esken 2012-12-04 23:34:32 UTC

*** This bug has been marked as a duplicate of bug 310186 ***