Summary: | Kontact 4.12.4 Crashes | ||
---|---|---|---|
Product: | [Applications] kontact | Reporter: | Sean <urbanmad> |
Component: | general | Assignee: | kdepim bugs <kdepim-bugs> |
Status: | RESOLVED UNMAINTAINED | ||
Severity: | crash | CC: | urbanmad |
Priority: | NOR | Keywords: | drkonqi |
Version: | 4.12.4 | ||
Target Milestone: | --- | ||
Platform: | Compiled Sources | ||
OS: | Linux | ||
Latest Commit: | Version Fixed In: | ||
Sentry Crash Report: | |||
Attachments: | New crash information added by DrKonqi |
Description
Sean
2014-04-02 19:10:24 UTC
Created attachment 85932 [details]
New crash information added by DrKonqi
kontact (4.12.4) on KDE Platform 4.12.4 using Qt 4.8.5
- What I was doing when the application crashed:
Selecting any email seems to make Kontact crash
-- Backtrace (Reduced):
#6 _strnlen (maxlen=582108, str=0x7f3486e52fdc "video/quicktime, variant=(string)iso"<Address 0x7f3486e53000 out of bounds>) at gstregistrychunks.c:52
#7 gst_registry_chunks_load_pad_template (end=0x7f3486ee11b8 "", in=0x7fffe6574178, factory=0x4561c60) at gstregistrychunks.c:526
#8 gst_registry_chunks_load_feature (plugin=0x4546750, end=0x7f3486ee11b8 "", in=0x7fffe6574178, registry=0x4547060) at gstregistrychunks.c:625
#9 _priv_gst_registry_chunks_load_plugin (registry=registry@entry=0x4547060, in=in@entry=0x7fffe6574178, end=end@entry=0x7f3486ee11b8 "", out_plugin=out_plugin@entry=0x0) at gstregistrychunks.c:861
#10 0x00007f34fec04470 in gst_registry_binary_read_cache (registry=registry@entry=0x4547060, location=location@entry=0x45491c0 "/home/seansloanejohnson/.gstreamer-0.10/registry.x86_64.bin") at gstregistrybinary.c:600
problem of qtwebkit and gstreamer. Is this something that will be patched soon? Or should I rebuild my machine? This bug has only been reported for versions before 4.14, which have been unsupported for at least two years now. Can anyone tell if this bug still present? If noone confirms this bug for a Framework-based version of kontact (version 5.0 or later, as part of KDE Applications 15.08 or later), it gets closed in about three months. Just as announced in my last comment, I close this bug. If you encounter it again in a recent version (at least 5.0 aka 15.08), please open a new one unless it already exists. Thank you for all your input. |