abrt version: 1.1.17
Attached file: backtrace, 51430 bytes
cmdline: 'kdeinit4: plasma-desktop [kdeinit] --nocrashhandler'
Attached file: coredump, 196751360 bytes
reason: Process /usr/bin/kdeinit4 was killed by signal 11 (SIGSEGV)
release: Fedora release 14 (Laughlin)
How to reproduce
1. Use kde
Created attachment 494252 [details]
OS Release: Fedora release 14 (Laughlin)
How to reproduce
1. Happened shortly after unlocking screen saver.
I *suspect* this is may related to the crashes fixed in kdepim-184.108.40.206 ,
#3 KCalCore::IncidenceBase::isReadOnly (this=0x0) at /usr/src/debug/kdepimlibs-4.6.2/kcalcore/incidencebase.cpp:286
#4 0x00007f904207d3d5 in CalendarSupport::Calendar::Private::updateItem (this=0x2184fb0, item=..., mode=<value optimized out>) at /usr/src/debug/kdebase-workspace-4.6.2/plasma/generic/dataengines/calendar/akonadi/calendar.cpp:323
Yes, that's the crash kdepim-4.4.11(.1) was released for. It should be fixed in kdepim-220.127.116.11.
Any idea when kdepim-18.104.22.168 will hit the testing repo? Crashes every 10 minutes are very annoying.
kdepim-22.214.171.124-2.fc15,kdepim-runtime-126.96.36.199-1.fc15 has been submitted as an update for Fedora 15.
kdepim-188.8.131.52-2.fc14,kdepim-runtime-184.108.40.206-1.fc14 has been submitted as an update for Fedora 14.
Package kdepim-220.127.116.11-2.fc14, kdepim-runtime-18.104.22.168-1.fc14:
* should fix your issue,
* was pushed to the Fedora 14 testing repository,
* should be available at your local mirror within two days.
Update it with:
# su -c 'yum update --enablerepo=updates-testing kdepim-22.214.171.124-2.fc14 kdepim-runtime-126.96.36.199-1.fc14'
as soon as you are able to.
Please go to the following url:
then log in and leave karma (feedback).
kdepim-188.8.131.52-2.fc15, kdepim-runtime-184.108.40.206-1.fc15 has been pushed to the Fedora 15 stable repository. If problems still persist, please make note of it in this bug report.
kdepim-220.127.116.11-2.fc14, kdepim-runtime-18.104.22.168-1.fc14 has been pushed to the Fedora 14 stable repository. If problems still persist, please make note of it in this bug report.