Bug 169966 - kontact crashes libkdecore KConfig
Summary: kontact crashes libkdecore KConfig
Status: RESOLVED REMIND
Alias: None
Product: kontact
Classification: Applications
Component: todo (show other bugs)
Version: unspecified
Platform: Ubuntu Linux
: NOR crash
Target Milestone: ---
Assignee: kdepim bugs
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2008-08-28 09:45 UTC by Pol
Modified: 2008-10-27 20:25 UTC (History)
0 users

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 Pol 2008-08-28 09:45:35 UTC
Version:            (using KDE 3.5.9)
OS:                Linux
Installed from:    Ubuntu Packages

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 0xb5e9b920 (LWP 11099)]
[New Thread 0xb1a61b90 (LWP 14012)]
[New Thread 0xb3544b90 (LWP 11199)]
[New Thread 0xb3d45b90 (LWP 11198)]
[New Thread 0xb4546b90 (LWP 11197)]
[New Thread 0xb4d47b90 (LWP 11196)]
(no debugging symbols found)
(...)

(no debugging symbols found)
[KCrash handler]
#6  0xb6e9654d in KConfigINIBackEnd::parseSingleConfigFile ()
   from /usr/lib/libkdecore.so.4
#7  0xb6e98d81 in KConfigINIBackEnd::parseConfigFiles ()
   from /usr/lib/libkdecore.so.4
#8  0xb6e29fe3 in KConfigBase::parseConfigFiles ()
   from /usr/lib/libkdecore.so.4
#9  0xb6de85bc in KConfig::reparseConfiguration ()
   from /usr/lib/libkdecore.so.4
#10 0xb6e4d951 in KConfig::KConfig () from /usr/lib/libkdecore.so.4
#11 0xb583fff5 in TodoSummaryWidget::updateView ()
  from /usr/lib/kde3/libkontact_todoplugin.so
#12 0xb58412a5 in TodoSummaryWidget::qt_invoke ()
   from /usr/lib/kde3/libkontact_todoplugin.so
#13 0xb6756831 in QObject::activate_signal () from /usr/lib/libqt-mt.so.3
#14 0xb67571e9 in QObject::activate_signal () from /usr/lib/libqt-mt.so.3
#15 0xb7d110a9 in KCal::Calendar::calendarChanged ()
   from /usr/lib/libkcal.so.2
#16 0xb7d117e8 in KCal::Calendar::qt_emit () from /usr/lib/libkcal.so.2
#17 0xb7d5de75 in KCal::CalendarResources::qt_emit ()
   from /usr/lib/libkcal.so.2
#18 0xb67566d8 in QObject::activate_signal () from /usr/lib/libqt-mt.so.3
#19 0xb7d5172e in KCal::ResourceCalendar::resourceChanged ()
   from /usr/lib/libkcal.so.2
#20 0xb2aa49f1 in KCal::ResourceRemote::doLoad ()
   from /usr/lib/libkcal_resourceremote.so.1
#21 0xb7d5258b in KCal::ResourceCalendar::load () from /usr/lib/libkcal.so.2
#22 0xb7d580ae in KCal::ResourceCached::slotReload ()
   from /usr/lib/libkcal.so.2
#23 0xb7d59b98 in KCal::ResourceCached::qt_invoke ()
   from /usr/lib/libkcal.so.2
#24 0xb2aa38ab in KCal::ResourceRemote::qt_invoke ()
   from /usr/lib/libkcal_resourceremote.so.1
#25 0xb6756704 in QObject::activate_signal () from /usr/lib/libqt-mt.so.3
#26 0xb67571e9 in QObject::activate_signal () from /usr/lib/libqt-mt.so.3
#27 0xb6ae8320 in QTimer::timeout () from /usr/lib/libqt-mt.so.3
#28 0xb677dd0e in QTimer::event () from /usr/lib/libqt-mt.so.3
#29 0xb66eac36 in QApplication::internalNotify () from /usr/lib/libqt-mt.so.3
#30 0xb66eca5f in QApplication::notify () from /usr/lib/libqt-mt.so.3
#31 0xb6eab672 in KApplication::notify () from /usr/lib/libkdecore.so.4
#32 0xb667b28d in QApplication::sendEvent () from /usr/lib/libqt-mt.so.3
#33 0xb66ddb19 in QEventLoop::activateTimers () from /usr/lib/libqt-mt.so.3
#34 0xb669064b in QEventLoop::processEvents () from /usr/lib/libqt-mt.so.3
#35 0xb6705f90 in QEventLoop::enterLoop () from /usr/lib/libqt-mt.so.3
#36 0xb6705c8e in QEventLoop::exec () from /usr/lib/libqt-mt.so.3
#37 0xb66ec7df in QApplication::exec () from /usr/lib/libqt-mt.so.3
#38 0x0805c113 in ?? ()
#39 0xb5efe450 in __libc_start_main () from /lib/tls/i686/cmov/libc.so.6
#40 0x0805b7e1 in ?? ()
Comment 1 Bram Schoenmakers 2008-08-28 09:50:46 UTC
Can you provide steps to reproduce and a better backtrace please? Read http://techbase.kde.org/index.php?title=Development/Tutorials/Debugging/How_to_create_useful_crash_reports for more info on how to obtain that.
Comment 2 Bram Schoenmakers 2008-10-27 20:25:54 UTC
Closing this bug due to lack of feedback. Reopen if you can provide the requested information. Thank you.