[kmail2] [Bug 330447] Folder properties set folder to view attachments as inline.
https://bugs.kde.org/show_bug.cgi?id=330447 bgodu...@pcprotechs.com changed: What|Removed |Added Status|RESOLVED|UNCONFIRMED Resolution|WONTFIX |--- --- Comment #5 from bgodu...@pcprotechs.com --- I would disagree, since there is already a properties page for every single folder in kmail where other properties can be set individually! So your pos of it's not easy for users to know that there is a global and a folder setting is simply ludicrous! Why not push an email to the entire community and see what everyone else has to say about it especially since each folder already has it's own separate properties page that can be set differently then what is set in the global properties!? -- You are receiving this mail because: You are the assignee for the bug. ___ Kdepim-bugs mailing list Kdepim-bugs@kde.org https://mail.kde.org/mailman/listinfo/kdepim-bugs
[kmail2] [Bug 330447] Folder properties set folder to view attachments as inline.
https://bugs.kde.org/show_bug.cgi?id=330447 --- Comment #3 from bgodu...@pcprotechs.com --- A simple way to test this additional feature would be to send yourself emails with images as attachments. Have Kmail redirect those messages to a specific folder as I have done for my security system. Then open those emails to see if your changes open the images inline when opening those emails. I'd be happy to send you some of these emails that my system captures if you wish and that way you could set up a redirection to a specific folder on my email address. -- You are receiving this mail because: You are the assignee for the bug. ___ Kdepim-bugs mailing list Kdepim-bugs@kde.org https://mail.kde.org/mailman/listinfo/kdepim-bugs
[kmail2] [Bug 330447] Folder properties set folder to view attachments as inline.
https://bugs.kde.org/show_bug.cgi?id=330447 --- Comment #2 from bgodu...@pcprotechs.com --- On Monday, January, 27, 2014 6:03:18 AM you wrote: > https://bugs.kde.org/show_bug.cgi?id=330447 > > Laurent Montel changed: > >What|Removed |Added > > CC||mon...@kde.org > > --- Comment #1 from Laurent Montel --- > Why you didn't change it for all messages ? > > Need a testcase Laurent, I don't want it to set like that for all folders since I receive quit a few emails with attachments not all of which are trust worthy to view inline. As I said in my feature request, the capability to set a single folder to do this would be great and would benefit not just myself but many others who have security systems that email images to them when an alarm is captured. -- You are receiving this mail because: You are the assignee for the bug. ___ Kdepim-bugs mailing list Kdepim-bugs@kde.org https://mail.kde.org/mailman/listinfo/kdepim-bugs
[kmail2] [Bug 330447] Folder properties set folder to view attachments as inline.
https://bugs.kde.org/show_bug.cgi?id=330447 bgodu...@pcprotechs.com changed: What|Removed |Added CC||bgodu...@pcprotechs.com -- You are receiving this mail because: You are the assignee for the bug. ___ Kdepim-bugs mailing list Kdepim-bugs@kde.org https://mail.kde.org/mailman/listinfo/kdepim-bugs
[kmail2] [Bug 330447] Folder properties set folder to view attachments as inline.
https://bugs.kde.org/show_bug.cgi?id=330447 bgodu...@pcprotechs.com changed: What|Removed |Added Platform|unspecified |Archlinux Packages -- You are receiving this mail because: You are the assignee for the bug. ___ Kdepim-bugs mailing list Kdepim-bugs@kde.org https://mail.kde.org/mailman/listinfo/kdepim-bugs
[kmail2] [Bug 330447] Folder properties set folder to view attachments as inline.
https://bugs.kde.org/show_bug.cgi?id=330447 bgodu...@pcprotechs.com changed: What|Removed |Added Version|4.12|4.12.1 -- You are receiving this mail because: You are the assignee for the bug. ___ Kdepim-bugs mailing list Kdepim-bugs@kde.org https://mail.kde.org/mailman/listinfo/kdepim-bugs
[kmail2] [Bug 330447] New: Folder properties set folder to view attachments as inline.
https://bugs.kde.org/show_bug.cgi?id=330447 Bug ID: 330447 Summary: Folder properties set folder to view attachments as inline. Classification: Unclassified Product: kmail2 Version: 4.12 Platform: unspecified OS: Linux Status: UNCONFIRMED Severity: wishlist Priority: NOR Component: folders Assignee: kdepim-bugs@kde.org Reporter: bgodu...@pcprotechs.com OK, here we go. I have one folder in KMail that my security system sends emails to including images, sometimes 6 or more images in an email. Is there anyway to default just this one folder to inline view for these emails? I already have HTML as a preference but that does NOT show these images in the inline view. All of these images have the .jpg extension. If there is no way to do this, then perhaps it should be a feature request to make life easier not only for me but for all others that have a security system that emails captured images on movement like a good security system should. Reproducible: Always Steps to Reproduce: 1.Wish list feature 2.A feature that the entire community would greatly appreciate 3. Actual Results: Set properties on specified folder to view email attachments inline instead of having to do so on every individual email in the folder. Expected Results: Set folder properties to view all email attachments in a specified folder as inline. This would be a great feature to add and I suspect many users would use it frequently on specified folders known to be OK to view without worry of a virus or other malady from an unknown user. For instance some days I receive up to 200 emails from my security system all of which contain image captures of movement. Sure would be nice to be able to just open the email and view all the attachments without having to resort to using the menu item viewhttps://mail.kde.org/mailman/listinfo/kdepim-bugs
[Bug 294770] New: KMail crash on opening email
https://bugs.kde.org/show_bug.cgi?id=294770 Summary: KMail crash on opening email Product: kmail2 Version: unspecified Platform: Fedora RPMs OS/Version: Linux Status: UNCONFIRMED Severity: crash Priority: NOR Component: general AssignedTo: kdepim-bugs@kde.org ReportedBy: bgodu...@pcprotechs.com Application: kmail (4.8.0) KDE Platform Version: 4.8.00 (4.8.0) Qt Version: 4.8.0 Operating System: Linux 3.3.0-0.rc4.git1.4.fc17.x86_64 x86_64 Distribution (Platform): Fedora RPMs -- Information about the crash: - What I was doing when the application crashed: Surfing the web with firefox. Opened KMail to check email. Tried to open a newly recieved email and double clicked it to open it and KMail crashed. The crash can be reproduced every time. -- Backtrace: Application: KMail (kmail), signal: Segmentation fault Using host libthread_db library "/lib64/libthread_db.so.1". pthread_cond_wait@@GLIBC_2.3.2 () at ../nptl/sysdeps/unix/sysv/linux/x86_64/pthread_cond_wait.S:166 16662:movl(%rsp), %edi [Current thread is 1 (Thread 0x7fb6b9879880 (LWP 1799))] Thread 8 (Thread 0x7fb6ad90e700 (LWP 1803)): #0 pthread_cond_timedwait@@GLIBC_2.3.2 () at ../nptl/sysdeps/unix/sysv/linux/x86_64/pthread_cond_timedwait.S:218 #1 0x003d3967b927 in wait (time=3, this=0x118a060) at thread/qwaitcondition_unix.cpp:84 #2 QWaitCondition::wait (this=, mutex=0x118a008, time=3) at thread/qwaitcondition_unix.cpp:158 #3 0x003d3966f1af in QThreadPoolThread::run (this=0x119c990) at concurrent/qthreadpool.cpp:141 #4 0x003d3967b4cb in QThreadPrivate::start (arg=0x119c990) at thread/qthread_unix.cpp:298 #5 0x003d30e07d14 in start_thread (arg=0x7fb6ad90e700) at pthread_create.c:309 #6 0x003d30af105d in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:115 Thread 7 (Thread 0x7fb6a7fff700 (LWP 1810)): #0 pthread_cond_wait@@GLIBC_2.3.2 () at ../nptl/sysdeps/unix/sysv/linux/x86_64/pthread_cond_wait.S:166 #1 0x003c77f7e685 in WTF::TCMalloc_PageHeap::scavengerThread (this=0x3c78952740) at ../../../Source/JavaScriptCore/wtf/FastMalloc.cpp:2495 #2 0x003c77f7e6e9 in WTF::TCMalloc_PageHeap::runScavengerThread (context=) at ../../../Source/JavaScriptCore/wtf/FastMalloc.cpp:1618 #3 0x003d30e07d14 in start_thread (arg=0x7fb6a7fff700) at pthread_create.c:309 #4 0x003d30af105d in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:115 Thread 6 (Thread 0x7fb6a77fe700 (LWP 1811)): #0 0x003d30ae85af in __GI___poll (fds=, nfds=, timeout=) at ../sysdeps/unix/sysv/linux/poll.c:87 #1 0x003d30647824 in g_main_context_poll (n_fds=1, fds=0x7fb69c0029c0, timeout=3093, context=0x7fb69c0009a0, priority=) at gmain.c:3412 #2 g_main_context_iterate (context=context@entry=0x7fb69c0009a0, block=block@entry=1, dispatch=dispatch@entry=1, self=) at gmain.c:3113 #3 0x003d30647944 in g_main_context_iteration (context=0x7fb69c0009a0, may_block=1) at gmain.c:3179 #4 0x003d397a2976 in QEventDispatcherGlib::processEvents (this=0x7fb69c0008c0, flags=...) at kernel/qeventdispatcher_glib.cpp:426 #5 0x003d3977382f in QEventLoop::processEvents (this=this@entry=0x7fb6a77fdd20, flags=...) at kernel/qeventloop.cpp:149 #6 0x003d39773ab8 in QEventLoop::exec (this=0x7fb6a77fdd20, flags=...) at kernel/qeventloop.cpp:204 #7 0x003d39678588 in QThread::exec (this=) at thread/qthread.cpp:501 #8 0x003d3967b4cb in QThreadPrivate::start (arg=0x1626cc0) at thread/qthread_unix.cpp:298 #9 0x003d30e07d14 in start_thread (arg=0x7fb6a77fe700) at pthread_create.c:309 #10 0x003d30af105d in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:115 Thread 5 (Thread 0x7fb6a5ae0700 (LWP 1812)): #0 pthread_cond_timedwait@@GLIBC_2.3.2 () at ../nptl/sysdeps/unix/sysv/linux/x86_64/pthread_cond_timedwait.S:218 #1 0x003d3967b927 in wait (time=3, this=0x1689fc0) at thread/qwaitcondition_unix.cpp:84 #2 QWaitCondition::wait (this=, mutex=0x168b928, time=3) at thread/qwaitcondition_unix.cpp:158 #3 0x003d3966f1af in QThreadPoolThread::run (this=0x169f3e0) at concurrent/qthreadpool.cpp:141 #4 0x003d3967b4cb in QThreadPrivate::start (arg=0x169f3e0) at thread/qthread_unix.cpp:298 #5 0x003d30e07d14 in start_thread (arg=0x7fb6a5ae0700) at pthread_create.c:309 #6 0x003d30af105d in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:115 Thread 4 (Thread 0x7fb65bfff700 (LWP 1814)): #0 0x7fff0a1ff8f4 in ?? () #1 0x003d3160410d in __GI_clock_gettime (clock_id=, tp=) at ../sysdeps/unix/clock_gettime.c:116 #2 0x003d396d0e74 in do_gettime (frac=0x7fb65bffea88, sec=0x7fb65bffea80) at tools/qelapsedtimer_unix.cpp:123 #3 qt_gettime () at tools/qelapsedtimer_unix.cpp:140 #4 0x003d397a317d in QTimerInfoList::updateCurrentTime (this=this@entry=0x7fb650002660) at kernel/qeventdispatcher_unix.cpp:343 #5 0x003d397a34c1 in QTimerInfoList::timerWait (this=0x7fb6
[Bug 294769] New: Kontact crashes on opening of email
https://bugs.kde.org/show_bug.cgi?id=294769 Summary: Kontact crashes on opening of email Product: kontact Version: unspecified Platform: Fedora RPMs OS/Version: Linux Status: UNCONFIRMED Severity: crash Priority: NOR Component: general AssignedTo: kdepim-bugs@kde.org ReportedBy: bgodu...@pcprotechs.com Application: kontact (4.8.0) KDE Platform Version: 4.8.00 (4.8.0) Qt Version: 4.8.0 Operating System: Linux 3.3.0-0.rc4.git1.4.fc17.x86_64 x86_64 Distribution (Platform): Fedora RPMs -- Information about the crash: - What I was doing when the application crashed: Opened Kontact to cheack mail. Tried to open an email and every time I click on an email Kontact crashes. Restarted it 3 times each resulting in a crash. The crash can be reproduced every time. -- Backtrace: Application: Kontact (kontact), signal: Segmentation fault Using host libthread_db library "/lib64/libthread_db.so.1". pthread_cond_wait@@GLIBC_2.3.2 () at ../nptl/sysdeps/unix/sysv/linux/x86_64/pthread_cond_wait.S:166 16662:movl(%rsp), %edi [Current thread is 1 (Thread 0x7f70b8b28880 (LWP 1654))] Thread 10 (Thread 0x7f70ad6c9700 (LWP 1655)): #0 pthread_cond_wait@@GLIBC_2.3.2 () at ../nptl/sysdeps/unix/sysv/linux/x86_64/pthread_cond_wait.S:166 #1 0x003c77f7e685 in WTF::TCMalloc_PageHeap::scavengerThread (this=0x3c78952740) at ../../../Source/JavaScriptCore/wtf/FastMalloc.cpp:2495 #2 0x003c77f7e6e9 in WTF::TCMalloc_PageHeap::runScavengerThread (context=) at ../../../Source/JavaScriptCore/wtf/FastMalloc.cpp:1618 #3 0x003d30e07d14 in start_thread (arg=0x7f70ad6c9700) at pthread_create.c:309 #4 0x003d30af105d in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:115 Thread 9 (Thread 0x7f70acdb0700 (LWP 1656)): #0 0x003d30ae85af in __GI___poll (fds=, nfds=, timeout=) at ../sysdeps/unix/sysv/linux/poll.c:87 #1 0x003d30647824 in g_main_context_poll (n_fds=1, fds=0x7f70a80029c0, timeout=5801, context=0x7f70a80009a0, priority=) at gmain.c:3412 #2 g_main_context_iterate (context=context@entry=0x7f70a80009a0, block=block@entry=1, dispatch=dispatch@entry=1, self=) at gmain.c:3113 #3 0x003d30647944 in g_main_context_iteration (context=0x7f70a80009a0, may_block=1) at gmain.c:3179 #4 0x003d397a2976 in QEventDispatcherGlib::processEvents (this=0x7f70a80008c0, flags=...) at kernel/qeventdispatcher_glib.cpp:426 #5 0x003d3977382f in QEventLoop::processEvents (this=this@entry=0x7f70acdafd20, flags=...) at kernel/qeventloop.cpp:149 #6 0x003d39773ab8 in QEventLoop::exec (this=0x7f70acdafd20, flags=...) at kernel/qeventloop.cpp:204 #7 0x003d39678588 in QThread::exec (this=) at thread/qthread.cpp:501 #8 0x003d3967b4cb in QThreadPrivate::start (arg=0x212cc20) at thread/qthread_unix.cpp:298 #9 0x003d30e07d14 in start_thread (arg=0x7f70acdb0700) at pthread_create.c:309 #10 0x003d30af105d in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:115 Thread 8 (Thread 0x7f7063de8700 (LWP 1667)): #0 pthread_cond_timedwait@@GLIBC_2.3.2 () at ../nptl/sysdeps/unix/sysv/linux/x86_64/pthread_cond_timedwait.S:218 #1 0x003d3967b927 in wait (time=3, this=0x276c5e0) at thread/qwaitcondition_unix.cpp:84 #2 QWaitCondition::wait (this=, mutex=0x276c588, time=3) at thread/qwaitcondition_unix.cpp:158 #3 0x003d3966f1af in QThreadPoolThread::run (this=0x277e470) at concurrent/qthreadpool.cpp:141 #4 0x003d3967b4cb in QThreadPrivate::start (arg=0x277e470) at thread/qthread_unix.cpp:298 #5 0x003d30e07d14 in start_thread (arg=0x7f7063de8700) at pthread_create.c:309 #6 0x003d30af105d in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:115 Thread 7 (Thread 0x7f7062bc2700 (LWP 1674)): #0 pthread_cond_timedwait@@GLIBC_2.3.2 () at ../nptl/sysdeps/unix/sysv/linux/x86_64/pthread_cond_timedwait.S:218 #1 0x003d3967b927 in wait (time=3, this=0x26512f0) at thread/qwaitcondition_unix.cpp:84 #2 QWaitCondition::wait (this=, mutex=0x2c74548, time=3) at thread/qwaitcondition_unix.cpp:158 #3 0x003d3966f1af in QThreadPoolThread::run (this=0x2c724d0) at concurrent/qthreadpool.cpp:141 #4 0x003d3967b4cb in QThreadPrivate::start (arg=0x2c724d0) at thread/qthread_unix.cpp:298 #5 0x003d30e07d14 in start_thread (arg=0x7f7062bc2700) at pthread_create.c:309 #6 0x003d30af105d in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:115 Thread 6 (Thread 0x7f7061aa0700 (LWP 1676)): #0 pthread_cond_timedwait@@GLIBC_2.3.2 () at ../nptl/sysdeps/unix/sysv/linux/x86_64/pthread_cond_timedwait.S:218 #1 0x003d3967b927 in wait (time=3, this=0x2dbd350) at thread/qwaitcondition_unix.cpp:84 #2 QWaitCondition::wait (this=, mutex=0x2dc3018, time=3) at thread/qwaitcondition_unix.cpp:158 #3 0x003d3966f1af in QThreadPoolThread::run (this=0x2dd64c0) at concurrent/qthreadpool.cpp:141 #4 0x003d3967b4cb in QThreadPrivate::start (arg=0x2dd64c0) at
[Bug 294644] Kontact crash with Kmail email selection
https://bugs.kde.org/show_bug.cgi?id=294644 --- Comment #1 from2012-02-23 14:54:36 --- Created an attachment (id=69035) --> (http://bugs.kde.org/attachment.cgi?id=69035) New crash information added by DrKonqi kontact (4.8.0) on KDE Platform 4.8.00 (4.8.0) using Qt 4.8.0 - What I was doing when the application crashed: This is reproducable everytime. Simply double clicking on an email to open it cuases Kontact to crash. However simply highlighting it and pressing the enter key to open it works without crashing Kontact. -- Backtrace (Reduced): #6 0x003d30b29706 in __nscd_get_mapping (type=type@entry=GETFDHST, key=0x3d30b7666a "hosts", mappedp=mappedp@entry=0x3d30db5468) at nscd_helper.c:417 [...] #8 0x003d30b26e05 in nscd_gethst_r (key=key@entry=0x7ffcec002b28 "wendellpotter.com", keylen=18, type=type@entry=GETHOSTBYNAME, resultbuf=resultbuf@entry=0x7ffcfc8eb440, buffer=buffer@entry=0x7ffcfc8eb060 "", buflen=buflen@entry=512, result=result@entry=0x7ffcfc8eb430, h_errnop=h_errnop@entry=0x7ffcfc8eb3f0) at nscd_gethst_r.c:147 #9 0x003d30b276d6 in __nscd_gethostbyname2_r (name=name@entry=0x7ffcec002b28 "wendellpotter.com", af=af@entry=2, resultbuf=resultbuf@entry=0x7ffcfc8eb440, buffer=0x7ffcfc8eb060 "", buflen=buflen@entry=512, result=result@entry=0x7ffcfc8eb430, h_errnop=h_errnop@entry=0x7ffcfc8eb3f0) at nscd_gethst_r.c:62 #10 0x003d30b0a06a in __gethostbyname2_r (name=name@entry=0x7ffcec002b28 "wendellpotter.com", af=af@entry=2, resbuf=resbuf@entry=0x7ffcfc8eb440, buffer=buffer@entry=0x7ffcfc8eb060 "", buflen=buflen@entry=512, result=result@entry=0x7ffcfc8eb430, h_errnop=h_errnop@entry=0x7ffcfc8eb3f0) at ../nss/getXXbyYY_r.c:194 #11 0x003d30ad96d2 in gaih_inet (name=name@entry=0x7ffcec002b28 "wendellpotter.com", service=, req=req@entry=0x7ffcfc8eb5d0, pai=pai@entry=0x7ffcfc8eb540, naddrs=naddrs@entry=0x7ffcfc8eb520) at ../sysdeps/posix/getaddrinfo.c:581 -- Configure bugmail: https://bugs.kde.org/userprefs.cgi?tab=email --- You are receiving this mail because: --- You are the assignee for the bug. ___ Kdepim-bugs mailing list Kdepim-bugs@kde.org https://mail.kde.org/mailman/listinfo/kdepim-bugs
[Bug 294644] Kontact crash with Kmail email selection
https://bugs.kde.org/show_bug.cgi?id=294644 bgodu...@pcprotechs.com changed: What|Removed |Added CC||bgodu...@pcprotechs.com -- Configure bugmail: https://bugs.kde.org/userprefs.cgi?tab=email --- You are receiving this mail because: --- You are the assignee for the bug. ___ Kdepim-bugs mailing list Kdepim-bugs@kde.org https://mail.kde.org/mailman/listinfo/kdepim-bugs
[Bug 294644] New: Kontact crash with Kmail email selection
https://bugs.kde.org/show_bug.cgi?id=294644 Summary: Kontact crash with Kmail email selection Product: kontact Version: unspecified Platform: Fedora RPMs OS/Version: Linux Status: UNCONFIRMED Severity: crash Priority: NOR Component: general AssignedTo: kdepim-bugs@kde.org ReportedBy: bgodu...@pcprotechs.com Application: kontact (4.8.0) KDE Platform Version: 4.8.00 (4.8.0) Qt Version: 4.8.0 Operating System: Linux 3.3.0-0.rc3.git7.2.fc17.x86_64 x86_64 Distribution (Platform): Fedora RPMs -- Information about the crash: - What I was doing when the application crashed: I selected one email then pressed the ctrl key to select another email to delete and upon pressing the control key Kontact crashed. Restarted it and tried to do the same thing it crashed again. The third time it stayed running and allowed me to select email with the ctrl key depressed to select multiple emails to delete The crash can be reproduced some of the time. -- Backtrace: Application: Kontact (kontact), signal: Segmentation fault Using host libthread_db library "/lib64/libthread_db.so.1". pthread_cond_wait@@GLIBC_2.3.2 () at ../nptl/sysdeps/unix/sysv/linux/x86_64/pthread_cond_wait.S:166 16662:movl(%rsp), %edi [Current thread is 1 (Thread 0x7f47bf7be880 (LWP 1495))] Thread 5 (Thread 0x7f47b28c7700 (LWP 1496)): #0 pthread_cond_wait@@GLIBC_2.3.2 () at ../nptl/sysdeps/unix/sysv/linux/x86_64/pthread_cond_wait.S:166 #1 0x003c77f7e685 in WTF::TCMalloc_PageHeap::scavengerThread (this=0x3c78952740) at ../../../Source/JavaScriptCore/wtf/FastMalloc.cpp:2495 #2 0x003c77f7e6e9 in WTF::TCMalloc_PageHeap::runScavengerThread (context=) at ../../../Source/JavaScriptCore/wtf/FastMalloc.cpp:1618 #3 0x003d30e07d14 in start_thread (arg=0x7f47b28c7700) at pthread_create.c:309 #4 0x003d30af105d in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:115 Thread 4 (Thread 0x7f47b1fa6700 (LWP 1497)): #0 0x003d30ae85af in __GI___poll (fds=, nfds=, timeout=) at ../sysdeps/unix/sysv/linux/poll.c:87 #1 0x003d30647824 in g_main_context_poll (n_fds=1, fds=0x7f47ac0029c0, timeout=250, context=0x7f47ac0009a0, priority=) at gmain.c:3412 #2 g_main_context_iterate (context=context@entry=0x7f47ac0009a0, block=block@entry=1, dispatch=dispatch@entry=1, self=) at gmain.c:3113 #3 0x003d30647944 in g_main_context_iteration (context=0x7f47ac0009a0, may_block=1) at gmain.c:3179 #4 0x003d397a2976 in QEventDispatcherGlib::processEvents (this=0x7f47ac0008c0, flags=...) at kernel/qeventdispatcher_glib.cpp:426 #5 0x003d3977382f in QEventLoop::processEvents (this=this@entry=0x7f47b1fa5d20, flags=...) at kernel/qeventloop.cpp:149 #6 0x003d39773ab8 in QEventLoop::exec (this=0x7f47b1fa5d20, flags=...) at kernel/qeventloop.cpp:204 #7 0x003d39678588 in QThread::exec (this=) at thread/qthread.cpp:501 #8 0x003d3967b4cb in QThreadPrivate::start (arg=0x1ca8ae0) at thread/qthread_unix.cpp:298 #9 0x003d30e07d14 in start_thread (arg=0x7f47b1fa6700) at pthread_create.c:309 #10 0x003d30af105d in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:115 Thread 3 (Thread 0x7f47615d3700 (LWP 1596)): #0 0x003d30ae85af in __GI___poll (fds=, nfds=, timeout=) at ../sysdeps/unix/sysv/linux/poll.c:87 #1 0x003d30647824 in g_main_context_poll (n_fds=1, fds=0x7f47580028d0, timeout=-1, context=0x7f47580009a0, priority=) at gmain.c:3412 #2 g_main_context_iterate (context=context@entry=0x7f47580009a0, block=block@entry=1, dispatch=dispatch@entry=1, self=) at gmain.c:3113 #3 0x003d30647944 in g_main_context_iteration (context=0x7f47580009a0, may_block=1) at gmain.c:3179 #4 0x003d397a2976 in QEventDispatcherGlib::processEvents (this=0x7f47580008c0, flags=...) at kernel/qeventdispatcher_glib.cpp:426 #5 0x003d3977382f in QEventLoop::processEvents (this=this@entry=0x7f47615d2d20, flags=...) at kernel/qeventloop.cpp:149 #6 0x003d39773ab8 in QEventLoop::exec (this=0x7f47615d2d20, flags=...) at kernel/qeventloop.cpp:204 #7 0x003d39678588 in QThread::exec (this=) at thread/qthread.cpp:501 #8 0x003d3967b4cb in QThreadPrivate::start (arg=0x29c7fa0) at thread/qthread_unix.cpp:298 #9 0x003d30e07d14 in start_thread (arg=0x7f47615d3700) at pthread_create.c:309 #10 0x003d30af105d in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:115 Thread 2 (Thread 0x7f4760dd2700 (LWP 1597)): [KCrash Handler] #6 0x003d30b29706 in __nscd_get_mapping (type=type@entry=GETFDHST, key=0x3d30b7666a "hosts", mappedp=mappedp@entry=0x3d30db5468) at nscd_helper.c:417 #7 0x003d30b2995d in __nscd_get_map_ref (type=type@entry=GETFDHST, name=name@entry=0x3d30b7666a "hosts", mapptr=mapptr@entry=0x3d30db5460, gc_cyclep=gc_cyclep@entry=0x7f4760dd0e90) at nscd_helper.c:452 #8 0x003d30b26e05 in nscd_gethst_r (key=key@entry=0x7f474c002ac8 "www.grassfire.com", keylen=18, type=type@entry=GETHOSTBYNAME
[Bug 294425] New: Kontact Crash when clicking on inbox on summary page. Ver 4.8.0
https://bugs.kde.org/show_bug.cgi?id=294425 Summary: Kontact Crash when clicking on inbox on summary page. Ver 4.8.0 Product: kontact Version: unspecified Platform: Fedora RPMs OS/Version: Linux Status: UNCONFIRMED Severity: crash Priority: NOR Component: general AssignedTo: kdepim-bugs@kde.org ReportedBy: bgodu...@pcprotechs.com Application: kontact (4.8.0) KDE Platform Version: 4.8.00 (4.8.0 Qt Version: 4.8.0 Operating System: Linux 3.2.6-3.fc16.x86_64 x86_64 Distribution: "Fedora release 16 (Verne)" -- Information about the crash: - What I was doing when the application crashed: Open Kontact, which is set to open on the summary page. On the summary page I have two links, one for the inbox and one for a spam folder. Clicking on either of these links crashes Kontact Restarting the app and clicking on either link makes Kontact crash again and again no matter how many times you restart Kontact -- Backtrace: Application: Kontact (kontact), signal: Segmentation fault Using host libthread_db library "/lib64/libthread_db.so.1". 82T_PSEUDO (SYSCALL_SYMBOL, SYSCALL_NAME, SYSCALL_NARGS) [Current thread is 1 (Thread 0x7fde6f6e0840 (LWP 1783))] Thread 3 (Thread 0x7fde64219700 (LWP 1784)): #0 pthread_cond_wait@@GLIBC_2.3.2 () at ../nptl/sysdeps/unix/sysv/linux/x86_64/pthread_cond_wait.S:165 #1 0x0034eb7b86ec in WTF::TCMalloc_PageHeap::scavengerThread (this=0x34ec17cc20) at ../../../Source/JavaScriptCore/wtf/FastMalloc.cpp:2495 #2 0x0034eb7b8819 in WTF::TCMalloc_PageHeap::runScavengerThread (context=) at ../../../Source/JavaScriptCore/wtf/FastMalloc.cpp:1618 #3 0x00369c607d90 in start_thread (arg=0x7fde64219700) at pthread_create.c:309 #4 0x00369c2ef48d in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:115 Thread 2 (Thread 0x7fde63910700 (LWP 1785)): #0 0x00369c2e6af3 in __GI___poll (fds=, nfds=, timeout=) at ../sysdeps/unix/sysv/linux/poll.c:87 #1 0x00369be44fd8 in g_main_context_poll (n_fds=1, fds=0x7fde5c0013e0, priority=, timeout=6359, context=0x7fde5c0009a0) at gmain.c:3402 #2 g_main_context_iterate (context=0x7fde5c0009a0, block=, dispatch=1, self=) at gmain.c:3084 #3 0x00369be4549c in g_main_context_iteration (context=0x7fde5c0009a0, may_block=1) at gmain.c:3152 #4 0x0036a4fa7dc6 in QEventDispatcherGlib::processEvents (this=0x7fde5c0008c0, flags=) at kernel/qeventdispatcher_glib.cpp:426 #5 0x0036a4f78182 in QEventLoop::processEvents (this=, flags=...) at kernel/qeventloop.cpp:149 #6 0x0036a4f783d7 in QEventLoop::exec (this=0x7fde6390fd40, flags=...) at kernel/qeventloop.cpp:204 #7 0x0036a4e78b27 in QThread::exec (this=) at thread/qthread.cpp:501 #8 0x0036a4e7bb6b in QThreadPrivate::start (arg=0x16a8550) at thread/qthread_unix.cpp:298 #9 0x00369c607d90 in start_thread (arg=0x7fde63910700) at pthread_create.c:309 #10 0x00369c2ef48d in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:115 Thread 1 (Thread 0x7fde6f6e0840 (LWP 1783)): [KCrash Handler] #6 0x0036a4f8f71f in QMetaObject::addGuard (ptr=0x7fffb5b7e0f0) at kernel/qobject.cpp:401 #7 0x0036a93cf03d in QPointer (p=0x20d6930, this=0x7fffb5b7e0f0) at ../../src/corelib/kernel/qpointer.h:60 #8 QApplication::notify (this=0x7fffb5b7f1a0, receiver=0x20d6930, e=0x7fffb5b7e370) at kernel/qapplication.cpp:4070 #9 0x003b56050eb6 in KApplication::notify (this=0x7fffb5b7f1a0, receiver=0x20d6930, event=0x7fffb5b7e370) at /usr/src/debug/kdelibs-4.8.0/kdeui/kernel/kapplication.cpp:311 #10 0x0036a4f7904c in QCoreApplication::notifyInternal (this=0x7fffb5b7f1a0, receiver=0x20d6930, event=0x7fffb5b7e370) at kernel/qcoreapplication.cpp:876 #11 0x0036a93ca962 in sendEvent (event=, receiver=) at ../../src/corelib/kernel/qcoreapplication.h:231 #12 QApplicationPrivate::sendMouseEvent (receiver=0x20d6930, event=0x7fffb5b7e370, alienWidget=0x20d6930, nativeWidget=0x1e72eb0, buttonDown=0x20d6930, lastMouseReceiver=..., spontaneous=true) at kernel/qapplication.cpp:3161 #13 0x0036a94462e5 in QETWidget::translateMouseEvent (this=0x1e72eb0, event=) at kernel/qapplication_x11.cpp:4520 #14 0x0036a94451aa in QApplication::x11ProcessEvent (this=0x7fffb5b7f1a0, event=0x7fffb5b7ec30) at kernel/qapplication_x11.cpp:3641 #15 0x0036a946c97c in x11EventSourceDispatch (s=0x1556000, callback=0, user_data=0x0) at kernel/qguieventdispatcher_glib.cpp:148 #16 0x00369be44acd in g_main_dispatch (context=0x1555610) at gmain.c:2441 #17 g_main_context_dispatch (context=0x1555610) at gmain.c:3011 #18 0x00369be452c8 in g_main_context_iterate (context=0x1555610, block=, dispatch=1, self=) at gmain.c:3089 #19 0x00369be4549c in g_main_context_iteration (context=0x1555610, may_block=1) at gmain.c:3152 #20 0x0036a4fa7d5f in QEventDispatcherGlib::processEvents (this=0x151bee0, flags=) at kernel/qeventdispatcher_glib.cpp:424 #21 0x0036a946c66e i
[Bug 294329] New: Kontact crash when clicking on Summary page inbox link
https://bugs.kde.org/show_bug.cgi?id=294329 Summary: Kontact crash when clicking on Summary page inbox link Product: kontact Version: unspecified Platform: Fedora RPMs OS/Version: Linux Status: UNCONFIRMED Severity: crash Priority: NOR Component: general AssignedTo: kdepim-bugs@kde.org ReportedBy: bgodu...@pcprotechs.com Application: kontact (4.8.0) KDE Platform Version: 4.8.00 (4.8.0 Qt Version: 4.8.0 Operating System: Linux 3.2.6-3.fc16.x86_64 x86_64 Distribution: "Fedora release 16 (Verne)" -- Information about the crash: - What I was doing when the application crashed: Open Kontact and on the summary page clicked on the link for the inbox, crash happens every time. Kontact version is 4.8.0 The crash can be reproduced every time. -- Backtrace: Application: Kontact (kontact), signal: Segmentation fault Using host libthread_db library "/lib64/libthread_db.so.1". 82T_PSEUDO (SYSCALL_SYMBOL, SYSCALL_NAME, SYSCALL_NARGS) [Current thread is 1 (Thread 0x7fb9db56c840 (LWP 4095))] Thread 4 (Thread 0x7fb9d00a2700 (LWP 4096)): #0 pthread_cond_wait@@GLIBC_2.3.2 () at ../nptl/sysdeps/unix/sysv/linux/x86_64/pthread_cond_wait.S:165 #1 0x0034eb7b86ec in WTF::TCMalloc_PageHeap::scavengerThread (this=0x34ec17cc20) at ../../../Source/JavaScriptCore/wtf/FastMalloc.cpp:2495 #2 0x0034eb7b8819 in WTF::TCMalloc_PageHeap::runScavengerThread (context=) at ../../../Source/JavaScriptCore/wtf/FastMalloc.cpp:1618 #3 0x00369c607d90 in start_thread (arg=0x7fb9d00a2700) at pthread_create.c:309 #4 0x00369c2ef48d in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:115 Thread 3 (Thread 0x7fb9cf799700 (LWP 4097)): #0 0x00369c2e6af3 in __GI___poll (fds=, nfds=, timeout=) at ../sysdeps/unix/sysv/linux/poll.c:87 #1 0x00369be44fd8 in g_main_context_poll (n_fds=1, fds=0x7fb9c80013e0, priority=, timeout=6617, context=0x7fb9c80009a0) at gmain.c:3402 #2 g_main_context_iterate (context=0x7fb9c80009a0, block=, dispatch=1, self=) at gmain.c:3084 #3 0x00369be4549c in g_main_context_iteration (context=0x7fb9c80009a0, may_block=1) at gmain.c:3152 #4 0x0036a4fa7dc6 in QEventDispatcherGlib::processEvents (this=0x7fb9c80008c0, flags=) at kernel/qeventdispatcher_glib.cpp:426 #5 0x0036a4f78182 in QEventLoop::processEvents (this=, flags=...) at kernel/qeventloop.cpp:149 #6 0x0036a4f783d7 in QEventLoop::exec (this=0x7fb9cf798d40, flags=...) at kernel/qeventloop.cpp:204 #7 0x0036a4e78b27 in QThread::exec (this=) at thread/qthread.cpp:501 #8 0x0036a4e7bb6b in QThreadPrivate::start (arg=0x190c7d0) at thread/qthread_unix.cpp:298 #9 0x00369c607d90 in start_thread (arg=0x7fb9cf799700) at pthread_create.c:309 #10 0x00369c2ef48d in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:115 Thread 2 (Thread 0x7fb986906700 (LWP 4108)): #0 pthread_cond_timedwait@@GLIBC_2.3.2 () at ../nptl/sysdeps/unix/sysv/linux/x86_64/pthread_cond_timedwait.S:216 #1 0x0036a4e7bfdf in wait (time=3, this=0x2094d70) at thread/qwaitcondition_unix.cpp:84 #2 QWaitCondition::wait (this=, mutex=0x2094d18, time=3) at thread/qwaitcondition_unix.cpp:158 #3 0x0036a4e6f5af in QThreadPoolThread::run (this=0x20a6be0) at concurrent/qthreadpool.cpp:141 #4 0x0036a4e7bb6b in QThreadPrivate::start (arg=0x20a6be0) at thread/qthread_unix.cpp:298 #5 0x00369c607d90 in start_thread (arg=0x7fb986906700) at pthread_create.c:309 #6 0x00369c2ef48d in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:115 Thread 1 (Thread 0x7fb9db56c840 (LWP 4095)): [KCrash Handler] #6 QApplication::notify (this=, receiver=0x2446d90, e=0x7fffd1b20af0) at kernel/qapplication.cpp:4076 #7 0x003b56050eb6 in KApplication::notify (this=0x7fffd1b217f0, receiver=0x2446d90, event=0x7fffd1b20af0) at /usr/src/debug/kdelibs-4.8.0/kdeui/kernel/kapplication.cpp:311 #8 0x0036a4f7904c in QCoreApplication::notifyInternal (this=0x7fffd1b217f0, receiver=0x2446d90, event=0x7fffd1b20af0) at kernel/qcoreapplication.cpp:876 #9 0x0036a93ca962 in sendEvent (event=, receiver=) at ../../src/corelib/kernel/qcoreapplication.h:231 #10 QApplicationPrivate::sendMouseEvent (receiver=0x2446d90, event=0x7fffd1b20af0, alienWidget=0x2446d90, nativeWidget=0x21fde60, buttonDown=0x2446d90, lastMouseReceiver=..., spontaneous=true) at kernel/qapplication.cpp:3161 #11 0x0036a94462e5 in QETWidget::translateMouseEvent (this=0x21fde60, event=) at kernel/qapplication_x11.cpp:4520 #12 0x0036a94451aa in QApplication::x11ProcessEvent (this=0x7fffd1b217f0, event=0x7fffd1b213b0) at kernel/qapplication_x11.cpp:3641 #13 0x0036a946c97c in x11EventSourceDispatch (s=0x17b98e0, callback=0, user_data=0x0) at kernel/qguieventdispatcher_glib.cpp:148 #14 0x00369be44acd in g_main_dispatch (context=0x17b9400) at gmain.c:2441 #15 g_main_context_dispatch (context=0x17b9400) at gmain.c:3011 #16 0x00369be452c8 in g_main_context_itera
[Bug 294083] Kamil tripled directory structure adding one local folder group(dupe of mail structure) and one called akonadi reource also dupe of orginal structure
https://bugs.kde.org/show_bug.cgi?id=294083 --- Comment #4 from2012-02-16 23:37:29 --- On Thursday, February 16, 2012 03:13:00 PM Laurent Montel wrote: > https://bugs.kde.org/show_bug.cgi?id=294083 > > > > > > --- Comment #3 from Laurent Montel 2012-02-16 15:12:59 --- > Yes if it's a bug it needs to be fix, right. > But how I reproduce it > I use kmail2 from 1 year and I don't see this bug... That's a good question? From what I can tell by looking through the various directories that akonadi points to, it seems it is an akonadi issue. Now if it is a back end problem with the database or not is yet another question! Now as I have stated, I went in to the akonadi configuration module in system setting and followed the paths in the file system and checked and they do exist but the are empty. So I went back into akonadi configuration and deleted those entries and before I could stop the akonadi service it recreated the entry I just deleted out of thin air. This should not happen. I do have program experience but it is windows based using VB 6 enterprise. So what I did was delete the directories that akonadi was pointing to, then deleted the resource out of akonadi configuration and before I could stop the akonadi service it recreated the entire resource yet again right down to the file directory in the system. Something is very wrong and from what I've seen it appears to be in the back end and the akonadi server itself. Hope this helps. The machine I'm currently using I'm going to upgrade to 4.8 but if you want I have another laptop that I can configure to match the configuration of this one after I clean it all up of old data which may take some time since I'm going away for a week for my 25th anniversary. Let me know if you want me to assist further in tracking down this ugly bug. My current system is Fedora 16 running the KDE 4.7.4 compilation with no other desktop software installed! -- Configure bugmail: https://bugs.kde.org/userprefs.cgi?tab=email --- You are receiving this mail because: --- You are the assignee for the bug. ___ Kdepim-bugs mailing list Kdepim-bugs@kde.org https://mail.kde.org/mailman/listinfo/kdepim-bugs
[Bug 294083] Kamil tripled directory structure adding one local folder group(dupe of mail structure) and one called akonadi reource also dupe of orginal structure
https://bugs.kde.org/show_bug.cgi?id=294083 bgodu...@pcprotechs.com changed: What|Removed |Added CC||bgodu...@pcprotechs.com --- Comment #2 from2012-02-15 11:37:30 --- I've been running the 4.7.4 software for almost a week before this happened. Yes my old mail was imported but that was a an entire week ago with no problems. When you go into the akonadi manager all this stuff just started showing up. There are serious problems going on with Kmail since it port to kmail2. Goggle Kmail and you'll see there are thousands of complaints on things that are happening with people trying to figure out how to fix it on their own.. As I stated Kmail has been working fine for an entire week with no problems of duplicate folders showing up at all, then yesterday all of a sudden these new folders show up out of nowhere, WHY? You can't remove them because they just magically come back. Even if I delete then from the akonadi software it recreates them by itself and adds them back into Kmail. This is a serious bug that needs to be fixed! -- Configure bugmail: https://bugs.kde.org/userprefs.cgi?tab=email --- You are receiving this mail because: --- You are the assignee for the bug. ___ Kdepim-bugs mailing list Kdepim-bugs@kde.org https://mail.kde.org/mailman/listinfo/kdepim-bugs
[Bug 294083] New: Kamil tripled directory structure adding one local folder group(dupe of mail structure) and one called akonadi reource also dupe of orginal structure
https://bugs.kde.org/show_bug.cgi?id=294083 Summary: Kamil tripled directory structure adding one local folder group(dupe of mail structure) and one called akonadi reource also dupe of orginal structure Product: kmail2 Version: 4.7 Platform: Fedora RPMs OS/Version: Linux Status: UNCONFIRMED Severity: major Priority: NOR Component: general AssignedTo: kdepim-bugs@kde.org ReportedBy: bgodu...@pcprotechs.com Created an attachment (id=68796) --> (http://bugs.kde.org/attachment.cgi?id=68796) ikage of tripled directory structure Version: 4.7 (using KDE 4.7.4) OS:Linux Opened Kmail this morning all looked fine. Left machine running came back after 3 hours and the directory struture has trippled! I now have the original directory structure, one called local folders and one called akonadi mail resource! These two new directory structures are completely void of any mail but they are exact duplicates of the original local folders created by kmail. It's as if they are ghosts of the original structure minus all the mail in the real local mail folder. Reproducible: Always Steps to Reproduce: See screenshot attachement Expected Results: A single directory structure that does NOT triplicate itself OS: Fedora 16 (x86_64) release 3.2.5-3.fc16.x86_64 Compiler: gcc -- Configure bugmail: https://bugs.kde.org/userprefs.cgi?tab=email --- You are receiving this mail because: --- You are the assignee for the bug. ___ Kdepim-bugs mailing list Kdepim-bugs@kde.org https://mail.kde.org/mailman/listinfo/kdepim-bugs
[Bug 293553] New: crash on close
https://bugs.kde.org/show_bug.cgi?id=293553 Summary: crash on close Product: kontact Version: unspecified Platform: Fedora RPMs OS/Version: Linux Status: UNCONFIRMED Severity: crash Priority: NOR Component: general AssignedTo: kdepim-bugs@kde.org ReportedBy: bgodu...@pcprotechs.com Application: kontact (4.7.4) KDE Platform Version: 4.7.4 (4.7.4) Qt Version: 4.7.4 Operating System: Linux 2.6.41.10-3.fc15.x86_64 x86_64 Distribution: "Fedora release 15 (Lovelock)" -- Information about the crash: - What I was doing when the application crashed:Closed Kontact after deleting mail. Password dialog seems to remain constantly open in the back ground The crash can be reproduced every time. -- Backtrace: Application: Kontact (kontact), signal: Segmentation fault 82T_PSEUDO (SYSCALL_SYMBOL, SYSCALL_NAME, SYSCALL_NARGS) [Current thread is 1 (Thread 0x7f7835d62840 (LWP 1975))] Thread 3 (Thread 0x7f782bd0e700 (LWP 1976)): #0 pthread_cond_wait@@GLIBC_2.3.2 () at ../nptl/sysdeps/unix/sysv/linux/x86_64/pthread_cond_wait.S:165 #1 0x0032a2cca93a in WTF::TCMalloc_PageHeap::scavengerThread (this=0x32a34cf2c0) at wtf/FastMalloc.cpp:2378 #2 0x0032a2ccaa29 in WTF::TCMalloc_PageHeap::runScavengerThread (context=) at wtf/FastMalloc.cpp:1497 #3 0x00327ae07b41 in start_thread (arg=0x7f782bd0e700) at pthread_create.c:305 #4 0x00327a6df49d in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:115 Thread 2 (Thread 0x7f782b405700 (LWP 1977)): #0 0x00327ae0a9a9 in __pthread_mutex_unlock_usercnt (mutex=0x7f78240009b8, decr=) at pthread_mutex_unlock.c:53 #1 __pthread_mutex_unlock (mutex=0x7f78240009b8) at pthread_mutex_unlock.c:298 #2 0x00327de41cb4 in g_main_context_prepare (context=0x7f78240009b0, priority=0x7f782b404c18) at gmain.c:2760 #3 0x00327de42bbd in g_main_context_iterate (context=0x7f78240009b0, block=1, dispatch=1, self=) at gmain.c:3072 #4 0x00327de4325c in g_main_context_iteration (context=0x7f78240009b0, may_block=1) at gmain.c:3155 #5 0x0030765853f6 in QEventDispatcherGlib::processEvents (this=0x7f78240008c0, flags=) at kernel/qeventdispatcher_glib.cpp:424 #6 0x003076559e02 in QEventLoop::processEvents (this=, flags=...) at kernel/qeventloop.cpp:149 #7 0x003076559fff in QEventLoop::exec (this=0x7f782b404d40, flags=...) at kernel/qeventloop.cpp:201 #8 0x00307647207f in QThread::exec (this=) at thread/qthread.cpp:498 #9 0x003076474af5 in QThreadPrivate::start (arg=0x1073280) at thread/qthread_unix.cpp:331 #10 0x00327ae07b41 in start_thread (arg=0x7f782b405700) at pthread_create.c:305 #11 0x00327a6df49d in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:115 Thread 1 (Thread 0x7f7835d62840 (LWP 1975)): [KCrash Handler] #6 operator QItemSelectionModel* (this=) at ../../src/corelib/kernel/qpointer.h:78 #7 QAbstractItemView::selectionModel (this=0x322d005347414c46) at itemviews/qabstractitemview.cpp:760 #8 0x003608885f08 in MailCommon::FolderTreeWidget::selectedCollections() const () from /usr/lib64/libmailcommon.so.4 #9 0x003607f2c3ce in KMMainWidget::updateFolderMenu() () from /usr/lib64/libkmailprivate.so.4 #10 0x003607f3bac3 in KMMainWidget::slotEndCheckFetchCollectionsDone(KJob*) () from /usr/lib64/libkmailprivate.so.4 #11 0x003607f3c408 in KMMainWidget::slotEndCheckMail() () from /usr/lib64/libkmailprivate.so.4 #12 0x003607f3fa81 in KMMainWidget::qt_metacall(QMetaObject::Call, int, void**) () from /usr/lib64/libkmailprivate.so.4 #13 0x00307656d5aa in QMetaObject::activate (sender=0x1495bf0, m=, local_signal_index=, argv=0x0) at kernel/qobject.cpp:3278 #14 0x003607eed9ec in KMKernel::slotProgressItemCompletedOrCanceled(KPIM::ProgressItem*) () from /usr/lib64/libkmailprivate.so.4 #15 0x003607ef804a in KMKernel::qt_metacall(QMetaObject::Call, int, void**) () from /usr/lib64/libkmailprivate.so.4 #16 0x00307656d5aa in QMetaObject::activate (sender=0x122c780, m=, local_signal_index=, argv=0x7fffe41d3fb0) at kernel/qobject.cpp:3278 #17 0x003603074332 in KPIM::ProgressManager::progressItemCompleted(KPIM::ProgressItem*) () from /usr/lib64/libkdepim.so.4 #18 0x003603074e63 in KPIM::ProgressManager::qt_metacall(QMetaObject::Call, int, void**) () from /usr/lib64/libkdepim.so.4 #19 0x00307656d5aa in QMetaObject::activate (sender=0x19c2060, m=, local_signal_index=, argv=0x7fffe41d40c0) at kernel/qobject.cpp:3278 #20 0x003603073f02 in KPIM::ProgressItem::progressItemCompleted(KPIM::ProgressItem*) () from /usr/lib64/libkdepim.so.4 #21 0x003603075bce in ?? () from /usr/lib64/libkdepim.so.4 #22 0x003603075dc2 in ?? () from /usr/lib64/libkdepim.so.4 #23 0x00307656d5aa in QMetaObject::activate (sender=0x14c73c0, m=, local_signal_index=, argv=0x7fffe41d41f0) at kernel/qobject.cpp:3278 #24 0x0035ff691905 in Akonadi::AgentManager::instanceStatusChanged (this=, _t1=) at /usr/sr
[Bug 269358] New: crash on open
https://bugs.kde.org/show_bug.cgi?id=269358 Summary: crash on open Product: kontact Version: 4.4.10 Platform: Fedora RPMs OS/Version: Linux Status: UNCONFIRMED Severity: crash Priority: NOR Component: general AssignedTo: kdepim-bugs@kde.org ReportedBy: bgodu...@pcprotechs.com Application: kontact (4.4.10) KDE Platform Version: 4.6.1 (4.6.1) Qt Version: 4.7.2 Operating System: Linux 2.6.35.11-83.fc14.i686 i686 Distribution (Platform): Fedora RPMs -- Information about the crash: - What I was doing when the application crashed: Serving the web. Went to open Kontact and it crashed before even opening. Just clicking on the desktop icon(link) caused this crash. Kontact was open previously and shut down correctly when closed. -- Backtrace: Application: Kontact (kontact), signal: Segmentation fault [KCrash Handler] #7 0x0509367c in QString (this=0x9bf1a98) at /usr/include/QtCore/qstring.h:728 #8 KontactInterface::Plugin::identifier (this=0x9bf1a98) at /usr/src/debug/kdepimlibs-4.6.1/kontactinterface/plugin.cpp:101 #9 0x05050fae in Kontact::MainWindow::activateInitialPluginModule (this=0x9a9c8f8) at /usr/src/debug/kdepim-4.4.10/kontact/src/mainwindow.cpp:289 #10 0x05051065 in Kontact::MainWindow::setInitialActivePluginModule (this=0x9a9c8f8, module=...) at /usr/src/debug/kdepim-4.4.10/kontact/src/mainwindow.cpp:266 #11 0x0804aa4f in KontactApp::newInstance (this=0xbf807cc4) at /usr/src/debug/kdepim-4.4.10/kontact/src/main.cpp:149 #12 0x075a3785 in KUniqueApplicationAdaptor::newInstance (this=0x99f32c0, asn_id=..., args=...) at /usr/src/debug/kdelibs-4.6.1/kdeui/kernel/kuniqueapplication.cpp:436 #13 0x075a3843 in KUniqueApplicationAdaptor::qt_metacall (this=0x99f32c0, _c=QMetaObject::InvokeMetaMethod, _id=0, _a=0xbf80724c) at /usr/src/debug/kdelibs-4.6.1/i686-redhat-linux-gnu/kdeui/kuniqueapplication_p.moc:81 #14 0x00161f35 in QDBusConnectionPrivate::deliverCall (this=0x9978d80, object=0x99f32c0, msg=..., metaTypes=..., slotIdx=4) at qdbusintegrator.cpp:941 #15 0x00163147 in QDBusConnectionPrivate::activateCall (this=0x9978d80, object=0x99f32c0, flags=337, msg=...) at qdbusintegrator.cpp:851 #16 0x001636b0 in QDBusConnectionPrivate::activateObject (this=0x9978d80, node=..., msg=..., pathStartPos=16) at qdbusintegrator.cpp:1429 #17 0x00163b3b in QDBusActivateObjectEvent::placeMetaCall (this=0x9e07530) at qdbusintegrator.cpp:1523 #18 0x06e777cf in QObject::event (this=0xbf807cc4, e=0x9e07530) at kernel/qobject.cpp:1217 #19 0x06e6256c in QCoreApplication::event (this=0xbf807cc4, e=0x9e07530) at kernel/qcoreapplication.cpp:1560 #20 0x021c9b60 in QApplication::event (this=0xbf807cc4, e=0x9e07530) at kernel/qapplication.cpp:2503 #21 0x021c754c in QApplicationPrivate::notify_helper (this=0x9986f48, receiver=0xbf807cc4, e=0x9e07530) at kernel/qapplication.cpp:4462 #22 0x021cc252 in QApplication::notify (this=0xbf807cc4, receiver=0xbf807cc4, e=0x9e07530) at kernel/qapplication.cpp:3862 #23 0x0759c92b in KApplication::notify (this=0xbf807cc4, receiver=0xbf807cc4, event=0x9e07530) at /usr/src/debug/kdelibs-4.6.1/kdeui/kernel/kapplication.cpp:311 #24 0x06e61f63 in QCoreApplication::notifyInternal (this=0xbf807cc4, receiver=0xbf807cc4, event=0x9e07530) at kernel/qcoreapplication.cpp:731 #25 0x06e65cb5 in sendEvent (receiver=0x0, event_type=0, data=0x9960a88) at kernel/qcoreapplication.h:215 #26 QCoreApplicationPrivate::sendPostedEvents (receiver=0x0, event_type=0, data=0x9960a88) at kernel/qcoreapplication.cpp:1372 #27 0x06e65e8e in QCoreApplication::sendPostedEvents (receiver=0x0, event_type=0) at kernel/qcoreapplication.cpp:1265 #28 0x06e8fb35 in sendPostedEvents (s=0x998c390) at kernel/qcoreapplication.h:220 #29 postEventSourceDispatch (s=0x998c390) at kernel/qeventdispatcher_glib.cpp:277 #30 0x004a0192 in g_main_dispatch (context=0x998c310) at gmain.c:2149 #31 g_main_context_dispatch (context=0x998c310) at gmain.c:2702 #32 0x004a0978 in g_main_context_iterate (context=0x998c310, block=1, dispatch=1, self=) at gmain.c:2780 #33 0x004a0c35 in g_main_context_iteration (context=0x998c310, may_block=1) at gmain.c:2843 #34 0x06e8fcad in QEventDispatcherGlib::processEvents (this=0x99607f0, flags=...) at kernel/qeventdispatcher_glib.cpp:422 #35 0x0227b1c6 in QGuiEventDispatcherGlib::processEvents (this=0x99607f0, flags=...) at kernel/qguieventdispatcher_glib.cpp:207 #36 0x06e610fa in QEventLoop::processEvents (this=0xbf807c24, flags=...) at kernel/qeventloop.cpp:149 #37 0x06e613aa in QEventLoop::exec (this=0xbf807c24, flags=...) at kernel/qeventloop.cpp:201 #38 0x06e65f57 in QCoreApplication::exec () at kernel/qcoreapplication.cpp:1008 #39 0x021c5358 in QApplication::exec () at kernel/qapplication.cpp:3736 #40 0x0804b76b in main (argc=162187272, argv=0xa0eb830) at /usr/src/debug/kdepim-4.4.10/kontact/src/main.cpp:224 Possible duplicates by query: bug 267199, bug 256827, bug 256085, bug 255142, bug 249532. Reported usi
[Bug 257571] New: Crashed making configuration changes
https://bugs.kde.org/show_bug.cgi?id=257571 Summary: Crashed making configuration changes Product: kontact Version: unspecified Platform: Fedora RPMs OS/Version: Linux Status: UNCONFIRMED Severity: crash Priority: NOR Component: general AssignedTo: kdepim-bugs@kde.org ReportedBy: bgodu...@pcprotechs.com Application: kontact (4.4.7) KDE Platform Version: 4.5.3 (KDE 4.5.3) Qt Version: 4.6.3 Operating System: Linux 2.6.34.7-61.fc13.i686 i686 Distribution (Platform): Fedora RPMs -- Information about the crash: - What I was doing when the application crashed: Setting up the back end for archiving and clicked on the explore button to find the program. This is the intial setup for the back end archiving feature -- Backtrace: Application: Kontact (kontact), signal: Segmentation fault [KCrash Handler] #7 0x03bf7848 in ?? () from /usr/lib/kde4/akregator_config_advanced.so #8 0x03bf78f2 in ?? () from /usr/lib/kde4/akregator_config_advanced.so #9 0x07b62bcb in QMetaObject::metacall (object=0x9e7aa70, cl=QMetaObject::InvokeMetaMethod, idx=27, argv=0xbfebf888) at kernel/qmetaobject.cpp:237 #10 0x07b71a75 in QMetaObject::activate (sender=0x9e7bd38, m=0x2cedb64, local_signal_index=2, argv=0xbfebf888) at kernel/qobject.cpp:3295 #11 0x02ab629a in QAbstractButton::clicked (this=0x9e7bd38, _t1=false) at .moc/release-shared/moc_qabstractbutton.cpp:206 #12 0x027c75fa in QAbstractButtonPrivate::emitClicked (this=0x9e7bd50) at widgets/qabstractbutton.cpp:546 #13 0x027c8945 in QAbstractButtonPrivate::click (this=0x9e7bd50) at widgets/qabstractbutton.cpp:539 #14 0x027c8c0e in QAbstractButton::mouseReleaseEvent (this=0x9e7bd38, e=0xbfebffd0) at widgets/qabstractbutton.cpp:1121 #15 0x0244061d in QWidget::event (this=0x9e7bd38, event=0xbfebffd0) at kernel/qwidget.cpp:8044 #16 0x027c749f in QAbstractButton::event (this=0x9e7bd38, e=0xbfebffd0) at widgets/qabstractbutton.cpp:1080 #17 0x02865843 in QPushButton::event (this=0x9e7bd38, e=0xbfebffd0) at widgets/qpushbutton.cpp:679 #18 0x023ed77c in QApplicationPrivate::notify_helper (this=0x937e698, receiver=0x9e7bd38, e=0xbfebffd0) at kernel/qapplication.cpp:4306 #19 0x023f4d7e in QApplication::notify (this=0xbfec0884, receiver=0x9e7bd38, e=0xbfebffd0) at kernel/qapplication.cpp:3871 #20 0x06047fab in KApplication::notify (this=0xbfec0884, receiver=0x9e7bd38, event=0xbfebffd0) at /usr/src/debug/kdelibs-4.5.3/kdeui/kernel/kapplication.cpp:310 #21 0x07b5e133 in QCoreApplication::notifyInternal (this=0xbfec0884, receiver=0x9e7bd38, event=0xbfebffd0) at kernel/qcoreapplication.cpp:726 #22 0x023f3ae8 in sendEvent (receiver=0x9e7bd38, event=0xbfebffd0, alienWidget=0x9e7bd38, nativeWidget=0x9b25750, buttonDown=0x2cf6318, lastMouseReceiver=..., spontaneous=true) at ../../src/corelib/kernel/qcoreapplication.h:215 #23 QApplicationPrivate::sendMouseEvent (receiver=0x9e7bd38, event=0xbfebffd0, alienWidget=0x9e7bd38, nativeWidget=0x9b25750, buttonDown=0x2cf6318, lastMouseReceiver=..., spontaneous=true) at kernel/qapplication.cpp:2971 #24 0x024712f0 in QETWidget::translateMouseEvent (this=0x9b25750, event=0xbfec04ec) at kernel/qapplication_x11.cpp:4380 #25 0x02470743 in QApplication::x11ProcessEvent (this=0xbfec0884, event=0xbfec04ec) at kernel/qapplication_x11.cpp:3391 #26 0x0249c74a in x11EventSourceDispatch (s=0x937a0e8, callback=0, user_data=0x0) at kernel/qguieventdispatcher_glib.cpp:146 #27 0x00510525 in g_main_dispatch (context=0x9379490) at gmain.c:1960 #28 IA__g_main_context_dispatch (context=0x9379490) at gmain.c:2513 #29 0x00514268 in g_main_context_iterate (context=0x477490, block=1, dispatch=1, self=0x9381fd8) at gmain.c:2591 #30 0x00514449 in IA__g_main_context_iteration (context=0x9379490, may_block=1) at gmain.c:2654 #31 0x07b86446 in QEventDispatcherGlib::processEvents (this=0x9355c18, flags=...) at kernel/qeventdispatcher_glib.cpp:412 #32 0x0249c336 in QGuiEventDispatcherGlib::processEvents (this=0x9355c18, flags=...) at kernel/qguieventdispatcher_glib.cpp:204 #33 0x07b5c80a in QEventLoop::processEvents (this=0xbfec07e4, flags=...) at kernel/qeventloop.cpp:149 #34 0x07b5cb4a in QEventLoop::exec (this=0xbfec07e4, flags=...) at kernel/qeventloop.cpp:201 #35 0x07b60807 in QCoreApplication::exec () at kernel/qcoreapplication.cpp:1003 #36 0x023ed828 in QApplication::exec () at kernel/qapplication.cpp:3585 #37 0x0804b32d in _start () Possible duplicates by query: bug 257341, bug 257334, bug 257114, bug 257028, bug 256278. Reported using DrKonqi -- Configure bugmail: https://bugs.kde.org/userprefs.cgi?tab=email --- You are receiving this mail because: --- You are the assignee for the bug. ___ Kdepim-bugs mailing list Kdepim-bugs@kde.org https://mail.kde.org/mailman/listinfo/kdepim-bugs
