Bug 173696 - kontact wont start after intrepid update, had problem with adding contacts before update
Summary: kontact wont start after intrepid update, had problem with adding contacts be...
Status: RESOLVED DUPLICATE of bug 165548
Alias: None
Product: kdelibs
Classification: Frameworks and Libraries
Component: kded (show other bugs)
Version: unspecified
Platform: Ubuntu Linux
: NOR crash
Target Milestone: ---
Assignee: Flavio Castelli
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2008-10-27 19:47 UTC by Kevin
Modified: 2010-02-25 00:31 UTC (History)
1 user (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 Kevin 2008-10-27 19:47:12 UTC
Version:            (using KDE 4.1.2)
OS:                Linux
Installed from:    Ubuntu Packages

Hi

I have a prior bug report re: not being able to update contacts in Kontact https://bugs.launchpad.net/bugs/275314

Over the weekend I did a distribution update to intrepid. Now neither Kontact or Korganizer will start. Korganizer is in the tray, but will not start.

Application: KDE Daemon (kded4), signal SIGSEGV
[Thread debugging using libthread_db enabled]
[New Thread 0xb60c88d0 (LWP 6717)]
[KCrash handler]
#6  0xb7c0bc09 in KDirWatchPrivate::useINotify (this=0x97d6838, e=0x98e7644)
    at /build/buildd/kde4libs-4.1.2/kio/kio/kdirwatch.cpp:534
#7  0xb7c0daf3 in KDirWatchPrivate::inotifyEventReceived (this=0x97d6838)
    at /build/buildd/kde4libs-4.1.2/kio/kio/kdirwatch.cpp:301
#8  0xb7c0dc9b in KDirWatchPrivate::qt_metacall (this=0x97d6838, 
    _c=QMetaObject::InvokeMetaMethod, _id=2, _a=0xbf925b0c)
    at /build/buildd/kde4libs-4.1.2/obj-i486-linux-gnu/kio/kdirwatch_p.moc:74
#9  0xb74aca60 in QMetaObject::activate () from /usr/lib/libQtCore.so.4
#10 0xb74ad7e2 in QMetaObject::activate () from /usr/lib/libQtCore.so.4
#11 0xb74e7633 in QSocketNotifier::activated () from /usr/lib/libQtCore.so.4
#12 0xb74b2637 in QSocketNotifier::event () from /usr/lib/libQtCore.so.4
#13 0xb6a2a8ec in QApplicationPrivate::notify_helper ()
   from /usr/lib/libQtGui.so.4
#14 0xb6a3276e in QApplication::notify () from /usr/lib/libQtGui.so.4
#15 0xb796672d in KApplication::notify (this=0xbf9261a0, receiver=0x97d6ba0, 
    event=0xbf925ed0)
    at /build/buildd/kde4libs-4.1.2/kdeui/kernel/kapplication.cpp:311
#16 0xb7497e61 in QCoreApplication::notifyInternal ()
   from /usr/lib/libQtCore.so.4
#17 0xb74c270a in ?? () from /usr/lib/libQtCore.so.4
#18 0xb64596f8 in g_main_context_dispatch () from /usr/lib/libglib-2.0.so.0
#19 0xb645cda3 in ?? () from /usr/lib/libglib-2.0.so.0
#20 0xb645cf61 in g_main_context_iteration () from /usr/lib/libglib-2.0.so.0
#21 0xb74c2478 in QEventDispatcherGlib::processEvents ()
   from /usr/lib/libQtCore.so.4
#22 0xb6ac4ee5 in ?? () from /usr/lib/libQtGui.so.4
#23 0xb749652a in QEventLoop::processEvents () from /usr/lib/libQtCore.so.4
#24 0xb74966ea in QEventLoop::exec () from /usr/lib/libQtCore.so.4
#25 0xb7498da5 in QCoreApplication::exec () from /usr/lib/libQtCore.so.4
#26 0xb6a2a767 in QApplication::exec () from /usr/lib/libQtGui.so.4
#27 0xb7ee90a6 in kdemain (argc=1, argv=0xbf926434)
    at /build/buildd/kde4libs-4.1.2/kded/kded.cpp:847
#28 0x080485a2 in main (argc=)
    at /build/buildd/kde4libs-4.1.2/obj-i486-linux-gnu/kded/kded4_dummy.cpp:3
#0  0xb7f24430 in __kernel_vsyscall ()


Please let me know if you need more.

Regards,

Kevin
Comment 1 David Faure 2008-10-27 22:45:41 UTC
Reassigning to someone who knows KDirWatch.

(Flavio: how about using flavio@castelli.name in kde-common/accounts? ;-)
Comment 2 Christoph Feck 2009-12-04 03:05:00 UTC
SVN commit 1058169 by cfeck:

Fix broken reading in inotifyEventReceived

Multiple bugs:
* MAX_PATH is 4096 on linux, but inotify_event needs some bytes as well
* the "pending" variable was incorrectly abused to mean both pending
    bytes in buffer as well as pending bytes in stream
* the offset was not reset to zero when the next chunk was reading
* when an event was larger than what was available in buffer, it was reading
    beyond the buffer boundaries

Many thanks to David for review and help with improving clarity of the code.

David, please test for regressions, maybe add a test which changes
some 1000 files in one go.

CCMAIL:faure@kde.org

CCBUG:165548
CCBUG:173696
CCBUG:175005
CCBUG:198692
CCBUG:204178


 M  +20 -9     kdirwatch.cpp  


WebSVN link: http://websvn.kde.org/?view=rev&revision=1058169
Comment 3 Christoph Feck 2010-02-25 00:31:15 UTC

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